Tcp-Ip4vse 1.5f Messages 20130301

Messages
Version 1 Release 5F
TCP/IP is a communications
facility that permits bi-directional
communication between VSE-based
software and software running on other
platforms equipped with TCP/IP.
This manual contains detailed explanations

of the messages issued by the programs
that make up the TCP/IP for VSE product.
Published March 2013. Copyright © 2013 CSI International

Copyright © 2013 by CSI International
All Rights Reserved
RESTRICTED RIGHTS LEGEND
Use, duplication, or disclosure by the Government is subject to the

restrictions as set forth in subparagraph (c)(1)(ii) of the Rights in
Technical Data and Computer Software clause at DFARS
252.227-7013.
This material contains confidential and proprietary material of

Connectivity Systems, Inc. (hereafter referred to as CSI International
and CSI) and may not be used in any way without written authorization
from CSI International. This material may not be reproduced, in whole
or in part, in any way, without prior written permission from CSI
International.
Permission is hereby granted to copy and distribute this document as

follows:
• Each copy must be a complete and accurate copy.

• All copyright notices must be retained.
• No modifications may be made.
• Use of each copy is restricted to the evaluation and/or promotion of
CSI International’s TCP/IP FOR VSE product or in accordance with a
license agreement.
TCP/IP FOR VSE Messages

Version 1 Release 5F
March 2013
Published by CSI International

8120 State Route 138
Williamsport OH 43164
Phone: 800-795-4914
Fax: 740-986-6022
Internet: http://www.csi-international.com
E-mail: info@csi-international.com
Technical Support: support@csi-international.com
Documentation comments: documentation@csi-international.com
CSI International Technical Support and
Technical Support Escalation
CSI Product
Technical Support
During Business Hours Monday through Friday, 9:00 A.M. through 5:00 P.M. EST/EDT
• Telephone
Toll Free in the USA: 800-795-4914
Worldwide: 740-420-5400
• E-mail
Questions: support@csi-international.com
• Web
http://csi-international.com/problemreport_vse.htm
Emergency Service After business hours, and 24 hours on Saturday and Sunday
(24/7)
• Telephone1
Worldwide: 740-420-5400
Escalating
Technical Issues
Business Hours Monday through Friday, 9:00 A.M. through 5:00 P.M. EST/EDT
Request support escalation by the telephone numbers or e-mail address listed

below.
1. Calls are automatically transferred to a 24/7 answering service that forwards all calls based on severity.

i
TCP-IP FOR VSE 1.5F Messages CSI International Technical Support
• Telephone
Worldwide: 740-420-5400
• E-mail
Escalation: support@csi-international.com
After Hours (SEV1) 1. Call one of the following telephone numbers.

Worldwide: 740-420-5400
2. Tell the operator that you have a “SEV1” issue.
The answering service will follow the following chain:

a. Technical Support Rep(s)
b. Product Developer (if necessary)
c. Technical Support Manager (if necessary)
d. Development Manager (if necessary)
e. Chief Operating Officer (if necessary)
f. Chief Executive Officer (if necessary)
3. Calls continue until the best person to resolve your issue is contacted.

ii
Updates
The following tables identify updates to the TCP/IP FOR VSE Messages.
These updates are associated with incidents in the CSI support database.
Recent changes are marked with a change bar in the margin.
Published March 2013

Chg ID Message Change Description Page
F007161 TCP140E Added this message to the manual 24.1
F007176 TEL927D/I Clarified that the return code is in hex 25.4
Published March 2012

F007138 TEL927D/I Added this message to the manual 25.4
Published February 2012

F007110 FTP301D Added this message to the manual 4.7

F007130 IPL615I Clarified the description of two values 12.15
output by QUERY STATS,LINKID=
F007102 IPN755I Added this message to the manual 13.78
F007134 IPN889I Clarified the meaning of two values 13.94
output by QUERY IBBLOK

iii
TCP-IP FOR VSE 1.5F Messages Updates

iv
Contents
CSI International Technical Support and Technical Support Escalation .................. i
Updates.......................................................................................................................... iii
1 BSD Series Messages .......................................................................................... 1.1

BSD001I ..............................................................................................................................1.1
BSD002I ..............................................................................................................................1.1
BSD003I ..............................................................................................................................1.1
BSD004D .............................................................................................................................1.1
BSD005I ..............................................................................................................................1.1
BSD006I ..............................................................................................................................1.2
BSD100I ..............................................................................................................................1.2
BSD101D .............................................................................................................................1.2
BSD102D .............................................................................................................................1.2
BSD103W ............................................................................................................................1.2
BSD104D .............................................................................................................................1.2
BSD105D .............................................................................................................................1.3
BSD106D .............................................................................................................................1.3
BSD108I ..............................................................................................................................1.3
BSD109I ..............................................................................................................................1.3
BSD110I ..............................................................................................................................1.3
BSD111D .............................................................................................................................1.4
BSD112D .............................................................................................................................1.4
BSD113I ..............................................................................................................................1.4
BSD114I ..............................................................................................................................1.4
BSD115I ..............................................................................................................................1.4
BSD116D .............................................................................................................................1.5
BSD117D .............................................................................................................................1.5
BSD119D .............................................................................................................................1.5
BSD120I ..............................................................................................................................1.5

v
TCP-IP FOR VSE 1.5F Messages Contents
BSD121I ..............................................................................................................................1.5
BSD122D .............................................................................................................................1.5
BSD123D .............................................................................................................................1.5
BSD124D .............................................................................................................................1.6
BSD125D .............................................................................................................................1.6
BSD126D .............................................................................................................................1.6
BSD127D .............................................................................................................................1.6
2 CGL Series Messages .......................................................................................... 2.1

CGL001W ............................................................................................................................2.1
CGL002E .............................................................................................................................2.1
CGL004W ............................................................................................................................2.1
CGL005I ..............................................................................................................................2.2
CGL010I ..............................................................................................................................2.2
CGL010I ..............................................................................................................................2.2
CGL011E .............................................................................................................................2.2
CGL012W ............................................................................................................................2.2
CGL015E .............................................................................................................................2.2
CGL016I ..............................................................................................................................2.3
CGL022I ..............................................................................................................................2.3
CGL023I ..............................................................................................................................2.3
CGL024E .............................................................................................................................2.3
CGL025I ..............................................................................................................................2.3
CGL026I ..............................................................................................................................2.3
CGL027I ..............................................................................................................................2.3
CGL029I ..............................................................................................................................2.3
CGL030I ..............................................................................................................................2.4
CGL031I ..............................................................................................................................2.4
CGL032I ..............................................................................................................................2.4
CGL033I ..............................................................................................................................2.4
CGL034I ..............................................................................................................................2.4
CGL035I ..............................................................................................................................2.4
CGL036I ..............................................................................................................................2.4
CGL037I ..............................................................................................................................2.4
CGL038I ..............................................................................................................................2.5
CGL039I ..............................................................................................................................2.5
CGL040I ..............................................................................................................................2.5
CGL041I ..............................................................................................................................2.5
CGL042I ..............................................................................................................................2.5
CGL043I ..............................................................................................................................2.5
CGL044I ..............................................................................................................................2.5
CGL045I ..............................................................................................................................2.5
CGL046I ..............................................................................................................................2.6
CGL047I ..............................................................................................................................2.6
CGL048I ..............................................................................................................................2.6
CGL049I ..............................................................................................................................2.6

vi
CGL050I ..............................................................................................................................2.6
CGL051I ..............................................................................................................................2.6
CGL052W ............................................................................................................................2.6
CGL053I ..............................................................................................................................2.6
CGL054W ............................................................................................................................2.7
CGL055I ..............................................................................................................................2.7
CGL056I ..............................................................................................................................2.7
CGL057W ............................................................................................................................2.7
CGL058W ............................................................................................................................2.7
CGL059I ..............................................................................................................................2.7
CGL060I ..............................................................................................................................2.8
CGL061I ..............................................................................................................................2.8
CGL062E .............................................................................................................................2.8
CGL063W ............................................................................................................................2.8
CGL064E .............................................................................................................................2.8
CGL065I ..............................................................................................................................2.8
CGL066E .............................................................................................................................2.9
CGL067I ..............................................................................................................................2.9
CGL100I ..............................................................................................................................2.9
CGL101I ..............................................................................................................................2.9
3 EXE Series Messages .......................................................................................... 3.1

EXE001I ..............................................................................................................................3.1
EXE002I ..............................................................................................................................3.1
EXE003E .............................................................................................................................3.1
EXE004E .............................................................................................................................3.1
EXE005I ..............................................................................................................................3.2
EXE006I ..............................................................................................................................3.2
EXE007E .............................................................................................................................3.2
EXE008E .............................................................................................................................3.2
EXE009E .............................................................................................................................3.2
EXE010E .............................................................................................................................3.3
EXE011E .............................................................................................................................3.3
EXE012E .............................................................................................................................3.3
EXE013I ..............................................................................................................................3.3
EXE014W ............................................................................................................................3.3
4 FTP Series Messages ........................................................................................... 4.1

FTP100I ...............................................................................................................................4.1
FTP101I ...............................................................................................................................4.1
FTP102I ...............................................................................................................................4.1
FTP103E ..............................................................................................................................4.1
FTP104E ..............................................................................................................................4.1
FTP105I ...............................................................................................................................4.2
FTP106I ...............................................................................................................................4.2

vii
FTP107W .............................................................................................................................4.2
FTP108I ...............................................................................................................................4.2
FTP109I ...............................................................................................................................4.2
FTP110I ...............................................................................................................................4.2
FTP111I ...............................................................................................................................4.2
FTP112E ..............................................................................................................................4.3
FTP113E ..............................................................................................................................4.3
FTP114E ..............................................................................................................................4.3
FTP115I ...............................................................................................................................4.3
FTP116I ...............................................................................................................................4.3
FTP117I ...............................................................................................................................4.3
FTP118I ...............................................................................................................................4.3
FTP120I ...............................................................................................................................4.3
FTP121I ...............................................................................................................................4.4
FTP122E ..............................................................................................................................4.4
FTP124W .............................................................................................................................4.4
FTP125E ..............................................................................................................................4.4
FTP126W .............................................................................................................................4.4
FTP127I ...............................................................................................................................4.5
FTP128I ...............................................................................................................................4.5
FTP129E ..............................................................................................................................4.5
FTP130E ..............................................................................................................................4.5
FTP131I ...............................................................................................................................4.5
FTP132I ...............................................................................................................................4.5
FTP133W .............................................................................................................................4.5
FTP134W .............................................................................................................................4.6
FTP137W .............................................................................................................................4.6
FTP300I ...............................................................................................................................4.6
FTP301D ..............................................................................................................................4.7
FTP301E ..............................................................................................................................4.7
FTP302I ...............................................................................................................................4.7
FTP303E ..............................................................................................................................4.8
FTP304I ...............................................................................................................................4.8
FTP305I ...............................................................................................................................4.8
FTP306I ...............................................................................................................................4.8
FTP308W .............................................................................................................................4.8
FTP309W .............................................................................................................................4.8
FTP310I ...............................................................................................................................4.8
FTP311I ...............................................................................................................................4.8
FTP312W .............................................................................................................................4.8
FTP313I ...............................................................................................................................4.9
FTP314I ...............................................................................................................................4.9
FTP315E ..............................................................................................................................4.9
FTP316I ...............................................................................................................................4.9
FTP318E ..............................................................................................................................4.9
FTP319E ..............................................................................................................................4.9

viii
FTP320W ...........................................................................................................................4.10
FTP321W ...........................................................................................................................4.10
FTP322E ............................................................................................................................4.10
FTP323E ............................................................................................................................4.10
FTP324E ............................................................................................................................4.11
FTP325W ...........................................................................................................................4.11
FTP326E ............................................................................................................................4.12
FTP327E ............................................................................................................................4.12
FTP328E ............................................................................................................................4.12
FTP329D ............................................................................................................................4.13
FTP330E ............................................................................................................................4.13
FTP331E ............................................................................................................................4.13
FTP332I .............................................................................................................................4.13
FTP333D ............................................................................................................................4.13
FTP341I .............................................................................................................................4.13
FTP342I .............................................................................................................................4.14
FTP343W ...........................................................................................................................4.14
FTP344D ............................................................................................................................4.14
FTP345D ............................................................................................................................4.14
FTP347W ...........................................................................................................................4.14
FTP348W ...........................................................................................................................4.14
FTP349W ...........................................................................................................................4.14
FTP350E ............................................................................................................................4.15
FTP351W ...........................................................................................................................4.15
FTP352W ...........................................................................................................................4.15
FTP353W ...........................................................................................................................4.15
FTP400I .............................................................................................................................4.15
FTP400W ...........................................................................................................................4.15
FTP402I .............................................................................................................................4.16
FTP800I .............................................................................................................................4.16
FTP900I .............................................................................................................................4.16
FTP901W ...........................................................................................................................4.16
FTP903E ............................................................................................................................4.16
FTP904I .............................................................................................................................4.17
FTP905D ............................................................................................................................4.17
FTP906D ............................................................................................................................4.17
FTP908I .............................................................................................................................4.17
FTP909I .............................................................................................................................4.17
FTP910I .............................................................................................................................4.17
FTP911I .............................................................................................................................4.18
FTP912I .............................................................................................................................4.18
FTP916E ............................................................................................................................4.18
FTP917I .............................................................................................................................4.18
FTP918D ............................................................................................................................4.18
FTP919D ............................................................................................................................4.18
FTP920D ............................................................................................................................4.18

ix
FTP921D ............................................................................................................................4.19
FTP922I .............................................................................................................................4.19
FTP923D ............................................................................................................................4.19
FTP928E ............................................................................................................................4.19
FTP930E ............................................................................................................................4.19
FTP931E ............................................................................................................................4.20
FTP933E ............................................................................................................................4.20
FTP934I .............................................................................................................................4.20
FTP935I .............................................................................................................................4.20
FTP936I .............................................................................................................................4.20
FTP938W ...........................................................................................................................4.20
FTP939I .............................................................................................................................4.20
FTP940W ...........................................................................................................................4.21
FTP941I .............................................................................................................................4.21
FTP942W ...........................................................................................................................4.21
FTP945W ...........................................................................................................................4.21
5 GPS Series Messages .......................................................................................... 5.1

GPS900I ...............................................................................................................................5.1
GPS901E ..............................................................................................................................5.1
GPS902E ..............................................................................................................................5.1
GPS903E ..............................................................................................................................5.2
GPS904E ..............................................................................................................................5.2
GPS905W ............................................................................................................................5.2
GPS906E ..............................................................................................................................5.2
GPS907E ..............................................................................................................................5.3
GPS908E ..............................................................................................................................5.3
GPS909I ...............................................................................................................................5.4
GPS910I ...............................................................................................................................5.4
GPS911E ..............................................................................................................................5.4
GPS912I ...............................................................................................................................5.4
GPS913E ..............................................................................................................................5.5
GPS915E ..............................................................................................................................5.5
GPS917I ...............................................................................................................................5.5
GPS918E ..............................................................................................................................5.6
GPS919E ..............................................................................................................................5.6
GPS920E ..............................................................................................................................5.6
GPS921W ............................................................................................................................5.7
GPS922I ...............................................................................................................................5.7
GPS923E ..............................................................................................................................5.7
GPS924I ...............................................................................................................................5.7
GPS925E ..............................................................................................................................5.7
GPS928I ...............................................................................................................................5.8
GPS929E ..............................................................................................................................5.8
GPS930I ...............................................................................................................................5.8
GPS931I ...............................................................................................................................5.8

x
GPS932I ...............................................................................................................................5.8
GPS933I ...............................................................................................................................5.9
GPS934I ...............................................................................................................................5.9
GPS935I ...............................................................................................................................5.9
GPS936I ...............................................................................................................................5.9
GPS937I ...............................................................................................................................5.9
GPS938I ...............................................................................................................................5.9
GPS939I ...............................................................................................................................5.9
GPS940I .............................................................................................................................5.10
GPS941E ............................................................................................................................5.10
GPS942E ............................................................................................................................5.10
GPS943E ............................................................................................................................5.10
GPS944E ............................................................................................................................5.11
GPS947W ..........................................................................................................................5.11
GPS948W ..........................................................................................................................5.11
GPS949E ............................................................................................................................5.11
GPS951W ..........................................................................................................................5.12
GPS952E ............................................................................................................................5.12
GPS953I .............................................................................................................................5.12
GPS954E ............................................................................................................................5.13
GPS956E ............................................................................................................................5.13
GPS957E ............................................................................................................................5.13
GPS958E ............................................................................................................................5.14
GPS959E ............................................................................................................................5.14
GPS960E ............................................................................................................................5.14
GPS961E ............................................................................................................................5.15
GPS962E ............................................................................................................................5.15
GPS963E ............................................................................................................................5.15
GPS964I .............................................................................................................................5.15
GPS965E ............................................................................................................................5.16
GPS966E ............................................................................................................................5.16
GPS967E ............................................................................................................................5.17
GPS968E ............................................................................................................................5.17
GPS969I .............................................................................................................................5.17
GPS970W ..........................................................................................................................5.17
GPS999D ...........................................................................................................................5.17
6 HTT Series Messages .......................................................................................... 6.1

HTT014W ............................................................................................................................6.1
HTT016W ............................................................................................................................6.1
HTT900I ..............................................................................................................................6.1
HTT901E .............................................................................................................................6.1
HTT902E .............................................................................................................................6.2
HTT903I ..............................................................................................................................6.2
HTT904W ............................................................................................................................6.2
HTT905D .............................................................................................................................6.2

xi
HTT906D .............................................................................................................................6.2
HTT907E .............................................................................................................................6.2
HTT908W ............................................................................................................................6.3
HTT909W ............................................................................................................................6.3
HTT910I ..............................................................................................................................6.3
HTT911I ..............................................................................................................................6.3
HTT912W ............................................................................................................................6.4
HTT913W ............................................................................................................................6.4
HTT914W ............................................................................................................................6.4
HTT915W ............................................................................................................................6.4
HTT916D .............................................................................................................................6.4
HTT917D .............................................................................................................................6.4
HTT918D .............................................................................................................................6.5
HTT919E .............................................................................................................................6.5
HTT920D .............................................................................................................................6.5
HTT921D .............................................................................................................................6.5
HTT922D .............................................................................................................................6.5
HTT923D .............................................................................................................................6.5
HTT924D .............................................................................................................................6.6
HTT925D .............................................................................................................................6.6
HTT926D .............................................................................................................................6.6
HTT928I ..............................................................................................................................6.6
HTT929D .............................................................................................................................6.6
HTT930I ..............................................................................................................................6.6
HTT931E .............................................................................................................................6.7
HTT932W ............................................................................................................................6.7
HTT933D .............................................................................................................................6.7
HTT935D .............................................................................................................................6.7
HTT936D .............................................................................................................................6.7
HTT937D .............................................................................................................................6.7
HTT938D .............................................................................................................................6.7
HTT939D .............................................................................................................................6.8
HTT940D .............................................................................................................................6.8
HTT941D .............................................................................................................................6.8
HTT942D .............................................................................................................................6.8
HTT943D .............................................................................................................................6.8
HTT944D .............................................................................................................................6.8
HTT945D .............................................................................................................................6.9
HTT946I ..............................................................................................................................6.9
HTT947I ..............................................................................................................................6.9
HTT948I ..............................................................................................................................6.9
HTT949I ..............................................................................................................................6.9
HTT950I ..............................................................................................................................6.9
HTT951I ..............................................................................................................................6.9
HTT952E ...........................................................................................................................6.10
HTT953W ..........................................................................................................................6.10

xii
HTT954D ...........................................................................................................................6.10
HTT955D ...........................................................................................................................6.10
HTT956D ...........................................................................................................................6.10
HTT957D ...........................................................................................................................6.10
HTT958D ...........................................................................................................................6.11
HTT959D ...........................................................................................................................6.11
HTT960D ...........................................................................................................................6.11
HTT962D ...........................................................................................................................6.11
HTT963W ..........................................................................................................................6.11
HTT964E ...........................................................................................................................6.11
HTT965E ...........................................................................................................................6.12
HTT966W ..........................................................................................................................6.12
HTT967E ...........................................................................................................................6.12
HTT968D ...........................................................................................................................6.12
HTT969D ...........................................................................................................................6.12
HTT970D ...........................................................................................................................6.12
7 IPA Series Messages ............................................................................................ 7.1

IPA101D ..............................................................................................................................7.1
IPA117E ...............................................................................................................................7.1
IPA200I ................................................................................................................................7.1
IPA302D ..............................................................................................................................7.1
IPA303D ..............................................................................................................................7.2
IPA305D ..............................................................................................................................7.2
IPA401D ..............................................................................................................................7.2
IPA402D ..............................................................................................................................7.2
IPA403D ..............................................................................................................................7.2
IPA404I ................................................................................................................................7.2
IPA405D ..............................................................................................................................7.2
IPA406D ..............................................................................................................................7.2
IPA407I ................................................................................................................................7.2
IPA408I ................................................................................................................................7.3
IPA409D ..............................................................................................................................7.3
IPA410W .............................................................................................................................7.3
IPA411I ................................................................................................................................7.3
IPA412D ..............................................................................................................................7.3
IPA413I ................................................................................................................................7.3
IPA414D ..............................................................................................................................7.3
IPA415D ..............................................................................................................................7.4
IPA416W .............................................................................................................................7.4
IPA501D ..............................................................................................................................7.4
IPA603E ...............................................................................................................................7.4
IPA604E ...............................................................................................................................7.4
IPA605E ...............................................................................................................................7.5
IPA606I ................................................................................................................................7.5
IPA607E ...............................................................................................................................7.5

xiii
IPA608D ..............................................................................................................................7.5
IPA609I ................................................................................................................................7.5
IPA610I ................................................................................................................................7.6
IPA611D ..............................................................................................................................7.6
IPA612I ................................................................................................................................7.6
IPA613W .............................................................................................................................7.6
IPA614W .............................................................................................................................7.6
IPA615W .............................................................................................................................7.7
IPA616I ................................................................................................................................7.7
IPA617I ................................................................................................................................7.7
IPA618W .............................................................................................................................7.7
IPA619W .............................................................................................................................7.7
IPA620I ................................................................................................................................7.7
IPA621W .............................................................................................................................7.8
IPA622E ...............................................................................................................................7.8
IPA623I ................................................................................................................................7.8
IPA624E ...............................................................................................................................7.8
IPA625E ...............................................................................................................................7.9
IPA626D ..............................................................................................................................7.9
IPA627D ..............................................................................................................................7.9
IPA628D ..............................................................................................................................7.9
IPA629I ................................................................................................................................7.9
IPA631D ..............................................................................................................................7.9
IPA632D ..............................................................................................................................7.9
IPA650E .............................................................................................................................7.10
IPA651E .............................................................................................................................7.10
IPA652E .............................................................................................................................7.10
IPA701D ............................................................................................................................7.10
IPA702I ..............................................................................................................................7.10
8 IPC Series Messages ............................................................................................ 8.1

IPC102D ..............................................................................................................................8.1
IPC107D ..............................................................................................................................8.1
IPC108I ................................................................................................................................8.1
IPC109D ..............................................................................................................................8.2
IPC110D ..............................................................................................................................8.2
9 IPD Series Messages ............................................................................................ 9.1

IPD100I ................................................................................................................................9.1
IPD101I ................................................................................................................................9.1
IPD102I ................................................................................................................................9.1
IPD103I ................................................................................................................................9.1
IPD104I ................................................................................................................................9.2
IPD106I ................................................................................................................................9.2
IPD107I ................................................................................................................................9.2

xiv
IPD108I ................................................................................................................................9.2
IPD109I ................................................................................................................................9.2
IPD110I ................................................................................................................................9.2
IPD111I ................................................................................................................................9.3
IPD112I ................................................................................................................................9.3
IPD113I ................................................................................................................................9.3
IPD114I ................................................................................................................................9.3
IPD115I ................................................................................................................................9.4
10 IPF Series Messages .......................................................................................... 10.1

IPF100I ..............................................................................................................................10.1
IPF101W ............................................................................................................................10.1
IPF102E .............................................................................................................................10.1
IPF103E .............................................................................................................................10.1
IPF104E .............................................................................................................................10.2
IPF105E .............................................................................................................................10.2
IPF106E .............................................................................................................................10.2
IPF107D .............................................................................................................................10.2
IPF108E .............................................................................................................................10.2
IPF109E .............................................................................................................................10.2
IPF110E .............................................................................................................................10.3
IPF122I ..............................................................................................................................10.3
IPF123I ..............................................................................................................................10.3
IPF124I ..............................................................................................................................10.3
IPF125E .............................................................................................................................10.3
IPF126I ..............................................................................................................................10.3
IPF127D .............................................................................................................................10.3
IPF152I ..............................................................................................................................10.4
IPF153I ..............................................................................................................................10.4
IPF154E .............................................................................................................................10.4
IPF155E .............................................................................................................................10.4
IPF156E .............................................................................................................................10.4
IPF157E .............................................................................................................................10.4
IPF158I ..............................................................................................................................10.4
IPF202E .............................................................................................................................10.4
IPF203E .............................................................................................................................10.5
IPF204E .............................................................................................................................10.5
IPF205E .............................................................................................................................10.5
IPF207I ..............................................................................................................................10.5
IPF212E .............................................................................................................................10.5
IPF213E .............................................................................................................................10.5
IPF214E .............................................................................................................................10.6
IPF302E .............................................................................................................................10.6
IPF306W ............................................................................................................................10.6
IPF307I ..............................................................................................................................10.6
IPF308E .............................................................................................................................10.6

xv
IPF309I ..............................................................................................................................10.6
IPF352E .............................................................................................................................10.7
IPF355E .............................................................................................................................10.7
IPF356E .............................................................................................................................10.7
IPF357E .............................................................................................................................10.7
IPF358E .............................................................................................................................10.7
IPF361E .............................................................................................................................10.7
IPF362D .............................................................................................................................10.8
IPF363D .............................................................................................................................10.8
IPF364D .............................................................................................................................10.8
IPF366E .............................................................................................................................10.8
IPF367E .............................................................................................................................10.8
IPF402D .............................................................................................................................10.8
IPF403W ............................................................................................................................10.9
IPF404E .............................................................................................................................10.9
IPF405W ............................................................................................................................10.9
IPF410E .............................................................................................................................10.9
IPF452I ..............................................................................................................................10.9
IPF453E ...........................................................................................................................10.10
IPF454E ...........................................................................................................................10.10
IPF455W ..........................................................................................................................10.10
IPF456E ...........................................................................................................................10.10
IPF457E ...........................................................................................................................10.10
IPF458E ...........................................................................................................................10.10
IPF459E ...........................................................................................................................10.11
IPF501I ............................................................................................................................10.11
IPF504E ...........................................................................................................................10.11
IPF505E ...........................................................................................................................10.11
IPF506E ...........................................................................................................................10.11
IPF507E ...........................................................................................................................10.11
IPF508E ...........................................................................................................................10.11
IPF509E ...........................................................................................................................10.12
IPF510E ...........................................................................................................................10.12
IPF511E ...........................................................................................................................10.12
IPF512E ...........................................................................................................................10.12
IPF513E ...........................................................................................................................10.12
IPF516I ............................................................................................................................10.12
IPF517E ...........................................................................................................................10.12
IPF518E ...........................................................................................................................10.13
IPF520E ...........................................................................................................................10.13
IPF521I ............................................................................................................................10.13
IPF522E ...........................................................................................................................10.13
IPF523E ...........................................................................................................................10.13
IPF524E ...........................................................................................................................10.13
IPF526E ...........................................................................................................................10.13
IPF527E ...........................................................................................................................10.14

xvi
IPF528E ...........................................................................................................................10.14
IPF529E ...........................................................................................................................10.14
IPF530D ...........................................................................................................................10.14
IPF531I ............................................................................................................................10.14
IPF532E ...........................................................................................................................10.14
IPF533E ...........................................................................................................................10.15
IPF536E ...........................................................................................................................10.15
IPF537W ..........................................................................................................................10.15
IPF602E ...........................................................................................................................10.15
IPF603W ..........................................................................................................................10.15
IPF604E ...........................................................................................................................10.15
IPF605E ...........................................................................................................................10.16
IPF701W ..........................................................................................................................10.16
IPF702D ...........................................................................................................................10.16
IPF703E ...........................................................................................................................10.16
IPF704D ...........................................................................................................................10.17
IPF705E ...........................................................................................................................10.17
IPF706W ..........................................................................................................................10.17
IPF707W ..........................................................................................................................10.17
IPF708W ..........................................................................................................................10.17
IPF709W ..........................................................................................................................10.18
IPF720E ...........................................................................................................................10.18
IPF721E ...........................................................................................................................10.18
IPF722W ..........................................................................................................................10.18
IPF723E ...........................................................................................................................10.18
IPF752E ...........................................................................................................................10.19
IPF753E ...........................................................................................................................10.19
IPF754D ...........................................................................................................................10.19
IPF755E ...........................................................................................................................10.19
IPF756E ...........................................................................................................................10.19
IPF802E ...........................................................................................................................10.20
IPF803E ...........................................................................................................................10.20
IPF804E ...........................................................................................................................10.20
IPF806D ...........................................................................................................................10.20
IPF807D ...........................................................................................................................10.20
IPF808D ...........................................................................................................................10.20
IPF809D ...........................................................................................................................10.21
IPF810W ..........................................................................................................................10.21
IPF811W ..........................................................................................................................10.21
IPF813E ...........................................................................................................................10.21
IPF814D ...........................................................................................................................10.21
IPF815D ...........................................................................................................................10.22
IPF816D ...........................................................................................................................10.22
IPF817D ...........................................................................................................................10.22
IPF820D ...........................................................................................................................10.22
IPF822I ............................................................................................................................10.22

xvii
IPF823E ...........................................................................................................................10.22
IPF824E ...........................................................................................................................10.23
IPF827E ...........................................................................................................................10.23
IPF828W ..........................................................................................................................10.23
IPF829W ..........................................................................................................................10.23
IPF830W ..........................................................................................................................10.23
IPF831W ..........................................................................................................................10.24
IPF833D ...........................................................................................................................10.24
IPF839E ...........................................................................................................................10.24
IPF841E ...........................................................................................................................10.24
IPF843E ...........................................................................................................................10.24
IPF845E ...........................................................................................................................10.25
IPF846E ...........................................................................................................................10.25
IPF901W ..........................................................................................................................10.25
IPF902W ..........................................................................................................................10.25
IPF903E ...........................................................................................................................10.25
IPF904E ...........................................................................................................................10.26
IPF905I ............................................................................................................................10.26
IPF906E ...........................................................................................................................10.26
IPF907W ..........................................................................................................................10.26
IPF908W ..........................................................................................................................10.26
IPF912W ..........................................................................................................................10.27
11 IPI Series Messages ........................................................................................... 11.1

IPI100I ...............................................................................................................................11.1
IPI101I ...............................................................................................................................11.1
IPI103D ..............................................................................................................................11.1
IPI105D ..............................................................................................................................11.2
IPI106I ...............................................................................................................................11.2
IPI107I ...............................................................................................................................11.2
IPI108I ...............................................................................................................................11.2
IPI109E ..............................................................................................................................11.3
IPI110I ...............................................................................................................................11.3
IPI120D ..............................................................................................................................11.3
IPI302D ..............................................................................................................................11.3
IPI303D ..............................................................................................................................11.4
IPI402D ..............................................................................................................................11.4
IPI403D ..............................................................................................................................11.4
IPI502D ..............................................................................................................................11.4
IPI504W .............................................................................................................................11.4
IPI505W .............................................................................................................................11.5
IPI506I ...............................................................................................................................11.5
IPI507I ...............................................................................................................................11.5
IPI508I ...............................................................................................................................11.6
IPI514D ..............................................................................................................................11.6
IPI515I ...............................................................................................................................11.6

xviii
IPI516I ...............................................................................................................................11.6
IPI517I ...............................................................................................................................11.7
IPI602D ..............................................................................................................................11.7
IPI702D ..............................................................................................................................11.7
IPI703D ..............................................................................................................................11.7
IPI803W .............................................................................................................................11.7
IPI804D ..............................................................................................................................11.8
12 IPL Series Messages .......................................................................................... 12.1

IPL121D .............................................................................................................................12.1
IPL124E .............................................................................................................................12.1
IPL125E .............................................................................................................................12.1
IPL126E .............................................................................................................................12.1
IPL127E .............................................................................................................................12.1
IPL128E .............................................................................................................................12.2
IPL130I ..............................................................................................................................12.2
IPL241D .............................................................................................................................12.2
IPL242E .............................................................................................................................12.2
IPL246D .............................................................................................................................12.2
IPL249E .............................................................................................................................12.2
IPL250E .............................................................................................................................12.3
IPL254E .............................................................................................................................12.3
IPL255E .............................................................................................................................12.3
IPL256E .............................................................................................................................12.3
IPL258I ..............................................................................................................................12.3
IPL279W ............................................................................................................................12.3
IPL280E .............................................................................................................................12.4
IPL281E .............................................................................................................................12.4
IPL282E .............................................................................................................................12.4
IPL283E .............................................................................................................................12.4
IPL284E .............................................................................................................................12.4
IPL285W ............................................................................................................................12.4
IPL286W ............................................................................................................................12.5
IPL287W ............................................................................................................................12.5
IPL288W ............................................................................................................................12.5
IPL289E .............................................................................................................................12.5
IPL290W ............................................................................................................................12.5
IPL291W ............................................................................................................................12.5
IPL292W ............................................................................................................................12.6
IPL293W ............................................................................................................................12.6
IPL294I ..............................................................................................................................12.6
IPL295D .............................................................................................................................12.6
IPL296W ............................................................................................................................12.6
IPL297W ............................................................................................................................12.6
IPL298W ............................................................................................................................12.7
IPL299W ............................................................................................................................12.7

xix
IPL300W ............................................................................................................................12.7
IPL301W ............................................................................................................................12.7
IPL302W ............................................................................................................................12.7
IPL307W ............................................................................................................................12.7
IPL308W ............................................................................................................................12.7
IPL309W ............................................................................................................................12.8
IPL310W ............................................................................................................................12.8
IPL311I ..............................................................................................................................12.8
IPL312I ..............................................................................................................................12.8
IPL313I ..............................................................................................................................12.8
IPL314I ..............................................................................................................................12.8
IPL315I ..............................................................................................................................12.8
IPL316I ..............................................................................................................................12.9
IPL317I ..............................................................................................................................12.9
IPL318I ..............................................................................................................................12.9
IPL319I ..............................................................................................................................12.9
IPL381D .............................................................................................................................12.9
IPL382E .............................................................................................................................12.9
IPL384E .............................................................................................................................12.9
IPL388E ...........................................................................................................................12.10
IPL391E ...........................................................................................................................12.10
IPL392E ...........................................................................................................................12.10
IPL395E ...........................................................................................................................12.10
IPL398E ...........................................................................................................................12.10
IPL399E ...........................................................................................................................12.10
IPL402D ...........................................................................................................................12.11
IPL463I ............................................................................................................................12.11
IPL465I ............................................................................................................................12.11
IPL467I ............................................................................................................................12.11
IPL469E ...........................................................................................................................12.12
IPL470D ...........................................................................................................................12.12
IPL472I ............................................................................................................................12.12
IPL473I ............................................................................................................................12.12
IPL474I ............................................................................................................................12.13
IPL491I ............................................................................................................................12.13
IPL602D ...........................................................................................................................12.13
IPL604E ...........................................................................................................................12.13
IPL605E ...........................................................................................................................12.13
IPL606E ...........................................................................................................................12.14
IPL607E ...........................................................................................................................12.14
IPL609E ...........................................................................................................................12.14
IPL610E ...........................................................................................................................12.14
IPL611E ...........................................................................................................................12.14
IPL612E ...........................................................................................................................12.15
IPL613I ............................................................................................................................12.15
IPL614I ............................................................................................................................12.15

xx
IPL615I ............................................................................................................................12.15
13 IPN Series Messages .......................................................................................... 13.1

IPN100I ..............................................................................................................................13.1
IPN101I ..............................................................................................................................13.1
IPN102I ..............................................................................................................................13.1
IPN103E .............................................................................................................................13.1
IPN104E .............................................................................................................................13.2
IPN105E .............................................................................................................................13.2
IPN106I ..............................................................................................................................13.2
IPN107E .............................................................................................................................13.2
IPN108I ..............................................................................................................................13.2
IPN109I ..............................................................................................................................13.2
IPN110E .............................................................................................................................13.3
IPN111I ..............................................................................................................................13.3
IPN112E .............................................................................................................................13.3
IPN113E .............................................................................................................................13.3
IPN114E .............................................................................................................................13.3
IPN115I ..............................................................................................................................13.4
IPN116E .............................................................................................................................13.4
IPN117E .............................................................................................................................13.4
IPN118E .............................................................................................................................13.4
IPN119E .............................................................................................................................13.4
IPN120E .............................................................................................................................13.4
IPN121E .............................................................................................................................13.5
IPN122E .............................................................................................................................13.5
IPN123D ............................................................................................................................13.5
IPN124W ...........................................................................................................................13.5
IPN125I ..............................................................................................................................13.5
IPN126E .............................................................................................................................13.6
IPN127I ..............................................................................................................................13.6
IPN128E .............................................................................................................................13.6
IPN129E .............................................................................................................................13.6
IPN130I ..............................................................................................................................13.6
IPN131I ..............................................................................................................................13.6
IPN132I ..............................................................................................................................13.7
IPN134I ..............................................................................................................................13.7
IPN135I ..............................................................................................................................13.7
IPN136W ...........................................................................................................................13.7
IPN137E .............................................................................................................................13.7
IPN138I ..............................................................................................................................13.7
IPN139I ..............................................................................................................................13.7
IPN140E .............................................................................................................................13.8
IPN141E .............................................................................................................................13.8
IPN142E .............................................................................................................................13.8
IPN143E .............................................................................................................................13.8

xxi
IPN144E .............................................................................................................................13.8
IPN145E .............................................................................................................................13.9
IPN146I ..............................................................................................................................13.9
IPN147I ..............................................................................................................................13.9
IPN148E .............................................................................................................................13.9
IPN149E .............................................................................................................................13.9
IPN150E ...........................................................................................................................13.10
IPN151E ...........................................................................................................................13.10
IPN152D ..........................................................................................................................13.10
IPN154E ...........................................................................................................................13.10
IPN155W .........................................................................................................................13.10
IPN157E ...........................................................................................................................13.11
IPN158E ...........................................................................................................................13.11
IPN159E ...........................................................................................................................13.11
IPN161W .........................................................................................................................13.11
IPN162E ...........................................................................................................................13.12
IPN163I ............................................................................................................................13.12
IPN164E ...........................................................................................................................13.12
IPN165E ...........................................................................................................................13.12
IPN166E ...........................................................................................................................13.12
IPN167E ...........................................................................................................................13.12
IPN168E ...........................................................................................................................13.13
IPN169E ...........................................................................................................................13.13
IPN170E ...........................................................................................................................13.13
IPN171E ...........................................................................................................................13.13
IPN172I ............................................................................................................................13.13
IPN173I ............................................................................................................................13.13
IPN177I ............................................................................................................................13.14
IPN178E ...........................................................................................................................13.14
IPN180W .........................................................................................................................13.14
IPN182W .........................................................................................................................13.14
IPN183E ...........................................................................................................................13.14
IPN184I ............................................................................................................................13.14
IPN185E ...........................................................................................................................13.15
IPN188I ............................................................................................................................13.15
IPN189W .........................................................................................................................13.15
IPN190E ...........................................................................................................................13.15
IPN191E ...........................................................................................................................13.15
IPN192E ...........................................................................................................................13.16
IPN193E ...........................................................................................................................13.16
IPN195E ...........................................................................................................................13.16
IPN196E ...........................................................................................................................13.17
IPN198E ...........................................................................................................................13.17
IPN199W .........................................................................................................................13.17
IPN200E ...........................................................................................................................13.17
IPN202I ............................................................................................................................13.18

xxii
IPN203W .........................................................................................................................13.18
IPN204W .........................................................................................................................13.18
IPN205A ..........................................................................................................................13.18
IPN206I ............................................................................................................................13.18
IPN207I ............................................................................................................................13.18
IPN208I ............................................................................................................................13.19
IPN209I ............................................................................................................................13.19
IPN210I ............................................................................................................................13.19
IPN211A ..........................................................................................................................13.19
IPN212W .........................................................................................................................13.19
IPN213I ............................................................................................................................13.20
IPN214I ............................................................................................................................13.20
IPN215I ............................................................................................................................13.20
IPN216I ............................................................................................................................13.20
IPN217E ...........................................................................................................................13.20
IPN219I ............................................................................................................................13.21
IPN222E ...........................................................................................................................13.21
IPN223A ..........................................................................................................................13.21
IPN224I ............................................................................................................................13.22
IPN225I ............................................................................................................................13.22
IPN226I ............................................................................................................................13.22
IPN227E ...........................................................................................................................13.22
IPN228I ............................................................................................................................13.22
IPN229I ............................................................................................................................13.22
IPN230I ............................................................................................................................13.23
IPN233I ............................................................................................................................13.23
IPN237I ............................................................................................................................13.23
IPN239W .........................................................................................................................13.23
IPN244W .........................................................................................................................13.23
IPN246I ............................................................................................................................13.23
IPN247W .........................................................................................................................13.23
IPN248I ............................................................................................................................13.24
IPN249I ............................................................................................................................13.24
IPN251I ............................................................................................................................13.24
IPN252I ............................................................................................................................13.24
IPN253I ............................................................................................................................13.24
IPN254I ............................................................................................................................13.24
IPN255I ............................................................................................................................13.25
IPN257I ............................................................................................................................13.25
IPN258I ............................................................................................................................13.25
IPN259I ............................................................................................................................13.25
IPN260I ............................................................................................................................13.25
IPN262E ...........................................................................................................................13.25
IPN263I ............................................................................................................................13.25
IPN264I ............................................................................................................................13.26
IPN267E ...........................................................................................................................13.26

xxiii
IPN271I ............................................................................................................................13.26
IPN272W .........................................................................................................................13.26
IPN273I ............................................................................................................................13.26
IPN274I ............................................................................................................................13.26
IPN275W .........................................................................................................................13.26
IPN276D ..........................................................................................................................13.27
IPN277W .........................................................................................................................13.27
IPN278E ...........................................................................................................................13.27
IPN279I ............................................................................................................................13.27
IPN280I ............................................................................................................................13.27
IPN281I ............................................................................................................................13.28
IPN282I ............................................................................................................................13.28
IPN283I ............................................................................................................................13.28
IPN284I ............................................................................................................................13.28
IPN285I ............................................................................................................................13.28
IPN286I ............................................................................................................................13.29
IPN287I ............................................................................................................................13.29
IPN288I ............................................................................................................................13.29
IPN289I ............................................................................................................................13.29
IPN290I ............................................................................................................................13.29
IPN291I ............................................................................................................................13.29
IPN292I ............................................................................................................................13.30
IPN293I ............................................................................................................................13.30
IPN294I ............................................................................................................................13.30
IPN295I ............................................................................................................................13.30
IPN296I ............................................................................................................................13.31
IPN297I ............................................................................................................................13.31
IPN300A ..........................................................................................................................13.31
IPN301E ...........................................................................................................................13.31
IPN302E ...........................................................................................................................13.31
IPN303E ...........................................................................................................................13.32
IPN304E ...........................................................................................................................13.32
IPN305E ...........................................................................................................................13.32
IPN306E ...........................................................................................................................13.32
IPN307E ...........................................................................................................................13.32
IPN308E ...........................................................................................................................13.33
IPN309E ...........................................................................................................................13.33
IPN310E ...........................................................................................................................13.33
IPN311E ...........................................................................................................................13.33
IPN312E ...........................................................................................................................13.33
IPN313E ...........................................................................................................................13.34
IPN314E ...........................................................................................................................13.34
IPN315E ...........................................................................................................................13.34
IPN316E ...........................................................................................................................13.34
IPN317E ...........................................................................................................................13.34
IPN318E ...........................................................................................................................13.35

xxiv
IPN319E ...........................................................................................................................13.35
IPN320E ...........................................................................................................................13.35
IPN321E ...........................................................................................................................13.35
IPN322E ...........................................................................................................................13.35
IPN323E ...........................................................................................................................13.36
IPN324E ...........................................................................................................................13.36
IPN325E ...........................................................................................................................13.36
IPN326E ...........................................................................................................................13.36
IPN327E ...........................................................................................................................13.36
IPN328E ...........................................................................................................................13.37
IPN329E ...........................................................................................................................13.37
IPN330E ...........................................................................................................................13.37
IPN331E ...........................................................................................................................13.37
IPN332E ...........................................................................................................................13.37
IPN333E ...........................................................................................................................13.37
IPN334E ...........................................................................................................................13.38
IPN348E ...........................................................................................................................13.38
IPN349E ...........................................................................................................................13.38
IPN350I ............................................................................................................................13.38
IPN351I ............................................................................................................................13.38
IPN353E ...........................................................................................................................13.38
IPN355I ............................................................................................................................13.39
IPN357I ............................................................................................................................13.39
IPN358I ............................................................................................................................13.39
IPN361W .........................................................................................................................13.39
IPN362I ............................................................................................................................13.39
IPN363I ............................................................................................................................13.39
IPN364I ............................................................................................................................13.39
IPN365I ............................................................................................................................13.40
IPN366I ............................................................................................................................13.40
IPN367I ............................................................................................................................13.40
IPN368I ............................................................................................................................13.40
IPN369I ............................................................................................................................13.40
IPN374I ............................................................................................................................13.40
IPN379I ............................................................................................................................13.41
IPN380I ............................................................................................................................13.41
IPN388W .........................................................................................................................13.41
IPN389E ...........................................................................................................................13.41
IPN391I ............................................................................................................................13.42
IPN394I ............................................................................................................................13.42
IPN395I ............................................................................................................................13.42
IPN396I ............................................................................................................................13.42
IPN397I ............................................................................................................................13.42
IPN398I ............................................................................................................................13.42
IPN399E ...........................................................................................................................13.43
IPN400I ............................................................................................................................13.43

xxv
IPN401I ............................................................................................................................13.43
IPN402I ............................................................................................................................13.43
IPN403I ............................................................................................................................13.44
IPN405I ............................................................................................................................13.44
IPN406E ...........................................................................................................................13.44
IPN409I ............................................................................................................................13.44
IPN410I ............................................................................................................................13.44
IPN426I ............................................................................................................................13.45
IPN427I ............................................................................................................................13.45
IPN428I ............................................................................................................................13.45
IPN429I ............................................................................................................................13.45
IPN430I ............................................................................................................................13.45
IPN431I ............................................................................................................................13.45
IPN432I ............................................................................................................................13.45
IPN433I ............................................................................................................................13.46
IPN435I ............................................................................................................................13.46
IPN437I ............................................................................................................................13.46
IPN438I ............................................................................................................................13.46
IPN439I ............................................................................................................................13.46
IPN440I ............................................................................................................................13.46
IPN441I ............................................................................................................................13.46
IPN442I ............................................................................................................................13.46
IPN443I ............................................................................................................................13.47
IPN444I ............................................................................................................................13.47
IPN445I ............................................................................................................................13.47
IPN446I ............................................................................................................................13.47
IPN448I ............................................................................................................................13.47
IPN449I ............................................................................................................................13.47
IPN450I ............................................................................................................................13.47
IPN451I ............................................................................................................................13.48
IPN452I ............................................................................................................................13.48
IPN453I ............................................................................................................................13.48
IPN454I ............................................................................................................................13.48
IPN455 .............................................................................................................................13.48
IPN456I ............................................................................................................................13.49
IPN458I ............................................................................................................................13.49
IPN459I ............................................................................................................................13.49
IPN464I ............................................................................................................................13.49
IPN465I ............................................................................................................................13.49
IPN466I ............................................................................................................................13.49
IPN468I ............................................................................................................................13.49
IPN469I ............................................................................................................................13.50
IPN470I ............................................................................................................................13.50
IPN471I ............................................................................................................................13.50
IPN472I ............................................................................................................................13.50
IPN473I ............................................................................................................................13.50

xxvi
IPN474I ............................................................................................................................13.50
IPN475I ............................................................................................................................13.51
IPN476I ............................................................................................................................13.51
IPN477I ............................................................................................................................13.51
IPN478I ............................................................................................................................13.51
IPN479I ............................................................................................................................13.51
IPN480I ............................................................................................................................13.51
IPN482I ............................................................................................................................13.51
IPN486E ...........................................................................................................................13.52
IPN489D ..........................................................................................................................13.52
IPN490W .........................................................................................................................13.52
IPN491I ............................................................................................................................13.52
IPN497I ............................................................................................................................13.52
IPN498D ..........................................................................................................................13.52
IPN499I ............................................................................................................................13.53
IPN500W .........................................................................................................................13.53
IPN503I ............................................................................................................................13.53
IPN504I ............................................................................................................................13.53
IPN506I ............................................................................................................................13.53
IPN507I ............................................................................................................................13.53
IPN509I ............................................................................................................................13.53
IPN510I ............................................................................................................................13.54
IPN512I ............................................................................................................................13.54
IPN514I ............................................................................................................................13.54
IPN516I ............................................................................................................................13.54
IPN518I ............................................................................................................................13.54
IPN519I ............................................................................................................................13.54
IPN521I ............................................................................................................................13.54
IPN522I ............................................................................................................................13.54
IPN524I ............................................................................................................................13.55
IPN525I ............................................................................................................................13.55
IPN528E ...........................................................................................................................13.55
IPN529I ............................................................................................................................13.55
IPN531I ............................................................................................................................13.55
IPN532I ............................................................................................................................13.55
IPN534I ............................................................................................................................13.55
IPN535E ...........................................................................................................................13.55
IPN536I ............................................................................................................................13.56
IPN537I ............................................................................................................................13.56
IPN538E ...........................................................................................................................13.56
IPN540W .........................................................................................................................13.56
IPN541 .............................................................................................................................13.57
IPN542I ............................................................................................................................13.57
IPN545I ............................................................................................................................13.57
IPN546I ............................................................................................................................13.57
IPN547W .........................................................................................................................13.57

xxvii
IPN548D ..........................................................................................................................13.58
IPN549E ...........................................................................................................................13.58
IPN552E ...........................................................................................................................13.58
IPN553E ...........................................................................................................................13.58
IPN554E ...........................................................................................................................13.58
IPN555E ...........................................................................................................................13.58
IPN556E ...........................................................................................................................13.59
IPN557E ...........................................................................................................................13.59
IPN558E ...........................................................................................................................13.59
IPN559E ...........................................................................................................................13.59
IPN560E ...........................................................................................................................13.59
IPN561E ...........................................................................................................................13.59
IPN562E ...........................................................................................................................13.59
IPN563E ...........................................................................................................................13.59
IPN564 .............................................................................................................................13.60
IPN565E ...........................................................................................................................13.60
IPN566E ...........................................................................................................................13.60
IPN567E ...........................................................................................................................13.60
IPN571I ............................................................................................................................13.60
IPN572I ............................................................................................................................13.60
IPN575I ............................................................................................................................13.60
IPN577I ............................................................................................................................13.60
IPN578E ...........................................................................................................................13.61
IPN579I ............................................................................................................................13.61
IPN581I ............................................................................................................................13.61
IPN582I ............................................................................................................................13.61
IPN586W .........................................................................................................................13.61
IPN587I ............................................................................................................................13.61
IPN591I ............................................................................................................................13.61
IPN592E ...........................................................................................................................13.62
IPN594W .........................................................................................................................13.62
IPN595I ............................................................................................................................13.62
IPN596I ............................................................................................................................13.62
IPN597I ............................................................................................................................13.63
IPN599E ...........................................................................................................................13.63
IPN600I ............................................................................................................................13.63
IPN601I ............................................................................................................................13.63
IPN602I ............................................................................................................................13.63
IPN603E ...........................................................................................................................13.63
IPN604W .........................................................................................................................13.64
IPN605I ............................................................................................................................13.64
IPN606I ............................................................................................................................13.64
IPN608E ...........................................................................................................................13.64
IPN609E ...........................................................................................................................13.64
IPN610E ...........................................................................................................................13.64
IPN611E ...........................................................................................................................13.65

xxviii
IPN612I ............................................................................................................................13.65
IPN613I ............................................................................................................................13.65
IPN614I ............................................................................................................................13.65
IPN615I ............................................................................................................................13.65
IPN616E ...........................................................................................................................13.65
IPN617I ............................................................................................................................13.65
IPN618I ............................................................................................................................13.66
IPN619I ............................................................................................................................13.66
IPN622W .........................................................................................................................13.66
IPN624I ............................................................................................................................13.66
IPN625E ...........................................................................................................................13.66
IPN627I ............................................................................................................................13.66
IPN631I ............................................................................................................................13.66
IPN632E ...........................................................................................................................13.67
IPN633E ...........................................................................................................................13.67
IPN634E ...........................................................................................................................13.67
IPN635I ............................................................................................................................13.67
IPN636I ............................................................................................................................13.67
IPN637 .............................................................................................................................13.68
IPN638E ...........................................................................................................................13.68
IPN639E ...........................................................................................................................13.68
IPN640I ............................................................................................................................13.68
IPN641E ...........................................................................................................................13.68
IPN642E ...........................................................................................................................13.69
IPN643E ...........................................................................................................................13.69
IPN644E ...........................................................................................................................13.69
IPN645E ...........................................................................................................................13.69
IPN646E ...........................................................................................................................13.69
IPN647I ............................................................................................................................13.70
IPN648I ............................................................................................................................13.70
IPN649E ...........................................................................................................................13.70
IPN651I ............................................................................................................................13.70
IPN652I ............................................................................................................................13.70
IPN654I ............................................................................................................................13.70
IPN655I ............................................................................................................................13.70
IPN656I ............................................................................................................................13.70
IPN657I ............................................................................................................................13.71
IPN658E ...........................................................................................................................13.71
IPN659E ...........................................................................................................................13.71
IPN661E ...........................................................................................................................13.71
IPN662E ...........................................................................................................................13.71
IPN663E ...........................................................................................................................13.71
IPN666E ...........................................................................................................................13.71
IPN667E ...........................................................................................................................13.72
IPN668E ...........................................................................................................................13.72
IPN669E ...........................................................................................................................13.72

xxix
IPN670E ...........................................................................................................................13.72
IPN671E ...........................................................................................................................13.72
IPN672E ...........................................................................................................................13.72
IPN673E ...........................................................................................................................13.73
IPN674E ...........................................................................................................................13.73
IPN676I ............................................................................................................................13.73
IPN677E ...........................................................................................................................13.73
IPN679I ............................................................................................................................13.73
IPN680E ...........................................................................................................................13.73
IPN681I ............................................................................................................................13.74
IPN694W .........................................................................................................................13.74
IPN700I ............................................................................................................................13.74
IPN701I ............................................................................................................................13.74
IPN702I ............................................................................................................................13.74
IPN703E ...........................................................................................................................13.74
IPN704E ...........................................................................................................................13.75
IPN705I ............................................................................................................................13.75
IPN706I ............................................................................................................................13.75
IPN707W .........................................................................................................................13.75
IPN708I ............................................................................................................................13.75
IPN710E ...........................................................................................................................13.75
IPN711I ............................................................................................................................13.76
IPN712I ............................................................................................................................13.76
IPN713E ...........................................................................................................................13.76
IPN714E ...........................................................................................................................13.76
IPN715I ............................................................................................................................13.76
IPN717E ...........................................................................................................................13.77
IPN750I ............................................................................................................................13.77
IPN751I ............................................................................................................................13.77
IPN752I ............................................................................................................................13.77
IPN754E ...........................................................................................................................13.77
IPN755I ............................................................................................................................13.78
IPN756E ...........................................................................................................................13.78
IPN757E ...........................................................................................................................13.78
IPN758W .........................................................................................................................13.79
IPN759I ............................................................................................................................13.79
IPN800I ............................................................................................................................13.79
IPN801I ............................................................................................................................13.79
IPN802E ...........................................................................................................................13.79
IPN804I ............................................................................................................................13.79
IPN805I ............................................................................................................................13.80
IPN806I ............................................................................................................................13.80
IPN807W .........................................................................................................................13.80
IPN808D ..........................................................................................................................13.80
IPN809D ..........................................................................................................................13.80
IPN810D ..........................................................................................................................13.80

xxx
IPN811D ..........................................................................................................................13.81
IPN812I ............................................................................................................................13.81
IPN813D ..........................................................................................................................13.81
IPN814I ............................................................................................................................13.82
IPN815D ..........................................................................................................................13.82
IPN816D ..........................................................................................................................13.82
IPN817D ..........................................................................................................................13.82
IPN819D ..........................................................................................................................13.82
IPN823D ..........................................................................................................................13.82
IPN824W .........................................................................................................................13.83
IPN825D ..........................................................................................................................13.83
IPN827D ..........................................................................................................................13.83
IPN828D ..........................................................................................................................13.83
IPN831W .........................................................................................................................13.83
IPN834I ............................................................................................................................13.83
IPN835I ............................................................................................................................13.84
IPN836I ............................................................................................................................13.84
IPN838I ............................................................................................................................13.84
IPN840I ............................................................................................................................13.84
IPN842I ............................................................................................................................13.84
IPN844I ............................................................................................................................13.84
IPN845D ..........................................................................................................................13.84
IPN846D ..........................................................................................................................13.85
IPN847I ............................................................................................................................13.85
IPN848D ..........................................................................................................................13.85
IPN849W .........................................................................................................................13.85
IPN850I ............................................................................................................................13.85
IPN851I ............................................................................................................................13.86
IPN852I ............................................................................................................................13.86
IPN853I ............................................................................................................................13.86
IPN854I ............................................................................................................................13.87
IPN855I ............................................................................................................................13.87
IPN858I ............................................................................................................................13.87
IPN859I ............................................................................................................................13.88
IPN860I ............................................................................................................................13.88
IPN861D ..........................................................................................................................13.88
IPN862D ..........................................................................................................................13.89
IPN863I ............................................................................................................................13.89
IPN864I ............................................................................................................................13.89
IPN865E ...........................................................................................................................13.89
IPN866E ...........................................................................................................................13.89
IPN867I ............................................................................................................................13.90
IPN868I ............................................................................................................................13.90
IPN869D ..........................................................................................................................13.90
IPN871E ...........................................................................................................................13.90
IPN872I ............................................................................................................................13.90

xxxi
IPN873D ..........................................................................................................................13.91
IPN874I ............................................................................................................................13.91
IPN875I ............................................................................................................................13.91
IPN876I ............................................................................................................................13.91
IPN877I ............................................................................................................................13.91
IPN878I ............................................................................................................................13.91
IPN879I ............................................................................................................................13.92
IPN880I ............................................................................................................................13.92
IPN881I ............................................................................................................................13.92
IPN882I ............................................................................................................................13.92
IPN883I ............................................................................................................................13.92
IPN884I ............................................................................................................................13.92
IPN885I ............................................................................................................................13.93
IPN886I ............................................................................................................................13.93
IPN887D ..........................................................................................................................13.93
IPN888I ............................................................................................................................13.93
IPN889I ............................................................................................................................13.94
IPN891D ..........................................................................................................................13.94
IPN892D ..........................................................................................................................13.94
IPN893I ............................................................................................................................13.95
IPN894I ............................................................................................................................13.95
IPN895I ............................................................................................................................13.95
IPN896I ............................................................................................................................13.95
IPN897I ............................................................................................................................13.95
IPN898I ............................................................................................................................13.96
IPN900D ..........................................................................................................................13.96
IPN901D ..........................................................................................................................13.96
IPN902E ...........................................................................................................................13.96
IPN903E ...........................................................................................................................13.96
IPN904E ...........................................................................................................................13.97
IPN905E ...........................................................................................................................13.97
IPN906E ...........................................................................................................................13.97
IPN907E ...........................................................................................................................13.98
IPN908E ...........................................................................................................................13.98
IPN909E ...........................................................................................................................13.98
IPN910E ...........................................................................................................................13.98
IPN911E ...........................................................................................................................13.98
IPN912E ...........................................................................................................................13.98
IPN913E ...........................................................................................................................13.98
IPN914E ...........................................................................................................................13.99
IPN915E ...........................................................................................................................13.99
IPN921I ..........................................................................................................................13.100
IPN922I ..........................................................................................................................13.100
IPN923E .........................................................................................................................13.100
IPN924I ..........................................................................................................................13.100
IPN925I ..........................................................................................................................13.100

xxxii
IPN926I ..........................................................................................................................13.100
IPN927I ..........................................................................................................................13.101
IPN928I ..........................................................................................................................13.101
IPN929I ..........................................................................................................................13.101
IPN930I ..........................................................................................................................13.101
IPN931E .........................................................................................................................13.101
IPN932I ..........................................................................................................................13.101
IPN936I ..........................................................................................................................13.101
IPN937I ..........................................................................................................................13.101
IPN938I ..........................................................................................................................13.101
IPN939E .........................................................................................................................13.102
IPN940E .........................................................................................................................13.102
IPN941E .........................................................................................................................13.102
IPN942E .........................................................................................................................13.102
IPN943E .........................................................................................................................13.103
IPN944E .........................................................................................................................13.103
IPN950I ..........................................................................................................................13.103
IPN951I ..........................................................................................................................13.105
IPN952I ..........................................................................................................................13.105
14 IPT Series Messages .......................................................................................... 14.1

IPT100I ..............................................................................................................................14.1
IPT101I ..............................................................................................................................14.1
IPT106D .............................................................................................................................14.1
IPT107I ..............................................................................................................................14.2
IPT109W ............................................................................................................................14.2
IPT110I ..............................................................................................................................14.2
IPT112I ..............................................................................................................................14.2
IPT203W ............................................................................................................................14.2
IPT240I ..............................................................................................................................14.3
IPT241I ..............................................................................................................................14.3
IPT242I ..............................................................................................................................14.3
IPT243I ..............................................................................................................................14.3
IPT245E .............................................................................................................................14.4
IPT246E .............................................................................................................................14.4
IPT247E .............................................................................................................................14.4
IPT248E .............................................................................................................................14.4
IPT301D .............................................................................................................................14.5
IPT302I ..............................................................................................................................14.6
IPT303D .............................................................................................................................14.6
IPT304I ..............................................................................................................................14.6
IPT317I ..............................................................................................................................14.7
IPT326D .............................................................................................................................14.7
IPT328D .............................................................................................................................14.8
IPT330I ..............................................................................................................................14.8
IPT334D .............................................................................................................................14.8

xxxiii
IPT337D .............................................................................................................................14.9
IPT338D .............................................................................................................................14.9
IPT339D .............................................................................................................................14.9
IPT340D .............................................................................................................................14.9
IPT341I ............................................................................................................................14.10
IPT342I ............................................................................................................................14.10
IPT343D ...........................................................................................................................14.10
IPT344I ............................................................................................................................14.11
IPT345I ............................................................................................................................14.11
IPT346D ...........................................................................................................................14.11
IPT347I ............................................................................................................................14.12
IPT348I ............................................................................................................................14.12
IPT349I ............................................................................................................................14.13
IPT351I ............................................................................................................................14.13
IPT352I ............................................................................................................................14.13
IPT353I ............................................................................................................................14.14
IPT354I ............................................................................................................................14.14
IPT355I ............................................................................................................................14.14
IPT356I ............................................................................................................................14.15
IPT357I ............................................................................................................................14.15
IPT359I ............................................................................................................................14.15
IPT360I ............................................................................................................................14.15
IPT361I ............................................................................................................................14.16
IPT400I ............................................................................................................................14.16
15 IPU Series Messages .......................................................................................... 15.1

IPU102D ............................................................................................................................15.1
IPU107I ..............................................................................................................................15.1
IPU108I ..............................................................................................................................15.1
IPU202D ............................................................................................................................15.1
16 IPX Series Messages .......................................................................................... 16.1

IPX109E .............................................................................................................................16.1
IPX110E .............................................................................................................................16.1
IPX111E .............................................................................................................................16.2
IPX112W ...........................................................................................................................16.2
IPX113E .............................................................................................................................16.2
IPX114W ...........................................................................................................................16.2
IPX115E .............................................................................................................................16.3
IPX200I ..............................................................................................................................16.3
IPX201I ..............................................................................................................................16.3
IPX202I ..............................................................................................................................16.3
IPX203E .............................................................................................................................16.3
IPX204W ...........................................................................................................................16.4
IPX205D ............................................................................................................................16.4

xxxiv
IPX206D ............................................................................................................................16.4
IPX207D ............................................................................................................................16.4
IPX208E .............................................................................................................................16.5
IPX209W ...........................................................................................................................16.5
IPX210W ...........................................................................................................................16.5
IPX211E .............................................................................................................................16.5
IPX400I ..............................................................................................................................16.6
IPX401I ..............................................................................................................................16.6
IPX402I ..............................................................................................................................16.6
IPX403E .............................................................................................................................16.6
IPX404W ...........................................................................................................................16.6
IPX405W ...........................................................................................................................16.6
IPX406W ...........................................................................................................................16.6
IPX407W ...........................................................................................................................16.7
IPX409I ..............................................................................................................................16.7
IPX410I ..............................................................................................................................16.7
IPX425W ...........................................................................................................................16.7
IPX426E .............................................................................................................................16.7
IPX427E .............................................................................................................................16.7
IPX500I ..............................................................................................................................16.7
IPX501I ..............................................................................................................................16.8
IPX502I ..............................................................................................................................16.8
IPX503E .............................................................................................................................16.8
IPX504E .............................................................................................................................16.8
IPX505E .............................................................................................................................16.8
IPX507E .............................................................................................................................16.9
IPX508I ..............................................................................................................................16.9
IPX509W ...........................................................................................................................16.9
IPX510I ..............................................................................................................................16.9
IPX511E .............................................................................................................................16.9
IPX512I ............................................................................................................................16.10
IPX513I ............................................................................................................................16.10
IPX514I ............................................................................................................................16.10
IPX515I ............................................................................................................................16.10
IPX516I ............................................................................................................................16.10
IPX517I ............................................................................................................................16.10
IPX518I ............................................................................................................................16.10
IPX520I ............................................................................................................................16.10
17 LPD Series Messages ........................................................................................ 17.1

LPD900I .............................................................................................................................17.1
LPD901E ...........................................................................................................................17.1
LPD902E ...........................................................................................................................17.1
LPD903I .............................................................................................................................17.1
LPD904D ...........................................................................................................................17.2
LPD905D ...........................................................................................................................17.2

xxxv
LPD906E ...........................................................................................................................17.2
LPD907D ...........................................................................................................................17.2
LPD908D ...........................................................................................................................17.2
LPD909D ...........................................................................................................................17.2
LPD910D ...........................................................................................................................17.2
LPD912E ...........................................................................................................................17.2
LPD913E ...........................................................................................................................17.3
LPD914E ...........................................................................................................................17.3
LPD915E ...........................................................................................................................17.3
LPD916E ...........................................................................................................................17.3
LPD917D ...........................................................................................................................17.3
LPD918D ...........................................................................................................................17.3
LPD919E ...........................................................................................................................17.4
LPD920E ...........................................................................................................................17.4
LPD921E ...........................................................................................................................17.4
LPD922D ...........................................................................................................................17.4
LPD923D ...........................................................................................................................17.4
LPD924D ...........................................................................................................................17.4
LPD926E ...........................................................................................................................17.5
LPD927E ...........................................................................................................................17.5
LPD928E ...........................................................................................................................17.5
LPD929E ...........................................................................................................................17.5
LPD930E ...........................................................................................................................17.5
LPD931E ...........................................................................................................................17.6
LPD932I .............................................................................................................................17.6
LPD933I .............................................................................................................................17.6
LPD934I .............................................................................................................................17.6
LPD935I .............................................................................................................................17.6
LPD936E ...........................................................................................................................17.6
LPD937E ...........................................................................................................................17.6
LPD938E ...........................................................................................................................17.7
LPD939D ...........................................................................................................................17.7
LPD940E ...........................................................................................................................17.7
LPD941D ...........................................................................................................................17.7
18 NTP Series Messages ........................................................................................ 18.1

NTP100I .............................................................................................................................18.1
NTP101E ...........................................................................................................................18.1
NTP102I .............................................................................................................................18.1
NTP103E ...........................................................................................................................18.2
NTP104E ...........................................................................................................................18.2
NTP105I .............................................................................................................................18.2
NTP106I .............................................................................................................................18.2
NTP107I .............................................................................................................................18.2
NTP108I .............................................................................................................................18.2
NTP109E ...........................................................................................................................18.3

xxxvi
19 RSA Series Messages ........................................................................................ 19.1

RSA001E ...........................................................................................................................19.1
20 SEE Series Messages ........................................................................................ 20.1

SEE100D ...........................................................................................................................20.1
SEE106W ...........................................................................................................................20.1
21 SHL Series Messages ........................................................................................ 21.1

SHL017E ...........................................................................................................................21.1
22 SOC Series Messages ........................................................................................ 22.1

SOC001E ...........................................................................................................................22.1
SOC002E ...........................................................................................................................22.1
SOC003E ...........................................................................................................................22.1
SOC004E ...........................................................................................................................22.1
SOC005E ...........................................................................................................................22.2
SOC006E ...........................................................................................................................22.2
SOC008E ...........................................................................................................................22.2
SOC009E ...........................................................................................................................22.2
SOC010E ...........................................................................................................................22.2
SOC011E ...........................................................................................................................22.2
SOC012E ...........................................................................................................................22.3
SOC013E ...........................................................................................................................22.3
SOC014E ...........................................................................................................................22.3
SOC015I ............................................................................................................................22.3
SOC016I ............................................................................................................................22.3
SOC017W ..........................................................................................................................22.3
SOC018E ...........................................................................................................................22.3
SOC020E ...........................................................................................................................22.4
SOC030E ...........................................................................................................................22.4
SOC031E ...........................................................................................................................22.4
SOC032E ...........................................................................................................................22.4
SOC033E ...........................................................................................................................22.4
SOC034E ...........................................................................................................................22.4
23 SSL Series Messages ......................................................................................... 23.1

SSL100D ............................................................................................................................23.1
SSL101D ............................................................................................................................23.1
SSL102D ............................................................................................................................23.1
SSL103D ............................................................................................................................23.1
SSL104W ...........................................................................................................................23.1
SSL106D ............................................................................................................................23.2
SSL107D ............................................................................................................................23.2
SSL108D ............................................................................................................................23.2

xxxvii
SSL109D ............................................................................................................................23.2
SSL110D ............................................................................................................................23.2
SSL111D ............................................................................................................................23.2
SSL112I .............................................................................................................................23.2
SSL113W ...........................................................................................................................23.2
SSL114I .............................................................................................................................23.3
SSL115W ...........................................................................................................................23.3
SSL116D ............................................................................................................................23.3
SSL117D ............................................................................................................................23.3
SSL118D ............................................................................................................................23.3
SSL200I .............................................................................................................................23.3
SSL201D ............................................................................................................................23.3
SSL202D ............................................................................................................................23.3
SSL203E ............................................................................................................................23.4
SSL303E ............................................................................................................................23.4
SSL400I .............................................................................................................................23.4
SSL401W ...........................................................................................................................23.4
SSL402I .............................................................................................................................23.4
24 TCP Series Messages ........................................................................................ 24.1

TCP140E ............................................................................................................................24.1
TCP700I .............................................................................................................................24.1
TCP701I .............................................................................................................................24.1
TCP702I .............................................................................................................................24.2
TCP703I .............................................................................................................................24.2
TCP704I .............................................................................................................................24.2
TCP705I .............................................................................................................................24.2
TCP706I .............................................................................................................................24.2
TCP707I .............................................................................................................................24.3
TCP708I .............................................................................................................................24.3
TCP709I .............................................................................................................................24.3
TCP710I .............................................................................................................................24.3
TCP711I .............................................................................................................................24.3
TCP712I .............................................................................................................................24.4
TCP800E ............................................................................................................................24.4
TCP801D ...........................................................................................................................24.4
TCP802E ............................................................................................................................24.5
TCP803E ............................................................................................................................24.5
TCP804E ............................................................................................................................24.5
TCP805E ............................................................................................................................24.5
TCP900I .............................................................................................................................24.5
TCP901I .............................................................................................................................24.5
TCP902D ...........................................................................................................................24.6
TCP903E ............................................................................................................................24.6
TCP904E ............................................................................................................................24.6
TCP905D ...........................................................................................................................24.6

xxxviii
TCP906E ............................................................................................................................24.6
TCP907I .............................................................................................................................24.6
TCP908I .............................................................................................................................24.6
TCP909I .............................................................................................................................24.6
TCP910D ...........................................................................................................................24.7
TCP911D ...........................................................................................................................24.7
TCP912I .............................................................................................................................24.7
TCP913I .............................................................................................................................24.7
TCP914W ..........................................................................................................................24.7
TCP915I .............................................................................................................................24.7
TCP916W ..........................................................................................................................24.8
TCP917W ..........................................................................................................................24.8
25 TEL Series Messages ......................................................................................... 25.1

TEL900I .............................................................................................................................25.1
TEL902D ...........................................................................................................................25.1
TEL907D ...........................................................................................................................25.1
TEL910D ...........................................................................................................................25.2
TEL912E ............................................................................................................................25.2
TEL913I .............................................................................................................................25.2
TEL916E ............................................................................................................................25.3
TEL917I .............................................................................................................................25.3
TEL918I .............................................................................................................................25.3
TEL919I .............................................................................................................................25.3
TEL920I .............................................................................................................................25.3
TEL921I .............................................................................................................................25.3
TEL922I .............................................................................................................................25.4
TEL923I .............................................................................................................................25.4
TEL924I .............................................................................................................................25.4
TEL925I .............................................................................................................................25.4
TEL927D/I .........................................................................................................................25.4
TEL936I .............................................................................................................................25.6
TEL938I .............................................................................................................................25.6
TEL942E ............................................................................................................................25.6
TEL943E ............................................................................................................................25.6
TEL952E ............................................................................................................................25.6
TEL953E ............................................................................................................................25.7
TEL954E ............................................................................................................................25.7
TEL955E ............................................................................................................................25.7
TEL956E ............................................................................................................................25.7
TEL957E ............................................................................................................................25.7
TEL960E ............................................................................................................................25.7
TEL961E ............................................................................................................................25.8
TEL962E ............................................................................................................................25.8
TEL963E ............................................................................................................................25.8
TEL965E ............................................................................................................................25.8

xxxix
TEL966E ............................................................................................................................25.9
TEL967E ............................................................................................................................25.9
TEL968E ............................................................................................................................25.9
TEL969E ............................................................................................................................25.9
TEL970E ..........................................................................................................................25.10
TEL980E ..........................................................................................................................25.10
TEL981W ........................................................................................................................25.10
TEL982W ........................................................................................................................25.10
TEL983W ........................................................................................................................25.11
TEL987I ...........................................................................................................................25.11
TEL999D/I .......................................................................................................................25.11
26 TLS Series Messages ......................................................................................... 26.1

TLS900I .............................................................................................................................26.1
TLS901I .............................................................................................................................26.1
TLS903I .............................................................................................................................26.1
TLS904D ...........................................................................................................................26.1
TLS907I .............................................................................................................................26.1
TLS908I .............................................................................................................................26.1

xl
1
BSD Series Messages
BSD001I phase version addr1
(Info) This message is issued the first time an application makes a call to the $SOCKLST
program. It contains the phase name, version, assembly date and time, and the load address of
the phase.
(Info) This message is issued during a startup call request to the $SOCKLST program. It
contains the name of the phase, version, assembly date and time, and the load address of the
phase.
BSD003I xxx R15=yyy RETCD=yyy ERRNO=yyy
(Info) This message is issued during a function done request from older ipnrxxx object code.
These have been replaced by the IPNRBSDC phase.
BSD004D $SOCKOPT=00524300 BSDCFG1=90 BSDCFG2=A0 SYSID=00
(Diagnose) This message is issued the once by $SOCKLST to display the $SOCKOPT options
that are being used. The SOCKOPT.A macro can be examined for more detailed explanation of
the displayed options.
BSD005I Socket debugging turned on.
(Important) This message is issued by $SOCKLST when socket debugging is turned on by the
EZAAPI command.

1.1
TCP-IP FOR VSE 1.5F Messages BSD Series Messages
BSD006I Socket debugging turned off.
(Important) This message is issued by $SOCKLST when socket debugging is turned off with
the EZAAPI command.
(Vital) This message is issued the first time an application uses the BSD socket API in a
partition. It contains the name of BSD phase, version, assembly date and time, and the load
address of the IPNRBSDC phase.
BSD101D function request started.
(Diagnose) This message is issued when in diagnostic mode. The displayed function is being
performed due to a request by a BSD application.
BSD102D function request completed R15=xxxxxxxx
(Diagnose) This message is issued when in diagnostic mode. The function shown has
completed and control is returning to the BSD application. xxxxxxxx is the result being returned
to the calling application. Although the result is dependent on the function call, a negative value
usually indicates that the request failed.
BSD103W function failed R15=x2 errno=x3 reason=x4 disp=x5
(Diagnose) This message is issued when in diagnostic mode and indicates that function has
failed. The fields are as follows:
x2 is the value returned in register 15. This is not necessarily the value returned to the
application at the time of the error, but it may be, for example, the return code from a VSE
GETVIS request.
x3 is the error number returned to the calling application.
x4 is an internal reason code.
x5 is the displacement within the BSD phase where the error occurred.
BSD104D Socket x1 allocated IPNRSO=x2 function=x3
(Diagnose) This message is issued when in diagnostic mode. A new socket has been allocated.
The fields are as follows:
x1 is the hexadecimal ID number of the newly allocated socket

x2 is the address of the allocated socket control block (IPNRSO)
x3 is the function that was active when the new socket was allocated

1.2
BSD105D Socket x1 referenced IPNRSO=x2 function=x3
(Diagnose) This message is issued when in diagnostic mode. A existing socket has been
referenced. The fields are as follows:
x1 is the hexadecimal ID number of the referenced socket

x2 is the address of the allocated socket control block (IPNRSO)
x3 is the function that was active when the new socket was referenced
BSD106D Running as a non-CICS task.
(Diagnose) This message is issued when in diagnostic mode. A application running in the
CICS/TS partition has requested a BSD function, but at the time of the call the associated task is
not running under the control of the CICS/TS main task. This could be a subtask attached in the
CICS/TS partition or application code running before CICS/TS is fully initialized.
Command-level CICS/TS services for storage requests, event waits, and other tasks will not be
used. VSE GETVIS, SETIME, and WAIT macros will be used instead for this subtask.
BSD108I TCP/IP recycle detected, nnn sockets closed during cleanup
(Critical) This message is issued when in diagnostic mode. It indicates that an application
request function was delayed because a recycle of the TCP/IP partition was detected.
BSD109I Checked: x1 Active: x2 Closed: x3 Listen: x4 Other: x5 Free: x6
(Important) This message is issued because the $SOCKOPT option “BSDCFG2=$OPTCHKR”

is in effect. This option causes all allocated sockets to be checked at the interval specified by the
$SOCKOPT CHKT=nnnn keyword.
The values displayed represent a summary of the currently allocated sockets.
BSD110I nnn sockets closed. Reason=xxx
(Info) This message is issued because the $SOCKOPT option “BSDCFG2=$OPTCHKR” is in

effect. This option causes all allocated sockets to be checked at the interval specified by the
$SOCKOPT CHKT=nnnn keyword.
The number of closed sockets and the reason they were closed is displayed. It is the
application’s responsibility to release unused sockets, and the application owning these dead
sockets should be reviewed and corrected so as to release its unused sockets.
xxx can be any of the following values:
“Timeout” means that “BSDCFG2=$OPTCHKR+$OPTFOPC” is in effect and that after the

socket was allocated, no socket open was ever issued using. It is therefore closed because it
has not been used for more than the CHKT= interval.

1.3
“Status” means that a status check of the socket issued to the TCP/IP partition has failed, and
the dead socket is therefore closed and marked for reuse.
“Forced” means that “BSDCFG2=$OPTCHKR+$OPTFOPC” is in effect and the socket was

allocated and opened, but it was not in a listen state for longer than 5 minutes. It is therefore
forced closed.
Use caution when setting “$OPTFOPC” to force closing opened connections. The associated
application should be examined and corrected.
BSD111D New highest socket number=nnnn
(Diagnose) This message is issued when in diagnostic mode. A new socket number has been
allocated, and a new highest allocated socket number has been attained.
BSD112D xxx bind to port nnnnn completed.
(Info) This message is issued when in diagnostic mode. A application has requested and
successfully issue a bind to port nnnnn. xxx is either TCP or UDP and indicates the type of
application.
BSD113I nnnn connect to ip-addr,port started.
(Info) This message is issued when in diagnostic mode. A application has requested a connect
from nnnn to a foreign ip-addr,port.
BSD114I xxxxxxxx yyyyyyyy zzzzzzzz
(Security) This message is issued when in diagnostic mode. This is an internal diagnostic
message that is used in various BSD functions. The text of the diagnostic message is variable
and is used for technical debugging.
BSD115I IPNRBSDC load=ad1 entry=ad2 ipnrcnst=ad3 pmblok=ad4
(Info) This message is issued the first time an application uses the BSD API in a partition. It
contains the name of BSD phase and three addresses:
The load address of the phase

The entry point of the phase
The address of the dynamically allocated common area
This information is intended to be used by CSI Technical Support to analyze problems that may
arise.

1.4
BSD116D Gives xxxxxxxx yyyyyyyy zzzzzzzz
(Diagnose) This message is issued when in diagnostic mode. This us an internal diagnostic
message that is used during givesocket processing. The text of the diagnostic message contains
either the originating clientid or destination clientid values.
BSD117D Take xxxxxxxx yyyyyyyy zzzzzzzz
(Diagnose) This message is issued when in diagnostic mode. This is an internal diagnostic
message that is used during takesocket processing. The text of the diagnostic message contains
either the originating clientid or destination clientid values.
BSD119D function request started.
(Diagnose) This message is issued when in diagnostic mode. The displayed function is being
performed due to a request by a application.
BSD120I Listen issued on socket @1.(@2.) for port @3. during @4.
(Info) This message is issued when in diagnostic mode. An application has requested a listen
state for a socket on a port.
BSD121I Listen active on socket num (addr) for port num during text
(Info) An application has requested a listen state for a socket on a port, but the socket is already
in a listen state.
BSD122D Socket x1 allocated IPNRSO=x2 function=x3
(Diagnose) This message is issued when in diagnostic mode. A new socket has been allocated,
but not anchored. The fields are as follows:
x2 is the address of the allocated socket control block (IPNRSO).

x3 is the function that was active when the new socket was allocated.
BSD123D AsyncIO values
(Diagnose) This message is issued when in diagnostic mode and indicates that an application
has requested an asynchronous I/O function. The values field contains information intended to
assist CSI Technical Support in diagnosing and resolving problems.

1.5
BSD124D AsyncIO base socket xxx for port yyyy closed
BSD126D Gethostbyaddr values
has requested an gethostbyaddr function. The values contains address of the area containing the
name of the associated IP address.

1.6
2
CGL Series Messages
CGL001W Cannot find program to remove: programname
(Important) CGILOAD was attempting to delete a program from partition GETVIS, but it could
not locate it in storage.
Operator Action: None. If this message occurs frequently, contact CSI Technical Support to
determine the cause of this condition.
CGL002E rexx-call failure RC=value reason=reason
(Vital) CGILOAD attempted to load a REXX/VSE program into partition storage using
ARXLOAD, but the process failed.
System Action: The request is cancelled.
Operator Action: Make sure that REXX/VSE is enabled. If it is, contact CSI Technical
Support to assist in troubleshooting.
CGL004W CGI encountered invalid OPEN type: hex-code
(Warning) A request was made to CGILOAD to pass control to a language type that is not
supported. The FITYPE value (in hex) is displayed (see the FIBLOK DSECT for a complete
description of these values).
System Action: The request is cancelled.
Operator Action: Make sure that your CGI is correctly defined. If it is, contact CSI Technical
Support to assist in troubleshooting.

2.1
TCP-IP FOR VSE 1.5F Messages CGL Series Messages
CGL005I CGI is now loaded. Name=name Type=type
(Diagnose) CGILOAD is operating in DEBUG mode, and a request was made to execute a
specific CGI that has not been invoked before. The name of the CGI and the type (REXX or
BAL, for example) is indicated in the message.
System Action: Storage has been allocated for the CGI, and it has been loaded into
CGILOAD’s partition GETVIS.
CGL010I CGL010I CGI program unloaded. Name: program Type=type
(Info) CGILOAD successfully deleted a program from the partition GETVIS so that a new copy
can be loaded later.
CGL011E CGI cannot obtain storage for chaining
(Vital) A request was made to CGILOAD to call a CGI and receive a response, but there is
insufficient 24-bit or 31-bit GETVIS to satisfy the request.
System Action: The request is canceled.
Operator Action: Increase the partition GETVIS in the CGILOAD’s partition.
CGL012W CGI-REXX module name terminated with RC=value
(Warning) CGILOAD issued a CALL to a REXX CGI, and the CGI terminated with a non-zero
return code.
System Action: Data returned from the CGI is passed along to HTTPD.
Operator Action: None. Informational only. You should probably correct your CGI to set
RC=0 and let the returned data indicate a correction or a failure.
CGL015E CGILOAD was unable to respond to HTTPD
(Vital) CGILOAD issued a CALL to a CGI and it returned data, but when CGILOAD
attempted to deliver that response back to HTTPD, it was unable to communicate using the
SOCKET link.
System Action: The request is terminated, and the storage is freed.
Operator Action: Ensure that HTTPD is active. Also, ensure that TCP/IP is still active. Check
for any other TCP/IP messages that may relate to this problem. If you cannot determine the
problem, contact CSI Technical Support.

2.2
CGL016I Closing the CGILOAD connection socket
(Diagnose) CGILOAD is executing in DEBUG mode. CGILOAD completed a request from the
HTTPD, and a connection has been closed.
CGL022I CGILOAD (version) generation date / generation time
(Info) CGILOAD was initializing. This message displays the version as well as the date and
time that it was assembled. This information tells you whether this version of CGILOAD is the
same as the TCP/IP stack. This is important to know for any type of problem determination.
CGL023I Debug has been set on
(Info) CGILOAD was initializing and found that the DEBUG execution parm was set to ON.
CGILOAD will begin to produce additional messages to SYSLOG.
CGL024E Unable to open passive SOCKET
(Critical) CGILOAD was trying to open a SOCKET to receive a request from the HTTPD, but
the SOCKET OPEN request failed.
System Action: The program is terminated.
CGL025I Waiting for an HTTPD request
(Info) CGILOAD is executing in DEBUG mode. CGILOAD is waiting for a request from the
HTTPD.
CGL026I Sending the data from CGILOAD back to HTTPD
(Diagnose) CGILOAD is executing in DEBUG mode. CGILOAD received a data buffer from
your CGI and is about to return it.
CGL027I Data has been sent to HTTPD
(Diagnose) CGILOAD is executing in DEBUG mode. CGILOAD sent data to HTTPD and is
waiting for an acknowledgement.
CGL029I Looking to see if name is already loaded
(Diagnose) CGILOAD is executing in DEBUG mode. CGILOAD has received a request to

load a CGI, and it will look for an existing chain.

2.3
CGL030I CGILOAD chaining process is complete
(Diagnose) CGILOAD is executing in DEBUG mode. CGILOAD has received a request to

load a CGI, and it did so successfully.
CGL031I Formatting the HTTP data for the CGI
(Diagnose) CGILOAD is executing in DEBUG mode. CGILOAD has received a request to run
a CGI. It is formatting the URL data.
CGL032I CGILOAD data has been formatted.
(Diagnose) CGILOAD is executing in DEBUG mode. CGILOAD has received a request to run
a CGI. It formatted the URL data.
CGL033I CGILOAD is freeing up storage.
(Diagnose) CGILOAD is executing in DEBUG mode. CGILOAD is being terminated and will
issue a series of FREEVIS calls.
CGL034I CGILOAD storage has been freed.
(Diagnose) CGILOAD is executing in DEBUG mode. CGILOAD is being terminated and

finished freeing up GETVIS.
CGL035I CGILOAD is removing a CGI from storage.
(Diagnose) CGILOAD is executing in DEBUG mode. A request has been passed to delete a
CGI from partition GETVIS.
CGL036I CGILOAD has removed the CGI from storage.
(Diagnose) CGILOAD is executing in DEBUG mode. A CGI has just been deleted from
partition GETVIS.
CGL037I Removing the HTML data from storage
(Diagnose) CGILOAD is executing in DEBUG mode. CGILOAD completed a request from the
HTTPD and is attempting to remove all of the chained HTML data that was kept in 31-bit
storage.

2.4
CGL038I CGILOAD has removed the HTML chain.
(Diagnose) CGILOAD is executing in DEBUG mode. A CGI has just finished executing, and
the HTML that it returned is now gone.
CGL039I CGILOAD will init the REXX environment.
(Diagnose) CGILOAD is executing in DEBUG mode. A REXX-CGI is wanted, so the

REXX/VSE environment needs to be initialized.
CGL040I CGILOAD initialized the REXX environment.
(Diagnose) CGILOAD is executing in DEBUG mode. A REXX-CGI is wanted, so the

REXX/VSE environment was initialized.
CGL041I CGILOAD will load a REXX program.
(Info) CGILOAD is executing in DEBUG mode. A REXX-CGI is wanted, so it will be loaded

into partition GETVIS.
CGL042I CGILOAD loaded a REXX program.
(Diagnose) CGILOAD is executing in DEBUG mode. A REXX-CGI was loaded into partition
GETVIS.
CGL043I Processing an OPEN request from HTTPD
(Diagnose) CGILOAD is executing in DEBUG mode. HTTPD is trying to call a CGI. This is
the initial request.
CGL044I CGI has returned control to CGILOAD
(Diagnose) A request was made to CGILOAD to pass control to a CGI-BAL program. This was
done, and now control has been passed back to CGILOAD after the CGI completed. This
message will display if CGILOAD is running in DEBUG mode.
System Action: Control is returned to CGILOAD.
CGL045I CGILOAD called the CGI.
(Diagnose) CGILOAD is executing in DEBUG mode. HTTPD called a CGI, and CGILOAD
completed the request.

2.5
CGL046I Processing READ request from HTTPD
(Diagnose) CGILOAD is executing in DEBUG mode. HTTPD called a CGI, and CGILOAD is
about to send the HTML that the CGI generated.
CGL047I CGILOAD is about to delete a CGI.
(Diagnose) CGILOAD is executing in DEBUG mode. CGILOAD is coming down, so it is

cleaning up storage by removing the CGI from GETVIS.
CGL048I CGILOAD deleted a CGI.
(Diagnose) CGILOAD is executing in DEBUG mode. CGILOAD is coming down, so it

cleaned up storage by removing the CGI from GETVIS.
CGL049I CGILOAD is about to load a program.
(Diagnose) CGILOAD is executing in DEBUG mode. HTTPD was requested to run a non-
REXX CGI, so the program will be loaded into GETVIS.
CGL050I CGILOAD loaded a program.
(Diagnose) CGILOAD is executing in DEBUG mode. HTTPD was requested to run a non-
REXX CGI, so the program was loaded into GETVIS.
CGL051I CGI was not previously loaded. Adding a chain.
(Diagnose) CGILOAD is executing in DEBUG mode. CGILOAD received a request to load a

CGI. It did not find an existing entry, so it created a new one.
CGL052W CGILOAD is unable to determine the LOIP value
(Warning) CGILOAD tried to start up, and in doing so it was asking the stack for the local IP
address, but the request failed.
System Action: Make sure that TCP/IP is active, or that a valid SYSID is in use during
CGILOAD initialization.
CGL053I CGILOAD is ready: SYSID=SYSID number IPADDR=IP address:port number
(Info) CGILOAD has successfully initialized and is telling you that it is in communication with
the TCP/IP stack at a specific IP address and port number

2.6
CGL054W CGILOAD terminating due to operator cancellation
(Important) The computer operator has cancelled the CGILOAD job. It will attempt to clean up
any communications and storage before terminating.
System Action: CGILOAD will attempt to clean up any communications and storage before
terminating.
CGL055I Pointing to REXX control block - hex value
(Info) During initialization, CGILOAD looks within VSE storage for pointers to the REXX/
VSE vector control blocks and displays their names and starting locations.
CGL056I The CGI OPEN request from HTTPD worked
(Diagnose) CGILOAD issued a CALL to the CGI, and the CGI terminated and returned a
positive length of data. This message is displayed if CGILOAD is running in DEBUG mode.
CGL057W The CGI-BAL data return length is < 1 byte
(Warning) CGILOAD received data from the CGI, but the output length field had a non-
positive integer.
System Action: CGILOAD will return a length of zero to HTTPD, and the user will see a null
screen.
Operator Action: Correct the CGI to output something in every case.
CGL058W REXX/VSE CGI support is disabled
(Warning) During initialization, CGILOAD looked within VSE storage for pointers to the
REXX/VSE vector control block and found that it was never initialized.
System Action: CGILOAD will shut down
Operator Action: Execute the required IBM utility to enable the REXX/VSE product.
CGL059I About to call the CGI-BAL program
(Diagnose) A request was made to CGILOAD to pass control to a CGI-BAL program. This
message is displayed if the DEBUG mode is enabled.
System Action: Control is passed to the CGI.

2.7
CGL060I program has been loaded into address
(Diagnose) HTTPD issued a call to CGILOAD for a non-REXX program that needed to be
loaded into partition GETVIS. This message tells you the name of the program and where it
was loaded.
Operator Action: None. Informational only. This message occurs if DEBUG mode is enabled.
CGL061I Bytes to send back to HTTPD: number
(Diagnose) CGILOAD issued a CALL to the CGI, and the CGI terminated and returned a
positive length of data. This message is displayed if CGILOAD is running in DEBUG mode. It
tells you how many bytes are being passed back to the HTTPD.
CGL062E Unable to connect to TCP/IP, SYSID=sysid
(Vital) CGILOAD attempted to establish a SOCKET connection with the TCP/IP partition, but
the SOCKET OPEN request failed.
System Action: CGILOAD terminates.
Operator Action: Make sure that the TCP/IP partition is up. If it is, make sure the CGILOAD
SYSID value is the same as the TCP/IP partition’s value. If the values match, make sure that
TCP/IP is not having any problems. If you still have problems, contact CSI Technical Support.
CGL063W Invalid port number passed. Using 4081
(Important) While CGILOAD was initializing, it checked the PORT execution parm and found
that the value was invalid. CGILOAD will default to using port number 4081.
Operator Action: Correct the execution parameter to eliminate this message.
CGL064E SOCKET OPEN terminated by the TCP/IP host
(Vital) CGILOAD was waiting for a session with the HTTPD, but the stack terminated the
session.
System Action: CGILOAD terminates.
CGL065I HTTPD request has been received. Bytes=nnnnn
(Diagnose) CGILOAD is executing in DEBUG mode. CGILOAD was waiting for a request
from the HTTPD, and a connection occurred.

2.8
CGL066E Receive of HTTPD data by CGILOAD failed
(Diagnose) CGILOAD is executing in DEBUG mode. CGILOAD was waiting for a request
from the HTTPD, and a connection occurred.
CGL067I Waiting to receive data from HTTPD
(Diagnose) CGILOAD is executing in DEBUG mode. CGILOAD is waiting for data to arrive
from the HTTPD.
CGL100I Common Gateway Interface (CGI) Startup for CGILOAD
(Info) CGILOAD is indicating that it is beginning to initialize the internal control blocks
required for the external CGI loader to function. This message is normally followed by
CGL053I to indicate that initialization was successful.
CGL101I CGL101I Common Gateway Interface (CGI) Shutdown for CGILOAD
(Info) CGILOAD is terminating.

2.9

2.10
3
EXE Series Messages
EXE001I Remote Execution Daemon (REXECD) is active on port nnnnn
(Info) REXECD been started and is waiting for work.
EXE002I Remote Shell Daemon (RSHD) is active on port nnnnn
(Info) RSHD has been started and is waiting for work.
EXE003E Unable to allocate GETVIS for a connection: nodename
(Critical) The remote execution daemon or the remote shell daemon was attempting to acquire
GETVIS to open a port and establish a session for a remote client, but the GETVIS request
failed.
System Action: The daemon will shut down.
Operator Action: Free up TCP/IP FOR VSE memory resources, or allocate more storage to the
partition running TCP/IP FOR VSE.
EXE004E Unable to open port nnnnn: RC=rc SRCODE=srcode
(Critical) The remote execution daemon or the remote shell daemon was attempting to acquire
GETVIS to open a port and establish a session for a remote client, but the GETVIS request
failed.
Operator Action: Free up TCP/IP FOR VSE memory resources, or allocate more storage to the
partition running TCP/IP FOR VSE.

3.1
TCP-IP FOR VSE 1.5F Messages EXE Series Messages
EXE005I Remote Execution Daemon (REXECD) has been shut down
(Info) REXECD been terminated either because of a DELETE REXECD command (because
TCP/IP is being shut down) or because of a GETVIS or OPEN SOCKET error during
initialization.
Operator Action: If the shut down was because of an error, you can try to restart the daemon.
Otherwise, no action is needed.
EXE006I Remote Shell Daemon (RSHD) has been shut down
(Info) RSHD been terminated either because of a DELETE RSHD command (because TCP/IP
is being shut down) or because of a GETVIS or OPEN SOCKET error during initialization.
Operator Action: If the shut down was because of an error, you can try restarting the daemon.
Otherwise, no action is needed.
EXE007E Socket send or receive failure. RC=rc SRCODE=srcode
(Critical) The remote execution daemon or the remote shell daemon was attempting to receive
some data from the remote client, but the receive failed.
System Action: The session is terminated, but the daemon waits for a new session.
Operator Action: If this repeats frequently, contact CSI Technical Support.
EXE008E Unable to locate REXX/VSE vector block
(Critical) The remote execution daemon or the remote shell daemon was attempting to initialize
the REXX/VSE environment, but the pointers in SYSCOM (IJBREXVT) do not contain a valid
address.
System Action: The daemon shuts down.
Operator Action: Initialize the REXX/VSE system if you have not already done so.
EXE009E Unable to add or delete a REXX environment. RC=rc Reas=reason
(Critical) The remote execution daemon or the remote shell daemon was attempting to initialize
or terminate REXX/VSE storage, but the request failed. The return code and the reason code
are provided in the error message.
Operator Action: Contact CSI Technical Support.

3.2
EXE010E Invalid datagram format received from remote client
(Critical) The remote execution daemon or the remote shell daemon was in a session with a
remote client, but the format of the data was invalid.
Operator Action: Repeat the process with a datagram trace enabled, and contact CSI
Technical Support for further assistance.
EXE011E Call to REXX program failed. RC=rc Reas=ReasonCode
(Critical) The remote execution daemon or the remote shell daemon was attempting to invoke a
REXX/VSE program, but the request failed.
Operator Action: If this repeats a frequently, contact CSI Technical Support.
EXE012E Unable to load/free REXX program name RC=rc
(Critical) The remote execution daemon or the remote shell daemon was attempting to load a
REXX/VSE program into storage, but the request failed.
Operator Action: Make sure the program exists and is in the LIBDEF search chain for .PROC
members. Make sure there is enough GETVIS in the TCP/IP partition. If this continues, contact
CSI Technical Support.
EXE013I Connecting STDERR via ipaddr:port
(Info) A remote execution client has contacted the shell daemon and requested that the daemon
connect back to the client at ipaddr using port.
Operator Action: If this repeats frequently, contact CSI Technical Support.
EXE014W STDERR port connection refused by the client
(Warning) The remote execution daemon or the remote shell daemon was attempting to connect
back to the client to complete the session, but the client refused the connection.
System Action: The session will end, and the daemon will wait for another request.
Operator Action: Reconfigure your client to allow a port connection from the VSE shell
daemon.

3.3

3.4
4
FTP Series Messages
FTP100I TCP/IP -- FTP Client -- Version ver
(Info) Issued to indicate initiation of the FTP client.
FTP101I Copyright dates (C) Connectivity Systems Inc.
(Info) This is the software copyright notice.
FTP102I TCP/IP -- FTP Client -- Complete
(Info) The FTP client has completed all assigned work and is terminating. Note that this
message does not imply that all requested operations completed successfully.
Administrator Action: If you are running the client in batch mode, check the job’s output for
other messages. Check for a non-zero completion code, which would indicate a failure of one or
more requests.
FTP103E TCP/IP -- FTP Client -- Failure
(Info) The FTP client has encountered a critical problem during operation and has terminated.
Administrator Action: Check the job’s output for additional messages that may indicate the
reason for the failure.
FTP104E Parameter errors found
(Info) One or more errors were detected by the batch FTP client while processing the
initialization parameters. The batch client will terminate.
Administrator Action: Examine the job’s output for information about which parameters were
in error. Correct the errors and resubmit the job.

4.1
TCP-IP FOR VSE 1.5F Messages FTP Series Messages
FTP105I Processing the execution parm override
(Info) The batch FTP client is starting to scan the execution parameters that you included in the
EXEC card PARM field.
FTP106I Processing of parm override complete
(Info) The batch FTP program has completed its scan of the execution parameters provided in
the PARM field of the EXEC card.
FTP107W Unidentifiable information found in parm
(Info) While processing the PARM field of the EXEC card the FTP client failed to find a
recognizable parameter. Processing terminates.
Administrator Action: Correct the problem, and then resubmit the job.
FTP108I Debugging set to On
(Info) This message is issued when DEBUG=ON is encountered as a parameter in the PARM
field. Once DEBUG is set to ON, the FTP client will issue additional messages that may be
useful in isolating problems in the transfer.
FTP109I IP Address is set to aaa.bbb.ccc.ddd
(Info) This message indicates the IP address of the foreign host that will be connected with for
file transfer. This message is issued when the IP parameter is processed and only indicates
correct syntax.
FTP110I PORT Number is set to aaa
(Info) This message indicates which TCP port number of the foreign host will be used for file
transfer. This message is issued when the PORT parameter is processed and only indicates
correct syntax.
FTP111I System ID is set to aa
(Info) This message indicates the system ID of the TCP/IP FOR VSE system that will serve as
the local host for the file transfer. This message is issued when the ID parameter is processed
and only indicates correct syntax.

4.2
FTP112E Syntax for parm is IP=nnn.nnn.nnn.nnn
(Info) This message is issued to remind you of the correct syntax of the IP parameter.
Administrator Action: Correct your syntax, and then resubmit the job.
FTP113E Syntax for parm is PORT=nnnnnn
(Info) This message is issued to remind you of the correct syntax of the PORT parameter.
FTP114E Syntax for parm is ID=nn
(Info) This message is issued to remind you of the correct syntax of the ID parameter.
FTP115I Connecting with TCP/IP for VSE partition
(Info) The FTP client is attempting to connect with the TCP/IP FOR VSE partition.
FTP116I Unable to open connection
(Info) The FTP batch client was unable to establish a connection with the foreign client. The
program terminates.
Administrator Action: Examine the job’s output for indications as to why the connection was
not established. Correct the improper conditions, and then resubmit the job.
FTP117I Now connected with partition
(Info) The FTP client was successful in establishing a connection with the TCP/IP FOR VSE
partition.
FTP118I Terminating connection
(Info) The FTP client is ending the session with the remote host.
FTP120I Connection has closed, successfully
(Info) The FTP client was successful in ending its session with the remote host.

4.3
FTP121I message text
(Info) This is a dummy message number used for displaying generic FTP client information.
System Action: The FTP client runs normally. This message number should not appear.
Operator Action: Contact CSI Technical Support to report the appearance of this message.
FTP122E GETHOSTBYNAME (DNS lookup) failed during request
(Info) The remote host whose name was specified in the IP= parameter of the batch command
could not be resolved. (The batch process attempted to do a gethostbyname lookup because IP=
was set to a domain name rather than a valid IP address.)
System Action: Execution terminates.
Operator Action: Ensure that the symbolic name is correct and that the host is able to
communicate. If the command failed during an OPEN process, the DNS server is not
responding. If it failed during a SEND, the DNS server rejected the request. If it failed during a
RECEIVE, the DNS server could not resolve the domain name.
Administrator Action: Use the SET DNSn= command to provide alternate DNS servers or to
provide for retries. Also consider increasing the timeout values for DNS calls.
FTP124W Flushing the rest of system input
(Info) An error has occurred while interpreting the control statements that prevents continuing.
Any remaining control statements are discarded.
Administrator Action: Examine the job’s output to determine what control statement(s) are in
error. When you re-run the job, be sure you allow for any operations that were performed
before the error was encountered.
FTP125E Sub system query failure
(Vital) The VSE SUBSID macro returned a non-zero code. The FTP client terminates.
FTP126W Interrupt has occurred, shutting down
(Warning) The FTP client has been interrupted (for example, it was canceled). The client
proceeds to termination.

4.4
FTP127I Local file identification has failed for DLBL: aaaaaaa at bbbbbbb
(Info) The FTP client has requested that a dynamic file definition be built for a specific file.
That request has failed.
Administrator Action: If you are running the client in batch mode, check the job’s output for
other messages. Check for a non-zero completion code, which would indicate the failure of one
or more requests.
FTP128I Syntax error in local file identification
(Info) The FTP client has requested that a dynamic file definition be built for a specific file, but
the syntax for request is not valid.
Administrator Action: Check your input parameter(s), and correct the syntax error.
FTP129E Syntax for parm is RETRY=nnnnnn
(Critical) The FTP client has requested that the default value for the retry counter be modified,
it but used an incorrect value.
Administrator Action: Correct the value in your job stream, and then resubmit the job.
FTP130E Syntax for parm is RETRYTIME=nnnnnn
(Critical) The FTP client has requested that the default value for the retry timer be modified, but
it used an incorrect value.
Administrator Action: Correct the value in your job stream, and then resubmit the job.
FTP131I Retry Counter is set to x
(Info) The FTP client has requested that the default value for the retry counter be modified.
FTP132I Retry Timer is set to x
(Info) The FTP client has requested that the default value for the retry timer be modified.
FTP133W Invalid level Translate Table: name
(Warning) The FTP daemon has encountered a request to use a translate table that is not
currently available. In the message text, level indicates how the table is being requested:
“Daemon” indicates that this is the daemon’s default translation table, as specified by the
DEFINE command that started the daemon.
“File” indicates that the translate table is associated with a specific file. It was assigned to the
file by a DEFINE FILE or MODIFY FILE command.

4.5
System Action: The daemon ignores the invalid translate table and continues processing.
Operator Action: For a level of “daemon,” ensure that the translate table is available, and then
cycle the affected daemons. For a level of “File”, ensure that the translate table is available, and
determine if the affected file(s) needs to be retransmitted.
Administrator Action: Ensure that translate tables are loaded during initialization prior to any
DEFINEs for FTP daemons.
FTP134W Security error: type
(Security) During an FTP session, a client requested that an action be performed. However,
security checking intercepted the request and rejected it.
System Action: The daemon does not perform the requested action, but it continues accepting
other requests from the user.
Operator Action: Many times the security error is caused by a simple typing error. However,
be alert to repeated attempts at trying passwords and randomly probing for allowed actions.
Administrator Action: You can use the daemon’s task identifier (the 5-character string,
ending with “:”, that preceded the message ID) to associate all messages issued by a particular
daemon during the course of an FTP session. This allows you to determine the user and IP
address responsible for the security error.
FTP137W Function of DLBL (DDname) failed. Reason: reason-text (RC=value)
(Warning) The FTP client issued a LABEL macro to find a DLBL. That request has failed.
System Action: The reason for the failure will be displayed. The request will fail. The function
is either “Locate”, meaning it was trying to look up the DLBL, or “Verify”, meaning that the
TCP/IP partition accepted the “Locate” and returned a LABEL control block (LPL) to be
verified as valid.
Administrator Action: Check the reason code. If RC=4, then it means that a DLBL is missing
and needs to be included in the FTP job. Review the text for the failure in the message. If you
still cannot determine the reason, contact CSI Technical Support.
FTP300I xxxxxxxx located at yyyyyyyy
(Info) The address of the program is displayed.
Administrator Action: If a problem occurs during the execution of FTPBATCH, this message
can help identify the failing program.

4.6
FTP301D FTPBATCH diagnostic RC=xx RS=yy
(Diagnose=FTP) This diagnostic message is produced when an abnormal condition occurs. The
value of the string diagnostic will vary depending on the condition.
The FTPBATCH program produced the return code RC and reason code RS. These codes may
be used by CSI Technical Support to diagnose the cause of the abnormal condition.
System Action: Depending on the problem, the FTPBATCH job may be terminated with a
non-zero return code.
Operator Action: Check the SYSLST output for other error messages. If the problem cannot
be resolved, contact CSI Technical Support.
FTP301E Critical Error Occurred Reason=xxxxxxxx
(Vital) A critical error occurred during the execution of FTPBATCH. There is an internal
processing error. The following reason codes exist:
Reason Code Meaning

RLIBFAIL The attempt to read FTPBATCH.L failed
FPSTZERO The call to locate a free port failed to return a valid port number
FTPDCDLF The CDLOAD of the FTPD daemon failed
ATTFAILF The ATTACH of the FTPD daemon failed
FTPDNLST The FTP daemon failed to initialize
ATTFAILC The ATTACH of IPNAFTPC failed
ATTFAFIT The ATTACH of the file I/O subtask failed
ATTCFAIL The ATTACH of the control subtask failed
FTPRZERO The receive returned with zero bytes
ICMDFAIL An internal command failed
FTPRSNDF The FTP SEND to IPNAFTPC failed
SUBABNDO A subtask ABENDed
STALLOUT A stall-out occurred
System Action: FTPBATCH terminates with a non-zero return code.
FTP302I Connected to TCP/IP SYSID aa in partition bb
(Info) FTPBATCH has successfully connected to the TCP/IP partition.

4.7
FTP303E ABEND aaaaaaaa PSW=bbbb CODE=cccc INT=dddd
(Important) An ABEND occurred in the FTPBATCH partition.
System Action: The PSW, registers, and storage at the time of the ABEND are written to
SYSLST.
FTP304I aaaaaaaa subtask is running
(Info) The subtask has been attached and has started running.
FTP305I Connection has closed successfully
(Info) The control session has been gracefully terminated.
FTP306I Commands from SYSIPT completed
(Info) FTPBATCH has completed reading commands from SYSIPT.
FTP308W Maintask posted with invalid ECB
(Warning) The FTPBATCH maintask was posted, but the ECB was invalid.
System Action: FTPBATCH continues to run.
FTP309W Command aaa failed and will be retried nnn times.
(Warning) The command failed to successfully complete and will be retried.
FTP310I aaa bytes sent bytes sent since start of session
(Info) The number of bytes sent as the result of FTP PUT commands.
FTP311I aaa bytes received since start of session
(Info) The number of bytes received as the result of FTP GET commands.
FTP312W Invalid operator command ignored
(Warning) The command issued by the operator to FTPBATCH is invalid.

4.8
FTP313I Zero bytes sent or received
(Warning) No data has been sent or received.
FTP314I Command connection SSL secured, data connection:xxxx
(Info) The FTP session will negotiate an SSL connection for all commands and replies. The
data connection will be either clear (no SSL), or private (SSL secured).
FTP315E Unidentifiable information found in PARM
(Important) While processing the PARM field of the EXEC card, FTPBATCH encountered an
invalid parameter.
System Action: Processing terminates.
Administrator Action: Correct the problem, and then resubmit the job.
FTP316I FTP Daemon terminated
(Info) The FTP daemon attached by FTPBATCH has terminated.
FTP318E FTPD Error Occurred Reason=xxxxxxxx
(Vital) A critical error occurred while attaching of the FTP daemon subtask.
System Action: FTPBATCH terminates with a non-zero return code.
Administrator Action: The following reason codes exist:
Reason Code Meaning

FTPCAUTH The PRODID authorization call failed
FTPCGALF The GETFLD ALET request failed
FTPDAUTH The PRODID authorization call failed
FTPDGALF The GETFLD ALET request failed
FTP319E TCP/IP System ID nn was not found
(Important) The requested TCP/IP system ID to be used was not found.
System Action: FTPBATCH terminates.
Administrator Action: Make sure the desired TCP/IP partition is running.

Use // OPTION SYSPARM='xx' in the batch job to identify the TCP/IP partition to be used.

4.9
FTP320W QUIT command sent after xxxxxxxx
(Warning) The QUIT command has been sent to terminate the FTP session. There are several
possible reasons why this happened:
• When an error occurs, the QUIT command is internally generated and sent.
• When the end-of-card input occurs without a QUIT as the last command, a QUIT is internally
generated and sent.
Operator Action: Be sure to include a QUIT command as the last input card for FTPBATCH.
FTP321W Connection stalled at hh:mm:ss
(Warning) No data has been sent or received during the interval specified by the
“SET TIMERAMT=” command.
System Action: FTPBATCH continues waiting for work.
Administrator Action: Use the SET TIMERAMT command to change the default to a higher
timer interval. The default value is 18000 (1 minute).
FTP322E No successful foreign completion message was received.
(Important) The “SET NEEDFMSG ON” command was issued, and FTPBATCH requires
either an F:226 or an F:250 for successful completion of any GET or PUT request.
Administrator Action: Examine the SYSLST output for failure messages from the foreign
host.
FTP323E No SET IPADDR= was issued in the main TCP/IP partition
(Important) A IP address of zeros is the current default IP address of the main TCP/IP partition.
The batch FTP client requires that this address matches the address of the VSE stack.
Administrator Action: Use the SET IPADDR= command in the main TCP/IP partition or add
a LIP= to the PARM= data of the FTPBATCH job to identify the default local IP address.

4.10
FTP324E Unable to load message handler rs=xxxxxxxx
(Important) The load of the common message handler has failed.
System Action: The FTPBATCH job is terminated.
Operator Action: Try to rerun the job. If the problem persists, contact CSI Technical Support.
Reason code Meaning

OPENCBAD Control open to the TCP/IP partition failed
OPENSRCD Control open to the TCP/IP partition failed
SENDCBAD Control send to the TCP/IP partition failed
SENDSRCD Control send to the TCP/IP partition failed
RECVCBAD Control receive to the TCP/IP partition failed
RECVSRCD Control receive to the TCP/IP partition failed
RECVNZER Control receive to the TCP/IP partition failed
CLOSCBAD Control close to the TCP/IP partition failed
BADSYSID Unable to locate the TCP/IP sysid in the SDL
ATTMFAIL The attach of the message subtask failed
FTP325W TCP/IP version different than FTPBATCH.
(Warning) FTPBATCH attempted to start up and discovered that the version of TCP/IP that is
being used is not the same release as the FTPBATCH client.
System Action: FTPBATCH continues.
Operator Action: If you are running multiple versions of TCP/IP, make sure that the LIBDEF
in the FTPBATCH job stream points to the correct version.

4.11
FTP326E VSE extract information failed rs=xxxxxxxx
(Important) FTPBATCH attempted to issue an EXTRACT macro for VSE system information,
but the request has failed.
System Action: The FTPBATCH job is terminated.
Operator Action: Try to rerun the job. If the problem persists, contact CSI Technical Support.
Reason Code Meaning

EXTRSYSF The VSE Extract ID=BDY request has failed
EXTRSVAF The VSE Extract ID=SVA request has failed
EXTRPARF The VSE Extract ID=PART request has failed
GFLDPPID The VSE Getfld Field=Logid request has failed
PRODAUTH The VSE Prodid Authorize request has failed
GFLDFPID The VSE Getfld Field=Logid for the main TCP/IP partition
has failed
GFLDALET The VSE Getfld Field=Alet for the main TCP/IP partition has
failed. The Alet is needed for access register mode
TCPEFAIL The VSE Extract ID=Part for the TCP/IP partition has failed
FTP327E Dataspace creation failed rc: aaa reason: bb
(Important) An attempt to create a data space has failed.
System Action: The definition of the dataspace file is aborted.
If this message is issued from an FTPBATCH partition, then FTPBATCH will terminate.
Operator Action: An RC of 8 with any ...0005... reason indicates that the space would violate
limitations set by your installation. In this case, use the VSE “QUERY DSPACE” and
“SYSDEF DSPACE” commands to display and modify the amount of virtual storage available
for data spaces.
FTP328E FTPBATCH failed, check SYSLST for errors rc=aaaa
(Important) FTPBATCH has failed.
System Action: The FTPBATCH job is terminated with a non-zero return code.
Operator Action: Check the SYSLST output for other error messages.

4.12
FTP329D Phase information
(Diagnose) The phase name was loaded at the displayed address.
FTP330E PARM='SSL=SERVER' must be specified to allow SSL.
(Important) The PARM field must contain “SSL=SERVER” to use SET SSL.
System Action: Add “SSL=SERVER” to the PARM field of the // EXEC FTPBATCH.
Operator Action: Correct the JCL, then rerun the job.
FTP331E Cannot respond to client: msg
(Info) During an FTP session, the daemon attempted to send the indicated message to the client,
but the transmission failed to complete.
System Action: The daemon attempts to continue the session. However, it is unlikely to
succeed.
Operator Action: Note any conditions indicated by other messages that may have caused the
transmission failure.
If the user session is hanging, it may be necessary to terminate it manually with either the
FLUSH or the DELETE FTPD commands.
Administrator Action: Frequent occurrence of this message may indicate a network problem
or incorrect script usage by the client.
FTP332I aaa sent bytes acknowledged by foreign stack
(Info) This is the number of bytes sent and acknowledged as the result of FTP PUT commands.
FTP333D count bytes acknowledged for prior retrieve.
(Diagnose=FTPD) This message indicates the total bytes retrieved and stored by the FTP
daemon during its last-completed operation.
FTP341I RETR/STOR to ip-addres,port flagged to be aborted
(Important) An FTP session with an active data transfer was aborted in response to an ABORT
command issued by the VSE operator
System Action: The data transfer operation is terminated.

4.13
FTP342I Session for userid ip,port terminated due to idletime exceeded
(Important) An FTP session has exceeded the allowed amount of idle time.
System Action: The FTP session is terminated.
Operator Action: The default idletime is 5 minutes, but it can be changed with the
“FTPBATCH SET IDLETIME nn” command, where nn is specified in 300th-second units.
FTP343W bytes of data received without end of record(cr/lf)
(Warning) This message is issued if extra bytes are received after the last complete record.
These extra byte(s) were not properly terminated. If this is a text file, then the last bytes of the
file are not delimited with a CR/LF (or other expected delimiter). The contents of the source file
on the remote system should be corrected to avoid this message.
FTP344D EXTTYPES xfer overrides used for aaa Type:bbb Structure:ccc Mode:ddd
(Diagnose=FTPD) This message is issued by the FTP daemon while DIAGNOSE=FTPD is in

effect. It identifies the transfer overrides that were used because the file type matched an entry
in the EXTTYPES.L member. Each entry in this member is mapped to a transfer type with
associated defaults.
FTP345D EXTTYPES file overrides used filename Recfm:xxx Recsize:yyy Blksize:zzz

effect. It identifies the file overrides that were used because the file type matched an entry in the
EXTTYPES.L member. Each entry in this member is mapped to a transfer type with associated
defaults for RECFM, RECSIZE, and BLKSIZE. By default, these values override both
DEFINE FILE and SITE command settings.
FTP347W Query connect,extended issued for fipaddr,fport(lport)
(Warning,Info) The SET DIAGNOSE QUERY command was successfully executed.

Diagnostic messages should be displayed in the TCP/IP partition.
FTP348W Diagnose TCP enabled/disabled for fipaddr,fport(lport)
(Warning) The SET DIAGNOSE TCP ON or OFF command was successfully executed.
Diagnostic messages should be displayed or disabled in the TCP/IP partition.
FTP349W Data connection foreign window size nnn(open/closed)
(Warning) A stalled connection was detected, and the window size of the foreign stack is
displayed. If the size is zero (closed), then the stall occurred because the foreign stack has
closed its window. The stack must reopen the window to avoid the stall-out.

4.14
FTP350E No successful local 226 message received.
(Important) While processing an FTP request, FTPBATCH waited for a valid “226” message
response that never arrived.
System Action: The batch client is cancelled.
Operator Action: This usually is the result of a clogged network or an FTP server that
cancelled the connection prematurely. Contact CSI Technical Support if the problem persists.
FTP351W Wrong version: phase
(Warning) The phase name is not the correct version.
FTP352W Should be : phase
(Warning) This the correct version for this phase.
FTP353W CDLOAD of xxxxxxxx failed
(Warning) The loading of phase xxxxxxxx has failed.
FTP400I Hardware crypto assist supports: SDES TDES AES128
(Info) This message is issued at startup when SSL=YES and CIPHER=HARDWARE are
specified. A crypto hardware assist query is issued, and the support cipher algorithms are
displayed.
FTP400W Hardware crypto assist detected with no AES or DES support KMC
(Warning) This message is issued at startup when SSL=YES and CIPHER=HARDWARE are
specified. A crypto hardware assist query was issued, but none of the cipher algorithms needed
for efficient encryption were supported. Contact your IBM hardware CE for current microcode
updates to support the DES and AES algorithms.

4.15
FTP402I SSL ciphers suites allowed: 2F 0A 09
(Info) This message is issued at startup when SSL=YES and CIPHER=HARDWARE are
specified. A crypto hardware assist query was issued, and the allowed cipher suites that the
hardware crypto assist (CPACF) supports are displayed. The hexadecimal values correspond to
the following SSL cipher suites:
Value Cipher Suite

01 RSA_NULL_MD5
02 RSA_NULL_SHA
08 RSA_SDES040_SHA
09 RSA_SDES056_SHA
0A RSA_TDES168_SHA
2F RSA_AES128_SHA
35 RSA_AES256_SHA
FTP800I id loaded at loc FTBLOK: addr
(Info) This message is issued at daemon startup and identifies the name of the driver phase, its
memory location, and the address of its definition block. This information may be useful to CSI
Technical Support.
FTP900I FTP Daemon listening aaa bb
(Info) An FTP daemon pseudo task has restarted. aaa is the identifier assigned by the DEFINE
FTPD command. bb is the port number (decimal) that will be monitored.
FTP901W PDF Error: text
(Warning) A request was made to convert the VSE text into a PDF before sending the text to
the FTP client. The PDF converter, however, returned an error code or could not be loaded.
System Action: The data will not be sent.
Administrator Action: Review the message, and make the appropriate correction before
retrying the request.
FTP903E Unable to obtain access to file system.
(Critical) The daemon was not able to gain access to the TCP/IP FOR VSE file system.
System Action: The daemon terminates.
Operator Action: Use a QUERY FILES command to ensure that at least one file has been
defined before restarting the daemon.

4.16
FTP904I FTP Daemon id has reached maximum sessions (max)
(Info) The FTP daemon indicated by id is now serving its maximum rated number of client
sessions, which is shown by max.
System Action: No further requests for FTP connections will be honored by this daemon until
a current session completes.
Operator Action: Ensure that FTP sessions have not been abandoned and left in a logged-on
state.
Administrator Action: If additional concurrent FTP sessions are desired, increase the daemon
count or the number of sessions that the daemon is permitted to handle. Before increasing the
number, be sure to consider the impact on storage, the network, and the CPU.
FTP905D Telnet error has occurred during event
(Diagnose=FTPD) During FTP processing, an error occurred on the control (telnet) connection.
event shows which telnet operation was being attempted at the time of the failure.
System Action: The FTP session terminates.
FTP906D Server diagnostic: type RC=rcode RS=reason
(Diagnose=FTPD) This is an FTP daemon diagnostic message. The codes displayed will be
useful to CSI Technical Support when diagnosing a problem.
Operator Action: This message can be eliminated by issuing the DIAGNOSE OFF command.
FTP908I Daemon Shutdown FTP ID: id Port: port
(Info) The FTP daemon identified by id is terminating.
Operator Action: If you want to restart the daemon, issue a DEFINE FTPD command.
FTP909I user in session with ip,port
(Security) The indicated user has started a session with an FTP client at the indicated IP address
and port.
FTP910I id data connection to ipaddr,port (lport)
(Info) This message is issued when a data connection has been opened with a remote FTP
daemon. The message shows the FTP daemon’s ID, the remote daemon’s IP address and port
number, and the local port number being used for the transfer.

4.17
FTP911I user ended session with ip,port
(Security) The indicated user has concluded a session with an FTP client at the indicated IP
address and port.
FTP912I id not accepting connections on port port
(Info) The indicated FTP daemon has ceased to accept requests for new FTP sessions on the
port shown.
FTP916E Unsupported item
(Important) While preparing to transfer a file, the FTP daemon encountered a request for an
unimplemented function of the File Transfer Protocol. The message indicates the type of
request being considered at the time.
System Action: The current file transfer is aborted.
FTP917I text
(Important) The FTP daemon allows the user of an FTP client to generate this message using
the SITE WTO command.
Operator Action: Determine any required actions from the message content.
Administrator Action: The four-digit pseudo task ID preceding the message number can be
used to associate the message with a particular FTP daemon. Other messages bearing the same
ID can be inspected for information on the UserID and IP address of the originator.
FTP918D data connection nnn retransmits
(Diagnose=FTPD) This message is issued when a data connection has completed and
retransmissions occurred. The messages shows the number of retransmits that occurred.
FTP919D File Storage Operation beginning
(Diagnose=FTPD) The FTP daemon is starting an RECEIVE operation for an incoming file.
FTP920D Mode aaa Structure bbb Type ccc
(Diagnose=FTPD) The file transfer being started by the FTP daemon has the stated
characteristics.

4.18
FTP921D LRECL aaa
(Diagnose=FTPD) The file being transferred by the FTP daemon has the stated LRECL.
FTP922I type connection using SSL ver Cipher=suite (handle)
(Security) A secure connection is being opened. This message indicates the connection type
(Data or Control), along with the SSL version and cipher suite being used for encryption.
handle provides information that that may be useful to CSI Technical Support if problems
occur.
FTP923D item: value

effect. It lists a series of items along with the values currently associated with each of them.
FTP928E Record nnn larger then max(mmm) for yyy. UNIX=xxx
(Important) During an FTP receive operation, a record was received that is longer than is
permitted for the target file. The record number, its length, and maximum allowed length are
also included in the message.
A common cause of this error is attempting to transfer a binary file while in Unix mode.
Because Unix equates ASCII and binary, TCP/IP FOR VSE was looking for ASCII end-of-
record separators but did not find them. Another cause is not supplying the correct RECFM and
LRECL when loading a SAM or VSAM file.
System Action: The file transfer is aborted.
Administrator Action: Be sure that RECFM and LRECL are specified, either in the DEFINE
FILE statement or by using FTP SITE commands. If the file is binary, either ensure that the
daemon is not in Unix simulation mode or rename the file to a recognized binary file type.
You can also specify UNIX=BIN in either the FTPBATCH PARM= or on the DEFINE FTPD
statement to force allowing a binary command to be respected while in Unix mode.
FTP930E Data received following EOF
(Important) The remote FTP daemon has transmitted an end-of-file marker or indicator. It then
followed that end-of-file with additional data.
System Action: The transfer is aborted.
Administrator Action: Ensure that the transmitting daemon is correctly indicating end-of-file.
Try retransmitting the file, specifying a different STRUCTURE and/or MODE.

4.19
FTP931E Write to file failed
(Important) During the receipt of a file, the daemon was unable to write the data to the
destination file.
Operator Action: Examine the console for additional diagnostic messages that might indicate
the problem. Ensure that the file is available, not full, and not write protected.
FTP933E Missing lead escape
(Important) While receiving a compressed record-mode file, the daemon did not find the first
character in the transmission to be an escape.
Administrator Action: Ensure that the remote daemon’s software is functioning properly.
Retry the transfer without compression.
FTP934I Processed command:
(Security) A DELETE, RENAME, MKDIR, or RMDIR command was executed. The text of
the command issued is recorded in the message file for auditing purposes.
FTP935I oper rec records, bytes for file file
(Security) This message is issued following transfer of a text file. It contains the total records
transferred, the bytes transferred, and the name of the transferred file.
FTP936I oper byte bytes for file file
(Security) This message is issued following the transfer of a binary file. It contains the total
records transferred, the bytes transferred, and the name of the transferred file.
FTP938W id data connection open failed F: ip,port L: ip,port
(Warning) This message is issued when a data connection could not be opened with a remote
FTP daemon. The messages show the FTP daemon’s ID, the IP address and port number of the
remote daemon, and the local port number being used for the transfer.
FTP939I Send of reply: xxx to command failed
(Info) Following the receipt and execution of a command issued to the daemon, the required
reply could not be sent to the FTP client that issued the command.

4.20
FTP940W send failed to F:ip,port L:port
(Warning) This message is issued when a data SEND fails. The message text shows the remote
daemon’s IP address and port number and the local port number used for the transfer.
FTP941I oper trailing blanks stripped
(Security) This message is issued following the transfer of a text file with SITE STRIP ON. It
contains the total number of trailing blanks that were truncated for all the text records of the
transferred file.
FTP942W REXXEXEC FileIO driver not loaded - Request bypassed
(Warning) A user issued a SITE REXX request, but the FileIO driver for that function was
never loaded.
System Action: The request fails.
Operator Action: If you want REXX EXEC to take place, then issue a DEFINE
FILEIO,TYPE=REXXEXEC command as part of the TCP/IP initialization. If not, then
suppress this message or use the security exit to provide more details.
FTP945W Data connection reset RC=code
(Important) This message is issued when a file transfer fails after a data connection has been
established. The socket codes are discussed in IPN950I Socket Scheduling Codes and IPN951I
Socket return codes (SRCODE).
System Action: The file transfer terminates, and the daemon waits for work.
Administrator Action: This condition is normal and expected in the TCP/IP environment, and
it may simply indicate that a user terminated a transfer by booting a PC. If it occurs frequently,
however, the network should be checked for problems.

4.21

4.22
5
GPS Series Messages
GPS900I iii GPS Daemon starting
(Info) The GPS daemon identified by iii is initializing for processing.
GPS901E iii GPS Daemon unable to allocate storage
(Vital) The GPS daemon identified by iii could not obtain enough partition storage to fully
initialize.
Operator Action: The storage shortage may be temporary. Wait for a brief period and then
restart the daemon.
Administrator Action: Either increase the amount of storage available in the partition, or free
storage being used for other purposes before restarting the GPS daemon.
GPS902E iii GPS Daemon unable to allocate FRBLOK
(Vital) The GPS daemon identified by iii could not allocate an FRBLOK for the TCP/IP file
system. Access to the file system is required for the daemon to operate.
Operator Action: Examine the console log for other messages that indicate the reason for this
failure. Ensure that a reasonable amount of partition storage is available for FRBLOK
allocation. Restart the GPS daemon.

5.1
TCP-IP FOR VSE 1.5F Messages GPS Series Messages
GPS903E iii GPS Daemon unable to locate storage file
(Vital) The GPS daemon identified by iii could not gain access to the temporary storage file
specified in the STORAGE= parameter.
System Action: The GPS daemon shuts down.
Operator Action: Ensure that the specified STORAGE= parameter identifies a fully qualified
public name from the TCP/IP file system and that it describes a valid library and sublibrary. To
test availability, try using FTP. You should be able to set the directory (CD) to the STORAGE=
value, and it must show up as a library.
GPS904E iii GPS Daemon detected possible file system damage
(Vital) The GPS daemon identified by iii could not gain access to the TCP/IP file system
because the structure of the file system is incorrect. One reason for this failure is that no file
system has been defined using the DEFINE FILE command or the EXEC FILESYS utility.
System Action: The GPS daemon shuts down.
Operator Action: Issue a QUERY FILES command to examine the contents of the file system.
Look for improper entries or other signs of problems. Review the console log for messages
relating to files. Delete and re-define the file that is specified by STORAGE=. If this does not
resolve the problem, cycle the TCP/IP partition.
GPS905W iii GPS processing previously queued data
(Important) During startup, the GPS daemon identified by iii found that its storage file already
contained untransmitted LPR data. This may have occurred if the previous instance of GPS
terminated abnormally for any reason, or if the remote LPD was previously unavailable. GPS
processing ensures that “stranded” data is not lost but is eventually sent to its intended
destination.
System Action: The previously queued data will be sent to the remote printer, and normal
processing will continue.
Administrator Action: If this is a frequent occurrence, examine how GPS, VTAM, and
TCP/IP are being shutdown.
GPS906E iii GPS could not open storage file
(Important) During startup, the GPS daemon identified by iii could not open the file specified
by the STORAGE= parameter.
System Action: The GPS daemon terminates.
Operator Action: Verify that the STORAGE= parameter specifies the fully qualified name of
a library and sublibrary defined to TCP/IP. Try accessing the file using FTP, and attempt to
read and write to the library.

5.2
GPS907E iii VTAM macro failure: xxx RC: cc Reason: rr
(Vital) The GPS daemon identified by iii encountered an unexpected failure of a VTAM request
during initialization. In the message text, xxx is the VTAM macro that failed, cc is the code
returned by the macro in register 15 (hexadecimal), and rr is the reason code returned in
register 0 (hexadecimal).
System Action: The GPS daemon will terminate or re-initialize, based on the
RETRY_COUNT= specification of the DEFINE GPSD command. If the problem is the result
of a REQSESS MACRO, the GPS daemon will complete initialization and wait for a BIND
request.
Operator Action: Examine the console log for other VTAM messages that may indicate the
reason for failure. Consult the IBM VTAM Programmer’s Reference for the specific meaning
of the return and reason codes. Restart the GPS daemon with “LOG=YES”. Examine the log
file for a dump of the VTAM control blocks following the error. If the failure indicates
REQSESS, this usually means that the target application (for example, CICS) is not ready to
accept a session. In this case, GPS will quietly wait for a BIND request from the application.
GPS908E iii VTAM Open failed. RC: cc Error: xx
(Vital) The GPS daemon identified by iii failed in its attempt to open its VTAM ACB. In the
message text, cc is the code returned by OPEN (hexadecimal), and xx is the error code from the
ACB (offset 23, decimal). Some of the error codes are as follows:
Code Meaning
24 A password is specified on VTAM APPL definition; GPS does not support passwds
50 VTAM is not present in the operating system
52 VTAM is in the process of terminating
54 The name specified in the GPS TERMNAME= parameter has not been defined to
VTAM as an APPL ID
56 The name specified in the GPS TERMNAME= parameter is defined to VTAM, but
NOT as an application ID
58 The name specified in the GPS TERMNAME= parameter is already open, perhaps
assigned to another GPS daemon
5A The name specified in the GPS TERMNAME= parameter could not be located in the
VTAM configuration tables; it may have been deactivated by the operator
5E VTAM is inactive or it is running at a priority lower than TCP/IP (VTAM must have
higher priority)
88 A temporary storage shortage has occurred
System Action: The GPS daemon will terminate or retry the OPEN based on the
RETRY_COUNT= specification of the DEFINE GPSD command.
reason for failure. Ensure that the value specified for TERMNAME= is a valid VTAM
application ID and that its status is active.

5.3
GPS909I iii VTAM retry number nn in ss seconds
(Info) The GPS daemon identified by iii failed in its attempt to begin VTAM processing. The
failure is considered transitory and the daemon will re-attempt the operation. In the message
text, nn is the retry attempt number and ss is the number of seconds that will elapse before the
retry is attempted.
System Action: TCP/IP will wait and then retry the connection.
Operator Action: Ensure that the VTAM APPL assigned to the GPS daemon is active.
Administrator Action: The RETRY= and RETRY_COUNT= parameters control the time
interval between retries and the total number of retries, respectively. Adjust these values for the
optimal results in your environment. If possible, determine the cause of the transitory failure
and make adjustments to prevent future occurrences.
GPS910I iii GPS Bind to application complete
(Info) The GPS daemon identified by iii had successfully negotiated a bind with a VTAM
application. Print data may now be sent from the VTAM application to GPS.
GPS911E iii VTAM Receive error. RC: cc Reason: rr
(Vital) The GPS daemon identified by iii encountered an error during a VTAM RECEIVE
request. In the message text, cc is the code returned by the RECEIVE macro in register 15
(hexadecimal) and rr is the reason code returned in register 0 (hexadecimal).
System Action: The GPS daemon closes the VTAM connection. If the RETRY_COUNT=
value has not been exhausted, the GPS daemon will attempt to re-initialize the connection. If
the specified retry attempts have been exhausted (or were not specified), the GPS daemon
terminates.
reason for failure. Correct the problem, and restart the GPS daemon if necessary.
Administrator Action: Consult the IBM VTAM Programmer’s Reference for the specific
meaning of the return and reason codes. Restart the GPS daemon with “LOG=YES”. Examine
the log file for a dump of the VTAM control blocks following the error.
GPS912I iii Application has released BIND
(Info) The GPS daemon identified by iii received and honored an UNBIND request from the
VTAM application.
System Action: All previously queued data, if any, will be sent to the remote printer. The GPS
daemon will then wait for another BIND request.

5.4
GPS913E iii File write failure: rr
(Vital) The GPS daemon identified by iii encountered an error while writing to the STORAGE=
file. In the message text, rr is the code returned by the TCP/IP file system in register 15
(hexadecimal). The member being written has a name equal to the value specified for
TERMNAME= and an extension of “PRINT”, if DEBUG=NO is in effect. Otherwise, the file
extension is of the form PRTnnnnn, where nnnnn is a number that begins with 00001, at
daemon initialization, and is incremented for each LPR operation.
System Action: The daemon attempts to LPR any queued data and then terminates.
Operator Action: Examine the console log for other messages that may indicate the reason for
failure. Ensure that the library is not full. Attempt to access the file using FTP, and test for the
ability to read and write.
Administrator Action: If this is a newly installed daemon, ensure that the library has been
defined using DEFINE FILE and that the sublibrary exists. Also, ensure that
READONLY=YES has not been specified for the library.
If this is an existing GPS daemon, the error is probably caused by a library-full condition.
Ensure that no production GPS daemons are executing in DEBUG=YES mode.
GPS915E iii Delete of member failed. RC: rr
(Vital) The GPS daemon identified by iii was unable to delete the staging member from the
STORAGE= library. In the message text, rr is the code returned by the TCP/IP file system in
register 15 (hexadecimal). The member name is the as same as the value specified by the
TERMNAME= parameter and the extension is PRINT.
System Action: GPS processing will continue.
Operator Action: No action required if other functions are ok.
Administrator Action: Examine the console log for other messages that may indicate the
reason for failure. This message does not necessarily indicate a severe problem.
GPS917I iii Waiting for BIND
(Info) The GPS daemon identified by iii is waiting for a VTAM application to request a BIND
with the logical unit named in the TERMNAME= parameter.
System Action: The GPS daemon waits for a BIND request.
Operator Action: If necessary, direct the target application (CICS or VTAM application) to
ACQUIRE the GPS printer.
Administrator Action: Consider specifying INSESS=YES on the DEFINE GPSD command.

This will cause GPS to attempt a BIND with the target application during startup and will
eliminate the need for the application to actively request the BIND.

5.5
GPS918E iii GPS Bind to application failed
(Important) The GPS daemon identified by iii has failed to negotiate a BIND with a VTAM
application.
System Action: The GPS daemon will wait for another BIND request.
Operator Action: Examine the console log for additional messages related to the failure.
Administrator Action: Ensure that the application program is attempting to bind in non-SNA
mode. Restart the daemon specifying LOG=YES, and examine the log for a dump of the
VTAM control blocks following the BIND failure.
GPS919E iii LPR operation has failed
(Important) The GPS daemon identified by iii has failed to complete an LPR operation. The
error is not considered to be recoverable.
System Action: The GPS daemon will shutdown and will preserve the un-transmitted data. If
the daemon is not running in DEBUG=ON mode, it will re-attempt the LPR operation
immediately on its next startup.
Operator Action: Previously issued messages should indicate the reason for the LPR failure.
Restarting the GPS daemon will cause an immediate retransmitting of the failed data.
Administrator Action: This particular failure usually indicates an error in GPS or LPR
parameters, such as those found in the LPR script. Using the TCP/IP command SET
DIAGNOSE=LPR and restarting the daemon will cause detailed LPR-related information to be
displayed on the console. Starting GPS with LOG=YES will also cause useful information to be
recorded in the GPS daemon’s LOG file.
GPS920E iii File close failed. RC: rr
(Important) The GPS daemon identified by iii encountered an error with the TCP/IP file system
when it issued a CLOSE request for its staging file. In the message text, rr is the return code
provided by the file system (hexadecimal).
System Action: The GPS daemon will attempt to LPR any collected data and will then
terminate. The LPR operation will probably fail with an I/O error.
Operator Action: Ensure that the GPS storage file is not full, and restart the daemon.
Administrator Action: Examine the console log for additional messages. Check the TCP/IP
file system for inconsistencies and errors. Ensure that the library is not full. Use FTP to access
the GPS storage library. You should be able to list the members and both read and write to the
library from your FTP client. Ensure that READONLY=YES was NOT specified on the
DEFINE FILE command for the library. If you are setting up a new GPS environment, ensure
that the STORAGE= parameter points to a library defined to TCP/IP by a DEFINE FILE and
that the sublibrary actually exists.

5.6
GPS921W iii TPEND received
(Important) During processing, a TPEND event was posted indicating that VTAM is
terminating or that the GPS APPL (LUname) was VARY’ed inactive.
System Action: The GPS daemon will queue any existing data to LPR and then terminate.
Operator Action: Restart the GPS daemon when VTAM is available.
GPS922I iii GPS Shutting down
(Info) The indicated GPS daemon is shutting down.
System Action: Prior to termination, GPS will attempt to LPR any remaining data that was
queued.
GPS923E iii File system deallocate error. RC: rr
(Important) During termination, the GPS daemon failed to properly disconnect from the TCP/IP
file system. In the message text, rr is the code returned by the file system (hexadecimal). This
message may indicate a problem with the TCP/IP file system.
System Action: GPS will attempt a normal shutdown.
Operator Action: No further action is required unless other symptoms occur.
GPS924I iii GPS Shutdown complete
(Info) The GPS daemon identified by ID iii has completed the shutdown phase.
Operator Action: You may restart this GPS daemon, if desired.
GPS925E iii DEBUG Write failed. RC: rr
(Info) While operating with DEBUG=YES, the GPS daemon identified by ID iii could not write
to the debugging file in the STORAGE= library. In the message, rr is the return code from the
file system (hexadecimal).
System Action: Processing continues, but the debugging data may be invalid or abbreviated.
Operator Action: This error probably indicates that the STORAGE= library is full. If this is
the case, it will be necessary to cycle the GPS daemon.
Administrator Action: Running GPS in DEBUG=YES mode causes all staged data and
additional debugging data to be retained for the daemon’s entire run. Under normal
circumstances, never run your GPS daemons in DEBUG=YES mode.

5.7
GPS928I iii Network retry number nn of mm in ss seconds
(Info) The GPS daemon identified by iii failed in its attempt to transmit the current print file
using LPR or could not connect with a “network printer”. The nature of this failure appears to
be transitory, and the daemon will re-attempt the operation. In the message text, nn is the retry
attempt number, mm is the total times this operation can be retried, and ss is the number of
seconds that will elapse before the retry is attempted.
System Action: GPS will retry the operation as indicated.
Administrator Action: The NETWORK_RETRY_COUNT= and

NETWORK_RETRY_TIME= parameters control the time interval between retries and the total
number of retries, respectively. Adjust these values for the optimal results in your environment.
If possible, determine the cause of the transitory failure and make adjustments to prevent future
occurrences.
GPS929E iii Required parameter missing: xxx
(Important) The GPS daemon identified with ID iii could not initialize because a required
parameter was not specified. In the message text, xxx indicates the missing parameter.
Different combinations of optional parameters will mean different combinations of required

parameters.
Administrator Action: Correct the DEFINE GPSD command to include all required
parameters.
GPS930I ID: iii LUname: tt Host: xx Printer: yy
(Info) Issued in response to a QUERY command, the GPS daemon identified by iii will transmit
to LP daemon on host xx and will use printer name yy. The daemon will appear as LU tt to the
application program. The following indented lines will describe other properties of the GPS
daemon.
GPS931I Target: tt Logmode: xx Insess: yy
(Info) Issued in response to a QUERY command. If INSESS=YES (yy), then the GPS daemon
will attempt to bind with the VTAM application, tt, using LOGMODE xx. This bind attempt
only occurs during initial daemon startup.
GPS932I User: ww Translate: xx Inserts: zz
(Info) Issued in response to a QUERY command. When initiating an LPR session, this GPS
daemon will identify itself to the remote LP daemon as user ww. The values for Translate and
Inserts will be used by GPS to format reports.

5.8
GPS933I Queuing: tt Storage: xx Log=yy Debug=zz
(Info) Issued in response to a QUERY command. The value coded for tt indicates where the
GPS daemon is staging the print data. “DISK” indicates that the data is contained in the storage
file (xx). “MEMORY” indicates that data is stored in 31-bit GETVIS pending final transmittal.
If yy is “YES”, the daemon is keeping a log file in the storage library. If zz is “YES”, the
daemon is operating in debug mode. In this mode, the daemon is not reusing its storage file(s)
and, in addition, is recording the data as it is received from VTAM.
GPS934I VTAM Retries: xx Retry Delay: yy
(Info) Issued in response to a QUERY command. xx is the number of times that the daemon will
retry a failing VTAM operation before terminating (assuming that errors are encountered). yy is
the time interval (in 300th-second units) between retries.
GPS935I Maxpages: ww Now queued: xx Maxidle: yy (zz seconds)
(Info) Issued in response to a QUERY command. ww is the maximum number of pages that will
be queued prior to initiating an LPR action. xx is the number of pages that are currently queued.
yy is the maximum idle time (in 300th-second units) that will elapse prior to initiating an LPR
action. zz is the same time expressed in seconds.
GPS936I Maxlines: ww Now queued: xx Maxchars: yy Now queued: zz
(Info) Issued in response to a QUERY command. ww is the maximum number of lines that will
be queued prior to initiating an LPR action. xx is the number of lines that are currently queued.
yy is the maximum number of characters that will be queued prior to initiating an LPR action.
zz is the number of characters that are currently queued.
GPS937I NOEJECT: ww Bracket Eject: xx
(Info) Issued in response to a QUERY command. If ww is “YES”, then initial formfeeds (those
preceding all other report data) are suppressed. If xx is “YES”, then receipt of a VTAM “Begin
Bracket” will cause a formfeed. Otherwise, brackets are ignored.
GPS938I Status: ww
(Info) Issued in response to a QUERY command. ww indicates the daemon’s current status.
GPS939I Network Retries: xx Retry Delay: yy
(Info) Issued in response to a QUERY command. xx is the number of times that the daemon will
retry a failing network operation before terminating (assuming that errors are encountered).
yy is the time interval (in 300th-second units) between retries.

5.9
GPS940I Control Order: xx
(Info) Issued in response to a QUERY command. xx is the order in which commands will be
placed in the control file.
GPS941E iii Could not load INSERTS: mmm RC: rrr
(Important) The GPS daemon identified with ID iii is being initialized in advanced mode and
the INSERTS= parameter was specified. However, an attempt to load the specified INSERTS
phase failed.
System Action: The GPS daemon terminates initialization.
Operator Action: Perform one of the following actions and then restart the daemon.
Remove the INSERTS= parameter from the DEFINE GPSD command.
Specify MODE=BASIC in the DEFINE GPSD command. Note that although the daemon
will initialize, any associated LPR attempts may fail until the problem with the INSERTS
phase is corrected.
Ensure that the named INSERTS phase is present and in the TCP/IP partition’s SEARCH
chain.
GPS942E iii VTAM op: xxxx RTNCD: rr FDBK2: ff
(Vital) The GPS daemon identified by iii received a bad completion code from a VTAM
operation. This message is issued from a SYNAD exit. In the message text, xxxx indicates the
VTAM macro that failed, rr is the recovery action (return) code in hexadecimal, and ff is the
RPL feedback code in hexadecimal.
Operator Action: Restart the daemon.
Administrator Action: Examine the values in this and related messages. Consult your VTAM
programming manuals for specific causes of the returned codes. If the cause and remedy are not
apparent, contact CSI Technical Support.
GPS943E iii Sense: ss Modifier: mm User Sense: uuuu
(Vital) The GPS daemon identified by iii received a bad completion code from a VTAM
operation. This message is issued from a SYNAD exit in conjunction with message GPSxxxE.
In the message text, ss is the System Sense byte, mm is the System Sense Modifier, and uuuu is
the User Sense data.

5.10
GPS944E iii VTAM data exceeds 8K
(Vital) The GPS daemon identified by iii received more than 8k of data from VTAM with
which to construct a 3270 buffer. This is far larger than any 3270 device is capable of holding.
Administrator Action: Check the application’s configuration, and limit the amount of data
sent in a single operation.
GPS947W iii VTAM RECEIVE failed to schedule. RTNCD: aa FDBK2: bb
(Vital) The GPS daemon identified by iii issued a VTAM RECEIVE request to obtain data
from the application but the macro failed to schedule. The hexadecimal values for the RPL
RTNCD and FDBK2 are displayed.
System Action: The daemon attempts to re-establish the VTAM connection.
Administrator Action: Check the IBM VTAM Programmer’s Guide for specific information
regarding the RTNCD and FDBK2 values.
GPS948W iii VTAM ACB is closed.
(Vital) The GPS daemon identified by iii issued a VTAM request to obtain data from the
application, but the ACB had been closed.
GPS949E Non-RPL LERAD event. Recovery Code: aa
(Vital) A GPS daemon had its LERAD exit driven, but no RPL address was passed. In the
message text, aa is the hexadecimal Recovery Action Code provided by VTAM.
System Action: The daemon takes additional recovery actions.

5.11
GPS951W iii VTAM RESETSR failed to complete. RTNCD: aa FDBK2: bb
(Vital) The GPS daemon identified by iii issued a VTAM RESETSR request, but it completed
with an error. The hexadecimal values for the RPL RTNCD and FDBK2 are displayed.
Administrator Action: Check the IBM VTAM Programmer’s Guide for specific information
regarding the RTNCD and FDBK2 values.
GPS952E iii LPR Receive failed to xxx Code yy
(Important) The GPS daemon identified by iii encountered a network error while attempting to
receive an ACK (x'00') from the remote LP daemon. In the message text, xxx is either
“schedule” or “complete,” depending on how the operation failed, and yy is the socket return
code.
The socket codes are discussed in IPN950I Socket Scheduling Codes and IPN951I Socket
return codes (SRCODE).
System Action: The GPS daemon will shut down; this is not a retriable condition.
Operator Action: Restart the GPS daemon to retry the operation.
Administrator Action: Examine the console for additional messages about this situation.
GPS953I iii LPR Send failed to type Code yy
(Important) The GPS daemon identified by iii was unable to transmit a data packet to the
remote LPD. An error flagged with “schedule” indicates that the socket would not accept the
request. “Complete” means that the data was accepted by the stack but could not be delivered.
The displayed code indicates the reason that the transmission has failed.
System Action: GPS will close the connection and restart the LPD operation based on the
NETWORK_RETRY_COUNT value.
Operator Action: Ensure that the remote LPD is active and able to accept data. Check the
console for additional messages.

5.12
GPS954E iii LPD returned NAK for xxx (nn)
(Important) The GPS daemon identified by iii encountered an error during an LPD session. In
the message text, xxx indicates the process that failed. nn is the “negative acknowledgement”
value (in hexadecimal) returned by the LP daemon. The correct value (ack) is always x'00'.
System Action: The GPS daemon will shut down as this is not a retriable condition.
Administrator Action: Check the LPD’s documentation for information on the meaning of the
specific NAK value.
GPS956E iii Network open failed to xxx. Code yy
(Important) The GPS daemon identified by iii encountered an error while attempting to
establish a network connection with a remote printer or LP daemon.
In the message text, xxx indicates whether the error occurred during “scheduling” or
“completion”. The code is the value returned by the open process.
System Action: The GPS daemon will attempt to open the network connection several times,
depending on the values coded for NRTIME= and NRCOUNT=. If the error cannot be cleared,
then the daemon terminates.
Operator Action: Ensure that the target printer or LPD is available and active.
Administrator Action: Try using PING or TRACERT to ensure that the remote host can be
reached and is available.
GPS957E iii Network close failed to xxx. Code yy
(Important) The GPS daemon identified by iii encountered an error while attempting to close a
network connection with a remote printer or LP daemon.
In the message text, xxx indicates whether the error occurred during scheduling or completion.
The code is the value returned by the close process.
System Action: The GPS daemon will continue processing.
Operator Action: Ensure that the target printer or LPD is available and active.
Administrator Action: Try using PING or TRACERT to ensure that the remote host can be
reached and is available.

5.13
GPS958E iiiControl open failed to xxx. Code yy
(Important) The GPS daemon identified by iii was unable to open a control connection to
request the resolving of a host name to an IP address. In the message text, xxx is “schedule” or
“complete” to indicate the phase of the connection process that failed, and yy is the socket
return code.
Operator Action: Ensure that the host name can be resolved and restart the daemon. Replacing
the host name with an IP address will eliminate the need for the control connection.
Administrator Action: Examine the console for additional messages issued in regard to this
situation.
GPS959E iii Insufficient xxx storage for LPR buffer.
(Important) The GPS daemon identified by iii could not obtain sufficient storage to allocate a
buffer to stage data to LPR.
In the message text, xxx indicates whether the storage needed is 24-bit or 31-bit. Disk queuing
requires 24-bit, while memory queuing can use 31-bit.
System Action: The GPS daemon will retry the operation several times.
Operator Action: Ensure that there is sufficient memory available for GPS use.
Administrator Action: If 31-bit storage is in short supply, consider increasing the partition
size. If 24-bit storage is problematic, consider using memory queuing.
GPS960E iii Queuing file could not be read. aa bb
(Important) The GPS daemon identified by iii could not read the queuing file to obtain the data
required for transmission to the remote LPD or printer.
aa is the completion code, and bb is the reason code returned by the Library file I/O driver.
System Action: The GPS daemon shuts down. When the problem can be corrected and the
daemon is restarted, GPS will attempt to send the queue data.
Operator Action: Examine other console messages for clues as to why the file retrieval failed.

5.14
GPS961E iii LPD rejected printer name: xxx (nn)
(Important) The GPS daemon identified by iii encountered an error during LPD session
negotiation. The printer queue xxx was requested, but the remote LPD failed to return a X'00'
acknowledgement. Instead, the LPD returned the hexadecimal nn
Operator Action: Change the printer queue name to the correct value or reconfigure the
remote LPD.
GPS962E iiiControl send failed to xxx. Code yy
(Important) The GPS daemon identified by iii was unable to send a control connection request
to resolve the host name to an IP address. In the message text, xxx is “schedule” or “complete”
to indicate the phase of the transmission process that failed and yy is the socket return code.
situation.
GPS963E iii Error while reading queue file. aa bb
(Important) The GPS daemon identified by iii could not read the queued data from the storage
file. In the message text, aa is the return code and bb is the reason code returned by the Library
file I/O routine.
situation.
GPS964I iii Network error while transmitting xx
(Important) The GPS daemon identified by iii was unable to transmit the specified item during
an LPR/LPD session. Values for xx are as follows:
“Printer name” — The first exchange with the LPD requires GPS to indicate the printer (or
queue) name to be used.
“Data command” — The LPD was being instructed to receive a data file.

5.15
“Data file” — The data file was being sent.

“Control command” — The LPD was being instructed to receive a control file.
“Control file” — The control file was being sent.
System Action: GPS will close the connection and restart the LPD operation based on the
NETWORK_RETRY_COUNT value.
Operator Action: Ensure that the remote LPD is active and able to accept data. Check the
console for additional messages.
GPS965E iii Network error while reading ACK for xxx
(Important) The GPS daemon identified by iii encountered a network error will attempted to
received and ACK (x'00') from the remote LP daemon. In the message text, xxx is the operation
for which an ACK is required.
situation.
GPS966E iiiControl receive failed to xxx. Code yy
(Important) The GPS daemon identified by iii was unable to receive the results from a control
connection request to resolve the host name to an IP address. In the message text, xxx is
“schedule” or “complete” to indicate the phase of the transmission process that failed and yy is
the socket return code.
Administrator Action: Examine the console for additional messages related to this situation.

5.16
GPS967E iiiControl close failed to xxx. Code yy
(Important) The GPS daemon identified by iii was unable to close the control connection after
resolving the host name to an IP address. In the message text, xxx is “schedule” or “complete”
to indicate the phase of the close process that failed and yy is the socket return code.
System Action: The GPS daemon will continue because the resolution already completed.
GPS968E iii Could not resolve host name: name
(Important) The GPS daemon identified by iii was unable to resolve the specified host name to
an IP address.
Operator Action: Ensure that the host name can be resolved, and restart the daemon.
GPS969I Maxidle: yy (zz seconds)
(Info) Issued in response to a QUERY command. yy is the maximum idle time (in 300th-second
units) that will elapse prior to closing the connection with the printer. zz is the same time
expressed in seconds.
GPS970W iii Direct socket send failed to xx Code hex Beginning recovery
(Info) While operating in direct socket mode, a data transmission to the printer has failed.
Failure may have occurred during either scheduling or completion of the send.
In the message, hex is the return code from the SEND operation.
System Action: GPS will attempt to re-open the connection and continue.
Operator Action: This error probably indicates that the printer went down, was disconnected
from the network, or has terminated the connection due to inactivity.
Administrator Action: Ensure that the value specified for MAXIDLE= is less than the
printer’s forced disconnect interval.
GPS999D text
(Diagnose=GPS) GPS999I messages contain information of a troubleshooting nature and

generally are issued only when DIAGNOSE GPS is in effect.

5.17

5.18
6
HTT Series Messages
HTT014W GETVIS failed for CGI program program RC=value
(Warning) HTTPD issued a call to a non-REXX CGI program that needed to be loaded into
partition GETVIS, but the GETVIS call failed.
Operator Action: Increase the amount of GETVIS in the TCP/IP partition.
HTT016W LOAD failed for program name RC=value
(Warning) The CGI file I/O driver attempted to load a non-REXX program into TCP/IP storage
with the LOAD macro, but it failed.
System Action: The process fails.
Operator Action: Check if the program exists, that it is in a sublibrary accessible to TCP/IP,
and that there is adequate GETVIS.
HTT900I HTTPD Startup (node)
(Info) The HTTP daemon is starting. The HTTP daemon handles Web-server requests.
HTT901E HTTP Daemon Unable to Allocate Storage
(Vital) There is insufficient 24-bit GETVIS for HTTPD to start a session.
Administrator Action: Reduce the amount of GETVIS utilization in the TCP/IP partition by
not over-allocating unnecessary resources. If the problem persists, contact CSI Technical
Support.

6.1
TCP-IP FOR VSE 1.5F Messages HTT Series Messages
HTT902E HTTP Socket open failed. R15=aa. SRCode=bb
(Important) The HTTP daemon was unable to open a socket connection.
System Action: If there are five open errors in a row, the daemon terminates. Otherwise, the
daemon will wait five seconds and attempt to open the socket again.
Operator Action: Examine other messages for clues to the problem, and restart the daemon.
HTT903I daemon Shutdown HTTP
(Info) The HTTP daemon is shutting down. No further HTTP requests are processed.
HTT904W Problem in locating File Request Block
(Warning) The HTTP task was attempting to locate a File Control Block to release storage, but
it was unable to find a matching anchor address.
System Action: Processing continues after taking a small snap dump for analysis.
Operator Action: If this happens repeatedly, contact CSI Technical Support.
HTT905D Closing socket due to description
(Diagnose=HTTP) The HTTP daemon is terminating a browser request. This diagnostic

message indicates the reason.
Operator Action: To eliminate this message, issue the DIAG -HTTPD command.
HTT906D Unable to locate aaa
(Diagnose=WEB) An HTTP request was made for the indicated object, but the object was not
found in the specified location. This may be a normal occurrence.
HTT907E HTTPD cannot locate resident EXTTYPES.L
(Vital) During TCP/IP initialization, the EXTTYPES.L table should have been loaded into 31-
bit GETVIS, with the message IPA616I indicating that it had been loaded. HTTPD looked into
GETVIS and could not find the control information.
System Action: HTTPD will use a default MIME content type for text/html.
Operator Action: Issue the command “RELOAD EXTTYPES” to the TCP/IP partition to load
the data into memory. Also, make sure that you have an EXTTYPES.L table in a VSE
sublibrary that is part of the TCP/IP for VSE initialization LIBDEF search chain. If all else
fails, contact CSI Technical Support for further assistance.

6.2
HTT908W HACKER ATTACK! Origin IPAddress: ipaddress
(Warning,Security) An HTTP request was made to “shell” into the operating system and invoke
any number of utilities normally available on a Unix or Windows computer. Because this is a
mainframe, the attempt failed.
System Action: The connection is terminated. The IP address of the client is displayed. The
source computer’s IP address is added to the “prevent access” list.
Operator Action: If the problem persists, turn this information over to your network
administrator
HTT909W HACKER ATTACK! Data: urlinfo
(Warning,Security) An HTTP request was made to “shell” into the operating system and invoke
any number of utilities normally available on a Unix or Windows computer
System Action: The connection is terminated. The first 32 bytes of data passed to HTTPD
through the URL is displayed.
administrator.
HTT910I Invalid HTTP request received: ipaddress
(Info) A TCP datagram arrived in the HTTP port, but it isn’t in any recognizable format. This
might be from a poorly written application, or a hacker may be doing a port-scan/banner-grab
from your system to determine your local environment.
System Action: The connection is terminated. The IP address of the client is displayed on
SYSLOG.
administrator.
HTT911I SOCKET call failed between HTTPD and CGILOAD
(Important) The HTTP daemon received a request to pass control to an external CGI, but the
communication interface, which consists of a SOCKET connection between the two
applications, failed.
System Action: The HTTPD will attempt to run the CGI locally.
Operator Action: Determine why the two applications cannot communicate. This message
may also mean that you need to have multiple CGILOAD programs running because the other
one may simply be busy.

6.3
HTT912W GET storage failure. SSI disabled
(Warning) A Web page was attempting to use the SSI (Server Side Include) facility
“<! INCLUDE FILE=name>.” Each SSI request requires 5k of 24-bit partition GETVIS. TCP/
IP doesn’t have even 5k of available contiguous GETVIS, so you cannot use SSI at this time.
Administrator Action: Reduce the number of unnecessary resources that have been allocated
to TCP/IP. If you cannot reduce the resource load, contact CSI Technical Support.
HTT913W HTTP warning: 0 bytes read - Retrying
(Warning) A request for a record from a CGI or the FileIO system returned a length of zero
without setting the EOF indicator. The null return is ignored, and the read request is repeated.
Administrator Action: If this is from a CGI, ensure that R1 is setting the correct length. If this
is from a file IO driver and the problem persists, contact CSI Technical Support.
HTT914W Record greater than 16k: X'xxx'
(Warning) A CGI was invoked and set R1 (returned record length) to a value greater than 16k.
The entire CGI request is discarded to eliminate a possible GETVIS overlay problem.
Administrator Action: Correct the CGI so that R1 is set to a valid length.
HTT915W CGILOAD not active. Required for aaa.
(Warning) An attempt was made to invoke a CGI that has been designated to run in a batch
partition outside of TCP/IP, but the CGI loading program, CGILOAD, is not active anywhere in
the VSE system. The request fails.
Administrator Action: Start the CGILOAD program to allow external batch CGI programs to
load and run.
HTT916D node (number) SSI complete, returning to filename
(Diagnose=HTTP) The HTTP daemon completed using a file that was included as part of an
SSI request. It will now return to the previous level of processing.
HTT917D HTTPD is connecting to CGILOAD via port nnn
(Diagnose=HTTP) The HTTP daemon received a request to pass control to an external CGI and
is about to open a SOCKET call between the two applications. The port number is included in
the message.

6.4
HTT918D Socket SEND failed. R15=X'aa' SRCODE=X'bb'
(Diagnose=WEB) The SOCKET SEND failed. The document will not be sent to the HTTP
client.
Administrator Action: Ensure that there is sufficient 24-bit partition GETVIS. If the problem
is intermittent, it might be because the Web client disappeared in the middle of a transmission.
If the problem persists, contact CSI Technical Support.
HTT919E REXX HTML() function error: GETVIS failed
(Critical) A REXX CGI attempted to issue the “HTML” function to return data back to the
client, but there is insufficient GETVIS to perform this activity.
Administrator Action: Free up GETVIS in the TCP/IP partition, or increase the overall
partition size.
HTT920D nodename (number) ready to receive inbound data
(Diagnose=HTTP) The HTTP daemon is open and has initiated a sequence of SOCKET
RECEIVE requests to accept the incoming data.
HTT921D note (number) Calling cginame with number bytes of data
(Diagnose=HTTP) HTTPD is about to invoke a CGI. The name of the CGI and the number of
bytes of data being passed to it are included in the message.
HTT922D node (number) Closing I/O interface to: filename
SSI request. It will now close that file.
HTT923D node (number) Close complete. Cleanup in progress.
SSI request. The file I/O interface has been successfully terminated. Buffers will now be
released.

6.5
HTT924D node (number) CGI name ended, returned number bytes
(Diagnose=HTTP) SET DIAG=HTTP is enabled, and an HTTP client invoked a CGI (CGI-
BAL or CGI-REXX) that was successfully loaded and called. The amount of data generated by
the CGI and returned is noted in the message.
Operator Action: None. Informational only. If you want to stop this message, use the
DIAG -HTTP operator command.
HTT925D node (number) Sending back number bytes (type)
(Diagnose=HTTP) A SOCKET call succeeded. This messages indicates how many bytes were
sent and the type of data.
HTT926D node (number) SSI will read/call filename/cginame
(Diagnose=HTTP) HTTPD encountered a file or CGI request in some text data that is part of a
server-side include (SSI). The name of the request is noted.
HTT928I Request not GET or POST: nnn
(Warning) The HTTP daemon received a request other than GET or POST.
Administrator Action: Perform a trace of the request and dump the trace to SYSLST. You
should see the problem datagram in the dump. If you cannot identify it, contact CSI Technical
Support.
HTT929D Security is looking for aaa in PASSWORD.HTML
(Diagnose=HTTP) SECURITY is enabled on the HTTP daemon. The HTTP daemon is looking
for the “&PASSWORD” or “&USERID” variables within the PASSWORD.HTML file.
This message is produced only when DIAGNOSE HTTP is in effect.
HTT930I Security could not find aaa in PASSWORD.HTML
(Important) SECURITY is enabled on the HTTP daemon. The HTTP daemon was looking for
the &PASSWORD or &USERID variables within the PASSWORD.HTML file, but it could
not find them. The user will not be able to log onto the server. A snap dump of the
PASSWORD.HTML file has been output to SYSLST.
Administrator Action: Print out the snap dump and make sure that the required field names
are in the file (“USERID” and “PASSWORD”). If they are not present, correct the file and
recatalog it. If the file looks fine, contact CSI Technical Support.

6.6
HTT931E Pseudo Task attach failed, aa
(Vital) The HTTPD daemon was unable to attach a TCP/IP pseudo task. In the message text,
aaa is the decimal return code from the internal attach process.
System Action: The browser request is canceled.
Operator Action: The failure may be the result of too many pseudo tasks or a lack of partition
GETVIS. If this message occurs frequently, reduce the workload for the TCP/IP partition.
HTT932W CLOSEFILE failed. Storage has not been freed
(Info) HTTPD tried to close a file, but the file I/O driver indicated that the request failed. If this
was a VSAM file, it will be left in an OPEN status. GETVIS will be freed from HTTPD.
System Action: If this occurs repeatedly, contact CSI Technical Support.
HTT933D SSL handshaking time (secs): nnn
(Diagnose=HTTP) The HTTP daemon received a request to use SSL and completed the initial
handshaking process. The message indicates how long it took.
HTT935D Processing failed. type=xxx code=nnn
(Diagnose=WEB) This message indicates the reason that a file request actually failed. This may
or may not be a program error.
HTT936D Initializing REXX/VSE hooks...
(Diagnose=HTTP) The HTTP task is initializing the REXX/VSE interface
HTT937D REXX/VSE hooks are/are not enabled
(Diagnose=HTTP) The HTTP task has initialized the REXX/VSE interface
HTT938D Releasing cgi-type buffers
(Diagnose=HTTP) The HTTP task is terminating and is now freeing up the allocated HTML
buffers.

6.7
HTT939D node (Main) Allocated SOCKET. Desc=addr
(Diagnose=HTTP) The HTTP daemon has successfully queued a socket for receiving browser
requests. The address of the SOCKET entry is in the message.
HTT940D node (number) HTTP subtask has been spawned
(Diagnose=HTTP) The HTTP daemon has started a subtask that will process a newly arrived
browser request.
HTT941D node (Main) Opening number sockets for port number
(Diagnose=HTTP) The HTTP daemon has started and is monitoring the indicated port. The
number of sockets (concurrent requests) is also displayed.
HTT942D node (Main) - Queuing another socket
(Diagnose=HTTP) The HTTP daemon is queuing a new socket to replace one that has been
converted to an active request. The new socket waits for the next browser request.
HTT943D nodename waiting for work
(Diagnose=HTTP) All outstanding browser requests have been assigned to subtasks and are in-
process. The HTTP daemon is now monitoring its assigned port for additional requests.
HTT944D node (Main) Checking incoming requests.
(Diagnose=HTTP) The HTTP daemon is checking for new browser requests. If any are found,
they will be assigned to individual subtasks for processing.

6.8
HTT945D node (Main) A connection has taken place
(Diagnose=HTTP) The HTTP daemon found a posted entry in the queue waiting to be
processed.
HTT946I Security: y/n Scanblocker: y/n
(Response) A continuation of message IPN509I, this message indicates status of the

SECURITY/SCANBLOCKER parameters.
HTT947I Lib: name Sublib: name
(Response) A continuation of message IPN509I, this message indicates whether the LIB and
SUBLIB parameters were set.
HTT948I Translate:name SOSI: name
(Response) A continuation of message IPN509I, this message indicates the translation tables
that are going to be used as well as SOSI.
HTT949I Count: nn Timeout: nn
(Response) A continuation of message IPN509I, this message indicates how many concurrent
ports will be opened and their timeout value during a receive.
HTT950I -----------------------------------------
(Info) This is a delimiter to let you know that the end of the HTTPD options list has been
reached for a specific daemon.
HTT951I Session rejected for aaa. LIMIT currently set to nnn
(Important) The HTTP daemon rejected a browser request because the maximum concurrent
requests are already in process.
System Action: The browser is notified of the rejection, and processing continues.
Operator Action: None. If this message appears frequently, you may want to start additional
HTTP daemons to increase concurrent processing.
Administrator Action: The LIMIT= parameter of DEFINE HTTPD allows you to specify
processing concurrency. The default value of 50 may not be sufficient in all cases.
Exceeding the concurrency limit may indicate that you are experiencing a DOS attack.

6.9
HTT952E SSL unable to initialize, reason: reason
(Vital) The HTTP daemon received a request to use SSL but it was unable to enable SSL
services.
System Action: Processing terminates
Operator Action: Review the reason for the failure. If you are unable to determine the reason
and correct it, contact CSI Technical Support.
HTT953W Cannot initialize REXX/VSE environment. RC=nn
(Warning) The HTTP daemon was attempting to initialize a REXX/VSE environment block
(using ARXINIT and passing an INITENVB request), but the REXX/VSE API returned a non-
zero return code.
System Action: Processing continues, but REXX CGIs will not function.
Operator Action: Refer to the REXX/VSE guide to determine possible problems.
HTT954D node (number) Received data from client: number bytes
(Diagnose=HTTP) The HTTP daemon queued up a SOCKET RECEIVE, and the client sent the
actual request. This message indicates the number of bytes sent.
HTT955D nodename (number) Accessing file name
(Diagnose=HTTP) HTTPD is opening a file to send back to the user.
HTT956D node (number) Loading CGI name from library.
(Diagnose=HTTP) HTTPD encountered a request to execute a CGI (non-REXX) as a subtask

of the HTTPD. The name of that phase is indicated.
HTT957D node (number) Attaching CGI name to the server
(Diagnose=HTTP) HTTPD encountered a request to execute a CGI (non-REXX) as a subtask

of the HTTPD. The server is allocating a control block to maintain the CGI.

6.10
HTT958D node (number) Invoking CGI name
(Diagnose=HTTP) HTTPD encountered a request to execute a CGI as a subtask of the HTTPD.

The server is in the process of passing control to that program.
HTT959D node (number) ALLOCATING/DEALLOCATING/RETURNING FRBLOK.

Address=X'address'
(Diagnose=HTTP) The HTTP daemon is about to allocate or deallocate a storage buffer used
for processing file I/O requests.
HTT960D nodename (number) Diag: string
(Diagnose=HTTP) HTTPD is processing a request. This diagnostic message can assist CSI
Technical Support in isolating any problems that the user may report.
HTT962D node (number) Reading input. Bytes returned: count
(Diagnose=HTTP) The HTTP daemon is processing an input file and has read some bytes of
data. This message tells you how much.
HTT963W nodename (number) CGI failed (name) Security failure
(Warning) HTTPD received a request from a Web client to execute a CGI, but the security exit
sent back a rejection code.
HTT964E HTTPD Working Storage error: location
(Vital) The HTTP daemon was about to use an internal data table, but a specific eyecatcher is
missing. This indicates that either the area was overlayed (storage corruption) or the pointer to
this area was corrupted.
System Action: Processing terminates.
Operator Action: If this problem repeats, contact CSI Technical Support.

6.11
HTT965E nodename (number) Bad file request block from routine_name
(Vital) HTTPD was going to perform a file I/O request, but it encountered a corrupted file
request block required for this operation.
Operator Action: Contact Technical Support.
HTT966W Requested to action a non-positive datagram length
(Warning) The HTTP daemon was requested to send or receive a datagram, but the length is
either zero or a non-positive value. This should never happen.
System Action: Nothing will be sent back.
Operator Action: If this occurs frequently, contact CSI Technical Support.
HTT967E Socket descriptor is missing or corrupt
(Vital) The HTTP daemon was requested to send a datagram to the client, but the socket
descriptor address was not initialized. This should never happen. It usually means that a SEND
is taking place without an OPEN or that storage has been overlayed.
System Action: The process terminates.
HTT968D nodename (number) CGI Initialization failed
(Diagnose=HTTP) HTTPD attempted to initiate a CGI request, but it failed.
System Action: The client is notified that the request cannot be completed.
HTT969D nodename (number) File/Web-Page not found
(Diagnose=HTTP) HTTPD failed to access a Web page or a file.
System Action: The client is notified that the request cannot be completed.
HTT970D node (id) Terminating step: text
(Diagnose=HTTP) This message indicates the stage of the termination process occuring within
the HTTP subtask (session).

6.12
7
IPA Series Messages
IPA101D Telnet Proxy: diagnostic text
(Diagnose=TELPROXY) This message is issued in response to an operator DIAGNOSE

TELPROXY command. The message text allows workflow to be traced through the Telnet
Connection Manager.
Operator Action: This message may be eliminated by issuing the DIAGNOSE -TELPROXY
command.
IPA117E Client-level Telnet translate table invalid
(Important) The Telnet client attempted to use the translate table that was specified by the SET
TELNET_TRANSLATE command. However, when the client started, the specified translate
table could not be found. The client continues execution but will use the the default translate
table.
Administrator Action: Be sure that an appropriate DEFINE TRANSLATION command has

caused the desired translate table to be loaded.
IPA200I diagnostic text
(Diagnose) This message is produced by the POP3 client when it is running with SET
DEBUG=ON.
The text portion of the message can be used to trace the client’s execution when trouble-
shooting a problem.
IPA302D Application Startup -- Connection FTP
(Diagnose=FTP) A VSE-based user has requested the services of an FTP client. The client task
is now starting and connecting with the user.

7.1
TCP-IP FOR VSE 1.5F Messages IPA Series Messages
IPA303D diagnostic text
(Diagnose=FTP) This message is used to trace the workflow through the FTP client. The text
displayed is, in general, only useful to CSI Technical Support.
Operator Action: This message can be eliminated with the DIAGNOSE -FTP command.
IPA305D Application Shutdown -- Connection FTP
(Diagnose=FTP) The FTP client has completed all functions or has failed in some manner. The
task is terminating and severing its connection with the user.
IPA401D FTP Command Request has been Received
(Diagnose=FTP) The FTP client has receive a command from the user.
IPA402D Application Startup FTP client (IPNAFTPC)
(Diagnose=FTP) The secondary FTP client task has been started due to a user’s request for an
FTP client.
IPA403D Local Telnet Connection Established for FTP
(Diagnose=FTP) The FTP client has established a Telnet connection with the remote host. This
connection will be used to transmit FTP commands and replies.
IPA404I Opening control connection to ip port
(Info) This message is used indicates that an FTP control connection open request has started to
the displayed IP address and port.
IPA405D Application Shutdown -- Command FTP
(Diagnose=FTP) The FTP client is shutting down. The Telnet connections will now be closed.
IPA406D FTP Command issued: cmd
(Diagnose=FTP) The user has entered the indicated command.
IPA407I FTP Commands to come from member: mmm
(Diagnose=FTP) FTP will fetch commands from library member mmm

7.2
IPA408I EOF in command member
(Diagnose=FTP) The FTP client has encountered the end of the library member. Processing
continues with manually entered commands.
IPA409D debugging information
(Diagnose=FTP) You are executing the FTP client with DIAGNOSE FTP enabled. The text
displays the command and its operands.
Administrator Action: None. Informational only.
IPA410W Unable to resolve host name: xxx
(Warning) The attempt to resolve host name xxx has failed.
System Action: The open of the desired host will not occur.
Operator Action: You should verify the host name is correct and review the SET DNSn
settings. Issue a QUERY OPTIONS to verify the current DNS resolution settings along with the
timeout setting for each DNS server.
IPA411I FTP Client connection using bbb Cipher=ccc Handle=ddd
(Info) The SSL protocol is being used to secure the connection with the version and cipher suite
indicated in this message.
IPA412D action RC=hex RS=hex
(Diagnose=FTP) This message displays the result of a specified action. The return and reason
codes are shown in hexadecimal. The contents of this message are, in general, only of interest to
IPA413I FTP command translation set to aaaa
(Info) The FTP command connection will translate commands and responses with the aaaa
translate table.
IPA414D Control connection established fipaddr fport (lport)
(Diagnose=FTP) This message indicates that an FTP control connection has been opened
between the displayed IP address and local port (in parenthesis).

7.3
IPA415D debugging information
(Diagnose=FTP) You are executing the FTP client with DIAGNOSE FTP enabled. The text
shown is the command response.
Administrator Action: None. Informational only.
IPA416W FTP command translation table xxxxxxx is invalid
(Warning) The FTP command connection translation table is not valid. Correct it, or use a
different translate table.
(Diagnose=DEBUG) This message is issued from the client command interface. The message
text indicates workflow passing through the routine. In general, this text is of interest only to
Operator Action: This message can be eliminated by issuing the DIAGNOSE -DEBUG
command.
IPA603E GETVIS failure loading file (size, loc)
(Vital) TCP/IP ran was unable to allocate sufficient storage to process the indicated file. size
indicates the amount of storage required, and loc shows the location where the storage was
requested.
Operator Action: Determine why the file was being loaded and how its failure to load will
affect operation.
Note: If the required storage amount is small, then other TCP/IP components will likely fail in a
short time.
Administrator Action: Increase the partition size, or change TCP/IP configuration options to
reduce the amount of memory required.
IPA604E Connection to Host failed.
(Vital) A SOCKET OPEN request was made, and the client was waiting for a connection from
the server. The return code was non-zero.
System Action: The session fails.
Operator Action: If the delay was 2 minutes, then the client timed out. Otherwise, it indicates
a rejection from the other end or lack of a proper route to reach the server.

7.4
IPA605E Unable to allocate TCP socket.
(Vital) A SOCKET OPEN request was made, but before a connection was able to begin the
TCP/IP stack (or lack of it) flagged the request as an error.
System Action: The session fails.
Operator Action: Make sure that the TCP/IP stack is up and that the correct SYSID is
indicated in the client execution parameter.
IPA606I Replacement value: value
(Info) The invoked client replaced a variable with a preset value, and this message indicates the
resulting setting.
System Action: None. Informational only.
Operator Action: If you want to disable this message, turn off the debugging setting for that
client.
IPA607E Unable to locate filename
(Response) While processing an operator command, TCP/IP was unable to locate the required
Library member.
Operator Action: Ensure that the indicated file exists and is in a Library accessible to TCP/IP
through the search chain.
Examine preceding console messages for additional clues, for example, messages from the
Librarian.
IPA608D type command has been issued
(Diagnose=DEBUG) This message indicates that TCP/IP has transmitted a command of the
indicated type (RSH, REXEC, FINGER, WHOIS).
Operator Action: This message may be eliminated by issuing the DIAGNOSE -DEBUG
command.
IPA609I Unable to locate variable: value
(Info) The invoked client attempted to replace a variable with a value, but no matching value in
storage was found.
client.

7.5
IPA610I Looking to replace variable: value
(Info) The invoked client was attempting to replace a variable with a value. This message
indicates the variable that will be sought after.
client.
IPA611D Connection opened with IP: aaa Port: bbb from Port: ccc
(Diagnose=LPR) The LPR client is opening a connection with a remote LPD. The variables
show the IP address and port information.
This message is produced only when DIAGNOSE LPR is in effect.
Administrator Action: If there is a problem connecting with the LPD, ensure that the port
numbers in use are acceptable to the remote software.
IPA612I File opened for xxx aaa,bbb,ccc
(Diagnose=(LPR,EMAIL)) The indicated client is opening a file to transmit its contents. The
variables show the file name nodes.
This message is produced only when DIAGNOSE EMAIL or LPR is in effect.
IPA613W Invalid item in file
(Response) While processing a RELOAD EXTTYPES command, TCP/IP has encountered a

record with invalid data. In the message text, item indicates the portion of the data that is
incorrect.
System Action: Processing proceeds with the next file record.
Operator Action: Examine the associated IPA615W message to identify the failing line in the
file.
Administrator Action: Correct the erroneous record in the file, then reissue the command.
IPA614W table is full
(Response) While processing a command to reconstruct the external names table, TCP/IP found
that more than the maximum of 8k was required.
System Action: Entries beyond the 8k limit are ignored.
Operator Action: Delete unnecessary entries from the EXTTYPES.L library member, and
issue the RELOAD EXTTYPES command.

7.6
IPA615W file seqnum data
(Response) While executing a command that involved processing a Library member, TCP/IP
encountered and error. In the message text, file is the member containing the incorrect entry,
seqnum is the sequence number (if present), and data is the first 40 bytes of the record.
Operator Action: Examine any preceding messages for information on the command being
executed and the reason the record was rejected.
Administrator Action: Correct the failing record.
IPA616I item has been loaded
(Response) Following an operator request, the indicated item has been loaded and is available
for use.
IPA617I Loading Library member member
(Response) In response to an operator command, TCP/IP has started to load and process the
indicated member from a Library.
IPA618W No EXTTYPES table found in GETVIS-31
(Warning) The EXTTYPES.L file was not loaded into GETVIS-31 during TCP/IP
initialization. A default MIME value will be used.
Operator Action: Issue a RELOAD EXTTYPES, and rerun the job if the output does not look
like what you want.
IPA619W No matching type type (mode).Using default.
(Warning) The attachment’s file type does not match any entry in the MIME table
(EXTTYPES.L). A default value will be used instead.
Operator Action: Update the EXTTYPES.L table, and issue the RELOAD EXTTYPES
command.
IPA620I variable has been stored: value
(Info) The invoked client stored a string relating to a variable into a table for later retrieval.
client.

7.7
IPA621W Unable to locate VCARD: name
(Warning) A request was made to attach a VCARD to the outgoing email, but the EMAIL client
was unable to access the requested binary LIBR member.
System Action: The EMAIL is sent without the VCARD.
Operator Action: Correct the name of the VCARD, or upload the desired VCARD into a
sublibrary that is part of the TCP/IP LIBDEF search chain.
IPA622E IPNAJSLD cannot load IPNAGETM Module
(Vital) The module that loads the JSEPLOOK and BLOCKLTR data into storage attempted to
LOAD the IPNAGETM module, which handles the LIBR I/O to obtain the data. The LOAD
request failed, and the process cannot contine.
System Action: The loading of those data areas is terminated, and all related storage is freed.
Operator Action: Check whether there is sufficient GETVIS in the partition. If there is, then
contact Technical Support.
IPA623I Skipping filename processing
(Info) The module that loads the JSEPLOOK and BLOCKLTR data into storage attempted to
find the data to use, but it was unable to do so.
System Action: The loading of that specific area is skipped. This may be normal if no JSEP
layout table or block letter definitions were defined and cataloged.
Operator Action: If you have defined these tables, make certain that they are correctly named
and stored in a VSE library that is part of the “*” or “SOURCE” LIBDEF search chain.
IPA624E Bad type parameter in line number
(Vital) The module that loads the JSEPLOOK and BLOCKLTR data into storage was
vaildating the input data and came across an invalid entry.
System Action: The name of the table (such as JSEPLOOK.L, although without the suffix) and
the line number in that table will be shown. A second line (message IPA615) will show the first
40 bytes of the bad entry.
Operator Action: Correct the entry in the table, and issue a RELOAD command for the JSEP
table.

7.8
IPA625E Errors encountered while loading tablename
(Vital) The module that loads the JSEPLOOK and BLOCKLTR data into storage encountered
one or more errors, which have been logged.
System Action: The JSEP tables are removed from storage.
Operator Action: Correct the input parameter errors, recatalog the table, and issue a RELOAD
to have the program try once more.
(Diagnose=EMAIL) This message is issued in response to a DIAGNOSE EMAIL command.

The text is useful in determining the source of problems that may occur in the email client.
(Diagnose=LPR) This message is issued in response to the DIAGNOSE LPR command. The
diagnostic text is useful in determining the source of problems that may occur during LPR
processing.
(Diagnose) This message is issued in response to a SET DEBUG=ON command in the input
string to the LPR client. It contains information that may be useful in diagnosing problems with
the LPR client.
IPA629I user-specified text
(Info) This message is issued in response to a SAY command passed to a client. The displayed
text is the operand specified with the SAY command.
(Diagnose) This message is issued in response to a SET DEBUG=ON command issued to the
RSH client.
(Diagnose=LIBR) This message is issued by IPNFGETM, which is used to obtain library

members for processing by other programs. The diagnostic text in the message may be useful in
determining the problem.

7.9
IPA650E TERMTYPE.L: LOGMODE missing for xxx
(Response) While processing an entry in the TERMTYPE.L member, an invalid entry was
encountered. The LOGMODE field was missing for the terminal type xxx.
System Action: TCP/IP stops processing the member, and the terminal types table remains
unchanged.
Administrator Action: Correct the record, and reissue the RELOAD TERMTYPE command.
IPA651E TERMTYPE.L: Terminal type too long, xxx
encountered. The terminal type field was too long for terminal type xxx.
The maximum length is 16 characters.
unchanged.
IPA652E TERMTYPE.L: LOGMODE too long, xxx
encountered. The LOGMODE field was too long for terminal type xxx.
The maximum length is 8 characters.
unchanged.
(Diagnose=CONT) This message is issued by the Control Manager to trace workflow through
the routine. The contents of the message will only be of use to CSI Technical Support.
command.
IPA702I Product code check for nnn failed t< Warning
(Info) This message is issued when an external request for product code validation fails.
nnn is the product/feature number.

7.10
8
IPC Series Messages
IPC102D Diagnostic text
(Diagnose=DEBUG) This message traces ICMP workflow. The message content may be self-
explanatory or of interest to CSI Technical Support.
Operator Action: This message can be eliminated by use of the DIAGNOSE -DEBUG
command.
IPC107D ICMP Check Sum Failed from source ip
(Diagnose=CHECKSUM) An ICMP datagram has arrived but could not be processed because
the checksum failed validation.
System Action: The datagram is discarded after it is dumped to SYSLST.
Operator Action: This message and dump are in response to DIAGNOSE CHECKSUM. Only
10 messages and dumps will be produced each time DIAGNOSE CHECKSUM is specified.
IPC108I ICMP Echo request has been received from: nnn
(Info) A remote client has sent a PING (or other ICMP echo) request to TCP/IP for VSE. nnn is
the IP address of the requester. Not all PING requests use ICMP, although this is most common.
UDP and TCP also have echo services.
This message is useful in diagnosing network routing problems. When this message is seen, it is
proof that inbound requests are reaching VSE. If the ping is failing, then the problem lies in
routing the reply back to the remote host.

8.1
TCP-IP FOR VSE 1.5F Messages IPC Series Messages
IPC109D Unsupported ICMP request from addr. Type: value
(Diagnose=REJICMP) An ICMP datagram has been detected that contains an unsupported

function.
Operator Action: This message and dump is in response to DIAGNOSE REJICMP. Only 10
messages and dumps are produced for each specification of DIAGNOSE REJICMP.
IPC110D ICMP - diagnostic text
(Diagnose=ICMP) This message is issued in response to the DIAGNOSE ICMP command and
conveys information on the progress of ICMP requests.
Operator Action: This message can be eliminated by using the DIAGNOSE -ICMP command.

8.2
9
IPD Series Messages
IPD100I File I/O Abend. Driver phase, Request "type". FRBLOK at addr
(Important) An abend has occurred while the indicated I/O operation was being processed. The
name of the phase assigned to process the request is also shown. The FRBLOK address, which
may be of interest to CSI Technical Support, is displayed.
Operator Action: Examine other messages for additional information.
IPD101I PSW: psw [ABEND/Interrupt Code: code] [Offset hex in prog name]
(Important) This message is produced when an abend or program check occurs in a File I/O
routine. The PSW is always shown. In addition, the Abend or interrupt code is displayed if it is
known. If the address where the interrupt occurred is within a program loaded by TCP/IP, the
name of the program and the offset within the program is shown.
Operator Action: Examine other console messages and SYSLST for additional information.
IPD102I 0: value 1: value ...etc...
(Important) This message is produced during a diagnostic dump and shows the current register
contents in hexadecimal.
IPD103I 8: value 9: value ...etc...
contents in hexadecimal.

9.1
TCP-IP FOR VSE 1.5F Messages IPD Series Messages
IPD104I 0: offset 1: offset ...etc...
contents as a hexadecimal offset within a program. The line that immediately follows will
contain the program name.
If no value is displayed, then the corresponding register does not address an area within a
program.
IPD106I Save area at: addr (Previous: addr Next:addr)
(Important) This message is produced during a diagnostic dump. It precedes a dump of the
register save area at the displayed address. The message also shows the addresses of save areas
chained from the current save area.
IPD107I File I/O requesting task: id Program: name
(Important) An abend has occurred while processing an I/O request. This message shows the
hex ID of the pseudo task that requested the I/O. The program running as the pseudo task is also
shown.
IPD108I Save area trace ended because reason
(Important) An abend has occurred while processing an I/O request. This message is produced
while the program save areas are being dumped. The reason will indicate why formatting was
terminated. Note that this is generally a normal situation.
IPD109I I/O Request made from addr, Offset hex in name
(Important) An abend has occurred while processing an I/O request. This message indicates the
address where the I/O request originated. The calling program’s name is also shown, if known,
as well as the offset within the program.
IPD110I File I/O Abend. name at addr is not valid.
(Important) An abend has occurred while processing an I/O request. While producing
diagnostics, the control block located at the indicated location is not valid.

9.2
IPD111I num bytes dumped; num bytes to go
(Info) This message is produced during a diagnostic dump. It is issued multiple times and
shows progress as lines are being written to SYSLST.
IPD112I File I/O Abend diagnostics complete
(Vital) An abend has occurred while processing an I/O request. This message indicates that all
diagnostics have now be printed to SYSLST.
IPD113I File I/O task has ABENDed. status
(Vital) An abend has occurred while processing an I/O request. This message indicates the
diagnostics that are being generated. The status field will display one of several values:
Status Text Meaning

CSI Diagnostics skipped Formatted diagnostics for CSI analysis are being skipped. This
generally occurs because a DUMPOPTIONS IBM/NONE
command was issued.
CSI Diagnostics in Formatted diagnostics for CSI analysis are now being
progress generated. This is the default behavior.
IBM Diagnostics in Because the DUMPOPTIONS IBM command was issued, VSE
progress will produce its standard dump for the condition encountered.
File I/O diagnostics now Following the production of diagnostics for a file I/O abend, a
inhibited flag is set to prevent diagnostics from being generated for
future abends. This prevents excessive spool use caused by
recording redundant information. The DUMPOPTIONS
command can be used to reinstate diagnostics, if desired.
Reloading the failed I/O The stack has determined that the reason for the file I/O failure
driver may be related to a corrupted phase. The phase is deleted, and a
fresh copy is loaded.
File I/O recover complete All required diagnostics are complete, and recovery of the
failed operation has been successful.
IPD114I File I/O ABEND code hex text
(Important) This message is produced during a diagnostic dump. It shows the VSE abend code
number (hexadecimal) and a plain-text description of the abend.

9.3
IPD115I 8: offset 9: offset ...etc...
contents as a hexadecimal offset within a program. The line that immediately follows will
contain the program name.
If no value is displayed, then the corresponding register does not address an area within a
program.

9.4
10
IPF Series Messages
IPF100I type I/O Handler action
(Info) The task that handles I/O for the indicated type is either starting or stopping.
IPF101W driver freed number orphaned buffers: size bytes each
(Warning) Either the TCP/IP partition is being shut down, or the command “DELETE
FILEIO,ID=drivername” was issued. The driver checked and discovered several blocks of
storage that were allocated for use by other applications but had not been freed.
System Action: The storage is freed.
Operator Action: None. If this command was manually entered, however, it means that an
application either cancelled and did not clean up storage, or it is held up and cannot request that
storage be freed. It also may mean that an application is very slow, and when it regains control
it may abend. Use this command only when you are sure it will not affect anything else.
IPF102E Sequential File open error. DLBL: name
(Important) The sequential disk file identified by its DLBL (name) could not be opened. This
message should be accompanied by other console messages that will indicate the reason for the
failure.
Administrator Action: Correct the problem and retry the file access.
IPF103E Sequential read request failure has occurred. DLBL: name
(Important) An attempt to read a record from a sequential disk file has failed. This message
should be accompanied by other console messages that will indicate the reason for the failure.
Administrator Action: Correct the problem and retry the file transfer.

10.1
TCP-IP FOR VSE 1.5F Messages IPF Series Messages
IPF104E Sequential write request failure has occurred. DLBL: name
(Important) An attempt to write a record to a sequential disk file has failed. This message
Administrator Action: Correct the problem and retry the file transfer.
IPF105E Sequential logical error has been detected. DLBL: name
(Vital) The ERROPT exit has been driven by the system. This message may be accompanied by
other console messages that will indicate the reason for the failure.
IPF106E Sequential wrong length error has been detected. DLBL: name
(Important) The WLRERR exit has been driven by the system. This message may be
accompanied by other console messages that will indicate the reason for the failure.
IPF107D Sequential record count of DLBL: aaa is bbb
(Diagnose=FILEIO) This is a diagnostic message issued when DIAGNOSE FILEIO is in

effect. The DLBL name and the number of records transmitted are displayed.
IPF108E Invalid SAM request: I/O type=value
(Critical) The sequential disk file identified by its DLBL (name) could not be opened because
the input/output type passed did not indicate INPUT or OUTPUT. This is represented by a one-
byte value in the FRBLOK, which is displayed in decimal in the error message. You can find a
list of values in the FRBLOK DSECT macro under a list of equates for FRPARM1.
System Action: The processing fails. A PDUMP of the file request block will be output to
SYSLST.
IPF109E Invalid SAM request: RECFM=recfm
the record format passed was invalid.
System Action: The processing fails. A PDUMP of the file-request block will be output to
SYSLST.

10.2
IPF110E Invalid SAM request: RECLN=recfm
the record length passed was invalid.
System Action: The processing fails. A PDUMP of the file request block will be output to
SYSLST.
IPF122I Sequential File open error. TLBL:name
(Important) The tape file identified by its TLBL (name) could not be opened. This message
Administrator Action: Correct the problem and retry the file transmission.
IPF123I Sequential read request failure has occurred. TLBL:name
(Important) An attempt to read a record from a tape file has failed. This message should be
Administrator Action: Correct the problem and retry the file transmission.
IPF124I Sequential write request failure has occurred. TLBL:name
(Important) An attempt to write a record to a tape file has failed. This message should be
Administrator Action: Correct the error and retry the file transmission
IPF125E Sequential logical error has been detected. TLBL:name
(Important) The ERROPT exit has been driven by the system. This message may be
IPF126I Sequential wrong length error has been detected. TLBL:name
(Important) The WLRERR exit has been driven by the system. This message may be
IPF127D Sequential record count of TLBL:aaa is bbb
(Diagnose=FILEIO) This is a diagnostic message issued when DIAGNOSE=FILEIO is in

effect. The TLBL name and the number of records transmitted are displayed.

10.3
IPF152I I/O Handler Open Data Space: name
(Info) The data space used for data is being opened. The name of the data space is also
displayed.
IPF153I I/O Handler Close Zip Data Space: name
(Info) The data space used for zipping is being closed. The name of the data space is also
displayed.
IPF154E Data Space open error, name reason
(Important) The attempt to open a data space has failed. The name of the data space and error
reason are displayed.
IPF155E Data Space close error, name reason
(Important) An attempt to close a data space has failed. The name of the data space and failure
reason are displayed.
IPF156E Data Space read error, name reason
(Important) An attempt to read from a data space has failed. The name of the data space and
failure reason are displayed.
IPF157E Data Space write error, name reason
(Important) An attempt to write to a data space has failed. The name of the data space and
failure reason are displayed.
IPF158I Data Space:name nnnnK used(nn%)
(Info) This amount of the data space used is displayed. This size of the data space is set by the
DEFINE DSPACE command, and it can be adjusted based upon the information contained in
this message. The K value is rounded up.
IPF202E VSAM ESDS File open error, Return: rr Feedback: ff DLBL: name
(Important) An open request for a VSAM ESDS has failed. rr is the return code in decimal, and
ff is the feedback code in decimal.

10.4
IPF203E VSAM ESDS File close error, Return: rr Feedback: ff DLBL: name
(Important) A close request for a VSAM ESDS has failed. rr is the return code in decimal, and
IPF204E VSAM ESDS File read error, Return: rr Feedback: ff DLBL: name
(Important) A read request for a VSAM ESDS has failed. rr is the return code in decimal, and ff
is the feedback code in decimal.
IPF205E VSAM ESDS File write error, Return: rr Feedback: ff DLBL: name
(Important) A write request for a VSAM ESDS has failed. rr is the return code in decimal, and
IPF207I VSAM ESDS record count of DLBL: aaa is bbb
(Info) This message is produced following processing of a file specified by DLBL name.
IPF212E loc GETVIS shortage, driver, task, length bytes.
(Vital) During normal processing, a File I/O driver was unable to obtain needed storage. The
message will indicate the RMODE of the required storage, the driver making the request, and
the size of the contiguous storage needed.
System Action: The process requiring the storage is failed, the requesting program is notified,
and processing continues with other work.
Operator Action: Examine other console messages to determine why there is a GETVIS
shortage. You may want to use the QUERY STORAGE command.
IPF213E Invalid driver type request. Addr: addr, Length: len
(Vital) An invalid File I/O request has been detected. This message shows which driver, the
type of request, the address of the data buffer (hexadecimal), and the buffer length (decimal).
System Action: The requesting program is notified of the failure, and processing continues.
Operator Action: Examine the console for additional messages from the program that made
the failing request.

10.5
IPF214E block is invalid. diagnostic data
(Vital) During File I/O processing, a driver program encountered an invalid control block. The
message will provide the name of the control block, the type of driver, the operation being
processed, and additional information.
Operator Action: Examine the console for additional messages. This error may indicate that a
general corruption of storage has occurred. It may be necessary to cycle the file I/O driver
program or the TCP/IP partition to recover.
Administrator Action: This message is followed by a dump of the failing control block. Please
have this dump available when calling CSI Technical Support.
IPF302E VSAM KSDS File type error, Return: rr Feedback: ff DLBL: name
(Important) An error has occurred while processing A request of type against a KSDS. In the
message, rr is the decimal return code, and ff is the decimal feedback code.
IPF306W VSAM KSDS File duplicate key write failed DLBL: name
(Warning) A write request for a VSAM KSDS has failed because the a record with a duplicate
key already exists. rr is the return code in decimal, and ff is the feedback code in decimal.
IPF307I VSAM KSDS File Switching from Skip Sequential to Direct. DLBL: name
(Info) While writing records to a KSDS, it was found that the keys were not in ascending
collating sequence (as understood by VSAM). TCP/IP FOR VSE switches to direct mode and
continues in a less efficient manner.
IPF308E VSAM KSDS File switching error, Return: rr Feedback: ff. DLBL: name
(Vital) TCP/IP FOR VSE was unable to switch from skip sequential to direct mode for the
indicated dataset. The decimal return code is rr. The decimal feedback code is shown as ff.
IPF309I problem description
(Important) Following a failed VSAM access request, a return code and reason code
combination are displayed. This message will provide a detailed description of the problem,
based on the description provided by IBM.
Operator Action: Determine the reason for the error and correct it.

10.6
IPF352E Member Open Failure, Lib:aa Sub:bb Mem:dd Type:ee
(Important) An open-for-output failure has occurred. The message provides information on the
member that was to be written. The open failure is reflected to the requester.
Administrator Action: Ensure that the specified library is not damaged.
IPF355E Member Close Failure, Lib:aa Sub:bb Mem:cc Type:dd
(Important) A CLOSE has failed for the indicated library and member. The failure is not
reflected to the requester.
Administrator Action: Ensure that the library and member are valid.
IPF356E Member Read Failure, Lib:aa Sub:bb Mem:cc Type:dd
(Important) A Librarian READ operation has failed. The library and member are shown in the
message text. The failure is reflected to the requester as an end-of-file.
Administrator Action: Check the library and member for validity.
IPF357E Member Write Failure, Lib:aa Sub:bb Mem:cc Type:dd
(Important) A Librarian WRITE operation has failed. The library and member are shown in the
message text. The failure is reflected to the requester as an error.
Administrator Action: Test the library and member for validity. Ensure that there is sufficient
room.
IPF358E RCode=aa Read=bb (cc)
(Important) Additional information for an open failure has been provided. If the R Code is
greater than 12, then you may also see an additional LIBR-generated message such as L163I.
Administrator Action: Review the IBM System Macros Reference Guide on LIBRM OPEN
to see what the return code information means. A small snap dump of a TCP/IP control block is
also produced to allow CSI Technical Support to debug the problem with you if you need
further assistance.
IPF361E Phase I/O is not supported
(Info) An attempt was made to process a VSE library “*.PHASE” member. This feature is
currently not available.
Operator Action: Use an alternate method to process LIBR phase members.
Administrator Action: The process is terminated.

10.7
IPF362D Access Control failure for existence of lib.sublib
(Diagnose=LIBR) A Librarian operation has failed. The library and member are shown in the
message text. The failure is reflected to the requester as an end-of-file.
Administrator Action: When using sec=yes, rules must be written to allow access.
IPF363D Access Control failure for contents of lib.sublib
(Diagnose=LIBR) A librarian request for the content of a library has failed due to a security
violation. The directory contents of the library will not be displayed.
IPF364D Access control failure for existence of lib.sublib
(Diagnose=LIBR) A librarian request for the content of a library has failed due to a security
violation. The directory contents of the library will not be displayed.
IPF366E I/O module access error: ADDR=x BUFSIZE=x
(Important) A file I/O driver I/O operation has failed because either bad pointer to a buffer or a
bad length for the input or output data occurred.
System Action: Transfer is aborted. A snap dump of the ACBLOK occurs.
IPF367E field= data
(Important) This message is produced following failure of the LIBR request. It displays the
contents of one or more Librarian feedback fields, as labeled.
Administrator Action: Review the IBM System Macros Reference Guide on LIBRM OPEN
to see what the return code information means.
IPF402D POWER process XPCC oper has failed. Codes: rc [feedback]
(Diagnose) The POWER I/O driver failed to communicate with the POWER partition using the
XPCC protocol. The message text indicates the internal process being performed at the time.
oper indicates the XPCC or XPCC/POWER operation being performed. Both return and
feedback codes (in decimal) are shown, as available.
Operator Action: Examine the console log for additional messages, both from TCP/IP and
POWER, that may provide additional information.

10.8
IPF403W Invalid Power job xxxxxxx Reason:yyyyyyyy
(Warning) The POWER I/O driver detected a invalid POWER job name, number, or segment
as indicated in the message.
System Action: Processing continues.
Operator Action: Examine the FTP statement and correct it. The job number should be five or
fewer numeric characters, and the job segment should be three or fewer numeric characters.
IPF404E POWER Open Failure. Code: c FDBK: d Queue: que Class: cl Name: a.b.c
(Important) The POWER I/O driver was unable to open a POWER queue entry. The message
text identifies the POWER queue being accessed, the name of the entry, and the return and
feedback codes from OPEN (see POWER Application Programming: Return and Feedback
Codes).
System Action: Processing continues with other work.
IPF405W JSEP type table (name) not found.
(Warning) The JSEP generator was told to build block letters (table BLOCKLTR) or the
general JSEP form (table JSEPLOOK), but it could not find a specific matching entry.
System Action: The string will be produced, but not in block letters.
Operator Action: Correct the table entry in JSEPLOOK.L, or add the appropriate table in
BLOCKLTR.L. Issue a RELOAD JSEP, and rerun the job.
IPF410E XPCC RC code FDBK code text
(Important) The POWER I/O driver has made a failing XPCC request to POWER. This failure
was reported in a preceding message. The purpose of this message is to provide a text
interpretation of the XPCC return and feedback codes. The return code and feedback values are
shown in decimal.
IPF452I ICCF Library connection established
(Info) After the file I/O driver IPNFICCF has been loaded into TCP/IP partition GETVIS, an
attempt is made to establish a communication session with the ICCF system. If you see this
message, then it means that you can process ICCF datasets.

10.9
IPF453E ICCF Library connection failure. RC=rc
(Important) After the file I/O driver IPNFICCF has been loaded into TCP/IP partition GETVIS,
an attempt is made to establish a communication session with the ICCF system. If you see this
message, then it means that TCP/IP cannot use ICCF members
Administrator Action: Make sure that there is an “// ASSGN SYS010” statement in your JCL
that is invoking the ICCF request. If it exists, then contact CSI Technical Support for further
assistance.
IPF454E ICCF member open failure. RC=rc Mem=membername
(Important) A request was made to get an ICCF member, but the file I/O driver IPNFICCF
failed. This may be the result of a misspelled name, or an incorrect library number was issued.
Administrator Action: Make sure that the ICCF library number is valid, that the member
name is spelled correctly, and that SYS010 is properly assigned to the controlling partition.
IPF455W ICCF library invalid library number: value
(Info) A request was made to get an ICCF member, but the library number, which must be a 1-
to 3-byte numeric value, was either missing or incorrect.
Administrator Action: Correct the value and resubmit the request.
IPF456E ICCF Library member read failure: rcode
(Important) A request was made to read an ICCF member. The OPEN request succeeded, but
the read failed in the middle of an otherwise good I/O request.
Administrator Action: Check the rest of your VSE system to make sure that all of the
necessary system components are active. If the problem continues, contact CSI Technical
Support.
IPF457E ICCF library cannot be written to
(Vital) A request was made to write to the ICCF library, but there is no interface to perform
such A request.
IPF458E ICCF Library GETVIS failure. RC=rc Length=length
(Critical) A request was made to perform ICCF I/O, but the file I/O driver IPNFICCF was
unable to allocate a minimal amount of storage to process the request.
Administrator Action: Free up any TCP/IP FOR VSE GETVIS, or run TCP/IP in a larger
partition. If the problem continues, contact CSI Technical Support.

10.10
IPF459E ICCF member name invalid: name
(Important) A request was made to get an ICCF member, but the member name, which must be
a 1- to 8-byte value, was either missing or invalid.
Administrator Action: Correct the value, and resubmit the request.
IPF501I IDCAMS message
(Info) IDCAMS is being invoked by the VSAMCAT File I/O driver program, and this message
shows the print lines being returned from that utility.
IPF504E IPNFVCAT unable to load IPNAGETM
(Vital) To dynamically create a VSAM cluster, IPNFVCAT needs to use the “Read Library
member” module IPNAGET. During a LOAD request, this processing failed.
System Action: The request to create a VSAM cluster fails.
Operator Action: Determine the reason for a LOAD macro failure, then resubmit the request.
IPF505E GETVIS failed for IPNFVCAT during OPENDIR
(Vital) You are attempting to OPEN an VSAM directory, but there is not enough GETVIS to
process that request.
IPF506E VSAMCAT open error, Return: code Feedback: n DLBL: x
(Important) You are attempting to OPEN an VSAM dataset, but the OPEN ACB request failed.
The return code, feedback code, and the DDNAME of the DLBL are provided in the error
message.
IPF507E VSAMCAT file close error, Return=ReturnCode Feedback=FeedbackCode

DLBL=ddname
(Important) IPNFVCAT attempted to issue a CLOSE on a VSAM file, but it failed. The return
code (R15), the feedback code from the ACBERFLG, and the DDNAME of the file are
displayed.
IPF508E VSAMCAT No associated group was found
(Vital) While reading the VSAM catalog in an attempt to process the directory information, an
anomaly was encountered that may indicate a problem with the catalog.

10.11
IPF509E VSAMCAT No associated data record was found.
IPF510E VSAMCAT No associated index record was found
IPF511E function call to internal routine failed: message-text
(Vital) The file I/O driver attempted to perform a specific function within the driver, calling a
special VSAM routine, but that special routine returned an error.
Operator Action: Contact Technical support.
IPF512E GETLBL failed for DDNAME: xxxxxxx RC=x
(Vital) A LABEL macro GETLBL was issued, but it returned a bad code. As a result, the
desired DLBL was not obtained.
Administrator Action: Contact CSI Technical Support for further assistance and provide all of
the information in this message.
IPF513E VSAM file GETNXGL error, DDNAME=xxxxxxx RC=x
(Vital) A LABEL macro GETLBL was issued, but it returned a bad code. As a result, the
desired DLBL was not obtained.
IPF516I IPNFVCAT: Snap dump of FRBLOK has been produced
(Info) DIAGNOSE FILEIO is in effect, so the VSAMCAT fileIO driver will output the
contents of the FRBLOK on SYSLST on OPEN.
IPF517E VSAM file GETNXGL error. RC=x
(Vital) A LABEL macro GETNXGL was issued, but it returned a bad code. As a result, the
desired DLBL was not processed.

10.12
IPF518E VSAM call label failed during y. RC=x
(Vital) A LABEL macro ended up with a critical error and was not able to perform any DLBL
label processing. The x value is the return code from the LABEL macro, while the y value is the
macro function that was being invoked. The call value is the type of label invocation being
performed.
Administrator Action: Contact CSI Technical Support for further assistance, and provide
them with all of the information in this message.
IPF520E VSAM Catalog DLBL does not exist, DDNAME: xxxxxxx
(Vital) A request was made to delete a file from the VSAM catalog, but there is no DLBL for
the existing catalog in either the system or partition label area. As a result, the delete will fail.
IPF521I IPNFVCAT: Accessing xxx.xxx.xxx....
(Info) DIAGNOSE FILEIO is set, so during OPEN processing IPNFVCAT will display the file
ID of the VSAM file being processed.
IPF522E Unsupported file type requested: xxxx
(Vital) You are attempting to process a type of VSAM cluster that is not supported by the
current IPNFVCAT fileIO driver.
IPF523E CDLOAD failure for IDCAMS, RC=n
(Vital) Certain functions such as DELETE and DEFINE CLUSTER need to pass dynamically
generated IDCAMS parameter “cards” to the IDCAMS program. IPNFVCAT attempted to
issue a LOAD macro against the IDCAMS module, but it failed.
IPF524E Unable to locate FTPMODEL: xxxxxxxx
(Vital) To dynamically create a VSAM cluster, IPNFVCAT needs a model to work from. The
default model name is FTPMODEL. IPNFVCAT was unable to locate the model name
indicated in the message.
IPF526E Dynamic DEFINE CLUSTER failed. Refer to SYSLST
(Vital) IPNFVCAT passed the dynamically generated DEFINE CLUSTER parameters to

IDCAMS. IDCAMS output the request to SYSLST but returned a non-zero return code. If this
was from an FTP request, the IDCAMS output will also be returned to the FTP client as well.

10.13
IPF527E Unable to add partition label. RC=x
(Important) A LABEL macro ADDLBL was issued, but a bad return code occurred, resulting in
the desired DLBL not being added. This modification is important because it was determined
that no label currently exists for the desired file.
IPF528E DLBL modify of DISP=(x,KEEP) failed. RC=x
(Important) A LABEL macro MODGRPL was issued, but a bad return code occurred, resulting
in the desired DLBL not being modified. This modification is important because it was
determined that it needed to switch between NEW and OLD (or OLD and NEW).
IPF529E DLBL replacement failed. RC=x
(Vital) A LABEL macro REPLBL was issued, but a bad return code occurred, resulting in the
desired DLBL not being modified. This modification is important because it was determined
that it needed to switch between NEW and OLD (or OLD and NEW).
IPF530D IPNFVCAT Method=xxxxxx DDNAME=xxxxxxxx
(Diagnose=FILEIO) DIAGNOSE FILEIO is set, and a file is about to be processed in some

way. This message tells you the DDNAME of the file that was used/generated and whether it is
input or output.
IPF531I IPNFVCAT Closing xxx.xxx.xxx...
(Info) DIAGNOSE=FILE is set, or IPNFVCAT is being shut down and it found some left-open
VSAM files. In either case, it will close the file after telling you which file is being closed.
IPF532E IPNFVCAT file read error RC=n FDBK=n DLBL=xxxxxx
(Important) IPNFVCAT attempted to read a VSAM cluster, but the READ failed. The
information displayed is the return code (R15), the feedback code (RPLFDBKC), and the
DDNAME of the file. A snap dump of the RPL will be produced on SYSLST.

10.14
IPF533E IPNFVCAT file write error RC=n FDBK=n DLBL=xxxxxxx
(Important) IPNFVCAT attempted to write to a VSAM cluster, but the WRITE failed. The
information displayed is the return code (R15), the feedback code (RPLFDBKC), and the
DDNAME of the file. A snap dump of the RPL will be produced on SYSLST.
IPF536E Sequence recovery type failed for name : RC=rr FDBK=ff
(Important) TCP/IP for VSE was unable to switch from skip sequential to direct mode for the
indicated dataset. rr is the decimal return code, and ff is the feedback/reason for the failure,
which will be the value in ACBERFLG. This will only occur during a failed CLOSE or re-
OPEN).
IPF537W VSAMCAT Duplicate record, ending write to name
(Warning) A write request for a VSAM KSDS has failed because the a record with a duplicate
key already exists. A snap dump of the problem record will be written to SYSLST.
IPF602E GETVIS failed for IPNFVTOC during OPDIR
(Vital) During the process of reading the VTOC, the file I/O driver needed to allocate storage
for a work area but was unable to do so.
Operator Action: Release system resources ,or reallocate partition GETVIS to the TCP/IP FOR
VSE partition.
IPF603W Unable to action VTOC: volid RC=value
(Warning) The pseudo task responsible for I/O to the VTOC was unable to perform the
necessary action required.
System Action: The process is terminated.
Operator Action: The return code reflects the result from an OVTOC or PVTOC request.
Refer to the IBM manual on these macros to determine the meanings of these codes, or contact
IPF604E IPNFVTOC cannot access VOL4 label
(Vital) The pseudo task responsible for I/O to the VTOC was unable to gain access to the VOL4
VTOC label.
Operator Action: The disk may be corrupted or invalid. Verify that you can process it with the
LVTOC utility. If so, contact CSI Technical Support for more assistance.

10.15
IPF605E Unable to action RC=value Name=volid
(Vital) The pseudo task responsible for I/O to the VTOC was unable to perform the necessary
action required.
Operator Action: The return code reflects the result from an OVTOC or PVTOC request.
Refer to the IBM manual on these macros to determine the meanings of these codes, or contact
IPF701W Unable to load driver: BIUAPMD is not in the SVA
(Warning) The File I/O task was attempting to start the driver that handles BIM-Edit I/O
operations. However, the driver could not find the indicated BIM-Edit interface in the SVA.
System Action: The File I/O driver terminates.
Operator Action: Ensure that the required BIM-Edit phase has been loaded into the SVA. Use
the DEFINE FILEIO command to reload the driver.
If this message appears during TCP/IP partition initialization, it probably means that BIM-Edit
is not installed and the message may safely be ignored.
Administrator Action: Add PARM=NODRIVER to the “// EXEC IPNET” statement, and add
explicit DEFINE FILEIO statements for the drivers required by your installation.
IPF702D Send to BIM-EDIT: string
(Diagnose) The BIM-EDIT file I/O driver is communicating with the BIM-EDIT subsystem
and is sending a command to be processed.
Operator Action: None. To disable this message, issue the command DIAG -LIBRARY.
IPF703E BIM-EDIT access failure. Missing item
(Vital) The BIM-Edit File I/O driver program received a request but was unable to complete it
because information was missing, as indicated in the message text.
System Action: The requesting program is notified of the failure.
Operator Action: Look for additional messages to determine the process that made the faulty
request.

10.16
IPF704D Response from BIM-EDIT: string
(Diagnose) The BIM-EDIT file I/O driver is communicating with the BIM-EDIT subsystem
and is receiving a response to a previously sent command.
Operator Action: None. To disable this message, issue the command DIAG -LIBRARY.
IPF705E BIM-EDIT I/O Failure: Type: type RC: rc User: user
(Vital) While attempting to process a BIM-EDIT library member, the API indicated that the
request failed.
Operator Action: Review the BIM-EDIT API documentation and determine the reason for the
failure. If problems continue, contact CSI Technical Support. The type of API request, the
return code from the API, and the USERID of the session are indicated in the message.
IPF706W Cannot process BIM-EDIT request. BIM-EDIT is down
(Warning) While attempting to process a BIM-EDIT request, the API indicated that BIM-EDIT
is inactive in VSE.
Operator Action: Start the BIM-EDIT interface in another partition.
IPF707W Invalid BIMEOPTN.L parameter found on line nnn
(Warning) While loading the BIM-EDIT default configuration file for TCP/IP, an invalid
parameter was encountered.
System Action: The process continues. The invalid entry is ignored.
Operator Action: Correct the invalid entry. To have the new entry take effect, you will need to
issued the command DELETE FILEIO,ID=IPNFBIME to unload the old options. The new
options will be loaded automatically when a new BIM-EDIT access request from TCP/IP is
issued.
IPF708W Unable to load BIMEOPTN.L config file. Using defaults
(Warning) The BIM-EDIT file I/O driver for TCP/IP attempted to load the default-options file
BIMEOPTN.L. It was unable to load the file for processing.
System Action: The process continues. Default values are used.
Operator Action: Make sure that your BIMEOPTN.L file is in a LIBDEF search chain that the
TCP/IP partition has access to. If you lost your old version, copy one from your installation job.

10.17
IPF709W BIM-EDIT type file is full.
(Warning) The BIMEOPTN.L file was being processed. A very large number of “SET
VSE_TYPE” statements were processed, and there is no room to add any more.
System Action: The process continues. The definition is skipped
Operator Action: Contact CSI Technical Support if you need additional statements.
IPF720E File (name) is neither REXX, nor GREXX. Cannot proceed.
(Vital) A request was made to the REXX/GREXX driver to process a file, but that file is neither
REXX nor GREXX.
System Action: The request is terminated.
Operator Action: This message should not occur and indicates an error internal in the product.
Contact CSI Technical Support.
IPF721E GREXX is not yet supported. Sorry.
(Vital) A request was made to the REXX/GREXX driver to process a file, but REXX/VSE is
not initialized.
Operator Action: Initialize REXX on your VSE system, and rerun the request.
IPF722W GREXX is not yet supported. Sorry.
(Warning) A request was made to the REXX/GREXX driver to process a file, and its type is
GREXX, but GREXX support is not provided.
Operator Action: None.
IPF723E REXX File I/O driver wait expired. Cannot proceed.
(Vital) A request was made to the REXX/GREXX driver to process a REXX program, which
must be single-threaded. After 5 minutes of waiting, the driver decided to terminate the request.
Operator Action: Determine which program caused the long wait in the first place, and correct
the problem or use GREXX. You may rerun the program that failed to wait.

10.18
IPF752E GETVIS failure for VOLLIE during action
(Vital) The I/O driver responsible for I/O to the Vollie libraries was unable to acquire sufficient
storage to serve the request.
System Action: Vollie I/O will terminate. The request will fail.
Operator Action: Check the storage allocations for the partition.
IPF753E text
(Vital) The pseudo task responsible for I/O to the Vollie libraries returned an error from the
Vollie API. The reason for the error is displayed.
System Action: Vollie I/O will terminate. The request will fail.
IPF754D IPNFVOLL DIAG: text
(Diagnose=FILEIO) You have issued DIAGNOSE FILEIO, and this is one of the many
messages that will be output as part of the TCP/IP diagnostic process.
Operator Action: This message can be eliminated by the command DIAGNOSE -FILEIO.
IPF755E Unable to find DLBL for ddname
(Important) A request was made to use the Vollie file I/O driver, but no DLBL was found for it
that matches your DEFINE FILE.
System Action: Check your DEFINE FILE and your TCP/IP startup JCL to make sure that the
DEFINE FILE DLBL name matches the one in the TCP/IP startup.
IPF756E IPNFVOLL was not properly link-edited.
(Vital) The I/O driver responsible for I/O to the Vollie libraries was not installed properly. This
means that when it was link-edited, the LIBDEF did not include the CA libraries where the CA-
Vollie product resides, and thus it was unable to find the required Vollie routines to link-edit.
System Action: Vollie Initialization within TCP/IP will terminate.
Operator Action: Relink the IPNFVOLL module, including the TCP/IP FOR VSE as well as
the Vollie libraries in the JCL. Ensure that the JCL includes the modules in the following order
as part of your link-edit: IPNFVOLL, VIPCTRL, VIPDOS, OLL6002, and OLL6003.

10.19
IPF802E Unable to locate active connection for xxxxxxxx
(Vital) A CAF-CGI request has been made by a Web client. However, the public name for the
CAF system passed to the CAF fileIO driver does not match any public name built by TCP/IP
FOR VSE by the DEFINE CAF command.
Administrator Action: Either issue a DEFINE CAF command to TCP/IP FOR VSE to build a
definition with the correct name, or modify the Web page that is passing an invalid CAF system
name.
IPF803E CICS connection not active for CAF xxxxxxxx
(Vital) A CAF-CGI request has been made by a Web client. And while the public name for the
CAF system passed to the CAF fileIO driver is correct, it could not find a DEFINE CGI that
was a CGI-CAF type.
Administrator Action: Either issue a DEFINE CGI command to TCP/IP for VSE to build a
definition with the correct name, or modify the Web page that is passing an invalid CGI name.
IPF804E Unable to locate CICS program xxxx for CAF xxxx
(Vital) A CAF-CGI request has been made by a Web client. And while the public name for the
CAF system passed to the CAF fileIO driver is correct, it could not find a DEFINE CGI that
was both a CGI-CAF type as well as had a CAFID that matched the CAFID that was passed as
part of the web browser request.
Administrator Action: Either issue a DEFINE CGI command to TCP/IP for VSE to build a
definition with the correct name, or modify the Web page that is passing an invalid CGI name.
IPF806D EOF condition occurred from CICS
(Diagnose=CAF) The CICS portion of CAF has completed, passing control back to the TCP/IP
stack, and indicating that there is no more data to return.
This message will only display if DIAGNOSE CAF is enabled.
Operator Action: None. Informational only.
IPF807D Pulling data off the CICS stack
(Diagnose=CAF) A CAF-CGI request is being processed, issuing a READ request to the CICS
interface. This message will be issued only if DIAGNOSE CAF is enabled.
IPF808D Retrieved nnn bytes from CICS
stack. This message tells you the total number of bytes that have returned. This message will be
issued only if DIAGNOSE CAF is enabled.

10.20
IPF809D CICS returned a BAD response
stack. However, the return code indicated that there was a problem with the formatted request
passed to it by the TCP/IP stack. This indicates an internal problem.
System Action: No data is returned to the client.
Operator Action: If this problem repeats, then contact CSI Technical Support.
IPF810W CICS returned a failure condition
(Warning) The CICS portion of CAF has completed, passing control back to the TCP/IP stack.
However, the return code was not EOF, GOOD, or BAD, which means that there was a possible
problem at the CICS side, such as a CGI abending under CICS.
System Action: If data were returned, the data will be sent to the initiating client.
Operator Action: None. However, if the CGI continues to fail, you will want to review the
CICS message area to determine the problem.
IPF811W Ending transfer due to transfer length
(Warning) The CICS portion of CAF has completed, passing control back to the TCP/IP stack.
However, the returned length of data was either a non-positive value or greater than 20k, which
is not acceptable.
System Action: No data is passed back to the client.
Operator Action: Review the logic of the CGI.
IPF813E Unable to acquire GETVIS for CAF session
(Vital) A CAF-CGI request has been made by a Web client. However, the TCP/IP partition was
unable to acquire the requisite amount of 24-bit GETVIS to start a session with CICS.
Administrator Action: Reduce the 24-bit GETVIS used in the TCP/IP partition or wait until
resources have been released and try again later on.
IPF814D Telling CICS to start the CAF CGI: xxxxxxxx
(Diagnose=CAF) A CAF-CGI request has been made by a Web client. The TCP/IP interface is
about to tell CICS to start the CGI for processing. This message is only displayed when
DIAGNOSE CAF is enabled.

10.21
IPF815D CICS has acknowledged the request
(Diagnose=CAF) A CAF-CGI request has been made by a Web client. The TCP/IP interface
has told CICS to start the CGI. CICS has responded that the CGI has been started. This message
will only display if DIAGNOSE CAF is enabled.
IPF816D Checking to see if program has started
earlier told CICS to start the CGI. TCP/IP is now checking if the program has actually started. It
is possible if CICS is running rather sluggishly for the CGI to still not have started. If this is the
case, then TCP/IP will wait until the CGI has actually started, for a maximum of 2 minutes.
IPF817D The CAF CGI is executing in CICS.
(Diagnose=CAF) A CAF-CGI request has been made by a Web client. The CGI was requested
for CICS execution, and CICS has acknowledged that the program has successfully started.
This message is only produced is DIAGNOSE CAF is enabled.
IPF820D Checking to see if program has ended
earlier told CICS to start the CGI. TCP/IP is now checking if the program has actually
completed, creating dynamic HTML to be returned. If the CGI is not yet done, then TCP/IP will
wait up to 2 minutes for the CGI to complete its task before telling the user that the CGI has
timed out.
IPF822I Passing bytes bytes back to the HTTPD
(Info) A CAF-CGI request has been made by a Web client. The TCP/IP interface earlier
retrieved data from CICS and is now about to pass it back to the HTTP Daemon. The number of
bytes passed to the daemon is indicated in the message. This message is only displayed if
DIAGNOSE CAF is enabled.
IPF823E TCP/IP CGI type (XFBLOK) is corrupted
(Vital) A CAF-CGI request has been made by a Web client. The TCP/IP interface is now
receiving the generated HTML data; however, the header that provides important information
appears to have been overlaid.
Administrator Action: A snap dump of the header is output on SYSLST. If this occurs
repeatedly, contact CSI Technical Support.

10.22
IPF824E TCP/IP CGI ACBLOK is corrupted
(Vital) A CAF-CGI request has been made by a Web client. The TCP/IP interface has received
the data and was trying to release the allocated control block (ACBLOK) but the control block
is not in the expected format, so either a bad pointer entered the file close routine, or storage has
been overlaid. In either case, it’s a bad thing.
Administrator Action: A snap dump of the header is output on SYSLST. If this occurs
repeatedly, contact CSI Technical Support.
IPF827E Unable to locate active connection for CAF type
(Vital) A user attempted to use CAF-FTP, but the TCP/IP partition was unable to communicate
with the CICS partition.
Administrator Action: Ensure that the CICS components to CAF are active. If so, try deleting
and redefining the CAF-FTP system. If you still have a problem, contact CSI Technical
Support.
IPF828W CICS connection not active for CAF nodename
(Warning) A user attempted to use CAF-FTP, but the TCP/IP partition was unable to
communicate with the CICS partition.
Administrator Action: Ensure that the CICS components to CAF are active. If you still have a
problem, contact CSI Technical Support.
IPF829W Unable to open CICS file filename for CAF nodename
(Warning) A user attempted to use CAF-FTP to open a file, but either the file does not really
exist, or the CICS side has denied you access to the file.
Administrator Action: Ensure that the CICS components to CAF are active. Make sure the file
name used is valid. If this is a file-I/O driver and not a real file, make sure that the file I/O driver
is defined to CICS. If you continue to have a problem, contact CSI Technical Support.
IPF830W Cannot connect to CAF - connection busy
(Warning) A request was made to issue a command to CAF. The connection is serial and each
request should only take a couple of seconds, and so your request we put in the queue.
However, a minute has gone by, and still there has been no movement within the queue.
System Action: The request will fail, and you are removed from the queue.
Administrator Action: Check the health of the stack. If there seems to be no other problems,
try deleting and defining CAF-FILE. If the problem persists, contact CSI Technical Support.

10.23
IPF831W Unable to action CAF (FILE). Request failed.
(Warning) A request was made to issue a command to CAF. The file I/O driver tried to perform
the action with CAF, but for some reason, communications failed.
System Action: The request will fail.
Administrator Action: Check the health of the stack. If there seems to be no other problems,
try deleting and defining CAF-FILE. If the problem persists, contact CSI Technical Support.
IPF833D CAF Trace: type Opening a data port
(Diagnose=CAFFTP) DIAGNOSE CAFFTP is enabled, and the file I/O driver is showing
workflow though the routine.
Administrator Action: None. Informational only. This is useful in debugging problems and
passing the information to CSI Technical Support. If you want to suppress the message, use the
command DIAGNOSE -CAFFTP.
IPF839E CAF data port connect timed out during type
(Vital) CAF-FTP connected to the CICS data port and was waiting for an acknowledgment, but
the connection timed out.
Administrator Action: Ensure that IPNX$FILE is up and running on the selected CICS
system. CAF-FTP should recover from this error. If this occurs often, contact CSI Technical
Support.
IPF841E CAF request port timed out during type
(Vital) CAF-FTP connected to the CICS request port and was waiting for a reply, but the
connection timed out.
Administrator Action: Ensure that IPNX$FILE is up and running on the selected CICS
system. CAF-FTP should recover from this error. If this occurs often, contact CSI Technical
Support.
IPF843E CAF data port socket status failed RC=rcode
(Vital) CAF-FTP tried to OPEN a SOCKET as a data port, but the SOCKET STATUS call to
that socket failed.
Administrator Action: Try deleting/defining CAF. If that fails, recycle TCP/IP. If the problem
persists, contact CSI Technical Support.

10.24
IPF845E CAF data socket initialization failure
(Vital) CAF-FTP tried to OPEN a SOCKET as a data port, but failed. IPF843E will indicate the
type of problem.
Administrator Action: Try deleting/defining CAF. If that fails, cycle TCP/IP. If the problem
IPF846E CAF data type process failed
(Vital) CAF-FTP tried to perform some type of SOCKET process, but it failed. The “type”
indicates the type of SOCKET process that was taking place at the time.
Administrator Action: Try deleting/defining CAF. If that fails, cycle TCP/IP. If the problem
IPF901W Unable to load driver: CSIHF00 is not in the SVA
(Warning) The driver phase responsible for HFS I/O was attempting to start. However, a
required module, CSIHF00, is not in the SVA.
Operator Action: Issue a “SET SDL” to load the HFS module into the SVA, and reload the
HFS driver.
If this message appears during TCP/IP partition initialization, it probably means that HFS is not
installed, and the message may safely be ignored.
IPF902W Record format xx not valid
(Warning) While attempting to access a HFS file, the record format being requested is invalid.
System Action: The invalid record format is ignored.
Operator Action: Specify RECFM=V on the DEFINE FILE for the HFS file system, or
specify SITE RECFM F or V.
IPF903E GETVIS failed for HFS during process
(Vital) While attempting to access a HFS file, the I/O driver needed to allocate storage for a
work area but was unable to do so.
Operator Action: Release system resources, and retry the failing operation.

10.25
IPF904E HFS function ERROR RC: rc File=file
(Important) The HFS file access routine returned an error indication when requested to perform
the displayed function.
Operator Action: Check the subsequent IPF905I messages for more information, and contact
IPF905I error description
(Info) This message provides additional information for the previously displayed IPF904E or
IPF907W messages.
Operator Action: Check the preceding messages
IPF906E HFS/FTP buffer too small
(Vital) The FTP buffer passed to the HFS I/O driver is too small to contain one directory entry.
IPF907W HFS function WARNING RC: rc File=file> 02401001 t< Warning
(Info) The HFS file access routine returned a warning when requested to perform indicated
function.
System Action: The process continues.
Operator Action: Check the IPF905I messages that follow for more information
IPF908W Unable to load driver: CSIHFACM phase not found
(Warning) The driver phase responsible for HFS I/O was attempting to start. However, a
required module, CSIHFACM, could not be found.
Operator Action: Ensure that CSIHFACM.PHASE is located in the TCP/IP partition’s phase
search chain. Issue a DELETE FILEIO and then a DEFINE FILEIO to retry the initialization.
If this message appears during TCP/IP partition initialization, it probably means that HFS is not
installed, and the message may safely be ignored.

10.26
IPF912W HFS failed: type RC=rcode RS=reason
(Vital) A failure occurred in the HFS file I/O driver. The error codes are unique for debugging.
Administrator Action: Refer to the HFS documentation for information on return code and
reason code values.

10.27

10.28
11
IPI Series Messages
IPI100I IP Processor type starting
(Info) TCP/IP processing is defined as a series of layers. The Internet Protocol (IP) handles the
logical IP datagrams.
Within the TCP/IP partition, a variety of processors are used to perform the various tasks for
handling the data at the IP level. This message indicates a particular processor is starting to
execute.
IPI101I IP Processor type stopping
(Info) TCP/IP processing is defined as a series of layers. The Internet Protocol (IP) handles the
logical IP datagrams.
handling the data at the IP level.
This message indicates a particular processor is terminating its processing.
Operator Action: This message should only occur during shutdown of the TCP/IP partition. If
it is seen at any other time, it will probably be necessary to stop and restart TCP/IP.
IPI103D Logical datagram length (nn) exceeds physical size (nn). Source: ipaddr
(Diagnose=REJLENGTH) The IP length field of a datagram specifies a value that exceeds the
datagram’s physical length. In the message text you will find the declared datagram length and
the physical packet length. These values are in decimal. The source IP address of the sender is
also displayed.
System Action: The datagram is discarded without further processing.
Operator Action: This message may be eliminated by issuing the DIAGNOSE -REJLENGTH
command. These message will automatically stop after 10 displays.

11.1
TCP-IP FOR VSE 1.5F Messages IPI Series Messages
Administrator Action: This problem can occur in a variety of situations, and it is difficult to
specifically identify what could cause this without examining the diagnostics.
Within a token-ring environment, it is possible for a datagram that is too large to pass through
the adjacent token-ring segment to be truncated instead of being discarded by the associated
bridge or card. If this is suspected, then the size of the inbound datagram can be reduced by
including a ROUTE statement that forces a smaller-than-normal Maximum Segment Size
(MSS) for messages transmitted over the suspect path.
IPI105D Misrouted Datagram. From source ip intended for dest ip
(Diagnose=MISROUT) A datagram has arrived but was not intended for us. GATEWAY is off.
Operator Action: This message and dump is in response to DIAGNOSE MISROUTE. Only
10 messages and dumps will be produced for each specification of DIAGNOSE MISROUTE.
Administrator Action: Determine why the network is directing unwanted traffic to VSE, and
correct the sender or router causing the problem.
IPI106I Diagnose for type terminated due to count
(Info) In response to a DIAGNOSE command, TCP/IP has been displaying series of diagnostic
messages. When the diagnose was enabled, a limit was set, either explicitly or by default.
This message indicates that the requisite number of diagnostic messages has now been
displayed.
System Action: DIAGNOSE for type has been terminated, and no further diagnostic messages
will be issued.
Operator Action: If additional displays are needed, re-enter the DIAGNOSE command.
IPI107I All traffic with ip will be prevented.
(Response) Issued in response to an ACCESS QUERY command, this message indicates an IP

address currently on the “black list”. Any inbound datagrams from this IP address will simply
be discarded without acknowledgement.
IPI108I Access type complete
(Response) Issued in response to an ACCESS command, this message indicates the successful
completion of the request.

11.2
IPI109E Access type failed. [reason]
(Response) Issued in response to an ACCESS command, this message indicates that the
requested function failed. If no reason is shown, the specified IP address was probably not in
the “prevent” table.
Operator Action: Re-issue the command with corrections.
IPI110I All traffic with address will be status
(Security) The indicated IP address has either been added or removed from the system’s “black
list”. All IP addresses that appear on this list are ignored by TCP/IP. All datagrams arriving
from a “black-listed” address are immediately discarded without acknowledgement.
“Black-listing” is controlled with the operator ACCESS command. Addresses may be

automatically added to the list by TCP/IP when hacking behavior is detected, or when the
Security Exit requests it.
Operator Action: The indicated address should be evaluated for its importance and risk. If the
address is legitimate, it may be appropriate to re-enable its access.
Administrator Action: Automatic suspension of an address is triggered by several criteria, one

of which is receipt of a datagram known to be injurious to other platforms (for example, Linux).
Although such commands would have no effect on a VSE-based system, you should be alert to
the possibility that other, more vulnerable hosts on your network have already been
compromised.
IPI120D IP checksum invalid. header
(Diagnose) TCP/IP’s checksum validation routine has determined that an inbound datagram
was corrupted in transit.
The invalid IP header, as received, is displayed.
System Action: The datagram is discarded, in accordance with the TCP/IP standards RFC.
Operator Action: Generally, none.
Administrator Action: Although checksum problems can be caused by loose or defective

cables and electrical interference, these are normally recovered by automatic retransmission
attempts. More serious causes are improper construction of checksums by the originating host
(rare) and improper modification of the datagrams while they are in transit.
IPI302D Input IP Request has been Received
(Diagnose=DEBUG) An incoming datagram has arrived for processing by the IP task.

11.3
IPI303D Unsupported IP protocol. From addr. Type: type
(Diagnose=REJPROT) A datagram has arrived that specifies an unsupported protocol.
Operator Action: This message and dump is in response to DIAGNOSE MISROUTE. Only
10 messages and dumps will be produced for each specification of DIAGNOSE MISROUTE.
Administrator Action: Determine why the network is directing unwanted traffic to VSE, and
adjust the sender or router causing the problem.
IPI402D Output IP Request has been Received
(Diagnose=DEBUG) A datagram fragment has arrived in the IP output task.
IPI403D diagnostic text
(Diagnose=ROUTING) This message is issued when DIAGNOSE ROUTING is in effect and

contains information useful in determining why outbound datagrams are not being sent to the
proper destination.
IPI502D Cleanup: text
(Diagnose=CLEANUP) This message is issued in response to the DIAGNOSE CLEANUP

command. The text portion will explain the operation of TCP/IP cleanup processing as it
proceeds.
Operator Action: This message may be eliminated by issuing the DIAGNOSE -CLEANUP
command.
IPI504W TCP/IP connection severed from partition, phase Port port
(Info) The indicated external partition and phase had an open TCP/IP connection. However, the
phase ended without closing the connection, which has now been severed.
Operator Action: Ensure that the indicated application processed correctly.
Administrator Action: Ensure that your applications properly close their TCP/IP connections
prior to terminating.

11.4
IPI505W VSAM Open File ddname not matched with file system
(Warning) If a TCP/IP connection is prematurely severed, then it is possible that a VSAM file
may inadvertently be left open due to a cancelled application. If the option to check for these
wayward opens is enabled using “OPENCHECK=ON”, then TCP/IP will dump the ACB for
any file that might be problem later on.
Operator Action: None. However, you might want to check the output to prevent problems
with batch processing later on. You can use the CLOSE command to close the ACB.
IPI506I Unable to locate COMREG for partid: address
(Info) TCP/IP has found an in-flight socket transaction (issued externally to the TCP/IP
partition) whose COMREG address is no longer PFIXED in storage.
This indicates that the task issuing the socket request is no longer active.
System Action: The transaction is invalidated and its associated storage is released. This
message is followed by IPI504I.
Operator Action: Check the system log for indications that an application has failed to
complete normally.
Administrator Action: Ensure that applications wait for all socket requests to complete before
terminating.
IPI507I Phase name in partid was pname1 and not pname2
partition) whose currently executing phase does not match that of the phase that issued the
socket request.
The message shows both the issuing phase name and the name of the phase now occupying the
partition.
System Action: The transaction is invalidated and its associated storage is released. This
Operator Action: This typically means that the original program crashed or terminated without
closing the SOCKET and another program is currently executing in that partition. Check the
system log for signs of an application terminating abnormally.
terminating.

11.5
IPI508I Job start time in partid was time1 and not time2
partition) whose currently executing job has a job-start time that does not match that of the job
issuing the socket request.
The message shows both the expected job-start time and the job-start time found in the
partition.
System Action: The transaction is invalidated, and its associated storage is released. This
Operator Action: This typically means that the original program crashed or terminated without
closing the SOCKET, and another program is currently executing in that partition. Check the
system log for signs of an application terminating abnormally.
terminating.
IPI514D aa bb-bit GETVIS nn%-used nnnnK-used nnnnK-free
(Diagnose=CLEANUP) This message is issued when DIAGNOSE CLEANUP is active and

when the total partition GETVIS used has increased.
Operator Action: This message may be eliminated by issuing the DIAGNOSE -CLEANUP
command.
IPI515I TCP/IP Stack QUIESCE progress
(Info) This message indicates that a series of status messages regarding the progress of a
QUIESCE ON command will follow.
These status displays will continue until all TCP/IP processing completes, or the QUIESCE
state is canceled (QUIESCE OFF).
IPI516I count connections active on port num
(Info) This message is part of a status display that is produced at regular intervals during
QUIESCE processing until all TCP/IP processing has completed.
Each message contains a count of currently active connections on a particular local port.
Operator Action: If progress toward a quiesced state is slowed or stopped, it may indicate a
stalled connection or an application that normally maintains an active connection.

11.6
IPI517I TCP/IP processing has been quiesced
(Info) This message is produced periodically when a QUIESCE has been requested and all
active connections have been closed.
This message also indicates that no new connections are possible until a QUIESCE OFF
command is issued.
IPI602D Prepare 1 Request has been Received
(Diagnose=DEBUG) A datagram has arrived in the Prepare 1 task for routing.
IPI702D Prepare 2 Request has been Received
(Diagnose=DEBUG) A datagram has arrived in the Prepare 2 task for possible fragmenting.
command.
(Diagnose=FRAG) This message is issued when DIAGNOSE FRAG is in effect. The

diagnostic text can be useful when dealing with problems involving datagram fragmentation.
Operator Action: This message may be eliminated by issuing the DIAGNOSE -FRAG
command.
IPI803W MAC for ip Changed from mac to mac
(Warning,Security) The device (on the local network) with the indicated IP address has
indicated that its hardware MAC address has changed. The text shows both the old and new
values.
This happens rarely and only if the remote host’s hardware is changed, or if the IP address is
reassigned to a different host.
This can also indicate an attempt to redirect network traffic to an unintended recipient where it
can be read or modified.
The most likely cause is a single IP address assigned to multiple hosts.
System Action: TCP/IP notes the change and continues processing with the updated MAC
address.
Operator Action: Ensure that the intended host IP address matches the MAC address of the
host’s adapter card. Notify your Security Manager.

11.7
(Diagnose=ARP) This message is issued when DIAGNOSE ARP is in effect and contains
information useful in diagnosing problem with ARP.

11.8
12
IPL Series Messages
IPL121D diagnostic text
(Diagnose=LINK) This message displays diagnostic information to allow workflow tracing.

The message will be self-explanatory or of interest to CSI Technical Support.
Operator Action: To eliminate this message, issue the DIAGNOSE -LINK command.
IPL124E Unable to Initialize IPNET
(Vital) The IPNET link driver failed to initialize. The system will retry the initialization until it
succeeds.
Operator Action: Examine the log for additional messages that may give clues to the failure.
IPL125E Contact made, but Connection failed, code dec
(Vital) Although the IPNET link driver found the target TCP/IP FOR VSE partition, it was
unable to connect to it. The driver will retry the connection until it succeeds.
IPL126E Unable to Establish Connection, code dec
(Vital) The IPNET link driver could not contact the target TCP/IP FOR VSE partition. The
driver will retry the connection until it succeeds.
IPL127E Contact Made, but close failed
(Important) During shutdown, the IPNET link driver was unable to get the target TCP/IP FOR
VSE partition to response to a close request. Shutdown continues.

12.1
TCP-IP FOR VSE 1.5F Messages IPL Series Messages
IPL128E Unable to Close Connection
(Important) During shutdown, the IPNET link driver was unable to close the connection with
the target TCP/IP FOR VSE partition. Shutdown continues.
IPL130I Link Level RAW Retransmitting, due to packet loss
(Info) The IPNET link driver attempted to transmit a datagram, but it timed-out.
System Action: Transmission will be re-attempted.
IPL241D Diagnostic text
(Diagnose=CETI) This message is produced when DIAGNOSE CETI is in effect. The message
text will be self-explanatory or of interest to CSI Technical Support.
Operator Action: To eliminate this message, issue the DIAGNOSE -CETI command
IPL242E I/O Error occurred on type device; Cuu: dvc Sns: sense
(Critical) The CETI driver encountered an error on the device being used for the purpose
indicated by type. The message includes the device address (dvc) and the sense bytes (sense) in
hexadecimal.
System Action: The CETI driver terminates.
Operator Action: Examine the sense data, correct the problem with the device, and restart the
driver.
IPL246D Link Level 802.3 Request has been received
(Diagnose=DEBUG) The device link has been successfully enabled and has received its initial
inbound interrupt.
IPL249E Unable to Initialize type
(Critical) The indicated device driver has failed to initialize. Traffic over the associated link
will not be processed.
Administrator Action: Correct any hardware errors and restart the link.

12.2
IPL250E Unable to verify type Device Assignment; Cuu: device
(Critical) A device to be used for network interface communication is not assigned to the TCP/
IP partition. In the message text, type indicates how the particular device will be used, and
device is the address of the device in question.
System Action: The device driver shuts down.
Operator Action: Assign the device to the TCP/IP partition, and restart the driver.
IPL254E No Attention Space on Interrupt Port
(Critical) The CETI interface driver has no more interrupt space in its internal table. The driver
terminates.
Administrator Action: Check your configuration for errors, and restart the driver. If the
condition persists, contact CSI Technical Support.
IPL255E Proper Query was not Received: Failure
(Critical) During CETI interface initialization, the proper handshake was not received.
System Action: The link driver terminates.
Operator Action: Check the CETI adapter and its configuration, and then restart the link.
IPL256E Unable to PFIX necessary storage
(Critical) The CETI interface driver could not obtain enough fixed storage for CCW operations.
System Action: The link driver terminates.
Administrator Action: Increase the amount of storage that TCP/IP FOR VSE may PFIX, and
cycle TCP/IP FOR VSE.
IPL258I type LAN Started on 00:00:00:00:00:00
(Info) A CETI interface LAN driver has initialized for the indicated protocol and is
communicating on the LAN using the displayed MAC address.
IPL279W Bad Status Code code for message type message type
(Warning) If you have “SET FULL_CETIERROR=ON” in the TCP/IP initialization, the CETI
device driver will check every inbound datagram status code before proceeding on. If the code
is not good, then that datagram will be dumped to SYSLST, and this message will be displayed.
Operator Action: None. But, you may want to review the SYSLST output. If this happens a
lot, consider doing some hardware diagnostics.

12.3
IPL280E CLAW: Unable to verify device assignment, CUU: cuu
(Critical) The device that you specified for the CLAW interface (cuu) has not been assigned.
Administrator Action: Check the device assignment and redefine the link.
IPL281E CLAW: GETVIS failed. RC: nn Length: ll bytes.
(Critical) During CLAW link initialization, a GETVIS failed. nn is the return code from
GETVIS, and ll is the storage length being requested.
Administrator Action: Ensure that the TCP/IP FOR VSE partition is large enough and that the
parameters specified in the DEFINE LINK command for the CLAW are reasonable.
IPL282E CLAW: PFIX failed. RC: nn Addresses: start-end
(Critical) During CLAW link initialization, a PFIX failed. nn is the return code from PFIX, and
start-end is address range of the storage being fixed.
Administrator Action: Increase the allowed PFIX value for the partition or decrease the
number/size of buffers to be allocated for the CLAW link.
IPL283E CLAW: Write error during initialization.
(Critical) During CLAW link initialization, a write to the CLAW failed. CLAW initialization is
abandoned.
Administrator Action: Look for other console messages that may have a bearing on the
problem. Check the console of the attached device for errors. This may be caused by a reversal
of the even/odd address pair assigned to the device.
IPL284E CLAW: Read error during initialization.
(Critical) During CLAW link initialization, a read from the CLAW failed. CLAW initialization
is abandoned.
Administrator Action: Look for other console messages that may have bearing on the
problem. Check the console of the attached device for errors. This may be caused by a reversal
of the even/odd address pair assigned to the device.
IPL285W CLAW: Flushing data. Link nn
(Important) During CLAW link initialization, unexpected data was received from the interface.
This data is discarded. In the message, nn is the logical link number over which the data was
transmitted.

12.4
IPL286W CLAW: System Validate returned nn
(Important) During CLAW link initialization, the System Validate request returned a non-zero
code (nn). This message will be followed by additional messages, depending on the value of nn.
IPL287W CLAW: Workstation name changed to xxx
(Important) During CLAW link initialization, the System Validate request was rejected due to
an invalid workstation name. TCP/IP FOR VSE will re-issue the request with workstation name
xxx.
Administrator Action: Determine the correct workstation name and include the value in the
DEFINE LINK command.
IPL288W CLAW: Host name changed to xxx
(Important) During CLAW link initialization, the System Validate request was rejected due to
an invalid host name. TCP/IP FOR VSE will re-issue the request with host name xxx.
Administrator Action: Determine the correct host name and include the value in the DEFINE
LINK command.
IPL289E CLAW: Software version incompatible
(Critical) During CLAW link initialization, the System Validate request was rejected due to an
invalid software version. Initialization is abandoned.
Administrator Action: Ensure that the workstation is not running back-leveled software.
IPL290W CLAW: Receive buffer factor reset to nn
(Important) During CLAW link initialization, the System Validate request was rejected because
TCP/IP FOR VSE’s receive buffer is too small. The request will be re-issued with the indicated
buffering factor, nn.
Administrator Action: Enter the indicated value as the read buffering factor on the DEFINE
LINK command.
IPL291W CLAW: Invalid response to connection request nn
(Important) During CLAW link initialization, the connection request returned an invalid code
(nn). TCP/IP for VSE waits for a response with a recognizable code.
Administrator Action: Consult the CLAW and the workstation’s documentation for the
meaning of the unrecognized code.

12.5
IPL292W CLAW: Data received on invalid link: nn
(Important) A transmission has been received from the CLAW that arrived on a logical channel
that is not assigned. The data is discarded.
Administrator Action: Check the workstation's configuration to ensure that it is not expecting
additional functions to be available on other logical channels.
IPL293W CLAW: Interface terminating due to system request
(Vital) Errors of a serious nature have occurred and the link is being terminated.
Administrator Action: Examine other messages for information on the condition that caused
the termination.
IPL294I CLAW: Initialization failed. Interface will retry in nn seconds
(Important) TCP/IP FOR VSE encountered errors during initialization of the CLAW interface.
These errors may to be transitory. Following nn seconds, initialization will automatically be
retried.
IPL295D CLAW: DEBUG diagnostic text
(Diagnose=LINK) This message is produced in response to the DIAGNOSE LINK command.

The text provides information on workflow passing through the CLAW link driver.
The message text will be self-explanatory or of interest to CSI Technical Support.
Operator Action: This message can be eliminated by using the DIAGNOSE -LINK command.
IPL296W CLAW: No room in appendage table
(Critical) During CLAW link initialization TCP/IP FOR VSE was unable to make an entry in its
internal appendage table.
Administrator Action: Try cycling the product, especially if other errors occurred prior to this
one. Contact CSI Technical Support.
IPL297W CLAW: Read operation has timed-out
(Critical) During CLAW link initialization, a read operation has not completed in a reasonable
period of time. Initialization is abandoned.
Administrator Action: Ensure that the workstation is not in a halted state. Retry the
initialization.

12.6
IPL298W CLAW: Write operation has timed-out
(Critical) During CLAW link initialization, a write operation was timed-out by the channel.
Initialization is abandoned.
Administrator Action: Ensure that the workstation is not in a halted state. Retry the
initialization.
IPL299W CLAW: I/O Failure. CCB follows addr
(Critical) During operation and I/O failed. In the message, addr is the address of the CCB
associated with the failing operation. This message is followed by IPL300W.
Administrator Action: Examine the messages that follow for information on the cause of the
I/O error.
IPL300W CLAW: text
(Critical) This message follows IPL299W and displays the contents of a CCB.
IPL301W CLAW: Failing CCWs follow
(Critical) This message is issued following an I/O error. It is followed by a series of IPL302W
messages that will contain the CCWs in the failing chain.
Administrator Action: Examine the CCWs and the associated CCB to determine the problem.
IPL302W CLAW: vaddr raddr ccw ccw
(Critical) This message follows IPL301W and displays the contents of a CCW. vaddr is the
CCW’s virtual address, raddr is the CCW’s real address, and ccw is the contents of the CCW.
IPL307W CLAW: Write I/O error. Will be retried.
(Info) An I/O error has occurred during a write operation. The operation is still potentially
viable and will be retried.
Administrator Action: Examine accompanying messages for clues to the problem.
IPL308W CLAW: Permanent write I/O error. Driver will terminate
(Critical) An I/O error has occurred during a write operation. The operation cannot be retried.
The link shuts down.
Administrator Action: Examine accompanying messages for clues to the problem. Restart the
link.

12.7
IPL309W CLAW: Read I/O error. Will be retried.
(Important) An I/O error has occurred during a read operation. The operation is still potentially
viable and will be retried.
Administrator Action: Examine accompanying messages for clues to the problem.
IPL310W CLAW: Permanent read I/O error. Driver will terminate
(Critical) An I/O error has occurred during a read operation. The operation cannot be retried.
The link shuts down.
Administrator Action: Examine accompanying messages for clues to the problem. Restart the
link.
IPL311I CLAW: Statistics Interval: hh hr, mm min, ss sec
(Response) Issued in response to a QUERY STATS,LINKID= command, this message

indicates the length of the statistics interval.
IPL312I CLAW: Inbound Recs: rr (xx/sec) Bytes: bb (yy/sec)
(Response) Issued in response to a QUERY STATS,LINKID= command, this summarizes the

total amount of records and data inbound from the workstation during the previous interval, as
specified in message IPL311I.
IPL313I CLAW: Outbound Recs: rr (xx/sec) Bytes: bb (yy/sec)

total amount of records and data outbound to the workstation during the previous interval, as
specified in message IPL311I.
IPL314I CLAW: Outbound Normal Recs: rr (xx/sec) Bytes: bb (yy/sec)

total amount of normal records and data outbound to the workstation during the previous
interval, as specified in message IPL311I. “Normal” records are those that are not being
retransmitted for any reason.
IPL315I CLAW: Outbound Retran Recs: rr (xx/sec) Bytes: bb (yy/sec)

total amount of records and data being retransmitted to the workstation during the previous
interval, as specified in message IPL311I. Records are retransmitted because the remote host
(not the workstation) failed to acknowledge receipt.

12.8
IPL316I CLAW: Outbound Overrun Recs: rr (xx/sec) Bytes: bb (yy/sec)

amount of records and data being retransmitted due to overrun of the workstation during the
previous interval, as specified in message IPL311I. The rules of TCP/IP require that the
workstation (as a gateway) must immediately transmit each record or discard it. Records may
not be queued.
Administrator Action: If this value becomes large, reduce the outbound buffering factor to
slow transmission to the workstation.
IPL317I CLAW: Outbound Recs Normal: nn% Retran: rr% Overrun: oo%
(Response) Issued in response to a QUERY STATS,LINKID= command, this summarizes

outbound records as percent of category.
IPL318I CLAW: Outbound Bytes Normal: nn% Retran: rr% Overrun: oo%
(Response) Issued in response to a QUERY STATS,LINKID= command, this summarizes

outbound data as percent of category.
IPL319I CLAW: Statistical counters reset
(Response) The statistical counters referenced in messages IPL311I through IPL318I have been
reset.
IPL381D CTCA: id diagnostic text
(Diagnose=LINK) This message is produced in response to a DIAGNOSE LINK command. It

allows tracing workflow through the CTCA link driver. The message text will be self-
explanatory or of interest to CSI Technical Support.
Operator Action: This message can be eliminated by issuing DIAGNOSE -LINK command.
IPL382E id I/O error receiving data from CTCA. Cuu: a Sns: b
(Critical) An error has occurred while receiving data over a CTC. The unit address and sense
information is also shown. The link is closed.
Administrator Action: Examine the sense data and correct the CTC problem. Restart the link.
IPL384E id I/O error sending data to CTCA. Cuu: a Sns: b
(Critical) An error has occurred while sending data over a CTC. The unit address and sense
information is also shown. The link is closed.
Administrator Action: Examine the sense data and correct the CTC problem. Restart the link.

12.9
IPL388E id CTC Adapter is not in proper state
(Critical) The CTC link level driver has found the CTC to be in an improper state. The link
driver terminates.
Administrator Action: Ensure that the CTC is properly configured and initialized. Restart the
driver.
IPL391E id Unable to Initialize CTC Adapter
(Critical) The link driver for CTC connections could not initialize. The CTC link is not
available.
Administrator Action: Check the console log for other messages. Correct and errors and
restart the link.
IPL392E id Unable to verify device assignment. Cuu: unit
(Critical) The link driver determined that the specified CTC was not assigned to the TCP/IP
FOR VSE partition. The driver terminates.
Operator Action: Assign the CTC adapter and restart the link.
IPL395E id SENSEID I/O error on dir Port. Cuu: a Sns: b
(Critical) The CTC link driver encountered an I/O error during a SENSEID operation on an
indicated port. The unit address and sense information are shown.
System Action: The driver shuts down.
Operator Action: Examine the sense information to determine the problem. Correct the error
and restart the link.
IPL398E id Unable to fix required storage
(Critical) The indicated link driver could not PFIX sufficient storage for channel programs and
buffers.
Operator Action: Increase the amount of storage that the TCP/IP FOR VSE partition can PFIX,
and restart TCP/IP FOR VSE.
IPL399E id Unable to obtain sufficient 24-bit storage.
(Critical) The indicated link driver could not obtain enough 24-bit partition GETVIS to
complete initialization.
Operator Action: Increase the amount of storage available to the TCP/IP partition, or
eliminate some processes that compete for storage and restart the link.

12.10
IPL402D diagnostic text
(Diagnose=LINK) An 802.2 driver task is issuing a message to allow the tracing of work flow
through the system.
The message text should be self-explanatory or is of interest to CSI Technical Support.
Operator Action: This message can be eliminated by issuing the DIAGNOSE -LINK
command.
IPL463I type link linkid Adapter num initiated STOPLAN
(Vital) The OSA device has sent a STOPLAN command to the link driver.
Through a process of trial and error, CSI has surmised that the STOPLAN command is being
used for flow control. When earlier versions of the adapter experienced a buffer overrun (too
much input), they would simply quit passing inbound data. No error condition was raised, and
outbound data continued to flow. In the new scheme, this condition results (apparently) in
paired STOPLAN/STARTLAN commands being sent to the software. Because the lost data is
simply “packet loss,” no further action is needed.
System Action: The link driver will issue a STARTLAN command after 5 seconds if the
adapter does not initiate one. Processing on unaffected adapters continues during this period.
Operator Action: Monitor the system and network to ensure that applications recover from the
delay.
Administrator Action: If this message occurs frequently, contact IBM for hardware support.
IPL465I type link linkid initiated SHUTDOWN
(Vital) The OSA device has sent a SHUTDOWN command to the link driver. CSI has no
information about why the device would initiate such a command, or what it means.
System Action: The link driver shuts down.
Administrator Action: Contact IBM for hardware diagnostics and service.
IPL467I Sense: string
(Important) Following an I/O error, the device driver issued a “Sense” command to retrieve
additional diagnostic data from the failing device. The returned hexadecimal string is returned.
A value of “Unknown” indicates that sense data could not be retrieved.
Operator Action: Capture the sense data for inspection by the hardware support person.

12.11
IPL469E node oper I/O Error. Device: cuu Status: ccdd CSW: status. disp
(Important) An I/O operation has failed to a network adapter. The link ID of the adapter is
shown followed by the failing operation. The device address, channel status (cc), device status
(dd), and CSW status are also show. If appropriate, message IPL467I will follow with the sense
bytes.
The last field indicates the disposition of the failed I/O, either “Retry” or “Failed”.
System Action: If possible, the I/O operation will be retried several times. Otherwise, the
device driver will terminate.
Operator Action: Ensure that virtual devices are correctly configured and that physical devices
are powered-up, accessible, and online before restarting the link driver.
Administrator Action: If I/O errors occur frequently, consult your IBM customer engineer or
other hardware vendor on appropriate diagnostic procedures.
IPL470D linkid diagnostic text
(Diagnose=LINK) This message is issued by the IPNLOSA2 driver phase and contains
diagnostic information CSI Technical Support can use to investigate the problem.
Operator Action: To eliminate the message from SYSLST, issue the DIAGNOSE -LINK
command.
IPL472I linkid Unsupported protocol: type
(Info) While deblocking a inbound buffer, the link driver encountered a transmission protocol
indicator that is not supported. The one-byte hexadecimal protocol type is shown in the
message.
System Action: The unsupported data block is discarded, and processing continues.
Operator Action: If this message occurs frequently and you determine that it is unimportant,
you can suppress its display on the console and on SYSLST.
Administrator Action: Determine what protocol is being presented and whether it can be
suppressed by the adapter hardware.
IPL473I linkid Unsolicited cmd received
(Info) The indicated link driver encountered an inappropriate command in the input buffer. This
command (cmd) should not be issued by the device and was not expected.
System Action: The command is ignored.
Administrator Action: Contact your hardware vendor for information on why the device is
issuing the indicated command and what remedial steps should be taken.

12.12
IPL474I linkid cmd returned code: dec
(Info) The indicated link driver received a non-zero completion code in response to the
command shown in the message text.
System Action: The link driver ignores the return code and continues normal operation.
Operator Action: If network communication appears to be faulty, consider cycling the link
driver or the partition.
Administrator Action: The return codes for most of the commands are not documented by the
hardware vendor. Please contact your vendor directly for an explanation of the codes and what
remedial steps are appropriate.
IPL491I type Link name started [on devices cuu-cuu] [to SYSID nn] [adapter num] [as
addr]
(Vital) The link-driver of the specified type and is now active. The message text identifies the
adapter's physical address and the IP address that TCP/IP will use for this link.
System Action: TCP/IP can begin processing when the first adapter becomes active. However,
processing will be limited until all defined links and adapters have been activated.
Operator Action: Ensure that all required links and adapters are active. This can be done with
the QUERY LINKS command.
IPL602D OSA Express text
(Diagnose=LINK) The OSA Express link driver issues this message to record diagnostic data
for resolving problems.
Operator Action: To eliminate this message, issue the DIAGNOSE -LINK command.
IPL604E Unable to load IJBOSA phase, return code:value
(Critical) The OSA Express link driver requires the IBM phase IJBOSA. The LOAD issued to
obtain that phase has failed with the indicated return code.
Operator Action: Compare the return code to the IBM code for the LOAD macro. Make any
adjustments based on the results.
IPL605E Unable to Initialize IJBOSA, return code:value
(Critical) The OSA Express link driver passed an initialization parameter to the IBM module
IJBOSA, but it returned a non-zero return code. This code is contained in the message text.
Operator Action: Check the hardware and logical connections to the device as well as the
device status. If you still cannot initialize the device, contact CSI Technical Support.

12.13
IPL606E Unable to Start IJBOSA, return code:value
(Critical) The OSA Express link driver passed a request to the IBM module IJBOSA to start the
device, but it returned a non-zero return code. This code is contained in the message text.
device status. If you still cannot start the device, contact CSI Technical Support.
IPL607E Unable to Remove IJBOSA, return code:value
(Critical) The OSA Express link driver passed a request to the IBM module IJBOSA to process
the DELETE LINK request, but it returned an error code. This code is contained in the message
text.
device status. If you still cannot delete the device, contact CSI Technical Support.
IPL609E Unable to initialize OSA Express, Link: LinkName
(Critical) TCP/IP has attempted to process a DEFINE LINK for an OSA Express adapter, but
the initialization process failed.
Operator Action: Review any other messages that appeared before this one, and perform
physical and logical connection resolution.
IPL610E An error has occurred during OSA Express operation, Code: code
(Critical) An attempt was made to enable the interface between VSE and the OSA Express
device, but the operation failed.
System Action: The connection is disabled.
Operator Action: Review the error code and any other messages that may have preceded this
one in order to determine the nature of the problem.
IPL611E Unable to issue PRODID, Code:num
(Critical) The OSA Express link driver needed to issue a PRODID macro to enable/use the
device, but it received a non-zero return code. This code is contained in the message text.
Operator Action: Check any previous messages to determine whether there have been any
failures in any other modules. Also check the amount of available GETVIS. If the problem

12.14
IPL612E Unable to PFIX storage, Code: num
(Critical) The OSA Express link driver needs fixed storage to enable/use the device, but the
PFIX request failed.
Operator Action: Make sure that you have real storage allocated to the TCP/IP partition. Each
OSA Express link will require about 33k of real storage, so make sure that you have allocated
enough.
IPL613I type Statistical Summary for Link id
(Response) This message marks the start of a display of statistical values associated with the
Link Driver of type, identified by the Link ID of id.
IPL614I MTU: size. Interval: duration
(Response) Issued as part of a display of statistical counters, this message identifies the
Maximum Transmission Unit size being used by the Link Driver and the length of time
(hh:mm:ss.mmm) over which the statistics were gathered.
IPL615I variable......value
(Response) Issued as part of a display of statistical counters (QUERY STATS,LINKID= ), this

message shows the current value of the named variable. The variables are as follows:
Variable Description
Received blocks Total receive count
Received bytes Total bytes received
Received bytes, large Total bytes received in datagrams over 576 bytes
Received blocks, large Total received blocks over 576 bytes long
Send bytes Total bytes sent
Send Blocks Total blocks sent
Send, Full block Total times the adapter accepted a block and reported that it had transferred its
buffer
Send, buffered Total times the adapter accepted a block and indicated that it had been buffered
Send, busy Total times the adapter rejected a block because all of its buffers were full. This
count includes all retry attempts.
Send, Max buffer Maximum bytes buffered before the buffer was shipped
Send, clear Total times the buffer was manually cleared
Busy mode Number of times the adapter entered busy mode. This value is incremented each
time a SEND initially fails because the device was busy. These failed attempts
were added to the chain of datagrams awaiting a successful transmission.
Busy mode, longest Largest number of consecutive times the adapter reported busy

12.15

12.16
13
IPN Series Messages
IPN100I TCP/IP Version ver date time, Initializing
(Info) TCP/IP FOR VSE has started its initialization process. This is the first message displayed.
ver is the version number of the product and date & time is the assembly date and time of the
version table.
IPN101I TCP/IP Operating System Interfacing Complete
(Info) TCP/IP FOR VSE has been successfully loaded and is now in control.
IPN102I Copyright years (c) Connectivity Systems Inc.
(Info) This message is the software copyright notice.
IPN103E TCP/IP Unable to initialize
(Critical) TCP/IP FOR VSE is returning control to the operating system after failing to initialize.
This is the final message.
Operator Action: Examine the job output for additional messages detailing problems.
Resubmit the job.

13.1
TCP-IP FOR VSE 1.5F Messages IPN Series Messages
IPN104E Unsupported VSE level vvrrmm
(Critical) TCP/IP FOR VSE is not able to run under this release of VSE.
Operator Action: If TCP/IP FOR VSE has executed on your operating system previously, this
may indicate that damage has occurred to the supervisor and an IPL is required. It may also
indicate that maintenance has been improperly applied to your system. Ensure that your
operating system is supported by TCP/IP FOR VSE. See the TCP/IP FOR VSE Installation Guide
before calling CSI Technical Support.
IPN105E Unable to inquire about the VSE level
(Critical) TCP/IP FOR VSE is not able to determine the release of VSE that you are running. It
uses the SUBSID macro (provided with VSE) to perform this task.
Operator Action: If TCP/IP FOR VSE has executed on your operating system previously, this
may indicate that damage has occurred to the supervisor and an IPL is required. It may also
indicate that maintenance has been improperly applied to your system. Ensure that your
operating system is supported by TCP/IP FOR VSE. See the TCP/IP FOR VSE Installation Guide
before calling CSI Technical Support.
IPN106I Task attach has completed
(Diagnose=DEBUG) This message is issued when processing is complete for the creation of a
task or pseudo task following the issuance of an ATTACH command.
IPN107E Task attach has failed, Phase: aaa Operation: bbb Code: ccc
(Vital) TCP/IP FOR VSE is unable to create a task or a pseudo task in response to the ATTACH
command, issued either explicitly or internally.
Operator Action: Ensure that the requested phase is spelled correctly and resides in a library
that can be accessed by TCP/IP FOR VSE.
IPN108I Initialization has begun
(Info) Control has been passed to the TCP/IP FOR VSE initialization routines. Processing of the
initialization parameters will now begin.
IPN109I Initialization has completed
(Info) TCP/IP FOR VSE has processed all initialization parameters. It will now proceed to the
start-up phase.

13.2
IPN110E Product key validation failed for product
(Critical) TCP/IP FOR VSE was unable to verify your license for the indicated product or
feature.
System Action: Execution continues, if possible, without the indicated product or feature.
Operator Action: Ensure that the PRODKEYS phase is present and in the search chain of the
partition issuing this message. You will need to restart the program to pick up any changes to
the PRODKEYS phase.
Administrator Action: Ensure that the correct license keys have been assembled into your
current PRODKEYS phase.
IPN111I phase version date time [Not loaded]
(Response) Issued in response to a QUERY VERSIONS command, this message indicates the
name of a phase (aaa), its version number (bbb), and the date (ccc) that it was last link-edited.
IPN112E Unable to obtain a free LUB for I/O driver, Cuu: aa
(Critical) TCP/IP FOR VSE failed to dynamically allocate a device at the indicated address due
to a lack of LUBs. Execution continues without the device.
Administrator Action: Increase the number of LUBs available to the partition and IPL.
IPN113E TCP/IP is out of support. Cannot run new service level.
(Info) Your current operating system and TCP/IP FOR VSE/ESA are now out-of-service.
Service level upgrades for your operating system level are not available beyond release 1.5,
service level E.
System Action: TCP/IP terminates.
Operator Action: Restart TCP/IP using 1.5E (or earlier) libraries.
Administrator Action: Although your IBM license for support and upgrades has expired,
TCP/IP support for earlier VSE levels is available from CSI International, both directly and
through distributors, worldwide.
IPN114E Incorrect version. Loaded copy phase version date time
(Response) Issued in response to a QUERY VERSIONS command, this message indicates a

problem with the version of the indicated phase. The message text describes the properties of
the phase that is now being used. This message may indicate the use of a substitute phase.
Operator Action: Ensure that the correct phase libraries are defined to TCP/IP FOR VSE and
that they are in the correct order.

13.3
IPN115I Applied fixes: list
(Response) This message, issued in response to a QUERY VERSIONS command, shows a list
(by number) of all fixes applied to TCP/IP FOR VSE.
IPN116E Unable to locate the physical device, Cuu: aaa
(Critical) Dynamic allocation of the device at the indicated address failed because the address
does not exist.
Administrator Action: Respecify the failing command with the correct device address.
IPN117E Unable to make dynamic assignment, Cuu: aaaa
(Critical) TCP/IP FOR VSE was attempting to dynamically allocate a device at location aaaa
but failed. Additional messages may indicate a specific problem.
Administrator Action: Correct any errors and retry the failing command.
IPN118E Unable to properly initialize the menu requested: aaa
(Response) Issued in response to a DEFINE MENU command, this response indicates that the
menu, aaa, contained errors and could not be initialized.
Administrator Action: Inspect SYSLST for more specific error indicators, correct them in the
menu source, and re-issue the DEFINE MENU command.
IPN119E Socket queue has been previously allocated
(Critical) During start-up, TCP/IP FOR VSE has found an existing socket queue. This queue
controls all TCP/IP communications and is deleted during TCP/IP FOR VSE termination
processing. This may mean that you are attempting to execute two copies of TCP/IP FOR VSE,
each using the same system ID (as assigned by the ID parameter in the PARM field of the
EXEC statement) or that TCP/IP FOR VSE has previously terminated without completing its
clean-up phase.
IPN120E No System GETVIS available for Sockets
(Critical) TCP/IP FOR VSE was unable to obtain enough System GETVIS area to allocate its
socket queue.
System Action: Initialization terminates.
Administrator Action: Increase the amount of system GETVIS area available. If you are
running multiple copies of TCP/IP FOR VSE, you may be able to release sufficient space by
closing down one or more of them. Examine other applications to determine whether one of
them is using excessive system GETVIS.

13.4
IPN121E No SDL space left for Sockets
(Critical) TCP/IP FOR VSE attempted to allocate a single SDL entry for use as an anchor but
there was insufficient space available.
System Action: TCP/IP FOR VSE terminates.
Administrator Action: To provide additional SDL space, examine the SDL statement within
your IPL procedure and increase the number of SDL entries to be allocated.
IPN122E Unable to locate our Socket in SDL list
(Critical) During shutdown, TCP/IP FOR VSE was not able to locate the anchor for the socket
queue. This is probably due to an improper start-up of another TCP/IP FOR VSE with the same
system ID (EXEC statement PARM field).
System Action: TCP/IP shuts down.
IPN123D type Socket call has been made
(Diagnose=SOCKET) This debugging message is issued when a DIAGNOSE SOCKET is in

effect. This information is of interest only to CSI Technical Support.
IPN124W Non-console req request ignored
(Important) While operating with DOWNCHECK ON, TCP/IP FOR VSE received a
SHUTDOWN or QUIESCE command from a location other than the operator’s console, for
example, IPNETCMD.
System Action: The request is ignored and processing continues.
Administrator Action: If the request is to be honored from a location other than the operator’s
console, then DOWNCHECK OFF must be in effect.
IPN125I request ignored
(Response) Following an operator request, TCP/IP FOR VSE prompted the operator for
additional information or a verification.
The response indicated that either the request was not desired or the verification was incorrect.
System Action: TCP/IP processing continues normally, without interruption.
Operator Action: If the TCP/IP request is desired, reenter it and respond appropriately to the
prompts.

13.5
IPN126E TRUST command failed: info
(Response) A problem was encountered while processing an operator “TRUST” command. The
message text indicates the nature of the problem.
System Action: The command is not processed.
Operator Action: Correct the command and re-enter it.
IPN127I ip address
(Response) Issued in response to a QUERY TRUSTED command, this message lists an IP

address that is considered to be “trusted.”
IPN128E info
(Response) Produced in response to a MODIFY ROUTE command, this message provides

information about an error in the command specification.
Operator Action: Correct the command and re-enter it.
IPN129E Unable to delete item, id
(Response) This message is issued in response to an operator DELETE command. The

indicated item identified by id could not be deleted.
Operator Action: This message is probably the result of a misspelling or an invalid syntax.
Retry the command.
IPN130I TCP/IP is executing in Demo Mode; Limited facilities available
(Critical) This message indicates that you are running TCP/IP FOR VSE in demonstration mode.
In this mode, many TCP/IP FOR VSE facilities are limited.
Administrator Action: Your CSI International representative can provide you with an
authorization code to fully activate the product. Contact your account manager or
sales@csi-international.com.
IPN131I Production use of "Demo Mode" to avoid licensing fees is theft.
(Critical) This informational message is a reminder that TCP/IP is not freeware or shareware
and that the demonstration mode is a courtesy to allow for initial evaluation.

13.6
IPN132I Contact CSI for details on rewards offered for reports of software piracy
(Critical) This informational message is a reminder that TCP/IP is not freeware or shareware
and that the demonstration mode is a courtesy to allow for initial evaluation of the product.
IPN134I Processing the execution parm override
(Info) TCP/IP FOR VSE is starting its scan of the PARM field of the EXEC statement.
IPN135I Processing of parm override complete
(Info) TCP/IP FOR VSE has completed processing all values specified in the PARM field of the
EXEC statement.
IPN136W Unidentifiable Information found in parm
(Warning) An unidentifiable keyword has been found in the PARM field of the EXEC
statement. TCP/IP FOR VSE continues initialization.
Administrator Action: Examine your JCL and ensure that the PARM field specifies only
correct entries. Depending on what caused the error, you may need to restart TCP/IP FOR VSE.
IPN137E ID= not specified correctly
(Vital) An error was detected while trying to decode the ID= parameter from the PARM field of
the EXEC statement. Although TCP/IP FOR VSE attempts to continue, chances of successful
initialization are slight.
Operator Action: Correct the syntax on the EXEC statement and restart TCP/IP FOR VSE.
IPN138I Corrupted chain pointer corrected
(Info) While attempting to allocate storage, TCP/IP FOR VSE noted that an internal control
block was corrupted. TCP/IP repaired the control block.
Administrator Action: If the situation happens more than once, contact CSI Technical
Support.
IPN139I System ID set to aa
(Info) This message is issued after the ID= parameter is decoded from the PARM field of the
EXEC card. The system ID is used to uniquely identify this particular TCP/IP FOR VSE
partition.

13.7
IPN140E name.PHASE could not be found. Code rc
(Important) The TCP/IP phase loader was unable to locate the named phase. The code is the
value returned in register 15 by the VSE LOAD macro.
System Action: Execution may or may not continue, depending on the importance of the
phase.
Operator Action: Ensure that all required TCP/IP functions are available. If required, restart
TCP/IP.
Administrator Action: Ensure that (1) all TCP/IP phases can be found using the search chain,
and (2) the libraries containing them are not corrupt.
IPN141E Link Type, xxx, can not be identified
(Response) The specification of TYPE= in a DEFINE LINK command was either missing or
invalid. Processing continues without the link.
Operator Action: Correct the specification and re-enter the command.
IPN142E Unable to setup Link Level routines
(Important) TCP/IP was unable to complete the initialization of one or more routines related to
the network interface.
System Action: TCP/IP will continue operation without the affected routines.
Operator Action: Examine the preceding messages for more insight into the problem. It may
be related to physical hardware, storage (or PFIXable storage) shortage, or a problem with a
VSE interface.
IPN143E LINKID= not specified
(Response) The LINKID= parameter on a DEFINE LINK command was missing or invalid.
System Action: Processing continues without the link.
Operator Action: Correct the LINKID= specification and re-enter the command.
IPN144E Link Level SYSID= not specified
(Response) The system ID of the target TCP/IP partition was omitted from a cross-partition
Operator Action: Supply the system ID of a TCP/IP partition and re-enter the command.

13.8
IPN145E Insufficient type storage for use. Code: rc Length: length
(Vital) TCP/IP could not obtain storage for the indicated use. The requested location is shown,
the return code value, and the contiguous storage length required.
System Action: TCP/IP will attempt to continue without the requested storage. Depending on
the use, connections and/or functionality may be lost. In some instances, TCP/IP FOR VSE may
terminate.
Operator Action: Try to reduce the load on the TCP/IP FOR VSE partition, if possible.
Discontinue debugging traces. Shutdown excess Daemons. Reduce optional buffering.
Be prepared to cycle or restart the TCP/IP FOR VSE partition, if functionality is impaired.
Administrator Action: Ensure that the TCP/IP partition has sufficient storage resources for the
loads imposed.
IPN146I TCP/IP Beginning Shutdown
(Info) TCP/IP FOR VSE has started the process of an orderly shutdown. This is probably in
response to an operator SHUTDOWN or CANCEL command.
System Action: Existing connections and processes are terminated and TCP/IP FOR VSE will
go to end-of-job.
IPN147I TCP/IP Shutdown complete
(Info) TCP/IP FOR VSE has completed the process of an orderly shutdown. This is the final
message prior to end-of-job.
System Action: TCP/IP completes detaching subtasks and goes to end-of-job.
IPN148E Define item, parm parameter missing.
(Response) A DEFINE command has been entered, but a required parameter was omitted.
System Action: The DEFINE command is suppressed.
Operator Action: Respecify the command and include all required parameters.
IPN149E Phase load failed for name. Code: rc
(Vital) Although TCP/IP was able to locate the requested phase and obtain the necessary
storage, the phase load was no successful.
System Action: Operation continues without the phase, if possible.
Operator Action: Examine other messages to determine the cause of the problem.

13.9
IPN150E Library action error. Phase: phase. Code: rc
(Vital) While loading the indicated phase, TCP/IP FOR VSE encountered a Librarian error. In
the message text, rc is the decimal return code from the LIBRM macro.
System Action: The phase is not loaded and TCP/IP FOR VSE continues, if possible.
Operator Action: Examine the console for other messages that might bear on this problem.
Administrator Action: Ensure that the library is not corrupt.
IPN151E Specified link not found
(Response) A STOP LINKID= command was issued, but the specified link could not be found.
Operator Action: Re-enter the command with the correct link ID.
IPN152D Phase aaaa has been loaded at bbbb
(Diagnose=DTLOAD) In response to a LOAD command, phase aaaa has been brought into
memory at location bbbb.
IPN154E Phase error: phase. Dump follows.
(Vital) While loading a phase, TCP/IP FOR VSE encountered data that appears to be incorrect.
System Action: TCP/IP FOR VSE quits loading the phase and produces a dump.
Administrator Action: Ensure that the phase data is correct and that the library is not corrupt.
Capture the phase dump before contacting CSI Technical Support.
IPN155W name lock held at dispatch. Id: id
(Warning) A TCP/IP pseudo task has returned control to the dispatcher while still holding
internal locks. This is an error in the program’s logic.
System Action: The locks are released and processing continues.
Operator Action: Watch TCP/IP FOR VSE for other signs of failure. Some processes may hang
or fail. It may be necessary to cycle the TCP/IP FOR VSE partition.
Administrator Action: Collect the diagnostic messages from SYSLST and contact CSI
Technical Support.

13.10
IPN157E INTERNAL ERROR: diagnostic text
(Vital) This message is issued when a “can’t happen” problem is encountered. The message
includes information that will describe the problem and possibly some error codes.
System Action: The state of the system is questionable following the appearance of this
message. Operation will continue, if possible.
Operator Action: Capture this message and any other relevant information from the log. Based
any of the information displayed, you may need to cycle the partition, reconfigure hardware, or
make adjustments to TCP/IP parameters.
Administrator Action: Please have the contents of SYSLST and all configuration decks
available before contacting CSI Technical Support.
IPN158E Error occurred while creating pseudo task
(Response) An error occurred while TCP/IP FOR VSE was attempting to create a pseudo task.
Other accompanying messages should indicate the source of this error.
IPN159E Unable to assign device dvc
(Response) TCP/IP FOR VSE was unable to dynamically allocate the required device whose
address is found in the message.
System Action: Processing continues without the device.
Operator Action: Determine the request that caused TCP/IP to attempt dynamic device
allocate. Either correct the request or ensure that the device is available and that there are
enough logical units available in the partition.
IPN161W Unable to Open Label Area specified. RC=rc
(Response) The label area specification used in a DEFINE FILESYS command could not be
opened. rc is the decimal return code from the failing VSE LABEL macro instruction.
Note: This command has been deprecated; use the EXEC FILESYS utility instead. See the
TCP/IP FOR VSE Installation Guide for information on this utility.
System Action: Operation continues without the files.
Operator Action: Refer to the IBM/VSE System’s Macro Guide to determine the reason for
the LABEL macro failure. Contact CSI Technical Support if you cannot solve the problem.

13.11
IPN162E Unable to Locate Requested Dataset: aaaaa
(Response) In response to a MODIFY FILE command, TCP/IP FOR VSE was unable to locate a
definition for the requested dataset. Note that this name is the Public Name and not necessarily
the actual dataset name.
Operator Action: Correct the dataset name and retry the command.
IPN163I Adjusted Dataset: aaaaa
(Response) Issued in response the MODIFY FILE command, this message indicates that the
dataset’s attributes were successfully modified.
IPN164E Definition failed, Dataset: aaaaa
(Response) The definition of the listed dataset could not be completed for a DEFINE FILE
command. Additional messages should indicate the precise problem.
System Action: Operation continues without the file.
Operator Action: Re-issue the DEFINE FILE command with corrected parameters.
IPN165E Critical Application Abend at addr. Phase: name, Offset: hex

(Critical) An abend has occurred in a critical routine.
System Action: TCP/IP FOR VSE will attempt a normal shut down.
Operator Action: Restart TCP/IP FOR VSE.
IPN166E Application Program Abend at: addr. Phase: name, Offset: hex
(Vital) A TCP/IP FOR VSE application task has abended.
System Action: A dump is produced. The system attempts to recover and continue processing.
Operator Action: Examine TCP/IP FOR VSE to ensure that its recovery was successful. If
other problems or loss of function is noted, it may be necessary to cycle the partition.
IPN167E PSW: hex Task: name Program: name Offset hex Int: code text
(Vital) This message is produced during abend and program-check processing and displays the
status of the task in control at the time of the error.

13.12
IPN168E Dynamic assignment of device has failed
(Response) TCP/IP is unable to dynamically assign a device during DEFINE LINK processing.
System Action: Execution continues without the link.
Operator Action: Correct the DEFINE LINK command and reissue it. If the DEFINE LINK of
a 3172 is followed by DEFINE ADAPTER statements, special procedures must be followed.
Consult the TCP/IP FOR VSE Installation Guide.
IPN169E Unable to PFIX required storage area
(Critical) When TCP/IP FOR VSE attempted to PFIX storage areas to be used for I/O, the PFIX
macro failed.
Operator Action: Increase the amount of allowable fixed memory by increasing the value in
the SET PFIX JCL statement and restart TCP/IP.
IPN170E Application Program Name not specified
(Response) TCP/IP FOR VSE was processing a DEFINE APPLICATION command; however,
you did not specify an application name.
System Action: The command is suppressed.
Operator Action: Correct the command and retry.
IPN171E Error occurred attaching xxx Driver: phase
(Response) While processing a DEFINE command, TCP/IP FOR VSE was unable to create a
pseudo task for the daemon’s driver program. Other accompanying messages should identify
the specific problem.
System Action: Operation continues without the daemon.
Operator Action: Correct the error and respecify the command.
IPN172I Caching=Enabled/Disabled Refresh=nnn minutes
(Response) A QUERY is made against DNS and DNS has been initialized by the appropriate
command.
IPN173I Auto-Domain=ON/OFF Retries=nnn
(Response) A QUERY is made against DNS. It indicates whether the option to auto-append the
domain name is enabled, and the number of retries to issue on a failed connection.

13.13
IPN177I Max-Cache=nnn Current-Cache=nnn
(Response) A QUERY is made against DNS. It indicates the amount of cache in use that was
initialized by the appropriate command.
IPN178E Link node name previously defined, Name: aaaaa
(Response) A DEFINE LINK command was issued but the ID= parameter was not unique.
Operator Action: Respecify the DEFINE LINK command with a unique link ID.
IPN180W Failure, IP address falls into extended mode
(Response) The address specified on a DEFINE ROUTE or MODIFY ROUTE command,

although valid, is not a class A, B, or C network address. Extended mode addressing is not
currently supported by TCP/IP FOR VSE.
Operator Action: Respecify the DEFINE ROUTE command using a class A, B, or C address.
IPN182W Routing information previously specified
(Response) The ID= specified on a DEFINE ROUTE command has already been used for
another route.
System Action: The definition is ignored.
Operator Action: Respecify the command with a unique route ID.
IPN183E Parm INIT=xxxxxxxx not specified correctly
(Vital) You have specified the INIT= parameter in the PARM field of the EXEC statement, but
the member name was syntactically invalid.
System Action: TCP/IP FOR VSE continues initialization without a member specification.
Operator Action: Ensure that the initialization member is correctly identified by the INIT=
parameter. You will probably need to cycle TCP/IP FOR VSE to pick up the proper initialization
parameters.
IPN184I User Initialization deck set to aaaa
(Info) Issued when the INIT= parameter is coded in the PARM field of the EXEC statement,
this message indicates the member name where TCP/IP FOR VSE expects to find the locally
defined initialization commands.

13.14
IPN185E Service has been limited by demo mode. 1 type Daemon allowed
(Response) You are running a demonstration copy of TCP/IP FOR VSE and have attempted to
use more facilities than permitted.
System Action: TCP/IP FOR VSE ignores the request to start additional daemons of type type.
Administrator Action: Contact your Connectivity Systems representative.
IPN188I IP Address aaa = Net: bb Subnet: cc Host: dd
(Response) This message displays TCP/IP FOR VSE’s IP network address and breaks it down
into the network number, subnetwork number and host number. Keep in mind that if the SET
MASK command has not yet been processed, the subnet and host field may be incorrect.
IPN189W PRODID AUTH failed. RC: dec
(Warning) During initialization, TCP/IP FOR VSE requested VSE to perform the PRODID
AUTH function. VSE indicated that the request failed, returning the completion code shown.
Because of this failure, TCP/IP FOR VSE may not perform in an acceptable manner.
Operator Action: Ensure that TCP/IP FOR VSE initialization completes and that the stack is
functioning correctly.
Administrator Action: Contact CSI Technical Support for assistance.
IPN190E Insufficient type-bit partition GETVIS to load item
(Vital) TCP/IP FOR VSE was unable to load the indicated item due to a shortage of storage with
the indicated attribute.
System Action: TCP/IP terminates.
Operator Action: If TCP/IP does not complete termination, it may be necessary to issue a
Cancel. Restart TCP/IP in a larger partition, or with options modified to require less storage.
Administrator Action: Note that requests for 31-bit storage will be filled with 24-bit storage if
31-bit memory is exhausted. This may cause a later request for 24-bit memory to fail.
IPN191E Storage corruption detected.
(Vital) TCP/IP FOR VSE incorporates a sophisticated storage manager. One of its tasks is to
ensure that memory is not “walked on” by incorrectly executing tasks and processes.
When “VERIFY_MEMORY ON” is in effect (this is the default for beta-level code), the
TCP/IP FOR VSE multi-tasking engines tests every storage element at every dispatch for
validity. Although this testing is expensive in terms of CPU required, it will catch most cases of
storage corruption while the offending program is still in control.

13.15
This message is followed by the contents of the general registers are the time the corruption was
noted. Other messages may also be present, providing additional information.
Operator Action: It may be necessary to cycle the TCP/IP partition to regain required
functionality. If you can determine the function being executed at the time of corruption, it is
recommended that it not be retried until the problem has been resolved.
Administrator Action: Contact CSI Technical Support immediately. If you are executing a
beta-level release, check for the availability of a newer version.
IPN192E Attempt to preempt timer by task, id. Owned by task, id.
(Vital) During execution of an internal timing request, a task attempted to use an ECB already
being used to time a different task.
System Action: The request fails an the requesting task is notified.
Operator Action: Watch for signs of timing-related failures.
Administrator Action: This message indicates an internal programming problem, and it

should be reported to CSI Technical Support as soon as possible.
IPN193E ECB in wait state. task, id
(Vital) A pseudo task returned control to the dispatching engine, specifying an ECB to be
waited on. Internal flags, however, indicate that another task is already using the ECB. This is
not permitted.
System Action: The task’s wait request ends immediately and control is returned.
Operator Action: Watch for signs of other problems.
Administrator Action: This message indicates an serious internal logic error, and it should be
reported to CSI Technical Support as soon as possible.
IPN195E Error occurred while attaching the type driver (phase)
(Important) A failure has occurred while creating a daemon of the type indicated. The phase
name of the daemon is also listed.
System Action: The daemon is not created.
Operator Action: Ensure that the named phase is accessible to the TCP/IP partition by the
library search chain. Examine the console log for additional messages that may show the reason
for the failure.
Retry the failing command.

13.16
IPN196E Required ID= parameter is missing
(Response) The previously entered command did not specify a value for the ID= parameter.
System Action: Execution of the command is suppressed.
Operator Action: Reenter the command with and ID= parameter.
IPN198E Real ECB reuse by task, id. Owned by task, id
(Vital) A pseudo task has requested a “wait” on an ECB already in use by another task.
Pseudo tasks employ two types of ECBs. Internal ECBs are known only to the TCP/IP
dispatching engine. “Real” ECBs are also known to, and posted by, VSE.
System Action: Control to returned to the requesting task without waiting.
Operator Action: It may be necessary to cycle the TCP/IP partition if its behavior becomes
erratic.
Administrator Action: Contact CSI Technical Support as soon as possible.
IPN199W Insufficient 24-bit GETVIS to start task task
(Warning) The dispatching engine was unable to obtain enough 24-bit partition GETVIS to
establish the linkage control blocks required to begin execution of the named task.
System Action: The task proceeds immediately to end-of-task processing.
Operator Action: Determine what work was not accomplished and take steps to restart the
process. Note that this level of storage shortage will probably require that the stack be cycled as
soon as possible.
Administrator Action: Because only programs linked with AMODE 24 require 24-bit control
areas, determine if excessive numbers of such programs are concurrently executing. Also note
that a 31-bit storage shortage will cause 24-bit memory to be substituted. In cases where this
substitution is for long-term use, or if fragmentation occurs, there will be insufficient usable 24-
bit storage when it is needed.
IPN200E ECB list error: addr taskid
(Important) A pseudo task issued a wait request, but the ECB or ECB list was not valid.
System Action: Control is returned to the task without waiting.
Operator Action: Be alert for other problems and messages.
Administrator Action: Contact CSI Technical Support as soon as possible.

13.17
IPN202I Registers at time:
(Info) This message is displayed as part of a diagnostic dump. Following this message, register
contents related to the time indicated will be displayed.
IPN203W Product is unlicensed, executing in demo mode
(Important) Based on the available authorization code(s), TCP/IP FOR VSE has determined that
no valid license for the product exists and that this is a demonstration copy. TCP/IP FOR VSE’S
demonstration mode is limited to one of each class of daemons and a maximum continuous run
time of one hour.
Operator Action: Notify your system administrator.
IPN204W Demo mode time limit has been reached, shutting down product
(Info) Based on the available authorization code(s), TCP/IP FOR VSE has been executing in
demonstration mode. Demonstration mode permits a maximum of one hour of continuous
execution. This time limit has been reached and TCP/IP FOR VSE is shutting down.
Administrator Action: You may restart TCP/IP FOR VSE for an additional one-hour period of
execution.
IPN205A Respond "YES" for type TCP/IP shutdown
(Response) A shutdown request of the indicated type has been received and TCP/IP is verifying
your intent.
System Action: The system continues operation but command processing waits for an answer
to the question.
Operator Action: If you wish to continue with the shutdown process, respond with “YES”. A
response of “NO” cancels the shutdown request and returns operation to normal.
Administrator Action: The DOWNCHECK command can be used to control whether a

shutdown verification is required.
IPN206I Dump has completed
(Info) This message is issued to notify you that a requested dump operation has been
completed.
IPN207I File I/O subtask has been re-attached after error
(Info) The true subtask responsible for performing file I/O has suffered a program check and
terminated. TCP/IP FOR VSE has attached a new copy of the subtask. All in-flight I/O
operations are recovered.

13.18
IPN208I File I/O driver error. Attempting recovery
(Vital) A request being processed by a file I/O driver has failed in an unexpected manner.
System Action: Diagnostic information is produced. The program that made the I/O request is
notified of the failure. Processing continues with other requests.
Operator Action: None. Other messages may be produced when the I/O failure is reflected to
the requesting program. Evaluate these messages for their effects on processing.
Administrator Action: Capture the dump. If this dump cannot be attributed to a user-written
application, then send it to CSI Technical Support.
IPN209I Service Pack nnn (APAR apar) has been applied. Pack status is bbb
(Important) This message indicates the level of maintenance applied to the product. The status
may be “ALPHA”, “BETA”, or “PROD”.
The “APAR” value indicates the equivalent IBM version of the product at this service level.
IPN210I [Socket] Trace ID id defined and running.
(Response) Issued in response to a DEFINE TRACE or DEFINE SOTRACE command, this

message indicates the successful definition of a new IBBLOK or socket trace.
IPN211A Respond "YES" to quiesce TCP/IP processing t< Resp
(Info) A QUIESCE command has been entered and TCP/IP is verifying your intent.
System Action: The system continues operation but command processing waits for an answer
to the question.
Operator Action: If you want the quiesce request to take effect, respond with “YES”. A
response of “NO” cancels the quiesce request and TCP/IP status does not change.
Administrator Action: The DOWNCHECK command can be used to control whether a

quiesce verification is required.
IPN212W Tracing information previously specified
(Response) Issued in response to a DEFINE TRACE command, this message indicates that the
ID= parameter specifies a value already in use.

13.19
IPN213I id tracing traffic between ip; port and ip; port
(Info) This message is issued when a DEFINE TRACE is in effect when the first datagram from
a connection is added to the trace set. The message shows the id specified in the DEFINE
TRACE command, as well as the source and target addresses of the datagram.
Exact duplicate messages can occur if all datagrams on a connection have rolled off the trace,
due to the value specified for SIZE= on the DEFINE TRACE command.
Exact duplicate messages can also occur when the datagrams made available to the trace are out
of time-sequence. This can occur due to retransmission and does not indicate a problem.
IPN214I Dump started
(Important) An error condition has caused TCP/IP to produce a diagnostic dump.
System Action: TCP/IP proceeds with diagnostic processing.
Operator Action: Watch for the IPN215I message that indicates the completion of the
dumping process. Be aware that during this period you may see a number of other messages
logged because the servicing of other requests is deferred until the dump is complete.
Administrator Action: If warranted, send the complete SYSLST to CSI Technical Support.
IPN215I Dump complete
(Important) An error condition has caused TCP/IP to produce a diagnostic dump. This process
is now complete.
System Action: TCP/IP resumes normal processing.
Administrator Action: If warranted, send the complete SYSLST to CSI Technical Support.
IPN216I Product code can be obtained from: (800) 795-4914, (614) 436-2059
(Info) You are currently executing the software in demonstration mode. You may request an
authorization code to fully activate the product. Contact your account manager or e-mail
sales@csi-international.com.
IPN217E Could not locate LINKID ed., adapter num
(Response) TCP/IP was unable to locate the link driver and adapter referred to by this Route.
For link types that support adapters (3172, OSA2), you must also specify the adapter number
(the default is “0”).
System Action: The route is not defined.
Operator Action: Ensure that the LINKID= parameter and, if applicable, the ADAPTER=
parameter identify an already defined Link/Adapter.

13.20
IPN219I No Service Pack has been applied (APAR apar), status xxx
may be “BETA” or “PRODUCTION”.
The “APAR” value indicates the equivalent IBM version of the product at this service level.
IPN222E TCP/IP System loop has been detected, action
(Info) The monitoring task has determined that TCP/IP for VSE has entered a never-ending
loop. This message, with different action values, will be issued several times.
System Action: The monitoring task analyzes the situation, produces diagnostics, and attempts
to correct the condition.
If the File I/O subtask is determined to be looping, it will be forced to program check. A dump
will be produced and the task re-attached. If this clears the problem, processing will resume.
If a “pseudo task” is determined to be at fault, it will also be forced to program check.

Depending on the task in question, TCP/IP for VSE will either resume operation or initiate a
shutdown. In either case, a diagnostic dump will be produced.
Operator Action: Secure the SYSLST and initialization parameters before contacting CSI
Technical Support. Note that recovery from a File I/O problem resumes with the failing request,
so no data is lost. Failure of a pseudo task will cause some TCP/IP for VSE activity or
functionality to be lost. Watch for other failures and hangs.
Cycle the partition, if necessary.
Regardless of recovery success, TCP/IP for VSE operations are all highly timing dependent.
Expect that many connections will fail and will need to be restarted.
Administrator Action: Determine what has changed since the last successful TCP/IP for VSE
operation. A key item to check is the security exit, if any is used.
IPN223A Please enter password
(Response) TCP/IP is requesting the operator’s password before allowing commands to be

issued.
System Action: Processing continues while TCP/IP awaits a response.
Operator Action: Enter the operator password to proceed. An invalid entry cancels the request.
Administrator Action: If a password is not desired, remove the SET PASSWORD command
from the initialization deck.

13.21
IPN224I System Analysis set to analyze aa
(Response) This message indicates that the system is performing an analysis of the indicated
resource.
IPN225I TCP/IP quiescing; connection requests are rejected
(Vital) TCP/IP has accepted an operator QUIESCE command.
System Action: Normal processing continues on all connections that are already established.
Additional socket OPEN requests by applications are rejected. Incoming connection requests
are rejected.
Operator Action: The QUIESCE OFF command may be entered to resume normal operation.
IPN226I TCP/IP QUIESCE is canceled. Normal processing resumes.
(Info) TCP/IP has received a QUIESCE OFF command
System Action: Any previously entered QUIESCE commands are canceled. Socket OPEN
requests from applications are once again honored, and incoming connection requests are
treated normally.
IPN227E TCP/IP recovery in progress. Please wait.
(Critical) A previously running TCP/IP has terminated without releasing its socket queues.
TCP/IP will now analyze the residual sockets and take corrective action to recover the storage.
This may take several minutes.
Operator Action: Watch for additional messages that may request your input.
IPN228I CHAP issued by task name
(Important) TCP/IP internal processing relies on a priority scheme for its VSE subtasks. Due to
error-recovery procedures and other issues, it is possible for this relationship to change. When
necessary, each subtask will, in turn, issue a CHAP until the correct order is restored.
IPN229I TCP/IP partition CPU at xx% for ss seconds. (flags)
(Important) The stack’s internal monitoring program has noticed that the TCP/IP partition has
consumed an unexpectedly large amount of CPU time over the indicated period. This may
indicate a problem.
System Action: The monitoring program will further examine the running tasks and programs
to determine if an actual loop condition exists.
Operator Action: Look for and correct condition that may be contributing to excessive CPU
usage by TCP/IP.

13.22
IPN230I IBM APAR aa (SP sp) has been applied. Status is bb
may be “ALPHA”, “BETA”, or “PROD”.
The “SP” value indicates the equivalent CSI version of the product for this APAR.
IPN233I IBM aaa Pack enabled by product key
(Info) This message indicates that you are using a valid IBM authorization key for the specified
pack, either “Base” or “Application”.
IPN237I parameter text
(Info) This message records the contents of the initialization deck(s). It is written only to
SYSLST.
If the text is shown as “++SUPRESSED++”, it means that the parameter contained a password
or other “secure” information of a sensitive nature.
IPN239W WARNING, possible version mismatch for phase aa
(Warning) During initialization, TCP/IP FOR VSE has noted that the listed phase is not at the
expected version level.
System Action: Initialization continues.
Administrator Action: Ensure that the TCP/IP installation is correct.
IPN244W There are no DNS settings defined.
(Response) Displayed when a QUERY is made against DNS and DNS has not been initialized
by the appropriate command.
IPN246I Upper Case message translation set to aa
(Info) TCP/IP FOR VSE will force all messages to upper case (or not), depending on
instructions contained in the PARM field of the EXEC statement.
IPN247W No DNS access points have been defined to TCP/IP
(Response) Displayed when a QUERY is made against DNS and there is no DNS server
defined to the system.

13.23
IPN248I Maximum Messages set to: aaa
(Response) In response to a SET MAXIMUM_MESSAGES command, this message verifies

the value that was set.
Note: The MAXIMUM_MESSAGES command has been deprecated.
IPN249I Value for aa set to bb
(Response) This message is included within a console display operation. In the text, the named
variable, aa, has been set to a new value, bb.
IPN251I Fixed retransmission rate set to aa
(Response) This message indicates the time interval (in 300th-second units) that will elapse
before an unacknowledged transmission will be considered eligible for retransmission. This
interval is used only if SET FIXED_RETRANS is set to ON.
Note: The FIXED_RETRANS command has been deprecated.
IPN252I Full CETI interface errors set to aa
(Response) This message indicates the level of error reporting to be performed by a link driver
supporting the CETI interface. “ON” will produce the maximum reporting of errors, including
some that are generally considered to be normal.
IPN253I << TCP/IP objects >>
(Response) This message marks the start of a display of the indicated objects.
System Action: TCP/IP proceeds with the listing of the requested object type.
IPN254I DNS a address is bb, Timeout is cc
(Response) Issued in response to a SET DNS command, this message indicates the IP address
(bb) that will be used for DNS number a. The timeout value is shown is in 300th-second units.
When a DNS look-up request is processed, each defined DNS is polled in order, beginning with
DNS1. The operation is complete when a DNS returns a response, either positive or negative. If
no response is received before the timeout interval is reached, the next DNS is polled.
The same DNS may be specified more than once (for example, SET DNS1 and SET DNS2) to
allow for a retry operation after a timeout.

13.24
IPN255I Reuse queue maximum size is set to aaa
(Response) Issued in response to a SET REUSE_SIZE command, this message verifies the
value set.
Note: The REUSE_SIZE command has been deprecated. See the IBBLOK command.
IPN257I Exit ID: aa Type: bb
(Response) Issued in response to a QUERY EXITS command, this message displays an exit’s
ID and type.
IPN258I Program: aa Address: bb
(Response) Issued in response to a QUERY EXITS command, this message displays an exit’s
associated program and its address.
IPN259I State: aaa
(Response) Issued in response to a QUERY EXITS command, this message displays the exit’s
current status, either “Active” or “Inactive”.
IPN260I Owners: (flag) C: id name; S: id name
(Diagnose) This message is issued when an IBBLOK is dumped if its internal “ownership”
flags are set.
The “C” field shows the task ID and task name of the connection manager that owns the
IBBLOK. The “S” field shows the task ID and task name of a service task that co-owns the
IBBLOK.
IPN262E Exit id could not be stopped/started.
(Response) You requested that an exit be started or stopped, but the indicated exit is not
available.
Operator Action: Correct your request and re-enter the command.
IPN263I Exit: aa has been bb
(Response) The specified exit has been either enabled or disabled, as indicated in the message.

13.25
IPN264I File defined, Dataset: aaaaa
(Response) The indicated dataset has been successfully defined. Note that the displayed name is
limited to 32 characters. The actual file name is as specified in the DEFINE FILE command.
IPN267E Task address missing during task termination.
(Critical) TCP/IP was attempting to terminate an internal task but found that it had no address
pointer. This may indicate storage corruption.
System Action: TCP/IP attempts to correct the problem and continue. This may result in some
connections being lost or entering a stalled state.
Operator Action: Monitor operations, and be prepared to cycle the TCP/IP partition if needed.
IPN271I nnn entry point(s) have been deleted.
(Response) Issued in response to a DELETE DNS command and reports the number of points
removed from the system.
IPN272W There are no DNS entry points to delete.
(Response) Issued in response to a DELETE DNS command because there are no entry points
defined to the system, and so you cannot remove something that does not exist.
IPN273I Maximum ttt Events: aaa Current Events: bbb
(Response) Issued in response to a QUERY EVENTS command, this message displays the
maximum concurrent events that can be processed in each category, and the number of events
that are currently being processed.
IPN274I num type-based SOBLOKs released (num bytes)
(Response) The operator RELEASE command has been accepted.
System Action: The indicated storage was successfully released.
IPN275W No script name found to process in field
(Warning) The EVENT client accepted a request to process an entry from the POWER queue. It
checked the specific field that should have a script name, but found none. This may or may not
be a problem.
Operator Action: If the process fails, this information may be useful in determining the reason
for the failure.

13.26
IPN276D Processing script=scriptname field=name
(Diagnose=EMAIL) While DIAGNOSE EMAIL was in effect, an EMAIL event was triggered
and a POWER queue entry is now being processed. This message indicates the name of the
script and the field in which it was found.
IPN277W Obsolete command: old [Replaced by: new]
(Response) The indicated command has been issued, but is no longer supported.
System Action: The command is ignored and execution continues.
Operator Action: In general, this message indicates that the requested operation is no longer
required or offered by the product. Ensure that you have not used an incorrect or misspelled
command.
If a replacement command is available to provide the function, it will also be shown. Refer to
the TCP/IP FOR VSE Command Reference to determine how to use the replacement command.
Administrator Action: Review configuration files and EXEC scripts for obsolete commands.
Deprecated commands are listed in Chapter 4, “Deprecated Commands,” in the Command
Reference manual.
IPN278E Corrupted block at location nn
(Vital) The specified control block at the indicated memory location has been found to be
invalid.
System Action: A snap dump of the failing control block is produced.
Operator Action: Before contacting CSI Technical Support, have the message and dump ready
for e-mailing.
IPN279I Dumping Trace ID id; IPadd: ip, Port: num
(Response) This message is issued in response to a DUMP TRACE command and is displayed
for each trace being displayed. The message text shows the ID associated with the DEFINE
TRACE command that created it. The candidate IP address and port number is also shown. If
either of these two values is “0”, then filtering was not performed on the 0-value.
IPN280I dir IBBLOK. L: ip, port. F: ip, port. Ident: id. t< Diag
(Info) This message is issued in response to a DUMP TRACE command and is displayed for
each IBBLOK (datagram) displayed. The message text shows the direction of the datagram,
along with the IP addresses and port numbers associated with the datagram.
The Ident field uniquely identifies the connection and is also displayed for Socket Blocks
(SOBLOK) and Connection Blocks (CCBLOK).

13.27
IPN281I IP: Len=len ID=ident TTL=ttl CS=chksum Src=from-ip Dest=to-ip
(Diagnose) This message is issued in response to a DUMP TRACE command and is displayed
for each datagram in the trace. The values displayed are interpreted from the IP header.
IPN282I TCP: SPort=num TPort=num Seq=seq Ack=ack-seq Win=window CS=chksum

Opt=options
for each TCP datagram in the trace. The values displayed are interpreted from the TCP header.
IPN283I IBBK: Retran=count Queued=time Depart=time Finish=time
for each outbound datagram in the trace.
The “Retran” value is the retransmit count. This will be 0 if no retransmissions were required.
The “Queued” time is the time of day when the outbound datagram was constructed and queued
for transmission.
The “Depart” time is the time of day when the datagram was actually transmitted by a link
driver. The “Finish” time is the time of day when the datagram was acknowledged by the
remote host.
IPN284I IBBK: Recv=time Finish=time
for each inbound datagram in the trace.
The “Recv” time is the time of day when the datagram was received by the link driver.
The “Finish” time is the time of day when the ACK and window values were applied and the
last byte of data was returned to the local application.
IPN285I dir proto action from phase (addr) in part. Time: time [delta]
(Response) Issued in response to a “DUMP TRACE” command, this message—along with

those that follow—describe the content of a single socket operation.
The first field will be either “Req”, to indicate that this is an incoming socket request, or
“Resp”, to indicate that this is the socket response being returned to the application. This is
followed by the protocol, such as TCP, and the action, such as OPEN or SEND.
Additional fields show the phase and partition that issued the socket request. The address
where the request originated is in parentheses. For request displays, the time is when the request
originated. For response displays, the time is when the response was posted back to the
application, along with the elapsed time (delta) between request and response.

13.28
IPN286I F: ip, port L: ip, port Ident: hex [BSD: num]
(Response) Issued in response to a “DUMP TRACE” command, this message provides

additional information about the socket being displayed.
The foreign IP address and port are shown, followed by the local port number. The “Ident” field
is a value that is unique to the connection. The physical address of the Socket Block is also
included.
In some instances, the “BSD:” string will appear, followed by a number. This is additional
information supplied by the BSD interface and shows the socket number used by the
application to refer to the connection.
IPN287I TCP type Seq: seq - seq, num bytes
(Response) Issued in response to a “DUMP TRACE” command, this message is provided for
sockets that perform TCP SEND and RECEIVE operations. The message shows the sequence
numbers assigned to the data bytes attached to the request, along with the byte count.
The sequence numbers are those used by the connection and can be used to associate the data
bytes with other traces.
IPN288I SRCODE: dec (hex) Length: num
(Response) Issued in response to a “DUMP TRACE” command, this message is displayed for
responses to socket requests. The message text shows the return code (SRCODE) value, both in
decimal and in (hexadecimal), followed by the number of data bytes returned.
IPN289I BSD Value: dec RC: dec Reason: dec Length: dec
responses to BSD Asynchronous I/O requests. The text will show (in decimal) the Return
Value, the Return Code, the Return Reason, and the returned data length.
IPN290I Dumping Socket Trace id; IPadd: ip, Port: num Num: dec proto
for each socket trace being displayed. The message text shows the ID associated with the
DEFINE TRACE command that created it. The candidate IP address and port number is also
shown.
Values shown as zero or null indicate that filtering was not performed on that value.
IPN291I TCP Control func ...data...
(Response) This message is produced in response to a DUMP TRACE command. It

summarizes sockets assigned to TCP CONTROL requests and responses. The message text
displays the Control function being requested, along with data pertinent to the request.

13.29
IPN292I BSD Socket Address: values
responses to BSD asynchronous I/O requests. The values shown comprise the “Socket
Address”. The first instance of this message contains a hexadecimal dump of the entire field. A
second line is produced with interpreted values, if the format is recognized.
In the interpreted line, the first field is the “family”. A value of 2 indicates IPv4 addressing. In
this case, the next value is the foreign port number, followed by the foreign IP address.
Not all asynchronous I/O operations request this information to be returned.
IPN293I Obsolete interface version: v.r
(Response) Issued in response to a “DUMP TRACE” command, this message indicates the
version and release level of the API used for the socket request.
This message is issued ONLY if the API version differs from the expected version.
IPN294I L: ip, port.; F: ip, port.; Ident: id. t< Resp
(Info) This message is issued in response to a DUMP TRACE command and is displayed for
each CCBLOK displayed. The message text shows the IP addresses and port numbers
associated with the connection.
The Ident field uniquely identifies the connection and is also displayed for Socket Blocks
(SOBLOK) and Datagram Blocks (IBBLOK).
IPN295I Queue time: msec Staging time: msec Proc Time: msec
(Response) Issued in response to a “DUMP TRACE” command, this message provides

additional information about the socket being displayed.
“Queue time” is the elapsed time from when the socket request was initiated until the stack
partition became aware of the request.
“Staging time” is the time required for the request to be passed to the appropriate connection
manager and to begin processing.
“Proc time” is the time required to actually process the request and return the results to the
requesting application.
All times are shown in milliseconds. Adding the three values will yield the complete response
time.
Large values for Queue or Staging time generally mean an incorrect dispatching priority for the
TCP partition, or lack of CPU resources. The value for Proc time will vary depending on the
type of request being performed.

13.30
IPN296I protocol state partid phase
for each CCBLOK displayed. The message text shows the connection protocol; the connection
state (TCP only); and for TCP and UDP, the partition ID and phase name of the connection’s
owner.
IPN297I Path: string
for each datagram in the trace.
The data displayed represents the path that the datagram took through the stack. This data may
be useful to CSI Technical Support when troubleshooting a problem.
IPN300A Enter/Continue TCP/IP Command
(Response) TCP/IP is prompting the operator for an operating command.
System Action: Processing continues while TCP/IP awaits a command.
Operator Action: Enter a TCP/IP command. To cancel the prompt, enter a null response.
If a null response causes the prompting message to be redisplayed, it is because

CONSOLE_HOLD ON is in effect. To delete the prompt, enter CONSOLE_HOLD OFF.
IPN301E First operand character is invalid. Operand: xxx
(Response) The previously entered command contains an operand whose first character is not
acceptable. The failing operand is displayed in the message.
System Action: TCP/IP will not execute the command.
Operator Action: Correct the error and re-enter the command.
IPN302E Operand has an invalid character. Operand: xxx
(Response) The previously entered command contains a character that is not permitted in this
context.

13.31
IPN303E IP address is invalid. Keyword: xxx
(Response) The previously entered command contains an invalid IP address specification. The
keyword that specified the invalid value is displayed.
IPN304E Unbalanced parentheses. Keyword: xxx
(Response) The previously entered command contains an operand with unbalanced

parentheses. The keyword that specified the invalid value is displayed.
IPN305E Hexadecimal value too large. Keyword: xxx Max: mmm
(Response) The previously entered command contains an operand whose hexadecimal value
was larger than permitted. The keyword that specified the invalid value is displayed, along with
the maximum permissible value.
IPN306E Invalid hexadecimal character. Keyword: xxx
(Response) The previously entered command contains an operand whose hexadecimal value
contained one or more invalid characters. Valid characters are A–F and 0–9. The keyword that
specified the invalid value is displayed.
IPN307E Missing operand. Keyword: xxx
(Response) The previously entered command contains a keyword that did not have an operand.
The keyword that is missing the operand is displayed.

13.32
IPN308E Invalid operand. Keyword: xxx
(Response) The previously entered command contains a keyword with an invalid operand. The
keyword with the invalid operand is displayed.
IPN309E Numeric value is not acceptable. Keyword: xxx
(Response) The previously entered command contains a numeric value that is syntactically
invalid. The keyword with the invalid operand is displayed.
IPN310E Invalid command: xxx
(Response) The previously entered command is invalid. The text string being processed as a
command is displayed.
IPN311E Invalid Subcommand: xxx
(Response) A subcommand of the previously entered command is invalid. The unrecognized

string is displayed in the message.
IPN312E Numeric value too low. Keyword: xxx Range: min, max
(Response) A numeric operand of the previously entered command is less than the minimum
value permitted. The keyword with the improper value is displayed in the message along with
the acceptable minimum and maximum values.

13.33
IPN313E Numeric value too high. Keyword: xxx Range: min, max
(Response) A numeric operand of the previously entered command is greater than the
maximum value permitted. The keyword with the improper value is displayed in the message
along with the acceptable minimum and maximum values.
IPN314E Command too long: xxx
(Response) A command has been input with continuation lines that, when assembled, exceeds
the maximum length supported by the parser.
IPN315E Unexpected end-of-input: xxx
(Response) While processing continuation lines, an unexpected end-of-data condition was

encountered. A portion of the incomplete command is displayed in the message.
IPN316E Invalid keyword: xxx
(Response) The specified keyword is not recognized or invalid with the command being
processed.
IPN317E Unrecognized value: xxx
(Response) The indicated value is not valid in the context in which it was used.

13.34
IPN318E Misplaced delimiter in Public name
(Response) A delimiter character (/\.) was found in an improper place within a public name
specification.
IPN319E Embedded blank in Public name
(Response) A public name was specified that contained an embedded blank. This is not
permitted.
IPN320E Name segment too long in Public name
(Response) A public name was specified that contained one or more name segments (nodes)
that exceeded 8 characters in length.
IPN321E Unexpected end of Public name
(Response) A public name ended before it was complete. This is probably because the last-
specified character in the name is a delimiter.
IPN322E Public name is too long
(Response) You have specified a public name that contains more than six nodes.

13.35
IPN323E Invalid character in Public name
(Response) You have specified a public name that contains one or mode invalid characters.
IPN324E Public name contains no characters
(Response) You have specified a public name but the specification is null.
IPN325E No option specified
(Response) You have specified a command that requires specification of an option, but none
was included in the command.
IPN326E Invalid IP address specification
(Response) You have specified a command that requires specification of an IP address.

However, the value specified was not valid.
IPN327E Invalid port specification
(Response) You have specified a command that requires specification of a port address.
However, the value specified was not a valid port.

13.36
IPN328E Invalid MAC address specification
(Response) The MAC address specified in the command is syntactically invalid.
IPN329E Required keyword missing. Command: xxx
(Response) The specified command did not contain all required keyword operands.
IPN330E Required "ID=" parameter missing
(Response) The command did not contain a specification for the required keyword ID=.
IPN331E This command must be issued from SYSID=00
(Response) This message is displayed when a restricted operator is issued to a TCP/IP partition
that is not identified as “SYSID=00”.
System Action: The command is not executed.
Operator Action: Re-issued the failing command to the TCP/IP stack identified as SYSID=00.
IPN332E Redefinition pattern not found
(Response) The pattern requested by the REDEFINE command could not be found.
Operator Action: Use the DEFINE command.
IPN333E Specified class not eligible for REDEFINE
(Response) The object requested by the REDEFINE command is not stored for re-definition.
Operator Action: Use the DEFINE command.

13.37
IPN334E Operand too long, keyword: key
(Response) The operand text specified for the indicated keyword was too long, or contained too
many suboperands.
Operator Action: Correct and re-enter the command.
IPN348E DSName error: reason
(Response) The previously entered command contains an invalid dataset name. reason will
explain why it is invalid.
IPN349E Invalid Error condition
(Response) The last-entered command caused an unexpected failure of the command parser.
Operator Action: Modify any questionable parameters or operands and retry the command.
Administrator Action: Report this failure, along with the precise command entered, to CSI
Technical Support.
IPN350I Current Status: aaa
(Response) This message is issued in response to a QUERY command. The status of the object
being displayed, either ACTIVE or INACTIVE, is shown.
IPN351I Current IPaddr: aaa
(Response) Displayed only for daemons that are currently connected to clients, this message
shows the client’s IP address.
IPN353E Task ID xxxx is not assigned.
(Response) TCP/IP FOR VSE is attempting to suspend or resume execution of the indicated
task. However, the task number is not assigned.
Operator Action: Reissue the command with a valid task number.

13.38
IPN355I Current Userid: user
(Response) Displayed only for daemons that are currently connected to clients and logged in,
this message shows the client’s user ID.
IPN357I Traffic has been flushed for IP: aaa Port: bbb
(Response) Issued following execution of the FLUSH command, this message indicates the IP
address and port for which datagrams have been eliminated and connections closed.
If the port number is 0, then all traffic and connections with the IP address have been deleted.
IPN358I Flush request has failed to locate any traffic for IP: aaa Port: bbb
(Response) Although a FLUSH command has been entered for the indicated IP address and
port, no currently queued data meets the specification.
IPN361W Unable to allocate type buffers. Current: num
(Response) TCP/IP FOR VSE attempted to increase the number of buffers of the indicated type.
The attempt failed due to insufficient free storage. The number of buffers currently allocated is
also displayed.
System Action: Processing continues with the already-allocated buffers.
Operator Action: You may want to try increasing the buffers at a later time when storage has
freed or become less fragmented.
Administrator Action: Ensure that the partition size is adequate.
IPN362I Maximum sessions: num, Current: num
(Response) Issued in response to a QUERY FTPD command, this message shows the
maximum number of sessions that this daemon will allow along with the number of currently
active sessions. Once the maximum number of active sessions is reached additional session
requests will be rejected.
IPN363I Last type time: time
(Response) Issued in response to a QUERY FTPD command, this message shows the time
when the last command or response occurred on the current FTP session’s control connection.
IPN364I Userid: userid connected from foip,foport
(Info) Issued in response to a QUERY FTPD command, this message shows the user’s ID,
foreign IP address, and foreign port of the connection being served by this FTP daemon.

13.39
IPN365I Started at: time date
(Response) Issued in response to a QUERY FTPD command, this message shows the time and
date this FTP session started.
IPN366I xxx files sent, yyy files received
(Response) Issued in response to a QUERY FTPD command, this message shows the number
of files sent and received for the connection being serviced by this FTP daemon.
IPN367I sent bytes sent (acked), rec bytes received
of bytes sent and received for the connection being served by this FTP daemon.
The value shown in parentheses is the number of bytes whose receipt has been acknowledged
by the remote host.
IPN368I Last type: text
(Response) Issued in response to a QUERY FTPD command, this message shows the last
command or last response that occurred on the current FTP session’s control connection.
IPN369I No FTP daemons currently active
(Response) Issued in response to a QUERY FTPD command when no active sessions are being
serviced.
IPN374I Count: dec Max: dec IP: addr Port: dec Num: dec
(Response) Issued in response to a QUERY TRACES command, this message displays the
number of records currently contained in the trace, the maximum blocks that will be retained
(SIZE= parameters), eligible IP address, eligible port number, and eligible trace number.

13.40
IPN379I Socket req dropped from part reason: code
(Info) Before moving data cross-partition, the socket mechanism determined that the original
requester is no longer in control of the partition. The cross-partition operation is discarded.
The message text includes the request type, the partition making the request, and one of the
following reasons:
Request queued to system task

Request queued to task number over 256
TIB address of requesting partition is bad
PIK of requesting partition is zero
Invalid PIK caused GETFLD to fail
Data length exceeds 64k
Partition start address is inconsistent
IPN380I Alternative IP address, ID: aaa IPAddr: bbb
(Response) This message displays an IP address that TCP/IP FOR VSE will respond to when it
receives an ARP request. The ID refers to the ID field of the DEFINE ALTID command that
created the alternate IP address.
IPN388W Warning: Errors occurred during TCP/IP Initialization
(Vital) One or more errors were detected during TCP/IP initialization processing. TCP/IP has
been able to complete initialization despite these errors.
Operator Action: Check SYSLST for specific error messages. Determine that TCP/IP FOR
VSE has initialized in a manner that is acceptable. Correct any invalid commands and issue
them manually from the console.
Administrator Action: Ensure that configuration decks are correct and that all assigned
devices and files are available.
IPN389E Security Exit phase did not load
(Response) TCP/IP FOR VSE was unable to load the security exit phase specified in a DEFINE
SECURITY command.
System Action: Execution continues with no change in security processing.

Operator Action: Ensure that the phase specified in the command exists and can be loaded by
TCP/IP FOR VSE.
Administrator Action: Review your security procedures.

13.41
IPN391I ID: aaa Member: bbb
(Response) This message is issued in response to the QUERY MENUS command. The ID field
corresponds to the menu’s name. The member names the file containing the menu’s source
code.
IPN394I Testing for an active VTAM partition
(Info) This message is issued when the WAIT VTAM command is encountered in the
initialization stream.
System Action: TCP/IP will now attempts to engage VTAM.
IPN395I Waiting for VTAM to become active
(Vital) This message is issued when the WAIT VTAM command is encountered in the
initialization stream and VTAM is not operational.
System Action: TCP/IP suspends its initialization activities until VTAM is available.
Operator Action: Ensure VTAM has been started.
Administrator Action: If TCP/IP does not require VTAM services, the WAIT VTAM
command should be removed from the initialization deck.
IPN396I VTAM is active and functioning
(Info) This message is issued when the WAIT VTAM command is encountered in the
initialization stream. An active VTAM has been detected and initialization will be resumed.
IPN397I Loading command deck name
(Response) Due to an EXECUTE or INCLUDE command, TCP/IP FOR VSE is loading the
indicated member from the library search chain. The member will be read completely before
any part of it is interpreted.
IPN398I Command deck aaa has been completely loaded
(Response) Due to an EXECUTE or INCLUDE command, TCP/IP FOR VSE has loaded the
indicated member from the library search chain. The contents of the member will now be
processed.

13.42
IPN399E Unable to load or locate command deck name
(Response) TCP/IP FOR VSE was unable to obtain the member specified in an EXECUTE or
INCLUDE command. Processing continues without the member.
Administrator Action: Ensure that the specified library member is in the library search chain
and has a type of “.L”.
IPN400I Port: num IPaddr: ip Timeout: int sec Limit: num
(Response) Issued in response to the QUERY PORTQUEUE command, this message

summarizes values in effect for a single instance of port (connection) queuing.
The values shown are the local port number, the foreign IP address (used as a filter), the time-
out value that a connection request can wait, and the maximum number of connection requests
that can be queued at one time.
IPN401I Queued: now/max/total Reject: num Good: num Lost: num

The three values for “Queued:” are the number of requests currently waiting a connection, the
largest number ever waiting, and the total connections queued since the statistical counters were
reset.
“Reject:” shown the number of connections requests that could not be queued because the
preset limit had been reached.
“Good:” indicates the number of connection requests that were queued and eventually matched
with a listen connection.
“Lost:” is a count of the connections that were terminated by the remote host while queued and
waiting for a listen connection.
IPN402I Avg wait: time msec; Avg lost: time msec; Int: interval

“Avg wait:” is the average time, in milliseconds, that each queued connection request had to
wait before being successfully paired with a listen connection.
“Avg lost:” is the average time, in milliseconds, that “lost” connections waited before they
initiated a disconnect.
“Int:” is the interval over which the statistics apply.

13.43
IPN403I Partition: id. Phase: name

The values shown are the LogID (partition identifier) and phase that last provided the values
currently in effect.
IPN405I Port queue values successfully set
(Response) Issued to indicate the successful completion of a PORTQUEUE command.
IPN406E Port queuing not changed. Error: dec Reason: dec Loc: code
(Response) Issued in response to a PORTQUEUE command, this message indicate a failure to

effect a change. The error code returned parallels those returned by the SOCKET macro
STATUS call. If the problem is insufficient storage, the reason code will contain the return
code provided by the VSE GETVIS macro. The location code will be useful to CSI Technical
Support if further diagnosis is required.
In addition to the standard socket return codes, the following codes may be displayed:
• SCBLOK not present. In general, this indicates that either TCP/IP has not yet initialized since
IPL or that an old release is executing (applicable only to the API interface).
• SCBLOK is invalid. This indicates corruption of a TCP/IP control block. Contact CSI Technical
Support for further support.
• SQBLOK not found. This code is issued when the requested stack ID is not currently running
(applicable only to the API interface).
• ASOCKET not present. This indicates corruption of a TCP/IP control block. Contact CSI
Technical Support for further support.
IPN409I Information for Link id [, Adapter num]
(Response) This message is produced in response to a QUERY ARPS command. Because

hardware (MAC) addresses are specific to each physical network segment, they are grouped by
Link and, if applicable, by adapter.
IPN410I ip > mac C: cnt
(Response) This message is produced in response to a QUERY ARPS command. ip is a TCP/IP

network address and mac is the corresponding hardware (MAC) address.
cnt is a count of the number of times that this address has been updated, either by a response to
our own request, by using information obtained when responding to an external request, or by
the receipt of an unsolicited broadcast ARP.

13.44
IPN426I Event ID: aaaaaa
(Response) An Event ID as specified in the DEFINE EVENT command that established it.
IPN427I Priority: aaaa, Order: bbbb, Script: name
(Response) This line indicates whether the automation daemon uses the POWER priority and
queue order to determine when to process an entry. The name of the script, if any, used to
process the entry is also shown.
IPN428I Class: a, Queue: bbb, Action: ccc, POWER SYSID: d
(Response) For POWER events, the class (a) and queue (bbb) where the event occurs (an event
is defined as whenever a listing is placed in the specified class and queue). The action, ccc, will
indicate LPR, FTP, or EMAIL. d is the SYSID that own the file.
IPN429I Host field: aaa, ID: bbb, Single: c
(Response) For POWER events, the JECL field (aaa) that will be inspected for the target host
or script information and the user ID (bbb) that will be used when accessing the POWER queue
during the processing of the event. (For security reasons, the associated password is not
displayed.) For Single (c), a value of “Y” indicates that LPR will single-space the report,
regardless of carriage control.
IPN430I Action: aaa, Retries: bb, Time: cc sec
(Response) The action to be taken when an event occurs. For POWER events, this action is
LPD (for use of the LPR/LPD transmission protocols), FTP (for use of the FTP transmission
protocol), or EMAIL (indicating that method of transmission). If an error occurs during
processing of this event, Retries (bb) specifies the number of times the operation is to be retried
and Time (cc) is the time in seconds between retries.
IPN431I Queue: queue POWER Name: name, Dest: dest
(Response) Issued as a response to QUERY EVENTS,DETAIL, this line displays the POWER
queue, file name, and destination of a file that is currently queued for transmittal or currently
being processed by the Automation Daemon.
IPN432I Public Name: aaaaa
(Response) The Public Name is the name by which this file is know to external (remote)
TCP/IP users. It may have been explicitly specified in the DEFINE FILE command, or it may
be the actual dataset name, if it was defined as the result of a DEFINE FILESYS command.
Note: DEFINE FILESYS has been deprecated; use the EXEC FILESYS utility instead. See the

13.45
IPN433I Type: aaa DLBL: bbb Driver: ccc
(Response) Issued in response to QUERY FILENAME, aaa is the file’s type, bbb identifies the
DLBL statement that defines the dataset. ccc identifies the driver phase that handles the I/O
operations.
IPN435I ID: id Port: port Driver: phase SSL: yes/no
(Response) The ID and Port values (decimal) are those specified by the DEFINE FTPD
command that started the daemon. Driver shows the name of the phase, running as a pseudo
task, that performs the duties of the daemon. The SSL value indicates whether the server
requires “secure” connections with this daemon.
IPN437I ID: aaaa Type: bb Dev: (cccc,cccc)
(Response) The values appearing here are those set by the DEFINE LINK command that
established the link.
IPN438I MTU: aaaa IP Address: bbbbb
(Response) The MTU size and IP address are those values set by the DEFINE LINK command
or the DEFINE ADAPTER command that established the link.
IPN439I Driver: aaaa
(Response) The driver is the name of the phase that was assigned (as a pseudo task) to drive the
link.
IPN440I ID: aaaa Type: bb Adapter: cccc
(Response) The values appearing here are those set by the DEFINE ADAPTER command that
established the link.
IPN441I MAC address: mac
(Response) For Ethernet and Token Ring links, this message indicates the MAC address by
which the adapter is addressed.
IPN442I AutoRestart: Yes/No Delay: msec Limit: times
(Response) For 3172-type links, these settings indicate what action, if any, will be taken when
the adapter initiates a STOPLAN or SHUTDOWN request.

13.46
IPN443I text
(Response) Issued as a response to QUERY EVENTS,DETAIL, this line displays possible

informational text that will indicate the current status of this event.
The text is self-explanatory.
IPN444I Print Name: name UserID: id [Hexdump Mode]
(Response) The Printer Name is the Public Name of this printer as set in the DEFINE LPD
command. The user ID is the value passed to the security exit on each call. If “Hexdump Mode”
is indicated, all listing to this print queue will be formatted as a hexadecimal dump.
IPN445I Queue: aaaa
(Response) aaaa is the fully-qualified name of the destination for listings sent to the printer
identified in the preceding IPN444I message. This name is defined as a Public Name in the
TCP/IP FOR VSE file system, either with the DEFINE FILE or the DEFINE FILESYS
command.
Note: DEFINE FILESYS has been deprecated; use the EXEC FILESYS utility instead. See the
IPN446I Library: aaaa.bbbb
(Response) The Library is a temporary area to store the listing until it is complete. This may be
either a library.sublibrary or the word “MEMORY” to indicate an in-core work area.
IPN448I ID: aaaa Link ID: bbbb
(Response) The ID field is the same as entered during execution of the DEFINE ROUTE
command that defined the route. The Link ID is the ID corresponding to the link created by the
IPN449I IP Address: ip Mask: mask
(Response) The IP address shown will be used as a pattern when selecting this route. The mask
value is the subnet mask currently being used to breakdown the IP address into its component
parts. Note that the IP address will be interpreted differently if the mask value is changed with
the SET MASK or DEFINE MASK commands.
IPN450I Net: aaaa Subnet: bbbb Host: cccc
(Response) The values shown are produced by taking the IP address, as specified in message
IPN449I, extracting the network number and applying the subnetwork mask.

13.47
IPN451I No route found for ipaddr
(Response) Issued in response to a QUERY ROUTE,ID= command, this message indicates that
the specified IP address is unreachable when using the current Route Table.
Operator Action: If it is desirable to allow access to the host identified by the IP address, use
the DEFINE ROUTE command to include an appropriate entry in the Route Table.
Administrator Action: Review your initialization parameters to ensure that the Route Table
definitions are complete and correct.
IPN452I System ID: aa
(Response) This is the unique identifying number assigned to this TCP/IP FOR VSE partition.
Other partitions running TCP/IP FOR VSE may communicate directly with this partition by
means of this number. It is also used to construct the name of the initialization member. The
value shown was coded as the operand of the ID= subparameter of the PARM= parameter on
the EXEC statement. There is no command available to set or change this value.
IPN453I IP Address: aaaa Submask: bbbb
(Response) This is the network address of TCP/IP FOR VSE and the mask that, when applied to
any address on its network, yields the subnetwork number. These values are set during
initialization by the SET IPADDR and SET MASK commands. Note that these values must not
be changed during TCP/IP FOR VSE operation.
IPN454I Link Retry Time: bbbb
(Response) The Link Retry Time is the interval, in 300th seconds, that TCP/IP FOR VSE will
pause before retrying a failed communications link. This value may be set at any time with the
SET LINK_RETRY command.
IPN455 If Inactive Link: action
(Response) Issued in response to a QUERY ROUTES command, This line indicates the next
action to take if this route matches a request, but the associated Link is unavailable.
An action of “Next Route” means that the search for a usable route continues with the next
route block. An action of “Stop” means that the IP address being routed will be reported as
“unreachable.”
Administrator Action: Use of the “Stop” attribute can be useful for situations when a
particular IP address or subnet can only be reached via a specific link. When the affected link is
unavailable, datagrams will not be redirected to routes where they are sure to fail.

13.48
IPN456I Retransmit Time: aaaa Window: bbbb
(Response) The Retransmit Time is the interval, in 300th-second units, that TCP/IP FOR VSE
will wait for an acknowledgment before retransmitting the message. This value may be changed
at any time with the SET RETRANSMIT command. The Window is the number of bytes that
will be sent to a remote host before an acknowledgment must be received. This value may be
changed at any time with the SET WINDOW command.
IPN458I Console Hold: aa Record: cc
(Response) The Console Hold value indicates whether the reply ID for TCP/IP’s partition is
forced on. This setting may be changed with the CONSOLE_HOLD command. The Record
value indicates whether summary information will be logged at the conclusion of each pseudo
task. This value may be changed with the RECORD command.
IPN459I Gateway: aa Isolation: bb
(Response) The Gateway setting indicates if will forward messages to another host. This value
can be changed with the GATEWAY command. Isolation ON prevents remote users from
initiating connections. It can be changed with the ISOLATION command.
IPN464I Type: aaaa Request: bbbb
(Response) The first field shows the socket’s type. The second field indicates the type of
request last executed by the socket.
IPN465I Port: aaaa Data Length: bbbb
(Response) The port is the decimal identifier of the local port being used by the socket
identified by the preceding IPN464I message. The data length field indicates the length
(decimal) of the data packet for send or receive operations, otherwise a zero.
IPN466I Foreign Address: aaaa Port: bb
(Response) The foreign address is the IP address of the remote partner, if any, of the socket
identified by the preceding IPN464I message. The port is the decimal representation of the port
being used at the remote end.
IPN468I id: name. D: disp off phase [ibbk]
(Response) Execution time values are displayed for a pseudo task. id: is the hexadecimal task
id. name is the phase name invoked when the task was created. The total times the task has been
dispatched is shown by disp. off is the offset within the phase (phase) to the currently executing
instruction. An optional value, ibbk, will show how many IBBLOKs the task currently owns.

13.49
IPN469I Bus num: count bytes
(Response) Issued as part of QUERY TASKS,EXTENDED, this message line shows the
number of IBBLOKs and the total storage queued on each of four busses.
This information is useful only in response to a request from CSI Technical Support.
IPN470I Dispatchable tib next
(Response) Issued as part of QUERY TASKS,EXTENDED, this message line indicates that
this particular task is dispatchable. The two values shown are the TIB of the VSE task
responsible for making the task dispatchable and the address of the next Task Block on the
dispatchable queue.
IPN471I ECB: addr Content: hex
(Response) Issued as part of QUERY TASKS,EXTENDED, this message line shows one of the
ECBs that is being waited on. The ECB’s content will be either the address of the owning Task
Block (if the high-order bit is set) or the value assigned by “POST.”
IPN472I Real ECB: addr hex Task: tkblok name
“real” ECBs that is being waited on by the dispatching engine.
Each entry will show the address and content of an ECB, along with the Task Block to be
dispatched when the ECB is posted complete. The final field is the name associated with the
task.
IPN473I Auto Security blocking by IP address status
(Response) This message indicates whether the Automatic Security Manager is blocking
system access by IP address.
IPN474I Auto Security blocking by IP address after nnn violations
(Response) The automatic security manager will now block a ip address that has more than nnn
violations. This can be reset with the ACCESS ALLOW command.

13.50
IPN475I User ID: aaaa
(Response) Lists a user ID as created by the DEFINE USER command. For security reasons,
the password is not displayed.
IPN476I Data: aaaa
(Response) The user data, as entered by the DEFINE USER command that created the user ID
entry in the preceding IPN475I message is displayed. If user data was not specified, this line is
omitted from the display.
IPN477I Task aaaa has resumed in phase bbbb. Disp: cc
(Response) Three fields are displayed. The first field is the task ID, in hexadecimal. The second
field is the phase name. The field labeled “Disp:” shows the count of the number of times that
the pseudo task has been dispatched.
IPN478I Task aaaa suspended in phase bbbb. Disp: cc
(Response) The pseudo task identified by aaaa is suspended and will not be dispatched. bbbb is
the phase being executed by the task. cc is the total number of times the task has been
dispatched since its creation.
Administrator Action: If appropriate, restart the task with the RESUME command.
IPN479I Timer remaing msec. Task: id name
currently running timers. The lines are shown in order of expiration, with the earliest entry first.
Each line also shows the task ID and task name that “owns” the time.
Note that a task can own more than one timer and that a task that owns a timer is not necessarily
waiting on it. This information is useful only in response to a request from CSI Technical
Support.
IPN480I TCP/IP for VSE log has been segmented
(Response) The console log produced by TCP/IP FOR VSE has been segmented. This is
generally in response to the console operator issuing a SEGMENT command. All data recorded
prior to this message is now available for printing.
IPN482I TCP/IP for VSE reply ID will [not] be maintained
(Response) This message is issued in response to the SET CONSOLE_HOLD command and
indicates whether the TCP/IP FOR VSE partition will force the continued display of the
communications reply ID.

13.51
IPN486E Command "value" not valid after initialization
(Response) The indicated valid console command was issued, but following completion of
TCP/IP initialization.
System Action: The command is ignored; operation continues.
Administrator Action: Some commands can only be issued prior to TCP/IP initialization.
These must be placed in a member that is processed as part of initialization.
IPN489D diagnostic text
(Diagnose=SECURITY) This message is produced when DIAGNOSE SECURITY is in effect.

The message text can be used to help track-down problems related to security call processing.
Operator Action: This message can be eliminated using the DIAGNOSE SECURITY
command.
IPN490W Unable to release required buffers. aaa remain.
(Response) This is in response to a SET TELNETD_BUFFERS command, where the value is

smaller than the existing value, and so the engine will remove any buffers from the pool that are
not in use. The system was unable to release enough unused buffers to reduce the total to the
requested number. aaaa is the number of buffers that remain allocated.
Operator Action: If the number of TELNETD_BUFFERS is too high, wait for several minutes
for the engine to free them up during a time when the stack is less active, and then re-issue the
command. If this message is issued, however, it probably indicates that your buffer pool should
not be reduced any further.
IPN491I ip-addr denied access to resource
(Security) This message is issued when using automatic security and access to a protected
resource is denied. The ip-address attempting the access and the resource requested are
identified in the message. No user-id was available at the time of the attempted access.
IPN497I user-id denied access to resource from ip-addr
(Security) This message is issued when using automatic security and access to a protected
resource is denied. The user-id attempting the access, the resource, and the requestors IP
address are included in the message.
IPN498D SCTYEXIT failed rs:xxxxxxxx offset:yyyyyyy
(Diagnose=SECURITY) This diagnostic message is issued by the automatic security when

DIAGNOSE SECURITY is used. The diagnostic information can be used to correct problems
in the automatic security logistics.

13.52
IPN499I TCP/IP processing started
(Response) This message is issued in response to a START command. The TCP/IP FOR VSE
dispatcher has resumed dispatching pseudo tasks (Daemons). Note that if the cessation of
processing has been more that a few seconds, it will be normal to lose a number of connections
and sessions due to time-outs.
IPN500W All TCP/IP processing stopped
(Critical) The command is issued in response to an operator STOP command or other command
that requires the dispatcher to be in a stopped state.
System Action: The TCP/IP dispatcher ceases all further operations until a START command
is issued.
Operator Action: Issue a START command as soon as possible.
IPN503I Symbolic Name: aaaaaa
(Response) In response to a QUERY NAMES command, the symbolic name aaaaaa is listed.
This name was created by the DEFINE NAME command.
IPN504I item: aaaaa
(Response) Issued in response to a QUERY NAMES command, this message displays the
information (IP address and script name) associated with the symbolic name appearing in the
immediately preceding IPN503I message.
IPN506I ID: a Port: b Driver: c
(Response) In response to a QUERY GOPHERDS command, this message summarizes one

Gopher Daemon. The daemon’s ID, its port number and the phase driving the daemon are
listed.
IPN507I Root: root
(Response) A continuation of message IPN506I. root is the root directory being used by the
daemon.
IPN509I ID: a Port: b Driver: c
(Response) In response to a QUERY HTTPDS command, this message summarizes one HTTP
daemon. The daemon’s ID, its port number and the phase driving the daemon are listed.

13.53
IPN510I Confine: yes/no Root: root
(Response) A continuation of message IPN509I. The value set for the CONFINE parameter is
displayed, as well as the root directory being used by the daemon.
IPN512I ID: aaa Port: bbb Driver: bbb
(Response) Issued in response to a QUERY IRCD command, this message displays the port
number and driver name for the daemon identified by the ID.
IPN514I ID: aaa Port: bbb Driver: bbb
(Response) Issued in response to a QUERY TFTPD command, this message displays the port
number and driver name for the daemon identified by the ID.
IPN516I variable = value
(Response) This message appears multiple times in response to a statistical QUERY command.
Each message shows a statistical variable and its current value.
Values may be listed with multipliers of K (1024), M (1024**2), G (1024**3), T (1024**4),

F (1024**5), and X (1024**6).
IPN518I Receive MSS: a
(Response) In response to a QUERY SET command, this message indicates the largest TCP
datagram that TCP/IP FOR VSE will accept
IPN519I Tab Char: a Escape Char: b
(Response) The Gopher Daemon is using a as a tab character and b as an escape character.
IPN521I ID: aaa Driver: bbb
(Response) Issued in response to a QUERY APPLICATIONS command, this message displays

the ID of the application and the driver program assigned to the daemon.
IPN522I Applid: aaa Type: bbb
(Response) Issued in response to a QUERY APPLICATIONS command, this message displays

the application ID and type of application supported by the daemon.

13.54
IPN524I Diagnose status for item set to ON/OFF
(Info, Response) This message displays the current status for a diagnose setting.
IPN525I Mailbox: aa
(Response) The Mailbox name, as entered with the DEFINE USER command. If MAILBOX
was not specified, this line is omitted from the display.
IPN528E Unable to define id. Object already exists.
(Response) Issued following a DEFINE command, this message indicates that an object has
already been defined with an identical ID= specification.
System Action: The DEFINE command is ignored.
Operator Action: Reenter the DEFINE command with a different value for ID=.
IPN529I Diagnose established for count. connections.
(Response) Issued in response to a DIAGNOSE CONNECTION command, this message

indicates the number of connections that met the specified criteria and were flagged for
diagnostic processing.
IPN531I Recfm: aa Lrecl: bb Blksize: cc
(Response) Issued in response to a QUERY FILE command.
IPN532I CC: aa CRLF: bb
(Response) Issued in response to a QUERY FILE command.
IPN534I ID: id Type: strb Kind:str [Scope: scope]
(Response) Issued in response to a QUERY TRACES command, this message displays the
trace ID value, the type of trace, and the kind of element(s) that are eligible.
For a socket trace, the scope of the trace is displayed, “Internal”, “External”, or “All”.
IPN535E Link driver does not collect statistics.
(Response) You issued a QUERY STATS for a link driver that does not collect statistics.

13.55
IPN536I Link driver statistics are being requested.
(Response) You issue a QUERY STATS command. The request is being passed to the
appropriate link driver.
IPN537I Gateway IP Address: aaa
(Response) Issued in response to a QUERY ROUTES command, the IP address of the

associated gateway is listed.
IPN538E Specified Link driver not found: id
(Response) You have issued a QUERY STATS,LINKID=id command. However, TCP/IP

could not find a Link Driver with the indicated ID.
System Action: The requested statistics are not displayed.
Operator Action: Re-enter the command with a LINKID that is assigned to an active Link
Driver. Use the QUERY LINKS command to obtain a list of valid Link IDs.
IPN540W Critical Storage Shortage: item
(Critical) TCP/IP was unable to obtain needed memory for the indicated item.
System Action: TCP/IP will attempt to defer the process requiring the unavailable storage until
more becomes available. This message will be re-issued at one-minute intervals until the
storage shortage is relieved.
Operator Action: Use the VSE GETVIS xx,DETAILS command and the TCP/IP QUERY
STORAGE command to display detailed information on allocated storage. If the condition
persists, you may need to restart TCP/IP FOR VSE.
If the item is “IBBLOKs” and there is still storage available, use IBBLOK STORAGE=xx or
IBBLOK PERCENT=nn to increase the amount of storage available for IBBLOK usage.
Administrator Action: Ensure that the TCP/IP partition is large enough to accommodate the
amount of processing required.

13.56
IPN541 IBBLOks being allocated from 24-bit GETVIS
(Warning) IBBLOKs are the containers used to store and move datagrams through the TCP/IP
stack. The amount of storage required for IBBLOKs varies widely, but it can consume large
amounts of partition GETVIS on active systems.
The system always attempts to allocate IBBLOKs from 31-bit GETVIS, preserving 24-bit
GETVIS for uses that require it. This message indicates that all 31-bit partition GETVIS has
been exhausted and that allocation has spilled-over into the 24-bit area.
System Action: Execution continues normally and will continue until the 24-bit GETVIS is
also exhausted. This message will be re-issued with each new allocation attempt, but not more
frequently that once per minute.
Administrator Action: Consider enlarging the TCP/IP partition to prevent possible short-on-
storage abends.
IPN542I aaa bbb ccc
(Response) This message is produced in response to the QUERY TRANSLATION command.

One message will be produced for each defined translate table. The first field will be the table’s
name. The second field will be either blank (for a single-byte character set table) or will be
“DBCS” (for a double-byte character set table). The third field will contain “Default” for the
single table that will used as the default translate table.
If the message “No matching SBCS table” appears, this means that the table is a DBCS and has
no corresponding SBCS entry. Such a table is not usable.
IPN545I GID: aaa UID: bbb Permissions: ccc
(Response) Issued in response to QUERY FILES, this message indicates the security level
assigned to the file.
IPN546I Cipher xxx active with keys from yyy phase
(Response) Issued in response to QUERY FILES, this message indicates the encryption cipher
and key phase being used for this HFS file.
IPN547W Storage Reuse Pool Release has Occurred
(Critical) TCP/IP encountered a failed request for storage but was able to satisfy its needs by
releasing free buffers.
System Action: Execution continues normally.
Operator Action: Use the TCP/IP QUERY STORAGE command to display detailed
information on storage use.

13.57
(Diagnose=IBBLOK) This message is issued when DIAGNOSE IBBLOK is in effect. The

message content can be useful in tracing a datagram’s progress through the stack.
Operator Action: This message can be eliminated by using the DIAGNOSE -IBBLOK
command.
IPN549E IPCCDROP error: err
(Vital) This message is issued when an attempt is made to release an IBBLOK, but conditions
exist that make this impossible.
The message text will indicate the reason for the failure.
System Action: The stack will abandon the IBBLOK in error and attempt to continue other
processing.
Operator Action: Be attentive to other signs of problems. Be prepared to cycle the stack if
problems persist.
Administrator Action: Capture all SYSLST output and contact CSI Technical Support.
IPN552E Unrecognized keyword on line aaa in member bbb
(Response) While processing a DEFINE MENU command, an invalid keyword was

encountered. The member name and the line in the member where the error occurred is
included in the message.
IPN553E Operand missing or too short on line aaa in member bbb
(Response) While processing a DEFINE MENU command, an invalid operand was

IPN554E Syntax error on line aaa in member bbb
(Response) While processing a DEFINE MENU command, a syntax error was encountered.
The member name and the line in the member where the error occurred is included in the
message.
IPN555E Numeric value out of range on line aaa in member bbb
(Response) While processing a DEFINE MENU command, a specified numeric value was too
large or too small. The member name and the line in the member where the error occurred is

13.58
IPN556E PF/PA key syntax is invalid on line aaa in member bbb
(Response) While processing a DEFINE MENU command, the specification of a PF or PA key

was syntactically incorrect. The member name and the line in the member where the error
occurred is included in the message.
IPN557E PF/PA key is not valid on line aaa in member bbb
(Response) While processing a DEFINE MENU command, the specification of a PF or PA key

was incorrect. The member name and the line in the member where the error occurred is
IPN558E Equal sign missing or misplaced on line aaa in member bbb
(Response) While processing a DEFINE MENU command, either an expected equal sign was
missing or an unexpected one was encountered. The member name and the line in the member
where the error occurred is included in the message.
IPN559E Variable name not recognized on line aaa in member bbb
(Response) While processing a DEFINE MENU command, an invalid variable name was
IPN560E Extra line in screen image. line aaa in member bbb
(Response) While processing a DEFINE MENU command, more than 24 lines were found in
the IMAGE area. The member name and the line in the member where the error occurred is
IPN561E Requested member, aaa, not in library
(Response) While processing a DEFINE MENU command, the requested member, aaa, could
not be located.
IPN562E I/O error or unexpected EOF while reading member aaa
(Response) While processing a DEFINE MENU command, the requested member, aaa, could
not be read or an end-of-file was reached before all 24 lines of the IMAGE area could be read.
IPN563E Not enough room for field on line aaa in member bbb
(Response) While processing a DEFINE MENU command IMAGE area, a field specification
was encountered whose length exceeds what is available on the screen line. The member name
and the line in the member where the error occurred is included in the message.

13.59
IPN564 Multiple command lines specified on line aaa in member bbb
(Response) While processing a DEFINE MENU command IMAGE area, more that one
command input area was encountered. The member name and the line in the member where the
error occurred is included in the message.
IPN565E Invalid operand value specified on line aaa in member bbb
(Response) While processing a DEFINE MENU command, an invalid value for an operand was
IPN566E GETVIS failure: RC = aaa
(Response) While processing a DEFINE MENU command, TCP/IP FOR VSE was unable to
obtain the storage necessary to save the definition.
IPN567E Character inside of command line. Line aaa in member bbb
(Response) While processing a DEFINE MENU command IMAGE area, a displayable

character was found within the area reserved for command input. The member name and the
line in the member where the error occurred is included in the message.
IPN571I Misdirect ID: aaa
(Response) Issued in response to a QUERY MISDIRECTIONS command, this line indicates

the ID assigned to the specific misdirection daemon.
IPN572I From IP: aaa To IP: bbb
(Response) Issued in response to a QUERY MISDIRECTIONS command, this line indicates

traffic that will be intercepted and possibly traced by TCP/IP FOR VSE. aaa is the address of the
sender of the intercepted traffic and bbb is the intended destination for the traffic.
IPN575I Network: ip (dec) Mask: mask
(Response) Issued in response to a QUERY MASKS command, this line shows the network
number and the subnet mask that will be used for this network.
IPN577I Mode: aaa Record Counter: bbb
(Response) Issued in response to a QUERY OPENFILES command, this line indicates the
file’s mode and the total number of records processed.

13.60
IPN578E Unable to close: aaa
(Response) Issued in response to a CLOSE FILE command, this message displays the Public
Name, aaa, of a file that could not be closed.
IPN579I A close request has been queued for: aaa
(Response) This message indicates that an open file will be closed, in response to a CLOSE
FILE command.
IPN581I object id has been deleted.
(Info) In response to a DELETE command, the indicated object identified by id, has been
deleted.
IPN582I ipaddr type [linkid]
(Response) The first field consists of an IP address that is considered to be a home address. The
second field shows the type of address:
• Main: Indicates the value established by SET IPADDR=. “Link:” Is shown if the value is being
used by a Link Driver.
• ARP: Indicates that the value was set by DEFINE ALTIP. IP addresses with this attribute will be
answered when ARP’ed, but will still be routed according to the Route Table.
IPN586W Console Port can only be specified during startup
(Info) A SET CONSOLE_PORT command was issued after TCP/IP FOR VSE initialization
completed. This command is available only during system initialization.
Note: The SET CONSOLE_PORT command as been deprecated.
IPN587I Pause interval: aaa (bbb Seconds)
(Response) Issued in response to a QUERY EVENTS command, this message displays the
current value of the pause interval. This is the interval that the Automation Daemon sleeps
when all work has been processed. Once this period has elapsed, the daemon scans for
additional work.
IPN591I Overrun adjustment: aa bytes
(Response) Issued in response to a QUERY LINKS command, this message displays the value
of the overrun adjustment. This adjustment is made when an overrun of the adapter is detected.

13.61
IPN592E Link Device improperly defined in PUB Table
(Critical) During initialization of a link driver, TCP/IP has determined that the specified device
is incorrectly defined to VSE.
System Action: The link driver is defined; however, proper execution is unlikely.
Operator Action: You may continue execution, but expect I/O errors on the link device.
Administrator Action: Correct your VSE device definition to exclude the Missing Interrupt
Handler (MIH).
IPN594W Authorization for function has expired. / will expire on date
(Info) This message is issued once per day when any TCP/IP product key is within 30 days of
expiration. Additional information can be obtained by issuing the QUERY PRODKEYS,ALL
command.
System Action: None. Operation continues. Any TCP/IP function that has already been
initialized will continue to operate. However, if the TCP/IP partition is cycled, expired
functions will NOT initialize.
Operator Action: Notify the System Administrator immediately. The 30-day countdown is
designed to allow sufficient time to obtain and install new product keys without operational
disruption. Note that once the expiration date has been reached, TCP/IP cannot be restarted.
Administrator Action: Obtain and install new product keys for the expiring products. If this
message is being displayed for a product that you do not license, then remove the extraneous
product key and re-generate your PRODKEYS phase.
IPN595I ID: aa Type: bb Driver: cc
(Response) Issued in response to a QUERY CAF command, this message displays a CAF
daemon’s ID, the type of daemon, and the driver phase. Note: This command is deprecated.
IPN596I Applid: aa State: bb
(Response) Issued in response to a QUERY CAF command, this message displays a CAF
daemon’s applid, and the daemon’s current state. Note: This command is deprecated.

13.62
IPN597I Shutdown Stage: aa, Performing: bb other info
(Info) TCP/IP is in its shutdown phase. It will close-down in an orderly fashion, terminating
connections and cleaning-up as appropriate.
There are 15 stages of termination. Each stage will take a varying amount of time to complete.
In each case, TCP/IP will move to the next step when the previous step completes, or if it fails
to maintain progress to completion.
System Action: Termination continues.
Operator Action: Be patient. Issuing a CANCEL will result in the cleanup being deferred to
the start-up phase. It may also result in a required IPL for TCP/IP restart.
IPN599E Valid Product code for product not found or expired
(Vital) The indicated subcomponent of TCP/IP will not execute because no valid authorization
code could be located.
System Action: TCP/IP continues execution without the unauthorized component.
Administrator Action: Ensure that a valid authorization code is present and in the TCP/IP
partition’s search chain.
IPN600I TCP/IP API Translator -- Version aa, bb
(Info) This message is displayed when the API translator starts. The version and service level
are shown.
IPN601I Copyright 1995, 2008 (C) Connectivity Systems Inc.
(Info) Product copyright date.
IPN602I TCP/IP Language Translator -- Complete
(Info) The language translator has completed.
IPN603E TCP/IP Language Translator -- Failure
(Vital) One or more errors have cause the translator program to terminate in failure.
Administrator Action: Examine the listing for additional messages.

13.63
IPN604W Parameter errors found
(Warning) The translator has completed processing the EXEC card PARM information, and
encountered errors.
System Action: The translator will terminate.
Operator Action: Correct the execution parameter and re-run the job.
IPN605I Processing the execution PARM override
(Info) The translator is beginning to examine the information in the EXEC card PARM field.
IPN606I Processing of PARM override complete
(Info) The translator has completed processing the EXEC card PARM information.
System Action: The translator continues.
IPN608E PARM LANG=name not specified correctly
(Vital) While processing the EXEC card PARM information, the translator was unable to
identify a supported language name.
Administrator Action: Correct the language specification and resubmit.
IPN609E 'COBOL', 'RPG', 'C', 'Assembler' OR 'PL/1' missing
identify a supported language name.
Administrator Action: Correct the language specification and resubmit.
IPN610E PARM ENV=name not specified correctly
(Vital) While processing the EXEC card PARM information, the translator was unable to parse
the environment type.
Administrator Action: Correct the environment specification and resubmit.

13.64
IPN611E 'CICS' or 'batch' missing
determine the environment type.
Administrator Action: Correct the environment specification and resubmit.
IPN612I Debugging set to ON
(Info) Based on PARM field information, the translator has entered debugging mode.
System Action: The translator will continue, generated output will vary.
IPN613I SYSPCH will be redirected to non-UR device
(Info) This message is displayed when the API translator starts and SYSPCH is assigned to
DISK or TAPE.
IPN614I WAIT text will not be generated within source
(Info) Based on PARM field information, the translator will suppress the generating of WAIT
commands due to USEWAIT=NO
System Action: The translator will continue, producing additional messages.
IPN615I WAIT text will be generated within source
(Info) Based on PARM field information, the translator will generate WAIT commands due to
USEWAIT=YES
IPN616E Invalid parameter setting: value
(Vital) The EXEC TCP (type) statement contains a request with a specific parm, but it does not
contain a correct value “(xx)”.
System Action: The translator will terminate processing.
Operator Action: Correct the invalid statement.
IPN617I ID: aa Cipher: bb
(Response) In response to a QUERY TLSD command, this message displays the ID of the
daemon and cipher suite used for key exchange, encryption, and message authentication.

13.65
IPN618I Port: aa Passport: bb
(Response) Issued in response to a QUERY TLSD command, this message displays the secure
port being monitored and the port to which decrypted data will be sent.
IPN619I Driver: aa Minimum version: bb
(Response) Issued in response to a QUERY TLSD command, this message displays the name
of the driver phase, and the minimum version of the TLS/SSL protocol that clients are allowed
to use when connecting to this server.
IPN622W OPEN/CLOSE task abend. Code: aa
(Info) The VSE subtask that handles the synchronous VTAM OPEN and CLOSE requests has
abended. The hexadecimal abend code is displayed. VSE will automatically close all VTAM
sessions when the subtask terminates. All TN3270 and GPS sessions will then be terminated.
System Action: TCP/IP re-attaches the subtask and continues.
IPN624I Data Port aa
(Response) The Data Port value as specified in the DEFINE FTPD command.
IPN625E Insufficient LOC=BELOW GETVIS to continue
(Vital) The translator was unable to acquire any GETVIS that it needs to store SYSIPT into
partition GETVIS.
Operator Action: Run the translator in a larger partition.
IPN627I EXEC CICS TRACE will be inserted into source
(Info) Based on PARM field information, the translator will generate EXEC CICS TRACE
because TRACE=YES
System Action: The translator will continue and will produce additional messages.
IPN631I Control has been passed to the TCP/IP engine
(Info) TCP/IP has completed its configuration and will now begin processing under its multi-
tasking engine.

13.66
IPN632E FRBLOK at addr is incorrect. Request posted complete w/ error
(Info) During recovery from a File I/O error, it was determined that one of the queued requests
is invalid.
System Action: The request is removed from the chain, and the requesting program is notified
that the request has failed.
Operator Action: Look for other messages that may indicate how this failure has affected
other parts of the stack.
IPN633E EMAIL control block not present or corrupt
(Critical) This message is issued in response to the EMAIL or QUERY EMAIL command. It
indicates that the internal control block is not present or has been corrupted.
System Action: The command is suppressed.
IPN634E Duplicate ECB. foreign-IP,port local-IP,port) ECB: ecb
(Important) A socket request received by TCP/IP specifies an ECB already assigned to an in-
flight request. this message identifies the connection by displaying the foreign and local IP
addresses and ports. Also shown is the address of the ECB being reused.
System Action: The request with the duplicate ECB will be rejected.
Administrator Action: Determine the application issuing the request and correct the program
logic. Ensure that programs making socket request are re-entrant, where appropriate, and that
WAIT operations are correctly being issued.
IPN635I Called from addr Program: name Offset: value
(Important) This message is displayed in addition to IPN635I when a duplicate ECB condition
occurs within a CSI-provided routine, operating within the stack partition.
Operator Action: Capture SYSLST before contacting CSI Technical Support.
IPN636I phase start length entry owner attr
(Response) Issued in response to a QUERY PROGRAMS command, this message summarizes

one program. The message displays the phase name, memory start location, length, and entry
point address. In addition, the owning p-task ID is shown. The phase’s attributes may include
“RENT” for re-entrant, or “SVA” if the phase is in SVA storage.

13.67
IPN637 I/O request requeued from offset hex in program
(Important) During error recovery, the File I/O task examines each outstanding I/O request.
This message is issued for each request and summarizes the requesting program and the offset
within the program where the request originated.
IPN638E I/O driver name shutdown returned code hex
(Important) Following a driver shutdown request, the named I/O driver returned a non-zero
code.
System Action: Processing continues and the driver is assumed to have shutdown.
Administrator Action: If the I/O driver is provided locally, ensure that its internal structure is
correct. Otherwise, contact CSI Technical Support.
IPN639E I/O Driver name has no shutdown routine.
(Important) While attempting to shutdown a file I/O driver, TCP/IP was unable to locate the
address of the shutdown routine.
System Action: Execution continues without shutting-down the routine.
IPN640I type Driver: phase Entry: addr Use: count
(Response) This message is issued in response to a QUERY FILEIO command and lists
information about one file type.
The type is the symbolic type name. This is the type assigned to each file by the DEFINE FILE
command.
The name of the loaded phase and its entry point address are also shown. The “Use” field
indicates the number of processes currently being handled by the driver.
IPN641E File I/O type "name" is unknown
(Important) This message is issued when a process requests that a File I/O driver be made
available for a file type that is not recognized by TCP/IP FOR VSE.
System Action: An error is returned to the calling process.
Operator Action: Examine any additional messages for information as to what process made
the failing request.
Administrator Action: This error should not occur unless an installation-provided process
makes an incorrect request or a version mismatch between TCP/IP phases is encountered.

13.68
IPN642E Driver name: name does not match internal name: name
(Important) During I/O driver shutdown processing, it was determined that the driver’s name
does not match the one internally coded.
System Action: The driver is not shutdown.
IPN643E File type "type" is already assigned to phase
(Response) An attempt was made to define a File I/O driver for the indicated file type.
However, this file type is already being processed by the indicated driver phase.
System Action: The new File I/O definition fails.
Operator Action: You must delete the old file I/O driver before a new one can be defined for
this file type.
IPN644E File I/O driver "phase" could not be loaded.
(Response) The phase specified on a DEFINE FILEIO command failed to load.
System Action: Processing continues without the File I/O definition.
Operator Action: Examine any other message to determine the cause of the failure. Typical
reasons include a misspelling of the name, an incorrect library search chain, and insufficient or
fragmented partition GETVIS.
IPN645E File I/O driver "phase" in use by count processes. Delete failed.
(Response) A command was entered to delete the named File I/O driver phase. However, one or
more processes are currently using this driver.
System Action: The delete fails and the driver continues to process.
Operator Action: Ensure that all use of the driver has ended before retrying the delete.
IPN646E File I/O driver "name" could not be found.
(Response) This message is issued in response to a DELETE FILEIO command. TCP/IP was
unable to locate the requested File I/O driver, indicated in the message.
Operator Action: Check for a misspelling of the name. Use the QUERY FILEIO command to
see a list of all File I/O drivers that are currently loaded.

13.69
IPN647I File I/O driver "name" deleted.
(Response) This message is issued in response to a DELETE FILEIO command and indicates
successful deletion of the named File I/O driver.
IPN648I File I/O driver phase for type type loaded at addr
(Response) This message is produced each time a file I/O driver is loaded and activated.
Operator Action: If other messages (from the I/O driver) indicate a problem, it may indicate
that the driver will need to be deleted and redefined.
IPN649E File I/O driver name failed to initialize. Reason: text
(Vital) The indicated File I/O driver was loaded but could not be initialized. The message text,
and additional message produced by the Driver, will indicate the reason.
Operator Action: Correct the problem, delete and reload the Driver.
IPN651I xxx translation tables being loaded from yyy
(Response) The Single Byte (SBCS) or Double Byte (DBCS) Character Set translation tables
are being loaded from library member yyy.
IPN652I Table xxx enabled for DBCS translation
(Response) The named translation table has been successfully prepared for use with Double
Byte Character Sets.
IPN654I Translation table created: xxx
(Response) A translation table has been successfully loaded and is accessible by the name xxx.
IPN655I Translation table replaced: xxx
(Response) A translation table has been successfully loaded and is accessible as name xxx. This
table replaces a previously loaded table of the same name.
IPN656I SBCS Table loading complete for member xxx
(Response) The indicated member has been completely processed, and all eligible translate
tables have been loaded.

13.70
IPN657I Default xxx translate table set to yyy
(Response) In response to a DEFINE TRANSLATE command, a default value for translation

(either SBCS or DBCS) has been set.
IPN658E Specified translate table not found. Default unchanged.
(Response) An attempt to set a default translation table has failed because the requested table
has not been loaded.
IPN659E Could not locate SBCS member xxx
(Response) A DEFINE TRANSLATION command has been entered but the specified member
could not be found.
IPN661E Insufficient GETVIS to load SBCS table
(Response) The system was unable to obtain sufficient storage to load an SBCS translation
table.
Operator Action: Due to the relatively small amount of space required for an SBCS translate
table, the TCP/IP partition will probably fail shortly.
Administrator Action: Examine how much storage is available for the TCP/IP partition.
IPN662E Invalid record in SBCS member xxx
(Response) While processing the specified translation table member, an invalid record was
encountered. This message is followed by IPN663E.
Administrator Action: If the translation table member was provided by CSI International it
may indicate library corruption or a faulty installation.
IPN663E text
(Response) This message follows IPN662E and contains the card image that contains the error.
IPN666E Unexpected end-of-file in member xxx
(Response) TCP/IP encountered a premature end-of-file while processing the indicated

translate table member.
System Action: System execution continues without the failing translate table.
Administrator Action: If the failing table is locally generated, ensure that its structure is
correct and retry. If the failure occurred while processing a table provided by CSI International,
it may indicate damage to the library or a faulty installation.

13.71
IPN667E Table name missing in member xxx
(Response) While processing a DEFINE TRANSLATE command, the system could not locate
the requested translate table.
IPN668E ID field missing in member xxx
(Response) While processing the specified SBCS translation table member, TCP/IP could not
locate the record that contains its character set IDs.
Administrator Action: If the translation table member was provided by CSI International, it
IPN669E One of the specified tables was not found
(Response) While processing a DEFINE TRANSLATION command to load a DBCS table,

TCP/IP could not locate one of the requested code pages.
Administrator Action: Ensure that the DBCS member contains both requested code pages.
IPN670E Duplicate table names in member xxx

TCP/IP noted that the code pages did not have unique names.
IPN671E xxx record missing from member yyy

TCP/IP noted that the specified record with identifier xxx is missing.
IPN672E Range between LOW and HIGH is invalid

TCP/IP noted that the range of values between LOW and HIGH is invalid.

13.72
IPN673E Field aaa bbb on record ccc of member ddd

TCP/IP noted an error on record number ccc in the DBCS member ddd. aaa is the data field that
is in error and bbb will indicate the nature of the error.
IPN674E Member name not specified.
(Response) A DEFINE TRANSLATION command has been entered but it did not contain a
member specification.
IPN676I DBCS translate table xxx has been yyy
(Response) The named Double-Byte Character Set (DBCS) translate table has been either
created or replaced.
IPN677E NAME= specified without ENTRY=
(Response) While processing a DEFINE TRANSLATE command, the NAME= parameter was
used without a value for ENTRY=.
Operator Action: Respecify the command without the NAME= parameter or with a values for
both ENTRY= and NAME=.
IPN679I EXEC CICS TRACE will not be added to source
(Info) Based on PARM field information, the translator will suppress the generating of EXEC
CICS TRACE due to TRACE=NO
IPN680E An error occurred. Check SYSLST/SYSPCH
(Vital) The language translator has completed. It is about to generate output but an error
occurred. It will continue to punch data to SYSPCH and will echo it to SYSLST.
System Action: Program terminates with a non-zero return code.
Operator Action: Refer to the output. Look for a “=======>” eyecatcher that will prefix each
error message.

13.73
IPN681I IPNETPRE.L - value has been set
(Info) The translator loaded the IPNETPRE.L file and has applied the default setting indicated
in the message.
IPN694W message text
(Warning) The parameter list passed to the common translation routine failed for any number of
reasons. The reason is listed in the message text.
System Action: The translation process will fail if it is unable to determine a possible default to
use in place of the erroneous parameter.
Operator Action: This is most likely a CSI application error. Report this to CSI Technical
Support if it occurs very often.
IPN700I TCP/IP Command Processor -- Version aaa, bbb
(Important) This message is issued from the batch command interface. The message text
identifies the version and service level of the module.
Administrator Action: Be sure that you are running the appropriate version, compatible with
the target TCP/IP partition.
IPN701I Copyright dates (C) Connectivity Systems Inc.
(Info) This is the software copyright notice.
IPN702I TCP/IP Command Processor -- Complete
(Info) This message is issued from the batch command interface. It indicates that the command
processor has completed all requests.
System Action: The batch command processor terminates.
IPN703E TCP/IP Command Processor -- Failure
(Important) This message is issued from the batch command interface. It indicates a failure
during the initialization phase has occurred.
Administrator Action: Look for additional messages to determine the exact cause of the
failure.

13.74
IPN704E Parameter errors found
(Info) This message is issued from the batch command interface. It indicates that one or more
values specified in the EXEC card PARM field are invalid.
Operator Action: Check for additional message and correct the PARM values before
resubmitting the job.
IPN705I Processing the execution parm override
(Info) This message is issued from the batch command interface. It indicates that the EXEC
card PARM values are about to be examined.
IPN706I Processing of parm override complete
(Vital) This message is issued from the batch command interface. It indicates that the
information specified on the EXEC card PARM information has been processed.
System Action: Execution of commands proceeds.
IPN707W Unidentifiable information found in PARM: aaa
(Warning) This message is issued from the batch command interface. It indicates that
unrecognizable data was found in the EXEC card PARM information. In the message text, aaa
are three characters that could not be interpreted.
System Action: The program iterates one character to the right and rescans for recognizable
data.
Administrator Action: Correct the invalid data.
IPN708I Debugging set to On
(Info) This message is issued from the batch command interface. It indicates that DEBUG=ON
was specified in the EXEC card PARM information. While in debugging mode, the commands
are parsed but NOT passed to the TCP/IP partition for execution.
IPN710E Error occurred during command processing: aaa
(Vital) This message is issued from the batch command interface. It indicates that an error
occurred while parsing a command. The message text should give an indication of the problem.
System Action: Execution of additional commands may proceed, depending on the severity of
the error.

13.75
IPN711I Loading command deck aaa
(Info) This message is issued from the batch command interface. You have included an EXEC
or INCLUDE command in your input stream. The batch command processor will fetch the
indicated member.
The member will be fetched using the batch partition’s search chain.
IPN712I Command deck aaa has been completely loaded
(Info) This message is issued from the batch command interface. You have included an EXEC
or INCLUDE command in your input stream. The batch command processor has fetched the
indicated member and will now proceed with execution.
Note that the member was fetched in the batch partition, using the batch partition’s search
chain.
IPN713E Unable to load or locate command deck aaa
(Critical) This message is issued from the batch command interface. You have included an
EXEC or INCLUDE command in your input stream. The batch command processor attempted
to fetch the indicated member but could not.
The member is fetched in the batch partition using the batch partition’s search chain.
IPN714E System ID is set to aa
(Vital) This message is issued from the batch command interface. It indicates that the ID=
parameter was specified in the EXEC card PARM information. However, the syntax was
invalid.
System Action: Execution of commands is suppressed.
Operator Action: Ensure that the ID= parameter specifies exactly two decimal digits.
IPN715I System ID is set to aa
(Info) This message is issued from the batch command interface. It indicates that ID=aa was
specified in the EXEC card PARM information.
System Action: All commands will be sent to the TCP/IP partition identified by aa.

13.76
IPN717E FLUSH command only available through console.
(Info) This message is issued from the batch command interface. You have included a FLUSH
command in your input stream. The batch command processor cannot be used to issue this
command.
Operator Action: Use the console interface to issue the FLUSH command.
IPN750I function: status
(Response, Security) This message is issued in response to a QUERY SECURITY of

SECURITY command. It indicates a specific security function and its current status.
IPN751I type data: string
(Response, Security) This message displays the current contents of the data string passed to the
Security Exit or automatic security routine on each call.
Operator Action: This string can be modified by the SECURITY command.
IPN752I Security Mode: mode Log: option Dump: option
(Response, Security) Issued in response to a SECURITY or QUERY SECURITY command,

this message displays the current security operating mode and what will be logged and dumped.
In “warn” mode, security failures are eligible for logging, but will be allowed. In “fail” mode,
security failures will prevent operations from being completed.
Logging option “none” prevents the results of security inquiries from being logged. An option
of “fail” causes only failed security attempts to be logged. “All” results in the logging of all
security failures, including those that occur while in warn mode.
The “dump” option works in the same manner as “log” but provides significantly more
information than simple logging. A dump, however, consumes much more space in the log.
IPN754E Security change denied
(Response, Security) A SECURITY command was issued to modify a setting or change the
status of security processing. However, previous to this a SECURITY LOCK command had
been issued.
System Action: TCP/IP continues with previously set security settings.
Operator Action: You must restart TCP/IP before you will be permitted to change any security
setting.
Administrator Action: If you include the SECURITY LOCK command in your initialization
parameter member, be sure that you have a method for bypassing the command in an
emergency.

13.77
IPN755I status type function value proto fport file path
(Security) This message indicates the status of a security check. The fields are as follows.
status is based on the security exit’s return code: “Pass”, “Fail,” or “Warn.”
type indicates the type of security request processed: “Unkn,” “Exit,” “File,” “User,” “IP,”
“CMD,” or “Mac.” (“Unkn” typically indicates a serious problem—the security exit is probably
back-leveled.)
function is the function request that came in. This is a string of characters that is passed from
one of the many TCP/IP FOR VSE clients and servers to the security exit. For example, “ICMP”
indicates that the request came from the daemon that received a “PING,” which was an ICMP
request (and different from TCP or UDP).
The remaining fields in the message text are based on the type:
For type = value is ... proto is ... fport is ... file, path
“File” User ID IP address Remote port File name and
number path
“User” User ID IP address Remote port
number
“IP” IP address Protocol (TCP,
UDP, ICMP)
“CMD” IP address
“Mac” MAC address
Operator Action: This message is used to debug or validate security issues. If there are no
issues, then you may want to use the MESSAGE command to suppress this message.
Otherwise, review the output and make decisions that are appropriate for your site.
IPN756E Conflicting options specified.
(Response) The command just entered specified two or more options that are inconsistent with
each other.
System Action: The command may not have been completely or correctly processed.
Operator Action: Determine the error, and if necessary enter corrective commands.
IPN757E The exit name could not be changed.
(Response) An attempt to change the name of the phase to be used as the security exit has
failed.
Operator Action: Ensure that the security exit is not already running and that the specified
phase exits and is accessible to the TCP/IP partition.

13.78
IPN758W Security settings have been LOCKED
(Security) Issued in response to a SECURITY LOCK command, this message indicates that all
TCP/IP security settings have been locked to there current settings.
Operator Action: Any changes to TCP/IP security settings will require that the stack be
restarted.
Administrator Action: If you include the SECURITY LOCK command in your initialization
parameter member, be sure that you have a method for bypassing the command in an
emergency.
IPN759I Security status change: item
(Security) This message indicates a status change in security processing.
Administrator Action: Each occurrence of this message should be evaluated for evidence of a
security breach.
IPN800I Event scheduled for deletion: xxx
(Response) Issued in response to a DELETE EVENT command, the indicated event has been
flagged for deletion. Deletion of the event will not occur until the automation daemon
completes any “in-flight” processes.
IPN801I Message suppression updated for: xxx
(Response) Issued in response to a MSGSUPPRESS command, the indicated message ID has

had its suppression criteria updated.
System Action: The system will now handle the indicated message in the manner specified.
IPN802E Message not in table: xxx
(Response) Issued in response to a MSGSUPPRESS command, the indicated message ID could

not be found in the messages table.
System Action: No changes to message suppression are made.

Operator Action: Ensure that the indicated message ID is valid. A very few messages are not
generated through the internal message facility and cannot be suppressed.
IPN804I Telnet translation will use xxxx
(Response) Issued in response to a SET TELNET_TRANSLATION or QUERY SET

command, this message indicates the translation table that will be used by the Telnet Client.

13.79
IPN805I Diagnose on for: xxx
(Response) Issued in response to the QUERY DIAGNOSE command, this message reports all
currently enabled diagnose conditions.
IPN806I item: status item: status
(Response) This message indicates the on/off status of the indicated variables.
IPN807W Unable to request program: phase name rc=value
(Warning) The SOCKET CONTROL process attempted to find an external program that should
have been loaded during the TCP/IP initialization, but the program just wasn’t there.
Operator Action: Check the TCP/IP search chain to make sure that the module exists. If not,
then restore it from your installation job stream.
IPN808D Closing protocol connection to the server
(Diagnose=DNC) The Domain Name Client has completed its communication with the DNS
server. It is now issuing a SOCKET CLOSE connection.
Operator Action: To eliminate this message, issue the DIAG -DNC command.
IPN809D Server UDP connection timed out. Resending Request.
(Diagnose=DNC) The Domain Name Client sent a request to the DNS server using the UDP
protocol, but it never got a reply.
System Action: Retry the same UDP connection for a total of no more than three times. If it
still fails, go to a backup server or a different protocol.
IPN810D Server connection was refused or terminated.
(Diagnose=DNC) The Domain Name Client sent a request to the DNS server, but the
RECEIVE process failed due to the server cutting the connection, or due to a problem in the
network.
System Action: The DNS client will mark this specific server with this specific protocol
unusable. It will try a backup server and protocol combination. It will attempt to try the failing
combination again after 20 minutes or more has elapsed.

13.80
IPN811D Sending a query to the DNS server - (protocol)
(Diagnose=DNC) The Domain Name Client is sending a query to the DNS server with a
specific protocol. The SOCKET SEND is in process.
IPN812I item value
(Response) This line is issued several times in response to a QUERY FRAGMENT command.
It summarizes a variety of statistical values that relate to the fragmentation of datagrams at the
IP level. The displayed values and their meanings follow:
Value Meaning
Pending Fragments This value is the total fragments that have been received and have
not yet been used or discarded.
Pending Datagrams This value is the total number of separate datagrams that are
currently being constructed from fragments as they arrive.
Total Fragments The total datagram fragments that have been received by the stack
since initialization.
Total Reassembled This is the total number of datagrams that have been successfully
assembled from fragments since the stack was initialized.
Total Used This value shows the total number of fragments that were used in
the construction of datagrams since the stack was initialized.
Total Expired This is the number of fragments that were discarded without being
used because too long a time interval elapsed without being able to
complete a full datagram.
Total Duplicates This is the number of fragments that were discarded without being
used because we already had an exact copy in memory. This
happens when a retransmission of a the original datagram (and all
its fragments) occurs.
Total Invalid This is the number of fragments that were discarded because they
were found to have invalid flags or other internal values. If this
value is large, it indicates a malfunctioning host, router, or gateway.
IPN813D Allocated bytes for reason
(Diagnose=DNC) The Domain Name Client has been invoked and needs to allocate storage to
process a request.

13.81
IPN814I Invalid DNS call: function
(Important) The Domain Name Client was passed a parameter list with an invalid call request.
This is probably a problem in the invoking program.
Operator Action: If the problem persists, contact CSI Technical Support.
IPN815D DNS lookup for type-Records domain
(Diagnose=DNC) The Domain Name Client will be resolving a domain name in order to
produce a specific kind of record. The message show the type of record and the name of the
domain that will be invoked.
IPN816D Found: data (type)
(Diagnose=DNC) The Domain Name Client received a response from the DNS server, and so
the data information and the type of information are displayed.
IPN817D Reqs:nnn Ans:nnn Auth:nnn Info:nnn
(Diagnose=DNC) The Domain Name Client received a response from the DNS server. Here we
will list the number of records that are contained within the response datagram.
IPN819D Found: request IP=ipaddr Local/Remote
(Diagnose=DNC) The Domain Name Client will indicate the type of request that is being
issued, the IP address, and whether the data was obtained locally, from the DEFINE NAME
statements, or from a DNS call.
IPN823D Domain Name Client invoked
(Diagnose=DNC) A request has been made to the Domain Name Client (DNC).
This message is issued only when DIAGNOSE DNC is in effect.

13.82
IPN824W DNC GETVIS Failure: aaa
(Warning) The Domain Name Client was unable to obtain enough storage to process a request.
System Action: The request is completed with a “not found” result.
Administrator Action: This message indicates a serious storage shortage in the TCP/IP
partition.
IPN825D Using DNS at aaa - (protocol)
(Diagnose=DNC) The Domain Name Client will be using the DNS at IP address aaa, and the
designated protocol (UDP or TCP) will be used for the I/O.
IPN827D text
(Diagnose=DNC) The Domain Name Client is operating with SET DIAG=DNC, and so
additional messages are being produced. This message number produces some generic data that
can be used for debugging purposes. It is a catch-all message for all DNS information.
IPN828D DNC Socket Error. aaa bbb ccc Code: ddd
(Diagnose=DNC) An error occurred while connecting with the DNS. In the text, aaa will
indicate the failing socket operation, bbb shows the connection type (UDP or TCP). ccc will be
“Schedule”, to indicate that the request could not be scheduled, or “Completion” to indicate a
completion error. ddd is the decimal return code. To interpret the code, see IPN950I Socket
Scheduling Codes and IPN951I Socket return codes (SRCODE).
IPN831W OPEN/CLOSE subtask reattached
(Critical) The true subtask responsible for performing VTAM OPEN and CLOSE operations
has terminated and been re-attached. The operating system will terminate all VTAM sessions.
System Action: Execution continues.
IPN834I SMTP Server: text : ipaddr
(Response) This line provides the server domain name and, possibly, the actual IP address. If
the server has never been used, the IP address will be “0.0.0.0”. If the server has been used, then
it will be set to the actual value.

13.83
IPN835I UserID: id
(Response) This line shows the user ID that will be used to access the SMTP server.
IPN836I item: text
(Response) This line displays various default values that will be used in constructing e-mails.
There values are used unless overridden.
IPN838I Truncate: yes/no AtSign: xx GMT: +/-hh:ss
(Response) This line displays various default values that will be used in constructing e-mails.
The GMT value is a generic override for e-mail only, and if not set it will display the value of
“(System)”, indicating that the VSE GMT offset will be used.
IPN840I Translation table (xx) : yy
(Response)
IPN842I DBlocks: aaa
(Response) Issued in response to QUERY FILES, this message indicates the number of
DBLOCKS allocated to a file of type DSPACE.
IPN844I type mode recfm mimetype
(Response) This message displays one line from the External Names Table (EXTTYPES.L)
currently being used to assign file attributes based on file name extensions. In the message, type
is the file extension (for example, TXT or HTML). The transfer mode (for example, BIN or
TEXT) is shown by mode. recfm is the record format (FB, S). The final field shows the MIME
content-type header used to encode a file for e-mail transmission and HTTP.
For more information on how file type entries in EXTTYPES.L control file transfer values, see
the TCP/IP FOR VSE Installation Guide, chapter 6, “Configuring FTP Clients and Daemons.”
IPN845D DNS response time (CPU secs): nnn
(Diagnose=DNC) A request was sent to the DNS server, and a response was received. This
message shows the number of CPU seconds that it took to perform the request (1 CPU second =
1/300th second clock time).

13.84
IPN846D Waiting for an answer. Max Time=nnn cpu secs
(Diagnose=DNC) The Domain Name Client send a request to the DNS server. Is it now issuing
a SOCKET RECEIVE to get a response.
IPN847I Unable to initiate DIAGNOSE for id
(Response) TCP/IP was unable to activate a specific DIAGNOSE command. In the message
text id is the identifier of the specific daemon for which the DIAGNOSE was issued.
System Action: DIAGNOSE status remains unchanged.
Operator Action: Make sure that the specified daemon is running.
IPN848D DNS reverse lookup requested for: ipaddr
(Diagnose=DNC) The Domain Name Client was asked to perform a special GetHostByAddress
request in order to obtain the name that is associated with that address. This method of getting
such inconsistent data is called a reverse lookup.
IPN849W IPNACONT waiting for IPNET initialization
(Warning) The SOCKET CONTROL process attempted to locate the IPNADNSC program that
should have been loaded during the TCP/IP initialization, but the program wasn’t there yet.
System Action: IPNACONT will wait until the program is available for a maximum of 2 min.
IPN850I IPNACONT waiting is complete
(Info) The SOCKET CONTROL process attempted to locate the IPNADNSC program, but it
had to wait awhile. This message says that the waiting is over and that IPNACONT is
continuing.
Operator Action: None. Operational only.

13.85
IPN851I Socket request dropped: No PCB. foreign local phase logid
(Info) While TCP/IP was attempting to access socket-related control blocks in an external
partition, it could not find an address for the PCB.
The message text includes the foreign IP address and port, the local port, the phase that issued
the request, and the logid of the requesting task.
This message usually means that the requesting program has terminated while the socket
request was in-flight.
System Action: The connection is closed, and all pending requests are flushed without altering
storage in the external partition.
IPN852I Socket request dropped: No COMREG. foreign local phase logid
partition, it could not find an address for the external partition’s COMREG.
The message text includes the foreign IP address and port, the local port, the phase that issued
the request, and the logid of the requesting task.
IPN853I Socket request dropped: COMREG has changed. exp/found foreign local phase
logid
partition, it discovered that the address for COMREG had changed since the original request
was issued. The expected and found values are included in the message text.
The message text also includes the foreign IP address and port, the local port, the phase that
issued the request, and the logid of the requesting task.

13.86
IPN854I Socket request dropped: PHASE has changed. fndphase foreign local phase logid
partition, it discovered that the address for COMREG had changed since the original request
was issued. The found phase name is included in the message text.
This usually means that the requesting program has terminated while the socket request was in-
flight.
IPN855I Socket request dropped: JOB start time has changed. exp/found foreign local
phase logid
partition, it discovered that the job start time had changed since the original request was issued.
The expected and found values are included in the message text.
flight.
System Action: The connection is closed and all pending requests are flushed without altering
IPN858I Socket request dropped: TIB has changed exp/found foreign local phase logid
partition, it discovered that the TIB address had changed since the original request was made.
Both the expected and found values are displayed (hexadecimal) in the message text.
flight.

13.87
IPN859I Socket request dropped: Control area modified. exp/found foreign local phase
logid
partition, it discovered that the data contained in the first 40 bytes of the descriptor block had
changed since the request was issued. In the message text both the expected and found values
are displayed.
This usually means that the requesting program has abandoned the I/O request or that a storage
overlay has occurred.
Administrator Action: Examine the issuing program for logic flaws. Programs that issue
TCP/IP requests MUST wait for all in-flight requests to be posted complete before the affected
storage is released or re-used.
IPN860I XMOVE failed: code foreign local phase logid
(Info) While TCP/IP was attempting to complete a socket request, it was unable to transfer
cross-partition data. In the message text, the hexadecimal return code from XMOVE is
displayed.
System Action: The socket request is abandoned without transferring data or posting the
application.
Operator Action: The requesting program or transaction may need to be canceled because it
may wait forever on an I/O request that will never complete.
IPN861D Storage Dump (id cnt) title
(Diagnose) This message precedes a short dump of storage for debugging purposes. In the
message, id is an internal identifier, cnt is the number of dumps that can still be produced before
they are suppressed, and title is a description of the storage to be dumped.
Operator Action: Generally, these dumps are produced as a result of an operator DIAGNOSE
command. DIAGNOSE OFF will prevent further dumps.
Administrator Action: Contact CSI Technical Support for help in interpreting the dump and
assistance in eliminating the condition that caused the dump.

13.88
IPN862D addr offset -storage- * ebcdic | ascii *
(Diagnose) One or more of these messages follow IPN861D. Each line displays up to 16 bytes
of storage. Included in the display is the virtual address, offset within the dumped area, up to
four dumped words of storage, the EBCDIC representation of the storage, and the ASCII
representation of the storage.
IPN863I POP3 server: text : ipaddr
(Response) This line displays the server’s domain name and, possibly, IP address. If the server
has never been used, the IP address will be “0.0.0.0”. If the server has been used, then it will be
set to the actual value.
IPN864I Socket request dropped: partid program (prog) abruptly terminated.
partition, it discovered that the program running in a specific partition was no longer there. The
partition and the name of the program are displayed in the message text.
This usually means that the requesting program has been cancelled while the socket request was
in-flight.
IPN865E Socket Block Damage. Dropping chain at aa
(Critical) An error has been detected in the Socket Block (SOBLOK) chain.
System Action: TCP/IP abandons whatever socket blocks remain on the queue and attempts to
continue operation. The address of the “bad” socket block is contained in the message.
Operator Action: Various applications may hang if they lose a socket block. You may need to
restart any hanging applications.
It is advisable to cycle the TCP/IP partition at the first convenient time.
IPN866E Message skeleton file phase failed to load.
(Critical) A CDLOAD has failed for the indicated message skeleton phase.
System Action: If the phase name is MSKELIP, then TCP/IP FOR VSE terminates with return
code 8. Otherwise, other messages will indicate the disposition of optional components.
Operator Action: Ensure that the indicated phase is in the TCP/IP FOR VSE search chain, and
restart the product.
Administrator Action: This may indicate that the TCP/IP FOR VSE distribution library has
been corrupted or that the product was not installed correctly.

13.89
IPN867I Ignorename: yes/no Max: nn Actual: nn
(Response) This message indicates value of the IGNORENAME= parameter.
IPN868I DIAGNOSE display on console is xxx
(Response) Issued in response to a SET DIAGNOSE=CONSOLE/NOCONSOLE command,

this message indicates whether messages produced in response to a DIAGNOSE command will
be shown on the console (enabled) or suppressed (disabled). In either case, the messages will be
written to SYSLST.
IPN869D XMOVE posted ecb:code foreign local phase logid
(Diagnose=SOCKET) TCP/IP has completed a socket request and posted the application’s
ECB. The address of the ECB is displayed.
System Action: The socket request is complete, and the application has been successfully
posted.
Operator Action: None.
IPN871E Version table could not be loaded
(Critical) TCP/IP FOR VSE was unable to load VERCHECK.PHASE. This phase contains
important information about phase versions and applied fixes.
System Action: Execution continues to the extent possible.
Administrator Action: Determine what happened to VERCHECK.PHASE. If necessary,

repeat the installation process.
IPN872I Xmit hesitation: time1, Idle timeout: time2 seconds
(Response) This message shows the transmission hesitation, in 300th-second units, and the idle
session timeout value. Hesitation is the time that the daemon will pause between each I/O to
ensure that the TCP/IP partition allows CPU cycles to pass to lower-priority partitions.
“Idle timeout” is the time that an idle daemon will wait before dropping the current user. If it is
non-zero, this timeout will be applied only when data is not being transferred and commands
are not being entered.

13.90
(Diagnose=SOCKET) This message is produced when DIAGNOSE SOCKET is in effect. It

produces messages related to the process of conveying information and completion status of
socket requests back to the original requestor.
Operator Action: This message can be eliminated by using the DIAGNOSE -SOCKET
command.
IPN874I Buffers: nn Buffer size: bb bytes
of FTPD buffers and the size of the buffers being used for this daemon.
Administrator Action: FTP transfer buffers are individually allocated by the FTP Daemons
when they are defined. You may adjust the number of buffers and the size of the buffers with
the DEFINE FTPD command.
IPN875I MTU: mtu RMSS: rmss Pulse: pulse sec status
(Response) Issued in response to a QUERY ROUTES command, this line shows the Maximum
Transmission Unit (MTU) size, the receive Maximum Segment Size (MSS), the pulse time, and
if in response to QUERY CONNECTS, the current pulsing status.
IPN876I SYN Retran: syn Data Retran: data Fixed: YES/NO
(Response) Issued in response to a QUERY ROUTES command, this line displays the
retransmission time (in milliseconds) for the initial SYN exchange. The data retransmission
time (in milliseconds) is also shown. If fixed = “NO”, then this is the starting point for
retransmission time calculations. If fixed = “YES”, then this is the value that is always used.
IPN877I Retran Min: min Max: max
(Response) Issued in response to a QUERY ROUTES command, this line indicates the
minimum and maximum values (in milliseconds) that can be used for calculating
retransmission time on this route.
IPN878I task prog start Di: cnt Du: time Ex: time SZ: cnt
(Info) This message is issued at the conclusion each pseudo task and summarizes the resources
consumed. It is produced only if RECORD ON is in effect.
Each record begins with the Task ID, the program name associated with the task, and the task’s
start time. “Di:” provides a count of the number of times the task was dispatched, “Du:” shows
the duration of the task (hh:mm:ss.mmm), “Ex:” is the amount of time that the task was in a
dispatched state, and “SZ:” is the number of times that the task was dispatched in Key 0 or
Supervisor State.

13.91
IPN879I Router: aaaa
(Info) This value indicates the router mode for an OSA/X adapter. Three possible values may
be displayed. “None” (default) indicates that the OSA/X will only accept traffic for its specific
IP address. “Primary” indicates that the OSA/X will accept traffic for any IP address and pass it
to the stack. “Secondary” indicates that this is a backup for another primary adapter. It will
function as “none” unless and until the primary fails. This link will then become “primary”.
For more information, see the IBM documentation for your OSA/X adapter.
IPN880I Root: aaaa
(Response) The FTP root directory for the user. This is defined by the DEFINE USER
command that created the user ID entry in the preceding IPN475I message. If ROOT was not
specified, this line is omitted from the display.
IPN881I xxx FTP Daemons defined, yyy FTP sessions active.
(Info) This message shows the total number of FTP daemons defined and the number of
sessions that are currently active.
System Action: Processing continues normally.
Operator Action: This message is informational only; no action is needed.
IPN882I Retry Delay: time Retries count
(Response) Issued in response to a QUERY ROUTES command, this line indicates the time (in
milliseconds) that will elapse between each retransmission on this route. Each transmission
failure will continue to be retried at this interval until count attempts have been made or an
acknowledgement is received.
IPN883I Valid for: processes
(Response) This line indicates all processes for which this user ID can be used.
IPN884I RWin: size
(Response) Issued in response to a QUERY ROUTES command, this line indicates the
maximum window size that will be presented to the foreign host.

13.92
IPN885I CPU ID: cpu (csi)
(Response) Issued in response to a QUERY PRODKEYS,ALL command, this message

displays the CPU ID information being used to validate the product keys.
The first value displayed is the CPU ID as reported by the hardware. The value in parentheses is
the adjusted CPU ID used to validate license information.
Administrator Action: This information will be useful to CSI Technical Support in the event
you are having difficulties with product key validation.
IPN886I product (vendor) expires on date
(Response) Issued in response to a QUERY PRODKEYS command, this message displays

current authorization for various products and features.
The format of this message will vary, and the text will be self-explanatory. The vendor field
(always in parentheses) shows who issued the product key, either “IBM” or “CSI”.
IPN887D Route ID node being used for ip
(Diagnose=ROUTING) This message indicates the route that will be used for the shown IP
address. The value for node corresponds to the ID= value specified with the DEFINE ROUTE
command that defined the route.
Operator Action: To eliminate this message, issue the DIAGNOSE -ROUTING command.
Administrator Action: This message is useful in determining the validity of your routing
table. To determine which route to use, TCP/IP scans the table in the same order as it is
displayed by the “QUERY ROUTES” command, and each valid route entry is examined.
(A valid route is one associated with an active link.)
The first match will determine the route EXCEPT for two cases:
• If ip is null (0.0.0.0), then the match will be with the first occurrence of a valid route with a null
IP address.
• Routes with null IP addresses are not examined until all other valid routes have been considered.
One additional special case is recognized: If the ip value is null (0.0.0.0) and no valid route
(specific or generic) is available, then the first physical entry in the route table will be used,
without regard to its association with an active link.
IPN888I flag value...
(Response) Produced as part of a connection display, this line shows the current values for the
named flag fields. This line may appear multiple times, depending on the number of flags.
This line is produced only for non-generic displays, or when EXTENDED=YES has been
specified.

13.93
IPN889I Size: bytes MTU: datagram Free: count/total Hits: count Misses: count
(Response) This message is issued in response to a QUERY IBBLOK command. It summarizes

how the datagram transport buffers are being used.
The buffers (IBBLOKs) are allocated only in discrete, 128-byte increments. For example, if
you have 500 bytes of data with a 40-byte header, then 540 is rounded up to the next 128-byte
value, or 640 bytes. Buffers up to 8K bytes long are retained in an IBBLOK pool for reuse. The
stack always tries to reuse more buffers than it allocates.
Same-sized buffers are tracked and displayed as a group. The “Size” field in the message
indicates the IBBLOK size to which the following information applies.
“MTU” indicates the maximum size datagram that will fit in the buffer. Essentially, this is the
data size plus 40 bytes for the headers.
“Free” is the count of currently free IBBLOKs out of the total retained for this IBBLOK size.
“Hits” and “Misses” refer to the number of times a free slot for an IBBLOK was available and
the number of times a GETVIS was required because a free slot was not available. The
IBBLOK pool index is 2K bytes long and consists of 512 fullword pointers. The IBBLOK
holding areas (slots) are allocated in increments of 128 bytes, up to a maximum of 8K. As
IBBLOKs are requested, available slots that match the needed size are searched for. Where
there is a match, the slot is marked as used. This is called a hit. If no matching slots are
available, storage is allocated. This is called a miss.
Two types of IBBLOKs are always temporary and counted as a miss: 24-bit IBBLOKs, which
are allocated when there is a lack of 31-bit storage, and IBBLOKs larger than 8K. These larger
IBBLOKs are always allocated and then released from memory after use.
IPN891D text
(Diagnose=DTLOAD) This message is issued in response to a DIAGNOSE DTLOAD

command. The displayed text contains information of use to CSI Technical Support in tracking
problems related to phase loading and unloading.
Operator Action: This message can be eliminated from SYSLST by using the
DIAGNOSE -DTLOAD command.
(Diagnose=ROUTING) This message is produced when DIAGNOSE ROUTING is in effect

and can be useful in troubleshooting problems in routing datagrams to the correct targets.
Operator Action: This message may be eliminated by using the DIAGNOSE -ROUTING
command.

13.94
IPN893I Freeing owned SOBLOK. Proto: prot Req: request
(Important) Although the socket is being passed back to the requestor, it is still flagged as
“owned” by a connection manager. This indicates a logic error.
System Action: The ownership flag is reset and processing continues.
Administrator Action: Capture SYSLST, and report this to CSI Technical Support.
IPN894I SOSBNEXT not clear. Proto: prot Req: request
(Important) Although the socket is being passed back to the requestor, it is still chained to other
socket blocks. This indicates a logic error.
System Action: The chaining field is cleared, and processing continues.
IPN895I SOCCBLOK not clear. Proto: prot Req: request
(Important) Although the socket is being passed back to the requestor, it is retains a pointer to
the CCBLOK that processed it. This indicates a logic error.
System Action: The pointer is cleared, and processing continues.
IPN896I Counts - Current: num Peak: num Failed: num
(Response) Issued in response to a QUERY IBBLOKS commands, this message shows the total
IBBLOKs currently allocated as well as the peak number ever allocated. The failed count
shows the total times that an IBBLOK was needed and could not be allocated.
IPN897I Space - Current: numk Peak: numk Max: numk (num%)
(Response) Issued in response to a QUERY IBBLOKS commands, this message displays the
total amount of storage tied up in IBBLOK allocations.
The current value is shown, followed by the maximum space ever allocated. The maximum
value shows the total storage that is permitted to be allocated as IBBLOKs. The value in
parentheses is the maximum as a percent of the partition’s 31-bit area and may exceed 100
percent because 24-bit may also be allocated. Note that if the partition has no 31-bit storage,
then the percentage will be relative to the 24-bit area.

13.95
IPN898I Internal SOECB content error. Called from offset in phase
(Important) When attempting to post socket completion to a requester internal to the stack, it
was discovered that certain eyecatchers had been changed in a manner that indicates that the
original requestor is no longer executing.
System Action: The socket is discarded and the specified ECB is not posted.
Administrator Action: If this is an isolated incident, especially if it occurs in close proximity

to operator action or other error indicators, it can be safely ignored. However, if this message
occurs frequently, or always involved the same phase or offset, contact CSI Technical Support.
IPN900D IPSTORX entry point: xxx
(Diagnose) This message is produced only when STORMON has been coded in the EXEC card
PARM field. It provides the memory location of the storage manager phase.
System Action: The storage monitor function will aggressively monitor storage for overlays.
This will increase the aggregate storage used and will also increase the CPU consumed. All
storage will be validity-checked after each dispatch. This check can be disabled with the
MEMORY_VERIFY OFF command.
IPN901D IPSTORX TIBPTR addr: xxx name
(Diagnose) This message is produced only when STORMON has been coded in the EXEC card
PARM field. It provides the unique TIB address as well as the name of each VSE subtask being
monitored for storage use.
IPN902E STORMAP could not be located
(Vital) A storage release request has been made, but the address passed does not point to the
start of an area previously obtained from the storage manager. Additional messages will
indicate the component making the request. If the storage is contained within an allocated area,
a map of the element will follow.
System Action: The storage is not freed, and execution continues.
Administrator Action: Forward a copy of SYSLST to CSI Technical Support.
IPN903E Free length (xxxxxx) is wrong
(Vital) A storage release request has been made, but the length to be freed does not match the
length originally obtained. Additional messages will indicate the component making the request
and provide a map of the element.

13.96
IPN904E Guard bytes destroyed
(Vital) When running in monitoring mode, the storage manager places random “guard bytes” in
the area immediately adjacent to each storage element. These bytes are tested when the storage
is to be freed and, depending on optional setting, after each dispatch. This message is produced
when the guard byte area is overlaid. Additional messages will follow.
Administrator Action: VERIFY_MEMORY can be used to regulate testing frequency.
IPN905E FREEVIS failed: code
(Vital) A storage release request has been made, but the VSE FREEVIS failed. The return code,
shown in decimal in the following table, indicates the problem.
Code Meaning
4 The size of the (real) partition GETVIS area is 0K
8 The specified length is negative
12 The specified address is not within the GETVIS area, or the address is not a multiple of
• 128 bytes if the GETVIS area is part of a partition
• 16 bytes if the GETVIS area is part of the SVA or the dynamic space GETVIS area
16 The specified storage block to be released (ADDRESS + LENGTH) exceeds the
GETVIS area or is not within a subpool
20 Invalid FREEVIS option
24 An invalid subpool ID was passed
28 The specified subpool does not exist
36 An invalid subpool index was specified in the SPID operand. The subpool was created
with the GETVIS operand SPCNTRL=YES (compare the GETVIS macro).
40 FREEVIS for an area or subpool for which a PFIX request is pending is not allowed
44 Address was not returned by GETVIS
48 Length does not match the GETVIS request
52 Storage overlay. Guard bytes have been destroyed
64 This task has no work area

IPN906E MACID SPID USAGE ID
(Vital) A label line. This will be followed by IPN907E.

13.97
IPN907E macid spid usage id
(Vital) This message displays information pertaining to a storage element. macid is an arbitrary
string used to determine where the allocation occurred. spid is the name of the VSE subpool
where the storage resides. If present, usage will describe what the storage is being used for. If
the storage is associated with a daemon, id may allow association.
IPN908E ADDRESS Length TKBLOK R14 Pt
(Vital) A label line. This message will be followed by IPN909E.
IPN909E addr leng tkblok r14 pt
(Vital) This message displays information pertaining to a storage element. addr is the address
of the storage and leng is the length of the allocation. tkblok is the address of the task block in
control at the time of allocation. r14 is the memory address of the point where allocation was
requested. pt is the value used for the guard bytes, if in effect.
IPN910E ADDRESS Length TKBLOK TIBPTR
(Vital) A label line.
IPN911E addr leng tkblok tibptr
(Vital) This message provides information on a storage request. addr is the address of the
storage (free request). leng is the length of storage requested or being freed. tkblok is the
address of the task control block making the request. tibptr is the TIB address of the VSE task
making the request.
IPN912E = Storage Element Information For xxxxxxxx =
(Vital) The next several messages will display values associated with a single storage element.
In the message, xxx is the address of the storage map (not the storage block).
IPN913E ======= xx Request Information Follows =======
(Vital) This message indicates the start of displayed information describing a storage request.
xx will be either “GET” or “FREE” depending on the type of request.

13.98
IPN914E Storage corruption Detected
(Vital) When the storage monitor was active, it detected that the guard bytes that follow each
storage element had been overwritten. Additional messages will provide more information on
this event.
System Action: Execution continues.
IPN915E GETVIS FAILED: code
(Vital) This message is produced when a storage request has failed. The decimal return code
from the GETVIS macro is shown in the message.
Depending on the value of code, you may be able to correct the problem, or you may need to
contact CSI Technical Support. The possible codes and their meanings are as follows:
Code Meaning
4 The size of the (real) partition GETVIS area is 0K
8 The specified length is negative or exceeds the GETVIS area
12 No more virtual storage is available in the GETVIS area, or a GETVIS request with
length zero has been specified for a non-existing subpool or a subpool that has no free
space
16 The maximum number of subpools is exhausted
20 Invalid GETVIS option
24 Invalid subpool ID
32 PFIX for an SVA subpool request failed
36 An invalid subpool index was specified and (a) the request was done with
SPCNTRL=YES and/or (b) the specified subpool name denotes an existing subpool
that was created with SPCNTRL=YES. (A subpool index is invalid if it points to a
subpool other than the supplied one. This includes a subpool index of zero for an
already-existing subpool.)
40 No access to the specified subpool is allowed as long as a PFIX request is pending
44 Program in AMODE 24 requested RMODE 31 storage
64 This task has no work area
Operator Action: If operational problems arise, it may be necessary to take corrective action.
If a lack of storage is indicated, if may be necessary to enlarge the partition.
Administrator Action: This message will be accompanied by other messages with additional
diagnostic information. Please save all such messages for CSI Technical Support.

13.99
IPN921I Map Pages: amount Subpools amount
(Response) As part of a QUERY STORAGE request, the number of map pages and pools in use
by TCP/IP is being displayed.
IPN922I spid elem stor act
(Info) This message details storage activity by subpool ID. spid is the subpool being listed. elem
is the number of storage elements currently allocated in the subpool. storage is the number of
bytes allocated in the subpool. act is the cumulative number of GETVIS requests issued to the
subpool since program startup.
Items displayed as absolute numbers indicate current values. If +/- is shown, the values
represent trends: the relative change in the value since the last “Q STOR ... SAVE” was issued.
IPN923E Specified address is unknown to TCP/IP
(Response) Issued in response to a Query Storage command, this message indicates that TCP/IP
has no record of the storage address specified.
Note that the Query Storage command can display information only about storage directly
allocated by TCP/IP. Storage allocated by the operating system or other programs by GETVIS
is not tracked. To display information about such storage, use VSE-provided commands, such
as SHOW.
Operator Action: Make sure that the address is specified correctly.
IPN924I Regs: values
(Vital) This message provides the register values of the requestor at the time of the request.
They are listed from 0 through 15.
IPN925I ------24 bit---- ------31 bit----
(Response) This message is issued in response to a QUERY STORAGE command. It provides

column headers for the data lines to follow.
IPN926I Address: addr Length: len
(Info) This message begins the detail listing of a single storage element. Additional information
will follow. The values for addr and len are in hexadecimal.

13.100
IPN927I Macid: text Locate: addr
(Info) text in the internal ID assigned to the storage request that obtained the storage element.
addr is the memory location that made the storage request.
IPN928I Usage: text ID: text2
(Info) text in the internal usage assigned to the storage request and text2 is the daemon ID
associated with the storage, if any.
IPN929I Allocated at: time
(Info) time is the date and time of day that the storage element was allocated.
IPN930I SPID Elem Storage Elem Storage Requests
(Response) This message is issued in response to a QUERY STORAGE command. It provides

column headers for the data lines to follow.
IPN931E STORAGE MANAGER SETUP FAILURE
(Info) The storage manager failed to initialize.
System Action: The job terminates.
Operator Action: Try running the affected job in a larger partition.
IPN932I Storage located at offset hex in phase name
(Response) Issued in response to a QUERY STORAGE command, this optional message is

displayed when the memory address in question is located within a phase. The message shows
both the name of the phase and the offset within the phase (in hexadecimal).
IPN936I Lock: xxx Requests: xxx Conflicts: xxx
(Info) This message is issued in response to a QUERY LOCK command.
IPN937I Held by: xxx
IPN938I Waiting: xxx

13.101
IPN939E Socket Overrun. Addr: addr Len: len Block ID: ident Source: reg14
(Vital) During an internal socket operation, it was determined the address and length of the
specified data area extended beyond the boundaries of the allocated storage. The “Block ID”
refers to an identifier belonging to the routine that allocated the storage block in question. reg14
is the address to which the socket call will return.
System Action: The socket operation is suppressed with return code 101.
Administrator Action: This indicates a probable internal logic error. Capture the logged data,
and contact CSI Technical Support.
IPN940E Socket Storage Error. Addr: addr Len: len Source: reg14
(Vital) During an internal socket operation, it was determined the address of the data area is not
within allocated storage. reg14 is the address to which the socket call will return.
System Action: The socket operation is suppressed with return code 102.
IPN941E FILE I/O Overrun. Addr: addr Len: len Block ID: ident FRBLOK: addr
(Vital) While processing a file I/O request, it was determined the address and length of the
specified data area extended beyond the boundaries of the allocated storage. The “Block ID”
refers to an identifier belonging to the routine that allocated the storage block in question. reg14
is the address to which the file I/O request will return.
System Action: The file I/O request is suppressed with return code 64.
IPN942E FILE I/O Error. Addr: addr Len: len FRBLOK: addr prog offset
(Vital) While processing a file I/O request, it was determined the address of the specified data
area is not known to the TCP/IP storage manager. prog is the calling phase and offset is the
offset within the phase from which the file I/O request was made.
System Action: The file I/O request is suppressed with return code 64.

13.102
IPN943E XLATE Overrun. Addr: addr Len: len Block ID: ident Source: reg14
(Vital) During an internal translation, it was determined the address and length of the specified
data area extended beyond the boundaries of the allocated storage. The “Block ID” refers to an
identifier belonging to the routine that allocated the storage block in question. reg14 is the
address to which the translate call will return.
System Action: The translation is suppressed.
IPN944E XLATE Storage Error. Addr: addr Len: len Caller: reg14
(Vital) During a data translation request it was determined the address of the data area is not
within allocated storage. reg14 is the address to which the translation call will return.
System Action: The translation is suppressed and the calling routine is notified.
Administrator Action: This indicates a probable internal logic error. Capture the logged data
IPN950I Socket scheduling codes
(Info) This message is a placeholder to allow documentation of the return and reason codes
produced by the socket API. This includes the SOCKET macro and code produced by the pre-
processor.
Note: The following codes are produced only when a socket request is NOT scheduled. They
should not be confused with SRCODES or those values returned as the result of processing a
socket request.
In the following table, two decimal values are shown. The first is the decimal value returned in
register 15 as the return code. The second decimal value shown is returned in register 0 as the
reason code. A reason code of “x” indicates that the value returned is meaningful but variable.
Codes Meaning
4,x Insufficient storage to schedule request. Register 0 will contain the return code
from GETVIS.
5,1 A RECEIVE (non-null) specified an address of zero for the buffer.
8,1 The SCBLOK could not be found. This means that either the stack is not running or
the stack’s software version is far back-leveled.
8,2 The stack is initializing or shutting down.
8,3 The SQBLOK is corrupt. This indicates that the stack’s queue block is defective. It
may be necessary to cycle TCP/IP to correct this.
9,2 The SCBLOK is corrupt. This indicates that the stack’s System Control Block has
been compromised. It may be necessary to cycle the stack or IPL to correct this.

13.103
Codes Meaning
10,3 Null SQBLOK pointer. Although this may indicate SCBLOK corruption, it
generally means that the target stack is not initialized.
11,4 Stack is in the process of shutting down.
12 The “descriptor” field is null. Except for OPEN calls, the contents of the descriptor
contain the connection’s unique identifier.
14,6 SOQUEUE field in SOWORK is null. This indicates that either macro calls are
being issued in an incorrect sequence, or the SOWORK area has been overwritten.
It may also indicate improper switching between AMODEs.
15,1 SQSOCKET pointer is null. This indicates corruption of the SQBLOK and may
require cycling of the TCP/IP partition.
16,x Can’t obtain SVA storage. Register 0 contains the return code set by GETVIS.
17,x Can’t free storage. Register 0 contains the return code set by FREEVIS.
18,1 During CLOSE processing, the SOWORK area is not being freed, but it was
dynamically obtained by OPEN.
18,2 During CLOSE processing, the SOWORK area is being freed, but it resides in
static storage.
18,3 SOWORK was obtained by a storage manager call, but SOCKET is attempting to
release using FREEVIS.
18,4 SOWORK was obtained by a storage manager call, but the storage manager is not
available to release it.
24,x VSE SUBSID macro failed. Register 0 contains the return code set by SUBSID.
28,1 SOPARM format invalid. Eyecatcher.
28,2 SOPARM format invalid. Version number.
28,3 SOPARM format invalid. Release number.
28,4 SOPARM format invalid. Descriptor field is zero.
36 The ECB value is currently assigned to another socket call.
40 The Connection Control block (CCBLOK) cannot be located.

13.104
IPN951I Socket return codes (SRCODE)
(Info) This message is a placeholder to allow documentation of the codes returned following
completion of a socket request.
In each case, the value shown is decimal (with the hexadecimal equivalent in parentheses). The
value is contained in the SRCODE field of the SRBLOK.
Code Meaning
0 (0) The socket request completed normally
4 (4) Connection not found (not applicable for OPEN). This indicates that the connection
has been terminated and the related control blocks are gone.
8 (8) Connection was reset by the foreign host
12 (0C) A timed OPEN or RECEIVE has reached the specified timeout value without
completing
16 (10) The descriptor field contains nulls. This request should have failed to schedule and
may indicate an incorrect use of the SOCKET macro or other API
20 (14) Duplicate ECB. This request shares an ECB and SRBLOK with another running
socket request
28 (1C) The TCP/IP stack is shutting down.
32 (20) For a STATUS call, the return area is too short to return the STATBLK
36 (24) This SEND was issued after a CLOSE request
40 (28) A SEND or RECEIVE was issued on a connection that is not established
44 (2C) Set on a CLOSE request that is issued while data that is already received and
acknowledged remains queued
48 (30) A STATUS call could not complete due to a storage shortage in the TCP/IP partition
IPN952I BSD Socket return codes
(Info) This message is a placeholder to allow documentation of the codes returned following
completion of a socket request.
Although the BSD programming interface provides return codes whose values are understood
by convention, there is no standard. To reduce confusion, we have adopted the values and
reasons assigned by IBM for their z/OS and z/VM implementations.
The code values shown are in decimal. When applicable, the corresponding SRCODE (in
decimal) is shown in parentheses.
Code Reason
100 Internal error (EINTERNAL)
113 Not valid socket (EBADF)
118 Application error (EFAULT)
121 Invalid parameter (EINVAL)

13.105
Code Reason
122 (32) Closed
127 No system space in table (ENFILE)
132 Request for storage failed (ENOMEM)
183 Unable to initialize (EVSE)
1103 Request in progress (EINPROGRESS)
1104 Already closed (EALREADY)
1112 Socket not supported (EOPNOTSUPP)
1114 Request not supported (EAFNOSUPPORT)
1117 (16, 29) TCP/IP is not up (ENETDOWN)
1121 (8) Connection reset by peer (ECONNRESET)
1122 No buffer space (ENOBUFS)
1124 (4) Connection not found (ENOTCONN)
1127 (12) Request timed out (ETIMEDOUT)
1128 Connection refused (ECONNREFUSED)
1152 (36) Request canceled

13.106
14
IPT Series Messages
IPT100I protocol Processor type starting
(Info) TCP/IP processing is defined as a series of layers. The Protocol layer handles the many
different protocols transmitted over IP. Examples would include TCP and UDP.
handling the data at this level of the stack.
This message indicates a particular processor is starting to execute.
IPT101I protocol Processor type stopping
(Info) TCP/IP processing is defined as a series of layers. The Protocol layer handles the many
different protocols transmitted over IP. Examples include TCP and UDP.
handling the data at this level of the stack.
This message indicates a particular processor is terminating its processing.
Operator Action: This message should only occur during shutdown of the TCP/IP partition. If
it is seen at any other time, it will probably be necessary to stop and restart TCP/IP.
IPT106D TCP has rejected/ignored a connection for lport from ip,port
(Diagnose=CONREJECT) A request for connection has been received from the indicated
foreign IP and port, but no listen connection exists on the local port (lport) to satisfy the
request.
System Action: No connection is opened. If STEALTH is set to ON, the request is quietly
discarded and the message will show “discarded”. If STEALTH is OFF, a RESET is sent to the
requestor and the message will show “discarded”.

14.1
TCP-IP FOR VSE 1.5F Messages IPT Series Messages
IPT107I TCP Check Sum Failed from source ip
(Info) A TCP datagram has arrived, but it could not be processed because the checksum did not
match.
Operator Action: This message and dump is in response to DIAGNOSE CHECKSUM. Only
10 messages and dumps will be produced for each specification of DIAGNOSE CHECKSUM.
IPT109W TCP Check Sum Failed, Failure Ignored
(Warning) The checksum of an incoming TCP packet is incorrect. However, current parameter
settings instruct TCP/IP FOR VSE to ignore the error. The corrupted packet is processed.
Administrator Action: Check for faulty communications paths, and consider re-enabling
checksum processing.
IPT110I Datagram length error from source ip. Discarded.
(Info) A TCP datagram has arrived, but its indicated length exceeded its physical length.
Operator Action: This message and dump is in response to DIAGNOSE REJLEN. Only 10
messages and dumps will be produced for each specification of DIAGNOSE REJLEN.
IPT112I header values
(Info) Displays the non-TCP values used in checksum verification.
IPT203W Closing connection with IP: ipaddress due to excessive traffic
(Warning) TCP/IP has closed its received window. However, the remote host has ignored the
closed status and continues to transmit.
“Closing the window” is the method specified in the TCP protocol to prevent the receiving side
of a connection from being swamped with data. All TCP/IP stacks recognize this capability. A
host’s failure to honor a closed window will eventually exhaust all storage on the receiving end
of the connection.
System Action: TCP/IP closes the connection and flushes the data buffers.
Administrator Action: Determine why the indicated host is ignoring the closed window
indicator, and correct it. Note that even with the window closed, a host is always required to
accept a single data byte. This is intended for transmitting “keep alive” packets. However, some
implementations misinterpret this requirement to mean that when the window is closed, send
the data as fast as you can, one byte at a time. This is both extremely inefficient and dangerous
to the VSE stack.

14.2
IPT240I logname on device
(Response) Issued in response to a QUERY LOGS command, this message identifies a

particular logging class and indicates where the information will be recorded. Additional lines
will provide more information pertaining to this logging class.
IPT241I Line Length: dec Lines per page: dec Timestamp: Left/Right/None
(Response) Issued in response to a QUERY LOGS command, this message provides additional
information about the logging class currently displayed.
This line indicates the maximum line length. (Overflow will cause the line to be broken at a
blank and a continuation character [>] to be appended.) The number of lines per page is also
shown.
The timestamp value indicates if and where each line will be timestamped.
IPT242I Total lines: dec Total pages: dec
information about the logging class currently displayed.
This line displays the total lines and pages written to this logging class since the stack was
initialized.
IPT243I Logging: route codes
information about the logging class currently be displayed.
This line displays the message types that will be written to the logging class being displayed.
The values shown will be a combination of “Critical,” “Vital,” “Warning,” “Important,” “Info,”
“Response,” “Security,” “Dig,” “All,” or “None”.
(Response) Issued in response to a DEFINE LOG command, this message indicates that there is
insufficient storage available to perform the task.
System Action: The log is not defined.
Operator Action: Retry the command. Because defining a log takes very little storage, this
message will almost certainly be accompanied by a number of more serious storage shortage
messages.

14.3
IPT245E Log already defined
(Response) Issued in response to a DEFINE LOG command, this message indicates that the log
is already defined.
System Action: The log is not defined.
Operator Action: Either specify a different name, or use the MODIFY LOG command to
change the characteristics of the existing log.
IPT246E Log not found
(Response) Issued in response to a MODIFY LOG command, this message indicates that the
specified log has not been defined.
System Action: The log is not modified.
Operator Action: Either correct the name specification, or use the DEFINE LOG command to
create a new log.
IPT247E Invalid log type
(Response) Issued in response to a DEFINE or MODIFY LOG command, this message

indicates an error in the “type” specification.
System Action: The log is not defined or modified.
Operator Action: Correct the type specification and reissue the command.
IPT248E Invalid logical unit
(Response) Issued in response to a DEFINE or MODIFY LOG command, this message

indicates an error in the “logical unit” specification.
System Action: The log is not defined or modified.
Operator Action: Correct the specification and reissue the command.

14.4
IPT301D diagnostic text
(Diagnose=TCP) This message is issued because DIAGNOSE TCP is in effect. The message
text is self-explanatory and of interest to CSI Technical Support. Some of the possible
diagnostic messages follow.
Message Meaning
Connect State set to Close wait The TCP connection driver has set the connection
state to CLOSED and is waiting for the next
command.
TCP request has been received The TCP connection driver has received a request
for processing.
Connect State set to Listen The TCP connection driver has set the connection
state to LISTEN.
Connect State set to Established The TCP connection driver has established a
connection with the remote end.
Application (TCP) Shutdown The TCP connection driver is shutting down its
Connection TCP connection.
Connect State set to Fin-Wait 1 The TCP connection driver has issued a FIN
command to the remote end and is waiting for a
response.
Connect State set to Closed The TCP connection driver has successfully closed
its connection.
Connect State set to Last-Ack The TCP connection driver has sent the final
acknowledgment (for FIN) to the remote end.
TCP Output request being The TCP connection driver is constructing an
generated at: aaa for: bbb outgoing datagram.
Analyze Inbound TCP against The TCP connection driver is scanning the
retrans queue retransmit queue for data blocks to discard, based on
the contents of an inbound packet.
Connect State set to Syn-Sent The TCP connection driver has sent a SYN response
to the remote end due to the previous receipt of a
SYN request.
Connect State set to Syn-Received The TCP connection driver has received a response
to a SYN request.
TCP Output request being The TCP processor is about to prepare an ACK or
generated RST response to an incoming TCP packet.
Operator Action: If these diagnostic messages are not required, they may be eliminated with
the DIAGNOSE -TCP command.

14.5
IPT302I Connection reset by foreign host ip,port local Ident: id
(Important) The TCP connection driver has received a RESET request from the remote host.
The foreign IP address and port sending the reset is shown, as well as the local port receiving
the RESET.
The “Ident” field can be used to link this message with a specific connection.
System Action: The VSE-based application is notified that the connection has been lost, and
any remaining queued data is discarded. Processing for other connections, for the same or other
remote hosts, continues.
IPT303D RTBLOK values set for ip,fport/rport (state) from rtid Ident: id
(Diagnose=(ROUTING,TCP)) In response to a DIAGNOSE ROUTING command, this

message is issued when the route table is examined for transmission values. In the message text,
the connection’s foreign IP address is listed along with the foreign and local ports. The state
value indicate the connection’s current status.
rtid is the ID= value from the DEFINE ROUTE command that established the RTBLOK being
used.
Operator Action: This message can be eliminated by issuing the DIAGNOSE -ROUTING
command.
IPT304I RTBLOK values NOT set for ip,fport/rport (state) Ident: id
(Important) The IP address shown in this message could not be associated with a routing block
(RTBLOK). In addition to the IP address, both the foreign and local ports for this connection
are shown. state is the connection’s status at the time of the message.
System Action: TCP/IP continues, using default values for this connection. This connection’s
performance may be less than optimal, and the connection may fail.
Operator Action: The QUERY CONNECTS command can be used to determine the
transmission values being used for this connection.
A DEFINE ROUTE command can be used to provide an appropriate route block and eliminate
the display of this message.
Administrator Action: Ensure that all possible IP addresses have either explicit or generic
matches in the Route Table, with appropriate connection values.

14.6
IPT317I No response from ip,port (lport). State: state [(Pulse)], Ident: id
(Important) During the course of a connection, the remote host failed to respond to a data
transmission (ACK). TCP/IP made numerous attempts at retransmission over a reasonable
period of time. The foreign IP address and port, along with the local port, uniquely identify the
failed connection.
The connection state at the time of failure is also shown.
If the timeout occurred during a “Pulse” operation, the message will indicate that. The “Ident”
field can be used to link this message with a specific connection.
System Action: TCP/IP FOR VSE transmits a RESET (which does not require
acknowledgement), internally closes the connection, and notifies the VSE-based application of
the failure.
Operator Action: Note any messages issued from other jobs or applications regarding the
failed connection, and take appropriate action.
Administrator Action: Excessive or sustained problems may indicated network problems or

routing issues.
IPT326D Pulse generated for IP: addr Port: port Local Port: port Ident: id
(Diagnose=(PULSE,TCP)) TCP/IP is transmitting a “pulse” over the active connection

specified by the displayed IP address and ports. The pulse was triggered because no traffic has
been detected during a predetermined threshold value.
The pulse consists of re-transmitting the last byte already acknowledged by the remote host.
The TCP protocol requires the remote host to re-acknowledge the transmission and discard the
duplicate byte.
If no acknowledgement is forthcoming, TCP/IP FOR VSE’s retransmission logic will kick-in

and, if unsuccessful, the connection will terminate.
System Action: If the pulse packet is acknowledged, nothing will happen. If it is not
acknowledged, the connection will be reset.
Operator Action: This message can be eliminated by issuing the DIAGNOSE -PULSE
command.
Administrator Action: Pulse is required to detect connections where the remote host has
“gone away” and no data is scheduled to be transmitted. An example would be idle Telnet
sessions, where the user may be away from the terminal temporarily or may have turned off
their PC.
The pulse interval may be adjusted down to the individual IP address using the DEFINE and
MODIFY ROUTE commands.

14.7
IPT328D Invalid RST from ip,port on port. Seq: seq Valid: seq - seq Ident: id
(Diagnose=(RESET,TCP)) This message indicates that a RESET request has been received but
is rejected as invalid.
The message indicates the foreign IP and port number along with the local port. The sequence
number appearing in the Reset packet is also shown, followed by the acceptable range for this
connection.
System Action: The RESET request is ignored, and the connection continues.
Administrator Action: An occasional appearance of this message is meaningless. However, if

it is frequently issued, it may indicate a malicious attempt to interfere with connections or
multiple devices with the same IP (or MAC) address.
IPT330I diagnostic text
(Diagnose=RESET) This message is issued while DIAGNOSE RESET is in effect. The

message text will be self-explanatory and of interest to CSI Technical Support. Some possible
messages follow:
Message Meaning
Reset against a pulse event F: ip,port L: port The indicated connection appeared to be
inactive. TCP/IP issued a “pulse” to
determine the remote host’s status. No
response was received during the normal
retransmission sequence, and the connection
has been reset.
Reset packet received from ip port for port
Operator Action: If this message is not required, it may be eliminated by issuing the
DIAGNOSE -RESET command.
IPT334D Socket request dropped F: ip,port L: port Ident: id
(Diagnose=SOCKET) TCP/IP has found it necessary to refuse a socket request from an

application. The connection is identified by the IP address and port numbers in the message.
System Action: Additional diagnostics and dumps will accompany this message.
Operator Action: This message can be eliminated by issuing the DIAGNOSE -SOCKET
command.

14.8
IPT337D Retransmit shutdown L:port F:IP,port Count:nn Time:xxms Ident: id
(Diagnose=(RETRANS,TCP)) The connection identified by the IP address and ports shown is

being closed while it is in retransmit mode. The final datagram was not acknowledged. In the
message text, the number of retransmissions (for the datagram) and the duration of the time
allowed between retransmission attempts are displayed.
Operator Action: This message can be eliminated by issuing the DIAGNOSE -RETRANS
command.
IPT338D Reset issued. F: address L: address Seq: hex (Send: hex, Recv: hex) Ident: id
(Diagnose=(RESET,TCP)) A reset has been transmitted over the connection identified by the
local and foreign IP addresses and ports. The sequence number sent with the reset is also
shown. The values in parentheses display the current sequence numbers of the SEND and
RECV streams.
A reset is issued when a datagram is received that is inappropriate for a connection. For
example, a datagram containing both a SYN and FIN is invalid and cannot be processed. In
such a case, the reset (RST) informs the sender of the rejection.
A reset is also used to abruptly terminate a connection and is used to signal an abnormal ending.
To be used in this manner, the sequence number is set to the value that would normally
accompany the next datagram.
System Action: The connection may continue or terminate.
IPT339D Reset reason: text Ident: id
(Diagnose=(RESET,TCP)) This message follows IPT338D. The text will indicate the reason
for issuing a RST to the remote host on the connection identified by “Ident.”
IPT340D Connection Summary: F: ip/port L: ip/port State: state BSD: num t<
Diag=Perform
(Info) This message and the messages that follow summarize the activity on a single, completed
connection.
The connection is identified by the foreign IP and port numbers (F:) and the local IP and port
number (L:). The connection’s duration is expressed in hours, minutes, seconds, and
milliseconds (hh:mm:ss.ttt).
If this is a BSD socket, the BSD socket number is displayed. This can be used to associate a
connection with a particular BSD socket.

14.9
This diagnostic summary display is produced only after a connection is closed and does not
indicate either success or failure.
Operator Action: If this message is not desired, it may be eliminated using the DIAGNOSE -
PERFORM command.
IPT341I Start: hh:mm:ss [End: hh:mm:ss] [Waiting: hh:mm:ss] Duration: time
(Response,Diagnose=PERFORM) This message contains information on a connection’s start

time, end time (if complete), the wait time since a datagram was last received, and the
connection’s duration.
The start and end times are shown as hours, minutes, and seconds (hh:mm:ss). These values are
displayed in local time. The duration and idle times are expressed in hours, minutes, seconds,
and milliseconds (hh:mm:ss.ttt).
Operator Action: If it was not produced by a QUERY CONNECTIONS command, this

message can be eliminated using the DIAGNOSE -PERFORM command.
IPT342I dir IS: hex [FIN: hex] Data: count
(Response,Diagnose=PERFORM) This message shows the values for one half of a connection,
either SEND or RECV. The Initial Sequence (IS) for the connection is shown, along with the
sequence number of the FIN indicator, if known.
The total data byte count is also displayed.
Sequence numbers are displayed in hexadecimal format. The byte count is shown as a decimal
number.
IPT343D Route: name; MTU: bytes, Send MSS: bytes (req, Recv MSS: bytes, Buffer: close/
open
(Diagnose=PERFORM) This message displays static values used for the duration of the
connection.
The Maximum Transmission Unit (MTU) size determines the largest block of data that is sent.
The MTU size includes all headers and data. It is usually hardware dependent and must
accommodate the smallest value for any device that will handle the data.
The Maximum Segment Size (MSS) is a value that is negotiated by the two connection partners
at the TCP level. It is the maximum number of bytes that can appear in a single TCP datagram
(TCP header plus data). The “Recv MSS” is determined by the VSE side of the connection; the
“Send MSS” is determined by the remote end of the connection.
The minimum and default value for MSS is 536 bytes. All implementations must support this
minimum value. However, note that a small MSS increases the overhead for the total
connection because each datagram includes an additional 40 bytes of header information.

14.10
Also, the physical transport used may have a fixed data length, with the unused portion of each
block carrying filler bytes. An MSS that is too large can result in datagram fragmentation. This
means that each TCP datagram is divided into two or more IP segments. There is additional
overhead in reassembling the fragments, and each fragment is subject to packet loss and
retransmission.
The value shown within parentheses is the MSS requested by the remote host. If this value is
zero, then no MSS was specified, and VSE selected a value. If this requested value would result
in immediate fragmentation of datagrams, then VSE reduced it to the maximum value that will
not result in datagram fragmentation.
The “Buffer” values are used to control opening and closing of the Receive Window. When the
queued inbound data reaches the first value, the receive window is considered to be “closed”.
This means that the end point of the receive window will not advance again until the amount of
buffered data drops to the second, “restart” value.
IPT344I dir count blocks; count bytes. type count blocks count bytes. Eff: value
(Response,Diagnose=PERFORM) This message summarizes network usage data. One line will
be produced for the Send side of the connection and one line for the Receive side.
The block counts indicate the physical transmission blocks, regardless of data size. The byte
counts include only the data portion of the transmissions. These two counts are provided for
both the initial transmission of each datagram as well as extra transmissions due either to packet
loss (retransmits) or to duplication of already-received data.
The efficiency rating indicates that ratio of data bytes to the actual bytes traversing the network.
For example, an efficiency of 75% indicates that 25% of your network resource was consumed
by overhead while this connection was communicating.
IPT345I Open by phase in partitionID Ident: id
(Response,Diagnose=PERFORM) This message shows the name of the phase that established
the connection and the partition where the phase is running.
The “Ident” field uniquely associates all control blocks associated with this connection.
IPT346D Retransmit mode count times. Cost: value seconds.
(Diagnose=PERFORM) This message indicates the number of times that the outbound side of
the connection had to enter retransmission mode. This is not the number of times a datagram
was retransmitted, but only an indication of how many times the mode was initiated.
The “Cost” is the approximate amount of additional time used by the connection while in
retransmit mode.

14.11
IPT347I mode Retrans, Init: syn/data, Limit: min/max, Delay: delay, Retries: count
(Response,Diagnose=PERFORM) This message contains the retransmission method and rules

that are being used for this connection. All time values are shown in milliseconds.
mode may be “Fixed” or “Variable”. In fixed mode, the transmission threshold remains
constant. In variable mode, the threshold is constantly adjusted based on the observed response
times of the connection.
The “Init” values show the starting retransmission thresholds. The syn value is used during
connection negotiation. Once the connection is established, the data value becomes the starting
threshold. These “threshold” values are used to determine the point in time when this
connection will enter “retransmission mode”.
min/max are the limits for calculated retransmission thresholds. These come into play when the
threshold is being dynamically adjusted by observing connections response times. Regardless
of the value calculated, it will never exceed these two values.
The delay time is a fixed time interval that will elapses between each retransmission of a
datagram. This time is used once the connection has entered retransmission mode due to the
retransmission threshold being exceeded.
The “Retries” field indicates the number of consecutive failed retransmission attempts that will
be made before terminating the connection.
This line is produced only for non-generic displays, or when EXTENDED=YES has been
specified.
IPT348I Retran Start: cur, Times: count, Current: mode, Total: count, Cost: time sec
(Response,Diagnose=PERFORM) This message contains information on the current

retransmission state of this connection.
The current retransmission threshold, either fixed or variable, is shown.
“Times” is the number of times that this connection has entered retransmission mode.
Retransmission mode is entered whenever a datagram’s acknowledgement is not received
before the threshold time is exceeded. The connection remains in retransmission mode until all
outstanding datagrams have been acknowledged. This usually will occur as a single ACK for
the highest sequence byte sent.
The “Total” field show the aggregate number of blocks retransmitted (multiple retransmissions
may be required for the same datagram).
The “Cost” is simply the accumulated time spent in retransmission mode. This may be
considered to be the extra time required for the connection that would have been avoided under
ideal circumstances.
This line is produced only for non-generic displays or when EXTENDED=YES has been
specified.

14.12
IPT349I Pulse: status, Interval: time sec, Count: count
(Response,Diagnose=PERFORM) This message summarizes the probing (pulse) conducted to

ensure that this connection is still alive.
The status field indicates that probes are “enabled” (will be issued as required), “disabled” (not
issued under any circumstances), or “in progress” (a probe has been sent and the results have
not yet arrived).
Note that connections may have probes temporarily disabled when appropriate. For example,
some FTP client/stack combinations violate the TCP protocols by not responding to probes sent
to the control connection while a data connection is open. Because the control connection will
always receive traffic following the close of a data connection, probes are not necessary and
are, therefore, temporarily disabled.
The Interval is the time that a connection may remain totally idle before a probe is sent. A value
of zero indicates that probing will never be performed on this connection, regardless of the
pulse status setting.
The “Count” field indicates the number of times the connection has been probed since it was
first established. High and increasing values do not indicate a problem. They are merely an
indicator of an idle connection.
This line is produced only for non-generic displays or when EXTENDED=YES has been
specified.
IPT351I Input queued: bytes (blocks) Recv buffer: bytes
(Response) Produced as part of a connection display, this message shows the amount of data
that has been received by the connection but not yet delivered to an application. The value is
shown both in aggregate bytes and number of datagrams (blocks).
The message also shows the aggregate size of all unfilled RECEIVE buffers, as provided by the
application.
IPT352I Roundtrip: Min: timems Max: timems Last: timems
(Response,Diagnose=PERFORM) This value is produced only for the “send” side of a

connection and indicates how responsive the remote host has been in acknowledging
transmissions.
The “Roundtrip” times show the minimum, maximum, and most recent elapsed time required to
receive an acknowledgement for a datagram.
These are the values that are used to recalculate the retransmission threshold.
The values shown in this message reflect ONLY those that were observed while the connection
was NOT in retransmission mode. When retransmission mode is entered, statistical data
collection is suspended until normal operation resumes. This line is produced only for non-
generic displays, or when EXTENDED=YES has been specified.

14.13
IPT353I > port faddr type bsd state [(Diagnose)]
(Response) This message marks the start of data being displayed for a connection. The local
port number is listed first, followed by the foreign host (IP address and port). Type indicates the
protocol assigned to this connection.
If this is a BSD socket, the BSD socket number is displayed. This can be useful in associating a
connection with a particular BSD socket.
The connection’s current state is indicated by state:
State Description
SYN SENT Synchronization requested of remote host
SYN RECEIVED Synchronization request reply received
ESTABLISHED Connection is active
FIN WAIT1, FIN WAIT2 Finished request processing
CLOSE WAIT Waiting for local end to close
LAST ACK Waiting for last acknowledgment
TIME WAIT Timed wait
CLOSED Connection has been closed
If “(Diagnose)” is displayed, it means that a previously issued DIAGNOSE CONNECTION

command was issued with criteria that matched this connection.
IPT354I Queued inbound: num blocks num bytes [(calc) num blocks num bytes (actual)]
(Response) This message shows the amount of data that has been received and acknowledged
but not yet delivered to the application that opened the connection.
Two sets of values may be shown: those derived by actually counting the the blocks and data,
and those that have been maintained as running totals. If these values are identical, only one set
of values is shown.
It is normal for the byte counts to differ by one or two bytes, but the blocks counts should
always be identical.
IPT355I On the wire: num blocks num bytes
(Response) This message shows how much data has been transmitted but yet not acknowledged
as received by the remote host.

14.14
IPT356I type sockets; RECV: num (num), SEND: num (num), STAT: num, CLOSE: num
ABORT: num CNTL: num
(Response,Diagnose=PERFORM) If type indicates “queued”, this message summarizes all of

the socket requests that are currently queued but not complete. If type indicates “total”, then the
values reflect the totals for the connection.
The number of sockets of each type is shown along with the aggregate bytes involved in
parentheses. For SEND sockets, this value is the actual bytes to be sent. For RECV sockets, the
value represents either buffer bytes available (queued) or total bytes actually returned (total).
Note that there can be only one CLOSE socket.
IPT357I dir: hex A: hex W: hex D: hex C: hex flags time
(Response,Diagnose=PERFORM) This message is produced multiple times as part of the

response to a QUERY CONNECT command. It shows the essential values of the last few sent
and received datagrams. They are displayed in chronological order, with the oldest datagram
displayed first.
Note that a fixed number of slots are used for “send” and “receive,” so some datagrams may not
display. The value shown as time is in hh:mm:ss.ttt and is the elapsed time of this trace entry
since the start of the connection.
The values are all shown in hexadecimal. For convenience, the datagram flags (SYN, FIN,
ACK) are also shown as text.
IPT359I cnt bytes awaiting ACK. Trans: cnt times. Next Xmit: sec
(Response) This message summarizes the amount of data sent to a remote host that has not been
acknowleged.
The “Trans:” value refers to the total times the data has been sent. This includes both the initial
transmittal and all retransmit attempts.
The “Next Xmit:” value is the interval yet to elapse before a retransmit will be attempted.
IPT360I Socket type count bytes, Duration: time [Timeout: time]
(Response) This message is part of the QUERY CONNECTS display. It shows the state of one
queued socket operation of the indicated type.
The number of bytes involved in the request is shown along with the elapsed time since the
request was queued. If the operation is timed, the amount of time remaining until “timeout” is
also shown.

14.15
IPT361I IBBLOKs (dir): num, num bytes
(Response,Diagnose=PERFORM) This line is produced only if this connection “owns” one or

more IBBLOKs. These are the control blocks that contain datagrams. Incoming IBBLOKs are
discarded when the information contained has been passed to the application.
Outbound IBBLOKs are retained until the data has been acknowledged by the remote host.
IPT400I Datagram has expired. From: ip To: ip Protocol: type
(Info) While operating in GATEWAY=ON mode, TCP/IP determined that a datagram required
additional routing to an external host. However, when the datagram’s time-to-live (TTL)
counter was decremented, it reached zero. Consequently, the datagram was simply discarded.
The message text shows both the originator’s IP address and the intended final destination. The
protocol (such as TCP, UDP, ICMP) is also shown, if it is recognized.
ICMP Echo (PING) requests are exempt from this message because trace route commands
intentionally cause TTL failures.
Operator Action: In general, no action is required unless this message appears frequently. In
such a case, check your routing tables against the source and target IP addresses. It is quite
possible that circular routing has been created among two or more TCP/IP stacks. Such a
condition causes a datagram to be passed in a loop until the TTL expires and the datagram is
discarded. As a result, the datagram never reaches its destination.

14.16
15
IPU Series Messages
IPU102D Input UDP Request has been Received
(Diagnose=DEBUG) The UDP input driver has received an incoming datagram.
IPU107I UDP Check Sum Failed from source ip
(Info) A UDP datagram has arrived, but it could not be processed because the checksum did not
match.
Operator Action: This message and dump is in response to DIAGNOSE CHECKSUM. Only
10 messages and dumps will be produced for each specification of DIAGNOSE CHECKSUM.
IPU108I UDP datagram rejected from source ip
(Diagnose=REJUDP) A datagram has arrived but could not be processed.
Operator Action: This message and dump is in response to DIAGNOSE REJUDP. Only 10
messages and dumps will be produced for each specification of DIAGNOSE REJUDP.
IPU202D UDP Output Request Received
(Diagnose=DEBUG) The UDP output driver has received a datagram to transmit to a remote
host.

15.1
TCP-IP FOR VSE 1.5F Messages IPU Series Messages

15.2
16
IPX Series Messages
IPX109E CDLOAD for IPNXITFC failed:xx
(Important) During OPEN processing for a CAF-controlled ACB, a CDLOAD failed for
IPNXITFC.PHASE. xx is the hexadecimal return code from CDLOAD.
System Action: The ACB remains closed and a code of X'5C' is returned to the application
issuing the OPEN.
Administrator Action: Ensure that the library containing IPNXITFC.PHASE is in the search
chain of the application (for example, CICS) that is issuing the OPEN.
IPX110E ATTACH failed: text
(Important) During OPEN processing for a CAF-controlled ACB, an ATTACH macro was
unable to create a subtask. In the message, two possible reasons are returned:
Returned Text Meaning

“No resources” A general condition that probably indicates a lack of GETVIS.
“31 tasks running” Indicates that the application issuing the OPEN already has the
maximum number of subtasks permitted.
System Action: The ACB remains closed and a code of X'5C' is returned to the application
issuing the OPEN.
Administrator Action: Ensure that there is sufficient memory and fewer than 31 subtasks
running in the application’s partition.

16.1
TCP-IP FOR VSE 1.5F Messages IPX Series Messages
IPX111E CAF application is in use: text
(Important) During OPEN processing for a CAF-controlled ACB, it was found that the ACB
was already open. In the message, text is the application ID from the ACB.
System Action: The ACB remains closed and a code of X'58' is returned to the application
issuing the OPEN.
Administrator Action: Ensure that no other task is using the ACB.
IPX112W CAF application is inactive: text
(Important) During OPEN processing for a CAF-controlled ACB, it was found that there was
no corresponding CAF daemon.
System Action: The ACB is passed to VTAM for processing.
Operator Action: If VTAM operation is desired, no action is necessary. If CAF operation is

desired, close the ACB, start an appropriate CAF daemon, and reopen the ACB.
IPX113E CAF Wrong ACB address: text
(Important) During CLOSE processing for a CAF-controlled ACB, it was found that the
address of the ACB passed to the close routine did not match the address of the ACB that was
opened, or no open ACB was found.
In the message text is the APPL ID of the ACB being closed.
The most probable cause of this message is starting a CAF daemon while a VTAM application
(for example, CICS) is already executing.
System Action: The ACB remains open and is passed to the system for its processing.
Operator Action: Do not activate a CAF daemon against an ACB already open to VTAM.
IPX114W CAF ACB already closed: text
(Warning) During CLOSE processing for a CAF-controlled ACB, it was found that ACB was
already closed.
System Action: The ACB is marked as closed and processing continues.

16.2
IPX115E CAF synchronization error: text
(Important) During OPEN processing for a CAF-controlled ACB, it was found that the CAF
daemon had not properly recycled since the ACB was last closed.
System Action: The ACB remains closed and a code of X'58' is returned to the application
issuing the OPEN.
Operator Action: Manually cycled the CAF daemon an retry the OPEN.
IPX200I CICS Access Facility (type) Interface Startup
(Info) The CAF module responsible for interfacing between TCP/IP and CICS for performing
data transfers has been enabled.
IPX201I CICS Access Facility (type) Interface Shutdown
data transfers is being terminated.
System Action: All communications with CICS have been terminated.
Operator Action: If this was the result of a DELETE CAF command, you can restart the
module with a
DEFINE CAF command.
IPX202I CAF Handling Processing for Applid CICSappl Type FILE or CGI
data transfers is ready to begin processing requests.
IPX203E Unable to open connection for CAF
(Critical) The CAF module responsible for interfacing between TCP/IP and CICS for
performing data transfers attempted to open a SOCKET for communications with CICS, but the
request failed.
System Action: The CAF component will shut down.
Operator Action: Make sure that there are enough resources for TCP/IP to function correctly.
Contact CSI Technical Support for further assistance.

16.3
IPX204W CAF Disconnecting from Applid CICSappl Type FILE or CGI
(Warning) The CAF module responsible for interfacing between TCP/IP and CICS for
performing data transfers was forced to disconnect from CICS because of an error in
communications, or CICS was terminated, or the CICS part of CAF was disabled, or CAF is
being shut down, or TCP/IP is being terminated.
System Action: If this was the result of CICS being shut down or the CICS component of CAF
having been terminated, the TCP/IP part of CAF will attempt to reconnect and wait until the
CICS component is available once more.
Operator Action: Check if the CICS part of CAF is operational. If not, then restart it. If it is,
make sure that it hasn’t abended. If there is still a problem, CSI Technical Support.
IPX205D Initializing CAF (type) services...
(Diagnose=CAFFTP) The CAF module responsible for interfacing between TCP/IP and CICS
for performing data transfers has seen that that there is no connection between the TCP/IP stack
and CICS.
System Action: CAF will proceed to initiate a connection between CICS and CAF.
Operator Action: None. This message displays when diagnostics are enabled.
IPX206D Checking the health of the CAF (type) connection...
for performing data transfers is about to check the health of the connection between TCP/IP and
CICS, which is frequently does.
System Action: CAF will proceed to initiate a test pulse between CICS and CAF.
Operator Action: None. This message displays when diagnostics are enabled.
IPX207D CAF (type) connection test has result
for performing data transfers has finished checking the health of the connection between TCP/
IP and CICS.
System Action: If the test failed, CAF will close and re-establish its connection with CICS. If it
succeeded, then no action will occur.
Operator Action: None. This message is enables when DIAG=CAFFTP is enabled.

16.4
IPX208E CAF (type) cannot action with node
(Critical) The CAF module responsible for interfacing between TCP/IP and CICS for
performing data transfers has either attempted to establish a connection with a node (either the
local file I/O driver, or the remote CICS driver in order to accept a request and pass it onto
CICS. Depending on the action in the message, the failure was either due to an inability to
establish a connect (SOCKET OPEN failed) or to send or receive data.
System Action: The specific TCP/IP CAF interface will terminate.
Operator Action: In order to restart CAF, you will need to issue a DEFINE CAF command.
But the failure indicates the inability for the stack to process a SOCKET connection, and
debugging in that area will need to be performed.
IPX209W There is no active CAF-type connection with CICS
(Warning) A request came from the local file I/O driver to send a CAF request, but there is no
link between CICS and the TCP/IP stack.
System Action: The request will not be processed, and the requester will be informed that there
is an error.
Operator Action: This should only happen if CAF is in an error recovery mode which can
occur when the stack or CICS is in the process of being recycled. If this continues, make certain
that CICS is active. The error recovery should prevent this from taking place after a minute.
IPX210W Invalid data was returned from CICS
(Warning) A request was sent to the CICS system, and the response was not in the expected
format.
System Action: The response is discarded, the request fails, and the driver will be informed
that there is an error.
Operator Action: This should not happen. A snap dump of the response will be placed in the
TCP/IP partition’s SYSLST. If this occurs more than once, have this data and contact technical
support.
IPX211E ATTACH for PULSE routine failed. Cannot startup CAF (type).
(Critical) When the CAF (FILE) system initializes, it will issue an ATTACH for a section of its
code that will OPEN the connection to CICS and maintain its health. This failed.
System Action: Without this routine, CAF (FILE) cannot work, and so it will shut down.
Operator Action: This should not happen. Try restarting CAF, and look at the system
resources and the health of TCP/IP. If all seems to be correct, then contact technical support.

16.5
IPX400I CICS ACCESS FACILITY (CGI) STARTUP
(Info) The CAF-CGI interface in CICS is starting up. You will eventually see message IPX401I
which indicates that the CAF interface is completely up.
IPX401I - CICS ACCESS FACILITY (CGI) READY
(Info) The CAF-CGI interface in CICS is now active.
IPX402I - CICS ACCESS FACILITY (CGI) SHUTDOWN
(Info) The CICS CAF CGI interface is being terminated. All future CAF requests will not work
until CAF is restarted.
IPX403E error has occurred in CAF-CGI: xxxxxxxx
(Vital) The CAF-CGI interface made a link call to a CICS program which terminated
abnormally.
Administrator Action: Perform normal problem determination techniques in order to isolate

the cause of your local application abend.
IPX404W - Socket call failed. Retrying...
(Warning) CAF-CGI attempted to OPEN a socket, SEND a datagram, or receive a datagram,

but the socket request failed.
Administrator Action: This may be normal. If it occurs repeated and with a lot of frequency,
contact CSI Technical Support.
IPX405W - TCGI TASK ALREADY ACTIVE. IGNORED
(Vital) The CAF-CGI interface in CICS is already active and an attempt was made to start it
again.
Administrator Action: Ignore this message if the task TCGI is already active. If not, you will
need to recycle CICS.
IPX406W - UNABLE TO LOAD PROGRAM: xxxxxxxx
(Warning) A web browser request was made to call a specific CICS program. CICS responded
that it could not load the program into CICS partition GETVIS. The request fails.
Administrator Action: Verify that the program is in a sublibrary that CICS is referencing via
the CICS startup LIBDEFs. Verify that there is adequate GETVIS in the CICS partition.

16.6
IPX407W - UNABLE TO AUTHORIZE PROGRAM: xxxxxxxx
(Warning) A web browser request was made to call a specific CICS program. CICS responded
that it could not authorize the use of the requested program. The request fails.
Administrator Action: Perform typical administration debugging to determine why your CICS
will not authorize link access to that program.
IPX409I CAF-CGI is waiting for TCP/IP (SYSID=xx)
(Info) The CICS CAF CGI interface has attempted to contact the TCP/IP partition, but is not
getting any response. It will continue to wait until there is a successful connect.
Administrator Action: Make sure that TCP/IP is active and functioning.
IPX410I (Generated on date at time)
(Info) The CAF-CGI interface in CICS is starting up. This message tells you when the CGI
module was created. This message is useful when attempting to debug version mismatch
problems.
IPX425W - UNABLE TO UPDATE TCP/IP VERSIONS TABLE
(Warning) The CAF-CGI interface in CICS attempted to tell TCP/IP the CICS-interface version
information, but the attempt failed.
Administrator Action: If this occurs frequently, contact CSI Technical Support.
IPX426E - PASSING BACK A CORRUPTED XFBLOK
(Vital) The CAF-CGI interface in CICS attempted to grab data passed to it by the CICS CGI,
but the special XFBLOK header information is corrupted.
Administrator Action: Contact CSI Technical Support. This indicates a storage overlay
problem within CICS.
IPX427E - STORING A MALFORMED XFBLOK
(Vital) The CAF-CGI interface in CICS attempted to store data passed to it by the CICS CGI,
but the special XFBLOK header information is corrupted.
Administrator Action: Contact CSI Technical Support. This indicates a storage overlay
problem within CICS.
IPX500I CICS Access Facility (FTP) Starting
(Info) The TFTP transaction has started and CAF FTP is now in CICS main storage.

16.7
IPX501I CAF FTP Services are now active under CICS
(Info) The TFTP transaction has started and CAF FTP is now in communication with the TCP/
IP partition, allowing FTP processing to take place between CICS and TCP/IP.
IPX502I Terminating CAF FTP Services
(Info) The TFTP transaction has determined that CICS is coming down, or a critical error has
occurred, forcing CAF FTP to be terminated.
IPX503E CAF FTP failed to write a record to CICS
(Critical) An FTP client attempted to write a record to the CICS file system, but CICS indicated
that either the WRITE was not allowed, or that it failed.
Operator Action: Additional information will be returned to the client. Refer to that
information to resolve the problem. If you cannot make such a determination, contact CSI
Technical Support.
IPX504E CAF FTP failed: failure-type
(Critical) An FTP client attempted to perform some process within CICS but the process failed.
Additional information in the message will indicate the cause for the failure.
Operator Action: The reason can be acceptable, such as a security error, or it may not. Review
the reason for the problem. If you cannot perform problem resolution, contact CSI Technical
Support.
IPX505E CAF FTP DS-Open Failure. RC=code Port= portnum ID=TCP/IP sysid
(Critical) CAF FTP attempted to send some data back to the FTP client. It does this by opening
a data port using the standard SOCKET interface. For some reason, the OPEN SOCKET failed.
“RC” is the SOCKET macro return code. “PORT” is the FOPORT value that CAF FTP was
attempting to communicate with. “ID” is the “SYSID” value of the TCP/IP partition.
System Action: A snap dump of the cross-partition control block is also output to SYSLST for
additional debugging by Tech Support.
Operator Action: Contact CSI Technical Support if this problem continues.
IPFX06E CAF FTP Socket type failed
(Critical) CAF FTP was attempting to contact the TCP/IP partition, but either an OPEN, SEND,
or RECEIVE request failed.
System Action: If this was a problem with an OPEN request, CAF FTP will determine if TCP/
IP is active, and it will wait until it is. If TCP/IP is active, but the CAF component is not defined
to that TCP/IP system, CAF-FTP will keep waiting.

16.8
Operator Action: If TCP/IP is active, and if CAF-FTP is defined in the TCP/IP partition, and
if the default SYSID value of “00” is valid (or an alternate value specified in the CICS startup
using “// OPTION SYSPARM='xx'”), then contact CSI Technical Support for further
assistance.
IPX507E CAF FTP cannot find requested CICS program
(Critical) The FTP client requested a function that would use a CICS defined program, such as
a file I/O driver, but CAF FTP was unable to find the specific program in any of the CICS
internal tables.
Operator Action: Make sure that the program requested is spelled correctly, and if it is, make
sure it is in the CICS “CEDA” file.
IPX508I CAF-FTP about to open socket (SYSID=sysid)
(Info) CAF FTP, after being loaded into CICS storage, is attempting to establish a SOCKET
connection between the TCP/IP partition and CICS.
IPX509W CAF FTP is waiting for TCP/IP SYSID=sysid)
(Warning) CAF FTP, after being loaded into CICS storage, attempted to establish a SOCKET
connection between the TCP/IP partition and CICS, but TCP/IP has not yet responded, or
perhaps TCP/IP is down or CAF-FTP is not defined to TCP/IP. In any case, CAF FTP under
CICS will continue to wait.
Operator Action: If the SYSID is valid, and TCP/IP is up, and if CAF-FTP is defined to the
TCP/IP partition, then contact CSI Technical Support for further assistance.
IPX510I CAF FTP Message from ipaddr userid)
(Info) An FTP client issues a “SITE WTO text” request, and CAF FTP is indicating who sent it
and from where. The actual text will follow in the next line. THis information will also be
logged to SYSLST as well as SYSLOG.
IPX511E CAF FTP bad XFBLOK socket port
(Critical) A request arrived for CAF-FTP, but the cross-partition control block is corrupted.
System Action: The cross-partition control block is dumped to SYSLST.
Operator Action: If the problem repeats, recycle TCP/IP. If it continues still, contact CSI
Technical Support.

16.9
IPX512I (Generated on date at time)
(Info) The CAF-FTP interface in CICS is starting up. This message tells you when the CGI
module was created. This message is useful when attempting to debug version mismatch
problems.
IPX513I Connecting to TCP/IP port number)
(Info) The CAF-FTP interface in CICS is connecting to the TCP/IP partition. This number
should match the port number indicated in the TCP/IP partition.
IPX514I The data port is now connected)
(Info) The CAF-FTP interface in CICS was connecting to the TCP/IP partition. This message
indicates that the connection was successful.
IPX515I Waiting for a response from TCP/IP
(Info) The CAF-FTP interface in CICS has connected to the TCP/IP partition and is waiting for
TCP/IP to send a request or to send data.
IPX516I Data received from TCP/IP. Bytes=count
(Info) The CAF-FTP interface in CICS has connected to the TCP/IP partition and has received
a request or data from TCP/IP.
IPX517I Entering CAF-FTP routine: Routine name
a request from TCP/IP. It is displaying the internal routine name that is being used.
IPX518I Passing control to driver:driver name
a request from TCP/IP. It is passing control to a user-written file I/O driver.
IPX520I - Entering IPNX$FTP routine - name
(Info) This debugging message indicates that the CAF-FTP module (IPNX$FTP) is about to
execute a specific routine.
Administrator Action: This message is only displayed as part of a debugging.

16.10
17
LPD Series Messages
LPD900I Daemon Startup LPD
(Info) The Line Printer daemon is initializing.
LPD901E LP Daemon Unable to Allocate Storage, type
(Important) The Line Printer daemon could not obtain sufficient storage for the indicated
operation.
System Action: If the daemon is initializing, it terminates. If the daemon is already running, it
will re-attempt to obtain storage at 60 second intervals.
Administrator Action: Run TCP/IP for VSE in a larger partition or reduce the number of
devices/daemons that are configured.
LPD902E LP Daemon Unable to Open Connection, code
(Vital) The Line Printer daemon could not open a passive connection (to listen for work). In the
text, code is the socket return code.
System Action: The daemon terminates.
Administrator Action: Check for other messages that might indicate the reason for failure.
LPD903I Daemon Shutdown LPD
(Info) The Line Printer Daemon is shutting down.

17.1
TCP-IP FOR VSE 1.5F Messages LPD Series Messages
LPD904D Sub LP Daemon Started correctly
(Diagnose=LPD) A Line Printer Daemon task has been started to process a specific LPD
request. This sub-daemon will process the single request exclusively.
LPD905D Sub LP Daemon Processing command
(Diagnose=LPD) The Line Printer sub-daemon has received a command to process data and is
evaluating it.
LPD906E Daemon Experienced flow error
(Vital) The Line Printer sub-daemon encountered an error in the sockets interface. The sub-
daemon terminates.
Administrator Action: Retry the operation. Look for related error messages from other
components.
LPD907D Daemon Passing a negative response
(Diagnose=LPD) The Line Printer sub-daemon is refusing a command passed by a user.
LPD908D Processing the Start command
(Diagnose=LPD) The Line Printer sub-daemon is starting a printer.
LPD909D Processing the Receive command
(Diagnose=LPD) The Line Printer sub-daemon is processing a receive command.
LPD910D Processing a complete queue entry
(Diagnose=LPD) The Line Printer sub-daemon has receive a complete request for printing a
file. The request is now being parsed and processed.
LPD912E Unable to read from the intermediate file
(Vital) The Line Printer sub-daemon encountered an error while attempting to read data from
the intermediate storage file. The operation is abandoned.
Administrator Action: Retry the operation. Check the library being used for intermediate
storage. Ensure that the intermediate storage location is correctly specified in the DEFINE LPD
command.

17.2
LPD913E Unable to open intermediate file
(Vital) The Line Printer sub-daemon encountered an error while attempting to open the
intermediate storage file. The operation is abandoned.
command.
LPD914E Unable to allocate file system
(Critical) The Line Printer sub-daemon encountered an error while attempting to allocate the
file system (library) for use as an intermediate storage file. The operation is abandoned.
command.
LPD915E Unable to locate directory information
(Critical) The Line Printer sub-daemon encountered an error while attempting to access
directory information for the library to be used as an intermediate storage file. The operation is
abandoned.
command.
LPD916E Unable to open the file
(Critical) The Line Printer sub-daemon encountered an error while attempting to open the file
to be used file intermediate storage. The operation is abandoned.
command.
LPD917D Obtaining a control file
(Diagnose=LPD) The Line Printer sub-daemon is obtaining a file for the temporary storage of
control information.
LPD918D Obtaining a data file
(Diagnose=LPD) The Line Printer sub-daemon is obtaining a file for the temporary storage of
data.

17.3
LPD919E Unable to open library member
(Vital) The Line Printer sub-daemon could not open the library member to be used as
temporary storage. The operation is terminated.
command.
LPD920E Unable to write library member
(Vital) The Line Printer sub-daemon could not write to the library member to be used as
temporary storage. The operation is terminated.
command.
LPD921E Unable to close library member, Ret: aa Feedback: bb
(Vital) The Line Printer sub-daemon could not close the library member used for temporary
storage. The operation is terminated.
In the message text, aa and bb are the decimal values of the librarian return and feedback codes.
command.
LPD922D Processing the Short command
(Diagnose=LPD) The Line Printer sub-daemon is processing a SHORT command.
LPD923D Processing the Long command
(Diagnose=LPD) The Line Printer sub-daemon is processing a LONG command.
LPD924D Processing the Remove command
(Diagnose=LPD) The Line Printer sub-daemon is processing a REMOVE command.

17.4
LPD926E Unable to obtain GETVIS for incoming printout
(Vital) While processing a request, the Line Printer daemon could obtain sufficient GETVIS to
buffer the file.
System Action: The file is discarded.
Administrator Action: Increase the partition GETVIS available for LPD, decrease the size of
the incoming print files, or specify a library and sublibrary to buffer the incoming files.
LPD927E Data file not received, nothing to process
(Vital) The Line Printer Daemon could not complete processing because no data file was
received.
System Action: The daemon waits for another request.
LPD928E Control file not received, nothing to process
(Vital) The Line Printer Daemon could not complete processing because no control file was
received.
System Action: The daemon waits for another request.
LPD929E The control file did not contain an appropriate print order
(Vital) While processing the control file the Line Printer Daemon could not find a "print" order.
System Action: The file is discarded.
LPD930E Daemon-level translate table invalid. Default substituted.
(Important) During initialization, the LP daemon encountered a request to use a specific

translate table. This table has not been defined to the TCP/IP partition.
System Action: Operation continues using the system-default translate table.
Operator Action: Stop and restart the daemon after loading the appropriate translate table.
Administrator Action: Ensure that the desired translate table is valid and has been loaded into
the TCP/IP partition.

17.5
LPD931E LPD queue name already defined: xxx
(Response) A DEFINE LPD command failed because the printer queue being defined already
exists.
System Action: The DEFINE command is not executed.
Operator Action: Respecify the command with a different queue name, or delete and then
redefine the existing queue.
LPD932I LPD queue scheduled for deletion: xxx
(Info) Issued in response to a DELETE LPD command, the indicated print queue has been
flagged for deletion. Note that deletion of the queue will not occur until the Line Printer
Daemon completes any “in-flight” processes.
LPD933I LPD processing request from host for queue
(Info) An LPD request has been received for the specified queue and is now being processed.
host is the IP address and port of the sending LPR.
LPD934I LPD processing stat Host host queue
(Info) The Line Printer Daemon has completed processing an entry for the specified queue for
an LPD located at host. The message will indicate either success or failure.
LPD935I LPD queue deleted: queue
(Info) The Line Printer Daemon has completed all processing on the indicated queue and has
deleted the queue based on a pending operation delete request.
LPD936E LPD unable to allocate FRBLOK. Code xxx
(Vital) The Line Printer sub-daemon could not allocate a file resource block for temporary
storage. This error is due to a problem obtaining storage.
Administrator Action: The error code (decimal) is what was returned by the failing GETVIS
operation.
LPD937E Filename xxx does not point to library.
(Vital) The Line Printer sub-daemon could not locate the library to be used as temporary
storage. The operation is terminated.
Administrator Action: Make sure that the file name specified in the LIBRARY= parameter
identifies a library that has been defined using a DEFINE FILE command.

17.6
LPD938E Work file, x/x/x.x, did not open. Code xxx
(Vital) The Line Printer sub-daemon could not open a library member for temporary storage.
The fully qualified file name is shown in the message, as is the reason code from the open
failure.
LPD939D LPD is loaded at X'address'
(Diagnose=LPD) When running with DIAGNOSE=LPD, this message tells you where the
daemon was loaded. This may be useful when performing problem resolution.
LPD940E iii Delete of member failed. RC: rr
(Vital) The LPD daemon identified by iii was unable to delete the staging member from the
STORAGE= library. In the message text, rr is the code returned by the TCP/IP file system in
register 15 (hexadecimal). The member name is the as same as the value specified by the
TERMNAME= parameter and the extension is PRINT.
System Action: LPD processing will continue.
Operator Action: No action required if other functions are OK.
Administrator Action: Examine the console log for other messages that may indicate the
reason for failure. This message does not necessarily indicate a severe problem.
LPD941D diagnostic text
(Diagnose=LPD) This message is issued when DIAGNOSE LPD is in effect. The text of this
message may be useful when troubleshooting difficulties with LPD.
Operator Action: This message may be eliminated by use of the DIAGNOSE -LPD command.

17.7

17.8
18
NTP Series Messages
NTP100I NTP Daemon Running
(Info) The NTP Daemon has started processing.
NTP101E Socket xxx failed yyy. Code zzz
(Warning) The NTP Daemon has encountered a communications problem. In the message text,
xxx indicates the type of operation that failed, and yyy indicates if the failure occurred before or
after the operation was scheduled. zzz is the decimal return code from the socket interface.
The socket codes are discussed in IPN950I (Socket Scheduling Codes) and IPN951I (Socket
return codes—SRCODE).
System Action: The NTP Daemon shuts down.
Operator Action: Restart the NTP Daemon.
Administrator Action: If this problem is persistent or frequent, contact CSI Technical

Support.
NTP102I NTP Daemon shutdown complete
(Info) The NTP Daemon has terminated processing.

18.1
TCP-IP FOR VSE 1.5F Messages NTP Series Messages
NTP103E Date not "SYSTEM"
(Important) The NTP Daemon has found that the date returned by the operating system is being
obtained from a JCL statement. The NTP Daemon requires that the date be calculated from the
TOD clock.
Operator Action: Correct the TCP/IP startup JCL.
NTP104E Year out of range
(Important) The NTP Daemon has determined that the current time (as returned by VSE) is
before 1999 or after 2016.
Operator Action: Ensure that the VSE system date is set correctly.
Administrator Action: In the unlikely event that you are running this code after 2016, contact
Connectivity Systems for an updated version.
NTP105I Daemon: ID xxx
(Info) Issued in response to a QUERY command, this message and those that follow will
display information pertaining to the NTP Daemon defined with ID=xxx
NTP106I Protocol: xxx Port yyy
(Info) Issued in response to a QUERY command, this message indicates the protocol being
used by the Daemon (UDP or TCP) and the port being monitored for requests.
NTP107I Hour correction: xxx. Second correction: yyy
(Info) Issued in response to a QUERY command, this message shows the adjustments being
applied to the TOD clock value prior to transmission to the remote NTP client. In the text, xxx is
a signed value for hours, and yyy is a signed value for number of seconds. Both values are
added to the time algebraically.
NTP108I Requests: xxx Last requestor: n.n.n.n
(Info) Issued in response to a QUERY command, this message shows the total time requests the
daemon has handled as well as the IP address of the last remote host to make a request.

18.2
NTP109E NTBLOK chain corrupt
(Vital) During termination, the NTP Daemon was unable to unchain its NTBLOK. This
indicates a storage-overlay problem.
System Action: Daemon termination completes without releasing the NTBLOK.
Operator Action: It may be necessary to cycle the TCP/IP partition before the NTP Daemon
can be restarted.

18.3

18.4
19
RSA Series Messages
RSA001E Modulation failed
(Critical) The RSA module was unable to calculate the correct value. The request to generate a
valid value failed.
Administrator Action: Contact CSI Technical Support.

19.1
TCP-IP FOR VSE 1.5F Messages RSA Series Messages

19.2
20
SEE Series Messages
SEE100D SVSEMNTR loaded at xxxxxxxx
(Diagnose) This message indicates that the SeeVSE product has loaded its monitoring phase.
SEE106W SeeVSE product code check failed
(Warning) This SeeVSE product attempted to initialize TCP/IP monitoring, but the
initialization process failed during the product code check.

20.1
TCP-IP FOR VSE 1.5F Messages SEE Series Messages

20.2
21
SHL Series Messages
SHL017E REXX SHELLMSG() function error: GETPARM failed
(Critical) A REXX shell attempted to issue the SHELLMSG function to return data to the RSH
or REXEC client using a stem, but the SHELLMSG function was unable to read any data
within the stem.
Administrator Action: Correct the logic of the REXX shell.

21.1
TCP-IP FOR VSE 1.5F Messages SHL Series Messages

21.2
22
SOC Series Messages
SOC001E SOCKET request type was missing
(Info) The REXX SOCKET function was invoked, but no “type” was issued (OPEN, CLOSE,
SEND, RECEIVE, STATUS, or ABORT).
Administrator Action: Correct the SOCKET call syntax being used.
SOC002E RPC is not supported
(Vital) The REXX SOCKET function was invoked, but a type of “RPC” was issued. This
SOCKET type is not supported.
SOC003E SOCKET request type is invalid.
(Info) The REXX SOCKET function was invoked, but the type was not valid.
Administrator Action: Correct the SOCKET call syntax to use one of the following types:
OPEN, CLOSE, SEND, RECEIVE, STATUS, or ABORT.
SOC004E SOCKET function is missing or invalid.
(Info) The REXX SOCKET function was invoked, but the type was not in the correct sequence
(for example, using SEND before OPEN).

22.1
TCP-IP FOR VSE 1.5F Messages SOC Series Messages
SOC005E GETVIS failed to acquire handle
(Important) The REXX SOCKET function was invoked, but it was unable to acquire enough
GETVIS to perform the request.
Administrator Action: Provide more partition GETVIS.
SOC006E LOPORT value missing or invalid
(Info) The REXX SOCKET function was invoked, but the LOPORT value was non-numeric,
greater than 64k, or was never set.
Administrator Action: Correct the SOCKET call syntax being used. The local port value must
be a number between 0 and 64k.
SOC008E FOIP value missing or invalid
(Info) The REXX SOCKET function was invoked, but the FOIP value is either non-numeric or
not in the format of nnn.nnn.nnn.nnn .
SOC009E FOPORT is only valid for clients, not servers
(Info) The REXX SOCKET function was invoked, but the FOPORT value was passed along
with an indicator that this program is to be used as a server. You cannot do this.
Administrator Action: Correct the SOCKET call syntax being used. Remove the FOPORT
setting, or set the program up as a client.
SOC010E FOPORT value is invalid
(Info) The REXX SOCKET function was invoked, but the FOPORT value was non-numeric,
greater than 64k, or was never set.
Administrator Action: Correct the SOCKET call syntax being used. The foreign port value
must be a number between 0 and 64k.
SOC011E SYSID value is invalid
(Info) The REXX SOCKET function was invoked, but the SYSID value is not 2 bytes long.
Administrator Action: Correct the SOCKET call syntax being used. The SYSID value must
be 2 bytes long.

22.2
SOC012E TIMEOUT value is invalid.
(Info) The REXX SOCKET function was invoked, but the timeout value is not numeric.
Administrator Action: Correct the SOCKET call syntax being used. The timeout value must
be a valid number.
SOC013E ASYNCH option is invalid.
(Info) The REXX SOCKET function was invoked, but the ASYNCH option is not YES or NO.
Administrator Action: Correct the SOCKET call syntax being used. The ASYNCH option
must be YES or NO.
SOC014E SOCKET failed to info
(Vital) The REXX SOCKET function attempted to issue a SOCKET call. However, the OPEN,
CLOSE, SEND, RECEIVE, STATUS, or ABORT request failed.
SOC015I Rexx Sockets version (type) - date: time
(Info) The SOCKET function has been invoked by REXX/VSE. This message provides you
with generation information.
SOC016I Copyright (c) date, Connectivity Systems, Inc.
(Info) The SOCKET function has been invoked by REXX/VSE. This message is the software
copyright information.
SOC017W RECEIVE request timed out
(Info) The REXX SOCKET function was invoked to perform a RECEIVE, but it timed out.
Administrator Action: Check your server connection, or increase the timeout value.
SOC018E SEND is missing data
(Info) The REXX SOCKET function was invoked to perform a SEND, but no data was passed
with it.
Administrator Action: Check your program to ensure that there is actual data that needs to be
passed.

22.3
SOC020E Cannot set variable RC=X'nn' Reas=X'nn'
(Vital) The REXX SOCKET function attempted to set a REXX variable. The return code and
reason code information is based on the IBM documentation in the REXX/VSE Reference.
SOC030E Data port status failed
(Important) The SOCKET function that has been invoked by REXX is trying to get the Socket
STATUS in order to obtain the local port number, but the SOCKET STATUS failed.
Operator Action: Retry the application. If it continues to fail, contact CSI Technical Support.
SOC031E Data port status failure
STATUS in order to obtain the local port number, but the SOCKET never connected.
SOC032E Unable to obtain local port number
STATUS in order to obtain the local port number, but the SOCKET never went into a LISTEN
state.
SOC033E CLIENT/SERVER option is incorrectly set
(Info) The REXX SOCKET function was invoked, but the CLIENT/SERVER option is not set
to CLIENT or SERVER.
SOC034E Local TCP/IP system is not available
(Important) The REXX SOCKET function was invoked, but on that same system there is no
TCP/IP system up with a matching SYSID.
Administrator Action: Wait until TCP/IP is up, or change the SYSID in your SOCKET call.

22.4
23
SSL Series Messages
SSL100D phase diagnostic information
(Diagnose) This message is issued when in diagnostic mode. It contains the name and version
of the SSL-related phase being used.
SSL101D xxx request started handle=yyy
(Diagnose) This message is issued when in diagnostic mode. It shows the function requested by
an SSL application.
SSL102D xxx request completed R15=yyy handle=zzz
(Diagnose) This message is issued when in diagnostic mode. It displays information about the
completion of a function requested by an SSL application.
SSL103D xxx failed RC=yyy(zzz) handle=addr
(Diagnose) This message is issued when in diagnostic mode.
An SSL request made by application xxx has failed. The return code and handle information is
in the message text.
SSL104W Hardware Crypto init failed R15=xxx for yyy
(Warning, Security) This message indicates that an attempt to initialize the Crypto Express 2
has failed. The text shows the code returned by the initialization request and the name of the
SSL application.

23.1
TCP-IP FOR VSE 1.5F Messages SSL Series Messages
SSL106D Hardware Crypto initialized for xxx
The indicated SSL appplication has successfully initialized the Crypto Express 2.
SSL107D Waiting for Close_Notify
An SSL application has requested a secure socket close. The close_notify has been sent to the
foreign SSL application, and we are waiting for a close_notify from the foreign application.
SSL108D xxx ciphers=yyy
The indicated SSL application has completed its handshake and will use the cipher shown.
SSL109D Session resumed xxx
(Diagnose) This message is issued when in diagnostic mode. The indicated SSL application has
resumed an SSL session.
SSL110D Server xxx handshake. Cipher=yyy zzz=aaa
The local server has started a handshake with a client using the displayed cipher and options.
SSL111D VSE available ciphers=xxx
The ciphers currently available to an SSL application are shown.
SSL112I IPDSCRFI LIB SUBLIB MEMBER TYPE successful xxx
(Info) This message is issued when SSL is requesting a VSE librarian member.
SSL113W IPDSCRFI get for LIB SUBLIB MEMBER TYPE failed
(Warning) This message is issued when in diagnostic mode. It is issued when a SSL request for
a VSE librarian member has failed.

23.2
SSL114I xxx successfully read
(Info) This message is issued when in diagnostic mode. It is issued when a SSL request for a
VSE sequential disk file has succeeded.
SSL115W Socket failed reason=xxx retcd=yyy errcd=zzz
(Warning) This message is issued when in diagnostic mode. It is issued when the CIALSRVR
program socket request has failed.
SSL116D text
The message text contains diagnostic information regarding an application’s SSL request.
SSL117D xxx failed reason=yyy disp=zzz
An SSL request made by application xxx has failed. The return code and disposition
information are shown.
SSL118D Close_Notify Alert received
An SSL application has received a close_notify from the foreign application.
SSL200I function version date time entrypoint-addr constantarea-addr dynworkarea-addr
The $SOCKDBG phase issued this message according to its MSGT setting. See Appendix B,
“$SOCKDBG Debugging Phase,” in the TCP/IP FOR VSE Programmer’s Guide.
SSL201D function request started handle=addr
SSL202D function request completed R15=xxxxxxxx handle=yyyyyyyy

23.3
SSL203E function failed RC=xxxxxxxx(yyyyyyyy) reason=zzzzzzzz
SSL303E xxx failed RC=yyy(zzz) reason=yyyyyyy
(Important) This message is issued when the requested function has failed for IPDSCRFI.
SSL400I Hardware Crypto Assist supports: [SDES TDES AES128]
(Important) This message is issued during startup of an SSL application when a $SOCKOPT
phase using option SSLCIPH=H (hardware) is specified.
A Crypto Hardware Assist query has been issued, and the supported cipher algorithms are
displayed.
SSL401W Hardware Crypto Assist detected with no AES or DES support kmc
(Warning) This message is issued during startup of an SSL application when a $SOCKOPT
phase using option SSLCIPH=H (hardware) is specified.
A Crypto Hardware Assist query was issued, but none of the cipher algorithms needed for
efficient encryption are supported.
Administrator Action: Contact your IBM hardware CE for current microcode updates to
support the DES and AES algorithms.
SSL402I SSL cipher suites allowed: hex_num_list
(Info) This message is issued during startup of an SSL application when a $SOCKOPT phase
using option SSLCIPH=H (hardware) is specified.
A Crypto Hardware Assist query was issued, and the allowed cipher suites are displayed. The
hexadecimal values correspond to the following SSL cipher suites:
Value Cipher
08 RSA_SDES040_SHA
09 RSA_SDES056_SHA
0A RSA_TDES168_SHA
2F RSA_AES128_SHA
35 RSA_AES256_SHA

23.4
24
TCP Series Messages
TCP140E Dynamic file type is not found
(Vital) An autonomous (dynamic) file was specified in an ATTACH (or SEND) command, but
no valid file type was passed to the EMAIL client.
System Action: The EMAIL job is aborted.
Operator Action: Ensure that a valid file type is specified in the autonomous file syntax, then
resubmit the job. See the TCP/IP FOR VSE User Guide, chapter 6, “TCP FOR VSE Email,” for a
list of file types you can specify with the ATTACH and SEND commands.
TCP700I client name (version info) has initialized.
(Info) The batch utility indicated in the message had performed the subtasking required to
perform console and printer messaging.
System Action: The program continues.
TCP701I client name TCP/IP (SYSID=xx) is inactive
(Info) The batch utility did not find a socket queue allocated for the desired SYSID. Depending
on the “WAIT” option, the program will either terminate or wait for TCP/IP to become
available.
Operator Action: Compare the SYSID in the message to the SYSID you need. If they do not
match, then correct the execution parameter. If they do match, then ignore the message.

24.1
TCP-IP FOR VSE 1.5F Messages TCP Series Messages
TCP702I client name TCP/IP (SYSID=xx) is active in partition
(Info) The batch utility found the correct TCP/IP stack, determined its stability, and tested
communications successfully.
Operator Action: None. To suppress this message, enable QUIET mode.
TCP703I client name Waiting for TCP/IP (sysid) to become active...
(Info) The batch utility did not find a socket queue allocated for the desired SYSID. It is
indicating that it will wait.
System Action: It will keep waiting until you MSG the partition or until the stack with the
matching SYSID becomes active.
TCP704I client name : Issue "MSG partition to terminate wait
(Info) The batch utility did not find a socket queue allocated for the desired SYSID. It is
indicating the command you can issue to the console to terminate the wait.
System Action: It will keep waiting until you MSG the partition or until the stack with the
matching SYSID becomes active.
TCP705I Terminating due to operator request.
(Info) While CHECKTCP was waiting for TCP/IP to become available, the operator messaged
the partition.
System Action: CHECKTCP will terminate.
TCP706I client name TCP/IP (SYSID=xx) is in recovery mode.
(Info) The batch utility found a socket queue, but a bit is set that indicates that the stack is
currently trying to recover from a previous crash.
System Action: Depending on the “WAIT=” parameter, the program will either continue to
wait or set a return code.
Operator Action: None. Informational only when “DEBUG” is enabled.

24.2
TCP707I client name TCP/IP (SYSID=xx) is initializing
currently initializing and is not ready to accept requests.
System Action: The program will either continue to wait or set a return code, depending on the
“WAIT=” parameter.
TCP708I client name EOJ RC=n
(Info) The batch utility is terminating. This message indicates the final return code.
Operator Action: To disable this message, disable debugging.
TCP709I client name TCP/IP (SYSID=xx) is initialized in partition
(Info) The batch utility found a socket queue that is not only allocated for the desired SYSID,
but has an indicator that it is ready to take commands.
TCP710I client name : TCP/IP (SYSID=xx) is not responding in partition
(Info) The batch utility found the correct TCP/IP stack and determined its stability, but
communications have failed.
System Action: The program will retry and wait.
Operator Action: None. To suppress this message, enable QUIET mode.
TCP711I client name : TCP/IP (SYSID=xx) crashed. Waiting... t< Info
(Info) The batch utility found a socket queue in which the designated partition does not have a
currently running stack. This typically means that the stack was brought down in an abnormal
manner.
System Action: Depending on the “WAIT” option, the program will either terminate or wait
for TCP/IP to become available.
Operator Action: Bring the TCP/IP stack up, or MSG the CHECKTCP partition to continue if
WAIT=YES.

24.3
TCP712I client name TCP/IP (SYSID=xx) is shutting down
shutting down.
System Action: The program will either continue to wait or set a return code, depending on the
“WAIT=” parameter setting.
TCP800E Bad XOBLOK passed to TCP/IP. Review dump for XOBL
(Info) This message is issued when an application produced with the TCP/IP preprocessor API
passes a faulty XOBLOK area to the stack interface routine.
System Action: The area passed as an XOBLOK will be dumped along with the application
transaction task. The label “XOBL” will be attached to the diagnostics. The application will be
terminated.
Operator Action: Capture the dump output, and forward it to the programmer responsible for
the application.
TCP801D IPNETX API: cmd failed to opt. RC: rc RE: re Loc: loc
(Diagnose) This message is produced when an application was precompiled with the
“DEBUG=YES” option. It is issued anytime a request returns a non-zero return code.
System Action: Execution continues with the appropriate codes returned to the application.
Operator Action: Inform the application programmer that messages are being issued.
Administrator Action: If these messages are not needed, recompile the program without
“DEBUG=YES”. A variety of information is included in the message. cmd indicates the
command being processed. opt will either be “schedule” to indicate a basic failure of the
request, or “complete” to indicate that the operation was accepted but failed after it was passed
to the stack.
The rc, re, and loc fields will show the Return code, reason code, and location code,
respectively, as decimal values.
If the location code is 14, then the problem is caused by an invalid or inappropriate value in the
XOBLOK. The bad value will be disclosed by the contents of the return code, as follows:
Ret Code Meaning

16 The descriptor (XODESC) is zero
20 The descriptor (XODESC) is NOT zero
24 XOCOMMND does not contain a valid command such as OPEN or SEND
28 XOACCESS does not contain a valid protocol such as TCP, UDP, or TELNET
For other location codes, an explanation of the scheduling codes is included with message
IPN950I. Codes returned at the completion of an operation may be found in message IPN951I.

24.4
TCP802E IPNETX API: XODESC is zero
(Info) This message is produced when the descriptor field is zero for all calls except OPEN.
This indicates that the connection has either not been opened or is already closed.
System Action: The requested operation is not performed.
TCP803E IPNETX API: XODESC not zero for OPEN
(Info) This message is produced when the XODESC field is not cleared to nulls prior to issuing
an OPEN. This usually occurs when you attempt to OPEN a new SOCKET connection without
closing the old one first (CLOSE clears XODESC).
System Action: The OPEN request is not performed.
Administrator Action: Correct the programming logic.
TCP804E IPNETX API: Unknown command passed
(Info) This message is produced when a bad control block is passed to the API. This will occur
if you have modified your IPNETPRE output manually, or if storage somehow has been
overlaid.
System Action: The request terminates.
Administrator Action: If this is not the result of manually modifying the output from
IPNETPRE, contact CSI Technical Support for further assistance.
TCP805E IPNETX API: Unrecognized protocol
(Info) This message indicates that an unknown protocol was specified in the XOACCESS field
passed to the TCP/IP interface routine. This usually is caused by modifying the code produced
by the preprocessor or by incorrectly modifying the XOBLOK.
System Action: The requested operation is not performed.
Administrator Action: Valid protocols include TCP, UDP, TELNET, RPC, CLIENT, FTP.
TCP900I Daemon Startup Client Automation Daemon
(Info) The daemon that monitors POWER queues for entries to be transmitted by TCP/IP is
starting.
TCP901I Daemon Shutdown Client Automation Daemon
(Info) The daemon that monitors POWER queues for entries to be transmitted by TCP/IP is
terminating.

24.5
TCP902D Client Automation Daemon -- Checking for work
(Diagnose=CLIENTD) The automation daemon is testing the queue for pending work.
TCP903E Unable to establish power connection - Ident
(Vital) The automation daemon was unable to identify a path to POWER.
Administrator Action: Ensure that the TCP/IP FOR VSE partition is operating under
POWER’s control.
TCP904E Unable to establish power connection - Connect
(Vital) The automation daemon was unable to connect with POWER. This indicates a potential
system failure.
Administrator Action: Check for related messages, especially from POWER. Correct any
apparent problems, especially storage shortages, and try again.
TCP905D Client Automation Daemon -- Action has been recognized
(Diagnose=CLIENTD) An event has occurred that matches an event definition. TCP/IP FOR
VSE will process accordingly.
TCP906E Client socket failure has occurred
(Critical) The Automation daemon has experienced an error in the sockets API. The daemon
has abandoned the current work.
TCP907I Processing Output: a for automated printing at: b on: c
(Info) The Automation daemon has selected a job for transmitting to a remote printer. In the
message text, a is the POWER job name, b is the IP address of the target host, and c is the name
of the printer.
TCP908I Processing Output: aaa has failed
(Info) TCP/IP FOR VSE was unable to process POWER member aaa as specified by an event
definition.
TCP909I Processing Output: a has completed
(Info) The Automation daemon has completed transmitting POWER job a.

24.6
TCP910D text
(Diagnose=LPR) This message is issued when DIAGNOSE=LPR is in effect. The text is

variable and describes the currently executing LPR script.
TCP911D Processing Event: aa Type: bb Action: cc
(Diagnose=CLIENTD) The automation daemon has found a work element that matches its
selection criteria. The event name (aa), type (bb), and action (cc) are included in the message
text.
System Action: The daemon processes the selected work.
TCP912I Processing Class: aa Job: bb cc dd
(Info) The automation daemon is processing an element for auto FTP. The message displays the
job name information and destination.
System Action: The daemon processes the selected work.
TCP913I Event Deleted: xxx
(Response) Issued in response to a DELETE EVENT command, this message indicates that the
named event has been successfully deleted.
System Action: The Automation daemon continues processing for the remaining events. If no
events remain, the automation daemon terminates. Defining new events will re-initialize the
Automation daemon.
TCP914W Retrying Event: aa Type: bb Action: cc
(Warning) The automation daemon has found a work element that failed and is retrying the
operation. The event name (aa), type (bb), and action (cc) are included in the message text.
System Action: The daemon retries the selected work.
TCP915I text
(Info) A PING command was issued from the console. The PING diagnostic message is
displayed.

24.7
TCP916W Unable to attach task for clientd operation
(Warning) The automation daemon attempted to attach a subtask, but the operation failed
because of insufficient storage or an internal error.
System Action: If you have sufficient GETVIS in the TCP/IP partition, contact CSI Technical
Support.
TCP917W Suspending listing due to failure. Name: pwrname, pwrnum
(Warning) The automation daemon attempted to send a POWER queue entry, but the operation
failed.
System Action: Enable SET DIAGNOSE for the client, and determine the cause of the error.
Correct the script, and then restart the client.

24.8
25
TEL Series Messages
TEL900I Daemon Startup Telnet Termname: aa port: bb
(Info) Each TELNET daemon issues this message on startup. The four hexadecimal digits
preceding the message ID indicate the pseudo task number associated with the daemon. aa is
the terminal name (LUname) of the virtual terminal, and bb indicates the TCP port being
monitored by the daemon.
TEL902D Negotiate: diagnostic text
(Diagnose=TELNET) This message is issued in response to a DIAGNOSE TELNET command

and conveys information pertinent to the process of session negotiation. At this point, the
Telent Client and daemon are exchanging parameters that will be used to govern the session.
No application is involved yet.
The content of this message will be self-explanatory or of interest to CSI Technical Support.
Messages from different daemons can be associated by examining the 4-character p-task
identifier that precedes each message.
Operator Action: This message can be eliminated by issuing the DIAGNOSE -TELNET
command.
TEL907D VTAM: diagnostic text
(Diagnose=TELNET) This message is issued in response to a DIAGNOSE TELNET command

and conveys information about the daemon’s connection with VTAM.
Operator Action: This message can be eliminated by issuing the DIAGNOSE -TELNET
command.

25.1
TCP-IP FOR VSE 1.5F Messages TEL Series Messages
TEL910D Network: diagnostic text
(Diagnose=TELNET) This message is issued in response to a DIAGNOSE TELNET

command. It conveys information about the daemon’s network connection through TCP/IP.
Operator Action: This message can be eliminated by issuing DIAGNOSE -TELNET.
TEL912E Unable to open VTAM ACB, Code: aaa Applid: bbb LU: ccc
(Vital) While initiating a Telnet session, this daemon was unable to open a connection with
VTAM. bbb is the target application, and ccc is the virtual terminal (LU).
The code, aaa, is the hexadecimal value returned by VTAM in the failing ACB. Some common
values are as follows:
Code Meaning
24 The APPL definition specified a password (not supported)
52 VTAM is shutting down.
54 The Applid (LU) is not defined to VTAM
56 The Applid, although defined, is not an appl
58 The Applid is already open
5A The Applid is not active (use V NET,ACT command)
5C VTAM not active or running at lower priority than TCP/IP
88 Temporary storage shortage
System Action: This daemon shuts down.
Operator Action: Check the console log for related VTAM messages. Ensure that the VTAM
definitions for the application ID and the LU name are correct. Restart the daemon.
TEL913I Socket CLOSE failure (a) Code: bb IPaddr: cc
(Vital) A transmission error has occurred during session termination. A CLOSE operation did
not complete as expected. In the text, a indicates either “A,” the CLOSE macro failed during
scheduling, or “B,” the failure occurred during actual transmission.
bb is the decimal code returned by CLOSE. Note that a code of 4 indicates that the socket was
already closed (probably by the client); this is normal. The socket codes are listed in IPN950I
Socket Scheduling Codes and IPN951I Socket return codes (SRCODE).
This message is produced only when DIAGNOSE TELNET is in effect.
System Action: The daemon resets and waits for another connection.

25.2
TEL916E Telnet Open error, R15: aaa Termname: bbb Target: ccc Macro: ddd
(Vital) The Telnet daemon issued a REQSESS to obtain a VTAM connection with ccc.
However, this request was refused by the target application or failed by VTAM.
This message is followed by TEL956E, which identifies the IP address from which the
connection request is being made.
Operator Action: Check additional TCP/IP and VTAM messages to determine the cause.
Ensure that the target application is active and accepting logins. Restart the daemon.
Administrator Action: In the case of CICS, be sure that the LU, bbb, is not flagged as “out-of-
service” and that CICS will accept a connection with that LU name. Especially, check that
security software is not objecting to the device.
TEL917I Daemon Resetting Telnet Termname: aa IPaddr: bbb
(Info) The daemon is closing down the session for virtual terminal (LU name) aa. The daemon
will then restart and wait for another request.
TEL918I Daemon Shutdown Telnet Termname: aa
(Info) The daemon is closing down the session for virtual terminal (LU name) aa. This
shutdown is due to an operator DELETE TELNETD command, a shutdown of the TCP/IP
partition, or an abend of the Telnet daemon.
TEL919I Daemon Shutdown Telnet Termname: aa
(Info) The daemon is closing down the session for virtual terminal (LU name) aa.
Administrator Action: Restart the daemon.
TEL920I ID: aaa (status)
(Response) Each TELNET daemon is identified by its unique ID, entered when the daemon was
created with the DEFINE TELNETD command. The status can be either Active or Inactive.
TEL921I Terminal: aaaa Target/Menu: bbbb
(Response) The terminal field is the name of the VTAM LUname that will be associated with
the client. The Target is the VTAM application ID for this connection. If Menu is specified, it is
the name of the menu that will be displayed.

25.3
TEL922I Port: aa Match IP: n.n.n.n
(Response) The port number is the TCP/IP port monitored by the Telnet daemon. The Match IP
is either an IP address or zero-host pattern that identifies which remote host(s) may connect.
Note that an address of 0.0.0.0 matches any request.
TEL923I aaa, bbb, ccc, ddd
(Response) The values for LOGMODE, LOGMODE2, LOGMODE3, and LOGMODE4 are
displayed.
TEL924I TN3270E: aaa Group: bbb Generic: ccc
(Response) Issued in response to the QUERY TELNETDS command, this message indicates
how TN3270E options are handled. “Listener” indicates that the daemon will handle session
negotiation but will NOT handle VTAM communication. “Effector” indicates that the daemon
will handle the VTAM portion of a previously negotiated session.
If specified, the group name must match on both the listener and effector. If omitted for a
listener, any effector will match. If omitted for an effector, any listener will match.
The Generic value is valid only on a listener. If present it names the effector group that will be
used to satisfy requests that do NOT specify an LUname.
TEL925I Session: aaa, bbb, ccc
(Response) This message is issued only for Telnet daemons that are currently connected to
clients. It displays the client’s IP address, the VTAM application currently in-session with the
client, and the LOGMODE being used.
TEL927D/I TELNETDS diagnostic: func RC=value RS=value
(Diagnostic/Info) This message provides diagnostic information that may be used to

troubleshoot a problem. The func field indicates where an error was detected, and RC/RS are
the return code (in hex) and the reason code, respectively. CSI Technical Support can use these
codes to help identify the error if the problem cannot be resolved.
The func field values are described in the following table.
func value Description

SSLIFAIL The SSL environment failed to initialize
TNPOOLNO An attempt was made to initialize SSL with POOL=YES, which is not allowed
SREDSSLN SSL handshaking failed
SREDFAIL SSL rejected the parameters passed to it for authentication
SREDFA15 SSL RECEIVE and decrypt process failed. RC contains the SOCKET R15 value

25.4
func value Description

SREDFASR SOCKET RECEIVE of SSL data failed. RC contains the SOCKET SRCODE
value
SREDNU15 SSL RECEIVE of null data failed. RC contains the SOCKET R15 value.
SREDNUSR SOCKET RECEIVE of null SSL data failed. RC contains the SOCKET
SRCODE value.
SSLR15BD SSL queuing of a RECEIVE failed. RC contains the SOCKET R15 value.
SSLSRBD SSL RECEIVE did not return expected data. RC contains the SOCKET
SRCODE value.
SSLW15BD SSL initiating a SEND of data failed. RC contains the SOCKET R15 value.
SSLWSRBD SSL was unable to send data. RC contains the SOCKET SRCODE value.
TELMFAIL Unable to produce the telnet menu for the user
TELMSCMN The telnet menu is not suitable for the receiving user
TELMSWFA A SEND of the telnet menu failed
CALMPULF An attempt to wait for the user to enter data (0-length read) into the telnet menu
failed
CALMRNFA The waiting for the user to enter something into the telnet menu failed
CALMGTLF A read of data entered into the telnet menu failed
CALMBNPO An invalid length was returned from the user response to the telnet menu
CALMSREF The data queued to the telnet menu failed to be passed to the application
SSLHSSLN SSL negotiation failed
SSLHSINI SSL parameters for the negotiation were rejected
SWRTSSLN Writing/sending of SSL data failed during initialization
SWRTFAIL Writing/sending of SSL data failed during encryption
SWRTFA15 Writing/sending of non-encrypted data failed during SOCKET call. RC contains
the R15 value of the SOCKET call
SWRTSRBD Writing/sending of non-encrypted data failed after a SOCKET call. RC contains
the SRCODE value.
Operator Action: The diagnostic messages (those that have a “D” suffix) may be suppressed
by using the following command:
DIAG -TELNET
Both non-diagnostic messages (those that have an “I” suffix) and diagnostic messages may be
suppressed by using the following command:
MESSAGE MSGID=TEL927,CONSOLE=no

25.5
TEL936I Telnet Session Established via: aaa from Ipaddr: bbb To: ccc
(Info) All session negotiations are completed, and a Telnet session now exists. aaa is the
APPLid being by the daemon (LUname), bbb is the IP address of the Telnet client, and ccc is
the APPLid of the target application.
TEL938I Telnet user entering menu from: aaa via: bbb
(Info) All session negotiations are completed and a Telnet session now exists for a user at IP
address aaa. The user is not yet connected with an application but is interacting with the menu.
bbb is the LUname for the session.
TEL942E VTAM op: xxxx RTNCD: rr FDBK2: ff
(Vital) The TELNET daemon received a bad completion code from a VTAM operation. This
message is issued from a SYNAD or LERAD exit. In the message text, xxxx indicates the
VTAM macro that failed, rr is the recovery action (return) code in hexadecimal, and ff is the
RPL feedback code in hexadecimal.
TEL943E Sense: ss Modifier: mm User Sense: uuuu
(Vital) The Telnet daemon received a bad completion code from a VTAM operation. This
message is issued from a SYNAD or LERAD exit in conjunction with message TEL942E. In
the message text, ss is the System Sense byte, mm is the System Sense Modifier, and uuuu is the
User Sense data.
TEL952E Insufficient GETVIS for menu. IP address: aaa
(Important) During initiation of a TN3270 session, the daemon was unable to acquire enough
GETVIS to load a copy of the Telnet menu.
System Action: The session is terminated.

25.6
TEL953E Critical error in menu chain. Menu aaa IP address: bbb
(Important) During initiation of a TN3270 session, the daemon was unable to run the menu
chain to locate the requested menu.
System Action: The session is terminated.
Operator Action: Cycle the TCP/IP partition to regain menu capability.
TEL954E Menu not found. Menu aaa IP address: bbb
(Important) During initiation of a TN3270 session, the daemon was unable to to locate the
requested menu. The session is terminated.
TEL955E Security failure. User ID: aaa IP address: bbb
(Security) While processing the User ID and password fields on a TN3270 menu, the user
repeatedly failed to provide the appropriate password.
System Action: The terminal session is terminated.
Administrator Action: This message may indicate a user who has forgotten a password or an
attempt to gain unauthorized access to your system.
TEL956E From IP Address: aaa
(Vital) This message immediately follows another TEL message and provides the IP address
connected to the daemon at the time of the error.
Operator Action: Check additional Telnet-issued messages for a description of the problem.
TEL957E OPNSEC error, Return: aaa. Reason: bbb Feedback: ccc Sense: ddd
(Vital) VTAM has refused a request to complete establishment of a session. Because this is
occurring after VTAM requested the daemon for a session, this may indicate a problem with the
BIND parameters.
System Action: The session is rejected. The daemon resets.
Administrator Action: Examine the displayed codes and consult the VTAM Programmer’s
manual for additional information. The Sense code (ddd) can be found in the SNA manual set.
TEL960E Insufficient GETVIS: rc
(Vital) The TELNET daemon was unable to obtain sufficient partition GETVIS for startup. The
hexadecimal code returned by the GETVIS macro is shown in the message text.

25.7
TEL961E VTAM GENCB failed. R15: xx R0: yy
(Vital) The TELNET daemon failed while constructing VTAM control blocks using the
GENCB macro. The hexadecimal codes returned in registers 15 and 0 are shown in the message
text.
TEL962E Socket OPEN failure. Code: aa Termname: bb Target: cc
(Vital) The daemon was unable to initiate a passive OPEN. In the message, aa is the code
returned by the macro. bb is the virtual terminal name, and cc is the target application ID.
Administrator Action: Look for other messages that may indicate abnormal conditions.
TEL963E Socket OPEN failure. Code: aa Termname: bb Target: cc
(Vital) A scheduled passive OPEN request has failed to complete normally.
TEL965E Socket SEND failure (a) Code: bb Data: cc IPaddr: dd
(Vital) A transmission error has occurred during session negotiation. A SEND operation to the
client did not complete as expected. In the text, a indicates either “A,” if the SEND macro failed
during scheduling, or “B,” if the failure occurred during an actual transmission. bb is the
decimal code returned by SEND.
The data being sent is in cc. One value being sent is:
FFFD18 — Esc+Do+Termtype

25.8
TEL966E Socket RECEIVE failure (a) Code: bb After: cc IPaddr: dd
(Vital) A transmission error has occurred during session negotiation. A RECEIVE operation
did not complete as expected. In the text, a indicates either “A,” if the RECEIVE macro failed
during scheduling, or “B,” if the failure occurred during actual transmission. bb is the decimal
code returned by RECEIVE.
cc is the request or response data last sent to the client by the daemon. Some values being sent
are:
FFFD18 — Esc+DO+TERMTYPE
FFFA1801FFF0 — Esc+SB+TERMTYPE+SEND+Esc+SE
FFFD19FFFB19 — Esc+DO+EOR+Esc+WILL+EOR
FFFD00FFFB00 — Esc+DO+BINARY+Esc+WILL+BINARY
FFFD18 — Esc+DO+TERMTYPE
TEL967E Negotiation error. Expected: aa Received: bb IPaddr: cc
(Vital) An error has occurred during session negotiation. In the message, aa is the value that
was expected, and bb is the value that was sent by the client. cc is the IP address of the client.
TEL968E Terminal type not supported: aa IPaddr: bb
(Info) During session negotiation, an unsupported terminal emulation was requested.
bb is the IP address of the client.
TEL969E VTAM Macro failed: macro Code: rc IPaddr: ipaddr
(Important) The Telnet daemon received a failure code from the indicated VTAM macro
instruction. The returned code, rc, is shown in decimal.
System Action: The Telnet session, if any, is terminated, and the daemon will reset (if
possible) or shut down.
Operator Action: Consult the IBM VTAM Programmer’s Reference for the meaning of the
return code.

25.9
TEL970E VTAM Operation failed: macro RTN: rtn FBK2: fbk R15: ret R0: reas IPaddr:
ipaddr
(Important) The indicated VTAM operation has completed, but with an error. The RPLRTNCD
and RRLFDB2 values are shown in hexadecimal. In addition, the R15 and R0 values returned
by the CHECK macro are also displayed in hexadecimal.
System Action: The Telnet session with ipaddr is terminated, and the daemon resets (if
possible) or terminates.
Operator Action: Consult the IBM VTAM Programmer’s Reference for the meaning of the
return code.
TEL980E Socket RECEIVE failure (a) Code: bb IPaddr: dd
(Info) A transmission error has occurred. A RECEIVE operation did not complete as expected.
In the text, a indicates either “A,” if the RECEIVE macro failed during scheduling, or “B,” if
the failure occurred during actual transmission. bb is the decimal code returned by RECEIVE.
TEL981W Daemon reset delayed, Termname: aa Target: bb IPaddr: cc
(Important) The daemon encountered a serious error while connecting to a VTAM application.
System Action: Because this condition may result in a failure loop, the daemon pauses for 60
seconds before resetting. This pause is bypassed if the daemon is using a Telnet menu. Once the
pause is complete, the daemon will reset and await the next request.
Operator Action: Examine any VTAM or CICS messages to determine what caused the error.
TEL982W VTAM session request rejected by application.
(Info) VTAM has driven the NSEXIT routine to notify the daemon that the application has
rejected a request to establish a session.
System Action: If the daemon uses a menu, the daemon resets. If no menu is specified, the
daemon shuts down.
This behavior is necessary to prevent every subsequent request for a Telnet session from
connecting with the failing daemon and being immediately terminated.
Operator Action: Determine why the session was rejected, and correct the problem before
restarting the daemon. Possible causes include:
• CICS has the terminal flagged as “out-of-service”

• Security software objects to the LUname. CICS autoinstall has reached its limit.

25.10
TEL983W VTAM session terminated application.
(Info) VTAM has driven the NSEXIT routine to notify the daemon that the application has
terminated the current session.
TEL987I Session ended by client at n.n.n.n
(Info) The remote Telnet client has closed the connection.
This is a normal event and is probably caused by the end-user closing the Telnet client software
without logging off normally.
If “during negotiation” appears, then the session ended prior to a successful exchange of session
values. This is also normal and may be caused by the client asking for inappropriate functions
(for example, non-3270 emulation), or simply because the user closed the client application.
System Action: The daemon resets.
Operator Action: If this message appears frequently, it may indicate a problem with the client
software. In this case, you may need to locate the device and deactivate it. Some relief can be
obtained by using the ACCESS command to deactivate the entire IP address.
TEL999D/I text
(Diagnostic/Info) This message displays generic information about Telnet operations.
TEL999 messages generally are displayed only when the DIAGNOSE TELNET command is in
effect.
Operator Action: The diagnostic messages (those that have a “D” suffix) may be suppressed
by using the following command:
DIAG -TELNET
Both non-diagnostic messages (those that have an “I” suffix) and diagnostic messages may be
suppressed by using the following command:
MESSAGE MSGID=TEL999,CONSOLE=no

25.11

25.12
26
TLS Series Messages
TLS900I Daemon Startup Transport Security Layer
(Info) The Transport Security Layer is starting. This task handles TLS requests.
TLS901I Session established with xxx,yyy Cipher=zzz
(Info) The Transport Security Layer daemon has successfully established a session with the
displayed IP address and port using the displayed cipher algortihm.
TLS903I Daemon Shutdown TLS
(Info) The TLS daemon is shutting down. No further TLS requests are processed.
TLS904D Sub TLS Daemon Started correctly
(Diagnose=SSL) The TLS daemon has received a request and has been assigned to a subtask.
TLS907I Active open to client successfully completed
(Info) The Transport Security Layer has successfully started.
TLS908I SSLD diagnostic:type RC=rcode RS=reason
(Vital) The SSL daemon was unable to process a request. The type of request and the reason for
the failure is contained in this message. Refer to the SSL documentation for additional
information on return code and reason code values.
Administrator Action: If this error continues, contact CSI Technical Support.

26.1
TCP-IP FOR VSE 1.5F Messages TLS Series Messages

26.2

Tcp-Ip4vse 1.5f Messages 20130301

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Tcp-Ip4vse 1.5f Messages 20130301

Uploaded by

Copyright:

Available Formats

Messages

This manual contains detailed explanations

Published March 2013. Copyright © 2013 CSI International

All Rights Reserved

RESTRICTED RIGHTS LEGEND

Use, duplication, or disclosure by the Government is subject to the

This material contains confidential and proprietary material of

Permission is hereby granted to copy and distribute this document as

• Each copy must be a complete and accurate copy.

TCP/IP FOR VSE Messages

Published by CSI International

Request support escalation by the telephone numbers or e-mail address listed

Copyright © 2013 by CSI International

After Hours (SEV1) 1. Call one of the following telephone numbers.

Toll Free in the USA: 800-795-4914

2. Tell the operator that you have a “SEV1” issue.

The answering service will follow the following chain:

b. Product Developer (if necessary)

c. Technical Support Manager (if necessary)

d. Development Manager (if necessary)

e. Chief Operating Officer (if necessary)

f. Chief Executive Officer (if necessary)

Copyright © 2013 by CSI International

Recent changes are marked with a change bar in the margin.

Published March 2013

Published March 2012

F007138 TEL927D/I Added this message to the manual 25.4

Published February 2012

F007110 FTP301D Added this message to the manual 4.7

Copyright © 2013 by CSI International

Copyright © 2013 by CSI International

CSI International Technical Support and Technical Support Escalation .................. i

1 BSD Series Messages .......................................................................................... 1.1

Copyright © 2013 by CSI International

2 CGL Series Messages .......................................................................................... 2.1

Copyright © 2013 by CSI International

3 EXE Series Messages .......................................................................................... 3.1

4 FTP Series Messages ........................................................................................... 4.1

Copyright © 2013 by CSI International

Copyright © 2013 by CSI International

Copyright © 2013 by CSI International

5 GPS Series Messages .......................................................................................... 5.1

Copyright © 2013 by CSI International

6 HTT Series Messages .......................................................................................... 6.1

Copyright © 2013 by CSI International

Copyright © 2013 by CSI International

7 IPA Series Messages ............................................................................................ 7.1

Copyright © 2013 by CSI International

8 IPC Series Messages ............................................................................................ 8.1

9 IPD Series Messages ............................................................................................ 9.1

Copyright © 2013 by CSI International

10 IPF Series Messages .......................................................................................... 10.1

Copyright © 2013 by CSI International

Copyright © 2013 by CSI International

Copyright © 2013 by CSI International

11 IPI Series Messages ........................................................................................... 11.1

Copyright © 2013 by CSI International

12 IPL Series Messages .......................................................................................... 12.1

Copyright © 2013 by CSI International

Copyright © 2013 by CSI International

13 IPN Series Messages .......................................................................................... 13.1

Copyright © 2013 by CSI International

Copyright © 2013 by CSI International