TXSeries For Multiplatforms Messages and Codes Version 6.2

TXSeries for Multiplatforms
Messages and Codes

Version 6.2
SC34-6639-02
Messages and Codes

Version 6.2
SC34-6639-02
Note
Before using this information and the product it supports, be sure to read the general information under Notices on page
925.
Third Edition (January 2008)

Order publications through your IBM representative or through the IBM branch office serving your locality.
Copyright International Business Machines Corporation 2001, 2008. All rights reserved.
US Government Users Restricted Rights Use, duplication or disclosure restricted by GSA ADP Schedule Contract
with IBM Corp.
Contents
About this book . . . . .
Who should read this book .
Document organization . . .
Related information . . . .
Conventions used in this book
How to send your comments .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
xiii
xiii
xiii
xiii
xiii
xv
Chapter 1. ERZxxx messages . . . . . . . . . . . . . . . . . . . 1

Chapter 2. BHG... . . . . . . . . . . . . . . . . . . . . . . . 501
Chapter 3. Abnormal Termination Codes
ABMB . . . . . . . . . . . . . .
ABMI . . . . . . . . . . . . . .
ABMM . . . . . . . . . . . . .
ABMO . . . . . . . . . . . . .
ABM0 . . . . . . . . . . . . . .
ABM3 . . . . . . . . . . . . . .
ACS1 . . . . . . . . . . . . . .
ADPL . . . . . . . . . . . . . .
AEIA to AEY3 . . . . . . . . . . .
AEY7 . . . . . . . . . . . . . .
AEY9 . . . . . . . . . . . . . .
AICA . . . . . . . . . . . . . .
AIS9 . . . . . . . . . . . . . .
AKCS . . . . . . . . . . . . . .
AKCT . . . . . . . . . . . . . .
APCN . . . . . . . . . . . . . .
APCT . . . . . . . . . . . . . .
ASRA . . . . . . . . . . . . . .
ASRB . . . . . . . . . . . . . .
ATCV . . . . . . . . . . . . . .
ATDD . . . . . . . . . . . . . .
ATNI . . . . . . . . . . . . . .
AZI4 . . . . . . . . . . . . . .
AZI6 . . . . . . . . . . . . . .
A011: . . . . . . . . . . . . . .
A012: . . . . . . . . . . . . .
A013: . . . . . . . . . . . . .
A014: . . . . . . . . . . . . .
A015: . . . . . . . . . . . . .
A031: . . . . . . . . . . . . .
A032: . . . . . . . . . . . . .
A033: . . . . . . . . . . . . .
A07A: . . . . . . . . . . . . .
A07B: . . . . . . . . . . . . .
A07C: . . . . . . . . . . . . .
A101: . . . . . . . . . . . . . .
A10A: . . . . . . . . . . . . .
A10C: . . . . . . . . . . . . .
A10D: . . . . . . . . . . . . .
A10E: . . . . . . . . . . . . .
A11A: . . . . . . . . . . . . .
Copyright IBM Corp. 2001, 2008
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
599
599
599
599
600
600
600
600
601
601
602
603
603
603
604
604
605
605
605
606
606
606
607
607
608
608
608
609
609
609
609
610
610
610
611
611
611
612
612
612
613
613
iii
A11B:
A11D:
A11F:
A11M:
A11N:
A11P:
A11T: .
A11U:
A11W:
A121:
A122:
A124:
A125:
A141:
A142:
A143:
A144:
A145:
A146:
A147:
A148:
A149:
A150:
A151:
A152:
A153:
A154:
A155:
A156:
A158:
A159:
A15A:
A15F:
A15Z:
A161:
A162:
A163:
A164:
A165:
A166:
A16E:
A16H:
A16Z:
A171:
A175:
A177:
A178:
A179:
A17A:
A17G:
A17H:
A17I: .
A17J: .
A17K:
A17L:
A17M:
iv
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
TXSeries for Multiplatforms: Messages and Codes
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
613
613
614
614
614
615
615
615
616
616
616
616
617
617
617
618
618
618
619
619
619
620
620
620
621
621
621
622
622
623
623
623
624
624
624
625
625
625
626
626
626
626
627
627
627
628
628
629
629
630
630
630
631
631
631
632
A17N:
A17O:
A17P:
A17Q:
A17R:
A17S:
A17T: .
A17U:
A194:
A195:
A19D:
A19E:
A21M:
A21R:
A21S:
A221:
A222:
A223:
A226:
A227:
A228:
A229:
A22A:
A22B:
A23A:
A23E:
A23F:
A23G:
A23L:
A23S:
A23T: .
A241:
A242:
A243:
A245:
A248:
A24F:
A24M:
A24S:
A25A:
A25E:
A25F:
A25L:
A25M:
A261:
A262:
A263:
A264:
A265:
A266:
A27A:
A27B:
A27C:
A27D:
A27E:
A27F:
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
Contents
632
632
633
633
633
634
634
634
635
635
635
636
636
636
637
637
637
638
638
638
639
639
639
639
640
640
640
641
641
641
642
642
642
642
643
643
643
643
644
644
644
645
645
645
646
646
646
646
647
647
647
648
648
648
649
649
A27G:
A27K:
A27L:
A28A:
A28B:
A28C:
A28D:
A28E:
A28F:
A28G:
A28H:
A28I: .
A28J: .
A28K:
A28M:
A28N:
A28O:
A30A:
A30B:
A30C:
A30D:
A30E:
A30F:
A30G:
A31A:
A31B:
A32A:
A32B:
A32C:
A32D:
A32E:
A32F:
A32G:
A32H:
A32J: .
A32K:
A32L:
A32M:
A331:
A341:
A342:
A371:
A372:
A373:
A374:
A375:
A376:
A377:
A378:
A379:
A37A:
A37B:
A37C:
A37D:
A41A:
A42A:
vi
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
649
650
650
650
651
651
651
652
652
652
653
653
653
654
654
654
654
655
655
656
656
656
657
657
657
658
658
658
658
659
659
659
660
660
660
661
661
661
662
662
662
663
663
663
664
664
664
665
665
665
666
666
666
667
667
667
A42B:
A42C:
A42D:
A42E:
A42F:
A42G:
A42H:
A42I: .
A42J: .
A42K:
A43A:
A43B:
A43C:
A43D:
A43E:
A451:
A452:
A453:
A460:
A461:
A462:
A463:
A464:
A465:
A466:
A467:
A468:
A469:
A46A:
A46B:
A46C:
A46D:
A46E:
A46F:
A47A:
A47B:
A47C:
A47D:
A48A:
A48B:
A48C:
A49B:
A50B:
A50C:
A53A:
A561:
A57A:
A583:
A61A:
A62C:
A62F:
A62G:
A62H:
A62J: .
A64A:
A64B:
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
668
668
668
669
669
669
670
670
671
671
671
672
672
672
672
673
673
673
674
674
674
674
675
675
675
675
676
676
676
677
677
677
678
678
678
679
679
679
680
680
680
681
681
681
682
682
682
683
683
683
684
684
684
684
685
685
Contents
vii
A64C:
A64D:
A64E:
A661:
A691:
A701:
A711: .
A731:
A741:
A751:
A752:
A761:
A771:
A82C:
A82E:
A82L:
A82M:
AA41:
AA42:
AA43:
AA44:
AA45:
AA46:
AA47:
AA48:
AA49:
AA4A:
AA4B:
AA4C:
AA4D:
AA4E:
AB31:
AB40:
AB41:
AB42:
AB43:
AB44:
AB45:
AB52:
AB53:
AB54:
AB55:
AB56:
AB57:
AB58:
AB61:
ACS1:
U0101:
U0701:
U0702:
U0703:
U0704:
U0705:
U0706:
U0707:
U0708:
viii
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
685
686
686
686
687
687
687
687
688
688
688
689
689
689
689
690
690
690
691
691
691
692
692
692
693
693
693
694
694
694
695
695
695
695
696
696
696
696
697
697
697
697
698
698
698
698
699
699
699
700
700
700
700
701
701
701
U0709:
U0710:
U0711:
U0712:
U0713:
U0714:
U1001:
U1002:
U1003:
U1004:
U1005:
U1006:
U1007:
U1008:
U1009:
U1010:
U1011:
U1012:
U1013:
U1014:
U1015:
U1016:
U1017:
U1018:
U1019:
U1020:
U1021:
U1022:
U1024:
U1025:
U1027:
U1028:
U1029:
U1030:
U1031:
U1032:
U1033:
U1034:
U1035:
U1036:
U1037:
U1038:
U1039:
U1101:
U1401:
U1403:
U1404:
U1501:
U1507:
U1512:
U1513:
U1514:
U1516:
U1517:
U1518:
U1701:
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
702
702
702
703
703
703
704
704
704
704
705
705
705
705
706
706
706
707
707
707
707
708
708
708
708
709
709
709
710
710
710
710
711
711
711
711
712
712
712
713
713
713
714
714
714
715
715
715
716
716
716
717
717
717
718
718
Contents
ix
U2203:
U2224:
U2231:
U2238:
U2239:
U2242:
U2243:
U2251:
U2264:
U2265:
U2269:
U2270:
U2274:
U2287:
U2288:
U2289:
U2312:
U2313:
U2314:
U2315:
U2319:
U2329:
U2334:
U2342:
U2348:
U2353:
U2354:
U2356:
U2358:
U2362:
U2372:
U2404:
U2406:
U2407:
U2409:
U2411:
U2413:
U2416:
U2419:
U2425:
U2430:
U2450:
U2451:
U2454:
U2455:
U2456:
U2457:
U2460:
U2463:
U2467:
U2470:
U2475:
U2497:
U2498:
U2499:
U2501:
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
718
718
719
719
719
719
720
720
720
720
721
721
721
721
722
722
722
723
723
723
723
724
724
724
724
725
725
725
726
726
726
726
727
727
727
728
728
728
729
729
729
729
730
730
730
731
731
731
732
732
732
733
733
733
733
734
U3901:
U4419:
U4511:
U4512:
U4536:
U4540:
U4541:
U4542:
U4801:
U4802:
U4803:
U4911:
U4916:
U5001:
U5104:
U5201:
U5310:
U5655:
U5701:
U5702:
U5733:
U5801:
U5802:
U5804:
U5805:
U5806:
U5807:
U5808:
U5810:
U5811:
U58400:
U58401:
U6201:
U6301:
U8005:
U8008:
U8022:
U8023:
U8025:
U8030:
U8032:
U8033:
U8034:
U8035:
U8036:
U8038:
U8039:
U8041:
U8045:
U8046:
U8047:
U8048:
U8049:
U8087:
UA401:
UB401:
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
734
734
734
735
735
735
736
736
736
736
737
737
737
738
738
738
739
739
739
739
740
740
740
740
741
741
741
742
742
742
743
743
743
743
744
744
744
744
745
745
745
745
746
746
746
746
747
747
747
747
748
748
748
748
749
749
Contents
xi
UB402:
UB404:
UB406:
UB407:
UB408:
UB519:
UB520:
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
Chapter 4. CICS Toolkit message and codes . . . . . . . . . . .

CICS Toolkit messages . . . . . . . . . . . . . . . . . . . .
0x502c5017: Collating Language %s Is different Than One Already
Installed %s... . . . . . . . . . . . . . . . . . . . . .
0x5c102017: tmxa_SetRMIAutoClose is obsolete -- use
tmxa_SetRMIOptions instead. . . . . . . . . . . . . . . . .
0x5c1c1457: Applid %d byte%s too long: recovery compromised . . . .
0x5c1c1837: %s to XID conversion failed: %k . . . . . . . . . . .
0x5c2c0c17: Aborting %s . . . . . . . . . . . . . . . . . .
0x5c301017: Recording heuristic damage for %s . . . . . . . . . .
0x5c380c17: Rollback assumed for %s . . . . . . . . . . . . .
0x5c381017: Rollback assumed for %s . . . . . . . . . . . . .
0x5c3c0c17: Heuristic outcome performed on %s. . . . . . . . . .
0x5c3c0c27: Recovery of %z may be compromised. . . . . . . . .
0x5c3c1c17: Terminating recovery scan for RM %d. . . . . . . . . .
0x5c401417: Recording heuristic damage for %s . . . . . . . . . .
0x5c541017: Truncating transaction identifier when constructing XID -recovery compromised. . . . . . . . . . . . . . . . . . .
0x5c541027: Truncating application identifier when constructing XID -recovery compromised. . . . . . . . . . . . . . . . . . .
0x64048c67: PPC Service Not Initialized . . . . . . . . . . . . .
0x640c6417: unknown/unexpected transaction state %d returned by
tran-service for tid: %#x . . . . . . . . . . . . . . . . . .
0x640c7017: Inserting Conversation with a NULL Attributes Structure . .
0x640c8017: duplicate sna conv found. . . . . . . . . . . . . .
0x64e41c17: new exec LU (%s) listed through old admin interface: %u
0x64e42017: . . . . . . . . . . . . . . . . . . . . . . .
0x64e45017: . . . . . . . . . . . . . . . . . . . . . . .
0x64e46c27: trdce_BindingImport FAILED (%k) . . . . . . . . . .
0x64e49027: New RPC failed (%k). Trying old RPC... . . . . . . . .
0x64e49037: failed to chmod file %s, errno: %d . . . . . . . . . .
0x64e49427: . . . . . . . . . . . . . . . . . . . . . . .
0x64e49437: Invalid remoteluProfilePriority (%lu). Exported profile will have
default priority value. . . . . . . . . . . . . . . . . . . .
0x64e49817: . . . . . . . . . . . . . . . . . . . . . . .
0x64e49c17: . . . . . . . . . . . . . . . . . . . . . . .
0x68044487: Illegal sync level: %i . . . . . . . . . . . . . . .
0x68044497: Illegal security level: %i . . . . . . . . . . . . . .
0x680448b7: . . . . . . . . . . . . . . . . . . . . . . .
0x680448c7: . . . . . . . . . . . . . . . . . . . . . . .
0x6804f8c7: Unable to initialize ppc services . . . . . . . . . . .
Status codes . . . . . . . . . . . . . . . . . . . . . . . .
Abort codes . . . . . . . . . . . . . . . . . . . . . . . .
Chapter 5. SARPC messages
.
.
.
.
.
.
.
749
749
750
750
750
750
751
. 753
. 753
. 809
.
.
.
.
.
.
.
.
.
.
.
809
809
810
810
810
811
811
812
812
812
813
. 813
. 813
. 814
. 814
. 814
. 815
815
. 815
. 816
. 816
. 816
. 816
. 817
.
.
.
.
.
.
.
.
.
.
817
817
817
817
818
818
818
818
819
900
. . . . . . . . . . . . . . . . . . 909
Notices . . . . . . . . . . . . . . . . . . . . . . . . . . . 925
Trademarks and service marks . . . . . . . . . . . . . . . . . . 926
xii
About this book

This book lists CICS messages and codes. The information can be used to
determine the cause of CICS problems. For more information, see the TXSeries for
Multiplatforms Problem Determination Guide.
Who should read this book

This book is for system administrators, terminal users, system programmers and
anybody else who needs to understand and respond to CICS messages and codes.
To use this book, you need to have a general understanding of CICS. You also
need more detailed knowledge about the part of CICS to which the message
pertains.
Document organization
This document has the following organization:
v CICS messages describes messages issued by CICS.
v CICS codes describes CICS abend codes.
The printed version of this book is available as two separate volumes. In online
formats (HTML and PDF), this book is provided as a single volume.
Related information
For further information on the topics discussed in this manual, see the following
documents:
v TXSeries for Multiplatforms Administration Guide
v TXSeries for Multiplatforms Administration Reference
v TXSeries for Multiplatforms Problem Determination Guide
Conventions used in this book

TXSeries for Multiplatforms documentation uses the following typographical and
keying conventions.
Table 1. Conventions that are used in this book
Convention
Meaning
Bold
Indicates values that you must use literally, such as commands,

functions, and resource definition attributes and their values. When
referring to graphical user interfaces (GUIs), bold also indicates
menus, menu items, labels, buttons, icons, and folders.
Monospace
Indicates text that you must enter at a command prompt. Monospace

also indicates screen text and code examples.
Italics
Indicates variable values that you must provide (for example, you
supply the name of a file for file_name). Italics also indicates
emphasis and the titles of books.
<>
Encloses the names of keys on the keyboard.
<Ctrl-x>
Where x is the name of a key, indicates a control-character

sequence. For example, <Ctrl-c> means hold down the Ctrl key
while you press the c key.
xiii
Table 1. Conventions that are used in this book (continued)
xiv
Convention
Meaning
<Return>
Refers to the key labeled with the word Return, the word Enter, or
the left arrow.
Represents the UNIX command-shell prompt for a command that

does not require root privileges.
Represents the UNIX command-shell prompt for a command that

requires root privileges.
C:\>
Represents the Windows command prompt.
>
When used to describe a menu, shows a series of menu selections.

For example, Select File > New means From the File menu,
select the New command.
Entering commands
When instructed to enter or issue a command, type the command

and then press <Return>. For example, the instruction Enter the ls
command means type ls at a command prompt and then press
<Return>.
[]
Encloses optional items in syntax descriptions.
{}
Encloses lists from which you must choose an item in syntax

descriptions.
Separates items in a list of choices enclosed in { } (braces) in syntax

descriptions.
...
Ellipses in syntax descriptions indicate that you can repeat the

preceding item one or more times. Ellipses in examples indicate that
information was omitted from the example for the sake of brevity.
IN
In function descriptions, indicates parameters whose values are used

to pass data to the function. These parameters are not used to
return modified data to the calling routine. (Do not include the IN
declaration in your code.)
OUT
In function descriptions, indicates parameters whose values are used

to return modified data to the calling routine. These parameters are
not used to pass data to the function. (Do not include the OUT
declaration in your code.)
INOUT
In function descriptions, indicates parameters whose values are

passed to the function, modified by the function, and returned to the
calling routine. These parameters serve as both IN and OUT
parameters. (Do not include the INOUT declaration in your code.)
$CICS
Indicates the full path name of the location in which the CICS
product is installed; for example, /usr/lpp/cics on AIX. If the CICS
environment variable is set to the product path name, you can use
the examples exactly as shown in this book; otherwise, you must
replace all instances of $CICS with the CICS product path name.
CICS on Open
Systems
Refers collectively to the CICS product for all supported UNIX

platforms.
TXSeries for
Multiplatforms
Refers collectively to the CICS for AIX, CICS for HP-UX, CICS for
Solaris, and CICS for Windows products.
CICS
Refers generically to the CICS for AIX, CICS for HP-UX, CICS for
Solaris, and CICS for Windows products. Other CICS products in the
CICS Family are distinguished by their operating system (for
example, IBM mainframe-based CICS for the z/OS platform).
How to send your comments

Your feedback is important in helping to provide the most accurate and highest
quality information. If you have any comments about this book or any other
TXSeries for Multiplatforms documentation, send your comments by e-mail to
idrcf@hursley.ibm.com. Be sure to include the name of the book, the document
number of the book, the version of TXSeries for Multiplatforms, and, if applicable,
the specific location of the information you are commenting on (for example, a page
number or table number).
About this book
xv
xvi
Chapter 1. ERZxxx messages

ERZ001001E Exception raised in CICS application
server code
Explanation:
An unexpected exception was caught in the CICS
application server code, during the execution of a
transaction program.
System action:
CICS abnormally terminates the transaction. The
application server continues, and is available to run
further transactions.
User response:
If the problem persists, there is no alternative but to call
your support organization.
Destination:
console.msg
ERZ002001E Usage: cicscvt fileName
Explanation:
You entered the cicscvt command incorrectly.
System action:
The cicscvt command terminates.
Destination:
CSMT
ERZ001002E
Look in console.msg and find the COBOL run time

system error number and error message (which
immediately precede this message). For further
information about the error, look up the error number in
the COBOL Error Messages manual. Correct the error
in your COBOL transaction program before attempting
to run the program again.
Abnormal termination U0101. CICS

was unable to attach shared memory.
Explanation:
CICS was unable to attach the Region Pool shared
memory. This can occur on UNIX if the access
permissions to the CICS shared memory segments
have been altered or if the data segment shared
memory identifier has been overwritten.
System action:
CICS abnormally terminates the region.
User response:
Enter the cicscvt command using the correct syntax, as
shown in the message.
Destination:
stderr
ERZ002002E Unable to initialize a parser
environment
Explanation:
The cicscvt command was attempting to obtain memory
for the parser. Insufficient memory was available.
User response:
On UNIX ask the system administrator to check for
inconsistencies in the CICS shared memory segments
using the ipcs command; these segments must have
read and write permissions for the user cics who must
be a member of the user group cics. If the problem
cannot be identified, call your support organization.
System action:
The cicscvt command terminates with exit code 1 and
does not produce any converted template files.
Destination:
console.msg
Destination:
stderr
ERZ001003E An error in a COBOL transaction

program caused the COBOL run time
system to generate the previous error
message
ERZ002003E Unsuccessful open of input file

fileName. errorMessage
Explanation:
CICS has detected that an error in a COBOL
transaction program caused a COBOL run time system
error to occur during the execution of the program. The
COBOL run time system has already written an error
message to console.msg.
System action:
CICS abnormally terminates the transaction.
User response:
User response:
Try again when the system is less busy and has more
memory available.
Explanation:
The file you requested cicscvt to process was unable to
be opened for the reason given by the operating system
as errorMessage.
System action:
User response:
Check that the fileName given is a valid readable file.
For further information consult the operating system
documentation for the fopen() function. Once the
fileName is corrected, retry the cicscvt command.
ERZ002004E ERZ002020E
Destination:
stderr
ERZ002004E Unsuccessful memory allocation to
create conversion template
Explanation:
The cicscvt command cannot allocate any more
memory from the operating system for the conversion
templates.
System action:
User response:
Try again when the system is less busy and has more
memory available.
Destination:
stderr
ERZ002005E Cannot register exception handler
Explanation:
The cicscvt command needs to run with an exception
handler, but a signal call to attach it gave an
unexpected response. This indicates an internal error.
System action:
User response:
Contact your support organization.
Destination:
stderr
ERZ002010E Unsuccessful open of output file
Explanation:
The cicscvt command was unable to open the output
file, errorMessage, for the reason given by the operating
system as errorMessage.
System action:
User response:
Check that the output file fileName does not exist and
that the current working directory has write permissions.
For further information consult the operating system
documentation for the fopen() function.
Destination:
stderr
ERZ002011I DFHCNV macro translation ended.

errorCountd errors, warningCountd
warnings.
Explanation:
The cicscvt command detected the stated number of
errors and warnings during map translation.
System action:
If an error or warning was detected during translation,
the cicscvt command terminates with exit code 1;
otherwise, it terminates with exit code 0.
User response:
None
Destination:
stderr
ERZ002015E Unsuccessful write to output file
Explanation:
The cicscvt command was unable to write to the output
file, errorMessage, for the reason given by the operating
system as errorMessage.
System action:
possibly produces partially converted template files.
User response:
Check that there is enough space on the disk for the
files produced and retry. For further information consult
the operating system documentation for the function
fprintf().
Destination:
stderr
ERZ002020E lineNumber: The ICTL directive is
invalid. A comma-separated list for the
start, continuation and end column
numbers is required.
Explanation:
The ICTL directive requires a comma-separated list of
1, 2, or 3 numbers to set the start, continuation, and
end columns for the input source file to cicscvt program.
System action:
The line containing the ICTL directive is ignored by
cicscvt, and the cicscvt command continues to process
the rest of the input file. The cicscvt command
terminates with exit code 1.
User response:
Edit the input file to correct the ICTL directive at the
given lineNumber, and retry the cicscvt command.
Destination:
stderr
ERZ002021E ERZ002026E
ERZ002021E lineNumber: Invalid character
character in continuation line
ERZ002024W lineNumber: No DFHCNV macro

found. The line will be ignored.
Explanation:
The continuation line contained within the file you
specified to cicscvt did not contain spaces between the
start column and continuation columns (defaults 1 and
16 respectively).
Explanation:
You have entered a record in your file that does not
have a DFHCNV macro. Each record must contain a
DFHCNV macro, optionally preceded by a label.
System action:
The cicscvt command ignores the line at lineNumber
and processes the rest of the file. The cicscvt command
User response:
Correct the continuation line that is specified at line
lineNumber of your input file, and retry the cicscvt
command.
Destination:
stderr
character in label
Explanation:
The file you requested cicscvt to process contained an
invalid label at line lineNumber. A label must begin with
a letter and only contain letters and digits.
System action:
The cicscvt command ignores the label and continues to
process the rest of the input file. The cicscvt command
User response:
Edit the input file to change the label specified at line
lineNumber such that it only contains letters and
numbers and that the first character is a letter, and retry
the translation.
Destination:
stderr
ERZ002023W lineNumber: Label label is too long.
Label truncated to truncatedLabel.
Explanation:
You have a DFHCNV macro label within your input file
at line lineNumber that has more than 63 characters.
System action:
The cicscvt command truncates the label and continues
to process the rest of the input file. The cicscvt
command terminates with exit code 1.
User response:
Edit the input file to shorten the label at the
lineNumberpecified, and retry the cicscvt command.
Destination:
stderr
System action:
The cicscvt command ignores the line and continues to
User response:
Edit the input file either to remove the record or to add
a valid macro, and retry the cicscvt command.
Destination:
stderr
ERZ002025W
lineNumber: Unknown word

macroType in place of a macro name
Explanation:
The cicscvt command does not recognize the word that
appears in the operation field (that is, as the first
non-blanks after any label) on the given line of your
input file. The only valid contents of that position are:
ICTL, TITLE, the macro name DFHCNV, and END.
System action:
The cicscvt command ignores the line containing the
unknown operation and continues to process the rest of
the input file. The cicscvt command terminates with exit
code 1.
User response:
Edit the input file either to remove or to correct the
invalid line, and retry the cicscvt command. Refer to the
TXSeries for Multiplatforms Intercommunication Guide
for more detail.
Destination:
stderr
character in DFHCNV macro
Explanation:
The input file you requested cicscvt to process contains
an invalid character on line lineNumber. The only valid
characters outside strings are letters, digits, =, ,, (, and
).
System action:
User response:
Edit the input file to correct the invalid character, and
retry the cicscvt command.
Destination:
stderr
ERZ002027E ERZ002041W
ERZ002027E lineNumber: No closing quote in string
ERZ002030W Conversion template file is empty
Explanation:
The closing quote for a string must occur before the end
of the record. lineNumber is the number of the line that
lacks a closing quote.
Explanation:
The input file you requested cicscvt to process did not
contain anything.
System action:
User response:
Edit the input file to add a closing quote to the string,
and retry the cicscvt command.
User response:
Run the cicscvt command again, using a valid input file.
Destination:
stderr
ERZ002039W lineNumber: DFHCNV TYPE=FINAL
macro is missing
Destination:
stderr
ERZ002028W
System action:
The cicscvt command terminates normally.
lineNumber: Invalid single & in string
Explanation:
You must use && in your input file to get a single & in a
string.
System action:
User response:
Edit the input file to correct the single & in the string,
and retry the cicscvt command.
Destination:
stderr
ERZ002029E lineNumber: DFHCNV macro options
optionName1 and optionName2
conflict
Explanation:
The input file you requested cicscvt to process contains
options to a DFHCNV macro that are mutually
exclusive.
System action:
User response:
Edit the input file to remove one of the conflicting
DFHCNV macro options, and retry the cicscvt
command. Refer to the TXSeries for Multiplatforms
Intercommunication Guide for more detail.
Destination:
stderr
Explanation:
The cicscvt command expected to find a DFHCNV
TYPE=FINAL statement on the given line, but was
unable to find one. Every file that needs to be translated
by cicscvt must have a DFHCNV TYPE=FINAL as the
last line in the file.
System action:
The cicscvt command processes the files requested and
User response:
Edit the input file to add a DFHCNV TYPE=FINAL
statement, and retry the cicscvt command.
Destination:
stderr
ERZ002040W lineNumber: Duplicate option
optionName. The last options
argument specified is used.
Explanation:
The specified option has been specified more than once
for this DFHCNV macro. The last options argument
specified is used. All other values are ignored.
System action:
The cicscvt command ignores the first occurrences of
the DFHCNV macros duplicated options and continues
to process the rest of the input file.
User response:
Edit the input file to remove the duplicate options in the
DFHCNV macro statement and retry the command.
Destination:
stderr
ERZ002041W lineNumber: Option optionName is
invalid for DFHCNV macro type
macroType
Explanation:
The cicscvt command has encountered an option that is
not valid for the DFHCNV macro statement of the
specified type.
ERZ002042W ERZ002046E
System action:
The cicscvt command ignores the option for the
DFHCNV macro statement and continues to process the
rest of the input file.
User response:
Edit the input file to check that there are no long words
and that quoted string are terminated correctly. Then
retry the command.
User response:
Edit the input file to remove the invalid option and retry
the command.
Destination:
stderr
Destination:
stderr
ERZ002045E CICS has detected a signature

inconsistency in the conversion
template resourceName being
released. Expected signature
expectedSignature.
ERZ002042W lineNumber: The CDEPAGE option in

DFHCNV TYPE=ENTRY statement is
ignored
Explanation:
The cicscvt command does not support the CDEPAGE
option for DFHCNV TYPE=ENTRY macro statement. To
specify the client and server code pages, use the
options CLINTCP and SRVERCP respectively.
System action:
The cicscvt command ignores the DFHCNV macro
statement and continues to process the rest of the input
file.
User response:
Edit the input file to remove the CDEPAGE option and
replace it with CLINTCP and SRVERCP options, if
required, and retry the command.
Destination:
stderr
ERZ002043E lineNumber: The DFHCNV macro
statement contains invalid DATA
Explanation:
The cicscvt command has encountered invalid data for
the DATA option for DFHCNV TYPE=SELECT macro.
Explanation:
CICS detected a signature inconsistency in the
conversion template for resource, resourceName, and
was unable to release the template from the Task
Shared Pool. This is likely to be caused by a users
application program that has corrupted the Task Shared
Pool, in which case a symptom record is written to the
symrecs file.
System action:
None
User response:
Observe any messages that precede this message and
consider restarting the region as soon as possible to
clear up any Task Shared Pool memory problems. If the
symptoms still persist, contact your support
organization.
Destination:
stderr
ERZ002046E Unsuccessful attempt to release
conversion template for resource
resourceName of class className
from memory
User response:
Edit the input file to correct the argument to the DATA
option and retry the command.
Explanation:
CICS was unable to release the conversion template for
resource, resourceName, of class, className, from
the Task Shared pool. This is likely to be caused by a
users application program that has corrupted the Task
Shared Pool, in which case a symptom record is written
to the symrecs file.
Destination:
stderr
System action:
None
System action:
option and continues to process the rest of the input file.
ERZ002044E lineNumber: The length of a token

string in the DFHCNV macro statement
is too long
Explanation:
The cicscvt command encountered a token or string that
was too long. Usually this is caused by a missing
delimiter such as a closing quote in a quoted string.
User response:
organization.
Destination:
CSMT
System action:
The cicscvt command terminates.
ERZ002047E ERZ002056E
inconsistency in the conversion
template resourceName being
accessed. Expected signature
expectedSignature.
Explanation:
CICS detected an inconsistency in the conversion
template data contained in the Task Shared Pool. This
is likely to be caused by a users application program
that has corrupted the Task Shared Pool, in which case
a symptom record is written to the symrecs file.
System action:
None
User response:
organization.
stderr
ERZ002054E lineNumber: The DFHCNV macro does
not contain the mandatory option
optionName
Explanation:
The file you requested cicscvt to process did not have
the required optionName specified in the DFHCNV
macro on line lineNumber. This option must be
specified for the DFHCNV macro at line lineNumber.
System action:
The cicscvt command ignores the statement line and
continues to process the rest of the file. This can
possibly lead to many error messages being produced,
especially if the ignored statement contains the
DFHCNV macro TYPE=ENTRY/SELECT.
User response:
Edit the input file to add the missing option to the
DFHCNV macro, and retry the command.
Destination:
CSMT
Destination:
stderr
ERZ002051E lineNumber: Missing typeintro

introducer in DFHCNV macro
ERZ002055E lineNumber: Invalid DFHCNV macro

option optionName was specified
Explanation:
The file you requested cicscvt to process did not have
the keyword typeintro introducer specified in the
DFHCNV macro on line lineNumber. Each DFHCNV
macro must have the typeintro introducer specified.
Explanation:
The file you requested cicscvt to process had an invalid
optionName specified at line lineNumber.
System action:
The cicscvt command ignores the statement and
continues to process the rest of the file. The cicscvt
command terminates with exit code 1.
User response:
Edit the input file to add the typeintro introducer to the
Destination:
stderr
ERZ002053W lineNumber: DFHCNV macro option
optionName is ignored
Explanation:
A DFHCNV macro option encountered by cicscvt was
ignored because one or more other options override the
ignored option.
System action:
The cicscvt command ignores the option and associated
parameter, and continues to process the rest of the
input file.
User response:
Edit the input file to remove the redundant option and
retry the command.
Destination:
System action:
The cicscvt command ignores the invalid operand and
continues to process the rest of the input file.
User response:
Edit the input file to remove or correct the invalid option
and retry the command.
Destination:
stderr
ERZ002056E lineNumber: DFHCNV macro option
optionName has invalid hexadecimal
data
Explanation:
The DFHCNV macro option optionName contains
incorrect hexadecimal data on line lineNumber. There is
possibly an odd number of hexadecimal digits or a digit
that is not within the hexadecimal range.
System action:
The cicscvt command ignores the statement and
continues to process the rest of the file.
User response:
Edit the input file to correct the hexadecimal data
associated with the optionName and retry the
command.
Destination:
stderr
ERZ002058E ERZ002068E
ERZ002058E lineNumber: Resource definition
resourceName already defined
Explanation:
The resource definition resourceName for DFHCNV
TYPE=ENTRY macro has already been specified in the
input file.
System action:
The cicscvt command ignores the option and its
arguments, and continues to process the rest of the file.
User response:
Edit the input file to change the resource name so that
is unique, and retry the command.
Destination:
stderr
ERZ002064W lineNumber: The DFHCNV macro
specifies DATATYP=USERDATA but
USREXIT has previously been set to
NO
Explanation:
To be able to use the user-replaceable conversion
DFHUCNV module, as implied by DFHCNV
DATATYP=USERDATA, you must supply a USREXIT
option value of YES.
System action:
The cicscvt command ignores the option
DATATYP=USERDATA and continues to process the
rest of the input file. At run-time, the user-exit is not
called to convert the user data.
User response:
If the user-exit is to be invoked at run-time, edit the
input file to change the USREXIT option for the current
resource name to YES.
Destination:
stderr
ERZ002065E lineNumber: Invalid value optionValue
for option optionName in DFHCNV
macro
Explanation:
The file you requested cicscvt to process had a
DFHCNV macro option that had an invalid value at line
lineNumber.
System action:
The cicscvt command ignores the invalid option and
User response:
Edit the input file to change the value of the option
specified and retry the command. Consult the TXSeries
for Multiplatforms Intercommunication Guide and its
following sections for values expected for the option.
Destination:
stderr
ERZ002066E lineNumber: Invalid argument

argumentValue for option optionName
in DFHCNV macro
Explanation:
The file you requested cicscvt to process had a
DFHCNV macro option that had an invalid argument at
line lineNumber.
System action:
The cicscvt command ignores the invalid option and
User response:
Edit the input file to change the argument to the option
specified, then retry the command. Consult the
for arguments expected for the option specified.
Destination:
stderr
ERZ002067E lineNumber: Unexpected DFHCNV
TYPE=KEY macro. This macro is only
valid for resource type FC.
Explanation:
The DFHCNV TYPE=KEY macro can only be defined in
the input file for the resource type FC. The macro
cannot be used in definitions whose resource type is
TS, TD, IC or PC.
System action:
file.
User response:
Edit the input file to remove the DFHCNV TYPE=KEY
macro statement, or change the resource type of the
current resource type to FC, and retry the command.
Destination:
stderr
macro statement. The first DFHCNV
macro should be TYPE=INITIAL.
Explanation:
The DFHCNV TYPE=INITIAL macro must be the first
DFHCNV macro statement in the source file to establish
the beginning of the conversion table.
System action:
file.
User response:
Edit the input file to add the DFHCNV TYPE=INITIAL
macro statement as the first DFHCNV macro statement
in the file, and retry the command.
Destination:
ERZ002069E ERZ002073E
stderr
macro statement encountered.
Expected to have TYPE=ENTRY
specified.
Explanation:
The input file did not have a DFHCNV TYPE=ENTRY
macro to identify the current resource. cicscvt
encountered an unexpected DFHCNV macro, (typically
with TYPE=KEY/SELECT/FIELD) at a point where no
resource had been defined. To define each conversion
template, there must be a valid DFHCNV TYPE=ENTRY
macro before any resource-specific macros.
System action:
file.
User response:
Edit the input file to add the DFHCNV TYPE=ENTRY
macro statement for the resource that is being defined
at line lineNumber and retry the command.
Destination:
stderr
macro statement. Expected to have
TYPE=SELECT or TYPE=KEY specified.
Explanation:
The input file to cicscvt had no conversion template
select or key template macros, DFHCNV
TYPE=SELECT or TYPE=KEY, defined for the current
resource type. There must be at least one DFHCNV
TYPE=SELECT or TYPE=KEY macro after a
resource-type initialization DFHCNV TYPE=ENTRY
macro.
System action:
statement and continue to process the rest of the input
file. If there are any further resource type TYPE=FIELD
macros that do not have a TYPE=SELECT macro
defined before, then each of these produces this
message.
User response:
Edit the input file to add the DFHCNV TYPE=SELECT
or TYPE=KEY macro statement for the resource that is
being defined at line lineNumber and retry the
command.
Destination:
stderr

TYPE=FIELD specified.
Explanation:
The input file lacks the option LAST=YES on the only,
or the last consecutive, DFHCNV TYPE=FIELD macro
following either a DFHCNV TYPE=KEY macro or a
DFHCNV TYPE=SELECT macro. There must be a
LAST=YES option in each such group within a
conversion template, and and it must be on the last
TYPE=FIELD macro in the group.
System action:
file.
User response:
Edit the input file to include a DFHCNV
TYPE=FIELD,...,LAST=YES macro statement for the set
of conversions that is being defined at or before line
lineNumber and retry the command.
Destination:
stderr
TYPE=SELECT specified.
Explanation:
There must be a DFHCNV TYPE=SELECT macro
defined for the current resource type. The previous
DFHCNV TYPE=SELECT macro definition in the file for
the same resource was not the default definition. A
default TYPE=SELECT macro is required to finish a
resource type conversion template.
System action:
file.
User response:
Edit the input file to add the DFHCNV TYPE=SELECT
macro statement for the resource that is being defined
at line lineNumber, or correct any error in the preceding
macro statements, and retry the command.
Destination:
stderr
macro option. Expected to have
OPTION=DEFAULT specified.
Explanation:
The current resource ENTRY has USREXIT=YES
specified. With USREXIT=YES specified,
OPTION=COMPARE is not allowed in any of the
DFHCNV TYPE=SELECT statements for that resource.
System action:
ERZ002074E ERZ002079E
file.
System action:
The cicscvt command continues to process the rest of
the input file.
User response:
Edit the input file to change the DFHCNV
TYPE=SELECT macro so that it has the
OPTION=DEFAULT and retry the command.
User response:
Edit the input file to assign a value to the optionName
Destination:
stderr
ERZ002074E lineNumber: DFHCNV macro statement
before TYPE=INITIAL or after
TYPE=FINAL is ignored
Explanation:
There is a DFHCNV macro statement either before the
DFHCNV TYPE=INITIAL or after the DFHCNV
TYPE=FINAL macros. These macro statements are
invalid and are ignored by cicscvt.
System action:
statement and continue to process the rest of the input
file.
User response:
Edit the input file to remove any DFHCNV macro
statements before and after the macros DFHCNV
TYPE=INITIAL and DFHCNV TYPE=FINAL,
respectively.
Destination:
stderr
ERZ002075E lineNumber: The DFHCNV
TYPE=FINAL statement is not expected
Explanation:
There is a DFHCNV TYPE=FINAL macro statement
before the definition of a conversion template has been
completed.
System action:
The cicscvt command terminates the translation
prematurely.
User response:
Edit the input file to remove the DFHCNV TYPE=FINAL
macro or to change the current conversion template so
that it has been completely defined.
Destination:
stderr
ERZ002076W lineNumber: The option optionName
has been assigned the DEFAULT
hexadecimal value value
Explanation:
A DFHCNV macro option has been omitted, although its
value is required, so cicscvt assigned the option a
default value.
Destination:
stderr
TYPE=INITIAL statement. Only one
DFHCNV TYPE=INITIAL statement can
be specified in a conversion template
file.
Explanation:
There is more than one DFHCNV TYPE=INITIAL macro
statement for the conversion template.
System action:
The cicscvt command terminates the translation
prematurely.
User response:
Edit the input file to remove the duplicate DFHCNV
TYPE=INITIAL macros, and retry the command.
Destination:
stderr
ERZ002078W lineNumber: Unexpected end of
DFHCNV macro statement
Explanation:
More macro options were expected where the end of
line appears. Typically, this warning is generated if a
macro statement terminates with a comma.
System action:
file.
User response:
Edit the input file to terminate the DFHCNV macro
correctly and retry the command.
Destination:
stderr
ERZ002079E lineNumber: Missing left parenthesis
in DFHCNV macro statement
Explanation:
A list for a DFHCNV macro option was not enclosed by
parentheses. All lists must be enclosed by parentheses.
System action:
file.
User response:
ERZ002080E ERZ002087W
Edit the input file to add the parentheses around the list
of arguments and retry the command.
Destination:
stderr
ERZ002080E lineNumber: Missing right parenthesis
in DFHCNV macro statement
Explanation:
A list for a DFHCNV macro option was not terminated
by a right parenthesis. All lists must be enclosed by
matching parentheses.
System action:
file.
User response:
Edit the input file to place parentheses around the list of
arguments and retry the command.
Destination:
stderr
ERZ002081E lineNumber: Missing comma in
Explanation:
The DFHCNV macro contained some macro options, or
a list of arguments to an option, not separated by
commas.
System action:
file.
User response:
Edit the input file to add the missing comma to the
Destination:
stderr
ERZ002082E lineNumber: Missing equal sign in
Explanation:
A macro option did not have a preceding equals sign at
line lineNumber in the input file.
System action:
The cicscvt command ignores the operand and
User response:
Edit the input file to add the missing equals sign to the
Destination:
stderr
10
ERZ002083E lineNumber: The DFHCNV macro

keyword keyword has an invalid
argument argumentValue
Explanation:
A DFHCNV macro keyword did not have a valid
argument on line lineNumber. For the keyword TYPE,
valid arguments are INITIAL, ENTRY, KEY, SELECT
and FIELD.
System action:
file.
User response:
Edit the input file to change the DFHCNV macros
keyword argument to one of INITIAL, ENTRY, KEY,
SELECT or FIELD and re-try.
Destination:
stderr
ERZ002086I The compiled template for resource
resourceName of type resourceType
has been written to fileName
Explanation:
The cicscvt command has successfully produced, from
your input file, a file containing the compiled data
conversion template for the specified resource.
System action:
the input file if more resource type specifications exist.
Otherwise it terminates.
User response:
None
Destination:
stderr
ERZ002087W lineNumber: The DFHCNV macro has
both DATA and XDATA options
specified. The value associated with
the option XDATA is ignored.
Explanation:
The cicscvt command encountered both the DATA and
XDATA options specified in the DFHCNV macro. The
data associated with the XDATA option is ignored.
System action:
The cicscvt command ignores the value associated with
the XDATA option and continues to process the rest of
the input file.
User response:
Edit the input file to remove one of the options DATA
and XDATA and retry the command.
Destination:
stderr
ERZ002089E ERZ002095E
load conversion template information
Explanation:
CICS was unable to load a conversion template into
memory as there was a memory shortage.
System action:
This results in no conversion taking place.
User response:
Try again when the system has more memory available.
If the problem persists, contact your support
organization.
Destination:
CSMT
ERZ002090E The resource resourceName in class
className is not defined in the
runtime database
Explanation:
CICS tried to load the resource names conversion
template file, but found that it was not defined in the
runtime database.
System action:
This results in no conversion taking place.
CICS was unable to retrieve the template and so no

conversion is done.
User response:
Check that the permissions are valid for reading on the
conversion template file specified. Retry, and if this does
not work then contact your support organization.
Destination:
CSMT
ERZ002093E Unsuccessful attempt to read
conversion template file fileName.
errorMessage
Explanation:
CICS was unable to read in the conversion template file
for the reason given by the operating system as
errorMessage. This is possibly due to corruption in the
file that is being read.
System action:
CICS was unable to retrieve the conversion template
and so no conversion is done.
User response:
Replace the conversion template file with a recompiled
version using cicscvt. If this message still persists,
contact your support organization.
User response:
Update the runtime database so that the resource name
is defined in the runtime database.
Destination:
CSMT
Destination:
CSMT
ERZ002094E The conversion template file

fileName is incompatible with the
current CICS run-time system
ERZ002091E The conversion template filename for

resource name resourceName is too
long
Explanation:
The version of cicscvt used to create the conversion
template file fileName does not match the current
version of the CICS runtime system.
Explanation:
CICS attempted to get the resource conversion template
file, but found that the complete pathname was too long.
System action:
The template is not retrieved and no conversion takes
place.
User response:
Install the conversion template file higher up in the
directory structure. Contact your support organization.
Destination:
CSMT
ERZ002092E Unsuccessful open of conversion
template file fileName. errorMessage
Explanation:
CICS was unable to open the specified file for reading
for the reason given by the operating system as
errorMessage.
System action:
System action:
CICS was unable to retrieve the conversion template
and so no conversion is done.
User response:
Replace the conversion template file with a recompiled
version using cicscvt. If this message still persists,
Destination:
CSMT
fileName is for a different resource
type
Explanation:
CICS was unable to use the conversion template file
fileName as this file was defined to be used by a
different resource type. This can happen if a conversion
template file has been incorrectly installed or renamed.
System action:
11
ERZ002096E ERZ003001W
CICS was unable to retrieve the correct conversion
template and so no conversion is done.
The cicscvt command truncates the name and

continues to process the input file.
User response:
Install the correct template, produced by cicscvt, for that
resource type.
User response:
Edit the input file to truncate the argument to the
DFHCNV macro option and retry the command.
Destination:
CSMT
Destination:
stderr

fileName is for resource name
resourceName1 and not
resourceName2
ERZ002099W lineNumber: Hexadecimal value

optionValue for option optionName
exceeds boundary conditions. The
DEFAULT hexadecimal value
defaultValue has been assigned.
Explanation:
CICS was unable to use the conversion template file
fileName as this file was defined to be used by a
different resource. This can happen if a conversion
template file has been incorrectly installed or renamed.
System action:
User response:
resource type and name.
Destination:
CSMT
inconsistency when trying to load the
conversion template fileName.
Expected signature signature.
Explanation:
CICS detected an inconsistency in the data contained
within the conversion template file. This is likely to be
caused by corruption of the conversion template file.
System action:
User response:
resource type and name. If the problem persists,
Destination:
CSMT
ERZ002098W lineNumber: The argument to the
DFHCNV macro option optionName
has been truncated to truncatedOption
Explanation:
The cicscvt command has encountered an argument to
a DFHCNV macro option that is too long, and so has
truncated it to truncatedOption.
System action:
12
Explanation:
The cicscvt command encountered a DFHCNV macro
optionName that was assigned a hexadecimal value
that was either too big or too small, and so cicscvt
assigned the option a default value.
System action:
the input file.
User response:
Edit the input file to assign a value to the optionValue
that is within boundary limits as specified in the
Destination:
stderr
ERZ003001W Variable in RIDFLD option is shorter
than KEYLENGTH value
Explanation:
The command level interpreter transaction (CECI) is
checking the syntax of a file control command, and the
command specifies a CECI user variable for the
RIDFLD option which is shorter than the value of the
KEYLENGTH option.
System action:
If there are no other errors during the CECI command
syntax checking phase, then the phase is completed
successfully, and you are able to execute the command.
During command execution, if the command updates
the value in the user variable specified for the RIDFLD
option, then the value is truncated to the length of the
user variable.
User response:
Increase the size of the user variable so that the length
is equal to the value specified for the KEYLENGTH
option.
Destination:
CECI user terminal
ERZ003002W ERZ003010E
ERZ003002W PF/PA key undefined
the value in the user variable specified, then the value

is truncated to the length of the user variable.
Explanation:
The user pressed a PF or PA key whose action is
currently undefined.
User response:
Correct the value as appropriate.
System action:
CECI waits for valid input.
Destination:
CECI user terminal
User response:
Use only the supported keys.
ERZ003007E Invalid name
Destination:
CECI user terminal
Explanation:
Invalid characters have been entered in name field.
Names are restricted to alphanumeric values.
ERZ003003W Invalid numeric value ignored
System action:
Explanation:
A numeric value has been badly specified and has been
ignored. It is possibly out of range or possibly contains
invalid characters.
System action:
the value in the user variable specified, then the value
is truncated to the length of the user variable.
User response:
Correct the name as appropriate.
Destination:
CECI user terminal
ERZ003008E Duplicate name
Explanation:
This message indicates that the variable name being
defined already exists.
User response:
System action:
Destination:
CECI user terminal
User response:
Correct the name as appropriate.
ERZ003004W Invalid hex characters ignored
Destination:
CECI user terminal
Explanation:
Invalid hexadecimal digits have been typed in a
hexadecimal input field. The invalid hex pairs are
ignored.
System action:
User response:
Destination:
CECI user terminal
ERZ003009E Variable does not exist or is null

Explanation:
A variable name being used does not exist, or has no
contents.
System action:
User response:
Create the variable with the necessary value.
Destination:
CECI user terminal
ERZ003010E Variable cannot be created
ERZ003005W Invalid negative value ignored

Explanation:
The length field for a variable has been badly specified,
and has been ignored.
System action:
Explanation:
A variable name being used does not exist, and there is
insufficient space to create it.
System action:
User response:
Delete any unused variables and retry.
Destination:
13
ERZ003011E ERZ004006E
CECI user terminal
ERZ003011E RIDFLD must be a variable for
browsing
Explanation:
checking the syntax of a file control browse command,
and the command specifies a literal value for the
RIDFLD option.
System action:
ERZ004002I Usage: cicstcl [-adesvp] [-c number]

[-g locale] [-l Language]
[-q{APOST|QUOTE}] [-x External
Cmd] [-X External Cmd] File
Explanation:
You entered the cicstcl command incorrectly.
System action:
The cicstcl command terminates with exit code 2. No
further messages are produced. No translated/compiled
output files are produced.
User response:
Specify a user variable for the RIDFLD option and retry.
User response:
Retry the command using valid syntax, as shown in the
message.
Destination:
CECI user terminal
Destination:
stderr
ERZ003012E Variable in FROM option is shorter

than length value
ERZ004004W Translator flag flagName ignored.
Explanation:
checking the syntax of a command which specifes a
FROM option using a user variable, with an explicit
LENGTH or FLENGTH option. The size of the user
variable is shorter than that requested by the explicit
length option.
System action:
CECI waits for valid input changing the size of the user
variable or the length option.
User response:
Increase the size of the user variable so that the length
is equal to or greater than the value specified for the
length option. Alternatively, reduce the size given in the
length option.
Destination:
CECI user terminal
ERZ004001I Usage: cicstran [-PDdesv] [-c number]
[-g locale] [-l language] [-O outputfile ]
[-q APOST | QUOTE] file
Explanation:
You entered the cicstran command incorrectly.
System action:
The cicstran command terminates with exit code 2. No
further messages are produced. No translated output
files are produced.
User response:
Retry the command using valid syntax, as shown in the
message.
Destination:
stderr
Explanation:
You specified a valid flag for cicstran or cicstcl under
incorrect circumstances. For example, a flag that you
entered can be valid for one language but not for the
language you specified.
System action:
The cicstran or cicstcl command ignores the specified
flag and continues the translation.
User response:
No immediate response is required. Retry the command
with valid flags if you do not wish to see this warning.
Destination:
stderr
ERZ004005E Unsuccessful open of input file
fileName; error code errorCode
Explanation:
The file you requested cicstran or cicstcl to process was
unable to be opened for the reason defined by the
operating system error code.
System action:
The cicstran or cicstcl command terminates with exit
code 2. No translated output files are produced.
User response:
Check that the file you entered is valid and has the
correct read permissions and retry. If the problem
persists contact your support organization
Destination:
stderr
ERZ004006E [ Missing quote or incorrect column
for EXEC command string
continuation.
Explanation:
14
ERZ004007E ERZ004012E
The EXEC command you entered in the application
source file contains a quote or double quote, followed
by a newline character before column 73.
System action:
value 1. The translated output is not compilable.
System action:
value 1. The translated output is possibly not
compilable.
User response:
Remove the newline character in the DFH macro in the
application source file and retry.
User response:
Edit the input application source file to correct the
continuation line command specified at the line number
and retry.
Destination:
stderr
ERZ004007E Unsuccessful close of input file
fileName; error code errorCode.
Explanation:
unable to be closed for the reason defined by the
System action:
code 2. The translated output is possibly not compilable.
User response:
Check that there is enough space left on the disk and
try the translation again. If the problem still persists
Destination:
stderr
ERZ004008E Unsuccessful open of output file
Explanation:
The output file produced by cicstran was unable to be
opened for the reason defined by the operating system
error code.
System action:
The cicstran or cicstcl command terminates immediately
with value 2 without producing a translated output file.
User response:
Check the environment (for example, the disk space
available) and retry. If the problem still persists, contact
Destination:
stderr
ERZ004009E [ lineno: macro cannot contain a new
line character.
Explanation:
You have a newline character between the parentheses
of the argument to the specified DFH macro in your
input application file.
Destination:
stderr
ERZ004010E Unsuccessful close of output file
Explanation:
The output file produced by either cicstran or cicstcl was
unable to be closed for the reason defined by the
System action:
with value 2, producing a non-compilable translated
output.
User response:
Check the environment (for example, the disk space
available) and retry. If the problem still persists, contact
Destination:
stderr
ERZ004011E Unsuccessful attempt to set locale to
localeName.
Explanation:
The locale you specified to cicstran using the -g option
is not valid.
System action:
with exit value 2, without producing a translated output
file.
User response:
Retry the command with a valid -g option.
Destination:
stderr
ERZ004012E Unsuccessful write to output file
Explanation:
The cicstran or cicstcl command was unable to write to
file fileName for the reason defined by the operating
system error code.
System action:
with exit value 2 and possibly produces a
non-compilable, partially translated output file.
User response:
15
ERZ004013E ERZ004017E
Use the operating system documentation to find the
meaning of the return code from the function fwrite().
Destination:
stderr
ERZ004013E Unsuccessful read of input
application file fileName; error code
errorCode.
Explanation:
not able to be read for the reason defined by the
System action:
User response:
Use the operating system documentation to find the
meaning of the return code from the function fread().
Destination:
stderr
ERZ004014E The CICS translator cannot find the
support module for programming
language loadmodule, or the support
module is invalid
Explanation:
The language module you supplied to cicstran or cicstcl
using the -l option was unable to be loaded. cicstran
and cicstcl support the C and COBOL languages for
CICS. The cicstran translator dynamically loads a
support module for a programming language when
requested (using the cicstran -l option [default
-lCOBOL]). If the cicstran translator cannot find the
support module for a language, or the support module
does not exist, or has an invalid internal format, then
cicstran generates this message. The support module is
possibly missing because CICS does not support the
programming language, the operating environment set
up is incorrect, or the load module is incorrectly
formatted.
System action:
with exit value 2, and produces no translated output
files.
User response:
Check that the language you requested is valid and try
again. If the problem persists then contact your support
organization.
Destination:
stderr
ERZ004015E Unsuccessful attempt to initialize a

translator environment.
Explanation:
The cicstran or cicstcl command was unable to set up
an internal translation facilities environment. Insufficient
memory was available.
System action:
This message can be produced from a number of
facilities of CICS, including cicstran and cicstcl, and
CICS transactions such as CECI and CECS. The action
taken by the system can differ according to the facility
being run. cicstran or cicstcl terminates immediately with
exit value 2, and does not produce a translated output
file.
User response:
In most cases try again later when the system has more
memory available. If the problem persists, contact your
support organization.
Destination:
stderr
ERZ004016E Unsuccessful memory allocation for
translator cross-reference storage;
error code errorCode
Explanation:
Your request for a cross-reference file produced by the
cicstran translator was unsuccessful due to shortage of
memory.
System action:
User response:
Try again later when the system has more memory
available. If the problem persists, contact your support
organization.
Destination:
stderr
ERZ004017E [ Continuation character or literal
expected.
Explanation:
The cicstran or cicstcl command encountered a string
literal in your COBOL application program that did not
have either the closing quotes or a continuation
character.
System action:
The cicstran or cicstcl command displays this message
and tries to translate the rest of the file. A
non-compilable translated file is produced.
User response:
Edit the input application source file to correct the line
that is indicated.
16
ERZ004019E ERZ004023E
Destination:
stderr
ERZ004019E Unsuccessful attempt to specify time
in output listing files. No listing file will
be produced.
Explanation:
The time text string obtained from the operating system
was too big for the CICS internal buffer.
System action:
The cicstran command continues to translate the
application source file but does not produce a listing or
cross-reference file as requested.
User response:
Destination:
stderr
ERZ004020E [ Command lineno: not recognized.
Explanation:
A command has been encountered that is not
recognized. This message can be produced from a
number of facilities of CICS, including cicstran and
cicstcl, and CICS transactions such as CECI and
CECS.
System action:
The cicstran or cicstcl command continues with the
translation but terminates with value 1 and produces a
non-compilable, partially translated output file. The CICS
transaction CECI displays the error but does not let you
execute the command.
User response:
If you are using cicstran or cicstcl then you must edit
the input source application program to correct the
command at the given line and retry the translation. If
you are using the CICS transactions such as CECI,
CEMT or CECS then you must amend the command by
overtyping and retry.
Destination:
stderr
cicstran or cicstcl continues to translate and terminates

with exit value 0. A compilable translated file is
produced, but the warning message must be
considered.
User response:
If you are using cicstran or cicstcl then you must edit
the input application source file and correct the
command introducer at the specified line number and
retry the translation.
Destination:
stderr
ERZ004022E [ Command lineno: is not valid for
environment or language.
Explanation:
A command was encountered that is not supported in
your environment or your applications programming
language. This message can be produced from a
CECS.
System action:
The cicstran or cicstcl command continues to translate
the rest of the input application file but terminates with
exit value 1. A non-compilable translated output file is
produced. The CICS transaction CECI displays the
error, but does not let you execute the command. The
CICS transaction CECS simply displays the error.
User response:
If you are executing cicstran or cicstcl then you must
edit the input application source file and remove/change
the command indicated by the line number and retry the
translation. If this command is absolutely required then
you must change the language of the source application
program to one that accepts the required command. If
you are using the CICS transactions CECI or CECS
then you must change the command so that it is valid
and retry.
Destination:
stderr
ERZ004023E [ Invalid command option lineno:.
ERZ004021W [ Invalid command introducer lineno:

specified.
Explanation:
A command introducer, that is a keyword which
introduces a command for example EXEC, was
encountered that was not recognized. This message
can be produced from a number of facilities of CICS,
including cicstran and cicstcl, and CICS transactions
such as CECI and CECS.
System action:
Explanation:
A command option was encountered that is not valid for
the command being analysed. This message can be
produced from a number of facilities of CICS, including
cicstran and cicstcl, and CICS transactions such as
CECI and CECS.
System action:
exit value 1. A non-compilable, partially translated output
file is produced. The CICS transaction CECI displays
the error but does not let you execute the command.
The CICS transaction CECS simply displays the error.
17
ERZ004024E ERZ004027E
User response:
edit the input application source file and remove/change
the command option indicated by the line number and
retry the translation. If you are using the CICS
transactions CECI or CECS then you must change the
command option so that it is valid and retry.
Destination:
stderr
ERZ004024E [ Command requires the option,
lineno:, when ] has been specified.
Explanation:
A command option, ] was specified which requires
another command option lineno: for the command to
be valid. This message can be produced from a number
of facilities of CICS, including cicstran and cicstcl, and
CICS transactions such as CECI and CECS.
System action:
User response:
edit the input application source file and add/remove the
appropriate command option indicated at the line
number specified and retry the translation. If you are
using the CICS transactions CECI or CECS then you
must change the command option so that it is valid and
retry.
Destination:
stderr
ERZ004025E [ Command requires the option:
lineno:.
Explanation:
A command option lineno: is required for the command
to be valid. This message can be produced from a
CECS.
System action:
User response:
edit the input application source file and add the
command option indicated at the line number specified,
and retry the translation. If you are using the CICS
18

Destination:
stderr
ERZ004026E [ Command options lineno: and ]
conflict.
Explanation:
The command has mutually exclusive options specified
for the particular command. This message can be
CECI and CECS.
System action:
The CICS transaction CECS simply display the error.
User response:
edit the input application source file and remove one of
the command options indicated, at the line number
specified, and retry the translation. If you are using the
CICS transactions CECI or CECS then you must
change the command option so that it is valid and retry.
Destination:
stderr
ERZ004027E [ Command option lineno:
unexpected: only valid if ] specified.
Explanation:
An unexpected option, lineno:, was encountered that is
valid for the command only if ] is specified. This
message can be produced from a number of facilities of
CICS, including cicstran and cicstcl, and CICS
transactions such as CECI and CECS.
System action:
the error, but does not let you execute the command.
User response:
Destination:
stderr
ERZ004028E ERZ004031E
ERZ004028E [ Command option lineno: has
unmatched parenthesis.
ERZ004030W [ No argument for command option

lineno: expected.
Explanation:
The command option, lineno:, has a missing opening
or closing parenthesis for its required argument. This
message can be produced from a number of facilities of
CICS, including cicstran and cicstcl, and CICS
Explanation:
An argument was specified for a command option that
expects no arguments. This message can be produced
from a number of facilities of CICS, including cicstran
and cicstcl, and CICS transactions such as CECI and
CECS.
System action:
System action:
cicstran and cicstcl ignore the argument associated with
the specified option, continue to translate the rest of the
input application file, and terminate with exit value 0. A
compilable translated output file is produced. The CICS
transaction CECI displays the warning and lets you
execute the command. The CICS transaction CECS
simply displays the warning.
User response:
edit the input application source file and add the missing
left/right parenthesis to the command option indicated,
at the line number specified, and retry the translation. If
then you must correct the missing parenthesis for the
User response:
If you are executing cicstran or cicstcl then you can edit
the input application source file, remove the command
options argument at the line number specified, and
transactions CECI or CECS then you can change the
Destination:
stderr
Destination:
stderr
ERZ004029E [ Option lineno: is not valid for the

environment or language.
ERZ004031E [ Option lineno: expected

DATA-VALUE argument.
Explanation:
The option, lineno:, is not a valid option for the
specified command in your environment or the language
of your input application program. This message can be
CECI and CECS.
Explanation:
The option, lineno:, had a missing argument that needs
to be a data value. This message can be produced from
a number of facilities of CICS, including cicstran and
CECS.
System action:
System action:
exit value 1. A non-compilable, partly translated output
User response:
edit the input application source file and remove the
transactions CECI or CECS then you must remove the
User response:
edit the input application source file and add the data
value argument to the command option indicated, at the
line number specified, and retry the translation. If you
are using the CICS transactions CECI or CECS then
you must add the data value argument to the command
option so that it is valid and retry.
Destination:
stderr
Destination:
stderr
19
ERZ004032E ERZ004035E
ERZ004032E [ Option lineno: expected NAME
argument.
ERZ004034E [ Option lineno: expected PTR-VALUE

argument.
Explanation:
to be a name. This message can be produced from a
CECS.
Explanation:
to be a pointer value. This message can be produced
from a number of facilities of CICS, including cicstran
and cicstcl, and CICS transactions such as CECI and
CECS.
System action:
System action:
User response:
edit the input application source file and add the name
argument to the command option indicated, at the line
number specified, and retry the translation. If you are
must add the name argument to the command option so
that it is valid and retry.
User response:
edit the input application source file and add the pointer
value argument to the command option indicated at the
you must add the pointer value argument to the
Destination:
stderr
Destination:
stderr
ERZ004033E [ Option lineno: expected

DATA-AREA argument.
ERZ004035E [ Option lineno: expected PTR-REF

argument.
Explanation:
to be a data area. This message can be produced from
a number of facilities of CICS, including cicstran and
CECS.
Explanation:
to be a pointer reference. This message can be
CECI and CECS.
System action:
System action:
the rest of the input application file, but terminates with
User response:
edit the input application source file and add the data
area argument to the command option indicated at the
you must add the data area to the command option so
User response:
edit the input application source file and add the pointer
reference argument to the command option indicated at
the line number specified, and retry the translation. If
then you must add the pointer reference argument to
the command option so that it is valid and retry.
Destination:
stderr
Destination:
stderr
20
ERZ004036E ERZ004040E
ERZ004036E [ Option lineno: expected CVDA
argument.
ERZ004038E [ Option lineno: expected HHMMSS

argument.
Explanation:
to be a CVDA. This message can be produced from a
CECS.
Explanation:
to be in HHMMSS format. This message can be
CECI and CECS.
System action:
System action:
User response:
edit the input application source file and add the CVDA
argument to the command option indicated at the line
must add the CVDA argument to the command option
so that it is valid and retry.
User response:
HHMMSS argument to the command option indicated at
the line number specified, and retry the translation. If
then you must add the HHMMSS argument to the
Destination:
stderr
Destination:
stderr
ERZ004037E [ Option lineno: expected LABEL

argument.
ERZ004039W [ argument lineno: for macro ] is

not supported.
Explanation:
to be a label. This message can be produced from a
CECS.
Explanation:
The CVDA lineno: for the ] macro is valid but is not
supported for this version of CICS.
System action:
User response:
edit the input application source file and add the label
argument to the command option indicated at the line
must add the label argument to the command option so
Destination:
stderr
System action:
The cicstran or cicstcl command substitutes the correct
value for the CVDA in the DFH macro and continues to
translate the input application file, terminating with exit
value 0. A compilable translated output file is produced,
but as the warning indicates, the CVDA value is not
supported by CICS.
User response:
You must edit the input application source file and
remove or change the DFH macro argument indicated
at the line number specified, and retry the translation.
Destination:
stderr
ERZ004040E [ Argument lineno: for macro ] is
invalid.
Explanation:
See the message. The CVDA lineno: for the DFH ] is
an invalid CVDA and is not supported.
System action:
21
ERZ004041W ERZ004045E
exit value 1. A non-compilable translated output file is
produced.
You must edit the input application source file and add
the arguments opening parenthesis to the DFH macro
argument indicated at the line number specified, and
retry the translation.
User response:
You must edit the input application source file and
remove or change the DFH macro argument indicated
at the line number specified, and retry the translation.
Destination:
stderr
Destination:
stderr
ERZ004041W [ lineno: is ambiguous. CICS
assumes ].
Explanation:
You specified lineno: on the command on the line
specified in the input file. This is a shortened version of
a required option, ], but it is also a shortened version
of another option. CICS assumes that you intended ]
for further analysis. This message can be produced
from a number of facilities, including cicstran and cicstcl,
and CICS transactions such as CECI and CECS.
System action:
the input application file with the specified command
option as a substitute. If the command option CICS
assumed is correct, then the cicstran or cicstcl
command terminates with exit value 0. A compilable
translated output file is produced. If the assumed
command option is wrong, then further errors occur and
the cicstran or cicstcl command terminates with exit
value 1. The CICS transaction CECI displays the
warning and tries to execute the command. The CICS
transaction CECS simply displays the warning.
User response:
If you are executing cicstran or cicstcl, edit the input
application source file to remove the ambiguity in the
command option on the line specified and retry the
translation. If you are using the CICS transactions CECI
or CECS then you can change the command option to
be more specific and retry.
Destination:
stderr
ERZ004042E [ lineno: Macro requires (.
Explanation:
The DFH lineno: has a missing opening parenthesis for
its required argument.
System action:
exit value 1. A non-compilable, partially translated
source file is produced.
User response:
22
ERZ004043E [ Unexpected end of application

source file lineno:
Explanation:
You did not terminate one or more of the following: a
CICS statement; a statement enclosed in quotes; a
comment statement; or an argument without the closing
parenthesis and the cicstran or cicstcl reached the end
of the file.
System action:
value 1 and produces a non-compilable translated
output file.
User response:
Edit the input application source file to correct the file
accordingly and retry the translation.
Destination:
stderr
ERZ004045E [ Option lineno: expected DATA AREA
not string literal
Explanation:
The argument specified with the lineno: was a string
literal and not a data area as was expected for that
option. This message can be produced from a number
of facilities of CICS, including cicstran and cicstcl, and
System action:
the rest of the input application file, but terminates with
User response:
change the command option so that it has a data area
argument and retry.
Destination:
stderr
ERZ004046I ERZ004052E
ERZ004046I Running the pre-translation -x step:
commandName
ERZ004050E Application path, pathName, is too

long
Explanation:
This is an information message to tell you that the
cicstcl pre-translation step is about to be executed.
Explanation:
The application pathname you specified to either
cicstran or cicstcl was too long.
System action:
The cicstcl command executes the pre-translation step.
System action:
with exit value 2. No translated output file is produced.
User response:
None
Destination:
stderr
ERZ004047I Running the translation step:
commandName
Explanation:
cicstcl is about to invoke the translator cicstran with the
arguments specified.
System action:
The cicstcl command executes the translation step.
User response:
None
Destination:
stderr
ERZ004048I Running the post-translation -X step:
commandName
Explanation:
cicstcl post-translation step is about to be executed.
System action:
The program cicstcl executes the post-translation step.
User response:
None
Destination:
stderr
ERZ004049I Running the compile and link step:
commandName
Explanation:
cicstcl is about to invoke the compile and link steps.
System action:
The cicstcl command executes the compile and link
step.
User response:
None
Destination:
stderr
User response:
Retry the command with a shorter path name.
Destination:
stderr
ERZ004051W [ Option lineno: already specified.
Explanation:
The command lineno: was already specified in the
command and is therefore ignored. Only the first option
is used. Therefore if you have a different argument
associated with the repeated option, this is not used.
facilities of CICS, including cicstran and cicstcl, and
System action:
the rest of the input application file and terminates with
exit value 0. A compilable translated output file is
produced. The CICS transaction CECI displays the
warning and lets you execute the command. The CICS
transaction CECS simply displays the warning.
User response:
change the command option so that it is valid and retry.
Destination:
stderr
ERZ004052E [ Command or DFH macro too long.
Explanation:
The command or DFH macro did not terminate or the
command contains unmatched quotes.
System action:
The cicstran or cicstcl command writes the untranslated
command to the output file and continues to process the
rest of the file.
User response:
Edit the input application source file to terminate the
command or DFH macro correctly, and retry the
translation.
Destination:
stderr
23
ERZ004054E ERZ004058E
ERZ004054E Unexpected Token Following
PROCEDURE DIVISION
Explanation:
You followed a PROCEDURE DIVISION statement in
COBOL with a token that was not expected. The
translator expects to see either a USING statement or
PERIOD directly after recognizing the PROCEDURE
DIVISION Token.
System action:
with exit value 1. A non-compilable translated output is
produced.
User response:
Edit the application source file to correct the
PROCEDURE DIVISION statement in your input
COBOL application program.
Destination:
stderr
ERZ004055E [ The command set lineno: specified
is not supported.
Explanation:
A command set introducer was specified that is not
supported by CICS.
System action:
The cicstran or cicstcl command does not translate the
command set specified and continues to translate the
rest of the input file. A non-compilable translated output
is produced.
User response:
edit the input application source file and correct the
command set introducer as indicated, at the line number
change the command set introducer so that it is valid,
and retry.
Destination:
stderr
ERZ004056W [ Option lineno: for command
ignored.
Explanation:
The lineno: for the command was ignored. This is
possibly due to options that are allowed for compatibility
purposes but are not actually supported by CICS. This
message can be produced from a number of facilities,
including cicstran and cicstcl, and CICS transactions
such as CECI and CECS.
System action:
the rest of the input application file, while ignoring the
option, and terminates with exit value 0. A compilable
translated output file is produced. The CICS transaction
24
CECI displays the warning and lets you execute the

command. The CICS transaction CECS simply displays
the warning.
User response:
the input application source file and remove the option
indicated, at the line number specified, and retry the
translation. If you are using the CICS transactions CECI
or CECS then you can remove the command option so
Destination:
stderr
ERZ004057W [ Command is ambiguous, lineno:
has been assumed.
Explanation:
A command that is ambiguous and can be matched to
another command has been encountered. CICS
therefore assumes the lineno: for further analysis. This
is possibly not the command you want to be analysed.
facilities, including cicstran and cicstcl, and CICS
System action:
the input application file with the specified command as
a substitute. If CICS assumed the correct command
then cicstran or cicstcl terminates with exit value 0. A
compilable translated output file is produced. If the
assumed command is wrong, then further errors occur
and the cicstran or cicstcl terminate with exit value 1.
The CICS transaction CECI displays the warning and
tries to execute the command. The CICS transaction
CECS simply displays the warning.
User response:
edit the input application source file and be more
specific about the command indicated, at the line
can change the command to be more specific and retry.
Destination:
stderr
ERZ004058E [ Option lineno: expected DATA AREA
not numeric value.
Explanation:
The argument specified with the lineno: was a numeric
value and not a data area as was expected for that
option. This message can be produced from a number
of facilities, including cicstran and cicstcl, and CICS
System action:
the input application file but terminates with exit value 1.
A non-compilable, partially translated output file is
ERZ004059W ERZ004065W
produced. The CICS transaction CECI displays the error
but does not let you execute the command. The CICS
transaction CECS simply displays the error.
User response:
edit the input application source file and change the
argument of the option indicated to a data area and
command options argument type so that it is a data
area argument and retry.
Destination:
stderr
ERZ004059W [ Command options lineno: and ]
conflict, optionName assumed.
Explanation:
The command has mutually exclusive options specified
and therefore CICS assumes optionName for further
analysis. This message can be produced from a number
of facilities, including cicstran and cicstcl, and CICS
System action:
the input application file with the assumed command
and terminates with exit value 0. A compilable translated
output file is produced. The CICS transaction CECI
displays the warning and does not let you execute the
command. The CICS transaction CECS simply displays
the warning.
If there is an error check the input application source

file.
Destination:
stderr
ERZ004061W Argument for flag option -c cannot
handle less than minLinePerPage.
Assumed minLinePerPage lines of code
per page
Explanation:
You entered a value to cicstran or cicstcl for the number
of lines per page option, -c, for a listing or
cross-reference file that is less than the minimum value.
Therefore cicstran or cicstcl assumes the minimum
value, minLinePerPage, for the number of lines per
page in the output listing and cross-reference files.
System action:
The cicstran or cicstcl command ignores the value
associated with the specified -c flag and defaults to the
minimum value. This value is purely governed by the
headers contained within the output listing file.
User response:
Increase the value of the -c, lines per page, option on
the command line when invoking cicstran or cicstcl.
Destination:
stderr
generate translated code.
User response:
the input application source file and correct the
command options indicated, at the line number
CICS transactions CECI or CECS then you can change
the command option so that it is valid and retry. Edit the
application source file and correct the command.
Explanation:
Your request for a translation by the cicstran or cicstcl
translator was unsuccessful due to shortage of memory.
Destination:
stderr
User response:
Try again later when the system has more memory
available. If the problem persists, contact your support
organization.
ERZ004060I cicstran translation ended: errorCountu

error(s), warnCountu warning(s).
Explanation:
This is an information message telling you how many
errors and warnings were found by cicstran or cicstcl
during translation.
System action:
The cicstran command finished translating. If there is an
error in the file, then a partially translated,
non-compilable file is produced. If there are no errors,
then a translated and compilable file is produced. The
cicstcl command continues to the compilation stage if
there were no errors.
User response:
System action:
with exit value 2. A non-compilable, partially translated
output file is possibly produced.
Destination:
stderr
ERZ004065W Argument for flag option -c cannot
handle more than maxLinePerPage.
Assumed maxLinePerPage lines of
code per page
Explanation:
You entered a value to the program cicstran or cicstcl
for the number of lines per page option, -c, for a listing
or cross-reference file that exceeds the maximum value.
Therefore cicstran or cicstcl assumes the maximum
value, maxLinePerPage, for the number of lines per
page in the output listing and cross-reference files.
25
ERZ004066E ERZ004070W
System action:
The cicstran or cicstcl command ignores the value
associated with the specified -c flag and defaults to the
maximum value.
User response:
Decrease the value of the -c, lines per page, option on
the command line when invoking cicstran or cicstcl.
Destination:
stderr
ERZ004066E [ Number of options for command ]
exceeded lineno:.
Explanation:
A number of commands have a limit on the number of
options that can be handled. This message expresses
that the maximum number of options for the command
specified was exceeded. This message can be
CECI and CECS.
ERZ004068I Post-translation -X step finished with

exit code: exitCode
Explanation:
Information message to tell you the exit code of the
command executed after the translation stage and
before the compile stage of cicstcl.
System action:
The cicstcl command continues to execute the compile
and link step.
User response:
If the exit code displayed is not the required exit code
then interrupt cicstcl with a Ctrl-C and re-enter the
corrected command.
Destination:
stderr
ERZ004069E [ Command requires the option,
lineno:, when both ] and optionName
have been specified.
System action:
Explanation:
The command option lineno: is required when the
options ] and optionName have both been specified in
the command. This message can be produced from a
CECS.
User response:
edit the input application source file and change the
number of options so that it is below the limit specified
command number of options and retry.
System action:
Destination:
stderr
User response:
edit the input application source file and add/remove the
appropriate command option indicated at the line
number specified and retry the translation. If you are
must change the command option so that it is valid and
retry.
ERZ004067I Pre-translation -x step finished with

exit code: exitCode
Explanation:
Information message to tell you the exit code of the
command executed prior to the translation stage of
cicstcl.
System action:
The cicstcl command continues to translate the input
application file and, if successful, continues to the
compile and link stage.
User response:
If the exit code displayed is not the required exit code
then interrupt cicstcl with a Ctrl-C and re-enter the
corrected command.
Destination:
stderr
Destination:
stderr
ERZ004070W Option optionName must not specify
a value, value ignored.
Explanation:
You entered a browse command on the terminal (using
the NEXT keyword) along with the name of a resource
to browse. This makes no sense.
System action:
CICS continues processing as if the resource name had
not been entered.
User response:
26
ERZ004071E ERZ005001I
Either retry the command without specifying a resource
name, or retry the command using a resource name but
without the NEXT keyword.
Destination:
stderr
ERZ004071E RIDFLD must be a fullword variable,
type F, for RBA or RRN.
Explanation:
You entered a read, write or delete command on the
terminal with the RBA or RRN option (implying an ESDS
or RRDS file) and specified a constant RIDFLD. This is
not allowed.
System action:
CICS waits for you to enter a variable for the RIDFLD
option or remove the RBA or RRN option.
User response:
If the file you are using is ESDS or RRDS, then specify
a fullword variable for the RIDFLD (which can be
defined by pressing PF5). If you are using a KSDS file
then remove the RBA or RRN option, as these are not
valid for this type of file.
Destination:
stderr
ERZ004072W Unsuccessful open of copybook
fileName.
Explanation:
The cicstran or cicstcl command was unable to locate
and open the specified copybook.
System action:
The cicstran or cicstcl command continues translation.
User response:
If the specified copybook contains CICS statements
ensure that it is pre-translated and that it is either in the
path specified in the COPY statement or in the path
specified by the COBCPY environment variable.
ERZ004074W Program does not begin with an

Identification Division.
Explanation:
The file translated did not contain an Identification
Division. It cannot be a complete COBOL program, but
is possibly valid as a COPY book.
System action:
The translator continues to translate any EXEC CICS
commands but does not insert any prologue or
epilogue.
User response:
None, if the file is designed to be used as a COPY
book.
Destination:
stderr
ERZ004075E Usage : argv[0] cobolfile
Explanation:
Wrong usage of cicscobinsert command.
System action:
The cicscobinsert command fails returning 1.
User response:
Check usage and try again.
Destination:
stderr
ERZ004076E File Input could not be opened, error
returned was %2$d
Explanation:
File compiled does not exist.
System action:
The cicscobinsert command fails returning 1.
User response:
Check the meaning of the error number when returned
from the fopen() call, check file name and try again.
Destination:
stderr
Destination:
stderr
ERZ004073W Error processing copybook

fileName.
ERZ005001I Usage: cicsmap [-a] [-e] [-f codeSet]

[-p|-s] [-r] [-x] fileName[.bms]
Explanation:
The cicstran or cicstcl command detected an error while
processing the specified copybook.
Explanation:
You entered the cicsmap command incorrectly.
System action:
The cicstran or cicstcl command continues translation.
User response:
Re-translate the specified copybook.
Destination:
stderr
System action:
The cicsmap command terminates.
User response:
Enter the cicsmap command using the correct syntax,
as shown in the message. See the TXSeries for
Multiplatforms Application Programming Guide for more
information.
Destination:
27
ERZ005002E ERZ005008E
stderr
ERZ005005E Cannot open input file fileName.

Reason was: errorMessage.
ERZ005002E Cannot convert between codesets

codeSet and currentCodeSet.
Explanation:
You cannot convert data between the codesets
specified. The codeSet is either specified explicitly by
the -f option or implicitly by the -e option.
System action:
User response:
Check that you have specified a valid codeset and that
a converter exists to convert from that codeset to the
codeset of your locale. Enter the command again, using
a valid codeset. See the TXSeries for Multiplatforms
Application Programming Guide for more information.
Destination:
stderr
ERZ005003E You must specify exactly one file
argument.
Explanation:
You entered the cicsmap command, but you specified
either zero or more than one file arguments.
System action:
User response:
Enter the command again, but specify only one file
argument. See the TXSeries for Multiplatforms
Application Programming Guide for more information.
Destination:
stderr
ERZ005004E Filename fileName has an incorrect
format.
Explanation:
You entered the cicsmap command, but you specified a
file name with an incorrect suffix, or the filename was
too long or otherwise incorrectly formed. Basic Mapping
Support (BMS) file names must have a .bms suffix and
cicsmap defaults this for you if you specify a file name
without a suffix.
System action:
User response:
Retry the cicsmap command with a valid BMS file
name.
Destination:
stderr
Explanation:
CICS cannot open the specified file for reading.
System action:
User response:
Retry the cicsmap command, using the correct file
name.
Destination:
stderr
ERZ005006E Unsuccessful memory allocation.
Basic Mapping Support (BMS) map
translation abnormally terminated.
Explanation:
cicsmap has run out of memory.
System action:
User response:
Try again when the system is less busy.
Destination:
stderr
ERZ005007E Unsuccessful attempt to set the
locale.
Explanation:
cicsmap cannot set the locale from the environment.
System action:
User response:
The locale is taken from the environment of the user
which called cicsmap. The locale categories within the
locale can be modified by a number of environment
variables. Ensure that each of these environment
variables specifies a valid locale and then retry.
Destination:
stderr
ERZ005008E Unrecoverable syntax error on line
lineNumber.
Explanation:
cicsmap detected an unrecoverable syntax error on the
given line, when translating the Basic Mapping Support
(BMS) map.
System action:
User response:
Correct the syntax error, and retry the cicsmap
command.
28
ERZ005009E ERZ005016E
Destination:
stderr
Destination:
stderr
ERZ005009E Cannot specify both -a and -s

options.
ERZ005013I Physical map generated to fileName.
Explanation:
cicsmap has been invoked with mutually exclusive
options.
System action:
User response:
Retry the cicsmap command, using the correct option.
Destination:
stderr
Explanation:
cicsmap generated the physical map with the specified
filename.
System action:
User response:
None
Destination:
stderr
ERZ005014I Logical map generated to fileName.
ERZ005010E Cannot open output file fileName.

Explanation:
cicsmap cannot open the specified file for writing.
System action:
User response:
If the specified file exists, then remove it. If not, check
that you have write permission in the current directory.
Destination:
stderr
ERZ005011I Basic Mapping Support (BMS) map
translation ended. errorCountd errors,
warningCountd warnings.
Explanation:
cicsmap generated the logical map with the specified
file name.
System action:
User response:
None
Destination:
stderr
ERZ005015E Cannot write to output file fileName.
Explanation:
cicsmap detected an error when writing to the specified
file.
Explanation:
CICS detected the specified number of errors and
warnings during map translation.
System action:
System action:
User response:
The reason for the error is given. Correct the error and
retry the cicsmap command.
User response:
None
Destination:
stderr
ERZ005012E Physical or Logical map not
generated.
Explanation:
Some errors have been detected in your Basic Mapping
Support (BMS) map and so the physical or logical map
has not generated.
System action:
User response:
Correct the errors and retry the cicsmap command.
Destination:
stderr
ERZ005016E DFHMDI parameters exceed physical
map limits on line lineNumber.
Explanation:
The map SIZE or number of fields exceeds the physical
map limit.
System action:
The cicsmap command continues processing.
User response:
Reduce the size of the map, and retry the cicsmap
command.
Destination:
stderr
29
ERZ005017W ERZ005025W
ERZ005017W Field on line lineNumber overlaps
another field.
ERZ005022E Invalid character characterValue in

label on line lineNumber.
Explanation:
A map field overlaps another field.
Explanation:
Labels must begin with a letter and contain only letters
and digits.
System action:
The cicsmap command continues processing.
User response:
Reposition the field, and retry the cicsmap command.
Destination:
stderr
ERZ005019E Line lineNumber contains invalid
characters for the current code set.
Explanation:
The line contains illegal multibyte sequences.
System action:
cicsmap ignores the line and continues processing.
User response:
Correct the line, and retry the cicsmap command.
Destination:
stderr
ERZ005020E The ICTL directive is not valid on line
lineNumber.
Explanation:
The ICTL directive requires 1, 2, or 3 comma separated
numbers to set the start, continuation, and end columns.
System action:
cicsmap ignores the ICTL directive and continues
processing.
User response:
Correct the ICTL directive, and retry the cicsmap
command.
System action:
cicsmap ignores the label and continues processing.
User response:
Correct the label, and retry the cicsmap command.
Destination:
stderr
ERZ005023W Field label labelValue too long on
line lineNumber. Label truncated to
characterCount characters.
Explanation:
Basic Mapping Support (BMS) field or group labels must
be less than thirty-one characters long.
System action:
cicsmap truncates the label and continues processing.
User response:
Destination:
stderr
ERZ005024W No macro found on line lineNumber.
Explanation:
Each record must contain a Basic Mapping Support
(BMS) macro, optionally preceded by a label.
System action:
User response:
Correct the line, and retry the cicsmap command.
Destination:
stderr
Destination:
stderr
ERZ005021E Continuation not valid on line

lineNumber. Line ignored.
ERZ005025W Unknown operation code opCode on

line lineNumber. Line ignored.
Explanation:
The continuation line did not contain blanks between
the start column and continuation columns, which are
columns 1 and 16 unless they have been reset by the
ICTL directive.
Explanation:
cicsmap detected an invalid operation code on the
given line. The only valid operation codes are: TITLE,
DFHMSD, DFHMDI, DFHMDF, and END.
System action:
User response:
Correct the continuation line, and retry the cicsmap
command.
Destination:
stderr
30
System action:
User response:
Correct the operation code, and retry the cicsmap
command.
Destination:
stderr
ERZ005026E ERZ005033E
ERZ005026E Invalid character characterValue on
line lineNumber.
Explanation:
cicsmap detected an invalid character on the given line.
The only valid characters outside strings are letters,
digits, =, ,, (, and ).
System action:
User response:
Correct the invalid character, and retry the cicsmap
command.
Destination:
stderr
ERZ005027E No closing quote in string on line
lineNumber.
Explanation:
The closing quote for a string must occur before the end
of the record.
System action:
User response:
Add a closing quote to the string, and retry the cicsmap
command.
Destination:
stderr
ERZ005028W
Invalid single & in string on line

lineNumber.
Explanation:
Use && to get a single & in a string.
System action:
cicsmap accepts the ampersand and continues
processing.
User response:
Although cicsmap handles the single ampersand, the
ampersands should be doubled up to produce a map
which can be ported to other CICS systems.
Destination:
stderr
Destination:
stderr
ERZ005030E = expected after operandValue on line
lineNumber.
Explanation:
cicsmap detected an operand that is not followed by an
= character. The operand must be followed by =.
System action:
cicsmap ignores the operand and continues processing.
User response:
Add an = after the operand, and retry the cicsmap
command.
Destination:
stderr
ERZ005031E Comma expected after operandValue
on line lineNumber.
Explanation:
cicsmap detected an operand that is not followed by a
comma. The operand must be followed by a comma.
System action:
User response:
Add a comma after the operand, and retry the cicsmap
command.
Destination:
stderr
ERZ005032E Missing ) after operandValue on line
lineNumber.
Explanation:
cicsmap detected that there is no matching ) for a list
operand that started with (.
System action:
User response:
Add a ) after the operand, and retry the cicsmap
command.
Destination:
stderr
ERZ005029E String is too long on line lineNumber.

Explanation:
A token which is too long has been found. This is
probably be an INITIAL string that contains more
characters than are permitted.
System action:
User response:
Check the length of all strings in the bms map and retry
the cicsmap command.
ERZ005033E DFHMSD operand operandValue is

not valid on line lineNumber.
Explanation:
The specified operand on the given line is not valid for
the DFHMSD macro.
System action:
User response:
Correct the operand, and retry the cicsmap command.
31
ERZ005034E ERZ005041E
Destination:
stderr
ERZ005034E DFHMDI operand operandValue is not
valid on line lineNumber.
Explanation:
the DFHMDI macro.
System action:
User response:
Destination:
stderr
ERZ005035E DFHMDF operand operandValue is
not valid on line lineNumber.
Explanation:
the DFHMDF macro.
System action:
stderr
ERZ005038W Unrecognized data after mapset
definition on line lineNumber.
Explanation:
cicsmap could not recognize the data after the mapset
definition.
System action:
cicsmap terminates.
User response:
Correct the data, and retry the cicsmap command.
Destination:
stderr
ERZ005039W DFHMSD TYPE=FINAL missing on
line lineNumber.
Explanation:
cicsmap expected to find a DFHMSD TYPE=FINAL
statement on the given line, but was unable to find one.
System action:
cicsmap terminates.
User response:
User response:
Add a DFHMSD TYPE=FINAL statement, and retry the
cicsmap command.
Destination:
stderr
Destination:
stderr
ERZ005036E DFHMSD macro missing on line

lineNumber.
ERZ005040E Invalid number number in

operandValue operand on line
lineNumber.
Explanation:
cicsmap expected to find a DFHMSD macro on the
given line, but could not find one.
System action:
cicsmap terminates.
User response:
Add a DFHMSD macro and retry the cicsmap
command.
Destination:
stderr
ERZ005037E DFHMDI macro missing on line
lineNumber.
Explanation:
cicsmap expected to find a DFHMDI macro on the given
line, but could not find one.
System action:
cicsmap terminates.
User response:
Add a DFHMDI macro, and retry the cicsmap command.
Destination:
32
Explanation:
cicsmap detected a number containing a non-numeric
value.
System action:
cicsmap ignores the operand, and continues
processing.
User response:
Correct the number, and retry the cicsmap command.
Destination:
stderr
ERZ005041E Invalid name name in operandValue
operand on line lineNumber.
Explanation:
cicsmap detected a name containing a numeric first
character on the specified line. Names must begin with
a letter.
System action:
processing.
User response:
ERZ005044E ERZ005051E
Correct the name, and retry the cicsmap command.
Destination:
stderr
stderr
ERZ005048E COLUMN parameter parameterValue
on line lineNumber is not valid.
ERZ005044E ATTRB parameter parameterValue on

line lineNumber is not valid.
Explanation:
The specified parameter after COLUMN= is not valid.
Explanation:
The specified parameter after ATTRB= is not valid.
System action:
cicsmap ignores the parameter, and continues
processing.
System action:
processing.
User response:
Correct the parameter, and retry the cicsmap command.
Destination:
stderr
User response:
Destination:
stderr
ERZ005049E CTRL parameter parameterValue on
ERZ005045E BASE parameter parameterValue on

Explanation:
The specified parameter after CTRL= is not valid.
Explanation:
The specified parameter after BASE= is not valid.
System action:
processing.
System action:
processing.
User response:
Destination:
stderr
ERZ005046E CASE parameter parameterValue on
Explanation:
The specified parameter after CASE= is not valid.
System action:
processing.
User response:
Destination:
stderr
ERZ005047E COLOR parameter parameterValue on
Explanation:
The specified parameter after COLOR= is not valid.
System action:
processing.
User response:
Destination:
User response:
Destination:
stderr
ERZ005050E DSATTS or MAPATTS parameter
parameterValue on line lineNumber is
not valid.
Explanation:
The specified parameter after DSATTS= or MAPATTS=
is not valid.
System action:
processing.
User response:
Destination:
stderr
ERZ005051E EXTATT parameter parameterValue on
Explanation:
The specified parameter after EXTATT= is not valid.
System action:
processing.
User response:
Destination:
33
ERZ005052E ERZ005059E
stderr
stderr
ERZ005052E FIELDS parameter parameterValue on

ERZ005056E DFHMDF JUSTIFY parameter

not valid.
Explanation:
The specified parameter after FIELDS= is not valid.
System action:
processing.
User response:
Destination:
stderr
ERZ005053E GRPNAME parameter parameterValue
Explanation:
The specified parameter appearing after JUSTIFY= is
not valid.
System action:
processing.
User response:
Destination:
stderr
Explanation:
The specified parameter after GRPNAME= is not valid.
ERZ005057E DFHMDI JUSTIFY parameter

not valid.
System action:
processing.
Explanation:
The specified parameter after JUSTIFY= is not valid.
User response:
System action:
processing.
Destination:
stderr
ERZ005054E HILIGHT parameter parameterValue
Explanation:
The specified parameter after HILIGHT= is not valid.
User response:
Destination:
stderr
ERZ005058E LANG parameter parameterValue on
System action:
processing.
Explanation:
The specified parameter after LANG= is not valid.
User response:
System action:
processing.
Destination:
stderr
ERZ005055E INITIAL, GINIT, or XINIT parameter
not valid.
Explanation:
The specified parameter after INITIAL=, GINIT=, or
XINIT= is not valid.
System action:
processing.
User response:
Destination:
34
User response:
Destination:
stderr
ERZ005059E LENGTH parameter parameterValue
Explanation:
The specified parameter after LENGTH= is not valid.
System action:
processing.
User response:
ERZ005060E ERZ005067E
Destination:
stderr
ERZ005060E LINE parameter parameterValue on
Explanation:
The specified parameter after LINE= is not valid.
System action:
processing.
User response:
Destination:
stderr
ERZ005061E MODE parameter parameterValue on
Explanation:
The specified parameter after MODE= is not valid.
System action:
processing.
User response:
Destination:
stderr
ERZ005062E OCCURS parameter parameterValue
Explanation:
The specified parameter after OCCURS= is not valid.
System action:
processing.
User response:
Destination:
stderr
ERZ005063E OUTLINE parameter parameterValue
Explanation:
The specified parameter after OUTLINE= is not valid.
System action:
processing.
User response:
Destination:
stderr
ERZ005064E PICIN or PICOUT parameter

not valid.
Explanation:
The specified parameter after PICIN= or PICOUT= is
not valid.
System action:
processing.
User response:
Destination:
stderr
ERZ005065E POS parameter on line lineNumber is
not valid.
Explanation:
The specified parameter after POS= is not valid.
System action:
processing.
User response:
Destination:
stderr
ERZ005066E PS parameter parameterValue on line
lineNumber is not valid.
Explanation:
The specified parameter after PS= is not valid.
System action:
processing.
User response:
Destination:
stderr
ERZ005067E SIZE parameter on line lineNumber is
not valid.
Explanation:
The specified parameter after SIZE= is not valid.
System action:
processing.
User response:
Destination:
stderr
35
ERZ005068E ERZ005075E
ERZ005068E SOSI parameter parameterValue on
ERZ005072E TIOAPFX parameter parameterValue

Explanation:
The specified parameter after SOSI= is not valid.
Explanation:
The specified parameter after TIOAPFX= is not valid.
System action:
processing.
System action:
processing.
User response:
User response:
Destination:
stderr
Destination:
stderr
ERZ005069E STORAGE parameter parameterValue

ERZ005073E TRANSP parameter parameterValue

Explanation:
The specified parameter after STORAGE= is not valid.
Explanation:
The specified parameter after TRANSP= is not valid.
System action:
processing.
System action:
processing.
User response:
User response:
Destination:
stderr
Destination:
stderr
ERZ005070E SUFFIX parameter parameterValue on

ERZ005074E TYPE parameter parameterValue on

Explanation:
The specified parameter after SUFFIX= is not valid.
Explanation:
The specified parameter after TYPE= is not valid.
System action:
processing.
System action:
processing.
User response:
User response:
Destination:
stderr
Destination:
stderr
ERZ005071E TERM parameter parameterValue on

ERZ005075E VALIDN parameter parameterValue on

Explanation:
The specified parameter after TERM= is not valid.
Explanation:
The specified parameter after VALIDN= is not valid.
System action:
processing.
System action:
processing.
User response:
User response:
Destination:
stderr
Destination:
stderr
36
ERZ005076W ERZ005090E
ERZ005076W SUFFIX parameter parameterValue
on line lineNumber is non numeric.
Explanation:
The specified parameter after SUFFIX= is not numeric.
System action:
cicsmap accepts the parameter, and continues
processing.
User response:
Use of a non-numeric parameter can conflict with
suffixes generated automatically by the TERM option.
To avoid any possibility of conflict, use a numeric suffix,
and retry the cicsmap command.
Destination:
stderr
ERZ005077W SUFFIX parameter parameterValue
on line lineNumber has been truncated.
Explanation:
The specified parameter after SUFFIX= is more than
one-character long.
System action:
cicsmap truncates the parameter to one character and
continues processing.
User response:
Change the SUFFIX parameter to a single character to
avoid this message.
Destination:
stderr
ERZ005078W Label labelValue too long on line
lineNumber. Label truncated to
characterCount characters.
Explanation:
Basic Mapping Support (BMS) labels must be less than
eight characters long.
System action:
cicsmap truncates the label and continues processing.
User response:
Destination:
stderr
ERZ005079E DATA parameter parameterValue on
Explanation:
The specified parameter after DATA= is not valid.
System action:
processing.
User response:
Destination:
stderr
ERZ005080W parameterName parameter
duplicated.
Explanation:
The specified list operand contains a duplicate
parameter; for example, ATTRB=(PROT,IC,PROT).
System action:
processing.
User response:
Remove the duplicate parameter, and retry the cicsmap
command.
Destination:
stderr
ERZ005081W parameterName parameters
parameterValue1 and parameterValue2
on line lineNumber cannot be used
together.
Explanation:
The specified parameters for the given operand are
mutually exclusive.
System action:
processing.
User response:
Remove one parameter, and retry the cicsmap
command.
Destination:
stderr
ERZ005082W optionName option on line
lineNumber already specified.
Explanation:
The specified option has already been given.
System action:
cicsmap ignores the duplicate option, and continues
processing.
User response:
Remove the duplicate option, and retry the cicsmap
command.
Destination:
stderr
ERZ005090E DFHMSD or DFHMDI macro on line
lineNumber must be labelled.
Explanation:
DFHMSD and DFHMDI macros must be labelled.
37
ERZ005091E ERZ005100W
System action:
cicsmap continues processing.
User response:
Add a label, and retry the cicsmap command.
ERZ005095W GRPNAME and OCCURS operands

together.
Destination:
stderr
Explanation:
The GRPNAME and OCCURS operands are mutually
exclusive.
ERZ005091E Label labelValue is duplicated on line

lineNumber.
System action:
cicsmap uses the first operand specified, and continues
processing.
Explanation:
The specified label already exists.
System action:
User response:
Change the label, and retry the cicsmap command.
Destination:
stderr
ERZ005093W BASE and STORAGE operands on
line lineNumber cannot be used
together.
Explanation:
The BASE and STORAGE operands are mutually
exclusive.
User response:
Remove either the GRPNAME or OCCURS operand,
Destination:
stderr
ERZ005097W PICIN or PICOUT on line lineNumber
can only be used with LANG=COBOL
or LANG=PLI.
Explanation:
The PICIN and PICOUT operands are only valid for
LANG=COBOL or LANG=PLI.
System action:
cicsmap ignores the PICIN or PICOUT operand, and
System action:
processing.
User response:
Remove the PICIN or PICOUT operand, or set
LANG=COBOL or LANG=PLI, and retry the cicsmap
command.
User response:
Remove either the BASE or STORAGE operand, and
Destination:
stderr
Destination:
stderr
ERZ005098W INITIAL, GINIT, and XINIT operands

together.
ERZ005094W SUFFIX operand on line lineNumber

overridden by TERM option.
Explanation:
The INITIAL, GINIT, and XINIT parameters are mutually
exclusive.
Explanation:
The TERM and SUFFIX operands are mutually
exclusive.
System action:
cicsmap uses the TERM operand, ignores the SUFFIX
operand, and continues processing.
User response:
Remove either the TERM or SUFFIX operand, and retry
Destination:
stderr
System action:
processing.
User response:
Remove either the INITIAL, GINIT, or XINIT operand,
Destination:
stderr
ERZ005100W TIOAPFX=YES must be specified on
line lineNumber.
Explanation:
CICS on Open Systems and CICS for Windows NT
require that TIOAPFX=YES is always specified.
38
ERZ005102W ERZ005114E
System action:
User response:
Add TIOAPFX=YES, and retry the cicsmap command.
Destination:
stderr
ERZ005102W Extended attribute attributeName is
not specified in MAPATTS on line
lineNumber.
Explanation:
Extended attributes specified in DFHMDF macros must
be specified in MAPATTS, implied by EXTATT or by
specifying extended attribute in the DFHMSD or
DFHMDI macro.
System action:
User response:
Add an extended attribute to MAPATTS, and retry the
cicsmap command.
Destination:
stderr
ERZ005103W DSATTS parameter parameterName
is not specified in MAPATTS on line
lineNumber - parameterName ignored.
Explanation:
All DSATTS parameters must be specified in MAPATTS
or implied by specifying the extended attribute in the
DFHMSD or DFHMDI macro.
System action:
User response:
Add the DSATTS parameter to MAPATTS, and retry the
cicsmap command.
Destination:
stderr
ERZ005110E SIZE operand must be specified on line
lineNumber.
Explanation:
SIZE defaults to (0,0) which is invalid, so you must
specify SIZE.
System action:
User response:
Add a SIZE operand, and retry the cicsmap command.
Destination:
stderr
ERZ005111E SIZE parameter is out of range on line

lineNumber.
Explanation:
The minimum map size is (1,1) and the maximum map
size is (240, 240). The specified map size is outside this
range.
System action:
User response:
Retry with values for rows and columns in the range 1
to 240 and retry the cicsmap command.
Destination:
stderr
ERZ005112W The total number of fields in the map
exceeds 1023 on line lineNumber.
Explanation:
The maximum number of fields in a map is 1023. The
map contains more than 1023 fields.
System action:
User response:
Reduce the number of fields on the map, and retry the
cicsmap command.
Destination:
stderr
ERZ005113W The total length of initial data in the
map exceeds 2560 characters on line
lineNumber.
Explanation:
The maximum total length of all initial data in a map is
2560 bytes. The number of characters in the map
exceeds this maximum.
System action:
User response:
Reduce the amount of initial data on the map, and retry
Destination:
stderr
ERZ005114E The parameterName parameter is out
of range on line lineNumber.
Explanation:
The value of the LINE or COLUMN parameter must be
in the range 1 to 240 (inclusive). The actual value is
outside this range.
System action:
User response:
39
ERZ005120E ERZ005126E
Change the value of the specified parameter, and retry
Correct the POS, SIZE or LENGTH operand, and retry

Destination:
stderr
Destination:
stderr
ERZ005120E POS operand must be specified on

line lineNumber.
ERZ005124W INITIAL data exceeds field length on

line lineNumber. The data is truncated.
Explanation:
POS defaults to (0, 0) which is invalid. Therefore, you
must specify POS.
Explanation:
The length of INITIAL, GINIT, or XINIT data exceeds the
field length specified by LENGTH. For unnamed fields
which contain MBCS characters, the initial data is
truncated only if the display width of MBCS characters
(regardless the number of bytes per character) exceeds
the LENGTH value.
System action:
User response:
Add the POS operand, and retry the cicsmap command.
Destination:
stderr
ERZ005121E POS operand is outside map
boundary on line lineNumber.
Explanation:
POS must specify a position within the specified map
SIZE. The current value is outside the map boundary.
System action:
User response:
Correct the POS or SIZE operand, and retry the
cicsmap command.
Destination:
stderr
ERZ005122E LENGTH zero or not specified on line
lineNumber.
Explanation:
The default LENGTH is 0, which is invalid. Therefore,
you must specify LENGTH.
System action:
User response:
Add a LENGTH operand, and retry the cicsmap
command.
Destination:
stderr
ERZ005123E Field exceeds map boundary on line
lineNumber.
Explanation:
The end of a field is outside the map.
System action:
User response:
40
System action:
User response:
Correct the value of the LENGTH, INITIAL, GINIT, or
XINIT operand, and retry the cicsmap command.
Destination:
stderr
ERZ005125E XINIT contains invalid or odd number
of hexadecimal characters on line
lineNumber.
Explanation:
XINIT must contain an even number of hexadecimal
characters. Valid hexadecimal characters are 0-9 and
A-F.
System action:
User response:
Correct the value of the XINIT operand, and retry the
cicsmap command.
Destination:
stderr
ERZ005126E XINIT parameter specifies invalid
characters for the current codeset.
Explanation:
The Multi Byte Character Set (MBCS) string formed
from the XINIT operand is not valid.
System action:
User response:
Correct the value of the XINIT operand, and check
whether you need to run the cicsmap -e command.
Destination:
stderr
ERZ005127E ERZ005134E
ERZ005127E GRPNAME operand specified on
unnamed field on line lineNumber.
Destination:
stderr
Explanation:
Fields defined with the GRPNAME operand must be
labelled.
ERZ005131W operandName operand on line

lineNumber is not supported.
System action:
Explanation:
CICS on Open Systems and CICS for Windows NT do
not support the TRANSP operand.
User response:
Add a label, and retry the cicsmap command.
Destination:
stderr
User response:
Remove the unsupported operand, and retry the
cicsmap command.
ERZ005128E OCCURS operand operandName on

line lineNumber less than 1 or greater
than 1023.
Explanation:
The value of the OCCURS parameter is out of range.
System action:
User response:
Correct the OCCURS operand, and retry the cicsmap
command.
Destination:
stderr
ERZ005129E
System action:
PICTURE character characterValue

Explanation:
The valid PICTURE characters are: A B E P S V X Z 9
0 / , . + - $ ( ) CR DB for COBOL and A B E F G H I K
M P R S T V X Y Z 1 2 3 6 7 8 9 / , . + - $ ( ) CR DB
for PL/I.
Destination:
stderr
ERZ005132W DSATTS or MAPATTS operand
operandName on line lineNumber is not
supported.
Explanation:
not support the operand.
System action:
User response:
Remove the unsupported operand, and retry the
cicsmap command.
Destination:
stderr
ERZ005133E Field in group groupName on line
lineNumber is not consecutive.
System action:
Explanation:
Fields in a group must be consecutive entries in a map
definition.
User response:
Correct the PICIN or PICOUT operand, and retry the
cicsmap command.
System action:
Destination:
stderr
User response:
Make all fields in a group consecutive, and retry the
cicsmap command.
ERZ005130W Field exceeds line boundary on line

lineNumber.
Destination:
stderr
Explanation:
The end of a field exceeds line boundary on the same
line.
ERZ005134E Field in group groupName on line

lineNumber is not in ascending order.
System action:
Explanation:
Fields in a group must be defined in ascending order of
screen position.
User response:
Correct the POS or LENGTH operand, and retry the
cicsmap command.
System action:
User response:
41
ERZ005135E ERZ005141W
Reorder the group elements in the map so that they are
in ascending order, and retry the cicsmap command.
Destination:
stderr
ERZ005135E The length of the field on line
lineNumber exceeds the maximum of
256.
Explanation:
The length of the field exceeds the allowed maximum of
256 bytes.
System action:
User response:
Check the LENGTH and any PICIN or PICOUT
operands and ensure that the length of the field is no
more than 256 bytes long. Then retry the cicsmap
command.
Destination:
stderr
ERZ005136W The ATTRB option on line lineNumber
has been ignored.
Explanation:
The ATTRB option can be specified only on the first
field in a group.
System action:
ERZ005138E The LENGTH option on line

lineNumber does not match the length
of the PICIN/PICOUT value.
Explanation:
The value supplied in the LENGTH operand differs from
the length of the value of the PICIN or PICOUT operand
for this field.
System action:
User response:
Amend either the LENGTH or the picture operands, and
Destination:
stderr
ERZ005139W The DET attribute on line lineNumber
is not supported.
Explanation:
not support the detectable (DET) attribute.
System action:
User response:
Remove the DET attribute, and retry the cicsmap
command.
Destination:
stderr
User response:
Remove the ATTRB operand, and retry the cicsmap
command.
ERZ005140E FOLD parameter on line lineNumber is

invalid.
Destination:
stderr
Explanation:
An invalid value has been specified for the FOLD
operand.
ERZ005137E The lengths of the PICIN and PICOUT

values on line lineNumber do not
match.
Explanation:
The lengths of the values of the PICIN and PICOUT
operands differ.
System action:
User response:
Check the values of the PICIN and PICOUT operands
and make them the same length. Retry the cicsmap
command.
Destination:
stderr
System action:
User response:
Correct the value to the operand and retry the cicsmap
command.
Destination:
stderr
ERZ005141W FOLD operand on line lineNumber
may only be specified on C maps.
Explanation:
FOLD is only valid in DFHMDI macros with LANG=C.
System action:
User response:
Remove the FOLD operand and retry the cicsmap
command.
42
ERZ005142W ERZ006006E
Destination:
stderr
Destination:
stderr
ERZ005142W The FIELDS=NO option on line

ERZ006002E cicssda cannot find message number

messageNumber in set catalogNumber
Explanation:
not support the FIELDS=NO option.
Explanation:
This message is issued when message
messageNumber cannot be found.
System action:
System action:
None
User response:
Remove the FIELDS=NO operand and retry the
cicsmap command.
User response:
Investigate contents of message catalog.
Destination:
stderr
ERZ005143W No fields have been specified for the
map on line lineNumber.
Explanation:
The map is not followed by any DFHMDF lines
specifying FIELDS.
System action:
User response:
Add some fields to the map and retry the cicsmap
command.
Destination:
stderr
ERZ005144W The DATA=BLOCK option on line
Explanation:
not support the DATA=BLOCK option.
System action:
User response:
Remove the DATA=BLOCK operand or specify
DATA=FIELD and retry the cicsmap command.
Destination:
stderr
ERZ006001E The specified message catalog
fileName cannot be opened
Explanation:
The specified message catalog fileName cannot be
opened.
System action:
cicssda exits.
Destination:
Any dialog for which a text string cannot be found.
ERZ006004E Unsuccessful paste operation; illegal
paste position.
Explanation:
Generated from the Paste, Move and Replicate options
on the Edit menu, when the chosen position causes the
new fields to overlap existing fields or interrupt a field
group, or causes a pasted group to include non-group
fields.
System action:
cicssda does not perform the Paste, Move or Replicate
action.
User response:
Repeat the operation at another position.
Destination:
Error panel dialog
ERZ006005E Unsuccessful paste of group name
groupName; duplicate field name
fieldName.
Explanation:
Generated from the Paste option of the Edit menu when
pasting a group causes duplicate field name(s) in the
current map.
System action:
cicssda does not perform the Paste action.
User response:
Paste group into new, empty map; change field name(s)
and remove the group name; cut or copy group to
clipboard and attempt to paste it into original map again.
Destination:
Error panel dialog
ERZ006006E Unsuccessful paste operation;
duplicate group name groupName.
Explanation:
User response:
Check access permissions to the message catalog.
43
ERZ006007E ERZ006013E
Generated from the Paste option of the Edit menu when
pasting a group causes a duplicate group name in the
current map.
System action:
cicssda does not perform the Paste action.
User response:
Paste group into new, empty map; change group name;
cut or copy group to clipboard and attempt to paste it
into original map again.
Destination:
Error panel dialog
ERZ006007E Unable to apply group name
groupName; some selected fields are
unnamed.
Explanation:
Generated from the field details dialog when applying a
group name to selected fields, and some of the fields
are unnamed.
System action:
cicssda does not perform the Apply action.
User response:
Set field names before grouping fields.
Destination:
Error panel dialog
groupName; selected fields are not
contiguous.
Explanation:
group name to selected fields, and the fields are not
contiguous.
System action:
User response:
Select contiguous fields.
Destination:
Error panel dialog
Error panel dialog

ERZ006010E Unable to apply field name
fieldName; duplicate field name.
Explanation:
Generated from the field details dialogs when applying a
field name which is not unique within the current map.
System action:
User response:
Choose another name.
Destination:
Error panel dialog
ERZ006011E Unable to ungroup fields; insufficient
space for attribute bytes.
Explanation:
null group name to a group, and ungrouping cannot be
accomplished because the addition of attribute bytes to
the second and subsequent members of the group
causes the ungrouped fields to overlap.
System action:
User response:
Move group fields apart before ungrouping.
Destination:
Error panel dialog
ERZ006012E Unable to change field type to INPUT;
insufficient space for stopper field.
Explanation:
Generated from the field details dialog when applying
field type INPUT to field which does not have enough
space at the end to add the two-character stopper.
System action:
User response:
Make room for the two-character stopper before
changing field type to INPUT.
ERZ006009E You cannot remove field name

fieldName; field belongs to group
groupName.
Destination:
Error panel dialog
Explanation:
null field name to a field which belongs to a group.

groupName; duplicate group name.
System action:
User response:
Ungroup fields before removing field names.
Destination:
44
Explanation:
group name which is duplicated in the unselected fields
in the current map.
System action:
ERZ006014E ERZ006020E
User response:
Choose another group name.
Destination:
Error panel dialog
ERZ006014E Unable to apply panel name
panelName; duplicate panel name.
Explanation:
Generated from the panel name entry dialog (via the
view menu) or the panel details dialog after an attempt
to enter a panel name which is the same as another
panel name in the panel group.
System action:
cicssda forces entry of unique panel name or cancels
the Apply action.
User response:
Choose another group name.
Destination:
Panel name entry dialog
ERZ006015E Unsuccessful open of file fileName;
reason is reasonString.
Explanation:
Generated from the file open dialog (or command line
parameter) when opening a file. The file was unable to
be opened for the reason specified in the message.
System action:
cicssda does not open the file.
User response:
Check the reason why the file was unable to be opened
and fix the problem appropriately.
Destination:
Error panel dialog
You have specified an invalid value for the rows or

columns of the panel. The minimum panel size is 1 x 1
and the maximum panel size is 240 x 240.
System action:
The panel size is not changed.
User response:
Retry with values for rows and columns in the range 1
to 240.
Destination:
Error panel dialog
ERZ006018E fileName is not a regular file
Explanation:
The given name is not a regular file and cannot be
opened for reading.
System action:
cicssda does not perform the open action.
User response:
Select a regular file to open.
Destination:
Error panel dialog.
ERZ006019E No unprotected or input fields in
panel
Explanation:
Cannot tab around panel in test mode with no data
entry fields.
System action:
cicssda does not perform the tab action.
User response:
Define some unprotected or input fields.
Destination:
Error Panel dialog
ERZ006016E Unsuccessful close of file fileName

Explanation:
Generated from the file save dialog when saving BMS
file (or from file open dialog when closing BMS file).
System action:
cicssda does not perform the Close action.
User response:
Check file access permissions.
Destination:
Error panel dialog
ERZ006017E Invalid panel dimensions: rows x
columns must both be in the range 1 to
240.
ERZ006020E You cannot enter non-numeric data in

numeric field
Explanation:
You cannot enter non-numeric data in numeric field.
System action:
User response:
Either enter numeric data, or remove NUM attribute
from the field.
Destination:
Error Panel dialog
Explanation:
45
ERZ006021E ERZ006028W
ERZ006021E Unable to print to file; enter
destination file for printing
Explanation:
You have selected Print to file without specifying a file
name.
System action:
cicssda does not perform the Print operation.
User response:
Enter a valid file name in print dialog.
Destination:
Error Panel dialog
ERZ006022E Unable to apply PICTURE string
pictureString; character characterValue
is not valid
Explanation:
PICTURE string that contains an invalid character.
System action:
User response:
Correct the PICIN or PICOUT string, and re-select apply
button.
Destination:
Error Panel dialog
ERZ006023E PICTURE string pictureString does
not match field length fieldLength
Error panel dialog

ERZ006025E Panel size cannot be reduced to rows
x columns; some fields would be
outside panel.
Explanation:
Generated from the panel details dialog when applying
a reduction in panel size to less than the rectangle that
encloses all existing fields.
System action:
User response:
Delete fields or retry with larger value for rows or
columns.
Destination:
Error panel dialog
ERZ006026E fileName is a subdirectory; please
select a file.
Explanation:
You have attempted to open a subdirectory instead of
a BMS source file.
System action:
cicssda does not perform the Open action.
User response:
Retry with a BMS source file.
Destination:
Error panel dialog
Explanation:
PICTURE string that does not match the field length.
ERZ006027E Unable to generate file fileName;

unable to execute commandString.
System action:
Explanation:
Generated from the Generate Map dialog, the CICS
executable cicsmap was unable to be started.
User response:
Correct the PICIN or PICOUT string, and re-select apply
button.
System action:
cicssda does not perform the Generate action.
Destination:
Error panel dialog
ERZ006024E Unable to apply OCCURS and
GRPNAME to same field
Explanation:
Generated from the field details dialog, cannot specify
OCCURS and GRPNAME for the same field.
System action:
User response:
Set Occurs or Group Name (not both) and repeat the
apply action.
Destination:
46
User response:
Make sure that the system executable cicsmap is in a
directory specified in the environment variable PATH
and has correct access permissions.
Destination:
Error panel dialog
ERZ006028W Unsuccessful open of default BMS
file fileName
Explanation:
cicssda was unable to open default BMS source file.
System action:
cicssda does not open the default BMS source file;
defaults for panel group, panel and field details are
used instead.
ERZ006029E ERZ006035E
User response:
Make sure that the default BMS file specified in
.Xdefaults.defaultBMS file exists and has correct
permissions.
Destination:
stderr
ERZ006029E You cannot set field type INPUT to
group fields
Explanation:
You attempted to apply field type INPUT to group fields
but members of a group cannot be input fields.
System action:
User response:
Either ungroup fields or set field type to AUTOSKIP,
UNPROTECTED, or PROTECTED.
Destination:
Error panel dialog
ERZ006030E cicssda cannot create font set
baseFontNameList
Explanation:
cicssda is unable to create a font set, bound to the
current locale, from the specified baseFontNameList.
The missing character sets are reported in subsequent
ERZ0632I messages.
System action:
cicssda terminates.
User response:
Check why the character sets listed in subsequent
ERZ0632I messages are missing (check font path) or
specify a font set appropriate to your locale via the -fn
fontName command-line argument.
Destination:
stderr
ERZ006032I Missing character set: characterSet
Explanation:
The specified character set required by the font set was
not found.
System action:
cicssda terminates or continues, depending on whether
the previous message was ERZ0630E or ERZ0631W.
User response:
See ERZ0630E or ERZ0631W.
Destination:
stderr
ERZ006033E Font set fontSet contains a
variable-width font fontName
Explanation:
cicssda requires fixed-width fonts. The specified font
within the specified font set is not fixed-width.
System action:
cicssda terminates.
User response:
Check that the font set specified on the command line
or in the resource file contains only fixed-width fonts.
Destination:
stderr
ERZ006034E cicssda cannot open X11 Input
Method
Explanation:
cicssda cannot open an X11 Input Method to handle
input in the current locale.
Destination:
stderr
System action:
cicssda terminates.
ERZ006031W Some character sets are missing for

font set baseFontNameList
User response:
Check that the X11 input method is installed for the
current locale.
Explanation:
Some of the character sets needed by the specified font
set are missing. The missing character sets are
reported in subsequent ERZ0632I messages.
System action:
cicssda continues, but characters that require any of the
missing character sets are displayed as a default
character (typically the space character).
User response:
Check why the character sets listed in subsequent
ERZ0632I messages are missing (check font path) or
specify a font set appropriate to your locale via the -fn
font command-line argument.
Destination:
stderr
ERZ006035E cicssda does not have a common
input style for locale
Explanation:
cicssda does not support any of the X11 input methods
input styles. At least one common input style must be
supported by cicssda and the input method for the
locale.
System action:
cicssda terminates.
User response:
47
ERZ006036E ERZ006043E
Try setting the environment variable $XMODIFIERS to
use a different input method for the locale.
Destination:
stderr
ERZ006036E cicssda cannot create an X11 Input
Context
Explanation:
cicssda cannot create an X11 Input Context for the input
method.
System action:
cicssda terminates.
User response:
Try setting the environment variable $XMODIFIERS to
use a different input method for the locale.
Destination:
stderr
ERZ006037E cicssda cannot convert field at row
row column column to PS=8
Explanation:
cicssda cannot convert the specified field to PS=8
because it contains single-width characters.
System action:
cicssda does not apply PS=8 to the specified field.
User response:
Delete all single-width characters from the field and try
again.
Destination:
stderr
ERZ006038W Initial value on line lineNumber
inconsistent with PS=8
Explanation:
The specified initial value contains single-width
characters, which are not allowed in PS=8 fields.
cicssda increases LENGTH.

User response:
None
Destination:
stderr
ERZ006040W LENGTH of PS=8 field on line
lineNumber is not even
Explanation:
PS=8 fields can only contain double-width characters,
so their LENGTH must always be even.
System action:
cicssda decreases LENGTH to make it even.
User response:
None
Destination:
stderr
ERZ006041W cicssda cannot determine the wide
space character for the locale
Explanation:
In multi-byte locales, cicssda needs to use wide spaces
to pad PS=8 fields. cicssda cannot determine the
appropriate wide space character for the locale.
System action:
cicssda continues, although PS=8 fields are possibly not
handled properly.
User response:
Exit cicssda and specify the wide space as the value of
the resource Cicssda.WideSpace in your .Xdefaults file.
Destination:
stderr
ERZ006042E Unable to apply name name; it has
already been specified.
System action:
cicssda changes the field to SOSI=YES, which allows
mixed single and double width characters.
Explanation:
You cannot enter a name which has already been
defined as a field name or panel name in the panel
group.
User response:
None
System action:
Destination:
stderr
User response:
Choose another name.
ERZ006039W Width of Initial value on line

lineNumber exceeds LENGTH
Explanation:
When the specified initial value is expanded to account
for SO/SI taking position, the display width of the field
exceeds LENGTH.
System action:
48
Destination:
Error panel dialog
ERZ006043E The parameter parameter is out of
range
Explanation:
ERZ006044E ERZ007003E
You have specified an invalid value for LINE or
COLUMN. The minimum size is 1 and the maximum
size is 240.
System action:
User response:
Retry with values for LINE and COLUMN in the range 1
to 240.
Destination:
Error panel dialog
ERZ006044E Value for the OCCURS parameter
must be in the range 1 to 1023.
Explanation:
The value of the OCCURS parameter is out of range.
System action:
ERZ007001E The Interval Control Element (ICE)

queue is inconsistent: queue head
(address address) has a previous ICE
(address address)
Explanation:
The CICS self-consistency checking mechanism
detected an error in the ICE queue.
System action:
User response:
Because the Interval Control data structures are held in
the Region Pool it is unlikely that the invalid data has
been produced by application code. Save any dump file
produced for use by your support organization. If the
problem persists, contact your support organization.
Destination:
console.msg
User response:
Retry with value for OCCURS in the range 1 to 1023.
ERZ007002E CICS cannot register Lock upcalls

routine
Destination:
Error panel dialog
Explanation:
CICS made an unsuccessful attempt to register an
internal function, and therefore CICS did not register the
internal prepare and abort functions.
ERZ006098E No online help facility is available

Explanation:
You have requested help, but cicssda is unable to
display help by using InfoExplorer.
System action:
No help information is displayed.
User response:
cicssda requires InfoExplorer to display the help
information, so check that InfoExplorer is available on
your machine.
Destination:
Error panel dialog
System action:
User response:
Resubmit the transaction. If the problem persists, CICS
possibly ran out of memory. This is possibly due to a
transaction that is looping in some way that causes
CICS to acquire substantial amounts of Region Pool
memory on its behalf. Check that the value of the
MaxRegionPool attribute in the Region Definition is
sufficiently large. Perform an immediate shutdown of the
region, increase the value, and restart the region.
Destination:
CSMT
ERZ006099E Usage: cicssda optionString fileName

Explanation:
You entered the cicssda command incorrectly.
System action:
The cicssda command terminates.
ERZ007003E Transaction transId could not be

triggered because it does not exist,
during a write operation to Transient
Data (TD) queue TDQname
User response:
Enter the cicssda command using the correct syntax, as
shown in the message.
Explanation:
The specified trigger transaction for Transient Data (TD)
queue TDQname was not able to be started because
no definition for it exists in the Transaction Definitions.
Destination:
stderr
System action:
User response:
See the following messages for further details.
Destination:
CSMT
49
ERZ007004E ERZ007009W
ERZ007004E CICS could not access the region
database
Explanation:
CICS has made an unsuccessful attempt to access the
region database.
System action:
User response:
Destination:
CSMT
ERZ007005E CICS cannot obtain memory to create
an Interval Control Element (ICE)
Explanation:
CICS made an unsuccessful attempt to create an ICE,
due to a memory allocation problem.
System action:
User response:
Destination:
CSMT
ERZ007006E CICS is unable to delete an item from
the Locked Resource list
CSMT
ERZ007007E CICS is unable to create a TIDE
Explanation:
Whilst processing a protected interval control request,
CICS was not able to create the Transaction Id Element
(TIDE) holding internal data about the request.
System action:
User response:
CICS to acquie substantial amounts of Region Pool
sufficiently large. If it is not, perform an immediate
shutdown of the region, increase the value, and restart
the region.
Destination:
CSMT
ERZ007008E CICS is unable to delete an ICE
Explanation:
Because of an internal problem, CICS was not able to
delete the internal data held about an interval control
request.
System action:
CICS continues processing
User response:
the Region Pool, this problem is unlikely to be caused
by application code. It is more likely to be caused by an
inconsistency in the CICS internal data structures.
Check that the next CICS self-consistency check of the
region is successful. If the problem reoccurs, save any
dump file produced and contact your support
organization.
Destination:
CSMT
Explanation:
Because of an internal problem, CICS was not able to
delete the details of the locked resource from the list of
all locked resources.
ERZ007009W Unable to run asynchronous

transaction transId on inactive
terminal terminalId
System action:
Explanation:
CICS tried to run an asynchronously-started transaction
on a terminal that was logged off.
User response:
Resubmit the transaction. If the problem persists, and
you want to investigate it, check that the next CICS
self-consistency check of the region is successful. If this
indicates a problem, take a system dump and contact
Destination:
50
System action:
CICS continues processing, and attempts to resubmit
the transaction when the terminal is logged on.
User response:
Sign on to the terminal, and the transaction runs.
Destination:
ERZ007010E ERZ007015E
console.msg
ERZ007010E Error obtaining data for terminal
terminalId for asynchronous running
of transaction transId
Explanation:
Whilst attempting to run an interval control request on
terminal terminalId, CICS was not able to obtain the
terminals details.
System action:
CICS continues processing, but does not submit the
asynchronous transaction.
User response:
Check that the terminal required for the asynchronous
start is in the database. Sign on to the terminal.
Destination:
console.msg
ERZ007011E Transaction transId not started
asynchronously
Explanation:
CICS was unable to start an asynchronous transaction
that is not attached to a terminal. The scheduler was
unable to schedule the request.
System action:
CICS continues processing, but does not start the
asynchronous transaction.
User response:
Check the console log for any other messages that
possibly indicate why the transaction was rejected. If
there are none, check that the transaction is correctly
defined and then resubmit. If the the problem persists
Destination:
console.msg
ERZ007012E Unable to queue transaction transId
on terminal terminalId
Explanation:
CICS made an unsuccessful attempt to start a
transaction on the named terminal.
System action:
transaction transId.
User response:
Check that a cicsterm is running for the named terminal.
If not, sign on to the terminal.
Destination:
console.msg
ERZ007013E Unable to obtain memory to create an

Interval Control Element (ICE)
Explanation:
CICS was not able to obtain the memory required to
create an ICE.
System action:
User response:
the region.
Destination:
CSMT
ERZ007014E Transaction transId could not be
triggered because principal facility
terminalId does not exist, during a
write operation to Transient Data (TD)
queue TDQname
Explanation:
The trigger transaction for Transient Data (TD) queue
TDQname was not able to be started because no
definition for the specified facility terminalId exists in
the Terminal Definitions.
System action:
User response:
Destination:
CSMT
ERZ007015E Unable to obtain memory to create a
Delay Context
Explanation:
CICS was not able to obtain memory for the data
required to allow an EXEC CICS DELAY call to delay a
task.
System action:
User response:
51
ERZ007016E ERZ007022E
the region.
Destination:
CSMT
ERZ007016E Unable to delete Waiting Task data
Explanation:
While processing a wait for a resource that has either
timed out, or the lock has become available, CICS was
not able to delete the information about the waiting task.
User response:
Destination:
CSMT
System action:
CICS continues processing.
ERZ007021E Unable to unlock resources at

syncpoint
User response:
the Region Pool, the problem encountered freeing the
data structures is unlikely to be caused by application
code. It is more likely to be caused by an inconsistency
in the CICS internal data structures. If you want to
investigate this problem, check that the next CICS
self-consistency check of the region is successful. If the
problem reoccurs, save any dump file produced and
Explanation:
At syncpoint, CICS attempts to release all the locks held
by a transaction. Because of an internal error, it was
unable to do so.
Destination:
CSMT
ERZ007019E Unable to restart a triggered
transaction
Explanation:
A triggered transaction ended without removing all of
the records from its Transient Data Queue. Interval
Control attempted to re-start the transaction, but was
unable to do so.
System action:
User response:
If you want to investigate this problem, examine
previous error messages for evidence of an earlier
problem, such as insufficient memory for an operation.
Check previous messages for possible reasons why this
transaction was not able to be run. Check that the next
CICS self-consistency check of the region is successful.
If the problem reoccurs, save any dump file produced
and contact your support organization.
Destination:
console.msg
ERZ007020E Unable to create a transaction ID
element (TIDE)
Explanation:
CICS was not able to create a TIDE.
System action:
52
System action:
User response:
in the CICS internal data structures. Check that the next
Destination:
CSMT
ERZ007022E Unable to unlock resources at
transaction end
Explanation:
At transaction end, CICS attempts to release all the
locks held by a transaction. Because of an internal
error, it was unable to do so.
System action:
User response:
in the CICS internal data structures. Check that the next
Destination:
CSMT
ERZ007024E ERZ007033E
ERZ007024E Attempt to delete a Temporary
Storage (TS) queue returned
ERZ_ABEND
Explanation:
Interval Control attempted to delete a TSQ used for an
Interval Control Element (ICE). It was unable to do so,
because the Temporary Storage delete operation
abnormally terminated.
System action:
User response:
Check that Temporary Storage is available. If it is not,
consider restarting the file server.
Destination:
CSMT
ERZ007028E Lock Resource structure (at address
address) has inconsistent signature;
expected expectedSignature actual
actualSignature
Explanation:
Self-consistency checking by CICS has detected an
inconsistent signature string in the Lock Resource
structure whose address is given.
System action:
CICS self-consistency checking continues.
User response:
been produced by application code. Consider shutting
the region down if any further errors are reported. Save
any dump file produced for use by your support
organization. If the problem persists contact your
Destination:
console.msg
ERZ007030W Cannot collect statistics for Interval
Control
ERZ007031E Unable to set an alarm for an ENQ

Explanation:
CICS detected an unexpected return code when
attempting to set an alarm.
System action:
User response:
Resubmit the transaction. If the problem persists CICS
the region. If the problem persists and you want to
investigate it, check that the value of the
DeadlockTimeout attribute in the Region Definitions is
valid. If you cannot find the problem, check that the next
Destination:
CSMT
ERZ007032E Unable to set an alarm
Explanation:
attempting to set an alarm.
System action:
CICS abnormally terminates the server.
User response:
CICS possibly ran out of memory. This is possibly due
to a transaction that is looping in some way that causes
the region. If you cannot find the problem, check that
the next CICS self-consistency check of the region is
successful.
Explanation:
CICS was not able to find an entry in the
Communications Definitions for the local system.
Destination:
CSMT
System action:
ERZ007033E Unable to access Temporary Storage
User response:
If you want statistics to be collected for Interval Control,
you must have an entry for the local system in the
regions Region Definitions. Shut down the region, add
the entry for the local system in the Region Definitions
and restart the region.
Destination:
CSMT
Explanation:
attempting to read from or write to temporary storage.
System action:
CICS continues processing. However, Interval Control is
only available if Temporary Storage is available.
User response:
Check that Temporary Storage is available. Check the
error logs for previous messages that might indicate the
cause of this problem.
53
ERZ007034E ERZ007039E
Destination:
CSMT
ERZ007034E The request to run a transaction is
invalid
Explanation:
CICS detected an invalid attempt to start a transaction.
This is possibly because you attempted to start a
CICS-private transaction, or because a transaction was
started at an inappropriate phase of region operation, or
on an invalid terminal, or the transaction definitions (TD)
did not allow the transaction to be run via the START
command.
System action:
User response:
Ensure that the START command is valid. Check that
the value of the InvocationMode attribute in the
Transaction Definition for the transaction you want to
START is appropriate.
Destination:
CSMT
ERZ007035E The Wait Task structure (at address
address) has inconsistent signature;
actualSignature
Explanation:
Self-consistency checking by CICS has detected an
inconsistent signature string in the Wait Task structure
whose address is given.
System action:
User response:
Destination:
console.msg
ERZ007036E The Interval Control Element (ICE)
queue is inconsistent: Unexpected
expiry time of head of queue
Explanation:
The self-consistency checking mechanism of CICS
System action:
User response:
54

Destination:
console.msg
ERZ007037E Interval Control Element (ICE)
(address address) has inconsistent
signature - expected
expectedSignature actual
actualSignature
Explanation:
The self-consistency checking mechanism in CICS.
detected an error in an element in the ICE queue.
System action:
User response:
Destination:
console.msg
ERZ007038E Interval Control Element (ICE) queue
inconsistent: ICE address is followed
by address instead of address
Explanation:
System action:
User response:
problem persists contact your support organization.
Destination:
console.msg
ERZ007039E Interval Control Element (ICE) queue
inconsistent: ICE address is preceded
by address instead of address
Explanation:
ERZ007040E ERZ007044E
System action:
User response:
Destination:
console.msg
ERZ007040E Interval Control Element (ICE) address
has inconsistent hash links: its reqId
reqId has a different hash value to the
reqId reqId of the next ICE address
Explanation:
System action:
User response:
Destination:
console.msg
has inconsistent hash links: its reqId
reqId has a different hash value to the
reqId reqId of the previous ICE
address
Explanation:
System action:
User response:
Destination:
console.msg
has an expiry time inconsistent with
that of other ICEs in the queue

detected an error in the ICE queue. CICS relocates the
ICE in the queue.
System action:
User response:
Destination:
console.msg
Lock Record (LR)
Explanation:
CICS was not able to obtain the memory required to
create an ICE.
System action:
User response:
sufficiently large. If it is not, increase the value, and
restart the region.
Destination:
CSMT
ERZ007044E Recovery of Interval Control Element
TSQname was unsuccessful due to an
I/O error
Explanation:
CICS was not able to recover an Interval Control
Element because it was unable to read the
corresponding Temporary Storage Queue.
System action:
User response:
Check that Temporary Storage is available. Restart the
file server if necessary. Performing a cold start avoids
this problem, but causes recovery information to be lost.
Destination:
console.msg
Explanation:
55
ERZ007045E ERZ007050W
TSQname was unsuccessful due to bad
data
Explanation:
CICS was not able to recover Interval Control Element
because the corresponding Temporary Storage Queue
contained unrecognized data.
System action:
User response:
Examine previous messages for problems that might
affect Temporary Storage. Restart the file server if
necessary. Performing a cold start avoids this problem,
but causes recovery information to be lost.
Destination:
console.msg
TSQname was unsuccessful
Explanation:
CICS recovered an Interval Control Element but was
unable to add it to the ICE queue. This must be due to
an internal inconsistency.
System action:
User response:
been produced by application code. It is more likely to
be caused by an inconsistency in the CICS internal data
structures. Performing a cold start avoids this problem,
but causes recovery information to be lost.
Destination:
console.msg
value of the CUBSDelayMinutes attribute in the Region

Definitions is reasonable: between 1 and 5999.
Performing a cold start avoids this problem, but causes
recovery information to be lost.
Destination:
console.msg
ERZ007048E Invalid attempt to route triggered
transaction transId for Transient Data
queue TDQname
Explanation:
The definition of a transaction that has been specified
as the trigger transaction for a transient data queue
indicates that the transaction is to be routed to another
system. This is invalid.
System action:
User response:
Consider changing the transaction definitions (TD) so
that the transaction has a blank RemoteSysId.
Alternatively, you can change the transient data
definitions (TDD) so that the TriggeredTransId contains
the name of a transaction that is run locally.
Destination:
CSMT
ERZ007049W Asynchronously-started transaction
transId terminated abnormally.
Temporary Storage Queue TSQName
should be deleted.
Explanation:
The asynchronously-started transaction has terminated
abnormally because the application server in which it
was running was unexpectedly terminated. CICS has
been unable to delete the TS queue associated with the
transaction.
ERZ007047E Unable to schedule the blocked ICE

recovery transaction
System action:
CICS continues.
Explanation:
CICS was not able to schedule the CICS-private
transaction that updates recovered starts in the event of
the file server not being available. This must be due to
an internal inconsistency.
User response:
Delete the TS Queue associated with the transaction.
This can be done by using the CICS-supplied
transaction CECI. Failure to delete the TS Queue can
result in the asynchronous start being recovered if the
region is warm started.
System action:
User response:
During auto start, CICS has attempted to recover
Interval Control Elements (ICEs), but is unable to do so
because Temporary Storage is unavailable. Therefore, it
attempts to schedule a transaction that recovers the
blocked requests. This attempt to schedule the
transaction has failed. If you want to investigate this
problem, check that the value of the MaxRegionPool
attribute in the Region Definition is sufficiently large. If it
is not, increase it and restart the region. Check that the
56
Destination:
console.msg
ERZ007050W Triggered transaction transId for
Transient Data Queue TDQname has
encountered problems
Explanation:
The triggered transaction has encountered a problem.
Previous messages possibly indicate the source of the
problem.
ERZ007051W ERZ007056E
System action:
CICS continues.
The TS Queue was possibly already deleted or the TSQ

definition is possibly incorrect.
User response:
Examine previous messages for the source of the
problem and take action accordingly.
Destination:
console.msg
Destination:
console.msg
ERZ007054I Temporary Storage queue of name

TSQname already exists
ERZ007051W Asynchronously-started transaction

transId has encountered problems
Explanation:
CICS detected that a temporary storage file of this
name already exists when attempting to write to
temporary storage.
Explanation:
The asynchronously-started transaction has
encountered a problem. Previous messages possibly
indicate the source of the problem.
System action:
CICS continues.
System action:
User response:
Check the Reqid used and alter it to avoid conflicts with
names of temporary storage queues.
User response:
Examine previous messages for the source of the
problem and take action accordingly.
Destination:
CSMT
Destination:
console.msg
ERZ007055E Unable to schedule the ICE cancel

transaction
ERZ007052W Transaction transId has not run.

Temporary Storage Queue TSQName
for Asynchronously-started transaction
transId should be deleted.
Explanation:
The asynchronously-started transaction has not run and
CICS has been unable to delete the TS queue
associated with the transaction. Other console
messages possibly indicate the cause of the problem. If
there are no other related messages, failure are
possibly due to problems in Transaction Definition (TD).
System action:
CICS continues.
User response:
Check the Transaction Definition (TD) for possible
errors. Delete the TS Queue associated with the
transaction. This can be done by using the
CICS-supplied transaction CECI. Failure to delete the
TS Queue can result in the asynchronous start being
recovered if the region is warm started.
Destination:
console.msg
ERZ007053E The reqid reqId does not exist
Explanation:
Attempt to delete the reqid has failed as it does not
exist.
System action:
CICS continues.
User response:
Explanation:
transaction that cancels starts.
System action:
User response:
This attempt to schedule the transaction responsible for
cancelling STARTS has failed. If you want to investigate
this problem, check that the value of the
sufficiently large. If it is not, increase it and restart the
region.
Destination:
console.msg
ERZ007056E Unable to locate Transaction
Definition for transaction transId
Explanation:
transaction identified in the message because the
Transaction Definition was not able to be located.
System action:
User response:
This attempt to schedule the internal transaction
transId has failed. If you want to investigate this
problem, check that the transId transaction is present
in the regions Transaction Definitions. Use the
definitions from another region to verify the definition
does not differ from the default definition for this
transaction.
57
ERZ007057E ERZ010003I
Destination:
console.msg
ERZ007057E Unable to queue transaction transId
on terminal terminalId, transaction
destination sysid is SysId, terminal
RemoteSysId SysId.
Explanation:
CICS made an unsuccessful attempt to start a
transaction on the named terminal. The transaction was
directed to start on terminal terminalId, at that time the
terminal had a RemoteSysId of SysId. The terminal
RemoteSysId is now SysId. This message is usually
driven by common client applications with a printer that
have terminated before a transaction can run on the
printer. If the terminals RemoteSysId is now NULL then
the terminal is active locally.
System action:
User response:
Check that a cicsterm or cicstermp is running for the
named terminal. If not, sign on to the terminal.
Destination:
console.msg
Wait Context
Explanation:
CICS was not able to obtain memory for the data
required to allow an EXEC CICS POST call to delay a
task.
System action:
User response:
the region.
Destination:
CSMT
ERZ007059E Excpection EXCEPTIONtext in hand
post thread.
Explanation:
CICS encountered an unexpected expection
(EXCEPTIONtext) while processing hand posts
System action:
58
User response:
Contact support
Destination:
console.msg
ERZ010001E Unable to run region regionName
because it is locked
Explanation:
CICS cannot start the region regionName because a
lock file already exists. This indicates either that the
region with this name is already running, or that the
region is not running and the lock file remains due to
the termination of the region in an uncontrolled manner.
System action:
CICS startup terminates.
User response:
If cicsgpid shows that a region of the given name is
running already, you cannot start it. If there is no region
running but a lock file exists, use cicsrlck to remove the
lock. When using cicsrlck, ensure that you only remove
the lock file for the region regionName.
Destination:
console.msg
ERZ010002E Unable to find the lock file for region
regionName
Explanation:
CICS was not able to find the lock file for the named
region. CICS creates the lock file at region startup and
deletes it at region shutdown. This error suggests that
the named region is not running.
System action:
cicsgpid terminates.
User response:
Check that you supplied the correct region name.
Destination:
stderr
ERZ010003I CICS is performing region abnormal
termination in process processName
Explanation:
CICS is abnormally terminating the region due to a
CICS internal error.
System action:
CICS abnormally terminates the region, and produces a
system dump.
User response:
Examine previous error messages to determine the
cause of the problem.
Destination:
console.msg
ERZ010004I ERZ010009I
ERZ010004I CICS will use AuthenticationService:
nameService
ERZ010007I About to run shutdown phase

phaseNumber programs
Explanation:
CICS uses the name service facilities supplied by
nameService for its clients to locate their servers and
uses authentication service facilities supplied by
authenticationService.
Explanation:
CICS shutdown processing is running the programs in
the shutdown program list for phase phaseNumber of
shutdown.
System action:
CICS continues to run start up.
User response:
None.
Destination:
console.msg
ERZ010005E Unable to find startup or shutdown
program programName
Explanation:
CICS cannot find the program programName listed in
the program list for startup or shutdown.
System action:
If this error occurs during startup, then CICS abnormally
terminates the region. If it occurs at shutdown, region
shutdown processing continues.
User response:
Check that the entries in the program list and the
Program Definitions (PD) are consistent. Use program
names, not transaction names in the startup or
shutdown program lists.
Destination:
console.msg
ERZ010006E Unable to run startup program
programName because of insufficient
authorization
Explanation:
The program programName cannot be run because it
has inappropriate security permissions.
System action:
If this error occurs during startup, then CICS abnormally
terminates the region. If it occurs at shutdown, region
shutdown processing continues.
User response:
Change the security permissions for the program.
Ensure that it has read and execute permission for user
cics.
Destination:
console.msg
System action:
CICS continues to shut down.
User response:
None
Destination:
console.msg
ERZ010008W Unable to read the region restart file,
operating system error number
errorNumber
Explanation:
CICS uses the restart file to recover information saved
during a previous run of the region. CICS was not able
to read data from the restart file.
System action:
CICS continues to run start up.
User response:
Check the access permissions for the region directory
and the region restart file. Ensure that they have read
and write permissions for user cics. The region restart
file was possibly truncated due to an operating system
problem. If you suspect that this is the case, check the
integrity of the filesystem. See message ERZ1092E
following this one for further details. If the content of
ERZ1092E gives insufficient information about why the
error occurred use the operating system error number
errorNumber to obtain more information.
Destination:
console.msg
ERZ010009I Unable to remove the lock file because
region regionName is still running
process processInformation
Explanation:
CICS attempted to remove a region lock file using
cicsrlck, but the named region is running.
processInformation is the process identification number
for the region process.
System action:
cicsrlck terminates.
User response:
Ensure that the named region is the region whose lock
file you wish to remove. In certain rare circumstances,
another process can be assigned the same process ID
that the region ran with. In this situation, you can use
the -f flag to force removal.
Destination:
59
ERZ010010W ERZ010016W
stderr
console.msg
ERZ010010W Removing the lock file region for

regionName although it is still running
process processName
ERZ010013I CICS has removed the lock file for

region regionName
Explanation:
cicsrlck removed the lock file for the named region even
though there appears to be a process running for the
region. cicsrlck removed the lock because you specified
the force flag -f. processName is the process
identification number for the region process.
Explanation:
cicsrlck has removed the lock file for the named region.
System action:
None
User response:
None
System action:
Destination:
stderr
User response:
Check whether the process running is for the region. If it
is, shut down the region immediately, because the
region is able to be started again, causing data to be
overwritten.
ERZ010014E Cannot read lock file for region

regionName because of operating
system error errorNumber
Destination:
stderr
ERZ010011E CICS cannot create region lock file
fileName for region regionName,
operating system error number
errorNumber
Explanation:
The CICS process was not able to create the lock file
for the named region.
System action:
CICS terminates.
User response:
Check that the directory for the named region has the
required permissions. Ensure that it is owned by user
cics and that it has read, write and execute permissions
for its owner. Check that the file system is not full. See
message ERZ1092E following this one for further
details. If the content of ERZ1092E gives insufficient
information about why the error occurred use the
operating system error number errorNumber to obtain
more information.
Destination:
console.msg
ERZ010012I CICS is performing an immediate
shutdown of region regionName
Explanation:
A request to shut down the region immediately has
been received.
System action:
The region commences an immediate shutdown.
User response:
None
Destination:
60
Explanation:
cicsgpid was not able to read the lock file for region
regionName.
System action:
User response:
Check that the region directory is available and that the
permissions for the region lock file are appropriate.
Destination:
stderr
ERZ010015E Cannot remove lock file for region
regionName because of operating
system error errorNumber
Explanation:
cicsrlck was not able to remove the region lock file.
System action:
User response:
Check that the permissions for the region directory and
the region lock file are correct. Ensure that they are
owned by user cics and have read, write and execute
permissions for their owner.
Destination:
stderr
ERZ010016W Could not open restart file for region
regionName, operating system error
number errorNumber
Explanation:
CICS was unable to open the region restart file.
System action:
CICS logs this message and continues.
User response:
ERZ010017I ERZ010025W
Check that the permissions for the region directory and
the region restart file are correct. Ensure that they are
owned by user cics and have read, write and execute
permissions for their owner. See message ERZ1092E
following this one for further details. If the content of
ERZ1092E gives insufficient information about why the
error occurred use the operating system error number
errorNumber to obtain more information.
Destination:
console.msg
ERZ010017I CICS is performing a normal shutdown
of region regionName
Explanation:
A request to shutdown the region normally has been
received.
System action:
The region commences a normal shutdown.
User response:
None
Destination:
console.msg
ERZ010018E Unable to allocate a unique identifier
for process processName
Explanation:
CICS was not able to create a region-wide unique
identifier for the named process.
System action:
User response:
If the problem persists, save any dump produced and
Destination:
console.msg
ERZ010019W Cannot start Application Server
Explanation:
CICS was unable to start an Application Server. This is
possibly because there are already a large number of
processes running.
System action:
The transaction that was to be run in the server is
placed on the queue and is run when a server becomes
available.
User response:
Check the system log for further error details. If the
system is heavily loaded, reduce the load by stopping
some processes or by restricting the maximum number
of Application Servers by updating the value of the
attribute MaxServer in the Region Definitions. Check
whether the region has been installed correctly and that
the processes have execute permission for the cics
user. If the cause of the problem cannot be found,

Destination:
console.msg
ERZ010020I The region is now ready for use
Explanation:
The region is now ready for use.
System action:
User response:
None
Destination:
console.msg
ERZ010023E Cannot attach or detach shared
memory segment, error code errorCode
Explanation:
CICS made an unsuccessful attempt to attach or detach
shared memory. The Data Segment shared memory
identifier was possibly overwritten. There is possibly
inconsistency in either CICS or operating system data
structures.
System action:
User response:
Save any dump produced and contact your support
organization.
Destination:
console.msg
ERZ010024E Invalid invocation of process
processName
Explanation:
An attempt was made to start an internal CICS process
processName. The process cannot be used in this
way.
System action:
CICS terminates the process.
User response:
Do not invoke this process directly. Refer to the CICS
documentation for details of how to start a CICS region.
Destination:
stderr
ERZ010025W Unable to write to restart file for
region regionName, operating system
error number errorNumber
Explanation:
CICS was unable to write to the restart file,
varDir/cics_regions/regionName/region_restart for
61
ERZ010026I ERZ010032E
the reason given by the operating system error code
errorNumber. On Windows NT you can find the drive
letter of the disk containing the cics_regions directory
by using the cicsname regions command.
System action:
CICS logs this message and continues.
User response:
Check that the region directory is still available, and that
the restart file has appropriate permissions. Check that
the file system is not full. See message ERZ1092E
following this message for further details. If the content
of ERZ1092E gives insufficient information refer to
operating system documentation for further information
about the operating system error number errorNumber.
Perform a normal shutdown followed by a warm start.
Destination:
console.msg
ERZ010026I Usage: cicsrlck [-f] [-a | -r regionName]
Explanation:
You invoked cicsrlck with invalid arguments.
System action:
User response:
Retry the command with the correct syntax. See the
TXSeries for Multiplatforms Administration Reference for
more information.
Destination:
stderr
ERZ010027E Could not generate a list of available
lock files
Explanation:
cicsrlck made an unsuccessful attempt to access each
region directory and determine if a lock file was present.
System action:
cicssrccreate was unable to access the directory. The

directory must exist, be owned by user cics and have
read, write and execute permissions for its owner.
System action:
cicssrccreate exits.
User response:
If the directory does not exist the product has not been
installed successfully.
Destination:
stderr
ERZ010030I CICS self consistency checking
started.
Explanation:
CICS has started to check the integrity of the region.
This check takes place at time intervals controlled by
the Region Definition (RD) entry.
System action:
CICS self consistency checking begins.
User response:
None
Destination:
console.msg
ERZ010031I Usage: cicsgpid [-r regionName]
Explanation:
The command was invoked with invalid arguments.
System action:
User response:
Retry the command with the correct syntax. See the
more information.
Destination:
stderr
User response:
Check the availability and access permissions for the
region directories in varDir/cics_regions. On Windows
NT you can find the drive letter of the disk containing
the cics_regions directory by using the cicsname
regions command. Ensure that each is owned by user
cics and has read, write and execute permissions for its
owner.
ERZ010032E Could not write process identifier to

standard output
Destination:
stderr
User response:
Check that the standard output of the cicsgpid
command is directed to a valid destination. If the
destination is a file, check that it is possible to write to
that file.
ERZ010029E Unable to access the directory

directoryName
Explanation:
62
Explanation:
cicsgpid encountered an error displaying the process
identifier of the region.
System action:
Destination:
stderr
ERZ010033E ERZ010041I
ERZ010033E Unable to obtain region definition
information
Explanation:
CICS detected an internal error accessing the region
database. CICS possibly ran out of Region Pool
memory.
System action:
User response:
Examine previous messages to determine the cause of
the problem and take appropriate action.
Destination:
console.msg
ERZ010034E Unable to complete access to region
information
Explanation:
CICS detected an internal error. Unable to update
region database. CICS possibly ran out of Region Pool
memory.
Examine the error log for earlier messages that possibly

indicate the cause of the problem. If problems persist,
Destination:
console.msg
ERZ010039E Unable to start process processPath
Explanation:
CICS was not able to start one of one of its internal
processes. See message ERZ1092E following this one
for further details.
System action:
If CICS is trying to start a new application server
(message ERZ1019W appears shortly after this
message), the start fails and the transaction is placed
on the queue. Otherwise, CICS shuts the region down
immediately.
User response:
User response:
Check that the operating system is capable of starting
new processes. If the system is heavily loaded, reduce
the load by stopping some processes or by restricting
the maximum number of Application Servers by
updating the value of the attribute MaxServer in the
Region Definitions. Check whether the region has been
installed correctly and that the processes have execute
permission for the cics user. If the cause of the problem
cannot be found, contact your support organization.
Destination:
console.msg
Destination:
console.msg
ERZ010035I Waiting for user tasks to complete
ERZ010040I CICS control process processName

terminated
System action:
Explanation:
Entering the phase 2 of normal shutdown, CICS waits
for all user tasks to complete.
System action:
CICS waits until no user tasks are running.
User response:
Terminate all user tasks. If you cannot stop a task
directly, or you are unsure which tasks are still running,
use CEMT to list running tasks and the terminals they
are running on. If the tasks cannot be completed then
CEMT can be used to purge them.
Destination:
console.msg
ERZ010038E Recovery Server has terminated
abnormally
Explanation:
The Recovery Manager has detected that a Recovery
Server completed with an abnormal return code.
System action:
CICS shuts the region down immediately.
User response:
Explanation:
One of the CICS control processes terminated. If the
termination was unexpected additional messages are
output.
System action:
If the termination was unexpected and the process was
not an Application Server (cicsas), the region
abnormally terminates.
User response:
If additional messages indicate that the process ended
abnormally they possibly also give possible causes of
the problem.
Destination:
console.msg
ERZ010041I CICS has received a region stop
request during region shutdown
Explanation:
CICS was performing a region shutdown when it
received a request to terminate the region.
System action:
63
ERZ010042E ERZ010052W
CICS immediately stops any shutdown processing and
attempts to end all region processes immediately.
stderr
User response:
Wait until message ERZ1043I or ERZ10122E appears.
If the message does not appear after three minutes, the
region is cancelled. If this happens run the cicsnotify
program to free any region resources before you
attempt to restart the region.
ERZ010045I Signal signalNumberd received and

ignored by process processName
Destination:
console.msg
ERZ010042E Invalid combination of MinServer
(servers) and MaxServer (servers)
attributes
Explanation:
The named process received an unexpected, but not
fatal, signal. For instance, signal 19 is SIGCONT that is
controlled entirely by the operating system. It is usually
sent to continue stopped processes. During a region
shutdown sequence this signal is possibly issued to a
CICS process as part of the normal system action for
ending a process.
System action:
CICS ignores the signal, and continues.
Explanation:
The minimum number of servers is greater than the
maximum number or the maximum number is zero. The
maximum must equal or exceed the minimum value and
must be greater than zero.
User response:
Refer to your operating system documentation to
determine the meaning of the signal. For AIX this
information is found in the AIX Base Operating System
and Extensions Technical Reference, Volume 2.
System action:
If this error occurs during startup, CICS terminates.
Otherwise CICS continues to run with unchanged
values.
Destination:
console.msg
User response:
Change the value of MinServer, MaxServer, or both. If
this occurs at startup alter the Region Definition (RD)
values or startup overrides.
Destination:
console.msg
ERZ010043I Shutdown of CICS region regionName
is complete
Explanation:
The shutdown of a CICS region is complete.
System action:
CICS terminates.
User response:
None
Destination:
console.msg
ERZ010044E Unable to find the CICS version
Explanation:
cicssrccreate uses cicsname to determine the version.
cicsname returned an error.
System action:
User response:
Examine previous messages for possible indications of
the problem. Check that the product has been installed
correctly.
Destination:
64
ERZ010048I Application Server serverId terminated

Explanation:
The identified Application Server has terminated and is
no longer available for use.
System action:
User response:
None
Destination:
console.msg
ERZ010049E Unable to schedule the CLAM
transaction
Explanation:
CICS made an unsuccessful attempt to submit the
internal CICS transaction, CLAM, to run asynchronously.
CICS possibly ran out of Region Pool memory.
System action:
User response:
Destination:
console.msg
ERZ010052W Recovery Server has terminated
abnormally
Explanation:
The Recovery Manager has detected that a Recovery
Server completed with an abnormal return code during
ERZ010053E ERZ010061E
a normal or immediate shutdown. This is the expected
behavior when the logical unit of work being resolved by
the Recovery Server remains unresolved.
ERZ010056E Region abnormally terminated during

region shutdown processing.
System action:
Shutdown continues.
Explanation:
A problem occurred during CICS region shutdown, and
the region is now terminating abnormally.
User response:
None
Destination:
console.msg
ERZ010053E Unable to start a thread
Explanation:
CICS detected an error when trying to start a thread to
perform an operation.
System action:
User response:
See message ERZ1092E following this one for further
details.
Destination:
console.msg
ERZ010054I CICS self consistency checking
completed
Explanation:
CICS has successfully completed a check of the
integrity of the region. No fatal inconsistencies were
found.
System action:
The region continues.
User response:
None
Destination:
console.msg
ERZ010055E Could not allocate a Common Work
Area (CWA) from task shared memory
Explanation:
During initialization, CICS was not able to obtain the
shared memory for the CWA. This is possibly because
there is insufficient memory allocated for the task
shared pool.
System action:
User response:
Check that the MaxTSHPool value in the Region
Definition is sufficiently large. Increase the value, and
cold start the region.
System action:
User response:
Examine previous messages for the cause of the
problem.
Destination:
console.msg
ERZ010057I Performing request to terminate
Application Server serverId
Explanation:
A request has been made to terminate an application
server. This is normally associated with a request to
purge a task, or when the Application Server timed out
having not been used for the ServerIdleLimit period
defined in the Region Definition (RD). It can also occur
when the Transaction Scheduler detects that an
Application Server was unsuccessful during processing
of a request to run a transaction.
System action:
CICS terminates the Application Server.
User response:
If this message appears very regularly then the RD
value of ServerIdleLimit was possibly set to too small a
value. This causes degradation in performance if
Application Servers are constantly being created and
terminated.
Destination:
console.msg
ERZ010061E Unable to initialize processName
process
Explanation:
CICS was not able to initialize an internal process.
System action:
If the process is an Application Server (cicsas), then
CICS attempts to continue normal operation. Otherwise
User response:
Check previous messages for possible causes of this
error.
Destination:
console.msg
Destination:
console.msg
65
ERZ010062E ERZ010069E
ERZ010062E Unable to allocate region memory
Explanation:
CICS was not able to allocate region pool storage.
System action:
If CICS is trying to start a new application server
(message ERZ1019W appears after this message), the
start fails and the transaction is placed on the queue.
Otherwise, CICS abnormally terminates the region.
User response:
Destination:
console.msg
ERZ010063I Running startup program
programName
Explanation:
CICS is about to run the named startup program.
System action:
CICS runs the program.
User response:
None
Destination:
console.msg
ERZ010064E Unable to attach region shared
memory or task shared memory
Explanation:
During initialization of a CICS process, CICS was not
able to attach the required memory. There is possibly
an inconsistency in CICS data.
System action:
User response:
A user transaction possibly caused this problem. If you
want to investigate further, see if a particular transaction
is associated with the problem.
Destination:
console.msg
ERZ010065E Unable to create CICS Log Daemon
process
Explanation:
CICS was not able to create the Log Daemon process.
console.msg
ERZ010066E Unable to create CICS Recovery
Manager process
Explanation:
CICS was not able to create the Recovery Manager
process.
System action:
User response:
Check that the system is not too heavily loaded, and
that CICS has been installed correctly.
Destination:
console.msg
ERZ010067E Unable to create CICS Application
Manager process
Explanation:
CICS was not able to create the Application Manager
process.
System action:
User response:
Destination:
console.msg
ERZ010068E Process initialization unable to find
required details for process processId
Explanation:
CICS was not able to find the details required to
initialize the given internal process.
System action:
User response:
The process cannot find an entry for itself in an
initialization table. This is possibly due to inconsistency
in CICS internal data. Attempt to start the region again,
and if the problem persists, contact your support
organization.
Destination:
console.msg
System action:
ERZ010069E Usage: cicssrcdestroy [-r regionName

| -s SFSserverName | -g
ppcgwyServerName]
User response:
Explanation:
cicssrcdestroy was run with incorrect parameters. One
(and only one) of the three options must be supplied.
Destination:
System action:
66
ERZ010070E ERZ010077E
cicssrcdestroy exits.
User response:
Run cicssrcdestroy with correct parameters.
Destination:
stderr
ERZ010070E Unable to initialize Task Control Area
(TCA)
Explanation:
CICS detected an error while initializing the TCA for a
process. CICS possibly ran out of Region Pool memory.
System action:
If the process in which this problem occurs is one of the
critical region processes then CICS abnormally
terminates the region. If the process being initialized is
an Application Server then just that process is
User response:
Look for earlier messages for the cause of this problem.
Destination:
console.msg
ERZ010073E Unable to start the transaction

transId
Explanation:
CICS detected an error when attempting to run the
CICS private transaction transId.
System action:
User response:
Examine previous messages for possible causes of this
error.
Destination:
console.msg
ERZ010074E Signature of RCA inconsistent:
actualSignature
Explanation:
The data in the regions data area has been found to be
inconsistent during CICS self consistency checking.
System action:
ERZ010071E Unable to create CICS Interval Control

process
User response:
Save any dump file produced. If the problem persists
Explanation:
CICS was not able to create the Interval Control
process.
Destination:
console.msg
System action:
ERZ010075E Exception exceptionName caught
User response:
Check that CICS has been installed correctly, and that
the system is not too heavily loaded.
Destination:
console.msg
ERZ010072I Deleting subsystem and notify method
subsystemName
Explanation:
cicssrcdestroy is about to delete an entry for the
subsystem and notify method subsystemName.
System action:
cicssrcdestroy continues.
Explanation:
CICS detected an unexpected exceptional condition.
System action:
If the exception is detected in an Application Server
(cicsas) the process is terminated and CICS continues.
CICS abnormally terminates the region if the exception
is detected in any other process.
User response:
Check any messages before this one for possible
causes of the error. Save any dump file produced. If the
Destination:
console.msg
User response:
None
ERZ010077E Usage: cics [-r regionName]

[overrideAttributes]
Destination:
stderr
Explanation:
CICS was unable to start because of incorrect
command-line parameters.
System action:
CICS terminates.
User response:
67
ERZ010081E ERZ010086E
Retry the command with the correct syntax to start
CICS.
Destination:
console.msg
ERZ010081E Error reading region database for
region regionName
Explanation:
The main CICS process was not able to read the region
database details.
System action:
CICS terminates.
User response:
Check that the region directory has appropriate access
permissions. Ensure that it is owned by user cics and
has read, write and execute permissions for its owner. If
not, the region was possibly not imported successfully.
Destination:
console.msg
ERZ010082E Unable to allocate memory for startup
or shutdown program programName
Explanation:
CICS attempted to run the named program but was
unable to allocate sufficient memory to do so.
System action:
If this error occurs during startup, CICS abnormally
terminates the region. Otherwise shutdown continues.
User response:
Destination:
console.msg
ERZ010083E Startup or shutdown program
programName abnormally terminated
Explanation:
During startup or shutdown processing CICS attempted
to run the named program from the startup or shutdown
program list. This program abnormally terminated.
System action:
User response:
There is possibly a problem with the program. If the
problem happened during startup, remove the program
from the startup program list and restart the region.
Check that the program is the correct one, and also that
it is suitable to be run as a startup or shutdown
program. One way of testing that the program is
suitable is to run it using EXEC CICS START without a
TERMID option.
68
Destination:
console.msg
ERZ010084E Startup or shutdown program
programName ended with ABEND
CANCEL or ABEND ABCODE CANCEL
Explanation:
During startup or shutdown processing CICS attempted
to run the named program from the startup or shutdown
program list. This program terminated.
System action:
User response:
There is possibly a problem with the program. If the
problem happened during startup, remove the program
from the startup program list and restart the region.
Check that the program is the correct one, and also that
it is suitable to be run as a startup or shutdown
program.
Destination:
console.msg
ERZ010085E Default region directory not found
Explanation:
No region name was specified to the cicsrlck or cicsgpid
command so the default region name was used The
directory containing the region configuration for this
default region was not able to be found.
System action:
The program terminates.
User response:
If the default region name is not the region required,
retry the command specifying the required name using
-r regionName. Otherwise, check that the default region
has been correctly installed and that the region directory
exists. Check that the access permissions for the
directory are appropriate. Ensure that it is owned by
user cics and has read, write, and execute permissions
for its owner.
Destination:
stderr
ERZ010086E Region directory for region
regionName not found or not
accessible.
Explanation:
cicsrlck, cicsgpid or CICS main process was not able to
find or access the named region.
System action:
User response:
ERZ010087E ERZ010096E
Check that the region named exists. On Windows NT
you can find the drive letter of the disk containing the
cics_regions directory by using the cicsname regions
command. Check that the access permissions for the
directory are appropriate.
Destination:
stderr
ERZ010087E Region forcibly terminated during
region abnormal termination
processing
Explanation:
While the region was performing an abnormal
termination, CICS detected another abnormal
termination.
System action:
CICS forcibly terminates all region processes.
User response:
Examine previous messages for possible causes of the
problem.
Destination:
console.msg
ERZ010088E Process processId could not access
the Region Pool during a system
abnormal termination
Explanation:
During abnormal termination of a region CICS was not
able to access region memory.
System action:
If this error does not occur in the main CICS controlling
process, CICS continues the region abnormal
termination process. Otherwise, CICS forcibly
terminates all region processes.
User response:
problem.
Destination:
console.msg
ERZ010089E Application Server serverId ended
unexpectedly
Explanation:
The Application Manager (cicsam) process detected the
unexpected end of the Application Server serverId.
System action:
CICS continues.
User response:
problem.
Destination:
console.msg
ERZ010090E Process cannot access region

memory
Explanation:
CICS cannot access the region memory needed to run
the process.
System action:
CICS attempts to continue running.
User response:
problem. If previous messages indicate that this
problem has occurred during abnormal termination, no
action needs to be taken. Otherwise this message
possibly indicates an inconsistency in either CICS or
operating system data structures. Request an
immediate shutdown of the region. Save any dump
produced and contact your support organization.
Destination:
console.msg
ERZ010092E errorMessage
Explanation:
An underlying error was detected.
System action:
See the preceding message for the action that is taken.
User response:
Use the contents of this message and the details of the
previous message to decide on the response.
Destination:
console.msg
ERZ010093E The transaction transId failed
Explanation:
A CICS private transaction failed. The region cannot
startup without the transaction completing.
System action:
User response:
Examine preceding messages to determine the cause of
this problem.
Destination:
console.msg
ERZ010096E Unable to delete subsystem
subsystemName
Explanation:
cicssrcdestroy encountered an error deleting an entry
for the named subsystem.
System action:
cicssrcdestroy exits.
User response:
69
ERZ010098E ERZ010103E
Look at the previous messages for the cause of the
error.
Destination:
stderr
ERZ010098E One of the region processes,
processName, terminated abnormally
Explanation:
One of the CICS region processes terminated
abnormally.
System action:
User response:
Examine previous messages for possible causes of this
problem.
Destination:
console.msg
ERZ010099W Unable to close the restart file for
region regionName, operating system
Explanation:
CICS detected an error when attempting to close the
restart file. See message ERZ1092E following this one
for further details.
System action:
CICS continues.
User response:
Check that the directory for the named region has the
required permissions. Ensure that it is owned by user
cics and has read, write and execute permissions for its
owner. Check that the file system is not full. If the
content of ERZ1092E gives insufficient information use
the operating system error number errorNumber to
obtain more information.
Destination:
console.msg
ERZ010100I The requested shutdown will be
performed when startup is complete
Explanation:
CICS has received a request to terminate the region
while it is still performing startup. It continues with
startup, and shut down the region as soon as startup is
complete.
System action:
CICS continues startup.
User response:
Wait until startup is complete. The region then shuts
down.
Destination:
console.msg
70
ERZ010101E Process Name is inconsistent:

actualSignature
Explanation:
CICS self consistency checking detected a problem.
The name of the current process in the task area is
incorrect.
System action:
CICS continues normal operation.
User response:
This problem is possibly caused by a transaction that
has overwritten CICS internal data. Shut down the
region as soon as possible. If the value of the attribute
SafetyLevel in the Region Definitions (RD) is set to
none, set it to normal. If you want to investigate this
problem, set the value of the attribute IntrospectInterval
in the RD to 1 and restart the region. Try to determine
which transaction is causing the problem.
Destination:
console.msg
ERZ010102E Process count (processCount) does
not equal number of processes in list
(processActual)
Explanation:
The maintained count of Process IDs was found to be
different from the actual number of Process ID
structures during CICS self-consistency checking. The
maintained count has now been set to the actual
number of structures.
System action:
CICS corrects the problem and continues operation.
User response:
There is an inconsistency with CICS internal data
structures. Shut down the region as soon as possible. If
the value of the attribute SafetyLevel in the Region
Definitions (RD) is set to none, set it to normal and
restart the region. If the problem persists then it is
probably not caused by a user transaction. If you want
to investigate it, set the value of the attribute
IntrospectInterval in the RD to 1 and restart the region.
Destination:
console.msg
ERZ010103E Region name regionName is too long
Explanation:
The region name is too long, use a shorter name.
System action:
CICS terminates.
User response:
Use the correct region name. If you did not specify a
region name because you wanted to use a default
region, ensure the default region has a shorter name.
ERZ010104E ERZ010111E
Destination:
console.msg
ERZ010104E Unable to set permission of region
message log fileName, operating
system error number errorNumber
Explanation:
CICS attempts to set the permissions of the region
message log file to an appropriate value. It was unable
to perform this operation. See message ERZ1092E
following this one for further details.
System action:
CICS startup continues.
User response:
Check that the region directory is accessible and has
write permission for the user cics. If not, correct the
region directorys permissions and restart the region.
Check that there is sufficient free space in the
filesystem containing the region directory.
Destination:
console.msg
ERZ010107W Line lineNumber of the region

environment file is invalid
Explanation:
There is a syntax error in the region environment file.
System action:
CICS attempts to read the next line in the environment
file and continues startup.
User response:
Correct the line in the environment file. If the value is
required for region operation, shut down the region and
restart it. The CICS environment file must contain only
comment lines that have a # in the first column, blank
lines, and lines in the form name=value.
Destination:
console.msg
ERZ010109I Running shutdown program
programName, from shutdown
program list 1
Explanation:
CICS is about to run the shutdown program named.
ERZ010105W The region environment file is

missing
System action:
CICS continues phase 1 of shutdown.
Explanation:
The environment file in the region directory is missing.
User response:
None
System action:
CICS continues.
Destination:
console.msg
User response:
If environment settings are required, create this file. An
example environment file is provided with the default
region.
ERZ010110I Running shutdown program

programName, from shutdown program
list 2
Destination:
console.msg
Explanation:
CICS is about to run the shutdown program named.
ERZ010106E Error errorCode occurred when

changing the file permissions of the
region message log
Explanation:
CICS attempts to set the permissions of the region
message log file to an appropriate value. It was unable
to perform this operation, because the operating system
error with code errorCode occurred.
System action:
CICS startup continues.
User response:
Check that the region directory is accessible and has
write permission for the user cics. If not, correct the
region directorys permissions and restart the region.
Destination:
console.msg
System action:
CICS continues phase 2 of shutdown.
User response:
None
Destination:
console.msg
ERZ010111E Usage: cicssrccreate [ -I ] [-r
regionName | -s SFSserverName -n
serverId -u userId | -g
ppcgwyServerName -n serverId -u
userId]
Explanation:
cicssrccreate was run with incorrect parameters. One
(and only one) of the three options must be supplied.
System action:
User response:
71
ERZ010112E ERZ010119E
Run cicssrccreate with correct parameters.
Look at the previous message for the cause of the error.
Destination:
stderr
Destination:
stderr
ERZ010112E Unable to locate the CICS product

directory productDirectory
ERZ010116E Region lock file found but not the

associated process for id processName
Explanation:
cicssrccreate was unable to find the location of the
CICS product directory. The CICS product has not been
successfully installed.
Explanation:
cicsgpid discovered an existing region lock file which
contained a process id. However, on examination no
process for that pid was able to be found. This situation
has probably arisen because the region was terminated
unexpectedly during normal operation. It did not have
time to remove the region lock file.
System action:
User response:
Install the CICS product.
Destination:
stderr
ERZ010113E Region directory directoryName does
not exist
Explanation:
cicssrccreate was called to create a subsystem entry for
a region which has not been successfully created on the
current machine.
System action:
User response:
Create the region before running cicssrccreate.
Destination:
stderr
ERZ010114I Creating subsystem subsystemName
for region regionName
Explanation:
cicssrccreate is about to create a subsystem entry
subsystemName for the region regionName.
System action:
User response:
Remove the region lock file using cicsrlck.
Destination:
stderr
ERZ010117I CICS is performing a cold start
Explanation:
CICS is performing a cold start either because it was
requested or because the region is being used for the
first time.
System action:
CICS continues.
User response:
None
Destination:
console.msg
ERZ010118I CICS is performing an auto start
Explanation:
CICS is performing an auto start.
System action:
cicssrccreate continues.
System action:
CICS continues.
User response:
None
User response:
None
Destination:
stderr
Destination:
console.msg
ERZ010115E Unable to create subsystem

subsystemName
ERZ010119E Not enough memory to set up the

environment from the region
environment file
Explanation:
cicssrccreate encountered an error creating an entry for
the named subsystem.
System action:
User response:
72
Explanation:
CICS is unable to obtain enough memory to set up the
environment as required.
System action:
CICS terminates.
ERZ010120I ERZ010125E
User response:
This message possibly means that the environment file
is too large. Check that everything defined in the
environment file is required. If the size of the
environment file cannot be reduced, increase the value
of the attribute MaxRegionPool in the Region Definition.
Destination:
console.msg
ERZ010120I Completed processing startup or
shutdown program list
Explanation:
CICS has completed processing one of the startup or
shutdown program lists.
System action:
CICS continues startup or shutdown.
User response:
None
Destination:
console.msg
ERZ010121E Unable to perform operation due to a
transient error
Explanation:
A transient error occurred repeatedly while attempting
an action.
System action:
CICS terminates.
User response:
See message ERZ5723I for further information.
Destination:
console.msg
ERZ010122E The region has been forcibly
terminated
Explanation:
CICS has encountered a problem during region
termination which prevents completion of the normal
termination actions.
System action:
CICS forcibly terminates all region processes and
removes the region lock file.
User response:
Examine previous messages for the cause of the
problem.
Destination:
console.msg
ERZ010123E Unable to set the locale or open

catalogue for process processName
Explanation:
CICS was unable to set the locale or was unable to
open the message catalogue in the current locale.
System action:
CICS terminates.
User response:
Check that the locale is defined correctly, and that there
is a message catalogue available for the locale. The
locale is taken from the environment of the user which
requested the operation. The locale categories within
the locale can be modified by a number of environment
variables. Ensure these environment variables contain a
valid locale.
Destination:
console.msg
ERZ010124E Unable to save locale for the process
processName
Explanation:
Was not able to save locale.
System action:
CICS terminates.
User response:
CICS possibly ran out of memory. Check that the
Region Definition (RD) value MaxRegionPool is
sufficiently large. Increase the value, and restart the
region.
Destination:
console.msg
ERZ010125E Unable to obtain locale of the process
processName
Explanation:
CICS was unable to obtain the locale of the current
process.
System action:
CICS terminates.
User response:
which requested the operation. On UNIX the locale
categories within the locale can be modified by a
number of environment variables. Ensure these
environment variables contain a valid locale.
Destination:
console.msg
73
ERZ010128E ERZ010135I
ERZ010128E Region regionName forcibly
terminated after detection of an
unexpected exit
Explanation:
The CICS region regionName terminated abnormally,
not as a result of a system or user requested shutdown
and without completing the normal shutdown procedure.
System action:
Any remaining processes associated with the region are
terminated and the region lock file is removed.
User response:
Check the previous messages to see if there is some
reason for the region to have terminated unexpectedly.
Destination:
console.msg
ERZ010129I CICS startup id: regionStartupId
Explanation:
This message logs the unique identifier for this
instantiation of the region. The startup identifier is used
for labelling Open File Descriptors (OFD) on the SFS,
and is displayed on the console so that the system
administrator can identify any open OFDs which do not
relate to this instantiation of the region.
System action:
CICS continues.
User response:
None
Destination:
console.msg
ERZ010130I Creating subsystem subsystemName
Explanation:
cicssrccreate is about to create a subsystem entry for
the subsystem subsystemName.
System action:
User response:
None
Destination:
stderr
ERZ010131W Subsystem subsystemName, already
exists
Explanation:
cicssrccreate is not creating an entry for the subsystem
subsystemName because one already exists.
System action:
User response:
74
If you wish to force the creation of the entry for the

subsystem subsystemName, destroy the current one
using cicsdestroy and retry this operation.
Destination:
stderr
ERZ010132E Usage: cicsclck [-r regionName]
Explanation:
cicsclck was invoked with invalid arguments.
System action:
cicsclck exits.
User response:
Retry the command with the correct syntax.
Destination:
stderr
ERZ010133E Insufficient authority to create
subsystem subsystemName
Explanation:
You do not have sufficient authority to run cicssrccreate.
System action:
cicssrccreate terminates.
User response:
If you are running on an AIX platform ensure that you
have read and execute access permission for the
commands mknotify, rmnotify, and mkssys. Otherwise
ensure that you have read and execute permission for
the cicsmkssys command.
Destination:
stderr
ERZ010134E Insufficient authority to destroy
Explanation:
You do not have sufficient authority to run
cicssrcdestroy.
System action:
cicssrcdestroy terminates.
User response:
If you are running on an AIX platform ensure that you
have read and execute access permission for the
command rmssys. Otherwise ensure that you have read
and execute permission for the cicsrmssys command.
Destination:
stderr
ERZ010135I CICS region regionName is being
started with locale categories
localeName
Explanation:
ERZ010136I ERZ010144I
The region regionName has been started in locale
localeName. The locale is taken from the environment
of the user associated with the region process. The
locale consists of a number of categories. On UNIX,
these categories can be modified by using environment
variables.
ERZ010139I The CICS termination transaction has

started
Explanation:
The CICS private transaction that performs transactional
work at system shutdown has started.
System action:
System action:
CICS continues shutdown.
User response:
None
User response:
None
Destination:
console.msg
Destination:
console.msg
ERZ010136I Creating CICS process processName
ERZ010140I The CICS termination transaction has

ended
Explanation:
The CICS process processName is being created.
System action:
User response:
None
Destination:
console.msg
ERZ010137I The CICS initialization transaction has
started
Explanation:
work at system startup has begun.
System action:
User response:
None
Destination:
console.msg
ERZ010138I The CICS initialization transaction has
ended
Explanation:
work at system startup has ended.
System action:
User response:
None
Destination:
console.msg
Explanation:
work at system shutdown has ended.
System action:
User response:
None
Destination:
console.msg
ERZ010141I Application manager now starting
MinServer servers
Explanation:
The application manager has been started and is now
bringing up the number of application servers specified
by the value of the MinServer attribute in the Region
Definitions.
System action:
User response:
None
Destination:
console.msg
ERZ010144I Application server serverId started
Explanation:
Application server serverId has started running.
System action:
CICS continues.
User response:
None
Destination:
console.msg
75
ERZ010145E ERZ010151W
ERZ010145E Unable to create /var/cics_regions/
regionName/region_lock
Explanation:
The CICS command was not able to create the lock file
for the named region.
System action:
The CICS command terminates with a non-zero exit
status.
User response:
Ensure that the region exists, is owned by user cics and
has read, write and execute permissions for its owner.
Ensure that the file system is not full.
Destination:
stderr
ERZ010146E Cannot create fileName for region
regionName
Explanation:
CICS was not able to create a lock file for the named
region. A region lock file cannot be created whilst the
region is running or while a major configuration change
is being made.
Destination:
console.msg
ERZ010148E CICS self consistency checking failed
Explanation:
When checking the integrity of the region, CICS
discovered an inconsistency. Please refer to the
preceding messages for more details.
System action:
User response:
If after following the guidelines given by the preceding
messages the problem still persists save the system
dump and contact your support organization.
Destination:
console.msg
ERZ010149E User identifier for user name
userName could not be found
Explanation:
cicssrccreate was unable to obtain the user identifier for
the given user name.
System action:
the command terminates.
System action:
User response:
Retry the command when the region has been shut
down or when configuration changes are complete. Use
the contents of the lock file to discover what is
happening. A value of 999999 in the lock file indicates
that configuration is taking place, any other value
indicates that a region is running. If the region lock file
exists and no-one is running a region or configuring it,
cicsrlck can be used to remove the region lock file. If
the lock file does not exist a more serious problem has
occurred. Check that the directory for the named region
has the required permissions. Ensure that it is owned by
user cics and has read, write and execute permissions
for its owner. Ensure that the file system is not full.
User response:
The given user name must exist before cicssrccreate
can be used. Create the user and retry the command.
Destination:
console.msg
Destination:
stderr
ERZ010150E Directory directoryName is not
accessible by user userName, or it
does not exist
Explanation:
Either directoryName is not readable, writeable and
executable by userName, or directoryName does not
exist.
System action:
ERZ010147I Waiting for Application Servers to

complete
User response:
Ensure that directoryName exists and that userName
has read, write and execute permissions to it.
Explanation:
CICS is waiting for any remaining Application Servers to
complete before finally shutting down the region.
Destination:
stderr
System action:
CICS continues shutdown. If after 5 minutes on normal
shutdown and 2 minutes on immediate shutdown, the
Application Servers have not completed, any remaining
ones is forcibly terminated and region shutdown
continues.
User response:
None
76
ERZ010151W Cold start forced as previous cold

start did not complete
Explanation:
An auto start was requested but the previous cold start
did not complete. As a result a cold start is forced.
System action:
ERZ010152I ERZ010158I
User response:
None
User response:
None
Destination:
console.msg
Destination:
console.msg
ERZ010152I Usage: cicsnotify {-? |

subsystemName}
ERZ010156I About to schedule the CICS

termination transaction
Explanation:
This is the usage message for the cicsnotify command.
Explanation:
CICS is about to schedule the transaction that performs
transactional work during shutdown.
System action:
cicsnotify exits.
User response:
None. See the TXSeries for Multiplatforms
Administration Reference for more information.
Destination:
stderr
ERZ010153I Application Servers are now being
forcibly terminated
Explanation:
CICS is about to forcibly terminate any Application
Servers that have not yet completed.
System action:
User response:
None
System action:
CICS waits for up to 15 minutes for the termination
transaction to be started. The wait occurs only if there is
not an Application Server available to run the
transaction. If the transaction is not scheduled
immediately message ERZ10139I appears. If after 15
minutes the transaction has not been started shutdown
continues without the transaction having run.
User response:
An Application Server can be made available by
terminating a running transaction.
Destination:
console.msg
ERZ010157W Invalid value for registerName pool
base register - defaulting to
0xregisterValue
Destination:
console.msg
Explanation:
The value of the registerName pool base attribute in
the Region Definitions was not valid.
ERZ010154I Waiting for Application Manager to

complete
System action:
CICS takes the default value for that register, and
Explanation:
CICS has terminated all of the Application Servers and
is now waiting for the Application Manager to complete.
System action:
CICS continues shutdown. If after 2 minutes the
Application Manager has not completed it is forcibly
terminated and region shutdown continues.
User response:
If you do not want to use the default value change it to
a valid one. See TXSeries for Multiplatforms
Administration Reference.
Destination:
console.msg
User response:
None
ERZ010158I Taking override for registerName pool

base register to be 0xregisterOverride
Destination:
console.msg
Explanation:
CICS is using the RegionPoolBase or
TaskSharedPoolBase attribute specified in the Region
Definitions.
ERZ010155I Application Manager is now being

forcibly terminated
Explanation:
CICS is about to forcibly terminate the Application
Manager.
System action:
System action:
CICS continues.
User response:
None
Destination:
77
ERZ010159W ERZ010165I
console.msg
ERZ010159W Override for registerName pool base
register not valid on this platform
Explanation:
CICS has detected that you have changed the value for
attribute registerName in Region Definitions (RD), but
this attribute is used on AIX platforms only.
System action:
CICS ignores the override and continues processing.
User response:
Do not specify this attribute in the RD. See TXSeries for
Multiplatforms Administration Reference.
Destination:
console.msg
ERZ010160I Creating CICS process processName
for listener listenerName
Explanation:
The CICS process processName is being created for
the protocol listener listenerName.
System action:
User response:
None
Destination:
console.msg
Check that CICS has been installed correctly. If the

system is heavily loaded, reduce the load by stopping
some processes or by restricting the maximum number
of Application Servers by updating the value of the
attribute MaxServer in the Region Definition.
Destination:
console.msg
ERZ010163I Waiting for listener listenerName to
initialize
Explanation:
CICS is waiting for initialization of the listener identified
by the protocol listener listenerName.
System action:
None
User response:
None
Destination:
console.msg
ERZ010164W SNA Listener Definition listenerName
ignored
Explanation:
CICS has initiated the SNA listener from the first SNA
protocol Listener Definition. A further SNA Listener
Definition listenerName exists which has been ignored.
System action:
Explanation:
CICS cannot access the Listener Definitions (LD) for
protocol listener listenerName.
User response:
Delete multiple SNA Listener Definitions to eliminate this
startup message. The resource definition can be deleted
by using the cicsdelete command. Refer to TXSeries for
Multiplatforms Administration Reference for more
information.
System action:
Destination:
console.msg
User response:
Examine surrounding messages in the message file for
possible causes.
ERZ010165I CICS control process processName

terminated abnormally
ERZ010161E Access to Listener Definition record

listenerName was unsuccessful
Destination:
console.msg
ERZ010162E Unable to create CICS process
processName for listener
listenerName
Explanation:
CICS was not able to create the process processName
for the protocol listener listenerName.
System action:
User response:
78
Explanation:
One of the CICS control processes terminated
abnormally. Preceding messages possibly indicate the
cause of the abnormal termination.
System action:
If the process that is terminating abnormally is not an
application server, the region also terminates
abnormally.
User response:
Examine preceding messages to identify the cause of
the abnormal termination.
Destination:
console.msg
ERZ010166I ERZ010173I
ERZ010166I About to set the DB2INSTANCE
environment variable to instanceName.
ERZ010170I Listener manager now starting

recovery listeners
Explanation:
The value of the environment variable DB2INSTANCE is
set to the value of the RDBMSInstance attribute in the
Region Definition (RD).
Explanation:
The Listener Manager has been started and is now
starting any listeners which have been defined to start
before recovery.
System action:
System action:
User response:
None
User response:
None
Destination:
console.msg
Destination:
console.msg
ERZ010167I Region Region has been configured to

support a Structured File Server(SFS).
ERZ010171I Listener manager started ListenerCount

recovery listeners
Explanation:
Region Region supports an SFS file system.
Explanation:
The Listener Manager has started ListenerCount
recovery listeners.
System action:
User response:
None
Destination:
console.msg
support a Database 2 FileSystem
Explanation:
Region Region supports a Database 2 FileSystem.
System action:
User response:
None
Destination:
console.msg
ERZ010169E Unable to create CICS Listener
Manager process
System action:
User response:
None
Destination:
console.msg
ERZ010172I Listener manager now starting
non-recovery listeners
Explanation:
The Listener Manager has been started and is now
starting any listeners which have been defined to start
following recovery.
System action:
User response:
None
Destination:
console.msg
Explanation:
CICS was not able to create the Listener Manager
process.
ERZ010173I Listener manager started listenerCount

non-recovery listeners
System action:
Explanation:
The Listener Manager has started listenerCount
non-recovery listeners.
User response:
System action:
Destination:
console.msg
User response:
None
Destination:
console.msg
79
ERZ010174E ERZ010180E
ERZ010174E CICS listener listenerName process
processName ended unexpectedly
Explanation:
The Listener Manager (cicslm) process detected the
unexpected end of the identified CICS listener process.
System action:
CICS continues.
User response:
problem.
Destination:
console.msg
ERZ010175I CICS listener listenerName process
processName terminated
Explanation:
The identified CICS listener process has terminated and
is no longer available for use.
System action:
User response:
None
Destination:
console.msg
ERZ010176E Listener child process (pid=childPid)
terminated unexpectedly
Explanation:
The Listener Manager process (cicslm) detected the
unexpected termination of a listener child process with
pid childPid.
System action:
console.msg
ERZ010178E Unable to allocate region memory
when attempting to start a listener
process
Explanation:
The Listener Manager process (cicslm) failed to allocate
region pool storage when attempting to start a listener
process.
System action:
User response:
Examine previous messages and symptom records for
possible causes of the problem. Consider increasing the
size of the region pool.
Destination:
console.msg
ERZ010179E The Listener Manager received an
invalid request type (RequestType)
Explanation:
The Listener Manager process (cicslm) has received an
invalid request with value of RequestType. This is an
internal error.
System action:
CICS terminates the region.
User response:
Save the console output and any dump produced and
Destination:
console.msg
ERZ010180E Unable to find region regionName
User response:
Examine previous messages and symptom records for
possible causes of the problem.
Explanation:
The CICS command tried to do some work in
varDir/cics_region/regionName but was unable to find
the directory.
Destination:
console.msg
System action:
The command terminates abnormally.
ERZ010177I Listener child process (pid=childPid)

terminated
Explanation:
The Listener Manager process (cicslm) detected the
termination of a listener child process with pid childPid.
The process is unavailable for further use.
System action:
User response:
None.
Destination:
80
User response:
Ensure that the region exists, is owned by user cics and
has read, write and execute permissions for its owner.
Ensure also that you have installed CICS correctly. If
you did not specify a region with the command, ensure
that the cics default region exists. On Windows NT you
can find the drive letter of the disk containing the
command.
Destination:
stderr
ERZ010181E ERZ010186I
ERZ010181E Unable to write file fileName, errno
errno
Explanation:
The cics command attempted to create and then write
to file fileName, but the command failed with errno
errno.

support an Oracle database as its
FileSystem
Explanation:
Region Region has been configured to map file control
and queue management to an Oracle database.
System action:
System action:
User response:
Check you have the necessary permissions to create
and write to the file in the regions directory. Check also
that the file system is not full. If this fails then check
errno for more information. Then retry the command.
User response:
None
Destination:
stderr
ERZ010182E Unable to close file fileName
Explanation:
CICS tried to close the file fileName but was unable to
do so. This is possibly because the file has been
corrupted or because a spurious signal interrupted the
process.
System action:
User response:
Try the command again. If the problem persists check
the installation of the CICS system.
Destination:
console.msg
ERZ010185E The region has been configured to
use DB2 as its FileSystem but CICS
could not determine the database
instance
Explanation:
The CICS regions has been configured to use DB2 for
its file and queue management but both the
DB2INSTANCE environment variable and the
RDBMSInstance field in the RD stanza are empty. CICS
cannot determine which database instance is to be
used for its file system.
System action:
CICS abnormally ends the region.
Destination:
stderr
User response:
Determine which database instance is to be used for
the CICS file control and queue management and set
this value in the RDBMSInstance field in the RD stanza
or in the DB2INSTANCE environment variable.
ERZ010183E This copy of CICS is not licensed and

is shutting down, reason code:
reasonCode
Destination:
console.msg
Explanation:
The CICS License Manager has not been able to find a
valid license for this copy of CICS. This means that
CICS cannot continue to execute and must shut down
immediately.
System action:
The region terminates abnormally.
User response:
Check the message log for further messages indicating
the nature of the problem. If this is an Evaluation copy
of CICS, then it is only licensed for a limited period.
Contact your support organization if you require help
with licensing this system. If this is a Production copy of
CICS, ensure that the Production license is enrolled.
Refer to documentation for further information.
ERZ010186I The region will use DB2 instance

instanceName
Explanation:
The CICS regions has been configured to use DB2 for
its file and queue management and has determined
from the DB2INSTANCE environment variable, that the
DB2 instance to use is instanceName.
System action:
User response:
Check that CICS is using the correct DB2 instance.
Destination:
console.msg
Destination:
console.msg
81
ERZ010187I ERZ010193W
ERZ010187I About to set the ORACLE_SID
environment variable to instanceName.
ERZ010190I CICS Release Number versionNumber

Revision Level revisionLevel
Explanation:
The value of the environment variable ORACLE_SID is
set to the value of the RDBMSInstance attribute in the
Explanation:
The CICS region is starting, using code from CICS
release versionNumber which is at revision level
revisionLevel.
System action:
User response:
None
User response:
None
Destination:
console.msg
Destination:
console.msg
use Oracle as its FileSystem but CICS
could not determine the database
instance
Explanation:
The CICS regions has been configured to use Oracle
for its file and queue management but both the
ORACLE_SID environment variable and the
RDBMSInstance field in the RD stanza are empty. CICS
cannot determine which database instance is to be
used for its file system.
System action:
User response:
Determine which database instance is to be used for
the CICS file control and queue management and set
this value in the RDBMSInstance field in the RD stanza
or in the ORACLE_SID environment variable.

use Oracle as its FileSystem but CICS
could not determine the value for
ORACLE_HOME
Explanation:
The CICS region has been configured to use Oracle for
its file and queue management but the ORACLE_HOME
environment variable was not defined. CICS cannot
determine which database is to be used for its file
system.
System action:
User response:
Determine which database home is to be used for the
CICS file control and queue management, then export
the ORACLE_HOME environment variable or define
ORACLE_HOME in the CICS regions environment file.
Destination:
console.msg
Destination:
console.msg
ERZ010192W LU0 Listener Definition listenerName

ignored
ERZ010189I The region will use variable

variableName defined as
variableSetting
Explanation:
CICS has initiated the LU0 listener from the first LU0
protocol Listener Definition. A further LU0 Listener
Definition listenerName exists which has been ignored.
Explanation:
The CICS regions has been configured to use Oracle
for its file and queue management and has determined
from the environment that variableName is defined as
variableSetting.
System action:
User response:
Check that CICS is using the correct value for
variableName.
Destination:
console.msg
System action:
User response:
Delete multiple LU0 Listener Definitions to eliminate this
startup message. The resource definition can be deleted
by using the cicsdelete command. Refer to TXSeries for
information.
Destination:
console.msg
ERZ010193W IIOP Listener Definition listenerName
ignored
Explanation:
82
ERZ010194E ERZ010198E
An IIOP Listener Definition listenerName exists which
has been ignored, because an IIOP Listener has
already been started.
System action:
User response:
Delete this Listener Definition to eliminate this startup
message. Only one IIOP Listener and one IIOP SSL
supported Listener definition can exist within a CICS
region. The resource definition can be deleted by using
the cicsdelete command. Refer to TXSeries for
information.
Destination:
console.msg
ERZ010194E IIOP Listener Definition error
Explanation:
CICS has initiated an IIOP listener with SSL support
from an IIOP protocol Listener Definition, but is unable
to find a IIOP Listener Definition without SSL support.
System action:
CICS abnormally terminates the region with abend code
U1037.
User response:
If you require IIOP with SSL support, you must also
define an IIOP Listener without SSL support. The
resource definition can be added by using the
cicsdelete command. Refer to TXSeries for
information.
Destination:
console.msg
ERZ010195E IIOP Listener Definition listenerName
ignored
Explanation:
CICS has detected an IIOP protocol Listener Definition,
but this listener type is not supported for this operating
system. Listener Definition listenerName has been
ignored.
System action:
User response:
message. The resource definition can be deleted by
using the cicsdelete command. Refer to TXSeries for
information.
Destination:
console.msg
ERZ010196E IIOP SSL Listener Definition

listenerName ignored
Explanation:
CICS has detected an IIOP protocol Listener Definition
which requires SSL support, but this is not supported for
this operating system. Listener Definition listenerName
has been ignored.
System action:
User response:
message. The resource definition can be deleted by
using the cicsdelete command. Refer to TXSeries for
information.
Destination:
console.msg
ERZ010197E IIOP SSL Listener cannot be
supported with IIOP version 1.0
Explanation:
An IIOP SSL Listener Definition is defined but the IIOP
version for generated object references is set to 1.0.
IIOP version 1.0 does not support transmission of
security component identifiers and is therefore unable to
negotiate the use of SSL on IIOP flows. If an IIOP SSL
Listener is required, the Region Definition attribute
IIOPObjrefsVersion must be set to 1.1 to enable
security component identifier support on IIOP flows.
System action:
U1038.
User response:
Define the IIOP version for generated object references
to 1.1 if you require an IIOP SSL Listener. Refer to
more information.
Destination:
console.msg
ERZ010198E IIOP work load managed SSL
configuration error
Explanation:
An IIOP work load managed SSL port is defined but no
IIOP SSL Listener has been defined for this region. The
Region Definition attribute IIOPGroupSSLPort defines
the IIOP work load managed SSL port.
System action:
U1039.
User response:
Define an IIOP SSL Listener if you intend to support an
IIOP work load managed SSL configuration. Refer to
83
ERZ010199I ERZ011001E
more information. Otherwise, unset the Region
Definition attribute IIOPGroupSSLPort.
Destination:
console.msg
None.
Destination:
console.msg
ERZ010199I CICS Interim Fix interimfixes detected
ERZ010204E Peer listener listenerName failed to

autoinstall
Explanation:
The Interim Fix that is listed in the message is installed.
Explanation:
The listener could not be autoinstalled.
User response:
None
System action:
CICS terminates.
Destination:
console
User response:
See previous messages for possible autoinstall failure
reasons.
ERZ010200I CICS observed an increase in the size

of the data segment for application
server serverId. The current data
segment size is MemSizeCur
Destination:
console.msg
Explanation:
Memory usage for a given application server has
increased.
System action:
User response:
Examine previous messages, symptom records and
running applications for possible causes of the problem.
Destination:
console
ERZ010201I Monitoring of the data segment is
enabled for application server
processes with
ServerMemCheckInterval=
ServerMemCheckInterval and
ServerMemCheckLimit=
ServerMemCheckLimit
Explanation:
Memory growth monitoring is switched on.
System action:
User response:
None
Destination:
console
ERZ010203I Region is configured to use EAM
module for authentication
Explanation:
The region configuration shows that an External
Authentication Module should be loaded by CICS to
perform user authentication.
System action:
CICS continues.
User response:
84
ERZ010205I CICS diagnostic patch diagpatch

detected
Explanation:
The diagnostic patch that is listed in the message is
installed.
System action:
User response:
None
Destination:
console
ERZ010206W Supported JDK Version is not
installed in this machine
Explanation:
JDK Version supported for this release is not installed
on this machine.
System action:
User response:
Check whether JDK Version installed on this machine
and the Supported Java Version for this release of CICS
matches.If not install the JDK version specified in the
CICS Supported Operating Environment Page.
Destination:
console
ERZ011001E Access to terminal record for terminal
termId was unsuccessful.
Explanation:
CICS cannot access the Terminal Definitions (WD)
record for terminal termId.
System action:
The transaction terminates with abend code A11W.
User response:
ERZ011002E ERZ011008W
possible causes.
Destination:
CSMT
ERZ011002E Storage allocation request from Task
Private Pool was unsuccessful.
Explanation:
CICS is short of Task Private storage and a storage
allocation request was unable to be satisfied.
System action:
The transaction is terminated with abend code A11M.
User response:
Try running the transaction again. If the transaction is
still unsuccessful, this is possibly because another
transaction is using a lot of storage. Ask the System
Administrator to check for any such transactions.
Destination:
CSMT
ERZ011003I Processing terminal installation
request for netname netName from
user userName on host hostName.
Explanation:
CICS has started to install the terminal with netname
netName on behalf of user userName.
System action:
Terminal installation continues.
User response:
None
ERZ011005I Terminal termId does not exist.

Explanation:
A request to stop a transaction on terminal termId was
rejected because the terminal does not exist. The
terminal was uninstalled after the request to stop the
transaction was made, but before the request was
scheduled.
System action:
CICS ignores the stop request.
User response:
None
Destination:
CSMT
ERZ011006E Terminal process does not support
size specified in terminal definition
deviceName
Explanation:
The terminal process attempting to connect to the
region does not support the terminal size included in the
selected terminal definition.
System action:
The install fails.
User response:
Either use a more recent level of the terminal
executable or connect to the region using a different
model identifier or netname.
Destination:
CSMT
Destination:
CSMT
ERZ011007I Terminal termId installation complete

for user userName, netname
netName.
ERZ011004I Processing terminal installation

request for device type deviceType
from user userName on host
hostName using device devId.
Explanation:
A terminal defined in the Terminal Definitions (WD) has
connected to the region and successfully installed.
Explanation:
CICS has started to autoinstall a terminal with device
type deviceType on behalf of user userName.
System action:
Terminal installation continues.
User response:
None
Destination:
CSMT
System action:
CICS can communicate with the terminal.
User response:
None
Destination:
CSMT
ERZ011008W Terminal termId was unable to save
terminal details to Temporary Storage
Queue (TSQ) TSQname.
Explanation:
Terminal termId was successfully installed, but was
unable to save its details to TSQ TSQname to enable
the terminal definition to be recovered in the event of
abnormal shutdown. This can possibly occur if terminals
are installed while CICS is checking that existing
85
ERZ011009E ERZ011015E
terminals are still active. If this is the case, the problem
is likely to affect only terminal installations performed
within the next few moments.
Destination:
CSMT
System action:
The installation completes successfully, but the terminal
is not recovered if an abnormal shutdown occurs.
ERZ011012I Terminal termId with netname

netName has been uninstalled.
User response:
Check that the file server is available, and the file used
for recoverable TSQs exists on the server. If recovery of
the terminal is required, sign the terminal off and
attempt the connection again after a short delay.
Destination:
CSMT
ERZ011009E Unable to autoinstall terminal for
device type deviceType.
Explanation:
A terminal has connected to the region and made an
unsuccessful attempt to autoinstall.
System action:
The installation operation terminates abnormally.
User response:
Examine the previous messages to determine why the
autoinstall was unsuccessful.
Destination:
CSMT
ERZ011010I Terminal termId autoinstall complete
for user userName, netname
netName, model modelId.
Explanation:
A terminal has connected to the region and was
successfully autoinstalled.
System action:
User response:
None
Destination:
CSMT
ERZ011011E Uninstall of terminal termId was
unsuccessful.
Explanation:
A terminal has disconnected from the region but the
uninstall was unsuccessful.
System action:
The transaction terminates abnormally. CICS ceases to
communicate with the terminal.
User response:
Examine previous messages to determine why the
terminal was unable to be installed.
86
Explanation:
A terminal has disconnected from the region.
System action:
CICS ceases to communicate with the terminal. The
terminal client terminates.
User response:
None
Destination:
CSMT
ERZ011013E Initialization for terminal termId was
unsuccessful.
Explanation:
CICS was unable to initialize the CICS terminal
component.
System action:
CICS terminates abnormally the region with code
U1101.
User response:
Examine previous messages to see if region is short of
storage.
Destination:
CSMT
ERZ011014E Storage allocation request from Task
Shared Pool was unsuccessful.
Explanation:
CICS is short of Task Shared storage and a storage
System action:
If this occurs during region initialization, then the region
terminates abnormally; otherwise the transaction
continues, but the terminal initialization operation was
unsuccessful.
User response:
Destination:
CSMT
ERZ011015E Failure in Remote Procedure Call to
installing terminal: errorText.
Explanation:
ERZ011016E ERZ011021E
CICS has processed a request to install a terminal but a
failure has occurred when responding to the terminal
process that made the request. The reason for the
failure is given in errorText.
ERZ011018I Processing terminal autoinstall request

from user userName on host
hostName.
System action:
Terminal installation terminates abnormally.
Explanation:
CICS has started to autoinstall a terminal on behalf of
user userName.
User response:
Check the reason for the failure specified in errorText
and correct the problem. If the failure was caused by an
communication timeout, try again when the system is
less busy. If the problem persists, please report details
to your support organization.
Destination:
CSMT
System action:
Terminal autoinstall continues.
User response:
None
Destination:
CSMT
ERZ011019E ... termId not recovered.
ERZ011016E Terminal termId with netname

netName is out of service.
Explanation:
The user has tried to install a terminal with netname
netName, but its Terminal Definition (WD) is marked as
out of service.
System action:
Terminal installation terminates with abend code A11T.
User response:
Try installing using another netname or use the CEMT
transaction to set the terminal back in service.
Destination:
CSMT
ERZ011017E No terminal model for device type
deviceType.
Explanation:
A terminal with TERM=deviceType has attempted to
autoinstall, but was unsuccessful because there are no
terminal models defined in the Terminal Definitions (WD)
with DevType=deviceType. The device type is obtained
from the -m option on the cicsterm command, from the
CICSTERM or TERM environment variables.
System action:
Autoinstall terminates with abend code A11N.
User response:
Retry the command specifying a device type that
matches the DevType entry in the Terminal Definitions
(WD), or add an entry to the WD to match the device
type specified. See the TXSeries for Multiplatforms
Destination:
CSMT
Explanation:
CICS is performing an automatic start and cannot
recover the Terminal Definition (WD) for terminal termId
from a Temporary Storage Queue.
System action:
CICS automatic start continues, but the terminal is not
recovered.
User response:
for recoverable TSQs exists on the server.
Destination:
CSMT
ERZ011020E Unable to generate unique netname for
terminal autoinstall.
Explanation:
A terminal has connected to the region and attempted
to autoinstall, but was unsuccessful because CICS was
unable to generate a unique netname. This is only likely
to occur when a very large number of terminals are
defined in the Terminal Definitions (WD) or have
autoinstalled to the region.
System action:
Autoinstall terminates abnormally.
User response:
Examine the WD and use CEMT inquire terminal to
determine how many terminals are connected to the
region. Delete any unwanted definitions and try again.
Destination:
CSMT
ERZ011021E Terminal installation for netname
netName was unsuccessful.
Explanation:
A terminal has connected to the region but was unable
to be installed using netname netName.
System action:
87
ERZ011022E ERZ011027E
CSMT
User response:
Examine the previous messages in the message file to
determine why the installation was unsuccessful.

netName is a printer.
Destination:
CSMT
ERZ011022E Netname netName does not exist in
the Terminal Definitions (WD).
Explanation:
to be installed using netname netName because there
is no terminal definition with netname netName in the
WD.
System action:
Terminal installation terminates with abend code A11F.
User response:
Add an entry to the WD or install the terminal using a
terminal definition already defined in the WD.
Destination:
CSMT
netName defines an autoinstalled or
surrogate terminal.
Explanation:
to be installed using netname netName because this
netname is in use by an autoinstalled terminal or by a
surrogate terminal.
Explanation:
to be installed using netname netName because the
Terminal Definition (WD) for this netname defines a
printer.
System action:
Terminal installation is terminated with abend code
A11P.
User response:
Retry the command specifying the netname of a WD
entry that defines a terminal or change the WD entry for
this netname to define a terminal instead of a printer.
Destination:
CSMT
netName is already installed.
Explanation:
to be installed using netname netName because a
terminal is already installed using this netname.
System action:
Terminal installation terminates with abend code A11B.
User response:
Install using either a different netname, no netname, or
a model name.
System action:
Destination:
CSMT
User response:
Install using a different netname or investigate why the
netname is being used by an autoinstalled terminal or
surrogate terminal.

netName is in use by a transaction
that is being purged.
Destination:
CSMT
netName is a remote terminal.
Explanation:
to be installed using netname netName because the
remote terminal.
System action:
User response:
Install using a different netname or modify the WD to
define the termid as a local terminal.
Destination:
88
Explanation:
to be installed using netname netName because a
terminal is already installed using this netname.
However, the transaction using this terminal was
requested to complete.
System action:
Terminal installation terminates with abend code A11B.
User response:
Allow time for the transaction to complete and then try
again.
Destination:
CSMT
ERZ011028E ERZ011036E
ERZ011028E CICS was unable to run autoinstall
user-exit program.
Explanation:
A terminal autoinstall or uninstall operation cannot run
the autoinstall user-exit program.
System action:
Autoinstall/uninstall terminates with abend code A11U.
User response:
Check that the CICS private transaction CHAT is
defined in the Transaction Definitions (TD), and that the
corresponding program is defined in the Program
Definitions (PD), exists at the pathname specified and is
executable by CICS.
Destination:
CSMT
ERZ011029E Bad terminal model modelName has
been selected.
Explanation:
The autoinstall user-exit program has selected a
terminal model that was not in the list supplied to it.
System action:
Terminal installation terminates with abend code A11U.
User response:
If this installation of CICS has replaced the autoinstall
user-exit program, check the program for coding errors;
otherwise report the problem to your support
organization.
Destination:
CSMT
ERZ011030E Terminal model modelName has been
deleted from Terminal Definitions (WD).
Explanation:
The terminal model modelName selected by the
autoinstall user-exit program was deleted from the
Terminal Definitions (WD).
System action:
Terminal autoinstall terminates with abend code A11U.
User response:
Try again. Someone possibly deleted the terminal model
modelName from the Terminal Definitions (WD) while
you were attempting to autoinstall.
Destination:
CSMT
ERZ011031E Sense code senseCode received from
terminal termId.
Explanation:
The terminal has received a bad 3270 data stream and
has returned a sense code to the region.
System action:
CICS continues processing. The terminal rejects the
remainder of the data stream.
User response:
Check that the datastream sent to terminal does not
contain any unsupported or illegal 3270 commands and
that all buffer addresses are in range of the screen size.
Destination:
CSMT
ERZ011032E Terminal autoinstall rejected by
user-exit program.
Explanation:
A terminal has connected to the region and attempted
to autoinstall, but was rejected by the autoinstall
user-exit program.
System action:
Terminal autoinstall terminates abnormally.
User response:
If this installation of CICS has replaced the autoinstall
user-exit program, investigate why the autoinstall was
rejected; otherwise report the problem to your support
organization.
Destination:
CSMT
ERZ011035E Terminal termId is set to reject
Automatic Transaction Initiation (ATI)
requests.
Explanation:
A request to run an ATI job on terminal termId was
rejected because the terminal is set to reject ATI
requests.
System action:
CICS continues without running the transaction.
User response:
Either use CEMT to enable the terminal to initiate ATI
requests, or run the transaction against another
terminal.
Destination:
CSMT
ERZ011036E Terminal termId is not installed.
Explanation:
CICS tried to start an Automatic Transaction Initiation
(ATI) job but was unsuccessful because terminal
termId is defined in the Terminal Definitions (WD), but
was not installed.
System action:
CICS continues and runs the transaction when the
terminal is installed.
User response:
89
ERZ011037E ERZ011044I
Install the terminal, and the ATI request runs.
Destination:
CSMT
ERZ011037E CICS could not contact terminal
termId.
Explanation:
CICS tried to start an Automatic Transaction Initiation
(ATI) job but was unsuccessful because it was unable to
communicate with terminal termId.
System action:
ERZ011040W CICS was unable to delete Temporary

Storage Queue TSQname when
uninstalling terminal termId.
Explanation:
A terminal has successfully uninstalled, but was unable
to delete the Temporary Storage Queue (TSQ)
TSQname that holds details allowing the terminal
definition to be recovered following abnormal shutdown.
System action:
The uninstall completes successfully, but if the TSQ
exists, the system attempts to recover the terminal
definition following abnormal shutdown.
User response:
Use CEMT to purge the terminal and then reinstall it.
User response:
Destination:
CSMT
Destination:
CSMT
ERZ011038E CICS was unable to start transaction

transId against terminal termId for
user userId .
ERZ011042E Storage allocation request from Region

Pool was unsuccessful.
Explanation:
An Automatic Transaction Initiation (ATI) request for
transaction transId on terminal termId was rejected.
System action:
User response:
Examine the previous messages in the message file for
more information about this condition.
Destination:
CSMT
ERZ011039W CICS was unable to write its terminal
details to the Temporary Storage
Queue TSQname for terminal termId.
Explanation:
Terminal termId has successfully installed, but was
unable to save its details to the first record of the
Temporary Storage Queue (TSQ) TSQname. This
record is normally used to enable the terminal definition
to be recovered following abnormal shutdown.
System action:
The installation completes successfully, but the wrong
terminal details are recovered following abnormal
shutdown.
Explanation:
CICS is short of Region storage and a storage
System action:
If this occurs during region initialization, then the region
terminates abnormally; otherwise the transaction
continues, but the terminal initialization operation was
unsuccessful.
User response:
Destination:
CSMT
ERZ011043I Terminal recovered after region restart.
Explanation:
CICS was autostarted and has successfully reattached
to your terminal. The terminal is again ready for use.
System action:
None
User response:
None
User response:
Destination:
stderr
Destination:
CSMT
ERZ011044I Attempting to recover terminal

termId...
Explanation:
90
ERZ011045I ERZ011053E
CICS is performing an auto-start and is attempting to
reattach the specified terminal. If the terminal no longer
exists, there is a short delay until the attempt to contact
it times out.
System action:
CICS attempts to contact the terminal.
ERZ011050I Usage: cicslterm [-?] [-r regionName]

[-n netName] [-m modelId] [-t
transaction] [-A animatortty] [-T
animatorTERM] [-h hostList]
User response:
None
Explanation:
cicsterm was invoked with incorrect arguments. This
message gives a summary of the options available. It
can also be produced by giving the -? option.
Destination:
CSMT
System action:
cicsterm terminates.
ERZ011045I ... termId recovered successfully.
User response:
Invoke cicsterm with correct parameters. See the
more information.
Explanation:
CICS is performing an automatic start and has
successfully reattached the terminal.
System action:
Automatic start continues.
User response:
None
Destination:
CSMT
ERZ011046W ... termId timed-out -- terminal not
recovered.
Explanation:
CICS is performing an automatic start and has not
received any response from the terminal.
System action:
The terminal is not recovered. Automatic start continues.
User response:
None
Destination:
CSMT
ERZ011047W ... termId data unavailable -- recovery
postponed.
Explanation:
CICS is performing an automatic start and cannot
access the Temporary Storage Queue containing the
terminal recovery data. Terminal recovery is postponed
until an Automatic Transaction Initiation (ATI) request is
processed for the terminal.
Destination:
stderr
ERZ011051I Usage: cicstermp [-?] -r regionName -n
netName [-f font] [-M paperType] [-p
printerType] [-P printCommand] [-R] [-s
fontSize] [-t transaction] [-h hostList]
[-S]
Explanation:
cicstermp was invoked with incorrect arguments. This
message gives a summary of the options available. It
can also be produced by giving the -? option.
System action:
cicstermp terminates
User response:
Invoke cicstermp with correct parameters. See the
more information.
Destination:
stderr
ERZ011052E Illegal option -optionName.
Explanation:
The option -optionName is not valid.
System action:
cicsterm/cicstermp terminates.
User response:
Issue the command with correct parameters as shown
in the following usage message.
System action:
Terminal recovery is postponed. Automatic start
continues.
Destination:
stderr
User response:
None
ERZ011053E cicstermp requires both -n netName

and -r regionName parameters.
Destination:
CSMT
Explanation:
cicstermp was invoked without specifying the mandatory
parameters -n netName and -r regionName.
91
ERZ011054E ERZ011060I
System action:
cicstermp terminates.
User response:
Invoke cicstermp with both the -n and -r options. See
the TXSeries for Multiplatforms Administration
Reference for more information.
ERZ011057E Unrecognized binding name in

3270keys file.
Destination:
stderr
Explanation:
cicsterm is processing the 3270keys file (or one loaded
from it) and has encountered the keyword bind, followed
by the binding name that is not a valid binding name.
Valid bindings include: delete, down, eraseeof, enter
and high_prot.
ERZ011054E Display area is too small for menu.
System action:
Explanation:
cicsterm requires a minimum screen depth of 12 lines to
display the region menu.
User response:
Correct the 3270keys file containing the unrecognized
binding.
System action:
Destination:
stderr
User response:
Increase the size of the display area.
Destination:
stderr
ERZ011055E Could not read 3270keys file keysFile
while processing topKeysFile.
Explanation:
cicsterm was processing the 3270keys file topKeysFile
but either was unable to read the 3270keys file
keysFile or opening that file exceeded the maximum
file nesting limit.
System action:
User response:
Check that the file exists and is readable; also ensure
that no load statement in this file (or in previous files
that were possibly loaded from keys file) specifies a file
that was already loaded, as this recursion causes the
maximum nesting depth to be exceeded.
Destination:
stderr
ERZ011056E Unrecognized keyword keyword in
3270keys file.
Explanation:
from it) and has encountered the keyword keyword that
is not valid. Valid keywords are: bind, load, print, if and
else.
System action:
cicsterm terminates
User response:
keyword.
Destination:
stderr
92
ERZ011058E The option -option requires an

argument.
Explanation:
A required argument was not supplied for the option
-option.
System action:
User response:
Add the required argument.
Destination:
stderr
ERZ011059E cicslterm initialization was
unsuccessful.
Explanation:
cicsterm or cicstermp was unable to initialize due to
memory allocation or operating system call failure.
System action:
User response:
Ensure that cicssetupclients was run and that there is a
valid keytab file in varDir/cics_clients.
Destination:
stderr
ERZ011060I Searching for available regions. Please
wait.
Explanation:
cicsterm is waiting for a list of regions before it displays
the region menu.
System action:
cicsterm continues to search for available regions.
User response:
Wait until the region menu appears or an error message
is issued.
ERZ011061E ERZ011067E
Destination:
stderr
User response:
color.
ERZ011061E No regions available.
Destination:
stderr
Explanation:
cicsterm was unable to find any available regions.
System action:
User response:
Ensure that at least one region is running and check the
region startup messages to see if any problems were
encountered trying to register the region with the
nameservice.
Destination:
stderr
ERZ011062I Connecting to region regionName.
Explanation:
cicsterm or cicstermp has started to connect to region
regionName.
System action:
cicsterm/cicstermp continues connecting to the region.
User response:
Wait until connection is successful or until an error
message is issued.
Destination:
stderr
ERZ011063E Connection to region regionName was
unsuccessful - reason.
Explanation:
cicsterm was attempting to contact the region
regionName, but was unsuccessful for the given
reason.
System action:
User response:
Ensure that the region exists and is running.
Destination:
stderr
ERZ011064I Unrecognized color color in 3270keys
file.
Explanation:
from it) and has encountered a binding that it expects to
be followed by a color. However color is not a valid
color. Valid colors are: black, blue, brown, cyan, green,
magenta, red and white.
System action:
cicsterm continues using the default color.
ERZ011065I No help available about subject.

Explanation:
cicsterm has received a request from the attached CICS
transaction to display help on the subject subject, but
cicsterm cannot obtain the requested help from the
information subsystem.
System action:
cicsterm continues processing.
User response:
Check that the CICS information subsystem is installed
on the machine running cicsterm.
Destination:
stderr
ERZ011066E Transaction transId rejected - reason.
Explanation:
The transaction transId was submitted to the
Transaction Scheduler (TS), but the TS rejected the
request for the reason given in reason.
System action:
CICS does not run the transaction. The terminal is
ready to submit another transaction.
User response:
Check that you entered the correct transaction name.
Check that transaction transId is correctly defined in
the Transaction Definitions (TD). Also check other
messages for signs of problems with the TS.
Destination:
stderr
ERZ011067E The transaction transId has terminated
with abend code abendCode.
Explanation:
The transaction transId has terminated abnormally.
System action:
The transaction terminates abnormally. If the transaction
that abended was the CHAT transaction, then the
terminal installation fails and the terminal is not
connected to CICS. If any other transaction abends, the
terminal is ready to submit another transaction.
User response:
Check CICS documentation or the transaction
documentation for the meaning of the abnormal
termination code.
Destination:
stderr
93
ERZ011068E ERZ011080E
ERZ011068E Cannot list available Regions - reason.
Explanation:
cicsterm is unable to get a list of available regions from
the name service for the reason given in reason.
System action:
User response:
Ensure that you have the required permissions.
Destination:
stderr
ERZ011070I cicslterm terminated (region
shutdown).
Explanation:
cicsterm or cicstermp has terminated because the
region is being shut down.
System action:
CICS continues to shut down; cicsterm/cicstermp
terminates.
User response:
Wait for the region to be restarted or connect to another
region.
Destination:
stderr
ERZ011071I cicslterm terminated (terminal
outservice).
Explanation:
terminal was set out of service.
System action:
User response:
Ask the System Administrator to put the terminal back
into service, or install as a different terminal.
Destination:
stderr
ERZ011072I cicslterm terminated (network
credentials expired).
Explanation:
network credentials have expired.
System action:
User response:
Refresh your credentials and then invoke another
cicsterm or cicstermp. If this fails check that there is a
valid keytab file in varDir/cics_clients. If there is not a
valid keytab file, run the cicssetupclients command.
94
Destination:
stderr
ERZ011073W Region name is too long - truncated
to regionName.
Explanation:
cicsterm or cicstermp has truncated your region name
because it contained too many characters.
System action:
cicsterm/cicstermp attempts to connect to regionName.
User response:
Invoke cicsterm or cicstermp specifying a valid region
name.
Destination:
stderr
ERZ011074W Netname is too long - truncated to
netName.
Explanation:
cicsterm or cicstermp has truncated your netname
because it contained too many characters.
System action:
cicsterm/cicstermp attempts to install your terminal with
netname netName.
User response:
Invoke cicsterm or cicstermp with a valid netname.
Destination:
stderr
ERZ011077E The printer options -f, -M, -R and -s
can only be used if POSTSCRIPT is
specified for option -p.
Explanation:
cicstermp was invoked with mutually exclusive options.
System action:
cicstermp terminates.
User response:
Invoke cicstermp with correct options. See the TXSeries
for Multiplatforms Administration Reference for more
information.
Destination:
stderr
ERZ011080E Print command printCommand was
unsuccessful.
Explanation:
cicstermp tried to print its temporary file using
printCommand, but it was unable to execute the
command.
System action:
cicstermp continues without printing the file.
ERZ011081E ERZ011100E
User response:
If you have specified your own print command using the
-P option of cicstermp, check that the program exists, is
on the current path and is executable.
Destination:
stderr
ERZ011081E Print command printCommand
terminated abnormally.
Explanation:
cicstermp tried to print its temporary file using the
command printCommand, but the command terminated
abnormally.
System action:
cicstermp continues; however, the file was possibly not
printed.
User response:
If you have specified your own print command using the
-P option of cicstermp, check that the command is
correct and returns an exit code of zero when it
succeeds. Also check that the print spooler (if any)
specified by the print command printCommand is
currently operational.
Destination:
stderr
ERZ011082E Unable to access print spool file
fileName.
Explanation:
cicstermp tried to append print data to the temporary file
fileName, but was unsuccessful.
System action:
cicstermp continues; however, the print data was not
appended.
User response:
Check that the directory of the file fileName has
permissions that allow file creation and that the file
system is not full.
ERZ011088E Install of hard-coded terminal definition

for netname netName already in
progress
Explanation:
A previous request to install a hard-coded terminal
definition has not yet completed. This is possibly due to
multiple requests to install the same definition being
submitted, by typing cicsterm followed by ctrl-C.
cicsterm does not pass ctrl-C requests from the CICS
client to the server until after cicsterm has successfully
completed. This is generally a symptom of a
performance problem.
System action:
CICS terminates the CICS-private transaction CHAT as
another CHAT is already in progress.
User response:
Investigate why the terminal user is getting slow
responses. Check that CICS is running by submitting a
transaction from an already installed terminal. Check
that autoinstall is functioning correctly. In particular,
check that there are no resource constraints for the
machine, that no CICS system limits were hit, that there
are no unexpected long running tasks and examine the
console log for unusual messages that can possibly
indicate either a CICS system problem or a problem
with the users terminal.
Destination:
console.msg
ERZ011099E Unexpected exception exceptionName
received.
Explanation:
cicsterm or cicstermp received an unexpected exception
and has terminated.
System action:
User response:
Please report details of this problem to your support
organization.
Destination:
stderr
Destination:
stderr
ERZ011083I Installed as printer termId, netname

netName.
ERZ011100E Printer with netname netName is a

terminal.
Explanation:
cicstermp was installed as a printer using the specified
termid and netname.
Explanation:
A printer has connected to the region but was unable to
be installed using netname netName because the
terminal.
System action:
cicstermp continues.
User response:
None
Destination:
stderr
System action:
Terminal installation is terminated with abend code
A11P.
User response:
95
ERZ011101E ERZ012003E
Retry the command specifying the netname of a WD
entry that defines a printer or change the WD entry for
this netname to define a printer instead of a terminal.
Destination:
CSMT
User response:
Respond to the warnings displayed and then hit Enter.
Destination:
stderr
ERZ012000I Sign-on is complete
ERZ011101E Invalid key code.

Explanation:
cicsterm has detected an error while receiving a key
code from the operating system.
System action:
User response:
Retry the command. If the problem persists contact your
Destination:
stderr
Explanation:
CICS verified the userid and password given to the
CESN transaction.
System action:
CICS verifies further transactions submitted at the
terminal against your security keys.
User response:
None. This message is for information only.
Destination:
terminal
ERZ012001I Sign-off is complete
ERZ011102I Searching for regions on

machineName
Explanation:
cicsterm is attempting to find CICS regions. The
terminal is now searching on machine machineName.
System action:
cicsterm continues.
User response:
No reponse is necessary.
Destination:
stderr
ERZ011103W Failed to contact CICS RPC listener
on machineName: reason
Explanation:
cicsterm is attempting to find CICS regions.
System action:
cicsterm continues but does not list any CICS regions
from machine machineName.
User response:
Check that the processes are all started.
Destination:
stderr
ERZ011104I Warnings displayed. Hit enter to
continue
Explanation:
cicsterm has displayed warnings relating to attempts to
locate CICS regions on one or more machines. These
messages are displayed until the user hits Enter.
System action:
cicsterm continues after Enter is hit.
Explanation:
On completion of the CESF transaction, CICS has
successfully signed you off the system.
System action:
If the routing transaction is not in effect, the CICS
terminal terminates shortly after displaying the message.
If the routing transaction is in effect, CICS verifies
further transactions submitted from the terminal against
the security keys in effect before the routing transaction
was submitted.
User response:
Destination:
terminal
ERZ012002I Signon at netname netName by user
userName is complete
Explanation:
CESN transaction.
System action:
User response:
Destination:
console.msg
ERZ012003E Invalid sign-on attempt
Explanation:
You attempted to sign-on, but either the userid or
password is invalid.
System action:
96
ERZ012004I ERZ013002E
CICS continues to verify further transactions against the
security keys associated with the userid used for the
terminal autoinstall. For CICS on Windows NT via the
IBM Clients or cicslterm that is the default userid.
User response:
Invoke CESN again and supply the correct userid and
password.
Destination:
terminal
ERZ012004I Sign-on is complete. Password has
been changed.
Explanation:
CESN transaction. CICS also responded to a request to
change the signon password.
System action:
terminal against your security keys. All new signon
attempts require the use of the new password.
User response:
Destination:
terminal
CANCEL the routing session and sign-off from the local

system using CESF if you wish to terminate your CICS
session.
Destination:
terminal
ERZ012008I You have cancelled your sign-on
request. Sign-on is terminated.
Explanation:
You have pressed PF3, and consequently CESN has
been successfully terminated.
System action:
CICS awaits further transaction requests.
User response:
Destination:
terminal
ERZ013001I Usage: cicstfmt [-h [!]hookIds][-m
[!]moduleIds][-o outFile][-f fileName |
[-r regionName][-s a|b | [-u userId] [-n
traceSeqNo | -p [traceSeqNos]]]]
Explanation:
You specified the -? option for cicstfmt. This message
gives the required syntax for cicstfmt.
ERZ012005I Signon at netname netName by user

userName is complete. Password has
been changed.
System action:
None
Explanation:
CESN transaction.
User response:
None. For more information about the cicstfmt
command, see the TXSeries for Multiplatforms
System action:
Destination:
stderr
User response:
Destination:
console.msg
ERZ012007W Sign-off is complete. GOODNIGHT
ignored when using routing
transaction.
Explanation:
You signed off from the system to which the sign-off
transaction was routed. CICS ignores the GOODNIGHT
option in this case.
System action:
CICS verifies further transactions submitted from your
terminal against the security keys in effect before the
routing transaction was submitted.
ERZ013002E Invalid Arguments: Usage: cicstfmt [-h

[!]hookIds][-m [!]moduleIds][-o
outFile][-f fileName | [-r regionName][-s
a|b | [-u userId] [-n traceSeqNo | -p
[traceSeqNos]]]] | [-?]
Explanation:
The arguments you supplied to cicstfmt were incorrect.
System action:
cicstfmt terminates with a non-zero return code.
User response:
Retry the cicstfmt command using the correct syntax, as
shown in the message. For more information about the
cicstfmt command, see the TXSeries for Multiplatforms
Destination:
stderr
User response:
97
ERZ013003E ERZ013011I
ERZ013003E Trace file fileName does not exist
Explanation:
cicstfmt was unable to find the given trace file.
System action:
User response:
Ensure that the specified trace file exists. You possibly
gave incorrect command line options, or a trace file
possibly does not exist.
Destination:
stderr
ERZ013004E Unable to obtain the user trace file for
user userId, on region regionName
Explanation:
cicstfmt was unable to find the details for the user
specified with the -u option or the TraceFile attribute in
the User Definition (UD) entry for the specified user is
blank.
System action:
User response:
Check that the user identifier is valid, and that the
TraceFile attribute in the UD entry for the user is not
blank.
Destination:
stderr
System action:
User response:
Set the CICSREGION environment variable to the name
of the default region. Alternatively, retry the command
specifying the name of a valid region with the -r option.
Destination:
stderr
ERZ013008I In region regionName the following
user trace files for user userId exist:
Explanation:
This message is followed by a list of user trace files.
System action:
None
User response:
Retry the cicstfmt command with the -u and the -n
options.
Destination:
stderr
ERZ013009E User userId does not have any user
trace files available for region
regionName
Explanation:
There are no user trace files available for processing.
System action:
None
ERZ013005E Unable to obtain region definitions for

region regionName
User response:
None
Explanation:
The cicstfmt command was unable to obtain the region
definitions for the given (or defaulted) region. If you did
not specify the -r option then the default region, as
specified by the CICSREGION environment variable,
has not been set up correctly.
Destination:
stderr
System action:
Explanation:
This message is prompting you to confirm your request
to remove the trace files.
User response:
Retry the command with a valid region name specified
by the -r option or correct the CICSREGION
environment variable.
System action:
None
Destination:
stderr
ERZ013006E Unable to obtain the default region
name
Explanation:
The cicstfmt command was unable to obtain the name
of the default region from the CICSREGION
98
ERZ013010I Do you really want to remove the trace

files for region regionName (Yes/No)?
User response:
Enter Yes or No.
Destination:
stderr
ERZ013011I Usage: cicstracefilter [-h[!]hookIds]
[-m[!]moduleIds]
Explanation:
This is the usage information produced by cicstracefilter
in response to the -? option. For more information about
ERZ013012W ERZ013018E
the cicstracefilter command, see the TXSeries for
Destination:
stderr
System action:
None
ERZ013015E Syntax error in list of hook identifiers
User response:
None
Destination:
stderr
ERZ013012W An invalid option optionName has
been specified
Explanation:
You specified an option optionName that is not
recognized by cicstracefilter.
System action:
The option is ignored and cicstracefilter continues.
User response:
Retry the command with valid options, if necessary.
Usage information can be obtained by entering the
command cicstracefilter -? or see the TXSeries for
information.
Destination:
stderr
ERZ013013W An invalid parameter parameterName
has been specified
Explanation:
You specified a parameter parameterName that is not
recognized by cicstracefilter.
System action:
The parameter is ignored and cicstracefilter continues.
User response:
Retry the command with valid parameters, if necessary.
Usage information can be obtained by entering the
command cicstracefilter -? or see the TXSeries for
information.
Destination:
stderr
ERZ013014E A hook identifier, hookId, has been
specified that is larger than the
maximum (FFF)
Explanation:
You specified a hook identifier, hookId, in the argument
to the -h option that is larger than the maximum
permitted hook identifier.
System action:
The cicstracefilter command terminates.
Explanation:
You supplied a list of hook identifiers as the argument to
the -h option, but the list is not in the correct format.
The list consists of a list of hook identifiers separated by
commas, each hook identifier consisting of three
hexadecimal digits. A range of hook identifiers can also
be specified by separating two hook identifiers by a -
character.
System action:
User response:
Retry the command with a valid list of hook identifiers.
Destination:
stderr
ERZ013016E Invalid range in list of hook identifiers
Explanation:
You supplied a list of hook identifiers as the argument to
the -h option, but a range of hook identifiers in the list is
not in the correct format. A range of hook identifiers is
specified by separating two hook identifiers by a -
character with the lower hook identifier first.
System action:
User response:
Destination:
stderr
ERZ013017E The hook identifier hookId contains
an invalid hexadecimal digit
Explanation:
The valid hexadecimal digits are 0 through 9, A
through F and a through f. The hook identifier hookId
contains a character that is not in this set.
System action:
User response:
Destination:
stderr
ERZ013018E A module identifier, moduleId, has
been specified that is larger than the
maximum permitted (999)
Explanation:
User response:
99
ERZ013019E ERZ013024I
You specified a module identifier, moduleId, in the
argument to the -m option that is larger than the
maximum permitted module identifier.
Check that the file system is not full and, if necessary,

recreate the trace or dump file. If the problem persists,
please contact your support organization.
System action:
Destination:
stderr
User response:
Retry the command with a valid list of module
identifiers.
Destination:
stderr
ERZ013022E An invalid hook type, hookType, was

encountered in stdin at offset
byteOffset - hook identifier hookId
Explanation:
The module identifier moduleId contains a character that
is not a valid decimal digit.
Explanation:
An error occurred while processing data from standard
input. Hook type hookType is not valid. The valid hook
types are 0 and 8. The input file is possibly not a valid
CICS trace or dump file, or it is possibly corrupted.
Trace entries were possibly already written to standard
output, in which case the output can be formatted by
using the cicstfmt command.
System action:
System action:
cicstracefilter terminates.
User response:
Retry the command with a valid list of module
identifiers.
User response:
If necessary, recreate the trace or dump file. If the
problem persists, please contact your support
organization.
ERZ013019E The module identifier moduleId

contains an invalid decimal digit
Destination:
stderr
ERZ013020W Module name moduleName does not
match the name of any CICS module
Explanation:
The module name, moduleName, does not match any
of the CICS module names.
System action:
cicstracefilter continues.
User response:
If necessary, retry the cicstracefilter command
specifying a valid module name.
Destination:
stderr
ERZ013021E Unable to read data from stdin at
offset byteOffset (error code errorCode)
Explanation:
An error occurred while reading data from standard
input. The error code returned by ferror was errorCode.
The input file is possibly not a valid CICS trace or dump
file, or it is possibly corrupted or truncated. Trace entries
were possibly already written to standard output, in
which case the output can be formatted by using the
cicstfmt command.
System action:
User response:
100
Destination:
stderr
ERZ013023E Unable to write data to standard
output (error code errorCode)
Explanation:
An error occurred while writing to standard output. The
error code returned by ferror was errorCode.
System action:
User response:
Check that there is sufficient space in the file system
and that you have the necessary permissions to write
the file. If the problem persists, please contact your
Destination:
stderr
ERZ013024I The following user trace files for user
userId exist:
Explanation:
This message is followed by a list of user trace files.
System action:
None
User response:
Retry the cicstfmt command with the -u and the -n
options.
Destination:
stderr
ERZ013025I ERZ013031E
ERZ013025I Usage: cicstfmt [-h [!]hookIds][-m
[!]moduleIds][-o outFile][-f fileName |
[-r regionName][-s a|b | [-u userId] [-n
traceSeqNo | -p [traceSeqNos]]]] | [-?]
Explanation:
This is the usage message for the cicstfmt command.
System action:
The command terminates.
User response:
None.
Destination:
stderr
ERZ013026E Entry userId not found for permanent
database class databaseName.
Explanation:
cicsftmt tried to read a record from the databaseName.
stanza file, looking for resource userId, but failed to do
so.
System action:
The command can continue or terminate, depending on
the severity of the problem.
User response:
Check that the stanza file exists, and has the correct
permissions to enable cics to read from it. Check that
this file has not been corrupted.
Destination:
stderr
ERZ013027E Unable to access directory directory,
errno errno.
Explanation:
CICS tried to look at the contents of the specified
directory but was unable to do so.
System action:
User response:
Ensure that the relevant directory exists and has the
necessary access permissions. Check errno for futher
information.
Destination:
stderr
ERZ013028E Unable to access trace file traceFile,
errno errno.
Explanation:
cicstfmt was unable to access the given trace file. This
was possibly in an attempt to read it or to delete it.
Depending on why the file was being accessed, the

command can choose either to ignore the file and
continue, or to terminate.
User response:
You possibly need to do nothing. If you believe the file
is supposed to exist then check it does, and check that
its permissions enable you to delete it. More information
can be found by using errno.
Destination:
stderr
ERZ013029E
Not enough memory for operation
Explanation:
cicstfmt tried to access some memory for its own
working storage but was unable to do so.
System action:
User response:
Ensure your machine has enough memory installed.
Check also that you have adequate paging space. See
the TXSeries Installation Guide for more information on
system resources.
Destination:
stderr
ERZ013030E Unable to find CICS data
Explanation:
cicstfmt encountered a problem while obtaining
information about the CICS system installed on your
machine.
System action:
cicstfmt terminates with a non-zero status.
User response:
Ensure that CICS is installed correctly.
Destination:
stderr
ERZ013031E Region name regionName is greater
than 8 characters long
Explanation:
A region name must be 8 characters or less.
System action:
The command abnormally terminates with a non-zero
error status.
User response:
Enter again with the correct region name.
Destination:
stderr
System action:
101
ERZ014001E ERZ014007E
ERZ014001E userid is not authorized to run
transId from termId.
Explanation:
The user userid has invoked a transaction transId at
terminal termId, or transaction transId was invoked
with no associated user identification for terminal
termId. The user permissions or terminal permissions
do not permit the transaction to run.
System action:
The transaction transId is not started. Abend code
A146 is displayed (via message ERZ1416E) at termId.
User response:
Ensure the Resource Security Level (RSL) key
(RSLKeyList) and the Transaction Security Level (TSL)
key (TSLKeyList) attributes in the User Definition for the
user userid permit access to the transaction transId. If
no user identifier is associated with the transaction then
ensure the Resource Security Level (RSL) key
(RSLKeyList) and the Transaction Security Level (TSL)
key (TSLKeyList) attributes in the Terminal Definition for
the terminal termId permit access to the transaction
transId. Resubmit the transaction request.
Destination:
console.msg
ERZ014002E exceptionText exception detected.
Explanation:
An abnormal condition was raised and caught while
running in CICS code.
System action:
The CICS process is terminated. If the process was an
application server then any task it was running is
terminated with abend code A142. If the process was a
CICS control process then the region is abnormally
terminated with code U1401.
User response:
This is a CICS internal problem. Save any dump file
produced. If the region was terminated, then restart the
region (ensuring the region is configured to produce a
dump if the problem recurs). Contact your support
organization.
Destination:
console.msg
ERZ014003E Unable to initialize process processId
as an application server.
Explanation:
CICS has detected an unrecoverable error during
application server startup.
System action:
The new application server being started is terminated.
User response:
This problem is most likely caused by CICS being short
of region pool storage. Look for storage errors reported
102
in console.msg and correct these. If the problem

persists, contact your support organization.
Destination:
console.msg
ERZ014004E Unable to allocate storage for
Transaction Work Area (TWA) in
transaction transId. Requested size is
length bytes.
Explanation:
CICS was unable to satisfy the storage allocation
request of length bytes for the Transaction Work Area
(TWA) in transaction transId.
System action:
The transaction transId is not started. If the transaction
was submitted from a terminal then abend code A143 is
displayed (via message ERZ1416E) at that terminal.
User response:
Other messages in CSMT or console.msg indicate the
underlying cause of this problem. If the cause of the
problem is shortage of region storage for CICS control
blocks then correct these problems. If the transaction
has inherited a COMMAREA from the previous
transaction then this takes up task private storage.
Otherwise, reconfigure the TWASize attribute in the
Transaction Definition to require less storage. Resubmit
the transaction request.
Destination:
console.msg
ERZ014005E Unable to execute transaction
transId. No initial program defined.
Explanation:
The transaction transId cannot be executed because
no initial program is specified in the Transaction
Definition.
System action:
User response:
The transaction is not executable because there is no
initial program specified in the ProgName attribute in the
Transaction Definition. Correct the Transaction Definition
to specify the name of the initial program and resubmit
the transaction.
Destination:
console.msg
ERZ014007E Incorrect Task Control Area (TCA)
signature found at address; expected
actualSignature.
Explanation:
ERZ014008E ERZ014012E
The CICS self-consistency checking has detected a
Task Control Area (TCA) in the TCA chain with an
incorrect signature.
System action:
User response:
This is a CICS internal problem. If the SysDump
attribute in the Region Definition is set to yes then a
region dump file is produced. Save this file. Restart the
region (ensuring the region is configured to produce a
organization.
Destination:
console.msg
ERZ014008E Unable to allocate storage for the
COMMAREA in transaction transId.
Requested size is length bytes.
Explanation:
request of length bytes for the COMMAREA in
System action:
User response:
blocks then correct these problems and retry the
transaction. Otherwise, redesign your transaction to use
less storage for the COMMAREA and resubmit the
transaction.
Destination:
console.msg
ERZ014009I Unable to free storage for the
COMMAREA in transaction transId
running at termId.
Explanation:
CICS was unable to free the storage used to hold the
COMMAREA saved by the previous transaction run at
termId.
System action:
CICS processing continues.
User response:
This message is logged for information only and has no
effect on the running of the transaction transId. It can
possibly indicate an internal CICS problem, and other
messages in console.msg or CSMT can provide further
information. It does mean that some storage acquired
on behalf of a transaction previously run at termId was
unable to be freed and this storage remains allocated
until the region is shut down. If the problem persists,

Destination:
console.msg
ERZ014010E Unable to initialize communications to
remote system to run transaction
transId.
Explanation:
CICS received a request from a remote system to run
the transaction transId and was unable to establish a
conversation with that remote system.
System action:
The transaction transId is not started.
User response:
This problem is caused by failure of the communications
links to the remote system, problems in the CICS
communications software or an invalid CICS Region
Definition. Look for communication errors reported in
console.msg or CSMT and correct these. If the problem
Destination:
console.msg
ERZ014011E Unable to allocate a communications
session with remote system sysId to
run transaction transId.
Explanation:
CICS has received a transaction request as a result of
an EXEC CICS START specifying a terminal identifier
that is configured as the identifier of a connected
system. An attempt to allocate a session with the
specified system was unsuccessful.
System action:
The transaction transId is not started.
User response:
This problem is caused by failure of the communication
links to the remote system or problems in the CICS
communications software. Look for communication
errors reported in console.msg or CSMT and correct
these. If the problem persists, contact your support
organization.
Destination:
console.msg
ERZ014012E CICS was unable to obtain a database
entry for terminal termId during
initialization of transaction transId.
Explanation:
The record describing the users terminal was unable to
be retrieved from the runtime region database.
System action:
103
ERZ014013E ERZ014017E
A141 is written to console.msg, and displayed at
termId if the terminal is still available.
User response:
Use CEMT from another terminal to inquire on the
Terminal Definition for termId. If you are using a
permanently connected terminal (as opposed to
autoinstalled) and it does not exist then contact your
System Administrator to add a Terminal Definition for
termId and resubmit the transaction. If the Terminal
Definition does exist, or if you are using an autoinstalled
terminal, then the terminal was possibly purged by, for
instance, CEMT SET TERMINAL OUTSERVICE.
Otherwise, this indicates an internal CICS problem.
Retry the transaction and if the problem persists,
Destination:
console.msg
ERZ014013E Terminal status does not permit
transId to be run at termId.
Explanation:
The attribute settings in the Terminal Definition for
termId do not permit the transaction to be run in the
way requested. This error is produced if the OutService
attribute in the Terminal Definition is set to yes; if the
transaction request was initiated from a terminal and the
CanStartTTIs attribute in the Terminal Definition is set to
no, or if the request is initiated as an Automatic Task
Initiation (ATI) (either locally or remotely) and the
CanStartATIs attribute is set to no.
System action:
User response:
Correct the terminal attributes to permit the transaction
to be run in the mode requested and resubmit the
transaction.
Destination:
console.msg
ERZ014014E Unable to initialize terminal termId as
principal facility for transaction
transId.
Explanation:
CICS was unable to initialize the terminal termId for
use during the initialization of transaction transId.
System action:
User response:
Other messages (ERZ062xxx) in CSMT or console.msg
indicate the underlying cause of this problem. Once
corrected, resubmit the transaction request.
Destination:
104
console.msg
ERZ014015E CICS was unable to save initial input
data from terminal termId during
Explanation:
The user data sent with the transaction request for
transId was unable to be written to the terminal
input/output area (TIOA) of terminal termId.
System action:
User response:
Other messages (ERZ062xxx) in CSMT or console.msg
indicate the underlying cause of this problem. Once
corrected, resubmit the transaction request.
Destination:
console.msg
ERZ014016E Transaction transId, Abend
abendCode, at termId.
Explanation:
The transaction transId running at the terminal where
this message is displayed was abnormally terminated
with code abendCode. If the transaction is not
associated with a terminal then ???? is substituted for
termId.
System action:
The transaction transId is abnormally terminated.
User response:
abendCode is the abnormal termination code that
caused the transaction to be terminated. If the code is
not one used for abnormal terminations initiated by
CICS then it is a user code generated by an EXEC
CICS ABEND ABCODE (abendCode). Correct the
problem and resubmit the transaction. If the transaction
was abended A147 while it was being debugged via
CEDF the debug terminal can remain locked; use
CEMT commands to put the debug terminal out of
service and reacquire it.
Destination:
console.msg and the terminal that invoked the
transaction.
ERZ014017E Unable to allocate storage for the
Exec Interface Block (EIB) in
transaction transId. Requested size is
length bytes.
Explanation:
request of length bytes for the Exec Interface Block
(EIB) during the initialization of transaction transId.
System action:
ERZ014019E ERZ014024E
Destination:
console.msg
User response:
blocks then correct these problems. Retry the
transaction request and, if the problem persists, contact
ERZ014021E Autoinstall of device deviceId was

unsuccessful.
Destination:
console.msg
ERZ014019E Unable to remove details of current
transaction transId to permit execution
of newTransId.
Explanation:
CICS received a request to replace the current
transaction transId with the new transaction
newTransId and was unable to remove details held
about the current transaction.
System action:
The new transaction newTransId is not started and the
current transaction is abended with code A145.
User response:
This is a CICS internal problem specific to the
environment created by the CRTE transaction. Other
messages in CSMT or console.msg indicate the
underlying cause of this problem. Restart the CRTE
session and resubmit the transaction. If the problem
Destination:
console.msg
Explanation:
An attempt to autoinstall a terminal definition from
device deviceId was unsuccessful.
System action:
The terminal is not installed into the region.
User response:
underlying cause of this problem. Once the cause of
these is corrected the autoinstall can be retried.
Destination:
console.msg
ERZ014022I Exception exceptiontext caught during
termination of transaction transId at
termId.
Explanation:
An abnormal condition was raised and caught during
the termination of the transaction transId running at the
terminal termId.
System action:
CICS continues with the termination of the transaction.
User response:
effect on the running of the transaction transId. It can
possibly indicate an internal CICS problem, and other
messages in console.msg or CSMT can provide further
information. If the problem persists, contact your support
organization.
ERZ014020E CICS was unable to obtain a database

entry for transaction transId.
Destination:
console.msg
Explanation:
The record describing the transaction transId was
unable to be retrieved from the runtime region database
or written back to the database.
ERZ014024E An attempt to attach the region

memory in process with id processId
was unsuccessful.
System action:
User response:
The most likely cause of this error is the Transaction
Definition being deleted by the System Administrator
while the transaction was being started. Use CEMT to
inquire on the Transaction Definition for transId. If it
does not exist then contact your System Administrator
to add the definition for transId and resubmit the
transaction. If the Transaction Definition does exist then
this indicates an internal CICS problem. Retry the
transaction and, if the problem persists, contact your
Explanation:
CICS made an unsuccessful attempt to attach to the
shared memory segment of the region.
System action:
CICS abnormally terminates the region with code
U1403.
User response:
If the process detecting the problem was an application
server (cicsas) then it is possible that the problem is
caused by user code that has corrupted internal CICS
data structures. Examine the use of static memory in
any transaction running at the time of failure. Retry the
failed transactions once they are checked. If the
process was a CICS control process then this indicates
105
ERZ014025E ERZ014028E
a CICS internal problem. If the SysDump attribute in the
Region Definition is set to yes then a region dump file is
produced. Save this dump file. Restart the region
(ensuring the region is configured to produce a dump if
the problem recurs). Contact your support organization.
Destination:
console.msg
ERZ014025E Unable to set region locale for
transaction transId. Region locale
categories were localeName.
Explanation:
CICS received a request to run the transaction transId
and was unable to set the locale of the application
server to the region locale.
System action:
User response:
The locale for the transaction is taken from the
environment of the user who submitted the transaction
request. If the requested locale cannot be set, or is not
supplied, then the application server is set to the region
locale to run the transaction. The requested locale
categories within the locale can be modified by a
number of environment variables. Ensure that each of
these environment variables contains a valid locale for
the machine where the transaction request is to be run
and retry the transaction request.
Destination:
console.msg
ERZ014026I Unable to save locale during
Explanation:
The locale for the transaction transId was unable to be
saved in the CICS region pool.
System action:
The transaction transId is started using the region
locale.
User response:
effect on the running of transaction transId, except that
the region locale is used instead of the requested
locale. This problem is most likely caused by CICS
being short of region pool storage. It can possibly
indicate an internal CICS problem, and other messages
in console.msg or CSMT can provide further
information. If the problem persists, contact your support
organization.
Destination:
console.msg
106
ERZ014027I Unable to set requested locale during

initialization of transaction transId or
having problems with the message
catalog. Requested locale categories
were localeName.
Explanation:
CICS received a request to run the transaction transId
and was unable to set the locale of the application
server to the requested locale or was unable to access
the message catalog.
System action:
The transaction transId is started using the region
locale.
User response:
effect on the running of transaction transId, except that
the region locale is used instead of the requested
locale. The requested locale for the transaction is taken
from the environment of the user who submitted the
transaction request. The locale categories within the
locale can be modified by a number of environment
variables. Ensure that each of these environment
variables contain a valid locale for the machine where
the transaction request is to be run and retry the
transaction request.
Destination:
console.msg
ERZ014028E Transaction transId was
unsuccessful in the invocation mode
check and could not be started.
Explanation:
This error message is produced if the security check on
the way in which the transaction was invoked is
unsuccessful. This check is based on the Transaction
Definition, the way in which the transaction was started
(either user requested, Automatic Task Initiation (ATI) or
triggered task), the principal facility for the task (either
input/output terminal, output terminal, communications
link or none) and the current CICS phase.
System action:
User response:
underlying cause of this problem. Check that the
InvocationMode attribute in the Transaction Definition for
transId permits the transaction to be run in the way
requested. Once the cause of the error is corrected the
transaction request can be retried.
Destination:
console.msg
ERZ014029W ERZ014034E
ERZ014029W Application server ended normally,
but log daemon wasnt notified.
Explanation:
The process that ended was still using a log file. This is
not supposed to occur.
System action:
The system notifies the log daemon that the log file is
no longer in use.
User response:
It appeared to cics that the process that last shut down
was an application server that ended normally, that is to
say with an exit code of 0. This is not the case. Check
what transaction, if any was running when the process
shut down, and that it is behaving correctly.
Destination:
console.msg
ERZ014030W Short-on-storage for user exit 15
(UE014015) parameter list.
ERZ014032E A null program name has been

returned by user exit 25 (UE014025),
while routing transaction transId.
Explanation:
This error message is produced if the dynamic
transaction routing user exit (UE014025) returns a null
program name in its parameter list field UE_dyrprog.
System action:
Other processing continues.
User response:
Ensure that your dynamic transaction routing user exit
does not return a null program name, even if the
transaction is to be routed remotely. Alter your user exit
and retry the dynamic transaction. Another cause of the
problem is possibly that the ProgName field in the
Transaction Definitions is null and user exit 25
(UE014025) has let the program name default to this.
Explanation:
A request to obtain storage in which to build a
parameter list for user exit 15 (UE014015) failed.
Destination:
console.msg
System action:
Processing continues as if user exit 15 (UE014015) is
inactive.
ERZ014033E User exit 25 (UE014025) has returned

a return code of UE_Term_Abend,
while routing transaction transId.
User response:
Produce a SNAP dump and investigate storage usage
in the CICS region; consider increasing the amounts of
storage available to CICS using region definition
parameters.
Explanation:
transaction routing user exit (UE014025) returns a
return code of UE_Term_Abend.
Destination:
CSMT
ERZ014031E Unable to allocate storage for user
exit 25 (UE014025) parameter list, while
routing transaction transId.
Explanation:
System action:
User response:
storage available to CICS using region definition
parameters.
Destination:
console.msg
System action:
User response:
Identify why your user exit has returned
UE_Term_Abend. It was possibly produced by your user
exit for a valid reason such as all remote systems being
unavailable. If you wish the dynamic transaction to be
routed ensure that your user exit returns UE_Normal.
Destination:
console.msg
ERZ014034E User exit 25 (UE014025) is not active,
and dynamic transaction transId has
been started.
Explanation:
transaction routing user exit (UE014025) is not active
and a dynamic transaction is started.
System action:
107
ERZ014035W ERZ014038W
User response:
If you are using dynamic transaction routing ensure that
you have written a dynamic transaction routing program.
Also ensure that the user exit program is associated
with the exit point, by using UserExitNumber attribute in
the Program Definitions. If you have tried associating a
program with the dynamic routing user exit, check the
console messages during region start-up to ensure that
the program was successfully loaded. You are advised
to restart CICS once you have discovered why your
dynamic transaction routing program is not active.
Destination:
console.msg
ERZ014035W User exit 25 (UE014025) requested to
terminate transaction transId without
an abend.
Explanation:
transaction routing user exit (UE014025) does not return
a recognized return code, or returns UE_Terminate.
resources were updated, this can result in a CICS

region termination to avoid corruption of user data.
Investigate the status of all resources used by the
hung transaction in order to determine whether there is
a non-CICS resource that can be prompted into action.
Ensure that the Transaction Definitions for the
transaction has the attributes Timeout and
DeadLockTimeout set to non-zero values. Use the XID
to determine the state of the transaction and/or to alter
that state in the database.
Destination:
console.msg
ERZ014037W Transaction transId rejected transaction disabled.
Explanation:
CICS attempted to run the transaction transId, but was
unable to, either because the transaction was disabled,
or the limit on the number of queued and active
transactions, for the class transId belongs to, was
reached. The class is specified by the TClass:
parameter in the Transaction Definitions. The maximum
number of tasks allowed is one less than the total of the
positional entries, in the Region Definitions parameters
ClassMaxTasks and ClassMaxTaskLim, for the
transaction class specified.
System action:
Processing of transaction transId stops normally. Other
processing continues.
System action:
The transaction is not run.
User response:
Ensure that your dynamic transaction routing program
returns a valid return code. If UE_Terminate was
returned, check why your dynamic transaction user exit
has returned this value. It was possibly produced by
your user exit for a valid reason such as all remote
systems being unavailable. If you wish the dynamic
transaction to be routed, ensure that your user exit
returns UE_Normal.
User response:
Enable the transaction if it is disabled (using cicsupdate
or CEMT). If the class limit was reached, wait until
some of the running tasks have finished, and resubmit
the transaction. If you want to raise the class limit,
increase the ClassMaxTasks or ClassMaxTaskLim
parameters, or set ClassMaxTaskLim to 0 for the
transaction class (which means no limit is placed on the
number of tasks). You can also move some transactions
to a different class.
Destination:
console.msg
ERZ014036E Unable to force purge process
processId as it is XA registered (XID
xId).
Explanation:
CICS was unsuccessful in attempting to force purge the
transaction running in the specified process. The main
thread has ignored both a request to force purge and an
asynchronous thread cancel. The XID with which the
transaction is registered is as given.
System action:
The attempt to force purge the transaction is
abandoned.
User response:
You can choose to forcibly terminate the process
indicated in the message. However, if any recoverable
108
Destination:
The users screen.
ERZ014038W Transaction transId running as task
taskId has used userCPU milliseconds
of user space CPU
Explanation:
The task has exceeded its maximum allowed user
space CPU. There is a possible program loop in the
task, or the maximum allowed user space CPU usage
for this task is set too low. See the MaxTaskCPU
attribute in the Transaction Definitions or the
MaxTaskCPU in the Region Definitions.
System action:
The task continues. The user space CPU usage for the
task is reset to zero.
User response:
ERZ014039E ERZ014048E
Check that the MaxTaskCPU attributes are set correctly.
Check the task for a possible infinite or runaway
program loop.
Destination:
console.msg
ERZ014039E Transaction transId running as task
taskId has used userCPU milliseconds
of user space CPU
Explanation:
The task has exceeded its maximum allowed user
space CPU. There is a possible program loop in the
task, or the maximum allowed user space CPU usage
for this task is set too low. See the MaxTaskCPU
attribute in the Transaction Definitions or the
MaxTaskCPU in the Region Definitions.
System action:
The task is abnormally terminate with abend code AICA.
User response:
Check that the MaxTaskCPU attributes are set correctly.
Check the task for a possible infinite or runaway
program loop.
ERZ014045I Forcepurge received, proceeding for

termination.
Explanation:
Forcepurge request has been received and honored.
System action:
Force purge the task and terminate the application
server.
User response:
None
Destination:
console.msg
ERZ014046I Forcepurge event received, reason
code: reason originator :originator.
Explanation:
Forcepurge request has been received.
System action:
CICS will make an attempt to force purge the task.
User response:
None
Destination:
console.msg
Destination:
console.msg
ERZ014040E First abend AbendStr occurred for

transaction Tranid in program
ProgName
ERZ014047E Abnormal termination A167:

Inconsistency detected in logical unit
of work control structures
Explanation:
Current transaction got its first abend in the specified
program.
Explanation:
The data structures used to drive a transaction are
inconsistent. They might have been deleted due to
asynchronous abort or they could have been corrupted.
System action:
Refer to the information for the specific abend.
User response:
Refer to the information for the specific abend.
Destination:
console
ERZ014041E Forcepurge cannot be done now.
System action:
CICS terminates the application server process with
code A167. The transaction running at this point in time
will abend.
User response:
If required, resubmit the transaction. See the additional
error messages produced for further information. Retry
the transaction call IBM Support if the problem persists.
Explanation:
When the forcepurge request is received the application
server was holding a critical lock for a long time
Destination:
console
System action:
The Task will not be forcepurged
ERZ014048E Forcepurge:Task could not be

terminated, exiting process
User response:
This message might indicate a hang situation. If the
region is not responding, contact your support
representative.
Explanation:
The current task can not be terminated as it could be in
a non-cancelable blocking call.
Destination:
console.msg
System action:
CICS terminates the application server process with exit
code 199.
User response:
109
ERZ015001E ERZ015005E
User response:
Correct the program belonging to the transaction that is
in error.
Destination:
console
Destination:
CSMT
ERZ015001E CICS self-consistency checking has

detected an inconsistency in the
Program Control internal data
structures
ERZ015004E CICS is unable to allocate storage to

hold a COMMAREA during an EXEC
CICS RETURN
Explanation:
The CICS self-consistency checking detected an error in
the Program Control internal data structures, in the
Region Pool, that hold information about programs
running at each logical level. This error was unable to
be corrected.
System action:
The region continues or terminates abnormally if the
inconsistency is serious (with abend code U1501).
User response:
Because the Program Control data structures are held
in the Region Pool it is unlikely that the invalid data was
produced by application code. Consider shutting the
region down if any further errors are reported. Save any
dump file produced for use by your support
organization. If the problem persists, contact your
Destination:
console.msg
ERZ015002E User userId is not authorized to run
program prpgramName
Explanation:
The named user attempted to run a program to which
the user does not have security access.
System action:
CICS returns the NOTAUTH condition to the application
and the transaction continues.
User response:
Request a change to the security permissions for the
Program Definition entry (PD), or use another program.
Destination:
console.msg
ERZ015003E Transaction transId attempted to run
a program with an empty name
Explanation:
CICS attempted to EXEC CICS LINK or EXEC CICS
XCTL to a program where the program name has no
characters.
System action:
CICS returns the PGMIDERR condition to the
application and the transaction continues.
110
Explanation:
CICS is unable to allocate storage from the
Task-Shared Pool for a COMMAREA to be passed to
another transaction via an EXEC CICS RETURN.
System action:
CICS terminates the transaction with abend code A156,
but the region continues.
User response:
Because memory in the Task-Shared Pool is continually
being acquired and freed by running transactions,
resubmission of this transaction can possibly be
successful. If this problem persists when you resubmit
the transaction, check whether any transaction is using
large amounts of Task-Shared storage. Finally, consider
increasing the size of the Task-Shared Pool by
restarting the region with an override for the value of the
MaxTSHPool attribute in the Region Definition (RD).
Destination:
CSMT
ERZ015005E CICS is unable to allocate Region
Pool storage for Program Control data
structures
Explanation:
CICS is unable to allocate storage from the Region
Pool, to hold the control information required for running
a new program.
System action:
CICS abnormally terminates the transaction, but the
region continues.
User response:
Because memory in the Region Pool is continually
being acquired and freed by CICS on behalf of running
transactions, resubmission of this transaction can
possibly be successful. If this problem persists when
you resubmit the transaction, check whether it is looping
in some way that causes CICS to acquire substantial
amounts of Region Pool memory on its behalf; for
example, check the depth of EXEC CICS LINKs in the
program, as Region Pool memory is required for each
logical level. Finally, consider increasing the size of the
Region Pool by restarting the region with an override for
the value of the MaxRegionPool attribute in the Region
Definition (RD).
Destination:
CSMT
ERZ015006W ERZ015011E
ERZ015006W Abnormal Termination abendCode,
Program programName, Transaction
transId, Terminal termId
Explanation:
CICS abnormally terminates the named transaction, with
top-level program pgmid, being run at the named
terminal.
System action:
CICS abnormally terminates the transaction. The region
continues.
User response:
Investigate the cause of the abnormal termination using
the CICS Problem Determination Guide. Also consider
using any dump file created for the transaction.
Destination:
CSMT
ERZ015007E Abnormal Termination U1507. CICS is
unable to free Program Control storage
Explanation:
CICS is unable to free Region Pool storage allocated for
Program Control data structures. These data structures
hold information about programs running at each logical
level.
System action:
User response:
in the Region Pool, the problem encountered freeing the
in the CICS internal data structures. If the problem
recurs, save any dump file produced and contact your
ERZ015009W Unable to free all CICS Program

Control storage
Explanation:
CICS was unable to clean up all memory used for
Program Control data structures from the Region Pool
by an application server. These data structures hold
information about programs running at each logical
level. This error occurs during application server
termination.
System action:
The application server is terminated.
User response:
If any further problems are reported by the CICS
self-consistency checking transaction, save any dump
files produced. If the problem recurs, contact your
Destination:
console.msg
ERZ015010E Unable to free Program Control
storage
Explanation:
CICS is unable to release some Task-Private Pool
storage allocated for Program Control data structures.
These data structures hold information about programs
running at each logical level.
System action:
CICS abnormally terminates the transaction and the
application server in which it was running (with abend
code A152).
User response:
This problem is unlikely to be caused by application
code. If the problem recurs, save any dump file
Destination:
console.msg
Destination:
CSMT
ERZ015008E CICS is unable to unload a program
ERZ015011E Unable to lock a database entry
Explanation:
CICS was unable to unload a program previously
loaded by an application server.
Explanation:
CICS is unable to lock a database entry for the program
definition of a program being run. This was due to lack
of space in the Region Pool.
System action:
application server in which it was running (with abend
code A155).
User response:
Check the symptom record file for any operating system
specific failure. The problem can also be caused by
incorrect application code, so check for this in the
transaction that failed.
Destination:
CSMT
System action:
application server running the transaction (with abend
code A154).
User response:
111
ERZ015012E ERZ015018W
program, as Region Pool memory is required for each
Definition (RD).
Destination:
CSMT
ERZ015012E Abnormal Termination U1512. CICS is
unable to delta a Program Definition
database entry
Explanation:
CICS is unable to delta a Program Definition database
record after locking it. This is likely to be caused by an
System action:
User response:
Any CICS internal data structure inconsistencies are
unlikely to be caused by application code, since they
are held in the Region Pool. Save any dump file
Destination:
console.msg
ERZ015014E Abnormal termination U1514. CICS is
unable to attach Region Pool
Explanation:
CICS was unable to attach shared memory used for the
Region Pool after returning from application code.
Region Pool memory is protected while running
application code, by detaching it.
System action:
User response:
This error can occur if shared memory segments are
removed accidentally. Otherwise, it can be caused by a
CICS internal problem. In this case, save any dump file
Destination:
console.msg
User response:
Save any dump file produced. This error is likely to be
caused by a CICS inconsistency, rather than incorrect
applications. If the problem recurs, contact your support
organization.
Destination:
CSMT
ERZ015016E Abnormal termination U1516. CICS is
unable to update the principal facility
database record
Explanation:
CICS was unable to update the database record for the
principal facility, during an EXEC CICS RETURN
TRANSID COMMAREA command. This is likely to be
caused by an inconsistency in the CICS internal data
structures.
System action:
User response:
Any CICS internal data structure inconsistencies are
unlikely to be caused by application code, since they
are held in the Region Pool. Save any dump file
Destination:
console.msg
ERZ015017E Unsuccessful system check of last
loaded program
Explanation:
CICS perform checks after loading each application
program used by a transaction. CICS was unable to
obtain information about the last program loaded.
System action:
CICS abnormally terminates the transaction with abend
code APCT.
User response:
Try resubmission of the transaction. If the problem
recurs, inspect the symptom record file for any
operating system specific error. Check the transaction
for very deep EXEC CICS LINK levels, as memory is
required for loading each level. If the problem persists,
save any dump file produced and contact your support
organization.
ERZ015015E CICS is unable to find a database

entry for the principal facility
Destination:
Explanation:
CICS was unable to find the database record for the
principal facility, during an EXEC CICS RETURN
TRANSID COMMAREA command.
ERZ015018W Abnormal Termination abendCode,

Transaction transId, Program
programName
System action:
application server in which it was running with abend
code A15F.
112
Explanation:
CICS abnormally terminates the named transaction, with
top-level program pgmid.
System action:
ERZ015019E ERZ015027E
continues.
User response:
Investigate the cause of the abnormal termination using
the CICS Problem Determination Guide. Also consider
using any dump file created for the transaction.
Destination:
CSMT
ERZ015019E A Program Control structure has an
invalid signature, should be:
expectedSignature is: actualSignature,
for Task Control Area at: TCAaddress
Explanation:
The CICS self-consistency checking detected an error in
the Program Control internal data structures, in the
Region Pool, that hold information about programs
running at each logical level. This error was unable to
be corrected.
System action:
The region continues.
User response:
produced by application code. Consider shutting the
region down if any further errors are reported. Save any
dump file produced for use by your support
organization. If the problem persists, contact your
ERZ015021E An EXEC CICS LINK specified a NULL

SYSID
Explanation:
The EXEC CICS LINK SYSID option must specify the
name of the system where the linked-to program
resides with up to four characters; CICS has instead
found a NULL or empty string.
System action:
The SYSIDERR condition is raised and the transaction
continues.
User response:
Correct the program or handle the condition as
appropriate.
Destination:
CSMT
ERZ015022E Program programPathName not found
Explanation:
CICS attempts to load a program but can not find it.
System action:
The transaction is abnormally terminated (with abend
code APCT).
User response:
Install the program in the correct place.
Destination:
CSMT
Destination:
console.msg
ERZ015027E Unexpected Exception - exception

string is: exceptionString
ERZ015020E Count of Program Control structures:

count1, in Task Control Area (at:
TCAaddress) differs from actual
number: count2
Explanation:
An exception is caught while running in CICS code.
Possible causes of the exception are an invalid
argument on an EXEC CICS command or a CICS
internal problem.
Explanation:
The periodic consistency check performed by CICS on
the Program Control structures detects an error that
CICS was unable to correct. These data structures hold
information about programs running at each logical
level.
System action:
The CICS region is abnormally terminated with abend
code U1501.
User response:
produced by application code. Save any dump file
Destination:
console.msg
System action:
The transaction and application server running the
transaction are abnormally terminated (with abend code
A158).
User response:
Inspect the symptom record file for symptom records
that indicate why the exception occurred. Investigate the
abend using appropriate debugging tools (for example:
CEDF, ANIMATOR). If the exception appears to occur
on a particular EXEC CICS command, and some form
of address exception is indicated, carefully check all
arguments specified on the EXEC CICS command and
correct the program if necessary. Otherwise, this is
probably a CICS internal problem. Save any dump file
produced. If the problem persists, contact your support
organization.
Destination:
CSMT
113
ERZ015028W ERZ015034E
ERZ015028W Exception in user application code
(programName) - exception string is:
exceptionString
Explanation:
An exception is caught while running in application
code.
System action:
The user application code is unloaded from the task.
The transaction is abnormally terminated (with abend
code ASRA).
User response:
Investigate the causes of the ASRA using appropriate
debugging tools (for example: CEDF, ANIMATOR).
CICS attempted to run a program that has a Remote

System Identifier (RemoteSysId) defined in its database
Program Definition entry (PD) when RemoteSysId is not
allowed (for example, the first program of a transaction).
System action:
The program is not run and the condition PGMIDERR is
raised.
User response:
Check the Program Definition entry (PD) and
Transaction Definition entry (TD) are correct.
Destination:
console.msg
Destination:
CSMT
ERZ015032E Transaction transId attempts to run

program programName which is
disabled

hold a COMMAREA during XCTL
Explanation:
CICS attempts to run a program whose database entry
is marked as disabled.
Explanation:
CICS is unable to allocate storage for a COMMAREA
from the Task-Private Pool to be passed to another
program during an EXEC CICS XCTL.
System action:
CICS terminates the transaction with abend code A151,
but the region continues.
User response:
Resubmission of the transaction can possibly work. If
not, determine if the transaction is using excessive
amounts of Task-Private Pool (Getmain) storage and
correct this.
Destination:
CSMT
ERZ015030E Unable to redirect debugger IO to
terminal termId, errno errorNumber
Explanation:
CICS is unable to redirect the debugger IO to the
specified terminal. The given terminal was unable to be
opened as a file.
System action:
CICS terminates the transaction with abend code A159.
User response:
Look up the error number in errno.h and investigate the
cause.
Destination:
CSMT
ERZ015031E Program programName in
Transaction transId has a Remote
System Identifier when it is not valid to
have one
Explanation:
114
System action:
If this is the first program in the transaction, CICS does
not start that transaction. If not, CICS returns the
PGMIDERR condition to the calling program.
User response:
Reenable the program and run the transaction again.
Destination:
console.msg
ERZ015033E Transaction transId attempts to run
program programName which is not
defined in the database
Explanation:
CICS attempts to run a program that is not defined.
System action:
If this is the first program in the transaction, CICS does
not start that transaction. If not, CICS returns the
PGMIDERR condition to the calling program.
User response:
Check the Transaction Definition entry (TD), Program
Definition entry (PD) and any application program used
in the transaction with EXEC CICS LINK or EXEC CICS
XCTL commands for errors.
Destination:
CSMT
ERZ015034E CICS is unable to allocate
Task-Private Pool storage for Program
Control data structures
Explanation:
CICS is unable to allocate storage from the Task-Private
Pool, to hold the control information required for running
a new program.
ERZ015035E ERZ015038W
System action:
region continues.
User response:
Resubmission of the transaction can possibly work. If
not, determine if the transaction is using excessive
amounts of Task-Private Pool (Getmain) storage and
correct this.
Destination:
CSMT
ERZ015035E The load of language support
program fileName fails
Explanation:
CICS attempts to load a language support program but
fails. Language support programs are used by CICS to
run application code written in different programming
languages.
System action:
If the attempt to load the C language support program
fails, the region is terminated with abend code U1517. If
the attempt to load another language support program
fails, the transaction is terminated with abend code
A15A.
User response:
Look up any error number in errno.h and investigate
the cause using the symptom records, if any are
available. Check the program being loaded is a valid
executable and is accessible. This error can also occur
if a component of the program is not available, for
example, if an Acu COBOL installation is not in /opt/acu
which is where CICS expects to find it, then Acu
COBOL program loads will fail. Consider reinstalling the
program. Also check the transaction for very deep levels
of EXEC CICS LINKs. If the problem cannot be solved
and persists, then save any dump file produced and
Destination:
console.msg
ERZ015036E Cannot complete Resource Definition
Online (RDO) command for program
programName
Explanation:
CICS cannot delete the details of the named program in
all of the regions Application Servers.
System action:
User response:
Examine the CICS message files for further information
relating to this message. If the delete system RDO
command failed because of a shortage of task private
storage, retry the RDO at a later time, when the system
is more lightly loaded. Also consider simplifying your
transactions, so that they use less task private storage.
If the RDO command failed because of a shortage of

region storage, retry the RDO command at a later time,
when the region is running fewer transactions. Further
consider increasing the amount of region storage
available to your region by amending the
MaxRegionPool attribute of the Region Definition (RD).
If the problem persists, or the RDO command has had
no perceivable effect, consider performing an automatic
start of your region, since the Application Servers are
possibly in an inconsistent state.
Destination:
console.msg
ERZ015037E Exception caught for user exit
(userExitName)
Explanation:
The attempt to invoke or execute a CICS user exit was
unsuccessful.
System action:
User response:
There are two possible causes. Either the attempt to
invoke the user exit program was unsuccessful (signal
4) or there was a processing exception in the user exit
program (signal 11). Examine the RCA user exit table
and TCA user exit table in a dump to determine the
status of the user exit; examine trace to determine the
parameters passed to the user exit and consider
inserting debugging information in the user exit program
(user exit workarea can be used for this). Ensure that
the rules for writing user exit programs were followed.
Destination:
console.msg
ERZ015038W PD stanza for Program
programName has an invalid
UserExitNumber userExitNumber
Explanation:
An invalid value was specified for the user exit number
System action:
CICS installs the PD stanza entry; but no user exit is
activated
User response:
Uninstall the PD stanza, alter the UserExitNumber to a
valid value and reinstall the PD stanza entry into the
run-time. This results in the user exit being activated for
any new Application Servers. It is, however, advisable to
shut down and restart the CICS region when changes
are made to the PD stanza for exit programs.
Destination:
console.msg
115
ERZ015039W ERZ015044W
ERZ015039W PD stanza - Program programName
for user exit
userExitNumber(userExitName)
defined as remote
Determine whether this is by accident or by intent.

Destination:
console.msg
Explanation:
The user exit program MUST be defined as local on this
CICS region
ERZ015042W Program programName now

associated with user exit
userExitNumber (userExitName)
System action:
activated
Explanation:
The user exit is activated for the CICS region.
User response:
Uninstall the PD stanza, alter the PD stanza and
reinstall the PD stanza entry into the run-time. This
results in the user exit being activated for any new
Application Servers. It is, however, advisable to
shutdown and restart the CICS region when changes
System action:
If this is during CICS region initialization then the
program is now activated at this user exit in all
Application Servers; if during run-time then the program
is activated at this user exit for all new Application
Servers, but any existing Application Servers are
reactivated for the program associated with this user
exit when the Application Server was initialized.
Destination:
console.msg
User response:
None
ERZ015040W PD stanza - Program programName

for user exit
userExitNumber(userExitName) not a
C program or does not exist
Explanation:
Either the program is not a C program or the Path is
invalid.
System action:
activated
User response:
Ensure that the program exists in the specified library
and is a C program. Uninstall the PD stanza, alter the
PD stanza and reinstall the PD stanza entry into the
run-time. This results in the user exit being activated for
any new Application Servers. It is, however, advisable to
shutdown and restart the CICS region when changes
Destination:
console.msg
ERZ015041W Processing request to replace
program programName with
programName2 for user exit
Explanation:
The user exit is already active for the CICS region. Only
one program can be associated with a user exit at this
release of CICS.
System action:
CICS replaces the user exit program for all new
Application Servers; any existing Application Server
continues to use the previous user exit program.
User response:
116
Destination:
console.msg
ERZ015043W Attempt to associate program
programName with user exit
userExitNumber failed.
Explanation:
Refer to previous messages for an explanation.
System action:
The user exit is not activated for the CICS region.
User response:
None
Destination:
console.msg
ERZ015044W Program programName no longer
associated with user exit
Explanation:
The user exit is de-actived for the CICS region.
System action:
The PD stanza for the program associated with the user
exit is uninstalled.
User response:
None
Destination:
console.msg
ERZ015045W ERZ016001E
ERZ015045W Attempt to load program
programName for user exit
userExitNumber(userExitName) failed
Explanation:
The program associated with the user exit failed to load
when initializing a new Application Server.
System action:
The user exit is de-activated for the region.
User response:
Refer to previous ERZ5802 messages for further
information. Ensure that the program exists in the library
that was specified on the Path in the PD stanza for the
program. Ensure that the guidelines for naming the
entry point for the application were followed for this
platform. If the user exit program was not compiled by
using the supplied sample makefile, compare the
makefiles to ensure that there are no significant
differences that are able to cause a load failure. It is
advisable to shutdown and restart the CICS region
when changes are made to the PD stanza for exit
programs.
Destination:
console.msg
exit 50 (UE015050) parameter list.
Explanation:
A request to obtain storage in that to build a parameter
list for user exit 50 (UE015050) failed.
System action:
region continues.
User response:
storage available to CICS using the region definition
parameters.
Destination:
console.msg
ERZ015047W User exit 50 (UE015050) has returned
an unrecognized return code, while
attempting to route a link request for
program programName.
Explanation:
Distributed Program Link (DPL) user exit (UE015050)
does not return a recognized return code.
System action:
The link request made for program programName
stops normally. Other processing continues.
Destination:
console.msg
ERZ015048W User exit userExitNumber
(userExitName) has an incorrect
version of the userExitStructure user
exit structure. The user exit has been
disabled.
Explanation:
A user exit structure referenced by the user exit
program has an incorrect version number, when
compared to the version number used by CICS. This
means that the structure used by the user exit was
changed since the user exit program was compiled. The
version number test is performed by the user exit
program and this message is only issued if the user exit
program returned either UE_SpecificVersion or
UE_HeaderVersion. The user exit is disabled for this
application server.
System action:
The user exits default action is taken, and the user exit
is disabled.
User response:
Obtain the latest version of cicsue.h. This contains both
the user exit specific and standard structures. Ensure
that the user exit is compiled by using the latest version
of cicsue.h. Check any fields used by the user exit
program that are contained in a structure that has
changed. A changed version number indicates that the
structure has changed since the previous version. If
cicsue.h was not updated since the user exit program
was compiled, check that the user exit program is
returning either UE_SpecificVersion or
UE_HeaderVersion for the correct reason.
Destination:
console.msg
ERZ016001E Abnormal termination U1601:
Explanation:
The data structures used to drive syncpoint processing
are inconsistent.
System action:
CICS terminates the region with code U1601.
User response:
Where this problem occurs during normal operation of a
region, it can be cleared by auto-starting CICS. If the
problem occurs during auto start following normal
shutdown, perform a cold start. Contact your support
organization if the problem persists.
Destination:
console.msg
User response:
Ensure that your dynamic DPL user exit program
returns a valid return code.
117
ERZ016002W ERZ016009E
ERZ016002W Unsuccessful memory allocation for
logical unit of work control information
Explanation:
CICS is unable to acquire Region Pool storage for the
data structures that control syncpoint processing.
System action:
CICS continues, but this message is likely to be
followed by another that abnormally terminates the task
or region.
User response:
When convenient, stop and auto start CICS with an
increased Region Pool size by overriding the
MaxRegionPool attribute (RD) on the command line. Do
the same for the permanent database by using
cicsupdate.
Destination:
CSMT
ERZ016005E Abnormal termination A165: CICS
internal error
Explanation:
CICS has detected an internal error that has prevented
a logical unit of work from starting or continuing.
System action:
CICS continues after terminating the affected
transaction with abnormal termination code A165 and
terminating the relevant application server process.
User response:
Resubmit the affected transaction. If the problem
Destination:
CSMT
Destination:
CSMT
ERZ016003W Unsuccessful memory allocation for

logical unit of work checkpoint
information
ERZ016006E Abnormal termination U1606: Invalid

information recovered from system log
Explanation:
The system was unable to acquire sufficient Task
Private storage to hold the checkpoint information for
logical units of work.
System action:
Checkpoint information is not logged, but CICS
continues. If CICS suffers an immediate shutdown,
recovery time is impaired. Log Service resource usage
increases.
User response:
Restart CICS (auto-start) when it is convenient to do so.
This action restores optimum recovery performance and
enables some Log Service resources to become
available.
Destination:
console.msg
ERZ016004E Abnormal termination A164: Unable to
start a new logical unit of work
Explanation:
CICS is unable to start a new logical unit of work. This
message is preceded by another message indicating
the reason.
System action:
The affected transaction is terminated with abend code
A164. The application server is also terminated in order
to reduce the possibility of further transactions being
affected by this problem.
User response:
Resubmit the affected transaction. Look at the
preceding error messages to see whether other user
responses are advised.
118
Explanation:
CICS has obtained invalid information from the system
log and is unable to complete recovery processing.
System action:
CICS is terminated with code U1606.
User response:
See message ERZ2407E.
Destination:
console.msg
ERZ016007E Abnormal termination A16Y: Problem
during SYNCPOINT
Explanation:
A problem was detected during a SYNCPOINT that
renders the CICS Application Server process unusable.
System action:
CICS terminates the affected Application Server with
code A16Y, backing out any recoverable work already
performed. CICS also terminates the application server
involved in order to release resources and allow other
tasks to continue.
User response:
Resubmit the affected transaction.
Destination:
console.msg
Unsuccessful memory allocation for
Explanation:
ERZ016010E ERZ016017E
CICS is unable to acquire Region Pool storage for the
data structures needed to process an active logical unit
of work.
System action:
CICS terminates the affected transaction with code
A163, backing out any recoverable work already
performed. CICS also terminates the application server
involved in order to release resources and allow other
tasks to continue.
User response:
Resubmit the affected transaction. If the problem
persists, stop and auto start CICS with an increased
Region Pool size by overriding the MaxRegionPool
attribute (RD) on the command line. Do the same for
the permanent database using cicsupdate.
Destination:
CSMT
Explanation:
During system startup, CICS is unable to acquire
sufficient Region Pool storage for the data structures
needed to process logical units of work.
System action:
CICS is terminated with abend code U1610.
User response:
Restart CICS with an increased Region Pool size. This
can be done by overriding the MaxRegionPool attribute
(RD) on the command line and using cicsupdate to
update the permanent database.
Destination:
console.msg
ERZ016011E Abnormal termination U1611: Unable to
recover CICS resources correctly
Explanation:
CICS is unable to recover CICS resources to the correct
state. This message is preceded by another message
indicating the reason, which was possibly sent to
destination CSMT.
System action:
User response:
See the preceding error message for advice.
Destination:
console.msg
ERZ016012E Abnormal termination U1612: The

effects of a committed transaction
could not be re-applied during restart
Explanation:
During recovery processing at system startup, the
effects of a committed transaction were unable to be
reapplied. This message is preceded by another
message indicating the reason, which was possibly sent
to destination CSMT.
System action:
User response:
See the preceding error message for advice.
Destination:
console.msg
ERZ016014E Abnormal termination U1614: Unable
to release Region Pool storage
Explanation:
CICS is attempting to release a block of Region Pool
storage but is unsuccessful.
System action:
CICS terminates with abnormal termination code U1614.
User response:
Restart CICS. If the problem persists, contact your
Destination:
console.msg
detected some missing data
Explanation:
CICS has detected an error in the Region Control Area
(RCA) that cannot be corrected.
System action:
CICS terminates the Region.
User response:
Destination:
console.msg
detected an unexpected signature
actualSignature in a memory structure
at address structureAddress (expected
signature is expectedSignature)
Explanation:
CICS has detected a signature field containing invalid
data. This message is produced only for memory
119
ERZ016018E ERZ016033E
structures obtained from the region pool so this problem
is not likely to be caused either by user action or by
user transactions.
System action:
User response:
Destination:
console.msg
detected inconsistent data in the
Unique Application Identity Pool
Explanation:
CICS has detected at least one inconsistency in the
Unique Application Identity Pool. Previous messages
detail the inconsistencies detected.
System action:
User response:
Destination:
console.msg
found actualCountu transaction
structures attached to the control
block located at structureAddress
(expected number is expectedCountu)
Explanation:
CICS has detected a mismatch between a counter field
in a control block and the number of elements that are
attached.
System action:
User response:
Destination:
console.msg
ERZ016025E Abnormal termination U1625: Remote
Procedure Call (RPC) protocol protocol
is invalid; Reason reason
Explanation:
CICS is unable to start because the Remote Procedure
Call (RPC) runtime system has rejected a request from
CICS to use the named protocol.
System action:
120
User response:
Verify that the RPC subsystem is correctly installed.
Contact your support organization for further
information.
Destination:
console.msg
ERZ016026E Abnormal termination A16Z: Unable
to initialize application server
Explanation:
CICS is unable to complete the initialization of an
application server. This message is possibly preceded
by a warning message describing the problem in more
detail.
System action:
CICS terminates the application server with code A16Z.
User response:
None. If this problem persists and is causing response
delays, contact your support organization.
Destination:
console.msg
ERZ016030W Unsuccessful memory allocation
from task-private storage
Explanation:
CICS is attempting to acquire a buffer from task-private
storage, but is unable to do so because there is
insufficient memory available. At the time this message
is produced, CICS is performing recovery processing or
server initialization and no user transactions are
permitted to run. This means that all of the task private
storage pool (which is of fixed size) must be available to
CICS for its own use.
System action:
CICS continues, but it is likely that additional messages
follow and that the region or server is terminated.
User response:
Cold start CICS and report the problem to your support
organization.
Destination:
console.msg
to reprepare a logical unit of work
Explanation:
CICS has encountered an internal problem while
attempting to reprepare a logical unit of work. Recovery
processing cannot continue.
System action:
User response:
ERZ016035W ERZ016046E
Destination:
console.msg
ERZ016035W Unable to initialize Transactional
Remote Procedure Call (TRPC) service
Explanation:
CICS is unable to initialize the Transactional Remote
Procedure Call (TRPC) service in a CICS server
process.
System action:
CICS continues but quickly terminates either the
application server process involved or the region if the
process is a recovery process. Further messages are
produced.
User response:
Destination:
console.msg
ERZ016036W Unexpected problem reading system
log during recovery

to register External XA-compliant
Resource Manager with the
Transaction Manager
Explanation:
CICS is unable to register an XA-compliant resource
manager with the Transaction Manager XA Service
because of an internal problem in the Transaction
Manager XA Service code.
System action:
The application server is abnormally terminated with
code U1644.
User response:
There is a limit to the number of XA-compliant resource
managers that can be registered with the Transaction
Manager XA Service. Try reducing the number
registered to see if this is the cause of the problem. If
the problem persists, or if you need to register so many
XA-compliant resource managers, contact your support
organization.
Destination:
console.msg
Explanation:
CICS encountered a problem reading the system log
during recovery processing.

to initialize the Transaction Manager
XA Service
System action:
CICS continues but quickly terminates the region.
Further messages are produced.
Explanation:
CICS is unable to initialize the Transaction Manager XA
Service due to an internal problem in the Transaction
Manager Service code.
User response:
Destination:
CSMT
Transactional Remote Procedure Call
(TRPC) service could not be initialised.
Explanation:
CICS is unable to initialize the Transactional Remote
Procedure Call (TRPC) service in a CICS server
process.
System action:
U1639.
User response:
Destination:
console.msg
System action:
code U1645.
User response:
This is an internal problem to CICS. Contact your
Destination:
console.msg
to find or access an External Resource
Managers XA Support file
Explanation:
CICS cannot locate, or does not have sufficient
permissions to access, an XA Support module for an
External Resource Manager.
System action:
code U1646.
User response:
Check that all SwitchLoadFile attributes in the XAD
database definitions refer to real files and that these
files are readable and executable by the userid cics. If
any attributes are incorrect modify them using the
121
ERZ016047E ERZ016051E
Resource Definitions Online (RDO) commands cicsget,
cicsdelete and cicsadd, or cicsupdate. If the file access
permissions are incorrect, correct them and restart the
transaction.
Check that all Structured File Servers and Distributed

Transaction Processing (DTP) clients are still running.
Restart any that have failed. If the problem persists,
Destination:
console.msg
Destination:
CSMT

to load an External Resource Manager
XA Support file
ERZ016050W Logical unit of work for transaction

transId has been backed out;
Distributed Transaction Service (TRAN)
reason abendReason
Explanation:
CICS is unable to load an External Resource Managers
XA Support file into the application server.
System action:
code U1647.
User response:
Check that you have built the switch load file correctly.
Rebuild it to make sure. If the problem persists, contact
your support organization
Destination:
console.msg
ERZ016048E Abnormal termination A16E: Unable
to allocate storage for registration of
an External Resource Manager
Explanation:
CICS is unable to allocate Region Pool storage for the
registration of an External Resource Manager.
System action:
code A16E.
User response:
When convenient, stop and auto start CICS with an
MaxRegionPool attribute (RD) on the command line. Do
the same for the permanent database using cicsupdate.
Destination:
console.msg
ERZ016049E Abnormal termination A162: Unable to
start a new Logical Unit of Work
Explanation:
CICS is unable to start a new logical unit of work in a
particular application server. A new logical unit of work
was obtained from the Transaction Manager, but it was
already abnormally ended before CICS made it ready
for use.
System action:
code A162.
User response:
122
Explanation:
A logical unit of work for transaction transId was
backed out by CICS. This message is produced only
when the logical unit of work is backed out and there is
no commit in progress. The message is not produced
when CEMT TASK PURGE or FORCEPURGE is used
on the transaction as in this case message ERZ1663W
is produced instead. It can possibly be caused by the
failure of CICS Toolkit components, such as Structured
File Servers or LOG servers, or by the failure of other
Distributed Transaction Processing (DTP) clients, such
as relational database managers, during the logical unit
of work. Note that this message is produced whenever
EXEC CICS SYNCPOINT ROLLBACK is issued as a
normal action by a CICS application program.
System action:
CICS continues, but it is likely that further messages
follow to terminate the transaction.
User response:
Check that all Structured File Servers, log servers and
Distributed Transaction Processing (DTP) clients are still
running. Restart any that have failed. If the problem is
anything other than one of those categorized as a
Client-Specified Abort and the problem persists,
Destination:
CSMT
Exception exceptionText caught
Explanation:
CICS has detected an unexpected fatal exception.
System action:
CICS terminates the region with abend code U1651.
User response:
This is an internal problem in CICS that cannot be
caused by the user. If the problem persists, contact your
Destination:
console.msg
ERZ016052W ERZ016056W
ERZ016052W Initiating abnormal termination of
logical unit of work tid
(GTID=globalTid, LUWID=LUWid,
Transaction=transId, TermId=termId,
UserId=userId)
Explanation:
CICS is initiating the abnormal termination of logical unit
of work tid. Generally this arises because of a CEMT
TASK PURGE or FORCEPURGE operation is being
carried out on the logical unit of work, but it can
possibly also be caused by internal errors in CICS or by
errors in user application code that cause the
transaction to end abnormally (without an explicit
syncpoint).
System action:
CICS abnormally terminates the logical unit of work.
User response:
None. Other messages indicate the reason why the
logical unit of work is being abnormally terminated.
Destination:
CSMT
ERZ016053W
Initiating forced backout of logical

unit of work tid (GTID=globalTid,
LUWID=LUWid, Transaction=transId,
TermId=termId, UserId=userId)
Explanation:
CICS is performing a CEMT SET TASK FORCEPURGE
on a transaction that is in syncpoint, but where the
outcome of the syncpoint is in doubt. The transaction is
specified in the Transaction Definition (TD) database
with an InDoubt attribute of WAIT_BACKOUT. CICS is
therefore forcing the logical unit of work to backout,
before ending the associated transaction. If the
transaction is distributed and other parts of it commit
heuristic damage occurs.
(situations in which parts of a distributed transaction

have committed and other parts have backed out).
System action:
The logical unit of work is forcibly finished. Ability to
detect and report on heuristic damage affecting the
associated transaction is lost.
User response:
None
Destination:
CSMT
to terminate logical unit of work tid
(GTID=globalTid, LUWID=LUWid,
Transaction=transId, TermId=termId,
UserId=userId)
Explanation:
CICS is unable to terminate logical unit of work tid,
because although the logical unit of work is in
syncpoint, it is not in doubt and is not in a state where it
can be forcibly finished.
System action:
This is an internal error condition so CICS terminates
the region with abend code U1655.
User response:
Auto start your region. If the problem persists, contact
Destination:
CSMT
ERZ016056W Heuristic damage detected for logical
User response:
None
Explanation:
CICS has detected heuristic damage affecting the
logical unit of work tid. This means that some parts
(logical units of work) of the transaction have committed
while other parts have backed out.
Destination:
CSMT
System action:
None
System action:
Logical unit of work tid is forcibly backed out.
ERZ016054W
Initiating forced finish of logical unit

of work tid (GTID=globalTid,
Explanation:
on a transaction that is still in syncpoint even though the
local outcome of the syncpoint is known. In this
situation, CICS forcibly finishes the identified logical unit
of work. Once the logical unit of work is finished it is not
possible to detect and report heuristic damage
User response:
Depending on the transaction involved you can possibly
be prepared to ignore this situation. Instead you can
restore the state of database entries and CICS
resources manually so as to fully commit or fully
backout the changes made by the transaction.
Destination:
CSMT
123
ERZ016057W ERZ016065I
ERZ016057W Cannot obtain global transaction
identifier for logical unit of work tid
(Transaction=transId, TermId=termId,
UserId=userId), reason reason
Explanation:
CICS is unable to obtain a global transaction identifier
for the specified logical unit of work.
System action:
CICS continues, but if heuristic damage occurs for the
logical unit of work, or if its outcome is forced (for
example by using CEMT SET TASK FORCEPURGE on
the associated transaction), then CICS is unable to
display the global transaction identifier in the warning
messages produced.
User response:
None. This problem makes it much more difficult to
identify other logical units of work involved in the
distributed transaction and so can possibly affect your
ability to take remedial action if this becomes necessary.
If this problem occurs persistently, contact your support
organization.
Destination:
CSMT
ERZ016058W
Initiating forced commit of logical

Explanation:
on a transaction that is in syncpoint, but where the
outcome of the syncpoint is in doubt. The transaction is
specified in the Transaction Definition (TD) database
with an InDoubt attribute of WAIT_COMMIT. CICS is
therefore forcing the logical unit of work to commit
before ending the associated transaction. If the
transaction is distributed and other parts of it backout
then heuristic damage occurs.
System action:
Logical unit of work tid is forcibly committed and the
associated transaction is then abnormally terminated
(another message accompanies the abnormal
termination).
User response:
None
Destination:
CSMT
ERZ016061I Application server serverId is
repreparing logical unit of work tid
Explanation:
CICS application server serverId is attempting to
reprepare logical unit of work tid.
System action:
124
None
User response:
None
Destination:
console.msg
ERZ016063W Logical unit of work for transaction
transId has been forcibly backed out
Explanation:
A logical unit of work for transaction transId was
backed out by CICS. This can happen either in
response to a CEMT SET TASK FORCEPURGE
command, or during abnormal termination of the task.
System action:
CICS continues, but further messages follow to
terminate the transaction.
User response:
None
Destination:
CSMT
ERZ016064I Application manager is waiting for
application servers to replay log
records
Explanation:
The CICS application manager is waiting for the
application servers it has started to replay the relevant
prepare records thereby repreparing themselves.
System action:
None
User response:
None
Destination:
console.msg
ERZ016065I Application server serverId has
resolved its transactions
Explanation:
CICS application server serverId has resolved its
transactions and is now signalling completion to the
application manager.
System action:
None
User response:
None
Destination:
console.msg
ERZ016070W ERZ016075E
ERZ016070W Unable to release storage buffer at
address bufferAddress
Explanation:
An error occurred while attempting to release task
private storage; the storage was not successfully
deallocated.
System action:
CICS is already processing an error (see accompanying
messages) and so the error handling being performed is
continued.
User response:
Check the CSMT log or console.msg file for associated
information. If other messages indicate that the problem
is an internal error in CICS, contact your support
organization.
Destination:
console.msg
to release task private storage buffer
Explanation:
An error occurred while attempting to release task
private storage; the storage was not successfully
deallocated.
System action:
User response:
organization.
Destination:
console.msg
Application Server terminated
unexpectedly during recoverable work
Explanation:
CICS has detected the unexpected termination of an
application server that was processing unfinished
recoverable work. This can possibly be caused by a
CICS internal error, or the process was possibly
terminated by a System Administrator. It can possibly
also be caused by a transaction that is coded to
terminate processes.
System action:
User response:
organization. Restart the region. If you suspect an
internal problem with CICS, first make sure that the
region is configured to produce a dump.
Destination:
console.msg
ERZ016073I Application server serverId is
repreparing logical unit of work tid for
transaction transId, user userId
Explanation:
CICS application server serverId is attempting to
reprepare logical unit of work tid that was originally
transaction transId run for user userId.
System action:
None
User response:
None
Destination:
console.msg
ERZ016074W A transaction has been rolled back
because the prepare phase timed out
during syncpoint processing. CICS
may be temporarily overloaded
Explanation:
A transaction was rolled back because the prepare
phase timed out during syncpoint processing. This can
be caused by a heavily loaded system or by a failure
during syncpoint of a component in a distributed Logical
Unit of Work.
System action:
A transaction was rolled back.
User response:
Refer to other messages that were issued to
console.msg. Check all components in the logical unit of
work for a failure. If the problem is believed to be due to
system loading, then retry the transaction when system
load has reduced and consult the sections on
performance in the CICS Administration Guide for
information about how to monitor and balance system
load.
Destination:
console.msg
to attach shared memory, reason
reason
Explanation:
CICS is unable to attach shared memory to the finished
function registered with the Distributed Transaction
Service (TRAN).
System action:
CICS terminates the region with abnormal termination
code U1675.
User response:
125
ERZ016076E ERZ016082E
None. If the problem persists, contact your support
organization.
ERZ016079I DB2 loaded as filesystem
Destination:
console.msg
Explanation:
CICS has successfully loaded DB2 for use as its
filesystem.

exit 51 (UE016051) parameter list.
Explanation:
System action:
region continues.
User response:
storage available to CICS using the region definition
parameters.
Destination:
console.msg
ERZ016077W User exit 51 (UE016051) has returned
an unrecognized return code.
Explanation:
This error message is produced if the Syncpoint user
exit (UE016051) does not return a recognized return
code.
System action:
The syncpoint request continues normally.
System action:
None.
User response:
None.
Destination:
console.msg
ERZ016080I SFS loaded as filesystem
Explanation:
CICS has successfully loaded SFS for use as its
filesystem.
System action:
None.
User response:
None.
Destination:
console.msg
ERZ016081E Unsuccessful load of DB2 as
filesystem with return code returnCode
Explanation:
This error message is produced when a failure has
occurred while CICS was trying to load the DB2 as the
filesystem.
User response:
Ensure that your Syncpoint user exit program returns a
valid return code.
System action:
CICS abnormally terminates with code U1681.
Destination:
console.msg
User response:
Examine preceeding messages to diagnose the
problem.
ERZ016078E An error has occurred loading the

Product Definitions
Explanation:
occurred while CICS was trying to load the Product
Definitions.
System action:
Destination:
console.msg
ERZ016082E Unsuccessful load of SFS as
Explanation:
occurred while CICS was trying to load the SFS as the
filesystem.
User response:
problem.
System action:
Destination:
console.msg
User response:
problem.
Destination:
console.msg
126
ERZ016083E ERZ016098E
ERZ016083E Filesystem switch file for DB2 could
not be found
On UNIX the file is called cicsswora. CICS expects to

find the file in directory prodDir/bin. Ensure that it is
there.
Explanation:
This error message is produced when the switchload file
is missing.
Destination:
console.msg
System action:
ERZ016088I Oracle loaded as filesystem
User response:
On UNIX the file is called cicsswdb2. On Windows NT
the file is called cicsswdb2.dll. CICS expects to find the
file in directory prodDir/bin. Ensure that it is there.
Destination:
console.msg
ERZ016084E Filesystem switch file for SFS could
not be found
Explanation:
is missing.
System action:
User response:
On UNIX the file is called cicsswsfs. On Windows NT
the file is called cicsswsfs.dll. CICS expects to find the
file in directory prodDir/bin. Ensure that it is there.
Destination:
console.msg
ERZ016086E Unsuccessful load of Oracle as
Explanation:
occurred while CICS was trying to load Oracle as the
filesystem.
System action:
User response:
problem.
Destination:
console.msg
ERZ016087E Filesystem switch file for Oracle
could not be found
Explanation:
is missing.
Explanation:
CICS has successfully loaded Oracle for use as its
filesystem.
System action:
None.
User response:
None.
Destination:
console.msg
detected inconsistent data in the
Unique Listener Identity Pool
Explanation:
CICS has detected at least one inconsistency in the
Unique Listener Identity Pool. Previous messages detail
the inconsistencies detected.
System action:
User response:
Destination:
console.msg
ERZ016098E Server side transaction support is
only possible with an SFS file system
Explanation:
The Region Definitions attribute ServerSideTran was set
to yes but the facility is not supported with the file
system specified by the FileSystemType attribute.
System action:
CICS startup processing continues, but the region does
not use server-side transaction support.
User response:
Alter the Region Definitions attribute ServerSideTran
and restart the CICS region.
Destination:
console.msg
System action:
User response:
127
ERZ016099E ERZ017006E
Explanation:
inconsistent. One of the reasons for this inconsistency
could be an asynchronous abort during the transaction
run.
System action:
CICS terminates the application server with code A167.
The transaction running at this point in time will fail.
User response:
the transaction and call IBM Service if the problem
persists.
Destination:
console.msg
ERZ017001E The CICS Action Table contains
invalid data
Explanation:
The table holding information about active ABEND,
Attention IDentifier (AID), and condition handlers, in the
Region Pool, contains invalid data.
System action:
The transaction and the application server in which it is
running are both terminated with abend code A171, but
the CICS region continues.
User response:
Because the Action Table is held in the Region Pool it is
unlikely that the invalid data was produced by
application code. It is possible that there are further
inconsistencies in the Region Pool; CICS
self-consistency checking transaction usually detects
this. If the transaction produces a dump file, save it for
possible use by your support organization. If the
Destination:
CSMT
ERZ017002W Unexpected Attention IDentifier (AID)
specified - value: AIDvalue
Explanation:
The named AID is specified on an EXEC CICS
HANDLE AID. CICS does not support this AID.
System action:
The transaction continues and CICS interprets the
command as if the AID was not specified.
User response:
Correct the program.
Destination:
console.msg
128
ERZ017003W Unexpected condition specified value: AIDvalue

Explanation:
The given condition was specified on an EXEC CICS
HANDLE CONDITION or EXEC CICS IGNORE
CONDITION command. CICS does not support this
condition.
System action:
The transaction continues and CICS interprets the
command as if the condition was not specified.
User response:
Correct the program.
Destination:
console.msg
ERZ017005E No memory available for Action Table
Explanation:
CICS was unable to acquire storage to create a new
Action Table from the Region Pool. This table holds
information about active ABEND, Attention IDentifier
(AID), and condition handlers.
System action:
User response:
program, as an Action Table is built for each logical
level. Finally, consider increasing the size of the Region
Pool by restarting the region with an override for the
value of the MaxRegionPool attribute in the Region
Definition (RD).
Destination:
CSMT
ERZ017006E Program programName issued too
many EXEC CICS POP HANDLE
commands
Explanation:
The named application program issued more EXEC
CICS POP HANDLE commands than EXEC CICS
PUSH HANDLE commands.
System action:
CICS returns an INVREQ condition to the application
User response:
Correct the named program.
ERZ017007E ERZ017011E
Destination:
console.msg

ERZ017007E The stack of Action Tables has invalid

data
User response:
program, as Region Pool storage is required for each
Definition (RD).
Explanation:
The stack of tables holding information regarding active
ABEND, Attention IDentifier (AID), or condition handlers
for the transaction at each logical level contains invalid
data.
System action:
User response:
Because the Action Tables are held in the Region Pool
it is unlikely that the invalid data was produced by
application code. It is possible that there are further
inconsistencies in the Region Pool; CICS
self-consistency checking transaction usually detects
this. If the transaction produces a dump file, save it for
Destination:
CSMT
ERZ017008E Invalid program programName1
specified as an ABEND handler by
program programName2
Explanation:
An EXEC CICS HANDLE ABEND PROGRAM command
specified an invalid program as the ABEND handler.
The program is invalid because it is not defined in the
Program Definition (PD) database, or it is disabled, or it
has a remote system identifier attribute in the Program
Definition database entry.
System action:
CICS returns the PGMIDERR condition to the
application and the transaction continues.
User response:
Correct the Program Definition or enable the program,
as appropriate.
Destination:
console.msg
ERZ017009E No memory available for Attention
IDentifier (AID) handling table
Destination:
CSMT
ERZ017010E No memory available for condition
handling table
Explanation:
table for storing condition handlers from the Region
Pool. This occurred during either an EXEC CICS
HANDLE CONDITION or an EXEC CICS IGNORE
CONDITION command.
System action:
running are both abnormally terminated with abend
code A17A, but the CICS region continues.
User response:
program, as Region Pool storage is required for each
Definition (RD).
Destination:
CSMT
Explanation:
table for storing AIDs handlers from the Region Pool.
This occurred during an EXEC CICS HANDLE AID
command.
ERZ017011E Program programName issued an

EXEC CICS HANDLE ABEND RESET
command without previously issuing
an EXEC CICS HANDLE ABEND
command
System action:
Explanation:
See message.
129
ERZ017012E ERZ017016E
System action:
CICS terminates the transaction with an abend code of
APCT.
User response:
Check the program and correct it.
Request a change to the security permissions, or use

another abend handler program.
Destination:
console.msg
Destination:
CSMT
ERZ017015E Abnormal termination U1701. CICS

was unable to allocate storage for
lookup tables
ERZ017012E Program programName received an

unexpected condition conditionNumber
Explanation:
During system startup, CICS was unable to allocate
Region Pool storage for its internal data structures.
Explanation:
A program received a condition that is not a CICS
condition.
System action:
APCT.
User response:
If the transaction produces a dump file, save it for
Destination:
CSMT
ERZ017013E Transaction abnormally terminated
due to error in condition handling
Explanation:
A program issued an EXEC CICS HANDLE ABEND
RESET command without any previous HANDLE
ABEND command, or the program encountered an
unexpected condition. Earlier log message ERZ1711E
or ERZ1712E contains more details.
System action:
APCT.
User response:
Take the action for either ERZ1711E or ERZ1712E,
depending on which message was logged earlier.
Destination:
CSMT
ERZ017014E Access denied to program
programName1, specified as an
ABEND handler by user userId in
program programName2
Explanation:
An EXEC CICS HANDLE ABEND PROGRAM command
specified a program to which the user does not have
security access.
System action:
CICS returns the NOTAUTH condition to the application
User response:
130
System action:
CICS shuts down the Region.
User response:
Increase the size of the Region Pool by restarting the
region with an override for the value of the
MaxRegionPool attribute in the Region Definition (RD).
organization.
Destination:
console.msg
ERZ017016E Abnormal termination A178. CICS was
unable to lock a handle abend program
database entry due to lack of storage
Explanation:
During an EXEC CICS HANDLE ABEND PROGRAM
command, CICS was unable to lock a handle abend
program database entry due to lack of space in the
Region Pool.
System action:
User response:
program, as storage is required for each logical level.
Finally, consider increasing the size of the Region Pool
by restarting the region with an override for the value of
the MaxRegionPool attribute in the Region Definition
(RD).
Destination:
CSMT
ERZ018001E ERZ018007W
ERZ018001E Port portNumber is already in use by
another application
Explanation:
An attempt to bind to an already bound TCP/IP port
portNumber was attempted. TCP/IP allows only one
server at a time to bind to any particular port.
System action:
The cicsteld server terminates.
User response:
Invoke cicsteld with the -P option specifying a different,
unused port number. Use the operating system netstat
command to list port numbers being used.
Destination:
stderr
ERZ018002E Port portNumber is reserved
Explanation:
An attempt to bind to a TCP/IP port portNumber, which
is marked as reserved, has occurred. This is usually a
port number less than 1024.
System action:
User response:
Invoke cicsteld with the -P option specifying a different,
unused port number. Use the operating system netstat
command to list port numbers being used.
Destination:
stderr
ERZ018003I Usage: cicsteld [-r regionName] [-P
portNumber] [-l locale] [-e emulation]
[-t initialTransaction] [-c
clientCodePage] [-s serverCodePage]
[-n netName] [-h hostList] [-v]
Explanation:
You have invoked cicsteld with invalid options.
System action:
The cicsteld server exits.
User response:
Correct the parameters passed to cicsteld.
Destination:
stderr
ERZ018004I Checking current user identity
Explanation:
cicsteld is attempting to check the user identity already
set up before cicsteld was called.
System action:
The cicsteld checks the user identity and then, if it is
valid, attempts to connect to the selected CICS region.
User response:
Wait for the check to complete. If the check fails, check

current identity or use the -p option to pass the identity.
Destination:
Telnet client display.
ERZ018005E This telnet client is unable to support
3270 emulation
Explanation:
The telnet client attempting to connect with the cicsteld
server is unable to emulate any of the known 3270
terminal types or does not specify what type of
terminals it supports.
System action:
User response:
Select an appropriate telnet client that is capable of
emulating a 3270 data stream terminal.
Destination:
stderr
ERZ018006E Transaction transId not submitted -errorString
Explanation:
The submission of the transaction transId was
unsuccessful, returning the supplied error details.
System action:
The transaction specified does not run.
User response:
Check that you entered the correct transaction name. If
so, check that the Transaction Definitions (TD) in the
region database includes the transaction. If the
errorString indicates that a communications failure
occurred, check that the CICS region is still running. If
the CICS region has terminated, end the telnet session
and invoke another.
Destination:
ERZ018007W Option optionName exceeds
maximum allowable length of
maxLength and has been truncated
Explanation:
An option was supplied to the cicsteld that exceeded
the maximum length allowed for that option maxLength.
System action:
The option is truncated to the maximum allowed and the
cicsteld continues initialization.
User response:
Restrict the length of the supplied option so that it does
not exceed the maximum allowable length.
Destination:
131
ERZ018009E ERZ018017E
stderr
User response:
Ensure that the region exists and is running.
ERZ018009E No port number specified and no

service found
Destination:
Explanation:
cicsteld was invoked from the command line with no
port number specified and no entry for cicsteld was
found in the TCP/IP services file. On UNIX this file is
located in directory /etc. On Windows NT this file is
located in direcotry %SystemRoot%system32driversetc.
System action:
The cicsteld server is terminated.
User response:
Restart cicsteld with a port number or ask your system
administrator to add an entry for cicsteld to the services
file.
Destination:
stderr
ERZ018013E Unsuccessful autoinstall of this

terminal -- errorString
Explanation:
cicsteld has attempted to autoinstall this terminal but
has received an error.
System action:
The cicsteld server is terminated after displaying this
message and the user pressing a key.
User response:
Check that a terminal model is available for the terminal
type supplied on the -e option of cicsteld or obtained
from the environment variable TERM.
Destination:
ERZ018010E Invalid port number

Explanation:
cicsteld was invoked from the command line with a port
number that is larger than 65535 or smaller than 0 and
so is invalid for a TCP/IP sockets port.
System action:
The cicsteld server is terminated.
User response:
Restart cicsteld with a port number in the range
0-65535
Destination:
stderr
ERZ018014I Searching for available regions

Explanation:
cicsteld is searching for available CICS regions to
display a selection menu. The cicsteld can take several
seconds before it obtains this information and displays
the region menu.
System action:
cicsteld continues to search for available regions.
User response:
Wait for display of the available regions menu.
Destination:
stderr
ERZ018011E No CICS regions available

Explanation:
cicsteld is unable to find any available CICS regions.
System action:
User response:
Restart cicsteld when a CICS region is available.
Destination:
ERZ018012E Connect to region regionName was
unsuccessful -- errorString
Explanation:
The requested region regionName cannot be
contacted.
System action:
132
ERZ018015I Connecting to region regionName

Explanation:
cicsteld is attempting to contact and connect to the
region regionName.
System action:
The cicsteld server connects to the named CICS region.
User response:
Wait for the connection to be set up.
Destination:
ERZ018017E Telnet client unable to support
options required
Explanation:
The client is unable to support the communications
protocol required by the cicsteld.
System action:
ERZ018018E ERZ018026E
User response:
Select an appropriate telnet client that is capable of
emulating a 3270 data stream terminal.
Destination:
Destination:
stderr
ERZ018022E Invalid selection, position cursor on

selected region
ERZ018018E Connection to telnet client closed

unexpectedly
Explanation:
You have placed the cursor on a line that does not have
a region. Reposition the cursor on the line displaying
the region you wish to connect to.
Explanation:
The client has terminated the connection to the cicsteld
unexpectedly.
System action:
User response:
Check the telnet client is functioning correctly.
Destination:
stderr
ERZ018019E Initialization was unsuccessful
Explanation:
The cicsteld did not successfully initialize due to
memory allocation or system call problem.
System action:
User response:
Report problem to your support organization.
Destination:
stderr
ERZ018020I cicsteld terminated, region shut down
Explanation:
The region that this cicsteld was connected to was shut
down.
System action:
User response:
Wait for the region to be restarted or restart the cicsteld
and select a different region if available.
Destination:
ERZ018021I cicsteld terminated, terminal out of
service
Explanation:
Your terminal is marked as out of service.
System action:
None
User response:
Ask the Administrator to reinstate your hard terminal
and then reinvoke cicsteld.
System action:
None
User response:
Move cursor to the row displaying the region of your
choice.
Destination:
ERZ018023I cicsteld terminated, network
credentials have expired
Explanation:
The login context for this cicsteld process has expired.
Further communication to the CICS region cannot take
place.
System action:
None
User response:
Restart cicsteld. This acquires a new login context.
Destination:
ERZ018025I cicsteld terminated, signal or exception
detected
Explanation:
cicsteld encountered an unexpected signal or exception.
System action:
User response:
Try running the cicsteld again. If the problem recurs,
Destination:
ERZ018026E Conversion between codepages
codePage1 and codePage2 not
supported
Explanation:
The cicsteld did not successfully initialize because
conversion between the codepage codePage1 and
codepage codePage2 is not supported.
System action:
133
ERZ018027E ERZ019001E
User response:
Check that you are supplying valid codepages to
cicsteld and that it is possible to convert between the
two codepages.
Destination:
stderr
ERZ018027E Connect to region regionName was
unsuccessful -- %2$s
Explanation:
There was an unexpected error while attempting to
connect to the requested region regionName.
System action:
User response:
Ensure that the region exists and is running. Ensure
that you have run cicssetupclients. If the region is
available and the problem recurs, contact your support
organization.
Destination:
ERZ018029E Port portNumber : bind failure - bind
returned errorNumber
Explanation:
An attempt to bind to port portNumber was rejected with
an unrecognized error code errorNumber.
System action:
User response:
Consult your telnet documentation to discover the
meaning of errorNumber and correct the condition. If the
error persists, contact your support organization.
Destination:
stderr
ERZ018030E cicsteld has experienced an internal
pipe failure
Explanation:
cicsteld has received an unexpected result from a call to
read data from one of its internal pipes.
System action:
User response:
Restart cicsteld. If the error persists, contact your
Destination:
stderr
ERZ018031I Searching for regions on

machineName
Explanation:
cicsteld is attempting to find CICS regions. The terminal
is now searching on machine machineName.
System action:
cicsteld continues.
User response:
No reponse is necessary.
Destination:
stderr
ERZ018032W Failed to contact CICS RPC listener
on machineName: reason
Explanation:
cicsteld is attempting to find CICS regions.
System action:
cicsteld continues but does not list any CICS regions
from machine machineName.
User response:
Check that the processes are all started.
Destination:
stderr
ERZ018033I Warnings displayed. Hit enter to
continue
Explanation:
cicsteld has displayed warnings relating to attempts to
locate CICS regions on one or more machines. These
messages are displayed until the user hits Enter.
System action:
cicsteld continues after Enter is hit.
User response:
Respond to the warnings displayed and then hit Enter.
Destination:
stderr
ERZ019001E Execution Diagnostic Facility (EDF)
could not update the Terminal
Definition for terminal termId.
Explanation:
EDF attempted to alter EDF control information in the
database entry for the named terminal but was unable
to update the Terminal Definition in the runtime
database.
System action:
EDF continues in the current mode of execution as the
mode was unable to be changed. Any transaction
currently running on the specified terminal continues.
User response:
134
ERZ019002E ERZ019006E
Examine the CICS message files as CICS possibly
wrote other messages that indicate why the attempt to
update the runtime database was unsuccessful.
Destination:
CSMT
could not update the System Definition
for system sysId.
Explanation:
database entry for the named system but was unable to
update System Definition in the runtime database.
System action:
currently attached from the specified system continues.
User response:
update the runtime database was unsuccessful.
Destination:
CSMT
could not read the command-line
arguments from terminal termId.
Explanation:
The CEDF transaction attempted to read command-line
arguments from the principal facility but was
unsuccessful.
System action:
currently being debugged continues.
User response:
read the command-line arguments was unsuccessful.
Try running the CEDF transaction again.
Destination:
CSMT
could not allocate region storage.
Explanation:
An attempt to allocate storage from the Region Pool to
contain EDF control information was unsuccessful. As
memory in the Region Pool is continually being acquired
and freed by CICS on behalf of running transactions,
this is possibly a transient problem that can occur when
CICS is heavily loaded.
CICS terminates the application server with an abend

code of A194. The CICS region continues.
User response:
Try turning EDF on and then running the transaction
again. If this problem persists when you resubmit the
transaction, check whether it is looping in some way
that causes CICS to acquire substantial amounts of
Region Pool memory on its behalf; for example, check
the depth of EXEC CICS LINKs in the program, as
Region Pool memory is required for each logical level.
Finally, consider increasing the size of the Region Pool
by restarting the region with an override for the value of
the MaxRegionPool attribute in the Region Definition
(RD).
Destination:
CSMT
could not read a message from the
CICS message catalog.
Explanation:
An attempt to read an EDF message from the CICS
message catalog was unsuccessful.
System action:
code of A195. The CICS region continues.
User response:
Check that the CICS message catalog for the region is
accessible and has the required permissions. Refer to
operating system documentation for further information
about the use of catalogs.
Destination:
CSMT
could not display a screen on terminal
termId while debugging task
taskNumber. EDF has been turned off.
Explanation:
An attempt to write an EDF screen to the debug
terminal was unsuccessful.
System action:
EDF terminates. The transaction continues but is no
longer debugged by EDF.
User response:
Examine the CICS message files to determine if the
debug terminal is unavailable. If the terminal is out of
service, then set the terminal back in service. If the
terminal is in service, ensure that the terminal and the
connection to it are available. Try turning EDF on and
then running the transaction again.
Destination:
CSMT
System action:
135
ERZ019007E ERZ019011E
could not allocate task-private storage
while debugging task taskNumber. EDF
has been turned off.
Explanation:
An attempt to allocate storage from the Task-Private
Pool in order to display an EDF screen on the debug
System action:
User response:
Try turning EDF back on and then running the
transaction again. If this problem persists when you
resubmit the transaction, determine if the transaction is
using excessive amounts of Task-Private Pool
(GETMAIN) storage and correct this.
Destination:
CSMT
could not create a display map area
Explanation:
An attempt to create part of an EDF map in order to
display an EDF screen on the debug terminal was
unsuccessful. The most probable cause of this problem
is that CICS is short of Task-Private Pool (GETMAIN)
storage.
System action:
User response:
Destination:
CSMT
could not create a display field while
debugging task taskNumber. EDF has
been turned off.
Explanation:
An attempt to create a field in part of an EDF map in
order to display an EDF screen on the debug terminal
was unsuccessful. The most probable cause of this
problem is that CICS is short of Task-Private Pool
(GETMAIN) storage.
System action:
136

User response:
Destination:
CSMT
could not free Task-Private storage
while debugging task taskNumber.
Explanation:
An attempt to free storage that EDF has allocated from
the Task-Private Pool was unsuccessful. The most
probable cause of this problem is that there is
inconsistency in CICS internal memory pointers, in
which case the transaction is abnormally terminated.
System action:
If the attempt to free the storage was unsuccessful
because CICS internal memory pointers are inconsistent
then the transaction is abnormally terminated.
Otherwise, EDF and the transaction continue.
User response:
Examine the CICS message files to determine why the
storage was not freed. If the transaction was abnormally
terminated use the transaction dump to investigate this
problem. It is possible that user application code is
writing to a storage area allocated to CICS internal use.
Check the use made of pointers to GETMAIN storage in
your application. If other messages indicate that the
problem is a software error in CICS then save any
dump file produced and contact your support
organization.
Destination:
CSMT
could not read from terminal termId
Explanation:
An attempt to read user input to an EDF screen
displayed on the debug terminal was unsuccessful.
System action:
User response:
connection to it are available. If the emulator process for
ERZ019012E ERZ019016E
the debug terminal is still running, try turning EDF on
and then running the transaction again.
Destination:
CSMT
could not refresh a display map while
debugging task taskNumber. EDF has
been turned off.
Explanation:
An attempt to refresh an EDF map field in order to
display an updated EDF screen on the debug terminal
was unsuccessful.

database entry for the named system but was unable to
access the System Definition in the runtime database.
System action:
code of A19E. The CICS region continues.
User response:
access the runtime database was unsuccessful.
Destination:
CSMT
System action:

could not access the runtime database
entry for resource resourceName.
User response:
refresh the map was unsuccessful. If the transaction
was abnormally terminated use the transaction dump to
investigate this problem. It is possible that user
application code is writing to a storage area allocated to
CICS internal use. Check the use made of pointers to
GETMAIN storage in your application. If other
messages indicate that the problem is a software error
in CICS then save any dump file produced and contact
Explanation:
EDF attempted to access the runtime database entry for
the named terminal or system but was unable to access
the resource in the runtime database.
Destination:
CSMT
System action:
EDF terminates and the transaction is no longer
debugged by EDF. The CICS region continues, but
there is possibly a serious problem with the runtime
database.
User response:
access the runtime database was unsuccessful. There
is possibly a serious problem with the runtime database
that can require restarting the region.

could not access the Terminal
Definition for terminal termId.
Destination:
CSMT
Explanation:
database entry for the named terminal but was unable
to access the Terminal Definition in the runtime
database.

could not communicate with terminal
termId while debugging task
taskNumber. EDF has been turned off.
System action:
code of A19D. The CICS region continues.
User response:
access the runtime database was unsuccessful.
Destination:
CSMT
could not access the System Definition
for system sysId.
Explanation:
Explanation:
EDF attempted to communicate with the debug terminal
but was unsuccessful.
System action:
EDF terminates. The transaction continues but is not
debugged by EDF.
User response:
the debug terminal is still running, try turning EDF on
and then running the transaction again.
Destination:
CSMT
137
ERZ019017E ERZ021002E
ERZ019017E Execution Diagnostic Facility
transaction (CEDF) could not display a
message on terminal termId.
Explanation:
An attempt to write a CEDF message to the debug
System action:
The CEDF transaction continues.
User response:
the debug terminal is still running, try running the CEDF
transaction again.
Destination:
CSMT
ERZ019019E Security violation: User userId on
terminal termId tried to debug
transaction transId but was denied
access. EDF has been turned off.
Explanation:
User userId attempted to debug transaction termId from
the terminal transId but a Transaction Security Level
(TSL) or Resource Security Level (RSL) check failed.
CICS performs TSL validation to verify that the debug
user (the user who is running CEDF), has sufficient
authorization to debug the transaction and, if so,
subsequent RSL validation is performed for both the
user who is running the transaction and the debug user.
One of these security checks failed.
System action:
EDF terminates and displays a Security violation
message on the debug users screen. The user
transaction continues.
User response:
If the debug user is allowed to debug the transaction,
check that both the CEDF transaction and the
transaction to be debugged have the same values for
both the TSLCheck and RSLCheck attributes in the
Transaction Definitions (TD). Also check that both
transactions have TSLKey and RSLKey attribute values
that are defined in the corresponding TSLKeyList and
RSLKeyList for the debug user in the User Definitions
(UD).
Destination:
CSMT
ERZ020001E CICS has been unsuccessful in
communicating with the cicsterm while
trying to display help using
InfoExplorer
Explanation:
138
You requested help, but CICS was not able to

communicate with the cicsterm to display help by using
InfoExplorer.
System action:
No help information is displayed. The transaction
continues.
User response:
Check the connection between CICS and the display.
Check that the emulator process and the application
servers are still running. Then try running the
transaction again.
Destination:
console.msg, CSMT
ERZ020002E CICS has been unsuccessful in
communicating with the terminal while
trying to display help using BMS
Explanation:
You requested help, but CICS was unable to
communicate with the terminal to display help using a
BMS map.
System action:
No help information is displayed. The transaction
continues.
User response:
Check the connection between CICS and the terminal.
Check that the terminal is in service. If not, use the
CEMT transaction to set the terminal back in service.
Destination:
console.msg, CSMT
ERZ020003E CICS has been unable to run the help
program. Press ENTER to continue.
Explanation:
Help has been requested but CICS has been unable to
run the program which displays help (DFHINFO).
System action:
Help is not displayed but other processing continues.
User response:
Check the preceding messages (on the application
owning region) for details of why the help program,
DFHINFO, did not succeed and then follow the actions
for those messages.
Destination:
The users screen.
ERZ021002E Unsuccessful close of file fileName
Explanation:
CICS detected an error when closing a file.
System action:
CICS raises the IOERR or ILLOGIC condition.
User response:
ERZ021004E ERZ021011E
Check the message files for any errors reported by the
file server. Check the File Definitions (FD) entry for the
file.
ERZ021009E File fileName is not CLOSED and

DISABLED, CICS cannot delete it
Destination:
CSMT
Explanation:
An attempt was made to delete a file when it is not
CLOSED and DISABLED.
ERZ021004E Unable to open file fileName
System action:
Explanation:
CICS detected an error when attempting to open a file.
System action:
CICS raises the IOERR or ILLOGIC condition. The file
is marked as CLOSED and UNENABLED.
User response:
file server. Check the File Definitions (FD) entry for the
file.
Destination:
CSMT
ERZ021005E Task timed out while waiting for file
fileName to be opened
Explanation:
While waiting for another task to open the file, the
DeadLockTimeout value (specified in the Transaction
Definition) for this task was exceeded, so the task timed
out.
System action:
The task is abended with the code AKCS.
User response:
file server, which possibly indicate a reason for reduced
response time. Resubmit the transaction.
Destination:
CSMT
ERZ021006E Unable to obtain the Task Control
Area (TCA)
Explanation:
A CICS internal function was not able to locate the TCA.
System action:
User response:
It is not possible to delete a file when it is not CLOSED
and DISABLED. First CLOSE and DISABLE the file
then try again.
Destination:
CSMT
file control information
Explanation:
CICS was attempting to obtain memory for file control
information from the Region Pool. Insufficient memory
was available.
System action:
The transaction is abnormally terminated with the code
A21M.
User response:
This is possibly a transient problem that occurs when
CICS is heavily loaded. Resubmit the transaction. If the
problem persists, you possibly need to reconfigure the
size of the Region Pool and restart CICS.
Destination:
CSMT
file control information
Explanation:
information from the Task-Shared Pool. Insufficient
System action:
The transaction is abnormally terminated with the code
A21M.
User response:
This is an internal error. Contact your support
organization.
User response:
This is possibly a transient problem that occurs when
size of the Task-Shared Pool and restart CICS.
Destination:
console.msg
Destination:
CSMT
139
ERZ021012E ERZ021034E
ERZ021012E Unable to restore File Definitions (FD)
entry to region database
Explanation:
CICS was not able to restore an FD entry to the region
database.
System action:
CICS abnormally terminates the transaction with code
A21R.
User response:
This is an internal CICS error. Contact your support
organization.
Destination:
CSMT or console.msg
Try to identify whether a user transaction overwrote the

data. Otherwise contact your support organization.
Destination:
console.msg
ERZ021032E Corrupt signature detected in FRTE
(address address); expected
actualSignature
Explanation:
CICS detected an inconsistency in its internal data
structures.
System action:
ERZ021013E Unable to find a File Definitions (FD)

entry in the region database
User response:
Explanation:
CICS was not able to locate an FD entry in the region
database.
Destination:
console.msg
System action:
A21S.
User response:
This is an internal CICS error. Contact your support
organization.
Destination:
CSMT or console.msg
ERZ021014I Unable to obtain File Definition (FD)
entry fileName from the region
database
Explanation:
CICS was not able to retrieve an FD entry from the
region database. It was probably deleted.
System action:
Processing continues.
User response:
None
Destination:
CSMT
detected an inconsistency in the CICS
internal data structures - details are in
the next message
Explanation:
CICS detected an inconsistency in its internal data
structures.
System action:
User response:
140
ERZ021033E FRTEcountu FRTEs exist (in structure

address address) for closed and
disabled file
Explanation:
The structure whose address is shown has one or more
FRTEs for a closed/disabled file.
System action:
User response:
Destination:
console.msg
ERZ021034E Maintained count of FRTEs
FRTEcountu different from the actual
number of FRTEs actualFRTEnumberu.
(Address of culprit structure address)
Explanation:
The structure whose address is shown has a
mismatched count of FRTEs.
System action:
User response:
Destination:
console.msg
ERZ021035E ERZ021055E
ERZ021035E Corrupt signature detected in File
Control Module data structure (address
address, occurring in TCA address
TCAaddress); expected
actualSignature
Explanation:
The indicated File Control structure has a corrupt
signature.
System action:
User response:
Destination:
console.msg
ERZ021050W CICS has ignored request to make
UPDATABLE file fileName
NOTREADABLE
Explanation:
Request to make an UPDATABLE file (as defined in the
File Definitions (FD) database) NOTREADABLE was
ignored. The file remains READABLE.
System action:
CICS makes the file readable and continues normally.
User response:
If you need to make the file NOTREADABLE then
ensure it is first NOTUPDATABLE.
Destination:
CSMT
ERZ021051W CICS has ignored request to make
BROWSABLE file fileName
NOTREADABLE
Explanation:
Request to make a BROWSABLE file NOTREADABLE
was ignored. The file remains READABLE.
System action:
CICS makes the file readable and continues normally.
User response:
If you need to make the file NOTREADABLE then
ensure it is first NOTBROWSABLE.
Destination:
CSMT
ERZ021052I Opening files ...
Explanation:
CICS has started opening all the files that are defined
as open and enabled.
CICS is continuing to initialize.

User response:
Wait until initialization is complete.
Destination:
console.msg
ERZ021053I ... file opening completed
Explanation:
CICS has finished opening all the files that are defined
as open and enabled.
System action:
CICS is continuing to initialize.
User response:
Wait until initialization is complete.
Destination:
console.msg
ERZ021054W Unsuccessful memory deallocation of
file buffer
Explanation:
An error occurred while CICS was attempting to release
a memory buffer used during the last file operation.
System action:
This message is logged but processing continues.
User response:
is a software error in CICS then contact your support
organization.
Destination:
CSMT
Explanation:
System action:
will abend.
User response:
Destination:
console
System action:
141
ERZ022139E ERZ023005E
ERZ022139E
System error errorCode while taking

backup of file storing data for
extrapartition Transient Data (TD)
queue TDQname.
Explanation:
CICS detected an error when taking the backup of the
file used to store data for the indicated queue. While
backing up the TDQ Extrapartition File cics renames the
existing file to filename.timestamp CICS shows the error
number returned from the rename call.
System action:
CICS does not proceed ahead with the backup and
continues to write the record in current EP TDQ File.
User response:
Check the error number and take suitable corrective
action. The most likely error is that the file access
permissions are incorrect If you cannot solve the
problem, contact your support organization.
Destination:
console.msg
ERZ023001I Temporary Storage Queue Aging:
Queue queueName deleted
ERZ023003E Temporary Storage (TS): Queue name

queueName is too long
Explanation:
Temporary Storage (TS) queue name queueName
exceeds the maximum allowed length of 8 bytes.
System action:
If the error occurs during region startup then CICS does
not install the invalid TS template, but processing
continues. If the error occurs during a Resource
Definition Online (RDO) session then the RDO
operation is terminated.
User response:
Reduce length of queue name queueName.
Destination:
stderr and console.msg
ERZ023004E CICS-private Temporary Storage
Queue aging transaction (CAGE)
already running; Quitting...
Explanation:
The CICS-private Temporary Storage Queue aging
transaction (CAGE) is already running at the moment;
this instance of the transaction is not needed.
Explanation:
Confirmation that the queue queueName has been
purged by the CICS-private Temporary Storage Queue
Aging transaction (CAGE).
System action:
CICS terminates subsequent (duplicate) invocations of
CAGE.
System action:
CAGE continues processing.
User response:
Investigate why an earlier invocation of this transaction
is apparently already running.
User response:
None
Destination:
CSMT
ERZ023002W Temporary Storage Queue Aging:
Unsuccessful attempt to delete queue
queueName
Explanation:
Temporary Storage Queue Aging transaction (CAGE)
detected an error when attempting to purge the queue
queueName. The problem affects just the one queue
and so CAGE allows queue aging to continue after
producing this diagnostic.
System action:
The queue queueName is not deleted and CAGE
continues queue aging of other queues. CAGE makes
further attempts to delete this queue the next time that
CAGE runs.
User response:
Refer to any previous messages relating to the attempt
to delete this queue.
Destination:
CSMT
142
Destination:
console.msg
ERZ023005E Temporary Storage (TS): Error writing
item itemNumber to queue queueName
Explanation:
A Temporary Storage (TS) write or rewrite operation on
the TS queue queueName was unsuccessful.
System action:
If this message has been produced while processing a
CICS Temporary Storage API, then an IOERR condition
is returned. Otherwise refer to the System Actions of
any subsequent messages.
User response:
CICS Temporary Storage API, your program specifies
how the IOERR condition is handled. Otherwise refer to
the User Responses of any subsequent messages.
Destination:
console.msg
ERZ023006E ERZ023013W
ERZ023006E Temporary Storage (TS): Error
reading item itemNumber from queue
queueName
Explanation:
A Temporary Storage (TS) read operation on the TS
queue queueName was unsuccessful.
System action:
User response:
Destination:
console.msg
ERZ023007E Temporary Storage (TS): Error
deleting item(s) from queue
queueName
Explanation:
Temporary Storage (TS) was unable to remove item(s)
from the queue when deleting the queue queueName.
System action:
CICS marks the queue as deleted and assumes that its
resources were purged. If this message has been
produced while processing a CICS Temporary Storage
API, then an IOERR condition is returned. Otherwise
refer to the System Actions of any subsequent
messages.
User response:
Destination:
console.msg
ERZ023010E Temporary Storage (TS): File server
error

Refer to any previous messages detailing what file
system error has occurred.
Destination:
console.msg
ERZ023011W Unsuccessful attempt to start
CICS-private Temporary Storage Aging
transaction (CAGE)
Explanation:
CICS detected an error when attempting to start the
Temporary Storage Aging transaction, CAGE.
System action:
CICS continues but CAGE is not run in this region
instantiation.
User response:
Check the file access permissions for running CAGE,
and check that a valid permanent database Transaction
Definition (TD) entry exists for CAGE. Restart the region
at the earliest possible opportunity so that TS queue
aging can be performed.
Destination:
console.msg
Unsuccessful allocation of Region Pool
memory for Temporary Storage (TS)
Explanation:
CICS is unable to allocate enough memory, from the
Region Pool, to initialize Temporary Storage (TS).
System action:
U2312.
User response:
You can increase the size of the Region Pool available
by restarting the region and overriding the
MaxRegionPool attribute, with a larger value, on the
command line.
Destination:
console.msg
Explanation:
CICS detected an error when attempting to obtain a file
handle for use by Temporary Storage.
ERZ023013W CICS-private Temporary Storage

Aging transaction (CAGE): Queue age
limit of TSQageLimit is too low,
ageLimitUsed days used instead.
System action:
Explanation:
The regions TSQAgeLimit attribute value TSQageLimit
is too low. CICS-private Temporary Storage Aging
transaction (CAGE) has used the minimum age limit
permitted.
User response:
System action:
User response:
143
ERZ023014E ERZ023019E
Increase the value of the TSQAgeLimit attribute in your
regions permanent database Region Definitions using
Resource Definition Online (RDO).
Destination:
console.msg
ERZ023014E Temporary Storage (TS): Queue Name
queueName has Remote Name
remoteName of different length
Explanation:
Queue name length is different from the length of its
remote name. Both names must be of the same length.
System action:
The queue is removed from the runtime database.
User response:
Update the permanent database entry for queueName
and make the remote name of the queue the same
length as the queues name or delete the queue and
add a new one with a name whose length is the same
as that of the remote name.
Destination:
console.msg
Temporary Storage (TS) Logical Unit of
Work (LUW) Chain at address
corruptLUWaddress in TCA at
TCAaddress.
Explanation:
CICS self-consistency checking has detected that the
chain of queues involved in the current LUW for the
transaction has been overwritten by invalid data.
System action:
U2315.
User response:
Restart the region. If CICS self-consistency checking
continues to detect inconsistencies contact your support
organization.
Destination:
console.msg
detected a Signature inconsistency:
expected expectedSignature found
actualSignature at address
signatureAddress
Explanation:
signature actualSignature is inconsistent with that
expected expectedSignature.
System action:
144

User response:
Restart the region at the earliest possible opportunity. If
CICS self-consistency checking continues to detect
inconsistencies contact your support organization.
Destination:
console.msg
ERZ023017I Processing temporary storage queues
...
Explanation:
CICS is now performing startup processing of temporary
storage queues. This step occurs after log file
processing has been completed and hence after queues
have been recovered from the log.
System action:
User response:
None
Destination:
console.msg
detected a zero length Temporary
Storage (TS) SET buffer at address
bufferAddress in the TCA at TCAaddress
Explanation:
Temporary Storage (TS) SET buffer length stored at
address bufferAddress has been overwritten with an
invalid value of 0.
System action:
User response:
Destination:
console.msg
Temporary Storage (TS) initialization
could not rewrite the Temporary
Storage (TS) runtime database entry
for queue queueName
Explanation:
CICS was not able to rewrite the runtime database TS
entry queueName.
System action:
U2319.
User response:
ERZ023020E ERZ023024I
Refer to any previous messages indicating why the
runtime database entry queueName was not able to be
updated.
timeout is reached. If the transactions deadlock timeout

is reached then the transaction is abnormally terminated
with code AKCS (or AEIR).
Destination:
console.msg
User response:
Delete any MAIN TS queues that are no longer
required. Try to identify particular transactions using
large amounts of Task-Shared Pool storage. Try to run
these at times of low system activity, or reduce their
storage requirements. If many transactions are affected,
reduce the number of application servers running.
Alternatively increase the size of your Task-Shared Pool
by changing the value of the MaxTSHPool attribute in
the Region Definitions.
ERZ023020E Temporary Storage (TS):

Unsuccessful checkpoint - unable to
allocate Region Pool memory
Explanation:
CICS was not able to checkpoint the Temporary Storage
(TS) state information because it was unable to allocate
Region Pool memory.
System action:
The system log does not checkpoint successfully. CICS
can possibly take significantly longer to perform
recovery processing during startup.
User response:
Region Pool memory was not able to be allocated. You
can increase the size of the Region Pool available by
restarting the region and overriding the MaxRegionPool
attribute, with a larger value, on the command line.
Destination:
console.msg
ERZ023021W Unsuccessful attempt to reschedule
CICS-private Temporary Storage Aging
transaction (CAGE)
Explanation:
The CICS-private Temporary Storage Aging transaction
(CAGE) transaction cannot reschedule itself to run the
following midnight.
System action:
The current CAGE transaction continues processing, but
CAGE is not run again during this instantiation of the
region.
User response:
Restart the region at the earliest possible opportunity.
Destination:
console.msg
ERZ023022E Temporary Storage (TS): NOSPACE
condition on MAIN queue queueName
Explanation:
CICS raised a NOSPACE condition for the Main (TS)
queue queueName.
System action:
CICS periodically retries the operation that resulted in
NOSPACE until sufficient space becomes available and
the operation succeeds or the transactions deadlock
Destination:
CSMT
ERZ023023E Temporary Storage (TS): NOSPACE
condition on Auxiliary queue
queueName
Explanation:
CICS raised a NOSPACE condition for the Auxiliary
(TS) queue queueName.
System action:
CICS periodically retries the operation that resulted in
NOSPACE until sufficient space becomes available and
the operation succeeds or until the transactions
deadlock timeout is reached. If the transactions
deadlock timeout is reached then the transaction is
terminated with abend code AKCS.
User response:
Delete any Auxiliary TS queues that are no longer
required. Try to identify particular transactions using
large amounts of File Space. Try to run these at times
of low system activity, or reduce their storage
requirements. If many transactions are affected, reduce
the number of application servers running.
Destination:
CSMT
ERZ023024I Temporary Storage (TS): NOSPACE
condition resolved on queue
queueName
Explanation:
CICS resolved the NOSPACE condition for the queue
queueName.
System action:
User response:
None
Destination:
CSMT
145
ERZ023025W ERZ023030E
ERZ023025W Temporary Storage (TS): Invalid
database entry resourceName
removed from runtime database
Explanation:
During initialization, CICS has found and deleted an
invalid Temporary Storage (TS) entry from the runtime
database. A message has already been generated that
indicates why the entry is considered invalid.
System action:
The invalid entry is deleted from the runtime database.
User response:
Refer to the previous message detailing why the entry is
considered invalid.
Destination:
console.msg
ERZ023026E Temporary Storage (TS): Vetoed
attempt to insert entry resourceName
since RemoteName remoteName does
not have the same length
Explanation:
CICS has vetoed the insertion of a Temporary Storage
(TS) entry into the runtime database because the queue
name length is different from the length of its remote
name. The names must be of the same length.
System action:
The TS queue entry is not added to the runtime
database.
User response:
Retry with the TS queues name and its RemoteName
attribute having the same length.
Destination:
console.msg
ERZ023027W Temporary Storage (TS):
Non-recoverable queue resourceName
not restored following abnormal
termination of a region
Explanation:
CICS has vetoed the addition of the Temporary Storage
(TS) entry resourceName into the runtime database
because non-recoverable queues are not restored on
region startup following an abnormal termination.
System action:
The entry resourceName is not added to the runtime
database.
User response:
None
Destination:
console.msg
146
ERZ023028I Temporary Storage queues have been

processed!
Explanation:
CICS startup processing of temporary storage queues
has now finished.
System action:
None
User response:
None
Destination:
console.msg
Temporary Storage (TS) initialization is
unable to restore queue queueName
Explanation:
CICS cannot insert a runtime database entry
queueName during Temporary Storage (TS) restoration
of queues from the system log.
System action:
U2329.
User response:
Restart the region. If the error continues to occur then
COLD start the region.
Destination:
console.msg
ERZ023030E Temporary Storage (TS): Cannot open
File Server serverName, Filename
fileName, Index indexName
Explanation:
CICS was unable to obtain a file handle for the
specified file.
System action:
User response:
how the IOERR condition is handled. Check that the file
server serverName is running and that the file name
fileName and index name indexName are configured
on that server.
Destination:
console.msg
ERZ023031E ERZ023038W
ERZ023031E Unsuccessful TS queue recovery unable to allocate Region Pool memory
Explanation:
CICS was unable to restore recoverable Temporary
Storage (TS) queues because it was not able to allocate
Region Pool memory.
System action:
The region is abnormally terminated.
User response:
Region Pool memory was not able to be allocated. You
Destination:
console.msg
ERZ023032E Unable to uninstall Temporary
Storage Queue queueName as it is not
a definition template
Explanation:
An attempt to uninstall the Temporary Storage (TS)
Queue queueName failed because it is a derived
queue (created by an EXEC CICS WRITEQ TS
command), not a definition template.
System action:
The TS Queue remains installed in the region.
User response:
Ensure the correct TS Queue is specified. To remove a
TS Queue from the region use the EXEC CICS
DELETEQ TS command.
Destination:
console.msg
ERZ023033E Unable to uninstall Temporary
Storage Queue definition queueName
as there is an underlying queue which
contains data
Explanation:
An attempt to uninstall Temporary Storage (TS) Queue
definition queueName failed because a TS Queue
containing data exists with the same name. The
definition cannot be removed from the region until the
Queue is deleted.
System action:
The TS Queue definition remains installed in the region.
User response:
Ensure the correct TS Queue is specified. Remove the
TQ Queue data with the EXEC CICS DELETEQ TS
command, then retry the uninstall of the definition.
Destination:
console.msg

Temporary Storage (TS) checkpoint
buffer size inconsistency
Explanation:
The size of the Temporary Storage (TS) checkpoint
buffer, read from the system log, has been overwritten.
It is the wrong size.
System action:
U2334.
User response:
Cold Start the region.
Destination:
console.msg
Unsuccessful attempt to empty file Server serverName, File fileName
Explanation:
CICS was not able to empty the file fileName when
trying to open it.
System action:
User response:
how the IOERR condition is handled. Check that the file
server serverName is running and that the file name
fileName is configured on that server. Refer to any
previous messages detailing errors in opening or
emptying the file. You possibly need to manually resolve
in-doubt transactions, and retry the cold start.
Destination:
console.msg
ERZ023038W Temporary Storage (TS): Detected
inconsistency between the checkpoint
data and existing data for queue
queueName
Explanation:
During startup, when processing the system log CICS
attempted to restore the state of queue queueName
from checkpoint data. The existing queue data was
found to be inconsistent with that in the system log and
the queue data was overridden with that in the system
log.
System action:
User response:
None
147
ERZ023040I ERZ023045E
Destination:
console.msg
ERZ023040I Temporary Storage (TS): No queues
found, so no TS queues to be
recovered
Explanation:
CICS was not able to find any Temporary Storage (TS)
entries defined after startup and system log checkpoint
processing, or during shutdown.
System action:
CICS does not know about any TS queues and
therefore does not recover or setup recovery data for
Temporary Storage.
User response:
None
Destination:
console.msg
Temporary Storage (TS) template
templateName at address
templateAddress: Unknown Status value
statusValue
Explanation:
CICS Temporary Storage (TS) self consistency checking
has found a TS queue template templateName whose
Status attribute value, statusValue, is invalid.
System action:
CICS recovers the inconsistent Status attribute value to
TEMPLATE and continues self-consistency checking.
User response:
Shutdown and restart CICS as soon possible, because
the integrity of the system can no longer be assured.
Destination:
console.msg
Temporary Storage (TS) queue runtime
database entry queueName at address
entryAddress: Unknown Status value
statusValue
Explanation:
has found a TS queue queueName runtime database
entry whose Status attribute value, statusValue, is
invalid.
System action:
U2342.
User response:
148
Restart the CICS region.

Destination:
console.msg
Temporary Storage (TS) queue
queueName: Pointer actualPointer,
recovered to expectedPointer
Explanation:
has found an internal pointer to be inconsistent with its
expected value.
System action:
CICS recovers the inconsistent pointer and continues
self-consistency checking.
User response:
Shutdown and restart CICS as soon as possible,
because the integrity of the system can no longer be
assured.
Destination:
console.msg
queueName: Item count actualCount,
recovered to expectedCount
Explanation:
has found the main Temporary Storage queues item
count inconsistent with the number of items in the
queue.
System action:
CICS recovers the queues item count to the number of
items in the queue and continues self-consistency
checking.
User response:
assured.
Destination:
console.msg
queueName: Item number
actualItemNumber, recovered to
expectedItemNumber
Explanation:
has found a main Temporary Storage queues item
number inconsistent with its position in the queue.
ERZ023046E ERZ023051E
System action:
CICS recovers the queues item number to match its
position in the queue and continues self-consistency
checking.
User response:
assured.
Destination:
console.msg
ERZ023046E Temporary Storage (TS): Unable to
write to Auxiliary queue queueName
Explanation:
CICS detected an unexpected return code from CICS
file support and was unable to write to the auxiliary
queue queueName.
System action:
CICS can abnormally terminate the transaction with
code A23F.
User response:
Delete the named queue from CICS and abnormally
terminate any transactions using the queue. Refer to
any file support messages that preceded this message.
Destination:
console.msg
read Auxiliary queue queueName
Explanation:
file support and was unable to read from the auxiliary
queue queueName.
System action:
code A23G.
User response:
Delete the named queue from CICS and abnormally
terminate any transactions using the queue. Refer to
any file support messages that preceded this message.
Destination:
console.msg
queueName: Auxiliary queue contains
Main queue data
Explanation:
CICS self-consistency checking has found an auxiliary
Temporary Storage (TS) queue containing main TS
queue data.

U2348.
User response:
Destination:
console.msg
ERZ023049E Unable to access Temporary Storage
(TS)
Explanation:
CICS was unable to provide access to auxiliary
Temporary Storage (TS) queues. This is possibly
caused by an unexpected response from CICS file
support while trying to open a file for auxiliary queues.
System action:
A23E.
User response:
Refer to the preceding message(s) that detail why CICS
was unable to access auxiliary TS queues.
Destination:
console.msg
ERZ023050E Invalid Temporary Storage (TS) File
server configuration - Server
serverName, File fileName, Index
indexName
Explanation:
The File server serverName configuration for auxiliary
Temporary Storage (TS) file fileName is not keyed
access and CICS cannot use it for TS processing.
System action:
Temporary Storage queues are unavailable until you
correct this problem.
User response:
Correct the configuration of the File fileName to keyed
access.
Destination:
console.msg
delete Auxiliary queue queueName
Explanation:
file support and was unable to delete the auxiliary
queue queueName.
System action:
code A23T.
User response:
System action:
149
ERZ023052E ERZ023057E
Abnormally terminate any transactions using the queue.
Refer to any file support messages that preceded this
message.
System action:
U2354.
Destination:
console.msg
User response:
organization.

detected an inconsistent Temporary
Storage (TS) SET buffer length of
bufferSize, at address bufferAddress in
the TCA at TCAaddress
Explanation:
CICS self-consistency checking has detected an invalid
SET buffer length bufferSize. It is supposed to be zero
because there is no SET buffer. The SET buffer length
has been recovered to 0.
System action:
User response:
Shutdown and restart CICS as soon as possible. If
Destination:
console.msg
detected an inconsistent Temporary
Storage (TS) count of LUW blocks
LUWcountu that is different from actual
number of blocks actualLUWcountu in
TCA at TCAaddress
Explanation:
CICS self-consistency checking has found a mismatch
between maintained count of LUWs and actual number
of LUWs.
System action:
U2353.
User response:
organization.
Destination:
console.msg
detected an invalid Temporary Storage
(TS) internal address invalidAddress in
queue entry at queueEntryAddress
Explanation:
CICS self-consistency checking has found an invalid
address to the Temporary Storage (TS) private
management data on queue entry at
queueEntryAddress.
150
Destination:
console.msg
queueName: Unknown queue type
queueType in private data at address
dataAddress
Explanation:
CICS self-consistency checking has found an unknown
Temporary Storage (TS) queue type in its internal
management data.
System action:
U2356.
User response:
organization.
Destination:
console.msg
queueName: Queue is Indoubt but is
not Recoverable in private data at
address dataAddress
Explanation:
CICS self-consistency checking has found an
inconsistency in the state of the Temporary Storage
(TS) queue queueName. It is not a recoverable queue
yet its state is INDOUBT.
System action:
U2357.
User response:
organization.
Destination:
console.msg
ERZ023058E ERZ023065I
queueName: Unknown queue Action
queueAction in private data at address
dataAddress
Explanation:
CICS self-consistency checking has found an unknown
Temporary Storage (TS) queue action queueAction in its
internal management data.
System action:
U2358.
User response:
organization.
Destination:
console.msg
detected an invalid Temporary Storage
(TS) SET Buffer address bufferAddress
in TCA at [TCAaddress]: Recovered it
to NULL and SET buffer size to zero
Explanation:
CICS self-consistency checking has found an invalid
SET Buffer memory pointer. It is recovered to NULL and
the SET buffer length set to zero.
System action:
User response:
assured.
Destination:
console.msg
ERZ023062E Abnormal Termination U2362: Unable
to access Auxiliary Temporary Storage
(TS) queues
Explanation:
CICS was unable to provide access to auxiliary
Temporary Storage (TS) queues.
System action:
U2362.
User response:
Refer to the preceding message(s) that detail why CICS
was unable to access auxiliary TS queues. Restarting
the auxiliary TS queue File Server(s) can enable access
to TS queues. If the problem persists it is likely that the
configuration of the TS queue File Server(s) is suspect.
Destination:
console.msg
ERZ023063I CICS has successfully deleted an
Auxiliary Temporary Storage (TS)
queue by suppressing a deadlock
timeout
Explanation:
The file server timed out a request to access the file
which contains Temporary Storage (TS) queues. CICS
was able to suppress this error by logically deleting the
queue.
System action:
CICS has successfully deleted the queue. This can
result in inefficient use of disk space.
User response:
CICS continues normally. If disk space becomes short,
then cold starting CICS possibly frees some disk space.
Destination:
console.msg
ERZ023064E The Temporary Storage (TS) file
fileName on server serverName has
an invalid definition
Explanation:
One of the system files that contain temporary storage
queues has an invalid definition. When you configure a
file server for a region, CICS creates these files. The
definition of these files must be that which CICS
creates. The only SFS attribute which you can configure
is the maximum number of records in the file.
System action:
Temporary Storage queues are unavailable until you
correct the problem.
User response:
Recreate the system file server file that is in error. You
can do this by configuring your file server for your
region.
Destination:
console.msg
ERZ023065I CICS has successfully deleted an
Auxiliary Temporary Storage (TS)
queue by suppressing a
communications error
Explanation:
CICS received a communications error from the file
server when attempting to access the file which
contains Temporary Storage (TS) queues. CICS was
able to suppress this error by logically deleting the
queue.
System action:
CICS has successfully deleted the queue. This can
result in inefficient use of disk space.
151
ERZ023070E ERZ023075E
User response:
CICS continues normally. If disk space becomes short,
then cold starting CICS possibly frees some disk space.
Destination:
console.msg
User response:
Examine accompanying messages to determine the
nature of the problem. If the problem cannot be
rectified, a cold start is required.
Destination:
console.msg
ERZ023070E Unable to open file fileName to

perform recovery processing for
Recoverable Temporary Storage
queues
ERZ023073E Unable to read data from file

fileName to recover Temporary
Storage queues
Explanation:
CICS cannot obtain the data needed for recovery
processing of Temporary Storage queues, as it is
unable to open the file containing the data.
Explanation:
CICS was unable to obtain data from the file containing
Transient Data recovery information, so is unable to
recover Temporary Storage queues.
System action:
System action:
User response:
Examine accompanying messages to determine why the
file cannot be opened. If the file is damaged, a backup
copy of the file can possibly be made available. If the
problem cannot be resolved, a cold start is required.
User response:
Examine accompanying messages to determine the
nature of the problem with the file. If the problem cannot
be rectified, a cold start is required.
Destination:
console.msg
ERZ023071E Unsuccessful buffer storage
allocation for recovery of Temporary
Storage queues
Explanation:
CICS was unable to allocate sufficient storage from the
task private storage pool, when attempting to recover
Temporary Storage during an auto start after a region
failure.
System action:
User response:
Increase the size of the task private storage pool by
increasing the value for the MaxTaskPrivatePool
attribute in the Region Definitions, and retry the auto
start. Alternatively, perform a cold start.
Destination:
console.msg
ERZ023072E Abnormal Termination U2372:
Recovery of Temporary Storage
Queues failed
Explanation:
CICS was unable to recover data required to provide
Temporary Storage queues. This data is stored in the
files which contain Temporary Storage queue records.
The region is unable to continue without recovery of this
data.
System action:
Region startup is abnormally terminated
152
Destination:
console.msg
ERZ023074I Recovery of Temporary Storage
queues is complete
Explanation:
CICS has completed recovery processing for Temporary
Storage queues.
System action:
None
User response:
None
Destination:
console.msg
ERZ023075E CICS is unable to save recovery
information for Temporary Storage
queue TSQname
Explanation:
CICS is unable to save information about operations on
recoverable Temporary Storage queues at transaction
syncpoint. If the transaction were allowed to complete,
CICS is possibly unable to recover the queue after a
subsequent failure.
System action:
The Logical Unit of Work is rolled back.
User response:
Other messages indicate the cause of the problem. The
recovery information is written to the filesystem, so
there is possibly a filesystem error reported before this
error.
Destination:
ERZ023076E ERZ023093E
console.msg
CICS does not perform the requested operation, your

transaction can abnormally terminate.
ERZ023076E Unable to store recovery information

for CICS queues
User response:
Region Pool memory was unable to be allocated. You
Explanation:
CICS is unable to save information to the file system to
enable recovery of Temporary Storage or Transient Data
queues after a system failure.
System action:
The transaction is abnormally terminated.
Destination:
console.msg
User response:
Other messages indicate the cause of the error,
perhaps a file system error. Correct the problem and
resubmit the transaction.

Unsuccessful attempt to allocate
Task-Private Storage
Destination:
console.msg
Explanation:
CICS was unable to allocate Task-Private Storage
during a Temporary Storage (TS) queue operation.
ERZ023077E Read of file fileName for recovery of

Temporary Storage queues failed with
timeout condition
Explanation:
A read operation for recovery of Temporary Storage
queues did not complete within the transaction
DeadLockTimeout value. This can be caused by a lock
held on the file by an unresolved transaction.
System action:
The region is abnormally terminated with abend code
U2372.
User response:
Determine the cause of the timeout error. Use file server
administration commands to identify inflight transactions
which are holding locks on the file, and, if necessary,
force the transactions with the tkadmin command, if the
file server is SFS, or list indoubt transactions with
prompting if the file server is DB2. Note that if the file
server is SFS, these locks are automatically dropped
when the time specified by the IdleTimeout attribute in
the SFS Definitions (SSD) has expired; CICS can then
be restarted. If the timeout is not caused by a retained
lock, it can possibly be solved by increasing the
DeadLockTimeout value for the Initialization transaction,
CAIN, which performs the recovery processing. If the
problem cannot be solved, a cold start of the region is
possibly necessary.
System action:
User response:
Task-Private storage was unable to be allocated. You
can reduce the amount of Task-Private Storage used by
your transaction by reducing your use of GETMAIN.
Destination:
console.msg
Task-Shared Pool memory
Explanation:
CICS was unable to allocate Task-Shared Pool memory
System action:
User response:
Task-Shared Pool memory was unable to be allocated.
You can reduce the amount of Task-Shared Pool
memory used by your transaction by reducing your use
of MAIN TS queues.
Destination:
console.msg
Destination:
console.msg

Region Pool memory

Unsuccessful attempt to register a
Logical Unit of Work (LUW)
Explanation:
CICS was unable to allocate Region Pool memory
Explanation:
CICS was unable to register a Logical Unit of Work
(LUW) for your transaction during an operation on
Temporary Storage (TS).
System action:
153
ERZ023094W ERZ023101E
System action:
User response:
registration of the LUW did not succeed.
Destination:
console.msg
ERZ023094W Unsuccessful memory deallocation of
Temporary Storage buffer
Explanation:
An error occurred while CICS was attempting to release
a memory buffer used by Temporary Storage.
System action:
This message is logged but processing continues.
User response:
Check the CSMT log or console.msg file, for associated
is a software error in CICS then contact your support
organization.
Destination:
CSMT
ERZ023097E Temporary Storage (TS): Auxiliary
queues currently not available
Explanation:
The Temporary Storage (TS) File server(s) is not
available, or the file containing the TS queues cannot
be accessed. This can be caused by a lock retained on
the file by an unresolved transaction.
System action:
CICS does not perform the requested Temporary
Storage operation.
User response:
Restart the TS queue File server(s), or investigate why
CICS is unable to access File server, and then retry the
operation. Retained locks on the file can be listed by
File server administration commands.
Increase the value of the transactions

DeadLockTimeout attribute in the Transaction
Definitions (TD) entry or investigate which transaction
has locked the resource or is using the most temporary
storage.
Destination:
console.msg or CSMT
ERZ023099E Abnormal termination A23S:
Unsuccessful Temporary Storage (TS)
space allocation
Explanation:
CICS detected a memory allocation error during a TS
queue operation.
System action:
CICS does not perform the requested operation. CICS
terminates the transaction with abend code A23S.
User response:
If a single transaction causes CICS to generate this
error on several occasions, the transaction is probably
in error. If so, you can use the CICS Problem
Determination Guide to solve this problem. Otherwise,
look at other messages in the message file to identify
which storage pool is affected, and change the memory
configuration attributes defined in the Region Definitions
(RD) entry.
Destination:
console.msg
ERZ023100E File operation for recoverable
Temporary Storage queue failed as File
server has been recycled
Explanation:
The connection to the File server for Temporary Storage
was temporarily lost. This has caused the connection to
the file to be invalidated. It is revalidated by CICS on
the next request to that file.
System action:
Destination:
console.msg
User response:
Resubmit the transaction. If communication errors
continue, refer to other messages to try to determine
the cause and correct it.
ERZ023098E Temporary Storage (TS) timed out
Destination:
console.msg
Explanation:
CICS has timed out a TS queue lock or NOSPACE
condition.
System action:
abnormally terminates the transaction that has timed out
with code AKCS in order to avoid a potential deadlock
situation.
User response:
154
ERZ023101E Transaction timed out waiting for

Temporary Storage file to be opened
by another task
Explanation:
The DeadLockTimeout value for the transaction was
exceeded while waiting for another transaction to finish
opening a file for auxiliary Temporary Storage queues.
ERZ023102E ERZ023106E
System action:
The transaction is abnormally terminated with code
AKCS.
User response:
Examine other messages for a problem in opening the
file. Resubmit the transaction. If this problem persists
when there is no problem with the file, it can be solved
by increasing the value of the DeadLockTimeout
attribute in the Transaction Definition.
Destination:
console.msg
ERZ023102E CICS is unable to save information for
START requests in the filesystem
Explanation:
During normal shutdown processing, CICS saves
information for unexpired START requests in the
filesystem, for use when the region is restarted. This
message indicates that CICS was unable to store that
information for START requests issued without the
PROTECT option, so these requests were unable to be
recreated on a normal region restart.
System action:
User response:
Examine other messages to determine the cause of the
error and correct it. Restart the region and resubmit the
START requests if required.
Destination:
console.msg
ERZ023103E CICS is unable to restore information
for START requests as the file for
non-recoverable Temporary Storage is
unavailable
Explanation:
During auto restart of the CICS region after a normal
shutdown, CICS retrieves information for START
requests issued without the PROTECT option from the
filesystem. This message indicates that CICS was
unable to retrieve the information as the required file is
not available. The file that contains the information is
the file used for non-recoverable Temporary Storage
Queues, specified by the NonRecTSQFile attribute in
the Region Definitions.
System action:
The region restart is terminated; restoration of the
information is retried on a subsequent auto start of the
region.
User response:
Examine accompanying message to determine why the
file is not available. Make the file available and auto
start the region.
Destination:
console.msg
ERZ023104E CICS is unable to restore information

for START requests from Temporary
Storage Queue queueName
Explanation:
During auto restart of the CICS region after a normal
shutdown, CICS retrieves information for START
requests issued without the PROTECT option from the
filesystem. This message indicates that CICS was
unable to retrieve the information because of an error.
System action:
The region restart continues. Unexpired START
requests which were stored in the named Temporary
Storage Queue are lost.
User response:
error and correct it if possible. Resubmit the START
requests if required.
Destination:
console.msg
ERZ023105W During a cold start, CICS is unable to
open and empty the files that store
Temporary Storage Queue data
Explanation:
During a cold start of the CICS region, the files that
store Temporary Storage Queue data in the filesystem
need to be emptied to keep the CICS and filesystem
information consistent. This message indicates that
there has been some error in opening and emptying
these files.
System action:
The region start continues. Further attempts are made
by CICS to empty the files if Temporary Storage queues
are accessed.
User response:
error and correct it if possible. If a database is being
used as the filesystem for Temporary Storage queues,
and CICS attempts to empty the files during a user task
that subsequently abends, the CICS and filesystem data
is inconsistent. To rectify such a situation, the problem
that is preventing the files from being opened and
emptied must first be solved, then the region can either
be cold started, or be shut down with an immediate
shutdown, and auto started to force recovery of the
queues.
Destination:
console.msg
ERZ023106E Abnormal termination ASRA. Attempt
to read into Region Pool memory.
Explanation:
The transaction has attempted a READQ TS operation
using an INTO buffer which specifies an address in
Region Pool memory.
155
ERZ023107W ERZ024007E
System action:
CICS terminates the transaction with abend code ASRA.
User response:
Check that the address specified in the INTO option
refers to memory accessible by the program and that
the LENGTH does not overrun the end of that memory.
Destination:
CSMT
ERZ023107W CICS self-consistency checking has
queueName: Last accessed time is
greater than the current time.
Explanation:
has found that the queues last access time occured in
the future.
System action:
CICS sets the last accessed time to the current time
and continues self-consistency checking.
User response:
None.
Destination:
console.msg
Explanation:
System action:
will abend.
User response:
Destination:
console
ERZ024005E Abnormal termination A245. Unable to
open log logFileName, reason
errorString.
Explanation:
CICS is unable to open the specified log file.
System action:
CICS terminates the Application Server with abend code
A245. Other Application Servers are not affected and
the region remains available.
156
User response:
Use information in errorString to determine the cause
of the error. Check the permissions for the CICS region
log directory to ensure that userid cics has both read
and write access. Also, check that there are no rogue
Application Servers persisting from a previous
invocation of the region. If there are, kill them.
Destination:
console.msg
ERZ024006E Abnormal termination U2406. Unable
to guarantee recovery of log
logFileName, reason errorString.
Explanation:
CICS is unable to write a restart record to log file
logFileName. If the region continues, this problem can
possibly prevent CICS recovery algorithms from working
correctly.
System action:
User response:
Verify that the CICS region log directory exists and that
sufficient storage has been allocated to it. If the problem
persists cold start CICS.
Destination:
console.msg
to recover CICS resources from log
logFileName.
Explanation:
There are the following reasons for this message:
v CICS has read an empty restart record for the master
log file. This occurs if, for example, CICS is auto
started following the deletion of the region master log.
v CICS is unable to determine the position in log file
logFileName at which to begin recovery processing.
A restart position is always set by CICS when it
creates a log file so this problem suggests a
malfunction in CICS logging.
v CICS is unable to read a log record at the restart
position in log logFileName. This error suggests that
the restart position for log file logFileName has been
overwritten with invalid data.
v CICS has read a record at the restart position in the
log file but it was the wrong size or contained invalid
data.
System action:
User response:
Check that the log files exist in the CICS region log
directory varDir/cics_regions/regionName/log. There
is one master log file for the region and a log file for
each of the Application Servers which were active when
the region was last stopped. The log files are named
ERZ024009E ERZ024019E
CICS_ML_regionName.control for the master log and
CICS_AS_applicationServerId.control for the
Application Server logs. If any of the log files are not
present, then, if the filesystem hosting the CICS region
log directory is configured to provide mirroring, switch to
the mirrored version containing the log files and auto
start CICS. Otherwise you need to cold start your CICS
region.
Destination:
console.msg
ERZ024009E Abnormal termination U2409. Error
errorNumber reading log file
logFileName.
a direction. Alternatively, CICS is possibly unable to

change the position of a log cursor in log logFileName
for reason errorString. Both of these problems prevent
the retrieval from the log of records required to recover
CICS resources correctly.
System action:
User response:
This message indicates an unexpected problem with the
log component. If the filesystem hosting the CICS
region log directory is configured to provide mirroring
switch to the mirrored version containing log
logFileName and auto start If the problem persists
Explanation:
An attempt to read the log file logFileName was
unsuccessful.
Destination:
console.msg
System action:
ERZ024016E Abnormal termination U2416. The log

component has an internal problem
and has initiated an immediate
termination of CICS
(Request=logRequest).
User response:
If the filesystem hosting the CICS region log directory is
configured to provide mirroring switch to the mirrored
version containing log logFileName and auto start
CICS. Otherwise cold start CICS.
Destination:
console.msg
ERZ024011E Abnormal termination U2411.
Unexpected recovery problem reading
from log logFileName.
Explanation:
CICS is attempting to read a start of checkpoint record
from the specified log but has retrieved some other
record instead.
System action:
User response:
version containing log logFileName and auto start
CICS. Otherwise cold start CICS.
Destination:
console.msg
Unexpected problem recovering
resources from log file logFileName,
reason errorString.
Explanation:
This can possibly be due to CICS being unable to open
a log cursor in log logFileName for reason
errorString. This operation attempts to establish a
context for subsequent reads by selecting a subset of
the log records to be retrieved, a position in the log and
Explanation:
The log component has an internal problem from which
it is unable to recover. It has requested CICS to
terminate the region immediately.
System action:
U2416.
User response:
Cold start CICS. If the problem persists or occurs
frequently, contact your support organization.
Destination:
console.msg
to recover CICS resources - missing
checkpoint data for module moduleId.
Explanation:
This message indicates an unexpected problem with the
CICS log component. CICS has recovered the last
successful checkpoint written to the log, but is unable to
find the checkpoint data required by module moduleId.
System action:
User response:
version containing the CICS region log files and auto
start CICS. Otherwise cold start CICS. If the problem
Destination:
console.msg
157
ERZ024020W ERZ024025E
ERZ024020W Unable to close log logFileName
during process exit, reason errorString
Explanation:
CICS is unable to close log logFileName during
Application Server termination (or during log daemon
exit).
System action:
CICS continues.
User response:
You can ignore this message since the log files are
closed by the operating system when the processes
terminate. However, it possibly indicates a problem with
the underlying file system being used by the log
component. If the problem persists, contact your support
organization.
Destination:
console.msg
ERZ024021W CICS self consistency checking:
checkpoint counter value of
checkpointCounteru exceeds
CheckpointInterval value
checkpointIntervalu in Region Record.
Reconciled - counter set to
CheckpointInterval.
Explanation:
CICS has detected that the checkpoint counter is out of
range. The counter has been reset to the checkpoint
interval specified for the region by the
CheckpointInterval attribute in the Region Definitions.
System action:
CICS continues.
User response:
None. If this problem happens frequently, contact your
Destination:
console.msg
ERZ024022E CICS self consistency checking:
unexpected signature signatureFound
detected in a memory structure at
address structureAddress. (Expected
signature is expectedSignature.)
Explanation:
CICS has detected a signature field containing invalid
data in the Region Pool storage. This problem is not
likely to be caused by either user action or user
transactions.
System action:
CICS is abnormally terminated. Further messages are
produced by CICS.
User response:
Refer to the abnormal termination message produced
by CICS after this message.
158
Destination:
console.msg
ERZ024023W CICS self consistency checking:
count of number of registered modules
has value moduleCountu which exceeds
expected maximum of RegMaxu.
Reconciled - count set to maximum.
Explanation:
CICS has detected that the count of registered modules
for journaling has exceeded its maximum value.
System action:
CICS continues.
User response:
None. If this problem happens frequently, contact your
Destination:
console.msg
unexpected module identifier moduleId
encountered at element
moduleAddressu in the table of modules
registered for journaling
Explanation:
CICS has detected an unexpected module identifier in
its table of modules registered for journaling. This table
is allocated out of the Region Pool so this is not a
problem likely to be caused by user action or user
transactions.
System action:
produced by CICS.
User response:
Destination:
console.msg
counter of Application Server logs in
use has value inUseCounteru which
differs from the expected count of
numberLogsFoundu.
Explanation:
CICS has detected a mismatch between a counter and
the actual number of objects existing. As these objects
are allocated out of the Region Pool, it is not likely that
this problem is caused by user action or user
transactions.
System action:
produced by CICS.
ERZ024030E ERZ024053I
User response:
Destination:
console.msg
to find log needed for recovery.
Explanation:
CICS is unable to find a log for a Application Server that
it has started. The list of logs available for use in
recovery processing is maintained in region memory
and is retrieved from the CICS master log during initial
recovery processing. This message is produced when
the CICS Application Manager (cicsam process)
attempts to read from a log not present in the list. This
does not happen unless an internal problem exists or
unless Region Pool memory has been overwritten.
System action:
User response:
Auto start CICS. If the problem persists report it to your
support organization. Alternatively, cold start CICS.
Destination:
console.msg
to open master log file logFileName,
reason errorString.
Explanation:
CICS detected an unrecoverable error when attempting
to open the master log file logFileName.
System action:
User response:
Check using the file system commands that the master
log files exist in the log file directory. The master log
consists of a control file, CICS_ML_regionName.control
and one or more extent files,
CICS_ML_regionName.extent.extentNumber. If they exist,
verify that there are no rogue processes (cics, cicsld,
cicsrm) persisting from a previous invocation of the
region. If there are any, kill them. If the problem persists
Destination:
console.msg
to write to log logFileName, reason
errorString.

User response:
Use the information in errorString to determine what
caused the error. If it indicates that there is no space
available, allocate additional space to the CICS region
log directory containing logFileName. Auto start CICS
to continue. For other error conditions, if the filesystem
hosting the CICS region log directory is configured to
provide mirroring switch to the mirrored version
containing log logFileName and auto start CICS.
Otherwise cold start CICS.
Destination:
console.msg
ERZ024052E NOSPACE condition has arisen on
user journal journalId
Explanation:
CICS is unable to write to user journal journalId
because there is insufficient space available in the file
system where it resides. The current DiskA or DiskB
attribute in the Journal Definitions (JD) for the journal
determines the pathname of the file used by that
journal.
System action:
CICS suspends the transaction for a while and then
retries the write operation.
User response:
Either wait for space to become available, or initiate
action to free some journal storage in the same file
system. The latter can involve using the EXEC CICS
SET JOURNALNUM CLOSE or ADVANCE commands
to close existing journals to CICS so that they can be
moved offline to free some space in the associated file
systems.
Destination:
console.msg
ERZ024053I NOSPACE condition resolved on user
journal fileName
Explanation:
CICS detected a NOSPACE condition when writing to
the user journal fileName. The condition has now been
corrected.
System action:
CICS continues.
User response:
None
Destination:
console.msg
Explanation:
CICS is unable to write to log file logFileName.
System action:
159
ERZ024054E ERZ024060E
reading the system log, reason
errorNumber.
Explanation:
CICS is attempting to obtain memory from the Region
Pool for reading the system log. Insufficient memory is
available.
System action:
CICS recovery processing cannot continue. CICS
terminates the region with abend code U2454.
User response:
Auto start CICS with an increased Region Pool size by
overriding the MaxRegionPool attribute in the Region
Definition on the command line. Do the same for the
permanent database by using cicsupdate.
Destination:
console.msg
log archive control information, reason
errorNumber.
Explanation:
CICS is attempting to obtain memory for log archive
control information from the Region Pool. Insufficient
memory is available.
System action:
User response:
permanent database by using cicsupdate.
Destination:
console.msg
CICScheckpoint data, reason
errorNumber.
Explanation:
CICS is attempting to obtain Task Shared Pool memory
for a start of checkpoint buffer to contain log
management data. Insufficient memory is available.
System action:
User response:
Auto start CICS with an increased Task Shared Pool
size by overriding the MaxTSHPool attribute in the
Region Definition on the command line. Do the same for
the permanent database by using cicsupdate.
Destination:
160
console.msg
to write log data to permanent storage,
reason errorString.
Explanation:
CICS writes some log data into buffered storage to
improve performance. It also attempts to write log data
direct to permanent storage (storage which survives a
system crash) forcing all earlier buffered data to
become permanent too. This message is produced
when the log component is unable to make data
permanent when requested to do so by CICS.
System action:
User response:
Refer to the file system documentation for information
concerning the error code. If the problem persists either
cold start CICS or contact your support organization.
Destination:
console.msg
ERZ024058W Unsuccessful checkpoint for CICS
module moduleId, reason errorNumber
Explanation:
CICS was unable to collect checkpoint information from
the specified internal module.
System action:
CICS terminates the checkpoint operation and
continues processing. The attempt to checkpoint is
unsuccessful, so it is not possible to discard log records
which are otherwise summarized by the checkpoint
data. In consequence, log files continue to grow and
this affects both Log Service performance and CICS
recovery time. It also increases the use of Log Service
resources which becomes a problem if there are
insufficient resources available.
User response:
Restart CICS when convenient, using either auto start
or cold start. If the problem persists contact your
Destination:
console.msg
ERZ024060E
Abnormal termination U2460.

Recovery processing is incomplete as
CICS is unable to open Application
Server log logFileName, reason
errorString.
Explanation:
CICS is unable to open Application Server log file
logFileName during recovery processing. The CICS
Application Manager obtains the list of Application
ERZ024061W ERZ024065W
Server log files needing recovery from the CICS master
log, and stores this list in memory obtained from the
Region Pool.
Possible causes of this problem therefore include:
v
Region Pool memory has been overwritten with

invalid data (either before the list is written to the Log
Service, or after the list has been retrieved from the
Log Service)
v Log Service data has been overwritten with invalid

data
v Other users of the Log Service have deleted the log
file
v The Log Service has been cold started since your
region was started
v Another process has the log file opened already.
It is unlikely that misbehaving user transactions can
cause this problem.
System action:
CICS stops further recovery processing and terminates
the region with abend code U2460.
User response:
Refer to the Log Service documentation for information
concerning the log error code. If the log error code
indicates that the file is already open, verify that there
are no rogue Application Servers persisting from a
previous invocation of the region. If there are, kill them
and restart CICS. If the log error code indicates that the
file does not exist verify that no other users have
deleted the log file. If so, cold start CICS. For other log
error codes either cold start CICS or, if the file system
being used by the log directory is being mirrored, switch
to the mirrored version and auto start CICS. If the
Destination:
console.msg
ERZ024061W Unable to close log logFileName,
Reason errorString
Explanation:
CICS was unable to close log logFileName. The log file
handle obtained from the Log Service by CICS for
operations on this file remains valid. This means that
unnecessary Log Service resources are retained by the
region and this can potentially degrade performance.
ERZ024062E Abnormal termination A24S.

log record.
Explanation:
Pool for a log record. Insufficient memory is available.
System action:
The CICS Application Server which failed to obtain
memory is terminated with abend code A24S as it is
unable to make the log record permanent.
User response:
When convenient to do so, auto start CICS with an
MaxRegionPool attribute in the Region Definition on the
command line. Do the same for the permanent
database (using cicsupdate).
Destination:
console.msg
log control information, reason
errorNumber.
Explanation:
Pool for a log control list element. Insufficient memory is
available.
System action:
User response:
permanent database (using cicsupdate).
Destination:
console.msg
ERZ024065W Unable to discard obsolete records
from log file logFileName, reason
errorString
User response:
If this problem is happening frequently and if you are
concerned that there is some performance degradation,
auto start CICS to free the excess resources.
Explanation:
CICS is unable to set the archive tail for log
logFileName. This operation normally causes log
records that are no longer needed by CICS to be
discarded from the log. As the operation has been
unsuccessful, the log component is likely to be using
more disk space than it otherwise needs. This can
adversely affect performance if the problem occurs
frequently or persists for some time on a heavily used
log.
Destination:
console.msg
System action:
CICS continues.
System action:
CICS continues.
User response:
No immediate action is necessary, but this condition
161
ERZ024066E ERZ024072E
Destination:
console.msg
Transaction could not write to system
log, reason errorString.
Explanation:
CICS detected an unrecoverable error while attempting
to write to the system log.
System action:
User response:
Look up the error code in the Log Service
documentation. If it indicates that there is no space
available, use Log Administration commands to add
additional space to the Log Service volume where the
system log resides. Auto start CICS to continue. For
other error conditions, if your Log Service is configured
to provide mirrored volumes, switch to the mirrored
volume containing the CICS master log (defined by
attribute CLogName in RD) and auto start CICS. (Refer
to the Log Service documentation for information about
how to do this.) Otherwise, terminate the Log Service
and restart it in recover mode before performing an auto
start of CICS (refer to the Log Service documentation
for information about how to do this), or cold start the
Log Service and then CICS. If the problem persists
Destination:
console.msg
ERZ024067E
Abnormal termination U2467. Cannot

initialize server log, reason errorString.
Explanation:
CICS was unable to initialize the log while attempting to
start a CICS process. This is usually because the
access permissions on the log directory
/var/cics_regions/regionName /log or on the files in the
directory are insufficient.
System action:
User response:
Check (and correct) the permissions on the log directory
and/or files. If the problem persists, call your support
organization.
Destination:
console.msg
user journal control information,
reason errorNumber.
Explanation:
CICS is attempting to open a user journal defined with
InitialOpenFlag=yes in the Journal Definitions (JD). It is
162
unable to create and insert a TDQ run time database

entry corresponding to the user journal being opened
because there is insufficient memory in the Region
Pool.
System action:
User response:
permanent database using cicsupdate.
Destination:
console.msg
ERZ024071E Invalid attempt to change definition of
journal journalId in the run time
database
Explanation:
CICS has vetoed an attempt to delete or alter the
definition of a journal in the run time database because
the journal is still in use. Similarly, amendments are
vetoed if the current destination is altered, for the same
reason. Note also that the open status of a journal can
be altered via the EXEC CICS SET JOURNALNUM
command only.
System action:
None
User response:
Retry the cicsdelete or cicsupdate request after closing
the journal or changing the current destination (EXEC
CICS SET JOURNALNUM command) as appropriate.
Destination:
CSMT
ERZ024072E Abnormal termination A24M.
Unsuccessful memory allocation while
opening journal journalId.
Explanation:
CICS failed to obtain memory while attempting to open
user journal journalId. CICS is unable to create and
insert a TDQ run time database entry corresponding to
the user journal because there is insufficient memory in
the Region Pool.
System action:
The transaction is terminated with abend code A24M.
User response:
Retry the request later. If this problem happens
frequently, increase the size of the Region Pool by
permanent database using cicsupdate.
Destination:
CSMT
ERZ024074E ERZ024083I
ERZ024074E Abnormal termination A24F. Unable to
save changes made to the run time
database record of journal journalKey,
reason errorNumber.
Explanation:
CICS is attempting to save changes made to the
specified journals run time database record, but is
unable to do so.
System action:
CICS terminates the transaction with abend code A24F.
User response:
If the CICS error code indicates insufficient memory,
retry when more memory is available. If this problem
happens frequently, increase the size of the Region
Pool by overriding the MaxRegionPool attribute in the
Destination:
CSMT
ERZ024075E
User response:
Check that the destination paths (attributes DiskA and
DiskB) specified in the JD both exist. If not, create any
missing directories or correct the destination paths as
appropriate (using RDO commands such as cicsget,
cicsdelete, cicsadd and cicsupdate to change both the
run time and permanent database definitions).
Also check the permissions on all directories in these
paths to ensure that userid cics has write access.
For the specified journal, check that there is space
available in the file system containing the current
destination of the journal.
Destination:
CSMT
ERZ024080I Application Manager has finished with
master log file
Abnormal termination U2475. Unable

to write to crucial user journal
journalId, reason errorNumberd.
Explanation:
CICS is attempting to write to user journal journalId
which is designated as a crucial journal. CICS is
unable to write to this journal. Possible causes include
deadlock timeout, insufficient space on the relevant file
system and bad destination path specified in the
Journal Definition (JD).
System action:
User response:
Check that the destination paths (attributes DiskA and
DiskB) specified in the JD both exist. If not, create any
missing directories or correct the destination paths as
appropriate and restart your region. Also check the
permissions on all directories in these paths to ensure
that userid cics has write access. For the specified
journal, check that there is space available in the file
system containing the current destination of that journal.
Explanation:
The CICS Application Manager has completed
processing the log files.
System action:
None
User response:
None
Destination:
console.msg
ERZ024081I CICS log daemon ready
Explanation:
The CICS log daemon process is no longer waiting for
access to the master log file. It is now ready to perform
logging.
System action:
None
User response:
None
Destination:
console.msg
Destination:
console.msg
ERZ024076E
The transaction is terminated with abend code A248.
Abnormal termination A248. Unable

to write to user journal journalId,
reason errorNumber.
Explanation:
CICS is attempting to write to non-crucial user journal
journalId, but is unable to do so. Possible causes
include deadlock timeout, insufficient space on the
relevant file system and bad destination path specified
in the Journal Definition (JD).
System action:
ERZ024083I Log daemon is waiting for access to

master log file
Explanation:
The CICS log daemon process is waiting for access to
the master log file. Only one process can open the file
at a time, and the Recovery Manager process must
finish with the file before it can be opened by the log
daemon.
System action:
None
163
ERZ024085I ERZ024098E
User response:
None
Destination:
console.msg
The CICS Application Server is restoring the state of

CICS resources which changed after the last checkpoint
was written.
System action:
None
ERZ024085I Application Manager is determining

recovery requirements
User response:
None
Explanation:
The CICS Application Manager is starting to process the
master log file. During this work it restores the state of
CICS resources from the last checkpoint written to this
log file and it builds up a list of Application Server log
files which need further processing.
Destination:
console.msg
System action:
None
User response:
None
Destination:
console.msg
ERZ024086I Application Manager has determined
recovery requirements
Explanation:
The CICS Application Manager process has finished
processing the master log file and now has a complete
list of further log files to be processed.
ERZ024089I Checkpointing started

Explanation:
CICS is commencing a checkpoint detailing the state of
all recoverable resources. It is written to the master log
file.
System action:
None
User response:
None
Destination:
console.msg
ERZ024090I Checkpointing completed
Explanation:
CICS has completed a checkpoint.
System action:
None
System action:
None
User response:
None
User response:
None
Destination:
console.msg
Destination:
console.msg
ERZ024087I Application Manager is opening log

files used previously

Exception exceptionName caught.
Explanation:
The CICS Application Manager is opening those
Application Server log files which were previously in use
by CICS.
Explanation:
CICS detected an unexpected fatal exception.
System action:
None
System action:
User response:
None
User response:
Restart your region. If the problem persists investigate
whether any particular transactions appear to cause this
problem and contact your support organization.
Destination:
console.msg
Destination:
console.msg
ERZ024088I Application Server is playing back

work that took place after the last
checkpoint
ERZ024098E Abnormal termination AKCS; write to

journal journalId has timed out
Explanation:
164
Explanation:
CICS has timed out while attempting to write to user
journal journalId.
ERZ024100E ERZ024104E
System action:
terminates the transaction with abend code AKCS in
order to avoid a potential deadlock situation.
User response:
Increase the value of the DeadLockTimeout attribute in
the Transaction Definitions (TD) entry and investigate
which transactions have taken the most space in the file
system being used by user journals. If any transactions
are found which are using unwarranted amounts of user
journal storage or extrapartition transient data queue
storage, disable the relevant journal or transient data
queue and archive and delete the corresponding file.
You possibly also need to purge the tasks running any
such transactions.
Destination:
CSMT
ERZ024100E Cannot advance (switch destination
files for) an unopened journal journalId
Explanation:
CICS received a request to switch files for a journal that
is not opened. The journal must be in the open state
before it can be advanced. The purpose of advancing a
journal is to allow the journal contents to be moved
offline for processing by user programs. If the journal is
in a closed state the relevant journal file is already
available to user programs without needing to advance
the journal first.
System action:
CICS does not perform the requested operation. It
returns ILLOGIC.
User response:
None
Destination:
CSMT
ERZ024101W Journal journalId cannot be closed
because it is not open
Explanation:
CICS received a request to close a journal that is not
open. The journal must be in the open state before it
can be closed.
System action:
returns ILLOGIC.
User response:
None
Destination:
CSMT
ERZ024102W Journal journalId cannot be opened

because it is not closed
Explanation:
CICS received a request to open a journal that is not
closed. The journal must be in the closed state before it
can be opened.
System action:
returns ILLOGIC.
User response:
None
Destination:
CSMT
ERZ024103E Cannot delete Transient Data (TD)
Queue TDQname for Journal
journalId, reason errorNumber
Explanation:
CICS was unable to delete the TD Queue dedicated to
journal journalId. This message usually means that the
TD Queue is in use (for example, a write request is
possibly in progress) and so cannot be deleted.
System action:
returns IOERR.
User response:
Check that the error code has this meaning and if so
retry until you succeed.
Destination:
CSMT
ERZ024104E Cannot obtain exclusive access to
Transient Data (TD) Queue TDQname
dedicated to journal journalId, reason
errorNumber
Explanation:
CICS was unable to obtain exclusive access to the TD
Queue underlying journal journalId.
System action:
returns IOERR.
User response:
If the reason for this error is insufficient memory,
increase the Region Pool size by overriding the
database using cicsupdate and retry. If the problem
persists contact your support organization.
Destination:
CSMT
165
ERZ024105E ERZ024109W
ERZ024105E Cannot save changes to run time
database entry for Transient Data (TD)
Queue TDQname, Journal journalId,
reason errorNumber
Explanation:
CICS was unable to save the updated run time
database record of TD Queue TDQname underlying
journal journalId.
System action:
returns IOERR.
User response:
If the reason for this error is insufficient memory,
increase the Region Pool size by overriding the
database using cicsupdate and retry. If the problem
persists contact your support organization.
Destination:
CSMT
ERZ024106E Journal journalId cannot be opened
because the Transient Data (TD) Queue
TDQname already exists
Explanation:
CICS was unable to open journal journalId because the
TD Queue for this journal (TDQname) already exists.
In order to open a journal, CICS expects to create a run
time database record for the TD Queue to be used
exclusively by the journal. CICS reserves TD Queue
names CJ01-CJ99 for this purpose.
System action:
CICS does not open the journal. The journal stays
closed. CICS returns INVREQ.
User response:
If the presence of the existing TDQ is inadvertent, use
RDO commands to remove or rename the TDQ in the
run time database. Retry the journal command.
Destination:
CSMT
ERZ024107W Run-time database definition of
journal journalId not installed because
there is an invalid attribute
combination in the database entry
Explanation:
CICS has detected either
v that both destinations (DiskA, DiskB attributes) of
journal journalId are the same (a journal must have
DiskA different from DiskB so that the journal
destination can be switched when required), or
v that both destination states (DiskAStatus,
DiskBStatus attributes) are the same (one journal
must be current and the other one must be ready).
166
System action:
CICS continues, but does not insert the journal
definition into the run time database.
User response:
Change the destinations (database attributes DiskA and
DiskB) associated with journal journalId so that they
are different. Ensure that all the necessary directories
exist and that userid cics has write permission to each.
Check also that attributes DiskAStatus and DiskBStatus
are different. Use RDO commands to effect any run
time database changes required. For example use
cicsget, cicsdelete and cicsadd.
Destination:
CSMT
ERZ024108E Cannot change destination of open
journal journalId
Explanation:
CICS has rejected a request to change the destination
of journal journalId because it is open.
System action:
CICS does not perform the requested action on the
journal. It returns INVREQ and continues.
User response:
Close the journal and retry.
Destination:
CSMT
ERZ024109W Run-time database definition of
journal journalId was not installed
because pathname pathName
specified for attribute attributeName in
database entry cannot be accessed
Explanation:
CICS has detected that a pathname specified in the
database entry (DiskA or DiskB attribute) for journal
journalId is not accessible by CICS.
System action:
CICS continues, but does not insert the journal
definition for journal journalId into the run time
database.
User response:
Check the DiskA and DiskB attributes of the specified
journal. These values cannot be empty strings but must
be pathnames writable by CICS. Check that the
directories exist and that user cics has read, write and
execute permissions for each. Correct any insufficient
permissions on the pathnames specified. Then re-install
the run time database entry, for example using cicsget,
cicsdelete and cicsadd.
Destination:
CSMT
ERZ024110E ERZ024116W
ERZ024110E Journal journalId cannot be deleted
because it is not closed
Explanation:
CICS received a request to delete a journal that is
open. The journal must be closed before it can be
deleted.
System action:
CICS does not perform the requested operation.
User response:
Close the journal and retry.
Destination:
CSMT
ERZ024111I numberOfJournals user journal(s)
successfully opened: listOfJournals
Explanation:
CICS has finished user journal initialization. The names
of the journals marked to be opened at startup and
successfully opened are displayed.
System action:
None
User response:
None
Destination:
console.msg
ERZ024112E Unable to save changes made to the
run time database record of journal
journalKey
Explanation:
CICS is attempting to save changes made to the
specified journals run time database record, but is
unable to do so.
System action:
CICS continues, but does not perform the requested
operation on the user journal.
User response:
If the CICS error code indicates insufficient memory,
retry when more memory is available. If this problem
happens frequently, increase the size of the Region
Pool by overriding the MaxRegionPool attribute in the
Destination:
CSMT
ERZ024113E Journal data corrupted
Explanation:
The self consistency checking in CICS detected that the
journal fields were not correct.
CICS is abnormally terminated.

User response:
by CICS after this message. Retry the operation. If the
Destination:
console.msg
ERZ024114W No user journals opened
Explanation:
CICS has finished user journal initialization. There are
no journals marked to be opened at startup which were
successfully opened.
System action:
None
User response:
None
Destination:
console.msg
ERZ024115W Cannot access master log as log
daemon process has terminated
Explanation:
CICS has made an attempt to access the master log
during shutdown after the log daemon process cicsld
has terminated.
System action:
Shutdown of the CICS region continues.
User response:
None
Destination:
console.msg
ERZ024116W The log directory is running short of
storage
Explanation:
CICS has detected that the log directory is running low
on available storage because there is insufficient space
available in the file system where it resides. The
pathname of the log directory is varDir/cics_regions/
regionName/log.
System action:
CICS continues to monitor this condition and continues
to issue this message periodically while the shortage
exists. If the log directory fills completely, CICS
terminates the region with abend code U2451 or U2498.
User response:
Increase the storage available to the file system.
Destination:
console.msg
System action:
167
ERZ024117W ERZ025008E
ERZ024117W Unable to free internal structures for
log logFileName following abnormal
termination of Application Server,
reason errorString
Explanation:
CICS is unable to free up the internal control blocks for
log logFileName following the abnormal termination of
an Application Server.
System action:
CICS continues.
User response:
You can ignore this message since the log control
blocks are deallocated when CICS is next stopped.
However, it possibly indicates an internal problem with
the log component, and, if the problem persists, contact
CSMT
ERZ025005E Rewrite of file: serverName/fileName,
index: indexName, was unsuccessful,
SFS code - errorCode errorString
Explanation:
A Structured File Server (SFS) error has occurred when
attempting to rewrite a modified record to the specified
file.
System action:
CICS has not rewritten the record. The transaction
continues.
User response:
Check that the SFS serverName is still running. Refer
to SFS documentation for further information concerning
the SFS error code.
Destination:
console.msg
Destination:
CSMT
ERZ025001E Unsuccessful open of file:

serverName/fileName, index:
indexName, SFS code - errorCode
errorString
ERZ025006E Delete from file: serverName/

fileName, index: indexName was
unsuccessful, SFS code - errorCode
errorString
Explanation:
attempting to open the specified file.
Explanation:
attempting to delete a record from the specified file.
System action:
CICS has not opened the file. The transaction
continues. CICS can possibly generate further
messages as a result of this error.
System action:
CICS has not deleted the record from the file. The
transaction continues.
User response:
Check that the SFS serverName is running. Check that
the resource definitions for the file are consistent with
the configuration of SFS. Refer to SFS documentation
for further information concerning the SFS error code.
Destination:
CSMT
ERZ025002E Close of file: serverName/fileName,
index: indexName was unsuccessful,
Explanation:
attempting to close a File Descriptor for the specified
file.
System action:
The transaction continues. CICS can possibly generate
further messages as a result of this error.
User response:
Check that SFS serverName is running. Refer to SFS
documentation for further information concerning the
SFS error code.
Destination:
168
User response:
the SFS error code.
Destination:
CSMT
ERZ025008E Attempt to obtain information for file:
serverName/fileName and index:
indexName was unsuccessful, SFS
Code - errorCode errorString
Explanation:
A Structured File Server (SFS) error has occurred while
obtaining information concerning the specified file and
index.
System action:
User response:
the resource definitions for file fileName and index
indexName are consistent with the configuration of
SFS. Refer to SFS documentation for further information
concerning the SFS error code.
ERZ025009E ERZ025014E
Destination:
CSMT
ERZ025009E Abnormal termination A25M: Failed to
obtain memory for file control
information.
Explanation:
information from the Region Pool. Insufficient memory
was available.
System action:
The transaction abnormally terminates.
User response:
This is possibly a transient problem that can occur when
size of the Region Pool and restart CICS.
Destination:
CSMT
ERZ025011E Select range in file:
Explanation:
attempting to select records in the specified file and
index.
System action:
holding locks on the file. If the file is one that is used to

store CICS queue data, this can cause a problem
during region restart. Such transactions can be
identified by filesystem administration commands and, if
necessary, the transactions can be forced with the
tkadmin command. Note that these locks are
automatically dropped when the time specified by the
IdleTimeout attribute in the SFS Definitions (SSD) has
expired.
Destination:
CSMT
ERZ025013E Could not get information about index
indexName for file:
serverName/fileName, SFS code errorCode errorString.
Explanation:
attempting to obtain information about the specified file
and index.
System action:
User response:
the configuration of SFS. In particular, check that the
SFS file serverName/fileName does have an index
indexName. Refer to SFS documentation for further
information concerning the SFS error code.
Destination:
CSMT
User response:
the SFS error code.
ERZ025014E Unlock of File: serverName/fileName,

index: indexName was unsuccessful,
Destination:
CSMT
Explanation:
attempting to unlock a record in the specified file.
ERZ025012E Close of file: serverName/fileName

was unsuccessful, SFS code errorCode errorString
System action:
The specified record was possibly not unlocked. The
transaction continues. CICS can possibly generate
Explanation:
attempting to close a File Descriptor for the specified
file.
System action:
User response:
the SFS error code. An error on closing the file can
indicate that there are inflight transactions which are
User response:
Destination:
CSMT
169
ERZ025016E ERZ025021E
ERZ025016E Get ESN for File: serverName/
fileName Failed, SFS Code - errorCode
errorString
ERZ025018E Inconsistent index information for file:

serverName/fileName, index
indexName, field fieldName
Explanation:
When CICS inserts records into an ESDS file, it first
inserts the record and then obtains the Entry Sequence
Number (ESN) of the inserted record from the
Structured File Server (SFS). The operation to obtain
this ESN was unsuccessful for the reason indicated.
Explanation:
The Structured File Server (SFS) index specification for
the file refers to a segment for which information cannot
be retrieved. The SFS file and index information are not
consistent.
System action:
If the file is recoverable, the transaction is abnormally
terminated. Hence the inserted record is removed from
the file. If the file is not recoverable the transaction
continues, although CICS possibly generates further
messages or error conditions as a result of this failure.
In this latter case, CICS does not attempt to remove the
inserted record, and a condition code can later be
raised.
User response:
If the file is non-recoverable, consider the effects of the
presence of the record whose ESN was not able to be
obtained. Consult the SFS documentation for further
information concerning the error code. The causes of
the failure are likely to be internal errors within either
CICS or SFS; contact your support organization for
additional information.
Destination:
CSMT
ERZ025017E Attempt to obtain duplicate key
information for file:
Explanation:
CICS is in the process of deleting a record from a file
which is being accessed via an index which permits
duplicate keys. The Structured File Server (SFS)
reported an error while attempting to detect whether
other records with the same key as the deleted record
also exist.
System action:
further messages as a result of this error. The record is
deleted.
User response:
The causes of the failure are likely to be internal errors
within either CICS or SFS; contact your support
organization for additional information.
Destination:
CSMT
System action:
User response:
Destination:
CSMT
ERZ025020E Select position in file: serverName/
fileName, index: indexName, for key:
keyValue was unsuccessful, SFS code
- errorCode errorString
Explanation:
attempting to select a record with the indicated key
value in the specified file.
System action:
User response:
Check that the SFS serverName is running. Refer to
SFS documentation for further information concerning
the SFS error code.
Destination:
CSMT
fileName, index: indexName, for RRN:
RRNd was unsuccessful, SFS Code errorCode errorString
Explanation:
attempting to select a record in a Relative File.
System action:
User response:
the SFS error code.
Destination:
CSMT
170
ERZ025022E ERZ025029E
fileName, index: indexName, for ESN:
ESN was unsuccessful, SFS code errorCode errorString
ERZ025027E Write record to file: serverName/

fileName, for index: indexName was
errorString
Explanation:
attempting to select a record in an Entry Sequenced
File.
Explanation:
attempting to write a record to the file.
System action:
System action:
User response:
the SFS error code.
User response:
Check that the SFS serverName is running. Ensure
that the SFS has sufficient processing threads. Refer to
the SFS error code.
Destination:
CSMT
Destination:
CSMT
ERZ025024E Read for delete in file: serverName/

fileName, index: indexName was
errorString
ERZ025028E Write of record to relative file:

serverName/ fileName, for RRN: RRNd
was unsuccessful, SFS code errorCode errorString
Explanation:
attempting to obtain a record with the intention of
deleting it.
Explanation:
attempting to write a record to the indicated Relative
file.
System action:
The record has not been deleted. The transaction
System action:
User response:
Destination:
CSMT
ERZ025026E Read record from file: serverName/
fileName, Index: indexName Failed,
SFS Code - errorCode errorString
User response:
the SFS error code.
Destination:
CSMT
ERZ025029E Write of record to entry sequenced
file: serverName/ fileName was
errorString
Explanation:
attempting to read a record from the specified file.
Explanation:
attempting to write a record to the indicated entry
sequenced file.
System action:
System action:
User response:
the SFS error code.
User response:
the SFS error code.
Destination:
CSMT
Destination:
CSMT
171
ERZ025030E ERZ025035E
ERZ025030E Browse of file: serverName/fileName,
index: indexName, key: keyValue was
unsuccessful due to earlier error
Explanation:
CICS has detected an error when starting a browse in a
clustered file. An error message previously written to the
message file possibly gives additional information.
System action:
User response:
Consult other messages recently written to the message
file for more detailed diagnostic information.
Destination:
CSMT
RRN: RRNd was unsuccessful due to
an earlier error
Explanation:
CICS has detected an error when starting a browse in a
relative file. An error message previously written to the
message file possibly gives additional information.
System action:
User response:
Destination:
CSMT
RBA: RBAd was unsuccessful due to
an earlier error
Explanation:
CICS has detected an error when starting a browse in
an entry-sequenced file. An error message previously
written to the message file possibly gives additional
information.
System action:
User response:
Destination:
CSMT
ERZ025033E Browse of file at first record:

indexName was unsuccessful due to
an earlier error
Explanation:
CICS has detected an error when starting a browse at
the first record in a file. An error message previously
information.
System action:
User response:
Destination:
CSMT
ERZ025034E Browse of file at last record:
indexName was unsuccessful due to
an earlier error
Explanation:
CICS has detected an error when starting a browse at
the last record in a file. An error message previously
information.
System action:
User response:
Destination:
CSMT
ERZ025035E A Record with an invalid RBA has
been written to a non-transactional file:
serverName/ fileName, an attempt to
repair the file has was unsuccessful,
and hence the file may now contain
invalid data.
Explanation:
A record was written to a non-transactional Entry
Sequenced file, and either the resulting ESN was too
large to be returned in the supplied 32 bit RBA field or
the ESN was not able to be obtained. An attempt to
repair the file by deleting the record was unsuccessful.
Hence the file now possibly contains an invalid record
that is visible via any alternate indexes.
System action:
User response:
172
ERZ025041E ERZ025047W
Contact system administrator. The file can possibly be
repaired by using SFS tools. Recurrence of the problem
can possibly be avoided by limiting the number of
records in such files.
Destination:
CSMT
ERZ025041E Data structure inconsistency has
been detected for file:
serverName/fileName
Explanation:
CICS self-consistency checking has detected an
System action:
After further self-consistency checking, CICS abnormally
terminates.
User response:
Determine the cause of the inconsistency in the internal
data structures. It is possible that these have been
overwritten by defective application programs. It is also
possible that an internal CICS error has caused this
inconsistency.
Destination:
CSMT
ERZ025042E Invalid variable length record
specification for file
serverName/fileName
Explanation:
The file definition declared to the Structured File Server
(SFS) either has more than one variable length field, or
the variable length field is not the last field in the record.
System action:
User response:
Consult the TXSeries for Multiplatforms Application
Programming Guide for details of the SFS file structures
that are supported by CICS. Either alter the CICS file
definition to reference an SFS file whose structure is
supported by CICS or adjust the SFS file definition.
Destination:
CSMT
ERZ025043E A variable length field has been found
index indexName for file
serverName/fileName
Explanation:
The file definition declared on the Structured File Server
has defined an index using a variable length field. CICS
does not support such indexes.
System action:

User response:
supported by CICS or adjust the SFS file definition. It is
possible that this file has other indexes that do not use
variable length fields, and hence CICS can possibly be
configured to access the files via such indexes.
Destination:
CSMT
ERZ025044E Record length recordLengthd too large
for file serverName/fileName, Index:
indexName.
Explanation:
The Structured File Server (SFS) file definition has a
record length greater than 32767.
System action:
User response:
Destination:
CSMT
ERZ025046E Variable field found in relative record
file definition serverName/fileName
Explanation:
CICS supports only fixed length Relative files.
System action:
User response:
Programming Guide for information concerning the SFS
file structures that are supported by CICS. Either alter
the CICS file definition to reference an SFS file whose
structure is supported by CICS or adjust the SFS file
definition.
Destination:
CSMT
ERZ025047W An Open File Descriptor has been left
open on the SFS for file
indexName
173
ERZ025050E ERZ025055E
Explanation:
CICS was unable to close a Structured File Server
(SFS) Open File Descriptor (OFD). This was possibly
caused by a prior abnormal termination of a CICS
process or by an inability to acquire sufficient Region
Pool memory to perform the required processing.
System action:
Processing continues. Future transactions will possibly
be unable to acquire exclusive access to resources that
held by the unterminated OFD.
User response:
Use SFS administration facilities to identify and
terminate the OFD. A label is present on the OFD which
contains the CICS startup identifier. This identifier
consists of the CICS region name and the region
startup time.
Destination:
console.msg
ERZ025050E SFS serverName is unavailable
Explanation:
CICS has been unable to access a Structured File
Server (SFS). This server has previously been usable.
The cause is possibly that the server has an insufficient
number of processing threads to enable it to service the
number of simultaneous requests it is receiving.
System action:
User response:
Use SFS diagnostic procedures to determine the nature
of the problem. The SFS possibly needs to be restarted,
possibly with a larger number of threads. CICS is then
able to resume its use of the server.
Destination:
CSMT
ERZ025051I SFS serverName is now available, file
fileName can now be accessed.
Explanation:
The indicated Structured File Server had previously
become unavailable, and hence the specified file was
not able to be accessed. CICS has now been able to
access the server and has reopened the file.
System action:
User response:
None
Destination:
CSMT
ERZ025052E File handle for file

serverName/fileName invalid
Explanation:
It is not possible to access the specified file because of
the indicated Structured File Server (SFS) error. The
cause is possibly that the server has an insufficient
number of processing threads to enable it to service the
number of simultaneous requests it is receiving.
System action:
further messages as a result of this error. Use of the file
continues to give errors until the SFS is again available.
User response:
Use SFS diagnostic procedures to determine the nature
of the problem. The SFS possibly needs to be restarted,
possibly with a larger number of threads. CICS is then
able to resume its use of the server.
Destination:
CSMT
ERZ025053E An abnormal return code,
returnCode, has been returned by the
SFS server side transaction support
Explanation:
The call to sfs_ServerTransactionBegin failed
System action:
The CICS region terminates immediately.
User response:
Investigate the reasons for this return code as specified
in the documentation.
Destination:
stderr
SFS server side transaction commit
Explanation:
The call to sfs_ServerTransactionCommit failed
System action:
User response:
Destination:
CSMT
SFS server side transaction backout
Explanation:
The call to function sfs_ServerTransactionAbort failed.
174
ERZ025092E ERZ025096I
System action:
User response:
Destination:
CSMT
ERZ025092E Key comparison for file:
serverName/fileName, Index:
indexName Failed, SFS Code errorCode errorString
Explanation:
attempting to compare two key values.
ERZ025094E Invalid segment number

segmentNumber for file:
indexName
Explanation:
The SFS index specification for the file refers to a
segment number which does not exist. The SFS file and
index information are not consistent.
System action:
User response:
System action:
Destination:
CSMT
User response:
ERZ025095E Unsuccessful reopen of file handle for

file: serverName/fileName, index:
indexName, SFS code - errorCode
errorString
Destination:
CSMT
Explanation:
A previously open Structured File Server (SFS) file was
not able to be reopened. The file possibly needs to be
reopened for one of two reasons: SFS has become
available after previously becoming unavailable and so
the file needs to be reopened, or SFS has terminated
an Open File Descriptor for the file and so it needs to
be reopened.
ERZ025093E Empty of file: serverName/fileName

was unsuccessful, SFS Code errorCode errorString
Explanation:
attempting to empty a file during a file open operation.
System action:
further messages as a result of this error. The file has
not been emptied.
User response:
there are no other users of the file. It is possible that the
file has been opened by the current CICS region, using
a different File Control access path. It is possible that
another CICS region is accessing the file. It is possible
that an off-line application program is using the file.
Another possibility is that a process that was previously
using the file has abnormally terminated. In this latter
case, the SFS administration interface permits the Open
File Descriptors for the file to be identified, and, where
appropriate, terminated. Refer to SFS documentation for
further information concerning the SFS error code.
Destination:
CSMT
System action:
CICS has not reopened the file. The transaction
User response:
Refer to SFS documentation for further information
Destination:
CSMT
ERZ025096I File handle reopened for file:
indexName
Explanation:
The indicated Structured File Server (SFS) had
previously terminated an Open File Descriptor. The file
has now been reopened.
System action:
The transaction continues
User response:
None
Destination:
CSMT
175
ERZ025097E ERZ025103W
ERZ025097E Select record for deletion in file:
indexName key keyValue was
unsuccessful, SFS Code - errorCode
errorString
Explanation:
attempting to select a record with the intention of
deleting it.
System action:
User response:
Refer to SFS documentation for further information
Destination:
CSMT
ERZ025098E CICS abnormal termination A25E: was
unable to get an RBA for recoverable
file serverName/fileName; SFS Code errorCode errorString
Explanation:
CICS has encountered a problem when attempting to
obtain the RBA of a record that it is inserting to a
Structured File Server (SFS) file.
System action:
The transaction terminates with code A25E. CICS does
not insert the record.
User response:
Refer to SFS documentation for information concerning
the SFS error code.
Destination:
CSMT
ERZ025099W Index indexName for file
serverName/fileName contains an
NLS field: generic operations should
not be used
Explanation:
The Structured File Server (SFS) does not support
generic key operations on NLS data. CICS File Control
generic key operations are not reliable when applied to
such indexes.
System action:
None
User response:
Consult TXSeries for Multiplatforms Application
Programming Guide for details of the file structures that
are supported by CICS. Either alter the CICS file
Destination:
176
CSMT
ERZ025100W Unsuccessful attempt at labelling
Open File Descriptor for file
indexName; SFS code - errorCode
errorString
Explanation:
An unsuccessful attempt was made to label an Open
File Descriptor (OFD). The OFD label was intended to
help identify which OFDs were used on your CICS
region, so that in the event of the region abnormally
terminating any OFDs left on the Structured File Server
(SFS) were able to be determined and removed by
using SFS administration facilities.
System action:
Processing continues. CICS continues to use the file.
User response:
None
Destination:
CSMT
ERZ025101E Abnormal termination A25L: Failed to
retain transactional lock for file
indexName; SFS code - errorCode
errorString
Explanation:
CICS was unsuccessful in retaining a transactional lock
for the named file.
System action:
User response:
the SFS error code.
Destination:
CSMT
ERZ025103W Unable to use the SFS as the
transaction has been terminated
Explanation:
CICS was not able to perform an operation on the
structured file system, as the transaction that was being
used has been asynchronously terminated.
System action:
CICS terminates the transaction.
User response:
Something other than CICS has caused the transaction
to terminate. If this persistently occurs, investigate the
cause. The most likely culprit is the SFS, but
communications errors are also possibly the cause.
CICS continues to run normally, however.
ERZ025104E ERZ026003E
Destination:
CSMT
ERZ025104E SFS batch call number callNumber
was unsuccessful with SFS code
errorCode - errorString.
Explanation:
CICS has detected an error when attempting to perform
a sequence of batched SFS writes or updates.
System action:
User response:
Refer to SFS documentation for the SFS error code.
Check that the SFS is running and listening for RPCs.
Otherwise refer to earlier messages generated to
determine the cause of the problem.
Destination:
console.msg
ERZ025105E Request to allocate storage for SFS
batch call was unsuccessful.
Explanation:
CICS was unable to satisfy a storage allocation request.
System action:
User response:
Release storage by reducing the load on the machine.
Destination:
console.msg
ERZ025106W Close of OFD OFDnumber was
unsuccessful; SFS code - errorCode
Explanation:
A Structured File Server (SFS) problem has occurred
when attempting to close a File Descriptor for the
specified file.
System action:
further messages as a result of this warning.
User response:
Check that the SFS is running. Refer to SFS
documentation for further information concerning the
SFS code.
Destination:
CSMT
ERZ025107W Allocation of numPages page(s) of

disk space was unsuccessful for file:
serverName/fileName, SFS Code errorCode errorString
Explanation:
attempting to allocate space for a file during an file open
operation.
System action:
The transaction continues. The file space has not been
allocated.
User response:
Check that there is enough space on the SFS volume
associated with this file.
Destination:
CSMT
ERZ026001E Search string is missing
Explanation:
You entered a find command without a search string.
System action:
CEBR waits for valid input.
User response:
Retry the command with search string, or enter any
other valid command.
Destination:
CEBR user terminal
ERZ026002E No string to find
Explanation:
You requested a repeated find by pressing the PF6 key,
but you have not previously requested a find.
System action:
User response:
Enter some other command.
Destination:
CEBR user terminal
ERZ026003E Line number is missing.
Explanation:
You did not specify a line number for the LINE
command.
System action:
User response:
Retry the command with a valid line number, or enter
any other valid command.
Destination:
CEBR user terminal
177
ERZ026004E ERZ026011E
ERZ026004E Line number is too large.
Explanation:
You requested a line number that exceeds the number
of records in the Temporary Storage queue being
browsed.
System action:
User response:
Retry the command with a valid line number, or enter
Destination:
CEBR user terminal
ERZ026005E Column number is missing.
Explanation:
You did not specify a column number for the COLUMN
command.
System action:
User response:
Retry the command with a valid column number, or
enter any other valid command.
Destination:
CEBR user terminal
ERZ026006E Column number is too large.
Explanation:
You requested a column number that exceeds the
number of columns of data found in the Temporary
Storage queue being browsed.
System action:
User response:
Retry the command with a valid column number, or
Destination:
CEBR user terminal
ERZ026007E Unable to purge temporary storage
queue. Response Code responseText
(responseCode)
Explanation:
CEBR attempted to purge data from the temporary
storage (TS) queue but was not successful. CEBR has
issued an EXEC CICS DELETE QUEUE TS command,
which has not succeeded. The message indicates the
condition code that was returned by CICS in the EIB.
System action:
CICS has not purged the TS queue. CEBR waits for
further input.
User response:
178
Determine the cause of problem and correct it.

Additional diagnostics were possibly written to
console.msg. If the TS queue is an auxiliary queue then
check that the Structured File Server is running.
Destination:
CEBR user terminal
ERZ026008E Terminal name is missing.
Explanation:
You did not specify a terminal identifier for the
TERMINAL command.
System action:
User response:
Retry the command with a valid terminal identifier, or
Destination:
CEBR user terminal
ERZ026009E Queue name is missing.
Explanation:
You did not specify a temporary storage queue name
for the QUEUE command.
System action:
User response:
Retry the command with a valid queue name, or enter
Destination:
CEBR user terminal
ERZ026010E Name of transient data queue is
missing.
Explanation:
You did not specify a transient data queue name for the
GET or PUT command.
System action:
User response:
Retry the command with a valid queue name, or issue
Destination:
CEBR user terminal
ERZ026011E Unable to read transient data queue.
Response Code responseText
(responseCode)
Explanation:
CEBR was attempting to execute a GET command but
was not able to read from a transient data (TD) queue.
CEBR issued an EXEC CICS READQ TD command,
ERZ026012E ERZ026017E
which has not succeeded. The message indicates the
condition code that was returned by CICS in the EIB.
System action:
It is possible that CEBR partially completed the GET
command. The current TS queue possibly now contains
additional records. CEBR now waits for further input.
User response:
Determine the cause of the problem. Further diagnostics
can possibly have been written to console.msg. Check
that specified TD queue exists, that it is valid to read
from it and that access to it is authorized. If the queue
was an intra-partition TD queue, check that the file
server is still running. Correct any problems and
re-issue the GET command, or issue any other valid
command.
Destination:
CEBR user terminal
ERZ026012E Unable to write transient data queue.
(responseCode)
Explanation:
CEBR was attempting to execute a PUT command but
was unable to write data to the transient data (TD)
queue. CEBR has issued an EXEC CICS WRITEQ TD
command, which has not succeeded. The message
indicates the condition code that was returned by CICS
in the EIB.
System action:
It is possible that CEBR partially completed the PUT
command, and the TD queue possibly now contains
additional records. CEBR waits for further input.
User response:
are possibly written to console.msg. Check that
specified TD queue exists, that it is valid to write to it
and that access to it is authorized. If the queue was an
intra-partition TD queue, check that the file server is still
running. Correct any problems and re-issue the PUT
command, or issue any other valid command.
Destination:
CEBR user terminal
ERZ026013E Command is not known. Please
re-enter.
Explanation:
You have specified a command that is not recognized.
System action:
User response:
Issue a valid command.
Destination:
CEBR user terminal
ERZ026014E Line command requires a positive

integer.
Explanation:
You have supplied an argument to the LINE command
that is not a positive integer.
System action:
User response:
Retry the command with a valid argument, or issue any
Destination:
CEBR user terminal
ERZ026015E Column command requires a positive
integer.
Explanation:
You have supplied an argument to the COLUMN
command that is not a positive integer.
System action:
User response:
Retry the command with a valid argument, or issue any
Destination:
CEBR user terminal
ERZ026016E Hexadecimal queue name is too long.
Explanation:
You attempted to specify a queue name as a
hexadecimal string but the string specified was too long.
Each pair of hexadecimal digits correspond to one
character of the queue name. The maximum length of a
temporary storage queue name is 8 characters and
hence for such queues the maximum number of
hexadecimal digits is 16. The maximum length of a
transient data queue name is 4 characters and hence
for these queues the maximum number of hexadecimal
digits is 8.
System action:
User response:
Destination:
CEBR user terminal
ERZ026017E Queue specified contains an invalid
hex digit.
Explanation:
You attempted to specify a queue name as a
hexadecimal string but you used an invalid hexadecimal
179
ERZ026018I ERZ026025E
format. Only the digits 0 to 9 and the letters A to F can
be used. The name must be delimited by apostrophes.
System action:
User response:
Destination:
CEBR user terminal
ERZ026018I Browse has ended normally. Ready for
next transaction.
Explanation:
Message displayed when CEBR terminates.
System action:
CICS awaits the submission of the next transaction.
User response:
Submit another transaction.
Destination:
CEBR user terminal
ERZ026019I String was not found.
Explanation:
CEBR did not find a record containing the string
specified.
single parameter. The commands that expect no

parameter are TOP, BOTTOM, PURGE, CANCEL and
QUIT. The commands that expect one parameter are
FIND, QUEUE, TERM, LINE, COLUMN, GET and PUT.
System action:
CEBR did not execute the command. CEBR waits for
valid input.
User response:
Retry the command without the extraneous parameter,
or issue any other valid command.
Destination:
CEBR user terminal
ERZ026024E Unable to read temporary storage
(responseCode)
Explanation:
CEBR was attempting to execute a PUT command but
was unable to read data from the temporary storage
(TS) queue. CEBR has issued an EXEC CICS READQ
TS command, which has not succeeded. The message
indicates the condition code that was returned.
System action:
Some records were possibly written to the transient data
queue specified in the PUT command. CEBR now waits
for further input.
User response:
None
User response:
were possibly written to console.msg. If the queue was
an auxiliary TS queue, check that the file server is still
running. Correct any problems and retry the PUT
Destination:
CEBR user terminal
Destination:
CEBR user terminal
ERZ026021I Temporary storage queue queueName

is empty.
ERZ026025E Unable to write temporary storage

(responseCode)
System action:
Explanation:
CEBR displays this message when the current TS
queue is empty.
System action:
None
User response:
None
Destination:
CEBR user terminal
ERZ026023E Command with invalid parameter was
ignored
Explanation:
You have either supplied a parameter to a command
where none was expected, or you have supplied more
than one parameter for a command that requires a
180
Explanation:
CEBR was attempting to execute a GET command but
was unable to write data to the temporary storage (TS)
queue. CEBR has issued an EXEC CICS WRITEQ TS
command, which has not succeeded. The message
indicates the condition code that was returned.
System action:
It is possible that CEBR wrote some records to the TS
queue. CEBR waits for valid input.
User response:
were possibly written to console.msg. If the queue was
an auxiliary TS queue, check that the file server is still
running. Correct any problems and retry the GET
Destination:
ERZ026026W ERZ026034E
CEBR user terminal
Destination:
CEBR user terminal
ERZ026026W ignoredCharacters ignored

Explanation:
You entered a FIND command but characters were
found after the character that delimits the FIND string.
System action:
CEBR executes the FIND command having excluded
the superfluous string from the search.
User response:
None
Destination:
CEBR user terminal
ERZ026027E Character Queue name is too long
Explanation:
You entered a queue name that is too long for the type
of queue. Temporary storage queue names must not be
longer than 8 characters. Transient data queue names
must not be longer than 4 characters.
System action:
CEBR did not carry out the command. CEBR waits for
valid input.
User response:
Retry the command with a valid queue name, or issue
Destination:
CEBR user terminal
ERZ026028E Quote to end hexadecimal string is
missing
Explanation:
You entered a queue name in hexadecimal format, but
the quote indicating the end of the hexadecimal string
was not found.
System action:
User response:
Re-enter the hexadecimal queue with the correct
syntax, or enter any other valid command.
ERZ026032W Too many command arguments;

superfluous arguments ignored.
Explanation:
You have either supplied a parameter to a command
where none was expected, or you have supplied more
than one parameter for a command the requires a
single parameter. The commands that expect no
parameter are TOP, BOTTOM, PURGE, CANCEL and
QUIT. The commands that expect one parameter are
FIND, QUEUE, TERM, LINE, COLUMN, GET and PUT.
System action:
CEBR executes the command ignoring all superfluous
arguments.
User response:
Destination:
CEBR user terminal
ERZ026033E Find terminated abnormally.
Explanation:
A Find (or Find Next) was executed, but while
attempting to read a record from the Temporary Storage
queue an unknown error occurred.
System action:
The Find is halted and control is returned back to the
user.
User response:
Destination:
CEBR user terminal
ERZ026034E Error attempting to read queue
queueName. Response Code
responseText (responseCode)
Explanation:
While attempting to read a line from a TS queue a
serious error occurred. Browsing of the queue is halted
and the repeat lines are cleared.
Destination:
CEBR user terminal
System action:
Viewing of the current queue is halted and the repeat
lines on the screen are cleared.
ERZ026031E Unrecognized input. Please try again.
User response:
Attempt to re-read the queue, or issue another valid
command.
Explanation:
You entered a command that is not supported by
CEBR.
System action:
Destination:
CEBR user terminal
User response:
181
ERZ027001E ERZ027004E
ERZ027001E
Remote system sysId cannot be

found
Explanation:
A Communications Definition (CD) entry called sysId
was not able to be found. This CD entry has been
requested either in the SYSID option of an EXEC CICS
command or in the RemoteSysId attribute of the
definition for a resource requested by the transaction.
Possible causes of this error include:
v A CD entry called sysId, which specifies the location
of the remote system, has not been defined.
v A CD entry that specifies the location of the remote
system has been defined, but it is not called sysId.
v A CD entry called sysId has been defined in the
CICS permanent database but this definition has not
been added to your regions runtime database.
System action:
CICS returns the SYSIDERR condition code to your
transaction.
ERZ027002E Communications error

primaryCode/secondaryCode on
connection to system sysId
Explanation:
CICS detected a communications error while processing
an EXEC CICS command in conjunction with the
remote system configured in Communications Definition
(CD) entry sysId. The type of error detected is
described by error code primaryCode/secondaryCode.
System action:
CICS abnormally terminates the intersystem request for
the EXEC CICS command. Further messages can be
logged.
User response:
Refer to the TXSeries for Multiplatforms
Intercommunication Guide, which describes what the
error code primaryCode/secondaryCode means and
how to correct the problem.
Destination:
CSMT
User response:
1. Determine whether CD entry sysId is defined in the
permanent database using the following command
(where regionName is the name of your region):
cicsget -r <regionName> -c cd sysId
If the CD entry does exist, use the cicsinstall
command to add it to your regions runtime
database. cicsinstall is described in the TXSeries for
2. If the CD entry does not exist, list the CD entries
defined in your region using the:
cicsget -r <regionName> -c cd -l
command. Then use the:
cicsget -r <regionName> -c cd <name>
command, where <name> is the name of a CD entry,
to display each CD entry. If you discover a CD entry
for the remote system is already defined, change
the application program or resource definition to use
the name of this CD entry as the SYSID.
3. If no CD entry is defined for the remote system then
you need to add one called sysId to your region.
This is described in the TXSeries for Multiplatforms
Intercommunication Guide.
Rerun the request once any necessary corrections have
been made.
Destination:
CSMT
182
ERZ027003E CICS cannot execute DL/I request

received from system sysId
Explanation:
A request to execute a DL/I function has been received
from system sysId. This CICS system does not support
the DL/I Application Programming Interface (API), so
cannot satisfy the request.
System action:
CICS abnormally terminates the function shipping mirror
transaction.
User response:
Use the procedures appropriate to the remote system to
ensure that it does not attempt to function ship DL/I
requests to CICS. This can include modifying the
remote transaction and the remote systems resource
definitions.
Destination:
CSMT
ERZ027004E System sysId is not in service
Explanation:
CICS cannot send a remote EXEC CICS request to
system sysId because the InService attribute of the
Communications Definition (CD) for sysId is set to no.
System action:
CICS returns the SYSIDERR condition code to your
program.
User response:
Set the system back in service by setting the InService
attribute of the CD for the system to yes, then retry the
transaction. The system can be set back in service
while the region is running using the command CECI
SET CONNECTION(sysId) INSERVICE.
ERZ027005W ERZ027009E
Destination:
CSMT
ERZ027005W System sysId rejected initialization
data
ERZ027007W The function shipping mirror

transaction received an error
(errorCode) while executing a START
NOCHECK request.
Explanation:
The remote system configured in Communications
Definition (CD) entry sysId rejected the function
shipping initialization data which specifies the local code
page and byte order.
Explanation:
The function shipping mirror transaction has executed a
START NOCHECK request and has received an error of
errorCode as a result. The state of the intersystems
link is such that the error response cannot be returned
to the requesting system.
System action:
CICS retries the function shipping request without the
initialization data. The remote system assumes defaults
for the code page and byte order.
System action:
If the request was for a protected resource, the CICS
function shipping mirror transaction abnormally
terminates.
User response:
If the remote system is CICS, prepare a
communications trace showing the initialization data
sent to the remote system and contact your support
organization. Otherwise, determine if the default code
page and byte order used by the remote system are
appropriate for your network. If so, ignore this message
and continue processing. If not, determine if a version of
CICS which supports the function shipping initialization
data is available for the remote system.
User response:
Refer to the EIBRESP code errorCode in the TXSeries
for Multiplatforms Application Programming Reference.
Examine the CICS message files for any additional
information.
Destination:
CSMT
ERZ027006E
Conversion template is inconsistent

with application data for resource
resourceName and type resourceType
Explanation:
The conversion template for resource resourceName
and type resourceType specifies either a select or
conversion offset which is larger than the amount of
application data that the function shipping mirror
transaction is converting. The type is as follows
v 0 - File Definition (FD)
v 1 - Transient Data Definition (TDD)
v 2 - Temporary Storage Definition (TSD)
Destination:
CSMT
ERZ027008E A backout of the current Logical Unit
of Work (LUW) is required
Explanation:
The function shipping request cannot proceed because
the LUW which it is part of has been backed out.
System action:
User response:
Examine the CICS message files for additional
information that can help to determine why the LUW
was abnormally terminated. Use the procedures
appropriate to any remote systems with which the
transaction has performed intersystem communication,
to obtain any additional information.
Destination:
CSMT
v 3 - Transaction Definition (TD)

v 5 - Program Definition (PD)
System action:
User response:
Examine your transaction and the conversion template
for the resource being accessed to ensure that they are
consistent with each other. In particular, ensure that
select and conversion offsets specify valid offsets which
are less than the size of the application data that your
transaction is function shipping.
Destination:
CSMT
ERZ027009E Rollback was received from system

sysId, in response to a CICS synclevel
1 commit request.
Explanation:
Your CICS application has been using synclevel 1 to
process remote function shipped resources. The
application took a syncpoint, either implicitly or explicitly,
and this has caused all local resources and synclevel 2
partner systems to be committed. However, when a
commit message was sent to a synclevel 1 partner
system, the system voted to backout.
System action:
CICS continues the synclevel 1 commit processing, with
the intention of committing as many synclevel 1
183
ERZ027010E ERZ027012E
resources as possible. The transaction is abnormally
terminated when the synclevel 1 processing is
complete.
User response:
Use the procedures appropriate to the remote system
sysId to obtain additional information that can help to
determine why the remote resource voted to roll back.
Perform any necessary recovery procedures.
Destination:
CSMT
User response:
Alter the application so that it sends less data on a
single EXEC CICS command request. If your application
needs to send large amounts of data to the remote
system consider using Distributed Transaction
Processing (DTP) for a better solution.
Destination:
CSMT
ERZ027012E
ERZ027010E Communications failure during a

CICS synclevel 1 commit request.
Explanation:
Your CICS application has been using synclevel 1 to
process remote function shipped resources. The
application took a syncpoint, either implicitly or explicitly,
and this has caused all local resources and synclevel 2
partner systems to be committed. However the commit
message failed to be sent to one or more synclevel 1
partner systems.
System action:
CICS continues the synclevel 1 commit processing, with
the intention of committing as many synclevel 1
resources as possible. The transaction is abnormally
terminated when the synclevel 1 processing is
complete.
User response:
Check for earlier messages that indicate the names of
the remote partner systems and the reasons for the
communications failures.
Destination:
CSMT
ERZ027011E Remote command request to system
sysId is requestLength bytes long which
exceeds the maximum length of
maxLength bytes
Explanation:
CICS is unable to proceed with a remote EXEC CICS
command request to the system configured in
Communications Definition (CD) entry sysId because
the amount of data that must be transmitted,
requestLength, exceeds the maximum amount of data
that can be sent as part of a single request.
The data required for such a request contains the user
data passed on the request plus a description of the
EXEC CICS command specified by the application. The
number of bytes required to describe an EXEC CICS
command varies depending on the type of request and
the number of options specified. Aim to keep the user
data under 32500 bytes long.
System action:
CICS returns the LENGERR condition to the application.
Further messages can be logged.
184
Unexpected communications
indicator indicatorNumber received from
mirror transaction transId in system
sysId
Explanation:
CICS is unable to continue with a function shipping
request because it received an unexpected
communications indicator, indicatorNumber, from the
mirror transaction transId. transId is running on the
system configured in Communications Definition (CD)
entry sysId.
The communications indicators are as follows:
5
No indicator was received (when one was

expected).
A Change Direction (CD) indicator was

received.
A Confirm (RQD2) indicator was received.
A Confirm (RQD2) and Change Direction (CD)

indicator was received.
A Confirm (RQD2) and Conditional End

Bracket (CEB) indicator was received.
10
A syncpoint indicator was received.
11
A syncpoint and Change Direction (CD)

indicator was received.
12
A syncpoint and Conditional End Bracket

(CEB) indicator was received.
13
A Conditional End Bracket (CEB) indicator was

received.
This problem is usually caused because the mirror

transaction, transId, is not configured correctly in the
remote system and so the remote system does not run
the CICS mirror program.
System action:
User response:
Check the definition of transaction transId in the remote
system invokes the CICS mirror program. Verify that the
remote system and the connection to it are functioning
normally by performing other intersystem
communication functions (such as transaction routing) to
the remote system. If the problem persists, prepare a
ERZ027013E ERZ027016E
communications trace showing the data received from
the remote system and contact your support
organization.
Destination:
CSMT
ERZ027013E The function shipping mirror
transaction transId cannot be started
from a terminal
Explanation:
You have started the function shipping mirror
transaction by entering the transaction code transId at
a terminal. The function shipping mirror transaction can
only be started by a remote system.
System action:
User response:
Do not attempt to start the function shipping mirror
transaction from a terminal.
Destination:
CSMT
ERZ027014E
A conversion template for resource

resourceName and type resourceType
is not defined
Explanation:
The resource definition for resourceName and type
resourceType has the attribute TemplateDefined set to
yes, but a conversion template for that resource cannot
be found. This is a configuration error as the
TemplateDefined must be set to yes only if you have
defined and installed a conversion template for the
resource.
The type, resourceType, is as follows.
v 0 - File Definition (FD)
v 1 - Transient Data Definition (TDD)
v 2 - Temporary Storage Definition (TSD)
v 5 - Program Definition (PD)
Data conversion templates are used by CICS to convert
application data that is sent between CICS regions
which are using different code pages. Data conversion
is performed by the mirror transaction. Therefore,
conversion templates are normally only required in the
region where the resource resides. However, if a
request is daisy-chained through a number of CICS
regions, the data conversion template can be placed in
an intermediate region. This moves the data conversion
from the resource owning region to the intermediate
region.
For more information on data conversion, see the

TXSeries for Multiplatforms Intercommunication Guide.
System action:
User response:
If conversion is not required for the resource set the
attribute TemplateDefined to no for the resource
definition and retry the transaction. If conversion is
required, define a conversion template for the resource
and make it available to the CICS region using cicscvt.
Destination:
CSMT
ERZ027015E Cannot allocate storage
Explanation:
CICS attempted to allocate task private storage when
encoding or decoding a message to be sent to or
received from a remote system, but was unsuccessful.
System action:
User response:
Consider simplifying your transactions, such that they
use less task private storage or increase the amount of
task private storage available. Refer to the TXSeries for
Multiplatforms Application Programming Guide for more
information.
Destination:
CSMT
ERZ027016E Incorrectly formatted message
received
Explanation:
CICS was not able to decode a message received from
a remote system while function shipping.
System action:
User response:
Ensure that the remote system is not executing a
Distributed Transaction Processing (DTP) transaction. If
it is, modify the transaction and/or its resource
definitions, so that it does not execute as the function
shipping mirror transaction, or does not allocate
conversations to the function shipping mirror
transaction. If this is not the case, verify that the remote
system and the connection to it are functioning normally
by performing other intersystem communication
functions (such as transaction routing) to the remote
system. If the problem persists, prepare a
organization.
Destination:
CSMT
185
ERZ027017E ERZ027021E
ERZ027017E
Data conversion routine for

resourceType resource, resourceName,
is unavailable. The server code page is
serverCodePage (serverShortCode).
The code page received from remote
system, sysId, was
receivedCodePage. The client code
page is clientCodePage
(clientShortCode)
Explanation:
CICS is unable to perform data conversion for a
function shipping request received from the remote
system defined in Communications Definitions (CD)
entry sysId because iconv conversion routines for the
requested code pages are not available.
Ensure that the data conversion routines required by

your region are correctly installed on the machine. Refer
to your operating system documentation on the iconv
utility for information on supported data conversion
routines. Some operating systems allow you to generate
you own conversion routines using the genxlt utility. If
genxlt is available, and the operating system does not
provide the conversion routines you need, then create
and install the required routines on your machine.
When the data conversion configuration is correct, rerun
the intersystem request.
Destination:
CSMT
ERZ027018E
Data conversion has been attempted because resource

resourceName has TemplateDefined=yes in its resource
definition and a conversion template is available. (Refer
to the TXSeries for Multiplatforms Intercommunication
Guide for more information on conversion templates.)
The conversion template is generated from DFHCNV
macros using cicscvt. These macros specify the
shortcode for this local CICS region
(SRVERCP=serverShortCode) and a default shortcode for
the remote system (CLINTCP=clientShortCode). The
remote system can also send its own short code, which
overrides clientShortCode. (This can be sent with the
request, or if the remote system is an IBM CICS client,
it can be sent with the client install request handled by
the CCIN transaction.)
CICS translates the shortcodes into code page names.
So serverShortCode and clientShortCode become
serverCodePage and clientCodePage respectively. (If a
shortcode is not recognized by CICS, it uses the
shortcode as the code page name.) It then calls iconv to
perform the data conversion. This message is produced
because iconv is unable to locate the conversion
routines that convert between code pages
serverCodePage and receivedCodePage or code pages
serverCodePage and clientCodePage.
System action:
User response:
Determine whether data conversion is required for this
resource. If it is not then set TemplateDefined=no in the
resourceType entry for resourceName.
Examine the shortcodes defined in the DFHCNV
macros. Check that they are being mapped to the
expected code pages. Alter the shortcodes in the
DFHCNV macros if they are not correct. For more
information on shortcodes and the DFHCNV macros
refer to the TXSeries for Multiplatforms
186
Converting from code page

codePage1 to code page codePage2
was unsuccessful
Explanation:
Data for a function shipping request was not able to be
converted between code page codePage1 and code
page codePage2 because:
v there is an error in the conversion routine or
v characters in the data are invalid for code page
codePage1 or
v characters in the data are not defined in code page
codePage2.
System action:
User response:
Ensure the data being sent or received as part of the
function shipping request is valid for code pages
codePage1 and codePage2. If not, you possibly need to
use the function shipping user conversion exit
(DFHUCNV) to convert the data. Refer to the TXSeries
information.
Ensure the conversion routines for code pages
codePage1 and codePage2 are correctly installed.
Some operating systems allow you to define you own
conversion routines using the genxlt utility. If the
conversion routine is user-defined then ensure it is
correct. Consult the operating system documentation on
iconv and genxlt for further details.
If you are unable to solve this problem yourself, contact
Destination:
CSMT
ERZ027021E Unexpected Function Shipping Error
Explanation:
The function shipping mirror transaction has failed due
to lack of system resources.
ERZ027022E ERZ027027E
System action:
User response:
information relating to this message. Consider retrying
the transaction when the system is more lightly loaded.
organization.
Destination:
CSMT
detected an inconsistency in the CICS
internal data structures
Explanation:
An inconsistency in the CICS run-time copy of the user
conversion templates has been detected.
System action:
The region continues, but the function shipping is
possibly unsuccessful.
User response:
If the inconsistency is such that the function shipping
mirror transaction is unable to convert application data,
restart the region. Also contact your support
organization.
Destination:
console.msg
ERZ027024E The mirror transaction transId is
unknown on system sysId
Explanation:
The intersystem request to run the mirror transaction
transId on the remote system configured in
Communications Definition (CD) entry sysId was
unsuccessful because transId is not recognized as a
mirror transaction by the remote system. The mirror
transaction is started in the remote system by Function
Shipping, Asynchronous Processing and Distributed
Program Link (DPL) requests. By default, CICS uses
the CPMI mirror transaction. This can be changed on
DPL requests
v using the TransId attribute of the local Program
Definitions (PD) entry for the linked-to program or
v using the TRANSID option of the EXEC CICS LINK
command.
System action:
The TERMERR condition code is returned to the
transaction.
User response:
Check that the transaction specified is supported by the
remote system and, if required, change your local
application to use a transaction that the remote system
supports. Check that the remote system is correctly
configured and running. Rerun the local transaction.
Destination:
CSMT
ERZ027025E SYNCONRETURN is not allowed when
a mirror task is already running
Explanation:
The SYNCONRETURN option has been specified in a
Distributed Program Link (DPL) request, but the
requesting program is already in conversation with a
mirror task (that is, a logical unit-of-work (LUW) is in
progress) in the remote system. The mirror task can be
a previous DPL request or a Function Shipping
command.
System action:
The INVREQ condition code is returned to the
transaction.
User response:
Correct the local program so that a syncpoint is taken
before the DPL SYNCONRETURN request, or remove
the SYNCONRETURN option from the LINK request.
Destination:
CSMT
ERZ027026E Change of mirror transaction to
newTransId is not allowed; oldTransId
is still running
Explanation:
newTransId has been specified, either as the TRANSID
option, or in the TransId attribute of the Program
Definition (PD), in a Distributed Program Link (DPL)
request. However, the requesting program is already in
conversation with a mirror task (that is, a logical
unit-of-work (LUW) is in progress) in the remote region
with TRANSID oldTransId. The mirror task can be a
previous DPL request or a Function Shipping command.
System action:
The INVREQ condition code is returned to the
transaction.
User response:
Remove the TRANSID option from the DPL request, or
the TransId attribute from the PD, so that the DPL
request runs under the TransId of the existing mirror
task (or change it to be the same explicitly).
Alternatively, take a syncpoint before the DPL request,
to complete the previous mirror task.
Destination:
CSMT
ERZ027027E A DPL mirror transaction cannot reply
to a syncpoint request received on a
DTP conversation with system sysId
Explanation:
The current program was started as the result of a
Distributed Program Link (DPL) request which did not
specify the SYNCONRETURN option. It has started a
187
ERZ027028E ERZ028001E
Distributed Transaction Processing (DTP) conversation
with another system sysId. The program that originated
the DPL request is the only one which is allowed to
issue syncpoint or backout commands.
Destination:
CSMT
System action:
ERZ027029E An intersystem request has

abnormally terminated with abend
code abendCode
User response:
Correct the programs so that the originator of the DPL
request is the only one that issues syncpoints, or use
the SYNCONRETURN option.
Explanation:
An intersystem request has abnormally terminated. A
symptom record (symrec) describing the problem has
been created and further messages can be logged.
Destination:
CSMT
System action:
code abendCode.
ERZ027028E
Unauthorized to run mirror

transaction transId on remote system
sysId for user userId
Explanation:
A function shipping request was unsuccessful because
either the local CICS region or the user userId does not
have sufficient authority to access:
v the remote system,
User response:
Follow the instructions given for the abend code
abendCode and any additional messages logged. If you
can not solve the problem yourself, save the CSMT log,
console.msg file and the symrec file and contact your
Destination:
CSMT
v the PPC gateway (if applicable),

v the mirror transaction transId or
v the resources requested in the function shipping
request.
Possible reasons for this include:
v on a SNA connection using a PPC gateway the
RuntimeProtection attribute in the Region Definition
(RD) entry for your region is different from the
ProtectionLevel attribute of your PPC gateway.
v on a TCP connection the RuntimeProtection attribute
in the RD entry for your region is different from the
RuntimeProtection in the remote regions RD entry.
v the remote system is expecting your local region to
send the users userid with the function shipping
request. However, the OutboundUserIds attribute in
the Communications Definition (CD) entry sysId is set
to not_sent. CICS sends the userid only if
OutboundUserIds=sent.
v the security configuration in the remote system does
not allow the local system, or the user userId, to
access either the mirror transaction transId or the
resources specified in the function shipping request.
System action:
The NOTAUTH condition is returned to the transaction.
User response:
If the user is supposed to have authority to access the
resources on the remote system then check the security
configuration in the local region, remote system and, if
applicable, PPC gateway to determine why the request
was unsuccessful. Refer to the TXSeries for
Multiplatforms Intercommunication Guide for information
on configuring intersystem security. Correct the source
of the problem and rerun the transaction.
188

connection to system sysId occurred
during remote command command
Explanation:
CICS detected a communications error while processing
an EXEC CICS command in conjunction with the
(CD) entry sysId. The type of error detected is
described by error code primaryCode/secondaryCode.
System action:
CICS abnormally terminates the intersystem request for
the EXEC CICS command. Further messages can be
logged.
User response:
Intercommunication Guide, which describes what the
error code primaryCode/secondaryCode means and
how to correct the problem.
Destination:
CSMT
ERZ028001E The connection to the remote system
sysId cannot be started.
Communications error
primaryCode/secondaryCode
Explanation:
CICS is unable to connect to the remote system
configured in Communications Definition (CD) entry
sysId. The error is described by the return codes
primaryCode/secondaryCode.
System action:
ERZ028002E ERZ028004E
continues.
User response:
Ensure that the remote system and the connection to it
are available. See the TXSeries for Multiplatforms
Intercommunication Guide for information about the
primary and secondary return codes.
Destination:
CSMT
primaryCode/secondaryCode detected
while communicating with the remote
system sysId
Explanation:
CICS received an error during communications with the
(CD) entry sysId. The error is described by the return
codes primaryCode/secondaryCode. Additional
information can possibly also be logged in a symptom
record (symrec).
System action:
continues.
User response:
Use the primary and secondary return codes
(primaryCode and secondaryCode respectively) to
determine the cause of the communications error. See
the TXSeries for Multiplatforms Intercommunication
Guide for information about the return codes and the
action to take.
Destination:
CSMT
ERZ028003E
The Terminal Definition for terminal

termId on system sysId is not
shippable
Explanation:
A Terminal Definition (WD) entry for the terminal termId
does not exist on the local system and cannot be
requested from the remote system defined in
Communications Definition (CD) entry sysId because
the terminal is defined on the remote system as not
shippable.
System action:
continues.
User response:
If you wish the remote system to ship terminal
definitions, configure the terminal definition in the
remote system as shippable. If the remote system is
CICS on Open Systems or CICS for Windows NT,
version 4, set the IsShippable attribute in the relevant
remote Terminal Definition (WD) entry to yes and
re-install the definition. If the remote system is not CICS
on Open Systems or CICS for Windows NT, version 4,

consult the appropriate documentation for the system to
determine how to configure the terminal definition as
shippable.
If you do not wish to ship terminal definitions from the
remote system, then create and install a Terminal
Definition (WD) entry on your local CICS region for the
remote terminal.
For more information about defining terminals as
shippable, refer to the TXSeries for Multiplatforms
Destination:
CSMT
ERZ028004E
Transaction transId, started by

terminal termId is part of a transaction
routing loop
Explanation:
CICS has routed transaction transId to a remote
system and the remote system then routed this request
back to CICS. CICS does not continue with the request
because there is a problem with the definition of
transaction transId, either in the local system or in the
remote system, which means that if CICS sends the
transaction request to the remote system system again,
the remote system probably routes it back to CICS. This
is called a transaction routing loop.
System action:
continues.
User response:
If you are running the CICS transaction CRTE, ensure
that you are not routing a transaction from the remote
system back to the local system (doing so creates a
loop).
If the transaction is defined as remote (see the
RemoteSysId attribute in the local Transaction
definitions (TD) entry) check the transactions definition
on the remote system. Ensure that this definition does
not define the transaction as a remote transaction back
onto this local region (thus creating a loop). If the
remote system is CICS on Open Systems or CICS for
Windows NT, version 4, you can do this by checking the
RemoteSysId attribute in the relevant TD entry on the
remote system. If the remote system is not CICS on
Open Systems or CICS for Windows NT, version 4,
consult the appropriate documentation to find out how
transactions are defined for that system.
Destination:
CSMT
189
ERZ028005E ERZ028009E
ERZ028005E Remote system sysId is unavailable
to run the transaction transId
Explanation:
Transaction transId is defined to be remote but the
transaction cannot be started because:
v The Communications Definition (CD) entry sysId is
not defined to your region.
v CD entry sysId is configured with attribute
InService=no. This means it is out of service and
unavailable for intersystem requests.
v The remote system configured in CD entry sysId can
not be contacted. This is possibly because it is not
running or the network is unavailable or the remote
systems location is incorrectly configured in CD entry
sysId.
v There is a problem with the configuration in your
region which is preventing intersystem requests from
using CD entry sysId.
System action:
User response:
Examine the CICS message files (CSMT and
console.msg) to determine why the remote system is
unavailable and follow the instructions for these
messages.
Destination:
The users screen.
ERZ028006E Transaction transId, running on
system sysId abnormally terminated
Explanation:
Routed transaction transId abnormally terminated on
(CD) entry sysId.
System action:
CICS abnormally terminates the local transaction. The
region continues.
User response:
Use the procedures that are appropriate for the remote
system to determine the reason for the abnormal
termination of the transaction.
Destination:
CSMT
ERZ028007E The connection to the remote system
sysId has failed. Communications
error primaryCode/secondaryCode
Explanation:
Communications with the remote system configured in
Communications Definition (CD) entry sysId has
stopped because of network failure or remote system
shutdown.
System action:
190

continues.
User response:
are available. If you require more detailed information
about the cause of this error, refer to the TXSeries for
Multiplatforms Intercommunication Guide for details of
the primary and secondary return codes (primaryCode
and secondaryCode respectively).
Destination:
CSMT
ERZ028008E A communications error occurred
while CICS was running transaction
transId routed from remote system
sysId
Explanation:
The remote system configured in Communications
Definition (CD) entry sysId has requested that
transaction transId is run on this local CICS region.
However, while CICS was either starting transaction
transId or running transaction transId, it detected a
communications error with the remote system.
System action:
continues.
User response:
Refer to previous messages associated with this
transaction in the CSMT log for further details about the
communications error. Follow the instructions for these
messages.
Destination:
CSMT
ERZ028009E A communications error occurred
during transaction routing of transId
to the remote system sysId.
Explanation:
During routing of the transaction transId to the remote
entry sysId, a communications error was detected.
System action:
continues.
User response:
Refer to previous messages associated with this
transaction in the CSMT for further details about the
communications error and for information about the
action to take.
Destination:
CSMT
ERZ028010E ERZ028013E
ERZ028010E
The relay transaction on system

sysId has abnormally terminated while
executing transaction transId
Explanation:
The conversation between local transaction transId and
a transaction running on the remote system defined in
abnormally terminated. Possible reasons include:
v Transaction transId is communicating with a terminal
attached to the remote system and the CICS relay
transaction running on the remote system to control
the terminal has abnormally terminated. This occurs if
the local transaction transId has sent a datastream
containing control commands (such as PRINT) that
the remote terminal does not support.
v Transaction transId is communicating with a
Distributed Transaction Processing (DTP) program
that has either abnormally terminated or called the
EXEC CICS ISSUE ABEND command.
System action:
User response:

continues.
User response:
Ensure that the transaction transId is being started
from a terminal and not by another transaction
executing ATI commands to start the transaction.
Destination:
CSMT
ERZ028012E
The transaction transId was unable

to run on system sysId.
Communications error
Explanation:
The transaction transId was not able to be started on
the remote system configured in Communications
Definition (CD) entry sysId because transaction
transId is not defined on that remote system.
System action:
continues.
v If transaction transId is a terminal transaction which

has been started by a transaction routing request
from the remote system, examine the messages in
the remote system to discover why the relay
transaction abnormally terminated. Follow the
instructions for these messages.
User response:
If the Transaction Definition (TD) entry for the
transaction transId has the attribute RemoteName set,
check that its value is the correct name for the
transaction on the remote system. If required, correct
the RemoteName attribute and re-install the TD entry
into the local region.
v If transaction transId is a DTP back end program

which was started by a DTP front end program, alter
the Transaction Definitions (TD) entry for transId so
IsBackEndDTP=yes.
If the RemoteName attribute is correct, verify that the

transaction with the name specified by the attribute is
available on the remote system.
v If transaction transId is a terminal transaction which

has been started by a DTP front end program, alter
the DTP front end program so it starts a back end
DTP program rather than transaction transId.
If the RemoteName attribute is not set, verify that the

transaction with the name transId is available on the
remote system.
Once the necessary corrections have been made to the

configuration and applications, rerun the request.
Destination:
CSMT
ERZ028011E The principal facility for the relay
transaction running transaction
transId is not a terminal.
Explanation:
The relay transaction was started without a terminal as
its principal facility.
The relay transaction is a CICS-private transaction that
provides the communication mechanism between the
terminal and the remote transaction transId that you
are attempting to run.
System action:
See the TXSeries for Multiplatforms Intercommunication

Guide for information about the primary and secondary
return codes.
Destination:
CSMT
ERZ028013E
Request received from system sysId

to ship a definition for terminal termId
which is not shippable
Explanation:
A request to ship a terminal definition for terminal
termId has been received from the remote system
sysId. The terminal definition cannot be shipped
because its Terminal Definition (WD) entry has
IsShippable=no. This means the terminal definition must
not be sent to a remote system.
System action:
191
ERZ028014E ERZ028016E
continues.

continues.
User response:
Confirm that it is desirable for the local system to ship a
terminal definition for the terminal termId. If it is, set the
IsShippable attribute of the WD entry for the terminal to
yes.
User response:
If this message is displayed in the application owning
system, verify that the remote system is not attempting
to start a backend Distributed Transaction Processing
(DTP) transaction whose local Transaction Definition
(TD) entry has the attribute IsBackEndDTP set to no. If
the remote system is running a DTP transaction then
set IsBackEndDTP to yes.
If it is not desirable to ship the terminal definition for

terminal termId from the local system, consider adding
a definition of the terminal on the remote system. If the
remote system is CICS on Open Systems or CICS for
Windows NT, version 4, this can be achieved by adding
a WD entry for the terminal, with the RemoteSysId
attribute set to the name of a Communications Definition
(CD) entry that defines a connection to the local region.
Otherwise consult the appropriate documentation for the
remote system to find out how to add the terminal
definition.
Destination:
CSMT
ERZ028014E Transformer number number could not
allocate storage
Explanation:
CICS is unable to allocate task private storage for a
message that is to be sent to or received from a remote
system. If the transformer number is 1 or 3, the storage
is being allocated while encoding a message to be sent
to a remote system. If the transformer number is 2 or 4,
the storage is being allocated while decoding a
message received from a remote system.
System action:
continues.
User response:
Retry the transaction when the system is more lightly
loaded or simplify the transaction so that it uses less
task private storage. Alternatively, increase the size of
the task private storage pool. This is configured in the
Region Definition (RD) entry attribute
MaxTaskPrivatePool.
Destination:
CSMT
ERZ028015E
Transformer number number received

an incorrectly formatted message
Explanation:
CICS was not able to decode a message received from
a remote system while transaction routing. If the
transformer number is 2, the message was received
from a remote terminal owning region. If the transformer
number is 4, the message was received from a remote
application owning region.
System action:
192
If this message is displayed in the terminal owning

region, verify that the remote transaction is not a back
end DTP transaction.
If neither of the above is the case, verify that the remote
system and the connection to it are functioning normally,
by performing other ISC functions (such as Function
Shipping) to the remote system. If the problem persists,
prepare a communications trace showing the data
received from the remote system and contact your
Destination:
CSMT
ERZ028016E Terminal Definition (WD) for terminal
termId is being used by another
terminal
Explanation:
CICS is unable to continue with a transaction routing
request for terminal termId because this terminal is
already in use by another transaction. This is possibly
because there are two terminals with the same name
(termid), possibly owned by different connected CICS
regions, that are running transactions on your local
region.
System action:
continues.
User response:
Retry the transaction. If the problem persists, consider
trying to make the terminal name unique within your
connected CICS regions. This can be achieved by
modifying the program that provides the terminal name.
If the terminal owning region is CICS on Open Systems
or CICS for Windows NT, version 4, this is the
DFHCHATX program. Alternatively, consider creating a
local WD entry for the remote terminal, specifying the
RemoteName and RemoteSysId attributes so the
terminal runs with a different name in the local region.
Destination:
CSMT
ERZ028017E ERZ028023E
ERZ028017E Converting from code page
was unsuccessful
Explanation:
The terminal datastream was not able to be converted
from the code page codePage1 to the code page
codePage2. This conversion is carried out when
encoding or decoding data that is about to be sent to, or
has been received from a remote system.
System action:
continues.
User response:
Ensure that the transaction is not sending terminal data
which contains characters that are not part of the
character set specified by the code page codePage1.
Further ensure that the transaction is not sending
terminal data which cannot be converted from the code
page codePage1 to the code page codePage2.
Consult the operating system documentation for further
details. If neither of the above is the case, then contact
Destination:
CSMT
ERZ028018E An operation on the terminal termId
was unsuccessful
Explanation:
A terminal related error occurred during one of the
following situations:
v CICS was attempting to receive data from or send
data to the terminal termId
v CICS was attempting to attach the terminal termId to
a task
System action:
continues.
User response:
Look in the CSMT and console.msg for additional
messages (of the form ERZ062nnns) giving more
information as to why the terminal operation was
unsuccessful. If the problem persists, then contact your
Destination:
CSMT
ERZ028020E Transaction transId cannot install a
TCTUA received from system sysId in
the Terminal Definition (WD) for
terminal termId
Explanation:
A Terminal Control Table User Area (TCTUA) has been
received whose length differs from the TCTUA length
specified in the local WD entry for the terminal.
System action:
continues.
User response:
Consider altering the TCTUALen attribute of the local
systems WD entry for the terminal and the TCTUA
length of the remote terminal definition so that they
match. If this message is displayed in the transaction
owning region, also consider deleting the local terminal
definition and allowing the remote system to ship
terminal definitions.
Destination:
CSMT
ERZ028021E The nominated next transaction
transId could not be started
Explanation:
CICS was not able to start the next transaction in a
pseudo-conversation sequence of transactions.
System action:
continues.
User response:
Verify that the nominated transaction is defined by
examining the entries in the Transaction Definitions
(TD).
Destination:
CSMT
ERZ028023E
Unexpected message received from

system sysId
Explanation:
CICS received an unexpected message from the remote
system. This has placed the conversation with the
remote system in such a state that the transaction
routing session cannot continue.
System action:
continues.
User response:
If this message is displayed in the application owning
region, verify that the remote system is not attempting
to start a back end Distributed Transaction Processing
(DTP) transaction whose local Transaction Definition
(TD) entry has the attribute IsBackEndDTP set to no. If
the remote system is running a DTP transaction, set
IsBackEndDTP to yes in the local Transaction Definition
(TD) entry.
If this message is displayed in the terminal owning
region, verify that the remote transaction is not a
backend DTP transaction.
If neither of the above is the case, check that the
transaction is not sending an invalid datastream, and
193
ERZ028025E ERZ028030E
verify that the remote system and the connection to it
are functioning normally, by performing other ISC
functions (such as Function Shipping) to the remote
system. If the problem still persists, prepare a
organization.
Destination:
CSMT
ERZ028025E
Cannot start transaction transId

from system sysId on the terminal
termId
Explanation:
CICS received a request from the remote system
sysId to start the transaction transId using the terminal
termId. CICS is unable to proceed with the request
because the RemoteSysId attribute on the Terminal
Definition (WD) entry for termId is not specified so the
terminal is defined as local.
ERZ028027E Unable to route transaction transId to

local system sysId
Explanation:
In the Transaction Definition (TD) entry for transaction
transId the RemoteSysId attribute names the local
system. The local systems name is specified in the
LocalSysId attribute of the Region Definition (RD) entry.
System action:
continues.
User response:
If you wish to run the transaction transId locally, do not
specify anything on the RemoteSysId attribute in the TD
entry. Otherwise, specify a RemoteSysId attribute in the
transactions TD entry which is the name of a
Communication Definition (CD) for a remote CICS
system.
Destination:
CSMT
System action:
continues.
ERZ028029E
User response:
Explanation:
CICS was not able to link to the transaction routing
User Conversion Program programName when
transaction routing to a remote system.
v If you require the terminal termId to be defined as

local to this CICS system, ensure that the remote
system sysId ships a terminal name that is unique
within your connected CICS systems. If the remote
system is CICS on Open Systems or CICS for
Windows NT, version 4, this can be done by
modifying its DFHCHATX program. For more
information on DFHCHATX, refer to the TXSeries for
Multiplatforms Intercommunication Guide. If the
remote system is not CICS on Open Systems or
CICS for Windows NT, version 4, refer to the
appropriate documentation for that systems user exit
program that provides the terminal name.
Alternatively, consider creating a local WD entry for
the terminal that is shipped from the remote system,
specifying RemoteName=termId and
RemoteSysId=sysId, so that the remote terminal has
a different name when it is using transactions on the
local region.
v If the terminal termId does not need to be defined as
local to this CICS region, alter the RemoteName
attribute on the terminals WD entry so that it
specifies the name of the Communications Definition
(CD) entry for the connection to the remote system.
Intercommunication Guide for more information on
shipped terminals.
Destination:
CSMT
194
Unsuccessful link to transaction

routing User Exit programName, when
transaction routing to system sysId
(The default transaction routing User Conversion

Program is DFHTRUC.)
System action:
continues.
User response:
1. Ensure that the Program Definition (PD) entry for
programName exists and that the EnableStatus
attribute is set to enabled.
2. Check that the PathName attribute in the PD entry
is correct (refer to the TXSeries for Multiplatforms
PathName).
3. Ensure that the program specified by the PathName
attribute in the PD entry exists and is executable.
For more information on DFHTRUC refer to the
Destination:
console.msg
ERZ028030E The transaction transId is unknown
on the remote system sysId
Explanation:
An attempt was made to run the transaction transId on
the remote system configured in Communications
ERZ028031E ERZ028034E
Definition (CD) entry sysId. This was unsuccessful as
the transaction is not defined on the remote system.
System action:
User response:
Verify that the transaction name transId is correct.
v If you wish to run transaction transId locally, set
RemoteSysId= in the Transaction Definition (TD)
entry transId.
v If you wish to run the transaction remotely, set the
RemoteSysId attribute of TD entry transId to the
name of a Communications Definition (CD) entry that
defines the location of the remote system on which
you wish to run the transaction.
Check that the transaction specified on the
RemoteName attribute in TD entry transId is
available on the remote system. (If the RemoteName
attribute is blank (), check transaction transId is
available on the remote system.)
Destination:
The users screen.
ERZ028031E Cannot start transaction transId on
the remote system sysId because the
remote system is out of service
Explanation:
Transaction transId is defined to be remote but the
transaction cannot be started because the remote
system is out of service.
System action:
User response:
Verify that the remote system is supposed to be in
service. If it is, put the system back in service by setting
the InService attribute of the Communication Definition
(CD) entry sysId for the remote system to yes.
Re-install the CD entry and re-submit the transaction.
Destination:
CSMT
ERZ028032E Cannot install terminal definition for
terminal termId shipped from system
sysId
Explanation:
CICS was not able to install a terminal definition for
terminal termId that has been requested from the
entry sysId.
System action:
continues.
User response:
Consider retrying the transaction when system sysId is
more lightly loaded. Consider increasing the size of the
task shared memory pool and the region memory pool.

This can be achieved by increasing the values given in
the MaxTSHPool and MaxRegionPool attributes of the
Region Definition (RD). CICS can possibly log additional
messages which give further information about why the
operation was unsuccessful. If the problem persists,
Destination:
console.msg
ERZ028033E Transaction transId cannot be run on
remote system sysId because the
remote system is unknown to CICS.
Explanation:
CICS is unable to run the remote transaction transId
because the Transaction Definition (TD) entry for the
transaction has the RemoteSysId attribute set to sysId
which is not the name of a Communications Definition
(CD) entry. The CD entry defines which system to which
the transaction is to be routed.
System action:
continues.
User response:
Either:
v Alter TD entry transId so the RemoteSysId attribute
is set to the name of a CD entry which defines the
location of the remote system.
v Create a CD entry called sysId which defines the
location of the remote system.
v Alter TD entry transId so the RemoteSysId attribute
is set to , which means the transaction runs on the
local CICS region.
Once all updated definitions are installed in your region,
re-submit the transaction.
Destination:
CSMT
ERZ028034E Attempt to free COMMAREA at
address address failed. This is not a
valid storage area address.
Explanation:
The COMMAREA passed to the Transaction Routing
User Conversion Program (DFHTRUC) has been
corrupted. It is likely that the COMMAREA at address
address has already been processed by another
FREEMAIN call.
System action:
User response:
Investigate the use of FREEMAIN of COMMAREAs in
DFHTRUC.
Destination:
195
ERZ028035E ERZ028041E
CSMT
ERZ028035E Attempt to free TCTUA at address
address failed. This is not a valid
storage area address.
Explanation:
The terminal user area (TCTUA) passed to the
Transaction Routing User Conversion Program
(DFHTRUC) has been corrupted. It is likely that the
TCTUA at address address has already been processed
by another FREEMAIN call.
System action:
User response:
Intercommunication Guide for details of the return codes
and the action to take. Ensure that the versions of
software used by your CICS region are compatible. Also
check that the software running on the remote system is
compatible with your local CICS region. If the remote
system is connected to your CICS region via a PPC
Gateway and a Systems Network Architecture (SNA)
network then check that the version of the PPC gateway
is compatible with the versions of CICS used by your
local region. If you find that the software used by the
communicating systems is incompatible then install the
correct versions. Try the transaction again. If the
User response:
Investigate the use of FREEMAIN of TCTUAs in
DFHTRUC.
Destination:
CSMT
Destination:
CSMT
ERZ028039I Terminal termId no longer

communicating; netname netName.
ERZ028036E Serious storage problem encountered

with region storage.
Explanation:
CICS is unable to get storage in which to build a list of
remote system identifiers to which the Terminal
Definition (TD) has been shipped. This is likely to be
just one manifestation of a much more serious problem.
System action:
User response:
Look on the console for associated messages and take
the actions recommended to resolve the problem.
Destination:
CSMT
ERZ028038E
Unexpected communications error

conversation with system sysId while
running transaction transId
Explanation:
CICS detected an unexpected condition while
communicating with the remote system configured in
Communications Definition (CD) entry sysId and is
therefore unable to continue with the transaction transId.
If the local CICS system is the terminal owning region,
then transId is the name of the remote transaction
running on the application owning region sysId. If the
local CICS system is the application owning region, then
transId the name of the local transaction which has
been transaction routed from the terminal owning region
sysId to the local CICS system.
System action:
A28M.
196
Explanation:
A terminal can no longer be contacted by the region.
System action:
The region no longer tries to communicate with the
terminal and frees up the netname for future use by
another terminal program.
User response:
None
Destination:
CSMT
ERZ028040E Transaction transId cannot be
onward routed as it is defined as
dynamic in an intermediate system.
Explanation:
A dynamic transaction can only be started in the
terminal owning system. A dynamic transaction cannot
exist on an intermediate system.
System action:
User response:
Ensure that dynamic transactions are only invoked in
the terminal owning system. Ensure that the local
transaction definition does not specify that the
transaction is dynamic.
Destination:
console.msg
ERZ028041E Intersystem request received for
transaction transId was unsuccessful
because the TD entry is configured
incorrectly for this type of request.
Explanation:
CICS is unable to accept an intersystem request for
transaction transId because the Transaction Definition
ERZ028042E ERZ030003W
(TD) entry is incompatible with the received request.
The received request indicates that the remote system
issued either a function ship, Distributed Program Link
(DPL) or Distributed Transaction Processing (DTP)
request.
System action:
The intersystem request fails. Further messages can
possibly be logged and the request terminated
abnormally.
User response:
Check the type of intersystem request is compatible
with the TD entry transId. If the request was for DPL
and the user program specifies a TRANSID for
transaction transId, check that this name does not
conflict with the name of an already defined non-DPL
transaction.
If the request was for function ship or DPL, ensure the
TD entry has the attribute Program set to DFHMIRS. If
the request was DTP, ensure the TD entry has the
attribute IsBackEndDTP set to yes.
Destination:
CSMT
Explanation:
System action:
will abend.
User response:
Destination:
console
ERZ029031E
transId sent data using the

commandName command on
conversation convId which is in state
conversationState.
Explanation:
Transaction transId issued the commandName
command with the FROM option on a Distributed
Transaction Processing (DTP) conversation convId. The
FROM option requests CICS to send data on the
conversation. The commandName command was
unsuccessful because the state conversationState does
not permit CICS to send data. This is a programming
error in the application program.
System action:
ATCV.
User response:
Correct the application program using the information in
Guide that explains how to write DTP programs. The
TXSeries for Multiplatforms Application Programming
Reference describes which commands are allowed in
each conversation state and the commands to issue to
change the conversation to the state required by your
application.
Destination:
CSMT
ERZ030001I CD entry sysId has been set up for the
local region
Explanation:
CICS has added a Communications Definition (CD)
entry for the local region as part of region initialization.
The SYSID for this CD entry, sysId, is defined in the
LocalSysId attribute of the Region Definition (RD).
System action:
User response:
None
Destination:
console.msg
ERZ030002W The local SYSID for this region is null
Explanation:
The LocalSysId attribute of the Region Definition (RD)
entry is null (). This means that intersystem requests
can not be issued by transactions running on your
region. In addition, your region will not be able to
receive intersystem requests.
System action:
CICS continues processing. However, all intersystem
requests will fail.
User response:
If your transactions are to issue intersystem requests
set the LocalSysId attribute of the RD entry. This must
be between 1 and 4 characters long. Once the
LocalSysId attribute of the RD entry is configured restart
your region so that the new value can take effect.
Destination:
console.msg
ERZ030003W A CD entry for the local SYSID sysId
exists and is being ignored
Explanation:
197
ERZ030004I ERZ030007E
The Communications Definition (CD) entry sysId has
the same name as your regions local SYSID defined in
the Region Definition (RD) entry attribute LocalSysId.
System action:
CICS continues processing. CD entry sysId will be
ignored and is not available for intersystem
communication.
User response:
If CD entry sysId is required for intersystem requests
modify either the LocalSysId attribute of the RD, or the
name of the CD entry so that these two values are
different.
Note: If you modify the LocalSysId attribute, you must
restart your CICS region before this value will
take effect. If you modify the name of the CD
entry ensure that the updated CD entry is
installed in your CICS region. The TXSeries for
Multiplatforms Intercommunication Guide
describes how to make changes to CD entries.
Destination:
console.msg
v CICS1
v OPENCICS
v MYLU
and the following values are invalid.
9
Begins with a number
1CICS
OPENcics
Contains lower case alphabetic characters
MY-LU
Contains the unsupported character -
System action:
CICS continues processing. SNA intersystem requests
will fail.
User response:
Modify the LocalLUName attribute of the RD so that it
contains a valid SNA LU name. Then restart your region
so that the new local LU name takes effect.
Destination:
console.msg
ERZ030004I Using LUname as the default SNA local

LU name
Explanation:
CICS will use LUname as its default local Logical Unit
(LU) name. The local LU name is the name that remote
systems use to contact your region across a Systems
Network Architecture (SNA) network. This LU name is
normally defined in the LocalLUName attribute of the
Region Definition (RD). If, however, LocalLUName=,
CICS will use the region name as the default local LU
name.
ERZ030006I PPC gateway GDname will use LUname

as the SNA local LU name
User response:
None
Explanation:
The PPC gateway defined in Gateway Definition (GD)
GDname will use local Logical Unit (LU) name LUname
for your region when communicating with remote
systems across a Systems Network Architecture (SNA)
network. The local LU name is the name that these
remote systems use to contact your region. It is defined
in the GatewayLUName attribute of the GD. If
GatewayLUName= the PPC gateway will use the
value in the LocalLUName attribute of the Region
Definition (RD). (If LocalLUName= it will default to the
name of your region.)
Destination:
console.msg
System action:
ERZ030005W
User response:
None
System action:
The default SNA local LU name

LUname contains unsupported
characters
Explanation:
The default local Logical Unit (LU) name for this region
LUname contains characters that are not supported by
the Systems Network Architecture (SNA). The LU name
must be no more than eight characters long. The first
character of this field must be an upper case alphabetic
character (A-Z) and the subsequent characters must be
either upper case alphabetic characters or numeric
(0-9). For example, the following values are valid for the
local LU name:
v A
198
Destination:
console.msg
ERZ030007E An inconsistency has been detected
in a CICS internal data structure
Explanation:
System action:
The region continues, but intersystems communication
can possibly be unsuccessful.
User response:
ERZ030008E ERZ030018W
Restart your region. If the condition persists, perform a
system dump and contact your support organization.
Destination:
console.msg
primaryCode/secondaryCode prevents
intersystem request for transaction
transId from starting
Explanation:
CICS was unable to start transaction transId. This
transaction was requested by a remote system as part
of an intersystem request. The error codes
primaryCode/secondaryCode describe the reason for
the failure.
System action:
User response:
Look for additional messages that explain the cause of
the error and follow the instructions associated with
these messages. The TXSeries for Multiplatforms
Intercommunication Guide provides information about
the communications error codes primaryCode/
secondaryCode.
Destination:
console.msg
ERZ030010W Unsuccessful syncpoint for
transaction transactionNumber - the
transaction is rolled back
Explanation:
A participant of transaction transactionNumber, has
requested a backout, or has abnormally terminated, in
response to a syncpoint request. It is also possible that
the local transaction was forcibly terminated during
syncpoint processing. The participant was possibly a
synclevel syncpoint PPC conversation, a Structured File
System (SFS) server, or an XA database server. If the
local transaction executed an explicit syncpoint (using
EXEC CICS SYNCPOINT), the local transaction, and all
of its participants are rolled back. If CICS executed an
implicit (end of transaction) syncpoint, the local
transaction, and all of its participants are abnormally
terminated.
System action:
The transaction abnormally terminates, or is rolled back.
User response:
Investigate the transaction participants, using
procedures appropriate to each, in order to determine
which of them requested the backout, or abnormally
terminated, and why it did so.
Destination:
CSMT

transaction transactionNumber - some
processing backed out
Explanation:
CICS has detected heuristic damage when performing
syncpoint processing for transaction transactionNumber.
This means that some participants of the transaction
have been committed, while others have been backed
out. The participants involved can be synclevel
syncpoint PPC conversations, Structured File System
(SFS) servers, or XA database servers.
System action:
User response:
Use the procedures appropriate to the participant
systems to determine why heuristic damage was
reported. The participant systems possibly require
manual intervention to synchronize resources that have
been either rolled back or committed.
Destination:
CSMT
transaction transactionNumber. PPC
error code errorCode (errorString)
Explanation:
A PPC error was reported when the local transaction
executed a syncpoint or syncpoint rollback.
System action:
User response:
information on why the syncpoint or syncpoint rollback
was unsuccessful. If your transaction is executing
Distributed Transaction Processing (DTP) commands
and the message indicates that PPC detected a state
error on one of its conversations, examine your
transaction and ensure that all of its synclevel syncpoint
conversations are in the appropriate state to execute a
syncpoint.
Destination:
CSMT
ERZ030018W The LD entry LDname referenced by
CD entry sysId is not configured for
TCP/IP
Explanation:
ConnectionType=cics_tcp and ListenerName=LDname.
The ListenerName attribute must therefore be
configured with the name of a Listener Definition (LD)
entry which has Protocol=TCP. However, LD entry
LDname does not have Protocol=TCP configured.
System action:
199
ERZ030019W ERZ030021E
Intersystem requests using CD entry sysId will fail.
User response:
Examine the CD entry sysId. If the ConnectionType is
cics_tcp, either:
v Alter LD entry LDname so that Protocol=TCP and the
other attributes are correctly configured for CICS
family TCP/IP.
or
v Alter CD entry LDname so that the ListenerName
attribute is set to the name of a CICS family TCP/IP
LD entry.
The TXSeries for Multiplatforms Intercommunication
Guide describes the LD and CD entries required for
CICS family TCP/IP support and how to install these
entries in your CICS region.
Destination:
console.msg
ERZ030019W The LD entry LDname referenced by
CD entry sysId does not exist
Explanation:
ListenerName=LDname. This attribute must be
LDname is not configured in your region.
System action:
Intersystem requests using CD entry sysId will fail.
User response:
cics_tcp, either:
Communications Definition (CD) sysId. However this

failed with the error code errorCode.
System action:
The current intersystem request fails. Further messages
can be logged.
User response:
Check that the versions of PPC and CICS installed on
your machine are compatible. If they are not compatible
install the correct versions. If you can not solve this
problem contact your support organization.
Destination:
console.msg
ERZ030021E
The GD entry GDname referenced

by CD entry sysId does not exist
Explanation:
An intersystems request was unsuccessful because the
Systems Network Architecture (SNA) Communications
Definition (CD) entry sysId references the Gateway
Definition (GD) entry GDname in the GatewayName
attribute. However, the GD entry GDname does not
exist. CICS requires the GD entry to contact the PPC
gateway and to authenticate requests from the PPC
gateway.
System action:
The current intersystem request fails.
User response:
Examine the CD entry sysId. If a PPC gateway is not
required to contact the remote system defined in CD
entry sysId, set the GatewayName attribute to . If a
PPC gateway is required to contact the remote system:
v Determine the name of the PPC gateway to be used.
v Configure a CICS family TCP/IP LD entry called

LDname in your region.
v View each of the GD entries defined in your region to

determine whether your region has a GD entry for
this PPC gateway.
or
v If there is a GD entry for the PPC Gateway check it

has been installed into the region. (Is the
ActivateOnStartup attribute set to Yes?)
v Alter CD entry sysId so that the ListenerName

LD entry.
CICS family TCP/IP support and how to install these
Destination:
console.msg
ERZ030020E Unable to add a PPC alias alias of
type aliasType and name DCEname for
CD entry sysId. The error code was
errorCode (errorString).
Explanation:
CICS issued a PPC function call to configure PPC with
details of the remote system described in
200
v If a GD entry for the PPC gateway does exist in your

region, modify the GatewayName attribute for the CD
entry sysId to be the name of the GD entry for the
PPC gateway.
v If a GD entry does not exist in your region create a
GD entry called GDname.
Ensure all updated CD and GD entries are installed in
your region.
Guide describes the GD and CD entries required for
SNA communications and how to install these entries in
your CICS region.
Destination:
console.msg
ERZ030022E ERZ030026W
ERZ030022E Unable to allocate storage for
incoming data
Explanation:
CICS attempted to allocate task private storage for a
message received as part of an intersystem request, but
this was unsuccessful.
System action:
User response:
Consider re-running the transaction at a later time when
the system is more lightly loaded. If this is a recurring
problem also consider simplifying your transactions, so
that they use less task private storage.
Destination:
console.msg
connection to system sysId
Explanation:
Communications error primaryCode/secondaryCode was
detected while communicating with the remote system
sysId
System action:
User response:
Ensure the remote system and the connection to it are
available. The TXSeries for Multiplatforms
Intercommunication Guide contains information about
the communications error codes primaryCode/
secondaryCode.
Destination:
CSMT
ERZ030024E Intersystem request for transaction
transId was unsuccessful because
connection sysId is out of service
Explanation:
CICS is unable to proceed with an intersystem request
because the Communications Definition (CD) entry
sysId has the InService attribute set to no. This makes
the CD entry unavailable for all intersystem requests
regardless of whether they are issued locally or
received from a remote system.
System action:
The intersystem request fails. Further messages can be
logged. The connection remains out of service.
User response:
Verify that the connection is supposed to be out of
service. If it is not supposed to be out of service, set the
connection in service. This can be achieved while the
CICS region is running, using the EXEC CICS SET
CONNECTION command. However, when the region is
restarted, the state of the connection will depend on the
InService attribute of the Communication Definition (CD)

entry sysId. Therefore, to make the connection default
to be in service whenever its CD entry is installed, you
must set the InService attribute to yes.
Destination:
console.msg
transId was unsuccessful because the
local SYSID for this region is null
Explanation:
The LocalSysId attribute of your CICS regions Region
Definition (RD) entry is null (). Therefore CICS is
unable to continue with the current intersystem request
issued by transaction transId.
System action:
The intersystem request fails. Further error messages
can be logged.
User response:
Set the LocalSysId attribute of the RD entry to a 1-4
character local SYSID. This name must be different
from the name (SYSID) of all Communication Definition
(CD) entries used by the transactions in your region.
Once the LocalSysId attribute of the RD entry is
configured restart your region so that the new value can
take effect.
Destination:
console.msg
ERZ030026W
CD entry sysId has the

RemoteLUName attribute set to the
local region name LUname
Explanation:
The Communications Definition (CD) entry sysId has the
RemoteLUName attribute set to one or the following
local names:
v The local Logical Unit (LU) name for the region. This
is configured in the LocalLUName attribute of the
local Region Definition (RD).
v The local region name. This is the regions APPLID.
v The LU name used by a PPC gateway. This is
configured in the GatewayLUName attribute of a
Gateway Definition (GD) entry.
v The LU name used for CICS family TCP/IP which is
derived from the TCP/IP address and port number
defined by the TCPAddress and TCPService
attributes of a Listener Definition (LD) entry.
If this CD entry is used by an intersystem request, the
request will be routed back to the local region by the
network.
System action:
User response:
201
ERZ030027E ERZ030030E
If this CD entry is supposed to be defined to route
requests back to the local region, no action is required.
If, however, this CD entry is required to contact a
remote system, modify the CD entry so that the
RemoteLUName attribute is set to the name of the
remote system. Then ensure that this updated CD entry
is installed in your region.
Destination:
console.msg
ERZ030029E Program programName is defined as
remote

Guide describes how to configure CD entries. It also
describes how to alter existing CD entries in your CICS
region.
Explanation:
CICS is unable to execute the CICS-supplied program
programName because the RemoteSysId attribute of
its Program Definition (PD) entry is not and this
CICS-supplied program is not allowed to be defined as
running on a remote system.
Destination:
console.msg
System action:

transId was unsuccessful because CD
entry sysId does not exist
User response:
Modify the PD entry programName so that
RemoteSysId= and install the updated PD entry in
your region. Then resubmit the transaction.
Explanation:
An intersystem request was unsuccessful because the
Communications Definition (CD) entry sysId associated
with the request is no longer installed in your region.
The CD entry was possibly deleted by the CICS
command cicsdelete or it was possibly uninstalled by
the CCIN transaction either at the request of the remote
system, or because the connection to the remote
system has failed.
System action:
logged.
User response:
Look at the CSMT, CCIN and console.msg logs for
additional messages that indicate how the CD entry was
removed. If the CD entry was deleted using the
cicsdelete command, determine why someone has
removed the CD entry. If the CD entry must still be
defined in your region, use the cicsadd to recreate it
before rerunning transaction transId. If the CD entry was
deleted by CCIN, reconnect the remote system so a
new CD entry is installed in your region, and rerun
Destination:
CSMT or console.msg
ERZ030028E A PD entry for program
programName does not exist
Explanation:
CICS is unable to execute the CICS-supplied program
programName because the Program Definition (PD)
entry for this program is not installed in the region.
System action:
User response:
Install an appropriate PD entry for the program and
202
Destination:
console.msg
ERZ030030E Intersystem request received from
unknown system systemName. The LU
name and network name of this system
are LUname and networkName
respectively
Explanation:
CICS has received an intersystem request from system
systemName. The Logical Unit (LU) name of this
system is LUname and the network name of this system
is networkName. The intersystem request has failed
because CICS does not have a Communications
Definition (CD) entry with the RemoteLUName attribute
set to LUname and, if networkName is not blank, the
RemoteNetworkName attribute set to networkName.
CICS requires a CD entry for the remote system when it
receives an intersystem request in order to perform
proper security checking and data conversion.
System action:
CICS abnormally terminates the intersystem request.
User response:
Determine whether your CICS region is supposed to
accept intersystem requests from this remote system. If
not contact the owner of the remote system to find out
why the remote system is sending requests to your
region. If the remote system is permitted to send
requests to your CICS region create and install a CD
entry for this remote system. The TXSeries for
Multiplatforms Intercommunication Guide describes how
to configure CD entries. It also describes how to alter
existing CD entries in your CICS region.
Destination:
console.msg
ERZ030031E ERZ030034E
ERZ030031E The attributeName attribute in
entryType entry entryName is null
Explanation:
The required attribute attributeName in entryType entry
entryName is null. Intersystems requests using this
entry can fail.
System action:
User response:
Delete the invalid entry from your region and re-install it
with correct attributes. The TXSeries for Multiplatforms
Intercommunication Guide describes how to configure
entryType entries. It also describes how to alter existing
entryType entries in your CICS region.
Destination:
console.msg
ERZ030032E
The attributeName attribute

attributeValue in entryType entry
entryName contains unsupported
characters
Explanation:
The attributeName attribute in entryType entry
entryName contains characters that are not supported
by the Systems Network Architecture (SNA). This field
must be no more than eight characters long. The first
character of this field must be an upper case alphabetic
character (A-Z) and the subsequent characters must be
either upper case alphabetic characters or numeric
(0-9). For example, the following values are valid for the
attributeName attribute:
v A
v CICS1
v OPENCICS
v MYNET
and the following values are invalid.
9
1CICS
console.msg
ERZ030033W The GD entry GDname referenced
by CD entry sysId does not exist
Explanation:
Communications Definition (CD) entry sysId references
the Gateway Definition (GD) entry GDname in the
GatewayName attribute. However, the GD entry
GDname does not exist. CICS requires the GD entry to
contact the PPC gateway and to authenticate requests
from the PPC gateway.
System action:
Intersystem requests that use CD entry sysId will fail.
User response:
Examine the CD entry sysId. If a PPC gateway is not
required to contact the remote system defined in CD
entry sysId set the GatewayName attribute to and
ConnectionType=local_sna. If a PPC gateway is
required to contact the remote system:
v Determine the name of the PPC gateway to be used.
v View each of the GD entries defined in your region to
determine whether your region has a GD entry for
this PPC gateway.
v If there is a GD entry for the PPC Gateway check it
has been installed into the region. (Is the
ActivateOnStartup attribute set to Yes?)
v If a GD entry for the PPC gateway does exist in your
region, modify the GatewayName attribute for the CD
entry sysId to be the name of the GD entry for the
PPC gateway.
v If a GD entry does not exist in your region create a
GD entry called GDname.
Ensure all updated CD and GD entries are installed in
your region. The TXSeries for Multiplatforms
Intercommunication Guide describes the GD and CD
entries required for SNA communications. It also
describes how to alter existing entries in your CICS
region.
Destination:
console.msg

OPENcics
Contains lower case alphabetic characters
MY-NET
Contains an unsupported character

transId was unsuccessful because it
used the local SYSID sysId
System action:
Explanation:
CICS is unable to continue with the intersystem request
for transaction transId because either:
User response:
Delete the entryName entry from your region and
re-install it with correct attributes. The TXSeries for
to alter these entries and install them in your region.
v Transaction transId issued an intersystem request

which specified a SYSID of sysId. This is the local
SYSID that is configured in the LocalSysId attribute
of your regions Region Definition (RD) entry. Using
the local SYSID on this type of intersystem request is
not supported.
Destination:
203
ERZ030035E ERZ030037E
v A remote system using a Logical Unit (LU) name (or
APPLID) of (8 spaces) has made an intersystem
request to your region.
System action:
User response:
Examine transaction transId.
v If it is issuing an intersystem request using SYSID
sysId, modify either the SYSID used on the
intersystem request, or the LocalSysId attribute of
your regions RD entry, so that the transaction
requests a SYSID which is both different from the
local SYSID and is the the name of a
Communications Definition (CD) entry that identifies
the required remote system. The TXSeries for
Multiplatforms Intercommunication Guide describes
how to configure CD entries. It also describes how
alter existing entries in your CICS region database.
v If transaction transId has been started by a remote
system called then alter the name of the remote
system.
Once all necessary updates have been made to your
region and the remote system then rerun the request.
Destination:
CSMT
ERZ030035E
Intersystem request received from

SNA system systemName was
unsuccessful because CD entry sysId
is not configured for this type of
connection.
ERZ030036E
Intersystem request received via PPC

from system systemName was
unsuccessful because CD entry sysId
is not configured for this type of
connection.
Explanation:
CICS is unable to accept an intersystem request from
remote system systemName because the
Communication Definition (CD) entry sysId is not
configured correctly. The intersystem request was either
received from a remote region using TCP or it was
received from a PPC gateway. This means that CD
entry sysId must either be configured so that
ConnectionType=ppc_tcp or it must be configured so
that ConnectionType=ppc_gateway and GatewayName
is set to the name of a Gateway Definition (GD) entry.
System action:
logged.
User response:
Either add a new CD entry or alter CD entry sysId so
your CICS region is configured with a CD entry for
remote system systemName that has the correct
attributes for the connection it is using. Ensure this CD
entry is installed in your region. Then rerun the
intersystem request.
Guide describes how to create and install CD entries in
your CICS region.
Destination:
console.msg
Explanation:
CICS is unable to accept a local SNA intersystem
request from remote system systemName because the
Communication Definition (CD) entry sysId is not
configured with ConnectionType=local_sna.
ERZ030037E
System action:
logged.
Explanation:
CICS is unable to accept a request from system
systemName because the Communications Definition
(CD) entry, sysId, is not configured with
ConnectionType=cics_tcp.
User response:
remote system systemName which has
ConnectionType=local_sna. Ensure this CD entry is
installed in your region. Then rerun the intersystem
request.
Guide describes how to create and install local SNA CD
Destination:
console.msg
204
Intersystem request received via

CICS TCP/IP from system systemName
was unsuccessful because CD entry
sysId is not configured for this type of
connection.
System action:
User response:
remote system systemName that has the correct
attributes for the connection it is using. Ensure this CD
entry is installed in your region. Then rerun the
intersystem request.
ERZ030044E ERZ030048E
Guide describes how to create and install CD entries in
your CICS region.
Destination:
console.msg
ERZ030044E The PPC code errorCode, indicating
the amount of data received from a
remote system was unexpected
Explanation:
During a receive from a remote system, the PPC code
indicating the amount of PPC data received errorCode
was not recognized by CICS. A complete list of possible
codes can be found in file prodDir/include/ppc/ppc.h
under the type ppc_whatDataReceived_t.
System action:
User response:
Ensure that the versions of software used by your CICS
region are compatible. Also check that the software
running on the remote system is compatible with your
local CICS region. If the remote system is connected to
your CICS region via a PPC Gateway and a Systems
Network Architecture (SNA) network check that the
version of the PPC gateway is compatible with the
versions of CICS used by your local region. If you find
that the software used by the communicating systems is
incompatible install the correct versions. Try the
transaction again. If the problem persists, contact your
Destination:
CSMT
ERZ030046E The communications function
functionName failed with
Explanation:
Communications error primaryCode/secondaryCode was
received from the internal CICS function call to
functionName.
System action:
User response:
incompatible install the correct versions. The TXSeries
for Multiplatforms Intercommunication Guide provides
information about the communications error codes
functionName/primaryCode. Try the transaction again. If

the problem persists, contact your support organization.
Destination:
console.msg or CSMT
ERZ030047W Unexpected communications error
Explanation:
CICS detected an unexpected communications error
during the freeing of a conversation.
System action:
User response:
primaryCode/secondaryCode. Try the transaction again.
organization.
Destination:
CSMT
ERZ030048E Unexpected communications error
Explanation:
CICS detected an unexpected communications error.
System action:
User response:
primaryCode/secondaryCode. Try the transaction again.
organization.
Destination:
CSMT
205
ERZ030049E ERZ030054E
ERZ030049E Unexpected Data Flow Control (DFC)
indicator errorCode during receive
Explanation:
An unexpected Data Flow Control (DFC) indicator
errorCode was received from a remote system during a
receive.
System action:
User response:
incompatible install the correct versions. Try the
transaction again. If the problem persists, contact your
Destination:
CSMT
ERZ030051W Unable to validate the password
received with userid userId from
system sysId. Using the region default
userid defaultUserId instead
Explanation:
A request was received from the remote system defined
in Communications Definition (CD) entry sysId.
However, the userid and password sent with the request
was not able to be validated. This can possibly be
because the userid is not defined to the region or
because the password is incorrect for the userid.
System action:
CICS assigns userid defaultUserId, which is defined in
the DefaultUserId attribute of the Region Definition (RD)
entry, to the request. If defaultUserId is authorized to
execute the request, the request continues. Otherwise,
the request will fail with a security violation.
User response:
Verify that the userid, userId is defined to the region in
the User Definitions (UD) and the password associated
with the userid is correct.
Destination:
CSMT
ERZ030053I Using a default local code page of
localCodePage which has a CICS
shortcode of shortCode
Explanation:
CICS is running with a default local code page of
localCodePage.
206
A code page identifies the hexadecimal codes used to

represent characters. For example, the letter A is
represented by 0x41 in the ASCII code page,
ISO8859-1, and as 0xC1 in the EBCDIC code page,
IBM-037. The regions local code page defines how
characters are represented locally. A transaction running
in the region will use the default local code page,
localCodePage, unless it was started by a cicsterm or
cicsteld terminal. Transactions started by these
terminals use the code page associated with the
terminals locale as the local code page.
Code page information is important when CICS is
communicating with remote systems as it affects data
conversion. Data conversion can possibly be required if
a remote system is using a different code page from the
local region. Refer to the TXSeries for Multiplatforms
Intercommunication Guide for information about CICS
data conversion.
CICS extracts the default local code page,
localCodePage, from the operating system. Its value is
derived from the locale setting of the local machine.
Refer to the operating system documentation for
information about the locales and code pages available
on your machine.
Code page localCodePage is equivalent to the CICS
Family shortcode, shortCode. Shortcodes are used to
specify code pages in the DFHCNV macros They are also
used to send code page information between CICS
systems. Refer to the TXSeries for Multiplatforms
Intercommunication Guide for more information about
shortcodes.
System action:
User response:
None
Destination:
console.msg
ERZ030054E
The LD entry LDname referenced by

CD entry sysId does not exist
Explanation:
An intersystems request was unsuccessful because the
Transmission Control Protocol/Internet Protocol
(TCP/IP) Communications Definition (CD) entry sysId
references the Listener Definition (LD) entry LDname in
the ListenerName attribute. However, the LD entry
LDname does not exist. CICS requires the LD entry to
contact the remote system.
System action:
The current intersystem request fails.
User response:
Examine the LD entries defined in your region.
ERZ030055E ERZ030058W
If LD entry LDname is defined, ensure
ActivateOnStartup=yes and the entry is defined in both
the permanent and runtime database. Then restart your
region as LD entries are only activated at region startup.
Messages will appear in the console.msg log during
startup which indicate that a listener process is being
started for the LD entry.
If LD entry LDname is not defined, but another suitable
LD entry with Protocol=TCP is defined, alter CD entry
sysId so the ListenerName points to this LD entry.
If no suitable LD entry is defined in your region, add an
LD entry called LDname and restart your region.
Guide describes how to configure CD and LD entries.
Destination:
console.msg
ERZ030055E
GD entry GDentry is using the same

local LU name, LUname, as GD entry
matchingGDentry
Explanation:
Gateway Definition (GD) entry GDentry is configured to
use the same SNA local Logical Unit (LU) name as GD
entry matchingGDentry. This meant an intersystem
request using GD entry GDentry was unsuccessful
because your SNA product only allows one operating
system process to use a particular local LU name.
ERZ030056W No SNA LD entry defined for CD

entry sysId
Explanation:
ConnectionType=local_sna which means the connection
must use the CICS local SNA support. However,
intersystem requests that use this CD entry will fail
because a Listener Definition (LD) entry with
Protocol=SNA is not defined in the region.
System action:
User response:
Add a LD entry with Protocol=SNA to your region
database and restart your region to activate this new
entry. The TXSeries for Multiplatforms
Intercommunication Guide describes how to add LD
entries.
Destination:
console.msg
ERZ030057W Ignoring attributeName attribute
attributeValue in CD entry sysId as the
ConnectionType is connectionType
The local LU name is configured in the

GatewayLUName attribute of the GD entry. The
describes the local LU names required by your region.
Explanation:
ConnectionType set to connectionType. This type of
connection expects attribute attributeName to be set to
blank (). However, in this CD entry, attribute
attributeName is set to attributeValue. This condition
does not make the CD entry unusable. A warning
message has been produced as this can possibly
indicate that the ConnectionType attribute is incorrectly
set.
System action:
System action:
User response:
Alter your region configuration so that each GD entry is
configured with a different LU name.
User response:
Examine all of the attribute settings in this CD entry and
correct them so they are consistent with the
ConnectionType. The TXSeries for Multiplatforms
CD entries. It also describes how to update CD entries.
If you change the LU name configured in a GD entry, or

if you remove a GD entry, make sure the configuration
for the original local LU name has been removed from
the PPC gateway server by either:
Destination:
console.msg
v using the ppcadmin delete luentry command or

v stopping and cold starting the PPC gateway server or
v stopping and destroying the PPC gateway server.
ERZ030058W The attributeName attribute in

entryType entry entryName is null
In addition, if you remove a GD entry, make sure there

are no Communications Definitions (CD) entries
referencing the GD entry in the GatewayName attribute.
Explanation:
The attribute attributeName in entryType entry
entryName is null. Intersystems requests using this
entry can fail.

Guide has more information on using PPC gateways.
System action:
Destination:
console.msg
User response:
207
ERZ030059E ERZ030062I
Check that the attribute is not required by any of the
intersystem requests that use the entry. If the attribute is
required, delete the invalid entry from your region and
re-install it with correct attributes. The TXSeries for
to configure entryType entries. It also describes how to
update entryType entries in your region.
Destination:
console.msg
ERZ030059E
or
v Set attribute GatewayLUName in GD entry GDentry
to the name of this new local LU name.
v Set Region Definition (RD) attribute LocalLUName to
LUname.
v Remove the configuration for local LU LUname from
using the ppcadmin delete luentry command or
GD entry GDentry is using the same

local LU name, LUname, as the local
SNA support
Explanation:
The PPC gateway defined in Gateway Definition (GD)
entry GDentry is configured to use the same SNA local
Logical Unit (LU) name as the regions local SNA
support. This will not work as your SNA product only
allows one process to use a particular local LU.
System action:
CICS continues processing. However, configuring this
PPC gateway can fail. In addition, inbound intersystem
requests through this PPC gateway or through local
SNA can fail.
User response:
Determine whether your region is supposed to use both
local SNA and a PPC gateway.
If local SNA is not required:
stopping and cold starting the PPC gateway

server.
Guide has more information on using PPC gateways
and local SNA.
Destination:
console.msg
ERZ030060I PPC gateway configuration has started
Explanation:
Information about the region is being passed to each of
the PPC gateways defined in the Gateway Definitions
(GD).
System action:
CICS passes information about the region to each PPC
gateway that is configured in the GD. Once CICS has
configured all the PPC gateways it writes message
ERZ3061I.
v Shutdown your region.
User response:
None
v Remove the Listener Definition (LD) entry which has

Protocol=SNA.
Destination:
console.msg
v Restart your region.

If the PPC gateway is not required:
v Remove the GD entry GDentry from your region.
v Remove the configuration for local LU LUname from
using the ppcadmin delete luentry command or
stopping and cold starting the PPC gateway
server or
stopping and destroying the PPC gateway server.
If both local SNA and the PPC gateway are required:
v Define another local LU in your SNA product.
v Set up each form of communication to use a different
local LU. Either:
Shutdown your region.
Set Region Definition (RD) attribute LocalLUName
to the name of this new local LU name.
Set attribute GatewayLUName in GD entry
GDentry to LUname.
Restart your region.
208
ERZ030061I PPC gateway configuration has ended

Explanation:
CICS has completed configuring the PPC gateways that
are defined in the Gateway Definitions (GD). This
message is written whether the configuration is
successful or not.
System action:
User response:
None
Destination:
console.msg
ERZ030062I Configuring PPC gateway GDname
with details of the region
Explanation:
Information about the region is being passed to the PPC
gateway described in Gateway Definition (GD) entry
GDname. This information will be used by the PPC
gateway to pass intersystem requests from remote SNA
system to the region.
ERZ030063I ERZ030066I
System action:
CICS passes:
System action:
v the SNA Logical Unit (LU) name configured in the

LocalLUName attribute of the Region Definition (RD)
and
User response:
None
to the PPC gateway described in the GD entry

GDname.
Destination:
console.msg
User response:
None
ERZ030065I Configuring PPC gateways with

transaction transId has started
Destination:
console.msg
Explanation:
A new Transaction Definition (TD) entry for transaction
transId has been installed in the CICS region. This TD
entry has the name of an IBM Communications Server
for AIX LU6.2 Transaction Program Name profile in the
TPNSNAProfile attribute. CICS will therefore attempt to
contact all PPC gateways defined in the Gateway
Definitions (GD) to inform them of this new CICS
transaction.

with details of local transactions
Explanation:
The identifiers of transactions that have an IBM
Communications Server for AIX LU6.2 Transaction
Program Name profile specified in the Transaction
Definition (TD) attribute TPNSNAProfile are being
passed to the PPC gateway described by Gateway
Definition (GD) entry GDname.
CICS transaction identifiers are only used by the AIX
PPC gateway. They are required to receive inbound
intersystem requests from remote SNA systems using
IBM Communications Server for AIX. If the PPC
gateway is not an AIX PPC gateway, CICS will stop
passing transaction identifiers after the first call to the
PPC gateway.
This message is written whether there are any TD
entries that have TPNSNAProfile set to a profile name
or not.
System action:
CICS examines each TD entry in the region database. If
the TPNSNAProfile attribute is set to the name of an
IBM Communications Server for AIX LU6.2 Transaction
Program Name profile (rather than ) the name of this
profile and the transaction identifier is passed to the
PPC gateway defined in the GD entry GDname. This
process stops after the first call to the PPC gateway if
the PPC gateway informs CICS that it is not an AIX
PPC gateway.
User response:
None
Destination:
console.msg
has ended
Explanation:
CICS has finished configuring the PPC gateway that is
defined by Gateway Definition (GD) entry GDname.
This message is written whether the configuration is
successful or not.
System action:
CICS passes the transaction identifier and the name of
the AIX SNA Server/6000 LU6.2 Transaction Program
Name profile to each PPC gateway defined in the
Gateway Definitions (GD). If the PPC gateway is an AIX
PPC gateway, it will inform IBM Communications Server
for AIX that it wishes to receive requests for the
transaction identifier. If the PPC gateway is not AIX it
will do nothing as only IBM Communications Server for
AIX requires configuration information about CICS
transactions.
Once CICS has configured all the PPC gateways
defined in the GD it displays message ERZ3067I.
User response:
None
Destination:
console.msg
with transaction transId
Explanation:
TPNSNAProfile attribute. CICS is about to pass the IBM
Communications Server for AIX LU6.2 Transaction
Program Name profile name and the transaction
identifier transId to the PPC gateway defined in the
Gateway Definition (GD) entry GDname.
System action:
CICS passes the transaction identifier and the name of
the IBM Communications Server for AIX LU6.2
Transaction Program Name profile to the PPC gateway
defined in the Gateway Definition (GD) entry GDname.
If the PPC gateway is an AIX PPC gateway, it will
inform IBM Communications Server for AIX that it
209
ERZ030067I ERZ030071E
wishes to receive requests for the transaction identifier.
If the PPC gateway is not AIX it will do nothing as only
IBM Communications Server for AIX requires
configuration information about CICS transactions.
User response:
None
Destination:
console.msg
ERZ030067I Configuring PPC gateways with
transaction transId has ended
Explanation:
CICS has completed configuring the PPC gateways that
are defined in the Gateway Definitions (GD) with details
of transaction transId. This message is displayed
whether the configuration is successful or not.
System action:
User response:
None
Destination:
console.msg
ERZ030068I Deleting transaction transId from PPC
gateways has started
Explanation:
A Transaction Definition (TD) entry for CICS transaction
transId has been deleted from the CICS region. This
TD entry had the name of an IBM Communications
Server for AIX LU6.2 Transaction Program Name profile
in the TPNSNAProfile attribute. CICS will therefore
attempt to contact all PPC gateways defined in the
Gateway Definitions (GD) to inform them that this CICS
transaction has been deleted.
System action:
CICS passes the transaction identifier transId to each
PPC gateway defined in the Gateway Definitions (GD).
If the PPC gateway is an AIX PPC gateway, it will
inform IBM Communications Server for AIX that it no
longer wishes to receive requests for the transaction
identifier. If the PPC gateway is not AIX it will do nothing
as only IBM Communications Server for AIX requires
configuration information about CICS transactions.
Once CICS has contacted all the PPC gateways
defined in the Gateway Definitions (GD) it displays
message ERZ3070I.
User response:
None
Destination:
console.msg

gateway GDname
Explanation:
A Transaction Definition (TD) entry for transaction
TPNSNAProfile attribute. CICS is about to pass transId
to the PPC gateway defined in the Gateway Definition
(GD) entry GDname.
System action:
CICS passes the transaction identifier to the PPC
gateway defined in the Gateway Definition (GD) entry
transId. If the PPC gateway is an AIX PPC gateway, it
will inform AIX SNA Server/6000 that it no longer wishes
to receive requests for the transaction identifier. If the
PPC gateway is not an AIX PPC gateway it will do
nothing as only IBM Communications Server for AIX
requires configuration information about CICS
transactions.
User response:
None
Destination:
console.msg
gateways has ended
Explanation:
CICS has finished deleting transaction transId from all
the PPC gateways defined in the Gateway Definitions
(GD). This message is displayed whether the deletion is
successful or not.
System action:
User response:
None
Destination:
console.msg
ERZ030071E Unable to contact PPC gateway
GDname registered at CDSname
Explanation:
CICS issued a configuration call to the PPC gateway
defined in Gateway Definition (GD) entry GDname.
However, the PPC gateway did not respond. Possible
reasons include:
v The PPC gateway is not running.
v The PPC gateway is running but is not listening for
requests. (For example, the PPC gateway is shutting
down.)
System action:
210
ERZ030072E ERZ030074E
CICS stops configuring this PPC gateway. Some or all
SNA intersystem requests that are supposed to use this
PPC gateway can fail until CICS successfully completes
this configuration.
User response:
v Check that the PPC gateway is running. The ps -ef |
grep ppcgwy command will display all the PPC
gateways running on a particular machine. If
necessary start the PPC gateway.
v If the PPC gateway was running, check the PPC
gateways message log for error or shutdown
messages. If you find error messages you do not
expect, investigate the causes of these errors. If you
find that the PPC gateway is shutting down, wait for
the shutdown to complete and restart the PPC
gateway.
Once you have ensured the GD entry is correct and the
PPC gateway is running, retry the PPC gateway
configuration either by:
v restarting your CICS region or
v running the CGWY transaction (see the TXSeries for
Multiplatforms Intercommunication Guide).
Destination:
console.msg
ERZ030072E
Unauthorized to contact PPC

gateway GDname registered at
CDSname
Explanation:
CICS issued a configuration request to the PPC
gateway defined in Gateway Definition (GD) entry
GDname. However, the PPC gateway rejected this
request as your CICS region does not have the correct
permissions to use this PPC gateway.
System action:
SNA intersystem requests through this PPC gateway
will fail until CICS completes this configuration.
User response:
Check that the PPC gateway defined in GD entry
GDname is the correct PPC gateway for your region.
Modify the GD entry if it does not contain the correct
values.
Once you are sure that your region now has access to
the PPC gateway, either restart your region or run the
CGWY transaction so that your region configures the
PPC gateway.
Destination:
console.msg
ERZ030073E
PPC gateway GDname registered at

CDSname does not recognize
configuration calls
Explanation:
However, the PPC gateway does not recognize the
configuration call and so returned an error code.
Possible reasons include:
v The PPC gateway was in the process of initializing or
shutting down when CICS made the configuration
call.
v The PPC gateway is running with a level of software
that is incompatible with the software being used by
your CICS region.
System action:
will fail until CICS successfully configures it.
User response:
GDname is the correct PPC gateway for your region. If
required, modify the GD entry so that it specifies the
correct PPC gateway.
Check that the software level of the PPC gateway is
compatible with your CICS region. If it is not, install the
correct levels of software.
Once you are sure that your region is configured to use
a PPC gateway running at the correct level of software
either restart your region or run the CGWY transaction
to configure the PPC gateway.
Guide explains how to set up and run your PPC
gateway. It also describes how to use the CGWY
transaction. If you need further help in solving this
Destination:
console.msg
ERZ030074E
Unable to configure PPC gateway

GDname registered at CDSname.
PPC status code is errorString
(errorCode)
Explanation:
However, the PPC gateway was unable to perform the
request and returned an error code errorCode. This
error code has a description of errorString. The
errorString indicates where the error occurred.
System action:
211
ERZ030075E ERZ030076E
will fail until CICS successfully configures it.
User response:
Use the value of errorString as a guide and check that
v the PPC gateway defined in GD entry GDname is the
correct PPC gateway for your region. If required,
modify the GD entry so that it specifies the correct
PPC gateway.
v your SNA product is running
v your PPC gateway is correctly set up and running
v the software level of the PPC gateway is compatible
with your CICS region. If it is not, install the correct
levels of software.
In addition, check the PPC gateways message file as
the PPC gateway possibly logged an error message.
PPC gateway messages and their meaning are
described in the TXSeries for Multiplatforms
Once you have corrected the problem, either restart
your region, or run the CGWY transaction to configure
the PPC gateway.
gateway. It also describes how to use the CGWY
transaction. If you need further help in solving this
Destination:
console.msg
ERZ030075E
Unable to configure transaction(s)

transIdList using a TPNSNAProfile of
SNAprofile in PPC gateway GDname
registered at CDSname
Explanation:
defined in Gateway Definition (GD) entry GDname. This
call passed information about your regions transactions
to the PPC gateway to enable the PPC gateway to
receive requests for these transactions from remote
System Network Architecture (SNA) systems. However,
the PPC gateway was unable to register the
transactions transIdList with IBM Communications
Server for AIX for one of the following reasons.
v IBM Communications Server for AIX is not running.
v The profile SNAprofile has the characters DEFAULT in
its name.
v The profile SNAprofile is not correctly defined in IBM
Communications Server for AIX.
v The GatewayLUName attribute of the GD entry
GDname is and there is a Listener Definition (LD)
entry with the Protocol attribute set to SNA installed
in your region.
212
v There is another process, such as a PPC gateway,

which is registered with IBM Communications Server
for AIX and is using the local SNA Logical Unit (LU)
name defined in the GatewayLUName attribute of the
GD entry GDname. (If GatewayLUName=, it
defaults to the LU name configured in the
LocalLUName attribute of your regions Region
Definition (RD)).
System action:
CICS processing continues. Inbound intersystem
requests for these transactions from remote SNA
systems can fail.
User response:
Check that IBM Communications Server for AIX is
running. If it is not, restart it. The PPC gateway is
supposed to register with IBM Communications Server
for AIX automatically. If this does not occur and
requests for transactions listed in transIdList from
remote SNA systems fail either restart your region or
run the CGWY transaction to configure the PPC
gateway.
Check that the profile SNAprofile is correctly defined to
IBM Communications Server for AIX. Issue the verifysna
-R command to ensure that this profile is copies into
IBM Communications Server for AIXs runtime database.
Check that there is only one copy of the PPC gateway
named in GD entry GDname running. The command ps
-ef | grep ppcgwy will list all the PPC gateways running
on a particular machine. Look for instances of the PPC
gateway that are using the name defined in the
GatewayCDSName attribute of GD entry GDname. If
more than one copy of this PPC gateway is running,
use the AIX command kill -9 to stop all of these PPC
gateways and, restart a new copy of the PPC gateway.
Once the PPC gateway has started, either restart your
CICS region or run the CGWY transaction to configure
the PPC gateway.
gateway. It also describes how to configure IBM
Communications Server for AIX profiles.
Destination:
console.msg
ERZ030076E
Unable to configure transaction(s)

transIdList using a TPNSNAProfile of
SNAprofile at PPC gateway GDname
(CDSname). PPC status code is
errorString (errorCode)
Explanation:
defined in Communications Definition (CD) entry
GDname with information about CICS transactions
ERZ030077I ERZ030080E
transIdList. However, this call failed with error code
errorCode. The message text associated with this error
code is errorString.
System action:
CICS continues processing. Inbound intersystem
systems can possibly fail.
User response:
transIdList is the correct PPC gateway for your region.
Modify the GD entry if it does not contain the correct
values.
Check that the software level of the PPC gateway is
compatible with your CICS region. If it is not, install the
correct levels of software and restart both the PPC
gateway and the CICS region.
If the PPC gateway is at the correct software level it is
possible that the PPC gateway was either not set up
correctly or not running when CICS issued the
configuration call. Ensure that the PPC gateway is
running correctly and restart your CICS region to
re-drive the PPC gateway configuration.
When you have solved the problem either restart you
CICS region or run the CGWY transaction to configure
the PPC gateway. The TXSeries for Multiplatforms
Intercommunication Guide explains how to set up and
run your PPC gateway. It also describes how to run the
CGWY transaction.
Destination:
console.msg
ERZ030077I Deleting details of local region from
PPC gateway GDname has started
Explanation:
The Gateway Definition (GD) entry GDname has been
deleted from the region database. CICS has started
removing details of your region from this PPC gateway
so that the PPC gateway will no longer send
intersystem requests to your region.
System action:
CICS makes a configuration call to the PPC gateway
that was defined in GD entry GDname.
User response:
None
Destination:
console.msg
ERZ030078I Deleting details of local region from
PPC gateway GDname has ended
Explanation:
CICS has finished removing details of your region from
the PPC gateway defined in Gateway Definition (GD)
entry GDname. This message is displayed whether the

deletion is successfully or not.
System action:
User response:
None
Destination:
console.msg
ERZ030079E Unable to delete transaction(s)
transIdList from PPC gateway
GDname
Explanation:
request. Details of the transactions listed in transIdList
can remain configured in the PPC gateway until your
region reconfigures the PPC gateway (either when your
region is restarted or the CGWY transaction is run).
This does not affect intersystems communication. If,
however, you add a TD entry for any of the transactions
listed in transIdList before the PPC gateway is
reconfigured the resulting configuration calls made to
the PPC gateway can fail.
System action:
User response:
This error does not affect the operation of your region
and PPC gateway. Action is only required if you are to
add a TD entry for any of the transactions listed in
transIdList, in which case run the CGWY transaction to
reconfigure the PPC gateway. If this fails refer to the
messages produced by CGWY.
Destination:
console.msg
ERZ030080E
Unable to delete transaction(s)

transIdList from PPC gateway
GDname. PPC status code is
errorString (errorCode)
Explanation:
request and returned an error code errorCode. This
error code has a description of errorString. The
errorString indicates where the error occurred.
Details of the transactions listed in transIdList can
remain configured in the PPC gateway until your region
reconfigures the PPC gateway (either when your region
is restarted or the CGWY transaction is run). This does
not affect intersystems communication. If, however, you
213
ERZ030081E ERZ030092E
transIdList before the PPC gateway is reconfigured the
resulting configuration calls made to the PPC gateway
can fail.
System action:
User response:
This error does not affect the operation of your region
and PPC gateway. Action is only required if you are to
transIdList in which case run the CGWY transaction to
reconfigure the PPC gateway. If this fails refer to the
messages produced by CGWY.
Destination:
console.msg
ERZ030081E Unable to configure PPC gateways
Explanation:
CICS is unable to configure the PPC gateways defined
in the Gateway Definitions (GD) because the CGWY
transaction will not start.

RemoteTCPAddress set to hostName. This host name
maps to more than one TCP/IP network adapter
address. CICS will use the first network adapter address
extracted as the address of the remote system. This is
address.
System action:
User response:
Examine address address. If this is the correct network
address for the remote system then no further action is
required. If this address is not the correct address for
the remote system then alter CD entry sysId so that
RemoteTCPAddress is set to the correct address. The
describes how to configure CD entries for CICS family
TCP/IP. It also describes how to alter CD entries in your
region.
Destination:
console.msg
System action:
ERZ030091E Unable to resolve RemoteTCPAddress

address in CD entry sysId
User response:
Check that there is a Transaction Definition (TD) entry
for the CGWY transaction installed in your region. Make
sure the attributes of this TD entry are as follows:
Explanation:
The TCP/IP name service is unable to convert the value
of address in the RemoteTCPAddress attribute in
Communications Definition (CD) entry sysId into a
TCP/IP network adapter address. This is possibly
because address is specified in an incorrect format, or
address is a host name which is not defined in the
TCP/IP name service.
v ActivateOnStartup = yes
v ProgName =
v RSLKey = private
v TSLKey = 1
v RSLCheck = none
v TSLCheck = internal
v EnableStatus = enabled
v IsBackEndDTP = no
v RemoteSysId =
v RemoteName =
v InvocationMode =
no_facility|any_start|at_normal_running
When the TD entry for CGWY is correct and if your
CICS region is using one or more PPC gateways use
the EXEC CICS START TRANSID(CGWY) command
to retry the CGWY transaction. If the problem persists
Destination:
console.msg
ERZ030090W TCP/IP host name hostName in CD
entry sysId maps to more than one
TCP/IP address, using address
address
Explanation:
214
System action:
CD entry sysId is marked as invalid and is unavailable
for intersystem requests.
User response:
Alter CD sysId so that the RemoteTCPAddress attribute
specifies a correct network adapter address. The
describes how to configure CD entries for CICS family
TCP/IP connections. It also describes how to alter CD
entries in your region.
Destination:
console.msg
ERZ030092E Unable to contact TCP/IP name
service to resolve RemoteTCPAddress
hostName in CD entry sysId
Explanation:
RemoteTCPAddress set to hostName. CICS is unable
to convert this TCP/IP hostname into a TCP/IP network
adapter address because it can not contact the TCP/IP
name server. This is possibly because the name server
is unavailable or the local machine is not correctly
configured to contact the name server.
ERZ030093E ERZ030096E
System action:
CD entry sysId is marked as invalid and is unavailable
for intersystem requests.
ERZ030095E
DTP request issued by transId is not

supported on CICS family TCP/IP
connection sysId
User response:
Using your operating system information, ensure the
TCP/IP name service is available to the local machine.
Delete and then add CD entry sysId to your region so
CICS accesses the TCP/IP name service to extract the
network adapter address. Refer to the TXSeries for
on managing CD entries in your region.
Explanation:
CICS is unable to continue with a Distributed
Transaction Processing (DTP) request for transaction
transId because Communications Definition (CD) entry
sysId is configured with ConnectionType=cics_tcp and
DTP is not supported on CICS family TCP/IP
connections.
Destination:
console.msg
System action:
The intersystem request is unsuccessful. Further
messages can be logged.
ERZ030093E Unable to resolve RemoteTCPAddress

address in CD entry sysId
Explanation:
CICS has detected an internal error which is preventing
it from initializing Communications Definition (CD) entry
sysId.
System action:
CD entry sysId is marked as invalid. Further error
User response:
Examine the console.msg file for messages describing
why CICS can not initialize CD entry sysId. Follow the
Destination:
console.msg
transId was unsuccessful because CD
entry sysId contains incorrect
attributes
Explanation:
CICS is unable to continue with an intersystem request
for transaction transId because the attributes in
Communications Definition (CD) entry sysId are not
correct. CICS has already reported the exact cause of
the problem during region initialization.
System action:
User response:
Examine the console.msg file as this will contain the
messages describing which attributes in CD entry sysId
are not correct. Follow the instructions associated with
these messages and rerun the intersystem request.
Destination:
console.msg
User response:
v If this transaction is issuing an EXEC CICS
ALLOCATE SYSID(sysId) command, alter transaction
transId to specify a CD entry in the SYSID option
which is not configured with
ConnectionType=cics_tcp.
v If transaction transId was started by a transaction
routing request sent from the remote system, alter
the IsBackEndDTP attribute in the Transaction
Definition (TD) entry for transId so
IsBackEndDTP=no.
v If transaction transId was started by a DTP
transaction in remote system sysId, alter the remote
transaction to use a connection which is not CICS
family TCP/IP.
Guide describes the EXEC CICS ALLOCATE command.
It also describes the different types of connections
supported by CICS and how to alter resource definitions
in your region.
Once the necessary changes have been made and the
updated programs and definitions have been installed in
your region, rerun the request.
Destination:
console.msg
ERZ030096E DTP request issued by transId is not
supported on connection to CICS
Client sysId
Explanation:
CICS is unable to continue with a Distributed
Transaction Processing (DTP) request issued by
transaction transId because the remote system
sysId is an CICS client which does not support DTP.
System action:
User response:
215
ERZ030097W ERZ030099E
v If this transaction is issuing an EXEC CICS
ALLOCATE SYSID(sysId) command, alter transaction
transId to specify a CD entry in the SYSID option
which is not configured as a connection to an CICS
client. The TXSeries for Multiplatforms
Intercommunication Guide describes the EXEC CICS
ALLOCATE command.
v If transaction transId was started by a request from
an CICS client terminal, alter the IsBackEndDTP
attribute in the Transaction Definition (TD) entry for
transId so IsBackEndDTP=no. The TXSeries for
how to alter resource definitions in your region.
Once the necessary changes have been made and the
updated programs and definitions have been installed in
your region, rerun the request.
Unable to locate GD entry using

local LU localLUname for remote
system remoteLUname
Explanation:
CICS has received an intersystem request from a
remote system called remoteLUname via a PPC
gateway server. This PPC gateway server is using the
Logical Unit (LU) name localLUname as this regions
local LU name. However, CICS does not have a
Gateway Definitions (GD) entry that is configured with
localLUname as the local LU name.
System action:
User response:
Add a GD entry for your PPC gateway server to your
CICS region, specifying
GatewayLUName=localLUname. The name of this GD
entry must be the same as the value of the
GatewayName attribute of the Communications
Definition (CD) entry for remote system remoteLUname.
Once the resource definitions are correct, rerun the
intersystem request. If you require further information,
see the TXSeries for Multiplatforms Intercommunication
Guide.
Destination:
console.msg
ERZ030098E The LD entry LDname referenced by
CD entry sysId is not configured for
TCP/IP
Explanation:
An intersystem request is using Communications
Definition (CD) entry sysId. This CD entry has
ConnectionType=cics_tcp and ListenerName=LDname.
The ListenerName attribute must therefore be
216
System action:
User response:
cics_tcp, either:
v Alter LD entry LDname so that Protocol=TCP and the
other attributes are correctly configured for CICS
family TCP/IP.
or
v Alter CD entry LDname so that the ListenerName
LD entry.
CICS family TCP/IP support. It also describes how to
install these entries in your CICS region.
Destination:
console.msg
ERZ030097W

LDname does not have Protocol=TCP configured.
Destination:
console.msg
ERZ030099E
Unable to accept an intersystem

request from remote system
remoteLUname because CD entry sysId
is not configured with a GD entry
using local LU localLUname
Explanation:
CICS has received a request from remote system
remoteLUname via a PPC gateway server. However,
the Communications Definition (CD) entry, sysId, for
remote system remoteLUname does not have the
GatewayName attribute set up correctly. Either:
v The GatewayName attribute is null ().
v The GatewayName attribute is not set to the name of
a Gateway Definition (GD) entry.
v The GD entry specified by the GatewayName
attribute is not configured with localLUname as the
local LU name.
System action:
User response:
If CICS appears to be using the wrong CD entry, look at
the CD entry that CICS was supposed to use, as this is
incorrectly configured. Check the
ConnectionType=ppc_gateway and the
RemoteLUName, SNAConnectName and
RemoteNetworkName attributes are correct. Examine
the GatewayName attribute in the CD entry.
v If it is null (), add a GD entry for your PPC Gateway
server to your CICS region, specifying
GatewayLUName=localLUname. Then alter the
ERZ030100E ERZ030101E
GatewayName attribute in CD entry sysId to be the
name of this new GD entry.
v If it is set to the name of a GD entry, ensure this
entry has GatewayLUName=localLUname and this
entry is installed in your region.
Otherwise, if CD entry sysId is the expected CD entry,
examine the GatewayName attribute in the CD entry.
v If it is null (), add a GD entry for your PPC Gateway
server to your CICS region, specifying
GatewayLUName=localLUname. Then alter the
GatewayName attribute in CD entry sysId to be the
name of this new GD entry.
v If it is set to the name of a GD entry, ensure this
entry has GatewayLUName=localLUname and this
entry is installed in your region.
Guide describes how to configure CD and GD entries
for SNA connections that use a PPC Gateway server. It
also describes how to modify CD entries and install GD
Destination:
console.msg
ERZ030101E
Local LU name localLU or Partner

LU name partnerLU used on
intersystem request to system sysId
through gateway GDname is incorrect
Explanation:
An intersystem request was made to the remote system
sysId. This CD entry has ConnectionType=ppc_gateway
and GatewayName=GDname which means the
intersystem request was supposed to be passed to the
PPC gateway server configured in Gateway Definitions
(GD) entry GDname. However, the intersystems request
was unsuccessful because either:
v the local logical unit (LU) name localLU contains
invalid characters, or
v the partner LU name partnerLU contains invalid
characters, or
v the partner LU name partnerLU is longer than eight
characters, or
Rerun the intersystem request once the changes have

been made to the resource definitions.
v the PPC gateway server has not been configured

with information about your CICS region, or
Destination:
console.msg
v there are two copies of your PPC gateway server

running, or
ERZ030100E
Local LU name localLU or Partner

LU name partnerLU used on
intersystem request to system sysId is
incorrect
Explanation:
sysId. However, this request was unsuccessful because
either the local logical unit (LU) name localLU or the
partner LU name partnerLU contains invalid characters.
The partner LU name partnerLU is configured in either
the RemoteLUName or the SNAConnectName attributes
of CD entry sysId.
The local LU name localLU is either the regions name
(APPLID) or it is configured in the LocalLUName
attribute of the Region Definition (RD) entry for your
region.
System action:
User response:
Correct the configuration of CD entry sysId so the local
and partner LU names used are correct.
If you require further information, see the TXSeries for
Multiplatforms Intercommunication Guide.
v the local LU name localLU can not be used by the

PPC gateway server because another operating
system process is already using it. This process can
be a CICS region using local SNA or another PPC
Gateway server.
The partner LU name, partnerLU, is configured in either
the RemoteLUName or the SNAConnectName attribute
of CD entry sysId.
The local LU name, localLU, is configured in the
GatewayLUName attribute of the Gateway Definition
(GD) entry GDname. (If this attribute is it defaults to
the LocalLUName attribute of the Region Definition (RD)
entry for your region.)
System action:
User response:
Check the localLU and partnerLU LU names contain
correct characters. Correct the CICS configuration if
necessary. The TXSeries for Multiplatforms
Intercommunication Guide describes how to alter CD,
GD and RD entries.
If localLU and partnerLU are correct, use the:
$ cicsget -r <regionName> -c gd GDname
command to display GD entry GDname. The
GatewayCDSName attribute will be configured with the
name of the PPC gateway server. The TXSeries for
217
ERZ030102E ERZ030104E
the GatewayCDSName attribute maps to the name of
the PPC gateway server.
Log on to the machine where the PPC gateway server
configured in GD entry GDname is supposed to run.
Use the:
$ ps -ef | grep ppcgwy
command to list the PPC gateway servers running. If
more than one copy of the PPC gateway server
configured in GD entry GDname is running then use the
cicsppcgwyshut command to shut one of them down.
Then shut the other one down using the kill -9
<processId> command where <processId> is the
operating system process identifier (pid) of the PPC
gateway server process. Finally restart your PPC
gateway server.
Check that all the PPC gateway servers running have
the correct CICS regions configured. Use the ppcadmin
list luentries command to display the configuration in
each PPC gateway server. (See the TXSeries for
on this command.) There must be one luentry for each
GD entry. If a PPC gateway server is missing
information about a CICS region then run the CGWY
transaction on that CICS region. The TXSeries for
to do this.
Look at the configuration of all the regions running on
on the same machine as the PPC gateway server. (The
cicslist command will list all of the CICS regions defined
on the machine.) Check the setting of the RD entry
attribute LocalLUName and the GatewayLUName
attributes of all the GD entries configured in these
regions. These local LU name values must be different
from localLU. If they are not, then you need to
rearrange the local LU names used on the machine.
Guide describes the local LU names required by your
region. It also describes how to alter GD and RD
entries.
If there are no errors in the LU names used by your
CICS regions and PPC gateway servers then you must
look for a SNA application that is using local LU name
localLU. It is not possible to share local LU names
between SNA application and a CICS region. So when
you locate this SNA application, change the local LU
name it is using.
Note: If you change the local LU name used by CICS,
a PPC gateway or a SNA application, ensure that
the configuration on all remote SNA systems that
communicate with the local LU name is also
updated. Otherwise these remote SNA systems
will no longer be able to connect to your
region/application.M/note>
218
Destination:
console.msg
ERZ030102E An intersystem request has
abnormally terminated with abend
code abendCode
Explanation:
CICS detected an unexpected condition while
processing an intersystem request. A symptom record
(symrec) has been created and further messages can
be logged. These will provide additional information
about the cause of the problem.
System action:
CICS abnormally terminates the intersystem request
with abend code abendCode.
User response:
abendCode and any additional messages logged by
CICS. If you can not solve the problem yourself, save
the CSMT log, console.msg file and the symrec file and
Destination:
console.msg or CSMT
ERZ030103E entryType entry entryName is
unusable because server-side
transactions are enabled
Explanation:
entryType entry entryName is requesting support for
PPC communications. However, the region is running
with ServerSideTran=yes in the Region Definition (RD)
entry. This attribute enables server-side transactions in
the SFS Server which means the region is unable to
support PPC communications.
System action:
The entryType entry entryName is marked as
unavailable for intersystem requests.
User response:
If you wish the CICS region to support intersystem
requests using PPC communications then restart your
CICS region with ServerSideTran=no. Alternatively,
remove entryType entry entryName from your regions
definitions.
Destination:
console.msg
ERZ030104E
Converting from code page

was unsuccessful
Explanation:
CICS control data for a Intersystem Communication
(ISC) request was not able to be converted between
code page codePage1 and code page codePage2
because:
ERZ030106E ERZ031006E
v there is an error in the conversion routine or
v characters in the data are invalid for code page
codePage1 or
Destination:
console.msg
v characters in the data are not defined in code page

codePage2.
ERZ031003W Invalid transaction identifier transId please resubmit
System action:
Explanation:
The transaction transId is not known on the remote
system.
User response:
Ensure the conversion routines for code pages
codePage1 and codePage2 are correctly installed.
Consult the operating system documentation on iconv
and genxlt for further details.
If you are unable to solve this problem yourself, contact
Destination:
CSMT
ERZ030106E XPRecv TIMEOUT with timeout value
%d and TermID %s
Explanation:
System action:
User response:
Destination:
ERZ031001E The principal facility for CRTE must
be a terminal
Explanation:
The CRTE transaction cannot be started without a
terminal as its principal facility.
System action:
User response:
Ensure that the transaction is being started from a
terminal, and not by another transaction executing ATI
commands that start the transaction.
Destination:
CSMT
System action:
CICS continues.
User response:
Verify that the transaction name you have entered is
correct, and that it is available on the system you are
transaction routing to.
Destination:
The users screen.
ERZ031004I Routing session to system sysId
terminated
Explanation:
CICS has terminated the transaction routing session to
system sysId.
System action:
CICS continues.
User response:
Enter your next transaction. All further transactions are
executed on the local system.
Destination:
The users screen.
ERZ031005E Incorrect syntax - Correct syntax is
CRTE SYSID {=sysId|(sysId)}
Explanation:
You attempted to start the CRTE transaction using an
incorrect syntax.
System action:
CICS terminates the CRTE transaction.
User response:
Re-enter the CRTE transaction using the correct syntax.
ERZ031002E Cannot obtain the National Language

Support (NLS) CANCEL keyword
Destination:
The users screen.
Explanation:
CRTE was not able to retrieve the CANCEL keyword
from the NLS message catalogue for your locale.
ERZ031006E Incorrect syntax - Correct syntax is

TPNxxxxx or CANCEL
System action:
CICS continues.
User response:
Verify that a CICS NLS message catalogue exists for
the locale of your region. As an interim solution, you can
type the word CANCEL in English to terminate the
transaction routing session.
Explanation:
You attempted to run the CRTE transaction using an
incorrect syntax.
System action:
CICS continues.
User response:
219
ERZ031007E ERZ031016W
To start a transaction on the remote system, enter a
valid transaction identifier. To terminate the transaction
routing session to the remote system, enter CANCEL. In
particular, you cannot start transactions by using a PF
key.
Destination:
The users screen.
ERZ031007E Remote system sysId cannot be
found
Explanation:
A Communications Definition (CD) entry for the remote
system sysId was not able to be found.
System action:
User response:
Verify that you have entered the correct system name
when invoking CRTE. Also verify that a Communications
Definition (CD) entry for the system exists.
Destination:
The users screen.
ERZ031008E Routing session terminated because
CICS has lost the connection to
system sysId
Explanation:
The CRTE session cannot continue because CICS has
detected a communications error on the connection to
the remote system.
System action:
User response:
available. Further information on the reason for the error
can be obtained by examining the CICS message logs
and by referring to TXSeries for Multiplatforms
Destination:
The users screen.
ERZ031009I Routing session to system sysId
started
Explanation:
CICS has started the transaction routing session to the
remote system sysId. All further transactions are
executed on the remote system.
System action:
CICS continues.
User response:
Clear the screen and enter the name of the transaction
to be started. To terminate the routing session, clear the
screen and enter CANCEL.
220
Destination:
The users screen.
ERZ031010E System sysId is not available
Explanation:
The transaction cannot be started because the remote
system, or the connection to it, are unavailable.
System action:
User response:
are available. Further information on why the system is
unavailable can be obtained by examining the CICS
message logs and by referring to TXSeries for
Destination:
The users screen.
ERZ031015E Terminal definition is not shippable
Explanation:
A request to ship a terminal definition has been received
from the remote system. The terminal definition cannot
be shipped because its Terminal Definition (WD) entry is
marked as unshippable.
System action:
User response:
Confirm that it is desirable for the local system to ship a
terminal definition for the terminal. If it is, then set the
IsShippable attribute of the WD entry for the terminal to
yes. If it is not desirable to ship terminal definitions from
the local system, consider adding a definition of the
terminal on the remote system. If the remote system is
CICS on Open Systems or CICS for Windows NT,
version 4, this can be achieved by adding a WD entry
for terminal, with the RemoteSysId attribute set to the
name of the local system. Otherwise consult the
appropriate documentation for that system.
Destination:
The users screen.
ERZ031016W The remote transaction has
abnormally terminated
Explanation:
The transaction that you are executing on the remote
system has abnormally terminated.
System action:
CICS continues.
User response:
Use the procedures that are appropriate for the remote
system to determine the reason for the abnormal
termination of the transaction. Further transactions that
you enter continue to be routed to the remote system.
ERZ031017E ERZ032002E
Destination:
The users screen.
ERZ031017E Routing session terminated because
of a transaction routing error
Explanation:
CICS cannot continue execution of the routing session
because of an error while transaction routing.
System action:
User response:
Examine the CICS message logs to obtain additional
information on the reasons for the error.
Destination:
The users screen.
ERZ031018E Unable to route to the local system
sysId
Explanation:
You have specified a remote system that is the same as
the name of the local system.
System action:
User response:
Re-enter CRTE, specifying a remote system for which a
Communications Definition (CD) entry exists.
Destination:
The users screen.
ERZ031019E System sysId is not in service
Explanation:
The system you have specified is not in service.
System action:
User response:
Verify that the system is supposed to be in service, then
set the system back in service by setting the InService
attribute of the Communication Definition (CD) entry for
the system to yes. Then re-submit the CRTE
transaction.
Destination:
The users screen.
ERZ031020W There is a problem communicating
with system sysId
Explanation:
CRTE is not known to the remote system.
System action:
CICS continues.
Verify that communication to the remote system is

correctly configured and that the connection is active.
Destination:
The users screen.
ERZ032001E The CICS-private transaction which
schedules remote transaction initiation
requests was unable to attach to
system sysId because of
Explanation:
The attempt to schedule a remote transaction initiation
request on system sysId was unsuccessful due to
failure to allocate a session to that system.
System action:
The CICS-private transaction is abnormally terminated
on this system. The request to schedule the transaction
is lost. Other processing continues.
User response:
The message indicates the reason for the failure, which
can result from loss of connectivity to the remote
system or a resource definition problem. Refer to the
TXSeries for Multiplatforms Problem Determination
Guide for further information concerning error codes
primaryCode and secondaryCode. Check the error
logs of the remote system to determine whether there
are any relevant messages. Determine the cause of the
problem and take appropriate remedial action before
retrying the failing request.
Destination:
CSMT
ERZ032002E The CICS-private transaction which
schedules remote transaction initiation
requests received communications
error primaryCode/secondaryCode
from system sysId.
Explanation:
The CICS-private transaction which schedules remote
transaction initiation requests received a
communications error during a conversation with system
sysId. This can result from loss of connectivity to that
system.
System action:
User response:
Intercommunication Guide for further information
concerning error codes primaryCode and
secondaryCode. Check the error logs of the remote
system to determine whether there are any relevant
User response:
221
ERZ032003E ERZ032008E
messages. Determine the cause of the problem and
take appropriate remedial action before retrying the
failing request.
Destination:
CSMT
ERZ032003E Transaction transId not executed on
terminal termId on system sysId.
Schedule request failed on that
system.
Explanation:
A request was made to schedule a task on remote
system sysId. The request was not able to be
executed.
Correct the CICS region definitions to be consistent.

Destination:
CSMT
ERZ032006E Message from system sysId garbled.
Explanation:
transaction initiation requests has received an
unintelligible message.
System action:
The conversation to the remote system is abnormally
terminated. The CICS-private transaction on this system
is abnormally terminated. Other processing continues.
User response:
Check the system definition tables of the remote system
to determine why schedule requests are not honored.
User response:
If this problem occurs repeatedly, determine the details
of remote requester from the remote system identified in
this message. Inform the administrator of that system of
the problem with a request to prevent this from
re-occurring. Ensure that the problem is not a
consequence of the CICS-private transaction being
invoked from an application program on that system.
Destination:
CSMT
Destination:
CSMT


Terminal invalid on that system.
System action:
Explanation:
transaction initiation requests has abnormally terminated
on system sysId.
System action:
User response:
Check the error logs of system sysId to determine the
reason for the abend on that system.
Destination:
CSMT
ERZ032005E System identifier for terminal termId
cannot be determined.
Explanation:
A request was made on this system to schedule a
transaction for a remote terminal, which has a system
identifier of NULL or a system identifier of a system
which is not defined.
System action:
transaction initiation requests is abnormally terminated
User response:
222
Explanation:
A request was made to schedule a task on remote
system sysId. The request was not able to be executed
because terminal termId is not defined on system
sysId.
System action:
Other processing continues. The request to schedule
the transaction is lost.
User response:
Ensure that terminal termId and transaction transId
are defined on system sysId.
Destination:
CSMT
ERZ032008E CICS-private transaction received an
unknown message from system sysId.
Explanation:
transaction received a message that was not expected
and is not supported.
System action:
The transaction is abnormally terminated on this
system. Other processing continues.
User response:
If this problem occurs repeatedly, determine the details
of remote requester from the remote system identified in
this message. Inform the administrator of that system
ERZ032009E ERZ032014E
about the problem with a request to prevent this from
re-occurring. Ensure that the problem is not a
consequence of the CICS-private transaction being
invoked from an application program on that system.
Destination:
CSMT
ERZ032009E
Request from System sysId to

initiate transaction transId on that
system on terminal termId was not
executed. Transaction is not defined
correctly on this system.
Explanation:
A transaction transId was scheduled on system sysId
against a terminal termId residing locally on this
system. Because the request was to run the transaction
transId on system sysId, the transaction must be
routed back to that system. However, the local definition
of the transaction transId is not correct.
A definition is required on this system defining the
transaction transId as remote on system sysId.
System action:
User response:
are defined correctly on both systems.
In particular, ensure that there is a transaction definition
for transaction routing the request back to system
sysId from this system. The RemoteSysId attribute in
the TD for transId must be sysId.
Destination:
CSMT
Remote system is quiescing.
Explanation:
A request was made to schedule a transaction on a
remote system sysId. The request was not able to be
executed because the remote system is quiescing.
System action:
The request to schedule the transaction is lost. Other
ERZ032012E Failed to initialize iconv descriptors.

Explanation:
A CICS-private transaction has attempted
unsuccessfully to initialize code page conversion (which
is used to perform ASCII/EBCDIC translation). As a
result intercommunication fails.
System action:
The CICS-private transaction is abnormally terminated.
User response:
There is a serious problem with the national language
support (NLS) environment of the operating system. A
required code page descriptor is possibly not installed.
A preceding message indicates which one is missing. If
the required NLS environment cannot be installed then
the CICS system must be restarted with a locale which
is supported on the system.
Destination:
CSMT
ERZ032013E ASCII/EBCDIC conversion has failed.
Explanation:
CICS-private transaction has been unable to perform an
ASCII/EBCDIC conversion.
System action:
The transaction is abnormally terminated. Other
User response:
Investigate the remote terminal definitions and
transaction definitions to determine whether they are
valid. If an invalid definition is found then correct it else
Destination:
CSMT
ERZ032014E Terminal definition for Terminal
termId specifies a remote system
identifier which is the same as the
local system.
Explanation:
A request to initiate a transaction for a remote terminal
cannot be processed as the terminal definition is
inconsistent.
User response:
Wait until the remote system is back in service before
sending any more requests to it.
System action:
The transaction is abnormally terminated. The request
to schedule the transaction is lost. Other processing
continues.
Destination:
CSMT
User response:
Correct the terminal definition.
Destination:
CSMT
223
ERZ032021E ERZ032027I
ERZ032021E
Transaction transId not executed on

Transaction is not defined correctly on
that system.
Explanation:
A transaction transId was scheduled on this system
against a terminal termId residing on the remote
system sysId. Because the request was to run the
transaction transId locally, the transaction must be
routed back to this system to run. However, the
definition of the transaction transId on system sysId is
not correct.
A definition is required on system sysId defining
transId as residing on this system.
System action:
The transaction is not scheduled. Other processing
continues.
User response:
are defined correctly on both systems. In particular,
ensure that there is a transaction definition for routing
transaction transId back to this system from the remote
system sysId.
Investigate how the connection definition has been

removed.
Destination:
CSMT
ERZ032025E Unable to obtain database entry for
terminal termId.
Explanation:
The terminal definition has been removed from the
runtime system. This is most likely to be an operational
error.
System action:
User response:
Investigate how the terminal definition has been
removed.
Destination:
CSMT
ERZ032026E Unsuccessful attempt to start the
CICS-private remote scheduling
transaction (CRSR).
Destination:
CSMT
Explanation:
CICS detected that the CICS-private transaction CRSR
was not defined in the regions database.
ERZ032022E Request from System sysId to initiate

transaction transId on that system on
terminal termId was not executed.
Terminal invalid on this system.
System action:
START requests that are for remotely defined terminals
are never processed. Other processing continues.
Explanation:
A request was received from remote system sysId to
initiate transaction transId on system sysId on terminal
termId. The request was not able to be honored
because terminal termId is not defined in this system.
System action:
User response:
are defined on both systems.
Destination:
CSMT
ERZ032024E Unable to obtain database entry for
system sysId.
Explanation:
The connection definition has been removed from the
runtime system. This is most likely to be an operational
error.
System action:
User response:
224
User response:
Ensure that the CICS-private transaction definitions are
the same as the default definitions for the CICS-private
transaction CRSR and restart the region.
Destination:
CSMT
ERZ032027I Communications with remote system
sysId failed; remote terminal START
requests not being transmitted.
Explanation:
This is an informational message. It informs CICS users
that START requests for remote terminals on the
specified system are not being sent since the remote
system is out of service. Requests remain queued until
the remote system is back in service.
System action:
START requests for remote terminals on the given sysid
are queued on this system.
User response:
Make arrangements to get remote system sysId back in
service.
Destination:
CSMT
ERZ032028I ERZ034001E
ERZ032028I Communications with remote system
sysId succeeded; sending remote
terminal START requests.
Explanation:
A previously out of service system is now in service.
START requests for remote terminals on that system
are now being sent to it.
System action:
START requests for terminals on the specified system
are now sent.
User response:
None
Destination:
CSMT
ERZ032029I Unsupported message type
(messageType) requested
Explanation:
A request to ship an unsupported message type to the
partner CICS system has been received.
System action:
No action is taken for this request. Other processing
continues.
User response:
None
ERZ032031E The CICS-private transaction CRSR

was invoked incorrectly
Explanation:
transaction initiation requests was invoked incorrectly for example, by an application issuing an EXEC CICS
START TRANSID(CRSR).
System action:
User response:
Establish how the CRSR transaction was invoked.
CRSR is a CICS-private transaction that must only ever
be started by CICS. Ensure that the InvocationMode
specified in the Transaction Definition (TD) for the
CRSR transaction has not been changed from the
default value, (this can possibly allow applications to
start the transaction illegally).
Destination:
CSMT
ERZ033001E Transaction transId rejected errorString.
Explanation:
The transaction transId was submitted to the
Transaction Scheduler (TS), but the TS rejected the
request for the reason given in errorString.
Destination:
CSMT
System action:
CICS does not run the transaction. The terminal is
ready to submit another transaction.
ERZ032030E Request from System sysId to initiate

transaction transId on that system on
terminal termId was not executed.
Transaction was dynamic on this
system.
User response:
Check that you specified the correct transaction name.
Check that transaction transId is correctly defined in
the Transaction Definitions (TD). Also check other
messages for signs of problems with the TS.
Explanation:
A request was received from system sysId to initiate
transaction transId on that system on terminal termId.
The request was not able to be honored because
transaction transId is defined as being dynamic on this
system.
Destination:
stderr
System action:
User response:
Ensure that dynamic transactions are not invoked on an
intermediate system. Ensure that the local transaction
definition does not specify that the transaction is
dynamic.
Destination:
CSMT
ERZ034001E Region name regionName is too long

Explanation:
Your Resource Definition Online (RDO) operation is
unsuccessful because the region name that you
specified is too long.
System action:
The RDO operation terminates.
User response:
Retry the RDO operation, specifying a shorter region
name.
Destination:
stderr
225
ERZ034002E ERZ034007E
ERZ034002E Unsuccessful Region Pool memory
allocation when inserting runtime
database entry resourceName into
class className
Explanation:
CICS was attempting to obtain sufficient Region Pool
memory to insert the runtime database entry. Insufficient
Region Pool memory was available.
stderr
ERZ034005E Abnormal termination U3405. Cannot
allocate Region Pool memory for
region database
Explanation:
CICS is unable to allocate enough memory, from the
Region Pool, to initialize the runtime database.
System action:
The entry is not inserted into the runtime database.
System action:
User response:
You can temporarily increase the size of the Region
Pool available by restarting the region and overriding
the MaxRegionPool attribute, with a larger value, on the
command line.
User response:
You can temporarily increase the size of the Region
pool available by restarting the region and overriding the
command line.
Destination:
console.msg and stderr
Destination:
stderr

deallocation when inserting runtime
database entry resourceName into
class className
ERZ034006E Unable to setup communications with

region. Runtime database request not
sent.
Explanation:
CICS was unable to release Region Pool memory used
during an attempt to insert an entry into the runtime
database.
System action:
The entry is still inserted into the runtime database
unless indicated otherwise by another message. The
Region Pool memory that has not been released is
released when the region is restarted.
User response:
There is a serious problem with your region. Restart the
region at the earliest opportunity. If the problem persists,
Destination:
console.msg and stderr
ERZ034004E Abnormal termination U3406. Invalid
runtime database hash table size
specified for class className
Explanation:
The value in RD stanza ClassTableSize attribute for
class className is invalid.
System action:
User response:
You can restart the region overriding the ClassTableSize
attribute, with valid values, on the command line. For a
permanent solution, update the ClassTableSize attribute
values in the RD resource definition stanza file. using
cicsupdate.
Destination:
226
Explanation:
Your Resource Definition Online (RDO) operation has
made an unsuccessful attempt to set up
communications with a region. The RDO request has
not been sent to the region, and CICS has therefore not
performed this operation on the runtime database.
System action:
The runtime database RDO operation terminates.
User response:
Check that the region is available before retrying the
RDO command.
Destination:
stderr
ERZ034007E Unable to communicate with region.
Runtime database request not sent.
Explanation:
made an unsuccessful attempt to communicate with a
region. The RDO request has not been sent to the
region, and CICS has therefore not performed this
operation on the runtime database.
System action:
User response:
Retry the RDO runtime operation. If it continues to fail,
Destination:
stderr
ERZ034008E ERZ034013W
ERZ034008E Unable to communicate with region.
Runtime database request already
sent.
Explanation:
made an unsuccessful attempt to communicate with the
region, but has already sent the RDO request to the
region. CICS possibly performed the runtime database
operation.
ERZ034011E Unsuccessful attempt to access

permanent database entry
resourceName in class className;
error code errorNumber
Explanation:
The Resource Definition Online (RDO) operation was
unsuccessful when accessing the permanent database
stanza files for the reason defined by the operating
system as error code errorNumber.
System action:
System action:
User response:
Messages in the regions console.msg possibly indicate
the cause of the failure. Retry the RDO runtime
operation.
User response:
Refer to operating system documentation for the error
code.
Destination:
stderr
Destination:
stderr
ERZ034012E Invalid server name serverName
ERZ034009E Runtime database request rejected by

region
Explanation:
CICS has vetoed the runtime database operation.
Messages in the regions console.msg indicate why the
operation has been vetoed.
System action:
The Resource Definition Online (RDO) runtime
database operation terminates.
User response:
Check the regions console.msg for the reason why the
operation was vetoed and respond accordingly.
Destination:
stderr
ERZ034010E Unsuccessful update to permanent
database entry resourceName in class
className
Explanation:
CICS detected error(s) in the updates requested to the
permanent database entry. Messages indicating the
error(s) encountered have already been written to
stderr.
System action:
The Resource Definition Online (RDO) operation
terminates.
User response:
As indicated by the previous message(s) detailing the
errors in the update request.
Destination:
stderr
Explanation:
The server name serverName must conform to the
CICS naming conventions for Servers. This is
/.:/cics/sfs/serverName for Structured File Servers
(SFS) and /.:/cics/ppc/gateway/gatewayName for PPC
Gateways.
System action:
CICS does not perform the CICS database operation.
User response:
Correct the input and retry the database operation.
Destination:
stderr
ERZ034013W Permanent database entry
resourceName already exists in class
className
Explanation:
You attempted to insert an entry that already exists in
the permanent database.
System action:
The entry is not inserted into the permanent database
and the Resource Definition Online (RDO) operation
terminates.
User response:
Select a new key or delete the existing entry
resourceName, as appropriate, and perform the insert
again. The insert was possibly unsuccessful because
another user inserted an entry with the same key.
Destination:
stderr
227
ERZ034015W ERZ034021E
resourceName in class className is
flagged as permanent. Amendment not
allowed.
Explanation:
You attempted to amend a permanent database entry
whose Permanent attribute has the value yes. Such
database entries cannot be amended.
System action:
The permanent database entry is not amended.
User response:
Perform an amendment to the entry that modifies its
Permanent attribute to no. You can make simultaneous
and/or further amendments to that entry until the
Permanent attribute is amended back to yes. Perform
such modifications with care.
ERZ034018E You are not authorized to operate on

the runtime database class className
Explanation:
You attempted to perform an operation on a runtime
database classs recovery image that you do not have
authority to operate on. The file access rights to the
runtime database recovery image stanza file,
administered by the operating system, do not allow you
access.
System action:
The operation terminates. The runtime database
operation has not been performed.
User response:
Login as a user with sufficient access to perform
updates to the classs run-time database recovery
image.
Destination:
stderr
Destination:
stderr

resourceName in class className
flagged as permanent. Deletion not
allowed.
ERZ034020E You are not authorized to operate on

the permanent database class
className
Explanation:
You attempted to delete a permanent database entry
whose Permanent attribute has the value yes. Such
database entries cannot be deleted.
System action:
The permanent database entry is not deleted.
User response:
If you want to delete the entry, you must first modify the
entrys Permanent attribute to no.
Destination:
stderr
ERZ034017E Unable to auto start. Incomplete or
missing runtime database recovery
image
Explanation:
CICS has detected a missing run-time database
recovery image stanza (.auto) file.
System action:
Startup of the region is terminated.
User response:
Either cold start the region or recover the run-time
database recovery image from a backup and attempt
the automatic start again.
Destination:
stderr
Explanation:
You attempted to perform an operation on a permanent
database classs stanza file that you do not have
authority to operate on. The file group access rights of
the stanza file do not allow you access.
System action:
The operation terminates. The permanent database
request has not been performed.
User response:
Login as a user with sufficient group access to perform
updates to the class in the permanent database. Group
access is required because any access to the database
class stanza file possibly requires reinstatement of a
backup file that was created and thus owned by another
administrator.
Destination:
stderr
ERZ034021E Runtime database initialization
unsuccessful
Explanation:
CICS detected error(s) during initialization of the runtime
database. Other error messages explain why the
initialization was unsuccessful.
System action:
User response:
As indicated by the message(s) detailing the errors
during database initialization. If these are errors in the
stanza entry(s) you must cold start the region.
Destination:
228
ERZ034023E ERZ034028E
console.msg
ERZ034023E Unable to setup access to stanza file
filePath; error code errorNumber
Explanation:
CICS cannot set up the file ownership and access rights
to the stanza file filePath. The error given by the
operating system as errorNumber specifies the reason
for the failure.
System action:
If the error occurs during region startup, CICS
terminates the startup procedure. If the error occurs
during a Resource Definition Online (RDO) session,
CICS terminates the current RDO operation.
User response:
On UNIX refer to the operating system documentation
on chown() and chmod(). On Windows NT refer to the
operating system documentation on setting file access
permissions.
Destination:
Permanent database stanza file
filePath does not exist
Explanation:
CICS cannot find the permanent database stanza file
filePath.
ERZ034026E Unable to access stanza file filePath;

Explanation:
CICS detected an error when attempting to access the
stanza file filePath. The operating system gives the
error as errorNumber.
System action:
User response:
As indicated by the operating system in the error code.
If the file is a permanent database classs stanza file it
can be restored from a backup. If the file is a temporary
or backup stanza file used during database operation
then the operation can be retried.
Destination:
ERZ034027E Unable to recover stanza file filePath
Explanation:
CICS detected an error when attempting to recover the
stanza file filePath. This message follows a detailed
message indicating the actual error that occurred.
System action:
System action:
User response:
Recover the permanent database stanza file from a
backup.
User response:
As indicated by the preceding message(s) detailing the
error detected.
Destination:
console.msg
Destination:
ERZ034025E Unable to access stanza file filePath
ERZ034028E Unable to remove temporary stanza

file filePath; error code errorNumber
Explanation:
CICS detected an error when attempting to access the
stanza file filePath. This message follows a detailed
message indicating the actual error that occurred.
System action:
User response:
As indicated by the preceding message(s) detailing the
error detected.
Destination:
Explanation:
CICS detected an error when attempting to remove the
System action:
User response:
remove(). The temporary stanza file is removed by the
next successful operation on the stanza.
Destination:
229
ERZ034029E ERZ034035E
ERZ034029E Unable to close stanza file filePath;
Explanation:
CICS detected an error when attempting to close the
System action:
If this error occurs during startup, CICS terminates the
startup procedure. If the error occurs during a Resource
Definition Online (RDO) session, CICS terminates the
current RDO operation.
User response:
fclose().
Destination:
ERZ034030E Unable to obtain exclusive lock on
stanza file filePath; error code
errorNumber
className. Other error messages explain why CICS is

unable to initialize the run-time database recovery
image.
System action:
User response:
As indicated by preceding message(s) detailing the
error(s) detected.
Destination:
console.msg
to obtain region name
Explanation:
CICS was unable to determine the name of the region.
System action:
User response:
Retry the operation. If the error continues to occur,
Explanation:
CICS was unable to complete an exclusive lock on the
stanza file filePath.
Destination:
stderr
System action:
ERZ034034W Runtime recovery image already

contains a resourceName entry for
class className
User response:
Refer to the operating system documentation for fcntl().
Destination:
to obtain region pathname
Explanation:
CICS was unable to determine the pathname for the
region.
System action:
Explanation:
CICS regions runtime database recovery image already
contains the entry. The runtime database and its
recovery image are out of synchronization for this entry.
System action:
The runtime database request is performed, but the
recovery image is not updated.
User response:
To get the runtime database and its recovery image
back into synchronization delete the record from the
runtime database and then add again.
Destination:
stderr
User response:
Retry the operation. If the error continues to occur,
ERZ034035E Abnormal termination U3410: Runtime

database recovery image path buffer
exceeded
Destination:
stderr
Explanation:
The size of the CICS internal buffer used to build up
pathnames during initialization of the runtime database
recovery image has been exceeded.
ERZ034032E Abnormal termination U3410: Runtime

database recovery image initialization
unsuccessful for class className
Explanation:
CICS detected an error when initializing the regions
run-time database recovery image for the class
230
System action:
User response:
Re-install the region so that its pathname is shorter.
ERZ034036E ERZ034042E
Destination:
console.msg
ERZ034036E Unsuccessful truncation of file
Explanation:
CICS detected an error given by the operating system
as errorNumber when truncating the stanza or
temporary file filePath for the permanent or runtime
database recovery image. A subsequent message
identifies the file or database and database class
affected.
System action:
If this error occurs during region startup, CICS
abnormally terminates region. If the error occurs during
a Resource Definition Online (RDO) session, CICS
terminates the current RDO operation.
User response:
CICS resilience ensures that any stanza affected is
recovered next time an operation is performed on that
stanza where the truncation failed. Refer to the
operating system documentation for ftruncate().
Destination:
ERZ034038E Invalid data detected in database
stanza entry resourceName for class
className
Explanation:
CICS detected a data conversion error when reading
the permanent database entry in the stanza file for class
className. Messages indicating the error(s) detected
have already been written to stderr or console.msg.
System action:
terminates the region. If the error occurs during a
Resource Definition Online (RDO) session, CICS
User response:
As indicated by the previous messages detailing the
errors encountered.
Destination:
ERZ034039E Cannot convert value attributeValue
for attribute attributeName into a
number
Explanation:
CICS cannot convert the attribute value attributeValue
into a valid number. If the error is detected in a CICS
database stanza file, rather than user input, further
messages are generated identifying the database
stanza entry containing the invalid value.
System action:

User response:
If the error is in a CICS database entry, edit the stanza
entry identified by subsequent messages to correct the
attribute value. If necessary, recover the database
stanza from a backup. If the error occurred when
entering an RDO operation, correct the input and retry
the command.
Destination:
ERZ034040E Attribute attributeName: Invalid value
attributeValue
Explanation:
CICS detected an invalid data value attributeValue for
the attribute attributeName. If the error is detected in a
CICS database stanza file, rather than user input,
further messages are generated identifying the
database stanza entry containing the invalid value.
System action:
User response:
the command.
Destination:
ERZ034042E Attribute attributeName: String value
starting attributeValue is too long
Explanation:
The attribute value attributeValue is longer than the
maximum string value length allowed for that attribute. If
the error is detected in a CICS database stanza file,
rather than user input, further messages are generated
identifying the database stanza entry containing the
invalid value.
System action:
User response:
231
ERZ034043E ERZ034047E
the command.
Destination:
ERZ034043E Attribute attributeName: String value
attributeValue has missing end quotes
Explanation:
The attributes string value attributeValue does not have
end quotes. If the error is detected in a CICS database
stanza file, rather than user input, further messages are
generated identifying the database stanza entry
containing the invalid value.
System action:
User response:
the command.
Destination:
ERZ034044E Attribute attributeName: Unexpected
quote characterValue found in string
value
ERZ034045E The stanza entry key stanzaKey is

embedded within another stanza entry
in database class className
Explanation:
CICS has unexpectedly encountered a stanza key
stanzaKey when scanning the attributes for a stanza
record in the class. This condition occurs either because
the blank separator line between two stanza records in
the class is missing, or because a : (rather than an =)
has been encountered after an attribute name. Further
stanza entry containing the unexpected key.
System action:
CICS ignores the key and continues converting the
remaining attributes to check for further errors. If the
error occurred during startup, CICS abnormally
User response:
entry identified by subsequent messages to add the
missing blank line between the stanza entries. If
necessary, recover the database stanza from a backup.
Destination:
ERZ034047E Attribute attributeName: Value
attributeValue out of range (minimum
minimumValue, maximum
maximumValue)
Explanation:
The attributes string value contains an unexpected
quote character. If the error is detected in a CICS
database stanza file, rather than user input, then further
Explanation:
The attribute value attributeValue is too big or too small
for the attribute. The allowable minimum value
minimumValue and maximum value maximumValue are
given. If the error is detected in a CICS database
System action:
System action:
User response:
If the error is in a CICS database entry edit the stanza
entry identified by subsequent messages and correct
the attribute value. If necessary, recover the database
the command.
User response:
the command.
Destination:
Destination:
232
ERZ034048E ERZ034052E
attributeValue out of range (minimum
minimumValue, maximum
maximumValue)
Explanation:
The attribute value attributeValue is too big or too small
for the attribute. The allowable minimum value
minimumValue and maximum value maximumValue are
given. If the error is detected in a CICS database
System action:
User response:
the command.
Destination:
ERZ034049W Attribute attributeName: Unexpected
data data ignored
Explanation:
The attribute value contains unexpected data. If the
error is detected in a CICS database stanza file, rather
than user input, further messages are generated
identifying the database stanza entry containing the
invalid value.
System action:
If this error occurs during startup, CICS continues to
bring up the region. If the error occurs during a
User response:
the command.
Destination:
attributeValue is an invalid key for
class className
Explanation:
The attribute value attributeValue is used as a key for

the database class className. The value is an invalid
key for that class. If the error is detected in a CICS
database stanza file, rather than user input, further
System action:
User response:
the command.
Destination:
ERZ034051E Vetoed attempt to insert or alter
runtime database entry resourceName
in class className
Explanation:
An attempt to insert or commit an update to an entry, in
the run-time database, has been vetoed. Previous
message(s) have been generated detailing the error(s)
in the entry.
System action:
The insert or update operation has not been performed.
User response:
Take the actions indicated by the previous messages
detailing the errors encountered and retry the insert
operation.
Destination:
console.msg
ERZ034052E Attribute attributeName: Non-ASCII
character encountered
Explanation:
The attributes string value contains unexpected
non-ASCII data. Only ASCII characters are allowed in
this attributes string value. If the error is detected in a
CICS database stanza file, rather than user input,
further messages are generated identifying the
database stanza entry containing the invalid value.
System action:
User response:
233
ERZ034055E ERZ034061E
the command.
Destination:
ERZ034055E Attribute attributeName: No room in
CICS internal buffer
Explanation:
CICS found insufficient buffer space available to
accommodate data for the attribute attributeName,
when converting the data from internal to external
(stanza) format.
System action:
If this error occurs in a region, CICS abnormally
User response:
Retry the operation. If this error continues to occur
contact, your support organization.
Destination:
allocation when updating runtime
database usage count for entry
resourceName in class className
Explanation:
CICS was unable to update the usage count of the
given database entry because the CICS Region Pool
does not have sufficient memory available.
System action:
The runtime database operation fails.
User response:
You can increase the size of the Region pool available
command line.
Destination:
console.msg
allocation when saving a copy of
runtime database entry resourceName
in class className
Explanation:
CICS was unable to take a copy of the given database
entry because the CICS Region Pool does not have
sufficient memory available.
System action:
The runtime database operation fails.
234
User response:
You can increase the size of the Region pool available
command line.
Destination:
console.msg
deallocation when accessing runtime
database
Explanation:
CICS was unable to release Region Pool memory used
during an attempt to access the runtime database.
System action:
CICS possibly continues processing, but there is a
serious problem with the runtime database.
User response:
There is a serious problem with your region. Restart the
region at the earliest opportunity.
Destination:
console.msg
ERZ034060E Invalid request to run the
CICS-private transaction CURD
Explanation:
The CICS-private transaction named CURD, used to
control communications between CICS regions and
RDO, cannot be started from a terminal.
System action:
code A341.
User response:
Do not attempt to run the CURD transaction.
Destination:
CSMT
ERZ034061E Invalid data in Resource Definition
Online (RDO) request to CICS-private
transaction CURD
Explanation:
The CICS-private transaction named CURD, used to
control communications between CICS regions and
RDO, received invalid data from RDO.
System action:
CICS abnormally terminates the transaction without
performing the requested RDO operation on the runtime
database.
User response:
Use CEMT to check that the configuration of the CURD
transaction and its corresponding program are correct.
Fix any errors and retry the operation. If you cannot
solve the problem, contact your support organization.
ERZ034062E ERZ034068E
Destination:
stderr
access to the file, check the regions installation, in

particular the files ownership, group and access
permissions.
ERZ034062E Unable to create a pipe for Region

Definition Online (RDO) to region
communications; error code
errorNumber
Destination:
stderr
Explanation:
made an unsuccessful attempt to create the operating
system pipes for communications with a region. The
RDO request has not been sent to the region, and CICS
has therefore not performed this operation on the
runtime database.
System action:
User response:
Check that the region is available and refer to the
operating system documentation for pipe() before
retrying the RDO operation.
Destination:
stderr
ERZ034064E Unable to remove backup stanza file
Explanation:
as errorNumber when attempting to remove the given
stanza file.
System action:
User response:
remove(). The temporary stanza file is removed by the
next successful operation on the stanza.
Destination:
ERZ034065E Your file access permissions do not
allow you to execute fileName
Explanation:
You are not in the set of users who are allowed execute
access to the file fileName. Subsequent messages
indicate the CICS operation that has failed.
System action:
The current CICS operation fails.
User response:
Log in as a user whose access permission allows
execution of the file fileName. If you have execute
ERZ034066E Abnormal termination U3466 - Unable

to cleanup runtime database on
abnormal termination of a task
Explanation:
CICS was unable to clean up the runtime database data
for the task that is terminating. This is probably due to
internal data corruption.
System action:
User response:
Destination:
console.msg
ERZ034067E Unable to execlp() the program
fileName used for Region Definition
Online (RDO) to region
communications; error code
errorNumber
Explanation:
made an unsuccessful attempt to execlp the program
fileName that is used in communications with a region.
The RDO request has not been sent to the region, and
CICS has therefore not performed this operation on the
runtime database.
System action:
User response:
execlp().
Destination:
stderr
ERZ034068E Abnormal termination A342.
CICS-private transaction CURD could
not communicate with Resource
Definition Online (RDO)
Explanation:
The CICS-private transaction CURD, used in CICS
region to RDO communications, made an unsuccessful
attempt to communicate with RDO.
System action:
CICS abnormally terminates the CICS-private
transaction CURD.
User response:
235
ERZ034069E ERZ034075E
Retry the RDO operation; if the operation continues to
fail, use CEMT to check that the configuration of the
CURD transaction and its corresponding program are
correct. Fix any errors and retry the operation. If you
cannot solve the problem, contact your support
organization.
Destination:
CSMT
internal database control structure for
class className
Explanation:
Self-consistency checking by CICS has detected that
the runtime database internal control structure for the
database class className is inconsistent.
System action:
User response:
inconsistencies, contact your support organization.
Destination:
console.msg
detected zero table entries for runtime
database class className in control
structure at address address
Explanation:
the runtime database internal control structure, at the
address given, contains no table entries. This is
inconsistent with the expect minimum of one.
System action:
User response:
Destination:
console.msg
ERZ034071E Unable to obtain read or shared lock
on stanza file fileName; error code
errorNumber
Explanation:
CICS was unable to complete a read or shared lock on
the stanza file fileName.
System action:
236

User response:
Refer to the operating system documentation for fcntl().
Destination:
ERZ034073E Unable to close a stanza file; error
code errorNumber
Explanation:
as errorNumber when attempting to close a stanza file.
System action:
User response:
fclose().
Destination:
ERZ034074E Unable to write to stanza file filePath;
Explanation:
as errorNumber when attempting to write, flush data, to
the stanza file filePath.
System action:
User response:
fflush(). CICS resilience ensures that, if the file where
the fflush() failed is a permanent database or runtime
database recovery image stanza file, it is recovered
next time an operation is performed on that stanza.
Destination:
ERZ034075E Unable to find the end of a stanza file;
Explanation:
as errorNumber when seeking the end of a stanza file.
System action:
abnormally terminates the region. If the error occurs
ERZ034076E ERZ034081E
User response:
fseek().
Destination:
ERZ034076E Unable to find the start position of a
stanza file; error code errorNumber
Explanation:
as errorNumber when seeking the start of a stanza file.
System action:
User response:
fseek().
Destination:
ERZ034077E Unsuccessful write to a stanza file;
Explanation:
as errorNumber when writing to a stanza file.
System action:

Destination:
console.msg
ERZ034079E Unable to rename stanza file
fromFilePath to toFilePath; error code
errorNumber
Explanation:
as errorNumber when attempting to rename
fromFilePath to toFilePath.
System action:
User response:
rename().
Destination:
ERZ034080E CICS path buffer too small to hold
path of runtime database recovery
image stanza for class className
Explanation:
A path buffer in CICS is too small to hold the full path
name of the runtime database recovery image stanza
file for the class className. The stanza file is the
stanza file itself, a backup of the stanza file, or a
temporary backup of the stanza file.
User response:
fwrite().
System action:
Destination:
User response:

actualSignature at address address
Destination:
console.msg
ERZ034081E Unable to obtain the current position
in a stanza file; error code errorNumber
Explanation:
the signature actualSignature at address address is
inconsistent with the expected signature
expectedSignature
Explanation:
as errorNumber when attempting to obtain the current
position in a stanza file.
System action:
System action:
User response:
237
ERZ034082E ERZ034087W
CICS ignores the named attribute and continues

handling any remaining attributes.
User response:
fgetpos().
User response:
If the error is in a permanent database entry, edit the
stanza entry identified by subsequent messages to
remove or correct the attribute. If necessary, recover the
database stanza from a backup. If the error occurred
when entering an Resource Definition Online (RDO)
operation, correct the input and retry the command.
Destination:
ERZ034082E CICS path buffer too small to hold
path of database stanza for class
className
Explanation:
A path buffer in CICS is too small to hold the full path
name of the permanent database stanza file for class
className. The stanza file is the stanza file itself, a
backup of the stanza file, or a temporary backup of the
stanza file.
System action:
User response:
Destination:
ERZ034083E Unsuccessful attempt to update
permanent database entry
resourceName in class className;
your updated entry is out-of-date
Explanation:
You or your operation attempted to update a permanent
database entry using data that is based on an
out-of-date version of the entry resourceName. This is
because someone else has updated the entry since
Resource Definition Online (RDO) read the entry that
you are attempting to apply the updates to.
System action:
CICS does not amend the entry; the current entry is
returned.
User response:
Attempt the operation again.
Destination:
stderr
ERZ034084W Attribute attributeName not
supported in database class className
Explanation:
The attribute attributeName is not recognized for the
CICS database class className.
System action:
238
Destination:
ERZ034085E Invalid database key resourceName
for database class className
Explanation:
The database entry key resourceName is invalid for the
CICS database class className.
System action:
User response:
If the error is in a permanent database entry edit the
stanza entry identified by subsequent messages and
correct the key. If necessary, recover the permanent
operation, correct the input and retry the command.
Destination:
ERZ034086E Attribute attributeName: No data
specified
Explanation:
CICS found no value for the attribute attributeName.
System action:
CICS ignores the attribute and continues handling any
remaining attributes to check for further errors. The
operation ultimately fails.
User response:
the command.
Destination:
resourceName not found in class
className
Explanation:
ERZ034089E ERZ034095E
CICS was unable to locate the permanent database
entry resourceName in the stanza file for the class
className.
System action:
CICS terminates the current resource Definition Online
(RDO) operation.
User response:
Use RDO to add the given entry or correct your RDO
request.
Destination:
stderr
ERZ034089E Stanza file fileName is empty, does
not have the mandatory default stanza
Explanation:
CICS found that the database stanza file fileName is
empty. Every stanza file must contain a default stanza.
System action:
terminates region. If the error occurs during a Resource
User response:
Edit the stanza file and add a default entry or recover
the database stanza from a backup.
Destination:
ERZ034090E CICS database key too long for class
className; the key is longer than the
maximum of maximumKeyLength bytes
Explanation:
The key is longer than the given maximum length
maximumKeyLength for the database class className.
System action:
CICS does not perform the requested database
operation. Further messages indicate what database
operation has failed.
User response:
If the error is in a permanent database entry, edit the
stanza entry and correct the invalid key. If necessary,
recover the database stanza from a backup. If the error
occurred when entering an Resource Definition Online
(RDO) operation, correct the input and retry the
command. If the error is in a runtime database request,
perform the appropriate action specified by subsequent
messages indicating what database operation failed.
Destination:
ERZ034092E Resource Definition Online (RDO) is

unable to communicate with region
regionName: CICS-private transaction
CURD has abnormally terminated with
code abendCode
Explanation:
Your RDO operation has lost communications with the
region regionName, because the CICS-private
transaction CURD has abnormally terminated with the
abend code abendCode.
System action:
User response:
Perform any appropriate action indicated by the abend
code abendCode and retry the RDO operation.
Destination:
stderr
ERZ034094E Unable to communicate with region
regionName: errorMessage
Explanation:
unable to communicate with the region regionName due
to the transaction scheduler error errorMessage. The
transaction schedulers error message errorMessage is
given.
System action:
User response:
Perform appropriate action dependent on the
transaction scheduler error errorMessage and retry the
RDO operation. Check that the cicssetupclients
command has been run on this system.
Destination:
stderr
ERZ034095E Unable to communicate with region:
unsuccessful attempt to allocate
memory for the communications buffer
Explanation:
unable to communicate with the region, because it is
unable to allocate sufficient memory for an internal
communications buffer.
System action:
User response:
Retry the RDO operation when the machine is less
loaded.
Destination:
stderr
239
ERZ034096E ERZ034101E
ERZ034096E Invalid server name resourceName
Explanation:
The Server name resourceName must be a name
starting with /.:.
System action:
User response:
Correct the input and retry the database operation.
Destination:
stderr
ERZ034097E Database stanza entry resourceName
for class className, requires the
missing attribute attributeName
Explanation:
CICS cannot find the attribute attributeName in the
stanza file entry resourceName for the class
className.
System action:
User response:
Edit the stanza file and add the missing attribute
attributeName or recover the database stanza from a
backup.
Destination:
ERZ034098E The default entry for database class
className is missing or contains
errors
Explanation:
The default database entry in the classs stanza file is
missing or contains errors that have been detailed by
previous messages. Every stanza file must contain a
default stanza.
System action:
User response:
If the default entry is missing, edit the stanza file and
add the missing default entry or, if necessary, recover
the database stanza from a backup. Otherwise, correct
the default entry as indicated by previous error
messages.
Destination:
240
ERZ034099W Unsuccessful attempt to insert entry

into runtime database: an entry with
key resourceName already exists in
class className
Explanation:
CICS cannot insert the given entry into the runtime
database class because an entry with the same key
already exists.
System action:
The runtime database entry is not inserted.
User response:
If you wish to insert this new entry, you must delete the
duplicate entry from the runtime database first.
Destination:
console.msg
ERZ034100E Unsuccessful creation of runtime
database recovery image directory
Explanation:
as errorNumber when attempting to create the given
runtime database recovery image directory filePath.
System action:
User response:
mkdir().
Destination:
console.msg
database recovery image directory
filePath; already exists, but is not a
directory
Explanation:
CICS is unable to create the runtime database recovery
image directory filePath, because the path already
exists and is not a directory.
System action:
User response:
Remove or move the file with the same path as the
runtime database recovery image directory CICS is
attempting to create, and cold start the region.
Destination:
console.msg
ERZ034102E ERZ034107E
database recovery image stanza
filePath; already exists, but is not a
file
Explanation:
CICS is unable to create the runtime database recovery
image stanza file filePath, because the path already
exists and is not a file.
System action:
User response:
Remove or move the directory with the same path as
the runtime database recovery image stanza CICS is
attempting to create, and cold start the region.
ERZ034105E Unsuccessful insertion of entry

resourceName into runtime database
recovery image class className
Explanation:
CICS is unable to insert the entry resourceName into
the runtime database recovery image. Messages
indicating the error(s) encountered have already been
written to stderr.
System action:
terminates.
User response:
errors in the deletion request.
Destination:
console.msg
Destination:
stderr

database recovery image stanza
ERZ034106E Unsuccessful creation of schema

stanza file filePath; error code
errorNumber
Explanation:
runtime database recovery image stanza file filePath. A
regions runtime database recovery image stanzas are
created on a cold start.
Explanation:
schema stanza file filePath.
System action:
User response:
Refer to the operating system documentation for creat()
and write(). Having resolved the error retry a cold start
of your region.
Destination:
console.msg
ERZ034104E Unsuccessful deletion entry
resourceName from runtime database
recovery image class className
Explanation:
CICS is unable to delete the entry resourceName from
the runtime database recovery image. Messages
indicating the error(s) encountered have already been
written to stderr.
System action:
terminates.
User response:
errors in the deletion request.
System action:
User response:
Refer to the operating system documentation for creat()
and write().
Destination:
console.msg
ERZ034107E Unable to remove backup file
fileName; error code errorNumber
Explanation:
CICS is unable to delete a backup file fileName from
the runtime database recovery during cold start. The
error code errorNumber was returned by the operating
system from the function remove().
System action:
User response:
remove() to find why CICS was unable to remove file
fileName. After resolving the problem retry the request
to cold start your region.
Destination:
stderr
Destination:
stderr
241
ERZ034108I ERZ034114E
ERZ034108I Loading region runtime database ...
Explanation:
CICS is loading the runtime database for your region.
System action:
CICS starts loading the runtime database for the region.
User response:
None
Destination:
console.msg
ERZ034109I ... region runtime database loaded!
Explanation:
CICS has completed loading the runtime database for
your region.
System action:
CICS continues starting the region.
User response:
None
Destination:
console.msg
ERZ034110W Data items superfluousDataItems
were ignored for attribute
attributeName. You can only specify
correctValueCount values for this
attribute.
Explanation:
You can only specify correctValueCount values for the
attribute that was in error.
System action:
CICS has ignored the superfluous data items for this
attribute.
User response:
Retry with the correct number of values.

User response:
Recreate and rerun the migration script for this resource
class. You can use the -o option of the cicsmigrate
command to ensure that error and warning messages
are stored in a log file. Serious errors are reported to
stderr. Check both for errors and warnings. See the
TXSeries Installation Guide for more on creating and
running the migration script.
Destination:
ERZ034112E Attribute name oldAttribute in class
className needs to be replaced by the
new name newAttribute
Explanation:
CICS has encountered the attribute name oldAttribute in
a stanza file for database class className. This
attribute has been renamed to newAttribute and the
new name must be used in the stanza.
System action:
CICS ignores the entry for this attribute. If an entry for
the new attribute name is not present in the stanza,
CICS possibly terminates the region.
User response:
Edit the stanza file and replace the old name
oldAttribute with the new name newAttribute.
Destination:
console.msg
ERZ034113W Attribute name oldAttribute in class
className has been replaced by the
new name newAttribute
Destination:
stderr
Explanation:
A command was entered specifying an attribute name,
oldAttribute, which has been changed to newAttribute.
ERZ034111E Version stamp in stanza for class

className is not at the correct level
System action:
CICS accepts the input for the old name as if it were for
the new name, and continues processing the command.
Explanation:
When a patch (Program Temporary Fix) or new version
is installed, the migration process automatically
increases the version number which is located in the
default stanza of every resource definition file. This
message appears if the version number is incorrect or
missing It possibly means that some error occurred
while the patch or new version was being migrated.
(See the TXSeries for Multiplatforms Administration
Reference for more on version stamps and default
stanzas.)
System action:
242
User response:
Use the new attribute name on further commands.
Destination:
stderr
ERZ034114E Unsuccessful attempt to uninstall entry
entryName from the Runtime
Database. Entry is marked as in use.
Explanation:
ERZ034116E ERZ035006E
An attempt was made to uninstall an entry from the
Runtime Database. The request was rejected as the
entry is currently in use.
System action:
The command terminates returning the value 0.
System action:
The entry is not removed from the Runtime Database.
User response:
See the TXSeries for Multiplatforms Administration
User response:
Retry the command when the entry is no longer in use.
Destination:
stderr
Destination:
console.msg
ERZ035003E Unable to create server serverName
ERZ034116E Unable to access runtime database

stanza file for class className.
Explanation:
You attempted to perform an operation on a runtime
database classs recovery image stanza file which was
unable to be found.
System action:
The operation terminates. The runtime database
operation has not been performed.
User response:
Verify that the operation you are attempting to perform
is valid at the current time, and that the stanza file is
supposed to exist. If the file is supposed to exist, then
verify that it has not been deleted and that the path
leading to the file is accessible.
Destination:
stderr
ERZ034117E Unable to access permanent database
stanza file for class className.
Explanation:
You attempted to perform an operation on a permanent
database classs stanza file that was unable to be
found.
System action:
The operation terminates. The permanent database
request has not been performed.
User response:
Verify that the operation you are attempting to perform
is valid at the current time, and that the stanza file is
supposed to exist. If the file is supposed to exist, then
verify that it has not been deleted and that the path
leading to the file is accessible.
Destination:
stderr
ERZ035001I Usage: cicsppcgwycreate { -? | [-v] [-I]
serverName [-m modelId]
[[attributeName=attributeValue]...] }
Explanation:
This is the usage message for the cicsppcgwycreate
command.
Explanation:
The command you have entered was unable to create a
new PPC gateway named serverName. Accompanying
messages identify the cause of the problem.
System action:
The command terminates abnormally, returning the
value 1.
User response:
Use accompanying messages to determine the cause of
the problem. Correct the problem, and retry the
command. If necessary, specify the -I flag to ignore
errors.
Destination:
stderr
ERZ035005E Unable to execute programName
Explanation:
The command you have entered was unable to execute
programName.
System action:
value 1.
User response:
Check that programName is in a directory specified by
your PATH environment variable, and that you have
permission to execute it. Correct the problem and retry
the command.
Destination:
stderr
ERZ035006E You must be logged in as root user
Explanation:
The command you have entered performs actions that
require root authority.
System action:
value 1.
User response:
Login as the root user and retry the command.
Destination:
stderr
243
ERZ035007I ERZ035013E
ERZ035007I Server serverName has been added to
GSD
Explanation:
An entry was added to the Gateway Server Definitions
(GSD) for PPC gateway serverName.
System action:
User response:
None
Destination:
stderr
ERZ035008I Server serverName has been added as
a subsystem
Explanation:
A subsystem was created for the PPC gateway
serverName.
System action:
User response:
None
Destination:
stderr
ERZ035009E Server serverName entry already
exists in GSD
Explanation:
An entry for PPC gateway serverName already exists
in the Gateway Server Definitions (GSD).
Destination:
stderr
ERZ035011E Unable to add server serverName to
GSD
Explanation:
The details of PPC gateway serverName were unable
to be added to the Gateway Server Definitions (GSD).
Accompanying messages identify the cause of the
problem. However, the most likely cause is that there is
already an entry for a PPC gateway of this name.
System action:
value 1.
User response:
the problem. Correct the problem and retry the
errors.
Destination:
stderr
ERZ035012W Unable to add a subsystem definition
for PPC gateway serverName
Explanation:
Subsystem names used for PPC gateways must be
unique. A subsystem definition for PPC gateway
serverName was not added because there is already a
PPC gateway subsystem whose ShortName is the
same as the ShortName specified. Because you have
specified the -I flag to ignore errors the existing
subsystem definition is modified.
System action:
value 1.
System action:
User response:
Either use the cicsppcgwydestroy command to remove
all the server details, or retry the command specifying
the -I flag to ignore errors.
User response:
If the name of the PPC gateway serverName
associated with the ShortName has not changed then
no action is necessary. However, if the PPC gateway
name is different destroy the server and retry command
or override ShortName with a valid one.
Destination:
stderr
ERZ035010W Server serverName entry already
exists in GSD
Explanation:
An entry for PPC gateway serverName already exists
in the Gateway Server Definitions (GSD) but, since the
command was invoked with the -I flag (ignore errors),
the command redefines the existing entry using any
overrides you have specified.
System action:
User response:
None
244
Destination:
stderr
ERZ035013E Unable to add a subsystem definition
for PPC gateway serverName
Explanation:
The command you have entered was unable to add the
details for PPC gateway serverName as a subsystem.
problem. An entry for your PPC gateway was not
created.
System action:
value 1.
ERZ035014E ERZ035019W
User response:
errors.
Destination:
stderr
ERZ035014E A server name was not supplied
Explanation:
The command you have entered requires a PPC
gateway name (for example, /.:/cics/ppc/gateway/
opencics), which was not supplied.
System action:
value 1.
contents using the rm -rf command. If necessary,

specify the -I flag to ignore errors. On Windows NT you
can delete the directory and its contents using the rd -s.
Destination:
stderr
ERZ035017I Removed directoryName
Explanation:
The directory directoryName was deleted, due to errors
when creating a new PPC gateway. Accompanying
messages identify the cause of the problem.
System action:
value 1.
User response:
Retry the command specifying a valid PPC gateway
name.
User response:
errors.
Destination:
stderr
Destination:
stderr
ERZ035015E The value in environment variable

ERZ_SvJsYmPw is incorrect
ERZ035018E Unable to find entryName in GSD
Explanation:
You have exported the environment variable
ERZ_SvJsYmPw. This is invalid since ERZ_SvJsYmPw
is a private CICS environment variable and must not be
used.
System action:
value 1.
Explanation:
The PPC gateway details for entryName was unable to
be retrieved from the Gateway Server Definitions
(GSD). Accompanying messages identify the cause of
the problem.
System action:
value 1.
User response:
Make sure that ERZ_SvJsYmPw is not set in your
environment and retry the command.
User response:
command.
Destination:
stderr
Destination:
stderr
ERZ035016W Unable to remove directoryName
ERZ035019W Unable to add server serverName to

GSD
Explanation:
The command you have entered tried but failed to
delete the directory directoryName and its contents.
problem. This message indicates that the command has
not managed to clean up and that files were not
removed.
System action:
value 1.
User response:
command. On UNIX you can delete the directory and its
Explanation:
The details of PPC gateway serverName was unable
to be added to the Gateway Server Definitions (GSD).
The most likely reason for this is that there is already an
entry for a PPC gateway of this name. As you have
specified the -I flag (ignore errors), the command
continues, using the existing GSD entry.
System action:
User response:
None
Destination:
245
ERZ035020E ERZ035025E
stderr
path of the message file is varDir/cics_servers/GSD/

cics/ppc/gateway/opencics/msg).
ERZ035020E Unable to get server serverName

from GSD
System action:
value 1.
Explanation:
The details of PPC gateway serverName was unable
to be retrieved from the Gateway Server Definitions
(GSD). Accompanying messages identify the cause of
the problem.
User response:
Use the PPC gateway messages to determine why the
server is not running. If necessary, correct the problem
System action:
value 1.
Destination:
stderr
User response:
Use messages to determine the cause of the problem.
Correct the problem and retry the command.
ERZ035024E Unable to shut down server

serverName
Destination:
stderr
ERZ035021I Usage: cicsppcgwylock { -? | { { -l | -u |
-t } serverName } }
Explanation:
This is the usage message for the cicsppcgwylock
command.
System action:
User response:
Destination:
stderr
ERZ035022I Usage: cicsppcgwyshut { -? | [-f] [-c]
serverName }
Explanation:
This is the usage message for the cicsppcgwyshut
command.
System action:
User response:
Destination:
stderr
ERZ035023E Server serverName is not running
Explanation:
The PPC gateway serverName is not running so the
command was unable to be executed. The PPC
gateway writes its messages to a file called msg under
the varDir/cics_servers directory structure in a
sub-directory based upon its name (for example for a
server named /.:/cics/ppc/gateway/opencics the full
246
Explanation:
The PPC gateway serverName was unable to be shut
down. Accompanying messages identify the cause of
the problem. The PPC gateway writes its messages to a
file called msg under the varDir/cics_servers directory
structure in a sub-directory based upon its name (for
example for a server named /.:/cics/ppc/gateway/
opencics the full path of the message file is
varDir/cics_servers/GSD/cics/ppc/gateway/opencics/
msg).
System action:
value 1.
User response:
Use accompanying CICS and server messages to
determine the cause of the problem. Correct the
problem and retry the command.
Destination:
stderr
ERZ035025E The request to stop server
serverName was unsuccessful
Explanation:
The command you have entered made a request to
stop the subsystem running PPC gateway serverName.
This request did not succeed. Accompanying messages
identify the cause of the problem.
System action:
value 1.
User response:
If after examining the accompanying messages you are
unable to determine the cause of the problem, retry the
command first using the -f flag (immediate shutdown)
and, if that is unsuccessful, the -c flag (cancel
subsystem).
Destination:
stderr
ERZ035026I ERZ035031W
ERZ035026I The lock has been removed for server
serverName
Explanation:
The lock, which indicates that PPC gateway
serverName is running, was removed.
ERZ035029E Server serverName was forcibly

unexpected exit
Destination:
stderr
Explanation:
The PPC gateway serverName terminated abnormally,
not as a result of a system or user requested shutdown,
and without completing the normal shutdown procedure.
The PPC gateway writes its messages to a file called
msg under the varDir/cics_servers directory structure
in a sub-directory based upon its name (for example for
a server named /.:/cics/ppc/gateway/opencics the full
cics/ppc/gateway/opencics/msg).
ERZ035027I Usage: cicsppcgwynotify { -? |

subsystemName }
System action:
value 1.
System action:
User response:
None
Explanation:
This is the usage message for the cicsppcgwynotify
command.
System action:
User response:
None.
Destination:
stderr
ERZ035028E The subsystem subsystemName has
returned unexpectedly
Explanation:
The subsystem subsystemName has terminated
unexpectedly and the cicsppcgwynotify command,
which is handling this event, was unable to reference
the PPC gateways name. The most likely reason for
this is that a PPC gateway was destroyed while it was
still running. The PPC gateway writes its messages to a
msg).
System action:
value 1.
User response:
If you think that the PPC gateway is still supposed to be
active, first use the subsystem name, which has the
format cicsppcgwy.ShortName, to identify which server
was running in that subsystem. For example, you can
use cicsget -c gsd -l to give the name of each server
and cicsget -c gsd serverName to give the corresponding
ShortName. Then use the PPC gateway messages to
determine why the server is not running.
Destination:
stderr
User response:
Use the messages from the PPC gateway and from the
operating system to determine why the server is not
running. Correct the problem and restart the PPC
gateway. If the problem persists contact your support
organization.
Destination:
stderr
ERZ035030I Authorization for server serverName
has been set to authorizationLevel
Explanation:
The authorization level of a PPC gateway indicates
whether or not the server Access Control Lists (ACLs)
are checked. A value of 0 indicates that authorization is
disabled and that ACLs are not checked. A value of 1
indicates that ACLs are checked.
System action:
User response:
None
Destination:
stderr
ERZ035031W Unable to update details of server
serverName
Explanation:
The command you have entered was unable to change
PPC gateway serverName. However, as you specified
the -I flag (ignore errors) on the command you entered,
the existing details are used. Accompanying messages
System action:
User response:
If the details of the PPC gateway serverName do not
need to be modified then no action is necessary.
However, if the PPC gateway details are different, use
247
ERZ035032E ERZ035039I
accompanying messages to determine the cause of the
problem. Correct the problem and retry the command.
Destination:
stderr
ERZ035032E Unable to remove primaryRestartFile
or backupRestartFile for server
serverName
Explanation:
When trying to cold start PPC gateway serverName
the command you have entered was unable to delete
the restart files that are used on an automatic start. It is
not possible to cold start a PPC gateway while either
the primaryRestartFile or the backupRestartFile exist.
problem.
System action:
User response:
This message indicates that the server was run and
contains recoverable data that is lost on a cold start. If
you really want to cold start, then use the
Destination:
stderr
ERZ035034E Server serverName was unable to
read or write to logical volume
volumeName using Id userId
Explanation:
The PPC gateway serverName keeps all its logging
information on the operating system logical volume
volumeName. In order for the PPC gateway to function
correctly it needs to be able to read and write to this
volume. It was unsuccessful. The most likely cause of
this problem is that the logical volume is not owned by
userId.
System action:
User response:
Investigate why userId is unable to read or write to
volumeName. Correct the problem and retry the
command. On UNIX, if the volumeName is not owned
by userId then use the operating system command
chown to change its ownership. On Windows NT,
consult the operating system documentation on taking
ownership of files.
Destination:
stderr
ERZ035036E Server serverName is already

running
Explanation:
The command you have entered is attempting to start a
PPC gateway named serverName. However, there is
already a server of this name running.
System action:
User response:
Shut down the existing PPC gateway and retry the
command.
Destination:
stderr
ERZ035037E The request to start server
Explanation:
start PPC gateway serverName. This request was
unsuccessful. Accompanying messages identify the
System action:
User response:
command.
Destination:
stderr
ERZ035038I Subsystem subsystemName has been
initialized
Explanation:
The subsystem subsystemName was successfully
initialized and a PPC gateway was started.
System action:
User response:
None
Destination:
stderr
ERZ035039I Waiting for subsystem
subsystemName to become active
Explanation:
The subsystem subsystemName was started. This
message is issued while the command you have
entered waits for it to become active.
System action:
User response:
248
ERZ035040E ERZ035047E
None
Destination:
stderr
ERZ035040E Timed out waiting for subsystem
subsystemName to respond
Explanation:
The subsystem subsystemName has not responded
within the time limit allowed by the command. The PPC
gateway writes its messages to a file called msg under
server named /.:/cics/ppc/gateway/opencics the full
cics/ppc/gateway/opencics/msg). If the msg file does
not exist check that the ppcgwy code is actually
installed.
System action:
User response:
Use the PPC gateway messages to determine why the
server is not running.
Destination:
stderr
ERZ035041E Timed out waiting for server
serverName to start
Explanation:
The PPC gateway serverName has not responded to
Remote Procedure Calls (RPCs) within the time limit
allowed by the command. If you were auto starting the
server (the default action), this message does not
necessarily indicate that there is a problem since the
PPC gateway can have a large amount of data to
recover that can possibly take longer than the timeout
defined. The PPC gateway writes its messages to a file
called msg under the varDir/cics_servers directory
msg).
System action:
User response:
Use the PPC gateway messages to determine if there is
a problem. If there is a problem, shut down the server
(using, for example the cicsppcgwyshut command),
correct the problem and retry the command. If the
ppcgwy process is using a large amount of processing
time (use an operating system command, for example
ps, to find out this information) then the PPC gateway is
almost certainly still recovering data; continue to wait for
the server to become active. Once the server has
initialized it writes a message. If the problem persists
either cold start the PPC gateway, serverName, in
which case all its recoverable information is lost, or

Destination:
stderr
ERZ035042I Server serverName is responding to
RPCs
Explanation:
The PPC gateway serverName is responding to
Remote Procedure Calls (RPCs). This means that the
server is ready to process requests.
System action:
User response:
None
Destination:
stderr
ERZ035046I Usage: cicsppcgwy { -? | [-I] [-v] [-t
traceMask] [[-T traceDestination]...]
[serverName]
Explanation:
This is the usage message for the cicsppcgwy
command. The server name must be specified on a
cold start. For an automatic start the command uses the
contents of environment variable
CICS_PPCGWY_SERVER.
System action:
User response:
Destination:
stderr
ERZ035047E Server serverName with log volume
volumeName could not be enabled
Explanation:
PPC gateway serverName was not able to be enabled
for full operations, using the command ppcadmin enable
server. Accompanying messages identify the cause of
the problem. The PPC gateway writes its messages to a
msg).
System action:
value 1.
User response:
249
ERZ035048I ERZ035053E
Use the accompanying messages from CICS and from
the PPC gateway to determine the cause of the
Destination:
stderr
Destination:
stderr
ERZ035051E No server name has been specified
ERZ035048I Server serverName has been enabled

successfully
Explanation:
The PPC gateway serverName was enabled for full
operations.
System action:
User response:
None
Destination:
stderr
ERZ035049E Server serverName could not be
changed to multi-user mode
Explanation:
PPC gateway serverName was unable to be changed
from single-user mode to multi-user mode, using the
tkadmin clear exclusiveauthority command.
problem. The PPC gateway writes its messages to a file
msg).
System action:
value 1.
User response:
Use the accompanying messages from CICS and from
the PPC gateway to determine the cause of the
problem. Shut down the server (using, for example the
cicsppcgwyshut command), correct the problem and
retry command.
Destination:
stderr
ERZ035050I Server serverName has been started
successfully
Explanation:
PPC gateway serverName was started successfully
and is ready for use.
Explanation:
When a PPC gateway is cold started a server name
must be specified explicitly. The contents of the
environment variable $CICS_PPCGWY_SERVER are
not used.
System action:
value 1.
User response:
Retry the command specifying the name of a PPC
gateway.
Destination:
stderr
ERZ035052W The subsystem subsystemName for
server serverName cannot be found
Explanation:
The command you have entered was unable to find the
subsystem entry subsystemName for PPC gateway
serverName and has assumed that it was already
deleted. Accompanying messages can possibly identify
the cause of the problem.
System action:
User response:
If the subsystem does not exist then no action is
needed. If the subsystem exists correct any problems
and retry the command or you can encounter problems
later if you create a new PPC gateway with the same
ShortName as server serverName.
Destination:
stderr
ERZ035053E The server serverName could not be
destroyed
Explanation:
The command you have entered was unable to destroy
the PPC gateway serverName completely.
problem.
System action:
value 1.
System action:
User response:
the problem. If necessary, correct the problem and retry
the command.
User response:
None
Destination:
stderr
250
ERZ035054I ERZ035060I
ERZ035054I The subsystem entry for server
serverName has been removed
Explanation:
The subsystem details of PPC gateway serverName
were deleted.
System action:
User response:
None
Destination:
stderr
stderr
ERZ035058W Restart file fileName could not be
found
Explanation:
The PPC gateway restart file fileName does not exist.
Since the command you have entered is attempting to
destroy a PPC gateway this is not a problem. The most
likely causes of this are either that you are destroying a
server that was already destroyed or that you are
destroying a server that was never started.
System action:
ERZ035055W The subsystem entry for server

serverName has not been removed
User response:
None
Explanation:
The subsystem entry for server serverName was not
removed because it is associated with a different server.
Accompanying messages give more information about
the problem.
Destination:
stderr
System action:
User response:
None
Destination:
stderr
ERZ035056W Server serverName was not found in
GSD
Explanation:
There is no entry for PPC gateway serverName in the
Gateway Server Definitions (GSD). This is not a
problem because the command you have entered is
attempting to destroy the server.
System action:
User response:
None
Destination:
stderr
ERZ035057I Server serverName has been removed
from GSD
Explanation:
PPC gateway serverName was deleted from the
Gateway Server Definitions (GSD).
System action:
ERZ035059W Restart file fileName could not be

removed
Explanation:
The PPC gateway restart file fileName was unable to
be deleted. Since the command you have entered is
attempting to destroy a PPC gateway this is not a
serious problem. If at a later stage you wish to create a
new PPC gateway with the same name as the one you
have just destroyed, you encounter problems because
restart file fileName does not match the new server.
System action:
User response:
Check the existence and access permissions for the file.
If necessary, log on with sufficient authority and delete
the file.
Destination:
stderr
ERZ035060I Restart file fileName has been
removed
Explanation:
The command you have entered has deleted PPC
gateway restart file fileName.
System action:
User response:
None
Destination:
stderr
User response:
None
Destination:
251
ERZ035061I ERZ035067E
ERZ035061I Usage: cicsppcgwydestroy { -? | [-v]
serverName }
ERZ035065W Server directory directoryName could

not be removed
Explanation:
This is the usage message for the cicsppcgwydestroy
command.
Explanation:
The PPC gateway directory directoryName and its
contents were unable to be deleted. Since the
command you have entered is attempting to destroy a
PPC gateway this is not a problem.
System action:
User response:
Destination:
stderr
ERZ035062E Unable to destroy active server
serverName
Explanation:
The command you have entered has attempted to
destroy PPC gateway serverName. This was
unsuccessful because the server is currently running.
System action:
value 1.
User response:
Ensure that you are destroying the correct PPC
gateway. If the server name is correct shut it down
(using, for example the cicsppcgwyshut command) and
retry the command.
Destination:
stderr
ERZ035063E Logical volume volumeName does
not exist
Explanation:
A PPC gateway requires logical volume volumeName
in order to log recoverable information. This logical
volume does not exist. Accompanying messages give
more information about the cause of the the problem.
System action:
value 1.
User response:
Create logical volume volumeName and retry the
command. If the logical volume was created on a
volume group other than the default group, then the
environment variable CICS_PPCGWY_VG needs to be
exported to reference this new volume group. e.g : if the
logical volume was created on vg01, then export
CICS_PPCGWY_VG=vg01 before retrying the
command.
Destination:
stderr
252
System action:
User response:
No action is necessary, but if you wish to clean up, log
on with sufficient authority and delete directory
directoryName (using, for example the rm -rf
command).
Destination:
stderr
ERZ035066I Usage: cicssmitppcgwy { -s
serverName | -e } processId
Explanation:
This is the usage message for the cicssmitppcgwy
command. Do not run this command from the command
line; it is to be invoked only by the system
administration interface.
System action:
value 1.
User response:
If you do not know which command to use, please refer
to the CICS documentation.
Destination:
stderr
ERZ035067E Unable to save name of PPC gateway
serverName into fileName
Explanation:
The command tried to write the name of the PPC
gateway serverName into file fileName but was
unsuccessful.
System action:
value 1.
User response:
Check that you have permission to create fileName
and that the file system is not full. Correct the problem
Destination:
stderr
ERZ035068E ERZ035074E
ERZ035068E You have not selected a PPC gateway
Explanation:
You have not selected a PPC gateway to work with.
System action:
value 1.
User response:
Select a working PPC gateway and retry the command.
Destination:
stderr
ERZ035069E Server name must be specified on a
cold start
Explanation:
You have tried to cold start a PPC gateway, without
specifying a server name. On a cold start all of the the
PPC gateways recoverable information is lost so, to
help ensure that the wrong server is not cold started,
the server name must be specified.
System action:
value 1.
User response:
Retry the command with the server name coded.
Destination:
stderr
ERZ035070E Usage: cicsppcgwyupdate { -n
newServerName -o oldServerName [-p
password] [-v] [-I]
Explanation:
This is the usage message for the cicsppcgwyupdate
command. Do not run this command from the command
line; it is to be and invoked only by the system
administration interface.
System action:
value 1.
User response:
If you do not know which command to use, please refer
to the CICS documentation.
Destination:
stderr
ERZ035071E Unable to update details of server
serverName
Explanation:
PPC gateway serverName. Accompanying messages
System action:
value 1.
User response:
errors.
Destination:
stderr
ERZ035072W Server serverName has already been
run
Explanation:
The command you have entered is going to modify the
details of PPC gateway serverName. This action
means that any of the PPC gateways recoverable
information is lost and, once updated, the server needs
to be cold started.
System action:
User response:
None
Destination:
stderr
ERZ035073E Server serverName has already been
run
Explanation:
The command you have entered attempted to modify
the details of PPC gateway serverName. This server
was previously run; if the command is allowed to
continue, all of the PPC gateways recoverable
information is lost.
System action:
value 1.
User response:
If you still want to modify the details of the PPC
gateway retry the command using the -I flag to ignore
errors.
Destination:
stderr
ERZ035074E Unable to rename server
oldServerName as newServerName as
newServerName already exists
Explanation:
The command you have entered attempted rename
PPC gateway oldServerName as newServerName.
Because PPC gateway newServerName is defined in
the Gateway Server Definitions (GSD), allowing this
253
ERZ035075W ERZ035082E
operation to continue causes PPC gateway
newServerName to lose all of its recoverable
information.
System action:
value 1.
User response:
If you still want to modify the details of the PPC
gateway retry the command using the -I flag to ignore
errors.
Destination:
stderr
ERZ035075W
Resource resourceName was not

recognized from the default Gateway
Server Definition (GSD).

the Planning and Installation Guide for more information
on system resources.
Destination:
stderr
ERZ035080E Unable to add environmentString to
the environment
Explanation:
The command you entered tried to add
environmentString to its environment but failed to do
so.
System action:
Explanation:
The resource specified, was not found in the default
Gateway Server Definition (GSD).
User response:
Check your system is not fully loaded, as this often is
the result of a lack of processing memory. Check also
that you have installed your system correctly.
System action:
Processing continues using the default values.
Destination:
stderr
User response:
Check that the default entry exists in the Gateway
Server Definitions (GSD). Retry the command specifying
the correct resource.
ERZ035081I Waiting for server serverName to

initialize.
Destination:
stderr
ERZ035078 E Usage: cicsppcgwydbadmin -s
server {-P | [[attribute=<value>]...]}
Explanation:
This is the usage message for cicsppcgwydbadmin .
The command is not expected to be run from the
command line as it is a CICS internal function.
System action:
The command terminates with a return code of 1.
User response:
Do not run the cicsppcgwydbadmin command from the
command line.
Destination:
stderr
ERZ035079E Not enough memory for operation
Explanation:
cicsppc tried to access some memory for its own
System action:
User response:
254
Explanation:
The server serverName was started asynchronously
and this message is issued while the command you
have entered waits for it complete the first stage of its
initialisation.
System action:
User response:
None
Destination:
stderr
ERZ035082E PPC gateway operation opCode
failed with error (errorCode) ErrorText
Explanation:
While executing cicppcgwy, a CICS Toolkit error
occurred that prevents the operation from completing
succesfully.
System action:
The command halts its attempt to create the current
PPC file and skip to the next stage.
User response:
Use the error code and text in the message to identify
the cause of the failure and correct the error.
Destination:
stderr
ERZ036003E ERZ036052W
ERZ036003E You must be logged on as root on
UNIX or as Administrator on Windows
NT
Explanation:
You attempted to run a command with insufficient
authority. On UNIX you must be logged on as root. On
Windows NT you must be logged on to a userid that is
a member of the cicsgroup or Administrators groups.
System action:
The command abnormally terminates returning the
value 1.
User response:
Log on correctly and retry the command.
ERZ036009W Waiting for lock

Explanation:
A server command requires a server lock to be taken however, the lock is already being held by another user.
System action:
The command loops until the lock can be taken.
User response:
None
Destination:
stderr
ERZ036034E Unable to execute executableName
Destination:
stderr
Explanation:
The command was unable to execute
executableName.
ERZ036007E Unable to start server serverName
System action:
Command abnormally terminates returning the value 1.
Explanation:
The Server serverName was unable to be started.
System action:
value 1.
User response:
Destination:
stderr
ERZ036008E Unable to access server definitions as
locked with file fileName
Explanation:
A CICS administration command was entered that must
secure a server definitions lock. However, the lock for
this server was already taken by another user. This can
possibly mean that the server is currently running, or
some other command or process is administering the
server definitions, or the lock was taken by a command
or process that subsequently terminated abnormally,
leaving the lock (this happens if, for example, the
machine is shut down while the server is running or
while administration commands are in progress).
System action:
The command exits returning the value 1.
User response:
If there are other CICS administration commands in
progress then wait for them to finish and retry the
command. Otherwise remove the lock file specified in
the message text and retry the command.
Destination:
stderr
User response:
Check that the executable is in a directory that is
named in your PATH variable, and that you have
permission to execute it.
Destination:
stderr
ERZ036050E Unable to contact host hostName
Explanation:
An operation to be executed on remote machine
hostName failed because the machine was unable to
be contacted.
System action:
User response:
Determine cause of communication failure, reestablish
contact with machine and retry command.
Destination:
stderr
ERZ036052W Lock file fileName was not found
Explanation:
The lock file fileName, used for locking a server,
cannot be removed during an unlock procedure.
System action:
User response:
The file was not supposed to be present, though this
does not prevent processing from continuing. The
server is left in an unlocked state.
Destination:
stderr
255
ERZ036053E ERZ036126I
ERZ036053E Unable to create lock file fileName
Explanation:
cannot be created. Accompanying messages identify
the exact cause of the problem.
System action:
User response:
Check both that you have permission to create files in
the following directories (and their sub-directories) and
that they are available:
v /var/cics_servers/SSD
v /var/cics_servers/GSD
See accompanying messages for further information.
Destination:
stderr
ERZ036054E Unable to remove lock file fileName
Explanation:
cannot be removed during a lock or unlock procedure.
Accompanying messages identify the exact cause of the
problem.
System action:
User response:
Check that you have permission to remove files in the
following directories (and their sub-directories) and that
they are available:
v /var/cics_servers/SSD
v /var/cics_servers/GSD
See accompanying messages for further information.
Destination:
stderr
ERZ036060W Subsystem definition for ShortName
shortName is already used by server
serverName
Explanation:
The ShortName attribute of a server must be unique
because it is used to generate the subsystem definition
name. shortName is already used by server
serverName.
System action:
User response:
Specify a unique ShortName value and retry the
command.
256
Destination:
stderr
ERZ036083E Unable to create directory
directoryName
Explanation:
It was not possible to create server directory
directoryName.
System action:
User response:
Check the existence and permissions on all the
directories named in the path of the directory being
created. You as an administrator must be in group cics,
and group cics must have read and execute permission
on all parent directories, and also write permission to
/var/cics_servers and to /var/cics_servers/SSD (GSD
if the command applies to a PPC gateway rather than a
SFS) and its sub-directories. See accompanying
messages for further information. Correct the problem,
Destination:
stderr
ERZ036084E Unable to change access permissions
on directory directoryName
Explanation:
A CICS command is unable to change the access
permissions on directory directoryName. Either the
directory does not exist, or you do not have the required
privileges to change its ownership.
System action:
User response:
created. You, as an administrator, must be in group cics,
and group cics must have read and execute permission
on all parent directories, and also write permission to
/var/cics_servers and to /var/cics_servers/SSD (GSD
if the command applies to a PPC gateway rather than a
SFS) and its sub-directories. See accompanying
messages for further information. Correct the problem,
Destination:
stderr
ERZ036126I Directory directoryName created
Explanation:
The directory directoryName was created.
System action:
User response:
ERZ036139E ERZ036149E
None
None
Destination:
stderr
Destination:
stderr
ERZ036139E Internal error in function

functionName
ERZ036147E Unable to access details on user

userId
Explanation:
An internal error has occurred in the specified function.
Explanation:
The command you entered was unable to access
details on user userId. This was probably because the
user does not exist. Previous messages identify the
exact problem.
System action:
value 1.
User response:
Destination:
stderr
ERZ036140E The server serverName cannot be
reached.
Explanation:
The server does not exist.
System action:
value 1.
User response:
Ensure you are trying to use a server that exists. Check
previous messages for any other errors.
Destination:
stderr
ERZ036141E Usage: cicspingserver serverName
Explanation:
You entered the cicspingserver command incorrectly.
System action:
value 1.
User response:
Retry the command using the correct syntax.
System action:
value 1.
User response:
Ensure that user userId exists and retry the command.
Destination:
stderr
ERZ036148W Directory directoryName is not
accessible by user userId or does not
exist
Explanation:
Either directoryName is not readable, writable and
executable by userId or does not exist.
System action:
User response:
None
Destination:
stderr
exist
Explanation:
executable by userId or it does not exist.
Destination:
stderr
System action:
value 1.
ERZ036146W Unable to access details on user

userId
User response:
Ensure directoryName exists and is readable, writable
and executable by userId.
Explanation:
exact problem.
Destination:
stderr
System action:
User response:
257
ERZ036150E ERZ036171I
ERZ036150E Unable to change ownership of
keytab file fileName to user userId
Explanation:
An attempt at changing the owner of fileName to
userId was unsuccessful. Previous messages identify
the exact problem.

User response:
Use accompanying to determine the cause of the
Destination:
stderr
System action:
value 1.
ERZ036169E Usage: cicsdefaultservers { -? | [ -s |

-c | -p ] }
User response:
Previous messages identify the problem.
Explanation:
You entered the cicsdefaultservers command incorrectly.
Destination:
stderr
System action:
value 1.
ERZ036152E Server serverName started, but has

not been initialized
User response:
Retry the command using the correct syntax. See the
more information.
Explanation:
The Server serverName was started but was unable to
be initialized.
System action:
User response:
Use any previous messages to help identify the
problem. The server must be shut down and restarted
before it can be used.
Destination:
stderr
ERZ036156E Unsuccessful attempt at changing
owner of fileName to userId
Explanation:
At attempt at changing the ownership of file or directory
fileName to user userId was unsuccessful.
System action:
value 1.
User response:
Make sure fileName exists and is local to the machine
(it cannot be a mounted directory). Retry the command.
Destination:
stderr
ERZ036157E Subsystem definition
subsystemName cannot be found
Explanation:
A subsystem definition for subsystemName was not
found. The most likely reason for this is that the server
name was entered incorrectly, or the subsystem
definition was prematurely deleted. Accompanying
messages identify the exact cause of the problem.
System action:
258
Destination:
stderr
ERZ036170E Unable to install server definitions
fileName
Explanation:
The cicsdefaultservers command attempted to install a
default version of the file fileName but the copy failed.
System action:
The command attempts to continue, but a failure return
code is given on command completion.
User response:
Check to see if the specified file exists. If the file
already exists no further action from this command is
required but to ensure no other commands fail check
the access permissions on the file. If the file does not
exist check that you have permission to write to the
directory and retry the command.
Destination:
stderr
ERZ036171I The following server definitions may
need migrating fileName
Explanation:
The cicsdefaultservers command attempted to install
new versions of the default server definitions but they
already exist. Some migration is possibly necessary to
upgrade the existing server definitions to the current
CICS release.
System action:
The command terminates normally returning the value
0.
User response:
ERZ036188I ERZ036202E
If you have not already done so, migrate the specified
stanza files using the cicsmigrate migration tool.
System action:
Processing continues and rebuilds the archive directory.
Destination:
stderr
User response:
None. The archive directory is rebuilt.
ERZ036188I Usage: cicsdefaultservers { -? | [ -s | -c

| -p ] }
Explanation:
This is the usage message for the cicsdefaultservers
command.
System action:
User response:
Destination:
stderr
ERZ036191E Both primaryRestartFile and
backupRestartFile are missing for
server serverName
Explanation:
The server restart files were unable to be found.
System action:
value 1.
User response:
On an auto start of a server at least one of the restart
files must be available. If neither restart file is available,
you need to cold start (initialize).
Destination:
stderr
ERZ036192W Restart file restartFileName is
missing for server serverName
Explanation:
The restart file restartFileName for server serverName
was unable to be found.
Destination:
stderr
ERZ036196E The archives directory directoryName
for server serverName does not exist
Explanation:
The archives directory for the server does not exist.
System action:
value 1
User response:
Retry the command specifying the -I flag (ignore errors),
which causes the directory to be rebuilt.
Destination:
stderr
ERZ036198I Restart files located for server
serverName
Explanation:
The restart files for the server were located.
System action:
User response:
None
Destination:
stderr
ERZ036200I Archives directory located for server
serverName
Explanation:
The archives directory for the server were located.
System action:
System action:
Processing continues using the other restart file.
User response:
None
User response:
None. The other restart file is rebuilt during server
startup.
Destination:
stderr
Destination:
stderr

running
ERZ036195W The archives directory directoryName

Explanation:
The attempted operation failed because a Server of the
same name is already running
Explanation:
The archives directory for the server does not exist but
is rebuilt.
System action:
value 1.
259
ERZ036203E ERZ036207E
User response:
If necessary, shut down the server of the same name
and restart the server.

msg).
Destination:
stderr
System action:
value 1.
ERZ036203E Unable to create logical volume

volumeName for server serverName
User response:
determine the cause of the problem. On Windows NT
msg file by using the cicsname serversdir command.
Shut down the server (using, for example either the
cicssfsshut or cicsppcgwyshut command), correct the
Explanation:
The command you have entered was unable to create
logical volume volumeName on an operating system
logical volume. Accompanying messages identify the
exact cause of the problem.
System action:
value 1.
Destination:
stderr
User response:
Use the accompanying CICS and server messages to
ERZ036206I Initialized logical volume volumeName

initialized for logging by server
serverName
Destination:
stderr
ERZ036204I Created logical volume volumeName
for server serverName
Explanation:
The command you have entered has successfully
created logical volume volumeName on an operating
system logical volume. This is used by server
serverName for logging.
System action:
User response:
None
Destination:
stderr
ERZ036205E Unable to initialize logical volume
volumeName for logging by server
serverName
Explanation:
The Server serverName unsuccessfully attempted to
initialize logical volume volumeName so that it can be
used to store log data, using the tkadmin init logvol
command. Accompanying messages identify the exact
cause of the problem. The server writes its messages to
a file called msg under the varDir/cics_servers
directory structure in a sub-directory based upon its
name (for example for a SFS named
/.:/cics/sfs/default the full path of the message file
is varDir/cics_servers/SSD/cics/sfs/default/msg and
for a PPC gateway named /.:/cics/ppc/gateway/
260
Explanation:
Logical volume volumeName was successfully
initialized and can be used to store log data for server
serverName.
System action:
User response:
None
Destination:
stderr
ERZ036207E Unable to create log file logFileName
Explanation:
When trying to create log file logFileName so it can be
used to store the recoverable data generated by server
serverName, using the tkadmin create logfile
command, the command you have entered has
encountered a problem. Accompanying messages
identify the exact cause of the problem. The server
writes its messages to a file called msg under the
varDir/cics_servers directory structure in a
SFS named /.:/cics/sfs/default the full path of the
message file is varDir/cics_servers/SSD/cics/sfs/
default/msg and for a PPC gateway named
/.:/cics/ppc/gateway/opencics the full path of the
message file is varDir/cics_servers/GSD/cics/ppc/
gateway/opencics/msg).
System action:
value 1.
User response:
ERZ036208I ERZ036212E
Shut down the server (using, for example either the
Destination:
stderr
ERZ036208I Created log file logFileName for server
serverName
Explanation:
created log file logFileName so it can be used to store
the recoverable data generated by server serverName.
System action:
User response:
None
Destination:
stderr
ERZ036209E Unable to access logical volume
volumeName for server serverName
ERZ036210I Server serverName has been

initialized
Explanation:
Server serverName is ready to process requests.
System action:
User response:
None
Destination:
stderr
ERZ036211E Unable to query media archive setting
Explanation:
The command you have entered is unable to query the
media archive setting of server serverName, using the
tkadmin query mediaarchiving command. The server
default/msg)
Explanation:
The command you have entered is unable to obtain
information about logical volume volumeName which
stores log data for server serverName, using the
tkadmin query logvol command. The most likely reason
for this is that you are trying to auto start a server that
was never started. The server writes its messages to a
example for a SFS named /.:/cics/sfs/default the
full path of the message file is varDir/cics_servers/
SSD/cics/sfs/default/msg and for a PPC gateway
named /.:/cics/ppc/gateway/opencics the full path of
the message file is varDir/cics_servers/GSD/cics/ppc/
gateway/opencics/msg).
System action:
value 1.
System action:
value 1.
ERZ036212E Unable to enable media archiving for

server serverName
User response:
Shut down the server (using, for example, either the
Destination:
stderr
User response:
Shut down the server (using, for example, the
cicssfsshut command), correct the problem and retry the
command.
Destination:
stderr
Explanation:
The command you have entered was unable to enable
the archiving of log records for server serverName,
using the tkadmin enable mediaarchiving command.
The server writes its messages to a file called msg under
default/msg)
System action:
value 1.
User response:
261
ERZ036213I ERZ036218E
Shut down the server (using, for example the
command.

Shut down the server (using, for example, the
command.
Destination:
stderr
Destination:
stderr
ERZ036213I Enabled media archiving for server

serverName
ERZ036216I Disabled media archiving for server

serverName
Explanation:
Server serverName archives log records.
Explanation:
Server serverName not archives log records.
System action:
System action:
User response:
None
User response:
None
Destination:
stderr
Destination:
stderr
ERZ036214W Need to backup server serverName

for media archiving to be effective
ERZ036217E The RPC error message is

errorMessage and RPC return code is
returnCode
Explanation:
Media archiving was just enabled on a server that
previously ran with it disabled. However, until the server
is subsequently backed up (by using the tkadmin
backup command) we do not have an image to restore
to.
System action:
User response:
Back up the server.
Destination:
stderr
ERZ036215E Unable to disable media archiving for
server serverName
Explanation:
The command you have entered was unable to stop the
archiving of log records for server serverName, using
the tkadmin disable mediaarchiving command. The
server writes its messages to a file called msg under the
default/msg)
System action:
value 1.
User response:
262
Explanation:
While attempting to communicate with a server an error
occurred that prevented the operation from completing
successfully.
System action:
value 1.
User response:
Ensure you are trying to use a server that exists. Check
previous messages for any other errors.
Destination:
stderr
ERZ036218E Usage: cicsgetbindingstring
serverName
Explanation:
The program must be called with exactly one parameter.
System action:
value 1.
User response:
Issue the command specifying the name of the server
for which the binding string is required.
Destination:
stderr
ERZ036219E ERZ036226E
ERZ036219E Unable to find server serverName
Explanation:
cicsgetbindingstring was unable to find binding
information for server serverName.
Explanation:
CICS tried to allocate some memory for a process but
was unable to do so.
System action:
value 1.
System action:
User response:
Check that the server is running.
Destination:
stderr
ERZ036220I Usage: cicsgetbindingstring
serverName
Explanation:
This is the usage message for the cicsgetbindingstring
command.
System action:
The command completed returning the value 0.
User response:
None.
Destination:
stderr
ERZ036221E Unable to read file fileName, errno
errorNumber
Explanation:
The cicsdefaultservers command attempted to read the
file fileName, but the command failed.
System action:
User response:
Check you have the necessary permissions to read the
file. Check also that the file is not corrupted. This error
can possibly indicate that CICS is not installed properly.
Destination:
stderr
ERZ036222W Unable to change details of file
fileName, errno errorNumber
Explanation:
An attempt at changing the owner of fileName to user
errorNumber failed.
System action:
The command can terminate abnormally.
User response:
Examine the value of errno to determine what the exact
problem is.
Destination:
stderr
User response:
Check also that your paging space is adequate. See the
Planning and Installation Guide for more information on
system resources.
Destination:
stderr
ERZ036224E Unable to close file fileName
Explanation:
CICS tried to close the file fileName but was unable to
do so. This is possibly because the file was corrupted or
because a spurious signal interrupted the process.
System action:
User response:
Try the command again. If the problem persists check
the installation of the CICS system.
Destination:
stderr
ERZ036225E Server operation opCode failed with
error (errorCode) ErrorText
Explanation:
While attempting to commincate with a server an error
occurred that prevented the operation from compleing
succesfully.
System action:
The error is returned to the calling command.
User response:
Destination:
stderr
ERZ036226E An RPC operation opCode failed with
Explanation:
While attempting to communicate with a server error
occurred that prevented the operation from completing
successfully.
System action:
The error is returned to the calling command.
User response:
263
ERZ036227E ERZ036233I
Destination:
stderr
ERZ036227E Unable to locate the Server
serverName
Explanation:
The current command was unable to locate the server
identified using the Cell Directory Services (CDS).
System action:
If an error occurred, an additional error message is
logged with exact details of the failure.
User response:
Verify that the server exists.
Destination:
stderr
ERZ036228E Unable to locate the Server
serverName
Explanation:
The current command was unable to locate the server
in the End-Point database.
System action:
If an error occurred, then an additional error message is
logged with exact details of the failure.
User response:
Verify that the server exists.
Destination:
stderr
the recoverable data generated by the server.

problem.
System action:
value 1.
User response:
Use the accompanying CICS and SFS messages to
Destination:
stderr
ERZ036231I Log file logfileName on server
serverName has been enabled.
Explanation:
Log file logfileName was enabled to store the
recoverable data generated by the server serverName.
System action:
User response:
None
Destination:
stderr
ERZ036232E Logical volumes on server
serverName could not be recovered.
Explanation:
Server serverName unsuccessfully attempted to bring
its data volumes up to date with information from its log
file. Accompanying messages identify the cause of the
problem.
ERZ036229E Server serverName contacted but

server not fully operational
System action:
value 1.
Explanation:
The current command was able to contact the server
identified in the message, but if failed to verify that the
server is fully operational.
User response:
System action:
The command cannot continue.
User response:
Verify that the server is running and has fully completed
its initialisation. When initialisation is fully complete
reissue the command.
Destination:
stderr
ERZ036230E Log file logfileName on server
serverName could not be enabled.
Explanation:
Log file logfileName on the server (SFS) serverName
was not able to be enabled. The log file is used to store
264
Destination:
stderr
ERZ036233I Logical volumes on server
serverName have been recovered.
Explanation:
The Structured File Servers (SFS) data volumes were
updated with the information in the servers log file.
System action:
User response:
None
Destination:
stderr
ERZ036234E ERZ037007E
ERZ036234E Unable to create directory dirName
Explanation:
The command you entered tried to create the specified
System action:
User response:
Check that the directory specified is in a directory that
you have permission to write to. Check also that there is
space in the file system.
Destination:
stderr
ERZ037001E Usage: cicssfsimport -i
schemaFileName -s serverName [-I] [-f
fileName [-x indexName ...] ...]
Explanation:
The command was invoked with incorrect arguments.
System action:
The command exits with return code 1.
User response:
Ensure the command is called with correct arguments.
Destination:
stderr
ERZ037002W Schema file schemaFileName does
not contain any details on file
fileName
Explanation:
There is no stanza entry for fileName in the schema file.
System action:
The cicssfsimport command continues.
User response:
Specify a file that does exist in the schema file.
Destination:
stderr
not contain details of index
indexName for file fileName
Explanation:
The entry for fileName in the schema file
schemaFileName contains no details of index
indexName.
System action:
The cicssfsimport command continues.
User response:
Specify an index for file fileName that exists in
schemaFileName.
stderr
ERZ037004E Destination file fileName does not
have write permission.
Explanation:
You have tried to write to destination file fileName, but
CALF has found that the files permissions do not allow
you to do so.
System action:
CALF continues.
User response:
Make sure that the destination file is writeable. You can
use the command EXEC CICS SET FILE(fileName)
ADDABLE to do this.
Destination:
stderr
ERZ037005E Destination file and source file do not
match.
Explanation:
CALF has detected that the source and destination files
are both local but have inconsistent file formats. This is
possibly because one file contains variable record
lengths but the other contains fixed record lengths, one
file is KSDS, the other is RRDS or because the record
lengths of the two files do not match.
System action:
CALF continues.
User response:
You are not able to import data between these files as
they are currently defined. Check to see if one file is of
variable length and the other of fixed length. Check that
they are both of the same type, (both KSDS, both
RRDS or both ESDS files). Check also the record
lengths of the two files are the same. If one of these
values is different across source and destination files
you need to redefine the destination file to be the same
as the source file.
Destination:
stderr
ERZ037007E Source record length shorter than
destination record length.
Explanation:
CALF has detected that the source file is remote and a
record was read from it whose length is less than the
record length of the fixed record length destination file.
The PAD field from the CALF transaction was not set to
Y.
System action:
CALF abnormally terminates with A373.
User response:
Destination:
265
ERZ037008E ERZ037013E
You either have to redefine the record length of the
destination file to be the same as that of the source file
or enable padding to occur by setting the PAD field to
Y.
Destination:
stderr
ERZ037008E Source record length longer than
destination record length.
Explanation:
The source file is remote and a record was retrieved
whose record length is longer than the record length of
the destination file.
System action:
User response:
You must define the record length of the destination file
to be consistent with that of the source file.
Destination:
stderr
ERZ037009E Source key does not match
embedded key in destination.
Explanation:
CALF has detected that the key retrieved from a source
record (which is used as the RIDFLD in a destination
record) does not match the embedded key in the
destination record.
System action:
ERZ037011E Unsuccessful attempt at opening file

fileName.
Explanation:
CALF was unable to open file fileName. This is
possibly because the file was not defined in the runtime
database, or you are not authorized to use the file.
Further information is possibly available in one of the
CICS message files.
System action:
CALF continues.
User response:
Check that the file is defined in the File Definitions.
Check also the Structured File Server Access Control
List (SFS ACL) for the file gives you the necessary
permissions to read the file. Check the CICS message
files for more information.
Destination:
stderr
ERZ037012E The value entered for SYNCPOINT is
not a valid number.
Explanation:
CALF has detected that you have entered a
SYNCPOINT value that is not a valid number. This field
can contain only digits ranging from zero to nine.
System action:
CALF continues.
User response:
Retry the transaction, specifying a valid number, such
that it only consists of digits ranging from zero to nine.
User response:
CALF is not able to write the record. Ensure that the
source and destination files have compatible definitions.
Destination:
stderr
Destination:
stderr
ERZ037013E The source and destination files have

not been opened successfully yet.
ERZ037010I Copy has completed successfully recordCount record(s) copied.
Explanation:
You have tried to import the source file (using function
key PF9 before you have opened the files using PF5.
Explanation:
CALF has successfully copied all records from the
source file to the destination file.
System action:
CALF continues.
User response:
You can press PF3 to end the CALF session and
continue with other CICS work, or press PF2 to import a
new file.
Destination:
stderr
266
System action:
CALF continues.
User response:
Ensure you use PF5 to open the files before you use
PF9 to import the source file. It is not enough to open
the files manually using for example CECI SET
FILE(fileName) OPEN; when CALF does this it also
performs extensive checking on both files.
Destination:
stderr
ERZ037014E ERZ037020E
ERZ037014E Error reading from file fileName.
(responseCode)
Explanation:
CALF has encountered an error while trying to read a
record from the source file. Further information is
possibly available in one of the CICS message files.
System action:
User response:
Check the CICS message files for further guidance on
resolving the problem.
Destination:
stderr
ERZ037015E Key already exists in the destination
file.
Explanation:
The destination files index is defined as unique and an
attempt was made to write a record to it with the same
key as an existing record.
System action:
User response:
Either set the DUPREC field to Y and try again or
allow duplicates on the index of the SFS file being
written to. If neither of these options is suitable, you
must abandon the import.
Destination:
stderr
ERZ037016E The source file fileName is not
browsable.
Explanation:
CALF has detected that you do not have the necessary
permissions to browse the source file fileName.
System action:
CALF continues.
User response:
Ensure that the file is browsable, by issuing the
command CECI SET FILE(fileName) BROWSABLE.
Destination:
stderr
ERZ037017E Value of DUPREC and PAD must be Y
or N.
Explanation:
CALF has detected that you have set the value of the
PAD or DUPREC field to be something other than Y
(for YES) and N (for NO).
CALF continues.
User response:
Ensure that the values in the PAD and DUPREC fields
contain only the characters Y or N.
Destination:
stderr
ERZ037018E Destination file must be local.
Explanation:
The file used as the destination is a remote file. Only a
local file can be used as the destination.
System action:
CALF continues.
User response:
Ensure that the file you wish to import data to resides
on your local machine.
Destination:
stderr
ERZ037019E Error writing to file fileName.
(responseCode)
Explanation:
CALF has encountered an error while trying to write a
record to the destination file. Further information is
System action:
User response:
Check the CICS message files for information regarding
the state of the source file and the Structured File
Server (SFS).
Destination:
stderr
ERZ037020E File fileName already exists on server
serverName.
Explanation:
The file fileName was already created on the server
serverName.
System action:
cicssfsimport exits with return code 3.
User response:
You can either supply the -I flag to the cicssfsimport
command, which ignores errors, or you can use the
Structured File Server (SFS) administration command to
destroy the file if you want to recreate it.
Destination:
stderr
System action:
267
ERZ037021W ERZ037033E
ERZ037021W File fileName already exists on
server serverName.
Explanation:
The file fileName was already created on the server
serverName.
System action:
User response:
If you believe that the file on the server is the wrong
one you can use the Structured File Server (SFS)
administration command to destroy the file.
User response:
Further messages identify the problem. Check the
cicssfsimport trace file for further information. Ensure
that the SFS is running and that you have sufficient
authority to modify the ACL controlling access to the file.
You possibly have to alter the ACL by hand; the
permissions required for the any_other and
unauthenticated ACL entry type are ADEIQRU.
Destination:
stderr
ERZ037031W Invalid PF or PA key pressed.
Destination:
stderr
Explanation:
You have pressed an undefined program function (PF)
or program attention (PA) key.
ERZ037022W Could not create index indexName

for file fileName.
System action:
CICS ignores the keystroke.
Explanation:
The index indexName was unable to be created for file
fileName.
User response:
Use a valid PF or PA key. Valid keys are displayed at
the bottom of the screen. You can also use the enter
key.
System action:
User response:
Check previous messages for any Structured File
Server (SFS) errors detailing why the index was unable
to be created.
Destination:
stderr
ERZ037032I CALF has ended normally. Ready for
next transaction.
Destination:
stderr
Explanation:
This is the message displayed when CALF terminates.
ERZ037027E Cannot read schema file fileName
System action:
CICS awaits the submission of the next transaction.
Explanation:
The schema file specified with the -i option was not
found, or was found but is empty, or was found but is
not readable by cicssfsimport.
System action:
User response:
Check that the schema file exists and is not empty.
Ensure that the file has the correct permissions to allow
read access. Retry the command using the correct
relative or absolute path of the schema file.
Destination:
stderr
ERZ037030E An unsuccessful attempt was made to
change the Access Control List (ACL)
for the SFS file fileName
Explanation:
cicssfsimport was unsuccessful when attempting to
modify the ACL for the SFS file fileName.
System action:
268
User response:
Submit another transaction.
Destination:
CALF user terminal
ERZ037033E Source and destination files are
identical.
Explanation:
CALF has detected that the source and destination file
names you have used are the same, and that the
source file is local, (the source file IS the destination
file).
System action:
CICS waits for new source/destination file names.
User response:
Ensure that if the source file is local then the name of
the destination file you use is different from it.
Destination:
CALF user terminal
ERZ037034E ERZ037056I
ERZ037034E Base name and file server are
identical for local files.
Explanation:
CALF has detected that the SFS file system and SFS
file name is identical for local source and destination
files.
System action:
CICS waits for new input.
User response:
Ensure that if the source file is local, then the SFS base
name and SFS file system name is different for this file
and the destination file.
Destination:
CALF user terminal
ERZ037035E Could not obtain details of SFS server
serverName
Explanation:
The Structured File Server (SFS) server serverName
was unable to be found in the SFS Server Definitions.
System action:
The command exits with return code 5
User response:
Check that the SFS server exists in the server
definitions. See any earlier messages for possible
causes of the problem.
Destination:
stderr
ERZ037038E You must specify a Primary Index
Name
Explanation:
You must specify a value for the Primary Index Name
attribute.
System action:
The command exits.
User response:
Specify a value for the Primary Index Name attribute.
Destination:
stderr
ERZ037039E You must specify Field Names for
Primary Index on file fileName
Explanation:
You must specify a value for the Field Names for
Primary Index attribute.
System action:
The command exits.
User response:
Specify a value for the Field Names for Primary Index
attribute.
Destination:
stderr
ERZ037040I Both files have been opened
successfully.
Explanation:
You requested that the two files specified were to be
opened. The command completed successfully and the
files were opened.
System action:
CALF continues.
User response:
To transfer the data from the source file to the
destination file press the PF9 key.
Destination:
stderr
ERZ037041E At least one filename must be
specified.
Explanation:
You pressed the PF5 key, Open Files, but did not
specify any files to open.
System action:
CALF continues.
User response:
Specify the file(s) you wish to open and retry the open
command.
Destination:
stderr
ERZ037055E Cannot save schema
schemaFileName in file fileName
Explanation:
The schema file schemaFileName was unable to be
written into file fileName.
System action:
User response:
Check that you have permission to create the file
fileName. See accompanying operating system error
messages for further information. Correct the problem
Destination:
stderr
ERZ037056I Usage: cicssmitschema {-s
schemaFileName | -e} processId
Explanation:
You entered the cicssmitschema command incorrectly.
System action:
269
ERZ037057E ERZ037063E
value 1.
User response:
Destination:
stderr
ERZ037057E You have not selected a schema file
Explanation:
You have not yet selected a schema file.
System action:
value 1.
User response:
Select a schema file before retrying the operation.
Destination:
stderr
ERZ037058W Secondary index indexName already
exists on file fileName.
Explanation:
The cicssfsimport command has encountered an index
that is already defined on file fileName.
System action:
The cicssfsimport command continues without adding
index indexName to file fileName.
ERZ037061W Decimal field name fieldName of file

fileName - field length must be 18
bytes
Explanation:
The cicssfsimport command has encountered a decimal
field with an explicit length set to a value other than 18
bytes. The length of a decimal field must be 18.
System action:
The length was set to 18 bytes, and the cicssfsimport
command continues.
User response:
None
Destination:
stderr
ERZ037062E Index indexName in file fileName
contains field name fieldName which
is not a name defined in fields Field 1
to Field 20
Explanation:
The cicssfsimport command has encountered a primary
or secondary index field name that is not one of the
names supplied as a name for Field 1 to Field 20.
System action:
The cicssfsimport command continues to check the rest
of the fields and then terminates abnormally returning
the value of 1.
User response:
This situation possibly arose because you are
attempting to define a number of indexes (including
existing ones) on an existing file. Ignore the message if
this is the case, as cicssfsimport continues and defines
other indexes you have specified. Or, repeat the
command with a new index name or another file name.
User response:
Correct the primary index field names to match those
names given to Field 1 to Field 20 that you want to form
the index.
Destination:
stderr
ERZ037063E File fileName - more than one

Primary Index Field Name supplied for
a Relative file
ERZ037059I Usage: cicssfsimport -i

schemaFileName -s serverName [-I] [-f
fileName [-x indexName ...] ...]
Explanation:
The cicssfsimport command was supplied with more
than one primary index field name for a relative file.
Relative files only have one primary index field.
Explanation:
This is the usage message for the cicssfsimport
command.
System action:
The command exits with return code 0.
Destination:
stderr
System action:
The cicssfsimport command terminates abnormally
returning the value of 1.
User response:
None
User response:
Correct the primary index field names. Only one can be
supplied, and this must be an unsignedInt32 field.
Destination:
stderr
Destination:
stderr
270
ERZ037064E ERZ037071E
ERZ037064E Primary Index Field Name
indexFieldName of file fileName is not
a field type of unsignedInt32
Explanation:
The cicssfsimport command has encountered a primary
index field for a relative file that is not a field type of
unsignedInt32.
System action:
User response:
Correct the field type for the primary index field selected
to be unsignedInt32 or select another primary index field
that has a type of unsignedInt32.
Destination:
stderr
User response:
Respecify the command correctly.
Destination:
stderr
ERZ037068I programName talking to: serverName
Explanation:
Indicates which server cicssdt is going to talk to.
System action:
User response:
None
Destination:
stderr
ERZ037069I Version [versionNumber]
ERZ037065E Secondary Index indexNumber of file

fileName, no field name given
Explanation:
The cicssdt version number.
Explanation:
The cicssfsimport command has encountered a
secondary index with no field name supplied.
System action:
System action:
User response:
None
Destination:
stderr
User response:
Correct the secondary index by supplying a field name
that forms the index.
ERZ037070I Contacting resourceName ...
Destination:
stderr
Explanation:
Displayed while cicssdt tries to contact the SFS.
ERZ037066E Schema File already exists
System action:
Explanation:
The cicsscdcreate command attempted to create the
empty schema file with the specified name, but a file
with that name already exists.
System action:
The cicsscdcreate command terminates abnormally.
User response:
Reexecute the command specifying a new schema file
name or remove the existing file if it is no longer
required.
Destination:
stderr
ERZ037067I Usage: cicsscdcreate { -? | -f
schemaFileName}
Explanation:
You entered the command incorrectly.
User response:
None
Destination:
stderr
ERZ037071E Failed to open file fileName
Explanation:
The cicssdt program was unable to open the specified
file.
System action:
cicssdt terminates.
User response:
Rerun cicssdt.
Destination:
stderr
System action:
271
ERZ037072I ERZ037079W
ERZ037072I Exit to command prompt. Use Ctrl-D or
exit to return ...
ERZ037076E A valid resourceName must be

provided with the optionName flag
Explanation:
The user has used the ! command to exit cicssdt.
Explanation:
An invalid or non-existent option was provided with the
optionName flag.
System action:
User response:
None
Destination:
stderr
System action:
cicssdt terminates.
User response:
None
Destination:
stderr
ERZ037073I Exiting on error ...

Explanation:
The -e option was used to invoke cicssdt and an error
was detected.
System action:
cicssdt terminates.
User response:
None
Destination:
stderr
ERZ037074W Unrecognized command
commandName ignored
Explanation:
An unrecognized command was caught in an cicssdt
script.
ERZ037077E You must provide a resourceName

either through the -s flag or by setting
the environment variables
CICS_XDT_SERVER or
CICS_SFS_SERVER
Explanation:
No server was provided so cicssdt was unable to start.
System action:
cicssdt terminates.
User response:
None
Destination:
stderr
System action:
ERZ037078E Usage: programName [-s

resourceName] [-i inputFileName] [-o
outputFileName] [-e] [-r] [-c
commandName ...]
User response:
None
Explanation:
The program was invoked incorrectly.
Destination:
stderr
System action:
cicssdt terminates.
ERZ037075E Command commandName not

recognized. Try help.
Explanation:
An unrecognized command was caught.
System action:
User response:
None
Destination:
stderr
User response:
Reinvoke the program correctly.
Destination:
stderr
ERZ037079W [Reached EOF in input file]
Explanation:
The end of an input file was encountered.
System action:
Processing continues in interactive mode.
User response:
None
Destination:
stderr
272
ERZ037080E ERZ037085I
ERZ037080E There is no available help for
command commandName
Explanation:
There is no help text for the specified command.
System action:
User response:
Specify a valid command.
Destination:
stderr
ERZ037081I [SFS Diagnostic Tool - Help] Valid
commands are: help (or ?)
commandName - setopen - list l create fileName - read fileName, (with
delete/update) - write fileName - empty
fileName - delete fileName - free
fileName - addindex fileName delindex fileName - info fileName server serverName - qtos
QSAMfileName - stof SFSfileName ftos SFSfileName - ! (ksh) - quit
Explanation:
Main online help panel.
System action:
User response:
None
Destination:
stderr
ERZ037082I [Command: create fileName] This
command creates a new file. Each
characteristic of the new file is
prompted for as needed. If no input is
made at the prompt a sensible default
is usually taken. However, the record
Field Name and Index Field Name use
an empty entry to indicate there are no
more fields. If q! is entered at any
prompt the command is terminated.
Explanation:
Online help for the create command.
System action:
User response:
None
Destination:
stderr
ERZ037083I [Command: write fileName] This

command inserts new records into an
existing SFS file. A shorthand format is
recognized for large records: A>>32
will fill the remainder of the field with
32 As.
Explanation:
Online help for the write command.
System action:
User response:
None
Destination:
stderr
ERZ037084I [Command: read fileName] Read
records from an SFS file. If the key is
to be taken as a string it must be
specified in the following format:
$Angus, ($stringName). You can
delete or update the record you have
just read. The update input behaves
the same as a write. If nothing is
entered for a field during an update the
field is left unaltered.
Explanation:
Online help for the read command.
System action:
User response:
None
Destination:
stderr
ERZ037085I [Command: list l searchString] This
command lists all the files on the
current server cicssdt is talking to. If
the l, (long), flag is used more
information is given on each file. A
search string can be used with or
without the long flag to list only certain
files, (l l cicstdq).
Explanation:
Online help for the list command.
System action:
User response:
None
Destination:
stderr
273
ERZ037086I ERZ037092I
ERZ037086I [Command: delete fileName] This
command deletes the specified file on
the current server cicssdt is talking to.
The setopen verb need not be used
for this command as delete will
temporarily turn on an exclusive open.
Explanation:
Online help for the delete command.
System action:
User response:
None
Destination:
stderr
ERZ037087I [Command: addindex fileName] This
command adds a secondary index to
the specified file. The setopen verb
need not be used for this command as
addindex will temporarily turn on an
exclusive open. Excluded keys are
currently not supported. If q! is
entered at any prompt the command is
terminated.
Explanation:
Online help for the addindex command.
System action:
User response:
None
Destination:
stderr
ERZ037088I [Command: delindex fileName] This
command deletes a secondary index
on the specified file. The setopen
verb need not be used for this
command as delindex will temporarily
turn on an exclusive open. If q! is
entered at any prompt the command is
terminated.
ERZ037089I [Command: empty fileName] This

command empties the specified file.
There are two types of empty available;
the Exclusive empty and the Shared
empty. The Exclusive is recommended
as it is quicker and cleans the whole
file. However, if the file is already open
the Shared empty will have to be used.
Explanation:
Online help for the empty command.
System action:
User response:
None
Destination:
stderr
ERZ037090I [Command: info fileName] This
command gives detailed information
about the specified file. It will also
show all the current Open File
Descriptors against it.
Explanation:
Online help for the info command.
System action:
User response:
None
Destination:
stderr
ERZ037091I [Command: free fileName] This
command attempts to close all the
open OFDs on the specified file.
(WARNING: Take care with this
command).
Explanation:
Online help for the free command.
System action:
Explanation:
Online help for the delindex command.
User response:
None
System action:
Destination:
stderr
User response:
None
Destination:
stderr
ERZ037092I [Command: server serverName] This

command changes the current server
to the new one specified. The complete
server name must be given.
Explanation:
Online help for the server command.
274
ERZ037093I ERZ037099I
System action:
User response:
None
ERZ037096I [Command: help (or ?) commandName]

This command gives general command
help or specific help for the specified
command.
Destination:
stderr
Explanation:
Online help for the help command.
ERZ037093I [Command: qtos QSAMfileName] This

command takes a QSAM file and
copies the records into an SFS file.
The SFS file must already exist.
Explanation:
Online help for the qtos command.
System action:
User response:
None
Destination:
stderr
ERZ037094I [Command: stof SFSfileName] This
command takes an SFS file and dumps
it to a flat file. Any type of SFS file with
any record format can be dumped. The
file can be reloaded using ftos.
Explanation:
Online help for the stof command.
System action:
User response:
None
Destination:
stderr
ERZ037095I [Command: ftos SFSfileName] This
command takes an SFS file and loads
it from a flat file. The file must have
been previously created from the stof
command.
Explanation:
Online help for the ftos command.
System action:
User response:
None
Destination:
stderr
System action:
User response:
None
Destination:
stderr
ERZ037097I [Command: !] Escapes to the
command prompt. Use Ctrl-D or exit to
return to the application.
Explanation:
Online help for the ! command.
System action:
User response:
None
Destination:
stderr
ERZ037098I [Command: setopen] This command
sets the characteristics of cicssdt
commands that involve opening files. If
a Transactional open is set cicssdt will
manage a client transaction for you.
The lock mode used during a read
can also be changed using this
command.
Explanation:
Online help for the setopen command.
System action:
User response:
None
Destination:
stderr
ERZ037099I [Command: quit] Exits the application.
If quit is not used at the end of a
input script, control will return to the
command prompt.
Explanation:
Online help for the quit command.
System action:
User response:
275
ERZ037100E ERZ037109I
None
Destination:
stderr
ERZ037100E TRPC initialization failed. Look for
communication errors
Explanation:
A TRPC initialization call failed.
System action:
cicssdt terminates.
User response:
Check server is up and running correctly.
Destination:
stderr
ERZ037102W (Server unavailable or non-existent)
Explanation:
The cicssdt program was unable to contact the specified
SFS.
System action:
User response:
Check the server is running and was correctly specified.
Destination:
stderr
ERZ037103I (Server OK)
Explanation:
The specified server responded.
System action:
User response:
None
Destination:
stderr
ERZ037104W [Command terminated. No Filename
Given]
Explanation:
No filename was supplied to the command.
System action:
User response:
Reissue the command with a valid filename.
Destination:
stderr
ERZ037105W [Command terminated. No Server

Name Given]
Explanation:
No server name was supplied to the command.
System action:
User response:
Reissue the command with a valid server name.
Destination:
stderr
ERZ037106E Failed to list files (Server:
serverName Error: SFSerror)
Explanation:
The call to the SFS failed.
System action:
The command returns with an error.
User response:
Check the SFS is still running.
Destination:
stderr
ERZ037107I No files found on server
Explanation:
No files were found on the SFS.
System action:
User response:
None
Destination:
stderr
ERZ037108E Failed to get OFD info (Server:
serverName File: fileName Error:
SFSerror)
Explanation:
System action:
User response:
Destination:
stderr
ERZ037109I [OFDs Left Untouched]
Explanation:
The user requested that no OFDs were to be closed.
System action:
276
ERZ037110E ERZ037117E
User response:
None
stderr
Destination:
stderr
ERZ037114E Failed to open QSAM definition file

(Server: serverName File: fileName
Error: errorNumber)
ERZ037110E Failed to add index (Server:

SFSerror)
Explanation:
The open call failed on the cicssdt QSAM definition file.
Explanation:
System action:
User response:
System action:
User response:
Check the file exists.
Destination:
stderr
Destination:
stderr
ERZ037115E Failed to open QSAM DFHCNV

template (Server: serverName File:
fileName Error: errorNumber)
ERZ037111W [Nothing Entered. Index Left

Untouched]
Explanation:
The open called failed on the QSAM DFHCNV template
file.
Explanation:
The user specified no index to delete.
System action:
User response:
None
Destination:
stderr
ERZ037112E Failed to delete index (Server:
SFSerror)
Explanation:
System action:
User response:
Destination:
stderr
ERZ037113E Failed to open log file (Server:
errorNumber)
Explanation:
The open call failed to create a new log file.
System action:
User response:
Check the file does not already exist.
Destination:
System action:
User response:
Destination:
stderr
ERZ037116E Failed to open default code pages
(Server: serverName Error:
errorNumber)
Explanation:
The code page conversion call failed to open at least
one of the specified code pages.
System action:
User response:
Check that the code pages are specified correctly.
Destination:
stderr
ERZ037117E Failed to find default code pages
(Server: serverName File: fileName)
Explanation:
No default code pages were able to be found in the
DFHCNV template file.
System action:
User response:
Check the file contains valid information.
Destination:
277
ERZ037118E ERZ037124E
stderr
The record read was not long enough to contain the

designated key.
ERZ037118E Bad length header read for QSAM

record (Server: serverName File:
fileName Record No.: recordNumber
Expected Length: expectedLength
Actual Length: actualLength)
System action:
Explanation:
An invalid record header was found in the QSAM file.
System action:
User response:
Destination:
stderr
ERZ037119E Bad variable length for QSAM record
Record No.: recordNumber Length:
recordLength)
Explanation:
An invalid record length was read. The record length
System action:
User response:
Destination:
stderr
ERZ037120E Bad record read from QSAM file
Record No.: recordNumber Expected
Length: expectedLength Actual
Length: actualLength)
Explanation:
An record of incorrect length was found in the QSAM
file.
System action:
User response:
Destination:
stderr
ERZ037121E QSAM record is too small for key
Record No.: recordNumber Key
Offset+Length: keyLength Record
Length: recordLength)
Explanation:
278
User response:
Destination:
stderr
ERZ037122E QSAM record is too small for data
Record No.: recordNumber Data
Position: dataOffset Record Length:
recordLength)
Explanation:
The record read was not long enough for the data
offset.
System action:
User response:
Destination:
stderr
ERZ037123E QSAM record is too big for the SFS
record (Server: serverName File:
SFS Record Length: SFSrecordLength
QSAM Record Length:
QSAMrecordLength)
Explanation:
The record read was bigger than the SFS record size.
System action:
User response:
Use an SFS file with larger records.
Destination:
stderr
ERZ037124E QSAM record size does not match the
SFS record. Record sizes must match
for fixed length SFS files. (Server:
serverName File: fileName Record
No.: recordNumber SFS Record
Length: SFSrecordLength QSAM
Record Length: QSAMrecordLength)
Explanation:
The record read did not match the the SFS record size.
System action:
User response:
Make sure the fixed record sizes match.
ERZ037125E ERZ037132E
Destination:
stderr
ERZ037125E QSAM record size is smaller than the
fixed SFS portion. Record sizes must
be at least as big as the fixed portion
of the SFS record. (Server:
serverName File: fileName Record
No.: recordNumber SFS Record
Length: SFSrecordLength QSAM
Record Length: QSAMrecordLength)
Explanation:
The record read was smaller than the fixed portion of
the SFS record.
System action:
User response:
Make sure the fixed record sizes match.
Destination:
stderr
ERZ037126E Failed to add record to SFS file
Error: SFSerror Record No.:
recordNumber)
User response:
None
Destination:
stderr
ERZ037129E Failed to open file (Server:
SFSerror)
Explanation:
System action:
User response:
Destination:
stderr
ERZ037130E Failed to get file info (Server:
SFSerror)
Explanation:
Explanation:
System action:
System action:
User response:
User response:
Destination:
stderr
Destination:
stderr
ERZ037131E Failed to get file index info (Server:

SFSerror)
ERZ037127E Failed to open QSAM file (Server:

errorNumber)
Explanation:
Explanation:
The open call failed on the specified QSAM file.
System action:
System action:
User response:
User response:
Destination:
stderr
Destination:
stderr
ERZ037128I Type in new letter to change value.
Just ENTER to leave as is ...
Explanation:
Advice text for the setopen command.
System action:
ERZ037132E Failed to close file (Server:

SFSerror)
Explanation:
System action:
User response:
279
ERZ037133E ERZ037140E
Destination:
stderr
ERZ037133E Memory allocation failed (Server:
errorNumber)
Explanation:
A memory allocation (malloc) call failed.
System action:
User response:
Check the operating system has available memory.
Destination:
stderr
ERZ037134E Failed to add record (Server:
SFSerror)
Explanation:
System action:
User response:
Destination:
stderr
ERZ037135E Failed to create file, (no fields
provided) (Server: serverName File:
fileName)
Explanation:
No fields were provided for the file record specification.
System action:
User response:
Reissue the command and provide at least one field.
Destination:
stderr
ERZ037136E Failed to create file, (max records is
zero) (Server: serverName File:
fileName)
Explanation:
The maximum number of records for the file was given
as zero.
Reissue the command and provide a maximum number

of records.
Destination:
stderr
ERZ037137E Failed to create file (Server:
SFSerror)
Explanation:
System action:
User response:
Destination:
stderr
ERZ037138E Failed to set key range (Server:
SFSerror)
Explanation:
System action:
User response:
Destination:
stderr
ERZ037139E Failed to read record (Server:
SFSerror)
Explanation:
System action:
User response:
Destination:
stderr
ERZ037140E Failed to delete record (Server:
SFSerror)
Explanation:
System action:
System action:
User response:
User response:
280
ERZ037141E ERZ037148E
Destination:
stderr
stderr
ERZ037141E Failed to update record (Server:

SFSerror)
ERZ037145E Failed to read record (Server:

SFSerror Record Number:
recordNumber)
Explanation:
Explanation:
The specified record number was unable to be read.
System action:
System action:
User response:
User response:
Destination:
stderr
Destination:
stderr
ERZ037142E Failed to delete file (Server:

SFSerror)
ERZ037146E Failed to write complete record

Error: errorNumber Record Number:
recordNumber Record Length:
recordLength Length Written:
lengthWritten)
Explanation:
System action:
User response:
Destination:
stderr
ERZ037143E Failed to empty file (Server:
SFSerror)
Explanation:
System action:
User response:
Destination:
stderr
ERZ037144E Failed to open flat file (Server:
errorNumber)
Explanation:
The cicssdt program was unable to open the specified
flat file.
System action:
User response:
Destination:
Explanation:
The specified record was unable to be written.
System action:
User response:
Check the flat file is not corrupt.
Destination:
stderr
ERZ037147E Failed to read record length (Server:
errorNumber Record Number:
recordNumber)
Explanation:
The specified record length was unable to be read.
System action:
User response:
Destination:
stderr
ERZ037148E Bad record length in record header
recordNumber Length Read:
lengthRead)
Explanation:
The specified record header contained invalid length
information.
281
ERZ037149E ERZ037155E
System action:
User response:
Destination:
stderr
ERZ037149E Failed to read complete record
recordNumber Record Length:
recordLength Length Read:
lengthRead)
Explanation:
The specified record was unable to be read.
System action:
User response:
Destination:
stderr
ERZ037150E Record too big for SFS record
recordNumber SFS Record Length:
SFSrecordLength Flatfile Record
Length: flatFileRecordLength)
Explanation:
The specified record is too big for the target SFS
record.
System action:
User response:
Destination:
stderr
ERZ037151E Record size is smaller than SFS fixed
record size (Server: serverName File:
fileName Error: errorNumber Record
Number: recordNumber SFS Fixed
Record Length: SFSfixedRecordLength
Flatfile Record Length:
flatFileRecordLength)
Explanation:
The specified record is too small for the target SFS
record.
Destination:
stderr
ERZ037152E Record size does not match SFS
record size (Server: serverName File:
Number: recordNumber SFS Record
Length: SFSrecordLength Flatfile
Record Length: flatFileRecordLength)
Explanation:
The specified record does not match the fixed SFS
record.
System action:
User response:
Destination:
stderr
ERZ037153E Failed to add record to SFS file
Error: SFSerror Record Number:
recordNumber)
Explanation:
System action:
User response:
Destination:
stderr
ERZ037154E Failed to open code pages
Explanation:
The iconv_open call failed.
System action:
The program returns with an error.
User response:
Ensure that code page translation is supported from
IBM-037 to ISO8859-1. Translate tables must be
prepared in advance.
Destination:
stderr
ERZ037155E Unexpected length lengthRead read
at record recordNumber
System action:
Explanation:
The cicsnetdata program failed to read the segment
length and flag bytes from the input.
User response:
System action:
282
ERZ037156E ERZ037163E
User response:
Ensure that the input is in netdata format.
Destination:
stderr

Destination:
stderr
ERZ037160I Control record: controlRecord
ERZ037156E Bad netdata segment length

segmentLength at record
recordNumber
Explanation:
The segment length is too small, it cannot be less than
3.
System action:
User response:
Destination:
stderr
ERZ037157E Excessive netdata segment length
segmentLength at record
recordNumber
Explanation:
The segment length is too big for the buffer.
System action:
User response:
Destination:
stderr
ERZ037158E Length error at record recordNumber
Explanation:
The data length read did not match the length given in
the segment length byte.
System action:
User response:
Destination:
stderr
ERZ037159E Control record eye-catcher is not
INMR at record recordNumber
Explanation:
The flag byte was set for a netdata control record, but
the beginning of the record did not contain INMR in
EBCDIC.
System action:
User response:
Explanation:
Identifies the control record, whose contents follow.
System action:
User response:
None
Destination:
stderr
ERZ037161W Data buffered at the end of file
Explanation:
The end of the input was found. One or more segments
of data are still buffered. The input was expected to end
with a last-segment of an INMR06 record.
System action:
User response:
Destination:
stderr
ERZ037162I Input records: inputRecordCount Control records: controlRecordCount Output records: outputRecordCount
Explanation:
Record counts. Control records are not added to the
output.
System action:
User response:
None
Destination:
stderr
ERZ037163E Data conversion incomplete at record
recordNumber
Explanation:
EBCDIC to ASCII conversion failed because the output
buffer was too short to hold the result.
System action:
User response:
None
Destination:
stderr
283
ERZ037164I ERZ037171W
ERZ037164I Description: netdataUnitDescription
ERZ037168W File fileName already exists
Explanation:
Describes a unit in a netdata control record.
Explanation:
The specified file already exists.
System action:
System action:
User response:
None
User response:
Decide whether or not the file is to be overwritten at the
next prompt.
Destination:
stderr
ERZ037165W Unexpected unit key unitKey at
record recordNumber
Explanation:
A unit in a netdata control record was not recognized.
The key is given in hexadecimal.
System action:
User response:
Destination:
stderr
ERZ037166W Bad description type descriptionType
in table
Explanation:
Internal error in cicsnetdata: the control record unit was
unable to be formatted.
Destination:
stderr
ERZ037169E File fileName has been destroyed,
please retry command after correcting
values.
Explanation:
The file fileName was half created when a value was
detected as being in error. This value must be corrected
by using the cicsupdate command and then retrying the
cicssfsimport command.
System action:
value 1.
User response:
Check the values in the schema file and update these
where they are incorrect, using the cicsupdate
command. Retry the cicssfsimport command.
Destination:
stderr
System action:
ERZ037170E File fileName could not be destroyed.
User response:
Explanation:
The file fileName was unable to be destroyed. Please
see SFS messages.
Destination:
stderr
ERZ037167I File number fileNumber
Explanation:
Control record INMR02 carries the file number within a
multiple file netdata stream. The cicsnetdata program
only supports one file. Multiple files are not separated.
System action:
User response:
None
Destination:
stderr
System action:
value 1.
User response:
Check SFS messages for more information.
Destination:
stderr
ERZ037171W Unable to connect to database (SQL
Error: SQLError)
Explanation:
The cicsddt program was unable to contact the
specified database.
System action:
User response:
Check the database is running and was correctly
specified.
284
ERZ037172I ERZ037179E
Destination:
stderr
ERZ037172I (Database OK)
Explanation:
The specified database responded.
System action:
User response:
None
Destination:
stderr
ERZ037173W [Command terminated. No Database
Name Given]
Explanation:
No database name was supplied to the command.
System action:
User response:
Reissue the command with a valid database name.
Destination:
stderr
ERZ037174W [Command terminated. No User
Name Given]
Explanation:
No database user was supplied to the command.
System action:
User response:
Reissue the command with a valid database user.
Destination:
stderr
ERZ037175E Failed to list tables (SQL Error:
SQLError)
Explanation:
An SQL error occurred while trying to list the database
tables.
System action:
User response:
Check the database is running.
ERZ037176I No tables found on database

Explanation:
No tables were found on the current database.
System action:
User response:
None
Destination:
stderr
ERZ037177E Failed to add index (SQL Error:
SQLError)
Explanation:
An SQL error occurred while trying to add the
secondary index.
System action:
User response:
Destination:
stderr
ERZ037178E Failed to delete index (SQL Error:
SQLError)
Explanation:
An SQL error occurred while trying to delete the
secondary index.
System action:
User response:
Destination:
stderr
ERZ037179E Failed to open log file (File: fileName
Error: errorNumber)
Explanation:
The open call failed to create a new log file.
System action:
User response:
Check the file does not already exist.
Destination:
stderr
Destination:
stderr
285
ERZ037180E ERZ037187E
ERZ037180E Failed to open QSAM definition file
(File: fileName Error: errorNumber)
ERZ037184E Failed to set up sqlda (SQL Error:

SQLError)
Explanation:
The open call failed on the QSAM definition file.
Explanation:
An SQL error occurred while trying to PREPARE or
DESCRIBE an SQL Data Area.
System action:
User response:
Destination:
stderr
ERZ037181E Failed to open QSAM DFHCNV
template (File: fileName Error:
errorNumber)
Explanation:
The open call failed on the QSAM DFHCNV template
file.
System action:
User response:
Destination:
stderr
ERZ037182E Failed to open default code pages
(Error: errorNumber)
Explanation:
The code page conversion call failed to open at least
one of the specified code pages.
System action:
User response:
Check that the code pages are specified correctly.
Destination:
stderr
ERZ037183E Failed to find default code pages
(File: fileName)
Explanation:
No default code pages were able to be found in the
DFHCNV template file.
System action:
System action:
User response:
Destination:
stderr
ERZ037185E Bad length header read for QSAM
record (File: fileName Record No.:
recordNumber Expected Length:
expectedLength Actual Length:
actualLength)
Explanation:
An invalid record header was found in the QSAM file.
System action:
User response:
Destination:
stderr
ERZ037186E Bad variable length for QSAM record
(File: fileName Record No.:
recordNumber Length: recordLength)
Explanation:
An invalid record length was read. The record length
System action:
User response:
Destination:
stderr
ERZ037187E Bad record read from QSAM file (File:
Expected Length: expectedLength
Actual Length: actualLength)
User response:
Explanation:
An record of incorrect length was found in the QSAM
file.
Destination:
stderr
System action:
User response:
286
ERZ037188E ERZ037194E
Destination:
stderr
ERZ037188E QSAM record is too small for key
recordNumber Key Offset+Length:
keyLength Record Length:
recordLength)
Explanation:
The record read was not long enough to contain the
designated key.
System action:
User response:
Destination:
stderr
ERZ037189E QSAM record is too small for data
recordNumber Data Position:
dataOffset Record Length:
recordLength)
Explanation:
The record read was not long enough for the data
offset.
System action:
User response:
Destination:
stderr
ERZ037190E QSAM record is too big for the
database record (File: fileName
Record No.: recordNumber SFS
Record Length: databaseRecordLength
QSAM Record Length:
QSAMrecordLength)
Explanation:
The record read was bigger than the database row size.
System action:
User response:
Use a database table with larger rows.
Destination:
stderr
ERZ037191E Failed to insert row into table (SQL

Error: SQLError)
Explanation:
An SQL error occurred while trying to insert a new row.
System action:
User response:
Destination:
stderr
ERZ037192E Failed to open QSAM file (File:
fileName Error: errorNumber)
Explanation:
The open call failed on the specified QSAM file.
System action:
User response:
Destination:
stderr
ERZ037193E Table tableName is not owned by
CICS or contains illegal column types
for CICS use
Explanation:
The specified table is not owned by the user cics or it
contains non-character column types.
System action:
User response:
Check the table has the correct attributes.
Destination:
stderr
ERZ037194E Failed to get table information (SQL
Error: SQLError)
Explanation:
An SQL error occurred while trying to gain table
information.
System action:
User response:
Destination:
stderr
287
ERZ037195E ERZ037202E
ERZ037195E Failed to create table because no
columns were provided
ERZ037199E Failed to delete table (SQL Error:

SQLError)
Explanation:
No columns were provided to create the new table.
Explanation:
An SQL error occurred while trying to delete the table.
System action:
System action:
User response:
Run the command again providing at least one column.
User response:
Destination:
stderr
Destination:
stderr
ERZ037196E Failed to create table (SQL Error:

SQLError)
ERZ037200E Failed to empty table (SQL Error:

SQLError)
Explanation:
An SQL error occurred while trying to create the table.
Explanation:
An SQL error occurred while trying to empty the table.
System action:
System action:
User response:
User response:
Destination:
stderr
Destination:
stderr
ERZ037197E Failed to read from table (SQL Error:

SQLError)
ERZ037201E Failed to open flat file (File: fileName

Error: errorNumber)
Explanation:
An SQL error occurred while trying to read from the
table.
Explanation:
The specified flat file was unable to be opened.
System action:
User response:
Destination:
stderr
ERZ037198E Failed to delete from table (SQL Error:
SQLError)
Explanation:
An SQL error occurred while trying to delete from the
table.
System action:
User response:
Destination:
stderr
288
System action:
User response:
Destination:
stderr
ERZ037202E Failed to read record (Error:
SQLerror Record Number:
rowNumber)
Explanation:
The specified row number was unable to be read.
System action:
User response:
Check the table contains valid information.
Destination:
stderr
ERZ037203E ERZ037209I
ERZ037203E Failed to write complete row (File:
fileName Error: errorNumber Row
Number: rowNumber Row Length:
rowLength Length Written:
lengthWritten)
Explanation:
The specified row was unable to be written.
System action:
Destination:
stderr
ERZ037207E Record too big for database record
(File: fileName Error: errorNumber
Record Number: recordNumber
Database Record Length:
databaseRecordLength Flatfile Record
Length: flatFileRecordLength)
User response:
Check the flat file is not corrupt.
Explanation:
The specified record is too big for the target database
record.
Destination:
stderr
System action:
ERZ037204E Failed to read record length (File:

Number: recordNumber)
Explanation:
The specified record length was unable to be read.
System action:
User response:
Destination:
stderr
ERZ037205E Bad record length in record header
(File: fileName Error: errorNumber
Record Number: recordNumber Length
Read: lengthRead)
Explanation:
The specified record header contained invalid length
information.
System action:
User response:
Destination:
stderr
ERZ037206E Failed to read complete record (File:
Number: recordNumber Record
Length: recordLength Length Read:
lengthRead)
User response:
Destination:
stderr
ERZ037208I [DB2 Diagnostic Tool - Help] Valid
commandName - list l - create
tableName - read tableName - write
tableName - empty tableName - delete
tableName - addindex tableName delindex tableName - info tableName database dbName - user userName qtod QSAMfileName - dtof tableName ftod tableName - ! (ksh) - quit
Explanation:
System action:
User response:
None
Destination:
stderr
ERZ037209I [Command: create tableName] This
command creates a new table. Each
characteristic of the new file is
prompted for as needed. If no input is
made at the prompt a sensible default
is usually taken. If q! is entered at any
prompt the command is terminated.
Explanation:
Online help for the create command.
Explanation:
The specified record was unable to be read.
System action:
System action:
User response:
None
User response:
Destination:
stderr
289
ERZ037210I ERZ037217I
ERZ037210I [Command: write tableName] This
command inserts new rows into an
existing table. A shorthand format is
recognized for large records: A>>32
will fill the remainder of the field with
32 As.
Explanation:
Online help for the write command.
System action:
User response:
None
Destination:
stderr
ERZ037211I [Command: read tableName] Read
records from a table. If the key is to be
taken as a number it must be specified
in the following format: #<Number>,
(#9). Hexadecimal keys can also be
specified using a prefix of 0x.
Explanation:
Online help for the read command.
System action:
User response:
None
Destination:
stderr
ERZ037212I [Command: list l searchString] This
command lists all the tables on the
current database. If the l, (long), flag
is used more information is given on
each table. A search string can be
used with or without the long flag to
list only certain tables, (l l CICS).
Explanation:
Online help for the list command.
System action:
User response:
None
Destination:
stderr
ERZ037213I [Command: delete tableName] This
command deletes the specified table
on the current database.
Explanation:
Online help for the delete command.
290
System action:
User response:
None
Destination:
stderr
ERZ037214I [Command: addindex tableName] This
command adds a secondary index to
the specified table. If q! is entered at
any prompt the command is
terminated.
Explanation:
Online help for the addindex command.
System action:
User response:
None
Destination:
stderr
ERZ037215I [Command: delindex tableName] This
command deletes a secondary index
on the specified table.
Explanation:
Online help for the delindex command.
System action:
User response:
None
Destination:
stderr
ERZ037216I [Command: empty tableName] This
command empties the specified table.
Explanation:
Online help for the empty command.
System action:
User response:
None
Destination:
stderr
ERZ037217I [Command: info tableName] This
command gives detailed information
about the specified table.
Explanation:
Online help for the info command.
System action:
ERZ037218I ERZ037225E
Online help for the dtof command.
User response:
None
System action:
Destination:
stderr
User response:
None
ERZ037218I [Command: database dbName] This

command attempts to change to a new
database. If the attempt fails control is
returned to the original database.
Explanation:
Online help for the database command.
System action:
User response:
None
Destination:
stderr
ERZ037219I [Command: user userName] This
command attempts to change the
current database user. If the attempt
fails control is returned to the original
user.
Explanation:
Online help for the user command.
System action:
User response:
None
Destination:
stderr
ERZ037220I [Command: qtod QSAMfileName] This
command takes a QSAM file and
copies the records into a database
table. The table must already exist.
Explanation:
Online help for the qtod command.
System action:
User response:
None
Destination:
stderr
ERZ037221I [Command: dtof tableName] This
command takes a database table and
dumps it to a flat file. The file can be
reloaded using ftod.
Destination:
stderr
ERZ037222I [Command: ftod tableName] This
command takes a database table and
loads it from a flat file. The file must
have been previously created from the
dtof command.
Explanation:
Online help for the ftod command.
System action:
User response:
None
Destination:
stderr
ERZ037224E You must provide a database either
through the -s flag or by setting the
environment variables
CICS_XDT_SERVER or DB2DBDFT
Explanation:
No database was provided, so the application was
unable to start.
System action:
The application terminates.
User response:
None
Destination:
stderr
ERZ037225E Tables containing columns of type
BLOB are not supported for this
command
Explanation:
Invalid action was attempted on a table containing a
column of type BLOB.
System action:
The command returns with an error
User response:
Retry with a valid table
Destination:
stderr
Explanation:
291
ERZ037226W ERZ037402E
ERZ037226W (Bind to database failed (SQL Error:
SQLError)
Explanation:
The application was unable to bind to the specified
database.
System action:
User response:
Check the database is running and was correctly
specified.
Destination:
stderr
ERZ037227I [Oracle Diagnostic Tool - Help] Valid
commandName - list l - create
tableName - read tableName - write
tableName - empty tableName - delete
tableName - addindex tableName delindex tableName - info tableName user userName - qtod QSAMfileName dtof tableName - ftod tableName - !
(ksh) - quit
System action:
cicsodt terminates.
User response:
Reinvoke the program correctly.
Destination:
stderr
ERZ037230E Failed to write record recordNumber
Explanation:
The cicsnetdata program failed to write the specified
record number to the output file.
System action:
User response:
Ensure there is enough space on the filesystem for the
output file.
Destination:
stderr
ERZ037401E Cannot run the db2 command. Check
the PATH environment variable
Explanation:
Explanation:
The PATH is not properly set to include the directory
containing the db2 executable.
System action:
System action:
Exit with return code 1.
User response:
None
User response:
Ensure that the PATH environment variable is set to
include all the directories required to run db2.
Destination:
stderr
ERZ037228E You must provide a user/password
either through the -u flag or by
setting the environment variable
CICS_XDT_USERPASS
Explanation:
No user/password was provided, so cicsodt was unable
to start.
Destination:
stderr
ERZ037402E Schema file schemaFileName is
either empty or contains invalid type
names
User response:
None
Explanation:
The schema file schemaFileName does not contain any
valid schemas. If the schema file is not empty, then it
must contain an error in the names of one of the types.
This second situation occurs only if the schema file is
edited by hand, since SMIT (on AIX) and the
Administration Utility (on Windows NT) ensure that only
valid types are placed into the schema file.
Destination:
stderr
System action:
ERZ037229E Usage: programName [-u

user/password] [-i inputFileName] [-o
outputFileName] [-e] [-r] [-c
commandName ...]
User response:
Check to ensure that the specified schema file is not
empty. If it is not empty, ensure that the type
specifications of the fields defined in the schema are
valid.
Explanation:
The program was invoked incorrectly.
Destination:
stderr
System action:
cicsodt terminates.
292
ERZ037403E ERZ037408W
ERZ037403E The existing file is not of type
fileType as specified in the schema
Explanation:
The database contains a file with the same name as
that specified in the schema. The file type of the
existing file is not the same as the filetype specified in
the schema.
System action:
User response:
Respecify the filetype in the schema to be consistent
with the filetype of the existing file or change the name
of the schema such that its name is different from that
of the existing file.
Destination:
stderr

User response:
Specify a positive variable field length.
Destination:
stderr
ERZ037407I Successfully created file fileName on
database databaseName
Explanation:
The file fileName was successfully created on database
databaseName. This means that all the fields specified
in the schema with the same name as fileName were
created with the names, types, and (optionally) field
lengths supplied, under user name CICS. Consequently,
the fully resolved name of the table is CICS.fileName.
System action:
Continues to process your command.
ERZ037404E Schema contains a CICS-reserved

field name fieldName
User response:
None.
Explanation:
The schema contains a field with a FieldName equal to
RRN, RBA or TIMESTA. These field names are
reserved for use by CICS and cannot be used to name
user-specified fields.
Destination:
stderr
System action:
User response:
Respecify the schema such that none of the fields have
a FieldName of RRN, RBA or TIMESTA.
Destination:
stderr
ERZ037405E Variable field length
variableFieldLength exceeds the DB2
limit of 32700
Explanation:
The variable field length specified in the schema
exceeds the maximum allowed in DB2.
System action:
User response:
Respecify the variable field length to be less than or
equal to 32700.
Destination:
stderr
ERZ037406E Variable field has an invalid length of
variableFieldLength
ERZ037408W Index name actualIndexName

(specifiedIndexName in the schema) on
file fileName already exists on the
database
Explanation:
The index actualIndexName already exists on the
database. The name in brackets specifies the index
name that was originally specified in the schema.
Database indexes are required to have a name that is
unique across the database. Indexes are renamed
during table creation so that they have a unique name.
The unique name is created by concatenating the file
name with the index number. The Primary index for a
file is given index number 0. Secondary indexes are
given index numbers 1 to 9, and secondary index
number 10 is given index number A.
System action:
If the -I flag was set on the command line, then
processing continues, otherwise the command exits with
return code 1.
User response:
Check that the index specified conforms with the
definition in the schema file. If it does not, then remove
it using the db2 DROP INDEX... command, then rerun
cicsdb2import to create an index with the desired
definition.
Destination:
stderr
Explanation:
variable field length is zero or negative
System action:
293
ERZ037409E ERZ037415E
ERZ037409E Implicit connection is not enabled:
the DB2DBDFT environment variable is
not set.
Explanation:
The database alias was not supplied on the command
line and implicit connection to the database was
attempted. This was not possible since the default
database was not specified in the environment variable
DB2DBDFT.
System action:
User response:
Either specify the desired database on the command
line using the -d option, or set the environment variable
DB2DBDFT.
Destination:
stderr
ERZ037410E Schema schemaName does not
contain any field definitions
Explanation:
The schema schemaName exists but does not contain
any field definitions.
System action:
User response:
Add field definitions to the schema, or remove it.
Destination:
stderr
ERZ037411I Connected to database databaseName
Explanation:
A connection was established to the database
databaseName. This connection is required in order to
create files and indexes. The connection to this
database is maintained while the cicsdb2import
command is running. All files and indexes specified in
the schema and on the command line are created on
this database.
System action:
User response:
None.
Destination:
stderr
ERZ037412E You do not have sufficient authority
to access schema files
Explanation:
The user who issued the cicsdb2import command does
not have the correct access permissions for the schema
files.
294
System action:
Exit with return code 1 .
User response:
On UNIX log on as root. On Windows NT log on as a
user that is a member of the cicsgroup or Administrators
groups. Retry the command.
Destination:
stderr
ERZ037413I Successfully added index
uniqueIndexName (originalIndexName
in the schema) for file fileName
Explanation:
The schema contains an index description with the
name originalIndexName; this index definition was
successfully added to the file fileName. Since database
indexes must be unique across an entire database,
cicsdb2import generates a unique name,
uniqueIndexName, and creates the index with that
name, rather than the name specified in the schema.
System action:
User response:
None.
Destination:
stderr
ERZ037414I The schema definition for file fileName
is consistent with that of the existing
file
Explanation:
There is a file fileName with the same name as that
defined in the schema already existing on the database.
Its field names are the same as those in the schema.
The field types are not checked for consistency between
the schema definition and the existing file.
System action:
User response:
None.
Destination:
stderr
ERZ037415E The schema definition of index
indexName contains a field name
fieldName which does not exist
Explanation:
The schema description of the index indexName
contains a nonexistent field name fieldName in the
IndexFieldNames (PrimaryIndexFieldNames in the case
of a primary index) section of the schema.
System action:
ERZ037416I ERZ037473W
User response:
Update the definition of the index in the schema to
contain only field names that are also defined in the
same schema.
Destination:
stderr
ERZ037416I Starting to create file fileName on
Explanation:
The command cicsdb2import has begun to process the
schema that describes the file fileName; an attempt is
made to create the file on database databaseName.
System action:
User response:
None.
Destination:
stderr
ERZ037420E SQL error returned, sqlcode sqlcode
Explanation:
A SQL API call to list the database directory failed.
System action:
User response:
Examine the value of sqlcode to determine the cause of
the failure.
Destination:
stderr
ERZ037460E You do not have sufficient
authorizations on database
databaseName to create tables
Explanation:
The user has neither of the authorizations (SYSADM or
DBADM) nor CREATETAB privilege on the database. At
least one of these privileges is required for
cicsdb2import to run successfully.
System action:
User response:
Rerun cicsdb2import when logged in as a user who has
the authority or privilege to create tables on the
database. Alternatively supply cicsdb2import with the
username and password of a user who does have these
privileges by specifying the -u userName flag and the -p
password flag.
Destination:
stderr
ERZ037470I No secondary indexes will be created

for file fileName since it is of type
relative
Explanation:
Secondary indexes cannot be created on files of type
relative. No attempt is made to check for secondary
indexes on a schema for a file of type relative.
Consequently no further warnings are issued.
System action:
User response:
None.
Destination:
stderr
ERZ037471E Usage: cicsdb2import -i schemafile
[-d database] [-u user -p password] [-I]
[-f file [-x index ... ] ] ...
Explanation:
cicsdb2import was invoked incorrectly.
System action:
Exit with return code 1 (incorrect usage).
User response:
Ensure the command is called with correct arguments
Destination:
stderr
ERZ037472W Schema file schemaFile does not
contain a valid schema for fileName
Explanation:
The specified schema file does not contain a description
schema for schemaFile, or the stanza is invalid. If the
schema file does contain a schema for schemaFile,
then this message can arise if a field in that schema
was given an invalid type.
System action:
User response:
Specify a filename for which a schema was written or, if
the schema does exist, check it for invalid types.
Destination:
stderr
not contain details of index
indexName for file fileName
Explanation:
The schema file schemaFileName exists, and contains
a schema for file fileName; however the schema for file
fileName does not contain a specification of index
indexName.
295
ERZ037474E ERZ037481E
System action:
User response:
Destination:
stderr
ERZ037474E File fileName already exists on
Explanation:
An attempt is being made either to create file fileName
or to add indexes to it. The file fileName already exists
on the database databaseName.
ERZ037478E The commandOption option requires

a mandatory argument
Explanation:
The command line option must be given an argument.
With the exception if the -I option, every command line
option must be given an argument.
System action:
Exit with return code 1 (usage error).
User response:
Rerun the command ensuring that all flags with
mandatory arguments have their arguments specified.
System action:
If the -I (ignore error) flag is set, continue processing. If
it is not set, exit with return code 1.
Destination:
stderr
User response:
If the user wishes only to create new indexes, rerun the
command with the -I (ignore error) flag set.
ERZ037479E Invalid command line option

commandOption
Destination:
stderr
ERZ037476W Could not create index
uniqueIndexName (schemaIndexName
in the schema) for file fileName
Explanation:
cicsdb2import was unable to create the specified index.
This can arise if the fields that compose the index are
not consecutive or if the index already exists on the
database.
System action:
User response:
Ensure that the fields that comprise the index are
consecutive.
Explanation:
An unknown command line option was specified.
System action:
User response:
Ensure that only the allowed command line options are
used.
Destination:
stderr
ERZ037480E The commandOption option must be
specified with this command
Explanation:
A mandatory option was not specified.
System action:
Destination:
stderr
User response:
Ensure that all mandatory options are given on the
command line.
ERZ037477E Command line argument

commandOption re-specified
Destination:
stderr
Explanation:
A command line option, other than -f or -x, was
specified more than once. Most of the command line
options ( -d, -u, -p, -i and -I) must not be specified
more than once.
System action:
User response:
Ensure that command line options (other than -f and
-x) are specified only once.
Destination:
stderr
296
ERZ037481E Cannot read schema file

schemaFileName
Explanation:
The specified schema file does not exist or is not
readable by this user.
System action:
User response:
Ensure that the specified schema file exists and can be
read by this user.
Destination:
stderr
ERZ037482E ERZ037490I
ERZ037482E Unable to find definition for database
databaseName
Explanation:
A database was specified that cannot be found.
System action:
Exit with return code 1. TRANSLATION_GUIDELINES
None.
User response:
Ensure that the specified database exists.
Destination:
stderr
ERZ037483E DB2 command on database
databaseName issued the following
message: db2Message
Explanation:
A DB2 command failed.
System action:
User response:
Examine the message returned by DB2 and follow the
action indicated for that message as specified in the
Messages and Problem Determination Guide for DB2.
Destination:
stderr
ERZ037484E Command could not complete
Explanation:
cicsdb2import received a signal that prevented it from
completing the processing requested. The full list of
signals that cause processing to stop in this way is: 1
(HUP), 2 (INT), 3 (QUIT), 8 (FPE), 10 (BUS), 11
(SEGV), 15 (TERM).
System action:
Exits with return code 1.
User response:
None.
Destination:
stderr
ERZ037486I Usage: cicsdb2import -i schemafile [-d
database] [-u user -p password] [-I] [-f
file [-x index ... ] ] ...
Explanation:
The user has requested usage information for
cicsdb2import using the -? option.
Destination:
stderr
ERZ037487E Unable to connect to database.
Explanation:
An attempt was made to connect to a database. This
did not succeed.
System action:
Issue message ERZ37483E to show the messages
issued by DB2, then exit with return code 1.
User response:
Follow the instructions for message number
ERZ37483E.
Destination:
stderr
ERZ037489E Field mismatch between schema
schemaName and existing file
fileName
Explanation:
There is a difference between the field names specified
in schema schemaName and the field names
discovered in an existing file fileName.
System action:
User response:
Either change the name of the schema so that it is
different from any existing filename, or alter the schema
definition so that it is consistent with the existing file.
Destination:
stderr
ERZ037490I Enter database password for user
userName:
Explanation:
The -u option was used to specify the user name but
the password was not supplied via the -p option. Since
it is mandatory to supply the password if the username
is supplied, this message prompts the user to enter their
password.
System action:
Wait for the password to be entered. The password is
not echoed back to the screen.
User response:
Enter the password for user userName.
Destination:
stderr
System action:
User response:
None.
297
ERZ037491E ERZ037496E
ERZ037491E Could not determine codeset width to
use with nlsString field
Explanation:
The system defined value for the maximum width of a
character in the current locale was found to be zero.
This value (MB_CUR_MAX) is set based on the
currently defined locale.
System action:
User response:
Check the currently defined locale. On UNIX, check that
the locale set by the LANG environment variable is
valid.
Destination:
stderr
ERZ037492E Field name fieldName of index
indexName on file fileName either
does not exist or is not consecutive
with its predecessor
Explanation:
The column names that comprise an index must be
consecutive. This means that they must be in the same
order as the column names that define the file itself,
and that each field specified must be adjacent to its
predecessor. This message is generated when the
index contains the name of a column that is not in the
same sequence as the columns of the file itself, or
when a column name in the index does not exist.
ERZ037494W Decimal field fieldName had illegal

length of fieldLength; setting the
fieldlength to mandatoryDecimalLength
Explanation:
A decimal field must have a field length of
mandatoryDecimalLength, which is 18. A decimal field in
the schema being processed was given a field length
different from mandatoryDecimalLength.
System action:
Set the FieldLength of the field fieldName to 18, and
continue.
User response:
To avoid this warning message, set the field length of
each decimal field in the schema to 18.
Destination:
stderr
ERZ037495W Invalid field type fieldType
Explanation:
The schema being processed contains a field with an
invalid field type fieldType.
System action:
User response:
Ensure that all fields have a valid field type. Schema
manipulation via SMIT on AIX and the Administration
Utility on Windows NT ensure that all field types are
valid.
System action:
The index indexName is not created. Processing
continues.
Destination:
stderr
User response:
Ensure that all indexes are defined with field names that
are consecutive.
ERZ037496E Unable to save database id

databaseName into file fileName.
Destination:
stderr
Explanation:
The write of the DB2 database (DB2) name
databaseName to file fileName was unsuccessful.
ERZ037493E Width of zero was specified for

fixed-length field fieldName
System action:
value 1.
Explanation:
Field fieldName was assigned a field length of zero.
Fixed length fields of type string or type byteArray
require a fieldlength to be supplied, which must be
greater than 0.
System action:
User response:
Ensure that all fields of type string or type byteArray
have their FieldLength set to 1 or greater.
Destination:
stderr
298
User response:
Check that you have permission to create fileName.
On UNIX Check that the file system, /temp, is not full.
On Windows NT, check that the drive and directory
defined in the TEMP environment variable are not full. If
either either environment is full, correct the problem and
retry the command.
Destination:
stderr
ERZ037497E ERZ037504I
ERZ037497E Usage: cicssmitdb2 { -s serverName |
-e } processId.
Explanation:
This is the usage message for the CICS private
command cicssmitdb2. This command is not to be run
from the command line.
User response:
If more security is required on the files created then
manually change the ACLs on the files created by using
the acl_edit command.
Destination:
stderr
System action:
value 1.
ERZ037501E Cannot run the sqlplus command.

Check the PATH environment variable
User response:
None
Explanation:
The PATH is not properly set to include the directory
containing the sqlplus executable.
Destination:
stderr
ERZ037498E You have not selected a DB2
database.
Explanation:
You have not selected a DB2 database (DB2).
System action:
value 1.
User response:
Select a DB2 database and retry the operation.
Destination:
stderr
ERZ037499I Usage: cicssmitdb2 { -s serverName |
-e } processId.
Explanation:
command cicssmitdb2. This command is not to be run
System action:
0.
User response:
None
Destination:
stderr
ERZ037500W Unable to query Minimum Protection
Level of Server serverName,
assumming unauthenticated
Explanation:
The command attempted to query the Protection Level
at which the SFS Server is running. This information is
used to establish which ACLs to set on the files being
created by the command.
System action:
The command continues, and sets unauthenticated
ACLs on the files it creates.
System action:
User response:
Ensure that the PATH environment variable is set to
include all the directories required to run sqlplus.
Destination:
stderr
ERZ037502E Usage: cicsoraimport -i schemafile [-u
user[/password]] [-I] [-f file [-x index ...
] ] ... [-t tableSpace]
Explanation:
cicsoraimport was invoked incorrectly.
System action:
Exit with return code 1 (incorrect usage).
User response:
Ensure the command is called with correct arguments
Destination:
stderr
ERZ037503E Oracle command on database
databaseName issued the following
message: oracleMessage
Explanation:
An Oracle command failed.
System action:
User response:
Examine the message returned by Oracle and follow the
action indicated for that message as specified in the
Messages and Codes Manual for Oracle.
Destination:
stderr
ERZ037504I Usage: cicsoraimport -i schemafile [-u
user[/password]] [-I] [-f file [-x index ...
] ] ... [-t tableSpace]
Explanation:
299
ERZ037505W ERZ038006E
The user has requested usage information for
cicsoraimport using the -? option.
System action:
User response:
None.
Destination:
stderr
ERZ037505W Fieldname fieldName too long being truncated to truncatedFieldName.
Explanation:
The fieldname specified in the schema definition for
cicsdb2import was too long and was truncated.
System action:
The command truncates the fieldname and continues.
User response:
None.
Destination:
stderr
ERZ038001E Usage: cicssfs { -? | [-t traceMask]
[[-T traceDestination]...] [-a | -nlv] [-I]
[serverName]
Explanation:
You entered the cicssfs command incorrectly.
System action:
value 1.
User response:
Retry the command specifying correct parameters. See
command when that configuration is complete. If there

is neither a region running or another user performing
configuration then see the message output just before
this one for further details.
Destination:
stderr
ERZ038004I Configuring SFS for recoverable
auxiliary TSQs for region regionName
Explanation:
The command is creating Structured File Server (SFS)
files for the regions recoverable auxiliary Temporary
Storage Queues (TSQs).
System action:
User response:
None
Destination:
stderr
ERZ038005I Configuring SFS for non-recoverable
Explanation:
files for the regions non-recoverable auxiliary
Temporary Storage Queues (TSQs).
System action:
User response:
None
Destination:
stderr
Destination:
stderr
Explanation:
The command encountered a problem running
programName.
ERZ038003E Region regionName does not exist, is

running, or is already being
configured. Configuration is not
possible.
System action:
value 1.
Explanation:
The Structured File Server (SFS) cannot be configured
for a region while the region is running or while SFS is
being configured by another user.
System action:
value 1.
User response:
If the region is running and the configuration change
must be made then shutdown the region. If another user
is performing configuration for the region then retry the
300
User response:
Refer to other messages displayed or in stderr. Check
that CICS is installed correctly. Check that the program
exists, is owned by user cics and has read, write and
execute permissions for its owner.
Destination:
stderr
ERZ038007I ERZ038016E
ERZ038007I Configuring SFS for logically
recoverable TDQs for region
regionName
Explanation:
files for the regions logically recoverable Transient Data
Queues (TDQs).
System action:
User response:
None
Destination:
stderr
ERZ038008I Configuring SFS for physically
recoverable TDQs for region
regionName
Explanation:
files for the regions physically recoverable Transient
Data Queues (TDQs).
System action:
User response:
None
Destination:
stderr
ERZ038009W Unable to update details of server
serverName
Explanation:
the SFS serverName. However, since the command
was invoked with the -I flag to ignore errors, the existing
details are used. Accompanying messages identify the
System action:
User response:
If the details of the SFS server serverName do not
need to be modified then no action is necessary.
However, if the SFS server details are different use
Destination:
stderr
ERZ038010I Configuring SFS for non-recoverable
TDQs for region regionName
Explanation:

files for the regions non-recoverable Transient Data
Queues (TDQs).
System action:
User response:
None
Destination:
stderr
ERZ038011I Configuring SFS for protected
Locally-Queueing requests for region
regionName
Explanation:
files for the regions Protected Locally-Queueing
requests.
System action:
User response:
None
Destination:
stderr
ERZ038012I Configuring SFS for unprotected
regionName
Explanation:
files for the regions Unprotected Locally-Queueing
requests.
System action:
User response:
None
Destination:
stderr
ERZ038016E Timed out waiting for server
serverName to start
Explanation:
The Structured File Server (SFS) serverName has not
responded to Remote Procedure calls (RPCs) within the
time limit allowed by the command. If you were auto
starting the server (the default action) this message
does not necessarily indicate that there is a problem as
the SFS can have a large amount of data to recover
that can possibly take longer than the timeout defined.
The SFS writes its progress messages to a file called
a server named /.:/cics/sfs/default the full path of
the message file is varDir/cics_servers/SSD/cics/sfs/
301
ERZ038019E ERZ038024I
default/msg). On Windows NT you can find the drive
letter of the disk containing the msg file by using the
cicsname serversdir command.
System action:
User response:
Use the SFS messages to determine if there is a
problem. If there is, shut down the server (using, for
example the cicssfsshut command), correct the problem
and retry the command. If the sfs process is using a
large amount of system CPU, then the SFS is almost
certainly still recovering data; continue to wait for the
server to become active. Once the server has initialized
it writes a message. If the problem persists cold start
SFS serverName (all data is lost) and restore data
from backup.
Destination:
stderr
ERZ038019E Unable to obtain region definition for
region regionName.
Explanation:
The region definition does not exist for region
regionName.
System action:
The command terminates abnormally returning the
value 1.
User response:
Add the region definition using the cicsdefault
command.
Destination:
stderr
ERZ038020E Unable to obtain server definition for
server serverName
Explanation:
The Structured File Server (SFS) definition does not
exist for server serverName. In order to resolve certain
attribue values the command requires access to the
SSD definition file.
System action:
value 1.
User response:
Add the server definition using the cicssfscreate
command. Alternatively, the server possibly exists on a
remote machine that cannot be reached.
Destination:
stderr
ERZ038022E Logical volume volumeName does

not exist
Explanation:
A Structured File Server (SFS) requires logical volume
volumeName in order to log recoverable information. It
does not exist. Accompanying messages give more
information about the cause of the the problem.
System action:
value 1.
User response:
Create logical volume volumeName and retry the
command.
Destination:
stderr
ERZ038023W Unable to create logical volume
volumeName
Explanation:
Logical volume volumeName was not able to be
created. Accompanying messages identify the cause of
the problem. The SFS writes its messages to a file
example for a server named /.:/cics/sfs/default the
SSD/cics/sfs/default/msg). On Windows NT you can
find the drive letter of the disk containing the msg file by
using the cicsname serversdir command.
System action:
value 1.
User response:
Destination:
stderr
ERZ038024I Logical volume volumeName for
server serverName has been created.
Explanation:
created logical volume volumeName. This is used by
Structured File Server (SFS) serverName to store data.
System action:
User response:
None
Destination:
stderr
302
ERZ038025E ERZ038031E
ERZ038025E Unable to add volume volumeName
to server serverName
ERZ038028E Unable to create Local Queue using

file fileName on server serverName.
Explanation:
The attempt to add volume volumeName to Structured
File Server (SFS) serverName was unsuccessful.
Explanation:
An attempt to create a Local Queue (LQ) on the
Structured File Server (SFS) serverName was
unsuccessful.
System action:
value 1.
User response:
Destination:
stderr
ERZ038026E Unable to create TSQ using file
fileName on server serverName
Explanation:
There was an error creating the Temporary Storage
Queue (TSQ) fileName on Structured File Server (SFS)
serverName.
System action:
value 1.
User response:
Refer to preceding messages, from sfsadmin, for the
reason why the TSQ was unable to be created. If the
preceding message gives the details on an already
existing file on the Structured File Server (SFS) then the
file cannot be created because one already exists. You
can ignore this step and continue with subsequent
configuration steps by retrying the request with Ignore
Errors selected (-I flag on command).
Destination:
stderr
ERZ038027E Unable to create TDQ using file
fileName on server serverName.
Explanation:
There is an error creating the Transient Data Queue
(TDQ) needed by the Structured File Server (SFS)
serverName for storing data.
System action:
value 1.
User response:
existing file on the Structured File Server (SFS) then the
file cannot be created because one already exists. You
can ignore this step and continue with subsequent
configuration steps by retrying the request with Ignore
Errors selected (-I flag on command).
Destination:
stderr
System action:
value 1.
User response:
reason why the LQ was unable to be created. If the
existing file on the SFS then the file cannot be created
because one already exists. You can ignore this step
and continue with subsequent configuration steps by
retrying the request with Ignore Errors selected (-I flag
on command).
Destination:
stderr
ERZ038029E Unable to update region definition.
Explanation:
The command was unable to update the region
definition.
System action:
value 1.
User response:
Check that you have read, write and execute
permissions for the region directory and that the file
system is not full.
Destination:
stderr
ERZ038030I Configuration completed successfully.
Explanation:
There were no problems reported during configuration.
System action:
User response:
None
Destination:
stderr
ERZ038031E Usage: cicssfscreate { -? | [-v] [-I] [-S]
[-m modelId] serverName
Explanation:
You entered the cicssfscreate command incorrectly.
System action:
303
ERZ038032E ERZ038041W
value 1.
User response:
Retry the command with correct parameters. See the
more information.
Destination:
stderr
ERZ038032E Usage: cicssfsdestroy { -? | [-v] [-I]
serverName }
Explanation:
You entered the cicssfsdestroy command incorrectly.
System action:
value 1.
User response:
Retry the command with correct parameters. See the
more information.
Destination:
stderr
ERZ038034E Unable to create server serverName
Explanation:
The command you have entered was unable to create a
new Structured File Server (SFS) named serverName.
problem.
Destination:
stderr
ERZ038037I Server serverName added to SSD
Explanation:
An entry was added to the Structured File Server (SFS)
Server Definitions (SSD) for SFS serverName.
System action:
User response:
None
Destination:
stderr
ERZ038038I Server serverName added as a
subsystem
Explanation:
A subsystem was created for the Structured File Server
(SFS) serverName.
System action:
User response:
None
Destination:
stderr
ERZ038039I The subsystem for server serverName
has been removed
System action:
value 1.
Explanation:
The details of Structured File Server (SFS)
serverName were deleted.
User response:
the problem. If necessary, certain errors can be ignored
if the command is run with the -I flag (ignore errors).
System action:
Destination:
stderr
ERZ038035E Unable to destroy server serverName
Explanation:
The command you have entered was unable to
completely destroy the Structured File Server (SFS)
serverName. Accompanying messages identify the
System action:
value 1.
User response:
command.
304
User response:
None
Destination:
stderr
ERZ038041W File fileName already exists on
server serverName
Explanation:
The file fileName already exists on Structured File
Server (SFS) serverName.
System action:
Processing continues, but other messages can be
produced as a result of this error that can possibly
cause the command to terminate. If the cicssfsconf
command is invoked without the -q flag information
about the existing file is displayed.
User response:
ERZ038050E ERZ038060E
If necessary, consider destroying the existing file by
using the SFS administration command sfsadmin.
Destination:
stderr
ERZ038050E Server serverName entry already
exists in SSD.
Explanation:
An entry for Structured File Server (SFS) serverName
already exists in the SFS Server Definitions (SSD).
System action:
value 1.
User response:
Either use the cicssfsdestroy command to remove all
the server details, or retry the command specifying the
-I (ignore errors) option.
Destination:
stderr
ERZ038051E Unable to add server serverName to
SSD
Explanation:
serverName were unable to be added to the SFS
Server Definitions (SSD). Accompanying messages
identify the exact cause of the problem. However, the
most likely cause is that there is already an entry for a
SFS of this name.
System action:
value 1.
User response:
the problem. Correct the problem and retry command.
Certain errors can be ignored if the command is run
with the -I flag (ignore errors).
Destination:
stderr
ERZ038052E Unable to add entry serverName as a
subsystem
Explanation:
The command you have entered was unable to add the
subsystem details for Structured File Server (SFS)
serverName. Accompanying messages identify the
exact cause of the problem. An entry for your SFS was
not created.
System action:
value 1.

the problem. Correct the problem and retry command.
Certain errors can be ignored if the command is run
with the -I flag (ignore errors).
Destination:
stderr
ERZ038053W Server serverName entry already
exists in SSD
Explanation:
An entry for Structured File Server (SFS) serverName
already exists in the SFS Server Definitions (SSD). But
as the command was invoked with the -I flag (ignore
errors) the command redefines the existing entry using
any overrides you have specified.
System action:
User response:
None
Destination:
stderr
ERZ038054E Unable to find entryName in SSD
Explanation:
The Structured File Server (SFS) details for entryName
were unable to be retrieved from the SFS Server
Definitions (SSD). Accompanying messages identify the
System action:
value 1.
User response:
command.
Destination:
stderr
ERZ038060E Waiting for lock.
Explanation:
A Structured File Server (SFS) command requires an
SFS lock to be taken; however, the lock is already being
held by another process.
System action:
The command loops until the lock is released or timeout
occurs.
User response:
Use the cicssfslock command to release the lock.
Destination:
stderr
User response:
305
ERZ038061E ERZ038072E
ERZ038061E The server serverName is currently
being administered by another
process.
Explanation:
Only one process at a time can administer the server.
Destination:
stderr
ERZ038070W Unable to add a subsystem definition
for server serverName.
User response:
Wait until the server has finished being administered by
the other process. Retry the transaction.
Explanation:
Subsystem names used for each Structured File Server
(SFS) must be unique. A subsystem name for SFS
serverName was not added as the ShortName defined
already exists. As you have run the command with the -I
flag (ignore errors) the existing subsystem definition is
modified.
Destination:
stderr
System action:
System action:
value 1.
ERZ038062W Unable to find the subsystem

definition for server serverName.
Explanation:
The command you have entered was unable to find a
subsystem definition for Structured File Server (SFS)
serverName. The definition was possibly already
deleted. Accompanying messages identify the cause of
the problem.
User response:
If the name of the SFS serverName associated with
the ShortName has not changed then no action is
necessary. However, if the SFS name is different
destroy the server and retry the command or override
ShortName with a valid one.
Destination:
stderr
System action:
ERZ038071W Subsystem definition for server

serverName has not been removed.
User response:
Check that the correct server name was specified.
Check accompanying messages to determine whether
the subsystem exists. Retry the command.
Explanation:
The command you have entered tried to delete a
subsystem definition that is associated with a different
server. The definition was not deleted. Accompanying
messages give more information about the problem.
Destination:
stderr
ERZ038063I Server serverName has been removed
from SSD.
Explanation:
Structured File Server (SFS) serverName was deleted
from the SFS Server Definitions (SSD).
System action:
User response:
None
Destination:
stderr
ERZ038065I Releasing lock for server serverName.
Explanation:
The lock, which indicates that Structured File Server
(SFS) serverName is running, was removed.
System action:
User response:
None
306
System action:
User response:
Check that the server name is correct. Retry the
command specifying the correct server.
Destination:
stderr
ERZ038072E Server serverName unable to
read/write to logical volume
volumeName using Id userId.
Explanation:
The Structured File Server (SFS) serverName keeps
essential information on the operating system logical
volume volumeName. In order for the SFS to function
correctly it needs to be able to read and write to this
volume. The most likely cause of this problem is that
the logical volume is not owned by userId.
System action:
User response:
Investigate why userId is unable to read/write to
volumeName. Correct the problem and retry the
ERZ038073E ERZ038154E
command. On UNIX, if the problem is that
volumeName is not owned by userId use the
operating system command chown to change its
ownership.
Destination:
stderr
ERZ038073E Unable to create logical volume
volumeName for server serverName.
Explanation:
The command you have entered was unable to create
logical volume volumeName. The logical volume is
required by Structured File Server (SFS) serverName
to store data. Accompanying messages identify the
exact cause of the problem. The SFS writes its
messages to a file called msg under the
server named /.:/cics/sfs/default the full path of the
System action:
value 1.
User response:
Use both the accompanying and the SFS messages to
determine the cause of the problem. Shut down the
server (using, for example, the cicssfsshut command)
correct the problem and retry the command.
Destination:
stderr
ERZ038076E Unable to shutdown server
serverName.
Explanation:
The Structured File Server (SFS) serverName was
unable to be shut down. The SFS writes its messages
to a file called msg under the varDir/cics_servers
directory structure in a sub-directory based upon its
name (for example for a server named
/.:/cics/sfs/default the full path of the message file
is varDir/cics_servers/SSD/cics/sfs/default/msg). On
Windows NT you can find the drive letter of the disk
containing the msg file by using the cicsname
serversdir command.
stderr
ERZ038151E You do not have sufficient authority
to run this command.
Explanation:
You attempted to run a command with insufficient
authority. On UNIX you must be logged on as root. On
Windows NT you must be logged on with a userid with
Administrator and cicsgroup authority.
System action:
value 1.
User response:
Login correctly and retry the command.
Destination:
stderr
ERZ038152E The request to start server
serverName was unsuccessful.
Explanation:
start Structured File Server (SFS) serverName. This
request was unsuccessful. Accompanying messages
identify the exact cause of the problem.
System action:
User response:
command.
Destination:
stderr
ERZ038153E Usage: cicssfsshut { -? | [-f] [-c]
serverName }
Explanation:
You entered the cicssfsshut command incorrectly.
System action:
value 1.
User response:
Retry the command with valid parameters. See the
more information.
System action:
value 1.
Destination:
stderr
User response:
Use accompanying and server messages to determine
the cause of the problem, if they exist. Correct the
ERZ038154E The request to stop server

serverName was unsuccessful.
Destination:
Explanation:
The command you have entered has sent a request to
stop the subsystem running Structured File Server
307
ERZ038155E ERZ038166I
(SFS) serverName. This request did not succeed.
problem.
System action:
value 1.
User response:
If after examining the accompanying messages you are
unable to determine the cause of the problem retry the
command, first using the -f flag (immediate shutdown)
and, if that is unsuccessful, the -c flag (cancel the
subsystem).
Destination:
stderr
ERZ038155E Unable to execute executableName.
Explanation:
The command you have entered was unable to execute
executableName.
System action:
value 1.
ERZ038163E Server serverName was forcibly

unexpected exit.
Explanation:
The Structured File Server (SFS) serverName
terminated abnormally, without completing the normal
shutdown procedure. The SFS writes its messages to a
example for a server named /.:/cics/sfs/default the
SSD/cics/sfs/default/msg). On Windows NT you can
find the drive letter of the disk containing the msg file by
using the cicsname serversdir command.
System action:
value 1.
User response:
Use the SFS and the operating system messages to
determine why the server has terminated abnormally.
Correct the problem and restart the SFS.
Destination:
SFS message log
User response:
Check that executableName is available on your PATH
environment variable and that you have permission to
execute it. Correct the problem and retry the command.
ERZ038165E Unable to write serverName to

fileName.
Destination:
stderr
Explanation:
The write of the Structured File Server (SFS) name
serverName to file fileName was unsuccessful.
ERZ038156E Server serverName is not running.
System action:
value 1.
Explanation:
The Structured File Server (SFS) serverName is not
running, so the command was unable to be executed.
The SFS writes its messages to a file called msg under
System action:
value 1.
User response:
Check that the server name is correct. Use the SFS
messages to determine why the server is not running.
Destination:
stderr
User response:
Check that you have permission to create fileName.
Check that the file system, /temp, is not full. Correct the
Destination:
stderr
ERZ038166I Usage: cicssmitsfs { -s serverName | -e
} processId.
Explanation:
command cicssmitsfs. This command is not to be run
System action:
value 1.
User response:
None
Destination:
stderr
308
ERZ038167E ERZ038174E
ERZ038167E You have not selected an SFS.
Explanation:
You have not selected a Structured File Server (SFS).
System action:
value 1.
User response:
Select an SFS and retry the operation.
Destination:
stderr
User response:
Shut down the server and retry the command.
Destination:
stderr
ERZ038172E Server serverName has already been
run.
Explanation:
The Structured File Server (SFS) serverName details
cannot be modified because the server has already
been run and possibly contains data that can be lost if
the server is modified.
ERZ038169E Usage: cicssfsupdate { -n newServer

-o oldServer [-p password] [-v] [-I]
System action:
value 1.
Explanation:
command cicssfsupdate. This command is not to be run
User response:
The server cannot be modified if it has been run. You
can force the change by specifying the -I flag (ignore
errors) to the command, but this results in the
destruction of the current server and the creation of a
new server with the modified attributes.
System action:
value 1.
User response:
None
Destination:
stderr
ERZ038170E Unable to update details of server
serverName.
Explanation:
The CICS private command cicssfsupdate was unable
to change Structured File Server (SFS) serverName.
problem.
System action:
value 1.
User response:
command.
Destination:
stderr
ERZ038171E Server serverName is running.
Explanation:
serverName cannot be updated because the server is
running.
System action:
value 1.
Destination:
stderr
ERZ038173W Server serverName has already been
run.
Explanation:
The forced changing of Structured File Server (SFS)
serverName that was run results in the destruction of
the current server and the creation of a new server with
the modified attributes. Any existing data in for this SFS
is lost.
System action:
Processing continues, all data stored on the SFS is lost.
User response:
None
Destination:
stderr
ERZ038174E Usage: cicssfsconf { -? | [-I] [-q] {-R
wc regionName
DefaultFileServer=serverName | wc
regionName | {ra|na|lr|pr|nr|lqp|lqu
regionName
[[attributeName=attributeValue]...] }}
Explanation:
You entered the cicssfsconf command incorrectly.
System action:
value 1.
User response:
309
ERZ038175E ERZ038181W
more information.
Destination:
stderr
ERZ038175E Server serverName cannot be
configured.
Explanation:
The Structured File Server (SFS) was not configured
with the desired files.
System action:
User response:
Check that the SFS server is running. Check for
previous messages, if any, to determine the cause of
the problem.
Destination:
stderr
ERZ038176I Adding TSQ file fileName to server
serverName, volume volumeName.
Explanation:
The Temporary Storage Queue (TSQ) file fileName is
being added to the Structured File Server (SFS).
System action:
User response:
None
Destination:
stderr
ERZ038177I Adding TDQ file fileName to server
serverName, volume volumeName.
Explanation:
The Transient Data Queue (TDQ) file fileName is being
added to the Structured File Server (SFS).
System action:
User response:
None
Destination:
stderr
ERZ038178I Adding Local Queueing file fileName
to server serverName, volume
volumeName.
Explanation:
The Local Queueing file fileName is being added to the
Structured File Server (SFS).
System action:
310
User response:
None
Destination:
stderr
ERZ038179E Unable to create TSQ queueId on
server serverName.
Explanation:
Temporary Storage Queue (TSQ) file queueId was
unable to be created on Structured File Server (SFS)
serverName.
System action:
value 1.
User response:
Refer to preceding messages, from the SFS
administration command sfsadmin, for the reason why
the TSQ was unable to be created.
Destination:
stderr
ERZ038180W Unable to create TDQ queueId on
server serverName.
Explanation:
Transient Data Queue (TDQ) queueId was unable to
be created on the Structured File Server (SFS)
serverName. The command was run with the -I flag to
ignore errors.
System action:
User response:
Refer to preceding messages, from the SFS
administration command sfsadmin, for the reason why
the TDQ was unable to be created.
Destination:
stderr
ERZ038181W Unable to create Local Queue
queueId on server serverName.
Explanation:
The Local Queue queueId was unable to be created
on the Structured File Server (SFS) serverName. The
command was run with the -I flag to ignore errors.
System action:
User response:
reason why the Local Queue was unable to be created.
Destination:
stderr
ERZ038182I ERZ038194I
ERZ038182I Server serverName started
successfully.
ERZ038188E Subsystem entry subsystemName for

the server serverName was not found.
Explanation:
The Structured File Server (SFS) serverName started
successfully.
Explanation:
A subsystem entry for serverName was not found.
System action:
User response:
None
Destination:
stderr
ERZ038183I Usage: cicssfslock { -? | [ -l | -u | -t ]
serverName }
Explanation:
This is the usage message for the cicssfslock
command.
System action:
User response:
Destination:
stderr
ERZ038186E Usage: cicssfsnotify subsystemName
System action:
User response:
The server name was entered incorrectly, or the
subsystem entry was prematurely deleted. Correct the
Destination:
stderr
ERZ038189W Directory directoryName cannot be
deleted.
Explanation:
The named directory cannot be deleted. This is
probably due to the presence of user files in the
directory that CICS has not created, and therefore does
not remove.
System action:
User response:
There is no need to take any action. However, in order
to conserve disk resources, it is recommended that the
files are identified and removed. The directory identified
here can then be removed.
Explanation:
This is the usage message for cicssfsnotify. This
command is not to be entered from the command line.
Destination:
stderr
System action:

running.
User response:
None
Explanation:
The command you have entered is attempting to start a
Structured File Server (SFS) named serverName.
However, there is already a server of this name running.
Destination:
stderr
ERZ038187I Usage: cicssfsshut { -? | [-f] [-c]
serverName }
System action:
value 1.
Explanation:
This is the usage message for cicssfsshut.
User response:
If necessary, shut down the server of the same name
System action:
Destination:
stderr
User response:
Destination:
stderr
ERZ038194I Usage: cicssfscreate { -? | [-v] [-I] [-S]

[-m modelId] serverName
Explanation:
This is the usage message for the cicssfscreate
command.
311
ERZ038195I ERZ038207E
System action:
User response:
Retry the command specifying a valid SFS name.
User response:
Destination:
stderr
Destination:
stderr
ERZ038200W Region protection level

configProtectionLevel is insufficient to
access server serverName, using
server protection level
runProtectionLevel.
ERZ038195I Directory directoryName has been

deleted.
Explanation:
The directory directoryName was removed, due to
errors in the creation of the specified Structured File
Server (SFS).
System action:
value 1.
User response:
command. If necessary specify the -I flag to ignore
errors.
Destination:
stderr
ERZ038196W Directory directoryName cannot be
deleted.
Explanation:
The command you have entered unsuccessfully tried to
delete the directory directoryName and its contents.
problem. This message indicates that the command has
not deleted all the files in the directory.
System action:
value 1.
User response:
the problem. Correct the problem (for instance, you can
delete the directory manually). On UNIX use the
command rm -rf. On Windows NT use the rmdir /s.
Retry the command.
Destination:
stderr
ERZ038197E A server name was not supplied.
Explanation:
The command you have entered requires the name of a
Structured File Server (SFS), for example,
/.:/cics/sfs/default.
System action:
value 1.
312
Explanation:
The protection level at which the region accesses the
Structured File Server (SFS), as defined in the Region
Definitions (RD), must be greater than or equal to the
protection level at which the SFS is running, as defined
in the SFS Server Definitions (SSD).
System action:
Processing continues and the file is created with the
required protection.
User response:
Change the appropriate protection level attribute to
ensure that the protection level at which the region is
accessing the SFS is greater or equal than the
protection level of the SFS. If you do not do this, the
region does not have sufficient authority to access cics
system SFS files.
Destination:
stderr
ERZ038202E Usage: cicssfslock { -? | [ -l | -u | -t ]
serverName }
Explanation:
You entered the cicssfslock command incorrectly.
System action:
value 1.
User response:
more information.
Destination:
stderr
ERZ038207E Logical volumes on server
serverName could not be recovered.
Explanation:
Structured File Server (SFS) serverName
unsuccessfully attempted to bring its data volumes up to
date with information from its log file, using the
command tkadmin recover lvols. Accompanying
messages identify the cause of the problem. The SFS
ERZ038208E ERZ038214I
System action:
value 1.
User response:
server (using, for example the cicssfsshut command),
Destination:
stderr
ERZ038208E Server serverName could not be
enabled.
Explanation:
The command was not able to enable Structured File
Server (SFS) serverName for full operations, using the
sfsadmin enable server command. Accompanying
messages identify the cause of the problem. The SFS
default/msg). n Windows NT you can find the drive
System action:
value 1.
User response:
Destination:
stderr
ERZ038209E Logical volume volumeName for
server serverName could not be
enabled.
Explanation:
Structured File Server (SFS) serverName was unable
to make logical volume volumeName by using the
tkadmin enable lvol command. The logical volume is
used to store the data for the server. The SFS writes its

System action:
value 1.
User response:
Destination:
stderr
ERZ038213W Server serverName could not be
changed to multi-user mode.
Explanation:
unable to be changed from single-user mode to
multi-user mode by using the tkadmin clear
exclusiveauthority command. Accompanying messages
identify the cause of the problem. The SFS writes its
System action:
value 1.
User response:
Destination:
stderr
ERZ038214I Authorization for server serverName
has been set to authorizationLevel
Explanation:
The authorization level of a Structured File Server (SFS)
indicates whether or not the server Access Control Lists
(ACLs) are checked. A value of 0 indicates that
authorization is disabled and that ACLs are not
checked. A value of 1 indicates that ACLs are checked.
System action:
User response:
None
Destination:
stderr
313
ERZ038215E ERZ038220E
serverName.
Explanation:
When trying to cold start Structured File Server (SFS)
serverName the restart files that are used on an auto
start were unable to be deleted. The server has already
been run and possibly contains recoverable data that
can be lost on a cold start. It is not possible to cold start
an SFS while either the primaryRestartFile or the
backupRestartFile exist. Accompanying messages
System action:
User response:
Use the accompanying messages to determine the
cause of the problem. Correct the problem and retry the
command.

subsystemName respond.
Explanation:
The subsystem subsystemName has not started within
the time limit allowed by the command. The SFS writes
its messages to a file called msg under the
System action:
User response:
Use the Structured File Server (SFS) messages to
determine why the server is not running.
Destination:
stderr
Destination:
stderr
ERZ038216I Subsystem subsystemName has been

initialized.
ERZ038219I Server serverName is responding to

RPCs.
Explanation:
The subsystem subsystemName was successfully
initialized and a Structured File Server (SFS) was
started.
Explanation:
The Structured File Server (SFS) serverName is
responding to Remote Procedure Calls (RPCs). The
server is ready to process requests.
System action:
System action:
User response:
None
User response:
None
Destination:
stderr
Destination:
stderr
ERZ038217I Waiting for subsystem

subsystemName to become active.
ERZ038220E Log file logfileName on server

serverName could not be enabled.
Explanation:
The subsystem subsystemName was started
asynchronously and this message is issued while the
command you have entered waits for it to become
active.
Explanation:
Log file logfileName on Structured File Server (SFS)
serverName was not able to be enabled by using the
tkadmin enable logfile command. The log file is used to
store the recoverable data generated by the SFS.
problem. The SFS writes its messages to a file called
a server named /.:/cics/sfs/default the full path of
the message file is varDir/cics_servers/SSD/cics/sfs/
System action:
User response:
None
Destination:
stderr
System action:
value 1.
User response:
314
ERZ038221I ERZ038227E
Destination:
stderr
ERZ038221I Log file logfileName on server
Explanation:
Log file logfileName was enabled to store the
recoverable data generated by Structured File Server
(SFS) serverName.
System action:
User response:
None
Destination:
stderr
ERZ038222I Logical volumes on server
serverName have been recovered.
Explanation:
The Structured File Servers (SFS) data volumes were
updated with the information in the servers log file.
System action:
User response:
None
Destination:
stderr
ERZ038223I SFS Logical volume volumeName has
been created for server serverName.
Explanation:
Logical volume volumeName was created for
Structured File Server (SFS) serverName using
operating system logical volume created by user. The
Logical volume uses the operating system logical
volume as its backing store and takes on all of its
physical characteristics.
ERZ038224I Logical volume volumeName on server

Explanation:
Structured File Servers (SFS) logical volume
volumeName was made accessible for I/O. Logical
volume is used to store the data for the SFS.
System action:
User response:
None
Destination:
stderr
ERZ038225E SFS Logical volume volumeName
could not be created for server
serverName.
Explanation:
The logical volume volumeName was not able to be
created for Structured File Server (SFS) serverName
using the command MapLVol. The operating system
logical volume failed to be mapped to a logical volume.
problem.
System action:
value 1.
User response:
server using, for example the cicssfsshut command),
Destination:
stderr
ERZ038226I Logical volume volumeName has been
added to server serverName.
Explanation:
The logical volume volumeName was associated with
Structured File Server (SFS) serverName.
System action:
System action:
User response:
None
User response:
None
Destination:
stderr
Destination:
stderr
ERZ038227E entryName could not be found in

SSD.
Explanation:
315
ERZ038228I ERZ038235I
The Structured File Server (SFS) details for entryName
was unable to be retrieved from the SFS Server
Definitions (SSD). Accompanying messages identify the
System action:
value 1.
User response:
command.
Destination:
stderr

Destination:
stderr
ERZ038233I Cold start of server serverName
requested, all data will be destroyed
Explanation:
The user has asked for a cold start of a Structured File
Server. This causes any data held on that server to be
destroyed.
System action:
Start continues
ERZ038228I Server serverName has been enabled.
User response:
None
Explanation:
enabled for full operations.
Destination:
stderr
System action:
User response:
None
Destination:
stderr
ERZ038231E No server name has been specified.
Explanation:
When a Structured File Server (SFS) is cold started a
server name must be explicitly specified. The value of
the environment variable CICS_SFS_SERVER is not
used.
ERZ038234I To continue cold start type continue

and press enter:
Explanation:
The user has asked for a cold start of a Structured File
Server. This causes any data held on that server to be
destroyed. A confirmation of this action is required
before the start continues. Replying continue enables
the start to proceed; any other response halts the
process.
System action:
The process waits for the user to type a response.
User response:
continue
System action:
value 1.
Destination:
stderr
User response:
Retry the command specifying a name of a SFS.
ERZ038235I Reply was responseString, cold start of

server serverName halted.
Destination:
stderr
Explanation:
The user had asked for a cold start of a structured file
server, but, as the response to message ERZ38234 was
not continue, the start was halted.
ERZ038232I Usage: cicssfs { -? | [-t traceMask] [[-T

traceDestination]...] [-a | -nlv] [-I]
[serverName]
[[attributeName=attributeValue]...]}.
Explanation:
This is the usage message for the cicssfs command.
The server name must be specified on a cold start. For
an auto start the command uses the contents of
environment variable CICS_SFS_SERVER.
System action:
User response:
316
System action:
The process returns to the system management panel.
User response:
None
Destination:
stderr
ERZ038236I ERZ038244E
ERZ038236I Reply was responseString, cold start of
server serverName continuing.
Explanation:
The user had asked for a cold start of a structured file
server, and the response to message ERZ38234 was
continue so the start is continuing.
System action:
The cold start continues.
User response:
None
Destination:
stderr
ERZ038237I Region regionName being reset to
work with Structured File Server
serverName.
Explanation:
The region is reset and configured for SFS
serverName.
System action:
User response:
None
Destination:
stderr
ERZ038238E serverName is not a valid Structured
File Server name.
Explanation:
The -R option was specified on a cicssfsconf command,
but the server name supplied, serverName, is not valid.
The server name must begin with /.:/.
System action:
User response:
Issue the command with the name of a valid SFS
Server.
Destination:
stderr
ERZ038239E Supply a value for DefaultFileServer.
Explanation:
With the -R option the DefaultFileServer attribute must
be set on the command line. The next message
provides the command syntax. On AIX if the command
is issued from the SMIT panel, when Reset File Server
to SFS? is set to Yes, the SFS server storing CICS
Queue Data must be modified to specify the SFS
required for configuration.
User response:
Issue the command with the name of a valid SFS
Server.
Destination:
stderr
ERZ038240W Resource resourceName was not
recognized from the default SFS Server
Definition (SSD).
Explanation:
The resource specified was not found in the default SFS
Server Definition (SSD).
System action:
Processing continues using the default values.
User response:
Check that the default entry exists in the SFS Server
Definitions (SSD). Retry the command specifing the
correct resource.
Destination:
stderr
ERZ038243E Unable to locate server serverName
Explanation:
CICS attempts to locate a server by searching for the
server on the current machine. CICS is unable to locate
the server serverName.
System action:
User response:
Check that the SFS server is running on the current
machine.
Destination:
stderr
ERZ038244E Process programName forcibly
terminated
Explanation:
The process was forcibly terminated from an external
signal. The SFS writes its messages to a file called msg
under the varDir/cics_servers directory structure in a
sub-directory based upon its name. On Windows NT
System action:
User response:
Destination:
stderr
System action:
317
ERZ038245E ERZ038251E
Explanation:
cicssfs tried to access some memory for its own
System action:
User response:
Destination:
stderr
ERZ038246I Usage: cicssfsupdate { -n newServer -o
oldServer [-p password] [-v] [-I]
Explanation:
command cicssfsupdate. This command is not to be run
System action:
0.
User response:
None
all queues by speciying the wc option, or select the

queues you require by specifying a compination of
(ra,na,lr,pr,nr,lqp,lqu).
System action:
User response:
Respecify the command selecting only the required
parameters.
Destination:
stderr
ERZ038249E You must specify a region name
Explanation:
The command your entered must specify at least one of
the operation options identified in the message.
System action:
User response:
Consult the usage message and reissue the command
correctly.
Destination:
stderr
ERZ038250E You cannot specify any attribute
overrides when wc option specified
Destination:
stderr
Explanation:
You have selected that all queues be created without
changing (wc) any values, but you have specified extra
options on the command line to the command.
ERZ038247E At least one of the operation options

{wc,ra,na,lr,pr,nr,lqp,lqu} must be
chosen
System action:
Explanation:
The command line your enter must specify at least one
of the operation options identified in the message.
System action:
User response:
Consult the usage message and reissue the command
correctly.
Destination:
stderr
ERZ038248E When wc specified you cannot
select any other operation options
Explanation:
On the cicssfsconf command you have selected that all
files be created to hold the regions queues by
specifying the wc option, but you also selected at least
one other queue type explicitly. You must either select
318
User response:
If you require to specify attribute overrides on the
command then reissue the command specifying the
queue types individually (ra,na,lr,pr,nr,lqp,lqu). Otherwise
reissue the command without the extra options that you
specified.
Destination:
stderr
ERZ038251E The -R option may only be specified
when the wc option is slected
Explanation:
The -R option to reset the FileServer values in the
region definitions can be specified only when the wc
option is selected to configure all queues for the region.
System action:
User response:
Respecify the command be either removing the -R
option or my changing the queus selector attribute to
wc.
ERZ038252E ERZ038259E
Destination:
stderr
ERZ038252E Failed to update all region definitions
to new values
Explanation:
You requeted to reset the Region Definitions to use the
SFS Server for its user files and queueing files. An error
occurred while updating the database.
System action:
User response:
A previously logged message details the exact nature of
the failure. Use this message to correct the problem and
Destination:
stderr
ERZ038253W Failed to update all region definitions
to new values
Explanation:
You requeted to reset the Region Definitions to use the
SFS Server for its user files and queueing files. An error
occurred while updating the database.
System action:
The command continues, but some of the values in the
CICS region database possibly need to be reset
manually to ensure that the SFS Server is used.
User response:
Previously logged messages detail the exact nature of
the failure. Use these messages to correct the problem
and reissue the command.
ERZ038255E SFS operation opCode failed with

Explanation:
While executing cicssfsconf, a CICS Toolkit error
occurred that prevent the operation from completing
succesfully.
System action:
SFS file and skips to the next stage.
User response:
Destination:
stderr
ERZ038257I Usage: cicsmakelv { -? | [-I] -v
<volumeName> -s <volumeSize> -p
<path>
Explanation:
You entered the cicsmakelv command incorrectly.
System action:
value 1.
User response:
Retry the command with valid parameters.
Destination:
stderr
ERZ038258E Logical volume with name
volumeName already exists
Destination:
stderr
Explanation:
You attempted to create a Logical volume with the
name specified in the message, but a logical volume
ERZ038254E Failed to parse attribute attribute,

current value value
System action:
The operation fails with an unsuccessful return code.
Explanation:
While executing cicssfsconf, the command attempted to
interpret the expanded value for the attribute identified
in the message, but this attempt failed.
User response:
If the volume truely no-longer exists then rerun the
command with the -I option to force the redefinition of
the Logiocal Volume.
System action:
SFS file and skips to the next stage.
Destination:
stderr
User response:
Verify the value identified in the message is correct and
ERZ038259E Logical volume with name

volumeName, Path volumePath
already exists
Destination:
stderr
Explanation:
name specified in the message, but a fully defined
logical volume with that name already exists.
System action:
319
ERZ038260E ERZ038266W
stderr
User response:
If you wish to redefine the logical volume then remove
the logical volume and reexecute the command.
ERZ038263E Logical Volume volumeName does

not exist
Destination:
stderr
ERZ038260E Error occurred updating Logical
Volume location information
Explanation:
While attempt to update the administration information
for a logcial volume an error occurred.
System action:
User response:
Verifty that the current userid has sufficient privelages to
perform administration task on the machine. Also verify
the machines registry contains no errors.
Destination:
stderr
ERZ038261E Failed to create data file volumePath
for volume volumeName
Explanation:
The command attempted to create a file to hold the
data associated with the logical volume identified in the
message but the attempt failed.
System action:
User response:
Ensure that there is enough room for the file to be
created and reexeute the command.
Destination:
stderr
ERZ038262E Failed to write byteCount bytes to file
fileName
Explanation:
An attempt to write a number of bytes to the file
identified in the message failed. CICS initialises the file
specified with null characters written in a number of
iterations. Each iteration writes byteCount bytes to the
end of the file. The default size for a PPC gateway file
is 4194304. The default size for SFS files is 67108864.
System action:
User response:
Verify that the path to the file identified in the message
exists and that the current userid has sufficient
privelages to create the file. Also verify the there is
sufficient storage available to create the file.
Destination:
320
Explanation:
You requested to perform an operation on the logical
Volume identified in the message, but the Logical
Volume definition was unable to be found.
System action:
User response:
Verify the name of the logical volume is correct.
Destination:
stderr
ERZ038264W Failed to remove file fileName
Explanation:
The command attempted to delete the file identified in
the message but the attempt failed.
System action:
The command continues.
User response:
If the file identified in the message still exists, then
verify that it is not still in use by any other processes
and then remove it.
Destination:
stderr
ERZ038265W Failed to open file fileName, SFS
error errorString
Explanation:
cicsdestroy attempted to open the file identified in the
message in order to delete it but the attempt failed.
System action:
The file is ignored and cicsdelete continues processing.
User response:
and then remove it.
Destination:
stderr
ERZ038266W Failed to remove file fileName, SFS
error errorString
Explanation:
cicsdestroy attempted to delete the file identified in the
message but the attempt failed.
System action:
The file is ignored and cicsdelete continues processing.
User response:
ERZ038267I ERZ038273E
and then remove it.
Destination:
stderr
The command continues, the logical volume is created

and the entry in the registry is redefined.
User response:
None.
Destination:
stderr
ERZ038267I Deleting CICS file fileName

Explanation:
cicsdestroy is about to delete the named SFS file.
System action:
User response:
None.
Destination:
stderr
ERZ038268E Failed to expand file fileName
Explanation:
The command you entered attempted to interpret the
expanded value for the attribute identified in the
message, but this attempt failed.
System action:
The command ends with a non zero return code.
User response:
reissue the command. If this is okay, check that CICS is
installed correctly.
Destination:
stderr
ERZ038271W Logical volume with name

volumeName, Path volumePath
already exists
Explanation:
name specified in the message, but a fully defined
logical volume with that name already exists. If the
logical volume is already in use by another server, then
one of the servers using the logical volume must be
reconfigured to use a different logical volume.
System action:
The operation continues and uses the existing logical
volume.
User response:
If the logical volume is in use then one of the servers
using the logical volume must be reconfigured to use a
different logical volume.
Destination:
stderr
ERZ038272I Waiting for server serverName to
initialise.
ERZ038269I Usage: cicsremovelv { -? | -v

<volumeName>}
Explanation:
The server serverName was started asynchronously
and this message is issued while the command you
have entered waits for it complete the first stage of its
initialisation.
Explanation:
You entered the cicsremovelv command incorrectly.
System action:
System action:
value 1.
User response:
None
User response:
Retry the command with valid parameters.
Destination:
stderr
Destination:
stderr
ERZ038273E Region RuntimeProtection

regionRuntimeProtection is insufficient
to access server serverName
ERZ038270W Redefining logical volume with name

volumeName, New Path volumePath
Explanation:
The value of the RuntimeProtection attribute to none in
the Region definitions disables the sending of
authenticated RPCs to the SFS Server. The value of
the ProtectionLevel level in the SFS Server definitions is
set such that only clients using authenticated RPCs are
allowed to communicate with the server.
Explanation:
name specified in the message. An entry for this logical
volume already exists in the registry but the volume
itself no longer exists.
System action:
System action:
Processing halts.
321
ERZ038274E ERZ038279E
User response:
Change the RuntimeProtection attribute in the region
definitions to enable the sending of authenticated RPCs
to the SFS Server and if necessary also increase the
Protection Level attributes associated with the queueing
files that are created upon that server.
Destination:
stderr
ERZ038274E Unable to add environmentString to
the environment
Explanation:
The command you entered tried to add
environmentString to its environment but failed to do
so.
System action:
User response:
Check your system is not fully loaded, as this often is
the result of a lack of processing memory. Check also
that you have installed your system correctly.
Destination:
stderr
serverName, errno errno.
Explanation:
When trying to cold start Structured File Server (SFS)
serverName the restart files that are used on an auto
start were unable to be deleted. The server has already
been run and possibly contains recoverable data that
can be lost on a cold start. It is not possible to cold start
an SFS while either the primaryRestartFile or the
backupRestartFile exist. Accompanying messages
System action:
User response:
Use the accompanying messages to determine the
cause of the problem. Correct the problem and retry the
command.
Destination:
stderr
subsystemName respond.
Explanation:
The subsystem subsystemName has not stopped
within the time limit allowed by the command. The SFS
322

System action:
User response:
Use the Structured File Server (SFS) messages to
determine why the server is not responding.
Destination:
stderr
ERZ038277E Failed to remove file fileName
Explanation:
The command attempted to delete the file identified in
the message but the attempt failed. The most likely
causes are that you have insufficent privilage to remove
the file or that the file is still in use.
System action:
User response:
If the file is still in use then, stop the server are rerun
the command, otherwise check the permissions on the
file and rerun the command.
Destination:
stderr
ERZ038278E
cicssfsconf failed because SFS

Server Name serverName could not be
expanded
Explanation:
cicssfsconf could not expand SFS server name to the
format /.:/cics/sfs/serverName as expected by CICS.
This is a rare error, possibly a failure to allocate
memory, which could be due to resource unavailability
on the machine.
System action:
User response:
Check your machine for any long running sessions or
other resource hogging programs. Stop them and retry.
Also, look for any errors prior to this in the error logs
Destination:
stderr
ERZ038279E Either runtime stanza entry or both
restart files are missing for the SFS
server ServerName
Explanation:
The command attempted to warm start the SFS, but
failed. Either the restart files or the runtime stanza entry
for the SFS server is missing, due to which SFS can not
ERZ039004E ERZ041001E
be warm started. As the SFS needs to be cold started
save the data before cold starting the SFS.
console.msg
System action:
The command terminates wth an error.
ERZ039007W Unable to produce a list of

transactions due to insufficient storage
User response:
Start the SFS server with StartType=Cold option.
Explanation:
A request was issued to produce a list of transactions in
the region, probably via CEMT. However, the list cannot
be produced as there is insufficient storage available in
the region.
Destination:
stderr
ERZ039004E Insufficient storage to initialize the
CICS scheduler
Explanation:
During region initialization the scheduler was unable to
obtain sufficient storage from the Region Pool to
initialize correctly.
System action:
CICS abnormally terminates.
User response:
Restart CICS with an increased Region Pool size by
overriding the MaxRegionPool attribute (RD) on the
Destination:
console.msg
ERZ039005W Transaction transId rejected due to
insufficient storage
Explanation:
CICS cannot accept the request to run a transaction as
there is insufficient storage available in the region.
System action:
CICS continues.
User response:
Resubmit the transaction request when some storage is
made available. This can be achieved by using CEMT
to purge unwanted tasks that are already in the region.
Destination:
console.msg
ERZ039006W Application server serverId
terminating due to insufficient storage
Explanation:
CICS is terminating the application server as there is
insufficient storage available in the region.
System action:
CICS continues. If, as a result of the server terminating,
there are fewer than MinServers left running, an attempt
is made to start another one.
System action:
CICS continues. The list of tasks is not produced.
User response:
None
Destination:
console.msg
ERZ039008E Self consistency check failure in
transaction scheduler
Explanation:
Data held in region storage by the transaction scheduler
has been found to be inconsistent during CICS self
consistency checking.
System action:
User response:
Because the corrupted data is held in region storage, it
is unlikely that application code has caused the
problem. Save any dump file produced for use by your
support organization. If the problem persists, obtain a
dump (see the TXSeries for Multiplatforms Problem
Determination Guide) and contact your support
organization.
Destination:
console.msg
ERZ041001E RPC call to the name space failed.
Explanation:
A crucial RPC call failed. This prevents the RPC
Listener from further processing. Message ERZ4102E
gives further indication of the cause of the failure.
System action:
The RPC Listener process terminates. This can possibly
result in abnormal termination of the region.
User response:
Check message ERZ4102E for cause of the failure.
Destination:
console.msg
User response:
None
Destination:
323
ERZ041002E ERZ041012E
ERZ041002E RPC failure message: errorMessage.
Explanation:
Reported message errorMessage when the RPC call
failed.
System action:
See the preceding message for the action that is taken.
User response:
The reported message indicates the source of the
problem.
Destination:
console.msg
ERZ041007E The cicsrl process has already been
started for this region
Explanation:
The Distributed Computing Environment has indicated
to CICS that a cicsrl process already exists for this
region.
System action:
The cicsrl process that was attempting to initialize is
terminated. This results in the abnormal termination of
the region.
User response:
Ensure that the cicsrl process is not already running for
this region.
Destination:
console.msg
ERZ041008E
The transaction name transId is

unknown to CICS
Explanation:
CICS has received an intersystem request for a
transaction transId, which contains characters that are
not supported by CICS for user transactions.
Your region recognizes the following transactions:v User transactions that have a Transaction Definition
(TD) installed
v Four CICS private transactions (which are used for
certain function shipping requests), called 0x01, 0x02,
0x03, and 0x05.
System action:
The transaction from the remote system is rejected
User response:
Establish which remote system sent the intersystem
request. Arrange for the program or system
configuration on that remote system to be changed so
that the remote system only sends your CICS system
transactions that your CICS system recognizes.
Destination:
console.msg
324
ERZ041009E Unable to schedule request for

transaction transId because PPC
communications are not supported
with server-side transactions
Explanation:
CICS has received an intersystem request for
transaction transId either from a PPC Gateway server or
from a PPC TCP/IP connection. However, CICS is
unable to accept this requests because the region is
running with ServerSideTran=yes in the Region
Definition (RD) entry. This attribute enables server-side
transactions in the SFS Server, which means the region
is unable to support PPC communications.
System action:
CICS rejects the incoming request.
User response:
If you wish the CICS region to support intersystem
requests using PPC communications then restart your
CICS region with ServerSideTran=no. Alternatively,
investigate why the intersystem request was sent to
your region and alter the configuration in the remote
system or PPC gateway server to prevent another
request from being sent.
Destination:
console.msg
ERZ041010E
RPC server register interface request

failed.
Explanation:
CICS is unable to register the RPC interface for use
when accepting intersystem communication requests
from IBM CICS clients. Message ERZ4102E gives
further indication of the cause of the failure.
System action:
The application server process continues processing,
but the intersystem request is terminated.
User response:
Check message ERZ4102E for cause of the failure.
Destination:
console.msg
ERZ041012E CICS Client RPC request terminated
with error: errorMessage.
Explanation:
A CICS client issued a RPC request to run a
transaction, but the request was unable to be processed
due to the reported error.
System action:
The request is rejected.
User response:
problem. Check the console log and the symrecs file for
further error diganostics. Correct the errors before
attempting to resubmit the request.
ERZ041013E ERZ042002E
Destination:
CSMT
ERZ041013E CICS Client RPC request failed with
error: errorMessage.
Explanation:
A CICS client issued a RPC request to a running
transaction with user input data, but the request was
unable to be processed due to the reported error.
System action:
The request is rejected and an error passed to the
running transaction.
User response:
further error diganostics.
Destination:
CSMT
ERZ041014E Exception exceptionName caught
processing RPC request from CICS
client
ERZ041016I CICS Client applId no longer

communicating: CD entry: sysId.
Explanation:
A CICS client can no longer be contacted by the region.
System action:
The region no longer tries to communicate with the
CICS Client and frees up the applid for future use by
another CICS Client.
User response:
None.
Destination:
CSMT
ERZ041017W RPC Server Got invalid request
requesttype from cicscp client
Explanation:
RPC server receives an invalid request from cicscp. The
respective cicscp request may not be processed
properly.
System action:
cicsrl ignores the request and cicscp might give an error
Explanation:
CICS detected an unexpected exception condition when
processing a RPC request from a CICS client.
User response:
If such errors occur frequently, please contact Support
Team with relevant data.
System action:
The request is rejected. If the exception was detected in
an Application Server (cicsas), the process is terminated
and CICS continues.
Destination:
Console file
User response:
Check any messages before this one for possible
causes of the error. If the problem persists contact your
Destination:
console.msg
ERZ041015E CICS Client RPC request failed with
error: errorMessage.
Explanation:
CICS issued a RPC request to a CICS client with user
output data, but the request was unable to be
processed due to the reported error.
System action:
The request is rejected and an error passed to the
running transaction.
User response:
further error diagnostics.
Destination:
CSMT
ERZ042001E Storage allocation request from

Task-Private Pool was unsuccessful
Explanation:
CICS is short of Task-Private storage and a storage
allocation request for an CICS client terminal install or
uninstall operation was unable to be satisfied.
System action:
The CICS client terminal request is not performed. CICS
abnormally terminates the CTIN transaction with code
A42A.
User response:
Check for any transactions using large amounts of
storage. Retry the operation. If it is still unsuccessful,
refer to any previous messages written to the CSMT log
and console.msg file that indicate why Task-Private
storage was unable to be allocated.
Destination:
CSMT
ERZ042002E Network failure detected on
connection to client system sysId
(applId)
Explanation:
325
ERZ042003E ERZ042008I
The connection to CICS client sysId has failed during a
terminal install request. The terminal can not be
installed.
System action:
CICS abnormally terminates the CTIN transaction with
abend code A42D.
User response:
Ensure that the CICS system and the connection to it
are available before retrying the request.
Destination:
CSMT
ERZ042003E CICS-private transaction was invoked
incorrectly
Explanation:
A CICS-private transaction that can only be invoked by
an CICS client was started by another mode of
invocation.
System action:
A42B.
User response:
Check that the attribute InvocationMode in the
Transaction Definition is correct. Refer to the TXSeries
for Multiplatforms Intercommunication Guide for more
information.
Destination:
CSMT
encoding or decoding data that is about to be sent to, or

was received from an CICS client.
System action:
The CICS client terminal request is not performed.
User response:
support (NLS) environment of the CICS system. If a
required code page descriptor is not installed, a
preceding message indicates which one is missing (see
the operating system documentation for further
information). If this is not the case, contact your support
organization.
Destination:
CSMT
ERZ042006I Processing terminal autoinstall request
from client system sysId (applId);
terminal type is deviceType
Explanation:
CICS has started to autoinstall a terminal with device
type deviceType on behalf of CICS client sysId.
System action:
Terminal autoinstall continues.
User response:
None
Destination:
CSMT
ERZ042004E An invalid request was received from

client system sysId (applId)
ERZ042007E Unable to autoinstall terminal from

client system sysId (applId); terminal
type is deviceType
Explanation:
An invalid terminal install or uninstall request was
received from CICS client sysId.
Explanation:
A CICS client has connected to the region and made an
unsuccessful attempt to autoinstall a terminal.
System action:
CICS abnormally terminates the CTIN transaction with
code A42B.
System action:
The CICS client terminal install request is not
performed.
User response:
Examine previous messages in the CSMT log for
possible causes. If the problem persists, check that the
version of the CICS client product is compatible with the
version of CICS.
User response:
Examine previous messages in the CSMT log to
determine the reason why the autoinstall was
unsuccessful.
Destination:
CSMT
was unsuccessful
Explanation:
The CICS client request was unable to be converted
from the code page codePage1 to the code page
326
Destination:
CSMT
ERZ042008I Processing terminal install request
from client system sysId (applId);
terminal NETNAME is netname
Explanation:
CICS has started to install the predefined terminal with
NETNAME netname on behalf of CICS client sysId.
System action:
Terminal install continues.
ERZ042009E ERZ042014E
User response:
None
Destination:
CSMT
ERZ042009E Unable to install terminal for client
system sysId (applId); terminal
NETNAME is netname
Explanation:
A CICS client has connected to the region and
attempted to install a predefined terminal using
NETNAME netname, but this was unsuccessful.
System action:
performed.
User response:
Examine previous messages in the CSMT log to
determine the reason why the install was unsuccessful.
Destination:
CSMT
ERZ042010E Error generating terminal install
response message for client system
sysId (applId)
Explanation:
An error occurred when generating the response
message to a CICS client terminal install request.
System action:
performed.
User response:
Examine previous messages in the CSMT log file to
determine the reason why the install was unsuccessful.
organization.
Destination:
CSMT
ERZ042011E NETNAME netname does not exist in
the Terminal Definitions (WD)
Explanation:
NETNAME netname, but this was unsuccessful
because NETNAME netname is not defined in the WD.
System action:
performed.
User response:
Add an entry to the WD for the NETNAME or try to
install the terminal using a NETNAME already defined in
the WD.
Destination:
CSMT
ERZ042012E Terminal termId with NETNAME
netname defines an autoinstalled or
transaction routed terminal
Explanation:
NETNAME netname, but was unsuccessful because
this NETNAME is in use by an autoinstalled terminal or
a transaction routed terminal.
System action:
performed.
User response:
Try to install using a different NETNAME or investigate
why the NETNAME is being used by an autoinstalled
terminal or transaction routed terminal.
Destination:
CSMT
netname is not defined for client
system sysId (applId)
Explanation:
NETNAME netname, but was unsuccessful because
the Terminal Definition (WD) for this NETNAME defines
a remote terminal for another system or CICS client.
System action:
performed.
User response:
Install using a different NETNAME or modify the WD to
define a terminal either as belonging to this CICS client
or as a local terminal.
Destination:
CSMT
netname is out of service
Explanation:
A CICS client terminal has attempted to install with
NETNAME netname, but the Terminal Definition (WD)
entry termId is marked out of service.
System action:
performed.
User response:
Try installing using another NETNAME or use the
CEMT transaction to set the terminal back in service.
327
ERZ042015E ERZ042020E
Destination:
CSMT
System action:
The CICS client terminal autoinstall request is not
performed.
ERZ042015E Access to WD entry for terminal

termId was unsuccessful
User response:
Install using another device type that matches a
DevType entry in the Terminal Definitions (WD), or add
an entry to the WD that matches the requested device
type.
Explanation:
CICS cannot access the Terminal Definitions (WD) entry
for terminal termId.
System action:
The CICS client terminal request is not performed.
User response:
possible causes.
Destination:
CSMT
netname is already installed
Explanation:
NETNAME netname, but was unsuccessful because a
terminal is already installed using this NETNAME.
System action:
performed.
User response:
Install the terminal using a different NETNAME, or do
not specify a NETNAME, so that it is autoinstalled.
Destination:
CSMT
ERZ042017I Terminal termId install is complete for
client system sysId (applId); terminal
NETNAME netname
Explanation:
A CICS client terminal defined in the Terminal
Definitions (WD) is successfully installed.
System action:
User response:
None
Destination:
CSMT
ERZ042018E No terminal model for device type
deviceType
Explanation:
A terminal has attempted to autoinstall with device type
deviceType, but was unsuccessful because there are
no terminal models defined in the Terminal Definitions
(WD) with DevType=deviceType.
328
Destination:
CSMT
ERZ042019E Unable to generate unique Terminal
ID for terminal autoinstall
Explanation:
attempted to autoinstall a terminal, but was
unsuccessful since CICS was unable to generate a
unique Terminal ID. This is only likely to occur when a
very large number of terminals are defined in the
Terminal Definitions (WD) or have autoinstalled to the
region.
System action:
performed.
User response:
Examine the WD and use CEMT INQUIRE TERMINAL
to determine how many terminals are connected to the
region. Delete any unnecessary definitions and try
again.
Destination:
CSMT
ERZ042020E Autoinstall user exit program returned
duplicate terminal termId from
NETNAME netname
Explanation:
A CICS client terminal has connected to the region and
attempted to autoinstall, but was unsuccessful because
the autoinstall user exit program has generated a
terminal name that already exists.
System action:
performed.
User response:
If you have replaced the autoinstall user exit program,
investigate why a duplicate name was returned;
otherwise report the problem to your support
organization.
Destination:
CSMT
ERZ042021I ERZ042026E
ERZ042021I Terminal termId autoinstall is
complete for client system sysId
(applId); terminal NETNAME is
netname, terminal model is model
Explanation:
A CICS client terminal is successfully autoinstalled.
System action:
User response:
None
Destination:
CSMT
ERZ042022I Retrying insertion with new key name
Explanation:
CICS has tried to create a Terminal Definition (WD)
entry with a generated terminal identifier, but has found
that this identifier already exists.
System action:
CICS tries to create the terminal again with a new
identifier.
User response:
None
Destination:
console.msg
ERZ042023E Unable to run the terminal autoinstall
user exit program
Explanation:
A CICS client terminal autoinstall or uninstall operation
cannot successfully run the autoinstall user exit
program.
System action:
The CICS client terminal autoinstall/uninstall request is
not performed.
User response:
Check that the CICS-private transaction CHAT is
defined in the Transaction Definitions (TD); that the
corresponding program is defined in the Program
Definitions (PD); that the transaction program exists at
the pathname specified; and that the program has the
correct file permissions. If these are all correct, check
the program for coding errors. If you have not replaced
the user exit program, report the problem to your
Destination:
CSMT
ERZ042024E Terminal autoinstall rejected by user

exit program
Explanation:
A CICS client terminal has connected to the region and
attempted to autoinstall, but was rejected by the
terminal autoinstall user exit program.
System action:
performed.
User response:
investigate why the autoinstall was rejected; otherwise
report the problem to your support organization.
Destination:
CSMT
ERZ042025E Invalid terminal model modelId
selected by user exit program
Explanation:
The terminal autoinstall user exit program has selected
a terminal model that was not in the list supplied to it.
System action:
performed.
User response:
check the program for coding errors; otherwise report
the problem to your support organization.
Destination:
CSMT
ERZ042026E Terminal model modelId has been
deleted from the Terminal Definitions
(WD)
Explanation:
The terminal model modelId selected by the terminal
autoinstall user exit program was deleted from the
Terminal Definitions (WD).
System action:
performed.
User response:
Try again. Someone possibly deleted the terminal model
modelId from the Terminal Definitions (WD) while you
were attempting to autoinstall an CICS client terminal.
Destination:
CSMT
329
ERZ042027E ERZ042038E
ERZ042027E Terminal termId is not a valid client
terminal
Explanation:
An uninstall request for terminal termId was received
from an CICS client that does not own the terminal.
System action:
The CICS client terminal uninstall request is not
performed.
User response:
This is an error either in CICS or in the CICS client
product. If the problem persists, contact your support
organization.
Destination:
CSMT
ERZ042028I Terminal termId with NETNAME
netname has been uninstalled.
Explanation:
A CICS client terminal has uninstalled and terminated its
connection with the region.
System action:
CICS ceases to communicate with the CICS client
terminal.
User response:
None
Destination:
CSMT
ERZ042029E Uninstall of terminal termId was
unsuccessful
Explanation:
A CICS client has requested a terminal uninstall from
the region, but the uninstall was unsuccessful.
System action:
The CICS client terminal uninstall request is not
performed.
System action:
CICS returns a response to the remote system
indicating that a CD entry already exists for the APPLID.
A new CD entry for the remote system is not added to
the region.
User response:
Change the remote system to request another APPLID,
or change the RemoteLUName attribute for CD entry
sysId.
Destination:
CSMT
ERZ042037E APPLID applId requested by
DFHCCINX already exists in CD entry
sysId
Explanation:
CICS is installing a new Communications Definitions
(CD) entry for an CICS client. The autoinstall program,
DFHCCINX, requested APPLID applId for this CICS
client. However, CICS is unable to install a CD entry
with this APPLID because the APPLID used by an CICS
client must be unique within the local CICS region and
APPLID applId is currently configured in CD entry sysId.
System action:
The autoinstall request is backed out. This includes
calling DFHCCINX again, this time specifying the action
as UNINSTALL.
User response:
Change DFHCCINX to return another APPLID or
change the matching RemoteLUName and/or
SNAConnectName attributes in CD entry sysId to a
different value. For more information on DFHCCINX,
refer to the TXSeries for Multiplatforms
Destination:
CSMT
ERZ042038E SYSID sysId requested by DFHCCINX
already exists in the CD
User response:
Examine previous messages to determine why the
uninstall was unsuccessful. Refer to the TXSeries for
Multiplatforms Intercommunication Guide for more
information on deleting terminals.
Explanation:
The SYSID sysId returned by the autoinstall program
DFHCCINX is the same as the SYSID (key) of an
existing Communications Definition (CD) entry.
Destination:
CSMT
System action:
CICS calls DFHCCINX indicating that the CD entry is
being deleted. A new CD entry is not added for the
remote system.
ERZ042036E Requested APPLID applId already

exists in CD entry sysId
Explanation:
A remote system has requested to use APPLID applId
when communicating with the local region. However,
this APPLID is already in use by a remote system that
is using Communications Definition (CD) entry sysId.
330
User response:
Change DFHCCINX to return another SYSID or to use
the SYSID passed to it by CICS. Alternatively change
the SYSID for CD entry sysId. For more information on
DFHCCINX, refer to the TXSeries for Multiplatforms
Destination:
CSMT
ERZ042039E ERZ042044E
primaryCode/secondaryCode detected by
CCIN transaction
Explanation:
The CICS to CICS install transaction, CCIN, detected a
communications error with the remote system.
System action:
CICS abnormally terminates the CCIN transaction.
User response:
Ensure that the remote system is still available and
restart it if necessary. Refer to TXSeries for
Multiplatforms Intercommunication Guide for further
information on the error codes primaryCode/
secondaryCode.
Destination:
CSMT
ERZ042040E Unable to generate unique SYSID for
an autoinstalled CD entry
Explanation:
A remote system has requested a connection to the
region. However, CICS was unable to autoinstall a CD
entry for the remote system because it can not generate
a unique SYSID for the CD entry. This is only likely to
occur when a very large number of remote systems and
terminals are defined in the Communications Definitions
(CD) and Terminal Definitions (WD).
System action:
CICS sends a response to the remote system indicating
it is busy and that the remote system can try to
reconnect later.
CSMT
ERZ042042E Removal of CD entry for remote
system applId is not allowed from
system sysId
Explanation:
The remote system defined in Communications
Definition (CD) entry sysId scheduled a CCIN
transaction and requested that CICS remove the CD
entry for system applId. This is not allowed. A remote
system can only request the removal of its own CD
entry.
System action:
CICS does not remove the CD entry.
User response:
Check the remote system is correctly configured. If the
Destination:
CSMT
ERZ042043I Waiting for tasks to finish with CD
entry sysId for remote system
LUname
Explanation:
CICS is uninstalling (deleting) CD entry sysId, either
because the remote system LUname requested it or
because the connection to the remote system has
failed. CICS is waiting while outstanding intersystem
requests from the remote system complete.
System action:
CICS retries the uninstall.
User response:
Examine the CD and WD and use CEMT INQUIRE
TERMINAL to determine how many terminals are
connected to the region. Delete any unnecessary
definitions and retry the connection request from the
remote system.
User response:
None
Destination:
CSMT
ERZ042044E
ERZ042041E Invalid terminal name termId returned

by user exit program
Explanation:
The terminal autoinstall user exit program has returned
an invalid terminal name.
System action:
performed.
User response:
check the program for coding errors; otherwise report
the problem to your support organization.
Destination:
Destination:
CSMT
Could not delete CD entry sysId for
remote system LUname
Explanation:
The remote system LUname is uninstalling, either due
to a request from the remote system, or because
communications to the remote system have failed. CICS
has waited for the tasks using Communications
Definition (CD) entry sysId to complete, but this has not
happened. CICS is therefore unable to delete the CD
entry.
If the remote system is communicating with your region
using a Systems Network Architecture (SNA) connection
then CICS reuses CD entry sysId when the remote
system reconnects.
If the remote system is communicating with your region
using CICS family TCP/IP support, then CICS creates a
331
ERZ042050E ERZ042053E
new CD entry client when the remote system
reconnects. CD entry sysId remains in the region,
unused and unusable, until the region is restarted. This,
in itself, does not cause problems in your region.
However, the CD entry is using region storage so, if this
message occurs frequently, other transactions can
possibly fail due to lack of storage.
System action:
CICS cannot delete the CD entry for the remote system.
The CCIN transaction completes.
version of DFHCCINX it means that either the CCIN

Transient Data Definition (TDD) entry for CCIN is
missing, or the program was compiled with a different
parameter structure than the one used by CICS.
System action:
CICS abnormally terminates the CCIN transaction and
the CD entry is not installed in the region. Additional
messages are logged indicating the abend code used
by DFHCCINX.
User response:
If this message occurs frequently, alter the applications
that are using the CD entry so they use the CD entry for
as short a time as possible.
User response:
Examine the logic for program DFHCCINX to determine
why it abnormally terminated. Correct the cause of the
error and retry the connection request from the remote
system.
Destination:
CSMT
Destination:
CSMT
ERZ042050E The CCIN transaction has abnormally

terminated with abend code
abendCode
ERZ042052W DFHCCINX abnormally terminated

during the delete of autoinstalled CD
entry sysId
Explanation:
The CICS to CICS install transaction, CCIN, has
abnormally terminated. This can be because:
Explanation:
The CICS-supplied program, DFHCCINX abnormally
terminated while processing a delete of
Communications Definitions (CD) entry sysId. If you are
using the supplied version of DFHCCINX it means that
either the CCIN Transient Data Definition (TDD) entry
for CCIN is missing, or the program was compiled with
a different parameter structure than the one used by
CICS.
v CCIN was invoked incorrectly.

v CCIN was unable to acquire sufficient storage to
process the request.
v The remote system has sent unrecognized data to
CICS.
v The connection between the remote system and
CICS failed.
v The user exit DFHCCINX abnormally terminated.
System action:
A symptom record (symrec) is created and further

messages can be logged to CSMT. These provide
additional information about the cause of the problem.
User response:
If DFHCCINX maintains any data about autoinstalled
CD entries, this data is now possibly inconsistent.
Examine the logic for DFHCCINX to determine if the
program abend has affected your region.
System action:
CICS abnormally terminates the CCIN transaction with
abend code abendCode.
Destination:
CSMT
User response:
abendCode and any additional messages logged to
CSMT. If you can not solve the problem yourself, save
the CSMT log, console.msg file and the symrec file and
Destination:
CSMT
ERZ042051E DFHCCINX abnormally terminated
during the autoinstall of CD entry
sysId for remote system LUname
Explanation:
The CICS-supplied program, DFHCCINX abnormally
terminated while processing an autoinstall request for
remote system LUname. If you are using the supplied
332
ERZ042053E Unable to link to program DFHCCINX

for the autoinstall of CD entry sysId
for remote system LUname
Explanation:
There is an error in the Program Definition (PD) entry
for the DFHCCINX program. This means CICS is
unable to process the autoinstall of a Communications
Definition (CD) entry for remote system LUname.
System action:
CICS abnormally terminates the CCIN transaction and a
CD entry is not installed. CICS sends a response to the
remote system indicating that it is busy and the remote
system can retry the connection request later. Additional
messages can be logged that describe the problem with
the PD entry.
User response:
ERZ042054I ERZ042056W
Correct the PD entry for DFHCCINX and install it in
your region. Then retry the connection request from the
remote system. Refer to the TXSeries for Multiplatforms
DFHCCINX and its PD entry.
Destination:
CSMT
ERZ042054I DFHCCINX has vetoed the autoinstall
of CD entry sysId which has
RemoteLUName set to LUname
Explanation:
The DFHCCINX program was called to validate the
autoinstall of Communications Definition (CD) entry
sysId. It returned a response indicating that CICS is not
supposed to autoinstall this CD entry.
System action:
CICS does not perform the autoinstall request. A
response is send to the remote system indicating that
the autoinstall request was cancelled.
User response:
If the remote system is not allowed to contact your
CICS region, no further action is required. If the remote
system is able to contact the local region, either:
v Alter the DFHCCINX program to allow this remote
system to connect to your region. The TXSeries for
how to configure, write and install a new version of
the DFHCCINX program.
v the code page specified in the RemoteCodePageTR

attribute of the default Communications Definition
(CD) entry is and
v data conversion routines are not available for
conversion between the local code page and the
code page, if any, received from the remote system.
No data conversion can be performed for transaction
routing requests sent between the local region and the
remote system.
System action:
CICS installs a CD entry for the remote system in the
region. The RemoteCodePageTR attribute for this CD
entry is set to the local code page so no data
conversion is performed. CICS sends a bad response to
the remote system indicating the code page is invalid.
User response:
If your region is using the supplied version of
DFHCCINX, modify the RemoteCodePageTR attribute
in the default CD entry to a code page that is suitable
for the remote system. Disconnect the remote system
from your region to uninstall the remote systems CD
entry. When the remote system reconnects, it uses the
new value in RemoteCodePageTR as the remote
systems code page. If your region is not using the
supplied version of DFHCCINX, examine the code for
your regions DFHCCINX to determine why it returned
CICS_CCINX_RETURNCODE_BADCP. For more information on
DFHCCINX refer to the TXSeries for Multiplatforms
or
Destination:
CSMT
v If the remote system is a CICS region, define a CD

entry for it. Then DFHCCINX is not called. The
TXSeries for Multiplatforms Intercommunication
Guide describes how to configure CD entries.
ERZ042056W CD entry sysId for EBCDIC system

LUname is configured with ASCII code
page codePage
Once you have made the necessary changes to your

region, retry the connection request from the remote
system.
Destination:
CSMT
ERZ042055I The code page for autoinstall of CD
entry sysId which has RemoteLUName
set to LUname is invalid. The code
page received from the remote system
was receivedCodePage, the default
code page is defaultCodePage and the
local code page is localCodePage
Explanation:
The DFHCCINX program indicates that the code page
for autoinstalled Communications Definition (CD) entry
sysId is not supported by the local system. If your
region is using the supplied version of DFHCCINX, it
means that:
Explanation:
CICS has opened a connection to remote system
LUname using the information in Communications
Definition (CD) entry sysId. This remote system uses
EBCDIC code pages for transaction routing. However,
CD entry sysId is configured with an ASCII code page
codePage in attribute RemoteCodePageTR. CICS is not
able to correctly interpret transaction routing data
received from this remote system.
System action:
The connection is acquired. However, transaction
routing requests on this connection fail.
User response:
Alter the RemoteCodePageTR attribute in CD entry
sysId so that it specifies the same EBCDIC code page
as defined for the connection in remote system
LUname. The TXSeries for Multiplatforms
Intercommunication Guide describes what values to use
in the RemoteCodePageTR attribute and describes how
to update the CD entry.
333
ERZ042057E ERZ042061E
Destination:
console.msg
System action:
CICS sends a response to the remote CICS region
indicating that it can not accept the connection request.
ERZ042057E SYSID sysId requested by DFHCCINX

already exists in the WD
User response:
Alter the APPLID used by the CICS client. Then the
remote CICS region can connect to your region.
Explanation:
The SYSID sysId returned by the autoinstall program
DFHCCINX is the same as the TERMID (key) of an
existing Terminal Definition (WD) entry.
System action:
CICS calls DFHCCINX indicating that the CD entry is
being deleted. A new CD entry is not added for the
remote system.
User response:
Change DFHCCINX to return another SYSID or to use
the SYSID passed to it by CICS. Alternatively change
the TERMID for WD entry sysId.
Destination:
CSMT
ERZ042058E A CICS Client has requested APPLID
applId which is defined in server CD
entry sysId
Explanation:
An CICS client is using APPLID applId that matches the
attributes of Communications Definitions (CD) entry
sysId. However, CD entry sysId is defined for a remote
CICS region (server). CICS is unable to install a CD
entry for the CICS client because it cannot distinguish
between requests for the remote CICS region and the
CICS client.
System action:
CICS sends a response to the CICS client indicating
that it can not accept the connection request.
User response:
Examine CD entry sysId. If this CD entry defines a
remote CICS region that is able to connect to your
region then alter the APPLID used by the CICS client.
Alternatively, delete CD entry sysId from your region
and the CICS client is then able to connect using
APPLID applId.
Destination:
CSMT
ERZ042059E Remote CICS region, LUname, has the
same name as the CICS client using
CD entry sysId
Explanation:
An CICS client is using APPLID LUname and
Communications Definitions (CD) entry sysId. This
APPLID is the name of a remote CICS region (server)
that is trying to autoinstall a CD entry in the local region.
CICS is unable to install a CD entry for the remote
CICS region as it cannot distinguish between requests
for the remote CICS region and the CICS client.
334
Note: If you are unable to identify the CICS client that

is using APPLID LUname and you wish the
remote region to connect to your region rather
that the CICS client then define a CD entry for
the remote CICS region and delete CD entry
sysId. Then the next time the CICS client
connects to your region, the request fails. The
owner of the failing CICS client then reports the
error or changes the CICS clients APPLID.
Destination:
CSMT
primaryCode/secondaryCode detected by
CTIN transaction
Explanation:
The CICS client terminal install transaction, CTIN,
detected a communications error with the client system.
System action:
CICS abnormally terminates the CTIN transaction.
User response:
Ensure that the client system is still available and restart
it if necessary. Refer to the TXSeries for Multiplatforms
Intercommunication Guide for further information on the
error codes primaryCode/secondaryCode.
Destination:
CSMT
ERZ042061E
RemoteLUName attribute
remoteLUname in CD entry sysId is not
the name of remote system
remoteSystem
Explanation:
CICS has opened a connection to a remote system
using the information in Communications Definition (CD)
entry sysId. However, CICS is unable to communicate
with this remote system as the RemoteLUName
attribute in the CD entry defined the name of the remote
system as remoteLUname whereas the remote system
is actually called remoteSystem.
This is possibly because:
v The location of the remote system configured in CD
entry sysId is incorrect.
v The remote system is CICS OS/2 and was just
upgraded from version 2 to version 3. This upgrade
changes the name of the CICS OS/2 system.
ERZ042062W ERZ042064E
v The name of the remote system is incorrectly
configured in CD entry sysId.
User response:
Examine CD entry sysId and either:
CICS has received a connection request from a remote

system using the TCP/IP address and port configured in
Communications Definition (CD) entry sysId. However,
CICS is unable to communicate with this remote system
as the RemoteLUName attribute in the CD entry defined
the name of the remote system as remoteLUname
whereas the remote system is actually called
remoteSystem.
v Alter CD entry sysId so that RemoteLUName is set to

remoteSystem.
This is possibly because:
or
v The location of the remote system configured in CD

entry sysId is incorrect.
v Alter the RemoteTCPAddress, RemoteTCPPort and

ListenerName attributes in CD entry sysId to contain
the location of remote system remoteLUname.
v The remote system is CICS OS/2 and was just

upgraded from version 2 to version 3. This upgrade
changes the name of the CICS OS/2 system.
System action:
CICS closes the connection to the remote system.
Install the updated CD entry into your region and rerun

the connection request. The TXSeries for Multiplatforms
Intercommunication Guide describes how to update CD
entries in your region.
Destination:
console.msg
ERZ042062W RemoteCodePageTR attribute
remoteCodePageTR in CD entry sysId is
not the same as code page
receivedCodePage received from
remote system remoteSystem
Explanation:
CICS is opening a connection to remote system
remoteSystem using the information in Communications
Definition (CD) entry sysId. However, remote system
remoteSystem is reporting its code page as
receivedCodePage whereas the RemoteCodePageTR
attribute in CD entry sysId is remoteCodePageTR. This
means transaction routing data conversion can possibly
fail on this connection.
System action:
The connection is acquired. However, transaction
routing requests on this connection can possibly fail.
User response:
Alter the RemoteCodePageTR attribute in CD entry
remoteCodePageTR so that it specifies code page
receivedCodePage. The TXSeries for Multiplatforms
Intercommunication Guide describes what values to use
in the RemoteCodePageTR attribute and describes how
to update the CD entry.
Destination:
console.msg
ERZ042063E
Explanation:
RemoteLUName attribute
remoteLUname in CD entry sysId is not
the name of remote system
remoteSystem
v The remote system is CICS OS/2 version 2 and it is

using multiple TCP/IP network adapters. This can
alter the name of the remote system each time it
attaches.
v The name of the remote system is incorrectly
configured in CD entry sysId.
System action:
CICS closes the connection to the remote system.
User response:
Examine CD entry sysId and either
v Alter CD entry sysId so that RemoteLUName is set to
remoteSystem.
or
v Alter the RemoteTCPAddress, RemoteTCPPort and
ListenerName attributes in CD entry sysId to contain
the location of remote system remoteLUname.
or
v Delete CD entry sysId. When the remote system next
connects, CICS autoinstalls a new CD entry for it.
Once your have made changes to the configuration
rerun the connection request. The TXSeries for
to update CD entries in your region.
Destination:
console.msg
ERZ042064E Cannot autoinstall terminal with
NETNAME netname - already in use
Explanation:
attempted to autoinstall a terminal using NETNAME
netname, but was unsuccessful because a terminal is
already installed using this NETNAME.
System action:
performed.
335
ERZ042065I ERZ043003E
User response:
Install the terminal using a different NETNAME, or do
not specify a NETNAME, so that CICS generates a
unique one for it.
Destination:
CSMT
ERZ042065I The password option, passwordOption,
requested by DFHCCINX for client
sysId will be ignored
Explanation:
The CICS supplied program DFHCCINX is called each
time an IBM CICS Client connects to the region. This
program is able to specify the attributes of the
Communications Definition (CD) entry that is
auto-installed by CICS for the client. One of the
attributes DFHCCINX can specify is how passwords
sent by the client are managed by CICS. In this case,
the value, passwordOption, specified by DFHCCINX for
client sysId is ignored because the value for the
RemoteSysSecurity attribute that was also requested by
DFHCCINX was not verify. Password management can
only be controlled if RemoteSysSecurity=verify.
The passwordOption value is specified in the
RemoteSysSecurity field of the COMMAREA returned
by DFHCCINX. The correct values for this field are
defined in the header file for this program called
cics_ccinx.h.
System action:
CICS continues processing. The CD entry is
successfully auto_installed.
User response:
Examine the configuration in the remote system, your
SNA service and CD entry sysId and alter it so it is
consistent and provides enough security information for
the intersystem request to execute on the remote
system.
Destination:
CSMT
ERZ043002E Remote transaction transId was not
accepted by the remote server within
the timeout specified in CD entry
sysId
Explanation:
The remote transaction transId did not start on the
remote CICS region or PPC Gateway server within the
timeout specified by the AllocateTimeout attribute of the
Communications Definition (CD) entry sysId.
System action:
Further messages can possibly be logged.
User response:
Examine the message files on the remote system and
on the local system to obtain further information as to
why the remote transaction did not start within the
timeout period. If the remote transaction was unable to
be started because the remote system does not have
enough application servers, increase the number of
available Application Servers in the remote system by
either:
v amending the MaxServer attribute in the remote
systems Region Definition (RD) entry).
User response:
No action is required. This message is for information
only.
v using the CEMT SET TCLASS MAXSERVERS

command on the remote system.
Destination:
CSMT
Alternatively, consider increasing the value of the

AllocateTimeout attribute in the CD entry.
ERZ043001W The OutboundUserIds field in CD

entry sysId is incorrect
Explanation:
The OutboundUserIds attribute in the Communications
Definition (CD) entry, sysId, is inconsistent with the
configuration in either the remote system or your SNA
service .
The OutboundUserIds attribute determines whether
CICS sends userids with outbound intersystem
requests. This message occurs if
OutboundUserIds=sent and the remote system is not
configured to receive userids. Refer to the TXSeries for
Multiplatforms Intercommunication Guide for more
information.
System action:
CICS sends the intersystem request without a userid.
336
If you need further information, see the TXSeries for

Destination:
CSMT
ERZ043003E An unexpected error (errorCode)
occurred during intersystems
communication to system sysId.
Explanation:
An attempt has been made to flow invalid data during
intersystems communication.
System action:
User response:
Refer to the errorCode for the cause of the problem.
Destination:
ERZ043004E ERZ043009E
CSMT
System action:
CICS abnormally terminates the transaction with A43D.
ERZ043004E An unexpected error (errorCode)

occurred during intersystems
communication to system sysId
User response:
Make any of the corrections to the Region Definitions
(RD) and Communication Definitions (CD) as described
above and then restart the region.
Explanation:
An error was detected while communicating with the
remote system sysId.
System action:
code A43B.
User response:
available.
Destination:
CSMT
ERZ043005E An inconsistency has been detected
in a CICS internal data structure
Explanation:
System action:
The region continues, but intersystems communication
can possibly be unsuccessful.
User response:
Restart your region. If the condition persists, perform a
system dump and contact your support organization.
Destination:
console.msg
ERZ043006I Communications switch layer
successfully initialized.
Explanation:
Communications switch layer successfully initialized.
System action:
CICS continues.
User response:
None
Destination:
console.msg
ERZ043007E The remote system sysId is not
known locally
Explanation:
An attempt has been made to contact a system that is
not known locally. This is because the LocalSysId is
null, or the sysId is the LocalSysId, or the
RemoteLUName is the same as the local region name
or the PPC Gateway has been restarted since the
region started.
Destination:
CSMT
ERZ043008E An asynchronous backout occurred
during intersystems communication
with system sysId
Explanation:
The transaction was backed out by a remote server or
application while it was communicating with the remote
system defined in Communications Definition (CD) entry
sysId. Possible reasons for this include:
v The transaction on the remote region was force
purged or abnormally terminated.
v A remote SFS server experienced an error or was
terminated prematurely.
v A PPC Gateway server experienced an error or was
terminated prematurely.
v The transaction is communicating with an application
that issued a tran_Abort call. This is not permitted
while the distributed logical unit of work (LUW) is
using a PPC Gateway server or a PPC TCP/IP
connection.
v The Remote Procedure Call (RPC) mechanism is
unavailable.
System action:
code A43E. All synchronization level 2 conversations
are abnormally terminated.
User response:
Examine the messages produced by all the applications
and servers involved in the distributed LUW. This
includes PPC gateway Servers, Structured File Servers
(SFS) and CICS on Open Systems regions. If any of
these has reported errors, correct the cause of these
errors and rerun the transaction. Look for incorrect
parameters being passed to CICS, timeouts expiring or,
if your application includes a remote CICS application,
then ensure it is not issuing a tran_Abort command.
Rerun the transaction once it has been corrected.
Destination:
CSMT
ERZ043009E Local SNA must be initialized before
transaction transId can use CD entry
sysId
Explanation:
Transaction transId made an intersystem request that
specified Communications Definition (CD) entry sysId.
This CD entry is configured with
337
ERZ043010E ERZ043011E
ConnectionType=local_sna, which means the
connection is to use Local SNA support. However, the
Local SNA support is unavailable either because:
v a Listener Definition (LD) entry with Protocol=SNA is
not defined, or
v the SNA product used by your region is not installed
or configured correctly.
System action:
User response:
v Check that an appropriate SNA product is installed on
your machine.
v Check this SNA product is correctly configured. The
TXSeries for Multiplatforms Intercommunication
Guide describes how to configure each SNA product.
v Ensure that a LD entry exists that has Protocol=SNA.
Guide describes how to configure Local SNA support.
Once Local SNA is configured, ensure that the Local
SNA support activated successfully during region
initialization. Then rerun the request.
Destination:
console.msg
ERZ043010E Modename modeName configured in
TD entry transId is unavailable for
connecting to remote system sysId
Explanation:
Transaction transId issued an intersystem request to the
(CD) entry sysId. However, this request was
unsuccessful because the modename modeName
configured in the SNAModeName attribute of
Transaction Definitions (TD) entry transId is not
correctly defined in either the local SNA product or the
remote system.
This problem can be caused because:
v The modename has been specified incorrectly in TD
entry transId.
v The CD entry sysId is not configured with the correct
remote system information in the RemoteLUName,
RemoteNetworkName and SNAConnectName
attributes.
v The local SNA product does not have the modename
modeName defined.
v The modename is SNASVCMG or CPSVCMG and so

cannot be used by CICS transactions.
System action:
User response:
Examine CD entry sysId and the SNA configuration in
your local SNA product and the remote system. You are
looking for inconsistencies within this configuration.
Ensure that:
v The modename modeName used in the TD entry
transId is correctly configured in both the local SNA
product and the remote system.
v CD entry sysId specifies the correct remote system.
Check the settings of the RemoteLUName,
attributes.
v The configuration in the local SNA product for the
remote system is correct and complete. Take special
care that any partner LU aliases defined correctly
map to the name of the remote system. Also check
that where partner LU aliases are required, they are
defined.
Once any necessary corrections have been made, rerun
the request.
Guide provides more information on the use of
modenames by CICS.
Destination:
CSMT
ERZ043011E Modename modeName is unavailable
for connecting to remote system sysId
Explanation:
the modename modeName configured in the
DefaultSNAModeName attribute of this CD entry is not
correctly defined in either the local SNA product or the
remote system.
v The modename has been specified incorrectly in the
CD entry.
v The local SNA product does not have the remote

system correctly defined.
v The CD entry is not configured with the correct

attributes.
v The remote system does not have the modename

modeName defined.
v The local SNA product does not have the modename

modeName defined.
v The definition of modename modeName in the local

SNA product is inconsistent with the definition of this
modename in the remote system.

338
ERZ043012E ERZ043014E
v The remote system does not have the modename
modeName defined.
v The definition of modename modeName in the local
SNA product is inconsistent with the definition of this
v The modename is SNASVCMG or CPSVCMG and so
cannot be used by CICS transactions.
System action:
User response:
your local SNA product and the remote system. You are
looking for inconsistencies within this configuration.
Ensure that:
v The local SNA product does not have a default

modename defined or does not support the definition
of a default modename.
v The remote system does not have the local SNA
products default modename defined.
v The definition of this modename in the local SNA
product is inconsistent with the definition of the
v The default modename is SNASVCMG or CPSVCMG
and so cannot be used by CICS transactions.
System action:
v The modename used in the CD entry is correctly

configured in both the local SNA product and the
remote system.
User response:
both your local SNA product and the remote system.
You are looking for inconsistencies within this
configuration. Ensure that:
v The CD entry specifies the correct remote system.

attributes.
v CD entry sysId specifies the correct remote system.

attributes.

defined.

defined.

the request.
Once you are sure the correct remote system is being

contacted, look at the setting of the default modename
in your SNA product. Refer to the TXSeries for
about how this is configured. Make sure it is set to a
modename that can be used to contact most, if not all,
of the remote systems used by your region.

Guide provides more information on the use of
modenames by CICS.
Destination:
CSMT
ERZ043012E Default modename configured in local
SNA product is unavailable for
connecting to remote system sysId
Explanation:
the default modename is not correctly configured in
either the local SNA product or the remote system.
v The CD entry sysId is not configured with the correct
attributes.
If the default modename for your SNA product is not

recognized by the remote system configured in CD
entry sysId, set the DefaultSNAModeName in CD entry
sysId to a modename that is configured in both the
remote system and the local SNA product.
the request.
Destination:
CSMT
ERZ043014E Transaction transId issued an
intersystem request to system sysId
when a backout was required
Explanation:
CICS is unable to proceed with an intersystem request
to the remote system configured in Communications
Definition (CD) entry sysId because the transaction that
issued the request, transId, is in backout required
state.
339
ERZ043015I ERZ043017E
Backout required state (sometimes referred to as
rollback required state) occurs when a transaction
receives a backout request from a remote system or
when a synchronization level 2 intersystem request is
abnormally terminated. (Refer to the TXSeries for
Multiplatforms Intercommunication Guide for an
explanation of when synchronization level 2 intersystem
requests are used and their implications.)
When a transaction is in Backout required state it can
not start new synchronization level 2 intersystem
requests. In addition, all Distributed Transaction
Processing (DTP) synchronization level 2 conversations
controlled by the transaction switch to rollback state,
which effectively prevents work on these conversations.
(Refer to the TXSeries for Multiplatforms
Intercommunication Guide for information on the DTP
commands and resulting conversation states.)
The Backout required state is cleared when a
transaction issues an EXEC CICS SYNCPOINT
ROLLBACK command. This backs out changes to
recoverable resources and allow synchronization level 2
requests to proceed. (The TXSeries for Multiplatforms
Application Programming Reference describes the
EXEC CICS SYNCPOINT ROLLBACK command.)
System action:
User response:
Look for additional messages written to the CSMT log
for transaction transId. These can help you identify
which intersystem request issued by the transaction was
unsuccessful. Examine the application code for
transaction transId. Try to locate the intersystem request
that caused the transaction to enter backout required
state. Correct the error processing associated with this
intersystem request so that EXEC CICS SYNCPOINT
ROLLBACK is issued whenever an error occurs that
puts the transaction into backout required state.
Destination:
CSMT
ERZ043015I The default modename for the region
is modeName
Explanation:
CICS has read the modename modeName from the
CICS_SNA_DEFAULT_MODE environment variable.
This modename has been truncated to 10 characters.
ERZ043016W The modeName modename should

not be used by CICS transactions
Explanation:
The modeName modename is a reserved SNA
modename used by SNA service transactions. It must
not be used by CICS transactions, as this can impact
the management of the SNA network. Some SNA
products prohibit the use of this modename.
System action:
CICS continues processing. Subsequent intersystem
requests using this modename can possibly be
unsuccessful.
User response:
Change the configuration in your CICS region to ensure
that the modenames used by your transactions are not
the reserved SNA modenames, SNASVCMG or
CPSVCMG. The TXSeries for Multiplatforms
modenames in CICS.
Destination:
console.msg or CSMT
ERZ043017E The modeName modename specified
in CICS_SNA_DEFAULT_MODE is
unavailable for connecting to remote
system sysId
Explanation:
the default modename modeName specified in the
CICS_SNA_DEFAULT_MODE environment variable is
not correctly configured in either the local SNA product
or the remote system.
v The CD entry modeName is not configured with the
correct remote system information in the
RemoteLUName, RemoteNetworkName and
SNAConnectName attributes.
v The remote system does not have this default
modename defined.
v The definition of this modename in the local SNA
product is inconsistent with the definition of the
System action:
v The default modename is SNASVCMG or CPSVCMG

and so cannot be used by CICS transactions.
User response:
None.
System action:
Destination:
console.msg
340
User response:
Examine CD entry modeName and the SNA
configuration in both your local SNA product and the
ERZ044026E ERZ045003E
remote system. You are looking for inconsistencies
within this configuration. Ensure that:
v CD entry modeName specifies the correct remote
system. Check the settings of the RemoteLUName,
attributes.
defined.
Once you are sure the correct remote system is being
contacted, check that the default mode name is
consistently defined both in your local SNA product and
in the remote system.
If the default modename for your SNA product is not
recognized by the remote system configured in CD
entry modeName you can choose to change the default
modename or set the DefaultSNAModeName in CD
entry sysId to a modename that is configured in both
the remote system and the local SNA product.
Guide has more information on the modenames used
by CICS transactions.
the request.
Destination:
CSMT
CICS IP Listener component
Explanation:
During region initialization CICS IP Listener component
was unable to obtain sufficient storage from the Region
Pool to initialize correctly.
System action:
User response:
Destination:
console.msg
ERZ045001I Unsuccessful Resource Security Level
(RSL) access for resource
resourceName, class className,
userid userId, transaction id transId
Explanation:
User userId is attempting to access resource

resourceName in resource class className from
within transaction transId. Probably the user userId, or
the transaction transId, does not have the required
RSL key to access this resource. Alternatively, in a
multiregion environment, the communications link
possibly does not have the required RSL key to access
this resource.
System action:
The program determines how CICS handles this error.
User response:
Check that the RSL key for the userid, the transaction,
and the communications link, if applicable, match the
RSL Key for the resource being accessed.
Destination:
CSMT
ERZ045002W No such resource resourceName,
class className
Explanation:
A transaction attempted to access a resource that does
not exist.
System action:
User response:
The transaction program determines how CICS handles
this error. Check transaction programs for resource
names that have been withdrawn from the regions
definitions.
Destination:
CSMT
ERZ045003E A transaction (transId) attempted to
start with an invalid
StartType/FacilityType combination
Explanation:
A transaction was unable to be started because the way
in which it was started, or the facility it was started
against, conflicts with the start methods or the facility
values specified in the InvocationMode attribute of the
transaction definition.
System action:
The transaction is not started.
User response:
Check the InvocationMode of the transaction definition
to ensure that transaction is configured with the
appropriate StartType and FacilityType for its operating
environment. The TXSeries for Multiplatforms
Administration Reference provides guidance on setting
a transactions InvocationMode. Some of the CICS
supplied transactions can be started only by particular
methods or against particular facilities. Do not change
the InvocationMode attributes of the CICS supplied
transactions.
341
ERZ045004E ERZ045012E
Destination:
console.msg
ERZ045004E Unsuccessful Transaction Security
Level (TSL) access for user userId,
transaction transId
Explanation:
User userId attempted to run transaction transId. The
user probably does not have the required TSL key to
run this transaction. Alternatively, in a multi-region
environment, the communications link possibly does not
have the required TSL key to run this transaction.
System action:
CICS prevents access to the named transaction.
User response:
Check that the TSL key for the userid, and the
communications link in a multi-region environment,
match the TSL Key for the transaction.
Destination:
CSMT
ERZ045005E A transaction attempted to start at an
inappropriate execution phase in the
region
Explanation:
CICS operates in a number of execution phases. A
transaction definition defines the execution phases a
transaction can run in and CICS sets an appropriate
indication of which execution phase the region is
currently operating at. A transaction cannot start if the
region is not executing in a phase defined by the
transactions definition.
System action:
The transaction is not started.
attributes in the Communications Definitions, and not

related to the DefaultUserId keys.
System action:
CICS generates a warning message to indicate a
possible security problem and grants public access.
User response:
A User Definitions entry for this user identifier can be
created if more specific access controls are required.
The TXSeries for Multiplatforms Administration
Reference provides guidance on resource definition
attributes and how to modify existing definitions.
Destination:
CSMT
ERZ045011E U4511: External Security Manager
could not be loaded
Explanation:
CICS did not load the External Security Manager
correctly.
System action:
User response:
Suitable actions include checking that:
v the Region Definitions identify the location and name
of the ESM module correctly
v the identified directory and file exist
v the directory and file permissions for the module file
are correct
v the ESM module has been compiled and linked
correctly
Destination:
console.msg
User response:
Check that the set of execution phases defined for a
transaction is suitable for the execution phase that the
region is in when the transaction is started. The
TXSeries for Multiplatforms Administration Reference
provides guidance on resource definition attributes and
how to modify existing definitions.
ERZ045012E U4512: External Security Manager

(ESM) initialization error, return code
returnCode
Destination:
console.msg
System action:
ERZ045006W User identity userId is not defined in

this Region. PUBLIC access granted
User response:
Check error code returnCode in the source and
documentation for the ESM to identify the nature of this
problem.
Explanation:
User identity userId, supplied when CICS scheduled a
Transaction Security Level (TSL) check, is not defined
in the User Definitions for the region. In the case where
this message is issued due to a shipped or routed
transaction, if the link is defined with
RemoteSysSecurity=local and there is no LinkUserId,
then tasks run as the default userid, but the security is
determined by the TSLKeyMask and RSLKeyMask
342
Explanation:
CICS loaded the ESM module, but returned error
returnCode when running the ESM entry function.
Destination:
console.msg
ERZ045013E ERZ045080W
ERZ045013E External Security Manager (ESM)
Resource Security Level (RSL) check
unsuccessful
Explanation:
The ESM callback function, used to perform resource
security checking returned an error code.
System action:
CICS abnormally terminates the application server.
User response:
Check the source and documentation for the ESM to
identify the nature of this problem.
Destination:
console.msg
User response:
None
Destination:
console.msg
ERZ045078I Finished validating transaction security
levels
Explanation:
CICS has finished checking for inconsistencies in the
RD and TD databases.
System action:
User response:
None
ERZ045014E External Security Manager (ESM)

Transaction Security Level (TSL) check
unsuccessful
Destination:
console.msg
Explanation:
The ESM callback function, used to perform transaction
security checking, returned an error code.
ERZ045079W User Definition userId has same

name as region. Internal security for
this user will allow only TSL/RSL
public access.
System action:
User response:
Check the source and documentation for the ESM to
identify the nature of this problem.
Destination:
console.msg
ERZ045016E CICS was unable to authenticate user
userId at terminal termId
Explanation:
User userId operating from principal facility termId
attempted to sign on to the region.
System action:
The sign on attempt does not succeed. CICS logs the
error and prevents the user from accessing the region
as user identity userId.
User response:
Check with user userId (if he or she exists) about this
sign on attempt as there was possibly an attempt to
breach the security of the region by someone
masquerading as user userId.
Destination:
console.msg
ERZ045077I Validating transaction security levels
Explanation:
CICS is starting a check for inconsistencies in the RD
and TD databases.
System action:
Explanation:
The User Definition userId has been defined with a key
which is the same as the name of the CICS region. This
can have unpredictable results and is not advised. The
user is allowed access only to resources with public
RSL/TSL keys.
System action:
The RSLKeyList and TSLKeyList attributes for that user
are changed to public.
User response:
Consider changing the key for that User Definition.
Destination:
console.msg
ERZ045080W Transaction transId will use internal
security for resources whose type is
marked internal in the RD database
Explanation:
There is a conflict of security parameters in the Region
Definitions (RD) and Transaction Definitions (TD) for the
region. Transaction transId is configured in the
Transaction Definitions to use external security. One or
more of the Region Definition attributes FileRSLCheck,
TransientDataRSLCheck, TemporaryStorageRSLCheck,
JournalRSLCheck, ProgramRSLCheck or
TransactionRSLCheck specify that external security is
not to be used.
System action:
CICS uses internal security as required by the Region
Definitions even though external security has been
selected in the TD database.
User response:
343
ERZ045081W ERZ045109I
Consider whether the region configuration is correct.
Destination:
console.msg
ERZ045081W Transaction transId will use internal
security for transaction transId
Explanation:
There is a conflict of security parameters in the Region
Definitions (RD). CICS uses internal security checking
when RSLCheck or TSLCheck is external, but
ESMLoad=no in the RD database.
ERZ045084E The principal principalName that was

specified for user userName is
incorrectly specified. This user is
ignored.
Explanation:
The principal that was specified on the Principal
attribute of a user definition is bad. Principals that start
with a / must begin with either /.:/ for the local cell or
/.../ for a global name.
System action:
System action:
If this message is produced during initialization, this
user is ignored. It is not recognized by CICS. If this
message is produced while adding a user by using
cicsadd, then the addition fails.
User response:
None
User response:
Correct the users principal and try again.
Destination:
console.msg
Destination:
console.msg
ERZ045082E CICS has run out of storage

specified for user userName is also
specified for user userName. This
user userName is ignored.
Explanation:
CICS has failed to allocate storage and cannot
continue.
System action:
The region abnormally terminates.
User response:
Check the values of the MaxRegionPool,
MaxTaskPrivatePool and MaxTSHPool region database
attributes. Increase these values and try again.
Destination:
console.msg
specified for user userName is too
long. This user is ignored.
Explanation:
The principal that was specified on the Principal
attribute of a user definition is too long. CICS expands
the principal to a global name starting /.../. This fully
qualified principal must be no longer than 256 bytes.
System action:
User response:
Shorten the users principal to a valid length and try
again.
Destination:
console.msg
344
Explanation:
The user that is being added has the same principal as
another user already defined to CICS. All users must
have different principals.
System action:
User response:
Create a new principal for this user and try again.
Destination:
console.msg
ERZ045109I CICS has added the principal
principalName with its account. The
key table file fileName has also been
added.
Explanation:
cicssetupclients has added the principal, account and
key table file it needs for the CICS terminal.
System action:
cicssetupclients continues processing.
User response:
None. This message is output for information only.
Destination:
stderr
ERZ045113E ERZ045134E
ERZ045113E CICS could not change the group
ownership of the key table file
fileName to cicsterm
Explanation:
cicssetupclients attempted to change the group
ownership of the named file to the group cicsterm, but
failed.
System action:
cicssetupclients stops immediately.
User response:
Use the message output by chgrp to correct the
problem and try again.
Destination:
stderr
ERZ045117W User identity for the LinkUserId
userId is not defined in this Region.
PUBLIC access granted for the link.
Explanation:
User identity for the LinkUserId userId, supplied when
CICS scheduled a Transaction Security Level (TSL)
check, is not defined in the User Definitions for the
region. This can be valid, for example, due to a shipped
or routed transaction.
System action:
CICS generates a warning message to indicate a
possible security problem and grants public access for
the link.
User response:
The LinkUserId is specified on the remote systems
Communications Definitions. A User Definitions entry for
this user identifier can be created if more specific
access controls are required for the link. The TXSeries
for Multiplatforms Administration Reference provides
guidance on resource definition attributes and how to
modify existing definitions. If you wish the RSLKeyMask
and TSLKeyMask to be used to determine the link
security instead of the LinkUserId, set LinkUserId= in
the Communications Definitions for the remote system.
Destination:
console.msg
ERZ045120W The database entry for the default
CICS user userId is being deleted
Explanation:
A request was made to delete the user userId from the
CICS runtime database. This user is defined as being
the default user for this region. Any client requests
received by the scheduler that do not come from a user
who has an entry in the CICS Runtime Database are
rejected.
System action:
The delete of the user from the database continues.
If client requests are made from users that have no

matching entry in the CICS Runtime Database, add an
entry for the CICS Default user back into the Database.
Destination:
console.msg
ERZ045121E Error trying to change users
password
Explanation:
You have tried to change your password, but there was
an error with a call.
System action:
The attempt to change password is abnormally
terminated. Your password is not changed.
User response:
Check that you have supplied the correct current
password for the user. Check also that the new
password is valid and that you are authorized to change
the password.
Destination:
console.msg
ERZ045133E Unable to update /etc/inittab
Explanation:
cicssetupclients made a call to mkitab to update
/etc/inittab in order to cause $CICS/etc/rc.cics to
be run at system restart. This call failed. The entry is
necessary to ensure that the 3270 terminal subsystem
used by cicsterm is initialized.
System action:
cicssetupclients exits without updating /etc/inittab.
User response:
Correct any problems indicated by mkitab. Then run
cicssetupclients again using the -m option. Alternatively
run $CICS/etc/rc.cics each time that the machine is
restarted.
Destination:
stderr
ERZ045134E Unable to change users CICS
password
Explanation:
The user has tried to change his or her CICS password
using the CESN transaction but CICS was unable to
change the password stored in its database.
System action:
The attempt to change the password is abnormally
terminated. The password is not changed.
User response:
Check that the file system holding the regions
definitions is not full. Then retry the operation.
Destination:
User response:
345
ERZ045135E ERZ046003E
console.msg
ERZ045135E New password is not a valid CICS
password
Explanation:
The user has tried to change his or her CICS password
using the CESN transaction but CICS was unable to
encrypt the supplied password.
System action:
terminated. The password is not changed.
User response:
Check that the new password is not longer than 8
characters. Then retry the operation.
Destination:
console.msg
ERZ045136E Attempt to change CICS password left
database inconsistent
Explanation:
The user has tried to change their CICS password using
the CESN transaction but CICS encountered difficulties
in updating its database. The permanent database entry
for the user in the regions User Definitions (UD) and
the corresponding warm start database entry were
possibly altered to contain the new password, but this
change has not been made for the active system.
System action:
terminated. The password is not changed now but can
possibly be changed when the region is restarted either
with a warm or a cold start.
User response:
Check that the file system holding the regions
definitions is not full. Then retry the operation. If the
operation again fails it is possibly necessary to reset the
password by using cicsupdate before the region is next
restarted.
Destination:
console.msg
ERZ045138I CICS has added the entry rccics to
the inittab
Explanation:
An entry has been added to the inittab to load the
kernal extensions for CICS 3270 Support and CICS IPC
on system restart.
ERZ045140E U4540: External Authentication

Manager could not be loaded
Explanation:
CICS did not load the External Authentication Manager
correctly or CICS was unable to find EAM Module in the
specified path.
System action:
User response:
Suitable actions include checking that: The Region
Definitions identify the location and name of the EAM
module correctly The identified directory and file exist
The directory and file permissions for the module file
are correct The EAM module has been compiled and
linked correctly
ERZ046001E Invalid command line option
optionName
Explanation:
You entered the specified option optionName. This
option is invalid.
System action:
error status. It also generates an information message
that gives the syntax of the command being run.
User response:
Destination:
stderr
ERZ046002E Unable to access region regionName
Explanation:
The region name regionName that you entered cannot
be accessed. Either the region name specified is invalid
or the region does not exist.
System action:
error status.
User response:
Check that the region name is correct. If it is, check that
the region directory has appropriate permissions. You
must have read, write, and execute permissions on the
region directory.
Destination:
stderr
System action:
ERZ046003E You must specify the class option -c

className
User response:
None
Explanation:
You did not specify the mandatory -c className option,
where className is the name of a resource class.
Destination:
stderr
346
System action:
ERZ046004E ERZ046010E
error status.
User response:
Retry the command, specifying -c className.
Destination:
stderr
ERZ046004E No such resource class
Explanation:
The class name you entered is not the name of a valid
resource class.
System action:
error status.
User response:
Retry the command with the name of a valid resource
class.
ERZ046007E Invalid password supplied for

CICSPassword attribute
Explanation:
An invalid password for the CICSPassword attribute
was supplied to cicsadd, cicsupdate, cicsupdateclass or
cicsmigrateclass. Passwords must not contain more
than 8 characters.
System action:
error status.
User response:
Retry the command supplying a valid password.
Destination:
stderr
ERZ046008E Cannot un-install entry entryName
Destination:
stderr
Explanation:
The cicsdelete command cannot uninstall the entry
entryName as it has not been installed or is marked as
in use.
ERZ046005E Entry entryName not found for

permanent database class className
System action:
The command, cicsdelete with the -R or -B option,
abnormally terminates with a non-zero error status.
Explanation:
The command cannot find the required entry in the
permanent database. You are probably providing an
incorrect key value or invalid region.
System action:
error status.
User response:
Check whether the resource exists. If not, retry the
command with correct parameters.
Destination:
stderr
ERZ046006E Entry entryName not found for
database class className
Explanation:
The command cannot find the required entry in the
database. You are probably providing an incorrect key
value or invalid region.
User response:
Check that you specified the entry name correctly. If
not, retry the command with the correct entry name.
Check for related messages in the region error log and
console.
Destination:
stderr
ERZ046009E You cannot add an entry to class
className
Explanation:
You are not allowed to use cicsadd to add entries of
class monitor and region.
System action:
error status.
User response:
Do not try this again.
System action:
error status.
Destination:
stderr
User response:
Check whether the resource exists. If not, retry the
command with correct parameters.
ERZ046010E You cannot delete entry of class

className
Destination:
stderr
Explanation:
You are not allowed to delete entries of class monitor
and region.
System action:
347
ERZ046011E ERZ046017E
error status.
User response:
ERZ046014E You cannot set up a startup image

entry for class className
Destination:
stderr
Explanation:
You are only allowed to use cicssetuprunimage to setup
run images for entries of class region, SFS and PPC
Gateway server.
ERZ046011E You must specify either the -a or -g

option
System action:
error status.
Explanation:
The -a or -g option is required for the command.
User response:
System action:
error status.
Destination:
stderr
User response:
Retry the command with the correct option.
ERZ046015E Addition, deletion or renaming of the

default entry is not permitted
Destination:
stderr
Explanation:
A default database entry has a key that is a string of
zero length. Such a key is usually expressed by two
adjacent quotation marks. For example the command
cicsget -r regionName -c fd retrieves the default entry
for the File Definitions. The default database entries are
created when the region database is created and
cannot subsequently be deleted or added.
ERZ046012E Invalid Resource Definition Online

(RDO) program name programName
Explanation:
The programName that you have entered is linked to
the RDO programs.
System action:
error status.
User response:
Enter correct program name. The program link was
presumably created on site. If this is not the case,
System action:
error status.
User response:
Destination:
stderr
Destination:
stderr
ERZ046016E The className record may not be

activated
ERZ046013E Unable to obtain the default entry for

permanent database class className
Explanation:
The region or monitor permanent database entry cannot
be installed using Resource Definition Online (RDO).
Explanation:
The command was unable to retrieve the default entry
for the class specified. Either the command was unable
to read the permanent stanza file (check for more
detailed messages output by the command), or the
default entry does not exist. The presence of a default
entry is mandatory for this class, and so permanent
database operations for this class cannot be performed.
System action:
error status.
User response:
Check the permanent database for inconsistency;
repair, or restore from a backup.
Destination:
stderr
348
System action:
error status.
User response:
Destination:
stderr
ERZ046017E The -f option is mandatory with a
class of scd
Explanation:
The -f option is required for the command when the
class is Structured File Server (SFS) Schema Files
(scd).
ERZ046018E ERZ046026E
System action:
error status.
User response:
Retry the command with the correct option.
Destination:
stderr
ERZ046018E The -optionName option is invalid
with a class of className
Explanation:
The named option must not be specified with this
particular class.
ERZ046021E Unsuccessful renaming of

oldEntryName to newEntryName, old
entry cannot be deleted
Explanation:
The renaming of a permanent database entry was
unsuccessful because the old entry was unable to be
removed.
System action:
The new entry is created and the old entry still exists.
error status.
System action:
error status.
User response:
Refer to previous messages detailing why the old entry
was unable to be deleted. Remove the appropriate old
or new entry using Resource Definition Online (RDO) as
applicable, retrying the operation if the new one is
removed.
User response:
Retry the command with the correct options.
Destination:
stderr
Destination:
stderr
ERZ046019E The -optionName option requires a
mandatory argument
Explanation:
The named option was specified without the required
option argument.
ERZ046025E ALL is not defaulted for DISCARD,

SET or PERFORM commands
Explanation:
You entered an incomplete CEMT DISCARD, CEMT
SET or CEMT PERFORM command.
System action:
CICS displays the appropriate CEMT panel.
System action:
error status.
User response:
Enter the correct CEMT DISCARD, CEMT SET or
CEMT PERFORM command.
User response:
Retry the command with the correct option argument.
Destination:
Message Panel or Response Area of CEMT Panel.
Destination:
stderr
ERZ046020E Could not access SFS Schema file
pathName; error errorNumber
Explanation:
A cicsadd command for the class scd (Structured File
Server schemas) was issued with a schema file path
that was unable to be accessed. The operating system
error is given.
ERZ046026E Commands other than INQUIRE are

not executed if they contain errors
Explanation:
There is an error in the CEMT command that you
entered. The error is described by accompanying
messages. The command is not executed.
System action:
CICS does not execute the CEMT DISCARD, SET or
PERFORM command.
System action:
error status.
User response:
Enter the correct CEMT DISCARD, CEMT SET or
CEMT PERFORM command.
User response:
Look up the errorNumber given in operating system
documentation to find out why the schema file was
unable to be accessed. When the problem is resolved,
retry the command.
Destination:
Destination:
stderr
349
ERZ046027E ERZ046037I
ERZ046027E fieldName value, value, is invalid
and has been ignored
Explanation:
You have entered an invalid value value.
System action:
User response:
Correct your invalid changes.
Destination:
ERZ046028I THERE ARE NO MESSAGES
Destination:
stderr
ERZ046032E Unable to access the CICS internal
inventory list
Explanation:
The CICS internal inventory list does not exist.
System action:
error status.
User response:
Check that the CICS installation was successful. If the
Explanation:
Placed in the Information Area of a CEMT panel when
there are no messages.
Destination:
stderr
System action:
ERZ046033E The CICS internal inventory list has

inconsistent data
User response:
None
Explanation:
The contents of CICS internal inventory are invalid and
cannot be used check region archives.
Destination:
directoryName
Explanation:
The operating system command mkdir was
unsuccessful.
System action:
error status.
User response:
Check whether the directory already exists and that
there is enough space in the filesystem. Consult the
operating system documentation.
System action:
error status.
User response:
Destination:
stderr
ERZ046036E The -optionName option must be
specified with this command
Explanation:
The -optionName option is mandatory for this
command.
Destination:
stderr
System action:
error status.
ERZ046031E Unable to create symbolic link

linkName for fileName
User response:
Retry the command, supplying the option.
Explanation:
The system command ln was unsuccessful trying to link
linkName to fileName. The error occurred during
cicsexport.
Destination:
stderr
System action:
error status.
User response:
Check the file permissions, and that there is enough
space in the file system. Consult the operating system
documentation.
350
ERZ046037I Specified region regionName already

exists
Explanation:
The region regionName exists in varDir/cics_regions.
This message is only for information. An existing region
cannot be overwritten without also supplying the force
flag (-F). On Windows NT you can find the drive letter of
the disk containing the cics_regions directory by using
the cicsname regions command.
ERZ046038E ERZ046045I
System action:
None
User response:
None
Destination:
stderr
ERZ046038E Unable to read the CICS internal
inventory list
Explanation:
The CICS internal inventory list is not readable by the
current user.
System action:
error status.
User response:
Check that the CICS installation was successful. If
Destination:
stderr
ERZ046039W Linked file fileName does not exist
Explanation:
A symbolic link fileName cannot be resolved. This does
not prevent a region from being created.
System action:
User response:
The link can be resolved manually if required.
Destination:
stderr
ERZ046040I Restoring fileName from back-up
Explanation:
The file fileName, which is a symbolic link, is being
replaced by a copy of the original file. This message is
for information only.
System action:
User response:
None
Destination:
stderr
ERZ046041W linkName does not exist - restoring
fileName from back-up
Explanation:
The symbolic link linkName cannot be resolved, so it is
being replaced by a copy of the original file.
System action:
User response:
None
Destination:
stderr
ERZ046042W fileName does not exist - link
linkName cannot be resolved
Explanation:
The link cannot be resolved.
System action:
User response:
None
Destination:
stderr
ERZ046043E fileName does not exist - link
linkName cannot be resolved
Explanation:
The link cannot be resolved, and the region is not
created.
System action:
error status.
User response:
Resolve links, or run the program in another mode.
Destination:
stderr
ERZ046044I linkName is a symbolic link to
fileName
Explanation:
This message is produced by cicsimport and cicsdefault
in verbose mode (-v) to indicate that linkName is a
symbolic link to file fileName.
System action:
User response:
None
Destination:
stderr
ERZ046045I Creating region regionName from
archive of default region
defaultRegionName
Explanation:
This message is produced by cicsdefault to indicate that
the region regionName is being created from an
archive of the default region defaultRegionName.
351
ERZ046046E ERZ046053E
System action:
existing region and other related information, so you can

possibly lose data that you wish to keep.
User response:
None
Destination:
stderr
Destination:
stderr
ERZ046050E Cannot find region to export
ERZ046046E Could not locate archive of default

region
Explanation:
No region name is specified and cannot find default
region.
Explanation:
cicsdefault or cicsmigrate cannot find the archive of the
default region.
System action:
error status.
System action:
error status.
User response:
Specify region name, or restore default region.
User response:
Check that the CICS installation was successful.
Restore from backup if possible.
Destination:
stderr
ERZ046047E Region regionName is locked command not allowed
Explanation:
cicsdefault or cicsimport was requested to overwrite an
existing region, and the existing region is locked for
execution. cicsdefault and cicsimport do not allow
overwriting of a locked region.
System action:
error status.
User response:
Check that the specified region is running. If the region
is running and you still want to run cicsdefault or
cicsimport then shut the region down and retry this
command. If the region is not running then use the
cicsrlck command to remove the lock file and retry this
command.
Destination:
stderr
ERZ046051E fileName does not exist in the
archive
Explanation:
The required file fileName cannot be found in the
region archive.
System action:
error status.
User response:
Destination:
stderr
ERZ046052E Absolute paths not permitted in the
region archive file
Explanation:
The region archive file contains absolute (rather than
relative) pathnames.
Destination:
stderr
System action:
error status.
ERZ046049E Region regionName already exists
User response:
Recreate an appropriate archive.
Explanation:
cicsdefault or cicsimport was requested to create a
region that already exists.
Destination:
stderr
System action:
error status.
ERZ046053E Option -optionName has invalid

argument argumentValue
User response:
Create a different region, or if you want to overwrite the
existing region then retry the command with the -F flag.
The use of the -F flag destroys region definitions for the
352
Explanation:
You are specifying an invalid argument,
argumentValue, for the command option -optionName.
System action:
ERZ046054E ERZ046061E
error status.
User response:
Retry the command specifying valid argument.
Destination:
stderr
ERZ046054E Group groupName is invalid
Explanation:
You are specifying a group that is not valid for your
userid.
System action:
error status.
User response:
Specify a valid group, or alter userid permissions.
Destination:
stderr
ERZ046055E All links in the archive could not be
resolved - program abnormally
terminating
Explanation:
One or more links cannot be resolved. The region is not
created.
System action:
error status.
User response:
Run the program again in a different mode, or restore
files so as to resolve links.
Destination:
stderr
ERZ046056E Command line option -optionName
re-specified
ERZ046057W Class className specified more

than once
Explanation:
The class className is specified more than once on
the command line.
System action:
User response:
None
Destination:
stderr
ERZ046059E Command line option optionName
expects a value
Explanation:
It is incorrect to specify the command line option
optionName without also providing a value.
System action:
User response:
Destination:
stderr
ERZ046060E Command line option optionName is
invalid
Explanation:
The option optionName is not a valid option.
System action:
User response:
Explanation:
You are specifying option -optionName more than
once.
Destination:
stderr
System action:
error status.
ERZ046061E Archive file fileName does not exist

or is not readable
User response:
Retry the command correctly.
Explanation:
The archive file fileName does not exist, or it cannot be
read.
Destination:
stderr
System action:
error status.
User response:
Retry the command specifying a valid archive file, or
make specified file available.
353
ERZ046062E ERZ046081E
Destination:
stderr
ERZ046062E Renaming of resources in the
run-time is not permitted
Explanation:
An attempt was made to rename a resource in the
run-time. This is valid only within the permanent
database environment via Resource Definition Online
(RDO) interface.
System action:
error status.
User response:
If renaming of the resource is required, then you can
only accomplish this within the permanent database
environment.
ERZ046069I Subsystem definition for region

regionName already exists
Explanation:
The subsystem definition for region regionName
already exists, and no attempt is made to create it. This
message is for information only.
System action:
User response:
None
Destination:
stderr
ERZ046073E Unable to update the keytab file with
the region regionName password
Destination:
stderr
Explanation:
The keytab file cannot be updated with the region
regionName password.
ERZ046063E You have insufficient privilege to run

the programName program
System action:
error status.
Explanation:
You are not running the named Resource Definition
Online (RDO) program as a user with sufficient
privileges.
User response:
Further error messages identify the problem. Ensure
that the name server is running, and that you have write
permission to the file.
System action:
error status.
Destination:
stderr
User response:
Login as a user with suitable privileges before executing
this command.
ERZ046080E Force flag must be specified
Destination:
stderr
ERZ046065E File fileName cannot be updated
Explanation:
This command updates the keytab file, fileName, in
order to add the automatically generated region server
password. The file cannot be updated.
System action:
error status.
User response:
Ensure file exists and is writable, and retry the
command. If the problem persists contact your support
organization.
Destination:
stderr
Explanation:
An existing region cannot be overwritten unless the -F
option is specified.
System action:
error status.
User response:
Enter again with the -F option, or specify a different
region.
Destination:
stderr
Explanation:
System action:
error status.
User response:
354
ERZ046083E ERZ046092I
Destination:
stderr
Destination:
stderr
ERZ046083E Unable to delete entity from the

registry, return code is returnCode
ERZ046090I Usage: cicsdefault -r regionName {-?|

[-g groupName] [-v] [-F]}
Explanation:
cicsdestroy was unable to delete an entity from the CDS
registry whilst attempting to destroy a region. The entity
that was unable to be deleted is either the region
principal, the region account or the region password
entry in the keytab file.
Explanation:
This is the usage message for the cicsdefault
command.
System action:
The command terminates, returning the value 1.
User response:
cicsdestroy trace file for further information. Ensure that
the CDS server is running, and that you have sufficient
authority to delete the entity. Perform the deletion by
hand.
Destination:
stderr
ERZ046087W Unable to access region definitions
(RD)
Explanation:
cicsdestroy was unable to access the region definitions
(RD). The cicsdestroy command uses the region
definitions (RD) to determine the SFS and LOG data to
be destroyed, so this file must be available in order to
destroy the region-owned SFS and LOG data.
System action:
The command continues, but the deletion of any
region-owned SFS and LOG data is not performed.
User response:
Check if any region-owned SFS and LOG data exists. If
data does exist, perform the deletion by hand.
Destination:
stderr
ERZ046089E Unable to delete file fileName on SFS
server serverName, return code is
returnCode
Explanation:
cicsdestroy was unable to delete the named SFS file on
the named SFS while attempting to destroy a region.
System action:
User response:
the SFS is running, that the file exists, and that you
have sufficient authority to delete the file. Perform the
deletion by hand.
System action:
The command exits.
User response:
If the command was specified incorrectly then retry with
valid parameters. You must be logged in as root on
UNIX or as a user with Administrator and cicsgroup
authority on Windows NT. See the TXSeries for
information.
Destination:
stderr
ERZ046091I Usage: cicsadd {-?|-c className [-r
regionName] [-P|-B] [-f fileName] [-m
modelId] resourceName
[[attributeName=attributeValue]...]}
Explanation:
This is the usage message for the cicsadd command.
System action:
The command exits.
User response:
valid parameters. See the TXSeries for Multiplatforms
Destination:
stderr
ERZ046092I Usage: cicsdelete {-?|-c className [-r
regionName] [-P|-R|-B] [-f fileName]
resourceName [resourceName...]}
Explanation:
This is the usage message for the cicsdelete command.
System action:
The command exits.
User response:
Destination:
stderr
355
ERZ046093I ERZ046099I
ERZ046093I Usage: cicsget {-?|-c className [-r
regionName] [-f fileName] {-l|-s
[resourceName]|[resourceName]}}
Explanation:
This is the usage message for the cicsget command.
System action:
The command exits.
User response:
Destination:
stderr
ERZ046094I Usage: cicsinstall {-?|[-v] [-r
regionName] {-a | -g groupName
[groupName...] }}
Explanation:
This is the usage message for the cicsinstall command.
System action:
The command exits.
User response:
Retry the command, if appropriate. See the TXSeries
information.
Destination:
stderr
User response:
Destination:
stderr
ERZ046097I Permanent database request for
resourceName succeeded, though
run-time request was unsuccessful
Explanation:
This message indicates that only your permanent
database operation succeeded. You requested that the
operation be performed on both the permanent and the
run-time database, but the run-time database operation
was unsuccessful.
System action:
None
User response:
Other messages indicate why the run-time request was
unsuccessful. Retry the command when appropriate.
Destination:
stderr
ERZ046098I Usage: cicsexport {-?| [-r regionName]
[-o outFile] [-t temporaryWorkspace] [-l
className...]}
Explanation:
This is the usage message for the cicsexport command.
ERZ046095I Usage: cicsdestroy {-?| -r regionName

[-I] [-s [-u userId[/passWd]]]}
System action:
Command terminates.
Explanation:
This is the usage message for the cicsdestroy
command.
User response:
valid parameters. It is possible that you have specified
an option of zero length. See the TXSeries for
information.
System action:
The command exits.
User response:
Destination:
stderr
ERZ046096I Usage: cicsupdate {-?|-c className [-r
regionName] [-P|-R|-B] [-f fileName]
[resourceName]
[[attributeName=attributeValue]...]}
Explanation:
This is the usage message for the cicsupdate
command.
System action:
The command exits.
356
Destination:
stderr
ERZ046099I Usage: cicsimport {-?| -r regionName
[-g groupName] [-i inFile] [-l m|o] [-v]
[-F] [-o] [-B]}
Explanation:
This is the usage message for the cicsimport command.
System action:
The command exits with a non zero return code.
User response:
If command is specified incorrectly then retry with valid
parameters. Check that you have not given zero length
strings as input. You must be logged in as root on UNIX
or as a user with Administrator and cicsgroup authority
ERZ046101I ERZ046110E
on Windows NT. See the TXSeries for Multiplatforms
Destination:
stderr
ERZ046101I Usage: cicssetuprunimage -c
className [-r regionName] [-a] [-e] [-s]
resourceName
[[attributeName=attributeValue]...]
Explanation:
This is the usage message for the cicssetuprunimage
command.
System action:
Program exits.
User response:
valid parameters.
Destination:
stderr
ERZ046104E Cannot find TRPC path name for
region regionName
Explanation:
The command being run was unable to obtain the
TRPC path of the region.
System action:
error status.
User response:
Run the command again specifying the correct region
name using the -r option. Alternatively, ensure that the
default region is set to the correct region, if the region
can be defaulted, and run the command again. Also,
ensure that the region directory is accessible.
Destination:
stderr
ERZ046105E Cannot find region directory for
region regionName
Explanation:
The command being run was unable to obtain the path
of the region directory.
System action:
error status.
User response:
name using the -r option. Alternatively, ensure that the
default region is set to the correct region, if the region
can be defaulted, and run the command again. If the
command being run is not cicsimport, ensure also that
the region directory is accessible.
Destination:
stderr
ERZ046106E Do not have permission to destroy
region regionName
Explanation:
cicsdestroy cannot access the region directory.
System action:
error status.
User response:
Ensure that you have access to the region being
destroyed and then repeat the command.
Destination:
stderr
ERZ046107I Operation failed with message
errorMessage
Explanation:
An operation failed with the message errorMessage.
Following messages give further details of the problem.
System action:
See following messages.
User response:
See following messages.
Destination:
stderr
ERZ046108W Cannot find SFS file fileName
Explanation:
While trying to delete SFS files, the cicsdestroy
command was unable to find the named file. This is
usually because the regions SFS files were not created
on the SFS, or because the SFS files were already
deleted from the server.
System action:
cicsdestroy continues trying to delete the other SFS
files.
User response:
None
Destination:
stderr
ERZ046110E Unsuccessful attempt to add entry
resourceName to permanent database
class className
Explanation:
Your attempt to add the entry resourceName to the
permanent database class className was
unsuccessful.
System action:
357
ERZ046111E ERZ046117I
The command terminates with a non-zero error status.
User response:
As indicated by the previous message(s) detailing why
the add request was unsuccessful.
Destination:
stderr
ERZ046111E Unsuccessful attempt to update entry
resourceName in permanent database
class className
Explanation:
Your attempt to update the entry resourceName in the
unsuccessful.
System action:
User response:
the update request was unsuccessful.
Destination:
stderr
ERZ046112E Unsuccessful attempt to delete entry
resourceName from permanent
database class className
Explanation:
Your attempt to delete the entry resourceName in the
unsuccessful.
System action:
User response:
the delete request was unsuccessful.
Destination:
stderr
ERZ046113E Your attempt to add resourceName is
incomplete
Explanation:
Your attempt to add resourceName is incomplete
because of an unsuccessful attempt to add it to the
CICS permanent or runtime database. The addition of
resourceName involves further operations as well as
adding it to the CICS database. These subsequent
operations were not performed.
System action:
User response:
You possibly partially added resourceName to CICS.
Either correct the error indicated by previous
358
message(s) and retry the operation specifying the -I flag

to ignore errors or delete resourceName and start
again.
Destination:
stderr
ERZ046114I Run-time database request for
resourceName succeeded, though
permanent request was unsuccessful
Explanation:
This message indicates that only your run-time
database operation succeeded. You requested that the
operation be performed on both the permanent and the
run-time database, but the permanent database
operation was unsuccessful.
System action:
None
User response:
Other messages indicate why the permanent request
was unsuccessful. Retry the command when
appropriate.
Destination:
stderr
ERZ046115E Region regionName is still running
Explanation:
cicsdestroy was unable to destroy the region
regionName because it was unable to obtain the region
lock. This means that either the region was running,
another process was performing region configuration, or
the region lock file was not removed when the region
terminated.
System action:
cicsdestroy exits
User response:
Repeat the command after a few minutes and check
that no other process is performing region configuration.
Examine the value in the region_lock file in the region
directory. If the region is still running the file contains
the processid of the main cics process. If the region is
still running, shut it down before attempting to remove it.
If there is no process running, remove the lock file using
the cicsrlck command and retry the cicsdestroy
command.
Destination:
stderr
ERZ046117I Deleting Structured File Server (SFS)
data for the region regionName
Explanation:
This message is produced by cicsdestroy to indicate
that the Structured File Server (SFS) data for the region
regionName is being deleted from the SFSs used by
the region regionName.
ERZ046119I ERZ046124E
System action:
User response:
None
Destination:
stderr
ERZ046119I Deleting subsystem definition for the
region regionName
Explanation:
that the subsystem definition for the region
regionName is being deleted.
System action:
User response:
None
Destination:
stderr
ERZ046120I Deleting files and directories for the
region regionName
Explanation:
This informational message is produced by cicsdestroy
to indicate that the directory varDir/cics_regions/
regionName is being deleted. On Windows NT you can
find the drive letter of the disk containing the
command.
System action:
User response:
None
Destination:
stderr
ERZ046121E Unable to remove the directory
structure for region regionName
Explanation:
This error message is produced by cicsdestroy and is
issued when the command to delete the region file
structure under varDir/cics_regions failed. The
command possibly partly completed, and it is possibly
necessary to remove any remaining files by hand.
System action:
The cicsdestroy command exits abnormally.
User response:
Remove any remaining files under varDir/
cics_regions/regionName. On Windows NT you can
find the drive letter of the disk containing the
command.
Destination:
stderr
ERZ046122E Unable to remove the region entry
from CDSprofile, return code is
returnCode
Explanation:
cicsdestroy was unable to remove the entry for the
region from the specified CDS profile.
System action:
The command continues, but the region entry possibly
remains in the specified CDS profile.
User response:
Check the cicsdestroy trace file for further information.
Ensure that the CDS name server is running, and that
you have sufficient authority to access the profile.
Perform the deletion by hand.
Destination:
stderr
ERZ046123E Region name regionName is reserved
by CICS
Explanation:
The region name regionName that you entered is
reserved by CICS.
System action:
error status.
User response:
Choose another name for your region.
Destination:
stderr
ERZ046124E regionName rejected - CICS region
name may not contain a .
Explanation:
The region name regionName that you entered
contained a period (.). This syntax is illegal for CICS
region names.
System action:
error status.
User response:
Choose another name for your region that does not
contain a ..
Destination:
stderr
359
ERZ046125W ERZ046130E
ERZ046125W No resources installed for group(s)
specified
Explanation:
You attempted to install a resource group or groups into
the CICS runtime database but no resources were
installed. Either no resources were found in the
permanent database for the groups specified or the
resources found were unable to be installed. Failure to
install a resource can possibly be caused by the
resource already existing in the runtime database or by
incorrect data in the resource definition.
System action:
The command terminates normally.
User response:
Check for other messages from the cicsinstall
command. If no other messages were issued this
indicates that no resources were found for the groups
specified. If you were expecting resources to be found
check the spelling of the group names specified on the
command with those specified in the permanent
database. If other messages were issued check their
explanations and look for further information on the
CICS console.
Destination:
stderr
ERZ046126W No resources installed which specify
ActivateOnStartup=yes
Explanation:
You attempted to install all resources that have the
ActivateOnStartup flag set into the Runtime database
but no resources were installed. Either no resources
were found in the permanent database with this flag set
or none of the resources found were able to be
installed. Failure to install a resource can possibly be
caused by the resource already existing in the runtime
database or by incorrect data in the resource definition.
System action:
The command terminates normally.
User response:
Check for other messages from the cicsinstall
command. If no other messages were issued this
indicates that no resources were found with the
ActivateOnStartup flag set. If other messages were
issued check their explanations and look for further
information on the CICS console.
Destination:
stderr
ERZ046127E File operation failed while reading
stanza file
Explanation:
While attempting to read a stanza file an undefined I/O
error occurred.
360
System action:
The command terminates abnormally. Any changes
made to the stanza file are backed out during the next
database operation on the stanza file.
User response:
Check that the filesystem on which the stanza file
resides is not full and retry the command. If the problem
persists check for warning messages in the system
error log and console.
Destination:
stderr
ERZ046128E File operation failed while writing to
stanza file
Explanation:
While attempting to write to a stanza file an undefined
I/O error occurred.
System action:
User response:
Destination:
stderr
ERZ046129E Memory get request for byteCount
bytes failed
Explanation:
The current program executed a request to the
operating system to get byteCount bytes of memory.
The request failed with not enough memory.
System action:
The command terminates abnormally. If changes were
being made to a stanza file, they are backed out during
the next database operation on the stanza file.
User response:
If the system was heavily loaded, wait until the load
decreases and rerun the command. If the problem
persists check for error messages in the system error
log and console.
Destination:
stderr
ERZ046130E File operation failed while closing
stanza file
Explanation:
While attempting to close the stanza file an undefined
I/O error occurred.
System action:
ERZ046131E ERZ046137E
User response:
ERZ046134E Unrecognized class className

specified
Explanation:
The class you specified for the -c option is not a valid
database class.
System action:
Destination:
stderr
User response:
Check the syntax of the command and retry the
command specifying a valid CICS database class.
ERZ046131E Illegal condition detected in CICS

internal function
Destination:
stderr
Explanation:
While running a CICS RDO Command an internal error
occurred.
ERZ046135E Stanza file for class className does

not contain attribute attributeName
System action:
User response:
Retry the command. If the problem persists check for
warning messages in the system error log and console.
Destination:
stderr
ERZ046132E -r option is not valid when updating
classes SSD, GSD or SCD
Explanation:
You have specified the -r option along with a server
database class. The region name is not a valid option
while updating the SSD, GSD or SCD schemas.
System action:
User response:
Retry the command with the correct syntax.
Destination:
stderr
ERZ046133E -r option must be specified for class
className
Explanation:
You have not specified a region name.
System action:
User response:
Retry the command specifying a region name.
Destination:
stderr
Explanation:
The attribute you specified, using the -b option, does
not exist in the stanza file for class className.
System action:
Processing of the cicsupdateclass command terminates
abnormally.
User response:
Check you have specified the attribute on the -b option
correctly, and retry the command.
Destination:
stderr
ERZ046136E Unable to convert option option to
numerical form
Explanation:
While using the -lt, or -gt flags on the cicsupdateclass
command you have specified an option that cannot be
converted to a long integer.
System action:
abnormally.
User response:
Check the number that you have specified for the
relevant flag and retry the command specifying a valid
integer.
Destination:
stderr
ERZ046137E Bad value attributeValue for attribute
attributeName, in class className, for
stanza with key resourceName
Explanation:
On the cicsupdateclass command you have specified to
update the value of attribute attributeName, if the value
is less than (-lt) or greater than (-gt) a specified value.
While attempting to convert the value in the stanza file
to a long integer an error occurred.
361
ERZ046138I ERZ046144I
System action:
abnormally.
If command was specified incorrectly then retry with

User response:
Check the value of the attribute specified by
className, attributeName, resourceName and verify
that it is a numerical value.
Destination:
stderr
Destination:
stderr
ERZ046138I Usage: cicsupdateclass {-?|[-r
regionName] [-w] -c className -a
attributeName [-n newValue | -b
fromAttribute] [[-lt | -gt | -eq ] oldValue]
[-k resourceName] [-f fileName]}
Explanation:
This is the usage message for the cicsupdateclass
command.
System action:
Program terminates.
User response:
Destination:
stderr
ERZ046139I Usage: cicsmigrateclass {-?|[-r
regionName] [-w] -c className [-a
attributeName {-n newAttribute | -d | -u
renameAttribute}] [-f fileName]}
Explanation:
This is the usage message for the cicsmigrateclass
command.
System action:
Program terminates.
User response:
Destination:
stderr
ERZ046140I Usage: cicscopystanza {-?|[[-w] -s
sourceRegion] -t targetRegion -c
className -k resourceName}
Explanation:
This is the usage message for the cicscopystanza
command.
System action:
Program terminates.
User response:
362
ERZ046141I Usage: cicsmigrate {-?|[ -r regionName

| -s | -c | -p | -m ] -g fileName -o
logFileName}
Explanation:
This is the usage message for the cicsmigrate script.
System action:
Program terminates.
User response:
Destination:
stderr
ERZ046142I No database migration to be done for
class className
Explanation:
No updates are needed for the class className to
migrate to the present release.
System action:
Program terminates.
User response:
none
Destination:
stderr
ERZ046143I Script output file and log file cannot be
the same file
Explanation:
On specifying the cicsmigrate command you have
specified the same name for both the log file and the
script file.
System action:
Program terminates.
User response:
Retry the command specifying distinct names for the log
file and the script file.
Destination:
stderr
ERZ046144I Unable to write to file logFileName
Explanation:
The script was unable to write to the log file you
specified.
System action:
ERZ046145I ERZ046153I
Program terminates.
User response:
Check the permissions on the log file you specified and
on the parent directory. Retry the command with a valid
log file.
Destination:
stderr
ERZ046145I Unable to write to file scriptFileName
Explanation:
cicsmigrate was unable to write to the script file you
specified.
System action:
Program terminates.
User response:
Check the permissions on the script file you specified
and on the parent directory. Retry the command with a
valid script name.
Destination:
stderr
ERZ046148I No regions to select
Explanation:
No regions were found in the CICS region directory.
System action:
The select command returns failure.
User response:
If there are regions defined, check the directory exists
and its access permissions. If the directory is a mounted
filesystem, ensure that it is mounted correctly.
Destination:
stderr
ERZ046149E Unable to create the archive file
fileName
Explanation:
The cicsexport command attempted to create the
archive file fileName but was unable to create or write
to the file.
System action:
The command terminates with a return code of 1.
User response:
Check that the filename specified points to a valid file.
Check that the filesystem on which the file resides is not
full and, if the file already exists, check that it is not a
special file such as a directory or a device. If the
filesystem is remotely mounted from another machine,
check that the exported filesystem honors super-user
access from the current machine.
Destination:
stderr
ERZ046150I No resources were found for the class

className in region regionName
Explanation:
You attempted to generate a list of all resources defined
in a region for a particular class. No resources were
found.
System action:
User response:
Verify the select specified the correct region and if in
error retry the command specifying the correct region.
Destination:
stderr
ERZ046151I Usage: cicslist { -? | [-r regionName] -c
className [-f fileName] [-d]}
Explanation:
This is the usage message for the cicslist script.
System action:
Program terminates.
User response:
If command was specified incorrectly, retry the
command with valid parameters.
Destination:
stderr
ERZ046152I No servers defined for class class
Explanation:
You attempted to generate a list of all servers defined
for a class but none were found.
System action:
User response:
Check by viewing the server stanza file that server
definitions exist, and check the permissions on the
stanza file.
Destination:
stderr
ERZ046153I No schemas defined in the file
fileName
Explanation:
You attempted to generate a list of all the schemas
defined in a file but none were found.
System action:
User response:
Check by viewing the schema file that definitions exist,
and check the permissions on the schema file.
Destination:
363
ERZ046156E ERZ046164E
stderr
ERZ046156E Cannot execute programName
User response:
None
Explanation:
The script was unable to execute programName.
Destination:
stderr
System action:
User response:
Check that the program is in a directory that is specified
in your PATH environment variable, and that you have
permission to execute it.
Destination:
stderr
ERZ046157E Cannot destroy server serverName server running
Explanation:
The server details cannot be destroyed because the
lock file for the server exists - this implies the server is
running.
System action:
value 1.
User response:
The server cannot be destroyed if it is running, so
perform a shutdown first. It is possible that due to a
previous system fault the server is not running but the
lock file was left. If this is the case, remove the lock file
by using cicsloglock.
Destination:
stderr
ERZ046158W Subsystem definition
subsystemName could not be found
Explanation:
The subsystem definition subsystemName cannot be
found, though the command run assumes that it exists.
System action:
User response:
The definition was supposed to exist, though this does
not prevent processing from continuing.
Destination:
stderr
ERZ046159I The subsystem definition for server
serverName has been removed
Explanation:
The subsystem definition for server serverName was
removed.
System action:
364
ERZ046161W The restart file restartFileName could

not be found
Explanation:
The restart file restartFileName, which contains the
restart string for the server, cannot be found during a
destroy operation.
System action:
User response:
None. The file was supposed to exist, but does not
prevent processing from continuing.
Destination:
stderr
ERZ046163E Could not create list of regions to
migrate
Explanation:
The command cicslist was used to generate a list of
CICS regions to be migrated on the machine; this
command was unsuccessful. It possibly indicates that
there are no regions defined on the machine.
System action:
The command possibly continues to migrate other
resources.
User response:
If there are no regions to be migrated for the machine,
no action is required. If there are regions that require
migration, examine the migration logfile for further
information on failure of the cicslist command, and
retain the logfile for use by your support organization.
Destination:
stderr
ERZ046164E Migration of region regionName was
unsuccessful
Explanation:
The CICS region regionName was not successfully
migrated.
System action:
resources.
User response:
Examine the output for related error messages to
determine the cause of failure.
Destination:
stderr
ERZ046168E ERZ046183E
ERZ046168E Could not create list of SFS servers
to migrate
Explanation:
The command cicsget was issued to generate a list of
SFS servers to be migrated for the machine; this
command was unsuccessful. It possibly indicates that
there are no SFS servers defined on the machine, or
that they were already migrated.
System action:
resources.
User response:
If there are no SFS servers to be migrated for the
machine, no action is required. If there are SFS servers
that require migration, examine the migration logfile for
further information on failure of the cicsget command,
and retain the logfile for use by your support
organization.
ERZ046174W Old CDS directories not deleted

Explanation:
The command was unable to delete the old CDS
directories after creating new ones for migration.
System action:
User response:
Examine the migration log file for related CDS
messages. The absence of these directories does not
cause a problem to the migrated system, but this
warning can possibly indicate an error with CDS.
Destination:
stderr
ERZ046181W commandName has successfully
deleted the CDS entities
Destination:
stderr
Explanation:
This information message is displayed when the
deletion of the Cell Directory Services (CDS) directories
and objects successfully completes.
ERZ046169E Migration of SFS server serverName

was unsuccessful
System action:
Explanation:
The command was unable to migrate the SFS
serverName.
User response:
None
System action:
resources.
User response:
Examine the output for related error messages to
determine the cause of failure.
Destination:
stderr
ERZ046171E No subsystem definition for region
regionName on this machine
Explanation:
The region regionName that is being migrated does not
have a valid subsystem definition. This means that the
region is not complete on this machine and needs to be
deleted and properly defined after migration of the
machine is complete. This possibly indicates that a
previous attempt to delete the region was incomplete.
System action:
User response:
Check that the region name is valid. If the region is
required, delete it and redefine it when migration of the
machine is complete.
Destination:
stderr
Destination:
stderr
ERZ046182I Usage: cicsmigratelevel {-?| [-r
regionName] -c className}
Explanation:
This is the usage message for the cicsmigratelevel
command.
System action:
Command exits.
User response:
valid parameters.
Destination:
stderr
ERZ046183E Cannot create lock file for server
serverName
Explanation:
The lock file used for locking the server cannot be
created.
System action:
User response:
Check that directories varDir/cics_servers/SSD and
varDir/cics_servers/GSD are available and that you
have permission to create files in them. On Windows
365
ERZ046184E ERZ046189E
NT you can find the drive letter of the disk containing
the cics_servers directory by using the cicsname
serversdir command. See accompanying operating
system error messages for further information. Correct
the problem and retry the command.
Destination:
stderr
ERZ046184E Cannot perform migration - server
serverName running
Explanation:
The migration cannot be performed because the lock
file for the server exists - this implies the server is
running.
System action:
value 1.
Ensure that user or group userId exists and then rerun

the command. If it does not exist then ensure CICS is
installed correctly.
Destination:
stderr
ERZ046187E Unsuccessful attempt at changing
owner of files in server directory
directoryName for server serverName
Explanation:
An attempt at changing the ownership of a file in the
server directory directoryName was unsuccessful.
System action:
User response:
Migration cannot take place if the server is running, so
perform a shutdown first. It is possible that due to a
previous system fault the server is not running but the
lock file still exists. If this is the case, remove the lock
file by using cicsloglock.
User response:
Check that the directories varDir/cics_servers/SSD and
varDir/cics_servers/GSD are available and that you
have permission to create files in them. See
accompanying operating system error messages for
further information. On Windows NT you can find the
drive letter of the disk containing the cics_servers
directory by using the cicsname serversdir command.
Destination:
stderr
Destination:
stderr
ERZ046185E Cannot read entry from server

database for server serverName
ERZ046188E Cannot perform migration
Explanation:
The server details for entry serverName cannot be
retrieved from the server database. Accompanying
ERZ034xxx and ERZ082xxx messages identify the
problem.
System action:
value 1.
User response:
Use messages to determine the cause of the problem.
Correct the problem, and retry the command.
Destination:
stderr
ERZ046186E Unable to access details on user or
group userId
Explanation:
CICS was unable to access details on user or group
userId. This was probably because the user or group
does not exist. Previous messages identify the exact
problem.
System action:
User response:
366
Explanation:
The migration was unable to be carried out.
Accompanying messages identify the problem.
System action:
value 1.
User response:
command.
Destination:
stderr
ERZ046189E Cannot create subsystem definition
subsystemName for server
serverName
Explanation:
It was not possible to create a subsystem definition
subsystemName during migration.
System action:
value 1.
User response:
command.
ERZ046190W ERZ046196E
Destination:
stderr
ERZ046193E Migration of database for server

ERZ046190W Unable to delete CDS entity

CDSname, return code is returnCode
Explanation:
Explanation:
cicsdestroy was unable to delete the named CDS object
or directory.
System action:
The command terminates, returning the value 1.
System action:
The command continues, but the CDS object or
directory is not deleted.
User response:
command.
User response:
the CDS name server is running, and that you have
sufficient authority to delete the entity. Perform the
deletion by hand.
Destination:
stderr
ERZ046191W Unable to delete entity from the
registry, return code is returnCode
Explanation:
cicsdestroy was unable to delete an entity from the CDS
registry whilst attempting to destroy a region. The entity
that was unable to be deleted is either the region
principal, the region account or the region password
entry in the keytab file.
System action:
User response:
the CDS server is running, and that you have sufficient
authority to delete the entity. Perform the deletion by
hand.
Destination:
stderr
Destination:
stderr
ERZ046194E The -f option must be specified for
class SCD
Explanation:
cicsupdateclass, cicsmigrateclass or cicsgetattribute
was unable to read or update the SCD stanza as
instructed, because you did not specify the filename of
the SCD stanza using the -f option.
System action:
User response:
Retry the command specifying the filename of the SCD
stanza.
Destination:
stderr
ERZ046195E The -f option is not valid for class
className
Explanation:
You have specified the -f option along with a resource
class other than SCD. The -f filename option is not a
valid option with this class.
System action:
ERZ046192W Cannot perform migration
User response:
Explanation:
Destination:
stderr
System action:
ERZ046196E Region regionName already exists
User response:
command.
Destination:
stderr
Explanation:
The cics migration script attempted to create a region
that already exists. This region name is reserved for use
by CICS migration.
System action:
User response:
367
ERZ046198E ERZ046205E
If this region was created during a previous run of the
CICS migration script, destroy this region directory by
using the rm -rf command. Otherwise, if this region
name contains special characters that are not allowed in
the CICS permanent region database, either use
cicsdestroy to destroy the region, or cicsexport or
cicsimport to rename your region. If this fails, then you
must remove this region using rm -rf, with the
appropriate permissions, in order to proceed with cics
migration, and retry running your cics migration script.
Destination:
stderr
ERZ046198E Unable to access stanza file
stanzaFile
Explanation:
cicsmigrate with the -c option, attempted to migrate the
default SFS schema, which was not found.
System action:
the cicsmigrate command abnormally terminates.
User response:
As you do not have a default SCD schema file in the
default SCD server directory to migrate, do not run
cicsmigrate with the -c option. If you have other SCD
schema files that you wish to migrate, run the
cicsmigrateclass command, using the -c scd and -f
options.
Destination:
stderr
ERZ046201E Insufficient space to complete the
copy. The file system is more than 94
percent full.
Explanation:
The migration script attempted to create a temporary
directory into which to copy the default stanzas for
migration. The creation completed successfully, but the
copy failed because the file system is full and there is
not enough space to complete the copy. The file system
needs to be purged.
System action:
The command exits with a non-zero return code.
User response:
Investigate the cause of the failure. The
varDir/cics_regions file system needs to be
maintained and purged.
Destination:
stderr
ERZ046202E The copy of the default stanzas to the
temporary directory failed
Explanation:
The migration script attempted to create a temporary

directory into which to copy the new stanzas for
migration. The creation completed successfully, but the
copy failed.
System action:
The command exits with a non-zero return code.
User response:
Investigate the cause of the failure. If the
varDir/cics_regions file system is full, CICS is
supposed to detect it as a separate error, but check it
anyway to make sure.
Destination:
stderr
ERZ046203I Usage: cicsmigrategateways {-?| -r
regionName [-w]}
Explanation:
This is the usage message for the cicsmigrategateways
command.
System action:
Program terminates.
User response:
valid parameters.
Destination:
stderr
ERZ046204E Cannot find database subdirectory for
region regionName
Explanation:
The command being run was unable to obtain the path
of the database subdirectory for the region.
System action:
error status.
User response:
name if using the -r option. Ensure also that the
database subdirectory is accessible.
Destination:
stderr
ERZ046205E The -l option is no longer a valid
option for the cicsmigrate command
Explanation:
The cicsmigrate command no longer accepts the -l
option. This is because there are no longer any log
servers to migrate for CICS on Open Systems.
System action:
error status.
User response:
368
ERZ046206E ERZ046211E
Run the command again specifying another
command-line option if required.
Destination:
stderr
ERZ046206E The stanza file stanzaFile does not
exist, or cannot be read, or is not
executable
Explanation:
CICS was unable to access the stanza file shown.
Information is required from the stanza for migration of
a region log or an SFS.
System action:
See the message following this one.
User response:
See the message following this one.
Destination:
stderr and stdout
ERZ046207E The attribute attributeName for log
server logServer could not be
obtained from the stanza file
stanzaFile
Explanation:
The attribute is required so that a clserver can be
started in place of the log server for migration. Either
the stanza file does not exist, cannot be read or does
not contain the attribute. This is possibly because the
log server definition was deleted.
Destination:
stderr and stdout
ERZ046209E Restart file restartFileName for server
serverName does not exist, is empty
or is not readable
Explanation:
The restart file is required so that a clserver can be
started in place of the log server for migration.
System action:
The log server is not started and any migration step that
requires the server fails.
User response:
If the problem can be corrected, any migration step that
fails can be run again. If the problem cannot be
corrected, the failed migration steps cannot be run
again. If this results in the failure to migrate an SFS
server, the next start of the SFS must be cold. If this
results in the failure to migrate a region logfile, the next
start of the region must be cold.
Destination:
stderr and stdout
ERZ046210E Subsystem subsystemName does not
exist
Explanation:
The subsystem definition is required to start a clserver,
in the place of a log server. It was supposed to exist for
the equivalent log server, but was deleted.
System action:
The log server is not started, and any migration step
that requires the server fails.
System action:
CICS is unable to start a clserver is place of a log
server. As a result the stage of migration that requires
this server to be running is halted.
User response:
If the log server definitions still exist and the problem is
corrected, the migration steps that have failed can be
run again if required.
User response:
None. The stage of migration that has failed cannot be
run again.
Destination:
stderr and stdout
ERZ046208E The userid userId of server
serverName has no home directory
Explanation:
The home directory of the servers contain vital
information for their migration. Without this information a
server cannot be migrated.
System action:
The migration step that requires the directory fails.
User response:
The failed migration steps cannot be restarted. If this
results in the failure to migrate an SFS, the next start of
the SFS must be a cold start. If this results in the failure
to migrate a region logfile, the next start of the region
must be a cold start.
Destination:
stderr and stdout
ERZ046211E CICS was unable to change the entry
for subsystem subsystemName
Explanation:
CICS was attempting to change the subsystem entry so
that it was able to be used to start a clserver in the
place of a log server, but the attempt failed.
System action:
User response:
None. The stage of migration that has failed cannot be
run again.
Destination:
369
ERZ046212I ERZ046219E
stderr and stdout
ERZ046212I Starting clserver serverName
Explanation:
The clserver is being started in place of the equivalent
log server.
System action:
Migration continues.
User response:
None
Destination:
stderr and stdout
ERZ046213E Start of clserver serverName failed
Explanation:
CICS was attempting to start a clserver in the place of a
log server, but the clserver failed to start.
System action:
User response:
See the previous message for the cause of the error. If
the error is corrected, the stage of migration that failed
as a result of the failure can be run again.
Destination:
stderr and stdout
ERZ046214I Waiting for clserver serverName to
initialize
Explanation:
CICS is waiting for the clserver to initialize.
System action:
When the server has initialized, migration continues.
User response:
None
Destination:
stderr and stdout
ERZ046216I Clserver serverName started

successfully
Explanation:
CICS has successfully started the clserver.
System action:
User response:
None
Destination:
stderr and stdout
ERZ046217I Dumping logfile for SFS server
serverName
Explanation:
CICS is about to attempt to dump the logfile of the SFS.
This is the first stage of SFS migration.
System action:
The logfile is dumped.
User response:
None
Destination:
stderr and stdout
ERZ046218I Logfile for SFS server serverName has
already been dumped
Explanation:
CICS has detected that this stage of migration for this
server was successfully completed previously.
System action:
The migration of this SFS progresses to the next stage.
User response:
None
Destination:
stderr and stdout
ERZ046219E SFS Server serverName not found in
stanza file stanzaFile
Explanation:
CICS is stopping the clserver as it is no longer required
for the stage of migration being run.
Explanation:
CICS attempted to obtain information relating to the
server from the stanza file, but the stanza contained no
record of the server. The server definition must be
deleted from the stanza after the first attempt to migrate
this server.
System action:
System action:
Migration of the server is halted.
User response:
None
User response:
If the migration of the server is required and the
problem can be corrected, the migration of the server
can be run again.
ERZ046215I Stopping clserver serverName
Destination:
stderr and stdout
Destination:
370
ERZ046220E ERZ046226E
stderr and stdout
ERZ046220E The attribute attributeName for SFS
obtained from the stanza file
stanzaFile
Explanation:
The attribute is required so that the SFS can be
migrated. Either the stanza file does not exist, cannot
be read or does not contain the attribute.
System action:
Migration of the server is halted.
User response:
If the migration of the server is required and the
problem can be corrected, the migration of the server
can be run again.
Destination:
stderr and stdout
ERZ046221E Home directory directoryName for
user userId does not have read, write
and execute permission
Explanation:
The userid of an SFS does not have the required
access to its home directory.
System action:
Migration of the SFS is halted.
User response:
Give user userId read, write and execute permission
for directory directoryName and run this stage of
migration again.
Destination:
stderr and stdout
ERZ046222E CICS cannot start clserver
serverName to migrate SFS server
serverName
Explanation:
Migration of the SFS requires the clserver, but the
clserver was unable to be started.
System action:
User response:
Earlier messages indicate the cause of the problem. If
these problems are corrected, this stage of migration
can be run again.
Destination:
stderr and stdout
ERZ046223E Dump of logfile to file dumpFile for

SFS server serverName failed. See
outFile.
Explanation:
CICS was attempting to dump the logfile of the SFS into
dumpFile during the first stage of SFS migration, but
this failed.
System action:
The output of the dump command is written to outFile
in the directory, varDir/cics_servers/SSD and migration
of the SFS is halted.
User response:
Examine outFile for the cause of the problem. If this is
corrected, this stage of migration can be run again.
Destination:
stderr and stdout
ERZ046224I Restoring logfile for SFS server
serverName
Explanation:
CICS is about to attempt to restore the logfile of the
SFS. This is the second and final stage of SFS
migration.
System action:
Migration of the SFS continues.
User response:
None
Destination:
stderr and stdout
ERZ046225I Logfile for SFS server serverName
already restored
Explanation:
CICS has detected that this stage of migration for the
server was previously successfully completed. As this is
the final stage of migration, migration of the server is
complete.
System action:
User response:
None
Destination:
stderr and stdout
ERZ046226E Dump or restart file for server
serverName does not exist
Explanation:
CICS requires that these files exist in the home
directory of the server to continue migration of the SFS.
Either a file was deleted or the server was successfully
migrated previously.
371
ERZ046227E ERZ046232E
System action:
ERZ046230E CICS is unable to start the volume

server. See outFile.
User response:
If migration of the SFS was not done before and is
required, the problem can be corrected by running SFS
migration again.
Explanation:
The volume server required to complete SFS migration
failed to start.
Destination:
stderr and stdout
System action:
The output of the volume server is written to outFile.
Migration of the SFS being migrated is halted.
ERZ046227E Archive directory directoryName for

created
User response:
Examine outFile for the cause of the problem. If the
error is corrected, and migration of the SFS is required,
run SFS server migration again.
Explanation:
The directory is required for migration of the SFS.
System action:
User response:
If migration of the SFS is required, create the directory
and run SFS migration again.
Destination:
stderr and stdout
ERZ046228I Starting volume server to restore
logfile for server serverName
Explanation:
A volume server is required for SFS migration, it is
being started.
Destination:
stderr and stdout
ERZ046231E An error occurred in mapping logical
volume volumeName. See outFile.
Explanation:
CICS received an error when attempting to map the
logical volume of the SFS being migrated.
System action:
The output of the command issued is written to outFile.
User response:
error is corrected, and migration of the SFS is required,
run SFS migration again.
System action:
CICS waits for up to 3 minutes for the server to
initialize.
Destination:
stderr and stdout
User response:
None
ERZ046232E Log Server serverName not found in

stanza file stanzaFile
Destination:
stderr and stdout
Explanation:
CICS was attempting to obtain information relating to
the log server from the stanza file. However, the
definition of the server serverName does not exist in
the stanza file.
ERZ046229E CICS is unable to generate a name for

the volume server
Explanation:
CICS issued the rpcutil command in order to generate a
name to be used for the volume server. This command
failed.
System action:
User response:
See preceding message for details of the error. If the
error is corrected and migration of the SFS is required,
Destination:
stderr and stdout
372
System action:
CICS is unable to start a clserver is place of the log
User response:
If the server no longer exists, the stage of migration that
has failed cannot be run again. However, if the log
server is defined on another machine, the clserver must
be started on the remote machine. SFS migration can
then be run again.
Destination:
stderr and stdout
ERZ046233E ERZ046239I
ERZ046233E An error occurred while restoring the
logfile for server serverName. See
outFile.
Explanation:
CICS failed to complete the second and final stage of
SFS migration. This stage restores the logfile of the
SFS, from the dump file created during the first stage of
SFS migration, back into the log volume.
System action:
The output of the restore command is written to outFile
in the directory, varDir/cics_servers/SSD, and
migration of the SFS is halted.
User response:
error is corrected and migration of the SFS is required,
Destination:
stderr and stdout
ERZ046234I Logfile successfully restored for server
serverName
Explanation:
The logfile of the SFS was successfully restored to the
log volume.
System action:
Migration of the SFS completes.
Migration of the region log data is halted.

User response:
If migration of the log data is required and the problem
can be corrected, migration of the region can be
restarted.
Destination:
stderr and stdout
ERZ046237E CICS cannot start clserver
serverName to migrate region
regionName
Explanation:
Migration of the region log data requires the clserver,
but the clserver was unable to be started.
System action:
User response:
Earlier messages indicate the cause of the problem. If
these problems are corrected, this stage of migration
can be run again.
Destination:
stderr and stdout
ERZ046238I Starting logfile conversion stage 1 for
region regionName
User response:
None
Explanation:
CICS is starting the first of 2 stages required to migrate
the region log data.
Destination:
stderr and stdout
System action:
ERZ046235I Converting log data for CICS region

regionName
Explanation:
CICS is about to convert the log data for region
regionName to the format used with the latest level of
the CICS product.
System action:
User response:
None
Destination:
stderr and stdout
ERZ046236E The attribute attributeName for region
regionName could not be obtained
from the stanza file stanzaFile
User response:
None
Destination:
stderr and stdout
ERZ046239I Starting logfile conversion stage 2 for
region regionName
Explanation:
CICS is starting the second and last stage required to
migrate the region log data.
System action:
User response:
None
Destination:
stderr and stdout
Explanation:
The attribute is required for migration of the region log
data, but it was unable to be read from the stanza file.
System action:
373
ERZ046240I ERZ046247I
ERZ046240I Logfile for region regionName
successfully converted
Explanation:
CICS has successfully migrated the log data for region
regionName.
System action:
User response:
None
Destination:
stderr and stdout
ERZ046241E Logfile conversion stage 2 for region
regionName failed, reason:
errorMessage
Explanation:
The second stage of region log data migration, for
region regionName, failed for the reason shown in
errorMessage.
System action:
User response:
can be corrected, migration of the region can be run
again.
Destination:
stderr and stdout
ERZ046242E Logfile conversion stage 1 for region
regionName failed, reason:
errorMessage
Explanation:
The first stage of region log data migration, for region
regionName, failed for the reason shown in
errorMessage.
System action:
User response:
can be corrected, migration of the region can be run
again.
Destination:
stderr and stdout
ERZ046243I No SFS servers to migrate
Explanation:
A request was made to migrate SFS servers. However,
no record of any previously started servers can be
found.
System action:
Migration proceeds to the next stage.
374
User response:
If this is unexpected, earlier messages show the cause
of the problem. If the problem can be corrected, SFS
server migration can be run again.
Destination:
stderr and stdout
ERZ046244I Starting migration of SFS server
serverName
Explanation:
CICS is about to start the migration of the SFS
serverName.
System action:
User response:
None
Destination:
stderr and stdout
ERZ046245E Migration of SFS server serverName
failed
Explanation:
CICS failed to migrate server serverName.
System action:
Migration of the server halted. Migration proceeds to the
next stage.
User response:
Refer to previous messages for the cause of the
problem.
Destination:
stderr and stdout
ERZ046246I Migration of SFS server serverName
successfully completed
Explanation:
CICS successfully migrated SFS serverName.
System action:
Migration proceeds to the next stage of migration.
User response:
Once migration is complete, the SFS can be warm
started.
Destination:
stderr and stdout
ERZ046247I Dump of logfile data for SFS server
serverName successful
Explanation:
CICS has successfully dumped the logfile data of the
SFS serverName. This is the first of two stages
required to migrate the log data of the SFS.
System action:
ERZ046248W ERZ046253E
Migration of the SFS continues to stage 2.
User response:
None
Destination:
stderr and stdout
ERZ046248W Restart files exist, the logfile for
server serverName has previously
been dumped
Explanation:
CICS has detected that the home directory of the server
already contains the files restart and restart.bak. This
indicates that the SFS was already migrated,
independently of the CICS migration procedure.
System action:
The migration of this SFS is halted and must not be run
again.
User response:
None
Destination:
stderr and stdout
ERZ046249I Generating the migration script. This
may take several minutes
Explanation:
The cicsmigrate command is creating the migration
script and adding migration commands into this script. If
you have many regions and servers, this process takes
several minutes to complete. Expect this to take at least
5 to 10 minutes, although this estimate depends on
machine size and usage.
System action:
User response:
None
Destination:
stderr
ERZ046250W fileName does not exist in the
archive
Explanation:
region archive.
System action:
User response:
Check that the CICS installation was successful. If you
were running the cicsimport command, prior to migrating
your regions for a new level of CICS, then ensure that
the cicsmigrate updates your region to add the missing
file. If the problem persists, contact your support
organization.
Destination:
stderr
ERZ046251I Usage: cicsgetattribute {-?|[-r
regionName] -c className -k
resourceName [-a attributeName] [-f
fileName]}
Explanation:
This is the usage message for the cicsgetattribute
command.
System action:
Program terminates.
User response:
If command was specified incorrectly, retry the
command with valid parameters.
Destination:
stderr
ERZ046252E Unable to retrieve value of attribute
attribute
Explanation:
The command attempted to get the value of the
attribute attribute from the stanza file for the specified
resource and class but was unable to find the definition.
System action:
Program terminates.
User response:
If command or the attribute was specified incorrectly,
retry the command with valid parameters.
Destination:
stderr
Explanation:
CICS was unable to execute programName. Either the
program is not in a directory specified in the PATH
environment variable or the user running the migration
does not have permission to execute it.
System action:
CICS is unable to start a clserver in place of the log
User response:
Check the paths in the environment variable PATH.
Ensure that $CICS/bin appears somewhere in this path.
Correct the problem and run again the stage of
migration that failed.
Destination:
stderr and stdout
375
ERZ046254E ERZ046278E
ERZ046254E clserver serverName failed to
initialize
Explanation:
CICS attempted to start the clserver serverName, but
the server failed to initialize correctly. This server is
required for migration.
System action:
The failed clserver is stopped and the stage of migration
that requires this server to be running is halted.
ERZ046272E Unable to delete table tableName on

DB2 server aliasName, return code is
returnCode
Explanation:
cicsdestroy was unable to delete the named DB2 table
on the named DB2 server while attempting to destroy a
region.
System action:
User response:
See previous message for possible causes of the error.
If none are obvious, it was possibly caused by CICS
stopping the server. If the error is corrected, the stage
of migration that failed as a result of the failure can be
run again.
User response:
DB2 is running, that the table exists, and that you have
sufficient authority to delete the table. Perform the
deletion by hand.
Destination:
stderr and stdout
Destination:
stderr
ERZ046255I The keytab file for region regionName

may be corrupted. Check before
running the region.
ERZ046273I Deleting DATABASE/2 (DB2) data for

the region regionName
Explanation:
The rgy_edit ktlist command on the keytab file for region
regionName was unable to find or access the keytab
file. This indicates possible corruption of the keytab file.
It can also be caused by wrong permissions on the file.
System action:
User response:
Ensure that the name server is running, and that you
have write permission to the file. Run rgy_edit domain
account ktlist -f keytabFileName.
Destination:
stderr
ERZ046256I Invalid database key for database class
className
Explanation:
The database entry key is invalid for the CICS database
class className.
System action:
User response:
If the error is in a permanent database entry edit the
stanza entry identified by subsequent messages and
correct the key. If necessary, recover the permanent
operation, correct the input and reenter the command.
Destination:
stderr
376
Explanation:
that DATABASE/2 (DB2) data for the region
regionName is being deleted from the DB2 server used
by the region regionName.
System action:
User response:
None
Destination:
stderr
ERZ046274I File System used by region
regionName cannot be identified
Explanation:
cicsdestroy was unable to identify the type of file system
used by the region regionName, possibly because the
region directory was already removed.
System action:
User response:
Remove unwanted files using cics administration
commands such as cicssdt for SFS.
Destination:
stderr
ERZ046278E DATABASE/2 (DB2) data cannot be
deleted for region regionName
Explanation:
DATABASE/2 (DB2) is unusable on this system. Either
the DB2 processes are missing or corrupt, or the db2
command cannot be found.
ERZ046279E ERZ046285E
System action:
The command continues destroying the region. The
DATABASE/2 (DB2) region data is still present.
User response:
Check that DATABASE/2 (DB2) is running correctly, and
that the necessary DB2 paths are in your PATH
Destination:
stderr
bytes failed
Explanation:
System action:
User response:
decreases and run the command again. If the problem
log and console.
Destination:
stderr
ERZ046280E Unexpected option option specified
on command line.
Explanation:
The option identified in the message was incorrectly
specified on the command line to the executing
program. The program does not accept this option as a
parameter.
System action:
User response:
Consult the usage message produced by the program
and respecify the options correctly.

and respecify the arguments correctly.
Destination:
stderr
ERZ046282E Option -option has already been
specified.
Explanation:
The option identified in the message was specified twice
in the command line to the executing program.
System action:
User response:
Remove the extra options specified and attempt to
reexecute the command.
Destination:
stderr
ERZ046283E Option -option must have a matching
argument.
Explanation:
The option identified in the message requires a
matching argument.
System action:
User response:
Respecify the command specifying the argument
required by the command. If an argument was specified
but begins with a - it was possibly interpreted as an
option; in this case, use a double - to ensure it is
treated as an argument.
Destination:
stderr
ERZ046284E The option -option must be specified.
Explanation:
The option identified in the message must be specified.
Destination:
stderr
System action:
ERZ046281E Unexpected argument arguments

specified on command line.
User response:
Respecify the command specifying the missing option
with any appropriate arguments.
Explanation:
The argument identified in the message was incorrectly
program. The program does not accept this argument
as a parameter.
System action:
User response:
Destination:
stderr
ERZ046285E At least one of the following options
must be specified optionList.
Explanation:
At least one of the options from the above list must be
specified.
System action:
377
ERZ046286E ERZ046292E
User response:
Respecify the command specifying the required option
System action:
The command terminates with a non-zero status.
User response:
Ensure that you have installed CICS correctly.
Destination:
stderr
Destination:
stderr
ERZ046286E At least optionNumb of the following

options must be specified optionList
ERZ046290E commandName was unable to open

file fileName, errno errorNumber.
Explanation:
At least optionNumb of the options from the above list
must be specified.
Explanation:
commandName was unable to open the specified file
for the reason given.
System action:
System action:
User response:
Respecify the command specifying the required options
User response:
Ensure that you have installed CICS correctly. Check
the value of errno for more information on the problem.
Destination:
stderr
Destination:
stderr
ERZ046287E Only one of the following options may

be specified optionList
ERZ046291E Unable to access directory directory,

errno errorNumber.
Explanation:
Only one of the options from the above list can be
specified.
Explanation:
The command you entered attempted to alter
permissions on directory directory but was unable to do
so.
System action:
User response:
Respecify the command specifying only one on the
options from the above list.
Destination:
stderr
ERZ046288E A maximum of optionNumb options
may be specified from optionList
Explanation:
A maximum of optionNumb options can be specified
from the above list.
System action:
User response:
Respecify the command specifying only the required
options with any appropriate arguments.
Destination:
stderr
Explanation:
The command you entered encountered a problem
while obtaining information about the CICS system
installed on your machine.
378
System action:
User response:
Check the directory permissions, also the value of errno
for more information on the problem.
Destination:
stderr
ERZ046292E Unable to get the current directory,
errno errorNumber.
Explanation:
The command you entered tried to find out which
directory you are in but was unable to do so.
System action:
User response:
Check that you have installed CICS correctly. Check the
value of errno for more information on the problem.
Destination:
stderr
ERZ046295I ERZ046309W
ERZ046295I Successfully deleted exsisting
principal principal
ERZ046298W Unable to modify the group

ownership for the file fileName
Explanation:
The command detected that a principal already existed
for CICS. To ensure that all information is recreated
successfully, the existing principal was successfully
deleted. This principal is recreated in the next stage of
the operation.
Explanation:
The command attempted to modify the group ownership
for the file identified in the message but the attempt
failed.
System action:
User response:
This message is for information only.
Destination:
stderr
ERZ046296W Unable to get details for security
group cicsterm
Explanation:
The command attempted to retrieve details for the
security group cicsterm, but the inquire failed.
System action:
User response:
The group cicsterm is normally created during product
installation and configuration. The lack of the group can
mean that some part of configuration is incomplete. The
command continues, but youare responsible for setting
the protection controls on the keytab file that is created.
Destination:
stderr
ERZ046297W Unable to get details for security
group cicsterm
Explanation:
The command attempted to retrieve details for the
security group cicsterm, but the inquire failed.
System action:
error status.
User response:
The group cicsterm is normally created during product
installation and configuration. The lack of the group can
mean that some part of configuration is incomplete. If
you have deliberately deleted this security group then
rerun this command with Ignore Errors options to
bypass this error. If you do this, then you are
responsible for setting the security on the keytab file.
Destination:
stderr
System action:
The command continues, but the group ownership of
the file is unchanged and can possibly need to be
modified to enable clients access to the file.
User response:
Investigate the cause of the error and manually change
the group owner of the file to be the group cicsterm.
Destination:
stderr
ERZ046299E Unable to modify the group
ownership for the file fileName
Explanation:
The command attempted to modify the group ownership
for the file identified in the message but the attempt
failed.
System action:
error status.
User response:
Investigate the cause of the errror and correct it. If you
wish to set the group owner of the file manually then
rerun the command specifying the IgnoreErrors flag
and then set the file ownership by hand.
Destination:
stderr
ERZ046302E Problem using region regionName
Explanation:
CICS encountered a problem accessing details about
region regionName.
System action:
The command terminates with an abnormal return code.
User response:
Ensure that the region exists and is properly configured.
If it does, ensure that you have installed CICS correctly.
Destination:
stderr
ERZ046309W Unable to change the ownership of
file fileName for region regionName to
userId:groupId
Explanation:
Unsuccessful attempt to change the ownership of file
fileName in region regionName. This is possibly
because the region file system directory is mounted
379
ERZ046321E ERZ046328W
from another machine. It is also possibly because the
userid or groupid of the original owner of the file does
not exist on this machine.
The command abnormally terminates. The directory

structure for the CICS system is created, but the CICS
subsystem is not.
System action:
The command continues creating the region. The region
is possibly unusable until you manually change the
ownership of this file or directory.
User response:
Check that the input file for the CICS system you are
trying to create is not corrupt. Check that the directory
structure for the region you are trying to import was
created correctly and, more specifically, that the
RD.stanza file is intact. Run the command again using
the -F (force) option.
User response:
Change the ownership of the file to userId:groupId.
Use the operating system command chown.
Destination:
stderr
ERZ046321E Unable to get information on file or
directory directoryName
Explanation:
The command you entered tried to obtain information on
the specified directory but was unable to do so.
System action:
The command abnormally terminates.
User response:
Check the directory exists and is readable.
Destination:
stderr
ERZ046322E Could not find stanza definition for
region regionName
Explanation:
The command you entered tried to retrieve information
from the CICS system just created but was unable to do
so.
System action:
The command abnormally terminates. The directory
structure for the CICS system is created, but the CICS
subsystem is not.
User response:
Check that the input file for the CICS system you are
trying to create is not corrupt. Check that the directory
structure for the region you are trying to import was
created correctly and, more specifically, that the
RD.stanza file is intact. Run the command again using
the -F (force) option.
Destination:
stderr
ERZ046323E Could not modify stanza definition for
server regionName
Explanation:
The command you entered tried to alter the region
stanza definitions in line with the -S or -D option you
gave it, but was unable to do so.
System action:
380
Destination:
stderr
ERZ046326E Error opening temporary file
fileName, error number errorNumber
Explanation:
cicsimport tried to open a working file but was unable to
do so.
System action:
User response:
Check that you have sufficient permissions to write to
the regions directory and that there is enough space in
the file system. Refer to the error number for more
information.
Destination:
stderr
ERZ046327E Unable to write to temporary file
Explanation:
cicsimport tried to write to a working file but was unable
to do so.
System action:
User response:
Check that you have sufficient permissions to write to
the regions directory and that there is enough space in
the file system. Refer to the error number for more
information.
Destination:
stderr
ERZ046328W Unable to obtain details of user
number userNumber, assuming user
cics
Explanation:
cicsimport tried to get details on the user number
specified but was unable to do so.
System action:
The command continues and assumes thw owning
userid is cics
ERZ046329W ERZ046337W
User response:
Check that the user exists. Check also that you have
installed the product according to the documentation.
ERZ046332W Unable to change to directory

dirName, errno errorNumber
Destination:
stderr
Explanation:
The command you entered tried to change directory to
dirName but was unable to do so.
ERZ046329W Unable to obtain details of group

number groupNumber, assuming
group cics
System action:
The command continues but creates all files in the
current directory.
Explanation:
cicsimport tried to get details on the group number
specified but was unable to do so.
User response:
Check that you have permission to write to the directory
specified. Check also that there is space in the file
system.
System action:
The command continues and assumes thw owning
group is cics
Destination:
stderr
User response:
Check that the group exists. Check also that you have
installed the product according to the documentation.
ERZ046335E Option -l not supported under

Windows NT
Destination:
stderr
Explanation:
You specified the -l option of cicsexport or cicsimport
but this is not supported under Windows NT.
ERZ046330W Error opening temporary file

Explanation:
cicsimport tried to open a working file but was unable to
do so.
System action:
The command continues, but you can possibly
encounter problems later on with ownership.
System action:
User response:
Run the command again without the -l option.
Destination:
stderr
ERZ046336W Unable to get machine name
User response:
Check that the import file was created correctly. This
error can possibly cause problems later on if you are
importing a file between different machines.
Explanation:
cicsdestroy needed the host name of your machine in
order to determine which SFS files to delete. It was
unable to get that information.
Destination:
stderr
System action:
The command continues if you have specified the -I
option, but your SFS data is not deleted.
User response:
This most likely indicates an operating system error.
Check that your machine was set up with the correct
name. You possibly need to alter the DefaultFileServer
attribute of your regions definitions file to explicitly state
the name of your machine.
Explanation:
System action:
User response:
Destination:
stderr
Destination:
stderr
ERZ046337W Failed to parse attribute attribute,
current value value
Explanation:
While executing cicsdestroy, the command attempted to
interpret the expanded value for the attribute identified
in the message, but this attempt failed.
System action:
381
ERZ046338I ERZ046345E
The command halts its attempt to delete the regions
SFS files and skips to the next stage.
System action:
User response:
User response:
Check that the directory exists and that you have
sufficient priviledge to access it. Use the error number
for more information.
Destination:
stderr
ERZ046338I Successfully exported region
regionName
Explanation:
cicsexport successfully made a copy of the named
region.
System action:
The command ends successfully.
User response:
Destination:
stderr
ERZ046339I Successfully imported region
regionName
Destination:
stderr
ERZ046343E transactionName unable to open
message file fileName for region
regionName
Explanation:
The LogViewer transaction transactionName was unable
to open the log file for the region named
System action:
The transaction ends abnormally
User response:
Check that the message file named in the message
exists, and that you have permission to access it
Destination:
Terminal
Explanation:
cicsimport successfully created a new region from the
specified archive region.
ERZ046344E transactionName cannot be run on this

terminal
System action:
The command ends successfully.
Explanation:
The LogViewer transaction transactionName is not
supported on this type of terminal, and cannot be run
User response:
Destination:
stderr
ERZ046341E Cannot find region regionName to
destroy
Explanation:
Your attempt to destroy the named region failed
because the command was unable to find it.
System action:
error status.
User response:
Ensure you gave the correct region name.
Destination:
stderr
ERZ046342W Unable to alter permissions of
directory directoryName, errno
errorNumber.
Explanation:
The command you entered tried to alter the permissions
of directory directoryName but was unable to do so.
382
System action:
User response:
Use a terminal with a TermType value of 145 (0x91) in
the WD definition
Destination:
Terminal
ERZ046345E transactionName failed to complete
initialization successfully
Explanation:
The LogViewer transaction transactionName
encountered an error during initialization, and cannot
continue This error is shown when an internal CICS
error occurs, and indicates a more serious problem with
CICS
System action:
User response:
Check the error logs for indications of other CICS errors
Destination:
Terminal
ERZ046346E ERZ046354E
ERZ046346E transactionName unable to re-open
message file fileName for region
regionName
Explanation:
to reopen the log file for the region named during the
Refresh operation
System action:
User response:
Check that the message file named in the message
exists, and that you have permission to access it
Destination:
Terminal
ERZ046347E transactionName unable initialize
region resources for region
regionName.
Explanation:
to initialize the region resources it required for the
named region. It is likely that a more serious problem
with CICS has already occurred.
System action:
User response:
Check the error logs for indications of other CICS errors
Destination:
Terminal
ERZ046348I Creating region regionName from
archive archiveName
Explanation:
This message is produced by cicsimport to indicate that
the region regionName is being created from archive
file archiveName.
System action:
User response:
None
Destination:
stderr
ERZ046349I Usage: cicsexport {-?| [-r regionName]
[-o outFile]}
Explanation:
This is the usage message for the cicsexport command.
System action:
Command terminates.

valid parameters. It is possible that you have specified
an option of zero length. See the TXSeries for
information.
Destination:
stderr
ERZ046350E regionName rejected - CICS region
name may not contain a badCharacter
Explanation:
The region name regionName that you entered
contained a bad character. This syntax is illegal for
CICS region names.
System action:
error status.
User response:
Choose another name for your region that does not
contain the bad character.
Destination:
stderr
ERZ046351I Deleting Oracle data for the region
regionName
Explanation:
that CICS file control data mapped onto Oracle for the
region regionName is being deleted from the Oracle
server used by the region regionName.
System action:
User response:
None
Destination:
stderr
ERZ046354E The cicsdestroy command failed to
complete successfully.
Explanation:
cicsdestroy ended with a non zero return code. Previous
error messages indicate the cause of failure.
System action:
The cicsdestroy command ends.
User response:
Check the User Response given for the previous error
messages. Rerun cicsdestroy using the -I option.
Destination:
stderr
User response:
383
ERZ046355E ERZ046362E
ERZ046355E The imported stanzas are not at the
current machine migration level.
Explanation:
The regions RD stanza, and the SFS servers SSD
stanza, if it exists, must be at the current machine
migration level.
System action:
User response:
Bring the stanzas up to the machine migration level and
retry.
Destination:
stderr
ERZ046356E Could not access subkeys for
RegistryKey (error code: ErrorCode).
Explanation:
During migration, the subkeys for the RegistryKey was
unable to be accessed in the registry. The ErrorCode
can be used to determine the cause of the error.
System action:
User response:
Note the registry key whose subkeys were unable to be
accessed.
Destination:
stderr
ERZ046357E Could not access values for
RegistryKey (error code: ErrorCode).
Explanation:
During migration, the values for the key RegistryKey
was unable to be accessed in the registry. The
ErrorCode can be used to determine the cause of the
error.
System action:
User response:
Note the registry key whose values were unable to be
accessed.
Destination:
stderr
ERZ046358E Could not migrate the key
RegistryKey since it already exists.
Explanation:
During migration, duplicate keys were found in the old
and new registry entries.
System action:
Processing continues. Old keys are left in the registry.
User response:
384
Note the registry key that was unable to be migrated.

Destination:
stderr
ERZ046359E Could not set value RegistryValue in
key RegistryKey (error code:
ErrorCode).
Explanation:
During migration, the value for the key RegistryKey
was unable to be set in the registry. The ErrorCode
can be used to determine the cause of the error.
System action:
Processing continues. The particular key to which this
value belongs is deleted in the new registry entry.
User response:
Note the registry key and the value that failed.
Destination:
stderr
ERZ046360E Could not close key: RegistryKey
(error code: ErrorCode).
Explanation:
During migration, the key RegistryKey was unable to
be closed in the registry. The ErrorCode can be used
to determine the cause of the error.
System action:
User response:
None.
Destination:
stderr
ERZ046361E Could not create key: RegistryKey
Explanation:
be created in the registry. The ErrorCode can be used
to determine the cause of the error.
System action:
User response:
Note the registry key that was unable to be created.
Destination:
stderr
ERZ046362E Could not open key: RegistryKey
Explanation:
be accessed in the registry. The ErrorCode can be
used to determine the cause of the error.
ERZ046363E ERZ046370E
System action:
ERZ046366I Key RegistryKey already exists.
User response:
Note the registry key that was unable to be accessed.
Explanation:
During migration, information is displayed about keys
that already exist for the new key in the registry.
Destination:
stderr
ERZ046363E Could not delete key: RegistryKey
Explanation:
be deleted from the registry. The ErrorCode can be
used to determine the cause of the error.
System action:
User response:
Note the registry key that was unable to be deleted.
Destination:
stderr
ERZ046364I Could not open key: RegistryKey. No
need to migrate information.
Explanation:
During migration, the old key RegistryKey was not
found. This means that no migration of registry needs to
be done.
System action:
Processing stops.
User response:
None.
Destination:
stderr
ERZ046365E Error: no 2 regions or SFS servers
can have the same name.
Explanation:
During migration, either 2 SFS servers or 2 regions with
the same name were found i.e. there is a similar entry
in the old as well as the new registry key.
System action:
Processing continues. That particular entry is not
migrated.
User response:
Note the error that occurred.
Destination:
stderr
System action:
User response:
None.
Destination:
stderr
ERZ046367I Migrating key RegistryKey...
Explanation:
During migration, the keys being migrated are
displayed.
System action:
User response:
None.
Destination:
stderr
ERZ046368I Migrating value RegistryValue...
Explanation:
During migration, the values of keys being migrated are
displayed.
System action:
User response:
None.
Destination:
stderr
ERZ046369E Registry migration failed.
Explanation:
Indicates the migration process failed.
System action:
Processing stops.
User response:
Check previous error messages for failures. Contact
Service giving the full output of the migration command.
Destination:
stderr
ERZ046370E Registry migration partially
successful.
Explanation:
Some of the keys and their values were not migrated.
System action:
385
ERZ046371I ERZ046378E
User response:
Check previous error messages for failures. Contact
Service giving the full output of the migration command.
Destination:
stderr
ERZ046371I Registry migration successful.
Explanation:
Registry migration was successful.
System action:
System is in a consistent state.
User response:
None.
Destination:
stderr
ERZ046372E Unexpected error occurred.
Explanation:
This is possibly an error in the CICS code.
System action:
Processing stops.
User response:
Contact Service.
Destination:
stderr
ERZ046373I Invoke cicsmigrate region_name for
each CICS region.
Explanation:
This message provides the syntax for cicsmigrate.cmd.
System action:
None.
User response:
None.
ERZ046375I Migrating CICS resources.

Explanation:
This message indicates the phase of migration being
performed.
System action:
None.
User response:
None.
Destination:
stderr
ERZ046376E Error ERROR_LEVEL getting region
directory information.
Explanation:
cicsmigrate.cmd was unable to find the location of the
CICS region directory.
System action:
Only items independent of a particular region are
migrated.
User response:
Contact service.
Destination:
stderr
ERZ046377E Error ERROR_LEVEL getting SFS
schema directory information.
Explanation:
cicsmigrate.cmd was unable to find the location of the
SFS schema directory.
System action:
Migration cannot continue.
User response:
Contact service.
Destination:
stderr
Destination:
stderr
ERZ046378E Unrecognised migration level.

ERZ046374I Migrating the NT registry.
Explanation:
cicsmigrate.cmd was unable to determine the migration
level of region being migrated.
Explanation:
performed.
System action:
System action:
None.
User response:
Contact service.
User response:
None.
Destination:
stderr
Destination:
stderr
386
ERZ046379I ERZ046386E
ERZ046379I Migrating region regionName from
migration level migration_level.
ERZ046383I Updating the resourceName in region

regionName.
Explanation:
performed.
Explanation:
Resource resourceName is being updated in region
regionName
System action:
None.
System action:
The definition of resourceName is updated in the
region being migrated.
User response:
None.
Destination:
stderr
ERZ046380I Updating the migration version stamp
in each region stanza entry.
Explanation:
performed.
System action:
Each stanza entry is updated to the new migration level.
User response:
None.
Destination:
stderr
ERZ046381I Updating the ClassTableSize.
Explanation:
performed.
System action:
The ClassTableSize is updated.
User response:
None.
Destination:
stderr
ERZ046382I Creating a temporary region.
Explanation:
performed.
System action:
A temporary region is created for use during migration.
It is deleted at the end of the migration process.
User response:
None.
Destination:
stderr
User response:
None.
Destination:
stderr
ERZ046384E Creating the resourceName in region
regionName.
Explanation:
Resource resourceName is being created in region
regionName
System action:
The new resource is created in the region being
migrated.
User response:
None.
Destination:
stderr
ERZ046385I Deleting the temporary region.
Explanation:
performed.
System action:
The temporary region, used during the migration, is
removed.
User response:
None.
Destination:
stderr
ERZ046386E Region regionName is already at
migration level migration_level.
Explanation:
The region specified was found already to be at the
target migration level.
System action:
The region is not changed.
User response:
Run cicsmigrate.cmd if other regions need to be
migrated.
Destination:
stderr
387
ERZ046387E ERZ047003E
ERZ046387E No region specified.
Explanation:
cicsmigrate.cmd was invoked without a region name.
System action:
Only items independent of a particular region are
migrated.
User response:
Run cicsmigrate.cmd again, but specify the name of a
region you wish to migrate.
Destination:
stderr
ERZ046388I Updating the migration version stamp
in cics_servers stanzas.
Explanation:
performed.
System action:
None.
User response:
None.
Destination:
stderr
ERZ046389E Invalid link or file File under the
region %2$s
Explanation:
When files under a region is actually a link to
nonexisting file, cicsexport had complained with
ERZ046002E - Unable to access the region symbolic
link name. It was very difficult to spot out the original
cause of the problem. Now the new message says the
there exists a link (File) under the region (
RegionName). But the file referred by the link does not
exist.
System action:
None.
User response:
Needs to check where the link points to, or whether the
file referred by the link exists or not. Either case the link
should point to a valid existing file or it should be a valid
file/directory under the region
Destination:
stderr
ERZ047001I CICS is out of Task Private Storage in
transaction transId on terminal termId
Explanation:
The Application Server running transaction transId on
terminal termId has exhausted its pool of task private
storage. A GETMAIN call has failed to satisfy a storage
request.
388
System action:
CICS raises the NOSTG condition against the
transaction. A user defined condition handler is invoked
if one has been defined. If no handler is defined for the
NOSTG or ERROR condition then the transaction is
User response:
Try to reduce the use of GETMAIN in transaction
transId.
Destination:
CSMT
ERZ047002I CICS is out of Task Private Storage in
transaction transId executing as a
background task
Explanation:
The Application Server running transaction transId has
exhausted its pool of task private storage. A GETMAIN
call has failed to satisfy a storage request. The
transaction was executing as a background ATI task, or
a back-end communications transaction (for DTP,
function shipping or transaction routing).
System action:
CICS raises the NOSTG condition against the
transaction. A user defined condition handler is invoked
if one has been defined. If no handler is defined for the
NOSTG or ERROR condition then the transaction is
User response:
Try to reduce the use of GETMAIN in transaction
transId.
Destination:
CSMT
ERZ047003E Transaction transId on terminal
termId, attempted to free storage at
address address. This address is not a
valid storage address
Explanation:
Transaction transId executed a FREEMAIN call for a
storage address which was not acquired by performing
a GETMAIN. The invalid storage address is address.
Invalid addresses are storage addresses which do not
point at storage areas allocated by a GETMAIN call or
which have already been processed by another
FREEMAIN call.
System action:
CICS raises an A47B abend code against the
transaction. A user defined abnormal termination
handler is invoked if one has been defined. If no
handler is defined then the transaction is terminated
abnormally .
User response:
ERZ047004E ERZ047008E
Investigate the use of FREEMAIN in the programs
associated with transaction transId. Addresses passed
to FREEMAIN must point at storage allocated by a
GETMAIN call.
Destination:
CSMT
ERZ047004E Transaction transId executing as a
background task, attempted to free
storage at address address. This
address is not a valid storage address
Explanation:
Transaction transId executed a FREEMAIN call for a
storage address which was not acquired by performing
a GETMAIN. The invalid storage address is address.
Invalid addresses are storage addresses which do not
point at storage areas allocated by a GETMAIN call or
which have already been processed by another
FREEMAIN call. The transaction was executing as a
background ATI task, or a back-end communications
transaction (for DTP, function shipping or transaction
routing).
System action:
CICS raises an A47B abend code against the
abnormally .
User response:
Investigate the use of FREEMAIN in the programs
associated with transaction transId. Addresses passed
to FREEMAIN must point at storage allocated by a
GETMAIN call.
Destination:
CSMT
ERZ047005I CICS is no longer out of Task Private
Storage in transaction transId on
terminal termId
Explanation:
The Application Server running transaction transId
returned some task private storage to an empty task
private storage pool. This can possibly allow
subsequent GETMAIN calls in transaction transId to
succeed.
System action:
The Application Server continues.
User response:
None
Destination:
CSMT

Storage in transaction transId
executing as a background task
Explanation:
The Application Server running transaction transId
returned some task private storage to an empty task
private storage pool. This can possibly allow
subsequent GETMAIN calls in transaction transId to
succeed. The transaction was executing as a
routing).
System action:
The Application Server continues.
User response:
None
Destination:
CSMT
ERZ047007E CICS has detected a storage
inconsistency in transaction transId
on terminal termId. The inconsistency
is in storage area address1 at address
address2
Explanation:
A transaction program has overrun a storage area
allocated by a GETMAIN call. The storage area begins
at address address1 and the inconsistency occurs at
address address2.
System action:
CICS raises an A47C abend code against the
abnormally .
User response:
If the definition of transaction transId indicates that a
transaction dump is taken use the dump file to
investigate the problem. If no dump is produced change
the Transaction Definition to force the transaction to
produce a dump if it is terminated abnormally. The
probable cause is that application code that copies data
from some storage area to the GETMAIN allocated area
is copying too much.
Destination:
CSMT
ERZ047008E CICS cannot initialize Task Private
Storage
Explanation:
CICS attempted to initialize Task Private storage, but
was unsuccessful. This error indicates a problem in
underlying system software.
System action:
389
ERZ047009E ERZ047012E
CICS abnormally terminates the Application Server.
User response:
Destination:
console.msg
executing as a background task. The
inconsistency is in storage area
address1 at address address2
Explanation:
address address2. The transaction was executing as a
routing).
System action:
CICS raises an A47C abend code against the
abnormally .
User response:
If the definition of transaction transId indicates that a
transaction dump is taken use the dump file to
investigate the problem. If no dump is produced change
the Transaction Definition to force the transaction to
produce a dump if it is terminated abnormally. The
probable cause is that application code that copies data
from some storage area to the GETMAIN allocated area
is copying too much.
Destination:
CSMT
inconsistency in storage area address1
at address address2
Explanation:
CICS has overrun a storage area allocated by a
GETMAIN call. The storage area begins at address
address1 and the inconsistency occurs at address
address2.
System action:
CICS raises an internal error code. This error can
possibly result in an Application Server or the region
being terminated abnormally.
User response:
Use transaction or region dumps to investigate this
problem. It is possible that user application code is
writing to a storage area allocated to CICS internal use.
390
Check the use made of pointers to GETMAIN storage in

your application. If the problem persists contact your
Destination:
console.msg
ERZ047011E CICS raised an unexpected error in
transaction transId on terminal termId
Explanation:
CICS was unable to allocate, or release, the control
block controlling a GETMAIN request.
System action:
CICS raises a NOSTG condition or A47D abend code
against the transaction, depending on the underlying
cause. A user defined condition handler or abnormal
termination handler is invoked if one has been defined.
If no handler is defined then the transaction is
User response:
problem is storage shortage for CICS control blocks,
retry the transaction. If the condition persists and affects
many transactions, restart the region with an expanded
Region Pool size, by adjusting the value for the
MaxRegionPool attribute in the Region Definition or by
using CICS start up parameters. If other messages
indicate that the problem is a software error in CICS,
Destination:
CSMT
ERZ047012E CICS raised an unexpected error in
transaction transId executing as a
background task
Explanation:
block controlling a GETMAIN request. The transaction
was executing as a background ATI task, or a back-end
communications transaction (for DTP, function shipping
or transaction routing).
System action:
CICS raises a NOSTG condition or A47D abend code
against the transaction, depending on the underlying
cause. A user defined condition handler or abnormal
termination handler is invoked if one has been defined.
If no handler is defined then the transaction is
User response:
problem is storage shortage for CICS control blocks,
retry the transaction. If the condition persists and affects
many transactions, restart the region with an expanded
Region Pool size, by adjusting the value for the
MaxRegionPool attribute in the Region Definition or by
ERZ047013E ERZ047019W
using CICS start up parameters. If other messages
Destination:
CSMT
ERZ047013E CICS raised an unexpected storage
error
Explanation:
block controlling a task private storage area used
internally by CICS.
System action:
CICS abnormally terminates the Application Server or
CICS control process which is affected. If a CICS
control process is affected CICS abnormally terminates
the region.
User response:
Other messages in console.msg indicate the underlying
cause of this problem. If the cause of the problem is
storage shortage for CICS control blocks then some
transactions possibly did not start. Retry transactions. If
the condition persists restart the region with an
expanded Region Pool size, by adjusting the value for
the MaxRegionPool attribute in the Region Definition or
by using CICS start up parameters. If other messages
Destination:
console.msg
ERZ047014W CICS has detected a storage
on terminal termId. The inconsistency
is in storage area address1 at address
address2
Explanation:
address address2.
System action:
None
User response:
The probable cause is that application code that copies
data from some storage area to the GETMAIN allocated
area is copying too much.
Destination:
CSMT

executing as a background task. The
inconsistency is in storage area
address1 at address address2
Explanation:
address address2. The transaction was executing as a
background ATI task, or as a back-end communications
routing).
System action:
None
User response:
The probable cause is that application code that copies
data from some storage area to the GETMAIN allocated
area is copying too much.
Destination:
CSMT
inconsistency in storage area address1
at address address2
Explanation:
address address2.
System action:
None
User response:
It is possible that user application code is writing to a
storage area allocated to CICS internal use. Check the
use made of pointers to GETMAIN storage in your
application.
Destination:
CSMT
ERZ047019W CICS cannot update the
GETMAIN/FREEMAIN abend statistic
for transaction transId
Explanation:
CICS was unable to increment the number of storage
abends statistic field in a transaction record.
System action:
The CICS Application Server continues.
User response:
The statistics handling failure is due to an error in CICS;
Destination:
CSMT
391
ERZ047020I ERZ048003E
ERZ047020I CICS is out of Task Private Storage
Explanation:
A CICS Application Server has exhausted its pool of
task private storage while servicing a request from
internal CICS software.
System action:
CICS abnormally terminates an Application Server or
CICS control process. This error can possibly result in
CICS abnormally terminating the region.
User response:
This error can cause a transaction or program to fail.
Retry failed transactions. Check your transactions use
of GETMAIN storage. It is possible that certain
transactions are allocating areas of storage that exceed
their requirements. It may be possible to reduce a
transactions use of task private storage. If the condition
Destination:
console.msg
ERZ047021E An internal CICS function attempted
to free storage at address address. This
address is not a valid storage address
Explanation:
An internal CICS function has attempted to free task
private storage which it never acquired or has already
freed.
System action:
CICS raises an error on the calling function, which can
result in an abend condition being raised.
ERZ048001I CICS is under stress. CICS is short on

Task Shared storage
Explanation:
CICS breached the configured task shared pool storage
threshold. CICS is using the last few percent of this
pool, and CICS is under stress.
System action:
CICS can suspend tasks pending availability of task
shared storage.
User response:
Shut down the CICS region and reconfigure the task
shared storage pool size (MaxTSHPool) and threshold
(TaskShPoolThreshold) attribute values in the Region
Definitions or by overriding the Region Definitions on
the CICS command line.
Destination:
console.msg
ERZ048002I CICS is under stress. CICS is short on
Run Time Support storage
Explanation:
CICS breached the configured run time storage pool
threshold. CICS is using the last few percent of this
pool, and CICS is under stress.
System action:
CICS can terminate tasks abnormally or can terminate
the region due to insufficient storage in the region pool.
User response:
This error indicates a problem in CICS software.
User response:
Shut down the CICS region and reconfigure the run
time storage pool size (MaxRegionPool) and threshold
(RegionPoolThreshold) attribute values defined in the
Region Definitions or by overriding the Region
Definitions on the CICS command line.
Destination:
console.msg
Destination:
console.msg

Storage

termId, attempted to free task shared
storage at address address. This
address is invalid
Explanation:
A CICS Application Server has returned task private
storage to an empty task private storage pool.
System action:
The Application Server or CICS control process
continues.
User response:
None
Destination:
console.msg
Explanation:
The transaction transId attempted to free some task
shared storage at the address address. This address is
invalid as it is not the beginning of a storage area
allocated from the task shared pool.
System action:
CICS abnormally terminates the application server or
CICS control process. If a CICS control process is
terminated CICS can abnormally terminate the region. If
an abnormal termination is raised on an application
server a user defined abnormal termination handler is
executed if one is defined.
User response:
392
ERZ048004E ERZ048010E
Check the use of the GETMAIN SHARED call and
subsequent FREEMAIN calls in transaction transId. If
shared storage is acquired by GETMAIN then, when it
is released, the storage address returned by GETMAIN
must be passed to FREEMAIN. Retry failed transactions
once they have been checked. If the condition persists
it possibly indicate a software problem in CICS. In this
instance contact your support organization.
Destination:
console.msg
termId attempted to free run time
support storage at address address.
This address is invalid
Explanation:
Transaction transId attempted to free some run time
support storage at address address. This address is
invalid as it is not the beginning of a storage area
allocated from the region pool.
System action:
terminated CICS can abnormally terminate the region. If
an abnormal termination is raised on an application
server a user defined abnormal termination handler is
executed if one is defined.
User response:
This message indicates a software problem in CICS.
Destination:
console.msg
ERZ048005I CICS is no longer short on task shared
storage
Explanation:
CICS has released enough task shared storage so that
the task shared pool is no longer under stress.
Suspended tasks now continue.
System action:
CICS continues.
User response:
Destination:
console.msg
ERZ048006I CICS is no longer short on run time
support storage
Explanation:
CICS has released enough storage so that the region
pool is no longer under stress.
System action:
User response:
None
Destination:
console.msg
ERZ048007E U4801: CICS self-consistency
checking has detected an
unrecoverable error
Explanation:
CICS found inconsistencies in the region pool control
structures. The console.msg log contains one or more
messages prior to this one, indicating the nature of the
problem.
System action:
User response:
This message indicates a software problem in CICS. If
the Region Definitions SysDump attribute is set to yes a
region dump file is produced. Restart the region
(ensuring that the the region is configured to take a
organization.
Destination:
console.msg
ERZ048008E U4802: CICS detected an
unrecoverable error freeing region pool
storage
Explanation:
Either CICS is attempting to free region pool storage it
has already freed, or a severe inconsistency in the
region storage management structures has occurred.
The console.msg log also contains one of the messages
ERZ4804E, ERZ4836E, or ERZ4846E indicating the
address that causes the error.
System action:
User response:
This message indicates a software problem in CICS. If
the Region Definitions SysDump attribute is set to yes a
region dump file is produced. Restart the region
(ensuring that the the region is configured to take a
organization.
Destination:
console.msg
ERZ048010E U4803: CICS did not initialize task
shared pool storage
Explanation:
CICS storage initialization detected an unrecoverable
error during region start-up. The problem is possibly due
to invalid task shared pool configuration parameters in
the Region Definition. The task shared pool size must
393
ERZ048012E ERZ048015E
be between the system imposed limits on the minimum
and maximum sizes of shared memory segments. The
problem is possibly due to insufficient memory, or else
the system-imposed limit on the number of shared
memory segments was possibly reached.
System action:
CICS abnormally terminates the region during start-up.
User response:
Check that the values for task shared pool configuration
are correct in the Region Definitions. The TXSeries for
Multiplatforms Administration Reference provides
guidance on region attributes. Check also that none of
the systems limits on shared memory segments have
been exceeded. Restart the region with new task
shared pool values in the Region Definition or by
overriding the Region Definition on the CICS command
line.
Destination:
console.msg
ERZ048012E U4803: CICS did not initialize region
pool storage.
Explanation:
CICS storage initialization detected an unrecoverable
error during region start-up. The problem is possibly due
to invalid region pool configuration parameters in the
Region Definition. The region pool size must be
between the system imposed limits on the minimum and
maximum sizes of shared memory segments. The
problem is possibly due to insufficient memory, or else
the system-imposed limit on the number of shared
memory segments was possibly reached.
System action:
CICS abnormally terminates the region during start-up.
User response:
Check that the values for region pool configuration are
correct in the Region Definitions. The TXSeries for
guidance on region attributes. Check also that none of
the systems limits on shared memory segments have
been exceeded. Restart the region with new region pool
values in the Region Definition or by overriding the
Region Definition on the CICS command line.
Destination:
console.msg
ERZ048013W Transaction transId on terminal
termId made an unauthorized attempt
to load or release program
programName
Explanation:
The transaction transId is attempting to use the LOAD
PROGRAM or RELEASE PROGRAM call for map or
table programName. The transaction user does not
have the correct combination of RSL keys to perform
this operation.
394
System action:
The LOAD PROGRAM or RELEASE PROGRAM call is
rejected and an error condition raised. If a user
condition handler is defined then CICS passes control to
the handler. If no handler is defined then CICS
terminates the transaction abnormally.
User response:
Arrange for the transaction user to have RSL keys that
allow access to programName if this is required.
Destination:
console.msg
ERZ048014I Out of CICS region pool storage.
Explanation:
CICS cannot allocate any more storage from the region
pool. CICS is not able to satisfy requests for control
block storage.
System action:
CICS can begin to abend tasks due lack of region pool
storage. The region can possibly abnormally terminate.
User response:
If this is a persistent condition you need to reconfigure
the values for the region pool in the Region Definitions.
The TXSeries for Multiplatforms Administration
Reference provides guidance on region attributes.
Restart the region with new region pool values in the
Region Definitions or by overriding the Region
Definitions on the command line using the -a option of
the startsrc or cicsstartsrc command.
Destination:
console.msg
ERZ048015E A48A: Transaction transId on
terminal termId is out of CICS task
shared pool storage
Explanation:
CICS suspends transactions in a queue if no task
shared pool storage is available to satisfy a request.
The leading member of the queue is eventually timed
out waiting for storage. Transaction transId is the
current head of the wait queue and is abnormally
terminated because it cannot acquire task shared
storage.
System action:
User response:
Retry the transaction. If this is a persistent problem
affecting many transactions consider reconfiguring the
size of the task shared pool. The TXSeries for
guidance on region attributes. Restart the region with
new task shared pool values in the Region Definitions
or by overriding the Region Definitions on the command
line.
Destination:
ERZ048016E ERZ048022E
console.msg
ERZ048016E A48B: Unexpected failure in CICS
storage control for transaction transId
on terminal termId
Explanation:
CICS did not successfully allocate or free a control
block in the region pool. This indicates a software
problem in CICS.
System action:
CICS raises an abnormal termination condition on
transaction transId. A user abnormal termination
handler is invoked if defined. If no handler is defined
then CICS abnormally terminates the transaction.
User response:
Destination:
console.msg
ERZ048017E CICS self-consistency checking
detected one or more inconsistencies
Explanation:
The self-consistency checking has found one or more
inconsistencies in the control blocks and data areas
concerned with the task shared pool. The console.msg
log contains one or more messages, prior to this one,
indicating the nature of the inconsistencies.
System action:
CICS recovers from these inconsistencies and the
region continues. However, the inconsistencies were
caused by software overwriting areas in the task shared
pool and some transactions can possibly terminate
abnormally.
User response:
The other messages logged contain address
information. This information can be used to analyze
system or transaction dumps. Dump analysis can
possibly indicate which transactions or programs are
overwriting the task shared pool areas. A possible cause
is a program that uses GETMAIN SHARED to allocate
task shared storage. If these programs write data
buffers of a greater size than the area allocated by
GETMAIN then other task shared pool allocations can
be overwritten. Other inconsistencies can be caused by
using LOAD PROGRAM to load a BMS map or a table
into storage and writing into this area if an address was
returned in the SET option. If the problem persists
Destination:
console.msg
ERZ048020E CICS has overwritten the Region

Control Area (RCA) signature
Explanation:
CICS has overwritten the region storage management
area in the RCA. This management area is the anchor
point for the region pool data blocks that record
allocations in the region pool. This error is not
recoverable.
System action:
CICS raises an abnormal termination code U4801, and
abnormally terminates the region. (See message
ERZ4807E).
User response:
This type of inconsistency indicates a software problem
in CICS. Produce a system dump and send it to your
Destination:
console.msg
ERZ048021E CICS has overwritten the region pool
data block signature at address
address
Explanation:
CICS has overwritten the region pool data block at
address address. A pool data block records the details
of an allocation in the region pool. This error is not
recoverable.
System action:
ERZ4807E).
User response:
Destination:
console.msg
data block terminator signature at
address address
Explanation:
CICS has overwritten the region pool data block at
address address. A pool data block records the details
of an allocation in the region pool. This error is not
recoverable.
System action:
ERZ4807E).
User response:
395
ERZ048023E ERZ048027E
Destination:
console.msg
data block chain at address address.
Explanation:
CICS has broken the region pool data block chain at
address address stated in the message. This chain
records all allocations in the CICS region pool. This
error is not recoverable.
System action:
ERZ4807E).
User response:
Destination:
console.msg
ERZ048024E A region pool storage area has been
overwritten by a data overrun at
address address (User Area at:
userDataAddress, Region Pool Data
Block at: dataBlockAddress)
Explanation:
A region pool storage area allocated to a CICS internal
function has been overwritten by code writing beyond
the end of the allocation. Address address indicates
where the inconsistency was detected, address
userDataAddress is the start of the allocated storage
area and address dataBlockAddress is the region pool
data block that records the details of this allocation. This
error is not recoverable.
System action:
ERZ4807E).
User response:
Destination:
console.msg
ERZ048025E CICS region pool data block chain
shorter than expected (Expected:
expectedValue, Actual: actualValue).
Recovered - expected count set to
actual count
Explanation:
The chain of pool data blocks for the region pool had
fewer elements than the master count in the Region
Control Area (RCA). This indicates that a region pool
396
data block chain pointer has been overwritten.

Effectively some part of the region pool is no longer
accessible to CICS storage control. The error is not
severe enough to cause CICS to abnormally terminate
the region but some transactions can possibly start to
fail. The master count is reset to the number of blocks
actually found in the chain.
System action:
CICS resets the master count in the RCA and the
region continues.
User response:
in CICS. Contact your support organization.
Destination:
console.msg
ERZ048026E CICS has overwritten a task shared
pool data block signature at address
address
Explanation:
CICS has overwritten the task shared pool data block at
address address. This error is not recoverable.
System action:
ERZ4807E).
User response:
Destination:
console.msg
ERZ048027E A task shared pool storage area has
been overwritten by a data overrun at
userDataAddress, Task Shared Pool
Data Block at: dataBlockAddress) recovered
Explanation:
A task shared storage area has been overwritten by
code writing beyond the end of the allocation at address
address. The base address of the storage allocation is
at address userDataAddress and the control block
managing this area is at address dataBlockAddress.
This error is recoverable. However, some transactions
can possibly abnormally terminate due to this
inconsistency.
System action:
CICS resets the allocation termination signature so that
CICS can continue.
User response:
The information in this message can be used to analyze
system or transaction dumps. Dump analysis can
possibly indicate which transactions or programs are
ERZ048028E ERZ048032E
overwriting the task shared pool areas. A possible cause
is a program that uses GETMAIN SHARED to allocate
task shared storage. If these programs write data
buffers of a greater size than the area allocated by
returned in the SET option. If the problem persists
Destination:
console.msg
ERZ048028E CICS task shared pool data block
chain shorter than expected (Expected:
actual count
Explanation:
The chain of pool data blocks for the task shared pool
had fewer elements than the master count in the Region
Control Area (RCA). This indicates that a task shared
pool data block chain pointer has been overwritten.
Effectively some part of the task shared pool is no
longer accessible to CICS storage control. The error is
not severe enough to cause CICS to abnormally
terminate the region but some transactions can possibly
start to fail. The master count is reset to the number of
blocks actually found in the chain.
System action:
CICS resets the master count in the RCA and the
region continues.
User response:
Destination:
console.msg
ERZ048029E CICS has overwritten the LOAD
PROGRAM data block signature at
address address
Explanation:
CICS has overwritten the management structure
controlling a LOADed map or table at address address.
This error is not recoverable.
System action:
ERZ4807E).
User response:
Destination:
console.msg
ERZ048030E CICS has overwritten the LOAD

PROGRAM data block chain in Hash
Bucket bucketAddress, Address address
Explanation:
CICS has overwritten or broken the LOAD PROGRAM
management data chain in hash bucket bucketAddress
at address address. This error is not recoverable.
System action:
ERZ4807E).
User response:
Destination:
console.msg
ERZ048031E CICS self-consistency checking found
an inconsistency in BMS map
mapName at task shared storage
address address, managed by LOAD
PROGRAM data block at address
dataBlockAddress.
Explanation:
The physical map mapName has been overwritten in
some way and cannot be used.
System action:
CICS marks the map image as disabled. CICS
continues processing but some currently running
transactions can possibly abnormally terminate due to
this inconsistency. CICS raises a PGMIDERR condition
against any new transactions requesting the map.
User response:
Use CEMT SET PROGRAM(...) NEWCOPY ENABLED
to force a reload of the image at the first opportunity. A
transaction or system dump can be used to investigate
which transactions or programs are overwriting the task
shared storage containing the map. The likely cause is
that a program is writing data using an address returned
from a LOAD PROGRAM(mapName) SET(<pointer>)
call. Writing data to the address returned from this
LOAD PROGRAM call causes inconsistencies in the
map (or table storage) allocated for mapName.
Destination:
console.msg
ERZ048032E CICS LOAD PROGRAM data block
chain in Hash Bucket address was
shorter than expected (Expected:
actual count
Explanation:
397
ERZ048033E ERZ048036E
A chain of data blocks associated with maps and tables
had fewer elements than the master count in the
corresponding address hash bucket. This indicates that
data block chain pointer has been overwritten. This
effectively means that CICS does not have full access
to all loaded maps or tables in hash bucket address.
This inconsistency is not severe enough to cause CICS
to abnormally terminate the region. However, some
storage stress in the task shared pool can possibly
occur and consequently some transactions can possibly
be abnormally terminated.
System action:
CICS resets the master count in hash bucket address
and the region continues.
User response:
Destination:
console.msg
background task, made an invalid
attempt to free task shared storage at
address address
Explanation:
Transaction transId attempted to free task shared
storage at address address. The address is invalid as it
is not at the beginning of a task shared pool allocation.
The transaction was executing as a background ATI
task, or a back-end communications transaction (for
DTP, function shipping or transaction routing).
System action:
terminated CICS can possibly abnormally terminate the
region. If an abnormal termination is raised on an
application server a user defined abnormal termination
handler is executed if one is defined.
User response:
Check the use of the GETMAIN SHARED call and
subsequent FREEMAIN calls in transaction transId. If
shared storage is acquired by GETMAIN then, when it
is released, the storage address returned by GETMAIN
must be passed to FREEMAIN. Retry failed transactions
once they have been checked. If the condition persists
it can possibly indicate a software problem in CICS. In
this instance contact your support organization.
Destination:
console.msg
ERZ048034E CICS made an attempt to free task
shared storage at address address.
This address is invalid
Explanation:
398
CICS software attempted to free some task shared

is not at the beginning of a task shared pool allocation.
System action:
region.
User response:
This error indicates a software problem in CICS.
Destination:
console.msg
background task, made an attempt to
free region pool storage at address
address. This address is invalid
Explanation:
Transaction transId attempted to free some region pool
storage at address address. This address is invalid as it
is not the beginning of a storage area allocated from the
region pool. The transaction was executing as a
routing).
System action:
region.
User response:
Destination:
console.msg
ERZ048036E CICS made an attempt to free region
pool storage at address address. This
address is invalid
Explanation:
CICS software attempted to free some region pool
is not at the beginning of a region pool allocation.
System action:
region.
User response:
Destination:
console.msg
ERZ048037W ERZ048041E
ERZ048037W Transaction transId executing as a
background task, made an
unauthorized attempt to load or release
program programName
Explanation:
The transaction transId is attempting to use the LOAD
PROGRAM or RELEASE PROGRAM call for map or
table programName. The transaction user does not
have the correct combination of RSL keys to perform
this operation. The transaction was executing as a
routing).
System action:
The LOAD PROGRAM or RELEASE PROGRAM call is
rejected and an error condition raised. If a user
condition handler is defined then CICS passes control to
the handler. If no handler is defined then CICS
abnormally terminates the transaction.
User response:
Arrange for the transaction user to have RSL keys that
allow access to programName if this is required.
Destination:
console.msg
ERZ048038E A48A: Transaction transId executing
as a background task, is out of CICS
task shared storage.
Explanation:
CICS suspends transactions in a queue if no task
shared pool storage is available to satisfy a request.
The leading member of the queue is eventually timed
out waiting for storage. Transaction transId is the
current head of the wait queue and is abnormally
storage. The transaction was executing as a
routing).
System action:
User response:
Retry the transaction. If this is a persistent problem
affecting many transactions consider reconfiguring the
or by overriding the Region Definitions on the CICS
command line.
Destination:
console.msg
ERZ048039E A48A: A CICS control process is out

of CICS task shared storage.
Explanation:
CICS suspends processes or transactions in a queue if
no task shared pool storage is available to satisfy a
request. The leading member of the queue is eventually
timed out waiting for storage. A CICS control process is
the current head of the wait queue and is abnormally
storage.
System action:
CICS abnormally terminates the process. This can
possibly cause CICS to abnormally terminate the region.
User response:
If this is a persistent problem consider reconfiguring the
or by overriding the Region Definitions on the CICS
command line.
Destination:
console.msg
storage control for transaction transId,
executing as a background task.
Explanation:
problem in CICS. The transaction was executing as a
routing).
System action:
CICS raises an abnormal termination condition on
transaction transId. A user abnormal termination
handler is invoked if defined. If no handler is defined
then CICS abnormally terminates the transaction.
User response:
Destination:
console.msg
storage control.
Explanation:
problem in CICS.
System action:
CICS abnormally terminates the current process and
region.
399
ERZ048042I ERZ048047E
User response:
Destination:
console.msg
ERZ048042I Region Pool initialized at address:
poolAddress
Explanation:
The CICS Region Pool storage area has been
successfully initialized. The base address of the Region
Pool is poolAddress.
System action:
CICS initializes the Region Pool.
User response:
None
Destination:
console.msg
ERZ048043I Task Shared Pool initialized at
address: poolAddress
Explanation:
The CICS Task Shared storage area has been
successfully initialized. The base address of the Task
Shared Pool is poolAddress.
System action:
CICS initializes the Task Shared Pool.
User response:
None
Destination:
console.msg
ERZ048044I Task Shared Pool is under stress.
Purging unused map/table areas.
Explanation:
CICS breached the configured task shared pool storage
threshold or received a no storage condition from the
low level storage manager. CICS attempts to reclaim
storage in the Task Shared Pool so that storage
requests can be completed.
System action:
CICS removes any unused BMS maps or application
tables from the Task Shared Pool.
User response:
This message indicates that the Task Shared Pool is
possibly underconfigured for the needs of the region.
Shut down the CICS region and reconfigure the task
shared storage pool size (MaxTSHPool) and threshold
(TaskShPoolThreshold) attribute values in the Region
Definitions or by overriding the Region Definitions on
the CICS command line.
Destination:
400
console.msg
ERZ048045I Purging of unused map/table areas
completed. purgedCount maps/tables
purged.
Explanation:
CICS completed storage reclamation in the task shared
pool and removed purgedCount maps/tables from the
pool.
System action:
None
User response:
None
Destination:
console.msg
ERZ048046E A region pool storage area has been
overwritten by a data overrun at
userDataAddress, Region Pool Data
Block at: dataBlockAddress)
Explanation:
CICS has detected a storage inconsistency while
attempting to reallocate, or deallocate a region pool
storage area allocated to a CICS internal function. CICS
has determined that the storage area has been
overwritten by code writing beyond the end of the
allocation. Address address indicates where the
inconsistency was detected, address userDataAddress
is the start of the allocated storage area and address
dataBlockAddress is the region pool data block that
records the details of this allocation.
System action:
region. If an abnormal termination is raised on an
application server a user defined abnormal termination
handler is executed if one is defined.
User response:
Destination:
console.msg
ERZ048047E A task shared pool storage area has
been overwritten by a data overrun at
userDataAddress, Task Shared Pool
Data Block at: dataBlockAddress).
Explanation:
CICS has detected a storage inconsistency while
attempting to deallocate, or reallocate a task shared
storage area. CICS has determined that the storage
ERZ050001E ERZ050006W
area has been overwritten by code writing beyond the
end of the allocation at address address. The base
address of the storage allocation is at address
userDataAddress and the control block managing this
area is at address dataBlockAddress.
System action:
CICS continues, but does not release the inconsistent
storage, so that further analysis of the inconsistency can
be performed. Some transactions can possibly be
abnormally terminated as a result of this inconsistency.
User response:
The information in this message can be used to analyze
system, SNAP, or transaction dumps. Dump analysis
can possibly indicate which transactions or programs
are overwriting the task shared pool areas. A possible
cause is a program that uses GETMAIN SHARED to
allocate task shared storage. If these programs write
data buffers of a greater size than the area allocated by
returned in the SET option. As this storage cannot be
released, there is less storage available to both CICS
and your applications. This can ultimately result in
performance degradation that can only be rectified by
restarting your CICS region. If the problem persists
Destination:
console.msg
ERZ050001E CICS is unable to re-attach shared
memory.
Explanation:
CICS made an unsuccessful attempt to attach shared
memory. An earlier message possibly provides more
details.
System action:
User response:
Restart the region. If the problem recurs, restart the
region with Monitoring disabled. If the problem persists,
Destination:
CSMT
ERZ050002W CICS is unable to initialize the TCA
structure and therefore disables
Monitoring.
Explanation:
There was insufficient memory in the Task-Private Pool
to allocate the TCA structure for Monitoring.
System action:
CICS continues with Monitoring disabled for this task.
User response:
Retry the transaction. If the error occurs repeatedly,

increase the Task-Private Pool size or simplify the user
programs private memory usage. Also try running the
transaction with Monitoring disabled.
Destination:
CSMT
ERZ050003I CICS Monitoring successfully
initialized.
Explanation:
CICS has successfully completed the Monitoring
initialization.
System action:
CICS continues.
User response:
None
Destination:
console.msg
ERZ050004W Monitoring write was unsuccessful.
Explanation:
CICS was unable to write to the Performance
Monitoring Extra-partition Transient Data Queue. More
details are possibly provided by an earlier message.
System action:
CICS continues with Monitoring disabled for this task.
User response:
For further guidance in resolving the problem, refer to
any previous messages reporting the unsuccessful
result of the write. If the problem persists, contact your
Destination:
CSMT
ERZ050006W User Event Monitoring Point (EMP)
Initialization was unsuccessful with
User Load Module (ULM) response
code responseCode.
Explanation:
The User EMP CICS_EMP_Init function returned an
unsuccessful result and has requested that CICS
disable the User Load Module (ULM) for the remainder
of the task. The ULM response code associated with
the failure is responseCode.
System action:
The transaction continues with User Load Module
(ULM) disabled.
User response:
This message can be safely ignored. However you must
determine if this results from a failure either in the
transaction or in the ULM. If so correct the failure as
necessary. If the ULM needs correction it is necessary
to restart the region in order to use the replacement
401
ERZ050007W ERZ050011W
ULM. Run with Monitoring disabled until the problem is
corrected. See the TXSeries for Multiplatforms
Administration Reference for information about CICS
User Exits.
Destination:
CSMT
EnterAPI function was unsuccessful
with User Load Module (ULM)
response code responseCode.
Explanation:
The User EMP CICS_EMP_EnterAPI function returned
an unsuccessful result and requested that CICS disable
the User Load Module (ULM) for the remainder of the
task. The ULM response code associated with the
failure is responseCode.
System action:
The transaction continues with the User Load Module
(ULM) disabled.
User response:
ULM. See the TXSeries for Multiplatforms
User Exits.
Destination:
CSMT
WriteRecord function was
unsuccessful with User Load Module
(ULM) response code responseCode.
Explanation:
The User EMP CICS_EMP_WriteRecord function
returned an unsuccessful result, and has requested that
CICS disable the ULM for the remainder of the task.
The ULM response code associated with the failure is
responseCode.
System action:
(ULM) disabled.
User response:
User Exits.
Destination:
402
CSMT
ReStart function was unsuccessful
with User Load Module (ULM)
response code responseCode.
Explanation:
The User EMP CICS_EMP_ReStart function returned
an unsuccessful result, and has requested that CICS
disable the ULM for the remainder of the task. The ULM
response code associated with the failure is
responseCode.
System action:
(ULM) disabled.
User response:
User Exits.
Destination:
CSMT
ERZ050010W A User Event Monitoring Point (EMP)
function disabled Monitoring with User
Load Module (ULM) response code
responseCode.
Explanation:
One of the User EMP functions requested that CICS
disable Monitoring for the remainder of this task. The
ULM response code reported is responseCode.
System action:
The transaction continues with Monitoring disabled.
User response:
User Exits.
Destination:
CSMT
ERZ050011W Unknown group name groupName in
Monitoring Exclude/Include attribute.
Explanation:
CICS detected an unknown group name when parsing
the Include or Exclude attribute in the Monitor
Definitions (MD).
ERZ050012W ERZ050016I
System action:
CICS continues, ignoring this Monitor group ID.
System action:
CICS continues with Monitoring disabled for the region.
User response:
Correct the invalid entry in the Include or Exclude
attribute. See the TXSeries for Multiplatforms
Administration Reference for information about the
attributes and for a list of valid values.
User response:
Ensure that the queue specified by the TDQ attribute of
the Monitoring Definitions (MD) is correct. If not, correct
it and cold start the region. If it is correctly specified,
add the appropriate queue definition to the Transient
Data Definitions (TDD) and then cold start the region.
Reference for information about the TDQ attribute.
Destination:
CSMT
ERZ050012W Unknown field identifier fieldId in
Monitoring Exclude/Include attribute.
Destination:
CSMT
Explanation:
CICS detected an unknown field ID when parsing the
Include or Exclude attribute in the Monitor Definitions
(MD).
ERZ050015W TD Queue queueName is not an

extra-partition queue - CICS disables
Monitoring.
System action:
CICS continues, ignoring this Monitor field.
Explanation:
The specified TD queue to which monitoring records are
to be written is not an extra-partition queue.
User response:
Correct the invalid entry in the Include or Exclude
attribute. See the TXSeries for Multiplatforms
Administration Reference for information about the
attributes and for a list of valid values.
Destination:
CSMT
ERZ050013W Unable to load the User Event
Monitoring Point (EMP).
Explanation:
CICS made an unsuccessful attempt at loading the User
Event Monitoring Point (EMP).
System action:
CICS continues with User Event Monitoring disabled for
the Application Server.
User response:
Ensure that EMP module specified by the
UserMonitorModule attribute of the Monitoring
Definitions (MD), has been correctly specified, and that
CICS has permission to access it. Also ensure that the
module has been correctly compiled and linked. See the
information about the UserMonitorModule attribute.
Destination:
CSMT
ERZ050014W CICS cannot find the Monitoring TD
Queue queueName in Transient Data
Definitions (TDD).
Explanation:
CICS Monitoring was unable find the entry for the
queue specified by the TDQ attribute in the Monitoring
Definitions (MD), in the Transient Data Definitions
(TDD).
System action:
User response:
the Monitoring Definitions (MD) is correct. It must be an
extra-partition queue. If necessary, correct it and cold
start the region. If it is incorrectly specified, add the
appropriate queue definition to the Transient Data
Definitions (TDD) and then cold start the region. See
Destination:
CSMT
ERZ050016I The Monitoring Transient Data (TD)
queue has not been defined.
Explanation:
You have not specified the Transient Data (TD) queue
to which the CICS monitoring records are to be written.
Monitoring can still be enabled, but no attempt is made
by CICS to write the monitoring records to a TD queue.
System action:
CICS continues.
User response:
If you do not require monitoring records to be written to
a TD queue then do nothing. If you do require
monitoring records to be written to a TD queue, update
the TDQ attribute in the Monitoring Definitions (MD), so
that it specifies an appropriate Transient Data (TD)
queue name, then restart the region, specifying a COLD
start. See the TXSeries for Multiplatforms Administration
Destination:
CSMT
403
ERZ050017W ERZ050027W
ERZ050017W Cannot read system/user clock CICS disables Monitoring.
ERZ050024W CICS cannot read TD Queue On-Line

Database record queueName.
Explanation:
CICS is unable to obtain the system time information.
Explanation:
Earlier messages were possibly issued in connection
with this problem.
System action:
The transaction continues with Monitoring disabled for
the remainder of the task.
User response:
If Monitoring is required, try rerunning the transaction. If
Destination:
CSMT
ERZ050022W Unexpected return code: returnCode,
from Monitoring User Load Module
(ULM) function functionName. Error
code: errorCode.
Explanation:
The Monitoring ULM function returned an unsuccessful
result and has requested that CICS disable User
Monitoring for the remainder of the task.
System action:
CICS continues with User Monitoring disabled for the
task.
User response:
This message can be safely ignored. However,
determine the cause of the failure in the ULM and
correct the failure as necessary. If you make changes to
the ULM you need to restart the region in order to use
the replacement ULM. If the ULM needs to be
corrected, the region possibly needs to be restarted,
using the replacement ULM. See the TXSeries for
Multiplatforms Administration Reference for information
about CICS User Exits.
Destination:
CSMT
ERZ050023W CICS cannot read MD Permanent
Database record.
Explanation:
CICS was unable to obtain the Monitoring definitions
from the MD Permanent Database.
System action:
CICS continues with Monitoring disabled for this region.
User response:
Ensure Monitoring definitions exist and are correct. If
not, correct and restart the region, specifying cold start.
Destination:
CSMT
404
System action:
User response:
For further guidance in resolving the problem, refer to
any previous messages reporting the unsuccessful
result. If the problem persists, contact your support
organization.
Destination:
CSMT
ERZ050025W CICS cannot allocate memory for
Monitoring TD Queue record.
Explanation:
There is insufficient memory in the Task-Private Pool for
the Monitoring TD Queue record.
System action:
CICS continues with Monitoring disabled for the task.
User response:
Restart the region. If problem persists, reduce
transaction memory usage or increase the Task-Private
Pool and once again restart the region.
Destination:
CSMT
ERZ050027W TD Queue queueName is not an
output queue - CICS disables
Monitoring.
Explanation:
to be written is not an output queue.
System action:
User response:
the Monitoring Definitions (MD) is a correct output
queue. If not, correct it and cold start the region. If it is
correctly specified, add the appropriate queue definition
to the Transient Data Definitions (TDD) and then cold
start the region. See the TXSeries for Multiplatforms
Administration Reference for information about the TDQ
attribute.
Destination:
CSMT
ERZ050028W ERZ051002E
ERZ050028W TD Queue queueName does not
have variable length records - CICS
disables Monitoring.
Explanation:
to be written is not defined to have variable length
records.
System action:
User response:
the Monitoring Definitions (MD) has variable length
records. If not, correct it and cold start the region. If it is
correctly specified, add the appropriate queue definition
to the Transient Data Definitions (TDD) and then cold
start the region. See the TXSeries for Multiplatforms
attribute.
Destination:
CSMT
ERZ050029W TD Queue record size too big
recordSize - CICS disables User
Monitoring.
Explanation:
The specified TD queue record size (system plus user)
is greater than allowed (USHRT_MAX).
System action:
region.
User response:
Reduce the amount of user data written by the User
Load Module (ULM) or reduce the number of system
fields reported.
Destination:
CSMT
ERZ050030E CICS is unable to release monitoring
record storage in the Task-Private
Pool.
Explanation:
CICS was unable to release the storage used to hold
the monitoring record.
System action:
CICS terminates the task abnormally.
User response:
It is likely that the transaction has caused a data
inconsistency in the Task-Private Pool. Check the User
Event Monitoring Point (EMP) and, if necessary, correct
the User Event Monitoring Point (EMP) function. In
order to use the replacement ULM, you need to restart
the region.
CSMT
ERZ050031W
TD Queue queueName does not

have MaxSize set to 0. - CICS disables
User Monitoring.
Explanation:
to be written does not have MaxSize value 0.
System action:
region.
User response:
the Monitoring Definitions (MD) has MaxSize set to 0.
Correct it and cold start the region. If it is correctly
specified, add the appropriate queue definition to the
Transient Data Definitions (TDD) and then cold start the
region. See the TXSeries for Multiplatforms
attribute.
Destination:
CSMT
statistics information.
Explanation:
CICS was attempting to obtain memory for statistics
information from the Task-Private Pool. Insufficient
System action:
After further processing the transaction abnormally
terminates.
User response:
Reduce the quantity of GETMAIN storage used by your
transaction. If the problem persists, contact your support
organization.
Destination:
CSMT
ERZ051002E Unable to write to the statistics file
fileName.
Explanation:
CICS made an unsuccessful attempt to write to the
statistics file fileName.
System action:
User response:
As a result of this error the statistics file can possibly
contain inconsistent data. Remove the file before
generating another statistics collection. Also ensure that
Destination:
405
ERZ051004E ERZ052007I
there is sufficient space available on the filesystem to
write the statistics data. If the problem persists, contact
Destination:
CSMT
ERZ051004E Unable to initialize the statistics file.
Explanation:
CICS was unable to initialize the statistics file, because
it was unable to be opened.
System action:
User response:
Ensure that the directory in which the statistics file is
situated exists. Also ensure that CICS has permission to
write to the statistics file. If the problem exists, contact
console.msg
ERZ052003W Unable to use all the dump directory
names due to lack of memory.
Explanation:
Either there are more sub-directories than CICS can
support, or the sub-directory names are too long to
include all the sub-directories as possible sites for dump
files.
System action:
CICS ignores some sub-directories.
User response:
Shorten the dump sub-directory names to attempt to
include them as possible sites for dump files.
Alternatively, reduce the number of dump directories.
Destination:
console.msg
Destination:
console.msg
ERZ052004I Dump to dumpsetName started.
ERZ051005E Unable to open the statistics file

fileName.
Explanation:
A dump was requested, and CICS is creating a dump
by the given name.
Explanation:
CICS made an unsuccessful attempt to open the
statistics file fileName.
System action:
The statistics collection is not made. The transaction
User response:
Ensure that the directory in which the statistics file is
situated exists. Also ensure that CICS has permission to
write to the statistics file. If the problem exists, contact
System action:
CICS creates the named dump, and generates
message ERZ5207I on successful completion of the
dump.
User response:
Check the dump. For information, please see the
Destination:
console.msg
ERZ052006I Shutdown Dump in progress.
Destination:
CSMT
Explanation:
A shutdown command has been issued and the region
is configured to produce a dump on shutdown.
ERZ052001I Dump Sequence Number reset.
System action:
CICS produces a dump and terminates the region.
Explanation:
CICS has reset the Dump Sequence Number to zero.
CICS uses this number to name dump files. Therefore
CICS can possibly overwrite files already in the dump
sub-directories, whose names are of the form
XXXX0001 and YYYY0002, for example.
System action:
User response:
Destination:
console.msg
ERZ052007I Dump to dumpsetName completed.
User response:
Copy the dump directory, sub-directories, and contents
to another directory. This ensures that CICS does not
overwrite dump files already existing in the
sub-directories.
Explanation:
CICS has created the specified dump.
Destination:
User response:
406
System action:
ERZ052008W ERZ052016W
Destination:
console.msg
ERZ052008W Out of space for dump file in
directory directoryName.
Explanation:
When writing to the specified directory, CICS detected
an out of disk space status.
System action:
CICS continues producing the dump with a new file and
directory.
User response:
Check the disk space available in the specified directory
and, if necessary, create some more space.
Destination:
console.msg
ERZ052011W Unable to access dump directory
entry entryName.
Explanation:
The specified dump sub-directory does not exist or is
not a directory.
System action:
CICS attempts to use the next available dump directory.
It ignores the sub-directory until the sub-directory is
accessible.
User response:
Change the access permissions and type of the dump
directory entry, if it exists. If the entry does not exist,
create it with the required access permissions.
ERZ052013I Dump dumpNumber - dumpCount core

dump(s) created.
Explanation:
CICS displays the number of core dumps produced for
a dump.
System action:
User response:
Destination:
console.msg
ERZ052014W Dump dumpNamedumpNumber :
Attempt no. attemptNumber failed to
create a core dump, error errorCode
Explanation:
CICS failed to create the specified core dump on the
numbered attempt.
System action:
User response:
Check the core dump sub-directory as specified by the
value of the CoreDumpName attribute in the Region
Definition. Check the availability of the core dump
sub-directory. If the sub-directory does not exist, create
it with read, write and execute permissions for user
cics. Further information can be obtained from the error
number supplied.
Destination:
console.msg
Destination:
console.msg
ERZ052015W Dump directory directoryName has

invalid permissions; expecting
permissions.
ERZ052012W Unsuccessful attempt to access core

dump sub-directory directoryName.
Explanation:
An entry under the dump directory is a directory but has
incorrect permissions.
Explanation:
The core dump sub-directory does not exist or is not a
directory.
System action:
CICS ignores the dump sub-directory.
System action:
CICS disables core dumps until the core dump
sub-directory is accessible.
User response:
Correct the access permissions on the dump
sub-directory.
User response:
Check the core dump sub-directory as specified by the
value of the CoreDumpName attribute in the Region
Definition. Check the availability of the core dump
sub-directory. If the sub-directory does not exist, create
it with read, write and execute permissions for user
cics.
Destination:
console.msg
Destination:
console.msg
ERZ052016W Unexpected error code (errorCode)

when attempting to access dump
directory directoryName.
Explanation:
CICS detected an unexpected access error.
407
ERZ052017W ERZ052023E
System action:
CICS ignores the dump sub-directory.
User response:
organization.
Destination:
console.msg
ERZ052017W Disk quota limit reached in directory
directoryName.
Explanation:
When writing to the specified directory, CICS reached
the disk space quota limit.
System action:
CICS continues to produce the dump with a new file.
User response:
Check the disk space quota allocation. If possible,
create a new directory. Otherwise, delete something
from the directory.
Destination:
console.msg
ERZ052018E Cannot access region dump directory
or sub-directory directoryName.
Explanation:
The dump directory specified in the DumpName
attribute of the Region Definitions (RD) is in error; or no
sub-directories exist in the region dump directory.
System action:
CICS disables all dumps.
User response:
Ensure the dump directory exists and that it has the
correct permissions. Also ensure that any dump
directory created contains subdirectories into which the
dumps can be placed. CICS uses the sub-directories,
under the dump directory, in collating sequence. Ensure
the subdirectories have read, write and execute
permission for user cics.
Destination:
console.msg
ERZ052020E Unable to access region dump
directory directoryName - system error
errorCode. Unable to produce dump
output
Explanation:
CICS cannot access the region dump directory.
System action:
User response:
Check the cause of this error. Ensure the dump
directory exists and that it has the correct permissions.
408
Also ensure that any dump directory created contains

subdirectories into which the dumps can be placed. In a
similar manner to the root dump directory ensure the
subdirectories have read, write and execute permission
for user cics.
Destination:
console.msg
ERZ052021E CICS is unable to provide a dump due
to insufficient system capability
Explanation:
A dump has been requested but the system is not
sufficiently initialized to perform a formatted dump.
System action:
CICS terminates the region.
User response:
Check the previous system messages. If you cannot
solve the problem, contact your support organization.
Destination:
console.msg
ERZ052022E Abnormal termination AKCS; unable
to close the dump file due to a
transient error.
Explanation:
CICS has timed out while attempting to close the dump
file after a dump.
System action:
terminates the transaction with abend code AKCS in
order to avoid a potential deadlock situation.
User response:
Check the availability of the dump directory. If the
problem occurs repeatedly contact your support
organization.
Destination:
console.msg
ERZ052023E Unable to write data to the dump file.
Explanation:
CICS has detected an error while attempting to write to
the dump file.
System action:
CICS does not perform write the data to the dump file.
The dump continues.
User response:
Check the availability of the dump directory. If the
problem occurs repeatedly contact your support
organization.
Destination:
console.msg
ERZ052024E ERZ053001W
ERZ052024E Unable to perform dump of area
areaId, exception exceptionName
caught.
Explanation:
Part of the system dump was unable to be performed
because of inconsistency in CICS internal data.
System action:
The dump continues.
User response:
Check next CICS internal consistency check for
possible indications of the problem. Contact your
Destination:
console.msg
ERZ052025I Dumping initialized with these options
set to YES dumpOptions.
Explanation:
Dump support has been initialized. Any dump options
which were set to YES in the Region Definitions (RD)
are listed.
System action:
Startup continues.
User response:
None
Destination:
console.msg
ERZ052026E Unable to perform full dump of
internal toolkit data, exception
exceptionName caught.
Explanation:
Part of the system dump was unable to be performed
because of inconsistency in CICS Toolkit internal data.
System action:
The dump continues.
User response:
Check any CICS Toolkit data which was dumped and
check the results of the next CICS internal consistency
check for possible indications of the problem. Contact
Destination:
console.msg
ERZ052027I Length of data dumped truncated to
INFDU_MAX_FLENGTH.
Explanation:
A request to dump data specified a length greater than
the maximum; the length of data dumped is truncated to
the maximum.
System action:
The dump continues.

User response:
If you require to dump greater than the maximum length
of data then this must be done in separate dump
requests each specifying a length not greater than the
maximum.
Destination:
CSMT
ERZ052028W Storage not allocated for parameter
lists - user exit 17 (UE052017).
Explanation:
Either a dump was requested during very early task
initialization, before storage allocated for the header
parameter list or a request to obtain storage in which to
build a specific parameter list for user exit 17
(UE052017) failed.
System action:
The dump continues as if user exit 17 (UE052017) is
inactive.
User response:
Take a SNAP dump and investigate storage usage in
the CICS region; consider increasing the amounts of
storage available to CICS via region definition
parameters.
Destination:
CSMT
ERZ052029E CICS is unable to suspend a process
during a dump due to insufficient
storage
Explanation:
During a system dump, an active process has been
requested to wait until the dump has finished. However,
there is not enough storage available in the region
storage pool to do this.
System action:
User response:
Increase the Region Definition value MaxRegionPool
and restart the region.
Destination:
console.msg
ERZ053001W Unable to cancel the CICS-private
transaction responsible for automatic
statistics collection
Explanation:
CICS encountered a problem when processing your
command to reschedule the automatic statistics
collection facility. More details are possibly provided by
an earlier message.
System action:
409
ERZ053002I ERZ053006E
Processing of your command continues.
User response:
Refer to the associated message for guidance on
Destination:
console.msg
ERZ053002I CICS statistics initialization is
complete. Interval recording is active,
for an interval of intervalHours hours,
intervalMinutes minutes and
intervalSeconds seconds. The
end-of-day time is set to EODhours
hours, EODminutes minutes and
EODseconds seconds.
Explanation:
CICS has initialized the automatic statistics collection
facility. Statistics are recorded and then reset at the end
of each interval. The interval duration is intervalHours,
intervalMinutes and intervalSeconds. The final collection
of the day (end-of-day) are made EODhours,
EODminutes and EODseconds after midnight.
System action:
CICS initialization continues.
User response:
None
Destination:
console.msg
ERZ053003I CICS statistics initialization is
complete. The interval duration is set
to intervalHours hours, intervalMinutes
minutes and intervalSeconds seconds,
with interval recording inactive. The
end-of-day time is set to EODhours
EODseconds seconds.
Explanation:
CICS has initialized the automatic statistics collection
facility. Statistics are be recorded at the end of each
interval. If interval recording is activated, the interval
duration is be intervalHours, intervalMinutes and
intervalSeconds. The final collection of the day
(end-of-day) is made EODhours, EODminutes and
EODseconds after midnight.
System action:
User response:
None
Destination:
console.msg
410
ERZ053004I Statistics interval set to intervalHours

hours, intervalMinutes minutes and
intervalSeconds seconds
Explanation:
CICS has successfully processed your request to alter
the statistics interval duration. Statistics are now be
recorded using an interval of intervalHours,
intervalMinutes and intervalSeconds, provided interval
recording is active.
System action:
The transaction continues.
User response:
None
Destination:
console.msg
ERZ053005I Statistics end-of-day set to EODhours
EODseconds seconds
Explanation:
CICS has successfully processed your request to alter
the time at which the final statistics collection of the day
(end-of-day) is made. The end-of-day collection is now
made at EODhours, EODminutes and EODseconds
after midnight.
System action:
User response:
None
Destination:
console.msg
ERZ053006E Unsolicited statistics could not be
collected
Explanation:
Statistics for a resource about to be deleted (unsolicited
statistics) were unable to be collected due to an error
while collecting the statistics. More details are possibly
provided by an earlier message.
System action:
CICS has not written the statistics. The region continues
but is possibly unable to process any further requests to
collect statistics, until the problem has been resolved.
User response:
Destination:
CSMT
ERZ053007W ERZ053012E
ERZ053007W The request to schedule automatic
statistics collection was unsuccessful
Explanation:
CICS encountered a problem when processing your
command to reschedule the automatic statistics
collection facility. This was due to an unsuccessful
request to asynchronously start the CICS-private
transaction responsible for the automatic collection of
statistics. More details are possibly provided by an
earlier message.
System action:
The region continues, but automatic statistics collections
is not made until the facility is reactivated.
User response:
resolving the problem. Once the problem has been
resolved, you can reactivate the automatic statistics
collection facility by altering the next collection time,
using the SET STATISTICS command.
Destination:
console.msg
ERZ053008E The end-of-day statistics could not be
collected
Explanation:
CICS was unable to make the final statistics collection
of the day (end-of-day) due to an error when collecting
the statistics. More details are possibly provided by an
earlier message.
System action:
collect statistics until the problem has been resolved.
User response:
Destination:
CSMT
ERZ053009E Interval statistics could not be
collected
Explanation:
CICS was unable to make an interval statistics
collection, due to an error when collecting the statistics.
More details are possibly provided by an earlier
message.
System action:
User response:
Destination:
CSMT
ERZ053010E Unable to save configuration to the
restart file
Explanation:
CICS was unable to save the statistics restart
configuration to the region restart file. More details are
possibly provided by an earlier message.
System action:
User response:
Remove the CICS restart file and restart the region,
specifying a COLD start. Refer to the associated
message for further guidance on resolving the problem.
organization.
Destination:
console.msg
ERZ053011E Request statistics could not be
collected
Explanation:
CICS was unable to process your request to perform a
statistics collection, due to an error when collecting the
statistics. More details are possibly provided by an
earlier message.
System action:
User response:
Destination:
CSMT
ERZ053012E Unable to obtain AUTO start
information, defaulting to a COLD start
for statistics initialization
Explanation:
CICS was unable to obtain the statistics configuration
information from the restart file. Statistics are initialized
as per a COLD start. More details are possibly provided
by an earlier message.
System action:
User response:
Destination:
console.msg
411
ERZ053013I ERZ054003E
ERZ053013I Statistics interval recording has been
activated
Explanation:
CICS has successfully processed your request to
activate statistics interval recording. Statistics are now
recorded at the end of each interval.
System action:
User response:
None
Destination:
console.msg
ERZ053014I Statistics interval recording has been
deactivated
Explanation:
CICS has successfully processed your request to stop
statistics interval recording. Statistics are no longer be
recorded at the end of each interval, until interval
recording is reactivated.
System action:
User response:
None
Destination:
console.msg
Explanation:
The CICS automatic statistics collection facility was not
active. This is possibly due to a problem earlier in the
region. CICS is restarting the facility.
System action:
The automatic collection of statistics is restarted. The
region continues.
User response:
None
Destination:
console.msg
Usage: cicsdfmt [ [[ -r regionName ] [
fileName ]] | directoryName | fileName |
[ -p [ -r regionName ] [ dumpFileName
]] ] | -?
Explanation:
Invalid arguments were given to cicsdfmt. Valid
arguments are
-r regionName
specifies the region to use
412
directoryName
lists dump files in directoryName
-p
purge all the dump files
-p dumpFileName
purge the specified dumpFileName dump files
System action:
None
User response:
Check the syntax supplied to cicsdfmt and retry the
command. See the TXSeries for Multiplatforms
Administration Reference for more information about
cicsdfmt.
Destination:
stderr
ERZ054002E Invalid region regionName
Explanation:
The region name given is not known to CICS.
System action:
None
User response:
Correct region name and retry the command.
Destination:
stderr
ERZ053015I Re-starting the automatic statistics

collection facility
ERZ054001E
fileName
names a particular file to format
ERZ054003E Invalid dump file fileName - enter

cicsdfmt -r regionName to list valid
dump files
Explanation:
cicsdfmt cannot find a dump file named fileName to be
formatted. The name of the dump file must be specified
without the suffix .dmpnn. cicsdfmt has searched
either the specified regions dump directory, or the
current directory and the parent of the current directory
and the default regions directory.
System action:
None
User response:
Check that you have specified a valid dump file name
without the suffix. Enter the command cicsdfmt -r
regionName to list the valid dump files. Retry the
command specifying the name of a valid dump file. See
Reference for more information about cicsdfmt.
Destination:
stderr
ERZ054004E ERZ054011E
ERZ054004E No dump files found in directory
directoryName
Explanation:
The directory directoryName contains no dump files.
System action:
None
User response:
Ensure that the directory supplied was indeed the
directory where the dumps were written and if, this is
correct, contact the system administrator to determine
the current destination of dump files.
Destination:
stderr
ERZ054005E Error while reading dump file
fileName
stderr
ERZ054008E Problem encountered with
programName executable
Explanation:
A program that has been called has failed.
System action:
None
User response:
Ensure the executable exists, check the path that is
used to access the required executable, and check that
there is enough space on the filesystem. Examine error
output to see if a previous error occurred. This possibly
indicates a CICS internal error.
Destination:
stderr
Explanation:
An error has occurred while formatting the named dump
file.
ERZ054009E Unable to read the dump format

template file, templateFile
System action:
None
Explanation:
The dump formatting program has been unable to read
the dump format template file.
User response:
Since one of the dump files being processed was found
to be in error, reproduce the dump or obtain assistance
to determine the nature of the error and attempt
possible correction.
Destination:
stderr
ERZ054006I The following files are available for
formatting:
Explanation:
A list of dump files which can be formatted follows this
message.
System action:
None
User response:
Ensure the dump formatting template has been installed
and has read permission.
Destination:
stderr
ERZ054010I Do you really want to remove the
dump files?
Explanation:
Asks you if you want to remove the dump files.
System action:
None
System action:
None
User response:
None
User response:
Enter either yes or no.
Destination:
stderr
Destination:
stderr
ERZ054007E No region name given
ERZ054011E File fileName in the path name does

not exist
Explanation:
You have entered the -r option without specifying a
region name.
System action:
None
User response:
Correct the command line arguments and retry.
Destination:
Explanation:
cicsdfmt cannot find the dump file named fileName to
be removed. cicsdfmt has either searched the specified
regions dump directory, or the current directory and the
parent of the current directory and the default regions
directory.
System action:
None
413
ERZ054012E ERZ054018E
User response:
Check for valid file names and retry the command.
ERZ054015E Directory dirName not found
Destination:
stderr
Explanation:
cicsdtmt tried to access dump directory dirName but
was unable to.
ERZ054012E Unable to find a default region
System action:
Explanation:
cicsdfmt encountered a problem while obtaining the
name of the default region.
System action:
cicsdfmt terminates with a non-zero status.
User response:
Ensure that the default region is set up correctly with
the right access permissions. The default region is the
name in the environment variable CICSREGION. If you
prefer to use a region other than the default, run
cicsdfmt again specifying the region name using the -r
option.
Destination:
stderr
Explanation:
cicsdfmt encountered a problem while obtaining
information about the CICS system installed on your
machine.
System action:
cicsdfmt terminates with a non-zero status.
User response:
Destination:
stderr
ERZ054014E Entry databaseEntry not found for
permanent database class
databaseName.
Explanation:
cicsdtmt tried to read a record from the
databaseName. stanza file, looking for resource
databaseEntry, but failed to do so.
User response:
Check that the directory exists and is readable. Check
that you have installed your cics region correctly.
Destination:
stderr
Explanation:
cicsdfmt tried to access some memory for its own
System action:
User response:
Destination:
stderr
ERZ054017E Unable to remove file fileName, error
errno
Explanation:
cicsdfmt tried to remove file fileName but was unable
to do so.
System action:
The command continues, but does not remove the file.
User response:
Check you have the necessary permissions to remove
the file. Check the value of errno for more information.
Destination:
stderr
System action:

User response:
Check that the stanza file exists, and has the correct
permissions to enable cics to read from it. Check that
this file has not been corrupted.
Explanation:
Destination:
stderr
System action:
error status.
User response:
Destination:
stderr
414
ERZ054019E ERZ055005E
ERZ054019E No dump files found in directories
under directoryName
Explanation:
The directory directoryName contains no dump files.
System action:
None
User response:
Ensure that the directory supplied was indeed the
directory where the dumps were written and if, this is
correct, contact the system administrator to determine
the current destination of dump files.
Destination:
stderr
ERZ054020E Problem using region regionName
Explanation:
CICS encountered a problem accessing details about
region regionName.
System action:
The command terminates with an abnormal return code.
User response:
Ensure that the region exists and is properly configured.
If it does, ensure that you have installed CICS correctly.
Destination:
stderr
ERZ055001E Usage: cicssfmt [[-c
categoryName[,..]] [-s startTime] [-e
endTime] [-l pageLength] [-w
pageWidth] [-h] [-i] fileName1
fileName2 ...] | [-?]
Explanation:
Your command specified the -? parameter or contained
incorrect syntax.
System action:
The sample application cicssfmt terminates.
User response:
Retry the command using the correct syntax, as shown
in the message.
Destination:
stderr
ERZ055002E The sample application cicssfmt
detected an unsuccessful open/close
of the statistics file fileName.
Explanation:
The sample application cicssfmt was unable to open or
close the file you requested cicssfmt to process.
Check the name of the file and the permissions and

retry the command.
Destination:
stderr
detected an unsuccessful read attempt
for the statistics file fileName.
Explanation:
The sample application cicssfmt detected a read error
for the file you requested for processing.
System action:
The sample application cicssfmt abnormally terminates.
User response:
Check the name of the file and whether CICS reported
any errors when writing to this file. If the name is
incorrect, retry the command with the correct file name.
Destination:
stderr
unexpectedly detected End Of File
(EOF) for statistics file fileName.
Explanation:
The file you requested cicssfmt to process terminated
abnormally.
System action:
User response:
Ensure that the file fileName, is a valid CICS statistics
file. Examine the CICS message logs to determine
whether CICS reported any errors when generating this
file,
Destination:
stderr
ERZ055005E End time (-e option) is earlier than
start time (-s option).
Explanation:
Your specified end time is earlier than your specified
start time. The end time must be later than the start
time.
System action:
User response:
Retry the command specifying valid start and end times.
Destination:
stderr
System action:
User response:
415
ERZ055006E ERZ055013E
ERZ055006E Unknown category type
categoryName specified for -c flag.
Destination:
stderr
Explanation:
The category that you have specified is not supported
by cicssfmt.
ERZ055010E Unsuccessful memory allocation

detected.
System action:
Explanation:
Insufficient memory was available when cicssfmt tried to
perform a malloc call.
User response:
Retry the command specifying a supported category
type.
System action:
Destination:
stderr
ERZ055007E You specified an invalid pagelength
for the -l option.
Explanation:
Your specified page length is invalid. You must specify a
positive number for the page length.
User response:
Check available memory space. Try ending
unnecessary sessions to release memory, or install
additional memory. If the problem persists contact your
Destination:
stderr
System action:
ERZ055011E The sample application cicssfmt does

not produce Summary Statistics for
categoryName category.
User response:
Retry the command specifying a positive number for
page length.
Explanation:
You selected the option for a Summary Report and also
the categoryName category. These are not compatible.
Destination:
stderr
System action:
ERZ055008E You specified an invalid pagewidth for

the -w option.
Explanation:
Your specified page width is invalid. You must specify a
positive number (50 or greater) for the page width.
System action:
User response:
Retry the command specifying a positive number (50 or
greater) for page width.
Destination:
stderr
ERZ055009E You incorrectly specified the time
format for the -s or -e option. It must
be expressed as yymmddhhmmss.
User response:
Retry the command specifying a valid category.
Destination:
stderr
ERZ055012W The sample application cicssfmt is
unable to find the record within the
period specified by the
starttime/endtime in file fileName.
Explanation:
The sample application cicssfmt was unable to find the
record within the specified period in the statistics file.
System action:
The sample application cicssfmt formats the entire
statistics file.
User response:
None.
Explanation:
Your specified time is not of the correct format. You
must specify the time in the format yymmddhhmmss.
Destination:
stderr
System action:
ERZ055013E You have not specified any files to be

formatted.
User response:
Retry the command specifying time in the format
yymmddhhmmss.
Explanation:
You must specify at least one filename.
416
System action:
ERZ055014E ERZ056005E
User response:
Retry the command specifying at least one statistics file
name.
Destination:
stderr
ERZ055014E The pagewidth is insufficient to
display the statistics data.
Explanation:
The page width that you specified was too small for the
sample application cicssfmt to display the statistics data.
System action:
User response:
Retry you request, specifying a larger page width, via
the -w option.
Destination:
stderr
ERZ055015W The statistics file fileName is empty.
Explanation:
The file you requested cicssfmt to process was empty.
System action:
The sample application cicssfmt continues.
User response:
Ensure that the file fileName, is a valid CICS statistics
file. Also ensure that a CICS statistics collection was
made and written to the statistics file fileName. If so,
examine the CICS message logs to determine whether
CICS reported any errors when generating this file,
The system administrator needs to investigate the

disappearance of the sleeping process. Other error
messages preceding or following this message possibly
give information about a process death.
Note that other than for some forcepurge and abnormal
application server termination conditions, the death of
the process is not supposed to be caused by CICS itself
as the process is supposed to be sleeping on the
condition. It was possibly killed by a user from the
command line, by a users application program, or by an
erroneous transaction program.
Destination:
console.msg
ERZ056002E Unexpected signal signalNumber
caught
Explanation:
Another process or user sent a signal that this process
did not expect.
System action:
The process takes the system default action (core
dump).
User response:
Determine why the signal is being sent; it was possibly
sent by a user from the command line.
Destination:
stderr
ERZ056003E Unsuccessful attempt to allocate
storage to perform a wait on a
condition
Destination:
stderr
Explanation:
Insufficient storage was available when allocating
Region-Pool memory used to queue a process that is
attempting to wait on a condition.
ERZ056001E CICS condition variable wakeup list

specifies a non-existent process
System action:
The waiting process is abnormally terminated with code
A561.
Explanation:
The list of sleeping process identifiers associated with a
given condition variable includes the identifier of a
process that is no longer in existence. This is an error
because the process does not normally disappear while
it is sleeping waiting on the condition.
System action:
If a single process wakeup is being performed the
process identifier in question is removed from the list of
sleeping process identifiers and a new process is
chosen for wakeup. If a multiple process wakeup is
being performed then the process identifier is discarded
and wakeup of the remaining sleeping processes
continues.
User response:
User response:
The error arises because CICS has run out of available
Region-Pool storage. Have the system administrator
investigate reconfiguring the system to make more
memory available.
Destination:
console.msg
actualSignature at address
signatureAddress
Explanation:
417
ERZ056006E ERZ056014E
signature actualSignature is inconsistent with that
expected expectedSignature
System action:
Self-consistency checking continues.
User response:
inconsistencies, then this is an internal software error;
Destination:
console.msg
detected an inconsistency in an unique
identity pools state: maximum pool
size poolSize, high water mark
highWaterMark, take index takeIndex
Explanation:
When performing self-consistency checking CICS
detected that internal management data on the state of
a unique identity pool has become corrupt.
highWaterMark cannot be greater than poolSize and
takeIndex cannot be greater than highWaterMark.
System action:
User response:
Destination:
console.msg
identity pools state: pool table pointer
is NULL
Explanation:
an unique identity pool has become corrupt. The pointer
to the table containing the unique identity states cannot
be NULL.
System action:
User response:
Destination:
console.msg
418

identity pools state: Id poolId is in use,
but high water mark is highWaterMark
Explanation:
an unique identity pool has become corrupt. Ids greater
than or equal to highWaterMark cannot be in use yet.
System action:
User response:
Destination:
console.msg
ERZ056012E Unsuccessful attempt at getting
system hostname
Explanation:
An unsuccessful attempt was made to get the name of
the host system using the uname command.
System action:
Processing continues; however, further messages can
be generated as a result of this error.
User response:
As this problem indicates a problem within CICS it is
extremely important that you save all diagnostic
information and contact your support organization.
Destination:
CSMT, stderr
ERZ056014E A CICS internal buffer has overflowed
Explanation:
An internal buffer used to expand strings has
overflowed.
System action:
Processing continues; however, other messages can be
generated as a result of this error.
User response:
As this problem indicates a problem within CICS it is
extremely important that you save all diagnostic
information and contact your support organization.
Destination:
CSMT, stderr
ERZ056015E ERZ056056E
ERZ056015E Default region name is too long
Explanation:
When trying to determine a working region name, if one
was not explicitly selected, the default region name was
found to be too long. All region names must be made
up of 8 or less characters.
System action:
No working region is determined.
User response:
Either select a correct working CICS region name or
establish a new working region name by updating the
environment variable CICSREGION.
Destination:
stderr
ERZ056016E Default region not found
Explanation:
When trying to determine a working region name, no
region directory was found.
System action:
No working region is determined.
User response:
Either select a correct working CICS region name,
create a new region, or update the environment variable
CICSREGION so that a default region exists with the
correct access permissions.
Destination:
stderr
ERZ056017E Unable to access default region
Explanation:
The access permissions on the default region directory
are such that you do not have sufficient authority to use
the region.
System action:
The selected command does not execute.
User response:
If the default region is a valid working region, check that
the directory for the default one has the required
permissions. Ensure that it is owned by user cics and
has read, write, and execute permissions for its owner.
Otherwise, either select a correct working CICS region
name or establish a new working region name by
updating the environment variable CICSREGION.
Destination:
stderr
ERZ056018E Unexpected error while obtaining
default region name
Explanation:
There was a CICS internal error.
System action:
The selected command does not execute.
User response:
As this problem indicates a problem with CICS default
processing please save all diagnostic information and
contact your support organization. To bypass the
problem either select a correct working CICS region
name or establish a new working region name by
updating the environment variable CICSREGION.
Destination:
stderr
ERZ056020E Unable to set locale as localeName
Explanation:
CICS was unsuccessful in setting locale either because
the catalog does not exist or because it was unable to
be found.
System action:
The request is abnormally terminated.
User response:
On UNIX the locale categories within the locale can be
modified by a number of environment variables. Ensure
that each of these environment variables contains a
valid locale for the machine where the operation is to be
done (such as LANG=en-us) and then retry.
Destination:
stderr
ERZ056055E Abnormal termination U5655: A
crucial mutual exclusion lock at
address lockAddress is held by a
terminated process
Explanation:
In order to maintain integrity of data structures CICS
uses a mutual exclusion locking scheme; a process has
terminated without releasing its exclusive hold on a
resource lock.
System action:
The region is abnormally terminated with code U5655.
User response:
Refer to preceding and subsequent messages for an
indication of why this happened. Additionally, the system
administrator needs to investigate the disappearance of
the process. For example, a force purge of a transaction
has this effect.
Destination:
console.msg
detected an inconsistency in a unique
identity pools state: range start
RangeStart is greater than range end
RangeEnd
419
ERZ056057E ERZ057004E
Explanation:
When performing self-consistency checking, CICS
a unique identity pool has become corrupt. RangeStart
must be less than or equal to RangeEnd.
System action:
User response:
Destination:
console.msg
detected an inconsistency in a unique
identity pools state: range start
RangeStart and range end RangeEnd
conflict with either current pool size
PoolSize or pool highwater mark
HighWaterMark
Explanation:
When performing self-consistency checking, CICS
a unique identity pool has become corrupt. PoolSize
and HighWaterMark must never exceed the difference
between RangeEnd and RangeStart.
System action:
User response:
Destination:
console.msg
ERZ057001E Cannot access message catalog
catalogName for message messageId
Explanation:
CICS was unable to retrieve the message text from the
message catalog catalogName. Note that the Message
Sequence Number (MSN) associated with this message
is the MSN for the original message.
System action:
User response:
If this is the first time CICS is being run, then ensure
that the operating system permits a sufficient number of
open files per process. Otherwise, check that an
accessible CICS message catalog exists in a directory
named in your environment variable NLSPATH. On
UNIX, a possible additional cause is that the
environment variable LANG is not valid.
420
Destination:
console.msg
ERZ057002E CICS internal error: Unsuccessful
condition conditionName for function
functionName on line lineNumber in file
fileName of module moduleNumber
Explanation:
CICS internal validation has detected a condition
conditionName for function functionName that is not
supposed to occur.
System action:
CICS generates one of the following messages:
ERZ5703E, ERZ5704E, ERZ5705E, ERZ5706E, or
ERZ5707E.
User response:
Refer to next message.
Destination:
console.msg, CSMT, stderr
ERZ057003E CICS internal error: Abnormally
terminating process with exit code
returnCode
Explanation:
CICS detected an unsuccessful condition within the
CICS internal code.
System action:
CICS abnormally terminates the relevant process with
abnormal termination code A57A. If the condition was
detected while processing an application then the
application server terminates and CICS attempts to
continue. Otherwise, the region terminates.
User response:
As this indicates a problem with CICS it is important
that you save all diagnostic information, especially
dumps, and contact your support organization.
Destination:
CSMT
terminating transaction with exit code
returnCode
Explanation:
CICS detected an unsuccessful condition in the internal
code of one of its transactions.
System action:
CICS abnormally terminates the transaction with
abnormal termination code A57A.
User response:
As this problem indicates a problem with a CICS
supplied transaction it is important that you save all
diagnostic information, especially dumps, and contact
ERZ057005E ERZ057021E
Destination:
stderr
terminating region with exit code
returnCode
Explanation:
CICS detected an unsuccessful condition within the
CICS internal code.
System action:
CICS abnormally terminates the region with abnormal
termination code U5701.
User response:
As this problem indicates a problem with CICS it is
important that you save all diagnostic information,
especially dumps, and contact your support
organization.
Destination:
console.msg
terminating threaded utility
Explanation:
code of one of its threaded utilities.
System action:
CICS abnormally terminates the threaded utility with
code 99.
User response:
As this problem indicates a problem with a CICS
threaded utility it is important that you save all
diagnostic information and contact your support
organization.
Destination:
stderr
terminating utility
Explanation:
code of one of its utilities.
System action:
CICS abnormally terminates the utility with code 99.
User response:
As this problem indicates a problem with a CICS utility it
is important that you save all diagnostic information and
Destination:
stderr
ERZ057010E Unable to display message

messageId as it is corrupted in
catalog catalogName
Explanation:
The message text CICS retrieved from the message
catalog catalogName was not prefixed by ERZ. Note
that the Message Sequence Number (MSN) associated
with this message is the MSN for the original message.
System action:
User response:
Check the operating system error log to confirm that
there are no disk problems. Otherwise, as this problem
is not supposed to occur, reinstall the CICS Machine
Readable Information (MRI) for your language.
Destination:
console.msg
ERZ057017E Not enough memory available to
initiate error handling
Explanation:
CICS was unable to allocate the memory required for
error processing.
System action:
User response:
Increase the size of the Region pool memory, as
defined in the Region Definitions (RD), by overriding the
attribute in the region startup command line and restart
the region.
Destination:
stderr
ERZ057020E Inconsistent signature string
Explanation:
inconsistency in one of its internal data structures
System action:
User response:
Check the system dump for signs of an inconsistency.
Destination:
console.msg
ERZ057021E Buffer OVERFLOW while processing
message messageId - supplied size
lengthu, required size sizeu
Explanation:
CICS message processing facility has overwritten a
buffer.
421
ERZ057022W ERZ057027E
System action:
CICS abnormally terminates the current execution
environment: in the runtime, the whole region is
terminated; elsewhere, the current process is
terminated.
User response:
The message catalog is possibly corrupted. Reinstall
the CICS Machine Readable Information (MRI) for your
language. If the problem persists, contact your support
organization.
User response:
Examine following messages to determine the cause of
the error.
Destination:
stderr
ERZ057025W Failed to open the symptom record
file fileName with error number
errorNumber
Destination:
console.msg, stderr
Explanation:
CICS was unable to open the file to which symptom
records are written.
ERZ057022W Failed to complete write to file

fileName with error number
errorNumber
System action:
CICS attempts to write the symptom record to standard
error. Another attempt is made to open the file the next
time that a symptom record has to be written.
Explanation:
CICS was unable to flush symptom record from an
output buffer to file fileName.
System action:
CICS continues.
User response:
Ensure that the file system for file fileName is not full.
For further information check the operating system
documentation for a description of error number
errorNumber.
Destination:
stderr
ERZ057023I Transaction transId timed out on
terminal termId due to a prolonged
transient error condition
Explanation:
CICS has encountered an error condition that was
supposed to be temporary. After several retries of the
operation the condition has not cleared.
System action:
User response:
Examine following messages to determine the cause of
the error.
Destination:
console.msg, stderr
ERZ057024I Utility/program timed out due to a
prolonged transient error condition
Explanation:
CICS has encountered an error condition that was
supposed to be temporary. After several retries of the
operation the condition has not cleared.
System action:
The utility/program is abnormally terminated.
422
User response:
Ensure that file fileName exists and that it has the
correct access permissions. Check the operating system
errorNumber.
Destination:
stderr
ERZ057026W Failed writing symptom record to file
fileName with error number
errorNumber
Explanation:
CICS was unable to perform a buffered write to file
fileName, where symptom records are written.
System action:
CICS continues.
User response:
Ensure that the file system for file fileName is not full.
For further information check the operating system
errorNumber.
Destination:
stderr
ERZ057027E Not enough memory available to save
locale
Explanation:
CICS was unable to obtain region memory while
attempting to save locale information.
System action:
User response:
Increase the size of the Region pool memory, as
defined in the Region Definitions (RD), by overriding the
attribute in the region startup command line and restart
the region.
ERZ057028W ERZ057033E
Destination:
stderr
ERZ057028W Failed to duplicate standard error
with error number errorNumber
Explanation:
CICS was unable to obtain a duplicate file descriptor or
a file stream for the duplicate standard error (stderr).
System action:
CICS continues, using unduplicated standard error. If
Animator is used CICS messages written to standard
error are displayed on the Animator panel and are not
written to the stderr destination.
ERZ057031E Unable to format message messageId

Explanation:
CICS retrieved the named message from the message
catalog but was unable to format the message. It is
likely that the message catalog being used is out of
date. Note that the Message Sequence Number (MSN)
associated with this message (ERZ5731E) is the MSN
for the original message that CICS failed to format.
System action:
User response:
Refer to the operating system documentation for a
description of error number errorNumber. Correct the
problem and restart the region.
User response:
Reinstall the CICS Machine Readable Information (MRI)
for your language. If the problem persists, consult your
support organization: there is a mismatch between the
message as defined in the message catalog and the
variable-replacement arguments supplied in the CICS
code.
Destination:
stderr
Destination:
console.msg
ERZ057029E Failed to open message catalog
ERZ057032E Buffer OVERFLOW while processing

internal text - supplied size lengthu,
required size sizeu
Explanation:
CICS was unable to open the message catalog cics.cat.
System action:
If the catalog was being opened for a task, the task is
terminated. If it was being opened for a region, the
region is abnormally terminated.
User response:
Check that there is a CICS message catalog in a
directory defined by the environment variable NLSPATH
and the the user cics has permission to read it. On
UNIX, also check that the environment variable LANG is
correct.
Destination:
console.msg, CSMT
ERZ057030E Failed to set locale LC_ALL to
localeName
Explanation:
CICS message processing facility has overwritten a
buffer.
System action:
CICS abnormally terminates the current execution
environment: in the runtime, the whole region is
terminated; elsewhere, the current process is
terminated.
User response:
The message catalog is possibly corrupted. Reinstall
the CICS Machine Readable Information (MRI) for your
language. If the problem persists, contact your support
organization.
Destination:
console.msg, stderr
Explanation:
CICS was unable to change locale.
ERZ057033E CICS is unable to attach shared

memory.
System action:
The region or the task is terminated.
Explanation:
CICS made an unsuccessful attempt to attach shared
memory. An earlier message provides more details.
User response:
that started the region or submitted the transaction
request. The locale categories within the locale can be
modified by a number of environment variables. Ensure
these environment variables contain a valid locale for
the machine where the operation is to be done and then
retry.
Destination:
console.msg, CSMT
System action:
User response:
Restart the region. If the problem recurs, restart the
region again with Monitoring disabled. If the problem
Destination:
CSMT
423
ERZ057034I ERZ058003E
ERZ057034I Previous console file is
Explanation:
CICS has started a new console file. The previous
console file has exceeded the limit set in the Region
Definition (RD) attribute MaxConsoleSize. If
MaxConsoleSize is set to 0, then the region starts a
new console only at region start time. Otherwise the
region starts a new console when MaxConsoleSize is
exceeded.
System action:
CICS continues.
User response:
None.
Destination:
console.msg
ERZ057035I Next console file is
Explanation:
CICS has started a new console file. The previous
console file has exceeded the limit set in the Region
Definition (RD) attribute MaxConsoleSize. If
MaxConsoleSize is set to 0, then the region starts a
new console only at region start time. Otherwise the
region starts a new console when MaxConsoleSize is
exceeded.
ERZ058001E Unsuccessful load of program

programName; error errorNumber
Explanation:
CICS cannot load the program programName for the
reason defined by the operating system error number
errorNumber. If more information is available from the
operating system regarding the failure, it is logged as
one or more subsequent ERZ5803E messages.
System action:
An error is returned to the function that requested the
load of the program.
User response:
Using the operating system error number and any
ERZ5803E messages logged, check that the program is
installed correctly, with the correct permissions, and that
any necessary shared libraries are installed correctly.
Destination:
stderr or console.msg
ERZ058002E Unable to find entry point for program
programName; error errorNumber
Explanation:
CICS is unable to find the main function for the
program.
System action:
CICS continues.
System action:
load of the program.
User response:
None.
User response:
Check that the program is built and installed correctly.
Destination:
console.msg
Destination:
ERZ057036E Failed to start new console

newFileName file, continuing to use
oldFileName
ERZ058003E Information on unsuccessful program

load: errorMessage
Explanation:
CICS has failed to start a new console file when the
Region Definition (RD) attribute MaxConsoleSize was
exceeded.
System action:
CICS continues to use the existing console file. CICS
tries to start a new console file when a further
MaxConsoleSize characters are written to the console
file.
User response:
Check the file system where the console files are stored
is not full.
Destination:
console.msg
424
Explanation:
This message contains diagnostic information from the
operating system relating to the previous failure to load
a program, reported in an earlier ERZ5801E message.
System action:
None
User response:
The information in this message can be used to
diagnose why the program load was unsuccessful. The
message consists of an ASCII message number
followed by zero or more characters of error-specific
message data. See the operating system
documentation for the loadquery() function for details of
how to interpret these messages.
Destination:
ERZ058004E ERZ058008E
ERZ058004E Unsuccessful unload of program with
handle handle; error errorNumber
Explanation:
CICS cannot unload the program represented by the
handle handle. The handle corresponding to a load of a
particular program is written in a system trace record.
The operating system error number is errorNumber.
System action:
unload of the program.
User response:
specific failure. The problem is possibly caused by an
inconsistency in the CICS Program Control internal data
structures. Consider shutting the region down if any
further errors are reported. Save any dump file
produced for use by your support organization.
Destination:
console.msg
ERZ058005E CICS is unable to acquire additional
storage to hold information on loaded
programs
Explanation:
CICS is unable to allocate additional storage to hold
information on all programs loaded by a process. If the
process that fails is the translator, the storage is
allocated from the standard heap of the process;
otherwise the storage is allocated from the Task-Private
Pool.
System action:
information.
User response:
The limit on the amount of data a process can use
possibly needs to be increased. If the problem occurs
during the execution of a transaction, determine if the
transaction is using excessive amounts of Task-Private
Pool (Getmain) storage and correct this. Alternatively,
consider restarting the region with an override for the
value of the MaxTaskPrivatePool attribute in the Region
Definition (RD).
Destination:
ERZ058006E CICS is unable to retrieve information
on loaded programs; return code
returnCode, error errorNumber
Explanation:
CICS is unable to retrieve information from the
operating system regarding the programs loaded by the
process. The problem is not caused by a shortage of
storage.

information.
User response:
specific failure. If the problem persists, save the
symptom record file and any dumps produced and
Destination:
ERZ058007E CICS is unable to allocate Region
Pool storage
Explanation:
CICS is unable to allocate storage from the Region Pool
to maintain the information on the programs loaded by
the process.
System action:
After further processing the transaction abnormally
terminates.
User response:
being acquired and released by CICS on behalf of
running transactions, retrying the transaction can
you retry the transaction, consider increasing the size of
the Region Pool by restarting the region with an
override for the value of the MaxRegionPool attribute in
the Region Definition (RD).
Destination:
console.msg
hold information on loaded programs
Explanation:
CICS is unable to allocate storage to hold information
on all programs loaded by a process. If the process that
fails is the translator, the storage is allocated from the
standard heap of the process; otherwise the storage is
allocated from the Task-Private Pool.
System action:
information.
User response:
possibly needs to be increased. If the problem occurs
during the execution of a transaction, determine if the
transaction is using excessive amounts of Task-Private
Pool (Getmain) storage and correct this. Alternatively,
consider restarting the region with an override for the
value of the MaxTaskPrivatePool attribute in the Region
Definition (RD).
Destination:
System action:
425
ERZ058009E ERZ058014I
ERZ058009E Data conversion routines between
code page codePage1 and code page
codePage2 are not available- errno is
errNo
Explanation:
CICS was unable to initialize the routines that are used
to convert data from code page codePage1 to code
page codePage2. This conversion is carried out when
processing data that is to be sent to, or was received
from, a remote system. The error number errNo is the
system errno set by the data conversion routines.
CICS uses the iconv data conversion routines if they
are available on the local operating system. Otherwise it
uses its own data conversion routines. In either case,
there is a different conversion routine for each pair of
code pages. Not all combinations of code page pairs
are supported. So it is possible that either one or both
of the names, codePage1 and codePage2, are not valid
code page names, or alternatively conversion routines
do not exist for this particular pair.
System action:
User response:
Check your operating system documentation to
determine if it supports iconv.
If iconv is available, reconfigure your CICS environment
so it is using code pages supported by your operating
system.
Where iconv is not provided by the operating system,
refer to the CICS documentation that lists the supported
code page pairs. Reconfigure your CICS environment to
only use these supported code pages.
Destination:
console.msg
ERZ058011E CICS was unable to interpret the
program stack
Explanation:
CICS detected a corrupt machine stack frame.
System action:
None
User response:
If this message is logged during the execution of a user
transaction then check that the transaction did not
corrupt the stack. Otherwise the problem lies in the
CICS code. If the problem persists, save the symptom
record file and any dumps produced and contact your
Destination:
console.msg
ERZ058012E No region name has been specified
Explanation:
The user has issued a cicsstart command, but did not
specify the name of the region to be started.
System action:
None
User response:
Retry the command specifying the correct region name.
Destination:
stdout
ERZ058013E Region regionName is locked
Refer to the CICS Intercommunication manual for

information on data conversion and configuring code
pages in your CICS region.
Explanation:
The user has issued a cicsstart command, but the
specified region is locked. This means the region either
is currently running or has terminated abnormally.
Destination:
CSMT
System action:
None
ERZ058010E Unable to handle signal

Explanation:
CICS was unable to trap an operating system signal
using the sigaction command.
System action:
User response:
Examine the CICS symptom record for the operating
system error number returned by the sigaction
command and check the operating system
documentation for a full description. For AIX, this
information can be found in the AIX Base Operating
System and Extensions Techincal Reference, Volume 2.
426
User response:
Investigate the reason why the lock exists and if
appropriate remove it. The cicsrlck command can be
used for this purpose.
Destination:
stdout
ERZ058014I Region regionName is being COLD
started
Explanation:
The user has issued a cicsstart command for a new
region or has specified the -c flag.
System action:
None
ERZ058015I ERZ058020I
User response:
None, this is an informational message.
Destination:
stdout
-f
Perform an immediate shutdown of CICS
-k
Perform a forced shutdown of CICS
System action:
None
ERZ058015I Region regionName is being AUTO

started
User response:
If the message was as a result of a syntax error, correct
the error and retry the command.
Explanation:
The user has issued a cicsstart command for the
specified region and a normal startup is in progress.
Destination:
stdout
System action:
None
User response:
Destination:
stdout
ERZ058016E Executing commandName requires
Administrator authority
Explanation:
The specified command can only be executed by users
with Administrator authority.
System action:
None
User response:
Log in as a user with Administrator authority and retry
the command.
Destination:
stderr
ERZ058016E Executing commandName requires
Administrator authority
Explanation:
with Administrator authority.
ERZ058018I The use of cancel (-k) is not

recommended. Do you wish to
continue?
Explanation:
A cicsstop -k command was issued for the region
identified in message ERZ5819I. The user must indicate
whether or not processing is to continue.
System action:
The system waits for the user to respond before
proceeding.
User response:
The user must reply with y to proceed, or with n to
terminate. If n is specified, no processing is performed.
Destination:
stdout
ERZ058019I Stop processing requested for
regionName
Explanation:
A cicsstop command was accepted for the indicated
region.
System action:
None
User response:
None
System action:
None
Destination:
stdout
User response:
Log in as a user with Administrator authority and retry
the command.
ERZ058020I Interrupting processName
Destination:
stderr
ERZ058017I Usage: cicsstop -? | {[-f] [-k] [REGION]}
Explanation:
This message indicates valid options for the cicsstop
command. It is issued in response to -? or as a result of
a syntactically incorrect request. The flags have the
following meanings:
-?
Display this message
Explanation:
identified by message ERZ5819I. The command
attempts to interrupt the indicated process before killing
it. Several of these messages can be issued. The first is
always preceded by message ERZ5818I.
System action:
None
User response:
None
Destination:
stdout
427
ERZ058021I ERZ058027I
ERZ058021I Killing processName
Explanation:
identified by message ERZ5819I. The command issues
a kill -9 for the indicated process. Several of these
messages can be issued. They are preceded by one or
more instances of ERZ5820I.
System action:
None
User response:
None
Destination:
stdout
ERZ058022E Error code (errorCode) starting
regionName
Explanation:
Processing attempted on behalf of a previous request
has failed. The failing request was an attempt to start a
region or an associated server (log or SFS).
System action:
The original request failed.
User response:
Check that passwords for users cics or Ssfs_server has
not expired. Use the error information to determine the
nature of the problem. Once the cause of the failure is
corrected, the failing request can be retried.
Destination:
stdout
ERZ058023I Subsystem subsystemName (process
ID processId) has been started
Explanation:
Processing on behalf of a previous start request was
completed.
System action:
The indicated subsystem initializes.
User response:
None
Destination:
stdout
ERZ058024E Unable to update the cicssrc
database for subsystem
subsystemName(processId) - error
code (errorCode)
Explanation:
An attempt to update information associated with the
indicated subsystem has failed.
System action:
None
428
User response:
No immediate action is necessary; the region was
started successfully. When it is necessary to shut down
the region, this must be performed manually by using
the signal command to notify the cics process.
Destination:
stdout
ERZ058025E Unable to start program
programName for subsystem
subsystemName
Explanation:
cicsstartsrc was not able to locate the indicated program
on behalf of the indicated subsystem.
System action:
None; the specified program is not started.
User response:
Correct the program name, or make the specified
program available. The command can then be retried.
Destination:
stdout
ERZ058026E Option optionName requires an
argument
Explanation:
The indicated command option requires a value to be
specified but none was. A usage message follows this
message indicating the expected syntax of the
command.
System action:
None
User response:
Correct the error and retry the command.
Destination:
stdout
ERZ058027I Usage: cicsstartsrc [ -a argumentString
] [ -e environment ] { -s
subsystemName | -g groupName }
Explanation:
This message is displayed as a result of -? being
specified or as a result of a preceding command
specification error. The meaning of the flags is as
follows:
-a
an argument string to be passed as a

parameter to the subsystem when it is started.
-e
any environment settings required for the

subsystem.
-s
the name of the subsystem to be started
-g
the name of a group to be started. All

subsystems in the group are started.
ERZ058028E ERZ058033I
System action:
None
User response:
If this message is displayed because of a preceding
error, correct the error and retry the command.
Destination:
stdout
ERZ058028E Unable to lock the cicssrc database error code (errorCode)
Explanation:
The command was unable to obtain exclusive access to
the cicssrc database.
System action:
None
User response:
Retry the command.
Destination:
stdout
ERZ058029E Group groupName is undefined or is
empty
Explanation:
An attempt to start the resources associated with the
indicated group failed.
System action:
None
User response:
Check that the group name was properly specified. If it
was, then there are no resources associated with that
name. Use the cicslssrc command to examine the
content of the repository and determine the correct
name.
ERZ058031E Unable to start subsystem

subsystemName - error code
(errorCode)
Explanation:
cicsstartsrc located the specified subsystem, but the
attempt to start it failed.
System action:
None
User response:
Destination:
stdout
ERZ058032E Skipping subsystem subsystemName
because of previous failure
Explanation:
Due to a previous error, cicsstartsrc is flushing
subsequent resources for which processing was
requested.
System action:
None
User response:
Destination:
stdout
ERZ058033I Usage: cicsstopsrc [ -f | -c ] { -a | -g
groupName | -s subsystemName [ -p
subsystemProcessId ] }
Explanation:
specification error. The flags have the following
meanings:
Destination:
stdout
-f
Perform an immediate shutdown of the

specified subsystem. SIGUSR1 is used to
request termination.
ERZ058030E Subsystem subsystemName is not

defined
-c
Cancel the specified subsystem. SIGKILL is

used to terminate the processes associated
with the subsystem.
-a
stop all known subsystems.
-g
stop all subsystems in the specified group.
-s
stop the specified subsystem.
User response:
Correct the subsystem name and retry the command.
-p
stop the specified subsystem, further qualified

by the specified process id
Destination:
stdout
System action:
None
Explanation:
A request to start the specified subsystem failed,
because its name was not recognized.
System action:
None
User response:
If this message was issued because of a preceding
syntax error, correct the error and retry the command.
Destination:
429
ERZ058034E ERZ058041I
stdout
Destination:
stdout
ERZ058034E No selection criteria specified, -a, -g

or -s is required
Explanation:
A cicsstopsrc command was issued, but no resources
were selected.
System action:
None
User response:
Retry the command indicating the resources for which
processing is to be performed.
ERZ058038I Subsystem subsystemName

successfully removed
Explanation:
The specified subsystem was successfully removed
from the cicssrc database.
System action:
None
User response:
None
Destination:
stdout
Destination:
stdout
ERZ058035E Subsystem name not specified
ERZ058039E Unable to remove subsystem

(errorCode)
Explanation:
A subsystem name was required but not specified.
System action:
None
Explanation:
A request to remove the specified subsystem from the
cicssrc database has failed.
User response:
Specify an appropriate subsystem name and retry the
command.
System action:
None
Destination:
stdout
ERZ058036E Unable to stop subsystem
(errorCode)
Explanation:
cicsstopsrc attempted to stop the named subsystem, but
processing failed.
System action:
None
User response:
Take whatever corrective actions are indicated by the
messages accompanying the error.
Destination:
stdout
ERZ058037I Usage: cicsrmssys -s subsystemName
Explanation:
specification error. -s identifies the subsystem to be
removed.
System action:
None
User response:
430
User response:
Destination:
stdout
ERZ058040E No modename specified, or else the
modename was too long
Explanation:
When attempting to allocate a conversation, no mode
name was specified. The mode name must either be
specified in the transaction definition or in the
communications definition or in the environment variable
CICS_SNA_MODE_NAME. This message can also
appear if the modename was specified by
CICS_SNA_MODE_NAME, but the mode name
specified was too long.
System action:
The conversation is not allocated.
User response:
Specify a valid mode name.
Destination:
console.msg
ERZ058041I Usage: mkssys -p -s -G -u -a -i -o -e -d
-D -q -Q -f -n -S -w
Explanation:
specification error.
ERZ058042E ERZ058047I
System action:
None
User response:
Destination:
stdout
ERZ058042E Subsystem subsystemName is
already defined
Explanation:
An attempt was made to add the named subsystem to
the cicssrc database, but a subsystem of the same
name is already defined.
ERZ058045I Subsystem Group PID Status

Explanation:
This is the first line of a multi-line display produced by
the cicslssrc command. Subsystem and group identify
subsystems and the group (if any) to which they belong.
Status indicates the current disposition of the
subsystem. If a subsystem is currently active, or is in
the process of being shutdown, PID identifies the
process ID of the principal process associated with the
subsystem.
System action:
None
User response:
None
System action:
None
Destination:
stdout
User response:
Correct the subsystem name as retry the command.
ERZ058046I subsystemStatus
Destination:
stdout
Explanation:
This is part of a multi-line display. The meaning of the
values returned is described in message ERZ5845I.

successfully added to the cicssrc
database
System action:
None
Explanation:
The specified subsystem was added to the cicssrc
database.
System action:
None
User response:
None
Destination:
stdout
ERZ058044E Error errorCode attempting to add
subsystemName to the cicssrc
database
Explanation:
The indicated error occurred while attempting to add the
specified subsystem to the cicssrc database.
System action:
None
User response:
Destination:
stdout
User response:
None
Destination:
stdout
ERZ058047I Usage: cicslssrc { [ -a ] | -s
subsystemName | -g groupName }
Explanation:
specification error. The flags have the following
significance:
-a
list all subsystems in the database.
-s
list the specified subsystem.
-g
list subsystems associated with specified

group.
System action:
None
User response:
Destination:
stdout
431
ERZ058048E ERZ058054E
ERZ058048E No subsystems were selected
Explanation:
The cicslssrc command as issued did not cause any
subsystems to be displayed.
System action:
None
User response:
If this was not the expected response, check the
selection criteria used and, if necessary, retry the
command.
Destination:
stdout
ERZ058049E Unable to display subsystem
subsystemName
Explanation:
The specified subsystem was unable to be displayed.
System action:
None
User response:
Destination:
stdout
ERZ058050E Unable to initialize cicssrc database
transactional services
Explanation:
Initialization of built-in transactional facilities for the
cicssrc database failed.
System action:
None
User response:
Check access permissions on the cicssrc database, its
parent directory, and related files in the directory. Also
ensure availability of free disk space within the parent
directory.
Destination:
stdout
ERZ058051E Subsystem subsystemName is active
and cannot be removed
Explanation:
An attempt was made to remove an active subsystem
using cicsrmssys. In order to be removed, a subsystem
must not be running.
System action:
None
User response:
Terminate the subsystem and retry the command.
Destination:
432
stdout
ERZ058052E Subsystem subsystemName is
already active
Explanation:
An attempt was made to start a subsystem that is
already running and does not permit multiple concurrent
instantiations.
System action:
None
User response:
Be content that the subsystem is already running, or
stop the subsystem and retry this command to restart it.
Destination:
stdout
ERZ058053W Subsystem or service
subsystemName is not active
Explanation:
An attempt was made to stop a subsystem or service
that is not running.
System action:
None
User response:
Check that the subsystem or service is not active. On
UNIX use ps -ef. On Windows NT look at the Services
from the Control Panel window. On UNIX if you want to
stop the subsystem manually, for the main cics region
process or for a log or SFS, first issue kill -s SIGUSR1
subsystemProcessId. If after a reasonable period of
time the subsystem has not terminated, issue kill -s
SIGTERM subsystemProcessId. AT YOUR OWN RISK,
you can issue kill -s SIGKILL subsystemProcessId to
terminate the subsystem as a last resort. However, this
is not recommended as the subsystem cannot catch
and handle SIGKILL and therefore cannot shutdown
cleanly.
Destination:
stdout
ERZ058054E Cannot remove cicssrc database lock
file lockFile
Explanation:
An attempt to remove the lock file named in the error
message failed. The named lock file synchronizes
access to a file of the same name, less the .lock
suffix.
System action:
None. The lock file remains.
User response:
Ensure that the file access permissions on the lock files
parent directory permit write access for the cics user
and members of the cics group. If the lock file no longer
ERZ058055E ERZ058059E
exists, determine whether its absence is due to manual
intervention (rm) by a CICS administrator or to a defect
in CICS. If the lock file does exist, consider removing it
by using rm, being careful to remove the lock file only if
it was created on behalf of the command just issued,
rather than being created on behalf of another user
currently issuing the same or a similar command. That
is, be careful not to remove another lock belonging to
another process.
Destination:
stdout
ERZ058055E Unable to lock fileName. File does
not exist.
Explanation:
An attempt was made to lock a non-existent file. This
error is not expected to occur, but is included for
completeness.
System action:
None
User response:
None
Destination:
stdout
ERZ058056E User lacks write access to fileName.
Lock failed.
Explanation:
A lock file cannot be created because the issuing user
does not have write access to the directory in which the
lock file is to be created.
System action:
None
User response:
Insure that the specified directory allows write access
for the cics user and group.
Destination:
stdout
and then retry the failing command. In the latter case,

manually remove the lock file as indicated in the
message text.
Destination:
stdout
ERZ058058E Unable to backout incomplete
updates made by a previous command
to the cicssrc database,
databaseName
Explanation:
The command issued results, or possibly results, in
modification of the cicssrc database, and therefore must
initialize its transaction services. The primary function of
this initialization is to complete any uncommitted
changes made by commands previously issued.
Transaction service initialization presumes changes to
be incomplete if the cicssrc database before image or
syncpoint, taken when the previous command started its
transaction, still exists. This indicates that the previous
transaction did not complete commit or backout
processing, so any updates made by the transaction
must be backed out (undone). This is accomplished by
overwriting the cicssrc database with its before image
from the previous transaction, kept in a file of the same
name as the cicssrc database, suffixed by .sync.
Receiving this message indicates that the syncpoint file
exists, but was unable to be reinstated as the official
cicssrc database file.
System action:
None
User response:
Examine accompanying error message for clues
indicating why the cicssrc database syncpoint file was
unable to be reinstated. Also, examine access
permissions on the cicssrc database files directory and
files therein. Look for disk space errors in that directory.
Correct any errors noted and retry the command. As a
last resort, a CICS administrator or super-user can, after
comparing the contents of the two files, overlay the
cicssrc database with the syncpoint file, removing the
latter.
ERZ058057E Unable to lock the cicssrc database. If

appropriate, remove lockFileName to
unlock.
Destination:
stdout
Explanation:
Lock file creation failed, presumably because the lock
file already exists.
ERZ058059E Cannot remove intermediate

syncpoint file fileName
System action:
None
User response:
Either the file is temporarily locked because it is being
accessed by another command, or a previous command
failed to properly release its lock. In the former case,
simply wait a few moments for the lock to be released
Explanation:
A transaction is being initiated against the cicssrc
database. The intermediate transaction syncpoint file
specified in the message text exists, presumably left
behind by a previous command, and cannot be
removed. Therefore, transaction initiation fails.
System action:
None
User response:
433
ERZ058060E ERZ058065E
Remove the specified file and retry the command.
Destination:
stdout
ERZ058060E Cannot create intermediate syncpoint
file fileName
Explanation:
A transaction is being initiated against the cicssrc
database. The intermediate transaction syncpoint file
specified in the message text cannot be created.
Therefore, transaction initiation fails.
System action:
None
User response:
Examine preceding error messages for clues indicating
why the intermediate syncpoint file for the cicssrc
database was unable to be created. Correct problems
found, and retry the command.
Examine preceding error messages for possible causes,

correct any found, and retry the command. Ensure that
the parent directory and files therein are writable by the
cics user and group.
Destination:
stdout
ERZ058063E Unable to commit updates to
databaseName. Removal of syncpoint
fileName failed.
Explanation:
The command attempted to commit updates it made to
the cicssrc database, but failed because the before
image (syncpoint) taken of the database prior to the
updates cannot be deleted.
System action:
None
Destination:
stdout
User response:
correct any found, and retry the command. Ensure that
the parent directory and files therein are writable by the
cics user and group.
ERZ058061E Cannot syncpoint cicssrc database,

databaseName, to intermediate
syncpoint file, fileName
Destination:
stdout
Explanation:
Initiation of a transaction against the cicssrc database
requires that a syncpoint of the database file be taken
before any updates are applied. Copy of syncpoint
information from the cicssrc database file to an
intermediate syncpoint file failed.
System action:
None
User response:
Examine preceding error messages for clues indicating
why syncpoint information was unable to be copied.
Correct problems found and retry the command.
Destination:
stdout
ERZ058062E Cannot rename cicssrc database
intermediate syncpoint, fileName, to
install to actual syncpoint fileName
Explanation:
A syncpoint of the cicssrc database file is taken at the
beginning of a transaction. First, a complete syncpoint is
created in an intermediate file. Once complete, the
intermediate syncpoint is renamed into place as the
official syncpoint for the transaction. This rename, and
hence transaction initiation, has failed.
System action:
None
User response:
434
ERZ058064E Internal shell script or function

invoked with incorrect syntax
Explanation:
CICS-internal command syntax error. Incorrect or
insufficient options or arguments were passed to an
internal CICS shell script or function.
System action:
None
User response:
Report a defect against the product.
Destination:
stdout
ERZ058065E Cannot backout cicssrc database
updates. Syncpoint file fileName does
not exist.
Explanation:
A request was made to backout transactional updates
made to the cicssrc database, but the syncpoint file
indicated by the message text, which is supposed to
contain a syncpoint of the database before any updates
were made, does not exist.
System action:
Updates made by the transaction are not undone and
become permanent.
User response:
None
ERZ058066E ERZ058071E
Destination:
stdout
Destination:
stdout
ERZ058066E Cannot backout cicssrc database

updates. Overlay of database,
databaseName, with the previous
syncpoint, fileName, failed.
ERZ058069E Cannot set group ownership on

directory databaseName to group
groupName
Explanation:
A request was made to backout transactional updates
made to the cicssrc database, but the syncpoint file
indicated by the message text, which contains a
syncpoint of the database before any updates were
made, cannot be reinstated by moving the syncpoint file
into place as the actual database.
System action:
None
User response:
Manually replace the cicssrc database file with its
syncpoint file as given in the message text, or examine
preceding error messages for possible causes, correct
any found, and retry the command. Insure that the
parent directory and files therein are writable by the cics
user and group.
Destination:
stdout
ERZ058067E regionName is not a valid region
name
Explanation:
The user has issued a cicsstart, cicsstop, or cicstail
command, but the name supplied is not the name of a
valid region.
System action:
None
User response:
Destination:
stdout
ERZ058068E Cannot create cicssrc database
directory, databaseName
Explanation:
The directory given in the message text does not exist
and was unable to be created. This directory is
supposed to be created during product installation, and
therefore this error is unexpected.
System action:
None
User response:
Check that directories along the path to the directory
being created either do not exist, or are writable by the
cics user and group. Otherwsie, retry the command as
super-user.
Explanation:
The cicssrc database directory did not exist, and so it
was just created. However, group ownership on the
directory was unable to be set to the primary CICS user
group as given in the message text.
System action:
The directory, having invalid ownership, and therefore
access, is removed.
User response:
Retry the command as super-user. If the same error is
still seen, examine preceding error message for
possible causes, correct any found, and retry the
command.
Destination:
stdout
ERZ058070E Cannot create file fileName
Explanation:
The file specified in the message text, probably either
the actual cicssrc database file or a file to contain a
syncpoint of the database, was unable to be created.
System action:
None
User response:
correct any found, and retry the command. Insure that
the parent directory is writable by the cics user and
group. Make sure enough disk space is available for the
file.
Destination:
stdout
ERZ058071E Cannot set access permissions
(accessPermissions) on fileName
Explanation:
On UNIX, the cicssrc database file or its syncpoint file
was successfully created, but its access permissions
were unable to be set to those given in parentheses.
System action:
None
User response:
Set access permissions on the file as indicated in the
message text by issuing the command chmod
accessPermissions fileName. Then retry the command.
Destination:
stdout
435
ERZ058072E ERZ058086E
ERZ058072E Cannot set group ownership of file
fileName to group groupName
ERZ058078E Error reading cicssrc database image

databaseName. Select failed.
Explanation:
The cicssrc database file or its syncpoint was
successfully created, but an attempt to assign group
ownership of the file to the specified user group failed.
Explanation:
An internal function was called to select cicssrc
database entries matching certain selection criteria from
a specified or defaulted database-image file. An error
occurred reading the specified or defaulted file
containing the database image.
System action:
None
User response:
Assign group ownership of the file manually, by issuing
the command chgrp groupName fileName. Without
proper ownership on the file, the wrong users can
possibly have access to the file, while the people who
are supposed to (members of the specified group) can
possibly not.
Destination:
stdout
ERZ058076E cicssrc database image
databaseName does not exist. Select
failed.
Explanation:
a specified or defaulted database-image file. The
specified or defaulted file containing the database
image does not exist.
System action:
None
User response:
None
Destination:
stdout
ERZ058077E Cannot read cicssrc database image
databaseName - permission denied.
Select failed.
Explanation:
a specified or defaulted database-image file. The
specified or defaulted file containing the database
image does not permit the user read access.
System action:
None
User response:
Adjust permissions on the file and retry the command,
or retry the command as a user with access to the file.
Destination:
stdout
System action:
None
User response:
correct any found, and retry the command.
Destination:
stdout
ERZ058085E Cannot rename cicssrc database
databaseName. Entry deletion failed.
Explanation:
Deletion from the cicssrc database involves renaming
the current database to a temporary location, creating a
new database file, and writing all entries from the
original database to the empty new database except the
entry being deleted. Renaming the cicssrc database
failed, so the subsystem entry was unable to be
deleted.
System action:
None
User response:
Insure that the cicssrc database directory permits write
access for the cics user and group. Examine preceding
error messages for possible causes of the rename
failure, correct any found, and retry the command.
Destination:
stdout
ERZ058086E Cannot create a new cicssrc database
file, databaseName. Restoring original
from backup copy. Entry deletion
failed.
Explanation:
entry being deleted. Creation of an empty new database
file failed, so the original, temporarily renamed, is
renamed back.
System action:
The original cicssrc database file is renamed back into
place.
User response:
Follow the instructions associated with the error
messages displayed just prior to the current.
436
ERZ058087E ERZ058092I
Destination:
stdout
ERZ058087E Cannot restore original
databaseName from backup copy in
backupName
Explanation:
entry being deleted. Creation of, or writing to, an empty
new database file failed, raising ERZ5886E or
ERZ5888E, and causing an attempt to be made to
restore the database by renaming it back from its
temporary location. This recovery action also failed.
-c
cold-start the region
-a
auto-start the region
-o
override the specified CICS parameter
System action:
None
User response:
If the message was issued as the result of an error,
correct the command and retry it.
Destination:
stdout
ERZ058090I Subsystem subsystemName is not
defined
System action:
None
Explanation:
A request to start the specified subsystem failed,
because its name was not recognized.
User response:
If the backup copy exists, rename it back into place as
the actual cicssrc database file.
System action:
None
Destination:
stdout
ERZ058088E Cannot rewrite cicssrc database
databaseName. Restoring original
from backup copy. Entry deletion
failed.
Explanation:
entry being deleted. The empty new database file was
created, but an error was encountered writing to it.
System action:
The original cicssrc database file is renamed back into
place.
User response:
Examine error messages displayed just prior to this for
possible causes, correct any found, and retry the
command. Check for an out of disk space condition
on the file system containing the cicssrc database.
Destination:
stdout
ERZ058089I Usage: cicsstart -? | {[-c] [-a] [-o
name=value ...] [region]}
Explanation:
Describes the options available on the cicsstart
command. This message is issued in response to -? or
as a result of a syntactically invalid request. The flags
have the following meanings:
-?
display this message
User response:
Correct the subsystem name and retry the command.
Destination:
stdout
ERZ058091I Retrying the cicssrc database lock for
up to waitTime seconds
Explanation:
CICS requires access to the CICS subsystem database
file, cicssrcdb, which is currently locked by another
process.
System action:
CICS waits a maximum of the specified number of
seconds for the lock to become available. If the lock
becomes available during this period of time, it is taken
by the current process that displays message ERZ5892I
and proceeds as normal. Otherwise, message
ERZ5857E is displayed and processing terminates.
User response:
None
Destination:
stderr
ERZ058092I The cicssrc database was successfully
locked with retries
Explanation:
Though the CICS subsystem database file was initially
locked by another process, subsequent retry
successfully obtained the lock.
System action:
Processing requiring the lock proceeds as normal.
User response:
None
437
ERZ058093E ERZ058098E
Destination:
stderr
ERZ058093E Cannot create file fileName
Explanation:
An attempt to create or write to the specified file failed.
System action:
The requested action terminates unsuccessfully.
User response:
Check ownership and access permissions on the parent
directory. Also check that the corresponding file system
is not full.
Destination:
stderr
ERZ058094E Unable to nohup a process to launch
and monitor subsystem
subsystemName. Error code
errorCode.
Explanation:
The users request to start the specified CICS region, or
associated log or SFS, subsystem failed due to an error
encountered when attempting to nohup a process which
in turn was to spawn the subsystem process, field
shutdown requests for the subsystem, and perform
cleanup for the subsystem if it terminates abnormally.
The error code returned by nohup is also given.
System action:
Subsystem startup fails.
User response:
Varies depending upon the specific error returned.
Examine the error code and any accompanying
messages for clues as to the cause. After correcting any
problems found, retry the command.
ERZ058096I Usage: cicsmknotify -n

subsystemName -m notifyMethod
Explanation:
specification error. The meanings of the flags are as
follows:
-m
specifies the notify method for the specified

subsystem, which is the absolute path of an
executable script or program to be run upon
abnormal termination of the subsystem.
-n
name of the subsystem for which the notify

method is to be configured.
System action:
None
User response:
If issued as a result of a syntax error, correct the
command and retry it.
Destination:
stdout
ERZ058097E Notify method already defined for
Explanation:
An attempt was made to define a notify method for a
subsystem for which a notify method was already
defined.
System action:
None
User response:
To update the notify method, first use cicsrmnotify to
remove the existing notify method, then retry this
command.
Destination:
stderr
Destination:
stderr
ERZ058095E The monitor process for subsystem

subsystemName was unable to start
the subsystem
ERZ058098E Unable to update the notify method

for subsystem subsystemName
Explanation:
The users request to start the specified CICS region, or
associated log server or SFS, subsystem failed when
the subsystems monitor process was unable to spawn
the subsystem process.
System action:
Subsystem startup fails.
User response:
Examine accompanying messages for clues to the
cause. After correcting any problems found, you can
retry the command.
Destination:
stderr
438
Explanation:
An attempt to update the notify method field of the
specified subsystems cicssrc database entry failed. The
notify method is an executable script or program run
automatically by the CICS System Resource Controller
(SRC) upon abnormal termination of the subsystem to
perform such cleanup as releasing subsystem locks,
and terminating straggling subsystem processes.
System action:
None. An error is returned to the caller, which can
ignore the error or terminate unsuccessfully.
User response:
Examine accompanying messages for clues to the
cause of the failure. If the command failed as a result of
ERZ058099I ERZ058104E
this error, retry the command after eliminating possible
causes. If the command succeeded, no steps need be
taken initially. However, if the notify method was being
defined, rather than removed, it needs to be run
manually if the subsystem terminates abnormally. In that
case upon abnormal termination of the subsystem, if it
is: (a) a region, issue cicsnotify cics.regionName, (b) a
PPC gateway server, issue cicsppcgwynotify
cicsppcgwy.gwyServerName, and (c) an SFS server,
issue cicssfsnotify cicssfs.SFSserverName.
Destination:
stderr
ERZ058099I Notify method added for subsystem
subsystemName
Explanation:
A notify method was successfully added for the
specified subsystem. The CICS subsystem controller
automatically executes the notify method if the
subsystem terminates abnormally, that is, without being
requested to shut down.
System action:
None
User response:
None
Destination:
stdout
ERZ058100I Usage: cicsrmnotify -n
subsystemName
Explanation:
specification error. The meanings of the flags are as
follows:
-n
name of the subsystem whose notify method

is to be removed.
System action:
None
User response:
If this message is issued as the result of a syntax error,
Destination:
stdout
ERZ058101E No notify method is defined for
Explanation:
An attempt was made to remove a notify method for a
subsystem for which no notify method is defined.
System action:
None
User response:
None
Destination:
stderr
ERZ058102I Notify method for subsystem
subsystemName removed
Explanation:
The specified subsystems notify method was
successfully removed.
System action:
None
User response:
None
Destination:
stdout
ERZ058103E Unsuccessful load of shared library
programName; error errorNumber; text
errorMessage.
Explanation:
CICS cannot load the shared library programName for
the reason defined by the operating system error
number errorNumber and error message
errorMessage.
System action:
load of the library.
User response:
Using the operating system error number and the error
message text, check that the shared library is installed
correctly, with the correct permissions and ownership,
and that all its external references can be resolved by
other shared libraries.
Destination:
ERZ058104E CICS could not find the entry point
name entryPointName in the shared
library programName; error
errorNumber; text errorMessage.
Explanation:
CICS loaded the shared library programName
successfully, but was unable to locate the entry point
entryPointName in it.
System action:
The library was unloaded and cannot be used.
User response:
Using the operating system error number and the error
message text, check that the shared library is installed
correctly. Check that the entry point exists in the shared
library and that it is exported correctly.
439
ERZ058105W ERZ058108E
Destination:
CICS abnormally terminates all local SNA intersystem

requests until your SNA product is active. CICS tries to
connect with the SNA product every ten seconds.
ERZ058105W The TaskSharedPoolBase address

violates COBOL restrictions
User response:
Restart the SNA product.
Explanation:
COBOL cannot access addresses above the 31 bit
boundary so you must put the task shared pool below
the 31 bit boundary if you intend to use COBOL. CICS
passes addresses from the task shared pool back to
user transactions. This fails for COBOL transactions.
You can ignore this message if you do not use COBOL
at all. You can reliably put the task shared pool above
or below the 31 bit boundary if you only run C
transactions. If you use COBOL, the entire task shared
pool must be below the 31 bit boundary: that is
TaskSharedPoolBase plus MaxTSHPool.
Destination:
console.msg and CSMT
System action:
CICS continues to initialize, but any COBOL
transactions you run can possibly abend.
v IBM Communications Server for AIX is not installed

on this machine.
User response:
Ignore this message if you never run COBOL
transactions. Otherwise change the value of the
TaskSharedPoolBase or MaxTSHPool attribute so that
the task shared pool is below the 31 bit boundary.
Destination:
console.msg
ERZ058108E Unsuccessful open on SNA logical

unit. Error number errorNumber.
Explanation:
CICS is unable to connect to IBM Communications
Server for AIX in order to send or receive intersystem
requests over SNA. errorNumber is the error number
(errno) returned to CICS by AIX on the open system
call. This problem can be caused because:
v IBM Communications Server for AIX is not correctly

configured for CICS.
v The system is short on resources which is preventing
the open call from succeeding.
System action:
CICS retries the open system call every ten seconds.
Until it is successful, CICS is not able to send or receive
intersystem requests using local SNA.
User response:
ERZ058106E Unsuccessful attempt to start a

listener thread
Explanation:
An attempt to start a local SNA listener thread was
unsuccessful. Threads are used within the local SNA
listener process (cicssl) to handle multiple incoming
intersystem requests. The most likely reason a thread
fails to start is that there is insufficient memory available
in the system to start the thread.
System action:
CICS can possibly not accept incoming intersystem
requests using local SNA.
User response:
Reduce the load of the system by running fewer
programs.
Destination:
console.msg
ERZ058107W SNA is not active. Restart the SNA
subsystem.
Explanation:
CICS has detected that your SNA product is not
running. This means it is unable to send or receive local
SNA intersystem requests.
System action:
440
v Check that IBM Communications Server for AIX is

installed on your machine. If IBM Communications
Server for AIX was not installed on the system, either
remove the Listener Definition (LD) entry for local
SNA support from the region database, or, if local
SNA support is required, install IBM Communications
Server for AIX.
v Check that IBM Communications Server for AIX is
correctly configured. The TXSeries for Multiplatforms
Using IBM Communications Server for AIX with CICS
explains how to set up IBM Communications Server
for AIX.
v Check that all IBM Communications Server for AIX
configuration is activated by issuing the verifysna -R
command.
v If IBM Communications Server for AIX is correctly
configured, refer to the IBM Communications Server
for AIX manuals for an explanation of the error
number. This can indicate which resource the system
is running out of.
Destination:
console.msg and CSMT
ERZ058109E ERZ058112E
ERZ058109E
Storage allocation request from

Task-Private Pool was unsuccessful
Explanation:
CICS was unable to obtain Task-Private Pool storage
for an incoming local SNA intersystem request. This is
possibly because the Task-Private Pool is too small for
the amount of work your region is managing or because
incoming requests are not being scheduled quickly
enough.
System action:
and disconnects from the SNA service for 10 seconds.
User response:
If this message occurs frequently, increase the size of
the Task-Private Pool available by restarting the region
and overriding the MaxTaskPrivatePool attribute with a
larger value on the command line. In addition, using the
CICS TASK statistics (see the TXSeries for
Multiplatforms Administration Guide), check that:
v The number of application servers is sufficient for the
number of transactions your region is running.
v The maximum task class limits are not too low for
some of your regions transactions.
The number of application servers and the maximum
task class limits can be altered when your region is
started by specifying new values for the MaxServer,
ClassMaxTasks and ClassMaxTaskLim attributes on the
command line. Alternatively, the TCLASS option of
CEMT allows you to alter these values while your region
is running.
Refer to the TXSeries for Multiplatforms Administration
Reference for more information on the attributes
mentioned above and for information on CEMT.
Destination:
console.msg
ERZ058110E Unsuccessful AIX select operation.
Error number errorNumber.
Explanation:
CICS was unable to issue a select system call on the
IBM Communications Server for AIX file descriptor being
used to handle incoming local SNA intersystem
requests. errorNumber is the error number (errno)
returned to CICS by AIX.
System action:
CICS stops listening for inbound local SNA intersystem
requests.
User response:
Refer to the relevant AIX manuals for an explanation of
the error number and take appropriate action.
Destination:
console.msg
ERZ058111E Unsuccessful IBM Communications

Server for AIX get parameters
operation. Error number errorNumber.
Explanation:
CICS was unable to issue an ioctl(GET_PARAMETERS)
system call on the IBM Communications Server for AIX
file descriptor while receiving an incoming intersystem
request. errorNumber is the error number (errno)
returned to CICS by AIX.
System action:
CICS closes and reopens the file descriptor with IBM
Communications Server for AIX to handle further
intersystem requests. The incoming intersystem request
is abnormally terminated.
User response:
Refer to the IBM Communications Server for AIX
manuals for an explanation of the error number and
take appropriate action.
Destination:
console.msg
ERZ058112E Unable to configure transaction(s)
transactionList using a TPNSNAProfile
of SNAprofile with IBM
Communications Server for AIX
Explanation:
CICS was unable to configure IBM Communications
Server for AIX with details about its transactions in order
to make them available for incoming intersystem
requests. The failure can be for one of the following
reasons:
v The LocalLUName attribute in the Region Definition
(RD) entry for your region matches the
GatewayLUName attribute of a Gateway Definition
(GD) entry.
v The GatewayLUName attribute of a GD entry is .
This means the GatewayLUName defaults to the
value in the LocalLUName attribute of the RD entry.
which is registered with IBM Communications Server
for AIX and is using the same local SNA Logical Unit
(LU) name defined in the LocalLUName attribute of
the RD entry.
System action:
systems can fail.
User response:
v Examine the CICS messages written to your regions
console.msg file as CICS logs whether the LU names
used by your region conflict. If messages were
logged, follow the instructions for these messages.
v Check there is no other copy of CICS or other SNA
application (the PPC gateway, for example) running
using the same local LU name configured for this
441
ERZ058113E ERZ058116E
region. If another application matches the same LU
name as CICS, either change the CICS LU name
and restart CICS, or terminate the other application.
Destination:
console.msg
ERZ058113E Unable to configure transaction(s)
using a TPNSNAProfile of SNAprofile
with IBM Communications Server for
AIX. Error number errorNumber.
Explanation:
CICS was unable to configure IBM Communications
Server for AIX with the transaction(s) that have
TPNSNAProfile=SNAprofile defined in their Transaction
Definitions (TD) entry. This means CICS can not receive
incoming intersystem requests for these transactions.
The failure can be for one of the following reasons:
v The profile SNAprofile has the characters DEFAULT in
its name.
v The profile SNAprofile is not correctly defined in IBM
Communications Server for AIX.
System action:
requests from remote SNA systems for the transactions
configured with TPNSNAProfile=SNAprofile can fail.
User response:
manuals for an explanation of the error number.
Use the sna -d l command to check that IBM
Communications Server for AIX is running. If required,
restart IBM Communications Server for AIX and your
AIX SNA link stations and CICS reconnects to SNA.
If IBM Communications Server for AIX is running, then
this error is caused by the TPN profile SNAprofile not
being recognized by IBM Communications Server for
AIX, or being invalid. Check that the IBM
Communications Server for AIX TPN profile called
SNAprofile exists and use the verifysna -R command
to add this new profile to the AIX SNA runtime
database. The TXSeries for Multiplatforms Using IBM
Communications Server for AIX with CICS explains how
to create IBM Communications Server for AIX TPN
profiles. Note that IBM Communications Server for AIX
does not permit you to define a TPN profile that has the
string DEFAULT in its name. So, for example, if
SNAprofile is TDEFAULT, modify all TD entries in
your region that use this profile name and ensure the
new value used is the name of a valid IBM
Communications Server for AIX TPN profile. Once you
have defined the TPN profile either restart your CICS
region to redrive the SNA configuration, or restart SNA
and CICS automatically redrives the SNA configuration.
Destination:
console.msg
442

was unsuccessful
Explanation:
A transaction name was unable to be converted from
the code page codePage1 to the code page
registering or unregistering a Transaction name with
your local SNA product.
System action:
The register or unregister request is not performed.
User response:
support (NLS) environment of the CICS system. If a
required code page descriptor is not installed, a
preceding message indicates which one is missing (see
the operating system documentation for further
information). If this is not the case, then contact your
Destination:
console.msg
ERZ058115W Transaction transId has already been
deleted from IBM Communications
Server for AIX
Explanation:
transId was deleted from the region. This TD entry has
the name of a SNA profile in the TPNSNAProfile
attribute. CICS has requested IBM Communications
Server for AIX to unregister this CICS transaction but
the transaction was not recognized or is already
unregistered.
System action:
User response:
Check there is no other copy of CICS or other SNA
application (the PPC gateway, for example) running
using the same local SNA logical unit name configured
for this region. The logical unit is defined either by the
LocalLUName attribute specified by the Region
Definition (RD), or, if null, by the name of the CICS
region.
Destination:
console.msg
ERZ058116E Unable to delete transaction transId
from IBM Communications Server for
AIX. Error number errorNumber.
Explanation:
ERZ058117E ERZ058121E
attribute. CICS has requested IBM Communications
Server for AIX to unregister this CICS transaction but
the request failed.
System action:
User response:
manuals for an explanation of the error number (errno).
AIX SNA link stations. CICS redrives the SNA
configuration once SNA is available.
Destination:
console.msg
allocation when registering transId
with local SNA
Explanation:
CICS was unable to obtain sufficient Region Pool
memory to register or unregister a transaction transId
with your SNA product. The amount of region storage
available is configured in the MaxRegionPool attribute of
your regions Region Definition (RD) entry.
System action:
CICS does not accept local SNA intersystem requests
for the transaction.
User response:
As CICS is continually acquiring and releasing region
storage on behalf of running transactions, retrying the
request can be successful. However, if this problem
occurs frequently, increase the size of the region pool
by overriding the MaxRegionPool value when you next
restart your CICS region.
This message is for information only. No action is

required.
Destination:
console.msg
ERZ058119I Deleting transaction transId from IBM
Explanation:
the name of an IBM Communications Server for AIX
LU6.2 Transaction Program Name profile in the
TPNSNAProfile attribute. CICS is about to request IBM
Communications Server for AIX to unregister this CICS
transaction from the list of transaction definitions.
System action:
CICS passes the name of the transaction transId to the
IBM Communications Server for AIX to unregister.
User response:
None
Destination:
console.msg
ERZ058120I Usage: cicschssys -s subsystemName
{ -S -n sigNormal -f sigForce | -p
programName }
Explanation:
specification error. -s identifies the subsystem to be
changed. -n identifies the normal stop signal. -f
identifies the forced stop signal. -p identifies the
program executed by the subsystem
System action:
None
Destination:
console.msg
User response:
ERZ058118I Configuring transaction transId with

IBM Communications Server for AIX
Destination:
stdout
Explanation:
transId was installed in the region. This TD entry has
attribute. CICS attempts to register this transaction with
IBM Communications Server for AIX. The SNA Server
needs to know the names of CICS transactions in order
to receive requests for them from remote SNA systems.
System action:
CICS passes the name of the transaction transId to IBM
Communications Server for AIX for registration.
User response:
ERZ058121E Subsystem subsystemName is active

and cannot be changed
Explanation:
An attempt was made to change an active subsystem
using cicschssys. In order to be changed, a subsystem
must not be running.
System action:
None
User response:
Terminate the subsystem and retry the command.
Destination:
443
ERZ058122I ERZ058127E
stdout
successfully changed
Explanation:
The specified subsystem was successfully changed in
the cicssrc database.
System action:
None
User response:
None
Destination:
stdout
ERZ058123E Unable to change subsystem
(errorCode)
v Use the verifysna -R command to commit the

updates to the AIX SNA profiles. Check the
messages from this command, as they can possibly
request that AIX SNA is restarted before the updates
take effect.
Destination:
CSMT or console.msg
ERZ058125E Function shipping or transaction
routing has been attempted to a non
CICS system
Explanation:
An attempt was made to transaction route or to function
ship to a system that is not CICS. Function shipping
and transaction routing services are only available on
CICS systems.
System action:
Explanation:
A request to change the specified subsystem in the
cicssrc database has failed.
User response:
Investigate why this has happened and correct the
problem.
System action:
None
Destination:
CSMT
User response:
Destination:
stdout
ERZ058124E
SNA has not been configured with

the cics primary group
Explanation:
CICS is not permitted to use some of the SNA functions
because the primary group of the cics userid was not
added to the list of trusted groups held in the IBM
Communications Server for AIX system defaults profile.
System action:
The SNA request is unsuccessful. Further messages
can be logged.
User response:
v Use the lsuser command to display the primary group
name of the cics userid.
$ lsuser cics
cics id=6853 pgrp=cics groups=cics,cicsterm,
cicsdemo,guest home=/usr/lpp/cics shell=/bin/ksh
gecos=CICS System User
$
The primary group is shown as the pgrp. The
standard primary group, as in this example, is cics.
v Log in as the root user.
v Configure the IBM Communications Server for AIXs
system defaults profile with this primary group as
described in TXSeries for Multiplatforms Using IBM
Communications Server for AIX with CICS.
444
ERZ058126E An unexpected error (errorNumber)

was received from SNA services
Explanation:
Error number (errno) errorNumber returned from an IBM
Communications Server for AIX call. This error number
is not expected by CICS so CICS can not handle the
error.
System action:
User response:
Look in your IBM Communications Server for AIX
documentation to discover the meaning of the error
number. If the problem persists contact your support
organization.
Destination:
CSMT
was unsuccessful
Explanation:
Data was unable to be converted between code page
codePage1 and code page codePage2. This
conversion is performed when encoding a message that
is about to be sent to, or when decoding a message
that was received from a remote system.
System action:
User response:
ERZ058128W ERZ058133E
Ensure that a code page conversion exists for the code
pages codePage1 and codePage2. Consult the
operating system documentation for further details. If a
code page conversion does exist, contact your support
organization.
Destination:
CSMT
ERZ058128W PIP data exceeds 16 elements for
transaction transId
Explanation:
More than 16 elements of PIP data were received with
an incoming local SNA intersystem request for
This can be caused because IBM Communications
Server for AIX passes PIP data elements to CICS in a
single buffer separated by X20 bytes. If the PIP data
contained any X20 bytes, CICS incorrectly parses the
PIP data and splits up a PIP data element into two or
more elements. This can result in the transaction
receiving more elements than were sent and some of
the X20 bytes being removed from the PIP data.
System action:
CICS schedules the intersystem request. The final
element of PIP data passed to the transaction includes
the excess PIP data.
User response:
Ensure that no more than 16 elements of PIP data are
sent by the front-end application and that this PIP data
does not contain any X20 bytes.
Destination:
CSMT
ERZ058129W Failed to set permissions for file
fileName
Explanation:
cicscp failed to set the permissions on the file fileName
to the correct value.
System action:
The cicscp command continues.
User response:
Check that root has the necessary permissions on the
file system containing the file.
Destination:
stderr
ERZ058130W Failed to set group for file fileName
Explanation:
cicscp failed to set the group on the file fileName to the
correct value.
System action:
User response:
Destination:
stderr
ERZ058131W Failed to set owner for file fileName
Explanation:
cicscp failed to set the owner of the file fileName to the
correct value.
System action:
User response:
Destination:
stderr
ERZ058132E CICS is unable to acquire additional
miscellaneous storage
Explanation:
CICS is unable to allocate additional storage to hold
miscellaneous transient information during configuration
by cicscp. The storage is allocated from the standard
heap of the process.
System action:
information.
User response:
possibly needs to be increased.
Destination:
stderr
ERZ058133E Abnormal termination U5802. CICS
failed to attach shared memory.
Explanation:
CICS failed to attach the Region Pool shared memory.
The access permissions to the CICS shared memory
segments were possibly altered, or the data segment
shared memory identifier was possibly overwritten.
System action:
User response:
On UNIX ask the system administrator to check for
inconsistencies in the CICS shared memory segments
using the ipcs command; these segments must have
read and write permissions for the user cics who must
be a member of the user group cics. If the SysDump
attribute in the Region Definition is set to yes then a
region dump file is produced. Save this dump file.
Restart the region (ensuring the region is configured to
445
ERZ058134E ERZ058138E
produce a dump if the problem recurs). If the problem
cannot be identified, call your support organization.
the servers using the logical volume must be

reconfigured to use a different logical volume.
Destination:
console.msg
Destination:
stderr
ERZ058134E Unable to contact the SNAplus server.

Primary return code returnCode,
secondary return code errorNumber.
ERZ058137E Linking failed because fileName file

was not writeable
Explanation:
CICS was unable to issue the SNAplus API command
receive_allocate. returnCode represents the SNAplus
primary return code and errorNumber the secondary
return code.
System action:
CICS does not accept incoming conversation requests
using local SNA. Incoming requests are abnormally
terminated.
User response:
Refer to the SNAplus manuals for an explanation of
primary and secondary return codes. Correct the
SNAplus Server problem.
Destination:
console.msg
ERZ058135E Logical volume volumeName is
currently owned by user userIdu
Explanation:
During the creation of an SFS or a PPC gateway, cicscp
detected that the logical volume that was to be used
already existed and was owned by a different user ID
from that required by the server being created.
System action:
The server is not created.
User response:
Choose a different userid for the server, change the
owner of the logical volume or remove the logical
volume.
Destination:
stderr
ERZ058136W Logical volume volumeName already
exists
Explanation:
During the creation of an SFS or a PPC gateway, cicscp
detected that the logical volume that was to be used
already existed. The logical volume is owned by the
correct user ID and is used for the server but it is
possible that the logical volume is already in use.
System action:
The server is created.
User response:
If the logical volume is not in use no action is
necessary. If the logical volume is in use then one of
446
Explanation:
cicstcl detected that an so_locations file already exists
but the file cannot be written to as it is required by the
OSF1 linker. The most likely cause is that the
so_locations file was created by another user.
System action:
Compilation and linking are not attempted.
User response:
Rename or remove the so_locations file. If you do not
have the required permissions to do this, then contact
the file owner or system administrator to rename or
remove the so_locations file.
Destination:
stderr
ERZ058138E
Unable to make intersystem request

from local LU localLU to partner LU
partnerLU using modename
modeName
Explanation:
An intersystem request to partnerLU was unsuccessful
because:
v IBM Communications Server for AIX does not
recognize your CICS regions local Logical Unit (LU)
name localLU. This LU name is configured in the
entry for your region.
v IBM Communications Server for AIX does not
recognize the remote systems LU name partnerLU.
This LU name is configured either in the
SNAConnectName or in the RemoteLUName
attribute of the Communications Definitions (CD)
entry used for the intersystem request.
v The modename modeName is null () and a default
modename was not configured in IBM
Communications Server for AIX. CICS uses a null
modename if:
a modename is not passed on the PROFILE
parameter of an EXEC CICS ALLOCATE
command and
there is no modename configured in the
SNAModeName attribute of the Transaction
Definitions (TD) entry for the transaction that
issued the intersystem request and
there is no modename configured in the
DefaultSNAModeName attribute of the
Communications Definition (CD) entry for the
SYSID (connection) used on the request.
ERZ058139E ERZ058142E
System action:
logged.
User response:
v Check that CICS is using the correct values for the
local LU name localLU, partner LU name partnerLU
and modename modeName. Correct these values if
required.
v Check that there is an IBM Communications Server
for AIX LU6.2 Side Information profile called localLU
which has the local LU alias set to localLU and the
modename set to a modename recognized by all
remote systems. Add or correct the IBM
Communications Server for AIX LU6.2 Side
Information profile as required.
for AIX LU6.2 Local LU profile that has the local LU
alias and the local LU name set to localLU. Add or
correct the IBM Communications Server for AIX Local
LU profile as required.
for AIX LU6.2 Partner profile called partnerLU which
has the partner LU alias set to partnerLU. Add or
correct the IBM Communications Server for AIX
LU6.2 partner profile, as required.
v Issue the verifysna -R command to ensure all IBM
Communications Server for AIXs profiles are
consistent and available to CICS.
Once the configuration is correct, retry the intersystem
request.
Destination:
CSMT
ERZ058139E Abnormal termination A583. COBOL
run-time system (RTS) is not
recoverable by CICS.
Explanation:
A program has exited with the Micro Focus COBOL
RTS in an unknown state, and possibly also with an
incomplete logical unit of work. This can happen when
using the Micro Focus COBOL ANIMATOR debugger,
for example, or when the Micro Focus COBOL RTS
returns an error.
System action:
CICS abnormally terminates the application server to
back out any incomplete logical unit of work, and to
terminate the Micro Focus COBOL RTS for that
application server. Further messages are logged if a
logical unit of work is backed out. This avoids leaving
the Micro Focus COBOL RTS in an unknown state as
this can prevent successful execution of subsequent
COBOL programs.
User response:
Depending on the transaction involved, it is possibly

acceptable to do nothing, such as when using
ANIMATOR, or it can be necessary to correct and
Destination:
console.msg
allocation when handling local SNA
logical unit
Explanation:
CICS was attempting to obtain sufficient Region Pool
memory to request registration of transactions with the
IBM Communications Server for AIX. Insufficient Region
Pool memory was available.
System action:
Incoming intersystem requests are abnormally
terminated.
User response:
You can increase the size of the Region Pool available
command line.
Destination:
console.msg
ERZ058141E Unsuccessful open of memory
mapped file fileName.errorMessage
Explanation:
The program cicscvt cannot open the specified
memory-mapped file for the reason given by the
operating system as errorMessage.
System action:
cicscvt terminates immediately.
User response:
Consult the operating system documentation on the
function openx() and try again when the system is less
busy and has more memory available. If the problem
still persists, then contact your support organization.
Destination:
stderr
ERZ058142E Unsuccessful attach of memory
mapped file fileName to current
process errorMessage
Explanation:
The program cicscvt cannot attach the memory mapped
file it created to the current process. This situation can
occur when cicscvt runs out of memory.
System action:
cicscvt terminates immediately.
User response:
447
ERZ058147E ERZ058151E
Consult the operating system documentation on the
function shmat() and try again when the system is less
busy and has more memory available. If the problem
still persists, then contact your support organization.
Destination:
stderr
ERZ058147E An unexpected error errorNumber
(hexErrorNumber) was received from
SNA services.
Explanation:
Error number (errno) errorNumber returned from a SNA
services call. This error number is not expected by
CICS so CICS can not handle the error.
System action:
User response:
Look in your SNA Server documentation to discover the
meaning of the error number. If the problem persists
Destination:
CSMT
ERZ058148W Unsupported synclevel 2
resynchronization transaction 0x06F2
request has been received
Explanation:
A SNA resynchronization transaction request was
received by the SNA listener. The remote system is
assuming the connection supports synchronization level
2, but the SNA listener only supports synchronization
levels 0 and 1.
System action:
The resynchronization transaction is abnormally
terminated. All further synchronization level 0 and 1
requests using the connection are processed normally.
User response:
Reconfigure the connection at the remote system to not
attempt binding sessions at synchronization level 2
and/or sending the resynchronization transaction.
Destination:
console.msg
ERZ058149E Local DEC SNA APPC/LU6.2
Programming Interface return code
(returnCode). Message - messageString.
This Local SNA return code is mapped into a more

general CICS return code for the transaction. Refer also
to the DEC SNA APPC/LU6.2 Programming Interface
documentation and to subsequent messages for more
details.
Destination:
console.msg
ERZ058150E Local SNA listener for Local LU
localLUName has encountered a
problem communicating with LU6.2
SNA Server Identifier snaServerId at
Server Node snaServerNode.
Explanation:
The ATTACH_LISTEN verb within the Listener thread
returned a status indicating there was a problem
communicating with the LU6.2 SNA Server. If the Server
is down, restart it. It is possible be that the LU6.2 SNA
Server is running but is not yet configured.
System action:
CICS continues to try to connect with the LU6.2 SNA
Server. This message is issued after a time interval until
the LU6.2 Server is reconfigured/restarted.
User response:
Check that the LU6.2 SNA Server is running and that it
is configured correctly. If necessary, restart and
reconfigure the LU6.2 SNA Server. Check that the
SNAServer details in the CICS Listener Definition are
correct and that they match those used by the
configuration program. Check that the value of the
LocalLUName attribute in the Region Definition matches
that specified in the LU6.2 Server configuration file. If
the LocalLUName attribute in the Region Definition is
not specified then the CICS region name is used by
default. Refer to any earlier console messages for more
information on the returned status.
Destination:
console.msg
ERZ058151E CICS Local SNA is unable to acquire
storage for dataLength bytes of Pip
Data on the inbound Tpn tpName from
remote LU remoteLU.
Explanation:
There was insufficient storage available on a CICS
application server to allocate storage for incoming PIP
Data.
Explanation:
An abnormal return code was returned by the DEC SNA
APPC/LU6.2 Programming Interface.
System action:
CICS deallocates the conversation and returns a
Resource Failure No Retry Sense Code to the remote
LU.
System action:
The action taken is dependent upon the return code
severity.
User response:
Determine if the transaction is using excessive amounts
of Task-Private Pool (Getmain) storage and correct this.
User response:
Destination:
448
ERZ058152E ERZ058157E
console.msg
ERZ058152E CICS Local SNA is unable to acquire
storage for dataLength bytes of Pip
Data .
Explanation:
There was insufficient storage available on a CICS
application server to allocate storage for outbound PIP
Data.
System action:
The CICS Allocate call is unsuccessful.
User response:
Determine if the transaction is using excessive amounts
of Task-Private Pool (Getmain) storage and correct this.
Destination:
CSMT
ERZ058153E Local SNA Listener has encountered
a problem communicating with the
LU6.2 SNA Server. DEC SNA Message messageString.
Explanation:
Local SNA has encountered a problem communicating
with the LU6.2 SNA Server. The return codes displayed
on the console were returned from the DEC SNA
APPC/LU6.2 Programming Interface, called within CICS,
which is used to communicate with the LU6.2 SNA
Server process.
System action:
All Local SNA intersystem requests are rejected.
User response:
Check that the LU6.2 SNA Server is running. If it is not
running then restart it. Run the Server configuration
program (this is not a CICS program) to install the
required LU and mode definitions in the Server. It is not
usually necessary to restart CICS.
Destination:
console.msg
ERZ058154E Local SNA Listener is abnormally
terminating. DEC SNA APPC/LU6.2
Programming Interface return code
(returnCode). DEC SNA Message messageString.
Explanation:
An abnormal return code has caused the Local SNA
Listener to abnormally terminate. No intersystem
requests using local SNA can take place until the region
is restarted.
System action:
The Listener thread is shut down.
User response:

Listener thread terminated. The region needs to be
restarted before intersystem requests through local SNA
can be restarted. Refer to the DEC SNA APPC/LU6.2
Programming Interface documentation for additional
return code information.
Destination:
console.msg
ERZ058155E An unexpected return code
(returnCode) was received from the
DEC SNA APPC/LU6.2 Programming
Interface
Explanation:
Status returnCode was not expected to be returned
from the DEC SNA APPC/LU6.2 Programming Interface.
System action:
User response:
Refer to the DEC SNA APPC/LU6.2 Programming
Interface documentation for further information on this
return code. Refer also to any subsequent console and
CSMT log messages.
Destination:
CSMT
ERZ058156E Transaction transId from remote LU
remoteLU has been rejected with
Sense Code (senseCode)
Explanation:
The inbound attach for transaction transId was
rejected.
System action:
The transaction is rejected.
User response:
Check the Sense Code in the ISC guide to determine
the reason for the transaction rejection.
Destination:
console.msg
ERZ058157E Unsuccessful Task Pool memory
allocation in local SNA for Transaction
transId with remote LU remoteSysId.
Explanation:
CICS was attempting to obtain sufficient Task Pool
memory to handle an incoming InterSystem
Communication (ISC) request. Insufficient Task Pool
System action:
The Incoming ISC request is rejected.
User response:
449
ERZ058158E ERZ058164E
You can increase the size of the Task-Private Pool
storage by changing the MaxTaskPrivatePool attribute in
the Region Definition (RD) and restarting the region.
Destination:
stderr
Destination:
console.msg
ERZ058161E The Link Station Name must be

supplied
ERZ058158E Unexpected CNOS transaction

received from remote LU remoteLU,
Sense Code (senseCode)
Explanation:
This message is displayed if cicscp detects that the
create or destroy sna_link command was invoked
without the Link Station Name argument.
Explanation:
A CNOS (change number of sessions 06F1, also
referred to as CLS1) transaction was received by the
Listener. CNOS, by default is handled by the SNA
LU6.2 Server. It is possible that an external application
has overridden the default by issuing a DEFINE_TP
verb, and allowed CNOS into CICS.
System action:
The CNOS transaction is rejected.
User response:
Refer the DEC SNA APPC/LU6.2 Programming
Interface documentation for details on how to set the
SNA LU 6.2 Server to handle the CNOS transaction.
Destination:
console.msg
System action:
None
User response:
Specify at least the type of the link and the link name.
Destination:
stderr
ERZ058162E The Link Station Address must be
supplied
Explanation:
create sna_link command, for the LLC2 link station type,
was invoked without the Link Station Address argument.
System action:
None

was received from the DEC SNA
Programming Interface
User response:
Specify at least the type of the link, the link name, and
the link station address.
Explanation:
The error errorNumber was not expected from DEC
SNA Programming Interface.
Destination:
stderr
System action:
ERZ058163E The required XID_NODE_ID

environment variable is not set
User response:
Look in the DEC SNA Programming Interface
documentation to discover the cause. Refer also to any
additional Console and CSMT log messages.
Explanation:
create sna_link command was invoked without the
environment variable XID_NODE_ID set. This is
required on DEC OSF/1 sna configuration to create a
link station definition.
Destination:
CSMT
ERZ058160E Operation only allowed on local Peer
Server
Explanation:
This message is displayed if cicscp detects that a SNA
configuration command was invoked on a node that
indicates that the Peer Server it uses is remote (the
GATEWAY_HOST environment variable is set).
System action:
None
User response:
Export the XID_NODE_ID environment variable in the
current shell and invoke the command again.
Destination:
stderr
System action:
None
ERZ058164E Attempt to create or destroy an

unsupported link station type
User response:
Either unset the GATEWAY_HOST environment variable
(if the Peer Server used is actually installed on the local
machine) or go to the Peer Server host and retry.
Explanation:
create or destroy sna_link command was invoked that
450
ERZ058165E ERZ058171E
specifies either a currently unsupported link station type,
or the valid link station type none
Destination:
stderr
System action:
None
ERZ058168E Invalid action specified
User response:
Use a supported link station type (not none).
Destination:
stderr
ERZ058165E The LLC2 mandatory Token Ring
station TRN-0 is not or cannot be
defined
Explanation:
create LLC2 sna_link command was invoked and that
the token ring station TRN-0 is either not defined
(remote Peer Server) or is not defined and cannot be
defined (local Peer Server)
System action:
None
User response:
If local Peer Server, investigate why it cannot be
defined. If remote Peer Server, the station needs to be
defined manually.
Destination:
stderr
ERZ058166E Usage: cicssnacfg [-r regionName] [-c
className] [-P|-R|-B] [-a action] [-t] [-f]
[-v] [[type=name]...] [resourceName]
[[attributeName=attributeValue]...]
Explanation:
Explanation:
The action specified on the -a option of the cicssnacfg
command is invalid.
System action:
cicssnacfg terminates.
User response:
Retry the command specifying a valid action.
Destination:
stderr
ERZ058169E LOCALLU value must be specified
Explanation:
An action was requested to be performed on a remotelu
resource, but no associated locallu was specified.
System action:
User response:
Retry the command specifying a LOCALLU value.
Destination:
stderr
ERZ058170E LOCALLU and REMOTELU values
must be specified
Explanation:
An action was requested to be performed on a mode
resource, but no associated locallu and remotelu were
specified.
System action:
System action:
User response:
Retry the command specifying LOCALLU and
REMOTELU values.
User response:
valid parameters.
Destination:
stderr
Destination:
stderr
ERZ058171E Configuration file fileName not found
Explanation:
The class specified on the -c option of the cicssnacfg
command is invalid.
Explanation:
cicssnacfg cannot find the specified configuration file.
Either the varDir/cics_sna directory does not contain the
required configuration files, or the region specified on
the -r option does not contain the required configuration
files.
System action:
System action:
User response:
Retry the command specifying a valid class.
User response:
Check the existance of the configuration files and retry
the command.
ERZ058167E Invalid class specified
451
ERZ058172E ERZ058180E
Destination:
stderr
ERZ058172E Internal error in cicssnacfg
Explanation:
cicssnacfg has detected an internal error.
System action:
ERZ058177E Error reading permanent database

configuration files
Explanation:
cicssnacfg has detected an error whilst attempting to
read a configuration file.
System action:
User response:
Contact your support center.
User response:
Check the configuration files and ensure they contain
valid stanza entries and are not empty.
Destination:
stderr
Destination:
stderr
ERZ058173E Unable to access region regionName
ERZ058178E Error occurred during access of

permanent database configuration files
Explanation:
The region name specified on the -r option on the
command line does not exist.
System action:
User response:
Check that the specified region exists, and retry the
command with a valid region name.
Destination:
stderr
ERZ058174E No match found for resource
resourceName in permanent database
Explanation:
cicssnacfg was unable to find a match for the specified
resource in the permanent database.
System action:
User response:
Check the resource name specified, and add to the
permanent database if necessary. Retry the command.
Destination:
stderr
ERZ058176E Invalid attribute attributeName found
in permanent database
Explanation:
An invalid attribute was found in the cicssnacfg
permanent database.
Explanation:
cicssnacfg has detected an error whilst accessing a
configuration file.
System action:
User response:
Check the configuration files and ensure they contain
valid stanza entries and are not empty.
Destination:
stderr
ERZ058179E Duplicate key resourceName found in
configuration file
Explanation:
cicssnacfg has found that the specified resourceName
already exists in a configuration file and cannot be
added.
System action:
User response:
Reissue the command with a resourceName that is not
already defined in the permanent database.
Destination:
stderr
ERZ058180E Bad value attributeValue for attribute
attributeName in className stanza
with key resourceName
System action:
Explanation:
cicssnacfg has found a bad value for attribute
attributeName.
User response:
Amend the invalid attribute and retry the command.
System action:
Destination:
stderr
User response:
Either check the command line string, or check the
configuration file for the specified data.
452
ERZ058181I ERZ058188I
Destination:
stderr
ERZ058181I Response from LU62_SERV for action
actionName is OK
Explanation:
cicssnacfg has performed action actionName
successfully and has received a good response from
the LU62 server.
System action:
cicssnacfg continues.
User response:
No action required.
Destination:
stderr
ERZ058182W Response from LU62_SERV for
action actionName is snaMessage
Explanation:
An error snaMessage was returned by the LU62 server
for action actionName.
System action:
User response:
Look up the description for snaMessage in the
appropriate Digital SNA documentation.
Destination:
stderr
ERZ058183E Error response from LU62_SERV :
snaMessage
Explanation:
An serious error (snaMessage) was returned by the
LU62 server.
System action:
User response:
Look up the description for snaMessage in the
appropriate Digital SNA documentation.
Destination:
stderr
None.
Destination:
stderr
ERZ058185E Must specify a resource name on
command
Explanation:
No resource name was specified on the command line.
System action:
User response:
Reissue the command specifying a resource name.
Destination:
stderr
ERZ058186E System error caused Peer Server
resourceName action failure
Explanation:
cicssnacfg detected an error during communication with
the Peer Server.
System action:
User response:
Investigate Peer Server.
Destination:
stderr
ERZ058187I Peer Server resourceName definition
already exists
Explanation:
There is an existing definition for resourceName in the
Peer Server.
System action:
User response:
None.
Destination:
stderr
ERZ058188I Peer Server resourceName action
succeeded
ERZ058184I Configuring locallu localluName,

remotelu remoteluName and mode
modeName
Explanation:
The action on resourceName at the Peer Server
succeeded.
Explanation:
cicssnacfg is configuring the LU62 server using the
specified lus and mode.
System action:
System action:
User response:
User response:
None.
Destination:
stderr
453
ERZ058189I ERZ058218E
ERZ058189I Peer Server resourceName definition
does not exist
Use the return code to diagnose the problem with SNA.

LU6.2 return codes are documented in the SunLink P2P
LU62 Programmers Guide.
Explanation:
There is no existing definition for resourceName in the
Peer Server.
Destination:
console.msg
System action:
User response:
None.
Destination:
stderr
ERZ058190W Peer Server is remote and cannot be
configured
Explanation:
The Peer Server is not on the local machine and so
cannot be configured with cicssnacfg.
System action:
User response:
Ensure that the remote Peer Server is configured
separately.
Destination:
stderr
ERZ058203E StartType has been specified more
than once
Explanation:
region StartType parameter was supplied more than
once via the -a, -c or -o options.
System action:
None
User response:
Correct the command and retry it.
ERZ058216E SunLink SNA lu62_register_tp

returned ReturnCodeu when attempting
to register a wildcard TP name of *.
Explanation:
CICS attempted to register a transaction program name
with the SunLink SNA PU2.1 Server using the SNA API
lu62_register _tp. This failed with a return code.
System action:
SNA is unavailable for use by CICS. CICS retries to
open the connection to the SNA server and register the
TP every ten seconds.
User response:
Destination:
console.msg
ERZ058217E SunLink SNA lu62_listen returned
ReturnCodeu when attempting to listen
on LU LuName for a wildcard TP
name of *.
Explanation:
CICS attempted to listen on an LU for all incoming TPs
using the SunLink SNA PU2.1 Server with the SNA API
lu62_listen. This failed with a return code.
System action:
open the connection to the SNA server and listen every
ten sec onds.
Destination:
stdout
User response:
ERZ058215E SunLink SNA lu62_open returned

ReturnCodeu (0xReturnCodeX) when
attempting to open LU LuName.
Destination:
console.msg
Explanation:
CICS attempted to open a connection to the SunLink
SNA PU2.1 Server using the SNA API lu62_open. This
failed with a return code.
ERZ058218E U5806 CICS is configured to use

Local SNA but the SunLink SNA
shared library sunlu62.so could not be
loaded.
System action:
open the connection to the SNA server every ten
seconds.
Explanation:
CICS is configured to use Local SNA but the SunLink
SNA shared library sunlu62.so was unable to be loaded.
This probably means that you have not installed
SunLink SNA correctly. There is either a Listener
Definition or a Communications Definition that
references Local SNA.
User response:
454
ERZ058219E ERZ058225E
System action:
User response:
If you want to use Local SNA, install SunLink SNA
correctly. If you do not want to use SNA then remove or
change the definitions that reference Local SNA. CICS
expects to find the SunLink SNA shared library in
/opt/SUNWlu62 or in /opt/SUNWappc or in a directory in
your LD_LIBRARY_PATH.
Destination:
console.msg
ERZ058219E U5807 CICS could not find a
necessary SNA function in the SNA
shared library sunlu62.so.
Explanation:
CICS was unable to find a necessary SNA function in
the SNA shared library sunlu62.so.
System action:
User response:
Install SunLink SNA correctly since it appears to be
corrupted.
Destination:
console.msg
ERZ058220E Free trial period has expired
Explanation:
An attempt was made to acquire a CICS license;
however, this was unsuccessful. Either a license does
not exist, an expiration date has passed, or the license
information was tampered with.
System action:
The program exits with a non-zero return code.
User response:
The trial period has expired; contact your support
organization to buy a copy of CICS for AIX.
Destination:
ERZ058221I The free trial period will expire in days
days
Explanation:
This message informs the caller that the free trial period
expires in a given time.
System action:
None.
User response:
Destination:
stdout or console.msg
ERZ058222E Virtual disk lvName not found

Explanation:
CICS cannot find a virtual disk named lvName in the
/dev/vd directory. This must be created before CICS can
perform the requested task.
System action:
None.
User response:
Create the virtual disk and retry the operation.
Destination:
stderr
ERZ058223E Virtual disk lvName cannot be
accessed by user userId
Explanation:
The virtual disk lvName must be created with read and
write permissions for user userId.
System action:
None.
User response:
Change the permissions for the virtual disk and retry the
operation.
Destination:
stderr
ERZ058224E Virtual disk lvName not found in
system configuration
Explanation:
The virtual disk lvName was not configured by using
dkconfig.
System action:
None.
User response:
Use dkconfig to configure the virtual disk and retry the
operation.
Destination:
stderr
ERZ058225E Unable to contact the TRANSIT
server. Primary return code returnCode,
secondary return code errorNumber.
Explanation:
CICS was unable to issue the TRANSIT API command
receive_allocate. returnCode represents the TRANSIT
primary return code and errorNumber the secondary
return code.
System action:
CICS does not accept incoming conversation requests
using local SNA. Incoming requests are abnormally
terminated.
User response:
455
ERZ058226E ERZ058230E
Refer to the TRANSIT manuals for an explanation of
primary and secondary return codes. Correct the
TRANSIT server problem.
Destination:
console.msg
ERZ058226E CICS is unable to load SNA library
libraryName. Abending region.
libraryName
environment variable
wappc32.dll
winnof32.dll
CICS_SNA_APPC_LIBRARY
CICS_SNA_ATTACH_LIBRARY
These environment variables can be set in either the

regions environment file, or in the NT environment.
They can be set to the filename of the library or the full
path name.
Explanation:
CICS was unable to load the SNA library libraryName.
This is required for local SNA. Local SNA was activated
by the presence of a Listener Definition (LD) entry with
Protocol=SNA in the region database.
When the configuration is complete, restart your region.
System action:
CICS abnormally terminates the region with abend
U5808.
ERZ058228E Additional errors occurred but are not

reported.
User response:
Refer to the CICS on Open Systems
Intercommunications Guide and either install the SNA
communications product or remove all entries from the
LD with Protocol=SNA.
Destination:
console.msg
ERZ058227E
Explanation:
System action:
None
User response:
diagnose why the program load was unsuccessful.
CICS is unable to load SNA library

libraryName. Abending region.
Explanation:
CICS was unable to load the SNA library libraryName.
This library is provided by a SNA product rather than
CICS. It is required for local SNA support. Local SNA
was activated by CICS because a Listener Definition
(LD) entry with Protocol=SNA appears in the region
database.
System action:
CICS abnormally terminates the region with abend
U5808.
User response:
Guide describes what local SNA is and how to configure
it.
If your region does not need local SNA, remove all
entries from the LD with Protocol=SNA.
If local SNA is required, ensure a SNA product
supported by CICS is installed on your machine. Usually
the SNA product copies its libraries into the standard
directory (for example C:WINNT35system32) so your
region can locate them. If the libraries are not copied to
this directory, ensure the directory where they reside is
listed in your regions PATH.
If necessary, the name of the SNA library used by CICS
can be changed by setting the appropriate environment
variable:
456
Destination:
console.msg
Destination:
ERZ058229E System error - error data is:
errorMessage
Explanation:
System action:
None
User response:
Destination:
ERZ058230E Local LU LUname is configured for
synchronization level 2
Explanation:
The CICS local SNA support has received a 0x06F2
transaction request from a remote system. This
transaction is used by two synchronization level 2
enabled systems when they connect to one another. As
local SNA does not support synchronization level 2,
CICS does not expect to receive a 0x06F2 transaction
request.
ERZ058231E
The most common reason that the remote system has
sent an 0x06F2 transaction request is because SNA
indicated in the bind request, which starts a session to
the remote system, that the local logical unit (LU)
LUname supported synchronization level 2. IBM
Communications Server for AIX does this if the local LU
name LUname is configured with the Recovery resource
manager (RRM) enabled.
Alternatively, CICS can receive the 0x06F2 transaction
request if the remote system is using a PPC gateway
server. The PPC gateway server can not examine the
bind request and so uses the 0x06F2 transaction
request to determine if the remote system supports
synchronization level 2.
System action:
CICS abnormally terminates the 0x06F2 transaction
which prevents any synclevel 2 intersystem requests
from being sent by the remote system.
User response:
To change the configuration in IBM Communications
Server for AIX so that LUname does not have the
Recovery resource manager (RRM) enabled.
v Log into AIX as the root user and enter:
smitty _snalocalu6ch
v Type in the name of the profile that was created for
LUname. Normally this is the same name as
LUname. You can use the F4 key to list the profiles
defined.
v Press enter to display the Change/Show LU 6.2 Local
LU Profile panel with the configuration for LU
LUname.
v Move the cursor down to the Recovery resource
manager (RRM) enabled? option and using F4, change
the setting to no. Press the enter key twice so that a
message is displayed saying the profile was
changed.
v Press F10 to return to AIX and enter the verifysna -R
command. This activates your change to the local LU
profile.
v Finally, stop and restart IBM Communications Server
for AIX so that the altered definition is used by CICS.
(See TXSeries for Multiplatforms Using IBM
Communications Server for AIX with CICS for
information on controlling IBM Communications
Server for AIX.)
If you need further information on configuring CICS and
IBM Communications Server for AIX, refer to the
Destination:
console.msg
ERZ058231E
Local LU LUname is in use by

another process
Explanation:
Server for AIX using local logical unit (LU) name
LUname. This local LU name is configured in the
entry for your region. Possible reasons that CICS is not
able to use this LU name include:
v It matches the GatewayLUName attribute of a
Gateway Definition (GD) entry.
v The GatewayLUName attribute of a GD entry is .
This means it defaults to the value in the
LocalLUName attribute of the RD entry.
which is also using local LU name LUname.
v The IBM Communications Server for AIX side
information profile called LUname does not have the
local LU alias set to LUname.
v The IBM Communications Server for AIX local LU
profile for LU LUname does not have the local LU
alias set to LUname.
System action:
CICS processing continues. However, until this problem
is resolved, CICS can not receive incoming intersystem
requests using local SNA.
User response:
If local SNA support is not required, remove all Listener
Definitions (LD) entries that have Protocol=SNA from
your region database and then restart your region.
Otherwise:
v Check the IBM Communications Server for AIX
configuration for LUname. Log on as the root user
and type smitty _snaLU62. This displays the LU 6.2
configuration panel. Check, and if necessary correct,
the Local LU and Side Information profiles for
LUname. The TXSeries for Multiplatforms Using IBM
Communications Server for AIX with CICS explains
how to set up these profiles.
v Examine the CICS messages written to your regions
console.msg file as CICS logs messages if the LU
names used by your region conflict. If messages are
logged, follow the instructions for these messages.
v Check there is no other CICS region, PPC gateway
server or SNA application running that is using
LUname as the local LU name. You can view the
local LU names being used by a PPC gateway server
with the ppcadmin list luentries command. Refer to
Guide for more information on this command. If
another process is using LUname as the local LU
name, either:
change the LU name used by your region and
restart CICS, or
terminate the other process or
change the LU name used by the other process.
457
ERZ058232E ERZ058235W
Note: If you change the LU name(s) used by your
CICS region, check that all the remote systems
that contact your CICS region are also updated
with the new LU name(s). Also, if you change the
LU name used by a PPC gateway server, then
ensure the configuration for the old local LU
name is removed from the PPC gateway using
the ppcadmin delete luentry command.
CICS tries to reconnect to IBM Communications Server

for AIX every ten seconds. Until it is successful, CICS is
not able to receive intersystem requests using local
SNA.
User response:
Destination:
console.msg
v Check to see if an IBM Communications Server for

AIX LU6.2 Side Information profile is defined. The
TXSeries for Multiplatforms Using IBM
Communications Server for AIX with CICS explains
how to set up this profile.
ERZ058232E IBM Communications Server for AIX

register subsystem operation returned
v Check that all IBM Communications Server for AIX

configuration is copied into IBM Communications
Server for AIXs runtime database by issuing the
verifysna -R command.
Explanation:
Server for AIX in order to receive inbound intersystem
requests over SNA. errorNumber is the error number
(errno) returned to CICS by AIX on the
ioctl(REGISTER_SUBSYSTEM) system call. This
problem is possibly caused because:
Destination:
console.msg
Explanation:
Error number errorNumber returned from an internal
cross process (ComSU_XP) call. This error is not
expected by CICS.
v The system resources required to complete the

system call are not available.
System action:
requests from remote SNA systems can fail.
User response:
AIX SNA link stations and CICS reconnects to SNA.
If the SNA subsystem is running, refer to the IBM
Communications Server for AIX manuals for an
explanation of the error number and the action required
to solve the problem.

was received from cross process
services
System action:
User response:
This error represents a failure to use cross process
communication within CICS while dealing with an
incomming Local SNA transaction. This message is
issued by components involved with the CICSSL
process. Record the full text of the message and its
RSN number and contact your support organization.
Destination:
console.msg
Destination:
console.msg
ERZ058235W Invalid data at line lineNumber in

iconv-emulation data file %2$s
ERZ058233E A Side Information profile called

LUname must be defined in IBM
Explanation:
During region initialization the CICS iconv-emulation
code encountered an invalid definition at the specified
line number within the specified data file.
Explanation:
Server for AIX in order to receive intersystem requests
over SNA. This is because a LU6.2 Side Information
profile for your region is not available in IBM
Communications Server for AIXs runtime database.
This profile must be called LUname, which is the local
logical unit (LU) name configured in the LocalLUName
attribute of the Region Definition (RD) entry. (If the
LocalLUName attribute is null (), it defaults to the
name of the CICS region.)
System action:
458
System action:
CICS continues, but it is possible that data conversion
between different code pages do not work as required.
User response:
If the data identified as invalid is needed for data
conversion to work as required, correct the invalid data
within the specified file and restart CICS.
Destination:
console.msg
ERZ058236E ERZ058242E
ERZ058236E CCSID for system codeset codeSet
not found in iconv-emulation data file
%2$s
Explanation:
code was unable to find the CCSID that corresponds to
the specifed default system codeset in the specified file.
None
User response:
Destination:
System action:
ERZ058240E Relocation entry number entryNumber

is defective in library libraryName
User response:
Ensure that the specified file contains an entry for the
CCSID that corresponds to the default system codeset
and restart CICS.
Explanation:
Destination:
console.msg
System action:
None
ERZ058237E Insufficient permission to add shared

object libraryName to loader domain
domainName
Explanation:
System action:
None
User response:
Destination:
ERZ058238E Cannot load library libraryName
Explanation:
System action:
None
User response:
Destination:
ERZ058239E Symbol symbolName in library
libraryName is not defined
Explanation:
User response:
Destination:
ERZ058241E The libraryName is not executable or
not in correct XCOFF format
Explanation:
System action:
None
User response:
Destination:
ERZ058242E System error: errorMessage
Explanation:
System action:
None
User response:
Destination:
System action:
459
ERZ058243E ERZ058304E
ERZ058243E Member libraryName is not found or
file is not an archive
Explanation:
System action:
None
User response:
Destination:
ERZ058244E Symbol symbolName used in
libraryName does not match exported
type
Explanation:
System action:
None
User response:
Destination:
ERZ058245E Alignment of text does not match
required alignment
Explanation:
System action:
None
User response:
Destination:
ERZ058301I Checking your DCE login status
Explanation:
Checks are being performed to ensure that you are
DCE logged in as the DCE principal cell_admin and that
your login has not expired.
System action:
None
User response:
If this check fails, first make sure that you are in fact
DCE logged in, then use klist to make sure that your
credentials have not expired.
Destination:
stdout
ERZ058303E Region regionName contains SFS
server serverName, not serverName
as specified
Explanation:
The region that was specified in the command already
exists and contains the location of the SFS. You cannot
redefine the location of the SFS once the region is
created.
System action:
None
User response:
Retry the command without specifying the name of the
SFS. It is taken from the Region definition. If the region
exists but the server does not, use the -f option to force
the creation of the SFS for the region.
Destination:
stderr
User response:
ERZ058304E The name resourceName is longer

than 8 chars, please select another
name
Destination:
Explanation:
The naming convention restricts the lengths of the
names you can supply for the region and the SFS to 8
characters in length.
ERZ058246E Insufficient permission to create

loader domain domainName
Explanation:
System action:
None
460
System action:
None
User response:
Select a shorter name.
Destination:
stderr
ERZ058306E ERZ058312I
ERZ058306E The Region cannot have the same
name as its server
Explanation:
The name of the region cannot be the same as an
existing server. This leads to naming collisions when the
logical volumes are created later in the installation
process.
System action:
None
User response:
Select a unique name.
Destination:
stderr
ERZ058307E The user cics is not a member of both
the cics and cicsterm groups
Explanation:
Checks are made to ensure that the user cics is a
member of both the groups cics and cicsterm. If this is
not the case, the command attempts to make cics part
of the group cics and cicsterm. If this fails, this error is
generated.
System action:
None
User response:
Add the user cics to the groups cics and cicsterm.
Destination:
stderr
ERZ058308E Server user check failed. serverName
must be in the group cics
Explanation:
After the userid for the SFS is created, it is checked to
ensure it is a member of the group cics.
System action:
None
User response:
Find out why the userid was unable to be added to the
group cics. Make it a member of the group cics and
retry the command.
Destination:
stderr
ERZ058309E Your user had to be added to groups
cics and cicsterm. You must log in
again
Explanation:
Your login user was found not to be a member of the
groups cics and cicsterm. The configuration process
requires that you are a member of these groups and
you are made a member of them. In order for this

change to take effect you must log out then log in
again.
System action:
None
User response:
Logout then login again. Retry the command.
Destination:
stderr
ERZ058310E Unable to create lvolSize MB volume
lvolName in volume group volumeGroup
Explanation:
An error occurred during the creation of a logical
volume. Refer to previous messages for more details of
the error condition. Typically this is caused by a lack of
space in the volume group. A different volume group
can be specified by using the environment variables
CICS_LOG_VG and CICS_SFS_VG which control the
placement of the logical volumes.
System action:
None
User response:
Correct the problem preventing the logical volume
creation. Ensure that everything is cleaned up from the
failed attempt to create the logical volume.
Destination:
stderr
ERZ058311I Removed lock file lockFile for
resourceType resourceName
Explanation:
The lock file for the resource specified was removed.
System action:
None
User response:
None
Destination:
stdout
ERZ058312I Creating the resourceType
resourceName
Explanation:
The resource named is about to be created.
System action:
None
User response:
None
Destination:
stdout
461
ERZ058314I ERZ058321I
ERZ058314I Starting the resourceType resourceName
Explanation:
The resource named is about to be started.
System action:
None
User response:
None
Destination:
stdout
ERZ058315I Configuring the SFS files for Region
regionName on SFS server SFSserver
Explanation:
The SFS files required for the region are about to be
created on the SFS. These files possibly already exist,
in which case error messages from SFS are received
and can be ignored.
System action:
None
User response:
None
ERZ058318E An effective id of root is required for

this command
Explanation:
with root privileges.
System action:
None
User response:
Log in as root and retry the command.
Destination:
stderr
ERZ058319E Either not DCE logged in as
cell_admin or credentials expired
Explanation:
For successful execution of the configuration command,
you must be logged in to the DCE. DCE logins expire
after a time interval determined in the DCE cell
configuration.
System action:
None
Destination:
stdout
User response:
Use the utility klist to determine your current DCE login
status. Log in to the DCE again.
ERZ058316E Option optionName requires a value
Destination:
stderr
Explanation:
Some of the options require a value. Refer to the usage
message for more information.
System action:
None
User response:
Refer to the usage message for more details.
Destination:
stderr
ERZ058317E Additional parameters parameters
specified at end of command
Explanation:
More parameters were specified than are required.
System action:
None
ERZ058320I Kernel Parm Cur Value Rec Value

Comments
Explanation:
Header line for the option that shows the value of some
Kernel parameters known to impact CICS.
System action:
None
User response:
None
Destination:
stdout
ERZ058321I Retrieving the parameter values from
the Kernel kernelFileName
User response:
Remove extraneous parameters from the command.
Explanation:
The values of the relevant kernel parameters are being
retrieved from the kernel file shown.
Destination:
stderr
System action:
None
User response:
None
Destination:
stdout
462
ERZ058322E ERZ058330I
ERZ058322E Kernel parameter kernelParameter not
found by grep in Kernel file
kernelFileName
Explanation:
The parameter shown was unable to be found in the
kernel. This is not a serious situation and does not
indicate that anything is amiss.
System action:
None
User response:
Use SAM to check the value of the kernel parameter.
Destination:
stderr
ERZ058324I Usage: cicsautodestroy { -? | -b | [-v]
[-y] { [-r regionName] [-s SFSserver] | {
-d -r regionName | -d -s SFSserver }}}
Explanation:
System action:
None
System action:
None
User response:
Respond yes to have the region or server stopped for
you.
Destination:
stdout
ERZ058328W The subsystemType subsystemName
will not be stopped and hence cannot
be destroyed
Explanation:
You chose not to stop an active server or region, so it
was not stopped. cicsautodestroy can only destroy
inactive servers or regions and moves on to the next
item to be destroyed.
System action:
The attempt to destroy the region or server is
abandoned.
User response:
None
Destination:
stdout
User response:
If the message was issued as a result of a syntax error,
ERZ058329E The subsystemType subsystemName

could not be stopped
Destination:
stdout
Explanation:
Attempts by cicsautodestroy to stop the region or server
to be destroyed were unsuccessful.
ERZ058326W The subsystemType subsystemName is

currently active. It must be stopped
before it can be destroyed.
Explanation:
Before a region or server can be destroyed, it must first
be stopped. cicsautodestroy has detected that the
specified region or server is running.
System action:
None
User response:
You are prompted to see if you wish to stop the region
or server that is to be destroyed.
Destination:
stdout
ERZ058327I Stop the subsystemType
subsystemName ?
Explanation:
The region or server you are attempting to destroy is
currently running. Before it can be destroyed, it must be
stopped. If you respond in the affirmative,
cicsautodestroy performs the stop for you.
System action:
None
User response:
Examine the output to find why the region or server was
unable to be stopped. Try stopping the region or server
manually to see what errors occur. If all else fails, use
kill to stop the server or region.
Destination:
stderr
ERZ058330I Testing if the server is running for
region regionName
Explanation:
When destroying a region, the SFS files for that region
are also removed. Before attempting to remove them,
the SFS is pinged. If the SFS is not running, you must
wait while each of seven file deletion attempts times
out. By doing an initial ping this waiting time can be
reduced.
System action:
None
User response:
None
463
ERZ058331I ERZ058336I
Destination:
stdout
ERZ058331I Destroy the subsystemType
subsystemName ?
Explanation:
This is your last chance to cancel the deletion of a
server or region. Answering no to this prompt prevents
this region or server from being destroyed.
System action:
A negative answer prevents the region or server from
being destroyed.
User response:
Answer yes to continue and destroy the region or
server.
Destination:
stdout
ERZ058332W This looks like it may be a remote
subsystemType
Explanation:
In the case of a region this means that the region
directory, cicssrcdb entry and region archive directory
are missing. It is possible that the region does not exist
or that is does exist on another system. It is still
possible to proceed with the destroy operation but you
can potentially damage DCE entries for the region on
another system within your DCE cell.
System action:
None
User response:
Check the region name entered. If that is correct and
you are sure that the region does not exist elsewhere in
the cell then, when you are prompted to continue with
the destroy, answer in the affirmative.
Destination:
stdout
ERZ058333I Potentially a remote subsystemType.
Destroy subsystemType subsystemName
?
Explanation:
The region has no region directory, cicssrcdb entry, or
region archive directory, which possibly indicates that
the region either does not exist or exists on a different
machine within your DCE cell. You can continue with
the destroy operation but, if this is a remote region, the
DCE entries for this region are removed, which is not
what you want for a remote region.
System action:
A region directory is created if you respond yes, and the
destroy operation proceeds.
User response:
464
Respond yes to continue with the destroy operation.

Destination:
stdout
ERZ058334W This could be a remote serverType
server since only the entryType entry
found
Explanation:
When a server is being accessed on a remote system,
the local system has just an SSD entry for the remote
server and no cicssrcdb entry. The server being
destroyed matches that profile and this is to alert the
user. Tests later in the destroy determine whether or not
the server is running remotely and stop the destroy
operation. However, if the server is remote and is not
running, the destroy proceeds and removes the DCE
information and the SSD entry for the remote server.
System action:
None
User response:
None
Destination:
stdout
ERZ058335E The subsystemType subsystemName is
running remotely, cannot be destroyed.
Explanation:
A ping of the server has determined that it is running
remotely. The server cannot be destroyed.
System action:
The destroy operation for this server is abandoned.
User response:
To destroy this server, go to the servers system and
perform the destroy operation there.
Destination:
stderr
ERZ058336I Destroying the subsystemType
subsystemName
Explanation:
The destroy operation is proceeding for the region or
server.
System action:
The region or server is destroyed.
User response:
None
Destination:
stdout
ERZ058337I ERZ058343E
ERZ058337I Removing the Logical Volume lvolName
from volume group volumeGroup
ERZ058341W Unable to remove SFS logical volume

lvolName because it is open
Explanation:
The logical volume is being removed from the volume
group.
Explanation:
The SFS server has one of its logical volumes open.
This prevents the volume from being removed. Logical
volumes such as this are remembered until the end of
the command, when a last attempt is made to remove
them in case the volume was closed in the meantime.
System action:
None
User response:
None
Destination:
stdout
ERZ058338E Unable to map the short serverType
name serverName to a long name
Explanation:
There is not enough of the server remaining to map the
short name to the long name. In the case where both
the cicssrcdb entry and the stanza entry are missing for
the server very little can be done. Bear in mind that this
is possibly a server running on a remote system.
System action:
Abandon the destroy operation.
User response:
If you know the long name of the server, retry the
command using that name. In this situation,
cicsautodestroy removes any DCE entries and
directories associated with the server, after asking.
System action:
Remember the logical volume for a further removal
attempt at the end of the command.
User response:
None
Destination:
stdout
ERZ058342E cicsname unable to access the region
directory for region regionName
Explanation:
An error was returned by cicsname after executing
cicsname -r regionName regiondbase.
System action:
The command terminates since this a fundamental
problem that must be resolved before the destroy can
continue.
User response:
Find out why cicsname is returning an error.
Destination:
stderr
Destination:
stderr
ERZ058339W No cicssrcdb or stanza entry found

for the serverType serverName
ERZ058343E Unable to access the stanza file

stanzaFile
Explanation:
No cicssrcdb or SSD entry was able to found for the
server whose name you specified. This possibly means
that the server does not exist or that you wish really
make sure that the server is destroyed. In the latter
case, proceeding with the destroy operation removes
any server directories and removes any references to
this server in DCE. This is a dangerous option if the
server is remote.
Explanation:
There is no stanza file for the region. When trying to
establish dependency lists of servers the stanza file is
pivotal. To destroy this region, if it exists, retry the
command without the -d option, which performs a
directed destroy of that region and not try to establish
dependencies.
System action:
None
User response:
None
Destination:
stdout
System action:
continue.
User response:
Retry the command without the -d option in order to
destroy this region.
Destination:
stderr
465
ERZ058344I ERZ058353W
ERZ058344I Building the lists of servers to be
destroyed
Explanation:
The regions dependent servers are being found.
System action:
None
User response:
None
Destination:
stdout
ERZ058345E Error while retrieving server
information from region stanza
Explanation:
An error occurred while retrieving server information
from the region stanza file. Cannot build the list of
dependent servers.
System action:
continue. A directed destroy, without the -d option, can
be performed on this region.
User response:
Examine the messages to determine why you have an
error retrieving information from the region stanza. A
directed destroy, without the -d option, can be
performed on this region.
Destination:
stderr
ERZ058348I Remove serverType server serverName
from list of servers to be destroyed ?
Explanation:
The server listed was found to be a dependent server of
another region that is not going to be destroyed.
Destroying this server leaves that region or server
inoperable until it is bound to another server. Refer to
the previous message to determine which region is
impacted if this server is destroyed.
System action:
None
User response:
Respond yes to remove this server from the list of
servers that are to be destroyed.
Destination:
stdout
ERZ058349W Region regionName is using
serverType server serverName which is
going to be destroyed
Explanation:
466
After building the list of servers to be destroyed, a

check is made to try to ensure that there no regions are
left without an SFS. You can still destroy the SFS server
listed in the message but be aware that the region listed
cannot be started without rebinding to another SFS
server.
System action:
None
User response:
None
Destination:
stdout
ERZ058350I These are the SFS server(s) which will
be destroyed:
Explanation:
This is an informational message that precedes the list
of servers that are going to be destroyed. You are
prompted for approval prior to the destruction of each
server unless you have chosen the automatic YES
option.
System action:
None
User response:
None
Destination:
stdout
ERZ058352E You must specify a server, a region or
both.
Explanation:
Unlike cicsautoconf, this command does not default any
server names. In the case of a directed destroy (without
the -d option) you must specify the name of a region or
the name of an SFS or both. The region and server do
not have to be related in any way. With a dependent
destroy, just specify the top of the dependent tree and
everything below is destroyed.
System action:
The command terminates after this error.
User response:
Retry the command specifying a region or server.
Destination:
stderr
ERZ058353W Dependencies taken from highest
level, ignoring lower levels.
Explanation:
When performing a dependent destroy, the highest level
in the dependency tree is used. A region is the highest
level and any SFS specified in the command line is
ERZ058354E ERZ058403E
ignored if a region is specified. The region is highest
because it has a dependent SFS. Below the region is
the SFS.
System action:
None
User response:
None
Destination:
stdout
ERZ058354E The volume lvolName is already in use
elsewhere, name collision with existing
region or server.
Explanation:
A check is made that looks into the stanzas for the
existing regions and servers. The check found a logical
volume of the same name in use already by an existing
region or server.
System action:
The command terminates after this error.
User response:
Select a different name for the server or track down the
duplicate volume and remove that server and the
offending volume.
Destination:
stdout
ERZ058355W Volume lvolName already exists but it
is actualSize MB instead of defaultSize
MB
User response:
Refer to preceding and subsequent messages for an
indication why this happened. Additionally, have the
system administrator investigate the disappearance of
the process. For example, a force purge of a transaction
has this effect.
Destination:
console.msg
CICS iconv-emulation
Explanation:
code was unable to obtain sufficient storage from the
Region Pool to initialize correctly.
System action:
User response:
Destination:
console.msg
ERZ058402E Error response retCode from NT
Registry during initialization of
iconv-emulation
Explanation:
code received an error response from the NT Registry.
Explanation:
The logical volume to be created already exists but the
size differs from the default size.
System action:
System action:
None
User response:
Check the NT response code in the appropriate
Microsoft Win32 manual.
User response:
Check the volume and, if necessary, destroy the server
and the logical volume, then retry the command.
Destination:
console.msg
Destination:
stdout
ERZ058400E Abnormal termination U58400: A
crucial mutual exclusion lock at
address lockAddress is held by a
terminated process
Explanation:
In order to maintain integrity of data structures CICS
uses a mutual exclusion locking scheme; a process has
terminated without releasing its exclusive hold on a
resource lock.
System action:
The region is abnormally terminated with code U58400.
ERZ058403E Iconv-emulation data file fileName

could not be found.
Explanation:
During region initialization, the CICS iconv-emulation
code was unable to find the specified file.
System action:
User response:
Ensure that the specified file does exist and is in the
expected directory.
Destination:
console.msg
467
ERZ058404E ERZ058410E
ERZ058404E cicscp failed to create a new process,
error number is errorNumber
Explanation:
This message is output if cicscp detects an error when
attempting to create a new process.
Explanation:
The lock file fileName cannot be created.
Accompanying messages can possibly identify the exact
System action:
The command fails.
System action:
Command abnormally terminates.
User response:
Retry the command. If it still fails then a user resource
limit or a system resource limit was possibly reached.
On UNIX, consult the operating system documentation
for fork() and check the conditions for the errorNumber
value. On Windows NT, Check the errorNumber value in
the appropriate Microsoft Win32 manual.
User response:
Check that you have permission to create files in the
directories in fileName and that they are available: See
accompanying messages for further information. Correct
the problem and retry the command. Ensure that the file
system is not full.
Destination:
stderr
Destination:
stderr
ERZ058405E The program programName failed to

execute, error number is errorNumber
Explanation:
This message is output if an error is detected when
executing the program.
System action:
The command fails.
User response:
for the execvp() function and check the conditions for
the errorNumber value. On Windows NT, Check the
errorNumber value in the appropriate Microsoft Win32
manual.
Destination:
stderr
ERZ058406E The function of stream failed with
Explanation:
manipulating the standard I/O streams during the
creation of a sub-process.
System action:
The command fails.
User response:
Retry the command. If it still fails then a system
resource limit was possibly reached. Consult the
operating system documentation for the appropriate
function and check the conditions for the errorNumber
value.
Destination:
stderr
468
Explanation:
System action:
User response:
None
Destination:
stderr
Explanation:
problem.
System action:
User response:
directories in fileName and that they are available: See
accompanying messages for further information. Correct
the problem and retry the command.
Destination:
stderr
Explanation:
possibly mean that the server is currently running, or
some other command or process is administering the
server definitions, or the lock was taken by a command
ERZ058411E ERZ058416I
or process that subsequently terminated abnormally,
System action:
User response:
Destination:
stderr
ERZ058411E Win32 API call function failed with
error errorNumber in service
serviceName
Explanation:
During processing of the specified NT service, a Win32
function call failed. This is an abnormal situation, but the
service possibly continues processing.
System action:
The service terminates if it cannot continue due to the
error.
User response:
Attempt to determine the reason for the call failure by
examining the error code. Collect any diagnostics and
Destination:
Windows NT Event Log
ERZ058412E Service serviceName cannot find
associated entry in NT Registry
Explanation:
The service cannot find the associated entry in the NT
Registry that was supposed to be added during the
creation of the region or server. This means that the NT
Registry entries and the NT Service entries are out of
step.
System action:
The service terminates.
User response:
Try to recreate the region or server and check for any
errors that occur during the creation that indicate that
information was not written to the NT Registry. Ensure
that the userid being used has access to the NT
Registry. If after recreating the region or server, the
error does not occur, then it is possible that the NT
Registry was corrupted.
Destination:
ERZ058413I Service serviceName has started

successfully.
Explanation:
The service has successfully started the region or
server.
System action:
The region or server is running.
User response:
None.
Destination:
ERZ058414I Service serviceName has stopped
successfully.
Explanation:
The service has successfully shutdown the region or
server.
System action:
The region or server has stopped.
User response:
None.
Destination:
ERZ058415E Service serviceName must be
controlled using CICS commands or
GUI.
Explanation:
An attempt was made to start or stop the service from
an unsupported application.
System action:
The service status does not change.
User response:
Use the CICS-supplied commands or the GUI to control
the service.
Destination:
ERZ058416I The CICS telnet server telnetServer
has started successfully
Explanation:
The telnet server has started and is ready to accept
incoming telnet requests.
System action:
The telnet server is running
User response:
None.
Destination:
469
ERZ058417I ERZ058430I
ERZ058417I The CICS telnet server telnetServer
has stopped successfully
Explanation:
The telnet server has stopped.
System action:
The telnet server has stopped.
User response:
None.
Destination:
ERZ058418E The CICS telnet server telnetServer
has stopped due to an error
Explanation:
An unexpected error has occurred.
System action:
The telnet server terminates.
User response:
Use the cicscp destroy telnet_server and cicscp create
telnet_server commands to recreate the telnet server. If
the telnet server fails to start collect any diagnostics and
Destination:
ERZ058419W The CICS telnet server telnetServer
is already running
Explanation:
An attempt was made to start a telnet server that is
already running.
System action:
The existing telnet server continues.
User response:
If you wish to stop the existing telnet server use the
cicscp destroy telnet_server command.
Destination:
to recreate the telnet server. If the telnet server fails to

start collect any diagnostics and contact your support
organization.
Destination:
ERZ058421W Region regionName has been
forcibly terminated
Explanation:
The CICS region regionName terminated forcibly under
user control. The user issued a cicsstop -k <region>
command to cancel the region.
System action:
Any remaining processes associated with the region are
terminated and the region lock file is removed.
User response:
None.
Destination:
console.msg and Windows NT Event Log
ERZ058422W Server serverName has ended
unexpectedly
Explanation:
The SFS serverName has ended without completing
the normal shutdown procedure. This is either caused
by the SFS terminating abnormally or by a user issuing
a tkadmin stop server command to shut down the SFS.
System action:
None.
User response:
If the SFS terminated abnormally, then use the SFS
message file and try to determine the cause of the
termination. If the SFS was shut down by a tkadmin
stop server command then no further action is required.
Destination:
ERZ058430I Usage: cicstail -? | [-r regionName | -f
inFile] [-b numBytes]
ERZ058420E Win32 API call function failed with

error errorNumber in telnet server
telnetServer
Explanation:
Describes the options available on the cicstail
command. This message is issued in response to -? or
as a result of syntactically invalid request.
Explanation:
During processing of the specified telnet server, a
Win32 function call failed.
System action:
None.
System action:
The telnet server terminates.
User response:
If the message was issued as the result of an error,
User response:
Attempt to determine the reason for the call failure by
examining the error code. Use the cicscp destroy
telnet_server and cicscp create telnet_server commands
470
Destination:
stdout
ERZ058431E ERZ058452E
ERZ058431E regionName is not a valid region
name
Explanation:
The user has issued a cicstail command, but the name
supplied is not the name of a valid region.
System action:
None.
User response:
Destination:
stdout
User response:
First look at the other messages issued by CICS, as
they show which transaction issued the request and can
possibly indicate why the request was unsuccessful. If
the CICS messages do not help you solve the problem,
look up the primaryRC response in the application
programming manual for your SNA product. Finally, if
you can not solve the problem yourself, contact your
Destination:
console.msg
ERZ058451E
ERZ058432E No region name has been specified

Explanation:
The user has issued a cicstail command, but did not
specify the name of the region to be used.
System action:
None.
User response:
Destination:
stdout
ERZ058433E fileName file does not exist or is not
readable
Explanation:
The specified file fileName does not exist, or it cannot
be read.
System action:
None.
User response:
Retry the command specifying a valid file name, or
make the specified file available.
Destination:
stdout
ERZ058450E
SNA returned primaryRC from an

APPC verb call
Explanation:
CICS issued an Advanced Program to Program
Communication (APPC) verb call to your SNA product
as part of a local SNA intersystem request. This APPC
call returned with the primaryRC response.
Note: The primaryRC and secondaryRC values are
displayed by CICS as hexadecimal numbers in
the local machine byte-order.
System action:
Further messages can be logged either to the
console.msg or the CSMT log.
SNA abnormally terminated during

an APPC verb call with return code
primaryRC
Explanation:
request returned with the primaryRC response which
normally means your SNA product is not running.
Note: The verb and primaryRC values are displayed by
CICS as hexadecimal numbers in the local
machine byte-order.
System action:
Further messages can be logged either to the
User response:
First check that your SNA product is running. If it is not,
check the message logs for the SNA product for error
messages that can possibly indicate why the SNA
product is not running. Restart your SNA product.
To determine which CICS requests were unsuccessful
as a result of this error, look for other messages issued
by CICS at the same time as this message. These
document which transaction(s) were affected and the
consequences.
If you need more information, look up the primaryRC
response in the application programming manual for
your SNA product. Alternatively, use the problem
determination information provided with your SNA
product.
Destination:
console.msg
ERZ058452E

APPC verb call because there are
insufficient system resources to
continue
Explanation:
471
ERZ058453E ERZ058455E
call returned with the primaryRC response which
indicates your machine is short of system resources.
System action:
CICS abnormally terminates the SNA intersystem
request. Further messages can be logged either to the
User response:
To determine which CICS requests were unsuccessful
as a result of this error, look for other messages issued
by CICS at the same time as this message. These
document which transaction(s) were affected and the
consequences.
Look up the primaryRC response in the application
programming manual for your SNA product. Also look
for errors reported in the message log used by your
SNA product and also the local NT system and
application logs. Alternatively, run a performance
monitor on your system to determine which resources
are running out.
Destination:
console.msg
ERZ058453E

APPC verb call because a SNA
component could not be loaded
Explanation:
request returned with the primaryRC response. This
response can indicate that your SNA product:
v is not installed,
v is not configured correctly, or
v is not running.
System action:
User response:
First ensure that your SNA product is running and
correctly configured. Then look for other CICS error
messages in the console.msg concerning local SNA and
follow the instructions for these messages. Finally,
check the message log of your local SNA product and
use the SNA product documentation to track down any
recorded problems.
Once you have corrected the local SNA environment,

rerun the intersystem request.
Destination:
console.msg
ERZ058454E The local LU alias alias has not been
defined in your SNA product
Explanation:
In order to use local SNA, your CICS region requires a
unique name in the SNA network. This name is called
the local Logical Unit (LU) name. This local LU name is
configured in the LocalLUName attribute of your
regions Region Definition (RD) entry.
When CICS calls the SNA product, it passes an alias, or
nickname for the local LU name. Your region is using an
alias called alias. However, this alias is not defined in
your SNA product so SNA can not identify your region.
The local LU alias defaults to the same name as your
local LU name. This can be changed using an
environment variable beginning CICS_SNA_LUALIAS.
For example, if LocalLUName is set to MYLU and the
local LU alias is supposed to be MYALIAS, then the
environment variable is
CICS_SNA_LUALIAS_MYLU=MYALIAS. Environment
variables can be set in your regions environment file, or
in the NT environment for either the regions userid, or
the system as a whole.
Whatever the value of the local LU alias you wish to
use, it must be entered in the definition of your regions
local LU name in your SNA product.
System action:
CICS abnormally terminates intersystem requests.
User response:
Look at the definition of your regions local LU name in
the SNA product and either change this definition to
match the values used by CICS, or change CICS to
match your SNA definitions.
If your definitions appear correct, make sure they are
loaded into your SNA product.
Destination:
console.msg
ERZ058455E Unable to start a new local SNA
intersystem request
Explanation:
CICS is unable to start a new local SNA intersystem
request because the number of running intersystem
requests ronment for either the regions userid, or the
system as a whole.
in the CICS process exceeds the maximum allowed by
your SNA product.
472
ERZ058456E ERZ058459E
The response returned by the SNA product was
AP_TOO_MANY_TPS. CICS uses a new TP for:
v Each DTP conversation.
v Each transaction routing request sent to a SYSID not
previously accessed by the local transaction.
v Each function shipping, DPL or Asynchronous
processing request sent to a SYSID not previously
accessed by the local transaction.
v An inbound intersystem request that starts a new
CICS transaction.
System action:
User response:
Look up the AP_TOO_MANY_TPS response in your
SNA products APPC programming manual to find out
what the maximum number of TPs are. Then look at the
transaction that caused the AP_TOO_MANY_TPS
response to occur. If the transaction is issuing too many
intersystem requests, modify its design so that is uses a
smaller number of intersystem requests. If the
transaction is not issuing intersystem requests, but
instead was started by an intersystem request, reduce
the number of inbound intersystem requests sent to you
region at any one time.
Destination:
console.msg
ERZ058456E Storage allocation request from the
region pool was unsuccessful
Explanation:
CICS is unable to acquire enough region storage to
issue a local SNA intersystem request. The amount of
region storage available is configured ronment for either
the regions userid, or the system as a whole.
in the MaxRegionPool attribute of your regions Region
Definition (RD) entry.
System action:
local LU alias defaults to the value in the LocalLUName

attribute in the Region Definition (RD) entry for your
region. Alternatively, it can be set using an environment
variable beginning CICS_SNA_LUALIAS. For example,
if LocalLUName is set to MYLU and the local LU alias is
MYALIAS, then the environment variable is
CICS_SNA_LUALIAS_MYLU=MYALIAS. This can be
set in your regions environment file, or in the NT
environment for either the regions userid, or the system
as a whole.
System action:
CICS continues initializing.
User response:
Destination:
console.msg
ERZ058458E No storage available for a
conversation record
Explanation:
CICS is unable to start a new local SNA intersystem
request because there is insufficient storage available in
the region pool. The amount of region storage available
is configured in the MaxRegionPool attribute of your
System action:
User response:
transaction can be successful. However, if this problem
Destination:
console.msg
ERZ058459E No storage available to initialize local
SNA
User response:
transaction can be successful. However, if this problem
Explanation:
CICS is unable to initialize local SNA because there is
insufficient storage available in the region pool. The
amount of region storage available is configured in the
MaxRegionPool attribute of your regions Region
Definition (RD) entry.
Destination:
console.msg
System action:
CICS is unable to support local SNA intersystem
requests.
ERZ058457I The local LU alias for local SNA

requests is alias
Explanation:
alias is the alias, or nickname, of your regions SNA
local LU name for local SNA intersystem requests. The
User response:
Increase the size of the region pool by overriding the
MaxRegionPool value when you next restart your CICS
region. Alternatively, consider reducing the size of the
trace buffer (RD attribute SysTraceBufferSize) or the
region database hash table (RD attribute
ClassTableSize).
473
ERZ058460E ERZ058463E
Destination:
console.msg
ERZ058460E The partner LU alias alias is not
recognized by your SNA product
Explanation:
The alias alias for one of the remote systems connected
by local SNA is not defined in your SNA product. This
alias is configured in your region as the
SNAConnectName or the RemoteLUName attribute of
the Communications Definition (CD) entry for the remote
system.
CICS has detected this condition during an intersystem
request.
System action:
Further messages are logged either in the console.msg
or the CSMT log. These indicate which CD entry was
used for the intersystem request.
User response:
they show which CD entry, and therefore which remote
system, the intersystem request was for. Look at the
definition of this remote system (called the partner LU)
in your SNA product. If it does not exist:
v Create a partner LU definition in your SNA product
ensuring the values configured match those in the
CICS CD entry.
If the partner LU definition does exist, either:
v Change the SNA product partner LU definition for the
remote system so that the alias is alias.
v Change the CICS CD entry for the remote system so
that the alias is the same as the alias configured in
your SNA product.
Once the definitions are corrected, rerun the intersystem
request.
Destination:
console.msg
ERZ058461E The partner LU name name is not
recognized by your SNA product
Explanation:
The name name for one of the remote systems
connected by local SNA is not defined in your SNA
product. This name is configured in your region as the
RemoteNetworkName and RemoteLUName attributes of
the Communications Definition (CD) entry for the remote
system.
CICS has detected this condition during an intersystem
request.
System action:
474

User response:
First look at the other messages issued by CICS as
they show which CD entry, and therefore which remote
system, the intersystem request was for. Look at the
definition of this remote system (called the partner LU)
in your SNA product. If it does not exist:
v Create a partner LU definition in your SNA product
ensuring the values configured match those in the
CICS CD entry.
If the partner LU definition does exist, either:
v Change the SNA product partner LU definition for the
remote system so that it matched the values from the
CICS CD entry, or
v Change the CICS CD entry for the remote system so
that it matches the values configured in your SNA
product.
Once the definitions are corrected, rerun the intersystem
request.
Destination:
console.msg
ERZ058462E SNA is unable to access data buffer
at address address with length length
Explanation:
A CICS transaction has passed an invalid buffer at
address address to CICS for a local SNA intersystem
request. Either address is not the address of storage
that can be accessed by SNA or address is a valid data
buffer but this buffer is less than length bytes long.
System action:
User response:
Look for the additional CICS messages in either the
console.msg or CSMT.out to determine which
transaction was unsuccessful. Then examine the
application code for this transaction to locate the invalid
buffer. Correct the application program and rerun the
transaction.
Destination:
console.msg
ERZ058463E The SNA product is preventing CICS
from sending user name userId with
an intersystem request
Explanation:
A Communications Definition (CD) entry with
ConnectionType=local_sna and OutboundUserIds=sent
ERZ058464W ERZ058469I
was specified on an intersystem request. However, your
local SNA product does not support sending userIds
without a password.
System action:
User response:
First look at the other messages issued by CICS as
they show which CD entry is incorrectly configured. Alter
this CD entry so that OutboundUserIds is not set to
sent. Rerun the intersystem request when the updated
CD entry is installed in your region.
ERZ058466I Listening for CICS transaction

requests sent to local SNA LU alias
alias
Explanation:
CICS has set up a listener process to receive local SNA
intersystem requests sent to the local Logical Unit (LU)
name configured in your SNA product with an alias of
alias.
System action:
User response:
required.
Destination:
console.msg
Destination:
console.msg
ERZ058464W The SNA product is preventing CICS

from sending the primaryCode/
secondaryCode response; sending
newPrimaryCode/newSecondaryCode
instead
ERZ058467I SNA is available
Explanation:
CICS is about to abnormally terminate an intersystem
request because of the primaryCode/secondaryCode
condition. However, your local SNA product does not
allow CICS to send the primaryCode/secondaryCode
response to the remote system.
Explanation:
Your local SNA product is running.
System action:
User response:
required.
Destination:
console.msg
System action:
and sends the newPrimaryCode/newSecondaryCode
response to the remote system.
ERZ058468E Unexpected error errorCode from the

local SNA attach manager call name
These error codes are described in the TXSeries for

Explanation:
CICS is unable to register itself with your local SNA
product. The response to the name call was errorCode.
User response:
required.
System action:
CICS is unable to receive inbound local SNA requests.
Destination:
console.msg
ERZ058465I Listening for all requests sent to local
SNA LU alias alias
Explanation:
CICS is able to receive all local SNA intersystem
requests sent to the Logical Unit (LU) alias alias.
System action:
User response:
required.
Destination:
console.msg
User response:
they can indicate why the request was unsuccessful. If
the CICS messages do not help you solve the problem,
look up the errorCode response in the application
programming manual for your SNA product. Finally, if
you can not solve the problem yourself, contact your
Destination:
console.msg
ERZ058469I CICS is using library version
major.minor of Local SNA product name
Explanation:
This message indicates which version of your local SNA
products APPC library is being used by CICS.
System action:
475
ERZ058470I ERZ058473E
User response:
required.
Destination:
console.msg
ERZ058470I Registering transactions with local
SNA
Explanation:
CICS is about to register its transactions with local SNA
so it can receive local SNA intersystem requests. Local
SNA intersystem requests for transactions that are not
registered are abnormally terminated by your SNA
product.
Message ERZ058472I is logged for each transaction
that is registered with your SNA product. CICS registers
all transactions that have a Transaction Definition (TD)
entry with at least one of the following values:
v IsBackEndDTP=yes
The request that failed was a SNA WinAsyncAPPCEx

call.
System action:
CICS continues processing. Inbound local SNA
intersystem requests for this transaction are abnormally
terminated by your SNA product.
User response:
they can indicate why the request was unsuccessful.
Also look at the log for your SNA product and the NT
application and event logs. If the system messages do
not help you solve the problem, look up the errorCode
response in the application programming manual for
your SNA product. Finally, if you can not solve the
problem yourself, contact your support organization.
Destination:
console.msg
ERZ058472I Transaction transId has been
registered with local SNA
v InvocationMode=comms_link
Explanation:
The Transaction Definition (TD) entry for transaction
transId has one or more of the following settings:
v InvocationMode=any_facility
v IsBackEndDTP=yes
v ProgName=DFHMIRS
System action:
User response:
Check that message ERZ058472I is issued for each
CICS transaction that is requested by incoming local
SNA intersystem requests. If a transaction is not
registered then alter its TD entry so that the
InvocationMode attribute includes comms_link. Then,
once this updated TD entry is installed in your region,
CICS registers the transaction with SNA.
v ProgName=DFHMIRS
CICS has registered this transaction with your local
SNA product. The SNA product needs to know the
names of CICS transactions in order to receive requests
for them from remote SNA systems.
System action:
Destination:
console.msg
User response:
required.
ERZ058471E Local SNA is unable to register

transaction transId; Error code is
errorCode
Destination:
console.msg
Explanation:
CICS is unable to register transaction transId with your
local SNA product. The SNA product needs to know the
names of CICS transactions in order to receive
intersystem requests for them from remote SNA
systems.
ERZ058473E Unable to register transaction transId

with local SNA as the system limit of
limit has been exceeded
CICS is attempting to register this transaction because

the Transaction Definition (TD) entry for transaction
transId one or more of the following settings:
v IsBackEndDTP=yes
v i.IsBackEndDTP=yes
Explanation:
The Transaction Definition (TD) entry for transaction
transId has one or more of the following settings:
v ProgName=DFHMIRS
v ProgName=DFHMIRS
476
CICS is unable registered this transaction with your

local SNA product because the number of transactions
ERZ058474E ERZ058477E
that CICS already has registered has reached the
operating system maximum of
MAXIMUM_WAIT_OBJECTS (limit).
The SNA product needs to know the names of CICS
transactions in order to receive requests for them from
remote SNA systems.
System action:
CICS continues processing. Incoming local SNA
intersystem requests for this transaction are abnormally
User response:
If this transaction is specified by incoming local SNA
intersystem requests, reduce the number of TD entries
in your region database that have one or more of the
following settings.
v IsBackEndDTP=yes
v ProgName=DFHMIRS
Destination:
console.msg
ERZ058474E Another process is already using the
local SNA LU alias alias
Explanation:
CICS is unable to listen for incoming local SNA
intersystem requests because another process
(probably another CICS region) is already using the
local Logical Unit (LU) defined for this CICS region.
The local LU for this region is configured in the
entry. The alias, or nickname, for this local LU name is
alias.
System action:
User response:
Examine the configuration of all of the applications and
services on your machine that use SNA. Ensure that
both the local LU name and the alias configured for this
CICS region are not used by any other process.
Destination:
console.msg
ERZ058475E Unable to register any transactions
with local SNA; Error code is errorCode
Explanation:
CICS is unable to initialize a local SNA listener. The
reason for this is described by errorCode.
System action:
CICS continues processing. Further messages can be
logged.
User response:
Look at the other messages issued by CICS, as they
indicate why the request was unsuccessful. Follow the
Destination:
console.msg
ERZ058476E Local SNA library not loaded in
process processId
Explanation:
CICS is unable to load the local SNA library into
process processId, which means all local SNA
intersystem requests that use this process are
System action:
CICS abnormally terminates all local SNA intersystem
requests that use this process.
User response:
Check the console.msg file for other error messages
concerning the local SNA library. If these exist, follow
the instructions for the earlier messages. If no other
messages exist, the APPC library for your SNA product
is deleted or corrupted. Correct the problem with the
library. If you cannot solve the problem yourself, contact
Destination:
console.msg
ERZ058477E A type exception occurred in a
callName call to the libraryName SNA
library
Explanation:
CICS issued a callName call to the SNA library provided
with your local SNA product. However this call was
unsuccessful and an exception was raised inside the
SNA library. Possible causes for this exception are:
v CICS is processing an intersystem request for a local
transaction and the transaction has either passed an
invalid pointer or an invalid length on an EXEC CICS
command.
v The SNA library is not able to acquire the resources it
needs to process the call because the local machine
is over-loaded.
v There is an internal error in your SNA product.
The default name for your SNA library is libraryName,
but this was possibly changed by the
CICS_SNA_APPC_LIBRARY environment variable.
System action:
CICS writes a symptom record describing the SNA
callName call to your regions symrecs file and
abnormally terminates the SNA request. Further
User response:
477
ERZ058478E ERZ058481W
concerning the SNA library. If these exist, follow the
instructions for the earlier messages.
If this exception occurred during an intersystem request,
check that the failing application program is passing
valid data buffers and parameters on the unsuccessful
intersystem request. Correct any errors and rerun the
transaction.
Check that your machine is not short of resources such
as virtual memory. Increase these resources as
required.
If you can not solve the problem yourself, contact the
organization supporting your SNA product.
Destination:
console.msg
ERZ058478E Unable to schedule incoming local
SNA intersystem request
Explanation:
A local SNA intersystem request was received by your
CICS region; however, CICS is unable to schedule the
request.
System action:
CICS abnormally terminates the local SNA intersystem
request.
User response:
Look at the other messages issued by CICS just before
this message as they can possibly indicate why the
request was unsuccessful. Follow the instructions for
these messages. If you can not solve the problem
yourself, contact your support organization.
Destination:
console.msg
Destination:
console.msg
ERZ058480E No storage available to register
transaction transId with local SNA
Explanation:
CICS has run out of space in the task private pool and
in unable set up the request that calls SNA to receive
notification of incoming local SNA intersystem requests.
The size of the task private pool is configured in the
MaxTaskPrivatePool attribute of the Region Definition
(RD) entry.
System action:
CICS retries the request for storage sometime later.
Meanwhile, your SNA product will abnormally terminates
all incoming local SNA requests for transaction transId.
User response:
Increase the size of the task private pool by overriding
the value of MaxTaskPrivatePool the next time your
region is started.
Destination:
console.msg
ERZ058481W There are no transactions registered
with local SNA
Explanation:
CICS receives local SNA intersystem requests only for
CICS transactions it has successfully registered with
your SNA product. However, currently there are no
transactions registered. This is possibly because:
v There are no transactions defined in the Transaction
Definition (TD) entries that have one or more of the
following values:
IsBackEndDTP=yes
ProgName=DFHMIRS
ERZ058479E No storage available to listen for

incoming local SNA requests
InvocationMode=comms_link
Explanation:
CICS has run out of space in the task private pool and
in unable set up the request that calls SNA to receive
notification of incoming local SNA intersystem requests.
Message ERZ058472I is logged for each transaction

that has these values.
The size of the task private pool is configured in the

MaxTaskPrivatePool attribute of the Region Definition
(RD) entry.
System action:
CICS retries the request for storage sometime later.
Meanwhile, your SNA product abnormally terminates all
incoming local SNA requests.
User response:
Increase the size of the task private pool by overriding
the value of MaxTaskPrivatePool the next time your
region is started.
478
InvocationMode=any_facility
v Errors have occurred that resulted in CICS

unregistering this transaction with SNA. A message is
logged whenever such an error occurs.
System action:
CICS continues processing. Meanwhile, incoming local
SNA intersystem requests for your region are
abnormally terminated by your SNA product.
User response:
Look at the console.msg file for your CICS region.
Check that message ERZ058472I is issued for each
CICS transaction that is requested by incoming local
SNA intersystem requests. If this message does not
ERZ058482E ERZ058485E
appear for a particular transaction then change the TD
entry for this transaction so that it has one or more of
the following values.
Destination:
console.msg
v IsBackEndDTP=yes
ERZ058484E Transaction transId is not correctly

defined to SNA
v ProgName=DFHMIRS
If the message is logged look for the error message that
describes why CICS is no longer registering (or listening
for) the transaction. Follow the instructions for the error
message.
If you make changes to any TD entries in the runtime
database while CICS is running, CICS automatically
registers the transaction with local SNA if it is
appropriate.
Destination:
console.msg
ERZ058482E operatingSysCall system call returned
errorCode
Explanation:
CICS issued a operatingSysCall call to the operating
system and it returned a errorCode error code. This is
not expected.
System action:
CICS abnormally terminates the current request. Further
User response:
Look up the error code in your operating system
documentation. Also view the system event log and
application log as they can possibly contain messages
that explain why the error occurred. For example, the
system possibly ran out of memory or was overloaded.
Correct the cause of the error and rerun the request.
Destination:
console.msg
ERZ058483E Transaction transId is not defined to
SNA
Explanation:
CICS is unable to register transaction transId with your
SNA product because this transaction is not defined in
SNA.
System action:
logged.
User response:
Add a definition of the CICS transaction to your SNA
product. Use cicssnatpns if your SNA product is
MicroSoft SNA Server, or the SNA node configuration
tool is you are using IBM Communications Server for
NT.
Explanation:
CICS received a local SNA intersystem request for
transaction transId. However, SNA also started another
operating system process to receive the intersystem
request. This means the definition for the transId
transaction in your SNA product configures transId as
an auto-started (dynamically load allowed) transaction.
This is not correct for a CICS transaction.
System action:
User response:
Change the definition of the CICS transaction in your
SNA product so that it is not auto-started (dynamically
load allowed). Use cicssnatpns if your SNA product is
MicroSoft SNA Server, or the SNA node configuration
tool is you are using IBM Communications Server for
NT.
Destination:
console.msg
ERZ058485E Transaction transId is no longer
registered with local SNA
Explanation:
An error has occurred that means CICS is no longer
able to register transaction transId with local SNA. SNA
requires the name of a CICS transaction to be
registered before it can pass incoming intersystem
requests for the transaction to your region.
System action:
SNA intersystem requests for this transaction are
User response:
Look for earlier messages in the console.msg file that
describe the error condition that occurred on the
transaction. Also view the system event log and
system possibly ran out of memory or was overloaded.
Correct the cause of the error. CICS reregisters the
transaction the next time the region is restarted, or if the
Trhasaction Definition (TD) entry for the transaction is
deleted and then added to the runtime database while
the region is running.
Destination:
console.msg
479
ERZ058486E ERZ058488W
ERZ058486E Local SNA request received for
incomingAlias rather than regionAlias
Explanation:
alias of regionAlias.
CICS has received a local SNA request that is intended
for the region/application that using incomingAlias as its
local LU alias.
Either more than one CICS local LU name and alias is
configured in SNA (which is not supported) or the local
LU alias defined in CICS is not correct.
The local LU alias in your region defaults to the same
name as the local LU name. This can be changed using
an environment variable beginning
CICS_SNA_LUALIAS. For example, if LocalLUName is
set to MYLU and the local LU alias is MYALIAS, then
the environment variable is
Whatever the value of the local LU alias you wish to
use, it must be entered in the definition of your regions
local LU name in your SNA product.
No other CICS local LUs can be defined in SNA and no
other CICS region can use SNA while this CICS region
is running.
System action:
CICS continues processing the request. Further
User response:
Look at the definition of your regions local LU name in
the SNA product and ensure the LU alias regionAlias is
correct for your region. If it is not, either change the
SNA definitions or change the alias used by your CICS
region. Ensure there are no other CICS local LUs
defined in SNA.
Destination:
console.msg

regions Region Definition (RD) entry. In this case it is
localLUname.
alias of localLUalias. This local LU alias defaults to the
same name as the local LU name or it can be changed
using an environment variable beginning
Currently, the local LU name localLUname is not
configured in your SNA product which means
intersystem requests using local SNA can fail.
To configure SNA, the local LU name localLUname
must first be defined with a local LU alias of
localLUalias in a configuration file using the SNA Node
Configuration tool. Once the local local LU name is
defined, the configuration file must be loaded into the
SNA node each time the node is started. It is possible
to view which local LU names are loaded into the node
by using the SNA Node Operations tool.
System action:
CICS continues processing the request. Further
User response:
First ensure that localLUname and localLUalias are the
correct values for your region. If they are not, alter
these names to their proper values and restart your
region.
When localLUname and localLUalias are correct, check
that they are defined in your SNA configuration file and
update the definitions as required.
Finally, load the configuration file into your SNA node
using either the Start Node or Apply New
Configuration options of the SNA Node Operations tool
as appropriate.
Destination:
console.msg
ERZ058487W Local LU name localLUname with

local LU alias localLUalias is not
configured in SNA
ERZ058488W SNA local LU name regionLUname is

associated with local LU alias
SNALUalias rather than the regions
local LU alias localLUalias
Explanation:
Explanation:
480
ERZ058489W
regionLUname.
Currently, the local LU name regionLUname is
configured in your SNA product to have the local LU
alias of SNALUalias rather than localLUalias. It is
therefore possible that CICS is unable send and receive
local SNA intersystem requests.
ERZ058489W Local LU alias localLUalias is defined

in SNA for local LU name SNALUname
rather than the regions local LU name
regionLUname
Explanation:
regionLUname.
If SNALUalias is not defined in your SNA product all

local SNA intersystem requests are unsuccessful.
Currently, the local LU alias localLUalias is configured in

your SNA product to be the local LU alias of another
local LU name, SNALUname. CICS therefore sends and
receives local SNA intersystem requests using the
SNALUname local LU name rather than regionLUname.
It is possible that some of these requests do not
succeed because the remote system is configured to
receive requests from regionLUname rather than
SNALUname.
System action:
logged.
System action:
logged.
User response:
First ensure that regionLUname and localLUalias are
the correct values for your region. If they are not, alter
region.
User response:
First ensure that regionLUname and localLUalias are
the correct values for your region. If they are not, alter
region.
When regionLUname and localLUalias are correct,

check that they are defined in your SNA configuration
file and update the definitions as required.
When regionLUname and localLUalias are correct,

check that they are defined in your SNA configuration
file and update the definitions as required.

as appropriate.

as appropriate.
Destination:
console.msg
Destination:
console.msg
If SNALUalias is defined as the alias of another local LU

name then CICS sends and receives local SNA
intersystem requests as this other local LU name. It is
possible that some of these requests do not succeed
because the remote system is configured to receive
requests from regionLUname.
481
ERZ058490I ERZ058494E
ERZ058490I Starting the SNA Attach Manager
Explanation:
CICS has started the Attach Manager feature of your
SNA product. This enables CICS to receive incoming
local SNA intersystem requests.
System action:
User response:
required.
Destination:
console.msg
ERZ058491E CICS is unable to receive requests for
transaction transId from local SNA
Explanation:
An error has occurred that means CICS is not able to
register transaction transId with local SNA. SNA
requires the name of a CICS transaction to be
requests for the transaction to your region.
System action:
SNA intersystem requests for this transaction are
User response:
describe the error condition that occurred on the
transaction. Also view the system event log and
system possibly ran out of memory (paging space) or
was overloaded. Correct the cause of the error. CICS
reregisters the transaction when the region is restarted.
Destination:
console.msg
ERZ058492E An operating system thread could not
be created for local SNA
Explanation:
An error has occurred that means CICS is not able to
create a new operating system thread. This thread is
required to register CICS transactions with local SNA.
SNA requires the name of each CICS transaction to be
requests for the transaction to your region. Each
operating system thread is able to register 64 CICS
transactions simultaneously.
System action:
SNA intersystem requests for all transactions that are
not currently registered with local SNA are abnormally
User response:
482

describe why the thread was unable to be created, Also
view the system event log and application log as they
can possibly contain messages that explain why the
error occurred. For example, the system possibly ran
out of memory (paging space) or was overloaded.
Correct the cause of the error. CICS reregisters all
transactions when the region is restarted.
Destination:
console.msg
ERZ058493E
An APPC verb call for transaction

transId detected an unexpected system
error with a secondary return code of
secondaryRC
Explanation:
Communication (APPC) verb call to your SNA product in
order to receive incoming local SNA intersystem
requests for CICS transaction transId. This APPC call
returned with the 11F0/secondaryRC response, which
can possibly indicate that your machine is short of
system resources.
Note: The 11F0 and secondaryRC values are displayed
by CICS as hexadecimal numbers in the local
machine byte-order.
System action:
CICS retries the APPC call. Meanwhile, it is possible
that some incoming local SNA intersystem requests are
unsuccessful.
User response:
Look up the 11F0/secondaryRC response in the
application programming manual for your SNA product.
Also look for errors reported in the message log used
by your SNA product and also the local NT system and
application logs. Alternatively, run a performance
monitor on your system to determine which resources
are running out.
Destination:
console.msg
ERZ058494E A type exception occurred in a
callName call to the libraryName SNA
library
Explanation:
CICS issued a callName call to the SNA Node
Operations Facility library provided with your local SNA
product. This call is used to receive incoming local SNA
intersystem requests. However it was unsuccessful and
an exception was raised inside the SNA library. Possible
causes for this exception are:
v The SNA library is not able to acquire the resources it
needs to process the call because the local machine
is over-loaded.
v There is an internal error in your SNA product.
ERZ058500E ERZ058506I
The default name for your SNA library is libraryName,
but this was possibly changed by the
CICS_SNA_ATTACH_LIBRARY environment variable.
System action:
CICS writes a symptom record describing the SNA
callName call to your regions symrecs file and
abnormally terminates the SNA request. Further
User response:
concerning the SNA library. If these exist, follow the
instructions for the earlier messages.
Check that your machine is not short of resources such
as virtual memory. Increase these resources as
required.
If you can not solve the problem yourself, contact the
organization supporting your SNA product.
Destination:
console.msg
ERZ058500E Could not spawn cobanimsrverrno.
Error number is cobanimsrverrno.
Explanation:
The COBOL Animator process could not be spawned.
System action:
cicsanimsrv terminates.
User response:
Take action that is appropriate for the errno.
Destination:
console
ERZ058501I RPC daemon started successfully.
Explanation:
The RPC daemon has been started successfully.
ERZ058503E
RPC daemon could not be started.
Explanation:
cicscp command failed to start the RPC daemon.
Possible causes could be, sarpcd missing from CICS
bin directory, port 135 might be in use by some other
process other than sarpcd, or some system error.
System action:
cicscp command terminates abnormally.
User response:
If port 135 is in use by some other process, free the
same. Otherwise, try running the script cicsstart_sarpc.
On failure, the script returns with the failure exit status.
Also, consider running the script cicsstart_sarpc in
Debug mode by environment variable DEBUG=1 to get
more information.
ERZ058504I Starting RPC daemon.
Explanation:
CICS is trying to start CICS supplied RPC daemon.
System action:
none
User response:
none
ERZ058505E DCE daemon is running.Current
version of TXSeries does not support
DCE.
Explanation:
CICS is trying to start CICS supplied RPC daemon and
it finds DCED running. If DCED is running, CICS
supplied RPC (SARPC) daemon cannot be started.
System action:
cicscp command terminates abnormally as DCE is not
supported.
System action:
none
User response:
Current version of TXSeries does not work with DCE. It
is recommended to unconfigure and uninstall DCE and
retry.
User response:
none
ERZ058506I RPC daemon stopped successfully.
ERZ058502I RPC daemon is already running.

Explanation:
The SARPC RPC daemon is already running on the
system.
System action:
none
Explanation:
The SARPC RPC daemon has been stopped
successfully.
System action:
none
User response:
none
User response:
none
483
ERZ058507E ERZ102008I
ERZ058507E Unsuccessful attempt to allocate
Task-Shared Pool memory.
Explanation:
CICS was unable to allocate Task-Shared Pool memory
needed for Application Server.
System action:
User response:
User can increase Task Shared Pool Storage size.
ERZ102002I Configuring databaseName for region
regionName.
Explanation:
Database is being configured for the region. This
includes creation of tables for the CICS region.
System action:
User response:
None
Destination:
stderr
ERZ102003E Region regionName is running or is
already being configured.
Configuration is not possible.
Explanation:
DB2 cannot be configured for a region while the region
is running, or while it is being configured by another
user.
System action:
value 1.
User response:
If the region is running and a configuration change must
be made then shutdown the region. If another user is
performing configuration for the region then retry the
command when that configuration is complete.
Destination:
stderr
ERZ102004I Configuring databaseName table
tableName for recoverable auxiliary
TSQs for region regionName
Explanation:
The command is creating tables for the regions
recoverable auxiliary Temporary Storage Queues
(TSQs).
System action:
User response:
None
484
Destination:
stderr
tableName for non-recoverable
Explanation:
The command is creating tables for the regions
non-recoverable auxiliary Temporary Storage Queues
(TSQs).
System action:
User response:
None
Destination:
stderr
Explanation:
The command encountered a problem running
programName.
System action:
value 1.
User response:
Refer to other messages displayed or in stderr. Check
that CICS is installed correctly. Check that the program
exists, is owned by user cics and has read, write and
Destination:
stderr
tableName for logically recoverable
Explanation:
The command is creating Database tables for the
regions logically recoverable Transient Data Queues
(TDQs).
System action:
User response:
None
Destination:
stderr
tableName for physically recoverable
Explanation:
ERZ102010I ERZ102015W
regions physically recoverable Transient Data Queues
(TDQs).
ERZ102013W NOTE: The created queue will be

treated as recoverable.
User response:
None
Explanation:
The user has requested a non-recoverable queue.
Because non-recoverable queues are not supported by
the DB2 file system, the queue is treated as
recoverable.
Destination:
stderr
System action:
ERZ102010I Configuring databaseName for

non-recoverable TDQs for region
regionName
User response:
Users that are dependent on non-recoverable file
semantics are recommended to maintain such queues
on a SFS supporting CICS region.
System action:
Explanation:
regions non-recoverable Transient Data Queues
(TDQs).
System action:
User response:
None
Destination:
stderr
tableName for protected
regionName
Explanation:
regions Protected Locally-Queueing requests.
System action:
User response:
None
Destination:
stderr
tableName for unprotected
regionName
Destination:
stderr
ERZ102014W NOTE: The created queue will be
treated as logically recoverable.
Explanation:
The user has requested a physically recoverable queue.
Because physically recoverable queues are not
supported by the DB2 file system, the queue is treated
as logically recoverable.
System action:
User response:
Users that are dependent on physically recoverable
queue semantics are recommended to maintain such
queues on a SFS supporting CICS region.
Destination:
stderr
ERZ102015W All unprotected STARTs are being
internally protected.
Explanation:
The user has requested a DB2 table for locally queued
Unprotected STARTs. DB2 acts as the resource
manager for starts. All STARTs are written to
recoverable queues.
System action:
Explanation:
regions Unprotected Locally-Queueing requests.
User response:
As it is not possible to store locally queued STARTs
remotely. Users who are dependent on local
unprotected STARTs must retain a local SFS server to
maintain these queues.
System action:
Destination:
stderr
User response:
None
Destination:
stderr
485
ERZ102016I ERZ102027E
ERZ102016I The product definition (XAD) created is
XAname.
Explanation:
The user has XAname, system defined product
definition (XAD).
System action:
User response:
None.
Destination:
stderr
ERZ102025E Cannot connect to Oracle,
databaseInstance, SQL return code
<SQLreturn>.
Explanation:
The attempt to connect to the Oracle instance was
unsuccessful. The return code indicates the cause of
the problem.
Destination:
stderr
System action:
value 1.
ERZ102020E You must be logged in as root on

UNIX or as Administrator on Windows
NT to run the programName command
User response:
Check the SQL return code to diagnose and correct the
problem.
Explanation:
You attempted to run cicsdb2conf when logged on with
insufficient authority. On UNIX you must be logged on
as root. On Windows NT you must be logged on with a
userid with Administrator and cicsgroup authority.
Destination:
stderr
System action:
Command terminates.
User response:
Log on correctly and retry the command.
Destination:
stderr
ERZ102023W Could not open log file logFile.
Explanation:
logFile was unable to be opened for writing the
configuration information.
System action:
Command continues.
User response:
Check the path and permissions on the path and file.
Destination:
stderr
ERZ102024E Cannot bind to DB2 aliasName, SQL
return code <SQLreturn>.
Explanation:
The connection to DB2 succeeded, but the attempt to
bind was unsuccessful. The return code indicates the
System action:
value 1.
User response:
problem.
486
ERZ102026E Unable to create TSQ using table

fileName.
Explanation:
There was an error creating the Temporary Storage
Queue (TSQ) fileName on DB2.
System action:
The command abnormally terminates unless you
specified the -I option.
User response:
Refer to preceding messages, from cicsdb2conf, for the
existing table on DB2 then the table cannot be created
on command).
Destination:
stderr
ERZ102027E Unable to create TDQ using table
fileName.
Explanation:
There is an error creating the Transient Data Queue
(TDQ) fileName on DB2.
System action:
The command abnormally terminates unless you
specified the -I option.
User response:
ERZ102028E ERZ102035I
retrying the command with Ignore Errors selected (-I
flag on command).
Destination:
stderr
ERZ102028E Unable to create Local Queue using
table fileName.
Explanation:
An attempt to create a Local Queue (LQ) on DB2 was
unsuccessful. The DB2 error code indicates the cause
of the problem.
System action:
The command continues if the -I option is set;
otherwise, the command terminates.
User response:
on command).
Destination:
stderr
ERZ102031E To configure DB2 for CICS both an

Instance Name and Alias Name must
be specified.
Explanation:
Instance Name and Alias Name are both mandatory on
the cicsdb2conf command.
System action:
value 1.
User response:
Set both Instance Name and Alias Name and retry the
command.
Destination:
stderr
ERZ102033I Create system defined XA XA
definition for region regionName.
Explanation:
User requested XA, system defined XA definition.
System action:
User response:
None
Destination:
stderr
ERZ102029E Unable to update region definition.

Explanation:
The command was unable to update the region
definition.
System action:
value 1.
User response:
Check the region definitions and retry the command.
Destination:
stderr
ERZ102030I Configuration completed successfully.
Explanation:
There were no problems reported during configuration.
System action:
User response:
None
Destination:
stderr
ERZ102034E Creation of XA definition for region

regionName was unsuccessful.
Explanation:
Region product definition (XAD) was unable to be
added to the CICS resource definitions. Other
messages can indicate the source of the problem.
System action:
value 1.
User response:
Check that the region specified exists. Check that the
access permissions for the directory
/var/cics_regions/<region> are appropriate. Ensure that
it is owned by user cics and has read, write and
Destination:
stderr
ERZ102035I Update the region definitions (RD) for
region regionName for databaseName
configuration.
Explanation:
Update of the RD definitions is in progress.
System action:
487
ERZ102036E ERZ102042E
User response:
None
Destination:
stderr
ERZ102036E Update of the region definitions (RD)
for region regionName was
unsuccessful.
Explanation:
The region definition (RD) was unable to be added to
the CICS resource definition. Other messages can
indicate the source of the problem.
System action:
User response:
Destination:
stderr
ERZ102037I The FileServer attribute in the file
definitions (FD) for region regionName
will not be changed.
Explanation:
The -f option on the cicsdb2conf command was set to
NULL. The FileServer attribute in the file definition (FD)
is not changed.
System action:
User response:
None
Destination:
stderr
ERZ102038I Update of file definitions (FD) for
region regionName for databaseName
configuration.
Explanation:
Update of the file definitions (FD) is in progress.
System action:
ERZ102039E Update of the file definitions (FD) for

region regionName was unsuccessful.
Explanation:
The file definition (FD) was unable to be added to the
CICS resource definition. Other messages can indicate
the source of the problem.
System action:
User response:
Check that the specified file exists. Check that the
access permissions for the file are appropriate. Ensure
that it is owned by user cics and has read, write
permissions for its owner.
Destination:
stderr
ERZ102040E Usage: cicsdb2conf [-I] [-m] -r
regionName [-l logFileName] {-C -i
instanceName -a aliasName [-f] [-g]
[-n|-s] [-u userName[,password]]
|[-S][-N][-D][-P][-T][-L][-Q]}
Explanation:
You entered the cicsdb2conf command incorrectly.
System action:
value 1.
User response:
Destination:
stderr
ERZ102041W Object fileName already exists
Explanation:
Table fileName already exists on DB2.
System action:
Processing continues, but other messages are
produced as a result of this error that can cause the
command to terminate.
User response:
If necessary you can destroy the existing object using
the database administration commands.
Destination:
stderr
User response:
None
ERZ102042E Cannot find the specified region.
Destination:
stderr
Explanation:
cicsdb2conf was unable to find or access the named
region.
System action:
User response:
488
ERZ102043E ERZ102049E
Destination:
stderr
ERZ102043E DB2 Alias aliasName, is not defined
in the Product Definition file (XAD).
Explanation:
The program expects to find aliasName in the XAOpen
string in Product Definitions file (XAD). The Alias Name
in the XAOpen string and the DefaultFileServer in the
Region Definitions (RD) must match.
System action:
User response:
Check that the region is successfully configured for DB2
and the product definitions file (XAD) is not corrupted.
ERZ102046E Cannot SQLstatement, SQL return

code <SQLreturn>.
Explanation:
The shown SQL statement was unsuccessful. The
return code indicates the cause of the problem.
System action:
value 1.
User response:
problem.
Destination:
stderr
ERZ102047W Cannot expand file fileName
Explanation:
cicsdestroy attempted to delete cics data you have on
DB2, but was unable to get the full name of the DB2 file
to delete.
Destination:
stderr
System action:
The command continues, but the named file possibly
needs to be deleted by hand.
ERZ102044E Environment variable

databaseInstance is not set
User response:
Once cicsdestroy has completed, check for remaining
DB2 files and delete them manually. This warning
possibly indicates a problem with your CICS installation.
Explanation:
The appropriate database instance variable was not set,
cicsdb2conf/cicsoraconf cannot access database
resources.
System action:
User response:
export DB2INSTANCE=<instance id> before invoking
cicsdb2conf.
Destination:
stderr
ERZ102045E Could not access user information for
userId
Explanation:
The DB2INSTANCE owner id <userid> does not exist.
System action:
value 1.
User response:
Set up the DB2 instance owner id as detailed in the
DB2 Installation and Operation Guide.
Destination:
stderr
Destination:
stderr
ERZ102048E Failed to create table tableName
Explanation:
An SQL error occurred while trying to create the table.
System action:
User response:
Destination:
stderr
ERZ102049E Failed to add index indexName
Explanation:
An SQL error occurred while trying to add the index.
System action:
User response:
Destination:
stderr
489
ERZ102050E ERZ102056E
ERZ102050E Unable to get CICS information
Set both Instance Name and Alias Name and retry the
command.
Explanation:
cicsdb2conf was unable to get information on your cics
region.
Destination:
stderr
System action:
The command terminates unsuccessfully.
User response:
Check that you have installed cics correctly. Check that
your region is defined correctly and that you have
permissions to read it.
Destination:
stderr
ERZ102051E Unable to allocate memorySize bytes
of storage
Explanation:
cicsdb2conf was unable to allocate the amount of
memory shown.
System action:
The command terminates unsuccessfully.
User response:
Check that you have sufficient resources on your
machine to perform the requested action.
Destination:
stderr
ERZ102052E Usage: cicsoraconf [-I] [-m] -r
regionName [-l logFileName]
{-C|-S|-N|-D|-P|-T|-L|-Q} [-i instance] [-f]
[-g] [-s] -u userName[/password] [-x
userName/password] [-t tableSpace]
Explanation:
You entered the cicsoraconf command incorrectly.
System action:
value 1.
User response:
Destination:
stderr
ERZ102053E To configure ORACLE for CICS
specify the instance ($ORACLE_SID)
Explanation:
Instance Name and Alias Name are both mandatory on
the cicsdb2conf command.
System action:
value 1.
User response:
490
ERZ102054W An Oracle request failed because:

errorMessage
Explanation:
The program issued and SQL command that returned
an error code. The text describing the error is contained
in this message. This can be an acceptable error such
as the failure of a table create because it was created
previously, or a more serious error such as insufficient
space to create the table.
System action:
The command either fails or runs to completion,
depending on which SQL command failed and the -I
invocation parameter.
User response:
Determine if the error was acceptable given the
circumstances in which the program was run. If the
error was not acceptable then refer to the Oracle
documentation to determine the correct course of
action.
Destination:
stderr
ERZ102055E An Oracle administration userid must
be specified
Explanation:
A userid with Oracle administration authority must be
specified via the -u parameter on the cicsoraconf
command. This id is required to allow cicsoraconf to
configure the Oracle tables that are used by CICS for its
queue management.
System action:
The cicsoraconf command is terminated.
User response:
Determine the Oracle administration id to use and
reinvoke the cicsoraconf command with the -u
parameter specifying the Oracle administration userid.
You also need the password, which can be specified as
part of the -u parameter or via the
CICSORAPASSWORD environment variable; otherwise,
you are prompted for it.
Destination:
stderr
ERZ102056E A password is mandatory when a
userid is specified on the -x parameter
Explanation:
The -x parameter was specified on the cicsoraconf
command but only a userid was specified. A password
is mandatory if a userid is specified.
ERZ102057I ERZ105001E
System action:
The cicsoraconf command is terminated.
User response:
Determine the Oracle password for the specified userid
and rerun the cicsoraconf specifying the password.
Destination:
stderr
System action:
The command continues but can possibly result in
abnormal termination returning the value 1.
User response:
problem.
Destination:
stderr
ERZ102057I Creating the Oracle table

Explanation:
The cicsoraconf utility is creating the Oracle table for
the cics file as indicated in the previous message.
System action:
The cicsoraconf command continues.
User response:
None
Destination:
stderr
ERZ102058I Creating the Oracle table index
Explanation:
The cicsoraconf utility is creating the Oracle table index
for the cics file as indicated in the previous message.
System action:
The cicsoraconf command continues.
User response:
None
Destination:
stderr
ERZ102059E Cannot connect to DB2, SQL return
code SQLreturn.
Explanation:
The attempt to connect to DB2 was unsuccessful. The
return code indicates the cause of the problem.
System action:
value 1.
User response:
problem.
Destination:
stderr
ERZ102060W DB2 warning - SQLstatement, SQL
return code <SQLreturn>.
Explanation:
The shown SQL statement was unsuccessful but
processing continues. The return code indicates the
ERZ102061I Modifying entry EntryName in

database manager configuration file.
Explanation:
CICS requires certain database manager parameters to
be set. Trying to configure these parameters in the
database. Database needs to be restarted for the
changes to be effective.
System action:
User response:
None.
Destination:
stderr
ERZ102062E Failed to configure entry EntryName
in database manager configuration file.
Explanation:
Main reasons for the failure are database connection
failure or preexisting invalid value. For further
explaination look at the other messages.
System action:
The command continues if the -I option is set;
otherwise, the command terminates.
User response:
Refer to the preceding messages and correct the
problem.
Destination:
stderr
Explanation:
The lock file fileName cannot be created.
Accompanying messages can identify the exact cause
of the problem.
System action:
Command abnormally terminates.
User response:
Check that you have permission to create files in the
directories named in fileName. Ensure also that the file
system is not full. See accompanying messages for
further information. Correct the problem and retry the
command.
Destination:
491
ERZ105002W ERZ105008W
stderr

directoryName

Explanation:
System action:
Explanation:
It was not possible to create server directory
directoryName.
System action:
Destination:
stderr
User response:
created. See accompanying messages for further
information. Correct the problem, and retry the
command.
Destination:
stderr
User response:
None
Explanation:
problem.
ERZ105006I Directory directoryName created

Explanation:
The directory directoryName was created.
System action:
System action:
User response:
directories named in fileName. Ensure also that the file
system is not full. See accompanying messages for
further information. Correct the problem and retry the
command.
User response:
None
Destination:
stderr
Explanation:
mean that the server is currently running, or some other
command or process is administering the server
definitions, or the lock was taken by a command or
process that subsequently terminated abnormally,
System action:
User response:
Destination:
stderr
492
Destination:
stderr
ERZ105007E Unable to change access permissions
on directory directoryName
Explanation:
A CICS command is unable to change the access
permissions on directory directoryName. Either the
directory does not exist or you do not have the required
privileges to change its ownership.
System action:
User response:
created. You must have read and execute permission
on all parent directories, and write permission to the
directory itself. See accompanying messages for further
information. Correct the problem, and retry the
command.
Destination:
stderr
ERZ105008W Unable to change details of file
fileName, errno errno
Explanation:
An attempt at changing the owner of fileName to user
errno failed.
ERZ105009E ERZ105026E
System action:
The command can possibly terminate abnormally.
System action:
The command fails.
User response:
Examine the value of errno to determine what the exact
problem is.
User response:
Retry the command. If you are in a long interactive
session with cicscp try ending the session and
submitting the command on the command line.
Destination:
stderr
Destination:
stderr
ERZ105009E Schema File already exists

Explanation:
The cicsscdcreate command attempted to create the
empty schema file with the specified name, but a file
System action:
The cicsscdcreate command terminates abnormally.
User response:
Reexecute the command specifying a new schema file
name or remove the existing file if it is no longer
required.
ERZ105023E Internal cicscp error detected:

errorNumber
Explanation:
This message is displayed if cicscp detects an internal
problem with the operation of cicscp itself.
System action:
None
User response:
Retry the command. If the problem persists, contact
Destination:
stderr
Destination:
stderr
ERZ105010I Usage: cicsscdcreate { -? | -f

schemaFileName}
ERZ105025E cicscp failed to execute the program

programName, error number is
errorNumber
Explanation:
System action:
User response:
Destination:
stderr
ERZ105021I Usage: cicssfslock {-? | [ -l | -u | -t ] }
serverName
Explanation:
executing the program.
System action:
The command fails.
User response:
for the execvp() function and check the conditions for
the errorNumber value. On Windows NT, Check the
errorNumber value in the appropriate Microsoft Win32
manual.
Explanation:
This is the usage message for the cicssfslock
command.
Destination:
stderr
System action:
ERZ105026E The function of stream failed with

User response:
None.
Explanation:
manipulating the standard I/O streams during the
creation of a sub-process.
Destination:
stderr
ERZ105022E cicscp failed to allocate storage
Explanation:
This message is output when cicscp fails to allocate
general storage (not storage mentioned in one of the
other failed to allocate messages).
System action:
The command fails.
User response:
Retry the command. If it still fails then a system
resource limit was possibly reached. Consult the
493
ERZ105027E ERZ105037E
operating system documentation for the appropriate
function and check the conditions for the errorNumber
value.
Destination:
stderr
ERZ105027E stanza override must be of the form
attributeName=attributeValue
Explanation:
This message is output if cicscp fails to parse a string of
stanza file attribute overrides.

bytes failed
Explanation:
System action:
System action:
The cicscp command fails.
User response:
decreases and rerun the command. If the problem
log and console.
User response:
Correct the syntax and retry the command.
Destination:
stderr
Destination:
stderr
ERZ105031E Subsystem definition
subsystemName cannot be found
Explanation:
A subsystem definition for subsystemName was not
found. The most likely reason for this is that the server
name was entered incorrectly, or the subsystem
definition was prematurely deleted. Accompanying
messages identify the exact cause of the problem.
System action:
ERZ105035E Unexpected option option specified

on command line.
Explanation:
The option identified in the message was incorrectly
program. The program does not accept this option as a
parameter.
System action:
User response:
and respecify the options correctly.
User response:
Use accompanying to determine the cause of the
Destination:
stderr
Destination:
stderr
ERZ105036E Unexpected argument arguments

specified on command line.
ERZ105032W Subsystem definition for ShortName

shortName is already used by server
serverName
Explanation:
The argument identified in the message was incorrectly
program. The program does not accept this argument
as a parameter.
Explanation:
The ShortName attribute of a server must be unique
because it is used to generate the subsystem definition
name. shortName is already used by server
serverName.
System action:
User response:
Specify a unique ShortName value and retry the
command.
Destination:
stderr
494
System action:
User response:
and respecify the arguments correctly.
Destination:
stderr
ERZ105037E Option -option has already been
specified.
Explanation:
The option identified in the message was specified twice
in the command line to the executing program.
ERZ105038E ERZ105050I
System action:
User response:
Remove the extra options specified and attempt to
reexecute the command.
Destination:
stderr
ERZ105041E At least optionNumb of the following

options must be specified optionList
Explanation:
At least optionNumb of the options from the above list
must be specified.
System action:
ERZ105038E Option -option must have a matching

argument.
User response:
Respecify the command specifying the required options
Explanation:
The option identified in the message requires a
matching argument.
Destination:
stderr
System action:
User response:
Respecify the command specifying the argument
required by the command. If an argument was specified
but begins with a - it was possibly interpreted as an
option; in this case, use a double - to ensure it is
treated as an argument.
ERZ105042E Only one of the following options may

be specified optionList
Explanation:
Only one of the options from the above list can be
specified.
System action:
Destination:
stderr
User response:
Respecify the command specifying only one on the
options from the above list.
ERZ105039E The option -option must be specified.
Destination:
stderr
Explanation:
The option identified in the message must be specified.
System action:
User response:
Respecify the command specifying the missing option
Destination:
stderr
ERZ105040E At least one of the following options
must be specified optionList.
Explanation:
At least one of the options from the above list must be
specified.
System action:
User response:
Respecify the command specifying the required option
Destination:
stderr
ERZ105043E A maximum of optionNumb options

may be specified from optionList
Explanation:
A maximum of optionNumb options can be specified
from the above list.
System action:
User response:
Respecify the command specifying only the required
options with any appropriate arguments.
Destination:
stderr
ERZ105050I Usage: cicscpio { -? | [-v] [-r | -w] [-f
fileName]
Explanation:
System action:
User response:
Destination:
stderr
495
ERZ105051E ERZ105064W
ERZ105051E Error opening or closing file or
directory fileName, error number
errno
User response:
Explanation:
The command you entered tried to open or close file or
directory fileName but was unable to do so.
Destination:
stderr
System action:
User response:
Check that the file exists and has reasonable
permissions on it. If the file does not exist it is possible
that your command was trying to create it, in which
case check that the directory permissions are correct.
Check that the file is in a valid format and is not
corrupted. Use the error number for more information.
Destination:
stderr
ERZ105062W Unable to access details on user

userId
Explanation:
exact problem.
System action:
User response:
None
ERZ105052E Error writing to file fileName, error

number errno
Destination:
stderr
Explanation:
The command you entered tried to write to file
fileName but was unable to do so.
ERZ105063E Unable to access details on user

userId
System action:
User response:
Check that the specified file has the correct permissions
(if it exists) and that there is sufficient space in the file
system to write to it. Use the error number for more
information.
Destination:
stderr
ERZ105053E Error - bad archive file
Explanation:
The command you entered was unable to read the
archive file you specified.
System action:
User response:
Ensure you have given a valid archive file name. Check
also that the archive file you specified is not corrupted.
Destination:
stderr
Explanation:
System action:
496
Explanation:
exact problem.
System action:
value 1.
User response:
Ensure that user userId exists and retry the command.
Destination:
stderr
ERZ105064W Directory directoryName is not
exist
Explanation:
executable by userId or does not exist.
System action:
User response:
None
Destination:
stderr
ERZ105065E ERZ105071E
exist
Explanation:
executable by userId or it does not exist.
System action:
value 1.
User response:
Ensure directoryName exists and is readable, writable
and executable by userId.
Destination:
stderr
Explanation:
System action:
User response:
Destination:
stderr
ERZ105067E Unable to access details on user or
group userId
Explanation:
CICS was unable to access details on user or group
userId. This was probably because the user or group
does not exist. Previous messages identify the exact
problem.
System action:
User response:
Ensure that user or group userId exists and then rerun
the command. If it does not exist then ensure that CICS
is installed correctly.
Destination:
stderr
ERZ105068E Unable to get the current directory,
errno errorNumber.
Explanation:
The command you entered tried to find out which
directory you are in but was unable to do so.
Check that you have installed CICS correctly. Check the

value of errno for more information on the problem.
Destination:
stderr
ERZ105069E Unable to get information on file or
directory fileName, errno
errorNumber.
Explanation:
The command you entered tried to get information on
the specified file or directory but was unable to do so.
System action:
User response:
Check that the file or directory mentioned in the
message exists and that you have access to it. Check
that it is not corrupted. Refer to errno for more
information.
Destination:
stderr
ERZ105070E Error reading file fileName, errno
errorNumber.
Explanation:
The command you entered tried to read file fileName
but encountered an error.
System action:
User response:
Check the file is not corrupted. It is possible that the
command received a spurious signal, in which case try
the command again. Refer to errno for more
information.
Destination:
stderr
ERZ105071E Unable to alter permissions/owner of
file fileName, errno errorNumber.
Explanation:
The command you entered tried to alter the permissions
or the owner of fileName but was unable to do so.
System action:
User response:
Check that the file exists and that you have sufficient
priviledge to access it. Use the error number for more
information.
Destination:
stderr
System action:
User response:
497
ERZ105090E ERZ105099I
ERZ105090E Server serverName contacted but
server not fully operational
Explanation:
The current command was able to contact the server
identified in the message, but if failed to verify that the
server is fully operational.
System action:
The command cannot continue.
User response:
Verify that the server is running and has fully completed
its initialisation. When initialisation is fully complete
Destination:
stderr
ERZ105093E Server serverName started, but has
not been initialized
Explanation:
The Server serverName was started but was unable to
be initialized.
System action:
User response:
Verify that RPC is running, and use any previous
messages to help identify the problem. The server must
be shut down and restarted before it can be used.
Destination:
stderr
ERZ105094E Unable to start server serverName
Explanation:
The Server serverName was unable to be started.
System action:
value 1.
Use a different import file.

Destination:
stderr
ERZ105096E Unable to create link from
sourceFileName to targetFileName,
errno errno
Explanation:
You tried to import a file from an operating system that
supports links. When the file was created it was done
so using the link option of cicsexport. The command
tried to create the link but was unable to do so.
System action:
User response:
Use the error number errno to investigate why the
command failed. Correct the problem and rerun the
cicsimport command using the -F option. You can use
the -lo option to ignore this error.
Destination:
stderr
ERZ105097W Target targetFileName of symbolic
link sourceFileName does not exist
Explanation:
so using the link option of cicsexport. The command
found that the target file does not exist.
System action:
Since you specified the -lo option, the command
continues.
User response:
Ensure that the target exists before running the region.
Destination:
stderr
User response:
ERZ105099I ProtectionLevel checked for server

serverName
Destination:
stderr
Explanation:
The ProtectionLevel for the server was checked.
ERZ105095E Linked files detected - not supported

under Windows NT
Explanation:
so using the link option of cicsexport which is not
compatible in a Windows NT environment.
System action:
User response:
498
System action:
User response:
None
Destination:
stderr
ERZ105100E ERZ105108E
ERZ105100E Both primaryRestartFile and
backupRestartFile are missing for
server serverName
Explanation:
The server restart files were unable to be found.
System action:
value 1.
User response:
On an auto start of a server at least one of the restart
files must be available. If neither restart file is available,
you must cold start (initialize).
Destination:
stderr
ERZ105101W Restart file restartFileName is
missing for server serverName
Explanation:
The restart file restartFileName for server serverName
ERZ105105W The archives directory directoryName

Explanation:
The archives directory for the server does not exist but
is rebuilt.
System action:
Processing continues and rebuilds the archive directory.
User response:
None. The archive directory is rebuilt.
Destination:
stderr
ERZ105106E The archives directory directoryName
Explanation:
The archives directory for the server does not exist.
System action:
value 1
System action:
Processing continues using the other restart file.
User response:
Retry the command specifying the -I flag (ignore errors)
which causes the directory to be rebuilt.
User response:
None. The other restart file is rebuilt during server
startup.
Destination:
stderr
Destination:
stderr
ERZ105102I Restart files located for server
serverName
Explanation:
The restart files for the server were located.
System action:
User response:
None
Destination:
stderr
ERZ105104I Keytab file checked for server
serverName
Explanation:
The keytab file for the server was checked.
System action:
User response:
None
Destination:
stderr
ERZ105107I Archives directory located for server

serverName
Explanation:
The archives directory for the server was located.
System action:
User response:
None
Destination:
stderr
ERZ105108E Unable to find data for region
regionName
Explanation:
System action:
User response:
Destination:
stderr
499
ERZ105109E ERZ105117I
ERZ105109E Unable to read the CICS internal
inventory list
ERZ105116E fileName does not exist in the archive

- command terminating
Explanation:
The CICS internal inventory list is not readable by the
current user.
Explanation:
region archive.
System action:
error status.
System action:
Since you specifed the -lm option, the command
terminates.
User response:
Check that the CICS installation was successful. If
User response:
It is probable that the cicsexport command used to
create the archive file used one of the linking options
available to it. If this is as desired, retry the cicsimport
command using the -lo option, which creates the
desired link. If this is not the case, check that the CICS
installation was successful and that the region archive
file you are using is not corrupt. If you were running the
cicsimport command, prior to migrating your regions for
a new level of CICS, then ensure that the cicsmigrate
updates your region to add the missing file. If the
Destination:
stderr
ERZ105110E The CICS internal inventory list has
inconsistent data
Explanation:
The contents of CICS internal inventory are invalid and
cannot be used check region archives.
System action:
error status.
User response:
Destination:
stderr
ERZ105115W fileName does not exist in the
archive
Explanation:
region archive.
System action:
Since you did not specify the -lm option the command
continues. Since you did not specify the -lo option, the
specified file is simply ignored.
User response:
available to it. If this is as desired, retry the cicsimport
command using the -lo option, which creates the
desired link. If this is not the case, check that the CICS
installation was successful and that the region archive
file you are using is not corrupt. If you were running the
cicsimport command, prior to migrating your regions for
a new level of CICS, then ensure that the cicsmigrate
updates your region to add the missing file. If the
Destination:
stderr
500
Destination:
stderr
ERZ105117I fileName does not exist in the archive
- creating link
Explanation:
region archive.
System action:
Since you specified the -lo command, the link is
created and the command continues.
User response:
available to it in which case you need to do nothing. If
this is not the case, check that the CICS installation was
successful and that the region archive file you are using
is not corrupt. If you were running the cicsimport
command, prior to migrating your regions for a new
level of CICS, then ensure that the cicsmigrate updates
your region to add the missing file. If the problem
Destination:
stderr
Chapter 2. BHG...
BHG0001
The connection to the SMAPPL is

broken
Explanation:
An exception was caught during a method execution
that involved the Systems Management (smappl)
Server.
User response:
Shut down the eui and the smappl (if it is still running).
Then restart the smappl and after that the eui. Contact
IBM Service if this does not cure the problem.
Destination:
trace file & GUI dialog to the user
BHG0002
The EUI can not receive the requested

information from the SMAPPL
Explanation:
An attempt to obtain information from the smappl was
unsuccessful. Possibly there are problems with the
currently defined filter.
User response:
Modify the current filter and try the operation again. If
the operation continues to fail then shut down the
smappl, the involved resource controllers and the eui.
Then restart the smappl, the resource controllers and
the eui. Retry the operation. Contact IBM Service if this
does not cure the problem.
Check that the DSOM daemon is still running. Retry the

operation. Contact IBM Service if this does not cure the
problem.
BHG0050
The requested action cannot be

performed.
Explanation:
An internal problem in matching an action id with an
appropriate action.
User response:
Contact IBM Service.
Destination:
BHG0051
An internal error has occurred.
Explanation:
An internal check detected a data inconsistency.
User response:
Destination:
BHG0052
The EUI is unable to retrieve the

required information from the
customization network.
Destination:
Explanation:
The EUI and its customization network do not seem to
be on the same level.
BHG0003
User response:
Ensure that the EUI executable (bhgeui) and the
customization network (bhcust.net) stem from the same
installation image. If this does not solve problem then
contact IBM Service.
The EUI can not currently access this

object.
Explanation:
An attempt to navigate to this object has failed. It is
possible that the object may have been deleted.
User response:
Check if the object still exists by choosing a different
navigation route. Use the refresh action to update the
information. Retry the operation. Contact IBM Service if
this does not cure the problem.
Destination:
Destination:
Explanation:
There is no online help for this object.
BHG0004
User response:
A transient DSOM error has occurred.
BHG0100
The Help System could not find a help

entry for this object.
Explanation:
A requested DSOM service is currently unavailable.
Destination:
Explanation:
BHG0101
User response:
This panel does not provide further

information via the Help System.
Explanation:
501
BHG0300 BHG0351
There is no online help for this panel.
User response:
Destination:
BHG0300
CICS Agent Transaction: Exception

caught:
Explanation:
An exception was caught during execution of the CICS
Agent Transaction. The exception details follow this
message.
System action:
The CICS Agent Transaction is terminated. The
exception details are traced.
User response:
Contact IBM Service if unable to identify the problem
Destination:
stderr / message log
BHG0301
CICS Agent Transaction. Unidentified

exception caught.
Explanation:
Agent Transaction that is not recognized.
System action:
The CICS Agent Transaction is terminated
User response:
Destination:
BHG0302
CICS Agent Transaction could not

open the trace log: %1
Explanation:
The trace log for the CICS Agent Transaction could not
be opened.
System action:
The CICS Agent Transaction continues with trace
disabled.
System action:
The CICS Agent Transaction continues. Messages can
not be logged.
User response:
Check that the specified log has a valid file name
Destination:
BHG0310
Explanation:
Agent Transaction Terminator. The exception details
follow this message.
System action:
The CICS Agent Transaction may not be terminated.
CICS shutdown may be waiting for the CICS Agent
Transaction to terminate. The exception details are
traced.
User response:
You may need to perform a CICS immediate shutdown.
Destination:
stderr
BHG0311
BHG0303
CICS Agent Transaction could not

open the message log: %1
Explanation:
The message log for the CICS Agent Transaction could
not be opened.
502
CICS Agent Transaction Terminator.

Unidentified exception caught.
Explanation:
Agent Transaction Terminator that is not recognized.
System action:
The CICS Agent Transaction may not be terminated.
CICS shutdown may be waiting for the CICS Agent
Transaction to terminate.
User response:
You may need to perform a CICS immediate shutdown.
Destination:
stderr
BHG0351
User response:
Check that the specified log has a valid file name
Destination:
CICS Agent Transaction Terminator:

Exception caught:
Invalid invocation. Syntax: bhgcatst

region_name [start | stop | trace level |
trace_size size]
Explanation:
The program was invoked with incorrect parameters
System action:
The program exits
User response:
Destination:
stderr
BHG0353 BHG0605
BHG0353
CICS ECI call to region %1 to start

Agent Transaction failed. ECI response
code = %2. ECI system return code =
%3. ECI abend code = %4.
Explanation:
A CICS ECI call to the named region failed.
System action:
The CICS Agent Transaction will not have been started.
BHG0602
The EUI is unable to connect to the

default server.
Explanation:
A connection between the eui and the smappl could not
be established.
System action:
None - the error has already been handled.
User response:
User response:
Specify the name of a running server explicitly and try
again.
Destination:
stderr
Destination:
BHG0354
bhgcatst: Exception caught:
BHG0603
The EUI is unable to connect to server

called %1
Explanation:
Agent Transaction start/stop program. The exception
details follow this message.
Explanation:
A connection between the eui and the smappl could not
be established.
System action:
The program is terminated
System action:
None - the error has already been handled.
User response:
User response:
Pick a new server name and try again.
Destination:
stderr
Destination:
BHG0355
bhgcatst. Unidentified exception

caught.
Explanation:
Agent Transaction start/stop program. The exception
details follow this message.
System action:
The program is terminated
User response:
Destination:
stderr
BHG0601
BHG0604
Explanation:
The string provides feedback on an objects status.
Explanation:
Various GUI screens (resource string)
System action:
None. (no error)
User response:
None. (no error)
BHG0605
Folder
Explanation:
The string is appended to the name of objects which
are folders.
System action:
None. (no error)
User response:
None.
State is %1
Color is %1
Explanation:
Various GUI screens (resource string)
System action:
None. (no error)
User response:
Pick a new server name and try again
Destination:
None. (no error)
Destination:
Various GUI screens (resource string).
Chapter 2. BHG...
503
BHG0606 BHG0909
BHG0606
The EUI message catalogue is at level

%1 and the server at level %2
Explanation:
The individual product components are at different
service levels.
System action:
None - the error has already been handled
User response:
Check that the individual product components are
picked up from the same installation image. Contact
IBM service.
Destination:
BHG0733
Location %2
Explanation:
This message is used to show action events in the
event monitor. %3 becomes the date and time set at the
server where the event was raised.
System action:
None
User response:
As appropriate on message text.
Destination:
event monitor
BHG0734
Either add an entry to cicssm.config allowing this user

to run the EUI on this node, and then run cicssm
configure, OR, switch to a node/userid which is defined
to cicssm.
Destination:
console log and screen
BHG0808
Need root authority to perform this

action.
Explanation:
A cicssm server has been started by a non root user.
System action:
None
User response:
Stop the server and restart using the cicssm command.
Destination:
BHG0809
User did not have sufficient authority

for action.
Explanation:
A cicssm server has been started by a non root user.
System action:
None
User response:
Stop the server and restart using the cicssm command.
ERROR %1 Location %2
Explanation:
This message is used to show action events in the
event monitor. %3 becomes the date and time set at the
server where the event was raised.
Destination:
BHG0904
User needs root authority for this

action. %1 action quitting.
System action:
None
Explanation:
cicssm configuration has not been performed correctly.
User response:
As appropriate on message text.
System action:
None
Destination:
event monitor
User response:
Consult the configuration guide for information on
correct configuration of cisssm.
BHG0735
User %1 on host %2 is not defined to

CICS SM for AIX.
Explanation:
A user tried to start an EUI on a node where that user is
not defined. That is, the cicssm.config does not contain
an entry permitting this user to start an EUI on this
node.
System action:
Terminate the eui
User response:
Destination:
BHG0909
Explanation:
cicssm internal error
System action:
None
User response:
Contact IBM service
Destination:
504
%1 is not a recognized class. %2

action quitting.
BHG0926 BHG0946
BHG0926
Verify Configuration has failed.
Explanation:
Some problem was encountered during the activation of
a plex.
System action:
None
User response:
Review previous messages to determine the cause of
the problem. In general an object will have failed to
perform as expected.

Destination:
event monitor.
BHG0940
Install of %1 has failed.
Explanation:
Some problem was encountered the Install operation on
the object.
System action:
None
Destination:
event monitor.
User response:
Examine the object probably using the object editor to
BHG0928
Destination:
event monitor.
Make Target Configuration has failed.
Explanation:
a plex.
System action:
None
User response:
BHG0942
Initialization of %1 has failed.
Explanation:
Some problem was encountered the Initialization
operation on the object.
System action:
None
Destination:
event monitor.
User response:
BHG0929
Destination:
event monitor.
Drop object completed successfully.

930 %iE Drop object has failed.
Explanation:
a plex.
System action:
None
User response:
Destination:
event monitor.
BHG0932
Asynchronous command has failed.
Explanation:
a plex.
System action:
None
User response:
BHG0944
Start of %1 has failed.
Explanation:
Some problem was encountered the Start operation on
the object.
System action:
None
User response:
Destination:
event monitor.
BHG0946
Stop of %1 has failed.
Explanation:
Some problem was encountered the Stop operation on
the object.
System action:
None
User response:
Chapter 2. BHG...
505
BHG0 948 BHG1002

Destination:
event monitor.
Destination:
event monitor.
BHG0 959
BHG0 948
Terminate of %1 has failed.
Explanation:
Some problem was encountered the Terminate
operation on the object.
System action:
None
User response:
Destination:
event monitor.
Explanation:
An asynchronously operation client program failed. The
error is further described in the internal trace log
bhgback.trc.
System action:
None
User response:
Contact IBM service with bhgback.trc.
Destination:
console and message log.
BHG1000
BHG0950
Deinstall of %1 has failed.
Explanation:
Some problem was encountered the Deinstall operation
on the object.
bhgback failed - see trace log for

details.
The operation completed successfully
Explanation:
The SmAppl has completed an operation.
System action:
None
System action:
None
User response:
None - purely informational
User response:
Destination:
stderr or message log
Destination:
event monitor.
BHG1001
BHG0954
Addition of sfs schema %1 has failed.
Explanation:
Some problem was encountered the Addition operation
on the object.
User Information - unknown cause
Explanation:
The SmAppl has completed an operation. An
informational trace message has been produced in the
server where the operation completed.
System action:
None
System action:
None
User response:
User response:
Destination:
Destination:
event monitor.
BHG1002
BHG0956
Deletion of sfs schema %1 has failed.
Explanation:
Some problem was encountered the Deletion operation
on the object.
Navigation has crossed to another

domain
Explanation:
The object to which you have just navigated is in a
different server to that in which you started.
System action:
None
System action:
None
User response:
User response:
Destination:
506
BHG1003 BHG1402
BHG1003
Asynchronous command has been

started successfully
Explanation:
The SmAppl has started an operation. On completion
there will usually be a message sent to the event
server.
System action:
None
User response:
Destination:
BHG1203
Explanation:
Two objects are already related. This is only a problem
if the user does not expect them to be.
System action:
None
User response:
Suspect that another user has related them.
Destination:
BHG1400
BHG1200
User Warning - unknown cause
Explanation:
The SmAppl has produced some trace in the server
where the operation completed. It details some
unexpected conditions which were handled.
System action:
None
User response:
As appropriate based on the trace information.
Destination:
BHG1201
The two subjects are not related by the

given relationship
Attempt to insert a duplicate

relationship ignored
User parameter error - unknown cause
Explanation:
The SmAppl has returned a non-zero return code to the
client having failed to perform some operation. The
problem was in the parameters passed to the operation.
System action:
User response:
Either correct the parameter value or correct the
problem in the client code. If the client code is part of
the CICSSM product (eg the EUI) contact IBM service.
Destination:
BHG1401
Unsupported/Illegal type
Explanation:
The unrelate operation found that the two objects were
not related. This is only a problem if the user was
expecting them to be related.
Explanation:
Parameters must be of the type specified by their
method. In general these will be long, float, string or
enumerations.
System action:
None
System action:
User response:
If the two subjects should be related then suspect that
some other user has deleted the relationship.
User response:
Destination:
BHG1202
Attribute composition error - no related

object to set attributes of
Destination:
BHG1402
Instance not found
Explanation:
The composed object (probably a connection) was
incomplete and hence its attributes could not be set.
Explanation:
You have tried to navigate to an object with a name
which can not be located.
System action:
None
System action:
User response:
None
User response:
problem in the client code. This may also be caused by
another user deleting the object.
Destination:
Chapter 2. BHG...
507
BHG1403 BHG1410
Destination:
Destination:
BHG1403
BHG1407
Non unique instance name
Explanation:
It is not possible to create two objects with the same
name in a given folder.
System action:
User response:
Choose a new name. The problem may be caused by
another user creating the object just before you.
Destination:
BHG1404
System action:
User response:
Either correct the attribute name or correct the problem
in the client code. If the client code is part of the
CICSSM product (eg the EUI) contact IBM service.
Destination:
Internal restriction (bh_nav_both)
Explanation:
The API currently does not allow this usage.
System action:
User response:
Destination:
BHG1406
Cardinality error - there is already a

forward relationship
Explanation:
A relationship has been defined one to one or one to
many. The addition of this relationship would break that
constraint.
System action:
None - the relationship is not inserted.
User response:
Do not add the relationship twice.
508
Explanation:
A relationship has been defined one to one or one to
many. The addition of this relationship would break that
constraint.
System action:
None - the relationship is not inserted.
User response:
Do not add the relationship twice.
Destination:
Attribute name not valid for this object
Explanation:
The attribute you are trying to get or set is not defined
on the object.
BHG1405
Cardinality error - there is already a

reverse relationship
BHG1408
Illegal relationship requested
Explanation:
The object does not support a relationship of the given
name.
User response:
Either correct the relationship name or correct the
Destination:
stderr / message log System Action : None - the error
has already been handled
BHG1409
Action not valid for this object
Explanation:
The object does not have an action of the given name.
System action:
User response:
Either correct the action value or correct the problem in
the client code. If the client code is part of the CICSSM
product (eg the EUI) contact IBM service.
Destination:
BHG1410
NULL or blank instance name not

allowed
Explanation:
Objects may not have a name which is a blank or NULL
string.
User response:
Either correct the name or correct the problem in the
client code. If the client code is part of the CICSSM
Destination:
BHG1411 BHG1419
stderr / message log System Action : None - the object
is not created or renamed
Destination:
BHG1411
BHG1416
Conditionality error - the object has

some relationships missing
Clone x cannot be created since node

y is unknown
Explanation:
The object has some relationships which must exist.
They do not currently exist when verified.
Explanation:
The named node given as a parameter cannot be
located.
System action:
System action:
User response:
Add the required relationships.
User response:
Correct the node name and retry the operation.
Destination:
Destination:
BHG1412
BHG1417
Named Object not known to server
Explanation:
An object cannot be located in a given server. It may
have been deleted by another user.
System action:
User response:
Suspect deletion by another user. Otherwise this may
indicate some internal error.
Destination:
BHG1413
Wrong class of related object
Explanation:
The objects given cannot be related since one of them
has the wrong class (eg a file not a program) to take
part in the given relationship.
User response:
Destination:
BHG1414
Instance name contains an illegal

character
Explanation:
Objects impose individual rules on the allowable
characters in their names. Refer to individual object help
for details.
System action:
User response:
Remove the offending characters in the name and retry
the operation.
Destination:
BHG1418
View name not valid for this object
Explanation:
The object does not have a view of the given name.
System action:
User response:
Either correct the view name or correct the problem in
Destination:
Node name not known to server
Explanation:
An object in the server has a relationship to another
object in a server which is unknown (not in the DSOM
Implementation repository).
System action:
User response:
This is probably caused by a configuration change in
which a server has been removed. Correction of this
error will probably require IBM assistance.
BHG1419
Too few input parameters provided
Explanation:
The method signature calls for more parameters than
provided.
User response:
Either provide more parameters or correct the problem
in the client code. If the client code is part of the
CICSSM product (eg the EUI) contact IBM service.
Destination:
Chapter 2. BHG...
509
BHG1420 BHG1601
stderr / message log System Action : None - the method
is not invoked.
Restart the server. If the server has not failed then

suspect some communication failure. Resolve with the
assistance of the cicssm ping command.
BHG1420
Destination:
Too many input parameters provided
Explanation:
The method signature calls for less parameters than
provided.
User response:
Either provide less parameters or correct the problem in
Destination:
BHG1421
Incorrect name syntax for a contained

name
Explanation:
A full name does not meet the requirements of such
names. Only object names given out by cicssm should
be used to locate objects.
System action:
User response:
Either correct the name or correct the problem in the
client code. If the client code is part of the CICSSM
Destination:
BHG1422
BHG1424
Explanation:
A readonly attribute may not have its value altered by
calls to the set attribute API.
System action:
User response:
Correct the in the client code. If the client code is part of
Destination:
BHG1425
System action:
User response:
Either correct the name value or correct the problem in
Destination:
Explanation:
Some objects such as system images may only be
associated with one other object eg a Plex.
System action:
User response:
Either rename the object or dissociate it with the other
object (eg remove the image from the other Plex).
Destination:
BHG1600
User response:
Suspect that some other user is currently operating on
the the object.
Destination:
Remote server probably inactive
Explanation:
A server has failed to communicate with another server.
This could be due to server failure, server not started or
some communications failure between the AIX systems.
System action:
User response:
User state error - unknown cause
Explanation:
An object is in an incorrect state to perform the
operation.
BHG1601
510
x is already associated with y
Sever name not defined to DSOM
Explanation:
A named server cannot be located in the
Implementation Repository.
BHG1423
Readonly attribute cannot be changed
The object is in the wrong state to

perform this operation
Explanation:
An object is in an incorrect state to perform the
operation.
User response:
Suspect that some other user is currently operating on
the the object.
Destination:
BHG1602 BHG1608
BHG1602
The attribute could not be retrieved

from the object
Explanation:
Some attributes can only be retrieved from an object
once it has been installed or started. This error indicates
that some such condition has occurred.
System action:
User response:
If the attribute is definitional then ensure the object is
more than just created. If operational ensure that it is
up (running).
Destination:
BHG1603
The attribute value could not be

changed in the object
Explanation:
System action:
User response:
up (running).
Destination:
BHG1604
The managed system would not

process the request - see error code in
log.
Explanation:
This indicates that CICSSM could not communicate an
attribute change to the managed system. It may indicate
an installation error (insufficient server authority etc.).
Generally it indicates that the managed system has
failed in some way.
BHG1605
A system or resource must be in the

up state before its operational
attributes can be accessed.
Explanation:
System action:
User response:
Ensure that the object is in the up state.
Destination:
BHG1606
A system or resource must have been

installed before its definitional
attributes can be accessed.
Explanation:
System action:
User response:
Ensure that the object is in more than the created
state.
Destination:
BHG1607
Cannot communicate with managed

system - see error code in log.
Explanation:
System action:
User response:
up (running).
System action:
Destination:
User response:
If this installation is new suspect authorization, if not
than suspect some failure of the managed system.
BHG1608
Destination:
Object must be in created state to

delete it.
Explanation:
Objects can only be deleted if they are stateless or
have state and it is created. Objects which they contain
must obay the same restrictions.
User response:
Chapter 2. BHG...
511
BHG1609 BHG1700
If the object is not created then stop, terminate and
then deinstall it before retrying the operation.
System action:
Destination:
User response:
Wait till the asynchronous operations complete before
retrying the operation.
BHG1609
Destination:
Object must be in created state to

rename it.
Explanation:
Objects can only be renamed if they are stateless or
have state and it is created.
System action:
User response:
If the object is not created then stop, terminate and
then deinstall it before retrying the operation.
Destination:
BHG1610
Object is in broken state and needs

manual intervention.
Explanation:
Some failure has occurred in the managed system. This
usually means that it failed to start or stop in a
reasonable time.
System action:
User response:
Investigate the cause of the failure using eg the tail log
commands.
Destination:
BHG1613
An object has been locked to prevent

alteration.
Explanation:
Some operations place locks on objects to prevent
alteration while an operation is in progress. Changes
are prevented during these periods.
System action:
User response:
Wait till the asynchronous operations complete before
retrying the operation. Note that the active topology is
locked to prevent alteration. This can cause actions
such as propagation of template attributes to fail.
Destination:
BHG1614
Attribute propagation failed for x

objects.
Explanation:
Some of the objects to which attributes were
propagated were unable to be completely updated. This
will usually be because an object is locked (eg the
active configuration).
System action:
Explanation:
This operation requires the object to be at least installed
in order to succeed.
User response:
Usually none. Propagation to the locked object can be
achieved by unlocking the object in question and then
repeating the operation. Note that locks are usually
placed for a good reason and unlocking should be
unusual.
System action:
Destination:
User response:
Ensure that the object is not created. If so then install it
and retry the operation.
BHG1700
BHG1611
Object must be more than just created

to allow this operation.
Destination:
BHG1612
An activate is already in progress.
Explanation:
Some operations are prevented while long-running tasks
such as the activation of an active topology are
proceeding.
512
Event notification lost in management

application. reason code : reason-code
Explanation:
the queue_event method of bh_event_manager
(bhevtman.c) was unable to add this notification onto its
queue due to a semaphore (code 1) or application
(code 2) problem.
System action:
none - the loss of an event notification is not fatal
User response:
BHG1701 BHG1707
contact ibm service
Destination:
BHG1701
Events buffer is full, oldest events will

be lost. either 1) the number of
subscriptions is too great or 2) the
event receiving process has died.
Explanation:
the outstanding events queue of bh_event_manager
(bhevtman.c) has more than max_event_queue_size
msgs.
System action:
User response:
reduce number of concurrent subscriptions. if event
receiving process has died contact ibm service
Destination:
BHG1702
Could not initialize event forwarding

process. No notifications will be sent.
reason code reason-code
Explanation:
init_event_manager failed to start the bh_event_server
process. code 1 = ftok failure code 2 = could not get
semaphore code 3 = could not start process
System action:
none - the loss of an event notifications is not fatal
User response:
contact ibm service. bighorn will continue to run
normally, but no event notifications will be sent.
BHG1704
semaphore error
Explanation:
bh_event_server wait on semaphore failed
System action:
User response:
normally, but event notifications may be lost.
Destination:
BHG1705
could not deliver event to x.
Explanation:
bh_event_server deliver_event failed code 1 = error
retrieving event from smappl
System action:
User response:
Destination:
BHG1706
som error trapped in bh_event_server:

code code, file file, line line
Explanation:
bh_event_server caught a som error
System action:
terminate bh_event_server for a base som error
message whose last digit is 9, otherwise do nothing.
Destination:
User response:
BHG1703
Destination:
message log
invalid invocation of event server
Explanation:
bhgevsrv process initialization failed wrong number of
arguments
System action:
User response:
normally, but no event notifications will be sent.
Destination:
BHG1707
could not open message log log
Explanation:
bhgevtsrv process could not open its message log
System action:
carry on, no messages will be written
User response:
Check that the file system is not full, and that the
bhgevsrv process has permission to create a file in the
log directory
Destination:
stderr
Chapter 2. BHG...
513
BHG1708 BHG1719
BHG1708
dsom error detected: som exception

type type. som error code code.
Explanation:
bhgevtsrv
System action:
The next message in the message log will detail the
action to be taken by the system. user response : See
next error message in file for any action necessary
Destination:
stderr,message log
BHG1709
BHG1716
Explanation:
the bhgevtsrv could not get a server object for the
SMAppl
System action:
terminate the bhgevtsrv process user response :
bighorn will continue to run, but no events will be sent.
Contact IBM service.
Destination:
starting event server

BHG1717
BHG1710
som error trapped: code code, file file,

line line
Explanation:
the server caught a som error
System action:
the server will terminate if this is a severe dsom error
whose last digit is 9, otherwise do nothing.
User response:
Destination:
invalid semaphore id id
Explanation:
the semaphore id passed as an argument to bhgevtsrv
could not be parsed
System action:
terminate the bhgevtsrv process
User response:
Destination:
System action:
terminate the bhgevtsrv process
User response:
Destination:
event server initialization complete
BHG1713
event server terminating
BHG1714
BHG1715
event server termination complete

event server received signal x
Explanation:
bh_event_server deliver_event failed code 2 = failed to
get client server object
System action:
User response:
Destination:
BHG1719
BHG1712
unable to create bh_event_manager

object
Explanation:
the bhgevtsrv could not get the events object in the
SMAppl
BHG1718
BHG1711
alias alias does not exist in the

implementation repository
Explanation:
bh_event_server deliver_event failed code 3 = failed to
get client bh_channel_receiver object
System action:
User response:
Destination:
514
BHG1720 BHG1728
BHG1720
Explanation:
bh_event_server deliver_event failed code 4 = client
error in receiving event
System action:
User response:
BHG1724
Event process sent unexpected

message x
Explanation:
The bhgeuevt process sent an unexpected message to
the EUI
System action:
Log exception and carry on
User response:
Report to ibm service - this is an abnormal situation
Destination:
Destination:
BHG1721
BHG1725
Could not start event receiving

process (fork failed)
Explanation:
The EUI could not fork a process to start the event
listening process bhgeuevt.
System action:
Shutdown EUI
Could not get event
Explanation:
The event process sent a message to the EUI to say an
event was waiting, but the EUI was unable to collect it.
System action:
User response:
contact ibm service.
User response:
Report to IBM service. An event has been lost, but the
EUI will continue to run
Destination:
Destination:
BHG1722
BHG1726
Could not communicate with event

receiving process
Could not get message from SMAppl
Explanation:
The EUI successfully forked its event receiving process,
but then failed to communicate with it.
Explanation:
The event process sent a message to the EUI to say a
message from the smappl was waiting, but the EUI was
unable to collect it.
System action:
Shutdown EUI
System action:
User response:
contact ibm service.
User response:
Report to IBM service. A message from the smappl has
been lost, but the EUI will continue to run.
Destination:
BHG1723
Event receiving process not yet

initialized. Wait 5 seconds and try
again.
Explanation:
The EUI successfully forked its event receiving process,
and is waiting to communicate with it.
System action:
None
User response:
This message is for information only. The EUI will retry
up to five times before giving up.
Destination:
Destination:
BHG1728
Event process terminated

unexpectedly. The EUI is shutting
down.
Explanation:
The event process bhgeuevt terminated unexpectedly.
The EUI cannot continue and will shutdown.
System action:
Shutdown EUI
User response:
Report to IBM service. Try restarting the EUI, if the error
persists, then run cicssm clean somdd.
Destination:
Chapter 2. BHG...
515
BHG1800 BHG1807
BHG1800
User error - unknown cause
Explanation:
Some unspecific problem has been found with the
operation that is being attempted. Usually there will be
more information in the server trace files.
System action:
User response:
Wait some time before retrying the operation. If the
problem persists examine the server console log.
Destination:
BHG1801
This operation doesnt work on a

container
Explanation:
The object being operated upon is a container of other
objects. The operation cannot be performed on this
container.
System action:
User response:
Suspect an error in client code. A previous navigation
error may be causing it to reference an incorrect object
or the code may be faulty.
Destination:
BHG1802
This operation doesnt work on a

relationship container
Explanation:
The object being operated upon is a container of other
objects. The operation cannot be performed on this
container.
System action:
User response:
Destination:
BHG1803
The server owning the object doesnt

have ROOT authority
Explanation:
The server has not been started with root authority.
System action:
User response:
516
Shutdown the server in question and restart using the

correct procedure using the cicssm script from a shell
with root authority.
Destination:
BHG1805
A CICSSM shell script was passed

incorrect parameters by the server
Explanation:
This is in internal error which may be provoked by
installation or configuration problems.
System action:
User response:
The server log will contain the name of the script which
failed and the parameters it was passed. Suspect that
the server was started with a PATH which contained a
non-CICSSM shell script of the same name (resolve
using the which command).
Destination:
BHG1806
A CICSSM shell script failed to create

the requested resources
Explanation:
The managed system was unable to complete an
operation.
System action:
User response:
Examine the server log and correct the underlying
cause of the problem. Usually it is lack of machine
resource eg disk.
Destination:
BHG1807
A CICSSM shell script failed to update

the requested resources
Explanation:
operation.
System action:
User response:
resource eg disk.
Destination:
BHG1808 BHG1814
BHG1808
Some file(s) do not exist, probably the

object is not in the correct state or has
been deleted by commands outside
CICSSM.
Explanation:
This is generally caused by users making resource
changes without involving CICSSM. The result will be
that CICSSM becomes out of date and assumes that
files still exist.
System action:
User response:
The server log will contain the name of the script which
failed and the parameters it was passed. Suspect that
another user has deleted the object using system
commands. It is also possible that files eg console.msg
have not yet been created by the cics system.
Destination:
BHG1809
A CICSSM shell script failed to

complete the request
Explanation:
operation.
System action:
User response:
resource eg disk.
System action:
User response:
Suspect that some relationships are missing eg a half
connection must have an other half relationship.
Destination:
BHG1812
The drop operation is not defined for

this pair of objects
Explanation:
This message indicates that the particular drop
operation does not mean anything. It may be that you
intended to perform the drag/drop the other way around.
System action:
User response:
If you think that the operation you are attempting should
be meaningful then try it in the other direction. If this
message re-occurs then consult the user guide which
lists the valid drag/drop operations for objects.
Destination:
BHG1813
Server already running
Explanation:
Once a server is running a subsequent attempt to start
the server will fail with this message.
System action:
Destination:
User response:
Do not continue to start the server.
BHG1810
Destination:
An asynchronous request failed
Explanation:
operation.
System action:
User response:
This may indicate that the machine was unable to fork a
new process in order to deal with the work request.
Examine the server log to discover the likely cause.
Destination:
BHG1811
Attribute composition error - no related

object to compose from
BHG1814
Multi-object operation failed partially.
Explanation:
An operation on multiple objects was partially
successful.
System action:
User response:
Examining the individual objects will indicate which of
them was unsuccessfully operated upon. In active
topology for example you should try to activate
individual topology elements in order to get a more
detailed picture of the problem.
Destination:
Explanation:
A composed object such as a connection was found to
be incomplete. Hence it does not have any attributes.
Chapter 2. BHG...
517
BHG1815 BHG1822
BHG1815
Multi-object operation failed

completely.
BHG1819
The model is already defined by a

template
Explanation:
An operation on multiple objects failed in all cases.
Explanation:
A model can only be defined by a single template.
System action:
System action:
User response:
Examining the individual objects will indicate why they
failed. In active topology for example you should try to
activate individual topology elements in order to get a
more detailed picture of the problems.
User response:
If you wish to change the template to model association
you must first use the object editor to delete the existing
association.
Destination:
Destination:
BHG1820
BHG1816
Clone not on a node - model x clone y
Explanation:
A clone has not been configured on a node.
System action:
User response:
Drag the system clone and drop it onto the node you
wish to have the installed system.
Destination:
BHG1817
Clone on multiple nodes - model x

clone y
Explanation:
A clone has been incorrectly configured on multiple
nodes.
This folder is already at its maximum

size
Explanation:
Some folder objects have a limit on the number of
objects they may contain. Once at the limit no further
objects can be added.
System action:
User response:
If you wish to add an object to this folder you must first
remove one of the existing objects.
Destination:
BHG1821
The operation has been canceled
Explanation:
An operation was canceled by a user before completion.
System action:
System action:
User response:
Using the object editor delete all the nodes which you
do not want the system clone to be on. It can only be
on a single node.
User response:
None.
Destination:
BHG1818
Program model not configured on

system model
Explanation:
A transaction model has been configured to have a first
program which is not itself configured on the system.
The transaction would thus fail.
Destination:
BHG1822
This operation only works on a

container
Explanation:
Some operations only work on containers which hold
multiple objects.
System action:
User response:
Correct the problem by dropping the program model on
the appropriate system model.
User response:
Destination:
Destination:
518
BHG1823 BHG2002
BHG1823
Failed to get source attributes
Explanation:
An internal error caused the attributes of a source
object to be unavailable during a copy operation.
System action:
User response:
Examine the objects in question and suspect that their
state is incorrect or that the managed system has failed
in some way.
Destination:
BHG1824
Failed to get target attributes
Explanation:
An internal error caused the attributes of an object to be
unavailable during a copy operation.
System action:
User response:
Examine the objects in question and suspect that their
state is incorrect or that the managed system has failed
in some way.
Rename or delete one of the duplicate clones.

Destination:
BHG1827
Rename not allowed on objects which

may be remote
Explanation:
Objects such as Nodes cannot be renamed since this
would cause severe confusion to the end user.
System action:
User response:
If the name is a serious problem then the object must
be deleted and created with the new name.
Destination:
BHG2000
Smappl Error - unknown cause
Explanation:
Examine the server console logs for the cause of the
problem.
System action:
Trace or console messages will have been produced.
Destination:
User response:
Look at the console messages for the cause of the
problem. If that fails call IBM service.
BHG1825
Destination:
Connection incomplete - system model

x half connection model y
Explanation:
A half connection model does not have a relationship to
another half connection model. This prevents a
connection being made between the appropriate clones.
System action:
Verification of the configuration fails immediately.
User response:
Relate the half connection model to the appropriate
other half connection by drag/drop or object editor.
Revalidate the configuration to check that the problem
has been corrected.
Destination:
BHG1826
BHG2001
Internal server error : bh_exception.

Please save the server trace logs and
contact IBM service.
Explanation:
problem.
System action:
User response:
Destination:
Duplicate clone - model x clone y
Explanation:
More than one clone of a CICS system or SFS server
has been found with a given name. The model and
clone names of the second instance are given in the
message.
System action:
Verification of the configuration fails immediately.
User response:
BHG2002
Internal server error : generic

exception. Please save the server trace
logs and contact IBM service.
Explanation:
problem.
System action:
Chapter 2. BHG...
519
BHG2003 BHG2013
User response:
Destination:
Destination:
BHG2010
BHG2003
Explanation:
An Internal error has occurred.
Attempt to get attributes has failed
Explanation:
problem.
Internal server error : missing. Please

save the server trace logs and contact
IBM service.
System action:
System action:
User response:
Contact IBM service with the console and trace logs.
User response:
Destination:
Destination:
BHG2011
BHG2005
Remote server name not found in

Explanation:
This indicates a configuration problem.
System action:
User response:
Refer to the configuration guide for further information
on correctly configuring CICSSM.
Destination:
BHG2006
Remote server metaclass not found
Explanation:
System action:
User response:
Destination:
BHG2007
System command failed to start a shell
Explanation:
problem.
System action:
User response:
This is probably caused by the AIX system being unable
to create a new process.
520
Subscription filter creation failed
Explanation:
System action:
User response:
Destination:
BHG2012
Subscription attempt failed
Explanation:
System action:
User response:
Destination:
BHG2013
Unsubscribe attempt failed
Explanation:
System action:
User response:
Destination:
BHG2020 BHG2029
BHG2020
Starting server
BHG2024
Initialization complete
Explanation:
A server is starting.
Explanation:
A server has completed its initialization and is ready.
System action:
None.
System action:
None.
User response:
None.
User response:
None.
Destination:
Destination:
BHG2021
BHG2025
Unable to find specified alias in

implementation repository. SOM
exception type %2. SOM error code
%3.
Explanation:
System action:
User response:
Destination:
BHG2022
No alias specified. Usage: %1 -a alias
Explanation:
A server has been invoked with incorrect parameters.
System action:
Shutting down server
Explanation:
A server has been requested to shutdown.
System action:
None.
User response:
None.
Destination:
BHG2026
SOM Error trapped: Code %2, File %3,

Line %4
Explanation:
The server caught a SOM Error
System action:
The server will terminate if this is a severe DSOM error
whose last digit is 9, otherwise do nothing.
User response:
Contact IBM Service. Event notifications may be lost.
User response:
If the cicssm command is used to start servers this
message should not appear.
Destination:
Destination:
BHG2028
BHG2023
Unable to activate implementation for

specified alias. SOM exception type
%2. SOM error code %3.
Explanation:
System action:
User response:
Destination:
Server alias is already active.
Explanation:
A server which is already running has been requested
to start.
System action:
None.
User response:
Do not repeat the start command.
Destination:
BHG2029
Shutdown of server is complete
Explanation:
A server has completed shutdown.
System action:
None.
Chapter 2. BHG...
521
BHG2030 BHG2037
User response:
None.
Destination:
BHG2030
Exception caught:
Explanation:
An exception was caught during execution of the server
. The exception text follows this message
BHG2034
Active cursor: user: %2 host: %3

identifier: %4
Explanation:
A client was found to be using the server during
shutdown.
System action:
The server completes termination
System action:
The server is terminated
User response:
The message notes the client affected. The client
process may wait for the duration of SOMDTIMEOUT
before completing.
User response:
Destination:
Destination:
BHG2035
BHG2031
Unidentified exception caught.
Explanation:
An exception was caught during execution of the server
System action:
The server is terminated
User response:
Destination:
BHG2032
Problem opening Instance database

%1
Explanation:
The server was unable to open or create an instance
database during startup.
System action:
The server terminates
User response:
This is usually a configuration problem. Suspect
permissions or lack of file space. The server console
may have more information.
Destination:
could not open message log: %2
Explanation:
The message log for the server could not be opened.
BHG2036
System action:
The SMAppl continues. Messages can not be logged.
Explanation:
The server was unable to open the data dictionary
during startup.
User response:
Check that the specified log has a valid file name, and
that the fils permissions and file system space are OK
Destination:
BHG2033
No remaining active cursors
Explanation:
The server which is shutting down has no clients.
System action:
The server completes termination
User response:
None.
Destination:
Problem opening Dictionary database

%1
System action:
User response:
This indicates a configuration problem. Suspect that the
CICSSM installation was incorrect or that the server has
been started manually (not using the cicssm script).
Destination:
BHG2037
Server received signal %2
Explanation:
The server was sent a signal by AIX.
System action:
As appropriate to the signal.
User response:
If the signal is SIGSEGV then contact IBM service with
the console and trace logs.
522
BHG2038 BHG2100
Destination:
BHG2038
Commencing server detection and

registration
Explanation:
The server is about to interact with DSOM.
System action:
None.
BHG2042
Communication failed to CICS

region:%1 type:%2 name:%3 rc:%4
Explanation:
The server has failed to communicate with a managed
system.servers.
System action:
None.
User response:
None.
User response:
Suspect that the BHGA transaction has encountered
problems. This can be rectified by stopping and
restarting the managed system.
Destination:
Destination:
BHG2039
BHG2043
Server detection and registration

complete
Explanation:
The server has successfully registered with DSOM.
System action:
None.
User response:
None.
Problem opening Annotation Database

%1
Explanation:
The server was unable to open or create an annotation
database during startup.
System action:
Destination:
User response:
This is usually a configuration problem. Suspect
permissions or lack of file space. The server console
may have more information.
BHG2040
Destination:
Broadcasting server shutdown
Explanation:
The server is broadcasting its shutdown to other
servers.
System action:
None.
User response:
None.
Destination:
BHG2041
Server shutdown broadcast complete
Explanation:
The server has completed broadcasting its shutdown to
other servers.
BHG2044
Class Initialization starting
Explanation:
The server is about to initialize the supported classes.
System action:
None.
User response:
None.
Destination:
BHG2100
Object deleted - detected on REAL

OBJECT
System action:
None.
Explanation:
The Server has been asked to reference a deleted
object.
User response:
None.
System action:
None
Destination:
User response:
The client must stop referencing the object.
Destination:
Chapter 2. BHG...
523
BHG2101 BHG2304
BHG2101
Object deleted - detected on a cursor

object
Explanation:
The Server has been asked to reference a deleted
object.
System action:
None
User response:
The client must stop referencing the object.
Destination:
BHG2200
A Server operation returned code %1
Explanation:
minor code is the result of some operation performed by
the SmAppl and may give additional information.
Destination:
BHG2301
Client has passed data with value

outside specified range
Explanation:
The value being set exceeds the allowed range.
System action:
None
User response:
Change the value of the parameter.
Destination:
BHG2302
Client has passed data with incorrect

TypeCode specified.
Explanation:
The value being set is of the wrong type.
System action:
None
System action:
None
User response:
Suspect that the managed system has failed.
User response:
Change the type of parameter being passed.
Destination:
Destination:
BHG2201
BHG2303
A Server operation returned code %1
Explanation:
minor code is the result of some operation performed by
the SmAppl and may give additional information.
System action:
None
User response:
Suspect that the managed system has failed.
Destination:
BHG2300
Client error - unknown cause
Explanation:
indications are that the problem was caused by faulty
client code which has sent data which doesnt match
the interface specification eg incorrect typecode or a
value outside the max/min range.
System action:
None
User response:
Reconsider the parameters passed to the operation.
524
Cursor is not connected to a SMAppl

or Resource Controller
Explanation:
The cursor has not been initialized correctly.
System action:
None
User response:
Suspect that the object has never been created.
Destination:
BHG2304
DSOM has not been initialized
Explanation:
The SOM_InitEnvironment(e) and or SOMD_Init(e) is
required.
System action:
None
User response:
Consult the API manual for the correct initialization.
Destination:
BHG2305 BHG2502
BHG2305
The server alias could not be found in

the implementation repository
Explanation:
All servers must be defined in the DSOM
Implementation Repository which is done during
configuration.
System action:
None
User response:
Consult the installation and configuration guide.
Destination:
BHG2306
The server was not activated
Explanation:
The Information in the DSOM Implementation
Repository may be preventing server activation.
System action:
None
User response:
Consult the installation and configuration guide.
Destination:
BHG2400
Thread restriction on navigation
Explanation:
One or more of the servers is single threaded and this
causes problems with some two-object operations.
System action:
None
User response:
Destination:
BHG2500
Must have root authority to run this

program.
Explanation:
The discovery program has been invoked by a user
other than root.
System action:
The program exits
User response:
This program should only be invoked from a Resource
Controller which, if started correctly using the
cicssmcommand, will have the correct authority.
Destination:
Thread restriction
Explanation:
System action:
None
User response:
Destination:
BHG2401
BHG2402
Thread restriction on dropped object
Explanation:
System action:
None
User response:
Destination:
BHG2501
Unrecognized option entered.
Explanation:
The discovery program has been invoked with an invalid
syntax.
System action:
The program exits
User response:
Controller which should invoke it correctly. Contact IBM
Service if unable to identify the problem
Destination:
BHG2502
DSOM initialization failed. Return code

%1
Explanation:
The discovery program was unable to initialize DSOM.
System action:
The program exits
User response:
The Resource Controller console log may contain
messages from DSOM that identify the problem.
Destination:
Chapter 2. BHG...
525
BHG2503 BHG2511
BHG2503
DSOM initialization completed.
Explanation:
Information only
System action:
None
User response:
None $
Destination:
stdout / message log
BHG2504
Discovering all regions on this node.
Explanation:
Information only
System action:
None
User response:
None
Destination:
BHG2508
Updating information about remote

systems relations.
Explanation:
Information only
System action:
None
User response:
None
Destination:
User response:
None
BHG2509
Destination:
Explanation:
Information only
BHG2505
System action:
None
Discovering selected regions on this

node.
Explanation:
Information only
System action:
None
Attempting to set the states of all

discovered objects.
User response:
None
Destination:
User response:
None
BHG2510
Destination:
Explanation:
The discovery program was unable to uninitialize
DSOM.
BHG2506
System action:
The program exits
Updating information about local

relations.
Explanation:
Information only
System action:
None
User response:
None
Destination:
BHG2507
Updating systems connection

information.
Explanation:
Information only
System action:
None
526
Problem encountered during DSOM

termination phase.
User response:
The Resource Controller console log may contain
messages from DSOM that identify the problem.
Destination:
BHG2511
Discovery process complete.
Explanation:
Information only
System action:
None
User response:
None
Destination:
BHG2512 BHG2601
BHG2512
Recognized syntax :-\n\ %1 server

node-object_id -a | -r [...] | -x [...]\n\
Where [...] is a list of cics region
names.
Explanation:
Information only
System action:
None
User response:
None
Destination:
BHG2514
System action:
The program exits
User response:
Destination:
Failed to find the given node in object
network.
Explanation:
The discovery program has caught an exception. The
exception description follows this message.
System action:
The program exits
User response:
Destination:
BHG2519
Failed to set the effective user id of

discovery to cicssm. seteuid return
code was %1.
Explanation:
Discovery cannot set its effective user id to cicssm.
System action:
None
User response:
Controller which, if started correctly using the cicssm
command, will have verified the environment.
Destination:
Exception caught during initialization.
Explanation:
The discovery program has caught an exception. The
exception description follows this message.
BHG2518
BHG2520
cicssm user id is not defined in the

environment.
Explanation:
Discovery has been started with an invalid environment
and cannot set its effective user id to be user cicssm.
System action:
None
User response:
Destination:
BHG2521
DSOM termination complete.
Explanation:
The discovery program has successfully uninitialized
DSOM.
System action:
None
User response:
None
Destination:
BHG2600
Must have root authority to run this

program.
Explanation:
The health monitor program has been invoked by a user
other than root.
System action:
The program exits
User response:
command, will have the correct authority. Contact IBM
Service if unable to identify the problem
Destination:
BHG2601
Exception caught during program

initialization.
Explanation:
The health monitor program has caught an exception.
The exception description follows this message.
System action:
The program exits
User response:
Destination:
Chapter 2. BHG...
527
BHG2602 BHG2610
User response:
None
BHG2602
Destination:
Health monitor termination complete.
Explanation:
Information only
System action:
None
User response:
None
Destination:
BHG2604
Starting up new monitor for cics region

%1
Explanation:
Information only
System action:
None
User response:
None
BHG2608
Server %1 already has a running health

monitor.
Explanation:
An attempt has been made to start a health monitor for
a Resource Controller but a monitor is already running.
System action:
The program exits. The existing monitor continues.
User response:
None
Destination:
BHG2609
cicssm user id not defined in the

environment.
Destination:
Explanation:
The health monitor has been started with an invalid
environment and cannot set its effective user id to
cicssm.
BHG2605
System action:
None.
Terminating monitor for cics region %1
Explanation:
Information only
System action:
None
User response:
None
User response:
Destination:
Destination:
BHG2610
BHG2606
Explanation:
Information only
Explanation:
The health monitor cannot set its effective user id to
cicssm.
System action:
None
System action:
None.
User response:
None
User response:
Starting DSOM initialization.
Destination:
BHG2607
DSOM initialization complete.
Explanation:
Information only
System action:
None
528
Failed to set effective user id of health

monitor to cicssm. seteuid return code
%1.
Destination:
BHG3000 BHG3200
BHG3000
The selected system could not be

accessed pid=%1 WorkTagNumber=%2
CallType=%3 UserId=%4
Explanation:
A task has been routed to a system but that system was
not available.
System action:
Retry the task. If the retry limit is reached select another
system. If the reselection limit is reached use the default
system.
System action:
The bhgwterm session ceases running.
User response:
This may be caused by software error, cache corruption
or a problem with the cache, semaphore, sockets or
message or trace files. Restart the bhgwterm session. If
it fails again use the cicssm clean command and restart
the wcm. If there is still a problem save the message
and trace files and contact IBM service.
Destination:
/var/cicssm/log/wcl.*.msg
User response:
Occasional errors are a feature of networked systems. If
errors are frequent investigate the status of the failing
system. Remember that the problem could be security.
BHG3103
Destination:
Explanation:
The window in which the bhgwterm session was started
is too small for it to be able to operate.
BHG3100
System action:
Terminated after failing to find list of

applications.
Explanation:
There are no applications to display in the currently
active configuration.
System action:
User response:
Check that the current configuration does contain
applications. If it does then check that the wcm is
running correctly. If in doubt restart it.
Terminated because the screen was

too small to display the menu.
User response:
Make the window larger.
Destination:
BHG3104
Terminated because of an unknown

error.
Explanation:
An error occured during normal operation.
Destination:
System action:
BHG3101
User response:
Save the message and trace files and contact IBM
service.
Terminated because an exception was

received during normal operation
Explanation:
Destination:
System action:
BHG3200
User response:
message or trace files. Restart the bhgwterm session. If
Destination:
BHG3102
Terminated because a system to run

the requested application could not be
selected.
Explanation:
User response:
Check that the requested application is in the currently
active configuration. If it does then check that the wcm
is running correctly. If in doubt restart it.
Destination:
Terminated because an unknown

exception was received during normal
operation
Explanation:
Chapter 2. BHG...
529
BHG3201 BHG3604
BHG3201

Explanation:
System action:
The bhgwteld session ceases running.
User response:
message or trace files. Restart the bhgwteld session. If
System action:
All subsequent selections will be to the default system.
No response statistics will be gathered.
User response:
Restart the client program. If this does not clear the
problem restart the wcm.
Destination:
BHG3602
An unknown exception occured whilst

opening the cache
Explanation:
An error occured whilst opening the cache.
Destination:
System action:
No response statistics will be gathered
BHG3202
User response:
The wlm client was unable to determine the cause of
this error. Restart the client program. If this does not
clear the problem restart the wcm.

operation
Explanation:
System action:
The bhgwteld session ceases running.
User response:
message or trace files. Restart the bhgwteld session. If
Destination:
BHG3600
The client group name has been

defaulted to grp1
Explanation:
A default value for the environment variable
BHG_WCL_GROUP_NAME has been used because it
is not set in the client environment.
System action:
The client will assume it is in the client group grp1 for
all subsequent selections.
User response:
Check and correct the system and user .profile files.
Destination:
BHG3601
An exception occured whilst opening

the cache
Explanation:
An error occured whilst opening the cache.
530
Destination:
BHG3603
The plex name has been defaulted to

cpx1
Explanation:
BHG_WCL_*_CICSPLEX_NAME has been used
because it is not set in the client environment. *
represents the client group as defined by the
BHG_WCL_GROUP_NAME environment variable.
System action:
The client will assume it is in the cicsplex cpx1 for all
subsequent selections.
User response:
Destination:
BHG3604
The connection list has been defaulted

to all
Explanation:
BHG_WCL_*_CONNECTION_LIST has been used
because it is not set in the client environment. *
represents the client group as defined by the
BHG_WCL_GROUP_NAME environment variable.
System action:
The client will assume it has connections to all system
clones with a connection load of 0.25 for all subsequent
selections.
User response:
BHG3605 BHG3620
Destination:
BHG3605
The application name has been

defaulted to null
Explanation:
The environment variable BHG_WCL_APPLICATION is
not set in the client environment.
System action:
No response statistics will be gathered. However if the
invocation of cicsteld supplied an application normal
operation is still possible.
User response:
clear the problem restart the wcm.
Destination:
BHG3610
A cache inconsistency was detected

during shut down. The system clone
load could not be found
Explanation:
An error occured during shut down.
System action:
The client will complete its shutdown as best it can.
User response:
User response:
If this error occurs frequently restart the wcm.
Destination:
Destination:
BHG3606
BHG3611
Initialization completed ExitStyle=%1

UserId=%2 ProcessId=%3 InitOk=%4
Explanation:
This message gives information concerning the
parameters with which a wlm client has been invoked.
These may be useful for resolving problems.
System action:
Normal operation continues.
User response:
Use as required for resolving problems.
Destination:
BHG3608
An exception occured during start up
Explanation:
An error occured during start up.
System action:
An exception occured during shut

down
Explanation:
System action:
User response:
Destination:
BHG3612
An unknown exception occured during

shut down
Explanation:
System action:
User response:
User response:
Destination:
Destination:
BHG3620
BHG3609
Explanation:
An error occured during client start up.

start up
Explanation:
An error occured during start up.
System action:
No SELECTION has been made

because of an error during start up
System action:
User response:
Chapter 2. BHG...
531
BHG3621 BHG3627
Destination:
BHG3621

because the cics system %1 is not in
an active configuration FileName=%2
LineNumber=%3
Explanation:
The region of which the client is a part is not in the
System action:
BHG3624
Explanation:
An error occured whilst locating the resource.
System action:
The default system will be selected. No response
statistics will be gathered.
User response:
If this occurs frequently restart the wlm client affected.
Destination:
BHG3625
User response:
Put the cics system into the currently active
configuration.
Destination:
BHG3622

because the retry request was
unexpected

because an error occured whilst
locating the resource
A default SELECTION has been made

because the resource does not have
the dynamic flag set
WorkTagNumber=%1
ResourceType=%2
ResourceModelName=%3
SystemCloneName=%4
Explanation:
The resource (program) requested does not have the
dynamic flag set. Wlm was therefore unable to select a
system to run it and thus ran it on the default system.
Explanation:
An unexpected retry request was received.
System action:
System action:
The retry request is discarded.
User response:
None.
User response:
If this problem occurs frequently restart the client
program. If this does not clear the problem restart the
wcm.
Destination:
Destination:
BHG3623

because the retry and reselection
limits have been reached
Explanation:
The request has been retried on all systems known to
wlm supporting the requested resource without success.
Therefore as a last resort wlm ran the resource on the
default system.
System action:
User response:
Check the operation of the cics systems.
Destination:
BHG3627

because the resource is not in the
current configuration
WorkTagNumber=%1
ResourceType=%2
SystemCloneName=%4
Explanation:
The resource (transaction or program) requested is not
in the currently active configuration. Wlm was therefore
unable to select a system to run it and thus ran it on the
default system.
System action:
User response:
Check the validity of the resource (model) name given
in this message. If it is invalid check why requests for it
are being issued. If valid check why it is not in the
Destination:
532
BHG3628 BHG3634
BHG3628

because we could not communicate
with WAP/WCM WorkTagNumber=%1
ResourceType=%2
SystemCloneName=%4
Explanation:
There was a communication failure which could not be
recovered between the client and the wcm or (more
likely) between the wcm and the wap.
System action:
User response:
Check that the wap and wcm are running correctly. If in
doubt restart them.
Destination:
BHG3629

because an error occured whilst
locating the resource
Explanation:
An error occured whilst locating the resource.
System action:
User response:
If this error occurs frequently restart the client. If this
does not resolve the problem restart the wcm.
Destination:
BHG3632
Explanation:
This message gives information concerning a selection
made by wlm. There is one message each time a
different selection is made.
System action:
User response:
The user could use this message to determine and
optimise the operation of wlm or cics systems. If this
information is not required it can be disabled by
reducing trace level.
Destination:
BHG3633
User response:
If this occurs frequently restart the wlm client affected.
Destination:
BHG3630
A cache inconsistency was detected.

The connection load could not be
found
Explanation:
System action:
Operation will continue as best it can.
New SELECTION WorkTagNumber=%1

ResourceType=%2
SystemCloneName=%4
ConnectionName=%5
SELECTION WorkTagNumber=%1
ResourceType=%2
SystemCloneName=%4
ConnectionName=%5
Explanation:
This message gives information concerning a selection
made by wlm. There is one message per selection.
System action:
User response:
User response:
Destination:
Destination:
BHG3634
BHG3631
A cache inconsistency was detected.

The system clone load could not be
found
Explanation:
System action:

because no systems were healthy and
connected WorkTagNumber=%1
ResourceType=%2
SystemCloneName=%4
Explanation:
The resource (transaction or program) requested is not
configured on any healthy, connected systems in the
Chapter 2. BHG...
533
BHG3635 BHG3643
currently active configuration. Wlm was therefore unable
to select a system to run it and thus ran it on the default
system.
System action:
User response:
in this message. Check that it is configured on at least
one system model which has at least one system clone
whose cics system is operational.
Destination:
BHG3635

because an exception occured whilst
making the selection FileName=%1
LineNumber=%2
Explanation:
An error occured whilst making a selection.
System action:
User response:
does not resolve the problem restart the wcm. If
problems persist use the cicssm clean command and
then restart. If there is still a problem save the message
Destination:
BHG3636

because an unknown exception
occured whilst making the selection
FileName=%1 LineNumber=%2
Explanation:
An error occured whilst making a selection.
System action:
User response:
resolve the problem restart the wcm. If problems persist
use the cicssm clean command and then restart. If
there is still a problem save the message and trace files
and contact IBM service.
Destination:
BHG3640
No statistics have been gathered

Explanation:
An error occured during client start up.
System action:
User response:
Destination:
BHG3641
No statistics have been gathered

because the response was unexpected
Explanation:
An unexpected response was received.
System action:
The response is discarded.
User response:
wcm.
Destination:
BHG3642
An exception occured whilst handling

a response FileName=%1
LineNumber=%2
Explanation:
An error occured whilst handling a response.
System action:
User response:
Destination:
BHG3643

handling a response FileName=%1
LineNumber=%2
Explanation:
An error occured whilst handling a response.
System action:
User response:
534
BHG3660 BHG3667
this error. If this error occurs frequently restart the client.
If this does not resolve the problem restart the wcm. If
Destination:
BHG3660
No response time has been recorded

because the start timestamp was
unexpected
Explanation:
An unexpected response time measurement event was
received.
System action:
User response:
wcm.
Destination:
BHG3661

a start timestamp FileName=%1
LineNumber=%2
Explanation:
An error occured whilst handling a start timestamp.
System action:
No response timings will be gathered.
User response:
Destination:
BHG3662

handling a start timestamp
Explanation:
An error occured whilst handling a start timestamp.
System action:
User response:

Destination:
BHG3665

because the end timestamp was
unexpected
Explanation:
received.
System action:
User response:
wcm.
Destination:
BHG3666

an end timestamp FileName=%1
LineNumber=%2
Explanation:
An error occured whilst handling an end timestamp.
System action:
User response:
Destination:
BHG3667

handling an end timestamp
Explanation:
An error occured whilst handling an end timestamp.
System action:
User response:
Destination:
Chapter 2. BHG...
535
BHG3670 BHG3685
BHG3670

because the change timestamp was
unexpected
BHG3680
%d %t %iE No application list has been

provided because WAP/WCM could not
supply it
Explanation:
received.
Explanation:
The client group of which the client is a part is not in the
System action:
System action:
No application list for user selection will be provided.
User response:
wcm.
User response:
Check the BHG_WCL_GROUP_NAME and
BHG_WCL_*_CICSPLEX_NAME environment variables
against currently active configuration.
Destination:
Destination:
BHG3671
BHG3683

a change timestamp FileName=%1
LineNumber=%2
No application list has been provided

because of a serious error whilst
searching the cache
Explanation:
An error occured whilst handling a change timestamp.
Explanation:
System action:
System action:
The cicslterm client will terminate.
User response:
User response:
Destination:
BHG3672

handling a change timestamp
Explanation:
An error occured whilst handling a change timestamp.
System action:
User response:
Destination:
Destination:
BHG3684
An exception occured whilst providing

an application list FileName=%1
LineNumber=%2
Explanation:
An error occured whilst providing an application list.
System action:
No application list will be available.
User response:
Destination:
BHG3685

providing an application list
Explanation:
An error occured whilst providing an application list.
System action:
No application list will be available.
User response:
536
BHG3688 BHG3695
Destination:
BHG3688
No first transaction has been provided

searching the cache
Explanation:
An error occured whilst locating the first transaction of
an application.
System action:
The session will be started without the first transaction
being invoked.
User response:
Destination:
BHG3689
No first transaction has been provided

because WAP/WCM could not supply
data on application %1
Explanation:
The resource (application) requested is not in the
currently active configuration. Wlm was therefore unable
to determine the first transaction.
System action:
being invoked.
User response:
in this message. If it is invalid check why requests for it
are being issued. If valid check why it is not in the
Destination:
BHG3692
No has first transaction been provided

searching the cache
Explanation:
An error occured whilst locating the first transaction of
an application.
System action:
being invoked.
User response:

Destination:
BHG3693
No has first transaction been provided

because application %1 does not have
one in the database
Explanation:
The resource (application) requested is available in the
currently active configuration but does not have a first
transaction specified. Wlm was therefore unable to
determine the first transaction.
System action:
being invoked.
User response:
Check the data base and supply a first transaction if
one is required.
Destination:
BHG3694
An exception occured whilst providing

a first transaction FileName=%1
LineNumber=%2
Explanation:
An error occured whilst providing a first transaction.
System action:
No first transaction will be available.
User response:
Destination:
BHG3695

providing a first transaction
Explanation:
An error occured whilst providing a first transaction.
System action:
No first transaction will be available.
User response:
Chapter 2. BHG...
537
BHG3700 BHG3722
Destination:
BHG3700
The region name has not been set

Explanation:
An error occured during initialization.
System action:
User response:
Destination:
BHG3701
An exception occured during

initialization FileName=%1
LineNumber=%2
Explanation:
System action:
User response:
If this error occurs restart the client. If this does not
BHG3720
Could not locate resource because an

internal program error occured (%1)
Explanation:
An internal program error occured whilst attempting to
locate a resource.
System action:
User response:
service.
Destination:
BHG3721
An exception occured whilst

communicating with the WCM
Explanation:
An error occured whilst communicating with the WCM.
System action:
User response:
If this error occurs frequently restart the client program.
Destination:
Destination:
BHG3722
BHG3702
Explanation:
An error occured whilst communicating with the WCM.

initialization FileName=%1
LineNumber=%2
Explanation:
System action:
User response:
this error. If this error occurs restart the client. If this
Destination:
538

communicating with the WCM
System action:
User response:
this error. If this error occurs frequently restart the client
program. If this does not resolve the problem restart the
wcm. If problems persist use the cicssm clean
command and then restart. If there is still a problem
save the message and trace files and contact IBM
service.
Destination:
BHG3723 BHG3733
BHG3723
Did not obtain data from WAP/WCM

because of its recent failure history
BHG3730
Could not select a partition because of

a cache inconsistency
Explanation:
A communication error occured during normal operation.
Explanation:
System action:
A default selection is made.
System action:
User response:
does not resolve the problem restart the wcm and finally
as a last resort restart the wap.
User response:
Destination:
Destination:
BHG3731
BHG3723
Did not obtain data from WAP/WCM

because of its recent failure history
Explanation:
System action:
User response:
Destination:
Explanation:
The module bhgwlmexit could not be loaded.
System action:
User response:
Check that the module bhgwlmexit is present in the
/usr/lpp/cicssm/bin directory, gives read access to the
user in question and that any libraries that it requires
are also present in the appropriate directory.
Destination:
BHG3732
BHG3724
Could not obtain data from WAP/WCM

because message retry was exhausted
Explanation:
System action:
User response:
Destination:
BHG3725
Region %1 has been located in

cicsplex %2
Could not load WLM user_exit module.
CONSIDERING partition
PartitionNumber=%1
SeparationName=%3
PartitionName=%4
PartitionUserData=%5
Explanation:
This message gives information concerning a partition
about to be considered by the users wlm exit. There is
one message per partition considered.
System action:
User response:
Explanation:
This message gives information concerning a region.
Destination:
System action:
BHG3733
User response:
None.
Destination:
Partition CONSIDERED
ReturnCode=%1 ChoicePriority=%2
Explanation:
This message gives information concerning a partition
considered by the users wlm exit. There is one
message per partition considered.
Chapter 2. BHG...
539
BHG3741 BHG3746
System action:

User response:
Destination:
Destination:
BHG3741
System %1 REJECTED because

resource %2 is currently locked out as
a result of previous errors
Explanation:
This message gives information concerning a system
considered for selection by wlm. There is one message
per system considered.
System action:
User response:
Destination:
BHG3742
Could not update the cache during

system selection
Explanation:
An error occurred during system selection.
System action:
The client will select a system as best it can.
User response:
Destination:
BHG3743

system selection
BHG3744
System %1 REJECTED because it is

not in the partition %2
Explanation:
System action:
User response:
Destination:
BHG3745
System %1 REJECTED because it does

not have a connection to this system
Explanation:
System action:
User response:
Destination:
var/cicssm/log/wcl.*.msg
BHG3746
System %1 REJECTED because its

connection to this system is out of
service
Explanation:
Explanation:
System action:
System action:
User response:
User response:
540
Destination:
BHG3747 BHG3753
BHG3747
System %1 REJECTED because it is

locked out as a result of previous
errors
Explanation:
System action:
User response:
Destination:
BHG3748
System %1 REJECTED because its

performance is too poor for it to be
usable
Explanation:
System action:
User response:
Destination:
BHG3749
System %1 CONSIDERED Load=%2

ConnectionLoad=%3 Health=%4
Same/Known=%5
Explanation:
System action:
User response:
Destination:
BHG3750
Could not find a connection because

of a cache inconsistency
Explanation:
An error occurred whilst selecting a system.
System action:
User response:
Destination:
BHG3751

of a cache inconsistency
Explanation:
System action:
User response:
Destination:
BHG3752
Could not find a connection because a

name (in the connection list) is too
long
Explanation:
System action:
User response:
Correct the value of the appropriate
BHG_WCL_*_CONNECTION_LIST environment
variable.
Destination:
BHG3753
Could not find a connection because a

value (in the connection list)is too long
Explanation:
System action:
User response:
Correct the value of the appropriate
BHG_WCL_*_CONNECTION_LIST environment
variable.
Destination:
Chapter 2. BHG...
541
BHG3754 BHG3764
BHG3754

of an internal program error
Explanation:
An internal program error occurred whilst selecting a
system.
System action:
User response:
service.
Destination:

response of a cics system selected by wlm. There is
one message per response.
System action:
User response:
Destination:
BHG3763
BHG3760
Could not update the statistics

because of an inconsistency while
handling a response
Explanation:
A system clone which was present in the cache at
selection time was not present when the response
occurred.
System action:
User response:
This error may occur when changing configurations. If
this error occurs frequently restart the client. If this does
not resolve the problem restart the wcm.
Destination:
BHG3761
Could not update the statistics

because of an inconistency whilst
handling a response
Explanation:
A system clone which was chosen at selection time no
longer has its attached data in the cache.
System action:
User response:
This error may occur when restarting the wcm. If this
error occurs frequently restart the client. If this does not
resolve the problem restart the wcm.
Destination:
BHG3762
Normal RESPONSE to session or

defaulted selection
WorkTagNumber=%1
SystemCloneName=%2
ResponseTime=%3
Explanation:
542
Normal RESPONSE
WorkTagNumber=%1
SystemCloneName=%2
ResponseTime=%3
PerformanceIndex=%4
Explanation:
System action:
User response:
Destination:
Any wlm client.
Destination:
BHG3764
Unreasonably fast or slow RESPONSE

WorkTagNumber=%1
SystemCloneName=%2
ResponseTime=%3 TargetTime=%4
Explanation:
A response occurred in an unreasonably short or long
time after the selection.
System action:
User response:
Occasional errors are a feature of networked systems. It
may also occur in some error situations. If this error
occurs frequently restart the client. If this does not
Destination:
BHG3765 BHG3770
BHG3765
Could not update the cache because of

an inconistency whilst handling a
response
Explanation:
A resource which was present in the cache at selection
time was not present when the response occurred.
System action:
system. If it is not restart the client. If this does not

Destination:
BHG3768
User response:
This error may occur when changing configurations. If
this error occurs frequently restart the client. If this does
not resolve the problem restart the wcm.
Destination:
BHG3766
Resource failed RESPONSE

WorkTagNumber=%1
SystemCloneName=%2
ResourceType=%3
ResourceLocation=%4
Explanation:
A response was received indicating that the resource is
not available on the selected system.
System action:
The system involved will not be selected again for the
the requested resource until a timeout has expired. No
response statistics will be gathered.
User response:
Determine whether the selected system is supposed to
support the requested resource. If it is investigate the
state of the cics system. If it is not restart the client. If
this does not resolve the problem restart the wcm. If
Destination:
BHG3767
System failed RESPONSE

WorkTagNumber=%1
SystemCloneName=%2
ResourceType=%3
ResourceLocation=%4
Explanation:
The selected system was found to be inoperable.
System action:
The system involved will not be selected again until a
timeout has expired. No response statistics will be
gathered.
User response:
be operational. If it is investigate the state of the cics
Abend RESPONSE
WorkTagNumber=%1
SystemCloneName=%2
ResourceType=%3
ResourceLocation=%4
Explanation:
System action:
User response:
Investigate the state of the cics system.
Destination:
BHG3769
RETRYING a previous selection

WorkTagNumber=%1
SystemCloneName=%2
ResourceType=%3
ResourceLocation=%4
Explanation:
A system which had previously been selected was
found to be inoperable and another is being selected.
System action:
Retry the previously selected system or select a
different one. No response statistics will be gathered.
User response:
Occasional errors are a feature of networked systems.
be operational. If it is investigate the state of the cics
system. If it is not restart the client. If this does not
Destination:
BHG3770
Invalid status RESPONSE

WorkTagNumber=%1
SystemCloneName=%2
ResourceType=%3
ResourceLocation=%4
Chapter 2. BHG...
543
BHG3771 BHG4201
Explanation:
A response which failed basic validity checks was
received.
System action:
User response:
User response:
It may be advisable to restart the wap or wcm involved.
Destination:
/var/cicssm/log/wap.*.msg
BHG4012
Destination:
BHG3771

system selection
Explanation:
System action:
User response:
Destination:
BHG4001
A cache manager has been given no

system images because none are
configured on node %1 FileName=%2
LineNumber=%3
Explanation:
A cache manager has been given no system images
because there are no cics system configured on its
node.
System action:
None.
A cache manager has been given

incomplete information because of a
cache inconsistency Parameter1=%1
Parameter2=%2 FileName=%3
LineNumber=%4
Explanation:
A wcm has been given incomplete information because
of a cache inconsistency.
System action:
As much data as possible is sent to the wcm.
User response:
Destination:
BHG4200
An invalid data request message was

received from cache manager %1
Explanation:
A message which did not pass validity checks was
received.
System action:
The message is discarded.
User response:
Check that the system name and port number allocated
to the wap is not being used by another service or
program.
Destination:
User response:
This is a normal situation. However a possible error is
for the node name in the smappl data base for a node
which is intended to have cics systems to be different
from the name actually given to the node.
BHG4201
Destination:
Explanation:
A message was received from a cache manager
requesting information that is not present in the smappl
data base.
BHG4011
A cache manager has been given

incomplete information because of a
cache inconsistency Parameter1=%1
Explanation:
A wcm has been given incomplete information because
of a cache inconsistency.
System action:
As much data as possible is sent to the wcm.
544
A request for an application list was

received from cache manager %1 but
no applications exist in the current
configuration FileName=%2
LineNumber=%3
System action:
The wap informs the wcm and wlm client that the data
is not available. Typical behaviour of a client in this
circumstance is to select the default system.
User response:
Check that the smappl data base matches the
resources that the cics applications use.
Destination:
BHG4202 BHG4300

BHG4202
Destination:
A request for data was received from

cache manager %1 but could not be
answered because the resource does
not exist in the current configuration
Explanation:
data base.
System action:
User response:
BHG4220

cache manager %1 may be incomplete
because the separation %1 has no
partitions in the current configuration
Explanation:
data base.
System action:
Destination:
User response:
BHG4210
Destination:

answered because the resource is not
configured on any system models in
the current configuration
Explanation:
data base.
System action:
User response:
BHG4221

cache manager %1 may be incomplete
because the partition %1 %2 does not
separate any system clones in the
current configuration
Explanation:
data base.
System action:
Destination:
User response:
BHG4211
Destination:

answered because the system models
have no system clones in the current
configuration
Explanation:
data base.
System action:
User response:
BHG4300
An internal program error occurred

whilst processing a data update
message FileName=%1
LineNumber=%2
Explanation:
An internal program error occurred.
System action:
User response:
Chapter 2. BHG...
545
BHG4301 BHG4311
Destination:
/var/cicssm/log/wap.*.msg or /var/cicssm/log/wcm.*.msg
System action:
BHG4301
User response:

message FileName=%2
LineNumber=%3 Parameter1=%1
Explanation:
Destination:
BHG4305
System action:
User response:
Destination:
BHG4302

message FileName=%3
Parameter2=%2
Explanation:
Explanation:
System action:
User response:
Destination:
BHG4310
System action:
User response:
Destination:
BHG4303

message FileName=%4
Parameter2=%2 Parameter3=%3
Explanation:
System action:
User response:
Destination:
BHG4304

message FileName=%5
Parameter4=%4
Explanation:
546

message FileName=%6
An invalid data update message was

received FileName=%1
LineNumber=%2
Explanation:
received.
System action:
User response:
to the wap or wcm is not being used by another service
or program.
Destination:
BHG4311

Explanation:
received.
System action:
User response:
or program.
Destination:
BHG4312 BHG4322
BHG4312

Parameter2=%2
Explanation:
received.
System action:
User response:
or program.
Destination:
BHG4313

BHG4315

Explanation:
received.
System action:
User response:
or program.
Destination:
BHG4320
A data update message is not

consistent with the state of the cache
Explanation:
received.
Explanation:
The data update message is not consistent with the
state of the cache.
System action:
System action:
The inconsistent data will be ignored and operation will
continue.
User response:
or program.
Destination:
User response:
Destination:
BHG4321
BHG314

Parameter4=%4
Explanation:
received.
System action:
User response:
or program.
Destination:

Parameter1=%1
Explanation:
state of the cache.
System action:
continue.
User response:
Destination:
BHG4322

Explanation:
Chapter 2. BHG...
547
BHG4323 BHG4602
state of the cache.

continue.
System action:
continue.
User response:
User response:
Destination:
Destination:
BHG4600
BHG4323
Explanation:
A mandatory environment variable describing the wap
system name & port number is not set.

Parameter3=%3
Explanation:
state of the cache.
System action:
continue.
User response:
Destination:
System action:
The wcm ceases running.
User response:
This may be caused by an error in configuring the wcm.
Review the configuration and then use the cicssm start
command to restart the wcm. If the wcm fails again use
the cicssm clean command and then restart. If there is
still a problem save the message and trace files and
Destination:
/var/cicssm/log/wcm.*.msg
BHG4601
BHG4324

Explanation:
state of the cache.
Terminated because WAP system name

& port number not set. Environment
variable %1 not set
Initialization started ID=%1 PID=%2

VarDirBase=%3 HostName=%4
WAPName=%5
Explanation:
An informational comfort message.
System action:
The wcm is starting its initialization.
User response:
None.
System action:
continue.
Destination:
User response:
BHG4602
Destination:
BHG4325

Parameter5=%5
Explanation:
state of the cache.
System action:
548
Initial connection to WAP failed

ReturnCode=%1
Explanation:
The initial attempt to connect to the wap failed.
System action:
Reconnection will be attempted when communication is
next required.
User response:
Check that the wap is running and that the wcm has
been configured with the correct system name and port
number.
Destination:
BHG4603 BHG4609
BHG4603

received whilst opening the cache
BHG4606
Initialization completed successfully,

awaiting messages
Explanation:
An error occurred whilst opening the cache.
Explanation:
System action:
System action:
The wcm has completed its initialization.
User response:
or a user permissions problem on the cache,
semaphore, sockets or message or trace files. Use the
cicssm start command to restart the wcm. If the wcm
fails again use the cicssm clean command and then
restart. If there is still a problem save the message and
trace files and contact IBM service.
User response:
None.
Destination:
BHG4604

exception was received whilst opening
the cache
Explanation:
System action:
User response:
The wcm was unable to determine the cause of this
error. Use the cicssm start command to restart the wcm.
If the wcm fails again use the cicssm clean command
and then restart. If there is still a problem save the
message and trace files and contact IBM service.
Destination:
BHG4605
A communication error occurred whilst

sending a new cache manager
message to the WAP ReturnCode=%1
Explanation:
An error occurred whilst sending a message to the wap.
System action:
Communication will be retried when communication is
next required.
User response:
Occasional errors are a feature of communications. If
these messages occur frequently check that the wap is
running and that the wcm has been configured with the
correct system name and port number.
Destination:
Destination:
BHG4607

whilst receiving a message
ReturnCode=%1
Explanation:
An error occurred whilst receiving a message from the
wap or from a wlm client.
System action:
next required.
User response:
Occasional errors are a feature of communications.
Destination:
BHG4608
Re-connection to WAP failed

ReturnCode=%1
Explanation:
An attempt to connect to the wap failed.
System action:
next required.
User response:
number.
Destination:
BHG4609

re-sending a new cache manager
message to the WAP ReturnCode=%1
Explanation:
System action:
next required.
User response:
Chapter 2. BHG...
549
BHG4610 BHG4615
Destination:
BHG4610

sending a cache not updated message
to a client ReturnCode=%1
Explanation:
An error occurred whilst sending a message to a wlm
client.
System action:
next required.
User response:
BHG4613

sending a data request message to the
WAP ReturnCode=%1
Explanation:
System action:
next required.
User response:
Destination:
Destination:
BHG- 4614
BHG4611
Explanation:
An error occurred during normal operation.

ReturnCode=%1
An exception was received whilst

updating the cache FileName=%1
LineNumber=%2
Explanation:
System action:
The wcm logs the error and continues running.
System action:
next required.
User response:
number.
User response:
message or trace files. If the problem occurs frequently
use the cicssm start command to restart the wcm. If the
wcm fails again use the cicssm clean command and
Destination:
Destination:
BHG4612
BHG4615

Explanation:
client.
System action:
next required.
User response:
Destination:
An unknown exception was received

whilst updating the cache
Explanation:
System action:
The wcm logs the error and continues running.
User response:
use the cicssm start command to restart the wcm. If the
wcm fails again use the cicssm clean command and
Destination:
550
BHG4616 BHG4632
BHG4616

sending a cache updated message to a
client ReturnCode=%1
Explanation:
client.
System action:
next required.
User response:
Destination:
BHG4619

Explanation:
client.
message or trace files. Use the cicssm start command

to restart the wcm. If the wcm fails again use the cicssm
clean command and then restart. If there is still a
problem save the message and trace files and contact
IBM service.
Destination:
BHG4622

operation
Explanation:
System action:
User response:
The wcm was unable to determine the cause of this
error. Use the cicssm start command to restart the wcm.
If the wcm fails again use the cicssm clean command
System action:
next required.
Destination:
User response:
BHG4630
Destination:
Explanation:
AIX has sent the SIGHUP signal to a wcm.
BHG4620
System action:
An invalid message was received

MessageType=%1
Explanation:
received.
System action:
User response:
program.
Destination:
BHG4621

Explanation:
System action:
User response:
Terminated because a SIGHUP signal

was received
User response:
Use the cicssm start command to restart the wcm.
Destination:
BHG4631
Terminated because a SIGINT signal

was received
Explanation:
AIX has sent the SIGINT signal to a wcm.
System action:
User response:
Destination:
BHG4632
Terminated because a SIGQUIT signal

was received
Explanation:
AIX has sent the SIGQUIT signal to a wcm.
System action:
Chapter 2. BHG...
551
BHG4633 BHG4703
User response:
Destination:
BHG4633
Terminated because a SIGSEGV signal

was received
System action:
The wap ceases running.
User response:
This may be caused by an error in configuring the wap.
command to restart the wap. If the wap fails again use
Explanation:
AIX has sent the SIGSEGV signal to a wcm.
Destination:
System action:
BHG4701
User response:
This may be caused by software error or by cache
corruption. Use the cicssm start command to restart the
wcm. If the wcm fails again use the cicssm clean
command and then restart.
Destination:
BHG4634
Terminated because a SIGTERM signal

was received
Explanation:
AIX has sent the SIGTERM signal to a wcm.
System action:
User response:
This will occur whenever the user requests that a wcm
be stopped by the cicssm command.
Destination:
BHG4635
Terminated because a SIGDANGER

signal was received
Explanation:
AIX has sent the SIGDANGER signal to a wcm.
System action:
User response:
This could be caused if the system is heavily
overloaded. Determine and clear the cause of overload
and then restart the wcm.
Destination:
BHG4700

variable %1 not set
Explanation:
552

VarDirBase=%3 WAPName=%4
Explanation:
System action:
The wap is starting its initialization.
User response:
None.
Destination:
BHG4702

Explanation:
System action:
User response:
cicssm start command to restart the wap. If the wap
fails again use the cicssm clean command and then
Destination:
BHG4703

the cache
Explanation:
System action:
User response:
The wap was unable to determine the cause of this
error. Use the cicssm start command to restart the wap.
If the wap fails again use the cicssm clean command
BHG4704 BHG4710
Destination:
BHG4704
Initialization completed successfully,

awaiting messages
User response:
use the cicssm start command to restart the wap. If the
wap fails again use the cicssm clean command and
Explanation:
Destination:
System action:
The wap is has completed its initialization.
BHG4708
User response:
None.
Destination:
BHG4705

whilst receiving a message
ReturnCode=%1
Explanation:
An error occurred whilst receiving a message from the
wsi or from a wcm.
System action:
next required.
User response:
Destination:
BHG4706
An invalid message was received

MessageType=%1
Explanation:
received.
System action:
User response:
program.
Destination:
BHG4707
An exception was received whilst

updating the cache FileName=%1
LineNumber=%2
Explanation:
System action:
The wap logs the error and continues running.

whilst updating the cache
Explanation:
System action:
The wap logs the error and continues running.
User response:
use the cicssm start command to restart the wap. If the
wap fails again use the cicssm clean command and
Destination:
BHG4709

Explanation:
n error occurred during normal operation.
System action:
User response:
to restart the wap. If the wap fails again use the cicssm
IBM service.
Destination:
BHG4710

operation
Explanation:
System action:
Chapter 2. BHG...
553
BHG4720 BHG4800
User response:
The wap was unable to determine the cause of this
error. Use the cicssm start command to restart the wap.
If the wap fails again use the cicssm clean command
Destination:
BHG4720

was received
Explanation:
AIX has sent the SIGHUP signal to a wap.
System action:
User response:
Use the cicssm start command to restart the wap.
Destination:

wap. If the wap fails again use the cicssm clean
Destination:
BHG4724
Explanation:
AIX has sent the SIGTERM signal to a wap.
System action:
User response:
This will occur whenever the user requests that a wap
be stopped by the cicssm command.
Destination:
BHG4725
BHG4721

was received
Explanation:
AIX has sent the SIGINT signal to a wap.
System action:
User response:
Destination:
BHG4722

was received
Explanation:
AIX has sent the SIGQUIT signal to a wap.
System action:
User response:
Destination:
BHG4723

was received
Explanation:
IX has sent the SIGSEGV signal to a wap.
System action:
User response:
554

was received

signal was received
Explanation:
AIX has sent the SIGDANGER signal to a wap.
System action:
User response:
and then restart the wap.
Destination:
BHG4800

variable %1 not set
Explanation:
System action:
The wsi ceases running.
User response:
This may be caused by an error in configuring the wap.
command to restart the wsi. If the wsi fails again use
Destination:
/var/cicssm/log/wsi.*.msg
BHG4801 BHG4808
BHG4801
Terminated because SMAPPL alias not

set. Environment variable %1 not set
Explanation:
A mandatory environment variable describing the
smappl alias is not set.
System action:
User response:
This may be caused by an error in configuring the wsi.
command to restart the wsi. If the wsi fails again use
Destination:
BHG4802

VarDirBase=%3 WAPName=%4
SMApplAlias=%5
Explanation:
System action:
The wsi is starting its initialization.
User response:
None.
Check that the installation procedure has been carried

out correctly and then restart the wsi.
Destination:
BHG4805
Terminated because the DSOM object

adaptor could not be created
Explanation:
The DSOM object adaptor could not be created
System action:
User response:
Destination:
BHG4806
Terminated because the DSOM

implementation repository could not be
accessed Major=%1
Explanation:
The DSOM implementation repository could not be
accessed
System action:
Destination:
User response:
BHG4803
Destination:
Terminated because the connection to

SMAPPL failed Major=%1
ReturnCode=%2
Explanation:
he wsi could not connect to the smappl.
System action:
User response:
Check that the smappl which the wsi is configured to
connect to is running.
Destination:
BHG4804
Terminated because the DSOM

implementation repository could not be
found Major=%1
Explanation:
The DSOM Implementation repository could not be
found
BHG4807
The initial attempt to connect to WAP

failed ReturnCode=%1
Explanation:
The initial attempt to connect to the wap failed.
System action:
next required.
User response:
Check that the wap is running.
Destination:
BHG4808
Initialization completed successfully.
Explanation:
System action:
System action:
The wsi is has completed its initialization and will now
proceed to load the active configuration of each plex.
User response:
User response:
Chapter 2. BHG...
555
BHG4809 BHG4820
None.
Destination:
BHG4809
Initial configurations loaded, awaiting

events.
Explanation:
System action:
The wsi is has completed the loading of the active
configuration of each plex.
User response:
None.
Destination:
BHG4810
A DSOM socket busy condition

occurred
Explanation:
A DSOM socket busy condition occurred.
System action:
The logs the error and continues running.
User response:
these messages occur frequently check that system is
not overloaded.
System action:
User response:
The wsi was unable to determine the cause of this error.
Use the cicssm start command to restart the wsi. If the
wsi fails again use the cicssm clean command and then
Destination:
BHG4813

Explanation:
System action:
User response:
cicssm start command to restart the wsi. If the wsi fails
again use the cicssm clean command and then restart.
If there is still a problem save the message and trace
files and contact IBM service.
Destination:
Destination:
BHG4814
BHG4811
Explanation:


the cache
Explanation:
System action:
System action:
User response:
The wsi was unable to determine the cause of this error.
Use the cicssm start command to restart the wsi. If the
User response:
to restart the wsi. If the wsi fails again use the cicssm
IBM service.
Destination:
BHG4812

operation
Explanation:
556
Destination:
BHG4820

was received
Explanation:
AIX has sent the SIGHUP signal to a wsi.
System action:
User response:
Use the cicssm start command to restart the wsi.
BHG4821 BHG4840
Destination:
BHG4825
BHG4821
Explanation:
AIX has sent the SIGDANGER signal to a wsi.

was received
Explanation:
AIX has sent the SIGINT signal to a wsi.
System action:
User response:
Destination:
System action:
User response:
and then restart the wsi.
Destination:
BHG4826
BHG4822

was received
Explanation:
AIX has sent the SIGQUIT signal to a wsi.
System action:
User response:
Destination:
BHG4823

was received
Explanation:
AIX has sent the SIGSEGV signal to a wsi.

signal was received
An exception was received

Explanation:
n error occurred during normal operation.
System action:
The wsi logs the error and continues running.
User response:
use the cicssm start command to restart the wsi. If the
Destination:
System action:
BHG4827
User response:
wsi. If the wsi fails again use the cicssm clean
Explanation:
Destination:
BHG4824

was received
Explanation:
AIX has sent the SIGTERM signal to a wsi.
System action:
User response:
This will occur whenever the user requests that a wsi be
stopped by the cicssm command.
Destination:

System action:
User response:
Destination:
BHG4840
An error occurred whilst accessing the

SMAPPL FileName=%4
LineNumber=%5 Major=%1
ExceptionName=%2 ReturnCode=%3
Explanation:
Chapter 2. BHG...
557
BHG4841 BHG4880
System action:
Destination:
User response:
This may be caused by smappl failure or DSOM
communication failure. If the problem occurs frequently
Destination:
BHG4841
An error occurred whilst accessing the

SMAPPL FileName=%2
LineNumber=%3 ReturnCode=%1
Explanation:
System action:
User response:
This may be caused by smappl failure or DSOM
communication failure. If the problem occurs frequently
BHG4862
An error occurred whilst sending the

WAP a flush message
Explanation:
System action:
next required.
User response:
running.
Destination:
BHG4863
An error occurred whilst

communicating with the WAP and
could not be recovered
Explanation:
An error occurred whilst communicating with the wap
and could not be recovered.
System action:
The wsi logs the error and retries the communication.
Destination:
User response:
BHG4860
Destination:
An error occurred whilst

communicating with the WAP, retrying
RetryCount=%1
Explanation:
An error occurred whilst communicating with the wap.
System action:
The wsi logs the error and retries the communication.
User response:
running.
BHG4864
An error occurred whilst sending the

WAP a data update message
Explanation:
System action:
next required.
Destination:
User response:
running.
BHG4861
Destination:

ReturnCode=%1
Explanation:
System action:
next required.
User response:
558
BHG4880
An error occurred because the

SMAPPL data base is in an
inconsistent state FileName=%1
LineNumber=%2
Explanation:
he SMAPPL data base is in an inconsistent state.
BHG4881 BHG4922
System action:
continue.
User response:
None.
Destination:
BHG4881

LineNumber=%3 Parameter=%1
BHG4901
Activation completed
Explanation:
System action:
The wsi has completed the activation of a new
configuration.
User response:
None.
Destination:
Explanation:
The SMAPPL data base is in an inconsistent state.
BHG4920
System action:
continue.
Explanation:
An event which did not pass validity checks was
received.
User response:
Examine the data base at the locations suggested by
the parameters.
System action:
The event is discarded.
Destination:
BHG4882

Parameter2=%2
An unexpected event was received

User response:
None.
Destination:
BHG4921

Parameter=%1
Explanation:
The SMAPPL data base is in an inconsistent state.
Explanation:
received.
System action:
continue.
System action:
User response:
Examine the data base at the locations suggested by
the parameters.
Destination:
User response:
None.
Destination:
BHG4922
BHG4900
Activating Plex %1 Configuration %2
Explanation:
System action:
The wsi is starting the activation of a new configuration.
User response:
None.
Destination:

Explanation:
received.
System action:
User response:
None.
Destination:
Chapter 2. BHG...
559
BHG923 BHG5004
BHG923

Parameter3=%3
Explanation:
received.
System action:
User response:
None.
Re-issue the command with the correct parameters

Destination:
stdout
BHG5001
Fixed root path %1 does not exist
Explanation:
The path specified for the installed CICSSM does not
exist.
System action:
The program exits
Destination:
User response:
Check that the path specified is correct and that the
product has been installed correctly
BHG4924
Destination:
stdout

BHG5002
Variable root path %1 does not exist
Explanation:
received.
Explanation:
The path specified for the /var structure for CICSSM
does not exist.
System action:
System action:
The program exits
User response:
None.
User response:
Destination:
BHG4925

Parameter5=%5
Explanation:
received.
Destination:
stdout
BHG5003
Required directory %1 does not exist
Explanation:
A directory in the /var structure for CICSSM does not
exist
System action:
The program exits
System action:
User response:
User response:
None.
Destination:
stdout
Destination:
BHG5004
BHG5000
Invalid invocation. Syntax: \n\n \ \t

bhg_configure.sh [config_file] \n\n \ \t\t
config_file default: var_root/bhg.config
Explanation:
Configuration file %1 not found
Explanation:
The specified configuration file for CICSSM can not be
found
System action:
The program exits
System action:
The program exits
User response:
Make sure a valid configuration file exists and re-issue
the command
User response:
Destination:
560
BHG5005 BHG5013
stdout
BHG5005
User response:
none
Using configuration file %1
Explanation:
The specified configuration file will be used
System action:
none
User response:
none
Destination:
stdout
BHG5006
BHG5010
Defining CICS resource controllers to

smappl %1
Explanation:
The defined CICS resource controllers are being
defined to the specified smappl
System action:
none
DSOM port number set to %1
Explanation:
The specified port number will be used by DSOM
System action:
none
User response:
none
Destination:
stdout
BHG5007
Destination:
stdout
User response:
none
Destination:
stdout
BHG5011
Defining %1 %2 to %3
Explanation:
The specified alias is being defined to the managers
System action:
none
Adding %1 alias %2 on node %3 to

Explanation:
The specified alias is added to the DSOM
System action:
none
User response:
none
Destination:
stdout
User response:
none
Destination:
stdout
BHG5012
Unable to define %1 %2 to %3. Return

code %4.
Explanation:
The CICS Resource Controller, %2, could not be
defined to the smappl, %3.
System action:
continues
Explanation:
The specified alias is being configured on the node
User response:
This could be caused if the resource controller is
already defined to the smappl. This can occur when
re-running the configuration process.
System action:
none
Destination:
stdout
User response:
none
BHG5013
BHG5008
Configuring %1 alias %2 on host %3
Destination:
stdout
BHG5009
Starting %1 alias %2 on host %3
Explanation:
The specified alias is being started on the node
System action:
none
Setting remote name %1 for %2 %3 in

%4
Explanation:
The name of a resource controller is being set in the
smappl
System action:
none
User response:
none
Chapter 2. BHG...
561
BHG5014 BHG5022
Destination:
stdout
BHG5014
BHG5018
Configuration for host %1 completed

successfully.
Explanation:
Configuration of CICS SM for AIX has completed for this
node
System action:
none
User response:
none
Destination:
stdout
BHG5015
Explanation:
The configuration has failed for this node. Preceding
messages will indicate the problem(s) encountered.
System action:
none
User response:
none
Destination:
stdout
BHG5016
Explanation:
Configuration could not complete as a server could not
be started.
System action:
Configuration terminates
User response:
Check the .console file for the server in /var/cicssm/log
to identify the cause of the problem
Destination:
stdout
BHG5019
Configuration for host %1 failed.
Explanation:
Configuration needs to start components that require
DSOM to be running but the daemon (somdd) could not
be started.
System action:
System action:
none
User response:
Information only.
Destination:
stdout
System action:
User response:
Correct the node name.
Destination:
stdout
Destination:
stdout
BHG5022
Alias %1 already exists in the

Explanation:
An alias is already defined to DSOM
System action:
Configuration continues
User response:
Information only.
Destination:
stdout
562
node name %1 specified in

configuration file can not be \ resolved
Explanation:
A node name in the cicssm.config file can not be
resolved. Names must be able to be resolved by the
host command.
User response:
Check the somdd console log in /var/cicssm/log to
identify the problem that DSOM encountered
BHG5017
Adding alias %1 to the implementation

\ repository
Explanation:
The alias is being defined to DSOM
BHG5021
Unable to start DSOM daemon.
Unable to start server %1
Configuring WLM application %1
Explanation:
The specified WLM application is being configured
System action:
none
User response:
none
Destination:
stdout
BHG5023 BHG5034
BHG5023
Configuring WLM client group %1
Explanation:
The specified WLM client group is being configured
System action:
none
User response:
none
Destination:
stdout
BHG5028
Unable to define node %1 to server

%1. \ Return code %2.
System action:
User response:
This could be caused if the resource controller is
already defined to itself. This can occur when re-running
the configuration process.
Destination:
stdout
DSOM daemon (somdd) must be

running to start CICS SM components
Explanation:
somdd is not running but is required to start the
requested component
System action:
The program exits
Destination:
stdout
BHG5032
EUI user %1 is not configured for host

%2
Explanation:
A request has been mada to start an EUI for a userid
that has not been defined and configured.
System action:
The program exits
User response:
define the user in the cicssm.config file and re-run
configuration
Unable to set host_name attribute of

server %1. \ Return code %2.
Explanation:
An attempt to set the host_name attribute for a CICS
Resource Controller has failed
System action:
User response:
Check the .console file for the resource controller to
Destination:
stdout
BHG5030
BHG5031
User response:
Start the DSOM daemon with cicssm start somdd
Explanation:
An attempt to define a server to itself has failed.
BHG5029
stdout
Destination:
stdout
BHG5033
Starting EUI alias %1 connected to

manager %2. \ Messages directed to
%3
Explanation:
Information only.
System action:
none
User response:
none

bhg_start.sh [-a server alias] [-s] [-e eui
manager]\n\n \ \t\t -e = start eui.
Specify manager to connect to \n \ \t\t
-a = start alias (manager or resource
controller) \n \ \t\t -s = start som
daemon (somdd)
Explanation:
System action:
The program exits
User response:
Destination:
stdout
BHG5034
EUI alias %1 is running on DSOM port

%2. \ Process id %3.
Explanation:
Information only.
System action:
none
User response:
none
Destination:
stdout
Destination:
Chapter 2. BHG...
563
BHG5035 BHG5043
BHG5035
Server alias %1 not defined in DSOM \

implementation repository.
Explanation:
The alias specified is not defined to DSOM
System action:
start command terminates
User response:
The name specified on the cicssm start command has
not been defined in the cicssm.config file.
Destination:
stdout
BHG5036
BHG 5040
Server alias %1 failed to start.
Explanation:
The server %1 has not started.
System action:
none
User response:
The request to start the server waited for 2 minutes for
the server to start. The server encountered a problem or
machine performance os poor. Check the .console log
for the server in /var/cicssm/log to identify the problem
Destination:
stdout
Starting server alias %1. Messages

directed to %2
BHG5041
EUI alias %1 has process id %2
Explanation:
Information only.
Explanation:
Information only.
System action:
none
System action:
none
User response:
none
User response:
none
Destination:
stdout
Destination:
stdout
BHG5037

bhg_wlm_start.sh [-w wap-name] [-h
wap-name] [-m wap-name] [-r]\n\n \ \t\t
-w = start wap with given name \n \ \t\t
-h = start health monitor connected to
wap with given name \n \ \t\t -m = start
cache manager connected to wap with
given name \n \ \t\t -r = start wlm
routing monitor
Explanation:
System action:
The program exits
User response:
Destination:
stdout
BHG5038
Waiting for server alias %1, process id

%2, \ to start
Explanation:
Information only.
System action:
none
User response:
none
Destination:
stdout
BHG5043
Server alias %1 process id %2 is no

longer running
Explanation:
Information only.
System action:
none
Starting DSOM daemon (somdd)
Explanation:
Information only.
System action:
none
User response:
none
Destination:
stdout
564
BHG5042
User response:
none
Destination:
stdout
BHG5044 BHG5618
BHG5044
Server alias %1 is running on DSOM

port %2. \ Process id %3.
Explanation:
Information only.
System action:
none
User response:
none
Destination:
stdout
BHG5045
Server alias %1 started successfully
System action:
none
User response:
none
Destination:
stdout
Workload Management Application %1
is already running. \ Process id %2.
System action:
none
User response:
none
Destination:
stdout
BHG5052
WLM interface to smappl %1 has been

started. \ Messages directed to %2.
Process id %3.
System action:
none
User response:
none
Destination:
stdout
BHG5616
Attempting to set state of region %1 to

starting.
System action:
None.
User response:
None.
Destination:
stdout
BHG5617
Attempting to cold start region %1.
Explanation:
User update.
WLM Application %1 has been started.
Messages directed to %2. \ Process id
%3.
Explanation:
Information only.
System action:
none
User response:
none
Destination:
stdout
BHG5051
Destination:
stdout
Explanation:
User update.
Explanation:
Information only.
BHG5049
User response:
none
Explanation:
Information only.
Explanation:
Information only.
BHG 5047
none
System action:
None.
User response:
None.
Destination:
stdout
BHG5618
Attempting to warm start region %1.
Explanation:
User update.
System action:
None.
Workload Management interface to %1

is already running. \ Process id %2.
Explanation:
Information only.
User response:
None.
Destination:
stdout
System action:
Chapter 2. BHG...
565
BHG5619 BHG5627
BHG5619
Start of region %1 has failed.
User response:
None.
Explanation:
The specified cics region could not be started on the
host machine.
Destination:
stdout
System action:
Program terminates.
BHG5624
User response:
Contact IBM Service if unable to identify the problem.
Destination:
stdout
BHG5620
Start of region %1 was successful.
User response:
None.
Destination:
stdout
up.
Attempting normal stop of region %1.
Explanation:
User update.
User response:
None.
Destination:
stdout
System action:
None.
User response:
None.
BHG5626
Stop of region %1 has failed.
Explanation:
The specified running cics region could not be stopped.
System action:
Program terminates.
Destination:
stdout
quiescing.
Explanation:
User update.
System action:
None.
User response:
None.
Destination:
stdout
User response:
Destination:
stdout
BHG5627
Stop of region %1 was successful.
Explanation:
User update.
System action:
None.
User response:
None.
Attempting to cancel stop region %1.
Explanation:
User update.
System action:
None.
566
BHG5625
System action:
None.
Explanation:
User update.
BHG5623
User response:
None.
Destination:
stdout
System action:
None.
BHG5622
Explanation:
User update.
System action:
None.
Explanation:
User update.
BHG5621
Attempting to immediate stop region

%1.
Destination:
stdout
BHG5628 BHG5636
BHG5628

terminating.
Destination:
stdout
Explanation:
User update.
System action:
None.
User response:
None.
BHG5633
Attempting to deinstall region %1.
Explanation:
User update.
System action:
None.
Destination:
stdout
BHG5629
User response:
None.
Attempting to terminate region %1.
User response:
None.
Destination:
stdout
Explanation:
User update.
System action:
None.
BHG5634
User response:
None.
Explanation:
The specified cics region could not be deinstalled from
the host machine.
Destination:
stdout
BHG5630
System action:
Program terminates.
Terminate of region %1 has failed.
Explanation:
The specified cics region could not be terminated.
System action:
Program terminates.
User response:
Destination:
stdout
BHG5631
User response:
Destination:
stdout
BHG5635
Deinstall of region %1 was successful.
Explanation:
User update.
System action:
None.
Terminate of region %1 was

successful.
User response:
None.
Destination:
stdout
Explanation:
User update.
System action:
None.
User response:
None.
Destination:
stdout
BHG5632
Deinstall of region %1 has failed.
BHG5636

created.
Explanation:
User update.
System action:
None.

deinstalling.
Explanation:
User update.
User response:
None.
Destination:
stdout
System action:
None.
Chapter 2. BHG...
567
BHG5637 BHG5645
BHG5637
Starting discovery of cics region %1.
Explanation:
User update.
Destination:
stdout
System action:
None.
User response:
None.
Destination:
stdout
BHG5638
%1 is not a recognized action for this

object.
System action:
Program terminates.
User response:
Retry with correct action parameter.
Destination:
stdout
Attempting to get initial state of %1.
System action:
None.
User response:
None.
Failed to obtain the initial state of %1.
Explanation:
The state of the named object in the instance network
was not returned.
System action:
Program termination.
User response:
Destination:
stdout
Attempting to set state of sfs server
%1 to installing.
Explanation:
User update.
System action:
None.
568
Explanation:
Attempt at setting an object state has failed.
User response:
Destination:
stdout
BHG5643
Attempting to install sfs server %1.
Explanation:
User update.
System action:
None.
Destination:
stdout
BHG5644
Install of sfs server %1 has failed.
Explanation:
The specified sfs server could not be installed on the
host machine.
System action:
Program terminates.
Destination:
stdout
BHG5641
Failed to set state of sfs server %1.
User response:
None.
Explanation:
User update.
BHG5640
BHG5642
System action:
Program terminates.
Explanation:
The user has asked for an action on this object which is
not allowed.
BHG5639
User response:
None.
User response:
Destination:
stdout
BHG5645
Resetting state of sfs server %1.
Explanation:
User update.
System action:
Usually program will terminate shortly after this
message.
User response:
None.
Destination:
stdout
BHG5646 BHG5654
BHG5646
Install of sfs server %1 was

successful.
Destination:
stdout
Explanation:
User update.
System action:
None.
User response:
None.
Destination:
stdout
BHG5647

%1 to down.
User response:
None.
Destination:
stdout
Explanation:
User update.
User response:
None.
BHG5652

%1 to starting.
Explanation:
User update.
System action:
None.

%1 to initializing.
User response:
None.
Destination:
stdout
Explanation:
User update.
System action:
None.
User response:
None.
BHG5653
Attempting cold start of sfs server %1.
Explanation:
User update.
System action:
None.
Destination:
stdout
Attempting to initialize sfs server %1.
User response:
None.
Destination:
stdout
Explanation:
User update.
System action:
None.
User response:
None.
Destination:
stdout
BHG5650

%1 to stopped.
Destination:
stdout
System action:
None.
BHG5649
BHG5651
System action:
None.
Explanation:
User update.
BHG5648
User response:
None.
BHG5654
Attempting warm start of sfs server

%1.
Explanation:
User update.
System action:
None.
Initialize of sfs server %1 was

successful.
Explanation:
User update.
User response:
None.
Destination:
stdout
System action:
None.
Chapter 2. BHG...
569
BHG5655 BHG5663
BHG5655
Start of sfs server %1 has failed.
User response:
None.
Explanation:
The specified sfs server could not be started on the
host machine.
Destination:
stdout
System action:
Program terminates.
BHG5660
User response:
Explanation:
The specified sfs server could not be stopped on the
host machine.
Destination:
stdout
BHG5656
System action:
Program terminates.
Start of sfs server %1 was successful.
Explanation:
User update.
User response:
None.
Destination:
stdout
%1 to up.
User response:
None.
Destination:
stdout
Explanation:
User update.
User response:
None.
BHG5662

%1 to terminating.
Explanation:
User update.
System action:
None.

%1 to quiescing.
Explanation:
User update.
User response:
None.
Destination:
stdout
System action:
None.
User response:
None.
Destination:
stdout
BHG5663
Attempting to terminate sfs server %1.
Explanation:
User update.
System action:
None.
Attempting to stop sfs server %1.
Explanation:
User update.
System action:
None.
570
Shutdown of sfs server %1 was

successful.
Destination:
stdout
System action:
None.
BHG5659
BHG5661
System action:
None.
Explanation:
User update.
BHG5658
User response:
Destination:
stdout
System action:
None.
BHG5657
Shutdown of sfs server %1 has failed.
User response:
None.
Destination:
stdout
BHG5664 BHG5673
BHG5664
Terminate of sfs server %1 was

successful.
Destination:
stdout
Explanation:
User update.
System action:
None.
User response:
None.
Destination:
stdout
BHG5665

%1 to deinstalling.
User response:
None.
Destination:
stdout
Explanation:
User update.
User response:
None.
BHG5671
Attempting to set state of sfs schema

%1 to installing.
Explanation:
User update.
System action:
None.
Attempting to deinstall sfs server %1.
Explanation:
User update.
User response:
None.
Destination:
stdout
System action:
None.
User response:
None.
Destination:
stdout
BHG5672
Failed to set state of sfs schema %1.
Explanation:
Attempt at setting an object state has failed.
System action:
Program terminates.
Deinstall of sfs server %1 has failed.
User response:
Explanation:
The specified sfs server could not be stopped on the
host machine.
Destination:
stdout
System action:
Program terminates.
BHG5673
User response:
Attempting to install sfs schema %1.
Explanation:
User update.
System action:
None.
Destination:
stdout
BHG5668

%1 to created.
Destination:
stdout
System action:
None.
BHG5667
BHG5669
System action:
None.
Explanation:
User update.
BHG5666
User response:
None.
Deinstall of sfs server %1 was

successful.
Explanation:
User update.
User response:
None.
Destination:
stdout
System action:
None.
Chapter 2. BHG...
571
BHG5674 BHG5682
BHG5674
Install of sfs schema %1 has failed.
Explanation:
The specified sfs schema file could not be installed.
System action:
Program terminates.
User response:
Destination:
stdout
BHG5675
Resetting state of sfs schema %1.
User response:
None.
Destination:
stdout
Install of sfs schema %1 was
successful.
Explanation:
User update.
User response:
None.
BHG5680
Initialize of sfs schema %1 was

successful.
Explanation:
User update.
User response:
None.
Destination:
stdout
System action:
None.
User response:
None.
Destination:
stdout
BHG5681

%1 to stopped.
Explanation:
User update.
System action:
None.

%1 to down.
User response:
None.
Destination:
stdout
Explanation:
User update.
System action:
None.
User response:
None.
Destination:
stdout
BHG5682

%1 to starting.
Explanation:
User update.
System action:
None.

%1 to initializing.
Explanation:
User update.
System action:
None.
572
Attempting to initialize sfs schema %1.
System action:
None.
Explanation:
User update.
BHG5678
BHG5679
Destination:
stdout
System action:
Usually program will terminate shortly after this
message.
BHG5677
Destination:
stdout
System action:
None.
Explanation:
User update.
BHG5676
User response:
None.
User response:
None.
Destination:
stdout
BHG5683 BHG5691
BHG5683
Attempting to start sfs schema %1.
Explanation:
User update.
Destination:
stdout
System action:
None.
User response:
None.
Destination:
stdout
BHG5684
Start of sfs schema %1 was

successful.
User response:
None.
Destination:
stdout
Explanation:
User update.
User response:
None.
BHG5689

%1 to terminating.
Explanation:
User update.
System action:
None.

%1 to up.
Explanation:
User update.
User response:
None.
Destination:
stdout
System action:
None.
User response:
None.
Destination:
stdout
BHG5690
Attempting to terminate sfs schema

%1.
Explanation:
User update.
System action:
None.

%1 to quiescing.
Explanation:
User update.
User response:
None.
Destination:
stdout
System action:
None.
User response:
None.
Destination:
stdout
BHG5687
Stop of sfs schema %1 was

successful.
Destination:
stdout
System action:
None.
BHG5686
BHG5688
System action:
None.
Explanation:
User update.
BHG5685
User response:
None.
BHG5691
Terminate of sfs schema %1 was

successful.
Explanation:
User update.
System action:
None.
Attempting to stop sfs schema %1.
Explanation:
User update.
System action:
None.
User response:
None.
Destination:
stdout
Chapter 2. BHG...
573
BHG5692 BHG5700
BHG5692

%1 to deinstalling.
Destination:
stdout
Explanation:
User update.
System action:
None.
User response:
None.
Destination:
stdout
BHG5693
BHG5697
Attempting to add sfs schema %1 to

server %2.
Explanation:
User update.
System action:
None.
Attempting to deinstall sfs schema %1.
Explanation:
User update.
User response:
None.
Destination:
stdout
System action:
None.
User response:
None.
Destination:
stdout
BHG5694
User response:
None.
Deinstall of sfs schema %1 has failed.
BHG5698
Addition of sfs schema %1 to server

%2 was unsuccessful.
Explanation:
The specified sfs schema file did not create any files on
the sfs server.
System action:
Program terminates.
Explanation:
The specified sfs schema file could not be deinstalled.
User response:
System action:
Program terminates.
Destination:
stdout
User response:
BHG5699
Destination:
stdout
BHG5695
Addition of sfs schema %1 to server

%2 was successful.
Explanation:
User update.
Deinstall of sfs schema %1 was
successful.
System action:
None.
Explanation:
User update.
User response:
None.
System action:
None.
Destination:
stdout
User response:
None.
BHG5700
Destination:
stdout
BHG5696
Attempting to delete sfs schema %1

from server %2.
Explanation:
User update.
%1 to created.
System action:
None.
Explanation:
User update.
User response:
None.
System action:
None.
Destination:
stdout
574
BHG5701 BHG5709
BHG5701
Deletion of %1 sfs schema data from

server %2 was unsuccessful.
Explanation:
The sfs files could not be deleted from the server.
System action:
Program terminates.
User response:
Destination:
stdout
BHG5702
Destination:
stdout
BHG5706
Deletion of %1 sfs schema data from

server %2 was successful.
Explanation:
The specified cics resource definition could not be
added to the regions permanent database.
User response:
Destination:
stdout
System action:
None.
User response:
None.
Destination:
stdout
BHG5707
Setting resource %1 to %2.
System action:
None.
Explanation:
User update.
User response:
None.
Destination:
stdout
User response:
None.
BHG5708
Destination:
stdout
Explanation:
User update.
Attempting to install resource %1 on
region %2.
Explanation:
User update.
System action:
None.
User response:
None.
Destination:
stdout
BHG5709
Destination:
stdout
Explanation:
User update.
cicsadd -c %1 -r %2 -P %3 %4
Attempting to set state of resource %1

to down.
System action:
None.
User response:
None.
BHG5705
Install of resource %1 on region %2

was successful.
System action:
None.
Explanation:
User update.
BHG5704
Install of resource %1 on region %2

was unsuccessful.
System action:
Program terminates.
Explanation:
User update.
BHG5703
User response:
None.
Attempting to initialize resource %1 on

region %2.
System action:
None.
Explanation:
User update.
User response:
None.
System action:
None.
Destination:
stdout
Chapter 2. BHG...
575
BHG5710 BHG5718
BHG5710
cicsupdate -c %1 -r %2 -R %3 %4
User response:
None.
Explanation:
User update.
System action:
None.
User response:
None.
Initialize of resource %1 on region %2

was unsuccessful.
Explanation:
added to the regions runtime database.
System action:
Program terminates.
User response:
Destination:
stdout
BHG5712
Initialize of resource %1 on region %2

was successful.
Explanation:
User update.
System action:
None.
User response:
None.

to stopped.
Explanation:
User update.
System action:
None.
User response:
None.
Attempting to terminate resource %1

on region %2.
Explanation:
User update.
System action:
576
cicsdelete -c %1 -r %2 -R %3 %4
System action:
None.
User response:
None.
Destination:
stdout
BHG5716
Terminate of resource %1 on region

%2 was unsuccessful.
Explanation:
deleted from the regions runtime database.
System action:
Program terminates.
User response:
Destination:
stdout
BHG5717
Terminate of resource %1 on region

%2 was successful.
System action:
None.
User response:
None.
Destination:
stdout
BHG5718
Attempting to deinstall resource %1

from region %2.
Explanation:
User update.
Destination:
stdout
BHG5714
BHG5715
Explanation:
User update.
Destination:
stdout
BHG5713
Destination:
stdout
Explanation:
User update.
Destination:
stdout
BHG5711
None.
System action:
None.
User response:
None.
Destination:
stdout
BHG5719 BHG5727
BHG5719
cicsdelete -c %1 -r %2 -P %3 %4
Explanation:
User update.
Destination:
stdout
System action:
None.
User response:
None.
Destination:
stdout
BHG5720
User response:
None.
BHG5724
Explanation:
User update.
System action:
None.
Deinstall of resource %1 on region %2
was unsuccessful.
User response:
None.
Explanation:
deleted from the regions permanent database.
Destination:
stdout
System action:
Program terminates.
BHG5725
User response:
Destination:
stdout
BHG5721
Deinstall of resource %1 on region %2

was successful.
Explanation:
The specified cics agent transaction definition could not
be added to the cics regions permanent database.
User response:
Destination:
stdout
System action:
None.
User response:
None.
Destination:
stdout
BHG5726
Resetting state of cics agent tran %1

on region %2.
Explanation:
User update.
System action:
None.

to created.
Explanation:
User update.
User response:
None.
Destination:
stdout
System action:
None.
User response:
None.
Destination:
stdout
BHG5723
Install of cics agent tran %1 on region

%2 failed.
System action:
Program terminates.
Explanation:
User update.
BHG5722
Attempting to install cics agent tran

%1 on region %2.
BHG5727
Install of cics agent tran %1 on region

%2 was successful.
Explanation:
User update.
System action:
None.
Starting discovery of node %1
Explanation:
User update.
System action:
None.
User response:
None.
Destination:
stdout
Chapter 2. BHG...
577
BHG5728 BHG5736
BHG5728
Setting state of cics agent tran %1 on

region %2 to down.
User response:
Explanation:
User update.
System action:
None.
User response:
None.
Destination:
stdout
BHG5729
Attempting to initialize cics agent tran

%1 on region %2.
User response:
None.
Destination:
stdout
region %2 to stopped.
System action:
None.
Destination:
stdout
BHG5734

region %2 to up.
System action:
None.
User response:
None.
System action:
None.
User response:
None.
Destination:
stdout
Destination:
stdout
BHG5735
Attempting to stop cics agent tran %1

on region %2.
Explanation:
User update.
Attempting to start cics agent tran %1
on region %2.
System action:
None.
User response:
None.
Explanation:
User update.
System action:
None.
User response:
None.
Destination:
stdout
Destination:
stdout
BHG5736
Stop of cics agent tran %1 on region

%2 failed.
Explanation:
The specified cics agent transaction could not be
stopped on the running region.
Start of cics agent tran %1 on region
%2 failed.
Explanation:
The specified cics agent transaction could not be
started on the running region.
578
Start of cics agent tran %1 on region

%2 was successful.
Explanation:
User update.
Explanation:
User update.
BHG5732
BHG5733
User response:
None.
System action:
None.
BHG5731
Destination:
stdout
Explanation:
User update.
Explanation:
User update.
BHG5730
System action:
Program terminates.
System action:
Program terminates.
User response:
BHG5737 BHG5750
Destination:
stdout
BHG5737
BHG5741
Stop of cics agent tran %1 on region

%2 was successful.
System action:
None.
User response:
None.
Destination:
stdout
Attempting to terminate cics agent tran
%1 on region %2.
Destination:
stdout
User response:
None.
Destination:
stdout
Explanation:
User update.
User response:
None.
Destination:
stdout
BHG5743
Attempting to deinstall cics agent tran

%1 from region %2.
%1 seconds spent waiting on lock for

%2.
Explanation:
User update.
System action:
None.
Explanation:
User update.
System action:
None.
User response:
None.
Destination:
stdout
User response:
None.
Destination:
stdout
BHG5744
Deinstall of cics agent tran %1 on

region %2 failed.
Explanation:
The specified cics agent transaction definition could not
be removed from the regions permanent database.
Forcibly removing lock for %1.
Explanation:
User update.
System action:
None.
User response:
None.
System action:
Program terminates.
Destination:
stdout
User response:
BHG5750
Destination:
stdout

region %2 to created.
System action:
None.
System action:
None.
BHG5740
User response:
None.
BHG5742
Explanation:
User update.
BHG5739
Explanation:
User update.
System action:
None.
Explanation:
User update.
BHG5738
Deinstall of cics agent tran %1 from

region %2 was successful.
Syntax: \n\n \ bhgvstate.sh server node

-r region [-F] \n \ server = alias of
cicssm server\n \ node = name of host
\n \ region = name of cics region whose
state is being verified. \n \ [-F] =
optional flag to force region into
correct state. \n
Chapter 2. BHG...
579
BHG5751 BHG5757
Explanation:
Usage message to user.
System action:
Usually the program terminates.

Destination:
stdout
User response:
Re-issue the command with the correct parameters.
BHG5754
Destination:
stdout
Explanation:
A system call to get the lifecycle state of the network
object representing the named cics region resulted in a
bad return code being returned.
BHG5751
Region %1 installed on host %2 but

unable to query \ src daemon for
status.
Explanation:
A query of the host machines src daemon resulted in a
bad return code. The cics regions state could not be
determined although an entry for it exists in the local
directory /var/cics_regions indicating that the region has
at least been installed on the host.
System action:
Program terminates.
User response:
Check status of the src daemon on the local host.
Restart if necessary. Contact IBM Service if unable to
identify the problem.
Destination:
stdout
BHG5752
Failed to read state of cics region %1

in network.
System action:
Program terminates.
User response:
Destination:
stdout
BHG5755
Region %1 on host %2 is correctly set

to created.
Explanation:
User update.
System action:
Program terminates.
User response:
None.
Region %1 not installed on host %2.

Setting state to created.
Destination:
stdout
Explanation:
A query of the host machines src daemon resulted in a
bad return code. The cics regions state could not be
determined. No entry was found in the local directory
/var/cics_regions. The region does not exist on the
named host.
BHG5756
System action:
Program terminates.
System action:
Program terminates.
User response:
Check status of the src daemon on the local host.
Restart if necessary. Contact IBM Service if unable to
identify the problem.
User response:
Retry command with the -F option to try and force the
region into the correct state. Contact IBM Service if
unable to identify the problem.
Destination:
stdout
Destination:
stdout
BHG753
Unable to find cics region %1 network

object.
Region %1 on host %2 is in an
incorrect state.
Explanation:
User update. The named cics regions network object is
in a state which does not agree with the real world.
BHG5757
Failed to set region %1 on host %2 to

the correct state.
Explanation:
The instance network object representing the named
cics region could not be found.
Explanation:
The SOM call to set the named cics regions object
state failed. The object remains in an incorrect state.
System action:
Program terminates.
System action:
Program terminates.
User response:
User response:
580
BHG5758 BHG5766
Destination:
stdout
BHG5758
The state of region %1 on host %2 has

been set to created.
User response:
None.
Destination:
stdout
Region %1 on host %2 is in a
transition state at the moment.
System action:
Program terminates.
User response:
Retry the command after the region has settled to a
steady state.
BHG5763

to stopped.
System action:
Program terminates.
User response:
None.
Destination:
stdout
BHG5764
Attempting to set region %1 on host

%2 to stopped.
Explanation:
User update.
Destination:
stdout
to up.
Explanation:
User update.
System action:
Program terminates.
User response:
None.
System action:
The setting of the named objects state is attempted.
User response:
None.
Destination:
stdout
BHG5765

been set to stopped.
Explanation:
User update.
Destination:
stdout
%2 to up.
Explanation:
User update.
System action:
User response:
None.
Destination:
stdout
Destination:
stdout
Explanation:
User update.
Explanation:
The named cics region is currently between object life
cycle states at the moment (eg, in stopping or starting).
BHG5761
System action:
Program terminates.
User response:
None.
System action:
Program terminates.
BHG5760

been set to up.
Explanation:
User update.
Explanation:
User update.
BHG5759
BHG5762
System action:
Program terminates.
User response:
None.
Destination:
stdout
BHG5766

to down.
Explanation:
User update.
System action:
Chapter 2. BHG...
581
BHG5767 BHG5775
Program terminates.
User response:
None.
BHG5772
Destination:
stdout
BHG5767

%2 to down.
System action:
User response:
None.
Destination:
stdout
been set to down.
User response:
None.
Destination:
stdout
Destination:
stdout
Sfs server %1 was successfully
installed.
Explanation:
User update.
User response:
None
Destination:
stdout
BHG5774
Syntax: \n\n \ bhsfsinst.sh -s sfs server

sfs server= full name of the sfs server
to be installed.\n
Explanation:
System action:
User response:
Destination:
stdout
Install of sfs server %1 has
unsuccessful.
System action:
Program terminates.
User response:
Removing SSD debris after failed

install of sfs server %1.
Explanation:
User update.
System action:
None.
User response:
None
Destination:
stdout
BHG5775
Explanation:
A problem occurred during the attempted installation of
the named sfs server on a host.
582
User response:
None
System action:
Program terminates.
System action:
Program terminates.
BHG5771
Explanation:
The attempted installation of the sfs server failed
because it already exists on the host.
BHG5773
Explanation:
User update.
BHG5770
Sfs server %1 has already been

installed on host.
System action:
Program terminates with a good return code (not an
error).
Explanation:
User update.
BHG5768
Destination:
stdout
SSD clean up completed after failed

install of sfs server %1.
Explanation:
User update.
System action:
Program terminates.
User response:
None
Destination:
stdout
BHG5776 BHG5793
BHG5776
Unable to complete SSD clean up after

failed install of \ sfs server %1.
Explanation:
The attempted removal from the host machines SSD
stanza file of the entry for the sfs server whose install
did not complete failed.
System action:
Program terminates.
User response:
Destination:
stdout
BHG5780
Syntax: \n\n \ bhsfsdeinst.sh -s sfs

server sfs server = full name of the sfs
server to be removed from host.
System action:
User response:
Destination:
stdout
unsuccessful.
Explanation:
The named sfs server was not completely removed from
the host machine.
System action:
Program terminates.
User response:
Destination:
stdout
BHG5782
Explanation:
System action:
User response:
BHG5791
Sfs server %1 not installed on host.

Start fails.
Explanation:
The named sfs server does not exist on the node ; it
has not been installed.
System action:
Program terminates.
User response:
Install the sfs server on the host machine and then retry
this command. Contact IBM Service if unable to identify
the problem.
Destination:
stdout
BHG5792
Attempting cold start of sfs server %1.
Explanation:
User update.
System action:
None
User response:
None
Destination:
stdout

completely successful.
Explanation:
User update.
System action:
Program terminates.
User response:
None.
Destination:
stdout
Syntax: \n\n \ bhsfsstart.sh -s sfs server

sfs server = full name of the sfs server
to be removed from host.\n \ [c] =
optional flag requesting cold start of
the sfs server. \n
Destination:
stdout
Explanation:
BHG5781
BHG5790
BHG5793
Attempting warm start of sfs server

%1.
Explanation:
User update.
System action:
None
User response:
None
Destination:
stdout
Chapter 2. BHG...
583
BHG5794 BHG5811
BHG5794
Warm start of sfs server %1 failed.

Attempting a cold start.
Explanation:
User update. A warm start action was requested on an
sfs server which has never previously been active
before.
System action:
None
User response:
None
Destination:
stdout
BHG5795
Start of sfs server %1 failed.
System action:
Program terminates.
User response:
Destination:
stdout
Stop of sfs server %1 has failed.
Explanation:
User update.
System action:
Program terminates.
User response:
Destination:
stdout
BHG5802
Explanation:
The named sfs server could not be started on the host
machine.
BHG5796
BHG5801
Stop of sfs server %1 has completed

successfully.
Explanation:
User update.
System action:
Program terminates.
User response:
None.
Destination:
stdout
BHG5810
Start of sfs server %1 was successful.
Syntax: \n\n \ bhg_hmon.sh server node

\n \ server = alias of the SOM server to
which health monitor will connect.\n\
node = name of the node.\n
Explanation:
User update.
Explanation:
System action:
Program terminates.
System action:
User response:
None
User response:
Destination:
stdout
Destination:
stdout
BHG5800
Syntax: \n\n \ bhsfsstop.sh -s sfs server

sfs server = full name of the sfs server
to be stopped.\n
BHG5811
Need root authority to run this

command.
Explanation:
Explanation:
User has insufficient authority to start the health
monitor.
System action:
System action:
Program exits.
User response:
User response:
Authenticate as root and then re-try command.
Destination:
stdout
Destination:
stdout
584
BHG5812 BHG5827
BHG5812
There is already a health monitor

running on this node.
Explanation:
During the preliminary start up of the health monitor, the
presence of another running health monitor was
detected.

Destination:
stdout
BHG5822
Deinstall of cics region %1 has

completed successfully.
System action:
Program exits.
Explanation:
User update.
User response:
This health monitor cannot be started until the other
running health monitor process is terminated. Monitor
precedence is up to the user.
System action:
Program terminates.
Destination:
stdout
BHG5813
User response:
None.
Destination:
stdout
Unable to query hosts src daemon for

active cics regions.
Explanation:
Before starting off the main health monitor, this
preliminary script will attempt to find out the names of
any cics regions currently active on this host. These will
be passed to the main health monitor when it is
invoked. If the hosts src daemon does not give a good
response when queried about running cics regions then
the health monitor start up will continue but obviously
without any of this information.
BHG5825
Explanation:
System action:
User response:
System action:
None.
Destination:
stdout
User response:
Check status of the src daemon on the host machine.
BHG5826
Destination:
stdout
BHG5820

command.
Explanation:
User has insufficient authority to use this command.
Syntax: \n\n \ bhdeinst.sh -r region \n \
region = name of the cics region to be
deinstalled from the host.\n
Explanation:
System action:
System action:
Program exits.
User response:
Destination:
stdout
User response:
BHG5827
Destination:
stdout
Explanation:
User update.
BHG5821
Syntax: \n\n \ bhg_cat_install.sh -r

region \n \ region = name of the cics
region to be initialized.\n
Deinstall of cics region %1 has failed.
The cics region %1 has already been

initialized.
System action:
Program exits with good return code.
Explanation:
User update.
User response:
None.
System action:
Program terminates.
Destination:
stdout
User response:
Chapter 2. BHG...
585
BHG5828 BHG5835
BHG5828
Initialization of cics region %1 was not

completely successful.
Explanation:
Some or all of the resource additions to the named cics
region did not complete successfully.
System action:
Program exits.
User response:
Destination:
stdout
BHG5829
BHG5832
Attempting cold start of region %1.
Explanation:
User update.
System action:
None.
User response:
None.
Destination:
stdout
The cics region %1 was successfully

initialized.
Explanation:
User update.
System action:
Program exits.
User response:
None.
Destination:
stdout
BHG5830
Destination:
stdout
BHG5833
Attempting auto (warm) start of region

%1.
Explanation:
User update.
System action:
None.
User response:
None.
Destination:
stdout
Syntax: \n\n \ bhsstart.sh -r region [ a |

c ] \n \ region = name of the cics region
to be started.\n\ [a] = flag indicating
auto (warm) start of region to be
attempted. \n\ [c] = flag indicating cold
start of region to be attempted.\n \ The
default start type is auto. \n
BHG5834
Region %1 is already running.
Explanation:
User update.
System action:
None.
Explanation:
User response:
None.
System action:
Destination:
stdout
User response:
BHG5835
Destination:
stdout
BHG5831
Explanation:
The start up of the specified cics region did not
complete successfully.
Region %1 does not exist on host.
Start action cannot proceed.
Explanation:
A check of the hosts /var/cics_regions directory
indicates that the region to be started has not been
installed yet. The start action must fail.
System action:
Program terminates.
User response:
Install the region on the host before attempting to start
it. Contact IBM Service if unable to identify the problem.
586
Region %1 could not be started.
System action:
Program terminates.
User response:
Destination:
stdout
BHG5836 BHG5847
BHG5836
The start of cics region %1 has

Explanation:
User update.
System action:
Program terminates.
User response:
None.
Destination:
stdout
BHG5840
Explanation:
User update.
System action:
None.
User response:
None.
Destination:
stdout
BHG5845
BHG5837
cics region %1 has abnormally

terminated. Start failed.
Explanation:
The specified cics region was successfully started but
was then shut down by a problem in the start up phase.
See the regions console.msg file for details.
System action:
Program terminates.
User response:
Destination:
stdout
BHG5838
cics region %1 has not started after %2

minutes.
System action:
Program terminates.
User response:
Destination:
stdout
cics regions status.
Explanation:
An attempt to verify that the named cics region was not
already active on this host failed because of a bad
return code from the hosts src daemon. The requested
region start operation continues.
System action:
None.
User response:
Destination:
stdout
Syntax: \n\n \ bhsstop.sh -r region [ i | c

] \n \ region = name of the cics region
to be stopped.\n \ [i] = flag indicating
immediate stop type is to be
attempted. \n \ [c] = flag indicating
cancel stop type is to be attempted. \n
\ The default stop type is normal
stop.\n
Explanation:
System action:
User response:
Explanation:
The cics region has not become fully operational after
the specified time limit has elapsed. See the regions
console.msg file for details.
BHG5839
Removing lock file for cics region %1.
Destination:
stdout
BHG846
Region %1 does not exist on host.

Stop action cannot proceed.
Explanation:
A check of the hosts /var/cics_regions directory
indicates that the region to be stopped has not been
installed yet. The stop action must fail.
System action:
Program terminates.
User response:
Install the region on the host before attempting to
invoke any operations on it. Contact IBM Service if
Destination:
stdout
BHG5847
Region %1 is not currently running.

Stop action cannot proceed.
Explanation:
The region to stop is not active on the host.
System action:
Program terminates with good return code.
User response:
None.
Chapter 2. BHG...
587
BHG5848 BHG5860
Destination:
stdout
BHG5852
BHG5848
Explanation:
The attempt at stopping the specified cics region did not
complete successfully. See the regions console.msg file
for details.

cics regions status.
Explanation:
An attempt to verify that the named cics region was not
already inactive on this host failed because of a bad
return code from the hosts src daemon. The requested
region stop operation continues.
System action:
Program Terminates.
User response:
System action:
None.
Destination:
stdout
User response:
BHG5853
Destination:
stdout
Explanation:
User update.
BHG5849
Immediate shutdown of cics region %1

requested.
Explanation:
User update.
System action:
None.
Region %1 could not be stopped.
Region %1 was stopped successfully.
System action:
Program Terminates.
User response:
None.
Destination:
stdout
User response:
None.
BHG5854
Destination:
stdout
Explanation:
The cics region has not fully shutdown after the
specified time limit has elapsed. See the regions
console.msg file for details.
BHG5850
Cancel shutdown of cics region %1

requested.
Explanation:
User update.
System action:
None.
User response:
None.
BHG5851
Normal shutdown of cics region %1

requested.
Explanation:
User update.
System action:
None.
User response:
None.
Destination:
stdout
588
System action:
Program terminates.
User response:
Destination:
stdout
BHG5860
Destination:
stdout
cics region %1 has not stopped after

%2 minutes.

command.
Explanation:
System action:
Program exits.
User response:
Destination:
stdout
BHG5861 BHG5868
BHG5861
Syntax: \n\n \ bhg_cat_deinstall.sh -r

region \n \ region = name of the cics
region to be terminated.\n
BHG5865
Explanation:
System action:
User response:
Destination:
stdout
BHG5862
Explanation:
Termination of cics region %1 has
failed.
Explanation:
The cicssm program and transaction definitions added
to the named cics regions database during initialization
were not successfully removed.
System action:
Program exits.
User response:
Destination:
stdout
BHG5863
Syntax: \n\n \ bhinst.sh -r region server

host [[attribute/value pairs]]\n \ region =
name of the cics region to be
terminated.\n \ server = alias of the
DSOM server running this command.
\n \ host = fully qualified name of the
host object in the network. \n \
[[attribute/value pairs]] = sequence of
pairs of the form attrib=value>\n \
representing region attributes to be
overridden\n\ upon installation. \n
Termination of cics region %1 has

Explanation:
User update.
System action:
Program exits.
System action:
User response:
Destination:
stdout
BHG5866
Region name %1 is too long. Must be 8

characters or less.
Explanation:
The input name for the region to be installed on the
host is too long.
System action:
Program exits.
User response:
Re-try command with a shorter region name of 8
characters or less.
Destination:
stdout
User response:
None.
BHG5867
Destination:
stdout
Explanation:
The named cics regions default sfs file server has
never been active on the host machine before. CICS
SM will attempt to cold start the sfs server and retry the
region install.
BHG5864
Region %1 already exists on the host

machine.
Explanation:
An attempted region install cannot continue as the
region has already been installed on the host machine.
System action:
Program exits.
User response:
Either deinstall the existing region from the host
machine and then re-try the install command, or else
give up trying to install the region.
Destination:
stdout
Install of region %1 requires cold start

of its sfs server.
System action:
Proceeds to try and cold start the regions sfs server.
User response:
None.
Destination:
stdout
BHG5868
Attempting cold start of default sfs

server %1 for region %2.
Explanation:
User update.
Chapter 2. BHG...
589
BHG5869 BHG5876
System action:
Cold start action attempted.
User response:
None.
Destination:
stdout
Program terminates.
User response:
Destination:
stdout
BHG5873
BHG5869
Sfs server %1 was successfully cold

started.
Explanation:
User update.
System action:
None.
User response:
None.
Destination:
stdout
BHG5870
Explanation:
The named cics regions default sfs server name could
not be determined. Region install fails here.
System action:
Program terminates.
User response:
Destination:
stdout
Region %1 install failed after default

sfs server cold start.
Explanation:
After the named cics regions default sfs server was
cold started on the host machine, a second attempt at
installing the region ended in failure.
System action:
Program terminates.
User response:
Destination:
stdout
BHG5874
Region %1 install completed

successfully.
Region %1s tsq file already existed

before install attempt.
Explanation:
User update.
System action:
None
User response:
None
Destination:
stdout
BHG5875
BHG5871
Unable to obtain name of region %1s

default sfs server. \ Unable to proceed
with install of cics region.
Failed to create tsq file for region %1.

Install fails.
Explanation:
User update.
Explanation:
The named cics regions tsq file could not be created.
See regions console.msg file for more information.
System action:
Program terminates.
System action:
Program terminates.
User response:
None.
User response:
Destination:
stdout
Destination:
stdout
BHG5872
Cold start of sfs server %1 failed.

Unable to proceed with \ install of cics
region %2.
Explanation:
The named cics regions default sfs server could not be
started (warm and cold starts both failed).
Consequently, the cics region install action fails.
System action:
590
BHG5876
Install of cics region %1 has failed.
Explanation:
The named cics region could not be installed on the
host machine. See regions console.msg file for more
information.
System action:
Program terminates.
User response:
BHG5877 BHG5889
BHG5886
Destination:
stdout
BHG5877
Install of cics region %1 has completed

successfully.
Explanation:
User update.
System action:
None.
User response:
None.
Destination:
stdout
BHG5878
Syntax: \n\n \ bhgvsfsstate.sh DSOM

server host -s sfs server [-F]\n \ DSOM
server = alias of the DSOM server
running this command.\n \ host= name
of the host machine where this
command will be run.\n \ sfs server =
full name of the sfs server whose state
is being queried.\n \ [-F] = optional
force of sfs server object to correct
state.\n
Explanation:
System action:
User response:
Customization of region %1s

permanent database failed.
Explanation:
The overriding of the named cics regions stanza
attributes with the attrib=value pairs entered by the user
did not complete successfully.
Destination:
stdout
BHG5887
Unable to find sfs server %1 network

object.
System action:
Program Terminates.
Explanation:
The instance network object representing the named sfs
server could not be found.
User response:
System action:
Program terminates.
Destination:
stdout
User response:
BHG5879
Customization of region %1s

permanent database completed.
Destination:
stdout
Explanation:
User update.
BHG5888
System action:
None.
Explanation:
object representing the named sfs server resulted in a
bad return code being returned.
User response:
None.
System action:
Program terminates.
Destination:
stdout
BHG5885

command.
Explanation:
System action:
Program exits.
User response:
Destination:
stdout
Failed to read state of sfs server %1 in

network.
User response:
Destination:
stdout
BHG5889
sfs server %1 on host %2 is correctly

set to created state.
Explanation:
User update.
System action:
Program terminates.
User response:
Chapter 2. BHG...
591
BHG5890 BHG5897
None.
Destination:
stdout
Destination:
stdout
BHG5894
BHG5890
sfs server %1 on host %2 is set to an

incorrect state.
Explanation:
The named sfs servers representative object in the
global instance network is set to a state which does not
agree with the true state of the sfs server.
System action:
Program terminates.
User response:
Retry the command with the -F option to try and correct
the real world / object state mismatch. Contact IBM
Service if unable to identify the problem.
Attempting to set sfs server %1 to

created.
Explanation:
User update.
System action:
None.
User response:
None.
Failed to set sfs server %1 on host %2

to the correct state.
Explanation:
The SOM call to set the named sfs servers object state
failed. The object remains in an incorrect state.
System action:
Program terminates.
User response:
Destination:
stdout
BHG5893
User response:
None
Destination:
stdout
BHG5895
Attempting to set sfs server %1 to up.
System action:
None.
User response:
None.
Destination:
stdout
BHG- 5896
Sfs server %1 on host %2 was

correctly set to up.
System action:
Program terminates.
User response:
None.
Destination:
stdout
BHG5897

set to stopped state.
Explanation:
User update.
System action:
Program terminates.

correctly set to created.
Explanation:
User update
System action:
Program terminates.
User response:
None.
592
System action:
Program terminates.
Explanation:
User update
Destination:
stdout
BHG5892
Explanation:
User update.
Explanation:
User update.
Destination:
stdout
BHG5891

set to up state.
User response:
None.
Destination:
stdout
BHG5898 BHG5910
BHG5898
Attempting to set sfs server %1 on

host %2 to stopped.
Explanation:
User update.
System action:
None.
User response:
None.
Destination:
stdout
BHG5899

correctly set to stopped.
System action:
Program terminates.
User response:
None.
Destination:
stdout
Explanation:
The instance network object representing the named
ppc gateway server could not be found.
System action:
Program terminates.
User response:
BHG5908
Failed to read state of ppc gateway

server %1 in network.
Explanation:
object representing the named ppc gateway server
resulted in a bad return code being returned.
System action:
Program terminates.
User response:
Need root authority for this command.
Explanation:
User has insufficient authority to run this command.
System action:
Program terminates.
User response:
Authenticate as root and then retry command.
Destination:
stdout
BHG5906
Unable to find gateway server %1

network object.
Destination:
stdout
Explanation:
User update
BHG5905
BHG5907
Destination:
stdout
BHG5909
Gateway server %1 on host %2 is

correctly set to created state.
Explanation:
User update.
System action:
Program terminates.
User response:
None.
Syntax: \n\n \ bhgvgwystate.sh DSOM

server host -s gwy server[-F]\n \ DSOM
server = alias of the DSOM server
running this command.\n \host = name
of the host machine where this
command will be run.\n \ gwy server =
full name of gateway server whose
state is being queried.\n \ [-F]= optional
force of gateway server object to
correct state.\n
Explanation:
System action:
Destination:
stdout
BHG5910
Gateway server %1 on host %2 is set

to an incorrect state.
Explanation:
The named gateway servers representative object in
the global instance network is set to a state which does
not agree with the true state of the gateway server.
System action:
Program terminates.
User response:
User response:
Retry the command with the -F option to try and correct
the real world / object state mismatch. Contact IBM
Service if unable to identify the problem.
Destination:
stdout
Destination:
stdout
Chapter 2. BHG...
593
BHG5911 BHG5919
BHG5911
Attempting to set gateway server %1 to

created.
BHG5915
Attempting to set gateway server %1 to

up.
Explanation:
User update.
Explanation:
User update.
System action:
None.
System action:
None.
User response:
None.
User response:
None.
Destination:
stdout
Destination:
stdout
BHG5912
Failed to set gateway server %1 on

host %2 to correct state.
Explanation:
The SOM call to set the named gwy servers object
state failed. The object remains in an incorrect state.
System action:
Program terminates.
User response:
Destination:
stdout
BHG5916
Explanation:
User update
System action:
Program terminates.
User response:
None.
Destination:
stdout
BHG5917
BHG5913
Gateway server %1 on host %2 was

correctly set to created.
Explanation:
User update
System action:
Program terminates.
User response:
None.
Destination:
stdout
correctly set to up state.
Explanation:
User update.
System action:
Program terminates.
User response:
None
Destination:
stdout

correctly set to stopped state.
Explanation:
User update.
System action:
Program terminates.
User response:
None.
Destination:
stdout
BHG5918
BHG5914

correctly set to up.
Attempting to set gateway server %1

on host %2 to stopped.
Explanation:
User update.
System action:
None.
User response:
None.
Destination:
stdout
BHG5919

correctly set to stopped.
Explanation:
User update
System action:
594
BHG6000 BHG8501
Program terminates.
BHG6202
User response:
None.
Destination:
stdout
BHG6000
Environment error. User id for CICS SM

is not defined or has uid=0.
Explanation:
An invalid environment has been detected.
System action:
The program should exit
Unable to activate implementation for

alias %1. SOM exception type %2. SOM
error code %3
Explanation:
The specified implementation id could not be activated.
This program is intended to be started by the DSOM
daemon (somdd) only.
System action:
The program exits.
User response:
This could be caused if the product has not been
configured correctly. Contact IBM Service if you are
User response:
The cicssm user id is probably undefined or you have
started a component in an invalid environment. If you
use the cicssm command to start components this will
not occur.
Destination:
stderr
Destination:
stderr /message log
Explanation:
The alias %1 is not intended to be started via the
DSOM daemon.
BHG6200
System action:
The program exits.
No implementation id specified.
Explanation:
An attempt has been made to start the bhgdsrv program
with an invalid parameter. This program is intended to
be started by the DSOM daemon (somdd) only.
System action:
The program exits.
User response:
Contact IBM Service if you did not invoke this program
intentionally
Destination:
stderr
BHG6201
BHG6203
alias %1 can not be started via somdd
User response:
None
Destination:
stderr
BHG6204
somdd process id is %1
Explanation:
Information only
System action:
None
Unable to find implementation id %1 in

implementation repository. SOM
exception type %2. SOM error code
%3.
Explanation:
An attempt has been made to start the bhgdsrv program
specifying an invalid implementation id. This program is
intended to be started by the DSOM daemon (somdd)
only.
System action:
The program exits.
User response:
This could be caused if the product has not been
configured correctly. Contact IBM Service if you are
User response:
None
Destination:
stdout
BHG8501
%2 action requested.
Explanation:
Status update for user.
System action:
Program continues.
User response:
None.
Destination:
stdout
Destination:
stderr
Chapter 2. BHG...
595
BHG8502 BHG8526
BHG8502
Need cicssm authority for %1 %2

action.
Explanation:
User has insufficient authority for a requested action.
System action:
Exit.
System action:
Command fails. Program exits after outputing help info.
User response:
Re-try the command with more information.
Destination:
stdout
User response:
Authenticate as cicssm and then re-try command.
BHG8516
Destination:
stdout
Explanation:
Inform the user that an error occurred during the
processing of the requested cicswlm command.
BHG8504
Invalid invocation
Explanation:
An action has been requested without the correct
number of parameters to ensure that it can be carried
out.
System action:
Command fails. Program exits after outputing help info.
User response:
Re-try the command with more information.
System action:
Exit.
User response:
None.
Destination:
stdout
BHG8523
Destination:
stdout
BHG8510
%1 is not a recognized option.

Command fails.
cicswlm command has failed.
Recognized start syntax:-\n\n \ cicswlm

start wap wap name\n \ cicswlm start
wcm wap name\n \ cicswlm start
routemonitor\n \ cicswlm start
healthmonitor wap name\n \ User needs
cicssm authority for all of the above. \n
Explanation:
Help information for the cicswlm start command.
Explanation:
Invalid parameter entered for a cicswlm action.
System action:
Exit.
System action:
Output help message then exit.
User response:
Read.
User response:
Retry with new data.
Destination:
stdout
Destination:
stdout
BHG8525
BHG8512
cicswlm has completed successfully.
Explanation:
Inform the user that the cicswlm process is exiting.
System action:
Exit.
User response:
None.
Destination:
stdout
BHG8515
Explanation:
Help information for the cicswlm configure command.
System action:
Exit.
User response:
Read.
Destination:
stdout
No process name entered. Command

fails.
Explanation:
An action has been requested on an object without the
necessary object name etc being entered.
596
Recognized configure syntax:-\n\n \

cicswlm configure\n\n \ User must
have cicssm authority for this
command.\n
BHG8526
Recognized list syntax:-\n\n \ cicswlm

list\n
Explanation:
Help information for the cicswlm list command.
BHG8534 BHG8538
System action:
Exit.
stdout
User response:
Read.
BHG8532
Destination:
stdout
BHG8534
WLM Application id file could not be

found - %1
Explanation:
The wap.wap name file could not be located
System action:
Exit.
User response:
Ensure the file is in the location expected
BHG8535
Explanation:
Help information for the cicswlm load command.
System action:
Exit.
User response:
Read.
Destination:
stdout
BHG8533
Destination:
stdout
Recognized load syntax:-\n\n \ cicswlm

load file name wap name \n \ User
needs cicssm authority for this
command.\n
Configuration file not found - %1
Explanation:
The wlm configuration file could not be located
WLM dictionary file could not be found
- %1
System action:
Exit.
Explanation:
The wlm.dict file could not be located
User response:
System action:
Exit.
Destination:
stdout
User response:
BHG8537
Destination:
stdout
BHG8536
Recognized verify syntax:-\n\n \

cicswlm verify file name\n \ User needs
cicssm authority for this command.\n
Explanation:
Help information for the cicswlm verify command.
System action:
Exit.
User response:
Read.
BHG8531
Explanation:
The DISPLAY environment variable is not set and so
the xterm cannot be started.
System action:
Exit.
User response:
Set the DISPLAY environment variable and resubmit the
command.
Destination:
stdout
BHG8538
Destination:
stdout
Non numeric value specified - %1
Explanation:
A numeric parameter was expected
System action:
Exit.
User response:
re-enter the command correctly
DISPLAY environment variable is not

set.\n
xterm or aixterm not found in path.\n
Explanation:
The xterm or aixterm is not defined in path, display
cannot be started.
System action:
Exit.
User response:
Update PATH environment variable and resubmit the
command.
Destination:
stdout
Destination:
Chapter 2. BHG...
597
BHG8539
BHG8539
xterm not found in path.\n
Explanation:
The xterm is not defined in path, display cannot be
started.
System action:
Exit.
User response:
Update PATH environment variable and resubmit the
command.
Destination:
stdout
598

ABMB
Explanation
The user has specified a cursor position in the BMS output request. It is larger than
the current screen size for the 3270 for which output is being built.
System action
The transaction is abnormally terminated with a CICS transaction dump.
User response
Correct the program that specified the incorrect cursor location.
Use trace to identify the statement issuing the request. Check that the cursor
position is being correctly set. The program may have been designed to run in
alternate screen size mode but is being run in default screen size mode, or it may
have been designed to run on a 3270 model different from the one in use. If the
program is routing a message, the route list should be checked. If the program is to
run with various 3270 models, the cursor position should be within the size of the
smallest screen.
ABMI
Explanation
The map specified for a BMS input mapping request was not an input map.
System action
The transaction is abnormally terminated with a CICS transaction dump.
User response
Either define another input map or redefine the existing map.
ABMM
Explanation
The program specified an invalid map.
System action
CICS abnormally terminates the transaction and produces a CICS transaction
dump.
User response
Verify that the mapset has been compiled with a version of cicsmap compatible
with the CICS region. Also, check that the pathname in the program definitions (PD)
points to a valid mapset.
599
ABMO
Explanation
The program specified a map that was not an output map, for a Basic Mapping
Support (BMS) output mapping request.
System action
dump.
User response
Either define another output map or redefine the existing map.
ABM0
Explanation
The program specified a map that CICS could not locate, for a Basic Mapping
Support (BMS) request.
System action
dump.
User response
Check whether the program specified the map correctly, and that the map is
defined.
ABM3
Explanation
A non terminal-oriented transaction issued a Basic Mapping Support (BMS) input or
output request.
System action
dump.
User response
The task issuing a BMS input or output request must be attached to a terminal.
ACS1
Explanation
CICS application server is not able to allocate enough memory in task private pool.
600
System action
The specified transaction terminates.
User response
This indicates a memory allocation failure. You possibly need to increase the size of
the task private pool and restart CICS.
ADPL
Explanation
A server program has issued a command which is restricted in the distributed
program link (DPL) environment. Certain API and CPI-RR requests, and the DL/I
terminate request are not allowed in the list of these restricted commands.
See the TXSeries for Multiplatforms Intercommunication Guide.
System action
CICS abends the transaction with a transaction dump.
User response
Remove the restricted commands from the server program, or run the server
program locally.
AEIA to AEY3
Explanation
CICS detected an exceptional condition for which no EXEC CICS HANDLE
CONDITION command is active and the RESP or NOHANDLE option is not
included in the associated command.
Because of their similar characteristics, these abnormal termination codes for the
EXEC interface program are described as a group. The codes and their
corresponding exceptional conditions are as follows:
601
Code
AEIA
AEID
AEIE
AEIG
AEIH
AEII
AEIJ
AEIK
AEIL
AEIM
AEIN
AEIO
AEIP
AEIQ
AEIR
AEIS
AEIT
AEIU
AEIV
AEIW
AEIZ
AEI0
AEI1
AEI2
AEI3
AEI8
AEI9
Condition
ERROR
EOF
EODS
INBFMH
ENDINPT
NONVAL
NOSTART
TERMIDERR
FILENOTFOUND
NOTFND
DUPREC
DUPKEY
INVREQ
IOERR
NOSPACE
NOTOPEN
ENDFILE
ILLOGIC
LENGERR
QZERO
ITEMERR
PGMIDERR
TRANSIDERR
ENDDATA
INVTSREQ
TSIOERR
MAPFAIL
Code
Condition
AEXL
AEYA
AEYB
AEYC
AEYE
AEYG
AEYH
AEYJ
AEYK
AEYL
AEYM
AEYN
AEYO
AEYP
AEYQ
AEYR
AEYT
AEYU
AEYV
AEYX
AEYY
AEYZ
AEY0
AEY1
AEY2
AEY3
DISABLED
INVERRTERM
INVMPSZ
IGREQID
INVLDC
JIDERR
QIDERR
DSSTAT
SELNERR
FUNCERR
UNEXPIN
NOPASSBKRD
NOPASSBKWR
SEGIDERR
SYSIDERR
ISCINVREQ
ENVDEFERR
IGREQCD
SESSIONERR
USERIDERROR
NOTALLOC
CBIDERR
INVEXITREQ
INVPARTNSET
INVPARTN
PARTNFAIL
System action
dump.
User response
Change the application program either to prevent the condition recurring, to check
the condition using the RESP option, or to handle the condition when it does occur
(by using the EXEC CICS HANDLE CONDITION command). You can use the
EIBRESP2 and EIBRCODE fields in the EXEC Interface Block (EIB) to help you
determine the cause of the exceptional condition.
AEY7
Explanation
A resource security check has failed. A transactions Transaction Definition (TD)
entry has requested resource security checking but this has been unsuccessful for
one of the following reasons:
v The transaction is not a terminal transaction
v The resource security specified in the relevant resource definitions entry is not
matched by the resource security authorization for your user identifier.
System action
dump.
602
User response
If you require access to this resource, ensure that you remove the reason why
access was unsuccessful.
RSLCheck=internal(CICS to perform resource security checks) is the default for
the CICS-supplied transactions; CECI, CEDF, CEBR, CSMI, CSM1, CSM2, CSM3,
and CSM5. If you wish to remove resource security checking for these or any other
transactions, you should define the transaction in the TD, specifying
RSLCheck=none. In the case of CEDF, the resource security checking is applied to
the transaction under test (not to CEDF itself). Specifying RSLCheck=none for the
CEDF transaction prevents the checks being applied to the transaction under test,
unless you specify RSLCheck=internalor RSLCheck=external, explicitly for that
transaction.
AEY9
Explanation
You have named the local region in the SYSID option of a command and the
underlying resource is marked as being remote.
System action
dump.
User response
Correct the transaction so that it does not use the SYSID option, or correct the
resource definition so that it does not point to a remote system.
AICA
Explanation
A task has been executing for longer thatn the MaxTaskCPU time. This abend
indicates a possible loop in the application. See the accompanying ERZ014039E
messages for further information.
System action
The task is terminated with a transaction dump.
User response
Identify the failing task and investigate the possible causes for the excessive CPU
usage.
AIS9
Explanation
The mirror program has detected that a DPL server program has returned in an
invalid state following the completion of the LINK command. The server program or
a program it linked to has initiated a synclevel 2 conversation with another program
603
which in turn has issued a syncpoint. The server program has not responded to the
syncpoint request which is still outstanding when control returns to the mirror
program.
The mirror program only issues this abend code if the LINK request did not specify
SYNCONRETURN TURN.
System action
The task is abnormally terminated with a transaction dump
User response
Correct the design of the DTP application or applications initiated by the server
program. If the SYNCONRETURN option is not specified on the LINK request, only
the client program should initiate the syncpoint. If it is necessary to issue syncpoint
requests from the DTP applications, consider using the SYNCONRETURN option
on the LINK request.
AKCS
Explanation
CICS detected a deadlock timeout condition. This condition may occur within any
transaction defined with a non-zero DeadLockTimeout attribute in the Transaction
Definitions (TD). This condition can also be raised by DB2 when it detects a
deadlock or timeout on its resources. Deadlock timeout occurs when a transaction
waits for longer than the time specified in DeadLockTimeout. (Note: the
DeadLockTimeout attribute is specified in seconds.)
System action
CICS abnormally terminates the transaction but does not produce a transaction
dump.
User response
You should re-run the transaction because the situation causing the transaction to
wait, may well clear itself. If this does not solve the problem, try increasing the
value of the DeadlockTimeout attribute to the maximum acceptable value. If this
does not solve the problem, please read Problem Determination. If SQLCODE -913
is reported in the symrecs file, refer to the relevant DB2 Problem Determination
Guide for further assistance.
AKCT
Explanation
CICS has detected a terminal read-time-out condition. The transaction has been
waiting for a terminal input message for an interval longer than that specified in
Timeout in the Transaction Definitions. (Note: The Timeout attribute is specified in
minutes.)
604
System action
CICS abnormally terminates the transaction but does not produce a transaction
dump.
User response
Check if the Timeout limit is too short.
APCN
Explanation
An attempt was made to release an object that is not correctly loaded.
System action
dump.
User response
Determine why your application issued more deletes than loads for a program, table
or map set.
APCT
Explanation
A requested program entry in the Program Definitions (PD) is disabled, or the
program has zero length, or an I/O error has occurred while loading the program.
System action
dump.
User response
Determine why the PD entry is disabled, or incorrect, or why the program has zero
length. If an I/O error occurred, previous error messages may indicate the source of
the error.
ASRA
Explanation
The task has terminated abnormally because of a signal or exception.
System action
CICS abnormally terminates the transaction and produces a transaction and
possibly a system dump.
605
User response
Determine and correct the cause of the signal or exception.
ASRB
Explanation
The task has terminated abnormally because of an incorrect system call.
System action
CICS abnormally terminates the transaction and produces a transaction and
possibly a system dump
User response
Determine and correct the cause of the incorrect system call.
ATCV
Explanation
An application attempted an operation with an LU6.2 system, but was not in a valid
state to attempt this operation, for one of the following reasons:
v The application is communicating with an LU6.2 system, and is not in the correct
state to perform the attempted operation.
v The application is using function shipping and a SYNCPOINT ROLLBACK was
required but not performed.
This abnormal termination also occurs when CICS cannot communicate with a
terminal.
System action
dump.
User response
Investigate the problem, using either the transaction dump or a debugging aid.
Possible debugging aids include CEDF, Trace, ANIMATOR, and dbx. For
information about transaction dumps, please read Problem Determination. Correct
the transaction and submit it again.
However, if the abnormal termination is due either to the user deliberately closing
his terminal or to some component such as rpcs timing out then check
console.msg. If console.msg indicates the cause, when it is necessary, you
should correct the problem.
ATDD
Explanation
The transaction attempted to access a Transient Data (TD) queue that is disabled.
606
System action
dump.
User response
Check why the queue is disabled. For information about transaction dumps, please
read Problem Determination.
ATNI
Explanation
CICS decides to abnormally terminate the transaction.
This abend occurs when a conversation is abnormally terminated. Conversations
being abnormally terminated may be due to both software and hardware causes. It
is impossible for CICS to know why a conversation was abnormally terminated.
In the case of a tty or cicsteld terminal, if the TERMERR condition is not handled,
this abend is the result of the physical terminal (or window) losing contact with
CICS.
System action
dump.
User response
For investigation of the failure you should first look for logged messages on the
local and the remote systems. Further investigation may be required using the
facilities offered by the other communication components involved.
AZI4
Explanation
An IRC data transmission request has been issued, but cannot be completed
because the other system has become unavailable for interregion communication.
System action
dump.
User response
Rerun the transaction when interregion communication is available.
607
AZI6
Explanation
The transaction was connected to another transaction in another CICS system via
an IRC link. This other transaction has abnormally terminated.
System action
dump.
User response
Correct the cause of the abend in the connected transaction.
A011:
Explanation
An error in a COBOL transaction program caused a COBOL runtime system error to
occur during the execution of the program.
System action
The transaction terminates abnormally.
User response
Look in console.msg for the COBOL runtime system error message. For further
information about the error, look up the error number in the COBOL documentation.
If the error number is 187 (Runtime system not found on $COBDIR path) check that
COBOL is properly installed and that the $COBDIR environment variable is properly
set up for the region. Otherwise correct the error in your COBOL program.
A012:
Explanation
An error in an IBM COBOL transaction program caused an IBM COBOL runtime
system error to occur during the execution of the program.
System action
User response
Look in console.msg for the IBM COBOL runtime system error message. For further
information about the error, look up the error number in the relevant IBM COBOL
documentation.
608
A013:
Explanation
An error in an IBM PL/I transaction program caused an IBM PL/I runtime system
error to occur during the execution of the program.
System action
User response
Look in console.msg for the IBM PL/I runtime system error message. For further
information about the error, look up the error number in the relevant IBM PL/I
documentation.
A014:
Explanation
An unexpected error occurred during initialization of a CICS Java task. This is
possibly a system problem such as a shortage of memory, or an internal error.
System action
User response
Look in console.msg for a Java exception message.
A015:
Explanation
An unexpected exception was generated by a CICS Java program.
System action
User response
There are additional CICS messages in CSMT and a Java exception message in
console.msg. Examine these to determine the cause of the problem and rectify if
possible.
A031:
Explanation
The CICS Command Level Interpreter (CECI) tried unsuccessfully to read user
input from the screen.
609
System action
CECI terminates abnormally.
User response
Check that the cicsterm session in which CECI is running is still active. Check that
the screen is properly connected and configured. Check the symptom records for
any related information.
A032:
Explanation
The CICS Command Level Interpreter (CECI) tried unsuccessfully to obtain Task
Private storage. CECI breached the CICS task private pool storage threshold.
System action
CECI terminates abnormally.
User response
Shut down the CICS region and reconfigure the task private storage pool size
(MaxTaskPrivatePool) attribute in the Region Definitions or by overriding the
Region Definitions on the CICS command line.
A033:
Explanation
An undetermined error has occurred during execution of the CICS Command Level
Interpreter (CECI or CECS). Further information is possibly available in one of the
CICS message files.
System action
CECI or CECS terminates abnormally.
User response
Refer to any associated messages in the CICS message files for further guidance
on resolving the problem.
A07A:
Explanation
A START command is invalid. This is possibly because there was an attempt to
START a CICS-private transaction, or because a transaction was started at an
inappropriate phase of region operation, or on an invalid terminal.
System action
610
User response
Check that the value of the InvocationMode attribute in the Transaction Definitions
of the transaction you want to START is appropriate.
A07B:
Explanation
There is insufficient memory available in the Region Pool to perform an Interval
Control operation
System action
The transaction abnormally terminates
User response
CICS possibly ran out of memory. This can be due to a transaction that is looping in
some way that causes CICS to acquire substantial amounts of Region Pool memory
on its behalf. Check that the value of the MaxRegionPool attribute in the Region
Definitions is sufficiently large. Perform an immediate shutdown of the region,
increase the value, and restart the region.
A07C:
Explanation
The definitions for a transaction that was specified as the trigger transaction for a
temporary data queue indicate that the transaction is to be routed to another
system. This is invalid.
System action
The transaction abnormally terminates
User response
Consider changing the transaction definitions (TD) so the transaction has a blank
RemoteSysId. Alternatively, you can change the transient data definitions (TDD) so
that the TriggeredTransId contains the name of a transaction that is run locally.
A101:
Explanation
CICS has detected an exceptional condition while executing in CICS code.
System action
CICS abnormally terminates the transaction and the application server where the
exception was detected.
611
User response
This abend indicates a CICS internal problem. Save any dump file produced and
A10A:
Explanation
CICS was unable to set up the message catalog. Messages are logged to indicate
the nature of the problem.
System action
User response
Refer to the associated messages for further guidance on resolving the problem. If
A10C:
Explanation
CICS was unable to register as an Application Server. Messages are logged to
indicate the nature of the problem.
System action
User response
A10D:
Explanation
CICS was unable to initialize a process.
System action
User response
612
A10E:
Explanation
An operation failed during an RPC call.
System action
User response
A11A:
Explanation
The terminal autoinstall was unsuccessful.
System action
User response
Examine the CSMT message log for possible causes.
A11B:
Explanation
The terminal installation was unsuccessful because another terminal using the
same netname is already installed.
System action
User response
Install using a different netname, or alternatively autoinstall the terminal by omitting
the netname.
A11D:
Explanation
There is a problem with CICS Task Private storage.
System action
Autoinstall or uninstall terminates abnormally.
613
User response
Retry the operation. If still unsuccessful, stop CICS and try again. Contact your
support organization if the problem persists.
A11F:
Explanation
The terminal installation was unsuccessful because there is no entry in the Terminal
Definitions (WD) for the specified netname.
System action
User response
Install using a different netname, add a WD entry for this netname, or autoinstall the
terminal by omitting the netname.
A11M:
Explanation
CICS is short of Task Private storage, and a storage allocation request for a
terminal operation was unable to be satisfied.
System action
User response
Retry the transaction. If it is still unsuccessful, check that this transaction is not
using a lot of storage. If it is not, check for any other transactions using a lot of
storage.
A11N:
Explanation
An attempt to autoinstall a terminal was unsuccessful because there are no terminal
models defined in the Terminal Definitions (WD) with DevType matching the model
you requested. The model can be requested by setting either the CICSTERM or the
TERM environment variable, or by specifying the -m option on the cicsterm
command.
System action
614
User response
Either add an entry to the WD with DevType matching your requested model, set
CICSTERM to match an existing DevType entry in the WD, or specify -m using an
existing DevType entry in the WD.
A11P:
Explanation
The terminal installation was unsuccessful because the Terminal Definition (WD) for
this netname is not consistent with the installation type. This occurs when you try to
install a printer using a non-printer definition, or when you try to install a terminal
using a printer definition.
System action
User response
Check that the netname used is correct. Check the definition for this netname to
ensure that it defines a printer or a terminal as required.
A11T:
Explanation
The terminal installation was unsuccessful.
System action
User response
A11U:
Explanation
The autoinstall user-exit program was unable to be run or rejected the autoinstall
request.
System action
Autoinstall or uninstall terminates abnormally.
User response
Check that the autoinstall user-exit program exists. It is specified in the Program
Definitions (PD) for the program associated with the CICS private CHAT transaction
in the Transaction Definitions (TD). If you have replaced the autoinstall user-exit
program, investigate why the program rejected the request.
615
A11W:
Explanation
The terminal uninstall was unsuccessful because the Terminal Definitions (WD)
entry for this netname was unable to be updated.
System action
The terminal uninstall terminates abnormally.
User response
A121:
Explanation
An unexpected error occurred during CESN execution.
System action
CESN terminates abnormally.
User response
Check the symptom records and console.msg for any related information.
A122:
Explanation
CESN encountered an error while trying to send some information to, or read input
from, the screen. Your terminal session is possibly unavailable to CICS. Further
information is possibly available in one of the CICS message files.
System action
User response
Check that the terminal session in which CESN is running is still active. Check that
your screen is properly connected and configured. Refer to any associated
messages in the CICS message files for further guidance on resolving the problem.
A124:
Explanation
CESN tried unsuccessfully to obtain a message from the message catalog.
System action
616
User response
Verify that CICS is installed correctly for the locale that you have chosen.
A125:
Explanation
CESN tried to do some work on the terminal on which it was running, but received
an error.
System action
User response
Verify that CICS is installed correctly on your machine. Ensure that the the terminal
on which CESN is running autoinstalled correctly.
A141:
Explanation
CICS detected an unrecoverable error during transaction initialization.
System action
CICS does not start the transaction.
User response
This abend indicates a problem during the initialization of the transaction. Examine
the messages written to CSMT and console.msg to determine the actual problem.
Refer to the documentation associated with the messages for further guidance on
resolving the problem and subsequent action.
A142:
Explanation
CICS detected an exceptional condition while executing in CICS code.
System action
CICS abnormally terminates the transaction and the application server in which the
exception was detected.
User response
This abend indicates a CICS internal problem. Save any dump file produced and
617
A143:
Explanation
CICS was unable to satisfy the task private storage allocation requirements during
transaction initialization.
System action
User response
This abend indicates that CICS was unable to allocate sufficient task private
storage to start the transaction. Examine the messages written to CSMT and
console.msg to determine the actual problem. Refer to the documentation
associated with the messages for further guidance on resolving the problem and
subsequent action.
A144:
Explanation
No initial program was defined for the transaction.
System action
User response
The transaction is not executable because there is no initial program specified in
the ProgName attribute in the transaction definition, because the ProgName
attribute refers to a program for which there is no corresponding program definition,
because the program is disabled, or because the dynamic transaction routing
program returned a null program name. Correct the transaction definition to specify
the name of the initial program, create a program definition entry matching the
program specified by the ProgName attribute, or ensure that the dynamic
transaction routing program returns a program name. Resubmit the transaction
request.
A145:
Explanation
CICS detected an unrecoverable error during transaction initialization within a CRTE
session.
System action
User response
This abend indicates a CICS internal problem during the initialization of a new
transaction to run within the environment created by CRTE. Examine the messages
618
written to CSMT and console.msg to determine the actual problem. Refer to the
documentation associated with the messages for further guidance on resolving the
problem and subsequent action.
A146:
Explanation
One of the authorization checks made at transaction initialization was unsuccessful.
System action
User response
This abend indicates a problem detected by the authorization checks made during
the initialization of the transaction. Examine the messages written to CSMT and
console.msg to determine the actual problem. Refer to the documentation
associated with the messages for further guidance on resolving the problem and
subsequent action.
A147:
Explanation
The transaction was purged.
System action
User response
This abend indicates that the transaction was purged, either via CEMT or as the
result of an immediate region shutdown, or because an exceptional condition was
detected. Resubmit the transaction.
A148:
Explanation
CICS is terminating a transaction and has found that a logical unit of work needs to
be committed. However, the attempt to commit resulted in a syncpoint rollback
because some other participant cannot commit due to a fatal problem.
System action
CICS abnormally terminates the transaction with code A148.
User response
Examine the messages written to CSMT and console.msg to determine the actual
problem. Check that the file server is still running. Correct any other errors and retry
the transaction. Refer to the documentation associated with the messages for
further guidance on resolving the problem and subsequent action.
619
A149:
Explanation
The dynamic transaction routing user exit (UE014025) returned a return code of
UE_Term_Abend.
System action
User response
This abend indicates that your dynamic transaction routing user exit returned a
code of UE_Term_Abend. If the abend was not expected, check your dynamic
transaction routing program to discover why this return code was set.
A150:
Explanation
The dynamic transaction routing user exit (UE014025) was not active when a
dynamic transaction was started.
System action
User response
A dynamic transaction cannot be started while the dynamic transaction routing
program is not active. Refer to the documentation associated with the messages for
further guidance on resolving the problem and subsequent action.
A151:
Explanation
CICS is unable to allocate storage for a COMMAREA from the Task-Private Pool to
be passed to a program during an EXEC CICS XCTL.
System action
CICS abnormally terminates the transaction, but the region continues.
User response
Resubmission of the transaction can possibly work. If not, determine whether or not
the transaction is using excessive amounts of Task-Private Pool (Getmain) storage
and correct this if necessary.
620
A152:
Explanation
CICS is unable to release some Task-Private Pool storage allocated for Program
Control data structures. These data structures hold information about programs
running at each logical level.
System action
CICS abnormally terminates the transaction and the application server in which it
was running.
User response
This problem is unlikely to be caused by application code. If the problem reoccurs,
save any dump file produced and contact your support organization.
A153:
Explanation
CICS is unable to run a program due to lack of space in the Region Pool or
Task-Private Pool for Program Control data structures. These data structures hold
information about programs running at each logical level.
System action
User response
The message logged earlier can be used to determine which storage pool was
empty (ERZ15005 or ERZ1534). If the Region Pool is empty, then because memory
in the Region Pool is continually being acquired and freed by CICS on behalf of
running transactions, resubmission of this transaction can possibly be successful. If
this problem persists when you resubmit the transaction, check whether it is looping
in some way that causes CICS to acquire substantial amounts of Region Pool
memory on its behalf; for example, check the depth of EXEC CICS LINKs in the
program, as Region Pool memory is required for each logical level. Finally, consider
increasing the size of the Region Pool by restarting the region with an override for
the value of the MaxRegionPool attribute in the Region Definition (RD). If the
Task-Private Pool is empty, resubmission of the transaction can possibly work. If
not, determine if the transaction is using excessive amounts of Task-Private Pool
(Getmain) storage and correct this.
A154:
Explanation
CICS is unable to lock a database entry for the definition of a program being run.
This is due to lack of space in the Region Pool.
621
System action
CICS abnormally terminates the transaction and the application server running the
transaction.
User response
Because memory in the Region Pool is continually being acquired and freed by
CICS on behalf of running transactions, resubmission of this transaction can
possibly be successful. If this problem persists when you resubmit the transaction,
check whether it is looping in some way that causes CICS to acquire substantial
amounts of Region Pool memory on its behalf; for example, check the depth of
EXEC CICS LINKs in the program, as Region Pool memory is required for each
logical level. Finally, consider increasing the size of the Region Pool by restarting
the region with an override for the value of the MaxRegionPool attribute in the
A155:
Explanation
CICS is unable to unload a program that was previously loaded by an application
server.
System action
was running.
User response
Check the symptom record file for any operating system-specific failure. The
problem can also be caused by incorrect application code, so check for this in the
transaction that failed.
A156:
Explanation
CICS is unable to allocate storage for a COMMAREA from the Task-Shared Pool to
be passed to another transaction via an EXEC CICS RETURN.
System action
User response
Because memory in the Task-Shared Pool is continually being acquired and freed
by running transactions, resubmission of this transaction can possibly be
successful. If this problem persists when you resubmit the transaction, check
whether any transaction is using large amounts of Task-Shared storage. Finally,
consider increasing the size of the Task-Shared Pool by restarting the region with
an override for the value of the MaxTSHPool attribute in the Region Definition
(RD).
622
A158:
Explanation
An exception is caught while running in CICS code. Possible causes of the
exception are an invalid argument on an EXEC CICS command or a CICS internal
problem.
System action
The transaction and application server running the transaction are abnormally
terminated.
User response
Inspect the symptom record file for symptom records that indicate why the
exception occurred. Investigate the by abend using appropriate debugging tools (for
example, CEDF or Animator). If the exception appears to occur on a particular
EXEC CICS command, and some form of address exception is indicated, carefully
check all arguments specified on the EXEC CICS command and correct the
program if necessary. Otherwise, this is probably a CICS internal problem. Save
any dump file produced. If the problem persists, contact your support organization.
A159:
Explanation
CICS is unable to redirect the debugger I/O to the specified terminal. The given
terminal was unable to be opened as a file.
System action
User response
Look up the error number in errno.h and investigate the cause.
A15A:
Explanation
CICS is unable to load the Micro Focus COBOL for UNIX language support
program cicsprCOBOL. cicsprCOBOL is used to load and run COBOL application
programs.
System action
User response
Investigate the cause of the load failure by using the ERZ015035E error message
logged earlier and the symptom records. Check that the full pathname of
cicsprCOBOL recorded in error message ERZ015035E refers to a valid executable
file that is accessible. If this file does not exist, contact your system administrator,
623
because Micro Focus COBOL for UNIX support is possibly not installed on CICS or
the CICS installation is possibly corrupted. In this last case, the system
administrator can consider reinstalling CICS and Micro Focus COBOL for UNIX
support for CICS. If the problem cannot be solved and persists, contact your
A15F:
Explanation
CICS is unable to find the database record for the principal facility during an EXEC
CICS RETURN TRANSID COMMAREA command.
System action
was running with abend code A15F.
User response
Save any dump file produced. This error is likely to be caused by a CICS
inconsistency rather than by incorrect applications. If the problem reoccurs, contact
A15Z:
Explanation
CICS caught a processing exception for a user exit.
System action
was running with abend code A15Z.
User response
Save any dump file produced. Examine the console for any associated messages
indicating changes in the status of the associated user exit program. Refer to
message ERZ015037E for further actions.
A161:
Explanation
The CICS Transaction Manager component (TRAN) has decided to terminate and
back out a logical unit of work immediately, without waiting for a syncpoint. This
frequently means that some other participant, such as a Structured File Server
(SFS), involved in the transaction had a fatal problem and so there is no point in
continuing the transaction any further.
System action
CICS abnormally terminates the transaction with code A161.
624
User response
Check that all Structured File Servers and all Distributed Transaction Processing
(DTP) clients are still running normally. Restart any components that have failed
and retry the transaction.
A162:
Explanation
CICS is unable to start a new logical unit of work in a particular application server.
A new logical unit of work was obtained from the Transaction Manager, but it was
already abnormally ended before CICS made it ready for use.
System action
See ERZ1649E.
User response
See ERZ1649E.
A163:
Explanation
CICS is unable to acquire Region Pool storage for the data structures needed to
process an active logical unit of work.
System action
See ERZ1609E.
User response
See ERZ1609E.
A164:
Explanation
CICS is unable to start a new logical unit of work. This message is preceded by
another message indicating the reason.
System action
See ERZ1604E.
User response
See ERZ1604E.
625
A165:
Explanation
CICS detected an internal error that prevents a logical unit of work from starting or
continuing.
System action
See ERZ1605E.
User response
See ERZ1605E.
A166:
Explanation
CICS is attempting to syncpoint but cannot complete successfully. This means
either that heuristic damage was detected by the Program to Program
Communication (PPC) component of CICS, or that a CICS internal error occurred.
In either case, additional error messages are produced.
System action
The affected transaction is abnormally terminated with code A166.
User response
See the additional error messages produced for further information. Retry the
transaction and call your support organization if the problem persists.
A16E:
Explanation
CICS is unable to allocate Region Pool storage for the registration of an External
Resource Manager.
System action
See ERZ1648E.
User response
See ERZ1648E.
A16H:
Explanation
CICS has detected heuristic damage affecting the transaction being abnormally
terminated.
626
System action
See ERZ1656W.
User response
See ERZ1656W.
A16Z:
Explanation
CICS is unable to complete the initialization of an application server. This message
is possibly preceded by a warning message describing the problem in more detail.
System action
See ERZ1626E.
User response
See ERZ1626E.
A171:
Explanation
The table holding information about active ABEND, Attention IDentifier (AID), and
condition handlers, in the Region Pool, contains invalid data.
System action
The transaction and the application server in which it is running are both abnormally
terminated, but the CICS region continues.
User response
Because the Action Table is held in the Region Pool it is unlikely that the invalid
data was produced by application code. It is possible that there are further
inconsistencies in the Region Pool, and the CICS self-consistency checking
transaction can detect this. If the transaction produces a dump file, save it for
possible use by your support organization. If the problem persists, contact your
A175:
Explanation
CICS was unable to acquire storage to create a new Action Table from the Region
Pool. This table holds information about active ABEND, Attention IDentifier (AID),
and condition handlers.
System action
627
User response
amounts of Region Pool memory on its behalf; for example check the depth of
EXEC CICS LINKs in the program, as an Action Table is built for each logical level.
Finally, consider increasing the size of the Region Pool by restarting the region with
an override for the value of the MaxRegionPool attribute in the Region Definition
(RD).
A177:
Explanation
The stack of tables holding information regarding active ABEND, Attention IDentifier
(AID), or condition handlers for the program at each logical level contains invalid
data.
System action
User response
Because the Action Tables are held in the Region Pool it is unlikely that the invalid
data was produced by application code. It is possible that there are further
inconsistencies in the Region Pool; and the CICS self-consistency checking
transaction can detect this. If the transaction produces a dump file, save it for
possible use by your support organization. If the problem persists, contact your
A178:
Explanation
During an EXEC CICS HANDLE ABEND PROGRAM command, CICS was unable
to lock a handle abend program database entry due to lack of space in the Region
Pool.
System action
User response
EXEC CICS LINKs in the program, as storage is required for for each logical level.
Finally, consider increasing the size of the Region Pool by restarting the region with
628
an override for the value of the MaxRegionPool attribute in the Region Definition
(RD).
A179:
Explanation
CICS was unable to acquire storage to create a new table for storing AIDs handlers
from the Region Pool. This occurred during an EXEC CICS HANDLE AID
command.
System action
User response
EXEC CICS LINKs in the program, as Region Pool storage is required for each
A17A:
Explanation
CICS was unable to acquire storage to create a new table for storing condition
handlers from the Region Pool. This occurred during either an EXEC CICS
HANDLE CONDITION or EXEC CICS IGNORE CONDITION command.
System action
User response
EXEC CICS LINKs in the program, as Region Pool storage is required for each
629
A17G:
Explanation
This is the abend code used if one of the conditions: QBUSY, NOSTG, NOJBUFSP,
ENQBUSY, SYSBUSY, when raised results in an abnormal termination of a
program.
System action
If there is no abend handler at any active logical level that clears the abend, then
the transaction is abnormally terminated with this abend code. Otherwise the abend
handler is executed and the transaction continues.
User response
Find which EXEC CICS command raised the condition. Then investigate why the
condition is raised. Either stop the condition being raised, or change the program to
handle or ignore the condition.
A17H:
Explanation
This is the abend code used if the condition WRONGSTAT, when raised results in
an abnormal termination of a program (the default action for the condition).
System action
User response
A17I:
Explanation
This is the abend code used if the condition NAMEERROR, when raised results in
System action
630
User response
A17J:
Explanation
This is the abend code used if the condition CCERROR, when raised results in an
abnormal termination of a program (the default action for the condition).
System action
User response
A17K:
Explanation
This is the abend code used if the condition MAPERROR, when raised results in an
System action
User response
A17L:
Explanation
This is the abend code used if the condition NOSPOOL, when raised results in an
System action
631
User response
A17M:
Explanation
This is the abend code used if the condition ROLLEDBACK, when raised results in
System action
User response
A17N:
Explanation
This is the abend code used if the condition END, when raised results in an
System action
User response
A17O:
Explanation
This is the abend code used if the condition ALLOCERR, when raised results in an
System action
632
User response
A17P:
Explanation
This is the abend code used if the condition STRELERR, when raised results in an
System action
User response
A17Q:
Explanation
This is the abend code used if the condition SPOLBUSY, when raised results in an
System action
User response
A17R:
Explanation
This is the abend code used if the condition SPOLERR, when raised results in an
System action
633
User response
A17S:
Explanation
This is the abend code used if the condition NODEIDERR, when raised results in
System action
User response
A17T:
Explanation
This is the abend code used if the condition TCIDERR, when raised results in an
System action
User response
A17U:
Explanation
This is the abend code used if the condition TASKIDERR, when raised results in an
System action
634
User response
A194:
Explanation
An attempt to allocate storage from the Region Pool to contain EDF control
information was unsuccessful.
System action
CICS abnormally terminates the application server and issues message
ERZ019004E. The CICS region continues.
User response
As memory in the Region Pool is continually being acquired and freed by CICS on
behalf of running transactions, this is possibly a transient problem that can occur
when CICS is heavily loaded. Try turning EDF on and then running the transaction
again. If this problem persists when you resubmit the transaction, check whether it
is looping in some way that causes CICS to acquire substantial amounts of Region
Pool memory on its behalf; for example, check the depth of EXEC CICS LINKs in
the program, as Region Pool memory is required for each logical level. Finally,
consider increasing the size of the Region Pool by restarting the region with an
override for the value of the MaxRegionPool attribute in the Region Definition (RD).
A195:
Explanation
An attempt to read an EDF message from the CICS message catalog was
unsuccessful.
System action
CICS abnormally terminates the application server. The CICS region continues.
User response
Check that the CICS catalog file for the region is accessible and has the required
permissions. Refer to the operating system documentation for further information
about the use of catalogs.
A19D:
Explanation
EDF attempted to alter EDF control information in the database entry for the named
terminal but was unable to access the Terminal Definition in the runtime database.
635
System action
User response
Examine the CICS message logs, because CICS possibly logged other messages
that indicate why the attempt to access the runtime database was unsuccessful.
A19E:
Explanation
EDF attempted to alter EDF control information in the database entry for the named
system but was unable to access the System Definition in the runtime database.
System action
User response
Examine the CICS message logs, because CICS possibly logged other messages
that indicate why the attempt to access the runtime database was unsuccessful.
A21M:
Explanation
CICS was attempting to obtain memory for file control information. Insufficient
System action
User response
This is possibly a transient problem that can occur when CICS is heavily loaded.
Resubmit the transaction. If the problem persists, consider reconfiguring the size of
an appropriate memory pool and restarting CICS. Check the message files for a
message regarding which memory pool was full.
A21R:
Explanation
CICS was unable to restore a File Definitions (FD) entry to the region database.
System action
User response
This is an internal CICS error. Contact your support organization.
636
A21S:
Explanation
CICS was unable to find a File Definitions (FD) entry in the region database that is
supposed to exist.
System action
User response
This is an internal CICS error. Contact your support organization.
A221:
Explanation
CICS was unable to obtain access to a Transient Data (TD) queue prior to
performing a read, write, or delete operation on it. CICS was unable to record the
fact that the queue was accessed. This probably indicates an unsuccessful
allocation request from the Region Pool. You can confirm this by searching for other
error messages preceding this one.
System action
User response
Check preceding messages for the cause of the error. If it was caused by an
unsuccessful allocation request from the Region Pool, the size of the Region Pool
can be increased by overriding the MaxRegionPool attribute, on the command line,
and restarting the region.
A222:
Explanation
Logging of recoverable data queue operations requires allocation of storage from
the Region Pool. This attempt was unsuccessful.
System action
User response
the region pool and restart CICS.
637
A223:
Explanation
This can occur when the SET option is used in an EXEC CICS READQ TD call or
when performing a write to an intrapartition TD queue. In the case of a READQ
operation, CICS was unable to allocate a buffer for return of the queue data. When
performing a WRITEQ operation, CICS was unable to allocate a buffer for
formatting the data before passing it to the file server.
System action
User response
This indicates a memory allocation failure. You possibly need increase the size of
the Task-Shared pool and restart CICS.
A226:
Explanation
During transaction syncpoint, CICS was unable to store recovery information about
a Transient Data queue operation in the filesystem.
System action
User response
Check preceding messages for the cause of the error. There is possibly a problem
writing data to the file that contains Transient Data queue records.
A227:
Explanation
For files used to store intrapartition TD queue data, CICS must obtain file handles
when a transaction first operates on a queue. This error arises if CICS cannot
obtain a file handle. See previous messages for details of the file server error.
System action
User response
This can indicate an unsuccessful attempt to aquire Region Pool m emory. You
possibly need to increase the size of the Region Pool and restart CICS.
638
A228:
Explanation
CICS must log all operations on physically recoverable TD queues as they are
performed. CICS generates this error if CICS was unable to write the log data.
CICS possibly did not perform the queue operation correctly, and is possibly unable
to recover the queue.
System action
CICS disables the queue, and terminates the transaction with abend code A228.
User response
Other messages can indicate the nature of the log service error. Check the error
logs and possibly the log server to ensure that its data is correctly formatted.
A229:
Explanation
Invalid attempt to delete an extrapartition Transient Data (TD) queue.
System action
User response
Check the program or the queue definition to ensure that the queue name is
correctly identified and that the queue type is extrapartition.
A22A:
Explanation
CICS was unsuccessful when deleting records from a Transient Data (TD) queue.
System action
CICS terminates the transation with abend code A22A.
User response
the file server to ensure that the file contains correctly formatted data. Previous
error messages can indicate the source of the error.
A22B:
Explanation
CICS was unsuccessful when opening a file server file storing either logical,
physical or non-recoverable Transient Data.
639
System action
CICS terminates the transaction with abend code A22B.
User response
Look at previous messages to see if there is a problem with the file server. If the file
server seems to be working correctly, then you can use file server administration
commands to interrogate the status of the file, and its index. Until the file is
available again you are not able to run any transaction using non-recoverable
TDQs.
A23A:
Explanation
During transaction syncpoint, CICS was unable to store recovery information about
Temporary Storage queue operations in the filesystem.
System action
CICS abnormally terminates the transaction with code A23A.
User response
Check preceding messages for the cause of the error. There is possibly a problem
writing data to the file that contains Recoverable Temporary Storage queue records.
A23E:
Explanation
CICS detected an unexpected return code from CICS file support and was unable
to open a file for auxiliary Temporary Storage queues.
System action
User response
Refer to any file support messages that preceded this message.
A23F:
Explanation
to write to an auxiliary queue.
System action
640
User response
We recommend that you delete the queue, identified by a preceding ERZ2346E
message, from CICS and abnormally terminate any transactions using the queue.
Refer to any file support messages that preceded this abnormal termination.
A23G:
Explanation
to read from an auxiliary queue.
System action
User response
We recommend that you delete the queue, identified by a preceding ERZ023047E
message, from CICS and abnormally terminate any transactions using the queue.
Refer to any file support messages that preceded this message.
A23L:
Explanation
Temporary Storage (TS) was unable to register a Logical Unit of Work for your
transaction
System action
CICS abnormally terminates your transaction.
User response
Refer to any previous message detailing why the registration failed and rerun the
transaction.
A23S:
Explanation
CICS is unable to allocate enough memory from either the Region Pool,
Task-Shared Pool or Task-Private memory. This abend is always preceded by either
an ERZ023090E, ERZ023091E or ERZ023092E message that details the type of
memory that CICS was unsuccessful in obtaining.
System action
User response
As for the preceding ERZ023090E, ERZ023091E or ERZ023092E message.
641
A23T:
Explanation
to delete an auxiliary queue.
System action
User response
We recommend that you abnormally terminate any transactions using the queue,
identified by a preceding ERZ023051E or ERZ023049E message. Refer to any file
support messages that preceded this message.
A241:
Explanation
CICS is unable to create the specified log file.
System action
See ERZ2401E.
User response
See ERZ2401E.
A242:
Explanation
CICS is unable to configure the specified log file.
System action
See ERZ2402E.
User response
See ERZ2402E.
A243:
Explanation
CICS is attempting to obtain exclusive access to a user journals run-time database
record, but is unable to do so because of insufficient memory.
System action
See ERZ2474E.
642
User response
See ERZ2474E.
A245:
Explanation
CICS cannot open the specified log file.
System action
See ERZ2405E.
User response
See ERZ2405E.
A248:
Explanation
CICS is attempting to write to a non-crucial user journal but is unable to do so.
Possible causes include deadlock timeout, insufficient space on the relevant
filesystem and bad destination path specified in the journal definition (JD).
System action
See ERZ2476E.
User response
See ERZ2476E.
A24F:
Explanation
CICS is attempting to save changes made to the specified journals run-time
database record, but is unable to do so.
System action
See ERZ2474E.
User response
See ERZ2474E.
A24M:
Explanation
CICS failed to obtain memory whilst attempting to open a user journal. CICS is
unable to create and insert a TDQ runtime database entry corresponding to the
user journal because there is insufficient memory in the Region Pool.
643
System action
See ERZ2472E.
User response
See ERZ2472E.
A24S:
Explanation
CICS failed to obtain memory for a log record because there is insufficient memory
in the Region Pool. This means that CICS is unable to make the log record
permanent.
System action
See ERZ2462E.
User response
See ERZ2462E.
A25A:
Explanation
CICS and the Structured File Server (SFS) are cooperating in processing the
current transaction. SFS has reported that it has detected a problem that requires
that the transaction be terminated.
System action
CICS terminates the transaction with code A25A. The CICS region continues to
operate, although other operations involving that particular SFS can possibly also
be unsuccessful.
User response
Check that the SFS is still running. Use SFS diagnostic facilities to determine the
cause of the problem. Restart the SFS server if necessary.
A25E:
Explanation
CICS has encountered a problem when attempting to obtain the RBA of a record
that it is inserting to a Structured File Server (SFS) file.
System action
A message detailing the problem is written to the message file. The transaction
terminates with code A25E. CICS does not insert the record.
644
User response
Refer to SFS documentation for information concerning the SFS error code that
was written to the message file.
A25F:
Explanation
CICS was unable to perform an operation on the structured file system, as the
transaction that was being used was asynchronously terminated.
System action
CICS writes a message to CSMT and terminates the transaction.
User response
Something other than CICS has caused the transaction to terminate. If this occurs
persistently, investigate the cause. The most likely culprit is the SFS, but
communications errors can also possibly be the cause. CICS continues to run
normally, however.
A25L:
Explanation
CICS was unsuccessful when attempting to retain a transactional lock on a record.
System action
A message containing the SFS error code is written to the message file and the
transaction abnormally terminates.
User response
Refer to SFS documentation for information concerning the SFS error code.
A25M:
Explanation
CICS was attempting to obtain memory for file control information from the Region
Pool. Insufficient memory was available.
System action
User response
This is possibly a transient problem that can occur when CICS is heavily loaded.
Resubmit the transaction. If the problem persists, consider reconfiguring the size of
the Region Pool and restarting CICS.
645
A261:
Explanation
CEBR tried unsuccessfully to obtain a message from the message catalog.
System action
CEBR terminates abnormally.
User response
A262:
Explanation
CEBR tried unsuccessfully to write to the screen.
System action
User response
Check that the cicsterm session in which CEBR is running is still active. Check that
the screen is properly connected and configured. Check the symptom records and
console.msg for any related information.
A263:
Explanation
CEBR tried unsuccessfully to read user input from the screen.
System action
User response
Check that the cicsterm session in which CEBR is running is still active. Check that
the screen is properly connected and configured. Check the symptom records and
console.msg for any related information.
A264:
Explanation
CEBR tried unsuccessfully to retrieve data passed from the EXEC CICS START
command.
System action
646
User response
A265:
Explanation
CEBR attempted to read a record from a queue and received an unexpected error
returned from the EXEC CICS READQ TS command.
System action
User response
A266:
Explanation
An undetermined error has occurred during CEBR execution.
System action
User response
A27A:
Explanation
A message to be sent to a remote system was unable to be encoded.
System action
User response
Examine the CICS message files for further information on the reason for this error.
If sufficient storage was unable to be allocated for the encoded message, retry the
transaction when the system is more lightly loaded, or simplify your transactions
such that they use less task private storage. If data was unable to be converted
between different code pages, ensure that an operating system conversion is
available between the two code pages. If the conversion is available, and the
647
A27B:
Explanation
A message received from a remote system was unable to be decoded.
System action
User response
If sufficient storage was unable to be allocated for the encoded message, retry the
transaction at a later time, when the system is more lightly loaded, or simplify your
transactions such that they use less task private storage. If data was unable to be
converted between different code pages, ensure that an operating system
conversion is available between the two code pages. If the conversion is available,
and the problem persists, contact your support organization.
A27C:
Explanation
The function shipping mirror transaction was unable to access a resource.
System action
User response
Consider rerunning the transaction at a later time when the system is more lightly
loaded. If the problem persists, contact your support organization.
A27D:
Explanation
A message was received that cannot be understood, or an unexpected
communications verb was received.
System action
User response
Ensure that the remote system is not executing a Distributed Transaction
Processing (DTP) transaction. If it is, modify the transaction and/or its resource
definitions, such that it does not execute as the function shipping mirror transaction,
or does not allocate conversations to the function shipping mirror transaction. If this
is not the case, verify that the remote system, and the connection to it are
functioning normally by performing other intersystem communication functions (such
as transaction routing) to the remote system. If the problem persists, prepare a
648
communications trace showing the data received from the remote system and
A27E:
Explanation
The function shipping mirror transaction has received a DL/I request that cannot be
serviced.
System action
User response
Use the procedures appropriate to the remote system to ensure that it does not
attempt to function ship DL/I requests to CICS. This can including modifying the
remote transaction and/or the remote systems resource definitions.
A27F:
Explanation
Task private storage was unable to be allocated.
System action
User response
Consider simplifying your transactions, such that they use less task private storage
or enlarge the task private storage pool.
A27G:
Explanation
The function shipping mirror transaction has received an error, while executing a
START NOCHECK request.
System action
The mirror transaction abnormally terminates.
User response
Examine the CICS message files, which can provide further information regarding
the nature of the error response code.
649
A27K:
Explanation
Your transaction was using synclevel 1 to process remote function shipped
resources. As a result of the transaction taking a syncpoint, either implicitly or
explicitly, all local resources and synclevel 2 partner systems were committed.
However, an error was detected when the commit message was sent to a synclevel
1 system.
System action
User response
Examine the CICS message files for additional information that can help to
determine why the transaction was rolled back. Use the procedures appropriate to
any remote systems with which the transaction has performed intersystem
communication with to obtain any additional information.
A27L:
Explanation
A remote system issued an EXEC CICS LINK to run a user program local to this
system. A COMMAREA was specified. The function shipping mirror transaction ran
the user program on this system and the program completed. CICS then detected
that the user program had overwritten memory beyond the end of the user
programs COMMAREA.
System action
CICS abnormally terminates the function shipping mirror transaction.
User response
Identify the user program being run using CICS product trace and correct the
programming error that caused the COMMAREA memory overwrite.
A28A:
Explanation
A communications error was detected while communicating with a transaction on
the remote system.
System action
CICS abnormally terminates the transaction. The region continues.
User response
Ensure that the remote system and the connection to it are available. Further
information on the reason for the error can be obtained by examining the CICS
650
message logs and referring to the TXSeries for Multiplatforms Intercommunication

Guide.
A28B:
Explanation
The remote transaction has abnormally terminated.
System action
CICS abnormally terminates the local transaction. The region continues.
User response
Use the procedures that are appropriate for the remote system to determine the
reason for the abnormal termination of the remote transaction.
A28C:
Explanation
The relay transaction was started without a terminal as its principal facility. :p. The
relay transaction is a CICS-private transaction that provides the communication
mechanism between the terminal on the terminal owning region and the transaction
on the application owning region.
System action
User response
Ensure that the transaction is being started from a terminal and not by another
transaction executing ATI commands to start the transaction.
A28D:
Explanation
CICS was unable to encode or decode a message that is to be sent to, or was
received from, a remote system.
System action
User response
Examine the CICS message logs to determine why a message was unable to be
encoded or decoded. If sufficient storage was unable to be allocated, retry the
transaction when the system is more lightly loaded, or simplify your transactions so
that they use less task private storage. Ensure that the remote system is not trying
to start a Distributed Transaction Processing (DTP) transaction.
651
A28E:
Explanation
A transaction has nominated a next transaction to run against a terminal as part of
a pseudo-conversation sequence of transactions, but CICS was unable to start it.
System action
User response
Examine the CICS message logs to determine which transaction was unable to be
started. Then verify that the nominated transaction is defined in the terminal owning
region by examining the transactions Transaction Definition (TD).
A28F:
Explanation
CICS was unable to perform an input or output operation on a terminal.
System action
User response
Examine the CICS message logs and consult the TXSeries for Multiplatforms
Problem Determination Guide to determine why the terminal was unable to be read
from or written to.
A28G:
Explanation
A Terminal Definition (WD) does not exist on the local system, and cannot be
requested from the remote system because it is defined as not shippable.
System action
User response
Confirm that it is desirable for the remote system to ship terminal definitions. If it is,
then set the Terminal Definition in the remote system as shippable. If the remote
system is a version of CICS on Open Systems, you can achieve this by setting the
IsShippable attribute of the WD to yes. If the remote system is not a version of
CICS on Open Systems, consult the appropriate documentation for the system to
determine how to set the Terminal Definition as shippable. :p. If it is not desirable to
ship terminal definitions from the remote system, add a WD for the remote terminal
on the local system.
652
A28H:
Explanation
A Terminal Definition (WD) was unable to be requested from the terminal owning
region, or was unable to be installed in the transaction owning region.
System action
User response
Examine the CICS message logs to determine why the WD entry was unable to be
installed. If the WD was unable to be installed because CICS is short on storage,
retry the transaction later, or increase the size of the task shared and region pools.
If the WD entry was unable to be installed because the WD entry in the terminal
owning region is defined as not shippable, consider defining it as shippable, or
consider installing a WD entry in the transaction owning region.
A28I:
Explanation
The Terminal Definition (WD) entry on the transaction owning region is in use by
another terminal, on another remote system.
System action
User response
Retry the transaction at a later time. If the problem persists, consider trying to make
the terminal name unique within your network of connected systems. This can be
achieved by modifying the user exit program that provides the terminal name. If the
terminal owning region is a version of CICS on Open Systems, this is the
DFHCHATX transaction. Also consider specifying a local WD entry for the remote
terminal, specifying the RemoteName and RemoteSysId attributes.
A28J:
Explanation
The TCTUA cannot be installed in the Terminal Definition (WD).
System action
User response
Consider altering the TCTUALen attribute of the local systems WD for the terminal
and the TCTUA length of the remote terminal definition such that they match. If this
message is displayed in the transaction owning region, also consider deleting the
local terminal definition and allowing the remote region to ship terminal definitions.
653
A28K:
Explanation
Transaction is part of a transaction routing loop.
System action
User response
If you are using CRTE, avoid routing back to the local system from the remote
system. If the remote transaction was itself defined as remote, verify that the
remote system for the transaction is correctly specified. If the remote system is a
version of CICS on Open Systems, you can achieve this by examining the
RemoteSysId attribute of the Transaction Definition (TD) entry. If the remote
system is not a version of CICS on Open Systems, consult the appropriate
documentation for that system.
A28M:
Explanation
An unexpected or unknown communications error has occurred.
System action
User response
Look for the message ERZ028038E in CSMT and follow the instructions associated
with it.
A28N:
Explanation
A dynamic transaction cannot be started on an intermediate system.
System action
User response
Ensure that the local transaction definition does not specify that the transaction is
dynamic. Dynamic transactions can be started only in terminal owning systems.
A28O:
Explanation
CICS is unable to link to the DFHTRUC program. DFHTRUC is required in order to
convert data in a COMMAREA or TCTUA for a transaction routing request. Further
654
information on the function of DFHTRUC can be found in the TXSeries for

System action
User response
Examine the messages written to the console.msg file and CSMT log to determine
why CICS can not link to the DFHTRUC program. Follow the instructions for these
messages.
A30A:
Explanation
Your transaction has executed a syncpoint or syncpoint rollback that was
unsuccessful, either because one or more of your transactions synclevel syncpoint
APPC conversations is in the wrong state, or because heuristic damage was
reported on one of your transactions APPC conversations.
System action
User response
Examine the CICS message files for additional information indicating why your
transaction was abnormally terminated. If a state error is reported on one of your
transactions APPC conversations, examine your transaction to ensure that all of its
synclevel syncpoint conversations are in the appropriate state to execute a
syncpoint or syncpoint rollback. If heuristic damage is reported, use the procedures
appropriate to the remote system to determine why heuristic damage was reported.
The local and remote systems can require manual intervention to synchronize
resources that were either rolled back or committed.
A30B:
Explanation
CICS attempted to allocate task private storage for a message received on an
Intersystems Communication (ISC) link, but was unsuccessful.
System action
The transaction is abended.
User response
Consider rerunning the transaction at a later time when the system is more lightly
loaded. Also consider simplifying your transactions, such that they use less task
private storage.
655
A30C:
Explanation
CICS is unable to execute a CICS-supplied program because the Program
Definition (PD) entry for this program does not exist.
System action
User response
Examine the CICS message files to determine which PD entry cannot be found.
Ensure that a suitable PD entry for the program exists. Then resubmit the
transaction.
A30D:
Explanation
CICS is unable to execute a CICS-supplied program because this program is
defined to be remote. CICS requires that this program is local. For a program to be
local, the RemoteSysId attribute of its Program Definition (PD) entry must either be
set to null () or the local SYSID. The local SYSID is configured in the LocalSysId
attribute of the Region Definition (RD) entry.
System action
User response
Examine the CICS message files to determine which PD entry is defined as remote.
Modify the RemoteSysId attribute of the PD entry for the program such that it
either specifies a null string () or the local SYSID. Then resubmit the transaction.
A30E:
Explanation
The transaction has terminated leaving an outstanding conversation to one or more
remote systems. In order to end the transaction CICS has abnormally terminated
the outstanding conversation(s).
System action
CICS abnormally terminates both the conversation(s) and the transaction.
User response
If this is a distributed transaction processing (DTP) program, alter the program logic
so that all conversations are terminated prior to the program issuing an EXEC CICS
RETURN. The TXSeries for Multiplatforms Intercommunication Guide provides more
information on DTP conversations. If the transaction is not using DTP, refer to any
656
associated messages that were logged for further guidance in resolving this
problem.
A30F:
Explanation
CICS is unable to complete a send or a receive of data for an intersystem request
because of an error in the length fields within the data.
System action
CICS creates a symptom record (symrec) describing the failing command and
User response
Examine the console.msg file and the CSMT log as these can contain messages
that describe the cause of the problem. If you can not solve this problem yourself,
save the message files and the symrecs file and contact your support organization.
A30G:
Explanation
CICS is unable to complete a send or a receive of Process Initialization Parameter
(PIP) data for an intersystem request because of an error in the length fields within
the PIP data.
System action
User response
Examine the console.msg file and the CSMT log as these can contain messages
that describe the cause of the problem. If you cannot solve this problem yourself,
save the message files and the symrecs file and contact your support organization.
A31A:
Explanation
The CRTE transaction was started without a terminal as its principal facility.
System action
User response
Ensure that the transaction is being started from a terminal, and not by another
transaction executing ATI commands that start the transaction.
657
A31B:
Explanation
CICS was unable to perform an input or output operation on a terminal.
System action
User response
Examine the CICS message logs and consult the TXSeries for Multiplatforms
Problem Determination Guide to determine why the terminal was not able to be
read from or written to.
A32A:
Explanation
A CICS-private transaction was unable to attach to a remote system.
System action
The transaction is abnormally terminated. Any ATIs that were to be transmitted to
the remote system and terminal are deleted.
User response
Look for messages ERZ3201E and ERZ3202E on CSMTLOG and follow the
instructions associated with them.
A32B:
Explanation
A CICS-private transaction attempted to send a request to a remote system that is
in the process of quiescing.
System action
User response
Look for message ERZ3210E on CSMTLOG and follow the instructions associated
with it.
A32C:
Explanation
conversation between CICS-private transactions was abnormally terminated. This
can be caused by a network failure or an abnormal termination of the CICS-private
transaction on the remote system.
658
System action
User response
with it.
A32D:
Explanation
There is an inconsistency with a remote system definition or a terminal definition.
System action
The CICS-private transaction is abnormally terminated. Any ATIs that were to be
transmitted to the remote system and terminal are deleted.
User response
Look for messages ERZ3205E, ERZ3214E, ERZ3215E, and ERZ3220E on
CSMTLOG and follow the instructions associated with them.
A32E:
Explanation
An invalid, unknown, or corrupt message was given to the CICS-private transaction
that schedules tasks to a remote system. There are many potential causes of this
problem such as someone attempting to transaction route the CICS-private
transaction or issuing EXEC CICS CONNECT PROCESS for it. These are the
symptoms to be expected if the remote system is incompatible with CICS on Open
Systems.
System action
User response
with it.
A32F:
Explanation
A request was made to schedule a task on a remote terminal; the terminal was not
available on the remote system.
659
System action
User response
with it.
A32G:
Explanation
A request was made to schedule a transaction on a remote terminal; the transaction
was not available on the remote system.
System action
User response
with it.
A32H:
Explanation
A request was made to schedule a transaction on a remote system, but the
schedule failed on the remote system.
System action
User response
Investigate the message logs on the remote system. There are probably messages
indicating the problem on the remote system; follow the actions documented for the
messages on the remote system. Look for message ERZ3203E on CSMTLOG and
follow the instructions associated with it.
A32J:
Explanation
ASCII to EBCDIC translation failed. There is a problem with the national language
support (NLS) environment.
660
System action
User response
with it.
A32K:
Explanation
A request to allocate storage has failed.
System action
The CICS-private transaction is abnormally terminated. Other storage-associated
problems can also occur in this CICS region.
User response
Investigate why there is not sufficient storage. Look for message ERZ3006E on the
logs and follow the instructions associated with it.
A32L:
Explanation
The CICS-private transaction CRSR, which schedules tasks for remote terminals,
was invoked by an invalid method. CICS-private transactions can only ever be
started by CICS.
System action
The CICS-private transaction CRSR is abnormally terminated.
User response
Investigate how the transaction was invoked and ensure that the transaction is not
invoked in this way again. Refer to the error message ERZ3231E (on the
CSMT.log) for more information regarding this error.
A32M:
Explanation
A request to ship an unsupported message type to the partner system was
received.
System action
The request is abnormally terminated.
661
User response
No user action is required.
A331:
Explanation
Although the CICS_EpiStartTran call returned CICS_EPI_NORMAL, the attempt to
schedule the transaction was unsuccessful.
System action
CICS does not run the transaction. The EPI is ready to schedule another
transaction.
User response
Examine the data buffer of the preceding CICS_EPI_EVENT_SEND event. Calling
CICS_EpiGetSysError specifying the TermIndex for the associated terminal returns
further information about the cause of the failure.
A341:
Explanation
An attempt was made to run the CICS-private transaction CURD from a terminal.
System action
User response
Do not run CURD from a terminal.
A342:
Explanation
The CICS-private transaction CURD, used in CICS regions to Resource Definition
Online (RDO) communications, made an unsuccessful attempt to converse with
RDO.
System action
CICS abnormally terminates the CURD transaction.
User response
662
A371:
Explanation
An undetermined error has occurred during CALF execution. Further information is
possibly be available in one of the CICS message files.
System action
CALF terminates abnormally.
User response
A372:
Explanation
CALF has determined that the source and destination files that you specified do not
have the same format. Specifically, the record length of the source file is greater
than the record length of the destination file.
System action
User response
Check to see that the source and destination filenames were entered correctly. Also
ensure that they are defined to be the same format and that the destination record
length, is sufficient to hold the longest source record. If the filenames were wrong,
reinvoke CALF, specifying the correct files. If the definitions for the files were
incorrect you possibly need to redefine the source file to the file server before you
can reinvoke CALF to copy them.
A373:
Explanation
CALF has determined that the length of the records in the source file is less than
the length of the records in the destination file, that you have requested that no
records are to be padded with nulls and that the destination is of fixed length.
System action
User response
You have requested CALF does not pad records with NULLs. Determine whether
you really need PAD set to NO. If not then use the default setting. If you need PAD
set to NO change the record length of the destination file to be the same of that of
the source file.
663
A374:
Explanation
CALF has detected an invalid request response (INVREQ) while it was writing to
the destination file. This is possibly due to insufficient authority on the file or
inconsistencies of key length and key position between the source and destination
files. It is also possibly due to an inconsistent conversion template for a remote
copy. Further information is possibly held in one of the CICS message files.
System action
User response
Check that the key of the source file is of the same length and in the same position
as that of the destination file (in the case of a KSDS file). Check also that the user
has add authority to write to the destination file. In the case of a remote source file,
ensure that the conversion template performs consistent conversion of the key and
the key section of the record.
A375:
Explanation
CALF detected a duplicate record response (DUPREC) while it was writing to the
destination file, but you have specified that duplicate records are not allowed.
System action
User response
The default setting for duplicate records is that they are to be allowed
(DUPREC=YES). You have set this value to NO. Determine whether you really
need DUPREC set to NO. If not then use the default setting. If you need DUPREC
set to NO then ensure the destination file is empty before using the import function.
A376:
Explanation
CALF has encountered an error while trying to read a record from the source file.
Further information is possibly available in one of the CICS message files.
System action
User response
If the source file is remote check that there is a connection to the remote system
where the source file resides. Refer to the CICS message files for more information.
664
A377:
Explanation
CALF has encountered an error while trying to write to the destination file. This is
possibly due to a lack of file space, or perhaps the destination file was closed after
you opened it. Further information is possibly available in one of the CICS message
files.
System action
User response
Check that the destination file is open and enabled and that there is enough space
in the file system to write to it. Check also that you have the necessary permissions
to write to the file. Refer to any associated messages in the CICS message files for
further guidance on resolving the problem.
A378:
Explanation
CALF has encountered an error while trying to send some information to the
screen. This is possibly due to your cicsterm session crashing. Further information
is possibly available in one of the CICS message files.
System action
User response
Check that the cicsterm session in which CALF is running is still active. Check that
your screen is properly connected and configured. Refer to any associated
A379:
Explanation
CALF has encountered a problem trying to read your input from the screen. This is
possibly due to your cicsterm session being unavailable to CICS. Further
System action
User response
Check that the cicsterm session in which CALF is running is still active. Check that
the screen is properly connected and configured. Refer to any associated
665
A37A:
Explanation
CALF tried unsuccessfully to obtain a message from the message catalog. This can
happen if your NLSPATH is set incorrectly or if your locale is wrong.
System action
User response
A37B:
Explanation
CALF encountered a problem while trying to inquire on either the source or the
destination file. This is possibly because the file is not present in the CICS runtime
database, or because you are not authorized to read the file. Further information is
System action
User response
Verify that both the source and the destination files are present and defined in the
FD stanza. Check also that you are authorized to read the file. Refer to any
associated messages in the CICS message files for further guidance on resolving
the problem.
A37C:
Explanation
CALF tried unsuccessfully to request a SYNCPOINT while it wrote to the
destination file. Further information is possibly available in one of the CICS
message files.
System action
User response
The system on which you are running CALF is unable to commit the syncpoint.
666
A37D:
Explanation
CALF tried to schedule the use of the destination file (by using ENQ) but
encountered an error. This is possibly because the destination file was in use at the
time CALF issued its request. Further information is possibly available in one of the
CICS message files.
System action
User response
It is possible that the source file was being written to at the time CALF tried to
schedule its use. Make sure nobody else is using your source file, then try the
operation again. If the problem persists refer to any associated messages in the
CICS message files for further guidance on resolving the problem.
A41A:
Explanation
System action
See ERZ4114E.
User response
See ERZ4114E.
A42A:
Explanation
A request to allocate storage from the Task Private Pool was unsuccessful.
System action
User response
Retry the operation. If it is still unsuccessful, this is possibly because another
transaction is using a large amount of Task-Private (GETMAIN) storage. Refer to
any previous messages in the CSMT log and console.msg files that possibly
indicate why Task-Private storage was unable to be allocated.
If the problem persists, increase the size of the Task Private Pool by changing the
value of the MaxTaskPrivatePool attribute in your regions Region Definition (RD)
entry and restart CICS.
667
A42B:
Explanation
The CTIN transaction was invoked incorrectly or the data received from the CICS
Client was invalid. The CTIN transaction must be issued only by a CICS Client to
install or uninstall a client terminal. It is not a general purpose transaction.
System action
CICS abnormally terminates the CTIN transaction. The install or uninstall request is
not performed.
User response
If this abend continues to occur when issued by a CICS Client, contact your support
organization.
A42C:
Explanation
A request to uninstall (delete) a Terminal Definitions (WD) entry for a CICS Client
terminal was unsuccessful. The uninstall request was possibly scheduled by CICS
because the network went down, or it was possibly scheduled by a CICS Client
when closing down the terminal session. The reason why the uninstall request was
unsuccessful is logged in a CSMT message.
System action
CICS abnormally terminates the CTIN transaction. The uninstall request is not
performed.
User response
Check the CSMT log to see why the uninstall abnormally terminated. If this occurs
repeatedly, ask the System Administrator to delete the WD entry from the region
database. If unwanted WD entries remain installed, further installs take longer to
perform and degrade performance.
A42D:
Explanation
The CTIN transaction was invoked correctly, but the network connection was lost
before the CICS Client terminal request completed.
System action
CICS abnormally terminates the CTIN transaction. The install or uninstall request is
not performed.
668
User response
Retry the CICS Client terminal operation. Refer to any previous messages in the
console.msg file and CSMT log that indicate why the network connection went
down.
A42E:
Explanation
A Communications Definition (CD) entry autoinstall request abnormally terminated.
v The autoinstall program, DFHCCINX, vetoed the autoinstall request.
v DFHCCINX requested a SYSID that matches an existing entry in either the
Communications Definition (CD) or Terminal Definitions (WD).
v CICS was unable to interpret the autoinstall data received from the remote
system.
System action
CICS logs error messages to CSMT and abnormally terminates the CCIN
transaction.
User response
Check the CSMT log and console.msg file for further messages that explain why
the autoinstall request was unsuccessful, and then follow the instructions for these
messages.
A42F:
Explanation
A Communications Definition (CD) entry uninstall (delete) request was unsuccessful.
System action
CICS logs error messages to the CSMT log and abnormally terminates the CCIN
transaction.
User response
Check the CSMT log and console.msg file for further messages that explain why
the uninstall request was unsuccessful, and then follow the instructions for these
messages.
A42G:
Explanation
The Communications Definition (CD) entry install or uninstall (delete) request was
unsuccessful due to a communication error on the connection with the remote
system.
669
System action
CICS logs a message indicating the type of communications error, creates a
symptom record (symrec), and abnormally terminates the CCIN transaction.
User response
Retry the operation. If the problem persists and the remote system remains running,
check that the communications protocol being used is set up correctly for the two
systems.
A42H:
Explanation
The CCIN transaction was invoked incorrectly. This transaction must be started only
by a remote CICS system or a CICS Client to autoinstall or delete Communications
Definitions (CD) entries. It is not a general purpose transaction.
System action
CICS creates a symptom record (symrec) and abnormally terminates the CCIN
transaction.
User response
No further action is required.
A42I:
Explanation
The CCIN transaction cannot interpret the data received from a remote system.
v The remote system is not compatible with the local region.
v The remote system is not a CICS region or a CICS Client.
v A user-written application running in the remote system has requested a
Distributed Transaction Processing (DTP) conversation with CCIN.
A symptom record (symrec) is created that contains the SYSID that CCIN was
scheduled against. If this is the local SYSID configured in Region Definition (RD)
attribute LocalSysId, the request was received from a remote system that is not
recognized by CICS. In this case the remote system is either a CICS Client or it is
a CICS region connecting over a CICS family TCP/IP connection. If the SYSID is
not the local SYSID, it is the name of the Communications Definition (CD) entry for
the remote system.
System action
CICS creates a symptom record and abnormally terminates the CCIN transaction.
User response
Identify the remote system using the SYSID from the symptom record or error
messages logged in connecting systems. If the remote system is a CICS Client,
alter the software or configuration used in the CICS Client so it is compatible with
670
your region. If the remote system is a CICS region, look for applications in this
remote system that are requesting a DTP conversation with CCIN.
A42J:
Explanation
CICS is unable to interpret the data received from a remote system because there
is a problem with the data conversion routines for conversion between the United
States (US) ASCII and EBCDIC code pages.
System action
CICS creates a symptom record (symrec) and abnormally terminates the CCIN
transaction.
User response
Examine the symptom record to determine the exact nature of the problem, then
use the information on National Language Support (NLS) supplied with the
operating system to correct the problem.
A42K:
Explanation
The CCIN transaction is unable to complete an install or an uninstall (delete) of a
Communications Definition (CD) entry because of an error in the region database.
System action
abnormally terminates the CCIN transaction.
User response
Examine the console.msg file and the CSMT log, as these possibly contain
messages that describe the cause of the problem. If you cannot solve this problem
yourself, save the message files and the symrec file and contact your support
organization.
A43A:
Explanation
CICS tried to allocate Task Private storage for intersystems communication, but was
unsuccessful.
System action
User response
Retry the transaction at a later time when the system is more lightly loaded, change
your transactions so that they use less task private storage, or increase the size of
671
the Task Private storage and warm start the region.
A43B:
Explanation
An error was detected during communications that requires the currently running
transaction to be terminated abnormally.
System action
CICS abnormally terminates the transaction. Message ERZ4304E is logged.
User response
Check the error message for the error reported by the communications protocol and
take appropriate action.
A43C:
Explanation
An inconsistency was detected in an internal CICS operation.
System action
User response
Retry the failed operation. If the condition persists, use CEMT PERFORM SNAP to
produce a system dump and contact your support organization.
A43D:
Explanation
An error was detected during communications that requires the currently running
transaction to be terminated abnormally.
System action
CICS abnormally terminates the transaction. Message ERZ043007E is logged.
User response
Check the error message for the nature of the problem and take appropriate action.
A43E:
Explanation
An asynchronous backout occurred during intersystems communication that
requires the currently running transaction to be terminated abnormally.
672
System action
CICS abnormally terminates the transaction. Message ERZ4308W is logged.
User response
Check the error message and any previous messages for the cause of the
asynchronous backout and take appropriate action.
A451:
Explanation
The user-defined External Security Manager (ESM) raised an unexpected error
condition when executing a Transaction Security Level (TSL) check on a
transaction.
System action
User response
Check the documentation and source code of the ESM to ascertain why an
unexpected error code was raised.
A452:
Explanation
The user-defined External Security Manager (ESM) raised an unexpected error
condition when executing a Resource Security Level (RSL) check in a transaction.
System action
User response
Check the documentation and source code of the ESM to ascertain why an
unexpected error code was raised.
A453:
Explanation
An update to a resource definition was unable to be completed.
System action
User response
This is an indication of a software problem in CICS. Contact your support
organization.
673
A460:
Explanation
CEMT has detected an error with your CICS region. Further information is possibly
available in one of the CICS message files.
System action
CEMT terminates abnormally.
User response
A461:
Explanation
CEMT tried unsuccessfully to obtain a message from the message catalog.
System action
User response
A462:
Explanation
CEMT is unable to create a panel for display on the screen.
System action
User response
Verify that CICS is installed correctly. Check the symptom records and console.msg
for any related information.
A463:
Explanation
CEMT is unable to create a map for display on the screen.
System action
674
User response
A464:
Explanation
CEMT is unable to create a field for display on the screen.
System action
User response
A465:
Explanation
CEMT is unable to write to a field for display on the screen.
System action
User response
A466:
Explanation
CEMT is unable to display a panel on the screen.
System action
User response
Check that the cicsterm session in which CEMT is running is still active. Check
that the screen is properly connected and configured. Check the symptom records
and console.msg for any related information.
A467:
Explanation
CEMT is unable to read from a field displayed on the screen.
675
System action
User response
A468:
Explanation
CEMT is unable to allocate a task table from region memory.
System action
User response
Ensure that the region is configured correctly and that enough memory is made
available. CEMT uses memory from a task private pool. Check the value of
MaxTaskPrivatePool in the region definitions; you can increase the size of task
private pool given to transactions by adjusting this attribute. Check the symptom
records and console.msg for related information.
A469:
Explanation
CEMT is unable to access its private error Temporary Storage Queue (TSQ).
System action
User response
Verify that the file server is configured correctly and is active for the region to which
CEMT was connected. Check the symptom records and console.msg for related
information. Restart CEMT. If the file server is inoperative, CEMT reverts to using
main TSQs instead of auxiliary TSQs.
A46A:
Explanation
CEMT is unable to read its private screen Temporary Storage Queue (TSQ).
System action
676
User response
information. Ensure that you have security access to CEMT TSQs. Adjust resource
definitions as necessary. Restart CEMT. If the file server is inoperative, CEMT
reverts to using main TSQs instead of auxiliary TSQs.
A46B:
Explanation
CEMT is unable to write to its private screen Temporary Storage Queue (TSQ).
System action
User response
information. Restart CEMT. If the file server is inoperative, CEMT reverts to using
main TSQs instead of auxiliary TSQs.
A46C:
Explanation
CEMT is unable to initialize the CICS internal command analyzer.
System action
User response
Verify that CICS is installed correctly and that the region to which CEMT was
attached is still active. Check the symptom records and console.msg for any related
information.
A46D:
Explanation
CICS is unable to syncpoint the CEMT transaction.
System action
User response
Check that the region to which CEMT was connected is still active. Check the
symptom records and console.msg for any related information.
677
A46E:
Explanation
CEMT is unable to write to its private screen Temporary Storage Queue (TSQ), as
there is insufficient Task Shared Pool Storage.
System action
CEMT is restarted using Auxiliary Temporary Storage.
User response
Ensure that the region is configured correctly and that enough memory is made
available. Check the value of MaxTSHPool in the region definitions; you can
increase the size of task shared pool by adjusting this attribute. Check the symptom
records and console.msg for related information.
A46F:
Explanation
CEMT is unable to write to Auxiliary Temporary Storage because the file which
contains the queues has no space available.
System action
User response
There are possibly associated messages in the console.log or CSMT.out files
detailing the file server error. CEMT uses Auxiliary Temporary Storage only if there
is insufficient Task Shared Pool Storage in the region for it to use Main Temporary
Storage. Check that the region is configured correctly (refer to abend A46E).
A47A:
Explanation
A transaction calls GETMAIN with a LENGTH or FLENGTH value of 0.
System action
A user abnormal termination handler is invoked if defined by the transaction
program. If no abnormal termination handler is defined then CICS abnormally
terminates the transaction.
User response
Check the programs associated with the transaction for the use of the GETMAIN
call. Ensure that the values passed in the LENGTH or FLENGTH options are
greater than zero.
678
A47B:
Explanation
A transaction calls FREEMAIN with the DATA option set to an invalid address.
System action
User response
Check the programs associated with the transaction for the use of the FREEMAIN
call. Ensure that the address value passed in the DATA option is one that has been
previously returned from a GETMAIN call and that the value was not already
processed by a previous FREEMAIN call. Produce a transaction dump and use it to
investigate this problem. Check CSMT and console.msg for any messages that can
be used to investigate the problem along with the transaction dump.
A47C:
Explanation
CICS detects a storage inconsistency. CICS uses a signature string placed at the
end of an allocated block of task-private storage. If this signature string is not in
place when the storage area is passed to a FREEMAIN call, this indicates that the
storage area was overrun during the transactions execution.
System action
terminates the transaction. A transaction dump is produced if this is indicated by the
User response
Produce a transaction dump and use it to investigate this problem. Check CSMT
and console.msg for any messages that can be used to investigate the problem
along with the transaction dump.
A47D:
Explanation
CICS returns an unexpected error while allocating or deallocating a control block
associated with a task-private storage call (GETMAIN or FREEMAIN). This
abnormal condition indicates a software problem in CICS.
System action
679
User response
Retry transaction to see if the condition has cleared. If the condition persists contact
A48A:
Explanation
A transaction was timed out waiting for task shared storage to become available.
System action
User response
Retry the transaction. If this is a persistent problem, check the size of the task
shared pool defined in the Region Definitions. If it is not large enough for the needs
of your region, then reconfigure the size of the task shared pool in the Region
Definitions or by CICS command line parameters at startup.
A48B:
Explanation
An unexpected error is returned from storage control.
System action
User response
This is indicative of a software problem in CICS. Contact your support organization.
A48C:
Explanation
CICS did not complete a LOAD PROGRAM, SEND MAP, or RECEIVE MAP call
because it was unable to load the map or table image into shared storage. This
occurred because of an input/output error reading the map or table image from disk
storage.
System action
terminates the transaction. A transaction dump is produced if this is indicated by the
680
User response
Retry the transaction. Check that the map or table to be loaded exists in the disk
directory indicated in the Program Definitions. If this error persists there is possibly
a problem with a disk drive; contact your support organization.
A49B:
Explanation
CICS has detected an inconsistency in its internal data structures while processing
a command to either start or stop user trace.
System action
User response
It is possible that CICS internal data structures were overwritten by a defective
application program. Retry the transaction. If the problem persists, contact your
A50B:
Explanation
CICS is unable to release monitoring record storage during initialization of the Task
Control Area (TCA) due to a data inconsistency in the Task-Private Pool. Further
messages can be found in the message log and give more information about the
problem.
System action
CICS abnormally terminates the task.
User response
It is likely that the transaction has caused a data inconsistency in the Task-Private
Pool storage. Check the User Event Monitoring Point (EMP) and, if necessary,
correct the User Event Monitoring Point (EMP) function. In order to use the
replacement ULM, you need to restart the region.
A50C:
Explanation
CICS is unable to release monitoring record storage during task termination due to
data inconsistency. Further messages can be found in the message log and give
more information about the problem.
System action
CICS abnormally terminates the task.
681
User response
It is likely that the transaction has caused a data inconsistency in the Task-Private
Pool storage. Check the User Event Monitoring Point (EMP) and, if necessary,
correct the User Event Monitoring Point (EMP) function. In order to use the
replacement ULM, you need to restart the region.
A53A:
Explanation
CICS was unable to process your request to collect statistics, due to an error while
collecting the statistics. Logged messages indicate the nature of the problem.
System action
User response
A561:
Explanation
CICS was unable to allocate storage to perform a wait on a condition.
System action
CICS abnormally terminates the process.
User response
A57A:
Explanation
CICS detected an unsuccessful condition.
System action
If the condition is detected in an Application Server process, then CICS abnormally
terminates the process and any transaction running in that process. If the process is
not an Application Server then the region terminates. If you are running a CICS
utility program, then the utility is halted.
User response
Investigate the circumstances in which the error occurred. Refer to the associated
messages for further guidance on resolving the problem. If the problem persists,
682
A583:
Explanation
A program has exited with the Micro Focus COBOL run-time system (RTS) in an
unknown state, and possibly also with an incomplete logical unit of work. This can
happen when using the Micro Focus COBOL ANIMATOR debugger, for example, or
when the Micro Focus COBOL RTS returns an error.
System action
CICS abnormally terminates the application server to back out any incomplete
logical unit of work, and to terminate the Micro Focus COBOL RTS for that
application server. Further messages are logged if a logical unit of work is backed
out. This avoids leaving the Micro Focus COBOL RTS in an unknown state, which
can prevent successful execution of subsequent COBOL programs.
User response
Depending on the transaction involved it is possibly acceptable to do nothing, such
as when using ANIMATOR, or it is possibly necessary to correct and resubmit the
transaction.
A61A:
Explanation
CICS is unable to register a function to be called at a syncpoint.
System action
CICS terminates the transaction abnormally.
User response
Examine surrounding messages for further help in the reasons for and the method
of avoiding this problem.
A62C:
Explanation
CICS attempted to perform a Basic Mapping Support (BMS) operation on a terminal
that does not support BMS operations.
System action
User response
Run the transaction on a terminal that does support BMS operations.
683
A62F:
Explanation
CICS cannot allocate memory for a terminal operation in one of the Task Private or
the Task Shared Pools.
System action
User response
Retry the transaction. If the condition occurs again, it is possibly due to heavy load
on CICS or because some transaction is using a large amount of memory.
A62G:
Explanation
CICS cannot update the Terminal Definitions (WD).
System action
User response
Any CICS internal data structure inconsistencies are unlikely to be caused by
application code, because they are held in the Region Pool. Save any dump file
A62H:
Explanation
CICS is unable to register a function to be called at a syncpoint
System action
User response
Examine surrounding messages for further information about this problem.
A62J:
Explanation
CICS cannot convert a data in Case=Mixed field in a BMS map to uppercase.
System action
684
User response
Correct the data that the transaction was trying to convert.
A64A:
Explanation
Either the ECI mirror transaction definition or the model terminal definition used for
the autoinstalled ECI terminal session has the UCTranFlag attribute set to yes.
System action
The ECI mirror transaction is abnormally terminated.
User response
Use RDO to redefine the offending transaction or model terminal definition to have
the UCTranflag attribute set to no. Uppercase translation must not be set because
the ECI protocols send data encoded within the 3270 data stream. If uppercase
translation is set on, the ECI data is corrupted and interpreted incorrectly.
A64B:
Explanation
The ECI mirror transaction received an error when reading or writing data to an ECI
application.
System action
User response
This abend can occur if the ECI application is prematurely terminated, for example
if the ECI request timed out or the interrupt key is entered at a terminal executing
the ECI application, or if the ECI mirror transaction is invoked directly at a CICS
terminal.
A64C:
Explanation
The ECI mirror transaction was invoked incorrectly or the data received from the
ECI application was invalid.
System action
User response
This abend can occur if the ECI mirror transaction is invoked directly at a CICS
terminal. If the abend occurs when running an ECI application, contact your support
organization.
685
A64D:
Explanation
CICS is short of Task-Private storage, and a storage allocation request for a ECI
operation was unable to be satisfied.
System action
User response
Retry the operation. If it is still unsuccessful, this is possibly because another
transaction is using a lot of Task-Private Pool (GETMAIN) storage. Refer to any
previous messages in the CSMT and console.msg files that indicate why
Task-Private storage was unable to be allocated.
A64E:
Explanation
An ECI application requested a syncpoint operation, but the syncpoint was
unsuccessful.
System action
Any recoverable resources used by the ECI mirror transaction are rolled back and
the transaction is abnormally terminated.
User response
Check the CSMT and console.msg files to see why the syncpoint operation failed.
For example, the ECI program was possibly requesting resources on a remote
CICS system, or using DTP, and the communications link to the remote system
failed. Ensure that the required resources are available before retrying the ECI
request.
A661:
Explanation
CICS was unable to release Region Pool memory, used during an attempt to
access the runtime database, while performing a SET command.
System action
User response
There is a serious problem with your region. Restart the region at the earliest
opportunity.
686
A691:
Explanation
System action
User response
opportunity.
A701:
Explanation
System action
User response
opportunity.
A711:
Explanation
System action
User response
opportunity.
A731:
Explanation
687
System action
User response
opportunity.
A741:
Explanation
It was not possible to read the region record from the runtime database during an
INQUIRE SYSTEM command.
System action
User response
opportunity.
A751:
Explanation
System action
User response
There is a serious problem with your region. Restart at the earliest opportunity.
A752:
Explanation
CICS was unable to allocate Region Pool memory for the runtime database while
performing a SET or INQUIRE command.
System action
User response
You can increase the size of the Region Pool available by restarting the region and
overriding the MaxRegionPool attribute, with a larger value, on the command line.
688
A761:
Explanation
System action
User response
opportunity.
A771:
Explanation
System action
User response
opportunity.
A82C:
Explanation
CICS was attempting to start a new browse or perform a new read-update but
Application Server SQL resources are exhausted.
System action
User response
Refer to CICS documentation that describes the limitations on the number of
concurrent browses and read-updates when mapping File Control to SQL. A system
limit has been breached, and the application requires reworking.
A82E:
Explanation
CICS encountered a problem when attempting to obtain the maximum current RBA
of an ESDS file.
689
System action
A message detailing the problem is written to the message file. The transaction
terminates with code A82E.
User response
Refer to DB2 or Oracle documentation, as appropriate, for information concerning
the database error code.
A82L:
Explanation
CICS was unsuccessful when attempting to retain a lock on a record.
System action
A message containing the database error code is written to the message file, and
the transaction terminates abnormally.
User response
Refer to DB2 or Oracle documentation, as appropriate, for information concerning
the database error code.
A82M:
Explanation
CICS was attempting to obtain memory for file control information from the Region
Pool. Insufficient memory was available.
System action
User response
This is possibly a transitory problem that can occur when CICS is heavily loaded.
Resubmit the transaction. If the problem persists, you possibly need to reconfigure
the size of the Region Pool and restart CICS.
AA41:
Explanation
CDCN/CADB encountered a problem trying to read BMS input from the screen.
This is possibly due to your cicsterm session being unavailable to CICS. Further
System action
CDCN/CADB terminates abnormally.
690
User response
Check that the cicsterm session in which CDCN/CADB is running is still active.
Check that the screen is properly connected and configured. Refer to any
associated messages in the CICS symptom records and console.msg files for
AA42:
Explanation
CDCN/CADB encountered an error while trying to send some BMS output to the
screen. This is possibly due to your cicsterm session being unavailable to CICS.
Further information is possibly be available in one of the CICS message files.
System action
User response
AA43:
Explanation
CDCN/CADB tried unsuccessfully to receive any options specified when
CDCN/CADB was invoked. This is possibly due to your cicsterm session being
unavailable to CICS. Further information is possibly available in one of the CICS
message files.
System action
User response
AA44:
Explanation
CDCN/CADB encountered an error while trying to obtain information about the
current terminal from the region database. Further information is possibly available
in one of the CICS message files.
691
System action
User response
Ensure that the terminal definition is installed correctly in the region database. Refer
to any associated messages in the CICS symptom records and console.msg files
for further guidance on resolving the problem.
AA45:
Explanation
CDCN/CADB tried unsuccessfully to obtain a message from the message catalog.
This can happen if your NLSPATH is set incorrectly or if your locale is wrong.
System action
User response
AA46:
Explanation
An undetermined error occurred at the start of CDCN/CADB execution. Further
System action
User response
Refer to any associated messages in the CICS symptom records and console.msg
files for further guidance on resolving the problem.
AA47:
Explanation
An attempt was made to start CDCN/CADB other than directly from a local terminal,
but CDCN/CADB can be invoked only directly from a terminal that is local to the
CICS region.
System action
692
User response
Invoke CDCN/CADB directly from a cicsterm that is on the same system as the
CICS region.
AA48:
Explanation
CDCN encountered an error while trying to send some text output to the screen.
This is possibly due to your cicsterm session being unavailable to CICS. Further
System action
CDCN terminates abnormally.
User response
Check that the cicsterm session in which CDCN is running is still active. Check
that the screen is properly connected and configured. Refer to any associated
messages in the CICS symptom records and console.msg files for further guidance
AA49:
Explanation
The debugging support runtime code tried unsuccessfully to obtain a message from
the message catalog. This can happen if your NLSPATH is set incorrectly or if your
locale is wrong.
System action
The CDCN transaction terminates abnormally.
User response
AA4A:
Explanation
The debugging support runtime code encountered an error while trying to send
some text output to the screen. This is possibly due to your cicsterm session being
unavailable to CICS. Further information is possibly available in one of the CICS
message files.
System action
CDCN terminates abnormally.
693
User response
Check that the cicsterm session in which CDCN is running is still active. Check
that the screen is properly connected and configured. Refer to any associated
messages in the CICS symptom records and console.msg files for further guidance
AA4B:
Explanation
The debugging support runtime code encountered an error while trying to allocate
memory for the transaction.
System action
CADB terminates abnormally.
User response
files and contact your support representative for further guidance.
AA4C:
Explanation
The CADB Key specified as a parameter is too long.
System action
User response
files.Please check documentation for the right length for a Key. Rerun CADB with
the right Key as parameter.
AA4D:
Explanation
The CADB Key is invalid.
System action
User response
files.Please check documentation for any rules associated with the Key and rerun
the CADB transaction .
694
AA4E:
Explanation
The CADB transaction failed to configure debugging data.
System action
User response
files. This could have been caused either by user error or some internal CICS error
to manage the debug data. Please check the documentation for CADB and retry.
AB31:
Explanation
An exception was raised in a CICS Java Application that was caught by the
application and was incorrectly not rethrown. The exception indicates an internal
error that cannot be handled by the application. Further information is unavailable
while the application does not rethrow the exception.
System action
User response
Examine your application and correct it to rethrow all CicsError exceptions. Then
rerun the transaction to obtain further information on the internal error. This now
results in a different abend with additional information.
AB40:
Explanation
IIOP request abended.
System action
IIOP request terminates.
User response
Check console.msg for further messages and correct the error before rerunning the
IIOP request.
AB41:
Explanation
Internal class table corrupted.
695
System action
See ERZ114008E.
User response
See ERZ114008E.
AB42:
Explanation
Java generic factory missing.
System action
See ERZ114009E.
User response
See ERZ114009E.
AB43:
Explanation
IIOP support abended.
System action
See ERZ114030E.
User response
See ERZ114030E.
AB44:
Explanation
An assert was detected in the IOM component of the ORB.
System action
See ERZ114033E.
User response
See ERZ114033E.
AB45:
Explanation
Error in class update transaction.
696
System action
Class update transaction terminates.
User response
Check console.msg for further messages and correct the error before rerunning the
class update transaction.
AB52:
Explanation
CICS detected an invalid region configuration.
System action
See ERZ115033E or ERZ115034E as appropriate.
User response
See ERZ115033E or ERZ115034E as appropriate.
AB53:
Explanation
CICS detected that this is a terminal attached mirror transaction.
System action
See ERZ115023E.
User response
See ERZ115023E.
AB54:
Explanation
CICS mirror failed to read request data.
System action
See ERZ115024E.
User response
See ERZ115024E.
AB55:
Explanation
CICS mirror failed to register COMMIT/ABORT callback functions.
697
System action
See ERZ115025E.
User response
See ERZ115025E.
AB56:
Explanation
CICS mirror failed to allocate storage for commarea.
System action
See ERZ115026E.
User response
See ERZ115026E.
AB57:
Explanation
CICS mirror failed to send response data.
System action
See ERZ115027E.
User response
See ERZ115027E.
AB58:
Explanation
CICS detected a corrupted commarea signature detected during free.
System action
See ERZ115028E.
User response
See ERZ115028E.
AB61:
Explanation
Local transaction aborted due to SNA timeout waiting on receive.
698
System action
User response
Either reissue the transaction or increase the receive timeout.
ACS1:
Explanation
CICS application server is not able to allocate enough memory in task private pool.
System action
The specified transaction terminates.
User response
the task private pool and restart CICS.
U0101:
Explanation
CICS was unable to attach the Region Pool shared memory.
System action
User response
Ask the system administrator to check for inconsistencies in the CICS shared
memory segments by using the ipcs command; these segments must have read
and write permissions for user cics and group cics. If the problem cannot be
identified, call your support organization.
U0701:
Explanation
CICS self-consistency checking: inconsistent ICE queue detected
System action
CICS abnormally terminates the region
User response
See message ERZ007001E for appropriate responses to this problem.
699
U0702:
Explanation
CICS self-consistency checking: mismatched expiry time/next start time
System action
User response
U0703:
Explanation
CICS self-consistency checking: inconsistent ICE links
System action
User response
U0704:
Explanation
CICS self-consistency checking: inconsistent ICE links
System action
User response
U0705:
Explanation
CICS self-consistency checking: inconsistent ICQ Reqid hash values
System action
User response
700
U0706:
Explanation
CICS self-consistency checking: inconsistent ICQ Reqid hash values
System action
User response
U0707:
Explanation
Was unable to schedule the blocked Interval Control Element (ICE) recovery
transaction
System action
User response
During auto start, CICS attempted to recover Interval Control Elements (ICEs), but
was unable to do so because Temporary Storage is unavailable. Therefore, it
attempts to schedule a transaction to recover the blocked requests. This attempt to
schedule the transaction has failed. Check that the region pool size is sufficiently
large. If it is not, increase it and restart the region. Check that the attribute
CUBSDelayMinutes in the Region Definitions has a reasonable value, between 1
and 5999. This symptom can be avoided by performing a cold start of the region.
U0708:
Explanation
The data in a Temporary Storage Queue is shorter than expected
System action
User response
During auto start, CICS has attempted to recover Interval Control Elements (ICEs),
but the Temporary Storage queue contains a record that is shorter than expected.
This is possibly because there is a problem with Temporary Storage. Examine
previous messages for an indication of the cause of the problem. This symptom can
be avoided by performing a cold start of the region.
701
U0709:
Explanation
CICS was unable to free a locked resource
System action
User response
During an attempt to delete a free a locked resource, CICS detected an
inconsistency in internal data structures. If you want to investigate this problem,
Check that the previous CICS self-consistency check did not detect any errors. Set
the IntrospectInterval in the Region Definitions to 1 minute and restart the region.
Attempt to reproduce the problem by running that same sequence of transactions
again. If you can reproduce the problem, take note of the transactions that were
running or were terminating when this error occurred, and contact your support
organization.
U0710:
Explanation
Timed wait failed in Interval Control process
System action
User response
The Interval Control process (cicsic) attempted a timed wait, but was unable to do
so due to a lack of region storage. CICS possibly ran out of memory. This can be
due to a transaction that is looping in some way that causes CICS to acquire
substantial amounts of Region Pool memory on its behalf. Check that the Region
Definition value MaxRegionPool is sufficiently large. Increase this value, and
restart the region.
U0711:
Explanation
Failed to access terminal details
System action
User response
While preparing to run a transaction, CICS was unable to access the details of the
terminal on which the transaction attempted to run. CICS possibly ran out of
memory. This can be due to a transaction that is looping in some way that causes
CICS to acquire substantial amounts of Region Pool memory on its behalf. Check
702
that the Region Definition value MaxRegionPool is sufficiently large. Increase this
value, and restart the region.
U0712:
Explanation
Failed to schedule internal transaction
System action
User response
While preparing to run an internal transaction, CICS was unable to find the
transaction, the transaction name is identified in the message that accompanies this
abend. The transaction definition was possibly deleted or disabled in the Trsanction
Definitions for the region. Check the definition for the missing transaction and
correct the problem. If the definition is missing copy the definition for the transaction
from another region.
U0713:
Explanation
Was unable to schedule the Interval Control Element (ICE) Cancel transaction
System action
User response
CICS has attempted to cancel Interval Control Elements (ICEs), but the attempt to
schedule the transaction CICE has failed. Check that the region pool size is
sufficiently large. If it is not, increase it and restart the region.
U0714:
Explanation
CICS received an unexpected exception while processing hand posts.
System action
User response
Contact support.
703
U1001:
Explanation
CICS detected an unexpected exceptional condition.
System action
User response
U1002:
Explanation
CICS failed to attach region shared memory or task shared memory segments.
System action
User response
U1003:
Explanation
CICS failed to create TS configuration file.
System action
User response
U1004:
Explanation
CICS failed to setlocale and/or open message catalogue.
System action
704
User response
U1005:
Explanation
Failed to save locale.
System action
User response
U1006:
Explanation
Failed to obtain locale.
System action
User response
U1007:
Explanation
CICS failed to obtain pointer to Region record.
System action
User response
U1008:
Explanation
CICS failed to detach pointer from Region record.
705
System action
User response
U1009:
Explanation
CICS failed to schedule the CLAM transaction.
System action
User response
U1010:
Explanation
CICS failed to cancel the CLAM transaction.
System action
User response
U1011:
Explanation
CICS was unable to get CWA.
System action
User response
706
U1012:
Explanation
bde_ThreadCreate failure.
System action
User response
U1013:
Explanation
CICS failed to initialize task private memory.
System action
User response
U1014:
Explanation
CICS failed to create heartbeat process.
System action
User response
U1015:
Explanation
System process ended unexpectedly or in error.
System action
707
User response
U1016:
Explanation
CICS failed to initialize process.
System action
User response
U1017:
Explanation
CICS failed to register as an Application Manager.
System action
User response
U1018:
Explanation
CICS self consistency checking failed.
System action
User response
U1019:
Explanation
CICS failed to create the Log Daemon.
708
System action
User response
U1020:
Explanation
CICS failed to create the Listener Manager.
System action
User response
U1021:
Explanation
CICS failed to create the Application Manager.
System action
User response
U1022:
Explanation
CICS failed to initialize TCA.
System action
User response
709
U1024:
Explanation
CICS failed to create the Transaction Server.
System action
User response
U1025:
Explanation
CICS failed to run the startup program.
System action
User response
U1027:
Explanation
CICS failed to allocate id hash table entry.
System action
User response
U1028:
Explanation
CICS failed to enable the Application Server group.
System action
710
User response
U1029:
Explanation
CICS failed to execute the CAIN transaction.
System action
User response
U1030:
Explanation
CICS failed to enable the Application Server class.
System action
User response
U1031:
Explanation
CICS failed to execute the CRAB transaction.
System action
User response
U1032:
Explanation
Unable to access listener definition record or unable to create CICS listener
process. Messages are logged to indicate the nature of the problem.
711
System action
User response
U1033:
Explanation
This copy of CICS is not licensed to run. The CICS License Manager was not able
to locate a valid license. Additional messages indicate the reason for the licensing
failure.
System action
User response
you require assistance in licensing your copy of CICS, contact your support
organization.
U1034:
Explanation
The CICS region was configured to use DB2 for its file and queue management but
CICS was unable to determine which DB2 instance to use. This was because the
DB2INSTANCE environment variable and the RDBMSInstance entry in the RD
stanze were both empty.
System action
User response
Determine which DB2 instance is to be used for the CICS file and queue
management and set this value in the RDBMSInstance field of the RD stanza or in
the DB2INSTANCE environment variable. If the problem persists, contact your
U1035:
Explanation
The CICS region was configured to use Oracle for its file and queue management
but CICS was unable to determine which Oracle instance to use. This was because
the ORACLE_SID environment variable and the RDBMSInstance entry in the RD
stanze were both empty.
712
System action
User response
Determine which Oracle instance is to be used for the CICS file and queue
management and set this value in the RDBMSInstance field of the RD stanza or in
the ORACLE_SID environment variable. If the problem persists, contact your
U1036:
Explanation
The CICS region was configured to use Oracle for its file and queue management
but CICS was unable to determine the value for ORACLE_HOME.
System action
User response
Determine the correct setting for ORACLE_HOME and export the ORACLE_HOME
environment variable or define it in the CICS regions environment file. If the
U1037:
Explanation
An IIOP listener definition must be defined if an IIOP SSL listener definition is
defined.
System action
User response
Define both an IIOP and an IIOP SSL listener definition if you require IIOP SSL
support.
U1038:
Explanation
An IIOP SSL listener definition is defined but the IIOP version for generated object
references is set to 1.0.
System action
713
User response
Define the IIOP version for generated object references to 1.1 if you require an IIOP
SSL Listener.
U1039:
Explanation
An IIOP workload-managed SSL port is defined but no IIOP SSL Listener was
defined for this region.
System action
User response
Define an IIOP SSL Listener if you intend to support an IIOP workload-managed
SSL configuration.
U1101:
Explanation
CICS was unable to initialize the CICS terminal component.
System action
CICS terminates the region abnormally.
User response
Examine previous messages to see whether the region was short of storage.
U1401:
Explanation
One of the CICS control processes detected an exceptional condition.
System action
User response
This abend indicates an internal problem in one of the CICS control processes. If
the region definition SysDump attribute is set to yes, a region dump file is
produced. Save this file. Restart the region, ensuring that the region is configured to
produce a dump if the problem recurs. Contact your support organization.
714
U1403:
Explanation
CICS made an unsuccessful attempt to attach to the shared memory segment of
the region.
System action
User response
This abend indicates an internal CICS problem. If the region definition SysDump
attribute is set to yes, a region dump file is produced. Save this file. Restart the
region, ensuring that the region is configured to produce a dump if the problem
recurs. Contact your support organization.
U1404:
Explanation
CICS made an unsuccessful attempt to browse the transaction definition database.
System action
User response
This abend indicates an internal CICS problem. If the region definition SysDump
attribute is set to yes, a region dump file is produced. Save this file. Restart the
region, ensuring that the region is configured to produce a dump if the problem
recurs. Contact your support organization.
U1501:
Explanation
The periodic consistency check performed by CICS on the Program Control
structures detects an error that CICS is unable to correct. These data structures
hold information about programs running at each logical level.
System action
The CICS region is abnormally terminated.
User response
Because the Program Control data structures are held in the Region Pool, it is
unlikely that the invalid data has been produced by application code. Save any
dump file produced for use by your support organization. If the problem persists
715
U1507:
Explanation
CICS is unable to free Region Pool storage allocated for Program Control data
structures. These data structures hold information about programs running at each
logical level.
System action
User response
Because the Program Control data structures are held in the Region Pool, the
problem encountered freeing the data structures is unlikely to be caused by
application code. It is more likely to be caused by an inconsistency in the CICS
internal data structures. If the problem reoccurs, save any dump file produced and
U1512:
Explanation
CICS is unable to delta a Program Definition database record after locking it. This is
likely to be caused by an inconsistency in the CICS internal data structures.
System action
User response
U1513:
Explanation
CICS is unable to get exclusive access to a Program Definition database entry.
CICS encountered an error freeing Region Pool storage during this operation. This
is likely to be caused by an inconsistency in the CICS internal data structures.
System action
User response
716
U1514:
Explanation
CICS is unable to attach shared memory used for the Region Pool after returning
from application code. Region Pool memory is protected while running application
code by detaching it.
System action
User response
This error can occur if shared memory segments are removed accidentally.
Otherwise, it can be caused by a CICS internal problem. In this case, save any
dump file produced and contact your support organization.
U1516:
Explanation
CICS is unable to update the database record for the principal facility during an
EXEC CICS RETURN TRANSID COMMAREA command. This is likely to be caused
by an inconsistency in the CICS internal data structures.
System action
User response
U1517:
Explanation
CICS is unable to load the C language support program cicsprC. cicsprC is used
to load and run C application programs.
System action
User response
Investigate the cause of the load failure by using the ERZ015035E error message
logged earlier and the symptom records. Check that the full pathname of cicsprC
recorded in error message ERZ015035E refers to a valid executable file that is
accessible. If this file does not exist, or is inaccessible, contact your system
administrator, because CICS is possibly not installed properly or possibly became
corrupted. In this case the system administrator can consider reinstalling CICS. If
717
the problem cannot be solved and persists, then save any dump file produced and
U1518:
Explanation
CICS is unable to allocate enough memory, from the Region Pool to initialize the
quickcell pools.
System action
User response
U1701:
Explanation
During system startup, CICS was unable to allocate Region Pool storage for its
internal data structures.
System action
CICS shuts down the region.
User response
Increase the size of the Region Pool by restarting the region with an override for
the value of the MaxRegionPool attribute in the Region Definition (RD). If the
U2203:
Explanation
System action
message ERZ022003E.
User response
message ERZ022003E.
U2224:
Explanation
CICS was unable to complete recovery processing for Transient Data queues.
718
System action
User response
Check preceding messages for the cause of the error. The recovery data is stored
in the filesystem, so this can be caused if CICS is unable to access that data.
U2231:
Explanation
System action
User response
U2238:
Explanation
System action
User response
U2239:
Explanation
System action
User response
U2242:
Explanation
719
System action
See message ER0Z22042E.
User response
U2243:
Explanation
System action
See message ER0Z22043E.
User response
U2251:
Explanation
System action
User response
U2264:
Explanation
System action
User response
U2265:
Explanation
720
System action
User response
U2269:
Explanation
System action
User response
U2270:
Explanation
System action
User response
U2274:
Explanation
System action
User response
U2287:
Explanation
721
System action
User response
U2288:
Explanation
System action
User response
U2289:
Explanation
System action
User response
U2312:
Explanation
CICS is unable to allocate enough memory, from the Region Pool, to initialize
Temporary Storage (TS).
System action
User response
You can increase the size of the Region Pool available by restarting the region and
overriding the MaxRegionPool attribute, with a larger value, on the command line.
722
U2313:
Explanation
CICS is unable to save information for unprotected asynchronous start requests in
the filesystem.
System action
User response
Determine the cause of the error from associated messages and resolve. Restart
the region and resubmit the start requests.
U2314:
Explanation
CICS is unable to restore information for unprotected asynchronous start requests
from the filesystem as the file server is unavailable.
System action
User response
Make the file server available and restart the region.
U2315:
Explanation
CICS self-consistency checking has detected that the chain of queues involved in
the current LUW for the transaction was overwritten by invalid data.
System action
User response
U2319:
Explanation
CICS was unable to rewrite a runtime database TS entry.
System action
723
User response
Refer to any previous messages indicating why the runtime database entry was
unable to be updated.
U2329:
Explanation
CICS cannot insert a runtime database entry during Temporary Storage (TS)
restoration of queues from the system journal.
System action
User response
Restart the region, if the error continues to occur then Cold start the region.
U2334:
Explanation
The size of the Temporary Storage (TS) checkpoint buffer, read from the system
journal, was overwritten. It is the wrong size.
System action
User response
Cold Start the region.
U2342:
Explanation
CICS Temporary Storage (TS) self consistency checking has found a TS queue
runtime database entry with an invalid Status attribute value.
System action
User response
U2348:
Explanation
CICS self-consistency checking has found an Auxiliary Temporary Storage (TS)
queue containing Main TS queue data.
724
System action
User response
U2353:
Explanation
CICS self-consistency checking has found a mismatch between maintained count of
LUWs and actual number of LUWs.
System action
User response
U2354:
Explanation
CICS self-consistency checking has found an invalid address to the Temporary
Storage (TS) private management data for a queue.
System action
User response
U2356:
Explanation
CICS self-consistency checking has found an unknown Temporary Storage (TS)
queue type in its internal management data.
System action
User response
Restart the region, if CICS self-consistency checking continues to detect
725
U2358:
Explanation
CICS self-consistency checking has found an unknown Temporary Storage (TS)
queue Action in its internal management data.
System action
User response
U2362:
Explanation
CICS was unable to provide access to Auxiliary Temporary Storage (TS) queues.
System action
User response
Refer to the preceding message(s) that detail why CICS was unable to access
Auxiliary TS queues. Restarting the Auxiliary TS File Server(s) can enable access to
TS queues. If the problem persists it is likely that the configuration of the TS File
Server(s) is suspect.
U2372:
Explanation
CICS was unable to complete recovery processing for Recoverable Temporary
Storage queues.
System action
User response
Check preceding messages for the cause of the error. The recovery data is stored
in the filesystem, so this can caused if CICS is unable to access that data.
U2404:
Explanation
CICS is unable to attach shared memory to the callback function registered with the
Log Service.
726
System action
See ERZ2404E.
User response
See ERZ2404E.
U2406:
Explanation
CICS is unable to write a restart record to a log file. If the region is allowed to
continue, this problem can prevent CICS recovery algorithms from working correctly.
System action
See ERZ2406E.
User response
See ERZ2406E.
U2407:
Explanation
This abend can be caused by any of the following:
v CICS was auto-started after the log service was cold started.
v CICS is unable to determine the position in a log file at which to begin recovery
processing. A restart position is always set by CICS when it creates a log file so
this problem suggests a malfunction in either CICS or the Log Service.
v CICS is unable to read a log record at the restart position in a log. This error
suggests that the restart position for the log file was overwritten with invalid data.
v CICS has read a record at the restart position in the log file but it contained
invalid data.
System action
See ERZ2407E.
User response
See ERZ2407E.
U2409:
Explanation
An attempt to read from a log file was unsuccessful.
System action
See ERZ2409E.
727
User response
See ERZ2409E.
U2411:
Explanation
An unexpected record type was read from a log file.
System action
See ERZ2411E.
User response
See ERZ2411E.
U2413:
Explanation
This abend can be caused by any of the following:
v CICS is unable to open a Log Service cursor in a log file. This operation attempts
to establish a context for subsequent reads by selecting a subset of the log
records to be retrieved, a position in the log and a direction. This problem
prevents the retrieval from the log of records required to recover CICS resources
correctly.
v CICS is unable to change the position of a Log Service cursor in a log. This
problem prevents the retrieval from the log of records required to recover CICS
resources correctly.
System action
See ERZ2413E.
User response
See ERZ2413E.
U2416:
Explanation
The Log Service has an internal problem from which it is unable to continue. It has
requested an action from CICS to terminate the region immediately.
System action
See ERZ2416E.
User response
See ERZ2416E.
728
U2419:
Explanation
CICS has recovered the last successful checkpoint written to the Log Service, but is
unable to find data for all the modules required.
System action
See ERZ2419E.
User response
See ERZ2419E.
U2425:
Explanation
CICS has detected a mismatch between a counter and the actual number of objects
existing. As these objects are allocated out of the region pool, it is not likely that this
problem is caused by user action or user transactions.
System action
See ERZ2425E.
User response
See ERZ2425E.
U2430:
Explanation
CICS is unable to find a log for a application server that it has started. The set of
logs available for use in recovery processing is maintained in memory allocated
from the region pool and is retrieved from the CICS master log (identified by the
CLogName attribute in RD) during initial recovery processing. This message is
produced when the CICS application manager (cicsam process) attempts to read
from a log not present in the available list. This is not supposed to happen unless
an internal problem exists or unless region pool memory was overwritten.
System action
See ERZ2430E.
User response
See ERZ2430E.
U2450:
Explanation
Failed opening the master system journal
729
System action
See ERZ2450E.
User response
See ERZ2450E.
U2451:
Explanation
CICS is unable to write to the specified log file.
System action
See ERZ2451E.
User response
See ERZ2451E.
U2454:
Explanation
CICS is attempting to obtain memory from the Region Pool for reading the system
log. Insufficient memory is available.
System action
See ERZ2454E.
User response
See ERZ2454E.
U2455:
Explanation
CICS is attempting to obtain memory for log archive control information from the
Region Pool. Insufficient memory is available.
System action
See ERZ2455E.
User response
See ERZ2455E.
730
U2456:
Explanation
CICS is attempting to obtain Task Shared Pool memory for a start of checkpoint
buffer to contain log management data. Insufficient memory is available.
System action
See ERZ2456E.
User response
See ERZ2456E.
U2457:
Explanation
CICS writes some log data into buffered storage to improve performance. It also
attempts to write log data direct to permanent storage (storage that survives a
system crash or a restart of the Log Service), forcing all earlier buffered data to
become permanent too.
This message is produced when the Log Service is unable to make data permanent
when requested to do so by CICS.
System action
See ERZ2457E.
User response
See ERZ2457E.
U2460:
Explanation
CICS is unable to open an Application Server log file during recovery processing.
The CICS application manager obtains the list of Application Server log files
needing recovery from the CICS master log, and stores this list in memory obtained
from the Region Pool.
Possible causes of this problem therefore include:
v Region Pool memory was overwritten with invalid data (either before the list is
written to the Log Service, or after the list was retrieved from the Log Service)
v Log Service data was overwritten with invalid data
v Other users of the Log Service have deleted the log file
v The Log Service was cold started since your region was started
v Another process has the log file opened already.
It is unlikely that misbehaving user transactions can cause this problem.
731
System action
See ERZ2460E.
User response
See ERZ2460E.
U2463:
Explanation
CICS is attempting to obtain memory from the Region Pool for a log control list
element. Insufficient memory is available.
System action
See ERZ2463E.
User response
See ERZ2463E.
U2467:
Explanation
CICS was unable to initialize the log service client whilst attempting to start a CICS
process. This is usually because the logserver process has died or because of RPC
communication problems.
System action
See ERZ2467E.
User response
See ERZ2467E.
U2470:
Explanation
CICS is attempting to open a user journal defined with InitialOpenFlag=yes in the
Journal Definitions (JD). It is unable to create and insert a TDQ runtime database
entry corresponding to the user journal being opened because there is insufficient
memory in the Region Pool.
System action
See ERZ2470E.
User response
See ERZ2470E.
732
U2475:
Explanation
CICS is attempting to write to a user journal that is designated as a crucial
journal. CICS is unable to write to this journal. Possible causes include deadlock
timeout, insufficient space on the relevant filesystem and bad destination path
specified in the journal definition (JD).
System action
See ERZ2475E.
User response
See ERZ2475E.
U2497:
Explanation
System action
See ERZ2497E.
User response
See ERZ2497E.
U2498:
Explanation
CICS detected an unrecoverable error whilst attempting to write to the system log.
System action
See ERZ2466E.
User response
See ERZ2466E.
U2499:
Explanation
CICS was unable to introspect Reg data
System action
See ERZ24113E.
733
User response
See ERZ24113E.
U2501:
Explanation
CICS failed to initialize server-side transaction support.
System action
User response
Refer to the associated messages for further guidance on resolving the problem.
U3901:
Explanation
Insufficient storage to initialize the transaction scheduler.
System action
Refer to message ERZ039004E.
User response
Refer to message ERZ039004E.
U4419:
Explanation
System action
See ERZ4419E.
User response
See ERZ4419E.
U4511:
Explanation
CICS was unable to load a user-defined External Security Manager (ESM) into the
region at region startup.
System action
CICS abnormally terminates the region during startup.
734
User response
Check console.msg for messages from CICS that concern problems with the
External Security Manager (ESM).
U4512:
Explanation
CICS was unable to initialize the user-defined External Security Manager (ESM).
The ESM initialization module returned an error.
System action
User response
Check the documentation and source code of the ESM to ascertain in what
circumstances errors can be raised during ESM initilization.
U4536:
Explanation
CICS was unable to allocate storage from the region pool.
System action
User response
Check the value of your MaxRegionPool, MaxTaskPrivatePool, and MaxTSHPool
region database attributes. Increase these values and try again.
U4540:
Explanation
CICS was unable to load a user-defined External Authentication Manager (EAM)
into the region at region startup.
System action
User response
Check console.msg for messages from CICS that concern problems with the
External Security Manager (EAM).
735
U4541:
Explanation
CICS has failed to change the password for a CICS User present in U ser Defintion
or External Authentication Manager.
System action
CICS abnormally terminates the application process.
User response
Check console.msg for further messages from CICS that indicate what went wrong.
U4542:
Explanation
CICS has failed to allocate storage ,while Installing User Attributes supplied by EAM
in CICS runtime.
System action
CICS abnormally terminates the application process.
User response
Check console.msg for further messages from CICS that indicate what went wrong.
U4801:
Explanation
CICS self-consistency checking detected some unrecoverable problems in the
region or task shared pools.
System action
User response
This abend is accompanied by messages in console.msg. Use these messages and
the information associated with them to determine what action to take.
U4802:
Explanation
CICS attempted to free region pool storage that was not allocated. This abend
usually indicates a software problem in CICS.
System action
736
User response
This abend is accompanied by messages in console.msg. Use these messages and
the information associated with them to determine what action to take. Contact your
U4803:
Explanation
CICS did not complete initialization of the region or task shared pools.
System action
CICS abnormally terminates the region at startup.
User response
There may be invalid parameters in the Region Definition defining the configuration
of the region or task shared pools. See TXSeries for Multiplatforms Administration
Guide for information on configuring these attributes. The system limits on numbers
or sizes of shared memory segments were possibly exceeded, or else there was
possibly insufficient memory to fulfill the request. Restart the region with new values
in the Region Definitions or by using CICS command line parameters at startup.
U4911:
Explanation
CICS was unable to process your request to either start or stop the auxiliary trace
facility, because it was unable to contact the CICS main process. More details are
possibly have been provided by an earlier messages.
System action
User response
Refer to the associated messages for guidance on resolving the problem. If the
U4916:
Explanation
CICS was unable to save the product trace restart configuration in the
region_restart file. More details are possibly provided by an earlier message.
System action
737
User response
Remove the CICS restart file and restart the region, specifying a cold start. Refer to
the associated messages for further guidance on resolving the problem. If the
U5001:
Explanation
CICS is unable to reattach shared memory. Further messages can be found in the
message log and give more information about the problem.
System action
User response
Restart the region. If the problem persists, contact your support organization.
U5104:
Explanation
CICS was unable to initialize the statistics file, because the file was unable to be
opened.
System action
User response
Ensure that the directory in which the statistics file is located exists. Also ensure
that CICS has permission to write to the statistics file. If the problem persists,
U5201:
Explanation
CICS was unable to allocate storage to perform a wait during a system dump.
System action
CICS abnormally terminates the process.
User response
Increase the Region Definition value MaxRegionPool and restart the region.
738
U5310:
Explanation
CICS was unable to save the statistics restart configuration to the region restart file.
System action
User response
Remove the CICS restart file and restart the region, specifying a COLD start. Refer
to the associated messages for further guidance on resolving the problem. If the
U5655:
Explanation
A crucial mutual exclusion lock is held by a terminated process.
System action
User response
U5701:
Explanation
CICS detected an unsuccessful condition.
System action
User response
U5702:
Explanation
CICS message processing facility overwrote a buffer.
System action
CICS abnormally terminates the current execution environment: in the runtime, the
whole region is terminated; elsewhere, the current process is terminated.
739
User response
U5733:
Explanation
CICS is unable to attach shared memory. Further messages can be found in the
message log and give more information about the problem.
System action
User response
Restart the region. If the problem persists, contact your support organization.
U5801:
Explanation
CICS failed to handle a synchronous terminating signal.
System action
User response
U5802:
Explanation
CICS failed to attach the Region Pool shared memory.
System action
User response
U5804:
Explanation
Server-side transaction support was requested but is not supported on this platform.
740
System action
User response
U5805:
Explanation
An attempt was made to acquire a CICS license; however, this was unsuccessful.
Either a license does not exist, an expiration date has passed, or the license
information was tampered with.
System action
User response
The trial period has expired. Contact your support organization to buy a copy of
CICS.
U5806:
Explanation
CICS is configured to use Local SNA, but the SunLink SNA shared library
sunlu62.so was unable to be loaded. This probably means that SunLink SNA is
installed incorrectly. There is either a Listener Definition (LD) entry or a
Communications Definition (CD) entry that references Local SNA.
System action
User response
If you want to use Local SNA then install SunLink SNA correctly. If you do not want
to use SNA then remove or change the definitions that reference Local SNA. CICS
expects to find the SunLink SNA shared library in /opt/SUNWlu62, in
/opt/SUNWappc, or in a directory in your LD_LIBRARY_PATH.
U5807:
Explanation
CICS was unable to find a necessary SNA function in the SNA shared library
sunlu62.so.
System action
741
User response
Install SunLink SNA correctly because it appears to be corrupted.
U5808:
Explanation
CICS failed to load SNA support.
System action
User response
U5810:
Explanation
CICS is configured to use Local SNA, but the APPC library for your SNA product
System action
User response
If you want to use Local SNA, then ensure that your SNA product is installed
correctly and set the CICS_SNA_APPC_LIBRARY environment variable to the full
path name of the SNA APPC library. If you do not wish to use local SNA, then
remove all Listener Definition (LD) entries that have Protocol=SNA from your
region.
U5811:
Explanation
CICS is configured to use Local SNA, but the Attach Manager library for your SNA
product was unable to be found.
System action
User response
If you wish to use Local SNA, then ensure that your SNA product is installed
correctly and set the CICS_SNA_ATTACH_LIBRARY environment variable to the
full path name of the SNA attach manager library. If you do not wish to use local
SNA, then remove all Listener Definition (LD) entries that have Protocol=SNA from
your region.
742
U58400:
Explanation
A crucial mutual exclusion lock is held by a terminated process.
System action
User response
U58401:
Explanation
The iconv-emulation code was unable to initialize correctly.
System action
User response
U6201:
Explanation
CICS cannot free the memory allocated for the terminal I/O area in the Task Shared
Pool.
System action
User response
Check your program to see that it is not incorrectly freeing or writing to memory in
the Task Shared Pool. Retry the transaction.
U6301:
Explanation
System action
See ERZ6308E.
743
User response
See ERZ6308E.
U8005:
Explanation
System action
User response
U8008:
Explanation
System action
User response
U8022:
Explanation
System action
User response
U8023:
Explanation
System action
744
User response
U8025:
Explanation
System action
User response
U8030:
Explanation
System action
User response
U8032:
Explanation
System action
User response
U8033:
Explanation
System action
745
User response
U8034:
Explanation
System action
User response
U8035:
Explanation
System action
User response
U8036:
Explanation
System action
User response
U8038:
Explanation
System action
746
User response
U8039:
Explanation
System action
User response
U8041:
Explanation
System action
User response
U8045:
Explanation
System action
User response
U8046:
Explanation
System action
747
User response
U8047:
Explanation
System action
User response
U8048:
Explanation
System action
User response
U8049:
Explanation
System action
User response
U8087:
Explanation
System action
748
User response
UA401:
Explanation
Insufficient storage to initialize CICS Open Listener component.
System action
See ERZ106001E.
User response
See ERZ106001E.
UB401:
Explanation
Unable to attach shared memory.
System action
See ERZ114003E.
User response
See ERZ114003E.
UB402:
Explanation
Unable to create .odbc.ini file.
System action
See ERZ114011E.
User response
See ERZ114011E.
UB404:
Explanation
No entry in class update table.
System action
See ERZ114027E and ERZ114028E as appropriate.
749
User response
See ERZ114027E and ERZ114028E as appropriate.
UB406:
Explanation
Unable to start Java virtual machine within a CICS application server process.
System action
See ERZ114036E.
User response
See ERZ114036E.
UB407:
Explanation
Unable to allocate region storage.
System action
See ERZ114041E.
User response
See ERZ114041E.
UB408:
Explanation
Invalid IIOP configuration data.
System action
See ERZ114042E, ERZ114043E, ERZ114044E, ERZ114049E, and ERZ114050E as
appropriate.
User response
See ERZ114042E, ERZ114043E, ERZ114044E, ERZ114049E, and ERZ114050E as
appropriate.
UB519:
Explanation
750
System action
See ERZ115019E.
User response
See ERZ115019E.
UB520:
Explanation
System action
See ERZ115020E.
User response
See ERZ115020E.
751
752
Chapter 4. CICS Toolkit message and codes

CICS Toolkit messages relating to the SFS Server and PPC Gateway Server can
be viewed on the console, stored in log files, and directed to the standard error
device for a server. Errors can be displayed on the screen in an application
program.
Note: In order for a formatted message string containing details about an error to
be displayed, the NLSPATH and LANG environment variables must be set.
This chapter describes the types of messages and codes generated by the CICS
Toolkit that are included in this document and how error information can be
displayed.
CICS Toolkit messages

The CICS Toolkit trace is described in the TXSeries for Multiplatforms SFS Server
and PPC Gateway Server: Advanced Administration.
0x10081c17 trpc_CallToGetTid failed: %k
0x141c1027 Cannot create thread pool ( %k ).
Explanation:
An attempt to register a function to be called when a
request to obtain a transaction identifier (TID) failed.
Explanation:
An attempt to create a server RPC thread pool failed
while the server was registering its administrative
interface.
User response:
This error occurs as the result of a coding error in the
application. If the application is user written, ensure that
the threadTid package is initialized only once;
otherwise, notify your customer support organization
about the error.
User response:
Depending on the error status, determine the root cause
of failure and take corrective action. The most likely
cause is the lack of sufficient memory resources (swap
space or real memory).
Component:
threadTid
Component:
admin
Severity:
WARNING
Severity:
WARNING
Variables:
%k an RPC or CICS Toolkit status code
Variables:
%k the status code returned from the
trdce_CreateThreadPool function
0x141c1017 Cannot convert the %s interface

specification to an interface id ( %k ).
Explanation:
The call to convert a RPCE interface specification into
an interface identifier failed because of an internal CICS
Toolkit error. Report the problem to your customer
Component:
admin
Severity:
WARNING
Variables:
v
v
%s the interface name

%k the status code returned by the rpc_if_inq_id
function
0x141c1057 Cannot register the %s administrative

interface ( %k ).
Explanation:
The error message indicates that an RPC runtime error
occurred.
Component:
admin
Severity:
WARNING
Variables:
v
v

%k the status code returned by the
trdce_OfferInterface function
753
0x14301c17 0x18080837
0x14301c17 Could not open trace redirection
output file %s .
0x18080817 Opening file %s failed with %k , errNo=

%d
Explanation:
The attempt to open the specified trace-redirection
output file failed.
Explanation:
The Log Service failed to open an archive file or device.
User response:
Verify that the specified trace-redirection file can be
written to by the process generating the trace (on the
node where the process is running). Some possible
causes follow:
v An invalid file pathname
v Insufficient privilege for the server process (not the
initiating trace administrative command) to write to
the specified file
v Insufficient resources, for example, not enough file
descriptors
Component:
admin
Severity:
WARNING
Variables:
%s the name of the file that could not be opened
0x14343c27 %s : Illegal Option -- %s
Explanation:
The user specified an illegal command-line option to the
trace listener program.
User response:
Correct the command line to specify only supported
options. This warning message displays the correct
command usage.
Component:
admin
User response:
Check that the file exists and that the permissions are
appropriate.
Component:
log
Severity:
WARNING
Variables:
v
%s the filename
%k the cause of the failure
%d the errno number
0x18080827 Closing file %s failed with %k , errNo=

%d
Explanation:
The Log Service failed to close an archive file or device.
User response:
Failure to close a file should happen rather rarely.
Report the error code to your customer support
organization.
Component:
log
Severity:
WARNING
Variables:
v
%s the filename
%d the errno number
Severity:
WARNING
Variables:
v
%s the program name
%s the offending user-specified option
0x14343c56
0x18080837 Reading file %s failed with %k , errNo=

%d
Explanation:
The Log Service failed to read from an archive file or
device.
Explanation:
See 0x14343c3c.
User response:
Examine the error code for an I/O error. Make sure no
other processes are manipulating the file.
0x14343c86
Component:
log
Explanation:
See 0xc8342c16.
Severity:
WARNING
Variables:
754
%s the filename
%d the errno number
0x18080847 0x18180427
0x18080847 Writing file %s failed with %k , errNo=
%d
Explanation:
The Log Service failed to write to an archive file or
device.
User response:
Component:
log
Severity:
WARNING
Variables:
v
%s the filename
%d the errno number.
0x18080857 Removing file %s failed with %k ,

errNo= %d
Explanation:
The Log Service failed to delete an archive file or
device.
User response:
Make sure the server has sufficient permission on the
file. Make sure no other processes are manipulating the
file.
Component:
log
Severity:
WARNING
Variables:
v
%s the filename
%d the errno number
0x18080867 Flushing file %s failed with %k , errNo=

%d
Explanation:
The Log Service failed to flush changes to an archive
file or device.
User response:
Component:
log
Severity:
WARNING
Variables:
v
%s the filename
%d the errno number
0x18080877 Unknown bde operation in

DisplayBdeError.
Explanation:
This message indicates an unlikely internal error.
User response:
Report this to your customer support organization.
Component:
log
Severity:
WARNING
0x18081037 OP MSG: Fetch archive file %s After
fetching, invoke tkadmin enable
archfile.
Explanation:
The log recovery procedure is expecting an archive file.
User response:
Move the expected archive file into the archive directory
and issue the tkadmin enable archfile command to tell
the server that the archive file is ready.
Component:
log
Severity:
WARNING
Variables:
%s the archive filename expected
0x18180417 Query on volume %s failed with %s
Explanation:
The Log Service failed to query the log volume.
User response:
Use the error returned by VOL to determine the cause
of the failure and take action accordingly.
Component:
log
Severity:
WARNING
Variables:
v
v
%s the volume identifier

%s the error returned by the Volume Service
(VOL)
0x18180427 Mount of volume %s failed with %s

Explanation:
An operation to mount the log volume failed.
User response:
755
0x18180437 0x18180477
of the failure and take action accordingly.
Component:
log
Severity:
WARNING
Variables:
v
v

(VOL)
0x18180437 Writing page range < %d , %d > on

volume %s failed with %s
0x18180457 Filling page range < %d , %d > on

volume %z failed with %s
Explanation:
An operation to fill a range of pages failed.
User response:
of failure (for example, an I/O error) and take action
accordingly.
Component:
log
Severity:
WARNING
Variables:
Explanation:
An operation to write to a range of pages failed.
%d the first page number
%d the last page number
User response:
of failure, for example, an I/O error, and take action
accordingly.
Component:
log
Severity:
WARNING
Variables:
v
%d the first page number
%d the last page number

(VOL)
0x18180447 Reading page versions for page %d on

volume %s failed with %s
Explanation:
An operation to read versions of a page failed.
User response:
of failure, for example, an I/O error, and take action
accordingly.
Component:
log
Severity:
WARNING
Variables:
v
%d the page number

(VOL)
0x18180467 Certifying volume %s failed with %s

Explanation:
An operation to certify the log volume failed.
User response:
of failure and take action accordingly.
Component:
log
Severity:
WARNING
Variables:
v
v

(VOL)
Explanation:
An operation to read the log volume failed.
User response:
of failure and take action accordingly.
Component:
log
Severity:
WARNING
Variables:
v
0x18180477 Reading from volume %s failed with

%s
756

(VOL)

(VOL)
0x18242c17 0x18400417
0x18242c17 Error %k while writing or forcing data
to log
Explanation:
The buffered log records cannot be forced to the disk,
probably because of an I/O error, and the log volume is
disabled.
User response:
Examine the error code and check for disk problems.
Component:
log
Severity:
WARNING
Variables:
v
%k the error status in text form
%s the log volume identifier
0x18242c27 Disabling log volume %s

Explanation:
See 0x18242c17.
0x18281417 Could not set tail after file deletion on
vol %s
Explanation:
The log tail cannot be reset after a log file is deleted on
the log volume, probably due to a shortage of space in
the log volume or to an I/O error.
User response:
Depending on the error code, check for disk problems
or use administrative tools to find out whether there is
enough space in the log volume.

or use administrative tools to find out whether there is
enough space in the log volume.
Component:
log
Severity:
WARNING
Variables:
v
%k the error code
0x18340c37 Log: Fm_Checkpoint: could not write

checkpoint record on volume %s
Explanation:
See 0x18340c27.
0x18340c67 Log: Fm_Checkpoint: error code was
%k
User response:
or use administration tools to find out if there is enough
space in the log volume.
Component:
log
Severity:
WARNING
Variables:
v
%k the error code
%k the error code
Component:
log
0x18340c77 Log: Fm_Checkpoint: could not set

tails, status %k
Severity:
WARNING
Explanation:
See 0x18340c67.
Variables:
0x18400417 Error %k while writing metadata to log
0x18340c17 Log: Fm_Checkpoint: could not write

start checkpoint record on volume %s
Explanation:
See 0x18340c27.
Explanation:
The log metadata cannot be written to the disk,
probably due to an I/O error. The log volume is
disabled.
User response:
0x18340c27 Log: Fm_Checkpoint: write error code

was %k
Component:
log
Explanation:
The start checkpoint record on the log volume was not
written, , probably due to insufficient space in the log
volume or an I/O error.
Severity:
WARNING
User response:
Variables:
v
%k the error code
757
0x18400427 0x1868dc17
0x18400427 Disabling log volume %z
Explanation:
See 0x18400417.
0x18400817 Error %k while forcing checkpoint to
log
Explanation:
The Log Service failed to force the checkpoint to the
disk, probably due to an I/O error. The log volume is
disabled.
User response:
Component:
log
Severity:
WARNING
Variables:
v
%k the error code
0x18400827 Disabling log volume %s

Explanation:
See 0x18400817.
0x18400c17 Unrecognized meta-record: type %d
Severity:
WARNING
Variables:
0x18681837 Log volume %z is short on free space.
Explanation:
The usable space in the log volume has fallen below
the set threshold. This does not mean that the log is
immediately out of service.
User response:
Use administrative tools to monitor the use of disk
space and expand the log volume if necessary.
Component:
log
Severity:
WARNING
Variables:
0x18684017 Could not update restart data to reflect
new archive tail.
Explanation:
The Log Service failed to write the restart record on the
log volume, probably due to insufficient space in the log
volume or to an I/O error.
Explanation:
The meta record type supplied is invalid. This indicates
an internal inconsistency in the Log Service (LOG).
User response:
or use administrative tools to find out if there is enough
space in the log volume.
User response:
Report this problem to your customer support
organization.
Component:
log
Component:
log
Severity:
WARNING
Variables:
%d the meta record type.
0x18681827 Compressing data on log volume %s
for space reclamation.
Explanation:
When it determines that a shortage of disk space is
possible, the Log Service (LOG) compresses data to
reclaim disk space.
User response:
Use administrative tools to monitor the use of disk
space.
Component:
log
758
Severity:
WARNING
0x1868dc17 Log archives may not contain
complete information for log volume
restore. Resolve pending transactions
and flush log media archives to fix this
problem.
Explanation:
In rare situations, the log archive files possibly do not
have a complete set of log records.
User response:
Resolve pending transactions and flush log media
archives to cover the potential vulnerability in case of
log disk failure.
Component:
log
Severity:
WARNING
0x1c500416 0x28106076
0x1c500416 The VOL restart data is corrupted.
Explanation:
The restart data on a volume is invalid.
User response:
Make sure the volume is not corrupted and was
operated by a compatible CICS Toolkit server.
Component:
vol
Severity:
FATAL
0x1c500426 Release and version numbers in VOL
restart data are invalid.
Explanation:
The release and version information on a volume does
not match the CICS Toolkit server version.
User response:
Make sure the volume is not corrupted and is operated
by a compatible version of the CICS Toolkit server.
Component:
vol
Severity:
FATAL
0x280c2057 The TRPC runtime library does not
match compiled manager stubs.
Interface name %s , function name %s ,
stubs version %d .
Explanation:
The generated code and the runtime library contain
incompatible versions.
User response:
Ensure that the application TIDL file is compiled with a
tidl compiler that matches the runtime CICS Toolkit
libraries.
Component:
trpc
Severity:
WARNING
Variables:
v
%s the function name
%s the interface version number for the

generated manager stub code
0x28106056 Runtime library could not acquire a

string binding for a well-known
endpoint ( %k ).
Explanation:
An invalid binding string for a well-known endpoint was
specified by the trpc_UseWkEndpoints or
trpc_BindWkEndpoints function. Most likely, it has

been specified incorrectly, it has been corrupted, or
there was insufficient memory to allocate for returning
the string binding.
User response:
Review the applications use of these functions or
ensure that the process has not exceeded its memory
limit and that sufficient swap space exists on the
machine.
Component:
trpc
Severity:
FATAL
Variables:
%k the error code returned by an RPC string-binding
function.
0x28106066 Runtime library could not parse the
string binding for a well-known
endpoint ( %k ).
Explanation:
A well-known endpoint string binding could not be
parsed, most likely because sufficient memory could not
be allocated for the parsed strings.
User response:
Ensure that the process has not exceeded its memory
limit and that sufficient swap space exists on the
machine.
Component:
trpc
Severity:
FATAL
Variables:
%k the error code returned by an RPC string-binding
function.
0x28106076 Runtime library was provided a
well-known endpoint that uses an
invalid protocol sequence ( %k ).
Explanation:
A well-known endpoint binding specified via the
trpc_UseWkEndpoints or rpc_BindWkEndpoints
function referenced an invalid or unsupported protocol
sequence.
User response:
Review the bindings specified by the application.
Component:
trpc
Severity:
FATAL
Variables:
759
0x28106086 0x2c101027
%k the error code returned by an RPC binding
function.
Severity:
FATAL
0x28106086 Runtime library was provided a

well-known endpoint lacking endpoint
information.
0x2c0c1c17 Application exiting while unterminated

transactions are in progress
Explanation:
A well-known endpoint binding specified via the
trpc_UseWkEndpoints or the rpc_BindWkEndpoints
function did not contain the required endpoint
information.
User response:
Review the bindings specified by the application.
Component:
trpc
Severity:
FATAL
Variables:
%k the error code returned by an RPC binding
function.
0x28107016 Runtime library has been given a
well-known endpoints that have not
been bound by the application.
Explanation:
The application has called the trpc_UseWkEndpoints
function, but at least one endpoint was specified for
which no binding exists.
User response:
Review the application for correctness and refer to the
documentation for the trpc_UseWkEndpoints function;
it is possible that the function trpc_BindWkEndpoints
is needed instead.
Component:
trpc
Severity:
FATAL
0x28107026 Runtime library needs a well-known
endpoint because the application is
recoverable.
Explanation:
A recoverable application must provide a well-known
endpoint. This error indicates that the function
trpc_SetEnvironment has been called and no
well-known endpoint has been specified.
User response:
Change the application to use the
trpc_UseWkEndpoints or trpc_BindWkEndpoints
function appropriately.
Component:
trpc
760
Explanation:
While one or more transactions were being processed,
the application called a function that terminates Tran C.
User response:
The response depends on the application. Transactions
will be eventually be aborted at a time depending on
timeout settings in other participants. This message
possibly helps explain why certain transactions were
aborted or are holding locks longer than expected at
other processes.
Component:
tc
Severity:
WARNING
0x2c101017 Unexpected status exception in
prepare callback: %d
Explanation:
An exception (other than an abort) occurred during the
execution of a user-written prepare callback function.
User response:
Based on the status code, determine the cause of the
exception and correct the prepare callback code.
Component:
tc
Severity:
WARNING
Variables:
%d the exception status code
0x2c101027 Unexpected address exception in
prepare callback
Explanation:
An address exception occurred during the execution of
a user-written prepare callback function.
User response:
Determine the cause of the address exception in the
applications prepare callback code (possibly by using a
debugger).
Component:
tc
Severity:
WARNING
0x2c180417 0x30141817
0x2c180417 Unexpected status exception from
subThread: %d
Explanation:
A status exception occurred during the execution of a
user-written subTran or subThread function being
executed inside a concurrent or cofor block.
the function uuid_from_string . The filename and line

number specify the location of the faulty code.
Component:
tc
Severity:
WARNING
User response:
Determine the cause of the status exception (using a
debugger) and correct the subTran or subThread code.
Variables:
Component:
tc
Severity:
WARNING
Variables:
%d exception status
0x2c180427 Unexpected address exception from
subThread.
Explanation:
An address exception occurred during the execution of
a user-written subTran or subThread function being
executed inside a concurrent or cofor block.
User response:
Determine the cause of the address exception and
correct the subTran or subThread code.
Component:
tc
Severity:
WARNING
0x2c200c17 %s
Explanation:
If a transaction is aborted as part of a concurrent
construct, this warning is generated with the abort
reason string.
Component:
tc
Severity:
WARNING
Variables:
%s the warning message with the abort reason
0x2c500417 %s ( %d ): %k
Explanation:
An attempt to convert the callers UUID string failed
during registration of an abort formatter from Tran C.
User response:
Change the application so that it specifies a properly
formatted UUID string for the abort formatter facility. The
UUID string format is defined in the reference page for
%s the application source code filename
%d the application source code line number

%s the status code returned by the
uuid_from_string function
0x30101c27 Incomplete Page Write detected on

page %s
Explanation:
The write operation to the page is incomplete due to a
disk I/O error.
User response:
Check for disk problems.
Component:
rec
Severity:
WARNING
Variables:
%s the page ID
0x3010c837 Read Page on volume %s page
number: %d failed with volStatus: %k
Explanation:
The Recovery Service failed to read a specified page
from the volume.
User response:
Examine the error code returned by VOL for an I/O
error.
Component:
rec
Severity:
WARNING
Variables:
v
%d the page number
%k the error returned by the Volume Service

(VOL)
0x30141817 All buffers in buffer pool pinned.

Explanation:
The buffer pool is exhausted and the page needed
cannot be brought in.
User response:
761
0x30181417 0x30183c37
Check if the buffer pool limit is sufficient for the
application. Restart the server with a larger buffer pool if
necessary.
Component:
rec
Severity:
WARNING
0x30181417 Read Page on vol %s pageNum: %d
failed with volStatus: %k
Explanation:
The Recovery Service failed to read the specified page
from the volume.
User response:
Check for a disk I/O error.

Component:
rec
Severity:
WARNING
Variables:
v
%d the page number
%k the error code returned by the Volume

Service (VOL)
0x30183847 ReadSegment on volume %z

pageNumBegin: %d numPages: %d
failed with vol_status: %k
Component:
rec
Explanation:
An operation to read a segment of pages from the
volume failed.
Severity:
WARNING
User response:
Variables:
Component:
rec
%d the page number

Service (VOL)
0x30181427 Write Page on vol %s pageNum: %d

Explanation:
An operation to write the specified page to the volume
failed.
User response:
Component:
rec
Severity:
WARNING
Variables:
v
%d the page number

Service (VOL)
Severity:
WARNING
Variables:
v
%d the starting page number
%d the number of pages to read

Service (VOL)
0x30183c37 WriteSegment on volume %z

pageNumBegin: %d numPages: %d
Explanation:
An operation to write a segment of pages to the volume
failed.
User response:
Component:
rec
Severity:
WARNING
0x30183027 Re-reading page on volume %z page

number: %d failed with volStatus: %k
Variables:
v
Explanation:
When a page is locked for writing to the disk, the
Recovery Service (REC) waits for the lock to be
dropped and rereads the page. This warning message
indicates a failure of the read operation.
%d the starting page number
%d the number of pages to write
User response:
762

Service (VOL)
0x303c6027 0x30680817
0x303c6027 Log read to lsn %z in archive %s
failed. The oldest backup truncate was:
%z
Explanation:
An operation to read the log record of the specified LSN
failed.
0x30483417 ForceEnable: Function unavailable

except in admin mode.
Explanation:
Forceenabling a volume is an operation available only
when the server is in administrative mode.
User response:
Report this problem to your customer support
organization.
User response:
Check the application to make sure that the operation to
force-enable a volume is invoked in administrative mode
only.
Component:
rec
Component:
rec
Severity:
WARNING
Severity:
WARNING
Variables:
v
%s the log sequence number (LSN)
%s the archive stream
%s the LSN for the last backup truncate
0x3044301c Failure to inititalize recovery service

%k
Explanation:
The REC facility was unable to initialize because of the
error specified in the error code.
User response:
The most likely error value for this message is
REC_OPEN_LOG_FAILURE, indicating that it was impossible
to open the log. Ensure that the correct log is specified
is correct and that it can be written to.
Component:
rec
Severity:
TERMINATE
Variables:
%k the error code from BDE
0x30481827 Vol %z is being marked Broken.Repair
will be necessary before it can be
enabled again.
0x30483427 ForceEnableVol: Bypassing the

required restore.
Explanation:
The volume to be force-enabled needs to be restored at
first.
User response:
Restore the volume by using the volume-restoration
procedure.
Component:
rec
Severity:
WARNING
0x30604817 replayFile: The first record required by
this restore could not be found in the
mediaArchive archive. The backup
used is not a valid backup
Explanation:
The log record identified by start LSN for the backup
cannot be found in the log media archive. This indicates
that the given backup is invalid.
User response:
Make sure a valid backup is used for restoring volumes.
Component:
rec
Explanation:
REC has marked the volume as broken. The volume
cannot be enabled before repair work is done.
Severity:
WARNING
User response:
Check for and fix the volume problem. Then certify the
volume before enabling it.
0x30680817 Opening backup file %s for read failed:

%k , system error %d .
Component:
rec
Explanation:
The REC Service failed to open the specified backup
file.
Severity:
WARNING
Variables:
User response:
Check the availability of the backup file.
Component:
rec
763
0x30680c27 0x30681847
Severity:
WARNING
Component:
rec
Variables:
v
%s the filename
Severity:
WARNING
Variables:
%d the system error code
%d the number of bytes to read
%s the filename
0x30680c27 Closing backup file %s failed: %k ,

system error %d .
Explanation:
An operation to close the specified backup file failed.
User response:
Failure to close a file happens rather rarely. Report the
error code to your customer support organization.
0x30681817 Opening backup file %s failed: %k ,

system error %d .
Explanation:
An operation to open the specified backup file failed.
Component:
rec
User response:
Check the availability of the backup file.
Severity:
WARNING
Component:
rec
Variables:
v
%s the filename
Severity:
WARNING
Variables:
%s the filename
0x30681027 Writing %d bytes to backup file %s

failed: %k , system error %d .
Explanation:
An operation to write to the specified backup file failed.
0x30681837 Closing backup file %s failed: %k ,

system error %d .
User response:
Check for I/O problems and make sure no other
processes are manipulating the file.
Explanation:
The REC Service failed to close the specified backup
file.
Component:
rec
User response:
Failure to close a file happens rather rarely. Report the
error code to your customer support organization.
Severity:
WARNING
Variables:
Component:
rec
%d the number of bytes to write
%s the filename.
Severity:
WARNING
Variables:
%s the filename
0x30681427 Read %d bytes at offset %d from

backup file %s failed: %k , system
error %d .
Explanation:
An operation to read from the specified backup file
failed.
User response:
Check for I/O problems and make sure no other
processes are manipulating the file.
764
0x30681847 Flushing backup file %s failed: %k ,

system error %d .
Explanation:
An operation to flush the changes to the specified
backup file failed.
User response:
0x30681857 0x50249836
Component:
rec
Severity:
WARNING
Variables:
v
%s the filename
0x30681857 Removal of backup file %s failed: %k ,

system error %d .
Explanation:
An operation to delete the specified backup file failed.
server. This warning indicates that the information

returned from the server is not compatible with the
client. Ensure that the versions of client and the server
are compatible.
Component:
sfs
Severity:
WARNING
Variables:
v
%x high version information
%x low version information
0x38381c17 Transaction Aborted With Unhandled

Abort String: %s
User response:
Make sure the server has sufficient permissions on the
file. Make sure no other processes are manipulating the
file.
Explanation:
A transaction aborted with an abort string that could not
be handled; that is, it was impossible to convert the
abort string to the corresponding abort reason code.
The abort reason code in this case is
SFS_TRANSACTION_ABORTED.
Component:
rec
Component:
sfs
Severity:
WARNING
Severity:
WARNING
Variables:
Variables:
%s the abort string
%s the filename
0x34180446 area: initialization failed: log enable

failed: %k
Explanation:
The server was unable to initialize the area manager
component because of a problem with the log.
User response:
Verify that the log is specified correctly, that it can be
written to, and that it is not being used by another
process. If the failure code indicates a corrupted log,
restore the log from backups.
Component:
area
Severity:
FATAL
Variables:
%k the failure code returned by the log component
0x38348827 sfs_OpenFile: Unknown SFS Server
Version Detected: 0x %x : %x .
0x3844d817 No Support for Caching at Server Turning off Caching

Explanation:
Based on the error code. An attempt was made to use
server-side caching, which is not supported by the
server. Turn off caching and try again.
Component:
sfs
0x50249836 SFS Server Initialization Failure: Invalid
SFS Server Version.
Explanation:
The server version found in the restart area does not
match the current server.
User response:
Use the appropriate server binary and make sure the
volume is not corrupted.
Component:
sfs_svr
Severity:
FATAL
Explanation:
Based on the error code. The sfs_OpenFile function
attempted to use an unknown version of the SFS
765
0x5024e437 0x502c5417
0x5024e437 Buffer pool exhausted. Restart SFS
using -b option greater than %u
Explanation:
The buffer pool being used to cache recently accessed
portions of volumes has been exhausted. This can
possibly result in excessive SFS disk I/O. Warm start
the SFS server, using the -b option to increase the
buffer pool size from its current size, which is indicated
in the message.
Component:
sfs_svr
Severity:
WARNING
Variables:
%u the current buffer pool size
0x50286417 Changing system idle timeout - old: %d
new: %d
Explanation:
The system idle timeout that serves as the default
timeout value for most of the timeouts in the server has
been changed to the new value. This message is for
information only.
Component:
sfs_svr
Severity:
WARNING
Variables:
v
%d the old system idle timeout
%d the new system idle timeout
0x502c3c26 sfs: Collating Language %s Could

Not Be Found.
Explanation:
When SFS was restarted, the collating language
specified did not match the one stored in the restart
area.
User response:
Do not specify a collating language for the server
restart. The server can find it from the restart data.
Component:
sfs_svr
Severity:
FATAL
Variables:
%s the collating language specified in the server
start command line
766
0x502c5027
Explanation:
See 0x502c5017.
0x502c5037 Setting The Collating Language To
%s Failed.
Explanation:
During a cold start, an attempt to set the collating
language failed. Therefore, any field of type nlsString is
treated as invalid and any comparisons between
nlsString field types can lead to unexpected results.
The setting of the collating language has failed possibly
because the native operating system call setlocale
failed to set the locale for the category LC_COLLATE.
For example, if the environment variable LANG is set to
C, then you can check to see if /usr/lib/locale/C/
LC_COLLATE exists.
Component:
sfs_svr
Severity:
WARNING
Variables:
%s the collating language
0x502c5057 Failed to initialize server: %k
Explanation:
The attempt to initialize the SFS server aborted
because of the reasons indicated by the error status
code.
Component:
sfs_svr
Severity:
WARNING
Variables:
%k the error status code
0x502c5417 Failed To Register Proc Interface: %k .
Explanation:
The SFS server failed to register the basic SFS
interface with the RPC runtime and TRDCE because of
reasons stated in the error code. In such a case, the
SFS server cannot be enabled.
Component:
sfs_svr
Severity:
WARNING
Variables:
0x502c5427 0x50401127
0x502c5427 Failed To Register Fast Proc Interface:
%k .
Explanation:
The SFS server failed to register the fast SFS interface
with the RPC runtime and TRDCE because of reasons
stated in the error code. In such a case, the SFS cannot
be enabled.
Severity:
WARNING
Variables:
0x50401017 Dumping State.
Component:
sfs_svr
Explanation:
A signal was received by the SFS server to dump the
current state of the server.
Severity:
WARNING
Component:
sfs_svr
Variables:
Severity:
WARNING
0x502c5447 Failed To Register Resources Interface:

%k .
0x50401097 SFS Forced Shutdown Signalled.
Explanation:
The SFS server failed to register the SFS
resource-administration interface with the RPC runtime
and TRDCE because of reasons stated in the error
code. In such a case, the SFS server cannot be
enabled.
Explanation:
A terminate signal was received by the SFS server. The
shutdown process is forced, and the exit will not be
clean.
Component:
sfs_svr
Component:
sfs_svr
Severity:
WARNING
Severity:
WARNING
0x504010b7 DANGER Signal Ignored By SFS.
Variables:
0x502c5457 Failed to register FLT interface: %k .
Explanation:
During the initialization process, the SFS server failed to
register the SFS Fast Local Transport interface because
of reasons stated by the error code. The SFS server
cannot be enabled.
Explanation:
This should happen only on AIX platforms. The
SIGDANGER signal received by the SFS server is
ignored.
Component:
sfs_svr
Severity:
WARNING
Component:
sfs_svr
0x50401127 Unexpected Signal Ignored by SFS: %d

.
Severity:
WARNING
Explanation:
An unexpected signal (represented by the number
specified) was received. The SFS server is ignoring this
signal.
Variables:
0x502c5467 Failed To Register Administrative
Interface: %k .
Explanation:
The SFS server failed to register the basic SFS
administrative interface with the RPC runtime and
TRDCE because of reasons stated in the error code. In
such a case, the SFS server cannot be enabled.
Component:
sfs_svr
Severity:
WARNING
Variables:
%d the signal number
Component:
sfs_svr
767
0x50401887 0x54049457
0x50401887
Explanation:
See 0x8c9c2857.
0x54048c37 Call to %s failed with status %k
Explanation:
A call to the specified function failed because of the
error specified in the error status code.
Component:
sfs_admin
Severity:
WARNING
Variables:
v
Specify the target option for tape and disk devices or

choose a different device.
Component:
sfs_admin
Severity:
WARNING
0x540490b7 Option %s ignored for devicetypes
disk and standard out
Explanation:
The option segmentsize was specified for an export
operation but is being ignored because the target is
either a disk or the standard output.
Component:
sfs_admin
Severity:
WARNING
0x54049057 server name too long

Explanation:
The SFS server name specified for an import or export
operation is too long. An SFS server name cannot be
longer than 254 characters. The export operation cannot
be continued.
User response:
Use a shorter SFS server name and try the operation
again.
Component:
sfs_admin
Severity:
WARNING
0x540490c7 segment size must be at least %d

bytes
Explanation:
The minimum segment size for a target of an export
operation is as shown. The segment size specified in
the command line is less than the minimum allowed.
Therefore, the operation has failed.
Component:
sfs_admin
Severity:
WARNING
Variables:
%d the minimum segment size
0x54049097 source file name too long

Explanation:
The SFS filename specified for an export operation is
too long. An SFS filename cannot be longer than 254
characters. The export operation cannot be continued.
User response:
Use a shorter SFS filename and try the operation again.
Component:
sfs_admin
Severity:
WARNING
0x540490a7 Option %s must be supplied for tape
and disk devices
Explanation:
The target option must be specified if the target device
in an export operation is either a disk or a tape. The
previous command did not specify such an option.
User response:
768
0x540490e7 Check point size is not equal to

segment size. Segment size will be
used as check point size.
Explanation:
The checkpoint size is not equal to the segment size to
be used in the export operation. This discrepancy is not
allowed. Therefore, the checkpoint size will be set to the
same value as the segment size.
Component:
sfs_admin
Severity:
WARNING
0x54049457 target name too long
Explanation:
The target SFS filename for an import file operation is
too long. The maximum length for the name of a target
SFS file is 254 characters.
User response:
0x54049467 0x540c20d7
Use a shorter SFS filename and try the operation again.
Component:
sfs_admin
Severity:
WARNING
0x54049467
Explanation:
See 0x54049057.
0x540c20a7 Invalid index field: %s

Explanation:
An index field must also be a record field. The specified
index field name was not found among the list of record
field names.
User response:
Check the record field names and the index field
names.
Component:
sfs_admin
0x54049477 Must provide target for tape and disk

devices and stdin
Severity:
WARNING
Explanation:
For an import file operation, a target SFS filename must
be specified if the source is the standard input or if the
source is the tape or disk device. The operation fails
otherwise.
Variables:
%s the index field name
Component:
sfs_admin
Severity:
WARNING
0x540c1037 Server undefined
Explanation:
SFS was unable to retrieve a server name from either
the command line or from the environment variables.
The sfsadmin commands fail if the server name is not
defined.
User response:
Specify the server with either the -server option on the
command line or the CICS_TK_SFS_SERVER
Component:
sfs_admin
Severity:
WARNING
0x540c2067 excluded key value for sfs_decimal not
implemented yet
Explanation:
The excluded key value cannot be of type sfs_decimal.
User response:
Change the definition of the excluded key.
Component:
sfs_admin
Severity:
WARNING
0x540c20b7 Invalid index field in excluded key: %s

Explanation:
An index field name in the excluded key list must also
belong to the index field list. The specified index field in
the excluded key does not meet this requirement.
User response:
Check the index field names.
Component:
sfs_admin
Severity:
WARNING
Variables:
%s the index field name in the excluded key list
0x540c20c7 Missing value for index field: %s
Explanation:
The index field names in the excluded key must be
accompanied by a field value. For the given
specification, no field value was specified for the given
index field name. Records with this key value will not be
inserted into the index.
Component:
sfs_admin
Severity:
WARNING
Variables:
%s the index field name for which no field value was
specified
0x540c20d7 Invalid unsigned integer value for field:
%s
Explanation:
The value assigned to the unsigned integer field is
invalid.
User response:
769
0x540c20e7 0x540c7827
Check the value assigned to make sure that it is a legal
unsigned integer.
0x540c2117 Key size too large
Component:
sfs_admin
Explanation:
The excluded key size is larger than
SFS_MAX_KEY_SIZE.
Severity:
WARNING
Variables:
%s the field name
0x540c20e7 Invalid float value for field: %s
Explanation:
The field value assigned for the float-type index field in
the excluded key is invalid.
User response:
Check the value assigned to the field and make sure
that it is a legal float value.
Component:
sfs_admin
Severity:
WARNING
Variables:
%s the index field in the excluded key
0x540c20f7 Value too long for field: %s
Explanation:
The string specified as the string-type field value in the
excluded key is longer than the field type description of
the field name.
User response:
Shorten the string specified and try again.
Component:
sfs_admin
User response:
Redefine the excluded key if possible.
Component:
sfs_admin
Severity:
WARNING
0x540c7027 Too large 64 bit integer value for field
%s
Explanation:
The 64-bit integer value specified for the specified field
is too big.
User response:
Specify a lower integer value and try again.
Component:
sfs_admin
Severity:
WARNING
Variables:
%s the field name
0x540c7427 Sign symbol in unsigned 64 bit integer
value for field %s
Explanation:
A symbol for a plus (+) or minus () sign was used in
the value to be assigned to a field of type 64-bit
unsigned integer.
Severity:
WARNING
User response:
Remove the symbol from the value and try the
operation again.
Variables:
%k the index field name in the excluded key
Component:
sfs_admin
0x540c2107 Excluded key value for sfs_timestamp

not implemented yet
Explanation:
The excluded key value cannot be of type
sfs_timestamp. This type has not been implemented.
User response:
Change the definition of the excluded key.
Severity:
WARNING
Variables:
%s the field name
0x540c7827 Invalid value of signed 64 bit integer
value for field %s
Component:
sfs_admin
Explanation:
The value specified for the field of type 64-bit signed
integer is invalid.
Severity:
WARNING
Component:
sfs_admin
Severity:
WARNING
770
0x540c7c47 0x58046417
Variables:
%s the field name
User response:
Change the continue action argument and try the
operation again.
0x540c7c47 Invalid integer value suffix for field: %s
Component:
sfs_admin
Explanation:
The only legal suffix for an integer value is K or k. The
value assigned to the specified field included a different
suffix.
User response:
Change the suffix to either K or k and try again.
Component:
sfs_admin
Severity:
WARNING
Variables:
%s the field name
0x540c8027
Explanation:
See 0x54048c37.
0x540c94f7 unknown device type
Explanation:
An unknown device type was specified in the export
file arguments. The only device types allowed are disk,
file, and tape.
User response:
Change the device type argument and try again.
Component:
sfs_admin
Severity:
WARNING
Severity:
WARNING
0x58043047 reinitialized collating language!
Explanation:
The exported function
ems_InitializeCollatingLanguage was called to
initialize the collating language to the SFS file servers
default settings. If the collating language was previously
set before the function was called, this warning is
generated.
Component:
sfs_ems
Severity:
WARNING
0x58046417 Invalid setting of environment variable
%s : %s
Explanation:
The value set for the specified environment variable is
invalid. It is possible that the values are not set properly.
Check the documentation for the correct setting of the
Component:
sfs_ems
Severity:
WARNING
Variables:
v
%s the environment variable
0x540c9557 unknown lock type
%s the value of the environment variable
Explanation:
An unknown record lock type was specified in the
export file arguments. The valid record lock types are
filelock, recordlock, and nolock.
0x58046417 Invalid setting of environment variable

%s : %s
User response:
Change the lock type and try the operation again.
Component:
sfs_admin
Severity:
WARNING
0x540c95b7 unknown continue action
Explanation:
An unknown continue action was specified in the
export file arguments. The valid continue action types
are resume, force and restart.
Explanation:
The value set for the specified environment variable is
invalid. It is possible that the values are not set properly.
Check the documentation for the correct setting of the
Component:
sfs_ems
Severity:
WARNING
Variables:
v
%s the environment variable
%s the value of the environment variable
771
0x58281427 0x583c2417
0x58281427 It is not necessary or useful to use
islogclose,
Explanation:
All logging in T-ISAM is done automatically by the SFS
server. Therefore, although C-ISAM requires users to
provide a log file and to start and stop logging, they are
not required in the case of SFS. The islogclose
function is provided only for source compatibility.
Component:
sfs_ems
Severity:
WARNING
0x58281437
Explanation:
See 0x58281427.
0x58281837 since the SFS does it for you.
Explanation:
All logging in T-ISAM is done automatically by the SFS
server. Therefore, although ISAM requires users to
provide a log file and to start and stop logging, they are
not required in the case of SFS. The islogopen function
is provided only for source compatibility.
SFS_NON_TRANSACTIONAL_OFD_REQUIRED.
Essentially, the isflush function has no effect and
returns with a success in this case.
Component:
sfs_ems
Severity:
WARNING
0x582c4047 Not setting volume name to NULL!
Explanation:
A NULL volume name was supplied to a
tisam_SetVolume function. This warning probably
occurred because the environment variable
CICS_SFS_TISAM_VOL was not set, and the function
was called with a NULL parameter.
Component:
sfs_ems
Severity:
WARNING
0x583c0c16 Could not add primary ISAM index to
the file!
Explanation:
SFS was unable to add a primary index to the SFS file.
Component:
sfs_ems
User response:
Contact your customer support organization.
Severity:
WARNING
Component:
sfs_ems
0x58281847 Not using log file supplied to

islogopen.
Explanation:
A log file was supplied by the islogopen call. However,
SFS automatically performs logging, and such a file is
not required. Therefore, the supplied log file is not being
used.
Component:
sfs_ems
Severity:
FATAL
0x583c2417 Could not delete file after partial
create!
Explanation:
This warning was generated during an attempt to create
a new ISAM file. The file was only partially created
when an error was encountered. However, it was
impossible to delete the partially created file.
Severity:
WARNING
User response:
Check the TRACE file for more information on why the
file creation failed.
0x58281867
Component:
sfs_ems
Explanation:
See 0x58281837.
0x58282437 isflush is a no-op on transactional
files.
Explanation:
The isflush function is to be called only on
nontransactional files. If the function is called on
transactional files, SFS returns the error code
772
Severity:
WARNING
Variables:
%s the filename
0x583c2427 0x584c0437
0x583c2427
Explanation:
See 0x583c2417.
0x58441527 tisam_Isstart: UnlockCurrent failed: %k
Explanation:
The isstart function was called without the
ISKEEPLOCK mode specified. Therefore, it was
necessary to drop any previously obtained lock.
However, the attempt to release the current lock failed
due to reasons stated in the error code returned.
Component:
sfs_ems
Severity:
WARNING
0x58483517 couldnt move CRP to records new

location (if any)! %k
Explanation:
The current record was updated. However, it was
impossible to move the current record pointer because
of the reasons stated by the error code returned.
Component:
sfs_ems
Severity:
WARNING
Variables:
0x58483ce7 couldnt unlock updated record - %k
Variables:
Explanation:
After the manual mode was used to update a record, it
was impossible to release the lock because of reasons
stated by the error code returned.
0x58481017 Erroneously inserted record could not

be deleted!
Component:
sfs_ems
Explanation:
A record was inserted in error, but it cannot be deleted.
Severity:
WARNING
User response:
Check the output files for more details on the cause of
the error.
Variables:
Component:
sfs_ems
0x58483cf7 couldnt check for duplicates! - %k
Severity:
WARNING
0x584834f7 couldnt check update for duplicates:
%k !
Explanation:
While the current record was being updated, it was
impossible to detect duplicates because of the reasons
specified by the error code returned.
User response:
Check the TRACE file for more details. Also study the
sfs_IsDuplicate functions for reasons why the check for
duplicates can fail.
Explanation:
While the current record was being updated and its
primary key value was used, detection of duplicates was
impossible for reasons stated by the error code. Check
the TRACE file for more details. Also study the
sfs_IsDuplicate functions for reasons why the checking
for duplicates can fail.
Component:
sfs_ems
Severity:
WARNING
Variables:
Component:
sfs_ems
0x584c0437 Unsupported type found in ems key

part!
Severity:
WARNING
Explanation:
While an interface-independent (EMS) keypart was
being converted to an ISAM key part, an unsupported
key part was found in the EMS key part. This situation
results in the error SFS_INTERNAL_ERROR.
Variables:
Component:
sfs_ems
Severity:
WARNING
773
0x5c040437, 0x5c 0x6805b877

0x5c040437, 0x5c TM-XA was unable to prevent
concurrent access to non-thread-aware
RM -- returning %s for ax_reg from RM
%d
Explanation:
While trying to dynamically register an RM with the
Transaction Manager, an attempt was made to acquire
the RM lock. This attempt failed because another thread
is holding this lock. The ax_reg function cannot be
allowed to proceed.
Component:
tmxa
Severity:
WARNING
Variables:
v
v
%s the error message returned by the ax_reg

function
%d the Resource Manager (RM) ID
WARNING
0x6805b827 Illegal Network Domain Name Length
Explanation:
The length of the network domain name is too long.
User response:
Adjust the length of the network domain name and retry
the operation.
Component:
ppc_cpic
Severity:
WARNING
0x6805b837 Illegal Network Domain Name
Explanation:
The network domain name is incorrect.
0x68050c27 Side info data inconsistency detected
User response:
Determine the correct network domain name and retry
the operation.
Explanation:
This is a PPC internal data structure error.
Component:
ppc_cpic
User response:
Try to restart the PPC application.
Severity:
WARNING
Component:
ppc_cpic
Severity:
WARNING
0x6805ac17 Unable to add Partner LU Name
Explanation:
An attempt to configure a partner LU failed.
User response:
Check the remote LU name and the transport
(GWY/TCP/SNA) used for it. Also check if it is already
configured.
Component:
ppc_cpic
Severity:
WARNING
0x6805b017 Unable to delete Partner LU Name
Explanation:
An attempt to delete a partner LU name failed.
User response:
Ensure that the specified partner LU name is configured
in PPC.
Component:
ppc_cpic
Severity:
774
0x6805b867 Executive LU Name should be

non-NULL
Explanation:
The Executive LU name must be specified.
User response:
Determine the Executive LU name and retry the
operation.
Component:
ppc_cpic
Severity:
WARNING
0x6805b877 Network Qualified Executive LU Name
should be less than 18 characters
Explanation:
The Executive LU name must contain fewer than 18
characters.
User response:
Adjust the Executive LU name and retry the operation.
Component:
ppc_cpic
Severity:
WARNING
0x6805b887 0x68241c77
0x6805b887 Executive LU Name not in
<NETWORK_DOMAIN.LUNAME> format
Explanation:
The Executive LU Name must be specified in the
following format: NETWORK_DOMAIN.LUNAME .
User response:
Ensure that the Executive LU name is specified
correctly with a period (.) between the two parts of the
name, and retry the operation.
Component:
ppc_cpic
Severity:
WARNING
0x6805cc17
Explanation:
See 0x68044487.
0x6805cc27
Explanation:
See 0x68044497.
0x6805cc37 TP Name may be too long for
function-shipping to CICS
Explanation:
The supplied TP name is possibly too long.
User response:
Determine the correct TP name and retry the operation.
Component:
ppc_cpic
Severity:
WARNING
0x68241c17 Illegal symDestName
Explanation:
An invalid format was used for the symbolic destination
name.
Provide a valid mode name.

Component:
ppc_cpic
Severity:
WARNING
0x68241c47 Illegal TPName
Explanation:
The supplied TP name is not permitted.
User response:
Provide a valid TP name.
Component:
ppc_cpic
Severity:
WARNING
0x68241c57 Illegal encrypt
Explanation:
The supplied encryption level is not permitted.
User response:
Determine the correct encryption level and retry the
operation.
Component:
ppc_cpic
Severity:
WARNING
0x68241c67 Illegal security
Explanation:
The supplied security level is illegal.
User response:
Determine the correct security level and retry the
operation.
Component:
ppc_cpic
Severity:
WARNING
User response:
Check the documentation for the valid format for the
name.
0x68241c77 Illegal securityUserId
Component:
ppc_cpic
Explanation:
The supplied security user ID is illegal.
Severity:
WARNING
User response:
Determine the correct security user ID and retry the
operation.
0x68241c27 Illegal modeName
Component:
ppc_cpic
Explanation:
The supplied mode name is illegal.
Severity:
WARNING
User response:
775
0x68241c87 0x6c041017
0x68241c87 Illegal securityPassword
Explanation:
The supplied security password is illegal.
User response:
Determine the correct security password and retry the
operation.
Component:
ppc_cpic
Severity:
WARNING
0x68243417 Illegal partnerLuName
Explanation:
The supplied partner LU name is invalid.
User response:
Determine the correct partner LU name and retry the
operation.
Component:
ppc_cpic
Severity:
WARNING
0x68243437 Illegal schedulerEntryName
Explanation:
The supplied scheduler entry name is invalid.
User response:
Determine the correct scheduler entry name and retry
the operation.
Component:
ppc_cpic
Severity:
WARNING
Examine the configuration file for corruption and retry

the operation.
Component:
ppc_cpic
Severity:
WARNING
Variables:
%c the configuration filename
0x68243887 Unable to process entry: %s
Explanation:
It was impossible to process an entry in the side
information file.
User response:
Determine the correct values in the side information file
and retry the operation.
Component:
ppc_cpic
Severity:
WARNING
Variables:
%s the entry that cannot be handled by PPC
0x68243897 Not all entries in the SideInfo file have
been read successfully.
Explanation:
It was impossible to read an entry in the side
information file.
User response:
Examine the side information file for problems.
Component:
ppc_cpic
Severity:
WARNING
0x68243817 unable to open config file

Explanation:
PPC was unable to read the configuration file.
User response:
Ensure that the configuration file exists and has the
correct permissions.
Component:
ppc_cpic
Severity:
WARNING
0x68243847 bad character in config file: %c
Explanation:
The configuration file contains an invalid character or
characters.
User response:
776
0x6c145427
Explanation:
See 0x6c144027.
0x6c041017 ExtractConvId: Incompatible PPC
service: local: %s remote %s
Explanation:
The PPC version of the local participant does not match
the PPC version of the remote participant.
User response:
Run the same PPC version on both participants in the
conversation.
Component:
ppc_tcp
Severity:
0x6c081c17 0x6c180437
WARNING
Variables:
v
%s the PPC version of the local participant
%s the PPC version of the remote participant
0x6c081c17 mismatched received reply tids

Explanation:
The transaction identifier of the PPC reply from the
remote end did not match the local transaction identifier.
User response:
This warning is caused by an internal PPC problem;
restart the PPC application.
Severity:
WARNING
Variables:
%x the unrecognized TRAN status code
0x6c142427
Explanation:
See 0x6c144027.
0x6c144017 socket returned -1 but errno is 0
Explanation:
A socket call on a 32-bit Windows system failed.
Component:
ppc_tcp
User response:
Check the socket documentation to get the error.
Severity:
WARNING
Component:
ppc_tcp
0x6c083c17 SendingCommAddrRequest:rpc_
network_inq_protseqs status:%#x
Explanation:
The RPC call rpc_network_inq_protseqs failed.
User response:
Check the RPC error documentation for the status for
the above call.
Component:
ppc_tcp
Severity:
WARNING
Variables:
%#x the status of the most-recent RPC call
Severity:
WARNING
0x6c144027 socket mode restore problem
Explanation:
A setsockopt call failed.
User response:
Check if there is sufficient memory for the call to
complete.
Component:
ppc_tcp
Severity:
WARNING
0x6c145417 accept returned -1 but errno is 0
0x6c084017 No common TRPC protocol with

remote PPC service.
Explanation:
This host and the remote host do not share a common
communications protocol.
User response:
Ensure that there are matching communications
packages on both machines.
Component:
ppc_tcp
Severity:
WARNING
0x6c087047 Unknown Tran Error: %#x
Explanation:
A transaction error unknown to PPC occurred.
Component:
ppc_tcp
Explanation:
A socket accept call failed.
User response:
Check the socket documentation for possible
responses.
Component:
ppc_tcp
Severity:
WARNING
0x6c180437 duplicate scheduler rpc result area
Explanation:
A second RPC was possibly attempted after the first
attempt was successful.
User response:
Ensure that two RPCs are not made for the same
function.
Component:
777
0x6c180447 0x6c183c17
ppc_tcp
Severity:
WARNING
0x6c180447 missing scheduler rpc result area
Explanation:
The result area assigned before an RPC was scheduled
was not found.
User response:
Restart the PPC application.
Component:
ppc_tcp
Severity:
WARNING
0x6c1804a7 bde_ThreadCreate failed
Explanation:
The thread-create operation failed.
User response:
Check for a shortage of resources, for example,
memory, for creating threads.
Check the documentation for the RPC status code and

take necessary corrective action.
Component:
ppc_tcp
Severity:
WARNING
Variables:
%k the RPC status code
0x6c182817 ppc_tcp_FailedRPC error
Explanation:
An unknown error occurred during function shipping to a
scheduler function.
User response:
Check the scheduler implementation.
Component:
ppc_tcp
Severity:
WARNING
0x6c182c57
Component:
ppc_tcp
Explanation:
See 0x6c184427.
Severity:
WARNING
0x6c183417 trpc_ConsBinding failed
0x6c180c77 bad return from scheduling rpc
Explanation:
An attempt to make an RPC handle transactional failed.
Explanation:
An known error was returned by the remote scheduler.
User response:
Check the PPC scheduler implementation.
Component:
ppc_tcp
Severity:
WARNING
User response:
Check that the necessary transaction initialization has
been made in the PPC application.
Component:
ppc_tcp
Severity:
WARNING
0x6c183c17 rpc_binding_free failed: %k
0x6c181c67
Explanation:
See 0x6c1804a7.
0x6c182057
Explanation:
See 0x6c187c17.
0x6c1820b7 trdce_QualifyName failed: %k
Explanation:
The call to create a fully qualified PPC server name
failed.
User response:
778
Explanation:
The RPC call rpc_binding_free failed.
User response:
Check the documentation for the rpc_binding_free call.
Component:
ppc_tcp
Severity:
WARNING
Variables:
%k the return code for the RPC call
0x6c183c27 0x6c187817
0x6c183c27 trpc_FreeBinding failed
0x6c186817
Explanation:
A call to free a transactional RPC handle failed. This
problem is usually caused by one thread trying to free a
handle while another thread has a call outstanding to
the same handle.
Explanation:
See 0x743c5816.
User response:
This problem can possibly lead to a very small memory
leak, which is rarely serious.
Component:
ppc_tcp
Severity:
WARNING
0x6c184027
Explanation:
See 0x6c183c17.
0x6c186827 uuid_to_string failed: %k

Explanation:
The specified RPC call failed.
User response:
Check the documentation for the RPC status code.
Component:
ppc_tcp
Severity:
WARNING
Variables:
%k the RPC status error code
0x6c186837
0x6c184417
Explanation:
See 0x743c5816.
Explanation:
See 0x6c184427.
0x6c186c17
0x6c184427 rpc_string_free failed: %k

Explanation:
The RPC call rpc_string_free failed.
User response:
Check the documentation for the rpc_string_free call.
Component:
ppc_tcp
Severity:
WARNING
Variables:
%k the status returned by the RPC call
Explanation:
See 0x743c5816.
0x6c186c27
Explanation:
See 0x6c186827.
0x6c186c37
Explanation:
See 0x6c184427.
0x6c187047 bind_Dump failed
0x6c185417
Explanation:
See 0x6c184427.
0x6c186427 bind_Scan failed
Explanation:
The scan operation of the binding list failed.
User response:
Check for any memory shortage.
Component:
ppc_tcp
Severity:
WARNING
Explanation:
An error occurred during dumping of a binding list..
User response:
Check for warnings for other RPC calls that immediately
precede this message.
Component:
ppc_tcp
Severity:
WARNING
0x6c187817
Explanation:
See 0x6c180447.
779
0x6c187c17 0x6c1c0c77
0x6c187c17 tid to binding mapping backout
problem
Explanation:
An error occurred during an attempt to get a binding for
a specified transaction.
User response:
No action is available.
Component:
ppc_tcp
Severity:
WARNING
0x6c1c0847 listen failed: errno: %d

Explanation:
The port did not go into the listen state.
User response:
Determine if the port is being used by another process.
Component:
ppc_tcp
Severity:
WARNING
Variables:
%d the errno specifying the reason why the listen
call failed
0x6c188017
Explanation:
See 0x6c185827.
0x6c188417
0x6c1c08a7 opening socket: errno: %d

Explanation:
It was impossible to open the socket for the reason
specified in errno .
Explanation:
See 0x6c1820b7.
User response:
Determine if the port is in use by another process. Also
ensure there are sufficient file handles available.
0x6c189417
Component:
ppc_tcp
Explanation:
See 0x6c1820b7.
0x6c189817 tid to binding mapping cleanup
problem
Explanation:
An error was returned during cleanup of binding
mapping.
Severity:
WARNING
Variables:
%d the errno value returned by the socket system
calls
0x6c1c08e7 getsockname: errno: %d
Component:
ppc_tcp
Explanation:
The getsockname operation failed.
Severity:
WARNING
User response:
Check the socket documentation for the specified error.
0x6c1c041c ppc_tcpSockInit: gethostbyname error:

%s not found
Explanation:
PPC Services were unable to resolve a specified
computer name to a valid IP address.
User response:
Ensure that the name specified is correct. If it is, ensure
that the DNS service is running properly.
Component:
ppc_tcp
Severity:
TERMINATE
Variables:
%s the computer name PPC is trying to resolve
780
Component:
ppc_tcp
Severity:
WARNING
Variables:
%d the errno value returned by the getsockname
system call.
0x6c1c0c77
Explanation:
See 0x6c1c08a7
0x6c1c0ca7 0x6c1c1417
0x6c1c0ca7 connect: errno: %d
0x6c1c1047 Bogus return from select happened
Explanation:
The connect operation failed.
Explanation:
An invalid value was returned from the select operation.
This message occurs only in debug versions.
User response:
Component:
ppc_tcp
Severity:
WARNING
Variables:
%d the errno returned by the connect call
0x6c1c1017 accept select problem: errno: %d
Explanation:
The select call failed.
User response:
Check the documentation for the select operation for
the specified error.
Component:
ppc_tcp
Severity:
WARNING
Variables:
%d the errno value returned by the select system
calls
0x6c1c1027
Explanation:
See 0x6c1c10a7.
0x6c1c1037 Select failed on socket %d , errno %d .
Explanation:
The select operation on the socket failed.
User response:
Check the documentation for the select operation for
the above error.
Component:
ppc_tcp
Severity:
WARNING
Variables:
v
v
%d the value of the socket on which the select

failed
%d the errno value returned by the select call
Component:
ppc_tcp
Severity:
WARNING
0x6c1c1057 First select returned %d : Second
select returned %d
Explanation:
This message occurs only in a debug version.
Component:
ppc_tcp
Severity:
WARNING
Variables:
v
%d the value returned by the first select

operation
%d the value returned by the second select

operation
0x6c1c10a7 accept: errno: %d

Explanation:
The socket accept call returned an error.
User response:
Check the system message for the errno to diagnose
the problem with the accept call.
Component:
ppc_tcp
Severity:
WARNING
Variables:
%d the errno value set by the accept system call
0x6c1c1417 ppc_tcp_SendBuffer: Unexpected
error( %d ) writing to socket( %d )
Explanation:
An error occurred while a buffer was sent over a socket.
User response:
Check the socket error code.
Component:
ppc_tcp
Severity:
WARNING
Variables:
v
%d the errno value returned by the write

operation
781
0x6c1c1c17 0x6c1c2c67
v
%d the socket number on which the write was

attempted
0x6c1c1c17
Explanation:
See <0x6c1c1037.
Check the documentation for the socket error code.

Component:
ppc_tcp
Severity:
WARNING
Variables:
%d the errno value set by the setsockopt call
0x6c1c1c27
Explanation:
See 0x6c1c1047.
0x6c1c1c37
0x6c1c2c37 getsockopt (keep alive) failed

Explanation:
The previous setsockopt function call failed with the
warning 0x6c1c2c17.
Explanation:
See 0x6c1c1057
User response:
Check the previous setsockopt warnings to determine
the reason for the failure and the appropriate response.
0x6c1c2027 close failed on socket %d , errno %d .
Component:
ppc_tcp
Explanation:
The close operation on the specified socket failed.
User response:
Component:
ppc_tcp
Severity:
WARNING
Variables:
v
%d the socket number on which the close

operation failed
%d the errno value returned by the close

operation
0x6c1c2c17 setsockopt (keep alive) failed: errno:

%d
Explanation:
The socket call setsockopt failed for the reason
specified in the errno value.
Severity:
WARNING
0x6c1c2c47 getsockopt (no delay) failed
Explanation:
The previous setsockopt call failed with the warning
0x6c1c2c27.
User response:
Component:
ppc_tcp
Severity:
WARNING
0x6c1c2c57 binding socket name: errno: %d
Explanation:
An error occurred in binding an address to a socket.
User response:
User response:
Component:
ppc_tcp
Component:
ppc_tcp
Severity:
WARNING
Severity:
WARNING
Variables:
%d the errno value set by the setsockopt call
Variables:
%d the errno value returned by the socket system
calls
0x6c1c2c27 setsockopt (no delay) failed: errno: %d

Explanation:
The socket call setsockopt failed with the error
specified in the errno value.
User response:
782
0x6c1c2c67 setsockopt (no linger) failed: errno: %d

Explanation:
The setsockopt failed for the reason specified in the
errno value.
0x6c1c2c77 0x70185417
User response:
WARNING
Component:
ppc_tcp
%s the string identifying the local LU
%k the error status value
Severity:
WARNING
Variables:
%d the errno value set by the setsockopt system
call
0x6c1c2c77 getsockopt (no linger) failed
Explanation:
The previous setsockopt called failed with the warning
0x6c1c2c67.
User response:
Variables:
0x700c1037
Explanation:
See 0x744c1017.
0x700c9107
Explanation:
See 0x7028b507.
0x700c9117
Explanation:
See 0x7028b517.
Component:
ppc_tcp
0x700c9137
Severity:
WARNING
Explanation:
See 0x7028b537.
0x70087027 listen with unregistered local LU : %s
0x700c9157
Explanation:
The PPC Gateway was unable to listen for the specified
local LU.
Explanation:
See >0x7028b5a7.
User response:
Check the validity of the LU name.
0x700c91d7
Component:
ppc_sna
Severity:
WARNING
Variables:
%s the local LU
0x70087417
Explanation:
See 0x70087027.
0x7008a417 unable to listen for resync tp on local
LU %s : %k
Explanation:
See 0x7028b637.
0x701804b7 illegal incoming SNA TPN: %y
Explanation:
The incoming TPN is invalid.
User response:
Check the SNA configuration.
Component:
ppc_sna
Severity:
WARNING
Variables:
%y the TPN
Explanation:
An error occurred during an attempt to listen on a given
LU.
0x70185417 Registration of LU failed: %k
User response:
Translate the error status code and take necessary
action.
Explanation:
The LU registration has failed for the reason specified in
the status code.
Component:
ppc_sna
User response:
Severity:
Component:
783
0x701c0417 0x701c0517
ppc_sna
Severity:
WARNING
Variables:
%k the error status indicating why the registration
failed
Severity:
WARNING
0x701c04d7 unknown communication system error:
AP_PARAMETER_CHECK, %l x
Explanation:
The SNA communication has returned an error.
0x701c0417 unknown comm sys error:

AP_BACKED_OUT, %l x
User response:
Check the SNA error log for error information
Explanation:
Component:
ppc_sna
User response:
Check the SNA error log for error information.
Severity:
WARNING
Component:
ppc_sna
Variables:
%l x the secondary SNA error
Severity:
WARNING
Variables:
%lx the SNA secondary error
0x701c0427 partner LU alias or mode not found
Explanation:
The value specified for the LU alias was not found.
User response:
Check the configuration for the correct value and retry
the operation.
Component:
ppc_sna
Severity:
WARNING
0x701c0477 comm sys cannot start tp
Explanation:
SNA was unable to start.
User response:
Component:
ppc_sna
Severity:
WARNING
0x701c04f7 unknown comm sys error:

AP_STATE_CHECK, %lx
Explanation:
User response:
Component:
ppc_sna
Severity:
WARNING
Variables:
%l x the SNA secondary error
0x701c0507 unknown comm sys error:
AP_ALLOCATION_ERROR, %lx
Explanation:
User response:
Component:
ppc_sna
Severity:
WARNING
Variables:
%l x the SNA secondary error
0x701c0487 local LU alias not found

Explanation:
The local LU alias was not found.
User response:
Check the configuration for the correct value and retry
the operation.
Component:
ppc_sna
784
0x701c0517 unknown comm sys error: AP_COMM_

SUBSYSTEM_NOT_LOADED, %l x
Explanation:
User response:
Component:
0x701c0537 0x7028b507
ppc_sna
Severity:
WARNING
Variables:
%l x the secondary SNA error
0x701c0537 unknown comm sys error: %x , %l x
Explanation:
User response:
Component:
ppc_sna
Severity:
WARNING
Variables:
v
%x the primary SNA error
%lx the secondary SNA error
0x701c0547 communication system abended

Explanation:
SNA has terminated abnormally.
User response:
Component:
ppc_sna
Severity:
WARNING
0x701c10b7 using <blank> mode
Explanation:
No mode was specified in the allocate request, and no
default mode was specified via the
CICS_PPC_SNA_DEFAULT_MODE. Therefore, the
allocate operation was attempted with a blank (all
spaces) mode.
0x70248837 tpn not deleted: %s

Explanation:
The TPN was not deleted.
User response:
Check the value of the TPN and retry the operation.
Component:
ppc_sna
Severity:
WARNING
Variables:
%s the TPN
0x70249817 sna delete tpn found again: %s
Explanation:
This is caused by an internal PPC mismatch.
Component:
ppc_sna
Severity:
WARNING
Variables:
%s the TPN
0x70249827 sna delete tpn not found: %s
Explanation:
User response:
No action is necessary.
Component:
ppc_sna
Severity:
WARNING
Variables:
%s the TPN
0x70282077
User response:
Ensure that the environment is set so that a reasonable
default mode is used.
Explanation:
See 0x744c1017.
Component:
ppc_sna
0x7028b507 SNA_FAIL: Check sna system status

(lssrc -s sna)
Severity:
WARNING
Explanation:
Check the status of SNA.
0x70248828
User response:
The SNA system has encountered a problem. Use local
procedures to determine the status of SNA.
Explanation:
See 0x70248837.
Component:
ppc_sna
Severity:
785
0x7028b517 0x7028b5a7
WARNING
0x7028b517 SNA_NSACT: Session resource limit
zero
Explanation:
The session resource limit is zero.
User response:
Reconfigure the SNA to change this limit.
Component:
ppc_sna
Severity:
WARNING
0x7028b527 SNA_NSLMT: Session resource limit
encountered
Explanation:
The resource limit for the session has been reached.
User response:
Determine if the value of the resource limit is correct
and if sessions are being freed.
Component:
ppc_sna
Severity:
WARNING
0x7028b537 SNA_NORCB: Conversation resource
limit encountered
Explanation:
The conversation resource limit has been reached.
User response:
Determine if the value of the resource limit is correct
and if sessions are being freed.
Component:
ppc_sna
Severity:
WARNING
0x7028b547 SNA_CSECURE: Security downgrade
required
Explanation:
The supplied security level must be downgraded.
User response:
Determine the correct security level and retry the
operation.
Component:
ppc_sna
Severity:
WARNING
786
0x7028b567 SNA_CSECINV: Security user error

Explanation:
The supplied security user was incorrect.
User response:
Determine the correct security user and retry the
operation.
Component:
ppc_sna
Severity:
WARNING
0x7028b577 SNA_CSECSME: Security same error
Explanation:
A security error occurred while a conversation was
made.
User response:
Component:
ppc_sna
Severity:
WARNING
0x7028b597 (SNA)EPERM: Primary group must be
system
Explanation:
The security users primary group must be system.
User response:
Modify the security users primary group to be system.
Component:
ppc_sna
Severity:
WARNING
0x7028b5a7 (SNA)ENOENT: Check program to
profile name consistency
Explanation:
An error occurred during an attempt to establish a
conversation with the peer.
User response:
Check the SNA documentation for the error.
Component:
ppc_sna
Severity:
WARNING
0x7028b607 0x7040dc27
0x7028b607 (SNA)EACCES: Check profiles
Explanation:
An SNA error occurred while a conversation was being
established.
User response:
Component:
ppc_sna
Severity:
WARNING
0x7028b637 (SNA)EMFILE: Too many open files
Explanation:
The limit for open file descriptors has been reached.
User response:
Determine the limit for open file descriptors and adjust
the value.
Component:
ppc_sna
Severity:
WARNING
0x70344817 Log record contains an unknown item (
%d )
Explanation:
Component:
ppc_sna
Severity:
WARNING
Variables:
%d the number indicating the unknown item
0x7040a817 ppc_snaTran_Prepare:Unexpected
tran-state %s
Explanation:
PPC has encountered an unexpected local transaction
status and is assuming that backout is required.
User response:
Study the transaction status to get more details.
Component:
ppc_sna
Severity:
WARNING
Variables:
%s a value indicating the transaction state
0x7040a826
Explanation:
See 0x7040a817.
0x7040ac17 Unexpected initiatorOutcome in
tran_PrepAtAllSites: %d
Explanation:
PPC has encountered an unexpected outcome and is
assuming that the transaction aborted.
User response:
Study the outcome and take necessary action.
Component:
ppc_sna
Severity:
WARNING
Variables:
%d the transaction outcome at the initiator
0x7040dc17 Transaction record already exists.
0x70406017 Unexpected tranState %s for tid: %#x

for providing outcome
Explanation:
The outcome of a transaction is unknown; an abort is
assumed.
Explanation:
This problem was caused by an internal PPC mismatch
while a gateway log record was being parsed.
User response:
Restart the PPC Gateway server.
User response:
Study the transaction status to get more details.
Component:
ppc_sna
Component:
ppc_sna
Severity:
WARNING
Severity:
WARNING
0x7040dc27 LUWID record already exists.
Variables:
v
%s a value indicating the transaction state
%x the transaction identifier
Explanation:
This problem was caused by an internal PPC mismatch
while a log record was being parsed.
User response:
787
0x7040dc37 0x74048417, 0x74

Component:
ppc_sna
Severity:
WARNING
0x7040dc37
Explanation:
See 0x70344817.
0x7040e017 Log record contains item too large
Explanation:
This problem was caused by an internal PPC mismatch.
User response:
Component:
ppc_sna
Severity:
WARNING
0x70410017
0x73ffffe8
Explanation:
See 0x7028b637.
0x73fffff7
Explanation:
See 0x7028b577.
0x73fffff8
Explanation:
See 0x7028b567.
0x73fffffc
Explanation:
See 0x7028b527.
0x74040837 Gateway Server Name not specifed
Explanation:
The PPC Gateway server name was not specified.
Explanation:
See 0x70406017.
User response:
Determine the name of the PPC Gateway server and
retry the operation.
0x70414c17 No tranRecord found for tid: %#x
Component:
ppc_gwy
Explanation:
This problem was caused by an internal PPC error,
indicating that no information for this transaction can be
found.
User response:
Component:
ppc_sna
Severity:
WARNING
Variables:
%x the transaction identifier
Severity:
WARNING
0x7404bc17
Explanation:
See 0x74055437.
0x7404d817
Explanation:
See 0x74055437.
0x7404dc17
0x70414c27 tran record count error

Explanation:
User response:
Component:
ppc_sna
Severity:
WARNING
Explanation:
See 0x74055437.
0x74048417, 0x74 Host System identifier was not
specified
Explanation:
The host system identifer was not specified.
User response:
Determine the host system identifier and retry the
operation.
Component:
ppc_gwy
788
0x74051c77 0x74053837
Severity:
WARNING
0x74051c77 unable to simultaneously process %s
and %s
Explanation:
Conflicting modification commands were used in
modifying the LU entry.
User response:
Issue separate modification commands for adding and
deleting a TPN.
Component:
ppc_gwy
Severity:
WARNING
Variables:
v
%s addtpn
%s deletetpn
0x74051c87 %s or %s option must be supplied

Explanation:
The addtpn or deletetpn option was not specified in
the ppcadmin command.
User response:
Provide one of these options in the command.
Component:
ppc_gwy
Severity:
WARNING
Variables:
v
%s addtpn
%s deletetpn
0x74051c97 %s not added

Explanation:
The specified TPN could not be added.
User response:
Validate the PPC Gateway server name specified in the
ppcadmin command. If the name is correct, check the
PPC Gateway server trace.
Component:
ppc_gwy
Severity:
WARNING
Variables:
%s the TPN that could not be added
0x74051ca7 %s not deleted

Explanation:
The specified TPN could not be deleted.
User response:
Validate the PPC Gateway server name specified in the
ppcadmin command. If the name is correct, check the
PPC Gateway server trace.
comp:
ppc_gwy
Severity:
WARNING
var:
%s the TPN that was not deleted
0x74052027 Remote LU alias was not specifed
Explanation:
The remote LU alias was not specified.
User response:
Determine the value of the remote LU alias and retry
the operation.
comp:
ppc_gwy
Severity:
WARNING
0x74052427
Explanation:
See 0x74052027.
0x74052827
Explanation:
See 0x74052027.
0x74053837 Invalid Conversation Id: %x
Explanation:
The conversation identifier was not found.
User response:
Check the conversion value specified in the ppcadmin
command.
comp:
ppc_gwy
Severity:
WARNING
var:
%x the invalid conversation ID
789
0x74053847 0x74054c37
0x74053847 Conversation Id was not specified
Explanation:
The conversation ID was not specified.
User response:
Determine the value of the conversation ID and retry the
operation.
comp:
ppc_gwy
Severity:
WARNING
0x74053857 Conversation Id was incorrectly
specified
Explanation:
The supplied value for the conversation ID was invalid.
User response:
Determine the correct value of the conversation ID and
comp:
ppc_gwy
Severity:
WARNING
0x74053c17
Explanation:
See 0x74053c47.
comp:
ppc_gwy
Severity:
WARNING
0x74053c67 LUW sequence number was not
specified or was specified incorrectly
Explanation:
The supplied value for the LUW sequence number was
invalid.
User response:
Determine the correct value of the LUW sequence
number and retry the operation.
comp:
ppc_gwy
Severity:
WARNING
0x74054827 LUW Id was not specified
Explanation:
The LUW ID was not specified.
User response:
Determine the correct value of the LUW ID and retry the
operation.
comp:
ppc_gwy
Severity:
WARNING
0x74053c27
Explanation:
See 0x74053c57.
0x74053c47 LUW name was incorrectly specified
Explanation:
The supplied value for the LUW was invalid.
User response:
Determine the correct value of the LUW and retry the
operation.
0x74054c27 Invalid Transaction Id: %d

Explanation:
the PPC Gateway server did not recognize the
transaction identifier.
User response:
Check the transaction ID specified in the ppcadmin
command.
comp:
ppc_gwy
comp:
ppc_gwy
Severity:
WARNING
Severity:
WARNING
var:
%d the transaction identifier
0x74053c57 LUW instance identifier was not

specified or was specified incorrectly
0x74054c37 TID was not specified
Explanation:
An incorrect LUW instance identifier was specified in the
ppcadmin command.
User response:
Check the identifier.
790
Explanation:
The transaction identifier was not specified.
User response:
Determine the correct value of the TID and retry the
operation.
comp:
0x74055417 0x74057027
ppc_gwy
Severity:
WARNING
0x74055417
Explanation:
See 0x74055437.
0x74055437 Executive LU was not specified
Explanation:
The Executive LU was not specified.
User response:
Specify the correct value of the Executive LU and retry
the operation.
comp:
ppc_gwy
0x74056447
Explanation:
See 0x74055447.
0x74056837
Explanation:
See 0x74055437
0x74056847
Explanation:
See 0x74055447.
0x74056c37 Global TID was not specified
Explanation:
The global transaction identifier was not specified.
Severity:
WARNING
User response:
Determine the correct value of the global TID and retry
the operation.
0x74055447 SNA Partner LU was not specified
comp:
ppc_gwy
Explanation:
The SNA partner LU was not specified.
User response:
Determine the correct value of the SNA partner LU and
comp:
ppc_gwy
Severity:
WARNING
0x74056c47 Invalid Global TID
Explanation:
The global transaction identifier was invalid.
Severity:
WARNING
User response:
Determine the correct value of the global TID and retry
the operation.
0x74055837
comp:
ppc_gwy
Explanation:
See 0x74055437.
0x74055847
Explanation:
See 0x74055447.
0x74056417
Explanation:
See 0x74055437.
0x74056437
Explanation:
See 0x74055437.
Severity:
WARNING
0x74057017
Explanation:
See 0x74057027.
0x74057027 Export file name was not specified.
Unable to replace it.
Explanation:
The export filename was not specified.
User response:
Determine the export filename and retry the operation.
comp:
ppc_gwy
Severity:
WARNING
791
0x74057437 0x74111427
0x74057437
Severity:
WARNING
Explanation:
See 0x74053847.
var:
0x74057447
Explanation:
See 0x74057437.
0x740c0447 Unexpected PPC return Code from
Converse with GWY Server: %#x
Explanation:
comp:
ppc_gwy
Severity:
WARNING
var:
%#x the return value that is not understood
0x74109417 Mismatch between number of tpns: %lu
and tpnCount: %lu
Explanation:
This problem is caused by an internal PPC mismatch.
comp:
ppc_gwy
Severity:
WARNING
%s the local LU
%k the error status
0x7410e417 Cannot alter fully qualified remote LU

Name.
Explanation:
The fully qualified LU name specified in the call does
not match the fully qualified LU name already
associated with the LU alias according the the lookup.
An error in configuration has caused two LUs to try to
use different fully qualified LU names for the same LU
alias.
User response:
Create a remote LU with the same fully qualified LU
name already associated with the LU alias.
comp:
ppc_gwy
Severity:
WARNING
0x7410ec17 partner %s not added [ %k ]
Explanation:
A remote LU could not be added.
comp:
ppc_gwy
Severity:
WARNING
var:
v
%lu a TPN
%lu the TPN count
var:
v
0x7410c817
Explanation:
See 0x70249817.
0x7410c827
Explanation:
See 0x70249827.
0x7410dc47 failed to restore local LU %s from
config: %k
Explanation:
An attempt to restore the PPC Gateway server to a
previous configuration status failed.
User response:
Note the error status and check for any subsequent
errors caused by this problem.
comp:
ppc_gwy
792
%s the partner
%k the status indicating why the partner was not
added
0x74111427 failed to restore LU pair %s from

config
Explanation:
The remote and local LU pair were not restored into the
PPC Gateway server during recovery.
User response:
A possible reason is insufficient memory.
comp:
ppc_gwy
Severity:
WARNING
0x74112817 0x74182d27
0x74112817
Explanation:
See 0x74109417.
%s the string that specifies the key filename from

which the password for the PPC Gateway server
principal is obtained
%k the results of an attempt to store the key

filename
0x74181507
Explanation:
See 0x6c1804a7.
0x74182c96 Unable to decode protection level ( %s

): %k
0x74181527
Explanation:
The protection-level string, from which PPC Gateway
gets the protection-level value, was specified incorrectly.
Explanation:
See 0x6c184487.
0x741820a6
Explanation:
See 0x6c184487.
0x74182c27 Failure during handling of %c switch:
%k
Explanation:
An RPC call failed with the specified error status.
User response:
Check the documentation for the error.
comp:
ppc_gwy
Severity:
WARNING
var:
v
%c the command-line option
%k the RPC error status
0x74182c56
Explanation:
See 0x6c1820b7.
0x74182c86 Unable to set key file ( %s ): %k
Explanation:
the PPC Gateway server was unable to allocate enough
memory for storing the key filename.
User response:
Make sure there is enough memory for the PPC
Gateway server.
comp:
ppc_gwy
Severity:
FATAL
var:
User response:
Check the documentation for the correct protection level
strings.
comp:
ppc_gwy
Severity:
FATAL
var:
v
%s the string that specifies the PPC Gateway

server protection level
%k the result of an attempt to translate the

protection level string to the protection level value
0x74182ca6 Invalid trace specification -- %s

Explanation:
A user has incorrectly specified trace redirection.
User response:
Consult the documentation for the correct specification
of trace redirection.
comp:
ppc_gwy
Severity:
FATAL
var:
%s the string that specifies the redirection of PPC
Gateway trace output
0x74182d27 Option -v required Usage: %s
Explanation:
The option -v is required.
User response:
Determine the value for the parameter and retry the
operation.
comp:
ppc_gwy
Severity:
WARNING
var:
%s the correct usage of the option
793
0x74182db7 0x74344017
0x74182db7 Invalid option specified Usage: %s
Explanation:
An invalid option was specified.
WARNING
var:
v %s the volume number
v
%x the error value
%s the disk name
%x the volume page number
comp:
ppc_gwy
%x the disk page number
Severity:
WARNING
0x74184417 Illegal LU pair: %s
User response:
Determine the value for the parameter and retry the
operation.
var:
%s the correct usage for the option
0x74183027 System crash imminent, machine low
on swap space.
Explanation:
The swap or paging space on the machine is low.
User response:
Determine the cause of the problem and correct it by
stopping nonessential processes or by increasing swap
space.
comp:
ppc_gwy
Severity:
WARNING
0x74183037 unknown signal caught: %lu
Explanation:
the PPC Gateway server caught a signal that it did not
handle.
User response:
Check who sent this signal.
comp:
ppc_gwy
Severity:
WARNING
var:
%lu the number of the signal caught
Explanation:
An internal PPC mismatch occurred. There needs to be
a slash character (/) in the string describing the LU pair.
User response:
No action is required.
comp:
ppc_gwy
Severity:
WARNING
var:
%s the string describing the LU pair
0x74340c37
Explanation:
See 0x6c1804a7.
0x74342526
Explanation:
See 0x743c5816.
0x74342576
Explanation:
See 0x6c1820b7.
0x74342c36
Explanation:
See 0x6c1820b7.
0x74343026
0x74183817 Volume [%z] error [%x] disk [%s]

VolPageNumber %x DiskPageNum %x
Explanation:
See 0x6c1820b7.
Explanation:
the PPC Gateway server received an error upcall from
the TRAN component.
0x74344017
User response:
Check the error received and correct it.
comp:
ppc_gwy
Severity:
794
Explanation:
See 0x744c1017.
0x74344027 0x74502017
0x74344027
0x744c1037 Illegal pip length
Explanation:
See 0x744c1027.
Explanation:
This is caused by an internal PPC problem.
0x743411d7
User response:
No action is necessary; contact your customer support
organization.
Explanation:
See 0x6c183c17.
0x74385026
Explanation:
See 0x14343c5c.
0x743c5816 rpc_if_inq_id failed: %k
Explanation:
The specified RPC call failed.
User response:
Check the RPC documentation for the error status.
comp:
ppc_gwy
Severity:
FATAL
var:
%k the RPC error status
0x744c1017 Unknown security level: %u
Explanation:
An invalid security level has been specified.
User response:
Specify the security level correctly and retry the
operation.
comp:
ppc_gwy
Severity:
WARNING
var:
%u the unrecognized security level
0x744c1027 Illegal luwid length
Explanation:
This is caused by an internal PPC problem.
User response:
No action is necessary; contact your customer support
organization.
comp:
ppc_gwy
Severity:
WARNING
0x74500417 tid to conversation mapping backout
problem
Explanation:
This problem is caused by an internal PPC mismatch.
User response:
comp:
ppc_gwy
Severity:
WARNING
0x74501817 illegal control received in function ship
client
Explanation:
The remote end sent an unexpected control to the local
PPC server.
User response:
Check with the remote application.
comp:
ppc_gwy
Severity:
WARNING
0x74502017 tid to conversation mapping cleanup
problem
Explanation:
This problem is caused by an internal PPC mismatch
User response:
comp:
ppc_gwy
Severity:
WARNING
comp:
ppc_gwy
Severity:
WARNING
795
0x74502417 0x7c184027
0x74502417 synclevel/threadTid inconsistency
detected
Explanation:
An inconsistency was detected between the synclevel
and the transaction level.
%k the Fast Local Transport (FLT) status code

0x78082817 Illegal LU name/length
Explanation:
The supplied LU name or length was invalid.
User response:
Make sure that the synclevel and the transaction level
match in the application.
User response:
Determine the correct LU name or length and retry the
operation.
comp:
ppc_gwy
comp:
ppc_snp
Severity:
WARNING
Severity:
WARNING
0x74502c27
0x78082827 clock was set back, LUWID duplication

possible
Explanation:
See 0x74501817.
0x74540817
Explanation:
Time is used in the creation of LUWIDS. The clock was
set back, introducing the risk of duplicate LUWIDs.
Explanation:
See 0x744c1017.
User response:
Since unknown behavior is possible, there is no specific
user response.
0x74540827
comp:
ppc_snp
Explanation:
See 0x744c1027.
0x74540847 Manager Function Pointer not
initialized for the Generic Trpc
interface
Explanation:
The PPC server application has not registered any
manager function for the specified program.
Severity:
WARNING
0x781c5c26
Explanation:
See 0x7040a817.
0x7c184017 Unknown Local LU Alias %s
User response:
Register a manager function for the program.
Explanation:
An invalid LU alias was specified.
comp:
ppc_gwy
User response:
Determine the correct LU alias and retry the operation.
Severity:
WARNING
comp:
ppc_rsn
0x74581017 Failed to register FLT dispatcher: %k .
Severity:
WARNING
Explanation:
An error was encountered during registration of an FLT
dispatcher.
var:
%s the LU alias
User response:
Translate the FLT error code and take necessary action.
0x7c184027 Invalid configuration for Local LU Alias

%s
comp:
ppc_gwy
Explanation:
An invalid connection type was specified for reaching
the local LU.
Severity:
WARNING
var:
796
User response:
If this error is in response to a ppcadmin command for
XLN, check the local and remote LU names.
0x7c184047 0x84044477
comp:
ppc_rsn
Severity:
WARNING
var:
%s the LU alias
0x7c184047 Invalid Connection Type for Remote LU
Alias %s
Explanation:
An invalid connection type was specified for reaching
the remote LU.
User response:
If this error is in response to a ppcadmin command for
XLN, check the local and remote LU names.
comp:
ppc_rsn
Severity:
WARNING
var:
%s the LU alias
0x7c184057 Unable to add Remote LU Alias %s
Explanation:
It was impossible to add a remote LU alias while
allocating resynchronization.
0x84040c27 Sign symbol for unsigned 64 bit

integer argument < %s >
Explanation:
A specified value (with a K suffix) contained a plus sign
(+) or a minus sign ().
User response:
Specify the argument as an unsigned integer without a
plus or minus symbol.
comp:
cmdline
Severity:
WARNING
var:
%s the argument that specified the invalid value
0x84041027 Invalid integer value suffix for
argument < %s >
Explanation:
A value contains an unsupported scale suffix
User response:
Specify the value properly by using a K or k suffix to
indicate a multiple of 1,000.
comp:
cmdline
Severity:
WARNING
User response:
Translate the error returned by the
ppc_snaRsn_Allocate function to get the error.
var:
%s the argument that specified the invalid value
comp:
ppc_rsn
0x84043c57
Severity:
WARNING
Explanation:
See 0x84050817.
var:
%s the LU alias
0x84044477 Unrecognized enumerated value %s

for argument < %s >
0x84040827 Too large 64 bit integer value for

argument < %s >
Explanation:
An invalid value was specified for an argument that
accepts only certain values.
Explanation:
A specified value (with a K suffix) exceeded the 64-bit
limit.
comp:
cmdline
Severity:
WARNING
var:
%s the argument that specifies the invalid value
User response:
Correct the value to conform to the list of valid values
comp:
cmdline
Severity:
WARNING
var:
v
v
%s the invalid value

%s the argument for which the invalid value was
specified
797
0x84044487 0x84045457
0x84044487 Missing required argument < %s >
Explanation:
The command issued did not specify a required
argument.
User response:
Supply the required argument with the command.
comp:
cmdline
Severity:
WARNING
var:
%s the required argument
0x84044497 Bad value for integer argument < %s >
Explanation:
An invalid integer was specified for an argument that
must be specified as an integer.
WARNING
var:
0x840444f7 Ambiguous enumerated value %s
for argument < %s >
Explanation:
An enumerated value matched more than one valid
value.
User response:
Modify the value to contain enough characters so that it
is uniquely specified.
comp:
cmdline
Severity:
WARNING
var:
v
User response:
Correct the value and retry the command.
comp:
cmdline
Severity:
WARNING
var:
%s the invalid value specified
0x840444a7 Bad value for unsigned integer
argument < %s >
Explanation:
An invalid value was specified for an argument that
must be specified as an unsigned integer.
User response:
comp:
cmdline
Severity:
WARNING
var:
0x840444b7 Bad value for list count < %s >
Explanation:
An invalid integer was specified for an argument that is
a list count.
User response:
comp:
cmdline
Severity:
798

%s the argument for which the ambiguous value
was specified
0x84045017 Default value for argument < %s > is

too long
Explanation:
There are too many default values for an argument.
User response:
This is caused by a coding error. Notify your customer
support organization if this warning occurs.
comp:
cmdline
Severity:
WARNING
var:
%s the offending command
0x84045457 Ambiguous switch %s
Explanation:
The specified option matches more than one valid
command-line option.
User response:
Modify the value to contain enough characters so that it
is uniquely specified.
comp:
cmdline
Severity:
WARNING
var:
%s the command-line option that failed
0x84045467 0x84048847
0x84045467 Unrecognized switch %s
0x84048827 Unrecognized %s : %s
Explanation:
The command-line option does not match any of the
supported command-line options.
Explanation:
An unrecognized command option or value was
specified by the user.
User response:
Consult the command help or the documentation to
obtain the list of valid options and their meanings.
User response:
Consult the usage description or documentation for valid
options and values and correct the command.
comp:
cmdline
comp:
cmdline
Severity:
WARNING
Severity:
WARNING
var:
%s the unrecognized option
var:
0x84045867
Explanation:
See 0x84050817.
0x84048836 Ambiguous argument name: %s
0x84048047 Unrecognized command or key word.

Enter %s %s for help
Explanation:
An invalid command or keyword was supplied.
User response:
Consult the documentation or the command help and
retry.
comp:
cmdline
Severity:
WARNING
var:
%s the program name
0x84048816 Unrecognized argument name: %s
Explanation:
An option in the command line is not recognized. For
example, the -server option is mistyped as -sever.
%s either a string option or an enumerated value,

depending on the type of error that was detected
%s the unrecognized command option or value
Explanation:
The command-line parser cannot match a partially
specified option name with the unique name of the
option. For example, if the -logvolume and -logfile
options are both valid for a command, an option
specified as -log triggers this message.
User response:
Use the full name of the option.
comp:
cmdline
Severity:
FATAL
var:
%s the ambiguous argument.
0x84048847 Ambiguous %s : %s
Explanation:
An ambiguous command option or value was specified
by the user.
comp:
administration command-line interface
User response:
Consult the usage description in the output of the
warning or the documentation for valid options and
values for the command. Correct the input by supplying
sufficient information to eliminate any ambiguity.
Severity:
FATAL
comp:
cmdline
var:
%s the unrecognized argument.
Severity:
WARNING
User response:
Check the command for typing errors.
var:
v
v
%s either a string option or an enumerated value,

depending on the type of error that was detected.
%s the unrecognized command or value
799
0x84050817 0x88084027
0x84050817 Too many arguments
Explanation:
More arguments were specified than are accepted by
the command.
User response:
Remove the extraneous arguments and retry the
command.
comp:
cmdline
Severity:
WARNING
0x88043816 The %s environment variable must be

set to use SFS EXTFH.
Explanation:
When SFS is used as a COBOL external file handler,
the environment variables must be set for the server
name and volume name.
User response:
Set the environment variables.
comp:
extfh
Severity:
FATAL
0x88042416 extfh: Does NOT support NLS filename

mapping.
var:
%s the name of the missing environment variable
Explanation:
The string %NLS% is specified in the filename-mapping
environment variable. EXTFH does not support national
language support (NLS) filename mapping.
0x88043827 EXTFH insert caching disabled due to

environment setting inconsistency.
User response:
Make sure the string is not used.
comp:
extfh
Severity:
FATAL
0x88042c26 extfh: Does NOT support interpretation
of, %c , %c , %c , or %c .
Explanation:
Micro Focus COBOL allows certain characters in
filenames that are stored in filename-mapping
environment variables. These characters tell the file
control to redirect input and output to a file rather than
to use the input and output as a normal COBOL file.
The CICS Toolkit does not support this feature.
User response:
Do not use those characters.
comp:
extfh
Severity:
FATAL
var:
v
%c the unsupported ampersand character (&)
%c the unsupported redirection character (>)
%c the unsupported redirection character (<)
%c the unsupported pipe character (|)
Explanation:
Insert caching is incompatible with other variable
settings. Insert caching cannot be performed if auto
flush is enabled and if duplicate detection is enforced on
all indices and slot choice is set to
FIRST_AVAILABLE_SLOT. If these settings are in force,
then insert caching is turned off. If insert caching is
required, reset the variables listed and try again.
comp:
extfh
Severity:
WARNING
0x88084017 The SFS EXTFH does not support
multiple reel files.
Explanation:
An attempt was made to access multiple reel files that
are supported by COBOL but not by SFS EXTFH. Such
files cannot be handled by SFS EXTFH. A solution is to
convert the file into some other type that can be
accessed by SFS EXTFH.
comp:
extfh
Severity:
WARNING
0x88084027 extfh: May be internal error or a
mismatch between the cobol record
specification and the SFS record
specification
Explanation:
An internal error was encountered during an attempt to
open a file. It is also possible that there was a mismatch
between the COBOL record specifications and the
record specifications of the corresponding SFS file.
800
0x88085837 0x880c1087
comp:
extfh
comp:
extfh
Severity:
WARNING
Severity:
WARNING
0x88085837 extfh: Unlocking a non-Input/Output

file.
0x880c1067 Could not close existing file ( %k )
Explanation:
An attempt was made to unlock all the records in a
line-advancing COBOL file. This call is not allowed. The
function attempting this operation returns a success, but
the records are not unlocked. If the COBOL program
depends on all records being unlocked, subsequent lock
conflicts can result.
Explanation:
During an attempt to open a line-sequential COBOL file
in output mode, an attempt was made to empty the
existing file with the same name. During this process,
an attempt to close this file failed because of the reason
stated in the error code. Check the TRACE file for more
details. The inability to empty an existing file is usually
caused by a lack of proper permissions.
comp:
extfh
comp:
extfh
Severity:
WARNING
Severity:
WARNING
0x88085c17 Caching not enabled for file %s : %k
var:
Explanation:
For the reason detailed by the error code, it was
impossible to turn on caching for the specified file. The
error code is returned by the sfs_InitializeCache
function.
comp:
extfh
Severity:
WARNING
var:
v
%s the file for which caching is not enabled
0x88086c27 extfh: Unable to close report writer file,

%s
Explanation:
It was impossible to close the report-writer file because
of the error specified in the error code that was
returned.
comp:
extfh
Severity:
WARNING
var:
%s the filename of the report writer
0x880c0817 Deleted file still open!
Explanation:
A line-sequential file that was just deleted is still open.
Check the COBOL code and make sure that files are
closed before they are deleted.
0x880c1077 Failed to create file %s : %k

Explanation:
During an attempt to open a line-sequential optional or
required COBOL file, an attempt was made to open the
corresponding UNIX file. This attempt failed because
the file did not exist. When an attempt was made to
create this file, the creation attempt also failed because
of the reason stated in the error code.
comp:
extfh
Severity:
WARNING
var:
v
%s the UNIX filename for the COBOL file
0x880c1087 Failed to open file %s : %k

Explanation:
An attempt to open a line-sequential COBOL file failed
because of reasons stated in the error code. The
corresponding UNIX file does exist, but it could not be
opened. A failure of this kind is typically caused by a
lack of read permissions. Make sure all such conditions
are satisfied and then try again.
comp:
extfh
Severity:
WARNING
var:
v

801
0x880c1097 0x88103857
v
0x880c1097 Failed to get unix file id for file %s : %k

Explanation:
During a file-open operation for a line-sequential
COBOL file, an attempt was made to retrieve the UNIX
file descriptor of the corresponding UNIX file. This
operation failed because of reasons stated in the error
code.
comp:
extfh
Severity:
WARNING
var:
v
0x880c1427 extfh: No CLOSE LOCK support for

line sequential files!
Explanation:
An attempt was made to close a COBOL line-sequential
file in the ems_closeLock lock mode. This mode is not
supported for line-sequential files. Check the COBOL
code to make sure that the line-sequential file is being
closed in proper mode. If the mode being used is
supported by COBOL but not by SFS, you possibly
need to change the mode.
comp:
extfh
Severity:
WARNING
0x880c1457 Failed to close unix file %s : %k
Explanation:
An attempt to close the UNIX file corresponding to the
COBOL line-sequential file failed with the reported
status code.
comp:
extfh
Severity:
WARNING
var:
0x880c1c77 No record locking allowed on line
sequential files!
Explanation:
A line-sequential COBOL file can be read under only
two record-lock modes: ems_noLock and
ems_lockAny. This warning is generated because an
attempt was made to read a line-sequential file in
another record-lock mode.
comp:
extfh
Severity:
WARNING
0x88103847 Cannot delete from closed file: %s
Explanation:
An attempt was made to delete a record from the
specified file, which was already closed. The delete
operation fails when such a request is made.
comp:
extfh
Severity:
WARNING
var:
%s the filename
0x88103857 Cannot delete from a sequential file.
Explanation:
In COBOL, records cannot be deleted from a
line-sequential file.
comp:
extfh
Severity:
WARNING
var:
v
%s the UNIX filename
0x880c1827 Failed to remove unix file: %k

Explanation:
This warning was generated during an attempt to delete
a COBOL line-sequential file. The Base Development
802
Environment (BDE) call to remove the corresponding

UNIX file failed for reasons stated in the returned status
code.
User response:
Fix the COBOL code to make sure that no such attempt
is made.
comp:
extfh
Severity:
WARNING
0x88103c36 0x9c141417
0x88103c36 EXTFH: cannot do random read on
sequential files
Explanation:
The application performed a random read on a
sequential file.
User response:
Use the appropriate file type for random reads.
comp:
extfh
Severity:
FATAL
0x88103c37 Cannot read from closed file: %s
Explanation:
An attempt was made to read a record from a closed
file.
User response:
Correct the COBOL code to make sure that the file is
not closed when it is necessary to read a record from it.
comp:
extfh
Severity:
WARNING
var:
%s the filename
0x88104037 Cannot rewrite from closed file: %s
Explanation:
An attempt was made to update a record belonging to a
previously closed file.
User response:
Fix the COBOL code to reopen the file before an
attempt is made to update the record.
comp:
extfh
Severity:
WARNING
var:
%s the filename
0x88104047 Cannot rewrite to standard input or
standard output.
Explanation:
An attempt was made to update records to the standard
output or the standard input. This is not allowed, and
such an operation fails.
extfh
Severity:
WARNING
0x881044a7 Cannot write to closed file: %s
Explanation:
An attempt was made to write a new record to a file that
was previously closed.
User response:
Fix the COBOL code to reopen the specified file before
attempting this write operation.
comp:
extfh
Severity:
WARNING
var:
%s the filename
0x881048a6
Explanation:
See 0x58481017.
0x882c0447 Changing the primary index key is not
implemented.
Explanation:
An attempt was made to change the primary index key.
This feature has not been implemented in SFS.
User response:
Make appropriate changes to the COBOL code.
comp:
extfh
Severity:
WARNING
0x9c141417 Unable to use read cache. SFS status:
%k
Explanation:
SFS was unable to initialize the READ cache because
of reasons explained in the error code returned by the
sfs_InitializeCache function.
comp:
sfs_ie
Severity:
WARNING
var:
User response:
Fix the COBOL code to make sure this attempt is not
made.
comp:
803
0x9c141427 0xa0080417
0x9c141427
Explanation:
See 0x9c141417.
0x9c1c1017 Unable to use insert cache. SFS
status: %k
Explanation:
SFS was unable to initialize the INSERT cache because
of reasons explained in the error code returned by the
sfs_InitializeCache function.
Check the status code and take action accordingly.

comp:
tkadmin
Severity:
WARNING
var:
%k the RPC failure status code
0xa0042827 Call to admin_ %s failed with status %k
comp:
sfs_ie
Explanation:
The RPC call to the server-side administration function
failed, possibly because of insufficient access authority.
Severity:
WARNING
User response:
Check the status code and take appropriate action.
var:
comp:
tkadmin
0xa0040417 Server name not defined
Severity:
WARNING
Explanation:
The tkadmin command cannot find the server name
that is defined by the -server option or the
CICS_TK_SERVER environment variable.
var:
v
%s the servers admin function name
User response:
Define the server appropriately.
0xa0042c27 Call to %s failed with status %k
comp:
tkadmin
Explanation:
The RPC to the server function failed.
Severity:
WARNING
User response:
Check the status code and take action accordingly.
0xa0040437 Unable to bind to server %s ( %k )
comp:
tkadmin
Explanation:
An attempt to bind to the specified server failed.
Severity:
WARNING
User response:
Examine the error code. Check the server name and
the server state.
var:
comp:
tkadmin
Severity:
WARNING
var:
v
%s the server name
%k the error code
0xa0040817 RPC failure with exception %k

Explanation:
The RPC sent to the server failed. The cause can be a
failure to contact the server, an unauthenticated client,
and so on.
User response:
804
v
v

%k the status code from the individual server
component that supports the function call
0xa0080417 With 0 delay, the rpc will not return.

Explanation:
If the -delay option is zero in the tkadmin stop server
command, the server simply exits without returning the
RPC call. The stop server command can possibly
receive a communications error in this case. This
message is for your information.
comp:
tkadmin
Severity:
WARNING
0xa0082c17 0xa0100417
0xa0082c17 Only TRAN tuning supported so far.
Explanation:
The tkadmin query tuning command can query the
tuning parameters only for the TRAN module so far.
User response:
Do not specify an unsupported module in the command.
comp:
tkadmin
Severity:
WARNING
0xa00c1017 Number of backup files is 0. No
backup performed
Explanation:
A zero argument was supplied for the -nfiles option to
the tkadmin backup lvol command.
User response:
Omit the option in order to use the default or supply an
appropriate value.
comp:
tkadmin
Severity:
WARNING
0xa00c1827 Bad backup file number
Explanation:
The -backupfilenum argument supplied in the tkadmin
restore lvols command is invalid.
User response:
Omit the option to use the default, or supply a valid
argument.
comp:
tkadmin
Severity:
WARNING
0xa00c1c17 Number of lvols is 0. No restore
performed
Explanation:
The number of volumes specified with the tkadmin
restore lvols command was 0 (zero). Thus, no restore
operation is performed.
0xa00c1c37 The %s option is not supported by the

given server.
Explanation:
The tkadmin command was possibly issued to an older
server version that does not support the -noresume
option.
User response:
Check the server version.
comp:
tkadmin
Severity:
WARNING
0xa00c5417 The %s option is not supported by the
given server.
Explanation:
server version that does not support the specified
option.
User response:
Check the server version and avoid using the option.
comp:
tkadmin
Severity:
WARNING
var:
%s The option string
0xa00ca017 Flushing media archives is not
implemented by the given server.
Explanation:
server version that does not implement the tkadmin
flush mediaarchive command.
User response:
Check the server version.
comp:
tkadmin
Severity:
WARNING
0xa0100417 invalid trace component
User response:
Provide the appropriate number of volumes in the
command.
Explanation:
The server component specified in the tkadmin query,
trace, or untrace component command is invalid.
comp:
tkadmin
User response:
Use the tkadmin list components command to obtain
the list of valid server components.
Severity:
WARNING
comp:
tkadmin
805
0xa0100817 0xa0107417
Severity:
WARNING
0xa0100817 invalid trace product
Explanation:
The server product specified in the tkadmin query,
trace, or untrace product command is invalid.
User response:
Use the tkadmin list products command to obtain the
list of valid server products.
comp:
tkadmin
Severity:
WARNING
0xa0105017 The server does not support the %s

command.
Explanation:
Probably because it is an older version, the server does
not support the specified tkadmin trace command.
User response:
Check the server version and use alternative
commands, such as query component, trace
component, or untrace component.
comp:
tkadmin
Severity:
WARNING
var:
%s the unsupported command
0xa0100c17 invalid trace option

Explanation:
An invalid trace option was supplied with one of the
following commands:
v
tkadmin trace product
tkadmin trace component
tkadmin untrace product
tkadmin untrace component
0xa0106417 invalid trace component

Explanation:
The product or component specified in the tkadmin list
trace command is invalid.
User response:
Use the tkadmin list components command to obtain
the list of valid server components.
User response:
Issue the command with a valid option.
comp:
tkadmin
comp:
tkadmin
Severity:
WARNING
Severity:
WARNING
0xa0106427
0xa0103c17 The server does not support the %s

option.
Explanation:
The tkadmin command was issued to an older server
version.
User response:
Check the server version and avoid using unsupported
options.
comp:
tkadmin
Severity:
WARNING
var:
%s the unsupported option in tkadmin dump
ringbuffer command, either -binary or -overwrite.
Explanation:
See 0xa0105017.
0xa0107017
Explanation:
See 0xa0105017
0xa0107417 Only one of %c %s and %c %s may be
specified
Explanation:
In the tkadmin dump ringbuffer command, one can
either specify a -file argument or -destination
argument, but not both.
User response:
Use only one argument.
comp:
tkadmin
Severity:
WARNING
var:
806
0xa0109c17 0xac0c0817
v
%c the option separator, usually - or /
%s the word file
%c the option separator, usually - or /
%s the word dest
0xa01c0417 The -extentsize option is not supported

by the given server.
0xa0109c17
Explanation:
The tkadmin init logvol command was possibly issued
to an older server version that does not support the
-extentsize option.
Explanation:
See 0xa0105017.
User response:
Omit this option and use the default.
0xa010a017
comp:
tkadmin
Explanation:
See 0xa0105017.
Severity:
WARNING
0xa010a817
0xac081c16 No restart data found
Explanation:
See 0xa0105017.
Explanation:
The restart file or files specified in the server command
line is not found or contains invalid information.
0xa0141417 Only one search qualifier permitted.
User response:
Make sure to supply valid restart files.
Explanation:
The tkadmin list tran command allows only one search
option, either -originator, -participant, or -global.
comp:
restart
User response:
Specify no more than one search option.
Severity:
FATAL
comp:
tkadmin
Severity:
WARNING
0xa0181427 Region offset %u on disk %s is too
large
Explanation:
The region size specified in the tkadmin create pvol or
the tkadmin expand pvol command exceeds the disk
size.
0xac083417 Restart device %s not found.

Creating one.
Explanation:
The restart file or device is not found in the servers
warm start. The Restart Service will create one.
User response:
Make sure that the server is restarted with the
appropriate restart files.
comp:
restart
User response:
Calculate the region size carefully.
Severity:
WARNING
comp:
tkadmin
var:
%s the restart device name
Severity:
WARNING
0xac0c0817 restart_Init failed: %k
var:
Explanation:
The restart initialization failed.
%u the disk region offset
%s the disk name
0xa0191417
Explanation:
See 0xa0040437.
User response:
Check the error code and make sure the number of
restart devices and the device names are valid.
comp:
restart
Severity:
WARNING
807
0xb8082016 0xc834281c
var:
%k the error code of the failed restart initialization
0xc834181c Illegal checkpoint interval specified:

%s
0xb8082016 log_Open failure ( %k )
Explanation:
An invalid checkpoint interval is specified.
Explanation:
The tranlog component was unable to open the log due
to the specified error.
User response:
Use a correct checkpoint interval.
User response:
Verify that the log is specified correctly, that it can be
written to and not being used by another process. If the
failure code indicates a corrupted log, restore the log
from backups.
comp:
tranLog
Severity:
FATAL
var:
%k the failure code returned by the log component
0xb8303816
Explanation:
See 0xb8082016.
0xc8340816 Too many server-specific options.
Explanation:
Too many server command-line arguments are
specified.
User response:
Make sure appropriate arguments are specified.
comp:
private
Severity:
FATAL
0xc8340897 %s : Illegal option or missing value for
option
Explanation:
The program does not understand the command issued
by the user. An invalid option was possibly used, or a
value must be provided with the option.
User response:
Check the documentation or the command help to
determine the valid command-line options for this
program.
comp:
private
Severity:
WARNING
var:
%s the program name
808
comp:
private
Severity:
TERMINATE
var:
%s the checkpoint interval specified in the command
line
0xc8341c17 %s : Invalid trace destination specified
-- %s
Explanation:
The user provided an invalid trace specification.
User response:
Consult the documentation for the proper format and
correct the trace specification.
comp:
private
Severity:
WARNING
var:
v
%s the program name
%s the invalid trace specification
0xc834281c Unable to register server with name %s

( %k ).
Explanation:
The server failed to register the specified server name
with CDS.
User response:
Check the CDS directory, the CICS_TK_ROOT
environment variable, and the server name for
correctness.
comp:
private
Severity:
TERMINATE
var:
v
%s the server name
%k the error code returned by RPC service
0xd8580817
0xd8580817 Too many features.
caused by a CICS Toolkit defect, in which case you

need to contact your customer support organization.
Explanation:
The application attempted to register too many
interfaces.
comp:
trdce
User response:
Ensure that there are fewer than 128 RPC interfaces
registered within the server. This warning is possibly
Severity:
WARNING
0x502c5017: Collating Language %s Is different Than One Already

Installed %s...
Component
sfs_svr
Severity
WARNING
Variables
v %s the new collating language that is requested
v %s the collating language that was previously installed
Explanation
During a restart of the SFS server, it was detected that the collating language
requested during the warm start is different from the one that was already installed
during the previous cold start. The new collating language is ignored, and the old
collating language is used.
0x5c102017: tmxa_SetRMIAutoClose is obsolete -- use

tmxa_SetRMIOptions instead.
Component
tmxa
Severity
WARNING
Explanation
The function tmxa_SetRMIAutoClose is obsolete. Use the new function instead.
0x5c1c1457: Applid %d byte%s too long: recovery compromised

Component
tmxa
Severity
WARNING
809
Variables
%d the number of bytes
Explanation
The specified application ID (XID) is longer than the maximum allowable global
transaction ID (GTRID). This error was encountered during an attempt to convert
the given XID to its corresponding GTRID.
0x5c1c1837: %s to XID conversion failed: %k

Component
tmxa
Severity
WARNING
Variables
v %s the GTRID to be converted
v %k the error code
Explanation
An attempt was made to convert a specified GTRID to an XID. This attempt failed
because of reasons stated in the error code.
0x5c2c0c17: Aborting %s
Component
tmxa
Severity
WARNING
Variables
%s the XID of the aborting transaction
Explanation
An attempt was made to end any outstanding associations that possibly are
currently suspended or are migrating. The xa_end_entry call to end the association
failed. This error causes the transaction to abort.
0x5c301017: Recording heuristic damage for %s

Component
tmxa
810
Severity
WARNING
Variables
%s the XID of the transaction
Explanation
An XA rollback operation was attempted. This operation failed, but the Resource
Manager did not inform the Transaction Manager (TM) of any specific reason. It can
be assumed that the XA rollback operation had an unknown outcome. A heuristic
damage has been recorded.
0x5c380c17: Rollback assumed for %s

Component
tmxa
Severity
WARNING
Variables
Explanation
While a transaction was being committed with the one-phase commit protocol, a call
to the xa_commit_entry function failed. It is assumed that the transaction has been
rolled back.
0x5c381017: Rollback assumed for %s

Component
tmxa
Severity
WARNING
Variables
%s the XID of transaction
Explanation
During an attempt to commit a transaction with the two-phase commit protocol, the
xa_prepare_entry function failed. It is assumed that the transaction will be rolled
back.
811
0x5c3c0c17: Heuristic outcome performed on %s.

Component
tmxa
Severity
WARNING
Variables
%s the XID of transaction
Explanation
A attempt was made to roll back the given XID using the xa_rollback_entry call.
The RM returned a heuristic outcome. Subsequently, the RM was asked to forget
this heuristically completed transaction branch.
0x5c3c0c27: Recovery of %z may be compromised.

Component
tmxa
Severity
WARNING
Variables
Explanation
A call to the xa_rollback_entry function did not return XA_OK. Instead, it returned a
value of type XA_RB*, which possibly indicates an error in processing the
xa_rollback_entry function. It is possible that recovery has been damaged
because of this error.
0x5c3c1c17: Terminating recovery scan for RM %d.

Component
tmxa
Severity
WARNING
Variables
%d the Resource Manager ID
812
Explanation
The Transaction Manager called the xa_recover_entry function to obtain a list of
prepared transaction branches from the Resource Manager. Because the call failed,
the recovery scan is being terminated for this RM.
0x5c401417: Recording heuristic damage for %s

Component
tmxa
Severity
WARNING
Variables
%s the XID for the transaction
Explanation
An attempt was made to commit a transaction by using the xa_commit_entry. This
call failed, indicating some catastrophic event at the Resource Manager. Because it
is possible that other Resource Managers have successfully committed their work
on behalf of this transaction branch, a heuristic damage warning is being recorded.
0x5c541017: Truncating transaction identifier when constructing XID -recovery compromised.

Component
tmxa
Severity
WARNING
Explanation
While an XID was being constructed from a specified TID and nesting model, it was
detected that the transaction identifier was too long and must be truncated.
Recovery has possibly been damaged.
0x5c541027: Truncating application identifier when constructing XID -recovery compromised.

Component
tmxa
Severity
WARNING
813
Explanation
While an XID was being constructed, it was found that the application identifier was
longer than the maximum branch qualifier size. It was necessary to truncate the
application ID. Recovery has possibly been damaged.
0x64048c67: PPC Service Not Initialized

Component
ppc
Severity
WARNING
Explanation
PPC Services have not been initialized.
User response
Initialize PPC Services by using the ppc_init function.
0x640c6417: unknown/unexpected transaction state %d returned by

tran-service for tid: %#x
Component
ppc
Severity
WARNING
Variables
v %d the transaction state
v %#x the transaction ID
Explanation
PPC does not recognize this transaction state.
User response
Check the transaction status and take necessary corrective action.
0x640c7017: Inserting Conversation with a NULL Attributes Structure

Component
ppc
Severity
WARNING
814
Explanation
An internal PPC mismatch has occurred.
User response
No action is needed.
0x640c8017: duplicate sna conv found

Component
ppc
Severity
WARNING
Explanation
A duplicate sna conversation has been found.
User response
Check the sna configuration for duplicate entries.
0x64e41c17: new exec LU (%s) listed through old admin interface: %u

Component
ppc
Severity
WARNING
Variables
v %s the LU
v %u PPC RPC protocol selector
Explanation
The administrative software being used is compatible with an earlier version of the
PPC Gateway server and cannot display the specified data it has received.
User response
Upgrade the administrative client to a later version compatible with the PPC
Gateway software.
0x64e42017:
Explanation
See 0x64e41c17.
815
0x64e45017:
Explanation
See 0x64e49027.
0x64e46c27: trdce_BindingImport FAILED (%k)

Component
ppc
Severity
WARNING
Variables
%k the status code returned by the most-recent RPC call
Explanation
A call to get the RPC handle for the specified server from CDS failed.
User response
Check the RPC error code and correct the problem or get the correct server name.
0x64e49027: New RPC failed (%k). Trying old RPC...

Component
ppc
Severity
WARNING
Variables
%k the PPC status of the latest PPC Gateway command
Explanation
The latest RPC returned with an error message of command not supported. The
PPC Gateway is probably an earlier version, and an RPC for the earlier version of
PPC Gateway was attempted.
User response
Use compatible versions of ppcadmin and PPC Gateway software.
0x64e49037: failed to chmod file %s, errno: %d

Component
ppc
816
Severity
WARNING
Variables
v %s the name of the file
v %d the errno value set by the chmod system call
Explanation
The chmod operation failed for the reason provided in errno.
User response
Check the permission and authorization of the user.
0x64e49427:
Explanation
See 0x64e49027.
0x64e49437: Invalid remoteluProfilePriority (%lu). Exported profile will

have default priority value.
Component
ppc
Severity
WARNING
Explanation
An invalid profile priority was specified for the remote LU.
User response
Correct the profile priority of the remote LU entry.
0x64e49817:
Explanation
See 0x64e49027.
0x64e49c17:
Explanation
See 0x64e49027.
0x68044487: Illegal sync level: %i

Component
ppc_cpic
817
Severity
WARNING
Variables
%i a number indicating the sync level
Explanation
The sync level is invalid for the operation.
User response
Adjust the sync level value and retry the operation.
0x68044497: Illegal security level: %i

Component
ppc_cpic
Severity
WARNING
Variables
%i a number indicating the security level
Explanation
The security level is invalid for the operation.
User response
Adjust the security level and retry the operation.
0x680448b7:
Explanation
See 0x68044487.
0x680448c7:
Explanation
See 0x68044497.
0x6804f8c7: Unable to initialize ppc services

Component
ppc_cpic
818
Severity
WARNING
Explanation
The ppc initialization call has failed because ppc is already initialized.
Status codes
The CICS Toolkit functions return status codes, for example,
SFS_NO_SUCH_FILE_SYSTEM. Applications should check the status returned by
functions and display a message if the status does not indicate success.
Each status code corresponds to a message. The following is a typical example:
ENC-sfs-0300: Operation requires a unique index
A code can be represented in four different forms:

v A status string, such as ENC-sfs-0051
v A decimal number, such as 1997905971
v A hexadecimal number, such as (0x7715a033)
v A C constant, such as SFS_NO_SUCH_FILE_SYSTEM
The CICS Toolkit provides the translateError command to translate status codes
into their associated messages. The following command example displays the
status string, message string, C constant, and hexadecimal number associated with
the status string ENC-sfs-0051:
% translateError ENC-sfs-0051
ENC-sfs-0051: Unknown file system [SFS_NO_SUCH_FILE_SYSTEM] (0x7715a033)
You can pass the translateError command any of the forms of the status code
(except the message string), and the command returns the other forms, including
the message string, as in the following examples:
% translateError SFS_NO_SUCH_FILE_SYSTEM
SFS_NO_SUCH_FILE_SYSTEM: ENC-sfs-0051: Unknown file system name. (0x7715a033)
% translateError 0x7715a033
0x7715a033: ENC-sfs-0051: Unknown file system name. [SFS_NO_SUCH_FILE_SYSTEM]
% translateError ENC-sfs-0051
Unknown file system name. [SFS_NO_SUCH_FILE_SYSTEM] (0x7715a033)
% translateError 1997905971
ENC-sfs-0051: Unknown file system name. [SFS_NO_SUCH_FILE_SYSTEM] (0x7715a033)
Note: The NLSPATH and LANG environment variables must be set for the
message string to be displayed in the output.
On Windows systems, you can use individual commands or the WinTrace graphical
user interface (GUI) to translate error codes and trace IDs.
ENC-adm-0002
v Status String: ENC-adm-0002
v Status Code: ADMIN_SERVER_NOT_IN_ADMIN_MODE
v Hexadecimal ID: 0x70084002
v Message: Server not in admin mode
819
ENC-adm-0003
v Status Code: ADMIN_CANNOT_OPEN_TRACE_FILE
v Message: Cannot open trace destination
ENC-adm-0004
v Status Code: ADMIN_INVALID_COMPONENT
v Message: Invalid component
ENC-adm-0005
v Status Code: ADMIN_ALREADY_INITIALIZED
v Message: Admin function has already been initialized
ENC-adm-0006
v Status Code: ADMIN_TRACE_DESTINATION_NOT_INITIALIZED
v Message: Trace destination uninitialized
ENC-adm-0007
v Status Code: ADMIN_INVALID_PARAMETER
v Message: Invalid parameter
ENC-adm-0008
v Status Code: ADMIN_NOT_SUPPORTED
v Message: Call not supported in this application
ENC-adm-0009
v Status Code: ADMIN_OUT_OF_MEMORY
v Message: Unable to allocate memory
ENC-adm-0010
v Status Code: ADMIN_NO_CALLBACK_REGISTERED
v Hexadecimal ID: 0x7008400a
v Message: No such generic callback registered
ENC-adm-0011
v Status Code: ADMIN_SERVER_IS_PRIMARY
820
v Hexadecimal ID: 0x7008400b

v Message: Server is already functioning as primary
ENC-alf-0001
v
v
v
v
Status String: ENC-alf-0001

Status Code: ALF_VALTYPE_MISMATCH
Hexadecimal ID: 0x701bd001
Message: Attribute value type mismatch.
ENC-alf-0002
v Status String: ENC-alf-0002
v Status Code: ALF_ATTRIBUTE_DOES_NOT_EXIST
v Hexadecimal ID: 0x701bd002
v Message: Named attribute does not exist.
ENC-alf-0003
v Status Code: ALF_ATTRIBUTE_NOT_A_LIST
v Message: Named attribute is not a list.
ENC-alf-0004
v Status Code: ALF_ATTRIBUTE_NOT_A_SET
v Message: Named attribute is not a set.
ENC-alf-0005
v Status Code: ALF_INDEX_INVALID
v Message: Index out of range.
ENC-alf-0006
v Status Code: ALF_VALUE_NOT_PRESENT
v Message: No element exists with specified value.
ENC-alf-0007
v Status Code: ALF_VALUE_ALREADY_PRESENT
v Message: Set already contains an element with specified value.
ENC-are-0001
v Status String: ENC-are-0001
v Status Code: AREA_MEMORY_LIMIT
v Hexadecimal ID: 0x702ac001
v Message: Out of memory
ENC-are-0002
821
v
v
v
v
Status String: ENC-are-0002

Status Code: AREA_AUTH_FAILURE
Hexadecimal ID: 0x702ac002
Message: Authorization failure
ENC-are-0003
v Status Code: AREA_COMMUNICATION_ERROR
v Message: Communication error
ENC-are-0004
v Status Code: AREA_INVALID_SERVER_NAME
v Message: Invalid server name
ENC-are-0005
v Status Code: AREA_UNKNOWN_SERVER_NAME
v Message: Unknown server name
ENC-are-0006
v Status Code: AREA_BINDING_FAILURE
v Message: Binding failure
ENC-are-0007
v Status Code: AREA_INTERNAL_ERROR
v Message: Internal error
ENC-are-0008
v Status Code: AREA_UNIMPLEMENTED
v Message: Not implemented
ENC-are-0009
v Status Code: AREA_INVALID_AREA_ID
v Message: Invalid area ID
ENC-are-0010
v Status Code: AREA_NO_SUCH_PAGE
v Hexadecimal ID: 0x702ac00a
822
v Message: No such page

ENC-are-0011
v Status Code: AREA_INVALID_RESTART_KEY
v Hexadecimal ID: 0x702ac00b
v Message: Invalid restart key
ENC-are-0012
v Status Code: AREA_RESTART_KEY_NOT_FOUND
v Hexadecimal ID: 0x702ac00c
v Message: Restart key not found
ENC-are-0013
v Status Code: AREA_INVALID_PAGE_SIZE
v Hexadecimal ID: 0x702ac00d
v Message: Invalid page size
ENC-are-0014
v Status Code: AREA_VOLUME_IO_ERROR
v Hexadecimal ID: 0x702ac00e
v Message: Volume IO error
ENC-are-0015
v Status Code: AREA_INVALID_CALLING_MODE
v Hexadecimal ID: 0x702ac00f
v Message: Invalid calling mode
ENC-bde-0001
v Status String: ENC-bde-0001
v Status Code: BDE_ALARM_INVALID_TIME
v Hexadecimal ID: 0x706bc001
v Message: An invalid alarm time has been specified.
ENC-bde-0002
v Status Code: BDE_EXTENT_TOO_SMALL
v Message: The given extent was too small to be useful.
ENC-bde-0003
v Status Code: BDE_FAILURE
v Message: General Failure.
ENC-bde-0004
823
v Status Code: BDE_FILE_DOES_NOT_EXIST

v Message: The file does not exist and could not be created.
ENC-bde-0005
v Status Code: BDE_FILE_EXISTS
v Message: The modes BDE_FILE_CREATE and BDE_FILE_EXCL were
specified but the file already exists.
ENC-bde-0006
v Status Code: BDE_FILE_HANDLE_LIMIT
v Message: The limit on the maximum number of open files has been
reached.
ENC-bde-0007
v Status Code: BDE_HAS_ASYNC_IO
v Message: The platform provides true asynchronous file I/O.
ENC-bde-0008
v Status Code: BDE_IN_PROGRESS
v Message: The I/O operation has not yet completed.
ENC-bde-0009
v Status Code: BDE_INTERNAL_MEMORY_LIMIT
v Message: There is insufficient internal memory to satisfy the
request.
ENC-bde-0010
v Status Code: BDE_INVALID_ACCESS
v Hexadecimal ID: 0x706bc00a
v Message: The file protection prohibits access to or creation of
the file.
ENC-bde-0011
v Status Code: BDE_INVALID_ALARM
v Hexadecimal ID: 0x706bc00b
v Message: An invalid alarm id (bde_alarm_t) was specified.
ENC-bde-0012
824
v Status Code: BDE_INVALID_ALIGNMENT

v Hexadecimal ID: 0x706bc00c
v Message: The given alignment is not an integer power of two.
ENC-bde-0013
v Status Code: BDE_INVALID_ARGUMENT
v Hexadecimal ID: 0x706bc00d
v Message: One of the given arguments was invalid.
ENC-bde-0014
v Status Code: BDE_INVALID_FILE_HANDLE
v Hexadecimal ID: 0x706bc00e
v Message: An invalid file handle (bde_file_t) was specified.
ENC-bde-0015
v Status Code: BDE_INVALID_HANDLER_TYPE
v Hexadecimal ID: 0x706bc00f
v Message: An invalid handler type (bde_handlerType_t) was
specified.
ENC-bde-0016
v Status Code: BDE_INVALID_OFFSET
v Message: An invalid offset was specified.
ENC-bde-0017
v Status Code: BDE_INVALID_OPTION
v Message: An invalid option was specified.
ENC-bde-0018
v Status Code: BDE_INVALID_PATH
v Message: The specified file does not exist.
v Explanation: The specified path is invalid. This usually indicates that the
path to a server executable has been incorrectly specified.
ENC-bde-0019
v Status Code: BDE_INVALID_PRIORITY
v Message: An invalid priority value was specified.
v Explanation: The requested priority could not be set when starting a
process.
ENC-bde-0020
825
v
v
v
v
Status String: ENC-bde-0020

Status Code: BDE_INVALID_PROC_HANDLE
Hexadecimal ID: 0x706bc014
Message: An invalid process handle (bde_process_t) was specified.
ENC-bde-0021
v Status Code: BDE_INVALID_REQUEST
v Message: The file was not opened in a mode that would permit the
attempted operation.
ENC-bde-0022
v Status Code: BDE_INVALID_SIGNAL
v Message: The list contains a signal value that is invalid on the
current platform.
ENC-bde-0023
v Status Code: BDE_INVALID_SIZE
v Message: The specified size was too large.
ENC-bde-0024
v Status Code: BDE_INVALID_THREAD
v Message: An invalid thread identifier (bde_thread_t) was
specified.
ENC-bde-0025
v Status Code: BDE_MEMORY_LIMIT
v Message: There is insufficient memory to satisfy the request.
ENC-bde-0026
v Status Code: BDE_NO_ASYNC_IO
v Message: The platform does not provide true asynchronous file
I/O.
ENC-bde-0027
v Status Code: BDE_NO_LIMIT_SET
v Message: No maximum limit has been set for the specified
resource.
826
ENC-bde-0028
v Status Code: BDE_OP_NOT_SUPPORTED
v Message: This operation is not supported for the current BDE
implementation.
ENC-bde-0029
v
v
v
v

Status Code: BDE_PROC_HANDLE_LIMIT
Hexadecimal ID: 0x706bc01d
Message: Insufficient system resources available to start a child
process.
ENC-bde-0030
v Status Code: BDE_PROC_INFO_INVALID_FILE
v Message: One of the file descriptors in the process info
structure is invalid.
ENC-bde-0031
v Status Code: BDE_PROC_NO_CHILDREN
v Message: No child processes are currently executing.
ENC-bde-0032
v Status Code: BDE_PROC_WAITER_EXISTS
v Message: A waiter already exists for the specified process.
ENC-bde-0033
v Status Code: BDE_SHORT_IO
v Message: The requested file operation only partially completed.
ENC-bde-0034
v Status Code: BDE_SHORT_READ
v Message: The requested read operation only partially completed.
ENC-bde-0035
v Status Code: BDE_SHORT_WRITE
v Message: The requested write operation only partially completed.
ENC-bde-0036
827
v
v
v
v

Status Code: BDE_SYSTEM_ERROR
Hexadecimal ID: 0x706bc024
Message: An unexpected operating system error was encountered.
ENC-bde-0037
v Status Code: BDE_THREAD_LIMIT
v Message: The limit on the maximum number of concurrent threads
has been reached.
ENC-bde-0038
v Status Code: BDE_TRANSIENT_ERROR
v Message: A system error occurred that may not occur if the call
is retried.
ENC-bde-0039
v Status Code: BDE_INVALID_USER
v Message: An invalid user name or password was specified.
ENC-bde-0040
v Status Code: BDE_INVALID_GROUP
v Message: An invalid group was specified.
ENC-bde-0041
v Status Code: BDE_INVALID_PGRP
v Message: An invalid process group was specified.
ENC-bde-0042
v Status Code: BDE_INVALID_DIRECTORY
v Message: An invalid directory was specified.
ENC-bde-0043
v Status Code: BDE_PROC_HAS_BEEN_JOINED
v Message: Attempt to join with a process that has already been
joined with.
ENC-bde-0044
828
v Status Code: BDE_PROC_STILL_ACTIVE

v Message: Attempt to terminate the handle of a still running
process.
ENC-bde-0045
v Status Code: BDE_PROC_HAS_EXITED
v Hexadecimal ID: 0x706bc02d
v Message: A reference was made to an invalid or defunct process.
ENC-bde-0046
v Status Code: BDE_LOCK_NOT_GRANTED
v Message: Requested lock is not granted.
ENC-bde-0047
v Status Code: BDE_INVALID_LOCK_TYPE
v Message: Lock type supplied is invalid.
ENC-bde-0048
v Status Code: BDE_BAD_FILE_HANDLE_FOR_LOCKING
v Message: File handle unsuitable for lock type.
ENC-bde-0049
v Status Code: BDE_LOAD_LOAD_OBJECT_FAILED
v Message: Could not load specified shared object.
ENC-bde-0050
v Status Code: BDE_LOAD_INVALID_MODE
v Message: Attempt to load object using invalid mode.
ENC-bde-0051
v Status Code: BDE_LOAD_NOT_SHARED_OBJECT
v Message: Attempt to load an object which is not shared.
ENC-bde-0052
v Status Code: BDE_LOAD_OBJECT_NOT_FOUND
829
v Message: Specified object/library file was not found. Check the

path and file name.
ENC-bde-0053
v Status Code: BDE_LOAD_UNRESOLVED_SYMBOLS
v Message: All the symbols could not be resolved.
ENC-bde-0054
v Status Code: BDE_LOAD_UNLOAD_OBJECT_FAILED
v Message: Could not unload object using the specified object
handle.
ENC-bde-0055
v Status Code: BDE_LOAD_INVALID_HANDLE
v Message: The handle specified is either invalid or it does not
point to module that is still open.
ENC-bde-0056
v Status Code: BDE_LOAD_NO_SYMBOL
v Message: The specified symbol was not found.
ENC-enc-1025
v Status String: ENC-enc-1025
v Status Code: ENCINA_STS_CATOPEN_FAILED
v Hexadecimal ID: 0x71b0a401
v Message: Failed to open the required catalog file.
ENC-enc-1026
v Status Code: ENCINA_STS_UNKNOWN_FACILITY
v Message: The supplied facility was unknown.
ENC-enc-1027
v
v
v
v
Status String: ENC-enc-1027

Status Code: ENCINA_STS_UNKNOWN_ERROR
Hexadecimal ID: 0x71b0a403
Message: The supplied error was not found or the catalog file was
badly formatted.
ENC-enc-1028
v Status Code: ENCINA_STS_BUFFER_TOO_SMALL
830
v Message: The supplied buffer was too small to perform the

conversion.
ENC-enc-1029
v Status Code: ENCINA_ABORT_FACILITY_INVALID_TID
v Message: The transaction identifier was invalid.
ENC-enc-1030
v Status Code: ENCINA_ABORT_FACILITY_INVALID_PTR
v Message: A pointer passed as an argument was invalid.
ENC-enc-1031
v Status Code: ENCINA_ABORT_FACILITY_NOT_SET
v Message: The abort reason was not set.
ENC-enc-1032
v Status Code: ENCINA_ABORT_FACILITY_NO_FORMATTER
v Message: No matching formatter for uuid.
ENC-enc-1041
v Status Code: ENCINA_STS_BAD_FORMAT
v Message: The status string was badly formatted.
ENC-epm-0001
v Status String: ENC-epm-0001
v Status Code: EPM_NO_SUCH_RESOURCE
v Hexadecimal ID: 0x71b64001
v Message: The requested resource name is not registered.
ENC-epm-0002
v Status Code: EPM_ARRAY_TOO_SMALL
v Message: The array provided for retrieving results is not large
enough.
ENC-epm-0003
v Status Code: EPM_RPC_FAILURE
v Message: An RPC failure occurred during the retrieval.
831
ENC-lck-0001
v Status String: ENC-lck-0001
v Status Code: LOCK_NOT_GRANTED
v Hexadecimal ID: 0x7451a001
v Message: The lock was not granted
ENC-lck-0002
v Status Code: LOCK_NOT_HELD
v Message: A lock is not held in the specified mode
ENC-lck-0003
v Status Code: LOCK_TRAN_INVALID
v Message: Transaction invalid
ENC-lck-0004
v Status Code: LOCK_TRAN_ABORTED
v Message: Transaction aborted
ENC-lck-0005
v Status Code: LOCK_NOT_INIT
v Message: The lock service has not been initialized
ENC-lck-0006
v Status Code: LOCK_ALREADY_INIT
v Message: The lock service is already initialized
ENC-lck-0007
v Status Code: LOCK_MODE_INVALID
v Message: A lock mode was invalid
ENC-lck-0008
v Status Code: LOCK_NAME_INVALID
v Message: The lock name was invalid
ENC-lck-0009
v Status Code: LOCK_SPACE_INVALID
832

v Message: The lock name space was invalid
ENC-lck-0010
v
v
v
v
Status String: ENC-lck-0010

Status Code: LOCK_WAIT_MODE_INVALID
Hexadecimal ID: 0x7451a00a
Message: The lock wait mode was invalid
ENC-lck-0011
v Status Code: LOCK_DURATION_INVALID
v Hexadecimal ID: 0x7451a00b
v Message: The lock duration was invalid
ENC-lck-0012
v Status Code: LOCK_RESTART_DATA_INVALID
v Hexadecimal ID: 0x7451a00c
v Message: The restart data was invalid
ENC-lck-0013
v Status Code: LOCK_PTR_INVALID
v Hexadecimal ID: 0x7451a00d
v Message: A data pointer was invalid
ENC-lck-0014
v Status Code: LOCK_CALLBACK_INVALID
v Hexadecimal ID: 0x7451a00e
v Message: The conflict callback and argument were invalid
ENC-lck-0015
v Status Code: LOCK_TIMED_OUT
v Hexadecimal ID: 0x7451a00f
v Message: Timeout expired while waiting for a lock
ENC-lck-0016
v Status Code: LOCK_DURATION_CONFLICT
v Message: New lock duration conflicts with current value
ENC-lck-0017
v Status Code: LOCK_TRAN_NOT_IN_PAIR
v Message: Transaction does not belong to compatibility pair
ENC-lck-0018
833
v
v
v
v
Status String: ENC-lck-0018

Status Code: LOCK_TOP_LEVEL_TRAN_REQUIRED
Hexadecimal ID: 0x7451a012
Message: Transaction is not a top-level tran as required
ENC-lck-0019
v Status Code: LOCK_TRAN_ALREADY_IN_PAIR
v Message: Transaction already belongs to a compatibility pair
ENC-lck-0020
v Status Code: LOCK_TRAN_RELATED
v Message: Transactions are already related - cannot be made
compatible
ENC-log-0002
v Status String: ENC-log-0002
v Status Code: LOG_INVALID_ARCHIVE
v Hexadecimal ID: 0x746f6002
v Message: Invalid archive id
ENC-log-0020
v Status Code: LOG_CHAIN_LIST_TOO_LONG
v Message: Too many chains for a record or cursor
ENC-log-0021
v Status Code: LOG_CHAINID_TOO_LONG
v Message: Chain ID size exceeds limit
ENC-log-0022
v Status Code: LOG_CHAIN_SIZE_TOO_SMALL
v Message: One or more chain ID buffers too small
ENC-log-0023
v
v
v
v
Status String: ENC-log-0023

Status Code: LOG_CHAIN_LIST_TOO_SMALL
Hexadecimal ID: 0x746f6017
Message: Insufficient chain identifier buffers
ENC-log-0026
v Status Code: LOG_INVALID_CURSOR
834
v Hexadecimal ID: 0x746f601a

v Message: Invalid cursor
ENC-log-0027
v
v
v
v

Status Code: LOG_END_OF_CURSOR
Hexadecimal ID: 0x746f601b
Message: No more records in the cursor
ENC-log-0070
v Status Code: LOG_INVALID_FILTER
v Message: Filter was null, empty, or too long
ENC-log-0126
v Status Code: LOG_LOGFILE_ALREADY_EXISTS
v Hexadecimal ID: 0x746f607e
v Message: Log file already exists
ENC-log-0127
v Status Code: LOG_NO_SUCH_LOGFILE
v Hexadecimal ID: 0x746f607f
v Message: No such log file
ENC-log-0128
v Status Code: LOG_INVALID_LOGFILE_NAME
v Message: Invalid log file name
ENC-log-0129
v Status Code: LOG_INVALID_HANDLE
v Message: Invalid log file handle
ENC-log-0135
v Status Code: LOG_INVALID_LSN
v Message: Invalid LSN
ENC-log-0160
v Status Code: LOG_RECORD_TOO_LARGE
v Hexadecimal ID: 0x746f60a0
v Message: Record size exceeds limit or buffer size
ENC-log-0191
835
v
v
v
v

Status Code: LOG_NEW_RP_TOO_HIGH
Hexadecimal ID: 0x746f60bf
Message: RP is greater than current archive head
ENC-log-0192
v Status Code: LOG_NEW_RP_TOO_LOW
v Hexadecimal ID: 0x746f60c0
v Message: RP is less than current restart point
ENC-log-0210
v Status Code: LOG_INVALID_TAIL_INCLUDE
v Hexadecimal ID: 0x746f60d2
v Message: Invalid tail
ENC-log-0211
v Status Code: LOG_NEW_TAIL_TOO_HIGH
v Message: New archive tail is greater than archive head
ENC-log-0212
v Status Code: LOG_NEW_TAIL_TOO_LOW
v Message: New archive tail is less than current tail
ENC-log-0234
v Status Code: LOG_BUFFER_TOO_SMALL
v Hexadecimal ID: 0x746f60ea
v Message: Buffer too small to contain the requested data
ENC-log-0250
v Status Code: LOG_NO_SPACE
v Hexadecimal ID: 0x746f60fa
v Message: Insufficient free space in log
ENC-log-0251
v Status Code: LOG_INVALID_WRITE_MODE
v Hexadecimal ID: 0x746f60fb
v Message: Invalid write mode
ENC-log-0256
v Status Code: LOG_VOL_ERROR
836
v Message: Error encountered while operating on a log volume.

v Explanation: An error occurred while reading from or writing to a log
volume. This typically indicates that the Volume Service (VOL)
encountered a hard I/O error.
v User Response: Default VOL tracing can be used to identify the
underlying error.
ENC-log-0257
v Status Code: LOG_VOL_TOO_SMALL
v Message: Log volume is too small for the implementation.
ENC-log-0268
v Status Code: LOG_ARCHIVE_ALREADY_EXISTS
v Hexadecimal ID: 0x746f610c
v Message: Log file archive already exists
ENC-log-0269
v Status Code: LOG_NO_SUCH_ARCHIVE
v Hexadecimal ID: 0x746f610d
v Message: Log file archive could not be found
ENC-log-0274
v Status Code: LOG_ARCHIVE_NOT_OFFLINE
v Message: Operation is only valid on offline archives
ENC-log-0275
v Status Code: LOG_ARCHIVE_NOT_ONLINE
v Message: Operation is only valid on online archives
ENC-log-0279
v Status Code: LOG_INVALID_VOLUME
v Message: Invalid volume name specified
ENC-log-0281
v Status Code: LOG_INVALID_ARCH_DEV
v Message: Invalid archive device name specified
ENC-log-0282
v Status Code: LOG_INVALID_ARCH_FILE
837
v Hexadecimal ID: 0x746f611a

v Message: Invalid archive file name specified
ENC-log-0285
v
v
v
v

Status Code: LOG_BUFFER_POOL_TOO_SMALL
Hexadecimal ID: 0x746f611d
Message: The configured buffer pool for the volume is too small
ENC-log-0286
v Status Code: LOG_ARCH_DEV_ERROR
v Hexadecimal ID: 0x746f611e
v Message: Error encountered while operating on the archive device
ENC-log-0287
v Status Code: LOG_INVALID_ARCHIVE_TYPE
v Hexadecimal ID: 0x746f611f
v Message: Invalid archive type specified
ENC-log-0290
v Status Code: LOG_CORRUPT_ARCH_FILE
v Message: An archive file is corrupted.
ENC-log-0291
v Status Code: LOG_VOLUME_NOT_READY
v Message: Log volume is not ready
ENC-log-0292
v Status Code: LOG_NOT_SUPPORTED
v Message: Specified option is not supported by the implementation.
ENC-log-0293
v Status Code: LOG_ARCH_FILE_NOT_ACCESSIBLE
v Message: Archive device file needed to complete a read is not
accessible.
ENC-log-0294
v Status Code: LOG_INVALID_EXTENT_SIZE
v Message: Invalid extent size specified
838
ENC-log-0295
v Status Code: LOG_NOT_LOG_VOLUME
v Message: The volume does not appear to be a log volume
ENC-log-0296
v Status Code: LOG_INVALID_CURSOR_ATTRIBUTE
v Message: Undefined cursor attribute specified.
ENC-pge-0002
v Status String: ENC-pge-0002
v Status Code: PAGE_NO_NEXT_PAGE
v Hexadecimal ID: 0x75eb4002
v Message: Next page not exist
ENC-pge-0003
v Status Code: PAGE_NO_PREV_PAGE
v Message: Previous page not exist
ENC-pge-0004
v Status Code: PAGE_INSUFFICIENT_SPACE
v Message: Not enough space on page
ENC-pge-0005
v Status Code: PAGE_PAGES_UNCHANGED
v Message: Pages not changed
ENC-pge-0006
v Status Code: PAGE_PAGES_MERGED
v Message: Pages merged
ENC-pge-0007
v Status Code: PAGE_PAGES_BALANCED
v Message: Pages balanced
ENC-pge-0008
v Status Code: PAGE_INVALID_OFFSET
839

v Message: Invalid data offset
ENC-pge-0009
v
v
v
v
Status String: ENC-pge-0009

Status Code: PAGE_EMPTY_AFTER_OP
Hexadecimal ID: 0x75eb4009
Message: Page empty after operation
ENC-pge-0010
v Status Code: PAGE_INSUFFICIENT_BUFFER
v Hexadecimal ID: 0x75eb400a
v Message: User provided buffer too short
ENC-ppc-0001
v Status String: ENC-ppc-0001
v Status Code: PPC_ALLOC_BUSY
v Message: Allocation failure, all sessions busy
ENC-ppc-0002
v Status Code: PPC_ALLOC_CONV_TYPE_MISMATCH
v Message: Allocation failure, conversation type mismatch
ENC-ppc-0003
v Status Code: PPC_ALLOC_FAILURE_NO_RETRY
v Message: Allocation failure, no retry
ENC-ppc-0004
v Status Code: PPC_ALLOC_FAILURE_RETRY
v Message: Allocation failure, retry
ENC-ppc-0005
v Status Code: PPC_ALLOC_PIP_ILLEGAL
v Message: Allocation failure, PIP data not supported
ENC-ppc-0006
v Status Code: PPC_ALLOC_PIP_MAL_FORMED
v Message: Allocation failure, PIP data incorrectly specified
ENC-ppc-0007
840
v
v
v
v
Status String: ENC-ppc-0007

Status Code: PPC_ALLOC_SCHEDULER_FAILURE
Message: Allocation failure, transaction scheduler failure
ENC-ppc-0008
v Status Code: PPC_ALLOC_SECURITY_VIOLATION
v Message: Allocation failure, security violation
ENC-ppc-0009
v Status Code: PPC_ALLOC_SYNCLEVEL_NO_LU_SUPP
v Message: Allocation failure, LU does not support synclevel
ENC-ppc-0010
v Status Code: PPC_ALLOC_SYNCLEVEL_NO_PGM_SUPP
v Hexadecimal ID: 0x7601a00a
v Message: Allocation failure, TPN does not support synclevel
ENC-ppc-0011
v Status Code: PPC_ALLOC_TPN_UNAVL_NO_RETRY
v Message: Allocation failure, TPN unavailable, no retry
ENC-ppc-0012
v Status Code: PPC_ALLOC_TPN_UNAVL_RETRY
v Message: Allocation failure, TPN unavailable, retry
ENC-ppc-0013
v Status Code: PPC_ALLOC_UNKNOWN_TPN
v Message: Allocation failure, TPN unknown
ENC-ppc-0014
v Status Code: PPC_ALREADY_INITIALIZED
v Message: PPC Service already initialized
ENC-ppc-0015
v Status Code: PPC_BACKED_OUT
841
v Message: Backed out

ENC-ppc-0016
v
v
v
v
Status Code: PPC_CONN_FAILURE_NO_RETRY

Message: Connection failure, no retry
Explanation: The allocate request failed because PPC was unable to
establish a SNA connection. This is commonly caused by a mismatch
between the prof_name entry of the side_info profile and the
local_lu_name of the local_lu_lu6.2 profile.
v User Response: Refer to the appropriate SNA configuration

documentation for more information.
ENC-ppc-0017
v Status Code: PPC_CONN_FAILURE_RETRY
v Message: Connection failure, retry
ENC-ppc-0018
v Status Code: PPC_DEALLOC_ABEND
v Message: Deallocated, abend
ENC-ppc-0019
v Status Code: PPC_DEALLOC_ABEND_PROG
v Message: Deallocated, program abend
ENC-ppc-0020
v Status Code: PPC_DEALLOC_ABEND_SVC
v Message: Deallocated, service program abend
ENC-ppc-0021
v Status Code: PPC_DEALLOC_ABEND_TIMER
v Message: Deallocated, timer abend
ENC-ppc-0022
v Status Code: PPC_DEALLOC_NORMAL
v Message: Deallocated, normally
ENC-ppc-0023
842
v Status Code: PPC_SUCCESS_HEURISTIC_MIXED

v Message: Commited_Heuristic mixed
ENC-ppc-0024
v Status Code: PPC_BACKED_OUT_HEURISTIC_MIXED
v Message: BackedOut_Heuristic mixed
ENC-ppc-0025
v Status Code: PPC_FAILURE
v Message: Failure
ENC-ppc-0026
v Status Code: PPC_INVALID_CONVERSATION_TYPE
v Message: Invalid conversation type
ENC-ppc-0027
v Status Code: PPC_INVALID_CONN_TYPE
v Message: Invalid connection type
ENC-ppc-0028
v Status Code: PPC_INVALID_CONVID
v Message: Invalid conversation identifier
ENC-ppc-0029
v Status Code: PPC_INVALID_DEALLOCATE_TYPE
v Message: Invalid deallocate type
ENC-ppc-0030
v Status Code: PPC_INVALID_ENCRYPT_LEVEL
v Message: Invalid encryption level
ENC-ppc-0031
v Status Code: PPC_INVALID_GDS_DATA
v Message: Invalid GDS data
843
ENC-ppc-0032
v Status Code: PPC_INVALID_LUNAME
v Message: Invalid LU name or Fully Qualified LU Name
ENC-ppc-0033
v Status Code: PPC_INVALID_MODE_NAME
v Message: Invalid mode name
ENC-ppc-0034
v Status Code: PPC_INVALID_OPTION
v Message: Invalid option
ENC-ppc-0035
v Status Code: PPC_INVALID_PREPARE
v Message: Invalid prepare
ENC-ppc-0036
v Status Code: PPC_INVALID_SECURITY_LEVEL
v Message: Invalid security level
ENC-ppc-0037
v Status Code: PPC_INVALID_SYNCLEVEL
v Message: Invalid synclevel
ENC-ppc-0038
v Status Code: PPC_INVALID_TID
v Message: Invalid transaction identifier
ENC-ppc-0039
v Status Code: PPC_INVALID_TPN
v Message: Invalid TPN
ENC-ppc-0040
v Status Code: PPC_INVALID_TS_DATA
844

v Message: Invalid transaction scheduler data
ENC-ppc-0041
v
v
v
v

Status Code: PPC_INVALID_USERID
Message: Invalid user identifier
ENC-ppc-0042
v Status Code: PPC_LISTENER_FAILURE
v Message: PPC listener failure
ENC-ppc-0043
v Status Code: PPC_NESTING_NOT_SUPPORTED
v Message: Nested transactions not supported
ENC-ppc-0044
v Status Code: PPC_NOT_DEALLOCATED
v Message: Conversation not deallocated
ENC-ppc-0045
v Status Code: PPC_NOT_INITIALIZED
v Message: PPC Service not initialized
ENC-ppc-0046
v Status Code: PPC_NOT_SNA_SYSID
v Message: Not a SNA system identifier
ENC-ppc-0047
v Status Code: PPC_PROG_ERROR_NO_TRUNC
v Message: Program error, not truncated
ENC-ppc-0048
v Status Code: PPC_PROG_ERROR_PURGING
v Message: Program error, purging
ENC-ppc-0049
845
v
v
v
v

Status Code: PPC_PROG_ERROR_TRUNC
Message: Program error, truncated
ENC-ppc-0050
v Status Code: PPC_STATE_ERROR
v Message: State error
ENC-ppc-0051
v Status Code: PPC_SVC_ERROR_NO_TRUNC
v Message: Service program error, not truncated
ENC-ppc-0052
v Status Code: PPC_SVC_ERROR_PURGING
v Message: Service program error, purging
ENC-ppc-0053
v Status Code: PPC_SVC_ERROR_TRUNC
v Message: Service program error, truncated
ENC-ppc-0054
v Status Code: PPC_SYSID_EXISTS
v Message: System identifier exists
ENC-ppc-0055
v Status Code: PPC_TPN_FAILURE
v Message: SNA TPNs not configured
ENC-ppc-0056
v Status Code: PPC_UNKNOWN_SYSID
v Message: Unknown system identifier
ENC-ppc-0057
v Status Code: PPC_CONNECTION_NAME_EXISTS
846
v Message: Connection name already exists

ENC-ppc-0058
v Status Code: PPC_PROTOCOL_UNAVAILABLE
v Message: Specified protocol uninitialized or unavailable
ENC-ppc-0059
v Status Code: PPC_GWY_NO_SYSID_MAP
v Message: No Map for SysId at Gateway
ENC-ppc-0060
v Status Code: PPC_GWY_SYSID_MAP_EXISTS
v Message: Map for SysId exists at Gateway
ENC-ppc-0061
v Status Code: PPC_UNKNOWN_SCHEDULING_FUNCTION
v Message: Unknown Scheduling Function
ENC-ppc-0062
v Status Code: PPC_SCHEDULING_FUNCTION_EXISTS
v Message: Scheduling function already exists
ENC-ppc-0063
v Status Code: PPC_UNKNOWN_GWY_SYSID
v Message: SysId unknown at Gateway
ENC-ppc-0066
v Status Code: PPC_GWY_INVALID_WAIT_TIME
v Message: Invalid wait time
ENC-ppc-0067
v Status Code: PPC_GWY_UNAUTHORISED_CLIENT
v Message: Client Unauthorised at Gateway
ENC-ppc-0068
847
v Status Code: PPC_GWY_ALREADY_INITIALIZED

v Message: Gateway Already Initialized
ENC-ppc-0069
v Status Code: PPC_ASYNC_ABORTED_TRANSACTION
v Message: Transaction aborted asynchronously
ENC-ppc-0070
v Status Code: PPC_THREAD_NOT_CERTIFIED
v Message: Thread not certified
ENC-ppc-0071
v Status Code: PPC_UNSUPPORTED
v Message: Unsupported function
ENC-ppc-0072
v Status Code: PPC_TIMED_OUT
v Message: Allocate timed out
ENC-ppc-0073
v Status Code: PPC_CONN_FAILURE_NO_RETRY_BO_REQUIRED
v Message: Connection failure, no retry BO
ENC-ppc-0074
v Status Code: PPC_CONN_FAILURE_RETRY_BO_REQUIRED
v Message: Connection failure, retry BO
ENC-ppc-0075
v Status Code: PPC_DEALLOC_ABEND_BO_REQUIRED
v Message: Deallocated, abend BO
ENC-ppc-0076
v Status Code: PPC_DEALLOC_ABEND_PROG_BO_REQUIRED
v Message: Deallocated, program abend BO
848
ENC-ppc-0077
v Status Code: PPC_DEALLOC_ABEND_SVC_BO_REQUIRED
v Message: Deallocated, service program abend BO
ENC-ppc-0078
v Status Code: PPC_DEALLOC_ABEND_TIMER_BO_REQUIRED
v Message: Deallocated, timer abend BO
ENC-ppc-0079
v Status Code: PPC_FAILURE_BO_REQUIRED
v Message: Failure BO
ENC-ppc-0080
v Status Code: PPC_SUCCESS_OUTCOME_PENDING
v Message: Success - outcome pending
ENC-ppc-0081
v Status Code: PPC_BACKED_OUT_OUTCOME_PENDING
v Message: Backed out - outcome pending
ENC-ppc-0082
v Status Code: PPC_UNSUCCESSFUL
v Message: Nothing to return
ENC-ppc-0083
v Status Code: PPC_UNKNOWN_GWY_SERVER
v Message: Gateway Server unknown in Name Service
ENC-ppc-0084
v Status Code: PPC_INTERFACE_NOT_SUPPORTED
v Message: Specified interface is not supported
ENC-ppc-0085
v Status Code: PPC_GWY_INVALID_LU_NAME
849

v Message: Invalid LU Name specified at Gateway
ENC-ppc-0086
v
v
v
v

Status Code: PPC_NOT_SNA_LUNAME
Message: Not a valid SNA LU Name
ENC-ppc-0087
v Status Code: PPC_LUNAME_EXISTS
v Message: LU Name exists
ENC-ppc-0088
v Status Code: PPC_UNKNOWN_LUNAME
v Message: Unknown LU Name
ENC-ppc-0089
v Status Code: PPC_COMMAND_UNNECESSARY
v Message: Unnecessary Gateway configuration command
ENC-ppc-0090
v Status Code: PPC_GWY_COMMAND_NOT_SUPPORTED
v Message: Unsupported Gateway command
ENC-ppc-0091
v Status Code: PPC_GWY_UNKNOWN_LUW
v Message: Unknown LUW at the Gateway Server
ENC-ppc-0092
v Status Code: PPC_GWY_UNKNOWN_TID
v Message: Unknown transaction at the Gateway Server
ENC-ppc-0093
v Status Code: PPC_GWY_NO_PENDING_RESYNC
v Message: No pending resynchronizations
ENC-ppc-0094
850
v
v
v
v

Status Code: PPC_UNKNOWN_TPNAME
Hexadecimal ID: 0x7601a05e
Message: TP name is not registered - command failed
ENC-ppc-0095
v Status Code: PPC_TPNAME_EXISTS
v Message: TP name has already been registered - command failed
ENC-ppc-0096
v Status Code: PPC_TPNAME_ERROR
v Message: TP name malformed - command failed
ENC-ppc-0097
v Status Code: PPC_GWY_RSN_PROTOCOL_VIOLATION
v Message: Protocol violation during resynchronization
ENC-ppc-0098
v Status Code: PPC_GWY_RSN_LOG_NAME_MISMATCH
v Message: Log Identifier Name mismatch during resynchronization
ENC-ppc-0099
v Status Code: PPC_GWY_RSN_ABNORMAL_XLN_REPLY
v Message: Abnormal reply in Exchange Log Names from partner during
resynchronization
ENC-ppc-0100
v Status Code: PPC_GWY_CNF_EXPORT_FILE_ERROR
v Message: Gateway configuration export file cannot be created or
over written
ENC-ppc-0101
v Status Code: PPC_DPL_ABEND_SET
v Message: CICS DPL abend code set
ENC-ppc-0102
v Status Code: PPC_DPL_CCODE_SET
851

v Message: CICS DPL condition code set
ENC-ppc-0103
v
v
v
v

Status Code: PPC_DPL_BAD_MESSAGE
Message: Malformed DPL message received from CICS
ENC-rec-0001
v Status String: ENC-rec-0001
v Status Code: REC_ACTIVE_SLAVES
v Hexadecimal ID: 0x76ae2001
v Message: Ending operation with active slaves.
ENC-rec-0002
v Status Code: REC_BUFFERS_EXHAUSTED
v Message: All buffers in the buffer pool are pinned.
ENC-rec-0003
v Status Code: REC_DISK_IO_ERROR
v Message: Disk read/write Error.
ENC-rec-0004
v Status Code: REC_INIT_NOTIFICATION_NOT_ACKED
v Message: Init notification for a pinned page not acknowledged.
ENC-rec-0005
v Status Code: REC_INVALID_OP_ID
v Message: Invalid operation identifier.
ENC-rec-0006
v Status Code: REC_INVALID_VOL_ACCESS
v Message: Invalid volume access.
ENC-rec-0007
v Status Code: REC_INVALID_PAGE_RANGE
v Message: Invalid page range.
ENC-rec-0008
852
v
v
v
v
Status String: ENC-rec-0008

Status Code: REC_NO_INIT_NOTIFICATION
Hexadecimal ID: 0x76ae2008
Message: Attempt to acknowledge a non-existent init notification.
ENC-rec-0009
v Status Code: REC_PAGE_NOT_PINNED
v Message: Page not pinned.
ENC-rec-0010
v Status Code: REC_PAGE_PINNED
v Hexadecimal ID: 0x76ae200a
v Message: Page is pinned.
ENC-rec-0011
v Status Code: REC_PAGE_UPDATE_NOT_BEGUN
v Hexadecimal ID: 0x76ae200b
v Message: Attempt to update a page without beginning a page
update.
ENC-rec-0012
v Status Code: REC_PAGE_UPDATE_NOT_FINISHED
v Hexadecimal ID: 0x76ae200c
v Message: Attempt to unpin a page without ending a page update.
ENC-rec-0013
v Status Code: REC_TID_NOT_ACTIVE
v Hexadecimal ID: 0x76ae200d
v Message: Specified transaction is not active.
ENC-rec-0014
v Status Code: REC_BACKUP_IN_PROGRESS
v Hexadecimal ID: 0x76ae200e
v Message: Backup of specified volume is in progress.
ENC-rec-0015
v
v
v
v

Status Code: REC_INVALID_BACKUP_TYPE
Hexadecimal ID: 0x76ae200f
Message: Invalid backup type.
ENC-rec-0016
v Status Code: REC_SEGMENT_IN_PROGRESS
853

v Message: Backup segment in progress.
ENC-rec-0017
v
v
v
v

Status Code: REC_BAD_BACKUP_FILE
Hexadecimal ID: 0x76ae2011
Message: Bad backup file.
ENC-rec-0018
v Status Code: REC_INVALID_BACKUP_ID
v Message: Invalid backup identifier.
ENC-rec-0019
v Status Code: REC_NO_ACTIVE_BACKUP
v Message: No active backup.
ENC-rec-0020
v Status Code: REC_NO_ACTIVE_SEGMENT
v Message: Attempt to end a backup segment without a corresponding
begin segment.
ENC-rec-0021
v Status Code: REC_NO_BACKUP
v Message: Specified volume has no backup.
ENC-rec-0022
v Status Code: REC_MEDIA_ARCHIVING_DISABLED
v Message: Media archiving is currently disabled.
ENC-rec-0023
v Status Code: REC_BACKUP_SEGMENT_ABORTED
v Message: Backup segment aborted.
ENC-rec-0024
v Status Code: REC_BACKUP_FILE_TOO_SMALL
v Message: Backup file is too small.
854
ENC-rec-0025
v Status Code: REC_RESTORE_ABORTED
v Message: Restore is aborted.
ENC-rec-0026
v Status Code: REC_RESTORE_NO_BACKUP
v Hexadecimal ID: 0x76ae201a
v Message: There is no backup for one of the volumes to restore.
ENC-rec-0027
v Status Code: REC_RESTORE_WRONG_FILE
v Hexadecimal ID: 0x76ae201b
v Message: The backup file does not match the volume being
restored.
ENC-rec-0028
v Status Code: REC_NO_ACTIVE_RESTORE
v Hexadecimal ID: 0x76ae201c
v Message: No active restore.
ENC-rec-0029
v Status Code: REC_VOL_ENABLED
v Hexadecimal ID: 0x76ae201d
v Message: Volume enabled.
ENC-rec-0030
v Status Code: REC_VOL_DISABLED
v Hexadecimal ID: 0x76ae201e
v Message: Volume disabled.
ENC-rec-0031
v Status Code: REC_VOL_BROKEN
v Hexadecimal ID: 0x76ae201f
v Message: Volume damaged.
ENC-rec-0032
v Status Code: REC_FUNCTION_UNAVAILABLE
v Message: Specified function is unavailable.
ENC-rec-0033
855
v Status Code: REC_LOG_ARCHIVE_FILE_INACCESSIBLE

v Message: Log archive file containing desired information is
inaccessible.
ENC-rec-0034
v Status Code: REC_MEDIA_ARCHIVE_ERROR
v Message: Error when operating on log media archive
ENC-rec-0035
v Status Code: REC_OPEN_LOG_FAILURE
v Message: Failure to enable the log.
ENC-rst-0001
v Status String: ENC-rst-0001
v Status Code: RESTART_INVALID_DEVICE_NAME
v Hexadecimal ID: 0x76d23001
v Message: Same names for two or more devices.
ENC-rst-0002
v Status Code: RESTART_INVALID_NUM_DEVICES
v Message: The number of device supplied is either less or greater
than the supported value.
ENC-rst-0003
v Status Code: RESTART_INVALID_RESTART_MODE
v Message: The restart mode is neither cold start nor warm start.
ENC-sfs-0002
v Status String: ENC-sfs-0002
v Status Code: SFS_BAD_ACCESS_MODE
v Message: Invalid access mode in open request
ENC-sfs-0003
v Status Code: SFS_BAD_ATTRIBUTE_NAME
v Message: Attribute name has an invalid format.
ENC-sfs-0004
v Status Code: SFS_BAD_AUTHORITY
856
v Message: Unrecognized authority value.

ENC-sfs-0005
v Status Code: SFS_BAD_CONSISTENCY
v Message: Invalid consistency value in open request.
ENC-sfs-0006
v Status Code: SFS_BAD_DUPLICATE_DETECTION
v Message: Invalid duplicate detection value in open request.
ENC-sfs-0007
v Status Code: SFS_BAD_FIELD_NAME
v Message: Invalid record field name.
ENC-sfs-0008
v Status Code: SFS_BAD_FIELD_SIZE
v Message: Invalid record field size.
ENC-sfs-0009
v Status Code: SFS_BAD_FIELD_TYPE
v Message: Unrecognized record field type.
ENC-sfs-0010
v Status Code: SFS_BAD_FILE_NAME
v Message: Invalid file name.
ENC-sfs-0011
v Status Code: SFS_BAD_FILE_ORGANIZATION
v Message: Invalid file organization value.
ENC-sfs-0012
v Status Code: SFS_BAD_INDEX_NAME
v Message: Invalid index name.
ENC-sfs-0013
857
v Status Code: SFS_BAD_KEY_VALUE

v Message: Invalid key value.
ENC-sfs-0014
v Status Code: SFS_BAD_NUMBER_OF_FIELDS
v Message: Invalid num of record or key fields.
ENC-sfs-0015
v Status Code: SFS_BAD_RECORD_VALUE
v Message: Invalid record value.
ENC-sfs-0016
v Status Code: SFS_BAD_VOLUME_NAME
v Message: Invalid volume name.
ENC-sfs-0017
v Status Code: SFS_CRP_UNDEFINED
v Message: The current record position is not established.
ENC-sfs-0018
v Status Code: SFS_CURRENT_RECORD_DELETED
v Message: The current record is deleted.
ENC-sfs-0019
v Status Code: SFS_CURRENT_UNDEFINED
v Message: There is a previous or next record but no current
record.
ENC-sfs-0020
v Status Code: SFS_DISALLOWED_ON_ACTIVE_INDEX
v Message: Invalid operation on an active index.
ENC-sfs-0021
v Status Code: SFS_DISALLOWED_ON_PRIMARY_INDEX
858
v Message: Invalid operation on primary index.

ENC-sfs-0022
v Status Code: SFS_DUPLICATE_IN_UNIQUE_INDEX
v Message: Attempt to insert a duplicate key in a unique index.
ENC-sfs-0023
v Status Code: SFS_END_OF_KEY_RANGE
v Message: Attempt to read past end of range.
ENC-sfs-0024
v Status Code: SFS_ESN_TOO_BIG
v Message: ESN is too large for 4-byte conversion.
ENC-sfs-0025
v Status Code: SFS_EXCLUSIVE_OFD_EXISTS
v Message: File is already opened exclusively.
ENC-sfs-0026
v Status Code: SFS_EXCLUSIVE_OFD_REQUIRED
v Message: Operation requires an exclusive OFD.
ENC-sfs-0027
v Status Code: SFS_FILE_DAMAGED
v Message: File is damaged.
ENC-sfs-0028
v Status Code: SFS_FILE_NAME_EXISTS
v Message: File by this name already exists.
ENC-sfs-0029
v Status Code: SFS_INDEX_NOT_ACTIVE
v Message: The index is not active.
ENC-sfs-0030
859
v Status Code: SFS_INDEX_NOT_UNIQUE

v Message: Operation requires a unique index.
ENC-sfs-0031
v Status Code: SFS_INDEX_NAME_EXISTS
v Message: Index by this name already exists.
ENC-sfs-0032
v Status Code: SFS_INSUFFICIENT_AUTHORITY
v Message: Insufficient authority for this operation.
ENC-sfs-0033
v Status Code: SFS_INSUFFICIENT_BUFFER
v Message: At least one supplied record buffer is too small.
ENC-sfs-0034
v Status Code: SFS_INSUFFICIENT_FILE_ACCESS_RIGHTS
v Message: Insufficient privilege for this operation.
ENC-sfs-0035
v Status Code: SFS_INTERNAL_SFS_ERROR
v Message: SFS internal error.
ENC-sfs-0036
v Status Code: SFS_INVALID_END_POINT
v Message: Either start or end of a range is invalid.
ENC-sfs-0037
v Status Code: SFS_INVALID_ESN
v Message: ESN is not a valid Entry Sequence Number.
ENC-sfs-0038
v Status Code: SFS_INVALID_ISOLATION_LEVEL
v Message: Unrecognized isolation level.
860
ENC-sfs-0039
v Status Code: SFS_INVALID_LOCK_MODE
v Message: Invalid lock mode value.
ENC-sfs-0040
v Status Code: SFS_INVALID_MAX_NUMBER_RECORDS
v Message: Invalid value for maximum number of records.
ENC-sfs-0041
v Status Code: SFS_INVALID_RECORD_SIZE
v Message: Invalid record size.
ENC-sfs-0042
v Status Code: SFS_MAX_NUMBER_RECORDS_EXCEEDED
v Message: Maximum number of records has been exceeded.
ENC-sfs-0043
v Status Code: SFS_MEDIA_RECOVERY_REQUIRED
v Message: Media recovery must be performed.
ENC-sfs-0044
v Status Code: SFS_MEMORY_LIMIT
v Message: Memory allocation failure.
ENC-sfs-0045
v Status Code: SFS_NO_ASSOCIATED_ESN
v Message: The OFD does not have an associated ESN.
ENC-sfs-0046
v Status Code: SFS_NO_ASSOCIATED_RSN
v Message: The OFD does not have an associated RSN.
ENC-sfs-0047
v Status Code: SFS_NO_DUPLICATE_DETECTION
861

v Message: Duplicate detection has not been requested for this OFD.
ENC-sfs-0048
v
v
v
v
Status String: ENC-sfs-0048

Status Code: SFS_NO_SUCH_ATTRIBUTE
Message: Attribute by this name is not found.
ENC-sfs-0049
v Status Code: SFS_NO_SUCH_FIELD
v Message: Field by this name does not exist.
ENC-sfs-0050
v Status Code: SFS_NO_SUCH_FILE
v Message: File by this name does not exist.
ENC-sfs-0051
v Status Code: SFS_NO_SUCH_FILE_SYSTEM
v Message: Unknown file system name.
ENC-sfs-0052
v Status Code: SFS_NO_SUCH_INDEX
v Message: Index by this name does not exist.
ENC-sfs-0053
v Status Code: SFS_NO_SUCH_KEY_VALUE
v Message: Cannot find a key by that value.
ENC-sfs-0054
v Status Code: SFS_NO_SUCH_VOLUME
v Message: Unknown volume name.
ENC-sfs-0055
v Status Code: SFS_NON_TRANSACTIONAL_OFD_REQUIRED
v Message: Operation requires non-transactional OFD.
ENC-sfs-0056
862
v
v
v
v

Status Code: SFS_NOT_AN_ENTRY_SEQUENCED_FILE
Message: Operation only allowed on a Entry-Sequenced file.
ENC-sfs-0057
v Status Code: SFS_NOT_A_RELATIVE_FILE
v Message: Operation only allowed on a relative file.
ENC-sfs-0058
v Status Code: SFS_OFD_ASSOCIATED_WITH_TRANSACTION
v Message: Ofd still associated with a transaction.
ENC-sfs-0059
v Status Code: SFS_OFD_INVALID
v Message: Invalid OfD.
ENC-sfs-0060
v Status Code: SFS_OPERATION_TIMED_OUT
v Message: Timeout expired before operation completed.
v Explanation: The requested Structured File Server (SFS) operation
timed out before completion. This could be caused by a long-running
operation or by a conflict (for example, a transactional lock conflict) which
prevents the operation from completing.
v User Response: Increase the operation timeout for the request or
resolve the conflict.
ENC-sfs-0061
v Status Code: SFS_PRIMARY_KEY_CANNOT_BE_ALTERED
v Message: Primary key value cannot be altered.
ENC-sfs-0062
v Status Code: SFS_SLOT_OCCUPIED
v Message: Record already exists at this relative slot.
ENC-sfs-0063
v Status Code: SFS_TRANSACTION_ABORTED
863
v Message: User transaction is aborted.

ENC-sfs-0064
v Status Code: SFS_UNIMPLEMENTED
v Message: This feature is not yet implemented.
ENC-sfs-0065
v Status Code: SFS_USER_TRANSACTION_REQUIRED
v Message: Operation on this OFD requires a user transaction.
ENC-sfs-0066
v Status Code: SFS_VOLUME_IO_ERROR
v Message: An I/O error occurred on the volume.
ENC-sfs-0067
v Status Code: SFS_VOLUME_NOT_MOUNTED
v Message: The specified volume is not mounted.
ENC-sfs-0068
v Status Code: SFS_VOLUME_SPACE_EXHAUSTED
v Message: The volume is full.
ENC-sfs-0069
v Status Code: SFS_WRONG_TRANSACTION
v Message: Attempt to associate an ofd with a transaction in a
different family.
ENC-sfs-0070
v Status Code: SFS_LAST_WRITE_UNDEFINED
v Message: Last write operation is not defined.
ENC-sfs-0071
v Status Code: SFS_CLIENT_MEMORY_CORRUPTION
v Message: A client memory corruption has been detected.
ENC-sfs-0072
864
v
v
v
v

Status Code: SFS_AREA_SPACE_EXHAUSTED
Message: The allocation in a file data or index area is
exhausted.
ENC-sfs-0073
v Status Code: SFS_BAD_RECORD_SPEC
v Message: Invalid record specification.
ENC-sfs-0074
v Status Code: SFS_BAD_KEY_SPEC
v Message: Invalid index specification.
ENC-sfs-0075
v Status Code: SFS_OFD_IN_AUTOCLOSE_MODE
v Message: This OFD has been opened in auto-close mode.
ENC-sfs-0076
v Status Code: SFS_COMMUNICATION_ERROR
v Message: A communication error occurred.
v Explanation: A transactional RPC (TRPC) or RPC from the SFS client to
the SFS server has failed. This could be caused by a wide range of
environmental problems, from a transient communication error to the
termination of the server process.
v User Response: Use default trpc tracing to identify the RPC exception
caught and verify the validity of the binding used for the RPC. Ensure
that the client process has a valid login context and check the viability of
the server using rpcutil ping server.
ENC-sfs-0077
v Status Code: SFS_BAD_FIELD_VALUE
v Message: Invalid field value.
ENC-sfs-0078
v Status Code: SFS_INVALID_SCAN_DIRECTION
v Message: Invalid scan direction value.
ENC-sfs-0079
865
v Status Code: SFS_INVALID_MODIFY_OPERATION

v Message: Invalid modify operation request.
ENC-sfs-0080
v Status Code: SFS_INVALID_RSN
v Message: The relative slot number is invalid.
ENC-sfs-0081
v Status Code: SFS_INCONSISTENT_OFDS
v Message: Batch request involves inconsistent OFDs.
ENC-sfs-0082
v Status Code: SFS_INVALID_BATCH_OPERATION
v Message: Invalid batch operation request.
ENC-sfs-0083
v Status Code: SFS_BAD_INDEX_SPEC
v Message: Invalid index specification.
ENC-sfs-0086
v Status Code: SFS_FILE_HAS_ACTIVE_INDICES
v Message: File has active indices.
ENC-sfs-0087
v Status Code: SFS_INDEX_ALREADY_REQUESTED
v Message: Copy operation requested that an index be copied more
than once.
ENC-sfs-0088
v Status Code: SFS_NOT_ALL_ACTIVE_INDICES_REBUILT
v Message: All active indices could not be rebuilt.
ENC-sfs-0090
v Status Code: SFS_FILE_NOT_READ_LOCKED
866
v Message: Operation requires a read lock on the source file.

ENC-sfs-0091
v Status Code: SFS_OPERATION_ABORTED
v Message: Operation was aborted.
ENC-sfs-0092
v Status Code: SFS_NO_SUCH_TRANSACTION
v Message: Transaction could not be found.
ENC-sfs-0093
v Status Code: SFS_INVALID_ARGUMENT
v Message: An invalid argument was specified.
ENC-sfs-0095
v Status Code: SFS_READ_FROM_MODIFIED_FILE
v Message: File was modified since last read.
ENC-sfs-0096
v Status Code: SFS_SECURITY_NOT_IN_USE
v Message: Security service is not in use.
ENC-sfs-0100
v Status Code: SFS_INVALID_TRANSACTION
v Message: Attempt to associate ofd with an invalid transaction.
ENC-sfs-0101
v Status Code: SFS_OFD_TRANSACTION_ASSOCIATION_TIMED_OUT
v Message: Procedure to associate a transaction to an ofd timed
out.
ENC-sfs-0102
v Status Code: SFS_IE_DEVICE_ERROR
v Message: A device error has been encountered.
ENC-sfs-0103
867
v
v
v
v

Status Code: SFS_IE_BADLY_DELIMITED_BUFFER
Message: Initial and final buffer length delimiters do not match.
ENC-sfs-0104
v Status Code: SFS_IE_CHKPT_FILENAME_CONFLICT
v Message: Checkpoint file by the same name exists for a different
SFS file.
ENC-sfs-0105
v Status Code: SFS_IE_END_OF_MEDIA_ON_READ
v Message: Next segment to read was not found on the media.
ENC-sfs-0106
v Status Code: SFS_IE_END_OF_MEDIA_ON_WRITE
v Message: The media is full.
ENC-sfs-0107
v Status Code: SFS_IE_ERROR_LOG_ERROR
v Message: Error processing the error log operations.
ENC-sfs-0108
v Status Code: SFS_IE_ERROR_LOG_FILENAME_CONFLICT
v Message: Error log by the same name exists for a different SFS
file.
ENC-sfs-0109
v Status Code: SFS_IE_ERROR_OBTAINING_EXPORT_ID
v Message: Unable to obtain an export ID.
ENC-sfs-0110
v Status Code: SFS_IE_FILE_MODIFIED
v Message: Force needed to continue the import or export function.
ENC-sfs-0111
v Status Code: SFS_IE_OPERATION_IN_PROGRESS
868

v Message: Restart, resume or force needed to continue the import
or export.
ENC-sfs-0112
v Status Code: SFS_IE_MEDIA_TOO_SMALL_FOR_METADATA
v Message: Need a larger media to store metadata.
ENC-sfs-0113
v Status Code: SFS_IE_TRAILER_NOT_EXPORTED
v Message: Cannot export trailer information since the media is
full.
ENC-sfs-0114
v Status Code: SFS_IE_UNABLE_TO_OPEN_FILE
v Message: Cannot open the SFS file.
ENC-sfs-0115
v Status Code: SFS_IE_UNABLE_TO_CLOSE_FILE
v Message: Cannot close the SFS file.
ENC-sfs-0116
v Status Code: SFS_IE_UNABLE_TO_DESTROY_FILE
v Message: Cannot destroy the SFS file.
ENC-sfs-0117
v Status Code: SFS_IE_UNABLE_TO_LOCK_FILE
v Message: Cannot lock the SFS file.
ENC-sfs-0118
v Status Code: SFS_IE_UNABLE_TO_GET_INFO
v Message: Cannot get the SFS file information.
ENC-sfs-0119
v
v
v
v

Status Code: SFS_IE_UNABLE_TO_GET_ATTRIBUTES
Message: Cannot get the SFS file attributes.
869
ENC-sfs-0120
v Status Code: SFS_IE_UNABLE_TO_SET_ATTRIBUTE
v Message: Cannot set the SFS file attributes.
ENC-sfs-0121
v Status Code: SFS_IE_UNABLE_TO_SET_RANGE_ON_SFS_FILE
v Message: Cannot set the range on the SFS file.
ENC-sfs-0122
v Status Code: SFS_IE_UNABLE_TO_READ_FILE
v Message: Cannot read records from the SFS file.
ENC-sfs-0123
v Status Code: SFS_IE_UNABLE_TO_EXTRACT_KEY
v Message: Cannot extract a key from SFS file.
ENC-sfs-0124
v Status Code: SFS_IE_UNABLE_TO_COMPARE_KEYS
v Message: Cannot compare keys from the SFS file.
ENC-sfs-0125
v Status Code: SFS_IE_UNABLE_TO_CREATE_FILE
v Message: Cannot create the SFS file.
ENC-sfs-0126
v Status Code: SFS_IE_UNABLE_TO_INSERT_INTO_FILE
v Message: Cannot insert records into the SFS file.
ENC-sfs-0127
v Status Code: SFS_IE_UNABLE_TO_GET_SECONDARY_INDEX_INFO
v Message: Cannot get the secondary index information.
ENC-sfs-0128
v Status Code: SFS_IE_UNABLE_TO_ADD_SECONDARY_INDEX
870

v Message: Cannot add a secondary index.
ENC-sfs-0129
v
v
v
v

Status Code: SFS_IE_UNABLE_TO_GET_ESN
Message: Cannot get the ESN for a record.
ENC-sfs-0130
v Status Code: SFS_IE_UNABLE_TO_GET_RSN
v Message: Cannot get the RSN for a record.
ENC-sfs-0131
v Status Code: SFS_IE_UNABLE_TO_FIND_RSN_FIELD
v Message: Cannot find the offset within a record to the RSN field.
ENC-sfs-0132
v Status Code: SFS_IE_UNABLE_TO_GET_SFS_DUPLICATE
v Message: Call to sfs_IsDuplicate failed.
ENC-sfs-0133
v Status Code: SFS_IE_UNABLE_TO_CREATE_CHKPT_FILE
v Message: Cannot create checkpoint file.
ENC-sfs-0134
v Status Code: SFS_IE_UNABLE_TO_OPEN_CHKPT_FILE
v Message: Cannot open checkpoint file.
ENC-sfs-0135
v Status Code: SFS_IE_UNABLE_TO_INSERT_CHKPT
v Message: Cannot insert checkpoints.
ENC-sfs-0136
v Status Code: SFS_IE_UNABLE_TO_DELETE_CHKPT
v Message: Cannot delete checkpoints.
ENC-sfs-0137
871
v
v
v
v

Status Code: SFS_IE_UNABLE_TO_UPDATE_CHKPT
Message: Cannot update checkpoints.
ENC-sfs-0138
v Status Code: SFS_IE_UNABLE_TO_SET_RANGE_ON_CHKPT_FILE
v Message: Cannot set range on checkpoint file.
ENC-sfs-0139
v Status Code: SFS_IE_UNABLE_TO_READ_CHKPT_FILE
v Message: Cannot read checkpoints.
ENC-sfs-0140
v Status Code: SFS_IE_UNABLE_TO_CLOSE_CHKPT_FILE
v Message: Cannot close checkpoint file.
ENC-sfs-0141
v Status Code: SFS_IE_UNABLE_TO_DESTROY_CHKPT_FILE
v Message: Cannot destroy checkpoint file.
ENC-sfs-0142
v Status Code: SFS_IE_VERSION_UNKNOWN
v Message: Version number in export set is not recognized.
ENC-sfs-0143
v Status Code: SFS_IE_IMPROPER_EXPORT_FORMAT
v Message: Section of export set unknown or not in correct order.
ENC-sfs-0144
v Status Code: SFS_IE_ERROR_IN_TRAILER
v Message: Unable to read trailer section.
ENC-sfs-0145
v Status Code: SFS_IE_UNABLE_TO_DETERMINE_DATA_REP
872
v Message: Unable to determine the byte order of integers.

ENC-sfs-0146
v Status Code: SFS_IE_UNABLE_TO_POSITION_DEVICE
v Message: Unable to find the device position.
ENC-sfs-0147
v Status Code: SFS_IE_UNABLE_TO_OPEN_DEVICE
v Message: Unable to open the device or file.
ENC-sfs-0148
v Status Code: SFS_IE_UNABLE_TO_CLOSE_DEVICE
v Message: Unable to close the device or file.
ENC-sfs-0149
v Status Code: SFS_IE_INVALID_SEGMENT_HEADER
v Message: Invalid field or value in segment header.
ENC-sfs-0150
v Status Code: SFS_INSERT_CACHE_NOT_FLUSHED
v Message: Failed to flush the contents of the insert cache.
ENC-sfs-0151
v Status Code: SFS_FILE_NOT_WRITE_LOCKED
v Message: Operation requires a write lock on the source file.
ENC-sfs-0152
v Status Code: SFS_READ_CACHE_NOT_FLUSHED
v Message: Failed to flush the contents of the read cache.
ENC-sfs-0153
v Status Code: SFS_OPERATIONAL_FORCE_NOT_ALLOWED
v Message: Incompatible operation with ofds operational force.
ENC-sfs-0154
873
v Status Code: SFS_DUPLICATE_DETECTION_NOT_ALLOWED

v Message: Incompatible operation with ofds duplicate detection.
ENC-sfs-0155
v Status Code: SFS_FUNCTION_NOT_SUPPORTED
v Message: Function not supported by server.
ENC-sfs-0157
v Status Code: SFS_MAX_BATCH_CALLS_EXCEEDED
v Message: Maximum number of batch calls exceeded.
ENC-sfs-0158
v Status Code: SFS_BAD_ATTRIBUTE_VALUE
v Message: Invalid attribute value.
ENC-sfs-0159
v Status Code: SFS_TRANSACTIONAL_OFD_REQUIRED
v Message: Operation requires a transactional OFD.
ENC-sfs-0160
v Status Code: SFS_FAILED_OPERATIONS_IN_INSERT_CACHE
v Hexadecimal ID: 0x7715a0a0
v Message: One or more records could not be flushed in insert cache
ENC-sfs-0161
v Status Code: SFS_FAILED_OPERATIONS_IN_READ_CACHE
v Message: One or more records could not be flushed in read cache
ENC-sfs-0162
v Status Code: SFS_CLIENT_SIDE_CACHING_NOT_ENABLED
v Message: Client side caching is not enabled.
ENC-sfs-0163
v Status Code: SFS_UNABLE_TO_REGISTER_INTERFACE
v Message: Failed to register an RPC interface.
874
ENC-sfs-0164
v Status Code: SFS_VOLUMES_NOT_RECOVERED
v Message: Logical data volumes are not recovered.
ENC-sfs-0165
v Status Code: SFS_BUFFER_POOL_EXHAUSTED
v Message: No more buffers available in pool
ENC-sfs-0166
v Status Code: SFS_UNKNOWN_INTEGER_FORMAT
v Message: Unable to byte swap integers according to format
received
ENC-sfs-0167
v Status Code: SFS_ST_ALREADY_ACTIVE
v Message: A server side transaction is already active for this
client.
ENC-sfs-0168
v Status Code: SFS_ST_NOT_ACTIVE
v Message: No server side transaction is active for this client.
ENC-sfs-0169
v
v
v
v

Status Code: SFS_ST_NOT_SUPPORTED
Hexadecimal ID: 0x7715a0a9
Message: SFS server does not support server side transactions.
ENC-tht-0001
v Status String: ENC-tht-0001
v Status Code: THREADTID_RREQ_FAILED
v Message: threadTid_CallbackAfterReceivingRequest failed
ENC-tmx-0001
v Status String: ENC-tmx-0001
v Status Code: TMXA_ALREADY_INITIALIZED
v Message: TM-XA has already been initialized using the tmxa_Init
function.
ENC-tmx-0002
875
v
v
v
v
Status String: ENC-tmx-0002

Status Code: TMXA_DID_NOT_MIGRATE
Hexadecimal ID: 0x778b7002
Message: A migration request was not honored by a resource
manager instance that claimed it supported migration.
ENC-tmx-0003
v Status Code: TMXA_EXISTING_ASSOCIATION
v Message: An association has already been made in this thread.
ENC-tmx-0004
v Status Code: TMXA_INTERNAL_ERROR
v Message: The TM-XA Service found some internal inconsistency or
memory allocation problem it could not resolve.
ENC-tmx-0005
v Status Code: TMXA_INVALID_PARAM
v Message: One of the parameters has an invalid value.
ENC-tmx-0006
v Status Code: TMXA_NO_EXISTING_ASSOCIATION
v Message: A request to remove an association was made when no
association existed.
ENC-tmx-0007
v Status Code: TMXA_NO_MORE_MEMORY
v Message: No memory available.
ENC-tmx-0008
v Status Code: TMXA_NOT_INITIALIZED
v Message: TM-XA has not yet been initialized using the tmxa_Init
function.
ENC-tmx-0009
v Status Code: TMXA_RESUMER_NOT_SUSPENDER
v Message: An attempt is made to resume an association that was not
migrated and was not suspended in the current thread.
876
ENC-tmx-0010
v Status Code: TMXA_TOO_MANY_INSTANCES_REGISTERED
v Hexadecimal ID: 0x778b700a
v Message: Too many resource manager instances have been
registered.
ENC-tmx-0011
v
v
v
v

Status Code: TMXA_TOO_MANY_TIDS
Hexadecimal ID: 0x778b700b
Message: Too many transactions have been associated with resource
managers.
ENC-tmx-0012
v Status Code: TMXA_TRAN_ERROR
v Hexadecimal ID: 0x778b700c
v Message: TRAN returned an unrecoverable error.
ENC-tmx-0013
v Status Code: TMXA_TRUNCATED_XID
v Hexadecimal ID: 0x778b700d
v Message: The TM-XA Service generated an XID value greater than
128 bytes. Recovery of the related transaction is compromised.
ENC-tmx-0014
v Status Code: TMXA_XACLOSE_ERROR
v Hexadecimal ID: 0x778b700e
v Message: An XA error was encountered while closing a resource
manager instance.
ENC-tmx-0015
v Status Code: TMXA_XACOMMIT_ERROR
v Hexadecimal ID: 0x778b700f
v Message: An XA error was encountered during an xa_commit call.
ENC-tmx-0016
v Status Code: TMXA_XAEND_ERROR
v Message: An XA error was encountered during an xa_end call.
ENC-tmx-0017
v Status Code: TMXA_XAFORGET_ERROR
v Message: An XA error was encountered during an xa_forget call.
877
ENC-tmx-0018
v Status Code: TMXA_XAOPEN_ERROR
v Message: An XA error was encountered while opening a resource
manager instance.
ENC-tmx-0019
v
v
v
v

Status Code: TMXA_XAPREPARE_ERROR
Message: An XA error was encountered during an xa_prepare call.
ENC-tmx-0020
v
v
v
v

Status Code: TMXA_XAROLLBACK_ERROR
Message: An XA error was encountered during an xa_rollback call.
ENC-tmx-0021
v Status Code: TMXA_XASTART_ERROR
v Message: An xa_start call was not successful.
ENC-tmx-0022
v Status Code: TMXA_XID_ALREADY_CHOSEN
v Message: The procedure specifies a model for a transaction that
already has an XID assigned to it.
ENC-tmx-0023
v
v
v
v

Status Code: TMXA_RMI_IS_BUSY
Message: The specified RMI is busy and cannot be disabled.
ENC-tmx-0024
v Status Code: TMXA_UNKNOWN_RMI
v Message: The specified RMID is illegal.
ENC-tmx-0025
v Status Code: TMXA_RMI_IS_DISABLED
v Message: Tried to manually flow XA calls to a disabled RMI.
ENC-tmx-0026
878
v Status Code: TMXA_RMI_IS_BEING_DISABLED

v Message: Tried to disable a RMI that is in the middle of being
disabled.
ENC-tmx-0027
v Status Code: TMXA_ALL_RMIS_ARE_DISABLED
v Hexadecimal ID: 0x778b701b
v Message: Tried to manually flow XA calls when all RMIs are
disabled.
ENC-tra-0001
v Status String: ENC-tra-0001
v Status Code: TRAN_NOT_SUPPORTED
v Message: The requested function is not supported in this
implementation.
ENC-tra-0010
v Status Code: TRAN_APPL_INITIALIZED
v Message: The application has already called tran_Init.
ENC-tra-0011
v Status Code: TRAN_APPL_NOT_INITIALIZED
v Message: The application has not called tran_Init.
ENC-tra-0012
v Status Code: TRAN_APPL_READY
v Hexadecimal ID: 0x7796800c
v Message: The application has already called tran_Ready.
ENC-tra-0013
v Status Code: TRAN_APPL_NOT_READY
v Hexadecimal ID: 0x7796800d
v Message: The application has not called tran_Ready.
ENC-tra-0014
v Status Code: TRAN_COMM_INITIALIZED
v Hexadecimal ID: 0x7796800e
v Message: The communication service has already called
tran_CommInit.
ENC-tra-0015
879
v Status Code: TRAN_COMM_NOT_INITIALIZED

v Hexadecimal ID: 0x7796800f
v Message: The communication service has not called tran_CommInit.
ENC-tra-0016
v Status Code: TRAN_ENVIRONMENT_INCOMPLETE
v Message: The application has not established one or more of the
environment functions.
ENC-tra-0017
v Status Code: TRAN_REC_INITIALIZED
v Message: The recovery service has already called tran_RecInit.
ENC-tra-0018
v Status Code: TRAN_REC_NOT_INITIALIZED
v Message: The recovery service has not called tran_RecInit.
ENC-tra-0019
v Status Code: TRAN_INVALID_SERVICE
v Message: The service identifier does not refer to a valid
communication or recovery service.
ENC-tra-0030
v Status Code: TRAN_NESTING_DISABLED
v Message: The application disabled nested transactions when it
called tran_Init.
ENC-tra-0031
v Status Code: TRAN_NESTING_NOT_SUPPORTED
v Message: This version of the Transaction Service does not support
nested transactions.
ENC-tra-0050
v Status Code: TRAN_INTERNAL_ERROR
v Message: The transaction service has encountered an internal
error.
ENC-tra-0070
880
v
v
v
v
Status String: ENC-tra-0070

Status Code: TRAN_INVALID_MESSAGE
Hexadecimal ID: 0x77968046
Message: The message cannot be interpreted.
ENC-tra-0071
v Status Code: TRAN_INVALID_RECORD
v Message: The log record cannot be interpreted.
ENC-tra-0100
v Status Code: TRAN_TID_NOT_VALID
v Message: The transaction identifier that was passed as an
argument did not meet the requirements for the function.
ENC-tra-0120
v Status Code: TRAN_NOT_BEGINNER
v Message: This application did not begin the transaction.
ENC-tra-0130
v Status Code: TRAN_TID_ACTIVE_CHILDREN
v Message: The transaction has children that have neither committed
nor aborted.
ENC-tra-0131
v Status Code: TRAN_TID_OUTSTANDING_REQUESTS
v Message: The transaction has sent requests for which replies have
not yet been received.
ENC-tra-0140
v Status Code: TRAN_COORDINATOR_NOT_SET
v Message: No coordinator has been specified yet.
ENC-tra-0141
v Status Code: TRAN_COORDINATOR_CONFLICT
v Message: Some other application insisted on a different
coordinator.
ENC-tra-0150
881
v
v
v
v
Status String: ENC-tra-0150

Status Code: TRAN_PROPERTY_KEY_NOT_FOUND
Message: No properties with the specified key were found.
ENC-tra-0151
v Status Code: TRAN_PROPERTY_KEY_RESERVED
v Message: The property key is reserved for use by the transaction
service.
ENC-tra-0160
v Status Code: TRAN_TRANSACTION_ABORTED
v Message: The message refers to a transaction that has been
aborted.
ENC-tra-0170
v Status Code: TRAN_SECURITY_KEY_ALREADY_SET
v Hexadecimal ID: 0x779680aa
v Message: A security key has already been associated with the
transaction.
ENC-trc-0001
v
v
v
v
Status String: ENC-trc-0001

Status Code: TC_NOT_INIT
Message: Transactional-C was not initialized.
ENC-trc-0002
v Status String: ENC-trc-0002
v Status Code: TC_ALREADY_INIT
v Message: Transactional-C was already initialized.
ENC-trc-0003
v Status Code: TC_ILLEGAL_SUSPEND
v Message: Illegal use of the suspend clause.
ENC-trc-0004
v Status Code: TC_ILLEGAL_SUSPEND_ARG
v Message: The tran_tid_t pointer passed as an argument to the
suspend clause was NULL.
ENC-trc-0005
882
v
v
v
v

Status Code: TC_ILLEGAL_RESUME
Message: The resumeTran statement was used in an illegal context
(e.g. in a concurrent statement).
ENC-trc-0006
v Status Code: TC_ILLEGAL_RESUME_ARG
v Message: The tran_tid_t argument passed to the resumeTran
statement does not belong to a suspended transaction.
ENC-trc-0007
v Status Code: TC_ILLEGAL_SUBTRAN
v Message: The subTran clause was used outside a concurrent or
cofor statement.
ENC-trc-0008
v Status Code: TC_ILLEGAL_SUBTHREAD
v Message: The subThread clause was used outside a concurrent or
cofor statement.
ENC-trc-0009
v Status Code: TC_ILLEGAL_TRAN
v Message: The transaction statement was executed within a
concurrent or cofor statement.
ENC-trc-0010
v Status Code: TC_ILLEGAL_TOPLEVEL
v Message: The topLevel statement was executed within a concurrent
or cofor statement.
ENC-trc-0011
v Status Code: TC_ILLEGAL_CATCH
v Message: The catchAbort statement was executed within a
ENC-trc-0012
v Status Code: TC_ILLEGAL_ABORT
883
v Message: The abort call was made outside the scope of a

transaction.
ENC-trc-0013
v Status Code: TC_ILLEGAL_CONCURRENT
v Message: The concurrent or cofor statement was executed within a
ENC-trc-0014
v Status Code: TC_ILLEGAL_CONCTHREAD
v Message: The concThread statement was executed within a
ENC-trc-0015
v
v
v
v

Status Code: TC_ILLEGAL_CALLBACK
Hexadecimal ID: 0x7796a00f
Message: An attempt was made to register a transaction service
callback outside the scope of a transaction.
ENC-trc-0016
v Status Code: TC_ILLEGAL_COMPLETED_TID
v Message: The getCompletedTid function was called outside commit
or abort clause.
ENC-trc-0017
v Status Code: TC_ILLEGAL_CONTAINING_TID
v Message: The getContainingTid function called outside the scope
of a transaction.
ENC-trc-0018
v Status Code: TC_ILLEGAL_MUTEX_TERMINATE
v Message: The tranMutexTerminate function was called on an
uninitialized tranMutex_t.
ENC-trc-0019
v Status Code: TC_ILLEGAL_MUTEX_LOCK
v Message: The tranMutexLock function was called on an
uninitialized tranMutex_t.
ENC-trc-0020
884
v
v
v
v

Status Code: TC_ILLEGAL_MUTEX_UNLOCK
Message: The tranMutexUnlock function was called on an
uninitialized, or unlocked, tranMutex_t.
ENC-trc-0021
v Status Code: TC_ILLEGAL_WATCHDOG
v Message: Attempt to set a watch on TRAN_TID_NULL.
ENC-trc-0022
v Status Code: TC_ILLEGAL_MEMORY_ALLOC
v Message: Call to tranMemAlloc made with either a size of zero or
on behalf of a non-existent transaction.
ENC-trc-0023
v Status Code: TC_ILLEGAL_MEMORY_FREE
v Message: Call to tranMemFree with a NULL or invalid pointer.
ENC-trc-0024
v Status Code: TC_ILLEGAL_RPC
v Message: Transactional RPC made on behalf of non-existent
transaction.
ENC-trc-0025
v Status Code: TC_ILLEGAL_ABORT_REASON
v Message: The abortReason function was called outside the scope of
an onAbort clause.
ENC-trc-0026
v Status Code: TC_ILLEGAL_ABORT_NAME
v Message: The abortModuleName function was called outside the
scope of an onAbort clause.
ENC-trc-0027
v Status Code: TC_ILLEGAL_ABORT_FUNCTION
v Message: The abortFunctionName function was called outside the
scope of an onAbort clause.
885
ENC-trc-0028
v Status Code: TC_ILLEGAL_LAZY
v Message: The lazyTran statement was executed before the recovery
service was initialized.
ENC-trc-0029
v
v
v
v

Status Code: TC_INIT_CALLBACK_FAILED
Hexadecimal ID: 0x7796a01d
Message: An application initialization callback returned FALSE.
ENC-trc-0030
v
v
v
v

Status Code: TC_TERM_CALLBACK_FAILED
Hexadecimal ID: 0x7796a01e
Message: An application termination callback returned FALSE.
ENC-trc-0031
v Status Code: TC_MALLOC_ERROR
v Message: Internal Transactional-C error -- vital memory
allocation failed.
ENC-trc-0032
v Status Code: TC_ILLEGAL_LOCK
v Message: A call to obtain a lock was made outside the scope of a
transaction.
ENC-trc-0033
v Status Code: TC_ILLEGAL_UNLOCK
v Message: A call to release a lock was made outside the scope of a
transaction.
ENC-trc-0034
v Status Code: TC_ILLEGAL_CHANGEMODE
v Message: A call to change a lock mode was made outside the scope
of a transaction.
ENC-trc-0035
v Status Code: TC_ILLEGAL_CALL
886
v Message: A Transactional-C construct was executed in non-Tran-C

thread.
ENC-trc-0036
v Status Code: TC_INTERNAL_ERROR
v Message: Internal Transactional-C error.
ENC-trc-0037
v Status Code: TC_DEFAULT_ERROR
v Message: Unknown error
ENC-trc-0038
v Status Code: TC_ILLEGAL_ABORT_CODE
v Message: The abortCode function was called outside the scope of
an onAbort clause.
ENC-trc-0039
v Status Code: TC_ILLEGAL_ABORT_FORMAT
v Message: The abortFormat function was called outside the scope of
an onAbort clause.
ENC-trc-0040
v Status Code: TC_ILLEGAL_ABORT_FORMAT_UUID
v Message: The abort format was not a valid uuid.
ENC-trc-0041
v Status Code: TC_ILLEGAL_ABORT_DATA
v Message: The getAbortData function was called outside the scope
of an onAbort clause.
ENC-trc-0042
v Status Code: TC_ILLEGAL_WRAP
v Message: The wrapEachCall statement was executed within a
ENC-trc-0043
v Status Code: TC_ILLEGAL_COMM_ERROR
887

v Message: The commError function was called outside the scope of
an onAbort clause.
ENC-trc-0044
v Status Code: TC_ILLEGAL_MARK_LAZY
v Message: The markTranLazy statement was executed in a
non-toplevel transaction or outside the scope of any transaction.
ENC-trf-0001
v Status String: ENC-trf-0001
v Status Code: TRACE_NO_ABORT_DATA
v Message: No trace buffer was found in the abort data.
ENC-trf-0002
v Status Code: TRACE_NO_FORMAT_FOUND
v Message: No format was found for the trace event.
ENC-trf-0003
v Status Code: TRACE_INVALID_INDEX
v Message: The requested parameter is not in the trace buffer.
ENC-trf-0004
v Status Code: TRACE_NO_MEMORY
v Message: Insufficient memory is available to process the request.
ENC-trf-0005
v Status Code: TRACE_BAD_THREAD
v Message: No information is available for the requested thread.
ENC-trp-0001
v Status String: ENC-trp-0001
v Status Code: TRPC_ASYNC_RPC_FAILED
v Message: UpcallCommSend fails
ENC-trp-0002
v
v
v
v
888
Status String: ENC-trp-0002

Status Code: TRPC_NULL_APPLID
Message: a null application id was provided
ENC-trp-0003
v Status Code: TRPC_NULL_HANDLE
v Message: a null handle was used
ENC-trp-0004
v Status Code: TRPC_NO_HANDLE
v Message: could not find handle in cache
ENC-trp-0006
v Status Code: TRPC_MULTIPLE_REGISTRATION
v Message: function has been multiply registered
ENC-trp-0007
v Status Code: TRPC_INVALID_ADDR_STRING
v Message: invalid application string has been used
ENC-trp-0008
v Status Code: TRPC_ALREADY_INITIALIZED
v Message: trpc has already been initialized
ENC-trp-0009
v Status Code: TRPC_INVALID_BINDING_HANDLE
v Message: invalid rpc binding handle has been used
ENC-trp-0010
v Status Code: TRPC_UNBOUND_TRAN_HANDLE
v Message: could not get a fully bound transactional handle
v Explanation: The transactional RPC (TRPC) has failed because a
fully-bound transactional handle could not be generated. This can be
caused by a null or invalid TRPC handle, or the failure of the RPC to the
target server.
v User Response: Check the clients default trpc tracing for the underlying
cause (usually, an RPC status or exception is identified as the root
cause).
ENC-trp-0011
889
v Status Code: TRPC_SREQ_FAILED

v Message: tran_CommSendingRequest failed
ENC-trp-0012
v Status Code: TRPC_RREQ_FAILED
v Message: tran_CommReceivedRequest failed
ENC-trp-0013
v Status Code: TRPC_SREP_FAILED
v Message: tran_CommSendingReply failed
ENC-trp-0014
v Status Code: TRPC_RREP_FAILED
v Message: tran_CommReceivedReply failed
ENC-trp-0016
v Status Code: TRPC_MGR_ABORTED
v Message: application provided manager function was aborted
ENC-trp-0017
v Status Code: TRPC_SREQ_CALLBACK_ABORTED
v Message: one of the sending request callbacks aborted the
transaction
ENC-trp-0018
v Status Code: TRPC_RREP_CALLBACK_ABORTED
v Message: one of the received reply callbacks aborted the
transaction
ENC-trp-0019
v Status Code: TRPC_NO_LOCAL_ADDRESS
v Message: could not get local address
ENC-trp-0020
v Status Code: TRPC_DUPLICATE_CALL
890
v Message: function has been erroneously called more than once

ENC-trp-0021
v Status Code: TRPC_NO_PROTSEQ_SUPPORTED
v Message: no protocol sequence could be used
ENC-trp-0022
v Status Code: TRPC_USE_WK_ALREADY_CALLED
v Message: trpc_UseWkEndpoints has already been called
ENC-trp-0023
v Status Code: TRPC_NOT_INITIALIZED
v Message: trpc i/f has not been initialized
ENC-trp-0024
v Status Code: TRPC_BIND_WK_ALREADY_CALLED
v Message: trpc_BindWkEndpoints has already been called
ENC-trp-0025
v Status Code: TRPC_GOT_DYN_BUT_NO_NS
v Message: trpc got a dynamic binding but the name service is not
running
ENC-trp-0026
v Status Code: TRPC_ALREADY_READIED
v Message: trpc has been already readied
ENC-trp-0027
v Status Code: TRPC_TRAN_NOT_READIED
v Message: tran_Ready has yet not been called
ENC-trp-0029
v Status Code: TRPC_RPC_FAILED
v Message: RPC failed for unknown reasons
v Explanation: A transactional RPC (TRPC) failed for unknown reasons.
This is the generic RPC failure status code for TRPC. This status is
891
returned when TRPC cannot successfully convert the exception caught

into an appropriate corresponding status.
v User Response: Use default trpc tracing to identify the exception
caught.
ENC-trp-0030
v Status Code: TRPC_CALLBACK_DATA_OVERFLOW
v Message: more callback data was supplied than could be
accomodated
ENC-trp-0031
v
v
v
v

Status Code: TRPC_INVALID_ASYNC_RPC
Hexadecimal ID: 0x7797701f
Message: parameters to an asynchronous RPC were invalid
ENC-trp-0033
v Status Code: TRPC_SREQ_PIGGYBACK_OVERFLOW
v Message: The Transaction Service state for an outgoing TRPC was
too large to be carried in the RPC message.
ENC-trp-0034
v
v
v
v

Status Code: TRPC_SREP_PIGGYBACK_OVERFLOW
Message: The Transaction Service state for an returning TRPC was
too large to be carried in the RPC message.
ENC-trp-0035
v Status Code: TRPC_SERVER_SIDE_ABORT
v Message: The server-side transaction was aborted or took an
exception.
ENC-trp-0036
v Status Code: TRPC_ABORT_REASON_UNKNOWN
v Message: The abort reason for the server-side transaction could
not be determined.
ENC-trp-0037
v Status Code: TRPC_DEFAULT_TIMEOUT_EXPIRED
v Message: The auto tran watch facilty aborted the transaction
because the default timeout expired.
892
ENC-trp-0038
v Status Code: TRPC_CAUGHT_RPC_FAILURE
v Message: (internal) An RPC was caught by a comm_status or
fault_status parameter.
ENC-trp-0039
v
v
v
v

Status Code: TRPC_NOT_IN_MGR
Message: not in manager function
ENC-trp-0040
v
v
v
v

Status Code: TRPC_SREP_FAILED_RPC_OK
Message: (internal) tran_CommSendingReply failed, but the RPC
returned normally.
ENC-trp-0041
v Status Code: TRPC_REQUEST_REJECTED
v Message: (internal) The RPC was rejected.
ENC-trp-0042
v Status Code: TRPC_NOT_IN_STUB
v Message: Call is only valid within a stub function
ENC-trp-0043
v
v
v
v

Status Code: TRPC_MGR_ABORTED_RPC_OK
Hexadecimal ID: 0x7797702b
Message: The application provided manager function was aborted,
but the RPC returned normally
ENC-vol-0001
v Status String: ENC-vol-0001
v Status Code: VOL_CHUNK_SIZE_MISMATCH
v Message: A physical volume chunk size differs from one backing a
logical volume.
ENC-vol-0002
v Status Code: VOL_ACCESS_DENIED
893
v Message: Client attempted to access a disk which belongs to

another VOL client.
ENC-vol-0003
v Status Code: VOL_DISK_DAMAGED
v Message: Disk control block is damaged.
ENC-vol-0004
v Status Code: VOL_DISK_IO_ERROR
v Message: Disk read/write error.
ENC-vol-0005
v Status Code: VOL_DISK_ONLINE
v Message: Disk is being used for read/write operations.
ENC-vol-0006
v Status Code: VOL_DISK_OFFLINE
v Message: Disk is not available for read/write operations.
ENC-vol-0007
v Status Code: VOL_DISK_PROTECTED
v Message: User is not permitted to access the disk.
v Explanation: The application was unable to read from or write to the
specified disk device.
v User Response: Ensure that appropriate permissions have been granted
for the device and that the application is running under the proper identity
to access the device.
ENC-vol-0008
v Status Code: VOL_DISK_INITIALIZED
v Message: Disk is already initialized.
ENC-vol-0009
v Status Code: VOL_DISK_NOT_INITIALIZED
v Message: Disk is not yet initialized.
ENC-vol-0010
894
v Status Code: VOL_INVALID_CHUNK_SIZE

v Message: Chunk size is not a power of two, or too large.
ENC-vol-0011
v Status Code: VOL_INVALID_DATA_POINTER
v Message: Client provided data pointer is NULL.
ENC-vol-0012
v Status Code: VOL_INVALID_DISK_ADDR
v Message: A supplied or calculated disk address is invalid.
ENC-vol-0013
v Status Code: VOL_INVALID_FLAG
v Message: Client provided state or mount flag is invalid.
ENC-vol-0014
v Status Code: VOL_INVALID_LOGICAL_ID
v Message: Client provided logical volume identifier is invalid.
ENC-vol-0015
v Status Code: VOL_INVALID_LOGICAL_SIZE
v Message: Client provided logical volume size is invalid.
ENC-vol-0016
v Status Code: VOL_INVALID_NAME
v Message: Client provided volume or disk name is invalid.
v Explanation: An incorrect name has been specified to the Volume
Service (VOL). The most common cause is that the specified physical
device or file volume does not exist, or that the specified logical volume
name has not been created.
ENC-vol-0017
v Status Code: VOL_INVALID_PAGE_NUMBER
v Message: Client provided page number is invalid.
ENC-vol-0018
895
v Status Code: VOL_INVALID_PHYSICAL_ID

v Message: Client provided physical volume identifier is invalid.
ENC-vol-0019
v Status Code: VOL_INVALID_RESTART_FN
v Message: Client provided NULL for restart function pointer.
ENC-vol-0020
v Status Code: VOL_NAME_COLLISION
v Message: A volume or disk of that name already exists.
ENC-vol-0021
v Status Code: VOL_OS_ERROR
v Message: Some operating system error occurred.
ENC-vol-0022
v Status Code: VOL_REGION_OCCUPIED
v Message: Client provided region is already in use.
ENC-vol-0023
v Status Code: VOL_REGION_TOO_SMALL
v Message: Client provided region is smaller than the chunk size.
ENC-vol-0024
v Status Code: VOL_UNINITIALIZED
v Message: The vol_Init() function has not been called.
ENC-vol-0025
v Status Code: VOL_VOLUME_DIRTY
v Message: A logical or physical volume is dirty.
ENC-vol-0026
v Status Code: VOL_VOLUME_INDETERMINATE
v Message: A logical or physical volume is indeterminate.
896
ENC-vol-0027
v Status Code: VOL_VOLUME_CORRUPTED
v Message: A logical or physical volume is corrupted.
ENC-vol-0028
v Status Code: VOL_VOLUME_MAPPED
v Message: A specified physical volume is mapped to logical volume.
ENC-vol-0029
v Status Code: VOL_VOLUME_MIRRORED
v Message: A specified logical volume is mirrored.
ENC-vol-0030
v Status Code: VOL_VOLUME_MOUNTED
v Message: A specified volume is mounted.
ENC-vol-0031
v Status Code: VOL_VOLUME_NOT_MAPPED
v Message: A specified physical volume is not mapped to a logical
volume.
ENC-vol-0032
v Status Code: VOL_VOLUME_NOT_MIRRORED
v Message: A specified logical volume is not mirrored.
ENC-vol-0033
v Status Code: VOL_VOLUME_NOT_MOUNTED
v Message: A specified volume is not mounted.
ENC-vol-0034
v Status Code: VOL_VOLUME_NOT_MOUNTED_MAINT
v Message: A specified volume is not mounted in maintenance mode.
ENC-vol-0035
897
v Status Code: VOL_VOLUME_OFFLINE

v Message: A specified physical volume is not available for
read/write request.
ENC-vol-0036
v Status Code: VOL_VOLUME_SIZE_MISMATCH
v Message: A region or physical volume is too small.
ENC-vol-0037
v Status Code: VOL_VOLUME_STALE
v Message: A specified physical volume is stale.
ENC-vol-0038
v Status Code: VOL_NOT_IMPLEMENTED
v Message: The function is not supported on the current machine
type.
ENC-vol-0039
v Status Code: VOL_FILE_DESCR_EXHAUSTED
v Message: The process limit for open file descriptors has been
reached.
ENC-vol-0040
v Status Code: VOL_INVALID_LAYOUT
v Message: A vol_physLayout_t is invalid.
ENC-vol-0041
v Status Code: VOL_INTERNAL_ERROR
v Message: An unexpected error was encountered by the Volume
Service.
ENC-vol-0042
v Status Code: VOL_INVALID_LOCK_ID
v Message: The lock identifier is not valid for this volume.
ENC-vol-0043
898
v Status Code: VOL_INVALID_LOCK_TYPE

v Message: The specified lock type is invalid.
ENC-vol-0044
v Status Code: VOL_LOCKS_EXHAUSTED
v Message: The maximum number of allowed locks has been reached.
ENC-vol-0045
v Status Code: VOL_LOCK_EXPIRED
v Message: A lock was held too long.
ENC-vol-0046
v Status Code: VOL_SYNC_IN_PROGRESS
v Message: A sync is already executing on this logical volume.
ENC-vol-0047
v Status Code: VOL_VOLUME_MOUNTED_RESTORE
v Message: A specified logical volume is mounted in restore mode.
ENC-vol-0048
v Status Code: VOL_VOLUME_MOUNTED_MAINT
v Message: A specified logical volume is mounted in maintenance
mode.
ENC-vol-0049
v Status Code: VOL_ID_COLLISION
v Message: A volume with the specified id already exists
ENC-vol-0050
v Status Code: VOL_VOLUME_NOT_LOCAL
v Message: Specified volume is imported from another site
ENC-vol-0051
v Status Code: VOL_VOLUME_IS_EXPORTED
899
v Message: Specified physical volume is currently exported

ENC-vol-0052
v Status Code: VOL_VOLUME_NOT_EXPORTED
v Message: Specified physical volume is not exported
ENC-vol-0053
v Status Code: VOL_VOLUME_ALREADY_IMPORTED
v Message: Specified physical volume is already imported
ENC-vol-0054
v Status Code: VOL_INVALID_REMOTE_VOLUME_NAME
v Message: Name specified for remote volume is invalid
ENC-vol-0055
v Status Code: VOL_REMOTE_VOLUME_SERVICE_UNAVAILABLE
v Message: Volume service at remote site is not available
ENC-vol-0056
v Status Code: VOL_REMOTE_ACCESS_DENIED
v Message: Client is not authorized to access the server
ENC-vol-0057
v Status Code: VOL_OPERATION_NOT_APPLICABLE
v Message: Requested operation is not applicable to the specified
volume
Abort codes
The CICS Toolkit provides a common interface for obtaining information about
aborts. Using the abort facility, programmers can define abort codes for use when
explicitly aborting transactions. Applications aborting transactions can set abort
reasons, which are typically presented as strings or codes.
The CICS Toolkit also aborts transactions and uses abort codes to specify the
reasons for system-defined aborts. A CICS Toolkit abort code can be represented in
the following forms:
v A character string, such as ENC-txx-0003
v A C constant, such as TX_THREAD_EXIT_ABORT_CODE
v A hexadecimal number, such as 0x77a6f003
900
v A message string, such as Thread exited without calling tx_commit.

As with a status code, you can use the translateError command with any form of a
system-defined abort code (except the message string), and the command returns
the other forms, for example:
% translateError ENC-txx-0003
ENC-txx-0003: Thread exited without calling tx_commit.
[TX_THREAD_EXIT_ABORT_CODE] (0x77af003)
Note: The NLSPATH and LANG environment variables must be set for the
message string to be displayed in the output.
ENC-ppc-1025
v Abort String: ENC-ppc-1025
v Abort Code: PPC_EXEC_BACKOUT_ISSUED
v Message: An executive application has issued backout and has not
supplied its own abort reason
ENC-ppc-1026
v Abort Code: PPC_EXEC_CONV_OUTAGE
v Message: An executive conversation has failed at a point which
has resulted in a backout
ENC-ppc-1027
v Abort Code: PPC_EXEC_CONV_ABEND
v Message: An executive conversation has been abended at a point
which has resulted in a backout
ENC-ppc-1028
v Abort Code: PPC_EXEC_SEND_ERROR
v Message: An executive application has replied to a syncpoint by
sending an error indication
ENC-ppc-1029
v Abort Code: PPC_EXEC_TRAN_ERROR
v Message: Error returned on tran call at a PPC executive, most
likely tran_End has returned an error and there is no abort reason
already set; this could be set for an async abort
ENC-ppc-1030
v Abort Code: PPC_EXEC_MULTIPLE_INITIATORS
901
v Message: Multiple syncpoint initiators detected at a PPC

executive
ENC-ppc-1031
v Abort Code: PPC_EXEC_INTEROP_IMPLICIT_SYNCPOINT_ERROR
v Message: An error occurred which would have otherwise been
returned from a syncpoint call but since this is an interop
transaction, there is no way for the application to recover and
reissue the call
ENC-ppc-1032
v Abort Code: PPC_EXEC_ABORT
v Message: The transaction has been aborted at a PPC executive and
no more detail is available
ENC-ppc-1033
v Abort Code: PPC_GWY_SYNCPOINT_REFUSED
v Message: A SNA host has replied to a syncpoint by sending a
backout
ENC-ppc-1034
v Abort Code: PPC_GWY_BACKOUT_RECEIVED
v Message: A SNA host has initiated a backout
ENC-ppc-1035
v Abort Code: PPC_GWY_CONV_OUTAGE
v Message: A SNA conversation has failed at a point which has
resulted in a backout, possibly after resynchronization
ENC-ppc-1036
v Abort Code: PPC_GWY_CONV_ABEND
v Message: A SNA conversation has been abended at a point which has
resulted in a backout, possibly after resynchronization
ENC-ppc-1037
v Abort Code: PPC_GWY_SEND_ERROR
v Message: A SNA host has replied to a syncpoint by sending an
error indication
902
ENC-ppc-1038
v Abort Code: PPC_GWY_TRAN_ERROR
v Message: Error returned on tran call at a PPC gateway, it is
possible that there are multiple syncpoint initiators at different
gateways or that an async abort has occurred without setting a
reason
ENC-ppc-1039
v Abort Code: PPC_GWY_MULTIPLE_INITIATORS
v Message: Multiple syncpoint initiators detected at a PPC gateway
ENC-ppc-1040
v Abort Code: PPC_GWY_ABORT
v Message: The transaction has been aborted at a PPC gateway and no
more detail is available
ENC-ppc-1041
v Abort Code: PPC_EXEC_TIMEOUT
v Message: The transaction has timed out waiting for a tran outcome
ENC-tmx-1026
v Abort String: ENC-tmx-1026
v Abort Code: TMXA_PROTO_ERROR_CODE
v Message: The TM-XA protocol was violated.
ENC-tmx-1027
v Abort Code: TMXA_XA_ERROR_CODE
v Message: A TM-XA call failed.
ENC-tmx-1028
v Abort Code: TMXA_MODEL_LINKED_CODE
v Message: A transaction linked with this one failed.
ENC-tmx-1029
v Abort Code: TMXA_INTERNAL_ERROR_CODE
903
v Message: An error was detected in a TM-XA internal data

structure.
ENC-tmx-1030
v Abort Code: TMXA_TRAN_ERROR_CODE
v Message: A Transaction Service call failed.
ENC-tmx-1031
v Abort Code: TMXA_MISSING_RECOVERY_SERVICE_CODE
v Message: Application is not recoverable.
ENC-tra-1025
v Abort String: ENC-tra-1025
v Abort Code: TRAN_ABORT_CLIENT_ABORT
v Message: A client (not the transaction service) aborted
ENC-tra-1026
v Abort Code: TRAN_ABORT_HEURISTIC_ABORT
v Message: Some application forced a partial outcome.
ENC-tra-1034
v Abort Code: TRAN_ABORT_UNILATERAL_ABORT
v Message: Abort information is unavailable due to crash or lost
communication
ENC-tra-1035
v Abort Code: TRAN_ABORT_REINFECTION
v Message: A new request arrived after voting read-only
ENC-tra-1036
v Abort Code: TRAN_ABORT_WORK_AFTER_PREPARE_CRASHED
v Message: Unprepared work was discovered after a crash
ENC-tra-1037
v Abort Code: TRAN_ABORT_INVALID_TRAN_MESSAGE
v Message: A protocol violation was detected
904
ENC-tra-1064
v Abort Code: TRAN_ABORT_PREPARE_INFERIORS_TIMEOUT
v Message: The prepare phase timed out
v Explanation: The transaction has been aborted because the prepare
phase timed out. By default, this message is attempted five times,
delaying for ten seconds between attempts.
v User Response: If all participants are believed to be running and
reachable, use trpc=all,tran=basic tracing to determine the underlying
cause of the RPC failure.
ENC-tra-1065
Abort Code: TRAN_ABORT_COORDINATOR_MIGRATION_FAILURE
Message: Coordinator migration timed out
Explanation: The transaction has been aborted because coordinator
migration timed out. By default, this message is attempted five times,
delaying for ten seconds between attempts.
v User Response: If all participants are believed to be running and
reachable, use trpc=all,tran=basic tracing to determine the underlying
cause of the RPC failure.
v
v
v
v
ENC-tra-1124
v Abort Code: TRAN_ABORT_ANCESTOR_ABORTED
v Message: An ancestor transaction aborted.
ENC-tra-1125
v Abort Code: TRAN_ABORT_COMMITTED_CHILD_ABORTED
v Message: A child transaction was aborted after it had ended.
ENC-tra-1126
v Abort Code: TRAN_ABORT_FAMILY_ABORT
v Message: The application aborted the entire family.
ENC-tra-1134
v Abort Code: TRAN_ABORT_PREPARE_FAILED
v Message: A recovery service refused to prepare
ENC-tra-1135
v Abort Code: TRAN_ABORT_NO_SUITABLE_COORDINATOR
905

v Message: All acceptable applications refused to coordinate
v Explanation: The transaction has been aborted because no suitable
participant agreed to coordinate commitment of the transaction. A
distributed transaction requires at least one recoverable participant to fill
this role.
ENC-tra-1136
v Abort Code: TRAN_ABORT_MISMATCHED_COORDINATOR
v Message: Coordinator selections conflicted
ENC-tra-1137
v Abort Code:
TRAN_ABORT_ASYNCHRONOUS_WORK_DURING_PREPARE
v Message: Prepare callbacks returned while requests were
outstanding
ENC-tra-1138
v Abort Code: TRAN_ABORT_ILLEGAL_LAST_CALL
v Message: The last call optimization was used illegally
ENC-trc-1025
v Abort String: ENC-trc-1025
v Abort Code: TC_UNKNOWN_ABORT_REASON_CODE
v Message: Unknown abort reason
ENC-trc-1026
v Abort Code: TC_SERVER_SHUTDOWN_CODE
v Message: Server was shutdown
ENC-trc-1027
v Abort Code: TC_APPL_EXIT_CODE
v Message: Application exited
ENC-trc-1028
v Abort Code: TC_CONC_STMT_ABORT_CODE
v Message: One or more subtransactions aborted
ENC-trc-1029
906
v
v
v
v
Abort String: ENC-trc-1029

Abort Code: TC_CONC_STMT_INSUFF_THREADS_CODE
Message: Failed to create requested number of threads
ENC-trc-1030
v Abort Code: TC_DEADLOCK_DETECTED_CODE
v Message: Transaction was deadlocked
ENC-trc-1031
v Abort Code: TC_RPC_FAILURE_CODE
v Message: RPC Failure:
v Explanation: A transactional RPC (TRPC) failure has been caught by
the Transactional-C library. This could be caused by a wide range of
environmental problems, from a transient communication error to the
termination of the server process.
v User Response: Use default trpc tracing to identify the RPC exception
caught and verify the validity of the binding used for the RPC. Ensure
that the client process has a valid login context and check the viability of
the server using rpcutil ping server.
ENC-trc-1032
v Abort Code: TC_MEMORY_EXHAUSTED_CODE
v Message: Transactional memory allocation failed
ENC-trc-1033
v Abort Code: TC_CAUGHT_ADDRESS_EXCEPTION_CODE
v Message: Uncaught address exception
ENC-trc-1034
v Abort Code: TC_CAUGHT_STATUS_EXCEPTION_CODE
v Message: Uncaught status exception:
ENC-trc-1035
v Abort Code: TC_CAUGHT_ABORT_EXCEPTION_CODE
v Message: Transactional-C ABORT exception caught
ENC-txx-0001
v Abort String: ENC-txx-0001
v Abort Code: TX_TIMEOUT_ABORT_CODE
907
v Hexadecimal ID: 0x77a6f001

v Message: Transaction timeout expired.
ENC-txx-0002
v
v
v
v
Abort String: ENC-txx-0002

Abort Code: TX_ROLLBACK_ABORT_CODE
Hexadecimal ID: 0x77a6f002
Message: tx_rollback was called.
ENC-txx-0003
v Abort String: ENC-txx-0003
v Abort Code: TX_THREAD_EXIT_ABORT_CODE
v Hexadecimal ID: 0x77a6f003
v Message: Thread exited without calling tx_commit.
908

ERZ-thd-0001 An address exception (%1$08X) has
occurred
Explanation:
The program referenced an address that was either not
mapped or does not have write permission.
User response:
Contact your support representative.
ERZ-thd-0003 An uninitialized exception has been
raised
Explanation:
Data was not properly initialized.
User response:
ERZ-thd-0005 An invalid address exception has
been raised
Explanation:
The program referenced an address that was either not
mapped or protected against modification.
User response:
ERZ-thd-0007 An insufficient memory exception
has been raised
Explanation:
The application either exceeded its memory limitation or
the system has exhausted its virtual memory.
User response:
ERZ-thd-0019 A broken pipe exception has been
raised
Explanation:
A broken pipe signal that was not handled has
occurred.
User response:
ERZ-rpc-0001
Operation out of range
Explanation:
A client called the nth operation in an interface but the
server supports fewer than n-1 operations from the
interface.
User response:
Modify the server to support the addition operations or
arrange for the client to find a server that supports the
requested operation.
ERZ-rpc-0002
Cannot create socket
Explanation:
An underlying problem prevented the RPC runtime from
creating a communications socket needed to make or
receive remote calls.
User response:
Contact your support representative
ERZ-rpc-0003
Cannot bind socket
Explanation:
RPC runtime could not assign an endpoint to a
communication socket.
User response:
ERZ-rpc-0013
Input arguments too big
Explanation:
The size of the input arguments to a remote call was
larger than is allowed in the current context. For
example, in broadcast calls the input arguments must fit
into a single transport-level packet.
User response:
Reduce the size of input arguments.
ERZ-rpc-0018
No memory for RPC runtime
Explanation:
The RPC runtime was not able to allocate heap storage,
or a fixed buffer supplied to IDL Encoding Services was
not large enough.
Explanation:
A parameter that is not valid has been detected for a
threads operation.
User response:
If the failure is caused by overuse of the underlying
system resources, such as address space or swap
space, reduce the direct use of these resources by the
application if possible, or use a larger buffer when
calling IDL Encoding Services.
User response:
ERZ-rpc-0020
ERZ-thd-0050 An Invalid parameter exception has

been raised
Call faulted
Explanation:
909
ERZ-rpc-0022 ERZ-rpc-0038
The execution of an application manager routine, such
as a division by zero, raised a fault or exception.
Applications usually do not see this error as it is
intercepted by the client stub and transformed into the
specific error condition that occurs in the application
manager routine.
User response:
None required.
ERZ-rpc-0032
Explanation:
An application specified an RPC protocol sequence that
is not recognized by the RPC runtime.
User response:
Specify only valid RPC protocol sequences.
ERZ-rpc-0033
ERZ-rpc-0022
Communications failure
Explanation:
The RPC runtime that was attempting to implement a
call to a remote procedure gave up waiting for the
execution of the procedure to start or complete because
the RPC runtime determined that it was not
communicating with the server.
User response:
Try another server.
ERZ-rpc-0026
RPC coding error
Explanation:
An internal error occurred.
User response:
Contact your service representative.
ERZ-rpc-0028
Call thread not found
Explanation:
An internal error occurred. This error occurs when the
call queue is full. Client requests are coming in faster
than they can be executed and eventually the call
queue fills up. This status is translated and returned to
the calling client as rpc_s_server_too_busy.
User response:
ERZ-rpc-0029
Invalid binding
Explanation:
RPC runtime was passed a binding handle that is not
valid.
Invalid RPC protocol sequence
Descriptor not registered
Explanation:
User response:
ERZ-rpc-0035
No protocol sequences
Explanation:
An application requested a list of the protocol
sequences supported by the RPC runtime, but none are
supported.
User response:
This may be an internal error. Report the error to your
service representative.
ERZ-rpc-0036
No protocol sequences registered
Explanation:
A server application called rpc_server_listen but did not
previously call rpc_server_use_protseq or one of its
variants.
User response:
ERZ-rpc-0037
No bindings
Explanation:
An application passed an empty or null binding vector
as input to the RPC runtime or requested a binding
vector to be returned by the RPC runtime, but no
bindings exist.
User response:
User response:
In the first case, change the application to pass a valid
binding vector. The second case may not indicate an
error condition.
ERZ-rpc-0031
ERZ-rpc-0038
Endpoint not found
Explanation:
User response:
Max descriptors exceeded
Explanation:
An application caused the RPC runtime to use more file
descriptors for communications sockets than the runtime
is able to store internally.
User response:
File descriptors used by the RPC runtime can be
reduced by making fewer remote calls in parallel, or by
calling rpc_server_use_protseq, or one of its variants,
fewer times.
910
ERZ-rpc-0039
No interfaces
Explanation:
An application requested a list of the network interfaces
registered by a server but no interfaces were registered.
User response:
Check that a server instance exporting the desired
interfaces is running.
ERZ-rpc-0040
User response:
Supply a valid timeout value.
Cannot inquire socket
Explanation:
The RPC runtime tried to get information about a
communications socket but failed due to an underlying
problem.
User response:
ERZ-rpc-0044
Unknown interface
Explanation:
A client application tried to make a remote call using an
interface that the server being called does not support.
This condition also includes the binding specifying a
server that does not support the RPC management
service such as the rpc_mgmt_* routines.
User response:
The client may have bound to a server that is not
appropriate. Bind the client again to another server, or
modify the application code to use the correct decoding
call.
ERZ-rpc-0045
Unsupported type
Explanation:
A client application tried to make a remote call using a
binding handle whose associated object UUID has a
type that is not supported for the interface being used.
User response:
Either the client established a binding with a server that
is not appropriate, and the client should bind again to
another server, or an application error exists.
ERZ-rpc-0046
ERZ-rpc-0047
No fault
Explanation:
User response:
Report the error to your service representative.
Invalid timeout
Explanation:
An application specified a timeout value that was not
valid to rpc_mgmt_set_com_timeout.
ERZ-rpc-0041
User response:
Change the application to make only supported calls.
Invalid call option
Explanation:
A call was attempted that is not supported by the
underlying RPC protocol. For example, calls to
procedures marked [broadcast] are not supported by all
RPC protocols.
ERZ-rpc-0048
Cancel timeout
Explanation:
A cancel was posted to a thread making a remote call,
a finite cancel timeout was previously specified by
rpc_mgmt_set_cancel_timeout, and the manager routine
did not respond to the cancel within the cancel timeout
period.
User response:
None required.
ERZ-rpc-0049
Call canceled
Explanation:
A cancel was posted to a thread making a remote call.
This error condition occurs at the server but is usually
not seen by the server application.
User response:
None required.
ERZ-rpc-0052
Cannot connect
Explanation:
An internal error occurred. The connection has been
aborted by either the client or server RPC runtime.
User response:
ERZ-rpc-0053
Connection aborted
Explanation:
An internal error occurred. The connection has been
aborted by either the client or server RPC runtime.
User response:
ERZ-rpc-0054
Connection closed
Explanation:
The underlying connection has failed.
User response:
Verify the underlying connection and try the operation
again.
911
ERZ-rpc-0055
Cannot accept
Explanation:
An internal error occurred. The listener thread cannot
accept the connection .
User response:
ERZ-rpc-0056
User response:
Invalid object
Explanation:
An application specified a UUID value that is not legal
or specified a value that was not a valid UUID.
User response:
Verify that the provided value is a UUID and that the
called routine allows that value. Some routines do not
allow a nil UUID.
ERZ-rpc-0062
Explanation:
An endpoint string with syntax that is not valid was
supplied as input to the RPC runtime.
User response:
Use valid endpoint string syntax.
Association group not found
Explanation:
ERZ-rpc-0058
ERZ-rpc-0078 Invalid endpoint format for remote

host
Protocol error
ERZ-rpc-0080 Unknown or unsupported manager

type
Explanation:
A client application tried to make a remote call using a
binding handle whose associated object UUID has a
type that is not supported for the interface being used.
User response:
Either the client bound to a server that is not
appropriate, in which case it should bind again to
another server, or there is an application error.
ERZ-rpc-0082 Association group maximum
exceeded
Explanation:
An internal error occurred. The maximum number of
associations per association group was exceeded.
Explanation:
User response:
User response:
ERZ-rpc-0084
ERZ-rpc-0064
Explanation:
An internal error occurred. The state machine state is
not valid.
Invalid string binding
Explanation:
An application presented a string binding as input to the
RPC runtime and the string binding has syntax that is
not valid.
User response:
Use the correct string binding syntax.
ERZ-rpc-0066
Connection request rejected
Explanation:
The server rejected the connection request from the
client. This can be because the server has reached its
maximum allowable connect requests.
User response:
The server may be receiving too many simultaneous
client requests. The client can try the server again or try
contacting a different server.
Invalid state machine state
User response:
ERZ-rpc-0086
Association shutdown
Explanation:
An internal error occurred. The client runtime has
received a shutdown request from the server runtime.
User response:
ERZ-rpc-0087
Transfer syntaxes unsupported
Explanation:
An internal error occurred. The proposed transfer syntax
is not supported by the server.
User response:
912
ERZ-rpc-0088
Context id not found
Explanation:
User response:
ERZ-rpc-0090
No addresses
Explanation:
User response:
ERZ-rpc-0092
Cannot get interface ID
Explanation:
The RPC runtime tried to get information about a
communications socket but failed due to an underlying
problem.
User response:
ERZ-rpc-0093
Protocol sequence not supported
Explanation:
An application specified an RPC protocol sequence that
is recognized but is not supported by the RPC runtime.
User response:
Specify only RPC protocol sequences supported by
your service representative.
ERZ-rpc-0099
Explanation:
An aspect of the arguments supplied as input to the
RPC runtime is not appropriate.
User response:
Ensure that your arguments for the call are correct. See
the documentation if needed.
ERZ-rpc-0100
Call orphaned
Explanation:
A client application has given up waiting for a manager
routine to return. This error occurs at the server but is
usually not seen by the server application.
User response:
Use another operation.
ERZ-rpc-0101
ERZ-rpc-0096
Unknown reject
Wrong kind of binding
Explanation:
An application specified a client binding handle as input
to an RPC runtime routine that expects a server binding
handle. Or, an application specified a server binding
handle as input to an RPC runtime routine that expects
a client binding handle.
User response:
Change the application to use the correct kind of
binding handle.
Call queued
Explanation:
An internal status code.
User response:
None required.
ERZ-rpc-0105
User response:
None required.
Not supported
Explanation:
The requested operation is not supported by the RPC
runtime. In the case of
rpc_mgmt_set_server_stack_size, the underlying thread
package does not support setting the stack size.
ERZ-rpc-0103
ERZ-rpc-0094
Invalid argument
Not an RPC tower
Explanation:
An internal status code. The protocol tower from the
endpoint mapper is not an RPC tower.
Explanation:
User response:
User response:
ERZ-rpc-0108
ERZ-rpc-0097
Type already registered
Explanation:
A server application tried to register an interface and
type, by means of rpc_server_register_if, that was
previously registered.
Call timed out
Explanation:
A remote call did not return before the timeout set by
rpc_mgmt_set_call_timeout expired.
User response:
None required.
User response:
Remove the redundant registration or unregister the
previously registered interface before registering.
913
ERZ-rpc-0109
Management operation disallowed
Explanation:
A client application called one of the management RPC
runtime functions and the remote server would not run
it.
User response:
Check the permissions and run the operation again.
ERZ-rpc-0110
Manager not entered
Explanation:
An internal status code.
User response:
None required.
ERZ-rpc-0111 Calls too large for well known
endpoint
Explanation:
The specified value of argument max_call_requests
exceeds the maximum allowed when using an endpoint
that is well known.
User response:
Specify a max_call_requests value of
rpc_c_protseq_max_reqs_default to obtain the
maximum value allowed for the specified protocol
sequence.
ERZ-rpc-0112
Server too busy
Explanation:
Client requests are coming in faster than they can be
executed by the server. The call queue of the server
reached the maximum client requests allowed.
User response:
A client can try the operation again with a different
server or wait a period of time and try again when the
current sever is less busy. Otherwise, the server can be
modified to increase the number of concurrent calls that
can be run by providing a larger max_calls_exec.
ERZ-rpc-0114
RPC protocol version mismatch
Explanation:
User response:
ERZ-rpc-0115
ERZ-rpc-0117
Fault context mismatch
Explanation:
A client application passed a context handle into a
remote call, but the server detected that the server does
not hold the specified context. This error can happen if
a server stops and starts again in between remote calls
from the client holding the context handle and the client
calls the server that started again.
User response:
ERZ-rpc-0125
Fault invalid bound
Explanation:
An application made a remote call that attempted to
pass or return an array with a dynamically specified
bound that is not appropriate to the declared
dimensions of the array.
User response:
Fix the application.
ERZ-rpc-0126
Fault invalid tag
Explanation:
An application made a remote call that attempted to
pass or return a discriminated union with a tag that was
no valid.
User response:
ERZ-rpc-0133
Fault remote communication failure
Explanation:
A server stub encountered a communications error.
User response:
The client code must recover from a remote call that
was not successful.
ERZ-rpc-0134
Fault remote no memory
Explanation:
A server stub or application manager routine was not
able to allocate heap storage.
User response:
If the failure is caused by overuse of underlying system
resources, such as address space or swap space,
ensure that the application uses as few system
resources as possible.
No import cursor
Explanation:
User response:
ERZ-rpc-0135
Fault unspecified
Explanation:
A server stub or application manager routine raised an
exception of an unknown kind.
User response:
914
ERZ-rpc-0136
Bad UUID version
Explanation:
An application passed a UUID as input to the RPC
runtime but the UUID was not recognized.
User response:
ERZ-rpc-0141
Internal error
Explanation:
User response:
ERZ-rpc-0142
User response:
Invalid string UUID
Explanation:
The contents of the string passed to uuid_from_string
were not in the valid UUID string format.
User response:
Supply a correctly formatted UUID.
ERZ-rpc-0161
Invalid inquiry context
Explanation:
An inquiry context that was not valid was passed to a
begin, next, or done operation.
User response:
Verify that the inquiry context is non-null and was
successfully created in a begin operation.
ERZ-rpc-0167
ERZ-rpc-0170
Profile element not found
Explanation:
The server or management application called
rpc_ns_profile_elt_remove specifying a profile member
name that was not found in the endpoint map.
User response:
Use the RPC control program to see if the profile
element exists. If it does not, correct the application. If
the profile element does exist in the endpoint map,
report the problem to your service representative.
UUID coding error
Explanation:
ERZ-rpc-0143
Make sure that the inquiry_type argument passed to

rpc_ns_profile_elt_inq_begin or
rpc_mgmt_ep_elt_inq_begin is within the set of
supported values.
No more profile elements
Explanation:
No more profile elements are found in the profile
lookup.
ERZ-rpc-0171
Profile element replaced
Explanation:
The profile element that the server or management
application is adding already exists in the endpoint map.
The old element was replaced.
User response:
None required.
ERZ-rpc-0181
No more bindings
Explanation:
A client or management application performing a lookup
operation on a endpoint map entry exhausted the list of
compatible bindings that were exported.
User response:
None required.
ERZ-rpc-0189
Invalid interface version option
Explanation:
The specified vers_option argument value was not valid.
User response:
Check the value provided and use one of the API
defined constants rpc_c_vers_*.
ERZ-rpc-0197
Unknown sockaddr
User response:
Explanation:
ERZ-rpc-0169
User response:
Invalid inquiry type
Explanation:
The application program attempted to perform a lookup
in either a profile or an endpoint map using a lookup
key that is not supported.
User response:
ERZ-rpc-0198
Unknown tower
Explanation:
User response:
915
ERZ-rpc-0200
Max calls (threads) too small
ERZ-rpc-0209
Cannot access endpoint database
Explanation:
A server application passed too small a value as the
max_calls_exec input parameter to rpc_server_listen.
Explanation:
The endpoint mapper could not open the existing
database file that holds the endpoint map.
User response:
Pass a large enough value for parameter
max_calls_exec.
User response:
Check the permissions on the database file.
ERZ-rpc-0201
cthread create failed
Explanation:
User response:
ERZ-rpc-0204
User response:
ERZ-rpc-0205 Cannot perform endpoint map
operation
Explanation:
An endpoint map operation was not performed because
of command arguments that are not valid or internal
data base management errors.
User response:
Check the command arguments or any internal data
base management errors. If the operation fails again,
contact your service representative.
Invalid endpoint database
Explanation:
The format of the database file that holds the endpoint
map was not what the endpoint mapper expects.
User response:
Delete the database file and start the endpoint mapper
again.
ERZ-rpc-0208
Cannot create endpoint database
Explanation:
The endpoint mapper could not create the database file
that holds the endpoint map.
User response:
Check the permissions on the database file and the
directory that contains the file.
916
Explanation:
The database file that holds the endpoint map could not
be opened because another process had the file locked.
User response:
cthread invoke disabled
Explanation:
ERZ-rpc-0207
ERZ-rpc-0210 Endpoint database already open by

another process
ERZ-rpc-0211
Invalid endpoint entry
Explanation:
An entry supplied to an endpoint map operation as input
contains data that is not valid, for example, a tower.
User response:
Correct the contents of the entry.
ERZ-rpc-0212
Cannot update endpoint database
Explanation:
The endpoint map operation was unable to write
modifications to the database file that holds the
endpoint map.
User response:
Check the permissions on the database file.
ERZ-rpc-0213 Invalid endpoint map or lookup
context
Explanation:
A context handle supplied as input to an endpoint map
operation referred to context that was not valid. This
may be an internal error.
User response:
ERZ-rpc-0214
Not registered in endpoint map
Explanation:
An entry supplied as input to an endpoint map
operation, for example, deletion, does not exist in the
endpoint map.
User response:
Supply only existing entries when deleting.
ERZ-rpc-0218 Unidentified communications error
in client stub
Explanation:
A communications error detected by the client stub
could not be mapped to an exception. Note that this
status is only used as the status value of the
rpc_x_unknown_error exception.
User response:
This error should be reported to your service
representative. All client communication errors should
result in identifiable exceptions. However, as a
workaround, the rpc_x_unknown_error exception can be
handled as a client communications error.
ERZ-rpc-0221 A client side context handle has
been incorrectly modified
Explanation:
The client side representation of a context handle was
changed while a remote procedure call was in progress.
User response:
Make sure there is no client-side thread, running
concurrently with the remote procedure call, that
modifies the context handle during the run of the remote
call.
ERZ-rpc-0222 Null value of [in] context handle or
all [in,out] context handles
Explanation:
If an operation has [in] or [in,out] context handle
parameters, the binding for that operation is determined
using those parameters. A null context handle does not
refer to valid binding information.
User response:
Make sure that all [in] context handles are non-null. If
the operation has [in,out] context handle parameters but
no [in] context handles, make sure that at least one of
the [in,out] context handles is non-null.
ERZ-rpc-0223
Persistent errors on socket
Explanation:
The RPC runtime encountered repeated errors using a
communication socket.
User response:
ERZ-rpc-0228
Call ID in packet unknown
Explanation:
User response:
ERZ-rpc-0229
Key ID in packet unknown
Explanation:
An internal error occurred. Key Identifier in packet is not
known.
User response:
ERZ-rpc-0251 Binding incomplete (no object ID
and no endpoint)
Explanation:
The specified server binding information was
insufficient. In a management call to the RPC runtime,
the client-supplied binding information lacked an
endpoint and an associated object UUID.
User response:
Supply complete binding information and an object
UUID to management calls.
ERZ-rpc-0253 Interfaces stub/runtime version is
unknown
Explanation:
An application supplied an interface handle that referred
to an interface that specified an unknown stub or
runtime interface version. Either the handle is not valid,
did not point to an interface, or there is a version skew
between the IDL compiler and the RPC runtime used by
the application developer.
User response:
Make sure the handle is valid and that correct versions
of the IDL compiler and RPC runtime are used.
ERZ-rpc-0254
Interfaces version is unknown
Explanation:
An application supplied an interface handle that referred
to an interface that specified an unknown interface
format version.
User response:
Make sure the handle is valid and that correct versions
of the IDL compiler and the RPC runtime are used.
ERZ-rpc-0258
No manager EPV available
Explanation:
The rpc_server_register_if routine was called specifying
the default manager Entry Point Vector, but no manager
Entry Point Vector exists. The server stub was
generated using -no_mepv.
User response:
Generate the server stub again without specifying
-no_mepv or provide a manager Entry Point Vector.
917
ERZ-rpc-0259
Stub or runtime protocol error
Explanation:
An internal stub or runtime error occurred.
User response:
ERZ-rpc-0271
Listener thread is not running
Explanation:
A request has been made through the
rpc_mgmt_stop_server_listening call to stop the listener
thread but the listener thread is not running.
User response:
Depending upon what the caller of
rpc_mgmt_stop_server_listening expected, this may be
expected behavior or it may indicate an application
program logic error. Check the program logic again.
ERZ-rpc-0272 Buffer not usable by IDL Encoding
Services
Explanation:
A buffer handed to the IDL Encoding Services was not
8-byte aligned or was not a multiple of 8 bytes.
User response:
Modify the application code so that the buffer is aligned
on an 8-byte boundary and is a multiple of 8 bytes long.
ERZ-rpc-0273 Action cannot be performed by IDL
Encoding Services
Explanation:
Either the action requested in the handle being used
was inconsistent with what was specified in the ACF, or
idl_es_inq_encoding_id was called with an encoding
handle that has not yet been used for any operation.
User response:
In the first case, compile the stubs again using a
modified ACF. In the second case modify the application
code so that it does not make this call.
ERZ-rpc-0275
User defined exception received
Explanation:
This status is given to a [fault_status] parameter if the
server returned a user exception.
User response:
Application dependent.
ERZ-rpc-0276 Conversion between codesets not
possible
Explanation:
This status is used by International Character code set
conversion routines to indicate that conversion between
the network and local code sets is not possible.
User response:
ERZ-rpc-0280
Explanation:
The rpc_cs_get_tags routine found that the extended
binding handle for I18N operation was broken.
User response:
If the rpc_cs_get_tags routine is called directly from a
user program, the user program may not have modified
the binding handle correctly. In this case, the user must
write his own get_tags routine. If the user program uses
the default RPC runtime I18N functionality, report the
error to your service representative.
ERZ-rpc-0282 Invalid character input for
conversion
Explanation:
Either the iconv routine or an X/Open Portability Guide
Version 4 multibyte conversion routine detected
character input that is not valid, for example, multibyte
input or lock-shift sequence that spans the input buffer
boundary, or an input character that is not in the set of
characters from which it is being converted was used.
User response:
ERZ-rpc-0283 No room to place the converted
characters
Explanation:
An iconv conversion routine detected that there was no
room left in the output buffer to place the converted
characters.
User response:
ERZ-rpc-0284 iconv failed other than conversion
operation
Explanation:
The iconv command failed with an error that was not a
conversion error.
User response:
ERZ-rpc-0286
Character sets are not compatible
Explanation:
The code set evaluation routine examines character set
compatibility before it checks code set compatibility,
because connecting different languages, English and
Chinese, for example, could result in massive data loss.
The evaluation routine detected that the server and
client do not share the same language.
User response:
918
I18N tags structure is not valid
ERZ-rpc-0288 Value not found in the code set
registry
Explanation:
The requested value, for example local code set name
or registry code set value, was not found in the code set
registry.
User response:
ERZ-rpc-0289 No local code set name exists in the
code set registry
Explanation:
The code set registry ID value rgy_code_set_value
passed to an rpc_rgy_* did not have a corresponding
locale code set name. This implies the code set is not
supported in your environment.
User response:
Ensure that the application uses a supported code set.
ERZ-rpc-0290 Cannot open the code set registry
file
Explanation:
The code set registry file could not be opened. The path
name to the code set registry file may not have been
specified correctly, or the permissions on the file may
have prevented access.
User response:
Check permissions on the code set registry file.
ERZ-rpc-0326 Illegal state transition detected in

CN server association state machine
[cur_state: %s, cur_event: %s, assoc:
%x]
Explanation:
An internal error occurred. A state transition that is not
legal was detected.
User response:
CN client association state machine
[cur_state: %s, cur_event: %s, assoc:
%x]
Explanation:
User response:
CN server association group state
machine [cur_state: %d, cur_event:
%d, grp: %x]
Explanation:
legal was detected.
User response:
ERZ-rpc-0291 Cannot read the code set registry

file

CN client association group state
machine [cur_state: %d, cur_event:
%d, grp: %x]
Explanation:
A read error occurred when reading the code set
registry.
Explanation:
legal was detected.
User response:
This is probably a problem in the underlying operating
system. Check that the file can be read, or notify your
system administrator.
User response:
ERZ-rpc-0292 Cannot allocate memory for code

set info

CN server call state machine
[cur_state: %d, cur_event: %d,
call_rep: %x]
Explanation:
Memory allocation failed within the code set registry
access routines.
Explanation:
legal was detected.
User response:
If the failure is caused by overuse of underlying system
resources, such as address space or swap space,
ensure that the application uses as few system
resources as possible.
User response:
919
CN client call state machine [cur_state:
%d, cur_event: %d, call_rep: %x]
Explanation:
legal was detected.
User response:
ERZ-rpc-0333 (receive_packet) assoc->%x %s:
Protocol version mismatch major->%x minor->%x
Explanation:
An internal error occurred. Protocol versions do not
match.
User response:
ERZ-rpc-0334 (receive_packet) assoc->%x
frag_length %d in header > fragbuf
data size %d
Explanation:
User response:
ERZ-rpc-0336
(%s) Unhandled call state: %s
Explanation:
User response:
ERZ-rpc-0337
%s failed: %s
Explanation:
A call to some internal routine or macro failed.
User response:
ERZ-rpc-0340
Explanation:
A call to some internal routine or macro on a server
failed.
User response:
ERZ-rpc-0344 (%s) Negotiated transfer syntax not
found in presentation context element
Explanation:
User response:
ERZ-rpc-0345 (%s) Inconsistency in ACC_BYTCNT
field
Explanation:
User response:
ERZ-rpc-0349 (%s) Unaligned
RPC_CN_PKT_AUTH_TRL
Explanation:
Authorization trailer on Connection Oriented RPC
Protocol protocol packet was not properly aligned.
User response:
ERZ-rpc-0350 (%s) Unexpected exception was
raised
Explanation:
An unexpected exception was caught by the RPC
runtime.
User response:
ERZ-rpc-0351
ERZ-rpc-0338
%s: call failed
Explanation:
User response:
%s failed, errno = %d
(%s) No stub data to send
Explanation:
No stub data was given to a routine to be sent.
User response:
ERZ-rpc-0352
ERZ-rpc-0339
%s on server failed: %s
(%s) Event list full
Explanation:
Explanation:
An event list of the state machine was full when an
attempt was made to put an event on it.
User response:
User response:
920
ERZ-rpc-0353 ERZ-svc-0001
ERZ-rpc-0353
(%s) Unknown socket type
Explanation:
The socket corresponding to a file descriptor is of an
unknown type.
User response:
ERZ-rpc-0361
Explanation:
A call to malloc failed to return memory.
User response:
Increase available memory and swap space if needed.
ERZ-rpc-0362
ERZ-rpc-0354
(%s) Call not implemented
Explanation:
A call to a routine that was not implemented was made
by the RPC runtime.
User response:
ERZ-rpc-0355
(%s) Invalid call sequence number
Explanation:
An RPC call structure was allocated or initialized with a
sequence number that was not valid.
User response:
ERZ-rpc-0356
(%s) Cant create UUID
Explanation:
A UUID could not be created.
User response:
(%s) Memory allocation failed
(%s) Memory reallocation failed
Explanation:
A call to realloc failed to return memory.
User response:
ERZ-rpc-0366 Out of memory while trying to run
down contexts of client %x
Explanation:
No memory was available from the operating system.
User response:
ERZ-rpc-0367 Exception in routine at %x, running
down context %x of client %x
Explanation:
An exception was caught by the runtime while trying to
rundown client context.
User response:
Fix the context rundown routine to avoid raising the
exception, or to CATCH it.
ERZ-rpc-0358 (%s) DG packet free pool is

corrupted
ERZ-rpc-0368
Explanation:
The packet free pool of the Connectionless RPC
Protocol datagram is corrupted.
Explanation:
A server stub or application manager routine received
an error status back from a code set conversion routine.
User response:
User response:
The data being converted is not valid or the conversion
routine that you supplied needs to be fixed.
ERZ-rpc-0359 (%s) Attempt to free already-freed

DG packet
Explanation:
An attempt was made to free a Connectionless RPC
Protocol datagram packet already on the free list of the
packet pool.
ERZ-rpc-0369
Fault codeset conversion error
codeset conversion error
Explanation:
A server stub or application manager routine received
an error status back from a code set conversion routine.
User response:
User response:
There is invalid data being converted or the user
supplied conversion routine needs to be fixed.
ERZ-rpc-0360
ERZ-svc-0001
(%s) Lookaside list is corrupted
Out of memory
Explanation:
A lookaside buffer, internal data structure, was
corrupted.
Explanation:
Could not allocate memory for message table, string
copy, or other internal requirement.
User response:
User response:
921
ERZ-svc-0016 ERZ-lib-0036
Increase the swap or paging space or acquire more
physical memory. Also check the program for bugs that
resulted in bad pointers corrupting the heap allocation
area.
ERZ-svc-0016
Out of memory
Explanation:
Could not allocate memory for message table, string
copy, or other internal requirement.
User response:
Increase the swap or paging space or acquire more
physical memory. Also check the program for errors that
resulted in bad pointers corrupting the heap allocation
area.
ERZ-svc-0020 No permission to open message
catalog
Explanation:
Local file permissions prevented the program from
opening the message catalog for the specified message
identifier.
ERZ-lib-0011 Database open failure - permission

denied
Explanation:
The server does not have permission to open the
database file. The open call returned EACCES.
User response:
Run the process as the operating system user that has
permission to access the database or change the
permission of the database file itself, or the path to it.
ERZ-lib-0012
Database open failure
Explanation:
The underlying database-open procedure failed for
some reason. The global variable errno may provide
more specific information.
User response:
The global variable errno may indicate what action to
take.
ERZ-lib-0013
Database store failure
User response:
No action may be required; program will use the default
message text.
Explanation:
The underlying database-store procedure failed for
ERZ-svc-0021
User response:
take.
Message catalog does not exist
Explanation:
The message catalog for the specified message
identifier does not exist.
User response:
No action may be required; the program will use the
default message text.
ERZ-dhd-0101
Cannot allocate memory
Explanation:
Memory allocation operation failed.
User response:
Check memory limits on your machine, and increase
available memory, if possible.
ERZ-lib-0010
Database open failure - no such file

or directory
Explanation:
The specified database file or part of its path was not
found. The open call returned ENOENT.
User response:
Correct the pathname to the file you are attempting to
open.
ERZ-lib-0014
Database fetch failure
Explanation:
The underlying database-fetch procedure failed for
User response:
take.
ERZ-lib-0015
Database delete operation failure
Explanation:
The underlying database-delete procedure failed for
User response:
take.
ERZ-lib-0036
Cannot allocate memory
Explanation:
Memory allocation operation failed
User response:
922
ERZ-lib-0040 ERZ-cpc-0006
Check memory limits on your machine, and increase
available memory, if possible.
ERZ-lib-0040
Database file lock or unlock failed
Explanation:
Either dce_db_lock() or dce_db_unlock() detected an
error, returned by a file locking function.
User response:
take.
ERZ-lib-0041
Database file stat failed
Explanation:
The underlying database-stat function failed for some
reason. The global variable errno may provide more
specific information.
User response:
take.
ERZ-cpc-0001 Current user/group not authorized
to access CICS communications.
Explanation:
The machine does not have a cics user and/or group
defined (cicsgroup on Windows). You are a non-root
user and your primary group is not the cics group.
(cicsgroup on Windows). WINDOWS only: Internal
failure attempting to initialize security attributes.
User response:
If your system has the correct user and group
configuration and the error persists, contact your
support representative.
ERZ-cpc-0002 Failed to identify shared memory
segment key.
Explanation:
ftok failed with associated errno.
User response:
Indicates the file used as key to create shared memory
segment was removed.
ERZ-cpc-0003
Failed to access control file.
Explanation:
Unable to open control file specified in
CIPC_CONFIG_FILE environment variable or default
control file (/var/cics_servers/cicsipc/.cicsipc).
User response:
Check space available in the file system to create the
file (see above for file name and location). Check
permissions of directory and (if existing) file (see above
for file name and location) relative to your current user
ID. WINDOWS: If the file has the read-only attribute,
reset this so that the file may be deleted (NOTE: this
attribute must have been set by another person/process

as it is not set by CICS). If the file exists but with the
wrong ownership/permissions, correct them (should be
in the cics group [cicsgroup on Windows] and at least
deletable by cics processes). If the file exists, as a last
resort, and only if you are sure nobody is using the
CICS communication facilities, remove the file and retry.
Any CICS or CICS-related process, such as an SFS
server or PPC gateway, or even a cicscp command,
will use CICS communications facilities.
ERZ-cpc-0004 Failed to get a handle for the
shared memory segment.
Explanation:
Failed to create new shared memory segment based on
generated key/size. Failed to find an existing shared
memory segment based on generated key / size.
WINDOWS: Unable to create or access pagefile backed
shared memory segment.
User response:
Check size environment variable is not set to an
unacceptable value for the system (minimum: 8MB,
maximum: 128MB). Check your system still has enough
resources to create a segment of default size
(approximately 126MB on UNIX, 88MB on Windows).
WINDOWS: Check for existence of Windows named
object called CIPC_SharedSegment using WinObj or
similar tool (look in BaseNamedObjects folder) with
wrong permissions (cicsgroup should have:
Delete/Change Perms/Change Owner/Query
Data/Query State/Modify State) UNIX : Check for
existence of clashing shared memory segment
created/used by another process with incorrect
permissions and remove if it exists (ipcs -m, ipcrm -m
commands).
ERZ-cpc-0005 The shared memory segment was
created by someone that was neither
the cics user, nor in the cics group.
Explanation:
Unknown, perhaps an attempted hack (denial of service
or intercept). WINDOWS: This can also be caused by
someone else using the same object name
(\CIPC_SharedSegment\).
User response:
Remove the offending shared memory segment
manually and retry
ERZ-cpc-0006 Failed to attach the shared memory
segment to the process.
Explanation:
The default base address, (0x70000000 for UNIX,
0x50000000 for Windows), or the address specified in
the CIPC_SHMBASE environment variable are
unacceptable (may be in use by something else for
instance). The system is unable to perform the attach
for other, perhaps resource related, reasons.
923
ERZ-cpc-0007 ERZ-cpc-0015
User response:
Check your systems resources. Use CIPC_SHMBASE
to control the base address (this must be changed for
ALL CICS related processes so cannot simply be
changed for a single client for instance).
ERZ-cpc-0007 Unable to initialize the storage pool
in the shared segment.
Explanation:
Pool size set in CIPC_SHMSIZE environment variable is
too small.
User response:
Increase pool size set in CIPC_SHMSIZE variable.
ERZ-cpc-0008
User response:
Increase pool size set in CIPC_SHMSIZE environment
variable or use default pool size by resetting this
variable.
Explanation:
Control file permissions overridden incorrectly, check it
can be deleted by cics group (cicsgroup on Windows).
Insufficient authorization (not in cics group, nor user
root).
User response:
Obtain necessary authorization, for example by
changing to cics group or root user.
ERZ-cpc-0014 Unable to read control file
ownership and permissions.
Explanation:
Insufficient authorization (not in cics group, not root
user, file perms set incorrectly).
User response:
Obtain necessary authorization, for example by
changing to cics group or root user.
Failed to allocate shared memory.
Explanation:
Unable to allocate shared storage (check pool size is
sufficient, CIPC_SHMSIZE environment variable).
User response:
Increase pool size using CIPC_SHMSIZE environment
variable.
ERZ-cpc-0010 Failed to read or set uid/gid fields
of new shared memory segment to
cics/cics.
Explanation:
Insufficient permissions or system resource issue.
User response:
Obtain necessary permissions, for example changing to
cics group or root user.
ERZ-cpc-0011 Failed to set user/group
permissions of new control file.
Explanation:
Insufficient permissions or system resource issue.
User response:
Check the control file permissions and retry.
ERZ-cpc-0012 AIX kernel extensions are not
loaded.
Explanation:
Incorrectly installed or configured CICS system.
924
ERZ-cpc-0013 Unable to find shared segment or

delete control file.
Unable to create ERT thread.
Explanation:
Pool size set in CIPC_SHMSIZE environment variable is
too small.
ERZ-cpc-0009
User response:
Run cicsipc_cfg -l to ensure that CICS kernel extension
is loaded correctly.
ERZ-cpc-0015 Failed to check and/or initialize

garbage collector thread.
Explanation:
Unable to create or open garbage collector control file
(by default, /var/cics_servers/.cipc_gc, overridden by
CIPC_GC_FILE environment variable). Unable to create
garbage collector thread if required.
User response:
Check and obtain necessary permissions for
creating/accessing garbage collector control file. Check
system resources.
Notices
This information was developed for products and services offered in the U.S.A. IBM
may not offer the products, services, or features discussed in this document in other
countries. Consult your local IBM representative for information on the products and
services currently available in your area. Any reference to an IBM product, program,
or service is not intended to state or imply that only that IBM product, program, or
service may be used. Any functionally equivalent product, program, or service that
does not infringe any IBM intellectual property right may be used instead. However,
it is the users responsibility to evaluate and verify the operation of any non-IBM
product, program, or service.
IBM may have patents or pending patent applications covering subject matter
described in this document. The furnishing of this document does not give you any
license to these patents. You can send license inquiries, in writing, to:
IBM Director of Licensing
IBM Corporation
North Castle Drive
Armonk, NY 10504-1785
U.S.A.
For license inquiries regarding double-byte (DBCS) information, contact the IBM
Intellectual Property Department in your country or send inquiries, in writing, to:
IBM World Trade Asia Corporation Licensing
2-31 Roppongi 3-chome, Minato-ku
Tokyo 106, Japan
The following paragraph does not apply to the United Kingdom or any other
country where such provisions are inconsistent with local law:
INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS
DOCUMENT AS IS WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS
OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES
OR CONDITIONS OF NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS
FOR A PARTICULAR PURPOSE. Some states do not allow disclaimer of express
or implied warranties in certain transactions, therefore, this statement may not apply
to you.
This information could include technical inaccuracies or typographical errors.
Changes are periodically made to the information herein; these changes will be
incorporated in new editions of the document. IBM may make improvements and/or
changes in the product(s) and/or the program(s) described in this publication at any
time without notice.
Any references in this information to non-IBM Web sites are provided for
convenience only and do not in any manner serve as an endorsement of those
Web sites. The materials at those Web sites are not part of the materials for this
IBM product and use of those Web sites is at your own risk.
IBM may use or distribute any of the information you supply in any way it believes
appropriate without incurring any obligation to you.
Licensees of this program who wish to have information about it for the purpose of
enabling: (i) the exchange of information between independently created programs
925
and other programs (including this one) and (ii) the mutual use of the information
which has been exchanged, should contact:
IBM Corporation
ATTN: Software Licensing
11 Stanwix Street
Pittsburgh, PA 15222
U.S.A.
Such information may be available, subject to appropriate terms and conditions,
including in some cases, payment of a fee.
The licensed program described in this document and all licensed material available
for it are provided by IBM under terms of the IBM International Program License
Agreement or any equivalent agreement between us.
Any performance data contained herein was determined in a controlled
environment. Therefore, the results obtained in other operating environments may
vary significantly. Some measurements may have been made on development-level
systems and there is no guarantee that these measurements will be the same on
generally available systems. Furthermore, some measurements may have been
estimated through extrapolation. Actual results may vary. Users of this document
should verify the applicable data for their specific environment.
Information concerning non-IBM products was obtained from the suppliers of those
products, their published announcements or other publicly available sources. IBM
has not tested those products and cannot confirm the accuracy of performance,
compatibility or any other claims related to non-IBM products. Questions on the
capabilities of non-IBM products should be addressed to the suppliers of those
products.
All statements regarding IBMs future direction or intent are subject to change or
withdrawal without notice, and represent goals and objectives only.
This information contains examples of data and reports used in daily business
operations. To illustrate them as completely as possible, the examples may include
the names of individuals, companies, brands, and products. All of these names are
fictitious and any similarity to the names and addresses used by an actual business
enterprise is entirely coincidental.
If you are viewing this information softcopy, the photographs and color illustrations
may not appear.
Trademarks and service marks

The following terms are trademarks or registered trademarks of the IBM Corporation
in the United States, other countries, or both:
Advanced Peer-to-Peer Networking
AS/400
CICS/400
926
AIX
CICS
CICS/6000
CICS/ESA
CICS/MVS
CICS/VSE
CICSPlex
C-ISAM
Database 2
DB2
DB2 Universal Database
GDDM
IBM Registry
IBM
IMS
Informix
Language Environment
MVS
MVS/ESA
OS/390
OS/2
OS/400
RACF
RETAIN
RISC System/6000
RS/6000
SOM
Systems Application Architecture
System/390
TXSeries
TCS
VisualAge
VSE/ESA
VTAM
WebSphere
z/OS
Domino, Lotus, and LotusScript are trademarks or registered trademarks of Lotus

Development Corporation in the United States, other countries, or both.
ActiveX, Microsoft, Visual Basic, Visual C++, Visual J++, Visual Studio, Windows,
Windows NT, and the Windows 95 logo are trademarks or registered trademarks
of Microsoft Corporation in the United States, other countries, or both.
Java and all Java-based trademarks and logos are trademarks or registered
trademarks of Sun Microsystems, Inc. in the United States, other countries, or both.
UNIX is a registered trademark of The Open Group in the United States and other
countries.
Acucorp and ACUCOBOL-GT are registered trademarks of Acucorp, Inc. in the
United States, other countries, or both.
Pentium is a trademark of Intel Corporation in the United States, other countries,
or both.
This software contains RSA encryption code.
Other company, product, and service names may be trademarks or service marks
of others.
Notices
927
928
SC34-6639-02

Spine information:
Messages and Codes
Version 6.2
SC34-6639-02

TXSeries For Multiplatforms Messages and Codes Version 6.2

Cargado por

Información del documento

Título original

Derechos de autor

Formatos disponibles

Compartir este documento

Compartir o incrustar documentos

Opciones para compartir

¿Le pareció útil este documento?

¿Este contenido es inapropiado?

Copyright:

Formatos disponibles

TXSeries For Multiplatforms Messages and Codes Version 6.2

Cargado por

Copyright:

Formatos disponibles

TXSeries for Multiplatforms

Messages and Codes

TXSeries for Multiplatforms

Messages and Codes

Third Edition (January 2008)

Chapter 1. ERZxxx messages . . . . . . . . . . . . . . . . . . . 1

TXSeries for Multiplatforms: Messages and Codes

TXSeries for Multiplatforms: Messages and Codes

TXSeries for Multiplatforms: Messages and Codes

TXSeries for Multiplatforms: Messages and Codes

Chapter 4. CICS Toolkit message and codes . . . . . . . . . . .

TXSeries for Multiplatforms: Messages and Codes

About this book

Who should read this book

Conventions used in this book

Indicates values that you must use literally, such as commands,

Indicates text that you must enter at a command prompt. Monospace

Encloses the names of keys on the keyboard.

Where x is the name of a key, indicates a control-character

Copyright IBM Corp. 2001, 2008

Table 1. Conventions that are used in this book (continued)

Represents the UNIX command-shell prompt for a command that

Represents the UNIX command-shell prompt for a command that

Represents the Windows command prompt.

When used to describe a menu, shows a series of menu selections.

When instructed to enter or issue a command, type the command

Encloses optional items in syntax descriptions.

Encloses lists from which you must choose an item in syntax

Separates items in a list of choices enclosed in { } (braces) in syntax

Ellipses in syntax descriptions indicate that you can repeat the

In function descriptions, indicates parameters whose values are used

In function descriptions, indicates parameters whose values are used

In function descriptions, indicates parameters whose values are

Refers collectively to the CICS product for all supported UNIX

TXSeries for Multiplatforms: Messages and Codes

How to send your comments

About this book

TXSeries for Multiplatforms: Messages and Codes

Chapter 1. ERZxxx messages

Look in console.msg and find the COBOL run time

Abnormal termination U0101. CICS

ERZ001003E An error in a COBOL transaction

ERZ002003E Unsuccessful open of input file

Copyright IBM Corp. 2001, 2008

ERZ002011I DFHCNV macro translation ended.

TXSeries for Multiplatforms: Messages and Codes

ERZ002024W lineNumber: No DFHCNV macro

lineNumber: Unknown word

ERZ002030W Conversion template file is empty

lineNumber: Invalid single & in string

TXSeries for Multiplatforms: Messages and Codes

ERZ002045E CICS has detected a signature

ERZ002042W lineNumber: The CDEPAGE option in

ERZ002044E lineNumber: The length of a token

Chapter 1. ERZxxx messages

ERZ002051E lineNumber: Missing typeintro

ERZ002055E lineNumber: Invalid DFHCNV macro

TXSeries for Multiplatforms: Messages and Codes

ERZ002066E lineNumber: Invalid argument

ERZ002071E lineNumber: Unexpected DFHCNV

TXSeries for Multiplatforms: Messages and Codes

TXSeries for Multiplatforms: Messages and Codes

ERZ002083E lineNumber: The DFHCNV macro