IMS: Messages and Codes, Volume 1 - IBM

IMS15.1.0

Messages and Codes, Volume 1:DFS Messages(2021-12-09 edition)

IBM

GC27-6789-00

Note

Before you use this information and the product it supports, read the information in “Notices” on page1387.

2021-12-09 edition.

This edition applies to IMS 15 (program number 5635-A06), IMS Database Value Unit Edition, V15.01.00 (programnumber 5655-DS5), IMS Transaction Manager Value Unit Edition, V15.01.00 (program number 5655-TM4), and to allsubsequent releases and modifications until otherwise indicated in new editions.© Copyright International Business Machines Corporation 1974, 2020.US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contract withIBM Corp.

Contents

About this information.......................................................................................... ixPrerequisite knowledge...............................................................................................................................ixHow new and changed information is identified........................................................................................ ixAccessibility features for IMS 15................................................................................................................. xHow to send your comments....................................................................................................................... x

Chapter 1. New, changed, and deleted messages and codes for IMS 15................... 1New messages and codes for IMS 15......................................................................................................... 1Changed messages and codes for IMS 15.................................................................................................. 4Deleted messages and codes for IMS 15....................................................................................................6

Chapter 2. IMS problem determination.................................................................11

Chapter 3. DFS messages.....................................................................................15

Chapter 4. DFS messages, DFS000I - DFS050A.....................................................19

Chapter 5. DFS messages, DFS051I - DFS100.......................................................41

Chapter 6. DFS messages, DFS101 - DFS150........................................................ 61

Chapter 7. DFS messages, DFS151-DFS200..........................................................73

Chapter 8. DFS messages, DFS201 - DFS250........................................................ 83

Chapter 9. DFS messages, DFS251 - DFS0300I.....................................................95

Chapter 10. DFS messages, DFS301A - DFS350A................................................109

Chapter 11. DFS messages, DFS351W -DFS400I................................................ 125

Chapter 12. DFS messages, DFS401I - DFS0450I................................................139

Chapter 13. DFS messages, DFS0451A - DFS0500I.............................................159


Chapter 15. DFS messages, DFS551I - DFS600I................................................. 197

Chapter 16. DFS messages, DFS601I - DFS650E................................................. 213

Chapter 17. DFS messages, DFS0651W - DFS700I..............................................231


Chapter 19. DFS messages, DFS0751I - DFS0800I..............................................277

iii

Chapter 20. DFS messages, DFS0801I - DFS0850W............................................297

Chapter 21. DFS messages, DFS0851W - DFS0900A........................................... 315





















Chapter 42. DFS messages, DFS1901I - DFS1950............................................... 553

Chapter 43. DFS messages, DFS1951 - DFS2000I............................................... 569



iv


Chapter 47. DFS messages, DFS2151 - DFS2200I............................................... 633


Chapter 49. DFS messages, DFS2251W - DFS2300I............................................657






Chapter 55. DFS messages, DFS2551I - DFS2600A.............................................733


Chapter 57. DFS messages, DFS2651A - DFS2700A............................................ 757



Chapter 60. DFS messages, DFS2801A - DFS2850E............................................ 785







Chapter 67. DFS messages, DFS3151 - DFS3200................................................ 861

Chapter 68. DFS messages, DFS3201 - DFS3250................................................ 885


Chapter 70. DFS messages, DFS3301W - DFS3350E........................................... 925

Chapter 71. DFS messages, DFS3351E - DFS3400I............................................. 939

v


Chapter 73. DFS messages, DFS3451 - DFS3500W............................................. 973


Chapter 75. DFS messages, DFS3551E - DFS3600I........................................... 1001

Chapter 76. DFS messages, DFS3601 - DFS3650I............................................. 1017

Chapter 77. DFS messages, DFS3651I - DFS3700............................................. 1043

Chapter 78. DFS messages, DFS3701I - DFS3750A...........................................1057

Chapter 79. DFS messages, DFS3751A - DFS3800............................................ 1079

Chapter 80. DFS messages, DFS3801 - DFS3850A............................................ 1095

Chapter 81. DFS messages, DFS3851I - DFS3900I............................................1107

Chapter 82. DFS messages, DFS3901W - DFS3950A......................................... 1119


Chapter 84. DFS messages, DFS4001 - DFS4050A............................................ 1147

Chapter 85. DFS messages, DFS4101A - DFS4150I...........................................1151

Chapter 86. DFS messages, DFS4151I - DFS4200I............................................1155

Chapter 87. DFS messages, DFS4201I - DFS4250............................................. 1169

Chapter 88. DFS messages, DFS4251 - DFS4300.............................................. 1173

Chapter 89. DFS messages, DFS4301E - DFS4350E...........................................1185

Chapter 90. DFS messages, DFS4351E - DFS4400E...........................................1197


Chapter 92. DFS messages, DFS4451I - DFS4500E........................................... 1227



Chapter 95. DFS messages, DFS4651E - DFS4700............................................ 1283



vi



Chapter 100. DFS messages, DFS5001 - DFS5100.............................................1333

Chapter 101. DFS messages, DFS7001 - DFS7500.............................................1339

Chapter 102. DFSD messages (DRD utilities).....................................................1349

Chapter 103. DFSIX messages (Installation Verification Program dialog)...........1355

Chapter 104. DFSI messages (Syntax Checker).................................................1377

Chapter 105. DFSS messages (IMS abend search and notification).................... 1383

Notices............................................................................................................1387Programming interface information......................................................................................................1388Trademarks............................................................................................................................................1388Terms and conditions for product documentation............................................................................... 1389IBM Online Privacy Statement.............................................................................................................. 1389

Bibliography.................................................................................................... 1391

vii

About this information

This information provides reference information for the abend codes, messages, status codes, and returncodes that are produced by IMS.

This information provides reference information for the abend codes, messages, status codes, and returncodes that are produced by IMS.

Volume 1 provides reference information for the IMS messages that have the DFS prefix, along with theirassociated return codes. It also provides diagnostic information that helps programmers, operators, andsystem-support personnel diagnose problems in IMS.

Volume 2 provides reference information for non-DFS prefixed IMS messages that are associated withIMS Base Primitive Environment (BPE); IMS Common Queue Server (CQS); IMS Common Service Layer(CSL); Database Recovery Control (DBRC) facility; IMS Connect; IBM® Resource Lock Manager (IRLM),and so on. It provides diagnostic reference information that helps programmers, operators, and system-support personnel diagnose problems in IMS.

Volume 3 provides reference information for all IMS abnormal termination (abend) codes, includinganalysis, explanation, possible causes, and APAR processing instructions.

Volume 4 provides return, reason, sense, function, and status codes for IMS Base Primitive Environment(BPE); IMS Common Queue Server (CQS); IMS Common Service Layer (CSL); Database Recovery Control(DBRC) facility; IMS Connect; IBM Resource Lock Manager (IRLM), and so on. It also provides diagnosticreference information that helps programmers, operators, and system-support personnel diagnoseproblems in IMS.

This information is available as part of IBM Documentation.

Prerequisite knowledgeBefore using this information, you should have knowledge of either IMS Database Manager (DB) or IMSTransaction Manager (TM). You should also understand basic z/OS® and IMS concepts, the IMS system foryour installation, and have general knowledge of the tasks involved in project planning.

Before using this book, you should have knowledge of either IMS Database Manager (DB) or IMSTransaction Manager (TM). You should also understand basic z/OS and IMS concepts, the IMS systemfor your installation, and have general knowledge of the tasks involved in project planning.

You should be familiar with z/OS, its system generation, and telecommunications, and the accessmethods used by IMS. Related publications are listed in the Bibliography.

You can learn more about z/OS by visiting the "z/OS basic skills" topics in IBM Documentation.

You can gain an understanding of basic IMS concepts by reading An Introduction to IMS, an IBM Presspublication.

IBM offers a wide variety of classroom and self-study courses to help you learn IMS. For a complete list ofcourses available, go to the IBM Skills Gateway and search for IMS.

How new and changed information is identifiedNew and changed information in most IMS library PDF publications is denoted by a character (revisionmarker) in the left margin. The first edition (-00) of Release Planning, as well as the Program Directory andLicensed Program Specifications, do not include revision markers.

Revision markers follow these general conventions:

• Only technical changes are marked; style and grammatical changes are not marked.

© Copyright IBM Corp. 1974, 2020 ix

http://www-01.ibm.com/support/knowledgecenter/zosbasics/com.ibm.zos.zbasics/homepage.html

https://www-03.ibm.com/services/learning/content/ites.wss/zz-en?pageType=page&c=a0011023

• If part of an element, such as a paragraph, syntax diagram, list item, task step, or figure is changed,the entire element is marked with revision markers, even though only part of the element might havechanged.

• If a topic is changed by more than 50%, the entire topic is marked with revision markers (so it mightseem to be a new topic, even though it is not).

Revision markers do not necessarily indicate all the changes made to the information because deletedtext and graphics cannot be marked with revision markers.

Accessibility features for IMS 15Accessibility features help a user who has a physical disability, such as restricted mobility or limitedvision, to use information technology products successfully.

Accessibility featuresThe following list includes the major accessibility features in z/OS products, including IMS 15. Thesefeatures support:

• Keyboard-only operation.• Interfaces that are commonly used by screen readers and screen magnifiers.• Customization of display attributes such as color, contrast, and font size.

Keyboard navigationYou can access IMS 15 ISPF panel functions by using a keyboard or keyboard shortcut keys.

For information about navigating the IMS 15 ISPF panels using TSO/E or ISPF, refer to the z/OS TSO/EPrimer, the z/OS TSO/E User's Guide, and the z/OS ISPF User's Guide Volume 1. These guides describe howto navigate each interface, including the use of keyboard shortcuts or function keys (PF keys). Each guideincludes the default settings for the PF keys and explains how to modify their functions.

Related accessibility informationOnline documentation for IMS 15 is available in IBM Documentation.

IBM and accessibilitySee the IBM Human Ability and Accessibility Center at www.ibm.com/able for more information about thecommitment that IBM has to accessibility.

How to send your commentsYour feedback is important in helping us provide the most accurate and highest quality information. If youhave any comments about this or any other IMS information, you can take one of the following actions:

• Submit a comment by using the DISQUS commenting feature at the bottom of any IBM Documentationtopic.

• Send an email to [email protected]. Be sure to include the book title and the publication number.• Click the Contact Us tab at the bottom of any IBM Documentation topic.

To help us respond quickly and accurately, please include as much information as you can about thecontent you are commenting on, where we can find it, and what your suggestions for improvement mightbe.

x IMS: Messages and Codes, Volume 1: DFS Messages

http://www.ibm.com/able

https://www.ibm.com/docs/en/ims

https://www.ibm.com/docs/en/ims

Chapter 1. New, changed, and deleted messages andcodes for IMS 15

A number of messages and codes are new, changed, or deleted in IMS 15.

New messages and codes for IMS 15IMS 15 includes new messages, as shown in the lists that follow.

New CQS messagesThe following messages are new:

CQS0224ECQS0249E

New CSL messagesThe following messages are new:

CSL2202E

CSL2505WCSL4200WCSL4201WCSL4202WCSL4203W

New DFS messagesThe following messages are new:

DFS7432IDFS686IDFS0745EDFS3253WDFS3458DFS3478DFS4401EDFS4470EDFS4550WDFS4553WDFS4555WDFS4690IDFS4691IDFS4692EDFS4723ADFS4725IDFS4787IDFS4852EDFS4861WDFS4862WDFS4863W

© Copyright IBM Corp. 1974, 2020 1

DFS4864WDFS4865EDFS4866EDFS4867ADFS4878IDFS4879IDFS4881IDFS4888IDFS4896IDFS4897IDFS4898EDFS4899WDFS4892EDFS4930IDFS4965EDFS4896IDFS4897IDFS4898EDFS5055IDFS5386IDFS7411IDFS7412IDFS7413IDFS7419EDFS7420EDFS7421EDFS7422EDFS7423EDFS7424EDFS7429EDFS7430WDFS7431IDFS7433EDFS7434WDFS7435EDFS7436EDFS7438EDFS7439EDFS7440WDFS7441IDFS7442WDFS7443EDFS7444EDFS7445ADFS7447E

New G messagesThe following messages are new:

G116G117

2 IMS: Messages and Codes, Volume 1: DFS Messages

G118G119G120G121G122

New FLD messagesThe following messages are new:

FLD760FLD761FLD763FLD764FLD765FLD766FLD767FLD768FLD769

New HWS messagesThe following messages are new:

HWSX0908WHWSX0915WHWSX0916W

New abend codesThe following abend codes are new:

01330397042104230424042504265121155

New AIB return and reason codesThe following status codes are new:

0108-071D

New component codesThe following component codes are new:

Return and reason codes for IMS Connect exitsSQL -9012SQL -9013

Chapter 1. New, changed, and deleted messages and codes for IMS 15 3

Changed messages and codes for IMS 15This release includes changed DSP messages, as shown in the lists that follow.

Changed BPE messagesBPE 0042E

Changed CQS messagesThe following messages are changed:

CQS0035E

Changed DFS messagesThe following messages are changed:

DFS0413IDFS627WDFS0730IDFS0762IDFS0919IDFS982IDFS1269EDFS1769WDFS1919IDFS1934EDFS2205IDFS2385EDFS2411IDFS2679ADFS2854ADFS3177EDFS3254IDFS3377DFS3398EDFS3435ADFS3498WDFS3505EDFS3551EDFS3613IDFS3649ADFS3656DFS4198EDFS4382WDFS4383EDFS4384IDFS4385WDFS4386IDFS4515WDFS4516EDFS4517IDFS5100E


DFS7412IDFS7413I

DFS4427EDFS4585WDFS4593EDFS4610EDFS4615EDFS554ADFS3176EDFS3438DFS4332EDFS3446DFS4447EDFS4549EDFS4774EDFS4775EDFS4830IDFS4851EDFS7443E

Changed DSP messagesThe following messages are changed:

DSP0012IDSP0141I

Changed FLD messagesThe following messages are changed:

FLD602FLD603FLD604FLD605

Changed HWS messagesThe following messages are changed:

HWSC0010IHWSP1503EHWSX0909E

Changed abend codesThe following abend codes are changed:

U0021U0070U0071U0073U0078U0166U0113


U0711U0718U0757U1002U1060U1143

Changed AIB return and reason codesThe following status codes are changed:

0110/0050

Changed component codesThe following component codes are changed:

BPESTART codesOTMA C/I return codesOTMA 001AOTMA 0028Return and reason codes for IMS Connect exitsIMS TM Resource Adapter return and reason codesSQL -9000SQL -9005SQL -9055

Deleted messages and codes for IMS 15The messages that are listed in the following sections were removed from IMS 15.

The following messages were deleted in this release:

DFS2211IG040G043G904G042G1205G1212

LGEN messages deletedThe following messages were removed with the removal of support for large system definitions (LGEN).


DFS3512IDFS3514IDFS3516IDFS3518IDFS3520IDFS3522IDFS3524IDFS3526IDFS3528IDFS3530IDFS3532IDFS3534IDFS3536IDFS3538IDFS3540IDFS3546IDFS3548IDFS3550IDFS3552IDFS3554IDFS3556IDFS3558IDFS3559ADFS3560IDFS3562IDFS3564IDFS3566IDFS3567IDFS3568IDFS3569IDFS3570IDFS3572IDFS3574IDFS3577ADFS3593IDFS3599I

G008G1211

RSR messages deletedThe following messages and abends were removed with the removal of support for Remote Site Recovery(RSR). These messages include messages issued by the Transport Manager Subsystem and other RSRservices, such as online forward recovery, log router, DBRC service groups.


Abends

360361362363364365378379380381388309030913399

DFS messages (IMS)

DFS170DFS176DFS2903IDFS2908IDFS2909IDFS2910IDFS2911IDFS2912IDFS2913IDFS2914IDFS2915IDFS2916WDFS2917IDFS2918ADFS2922ADFS2923IDFS2924IDFS2925IDFS2926IDFS2927IDFS2928IDFS2929ADFS2931IDFS2932IDFS2933IDFS2935IDFS2936IDFS2937I

DFS2953IDFS2954IDFS2955WDFS2956IDFS2959IDFS2960ADFS2961IDFS2962IDFS2963ADFS2964IDFS2965ADFS2966ADFS2967ADFS2968ADFS2969ADFS2980EDFS2981EDFS2982EDFS2983EDFS2984IDFS2989IDFS4010WDFS4011IDFS4012IDFS4013WDFS4014IDFS4015IDFS4016ADFS4017ADFS4018IDFS4019IDFS4020IDFS4021IDFS4022IDFS4024IDFS4025IDFS4026IDFS4027IDFS4028IDFS4029I

DFS4030ADFS4031ADFS4032ADFS4033IDFS4034ADFS4034IDFS4035ADFS4036IDFS4037ADFS4039ADFS4041IDFS4042ADFS4043ADFS4044ADFS4045ADFS4046ADFS4047ADFS4048IDFS4049IDFS4050ADFS4051IDFS4052ADFS4053ADFS4054ADFS4055IDFS4056IDFS4057ADFS4058ADFS4060IDFS4061ADFS4062WDFS4063IDFS4064WDFS4065ADFS4066IDFS4067ADFS4068ADFS4069ADFS4070ADFS4071I


DFS4072ADFS4073ADFS4074WDFS4075ADFS4076ADFS4077IDFS4078IDFS4079ADFS4085WDFS4086WDFS4087ADFS4088ADFS4089ADFS4090ADFS4091IDFS4092ADFS4094ADFS4095ADFS4096ADFS4097IDFS4098ADFS4099ADFS4100IDFS4101ADFS4102ADFS4103IDFS4104ADFS4105ADFS4106IDFS4107ADFS4108ADFS4109DFS4111IDFS4112ADFS4113IDFS4114ADFS4115IDFS4121IDFS4122ADFS4123IDFS4124IDFS4125IDFS4126IDFS4127A

DSP messages (DBRC)

DFS4130IDFS4131ADFS4132ADFS4133ADFS4134IDFS4135IDFS4136IDFS4150IDFS4152ADFS4153WDSPM058IDSPM059IDSP1001IDSP1002IDSP1030IDSP1004IDSP1005IDSP1006IDSP1007IDSP1009IDSP1010IDSP1011IDSP1012IDSP1013IDSP1014IDSP1016IDSP1017IDSP1021IDSP1022IDSP1025IDSP1027IDSP1028IDSP1029IDSP1030IDSP1032IDSP1035IDSP1036IDSP1037IDSP1038IDSP1042IDSP1043IDSP1044I


ELX messages (TMS)

ELX0001AELX0002AELX0003AELX0004AELX0005AELX0100AELX0101WELX0102WELX0103IELX0104AELX0105IELX0106AELX0107IELX0108IELX0109IELX0111AELX0112IELX0113AELX0114IELX0115IELX0116AELX0118AELX0119IELX0120IELX0122IELX0128IELX0129IELX0130IELX0150IELX0170IELX0171AELX0181AELX0183AELX0184IELX0185IELX0187IELX0188IELX0189IELX0200I

ELX0201WELX0202IELX0203WELX0204IELX0205IELX0209IELX0210AELX0211IELX0212AELX0213AELX600AELX1001EELX1002IELX1003WELX1004WELX1005WELX1010IELXC106IELXC109IELXC112AELXC160IELXC161IELXC162AELXC181IELXC315I

G messages (SYSGEN)

G1205G1212


Chapter 2. IMS problem determinationIMS messages and codes problem determination is accomplished by using procedures established byIBM.

Problem determination is accomplished by using procedures for identifying a failing module or programand determining whether the user or IBM is responsible for resolution of a given problem.

Problem determination information is included, as appropriate, for all messages and codes. In mostinstances, one or more numbers (for example, "4,6") appear after the heading Problem Determinationfor a given message or code. These numbers are cross-references to the numbered items that appear inthe following list of standard problem determination actions to be taken by the user.

1. Save the console sheet from the z/OS console.2. Save the input associated with the job.3. Save the SYSOUT (system output) associated with the job.4. Save the storage memory dump at time of failure of the IMS control region, and save the memory

dump of all associated message regions. (If SYS1.DUMP is used, print, and save it.)5. Save the IMS log printout.6. Save the IMS master terminal printout.7. Save the local or remote terminal printout.8. Save the JCL listings.9. Save the ACB generation output.

10. Save the IMSGEN listing.11. Save the SYSABEND memory dump. (If SYS1.DUMP is used, print, and save it.)12. Save the assembly listing of any user-modified IMS modules.13. Save the bind map.14. Save the LOG trace.15. Save the IMS log printout starting with the records that were written just before abnormal

termination.16. Save the output listing from the MFS Language Utility execution.17. Collect the following problem-related data:

a. System memory dump if running batch.b. If running online, print log records type X'67', sub-record type X'FF' (Pseudoabend). Use the File

Select and Formatting Print program to print these records. The OPTION PRINT control statementmust specify EXITR=DFSERA30.

c. Run the DL/I test program (DFSDDLTO) with SNAP statements before and after the failing call.d. Save the PSB and DBD listings or statements, or both, related to the failure.e. Create a memory dump of log records type X'67', sub-record type X'FE' (program isolation trace).

Use the File Select and Formatting print program to print the records. Program isolation tracemust be enabled when the log is created. The OPTION PRINT control statement must specifyEXITR=DFSERA40.

f. If online, a snap from the log of the online region.g. A history of the database backout, recovery, and reorganization activity.

18. Save the assembly listing for the associated DBDs.19. Save the assembly listing for the associated PSBs.20. Save a listing of the VSAM catalog entries for the associated data sets at the time of failure.21. Reserved for future use


22. Reserved for future use23. Contact IBM for hardware support.24. Create a memory dump of the 3270 diagnostic error log records off the IMS log: Record type X'67':

sub-record type X'03'.25. Submit a copy of the IMS log.26. Determine the CCB involved from the SPACCB field of the scratch pad area or from the CTBCCBPT

field. Determine the associated (a) source and output CNT, and (b) the line and PTERM (CTB).

Determine from log records 01, 02, 03, 07, 08, 11, 12 and 13 the status of the conversation:

a. The message was ready, but the application was not scheduled. A 01 destination is aconversational SMB.

b. The application was scheduled and a 08 record was produced.c. The application inserted a segment to a conversational terminal. If the destination of the message

is CNT, 03 and 13 records are produced.d. The application inserted a segment to a conversational program. SPA is the first segment of a

message in the 03 records.e. The application finished normally or terminated abnormally. The 07 record contains the

completion code of a conversational application. The DLRFLAG2 area (the last word of the 07log record) contains synchronization point information.

f. A 12 record indicates that the conversation was terminated.g. Determine if 02 records, produced for the following commands, affected the terminal in

conversation: /EX1, /HOLD, /REL, or /START LINE (no PTERM).h. Does restarting IMS affect the conversation? For details, see the input to and output logs from

restart.27. Save the z/OS hardcopy message log output.28. Determine the status of z/OS and IRLM operating in the other system with which this system is

connected during normal operations.29. Save the IRLM address space dump generated at the time of the failure.30. Save the memory dump of any IMS online or batch address space that failed near the time of the

IRLM failure. Follow IMS problem determination procedures relative to the IMS memory dump. TheIMS failure might be related to the IRLM failure.

31. Save a listing of the IRLM start procedure JCL.32. Save a listing of the IMSGEN performed to install the IRLM.33. Save listings of the VTAM® definitions performed to install the IRLM.34. Save the GTF trace output, if any is available showing activity at the time of the failure.35. Refer to the following manuals for further assistance to resolve your problem:

• IMS Version 15 Messages and Codes, Volume 1: DFS Messages• IMS Version 15 Messages and Codes, Volume 2: Non-DFS Messages• IMS Version 15 Messages and Codes, Volume 3: IMS Abend Codes• IMS Version 15 Messages and Codes, Volume 4: IMS Component Codes• IMS Version 15 Diagnosis

Check all input for accuracy and analyze any memory dumps.

If you are still unable to solve your problem, contact IBM Software Support for further assistance.36. If you are unable to solve the problem, contact IBM Software Support for assistance.37. Submit a copy of the type X'02' log records.38. Save the CCTL SNAP or SDUMP data set.39. Save a listing of the DBRC RECON.


40. Take an SVC memory dump and contact IBM Software Support for further assistance.

Chapter 2. IMS problem determination 13

Chapter 3. DFS messagesThe DFS messages are issued by IMS to indicate when some event or series of events have occurred inthe running of the program.

DFS messages have the form DFSnnnnZ. The nnnn are 3 or 4-digit numbers; the letter Z represents asuffix code. The messages are sorted according to the numeric value of nnnn.

Keycall messages bound for the system console have the suffix I appended to the message.

Some messages have an IMS system ID appended to identify the IMS system receiving the message whenmultiple IMS systems are being run.

When TIMESTAMP is specified in the COMM or IMSGEN macro, the time is inserted between the messagenumber and the text for each of the following messages. The time is not inserted in a DBCTL environment.

• DFS001 through DFS056• DFS058 through DFS091• DFS093 through DFS193• DFS195 through DFS300• DFS574 through DFS577• DFS968• DFS999• DFS2000 through DFS2010• DFS2013 through DFS2018• DFS2020 through DFS2078• DFS2100 through DFS2144• DFS2151 through DFS2173• DFS2231 through DFS2274• DFS2290• DFS2418• DFS2460• DFS2468• DFS2476• DFS2530 through DFS2538• DFS2577• DFS2610• DFS2717• DFS3101 through DFS3117• DFS3200 through DFS3250• DFS3411 through DFS3413• DFS3420• DFS3431• DFS3438• DFS3440 through DFS3442• DFS3451 through DFS3454• DFS3457


• DFS3460• DFS3461• DFS3470 through DFS3472• DFS3656• DFS3800

The following information is supplied with each message when applicable:

Explanation: States what the message means; why it appears; what caused it; what its variable entryfields are.

System action: States what is happening as a result of the condition causing the message; whether thesystem is waiting for responses. If this information is not shown, it does not apply.

Operator, System programmer, Programmer, or User response: If a response is necessary, states whoperforms the action, what the pertinent responses are, and their effect on the system or program. If thisinformation is not shown, it does not apply.

Problem determination: If the problem recurs or persists so that system efficiency suffers, this sectionstates what actions must be performed to obtain adequate data for trained hardware or programmingsupport personnel to diagnose the problem. If this information is not shown, it does not apply.

Problem Determination refers to a list of problem determination actions that are specified in Chapter2, “IMS problem determination,” on page 11. These common action tables do not teach diagnostictechniques, but instruct the operator or programmer about what to do when problems recur. The problemdetermination actions aid you in identifying hardware or programming problems and provide essentialprogramming information that qualified support personnel can use to diagnose and correct the difficulty.

Those messages that refer to function "ff" apply to one of the following utilities as denoted by the2-character codes shown below:

Code Meaning

PO Prereorganization

CA Change Accumulation

IM Image copy

RV Database Recovery

SU HISAM Reorganization Unload

RU Secondary Index Unload

SR HISAM Reorganization Reload

RR Secondary Index Reload

DU HD Reorganization Unload

DR HD Reorganization Reload

ZB Database Zap

ZM Module Zap

SN Database Scan

PR Prefix Resolution

PU Prefix Update

Severity: The chart below applies to the MFS Language utility program severity codes. The severity codeindicates the seriousness of the message.

Messages produced by the preprocessor phase of the MFS Language utility place the severity code to theright of each message number. Messages produced by the other phases do not include the severity code


in the message text. Consult the individual message descriptions for specific severity codes associatedwith each message.Severity code

Meaning0

Message is an information message only.4

Severity code 4 is produced by warnings, minor errors, and assumed defaults that are probably valid.The creation of valid blocks is probable.

8This error is significant and it results in questionable defaults, or ignored specifications. The creationof invalid blocks is possible.

12Required operand is omitted or contradictory specifications have been supplied. Creation of invalidblocks is probable.

16Language translation continues with limited function. Created blocks are invalid, or creation of blocksis suppressed.

20Language translation cannot continue and is terminated immediately. Created blocks are invalid.

The highest severity code issued by the MFS Language Utility Program during a job step is returned as thecompletion code to the operating system.

Chapter 3. DFS messages 17

Chapter 4. DFS messages, DFS000I - DFS050A

This topic contains the following messages:

DFS000I various

ExplanationThis message number is used for the followingsituations:

• An IMS message number prefixed to user messagessent to the system console through the IMS queues.

• A message ID for /DISPLAY responses.• A message number for messages switched to the

system console.• Continuation lines on messages of more than one

segment.• Name of DBRC region to be included online.

System actionIMS continues processing.

ModuleDFSCINB0, DFSDNSC0, DFSFDR60

DFS001 UNDETERMINED ERROR ON 3270.LINE x PTERM y

ExplanationAn undetermined error was detected in moduleDFSDN130 (remote 3270), or in DFSDN140 (local3270).

System actionThe line has been stopped. A log record type X'67'sub-record X'01' has been written using the IMSTRACE facility, which provides a snap of the IMScontrol blocks and save areas.

Operator response:(master terminal) You can attempt to restart the linewith a /START LINE x PTERM ALL command. If thefailure occurs consistently, please print the log dataset to determine the cause of the error.

Problem determination1, 5, 6, 36

ModuleDFSDN130, DFSDN140

Related information“IMS problem determination” on page 11IMS messages and codes problemdetermination is accomplished by usingprocedures established by IBM.

DFS002I MONITOR WILL NOT BEAVAILABLE-NOT SL TAPE

ExplanationThe data communication monitor tape must be ascratch tape with a standard label or standard userlabel.

System actionIMS continues processing without monitor logging.

Operator response:If data communication monitor logging is required,IMS must be restarted.

Programmer responseIf data communication monitor logging is needed,make sure that the IMSMON DD statement specifiesa standard label or standard user label.

Module:DFSXLGI0

DFS003I xxx MODE COMPLETED.

or

DUP MODE COMPLETED. nnnnn ERRORS.

ExplanationEither form of this message can be issued, and bothindicate that the Log Recovery utility successfullycompleted the DUP, REP or CLS function. nnnnnspecifies the number of error records written on theinterim log data set during the DUP processing. xxxrepresents the CLS or REP mode.


System actionThe Log Recovery utility terminates normally.

Programmer responseFor CLS mode and REP mode, no response is required.

For DUP mode, if nnnnn=0, the output log is error freeand can be used as the online log data set (OLDS).If nnnnn=1 and you specified ERRC=00000, an erroroccurred on the input log and the output log wastruncated at the point of error. Check the input logat the error point to determine if the output log wastruncated at the correct point. Otherwise, use the LogRecovery utility in REP mode to produce an error freeOLDS.

ModuleDFSULG10

DFS0005A REPLY "Y" IF THIS IS A REMOTEDRRS SITE

ExplanationDuring shared virtual storage option (VSO) area openprocessing, the IMS-managed dual structure supportdetected the DEALLOCATE PENDING CONNECTIVITYLOST status for the structure. If you are employinga DASD mirroring solution for disaster recoverywith CFRM policies identical at both the disasterrecovery remote sites (DRRS) and the production site,answering Y identifies this system as an IMS at adisaster recovery site. It bypasses the error status. Besure to include both the production site and disasterrecovery site CF in the preference list for the SVSOstructures.

System actionIf you indicate that this system is a remote disasterrecovery site, IMS proceeds with the area openprocessing by creating and connecting to a newstructure.

If you indicate that this system is not a remote disasterrecovery site, the area open processing is terminatedwith message DFS3702I with reason code 41.

System programmer response:Reply Y or y if this IMS is at the remote disasterrecovery site. Any other reply indicates this IMS is notat disaster recovery site.

Module:DBFVXAS0

DFS0006E REQUESTED VERSION req_v_nmbrAND CURRENT VERSION

cur_v_nmbr OF DEDB dedbnameARE INCOMPATIBLE

ExplanationAn application program attempted to access a versionof a Fast Path data entry database (DEDB) otherthan the current version, but IMS cannot build theinternal blocks that are required to access non-currentversions of the database, because the current versionof the database contains a change in the databasedefinition (DBD) that is not supported by databaseversioning.

Application programs cannot access any prior versionof the database, unless the application programs arechanged or the unsupported change is removed fromthe database.

In the message text:cur_v_nmbr

The version number of the current version ofthe DEDB database that is identified in themessage text. The current version is the versionof the database that contains the actual physicalstructure of the database as it is stored on DASD.The current version of the database contains astructural change that is incompatible with theprior version of the database.

req_v_nmbrThe version number of the requested versionof the DEDB database that is identified in themessage text. An application program attemptedto access the requested version; however, IMScannot return data in the format defined by therequested version of the database, because thecurrent version contains an incompatible structuralchange.

Possible cause: The incompatible changes areindicated in one or more DFS0123E messages thatIMS issues to the console before this message.

System action:Access to the database fails and the applicationprogram receives a status code.

System programmer responseNote the return codes in all DFS0123E messages. Lookup the meanings of the return codes in the DFS0123Edocumentation.

Module:DBFVER10

Related conceptsDatabase modifications supported by databaseversioning (Database Administration)


http://www.ibm.com/support/knowledgecenter/SSEPH2_15.1.0/com.ibm.ims15.doc.dag/ims_db_versioning_changes_supported.htm#ims_db_versioning_changes_supported


Related information“DFS0123E” on page 65DBD CHANGE UNSUPPORTED BY VERSIONING:DB=dedbname RSN=rc SEG segmname variabletext

DFS0007I /STA MADSIO COMMANDIGNORED. MADSIOT ALREADYACTIVE.

ExplanationThe MADSIOT function was already active whenthe /START MADSIO command was issued. Issuethe /START MADSIO command to resume MADSIOTfunction if it is stopped.

System actionThe /START MADSIO command was not processed.

Operator responseNo action is required.

ModuleDBFCST00

DFS0008I /STO MADSIO COMMANDIGNORED. MADSIOT IS NOTACTIVE.

ExplanationThe MADSIOT function was not active when the /STOPMADSIO command was issued.

System actionThe /STOP MADSIO command was not processed.


ModuleDBFCST00

DFS009 timestamp COMMAND NOTAUTHORIZED AS ENTERED FROMOM API

ExplanationThe command that was entered is not authorizedfrom the entering OM API. The command authorizationwas specified on the CMDSEC= parameter of the CSL

PROCLIB member DFSCGxxx (RACF® or equivalent,DFSCCMD0, or both), but it does not authorize the userID of the OM API to issue the command.

System actionThe command is rejected.

Programmer responseReenter the command from an OM API with anauthorized USERID, or update the authorizationinformation for the current USERID and reenter thecommand from the OM API.

ModuleDFS0CM30

DFS0011W AREA=areaname DD=ddnameALLOCATION FAILED

ExplanationThe named DD could not be allocated by the /STARTAREA command. The named DD is not specified bya DD statement nor is it specified in the ALLOCATE/DEALLOCATE parameter list.

System actionProcessing continues without the named DDallocation.

Programmer responseCorrect the DD in the ALLOCATE/DEALLOCATEparameter list, and reenter the /STARTAREA command or issue the UPDATE AREASTART(ACCESS) command.

ModuleDBFARDA0

DFS0012I SPOOL DATASET UNALLOCATIONERROR - aaaaaaaa,bbbb,cccccccc,dddd,eeee,ff,gggg,hhhh,ii..ii

ExplanationAn error occurred during deallocation of an IAFP JESSPOOL data set.

In the message text:aaaaaaaa

Job name of the IMS-dependent region for whichthe deallocation failed.

Chapter 4. DFS messages, DFS000I - DFS050A 21

bbbbJob number corresponding to job aaaaaaaa

ccccccccThe ddname of SPOOL data set.

ddddDependent region number.

eeeeReturn code from SPOOL data set deallocationprocessing.

ffDeallocation request type. Possible values are asfollows:80

No special request40

Remove from hold status20

Send to remote destination08

Delete data setgggg

Dynamic deallocate error code.hhhh

Dynamic deallocate error information.ii..ii

data set name for 44 bytes.

This message is returned only if the applicationprogram requested "Messages" for the data set in theIAFP= options parameter.

During IMS sync point or Terminate Thread processing,the referenced print data set was not deallocated.The print data set remains allocated to the dependentregion until the dependent region terminates. Thedependent region must be terminated as soon aspractical so MVS can deallocate the data set. The MVSoperator might need to control the proper dispositionof the print data set. See message DFS0013E fordetailed information about the deallocation error.Additional information about the error is also availableon the IMS system log, log record type 67D0.

System actionProcessing continues uninterrupted.

Programmer responseReview the ff section of this message. If ff=8, thedeallocation failure occurred while attempting todelete the data set. Delete the data set as soon as thedependent region terminates. If ff contains any othervalue, print the data set after the dependent regionterminates.

Problem determinationSee the z/OS MVS Programming: Authorized AssemblerServices Guide (SA22-7608) for error and informationcodes.

Module:DFSIAFP0

Related referencez/OS: Deallocating resourcesz/OS: Interpreting error reason codes fromDYNALLOCRelated information“DFS0013E” on page 22IAFP SPOOL PROC. ERR. LTERM=cccccccc,REGION=xxxx, OPERATION=xxx, R.C.=xxxx,REASON CODE=xxxx

DFS0013E IAFP SPOOL PROC. ERR.LTERM=cccccccc, REGION=xxxx,OPERATION=xxx, R.C.=xxxx,REASON CODE=xxxx

ExplanationAn IMS or z/OS system error occurred in theprocessing of an IAFP JES SPOOL data set. Theoperation, return code, reason code, and the LTERMname specified by the application as the "Dest Name"is displayed. REGION is the IMS-dependent regionnumber in which the error occurred. The operationsare as follows:DYN

The JES SPOOL data set was not dynamicallyallocated.

MEMMemory was obtained for IAFP processing. Thisis a critical system error. Consult the systemprogrammer for return code meaning.

OPNThe JES SPOOL data set was not opened.

OUTThe OUTPUT descriptor for the JES SPOOL data setdynamically allocated was not created (SVC 109failure).

UNAThe JES SPOOL data set was not dynamicallydeallocated.

WRTThe JES SPOOL data set was not written to.

For a BSAM WRT operation, if the value of LLZZ isnot 4 bytes larger than the value of llzz, a writeerror occurs and this message is issued by the IMSSpool API interface. The status code for the ISRTcall is AX.


http://www-01.ibm.com/support/knowledgecenter/SSLTBW_2.4.0/com.ibm.zos.v2r4.ieaa800/deallo.htm?lang=en

http://www-01.ibm.com/support/knowledgecenter/SSLTBW_2.4.0/com.ibm.zos.v2r4.ieaa800/erc.htm?lang=en



Programmer responseIMS has detected an error in either an IMS orz/OS systems service. See the message text for anindication of the IMS or z/OS service being used.Additional information about the error is also availableon the IMS system log, log record type 67D0.

Problem determinationSee the z/OS MVS Programming: Authorized AssemblerServices Guide (SA22-7608) for return and reasoncodes.

Module:DFSIAFP0

Related referencez/OS: Deallocating resourcesz/OS: Interpreting error reason codes fromDYNALLOC

DFS0014I JES SPOOL D.S. REQUIREScccccccc,JOBNAME=cccccccc,JOB#=aaaa,DDNAME=cccccccc,DATASET=aa..aa

ExplanationAn application program requested messages for thedata set in the IAFP= options parameter. During IMSrestart, the status of an IAFP JES SPOOL data set wasin doubt when the previous IMS terminated. To ensuremessage integrity, the z/OS operator must process thisdata set as indicated. It is possible that the indicateddata set cannot be found.

This message might not represent a problem and isapplicable only if the IMS application requested printdisposition messages for the data set.


Operator responsePerform one of the following actions:DELETION

Delete the indicated JES SPOOL data set.PRINTING

Deallocate the indicated JES SPOOL data set forprocessing by the JES SPOOL driver (for example,PSF).

Module:

DFSIAFP0

DFS0015I mmmm nn FAILED TO GETCONTROL BLOCK cccc

ExplanationDBFCDRC0 was unable to obtain WORK storage. In themessage text:mmmm

Short name of module.nn

Position in the module where the message isissued.

ccccThe control block name.

The short name is DRC0. The module name isDBFCDRC0. The function is to process /DISPLAYRTCODE command

System action/DISPLAY RTCODE command aborted.

User responseNo action is required.

ModuleDBFCDRC0

DFS0017I An invalid service call has beenissued to FP command ITASK.

ExplanationAn invalid call was issued.


Operator response:Contact IBM Software Support.

ModuleDBFCST00

DFS0019I DBRC UNAUTH REQUESTFAILED FOR DBD=dbdname,AREA=areaname RC=xx

ExplanationDBFARD30, DBFARD40, DBFMLCL0, DBFHDEP0, orDBFSTAP0 issued UNAUTH request to DBRC, but


http://www-01.ibm.com/support/knowledgecenter/SSLTBW_2.4.0/com.ibm.zos.v2r4.ieaa800/deallo.htm?lang=en



DBRC returned a nonzero return code less or equal to16.

System actionThe unsuccessful return code is passed to the caller.

User responseFor the meaning of the return code, see the "Returncodes from Unauthorization call" topic. Contact theIBM Software Support if additional help is needed.

Module:DBFARD30, DBFARD40, DBFMLCL0, DBFHDEP0,DBFSTAP0

Related referenceDBRC request return codes (Messages andCodes)Return codes from Unauthorization call(Messages and Codes)

DFS0020I DMAC HAS BAD POINTERTO DMCB, /DIS STATUS DBCOMMAND REJECTED

or

NO DDIR WAS FOUND, /DIS STATUS DB COMMANDREJECTED

or

NO DMCB WAS FOUND NO FP DB ISAVAILABLE, /DIS STATUS DB COMMAND REJECTED

or

DMCB HAS BAD POINTER TO DDIR, /DIS STATUS DBCOMMAND REJECTED

ExplanationInconsistency in control block was found during /DISSTATUS DB command processing.

System actionNon-zero return code is set for the caller. /DISSTATUS DB command is terminated.

User responseGather information about the database and contactIBM Software Support.

Module:DBFCDAR0

DFS022I DYNAMIC BACKOUT WAS|NOTSUCCESSFUL FOR jobname

ExplanationThis batch job's log resides on DASD, and theexecution parameter BKO=Y (dynamic backout) wasspecified. The job pseudoabended, and IMS invokeddynamic backout. This message will indicate whetheror not the backout was successful.

System actionThe batch job is terminated abnormally.

Programmer responseIf the dynamic backout was unsuccessful, the BatchBackout utility can be used to attempt the backout.

Problem determination1, 2, 8, 11, 36

ModuleDFSDLA00


DFS0023I COMMAND REJECTED. MADSIOTKEYWORD NOT FOUND INDFSVSMxx.

ExplanationThe /START MADSIO or /STOP MADSIO commandwas issued, but the MADS I/O Timing function was notenabled in this IMS.

System actionProcessing continues.

Operator responseTo enable the MADS I/O Timing function, specifythe keyword MADSIOT in the DFSVSMxx PROCLIBmember by using the format:

MADSIOT=(StructureName,IOTime)


http://www.ibm.com/support/knowledgecenter/SSEPH2_15.1.0/com.ibm.ims15.doc.msgs/compcodes/ims_dbrcrequestretcodes.htm#d2hsrcims_dbrcrequestretcodes


http://www.ibm.com/support/knowledgecenter/SSEPH2_15.1.0/com.ibm.ims15.doc.msgs/compcodes/ims_unauthoretcodes.htm#ims_unauthoretcodes


Where:

• StructureName is 16 characters.• IOTime is a 3-digit value (0-255) that specifies the

time span in which the Media Manager returns thestatus of the IO request.

The MADSIOT function will be enabled after IMSrecycles.

Module:DBFCST00

DFS024 INVALID PASSWORD FORMAT

ExplanationThe password format of the last input was invalid forone of the following reasons:

• The opening parenthesis or the bypass character isthe last character of the input data.

• The password is longer than eight characters.• There is no closing parenthesis or bypass character.

System actionIMS ignores the entered data.

Operator response:Reenter the data with the correct password format.

Module:DFSICIO0

DFS025 UNABLE TO FIND INPUTTINGTERMINAL. LINE STOPPED. LINE xPTERM y

ExplanationInput was received on the indicated line, and theoriginating terminal could not be determined.

System actionThe line has been stopped. A log record type X'67',sub-record X'01' was written using the IMS TRACEfacility, which provides a snap of the IMS controlblocks and save areas.

Operator response:(master terminal) Contact your IMS systemprogrammer for assistance. Determine the cause ofthe failure (possible hardware malfunction, or terminalnot defined to IMS). The line can be restarted withthe /START LINE command.

Programmer responseDetermine the cause of the failure.


ModuleDFSDN030


DFS026 UNABLE TO FIND INPUTTINGTERMINAL. LINE DEACTIVATED.LINE x PTERM y

ExplanationInput was received on the indicated line, and theoriginating terminal or control unit could not bedetermined.

System actionThe line was deactivated. A log record type X'67',subrecord X'01' was written using the IMS TRACEfacility, which provides a snap of the IMS controlblocks and save areas.

Operator response:(master terminal) Notify your IMS systemprogrammer. The line cannot be reactivated until theIMS system has been shut down and restarted.

Programmer responseDetermine the cause of failure.

Problem determination14, 36

ModuleDFSFTRM0


DFS027 I/O ROUTINE ERROR


ExplanationThe device module has failed to interface correctlywith the communications analyzer. This was caused bya device-dependent module logic error.

System actionThe line has been shut down. A log record type X'67',subrecord X'01' was written using the IMS TRACEfacility, which provides a snap of the IMS controlblocks and save areas.

Operator response:(master terminal) Notify your IMS systemprogrammer. The line cannot be reactivated untilthe IMS control region has been shut down andreactivated.

Programmer responseDetermine the cause of failure.


ModuleDFSICIO0


DFS028 INVALID ATTENTION INPUTDETECTED

ExplanationInput that required action was received, but theDFSCFEP0 (MFS Paging Processor) did not recognizeit.

System actionInput is ignored, and the terminal is made inoperable.

Programmer responseIf the terminal is programmable, check the logic—howis attention sent to the host? If the terminal is notprogrammable, there is a probable hardware error. Ifthe problem recurs, take a DC trace or a GTF trace.

ModuleDFSCFEP0

DFS029 DDM LOGIC ERROR DETECTED

ExplanationAn invalid request was returned to the MFS outputcontrol module (DFSCFEO0) from a device-dependentmodule. The device-dependent module requested thedata after the EOM or EOD occurred.

System actionThe terminal is made inoperable.

Programmer responseCheck for any discrepancy between the actualterminal and its definition in IMS. If the terminalis programmable, also check for logic errors in theoutput.

ModuleDFSCFEO0

DFS030I DBRC VERUOR REQUEST FAILED,RC=yy

or

DBRC REQUEST FAILED, REASON=xx, RC=yy

or

DBRC SIGNOFF REQUEST FAILED xx, RC=yy

or

DBRC SAVUOR REQUEST FAILED, RC=yy

or

DBRC UPDUOR REQUEST FAILED, RC=yy

ExplanationThe first form of the message is issued by modulesDFSDBAU0, DFSDDUI0, DFSDLOC0, and DBFPICT0.The second form of the message is issued bymodule DFSPCCC0. The SAVUOR, UPDUOR andVERUOR versions of the message are issued by eitherDFSRBOI0, DFSDBDR0 or DFSST500.


The particular DBRC request with or without thereason code xx failed with a return code of yy.

To determine the cause of the failure indicated by thereturn code yy, see the DBRC request return codesinformation in IMS Version 15 Messages and Codes,Volume 4: IMS Component Codes.

The following reason codes indicate the xx value.Code (hex)

Meaning01

A synchronization process or emergency restartbackout process attempted to notify DBRC of adatabase backout failure. DBRC indicated that thedatabase was not registered. If the database is notregistered, neither process notifies DBRC, and thecondition does not occur.

02A synchronization process or an emergency restartbackout process attempted to notify DBRC of adatabase backout failure. DBRC indicated thatthe subsystem was not authorized to use thedatabase. Because no changes to the databasecould have been made unless it was authorized,this condition should not have occurred.

03A database authorization call was made to DBRC.A return code X'0C', which indicated that thesubsystem was not signed on to DBRC, wasreceived upon return. This condition should nothave occurred unless there was an error in the IMSsubsystem initialization or in the DBRC.

05A sign-off call was made to DBRC while IMSwas terminating. The return code indicated thateither there was no subsystem entry found, thatan internal error was encountered during theunauthorization process, that the subsystem entrywas found but terminated abnormally, or that therecovery processing had been started.

06DBRC was called to unauthorize a databaseduring DL/I close processing. The return codeset by DBRC indicated that the database wasnot registered in the RECON data set. Becausethe unauthorization call is only issued if thedatabase is registered to DBRC, an internal errorhas occurred.

07DBRC was called to unauthorize a database duringDL/I close processing. The return code set byDBRC indicated that the subsystem was notregistered in the RECON data set. Because thesubsystem was registered when authorization for

the database was obtained, an internal error hasoccurred.

08DBRC was called to unauthorize the databaseduring DL/I close processing. The return codefrom DBRC indicated that the subsystem didnot have authorization for the database. Becauseauthorization for the database was obtained beforethe database was opened, this condition shouldnot occur.

Abend 3275 is issued if DBRC returns this codeand the system is not being emergency restarted.During emergency restart, this condition mightexist if the /DBRECOVERY command is run for theHALDB master before the /ERESTART command isrun.

09DBRC was called to unauthorize a databaseduring DL/I close processing. The return code setby DBRC indicated that an internal DBRC erroroccurred during or subsequent to the authorizationprocess, or that the unauthorization process wasunable to produce a new authorization state for thedatabase. See the message issued by DBRC beforethe abend for further explanation.

0AThe database open call to DBRC was issued duringDL/I open processing. The return code from DBRCindicated that the database being processed wasnot registered to DBRC. This situation might notoccur, because DBRC is not called during openprocessing unless authorization for the databasewas previously obtained from DBRC.

0BThe return code set by DBRC when the databaseopen call was processed indicated that thesubsystem was not registered to DBRC. Thissituation should not occur, because DBRC is calledduring DL/I open processing only if the subsystempreviously obtained authorization for the database,at which time it must be registered to DBRC.

0CThe database open call to DBRC was issuedduring DL/I open processing. The return codefrom DBRC indicated that the subsystem did nothave authorization for the database. This situationshould not occur because the open call to DBRCis issued only if authorization was obtained for thedatabase before DL/I open processing was started.

0DThe database open call to DBRC was issuedduring DL/I open processing. The return code fromDBRC indicated that an internal DBRC error wasdetected.


0EThe DBRC call to reverify the data sets failed.

0FDBRC received an end HSSP Image Copy callduring image copy termination. The DBRC returncode indicates that the image copy recordspecified was not found. The begin HSSP ImageCopy call should create that image copy record.

10DBRC received an end HSSP Image Copy callduring image copy termination. The DBRC returncode indicates that the database/area was notregistered in the RECON data set. HSSP ImageCopy can only process a registered database/area.

20DBRC received an end HSSP Image Copy callduring image copy termination. The DBRC returncode indicates that the end HSSP Image Copy callwas already made for this image copy processing.Abend 3275 is issued if DBRC returns this codeand the system is not being emergency restarted.

30DBRC received an end HSSP Image Copy callduring Image Copy termination. The DBRC returncode indicates that an internal DBRC erroroccurred.

40DBRC received an end HSSP Image Copy callduring image copy termination. The DBRC returncode indicates that an invalid parameter wasfound.

53DBRC was called to create a REORG record for thedatabase. The return code from DBRC indicatesthere was a problem processing the request. Foradditional information about return codes fromthe RELOAD Utility, and to determine the causeof the failure, see the DBRC request return codesinformation in IMS Version 15 Messages andCodes, Volume 4: IMS Component Codes.

54DBRC was called to create a REORG record for thedatabase. The return code, X'04', indicated thatthe database was not registered.

55DBRC was called to create a REORG record for thedatabase. The return code, X'08', indicated therewas an I/O error reading the RECON data set or aDD statement was not included for a data set beingreorganized.

56An invalid partition reorganization number waspassed on the notify reorganization call to DBRC.

System actionIMS terminates abnormally with abend 3275.

Programmer responseCheck the return code and take appropriate action.

Problem determination:1, 4, 10, 35

Module:DFSDDUI0, DFSDLOC0, DFSPCCC0, DBFPICT0

Related referenceDBRC request return codes (Messages andCodes)Related information“IMS problem determination” on page 11IMS messages and codes problemdetermination is accomplished by usingprocedures established by IBM.

DFS031I IRLM QUIT REQUEST FAILED,RC=xx-yy

ExplanationDuring normal termination of IMS, the quit request tothe IRLM failed. The return code xx and reason code yyindicate the error condition. To determine the cause ofthe failure, see IRLM request return and reason codeinformation for the QUIT request codes.

System actionIMS terminates abnormally.

Operator responseInform the system programmer.

Programmer responseCheck the cause of the problem and, if necessary,restart IMS with /ERE.


Module:DFSPCCC0

Related referenceIRLM request return and reason codes(Messages and Codes)Related information“IMS problem determination” on page 11




http://www.ibm.com/support/knowledgecenter/SSEPH2_15.1.0/com.ibm.ims15.doc.msgs/compcodes/ims_irlmreqestcodes.htm#ims_irlmreqestcodes


IMS messages and codes problemdetermination is accomplished by usingprocedures established by IBM.

DFS032I DUPLICATE ENTRY ON IDENTIFYREQUEST, RESTART ABORTED

ExplanationAn identify request was issued to the IRLM and thereturn code received indicated that an entry existed bythat name.

System actionRestart is terminated.

Operator responseIf no backout is required, enter /ERE COLDSYS torestart IMS.

Module:DFSRST00

DFS033I DUPLICATE ENTRY ON SIGNONREQUEST, RESTART ABORTED

ExplanationA sign-on request was issued to DBRC and the returncode received indicated that an entry already existedin the RECON data set for the IMS system.

System actionRestart is aborted.

Operator responseIf an XRF alternate system is being started, enterthe /ERE BACKUP command; otherwise, enter /EREOVERRIDE.

ModuleDFSRST00

DFS034I DATA BASE AUTHORIZATION ANDLOCKS RELEASED

ExplanationAn emergency COLDSYS start, using /ERE COLDSYScommand, was specified, and the database and globallocks authorized from the previous run of IMS werereleased.

System actionIMS continues with the execution.

Programmer responseEnsure that offline recovery or batch, or both, backoutis performed.

Module:DFSRST00

DFS035I TYPE INITIALIZATION COMPLETE

ExplanationThis message indicates that the initialization processis complete. After the issuance of this message, theprocess links to the application program.

When BATCH is displayed in the TYPE field, theinitialization process is complete for a DL/I batchenvironment. When TMBATCH is displayed in the TYPEfield, the initialization process is complete for a TMbatch environment.

System actionExecution continues.

Module:DFSPCC30

DFS036A BATCH BACKOUT /NOTREQUIRED/IS REQUIRED/ FORjobname

ExplanationThis message indicates whether a batch backout isrequired after a batch job was terminated abnormallyand updates were committed. If batch backout is notrequired, the application program made all updatesbefore the last checkpoint or the dynamic backout inbatch (BKO=Y) ran successfully. If batch backout isrequired, the application program made updates afterthe last checkpoint.

System actionThe batch job terminated.

Programmer responseIf a batch backout is not required, you must eitherrestart the program from the last checkpoint or froman earlier checkpoint. The option of restarting a jobfrom an earlier checkpoint is not available in a data-sharing environment.


• To restart the program from the last checkpoint, usethe XRST call.

• To restart the program from an earlier checkpoint, doone of the following:

– Run the Batch Backout utility to the firstcheckpoint that occurred before the programmade any updates. Then rerun the program.

– Run the Batch Backout utility to a checkpoint thatoccurred after the program made some updates.Then use the XRST call to restart the program atthe checkpoint used in the batch backout job.

If a batch backout is required, you must either restartthe program from the last checkpoint or from anearlier checkpoint. The option of restarting a job froman earlier checkpoint is not available in a data-sharingenvironment.

• To restart the program from the last checkpoint, runthe Batch Backout utility. Then use the XRST call torestart the program.

• To restart the program from an earlier checkpointthan the last one, do one of the following:

– Run the Batch Backout utility to the firstcheckpoint that occurred before the programmade any updates. Then rerun the program.

– Run the Batch Backout utility to a checkpoint thatoccurred after the program made some updates.Then use the XRST call to restart the program atthe checkpoint used in the batch backout job.

Module:DFSPCCC0, DFSFLST0

DFS036I BATCH BACKOUT /NOTREQUIRED/IS REQUIRED/ FORjobname

ExplanationThis message indicates whether batch backout isrequired for a batch job that is terminating abnormally.If batch backout is not required, the applicationprogram terminated abnormally for one of thefollowing reasons:

• No database updates were made• The job has no log• The dynamic backout in batch ran successfully.

If batch backout is required, the application programmakes database updates, but no CHKPT checkpointcall is made. Message DFS681I is not issued.

Batch backout can also be required for a job wherethere have been no updates but where GET TYPE callsresulted in extended pointer set corrections.

System actionThe batch job terminated.

Programmer responseIf a batch backout is required, run the Batch Backoututility. Rerunning the backout from the beginning orusing XRST is your or your application's option; thereare no IMS integrity issues after backout is donesuccessfully.

Module:DFSPCCC0, DFSFLST0

Related information“DFS681I” on page 238CHKPT xxx PSB psbname JOB jobname IDuserckptid yyy zzzzzz [X'nnnnnnnnnnnnnnnn']

DFS037I IRLM SPECIFIED, DBRC NOTACTIVE

ExplanationFor this execution of IMS, IRLM=Y was specified butDBRC was not specified in the IMSGEN. It might havebeen overridden in the JCL EXEC statement.

System actionIMS terminates abnormally with IRLM abend 0037.

Programmer responseEnsure that DBRC was specified in the IMSGEN or thatDBRC=N was not specified in the EXEC job controlstatement parameter list.

Problem determination:8, 10

Module:DFSXLIC0, DFSRST00


DFS038I PURGE REQUEST FAILURE,UNABLE TO RELEASE LOCKS

ExplanationA purge command to release all locks held by thissubsystem from the previous execution failed. Uponcompletion of an emergency restart or batch backoutexecution, a purge command is issued to the IRLMto release all locks. The attempt to release the locks


resulted in a bad return code. Register 15 contains thereturn code. To determine the cause of the failure, seethe PURGE request codes in IRLM request return andreason code information.


Programmer responseEnsure that the IRLM is active.


Module:DFSPCCC0, DFSRST00

Related referenceIRLM request return and reason codes(Messages and Codes)Related information“IMS problem determination” on page 11IMS messages and codes problemdetermination is accomplished by usingprocedures established by IBM.

DFS039I IMS WAITING FOR IRLM ARMREADY.

or

IRLM IDENTIFY REQUEST FAILED, RC=xx-yy

Explanation:This message accompanies DFS039A. See theinformation for that message for a detailedexplanation and actions. For the return code xx-yy, seeIRLM return and reason codes.

Related informationDFS039Aimsid ACTIVE, REPLY RETRY, CANCEL, ORDUMP.

DFS039A imsid ACTIVE, REPLY RETRY,CANCEL, OR DUMP.

or

xxxx NOT ACTIVE. REPLY RETRY, CANCEL, ORDUMP.

ExplanationMessage DFS039I is followed by this message.

Message DFS039I is first issued when an IDENTIFYrequest to the IRLM fails. Return code xx andreason code yy indicate an error condition. Returncode 00 or 04 are returned if IRLM is holdingsubsystem information for a DL/I batch job. Use the FIRLMPROC,STATUS command to display information.Run batch backout for the DL/I batch job thatencountered RC=00 or RC=04.

To determine the cause of the failure for messageDFS039I, see the IDENTIFY request explanation inthe IRLM request return and reason code information.This message is followed by a second DFS039I or aDFS039A message.

The second version of DFS039I might be issued ifIMS and IRLM are enabled for the z/OS automaticrestart manager. The message indicates IMS restartis WAITING for IRLM to send READY to the automaticrestart manager.

The DFS039A message is a WTOR. The first form of themessage is issued if the xx-yy fields indicate the fileIRLM named in the xxxx field is not active. The secondform of the message is issued if the IMS ID that isidentified to IRLM is already active.

System actionIf IMS is not registered with the automatic restartmanager and the xx-yy fields indicate that IRLM is notactive or that this IMS subsystem is already identifiedto IRLM, the WTOR form of the message is issued.Other error return and reason codes causes IMS toabend with 0039.

If IMS is in the process of being restarted bythe automatic restart manager and the xx-yy fieldsindicate that IRLM is not active or that thisIMS subsystem is already identified to IRLM, IMSdetermines if IRLM was registered to the automaticrestart manager in the previous IMS run. In thecase when IRLM was previously registered with theautomatic restart manager, IMS issues the secondform of the DFS039I and WAIT until the automaticrestart manager is aware that IRLM is ready for work.Other error return and reason codes cause IMS to endabnormally with abend 0039.

Operator responseOperator action is required for the WTOR form of themessage.

If the IRLM named in the xxxx field is not active,ensure the xxxx name is correct. If xxxx is not thecorrect name, the operator can reply ABEND to the




http://www-01.ibm.com/support/knowledgecenter/SSEPH2_14.1.0/com.ibm.irlm.doc.mc/src/tpc/irlm_codes.htm

WTOR and then start IMS again specifying the correctIRLMNM. If xxxx is correct, the operator can wait untilthe IRLM is active and then reply RETRY to the WTOR.

If the IMS subsystem is already identified to theIRLM, the operator should investigate the status ofthe subsystem currently identified to IRLM. There areat least two situations where a delay in identifying toIRLM might be needed. First, the submission of twoor more IMS Batch jobs with accidentally the samejob name could happen. Waiting for the first batchjob to finish and then replying RETRY would allowthe second job to then proceed. If the same job isaccidentally submitted twice, the job will probably onlyrun once and the installation might want the operatorto terminate the second job by replying CANCEL.

Second, some failures for which a CICS® XRF alternatetakes over can result in the identify return codeindicating the subsystem is already active. IRLMcorrective action to force IRLM into an in-doubt stateand then a failure state can be called before replyingRETRY in this case.

The WTOR replies and their meaning follow.RETRY

This causes IMS to retry the IRLM IDENTIFY. If thesituation has not been corrected, the DFS039I andDFS039A messages occur again.

CANCELThis causes IMS subsystem initialization toterminate with abend 0039 without a memorydump. If the IRLM was not active when theOS operator modified IMS with the RECONNECTcommand, responding CANCEL only terminates theIRLM reconnect processing; as a result, the OSoperator receives message DFS625I with a 08code.

DUMPThis problem causes the IMS subsystem to abend0039 with a memory dump.


Module:DFSRST00, DFSPCCC0

Related tasksIRLM return and reason codesRelated information“DFS039I” on page 31IMS WAITING FOR IRLM ARM READY.0039 (Messages and Codes)“IMS problem determination” on page 11IMS messages and codes problemdetermination is accomplished by usingprocedures established by IBM.

DFS040I UNABLE TO ACQUIRE COMMANDLOCK, DATA SHARINGDISCONTINUED

ExplanationIMS attempted to acquire the command lock afterlinkage was established with the IRLM. The commandlock is used for communication between sharing IMSsubsystems and is required when data is shared.

System actionIMS continues without data sharing.

Operator response:(master terminal) Ensure that communication hasbeen reestablished between sharing IRLMs. If datasharing is required, shut down IMS and restart it.

Module:DFSRST00, DFSPCCC0

DFS041I DBRC SIGNON REQUEST RC=cc

ExplanationA sign-on request to DBRC completed with the returncode cc specified. For the definition of the return code,see the DBRC request return codes information.

System actionIf the return code indicates a severe error, IMSterminates with abend 0041; otherwise, executioncontinues.

Return codes 16 and 24 might cause IMS to terminatewith abend 0041.

Return codes 8, 12, 20, 28, 32, and 41 cause IMS toterminate with abend 0041.

Programmer responseA sign-on failure can occur if the sign-on requestspecified a subsystem ID existing in the RECONdata set. See the DBRC CHANGE.SUBSYS orDELETE.SUBSYS command for information aboutupdating the subsystem record in RECON.

You can take the following actions depending on thereturn code cc. All other return codes indicate apossible system error; see DBRC request return codesinformation for any return codes not listed here.8,12,16,20

This problem occurs during a cold or warm startof an online system or during initialization of abatch system. The code indicates that there is aconflict between the subcode system ID in this



http://www.ibm.com/support/knowledgecenter/SSEPH2_15.1.0/com.ibm.ims15.doc.msgs/msgs/0039.htm#imsabend0039

system and DBRC. The subsystem ID is the IMSIDfor online systems or the job name for batchsystems. Either change the subsystem ID for thissystem and resubmit the job, or list the subsystementry already known to DBRC and determine why aduplicate exists.

24This problem occurs during emergency restart orbatch backout, for information only, and indicatesthat the previous execution failed withoutinforming DBRC of the abnormal termination. Noaction is required.

28This problem occurs during batch backout andindicates that DBRC is not aware of the subsystementry for the log supplied to batch backout. Ensurethat the proper log is used. If it is, then batchbackout was not needed and no further action isrequired. This occurs during batch backout andindicates that DBRC is not aware of the subsystementry. The batch backout probably does not haveto be done, and no action is required.

32This problem occurs during emergency restart orbatch backout and indicates that a change hasbeen made in the IRLM name. Rerun the job,specifying the same IRLM name as used in theoriginal execution.

41This problem occurs during sign-on to DBRC andindicates that a 24 K IMODULE GETMAIN requestfor subpool 0 storage failed. Register 8 in theabend registers contains the return code from theIMODULE GETMAIN failure. For more information,see the IMODULE return code information.

96The subsystem attempting to sign on is an earlierrelease than is allowed. Check the MINIMUMVERSION value in the RECON data set.


Module:DFSRST00, DFSPCCC0, DFSRCP00

Related referenceDBRC request return codes (Messages andCodes)IMODULE return codes (Messages and Codes)Related information“IMS problem determination” on page 11IMS messages and codes problemdetermination is accomplished by usingprocedures established by IBM.

DFS042I BACKOUT REQUIRED, DBRCSIGNON FAILED

ExplanationAfter processing the input log, it was determined thata backout was required. The sign-on to DBRC indicatedthat an entry did not exist for this subsystem and thatthe previous execution of this subsystem indicatedthat DBRC was active during its execution. The samecondition is required to be established when runningan emergency restart.

System actionIMS terminates abnormally when a critical error occurswith abend 0042.

Programmer responseEnsure that DBRC is specified for this execution of IMSor that the same RECON data set is used.


Module:DFSRLP00

Related informationIMS abend 0042“IMS problem determination” on page 11IMS messages and codes problemdetermination is accomplished by usingprocedures established by IBM.

DFS043I DBRC SIGNON REQUEST FORRECOVERY END FAILED, RC=cc

ExplanationAfter the emergency restart or batch backout processcompletes, a sign-on for "recovery end" is issued tonotify DBRC that the recovery process had completedsuccessfully. However, the request was not successfuland the return code specifies the error detected byDBRC. For the definition of the return codes, see theDBRC request return codes information.


Programmer responseCheck the return code and take proper action.





http://www.ibm.com/support/knowledgecenter/SSEPH2_15.1.0/com.ibm.ims15.doc.msgs/compcodes/ims_imoduleretcodes.htm#ims_imoduleretcodes


Module:DFSPCCC0, DFSRST00

Related referenceDBRC request return codes (Messages andCodes)Related information0043 (Messages and Codes)“IMS problem determination” on page 11IMS messages and codes problemdetermination is accomplished by usingprocedures established by IBM.

DFS044I DBRC TURNED OFF FOR THISEXECUTION

or

DBRC REQUIRED FOR THIS EXECUTION

ExplanationOne of the following problems occurs when DBRCREQUIRED FOR or TURNED OFF displays:

• A utility program attempted to run against a HALDBwithout DBRC.

• DBRC REQUIRED FOR THIS EXECUTION

DBRC=FORCE was specified in the installationdefaults module DFSIDEF0. DBRC=N was specifiedas an execution-time parameter for this step.

Database backout was running; DBRC was notactive and was not overridden by an execution-timeparameter of DBRC=N. The previous execution ofIMS had used DBRC, and DBRC was not specifiedfor this execution. The same condition used in theprevious execution, namely utilization of DBRC, mustbe used in this condition for database backoutunless DBRC is overridden by DBRC=N. If the IRLMwas active during the previous execution, DBRCmust always be active during this execution ofdatabase backout.

• DBRC TURNED OFF FOR THIS EXECUTION

Database backout is running. DBRC=N was specifiedfor this execution, and DBRC was active in theprevious execution. Processing continues normallywithout DBRC.

System actionWhen DBRC REQUIRED FOR THIS EXECUTIONappears, the job terminates abnormally. When DBRCTURNED OFF THIS EXECUTION appears, processing

continues normally. DBRC is not used during thisexecution.

Programmer responseWhen DBRC REQUIRED FOR THIS EXECUTIONappears, ensure that DBRC is present for thisexecution. For database backout, an execution-timeparameter of DBRC=N can be specified if IRLM was notpresent in the previous execution.

When DBRC TURNED OFF FOR THIS EXECUTIONoccurs, processing continues without DBRC. Beforereactivating DBRC, record the information aboutthe OLDS data set (IMS log) created by thisbackout execution while DBRC was inactive in RECONusing the DBRC commands NOTIFY.PRILOG andNOTIFY.SECLOG.


Module:DBFUMIN0, DFSRLP00, DFSBCKI0


DFS045I IRLM REQUIRED FOR THISEXECUTION

ExplanationA /ERE was entered for an emergency restart, ordatabase backout was executing and the IRLM wasnot active. previous execution of IMS had utilizedthe IRLM, and for this execution the IRLM was notspecified. It is required for an emergency restart and adatabase backout that the same condition used by theprevious execution of IMS exists for this execution.

System actionIMS terminates abnormally with abend 0045. Adatabase backout terminates with a nonzero returncode.

Programmer responseEnsure that the IRLM is present for this executionor that the proper IRLM was specified. IRLM= orthe IRLMNM= parameters should have the samespecification.






ModuleDFSBCKI0, DFSRLP00, DFSRST00


DFS046A PROCESSING INTENT pppppppFOR DATA BASE xxxxxxxx NOTCOMPATIBLE WITH ACCESS zz.PSB=PSB name.

ExplanationOne of the DB-PCBs contained in the named PSBreferenced the named database xxxxxxxx whichhad an incompatible PROCESSING INTENT pppppppwith the ACCESS parameter zz defined in thedatabase statement for the IMS online subsystem.The PROCESSING INTENT, READ-GO, READ, UPDATE,or EXCL is derived from the PROCOPT specificationsin the PSBGEN. The PSB name only appears in themessage text if the IMS is an online subsystem.

System actionA batch region (DL/I or DBB region) will terminate withabend 0046. Dependent regions continue processing,but the programs cannot access the database. Anattempt to access the database will result in either a'BA' status code, if the program has issued the INITcall, or in abend 3303, if the program has not issuedthe INIT call. If the database is a Fast Path DEDB, thePSB is stopped.

Operator response:(master terminal) Notify your IMS systemprogrammer of the message.

Programmer responseOne of the following responses should be taken:

• Contact the master terminal operator to change thedatabase ACCESS parameter to the level compatiblewith your PROCESSING INTENT.

• Change the PROCOPT operand specifications tothe level compatible with the ACCESS parameterdefined in the database statement for the IMS onlinesubsystem. Rerun ACBGEN, and then the job.

Problem determination6, 10, 29

ModuleDBFDBPV0, DFSDBAU0


DFS047A UNABLE TO OBTAINAUTHORIZATION FOR DATA BASExxxxxxxx. REASON CODE = zz.PSB= psbname.

ExplanationIMS was unable to obtain database authorization forthe database identified by xxxxxxxx. The databaseappears in one of the DB PCBs contained in psbnameduring PSB scheduling. The PSB name only appears inthe message text if the IMS is an online control region.Code (hex)

Meaning01

The requested state and the current authorizationstate (see RECON data set) are incompatible.The database is authorized by another active orabnormally terminated IMS subsystem, and itsauthorization state is incompatible with the currentauthorization request.

02The database is not registered in the RECON dataset.

03The database is marked as prohibiting furtherauthorization for one of the following reasons: aglobal /DBRECOVERY, a global /STOP, an UPDATEDB STOP, or a CHANGE.DB(NOAUTH) command.

04The database is authorized only if therequested state is "READ" or "READ-GO" becauseof a global /DBDUMP or an UPDATE DBSTOP(UPDATES) command.

05The database is marked as needing an image copy.

06The database is marked as needing recovery.

07The database is marked as needing backout. In adata sharing environment, you can use a LIST.DBcommand to determine which subsystems requireback outs for the named database.


08For sharing within a host, the requestingsubsystem is not within the authorized host.

09One or more subsystems for which the databasehas been previously authorized are supposed to beactive, but the subsystems are not known to IRLM.IRLM=N or another IRLM name might have beenspecified on the subsystem.

10The database has been previously authorized tothe subsystem.

11An invalid parameter is found during the databaseusage compatibility evaluation process. Possibly,the database record in the RECON data set is bad.

12The current authorization state in DBRC is invalidbecause of a not authorized error.

13An error occurred in DBRC while trying to processan authorization request.

14An error occurred in DBRC while trying to process achange authorization request.

15The database is already authorized to an activeIMS subsystem.

16The area is not marked as needing recovery for theDEDB initialization utility.

18The Fast Path area is currently being altered.

19The data set name of the database data set passedto DBRC does not match the data set name in theRECON data set.

20Database authorization failed because thedatabase was not registered with DBRC. Inaddition, the DBRC RECON data sets wereinitialized with FORCER, which requires that alldatabases must be registered.

This error might be the result of a mismatch ofdata set names in the RECON data set and in thedynamic allocation blocks (DFSMDA members).

22The database is currently authorized to anothersubsystem.

31The definition of the HALDB has changed. Youmust perform a partition structure rebuild beforeauthorization can be granted for the partition.

Issue a /START DB command with the OPENkeyword for the HALDB master to perform therebuild

32The HALDB needs to be initialized.

33An attempt has been made to authorize the HALDBmaster. Authorization can only be requested at thepartition level.

34Partition Initialization is requesting authorizationfor a partition that does not need to be initialized.

35The DB partition cannot be authorized until a highkey is defined. A key is required because theHALDB master does not use a Partition SelectionRoutine.

36Image copy not allowed during HALDB OLRprocessing.

37Loading into an M-through-V DBDS of a partitiondatabase is not allowed.

38Offline reorganization is not allowed when HALDBOLR is active and the HALDB OLR is owned by anIMS subsystem.

39A HALDB partition database can be reorganizedonline. This release of IMS does not supportrunning database utilities for OLRCAP databases.

40Batch jobs are not allowed authorization when theREORG INTENT = ON is set for the database. Thedatabase is currently being reorganized. Onlineimage copy also fails authorization.

41The database is quiesced or in the process of beingquiesced.

42The database is not quiesce held and image copyattempting authorization.

43The randomizer name that was passed is differentfrom the randomizer name stored in the RECON.

80The partition name table DFSPNT is not initializedfor the specified HALDB partition.

81An error occurred attempting to load the masterDMB for the specified HALDB partition.


82An error occurred attempting to load a DMB ofthe altered version of a HALDB partition thatis identified by DATA BASE = xxxxxxxx in themessage text. Message DFS3547E, which is issuedto the system console before message DFS047A,contains information about why the DMB could notbe loaded.

83IMS could not build the internal blocks that arerequired to access a HALDB partition that has astatus of ALTER IN PROGRESS in the RECON dataset, therefore authorization to the HALDB partitionfailed. The partition is identified by DATA BASE =xxxxxxxx in the message text. Message DFS1849E,which is issued to the system console beforemessage DFS047A, identifies the reason that theinternal blocks could not be built.

System actionA batch region (DL/I or DBB region) terminates withabend 0047. The database is stopped. Dependentregions continue processing, but programs cannotaccess the database. An attempt to access thedatabase will result in either a BA status code, if theprogram has issued the INIT call, or in abend 3303, ifthe program has not issued the INIT call.

For reason codes 41 and 42, the authorization requestis denied.

Programmer responseReason codes 01 through 09 and 15 through 19,indicating a temporary authorization failure, can becorrected by one of the following actions:

• Wait for a currently authorized subsystem toterminate or enter a /DBRecovery UPDATE DBSTOP(ACCESS) to unauthorize the database fromthe currently authorized subsystems. Batch backoutor an emergency restart might be required for anabnormally terminated subsystem. (RC 01, 08 or 15)

• Verify that the correct log is input to the batchbackout utility if DBRC=C is being used. (RC 01)

• Enter a /START DB or UPDATE DBSTART(ACCESS), a /DBDUMP or UPDATE DBSTART(UPDATES), or a CHANGE.DB (auth)command. (RC 03)

• Enter a /START DB or UPDATE DBSTART(ACCESS) command. (RC 04)

• Run the appropriate IMS utility. (RC 05, 06 or 07)• Run this IMS subsystem on the host where the

database is currently authorized. (RC 08)

• Wait for the failed subsystems to complete theemergency restart or database backout. (RC 09)

• Use the DBRC command CHANGE.SUBSYS toindicate that an IMS subsystem is no longer active.(RC 15)

• Use the DBRC CHANGE.DBDS command to mark anarea as needing recovery. (RC 16)

• Use the DBRC INIT.DBDS command to register aDBDS or DEDB area to DBRC. (RC 18, 19)

• Wait for the DEDB Alter utility to complete or use theDBRC CHANGE.DB NOALTER command to indicatethe DEDB Alter utility is no longer active (RC 18).If the "QUIESCE" status is set in the RECON, usethe CHANGE.DBDS NODBQUI command to reset thequiesce status.

• In ACBSHR=N environment, the DEDB Alter utilitychanged the randomizer while the IMS was down.

• Check the RECON data set to determine the correctauthorization state.

Reason codes 10 through 14 indicate that a systemerror has occurred. If these problems persist, contactIBM for problem determination assistance.

For reason code 33, check the DBDLIB level of thedatabases to make sure that they match the RECONlevel.

For reason codes 41 and 42, wait for the quiesceto end and rerun the job which failed authorization.The status of the database can be determined byissuing /DISPLAY DB QSC, /DISPLAY STATUSDB, or Query DB, or LIST.DB DBD(dbname), andexamining the output. If the image copy failed, waitfor the quiesce to end or until the QUIESCE HELD flagis set on. You can set the QUIESCE HELD flag on byUPD START(QUIESCE) OPTION(HOLD) commandprocessing when quiesce has occurred.

For reason code 82, see message DFS3547E, whichis issued to the system console before messageDFS047A.

For reason code 83, see message DFS1849E, whichis issued to the system console before messageDFS047A.

Problem determination35

Module:DFSDBAU0

Related information“DFS1849E” on page 537CHANGE NOT SUPPORTED BY ALTER OPTIONRS=rsnc PST=pstno SEGMENT segmname“DFS3547E” on page 997


UNABLE TO LOAD ALTERED DEFINITIONS FORDATABASE db_name, RSN=rsn“IMS problem determination” on page 11IMS messages and codes problemdetermination is accomplished by usingprocedures established by IBM.

DFS0048I DBRC INITIALIZATION FAILED -RC = nn

ExplanationThe initialization for DBRC failed for one of thefollowing reasons:Code (Dec)

Meaning4

IMODULE GETMAIN for DFSRCWK failed.8

IMODULE LOAD failed for one of the IMS/DBRCcontrol modules.

12Database Recovery Control initialization first pass(INIT-0) was not successful.

16Database Recovery Control initialization secondpass (INIT-1) was not successful.

20Quick save get failed for one of the IMS DBRCcontrol modules.

24ITASK CREATE failed for one of the IMS DBRCcontrol modules.

28IMODULE LOAD for DFSRSMD0 failed.

32DFSRSMD0 call failed.


Programmer responseSee abend 0048.

Problem determination1, 2, 3, 4, 8, 12

ModuleDFSXRIC0, DFSXRID0


DFS049I UNABLE TO OBTAIN STORAGETO BUILD DATA BASEAUTHORIZATION REQUEST LIST.PSB yyyyyyyy STOPPED.

ExplanationA conditional GETMAIN was issued in an attempt toobtain a larger work storage area to build the databaseauthorization request list. However, the GETMAINfailed. The reason for the failure is due either tothe PSB yyyyyyyy, which contains too many databasePCBs, or to the small REGION size specified in the JOBstartup JCL.

System actionThe named PSB is stopped. For an MPP, the inputmessage is placed back into the message queue.For a BMP, IFP, DBB, or DLI region type, the regionterminates abnormally with abend 0047.

While processing a command such as a /START DBcommand, no program specification block (PSB) existsand abend 0047 is not issued. If the failure occursduring a restart with in-doubt units of recovery, abend0484 is issued.


Programmer responseTake one of the following actions:

• For an online subsystem, increase the size of theREGION parameter in the IMS control region startupJCL. For a batch subsystem, increase the size of theREGION parameter in the JOB startup JCL.

• Change the PSB to contain a lesser number ofdatabase PCBs. Rerun ACBGEN and then the job.

Problem determination:6, 10, 19

Module:DFSDBAU0

Related information0047 (Messages and Codes)0484 (Messages and Codes)“IMS problem determination” on page 11



http://www.ibm.com/support/knowledgecenter/SSEPH2_15.1.0/com.ibm.ims15.doc.msgs/msgs/0484.htm#imsaben0484


DFS050A SHARED ACCESS TO VSAMDATASET ddname NOT ALLOWEDBY CATALOG

ExplanationDL/I open processing of the database containing thedata set ddname detected that SHR (3,3) was notspecified on the Access Method Services DEFINEcommand and that DISP=SHR was not specified onthe DD statement for the data set. SHR(3,3) andDISP=SHR must be specified when these are true:

• SHARELVL=2 or 3 is specified for the database onthe INIT.DB or CHANGE.DB command.

• ACCESS=RD or UP is specified for the database onthe system definition DATA BASE macro statementor on the /START command.

For an XRF-capable IMS system, databases must beSHR(3,3). Message DFS0730I contains the databasename.

This message can also be issued because there isno VSI for the VSAM data set in a data sharingenvironment.

AnalysisDFS050A is most commonly issued when one of thefollowing statements is not true:

• The VSAM SHAREOPTIONS on the DEFINE CLUSTERis not specified as (3 3).

• The DISP is not SHR in the JCL or the DFSMDA block.

Possible cause: You must define VSAM databasedatasets with SHAREOPTIONS(3 3) and allocate themwith DISP=SHR to use database sharing.

System actionMessage DFS0730I reason code I,33 is issued. Seethe "System action" section for message DFS0730I.

Programmer responseCorrect the SHR options and disposition specifiedfor the data set if shared access to the database iswanted. If not, the CHANGE.DB command can be usedto change the SHARELVL specification for the databaseto 0 or 1. If ACCESS=RO or EX is specified for thedatabase for IMS system definition, or on the /STARTcommand, the error will not occur.

Problem determination:2, 6, 8, 10, 20

Module:DFSDLOC0

Related information“DFS0730I” on page 257UNABLE TO OPEN OR CLOSE DATASET WITHDDNAME ddname FOR REASON x, yy, zDATABASE dbdname programid“IMS problem determination” on page 11IMS messages and codes problemdetermination is accomplished by usingprocedures established by IBM.


Chapter 5. DFS messages, DFS051I - DFS100


DFS051I hh.mm.ss RESTART IN PROGRESSLINE xxxx aa,bbbb,cc,dd,ee,ff,gg,hh,iiii,jjjj

ExplanationAttention: IMS no longer supports BTAMterminals.

An I/O error occurred on a component of the remote3270 network indicated by the line number. Theremote 3270 device-dependent module generatesa /RSTART command for the appropriate physicalterminals in an attempt to restart the physicalterminals affected by the I/O error. If the errorpersists, the device-dependent module attempts the /RSTART command a specified number of times andwhen the limit is reached, marks the appropriatecomponents inoperable. A description of the errorinformation contained in the message is as follows:aa

This field contains the ECB completion code.bbbb

The DECTYPE field indicates the type of failingoperation.

ccThe DECTPCOD field indicates the datacommunication operation code from the last CCWexecuted in the channel program.

ddThe DECFLAGS field contains the flag byte passedto IMS from BTAM. The field might containinformation as to the cause of the failure.

eeThe DECSENS0 field contains the senseinformation from the DECB if the status in the CSWindicates a unit check.

ffThe DECERRST is the error status field from theDECB.

ggThe DECCSWST is the CSW status field from theDECB.

hhThis field contains the device-dependentmodule code. When the 3270 device-dependentmodule shuts down a component of the datacommunication network, a device-dependentmodule reason code is put in the CLBTEMP1 field

to indicate why the device-dependent module shutthe component down.

iiiiThis field contains the BSCK return code. The codeis passed from the BSC check routine (DFSBSCK0)to the device-dependent module. The BSC checkroutine analyzes the I/O completion and passesa unique return code to the device-dependentmodule, depending on the contents of the DECBfields.

The function code and response codes displayed infield iiii are described below.

jjjjThis field contains the SENSE/STATUS informationfrom the 3270 device (if applicable). See IBM 3270Information Display System for an explanation ofthe SENSE/STATUS codes.

The function code replaces the first two characters infield iiii. It is returned in register 0 and has one of thefollowing meanings:Code

MeaningX'00'

UndeterminedX'01'

SelectionX'02'

PollingX'03'

Read dataX'04'

Write dataX'05'

ReservedX'06'

ReservedX'07'

Reserved

The response code replaces the last two characters inthe field iiii. It is returned in register 15 and has one ofthe following meanings:Code

MeaningX'00'

No error detected


X'01'Wait for acknowledgment (WACK)

X'02'Contention

X'03'Negative acknowledgment (NACK)

X'04'End-of-transmission (EOT)

X'05'Reverse interrupt (RV1)

X'06'No entries in polling list

X'07'Negative response

X'08'No response

X'09'Block ended with ENQ (or ENQ only)

X'10'SOH%S message

X'11'SOH%R message

X'12'Reserved

X'13'Invalid response

X'14'Start-of-text—enqueue (STX—ENQ) sequence

X'15'Temporary text delay (TTD)

X'16'Incorrect alternating acknowledgment

X'17'–X'31'Reserved

X'32'Undetermined error

X'33'270X error

X'34'Line error

X'35'–X'63'Reserved

In addition to the error information contained in themessage, the device-dependent module logs out, onthe IMS log data set, all of the IMS control blocks fromthe time of failure in an X'6703' record.

Module:DFSC3270

DFS052 CARD ENTRY INDICATED, NOCARD DATA FOUND

ExplanationA hardware malfunction occurred on a 3270 magneticcard reader. The AID byte indicated that a readoperation was requested, but the card data was notreceived in the TP buffer.

System actionInput is ignored.

Operator responseCarefully reinsert the card. If the problem recurs,perform the terminal troubleshooting procedures.

Module:DFSCFE00

DFS053 TERMINAL RESTARTED-PLEASEREFORMAT SCREEN

ExplanationAs a result of an I/O error, a terminal that was inconversation or exclusive mode, was stopped and hasnow been restarted.

System actionThe system continues normal processing.

Operator responseIf the terminal was in conversational mode, enter a /HOLD followed by a /RELEASE command to reformatthe screen with the last format sent before thismessage.

Module:DFSDN130

DFS054 INPUT NOT ALLOWED TILLPRINTER IS AVAILABLE

ExplanationInput from a 3277 is not permitted while a 3284/3286printer is busy processing a copy operation.

System actionThe input is ignored.

Operator response:(terminal operator) Wait until the printer becomesavailable.


Module:DFSCFEP0

DFS055 INCORRECT RESPONSEREQUESTED

ExplanationThe response requested by a logical unit did notagree with the INQUIRY= parameters specified for thistransaction at system definition.

System actionThe input is rejected.

Operator response:Reinitiate the session.

Problem determinationThis problem is a probable user error in the systemdefinition or the Intelligent Remote program in thelogical unit. Update transactions, recoverable inquirytransactions, and message switches must requesta positive response. Unrecoverable transactions canoptionally request a positive response.

Module:DFSICIO0

DFS056 COMMAND NOT VALID WITH MFSOPTION 3

ExplanationYou entered a command, and the Message InputDescription (MID) has the parameter OPT=3 coded.

System actionThe command is not processed.

Operator response:(remote terminal) Because this message wasformatted using the default blocks, which do not useoption 3, the command can be reentered at this time.

Module:DFSICL30

DFS057I REQUESTED BLOCK NOTAVAILABLE: blockname RC =reason

ExplanationMFS cannot fetch the control blocks required toprocess an output message or to process the /FORMATrequest. blockname in the message identifies theblock that could not be fetched and is either the MOD

or the DOF name. If it is the DOF name, the first twobytes of the name are the device type and featuresprinted in hexadecimal. For an interpretation of thesetwo bytes, see Format library member selection(Application Programming APIs).

The reason code reason indicates the type of failurethat occurred:Code (hex)

Meaning04

The indicated block name was not found inthe active format data set library. The followingconditions can cause this reason code to beproduced:

• There is a misspelled message output descriptor(MOD) name or the MOD does not exist in theactive format data set library.

• A device output format (DOF) for the specifiedMOD with the device type and feature indicateddoes not exist in the active format data setlibrary.

08There is a permanent I/O error in the active formatdata set library.

0CThe main storage space required for the MOD orDOF, or both, is greater than the maximum spacecurrently available in the message format bufferpool. Alternatively, no fetch request elements(FREs) were available. This return code is issuedonly by prefetch routines, not by immediate fetchroutines.

14A MOD block was to be fetched. The fetched blockwas not a MOD.

18The MOD block fetched was compiled beforeRelease 1.1.1 of IMS.

1CThe MOD and DOF fetched were incompatible (notcompiled at the same time). The use of z/OSutilities to alter the active format data set librarycan cause this problem.

20The MOD or DOF contains an invalid field. Thisproblem can be caused by modification of, ordamage to, the format or test format library.

24The requested MOD or DOF is too large for themessage format buffer pool (MFBP). The MFBPmust be increased. Notify the system programmer.

Chapter 5. DFS messages, DFS051I - DFS100 43

http://www.ibm.com/support/knowledgecenter/SSEPH2_15.1.0/com.ibm.ims15.doc.apr/ims_formatlibrary.htm#ims_formatlibrary


28The DOF and CIB screen sizes are incompatible.This problem occurs only for 3270-AN devicetypes. The screen size defined for systemdefinition was different from the size in the devicecharacteristics table, DFSUDTOX. The systemprogrammer should ensure that the correct devicecharacteristics table is used.

38The MOD is not available because use of the MODcauses the HIOP storage pool to be overwritten.

78The DOF is not available because use of the DOFcauses the HIOP storage pool to be overwritten.

System actionSince the requested blocks were not available, IMSformatted and sent the message using the 'defaultblock error message format (DFSMO3)', and thendequeued the message.

If TRACE is set on for this NODE/PTERM, an X'67'record is created on the IMS log with the ID of "FERR".

Operator response(master terminal) Take the following action to correctthe errors:

For reason code 20:

Stop using the transactions using the MOD or the DOF,or both, for a time sufficient to allow the blocks tobe replaced by others in the Message Format. Try thefailing transaction again. If the error persists, the blockwas destroyed in the FORMAT or TFORMAT library, anerror was compiled into the block, or there is an errorin one of the MFS online modules. If the error does notrecur, data was overlaid in the message format bufferpool. In both cases, the X'67' log record containshelpful information.

For reason codes 38 and 78:

Stop using the transactions using the MOD, the DOF,or both until the blocks can be replaced. The MOD orDOF and its format set must be recompiled and thenreplaced using the online change process. The invalidblock might have been destroyed in the FORMATlibrary, an error might have been compiled into theblock, or an error exists in one of the MFS onlinemodules.

Two X'67' log records are written to the IMSlog. The first record has an ID of MTRP and hasinformation useful for diagnosing the reason forpotential overwrite. The second record has an ID ofFERR and records the unavailability of the MOD orDOF.

Programmer responseTake the following action to correct the errors.

For reason code 04:

• Ensure that the MOD name provided from theapplication program, by the previous Message InputDescription (MID) NXT= parameter, or in a /FORMATcommand is spelled correctly and that the MODexists in the active format data set library.

• Ensure that the DOF exists in the active format dataset library with the device type and features of theterminal receiving the error message. If the MODspecifies the IGNORE option, the DOF must have theIGNORE feature specified.

For reason code 0C:

Use the MFS utility to determine the combined sizeof the MOD and DOF. Increase the space available forformat blocks in the message format buffer pool usingthe "HHH" parameter on the IMS control region EXECstatement.

For reason codes 14 and 1C:

Reprocess the message source definition using theMFS Language utility.

For reason code 18:

The MFS libraries from previous versions cannot beused. All message and format source definitions mustbe recompiled using the MFS Language utility.


Module:DFSCFEO0

Related referenceFormat library member selection (ApplicationProgramming APIs)Related information“IMS problem determination” on page 11IMS messages and codes problemdetermination is accomplished by usingprocedures established by IBM.

DFS058I CCC COMMAND COMPLETEDEXCEPT KKK P01, P02, P03, P04,P05, P06, P07, ...ETC.

or

CCC COMMAND IN PROGRESS

or




CCC COMMAND COMPLETED

ExplanationIn the message text:

CCCCommand name of three or more characters.

KKKKeyword name of three or more variables.

P0nThe parameter name, where n=1-10. Assumethat it is at least three characters, since mostinstallations have resource names of three or morecharacters.

ETCThe terminal entering the command received theexception parameters on one line, followed by ETCif there were more exceptions.

The EXCEPT phrase indicates which parameterswere not processed. See the information about thecommand to understand possible errors when theEXCEPT phrase is used.

When an exception is found while processing a genericparameter, up to 10 of the specific resource names inerror that match the generic parameter are moved tothe end of the condensed command buffer. They arethen marked in error. Thus, if 20 resources matchingthe generic parameter could not be processed bythe command, only ten of them are moved into thecondensed command buffer and are marked in error.The number 10 is selected to guarantee that ETCappears at the end of the DFS058 message. It isassumed that the display line of the message is amaximum of 79 bytes.

System actionThe system continues processing.

Programmer responseVerify that the present command is correct.

Module:DFSCLMO0

DFS059I TERMINAL status

ExplanationInformation at a local or remote terminal informs theoperator of terminal status.

Operator response:(local/remote terminal) Take the action requireddepending on the status information.

Module:DFSCLMO0

DFS060 nnn IS AN INVALID MESSAGE KEY

ExplanationThe number (nnn) was passed to the messagegenerator module by some other module in thesystem. However, this message number was not foundin the message table.

Another possibility is that a message in the UserMessage table is longer than 128 characters.

System programmer response:Ensure that no message in the User Message table islonger than 128 characters.

Problem determination:1 or 6 or 7 and 36

Module:DFSCLMR0

Related referenceUser Message table (DFSCMTU0) (Exit Routines)Related information“IMS problem determination” on page 11IMS messages and codes problemdetermination is accomplished by usingprocedures established by IBM.

DFS0061I INVALID CALL TO MESSAGEGENERATOR: reason

ExplanationPossible values of reason are:

• 'CONSOLE CNT(WTOR) NOT FOUND.'• 'ERROR HAPPENED ON REROUTE.'• 'MSG NOT LOCKED INCORE FOR ICIO.'• 'INCORRECT CALLER.'• 'REMOTE DESTINATION IS NOT A CNT.'• 'QUEUES ARE NOT AVAILABLE.'• 'NEGATIVE MSG LENGTH.'• 'INNER SEG LENGTH > TOTAL LENGTH.'• 'INVALID MSG TYPE.'• 'NONZERO RETURN CODE FROM ROUTER.'• 'CQS ENQUEUE FAILS.'

A module within IMS called the message generatorand failed to provide a proper call interface.


http://www.ibm.com/support/knowledgecenter/SSEPH2_15.1.0/com.ibm.ims15.doc.err/ims_dfscmtu0.htm#ims_dfscmtu0

System actionIMS logs the error information using a type X'6701' logrecord.

Problem determination1, 6, or 7

ModuleDFSCLMR0


DFS0062W LOAD FAILED FORDRU EXIT xxxxxxxxTMEMBER=yyyyyyyyyyyyyyyy

ExplanationThe OTMA Destination Resolution (DRU) exit, that wasspecified on the client-bid or a partner create request,failed to load.

In the message text:xxxxxxxx

The name of the DRU exityyyyyyyyyyyyyyyy

The transaction member (tmember) name

This message appears on the IMS master terminal andthe write-to-operator (WTO) terminal.

This message only appears on the IMS masterterminal.

System action:Client-bid or partner-create continues without the DRUexit.

Programmer response:Verify that the DRU exit specified is needed. If not, youcan ignore this message. If the DRU exit is needed,disconnect the client and correct the problem byensuring that the DRU name is correct and that themodule resides in the IMS STEPLIB. Then reconnectthe client.

DFS063I RESTART COMMAND REQUIRED

ExplanationNo input is allowed before a restart command.

System actionThe command is ignored.

Operator response:(master terminal) Enter either an /ERESTART or an /NRESTART command.

Module:DFSICIO0, DFSICL30

DFS064I DESTINATION CAN NOT BE FOUNDOR CREATED, DEST=destination [I:sss1/name1, D: sss2/name2]

ExplanationThe first eight characters of the input could not berecognized as a valid transaction, logical terminalname, or command.

In the message text:sss1/name1

The source SYSID and source LTERM name for theinput system.

sss2/name2The destination SYSID and destination LTERM orTRAN code of the processing system.

This information appears only when the error isdetected in a remote system (sss2).

destinationThe name of the destination that could not befound or created.

This message can occur if all the following conditionsare true:

• A terminal is not in a conversational or preset mode.• The Global Physical Terminal Input edit routine did

not exist for the terminal.• The MFS bypass with MODname DFS.EDTN is used.

When all three of these conditions are true, theAttention Identification (AID) byte is the first item inthe data area. It is rejected as an invalid transactioncode.

This message can also be issued if either of thefollowing conditions are true:

• The Message Control/Error Exit routine (DFSCMUX0)is customized in the receiving system to specify anincorrect exit flag.

• The exit flag is correct, but an error was found whileIMS was performing the requested action and IMSperformed the associated default action instead.

For CPIC/APPC transactions failing with DFS064 as aconsequence of the TP profile (TPN) being deleted, themessage contains only the first eight characters of the


TPName that was not found. Use this information toidentify the resource that was not found.

System actionThe data entered is ignored.

Operator response(local/remote terminal) Reenter the data correctly. Ifthe MFS bypass was not used, establish preset modeby using the /SET TRANSACTION command. If it stillfails, notify the System Programmer.

(master terminal) Inform the system programmer.

If the optional part of this message is printed, notifythe system programmer that the blocks are notsynchronized.

Problem determination:14

Module:DFSICIO0


DFS065 TRAN/LTERM STOPPED, T/L=name[I: sss1/name1, D: sss2/name2]

ExplanationA /STOP command has stopped queuing on thedestination queue.





nameThe name of the transaction or LTERM that wasstopped.


Operator response(local/remote terminal) Inform the systemprogrammer. Start the transaction or logical terminal,and reenter the data.

If the optional part of this message is printed, startthe transaction or logical terminal. Then notify thedestination system master terminal operator and itssystem programmer.


Module:DFSICIO0


DFS0066I NOTIFY RESPONSE HAS COMEBACK FROM ims_id

ExplanationIMS Fast Path has a sysplex communication protocol,which utilizes the IRLM notify process to communicatewith all sharing IMS subsystems in the sysplex.IMS waits until all IMS subsystems respond to thesysplex communication protocol, or until the initiatingIMS times out the notify, terminating the requestedfunction. This IMS sent a sysplex communicationmessage to the other sysplex members, and aresponse came back from ims_id.

In the message text:ims_id

The IMS ID of the sysplex member thatsuccessfully returned a response to the NOTIFYmessage.

System programmer response:No action is required for this particular ims_id.However, if this message has not been returned foranother sysplex member, check whether that IMS onthe sysplex is waiting for some interruption or is havinga problem.


DFS0067W SLDS READ DATASPACE STORAGERELEASED


ExplanationEither a /STOP SLDSREAD command was entered orz/OS notified IMS that a shortage of auxiliary storagewas encountered. IMS has terminated system log dataset (SLDS) read activity and released its dataspacestorage.

System actionThe internal IMS functions that require SLDS data fail.One or more of the following functions can fail:

• Dynamic backout• Batch message processing (BMP) extended restart

(XRST)• Unit of work table entry (UOWE) resynchronization

Other IMS processing continues.

Operator responseStorage shortages are often the result of morethan one internal work unit needing SLDS datasimultaneously. BMPs using XRST are especiallyvulnerable if the records needed are widely separatedon the log. Trying the failed functions again seriallyoften resolves the problem.

For UOWE resynchronization, repeated attemptsto retry the function can result in incrementalimprovements until success is achieved.

If the auxiliary storage shortage involved competitionwith other jobs or z/OS components and the failedfunction was dynamic backout, try restart the affecteddatabases when more storage becomes available. Ifnot, batch backout is required.

DFS068 BACKSPACE BEYOND MSG START

ExplanationThe input editor module stepped backward beyondthe beginning of the message attempting to eliminatebackspaces.


Operator response:Correct the data and rerun the command.

Module:DFSCFEI0, DFSICIO0

DFS069 TERMINAL INACTIVE

ExplanationThe source physical or logical terminal is not activebecause:

• It is LOCKED.• A /STOP or /PSTOP was entered.• Input was stopped by a /PURGE command.• There is no LTERM assigned for the input PTERM.


Operator response:Correct the condition through the UNLOCK, START, or /ASSIGN command, and reenter the data.

Module:DFSICIO0

DFS070 UNABLE TO ROUTE MESSAGERSN=xxyy (I: sss1/name1, D: sss2/name2)

ExplanationOne of the following situations occurred and an errorwas encountered while routing the message:

• IMS attempted to enqueue a message.• A /FORMAT command was entered.• One of these entry points in the TM and MSC

Message Routing and Control user exit (DFSMSCE0)attempted to reroute a message:

– Link Receive Routing– Program Routing– Terminal Routing

In the message text:xx

The IMS module that detected the error:Code

Meaning00

Unknown module or DFSMSCEC requestor01

DC Communication Manager (DFSICIO0)02

LU 6.2 Receive LU Manager (DFSRLM10)03

OTMA Receive LU Manager (DFSYTIB0)04

DC Call Handler (DFSDLA30)


05MSC Analyzer (DFSCMS00)

06/FORMAT command processor (DFSICLK0)

08IMS Termination (DFSTRM00)

10IMS Initialization (DFSIINB0)

yyThe reason for the error:Code

Meaning02

The exit requested two user prefixes.03

The exit requested two internal prefixes.Internal prefixes are reserved for IMS internaltools.

04The prefix buffer length was too large.

05A DFSPOOL error occurred on the get prefixbuffer.

06The exit return code was negative.

07The exit return code was too high.

08A DFSBCB error occurred while getting a BCBcontrol block.

09A bad SYSID was detected.

10A Message Queue Manager error occurredwhile inserting a prefix.

11A nonzero return code was received fromDFSICLR1.

12The message destination is an invalid type forthe AVM/ISC link.

13Change destination error. User exit requestedto change the destination name to a differenttransaction by setting MSLR2CHG, MSPR2CHG,or MSTR2CHG. The new destination name atMSLRDEST, MSPRDEST, or MSTRDEST is not atransaction destination.

14Change destination error. User exit requestedto change the destination name to a different

LTERM by setting MSLR2CHG, MSPR2CHG, orMSTR2CHG. The new destination name atMSLRDEST, MSPRDEST, or MSTRDEST is not anLTERM destination.

15The DFSMSCEC exit routing flag is in error.

16A DFSUSRX interface error occurred.

17Change destination error. User exit requestedto change the destination name by settingMSTR2CHG or MSLR2CHG or MSPR2CHG.The new destination name at MSTRDEST,MSLRDEST, OR MSPRDEST was not be found.

18The exit changed the destination name of theI/O PCB message.

19The exit requested rerouting for the I/O PCBmessage.

20The exit changed the destination name to acommand (for example, /CMDVERB).

21The user exit override of MSNAME was invalid.

22Local share queue registration failed forrerouting the transaction to the local sharedqueues.

23The exit routed the transaction to an invalid,remote destination.

24The exit rerouted the message to an invalidMSC system identification (for example,SYSID).

25The exit routed the message to an invalidMSNAME.

26The exit routed an intermediate messageto this local IMS, but the source SYSID isunknown to this local IMS.

27The exit indicated routing to a remote IMS butdid not set the destination SYSID or MSNAME.

28The exit requested rerouting to the sourcesystem but MSC was not system defined or thesource SYSID was not valid.

29The exit requested that direct route overridebut override was unsuccessful.


30The exit requested invalid rerouting for a front-end switch message to a remote IMS.

31The exit requested rerouting for a responsemessage.

33DFSMSCE0 initialization failed becauseDFSMSCSV is not supported.

34DFSMSCE0 initialization failed because theDFSMSCSV length is invalid.

35DFSMSCE0 initialization failed because thecharacter string VECTOR is not present.

36The user prefix segment (MSCEUPR) wasinvalid when the exit returned to IMS.

37The internal prefix segment (MSCEIPR) wasinvalid when the exit returned to IMS. Internalprefixes are reserved for IMS internal tools.

38The exit overlaid the 512–byte user work areabuffer.

39The exit overlaid the MSEB BCB block name.

40The exit overlaid the parameter list.

Codes 41 through 52 apply to the /FORMATcommand.41

The CNT for the terminal to be formatted wasnot found.

42The specified terminal is a remote LTERM.

43The specified terminal is a dynamic MSNAME(LNB).

44The destined terminal (which is different fromthe input terminal) is not MFS-formatted.

45The destined terminal is in line response mode.

46The destined terminal is in TERMINALresponse mode.

47Conversation is active on the destined terminal(when LTERM was specified in the command).

48The terminal is in input only mode.

49The terminal is in the exclusive mode (whenLTERM was specified in the command).

50The call to Queue Manager failed for a putlocate call.

51The inset prefix call to Queue Manager failed.

52The call to enqueue the message failed.

sss1/name1The source SYSID and source LTERM name for theinput system.


System actionThe /Format command or message routing request iscanceled.

If one of the exits attempted to reroute a message orIMS attempted to enqueue a message, a log recordtype X'67', subcode X'01' (ID=AER1, ID=MSCE, orboth) is written to the log. More than one record mightbe written to record the error. These records containthe IMS control blocks and save areas used by IMS orthe user exit when the error was encountered.

Operator response:(master terminal) Notify the system programmer.

System programmer responseOne of the following situations might have caused theerror:

• Operator error. For example, an incorrect transactioncode or LTERM name might have been entered.

• A user routing exit error occurred.• An IMS internal error occurred.

If the error is caused by the DFSMSCE0 user exit, seeTM and MSC Message Routing and Control User exitroutine (DFSMSCE0) (Exit Routines) and the prologueof the sample DFSMSCE0 exit for an explanation of therouting option.

For all other situations, see Data communicationservice aids (Diagnosis) for diagnostic informationabout message DFS070. Check the RSN, and followthe instructions for determining the cause. Print the6701 log records for additional information.

Module:


http://www.ibm.com/support/knowledgecenter/SSEPH2_15.1.0/com.ibm.ims15.doc.err/ims_dfsmsce0.htm#ims_dfsmsce0

http://www.ibm.com/support/knowledgecenter/SSEPH2_15.1.0/com.ibm.ims15.doc.err/ims_dfsmsce0.htm#ims_dfsmsce0

http://www.ibm.com/support/knowledgecenter/SSEPH2_15.1.0/com.ibm.ims15.doc.dgr/ims_dc_data_comm_service_aids.htm#ims_dc_data_comm_service_aids


DFSCMS00, DFSDLA30, DFSICLK0, DFSICIO0,DFSIINB0, DFSRLM10, DFSTRM00, DFSYTIB0

DFS071 SYSTEM DISCONNECT

ExplanationFive attempts to sign on were invalid.

System actionThis message notifies the switched terminal operatorthat IMS is disconnecting this line.

Operator response:(master terminal) Establish the correct sign-oncommand before trying to sign on again.

Module:DFSICA10, DFSICIO0

DFS072I UNABLE TO OUTPUT LINE xPTERM y

ExplanationA permanent I/O error was detected attempting towrite a message to the indicated IMS line and physicalterminal.

System actionThe terminal has been PSTOPPED.

Operator response:(master terminal) After the malfunction has beencorrected, a /START LINE x PTERM y or a /RSTARTLINE x PTERM y command can be used to resumeoperations on the terminal.

DFS074 QUEUE ERROR-MESSAGECANCELED RSN=xxyy

ExplanationAn attempt was made to acquire a queue buffer. AnISRT locate, ISRT move, or reposition call wasissued, but an error was detected with the call or thecall could not be processed.

In a shared-queues environment, this message canindicate a failure in the CQSPUT process during insertprocessing or a problem due to a CQS structure failureor CQS unavailability.

The reason code RSN=xxyy is optional and is notalways included. If the reason code is present, it canbe one of the following values:xx

IMS module that detected the error:

01/DIS CPLOG (DFSDCPL0)

02Communications analyzer (DFSICIO0)

03/DIS controller (DFSICLD0)

04/NRE, /ERE (DFSICL20)

05/CQQUERY STATISTICS (DFSICQ20)

06OTMA SYNC processor (DFSYTIB0)

yyReason for the error:01

The requested size is less than 1 byte; forexample, LLZZ + 1 byte or larger.

02A QMGR or CQS ISRT error occurred.

03A queue buffer reposition error occurred.

04User exit DFSQSPC0 or IQCQMRI0 erroroccurred. If IBM IMS Queue Control Facilityfor z/OS is being used, the requested messagewas canceled because the node and client areusing too many queue buffers.

System actionThe queue buffer is canceled. Type 6701-AER1 and67D0 records are logged for some errors.

For OTMA, message DFS1269E RC4011 is also issuedand a X'67D0' trace entry is written to the log.

System programmer responseThis error might occur for one of the following reasons:

• An IMS or CQS internal error occurred.• The message queue is filling up.• A problem with the shared queue was encountered.• A user queue space notification user exit

(DFSQSPC0) or a tool using the exit, such as theIMS Queue Control Facility exit tool (IQCQMRI0), hasrejected the queue buffer request.

The response depends on the reason code yy, asfollows:

01Size requested is less than 1 byte.

Response: This problem is an IMS internal error.Print the 6701 and 67D0 records if available.


02QMGR ISRT or CQS error

Response: QMGR returned a nonzero return code.If IMS is not using shared queues, This situationcould be a problem with the local queues. If youare using shared queues, this could be a CQS ora problem with the shared queues. Print the 6701and 67D0 records if available.

03Queue buffer reposition error

Response: This problem is an IMS internal error.Print the 6701 and 67D0 records if available.

04User exit DFSQSPC0 or IMS Queue Control Facilityexit IQCQMRI0 requested that the message becanceled because the node and client are usingtoo many queue buffers.

Response: The user exit DFSQSPC0 or IMS QueueControl Facility exit IQCQMRI0 set QSPCFLG2 =QSPCF2NO in the exit DFSPARM area, becauseit determined that the caller was using toomany queue buffers. The QMGR then set theQMGRO3NO flag in the DFSQMGR parameter areaof the caller and canceled the ISRT, releasing thequeue buffers. To determine the pool usage, printthe 6701 records if available. Then refer to theDFSQSPC0 exit, or IQCQMRI0 exit if you are usingthe IMS Queue Control Facility, and the queueusage from the /DIS POOL QBUF command formore information.

Module:DFSICIO0, DFSICLD0, DFSICL20, DFSYTIB0,DFSDGS96

DFS075I REQUESTED BLOCK NOTAVAILABLE: MID name

ExplanationThe Message Format Service (MFS) cannot fetch thecontrol blocks required to process an input message.The message identifies the MID name for the MIDand DIF pair requested. The MID or DIF contains aninvalid field, which is probably caused by modificationor damage to the Format or Test Format libraries.

System actionMFS ignores the input message.

Programmer responseStop using the transaction requiring this MID or DIF,or both, block long enough to allow the blocks to bereplaced by others from the Message Format Library.

Then retry the failing transaction. If the error persists,the blocks were damaged in the Format or Test Formatlibrary, an error was compiled into the blocks, or anerror exists in an MFS online module.

Module:DFSCFEI0

DFS076 MULTI-SEGMENT INPUT INVALID[I: sss1/name1, D: sss2/name2]

ExplanationA buffered terminal device attempted to send multiplesegments of an input transaction which was defined asa single segment transaction.



sss2/name2The destination SYSID and destination LTERM orTRAN code of the processing system


System actionThe message was canceled. If the input wasprocessed by the MFS Utility, the input message wasdefined with multiple segments.

Operator responseReenter the message properly.

If the optional part of the message is printed, notifythe system programmer that the blocks are notsynchronized.


Module:DFSCON00, DFSICIO0


DFS077 COMMAND INPUT EXCEEDSMAXIMUM LENGTH

ExplanationThe maximum length of a command is defined as thatwhich fits in a queue message buffer.



Operator response:(local/remote terminal) Reduce the length of thecommand and reenter. If commands of this length arerequired, the system can be redefined with increasedmessage buffer size.

Module:DFSICIO0

DFS078 COMMAND INVALID AS SECONDSEGMENT

ExplanationA multi-segment input message was in process whenthis command was entered.

System actionBoth the message and the command are canceled.

Operator response:(local/remote terminal) Reenter the message andcommand separately.

Module:DFSICIO0

DFS079 INPUT IGNORED-SYSTEM INSHUTDOWN

ExplanationA shutdown checkpoint is in process, and all inputfrom terminals is suspended.


Operator response:(local/remote terminal) Reenter the data after thesystem has been restarted.

Module:DFSICIO0

DFS080 MESSAGE CANCELED BY INPUTEDIT ROUTINE

ExplanationA user-supplied edit routine has rejected and canceledthe last input message.

System actionThe entered message is ignored.

Operator response:Reenter the message in a format acceptable to the editspecifications.

Module:DFSICIO0

DFS081 TRACE EXIT COMMANDUNSUCCESSFUL RSN=xxyy

ExplanationThe /TRACE EXIT command was entered incorrectly,the command is not supported on this IMS system, orthis problem is an IMS internal error. In the messagetext:xx

The IMS module that detected the error:01

Trace Command Processor (DFSICLN5)yy

The reason for the error:01

An invalid keyword was specified for the traceexit.

02An invalid parameter type was specified for thetrace exit command.

03No parameter type was specified for the traceexit command.

04Multiple parameter types were specified forthe trace exit command.

05The DFSMSCD control block is missing for thetrace exit (DFSMSCE0) command.

06An Invalid parameter subtype was specified forthe trace exit command.

07The trace exit is not supported for thisenvironment.

08The required exit was not loaded for the starttrace command.

09Required exit not loaded for start tracecommand.

10A system command failure occurred.

11The parameter length was invalid.


System actionThe entire command was ignored, or one or moreparameters were ignored.

Operator response:(master terminal) Check the syntax of the commandto ensure that it is correct. Reissue the commandwith the proper keyword and parameters. Issue the /DISPLAY TRACE EXIT command to determine whichparts of the command ran successfully and if the exit isinstalled. If the exit is not installed, the status of all theexit entry points is N/A on the display output. If theproblem persists, contact the system programmer.

System programmer responseOne of the following situations might have caused theerror:

• An operator error. For example, incorrect syntaxmight have been entered.

• A user routing exit (DFSMSCE0) initialization error.• An IMS internal error.

See "DC–Data Communication Service Aids" in IMSVersion 15 Diagnosis for diagnostic information aboutmessage DFS081. See the RSN and follow theinstructions for determining the cause. You mightneed to print the 6701 log records for additionalinformation.

Module:DFSICLN5

DFS082 ERROR READING QUEUE, QUEUESHUTDOWN [I: sss1/name1, D:sss2/name2] [name RC = nn]

ExplanationAn unrecoverable I/O error occurred attempting toread a record from a logical terminal queue.




This information appears only when the error isdetected in a remote system (sss2):

nnThe decimal value of the queue manager returncode. Possible queue manager return codes are:04

No segment returned for destination name.

08No more messages on the queue fordestination name.

12Destination name is in use.

36MSC prefix does not exist. The message hasbeen dequeued.

40ISC prefix does not exist. The message hasbeen dequeued.

System actionThat queue was stopped. A log record type X'6701',ID=MER1, was written using the IMS TRACE facility,which provides a snap of the IMS control blocks andsave areas.

Operator response:(master terminal) If the optional part of the messageis printed, coordinate restarting the resource with thedestination system master terminal operator and itssystem programmer.

System programmer responseIf the message has been dequeued, examine theMER1 record to determine which message wasdequeued.

Module:DFSCM7A0, DFSCM7B0, DFSICIO0

DFS084 CONVERSATION IN PROCESS

ExplanationA conversational program has not yet responded tothe last input message. Conversation is a two-wayexchange. If this message is paged, it must becompletely viewed and deleted by the operator beforethe response is complete.

System actionIMS discards the entered data. The applicationprogram responds to the last accepted input, unlessthe terminal is page protected.

Operator responseAwait reply from the program, and reenter data;or delete last page, and reenter data; or /EXIT toterminate the conversation, and reenter the data; or,if paging has been specified, you might have to pressthe PA2 key to delete the message.


Programmer responseScreen protection has been specified as either aterminal option or an MFS option. Determine whetherthis is necessary for this transaction.

Module:DFSCON00, DFSICLH0

DFS085I CONVERSATION CANNOT BECONTINUED: {NO PREVIOUSOUTPUT MESSAGE | STORAGEERROR | SPA NOT FOUND INOUTPUT MESSAGE | CQS ERROROR CQS NOT AVAILABLE | SPAHAD BAD DATA OR FORMAT}

ExplanationIMS attempted to retrieve the SPA for the inputmessage from the previous output message, but anerror occurred. The conversational transaction cannotbe continued at this time due to the error indicated:

• NO PREVIOUS OUTPUT MESSAGE

The previous conversational output message couldnot be located.

• STORAGE ERROR

An error occurred trying to acquire temporarystorage.

• SPA NOT FOUND IN OUTPUT MESSAGE

The SPA could not be found in the previousconversational output message.

• CQS ERROR OR CQS NOT AVAILABLE

Either the Common Queue Server (CQS) wasunavailable or a CQS error occurred.

• SPA HAD BAD DATA OR FORMAT

IMS attempted to convert the SPA from an internalpacked format to an unpacked format, but wasunsuccessful.

System actionThe input data is ignored.

Operator responseTake the appropriate action:

• NO PREVIOUS OUTPUT MESSAGE

IMS will probably never be able to continue thisconversation. Terminate the conversation with an /EXIT command. For OTMA users, the conversationwill be terminated by IMS.

• STORAGE ERROR

Reenter the input data after waiting a for some timefor the storage shortage to be eliminated.

• SPA NOT FOUND IN OUTPUT MESSAGE

IMS will probably never be able to continue thisconversation. Terminate the conversation with an /EXIT command. For OTMA users, the conversationwill be terminated by IMS.

• CQS ERROR OR CQS NOT AVAILABLE

Reenter the input data after waiting a some time forCQS to become available. If the problem is causedby a CQS error, you might have to terminate theconversation with an /EXIT command. For OTMAusers, the conversation will be terminated by IMS.

• SPA HAD BAD DATA OR FORMAT

IMS will not be able to continue this conversation.Terminate the conversation with an /EXITcommand.

Module:DFSCON00, DFSYTIB0

DFS086 CONVERSATION RESOURCESUNAVAILABLE

ExplanationThe maximum number of concurrent conversationsallowed (65,535) was exceeded.

System actionThe conversation is not started.

Operator response:(local/remote terminal) Wait for someone to finishand try again. If this response occurs frequently, notifythe systems operation personnel.


Module:DFSCON00


DFS087 USER PTERM INPUT EDIT ERROR-INPUT IGNORED

ExplanationThe user physical terminal input edit exit routineattempted to insert a transaction code or passwordand:


• MFS bypass was not active.• The total size of the attempted insert was less than 6

or greater than 22.

System actionA log record type X'67', subrecord X'01', has beenwritten using the IMS TRACE facility, which providesa snap of the IMS control blocks and save areas. Thedata entered is ignored.

Operator response:Notify the system programmer.

System programmer responseCorrect the error in the user physical terminal inputedit exit routine.

Module:DFSICIO0

DFS0088I LS0 INITIALIZATION FAILED -identifier

ExplanationInitialization for the Local Storage Option failed forthe reason indicated by identifier. The module orcontrol block identified in message DFS0088I wasbeing processed when the error occurred.Identifier

Reason1. DFSKLSM

IMODULE GETMAIN failed.2. DFSKLSM0 or DFSKLSD0

IMODULE LOAD failed for one of these modules.3. DFSXMCTL

Not initialized for LS0.4. SAP

Insufficient SAPs were assigned for LS0.

System actionThis message is followed by abend 0088.

System programmer responseReason

Action1.

Increase the IMS control region size.2.

Correct the JOB/STEPLIB DD statement or bind theLS0 modules into the correct library.

3.Determine the DFSXMCTL problem by referencingmodule DFSMINIO. Contact IBM for assistance.

4.Determine the SAP problem by referencing moduleDFSXLIC0. Contact IBM for assistance.

Problem determination:1, 2, 3, 4, 8, 12

Module:DFSKLSI0


DFS0089 OUTPUT EXCEEDS BUFFER SIZELTERM xxxxxxxx LINE yyy PTERMzzz OUTPUT EXCEEDS BUFFERSIZE LTERM xxxxxxxx NODEyyyyyyyy

ExplanationAn application program using the MFS bypassattempted to send an output message that is longerthan the length specified in the OUTBUF parameterof the TERMINAL macro during system definition. Inaddition, the access method in use is either VTAMnon-SNA or another IMS-supported terminal withOPTIONS=NOXPAR. The OUTBUF value should be setequal to the maximum RU size acceptable to theterminal (and VTAM and its NCP) because IMS doesnot send an output message inserted by an applicationthat exceeds this value.

System actionA log record type X'67' subrecord X'01' has beenwritten using the IMS trace facility, which providesa snap of the IMS control blocks and save areas. Ifthe last message segment moved into the line buffer(=OUTBUF) by DD6 fitted exactly, the contents ofthis line buffer was already sent to the terminal. Theterminal is made inoperable, and message DFS998I issent to the master terminal operator.

Operator response:(master terminal): Upon receipt of message DFS998I,the LTERM should be reassigned or the messagedequeued. The terminal can then be restarted. Notifythe system programmer.

System programmer responseTake one of the following actions:


• Increase OUTBUF value in TERMINAL macro forsystem definition.

• Restrict the application program not to sendmessages greater in length than OUTBUF value.

Module:DFSCD600, DFSCD610, DFSCD620

Related information“DFS998I” on page 359LINE xxx PTERM yyy IS INOPERABLE

DFS0090 USE OF MODNAME DFS.EDTNREQUIRES TERMINAL INPUT EDITROUTINE

ExplanationWhen MFS BYPASS option is selected and theMODNAME DFS.EDTN is used, the user must providea Physical Terminal Input edit routine.



System programmer responseInclude a user Physical Terminal Input edit routine insystem definition. See the topic on "Physical Terminal(Input) edit routine" in IMS Version 15 Exit Routines.

ModuleDFSICIO0

Related referencePhysical Terminal (Input) edit routine(DFSPIXT0) (Exit Routines)

DFS091I UNABLE TO LOCATE X'42' LOGRECORD

ExplanationBatch backout was being initialized but no X'42' logrecord was found on the input log volume.

System actionBatch backout is terminated.

Programmer responseThis error can occur if only one input volume wassupplied to database backout and the X'42' log recordhad not yet been written on that volume. Rerun the

database backout specifying the last two volumes asinput. If more than one volume was already suppliedor if only one volume was created, then a system errorhas occurred.


Module:DFSBCKI0


DFS092I IMS LOG TERMINATED

ExplanationThis informational message indicates that the IMSsystem log has been terminated.

System actionIMS has terminated.

Module:DFSFDLS0

DFS093 COMMAND NOT AUTHORIZED ASENTERED WITH CRC FROM MCSOR E-MCS CONSOLE

ExplanationThe command is not allowed from the MCS console.The command authorization, which was specifiedon the CMDMCS execution parameter (RACF (orequivalent), DFSCCMD0, or both) did not authorize theuser ID of the console to issue the command.


Operator response:(master terminal) Reenter the command froman authorized console, or update authorizationinformation to allow the command from the console.

Module:DFSICLP0

DFS094I THE COMMAND WAS UNABLE TOACQUIRE A LATCH

ExplanationThe command tried to get a latch and failed. Forexample, the command tried to get the DRSC latch in


http://www.ibm.com/support/knowledgecenter/SSEPH2_15.1.0/com.ibm.ims15.doc.err/ims_dfspixt0.htm#ims_dfspixt0

http://www.ibm.com/support/knowledgecenter/SSEPH2_15.1.0/com.ibm.ims15.doc.err/ims_dfspixt0.htm#ims_dfspixt0

order to update or access MSC resources, but it failed.This is probably due to an internal error.


User responseCapture an IMS dump and contact IBM softwareSupport for assistance.

Module:DFSCML70, DFSICLG0, DFSICLN0, DFSICL60,DFSIC460

Related conceptsCollecting IMS diagnostic information(Diagnosis)

DFS0095I VSO1THLD n | VSO2THLD n |VSO3THLD n

ExplanationDuring IMS initialization, this message is issued wheren is used to display the value of the VSO1THLD,VSO2THLD, or VSO3THLD parameter as specified inthe DFSDFxxx member of the IMS PROCLIB data setunder the <SECTION=FASTPATH> section.

VSO1THLD=Specifies the castout threshold time in seconds fora VSO area with less than or equal to 800 controlintervals (CIs). The valid range is 1 - 300. Thedefault value is 300.

VSO2THLD=Specifies the castout threshold time in seconds fora VSO area with 801 - 3500 CIs. The valid range is1 - 300. The default value is 240.

VSO3THLD=Specifies the castout threshold time in seconds fora VSO area with greater than 3500 CIs. The validrange is 1 - 300. The default value is 180.


Programmer responseNo action is required.

ModuleDBFFATC1

DFS0096W DATA BASE BUFFERS PURGED,UPDATE INTENT, NOLOGSELECTED.

ExplanationA batch IMS job ran without an IMS log data set andabended while using a PSB with UPDATE INTENT. Thedatabase buffers were purged, but the database mightstill be bad.

System actionIMS (E)STAE continues processing an abend.

Programmer responseDetermine if the database still has its integrity byinterrogating the type of abend and the abendingprogram.

ModuleDFSFLST0

DFS097 LTERM/S LOCKED/STOPPED

ExplanationThe LTERM specified was locked or stopped.


Operator response:(local/remote terminal) Either start or unlock theLTERM, or sign on for another terminal.

Module:DFSICA10

DFS098 PTERM LOCKED/STOPPED

ExplanationThe physical terminal was locked, stopped, orinoperable.

Operator response:(local/remote terminal) Have the master terminaloperator start or unlock the PTERM.

Module:DFSICA10

DFS099 MULTIPLE LINE PARAMETERS AREINVALID


http://www.ibm.com/support/knowledgecenter/SSEPH2_15.1.0/com.ibm.ims15.doc.dgr/ims_diagdocs.htm#ims_diagdocs

http://www.ibm.com/support/knowledgecenter/SSEPH2_15.1.0/com.ibm.ims15.doc.dgr/ims_diagdocs.htm#ims_diagdocs

ExplanationA command that refers to one or more physicalterminals can only specify one line. For example:

• PTERM ALL can only be specified for a single line.• PTERM ALL cannot be specified when displaying

lines by attribute.


Operator response:(local/remote terminal) Reenter the commandproperly.

Module:DFSICL10, DFSICL30, DFSIC440

DFS100 LINE KEYWORD NOT PRESENT

ExplanationIf PTERM keyword is present, the LINE keyword is alsorequired.



ModuleDFSICL10


Chapter 6. DFS messages, DFS101 - DFS150


DFS101 MULTIPLE RESTART COMMANDSARE INVALID

ExplanationAfter the system is started through an /NRESTARTor /ERESTART command, this command cannot beentered again.


Operator response:(local/remote terminal) If you want to restartdifferently, shut down the system, and bring it upagain.

ModuleDFSICL30

DFS102 PTERM KEYWORD NOT PRESENT

ExplanationThe keyword PTERM must be used with the keywordLINE.



Module:DFSICL10, DFSICL80

DFS103 DATABASE/AREA KEYWORD NOTPRESENT

ExplanationDBDUMP requires the keyword DATABASE followedby the requested database names. /DBRECOVERYrequires the keyword DATABASE followed by therequested database names or the keyword AREAfollowed by the requested area names.


Operator response:(master terminal) Reenter the command properly.

ModuleDFSICL20

DFS104 NO TEXT SUPPLIED, CANNOTBROADCAST

ExplanationOn /BROADCAST command, you must enter the data tobe broadcast as the second segment of the message.None was supplied.


Operator response:Reenter the command properly.

Module:DFSICL30

DFS105I COMMAND VERB xxxxxxxxxxx ISINCORRECT

ExplanationThe command verb xxxxxxxxxxxx is incorrect. The firstthree characters of the command verb are correct,but the command is incorrect thereafter. Up to 11characters of the incorrect command verb are includedin the error message.


Operator responseReenter with just the first three characters or thecorrect full spelling of the command verb.

Module:DFSICL30

DFS106 TRAN KEYWORD NOT PRESENT


ExplanationTRAN is the only keyword allowed with the TERMINALkeyword.



Module:DFSICL80

DFS107 REQUIRED KEYWORD NOTPRESENT

ExplanationNone of the acceptable keywords for this commandwere present.


Operator responseMake sure that the keyword is valid for the system youare running (IMS DB/DC, DBCTL, or DCCTL). Select avalid keyword; then reenter the command.

ModuleDFSCML70, DFSICA10, DFSICLE0, DFSICLG0,DFSICLH0, DFSICLJ0, DFSICLN0, DFSICLQ0,DFSICLU0, DFSICL10, DFSICL20, DFSICL40,DFSICL60, DFSICL70, DFSICL80, DFSICL90,DFSICM00, DFSIDPK0, DFSIDP00

DFS108 COMMAND SYNTAX INVALID

ExplanationThe command entered did not conform to establishedsyntax rules.


Operator responseCheck for syntax errors, including spelling andincorrect delimiters, then reenter the commandcorrectly.

Module:DFSICL30, DFSICLN2, DFSICLN3, DFSICLN4

DFS110I COMMAND KEYWORDyyyyyyyyyyyy INVALID FORimstype

ExplanationKeyword yyyyyyyyyyyy is not supported withcommands for this imstype of IMS. Up to 12 charactersof the invalid keyword are included in the errormessage. The imstype is one of the following:

ACTIVEDBCTLDCCTLXRF ALTERNATENON-DBCTLNON-DCCTL

Keywords that are not supported on an activesubsystem include BACKUP, which is only supportedon an XRF alternate.

Keywords that are not supported in DBCTL relate toDC.

Keywords that are not supported in DCCTL relate toDB.

Keywords that are not supported on an XRF alternatesystem include most keywords, except those requiredwith commands that operate the XRF alternate.

Keywords that are not supported in NON-DBCTL relateto DBCTL.

Keywords that are not supported in NON-DCCTL relateto DCCTL.


Operator responseCheck the keywords and run the command again.

Module:DFSICL30, DFSDGSA1, DFSDGSB0, DFSDGSD0,DFSDGSL0, DFSDGSL1, DFSDGSL2, DFSDGSN0,DFSDGSR0, DFSDGST0, DFSDGSU0

DFS111 TIMEOUT-RESEND MESSAGE

ExplanationBetween characters of a message, 28 seconds isallowed before the hardware times out and cancels themessage.

System actionThe message is canceled.


Operator response:(Local/remote terminal) Reenter the message withoutexcessive delay.

ModuleDFSDN020, DFSDS010, DFSDS020, DFSDS040,DFSICL30

DFS112 BLDQ KEYWORD NOT PRESENT

ExplanationBLDQ keyword must be present for the /ERESTARTcommand with checkpoint 0 or if the FORMAT keywordis supplied with the /ERESTART command.


Master terminal operator response: Reenter thecommand properly.

ModuleDFSICL20

DFS113 LINE KEYWORD PARAMETER NOTPRESENT

ExplanationThe LINE keyword was present, but was not followedby any parameters.


Operator response:(local/remote terminal) Reenter with properspecifications.

ModuleDFSICLJ0, DFSICLN0, DFSICL10, DFSICL50,DFSICL80, DFSIC440, DFSIDP60, DFSIDP70,DFSIDP80

DFS114 LTERM KEYWORD PARAMETERNOT PRESENT

ExplanationThe LTERM keyword was not followed by anyparameters.


Operator response:Check the syntax of the command and reenter it.

ModuleDFSICA10, DFSICLJ0, DFSICL80, DFSICL90,DFSICV10, DFSIC440, DFSIDP40, DFSIDP70

DFS115 PTERM KEYWORD PARAMETERNOT PRESENT

ExplanationThe PTERM keyword was not followed by anyparameter.


Local/remote terminal operator response:

Reenter the command properly.

ModuleDFSICLJ0, DFSICLN0, DFSICL10, DFSICL50,DFSICL80, DFSIC440, DFSIDP60, DFSIDP70,DFSIDP80

DFS116 DATABASE|AREA KEYWORDPARAMETER NOT PRESENT

ExplanationThe database or area keyword was not followed by aparameter.


Operator responseReenter the correct command.

ModuleDBFCDAR0, DFSICL20, DFSICL80, DFSICL90,DFSIC430, DFSIDPJ0, DFSIDP50

DFS117 PROGRAM KEYWORD PARAMETERNOT PRESENT

Chapter 6. DFS messages, DFS101 - DFS150 63

ExplanationThe PROGRAM keyword was not followed by aparameter specifying which program.


Local/remote terminal operator response: Reenterthe command properly.

ModuleDFSICL80, DFSICL90, DFSIC430, DFSIDP50

DFS118 COMMAND IS INVALID FORNONSWITCHED TERMINAL

ExplanationThe /IAM command is invalid.

System actionThe command was ignored.

Module:DFSICLA0

DFS119 LTERM IN USE, CANNOT PROCESSCOMMAND

ExplanationAn LTERM is either having a message dequeued andsent or is marked for use by another task. The LTERMcannot be reassigned until either the message isdequeued and sent, or the other task has finishedusing it.

If TCO is active, this message might see the TCOlogical terminal DFSTCFI.

If STM is active (STM=Y), this message can indicatethat the LTERM is being updated in the RM resourcestructure by another task. You cannot reassign theterminal until IMS is able to obtain the LTERMinformation from the RM resource structure. In thiscase a DFS4447 message is also issued.

System actionThe command is rejected. If the command was /ASSIGN LTERM PRIMARY, the primary masterterminal assignment might have succeeded.

Operator response:Reenter the command. If the command continues tobe rejected with this error message, notify systemprogrammer immediately.

System programmer responseEnter the /CLS NODE XXX command for the node ofthe LTERM being assigned; then enter the /ASSIGNcommand again.

Verify that the command completes successfully; if itstill fails, create an SVC memory dump and contactIBM Software Support.

Module:DFSICL70

DFS120 MESSAGE CANCELED, TEXTSEGMENT DID NOT END IN EOB

ExplanationThe presence of an end of block (EOB) enables IMSerror checking for the data entered. IMS does notaccept a message without EOB. All data must end withan EOB.


Operator response:(local/remote terminal) Enter EOB by itself to endmulti-segment transaction.

DFS121I PARAMETER TOO LONG

ExplanationParameters are restricted to 8 bytes or less.


Operator response:Reenter the command with a valid length parameter.

Module:DBFICL20, DFSICA10, DFSICL30, DFSICL60,DFSICLN3, DFSICLN4

DFS122 SPECIFIC PARAMETER MIXEDWITH ALL PARAMETER

ExplanationIf the ALL parameter is specified, no other parametercan be included for the same keyword.



Operator responseRemove any parameters you specified with theALL parameter. If you specified the ALL parametercorrectly, check for one of the following:

• A misspelled or an invalid keyword• A keyword that is not valid for the system you are

running (IMS DB/DC or DBCTL).

Correct the keyword and reenter the command.

ModuleDFSICL30, DFSICV10

DFS0123E DBD CHANGE UNSUPPORTEDBY VERSIONING: DB=dedbnameRSN=rc SEG segmname variabletext

or

DBD CHANGE UNSUPPORTED BY VERSIONING:DB=dedbname RSN=rc SEG segmname FLDfld_name variable_text

ExplanationAn application program attempted to access a versionof a Fast Path data entry database (DEDB) otherthan the current version, but IMS cannot build theinternal blocks that are required to access non-currentversions of the database, because the current versionof the database contains a change in the databasedefinition (DBD) that is not supported by databaseversioning.


In the message text:dedbname

The name of the DEDB that contains the changesthat are unsupported by database versioning.

fld_nameThe name of the field that is associated with theunsupported change.

rcThe reason code that identifies the DBD changethat is not supported by database versioning.Look up the return code in the following tablefor additional information about the unsupportedchange.

segmnameThe name of the segment that is associated withthe unsupported change.

variable_textA short description of the change that is notsupported by database versioning. Look up thereturn code in the following table for additionalinformation about the unsupported change.

Table 1. Return code and variable text meanings for DFS0123E

RC

Variable text Meaning

01

SEG segmname EXPECTED,FOUND SEG segmnameINSTEAD

The order of the segments in thecurrent version of the databasedid not match the order in therequested version of the database.

A segment order mismatch canhappen if any of the followingchanges were made to the currentversion of the database:

• The expected segment wasdeleted

• A segment was inserted beforethe expected segment

• The order of the segments waschanged

IMS might also issue this messageif the expected segment wasskipped due to a previous error inthe validation process.

IMS issues this message for eachsegment it finds that is not theexpected segment.

02

SEG segmname NEW After validating all of the segmentsin the requested version of thedatabase, the current version ofthe database contains an additionalsegment.

03

SEG segmname NOTFOUND

A segment in the requested versionof the database was not foundin the current version. A segmentmight not be found for any of thefollowing reasons:

• The segment was renamed• A segment was deleted• A segment was skipped while

searching for another segment

04

SEG segmnameINSERTION RULECHANGED

The rule that specifies how datais inserted in this segment waschanged.

05

SEG segmnameCOMPRESSION EXITCHANGED

The compression exit routine for asegment was changed.

06

SEG segmname TYPECHANGED

The type of the segment(Direct Dependent or SequentialDependent) was changed.

07

SEG segmname SUBSETPOINTER(S) CHANGED

The subset pointers were changed.


Table 1. Return code and variable text meanings for DFS0123E(continued)

RC


08

SEG segmname MINIMUMLENGTH CHANGED

The minimum length of thesegment was increased ordecreased. This message is alsoissued when a segment is changedfrom variable length to fixed lengthor vice versa.

09

SEG segmname MAXIMUMLENGTH DECREASED

The length of segment wasdecreased.

10

SEG segmname DATACAPTURE EXIT CHANGED

One or more of the data captureexit routines was changed.

11

FLD fld_name NOT FOUND A field in the old segment wasnot found in the current version ofthe segment. Either the field wasdeleted or a previous error causedit to be skipped.

12

FLD fld_name EXPECTED,FOUND FLD fld_nameINSTEAD

While looking for a match to afield in the old segment version,a different field was encounteredinstead. This message is issuedfor each field that is encounteredthat is not the expected field. Ifthe expected field was skipped dueto a previous error, a message isissued for each of the remainingfields in the segment.

13

FLD fld_name OFFSETCHANGED

The offset of a field in therequested database was changedin the current version of thedatabase.

14

FLD fld_name LENGTHCHANGED

The length of a field in therequested database was changedin the current version of thedatabase.

15

FLD fld_name TYPECHANGED

The type of padding was changedin the field.

16

FLD fld_nameSEQUENCING CHANGED

The field was changed fromsequenced to unsequenced or viceversa.

17

FLD fld_name OVERLAPSFLD fld_name

The field definitions in thecurrent version of the databaseare incompatible with the fielddefinitions of the requesteddatabase, because the offsets andlengths of two or more new fields inthe current version of the databaseoverlap each other.

18

SEG segmname MAXLENGTH OF VAR LENGTHSEG INCREASED

A variable length segment hasincreased in length.

19

SEG segmnameSECONDARY INDEXRELATIONSHIP CHANGED

A segment changed from beinginvolved in a secondary index tono longer being involved in asecondary index.

20

SEG segmnameREFERENCED BYSECONDARY INDEX,CHANGED

A segments involved in a secondaryindex has increased in length oradded new fields.

Table 1. Return code and variable text meanings for DFS0123E(continued)

RC


21

SEG segmname SDEPCHANGED

An SDEP has increased in length oradded new fields.

System actionIMS cannot build the internal blocks that are requiredto provide access to prior versions of the database.Only the most recent version of the database can beaccessed.

IMS continues checking for other unsupportedchanges.

Programmer responseDetermine whether you need to keep the changes inthe database or remove them.

If you keep the changes in the database, existingapplication programs cannot access the database untilthey are modified to use the new database structure.The prior versions of the database cannot be accessedanymore.

If you need to remove the unsupported changes fromthe database, you need to recover the database to theprior version. Any updates to the database that weremade by application programs that used the currentversion of the database will be lost.

The version numbers for the current version of thedatabase and the version of the database that theapplication program was attempting to access areidentified in message DFS0006E. Message DFS0006Eis issued to the console after the last or onlyDFS0123E message.

Module:DBFVER10

Related conceptsDatabase versioning (Database Administration)Related information“DFS0006E” on page 20REQUESTED VERSION req_v_nmbr ANDCURRENT VERSION cur_v_nmbr OF DEDBdedbname ARE INCOMPATIBLE

DFS124 CANNOT ENQUEUE LTERM ONLINE

ExplanationThe queue module was not able to enqueue the logicalterminal on the new line.

Operator response:


http://www.ibm.com/support/knowledgecenter/SSEPH2_15.1.0/com.ibm.ims15.doc.dag/ims_db_versioning.htm#ims_database_versioning

(master terminal) This denotes a system error, andthe system should be shut down and dumped at theearliest possible time for analysis of the problem.Notify your IMS system programmer.

Module:DFSICL70

DFS0126I IMS CONNECTION WITHAPPC/MVS HAS BEEN STOPPED

ExplanationA /STOP APPC command was entered. The IMS APPCconnection to MVS™ stops successfully. The systemissues this message after the connection betweenAPPC/MVS and IMS was stopped successfully. IMSstops scheduling transactions from LU 6.2 devices.

System actionIMS continues processing without the APPC/MVS LU6.2 services. These services are unavailable until youenter a /STA APPC command.



Module:DFS6ECT0

DFS127 TOO MANY KEYWORDS

ExplanationToo many keywords were supplied.


Local/remote terminal operator response: Recheckthe format of the command, and delete theunnecessary keywords.

ModuleDFSCML70, DFSICA10, DFSICLE0, DFSICLG0,DFSICLJ0, DFSICLQ0, DFSICLU0, DFSICL10,DFSICL20, DFSICL60, DFSICL70, DFSICL80,DFSICL90, DFSICM00, DFSIC430, DFSIDP00,DFSIDP30

DFS128 TOO FEW KEYWORDS

ExplanationToo few keywords were supplied for this command.


Local/remote terminal operator response: Check thecommand format, and reenter it correctly.

ModuleDFSICLJ0, DFSICLQ0, DFSICL80

DFS129 INPUT ERROR, ONLY KEYBOARDBEING READ

ExplanationAn input error was detected while reading from acomponent. The keyboard is the only device fromwhich input will be accepted until the componentis restarted by entering a /RDR statement from thekeyboard.


Operator response:(local/remote terminal) Correct the problem, andenter the /RDR statement.

ModuleDFSDN020

DFS130 INVALID KEYWORDCOMBINATION

ExplanationOne or more of the keywords entered wereincompatible with another specified.

System action:The command is ignored.

Operator response:Check the keyword combination, and reenter thecommand.

Module:DFSICLJ0, DFSICLN0, DFSICL20, DFSICL30,DFSICL40, DFSICL60, DFSICL80, DFSIC430,DFSIC470, DFSIDP00, DFSICLN1, DFSICLN2,DFSICLN3, DFSICLN4

DFS131 PTERM IN/OUT NOT THE SAME


ExplanationThe master terminal logical terminal must have itsoutput physical terminal also assigned as its inputphysical terminal.


Operator response:Reassign the terminal properly.

Module:DFSICL70

DFS132 ALL DATABASE|AREAPARAMETERS ARE INVALID

ExplanationThis message is issued for one of the followingreasons:

• The database or area names entered are invalid.• A parameter is valid, but has failed processing (for

example, an allocation error has occurred on thedatabase).

• A valid parameter was specified, but the particulartype of IMS you are running does not support thatparameter.

• If you receive this message during a /START DBpartname, where partname is a HALDB partition thatwas added, and a partition structure rebuild has notbeen performed, then issue a /START DB haldbmstOPEN, where haldbmst is the master of the partition.Then issue a /START DB partname or a call for a keyin the key range of the new or redefined partition.This response performs a partition structure rebuildand enables the partition for use.


Operator responseReenter the correct database or area names that havebeen defined to IMS. If the parameter is valid, corrector investigate other error messages and reenter thecommand. Make sure any command keywords orparameters are valid for the flavor of IMS you arerunning.

Module:DBFCDAR0, DFSDBDR0, DFSICL20, DFSIC430,DFSIDPJ0, DFSIDP50

DFS133 BLDQ MUST NOT BE PRESENT

ExplanationThe BLDQ keyword is not permitted with a cold start.


Operator response:(master terminal) Reenter the command properly.

ModuleDFSICL20

DFS134 SHUTDOWN CHECKPOINT NOT INPROGRESS, CANNOT PROCESSCOMMAND

ExplanationOne of the following problems occurred:

• A /DISPLAY SHUTDOWN status command wasentered before a checkpoint command was issued.

• An /IDLE command (without the NOSHUT keyword)was entered before a checkpoint command wasissued.

• An /IDLE NODE command was entered before a /STOP DC or a /CHE command was issued.


Operator response:(master terminal) For /IDLE NODE, reenter thecommand after you issue the /STOP DC or /CHEcommand. For other commands, reenter the commandafter the checkpoint is in progress.

Module:DFSICLG0, DFSIDP90

DFS135 INVALID COMMAND ATTRIBUTECOMBINATION

ExplanationOne or more command attributes specified wereinvalid when used with another specified.


Operator responseReenter the command with the proper attributecombination.


Module:DFSIDP50

DFS136I COMMAND xxxxxxxxxx INVALIDFOR imstype

ExplanationThe command xxxxxxxxxx is not supported for thistype of IMS, imstype. Up to 10 characters of thecommand verb are included in the error message. Theimstype is one of the following:

• DBCTL - Commands that are not supported in DBCTLrelate to DC

• DCCTL - Commands that are not supported in DCCTLrelate to DB

• XRF ALTERNATE - Commands that are not supportedon an XRF alternate system are those not required tooperate the XRF alternate


Operator responseVerify the commands that are valid for the flavor ofIMS you are running and run the command again.

Module:DFSICL30

DFS137 CANNOT PROCESS UPDATETRANSACTION FROM INQUIRYTERMINAL

ExplanationSwitched terminals signed on for inquiry. Logicalterminal names cannot enter a transaction code thatwas defined as updating a database.

System actionThe message is ignored.

Operator response:(local/remote terminal) For this transaction, sign onfor a subpool or subpool CNT again.

Module:DFSICIO0

DFS138 LINE NOT STARTED, CANNOTPROCESS COMMAND

ExplanationTo assign the master terminal to a new line or node,that line must be in a started and operable state.

Operator response:Start the line, or node, and reenter the command.

Module:DFSICL70

DFS139 PTERM OR COMPONENT IS NOTOPERABLE

ExplanationIn order to assign the Master Terminal to a physicalterminal or node, the physical terminal must bestarted and operable, or the node must be in session.

Operator response(master terminal) Ensure that the physical terminaland lines are started and operational. If not, issuea /RSTART LINE x or /RSTART LINE x or /RSTART LINE x PTERM y command. If theterminal or its components are inoperable, reenterthe command when they become operable. If theline and terminal are operational, ensure that thelogical terminal being reassigned is assigned to acomponent which is attached and operable. Whenreassigning from a terminal with components to aterminal without components, use either the ICOMPTor COMPT keyword with value=1.

VTAM: Ensure that the node referenced is in session.Then reenter the assign command.

ModuleDFSICL70

DFS140I CHECKPOINT IN PROGRESS,CANNOT PROCESS COMMAND

ExplanationYou entered a command. However, a checkpoint froma previously entered command or an automatic systemcheckpoint was in progress.


Operator response:Wait for checkpoint ID to be displayed and reenter thecommand.

Module:DBFARDA0, DFSICL20, DFSICL40, DFSICLQ0

DFS141 ERESTART IN PROGRESS,CANNOT PROCESS COMMAND


ExplanationAn /ERESTART command is currently beingprocessed.


Operator response:Wait for this command to run completely beforeattempting to run other commands.

Module:DFSICL20, DFSICL30

DFS142 NRESTART IN PROGRESS,CANNOT PROCESS COMMAND

ExplanationYou entered a command, but an /NRESTARTcommand was being processed.


Operator response:(local/remote terminal) Wait for this command tocomplete before attempting to enter anything into thesystem.

Module:DFSDNSC0, DFSICL20, DFSICL30

DFS143 PTERM/LTERM IN USE, CANNOTPROCESS COMMAND

ExplanationThe named terminal is being used by another terminal.


Operator response:Sign on for another terminal, or try again later.

Module:DFSICA10, DFSICL50

DFS145I DATABASE IS EMPTY AFTERRELOAD COMPLETED

ExplanationHD Reload utility encountered a logical end of filewhile reading the DFSUINPT data set. However, norecords were found to insert into the database beingreloaded.

System actionProcessing terminates with a return code of 4.

Programmer responseVerify that the appropriate data set was supplied tothe HD Reload utility. The data set was produced bya previous execution of the HD Unload utility for thespecified database.


ModuleDFSURGL0


DFS146 TRAN KEYWORD PARAMETER NOTPRESENT

ExplanationThe transaction keyword has no parameter specifyingwhich transaction.



ModuleDFSICL80, DFSICL90, DFSIC430, DFSIDP40

DFS147 REQUIRED KEYWORDPARAMETER NOT PRESENT

ExplanationOne or more keywords specified in this command werewithout parameters.




Module:DFSCML70, DFSICLG0, DFSICLN0, DFSICLQ0,DFSICL10, DFSICL70, DFSICM00, DFSICV10,DFSIC460, DFSIDPC0, DFSIDPD0, DFSIDP30,DFSIDP40

DFS148 FORMAT KEYWORD PARAMETERNOT PRESENT

ExplanationThe FORMAT keyword was entered, but the parameterspecifying which data set to format was omitted.



Module:

DFSICL20

DFS150 LINE KEYWORD PARAMETER ISINVALID

ExplanationThe line number specified was found to be invalid. Itwas either non-numeric, less than 1, or greater thanthe maximum specified at system definition.



Module:DFSICLJ0, DFSICLN0, DFSICL30, DFSICL50,DFSICL70, DFSICL80, DFSIC440, DFSIDP60,DFSIDP70, DFSIDP80


Chapter 7. DFS messages, DFS151-DFS200


DFS151 LTERM KEYWORD PARAMETER ISINVALID

ExplanationThe logical terminal name specified was not defined tothe system.

If this IMS system is part of a sysplex using the IMSResource Manager, the logical terminal (LTERM) namemight be actively on or owned by another IMS system.As a result, the LTERM name would not be found onthis IMS, even if it was statically defined to the system.


Operator response:Correct the LTERM parameter and reenter thecommand.

Module:DFSICA10, DFSICLE0, DFSICLJ0, DFSICL70,DFSICV10

DFS152 PTERM KEYWORD PARAMETER ISINVALID

ExplanationThe physical terminal specified is not numeric, or theline has no terminal specified by that relative number.


Operator response:Check the system as defined and reenter thecommand properly.

Module:DFSICLJ0, DFSICL30, DFSICL50, DFSICL70,DFSIDP80

DFS153 DATABASE KEYWORDPARAMETER IS INVALID

ExplanationThe database specified was not able to be found as adefined database for this system.


Operator response:(local/remote terminal) Correct the parameter andreenter the command.

DFS154I COMMAND xxxxxxxxxx INVALID;REQUIRES COMPONENTcomponent

ExplanationThe command xxxxxxxxxx was invalid without thecomponent component. Up to 10 characters of thecommand verb are included in the error message.component can be one of the following components:

CQSFAST PATHMSCVTAM


Operator responseStart IMS with the specified component and reenterthe command.

Module:DFSICL30, DFSDGSA1, DFSDGSR0

DFS155 CHECKPOINT KEYWORDPARAMETER IS INVALID

ExplanationA nonzero checkpoint ID was specified for theCHECKPOINT parameter in the restart command.Since IMS determines the correct checkpoint to usefor restart, the only CHECKPOINT parameter acceptedas an override is zero.



Operator responseIf you are starting IMS for the first time (no previousshutdown), or if you want to restart using thecheckpoint taken during IMS cold start, take one ofthe following actions:

• Reissue the restart command specifyingCHECKPOINT 0.

• Omit the CHECKPOINT keyword and reissue therestart command.

Module:DFSICL20

DFS156 TRAN KEYWORD PARAMETER ISINVALID

ExplanationThe TRAN keyword parameter was invalid for one ofthe following reasons:

• The name specified for the transaction keyword wasnot a valid transaction code.

• The command does not permit a parameter after thetransaction keyword, but a parameter was entered.



Module:DFSICLE0, DFSIC430, DFSIDP30

DFS157 PRIORITY KEYWORD PARAMETERIS INVALID

ExplanationThe priority of a transaction must be 0 through 14; allother parameters are invalid. For BMP transactions,the normal and limit priorities cannot be changedusing the /ASSIGN command.


Operator response:Correct the command and reenter it.

Module:DFSICL70

DFS158 PARAMETER ALL IS NOTSUPPORTED IN THIS COMMAND

ExplanationThis message was generated for one of the followingreasons:

• Line ALL cannot be specified if the PTERM parameteris specified.

• Parameter ALL is not supported in this form of thecommand.


Operator response:(local/remote terminal) Enter the command againwith a specific parameter. To broadcast to all lineswith a specification of LINE ALL, enter the commandwithout the PTERM keyword. Check for the other /LOCK and /UNLOCK command formats.

Module:DFSIDPD0, DFSIDP60, DFSICL10, DFSICL80,DFSICL90, DFSICLN2

DFS159 FORMAT KEYWORD PARAMETERIS INVALID

ExplanationThe parameter specified for the FORMAT keyword wasnot recognizable by the system.


Operator response:(local/remote terminal) Check the command syntaxand reenter the command.

Module:DFSICL20

DFS160 MSDB PARAMETER INVALID WITHGLOBAL KEYWORD

ExplanationReserved parameter MSDB is not supported with theGLOBAL keyword.


Operator responseReenter the command without keyword GLOBAL.

Module:DFSICM40


DFS161 LIMIT/PROCESS COUNTKEYWORD PARAMETER ISINVALID

ExplanationThe limit or process count must be greater than zeroand less than 65536.



Module:DFSICL70

DFS163 KEYWORD IS INVALID

ExplanationOne or more keywords specified were invalid for thecommand being entered. Alternatively, a keyword usedwas for an optional feature (such as VTAM or FASTPATH) not in your system.


Operator response:(local/remote terminal) Check the command formatand reenter the command.

Module:DFSCML70, DFSICA10, DFSICLD0, DFSICLE0,DFSICLG0, DFSICLJ0, DFSICLN0, DFSICLQ0,DFSICLU0, DFSICL10, DFSICL20, DFSICL40,DFSICL60, DFSICL70, DFSICL90, DFSICM00,DFSICVA0, DFSIC460, DFSIDPK0, DFSIDP00,DFSIDP80, DFSICLN1

DFS164 FIRST KEYWORD IS INVALID

ExplanationThe first keyword of the command is invalid for the /ASSIGN command.


Operator response:(master terminal) Check the format, and reenter thecommand.

Module:DFSCML70, DFSICL70

DFS165 COMMAND VERB IS INVALID

ExplanationThe command verb could not be recognized as valid.


Operator response:Correct the command and run it again.

Module:DFSICIO0, DFSICLP0

DFS166I CHECKPOINT ID NOT ON LOG RE-ENTER RESTART COMMAND

ExplanationIMS issues this message for the following reasons:

• The OLDS/SLDS did not contain the specifiedcheckpoint or the checkpoint was invalid.

• IMS is searching for the restart checkpoint. If theOLDS data sets are not being used, the PRIOLDSand SECOLDS records need to be removed from theRECON. Archive and error status flags do not excludelogs from restart processing.

System actionIMS waits for another restart command.

Operator responseReissue the restart /NRE or /ERE command.

Module:DFSRBCP0

DFS167 INVALID RESTART FROM CHKPTSPECIFIED. RE-ENTER RESTARTCOMMAND

ExplanationThis message is generated when the operator requestsone of the following invalid combinations:

• Normal warm start from a simple checkpoint• BLDQ type restart from a FREEZE or SIMPLE

checkpoint• Non-BLDQ type restart from a PURGE or DUMPQ

checkpoint• /ERE command specifying CHKPT 0, but the

checkpoint returned by the logger is not a cold startcheckpoint.

Chapter 7. DFS messages, DFS151-DFS200 75

System actionIMS waits for another RESTART command to beentered.

Operator response:(master terminal) Enter the correct command or entera cold start. If a cold start is to be done, IMS mustbe reloaded because the prior restart command mighthave modified the control blocks. A cold start assumesthat the control blocks have not been previously used.


Module:DFSRBCP0


DFS168I CHECKPOINTED BLOCKS DO NOTMATCH LOADED BLOCKS. REASONCODE xxxx.

Explanation:See the description of message DFS0168I.

Related information“DFS0168I” on page 76CHECKPOINTED BLOCKS DO NOT MATCHLOADED BLOCKS. REASON CODE xxxx.

DFS0168I CHECKPOINTED BLOCKS DO NOTMATCH LOADED BLOCKS. REASONCODE xxxx.

ExplanationThis message is generated if you changed either theIMS checkpoint or loaded blocks since the specifiedcheckpoint was taken. For an explanation of thereason code, see abend 0168.


Operator response(master terminal) Either cold start the system, or re-IPL IMS with the nucleus that was used when thecheckpoint was taken and attempt the warm startagain.

Programmer responseSee the description of abend 0168.


ModuleDBFEROC0, DBFNRSTO, DFSRLP00, DFSFDR10

Related information0168 (Messages and Codes)“IMS problem determination” on page 11IMS messages and codes problemdetermination is accomplished by usingprocedures established by IBM.

DFS169I INITIALIZATION IN PROGRESS,CANNOT PROCESS COMMAND

ExplanationThe log routing function of the tracking subsystem isinitializing and cannot respond to the command.


Operator responseReenter the command at a later time.

Module:DFSIDPO0

DFS172 MULTIPLE PHYSICAL PAGE INPUTMUST BE FROM SAME PARTITION

ExplanationDuring multiple physical page input processing, inputdata was entered from a partition that was not thepreviously inputting partition. An input message wasnot created.

System actionIf an output message was in progress, it is returned tothe message queue. Input data is ignored.

Operator response:If an output message was in progress, request the nextmessage to obtain it.


Module:DFSCFEI0

Related information“IMS problem determination” on page 11




DFS173I A NORMALLY COMPLETED JOBMAY NOT BE BACKED OUT IF THEIRLM WAS ACTIVE

ExplanationDatabase Backout is running. DBRC=C was specifiedfor this execution, but IRLM was active in the previousexecution.

System actionThe backout job terminates with a nonzero returncode.

Module:DFSBCKI0

DFS174 AREA|DATABASE|DATAGROUPKEYWORD NOT PRESENT

ExplanationKeyword AREA, DATABASE, or DATAGROUP was notpresented on a /DBDUMP or /DBRECOVERY command.


Operator responseCorrect the command and reenter it.

Module:DFSICM40

DFS175 DATABASE|DATAGROUPKEYWORD PARAMETER NOTPRESENT.

ExplanationThe DATABASE or DATAGROUP keyword was notfollowed by a parameter.


Operator responseCorrect the command, and reenter it.

Module:DFSICM40, DFSIC4C0

DFS177 DATA FOLLOWED EOB OR EOM.REENTER MESSAGE

ExplanationNo data is allowed to follow an end-of-block (EOB)or end-of-message (EOM) in an IBM 2740 Model 2buffer. The operator must enter the entire messageagain correctly.


Operator response:(local/remote terminal) Route the message back tothe inputting terminal.

Module:DFSDN040

DFS178I INTERNAL ERROR, CANNOTPROCESS COMMAND

ExplanationDBRC detected an internal error when it was called toreturn a list of database or area names for one of thefollowing commands:

• DBRECOVERY DATAGROUP• START DATAGROUP• STOP DATAGROUP

This message is also issued for internal errors thatresult from an online change command, such as:

• /MODIFY ABORT• TERMINATE OLC• /MODIFY COMMIT• INITIATE OLC PHASE(COMMIT)• /MODIFY PREPARE• INITIATE OLC PHASE(PREPARE)


Module:DFSIC4C0, DFSICM30, DFSICM40, DFSICV30,DFSICV80, DFSOLC10

DFS179 TERMINATION IN PROGRESS,CANNOT PROCESS COMMAND.

ExplanationIMS is terminating.



Module:DFSIDPO0, DFSIC4A0, DFSIC4B0

DFS180 NO ACTIVE CONVERSATION INPROCESS, CANNOT PROCESSCOMMAND

ExplanationA conversational command was entered for a terminalor user that had no active conversation.

System actionThe command was ignored.

Operator response:(master terminal) If the user specified non-autodelete for paging and has not dequeued theconversational reply, this message can occur as aresult of the /EXIT command being entered. If so, toallow the system to continue, enter a question markcharacter (?) to dequeue the last paged message.

Module:DFSICLH0

DFS181 INVALID OR MISSING KEYWORD

ExplanationOne or more required keywords were not specified, orinvalid keywords were specified for the command.


Problem determination:Check the format, and reenter the command properly.

Module:DFSIC430, DFSIC460, DFSICLG0, DFSICLH0,DFSICLQ0, DFSICLW0, DFSICLY0, DFSICL40,DFSICL50, DFSICL60, DFSICM00, DFSICV10,DFSIDPB0

DFS182I INVALID OR MISSINGPARAMETER

ExplanationEither a parameter was missing for one or more of thespecified keywords or it was invalidly specified.


If you received this message while running a commandfor a data group, or after entering a command for adata group, verify that you used the DBRC commandINIT.DBDSGRP GRPNAME(name) DBGRP(dbname)to create the group.

Operator response:Reenter the correct format of the command.

Module:DFSCML70, DFSICLE0, DFSICLG0, DFSICLH0,DFSICLJ0, DFSICLK0, DFSICLM0, DFSICLN0,DFSICLQ0, DFSICLW0, DFSICLU0, DFSICLY0,DFSICL10, DFSICL20, DFSICL50, DFSICL60,DFSICL70, DFSICL90, DFSICM00, DFSICM40,DFSICVA0, DFSIC410, DFSIC420, DFSIC430,DFSIC450, DFSIC460, DFSIC470, DFSIC480,DFSIDPL0, DFSIDP00, DFSIDP60, DFSIDP70,DFSIDP80, DFSIDPB0, DFSIDPH0, DFSIDPI0,DFSICLN1, DFSICLN2, DFSICLN3, DFSICLN4

DFS183I CONVERSATION ID INACTIVE ONPTERM OR USER, COMMANDUNPROCESSED

ExplanationThe conversation specified by the ID of this commandwas not assigned to the terminal or user specified.Therefore, no action was taken.

System actionThe entered command is disregarded.

Operator response:(local/remote terminal) Correct the ID of the terminalor user specification and reenter the command.

Module:DFSICLH0

DFS184 CONVERSATION IN USE. CANNOTPROCESS COMMAND


• The conversation message is presently in the queuewaiting to be processed by a message processingprogram.

• The last output message is temporarily unavailablebecause of incomplete restart resynchronization.

• The Use Manager LOCK request failed because theConversation Control Block (CCB) is currently in useby some other process.



Operator response:Wait for the response from the program beforereentering the /HOLD or /EXIT command. If theconversation is in use because of incomplete restartresynchronization or if the CCB is in use by some otherprocess, this condition should exist for only a shortamount of time.

Module:DFSICLH0

DFS185 CONVERSATION NOT SCHEDULED,CANNOT PROCESS COMMAND

ExplanationThe conversation is still in the process of beginning.


Operator response:Wait for the first message to be completed beforereentering the command.

Module:DFSICLH0

DFS186 CONVERSATION ID IS INVALID

ExplanationThe parameter entered as an ID for the conversationwas not four characters long, was an invalidconversation number for this system, or was for aninactive conversation.



Module:DFSICLH0

DFS187 NO HELD CONVERSATION ONTHIS PTERM, CANNOT PROCESSCOMMAND

ExplanationThere are no conversations held for the currentterminal. If any were held they have been terminatedor released already through the /RELEASE or /EXITcommand.


Module:DFSICLH0

DFS188 CONVERSATION IN PROCESS,CANNOT ACTIVATE ANOTHER

ExplanationOnly one conversation can be active on a terminal at atime.


Operator response:If you want to activate a new conversation, eitherexit the current one or hold it before reentering the /RELEASE command.

Module:DFSICLH0

DFS189 TERMINAL OR USER NOTSTOPPED AND IDLE, CANNOTPROCESS COMMAND

ExplanationThe terminal or user must be stopped or idle, or both,before the command can be processed.

For /DEQUEUE LINE, LTERM, MSNAME, or NODEcommand, the line, MSC link, or node must be stoppedand idle if the PURGE/PURGE1 keyword is specified.

For /DEQUEUE LTERM with the PURGE/PURGE1keyword specified, if the command is issued for adynamic LTERM in a shared-queue environment withthe STM=YES option specified, the user must bestopped and idle.

For /DEQUEUE LUNAME, the LU 6.2 destination mustbe stopped.

For /DEQUEUE USER, the user must be stopped if thePURGE/PURGE1 keyword is specified.

For /EXIT command, the line or node must bestopped and idle to protect the conversationaluser from having the conversation terminated whileentering a segment for it.



Operator response(local/remote terminal) For /DEQUEUE LINE, /DEQUEUE LTERM, /DEQUEUE MSNAME, and /DEQUEUENODE, stop and idle the line/node/link. For /DEQUEUELUNAME, stop the LU 6.2 destination. For /DEQUEUEUSER, stop the user.

For /DEQUEUE LTERM with the PURGE/PURGE1keyword specified, complete the following steps:

1. Issue a /STOP USER command to set the user inthe stopped status.

2. Issue the /DEQUEUE LTERM command with thePURGE/PURGE1 keyword again.

3. If the command fails again with a DFS189 messagebecause an IMS checkpoint is triggered after the /STOP USER command but before the /DEQUEUELTERM (PURGE/PURGE1) command is issuedagain, restart the user, and repeat Steps 1-2.

Module:DFSICLH0, DFSICLJ0, DFSICL50

DFS190 CANNOT OUTPUT PRINTER 1

ExplanationThe specified terminal component caused an I/O error.

System actionThe terminal component is shut down.

Operator response:Correct the problem, and enter the proper componentrestart command to continue output.

Module:DFSDN020, DFSDS020

DFS191 CANNOT OUTPUT PRINTER 2



Operator response:Correct the problem, and enter the proper componentrestart command to continue output.


DFS192 CANNOT OUTPUT PUNCH 1



Operator response:Correct the problem, and enter the correct componentrestart command to continue the output.


DFS193 CANNOT OUTPUT PUNCH 2



Operator response:Correct the problem, and enter the correct componentrestart command to continue output.


DFS194W DATA BASE xxxxxxxx REFERENCEDBY PSB yyyyyyyy IS NOTREGISTERED WITH DBRC.

ExplanationThe named database referenced by the namedPSB was not registered with DBRC. IMS treats thedatabase as though exclusive use was specified for thesubsystem by the user.

System actionThe PSB scheduling continues.



• If data base integrity protection is wanted in the datasharing environment, register the database to DBRC.

• If the registration is not desirable, make sure that noapplication program currently updates the databaseacross subsystems.

Module:DFSDBAU0

DFS195 UNABLE TO ACQUIRE BUFFER FORLOOP TEST


ExplanationNo buffer was available to start a loop test operation.


Operator response:If this situation persists, contact systems operationpersonnel.

Module:DFSICL50

DFS196 INPUT ONLY DEVICE, TEST/LOOPTEST INVALID

Explanation/TEST and /LOOPTEST commands cannot be enteredfrom an input-only terminal.


Programmer responseContact your IMS system programmer for assistance.

Module:DFSICL50

DFS197 CONVERSATION NOT ALLOWEDON SHARED LOGICAL TERMINAL

ExplanationMore than one physical terminal was using the logicalterminal assigned to your terminal, or it was assignedto another terminal for output. Conversationaltransactions cannot be entered from this type ofcommunication network.

System actionThe requested conversation is not started.

Operator response:

If the transaction is required, request the masterterminal operator to assign an unshared logicalterminal to this PTERM.

Module:DFSCON00

DFS198 SHUTDOWN IN PROCESS

ExplanationShutdown was already in progress when the /DISPLAY SHUTDOWN STATUS command was entered.Status request is ignored when shut down is at apoint where no messages are in progress, and nocommunication lines or physical terminals are active.

System actionShutdown continues.

Module:DFSIDP90

DFS200 IMS DISCONNECTED LINE XXX

ExplanationOn a 1050 switched communication line, an erroroccurred while attempting to send to PRINTER 1 orread from the keyboard. On a 3275 switched line, anuncorrectable I/O error occurred.

System actionIMS disconnected the terminal. The line was restarted.You can attempt to reconnect if you want.

Operator response(Local/remote terminal) On a 1050, check the switchsetting at the remote terminal. On a 3275, no action isrequired.

ModuleDFSDS020, DFSDS040, DFSDS050, DFSDS060




DFS201 INVALID LTERM CHAIN FORFORMAT SPECIFIED

ExplanationThe LTERM specified in a /ASSIGN command is theinput LTERM for multiple physical terminals (LTERMs).


Operator response:(master terminal ) Reenter the command, usingproper format to cause the desired results.

ModuleDFSICL70

DFS202 2770/2265 PROCEDURAL ERROR.

ExplanationThe /TRACE SET ON or /TRACE SET OFF commandwas entered with no monitor parameters specified.


Operator response:(entering terminal) Reset the terminal, and try theoperation again.

Module:DFSDN070

DFS203 LOOPTEST NOT VALID FOR THISLINE

ExplanationA /LOOPTEST command has been entered for aswitched line, or a remote processor line, that is, aSystem/3 or System/7. A /LOOPTEST command is notvalid for these types of lines.


ModuleDFSICL50

DFS204 INVALID LTERM ASSIGNMENTFOR 2770.

ExplanationAn invalid LTERM assignment has been made fora 2770 terminal. The terminal has a componentLTERM assigned to an input-only component slot. Theterminal was stopped.


Operator response:(master terminal) As a temporary circumvention,reassign the LTERM in error.

Programmer responseEnsure that system definition for the terminal wascorrectly specified.

Module:DFSDN090

DFS205 STORAGE NOT AVAILABLE FORBUILDING PARTITION CIBS

ExplanationMFS received a message to build partition CIBS(communication interface block storage), but wasunable to acquire storage to build partition CIBS.

System actionThe LTERM was marked inoperable, and the messagecausing the problem was returned to the messagequeue.

Operator response:(master terminal) Contact your IMS systemprogrammer for assistance. If use of the LTERM isto continue, a /START LTERM xxx command mustbe issued. The message can be removed from themessage queue with the /DEQUEUE LTERM P1PURGE1 command.


Programmer responseSend the output message when system activity hasdecreased and more storage is available, or increasethe main storage available to IMS.

Module:DFSCFEO0

DFS206 QBLK D/S LIMIT REACHED. MUSTREBUILD.

ExplanationA record was allocated within the shutdown area onthe IMS.QBLKS system data set.

System actionAn internal /CHE DUMPQ command was initiated andin most cases, the system shuts down. In an XRFenvironment, a /CHE SNAPQ will be initiated if thereare VSO areas that have I/O tolerated data, and thesystem will not shut down.

Operator responseIf the system shuts down, increase the spaceallocation for the IMS.QBLKS system data set andrestart from the DUMPQ checkpoint which follows themessage. The secondary allocation is not normallyapplicable to IMS queue data sets. Note also that theFORMAT parameter must be used to format this dataset during restart.

If a SNAPQ has been issued, the system continuesto run, but it approaches the threshold value onthe queue data set. If the system abends, increasethe queue data set allocation and restart the systemfrom the SNAPQ checkpoint using the /ERE BUILDQcommand.

Module:DFSQMGR0

DFS207I SMSG D/S LIMIT REACHED. MUSTREBUILD.

ExplanationA record has been allocated within the shutdown areaon the IMS.SHMSG system data set.

System actionAn internal /CHE DUMPQ command has been initiatedand in most cases, the system shuts down. In anXRF environment a /CHE SNAPQ is initiated if thereare VSO areas that have I/O tolerated data, and thesystem does not shut down.

Operator response(z/OS system) If the system shuts down, increasethe space allocation for the IMS.SHMSG system dataset and restart from the DUMPQ checkpoint whichfollows the message. The secondary allocation is notnormally applicable to IMS queue data sets. TheFORMAT parameter must be used to reformat this dataset during restart.


Module:DFSQMGR0

Related conceptsMessage queue data set failures (Operationsand Automation)Related reference/NRESTART command (Commands)

DFS208I LMSG D/S LIMIT REACHED. MUSTREBUILD.

ExplanationA record has been allocated within the shutdown areaon the IMS.LGMSG system data set.

System actionAn internal /CHE DUMPQ command has been initiatedand in most cases, the system shuts down. In anXRF environment, a /CHE SNAPQ is initiated if thereare VSO areas that have I/O tolerated data, and thesystem does not shut down.

Operator response(z/OS system operator) If the system shuts down,increase the space allocation for the IMS.LGMSGsystem data set and restart from the DUMPQcheckpoint which follows the message. The secondaryallocation is not normally applicable to IMS queuedata sets. The FORMAT parameter must be used toreformat this data set during restart.


Module:DFSQC010


http://www.ibm.com/support/knowledgecenter/SSEPH2_15.1.0/com.ibm.ims15.doc.oag/ims_msgqueue_failure.htm#ims_msgqueue_failure


http://www.ibm.com/support/knowledgecenter/SSEPH2_15.1.0/com.ibm.ims15.doc.cr/imscmds/ims_nrestart.htm#ims_cr2nrestart

Related conceptsMessage queue data set failures (Operationsand Automation)

DFS209 STOP FOR DEPENDENT REGIONIN PROGRESS, CANNOT PROCESSCOMMAND.

ExplanationA /STOP or /PSTOP command is currently in process.


Operator response:Reenter the command. If the message is received afterseveral attempts, terminate the IMS system by usingan MVS modify F command, and contact your IMSsystem programmer.


Module:DFSIC470


DFS210 LTERM MAY NOT BE REASSIGNED

ExplanationThe system console LTERM and inquiry LTERM cannotbe reassigned. If a given physical terminal has onlyone LTERM assigned to it, that LTERM cannot bereassigned unless the physical terminal is inoperable.An LTERM cannot be reassigned to its own position.


Operator response:(master terminal) Reenter the command with adifferent LTERM name.

Module:DFSICL70

DFS211 INVALID REASSIGNMENT FORNAMED LTERM

ExplanationAn attempt was made to:

• Assign the master terminal to an ineligible device• Make an improper assignment for VTAM nodes that

would split the logical terminal• Make an improper assignment for a node or user that

was created to retain status data.• Assign the output to an input only device.

The master terminal cannot be assigned to any of thefollowing:

• A user• A switched line• An input-only terminal• An output-only terminal• An NTO terminal• An unattended SLUTYPE1 terminal• An LUTYPE6 node.

An assignment that splits the logical terminal for VTAMnodes is not allowed. The format of the command is:

/ASSIGN INPUT LTERM lterm1 TO NODEnode1/ASSIGN OUTPUT LTERM lterm1 TO NODEnode1/ASSIGN LTERM lterm1 TO LTERM lterm2(where lterm1 or lterm2 is associated with aVTAM node).

Nodes or users that were only created to retain statusdata and have not been logged on or signed on are notallowed in an /ASSIGN command. For example, a /TRACE SET ON NODE command that creates a nodewith a status of trace, in anticipation of the terminallogging on, is not allowed as a node parameter in the /ASSIGN command.


Operator response:(master terminal) Enter a valid form of the /ASSIGNcommand.

ModuleDFSICL70

DFS211I INVALID REASSIGNMENT FORNAMED LTERM

ExplanationSee message DFS211

Related information“DFS211” on page 85




INVALID REASSIGNMENT FOR NAMED LTERM

DFS212 PTERM IN USE, CANNOT PROCESS

ExplanationThe physical terminal is in conversational mode, inpreset mode, in response mode, or is a signed-onsubpool.


Operator response:(master terminal) Wait for the terminal to be free oruse another terminal.

ModuleDFSICLE0, DFSICL70

DFS213 COMMAND FORMAT IS INVALIDFOR LTERM

ExplanationThe /ASSIGN command format is invalid or theLTERM structure is invalid for the particular commandoperands.


Operator response:(master terminal) Verify the command syntax andreenter the command.

ModuleDFSICL70

DFS214 ASSIGNMENT TO SWITCHEDLINES NOT ALLOWED

ExplanationLTERMs cannot be assigned to switched lines.


Operator response:(master terminal) Assign the LTERM to a valid line.

ModuleDFSICL70

DFS215I COMMAND INVALID ON THIS IMSSYSTEM

ExplanationThis command can be issued only on the IMS systemdesignated as the command master. All commandsentered from a local IMS (the MTO, a local userterminal, or AOI) are treated as the command master.For a command entered from the Operations Manager(OM) TSO Single Point of Control (SPOC), only one IMSamong those chosen by OM to process the commandis treated as the command master.


Operator responseIf you enter the /OPNDST command from OM TSOSPOC and you want to log the node onto a particularIMS, specify ROUTE(imsid). If your command doesn'tspecify ROUTE(imsid), the /OPNDST command isrouted to all the IMS systems and IMS will onlyprocess the command on the IMS that is designatedas the command master. The other IMS systems willissue this message.

Module:DFSICLQ0

DFS216 SYSTEM COMMAND FAILURE,NOTIFY SYSTEM PROGRAMMER

ExplanationThe command processor detected either an errorthat was unrecoverable or an invalid interface with acommand action module.

System actionThe entered command is ignored.

Operator response:(local/remote terminal) Determine which commandcaused the message, and notify the systemprogrammer.


ModuleDFSDBDR0, DFSDGS98, DFSICLC0, DFSICLG0,DFSICLH0, DFSICLJ0, DFSICLN0, DFSICLP0,DFSICLZ0, DFSICL40, DFSICL60, DFSIC410,DFSIC420, DFSIC430, DFSIC440, DFSIC450,


DFSIC460, DFSIC470, DFSIDP60, DFSIDPB0,DFSIDPH0, DFSIDPK0, DFSICLN1, DFSICLN2


DFS217 7770-3 USER INPUT EDIT ERROR,LINE STOPPED. LINE xxx PTERMnnn

ExplanationUser module DFSI7770 has passed incorrectinformation to the 7770 device module.

System actionThe line stops and processing continues.

Operator response:(master terminal) Notify the system programmer. Donot restart the line.

ModuleDFSDS030

DFS218 7770-3 USER OUTPUT EDITERROR, LINE STOPPED. LINE xxxPTERM yyy

ExplanationUser module DFSO7770 has passed incorrectinformation to the 7770 device module.

System actionThe line is stopped, and IMS continues processing.

Operator response:Notify the system programmer. Do not restart the line.

Module:DFSDS030

DFS219 7770-3 USER SIGN ON EDITERROR, LINE STOPPED. LINE xxxPTERM nnn

ExplanationUser module DFSS7770 passed incorrect informationto the 7770 device module.

System actionThe line is stopped and IMS continues processing.

Operator response:(master terminal) Notify the system programmer. Donot restart the line.

Module:DFSDS030

DFS220 NO MESSAGE IS AVAILABLE FORREPEAT.

ExplanationA 7770 terminal requested that a message berepeated. Either no message has been sent previouslyto the caller, or a READ/WRITE queue error occurredwhile retrieving the last output message.


Operator response:(master terminal) Continue normal processing, anddo not use repeat until you have received an outputmessage.

Module:DFSDS030, DFSICIO0

DFS221 7770-3 CONTROL UNIT HAS MAKEBUSY SWITCH SET FOR LINE xxxPTERM nnn

ExplanationThe 7770 control unit for LINE xxx has the make-busyswitch on.


Operator response:If the switch action is intentional, continue normalprocessing. If it is not intentional, make sure that theswitch is turned off and then START the LINE andPTERM to continue.

Module:DFSDS030

DFS222 INVALID PAGE REQUEST

ExplanationThe format of the request-for-new-page entry isimproper or incorrect.

System actionThe request is ignored.


Local/remote terminal operator response: Seemessage DFS223.

ModuleDFSCFEP0, DFSPAGE0

Related information“DFS223” on page 88PAGE REQUESTED NOT CONTAINED INCURRENT MESSAGE

DFS223 PAGE REQUESTED NOTCONTAINED IN CURRENTMESSAGE

ExplanationYou requested a page before the first page or after thelast page of this message.


Operator response(local/remote terminal)

• If the device is a 2260 or a 2265,

– Reenter the request for a page within thismessage, or

– Enter a question mark (?).• If the device is a 3270 display, a 3600 display, or

a remote program using the MFS DPM formattingfunction,

– The original message is still on the queue for thisLTERM.

– If only one LTERM is assigned to this physicalterminal, a NEXTMSG request (or pressing the PA2key on a 3270 or SLU2 device) will get the firstphysical page of the original message.

– If multiple LTERMS are assigned to this physicalterminal, a NEXTMSG request (or pressing the PA2key on a 3270 or SLU2 device) will get the firstphysical page of a message destined to the nextLTERM assigned to this physical terminal.

– Pressing any key other than the PA2 key (on a3270 or SLU2 device) will cause a new messageto be displayed while the original is still on thequeue.

• If the terminal is programmable,

– Notify the system programmer.

Programmer responseIf the terminal is programmable, check the logic todetermine how paging requests are sent to IMS.

ModuleDFSCFEO0, DFSCFEP0, DFSPAGE0

DFS224 MULTI-PAGE MESSAGE NOT INPROCESS, REQUEST IGNORED

ExplanationA paging request was made while a message wasbeing viewed which was not formatted as a multiple-page message. Therefore, the request cannot behonored.

System action:The request is ignored.

Operator response:Resubmit the request.

Module:DFSCFEP0, DFSPAGE0

DFS225A CTL REGION WAITING FOR DBRCREGION (name) INIT

ExplanationBefore issuing the IMS ready message, the controlregion waits, if necessary, for the DBRC region toinitialize.

In the message text:name

The name of the member in SYS1.PROCLIB whichcontains the DBRC region JCL

System actionThe control region waits for the DBRC region toinitialize.

Operator responseUse the z/OS command D A,L to determine if the DBRCjob exists. If so, no action is required. DBRC eventuallyfinishes its initialization and the IMS Ready messageis issued. If the DBRC JCL had an error, it is notnecessary to cancel the control region if the correctedprocedure is manually started from the z/OS console.

Programmer responseIn the case of a JCL error, correct the DBRC region JCL.

Module:


DFSXCIC0

DFS0226A CTL REGION WAITING FOR CQS(name) RESPONSE TO CONNECTREQUEST - imsid

ExplanationThis message indicates that the IMS control region hasissued the CQS CONNECT request and is waiting for aresponse from CQS.

The message is issued before message DFS810 forsystems:

• That are not XRF capable• During IMS restart for XRF active systems• During XRF takeover for XRF alternate systems.

If the CQS region is stopped after IMS connects toCQS, IMS must reconnect to CQS after the CQS regionbecomes available again. This message is also issuedduring reconnect processing.


The name specified by the CQS= parameter. Thiscan be either the name of the SYS1.PROCLIBmember containing the CQS region JCL, or thename of the member containing the z/OS STARTcommand used to start the CQS procedure.

imsidThe IMS identifier.

System actionThe control region waits for the CQS region to respondto the CONNECT request. The CQS region cannotcomplete the CONNECT request until CQS completesinitialization and issues the CQS READY message,CQS0020.

Operator responseIf CQS is initializing, no action is required. CQS willcomplete CONNECT processing. If CQS issued a WTORas part of CQS initialization, respond to the WTORto allow CQS initialization to complete. If the CQSaddress space fails before it responds to the CONNECTrequest, the IMS control region is notified and noaction is necessary.

ModuleDFSSQ020

DFS227A CTL REGION WAITING FOR DLSREGION (name) INIT

ExplanationBefore issuing the IMS Ready message, the controlregion waits, if necessary, for the DL/I subordinateaddress space to initialize. name is the name of themember in SYS1.PROCLIB which contains the DL/Isubordinate address space JCL.

System actionThe control region waits for the DL/I subordinateaddress space to initialize.

Operator responseUse the z/OS command D A,L to determine if the DL/Isubordinate address space job exists. If so, no actionis required. DL/I subordinate address space eventuallyfinishes its initialization, and the IMS Ready messageis issued. If the DL/I subordinate address space JCLhad an error, it is not necessary to cancel the controlregion if the corrected DL/I subordinate address spaceprocedure is manually started from the z/OS console.

If the DLISAS region appears to be started, it ispossible that DLISAS is actually waiting for the DBRCregion to initialize. Also check the DBRC region JCL forerrors.

Programmer responseIn the case of a JCL error, correct the DL/I subordinateaddress space region JCL.

Module:DFSXCIC0

DFS228I DLS RECALL TCB INITIALIZATIONCOMPLETE

or

DLS REGION DYNAMIC ALLOCATION INITIALIZED

or

DLS REGION STORAGE COMPRESSION INITIALIZED

or

DLS REGION INITIALIZATION COMPLETE


ExplanationInitialization for the indicated function in theDL/I subordinate address space has successfullycompleted.

ModuleDFSXBC60, DFSXDL10, DFSXDYA0

DFS0229W CSA PSB POOL SIZE GT OR EQ TODLS PSB POOL SIZE

ExplanationThe DL/I subordinate address space option wasselected. IMS initialization determined that the sizeof the CSA PSB pool was equal to or larger than thesize of the PSB pool in DL/I subordinate address spacelocal storage.

System actionIMS initialization continues.

Operator responseNotify the system programmer of the receipt of thismessage.

Programmer responseThe sizes of the two PSB pools are specified withthe CSAPSB= and DLIPSB= parameters on the controlregion JCL. Normally, the DL/I subordinate addressspace PSB pool should be much larger than the CSAPSB pool.

ModuleDFSIINS0

DFS230 TRAN SPECIFIED WITH ABDUMPOR TRAN KEYWORD IS NOT VALID

ExplanationThe transaction name specified with the ABDUMP orTRAN keyword was not a valid transaction name orwas missing.


Operator response:Reenter the command with a valid transaction name.

Module:DFSIC470

DFS231 ONLY ONE REGION MAY BESPECIFIED WITH ABDUMP, TRAN,CANCEL, AOITOKEN, OR SYNC

ExplanationYou have specified more than one region ID in a /STOP REGION or /PSTOP REGION command thathas the ABDUMP, TRAN, CANCEL, AOITOKEN, or SYNCkeyword specified.


Operator response:Reenter the command with only one region IDspecified.

Module:DFSIC470

DFS232 CLASS PARAMETER IS MISSINGOR INVALID

ExplanationA command was issued with the CLASS keyword. Theparameter following the class keyword is either:

• An invalid class number• Not specified


Operator response:(local/remote terminal) Reenter the command withthe correct CLASS parameter.

Module:DFSICL70, DFSIC430

DFS233 UNABLE TO PERFORM TEST, NOLOGICAL TERMINAL ASSIGNED.

ExplanationText was entered from a terminal in TEST mode. NoLTERM is assigned to the terminal, so the test cannotbe performed.


Local/remote terminal operator response: /ASSIGNan LTERM to the terminal or enter /END, removing theterminal from test mode.


ModuleDFSICIO0, DFSCFEO0, DFSCFEP0, DFSPAGE0

DFS234 INVALID RETURN FROM PAGING

ExplanationWhile processing an input message, the PagingProcessor returned to an invalid location in the callingmodule.


Programmer responseThis problem is an IMS logic error. Call IBM SoftwareSupport for assistance.

Module:DFSCFEI0

DFS235 SYSIN DATA STREAM CLOSED

ExplanationA SYSIN data stream was read.

Module:DFSDN150

DFS236 TERMINAL IS NOT RECEIVING AMESSAGE.

ExplanationA /DEQUEUE command was received for a terminalthat was not receiving a message. If LTERM wasspecified, the PTERM might be receiving, but theLTERM was not.


Operator response:(local/remote terminal) Verify that the appropriatePTERM or LTERM, or both parameters were specifiedand that the terminal was receiving a message. ThePURGE keyword can be used to dequeue all messagesif the LINE is stopped and idle.

Module:DFSICLJ0

DFS237 DUPLICATE KEYWORDS AREINVALID.

ExplanationYou can use only one of each keyword in thecommand.


Operator response:Reenter the correct command.

ModuleDFSICLJ0, DFSICLN0, DFSICVA

DFS238 LTERM NOT ASSIGNED TO LINE/PTERM

ExplanationThe LTERM specified in the command was notassigned to the LINE and PTERM specified.


Operator response:Identify the appropriate LINE/PTERM/LTERMcombination, and reenter the command.

Module:DFSICLJ0

DFS239 NO PARAMETER ALLOWED WITHPURGE OR PURGE1.

ExplanationPURGE requests that all messages for the specifiedterminal be dequeued and PURGE1 requests that thetop message for the specified logical terminal bedequeued. No parameter is allowed.


Operator response:(local/remote terminal) Reenter the command in theproper format.

ModuleDFSICLJ0

DFS240 UNABLE TO COMPLETE DEQUEUEPURGE/PURGE1


ExplanationThe command was rejected because of one of thefollowing reasons:

• OTMA has sent the output message to the client.OTMA cannot perform dequeue processing until itreceives an acknowledgment, ACK or NAK, from theclient.

• An IMS conversation exists between the specifiedterminal and an application program.

• An error was detected in the process of dequeuingmessages. DFSQMGR0 has returned a code otherthan 0 or 8.

• For the LU 6.2 device, an LU 6.2 conversation is inprogress.


Operator responseIf an IMS conversation exists, use the /EXITcommand to terminate the IMS conversation anddequeue the messages. For the LU 6.2 device, stopthe device and end the LU 6.2 conversation using theVTAM V NET,INACT command.

If an IMS conversation does not exist, or if LU 6.2support or OTMA support is not used, notify the IMSsystem programmer.

Ensure that the OTMA client sends an ACK or NAKmessage to IMS before the TPIPE is stopped fordequeue processing. If the ACK or NACK cannotbe sent by the OTMA client, issue a /STOP OTMAcommand and dequeue the message.


Module:DFSICLJ0


DFS241 EXCLUSIVE CMD INVALID FORINPUT TERMINAL

ExplanationThe /EXCLUSIVE command with the LINE/PTERMparameter is only applicable when the PTERMdescribes a terminal which has no input capability.


Operator response:Ensure that appropriate terminal type and parametersare used, and reissue the command.

Module:DFSICL50

DFS242 AUDITOR'S KEY REQUIRED

ExplanationAn output message exists for a 2980 Model 4 terminal,requiring the auditor key to be inserted in order toreceive the message.

Operator response:(master terminal) Insert the auditor key and enter aquestion mark (?). IMS then attempts transmission ofthe message.

Module:DFSDN110

DFS243 TRANSACTION BUSY-REENTERCOMMAND

ExplanationAn /ASSIGN command was issued with operandsspecifying a transaction currently being scheduled.


Operator response:Reenter the command after a short time has elapsed.

Module:DFSICL70

DFS244 COMMAND INVALID FROMINPUTTING TERMINAL

ExplanationA /FORMAT command has been entered from aterminal which is not supported by the MFS.


Operator response(master terminal)

No action is required.


The /FORMAT command should not be entered from aterminal which is not supported by the MFS.

ModuleDFSICLK0

DFS245 UNABLE TO FETCH ERRORDEFAULT BLOCK-TEST MODERESET

ExplanationWhile in MFS TEST mode, an error occurred attemptingto fetch MFS blocks for an output message. An erroralso occurred attempting to fetch the IMS error defaultblocks, DFSM03 and DFSDF2.

System actionMFS TEST mode has been reset for this terminal.

Operator response:(local/remote terminal) A request for the nextmessage results in an IMS attempt to fetch MFS blocksfrom the production library.

Programmer responseFor an explanation of the failure, see messageDFS271. If format blocks are currently being added tothe test library, I/O errors might result; try again whenadditions are complete.

Problem determinationLog record type X'67', subrecord X'01', ID'FERR', whichcontains diagnostic information, is produced if /TRACEis set on for PTERM at the time of failure.

Module:DFSCFEO0

Related information“DFS271” on page 100UNABLE TO LOAD ERROR MESSAGE OUTPUTDESCRIPTION

DFS246 SPACE EXCEEDED-TEST MODERESET

ExplanationWhile in MFS TEST mode, the space required for testformat blocks was exceeded. MFS TEST format blocksare loaded in the CIOP pool below the 16M line. Thismessage is issued if the CIOP pool does not havesufficient storage below the line.

System actionMFS TEST mode has been reset for this terminal.

Operator response:(local/remote terminal) If a terminal on another lineis also in MFS TEST mode, a retry might be successfulwhen that terminal is not active or is out of MFS TESTmode. If no other terminals are in MFS TEST mode,the blocks exceed the maximum space defined and arenot available in MFS TEST mode. In addition, you canreduce the use of storage below the 16M in the CIOPpool.

Problem determinationLog record type X'67', subrecord X'01', ID'FERR', whichcontains diagnostic information, is produced if /TRACEis set on for PTERM at the time of failure.

ModuleDFSCFEO0, DFSCFE10

DFS247 FIELD LENGTH ERROR-INPUTIGNORED

ExplanationMore data was received for a field than is valid for theformat displayed. Probable cause is that the terminaloperator depressed the CLEAR key when the terminalwas not protected from receiving output.

System actionThe input data was ignored.

Operator response:(local/remote terminal) If the last operator actionbefore receiving the previous output was not a clearor power-off power on sequence, notify your systemprogrammer of a possible hardware or softwareproblem.

Module:DFSCFE00

DFS248 MID AND DIF AREINCOMPATIBLE-INPUT IGNORED

ExplanationThe MID and DIF in the active format data set werenot processed by the MFS Language utility at the sametime. They are not usable for online editing.



Operator response:(master terminal) Recompile the input MSG and FMT.Ensure that the FMT includes a DEV statement for theappropriate device type and features. Ensure also thatthe phase 4 output is inserted into the online formatdata set.

Module:DFSCFEI0

DFS249 NO INPUT MESSAGE CREATED

ExplanationThis message is issued when:

• Editing of input data resulted in a message with nodata, which is ignored by the system, or

• A single segment message from a non-3270 deviceis canceled with '**' at the end of a messagesegment.

• A send error occurs on an APPC (LU 6.2conversation) for one of the following reasons:

– The IMS partner sent a data segment without anydata (a null segment).

– User edit exit issued a return code of 8 (delete all)while processing incoming message segments.

– User edit exit issued a return code of 4(delete current) for all segments while processingincoming message segments.

– The IMS partner issued receive without sendingany data on an iteration of an IMS conversationaltransaction.

System actionThe input data was ignored and the system continuesprocessing.

Operator response:Enter all required input data for this format. If allrequired input data was entered, contact your IMSsystem programmer.

Programmer response:If the message was issued when a send error occurredfor an APPC, determine the type of error. If it was anunacceptable response, correct the error.

Module:DFSCFEI0, DFSICIO0

DFS250 INTERVENTION REQUIRED, LINE xPTERM y

ExplanationAn intervention-required situation was detected on adevice attached to a remote teleprocessing controlunit.

System actionThe system waits for a READY indication.

Operator response:(master terminal) Making the device ready will causeoperation to resume. Any output messages in progresswill be restarted. Any input in progress must bereentered.

Module:DFSDN130


Chapter 9. DFS messages, DFS251 - DFS0300I


DFS251 REMOTE CONTROL UNITINOPERABLE [LINE x PTERM y]

Explanation:For information and responses, see DFS251I.

Related informationDFS251Ihh.mm.ss CONTROL UNIT INOPERABLE LINE xPTERM y-z aa,bbbb,cc,dd,ee,ff,gg,hh, iiii,jjjj

DFS251I hh.mm.ss CONTROL UNITINOPERABLE LINE x PTERM y-zaa,bbbb,cc,dd,ee,ff,gg,hh, iiii,jjjj

ExplanationA remote control unit for one or more devices hasbecome inoperable. All terminals associated with thefailing control unit have been stopped. See informationabout the z/OS system error message IEA000I for lineand TCU errors or IMS error message DFS973I for3270 device errors.

Attention: IMS no longer supports BTAMterminals.

The following description applies to remote 3270devices:Code

Meaningy-z

This field gives the range of PTERMs that areconnected to the control unit.

aaThis field contains the ECB completion code.

bbbbThe DECTYPE field indicates the type of failingoperation.

ccThe DECTPCOD field indicates the datacommunication operation code from the last CCWrun in the channel program.





hhThis field contains the device-dependentmodule code. When the 3270 device-dependentmodules shut down a component of the datacommunication network, a device-dependentmodule reason code indicates why the device-dependent module shut down the component. Thedevice-dependent module codes are describedbelow.


Note: A BSCK return code of X'0108' is set for aselection timeout from the remote control unit. Ifa port does not exist, a /START command mustbe issued which does not include the unavailablePTERMS.

jjjjThis field contains the SENSE/STATUS informationfrom the 3270 device (if applicable). See IBM 3270Information Display System for an explanation ofthe SENSE/STATUS codes.

The device-dependent module codes (field hh) havethe following meanings:Code (Dec)

Meaning01

Data received did not start with start-of-text/start-of-header (STX/SOH) or did not end with end-of-transmission block (ETB) or end-of text (ETX).

02An invalid attention-identification (AID) characterwas received from the 3270.

03One of the following occurred:


• Start/stop (S/S) READ was performed, but dataother than an S/S message was received.

• Fewer than 9 bytes were read on an S/S READ.• S/S message did not have STX character in

correct place.• Device address in S/S message does not match

device address in communication terminal block(CTB).

04Invalid return code passed back in CLBTEMP5from DFSBSCK0.

05Invalid S/S combination received.

06S/S related to a copy operation was received.However, no copy operation was in progress, oran error occurred on copy operation and device-dependent module found invalid DECTYPE or datastream.

07Interrupt request invalidly received from the 3275video display.

08Device end S/S message received, but device-dependent module is not in READ setup or READinterrupt logic.

09Fewer than 5 bytes were read.

10Device address in data stream was invalid for adevice on this control unit or line.

11Retries exhausted on temporary error.

Operator response:(master terminal) Correct the malfunction, and restartall terminals associated with the remote control unitfor LINE x PTERM y. Any operations in progress mustbe restarted.


Module:DFSC3270 (DFS251I), DFSDN030, DFSDN130(DFS251)

Related referencez/OS: IEA000IRelated information“DFS973I” on page 350LINE xxx, PTERM yyy, aaa, {G|S}, tttt, ssss,conditions“IMS problem determination” on page 11


DFS252 ATTEMPT TO OUTPUT DETECTEDBUSY CONDITION

ExplanationA busy condition has been detected on a deviceattached to a remote 3271/3275 or 3275 dial controlunit. A busy condition is not considered normal at thetime it was detected and is normally the result of anoperation being attempted on a terminal when thescreen is unprotected.

Operator response:(local/remote terminal) Any output messagesin progress are sent after this error message.Refrain from performing terminal operations on anunprotected screen.


DFS253 TCU INOPERABLE LINE x PTERM y

ExplanationSee message DFS253I for an explanation and actions.

Related informationDFS253Ihh.mm.ss TCU INOPERABLE LINE x PTERM y-zaa,bbbb,cc,dd, ee,ff,gg,hh,iiii,jjjj

DFS253I hh.mm.ss TCU INOPERABLE LINEx PTERM y-z aa,bbbb,cc,dd,ee,ff,gg,hh,iiii,jjjj

ExplanationThe 270X for LINE x PTERM y is inoperable. AllPTERMs on the line have been marked inoperable,and the line has been placed in an idle state. Seethe information about the z/OS system error messageIEA000I for line and TCU errors or to IMS errormessage DFS973I for 3270 device errors.

Attention: The DFS253I form of the message isissued only for remote 3270 lines.

Attention: IMS no longer supports BTAMterminals.

The following description applies to remote 3270lines:Code

Meaning


http://www-01.ibm.com/support/knowledgecenter/SSLTBW_2.4.0/com.ibm.zos.v2r4.ieam600/m009652.htm?lang=en

y-zThis field gives the range of PTERMs that areconnected to the line.

aaThis field contains the ECB completion code.

bbbbThe DECTYPE field indicates the type of failingoperation.

ccThe DECTPCOD field indicates the datacommunication operation code from the last CCWrun in the channel program.





hhThis field contains the device-dependentmodule code. When the 3270 device-dependentmodule shuts down a component of the datacommunication network, a device-dependentmodule reason code is put in the CLBTEMP1 fieldto indicate why the device-dependent module shutdown the component.


jjjjThis field contains the SENSE/STATUS informationfrom the 3270 device (if applicable).

Operator response:(master terminal) Correct the malfunction, and issuea /START or /RSTART LINE x PTERM ALLcommand.


Module:DFSC3270 (DFS253I), DFSDN130 (DFS253)

Related referencez/OS: IEA000Iz/OS: Exception conditions and senseinformationRelated information“IMS problem determination” on page 11IMS messages and codes problemdetermination is accomplished by usingprocedures established by IBM.

DFS254 BUFFER SIZE INCREASED

ExplanationThe buffer size for a 3270 local line group was notadequate to contain an input message. The buffersize has been increased by 300 bytes for all ensuingmessages.


If this message is repeated, increase the BUFSIZEparameter specified during IMS system definition forthe 3270 local lines, or decrease the amount of databeing input at the terminal.

Module:DFSDN140

DFS255 COPY NOT ALLOWED

ExplanationA request has been made for a video display to becopied to a printer. However, the buffer on the displaywas locked by program action.

Operator response:If the display is intended to be locked, it is not possibleto copy the current display. If it is required to copythe current display, contact the person responsible fordevelopment of the 3270 terminal message formats inyour installation.

Module:DFSDN130

DFS256 PRINTER FOR COPY NOTCURRENTLY AVAILABLE

ExplanationA copy operation was requested on a 3270 terminal,but a printer was not currently available. Alternatively,an intervention-required was returned by the printercomponent of a 3275.

Chapter 9. DFS messages, DFS251 - DFS0300I 97


http://www-01.ibm.com/support/knowledgecenter/SSLTBW_2.4.0/com.ibm.zos.v2r4.istprg0/excsi.htm?lang=en


Operator responseHave the master terminal operator start the PTERMswhich represent printers that can be candidates fora copy operation from the specified terminal. If anintervention-required situation exists on the printercomponent of a 3275 device, make the printers ready.

Problem determinationDo a /DISPLAY LINE x PTERM ALL for the linecontaining the terminal.




DFS257 ERROR OCCURRED DURING LASTTRANSMISSION.

ExplanationAn input or output error occurred during the last inputor output transmission to a 3270 terminal.

Operator response:Reenter the last input message, or press theappropriate key to have the last message resent.




DFS258 UNABLE TO LOCATE MESSAGEDESCRIPTION-INPUT IGNORED

ExplanationEither an I/O error occurred while attempting to fetchthe message input descriptor block or the deviceinput format block, or the blocks were not in theactive format data set, or the block fetched was nota message input descriptor block.


Operator response:Clear the screen, and enter a /FORMAT command.Contact your IMS system programmer for assistance.

Module:DFSCFEI0

DFS259 NO MATCHING STATION CTB.

ExplanationIMS remote station support encountered a problem.No station communication terminal block (CTB)matching the address in the polling list was found.Communication was terminated.

Operator response:(master terminal) Notify your IMS systemprogrammer.

Module:DFSCRSS0

DFS260 PERMANENT TRANSMISSIONERROR LINK x

or

PERMANENT TRANSMISSION ERROR LINE x PTERMy

ExplanationA permanent transmission error occurred whilecommunicating with the remote station identified bythe message, or with another IMS system on theidentified link.

Note: The LINK x portions of this message pertain toMultiple Systems Coupling.

System actionIMS stops the data traffic on the link.

Operator response:(master terminal) When you have corrected theproblem, restart communication using the /STARTLINE x PTERM y or /RSTART LINK x command.

Programmer responseDetermine the cause of the I/O error.

Module:DFSCRST0, DFSCS7T0


DFS261 INVALID DATA FLAGS LINE xPTERM y

ExplanationIMS remote station support encountered an error.The flags in a data block were inconsistent, that is,first segment was indicated while a message was inprogress. Communication was terminated.

Operator response:Notify your IMS system programmer.

Module:DFSCRSV0

DFS262 MESSAGE STARTED DURINGSHUTDOWN. LINE x PTERM y

ExplanationIMS remote station support. IMS sent an immediate-shutdown request or received either a shutdownrequest or a shutdown complete. It then receivedthe first segment of a message. Communication wasterminated.

Operator responseNotify your IMS system programmer.

Module:DFSCRSV0

DFS263 INVALID TERMINAL IDENTIFIERIN DATA BLOCK LINE x PTERM y

ExplanationFor IMS remote station support, a terminal identifiernot defined in the IMS system definition was receivedin a data block. Communication was terminated.


ModuleDFSCRSV

DFS264 INVALID TERMINAL ID IN STATUSCHANGE SEGMENT LINE x PTERMy

ExplanationIMS remote station support. A terminal identifiernot defined to IMS system definition was receivedin a status change segment. Communication wasterminated.


Module:DFSCRSX0

DFS265 INVALID TERMINAL ID IN I/OSYNCH SEGMENT LINE x PTERM y

ExplanationFor IMS remote station support, a terminal identifiernot defined to IMS system definition was received inan I/O synchronization segment. Communication wasterminated.


Module:DFSCR2Y0

DFS266 OUTPUT NOT IN PROGRESS LINE xPTERM y

ExplanationFor IMS remote station support, an error messagewas received specifying a terminal which had nooutput message in progress or which had a systemmessage (Q3 output) in progress. Communication wasterminated.


Module:DFSCR2Z0

DFS267 INVALID TERMINAL IDENTIFIERIN ERROR MESSAGE LINE xPTERM y

ExplanationFor IMS remote station support, a terminal identifiernot defined to IMS system definition was received inan error message. Communication was terminated.


System programmer response:Correct the terminal identifier.

Module:DFSCR2Z0

DFS268 INVALID BLOCK FORMAT LINE xPTERM y


ExplanationIMS remote station support. One of the followingproblems occurred:

• The first 2 characters in a block were neither DA norSY.

• The input block conversion routine was unable toconvert a received block from transmission code toEBCDIC.

• The length exceeded the end of the input block.

Communication with the remote station is terminated.


Module:DFSCRSU0, DFSCRSV0, DFSCS7U0

DFS269 SHOULD NOT OCCUR TYPE ERRORON LINK x

or

SHOULD NOT OCCUR TYPE ERROR ON LINE x

ExplanationIMS remote station support encountered an error. Thiserror can be caused by one of the following problems:

• A hardware malfunction• An invalid specification to z/OS system definition• A programming logic error in the program that

resides in the intelligent remote station

Note: The LINK x portions of this message pertain to aMultiple Systems Coupling feature system.

System actionIMS stops the line or link.

Operator response(master terminal) When you have corrected theproblem, restart communications, using the /STARTLINE x or /RSTART LINK x command.

Module:DFSCMS70

DFS270 PARTITIONED FORMAT SENT TO:[ NODE nodename|LINE x PTERMy]

ExplanationMFS was instructed to format a message with adevice output format (DOF) that specified a partitiondescriptor block (PDB). However, the message was notdirected to a SLU2 terminal.

System actionThe LTERM was marked inoperable, and the messagecausing the problem was returned to the messagequeue.

Operator response:(master terminal) Your IMS system programmershould direct the message to a SLU2 terminal anduse the right device output format (DOF). If theuse of the LTERM is to continue, a /START LTERMxxx command must be issued. This message can beremoved from the message queue with the /DEQUEUELTERM P1 PURGE1 command.

Programmer responseDirect the message to a SLU2 terminal.

Problem determinationLog record X'67' (subrecord X'01', ID'FERR'),which contains diagnostic information, is producedautomatically.

Module:DFSCFEO0

Severity:None.

DFS271 UNABLE TO LOAD ERRORMESSAGE OUTPUT DESCRIPTION

ExplanationThe system was unable to load the error messageoutput description.

System actionBlock fetch has failed for the IMS default messageoutput description or the associated device outputformat. Fetch also failed for a requested messageoutput description or a device output format. TheLTERM was marked inoperable with a QERROR status,and the message causing the problem was returned tothe message queue. This message is sent to the z/OSsystem console if the LTERM involved is the masterterminal.

Operator response:(master terminal) Notify your IMS systemprogrammer. The MTO should ensure that the IMS


default message output description and device outputformats are in the format library and that I/O errorsare not occurring. If use of the LTERM is to continue,a /START LTERM xxx command must be issued. Themessage can be removed from the message queuewith the /DEQUEUE command.

Programmer responseSee the description of message DFS057I for possiblecauses of block fetch errors.

Problem determinationLog record type X'67', subrecord X'01', ID'FERR'which contains diagnostic information, is producedautomatically.

Module:DFSCFEO0

Related information“DFS057I” on page 43REQUESTED BLOCK NOT AVAILABLE:blockname RC = reason

DFS272 FORMAT BLOCK LEVEL ERROR-INPUT IGNORED

ExplanationThe DIF block that was fetched to process the inputwas not at the same level as the MID block used toformat the message or the DOF block used to formatthe device. In MFS TEST mode, new format blockshave been added to the test library since the lastoutput to the terminal. If not in MFS TEST mode,format blocks have been changed by switching theformat data sets with the /MODIFY or INITIATE OLCcommands since the last output to the terminal.


Operator responseFormat the screen and reenter the input. If the lastoutput was logically paged by the operator, it is stillavailable; request the next message. If the last outputmessage was not completely transmitted (all pages), itis still available; request the next message.

Module:DFSCFEI0

DFS273 QUEUE ERROR ON MESSAGEDELETION

ExplanationAn error occurred while attempting to delete themessage in progress. Either an I/O error has occurredon the message queue data set, or an internal logicerror has occurred.


Operator response:Contact your IMS system programmer for assistance.

Module:DFSCFEO0

DFS274 LOAD MODULE DATASET NOTOPEN LINE x PTERM y

ExplanationA System/7 issued a request for a load module,but the load module data set could not be opened.Communication was terminated.

Operator response:(master terminal) Contact your IMS systemprogrammer for assistance.

Module:DFSCS7B0

DFS275 BUFFER TOO SMALL FOR IPLREQUEST LINE x PTERM y

ExplanationA System/7 requested the IPL sequence from IMS,and the input buffer specified for the line is not largeenough.

System actionCommunication is terminated.

Operator responseContact your IMS system programmer for assistance.

Module:DFSCS7B0

DFS276 TRANS ERROR DURING LOADMODULE TRANSMISSION LINE xPTERM y

ExplanationA permanent transmission error occurred whiletransmitting a load module to a System/7.



Operator response:Perform an IPL of the system if required. Startcommunication using the /START line x ptermy command from the IMS master terminal. Have theSystem/7 reissue the load request.

Module:DFSCS7B0

DFS277 I/O ERROR ON THE SYSTEM/7LOAD MODULE DATASET LINE xPTERM y

ExplanationAn I/O error occurred on the load module data setwhile processing a System/7 load request.


Operator response:(master terminal) Contact your IMS systemprogrammer for assistance.

Module:DFSCS7B0

DFS278 MODULE REQUESTED BYSYSTEM/7 DOES NOT EXIST LINEx PTERM y

ExplanationA System/7 requested a module to be loaded thatcould not be found in the load module data set.


Operator response:Contact your IMS system programmer for assistance.

Module:DFSCS7B0

DFS279 LEVEL KEYWORD IS MISSING ORHAS INVALID PARAMETER

ExplanationThe LEVEL keyword in the command is required andhas not been entered, has more than one parameter,or does not have a numeric value of 1 through 4.

Operator responseCorrect the format, and reenter the command.

Module:DFSICLN0

DFS280 SET KEYWORD IS MISSING ORHAS INVALID PARAMETER

ExplanationThe command entered requires the SET keyword, butit was not supplied. The keyword has more than oneparameter, or the parameter was not ON or OFF.


Operator response:Correct the error, and reenter the command.

Module:DFSICLN0, DFSICLN4

DFS281 MODULE KEYWORD IS MISSINGOR HAS INVALID PARAMETER

ExplanationThe command which was entered requires the modulekeyword and it was not supplied, has a parameterother than DDM, MFS, or ALL specified.

Operator responseCorrect the error, and reenter the command.

Module:DFSICLN0

DFS282 TEST MFS NOT OPERATIVE

ExplanationEither the MFS TEST facility was not included atsystem definition or the test format data set could notbe opened during IMS initialization.



Module:DFSICL50




DFS283 TEST MFS NOT SUPPORTED FORTHIS TERMINAL

ExplanationTEST MFS was specified for a non-MFS terminal.


Operator response:(local/remote terminal) Correct the command, andreenter it properly.

Module:DFSICL50

DFS284 CANNOT START TEST MFS MODEWITH MESSAGE IN PROGRESS

ExplanationStatus cannot be changed while the message is beingprocessed.


Operator response:Reissue the command when the terminal is not activeor is stopped.

Module:DFSICL50

DFS285 CANNOT STOP TEST MFS MODEWITH MESSAGE IN PROGRESS

ExplanationStatus cannot be changed while the message is beingprocessed.


Operator response:(local/remote terminal) Reissue the command whenthe terminal is not active or is stopped.

Module:DFSICL50

DFS286 SECURITY VIOLATION LINE xPTERM y

or

SECURITY VIOLATION NODE nodename[USERusername]

or

SECURITY VIOLATION USERID userid PROGRAMprogramname

Explanation:This message is related to DFS286I. See that messagefor a detailed explanation and actions.

Related informationDFS286ISECURITY VIOLATION USERID useridPROGRAM programname

DFS286I SECURITY VIOLATION USERIDuserid PROGRAM programname

or

SECURITY VIOLATION LINE x PTERM y

or

SECURITY VIOLATION USERID userid

ExplanationThe user requested notification at the master terminalwhen a threshold count of security errors was reached.This threshold was reached on one of the following:

• LINE x PTERM y• NODE nodename (USER username)• USERID userid PROGRAM programname

IMS issues USER username with NODE nodename ifthe terminal is signed on with the /SIGN command.IMS issues USERID userid PROGRAM programnameif an application program issues an ICMD call thatcauses a security error. USERID userid is the userID of the user that invoked the program that issued theICMD call. The user ID is based on the type of regionin which the program was executing and whether a GetUnique (GU) call was done:

Region Type GU Done Userid

BMP N/A BMP JCL USER


Region Type GU Done Userid

DBT N/A Security token passed inthe PAPL

IFP NO Program name

IFP YES User ID (if terminalsigned on) or LTERMname where a transactionwas issued

MPP NO Program name

MPP YES User ID (if terminalsigned on) or LTERMname where a transactionwas issued

BMP NO BMP JCL USER

BMP YES User ID (if terminalsigned on) or LTERMname where a transactionwas issued

For resources defined to IMS using system definition,the security threshold is defined with the SECCNTkeyword on the COMM, IMSGEN, or SECURITY macros.For dynamic resources, if the SECCNT parameteris not zero, a threshold value of one is alwaysused. The threshold can also be reached because ofunauthorized transactions attempting to issue a DL/ICMD call; in this case, the transaction code involved isidentified.

System actionThe action is determined by the master terminaloperator.

Make sure the user ID is authorized for the resourcesthat you are trying to schedule.

Operator response:(master terminal) Handle as directed by your securityprocedures.

Module:DFSCMD30, DFSICLZ0, DFSICIO0

Related informationDFS286SECURITY VIOLATION LINE x PTERM y

DFS0287A THERE IS NO SECONDARY INDEXTO PROCESS. DO NOT USEMIGRATX.

ExplanationMIGRATX=YES was specified, but the database youare trying to migrate has no secondary index.

System actionThe HD Reorganization Unload utility job terminatedwith a return code 16.

User response:Do not specify MIGRATX=YES in the SYSIN controlcard if you are trying to migrate a database withoutsecondary index.

Module:DFSURGU0

DFS0288E HISAM REORG UTILITIES CANNOTBE USED FOR FAST PATHSECONDARY INDEX DATABASE,xxxxxxxx

ExplanationSpecifying a Fast Path secondary index database (FPSIDB) as input to either the HISAM Reorganizationunload or reload utilities (DFSURUL0 or DFSURRL0) isnot supported. In the message text:xxxxxxxx

The name of the Fast Path secondary indexdatabase

System actionThe batch job abnormally terminates with IMS abend0288.

Programmer responseUse an appropriate utility to reorganize or recoverFast Path secondary index databases. To reorganize anFPSI DB, an IDCAMS REPRO is sufficient. To recoveran FPSI DB, use either the IMS Recovery Utility,DFSURDB0, or an index builder tool of any IMS vendorproduct.

Module:DFSDLBL0

Related information0288 (Messages and Codes)

DFS289 INVALID VALUE FOR SEGNO/SEGSIZE SPECIFIED

ExplanationThe command previously entered has a SEGNOor SEGSIZE keyword was entered with an invalidparameter specified. The parameter immediatelyfollows the keyword. Valid values for the SEGNO andSEGSIZE are 0 through 65,535, inclusive.



System actionThe command is not processed. Another command, amessage switch, or a transaction can be entered.

Operator response:(entering terminal) Determine the correct value to bespecified for the SEGNO or SEGSIZE parameter, andreenter the command.

Problem determinationHave a copy of the entered command and responseavailable, and contact your IMS system programmer.

Module:DFSICL70

DFS290 NO MESSAGES AVAILABLE FOROUTPUT

ExplanationAn IMS MFS Message Advance Protect or a VTAMready-to-receive indicator was received by IMS, andeither no messages were available or the terminal is ina special status where no output is possible.

System actionFor MFS, the terminal is placed in a page-protectedstatus if it is a video device. For a VTAM ready-to-receive indicator where output is not quiesced, anyvideo component is left in an unprotected status.

Operator response:If a message is expected, either wait briefly, reenterthe request, then enter the next message request andwait, or enter an appropriate command to release anyspecial status conditions that might exist.

Programmer responseUse the /DISPLAY NODE command to determine ifmessages are queued, and whether the terminal is in aspecial status such as CONVERSATION or EXCLUSIVE.


Module:DFSCFEP0, DFSCVFC0, DFSCVFZ0


DFS291 INPUT MUST BEGIN FROM FIRSTPHYSICAL PAGE

ExplanationInput data was entered from other than the firstphysical page of a DPAGE with multiple physical pageinput specified. An input message was not beingcreated.

System actionIf an output message is in progress, it is placed backinto the message queue. Input data is ignored.

Operator response:If an output message was in progress, request thenext message to obtain it. See the information aboutmultiple physical page input procedures.


Module:DFSCFEI0

Related conceptsMultiple physical page input (Operations andAutomation)Related information“IMS problem determination” on page 11IMS messages and codes problemdetermination is accomplished by usingprocedures established by IBM.

DFS292I INVALID RANGE SPECIFICATION

ExplanationThe following are possible causes of this message:

• Range parameters were specified with a keywordthat does not support range parameters.

• The second member of the range specification wasnot larger than the first.

• One of the nodes specified is not in the system.• Both of the nodes specified are dynamic.


Operator responseReenter the command correctly.

Range specifications apply only to the keywords LINE,LINK, NODE, and PTERM. Range specifications forthe NODE keyword apply only to static nodes. Bothmembers of the range specification must exist andmust be defined through system definition.

For dynamic terminals or users, generic parametersupport replaces range specifications. A generic


http://www.ibm.com/support/knowledgecenter/SSEPH2_15.1.0/com.ibm.ims15.doc.oag/ims_3270_physicalpage.htm#ims_3270_physicalpage

http://www.ibm.com/support/knowledgecenter/SSEPH2_15.1.0/com.ibm.ims15.doc.oag/ims_3270_physicalpage.htm#ims_3270_physicalpage

parameter contains one or more special characters, *,or '. The asterisk indicates that at least one charactermight replace it, creating a valid resource name. Forexample, /DISPLAY NODE *SLU6* displays nodeswhich contain the character string SLU6.

Module:DFSICL30

DFS0293 INVALID ID CARD READER INPUT

ExplanationInput from an operator identification card reader wasinvalid. No "EOR" or "EOI" character was found toterminate the input data, or the LRC check failed.

System actionAny input message in progress is discarded.

Operator response:(master terminal) Retry the operation. If the errorpersists, notify your systems programmer.

Programmer response1. Ensure that entry is made into a field large enough

to contain all card data.2. Ensure that the card being used and the 3270

hardware function correctly.

Problem determinationUse /TRACE and DFSERA10 to obtain a printout of theterminal input data received by IMS. See IBM 3270Information Display System for data formats.

ModuleDFSCFE10, DFSCFE00

DFS294 ID CARD READER USE ALLOWEDONLY ONCE PER MESSAGE

ExplanationWhen creating a multiple physical page input message,the 3270 operator ID card reader can be used onlyonce.


Operator response:Reenter the message using the ID card reader onlyonce.

Problem determination:

16

Module:DFSCFE00, DFSCFE10


DFS295 IMMEDIATE PEN DETECT LITERALALLOWED ONLY ONCE PERMESSAGE

Explanation3270 immediate pen detect can be used in mixedmode, or to create an input literal only once permessage.


Operator response:Reenter the message, using the immediate pen detectfacility only once.

Problem determination:MFS

Module:DFSCFE00

DFS296 PROGRAM FUNCTION KEYLITERAL ALLOWED ONLY ONCEPER MESSAGE

ExplanationWhen creating a multiple physical page input message,the program function key can be used to create aliteral value only once. Keys defined for operatorcontrol can be used more than once.


Operator response:Reenter the input message, using the correct programfunction keys.


Module:DFSCFE00




DFS297 MULTIPLE PHYSICAL PAGE INPUTIS NOT IN PROGRESS

ExplanationWhen no multiple physical page input message wasbeing created, the operator has entered a request toterminate multiple physical page input (ENDMPPI).

System actionInput data is discarded.

Operator response:Reenter the input, using the appropriate procedure.


Module:DFSCFEI0


DFS298 INPUT MESSAGE CANCELED BYSEGMENT EDIT EXIT

ExplanationA user-supplied MFS segment edit exit routinerequested that the input message be canceled orechoed by DPM-B.

Either the reason for the cancellation is dependentupon an application, with invalid input, or thedistribution presentation management B (DPM-B)requests that the input message be echoed. Theechoed message is not supported for DPM-B.

System actionThe input message in progress is deleted.

Operator response:Enter the message in the manner required by the exitroutine.

Programmer responseVerify correct operation of the user-supplied exitroutine. Terminal input data can be examined by useof the /TRACE facility.

Module:DFSCFEI0

DFS299 SEGMENT EDIT EXIT FAILURE-NOTIFY SYSTEMS PROGRAMMER

ExplanationA user-supplied MFS segment edit exit routine haseither increased segment size beyond the maximumallowed, or returned an invalid return code. Systemintegrity can be harmed due to the edit routine failure.

System actionThe input message in progress is deleted.

Operator response:Record what was entered before this message wasdisplayed, then contact your IMS system programmer.

Programmer responseCorrect the segment edit exit routine, and replace itin the IMS nucleus. Verify correct operation of theuser-supplied exit routine. Terminal input data can beexamined by use of the /TRACE facility.

Module:DFSCFEI0

DFS0300I OUTPUT DATA SET SPECIFIEDBY DDNAME ddname WAS NOTSUCCESSFULLY CLOSED

ExplanationDuring Database Image Copy 2 (DFSUDMT0) utilityprocessing, data set close was unsuccessful or wasnot attempted (by DFSMSdss) for the output data setindicated by ddname. The data set is therefore notusable as an image copy.

System actionImage copy processing continues for the inputDBDSs if there is another output copy (primaryor secondary) that has not encountered an error.Otherwise processing fails for the DBDSs and messageDFS3144A is issued.

Operator responseSubmit another Image Copy 2 job to copy any DBDSsfor which image copy processing failed.

Module:DFSUDUI1


Chapter 10. DFS messages, DFS301A - DFS350A


DFS301A UNABLE TO OPEN DDNAME-ddname

ExplanationThe issuing utility program was unable to open a DCBwith the ddname specified in the message.

System actionProcessing is terminated with a nonzero return code.

Programmer responseEnsure that all necessary DD statements requiredfor execution are supplied. Correct any missing JCLstatements, and resubmit the job. See abend code0302.

Problem determination2, 3, 8, 18, 20, 35. Also, if this message was producedwhile running under the Utility Control Facility, rerunthe job with a FUNCTION=OP,MSGNUM=301 controlstatement in the DFSYSIN data set. You must supply aSYSUDUMP DD statement in this step.

ModuleDFSPIRP0, DFSUCMN0, DFSUCP40, DFSUC150,DFSUC350, DFSUDMP0, DFSURDB0, DFSURGL0,DFSURGU0, DFSURRL0, DFSURUL0, DFSUTR20,DFSUTR30


DFS302A INVALID OR MISSING FUNCTIONff SPECIFIED ON REQUEST nnnn

ExplanationA utility control statement with an invalid or missingcontrol function code was detected. The ff is eitheromitted or, if present, was not a valid 2-charactercodes. For the valid codes, see information about theUtility Control Facility. The nnnn is the control requestnumber.


Programmer responseCorrect the control statement, depending on the utilityprogram being executed, and resubmit the job. Seeabend code 302.

Problem determination2, 3, 8, 35. Also, if running under theUtility Control Facility, rerun the job with aFUNCTION=OP,MSGNUM=302 control statement inthe DFSYSIN data set. You must supply a SYSUDUMPDD statement in this step. PSB pool should be muchlarger than the CSA PSB pool.

Module:DFSUCP40

Related referenceControl statements for the DFSUCF00 utility(Database Utilities)

DFS0303I xxxx <DYNAMIC BLOCK>

or

THE FOLLOWING BLOCKS WILL BE <DYNAMICALLYFIXED | ALLOCATED IN DREF STORAGE>:

ExplanationAs storage for the block is obtained, the dynamicBLOCKS specified in the DFSFIXnn member of the dataset described by DDNAME=PROCLIB is page fixed. Theblocks specified in the DFSDRFnn member of the dataset described by DDNAME=PROCLIB are allocated ina DREF storage subpool. xxxx is the IMS name of theblock to be page fixed or allocated in DREF storage.

System actionIMS initialization continues.


Module:DFSXFIX0

DFS304A DBD NAME NOT SPECIFIED FORFUNCTION ff ON REQUEST nnnn



http://www.ibm.com/support/knowledgecenter/SSEPH2_15.1.0/com.ibm.ims15.doc.dur/ims_dfsucf00utility.htm#ims_dfsucf00utility

http://www.ibm.com/support/knowledgecenter/SSEPH2_15.1.0/com.ibm.ims15.doc.dur/ims_dfsucf00utility.htm#ims_dfsucf00utility

ExplanationA utility program encountered a control statement withthe DBD name field blank. nnnn is the control requestnumber.


Programmer responseCorrect the control statement to include the DBDname, and resubmit the job. See abend code 0302.

Problem determination2, 3, 8, 35. Also, if running under theUtility Control Facility, rerun the job with aFUNCTION=OP,MSGNUM=304 control statement inthe DFSYSIN data set. You must supply a SYSUDUMPDD statement in this step.

Module:DFSUCP40


DFS305A DBD/PSB LIBRARY DOES NOTCONTAIN DBD/PSB dbdname

ExplanationA utility program was unable to find a DBD/PSB withthe name specified in the utility control statement.


Programmer responseCorrect either the utility control statement or theDD statement specifying the DBD/PSB library, andresubmit the job. See abend code 0302.

Problem determination2, 3, 8, 18, 35. Also, if running under theUtility Control Facility, rerun the job with aFUNCTION=OP,MSGNUM=305 control statement inthe DFSYSIN data set. You must supply a SYSUDUMPDD statement in this step.

Module:

DFSUCMN0, DFSUCP40, DFSUCUM0, DFSURUL0Related informationIMS abend 0302“IMS problem determination” on page 11IMS messages and codes problemdetermination is accomplished by usingprocedures established by IBM.

DFS306A DBD dbdname DOES NOTCONTAIN DDNAME FORFUNCTION ff

ExplanationA utility program attempted to locate the ddnamespecified in the control statement in the DBD dbdnamespecified. The attempt was unsuccessful.


Programmer responseCorrect the control statement in error, and resubmitthe job. See abend code 0302.

Problem determination2, 3, 8, 35. Also, if running under theUtility Control Facility, rerun the job with aFUNCTION=OP,MSGNUM=306 control statement inthe DFSYSIN data set. Supply a SYSUDUMP DDstatement to this step.

Module:DFSUCCT0, DFSUCP40, DFSUCUM0, DFSUDMP0,DFSURDB0


DFS307A NO DDNAME SPECIFIED FOR DATABASE dbdname FOR FUNCTION ff

ExplanationA utility program found a control statement whichrequired a ddname, but did not contain one.






Programmer responseCorrect the control statement, and resubmit the job.See abend code 0302.


Module:DFSPRSDI, DFSUCP40

Related informationIMS abend 0302

DFS308A NO OUTPUT DDNAME SPECIFIEDFOR FUNCTION ff ON REQUESTnnnn

ExplanationA utility program found a control request that requiredan output data set DDNAME in the control statement,but it was not supplied. nnnn is the control requestnumber.


Programmer responseCorrect the control request, and resubmit the job.


Module:DFSUCP40


DFS309A CONTROL STATEMENT ERROR-INVALID/MISSING KEYWORDkeyword

ExplanationA control program either detected a missing keywordthat was required or was not able to identify akeyword.


Programmer responseCorrect the control statement, and resubmit the job.


Module:DFSUCP40


DFS310A INPUT RECORD IMAGE FORddddddddddddd IS IN ERROR ANDFOLLOWS THIS MESSAGE

ExplanationA utility program issues this message after detectingan error in a control statement. The message textidentifies the statement in error. dddddddddddddidentifies the unique data by the utility currentlyrunning to produce a customized message. Thismessage can be issued for the following situations:

• The database did not have to be scanned whenrunning DFSURGSO.

• When running OLIC, the DBD name specified on theinput control statement was not found in a DB PCB inthe OLIC PSB, or the PSB specified LANG=PL/I. OLICrequires LANG=ASSEM.

• The track recovery option was specified for an indexKSDS.


Chapter 10. DFS messages, DFS301A - DFS350A 111


Programmer responseCorrect any errors, and resubmit the job.

Problem determination2, 3, 8, 36. Also, if running under theUtility Control Facility, rerun the job with aFUNCTION=OP,MSGNUM=310 control statement inthe DFSYSIN data set. Supply a SYSUDUMP DDstatement for this step.

Module:DFSUCMN0, DFSUCP40, DFSUCUM0, DFSUDMP0,DFSUICP0, DFSURDB0, DFSURGP0, DFSURGS0,DFSURG10, DFSURRL0, DFSURUL0, DSPLRC10


DFS311A RESTART WAS NOT SPECIFIEDAND NO DFSYSIN DATASETEXISTS

ExplanationThe Utility Control Facility could not locate any controlstatements to determine its processing. It is necessaryto either have a DFSYSIN data set or a "start"parameter.


Programmer responseCorrect the error, and resubmit the job.

Problem determination2, 3, 8, 36. Also, run the job with aFUNCTION=OP,MSGNUM=311 control statement inthe DFSYSIN data set. Supply a SYSUDUMP DDstatement to this step.

ModuleDFSUCP10


DFS312A DDNAME ddname DOES NOTCONTAIN A VALID IMAGEOR REORGANIZED COPY FORFUNCTION RV

ExplanationThe Database Recovery utility was supplied an inputdata set defined by the DDNAME ddname whoseheader record was not of the correct format. An errorof this type can occur when the format of the imagecopy header record does not match that of a currentlysupported release of IMS.


Programmer responseEnsure that the input was correct, or correct it, andresubmit the job. See abend code 302.


ModuleDFSURDB0


DFS313A HD UNLOAD CANNOT BE USEDTO UNLOAD INDEX DATABASE -dbdname

ExplanationThe Hierarchic Direct (HD) Reorganization utilitiescannot be used to unload or reload an index database.

System actionProcessing terminates with a nonzero return code.



Programmer responseThe Hierarchic Sequential (HS) Unload/Reload utilitiesshould be used to reorganize an index database.

ModuleDFSUFGU0

DFS314I TRAP KEYWORD HAS INVALIDPARAMETER

ExplanationThe /TRACE SET ON TRAP command was issued,but the TRAP keyword parameter was missing orinvalid.


Operator response:(master terminal) Check the command format andreenter the corrected command.

ModuleDFSICLN0

DFS315A DEVTYPE MACRO FAILED ONDDNAME ddname FOR FUNCTIONff

ExplanationA utility program issued an SVC 24 (DEVTYPE) toobtain information about an input or output device.The return code indicated that the attempt to do thiswas unsuccessful.


Programmer responseReport this to system operation personnel. See abendcode 0302.


ModuleDFSUCP40, DFSURGP0, DFSURGS0, DFSURGU0,DFSURG10, DFSURUL0


DFS316A DBD dbdname CONTAINS ANUNKNOWN ORGANIZATION CODEcc

ExplanationThe specified DBD dbdname did not contain a validdatabase organization code. The value cc is the code inquestion.


Programmer responseEnsure that the DBD supplied was an IMS DBD. Correctany discrepancies, and resubmit the job. See abendcode 0302.


ModuleDFSUCP40, DFSUDMP0, DFSURDB0, DFSURGU0


DFS317W HEADER RECORD FOR DDNAMEddname NOT FOUND ON DDNAMEddname FOR FUNCTION ff




ExplanationThe utility ff program was supplied an input data setthat was for the proper DBD, but not for the properdata set required.


Programmer responseCorrect the error, and resubmit the job. See abendcode 0302.


ModuleDFSUCP40, DFSURDB0


DFS318A RECORDS FROM DDNAME ddnameARE LARGER THAN DDNAMEddname SUPPORTS.

ExplanationThe utility program was provided an output devicewhose maximum record length was smaller than theinput record length.


Programmer responseChange the specified DD statement device type to adevice capable of handling the input record length, andresubmit the job.

Problem determination2, 3, 8, 36. Also, if running under theUtility Control Facility, rerun the job with aFUNCTION=OP,MSGNUM=318 control statement in

the DFSYSIN data set. Supply a SYSUDUMP DDstatement to this step.

Module:DFSUCP40, DFSURGU0


DFS319A DDNAME ddname HAD APERMANENT I/O ERROR FORFUNCTION ff

ExplanationA utility program encountered an unrecoverable I/Oerror on the named data set.

System actionIf the error occurred on an output volume and multipleoutput copies were specified, the program terminatesin error. For the Database Image Copy 2 utility(DFSUDMT0), message DFS3144A with reason code0E is also issued to identify the database data setsfor which image copy processing has failed. The utilityterminates if there are no other database data sets forwhich image copy processing has not completed.

Problem determination:2, 3, 8, 17g, 36

Module:DFSBCKI0, DFSUCP40, DFSUDMP0, DFSUDMT0,DFSURGU0, DFSURUL0

Related information“DFS3144A” on page 855IMAGE COPY PROCESSING FAILED FOR DB/AREA dbname DDN ddname, REASON = nn“IMS problem determination” on page 11IMS messages and codes problemdetermination is accomplished by usingprocedures established by IBM.

DFS320I DDNAME ddname IS STOPPEDBUT DDNAME ddname CONTINUES

ExplanationA utility program encountered an I/O error on anoutput volume. Two copies were specified. Theprogram continued with the good alternate copy.

System actionProcessing continues with only one output copy.


Programmer responseOne copy of the dumped data set is created. If youwant two copies, ensure that the output units andvolumes are in good working order, and resubmit thejob.


Module:DFSUCP40, DFSUDMP0, DFSURGU0, DFSURUL0


DFS321W FUNCTION ff EXPERIENCED ANERROR AND MUST BE RESTARTED

ExplanationA utility program encountered errors prohibiting thesuccessful completion of the requested operation.


Programmer responseCorrect any errors noted before this message andrerun the failing requests. If running under the UtilityControl Facility, correct the errors and change thePARM= on the JCL to indicate RESTART is needed oradd a control statement to the DFSYSIN data set witha FUNCTION=OP,REQUEST=RESTART. Some utilitiescannot be restarted within their execution.


Module:DFSUDMP0

Related referenceUtility Control Facility (DFSUCF00) (DatabaseUtilities)Related information“IMS problem determination” on page 11IMS messages and codes problemdetermination is accomplished by usingprocedures established by IBM.

DFS322W FUNCTION ff WAS NOT SUPPLIEDAN IMAGE COPY INPUT

ExplanationThe utility ff found the image copy input data setspecified as DD DUMMY.


Programmer responseIf no input was required, no action is necessary.Otherwise, correct the input, and resubmit the job.


Also, if running under the Utility Control Facility,rerun the job with a FUNCTION=OP,MSGNUM=322control statement in the DFSYSIN data set. Supply aSYSUDUMP DD statement to this step.



DFS323W FUNCTION ff WAS NOT SUPPLIEDA CHANGE ACCUMULATION INPUT

ExplanationA utility program found the accumulated change inputdata set specified as DD DUMMY.


Programmer responseIf no input was required, no action is necessary.Otherwise correct the input, and resubmit the job.



http://www.ibm.com/support/knowledgecenter/SSEPH2_15.1.0/com.ibm.ims15.doc.dur/ims_dfsucf00.htm#ims_dfsucf00

http://www.ibm.com/support/knowledgecenter/SSEPH2_15.1.0/com.ibm.ims15.doc.dur/ims_dfsucf00.htm#ims_dfsucf00




DFS324W FUNCTION ff WAS NOT SUPPLIEDAN INPUT LOG FILE

ExplanationThe utility program found the log input data wasspecified as DD DUMMY.


Programmer responseIf no input was required, no action is necessary.Otherwise correct the input, and resubmit the job.


Module:DFSUCP40, DFSURDB0


DFS325A PURGE DATE ON DDNAME ddnameIS LATER THAN DATE ON DDNAMEddname FOR FUNCTION ff

ExplanationA utility found that the purge date specified when theaccumulated change input data set was created waslater than the date the image copy input data set wascreated.


Programmer responseIf any change records were created between thesubject dates and are required for database integrity,the accumulated change input must be recreated andthe recovery job submitted again.




DFS326A DDNAME ddname INPUT IGNOREDDUE TO PURGE DATE ON DDNAMEddname

ExplanationThe Database Recovery utility program found thecreation date of the accumulated change input dataset to be earlier than the creation date of the imagedump data set. Because all records are already on thedump, the accumulated change input data set is notbeing used.



ModuleDFSUCP40, DFSUDMP0, DFSURDB0



DFS327W NO RECORDS ON DDNAMEddname FOR RECOVEREDDATASET

ExplanationA utility program scanned the input data set ddnamefor records applicable to the data set being recovered,but none were found.

Programmer responseEnsure that the input data set was correct. If not,correct the JCL, and resubmit the job.




DFS328A DDNAME ddname REQUIREDBUT WAS NOT SUPPLIED FORFUNCTION ff

ExplanationA utility program found that a required data setddname was not supplied.


Programmer responseSupply the required DD statements, and resubmit thejob.


ModuleDFSUCP40


DFS329A HEADER RECORD ON DDNAMEddname IS NOT CONSISTENTWITH ddname/dbpcb FORFUNCTION ff

ExplanationA utility program encountered an input data set headerrecord whose data set description does not match theDBD description, or the header record of the otherinput data set indicated.


Programmer responseEnsure that all inputs are correct, and resubmit thejob. See abend code 302.



Related informationIMS abend 0302“IMS problem determination” on page 11




DFS330A DDNAME ddname IS OUT OFSEQUENCE FOR FUNCTION ffREASON=r

ExplanationA utility program encountered an OSAM/ESDS recordin the data set ddname whose relative block numberwas lower than the last record update. The reasoncodes and their meanings are:

CodesExplanation

1An ESDS or an OSAM RBN key-sequence erroroccurred.

2A KSDS key-sequence error occurred.

3The log dates are out of sequence (not inascending sequence).

4The date-time in a change accumulation record islater than the date-time in a log record which is tobe merged.


Programmer responseThe input file is in error; re-create it, and resubmit thejob. See abend code 0302.


Module:DFSURDB0


DFS331A DDNAME ddname IS AN EMPTYDATASET BUT SHOULD NOT BE

ExplanationA utility program attempted to read a data set, but gotan immediate end-of-file condition.


Programmer responseEnsure that the appropriate data set was supplied.Correct any error, and resubmit the job.


Module:DFSUCP40


DFS332A OSAM RECORD FROM DDNAMEddname HAS RBN nnnnnnnn ANDIS BEYOND THE CURRENT END OFTHE DATASET

ExplanationThe Database Recovery utility encountered an OSAMrecord in the accumulated change or log input dataset (ddname) that contained an RBN value that wasgreater than the RBN value of the next block afterthe end of the data set. This condition should neverexist under normal operation, because inserts alwaysuse the next sequential RBN value after the end ofthe data set. The most probable cause for this is thatan applicable log data set was not included in eitherthis run or an accumulation run. Another possibilityis that a HISAM reorganization unload was run, thecorresponding reload was not performed, and theunload tape was used as an input to the recoveryprogram.




Programmer responseEnsure that all supplied inputs are correct, andresubmit the job. See abend code 0302.

Problem determination2, 3, 5, 6, 8, 12, 14, 17g, 35. Also, if runningunder the Utility Control Facility, rerun the job witha FUNCTION=OP,MSGNUM=332 control statement inthe DFSYSIN data set. Supply a SYSUDUMP DDstatement to this step.

Module:DFSUCP40, DFSURDB0


DFS333A KEY ID ON DDNAME ddname DOESNOT EXIST IN DDNAME ddnameDATASET

ExplanationThe recovery program encountered a changeaccumulation or a system log record for a KSDS dataset with a key that does not exist in the recovereddata set. This indicates the input supplied was notcorrect. Normal operation requires that if a record onthe change accumulation or the system log is not anentire and complete record, then it must already existin the database data set or the image copy. Thereare two basic reasons this message would be issued.These database errors are commonly caused by usingthe wrong image copy, or because a log data set wasmissed during change accumulation.

• The change accumulation or system log record is fora partial update (indicated by an offset greater thanzero). This record cannot be processed because thedatabase record does not exist.

• The change accumulation record contains changesfor two separate areas in a database record. Thisrecord cannot be processed because the databaserecord does not exist.


Programmer responseEnsure that all input data sets are correct, andresubmit the job. See abend code 302.




DFS334I DDNAME ddname DATASET MAYBE SCRATCHED

ExplanationThe Utility Control Facility has determined that thenamed data set ddname is not required for RESTARTand can be released for other uses.

Programmer responseVerify that this determination is correct, then disposeof data set with normal procedures.


Module:DFSUCPA0, DFSUCP60


DFS335A DDNAME ddname DATASET MUSTBE KEPT IF RESTART IS TO BEUSED

ExplanationThe Utility Control Facility has determined that thenamed data set with the identified ddname is requiredto complete the functions requested in the DFSYSINdata set.




System action:Processing terminates with a nonzero return code.

Programmer responseKeep the named data sets for subsequent RESTART.


Module:DFSUCP00


DFS336I WTOR REPLY REQUESTSTERMINATION, RESTARTMESSAGE WILL BE WRITTEN

ExplanationThe operator replied to the Utility Control FacilityWTOR and specified that the program shouldterminate.

System actionAppropriate messages are written to allow RESTART tobe run.

Programmer responseChange the JCL to allow for the RESTART, andresubmit the job.


Module:DFSUCPA0, DFSUCP60


DFS337A BUFFER POOL TOO SMALL FORFUNCTION ff

ExplanationA utility program requested buffer pool space, butnone was available.


Programmer responseIncrease the buffer pool specification, and resubmitthe job.


Module:DFSUDMP0, DFSURDB0, DFSURGL0, DFSURGU0,DFSURRL0, DFSURUL0


DFS338A DATASET DDNAME ddname IS TOOSMALL FOR FUNCTION ff

ExplanationA utility program attempted to add a record to the dataset ddname, but all available extents were used andunavailable.


Programmer responseIf the data set is HISAM organization, increase thespace allocation. If the data set is HD organization,ensure that input data was correct, and resubmit thejob.

Problem determination2, 3, 8, 36. Also, if running under theUtility Control Facility, rerun the job with a


FUNCTION=OP,MSGNUM=338 control statement inthe DFSYSIN data set. Supply a SYSUDUMP DDstatement to this step.

Module:DFSUDMP0, DFSURDB0, DFSURGL0


DFS339I FUNCTION ff HASCOMPLETED {NORMALLY|ABNORMALLY}{rc=nn|x NO. OFUPDATES=nnnnnnnn}

ExplanationA utility program completed processing. The returncode might not be printed, depending on the utilityprocessing. The letter x indicates the sort phase andis present depending on the utility processing. Thereturn codes for the individual utility programs aredocumented with the information on the utility.

For FUNCTION PU, the NO. OF UPDATES=nnnnnnnnphrase is included, where nnnnnnnn is the count ofrecords on the input DFSURWF3 data set generatedby the Prefix Resolution utility. This count might differbetween identical utility runs under UCF versus non-UCF for some combinations of data and databaseconfigurations.

Problem determination2, 3, 8, 18, 36. Also, if running under theUtility Control Facility, rerun the job with aFUNCTION=OP,MSGNUM=339 control statement inthe DFSYSIN data set. Supply a SYSUDUMP DDstatement in this step.

ModuleDFSUCMN0, DFSUCP40, DFSUCUM0, DFSUDMP0,DFSURDB0, DFSURGL0, DFSURGP0, DFSURGS0,DFSURG10, DFSURPR0, DFSURRL0


DFS340I DATABASE dbdname HAS BEENSUCCESSFULLY {UNLOADED|LOADED|RECOVERED} BYFUNCTION ff [DATASET ddname]

ExplanationThe described function has been completed. Theprinting of DATASET ddname is dependent on theutility being run.


Module:DFSUCP40, DFSURGL0, DFSURGS0, DFSURGU0,DFSURRL0


DFS341A CATASTROPHIC ERROROCCURRED IN DL/I DURINGFUNCTION ff

ExplanationA utility program requested DL/I to perform anoperation on the data set being processed. The PSTreturn code (PSTRTCDE) indicates why the task cannotbe performed.


Programmer responseEnsure that the IMS system and all control statementsare valid, and resubmit the job.


Module:DFSUDMP0, DFSURDB0, DFSURGL0, DFSURGU0,DFSURRL0, DFSURUL0




DFS342I RESTART NOT REQUESTED,NORMAL PROCESSING BEGINS

ExplanationThis message indicates a normal startup for the UtilityControl Facility.



DFS343W DDNAME ddname WAS SPECIFIEDAS DD DUMMY OR WAS OMITTEDFOR FUNCTION ff

ExplanationThe ddname described was flagged as a possible error.ff indicates the name of the function.


Programmer responseVerify that the JCL is correct. If not, correct, andresubmit the job.





DFS344W DDNAME FOR output COPY WAS|WAS NOT SUPPLIED, n COPYREQUESTED FOR FUNCTION ff

ExplanationA utility program was directed by a control statementto create n copies of the output data set but a ddnamewas/was not supplied.


Programmer responseIf one copy was requested, remove the ddname for thesecond copy from the control statement. If two copiesare requested, add the second ddname to the controlstatement. If one copy was requested, but no ddnamewas supplied, supply it, and resubmit the job.


ModuleDFSUCP40, DFSURGU0, DFSURUL0


DFS345I RESTART REQUESTED, RESTARTPROCESSING BEGINS

ExplanationThis message identifies a startup for theUtility Control Facility when the PARM= or aFUNCTION=OP,REQUEST=RESTART control statementin the DFSYSIN data set has requested a RESTART.


DFS346A NO ALTERNATE UNIT AVAILABLEFOR DDNAME ddname FORFUNCTION ff

ExplanationA utility program encountered a permanent I/O erroron an output data set, and no alternate output unit wasavailable.



Programmer responseIf two copies were requested, one copy had alreadyterminated because of an I/O error. There is no validoutput for this execution; therefore, ensure that outputunits and volumes are in good working order, andresubmit the job.



ModuleDFSUCP40, DFSURGU0


DFS347I CONTROL DATASET BUILT ONDDNAME ddname

ExplanationThe Utility Control Facility has constructed the ControlDataset and written it to the data set ddname. Thisdata set is required if a RESTART is needed.

Programmer responseAt the normal termination of the Utility Control Facilityprocessing, this data set can be scratched. If acondition that can be restarted is encountered, thisdata set must be supplied as the DFSOCDS DD dataset.


DFS348A UNEXPECTED RETURN STATUS ssON CALL FROM FUNCTION ff

ExplanationA utility program encountered an unexpected returnstatus after a DL/I call. The ss is replaced by the actualstatus received.




Module:DFSUCP40, DFSURGL0, DFSURGU0


DFS349I ALL FUNCTION TYPE ff REQUESTSCOMPLETED

ExplanationThe Utility Control Facility completed processing allrequests of the stated type. This message provides anadditional cross-check to this processing. It is issuedeven though you did not request any of this type ofprocessing, so you can verify that all functions wereattempted.

Programmer responseIf all messages are satisfied, no further actionis required. If all functions were not completed,change the DFSYSIN data set control statements torequest those functions that were not completed, andresubmit the job. Do not specify RESTART.


DFS350A DATABASE dbname CONTAINS NODATASETS

ExplanationA utility program encountered a DBD that did notcontain any data set groups.



Programmer responseCheck the DBD defining this database. A primary dataset name is required. Correct the error, and resubmitthe job.

Problem determination2, 3, 8, 36. Also, if running under the UtilityControl Facility, rerun the job with a FUNCTION=OP,MSGNUM=350 control statement in the DFSYSIN dataset. Supply a SYSUDUMP DD statement to this dataset.

ModuleDFSUCCT0



Chapter 11. DFS messages, DFS351W -DFS400I


DFS351W DFSYSIN DATA SCANNED FOROPTION REQUESTS ONLY

ExplanationThe Utility Control Facility was restarted. Since the oldcontrol data set defines the functions to be used, thenew DFSYSIN data set is processed for FUNCTION=OPtypes of control requests.


Programmer responseVerify that the processing was indeed to be restarted.If it was, no further action is needed. If it was not,correct the JCL to remove the request for RESTART,and resubmit the job.




DFS352I DFSYSIN DATA OPTIONS HAVEBEEN SUPPLEMENTED WITHDEFAULTS

ExplanationThe Utility Control Facility has augmented theDFSYSIN data set requests with defaults.


DFS353A CONTROL DATASET IS INVALIDOR CONTAINS CONFLICTINGREQUESTS

ExplanationAn error has been detected by the Utility ControlFacility that made the control data set unacceptablefor use. Prior messages define the reason for thiscondition.


Programmer responseCorrect any errors, and resubmit the job. Do notindicate RESTART.




DFS354I NO ERRORS DETECTED. DATABASE RELOAD SUCCESSFUL.

ExplanationThe HD Reorganization Reload Utility has successfullyreloaded the database.

Module:DFSURGL0

DFS355I ERRORS DETECTED. DATA BASERELOAD UNSUCCESSFUL.

ExplanationErrors described in preceding messages haveprecluded the successful reloading of the database.


Programmer responseCorrect the errors, and resubmit the job.

Module:DFSURGL0

DFS356A HEADER RECORD NOT FOUND ONDDNAME ddname FOR FUNCTIONff

ExplanationA utility program found the input data set ddname wasnot a valid data set for this function. The header recordon the input file was invalid or of the wrong format forthe requested processing.


Programmer responseEnsure that the input was correct. If it was, this inputfile is incorrect and must be recreated. After the file iscorrected, resubmit the job. See abend code 0302.


Module:DFSUCP40, DFSUC350, DFSURDB0


DFS357A RESTART FAILURE-DFSOCDS ISNOT READABLE

ExplanationWhen the Utility Control Facility was attempting toperform a RESTART, an error occurred that preventedsuccessful reading of the old control data set.


Programmer responseEnsure that the correct data set was supplied. Movedata set to another device (in the case of I/O errors),and resubmit the job.


Module:DFSUCP40, DFSURUL0


DFS358A INVALID SEGMENT CODE ssFOUND IN DATABASE dbdnameDDNAME ddname ON FUNCTION ff

ExplanationA utility program encountered a segment with aphysical segment code of zero or higher than thehighest segment code in the associated DBD dbdnamedata set ddname. The segment code replaces the ss.


Programmer responseEnsure that the DBD supplied accurately describesthe database. If the data integrity of the databaseis questionable, run the Database Recovery utilityprogram against the database in question, andresubmit the job.







DFS359A RESTART FAILURE-FUNCTION ffNOT FOUND IN DFSOCDS

ExplanationWhen the Utility Control Facility was attempting toperform a RESTART of a function, function ff was notindicated as required in the control data set. Thisproblem does not happen under normal processing.


Programmer responseEnsure that the proper control data set has beenspecified on the DFSOCDS DD statement. Ensure thatthe proper journal data set has been specified on theDFSOJRNL DD statement. Ensure that a RESTART iswanted, and resubmit the job.




DFS360I ERROR-ID CARD ERRORENCOUNTERED

ExplanationThe Change Accumulation utility encountered a controlstatement with a control code of ID that was invalid.


Module:DFSUCCT0

DFS361A DFSNCDS IS NOT READABLE,RESTART NOT POSSIBLE, RE-RUNJOB FROM BEGINNING

ExplanationWhile the Utility Control Facility was attempting towrite or read the new control data set from theDFSNCDS file, an error was detected. This error mightbe either physical device oriented or logical in nature.


Programmer responseIf the processing being done is a RESTART, verifythat the DFSNCDS data set was properly allocated.If the processing was not RESTART, the error wasprobably caused by user-supplied control statementinformation and a prior message will reflect this error.Correct any errors, and resubmit the job.

Problem determination2, 3, 8, 36. Also, if running under theUtility Control Facility, rerun the job with aFUNCTION=OP,MSGNUM=361 control statement in theDFSYSIN data set. Supply a SYSUDUMP DD statementto this step.

Module:DFSUCP40


DFS362I function HAS TERMINATED WITHRETURN CODE nn

ExplanationThe currently running utility has terminated and ispassing return code nn.

Programmer responseIf the return code is zero, no further action is required.If the return code is nonzero, correct any errors, andresubmit the job.

Problem determination2, 3, 8, 36. Also, if running under theUtility Control Facility, rerun the job with a

Chapter 11. DFS messages, DFS351W -DFS400I 127

FUNCTION=OP,MSGNUM=362 control statement inthe DFSYSIN data set. Supply a SYSUDUMP DDstatement to this step.

Module:DFSUCMN0


DFS363A {*ALL|*OTHER} SPECIFIED MORETHAN ONCE FOR FUNCTION CA

ExplanationThe stated parameter was stated more than once. If aDB0 statement is used, you cannot also use a DB1*ALLstatement. Only one DB statement can specify the*OTHER parameter.


Programmer responseCorrect the control statements, and resubmit the job.


Module:DFSUCCT0, DFSUCP40, DFSUCUM0


DFS364W DDNAME ddname SPECIFIEDMORE THAN ONCE

ExplanationA control statement has specified a dbdname/ddnamecombination on more than one control statement.

System actionProcessing continues; the duplicate control statementis ignored.



Module:DFSUCUM0


DFS365A {DDNAME|DBNAME} TABLE HASOVERFLOWED

ExplanationA utility program encountered more ddnames anddbnames than were specified, and the anticipated sizeof the memory table was exceeded.


Programmer responseIf an ID control statement was supplied, increase themaximum ddname and dbname specification. If not,supply one with the correct change, and resubmit thejob.


Module:DFSUCUM0


DFS366A REQUEST nnnn IS A DUPLICATEFUNCTION REQUEST OF REQUESTnnnn AND IS AN ERROR


ExplanationThe Utility Control Facility detected duplicaterequests. The two input control request numbersreplace the nnnn values.


Programmer responseRemove one of the requests, and resubmit the job.


Module:DFSUCUM0


DFS367I UTILITY CONTROL FACILITYRUNNING, ENTER REQUESTS ASNEEDED

ExplanationThe Utility Control Facility has finished initializationand is preparing to run the requested functions. Thismessage is also the WTOR message, and is displayedon the operator console to allow communications withthe running program.

Programmer responseNo action is required unless special termination orstatus information is required.

Module:DFSUCP40, DFSUCUM0

DFS368I ERLG RECORD ENCOUNTEREDFOR DATABASE dbdname DATASETddname ON VOLUME vol. ser. FORFUNCTION CA

ExplanationThe Change Accumulation utility has encountered anError Log Record (ERLG) in the input files. You canconsider track recovery.

Operator responseThe console operator should report this problem to thesubmitter of the job.

Programmer responseNotify Database Management personnel so they candetermine which type of database recovery to use withthis change accumulation data.


Module:DFSUCMN0, DFSUCP40, DFSUCUM0


DFS369I {FUNCTION IS ff [FOR DATABASEdbdname] [DATASET ddname]|INVALID REPLY}

ExplanationThis message is issued in response to the reply to theWTOR of the Utility Control Facility. If an invalid replywas made, the second message is issued.


Module:DFSUCUM0

DFS370W REQUEST nnnn IS NOT REQUIREDAND IS IGNORED

ExplanationA DB Scan, Prefix Resolution, or Prefix Update controlrequest was supplied when it was not required;processing continues.




Module:DFSUCP40


DFS371A A RECORD KEY LENGTH nnn ISLONGER THAN SPECIFIED FORFUNCTION CA

ExplanationAn input record has been encountered with a keylength nnn, which is longer than was specified on an IDcontrol statement, or if no ID statement was supplied,a key longer than 10 bytes was encountered.


Programmer responseSupply an ID control statement with a correct keylength specification, and resubmit the job.


Module:DFSUCCT0, DFSUCUM0


DFS372A DBD dbdname CONTAINS ABLANK DDNAME

ExplanationThe DBD dbdname specified in the text has a primeddname that is blank.


Programmer responseThis error indicates that the DBD specified is a logicalDBD. Correct the control statement specification, andresubmit the job.


Module:DFSUCMN0, DFSUCP40


DFS373A DDNAME DFSUCUM0 IS NOTA VALID OLD CHANGEACCUMULATION DATASET

ExplanationAn old accumulated data set was supplied which didnot have a header record of the correct format.


Programmer responseCorrect inputs, and resubmit the job.


Module:DFSUCMN0, DFSUCP40, DFSUC350




DFS374W WARNING-NO CHANGE RECORDSFOUND ON LOG(S)

ExplanationEither the log input supplied did not contain anyrecords with a log record code of X'50', or all recordswere before the purge date.


Programmer responseEnsure that all inputs are correct. If not, correct inputsand resubmit the job.

Problem determination2, 3, 8, 36. Also:

• If you are running under the Utility Control Facility,rerun the job with a FUNCTION=OP,MSGNUM=374control statement in the DFSYSIN data set. Supplya SYSUDUMP DD statement to this step.

• If you are running change accumulation because youreceived message DSP0281I, update the RECON toshow that the change accumulation was performed.

Module:DFSUCMN0, DFSUCP40, DFSUCUM0

Related informationDSP0281I (Messages and Codes)“IMS problem determination” on page 11IMS messages and codes problemdetermination is accomplished by usingprocedures established by IBM.

DFS375A DFSOJRNL IS NOT CONSISTENT,RESTART NOT POSSIBLE

ExplanationThe Utility Control Facility determined that the inputold journal data set is not correct, or is not proper forthe associated DFSOCDS data set.


Programmer responseEnsure that the proper input files are supplied, andthat a RESTART is to be done, and resubmit the job.


Module:DFSUCP40


DFS376A AN APPARENT SORT SEQUENCEERROR HAS BEEN DETECTED

ExplanationA record has been received at SORT EXIT 35, which isof a lower sequence than the last record received. Thisis an internal system error.



ModuleDFSUCMN0, DFSUCP40


DFS377A CHECKPOINT INPUT INVALID ONDDNAME ddname FOR FUNCTIONff


http://www.ibm.com/support/knowledgecenter/SSEPH2_15.1.0/com.ibm.ims15.doc.msgs/msgs/dsp0281i.htm#dsp0281i

ExplanationA utility program was supplied a restart data set thatwas not of proper format.


Programmer responseIf a RESTART was not required, remove the DDstatement DFSURSRT. If a RESTART was required,ensure that the DD statement is correct, and resubmitthe job. If the DD statement was correct, thecheckpoint data set has been destroyed and cannotbe used. RESTART the job from the beginning.




DFS378I CHECKPOINT RESTARTSUCCESSFULLY POSITIONED FORFUNCTION ff

ExplanationThe Utility Control Facility has successfully positionedinput, output, and database files.




DFS379I ERRORS DETECTED-CHECKPOINTRESTART UNSUCCESSFUL

ExplanationThe checkpoint restart attempt was unsuccessfulbecause of conditions described by precedingmessages.

Programmer responseIf the error encountered can be corrected, correct theerror and resubmit the job. Otherwise, restart the jobfrom the beginning.

Module:DFSURGU0

DFS380A UNABLE TO POSITION DATABASEdbdname FOR FUNCTION ff

ExplanationWhile attempting to position database dbdname, autility program could not locate the checkpointedsegment.


Programmer responseEnsure that all DD statements are correct and thedatabase has not been changed between the originalunload and the RESTART attempt. If corrections canbe made, resubmit the job. Otherwise, restart the jobfrom the beginning.




DFS381I CHKPNTnnnn, {*****|vol1},{*****|vol2}, segname


ExplanationThe system writes this message to the console everytime a checkpoint is taken by the HD ReorganizationUnload utility program.

In the message text:nnnn

A decimal value 1 - 9999, incremented by 1 forevery checkpoint taken

vol1The current primary output volume serial numberor asterisks indicating that the primary outputvolume is not in use

vol2The current secondary output volume serial orasterisks indicating that the secondary outputvolume is not in use

segnameThe segment name of the segment being retrievedwhen the checkpoint was taken


Module:DFSURGU0

DFS382A DBD dbdname IS NOT A VALIDDBD FOR THIS FUNCTION ff

ExplanationThe DBD dbdname supplied on a control statementwas used to load a DBD. Upon examination of theDBD, it was discovered that the DBD was not a validIMS DBD, or it was a HALDB and the utility does notsupport HALDBs


Programmer responseEither correct the control statement, or if the controlstatement is correct, replace the DBD with a valid IMSDBD.


Module:

DFSUCP40, DFSURUL0Related information“IMS problem determination” on page 11IMS messages and codes problemdetermination is accomplished by usingprocedures established by IBM.

DFS383A INPUT RECORDS ARE NOTIN SEQUENCE FROM DDNAMEddname FOR FUNCTION ff

ExplanationA root segment has been encountered with asequence field (key) equal to or lower than theprevious root segment processed.

System actionExecution is terminated.

Programmer responseIf the abend option was specified and a SYSUDUMP orSYSABEND DD statement was provided, abend 0359 isissued, and a storage dump was produced. Register 11at entry to abend is the address of the current key, andregister 9 is the address of the previous key.




DFS384A PROCESSING OF LAST UCFREQUEST COMPLETED-RESTARTNOT ALLOWED

ExplanationThe Utility Control Facility has completed all requestssuccessfully. Since normal completion has beenachieved, RESTART is not allowed.


http://www.ibm.com/support/knowledgecenter/SSEPH2_15.1.0/com.ibm.ims15.doc.msgs/msgs/0359.htm#kf00177



Module:DFSUCP40


DFS385A WORK AREA EXCEEDED IN FIELDname FOR REQUEST nnnn

ExplanationThe Utility Control Facility was processing a requestfrom the DFSYSIN data set when the field name in theDFSUCP70 work area overflowed.


Programmer responseToo many parameters were specified on the controlrequest nnnn. Make multiple control requests to do thesame function as the one in error. This action shortensthe overall length of the table requirements and stillperform the required function. Resubmit the job; donot perform a RESTART.


Module:DFSUCP40


DFS386A A PREMATURE EOF WASENCOUNTERED ON DDNAMEddname

ExplanationThe utility program was reading an input file whenit reached the End of File. This condition was notexpected at that precise time, and is therefore anerror.


Programmer responseEnsure that the data set is complete, and resubmit thejob.




DFS387I ERROR-NO VALID RECORDS ONINPUT DATASET

ExplanationThe input data set to the HD Reorganization Reloadprogram contained no valid unloaded databaserecords. The return code is 16.

Programmer responseCorrect the invalid input, and resubmit the job. Ensurethat the HD unload was successful and that theunloaded data set is valid. It might be necessary torerun the unload program to re-create the input for thereload before resubmitting the job.

Module:DFSURGL0

DFS388A DDNAME ddname DID NOT HAVEA STATISTICS RECORD FORFUNCTION ff


ExplanationA utility program was processing an input file ddname,and expected to find a statistics record.


Programmer responseIf "NSTAT" was specified on HISAM unload, specifyOPTIONS=(NSTAT) in the SYSIN data set for HISAMreload. Correct any errors, and resubmit the job.




DFS389W PROCESSING FOR THE{FOLLOWING | PRECEDING}REQUEST HAS TERMINATED{ABNORMALLY | NORMALLY}

ExplanationThis informational message is issued to tell the userhow a request completed.

System actionProcessing terminates normally or abnormally asindicated in this message.

Programmer responseIf an abnormal termination has occurred, correct theerrors printed prior to this message, and resubmit thejob. If a normal termination has occurred, no furtheraction is necessary.



ModuleDFSUCP40, DFSURGL0


DFS390A DDNAME ddname HAS ANINVALID LOGICAL RECORD FORFUNCTION ff

ExplanationThe issuing program encountered one of the followingerrors:

• The input record is not a valid type. The validtypes are 00 (logical parent), 10 (logical child), 60(dummy), and 80 (checkpoint).

• While processing a type 00 or type 10, an invalidlogical description exists in the DBD.

• During input processing of work file data sets, a workfile record was found that contains a segment notfound in the segment descriptor blocks (SDB).

In the first two cases, the work file record is printed foreach occurrence of the invalid condition. In the thirdcase, the work file record is printed once and the jobterminates. This work file record is from the specifieddata set on the DFSURWF3 DD statement. The recordis printed in hexadecimal with EBCDIC translation.


Programmer responseEnsure that the complete log data set file is suppliedas input, and resubmit the job.


Module:DFSUCMN0, DFSUCP40




DFS391I This message is variable

ExplanationAnytime a utility must print a general message, it usesthis message. No warning or error message uses thisnumber.


Module:DFSUARC0, DFSUARP0, DFSUCCT0, DFSUCP40,DFSUDMP0, DFSUICP0, DFSURDB0, DFSURRL0,DFSULG20, DFSUPNT0


DFS392A DUPLICATE NAMES nameSPECIFIED ON CONTROLREQUEST FOR FUNCTION ff

ExplanationThe control statement contains duplicate datadefinition names (ddnames). This condition wouldhave caused a system abend 0013.


Programmer responseThe control request in error is flagged on the outputprinter. Correct the error, and resubmit the job.


Module:DFSUCMN0, DFSUCP40, DFSUDMP0


DFS393A BLDL FAILED FOR MODULEcccccccc

ExplanationThe module listed, cccccccc, was not found when theBLDL macro searched the PDS directories for STEPLIB,JOBLIB, SYS1.LINKLIB.

System actionProcessing stops for the utility.

Programmer responseVerify that the JCL specifies the correct libraries andthat the module is in one of the program libraries.Rerun the job.

Problem determination1, 2, 3, 4, 8, 12, 36. Also, if running underthe Utility Control Facility, rerun the job with aFUNCTION=OP,MSGNUM=393 control statement inthe DFSYSIN data set. Supply a SYSUDUMP DDstatement to this step.

Module:DFSUCF00, DFSURDB0

Related referencez/OS: BLDL completion codesRelated information“IMS problem determination” on page 11IMS messages and codes problemdetermination is accomplished by usingprocedures established by IBM.

DFS394A AN RBA SEQUENCE ERROROCCURRED FOR FUNCTION ff

ExplanationA utility program was reading an ESDS, and thereturned relative byte address (RBA) of the record wasnot higher than the prior one.




https://www.ibm.com/support/knowledgecenter/SSLTBW_2.1.0/com.ibm.zos.v2r1.idad500/d5010.htm

Programmer responseThe database is in error. Recovery of the data setis required. Use the Database Recovery utility toaccomplish this recovery.


Module:DFSUDMP0, DFSURDB0


DFS395I BACKOUT COMPLETE FOR PSBpsbname [TO CHKPT chkptid] [FORREGION regid]

ExplanationThe Database Backout utility successfully completedthe requested database backout. If the CHKPT optionwas specified in the SYSIN data file, TO CHKPTchkptid identifies the checkpoint to which the backoutwas completed, and FOR REGION regid identifies theregion in which the PSB was running. (default=01)

Operator response:Record the checkpoint number and the volume serialnumber in case a restart action must be requested.

Problem determination:1, 2, 3, 5, 8, 11, 17a, 17d, 17g, 20, 36

Module:DFSBACK0, DFSRDBC0


DFS396I SYSTEM ERROR DURINGBACKOUT OF DATA BASE dbnamePROGRAM psbname

ExplanationThe Database Backout utility was unable to locatea data management block directory entry for thedatabase specified.

Programmer responseThis problem indicates that the PSB used for backouthas changed since the original run. Check the PSBrequested in the EXEC statement to ensure that thename and the PSB are correct. Correct any errors, andrerun the job.




DFS397I BACKOUT UNABLE TO OPEN DATABASE dbname PROGRAM psbname

ExplanationThe Database Backout utility was unable to open thespecified database.

Programmer responseCheck the DD statements to ensure that they arepresent and identify the data sets properly. Correctany errors, and rerun the job.




DFS398I I/O ERROR DURING BACKOUT INDATA BASE dbname PROGRAMname

ExplanationThe Database Backout utility encountered an I/O errorwhile attempting backout on the specified database.

Programmer responseRun the Database Recovery utility against thedatabase in error. Use all log data sets, including theoutput of this backout attempt. Then rerun the backoutjob.





DFS399I BUFFER POOL TOO SMALL FORBACKOUT OF DATA BASE dbnamePROGRAM psbname

ExplanationThe database buffer pool was too small toaccommodate the database specified while attemptingto run the Database Backout utility.

Programmer responseIncrease the database buffer pool size in the EXECstatement, and rerun the job.




DFS400I BATCH BACKOUT UNABLE TOOPEN THE INPUT LOG ddname

ExplanationThe Batch Backout utility (Database utility) wasunable to open the log data set specified by ddnameIMSLOGR or IMSLOGRx.

System actionThe Batch Backout utility, DFSBBO00, terminates witha return code of X'14'.

Programmer responseCheck the DD statement, correct any errors, and rerunthe job.

Problem determination1, 2, 3, 5, 8, 11, 17a, 17d, 17g, 20, 36

ModuleDFSBACK0, DFSBCKI0



Chapter 12. DFS messages, DFS401I - DFS0450I


DFS401I DBRC CALL FAILURE - RETURNCODE = xx - CALL = yyyyyy

ExplanationThe Batch Backout utility received an unexpectedreturn code from DBRC. yyyyyy is the call made toDBRC, and xx is the return code from DBRC.

System actionIf the call identified in the message is SAVUOR,LOGSET, or VERUOR, the batch backout jobterminated. If the call is UPDUOR, INIT, or EOJ, therequired changes have been successfully backed outof the databases associated with the PSB for which theBatch Backout utility was being run.

Programmer responseIf the call identified in the message is SAVUOR,LOGSET, VERUOR, or UPDUOR, contact IBM forproblem determination assistance.

If the call is INIT or EOJ, see one of the followingreturn codes:

Code (hex)Explanation

08The IMS subsystem for which backout was beingperformed was not authorized to use one or moreof the databases that had changes backed out.

A previous error might have caused the loss ofthe database authorization. Determine the causeof any previous errors. Otherwise, the DBRC EOJcall has failed and the RECON data set might needupdating.

2CAn internal DBRC error occurred. DBRC was notable to access the RECON data set. Ensure that theappropriate DD statement for the RECON data setis available.

30The parameters passed to DBRC were invalid.The RECON data set must be updated manually.Contact IBM for problem determination assistance.


Module:

DFSBACK0Related information“IMS problem determination” on page 11IMS messages and codes problemdetermination is accomplished by usingprocedures established by IBM.

DFS0401I DBRC CALL FAILURE - RETURNCODE = xx - CALL = yyyyyy

Explanation:See DFS401I

Related information“DFS401I” on page 139DBRC CALL FAILURE - RETURN CODE = xx -CALL = yyyyyy

DFS0402 DATABASE dbname NOT STARTEDDUE TO RECOVERY NEEDED.

ExplanationWhile processing a /START DB command, the systemfound that a deferred backout was required for thedatabase, dbname. A verification of this backout usingDBRC (to ensure that the backout was not done bybatch backout utility) found that the database firstrequires forward recovery. This condition occurs duringthe first active start after a remote takeover. Theshadowed database was not authorized to the trackingsystem at the time of the takeover while the copy ofthe active was updated before takeover.

System actionThe database is not started and the backout is notdone.

User responseForward recover the database; then reissue the startcommand.

Module:DFSDBDR0

DFS0403W IMS xxxxxxxxx CALL TO MVSARM FAILED - RETURN CODE=nn,REASON CODE=nnnn.


ExplanationA call to the z/OS Automatic Restart Manager (ARM)failed. The message text contains the type of call,represented by xxxxxxxx, and the return and reasoncodes. Values for xxxxxxxxx are:REGISTER

Register with the z/OS ARM.READY

Notify the z/OS ARM that IMS is ready to acceptwork.

ASSOCIATENotify the z/OS ARM that this is an XRF alternate ora Fast DB Recovery region.

UNKNOWNAn unknown request value was passed toDFSARM00.

System actionIMS ignores the return code and continues running.

Programmer responseTo determine the reason for the failure, check theIXCARM return and reason codes. Then, correct theproblem.

Module:DFSARM00

Related referencez/OS: IXCARM return and reason codes

DFS0404W INCONSISTENT ACBLIBSPECIFICATION - IMSACBx -CODE=yyy-zzz

ExplanationThe DL/I subordinate address space option wasselected. The ACBLIB specification in the IMSprocedure did not match the correspondingspecification in the DL/I subordinate address spaceprocedure. The message indicates the DDNAME inerror, either IMSACBA or IMSACBB. yyy is defined asfollows:

CodesExplanation

001The number of data sets specified for the DDNAMEwas not the same. zzz does not apply.

002The number of data sets was the same. However,the data set names and volume serial number didnot match. zzz identifies the data set specificationin error. For example, if zzz is 002, the second data

set specified for IMSACBx is not the same in bothprocedures.

003IMSACBx represents the inactive ACBLIB. ThisDDNAME was defined in one procedure, but notin the other. To use the online change function,the inactive ACBLIB must be defined in bothprocedures. zzz identifies the procedure missingthe specification: 001 for the IMS procedureand 002 for the DL/I subordinate address spaceprocedure.

004The DD statement for the IMSACBA or IMSACBB ismissing.zzz can be:

001 - DD statement missing from the IMSprocedure002 - DD statement missing from the DL/I SASprocedure

System actionIf yyy is 1 or 2, the DL/I subordinate address spaceabends with 0023, causing the control address spaceto abend with 0150. If yyy is 3, initialization continues.

If yyy is 004, IMS terminates abnormally with abendcode 0023.

Programmer responseIf yyy is 1 or 2, correct the specification for theindicated DDNAME. The data sets specified and theirconcatenation order must be identical in both the IMSand DL/I address space procedures. If yyy is 3, andyou intend to use the Online Change function, cancelthe control region and supply the missing specificationfor the inactive ACBLIB.

If yyy is 004, correct the specification for the indicatedDDNAME.

Module:DFSSDLC0

DFS0406A AN ERROR OCCURRED DURINGAUTHORIZATION PROCESSINGFOR DATABASE xxxxxxxx. RETURNCODE = yy. PSB=zzzzzzzz

ExplanationIMS was unable to obtain database authorization forthe named database, which appears in one of the DBPCBs contained in the named PSB. The PSB name onlyappears in the message text if the failure occurred fora call from an online application.

The return code (hex)yy can have the following valuesand meanings.


http://www-01.ibm.com/support/knowledgecenter/SSLTBW_2.4.0/com.ibm.zos.v2r4.ieai700/ieai70037.htm?lang=en

Code (Dec)Meaning

01During the authorization of a HALDB partition,the partition was found to be allocated and notauthorized. The partition must be deallocatedbefore authorization can be done but deallocationfailed. Look for deallocation failed messages,DFS2503W, for the reason why and make anynecessary changes. Then run the job again.

System actionThe application terminates with either a BA statuscode, if the program has issued an INIT STATUSGROUPA call. It terminates with or an abend 3303, ifthe program has not issued the INIT call.

Programmer responseTake the appropriate action for the return code.


Module:DFSDBAU0

Related informationDFS2503WDYNAMIC action_type FAILEDFOR DATA SET NAMExxxxxxxx.xxxxxxxx.xxxxxxxxDATABASE NAME dbdname REASON CODEyyyyy3303 (Messages and Codes)“IMS problem determination” on page 11IMS messages and codes problemdetermination is accomplished by usingprocedures established by IBM.

DFS0407I REGION TOO SMALL

ExplanationModule DFSILTA0 was unable to get enough storage tobuild queue entries.

System actionDFSILTA0 terminates abnormally with abend 0407.

Programmer responseRerun the job in a larger region or code the ST=parameter on the EXEC statement to process a shortertime.

Module:

DFSILTA0Related information0407 (Messages and Codes)

DFS0408I INVALID 'ST' PARAMETER.

ExplanationThe EXEC statement had an invalid ST parameter.

System actionThe Log Transaction Analysis program, DFSILTA0,terminates abnormally with abend 0415.

Programmer responseCorrect the parameter on the EXEC statement, andresubmit the job.

Problem determinationCheck the format of the EXEC statement parametersfor the Log Transaction Analysis utility.

Module:DFSILTA0


DFS0409I INVALID 'OUT' PARAMETER.

ExplanationThe EXEC statement had an invalid OUT parameter.

System actionThe Log Transaction Analysis program, DFSILTA0,terminates abnormally with abend 0415.

Programmer responseCorrect the parameter in the EXEC statement, andresubmit the job.

Problem determinationCheck the format of the EXEC statement parametersfor the Log Transaction Analysis utility.

Module:DFSILTA0


DFS0410I END OF FILE ON LOG DATASET

Chapter 12. DFS messages, DFS401I - DFS0450I 141





ExplanationThe end-of-file has been reached on the input log dataset.

System actionThe Log Transaction Analysis program, DFSILTA0,terminates normally.

Module:DFSILTA0

DFS0411I DDNAME OPEN FAILED.

ExplanationOPEN failed for the data set defined by the ddname inthe message. Register 11 points to the DCB of the dataset.

System actionDFSILTA0 terminates abnormally with abend 0411.

Programmer responseCorrect the JCL, and resubmit the job.

Problem determinationCheck the DCB and DD statement.

Module:DFSILTA0


DFS0412I MISSING 08 RECORD

ExplanationThe Log Transaction Analysis program, DFSILTA0, wasunable to connect a termination record (X'07') with aprior schedule record (X'08').

System actionDFSILTA0 continues processing. Any transactionsassociated with the X'08' record application programschedule is ignored.

Problem determination:This problem is a probable IMS error. 1, 2, 3, 8, 25, 36

Module:DFSILTA0



DFS0413I INCORRECT LOG DATASETxxxxxxxx - DISCARDED RC=zz

ExplanationThe DD statement xxxxxxxx for the log data set wasincorrectly specified. The error was caused by one ofthe following:

• A DD DUMMY or DSN=NULLFILE was specified.• The specified secondary log data set is not used,

because the log recording mode is single.• The required primary or secondary partner for OLDS

ddname was not specified. The log recording modeis dual, and the online log data sets (OLDS) must bespecified in pairs (primary and secondary).

• For a batch program, the DD statement wasincorrectly specified.

• For an online program, DUAL log recording modewas requested. The allocation for the primary OLDSwas successful, but the allocation for the secondaryOLDS failed.

• The attributes were incorrectly specified when theDD name specifies a write-ahead data set (WADS).

The reason code zz can have the following values andmeanings:Code (Dec)

Meaning04

Allocation failed for DDNAME=xxxxxxxx for one ofthese reasons:

• No DFSMDA member was found, and the DDstatement was not found in the JCL stream.

• If message DFS2503W is also received, seeDFS2503W for the reason for the allocationfailure.

08OLDS/WADS device was not DASD.

12DEVTYPE failed for DDNAME=xxxxxxxx.

16DDNAME=xxxxxxxx was specified as DD DUMMY orDSN=NULLFILE.

20RDJFCB failed for DDNAME=xxxxxxxx.

28OBTAIN failed for the data set defined byDDNAME=xxxxxxxx.



32OLDS block size was not a multiple of 2K.

36Dual OLDS was specified, and the secondary OLDSblock size (DFSOLSnn) was different from theprimary OLDS block size (DFSOLPnn).

40The OLDS block size was less than thelargest OLDS block size (DFSOLPnn,DFSOLSnn)successfully allocated.

44The WADS device type was inconsistent (distinct).

48The OLDS block size was greater than the trackcapacity.

52BUFSTOR=64 was specified on the OLDSDEFstatement, but this OLDS was not an extendedformat data set.

56The WADS is smaller than 5 tracks.

60The IMS Logger received a nonzero return codefrom the DFSMS Media Manager when the loggerconnected to a WADS by using a CONNECT(OPEN) command. The most common reason forthis error is that the WADS is not a VSAM data set.

64The WADS CI size was not 4 KB

System actionThe DD error statement is discarded and systeminitialization continues. If DUAL is requested and anerror exists in an OLDS pair, the OLDS pair is discarded.System initialization continues.

Programmer responseCheck the DD statement and correct any errors so thatthe data set will be available the next time the systemis initialized.


Module:DFSFDLS0, DFSXLGI0

Related information“DFS2503W” on page 719DYNAMIC action_type FAILEDFOR DATA SET NAMExxxxxxxx.xxxxxxxx.xxxxxxxxDATABASE NAME dbdname REASON CODEyyyyy

“IMS problem determination” on page 11IMS messages and codes problemdetermination is accomplished by usingprocedures established by IBM.

DFS0414I CONTINUING WITH ALTERNATELOG

Explanation

or

PERMANENT I/O ERROR ON ddname - DURING LOGzzzz xx

ExplanationEither form of this message can be issued. Thefirst message indicates that a permanent I/O erroroccurred in the log data set specified by the ddname.The log data set is either an online log data set (OLDS),a write-ahead data set (WADS), or a batch system logdata set (SLDS). The value of zzzz is WRITE or READ.

The second message indicates that the systemcontinues with an alternate log data set.

For WRITE errors, xx is an invalid DECB post code,which is contained in the first byte of the ECB (ECBCC).No xx value with a WRITE error indicates that a logdata set CLOSE error occurred during EOV processing.

For READ errors, xx is an OSAM error return code.

The values and meanings of xx are as follows:


01DD statement missing.

02Concatenated data set.

03Fewer units than volumes specified for a DASDdata set.

04JCL specified a DSORG type not permitted byOSAM.

05DSCB for data set not found.

06First volume DSCB specified a DSORG type notpermitted by OSAM.

07DCB block size not equal to DSCB block size afterJFCB/DCB merge.


08DCB LRECL size not equal to DSCB LRECL size afterJFCB/DCB merge.

09Neither the LRECL nor block size was specified inthe DSCB, DCB, or JCL.

0AThe specified block size is less than LRECL.

0BThe specified block size exceeds track size for thespecified device.

0CA previous OPEN or EOV failed.

0DVIO not supported by OSAM. The data set isallocated to a VIO unit.

0ETape devices are not supported. The data set isallocated to a tape device.

0FSome internal error occurred in the OSAM DEBsubroutine. DCBWRK1 indicates the error code.

10Block size greater than track size.

If an error is detected by IOS, the message textmight also contain I/O completion codes. For moreinformation, see the IOSCOD field in z/OS: IOSBmapping.

If hardware errors occur, see the z/OS IOS000Imessage issued before this message.

System actionIMS continues execution with a spare WADS(DFSWADSn, n=0,1,...9), if one is available. If nosuch WADS exists, IMS continues logging in adegraded mode by truncating log buffers to ensure thepreservation of Log-Write Ahead Protocols (LWA).

One of the following occurs for the other WRITE errorcases:OLDS

IMS continues execution if 2 or more OLDSremain. If only one OLDS remains, an internalCHECKPOINT FREEZE is performed. If no OLDSremains, IMS abends with abend 0616.

SLDSIMS continues execution if dual logging is in effectand an alternate SLDS exists. If an alternate SLDSis unavailable, IMS abends with abend 0616.

Operator responseIf the error occurs on an OLDS and dual logging wasnot being used, or if errors occur on both copies ofa dual OLDS log, then run the Log Recovery utility toclose the OLDS in error.

For an invalid DECB post code with no associatedhardware error, set a SLIP to capture a memory dumpat the next message occurrence and contact IBMSoftware Support.

If an error IOS002A occurred indicating no pathswere available to the allocating device and CLOSEprocessing also involving an I/O request is started, theCLOSE might still appear hung. Issue V OFFLINE tothe UCB.

Module:DFSFDLS0

Related referencez/OS: IOS000IRelated informationIMS abend 0616

DFS0415W PARTITIONED DATABASE INIT| TERM | START EXCEPTIONCONDITION - FUNC= ffffffff,DBNAME= dddddddd, PARTNAME=pppppppp, REASON= rr

ExplanationAn error occurred during the INIT, TERM, or STARTprocessing of a HALDB structure.

In the message text:ffffffff

The keyword specifying the INIT, TERM, or STARTfunction that encountered the error. ffffffff is one ofthe following:SYS DDIR

System initialization of HALDB DDIR structuresSYS DMB

System initialization of HALDB DMB structuresSEL DMB

System initialization of a selected HALDB DMBstructure

PART DBInitialization of a HALDB (DDIR and DMBstructures)

RBLD PDBReinitialization of a HALDB name table

PART DBTermination of a HALDB structure


https://www.ibm.com/support/knowledgecenter/en/SSLTBW_2.2.0/com.ibm.zos.v2r2.iead200/iead200672.htm

https://www.ibm.com/support/knowledgecenter/en/SSLTBW_2.2.0/com.ibm.zos.v2r2.iead200/iead200672.htm

http://www-01.ibm.com/support/knowledgecenter/SSLTBW_2.4.0/com.ibm.zos.v2r4.ieam900/m012917.htm%23m012917?lang=en


PART DDIRCommand initialization of a partitioned DBDDIR structure

PART DMBCommand initialization of a partitioned DBDMB structure

ddddddddIdentifies the database that encountered the error.

ppppppppIdentifies the partition in dddddddd thatencountered the error. If the error pertains to thedatabase in general, the partition name is specifiedas N/A.

rrThe reason code identifies the cause of the error:Reason code

Meaning01

Invalid function code02

Unable to allocate XPARTW storage03

Database DDIR not found04

Database not defined as partitioned05

HALDB not initialized. Master HALDB is offline.The database might not have been initializedor it might have been taken offline with a /DBRECOVERY command. Use /DIS DB or QRYDB NAME() SHOW(ALL) to view the databasestatus.

06Unable to allocate storage stack area

07Invalid database organization

08Inconsistent database organization

09Invalid STR modification state

10Unable to allocate part list storage

11Unable to allocate DFSPNT storage

12Unable to allocate part DDIR

13Unable to allocate part DMB

14Unable to allocate part DCB

15Unable to allocate ILE ACB

16Unable to allocate DBRC name list

17Unable to allocate part unique storage

18Unable to allocate PHIDAM index ACB

19Failed to obtain storage for the databasedirectory extension block

20Unable to load selection exit

21Selection exit not linked reentrant

22Unable to locate selection exit

30Unable to allocate DFSPTX storage

31Unable to allocate DFSPTK storage

32Unable to allocate DFSPDA storage

40Partitioned database DDIR not inactive

41Partition DDIR not inactive

43Partitioned database DMB not initialized

44Duplicate database name DDIR encountered

45Unable to load dfsdt150

46Exceeded the maximum of 32,767 datamanagement blocks (DMB)

50No HALDBs found

51Partitioned structure not required

60Partitioned database DDIR list not found

61Unable to deallocate part data set

70Unable to allocate DXPXDLIL storage

71DBRC query error

72No partition data returned by DBRC


73Target partition data not found by DBRC

74DBRC not active

75The specified non-registered HALDB is not acatalog database. The HALDB structure is notbuilt and the HALDB is not usable.

76The DFSHDBSC data set does not containinformation for the structure of the specifiedHALDB.

77An error occurred while building the non-registered database structure.

83An error occurred during a Resource Manger(RM) query. Global status for the newly addedpartition was not applied.

90Warning, partition precluded from rebuild.

91The partition DDIR block cannot be dequeuedfrom the DDIR chain because working storagecannot be obtained.

92The partition DDIR block is no longer beingused and is removed from the DDIR chain.

93The partition is deleted because the HALDBmaster was deleted by online change.

99Error encountered for one or more databases.

System actionPartition structure processing terminates with anonzero return code.

System programmer responseDetermine the cause of the failure as indicated bythe reason code rr returned in the message text. Takeappropriate measures to correct the problem based onthe reason code explanation.


Module:DFSPSM10


IMS messages and codes problemdetermination is accomplished by usingprocedures established by IBM.0880 (Messages and Codes)

DFS0416I INITIALIZATION FAILED-(E)STAEERROR

ExplanationIMS initialization was unable to establish the IMS(E)STAE environment.


Module:DFSXCIC0, DFSXLGI0


DFS417I PAGE FREE FAILED.

ExplanationDuring STAE exit processing, module DFSFCST0attempted to free the page contained in the page fixlist and was unsuccessful. The page free list address islocated at label SCDFIX in the SCD.

System actionAfter issuing the message, STAE exit processingcontinues.

Problem determination1, 4, 5, 6, 8, 11, 36

ModuleDFSFCST0


DFS418A PSB IS NOT AUTHORIZED FOR ON-LINE IMAGE COPY

ExplanationThis message occurs if the PSB specified by the userwas generated without the OLIC=YES option on thePSBGEN macro.




System actionThe utility ends with a return code of 16.

Programmer responseEither correct the PSB or use a PSB with the optionproperly specified.

Module:DFSUICP0

DFS0420A DBD dbdname STOPPED ---PREVIOUS WRITE ERRORDETECTED.

ExplanationRestart processing found a database that previouslyincurred a write error. If you recovered the database,issue a /DBR DB dbdname, UPDATE DB NAME(name)STOP(ACCESS)1, /START DB, or an UPDATE DBSTART(ACCESS) command. If you did not recover thedatabase, it must be recovered before the database isrestarted or the data integrity can be lost.1 These commands do not automatically issuecheckpoints unless OPTION(FEOV) is specified.


Operator response:(master terminal) Notify the system programmer.If the database has been recovered before restart,start the database with the /DBR and /STARTDB commands or UPDATE DB NAME(dbdname)STOP(ACCESS) and UPDATE DB NAME(dbdname)START(ACCESS). If recovery has not been done,wait until recovery is performed before starting thedatabase.

Programmer responsePerform a database recovery before IMS restart.Ensure that the database has been recovered beforerestarting it.


Module:DFSRST00, DFSSDL40


DFS421I UNABLE TO OPEN SYSPRINTDATASET, JOB TERMINATED.

ExplanationA DD statement for the SYSPRINT data set was notsupplied to the SYSOUT print utility (DFSUPRT0).This message is printed using the z/OS Write-To-Programmer facility (return code = 8).


Module:DFSUPRT0

DFS422I I/O ERROR WRITING SYSPRINTDATASET, JOB TERMINATED.

ExplanationA permanent I/O error occurred while the SYSOUTprint utility was writing to the SYSPRINT data set.This message is printed using the z/OS Write-To-Programmer facility (return code = 0C).


Module:DFSUPRT0

DFS423I jobname, stepname, dev addr, DA,ddname, GET, status, disk addr,QSAM

ExplanationAn I/O error occurred while processing a spoolSYSOUT data set in the print utility DFSUPRT0. Thedata set was CLOSED and processing continued withthe next.

The information in this message is obtained fromthe SYNADAF z/OS macro. In a batch environmentrunning DFSUPRT0, the fields in the message and theirmeanings are the following:jobname

Label on the JOB JCL statementstepname

Label on the EXEC JCL statementdev addr

Hardware address of the device where the data setresides

DADirect Access


ddnameLabel on the DD JCL statement for the data set

GETQSAM operation that encountered the error

statusError description

disk addrActual track address and block number. The formatis BBCCHHR in hexadecimal format (2 byte binarynumber, 2 byte cylinder number, 2 byte head ortrack number, 1 byte record number on the track).

QSAMQueued Sequential Access Method used by theutility.

Programmer responseReallocate the failing data set or assign an alternatetrack if required before further use.

Module:DFSUPRT0

Related referencez/OS: SYNADAF - Perform SYNAD analysisfunction (BDAM, BISAM, BPAM, BSAM, EXCP,QISAM, and QSAM)

DFS424I NO SPOOL DATASETS TO BEPRINTED.

ExplanationThe spool SYSOUT print utility was run with noddnames of the form SPOOLnnn. The job wasterminated with return code 4.


Module:DFSUPRT0

DFS425I INVALID SPOOL DATASETFORMAT.

ExplanationEither a noninitialized spool data set, a nonspool dataset with the SPOOLnnn ddname format, or an onlinesystem failure while writing a status record caused theprint utility program to reject printing of a spool dataset.

Programmer responseReinitialization of the IMS online control systemusing this data set should be accomplished prior tosubmitting the print program for further execution.

ModuleDFSUPRT0

DFS0426I PHYSICAL I/O ERROR IN STEPstepname prcstpnm

ExplanationA physical input or output error occurred ona database used by step stepname procedurewith stepname prcstpnm. Message DFS0451I (orDFS0451A) was issued indicating the nature of theerror. In addition, the step is abnormally terminating.The IOEROPN parameter of the PSB for this steprequested issuing an abend 0451, but the stepterminated abnormally for some other reason. Anabend 0451 was not be issued.

Programmer responseTake the appropriate action to correct the conditionsthat caused the I/O error and the abend condition.


Module:DFSDVBH0

Related information“DFS0451I” on page 159modname, dbdname, ddname, i/o error, decbfield“IMS problem determination” on page 11IMS messages and codes problemdetermination is accomplished by usingprocedures established by IBM.

DFS0427I LOGICAL ERROR ON ddname,ERROR CODE Vxx or Iyy.

ExplanationA logical error occurred while processing a VSAMdatabase.

In the message text:ddname

The DD name of the data set on which the logicalerror occurred.

xxThe logical hexadecimal error return code placedin the RPL feedback field by VSAM on the request


http://www-01.ibm.com/support/knowledgecenter/SSLTBW_2.4.0/com.ibm.zos.v2r4.idad500/syndf.htm?lang=en



that was in error. For an explanation of VSAMlogical error return codes, see z/OS DFSMS MacroInstructions for Data Sets.

yyAn IMS buffer handler logical error.

Vxx

An unexpected logical error was returned byVSAM.

System Action: The application programterminates abnormally with pseudoabend 0427,and IMS continues processing. However, ifDUMP=YES was specified on the DL/I bufferoptions statement, the application terminates withIMS standard abend 0427, and the control regionterminates abnormally.

Iyy

An unexpected condition occurred in DFSDVSM0.04

An invalid local vector index was detectedwhile testing for buffer validity using couplingfacility services.

08An unexpected return code was returned fromVSAM while testing for buffer validity usingcoupling facility services.

System Action: The buffer handler causes theapplication program to be terminated with abend0427.

If you have a program specification block (PSB)where one PCB has PROCOPT=L and another PCBhas PROCOPT=I (or GIRD or A), the results areunpredictable. This message can be issued.

Also, see the 0427 abend code information.


Module:DFSDVSM0


DFS0428I PSB SPECIFIED IN EXECUTEPARMS DOES NOT MATCH PSB ONLOG DATASET.

ExplanationThe PSB specified in the EXEC parameters of the BatchBackout job did not match the PSB on the update (typeX'50') records in the log data set supplied to BatchBackout.

This error occurs during backout of a batch job inwhich IRLM is being used for data sharing. If the wrongPSB was specified on the EXEC parameters, this checkprevents a data integrity exposure if batch backoutreleases all IRLM locks for a failed batch job, but doesnot complete any backout.

System actionBatch Backout terminates.

Programmer responseMake sure the PSB specified on the EXEC parametersmatches the PSB specified in the batch job beingbacked out.

Module:DFSBCKI0

DFS0429I VSAM {GENCB|MODCB} ERROR,RETURN CODE X'yy'.

ExplanationDL/I VSAM pool initialization issued a VSAM GENCBor MODCB macro, and encountered an error conditionreturned from VSAM X'yy' is the hexadecimal returncode in register 15 returned by VSAM.

System actionAbend 0430 is issued, and the step is terminated.

Programmer responseFor an explanation of return codes from VSAM GENCBand MODCB, see z/OS DFSMS Macro Instructions forData Sets.


Module:DFSDVBI0

Related referencez/OS: VSAM macro return and reason codesRelated informationIMS abend 0430“IMS problem determination” on page 11



http://www-01.ibm.com/support/knowledgecenter/SSLTBW_2.4.0/com.ibm.zos.v2r4.idad500/x1a.htm?lang=en



DFS0430I UNABLE TO INITIALIZE DL/IBUFFERING SERVICES, REASONCODE xx

ExplanationThe DL/I buffering services function cannot beinitialized. The variable xx is the reason for the failureand can have the following values:Reason code: 01

In a DL/I or DBB region, the PSB contained one ormore PCBs for VSAM databases. However, the DL/Ibuffer pool parameter data set (DFSVSAMP) wasnot provided.

Programmer response: Provide a DL/I buffer poolparameter data set to describe the VSAM buffersubpools for the job step.

Reason code: 02DL/I was unable to OPEN the buffer pool controlstatement data set. For batch regions, this dataset is defined by DDNAME DFSVSAMP. For onlineregions, this data set is defined by DDNAMEPROCLIB.

Programmer response: Ensure that the DDstatement is correct for the region type. Inaddition, for online regions, ensure that the valuespecified by the parameter VSPEC is a valid suffixto complete the member name of DFSVSMxxand the member name which exists in PROCLIB.Member name, DFSVSM00, is used if VSPEC is notspecified.

Reason code: 03In a DLI or DBB region, the PSB containedone or more PCBs for VSAM databases, but novalid subpool definition statements were found.Message DFS0434I or DFS0435I, or both, wasissued.

Programmer response: See message DFS0434I orDFS0435I.

Reason code: 04In a DLI or DBB region, the PSB contained one ormore PCBs for VSAM databases, but no subpooldefinition statements were found.

Programmer response: Check the controlstatements and correct if necessary.

Reason code: 05An I/O error was encountered while reading theDL/I buffer pool parameter data set.

Programmer response: See message DFS0436I.

Reason code: 06An error was encountered while attempting tobuild the VSAM shared resource pools. MessageDFS0432I was issued.


Reason code: 07An error was encountered while attempting to loada DL/I module. Message DFS0438I was issued.


Reason code: 08An error was encountered while issuing a VSAMSHOWCB macro. Message DFS0429I was issued.


Reason code: 09An error was encountered while attempting toobtain main storage for the DL/I buffer handlerpool. Message DFS0431I was issued.


Reason code: 10An error was encountered while issuing a VSAMGENCB macro. Message DFS0429I was issued.


Reason code: 11A GETMAIN failure occurred while processing DBDstatements for the specific subpool or shared-pool ID table or while processing the POOLIDstatements for the specific shared-pool ID table.

Programmer response: Rerun IMS with a largerregion size parameter.

Reason code: 12An error was encountered while attempting toobtain main storage for the ddname open table.Message DFS0441I was issued.


Reason code: 13An incompatible combination of controlstatements was found in the DFSVSAMP data set.The IOBF= statement requested that the OSAMbuffer pools be defined and allocated, but theOSAMOP IOSCB=NO statement requested that noOSAM resources be used in the batch environment.

Programmer response: Determine if an OSAMdatabase is to be accessed by the application. Usethe appropriate control statement.

Reason code: 14Hiperspace buffering is either specified on asubpool with a size of less than 4 KB, oris unavailable because of insufficient expandedstorage for the specified subpool size.


Programmer response: Remove any Hiperspacebuffering specifications on buffer sizes less than4 KB. See the z/OS MVS Initialization andTuning Guide (SA22-7591) for expanded storageproblems.

Reason code: 15A VSRBF keyword for VSAM subpool definition wasencountered before the first POOLID statement.When using the POOLID statement to defineone or more VSAM local shared resource pools,the VSRBF subpool definition statement for eachVSAM local shared resource pool must follow thePOOLID statement to which it pertains.

Programmer response: Review the informationabout the member DFSVSMxx. Correct the controlcards and resubmit the job.

Reason code: 16Duplicate coupling facility structure names werespecified on the CFNAMES control statement.Message DFS3385I is also issued to further definethe error.

Programmer response: Review the informationabout the member DFSVSMxx. Correct theCFNAMES control statement, and resubmit the job.

Reason code: 17All keywords (CFIRLM, CFOSAM, and CFVSAM)must be specified on the CFNAMES controlstatement. Message DFS3388I is also issued tofurther define the error.


Reason code: 18An error was found on the CFNAMES controlstatement. Message DFS0437I is also issued tofurther define the error.


Reason code: 19

Explanation: In a batch environment, IRLM isbeing used, but DBRC is not.

Programmer response: Make sure that DBRC wasspecified in the IMS system definition or thatDBRC=N was not specified on the EXEC statementof the execution JCL.

Reason code: 21An error was encountered while attempting toobtain main storage for the Block SerializationLatch table. Message DFS3287E was issued.

Programmer response: See message DFS3287E.

System actionIMS is terminated with abend 0430.


Module:DFSDVBI0, DFSXBAT0, DFSTRA00

Related informationIMS abend 0430“DFS3287E” on page 916STORAGE NOT AVAILABLE FOR BLOCKSERIALIZATION TABLE, RETURN CODE X'xx'“DFS0429I” on page 149VSAM {GENCB|MODCB} ERROR, RETURN CODEX'yy'.“DFS0431I” on page 151STORAGE NOT AVAILABLE FOR VSAM BUFFERPOOL, RETURN CODE nn“DFS0432I” on page 152VSAM SHARED RESOURCE POOL CANNOT BEBUILT, RETURN CODE X'yy', POOL ID xxxx, zzzzz“DFS0433I” on page 152NUMBER OF BUFFERS FOR SUBPOOL SIZEnnnnn CHANGED TO mmm“DFS0434I” on page 152BUFFER SIZE OR KEYWORD INVALID ON CARDnnn“DFS0435I” on page 153NUMBER OF BUFFERS INVALID ON CARD n“DFS0436I” on page 153I/O ERROR ON CONTROL CARD DATASET“DFS0437I” on page 153CARD nnn, ERROR IN PARAMETER mmm“DFS0438I” on page 154UNABLE TO LOAD MODULE m, return code X'nn'“DFS0441I” on page 155STORAGE NOT AVAILABLE FOR OPEN TABLE,RETURN CODE X'yy'“IMS problem determination” on page 11IMS messages and codes problemdetermination is accomplished by usingprocedures established by IBM.

DFS0431I STORAGE NOT AVAILABLE FORVSAM BUFFER POOL, RETURNCODE nn

ExplanationAn error was encountered while attempting toGETMAIN storage for the DL/I VSAM buffer pool.nn is the return code from the IMODULE GETMAIN



macro. For a description of these return codes, see theIMODULE return codes information.


Programmer responseIf insufficient storage is available, increase the mainstorage available to IMS. If LSO (local storage option)is selected for the DL/I SAS region, then subpool 251(low private storage) for the DL/I region is not largeenough for the DL/I buffer pool. Increase the regionparameter in DL/I startup JCL. If LSO=N (no separateDL/I address space) is selected, then there is notenough subpool 231 available. Increase the regionparameter in the control region JCL.


Module:DFSDVBI0

Related referenceIMODULE return codes (Messages and Codes)Related informationIMS abend 0430“IMS problem determination” on page 11IMS messages and codes problemdetermination is accomplished by usingprocedures established by IBM.

DFS0432I VSAM SHARED RESOURCE POOLCANNOT BE BUILT, RETURN CODEX'yy', POOL ID xxxx, zzzzz

ExplanationIMS issued a VSAM BLDVRP macro to build theVSAM shared resource pool. VSAM detected an errorcondition and did not build the pool. The variable yyis the hexadecimal error code returned by VSAM. Ifmultiple shared resource pools were requested, POOLID xxxx indicates the particular shared resource poolin error. zzzzz is the shared resource pool type, that iseither INDEX or DATA.

System actionIf the shared resource pool in error is the only orthe default shared pool requested, IMS terminatesabnormally. It issues an abend 0430. Otherwise, IMSreassigns the data sets to the default shared resourcepool.

Programmer responseFor further explanation of the return codes fromthe VSAM BLDVRP macro, see z/OS DFSMS MacroInstructions for Data Sets.

Module:DFSDVBI0

Related referencez/OS: BLDVRP return codesRelated informationIMS abend 0430

DFS0433I NUMBER OF BUFFERS FORSUBPOOL SIZE nnnnn CHANGEDTO mmm

ExplanationThe number of buffers specified for the VSAM orOSAM subpool size nnnnn was less than the requiredminimum or greater than the allowed maximum.

System actionThe system built mmm buffers in the subpool.

Programmer responseFor an explanation of the number of buffers,see Specifying VSAM and OSAM subpools (SystemDefinition).


Module:DFSDVBI0

Related conceptsSpecifying VSAM and OSAM subpools (SystemDefinition)Related information“IMS problem determination” on page 11IMS messages and codes problemdetermination is accomplished by usingprocedures established by IBM.

DFS0434I BUFFER SIZE OR KEYWORDINVALID ON CARD nnn

ExplanationThe nth statement in the buffer pool parameter dataset specified an invalid buffer size or an invalidkeyword. A buffer size must be 512, 1024, 2048,4096, or a multiple of 4096 up to and including 32768.




http://www-01.ibm.com/support/knowledgecenter/SSLTBW_2.4.0/com.ibm.zos.v2r4.idad500/x2i.htm?lang=en


http://www.ibm.com/support/knowledgecenter/SSEPH2_15.1.0/com.ibm.ims15.doc.sdg/ims_sdr73.htm#sdr73




System actionThe statement is bypassed.



Module:DFSDVBI0


DFS0435I NUMBER OF BUFFERS INVALID ONCARD n

ExplanationThe nth statement in the buffer pool parameter dataset specified an invalid number of buffers, or the valuespecified was not numeric.

System actionIf VSAM is used (and the value is not numeric),the statement is bypassed. For OSAM, defaults aretaken for all remaining parameters. If the parameteris numeric, see message DFS0433I.

Programmer responseCorrect the control statement; then resubmit the job, ifnecessary.


Module:DFSDVBI0

Related information“DFS0433I” on page 152NUMBER OF BUFFERS FOR SUBPOOL SIZEnnnnn CHANGED TO mmm“IMS problem determination” on page 11IMS messages and codes problemdetermination is accomplished by usingprocedures established by IBM.

DFS0436I I/O ERROR ON CONTROL CARDDATASET

ExplanationModule DFSCVBIO attempted to read the buffer poolparameter data set (DFSVSAMP) and encountered anI/O error.

System actionIn region type DBB or DLI, if a database using VSAMwas specified in the PSB, abend 0430 was issued. Inall other cases, processing continues without a DL/IVSAM buffer pool.

Programmer responseEnsure that the DD statement for DFSVSAMP iscorrect, and resubmit the job.


Module:DFSDVBI0


DFS0437I CARD nnn, ERROR IN PARAMETERmmm

ExplanationThe nth statement in the buffer pool parameter dataset has an error in the mth parameter. For an onlinesystem, this error occurs if system definition does notinclude the DBD. For a batch job, this error occurs ifthe DBD is not generated within the PSB being used.This error can also occur if invalid parameters are onthe following statements:

CFNAMESIOBFDBDOPTIONSVSRBF or VSAM buffer pool definitionRESVPOOLLOCKTIMEFFROLR

System actionThe parameter is ignored, and processing continues.

In the buffer pool parameter data set, if the databaseparameter is specified with a data set number of A toJ, L or X for HALDB but the database is a NON HALDB,



the system issues this message; the allocation doesnot occur. If the database is later converted to HALDB,then the allocations for this entry become live as soonas the database is started (without recycling IMS). Thesame occurs if you have a data set number 1 and areconverting from HALDB to NON HALDB.

Programmer responseThe parameter has been ignored. Correct the controlstatement, and resubmit the job. See the IMS systemdefinition information for parameter formats.


Module:DFSDVBI0, DFSTRA00, DFSRDB30


DFS0438I UNABLE TO LOAD MODULE m,return code X'nn'

ExplanationAn error was encountered while attempting to load themodule with module name m. X'nn' is the hexadecimalreturn code from the IMODULE LOAD macro. For adescription of these codes, see the IMODULE returncodes information.

System actionIMS is terminated abnormally with abend 0430.

Programmer responseProvide the module in a library where it can beaccessed without error.


Module:DFSDVBI0


DFS0439I WARNING, VSAM SUBPOOLSWITH EQUAL LENGTH BUFFERSHAVE BEEN DEFINED, POOL IDxxxx

ExplanationTwo or more VSAM subpool definition statementsspecify the same buffer size. If multiple sharedresource pools were requested, POOL ID xxxxindicates the particular shared resource pool in error.

System actionA subpool is built with the sum of the number ofbuffers specified.

Programmer responseIf the intent was to build separate subpools, thencorrect the subpool definition statements to specifydifferent buffer sizes.


Module:DFSDVBI0


DFS0440A GSR POOL ALREADY EXISTS,REPLY 'LOCAL' 'DELETE' OR'ABEND'

ExplanationIMS issued a VSAM BLDVRP macro to build the VSAMglobal shared resource pool. When a return code of4 is returned, indicating that a GSR pool exists, thesystem operator must reply.

System actionIMS waits for operator's response.

Operator responseUse one of the following responses:LOCAL

Another IMS system is running with a GSR and youwant initialization to continue. This option resultsin the use of the local shared resource (LSR) poolfor this run of IMS.




DELETENo other IMS system is running currently and youwant to have the global shared resource (GSR)pool. This option results in the current GSR poolbeing deleted and a new GSR pool being built forthis run.

Note: Choosing this option when a current IMSsystem running with a GSR pool, the pool isdeleted. Results are unpredictable.

ABENDAnother IMS system is running with GSR, and youdo not want to run this system with LSR, or you donot know whether another system is running withGSR and you want to terminate the initialization.This option results in message DFS0432I followedby abend 0430.


Module:DFSDVBI0


DFS0441I STORAGE NOT AVAILABLE FOROPEN TABLE, RETURN CODE X'yy'

ExplanationAn error was encountered while attempting toGETMAIN storage for an open table. 'yy' is the returncode from the IMODULE GETMAIN. For a descriptionof these codes, see the IMODULE return codesinformation.


Programmer responseIf insufficient storage is available, increase the mainstorage available to IMS.


Module:DFSDVBI0

Related referenceIMODULE return codes (Messages and Codes)Related informationIMS abend 0430“IMS problem determination” on page 11


DFS0442A VSAM RDF/CIDF BADDBD=dbdname DD=ddname

ExplanationBefore writing a VSAM control interval, the recorddefinition field (RDF) and the control interval definitionfield (CIDF) were checked and found to be invalid orinconsistent with the record format required by IMS.

System actionThe application program terminates abnormally.

Programmer responseUse the database recovery procedure to reconstructthe database in error.


Module:DFSDVSM0


DFS0443I dbname IS REGISTERED AS NON-RECOVERABLE

Explanation:For information and actions, see message DFS0443W.

Related informationDFS0443Wdbname IS INCONSISTENT WITH OTHER DBSIN THE DBNET

DFS0443W dbname IS INCONSISTENT WITHOTHER DBS IN THE DBNET

ExplanationScheduling issues the first form of the message whenthe identified database is registered with DBRC asnonrecoverable.

Scheduling issues the second form when theidentified database is registered as nonrecoverableand related databases are registered as recoverable.It is suggested that all related databases be eitherrecoverable or nonrecoverable.






This is an informational message.

Module:DFSDBLN0

DFS0444 MESSAGE LENGTH EXCEEDS FASTPATH BUFFER LENGTH - INPUTIGNORED

ExplanationThe terminal operator entered a Fast Path messagesegment that was too long for the expedited messagehandling buffer (EMHB). The EMHB is defined in theFPBUFLEN keyword on the TERMINAL macro.

System actionThe transaction message is discarded.

Operator responseCorrect the format of the transaction message; thenreenter the command.

Module:DBFSUIX0

DFS0445I WARNING - INVALID VSAMSHARED RESOURCE POOLDEFINITION, POOLID xxxx,REASON CODE yy

ExplanationThe definition for the VSAM shared resource pool isinvalid. xxxx identifies the pool ID, and yy identifiesone of the following reason codes:Reason code: 01

An error was detected in an attempt to definean index subpool without any data subpool withinthe same VSAM shared resource pool. IMS cannotbuild the particular shared resource pool.

Programmer response: Correct the controlstatements before the next job execution.

Reason code: 02The maximum number of VSAM shared resourcepools has been exceeded. Any POOLID statements(with the corresponding VSRBF statements) foundafter the limit is reached are ignored. The warning

message is issued only for the first valid POOLIDstatement that exceeds the limit.

Programmer response: Combine or eliminate theVSAM POOLID subpool definition statements thatexceed the limit.

Reason code: 03While processing POOLID subpool definitionstatements, an invalid pool ID was found. IMSignores the POOLID statement and all VSRBFstatements defining subpools within that sharedresource pool. Only the first four characters of theinvalid pool ID appear in the warning message. SeeDefining VSAM buffer pools (System Definition) foran explanation of the POOLID statement.

Reason code: 04While processing POOLID subpool definitionstatements, a POOLID statement was coded witha duplicate pool ID. IMS ignores the POOLIDstatement with the duplicate pool ID. IMS alsoignores all VSRBF statements that define subpoolsin that shared resource pool.

Programmer response: Correct the controlstatements before the next job execution.

Reason code: 05While processing POOLID subpool definitionstatements, an invalid parameter was found. IMSignores the remainder of the particular POOLIDstatement and uses the default values of theremaining parameters. See Defining VSAM bufferpools (System Definition) for an explanation of thePOOLID statement.

Reason code: 06An error was detected while processing POOLIDsubpool definition statements. The VSAM sharedresource pool ID on the POOLID subpool definitionstatement (for a shared resource pool other thanthe default pool) was not referenced by any validbuffer pool DBD statement. The VSAM sharedresource pool is built but not used. See DefiningVSAM buffer pools (System Definition) for anexplanation of the POOLID statement.

Reason code: 07An error was detected in the attempt to define aVSAM shared resource pool which did not containa subpool. A POOLID subpool definition statementis followed by another POOLID statement ratherthan by VSRBF subpool definition statements. AVSAM shared resource pool without any definedsubpool is ignored. See Defining VSAM bufferpools (System Definition) for an explanation of thePOOLID statement.

Reason code: 08The maximum number of VSAM shared resourcepools has been exceeded when the number


http://www.ibm.com/support/knowledgecenter/SSEPH2_15.1.0/com.ibm.ims15.doc.sdg/ims_dfsvsmxx_proclib_vsam.htm#definingvsambufferpools







of shared pools reserved with the RESVPOOLstatement is considered. Normally, the maximumnumber of shared pools allowed is:15

in a batch or utility environment16

in a DC or DBCTL environment

Any POOLID statements (with the correspondingVSRBF statements) found after the limit is reachedare ignored. The warning message is only issuedfor the first valid POOLID statement exceeding thelimit.

IMS buffer pool initialization continues.

Programmer response: Combine or eliminate theVSAM POOLID subpool definition statements thatexceed the limit.

Reason code: 20A terminal in Fast Path response mode attemptedto logon to an IMS system that is not Fast Pathcapable.

Module:DBFSUIX0, DFSRDB30

DFS0446I WARNING - VSAM SHAREDRESOURCE POOLID xxxx ON DBDSTATEMENT IN ERROR

ExplanationAn error was detected while processing DBDstatements. The VSAM shared resource pool ID onthe DBD statement did not match the ID on any validPOOLID subpool definition statement.

System actionIMS reassigns the data set to the default sharedresource pool.

Programmer responseCorrect the control statement before the next jobexecution.

Module:DFSRDB30

DFS0447I NUMBER OF BUFFERS FOR VSAMSUBPOOL SIZE nnnnn CHANGEDTO mmm, POOL ID xxxx

ExplanationThe number of buffers specified for the VSAM subpoolsize nnnnn was either less than the required minimumor was greater than 32767. If multiple shared resource

pools were requested, POOL ID xxxx indicates theshared resource pool in error.

System actionmmm buffers were built in the subpool.

Programmer responseFor an explanation of buffer pool specifications, seethe IMS system definition information.

Module:DFSDVBI0

DFS0448I VSAM HIPERSPACE BUFFERINGINVALID|UNAVAIL|FAILED FORSUBPOOL SIZE nnnnn, POOL IDxxxx

ExplanationVSAM Hiperspace buffering is invalid when specifiedon a subpool size less than 4 K bytes. VSAMHiperspace buffering is unavailable for the indicatedsubpool size because of insufficient expanded storage,and the Hiperspace buffers were defaulted orspecified as optional.

VSAM Hiperspace buffering failed for the indicatedsubpool size because of insufficient expanded storage,and the Hiperspace buffers were specified as required.

If multiple shared resource pools were requested,POOL ID xxxx indicates the shared resource pool inerror.

System actionFor INVALID or FAILED, IMS initialization abnormallyterminates with abend 0430.

For UNAVAIL, initialization of IMS continues withoutHiperspace buffering for the identified VSAM subpool.

Programmer responseRemove any Hiperspace buffering specifications onbuffer sizes less than 4 K.

If sufficient expanded storage exists and this messageindicates that storage is unavailable, try increasingthe z/OS SRM values in the IPS statement forPWSS=(min,max). See z/OS MVS Initialization andTuning Guide (SA22-7591).

Module:DFSDVBI0

DFS0448W VSAM HIPERSPACE SIZESPECIFIED EXCEEDS THE 2GBLIMIT, POOL ID xxxx.


ExplanationThe size of a Hiperspace pool size exceeded the 2 GBlimit.

In the message text:xxxx

The local shared resource (LSR) VSAM buffer poolID

System actionThe Hiperspace pool size defaults to the 2 GB limit.

Programmer responseCheck the specification of the buffer.

Module:DFSDVBI0

DFS449A VOLUME...... IS INCORRECT FORRESTART-MOUNT VOLUME......

ExplanationDuring restart processing, the utility detected anincorrect volume mounted for the continuation of theimage data set.

System actionThe utility closes the data set, forcing the incorrectvolume to be demounted, and then opens the data set.The utility continues to do this until the correct volumeis mounted.

Operator responseIf the volume serial numbers are not specificallymentioned in the JCL or catalog, mount the volume

specified in the second half of the message. If thevolume is described, continue mounting volumes thatz/OS will accept until the volume the utility requires iseventually mounted.

Module:DFSUICP0

DFS0450I DFSDDLE0 dbdnameSTOPPED-LOGICAL ERRORDDNAME=ddname VSAM ERRORCODE=nn

ExplanationThe module detected a read or write error on thedatabase definition name on the DDNAME data set.This message indicates VSAM returned (in register15) a return code of 8 to a VSAM PUT from moduleDFSDDLE0. A logical error code from the RPL is alsoprinted to further define the logical error.



Module:DFSDDLE0



Chapter 13. DFS messages, DFS0451A - DFS0500I


DFS0451A modname, dbdname, ddname, i/oerror, decb field

ExplanationThis message is related to DFS0451I. See thatmessage for a detailed explanation and actions.

Related informationDFS0451Imodname, dbdname, ddname, i/o error, decbfield

DFS0451I modname, dbdname, ddname, i/oerror, decb field

or

hhmmss, variable text

ExplanationAny of the forms of this message can be issued. AREAD or a WRITE error has occurred during an I/Ooperation.

Module modname detected an error during an I/Ooperation or while processing the write error queueelements (WEQE) for the identified ddname indatabase dbdname. The variable i/o error indicateswhether it is a READ error or whether a WEQE is found,and the status code is returned to the applicationprogram. No status code is returned for the WRITEerror.

If the access method is VSAM, this message ispreceded by a display of bytes 26-125 of theVSAM physical error message, prefixed by DFS0451Ihhmmss. For the format and contents of this message,see z/OS DFSMS Macro Instructions for Data Sets.

If the access method is OSAM, decb field is the fieldDECBSTAT from the DECB used for the I/O operation,followed by a description of the error. See messageDFS0762I for the DECB status code (DECBSTAT)definitions.

If the IOEROPN=(n,WTOR) parameter is specifiedwhen the PSB is generated and if the system isbatch (DLI or DBB), the operator can specify abendor continue. This option is only specified in batch for anaction-required message.

The values are defined as follows:modname

One of the following modules issued the message:

DFSDVSM0DFSDBH00DFSDDLE0

dbdnameDatabase name

ddnameDD name

i/o errorIndicates that a READ or WRITE error has occurredduring an I/O operation or that the WEQE (writeerror queue element) was detected. Whenever aWRITE error has occurred and the subsystem doesnot have a copy of the data, a WEQE is created forthe block.

If an application requests data in a block with aWEQE, this message is generated and a statuscode is passed back to the application program.After the database recovery has been performed,all WEQEs for the database will be freed. TheWEQE in the subsystem incurring the WRITE error(data sharing or non-data sharing environment)is flagged to allow error free READ operationsfor that block in that subsystem. In a datasharing environment, if an application running in asubsystem other than the one incurring the WRITEerror requests a segment in the given databaseblock, this message is generated and a statuscode is passed back to the application program.A READ operation is not issued for the block sinceit was incorrect. After the database recovery hasbeen performed, all WEQEs for the database willbe freed. In a nondata sharing environment, ifthe database is closed and then reused withoutrecovering it (for example /DBD instead of /DBR), this flag is removed and subsequent READrequests for that block result in this message beingissued.

decb fieldA DECB field is indicated by the DECBSTAT orDECBEXC

For the hhmmss, variable text version:

A READ or a WRITE error has occurred during an I/Ooperation. This form of the message is issued for VSAM


errors. hhmmss is a time stamp, and variable text isfrom VSAM.

The VSAM error IEQE indicates the existence of akey-sequenced data set (KSDS) IO toleration extendederror queue element (EEQE) to prevent any access tothe record pointed by the EEQE.

System actionFor the action-required message, DL/I waits forthe operator to respond before continuing. If theoperator responds with ABEND, the applicationprogram terminates with pseudoabend 0451, and IMScontinues processing. However, if DUMP=YES wasspecified on the DL/I buffer options statement, theapplication terminates with standard abend 0451. Anoperator response of CONT causes IMS to continueprocessing.

For the information message, processing continues.

If IOEROPN=(451,WTOR), IMS terminates with abend0451, even if the operator responds CONT to theDFS0451A message.

Operator response(system): For the action-required message, replyABEND to cause abend 0451, or CONT to cause IMSto continue processing. No action is required for theinformation message.

(master terminal) : Contact the appropriate supportpersonnel responsible for the recovery of thedatabase.

System programmer responseFor both messages, if it is a permanent READ erroror WRITE error, recover the database. However, ifonly WRITE errors occur, the database might continueto be used by the online system, and recovery canbe delayed until a convenient time. If applicationperformance is affected or READ errors occur, thedatabase must be recovered.


Module:DFSDBH40, DFSDDLE0, DFSDVSM0

Related referencez/OS: RPLERRCD reason codesRelated information“DFS0762I” on page 280OSAM (TAPE | DASD) (READ | WRITE) ERROR -FUNC=aa STATUS=bb, cc, dddd, eeee, ffff“IMS problem determination” on page 11


DFS0452I DUP-CLOSE NO LONGERSUPPORTED -- USE DUP AND REPTHEN RERUN CLS MODE

or

CONTROL CARD INPUT NOT PRESENT

or

ERROR IN CONTROL CARD FORMAT

ExplanationEither control statement input was missing or acontrol statement was in error. The erroneous controlstatement is printed on the SYSPRINT data set.

Programmer responseResubmit the job with a control statement or acorrected control statement.

Module:DFSULG10

DFS0453I UNABLE TO OPEN xxx

ExplanationThe data set (xxx) was not able to be openedsuccessfully. xxx consists of a descriptive name of thedata set plus the ddname.

The values for xxx are:

CARD INPUT ddnamePRINT OUTPUT ddnameINPUT OLDS ddnameINPUT SLDS ddnameOUTPUT LOG ddnameNEXT OLDS ddname

System actionIf the error occurs on a dual WADS or dual Next,OLDS processing continues using the alternate dataset. Otherwise, the Log Recovery utility terminatesprocessing.


http://www-01.ibm.com/support/knowledgecenter/SSLTBW_2.4.0/com.ibm.zos.v2r4.idad500/rplerr.htm?lang=en

Programmer responseIf the Log Recovery utility fails, ensure that a DDstatement is present and specified correctly. If ahardware failure is indicated, rerun the job specifyingan alternate unit.

Module:DFSULG10, DFSULG20

DFS0454I UNSUCCESSFUL ALTERNATE LOGDATASET POSITION---REASON x

ExplanationDual input logs were specified for the Log Recoveryutility. An error was detected while reading one of theinput logs.

The value of the reason code x is 2 or 3.Code (hex)

Meaning02

Dual SLDS input was provided. The two SLDSs didnot start with the same block of data. DFSULG20processing has terminated for both input logs, butthe block of data common to both logs was notsuccessfully read.

03Dual input logs were provided. DFSULG10 tried toread the first block from each log to determineif the input was valid. For OLDS, the first pairof blocks must be readable and identical. ForSLDS, the first pair of blocks must be readable.If the SLDS blocks are not identical, the higherlog sequence number (for the first log record)is saved. Processing of that input log (and itscorresponding output log) is suspended until thehigher log sequence number is found on the otherremaining input log.

System actionThe Log Recovery utility terminates processing with amemory dump.

Programmer responseFor reason code 02, examine the error block listingand the input logs. Try to determine why the matchingblock was not read. (The matching block is either anerror block or is missing on the input log.) If the blockis in error, correct the block using z/OS system utilities.If the block is missing, provide all SLDS volumes asinput. Then rerun the utility.

For reason code 03, use z/OS system utilities toexamine the input logs. Correct the error and rerun theutility.


DFS0455I I/O ERROR ON xxx DURING mmmOPERATION

ExplanationThe Log Recovery utility, DFSULTR0, encountered anI/O error on data set xxx while processing in modemmm. The value of mmm is CLS, DUP, or REP. xxxconsists of a descriptive name of the data set plus theddname.

The values for xxx are:

INPUT OLDS ddnameINPUT SLDS ddnameOUTPUT LOG ddnameNEXT OLDS ddname

System actionIf the I/O error occurs on a dual data set, processingcontinues using the alternate data set. Otherwise, theLog Recovery utility terminates processing.

Programmer responseIf the Log Recovery utility fails (that is, return code =8), do one of the following:

• If the error occurred on the interim log data seteither during REP mode, input OLDS, or next OLDS,run DUP mode to close or recover the data sets.

• If the error occurs on the interim log data set duringDUP mode or during an output log, rerun the job andspecify another drive or volume.


DFS0456I ERROR ID'S ON STATEMENT ANDINTERIM LOG DO NOT MATCH


• The input control statements to a REP modeoperation were out of sequence.

• The sequence number is wrong.• The control statements are missing.

System actionThe Log Recovery utility terminates processing.

Chapter 13. DFS messages, DFS0451A - DFS0500I 161

Programmer responseDo the following:

1. Verify that the control statements agree with theprinted output produced in the DUP mode run.

2. Correct and resubmit the job.3. Ensure that the appropriate interim log data set

was used.

Module:DFSULG10

DFS0457I CONTROL CARD SPECIFIED 'B'RECORD---NO 'B' RECORD ONINTERIM LOG

ExplanationSYSIN input specified that the data be replaced in theB record of the given sequence number. An A recordwas encountered but no corresponding B record waspresent.


Programmer responseTake the following actions:

• Check the printed output from the previous DUP runto ensure that the B records were produced.

• Ensure that the appropriate interim log data set wasused.

Module:DFSULG10

DFS0458I CONTROL CARD OUT OFSEQUENCE

ExplanationThe control cards are out of sequence.

Programmer responsePut the control cards in the appropriate sequence, andresubmit the job.

Module:DFSULG10

DFS0459I EOF ON INTERIM LOG WITHCONTROL CARD YET TO PROCESS

ExplanationControl statements were submitted for records not onthe interim log data set. The remaining unprocessedcontrol statements are printed on the SYSPRINT dataset.


Programmer responseDetermine if the extra control statements are valid. Ifthey are not, a volume of the interim log data set wasprobably omitted from the job.

Module:DFSULG10

DFS0460I REPLACEMENT DATA WILL NOTFIT IN RECORD

ExplanationThe offset plus the length of the data specified by theREP statement falls outside of the indicated block.


Programmer responseExamine the printed output from the previous DUP runto determine the proper offset and length. Correct thecontrol statement, and rerun the job.

ModuleDFSULG10

DFS0461I USER HAS SPECIFIED 'REP' INBOTH A AND B RECORDS

ExplanationFor a given sequence number, data can be replacedin either the A record or the B record. It cannot bereplaced in both records.

Programmer responseResubmit the job, specifying "REP" in either the Arecord or the B record.

ModuleDFSULG10


DFS0462 NOBUILDQ KEYWORD MUST NOTBE PRESENT

ExplanationYou can use the NOBUILDQ keyword only whenwarm starting IMS using the /NRE command with theFORMAT keyword included. (Even though the BUILDQkeyword is valid with the /ERE command, NOBUILDQis not valid.) For a description of the syntax of the /NREand /ERE commands, see IMS Version 15 Commands,Volume 1: IMS Commands A-M.

ModuleDFSICL20

Related reference/NRESTART command (Commands)/ERESTART command (Commands)

DFS0463I BUILDQ OR NOBUILDQ KEYWORDREQUIRED

ExplanationYou entered the /NRE FORMAT command to warmstart IMS, but omitted the BUILDQ or NOBUILDQkeyword. You must specify either BUILDQ to build thequeues after formatting the data sets indicated by theFORMAT keyword, or NOBUILDQ to format the datasets without rebuilding the queues.

For the commands /NRE FORMAT SP and /NREFORMAT ALL, NOBUILDQ is invalid and you mustspecify BUILDQ.


ModuleDFSICL20

DFS0464A THE SECONDARY INDEXINDICATOR IS NOT ON IN THEDBD FOR MEMBER (dbdname)

ExplanationThe control statement image printed before thismessage indicates that the dbdname specified is asecondary index, but the secondary index flag is noton in the DBD member.

System actionIf the utility is not executing under the UtilityControl Facility (UCF) and the OPTIONS=ABEND isnot selected, execution continues to the next controlstatement image. The step terminates with a returncode of 8. If the OPTIONS=ABEND card is specified,the utility terminates with a user abend.

If the utility is executing under the UCF, processingceases and execution terminates with a return code of8.

Programmer responseVerify that the control statement image is specifiedcorrectly and check the source DBD for the databasename printed in the message. Rerun the job aftermaking the appropriate corrections.

ModuleDFSURUL0

DFS0465I PSB psbname IS INCORRECT FORDBD dbdname, PSB STOPPED.

ExplanationThe named PSB has a DL/I PCB statement thatreferences a Fast Path (MSDB or DEDB) DMB.

System actionThe PSB is stopped.

Programmer responseCorrect the PSB in error, rerun ACBGEN, and rerun theprogram.

ModuleDFSDBLP0, DFSXRBL0

DFS0466I NO xxxxxxxx DD CARD SPECIFIED

ExplanationThe utility program found a control statement thatrequires the ddnamexxxxxxxx which was not supplied.

System actionThe Log Recovery Utility terminates processing.

Programmer responseCorrect the control statement or JCL and resubmit thejob.


http://www.ibm.com/support/knowledgecenter/SSEPH2_15.1.0/com.ibm.ims15.doc.cr/imscmds/ims_nrestart.htm#ims_cr2nrestart

http://www.ibm.com/support/knowledgecenter/SSEPH2_15.1.0/com.ibm.ims15.doc.cr/imscmds/ims_erestart.htm#ims_cr1erestart

DFS467I xxxxxxxx DDDUMMY CARDSPECIFIED

ExplanationThe utility program found a control statement thatrequired the ddname xxxxxxxx which is DD DUMMY.

System actionThe Log Recovery Utility terminates processing.

Programmer responseCorrect the control statement or JCL and resubmit thejob.

DFS468 INCORRECT VTAM LEVEL - RNRDISABLED

ExplanationRapid Network Reconnect (RNR) must be running withVTAM 4.4 or above. If VTAM is not at the correct level,RNR is disabled.

System actionIMS continues normal execution.


DFS469 ALL SESSION RECONNECTS HAVEBEEN INITIATED

ExplanationAll session reconnections for the IMS Rapid NetworkReconnect option have been scheduled. The sessionreconnection function runs asynchronously withnormal IMS processing and the MTO is notified of anyreconnect failures.



DFS470 RAPID NETWORK RECONNECTSTARTING

ExplanationIMS starts the Rapid Network Reconnect process.



Module:DFSVTP00

DFS0471I IMS CANNOT LOCATE NODExxxxxxxx DURING RAPIDNETWORK PROCESS

ExplanationDuring the session reconnect process, VTAM notifiesIMS that all sessions are pending recovery. Torestore each individual session, IMS has to locateits corresponding control block. However, the controlblock for the node xxxxxxxx was not found.


Operator response:The session can be restarted, as appropriate, usingnormal session initiation procedures.


Module:DFSIDC00


DFS0472I RNR FUNCTION DISABLED FORIMS/ESA EXECUTION WITH XRF

ExplanationThe RNR option was specified as an IMS executionparameter for an IMS system generated with XRF.

System actionIMS execution continues with the RNR functiondisabled.

Operator response(master terminal) Continue with the execution andRNR disabled. Use of RNR requires a new IMS systemdefinition without XRF included (HSB=NO on theIMSCTRL macro statement).



Module:DFSIIDC0


DFS473 PROTECTED DATA FIELD ALTERED- INPUT IGNORED

ExplanationThe Message Format Service (MFS) detects changedcontent in a protected field from the input of a 3270or SLU2 device. The content of the protected field thatwas transmitted to the device differs from the contentreceived.

System actionThe system ignores the input and creates an X'6701'log record with the ID of MFSP.

Output destinationA 3270 or SLU2 device.

Operator responseContact the IMS system programmer for assistance.

Programmer responseVerify if the device is secure and operating properly.


Module:DFSCFE00


DFS0474W RAPID NETWORK RECONNECTFAILED INQUIRE/RESTORERC=nn, FDB2=mm

ExplanationVTAM INQUIRE or RESTORE commands were issuedduring Rapid Network Reconnect, and VTAM returneda bad code.

In the message text:nn

The return code received from VTAM.mm

The FDB2 returned by VTAM.

For information returned by VTAM and possibleactions, see z/OS Communications Server SNAMessages (SC31-8790) and z/OS CommunicationsServer: SNA Programming (SC31-8829).

System actionIMS terminates the Rapid Network Reconnect.

Operator response:The session can be restarted, as appropriate, usingnormal session initiation procedures.


Module:DFSIDC00

Related referencez/OS: RPL return code (RTNCD,FDB2)combinationsRelated information“IMS problem determination” on page 11IMS messages and codes problemdetermination is accomplished by usingprocedures established by IBM.

DFS0475I POSITION FAILURE DURINGREPOSITIONING ON FILENAME,EXPECTED xxxxxxxx, FOUNDyyyyyyyy

or

GETMAIN FAILURE DURING REPOSITIONING ONFILENAME, RETURN CODE RETCODE

or

BSP FAILURE DURING REPOSITIONING ONFILENAME, RETURN CODE RETCODE, REASON CODEREACODE

or

READ FAILURE DURING REPOSITIONING ONFILENAME, POST CODE POSTCODE


http://www-01.ibm.com/support/knowledgecenter/SSLTBW_2.4.0/com.ibm.zos.v2r4.cs3cod0/rfbk.htm?lang=en


or

WRITE FAILURE DURING REPOSITIONING ONFILENAME, POST CODE POSTCODE

ExplanationThis message follows message DFS0414I. After an I/Oerror on one OLDS using dual logging, IMS attempts toback out the data that was written to the other OLDSin the pair. To do this, IMS attempts to reestablishposition in the file. Various errors can occur duringthe repositioning process. Each form of the messageindicates a specific repositioning error. IMS issues thefirst form of the message when an IMODULE GETMAINcall to obtain a temporary Read/Write buffer fails.The return codes from the call indicate the followingconditions:

CodesExplanation

4Storage not allocated

8Parameter error

38Caller in SRB or XM mode

IMS issues the second form of the message when aBSP (BACKSPACE ) request fails. For a description ofthe return codes and reason codes, see z/OS DFSMSMacro Instructions for Data Sets. IMS issues the thirdand fourth forms of the message when a BSAM read orwrite request fails. For a description of the post codes,see MVS/DFP V3R3 Customization (SC26-4560), whichrefers to them as status indicators in the ECB. IMSissues the fifth form of the message when it hasrepositioned itself in the OLDS but finds that the blockat that point does not have the expected sequencenumber. The expected sequence number is xxxxxxxx.The found sequence number is yyyyyyyy.

System actionIMS continues processing and switches OLDS.

Programmer responseSince some of the blocks of data can be duplicatedin the old and new pair of OLDS, run the log recoveryutility to remove the extra blocks and close the OLDS.(DBRC does not archive the OLDS unless this is done.)Run the utility in CLS mode using DFSOLP, DFSOLS,DFSNOLP, and DFSNOLS DD statements. So not useDFSWADSn DD statements. The DFSOLP and DFSOLSDD statements must reference the OLDS pair on which

the I/O error occurred. The DFSNOLP and DFSNOLSDD statements must reference the OLDS pair to whichIMS switched following the I/O error.

Module:DFSFDLB0, DFSFDLS0

Related referencez/OS: BSP completion codesRelated information“DFS0414I” on page 143CONTINUING WITH ALTERNATE LOG

DFS0476A SPOOL DATASET ABEND --DDNAME = xxxxxxxx

ExplanationA permanent I/O error occurred during OPEN, CLOSE,or EOV processing and an IMS DCB abnormaltermination exit received control. In the message text,xxxxxxxx is the ddname being processed at the timeof the abend. z/OS also issues a message to describethe abend; the z/OS console log contains this messagerelated to this ddname.

System actionIMS ignores the abend and switches to the nextavailable spool data set.

Programmer responseEnsure that there is a spool data set available. If thereis no spool data set available, schedule the spool printutility to unload the spool data sets. Additionally, inan XRF environment, consider issuing a takeover andallocating new spool data sets. As long as there isno spool data set available, IMS queues all messagesdestined to the spool LTERM to the message queue.This problem can lead to an abend 0758.

Module:DFSDN155


DFS0477A INVALID CLOCK SETTING.EXCESSIVE UTC OFFSET. RESETCLOCK AND REPLY C FORCONTINUE OR A FOR ABORT.

ExplanationThe UTC offset must be within the range of -11:00to +14:00 hours. The value is outside this range. Theoperator probably made an error in the SET CLOCKcommand.


http://www-01.ibm.com/support/knowledgecenter/SSLTBW_2.4.0/com.ibm.zos.v2r4.idad500/d5012.htm?lang=en


This message is a WTOR message, and systeminitialization is suspended until the operator replies.IMS might reissue this message if the clock setting isstill invalid after the operator replies.

System actionIf the operator replies C, IMS initialization continues. Ifthe operator replies A, IMS terminates abnormally withabend 0525, subcode 03.

Operator responseIf you can correct the error by a SET CLOCKcommand, enter the SET CLOCK command beforereplying to this message. If you cannot correct theerror without an IPL, enter the abort option (A) to allowIMS to make an orderly shutdown.

Module:DFSTIME0


DFS0478A INVALID CLOCK SETTING.EXCESSIVE UTC OFFSET. RESETCLOCK IMMEDIATELY.

ExplanationThe UTC offset must be within the range of -11:00 to+14:00 hours. The value was outside this range. Theoperator probably made an error in the SET CLOCKcommand. This highlighted message indicates that theoperator act immediately.

System actionThis message remains highlighted until the clock iscorrected.

Operator responseEnter a SET CLOCK command with the correct clocksetting or local time value.

The system continues to process transactions, but thestored time stamps are not convertible to the currentlocal time. Correcting the clock to a valid local timeeliminates the cause of this message and removes thehighlighted messages from the screen.

If entering the correct local time value does notcorrect the problem, the TOD clock must contain aninvalid UTC value. An IPL might be required to set acorrect UTC value in the TOD clock.

Module:DFSTIME0

DFS0479A ISSUE UNQUALIFIED GN FAILED =xx

Explanationxx indicates the DL/I status code for the error.

System actionProcessing stops.

Programmer responseCorrect the JCL error indicated by the DL/I statuscode. See the DL/I status codes information.

Module:DFSMAID0

Related referenceDL/I status codes (Messages and Codes)

DFS480E REQUESTED MODULE NOT FOUND,NAME=module_name

ExplanationModule module_name could not be loaded whileexecuting in a persistent JVM dependent regionenvironment. This message precedes messageDFS554A, which indicates a S806 abend.

System actionThe application is terminated.

System programmer response:Ensure the module is correctly specified inthe dependent region STEPLIB or equivalentconcatenation, so the module can be found and loadedby the system.

Module:DFSPCC20


DFS0481A CANNOT ALLOCATE STORAGE-GETMAIN

ExplanationAn error occurred while trying to obtain storage.

System actionProcessing stops. Storage is not allocated.



http://www.ibm.com/support/knowledgecenter/SSEPH2_15.1.0/com.ibm.ims15.doc.msgs/compcodes/ims_dlistatuscodes.htm#ims_dlistatuscodes

System programmer responseIncrease the region size in the startup JCL.

Module:DFSMAID0

DFS0482A PARTITION SIZE SELECTION TOOSMALL

ExplanationThe selection size for a HALDB partition was too small.


System programmer responseIncrease the size for the HALDB partition selection.

Module:DFSMAID0

DFS0483A HD UNLOAD ENCOUNTERED ANERROR OPENING THE SYSINDATASET

ExplanationThe data set described by the SYSIN DD card was notable to be opened.

System actionProcessing is halted.

User responseCorrect the data set referenced by the SYSIN DD card.

Module:DFSURGU0

DFS0484A THE FOLLOWING DATASETS FORDATA BASE dbdname ARENOT REGISTERED TO DBRC:ddname1 . . . . ddnamen

ExplanationDL/I open processing for database dbdname failedbecause the open data sets listed are not registeredin the RECON data set, although the database isregistered.

System actionMessage DFS0730I with reason code I,35 is issued.See System Action for message DFS0730I.

Programmer responseUse the DBRC INIT.DBDS command to registerthe data sets in the RECON data set so that thenecessary recovery-related information is recordedduring execution.


Module:DFSDDUI0

Related information“DFS0730I” on page 257UNABLE TO OPEN OR CLOSE DATASET WITHDDNAME ddname FOR REASON x, yy, zDATABASE dbdname programid“IMS problem determination” on page 11IMS messages and codes problemdetermination is accomplished by usingprocedures established by IBM.

DFS0485W RECOVERY DATA FOR [DATABASE dbdname|AREA areaname]MISSING FROM THE RECONDATASET

ExplanationRecovery information for database dbdname or areaareaname might be missing from the RECON dataset. The database or area is being opened for updatewith DBRC so that log data sets generated during theexecution are recorded in the RECON data set. In aprevious run when update ACCESS to the databaseor area was allowed, DBRC was not used. Therefore,unless explicit action was taken, the RECON data setcontains no record of log data sets from previousexecutions necessary to generate valid recovery JCL.

If the log data sets from the previous executionswere explicitly added to RECON, then this messageconfirms that the RECON is again being used to recordrecovery information. If an image copy was recorded inRECON since the last update of the database or areathat did not use DBRC, and if the log data sets fromthe previous executions were not recorded in RECON,then this message indicates that recovery from imagecopies before the updates without DBRC are invalid.

System actionExecution continues. The DBRC usage indicator (DUI)in the database is updated with the identification ofthe RECON data sets that currently record recoveryinformation.


Programmer responseYou can take one of the following actions:

• Use the appropriate DBRC commands to manuallyupdate the RECON data set to ensure that alllogs required as input for recovery or changeaccumulation are recorded.

• Take and record an image copy of the database(or area) in the RECON data set to provide a newrecovery base.

The first execution that opened this database or areafor update processing without DBRC issued messageDFS0486W.

Module:DFSDDUI0, DBFMOPC0

DFS0486W THE RECON DATASET WILL NOTBE UPDATED FOR [DATA BASEdbdname|AREA areaname]

ExplanationThe database dbdname or area areaname wasbeing opened for update processing without DBRCcontrol. Although DBRC was used during the previousexecution for which update ACCESS to the database orarea was allowed, log data sets generated during thecurrent execution will not be automatically recorded inthe RECON data set. Unless explicit action is taken, theRECON data set will not contain the necessary datato generate JCL for valid Database Recovery utilityprocessing.

Important: The conditions that cause this messageto be issued should always remain under direct usercontrol.

If the named database or area is concurrently beingupdated by subsystems that are using DBRC andperforming database or block level data sharing,then allowing execution to continue without directDBRC control might jeopardize the integrity andrecoverability of the database or area.

System actionExecution continues. The DBRC usage indicator (DUI)in the database is updated to reflect that this databaseor area is being updated without DBRC.

Programmer responseYou can take one of the following actions:

• Use the appropriate DBRC commands used tomanually update the RECON data set to ensure thatall log data sets required as input for recovery or forchange accumulation are recorded.

• Take and record an image copy of the databaseor area in the RECON data set to provide a newrecovery base.

Change the JCL for all subsystems that access thisdatabase or area so that they all use the same RECONdata sets and DBRC.


DFS0487W THE RECON DATASET USEDFOR [DATA BASE dbdname|AREAareaname] HAS CHANGED

ExplanationThe database dbdname or areaareaname has beenopened for update processing. This message is awarning that the RECON data set being used to recordthe update logs for the database or area might notcontain the most recent recovery generation datafor the database or area. DL/I (or Fast Path) openprocessing for the database or area detected that theRECON data set used might not be the one used duringthe previous execution to record logs for the databaseor area. The RECON data set, therefore, might notcontain data necessary to generate correct JCL for thedatabase or area recovery processing utilities.

Important: If the area was not opened previously withaccess intent of update or exclusive, this messagecan appear even though the RECON data set has notchanged.

System actionExecution continues. The DBRC usage indicator (DUI)in the database is updated with the identification ofthe RECON data sets which currently record recoveryinformation.

Programmer responseIf the database or area is registered in more thanone RECON data set, ensure that the correct oneis being used for this execution. The appropriateDBRC commands can be used to manually updatethe RECON data set to ensure that all logs requiredas input for recovery or change accumulation arerecorded, or an image copy of the database or areashould be taken and recorded in the RECON data set toprovide a new recovery base.


DFS0488I DBR | DBD | STA |STO COMMAND COMPLETED.DATAGROUP (groupname)


or

DBR | DBD | STA | STO | LOCK | UNLOCK COMMANDCOMPLETED. DBN=database_name RC=nn.

or

DBR | DBD | STA | STO | VUN COMMANDCOMPLETED. DBN | AREA | ADS=database_name |area_name | adsname RC=nn

or

UNLOCK COMMAND COMPLETED. RC=nn

or

DBR | DBD | STA | STO COMMAND COMPLETED.KEYWORD ALL

ExplanationThe /DBRECOVERY, /DBDUMP, /START, or /STOPcommand processing is completed. A zero returncode indicates that the named database has beensuccessfully processed. The ADS specification iseffective only for the /STOP command. The areais only for the /DBRECOVERY, /START, and /STOPcommands. A nonzero return code indicates that anunexpected error was encountered while processing.

If the data group contains both full function and FastPath databases, you might see a command completemessage before seeing any messages indicating FastPath areas did not start successfully.

The /VUNLOAD command completed processing forarea xxxxxxxx. DFS0488I is only issued for areas forwhich the /VUNLOAD command failed, along with thereason code. The reason code indicates the result ofthe command. A final DFS0488I message is issued toindicate that the command is completed.

For the second form of the message, the return codenn can have the value 00, 04, or 20.

The third and fourth forms of the message are issuedto avoid excessive individual messages for successfuloperations.

When the keyword ALL is specified, one DFS0488I isissued for every database name, area name, or ADSname in error, followed by a final DFS0488I DBR|DBD|STA|STO|VUN COMMAND COMPLETED message.

DFS0488I is not issued for each database name, areaname, or ADS name with return code of 00 (RC=00indicates that the command was successful).

This message is only received for the LOCK commandthat is issued from an OM API.

Return code (Dec)Meaning

01The requested state and the current authorizationstate (see the RECON data set) are incompatible.The database is authorized by another active orabnormally terminated IMS subsystem, and itsauthorization state is incompatible with the currentauthorization request.

02The global command was not able to synchronizewith all data sharing partners. The command wascompleted on the subsystem that received thismessage, but the partners must be interrogated todetermine if the command completed successfully.

03The database is marked as prohibiting furtherauthorization for one of the following reasons; aglobal /DBRRECOVERY, a global /STO, or a DBRCCHANGE.DB(NOAUTH) command.

04An error occurred at the close of the database. Fordetailed information about the reason codes, referto message DFS730I.

Module DFSMDA00 can also issue return code4 if dynamic allocation or deallocation failed.This code indicates an interface problem betweenanother IMS module and the IMS dynamicallocation module, DFSMDA00. This code can alsoindicate a missing or bad DFSMDA00 member.

For a /VUNLOAD command, the area specified wasnot found in any data space or coupling facilitystructure. Verify that the area name is correct.Issue a /DISPLAY FPVIRTUAL command to findwhich areas are in data spaces or coupling facilitystructures.

For the second form of the message, thisreturn code indicates that the /UNLOCK SYSTEMcommand was only partially successful. At leastone tolerated block or CI could not be purged.Enter the /UNLOCK SYSTEM command again later.

Return code 04 can also mean that the database isauthorized only if the requested state is "READ" or"READ-GO" because of a global /DBD command.

05The database is marked as needing an image copy.


06The database is marked as needing recovery.

07The database is marked as needing backout.

08Dynamic allocation failed (from DFSMDA00). Thiscode indicates that the IMS dynamic allocationmodule (DFSMDA00) received a nonzero returncode from MVS dynamic allocation.

For a /VUNLOAD, /STOP AREA GLOBAL, /DBRECOVERY AREA GLOBAL, or /STOP ADScommand, an attempt to get the VUNLOADlock for an area in a coupling facility structurefailed. The /VUNLOAD, /STOP AREA GLOBAL, /DBRECOVERY AREA GLOBAL, or /STOP ADScommand is terminated. The VUNLOAD, STOP, orDBR processing is not done.

09During authorization change processing, IRLMcould not identify one or more subsystems.You might have IRLM=N or another IRLM namespecified on the subsystem.

11An invalid parameter was found duringthe evaluation process for database-usagecompatibility. The database record in the RECONdata set might be invalid.

12Dynamic allocation or deallocation failed becauseno storage was available from DFSMDA00.

Return code 12 can also mean that the currentauthorization state in DBRC is invalid because of anunauthorization error.

14The named database cannot be started because ofone of the following possible conditions:

• DBRC has already authorized other READaccess users in the other IMS subsystem toaccess the database. The granted authorizationlevel for the other subsystem is incompatiblewith the original authorization level for thecurrent subsystem because of the last /DBDUMPcommand issued. As a consequence, the originalauthorization level cannot be restored for thecurrent subsystem.

• The changed database authorization level hasbeen requested through the /STA DB ACCESScommand. The request for the change in theACCESS parameter failed because the databasewas incompatible with the authorization levelcurrently held in the other IMS subsystem.

Return code 14 can also mean that an erroroccurred in DBRC while trying to process a changeauthorization request.

15The duplicate AREA entry on the /DBRECOVERYAREA command is ignored. The area was alreadyunauthorized by DBRC.

16Dynamic allocation or deallocation failed becauseof a system error. For detailed information aboutthe reason codes, refer to message DFS2498I.

20For the /UNLOCK SYSTEM command, one of thefollowing conditions occurred:

• There were no EEQEs to purge.• The /UNLOCK command was entered on an IMS

system that is not XRF-capable.• The /UNLOCK command was entered on an

active system that was not a previous alternatesystem. This command must be entered only onthe alternate system.

• The /UNLOCK command was entered on thealternate system before the alternate systemcompleted the XRF takeover. This commandmust be entered on the alternate system onlyafter one or more of the following events haveoccurred:

– The failing active system has terminated– The processor containing the failing active

system has been reset– I/O prevention on the active system is

complete

21One of the following occurred:

• A VLOCK request cannot be granted whenprocessing a /START AREA, or a /VUNLOADAREA command. The area is marked asSTOPPED. One sharing IMS system is holding theretained VLOCK exclusive.

• While processing either a /VUNLOAD AREA, ora /START AREA command, an IMS sharingpartner noted an inconsistency in the VSOoptions between the DEDB area control block(DMAC) on DASD and the DMAC in storage. Thearea is marked as STOPPED.

Issue a /START AREA command to correct theinconsistency.

• During /VUNLOAD, or a /START AREA commandprocessing, an IMS sharing partner noted aninconsistency in VSO options between the DMACon DASD and the DMAC in storage. The AREA


is stopped. Issue a /START AREA command tocorrect the inconsistency.

• During /START AREA command processing, anIXLFORCE command is issued to delete anyfailed persistent connections from a prior failedsystem. The IXLFORCE command was not ableto delete the failed persistent connection. In thiscase, the following messages are generated:

– DFS2783A UNABLE TO DELETE FAILED-PERSISTENT CONNECTION TO STR:SSSSSSSSSSSSSSSS REASON=RRRR

– DFS0488I STA COMMAND COMPLETED.AREA= XXXXXXXX RC=21

24A command with the ALL keyword is not processedfor a Fast Path MSDB. If /START DB ALL accessis entered, module DFSDBDR0 does not includeMSDBs.

28The named database cannot be started because ofthe following conditions:

• The request to change the databaseauthorization level to a data entry database(DEDB) has been requested through the /STARTDB ACCESS command. The change of anauthorization level to a DEDB cannot be donebecause the referenced DEDB is in use by aregion.

• Changing the DEDB access intent requiresstopping the scheduling of all PSBs thathave access to the target DEDB. This codemight require stopping regions in which PSBsassociated with WFI transactions are currentlyscheduled, and stopping the transactions orPSBs for non-WFI transactions.

31A /START AREA command failed because the areais marked as recovery-needed in the DBRC RECONdata set, or the DBRC RECON indicates that thereare no available area data sets for the area.

34Because a /START DB ACCESS command wasissued, a change database authorization requestwas made from IMS to DBRC. The encodeddatabase state returned from DBRC was set to avalue of zero.

35A backout error occurred for the database. A /START command for the database is invalid untila /DBRECOVERY command is issued and batchbackout is performed.

37One of the following events occurred:

• A write error occurred for the database. Thecommand issued is invalid until a /DBRECOVERYcommand is issued.

• A request for a new dataspace was issued duringthe open processing for a shared VSO area. Referto message DFS2444I, that precedes messageDFS0488I.

38A /START DB command was not run because thedatabase was being extended during an IMS XRFtakeover, and I/O Prevention was not yet complete.You cannot start the database until IMS knows thatI/O Prevention is complete.

39A /START DB command specifying ACCESS=ROor RD is invalid while incomplete, restartableback outs exist for the database. IMS must haveupdate or exclusive access to the database to redothe incomplete back outs. The command is notprocessed for the specified database.

41The area is not loaded into the Coupling Facility.This code does not prevent access to thearea unless this code is preceded by messageDFS2819A.

42The named HALDB partition cannot be processedin response to a /START DB command becauseof an error in the Partition Structure Manager.Check the system console for related DFS0415Wmessages.

43The named database cannot be processed inresponse to a /DBRECOVERY command becauseone or more in-doubt EEQEs exist for the databaseand the NODBR keyword was specified in theDFSVSMxx member of the IMS PROCLIB data set.

44When the /STOP ADS command is entered, theADS of the named ddname is already stopped.This /STOP ADS command is ignored.

45A /DBR, /DBD, /STA, or /STO command wasissued against the named database or HALDBpartition that is QUIESCED or has QUIESCEin progress. Try the command again after theQUIESCE has been released. If the quiesce isin a held state, release it with an UPDATE DBSTOP(QUIESCE) command.

50A /DBRECOVERY, /START, or /STOP commandwas issued with AREAGROUP or DBGROUP, wherethe AREAGROUP contained a specified databaseor the DBGROUP contained a specified area. The


command is not processed for databases in anAREAGROUP or areas in a DBGROUP.

On a system that is defined to support Fast Path,the keyword 'MSDB' was entered on a /START, /STOP, or /DBRECOVERY command. (MSDB isallowed on /DBDUMP.) The keyword is ignored andthe remainder of the command is processed.

52A /DBRECOVERY or /START command wasentered for a database that was in the process ofbeing recalled from HSM. The command processis not performed at this time. The /DBRECOVERYcommand must be entered again after thedatabase is recalled. The /START command willbe automatically performed after the recall iscomplete.

54There is a discrepancy between the number of ADSallocated by IMS and the number of ADS known toDBRC. Correct the discrepancy, then reissue the /DBRECOVERY or /STOP command to deallocate thedata sets.

55The command failed because the FF DB or FP areais currently being recovered.

56An error occurred while attempting to openthe named database or HALDB partition. Checkthe System Console for message DFS0730I todetermine the reason for the failure.

57The named database is a HALDB master andis invalid with the OPEN keyword. However, apartition structure rebuild is attempted if neededand if only one HALDB master was specified in thecommand. No rebuild is attempted if more thanone database name is listed in the command.

58The named HALDB partition cannot be processedin response to a /DBDUMP, /DBRECOVERY, /START, or /STOP command. It is still in useby an active HALDB OLR. The command is notprocessed for the HALDB partition named in themessage. However, processing continues for anyother databases or HALDB partitions specified inthe command.

60The command failed because the area has beendeleted by Online Change.

62The named database failed directory initializationor the DBB or PSB pool space was not largeenough to accommodate the blocks. Check the

system console for messages that reference thisdatabase.

70The named database or HALDB partition failedauthorization. Check the system console formessages that are related to the authorizationfailure. Check the status of the named databaseor HALDB master if no messages related to theauthorization failure are found.

71OPEN keyword processing could not continuefor the named HALDB partition because a /DBRECOVERY command has been issued for theHALDB master. Start the HALDB master and thenreissue the command to start the HALDB partition.This situation can also occur if the partition hasbeen deleted and a partition structure rebuild hasoccurred. You can perform a partition structurerebuild by issuing a /START DB haldbmstOPEN command or UPD DB NAME(haldbmst)START(ACCESS) OPTION(OPEN) command,where haldbmst is the master of the partition, or byissuing a qualified GU call for a key in the key rangeof the partition. You can use the LIST.RECONcommand to determine if the partition exists or hasbeen deleted.

72Partition DBM build failed for the namedHALDB partition. Check the System Console forDFS0415W messages to determine the reason forthe failure.

73DMB build processing failed for the nameddatabase or HALDB partition. Check the systemconsole for DFS0561 or DFS0592I messages todetermine the reason for the failure.

74DMB build processing failed for the nameddatabase or HALDB partition because the datamanagement block pool (DMB pool) is too smallto hold all the required data management blocks.Change the appropriate parameter to make thepool larger and restart the system. MessageDFS0992I might also be issued.

75DMB build processing failed for the nameddatabase or HALDB partition. IMS detected a DMBpool shortage while attempting to load the DMBblock for the named database or HALDB partition.The size of the DMB pool must be large enoughto accommodate all DMBs that are actively beingused. Change the appropriate parameter to makethe pool larger and restart the system.


76DMB build processing failed for the nameddatabase or HALDB partition. Check the SystemConsole for DFS0564I messages to determine thereason for the failure.

77DMB build processing failed for the nameddatabase or HALDB partition. An unexpectedreturn code was received. Check the systemconsole for any related messages and contact IBMSoftware Support.

79The command was issued for a database that isstill being processed by Restart Parallel DatabaseOpen. Wait for that process to complete and try thecommand again.

80The named DEDB database cannot be started in anon-FP system.

81This message is generated because the userissued a /VUN command for an area in a databasethat was read authorized. The /VUN commandmust be entered on an IMS subsystem that hasupdate authorization for the database.

82A /DBR, /STO or /VUN area command wasissued against an area that is quiesced.Stop the quiesce by issuing a UPDATE AREASTOP(QUIESCE) command and issue thecommand again.

83For the /UNLOCK command, an internal startdatabase (/STA ) command failed because ofCommon Service Area (CSA) shortage. Issue amanual /STA DB command for each databasethat has received message DFS0451I with the textIEQE FOUND.

84The /START, /STOP, /DBR, or /DBD command forthe database could not be processed because theresource is in the process of being imported fromthe IMS change list or the import from the changelist failed. The resource cannot be acted on by thetype-1 command until it is successfully imported.



Module:DBFARD10, DBFARD40, DBFARDA0, DFSDBDR0,DFSRDSH0, DBFCVUN0


DFS0489I DATA BASE database name ISCHANGED TO INQUIRY ONLYSTATUS

ExplanationThe database identified in the message was changedto INQUIRY ONLY status because the image copyneeded flag is set in the DBRC RECON data set. Whenan Online Image Copy utility is scheduled to copy thedatabase, the database authorization level must bechanged to a read level in order to permit the onlineimage copy to run. The Online Image Copy utility isrequesting the read level authorization on behalf of theIMS subsystem.

System actionIMS processing continues with the online image copy.However, the database is marked for use as inquiryonly.

Operator responseIf an update or exclusive authorization level is requiredfor the online IMS subsystem, enter a /START DBor UPDATE DB START(ACCESS) command after thecompletion of the Online Image Copy utility.


Module:DFSDBAU0


DFS0490I HD UNLOAD OF PARTITIONEDDATA BASES IS NOT SUPPORTEDFOR UCF

ExplanationHD unload of HALDB is not supported for the UtilityControl Facility (UCF).

System actionExecution halts, and the return code is set to 16.


Module:DFSURGU0

DFS0491A ERROR IN DFSCTL DATASET

ExplanationA statement in the DFSCTL data set contained an error.Messages that follow this one display the incorrectline and describe the error. This message displays theaffected region, when possible.

System actionThe region is terminated.

Programmer responseCorrect the line in error based on the messages thatfollow.

Module:DBFPCAA0, DBFPHI00, DBFPHI10, DBFPHI20,DBFPHI30

DFS0492I line in error

ExplanationThis message displays the incorrect line in the DFSCTLdata set. At least one more message follows thisone to provide additional information. This messagedisplays the affected region, when possible.


Programmer responseCorrect the error based on the information in thismessage and the next messages.

Module:DBFPCAA0, DBFPHI00, DBFPHI10, DBFPHI20,DBFPHI30

DFS0493I INVALID CHARACTERS INDATABASE NAME

ExplanationThe database name in the statement shown inmessage DFS0492I contained invalid characters.


Programmer responseCorrect the line in error.

Module:DBFPCAA0

Related information“DFS0492I” on page 175line in error

DFS0494I NO DATABASE NAME GIVEN

ExplanationThe statement shown in message DFS0492I did notspecify a database name.



Module:DBFPCAA0


DFS0495I NO PCB LABEL GIVEN

ExplanationThe PCB label was missing in the statement shown inmessage DFS0492I.



Module:DBFPCAA0


DFS0496A PARTITION SELECTION FOR DATABASE DATASET FAILED

ExplanationHDUNLOAD encountered an error from IMS PartitionSelection while preparing to unload the database


segments for a partition or range of partitionsbelonging to the database specified on the jobparameter card.

System actionProcessing halts with return code 16.

User responseVerify that the database input on the job parametercard is correct. If you specified a range ofpartitions in the SYSIN using NUMBER= (for example,PARTITION=PART2,NUMBER=5) then you might needto correct the range value or correct RECON bydefining additional partitions. Consult your partitionselection exit routine to identify partition names withinthe scope of the range.

If partitions are missing, define them using thePartition Definition utility TSO panels and resubmit thejob.

Module:DFSURGU0

DFS0497I INVALID CHARACTERS IN PCBLABEL

ExplanationThe PCB label in the statement shown in messageDFS0492I contained invalid characters.



Module:DBFPCAA0


DFS0498I INVALID DATABASE NAMELENGTH

ExplanationThe length of the database name in the statementshown in message DFS0492I was invalid. The namemust be from 1 to 8 characters in length.



Module:DBFPCAA0


DFS0499I INVALID PCB LABEL LENGTH

ExplanationThe length of the PCB label in the statement shown inmessage DFS0492I was invalid. The PCB label mustbe from 1 to 8 characters in length.



Module:DBFPCAA0


DFS0500I DANGLING COMMA ON END OFSTATEMENT

ExplanationThe statement shown in message DFS0492I ends witha comma.



Module:DBFPCAA0





DFS0501I IC OPTION SPECIFIED FOR NONPROCOPT H PCB x. RGN n

ExplanationPCB x specified the image copy (IC) option, but notprocessing option H (PROCOPT=H). The IC option isonly valid for PROCOPT H PCBs.


Programmer responseEither remove the IC option for this PCB, or specifyPROCOPT H and rerun PSBGEN.

Module:DBFCPY00

DFS0502I MULTIPLE DATABASE NAMESGIVEN

ExplanationThe statement shown in message DFS0492I containedtwo DATABASE= (or DB=) keywords.



Module:DBFPCAA0


DFS0503I DATABASE x NOT FOUND INSYSTEM. RGN n

ExplanationIn the statement shown in message DFS0492I, theDATABASE= (or DB=) keyword specified a databasethat does not exist.



Module:DBFPHI00


DFS0504A NO PCB FOUND WITH LABEL xFOR DATA BASE y. RGN n

ExplanationNo PCB was found with label x for database y.



Module:DBFCPY00

DFS0505I MULTIPLE PCB LABELS GIVEN

ExplanationThe statement shown in message DFS0492I containedtwo PCB= keywords.



Module:DBFPCAA0

Related information“DFS0492I” on page 175


line in error

DFS0506I SUBSET POINTER IS NOT VALIDFOR SENSEG segmentname IN PCBdbdname IN PSB psbname

ExplanationThe SSPTR subset pointer is specified in the SENSEGstatement but not defined in the corresponding SEGMstatement. In the message text:segmentname

The SENSEG that contains the invalid subsetpointer.

dbdnameThe SEGM segmentname of the DBD that does nothave the SSPTR subset pointer defined.

psbnameThe PSB that contains the invalid statement.



• If the application program does not use a subsetpointer, ignore this message.

• Remove the SSPTR subset pointer from the SENSEGstatement in the PSB. Then rerun the PSBGEN, thenrerun the ACB utility with a BUILD statement for thePSB.

• Add the SSPTR subset pointer in the SEGMstatement in the DBD. Then rerun the DBDGEN, thenrerun the ACB utility with a BUILD statement for thePSB.

Module:DBFUDLB0

DFS0507I PRIMARY MASTER LOGICALTERMINAL IS NOT DEFINED

ExplanationIMS initialization detected that the primary masterlogical terminal (PMTO) was not defined in the system.

System actionIMS initialization terminates with abend 3477.

System programmer responseEnsure that the PMTO is properly specified in thesystem definition.

Module:DFSAINB0


DFS0508I ADJACENT COMMAS INSTATEMENT. RGN n

ExplanationThe statement shown in message DFS0492I containedadjacent commas (,,).



Module:DBFPCAA0, DBFPHI10, DBFPHI20


DFS0509A PARTITION SELECTION FAILED

ExplanationA logic error was encountered when accessing aHALDB partition for an online change copy.

System actionThe utility ends with a return code of 08.

System programmer responseExamine a list history for the partition DBDS beingcopied to determine the cause.

Module:DFSUICP0

DFS0510E THE SETI STATEMENT IS INVALID.RGN n

ExplanationThe statement shown in message DFS0491A orsubsequent messages contained an invalid programspecification block (PSB) name. n is the region IDnumber.

The PSB=psbname on the set index maintenance off(SETI) statement in the DFSCTL data set for the BMPapplication is used to suppress index maintenancefor Fast Path secondary index databases that are



referenced in the BMP application. However, there wasan error in the PSB= parameter in the SETI statement.

One of the following errors occurred:

• The PSB name in the PSB= parameter in the SETIstatement does not match the PSB name of the BMPapplication.

• The PSB= parameter is omitted from the SETIstatement.



Module:DBFPCAA0, DBFINTE0

Related information“DFS0491A” on page 175ERROR IN DFSCTL DATASET

DFS0511I DUPLICATE OPTIONS FOR DB=xAREA=y. RGN n

ExplanationThe area was specified twice, either implicitly orexplicitly, in the SETO statement shown in messageDFS0492I.



Module:DBFPHI10


DFS0512I UNRECOGNIZED KEYWORD. RGNn

ExplanationThe SETO statement shown in message DFS0492Icontained an invalid keyword.



Module:DBFPHI10, DBFPHI20


DFS0513I NO PARAMETERS SPECIFIED ON xKEYWORD. RGN n

ExplanationNo parameter list followed the IC= (or NOIC=)keyword on the SETO statement shown in messageDFS0492I.





DFS0514I UNRECOGNIZED TEXT AFTERENDING PAREN ON x KEYWORD.RGN n

ExplanationIMS did not recognize the text between the IC= (orNOIC=) keyword parameter list and the next comma(for example, IC=(AREA1)bad,). Message DFS0492Ishows the SETO statement containing the error.



ModuleDBFPHI10, DBFPHI20



line in error

DFS0515I INVALID AREA NAME LENGTH.RGN n

ExplanationThe length of an area name in the statement shown inmessage DFS0492I was invalid. Area names must befrom 1 to 8 characters in length.



Module:DBFPHI30


DFS0516I INVALID CHARACTERS IN AREANAME. RGN n

ExplanationAn area name in the statement shown in messageDFS0492I contained invalid characters.



Module:DBFPHI30


DFS0517I AREA x NOT FOUND IN DATA BASEy. RGN n

ExplanationArea x was not defined in database y.



Module:DBFPHI30

DFS0518I INVALID DASH SEPARATOR. RGNn

ExplanationIn the statement shown in message DFS0492I, a dashseparated 3 or more area names (for example, IC=(A1-A2-A3)).





DFS0519I AREAS x AND y ARE IN THEWRONG ORDER. RGN n

ExplanationIn the statement shown in message DFS0492I, areasx and y, which are the starting and ending points foran area range, were in the wrong order. Areas must bespecified in DBDGEN order.





DFS0520I TERMINATION ITASK WAITS DUETO LONG BUSY FAST PATH ADSAREA=areaname DDN=ddname


ExplanationDuring shutdown processing, IMS determined thatone or more Fast Path ADSs is under a Long Busycondition. The Long Busy Recovery must finish beforeshutdown processing continues.

In the message text:areaname

The name of the area to which the long busy ADSbelongs.

ddnameThe data description name of the long busy ADSthat is registered in the RECON data set.

System actionThe termination ITASK is posted after the Fast PathLong Busy ADSs complete recovery. IMS shutdownprocessing continues.


Module:DBFTERM0

DFS0521I UNMATCHING PARENTHESIS.RGN n

ExplanationThe statement shown in message DFS0492I containedmore open parentheses than closing parentheses.





DFS0522I AREA x SPECIFIED TWICE INAREA LISTS. RGN n

ExplanationThe area list in the SETR statement shown in messageDFS0492I contained the area name twice.



Module:DBFPHI20


DFS0523I UNRECOGNIZED TEXT AT END OFAREA LIST. RGN n

ExplanationThe text at the end of the area list for an IC= keywordwas invalid. Only 1ABEND, 2ABEND, or CONTINUE(and their synonyms) are valid for the end of the arealist.



Module:DBFPHI10

DFS524I DFSZDI00-GSAM INIT.AUTHORIZATION DENIED

ExplanationThe IMSAUTH macro returned a nonzero codeindicating that module DFSZDI40 is not in theauthorized library.

System actionThe region is terminated with abend 0657 and amemory dump.

Operator response:Rerun the job. If the situation persists, contact yourIMS system programmer.

Programmer responseVerify the status of the IMS libraries.

Module:DFSZDI40



DFS0525A A PROCOPT H PCB WASSPECIFIED TO AN xxx REGION.PCB x IN PSB y. RGN n

ExplanationPCB x in PSB y specified processing option H, but theregion is an IFP, MPP, message-driven BMP, WFI BMP,or CCTL thread. In addition, the JCL for this regioncontains some SETO statements in the //DFSCTL dataset. Programs using HSSP (PROCOPT=H) can only runin a BMP region.

System actionFor an IFP, MPP, message-driven BMP, or WFI BMP,the region is terminated with abend 1060. For a DBCTLthread, the 1060 abend code is returned to the CCTLto indicate a schedule failure.

Programmer responseAn IFP, MPP, message-driven BMP, WFI BMP, or DBCTLthread cannot schedule a PSB containing a PCB usingprocessing option H. Correct the processing option.

Module:DBFCPY00


DFS0526A AN INCONSISTENCY EXISTSBETWEEN THE PSB AND THEDEDB'S DBD. PCB x IN PSB y. RGNn

ExplanationThe DBD was changed in the DBDLIB and was used foran ACBGEN to build a PSB. A warning message wasissued during ACBGEN that the DBD was not replacedin the ACBLIB.

System actionAbend code 1013 is returned to the CCTL to indicate aschedule request failure.

Programmer responseRerun the ACBGEN utility to correct the inconsistencybetween the PSB and the DBD.

Module:DBFCPY00


DFS0527A A GETMAIN FAILED TO OBTAINSEGMENT WORKAREAS IN SP231ECSA. ECSA NEEDS TO BE FREEDUP.

ExplanationIMS was unable to obtain the requested storage.

System actionAbend code 1061 is returned to the CCTL to indicate aschedule request failure.

Programmer responseFree ECSA storage and rerun the job.

Module:DBFCPY00, DBFCPY20


DFS0528I PSTOP/STOP CMD FOR RGN nnnnWAITING IN QSN EXIT. CODE = x

ExplanationThe dependent region was placed in a wait state byDFSQSPC0, the IBM IMS Queue Control Facility forz/OS version of the Queue Space Notification Exit.The wait state occurred based on IMS queue usage,which exceeded the user or default limits. While thedependent region was in a wait state, a /STOP or /PSTOP command was entered against the region. Toterminate an application program or region in thisstate, use one of the following methods:

• Use the QCF TSO/ISPF interface.• Enter a /STOP REGION x ABDUMP tranname

command to terminate the application program,and then enter a /STOP REGION x command toterminate the region.


The dependent region that was placed in a waitstate.

xThe reason code, which can be one of thefollowing:1

Indicates that the dependent regionterminates with abend 0408. This abend






is normal if a /STOP REGION x ABDUMPtranname command was issued.

2Indicates that the region is no longer waiting inthe queue space notification exit, or it was notrecognized in that state when the commandwas issued.

3Indicates a failure to acquire space to processa /STOP or /PSTOP command (DFSSTOP). Thiserror should not occur.

System actionNone.

Operator responseTake the appropriate action based on the return code:1

Enter the /DISPLAY ACTIVE REGION command.If the status that displays is WAIT-QSN, entera /STOP REGION x ABDUMP tranname commandto terminate the application program, then entera /STOP REGION x command to terminate theregion. If reason code 1 is received persistently fora specific region, report the problem to the systemprogrammer.

2Enter the /DISPLAY ACTIVE REGIONcommand. If the status that displays is WAIT-QSN, enter a /STOP REGION x ABDUMP trannamecommand to terminate the application program,then enter a /STOP REGION x command toterminate the region. If message DFS0528I occursagain with reason code 1 when the /DISPLAYcommand continues showing WAIT-QSN, reportthe problem to the system programmer.

3Report the problem to the system programmer.

System programmer responseIf reason code 1 persists, or reason code 3 is issued,call the IBM Software Support for assistance.

Module:DFSSTOP0


DFS529E AN INVALID VALUE IS SPECIFIEDON THE JVM EXEC PARAMETER

ExplanationA dependent region cannot be initialized becausean invalid value is specified on the positional JVMparameter in the PARM= list of the EXEC job controlstatement.

System actionThe dependent region is terminated abnormally.

Operator responseCorrect the value that is specified on the JVMparameter in the EXEC job control statement and runthe job again.

Valid values for the JVM parameter are 31, 64, or3164. The value 64 is only valid for the JMP and JBPdependent regions types.


Module:DSFRRA40

DFS0530I DFSZDC00 I/OERROR DBDNAME=dbdnameDDNAME=ddnameGBCRTNCD=xxxx

ExplanationThe GSAM controller has detected an error writing outbuffers during a purge or checkpoint operation.

xxxx is the 2-byte field GBCRTNCD in hexadecimal.See GB DSECT for definition of the GBCRTNCD fieldbits.

System actionGSAM terminates with abend 0271.

Programmer responseUse a data recovery procedure to reconstruct the dataset in error.

Module:DFSZDC00


DFS0531I IMAGE COPY DATASET OPENFAILED




or

REASON CODE=01 AREA=areaname REGID=regidDEVICE TYPE NOT SUPPORTED. DD=ddnameDSN=dsname

or

REASON CODE=02 AREA=areaname REGID=regidMAXIMUM PICS ALREADY EXIST

or

REASON CODE=03 AREA=areaname REGID=regidAREA IS NOT REGISTERED IN DBRC

or

REASON CODE=04 AREA=areaname REGID=regidINVALID PARAMETER FOUND IN DBRC

or

REASON CODE=05 AREA=areaname REGID=regidINTERNAL DBRC ERROR

or

REASON CODE=06 AREA=areaname REGID=regidDBRC DID NOT HAVE ENOUGH IDS(S)

or

REASON CODE=07 AREA=areaname REGID=regidNO IDS(S) COULD BE USED

or

REASON CODE=08 AREA=areaname REGID=regidAREA DOES NOT HAVE REUSE ATTRIBUTE

or

REASON CODE=09 AREA=areaname REGID=regidHSSP IC ALREADY IN PROCESS

or

REASON CODE=10 AREA=areaname REGID=regidDUPLICATE DDNAME FOUND DD=ddnameDSN=dsname

or

REASON CODE=11 AREA=areaname REGID=regidSPACE FOR IDSC(S) UNAVAILABLE DD=ddnameDSN=dsname

or

REASON CODE=13 AREA=areaname REGID=regidQSAM OPEN CIC XFP TCB RETRY DD=ddnameDSN=dsname

or

REASON CODE=14 AREA=areaname REGID=regidGETMAIN FAILED - DBRC BLKS

or

REASON CODE=15 AREA=areaname REGID=regidQSAM OPEN FAILED DD=ddname DSN=dsname

or

REASON CODE=16 AREA=areaname REGID=regidGETMAIN FAILED FOR HSSP IC BLOCKS ANDBUFFER

or

REASON CODE=17 AREA=areaname REGID=regidALLOC FAILED DDNAME NOT FOUND IN TIOTDD=ddname DSN=dsname

or

REASON CODE=18 AREA=areaname REGID=regidEEQE EXISTS WITHOUT A BUFFER


or

REASON CODE=19 AREA=areaname REGID=regidAREA IS NONRECOVERABLE

or

REASON CODE=20 AREA=areaname REGID=regidRDJFCB/MODCB ERROR DD=ddname DSN=dsname

or

REASON CODE=31 AREA=areaname REGID=regidALLOCATED SPACE NOT ENOUGH

ExplanationThe HSSP Image Copy open processing failed for animage copy data set (IDS) or image copy set up. Asecond DFS0531I message provides a reason codeand a brief description of the error.

System actionHSSP Image Copy processing terminated when an IDSopen failure occurred for one of these reason codes:02, 03, 04, 05, 06, 07, 08, 09, 12, 16, and 18.

HSSP Image Copy processing can terminate when anIDS open failure occurs for one of these reason codes:01, 10, 11, 13, 17, 20, 31. Whether the image copyprocess terminates depends on which image copyoptions you specified.

For reason code 19, the HSSP/IC job fails with a userabend 1062.

For all IDS open failure reason codes, HSSP processingcan continue with or without image copy, or mightterminate, depending on which HSSP Image Copyoptions you specified. Valid options are CONTINUE,1ABEND, 2ABEND and IC=0,1,2.

Programmer responseTake the appropriate action based on the reason codeyou received.

CodesAction

01Check the appropriate VSAM catalog or JCL DDstatements to determine if a disk device isspecified for the named IDS. If dynamic allocationoccurred, check the dynamic allocation parameter

list to find the device type specified for the namedIDS. If a device other than a disk was specified,change the device type to the disk device; thenrerun the job.

02Rerun the program as soon as the conflict isresolved. Create a valid image copy.

03Add the missing resource description to DBRC andrerun the program.

04, 05These codes indicate an internal system problem.Contact your IBM Software Support for help.

06, 07, 08Add the missing resource description to DBRC andrerun the program.

09Issue the CHANGE.IC command to terminate theprevious HSSP IC process (creating either a partialor complete HSSP IC data set).

10The ddname identified in the message exists in theIMS subsystem. This means that either the IDSis already opened or the ddname is incorrect. Ifthe IDS is already open, delete the DD statementfor that ddname. If the ddname was incorrect, butmatched another ddname in the IMS subsystem,correct the input ddname; then rerun the job.

11Rerun the job when the common service area(CSA/ECSA) usage is low.

12The user determines the action. (A possible actionis to recover the area and rerun the job.)

13Sequential access method OPEN can abend. Takethe action suggested in the sequential accessmethod message.


15Sequential access method OPEN displays a returncode in sequential access method messages.


CodesExplanation

17If a DD statement is specified, make sure that theddname is correct. If the DD statement is missing,specify a DD statement. If dynamic allocation


failed, take the action suggested in messageDFS2502W or DFS2503W. Then rerun the job.

CodesExplanation

18The user determines the action. (A possible actionis to rerun the job after the EEQEs owned by thesharing system have been purged for this area.)

CodesExplanation

19HSSP Image Copy (HSSP/IC) has been requestedfor a nonrecoverable DEDB. Fuzzy image copies arenot permitted for nonrecoverable DEDBs.

Take one of the following actions:

• Remove the nonrecoverable DEDB area from theHSSP/IC specification.

• Run the Image Copy utility or Image Copy 2utility to produce a non-fuzzy image copy.

CodesExplanation

20Delete the physical data set and redefine it. Thenrerun the job.

31Delete the named image copy data set andredefine it with at least as much space as the areadata set. Then rerun the job.


Module:DBFPICE0


DFS0532I IMAGE COPY FAILED FORAREA=areaname[IMAGE COPYITASK CREATE FAILED | IMAGECOPY ITASK ABORTED DURINGINITIALIZATION | EEQE EXISTSWITHOUT BUFFER]

or

IMAGE COPY PROCESS (STARTED|TERMINATED)FOR AREA=areaname REGID=regid, RC=((0|4)|8.)DSN1=dsname1

or

IMAGE COPY PROCESS (STARTED|TERMINATED)FOR AREA=areaname REGID=regid, RC=((0|4)|8.)DSN1=dsname1 | DSN2=dsname2

or

IMAGE COPY STARTED FOR AREA=areaname

ExplanationThe HSSP Image Copy set up finished, and Image Copyeither started, terminated, or failed.

The return codes, explained below, indicate whichaction was taken.

CodesExplanation

00Image copy started successfully with the identifiedDSNs.

04An error occurred while attempting to open animage copy data set. Image copy processingcontinues with the remaining data set (identifiedin the message) according to the user image copyspecifications. Message DFS0531I precedes thismessage and explains the cause of the IDS openfailure.

08An error occurred while trying to open an imagecopy data set or during image copy set up.The image copy process terminates. MessageDFS0531I precedes this message and explains thecause of the image copy set up or open failure.

Note: If the second form of this message is issued,other messages might be displayed between the twoforms of the DFS0532I message.

If the IMAGE COPY FAILED form of the messageappears, the action depends on the text that follows:

• IMAGE COPY ITASK CREATE FAILED indicatesthat a failure occurred during the dynamic creationof an image copy ITASK.

• IMAGE COPY ITASK ABORTED DURINGINITIALIZATION indicates that the image copyITASK aborted; see message DFS0531I.

• EQE EXISTS FOR SAME RBA FOR ALL ADS(S)indicates that an image copy is not possible.

• EEQE EXISTS WITHOUT BUFFER indicates thatdata is unavailable for image copy.


System actionThe image copy process either continues orterminates.

Programmer responseTake the appropriate action based on the informationin the message.

Module:DBFPICS0

DFS0533E SETO WITH IC= AND SETUWITH FPBP64U=Y ARE MUTUALLYEXCLUSIVE PARAMETERS

ExplanationThe HSSP job included the SETO control statementwith IC= specified and the SETU control statementwith FPBP64U=Y specified, which are mutuallyexclusive parameters. 64-bit utility private bufferpools cannot be used with the HSSP image copyprocess.

System actionThe HSSP job terminates with abend code 1060(U1060).

Programmer responseEither remove the IC= option from the SETO statementor remove the SETU statement. Then, resubmit theHSSP job.

Module:DBFPHI10

DFS0534I FPBP64U=Y WAS SPECIFIED ONTHE SETU STATEMENT

ExplanationThe HSSP job included the SETU control statementwith FPBP64U=Y specified. The HSSP job will allocateand use a 64-bit utility private buffer pool.

System actionNo action is required.


Module:DBFPHI00

DFS0535A xxxx DISC PROCESS ATTEMPTEDAREA a

or

RGN=r, xxxx CONN PROCESS ATTEMPTED AREA a,PCB LABEL z

Explanation:See the information for DFS0535I. for a detailedexplanation and actions.

Related informationDFS0535IRC=01, yyyy ALREADY RUNNING

DFS0535I RC=01, yyyy ALREADY RUNNING

or

RC=03, AREA LOCK FAILED

or

RC=04, AREA IS STOPPED

or

RC=05, AREA FAILED TO OPEN

or

RC=06, 2ND CI UPDATE AND/OR NOTIFY FAILED

or

RC=07, UOW LOCK MODE INITIATION FAILED

or

RC=08, INSUFFICIENT STORAGE FORAREA PRIVATE BUFFER POOL. STORAGEREQUESTED=nnnnnnnK. STR MGR RC=xxx

or


RC=09, PRIVATE BUFFER POOL ALREADY EXISTSsysid

or

RC 10, COULD NOT GET AN AWE sysid

or

RC 11, INVALID REQUEST SENT TO DBFPAPB0 sysid

or

RC=12, AREA IS IN A QUIESCE STATE sysid

ExplanationA process was attempted but could not complete forthe reason listed in the message.

• RGN=r, xxxx CONN PROCESS ATTEMPTED AREAa, PCB LABEL z

Process xxxx was not started. Process xxxx can be:

HSREHigh Speed Reorganization utility

HSSPHigh Speed Sequential Processing

PRELVSO preload process

Region r identifies the affected region.• xxxx DISC PROCESS ATTEMPTED AREA a

Process xxxx could not disconnect. Process xxxx canbe:HSRE

High Speed Reorganization utilityHSSP

High Speed Sequential ProcessingPREL

VSO preload process• RC=01, yyyy ALREADY RUNNING

Process yyyy is active on the area or has notdisconnected from the area. Process yyyy can be:DA00

DEDB Alter utilityHSRE

High Speed Reorganization utilityHSSP

High Speed Sequential Processing

MDLODEDB Sequential Dependent Delete utility

MMHODEDB area data set Compare utility

MRIODEDB area data set Create utility

MSCODEDB Sequential Dependent Scan utility

PRELVSO preload process

• RC=03, AREA LOCK FAILED

Process xxxx failed to acquire the area lock for thearea.

• RC=04, AREA IS STOPPED

Process xxxx cannot run on a stopped area.• RC=05, AREA FAILED TO OPEN

The attempt to open area a failed.• RC=06, 2ND CI UPDATE AND/OR NOTIFYFAILED

Process xxxx failed because the IRLM notify failed orthere was an error in the second CI update.

• RC=07, UOW LOCK MODE INITIATION FAILED

The transition to UOW locking mode wasunsuccessful. A probable cause is a failure in thenotify process to a sharing subsystem.

• RC=08, INSUFFICIENT STORAGE FORAREA PRIVATE BUFFER POOL. STORAGEREQUESTED=nnnnnnnK. STR MGR RC=xxx.

Unable to create private buffer pool; sufficientstorage was not available. In the message, nnnnnnnis the number of 1014 bytes of storage requested,and xxx is the return code set by the IMS storagemanager.

• RC=09, PRIVATE BUFFER POOL ALREADYEXISTS sysid

Process xxxx requested the creation of the areaprivate buffer pool but the buffer pool exists already.

• RC 10, COULD NOT GET AN AWE sysid

The request for an AWE control block failed toprocess xxxx.

• RC 11, INVALID REQUEST SENT TO DBFPAPB0sysid

An invoking module passed an invalid request codeto DBFPAPB0.

• RC=12, AREA IS IN A QUIESCE STATE sysid

The process cannot run on a quiesced area.


System actionThe action the system takes are listed for the differentforms of the message:


Process xxxx terminates.• xxxx DISC PROCESS ATTEMPTED AREA a

Process xxxx terminates without disconnecting.• RC=12, AREA IS IN A QUIESCE STATE sysid

The utility terminates.

System programmer responseThe actions to take are listed for the different forms ofthe message:


See the accompanying DFS0535I message.• xxxx DISC PROCESS ATTEMPTED AREA a

See the accompanying DFS0535I message.• RC=01, yyyy ALREADY RUNNING

Run the utility or process again when process yyyyhas completed. This message can also be issued ifa previous process did not complete successfully; ifso, issue a /STOP and /START command pair for thearea to allow the requested process to run. If thismessage is received in a data sharing environment,issue the /STOP and /START command pair on allsharing subsystems.

• RC=03, AREA LOCK FAILED

Determine the cause of the lock failure and correctthe problem. If a disconnect did not completebecause of an area lock failure, a /STOP and /STARTcommand pair might be required to allow otherprocesses to run.

• RC=04, AREA IS STOPPED

Issue a /START command to start the area.• RC=05, AREA FAILED TO OPEN

See message DFS3702I to determine why the openfailed.

• RC=06, 2ND CI UPDATE AND/OR NOTIFYFAILED

See accompanying messages for more information.• RC=07, UOW LOCK MODE INITIATION FAILED

Correct the failing component and rerun.• RC=08, INSUFFICIENT STORAGE FOR AREAPRIVATE BUFFER POOL

Run process xxxx again when storage is available.• RC=09, PRIVATE BUFFER POOL ALREADYEXIST sysid

This indicates a logic error in the software. Runprocess xxxx again. If the error still occurs, contactIBM Software Support.

• RC=10, COULD NOT GET AN AWE sysid

Run process xxxx again when storage is available.• RC=11, INVALID REQUEST SENT TO DBFPAPB0sysid

This indicates a logic error in the software. Runprocess xxxx again. If the error still occurs, contactIBM Software Support.

• RC=12, AREA IS IN A QUIESCE STATE sysid

Stop the quiesce by issuing a UPDATE AREASTOP(QUIESCE) command, and rerun the namedutility.

Programmer responseEnsure that no HSSP process or utility is active in anarea before restarting the HSSP job.

Module:DBFPMSG0, DBFPSET0, DBFUHDR0

DFS536A LAST CONVERSATION MESSAGEUNAVAILABLE - reason

ExplanationThe /RELEASE command failed to retrieve the lastoutput message for the IMS conversation for oneof the following reasons indicated by reason in themessage text:

STORAGE UNAVAILABLERESTART RESYNC INCOMPLETEQUEUE ERROR


Operator responseAll of these errors are likely to be temporary. Reenterthe command after a short wait for the conditioncausing the failure to be resolved.

Module:DFSICLH0

DFS0537I AREA=areaname DD=ddname,DSN=dsname CLOSED, IC FAILED


or

AREA=areaname DD=ddname, DSN=dsname OPEN|CLOSED

or

AREA=areaname DD=ddname, DSN=dsname CLSRETRY FP TCB

ExplanationHSSP Image Copy opened or closed the image copydata set normally.

If the data set is being closed after an error, you seethe IC FAILED form of the message. CLS RETRY FPTCB indicates that the image copy is closed and failed.



Module:DBFMPCL0, DBFICSQ0, DBFPICT0, DBFPIOS0

DFS0538I I/O ERROR qsam_info

ExplanationThe SYNADAF ACSMETH=QSAM macro gatheredinformation from QSAM. qsam_info contains a systemmessage number that explains the content of themessage.

System actionIMS stops processing for the data set.

Programmer responseCorrect the error and reissue the command, asappropriate.

Module:DBFICSQ0

DFS0539A HD RELOAD IS UNABLE TOPROCESS THE UNLOAD FILE DUETO INVALID STAT RECORD

ExplanationThe statistics records in HD Unload data set are notrecognizable by HD Reload utility.

System actionHD Reload utility terminates with abend 0355.

Programmer responseSave HD unload data set and HD Reload job output.Then contact IBM Software Support.

Module:DFSURGL0


DFS0540I xxxxx PROGRAM=programname, CKPTID=checkpointid,REGID=regionid, DAY=ddd,TIME=hhmmssthmiju+0000

ExplanationAn extended (or symbolic) checkpoint, or an extendedrestart (XRST) request was processed. In the messagetext, xxxxx can be one of the following values:*EXTENDED CHECKPOINT*

An extended (or symbolic) checkpoint wascompleted. X'18' log records were recorded.To suppress issuing message DFS0540I andDFS0542I, specify NOMSG540 on the CKPTID=EXEC parameter. If you also want to suppressissuing message DFS681I, specify NOMSGS.

*XRST IN PROGRESS*An extended restart call (XRST for a BMPapplication orIMSTransaction.getTransaction().restart for a JBP application) was processed. The X'18'records are located in the log.

*XRST CKPT NOT IN OLDS*A BMP and JBP application requested an XRST.The OLDS no longer contains the X'18' records ofthe last symbolic checkpoint.

*XRST LAST CKPT ID IS*A BMP requested XRST, specifying a checkpoint IDvalue. The specified value is not the same as thevalue recorded by IMS as the last checkpoint ofthe BMP. The last checkpoint ID recorded by IMS isdisplayed in the message.

The time and day displayed are the universalcoordinated time (UTC) at which the checkpoint wastaken.



System actionIn the first two cases, processing continues normally.In the last two cases, the action depends on whetherthe BMP job contains an IMSLOGR DD data set. If thedata set is present, it is used as the log input for theXRST. Otherwise, the BMP is terminated with abend0102.

Programmer responseWhen the program terminates with abend 0102,determine which log data set and volume contain theXRST checkpoint ID. Add an IMSLOGR DD statementto the JCL, specifying this log data set and volume. Setthe BMP checkpoint ID EXEC parameter to equal thecheckpoint ID you want, and resubmit the job.

After IMS issues either the *XRST CKPT NOT IN OLDS*or the *XRST LAST CKPT ID IS* message and theprogram terminates with abend 0102, you can restartfrom the last user checkpoint known to IMS. Resubmitthe BMP job, specifying LAST as the XRST symboliccheckpoint ID value.

For the *XRSTCKPT NOT IN OLDS* message, youcan specify LAST as the XRST checkpoint ID whenresubmitting the job.

Module:DFSZSC00, DFSDLA00


DFS541 INVALID OR MISSING OPTIONPARM

ExplanationThe keyword OPTION was entered on an /EREcommand. An invalid parameter or no parameterfollowed this keyword.

System actionThe /ERE command is rejected.

Programmer responseRemove the OPTION keyword from the /EREcommand or add the SYNCPLEX parameter to thiskeyword.

Module:DFSICL20

DFS0542I *EXTENDEDCHECKPOINT* DAY=ddd,TIME=HHMMSSTHMIJU+0000

ExplanationAn extended checkpoint was processed. This messagefollows message DFS0540I.

In the message text:

dddA Julian date.

HHMMSSTHMIJU+0000The universal coordinated time (UTC) at which thecheckpoint was taken.

This message is suppressed if message DFS0540I issuppressed. To suppress only the issuing messageDFS0542I, code NOMSG542 on the CKPTID=EXECparameter. If you also want to suppress messageDFS681I, code NO681542. If you want to suppressmessages DFS681, DS0540I and DFS0542I, codeNOMSGS.

System actionProcessing continues normally.


Module:DFSZSC00

Related information“DFS0540I” on page 190xxxxx PROGRAM=program name,CKPTID=checkpointid, REGID=regionid,DAY=ddd, TIME=hhmmssthmiju+0000

DFS0543I MADS I/O TIMING RECOVERYSTARTED FOR AREA=AAAAAAAADDN=DDDDDDD

ExplanationThis message indicates that the recovery process forthe Long Busy area has begun.


AAAAAAAAThe name of the Long Busy area for which recoverywas started.

DDDDDDDThe data description name of the Long Busy area.

System actionThis system receives message DFS1558I when theMADS I/O Timing recovery for the area data set (ADS)ends.

System programmer response:



Module:DBFMLBR0

DFS0546I LONG BUSY ADS CLOSED.AREA=xxxxxxxx,ADS=yyyyyyyy,UNIT=nnnn

ExplanationA long busy condition persisted long enough forthe maximum CI (1000 CIs per AREA) limit to beexceeded. When this happens, MADSIOT functionissues an internal STOP ADS command. The STOPADS process calls Media Manager DISCONNECTfunction under XFP TCB and if DASD is still in long busycondition, the DISCONNECT function is suspendeduntil the long busy condition is relieved or IOTIMING isreached.

During the suspension, all ITASKs including OTHREAD,CHKPT, and FP commands under XFP TCB are notserviced. To reduce the impact, this message can beused by automated operator to force the long I/Odevice offline.


Module:DBFARD20

DFS0548A RRS NOT ACTIVE BUT RRS=YSPECIFIED - REPLY: RETRY,CONTINUE OR CANCEL

ExplanationIMS received a CRG_EM_STATE_ERROR return codefrom the CRGSEIF (set exits) call, indicating that RRSwas not active.

System actionThe system waits for a reply to this message.

Operator responseStart RRS and then reply RETRY to the message.Reply CONTINUE if RRS is to be started later withan automatic asynchronous connection made to IMS.Reply CANCEL if RRS is not needed in this execution ofIMS.

In the batch environment, a CONTINUE reply is thesame as CANCEL.

Module:DFSRRSI0, DFSRRSB0

DFS0548E ERROR BUILDING RESOUCECLEANUP ENVIRONMENT, RC=rc -details

ExplanationAn error occurred while IMS was establishingits resource cleanup and online dump formattingenvironment during IMS initialization.

In the message text:rc

The return code from the failing service.details

A one-line explanation of the type of error that wasdetected.

The details portion of the DFS0458E messagefurther explains the error detected and can be oneof the following values:ERROR OBTAINING GRMB STORAGE

IMS could not obtain storage required for aGRMB (Global Resource Manager Block). rc inthe message is the return code from the z/OSSTORAGE OBTAIN macro.

ERROR OBTAINING XSSCT STORAGEIMS could not obtain storage required for anXSSCT (IMS 31 bit extended SSCT). rc in themessage is the return code from the z/OSSTORAGE OBTAIN macro.

ERROR OBTAINING DFSMRC20 STORAGEIMS could not obtain storage to direct loadmodule DFSMRC20. rc in the message is thereturn code from the z/OS STORAGE OBTAINmacro.

BPESVC FUNC=INIT ERRORAn error occurred during BPESVC FUNC=INITprocessing. rc in the message is the returncode from the BPESVC macro.

ERROR ISSUING BLDL FOR DFSMRC20An error occurred issuing a BLDL macro call formodule DFSMRC20. rc in the message is thereturn code from the z/OS BLDL macro.

ERROR LOADING DFSMRC20IMS could not load module DFSMRC20. rc inthe message is the return code from the z/OSLOAD macro.

ERROR LOADING DFSRTM00IMS could not load module DFSRTM00. rc inthe message is the return code from the z/OSLOAD macro.

ERROR ADDING ADDRSPC RESMGRIMS could not dynamically add an addressspace resource manager to the system. rc in


the message is the return code from the z/OSRESMGR macro.

ERROR ADDING TASK RESMGRIMS could not dynamically add a task resourcemanager to the system. rc in the message isthe return code from the z/OS RESMGR macro.

AN ABEND OCCURREDAn abend occurred during the building of theIMS resource cleanup environment. rc in themessage is the abend code.

UNABLE TO ESTABLISH ESTAEIMS was unable to establish an ESTAE recoveryroutine to protect the resource cleanupenvironment initialization. rc in the message isthe return code from the z/OS ESTAEX macro.

ENQ FAILED ON SYSZDFS DFSGRMBIMS was unable to obtain an exclusive ENQ onthe resource "SYSZDFS DFSGRMB". rc in themessage is the return code from the z/OS ENQmacro.

ERROR OBTAINING DFSMRC00 STORAGEIMS could not obtain storage to direct loadmodule DFSMRC00. rc in the message is thereturn code from the z/OS STORAGE OBTAINmacro.

ERROR ISSUING BLDL FOR DFSMRC00An error occurred issuing a BLDL macro call formodule DFSMRC00. rc in the message is thereturn code from the z/OS BLDL macro.

ERROR LOADING DFSMRC00IMS could not load module DFSMRC00. rc inthe message is the return code from the z/OSLOAD macro.

UNKNOWN ERRORAn unexpected error occurred during the IMSresource manager cleanup initialization.

ERROR OBTAINING DFSAFMX0 STORAGEIMS could not obtain storage to direct loadmodule DFSAFMX0. rc in the message is thereturn code from the z/OS STORAGE OBTAINmacro. IMS initialization continues; however,online dump formatting for IMS is unavailable.

ERROR ISSUING BLDL FOR DFSAFMX0An error occurred issuing a BLDL macro call formodule DFSAFMX0. rc in the message is thereturn code from the z/OS BLDL macro. IMSinitialization continues; however, online dumpformatting for IMS is unavailable.

ERROR LOADING DFSAFMX0IMS could not load module DFSAFMX0. rcin the message is the return code from thez/OS LOAD macro. IMS initialization continues;however, online dump formatting for IMS isunavailable.

DFSAFMX0 IEFSSI ADD FAILEDIMS was unable to add a subsystemdynamically to z/OS to enable IMS to performdump formatting for SNAP, SYSABEND, andSYSUDUMP dumps. The top 2 bytes of rc inthe message is the return code from the z/OSIEFSSI REQUEST=ADD macro. The bottom 2bytes of rc in the message is the reasoncode from IEFSSI. IMS initialization continues;however, online dump formatting for IMS isunavailable.

DFSAFMX0 IEFSSI ACTIVATE FAILEDIMS was unable to dynamically activate asubsystem to z/OS to enable IMS to performdump formatting for SNAP, SYSABEND, andSYSUDUMP dumps. The top 2 bytes of rcin the message is the return code from thez/OS IEFSSI REQUEST=ACTIVATE macro. Thebottom 2 bytes of rc in the message is thereason code from IEFSSI. IMS initializationcontinues; however, online dump formatting forIMS is unavailable.

DFSAFMX0 IEFSSVT CREATE FAILEDIMS was unable to create a subsystem vectortable for the IMS-added subsystem to enableIMS to perform dump formatting for SNAP,SYSABEND, and SYSUDUMP dumps. The top 2bytes of rc in the message is the return codefrom the z/OS IEFSSVT REQUEST=CREATEmacro. The bottom 2 bytes of rc in themessage is the reason code from IEFSSVT. IMSinitialization continues; however, online dumpformatting for IMS is unavailable.

DFSAFMX0 IEFSSVT EXCHANGE FAILEDIMS was unable to update the DFSAFMX0subsystem vector table entry to point to a copyof DFSAFMX0 more recent than the copy thathad been previously installed. The top 2 bytesof rc in the message is the return code from thez/OS IEFSSVT REQUEST=EXCHANGE macro.The bottom 2 bytes of rc in the message is thereason code from IEFSSVT. IMS initializationcontinues. The previously installed copy ofDFSAFMX0 is used as the IMS online dumpformatting exit.

System actionFor errors during the initialization of the online dumpformatter exit DFSAFMX0, the module detecting theerror, DFSRTMI0, returns a zero return code to itscaller. IMS continues execution; however, IMS onlinedump formatting might not be available for thisinstance of IMS.

For all other errors, the module detecting the error,DFSRTMI0, returns a non-zero return code to its caller.


System programmer responseIf the error described in this message is caused byenvironmental conditions (for example, insufficientstorage or modules missing from IMS.SDFSRESL),correct the indicated problem and restart the addressspace. Otherwise, save any dump and SYSLOGinformation, and contact IBM Software Support.

Module:DFSRTMI0

Related referenceBPESVC codes (Messages and Codes)z/OS: STORAGE OBTAIN return and reasoncodesz/OS: BLDL completion codesz/OS: LOAD return and reason codesz/OS: Return codes from the ADD function(RESMGR)z/OS: ESTAEX return and reason codesz/OS: ENQ return and reason codesz/OS: IEFSSI return and reason codesz/OS: IEFSSVT return and reason codes

DFS549I ESAF SIGNON ACEE ENABLED

ExplanationESAF_SIGNON_ACEE=YES was specified in theDFSJVMEV member of the IMS PROCLIB data set forthis persistent Java virtual machine (JVM) dependentregion.

Output destinationThe Systems Console

Module:DFSPCC20, DFSPCJM0, DFSPCJB0

Related referenceDFSJVMEV (JVM environment settings member)(System Definition)

DFS550I DFSNDMI0 {SUCCEEDED|FAILED}REGION=rrrrr JOBNAME=jjjjjjjjSTEPNAME=ssssssssTRANSACTION=ttttttttPSB=ppppppppSSYSID=wwwww[FAILURECODE=xxx RETURN CODE=yyy|N/A] [DESTINATION=ddddddddDSYSID=zzzzz|N/A] timestamp

ExplanationThe application program associated with PSBpppppppp terminated abnormally while processing

transaction tttttttt. The Non-Discardable MessagesUser exit interface (DFSNDMI0) either succeeded orfailed in requeuing the input message associated withtransaction tttttttt to destination dddddddd.

If DFSNDMI0 succeeded, the DESTINATION andDSYSID= information are displayed. The FAILURECODE information and the RETURN CODE informationare not displayed.

If DFSNDMI0 failed, the FAILURE CODE and theRETURN CODE information are displayed. TheDESTINATION and DSYSID information are displayedonly for some failure codes. If displayed, theDESTINATION and DSYSID information follow theFAILURE CODE information and the RETURN CODEinformation.

The SUCCEEDED version of this message is alwaysfollowed by message DFS554A, and for certainconditions, can also be followed by DFS555I. TheSUCCEEDED version is issued only if DFSNDMI0successfully queues the input message associatedwith transaction tttttttt to destination dddddddd afterreceiving return code 16 from the Non-DiscardableMessages user exit NDMX.

The meanings of the message fields are:rrrrr

Region IDjjjjjjjj

Job name (padded with blanks)ssssssss

Step name (padded with blanks)tttttttt

Transaction that the application associated withPSB pppppppp was processing when it abended

ppppppppPSB associated with abended application program

wwwwwSystem ID of the system from which theinput message in process and associated withtransaction tttttttt originated (the source systemID)

xxxOne of the following failure codes is displayed onlyin the FAILED version of this message:001

Queue manager was unable to obtain the inputmessage associated with transaction tttttttt.

002Unable to obtain storage for NDM SPA buffer(IMODULE GETSTOR failure).

003Unable to obtain storage for message segmentbuffer (IMODULE GETSTOR failure).


http://www.ibm.com/support/knowledgecenter/SSEPH2_15.1.0/com.ibm.ims15.doc.msgs/compcodes/bpesvc.htm#bpesvc

http://www-01.ibm.com/support/knowledgecenter/SSLTBW_2.4.0/com.ibm.zos.v2r4.ieaa400/iea3a4_STORAGE_OBTAIN.htm?lang=en



http://www-01.ibm.com/support/knowledgecenter/SSLTBW_2.4.0/com.ibm.zos.v2r4.ieaa900/iea3a9_Description5.htm?lang=en

https://www.ibm.com/support/knowledgecenter/en/SSLTBW_2.1.0/com.ibm.zos.v2r1.cs3cod0/enf.htm


https://www.ibm.com/support/knowledgecenter/SSLTBW_2.3.0/com.ibm.zos.v2r3.ieaa200/iea3a2_ESTAEX_-_Specify_task_abnormal_exit_extended.htm

http://www-01.ibm.com/support/knowledgecenter/SSLTBW_2.4.0/com.ibm.zos.v2r4.ieaa200/ENQ_Description.htm?lang=en

http://www-01.ibm.com/support/knowledgecenter/SSLTBW_2.4.0/com.ibm.zos.v2r4.ieaa900/iea3a9_IEFSSI_____Dynamically_query_a_subsystem.htm?lang=en

http://www-01.ibm.com/support/knowledgecenter/SSLTBW_2.4.0/com.ibm.zos.v2r4.ieaa200/iea3a2_IEFSSVT_____Create_a_subsystem_vector_table.htm?lang=en

http://www.ibm.com/support/knowledgecenter/SSEPH2_15.1.0/com.ibm.ims15.doc.sdg/ims_dfsjvmev_proclib.htm#DFSJVMEVJVMEnvironmentSettingsMembe

http://www.ibm.com/support/knowledgecenter/SSEPH2_15.1.0/com.ibm.ims15.doc.sdg/ims_dfsjvmev_proclib.htm#DFSJVMEVJVMEnvironmentSettingsMembe

004There is no input message.

005OTMA FINDDEST failed.

006System locate service failed (DFSSLC failure).

007FINDDEST failed (DFSFNDST failure).

008LUM failed to build the APPC message prefix.

009Queue manager failed to insert the message.

010No more inserts are allowed by this UOW.

011The Non-Discardable Messages user exitspecified an invalid destination transaction forrequeue.

012The message was not requeued to itspermanent destination (DFSICLR2 failure).

013Unable to obtain storage for the NDM interfaceblock (IMODULE GETSTOR failure).

014Unable to obtain storage for the USRX interfaceblock (IMODULE GETSTOR failure).

015The Non-Discardable Messages user exit wasnot started (DFSUSRX failure).

016The destination specified for requeue is zerosor blanks (return code 16 from the Non-Discardable Messages user exit).

017Unable to obtain storage for message recordbuffer (IMODULE GETSTOR failure).

018Unable to obtain storage for single segmentmessage buffer (IMODULE GETSTOR failure).

019The Non-Discardable Messages user exitrequested that IMS requeue the input messageto a transaction. However, one of the followingconditions exists:

• One of the input message segments exceedsthe allowable segment length for thedestination transaction.

• The total number of input message segmentsexceeds the allowable number of segmentsfor the destination transaction.

yyyReturn code of the IMS service that failed, or N/Aif xxx is 004, 010, 011, 016, or 019. This fieldis displayed only in the FAILED version of thismessage.

ddddddddDestination to which the Non-DiscardableMessages user exit asked to have the inputmessage requeued (return code 16). This field isalways displayed in the SUCCEEDED version of thismessage; it is sometimes displayed in the FAILEDversion of this message.

zzzzzDestination system ID – system ID of thesystem to which the input message in processand associated with transaction tttttttt was sent(SUCCEEDED version) or would have been sent(FAILED version), or N/A if xxx = 005, 006, or 007.This field is always displayed in the SUCCEEDEDversion of this message; it is sometimes displayedin the FAILED version of this message.

System actionFor the SUCCEEDED version of this message, theinput message associated with transaction tttttttt isrequeued to destination dddddddd and then deletedfrom transaction tttttttt. For the FAILED version ofthis message, the input message associated withtransaction tttttttt is deleted from the system unlessthe application abend is 3303, 2478, 0777, or 2479.

Operator response:For the SUCCEEDED version of this message, seemessages DFS555I and DFS554A, which alwaysfollow this message at the IMS master terminal.Inform the appropriate personnel of the applicationprogram abend. For the FAILED version of thismessage, see failure code xxx to determine whyDFSNDMI0 failed.

Programmer response:Correct the cause of the application program abend.


Module:DFSNDMI0

Related information“DFS554A” on page 197jobname.region.stepname. prog PSBname(x)transaction-codesys-completion-code user-completion-code PSBSMBLTERM:|LUNAME:|RTKN=tokenREASON=reason originating terminal“DFS555I” on page 200


TRAN tttttttt ABEND (SYSID sss);REASON=reason; MSG IN PROCESS: xxxx (UPTO 78 BYTES OF DATA) time-stampIMS abend 0777IMS abend 2478IMS abend 2479

IMS abend 3303“IMS problem determination” on page 11IMS messages and codes problemdetermination is accomplished by usingprocedures established by IBM.




http://www.ibm.com/support/knowledgecenter/SSEPH2_15.1.0/com.ibm.ims15.doc.msgs/msgs/2479.htm#imsabennd2479




DFS551I {IFP | MESSAGE | BATCH |JMP | JBP} REGION xxxxxxxxSTARTED. ID=yyyyy TIME=zzzzCLASSES=xxx,xxx,xxx,xxx

ExplanationA dependent processing region started. The possibledependent processing regions are:

• Batch• Fast Path• JVM batch• JVM message• Message• DMU

DMU (Database Metadata Update) region is spawnedupon the submission of the first DDL statement and allDL/I calls associated with DDL processing are handledunder the DMU region.

xxxxxxxx is replaced by the job name, yyyyy is replacedby the PST number, and zzzz is replaced by the time(hhmm) started.

The ID field identifies the region and is used with the /STOP REGION command.

System actionA message, BMP, JMP, or JBP region is processingtransactions of the specified class.


Module:DFSSMIC0,DFS3MIC0

DFS552I {IFP | MESSAGE | BATCH | JMP|JBP} REGION xxxxxxxx STOPPED.ID=yyyyy TIME=zzzz

ExplanationA dependent processing region stopped. The possibledependent processing regions are:

• Batch• Fast Path

• JVM batch• JVM message• Message• DMU

DMU (Database Metadata Update) region is spawnedupon the submission of the first DDL statement and isterminated after the processing of Commit DDL.

xxxxxxxx is replaced by the job name, yyyyy is replacedby the PST number, and zzzz is replaced by the time(hhmm) stopped.

System actionA message or BMP region is terminated.


Module:DFSSDA10, DFSSDA20, DFS3DL10

DFS553I JOBNAME STEPNAME UNKNOWNCALL FUNCTION CODE

ExplanationThe IMS control program received a request toschedule a program in a dependent region. The typeof request cannot be identified.

System actionThe call function is ignored and processing continues.



DFS554A jobname.region.stepname. progPSBname(x) transaction-codesys-completion-code user-completion-code PSB SMBLTERM:|LUNAME:|RTKN=tokenREASON=reason originatingterminal


ExplanationThe IMS application indicated by prog PSBnameencountered a system abend or a user abendindicated by sys-completion-code or user-completion-code respectively.

The information for this message is printed asindicated. This message can be multiline.

The program PSB name is associated with one of thefollowing region types, which is indicated by (x):

0IMS program controller

1MPP region

2BMP region

3The Coordinator Control (CCTL) thread

4IFP region

5JMP region

6JBP region

7Application Execution Region (AER) region; forexample, an ODBM application that is running inan AER

For DBCTL/CCTL threads, the word NOPSBAVL mightbe displayed as the PSBNAME in the text of themessage. This condition indicates that a sign-on createthread call was made to DBCTL using the CCTL toinitially establish the thread. However, before a callwas made to schedule the PSB, the thread wasstopped. Until a call is made to schedule the PSB, thename of the PSB is unknown to DBCTL.(x)

Identifies the region type associated with the jobname.

For an MPP region, x = 1.For a BMP region, x = 2.For a DBCTL region, x = 3.For an IFP region, x = 4.For a JMP region, x = 5.For a JBP region, x = 6.For an AER region, x = 7.

The termination of the CCTL thread is caused by one ofthe following causes:

• A CCTL application abend or pseudoabend• A CCTL abend

• A CCTL request for termination of its connection toDBCTL while its thread is still active

SMB indicates that the transaction was stopped, andthe absence of SMB indicates that the transactionwas not stopped. PSB indicates that the program wasstopped, and the absence of PSB indicates that theprogram was not stopped. LTERM or LUNAME is thename of the terminal. LUNAME is displayed in placeof LTERM when the originating terminal is LU6.2 orOTMA, unless the LUNAME information is in transition.If the LUNAME information is in transition, UNKNOWNis displayed.

For DBCTL/CCTL threads, this message displays therecovery token. The first 8 bytes of this token are inEBCDIC and are displayed as characters; the second 8bytes of the token are displayed in hexadecimal form.However, if DBCTL detects a failure during schedulingof the PSB (for example, abends 0428, 0437, 0456,0457, and 0458), the recovery token is displayed aszeros. This signifies that recovery of an unscheduledPSB is not needed.

Except for DBCTL, if the user completion code is U428,the PSB name is blank because the PSB was notfound.

If the user completion code is 0448, 0452, 0456,or 0458, the transaction code and the stopped SMBname are blank.

If the user completion code is 0464, SYS does notrepresent a system completion code, but rather theerror return code from the reply SVC. These returncodes are:

CodesExplanation

001Simulated region termination or reply recursion.

002Address of the dependent region TCB is invalid.

003Dependent task is terminating (TCBFLGS1 is set).

004Dependent task is terminating (TCBFLGS5 is set).

005Dependent task does not have an RCPARMS.

006PSTID does not match RCID.

009The dependent region was probably canceled byz/OS.

REASON=reason is displayed only if the abend reasoncode is available. The message can be issued duringCreate Thread processing or by the dependent


region environment controller module (for example,DFSECP10). reason has the following forms:

For abend 0711REASON=xxxxyyyy, where xxxx is the returncode from z/OS Recovery Resource ManagementServices (RRMS) or from z/OS UNIX SystemServices, and yyyy is the abend 0711 reason code.

For abend 0129REASON=xxxxyyyy, where xxxx is the SAF returncode and yyyy is the RACF or equivalent returncode.

For abend 0128REASON=xxxxxxxx, where xxxxxxxx is the returncode from the APPC Associate service (ATBASOC).

For abend 0109REASON=xxxxxxxx, where xxxxxxxx is the returncode from the APPC/OTMA synchronous sharedqueue.

For abend 0425REASON=xxxxxxxx in the DFS554A messageidentifies the reason code or completion codeof why the runtime program resource or runtimedatabase resource could not be created. Refer toDFSCMDRR for the explanation of the reason codeor completion code.

For abend 0426REASON=xxxxxxxx in the DFS554A messageidentifies the reason code or completion codeof why the runtime program resource or runtimedatabase resource could not be created. Refer toDFSCMDRR for the explanation of the reason codeor completion code.

System actionThis message might follow message DFS555I. If thetransaction input message that caused the applicationprogram to terminate abnormally is available, the first79 bytes of the input message are printed by messageDFS555I. A transaction is considered "available" if theinput message in process by the application is on themessage queue. Exceptions are:

• The application has not issued a GU call.Therefore, the message did not cause the abnormaltermination.

• An abnormal termination that could be rescheduledoccurred (for example, PI lockout) unless the Non-Discardable Messages user exit told IMS to discardthe input message.

• This message is preceded by the SUCCEEDEDversion of message DFS550I.

The preceding exceptions allow the message to runagain.

If the application program terminated abnormally afterthe last message was removed from the applicablequeue, the transaction is not available and onlymessage DFS554A is printed.

If during the initialization of a new message regionthe IMS control region can determine that a previousregion was canceled, the job name and step namefields of this message contain the words REGIONCANCELED. The region is the identity of the newdependent region.

If a system abend 806 occurs in a persistent JVMdependent region, this message might follow messageDFS480E.

Operator response:(master terminal) Inform appropriate personnel ofthe application program abend. See abends 0448,0452, 0456, 0458. See message DFS550I which mightprecede this message at the IMS master terminal.

Programmer responseCorrect the cause of the application program abend.

Problem determination:4, 5, 6, 8, 10, 18, 19

Module:DFSFXC30, DFSDSC00

Related information“DFS550I” on page 194DFSNDMI0 {SUCCEEDED|FAILED} REGION=rrrrrJOBNAME=jjjjjjjj STEPNAME=ssssssssTRANSACTION=tttttttt PSB=ppppppppSSYSID=wwwww[FAILURE CODE=xxx RETURNCODE=yyy|N/A] [DESTINATION=ddddddddDSYSID=zzzzz|N/A] timestampIMS abend 0109IMS abend 0128IMS abend 0129IMS abend 0448IMS abend 0452IMS abend 0456IMS abend 0458IMS abend 0711“IMS problem determination” on page 11IMS messages and codes problemdetermination is accomplished by usingprocedures established by IBM.

DFS555A SUBSYSTEM xxxx OASNyyyyyyyyyyyyyyyy STATUSCOMMIT|ABORT





http://www.ibm.com/support/knowledgecenter/SSEPH2_15.1.0/com.ibm.ims15.doc.msgs/msgs/0448.htm#imsabends0448





ExplanationThis addition to message DFS555I is producedby the IMS sync point processing modules. Thepurpose of this message is to give the operatorenough information so that the external subsystemresources can be properly managed. xxxx representsthe subsystem name and the y value represents theoriginating application sequence number (OASN) thatis a part of the recovery ID for the thread.

System actionIMS, acting as a commit coordinator, attempts tomanage the thread as indicated in this message. Ifconditions do not allow IMS to do this, the systemprogrammer can do it by using the appropriateexternal subsystem commands. IMS must be notifiedwhen the system programmer has run the appropriatecommand.

Operator responseNotify the system programmer about this segmentappearing in the message.

System programmer responseThe inconsistency of the thread status between IMSand the external subsystem must be corrected. The /CHANGE command enables the function to correct theIMS status. The external subsystem should providesimilar function for its half of the thread.

Module:DFSFXC30, DFSFXC40

Related information“DFS550I” on page 194DFSNDMI0 {SUCCEEDED|FAILED} REGION=rrrrrJOBNAME=jjjjjjjj STEPNAME=ssssssssTRANSACTION=tttttttt PSB=ppppppppSSYSID=wwwww[FAILURE CODE=xxx RETURNCODE=yyy|N/A] [DESTINATION=ddddddddDSYSID=zzzzz|N/A] timestamp

DFS555I TRAN tttttttt ABEND (SYSIDsss); REASON=reason; MSG INPROCESS: xxxx (UP TO 78 BYTESOF DATA) time-stamp

ExplanationAn application program abend occurred during theprocessing of transaction tttttttt (in system sss ina multi-system environment). The variable xxxx isreplaced by up to 78 characters of the inputtransaction being processed. A time stamp follows theinput transaction data.

If the input transaction is missing, the followingmessage appears: QMGR RC NE 0, MSG. NOTAVAIL.

REASON=reason is displayed only if the abend reasoncode is available. The message can be issued duringCreate Thread processing or by the dependentregion environment controller module (for example,DFSECP10). reason has the following forms:

For abend 0109REASON=xxxxxxxx, where xxxxxxxx is the returncode from the APPC/OTMA synchronous sharedqueue.

For abend 0119REASON=00000008, indicates a problem withtiming out.REASON=00000012, the APPC device or OTMAclient explicitly directed IMS to abort syncpointprocessing.

For abend 0128REASON=xxxxxxxx, where xxxxxxxx is the returncode of the APPC Associate service (ATBASOC).

For abend 0129REASON=xxxxyyyy, where xxxx is the SAF returncode and yyyy is the RACF or equivalent returncode.

For abend 0711REASON=xxxxyyyy, where xxxx is the return codeof the RRMS service that failed and yyyy is theabend 0711 reason code.

System actionThe input transaction identified by this message isdeleted from the system unless this message ispreceded by the SUCCEEDED version of messageDFS550I.

Operator response(terminal operator) If this multi-segment messageuses Message Format Service to send a formattedscreen with a SYSMSG field, only one segment issent at a time. Press PA1 to retrieve the remainingsegments.

(master terminal) See message DFS554A, whichalways follows this error message at the IMS masterterminal. See message DFS550I, which might precedethis message at the IMS master terminal.

Programmer responseCorrect the cause of the application program abend.



Module:DFSFXC40

Related informationIMS abend 0109IMS abend 0119IMS abend 0128IMS abend 0129IMS abend 0711“DFS550I” on page 194DFSNDMI0 {SUCCEEDED|FAILED} REGION=rrrrrJOBNAME=jjjjjjjj STEPNAME=ssssssssTRANSACTION=tttttttt PSB=ppppppppSSYSID=wwwww[FAILURE CODE=xxx RETURNCODE=yyy|N/A] [DESTINATION=ddddddddDSYSID=zzzzz|N/A] timestamp“DFS554A” on page 197jobname.region.stepname. prog PSBname(x)transaction-codesys-completion-code user-completion-code PSBSMBLTERM:|LUNAME:|RTKN=tokenREASON=reason originating terminal“DFS555A” on page 199SUBSYSTEM xxxx OASN yyyyyyyyyyyyyyyySTATUS COMMIT|ABORT“IMS problem determination” on page 11IMS messages and codes problemdetermination is accomplished by usingprocedures established by IBM.

DFS0556I COMMAND REJECTED; DBCTLTHREAD IS ACTIVE

ExplanationYou entered a /STOP REGION or /STOP THREADcommand for an active Database Control (DBCTL)subsystem thread. (For example, the DBCTL threadhas a PSB scheduled.)

System actionThe command is ignored, and the thread continuesprocessing.

Programmer responseDetermine if you specified the correct region ID, or usethe ABDUMP form of the command.


Module:DFSDSTP0


DFS0557I STOP REGION NOT VALID-REGIONnn IS BMP.

ExplanationA /STOP REGION command has been entered for adependent region in which a BMP is processing.

System actionThe entered command is ignored. The IMS and thedependent region, which is identified by nn, continuerunning.

Programmer responseDetermine if the correct region ID was used, or use theABDUMP form of the /STOP REGION command.


Module:DFSSTOP0


DFS0558I TRAN xxxxxxxx NOT SCHEDULED

ExplanationA /STOP REGION ABDUMP or a /PSTOP REGION xTRAN y command was entered, but the transactionxxxxxxxx is not scheduled in the region specified.

System actionThe entered command is ignored. The IMS and thedependent region, which is identified by nn, continuerunning.

Programmer responseDetermine if the correct region ID was used, or usethe /STOP REGION command for an unscheduledregion.


Module:







DFSSTOP0Related information“IMS problem determination” on page 11IMS messages and codes problemdetermination is accomplished by usingprocedures established by IBM.

DFS0559I ABEND ALREADY SCHEDULED FORREGION nn, TRAN xxxxxxxx

ExplanationThe region or application specified in a /STOPREGION command is in the process of abending.

Programmer responseIf the dependent region does not terminate, you mightcancel it, as a last resort. This action can cause theabend of the entire IMS system.

Module:DFSSTOP0

DFS560I PROC OPTION L OR LS SPECIFIEDFOR PSB psbname

ExplanationOne or more PCBs within the named PSB has L or LSspecified as the processing option. This is valid in abatch region only.


Programmer responseCorrect the PSB in error, and rerun the ApplicationControl Blocks Maintenance utility.

Module:DFSDBLM0, DFSXRBL0

DFS561A ERROR READING ACBLIB,{PSB=psbname|DMB=dmbname}

ExplanationAn I/O error occurred while reading the named PSB ordata management block from the Application ControlBlocks Library. The PSB or data management blockhas been stopped. No further attempt is made toread the affected block, and no program using thatblock is scheduled. If a dynamic PSB is added toa concatenation of ACBLIB that causes the data setto be expanded to a secondary extent, that PSB isunavailable to the online system until the ACBLIB isclosed and reopened by IMS.

An online change procedure can issue this message. Ina read error to the ACBLIB data set, the online changeprocess in terminated.

System actionThe dependent region terminates abnormally.

If you receive this message during an online changeprocedure, the online change is terminated.

Programmer responseTo regain use of the affected block, perform ACBLIBonline change (/MODIFY PREPARE ACBLIB and /MODIFY COMMIT) or shut down the system, correctthe error condition, and restart the system.

You must complete the online change procedure byissuing either a TERM OLC or a /MODIFY ABORTcommand.

Problem determinationIf message DFS825I appears at start-up, verify that atleast one DBD is built in the active ACBLIB when DRDis enabled.

Module:DFSDBLR0, DFSXRBL0, DBFOLC01

DFS561E GETMAIN FAILED FOR QSAVEAREA, ACB LOAD/READTERMINATED

ExplanationGETMAIN failure occurred for QSAVE area below the16 MB line in the process of ACBLIB load or read.

System actionACBLIB load/read terminates.

Programmer responseCheck the application programs which are using alarge percentage of CSA and cancel them if possible.

Module:DFSDBLR0

DFS562I INVALID CORE SIZE REQUIREDFOR {PSB psbname|DMBdmbname}

ExplanationThe named block required more space than wasavailable in the PSB or data management pool. This


situation indicates that the affected pool is not largeenough to accommodate the largest block.


Programmer responseRestart the system with a larger pool size specified.

Module:DFSDBLD0

DFS563I PSB psbname REQUIRESUNKNOWN DMB dmbname, PSBSTOPPED

ExplanationThe system was not able to find data managementblock (DMB) dmbname.

• The named PSB references a data managementblock which was not specified at system definitiontime. If running an IFP DEDB Online utility program,the data management block name specified in thesecond positional operand of the PARM field was notdefined as a DEDB.

If a DEDB Online utility is initiated, the nameddata management block which was specified in thesecond positional operand of the PARM field on theEXEC control statement has not been defined as aDEDB in the DBDGEN.

• The named PSB is a resident PSB and IMSis attempting to schedule this PSB. The datamanagement block number this PSB refers to nolonger matches with the data management blocknumber of the database. The copy of the residentPSB loaded at IMS initialization time can no longerbe used.

Programmer responseCorrect either the PSB or the system definition. For aDEDB Online utility, do either of the following actions:

1. Correct the database name in the second positionaloperand of the PARM field on the EXEC controlstatement, and resubmit the job.

2. Redefine the named database as a DEDB, rerunACBGEN the next time the IMS control region isstarted, and resubmit the job.

The resident PSB can only be reloaded by restartingIMS.

Module:DFSDBLI0, DFSXRBL0, DFSDBLM0

DFS564I DMB dmbname1 REFERENCESUNKNOWN DMB dmbname2, DMBSTOPPED

ExplanationThe first data management block contains a referenceto the second data management block. The seconddata management block was not specified at systemdefinition time.

System actionA BMP region terminates with abend 0458. Abatch DBB region terminates with abend 0821. Ifthe message was issued during IMS initialization,execution continues, but the first data managementblock is marked as unusable.

Programmer responseCorrect the data management block or the systemdefinition.

Module:DFSDBLD0, DFSXRBL0

Related informationIMS abend 0458IMS abend 0821

DFS0565I cccc COMMAND NOT PROCESSEDDB=xxxxxxxx IN USEBY PSB=psbname, REG=region-number

ExplanationThe named DL/I database, xxxxxxxx, cannot beprocessed in response to a /DBDUMP, /DBRECOVERY,or /START command. It is still in use by an activebatch message processing program.

region-number is the number of the region in which aprogram is using database xxxxxxxx.

The MPP region identified in this message can occur tobreak a potential deadlock condition between OnlineChange, a DBR or STA command against a databasebeing used by the MPP, and an application running inthe MPP issuing an ICMD or CMD call.

System actionThe command is not processed for the databasenamed in the message, but processing continues forany other databases specified in the command.

If the NOFEOV keyword is not specified on /DBR or /DBD, a new log volume is mounted.




If /DBD or /DBR is entered, a simple checkpoint istaken.

Operator responseWait for the program to terminate, and reissue the /DBDUMP, /DBRECOVERY, or /START command


Module:DFSDBDR0


DFS0566I PSTOP OR STOP NOT VALID FORTRAN xxxxxxxxx

ExplanationYou entered a /PSTOP REGION TRAN or /STOPREGION TRAN command for a transaction that isnot of the WFI (wait-for-input) type or is Fast Pathexclusive type.


Module:DFSSTOP0

DFS0567I PSB POOL TOO SMALL-PSBnnnnnnnn STOPPED.

ExplanationDuring initialization, insufficient space was available toload the intent list for the PSB specified.

System actionThe PSB is marked unusable, and no transaction thatuses it is scheduled. Normal execution continues.

Programmer responseAt the next IMS execution, increase the size of the PSBpool.

Module:DFSXRBL0

DFS0568I CANCEL INVALID FOR REGION xx;NO PRIOR STOP REGION ABDUMPCOMMAND

ExplanationYou entered a /STOP REGION CANCEL command forregion xx. However, this command is invalid if it is notpreceded by a /STOP REGION ABDUMP command.

Operator response:Issue the /STOP REGION ABDUMP command for theregion. If the /STOP REGION ABDUMP commanddoes not correct the problem, issue a /STOP REGIONCANCEL command.

Module:DFSSTOP0

DFS0569I PSTOP OR STOP COMPLETE FORREGION nnnnttttxxxxxxxx

ExplanationA /PSTOP or /STOP command for the specified regionand transaction successfully completed. A QC statuscode is returned to a wait-for-input (WFI) applicationprogram that is processing in the region. An AOapplication that issued a GMSG call with the waitoption might be waiting for a message on an AOItoken. An application waiting for an AOI token receivesan AIB return code of X'00000004' and an AIB reasoncode of X'0000004C'. If your application issued asynchronous callout ICAL call, it might be waiting fora response from the ICAL call. An application waitingfor a synchronous callout response receives an AIBreturn code of X'00000100' and an AIB reason code ofX'00000104'.nnnn

The region number entered on the command.tttt

AOIT, TRAN, or SYNC. AOIT means the name thatfollows is an AOI token name. TRAN means thename that follows is a transaction name. SYNCmeans that the name that follows is a TPIPE name.

xxxxxxxxThe AOI token name, transaction name, or TPIPEname entered on the command.

System actionIf tttt is AOIT, the region is no longer waiting forthe AOI token. If tttt is SYNC, the region is nolonger waiting for the synchronous callout response.Otherwise, the specified region is still available forscheduling.

A batch message processing region (BMP) scheduledagainst wait-for-input (WFI) transactions returns aQC status code (no more messages) for /PSTOPREGION, /DBD, /DBR, or /START commands only.

Module:


DFSSTOP0

DFS0570I INVALID SECONDARY LIST TYPEWAS FOUND IN DBD dbdname

ExplanationAn internal system error has occurred. If a SYSUDUMPor SYSABEND DD statement was provided, a memorydump was produced.

System actionAbend 0947 is issued.

Programmer responseRemove all PSBs that reference the named DBD fromthe control statement list, and rerun the program.

Module:DFSUAMB0


DFS0571E I/O ERROR ATTEMPTING TO STOWIN ACBLIB DIRECTORY

ExplanationAn I/O error occurred during the execution of an OSSTOW macro within module DFSUAMB0.

Programmer responseCorrect the condition that led to the I/O error,and rerun the program. For more information aboutrecovering from ACBLIB errors, see the descriptionin IMS Version 15 Operations and Automation aboutrecovering from IMS failures.

Module:DFSUAMB0

DFS0572A THE ACBLIB DIRECTORY IS FULL.INCREASE DIRECTORY SIZE ANDRERUN.

ExplanationInsufficient directory space was allocated in theIMS.ACBLIB partitioned data set.

Programmer responseEither delete unused PSBs and DBDs from the ACBLIB,using the DELETE function, or copy the contents ofthe current ACBLIB to a new data set with a largerdirectory allocation.

Module:DFSUAMB0

DFS0573E I/O ERROR DURING BLDL ONACBLIB DIRECTORY

ExplanationAn I/O error occurred during the execution of an OSBLDL (build library directory list) macro within moduleDFSUAMB0.

Programmer responseCorrect the condition which led to the I/O error,and rerun the program. For more information aboutrecovering from ACBLIB errors, see the descriptionin IMS Version 15 Operations and Automation aboutrecovering from IMS failures.

Module:DFSUAMB0

Related referencez/OS: BLDL completion codes

DFS574 UNEXPECTED DATA RECEIVED-INPUT IGNORED

ExplanationMFS received a field from the 3270 device that wasnot defined in the device input descriptor. Either thescreen size for the device was incorrectly definedduring IMS system definition, or a probable hardwaremalfunction has occurred.

System actionThe input is canceled.

Operator response:Retry the input. If the error persists, contact your IMSsystem programmer for assistance.

Programmer responseCheck to see that the specification of lines andcolumns in the SIZE keyword of the TYPE orTERMINAL macro used for IMS system definition forthis device is correct. If it is correctly specified, usethe /TRACE command to obtain a printout of theterminal input data received by IMS. Obtain a printoutof the DIF and compare the buffer addresses todetermine if a hardware error occurred.


Module:DFSCFE00





DFS575 SPA ERROR-CONVERSATIONTERMINATED

ExplanationIMS has detected an invalid program switch. It isinvalid because the application program tried to takeone of the following actions:

• Switch to an LTERM name.• Switch to a Fast Path exclusive transaction.• Switch to an undefined transaction.

System actionIMS terminates the transaction.

Operator responseInform the master terminal operator.

Programmer responseChange the application program to prevent thedescribed inconsistencies.

Module:DFSCMS00

DFS576I EXIT COMPLETED, TRANSACTIONDISCARDED

Explanation/EXIT processing found the transaction available inthis system and was able to discard it.

System actionThe conversation is terminated.

Module:DFSICLH0

DFS577I EXIT COMPLETED, TRANSACTIONSTILL ACTIVE

Explanation/EXIT command processing found that thetransaction was in a remote system or hasalready been scheduled for processing. Commandprocessing is completed and the conversation isterminated, but the conversational transaction will

still be run. When the conversational response isreceived, the Conversational Abnormal Terminationexit (DFSCONE0) is called and the response messageis queued to the response terminal.

System actionThe conversation is terminated.

Module:DFSICLH0

DFS0578I READ SUCCESSFUL FOR DDNAMExxxxxxxx MEMBER yyyyyyyy

ExplanationMember yyyyyyyy from DDNAME xxxxxxxx data set wassuccessfully read.


Module:DFSXRPS0, DFSIILD0, DFSDFN10, DFSDFN20

DFS0579W FIND FAILED FOR DDNAMExxxxxxxx MEMBER=yyyyyyyyRC=zz

ExplanationThe FIND failed for member yyyyyyyy from DDNAMExxxxxxxx data set. This problem can prevent IMSfrom acquiring information needed for initialization.Descriptor members are unavailable, if this messageis received for the MFS Device Characteristics Tableutility.

The hexadecimal return code zz can have the followingvalues:


04Name not found

08Permanent I/O error during directory search

System actionIMS might terminate with abend 0015 if the memberis required by IMS. IMS terminates with abend 1012if the member is DBFMSDBn. The MFS DCT Utilityterminates with a return code of 4.

Operator response:(master terminal) If IMS does not abend, determine ifmember yyyyyyyy is necessary for your installation. Forthe MFS DCT Utility, DDNAME xxxxxxxx is required.


Programmer responseFor a required member, make sure that the correctsuffix was specified, and member yyyyyyyy is valid. IfRC=08, place the member in a data set where it can beaccessed without error.


Module:DFSXRPS0, DFSIILD0, DFSPMBR0, DFSUTB00


DFS0580E UNABLE TO OPEN DCB-DDNAME=ddname

ExplanationThe data control block (DCB) indicated by ddname inthe message could not be opened.

System actionThe ACBGEN utility is terminated.

Programmer responseCheck the JCL, and rerun the program.

Module:DFSUACB0

DFS0581E I/O ERROR ON unit address, devicetype, ddname, operation, errortype, bbcchhr, access method

ExplanationA permanent I/O error occurred on the deviceidentified in the message text.


Programmer responseCorrect the error condition, and rerun the program.

Module:DFSUACB0

DFS0582E PERMANENT I/O ERROR DURINGBLDL ON REQUESTED DBDS INACBLIB

ExplanationBPAM encountered a permanent I/O error whiletrying to search the directory of the ACBLIB. It wasattempting to find the entry for one or more data basedescriptions (DBDs) that were requested on a BUILDor DELETE control statement.


Programmer responseRecreate ACBLIB with a PSB=ALL option, or restorethe ACBLIB with a backup copy if available. For moreinformation about recovering from ACBLIB errors, seethe description in IMS Version 15 Operations andAutomation about recovering from IMS failures.

Module:DFSUACB0

Related conceptsOther system data set failures (Operations andAutomation)Related referencez/OS: BLDL completion codes

DFS0583E PERMANENT I/O ERROR WHILETRYING TO DELETE DBD|PSB=name FROM ACBLIB USINGSTOW WITH DELETE OPTION.

ExplanationA program specification block (PSB) or databasedescription (DBD) was to be deleted from ACBLIB asthe result of a specific DELETE request or because therequired blocks could not be built. A permanent erroroccurred during the delete.


Programmer responseRecreate the ACBLIB with PSB=ALL option, or restorethe ACBLIB if a backup copy is available. For moreinformation about recovering from ACBLIB errors, seethe description in Other system data set failures(Operations and Automation) about recovering fromIMS failures.

Module:DFSUACB0

DFS0584E ERROR DURING PRE|POST-COMPRESS


http://www.ibm.com/support/knowledgecenter/SSEPH2_15.1.0/com.ibm.ims15.doc.oag/ims_otherdata_failure.htm#ims_otherdata_failure





ExplanationThe IEBCOPY utility returned a nonzero return codewhen attempting a compress of ACBLIB.


Programmer responseCorrect the error condition as indicated by theIEBCOPY error messages.

Module:DFSUACB0

DFS0585E UTILITY TERMINATED DUE TOERROR

ExplanationAn error indicated by a previous message causedthe program to terminate before all functions werecomplete. The return code is 16.


Programmer responseCorrect the errors, and rerun the program.

Module:DFSUACB0

DFS0586I {PSB psbname|DBD dbdname}REQUESTED IN A {BUILD|DELETEOPERATION} {NOT FOUND INACBLIB|IS A PSB}-REQUESTIGNORED.

ExplanationA build error is associated with the indicated PSB orDBD that was requested in a build or delete operation.

• If the message is NOT FOUND IN ACBLIB, the PSBor DBD does not exist in the ACBLIB data sets.

• If the message is IS A PSB, the directory entry forthis member is a PSB.

There is no first in, first out (FIFO) process for the ACBMaintenance utility SYSIN input control statements. Ifboth the BUILD PSB= and BUILD DBD= parametersare specified in the same application control block(ACB) generation job SYSIN control statement, DBD=operands are passed to the block builder utilityprogram first. Message DFS0586I is issued if the DBDis not already in the ACBLIB data sets, regardless

of where DBD= operands are specified in the SYSINcontrol statements.

System actionThis request is ignored. Processing continues, but thereturn code is 8.

Programmer responseCorrect the errors, and rerun the program.

Module:DFSUACB0

DFS0587I ERROR BUILDING PSB=psbname-IT WILL BE DELETED FROMACBLIB

ExplanationThe block builder returned a nonzero completioncode after processing the indicated PSB. The PSB isdeleted from ACBLIB, processing continues, and thereturn code is set to 8. If this message is precededby message DFS0921I, no member is deleted fromACBLIB because the indicated PSB is a DBD.

Programmer responseCorrect any errors indicated by the error messages,and rerun the program with a BUILD statement for thisPSB.

Module:DFSUACB0

Related information“DFS0921I” on page 334PSB psbname IS NOT A PSB

DFS588I CONTROL CARD SYNTAX ERROR-{INVALID LABEL|OP CODE|BLK TYPE|OPERAND|OPTION|FORMAT| CONTINUATION}<'symbol'>

ExplanationFor information, see message DFS0588I.

Related information“DFS0588I” on page 208CONTROL CARD SYNTAX ERROR- {INVALIDLABEL|OP CODE|BLK TYPE|OPERAND|OPTION|FORMAT| CONTINUATION} <'symbol'>

DFS0588I CONTROL CARD SYNTAX ERROR-{INVALID LABEL|OP CODE|BLK TYPE|OPERAND|OPTION|


FORMAT| CONTINUATION}<'symbol'>

ExplanationA control statement syntax error was detected. Theremaining statements are scanned, but no processingare attempted. The symbol enclosed in quotationmarks is the symbol or delimiter which caused theerror. If FORMAT is indicated, the logical end ofstatement was reached before the statement wascomplete. If CONTINUATION is indicated, an invalidcontinuation was detected.

Programmer responseCorrect the control statement, and rerun the program.

Module:DFSUACB0

DFS0589I PROCESSING COMPLETED FORPSB psbname. PCB=xxxxxx,PSB=xxxxxx, WORKAREA=xxxxxx,TOTAL SIZE=xxxxxx

ExplanationThe blocks for the indicated PSB were successfullybuilt and written to ACBLIB. The required buffer sizesfor inter-region copy are indicated. See the descriptionof the DIRCA parameter of the IMSBATCH procedure,in Parameter descriptions for IMS procedures (SystemDefinition). PCB is the work area size required in theMSG or BMP region. PSB is the size of the fixed PSBblocks required in the PSB pool. WORKAREA is thesize of various work areas required for the PSB andis obtained from the PSB work pool (PSBW pool). Seemessage DFS0593I for sizes of each of the variouswork areas. WORKAREA gives the size at ACBGENtime. This is the minimum size for the work areas.At scheduling time, this size can be increased. Asignificant increase can occur if the size is changed tothe size of the long message queue buffer. TOTAL SIZEis the combined PSB pool size and PSB work pool sizerequirement at ACBGEN time. The FP work areas usedfor EPCBs are not included in the WORKAREA above.

Module:DFSUACB0

Related information“DFS0593I” on page 209PSB-psbname WORKAREA BREAKOUT.NDX=xxxx, XIO=xxxx, IOA=xxxxxx, SEG=xxxxx,SSA=xxxxx

DFS0590I END OF ACBLIB MAINTENANCE.HIGHEST CONDITION CODE WAScode

ExplanationThe ACB Maintenance utility finished the requestedoperations. The highest condition code encounteredduring execution is indicated.

Module:DFSUACB0

DFS0591I MAX PCB SIZE=xxxxxx, MAX PSBSIZE=xxxxxx, MAX WORKAREASIZE=xxxxxx, MAX TOTALSIZE=xxxxxx

ExplanationThe PSBs operated on as a result of this executionrequire the indicated inter-region copy bufferrequirements as a maximum value. See the descriptionof the DIRCA parameter of the IMSBATCH procedure,in Parameter descriptions for IMS procedures (SystemDefinition). The individual sizes are indicated inmessage DFS0589I.

Module:DFSUACB0

Related information“DFS0589I” on page 209PROCESSING COMPLETED FOR PSB psbname.PCB=xxxxxx, PSB=xxxxxx, WORKAREA=xxxxxx,TOTAL SIZE=xxxxxx

DFS592I EMBEDDED EOF FOUND IN ACBLIB{DMB|PSB} name

ExplanationThe indicated PSB or data management block has anend of file within the member.

System actionThe PSB or data management block is stopped.

Programmer responseIf concatenated libraries are specified for IMSACB,verify that the library with the largest block size isspecified first. If ACBGEN has been run against alibrary that is shared with the online system, ensurethat the COMPRESS option was not specified. Ifneither of the above errors has occurred, the memberin ACBLIB, specified in the error message, must berecreate to correct the error condition.

Module:DFSDBLR0, DFSXRBL0

DFS0593I PSB-psbname WORKAREABREAKOUT. NDX=xxxx, XIO=xxxx,


http://www.ibm.com/support/knowledgecenter/SSEPH2_15.1.0/com.ibm.ims15.doc.sdg/ims_parameter_descriptions_for_procedures.htm#ims_procedure_parm_descriptions




IOA=xxxxxx, SEG=xxxxx,SSA=xxxxx

ExplanationThe total work area for the indicated PSB is brokendown into its components. NDX is the work arearequired for DL/I ACTION modules. XIO is the workarea used by index maintenance. IOA is the area usedto hold data being copied from or to a dependentregion. This size is specifiable on the PSB. SEG is thearea required for compressible segment manipulation.SSA is the area required to hold SSAs copied from thedependent region. This value is specifiable on the PSB.

Module:DFSUACB0

DFS594I MFS TEST FACILITY NOTAVAILABLE-xxxxx

ExplanationInitialization could not open the DCB for the MFS TESTlibrary. MFS TEST was unavailable. If xxxxx is NOFND,then no DD statement was found. If xxxxx is DUMMY,then DD DUMMY was specified. If xxxxx is NOOPN,then OPEN failed.

Programmer responseIf xxxxx=NOFND or DUMMY, correct the JCL for thenext IMS execution. If xxxxx=NOOPN, a z/OS messagedescribing the OPEN failure might be issued. If a z/OSmessage is received, see z/OS MVS System MessagesVol 1 (SA22-7631) for further information.

Module:DFSIINB0

DFS595I REGION SIZE TOO SMALL FORDFSUTR20 REPORT

ExplanationThe amount of virtual storage specified in the regionparameter of the EXECUTE statement was insufficientto hold the summary tables generated during the inputphase of a Monitor Report Print utility.

Programmer responseAssign a larger region to the job, and rerun it.

Module:DFSUTR20, DFSUTR30

DFS0596W READ FAILED FOR DDNAMExxxxxxxx MEMBER= yyyyyyyy

:

variable text

ExplanationThe READ failed for member yyyyyyyy from theDDNAME xxxxxxxx data set. This problem canprevent IMS from acquiring information required forinitialization.

The DDNAME xxxxxxxx data set is not valid forprocessing. This problem can prevent IMS fromacquiring information required for initialization. Thismessage is preceded by message DFS0596W, READFAILED, which provides the member name for theattempted READ.

In the message:xxxxxxxx

Data set nameyyyyyyyy

Membervariable text

The operating system SYNADAF macro instructionsupplies the text of this message.

System actionIMS might terminate with abend 0015 if the memberis required by IMS. IMS terminates with abend 1012 ifthe member is DBFMSDBn.

Operator response:(master terminal) If IMS does not abend, determine ifmember yyyyyyyy is necessary for your installation.

Programmer responseFor a required member, make sure that the correctsuffix was specified, and member yyyyyyyy is valid.Attempt to rebuild the member in a different locationin the data set.


Module:DFSXRPS0, DFSPMBR0

Related referencez/OS: SYNADAF error descriptionsRelated informationIMS abend 0015IMS abend 1012“IMS problem determination” on page 11


http://www-01.ibm.com/support/knowledgecenter/SSLTBW_2.4.0/com.ibm.zos.v2r4.idad500/synmess.htm?lang=en




DFS0597W OPEN FAILED FOR DDNAMExxxxxxxx

ExplanationThe OPEN failed for the DDNAME xxxxxxxx data set.If this message occurs during IMS initialization, IMSmight not be able to acquire the information neededfor initialization. If the MFS Device CharacteristicsTable utility issues this message, the descriptormembers are unavailable.

System actionIMS initialization abnormally terminates with abend0016. The MFS Device Characteristics Table utilityends with a return code of 12.

Operator response:(master terminal) If IMS does not abend, determine ifDDNAME xxxxxxxx is necessary for the installation. Forthe MFS Device Characteristics Table utility, DDNAMExxxxxxxx is required.

Programmer responseValidate the DDNAME xxxxxxxx data set and make surethat the DDNAME xxxxxxxx DD statement is included inthe JCL.




DFS598I NO DLI CALL REPORT REQUESTED

ExplanationNeither a DLI nor an ONLY DLI statement was includedin the analysis control data set.

Programmer responseIf you want a DL/I call report, include either DLI orONLY DLI in the analysis control data set and rerun thejob.

Module:DFSUTR10

DFS599I UNDEFINED ANALYSIS CARDIGNORED

ExplanationAn unrecognizable control statement appeared in theanalysis data set.

System actionProcessing continues with the next control statement,if any.

Programmer responseExamine and correct the statements in the analysiscontrol data set.


DFS600I NUMBER EXCEEDS 8 DIGITS

ExplanationA number in a distribution redefinition statementexceeded 8 digits.

System actionProcessing terminates. Redefinition is ignored for thedistribution identifier implied.

Programmer responseCorrect the distribution redefinition statement, andrerun the job.




Chapter 16. DFS messages, DFS601I - DFS650E


DFS601I NONNUMERIC DIGIT IN NUMERICFIELD

ExplanationA non-numeric character appeared in a numeric fieldof a distribution redefinition statement.

System actionProcessing continues. Redefinition is ignored for thedistribution identifier implied.

Programmer responseCorrect the redefinition statement, and rerun the job.


DFS602I INVALID DISTRIBUTIONIDENTIFIER

ExplanationAn invalid distribution identifier appeared in astatement in the analysis control data set.

System actionProcessing continues. The error statements areignored during execution.

Programmer responseCorrect the distribution redefinition statement, andrerun the job.


DFS603I IMS DLS CLEANUP(type) status FOR taskjobname.stepname.procstepnameRC=xx

Explanation:For information and actions, see DFS603W.

Related informationDFS603WIMS DLS FAILURE (xx) FOR task id

DFS603W IMS DLS FAILURE (xx) FOR task id

ExplanationThe IMS DL/I subordinate address space (DLS)resource cleanup processing (SSI routine) producestwo forms of message DFS603; one is a warning andthe other is informational.

The warning message, DFS603W, appears every time arecoverable failure occurs during cleanup processing.The message provides a failure code, xx, specifying thefunction executing at the time the failure is detected.DLS resource cleanup processing resumes with thenext function in the termination process.

The information message, DFS603I, is produced oncefor the job step TCB at the end of cleanup, andonce for each ESTAE failure under a subtask. AnESTAE failure occurs when the SDWA is not presentor no retry is possible. If all TCBs complete withouterrors, the informational message shows a status ofCOMPLETE with a zero return code; otherwise, for allbut exceptional failures where subtask error recordingis not possible, the status is FAILED with a return codeof X'FF'. (See the hexadecimal return codes describedlater in the message for the meaning of return codeX'FF'.)

Remember: When ESTAE is entered and retry ispossible, the SDWA is written to SYS1.LOGREC.Included in the entry are the job name, the releaseand level of the terminating IMS, and the failure code.The following table shows the message text:

Table 2. DFS603W message text

Keyword Values Meaning

type EOM EOT ESTAE End of Memory End of Task ESTAEfailure; no retry possible

status COMPLETE FAILED

IMS DLS resource cleanup finishedsuccessfully. IMS DLS resourcecleanup encountered at least onefailure during cleanup.

task ST JS Subtask Job step task

id jobnameID=imsid

For End of Task failure For End ofMemory failure

The return code, xx, indicates the results of DLSresource cleanup processing. A return code of X'00'indicates DLS resource cleanup finished successfully.Return code values X'30' through X'58' representfailures during End of Task termination. Values X'C0'through X'D8' represent failures during End of Memory


termination. The return codes have the followingvalues and meanings.Code (hex)

Meaning00

Cleanup finished successfully.01

GETMAIN failed for work area. Minimal cleanupprocessing is performed.

02Failure while attempting to obtain either the SSCDimage or SCD address, or both. The only cleanupperformed is to null the DLS REAL SSCT.

03Failure or operator cancel occurred during cleanupprocessing causing ESTAE to be driven for anunrecoverable failure. Abbreviated cleanup isattempted. ESTAE is unable to obtain storage forthe failure message. Processing terminates.

04ESTAE could not be established. Minimal cleanupprocessing is performed.

08Failure while attempting to obtain the SSCD imageor SCD address. Processing resumes with the nextfunction.

0CFailure while locating DLS DUMP SSCT orattempting to obtain the SSCD image or SCDaddress. The only cleanup performed is to null theDLS REAL SSCT.

10Failure while attempting to set IMS DLS REAL SSCTto null. Processing is terminated.

30Failure while updating the DLS control bits.Processing resumes with the next function.

34Failure while disconnecting cross-memory tables.Processing resumes with the next function.

38Failure while attempting to page free fixed storageobtained by the terminating TCB. Processingresumes with the next function.

3CFailure during delete subpool all function for task.Processing resumes with the next function.

50Failure attempting to set IMS DLS REAL SSCT tonull. Processing resumes with the next function.

54Failure while attempting to post the control region.Processing resumes with the next function.

58Failure while attempting to set IMS DLS DUMPSSCT to null. Processing resumes with the nextfunction.

D0Failure while attempting to set IMS DLS REAL SSCTto null. Processing resumes with the next function.

D4Failure while attempting to post the control region.Processing resumes with the next function.

D8Failure while attempting to set IMS DLS DUMPSSCT to null. Processing resumes with the nextfunction.

FCDLS cleanup processing canceled by operator.Abend X'x22' is intercepted by ESTAE, and no retryprocessing is permitted. An abbreviated form ofcleanup processing is performed by the ESTAEroutine.

FFDLS cleanup processing was completed, but one ormore failures occurred during cleanup.

System actionIf the return code is X'00' for End of Task termination,the DLS resource cleanup processing completedsatisfactorily. If the return code is X'00' for End ofMemory termination, cleanup completed satisfactorily,but is limited to non-task-related functions only. If thereturn code is X'FF', one or more failures occurred, andcleanup processing related to those failures might nothave been completed.


Module:DFSDRCL0


DFS0604W DCBRECFM IS NOT FIXED BLOCKFOR DDNAME xxxxxxxx

ExplanationThe DDNAME xxxxxxxx data set record format was notvalid. The record format must be fixed or fixed block. Ifthis message is received during IMS initialization, IMS


might not be able to acquire the information requiredfor initialization. If this message is received from theMFS Device Characteristics Table utility, the descriptormembers are unavailable.

System actionIMS initialization abnormally terminates with abend0010 for DDNAME PROCLIB. The MFS DeviceCharacteristics Table utility ends with a return code of12.

Operator response:(master terminal) If IMS does not abend, determineif the DDNAME xxxxxxxx DD statement is necessaryfor the installation. For the MFS Device CharacteristicsTable utility, DDNAME xxxxxxxx is required.

Programmer responseEnsure that the DDNAME xxxxxxxx data set hasRECFM=F or RECFM=FB.


Module:DFSXRPS0, DFSIILD0, DFSUTB00, DFSPMBR0


DFS0605W DCBBLKSIZE IS NOT VALID FORDDNAME xxxxxxxx

ExplanationThe DDNAME xxxxxxxx data set block size wasnot valid. If this message is received during IMSinitialization, this problem can prevent IMS fromacquiring information required for initialization. If theMFS Device Characteristics Table utility issues thismessage, the descriptor members are unavailable.

System actionIMS initialization abnormally terminates with abend0012 for DDNAME PROCLIB. The MFS DeviceCharacteristics Table utility ends with a return code of12.

Operator response:(master terminal) If IMS does not abend, determineif the DDNAME xxxxxxxx DD statement is necessaryfor the installation. For the MFS Device CharacteristicsTable utility, DDNAME xxxxxxxx is required.

Programmer responseEnsure that the DDNAME xxxxxxxx data set block sizeis a multiple of 80.


Module:DFSPMBR0, DFSXRPS0, DFSIILD0, DFSUTB00


DFS0606I MINIMUM CORE OF 16K BYTESWAS NOT AVAILABLE FORSUMMARY TABLE.

ExplanationThe initial GETMAIN that gets storage for tablesholding accumulated data failed.

System actionThe program terminates and returns with no reports.

Programmer responseIncrease the region size, and resubmit the job.


DFS607I UNEXPECTED CONTINUATIONCARD RECEIVED.

ExplanationA statement with at least one first blank characterappeared in the analysis control data set. It isa continuation statement, but is not precededby a distribution redefinition statement showing acontinuation. Continuation is indicated by a commafollowing the last operand.

System actionProcessing continues. The statement in error isignored.

Programmer responseCorrect this statement if it is not a continuationstatement, or show the continuation in the distributionredefinition statement previously defined for a futurerun.

Chapter 16. DFS messages, DFS601I - DFS650E 215




DFS0608W NULL ENTRY FOR DDNAMExxxxxxxx MEMBER = yyyyyyyy

ExplanationMember yyyyyyyy from the DDNAME xxxxxxxx data setwas empty.

System actionIMS might terminate with abend 0015 if the member isrequired by IMS.

Operator response(master terminal) If IMS does not abend, determine ifmember yyyyyyyy is necessary for your installation.

Programmer responseMake sure that the correct member suffix wasspecified and that member yyyyyyyy contains validdata.




DFS609I EXPECTED CONTINUATION CARDNOT RECEIVED.

ExplanationA continuation was indicated by a comma at theend of the last operand in a distribution redefinitionstatement. However, the following statement imagewas not a continuation.


Programmer responseProvide the missing continuation statement, if it wasneeded. If no continuation was intended, correct the

distribution redefinition statement so that the lastoperand ends with a blank.


DFS0610W GETMAIN FAILED FOR TABLE =zzzzzzzz

ExplanationTable zzzzzzzz could not be built. This problem canprevent IMS from acquiring information required forinitialization.

System actionIMS might terminate with abend 0008 if table zzzzzzzzis required by IMS. IMS terminates with abend 1012 ifthe member is DBFMSDBn.

Operator response:Increase the size of the region, and try IMS again.

Programmer responseValidate the size of the region.



Related informationIMS abend 0008IMS abend 1012“IMS problem determination” on page 11IMS messages and codes problemdetermination is accomplished by usingprocedures established by IBM.

DFS611I EXPECTED CONTINUATION CARDNOT RECEIVED AT ANALYSISEODAD.

ExplanationA continuation was indicated by a comma at theend of the last operand in a distribution redefinitionstatement. However, the end of the analysis controldata set was reached without getting a continuationstatement image.




http://www.ibm.com/support/knowledgecenter/SSEPH2_15.1.0/com.ibm.ims15.doc.msgs/msgs/0008.htm#kf00005


Programmer responseProvide the missing continuation statement, if it wasneeded. If no continuation was intended, correct thedistribution redefinition statement so that the lastoperand ends with a blank.


DFS0612I IMS LOGIC ERROR. R14=xxR15=yy

ExplanationIMS encountered an error. The xx value (hexadecimal)represents the return code from a called routine, andis present only when a called routine detects theerror. Otherwise, the xx field contains 00. The yy value(hexadecimal) identifies the reason for the error.xx yy

Meaning00 10

The database DDIR or Fast Path DMAC was notfound and was not passed on an EEQE CREATEcall. Module DFSTOPR0 issues return code X'10'.

00 11The EEQE was not found for an EEQE DELETE.Module DFSTOPR0 issues return code X'11'.

00 12The buffer length was not specified on an EEQECREATE. This problem might not be discovereduntil a later EEQE COPY call. Module DFSTOPR0issues return code X'12'.

xx 14During Batch Backout processing, DBRC was calledto change EEQE type. DBRC returned a nonzeroreturn code xx, described later in this message.Module DFSTOPR0 issues return code X'14'.

00 15An I/O Toleration EEQE CREATE during an XRFtakeover found an EEQE that was not owned bythis IMS and therefore not valid for this IMS totolerate. Module DFSTOPR0 issues return codeX'15'.

00 1FAn EEQE COPY request found an EEQE that waseither not owned or was a user type EEQE. ThisIMS should not have the block or control intervalin the buffer pool. Module DFSTOPR0 issues returncode X'1F'.

nn 22I/O retry during database close or I/O TolerationPURGE processing received a nonzero return codefrom the buffer handler routine. The nn valueis the hexadecimal return code from the buffer

handler. For additional information, see return andfunction codes information. Module DFSTOBH0issues return code X'22'.

00 31An X'26' or X'4026' log record containing a bufferimage was found, but the corresponding EEQE wasnot found. The EEQE is built from a prior X'25'or X'4025' EEQE log record. Module DFSTORS0issues return code X'31'.

00 32The X'25' or X'4025' EEQE log record beingprocessed could not find a DDIR for the databaseindicated in the EEQE. Module DFSTORS0 issuesreturn code X'32'.

xx 41The I/O Toleration EEQEs created during an XRFtakeover received the hexadecimal return code xxfrom DBRC. The DBRC return codes are describedlater in this message. Module DFSTODI0 issuesreturn code X'41'.

xx 42Return code xx was returned from DBRC whiledeleting an EEQE. The DBRC return codes aredescribed later in this message. Module DFSTODI0issues return code X'42'.

xx 43Return code xx is returned from DBRC whenadding an EEQE. The DBRC return codes aredescribed later in this message. Module DFSTODI0issues return code X'43'.

DBRC return codes

The DBRC hexadecimal return codes contained in thexx field have the following values and meanings:xx

Meaning04

The DBDS already has an EEQE.08

The database is not registered in the RECON dataset.

0CA DBDS is not registered in the RECON data set.

10The subsystem is not registered in the RECON dataset.

14The subsystem is not authorized to use thedatabase.

18The DBDS does not have an EEQE.


1CAll EEQE changes in the parameter could not besatisfied.

20The EEQE limit for the database has been reached.

2CInternal DBRC error.

30An invalid parameter was detected.

System actionThis informational message is sent to the masterterminal operator and the z/OS console. It precedesabend 0602.

Module:DFSTOBH0, DFSTODI0, DFSTOPR0, DFSTORS0

Related referenceReturn and function codes associated withthe external subsystem support (Messages andCodes)

DFS0613I CTL|DBC RGN U113 DUE TO SxxxUyyyy DURING DL/I CALL IN MPP|CCTL zzzzzzzz

ExplanationAn abend occurred while processing a DL/I call in aparallel DL/I call under the dependent region TCB orunder a DRA thread TCB for a Coordinator Control(CCTL). This problem caused a critical failure thatrequired an abnormal termination of the IMS controlregion.xxx

The system abend code. This code is S000 if it is auser abend.

yyyyThe user abend code. This code is 0000 if it is asystem abend.

zzzzzzzzJob name of the abending dependent region or thejob name of the CCTL.




Module:

DFSPCC20, DFSASK00Related informationIMS abend 0113“IMS problem determination” on page 11IMS messages and codes problemdetermination is accomplished by usingprocedures established by IBM.

DFS0614I I/O RETRY SUCCESSFUL. DATABASE dbname DDNAME ddnameRBN/RBA nnnnnnnn

ExplanationThe I/O error block or control interval for the blocknumber or RBA nnnnnnnn in database dbname wassuccessfully rewritten to or reread from a direct accessstorage device (DASD) when the reread/rewrite wasdone at database close time. The DD statement isidentified by dbname. The I/O error was corrected.

System actionThis informational message is sent to the masterterminal and the z/OS console when the I/O rewriteor reread is successful. Other block level sharingsubsystems are notified with an IRLM NOTIFY toremove their record of the I/O error. DBRC is told toremove the I/O error RBN/RBA from the database dataset (DBDS) record.


The I/O error was corrected.


The I/O error was corrected.

Module:DFSTOBH0

DFS0615I ALL I/O ERRORS SUCCESSFULLYCORRECTED FOR DATA BASEdbname

ExplanationAll I/O error blocks or control intervals for thedatabase dbname were successfully retried. Thismessage indicates that previous I/O errors werecorrected and it is not necessary to recover thedatabase. IMS automatically attempts to retry write orread I/O errors at database close time.


http://www.ibm.com/support/knowledgecenter/SSEPH2_15.1.0/com.ibm.ims15.doc.msgs/compcodes/ims_returnandfunctioncodes.htm#ims_returnandfunctioncodes




System actionThis informational message is sent to the masterterminal and the z/OS console.


Programmer responseIt is not necessary to recover the database.

Module:DFSTOCL0

DFS616I SYSTEM LOG DATASET NOTCLOSED- LOG WRITE ERROR

or

SYSTEM LOG DATASET NOT CLOSED- LOG WRITEERROR. LAST LOG SEQ NUMBER=xxxxxxxx

or

OLDS BUFFER PURGE FAILED

or

OLDS BUFFER PURGE FAILED. LAST LOG SEQNUMBER =xxxxxxxx

or

OLDS BUFFERS SUCCESSFULLY PURGED

ExplanationA permanent I/O error occurred on the last remainingIMS log data set. If dual logging is in effect for IMSbatch, the error occurs when both of the log data setsare damaged. For IMS online, the error occurs whenthe last remaining OLDS has a permanent I/O error ordoes not have enough space to complete a checkpointfreeze. There are 5 forms of this message.

The first form is issued when a permanent I/Oerror occurs on the last remaining IMS log data set.This form is also issued when an IMS batch regionterminates abnormally without successfully closingthe batch log (SLDS) and IMS fails to locate the last logrecord sequence number written on the batch SLDS.

The last log record sequence number is not included inthe message when:

• An IMS online system is running.• No blocks are written on the log at the time of abend.• An invalid block number is detected in the log

buffers.

The second form is issued when an IMS batch regionterminates abnormally without successfully closingthe batch log (SLDS), and the last log record sequencenumber written on the batch log is located in a logbuffer.

The third form of the message is issued when anIMS online system terminates abnormally withoutsuccessfully closing the online log data set (OLDS)and IMS fails to locate the last log record sequencenumber written on the OLDS. The last log recordsequence number is not included in the messagewhen:

• The OLDS is not opened when the OLDS Buffer PurgeESTAE routine (DFSFDLF0) receives control.

• DFSFDLF0 fails the GETMAIN request for itsmessage area.

• DFSFDLF0 fails to locate the last log sequencenumber written on the OLDS in all OLDS buffers.

The fourth form is issued when an IMS online systemterminates abnormally without successfully closingthe OLDS, and the last log record sequence numberwritten on the OLDS is located in a log buffer.

The fifth form is issued when an IMS online systemterminates abnormally and successfully purges allOLDS buffers during the OLDS Buffer Purge ESTAEroutine.

System actionFor the first two forms of this message, IMS terminatesabnormally. Otherwise, IMS continues processing.

Programmer responseFor the first two forms, allocate new log data sets toreplace the ones that have encountered I/O errors.It might be necessary to use the Log Recovery utilityto create log data sets free from WRITE or CLOSEerrors. When a sufficient number of log data setsare available, emergency restart IMS to continueprocessing. Otherwise, not action is required

Module:DFSFDLS0, DFSFDLG0

DFS0617I RDS BUFFERS HAVE BEENSUCCESSFULLY PURGED.


ExplanationDuring normal or STAE termination processing of IMS,the restart data set (RDS) buffers were successfullypurged. The checkpoint table has been written.

System actionIMS continues with its termination process.


Module:DFSRDS00

DFS0618A A RESTART OF A NON-ABNORMALLY TERMINATEDSYSTEM MUST SPECIFYEMERGENCY BACKUP OROVERRIDE.

ExplanationAn attempt to restart an IMS system, which DBRC didnot flag as abnormally terminated, failed. This problemoccurs most commonly after a power failure or duringrestart of an alternate system in an XRF-capableenvironment, but can occur in other situations.

System actionIMS terminates the restart and waits for the operatorto enter another restart command.

Operator responseMake sure that no IMS system is currently activewith the same subsystem name. Check for DBRC andDLISAS regions that might still be active after a priorfailure of the CTL region. If DBRC or DLISAS regionsare still active without a corresponding CTL region,cancel them before proceeding.

If there is no IMS system currently active withthe same subsystem name, then issue the /EREOVERRIDE command. In an XRF environment, issuethe /ERE BACKUP command.

Module:DFSRST00

DFS0619I JOBNAME.STEPNAME.PROCSTEPNAME MADE NON-SWAPPABLE

ExplanationThe named job step has been made nonswappable byusing the IMS no-swap service call of the IMS SVC

(DFSV4200). This message is provided for informationonly.

System actionThe requested caller is made nonswappable.

Module:DFSV4200

DFS0620I RESTART DATASET CLOSED

ExplanationThe restart data set was closed successfully.


Module:DFSFDPL0

DFS621W IMS type LEVEL (level)INCOMPATIBLE WITH REGION

ExplanationThe release level of the IMS region is incompatiblewith the installed release level of the module issuingthe message. The module might not be able to performthe required functions. The following table shows themeaning of the message:

Table 3. Meaning of DFS621W keywords


type RTM The IMS resource termination manager(DFSRTM00) is assembled at an olderrelease level than the terminating IMSregion. DFSRTM00 might not be able toperform the required resource cleanup.

SVC The IMS SVC (DFSVC200) is assembledat a release level incompatible with theinitializing IMS region. The SVC functionsfor this IMS region might fail or produceunexpected results.

level nnn The release level of the IMS moduleissuing the message.


Programmer responseInstall the correct level of DFSVC200 or DFSRTM00.

Module:DFSMRC20, DFSRTM00, DFSVC200


DFS0622I job.step.proc-KEY 0-7 NOTALLOWED FOR DLI, DEP ORUTILITY RGN

ExplanationYou specified a protect key of 0-7 for a DL/I, DEP, orutility region. In z/OS, only the online control region isallowed to run under a protect key in the range 0-7.

System actionIMS issues abend 0622 for the region that issued thismessage.

Programmer responseSee abend code 0622.

Module:DFSRRA00

Related informationAbend 0622

DFS623I job.step.proc-KEY 0-7 REQUIREDFOR ONLINE CONTROL REGION

ExplanationIMS attempted to initialize an online control region inz/OS with a protect key in the range 8-15; a key of 0-7is required.


Programmer responseSee the information for abend code 0623.

Module:DFSRRA00


DFS624I COMMAND VERB/OPTION NOTSUPPORTED (y)

ExplanationA command verb or option that is not supported byIMS was entered by the operating system MODIFYcommand interface or by an external subsystem. Thevalue of y represents up to 12 bytes of the commandverb or option input data.


Operator responseIf the MODIFY command was entered by the operator,check for spelling errors or format errors in thecommand. Correct the command and rerun.

Programmer responseMake sure that the command syntax is correct.

Module:DFSFCTT0

DFS625I IRLM RECONNECT COMMANDFAILED, CODE - nn

ExplanationThe OS operator has entered an OS MODIFY commandto IMS specifying RECONNECT, and IMS was unable tocomplete the IRLM RECONNECT command.

The value of nn is indicated by one of the followingcodes:Code (Dec)

Meaning04

The IRLM did not give the IMS status exit controlfor an IRLM failure. This means either IRLM has notbeen used at all during this execution of IMS orthe IMS-to-IRLM connection is still active. During areconnect attempt, be aware of the following:

• Every dependent region with an intent to usea database must go through terminate threadprocessing.

• Any such dependent region that does notterminate prevents IMS from completing thesteps necessary to clean up from the IRLMfailure.

• IMS cannot be reconnected to the IRLM or beterminated until all region disconnect processinghas completed.

• You must abend those regions that are in variousstages of disconnect processing (such as waitingin an application for a timer pop, or waiting for areply to a WTOR).

08IMS was unable to sign on to the IRLM againand the operator replied CANCEL to messageDFS039A.




12IMS found applications still scheduled against thedata bases which were active at the time of theIRLM failure and therefore could not proceed withthe IRLM reconnect command.

System actionProcessing continues without the use of the IRLM.

Module:DFSFCTT0, DFSRDSH0

DFS626I IRLM RECONNECT COMMANDSUCCESSFUL

ExplanationThe OS operator has entered an OS MODIFY commandto IMS specifying RECONNECT and IMS successfullyreconnected to the restarted IRLM. This message issent to both the Master Terminal Operator and theOS operator to inform them of the reconnection. TheMaster Terminal Operator can now start the stoppeddatabases as wanted.


Module:DFSRDSH0

DFS627I IMS RTM CLEANUP(type) status FOR taskjobname.stepname.procstepnameRC=xxx

Explanation:For information and actions, see message DFS627W.

Related informationDFS627WIMS RTM FAILURE (xxx) FOR task id

DFS627W IMS RTM FAILURE (xxx) FOR taskid

ExplanationThe IMS resource termination manager (RTM)produces two forms of message DFS627; one is awarning and the other is informational.

The warning message, DFS627W, appears every timea recoverable failure occurs during RTM processing, orwhen a nonzero return code is received from a routinecalled by RTM. The message provides a failure code,xxx, specifying the function executing at the time thefailure is detected. RTM resumes processing with thenext function in the termination process.

The informational message, DFS627I, is producedonce for the job step TCB at the end of cleanup,and once for each ESTAE failure under a subtask. AnESTAE failure occurs when the SDWA is not presentor no retry is possible. If all TCBs complete withouterrors, the informational message shows a status ofCOMPLETE with an X'00' return code; otherwise, thestatus is FAILED with a return code of X'FF'. (Seethe hexadecimal return codes described later in themessage for the meaning of return code X'FF'.)

Remember: When ESTAE is entered and retry ispossible, the SDWA is written to SYS1.LOGREC.Included in the entry are the job name, the releaseand level of the terminating IMS, and the failure code.

The following table shows the message text:

Table 4. DFS627W message text


type EOM EOT ESTAE End of Memory End of Task ESTAEfailure; no retry possible

status COMPLETEFAILED

IMS finished successfully. IMSencountered at least one failureduring cleanup.

task ST JS Subtask Job step task

id jobnameID=imsid

For End of Task failure For End ofMemory failure

The return code, xxx, indicates the results of resourcecleanup processing. Return code values X'00' throughX'FF' are produced by DFSRTM00. Values X'04'through X'78' represent failures during End of Tasktermination. Values X'C8' through X'EC' representfailures during End of Memory termination. Othervalues produced by DFSRTM00 apply to either typeof termination. Return code X'100' or greater areproduced by DFSMRC20. The return codes have thefollowing values and meanings.Code (hex)

Meaning00

Cleanup finished successfully.01

GETMAIN failed for work area. Minimal cleanupprocessing is performed.

04ESTAE could not be established. Minimal cleanupprocessing is performed.

08Not used.

0CA failure occurred while scanning the TCB Tableduring TCB validation. Processing resumes withthe next function.


10A failure occurred while performingAvailability Manager disconnect processing (XRFenvironments only). Processing resumes with thenext function.

14RTM received a nonzero return code fromGETMAIN when storage was requested forsave areas while performing Availability Managerdisconnect processing (XRF or Fast DatabaseRecovery environments only). Processing resumeswith the next function.

18A failure occurred while performing IMSIntersubsystem Interface termination processing.Processing resumes with the next function.

1CA failure occurred while disconnecting memory-to-memory window headers. Processing resumeswith the next function.

20A failure occurred while scanning TCB DEB chain.Processing continues with the next DEB on chain.

24A failure occurred while performing HALT I/O orquiesce function for channel to channel device.Processing continues with the next DEB on chain.

28A failure occurred while closing an OSAM data set.Processing continues with the next DEB on chain.

2CA failure occurred while closing an OS data set.Processing continues with the next DEB on chain.

30A failure occurred during processing, or nonzeroreturn code received from IMS Resource LockManager quit function. Processing resumes withthe next function.

34A failure occurred while page freeing OSAM shortterm I/O pages. Processing resumes with the nextfunction.

38A failure occurred while disconnecting cross-memory tables. Processing resumes with the nextfunction.

3CA failure occurred while releasing CSA storagefor RGPARMS. Processing resumes with the nextfunction.

40A failure occurred during processing or nonzeroreturn code received from SVC termination and

CSA cleanup routine. Processing resumes with SVCdirectory cleanup.

44A failure occurred during processing or nonzeroreturn code received from SVC directory cleanuproutine. Processing resumes with the nextfunction.

48A failure occurred while performing an ENFREQDELETE call to delete an IMS ENF listen exit.Processing resumes with the next function.

4CA failure occurred while performing an IXLDISCcall to disconnect from a coupling facility structure.Processing resumes with the next function.

50A failure occurred while performing an ENFREQDELETE call for the IMS ARM ENF listen exit.Processing resumes with the next function.

54A failure occurred while performing Media Managercontrol block clean up for opened Fast Path DEDBareas. Processing resumes with the next function.

58A failure occurred while performing Fast Path 64-bit buffer cleanup. Processing resumes with thenext function.

59-5BNot used.

5CA failure occurred while performing logger cleanup.Processing resumes with the next function.

5D-67Not used.

68Batch IRLM PC cleanup.

70A failure occurred attempting to set IMS DUMPSSCT to null. Processing resumes with the nextfunction.

74A failure occurred during delete subpool allfunction for IMS subtask. Processing resumes withthe next function.

C8RTM received a nonzero return code from theSVC directory cleanup routine. Processing resumeswith the next function.

CCRTM received a nonzero return code from the IRLMquit function. Processing resumes with the nextfunction.


D0A failure occurred attempting to route control toDFSRTM00. The ESTAE in DFSMRC20 interceptsthe abend and attempts an abbreviated cleanup.

ECA failure occurred attempting to set IMS DUMPSSCT to null. Processing resumes with the nextfunction.

F0The DL/I subordinate address space can terminatewithout successfully performing resource cleanupfor the region. If this happens, the DLS SSCTsmight be left after the DLS region has terminated,which can produce abends in the Master SchedulerBroadcast function. In attempting to preventcertain abends if running with a DLS region, thecontrol region job step TCB searches for the DLSSSCTs during cleanup processing. If either SSCTis found, SSCT cleanup is attempted. If cleanupof the DLS SSCTs succeeds, message DFS627WIMS RTM FAILURE (F0) FOR DLS is issued.If cleanup fails, the standard form of the warningmessage is issued. Processing resumes with thenext function.

FCResource cleanup processing canceled byoperator. Abend X'x22' is intercepted by ESTAE,and no retry processing is permitted. Anabbreviated form of cleanup processing isperformed by the ESTAE routine.

FFResource cleanup processing was completed, butone or more failures occurred during cleanup.Message DFS627W explains the reason for thefailure.

100While processing on behalf of an IMS TCB,DFSMRC20 determined that the DUMP SSCTwas invalid. No cleanup is attempted for theterminating TCB.

104ESTAE could not be established. Control isnot passed to DFSRTM00. The only processingattempted is setting the DUMP SSCT to null.

108DFSRTM00 address is zero in the SSCT.Abbreviated cleanup is attempted.

10CA failure occurred attempting to route control toDFSRTM00. The ESTAE in DFSMRC20 interceptsthe abend and attempts an abbreviated cleanup.

110Previous job step or end-of-memory cleanup wasattempted and failed. DFSMRC20 resets the IMS

DUMP SSCT to null and returns to z/OS. Some IMSresources might not have been cleaned up.

114DFSMRC20 was called for a non-IMS job step TCBin an address space with an active IMS SSCT.This is usually the result of a prior IMS resourcecleanup failure, or of DFSMRC20 not receivingcontrol for an IMS job step TCB termination.DFSMRC20 resets the IMS DUMP SSCT to null andreturns to z/OS. Some IMS resources might nothave been cleaned up.

118DFSMRC20 was called for task termination afterthe IMS job step TCB entered final terminationin module DFSRTM00. The job step task is stillactive. This situation is not an error; however, thiscode is used internally for tracing this event fordiagnostics.

System actionIf the return code is X'00' for End of Task termination,the resource cleanup processing for the IMS regioncompleted satisfactorily. If the return code is X'00'for End of Memory termination, cleanup completedsatisfactorily, but is limited to non-task-relatedfunctions only. If the return code is X'FF', one or morefailures occurred, and cleanup processing related tothose failures might not have been completed.


Module:DFSRTM00, DFSMRC20

Related information“DFS627I” on page 222IMS RTM CLEANUP (type) status FOR taskjobname.stepname.procstepname RC=xxx“IMS problem determination” on page 11IMS messages and codes problemdetermination is accomplished by usingprocedures established by IBM.

DFS628I ABNORMAL TERMINATIONSCHEDULED

ExplanationThe z/OS system console operator entered a MODIFYIMS.DUMP command to abnormally terminate the IMSregion.

System actionThe IMS region is abnormally terminated with amemory dump.


Module:DFSFCTT0

DFS629I IMS ttt TCB <action> IMS|SYSsss|uuuuvvvvIMS ttt TCB <action>IMS|SYS sss|uuuuvvvv

or

IMS BATCH REGION ABEND - IMS|SYS uuuu

or

PSW AT ERROR = hhhhhhhh hhhhhhhh

or

MODID = cccccccc EPA = aaaaaaaa

or

IMS DBC REGION ABEND

ExplanationFor IMS online, the first form of the message is issued;the third and fourth form might be issued. For IMSbatch, the second form is issued; the third form mightbe issued.

For a Database Control (DBCTL) subsystem, the fifthform is issued when the DBCTL or z/OS operator issuesa MODIFY command to stop the DBCTL region.

In the message text, the variables have the followingmeanings:ttt

IMS TCB type nameaction

The action is ABEND if the IMS control region isterminating or DUMP if a memory dump is beingproduced for a dependent region.

sssThe system abend code, if available

uuuuThe user abend code (if available) or the systemabend code

vvvvThe failing IMS address space or externalsubsystem

DLSThe failure was for a TCB in the DL/I addressspace.

IESThe failure was in the IMS support code of anexternal subsystem.

ESCThe failure was not in the IMS support code forthe failing external subsystem.

U0027Original abend code

No valueThe failure was in the IMS CTL address space.

hh..hhHexadecimal PSW contents

ccccccccModule executing at time of the error

aaaaaaaaHexadecimal address of module entry point

System actionFor some IMS TCB failures, the IMS systemterminates. For other IMS TCB failures, (such asdynamic allocation, Fast Path-dependent region,storage compression, and some DBRC failures) IMScontinues processing. For IMS external subsystemfailures, the external subsystem task terminates.

Operator responseIf an external subsystem task terminates, restart thetask with the /START SUBSYS command.

Programmer responseTo determine the cause of the problem, examine thediagnostic output, which can include:

• Spin-off dumps created by IMS external subsystemsor DBRC.

• Software LOGREC entries created by dynamicallocation.

• Fast Path-dependent region dumps created by FastPath-dependent regions.

Module:DFSFDMP0, DFSFLST0

DFS630I WAITING FOR IRLM INITIALSTATE.

ExplanationThe IRLM is in an initial WAIT state for all currentsubsystems to be identified, respective database


reverified, and backouts to be processed. Thismessage is sent to the OS operator and the MasterTerminal Operator prior to the WAIT state.

System actionProcessing continues after a short wait.

Operator responseIf the wait becomes excessive, you might need toreview all subsystems attached to the IRLM anddetermine which might be causing the delay. Thissubsystem (if IMS) will probably not have issued theDFS630I message.

ModuleDFSSDLB0

DFS631I DBRC ADDRESS SPACETERMINATION UNPREDICTABLEDUE TO CONTROL REGIONABNORMAL TERMINATION

ExplanationThe IMS control region may have terminatedbefore the connection between IMS and DBRC wascompleted. In this case the DBRC address space mightterminate abnormally or might not terminate at all.

The IMS control region may have terminated after theDBRC address space had abnormally terminated.

System actionDBRC may or may not be abnormally terminated.

Operator responseIf DBRC is not terminated, you must terminate it usingthe console.

ModuleDFSFSTM0

DFS632I job.step.proc-EXCESSIVE NUMBEROF PARAMETERS IN PARM FIELD

ExplanationThe EXEC statement PARM field contained too manypositional parameters.


Module:DFSRRA20

DFS0633I DBRC PARAMETER SPECIFIEDVALID ONLY FOR BATCH BACKOUT

ExplanationDBRC=C was specified, but the program name was notDFSBBO00. Batch Backout is the only valid programthat can be specified with the DBRC=C parameter.

System actionThe IMS job terminates abnormally with abend 0633.

Programmer responseCorrect the conflict between the DBRC and MBRparameters.

Module:DFSRRA00


DFS634I job.step.proc-BLANKENCOUNTERED AS FIRST CHAROF PARAM VALUE

ExplanationA positional parameter in the PARM field of the EXECstatement contained one or more leading blanks.

System actionSystem terminates abnormally.


Module:DFSRRA00

DFS635 COMMAND BUFFER TOO LARGE:CANNOT PROCESS COMMAND.

ExplanationThe entered command required a buffer length greaterthan X'FFFF' (65,535) bytes. X'FFFF' is the limitfor the /DISPLAY command, while X'7FFF' (32,767)bytes is the limit for all other commands. Thecommand in error probably contained the NODEkeyword with the ALL parameter.




Programmer responseReduce the storage requirements by reentering thecommand as multiple commands with a specifiedrange. The number of parameters that can be specifiedfor a /DISPLAY command is approximately 5500, and2500 for all other commands. Contact the systemprogrammer for assistance.

Module:DFSICL30

DFS636I job.step.proc-LAST FIXED LENGTHPARM VALUE TOO SHORT

ExplanationThe last fixed-length parameter value in the PARMfield of the EXEC statement was too short.


Programmer responseVerify that no preceding value is incorrect. Correct anyerror, and resubmit the job.

Module:DFSRRA20

DFS0637W xxxx REQUEST NOT SATISFIEDDUE TO POOL EXPANSION LIMIT

ExplanationOne or more requests for storage from the IMS storagepool xxxx were not satisfied. The request causes thepool size to exceed the upper expansion limit. Theupper limit is specified on the execution parameters.

System actionIf the caller specified that the IMS storage poolmanager waits for storage, the caller waits untilenough storage is returned to the storage pool tosatisfy the request or until the caller has waitedthe maximum number of compression cycles. If therequest is not satisfied, a nonzero return code isreturned to the caller.

Programmer responseIf this message is issued repeatedly for the samestorage pools, increase the upper expansion limit forthose pools.

Module:DFSSTAT0

DFS638I job.step.proc-COMMA FOUNDWITHIN EXTENT OF FIXEDLENGTH PARAM

ExplanationA comma was found within the extent of a fixed-lengthfield.



Module:DFSRRA00

DFS639W INVALID STG POOL DEF FOR (xxxx)(*) parm

ExplanationThe IMS.PROCLIB member DFSSPMnn contains astorage pool definition statement with an invalidparameter. The allowable parameters are pool nameand buffer definition.

If parm indicates FPL=zzzz, then the pool name isinvalid. The IMS storage pool zzzz has not beendefined.

If parm indicates (a, b, c, d), then the buffer definitionis invalid for pool xxxx. The following list defines thebuffer definition subparameters:a

Defines the buffer size, which is a unique 1 to5-digit numeric value. The allowable range is 8through 65536. The buffer size value is roundedup to the nearest multiple of eight.

bDefines the number of buffers in the primarystorage allocation. The value must be a 1 to 5-digitnumeric value in the range of 2 through 65535.

cDefines the number of buffers in secondarystorage allocations. The value must be a 1 to5-digit numeric value in the range of 2 through65535.


dDefines whether the primary storage allocation isobtained during IMS initialization. The allowablevalues are Y and N. If Y is specified, the primarystorage allocation is obtained during initialization.If N is specified, the primary storage allocation isnot obtained until it is needed to satisfy a bufferrequest.

One DFS639W message is issued for every occurrenceof an invalid parameter.

System actionIf the pool name parameter is invalid, the storagemanager ignores the definition for the pool whilecontinuing to validate the remaining parameters.

If the buffer definition parameter is invalid, either theparameter is interpreted or it is ignored.

If the value for subparameter a exceeds the allowablemaximum of 65536, a value of 65536 is used. Ifthe value for subparameters b or "c" exceeds theallowable maximum of 65535, a value of 65535 isused. If the subparameter d is invalid, the primaryallocation of storage is obtained when it is needed forprocessing and not during IMS initialization.

If the value for subparameter a is zero or isa previously defined value, the buffer definitionparameter is ignored. A maximum of thirty-twodefinitions are allowed for a pool. If an * precedesPARM, the maximum number has been exceeded andPARM has not been validated. It is ignored.

Programmer responseCorrect the invalid statement.

Module:DFSXSPM0

DFS640I job.step.proc-REQUIREDPARAMETER OMITTED FROMPARM FIELD

ExplanationA required parameter for the execution specified bythe first three characters of the EXEC statement PARMfield was omitted.



Module:DFSRRA20

DFS641I jobname.jobstep-INCORRECTREGION PARAMETER IN EXECSTATEMENT

ExplanationThe Database Recovery utility DFSURDB0 was run inan invalid region type. The batch region type specifiedin the first subparameter of the //EXEC PARM fieldmust be UDR.


Programmer responseSee abend code 0641.


DFS642I job.step.proc-PARAM EXCEEDSMAX ALLOWABLE LENGTH

ExplanationA parameter value, such as the program name ina DL/I execution, exceeded the maximum allowablelength.



Module:DFSRRA00

DFS643I job.step.proc-NON-NUMERICVALUE SPECIFIED FOR NUMERICPARAMETER IN PARM FIELD

ExplanationAll numeric parameters are examined; if a non-numeric value is specified for any numeric parameter,this message is sent to the console operator.

System actionThe IMS region that issues this message terminateswith abend 0643.



Programmer responseCorrect the EXEC statement parameter in JCL, andresubmit the job.


Module:DFSRRA00


DFS644I job.step.proc-INTERNALDESTINATION LIST IS INVALID

ExplanationSystem error was encountered.


Operator response:(z/OS System operator) Refer this error to IMSsystems operation personnel.

Problem determination1, 2, 3, 4, 36. Also, get an assembly listing ofDFSRRA00 as used on-site.

Module:DFSRRA20


DFS645W PRIMARY xxxx STORAGEEXCEEDED POOL EXPANSIONLIMIT

ExplanationDuring xxxx storage pool initialization, theaccumulated size of the primary buffer allocationsspecified exceeded the upper expansion limitspecified. This message is issued before any attemptto obtain storage for buffers. If the upper expansionlimit value specified is less than the sum of thestorage required to allocate all the primary buffer sizesspecified, this message is issued. No primary storage

is allocated for the pool. Storage blocks are allocatedas needed. All blocks in the pool are compressible.

System actionIMS initialization continues normally.

Operator responseNotify the system programmer.

System programmer responseThe default upper expansion limit for the pool mighthave been overridden using the EXEC parametersor the DFSPBxxx member. The default primary andsecondary storage pool allocations might need to beoverridden by storage pool definition statements inthe IMS.PROCLIB member DFSSPMxx. Ensure thatthe storage pool definitions specify the appropriatesize primary blocks and that the accumulated primarystorage allocation specification does not exceed thespecified upper limit.

Module:DFSSPM30

DFS646I job.step.proc-SPIE OPTION INPARM FIELD INVALID

ExplanationAn invalid SPIE option was found in the parameterfield. The SPIE option in the parameter field must be 0or 1.



Module:DFSRRA00


DFS0647W READ OF PSB psbname OR INTENTLIST FOR PSB RECEIVED INVALIDDATA. PSB STOPPED.

ExplanationA BLDL was done for the PSB to generate a directoryentry list, and a read issued on the TTR was returnedby the BLDL macro. After the read was completed, the



http://www.ibm.com/support/knowledgecenter/SSEPH2_15.1.0/com.ibm.ims15.doc.msgs/msgs/0646.htm#imsabens0646

results were invalid. The problem might result fromone of the following causes:

• For a DOPT PSB, a compression and a read occurredsimultaneously.

• For a nonresident PSB, a compression occurredsometime after the IMS system was start.

Operator responseTake one of the following actions:

• For a DOPT PSB, start the PSB after the compressionhas completed. Then, reschedule the job.

• For a nonresident PSB, an online change must bedone after the compression has completed.

DFS648I job.step.proc-VALIDITY CHECKOPTION IN PARM FIELD INVALID

ExplanationA validity check option in the PARM field was specifiedincorrectly.



Module:DFSRRA20


DFS0649W PSB psbname INSUFFICIENTFREE STORAGE BELOW 16MEG. REQUIRED = xxxxxxxxAVAILABLE=yyyyyyyy

ExplanationACB Generation attempted to build a PSB blockfor psbname, but the PSB generated size required

xxxxxxxx bytes of storage below the 16 MB line andonly yyyyyyyy bytes were available.

System actionThe PSB is deleted from ACBLIB and a return code 8 isset. ACBGEN continues with the next PSB.

Programmer responseRedesign the PSB with fewer SENSEG statements,fewer PCB statements, or both.

Module:DFSUAMB0

DFS650E NON-LE COMPLIANT PROGRAM INPERSISTENT JVM ENVIRONMENT,NAME=program_name

ExplanationYou attempted to load and execute a program thatdid not conform to the Language Environment (LE) ina persistent JVM dependent region environment. Anyprogram that executes in a persistent JVM dependentregion environment must be LE-conforming.

System actionAbend U0101-05 (reason code 5) is issued toterminate the application.

Programmer responseCorrect the program to make it LE-conforming. Theprogram did not contain a valid LE entry prolog. Ensurethat the program was compiled with a current LEenabled compiler.

Module:DFSPCC20

Related conceptsz/OS: Creating applications with z/OS LanguageEnvironmentz/OS: Preparing an application to run withLanguage Environment



http://www-01.ibm.com/support/knowledgecenter/SSLTBW_2.3.0/com.ibm.zos.v2r3.ceea200/usexst.htm

http://www-01.ibm.com/support/knowledgecenter/SSLTBW_2.3.0/com.ibm.zos.v2r3.ceea200/usexst.htm

http://www-01.ibm.com/support/knowledgecenter/SSLTBW_2.3.0/com.ibm.zos.v2r3.ceea200/wriapp.htm

http://www-01.ibm.com/support/knowledgecenter/SSLTBW_2.3.0/com.ibm.zos.v2r3.ceea200/wriapp.htm

Chapter 17. DFS messages, DFS0651W - DFS700I


DFS0651W ERROR XX READING DBD PSB INTyyyyyyyy FROM ACBLIB.

ExplanationValidation of the PSB, DBD, or intent list read fromACBLIB indicated an error. The block in error is notused.

The yyyyyyyy field indicates the name of the PSB, DBD,or intent list where the validation error was detected.The xx field indicates the validation error detected asfollows:

xxValidation error

01The read should have returned DMB yyyyyyyy.Validation of the data read indicated that what wasread was not a DMB.

02The read should have returned PSB yyyyyyyy.Validation of the data read indicated that it is notthe expected PSB.

03The PSB read is not consistent with the PSBsizes obtained from the ACBLIB PDS directory atinitialization time.

05The read of the intent list for PSB yyyyyyyy readzero bytes.

06The length of the intent list stored within the listitself for PSB yyyyyyyy is invalid.

07The length of the intent list read for PSB yyyyyyyyis not consistent with the length of the intent listobtained from the ACBLIB PDS directory at IMSinitialization time.

08The intent list for PSB yyyyyyyy contains invalidoffsets.

09The intent list for the PSB included DMB A butdid not include DMB B. DMB B is related toDMB A either by a secondary index or a logicalrelationship and should be included in the intentlist. The PSB is therefore inconsistent with its

DBDs. The ACBGEN utility must be run to resolvethe inconsistency.

10The DSG DMB offset is inconsistent with the intentlist length. This offset is used to retrieve theDDIR address from the PSB intent list. A DDIRaddress could not be retrieved because the DSGDMB offset is zero, negative, or larger than theintent list length. ACBGEN is required to resolvethe inconsistency.

11The data set group built for PSB yyyyyyyy isinconsistent with the data set group defined in therelated DBD. To resolve the discrepancy, run theACBGEN to rebuild the DBD. This can also occurwhen the PSB refers to a DBD that was not foundin the ACBLIB.

12The read did not return a time stamp when thisPSB was last rebuilt. The time stamp was usedto validate the consistency between this PSB andits DMB. The time stamp was generated by theACBGEN utility, and was stored at the end of PSB.You must run the ACBGEN utility again to rebuildthe PSB.

13One or more of the DMBs referenced in the PSBintent list has structural changes and has beenrebuilt. The PSB has not been rebuilt and is notconsistent with its DBD. You must run the ACBGENutility again to resolve the inconsistency.

14The DMB referenced in the PSB intent list isbeing committed by Member Online Change. Theprogram that uses this PSB cannot be scheduled.

15The PSB size in the PSB directory is not consistentwith the size obtained from the ACBLIB PDSdirectory at ACB online change time.

Possible reasons for the above errors are as follows:

• The active ACBLIB was compressed while beingused by IMS.

• Library Look Aside (LLA) was used improperly. Forexample, LLA was used for the inactive ACBLIB andthe resident directory was not updated followingthe copy of the staging library to the inactiveACBLIB. The /MODIFY COMMIT or INITIATE OLCPHASE(COMMIT) commands then switched the


inactive to the active with a back-level copy of thePDS directory for the ACBLIB left in memory. It ishighly recommended that LLA never be used for theACBLIB data sets.

• A PSB was copied to both the inactive and the activeACBLIBs before the /MODIFY COMMIT or INITIATEOLC PHASE(COMMIT) commands. If this occurs, thecomparison of the dates of the active and inactivewill be equal with the implication that the PSB didnot change. This will result in reading a new PSBwithout refreshing the PSB sizes kept in the PSBdirectory.

• There is a duplicate database definition for adatabase that has logical relationships. BecauseNAMECHK=NO was specified in the IMSCTRL macro,two copies of the same DDIR have been generated:the first DDIR contains a valid DMB address, but thesecond contains a DMB address of zeros. The PSBintent list could point to either the first or secondDDIR. This error message occurs when it points tothe invalid DMB address in the second DDIR.

System actionIf the error occurs on a DMB, the DMB is marked bad.Programs that use the DMB are not scheduled. Thecondition can only be corrected by replacing the DMBusing online change. If the error occurs on a PSB or anintent list, the PSB is marked bad unless it is a DOPTPSB, in which case it is stopped. Programs using thePSB will not be scheduled. If the PSB is a DOPT PSB,the condition can be corrected by replacing the PSB inACBLIB. If the PSB is not a DOPT PSB, it can only becorrected by replacing the PSB using online change.

If the PSB is not a DOPT PSB and the validation errorcode is 15, the error condition can only be correctedby not specifying the same ACBLIB data set on bothactive and inactive ACBLIB concatenation. As a result,ACB online change will not work.

Module:DFSXRBL0, DFSDBLD0, DFSDBLI0, DFSDBLP0

DFS652I job.step.proc-PARM FIELDOMITTED

ExplanationAll IMS run statements must contain a PARM field.



Module:DFSRRA20


DFS0653I PROTECTED CONVERSATIONPROCESSING WITH RRS ENABLED

ExplanationIMS initialized with the Resource Recovery Subsystem(RRS/MVS) and is prepared to participate in protectedconversation work.



Module:DFSRRSI0

DFS654I job.step.proc-PARM FIELD TOOSHORT

ExplanationPARM field specified in the EXEC statement was lessthan 3 characters in length.



Module:DFSRRA00


DFS655I CTL RGN U780 RC=xxxx DUE TOSyyy Uzzzz WHILE HOLDING ALATCH IN MPP nnnnnnn

ExplanationAn abend occurred while holding an IMS latch andcaused a critical failure that required an abnormaltermination of the IMS control region.xxxx

Represents the return code of abend 0780. For anexplanation of individual return codes, see abend0780 information.




yyyRepresents the system abend of the dependentregion abend code. (If the abend is a user abend,the system code is represented by S000.)

zzzzRepresents the user abend of the dependentregion abend code. (If the abend is a systemabend, the user code is represented by 0000.)

nnnnnnnJob name of the terminating dependent region.

Module:DFSASK00


DFS656I job.step.proc-PROTECT KEYOPTION INVALID IN PARM FIELD

ExplanationThe value specified in the EXEC statement for theonline control program (CTL) was invalid. Only thevalues 0 and 1 are valid.

Programmer responseCorrect the error, and reissue the IMS STARTcommand.

Module:DFSRRA20

DFS0657I IMS rrr ABENDUaaaa MODULE=mmmmmmmmLABEL=llllllll R14=xxxxxxxx

ExplanationThe GSAM initialization process encountered an error.The variable fields are defined as follows:IMS rrr

IMS release levelUaaaa

IMS abend codeMODULE=

Module that detected the errorLABEL=

Unique label at which the error was detected. Thisvalue corresponds to the error reason code. Seethe information about the IMS abend code.

R14=BAL return register (to the module that discoveredthe error).

System actionThe program terminates abnormally with the abendcode identified as aaaa.

Operator responseDetermine the cause of the error, correct the problem,and rerun the job.

Module:DFSZDI00

Related conceptsIMS abend codes (Messages and Codes)

DFS658I job.step.proc-PROGRAM NAMEPARAMETER OMITTED FROMPARM FIELD

ExplanationThe program name parameter was omitted from thePARM field.


Module:DFSRRA00

DFS0659I CTL RGN U780 RC=xxxx BECAUSECCTL yyyyyyyy WAS TERMINATEDWHILE DBCTL THREAD HELDLATCH

ExplanationThe CCTL was terminated while a DBCTL thread washolding an IMS unrecoverable latch. This problemcaused a critical failure that required an abnormaltermination of the IMS control region.xxxx

Represents the return code from the failed attemptat latch recovery. For an explanation of returncodes, see the IMS abend 0780 information.

yyyyyyyyJob name of the terminated CCTL region.

Module:DFSSDA30


DFS660I job.step.proc-PARM FIELDOMITTED FROM EXEC STATEMENT

Chapter 17. DFS messages, DFS0651W - DFS700I 233


http://www.ibm.com/support/knowledgecenter/SSEPH2_15.1.0/com.ibm.ims15.doc.msgs/abends/ims_aboutimsabendcodes.htm#aboutimsabends


ExplanationAll IMS execute statements must contain a PARM field.

Programmer responseSee the information about PARM fields.

Module:DFSRRA00

Related conceptsSpecifying IMS execution parameters (SystemDefinition)Related referenceParameter descriptions for IMS procedures(System Definition)

DFS0661I CANNOT PROCESS /STARTREGION COMMAND:MEMBER=member_name JOBNAME=job_name RC=X'xxxxxxxx'

ExplanationThe /START REGION command with the specifiedmember and job name failed for one of the followingreasons:04

The JOB statement is missing from the PROCLIBmember.

08An incomplete statement was encountered.

0CUnable to add the IMSID parameter to the EXECstatement.

10The parameter field is continued incorrectly.

14The EXEC statement has no parameters.

18The PROCLIB cannot be opened.

1CThe data set record format is incorrect.

20The data set block size is incorrect.

24The PROCLIB member cannot be found. Theinstream procedure is not supported by thegeneric /START REGION command.

28The first statement of the PROCLIB member is notthe JOB statement.

2CThe procedure statement is not valid. The instreamprocedure is not supported by the generic /STARTREGION command.

30The EXEC statement is missing.

Programmer responseVerify that the member and job names are correct.Also check the JCL statements in the specifiedmember. Make the necessary corrections and reissuethe command.

Module:DFSPMBR0

DFS662I job.step.proc-FIRST POSITIONALPARAM IN PARM FIELD ISINVALID

ExplanationThe first positional parameter in the PARM field wasinvalid.



Module:DFSRRA00


DFS0663I (Message text varies for DFS0663I,DFS0664W, and DFS0665E)

ExplanationSee the explanation for DFS0665E.

Related informationDFS0665E(Message text varies for DFS0663I, DFS0664W,and DFS0665E)

DFS0664W (Message text varies for DFS0663I,DFS0664W, and DFS0665E)

ExplanationSee the explanation for DFS0665E.

Related informationDFS0665E


http://www.ibm.com/support/knowledgecenter/SSEPH2_15.1.0/com.ibm.ims15.doc.sdg/ims_i2hspcx.htm#i2hspcx

http://www.ibm.com/support/knowledgecenter/SSEPH2_15.1.0/com.ibm.ims15.doc.sdg/ims_i2hspcx.htm#i2hspcx




(Message text varies for DFS0663I, DFS0664W,and DFS0665E)

DFS0665E (Message text varies for DFS0663I,DFS0664W, and DFS0665E)

ExplanationThe Fast Path trace routines issue messagesDFS0663I, DFS0664W, and DFS0665E. If you areunable to determine the problem, contact IBMSoftware Support. Save a copy of the message numberand text that you received.

Module:DBFTRAK0 (DFS0663I), DBFTRAK0 (DFS0664W andDFS0665E)

DFS0666I AREA xxxxxxxx COULD NOTBE PROCESSED DUE TO LOCKFAILURE

ExplanationThe AREA xxxxxxxx could not be processed for one ofthe following reasons:

• A /START, /STOP, /DBR AREA, or /STOP ADScommand was not processed because the AREALOCK failed.

• A /STOP or /DBR AREA GLOBAL command wasrejected because another subsystem holding theAREA LOCK is down.

System actionCommand processing terminates.

Programmer responseFor the second problem, use the LOCAL keywordinstead of the GLOBAL keyword.

Module:DBFARDA0

DFS667I NON-REENTRANT MODULES HAVEBEEN PRELOADED

ExplanationThe program module preload function loaded thespecified non-reentrant program modules into theregion/partition.

Module:DFSPCC20

DFS0668I PROCLIB BLKSIZE NOT MULTIPLEOF 80.

ExplanationThe IMS initialization process found the IMS PROCLIBdata set block size to be other than a multiple of 80.The logical record length must be 80.

System actionNo modules have been preloaded. Initializationcontinues.

Programmer responseContact your IMS system programmer.

Problem determinationSave the LISTCTLG and LISTVTOC for the IMSPROCLIB.

Module:DFSRRA00

DFS0669I PROCLIB RECFM NOT 'F' OR 'FB'

ExplanationThe IMS initialization process found the IMS PROCLIBdata set record format to be neither "fixed" nor "fixed-blocked".

System actionNo modules have been preloaded. Initializationcontinues.

Programmer responseContact your IMS system programmer. The IMSPROCLIB, to be usable, must be "F" or "FB".

Problem determinationSave the LISTCTLG and LISTVTOC for IMS PROCLIBconsole log.

Module:DFSRRA00

DFS670I job.step.proc-MODULES HAVEBEEN PRELOADED

ExplanationThe Program Module Preload function loaded thespecified program modules into the region/partition atinitialization.

Module:DFSPLDR0


DFS671I job.step.proc - FOR THISEXECUTION, DBRC IS SET TOFORCE FORCE | YES | NO

ExplanationAfter the processing of all the parameters wascomplete, the final DBRC parameter setting wasFORCE, YES, or NO.



Module:DFSRRA70, DFSRRA80

DFS0671W MEMBER DFSIDEF0 NOT FOUND -REQUIRED FOR INITIALIZATION

ExplanationMember DFSIDEF0 is required for IMS initialization,but could not be loaded.


Programmer responseThe DFSIDEF0 module is built by the Syntax Checker.

Module:DFSRRA00


DFS672I job.step.proc - MODULE DFSIDEF0CONTAINS UNEXPECTED DATA

ExplanationOptional defaults module DFSIDEF0 was successfullyloaded, but the verification of the contents foundunexpected data.

System actionThe following initial default is set for this execution ofIMS: DBRC=YES.

Programmer responseVerify that DFSIDEF0 has been built correctly.

Module:DFSRRA70, DFSRRA80

DFS0673E EPCB BUFFER REQUEST EXCEEDSPOOL SIZE. JOBNAME=job_nameREQ-SIZE=X'req_size'

ExplanationIMS attempted to obtain an EPCB buffer, and thelength specified was greater than the EPCB pool size.


job_nameThe name of the dependent region job that issuedthe storage request for the EPCB buffer

req_sizeThe length (in hexadecimal) of the EPCB bufferrequested

System actionThe dependent region is abnormally terminated.

Operator responseSpecify a larger EPCB Pool size at the next IMS start, orlower the EPCB size requirement for dependent region.

Module:DBFDBPV0


DFS674I job.step.proc-PROCLIB MEMBERCONTAINS BLANK RECORD

ExplanationThe IMS initialization process encountered an invalidrecord while reading the specified member of IMSPROCLIB. The first 71 characters were blank.

System actionNo modules have been preloaded or identified tovirtual fetch (VF), and initialization continues.

Operator responseContact your IMS system programmer.

System programmer responseCheck the member identified by job.step.proc in themessage and verify that it is valid.

Module:DFSPLPP0




DFS675I job.step.proc-PROCLIB MEMBERDELIMITER NOT FOUND

ExplanationThe IMS initialization process, while scanning arecord from the specified member of IMS PROCLIB,encountered a character other than one of thefollowing:

• blank - used to end a list of modules• comma - used between module names• $#@ - national characters• ABCDEFGHIJKLMNOPQRSTUVWXYZ - alphabetic

characters• 0123456789 - numeric characters

System actionNo modules have been preloaded or identified tovirtual fetch (VF), and initialization continues.

Module:DFSHLIN0, DFSPLPP0

DFS676I job.step.proc-NO MODULES HAVEBEEN PRELOADED

ExplanationNone of the modules specified for preloading wereeligible.

System actionNo modules have been preloaded, but initializationcontinues.

Operator responseNotify the IMS system programmer at your installation.

Programmer responseTo determine if the preload function is being usedcorrectly, see the system definition information.


Module:DFSPLDR0


DFS677I PERMANENT I/O ERROR ON JOB/LINK/SVCLIB FOR FOLLOWINGMODULES:

ExplanationModule preload encountered an I/O error whenscanning the PDS directories for STEPLIB, JOBLIB,SYS1.LINKLIB, or SYS1.SVCLIB. The modules forwhich it was scanning are listed following thismessage.

System actionIMS terminates abnormally with an abend 0718.

Operator responseContact your IMS system programmer for assistance.

Programmer responseIf you decide this is a permanent condition, follow yourPDS recovery procedure.


Module:DFSPLPP0


DFS678I BLDL FAILED FOR FOLLOWINGMODULES:

ExplanationThe modules listed were not found when modulepreload scanned the PDS directories for: STEPLIB,JOBLIB, SYS1.LINKLIB, or SYS1.SVCLIB.

System actionInitialization continues. If the modules were not in theLINKPACK, an 806 system abend occurs.

Operator responseIf an 806 system abend occurs, give the IMS systemprogrammer in your installation the storage memorydump and the z/OS console printout.


http://www.ibm.com/support/knowledgecenter/SSEPH2_15.1.0/com.ibm.ims15.doc.msgs/msgs/0718.htm#imsabned0718

Programmer responseIf an 806 system abend occurs, check the PDSs fordamage.


Module:DFSPLDR0, DFSPLPP0

Related referencez/OS: BLDL completion codesRelated information“IMS problem determination” on page 11IMS messages and codes problemdetermination is accomplished by usingprocedures established by IBM.

DFS679I FOLLOWING MODULES NOTLOADED: module_names

ExplanationModule preload attempted to load the listed modules,but z/OS failed or the IMS Module Manager(DFSMODU0) rejected the load request. The returncode follows each module name. For an explanation ofthe IMODULE LOAD return codes, see the IMS systemservices return code information.

This message might also be issued if sufficient storageis not available.

System actionIf any of the modules are required by IMS, abend 0718follows. If all of the modules are optional, initializationcontinues.

Operator responseContact the IMS system programmer at yourinstallation.

Programmer responseCheck the JOB/STEPLIB PDS member attributes. Toavoid possible physical damage to the DASD pack, youmight want to again bind those modules that were notloaded.

If sufficient storage is not available, increase the SQA,CSA, or region size, as needed.


Module:DFSPLDR0

Related referenceIMS system services return codes (Messagesand Codes)Related informationIMS abend 0718“IMS problem determination” on page 11IMS messages and codes problemdetermination is accomplished by usingprocedures established by IBM.

DFS680I USING CHKPT yyddd/hhmmss

ExplanationThe system selected this checkpoint for emergency ornormal restart.

System actionNormal processing continues.

Module:DFSRBCP0

DFS681I CHKPT xxx PSB psbname JOBjobname ID userckptid yyy zzzzzz[X'nnnnnnnnnnnnnnnn']

ExplanationAn IMS batch or batch message processing (BMP) jobhas issued a CHKP checkpoint call. For a batch job,xxx is DLI, yyy is SER, and zzzzzz is the current volumeserial number of the output log. For a BMP, xxx is BMP,yyy is DDN, and zzzzzz is the ddname of the currentoutput online log data set, OLDS.

In either case, in the message text:

• psbname is the name of the PSB which issued thecheckpoint call

• userckptid is the 8-byte checkpoint ID valuespecified by the application program.

• If it appears, nnnnnnnnnnnnnnnn is the EBCDICrepresentation of the HEX value of the checkpointID.

To suppress issuing this message, code NOMSG681on the CKPTID= EXEC parameter. If you also want tosuppress issuing message DFS0540I and DFS0542I,code NOMSGS. If you want to suppress only messagesDFS681I and DFS0542I, code NO681542.

Note: In most cases, the checkpoint ID consistsof printable universal character data. When thecheckpoint ID consists of printable universal characterdata, the EBCDIC representation of the HEX value ofthe checkpoint ID does not appear. If the EBCDIC



http://www.ibm.com/support/knowledgecenter/SSEPH2_15.1.0/com.ibm.ims15.doc.msgs/compcodes/ims_imssystemservicesretcodes.htm#ims_imssystemservicesretcodes



representation of the HEX value does appear, it mustbe translated to binary for restart purposes.


Module:DFSRDBL0, DFSRBLB0

DFS682I BATCH-MSG PROGRAM pgmnameJOB jobname MAY BE RESTARTEDFROM CHKPT ID id-value[X'nnnnnnnnnnnnnnnn']

ExplanationOne of the following occurred:

• IMS was processing the checkpoint FREEZEcommand and the batch message processingprogram listed made a CHKP call with the indicatedcheckpoint ID value.

• During emergency restart processing, the batchmessage processing program listed was processingat the time of system failure. The indicated CHKPT-ID was the last CHKP call issued. All databases andthe message queue have been restored to reflect thestatus that existed at the time the CHKP call wasissued.

Note: The jobname and psbname are the same if thismessage was issued during emergency restart.

• The indicated CHKPT-ID was the last CHKP callissued before abnormal termination of the listedbatch message processing program. All databasesand the message queues have been restored toreflect the status that existed at the time the CHKPcall was issued.

Note: In most cases, the checkpoint ID consistsof printable universal character data. When thecheckpoint ID consists of printable universal characterdata, the EBCDIC representation of the HEX value ofthe checkpoint ID does not appear. If the EBCDIChexadecimal value nnnnnnnnnnnnnnnn does appear,it must be translated to a binary value for restartpurposes.


Operator response(master terminal) Take one of the following actions:

• If the batch message processing program readsmessages from the message queue and does notrequire restart routines, start the program in thenormal manner.

• If the batch message processing program does notread messages from the queue or requires restartroutines, restart the program from the checkpoint IDlisted.

Problem determination4, the log data set being used for restart, or the currentIMS system log if restart is not in progress.

Module:DFSRBLB0, DFSRBOI0, DFSRDBL0


DFS683I nnnnn DFS681I MESSAGESSKIPPED FOR BMP=PSBNAMEJOB=JOBNAME

ExplanationThis message is issued when a number, nnnnnn,of DFS681I messages were omitted per batch/BMPregion. You can specify the maximum numberof DFS681I messages to be issued per secondin a batch/BMP region. This is done on theOPTION,ISSUE681= statement within the DFSVSMxxmember. If some of these messages are omitted as aresult, DFS683I gives the number omitted.

System actionNormal processing continues

Operator responseIf a large number of DFS681I messages areskipped for a BMP region, the application might belooping. Contact the IMS system programmer at yourinstallation.

ModuleDFSRDBL0

Related information“DFS681I” on page 238CHKPT xxx PSB psbname JOB jobname IDuserckptid yyy zzzzzz [X'nnnnnnnnnnnnnnnn']

DFS684I job.step.proc-CTL PROGRAM NOTEXECUTED, SVC INITIALIZATIONFAILED


ExplanationIMS type 2 SVC initialization failed. Some possiblereasons for the failure are:

• An attempt was made to start a second copy of IMScontrol region with the same IMSID as one alreadyrunning. This can also occur if IMS SVC terminationfailed in a previous run of IMS with the same IMSID.

• The IMS SDFSRESL is not authorized or the IMS SVCmodule is being loaded from an unauthorized library.

• The region size is too small.• Not enough CSA is available.

Abend 0684 and message DFS686W accompany thismessage.

System actionThe region that issued abend 0684 terminatesabnormally.

Programmer responseDo one of the following:

• Correct the duplicated IMSID situation and rerun thejob.

• Make sure IMS SDFSRESL is authorized or includethe DFSRESLB DD statement that points to anauthorized library containing the IMS SVC modules.

• Increase the region size.• Allocate additional CSA and IPL the system.

See abend 0684 and message DFS686W for additionalinformation.

Module:DFSRRA00

Related informationAbend 0684DFS686WIMS jobname imsid INIT/TERM (nn) FAILURERC=xxxxyyzz

DFS0685I WRITE TO INTERNAL READERFAILED: DDNAME=data_set_nameMEMBER=member_name JOBNAME=job_name

ExplanationWriting the specified member to the internal readerfailed.

Programmer responseCheck any messages that the internal reader mighthave issued. Verify that the member, data set, andjob names are correct. Make the necessary correctionsand reissue the command.

Module:DFSPMBR0

DFS686W IMS jobname imsid INIT/TERM (nn)FAILURE RC=xxxxyyzz

ExplanationAn SVC initialization or termination failure occurredduring processing. The jobname and imsid identifythe IMS system. If the imsid field is N/A, the imsidwas unavailable at the time the message was issued.The function code nn identifies the SVC initializationor termination function processing at the time of theerror. Possible function code values are:Code

Function01

INITSVC, SVC initialization02

INITDEP, dependent region initialization03

Reserved04

TERMSVC, SVC termination05

TERMDEP, dependent region termination06

Reserved07

INITSCD, initialize SCD in IMS SVC vector table08

KILLSVC, clear SVC directory entries09

INITBAT, batch region initialization

Return code xxxxyyzz identifies the type of failure andwhere it occurred:xxxx

If nonzero, xxxx is the return code from a servicecalled by the SVC. For IMODULE and IMSAUTHfailures, see the IMS system services return codeinformation.

yyThe module that issued the message:

03=DFSVC20005=DFSVCI00



zzThe return code from the SVC module thatindicates what type of failure occurred.

The values for yyzz for DFSVC200 failures are:301

GETMAIN failed for DFSVCI00 parameter list.302

Invalid function303

SVC directory block address is zero or unable tolocate directory entry for region.

304Region type of caller is invalid for request.

305Vector table address is zero.

306SVC release is incompatible with IMS release.

307SVC number is invalid in SSCD/SCD.

308GETMAIN failed for DCB work area.

309SSCD copy failed.

30ASVC number changed in SSCD after SVC validation.

30BSCD address is zero.

30CRMPL address is zero.

30DNon-authorized caller of an authorized function.

30EInvalid SCDRGTYP value.

30FOnline IMS caller is not in a system key.

The values for yyzz for DFSVCI00 failures are:501

Invalid function502

Invalid caller503

Duplicate IMSID505

GETMAIN failed for SVC directory block.506

GETMAIN failed for SVC vector table.507

IMSAUTH BLDSSCT failed.

508IMODULE LOAD for DLS/LSO table failed.

509IMODULE LOAD for an IMS SVC routine failed.

For batch IMS, the routine is one of the following:DFSAOS70, DFSV4200, DFSV4300, or DFSV4400.

Ensure that these modules are in an authorizedlibrary.

For online IMS, the routine is one of the following:DFSAOS70, DFSASK00, DFSBCK00, DFSICSC0,DFSUICC0, DFSV4100, DFSV4200, DFSV4300,DFSV4400, or DFSVES00.

Ensure that these modules are in the IMSSDFSRESL data set.

50AIMODULE LOAD for DFSAOSF0 failed. For batchIMS, ensure that this module is in an authorizedlibrary.

50BIMODULE LOAD for DFSISI00 failed.

50CGETMAIN failed for SSVT.

50DCaller is using invalid SVC number.

50EIMODULE GETMAIN for key 7 SCD failed.

50FIMSAUTH SSCTSCD failed.

510IMODULE LOAD for DFSSTM00 failed. For batchIMS, ensure that this module is in an authorizedlibrary.

511IMODULE LOAD for DFSKPXT0 failed. For batchIMS, ensure that this module is in an authorizedlibrary.

512IMODULE LOAD for DFSTOPR0 failed. For batchIMS, ensure that this module is in an authorizedlibrary.

513IMODULE GETMAIN for CBT header failed.

514IMODULE LOAD for DFSBC000 failed. For batchIMS, ensure that this module is in an authorizedlibrary.

515Unable to initialize DFSCBT10 blocks. For batchIMS, ensure that this module is in an authorizedlibrary.


516Unable to initialize CBTE blocks.

517IMODULE LOAD for DFSSPF00 failed. For batchIMS, ensure that this module is in an authorizedlibrary.

518IMODULE LOAD for DFSLMGR0 failed. For batchIMS, ensure that this module is in an authorizedlibrary.

519GETMAIN failed for DFSSTM00 work area.

51AUnable to obtain SRBC IPAGE.

51BInvalid SSCD eyecatcher in caller-passed SSCDblock.

51CIMODULE LOAD for DFSLRH00 failed. For batchIMS, ensure this module is in an authorized library.

51DModule assembled at level incompatible with IMSrelease.

51EBatch Region initialization failed - two IMS imagesin the same address space using the same IMS ID.

51FBatch Region initialization failed - two IMS imagesin the same TSO address space.

520Batch Region initialization failed - two IMS imagesin the same address space using the same TCB.

521Dependent Region initialization failed - two IMSimages in the same address space, same IMS ID,and one of the images not a dependent region.

522Dependent Region initialization failed - two IMSimages in the same address space, same IMS ID,both dependent regions, but different TCBs. (Thisis not a dependent region waiting for a controlregion to come up and going through SVC INITretry logic.)

523Dependent Region initialization failed - two IMSimages in the same address space and one of themis a control region.

524Dependent Region initialization failed - two IMSimages in the same TSO address space.

525Dependent Region initialization failed - two IMSimages in the same non-TSO address space, notcontrol regions, but the same TCB.

526IMODULE LOAD for DFSDCFR0 failed. For batchIMS, ensure that this module is in an authorizedlibrary.

527IMODULE LOAD for DFSDXES0 failed. For batchIMS, ensure that this module is in an authorizedlibrary.

528IMODULE LOAD for DFSDMAW0 failed. For batchIMS, ensure that this module is in an authorizedlibrary.

529IMODULE GETMAIN for key 7 CFB failed.

52AIMODULE LOAD for DFSDCFC0 failed. For batchIMS, ensure that this module is in an authorizedlibrary.

52BIMODULE LOAD for DFSRRSB0 failed. For batchIMS, ensure that this module is in an authorizedlibrary.

52CUnable to load module DFSRTMI0. For batch IMS,ensure that this module is in an authorized library.

52DUnable to establish resource cleanup environmentfor IMS.

52EIMS was started on a machine that was notrunning in z/Architecture® mode. IMS requires z/Architecture mode.

52FIMS was started on a z/OS release that doesnot support 64-bit virtual storage services. IMSrequires 64-bit storage services.

530Initialization of IMODULE services failed. See thepreceding DFS4342E message for details aboutthe failure. xxxx in the message is the returncode from IMODULE services initialization moduleDFSMODX0.

531IMS was started on an unsupported processortype. IMS 15 and later requires a System z10®

processor (machine type 2097) or above. See theIMS Version 15 Release Planning for a complete listof supported processors.


532Double INITBAT call. DFSVCI00 was called forbatch SVC initialization, but batch initialization wasalready done.

533DFSVCI00 was called for batch SVC initialization,but the region type did not indicate it was a batchIMS region.

534IMODULE LOAD for DFSMDA00 failed. For batchIMS, ensure that this module is in an authorizedlibrary.

535Getmain failed for BLDL in directed loadsubroutine.

536BLDL failed to locate the requested module indirected load subroutine.

537STORAGE OBTAIN for module directed load failed.

538LOAD failed to load module into storage.

539PGSER PROTECT module DFSISI00 failed.

System actionSVC initialization or termination processing terminates.The SVC module passes a return code to the caller,who might issue an IMS abend.

Programmer responseDetermine the cause of the failure and correct theproblem. For IMS batch job DFSVCI00 errors thatinvolve IMODULE LOAD, the modules that are beingloaded must come from an APF-authorized library. Ifyou are using a DFSRESLB DD statement in your batchjob, ensure that the modules that are listed under"Specifying the DFSRESLB DD statement in IMS batchprocedures" in are all included in DFSRESLB, and thatall of the data sets in the DFSRESLB DD concatenationare APF-authorized.


Module:DFSVCI00, DFSVC200

Related referenceIMS system services return codes (Messagesand Codes)Processor requirements (Release Planning)Related information“IMS problem determination” on page 11


DFS687I DBRC INDICATES DBD=x WITHINPSB=y WITH TOKEN=z WASBACKED OUT, RIS HAS BEENPURGED.

ExplanationWhile IMS attempts to build a recoverable in-doubtstructure (RIS), DBRC informs IMS that database xwithin PSB=y was altered under a unit of recoveryidentified by token z and was backed out throughBatch Backout. The online region considered thechanged data to be in an indoubt state.

System actionThe online system stops the database identified, but itdoes not build a recoverable in-doubt structure for thedata.

Programmer responseIf the backing-out of the data was intended, thena /START DB or UPDATE DB START(ACCESS)command makes the database available. However, ifbacking-out of the data was not intended, or if multipleresource managers are involved, an investigation intothe resolution of the in-doubt data must be made.

Module:DFSDRIS0

DFS688I job.step.proc-CANCELED BYOPERATOR. CTL PGM NOT ACTIVEhh.mm.ss

ExplanationThe control region was not active. This situationwas determined by the dependent region parameteranalysis. The job was canceled because:

• The cancel option (OPT=C) was specified on thedependent region EXEC statement.

• The operator entered CANCEL or C in response toerror message DFS690A.

Module:DFSRRA00

Related information“DFS690A” on page 244




http://www.ibm.com/support/knowledgecenter/SSEPH2_15.1.0/com.ibm.ims15.doc.rpg/ims_processors.htm#ims_processors

CTL xxxx NOT ACTIVE, REPLY 'WAIT' OR'CANCEL' - yyyyyyyy

DFS689I job.step.proc--DBRC/DLS REGIONCANCELED HH.MM.SS

ExplanationEither the DBRC or DL/I subordinate address spaceregion could not successfully connect to its associatedcontrol region. Most likely, the control region wasabnormally terminated.

System actionThe indicated region terminates with abend 0689.


Module:DFSRRA00


DFS690A CTL xxxx NOT ACTIVE, REPLY'WAIT' OR 'CANCEL' - yyyyyyyy

or

job.step.proc-CTL PGM NOT ACTIVE, REPLY 'WAIT'OR 'CANCEL' OR 'alt-id'

ExplanationThere are two forms of this message. In aDatabase Control (DBCTL) subsystem environment, aCoordinator Control (CCTL) subsystem tried to identifyto an IMS control program that was not active. Theinactive IMS control program is xxxx; the identifyingCCTL is yyyyyyyy.

For the second form of this message: a dependentregion started running when the IMS control orDatabase Control (DBCTL) region was not active.

System actionIf you entered WAIT, the dependent region waits;if you entered CANCEL, the dependent regionterminates. If you specified neither, the dependentregion uses the reply as a name of an alternate controlregion to which it attempts to identify.

If you entered WAIT, the CCTL waits before attemptingto identify again. If you entered CANCEL, the currentinitialization transaction is terminated.

Operator response(master terminal) Reply WAIT or CANCEL, if eitheris appropriate. If the control region will soon beavailable, reply WAIT. Reply with an alternate controlregion ID, if one is active.

The JCL for the dependent job region must specifythe same IMSID and SDFSRESL as the IMS controlregion. If the dependent region JCL IMSID is incorrect,reply with the correct control region ID. If SDFSRESL isincorrect, reply CANCEL, correct the dependent regionJCL, and resubmit the job.

Module:DFSRRA00, DFSPRA10

DFS691I WAITING FOR CTL xxxx - yyyyyyyy

ExplanationIn a Database Control (DBCTL) environment, IMSissues this message when the operator enters WAITin response to a DFS690A message. A CoordinatorControl (CCTL) subsystem is waiting for the IMScontrol program to become active. The inactiveprogram is xxxx; the identifying CCTL is yyyyyyyy.

System actionThe CCTL waits a user-specified number of seconds,taken from the TIMER= parameter in the DRA StartupTable, DFSPZPxx, before attempting to identify toDBCTL.

Module:DFSRRA00

Related information“DFS690A” on page 244CTL xxxx NOT ACTIVE, REPLY 'WAIT' OR'CANCEL' - yyyyyyyy

DFS692I jobname.stepname.procstepnameBUFFER CONTROL-BUF=value

ExplanationThe buffer control value might be used when the logterminator program is needed to close the log data set.

Module:DFSDLN00

DFS0693I RIS ESTABLISHED FOR PSBxxxxxxxx, PRTKN=yyyyyyyy,TOKEN=zzzzzzzz, RRS-



URID=wwwwwwwwwwwwwwwwwwww

ExplanationA Recoverable In-doubt Structure (RIS) wasestablished for a thread in either a CCTL-IMSenvironment or in an RRS protected conversationenvironment. The RRS-URID is supplied for onlyprotected conversation work and is the RRS unitof recovery interest token. The referenced PSB isxxxxxxxx, the pseudo token is yyyyyyyy, and the actualIMS recovery token is zzzzzzzz. The RIS is maintaineduntil a resynchronization process is performed withIMS.

Module:DFSDRIS0

DFS694I 'CTL' WAS SPECIFIED FOR JOBSTEP EXECUTION

ExplanationThe IMS control region was started using job JCL, butCTL was specified in the execution JCL parameter. IMSinitialization continued.

System actionThe IMS control program operates as a job step task.

This message can be avoided if the CTX" parameter isused, or if the IMS control region is started as a systemtask.

Programmer responseConsult the IMS system programmer for yourinstallation before doing this action.

Module:DFSRRA00

DFS0695I OSAM (OPEN|CLOSE|EOV)INTERCEPT,ABEND=sss-rc,DDN=dddddddd

ExplanationOSAM issued an OPEN, CLOSE, or EOV macrocall, and the DCB abend exit routine was enteredbecause of an abnormal condition. The abend canbe ignored, thus preventing the IMS region fromterminating abnormally. The requested function wasnot performed, and the data set are closed, if possible.


sss-rcThe system completion code (abend), and thesubcode that might accompany the abend (seez/OS MVS System Codes (SA22-7626) for adescription of the abend.)

ddddddddThe data definition name (ddname) of the data setencountering the error

System actionA nonzero return code is passed to the caller ofOSAM. Depending upon the function requested (OPEN,CLOSE, or EOV), the caller displays an additionalerror message, or can ignore the error and continueprocessing.

Programmer responseThe purpose of this message is to record the factthat an ignorable abend condition occurred. The abendmight be expected or permitted, for example, whileclosing a data set that has been renamed or deleted. Ifthe abend is the result of I/O errors while processingthe VTOC or writing a file mark to the data set, the typeof data set (database, IMS system data set, or log dataset) determines the recovery process to follow.


Module:DFSAOSF0

Related referencez/OS: System completion codes

DFS0696I COMMAND REJECTED, UNABLE TOGET STORAGE

ExplanationA command module tried to get storage with invalidparameters. The storage manager rejected the storagerequest. The command cannot be processed. Thisproblem is an internal error that requires action by thesystem programmer.




http://www-01.ibm.com/support/knowledgecenter/SSLTBW_2.4.0/com.ibm.zos.v2r4.ieah700/h7scc.htm?lang=en

System programmer responseIf the storage manager trace was active at the timeof the command failure, find the trace log recordassociated with the storage request failure.

If the storage manager trace was not active at thetime of the command failure, turn it on using the /TRACE SET ON TABLE STRG command. Reenter thecommand. If the command fails again, find the neededinformation in the associated storage manager tracelog record.

Module:DFSICA20, DFSICLI0, DFSICLM0, DFSICL60,DFSICL90, DFSICV40, DFSIC410, DFSIC460

DFS697I IMODULE FAILED REG15=xx INDFSDINB0 FOR EPLOC=yyyyyyyy

ExplanationAn IMODULE LOAD or an IMODULE GETMAINfailed during Database Control (DBCTL) subsysteminitialization (DFSDINB0). Register 15 contains thereturn code from the IMODULE routine (DFSMODU0).For the meaning of the return code, see theIMS system services return code information. Fieldyyyyyyyy is the location in DFSDINB0 where the erroroccurred.

System actionFor a DBCTL-only system, IMS issues abend 0718 forIMODULE LOAD failures and abend 0580 for IMODULEGETMAIN failures.

For an online DBCTL system, the online systemcontinues to run, and IMS informs the CoordinatorControl (CCTL) subsystem that DBCTL initializationfailed.

Programmer responseContact IBM Software Support for help in diagnosingthe problem.

Module:DFSDINB0

Related referenceIMS system services return codes (Messagesand Codes)Related informationIMS abend 0580IMS abend 0718

DFS0698W PROTECTED CONVERSATIONPROCESSING NOT ENABLED - RRSIS NOT AVAILABLE

ExplanationIMS attempted to initialize with the z/OS ResourceRecovery Services (RRS) in a z/OS system, but RRS isnot active.


User responseIf you want to use protected conversation processing,activate RRS. IMS and RRS automatically connectsand perform their coordinated restart. Protectedconversation processing will then be enabled.

Module:DFSRRSI0DFS0698W

PROTECTEDCONVERSATIONPROCESSINGNOT ENABLED -UNABLE TOBUILD VECTORTABLE OF RRMSSERVICES

ExplanationIMS could not buildits internal vector tableof RRMS services fromSYSQ.CSSLIB.

System actionProtected conversationprocessing is disabledfor the instance of IMSand restart processingcontinues.

User responseIf you want to useprotected conversationswith IMS, make surethat your SYSQ.CSSLIBcontains the RRMSservice stubs (CRG, CTX,and ATR modules). Thenrestart IMS.

Module:DFSRRSI0

DFS0698W

PROTECTEDCONVERSATION

PROCESSINGNOT ENABLED -UNABLE TOREGISTER AS ARESOURCEMANAGERRC=xxxxxxxx

ExplanationIMS could not registeras a resource managerwith RRMS RegistrationServices. The return codexxxxxxxx is from theCRGGRM service.

System actionProtected conversationprocessing is disabledfor this instance of IMS,and restart processingcontinues.

User responseIf you want to useprotected conversationprocessing, restart IMS.

Module:DFSRRSI0

Related referencez/OS: RegisterResource_Manager(CRGGRM,CRG4GRM)






http://www-01.ibm.com/support/knowledgecenter/SSLTBW_2.4.0/com.ibm.zos.v2r4.iean100/grm.htm?lang=en




DFS0698W

PROTECTEDCONVERSATIONPROCESSINGNOT ENABLEDDUE TO ABENDwxxxx REASONCODE=yyyyyyyyRRSRC=zzzzzzzz

ExplanationIMS abendedduring restartor resynchronizationprocessing with z/OSResource RecoveryServices.w

S (system abend) or U(user abend)

xxxxAbend code. A systemabend code is inhexadecimal and auser abend code is indecimal.

yyyyyyyyAbend reason code ifapplicable.

zzzzzzzzReturn code from RRSservice if applicable.

System actionProtected conversationprocessing is disabledfor this instance of IMS,and restart processingcontinues.

User responseIf you want to useprotected conversationprocessing, restart IMS.

Module:DFSRRSI0

DFS0698W

PROTECTEDCONVERSATIONPROCESSINGNOT ENABLED -NOTSUPPORTED IN

LSO=YENVIRONMENT

Explanationz/OS Resource RecoveryServices support cannotbe provided in alocal storage optionenvironment.

System actionProcessing continueswithout RRS.

User responseLSO=S must be specifiedif an RRS connection isdesired.

Module:DFSIRST0

DFS0698W

PROTECTEDCONVERSATIONPROCESSINGNOT ENABLED -OPERATORDECISION

ExplanationThe operator repliedCANCEL to the DFS0548Amessage.

System actionThe system continueswithout z/OS ResourceRecovery Services.


Module:DFSRRSI0

Relatedinformation“DFS0548A” onpage 192RRS NOT ACTIVEBUT RRS=YSPECIFIED -REPLY: RETRY,

CONTINUE ORCANCEL

DFS0698W

PROTECTEDCONVERSATIONPROCESSINGNOT ENABLED -PREVIOUSACTIVE IMSHAS NOTTERMINATED

ExplanationIMS attempted toset exits with z/OSResource RecoveryServices because RRS=Ywas specified. A returncode was receivedindicating that this IMSalready has exits set withRRS. This is the caseof a previous active orthe old XRF active notterminating.

System actionThe system highlightsthis message to indicatethe severity and willrepeatedly attempt to setexits asynchronously toother processing.

Operator responseEnsure the previousactive terminated, even ifmanual action is required.

Module:DFSRRSI0

DFS0698W

PROTECTEDCONVERSATIONPROCESSINGNOT ENABLED -PREVIOUS RRSSYSTEM HASNOTTERMINATED

ExplanationIMS received aATR_RESTART_WRONG_SYSTEM return code fromthe ATRIBRS (beginrestart) call, indicatingthat IMS is restarting onthe wrong system. This isthe case in which an IMSis being started onanother system or theXRF alternate isattempting to takeover.z/OS Resource RecoveryServices requires thatresource managersrestart on the samesystem as before if thereis work to be resolved,unless the RRS on theprevious system isinactive.

System actionIMS continues processingwithout RRS, butrepeatedly attempts to dothe restart with RRS.

Operator responseEnsure the previousactive terminated, even ifmanual action is required.

Module:DFSRRSI0

DFS0699I RESYNC (COMMIT|ABORT)COMPLETE FOR PSB xxxxxxxx,PRTKN=yyyyyyyy,TOKEN=zzzzzzzz, RRS-


URID=wwwwwwwwwwwwwwwwwwww

ExplanationA phase 2 COMMIT or ABORT process completed foran in-doubt unit of work (UOW) identified by pseudotoken yyyyyyyy and PSB xxxxxxxx. The IMS recoverytoken is zzzzzzzz. If the UOW was part of a protectedconversation, the z/OS Resource Recovery Services(RRS) unit of recovery interest token, wwwwwwww, isalso supplied.

Module:DFSDRID0

DFS700I INVALID CONTROL CARD FORMAT.SUBCODE=xxxx

ExplanationThe control statement printed before this messagecontains an error.

System actionThe control statement is ignored and standard defaultsare used.

Programmer responseThis is a user error. Correct the control statement andresubmit the job. See the following list of subcodesxxxx to determine the error.Code

Subcodes for messages0001

Control statement column 10 invalid.0002

SKIP keyword without value.0003

SKIP specified twice.0004

SKIP value too long.0005

SKIP value invalid.0006

STOPAFT keyword without value.0007

STOPAFT specified twice.

0008STOPAFT value out of range.

0009STOPAFT missing right parenthesis.

0010STOPAFT missing comma.

0011STOPAFT value too long.

0012STOPAFT value invalid.

0013DDNAME keyword without value.

0014DDNAME specified twice.

0015DDNAME value too long.

0016DDNOUT keyword without value.

0017DDNOUT specified twice.

0018DDNOUT value too long.

0019Invalid keyword in column 16.

0020Not used.

0021Not used.

0022Not used.

0023D= keyword without value.

0024K= keyword without value.

0025H= keyword without value.

0026O= keyword without value.

0027Not used.

Module:DFSERA10




DFS701I INVALID CARD TYPE.

ExplanationA statement did not contain CONTROL, OPTION, *, orEND in column 1.

System actionThe statement is printed and ignored. Processingcontinues.

Programmer responseCorrect the statement or remove it from the input data,and resubmit the job.

Module:DFSERA10

DFS702I INVALID OPTION CARD OR PRIORERROR. SUBCODE=xxxx

ExplanationThe OPTION statement identified in the message testby xxxx is in error, or a previous error caused thisstatement to be ignored.

Programmer responseCorrect the option statement and resubmit the job.See the following subcode listing to determine theerror.xxxx

Subcodes for messages0001

Keyword invalid in column 10.0002

Invalid keyword in option statement.0003

V= keyword without value.0004

VALUE= keyword without value.0005

SYM= & VALUE= keywords on the same option.0006

VALUE= specified twice.0007

VALUE= & without symbol name.

0008VALUE= &symbol, symbol name > 8.

0009FLDTYP keyword without value.

0010FLDTYP specified twice.

0011FLDTYP invalid.

0012COND= keyword specified twice.

0013COND= keyword without value.

0014COND=T without Y or N.

0015COND= blank or comma missing.

0016FLDLEN used with COND=T.

0017COND= value invalid.

0018FLDLEN keyword without value.

0019FLDLEN specified twice.

0020FLDLEN value too long.

0021FLDLEN value invalid.

0022FLDLEN value out of range.

0023OFFSET= keyword without value.

0024OFFSET= specified twice.

0025OFFSET= value too long.

0026OFFSET= value invalid.

0027OFFSET= value out of range.

0028Not used.

0029SYM= keyword without value.


0030SYM= first character not '&'.

0031SYM= specified twice.

0032SYM=& without symbol name.

0033SYM=&symbol, symbol name > 8.

0034STOPAFT= keyword without value.

0035STOPAFT= specified twice.

0036STOPAFT= value too long.

0037STOPAFT= value invalid.

0038STOPAFT= value out of range.

0039STARTAF= keyword without value.

0040STARTAF= specified twice.

0041STARTAF= value too long.

0042STARTAF= value invalid.

0043STARTAF= value out of range.

0044STOPAFT= used without COND=E.

0045STARTAF= used without COND=E.

0046C= value invalid.

0047EXITR= keyword without value.

0048EXITR= specified twice.

0049EXITR= value too long.

0050Not used.

0051Not used.

0052Not used.

0053Not used.

0054DDNAME= keyword without value.

0055DDNAME= specified twice.

0056DDNAME= value too long.

0057PRTSYS= keyword without value.

0058PRTSYS= specified twice.

0059PRTSYS= without option COPY.

0060PRTSYS= value invalid.

0061H= keyword without value.

0062B= keyword without value.

0063O= keyword without value.

0064L= keyword without value.

0065C= keyword without value.

0066T= keyword without value.

0067E= keyword without value.

0068Not used.

0069D= keyword without value.

0070P= keyword without value.

0071PARM parameter specified more than once.

0072No PARM parameter specified.

0073Format error in PARM list (missing leftparenthesis).

0074Format error in PARM list (length is less than 3).

0075Format error in PARM list (length is greater than258).

0076Format error in PARM list (missing rightparenthesis).

0077You specified FLDLEN or FLDTYP, but did notspecify VALUE.


Module:DFSERA10

DFS703I NORMAL END OF JOB.

ExplanationProgram has terminated without uncontrollable errors.Error messages might have been printed but no abendconditions occurred.

Programmer responseVerify that all options completed normally.

Module:DFSERA10

DFS704I NO OPTION CARDS SUPPLIED.

ExplanationThis message was issued for one of the followingreasons:

• The OPTION statements were omitted.• Errors caused all options to be ignored.

System actionA test sequence was ignored.

Programmer responseIf the OPTION statements were omitted, include theOPTION cards as needed.

Otherwise, correct errors as previously noted inSYSOUT printing.

Module:DFSERA10

DFS705I UNABLE TO OPEN INPUT FILE.

ExplanationThe OPEN for the data set associated with the lastcontrol statement failed.

System actionThe error message is printed and processing continueswith the next input statement.

Programmer responseVerify that the JCL is correct and the DCB parametersare supplied if the data set does not use a standardlabel, and rerun the job.

Module:

DFSERA10

DFS706I ELEMENT LIST ERROR.

ExplanationIf RC=04, DFSERA10 detected a duplicate symbol orthe symbol specified in the VALUE= option was notfound. You must specify a SYM= statement before theVALUE= statement that contains that symbol.

System actionProcessing terminates and the next test sequence isconstructed.

Programmer responseIf previous errors were printed, correct them and rerunthe job.

Problem determinationIf the error persists, see 2, 4, 36

Module:DFSERA10


DFS707I END OF FILE ON INPUT.

ExplanationThe input file reached an EOF. The current testsequence is ended.

Module:DFSERA10

DFS708I OPTION COMPLETE.

ExplanationThe current test sequence is ended.

System actionProcessing continues on the next sequence.

Module:DFSERA10

DFS709I UNABLE TO OPEN OUTPUT FILE.


ExplanationThe OPEN for the data set associated with the lastcontrol statement failed.

System actionThe error message is printed and processing continueswith the next statement.

Programmer responseVerify that the JCL is correct and the DCB parametersare supplied if the data set does not use a standardlabel, and rerun the job.

Module:DFSERA10

DFS710A UCF TERMINATING DUE TO STOPREQUEST

ExplanationWhile processing under the Utility Control Facility,the system operator requested a "stop-processing"or a control function contained an EXEC=STOP on itscontrol statement.

System actionProcessing stops, and return code 4 is passed to thenext step.

Programmer responseIf further processing is required, change the JCL toallow for Restart under the Utility Control Facility, andresubmit the job.

Problem determination1, 2, 8, 11, 36. Also, rerun the job with aFUNCTION=OP,MSGNUM=710 control statement inthe DFSYSIN data set. Supply a SYSUDUMP DDstatement to this step.

Module:DFSUCF00


DFS711W VERIFY FAILED FOR module/database csect/data set ONREQUEST nnnn FOR FUNCTION ff

ExplanationWhile processing a zap function (ff), a verification ofdata failed. The module and csect or database anddata set is identified.


Programmer responseCorrect the input control statement data, and resubmitthe job.


Module:DFSUCF00


DFS0712A xxxxx KEYWORD REPEATED-MAYBE SPECIFIED ONLY ONCE

ExplanationA keyword on the control statement to moduleDFSPIRP0 was specified more than once.

System actionThe control statement is scanned for further errors,and processing is terminated.

Programmer responseCorrect the control statement specifying a keywordonly once.

Module:DFSPIRP0

DFS0713A DATE INVALID

ExplanationAn invalid DATE parameter was specified. Possiblecauses are:

• The date was not in the form MM/DD, where MM isone or two numeric characters from 1 through 12


and DD is one or two numeric characters from 1through 31.

• The date (DD) specified is too large for thecorresponding month (MM).

System actionThe program is terminated.

Programmer responseCorrect the DATE parameter in the DFSPIRP0 controlstatement.

Module:DFSPIRP0

DFS0714A xxxxx PARAMETER DOES NOT ENDWITH COMMA OR SPACE

ExplanationA parameter on the control statement to moduleDFSPIRP0 did not end with a comma or space.


Programmer responseCorrect the control statement.

Module:DFSPIRP0

DFS0715A STOP TIME SPECIFIED PRECEDESSTART OF TRACING

ExplanationThe DATE operand on the control statement to moduleDFSPIRP0 specified a date prior to the start of PItracing. The hours and minutes (HHMM) specifiedfor the STOP parameter, combined with the datespecified, was before 00:00:00 on the date tracingstarted. This message is issued after the controlstatement scan has been completed.


Programmer responseCorrect the control statement omitting the DATEoperand or the STOP parameter, or specify them suchthat the stop time is after PI tracing was started.

Module:

DFSPIRP0

DFS0716A PRINT MUST BE SPECIFIEDBEFORE ANY KEYWORDS

ExplanationA keyword other than PRINT was specified first on thecontrol statement to module DFSPIRP0.

System actionThe control statement is scanned for further errors andprocessing is terminated.

Programmer responseCorrect the control statement specifying PRINT as thefirst keyword.

Module:DFSPIRP0

DFS0717A STOP TIME SPECIFIED PRECEDESSTART TIME SPECIFIED

ExplanationThe STOP parameter was earlier than the STARTparameter. This message is issued after the controlstatement scan has been completed.


Programmer responseCorrect the control statement specifying a stop timelater than the start time.

Module:DFSPIRP0

DFS0718W BLANK OR NO CONTROL CARDSPECIFIED-IGNORED

ExplanationA SYSIN DD statement was included but the input dataset contained a blank line or the data set was empty(no records).

System actionThe report includes records from the beginning tothe end of the log data set. The control statementprocessing is bypassed.


Programmer responseIf a time period was wanted, provide a valid controlstatement. If no control statement is required, theSYSIN DD statement should be omitted.

Module:DFSPIRP0

DFS0719I X'4006' CHECKPOINT RECORDNOT FOUND ON THE INPUT LOG

ExplanationAn X'4006' checkpoint log record must be processedbefore any PI trace log records. No report wasgenerated because an X'4006' log record was notfound. X'4006' log record can be lost when specifyingonly part of the log data set on the LOGTAPE DDstatement.

System actionThe IMS Program Isolation Trace Report utility,DFSPIRP0, is terminated.

Programmer responseSpecify the correct SLDSs, including all volumes incorrect sequence, on the LOGTAPE DD statement.


Module:DFSPIRP0


DFS0720A xxxxx TIME INVALID

ExplanationThe start or stop time was not specified in two numericcharacters from 00 through 99 for hours, and in twonumeric characters from 00 through 59 for minutes.

System actionThe control statement is scanned for further errors,and processing is terminated.

Programmer responseCorrect the start or stop time on the control statement.

Module:DFSPIRP0

DFS0721A INVALID KEYWORD IN DFSPIRP0CONTROL CARD

ExplanationThe control statement to module DFSPIRP0 containedan operand other than PRINT=, START=, STOP=, orDATE=.



Module:DFSPIRP0

DFS0722I NO TRANSACTION HAD TO WAITFOR AN ENQUEUE DURING THETIME PERIOD

ExplanationNo transaction had to wait for an enqueue during thetime period and no report was generated.

System actionThe program reaches normal completion.

Programmer responseThis might be a normal condition. If a controlstatement was included, ensure that the time periodwas correct.

Module:DFSPIRP0

DFS0723A REGION SIZE TOO SMALL FORPROGRAM DFSPIRP0

ExplanationThe region size specified for program DFSPIRP0 wasnot large enough to contain the common work area,input log buffer, and data management block list.


Programmer responseIncrease the region size, and resubmit the job.

Module:


DFSPIRP0

DFS0724A NO TRACE RECORDS ON LOGDATASET FOR THE TIME PERIOD

ExplanationNo program isolation (PI) trace log records were foundon the log data set during the specified time period.This problem occurred because:

• PI tracing was not in effect during the time period.• The IMS system was dormant during the period and

no activity occurred which required tracing.• The time period specified on the control statement

for the IMS program isolation trace report utility didnot overlap the time period corresponding to the logdata set provided by the log DD statement.

System actionNo report is generated and the program completesnormally.

Programmer responseEnsure that the time period specified on the controlstatement corresponds to the log data set provided.Check the console records to determine if PI tracingwas active during the time period. If PI tracing wasactive check to see if the system was dormant.


Module:DFSPIRP0


DFS0725I INITIATE|UPDATE|TERMINATEOLREORG COMMAND FOR DBdbnamexx COMPLETE. CC= nn

ExplanationThe /INITIATE, /UPDATE, or /TERMINATE OLREORGcommand processing is complete.


dbnamexxis the HALDB partition name entered in thecommand

nnis the completion code

A zero completion code indicates that the commandhas been successfully processed. Message DFS2970Iis issued after OLR initialization completes toindicate that the HALDB OLR has started. A nonzerocompletion code indicates that an unexpected errorwas encountered during command processing.

Completion codeMeaning

0REQUEST SUCCESSFUL

10RESOURCE NAME INVALID

14RESOURCE NOT A PARTITION NAME

1CRESOURCE IS A PARTITION SECONDARY INDEX

20INIT OLREORG ISSUED, OLR IS ALREADY INPROGRESS

24NO OLREORG IS IN PROGRESS

28NO DMB LOADED - need to schedule a PSB thatreferences the DB

AEDYNAMIC ALLOCATION ERROR

C1OLREORG DDIR MISSING

C3OLREORG PARTITION STOPPED, or LOCKED, orDBDUMPED

C4OLREORG PARTITION BEING RECOVERED

C5OLREORG PARTITION ACCESS NOT UPDATE/EXCLUSIVE

C6OLREORG SCHEDULING FAILED - A failure to buildrequired blocks/PSB or partition selection failureoccurred.

C7OLREORG PARTITION NOT AUTHORIZED - CheckHALDB Master status

C8OLREORG MASTER STOPPED, or LOCKED, orDBDUMPED

C9OLREORG MASTER ACCESS NOT UPDATE orEXCLUSIVE

CAOLREORG SET OWNERSHIP FAILED


CBPARTITION NOT IN SPECIFIED STATUS

CCOLR already active for the partition

CEHALDB OLR cannot access all the data in thepartition because an EEQE exists.

DADATABASE BEING RECALLED FROM HSM



Module:DFSORC10, DFSORP50

Related information“DFS2970I” on page 814OLR STARTED | RESUMED FORNAME=partname MASTER=masternamePST=pstnumber“IMS problem determination” on page 11IMS messages and codes problemdetermination is accomplished by usingprocedures established by IBM.

DFS0726A CONTROL CARD ERROR-PROCESSING TERMINATED

ExplanationThe control statement to module DFSPIRP0 containedone or more errors as indicated by previous messages,or data was entered past position 71 on the controlstatement.



Module:DFSPIRP0

DFS0727A DATE/TIME SPECIFIED NOTWITHIN 12 DAYS OF DATE PITRACE STARTED


• The DATE operand specified a date that was morethan 12 days before or after the date PI tracing wasstarted.

• The combination of the START and DATE operandsresulted in a start time greater than 12 days from thedate PI tracing started.


Programmer responseCorrect the control statement specifying a valid date orstarting time.

Module:DFSPIRP0

DFS0728W DATE SPECIFIED PRECEDES DATETRACING STARTED

ExplanationThe date specified was before the date PI tracingstarted. If IMS was active for more than one day, PItracing might have begun after the first day that IMSwas started.


Programmer responseDetermine if the date specified was as intended.

Module:DFSPIRP0

DFS0729I UNABLE TO OBTAIN WORKAREA FOR DL/I OPEN/CLOSEPROCESSING

ExplanationWhen attempting to open or close a DL/I database, itwas found that main storage space for the work arearequired for OPEN/CLOSE processing was unavailable.

System actionProcessing of the DL/I call is terminated and a statuscode of AI is returned in the PCB. In addition, theerror code from the IMODULE routine is stored inPSTRTCDE.


Programmer responseProvide a larger address space for the step so that thework area can be obtained.

Problem determination:1, 2, 3, 17b, 36

Module:DFSDLOC0


DFS0730I UNABLE TO OPEN OR CLOSEDATASET WITH DDNAME ddnameFOR REASON x, yy, z DATABASEdbdname programid

ExplanationAn error occurred when IMS tried to open or closea database. ddname is the DD statement name ofthe data set on which the error occurred. x, yyrepresents the major and minor reason codes. Thedata set ddname is a part of the DBD dbdname. Ifan error occurred when IMS tried to open a database,programid is included in the message. When ascheduler message block (SMB) is present, programidrepresents the transaction code (TRN). When an SMBis not present, programid represents the PSB name.

The following information provides the explanation,programmer response, and problem determinationcodes for the various major and minor reason codes:

CodesExplanation

A,yyAn attempt was made to open an OSAM dataset. The OSAM OPEN routine returned an errorindication. yy is the hexadecimal error code thatis returned in register 15.Code (hex)

Meaning00

The normal condition.04

The DCB is already being opened or closed.08

The DCB is already open.0C

The DECBTYPE is invalid.

10

A failure in the IMS SVC occurred. DCBWRK1indicates the reason.

z Value (hex)Meaning

01Internal error, Media Manager call failure.

02Internal error, caller’s MMCLP invalid.

03Internal error, DCB already open.

04Internal error, not OSAM OPEN.

05Already open as DUMMY.

06DCB had earlier problem.

07Internal error, caller did not pass DD name.

08

Internal error; caller passed zero for anMMP address.

Programmer response: Call IBM SoftwareSupport.

14An I/O error occurred while the OSAMOPEN routine was scanning for a file mark,formatting, or writing a file mark. SeeDECBSTAT for additional information.

18An invalid RBN was calculated. The RBN iseither 0 or is greater than the maximum RBNfor the data set.

1CAn error occurred during TCLOSE processingfor the data set. DCBWRK1 indicates thereason.

20An error occurred while acquiring storage thatuses IMODULE.

24An error occurred during EOV processing forthe data set.

28OSAMOP IOSCB=NO was specified in a controlstatement data set. This value caused BATCHinitialization to bypass the allocation of OSAMI/O blocks and prevented the use of the OSAMaccess method.


z is the hexadecimal error subcode returned atthe last byte (byte number 4) in the field nameDCBWRK1 by module DFSAOSF0. This subfieldof the message is used only for a message thatcontains reason code A,10.z Value (hex)

Meaning01

The DD statement is missing, or fordynamically allocated data sets, the data setis not yet allocated.

02The data set is a concatenated data set.

03Fewer units than volumes were specified for aDASD data set.

04JCL specified a DSORG type not permitted byOSAM.

05The DSCB for the data set was not found.

06First volume DSCB specified a DSORG type notpermitted by OSAM.

07DCB block size not equal to DSCB block sizeafter Job File Control Block/DCB merge.

08DCB LRECL size not equal to DSCB LRECL sizeafter Job File Control Block or Data ControlBlock (DCB) merge.

09Neither the LRECL nor block size was specifiedin the DSCB, DCB, or JCL.

0AThe specified block size is less than LRECL.

0BThe specified block size exceeds the track sizefor the specified device.

0CA previous OPEN or EOV failed.

0DVIO not supported by OSAM. The data set isallocated to a VIO unit.

0ETape devices are not supported. The data set isallocated to a tape device.

0FAn internal error occurred in the OSAM DEBsubroutine. DCBWRK1 indicates the errorcode:

01The block size is greater than the track size.

02The DEB length is greater than themaximum allowed. There are too manyextents. This situation might be the resultof a DFS0842I message REASON=5 issuedearlier by the same or a different job.

10IEFDDSRV failed to perform the function.

11Inconsistent number of allocated devices.

12The reread of the job file control block (JFCB)failed.

13User description area (UDA) SSI interface error.

14DCM is already open as a DD dummy.

15This is not OSAM open calling.

16DCB is already open by MVS.

17Invalid parameter.

18Error reading the job file control block (JFCB).

19Open failure with no abend.

1AError obtaining DSCB on the first volume of theOSAM data set.

1BError constructing extends for all of thevolumes of the OSAM data set. Return codefrom OSAMDEB subroutine is 8 in register 15.

1CError locating or loading the OSAM I/Oroutines.

1DError releasing a captured UCB.

1EBad conversion from the current volume DSCBTTR to the disk address MCCHHR.

99The DCB abend exit was entered. MessageDFS0695I is also displayed. See that messagefor an explanation of the error.

Programmer response: Correct the JCL error byusing the major and minor reason codes given.


B,10The IDAXVIM FUNC=CALLXVI call to invalidate thebuffer received a nonzero return code (RC). Themajor RC is X'04' and the minor RC is X'10'. Thismeans the call was illegal , and it failed to releaseownership.xx

Return code from IDAXVIM.08

No room in the user's AREA.12

VSAM structure error.

Operator response: No action is required.

System programmer response: Save thediagnostic information. Contact IBM SoftwareSupport for assistance.

B,40A coupling facility (CF) environmental erroroccurred.

Programmer response: Determine the exact errorby using the IMS DFSERA10 utility and selectingthe X'67FD' record from the IMS log. This recordincludes the REQUEST=IXLCACHE macro with areason code, RSNC=xxxxxxxx. The last 4 digitsof the number string xxxxxxxx represent the trueerror code. For example, if the reason code isRSNC=0C170C19, look up reason code 0C19.See the z/OS MVS Programming: Sysplex ServicesReference for reason code descriptions.

B,yyDL/I OPEN/CLOSE called the DL/I buffer handlerfor buffering services. The buffer handler returnedwith an error indicator. yy is the hexadecimal valuethat was returned in PSTRTCDE by the bufferhandler.

Programmer response: For information on bufferhandler return codes, see the IMS return andfunction codes information.

C,yyAn error was detected by VSAM CLOSE. yy is thehexadecimal error field from the VSAM ACB.

Programmer response: See an explanation ofVSAM CLOSE error codes.

E,yyDL/I OPEN/CLOSE issued a VSAM ERASE macroand encountered an error condition returned fromVSAM. If a physical (I/O) error occurred, messageDFS0731I or DFS0451I was issued indicating thenature of the error, and yy is the hexadecimal valuereturned by VSAM in register 15; otherwise, yyis the hexadecimal logical error code returned byVSAM.

Programmer response: See an explanation ofVSAM logical and physical error return codes.

G,yyDL/I OPEN/CLOSE issued a VSAM GET macroand encountered an error condition returned fromVSAM. If a physical (I/O) error occurred, messageDFS0731I or DFS0451I was issued indicating thenature of the error, and yy is the hexadecimal valuereturned by VSAM in register 15; otherwise, yyis the hexadecimal logical error code returned byVSAM.


I,01The relative key position from the DBD is not thesame as the relative key position that was definedto VSAM.

Programmer response: Correct the relative keyposition specified to VSAM. The correct relativekey position to be defined for VSAM is provided inthe output listing from DBD generation.

I,02The key length from the DBD is not the same as thekey length that was defined to VSAM.

Programmer response: Correct the key lengthspecified to VSAM. The correct key length to bedefined for VSAM is provided in the output listingfrom DBD generation.

I,03The record size or block size for OSAM databasepartitions for the data set being opened is notlarge enough to contain the longest segment in thedatabase plus the IMS overhead required.

Programmer response: Correct the record sizespecified to VSAM. For OSAM database partitions,correct the block size. The correct record size todefine for VSAM is provided in the output listingfrom DBD generation.

I,04The record size for the HD VSAM ESDS beingopened was not defined to VSAM as 7 bytes lessthan the CI size. The record size for an HD VSAMESDS data set must be 7 bytes less than the CIsize.

Programmer response: Redefine the VSAM dataset so that record size is 7 bytes less than the CIsize.

I,05The record size of an HS VSAM KSDS or ESDSbeing opened for load is not a multiple of two. Therecord size for VSAM HS data sets must be an evennumber.


Programmer response: Correct the record sizespecified to VSAM.

I,06Upon opening an HSAM VSAM data set, the blocksize was found to be less than the LRECL. Theblock size must be equal to or greater than theLRECL.

Programmer response: Correct the block sizespecified to VSAM.

I,07An HS VSAM database is defined with the ESDSrecord size shorter than the KSDS record size.

Programmer response: Change the VSAMdefinition so that the ESDS record size is equal toor greater than the KSDS record size.

I,08An attempt was made to open a VSAM data setfor which there was no DD statement, or fordynamically allocated data sets, the data set is notyet allocated. The message indicates the ddnameassociated with the data set that was opened.

Programmer response: Check the JCL and DBDfor the job to determine the DD statementrequirements.

System operator response: Use an UPDATE DBSTART(ACCESS) or /START DB command tocause allocation retry.

I,09An attempt was made to open a VSAM or OSAMDCB and the ddname was already in the opentable. This indicates that the data set is currentlyopened under a data management block and anattempt was made to open it under a second datamanagement block, which was caused by havingtwo DBDs referring to the same ddname. TwoDBDs cannot reference the same ddname.

Programmer response: Find the two DBDs thatreference the same ddname and delete one.Change the PSB to reference the correct DBD; thenrun the PSB generation utility.

I,10An attempt was made to open a VSAM ACB andthe ddname was already in the open table. Thisindicates that the data set is currently open undera data management block and an attempt wasmade to open it under a second data managementblock, which was caused by having two DBDsreferring to the same ddname. Two DBDs cannotreference the same ddname.

Programmer response: Find the two DBDs thatreference the same ddname and eliminate one.

Change the PSB to reference the correct DBD, andthen run the PSB generation utility.

I,11An attempt was made to open an ISAM DCB oran OSAM DCB associated with an ISAM DCB. IMSdoes not support combinations that include ISAM.

This code can also be issued during loadprocessing for an HSAM database, because thecurrent DCB is missing a DCBE.

Programmer response: Convert HISAM or theindex database of a HIDAM structure to the VSAMorganization, which is supported.

I,12An attempt was made to open a VSAM ACB in thespecified VSAM shared resource pool. No subpoolwithin the shared resource pool was large enough.IMS tries to open the VSAM ACB again, using thedefault VSAM shared resource pool.

Programmer response: Check the VSRBF subpooldefinition statements for the VSAM sharedresource pool for this data set. Define subpoolbuffer sizes big enough for this data set and forthe KSDS index.

I,13The system was unable to satisfy a GETMAINrequest for an additional ddname open table. Thiserror occurred during the opening of a DCB.

Programmer response: Provide a larger addressspace for this step.

I,14The system was unable to satisfy a GETMAINrequest for an additional ddname open table. Thiserror occurred during the opening of an ACB.


I,15An error was detected during OPEN processing ofan HSAM or OSAM data set. The data set was notallocated at the time IMS tried to obtain DBRCauthorization for the database. See return codeI,16 for a complete description of the error.

Programmer response: If there is an incorrectdynamic allocation of the data set, or anincompatible allocation program or product, usethe /DBR command to unallocate the database.Correct the dynamic allocation specification, or theprogram or product, and then enter an UPDATE DBSTART(ACCESS) or /START for the database.

I,16An error was detected during OPEN processing ofa VSAM data set. The data set was not allocated atthe time IMS tried to obtain DBRC authorization


for the database. Later, when the data set wasopened, it was allocated. This can happen for oneof the following reasons:

• The dynamic allocation specifications forthe data set are incorrect. The DFSMDATYPE=DATASET statement for the data set wasincluded within the DFSMDA TYPE=DATABASEstatement for a different database. For example,the DFSMDA TYPE=DATASET statement for theindex of a HIDAM database is included withinthe DFSMDA TYPE=DATABASE statement for thedata part of the HIDAM database.

• The dynamic allocation specifications for thedata set are incorrect. Preceding messageDFS2499W indicates an invalid allocate requestfor the database. For example, the MDA memberfor the database specifies two data sets. The JCLincludes DD statements for one of the data sets,but not all of the data sets included in the MDAmember.

• The allocation was performed by anincompatible allocation program or product,which allocated the database after theauthorization for the database, but before theopen of the database.

Programmer response: If the error was caused byincorrect dynamic allocation of the data set:

1. Enter a /DBR command to deallocate thedatabase.

2. Correct the dynamic allocation specification.3. Enter an UPDATE DB START(ACCESS) or /START for the database.

If the error was caused by an incompatibleallocation program or product:

1. Enter a /DBR command to deallocate thedatabase.

2. Correct the program or product.3. Enter an UPDATE DB START(ACCESS) or /START for the database.

I,20The system is not able to satisfy a GETMAINrequest for the record size of the KSDS beingopened for sequential mode.


I,21The system is not able to satisfy the GETMAINrequest for the block size of an HSAM database.


I,22The system is not able to satisfy a GETMAINrequest for the control interval size to use to writethe first CI of the ESDS data set being opened forload processing.


I,23The system is not able to satisfy a GETMAINrequest for the record size of the ESDS data setbeing opened. The area is used to format thecurrent CA when the end RBA for the data set isnot on a CA boundary.


I,25The system is not able to satisfy a GETMAINrequest for the record size of KSDS to be used for atemporary work buffer.


I,26The system is not able to satisfy a GETMAINrequest for an area to contain the ddnames ofall the data sets contained in the database. Atemporary work area to build the list of ddnamesis required during open-for-update processing of adatabase that is registered to DBRC.


I,30An attempt was made to open a VSAM data setassociated with a PCB that has processing option Land the data set is not empty.

Programmer response: If the old data set is to bescratched, delete it using the VSAM AMS program.If the data set is not to be scratched, use a PCBwith processing option other than L.

I, 31An attempt was made to open a VSAM data setassociated with a PCB, which has a processingoption other than L, and the data set is empty.

Programmer response: Use a PCB with processingoption L to perform the initial loading of adatabase. When developing the JCL, use thefollowing procedure:

1. Delete or define KSDS data set.2. Run a DFSPRECO job to rebuild the indirect list

entry (ILE) and the Primary Index data set.


Note: If you cancel the job while in “2” on page261, rerun the entire job starting from “1” on page261. Do not restart in “2” on page 261.

I,32During an attempt to open a VSAM KSDS data set,it was determined that the total length of the indexVSI plus the data VSI plus the size of the IMS NCBwas greater than decimal 255 (including the lengthfield). This value is passed to IRLM during a notifyas the length of the message area, and must beless than decimal 256 (including the length field)due to an IRLM restriction.

Programmer response: Check the define clusterfor key ranges. Each key range increases the sizeof the index VSI by decimal 32 bytes. IMS does notuse or support VSAM key ranges.

I,33DL/I open processing determined that sharedaccess is allowed for the data set but theSHR options specified on the Access MethodServices DEFINE are not appropriate for datasharing. Message DFS050A was issued. For furtherdescription of the failure, see message DFS050A.

Programmer response: See message DFS050A.

I,34During an attempt to open a VSAM KSDS data set,either the index component or the data componentwas not opened.

Programmer response: Verify that the data setname specified for the DD statement being openedis the data set name for the VSAM cluster, ratherthan the data set name of one of the componentsof the cluster.

I,35During open-for-update processing of thedatabase, it was determined that not all the datasets contained in the database are registered toDBRC. Message DFS0484A was issued listing thedata sets that are not registered.

Programmer response: See message DFS0484A.

I,36During an attempt to open a VSAM KSDS data set,it was determined that the KSDS is an SMS data setwith the EXTENDED ADDRESSABILITY attribute,which IMS does not support. If the data set isdefined in JCL as DD DUMMY, the test for ExtendedAddressability cannot be completed and will causethis subcode.

Programmer response: The data set wasallocated using a data class that specifiedEXTENDED ADDRESSABILITY, which is not allowedfor data sets that IMS uses. The data set must be

allocated with a data class that does not specifyEXTENDED ADDRESSABILITY.

In the case of DD DUMMY, correct the data setname or remove it as appropriate, and then runthe job again to allow Extended Addressabilitychecking to proceed.

I,37During an attempt to open a VSAM ESDS data set,it was determined that the ESDS is an SMS data setwith the EXTENDED ADDRESSABILITY attribute,which IMS does not support. If the data set isdefined in JCL as DD DUMMY, the test for ExtendedAddressability cannot be completed and will causethis subcode.

Programmer response: The data set wasallocated using a data class that specifiedEXTENDED ADDRESSABILITY, which is not allowedfor data sets that IMS uses. The data set must beallocated with a data class that does not specifyEXTENDED ADDRESSABILITY.

In the case of DD DUMMY, correct the data setname or remove it as appropriate, and then runthe job again to allow Extended Addressabilitychecking to proceed.

I,38During an attempt to open a VSAM data set, it wasdetermined that the data set is an SMS extendedformat data set with the COMPACTION attribute,which IMS does not support.

Programmer response: The data set wasallocated by using a data class that specified theCOMPACTION attribute, which is not allowed fordata sets that IMS uses. The data set must beallocated with a data class that does not specifyCOMPACTION.

I,47

During an attempt to open a VSAM data set, itwas determined that the data set was cached byHiperbatch. IMS does not support Hiperbatch.

Programmer response: A data set must have aRACF DLFCLASS profile for it to be eligible to becached by Hiperbatch. Remove the data set fromthe DLFCLASS or use a different data set name.

I,50One of the following errors occurred:

• No VSAM buffer subpool has buffers largeenough to contain the control intervalsassociated with the data set being opened.

• A DFSVSAMP DD statement is missing.• No OSAM buffer pool has buffers large enough to

contain the associated blocks.


Programmer response: Rerun the step, but thistime specify a buffer subpool large enough tocontain the control interval blocks.

I,51IMS retains the RBA of the last used record in anESDS in the first CI of that data set. During DL/IOPEN, it was found that this RBA did not fall in thelast CI of the data set.

I,52The IMODULE facility of IMS failed while loadingor deleting the randomizing routine, the SecondaryIndex Database Maintenance exit routine, or theSegment edit/compression exit routines.

Programmer response: Message DFS0733I wasissued indicating the cause of the failure. Seemessage DFS0733I.

I,53An HSAM data set failed to open.

Programmer response: See the explanation forthe AI status code in DL/I status code informationfor possible reasons for the failure.

I,54An HSAM data set failed to open.

Programmer response: See the explanation forthe AI status code in DL/I status code informationfor possible reasons for the failure.

Save a VTOC listing of the volume in question forproblem determination.

I,55An attempt was made to open a data set thatpreviously failed during VERIFY. The data set couldnot be opened or closed.

I,56An attempt was made to OPEN an HSAM database.The DCB BLKSIZE for the data set was notprovided by either the JCL or the label on thevolume; as a result, the block size is 0.

Programmer response: Ensure that the JCL for thejob is correct and that the database is loaded.

Save a VTOC listing of the volume in question forproblem determination.

I,57,ZAfter the VSAM open and verify was done fora HISAM or non-unique secondary index ESDSdata set, the end of the data set was adjustedbecause Extended Error Queue Element blocks(EEQEs) were present. VSAM SVC 109 was issuedto inform VSAM so that VSAM could adjust the VSIinformation. The SVC returned a nonzero returncode in register 15. Subcode Z in the message is

the hexadecimal error subcode returned in register15.

CodesExplanation

I,58An initialization error was detected by a SegmentEdit/Compression exit routine.

Programmer response: Message DFS0749Iwasissued indicating the cause of the failure. Seemessage DFS0749I.

CodesExplanation

I,60A VSAM data set has a CI size which exceedsthe maximum CI size supported by DL/I which is30720.

Programmer response: Redo the AMS defineusing a CI size equal to or less than 30720.

I,61During an attempt to open a VSAM or OSAM dataset, a lock could not be acquired.

To determine the problem, see abend 3303.

I,62The relative key position in the indirect list data set(ILDS) is not zero.

Programmer response: Define the relative keyposition as ZERO in the VSAM cluster definition forthe indirect list data set (ILDS).

I,63The record length in the indirect list data set (ILDS)is not correct.

Programmer response: Define the record lengthas 50 in the VSAM cluster definition for the indirectlist data set (ILDS).

I,64The key length in the indirect list data set (ILDS) isnot correct.

Programmer response: Define the key length as 9in the VSAM cluster definition for the indirect listdata set (ILDS).

I,65The partition ID within the data set does not matchthe partition ID being opened.

Programmer response: Correct the name of thedata set so that it matches the partition ID.

I,66An ACBGEN of the PSB has not been performedsince the database was changed to Partitioned.


Programmer response: Perform the appropriateACBGEN. STATUSAI is returned to the application;use this to look up which PSB the application isusing and which ACB that PSB is generated in. Youcan also look at the job's JCL to determine whichACB library it's running against.

I,67Free space has been defined on a data clusterof an ESDS database. An ESDS database is notallowed to have free space defined.

Programmer response: Remove the free spacefrom the data cluster definition.

I,68An error was detected during initial OLR processingwhen the first CI of a VSAM output data set wasbeing formatted.

Programmer response: Scratch and reallocate theoutput data set.

I,70An invalid index has been defined on an INDICESparameter of a SENSEG statement of a PCB duringPSB generation.

Programmer response: Correct the INDEX namespecified on the INDICES parameter of theSENSEG statement of the PCB in question.

I,71

An error was detected during close processing ofan OSAM data set. An I/O error was encountered.Subcode z in the message is the hexadecimal errorsubcode returned at the last byte (byte number 4)in the field name DCBWRK1 by module DFSAOSF0.

For OSAM using linear data sets, subcodes fromDFSAOSFM have a different meaning. See the setof subcodes for the Z value for OSAM using lineardata sets.

Z value(hex)Meaning

01An error occurred while processing closingvolume extents. Return code from OSPLITsubroutine is 4 in register 15.

02An error occurred while converting OSAM DataExtension Block (DEB) to MVS DEB. Returncode from OSDEB subroutine is 4 in register15.

03DCB is already closing.

04DEB/DCB validation check failed.

05An error occurred while processing closingvolume extents. Return code from OSPLITsubroutine is 8 in register 15.

06An error occurred while converting OSAM DataExtension Block (DEB) to MVS DEB. Returncode from OSDEB subroutine is 8 in register15.

07Error releasing DCB extension area.

99The DCB abend exit was entered. MessageDFS0695I is also displayed. See that messagefor an explanation of the error.

Programmer response: Check the messages thatpreceded the I/O error, likely DFS0762I andDFS0451I. Correct the failure.

I,72An error was detected during close processing ofan OSAM data set. An I/O error was encountered.

Programmer response: Check the messages thatpreceded the I/O error, likely DFS0762I andDFS0451I. Then, correct the failure.

O,yyVSAM OPEN detected an error. yy is thehexadecimal error field from the VSAM ACB.

Programmer response: If yy is DC and thedatabase is organized as VSAM KSDS, run theLISTCAT command to get a report from theVSAM catalog. Review the CISIZE of the indexcomponent data set with the installation bufferpools defined in the DFSVSAMP data set forbatch jobs, or in the DFSVSMxx member foronline system. Verify that the CI specified in theinstallation is at least as large as the CISIZE fromthe LISTCAT.

See an explanation of VSAM OPEN error codes.

P,yyDL/I OPEN/CLOSE issued a VSAM PUT macroand encountered an error condition returned fromVSAM. If a physical (I/O) error occurred, messageDFS0731I or DFS0451I was issued indicating thenature of the error, and yy is the hexadecimal valuereturned by VSAM in register 15; otherwise, yyis the hexadecimal logical error code returned byVSAM.


R,01The database, dbdname, could not be openedbecause the installation's security product did not


allow IMS to access the VSAM data set for ddnameat the required level. The specific cause or theerror is described in the message DFS0735I-R01for the dbdname and ddname.

Programmer response: See message DFS0735Ifor problem determination.

R,02The database, dbdname, could not be openedbecause IMS was unable to access the data setassociation block (DSAB) for ddname. The specificcause or the error is described in the messageDFS0735I-R02 for the dbdname and ddname.


R,03The database, dbdname, could not be openedbecause DFP Catalog Management encounteredan error accessing the catalog for the VSAM dataset. The specific cause or the error is described inthe message DFS0735I-R03 for the dbdname andddname.


S,yyDL/I OPEN/CLOSE issued a VSAM SHOWCB macroand was returned a nonzero return code indicatingan error condition. yy is the hexadecimal valuereturned by VSAM in register 0 indicating thenature of the error.


V,yyDL/I OPEN/CLOSE issued a VSAM VERIFY macroand encountered an error condition returned fromVSAM. If a physical (I/O) error occurred, messageDFS0731I or DFS0451I was issued indicating thenature of the error, and yy is the hexadecimal valuereturned by VSAM in register 15; otherwise, yyis the hexadecimal logical error code returned byVSAM.


System actionIMS issues the error message.

Processing of the DL/I call is terminated and a statuscode of AI is returned in the PCB. In addition, theddname from the message is stored in the segmentname.

Operator response:Contact your system programmer for assistance.

Problem determination:1, 3, 8, 17b, 17d, 18, 20, 36

Module:DFSDLOC0

Related conceptsIMS buffer pools (System Definition)Related referenceIMS return and function codes (Messages andCodes)DL/I status codes (Messages and Codes)z/OS: RPLERRCD reason codesz/OS: CLOSE return and reason codesRelated information“DFS050A” on page 39SHARED ACCESS TO VSAM DATASET ddnameNOT ALLOWED BY CATALOG“DFS0451I” on page 159modname, dbdname, ddname, i/o error, decbfield“DFS0484A” on page 168THE FOLLOWING DATASETS FOR DATA BASEdbdname ARE NOT REGISTERED TO DBRC:ddname1 . . . . ddnamen“DFS0695I” on page 245OSAM (OPEN|CLOSE|EOV)INTERCEPT,ABEND=sss-rc, DDN=dddddddd“DFS0733I” on page 266IMODULE ERROR xx {LOADING | DELETING}{RANDOMIZING | INDEX EXIT | COMPRESSIONEXIT} MODULE moduname“DFS0735I” on page 267SAF ACCESS FAILED-Rnn dbdname-ddnameRETURN CODE=nnn. REASON CODE=nnnn.module-name.“DFS0749I” on page 274COMPRESSION EXIT ROUTINE nnnnnnnnINITIALIZATION ERROR - Uaaaa REASONrrrrrrrr“DFS0762I” on page 280OSAM (TAPE | DASD) (READ | WRITE) ERROR -FUNC=aa STATUS=bb, cc, dddd, eeee, ffffIMS abend 3303AI (Messages and Codes)“IMS problem determination” on page 11IMS messages and codes problemdetermination is accomplished by usingprocedures established by IBM.

DFS0731I (A VSAM physical error messagestarting with VSAM message byte26.)


http://www.ibm.com/support/knowledgecenter/SSEPH2_15.1.0/com.ibm.ims15.doc.sdg/ims_i2hsbsz.htm#i2hsbsz

http://www.ibm.com/support/knowledgecenter/SSEPH2_15.1.0/com.ibm.ims15.doc.msgs/compcodes/ims_imsretandfunccodes.htm#ims_imsretandfunccodes

http://www.ibm.com/support/knowledgecenter/SSEPH2_15.1.0/com.ibm.ims15.doc.msgs/compcodes/ims_imsretandfunccodes.htm#ims_imsretandfunccodes


http://www-01.ibm.com/support/knowledgecenter/SSLTBW_2.4.0/com.ibm.zos.v2r4.idad500/rplerr.htm?lang=en

http://www-01.ibm.com/support/knowledgecenter/SSLTBW_2.4.0/com.ibm.zos.v2r4.idat300/x1e.htm?lang=en


http://www.ibm.com/support/knowledgecenter/SSEPH2_15.1.0/com.ibm.ims15.doc.msgs/msgs/ai.htm#ai

ExplanationA physical I/O error has occurred while executing aVSAM open or close. Message DFS0730I has beenissued to explain the details of this failure.

System actionSee message DFS0730I.

Programmer responseSee z/OS DFSMS Macro Instructions for Data Setsfor the VSAM physical error message. If necessary,recover the database by using IMS recovery utilities.

Problem determination:1, 17b, 18, 20, 23

Module:DFSDLOC0

Related referencez/OS: Reason code (physical errors)Related information“DFS0730I” on page 257UNABLE TO OPEN OR CLOSE DATASET WITHDDNAME ddname FOR REASON x, yy, zDATABASE dbdname programid“IMS problem determination” on page 11IMS messages and codes problemdetermination is accomplished by usingprocedures established by IBM.

DFS0732I WARNING MULTIPLE VSAM ACBSOPEN FOR DATASET WITH DDCARD xxxxxxxx

ExplanationA return from a VSAM open macro indicated that theopen completed, but there was already one or moreACBs open for the indicated data set. The SHR optionof the VSAM DEFINE utility provides the user theability to control the extent that a data set can beshared. The DEFINE has allowed the current data setto be shared.

System actionThe IMS system ignores the error and continuesprocessing.

Programmer responseThe IMS databases should never be shared by multiplebatch regions or batch and online regions. Correct theerror, and resubmit the job.

Module:

DFSDLOC0

DFS0733I IMODULE ERROR xx {LOADING| DELETING} {RANDOMIZING |INDEX EXIT | COMPRESSIONEXIT} MODULE moduname

or

IMODULE ERROR xx {LOADING | DELETING}{RANDOMIZING | INDEX EXIT | COMPRESSIONEXIT} MODULE moduname FOR DATABASEdedbname

or

IMODULE ERROR xx {LOADING | DELETING}{RANDOMIZING | INDEX EXIT | COMPRESSIONEXIT | SPARSE EXIT | PARTITION EXIT} MODULEmoduname FOR DATABASE dedbname

ExplanationThe IMODULE function of IMS encountered an errorwhen it attempted to load or delete one of thefollowing exit routines:

• A randomizing routine• A secondary indexing exit routine• An edit or compression exit routine• A sparse exit or partition exit routine for a DEDB

database with a Fast Path secondary index defined


Hexadecimal return code from IMODULE.moduname

Name of the exit routine.

For a description of IMODULE return codes, seeIMODULE return codes (Messages and Codes).

For a Fast Path database compression exit loadingerror, or a Fast Path secondary index sparse exit orpartition exit loading error, the DEDB database name(dedbname) is displayed in the message text. In thiscase, there is no accompanying message DFS0730I.

System actionMessage DFS0730I reason code I,52 is issued. If theattempt to load an exit routine failed, the database(named in message DFS0730I) is stopped. See theSystem Action information for message DFS0730I.


http://www-01.ibm.com/support/knowledgecenter/SSLTBW_2.4.0/com.ibm.zos.v2r4.idad500/x1o.htm?lang=en


Programmer responseProvide the module in a library where it can beaccessed without error.

Problem determination:1, 2, 3, 17b, 36

Module:DFSDLOC0, DBFMSIU0, DBFOLC02, DFSDOCA0

Related referenceIMODULE return codes (Messages and Codes)Related information“DFS0730I” on page 257UNABLE TO OPEN OR CLOSE DATASET WITHDDNAME ddname FOR REASON x, yy, zDATABASE dbdname programid“IMS problem determination” on page 11IMS messages and codes problemdetermination is accomplished by usingprocedures established by IBM.

DFS0734I UNABLE TO MERGE LOG DATASETS

ExplanationThere was an I/O error on one of the input log datasets to the Log Merge utility, DFSLTMG0.

System actionThe program terminates with decimal return code 12.

Programmer responseCorrect the error, and rerun the job.

Problem determinationSee the operating system message.

Module:DFSLTMG0

DFS0735I SAF ACCESS FAILED-Rnndbdname-ddname RETURNCODE=nnn. REASON CODE=nnnn.module-name.

ExplanationThe access authorization process for a VSAM or MediaManager data set encountered an error and failed. Rnnis the IMS reason for the failure. dbdname-ddname arethe DBD or Media Manager area name and ddnameof the data set being checked. RC=nnn REASONCODE=nnn are the return and reason code associatedwith the failure. module-name is the name of themodule that failed.

The reason code indicates the type of failure thatoccurred:Code (nnn)

MeaningR01

The database, dbdname, could not be openedbecause IMS was not allowed to access the dataset for dbdname-ddname at the required level.

R02The database, dbdname, could not be openedbecause IMS was not allowed to access the dataset association block (DSAB) for ddname. See theerror return code from the z/OS macro GETDSABthat was issued with ddname.

R03The database, dbdname, could not be openedbecause DFP Catalog Management encounteredan error accessing the catalog for the data set.The name of the Catalog Management module thatfound the error is module-name.

System actionThe data set is not opened.

Programmer responseThe response depends on the reason code.For reason code R01:

Check the return and reason codes as well as thesecurity product messages.

For reason code R02:Check the documentation on the return andreason codes for the GETDSAB macro in z/OSMVS Programming: Authorized Assembler ServicesReference Vol 2 (SA22-7610).

For reason code R03Check the documentation on the return and reasoncodes for the Catalog Management messageIDC3009I in z/OS MVS System Messages Vol 6(SA22-7636).

Problem determinationFor reason code R01:

See the IDC3009I message and the securityproduct documentation.

For reason code R02:See the GETDSAB documentation.

For reason code R03:See the IDC3009I message.

Module:DFSDRAC0



Related referencez/OS: GETDSAB return and reason codesRelated informationz/OS: IDC3009I

DFS736 PARM SYNCPLEX INVALID ON NRECOMMAND

ExplanationThe keyword OPTION with the parameter SYNCPLEXwas entered on a /NRE command. This combination isan invalid. The SYNCPLEX parameter is valid only onthe /ERE command.

System actionThe /NRE command is rejected.

Programmer responseRemove the OPTION SYNCPLEX from the /NREcommand.

Module:DFSICL20

DFS0737A DBRC SHOWS NO AVAILABLEOLDS. REPLY 'RETRY' OR 'ABEND'.

ExplanationDuring takeover or emergency restart, IMS tries toswitch to an available OLDS when the last OLDS doesnot have enough space for the WADS data and the finalaccounting record. If DBRC determines that none ofthe usable OLDS is available, this message is issued.

System actionAfter issuing this message, IMS retries the OLDSavailability scan for any response other than 'ABEND'.

Programmer responseObtain a listing of the appropriate PRIOLDS recordfrom the RECON data set. Try to make available anyOLDS listed as unavailable; in particular, archive anyOLDS that should be archived. IMS can be directed toretry the switch whenever OLDS availability changes.If you cannot correct this problem, reply ABEND; thenattempt emergency restart with more OLDSs.

Module:DFSFDLN0

DFS0738I tt...tt DDNAME=ddddddddLOGSEQ=nnnnnnnn

ExplanationAn error occurred, terminating an OLDS during IMSrestart.

In the message text:dddddddd

The ddname of the data set being processedwhen the error was encountered. dddddddd canbe blank.

nnnnnnnnThe log sequence number last processed.nnnnnnnn can be blank.

tt...ttReason string, can be one of the following string:OPEN ERROR FOR IMS LOG

Could not open the data set.READ ERROR ON IMS LOG

Read error.LOG SEQ ERROR ON IMS LOG

Next sequential block or log record not found.MISSING BLOCK ON IMS LOG

The next sequential log physical block wasnot found, but a higher sequence log physicalblock was found.

TRKCALC FAILED FOR IMS LOGTRKCALC macro failed

LOGIC ERRORA logic error was detected.

LOG TERMINATION FAILED FOR IMS LOGThe log could not be properly terminated.

VERIFY ERROR FOR IMS LOGThe WADS was not the one used when theOLDS was used.

MISSING RECORDS IN WADSA sequence of WADS records had fewerrecords than it should.

System actionIMS can continue if dual was specified for the dataset in which the problem occurred (for example, dualWADS or dual OLDS). Otherwise, IMS issues messageDFS0738X and terminates with abend 0005.

Programmer responseTerminate OLDS, using the Log Recovery utility; thenrestart IMS.




https://www-01.ibm.com/support/knowledgecenter/en/SSLTBW_2.4.0/com.ibm.zos.v2r4.ieam600/idc3009i.htm

Save a copy of the OLDSs and WADSs data sets. Also,list the DBRC RECON data set.

Module:DFSFDLM0, DFSFDLN0, DFSFDLP0, DFSFDLR0,DFSFDLT0

Related information“DFS0738X” on page 269ERROR TERMINATING OLDS RC=xx ddddddddnnnnnnnIMS abend 0005“IMS problem determination” on page 11IMS messages and codes problemdetermination is accomplished by usingprocedures established by IBM.

DFS0738X ERROR TERMINATING OLDSRC=xx dddddddd nnnnnnn

ExplanationRestart cannot proceed because of errors encounteredtrying to terminate an OLDS during IMS restart.



nnnnnnnThe log sequence number last processed. nnnnnnncan be blank.

xxThe hexadecimal error code. Register 14 containsthe address of the routine that detected the error.Register 15 contains an error code.Code (hex)

Meaning01

Could not open the WADS while trying to locatethe last-used WADS.

02The WADS was not the one used when theOLDS was used.

05The WADS was not the one used when theOLDS was used.

06WADS at the time of the last IMS failure wasunavailable. The error occurred while trying tolocate the last-used WADS.

07TRKCALC macro failed while trying to locatethe last used WADS.

09OLDS block sequence error (next sequentialblock was not found but a higher sequenceblock was found in the WADS) while rebuildingan OLDS block. A read error might haveoccurred in the middle of the OLDS.

0BWADS segment TOD is not in ascending orderwhile rebuilding an OLDS block.

0CInvalid BDW was found in the rebuilt OLDSblock.

0DInvalid RDW was found in the rebuilt OLDSblock.

0ERDW of X'FFXX' was found in the rebuilt OLDSblock, and it was not the last block in theWADS.

0FLog record sequence error was found in therebuilt OLDS block.

10Read error in a WADS while rebuilding an OLDSblock.

11EOF was detected in a WADS while rebuildingan OLDS block.

12Invalid segment ID (segment count is toolarge) was found while rebuilding an OLDSblock.

13Device error (segments were not written in thecontiguous WADS records) was found whilerebuilding an OLDS block.

A sequence of WADS records had fewerrecords than it should.

14Logic error was detected in moduleDFSFDLW0.

1COLDS termination process failed. MessageDFS0738I, indicating the cause of the error,might have been issued before this message.

20A reusable OLDS is unavailable. IMS could notfind an OLDS while copying an OLDS block froma WADS. All OLDS are either marked in error orunarchived.



21Not enough space on the current OLDS to holdall the WADS data, and no OPEN or reusableOLDS are available.

22Logic error was detected in module DFSFDLU0.

System actionIMS terminates with abend 0005.

Programmer responseTerminate OLDS, using the Log Recovery utility; thenrestart IMS.



Module:DFSFDLM0, DFSFDLN0, DFSFDLP0, DFSFDLR0

Related information“DFS0738I” on page 268tt...tt DDNAME=dddddddd LOGSEQ=nnnnnnnnIMS abend 0005“IMS problem determination” on page 11IMS messages and codes problemdetermination is accomplished by usingprocedures established by IBM.

DFS0739I tt...tt DDNAME=ddddddddLOGSEQ=nnnnnnnn

ExplanationAn error occurred while accessing a log data set duringIMS restart.


The ddname of the data set last processed whenthe error was encountered. dddddddd can beblank.

nnnnnnnnThe log sequence number last processed.nnnnnnnn can be blank.

tt..ttA string indicating the reason for the error. Thisvariable can be one of the following strings:OPEN ERROR FOR IMS LOG

Could not open the data set.CLOSE ERROR FOR IMS LOG

Could not close the data set properly.

READ ERROR ON IMS LOGRead error.

WRITE ERROR ON IMS LOGWrite error occurred while formatting theWADS.

LOG SEQ ERROR ON IMS LOGNext sequential block or log record not found.

MISSING BLOCK ON IMS LOGThe next sequential log physical block wasnot found, but a higher sequence log physicalblock was found.

TRKCALC FAILED FOR IMS LOGTRKCALC macro failed

LOGIC ERRORA logic error was detected.

UNABLE TO ALLOCATE IMS LOGDynamic allocation failed, a DD statement ismissing, or OPEN failed.

SEQUENCE ERROR - BOTH OLDSIn dual logging, a read error was detected onboth OLDS.

READ ERROR - BOTH OLDSIn dual logging, a read error was detected onboth OLDS.

XRF-ALT OR FDR GOT AN SLDSIn an XRF complex, the alternate (backup)system either allocated an SLDS or determinedthat the next log to be allocated is an SLDS.

In a Fast Database Recovery environment, theFast Database Recovery region either allocatedan SLDS or determined that the next log to beallocated is an SLDS.

WAITING FOR RESERVE - OLDSIn an XRF complex, takeover was requested,but the alternate system is unable to reservethe current OLDS.

WAITING FOR RESERVE - WADSIn an XRF complex, takeover was requested,but the alternate system is unable to reservethe current WADS.

DFSFDLVO RRTT TABLE ERRORA restart read transition table error wasdetected.

REREAD LAST GOOD BLK FAILDuring normal error recovery, an attempt toreread the last good OLDS block failed.

System actionIMS continues processing if an alternative inputlog data set is available or issues DFS0739X andterminates with abend 0175.



In an XRF complex, the IMS alternate systemencountered errors from which recovery wasimpossible. IMS issues message DFS0739X andterminates with abend 0176.

In a Fast Database Recovery environment, the IMSsystem issues message DFS0739X and terminateswith abend 0176.

Operator responseIf this error occurred during Fast Database Recoveryregion initialization, take a simple checkpoint in theactive IMS system, and make sure that the restartablecheckpoint is found in the OLDS before restarting theFast Database Recovery region.



Module:DFSFDLR0, DFSFDLM0, DFSFDLN0, DFSFDLP0,DFSFDLT0

Related information“DFS0739X” on page 271ERROR READING IMS LOG RC=xx ddddddddnnnnnnnIMS abend 0175IMS abend 0176“IMS problem determination” on page 11IMS messages and codes problemdetermination is accomplished by usingprocedures established by IBM.

DFS0739X ERROR READING IMS LOG RC=xxdddddddd nnnnnnn

ExplanationRestart cannot proceed because of errorsencountered.



nnnnnnnThe log sequence number last processed. nnnnnnncan be blank.

xxA hexadecimal error code. Register 14 containsthe address of the routine that detected the error.Register 15 contains an error code.

Code (hex)Meaning

15Could not open the data set.

16Could not close the data set properly.

17Read error.

18Reread of last good block failed.

19OLDS block sequence error.

1ANext sequential log record was not found.

1BTRKCALC macro failed.

1CLatest OLDS could not be terminated.

1DAllocation of the log data set failed. Dynamicallocation failed, a DD statement is missing,or OPEN failed. The left half of Register 15contains the DFSMDA return code.

1ENext log data set record was not found in theRECON data set, or the next OLDS is markedinvalid.

1FLatest log data set record was not found in theRECON data set, or the next OLDS is markedinvalid.

20Reusable OLDS is unavailable.

21Error return code from DBRC. Left half ofregister 15 contains the DBRC return code.

22A logic error was detected.

23Restart read transition table failure.

24A sequence error occurred on both OLDS (duallogging).

25A read error occurred on both OLDS (duallogging).

26In an XRF complex, the alternate system eitherallocated an SLDS or determined that thenext log to be allocated is an SLDS. In aFast Database Recovery environment, the FastDatabase Recovery region either allocated an




SLDS or determined that the next log to beallocated is an SLDS.

System actionIMS terminates with abend 0175. In an XRF complex,the IMS alternate system terminates with abend 0176.

In a Fast Database Recovery environment, the FastDatabase Recovery region terminates with abend0176.

Operator responseIf this error occurred during Fast Database Recoveryregion initialization, take a simple checkpoint in theactive system and make sure that the restartablecheckpoint is found in the OLDS before restarting theFast Database Recovery region.



Module:DFSFDLM0, DFSFDLN0, DFSFDLP0, DFSFDLR0

Related informationIMS abend 0175IMS abend 0176“IMS problem determination” on page 11IMS messages and codes problemdetermination is accomplished by usingprocedures established by IBM.

DFS0740I DBRC SAYS NO BACKOUTSNEEDED FOR DB xxxxxxxx

ExplanationWhen you issue a /START DB command withoutthe NOBACKOUT keyword, DBRC might tell IMS thatbackouts are not required. However the IMS onlinesystem might still think that backouts are required.This situation occurs when batch backouts havealready run successfully.

System actionIMS continues processing. Control blocks maintainedby the online IMS system to track of the backout dataare released as if the operator specified NOBACKOUT.


Module:DFSDBDR0

DFS0741I DATA COMPRESSION ERROR,UNCOMPRESSED DATA WILL BEWRITTEN TO DD DFSUCUMNDATASET

ExplanationAn error was detected while performing datacompress processing during change accumulationprocessing.

System actionProcessing continues; the expanded data is written tothe new change accumulation data set.

Module:DFSURIO0

DFS0742I WHILE EXPANDING DATA ERRORFOUND

ExplanationAn error was detected while performing dataexpansion during change accumulation or databaserecovery processing.

System actionProcessing terminates with a return code of 8 forChange Accumulation and a return code of 16 forDatabase Recovery.

Programmer responseSave job output and job input. Contact IBM SoftwareSupport.

Module:DFSURIO0

DFS0743I RRS HOLDS AN INDOUBT UOR FORWHICH IMS HAS NO DATA:URID=xxxxxxxxxx,TOKEN=yyyyyyyyyy

ExplanationDuring an IMS restart, RRS held some indoubt units ofrecovery (UOR), for which IMS has no knowledge. Thissituation was probably as a result of an IMS cold start.

In the message text:xxxxxxxxxx

The RRS unit of recovery identifier




yyyyyyyyyyThe IMS recovery token


User responseThe RRS URID and IMS recovery token are supplied.Use these to examine the RRS ISPF panels and theIMS log to determine the extent of a possible batchrecovery.

Module:DFSRRSI0

DFS0744A IMS HOLDS AN INDOUBT UOR FORWHICH RRS HAS NO DATA:URID=xxxxxxxxxx,TOKEN=yyyyyyyyyy

ExplanationDuring a restart, IMS determined that it held anindoubt unit of recovery (UOR), as identified by theIMS recovery token and the RRS unit of recoveryidentifier. However, z/OS Resource Recovery Servicesindicated that hardened log data was unavailable. Thisdata was needed to resolve the indoubt UOR.

In the message text:xxxxxxxxxx

The RRS URIDyyyyyyyyyy

The IMS recovery token

System actionIMS builds a recoverable indoubt structure (RIS) foreach indoubt UOR and waits for a resolution withthe /CHA UOR command. The RIS is maintained untilthe UOR is resolved or a cold start is done. A cold startis not recommended.

User responseResolve the indoubt UOR by issuing the /CHAcommand.

Module:DFSDRIS0

DFS0745E RRS HOLDS AN aaaaaaaaUOR FOR IMS STATE:bbbbbbbb, URID=xxxxxxxxxxTOKEN=yyyyyyyyyy

ExplanationDue to an error in either IMS or Resource RecoveryServices (RRS), the last recorded state in IMS for aUnit of Recovery (UOR) is incompatible with the lastrecorded state for the UOR in RRS. The followingtable shows the possible incompatible UOR states thatmight trigger this message to be issued.

Table 5. Possible incompatible UOR states

RRS State IMS State

INDOUBT INFLIGHT

INDOUBT PHASE 2

INCOMMIT INFLIGHT

The module DFSRRSI0 performs UOR synchronizationbetween IMS and RRS and issues this DFS0745Emessage after an incompatible state of a UOR isdetected. The UOR synchronization code path isdriven whenever IMS and RRS need to establish orreestablish communication with one another.

When IMS detects incompatible states for a UORduring IMS emergency restart (/ERE.), IMS continueswith emergency restart processing. Any unresolvedUORs may be manually resolved by using theinformation provided in this message.


The state of the unit of recovery (UOR) from thepoint of view of RRS. The value is either INCOMMITor INDOUBT.

bbbbbbbbThe state of the unit of recovery (UOR) from thepoint of view of IMS. The value is either INFLIGHTor PHASE 2.

xxxxxxxxxxThe RRS unit of the recovery identifier (URID).

yyyyyyyyyyThe IMS recovery token.

System action:Processing continues.

Output destinationMTO and the system console.

User responseUse the RRS URID and IMS recovery token thatare supplied in the message to examine the RRSISPF panels and the IMS DISPLAY UOR command todetermine the state of the UOR and possible actions tobe taken.


If the problem persists, contact IBM Software Supportand provide the RRS trace, the IMS log, and the outputof the RRS ISPF panels.

Module:DFSRRSI0

DFS0746I UOR IS ONE OF MULTIPLE UORSIN A SINGLE IMS COMMIT SCOPE- ALL UORS IN THIS SCOPE WILLBE RESOLVED

ExplanationThe unit of recovery (UOR) identified in the /CHAcommand was part of a protected conversationinvolving more than one IMS UOR. Because thedatabase changes done by one UOR could bedependent on a prior UOR, the changes must beresolved in a single sync point, and in the proper order,if the action is backout.

System actionPhase two of sync point is done for all of the UORsinvolved. Processing continues


Module:DFSIRST0

DFS0747I CHANGE ACCUM DATASET ISMARKED INCOMPLETE

ExplanationThe IMS Database Recovery utility detected thatthe input Change Accumulation (CA) data set isincomplete. It does not contain all the log data setchanges required to recover a database data set.

System actionThe Database Recovery utility terminates processing.

Programmer responseRun the Change Accumulation utility providing thenecessary log input; then run the Database Recoveryutility again.

Module:DFSURDB0

DFS0748I UNEXPECTED CHANGE ACCUMRECORD ENCOUNTERED -xxxxxxxx

ExplanationThe utility reading the Change Accumulation (CA) dataset detected that the input CA data set is missing orincomplete. The Change Accumulation utility splits adetail or spill record when all data for that detail orspill record does not fit into one detail or spill record.The message is issued for one of these reasons:

• One of the split detail records is missing.• One of the split spill records is missing.• A detail record is marked as having spill records, but

the Change Accumulation utility did not receive anyspill records for that detail record.


The name of the database with the record

System actionThe utility reading the CA data set terminatesprocessing.

System programmer responseSupply all CA volumes to the utility reading the CA dataset; then rerun the utility.


Module:DFSUC350


DFS0749I COMPRESSION EXIT ROUTINEnnnnnnnn INITIALIZATIONERROR - Uaaaa REASON rrrrrrrr

ExplanationAn initialization error was detected by a Segment Edit/Compression exit routine.

In the message text:nnnnnnnn

Name of the exit routine.Uaaaa

The IMS user abend code generated by the exitroutine.

rrrrrrrrThe unique label at which the error was detected.This label corresponds to the error reason code.


See the appropriate abend code for a descriptionof each code.

System actionMessage DFS0730I is issued with reason code I,58 .The database, identified in message DFS0730I, isstopped. For additional information, see messageDFS0730I.

Programmer responseDetermine the cause of the error and correct theproblem.

Module:DFSDOCA0

Related information“DFS0730I” on page 257UNABLE TO OPEN OR CLOSE DATASET WITHDDNAME ddname FOR REASON x, yy, zDATABASE dbdname programid

DFS0750I ERROR WITH rrr PGFIX, RETURNCODE = x

ExplanationA nonzero return code was received from the operatingsystem when attempting to fix storage. The page fixwas in response to the parameters supplied in theDFSFIXnn member of the data set described by theDDNAME=PROCLIB.

In the message text:rrr

The region where the storage was fixed andindicates CTL for the control region or DLS for theDL/I subordinate address space region.

xThe page fix error return code and is defined asfollows:

• 04 One or more entries could not be fixed.• 08 Insufficient number of pages available to

satisfy request.• 0C List format invalid.• 10 Parameter list pointer invalid.



Module:DFSIFIX0





DFS0751I IMS NOT RUNNING IN A VIRTUALREGION

ExplanationThe IMS control region is not being run in a z/OSsystem as a VIRTUAL=VIRTUAL region.

System actionIMS continues running in a VIRTUAL=REALenvironment.

Operator response:Either continue running as REAL, or close IMS downwith a shutdown checkpoint and rerun the IMS controlregion in a VIRTUAL=VIRTUAL region, if that is whatyou want.

Module:DFSIFIX0

DFS0752I UNEXPECTED CHANGE ACCUMTIME ENCOUNTERED - DBxxxxxxxx DSID yyy

ExplanationThe Change Accumulation (CA) detected a spill recordwith a time stamp earlier than the previous detailrecord time stamp. The value of xxxxxxxx is thedatabase name of the record. The value of yyy is thedata set ID of the record.

System actionThe CA utility processing continues.

System programmer responseTake an image copy of all databases and data set IDsidentified by message DFS0772I.

Module:DFSUC350

Related information“DFS0772I” on page 284KSDS EXTENDING AT TAKEOVER - DBDdddddddd, PROGRAM pppppppp NOT BACKEDOUT

DFS0753A MISSING SPILL RECORD AFTERA 5220 DETAIL RECORD - DBxxxxxxxx DSID yyy

ExplanationThe Change Accumulation (CA) detected a missing5240 spill record after a 5220 detail record wasprocessed. The value of xxxxxxxx is the databasename of the record. The value of yyy is the data setID of the record.

System actionThe CA utility terminates processing.

System programmer responseSave the RECONs, DBDLIB, CA jobs, CA data sets, andall logs. Contact IBM Software Support for assistance.


Module:DFSUC350


DFS0754I CADS INVALID FOR COEXISTENCE- ddname dsid

ExplanationThe CADS provided to the DB Recovery or ChangeAccumulation (CA) process in IMS Version 9 wasnot created by an IMS utility that stores coexistenceinformation in the file. Change Accumulation cannotaccept this CADS as input.

System actionThe process for this DBDS is ended.

System programmer responseInvalidate all of the CA data sets for the named DBDdata set. Run the process again using only log input asa source of changed data.


Module:DFSURIO0

DFS0755I FORMAT ERROR IN PROCLIBMEMBER=DFSFIXnn|DFSDRFnn

ExplanationAn error in format was encountered in the parametersspecified in the member DFSFIXnn or DFSDRFnn ofthe data set defined by the DDNAME=PROCLIB.

System actionIMS continues, but page fixing and allocation in DREFstorage of portions of the control program and modulepreload do not occur.

Operator response:(master terminal) Either continue running IMS withoutthe parts fixed or allocated in DREF storage, or doa shutdown checkpoint and rerun after DFSFIXnn orDFSDRFnn has been corrected.

Programmer responseCorrect the format of the FIX parameter in DFSFIXnnor the DREF parameter in DFSDRFnn.

Problem determinationFor a description of the DFSFIXnn member, seeDFSFIXnn member of the IMS PROCLIB data set(System Definition). For a description of the DFSDRFnnmember, see DFSDRFnn member of the IMS PROCLIBdata set (System Definition).

Module:DFSIFIX0

DFS0756I INVALID WORD IN DFSFIXnn|DFSDRFnn xxx

ExplanationThe word xxx specified in the member DFSFIXnnor DFSDRFnn of the data set defined by theDDNAME=PROCLIB is invalid.

System actionIMS continues running.

Operator response(master terminal) Either continue running IMS withoutthe parts fixed or allocated in DREF storage, or doa shutdown checkpoint and rerun after DFSFIXnn orDFSDRFnn has been corrected.

Programmer responseCorrect the invalid word in the DFSFIXnn or DFSDRFnnmember.


Module:DFSIFIX0

DFS0757I FIX COMPLETE: NO FIXINGREQUESTED

ExplanationThe DFSFIXnn member of the IMS PROCLIB data setis processed in two passes. This message can beissued during each pass and for two conditions. First,member DFSFIXnn of data set DDNAME=PROCLIBdid not request any fixing of storage for this pass.Second, the member contains either all blanks or allinvalid parameters. For invalid parameters, look for apreceding DFS0755I message. To determine whetherpage fixing was successful during a pass, look for aDFS0759I message.


Operator response:(master terminal) If page fixing was processed asexpected, no action is needed. If problems wereencountered, either continue running IMS without thepage-fixed parts or do a shutdown checkpoint andrestart IMS after DFSFIXnn has been corrected.

Programmer responseIf page fixing was not processed as expected, correctthe parameters in DFSFIXnn and restart IMS.

Problem determinationSee a description of the DFSFIXnn member.

Module:DFSIFIX0

Related referenceDFSFIXnn member of the IMS PROCLIB dataset (System Definition)Related information“DFS0755I” on page 278


http://www.ibm.com/support/knowledgecenter/SSEPH2_15.1.0/com.ibm.ims15.doc.sdg/ims_dfsfixnn_proclib.htm#ims_dfsfixnn_proclib


http://www.ibm.com/support/knowledgecenter/SSEPH2_15.1.0/com.ibm.ims15.doc.sdg/ims_dfsdrfnn_proclib.htm#ims_dfsdrfnn_proclib








FORMAT ERROR IN PROCLIBMEMBER=DFSFIXnn|DFSDRFnn“DFS0759I” on page 279THE FOLLOWING VIRTUAL ADDRESSES HAVEBEEN FIXED IN rrr xxxxxxxx yyyyyyyy-zzzzzzzz

DFS0758I FIX FAILURE: MORE THAN 62AREAS TO BE FIXED

ExplanationTo FIX storage as described by the parametersin the member DFSFIXnn of the data set whoseDDNAME=PROCLIB, more than 62 areas must befixed.


Operator response:(master terminal) Either continue running IMS withoutthe fixed parts, or do a shutdown checkpoint and rerunafter DFSFIXnn has been corrected.

Programmer responseReduce or combine areas to be fixed, and correct themember DFSFIXnn.

Problem determinationFor a description of the DFSFIXnn member, seeDFSFIXnn member of the IMS PROCLIB data set(System Definition).

Module:DFSIFIX0

DFS0759I THE FOLLOWING VIRTUALADDRESSES HAVE BEEN FIXED INrrr xxxxxxxx yyyyyyyy-zzzzzzzz

ExplanationThe virtual address range (yyyyyyyy-zzzzzzzz) has beenfixed in response to the parameters specified in themember DFSFIXnn of the data set described by theDDNAME=PROCLIB.

rrr identifies the region where the storage was fixedand will indicate:

CTL for the control regionDLS for the DL/I subordinate address space region

xxxxxxxx is the IMS name of the area fixed.

Note: For Fast Path blocks that are page fixed, In rrris not displayed. Fast Path blocks are page fixed in thecontrol region (CTL).

If the total size of all DEDB blocks in the systemexceeds 1 MB, IMS displays multiple DFS0759Imessages during start-up.


Module:DFSIFIX0

DFS0760I THE FOLLOWING FIX|DREFOPERANDS WERE NOT FIXED IN|ALLOCATED IN DREF IN rrr:xxxxxxxx

ExplanationThe operand specified has not been fixed or allocatedin DREF storage in the region indicated byrrr. Thevariable rrr is either CTL for the control region or DLSfor the DL/I subordinate address space. Either a poolor block name has been incorrectly specified, or themodule specified has not been loaded in region rrr.


Programmer responseIf a pool or block name was intended, update memberDFSFIXnn or DFSDRFnn in the IMS procedure library(DDNAME=PROCLIB) to correct the specification. For arequest to page fix a module, this message might benormal if the DL/I address space has been selected,because the module will be located in one region andnot in the other region.


Module:DFSIFIX0

DFS0761I SPACE NOT AVAILABLE FOR<PGFIX|DREF> PARAMETER LIST

ExplanationStorage to build a PAGE FIX or DREF parameter list inresponse to the parameters specified in the memberDFSFIXnn or DFSDRFnn of the data set describedby the DDNAME=PROCLIB does not exist in the IMScontrol region.









Operator response(master terminal) Either continue running IMS withoutthe parts fixed or allocated in DREF storage, or do ashutdown checkpoint and rerun after the region sizehas been changed.

Programmer responseIncrease the size of the IMS control region by a sizeequal to one page.

Module:DFSIFIX0

DFS0762I OSAM (TAPE | DASD) (READ| WRITE) ERROR - FUNC=aaSTATUS=bb, cc, dddd, eeee, ffff

ExplanationAn OSAM I/O error was encountered. A two- or three-line message, each numbered DFS0762I, is generated:

• The first line indicates (1) whether the I/O operationwas directed to a tape or to a direct-access device,(2) whether the I/O operation was READ or WRITE,(3) the OSAM operation type, and (4) the endingstatus of the operation.

• The second line indicates (1) the 4-character UNITname, (2) the failing channel command word, (3)if the device is direct access, the full disk addressassociated with the I/O operation, and (4) the IMSlog record types under which OSAM I/O controlblocks were logged.

Note: The second line is not displayed if the I/Ooperation was not started.

• The third line shows the name of the data set onwhich the error was located.

The variable fields are defined as follows:FUNC=aa

The OSAM operation type - defined as follows:01 Read-specific OSAM block02 Reserved03 read multiple OSAM buffers

*04 Scan for file mark05 Reserved06 Reserved

*07 STAE

08 Write specific OSAM block09 Reserved

*0A Write queued buffers

*0B Write sequential block

*0C Format logical cylinder

*0D Write file mark0E Reserved

*0F Format extent

*10 REDRIVE after EOV

*11 REDRIVE after DDR SWAP

*12 Post tape RRQ in error13 Virtual format logical cylinder

(* Indicates internal functions.)

STATUS=bbThe IOSB/IOB completion code used to post theoperation complete.

ccThe DECB status code (DECBSTAT) is defined asfollows:01 Undefined operation code02 DCB not open03 IDAL translation error04 Channel program protection error05 Incorrect length error (bad DCBBUFL)06 Permanent I/O ERROR07 DCB specified as DD Dummy08 RBN conversion error09 RBN beyond current end of data set0A End-of-file reached0B Caller not authorized for call type0C Unable to obtain channel program work area0D No space to add block to data set0E Associated chained block I/O error0F Reserved10 Unable to allocate an IOSB from the OSAM I/Ostorage pool11 DEB/DCB validity check error12 I/O prevented


13 Write queue errors (buffer prefix containsstatus)14 Buffer ignored due to previous error15 Chained read error (buffer prefix has status)16 Reserved17 Invalid block/buffer count18 Buffer prefix chained out of sequence19 Tape I/O error-try DDR SWAP1A Write attempted to a read-only data set1B I/O request terminated abnormally becauseof program check or machine check in IOS orappendage.1C Channel program check1D Record not found1E DCB already closing1F Nonzero return code from page fix routine20 Channel program translate error

ddddThe unit and channel status of the CSW

eeeeThe residual byte count of the failing CCW.

ffffThe first two sense bytes if the unit status in theCSW indicates unit check. If a unit check is notindicated, periods (.) are displayed.

Remember: If the I/O operation was not started,the character string I/O NOT STARTED is displayedinstead of the status bytes, the residual byte counts,and the first two sense bytes.UNIT=gggg

The 4-character unit name associated with thedevice.

FAILING CCW=hh Operation codeii Flagsjjjj Byte count

Note: If it is determined that the CCW address isinvalid, that is, causes a program check if used, thecharacter string UNKNOWN is displayed instead of theselected CCW fields. The paired comma indicates theabsence of the data/IDAL address.IOSEEK=kkk..k

The full disk address of the form MBBCCHHR. Thisfield is displayed only for direct-access devices.

LOG=llllThe IMS log record types under which the OSAMI/O control blocks were logged.

6201Only an X'6201' record was logged.

6202Both an X'6201' and an X'6202' record werelogged.

6203All three types of records were logged.

GERRX'6201' and X'6202' records were logged, but anattempt to log an X'6203' record failed because ofa GETMAIN error.

LERRX'6201' and X'6202' records were logged, but anattempt to log an X'6203' record failed because ofa logging error.

System actionProcessing continues. If the I/O error involves auser database, messages DFS0451I follow. See theexplanation for that message.

Operator response:Issue the /START DATABASE command, see if errorsare resolved.

Module:DFSAOS80

Related information“DFS0451I” on page 159modname, dbdname, ddname, i/o error, decbfield

DFS0763I STOP ABDUMP REJECTED FORTHREAD nnnn; SINGLE PHASESYNC POINT IN PROGRESS

ExplanationYou entered a /STOP REGION nnnn ABDUMP whilesingle phase sync point processing was in progress foran active Database Control (DBCTL) subsystem thread.

System actionThe command is ignored, and the thread continuessync point processing.

Module:DFSDSTP0

DFS0764A PAGE FIX FOR EXCPVR-REQUIREDAREAS FAILED. REPLY 'RETRY' OR'EXCP'.

ExplanationThe IMS system attempted to PAGE FIX areas ofstorage for the EXCPVR option. The operating systemwas unable to satisfy the request. The operator can


retry the PAGE FIX or answer EXCP, which cancels theEXCPVR option.

System actionIMS waits for the operator reply.

Operator response:(z/OS System) The operator can reply EXCP to cancelthe EXCPVR option or can attempt to make fixablestorage available and then answer RETRY. Fixablestorage can be made available by stopping otherjobs within the operating system. Decreasing generalactivity within the operating system can also makefixable storage available.

Module:DFSXIOB0

DFS0765I STORAGE NOT AVAILABLE FORNODE INTERPRET TABLE

ExplanationAn error was encountered while attempting to acquirestorage for the node interpret table from subpool 251.IMS is not able to communicate with an XRF complexuntil this problem is resolved and IMS is restarted.

The node interpret table is used to resolve the genericand actual node names for VTAM MSC links and ISCsessions communicating with an XRF complex.


Programmer responseIncrease the main storage available to IMS.

Module:DFSCINB0

DFS0766I PAGE FIX FOR STORAGE MGMTCONTROL BLOCKS FAILED

ExplanationAn attempt to page fix control blocks for storagemanagement failed.

System actionSystem continues, but with possible performancedegradation.

Operator response:Either continue running IMS without the fixed parts,or shutdown checkpoint and rerun when more realstorage is available.

Programmer responseMake certain more real storage is available to the IMScontrol program during the next execution.

DFS0767I OTMA MESSAGE FLOODCONDITION HAS BEEN RELIEVEDFOR MEMBER YYYYYYYY

ExplanationThe IMS system has processed the OTMA inputmessages to reduce the number of active inputmessages in the input queue. The input messagesfrom the member have reached 50% or below of themaximum active input message count.

System actionIMS continues to process OTMA messages from themember.

Programmer responseThis message informs the programmer that the OTMAmessage flood condition has been improved.

Module:DFSYFD00

DFS0768I AN INVALID BSAM FORMATTEDRECORD WAS DETECTED INDDNAME=xxxxxxxx. IT HAS BEENCLOSED

ExplanationA record in data set DDNAME=xxxxxxxx violated BSAMformatting rules for variable-length records.

System actionAn AF status code is returned to the database PCB.GSAM control blocks and the buffer containing theinvalid record are written to the IMSERR or SYSPRINTdata set. If another call is made to this data setwithout reinitializing GSAM, abend 0272 is issued.

Programmer responseTerminate the program, and correct the data set.


Module:DFSZD210





DFS0769I ttt SELECTIVE DISPATCHING - rrrr

ExplanationSelective dispatching was in effect since the lastcheckpoint because of a resource shortage. tttidentifies the TCB under which selective dispatchingwas in effect. rrrr identifies the resources which hadthe shortage.

Resources shortages are generally caused by anabnormally high volume of activity under the followingTCBs:TCB

Possible causes of selective dispatchingCTL

• High volume of communications activity.• Insufficient number of SAPs defined for the size

of the terminal network.• A disruptive event that caused communications

processing to be interrupted and a flood ofqueued communications work.

• IMS internal problems.

ALM

• High volume of LU 6.2 communications activity.• A disruptive event that caused LU 6.2

communications to be interrupted and a flood ofqueued LU 6.2 work.

• An application program coded to maintainallocated LU 6.2 conversations for an extendedperiod.

• IMS internal problems.

OIM

• OTMA experienced a high volume of OTMA CM1or CM0 input transactions.

• Insufficient number of pre-allocated SAPs aredefined for the OTMA client.

• OTMA communication was interrupted becauseeither IMS was restarted or OTMA was stoppedand restarted.

• An OTMA client application is coded to keep CM1sessions for an extended period of time.

• IMS experienced internal problems, such as longwait for a common resource, a long wait for I/Oto the log, or a wait for a latch.

When an IMS TCB is in selective dispatching, onlypriority units of work (for example, the MTO terminal)

and those already holding resources can be processeduntil the resources become available again. This coulddegrade response time for some terminal users.

The SAP resource can cause selective dispatchingwhen it is. in short supply. SAPs are IMS internalcontrol blocks that are required to process IMS unitsof work, communication requests (terminals) and LU6.2 requests. If the supply of available SAPs becomeslow, IMS attempts to allocate additional SAPs upto a maximum amount. If no SAPs are availableto process a unit of work, IMS invokes selectivedispatching for SAPs. When this occurs, IMS units ofwork can be processed only when another unit ofwork terminates and releases its SAP. This can causedegraded performance of the IMS system.

System actionContinues processing.

Operator responseThis message indicates a possible resource shortage.If this message occurs frequently, or is accompaniedby performance degradation, the system programmershould be informed.

System programmer responseThis message does not necessarily indicate that thereis a problem with IMS. Selective dispatching can occurfor legitimate reasons (for example, during an IMScheckpoint, or due to quick peaks in communicationsactivity. If this message occurs frequently or isaccompanied by IMS performance problems such aspoor terminal response time, then additional analysisis advisable.

If the TCB in selective dispatching is CTL, the numberof available dynamic SAPs can be increased bychanging the SAV= parameter on the IMS startup JCLor in the DFSPBxxx members.

If the TCB in selective dispatching is ALM, theproblem could be an application program that doesnot deallocate its LU 6.2 conversation for a longperiod. This can occur when an application programdoes not receive an immediate LU 6.2 response toCONFIRM.

If the TCB is OIM, the selective dispatching applies toOTMA and the reason for using selective dispatchingwas probably transient. To avoid selective dispatchingfor OTMA, you can adjust the number of pre-allocatedSAPs and the maximum number of SAPs that IMScan allocate dynamically by specifying the DSAP andDSAPMAX parameters in the OTMA client descriptor inthe DFSYDTx PROCLIB member and restarting IMS.


A dispatcher statistics log record (type X'45' subcodeX'0F') is written at each checkpoint. These logrecords should be printed and analyzed for selectivedispatching problems. Additional statistics records(type X'45') might be useful in indicating high storagepool utilization. Any problem reports related toselective dispatching should include a copy of the IMSlog that contains the checkpoint intervals during whichthe problem occurred or a printed copy of the X'45'records for those checkpoints.

Problem determination:5, 6, 23 34

Module:DFSSTAT0


DFS0770W NO FP CONTROL BLOCKS AREABOVE 16 MB

ExplanationFast Path control block module (DBFCONT0) was notallocated in ECSA because of insufficient storage.

System actionIMS gets storage from CSA and continues processing.

Programmer responseNotify the z/OS system programmer.

Module:DBFIFIX0

DFS0771I IMS LOGGING IS NOT IN EFFECT.

ExplanationIMS LOGGING is not in effect because an extended,or symbolic, checkpoint call has been issued and theIEFRDER DD statement is missing or has been definedas DD DUMMY.

System actionIf the IEFRDER DD is defined as DD DUMMY, only themessage is issued and processing continues. If theIEFRDER DD statement is missing, the call continuesto be processed but STATUSNL is returned in theIOPCB.

Programmer responseIf logging is needed for this job, add an IEFRDER DDstatement to the JCL.

Module:DFSPR000, DFSZSC00

DFS0772I KSDS EXTENDING AT TAKEOVER- DBD dddddddd, PROGRAMpppppppp NOT BACKED OUT

ExplanationA VSAM KSDS was being extended by the failing activeIMS system during takeover. The variable ddddddddidentifies the database; pppppppp identifies theprogram for which no backouts were done.

The IMS alternate system taking over the workload ofa failing active system does not know how or wherethe failing or degraded active system is changing theend-of-data. For this reason, IMS cannot use thisdatabase safely until the failing active system hasterminated.

System actionThe backouts for this database have been deferred,and the database is stopped. Either messageDFS2012I or DFS0773I are issued when the databaseis stopped.

Programmer responseWhen the failing active system has terminated, you cansafely start the database again. If the log containingthe database changes to be backed out has alreadybeen archived, you must run Batch Backout forthe PSB identified in this message. Then start thedatabase with the NOBKO parameter of the /STARTDB command or issue UPDATE DB START(ACCESS)OPTION(NOBACKOUT).

Module:DFSRBOI0

Related information“DFS0773I” on page 284DATA BASE - dddddddd STOPPED.“DFS2012I” on page 591GLOBALLY SHARED DATA BASE|AREA -dbdname|areaname STOPPED.

DFS0773I DATA BASE - dddddddd STOPPED.

ExplanationA non-block level shared database was beingextended by the failing active IMS system during


takeover. The variable dddddddd identifies thedatabase.

The IMS alternate system taking over the workloadof a failing IMS active system does not know howor where the failing or degraded active is changingthe end-of-data. For this reason, IMS cannot use thisdatabase safely until the failing active terminates.

System actionThis database has been stopped until the failing activeterminates. You cannot enter a /START DB or UPDATEDB START(ACCESS) command until the new activeIMS system knows that I/O Prevention is complete.

Programmer responseWhen the failing active IMS terminates completely, youcan safely start the database.

Module:DFSHDCL0

DFS0774I (CCCCFFSS) AREA=AREANAMEDD=DDNAME, AREA CLOSED,MUST COMPLETE TOSSED,CI-RBA=NNNNNNNNN, SEVEREERROR

ExplanationAn attempt was made to write to a closed area. Thissituation indicates a system error.

System actionThe WRITE MUST COMPLETE DMHR is disregarded,and the dependent region is terminated.

System programmer responseContact IBM service.

DFS0775I COMMAND REJECTED; TCO IS NOTACTIVE

ExplanationYou entered a /TRACE SET ON|OFF TCO command,but the Time-Controlled Operations are not active.


Operator response:Start the Time-Controlled Operations before enteringthe command.

Module:

DFSICLN0

DFS0776A AMP PARAMETER INVALIDFOR OSAM DATASET- DDNAMExxxxxxxx

ExplanationA DD statement for an OSAM data set contained theparameter AMP, which is not valid for OSAM.

System actionA return code of 16 is set and processing stops.

Programmer responseRemove the AMP parameter from the DD statement forthe OSAM data set and rerun the job.

Module:DFSURDB0

DFS0777 LU=xxxxxxxx EXCEEDS ALLOWEDQUEUE SPACE -- MESSAGECANCELLED

ExplanationAn attempt was made to acquire a buffer from thequeue manager. The requested size exceeded theallowed space for that LU. The variable xxxxxxxx isthe inputting LU name. If the LU name is network-qualified, it can be up to 17 bytes long. The allowedspace is the amount of space controlled by userinstallation, using the user exit DFSQSPC0.


Programmer responseCheck the size of the message.

Module:DFSRLM10

DFS0778I xxxxxxxx ERROR eeeeeeeeMERGING SIDTABLE FROM MSCSUBSYSTEM yyyyyyyy, ACTION =zzzzzzzz

or

xxxxxxxx MSC SUBSYSTEM yyyyyyyy HAS JOINED/LEFT THE SHARED QUEUES GROUP, ACTION =zzzzzzzz


or

xxxxxxxx ERROR eeeeeeee SENDING/RECEIVINGSIDTABLE TO/FROM MSC SUBSYSTEM yyyyyyyy,ACTION = zzzzzzzz

ExplanationThis message is produced when the multiple systemscommunications (MSC) feature is supported in ashared queues group (SQG) environment and one ofthe following events occurs:

• An IMS subsystem joins or leaves the shared queuesgroup.

• An error is detected while sending or receivingthe MSC system identification table (SIDTABLE)to or from another IMS while processing an IMSsubsystem join or leave.

• An error is detected while merging a SIDTABLEreceived from another IMS that has joined theshared queues group.

• A residual SIDTABLE storage area is being freedthat was created from a previous merge of theSIDTABLES when an IMS subsystem joined theshared queues group.

In the message text:Variable

Meaningxxxxxxxx

The IMSID of the system that issued the messageor detected the error.

yyyyyyyyThe IMSID of the other IMS that joined or left theSQG, or where the SIDTABLE was being sent toor received from, or where the SIDTABLE beingmerged was sent from.

zzzzzzzzaction code:ACCEPTED

The event join/leave was acceptedIGNORED

The error was ignored. If receiving a SIDTABLEfrom another IMS, the received table isnot merged with current table. If sending aSIDTABLE to another IMS, the table might notarrive in the other IMS to be processed. Ifmerging a SIDTABLE, one or more SYSIDS inthe received table is ignored.

eeeeeeeeError code produced by the MSC Shared QueuesInitialization Routine that detected the error.

RoutineDescription

FREEAWSIError freeing received SID table storage.

FREEENDError freeing storage at end processing.

FREEOSIDError freeing old SID table storage after merge.

FREEXCFSError freeing storage acquired by XCF.

FUNCHIGHFunction value too high.

FUNCZEROFunction not specified.

GETAWSIDError getting AWE/SID table storage.

GETHLNBError getting LNB storage.

GETNSIDError getting storage or blocks for new SIDtable.

INITSIDError initializing SID table.

INVAWECBECB in AWE Invalid.

System actionIMS continues processing. If the event was an error,a type 6701-MNZE log record was written to the IMSonline log data set. IMS continues processing.

Operator responseIf an error was indicated, the join, leave, or mergeevent might not be completely processed. Have theerror corrected and bring the affected IMS subsystemsdown and back up again (for example, leave andjoin). If no error is indicated, then this message isinformational only.

Programmer responseIf the event was an error, this is most likely an errorwith the MSC configuration, or a system error inthe IMS subsystems or MS XCGF facility. Collect thedocumentation noted under problem determinationand call IBM Software Support.

Problem determinationRecord this message and any other DFS0778messages from both IMS subsystems in the sharedqueues group identified by the IMSIDS in the


messages. Print the 6701-MNZE log records usingthe DFSERA10 log print utility, from the online logdata sets from both IMS subsystems. Take a consolememory dump of both IMS subsystems using thez/OS DUMP command, as soon as possible beforeany other IMS subsystems join or leave the sharedqueues group. Save the memory dumps in case theyare needed for diagnosis.

Module:DFSMNZ00

DFS0779E KEYWORD keyword OMITTED

or

ERROR FOR PROCLIB MEMBER member_name,JOBNAME=job_name

or

STRUCTURE NAMES FOR EMHQ AND MSGQ SHOULDBE UNIQUE - STRUCTURE NAME=structure_name

ExplanationIMS initialization encountered an error whileprocessing either the DFSSQxxx PROCLIB memberor the SHARED_QUEUES section of the DFSDFxxxPROCLIB member. Multiple DFS0779E messages canbe issued if multiple errors are found. After issuing thismessage, IMS terminates with abend code 0071.member_name

The name of the PROCLIB member or membersthat were being parsed. If shared queuesparameters are coded in both DFSSQxxx andDFSDFxxx, both members are listed.

job_nameIf applicable, the IMS control region job name.

structure_nameThe structure name that was specified both for themessage queue and the EMH queue structure.

keywordThe name of a required keyword that was notfound.

System actionIMS initialization terminates with abend code 0071.

System programmer responseCorrect the shared queues parameters ineither the DFSSQxxx IMS.PROCLIB member, orthe SHARED_QUEUES section in the DFSDFxxxIMS.PROCLIB member, and restart IMS. Sharedqueues parameters can be specified in both of theselocations. Parameters that are specified in DFSSQxxxoverride parameters specified in DFSDFxxx.

Module:DFSSQ012


DFS0780I EOD WAS ENCOUNTEREDWHILE REPOSITIONINGDDNAME=xxxxxxxx DURING XRST.

ExplanationEnd-of-data was encountered while repositioning aGSAM non-DASD data set during an extended restartoperation.

System actionGSAM terminates with abend 0102.

Programmer responsePrint type '18' log records used for the restart to assistin problem determination.


Module:DFSZD210


DFS0781I ABEND cccc IN mmmm...

ExplanationThe variable cccc identifies the 4-digit user abend orpseudoabend, or the 3-digit system abend; mmmm isthe CHANGEID information for the abending module.This information varies, depending upon the codingof the CHANGEID macro. Basically, the CHANGEIDinformation contains the module name, assembly dateand time, latest applied APAR number, and a variablecharacter string identifying all the applied APARs.




This message is issued for all abends, whether atransaction retry is attempted. It is issued:

1. At the time of the initial failure, before a potentialtransaction retry.

2. At the time the failure recurs after a transactionretry attempt, if the retry results in a failure.

Note: The failure occurring on the transaction retrymight not be the same as the original failure, althoughthis should be an exceptional case.

System actionEven if a transaction retry is attempted, the systemcontinues to terminate abnormally, providing the usualmemory dumps, entries to the log tape, and collectingdiagnostic information.


System programmer responseSave the diagnostic information. Contact IBM SoftwareSupport for assistance.

Module:DBFTCMT9

DFS0782I NO INFO ABOUT ABENDINGMODULE - R12 NOT POINTINGCHANGEID

ExplanationWhen register 12 does not point to the CHANGEIDinformation, this message is issued instead ofDFS0781I, ABEND ccc IN mmmm.

If a non-IBM, IMS application program terminatesabnormally, this message might be sent to the JES2log. CHANGEID information is expected for IBM, IMSmodules only.




System programmer responseIf this is an IMS user abend or system abend, saveall diagnostic information. Then contact IBM SoftwareSupport for assistance in problem determination.

If this is an application abend, see your installationprocedure for handling application program abends.

Module:DBFTCMT9

DFS0783I NO INFORMATION ABOUTABENDING MODULE - SDWA NOTAVAILABLE

ExplanationWhen the ESTAE process cannot obtain a systemdiagnostic work area (SDWA), this message is issuedinstead of DFS0781I, ABEND cccc IN mmmm.




Module:DBFTCMT9

DFS0784I TRAN tttttttt TO BE RETRIED-MSGnnnnn TERM xxxxxxxx jjjjjjjj

ExplanationThis message is issued when a failing transaction iseligible to be retried (possibly in a different dependentregion). The variable tttttttt identifies the transactioncode; nnnnn identifies the input sequence numberassociated with the failing transaction; xxxxxxxxidentifies the originating terminal for the messageassociated with the failing transaction. The variablejjjjjjjj identifies the job name of the dependent region inwhich the transaction failed.

System actionThe system retries the transaction.



Module:DBFTCMT9

DFS0785I TRAN tttttttt NOW IN RETRY -MSGnnnnn TERM xxxxxxxx jjjjjjjj

ExplanationThis message is issued when transaction retry is inprogress. The variable tttttttt identifies the transactioncode; nnnnn identifies the input sequence numberassociated with the failing transaction; xxxxxxxxidentifies the originating terminal for the messageassociated with the failing transaction. The variablejjjjjjjj identifies the job name of the dependent region inwhich the transaction is retried.

System actionThe system starts to process the transaction to beretried and produces additional diagnostic information(detailed trace information) during the retry tofacilitate problem analysis.

This diagnostic information is made availableimmediately after completing (successfully orunsuccessfully) the retried transaction. The diagnosticinformation is routed to a SYSOUT data set using theSYSOUT class specified in the MSGCLASS parameter ofthe JOB statement of the dependent region in whichthe transaction is retried.

Operator response:Ask the system programmer to collect the additionaldiagnostic information.

System programmer responseCollect the additional diagnostic information.

Module:DBFTCMT9

DFS0786I A SECOND ABEND OCCURREDDURING TRANSACTION RETRY

ExplanationThis message is issued after an unsuccessfultransaction retry, and follows message DFS0781I,ABEND cccc IN mmmm.

Note: If transaction retry fails with an abend identicalto the original failure, this information is providedtwice: once when the failure occurs, and a second timewhen transaction retry reproduces the failure.

System actionThe system again terminated abnormally while in theprocess of executing transaction retry.



Module:DBFTCMT9

DFS0787I TRANSACTION RETRY WASATTEMPTED AND COMPLETEDSUCCESSFULLY

ExplanationThis message is issued at entry to the sync process ofthe retried transaction after a successful transactionretry.

System actionSync processing continues for the retried transaction.

In this case, the system does not stop the transactionand overrides the action indicated in messageDFS554A.


System programmer responseSave the diagnostic information. If the error recurs,contact IBM Software Support for assistance.

Module:DBFTCMT9

Related information“DFS554A” on page 197jobname.region.stepname. prog PSBname(x)transaction-codesys-completion-code user-completion-code PSBSMBLTERM:|LUNAME:|RTKN=tokenREASON=reason originating terminal

DFS0788I DYNAMIC ALLOCATION FORTRACE DATASET FAILED - REASONCODE nnnn


ExplanationThis message is issued when dynamic allocation failsfor the trace data set. Reason code nnnn is explainedin z/OS MVS Programming: Authorized AssemblerServices Guide (SA22-7608)

System actionThe system continues transaction retry withouttracing, attempting to acquire the needed resource atthe time of the next application program calls.


System programmer responseNo action is required.

Module:DBFTCMT9

Related referencez/OS: Interpreting error reason codes fromDYNALLOC

DFS0789I GETMAIN FAILED TODYNAMICALLY ALLOCATE TRACEDATASET

ExplanationThis is an informational message only.




Module:DBFTCMT9

DFS0790I OPEN FAILED FOR DYNAMICALLYALLOCATED TRACE DATASET

ExplanationThis is an informational message only.



Master terminal operator response


ModuleDBFTCMT9

DFS0791A PROCESSING OF HSSP HIC/PICBY DB RECOVERY TERMINATEDABNORMALLY FOR AREA=xxxxxxxxDD=yyyyyyyy REASON CODE=zz

ExplanationThis message is issued during execution of theDatabase Recovery utility when an error involving anHSSP Image Copy (HIC) or HSSP Partial Image Copy(PIC) occurs. The Database Recovery utility failed.The following reason codes indicate the cause of theproblem:Reason code

Explanation10

DD statement for Area xxxxxxxx DD yyyyyyyy wasmissing in the JCL.

20Utility was unable to open a DCB with DDNAMEyyyyyyyy.

30VSAM SHOWCB failed.

40VSAM MODCB failed.

50Either the date/time stamp in the second CI doesnot match the HIC/PIC time stamp, or the secondCI indicates that the data set is not an image copydata set.

60The PIC time stamps are not in chronologicalorder.

70The date/time-stamp does not match the stamp inthe log record for any of the input HIC/PIC datasets.




Programmer responseFor reason code 10, ensure that all required DDstatements are supplied.

For reason code 20, use the memory dump todetermine the cause of the open error (see z/OSDFSMS Macro Instructions for Data Sets for possiblecauses of failure).

For reason codes 30 and 40, contact your IBMrepresentative.

For reason code 50, ensure that all HIC/PIC data setsused are valid.

For reason code 60, ensure that the PIC time stampscontained in SYSIN are in date/time sequence.

For reason code 70, ensure that SYSIN contains allneeded HIC/PIC time stamps.

Problem determination2, 3, 4, 8, 20, 36, and listings of the RECON data sets.

Module:DBFUHIC0

Related referencez/OS: OPEN--Connect Program and Data(BDAM, BISAM interface to VSAM, BPAM, BSAM,QISAM interface to VSAM, and QSAM)Related information“IMS problem determination” on page 11IMS messages and codes problemdetermination is accomplished by usingprocedures established by IBM.

DFS0792A DATABASE TARGET VSAMDATASET MUST BE EMPTY PRIORTO RUNNING RECOVERY

ExplanationWhen running the Database Recovery utility, if theDDNAME specifies VSAM data set and a failureoccurred during a previous run of the utility, then itmight be necessary to delete and redefine the VSAMdata set.


Programmer responseDelete and redefine the VSAM data set that is beingopened for output as the target data set.

DFS0793I THE TOTAL OTMA SEND-THEN-COMMIT(CM1) CONTROL BLOCKS(TIB) HAS DECREASED BELOW nnn

or

THE FLOOD CONDITION OF TOTAL OTMA INPUTMESSAGES (TIB) WAS RELIEVED

Explanation:This message is issued during an OTMA message floodcondition to provide status on the flood condition.The total number of uncompleted OTMA commitmode 1 (CM1) messages from all the OTMA clients isdecreasing.

System action:Processing continues. An OTMA protocol message withthe OK status is sent to all the OTMA clients.

System programmer response:The global OTMA message flood condition has beenresolved. However, an individual OTMA member mightstill experience a flood condition.

Module:DFSYFD00

DFS794I APPLICATION NOT PERMITTED TOREASSIGN LTERM IT IS USING

ExplanationThe /ASSIGN command was rejected because AOIprograms are not permitted to reassign an LTERM thatthe application is using.


Programmer responseRedesign the AOI application program so that it doesnot issue an /ASSIGN command that reassigns anLTERM it is already using. The LTERM in the redesignedAOI program cannot be any of the following:

• The LTERM that originated the AOI transaction• The destination LTERM to which the application is

inserting messages• The alternate destination LTERM to which the

application is inserting messages

Module:DFSICL70


http://www-01.ibm.com/support/knowledgecenter/SSLTBW_2.4.0/com.ibm.zos.v2r4.idad500/opn.htm?lang=en



DFS795I RESOURCE ACCESS FAILURE;NOTIFY SYSTEM PROGRAMMER

ExplanationThe command was rejected because the commandprocess detected a system error while attempting toaccess a resource. A request to use or lock a resourceresulted in an unexpected return code.



System programmer response:See the topic titled "IMS problem determination".


Module:DFSICL70


DFS0796A IS NOT A VALID HALDB MASTEROR PARTITION DATABASE,REASON=nn

ExplanationOne of the following errors was encountered:Code (hex)

Meaning01

The DBD specified was not found in DBDLIB.02

The DBD specified was found in DBDLIB but is nota HALDB DBD.

03The specified HALDB DBD does not exist inRECON.

04The specified HALDB partition does not exist inRECON.

System actionProcessing continues if other HALDB masterdatabases or partitions are to be processed and returncode is set to 8.

User responseCheck and correct the error condition indicated by thereason code.

Module:DFSUPNT0, DFSUPNT1

DFS0796I Reason Code = rc message

ExplanationAn error occurred, indicated by rc, with anaccompanying message issued by module DFSUPNT0.Each reason code has its own explanation andresponse. See the following reason codes andmessages to further identify the type of error andappropriate action:

REASON = 01 DATABASE OR PARTITION NOTFOUND IN RECON - &DBNAME

The specified DBD, &DBNAME, does not exist inRECON.

System Action: Processing halts and return codeis set to 8. Check and correct the error conditionindicated by the message and reason code.

REASON = 02 DATABASE IS NOT A HALDB DBD ORPARTITION - &DBNAME

The specified DBD, &DBNAME, is not defined inRECON as a HALDB.

System action: Processing halts and return code isset to 8.

User response: Check and correct the errorcondition indicated by the message and reasoncode.

REASON = 03 DATABASE NOT FOUND IN DBDLIB -&DBNAME

The specified DBD, &DBNAME, is defined in RECONas a HALDB, but it was not found in DBDLIB.



REASON = 04 INITALL NOT ALLOWED FORPARTITION - &DBNAME

A conflict resulting from a SYSIN statementspecifying a partition name that is a partition


of a HALDB master name &DBNAME which alsoappears in a different SYSIN statement.

System action: Processing halts.

User response: Remove the conflicting statementsspecifying partition names, if you want to initialize(INITALL) all of the HALDB partitions; or removethe INITALL statement from the DFSOVRDS dataset to unconditionally initialize specific partitions.Remove the HALDB master name if no additionalpartitions existing in RECON and recorded asPINIT=YES (partition initialization required) are tobe initialized.

Module:DFSUPNT0

DFS0797E The database PCB control blockswere incorrectly built for HALDBmaster database

ExplanationValidation of the PCB control blocks for the specifiedHALDB master database failed. This is an IMS internalerror.

System actionProcessing is halted.

Operator response:Call IBM Software Support to report this problem.

Module:DFSUPNT0, DFSUPNT1

DFS0798I eee PROCESSING COMPLETE FORjjjjjjjj RC=0000RSN=00000000 ASCB=aaaaaaaaASID=ddddTRC=tttttttttttttttt:zzzzzzzz

ExplanationAn end of memory (EOM) event for an IMS dependentregion has been detected and processed.

In the message text:eee

SSI call type: EOM (end of memory) or EOT (end oftask)

jjjjjjjjDependent region job name

aaaaaaaaDependent region ASCB (address space controlblock)

ddddDependent region ASID (address space identifier)

ttttttttttttttttTrace string (IDTEOMTR or IDTEOTTR)

zzzzzzzzAddress of the IDT entry

System action:The results of EOM processing are displayed inthe message. The region has terminated, clean upprocessing was successful, and the IDT and VTDentries for the region are cleared.


Module:DFSBCK00, DFSISI00, DFSVCI00

Related referenceEnd of memory codes from DFS0798I(Messages and Codes)Related information“DFS0798W” on page 293eee PROCESSING COMPLETE FOR jjjjjjjj RC=rrrrRSN=ssssssss ASCB=aaaaaaaa ASID=ddddTRC=tttttttttttttttt:zzzzzzzz

DFS0798W eee PROCESSING COMPLETE FORjjjjjjjj RC=rrrrRSN=ssssssss ASCB=aaaaaaaaASID=ddddTRC=tttttttttttttttt:zzzzzzzz

ExplanationAn end of memory (EOM) event for an IMS-dependentregion has been detected and processed.

In the message text:eee

SSI call type: EOM (end of memory) or EOT (end oftask)

rrrrReturn code

ssssssssReason code

jjjjjjjjDependent region job name

aaaaaaaaDependent region ASCB (address space controlblock)

ddddDependent region ASID (address space identifier)

ttttttttttttttttTrace string (IDTEOMTR or IDTEOTTR)

zzzzzzzzAddress of the IDT entry


http://www.ibm.com/support/knowledgecenter/SSEPH2_15.1.0/com.ibm.ims15.doc.msgs/compcodes/ims_eom_conditions.htm#returnandreasoncodestableforpk61267

http://www.ibm.com/support/knowledgecenter/SSEPH2_15.1.0/com.ibm.ims15.doc.msgs/compcodes/ims_eom_conditions.htm#returnandreasoncodestableforpk61267

System action:The results of EOM processing are displayed in themessage.

System programmer response:Contact IBM Software Support for help.

Module:DFSBCK00, DFSISI00, DFSVCI00

Related information“DFS0798I” on page 293eee PROCESSING COMPLETE FOR jjjjjjjjRC=0000RSN=00000000 ASCB=aaaaaaaa ASID=ddddTRC=tttttttttttttttt:zzzzzzzz

DFS0799E rgntype REGION jobname BEINGTERMINATED AT CONTROLREGION END OF MEMORY

ExplanationThe control region address space ended beforea subordinate address space (DL/I or DBRC) wasproperly shut down. IMS detects this condition andabnormally terminates the surviving region with userabend 0150. This is an unusual condition, and mightoccur when the FORCE command is issued against thecontrol address space, or the control address spaceis terminated without completing resource cleanup. Ifyou receive this message, be aware that some IMS-allocated resources such as common storage mightnot have been freed from the prior IMS instance. Thiscondition might require an IPL of your z/OS system torecover or release these resources.

In the message text:rgntype

The address space type of the region beingabnormally terminated, which is either DL/I orDBRC.

jobnameThe job name of the DL/I or DBRC region beginabnormally terminated.

System actionIMS schedules the abnormal termination of theindicated address space. The address spaceterminates with abend 0150.

Operator responseBefore restarting IMS, ensure that the DL/I or DBRCaddress space indicated by rgntype terminates. If theregion does not terminate, attempt to cancel it fromthe console. This message indicates that IMS resourcecleanup might have been skipped or only partially

completed. This is likely if the FORCE command wasissued against your IMS control region. When youreceived this message, you might encounter storageshortages or other resource-related problems, whichmight require an IPL of the z/OS system.


Module:DFSRSMR0


DFS0800I AWAITING NOTIFICATION FROMSUBSYS xxxxxxxx

ExplanationIMS attempted to connect to the subsystem specifiedby xxxxxxxx. The connection failed because thespecified subsystem either was not active or couldnot respond to the connection attempt. A notifymessage was queued by the specified subsystem.When the subsystem becomes active and can connect,the subsystem issues an internal MODIFY command(notify message) to IMS where the connection processis attempted again.

System actionThe IMS subtask TCB attached for the specifiedsubsystem waits for an internal MODIFY commandto attempt the connection process again. Until theinternal MODIFY command is issued, a /STA Subsysfor xxxxxxxx does not work, and a DFS058I messageis issued with CCC COMMAND COMPLETED EXCEPTxxxxxxxx text.

Programmer responseRestart the specified subsystem to issue the internalMODIFY command. The connection process is thenattempted again.

This error might occur if the subsystem that is tryingto issue the MODIFY command does not have theauthority to issue the command. Check your z/OSsystem log (SYSLOG) for security errors to determineif this is the cause of the problem. If it is, correct theproblem and then restart the specified subsystem.

Module:DFSESI30




CCC COMMAND COMPLETED EXCEPT KKK P01,P02, P03, P04, P05, P06, P07, ...ETC.


Chapter 20. DFS messages, DFS0801I - DFS0850W


DFS0801I SUBSYSTEM CONNECTION FORxxxxxxxx COMPLETE

ExplanationIMS has successfully connected to the externalsubsystem xxxxxxxx, which was defined in the SSMmember for subsystem connection.

System actionA subsystem-to-subsystem connection exists betweenIMS and the specified subsystem.

Module:DFSESI30

DFS0802I CANCEL COMMAND REJECTEDBY IMS, USE /STOP REGIONCOMMAND TO STOPIMS DEPENDENT REGION,JOBNAME=zzzzzzzz

ExplanationIMS intercepts all cancel commands for its dependentregions to avoid a possible abend 0113. zzzzzzzz is thename of the job that encountered the problem.

System actionCommand is ignored.

Operator response:Enter the proper /STOP REGION command to IMS ifyou want to stop the IMS-dependent region.

Module:DFSISI00

DFS0803A NO STATS RECORDS FOUND ATEND OF INPUT

ExplanationHISAM reload module did not encounter any statisticalrecords at end of input from HISAM unload. Thismessage is issued along with a statistical reportto show statistics accumulated from the input fordiagnostic purposes.

System actionAbnormally terminates with a return code 8.

Programmer responseA probable cause of this error is using the first volumeof a multi-volume set of input and thus causing thereload module to encounter data at end of input,rather than statistical records.

Input from an unload that had abnormally terminatedcan also cause this condition.


Module:DFSURRL0


DFS0804I CANCEL COMMAND REJECTED BYIMS, /MODIFY COMMIT COMMANDIN PROGRESS, JOBNAME =xxxxxxxx

ExplanationIMS does not allow a CCTL or ODBA connectedaddress space to be canceled while a /MODIFYCOMMIT or INITIATE OLC PHASE(COMMIT)command is in progress.



Reissue the CANCEL command after the /MODIFYCOMMIT or INITIATE OLC PHASE(COMMIT)completes.

Module:DFSISI00

DFS0805I CANCEL COMMAND REJECTED BYIMS. JOBNAME=nnnnnnnn HASACTIVE ODBA THREADS. ODBAID=iiiiiiii


ExplanationIMS intercepts all cancel commands that target anaddress space connected to IMS. The command isrejected because there are active ODBA threads.


The job or task name.iiiiiiii

The ODBA identifier to IMS returned by a /DISCCTL ALL command.

System actionThe command is rejected. After the CANCEL commandis issued, no new threads will be allowed to start fromthe target address space until the connection to IMShas terminated.

Operator responseAllow the active threads to complete, then reissue theCANCEL command.

Module:DFSISI00

DFS0806I NO DBCTL MULTI-SEGMENTCOMMAND BUFFERS AVAILABLE

ExplanationIn a Database Control (DBCTL) environment, you canperform multi-segment command processing from amaximum of eight consoles at a time. This messageappears when eight consoles are currently in themulti-segment processing state.

System actionThe command segment is ignored.

Programmer responseTry again later. If repeated attempts fail, otherconsoles might be in multi-segment command modeand are unaware of it. Enter a command recognitioncharacter (CRC) from one of these other consoles.

Module:DFSISI20

DFS0807I DBCTL MULTI-SEGMENTCOMMAND BUFFER OVERFLOW

ExplanationIn a DBCTL environment, a multi-segment commandcan have a maximum length of 241 characters. This

number includes the leading command recognitioncharacter (CRC) in the first segment, but not doesnot include CRCs in other segments. The segmentsentered from the console are internally concatenated.If the concatenated segments of the command exceedthe 241 character maximum, this message appears.

System actionThe segment that caused the command to exceedmaximum length is discarded. All previous segmentsremain internally concatenated.

Programmer responseTerminate the in-progress command by entering ashorter final segment. A single CRC entered at theconsole is a valid final segment.

Module:DFSISI20

DFS0808W IMS region region-id (in IMSback-end aaaaaaaa) has been inwait-syncpoint|wait-RRS status forOTMA client yyyyyyyy and tpipezzzzzzzz for xx minutes.

ExplanationThe region indicated in the messages has beenin a wait-syncpoint condition for xx minutes. Theinformation in the message is as follows:aaaaaaaa

IMS nameyyyyyyyy

OTMA client namezzzzzzzz

The transaction pipe namexx

Time in minutes that the region has been in a waitstate

System actionThe IMS region remains in the wait-syncpointcondition until the needed ACK or NAK response isreceived, or until an IMS command is issued to stopthe waiting.

Programmer responseCheck the OTMA client application to find out why arequired ACK or NAK is not sent to IMS OTMA.

Module:DFSYMEM0


DFS0809E IMS region region-id (in IMS back-end aaaaaaaa) has timed outfor OTMA client yyyyyyyy tpipexxxxxxxx for nn seconds.

ExplanationOTMA detected a timeout for a transaction running in adependent region for a CM1 message. The informationin the message is as follows:aaaaaaaa

IMS nameyyyyyyyy

OTMA client namexxxxxxxx

The transaction pipe namenn

Time in seconds that the region has been in a waitstate

System actionFor MPP regions, IMS terminates the transactionabnormally and issues an abend 0119.

For IFP regions, the action depends on the sharedqueue environment.

• Without shared queues, or with shared queues butwhen processing a local transaction (originating onprocessing IMS), no abend is issued. IMS backs outthe updates and sends a deallocate abnormal flow tothe end-client.

• For IFP regions, operating in a shared queueenvironment and processing as a back-end (messageorigin is not the processing IMS), an abend 0119 isissued.

Programmer responseCheck the OTMA client application to determine whythe required ACK or NAK response is not sent to IMSOTMA.

Module:DFSYMEM0


DFS810A IMS (DCCTL) READY yyyyddd/hhmmsst jobname.stepname

ExplanationIMS initialization has successfully completed. Anappropriate /NRESTART or /ERESTART commandshould be entered to tell IMS what restart processing

is required. When (DCCTL) is displayed in the message,the DCCTL environment has been initialized.

System actionWaits for /ERESTART or /NRESTART command.

Operator response(master terminal) Enter an /ERESTART or /NRESTART command.

Module:DFSCINB0

DFS0811A UNABLE TO OBTAIN GGGGIGABYTES OF 64-BIT STORAGEFOR THE ACB POOL.REASON=xxxx

ExplanationYou specified the ACBIN64 parameter to create a 64-bit storage pool for ACB members. The size of thestorage request is GGG gigabytes. IMS control regioninitialization attempted to obtain this 64-bit storagepool, but storage was not available for the reasonspecified in xxxx.

System actionIMS initialization continues without the ACB membersin 64-bit storage.

Operator responseThe explanations of the reason codes are in thefollowing z/OS publications:

z/OS MVS Assembler Services Reference IAR-XCT(SA22-7607)z/OS MVS Authorized Assembler Services ReferenceLLA-SDU (SA22-7611)

Determine the appropriate response based on thereason code. If the reason code indicates that therewas not enough storage available, verify the amountof 64-bit storage available and adjust the requestedamount.


Related referencez/OS: IARST64 64-bit storage servicesz/OS: IARST64 return and reason codesRelated information“IMS problem determination” on page 11

Chapter 20. DFS messages, DFS0801I - DFS0850W 299


http://www-01.ibm.com/support/knowledgecenter/SSLTBW_2.4.0/com.ibm.zos.v2r4.ieaa200/iarst64.htm?lang=en

http://www-01.ibm.com/support/knowledgecenter/SSLTBW_2.4.0/com.ibm.zos.v2r4.ieaa900/iarst64.htm?lang=en


DFS812I PERMANENT I/O ERROR ONJOBLIB/LPALIB

ExplanationWhile searching PDS directories for JOBLIB orSYS1.LPALIB, a permanent I/O error occurred.

Programmer responseEnsure that JOBLIB allocation for the region is correct.If it is correct, contact your IMS system programmerfor assistance.

Module:DFSIINl0

DFS813I BLDL FAILED FOR FOLLOWINGJOBLIB/LPALIB

ExplanationWhile searching the PDS directories for JOBLIB orSYS1.LPALIB, modules required to support IMS couldnot be found. Module names follow the message.

Operator response:Notify the system programmer responsible for IMS.

Module:DFSIINl0

Related referencez/OS: BLDL-Build a directory entry list (BPAM)

DFS814I INITIALIZATION FAILED FORFOLLOWING LINEGROUPS

ExplanationWhile initializing the line groups for thecommunications facility of IMS, IMS found that one ormore line groups could not be initialized. A messagelisting the ddnames of the line groups involvedand the reason they could not be initialized followsthis message. Possible reasons for unsuccessfulinitialization include:ddname

Reasonddname.ALLOC

An incorrect device type has been allocated to thisDD statement When the ddname is for a spooldevice, JES SPOOL DATASET (SYSOUT) might beincorrectly specified for at least one DD statementin the line group. This message is issued once for

each DD statement in the line group, even if onlyone DD statement has an incorrect specification.

ddname.DUMMYThe first statement in a line group was specified asDD DUMMY.

ddname.NOFNDThe DD statement was not present.

ddname.NOTSPIMS-issued I/O operations do not support PDSW,HFS, or any other extended-format data sets.

ddname.STORGThere is not enough storage in subpool 0 toinitialize the EXCP process.

ddname.UNITThe DD statement does not point to a valid CTCdevice.

Operator response:(master terminal) Ensure that those line groups notinitialized were intentionally not initialized. If linegroups which should have been initialized were not,bring this message to the attention of the systemprogrammer responsible for IMS.

Module:DFSIINB0

DFS815I UNABLE TO OPEN LINEGROUPS

ExplanationDuring initialization of the control region, it was notpossible to open any communication line groups.The reason might be improper allocation or lack ofallocation for any line groups.

Programmer responseEnsure that line groups are allocated using correctddnames as shown in output from Stage 2 of IMSsystem definition.

Module:DFSIINB0

DFS816A NOP ISSUED TO 7770-3 LINE aaa.REQUEST DID NOT COMPLETE IN15 SECONDS. REPLY 'POST' OR'RETRY'.

ExplanationThe 7770 line with a unit address of aaa had aNOP request issued which failed to complete duringinitialization.

System actionWaits for reply.


http://www-01.ibm.com/support/knowledgecenter/SSLTBW_2.4.0/com.ibm.zos.v2r4.idad500/bldl.htm?lang=en

Operator response:(master terminal) Replies can be uppercase orlowercase. A reply of POST causes the line tobe posted unusable; a reply of RETRY causes theoperation to be retried.

Module:DFSIIO30, DFSXCIC0, DFSXLGI0

DFS817A NOP ISSUED TO 7770-3 LINE aaa.CONTROL IS NOT OPERATIONAL.REPLY 'POST' OR 'RETRY'.

ExplanationThe 7770 control unit with line address aaa is offline.


Operator response:Replies can be uppercase or lowercase. A reply ofPOST causes the line to be posted unusable. If theoperation is to be retried, place the control unit onlinebefore replying RETRY. A reply of RETRY causes theoperation to be retried.

Module:DFSIIO30

DFS818A NOP ISSUED TO 7770-3 LINEaaa. RESULT WAS I/O ERRORcccc,ss,ee,ii. REPLY 'POST' OR'RETRY'.

ExplanationAn I/O error occurred.

In the message text:Code

Meaningaaa

The line control unit addresscccc

The CSW statusss

The sense statusee

The DECB DECERRST fieldii

The IOB IOBINCAM field


Operator response:

Replies can be uppercase or lowercase. A reply ofPOSTcauses the line to be posted unusable; a replyof RETRY causes the operation to be retried.

Module:DFSIIO30

DFS819I YOUR REPLY TO THE LASTMESSAGE WAS INVALID. PLEASETRY AGAIN

ExplanationThe operator gave an invalid reply to one of thefollowing messages: DFS816A, DFS817A, or DFS818A.

Operator response:Wait for the appropriate message above to bereissued, and then retry your reply.

Module:DFSIIO30

Related information“DFS816A” on page 300NOP ISSUED TO 7770-3 LINE aaa. REQUESTDID NOT COMPLETE IN 15 SECONDS. REPLY'POST' OR 'RETRY'.“DFS817A” on page 301NOP ISSUED TO 7770-3 LINE aaa. CONTROL ISNOT OPERATIONAL. REPLY 'POST' OR 'RETRY'.“DFS818A” on page 301NOP ISSUED TO 7770-3 LINE aaa. RESULTWAS I/O ERROR cccc,ss,ee,ii. REPLY 'POST' OR'RETRY'.

DFS0820W PARTITION INITIALIZATIONERROR ENCOUNTERED FORMASTER DATABASE mdbname, DLISTATUS CODE= dlistatus

ExplanationAn error was encountered that prevented theinitialization of all the partitioned data sets.

System actionProcessing continues. The return code is set to 4.

User responseCheck the DBDGEN for errors. Verify that all theHALDB master partition data sets have been correctlydefined.

Module:DFSURPR0

DFS821I NO DATA BASE DIRECTORIESDEFINED


ExplanationAt system definition time, no databases were definedto the system. Therefore, no database directoryinitialization is required.


Module:DFSIIND0

DFS822I NO ALLOCATION FOR DDN'IMSACBx' IN (CTL|DLS) ADDRESSSPACE.

ExplanationThe ACBLIB data sets must be defined in the JCL usedto start IMS. The DDNAMEs used to define ACBLIB areIMSACBA and IMSACBB. x is either A or B, indicatingthe missing JCL DD statement. DLS is included inthis message if the error was detected in the DL/Isubordinate address space. In a DL/I subordinateaddress space environment, both the control regionand JCL must define ACBLIB.

System actionIMS terminates with abend 0071 or 0821.

Programmer responseCheck the JCL to ensure proper allocation per the IMSsystem definition information.

Module:DFSRDB30


DFS823I UNABLE TO OPEN DDN 'IMSACBx'IN (CTL|DLS) ADDRESS SPACE.

ExplanationA permanent I/O error might have occurred duringOPEN. x=A or B depending upon whether IMSACBAor IMSACBB is active. DLS is included in this messageif the error occurred in the DL/I subordinate addressspace.


Programmer responseEnsure that ddname IMSACBx is allocated properlyand that the data set specified at IMS systemdefinition time exists. x=A or B.

Problem determinationCheck the JCL to ensure proper allocation per the IMSsystem definition information.

Module:DFSBIND0, DFSIIND0


DFS824I DFS824I PDS DIRECTORY READERROR DDN 'IMSACB ' RC=xxRSN=yy

ExplanationAn I/O error has occurred while trying to read the PDSdirectory for ddname IMSACBx. The return code fromthe call to the BLDL macro is shown as xx, and thereason code is yy.


Programmer responseCheck the JCL to ensure proper allocation per the IMSsystem definition information.

Problem determinationSee message DFS823I.

Module:DFSBIND0, DFSRDB30

Related referencez/OS: BLDL completion codesRelated information“DFS823I” on page 302UNABLE TO OPEN DDN 'IMSACBx' IN (CTL|DLS)ADDRESS SPACE.IMS abend 0071IMS abend 0821

DFS825I BLDL FAILED FOR ALL DEFINEDDATA BASE DIRECTORIES









ExplanationNo valid directory entries for databases named at IMSsystem definition time could be found on the data setallocated to ddname IMSACB.

System actionIMS terminates with abend 0071 when dynamicresource definition (DRD) is not enabled. When DRDis enabled then IMS continues to restart but does notprocess programs (PDIRs).

Operator response(master terminal) Contact your IMS systemprogrammer.

Programmer responseEnsure that at least one DBDGEN for the definedsystem has been run and that it is placed in theACBLIB data set defined by ddname IMSACB. If DBDsexist in the IMSACB library, validate that the IMSACBlibrary is built at the same IMS level as the IMSexecution library.

Problem determinationMessage DFS826I contains a list of reasons for whichthe directory entries might have been invalid.

Module:DFSRDB30

Related referencez/OS: BLDL completion codesRelated information“DFS826I” on page 303BLDL FAILED FOR FOLLOWING DBDs:IMS abend 0071

DFS826I BLDL FAILED FOR FOLLOWINGDBDs:

or

xxx DBD ERRORS SENT TO JOB LOG

or

xxx DBD ERRORS SUPPRESSED

ExplanationThe first form of this message is repeated as DBDnames are listed that were not found or did not meetrequirements on ACBLIB. A reason follows each name.Name

MeaningNOFND

Not foundNOTPS

A DBD was defined as a PSB at IMS systemdefinition.

NOBUFBuffer size was zero.

ALIASAlias names are not allowed.

NOTDMA PSB was defined as a data management block atIMS system definition.

NOTCPNot compatible

No programs or transactions which use the nameddatabases or PSBs are scheduled for execution byIMS.

In the second form of this message, xxx is the numberof DBD errors.

IMS issues the third form of this message ifyou specified MSG0826=SUPPBLDL in the DFSDFxxxPROCLIB member. DFS826I messages are not sent tothe job log.

System actionIMS continues running if running in either a CTX orCTL type IMS region. IMS abends with abend 0821 ifrunning in a DBB type IMS region.

Programmer responseFor the first form of this message, no action isrequired. No programs or transactions which use thenamed databases or PSBs are scheduled for executionby IMS. For NOTCP, an ACBGEN must be done.

For the second form of this message, see the job logfor all DFS826I messages.

Problem determinationSee the IMS system definition information.







DFS827I DYNAMIC PSB psbname BLDLFAILED-aaaaa

ExplanationThe BLDL for the PSB indicated by psbname in themessage failed for the reason specified by one of thefollowing codes, aaaaa in the message text:Name

MeaningIOERR

I/O error reading the directoryNOFND

Member not foundCONCT

Member is in first concatenation.ALIAS

Member is an alias.NOTPS

Member is not really a PSB.NOBUF

No buffer size was available.NOTCP

Not compatible


Programmer responseNo programs or transactions that use the nameddatabases or PSBs are scheduled for execution byIMS.

Problem determinationSee the IMS system definition information.

Module:DFSDBLI0

DFS828I WARNING: xxxx POOL NOTCREATED

ExplanationThe pool named xxxx has not been created becauseboth the IMS system definition and override values onthe EXEC statement are zero for the named pool.

System actionIMS continues initialization, but the named pool doesnot exist during the IMS run.

Programmer responseMake sure that the named pool is not needed for theIMS installation configuration.


Module:DFSDOBI0, DFSIINS0


DFS829I NO PROGRAM DIRECTORIESDEFINED

ExplanationAt system definition time, no programs were definedto the system. Therefore, no program directoryinitialization was required. Also, no database directoryinitialization is done.

Problem determinationCheck system definition Stage 2 output.

Module:DFSIIND0

DFS830I BLDL FAILED FOR FOLLOWINGPSBs;

or

xxx PSB ERRORS SENT TO JOB LOG

or

xxx PSB ERRORS SUPPRESSED

ExplanationThe first form of this message is repeated as PSBnames are listed that were not found or did not meetrequirements on ACBLIB. A reason follows each name.See message DFS826I.

For the second form of this message, more than tenPSB errors were found; xxx is the number of PSBerrors found.


System actionIMS continues running if running in either a CTX or CTLtype IMS region. IMS terminates with abend 0821 ifrunning in a DBB type IMS region.

Programmer responseFor the first form of this message, note that noprograms or transactions that use the named PSB arescheduled for execution by IMS.

For the second form of this message, see the job logfor all DFS830I messages.

IMS issues the third form of this message ifyou specified MSG0830=SUPPBLDL in the DFSDFxxxPROCLIB member. DFS830I messages are not sent tothe job log.


Related referencez/OS: BLDL completion codesRelated information“DFS826I” on page 303BLDL FAILED FOR FOLLOWING DBDs:

DFS831I BLDL FAILED FOR ALL DEFINEDPROGRAM DIRECTORIES

ExplanationNo valid directory entries for programs defined duringIMS system definition were found in the ACBLIB dataset allocated to ddname IMSACB.

During initialization, the PSBs defined during IMSsystem definition, or defined in the CICS programdirectory (PDIR), are loaded and validated. At leastone valid PSB must be found in ACBLIB. If no PSBs, orno valid PSBs are found, message DFS831I is issued.


Operator response(master terminal) Make sure that no message regionswere going to be run. If yes, contact your IMS systemprogrammer for assistance.

Programmer responseCheck the JCL for proper allocation. In addition,ensure that at least one PSBGEN for a non-DOPT PSBwas run, and that the PSB is placed in the ACBLIB dataset defined by ddname IMSACB.

Module:DFSRDB30


DFS0832I ABEND Uwwww REASON CODExxxx yyyy PARTITION | DATABASEzzzzzzzz

ExplanationUse this message to assist in debugging problems thatcause an IMS abend. This message is issued when anabend condition is detected by module DFSDLA00 orDFSFDMP0. This condition can be caused by either:

• A nonzero return code on a partition selection orvalidation.

• A pseudoabend set by module DFSDLR00,DFSDDLE0, DFSDXMT0, DFSDLD00, DFSRBOI0,DFSFXC50, or DFSRCHB0.

In the message text:wwww

The pseudoabend code.xxxx

One of the following:

• The reason code for HALDB abends, or N/A fornon-HALDB abends.

• One of these detected IMS abends:

0776088033033498

For these abends, the reason code is yyyy and itis related to a problem that was detected whileprocessing a HALDB.

yyyyIf xxxx (the abend) is not one of the above, thevalue of yyyy is N/A. Otherwise, it is one of thefollowing reason codes:4001

No more partitions are defined4014

A HALDB was defined as non-registered in theDFSDFxxx PROCLIB member but was found tobe registered in the RECON data set.

4020DB authorization error (data unavailable)

4025DB unload action error

4026DB initialization action error




4032Partition unavailable due to a migrated dataset.

4059The access level is not compatible with theintent level

8001Target partition requires initialization

8010Target partition not found

8011An invalid key for a partition was found.

8031Open DMB failure

8051User partition selection failed

C001Non-partitioned DB access

C002Partitions not active

C003Partition stopped

C004Partition structure terminating

C005Partition structure not initialized

C006Partition structure rebuild failed

C009ILDS DSG not provided

C010Unusual structure status

C030Invalid authorization reason code

C031Partition open error

C040Invalid partition DDIR

C041Invalid partition set operation

C042Unable to allocate PSETE storage

C043Invalid partition set selection action

C050User selection exit not invoked

C060Invalid function code

C070Buffer handler byte locate failed

C071Buffer handler locate by key failed

C072Error occurred during processing against theindirect list data set (ILDS).

C073Buffer handler mark altered failed

C074Buffer handler byte locate & mark alteredfailed

C075IRLM root lock request (GRID) failed

C076Request to obtain BCB storage (BCBGET) failed

C077Refresh OLR cursor request failed

PARTITION | DATABASEIf HALDB, PARTITION. If non-HALDB, DATABASE.

zzzzzzzzThe DBD name for one of these:

• HALDB partition• HALDB master• Non-HALDB database

or NOTAPPLI if no DBD is available.

System actionThe application program is terminated.

Programmer responseCorrect the situation that caused the application toterminate.

Module:DFSDLA00, DFSFDMP0

DFS833I INSUFFICIENT (CTL PRIVATE|COMMON SYSTEM) MEMORY FORRESIDENT INTENT LISTS

ExplanationThere was not enough storage to make intent listsresident. The storage requested was either for spacewithin the region or for space in the common systemarea (CSA). The latter case implies that the DL/Isubordinate address space option has been selected.

System actionNo intent lists are made resident.


Programmer responseIncrease the IMS region size if the message specifies"private".

Module:DFSIIND0

DFS834I INSUFFICIENT (COMMONSYSTEM|DLS PRIVATE) MEMORYFOR RESIDENT PSBS

ExplanationThere was not enough storage to make PSBs resident.The storage requested was either for space within thecommon system area (CSA) or from DL/I subordinateaddress space private memory (DLS).

System actionNo PSBs are made resident.

Programmer responseEither provide more space in the area where the spaceis obtained or make fewer PSBs resident.

Module:DFSIIND0

DFS835I INSUFFICIENT (COMMONSYSTEM|DLS PRIVATE) MEMORYFOR RESIDENT DMBS

ExplanationThere was not enough storage to make specified datamanagement blocks resident. The storage requestedwas either for space within the common system area(CSA) or from DL/I subordinate address space privatememory (DLS).

System actionNo data management blocks are made resident.

Programmer responseEither provide more space in the area where the spaceis obtained or make fewer data management blocksresident.

Module:DFSIIND0

DFS836I THE FOLLOWING SHARED DMBsNOT FOUND IN THE LIBRARY

ExplanationWhile initializing database directories, an entry for oneor more shared index data management blocks couldnot be located in the ACBLIB. The affected entries arelisted after the header.

System actionAll listed databases are stopped permanently andinitialization continues.

Operator response:Notify the IMS system programmer of the condition.

Programmer responseReconstruct the affected entries in the ACBLIB, usingthe IMS ACB utility.

Module:DFSIIND0

DFS837I SHARED INDEX NOT DEFINEDDMB dbdname

ExplanationThe named database was part of a shared index DMBin the ACBLIB but had not been defined to the IMSsystem during the IMSGEN process.

System actionAll databases forming the shared index group arepermanently stopped and initialization continues.


Programmer responseCorrect the affected entries in the ACBLIB.

Module:DFSIIND0

DFS838I I/O ERROR READING SHAREDINDEX LIST FOR DMB dbdname

ExplanationThe named database was a shared index. While tryingto read the index list from the ACBLIB, a permanentI/O error occurred.

System actionThe affected database is permanently stopped, andinitialization continues.

Operator response:


Notify the system programmer of the condition.

Programmer responseCorrect the condition causing the I/O error.

Problem determinationCheck the system console or the log record, or both,for information about the cause of the I/O error.


DFS0839I DATA BASE BUFFER POOL NOTPURGED

ExplanationA database buffer was not purged after an abendbecause:

• DL/I was active at time of abend.• No STAE work area was provided.• The PSB had update intent but the log was DD

dummy.• The buffer handler gave a bad return code on the

purge call.• The GETMAIN for save areas failed.• The buffer handler was not in storage.


Module:DFSFLST0

DFS0840I INDEX ERROR (dbdname) (statuscode) (first 45 bytes of key)

ExplanationAn error condition was encountered by the indexmaintenance function. The message shows thedbdname, the status code, and the first 45 bytes ofthe key. The status code can be NE, NI, NO, or BLANK.

CodeMeaning

NEAn attempt was made to delete an index record,but the record did not exist. This might be a validcondition if the secondary index was processedas a database and some secondary index entrieswere deleted. If the source segment is deleted andits index entry is not present, the NE status codeis the result. The DFS0840I message is sent for

information purposes, but since this might be avalid condition, a BLANK status code is returned tothe application program. See the description of theNE status code in the DL/I status code information.

You can suppress the DFS0840I messageby specifying ISSUE840=NO on an OPTIONSstatement in the DFSVSMxx PROCLIB member.

NIEither a data set could not be opened or there wasa duplicate segment in a unique secondary index.If a data set could not be opened, the messageis preceded by a DFS0730I message and followedby a 0826 pseudoabend or real abend. If thereis no preceding DFS0730I message, then there isa duplicate segment in a secondary index. If it ispossible to back out prior changes for the call,this message is suppressed. Only the NI statusis returned to the application program. If it isnot possible to back out other changes for thecall, or if ISSUE840=YES has been specified onan OPTIONS statement in the DFSVSMxx member,this message is displayed and is followed by a0828 pseudoabend or real abend. For additionalinformation, see the descriptions of the NI statuscode in the DL/I status code information.

The conditions which do not support backing outprior updates for the call are:

• The execution environment is batch and does notuse a DASD log with BK0=YES specified on thePARM field of the JCL EXEC statement.

NOAn I/O error was detected. This message shouldbe preceded by a VSAM error message whichdescribes the error. A database recovery mightbe necessary. The NO status is returned to theapplication program. If it is possible to back outprior changes for the call (see details below), thismessage is suppressed. If it is not possible toback out prior changes for the call, this message isdisplayed and is followed by a 0826 pseudoabendor real abend. See the description of the NO statuscode in the DL/I status code information.

BLANKAn unexpected return code was received from acall to the buffer handler. In this case, the messageshould be accompanied by a 0825, 0826, or 0829pseudoabend or real abend.

System actionDescribed above.


Programmer responseSee the status code descriptions or abendexplanations.


Module:DFSDXMT0

Related referenceDL/I status codes (Messages and Codes)Related information“DFS0730I” on page 257UNABLE TO OPEN OR CLOSE DATASET WITHDDNAME ddname FOR REASON x, yy, zDATABASE dbdname programidIMS abend 0825IMS abend 0826IMS abend 0829“IMS problem determination” on page 11IMS messages and codes problemdetermination is accomplished by usingprocedures established by IBM.

DFS0841I SAF INTERFACE ERROR. SAFRC=nn, RACROUTE=racf-function,RETURN=(yy,zzz)

ExplanationA RACROUTE call received a failing return code(RC=nn) from the SAF interface during initializationprocessing. The failing RACROUTE function was racf-function. The security product return code is yy, andthe reason code is zzz.

System actionIf the error occurs in the control region, IMSinitialization terminates with an abend 0071. If theerror occurs in the DLISAS region, IMS initializationterminates with an abend 0029.

Programmer responseIf this a problem with the installation of RACF,analyze the return and reason codes for racf-functionin z/OS Security Server RACROUTE Macro Reference(SA22-7692).

To bypass all RACF checking for online IMS systems,modify the z/OS program properties table forDFSMVRC0 as described in z/OS MVS Initialization andTuning Reference (SA22-7592).

Problem determination:1,3,4,6

Module:DFSXRAC0

Related referencez/OS: RACROUTE return codes and reasoncodesz/OS: z/OS system tailoringRelated informationIMS abend 0029“IMS problem determination” on page 11IMS messages and codes problemdetermination is accomplished by usingprocedures established by IBM.

DFS0842I OSAM DATASET CANNOTBE EXTENDED, REASON=X,Z,dbdnameddname, dsname

ExplanationOSAM was unable to extend the named data set.A two line message each numbered DFS0842I isissued. The first line indicates why the data set is notextendable. It also contains the dbdname. The secondline contains the ddname and the dsname.

In the message text:X

The reason code that identifies the error conditionZ

The hexadecimal error subcodedbdname

The database nameddname

The data definition namedsname

The data set name

One of the following reason codes (X) identifies theerror condition. The first word in the description is thelabel name where the error was detected. The firstword in the description is the label name where theerror was detected. Conditions 1, 2, and 3 occur onlyin a data sharing environment when the data set wasextended on another subsystem. The subsystem withthe error was unable to perform a similar extension.X reason code

Error condition1

LCREAT10: Pseudo data set extension failed.2

DSXT0350: The volume serial number for the newextent does not match the volume serial numberbroadcast by the extending subsystem.






http://www-01.ibm.com/support/knowledgecenter/SSLTBW_2.4.0/com.ibm.zos.v2r4.ichc600/ich2c6_Return_codes_and_reason_codes1.htm?lang=en


http://www-01.ibm.com/support/knowledgecenter/SSLTBW_2.4.0/com.ibm.zos.v2r4.ieae200/ieae20011.htm?lang=en


3DSXT0360: An error occurred while processing anOSAM TCLOSE function for the data set. A TCLOSEis the closing and reopening of the data set toacquire new extent information.

4Not used.

5

LCREAT30: An attempt to allocate another extentfor the data set using the OSAM end-of-volumeroutine failed. The data set could not be extended.

6LCREAT40: An attempt to obtain a buffer for therequested block failed. This problem might havebeen caused by I/O errors on one of the OSAMdata sets that share the same set of buffers.

7LCREAT70: An I/O error was received during theformat logical cylinder operation.

The following subcodes (Z) identify error conditionsdetected by DFSAOSF0 and DFSAOS10. The Z subcodeis returned in DCBWRK1+3, and is used to identifyerror conditions associated with reason code 5.Z subcode (hex) - set by module DFSAOSF0:

Meaning01

Data control block (DCB) marked unusable.02

DCB is DD dummy data set.03

DCB is not open.04

Data extension block (DEB) has reached maximumsize.

05Data set not extendable, or secondary allocation isnot permitted.

06Insufficient volumes.

07An error occurred while locating the currentvolumes extents. The return code from the OSPLITsubroutine is 4 in register 15.

08An error occurred while converting an OSAM dataextension block (DEB) to an MVS DEB. The returncode from the OSDEB subroutine is 4 in register15.

09An error occurred while constructing an OSAMDEB. The return code from the OSAMDEBsubroutine is 4 in register 15.

0ADEB/DCB validation check failed.

0BThis call is not for an EOV call request.

0CAn error occurred while locating the currentvolumes extensions. The return code from theOSPLIT subroutine is 8 in register 15.

0DAn error occurred while converting an OSAM dataextension block (DEB) to an MVS DEB. The returncode from the OSDEB subroutine is 8 in register15.

0EAn error occurred while constructing an OSAMDEB. The return code from the OSAMDEBsubroutine is 8 in register 15.

0FError releasing a captured unit control block (UCB).

Z subcode (hex) - set by module DFSAOS10:Meaning

20End-of-volume (EOV) is already pending.

21I/O error was encountered

22DCB was DD dummy data set. It was detected byDFSAOS10.

23DCB was not open. It was detected by DFSAOS10.

24Error acquiring new extent.

System actionFor condition 1, 2, or 3, the application programpseudoabends with abend 0842. For the otherconditions, processing continues and messageDFS0845I might follow.

Operator response:(master terminal) Notify the IMS system programmeror database administrator of the condition.

Programmer responseTake the following actions:

• If data set extend error 1, 2, or 3 occurs in a datasharing environment, ensure that all the volumes of


the database are shared among the subsystems andthat a path exists to all volumes.

• If data set extend error 5 occurs, add additionalspace or reduce the number of DASD extents,by reorganizing the database or recovering thedatabase with larger space parameters. After anextend error 5, if an OSAM data set cannot beopened because it extends beyond the OSAM-supported maximum number of extents, you mightneed an intermediate utility step when opening thedata set to allow the system to release the unusedextents. For example, use an ADRDSSU job withRELEASE, or a copy utility such as IEBGENER witha dummy input data set and the OSAM data setas output, specifying DISP=MOD and SPACE=(xxx,(primary,secondary),RLSE). For information aboutextends, see Using OSAM as the access method(Database Administration).

• If I/O errors were encountered, follow the actionsdefined in message DFS0451I or DFS0451A.


Module:DFSDBH40 and DFSDBH4M

Related information“DFS0451I” on page 159modname, dbdname, ddname, i/o error, decbfield“DFS0451A” on page 159modname, dbdname, ddname, i/o error, decbfieldIMS abend 0842“IMS problem determination” on page 11IMS messages and codes problemdetermination is accomplished by usingprocedures established by IBM.

DFS0843I dbname MAXIMUM NUMBEROF BYTES REACHED,DDNAME=ddname

ExplanationThe data set group of an HDAM, HIDAM, PHDAM, orPHIDAM database has reached its maximum capacity.

For non-HALDB databases, the maximum size of adata set is:

• If the data set is VSAM, 4 GB.• If the data set is OSAM, 4 GB for a data set with an

odd-length block size and 8 GB for a data set with aneven-length block size.

4,294,967,295 bytes (4 GB) is the largest absolutenumber for a fullword. A non-HALDB OSAM database

with an even block size doubles the possible storagewithin a fullword to 8,589,834,591 bytes (8 GB).

For HALDB database partitions, the maximum size of adata set is:

• If the data set is VSAM, 4 GB.• If the data set is OSAM, 4 GB or 8 GB.

System actionAn attempt to obtain space is made by examiningbitmaps. The search starts at the end of the dataset and works up to the start. If this is unsuccessful,message DFS0844I is issued and the transactionterminates with pseudoabend 0844.

Programmer responseReorganize the database to consolidate and reclaimspace. If this does not work, consider taking one of thefollowing actions:

• For a HALDB database, split the partition into two ormore partitions.

• For a HALDB database that uses VSAM data sets or4-GB OSAM data sets, consider using 8-GB OSAMdata sets.

To use 8-GB OSAM data sets, the HALDB databasemust be registered to DBRC as supporting 8-GBOSAM data sets. HALDB databases that use 8-GBOSAM data sets cannot be reorganized with theHALDB Online Reorganization (OLR) function

• For a non-HALDB database, convert the database toHALDB.

• For a non-HALDB database that uses VSAM datasets, change the database to use OSAM data setswith an even block size.

• Use multiple data set groups.

Module:DFSGGSP0

Related information“DFS0844I” on page 311modulename dbname DATASET FULL,DDNAME=ddnameIMS abend 0844

DFS0844I modulename dbname DATASETFULL, DDNAME=ddname

ExplanationThe named database data set has no more space inwhich to place data and precedes pseudoabend 0844.One of the following occurred:


http://www.ibm.com/support/knowledgecenter/SSEPH2_15.1.0/com.ibm.ims15.doc.dag/ims_useosamaccess.htm#ims_useosamaccess

http://www.ibm.com/support/knowledgecenter/SSEPH2_15.1.0/com.ibm.ims15.doc.dag/ims_useosamaccess.htm#ims_useosamaccess



• An attempt to insert a new record into the nameddata set failed because no space was available.

• An insert call was issued to a data set that wasdefined as DD DSNAME=NULLFILE or DD DUMMY.

System actionThe application program is terminated withpseudoabend 0844. For HISAM or index databases,the database is stopped.

Operator responseFor HISAM or index databases, you must issue a /START command to restart the database.

(master terminal) Notify the IMS system programmeror database administrator of the condition.

Programmer responseThe backout of uncommitted changes after anypseudoabend 0844 restores the database to aconsistent and usable state. However, inserts cancause the same condition to occur. While offline (usingthe /DBR command), you must copy the database toa larger space allocation. Then make the databaseavailable to the online region using the /STARTcommand.


ModuleDFSDVSM0, DFSDDLE0


DFS0845I dbname DATASET LIMITREACHED, DDNAME=ddname

ExplanationAn attempt to create another block in an HDAM,HIDAM, PHDAM, or a PHIDAM database failed,because additional extents could not be allocated oran I/O error was encountered while creating additionalblocks.

System actionThe bitmaps are searched to find available spacewithin the database. If space is found, it is used and

processing continues. If space is not found, messageDFS0844I is issued.


Programmer responseIf additional extents cannot be allocated, additionalvolumes can be added or the database can bereorganized. If an I/O error was encountered, andsufficient space was found using the bitmap search,migrate the database to another physical location toavoid additional I/O errors.

Module:DFSGGSP0

Related information“DFS0844I” on page 311modulename dbname DATASET FULL,DDNAME=ddname

DFS846I CONTROL CARD ERROR, {NAMEEXCEEDS 8 BYTES|EXCESSIVEPARAMETERS|MISSING PAREN|SETS OF PARAMETERS > 100|BADTIME CARD|I/O INVALID}

ExplanationA control statement was in error.

System actionDFSIST40 terminates abnormally.

Programmer responseCheck the control statements for the specified error.Correct the error, and resubmit the job.

Module:DFSIST40

DFS847I UNRECOGNIZED CONTROL CARDBYPASSED

ExplanationA control statement contained an invalid keyword. Theother control statements are processed, and the jobcontinues.

System actionDFSIST40 continues execution.



Programmer responseCheck the control statements. Correct the error, andrerun the job if necessary.

Module:DFSIST40

DFS848I CONTROL CARD ERROR, NOOUTPUT SELECTED

ExplanationNo messages met the selection criteria of the controlstatements.

System actionDFSIST40 terminates normally.

Programmer responseCheck the JCL and control statements, and determineif there should have been output. Correct the error,and rerun the job if necessary.

Module:DFSIST40

DFS849I NO OUTPUT DATASETSREQUESTED, EOJ

ExplanationThe statistics program found that neither IMSLOG0 norIMSLOGP was specified.

System actionDFSIST40 terminates.


Module:DFSIST40

DFS0850W PARTITIONED DATABASESTRUCTURE INITIALIZATIONERROR ENCOUNTERED FORDATABASE mdbname

ExplanationDatabase structure initialization failed for the databaseidentified by mdbname. For additional information, seethe accompanying message DFS0415W, if present.


User responseCheck the JCL for correct RECON data sets andDFSVSAMP DD card. After you correct the error,resubmit the job.

Module:DFSURPR0

Related information“DFS0415W” on page 144PARTITIONED DATABASE INIT | TERM |START EXCEPTION CONDITION - FUNC= ffffffff,DBNAME= dddddddd, PARTNAME= pppppppp,REASON= rr


Chapter 21. DFS messages, DFS0851W - DFS0900A


DFS0851W PARTITIONED DATABASESTRUCTURE TERMINATIONERROR ENCOUNTERED FOR DATABASE mdbname

ExplanationThe Partition Structure Manager was unable toterminate the database structure for the databaseidentified by mdbname. For additional information, seethe accompanying message DFS0415W, if present.


Module:DFSURPR0

Related information“DFS0415W” on page 144PARTITIONED DATABASE INIT | TERM |START EXCEPTION CONDITION - FUNC= ffffffff,DBNAME= dddddddd, PARTNAME= pppppppp,REASON= rr

DFS852W REPLACE IGNORED DUE TOFAILURE OF VERIFY

ExplanationA VERIFY operation preceding this REP operation didnot compare correctly and caused this REP to beignored.


Programmer responseCorrect input control statement data for the VERIFY,and resubmit the job.


Module:

DFSUCF00, DFSURGP0, DFSURGS0, DFSURG10,DFSURPR0


DFS853A MISSING/INVALID KEYWORDkeyword FOR FUNCTION ff

ExplanationA control program detected a missing keyword thatwas required.


Programmer responseSupply the required keyword and data, and resubmitthe job. Do not perform a Utility Control Facility restart.

Problem determination1, 2, 8, 11, 36. Also, if running under theUtility Control Facility, rerun the job with aFUNCTION=OP,MSGNUM=853 control statement inthe DFSYSIN data set. Supply a SYSUDUMP DDstatement to this step.

Module:DFSUCF00, DFSURGP0


DFS854A CONTROL STATEMENT ERROR-INVALID/MISSING VALUE FORKEYWORD keyword

ExplanationA control program detected a missing value for akeyword or determined that the value supplied on thekeyword was incorrect.



Programmer responseCorrect the data, and resubmit the job.

Problem determination1, 2, 8, 11, 36. Also, if running under theUtility Control Facility, rerun the job with aFUNCTION=OP,MSGNUM=854 control statement inthe DFSYSIN data set. Supply a SYSUDUMP DDstatement to this step.

Module:DFSUCF00, DFSURGP0, DFSURGS0, DFSURPR0


DFS855I PRECEDING CARDS WERE USEDTO FORM REQUEST nnnn

ExplanationThe control statements listed immediately before thismessage were used to form a single request of theUtility Control Facility.


Module:DFSUCF00, DFSURGP0, DFSURG10

DFS856A UNABLE TO BUILD CONTROLBLOCKS FOR DATA BASE dbdnameFOR FUNCTION ff

ExplanationThe issuing program requested construction of controlblocks for the named database. The request was notsuccessfully completed.

System actionThe job terminates.

Programmer responseEnsure that a valid DBD exists for the named database,and resubmit the job.


Module:DFSURGP0, DFSURGS0, DFSURPR0


DFS857I MISSING OR INVALID CONTROLDATASET

ExplanationThe issuing program attempted to read the inputcontrol data set generated by the DatabasePrereorganization utility (DFSURPR0). One of thefollowing conditions occurred:

• You did not provide a control data set.• The control data set identified was not present in thefirst block of the control data set.

• The control data set did not contain the number ofblocks indicated in the first block of the control dataset.

Programmer responseEnsure that a valid control data set is providedto the issuing program. Rerun the DatabasePrereorganization utility, if necessary.


Module:DFSURGP0, DFSURGS0, DFSURG10


DFS858A BUFFER HANDLER RETURNEDAN ERROR CODE OF cc FORFUNCTION ff

ExplanationThe issuing program received a nonzero return codefrom the buffer handler. The meaning of this returncode can be found in the PST DSECT in the field


labeled PSTRTCDE. For information about bufferhandler return codes, see the IMS return code andfunction code information.

System actionProcessing terminates with nonzero return code.

Programmer responseCorrect any errors noted by the return code, andresubmit the job.


Module:DFSURGP0, DFSURGS0

Related referenceReturn and function codes associated withthe external subsystem support (Messages andCodes)Related information“IMS problem determination” on page 11IMS messages and codes problemdetermination is accomplished by usingprocedures established by IBM.

DFS859A DL/I RETURNED AN ERROR CODEOF return code FOR FUNCTION ff

ExplanationThe issuing program received an unexpected returncode after a DL/I call.


Programmer responseCorrect any errors indicated by the return code, andresubmit the job.




DFS860A DUPLICATE INDEX ENTRY followedby one or more lines containinginput record in hexadecimal andEBCDIC format

ExplanationThe issuing program found an input record from theinput work file that attempted to create a duplicateindex entry where duplicate entries were not definedfor the index field named in the input record.


Programmer responseEither redefine the index relationship so that theindex violation is removed, or change the databaserecord that caused the duplicate entry creation to beattempted. Then resubmit the job.


Module:DFSURGP0


DFS861I number input-control-card

ExplanationThe issuing program is displaying an input controlstatement provided for it. Numbers are assignedsequentially for reference by subsequent errormessages that might be generated.

Programmer responseVerify that the information displayed is consistent withthe entered information.


Module:

Chapter 21. DFS messages, DFS0851W - DFS0900A 317




DFSURGP0, DFSURGS0, DFSURPR0Related information“IMS problem determination” on page 11IMS messages and codes problemdetermination is accomplished by usingprocedures established by IBM.

DFS862I DBS=databasename,segmentname

ExplanationThis message might be issued more than onetime to provide a list of segments to be scannedby the Database Scan Utility (DFSURGS0). If anOPTIONS=(PUNCH) control statement was providedto the program issuing the message, the portion ofthis message beginning with the characters DBS arewritten to SYSPUNCH.

Programmer responseThe Database Scan Utility (DFSURGS0) must be runfor each of the databases indicated by the scan listprovided by this message.


Module:DFSURPR0


DFS863I DUPLICATE NAME ON INPUTCONTROL CARD, number

ExplanationThe issuing program found a database name thatappeared on the preceding input control statement(indicated by number).

Programmer responseCorrect the input control statement preceding themessage, and resubmit the job.


Module:DFSURPR0



DFS864W DBR AND/OR DBIL CONTROLREQUESTS MISSING FORFUNCTION ff

ExplanationThe issuing program read and interpreted all thecontrol statement requests from the SYSIN (DFSYSINfor Utility Control Facility) data set. After analysisof the control data set, it was found that noreorganizations or initial loads were requested.Although this is possible under the Utility ControlFacility, it is an error when executing the DatabasePrereorganization utility (DFSURPR0).

System actionIf running under UCF, processing continues; otherwise,processing terminates with a nonzero return code.

Programmer responseIf running under the Utility Control Facility, ensurethat this is correct operation. If not, correct, or ifrunning the Database Prereorganization utility, supplythe required control statements, and resubmit the job.Do not attempt a restart. If the output is correct, nofurther action is required.

Module:DFSURGS0, DFSURPR0

DFS865I UNABLE TO CONSTRUCT ACONTROL LIST ENTRY FORFUNCTION database-name1segment-name1 database-name2segment-name2

ExplanationThe issuing program was attempting to construct acontrol list entry for the logical relationship that wasdefined to exist between the above-named database-and segment-names. The definition was not verified inthe control blocks available to DL/I.

Programmer responseEnsure that valid DBDs are available to define theindicated logical relationship.


Module:DFSURPR0



DFS866I NORMAL PROGRAMTERMINATION number

ExplanationThe issuing program terminated normally. number, ifpresent, is the number of input work data set recordsprocessed by the issuing program.


Module:DFSURGP0, DFSURGS0, DFSURG10, DFSURPR0


DFS867I UTILITY CHECKPOINT, pgm-namechkpt-# volume-serial

ExplanationThe issuing program completed a checkpoint at oneof the intervals specified by the user. The name ofthe program issuing the message and the checkpointnumber are known. The volume serial number that thecheckpoint record was written to is also shown.

Operator response:Record the checkpoint number and volume serialnumber in case a restart action must be requested.




DFS868I (INPUT|OUTPUT) VOLUMES:volser1, volser2, etc..

ExplanationThis message is issued one or more times to displaythe volume serial identifiers of the volumes used

to contain the INPUT/OUTPUT work data set of theissuing program.


Module:DFSURGS0


DFS869A SEGMENT segment-name WASNOT FOUND IN THE CONTROLBLOCKS FOR FUNCTION ff

ExplanationThe issuing program was unable to locate the controlblocks for the named segment. The segment waseither listed on an input control statement, or on theinput control data set.


Programmer responseEnsure that valid DBDs are available for the suppliedinput control statements or control data set, or both,and resubmit the job.


Module:DFSURGS0


DFS871E error_type ERROR ENCOUNTEREDLOADING ILDS WITH


DDNAME=ddname RC= nnnnnnnnREASON= yyyyyyyy

ExplanationModule DFSURIT0 encountered an error during ILDSdata set processing for the ILDS identified by ddnamewhile migrating to a HALDB.

In the message text:error_type

Describes the error encountered. The possibleerror types are:

ABENDDSPSERVFREEMAINGETMAINLOADSORTVSAM

ddnameThe ILDS that encountered the error.

nnnnnnnnThe return code found in register 15 when theerror was encountered. If error_type is ABEND, thisfield is the abend code.

yyyyyyyyThe reason code; if the error type is ABEND, RC isblank.

System actionProcessing terminates with return code 8. The affectedILDS is marked "Recovery Needed" in RECON.

Programmer responseRun the ILDS/INDEX Rebuild Utility (DFSPREC0) torebuild the ILDS identified by ddname.

Problem determination:2, 3, 8, 36. Not a valid message for UCF

Module:DFSURGL0


DFS872I DATA BASE NOT SCANNED,database-name

ExplanationThe named database was not scanned. DFS873I isissued before this message.


Module:DFSURGS0

Related information“DFS873I” on page 320SEGMENT NOT SCANNED, database-namesegment-name“IMS problem determination” on page 11IMS messages and codes problemdetermination is accomplished by usingprocedures established by IBM.

DFS873I SEGMENT NOT SCANNED,database-name segment-name

ExplanationThe issuing program found one or more of thefollowing errors when checking the control blocks forthe named segment:

1. The named segment was not found in the controlblocks for the named database,

2. The named segment does not participate in anylogical relationships with any of the segments in thedatabases listed in the control data set as beinginitially loaded or reorganized.

Programmer responseEnsure that valid DBDs are available for the suppliedcontrol statements or control data set, or both.


Module:DFSURGS0


DFS874I FUNCTION REQUEST(STATISTICS|STATUS) DEFAULTSFOLLOWED BY AN *

ExplanationThe Utility Control Facility has prepared a list of all therequested functions along with the defaults that will


be used on this execution. This message is followed bymessages DFS875I and DFS876I.



Related information“DFS875I” on page 321FUNCTION functional utility name REQUESTEDBY FUNCTION=ff ON REQUEST nnnn“DFS876I” on page 321keyword=value * keyword=value * etc..“IMS problem determination” on page 11IMS messages and codes problemdetermination is accomplished by usingprocedures established by IBM.

DFS875I FUNCTION functional utility nameREQUESTED BY FUNCTION=ff ONREQUEST nnnn

ExplanationThe named utility was requested for execution by acontrol request with a keyword of FUNCTION=ff, andthe control statement request sequence was nnnn.




DFS876I keyword=value * keyword=value *etc..

ExplanationThis message is issued one or more times to list therequested or defaulted keyword, and values for eachrequested function of the Utility Control Facility.

Important: The defaults for the message are from aFUNCTION=OP statement or UCF only.


Module:DFSURG10


DFS877A DUPLICATE RECORD FOR LOGICALPARENT (followed by one or morelines containing input records inhexadecimal and EBCDIC format)

ExplanationThe issuing program found a type 00 input workdata set record that was for the same occurrenceof a logical parent/logical child pair as a previousinput work data set record. Only one type 00 recordcan exist for a concatenation of a logical child andlogical parent segment. This condition could be causedby supplying as input to the issuing program workdata sets that were generated by multiple runs of adatabase initial load reorganization, or scan.

Programmer responseThe result of prefix resolution is invalid. Determinethe cause of the incorrect DFSURWF1 record. Theserecords should be analyzed using the DFSURWF1DSECT from the assembly of prefix resolution,DFSURG10, or IMS DSECTS module, DFSADSCT. IfDBIL is used in PREREORG, then the logical parentconcatenated key begins at offset X'19'. If DBR isused in PREREORG, then the LPARENT old addressalso begins at offset X'19'. The RBA address of thissegment is at offset X'0C' in the DFSURWF1 record.

Ensure that only work data sets from databasescurrently being initially loaded, reorganized, orscanned are supplied as input to the issuing program.


Module:DFSURG10



DFS878W CAUTION-NO LOGICAL CHILDRECORD FOUND FOR THELOGICAL PARENT RECORD(followed by one or morelines containing input records inhexadecimal and EBCDIC format)

ExplanationThe issuing program expected to find one or moretype 10 records for the type 00 input work dataset record displayed. A type 00 record is generatedfor a logical parent. A type 10 record is generatedfor each of its logical children. This condition couldbe caused by not supplying as input to the issuingprogram all work data sets that were generated by thedatabases currently being initially loaded, reorganized,or scanned. Because it is not necessary for logicalchildren to actually occur for each logical parent, thismessage is issued as a caution.

Prefix resolution might be invalid if this message isissued. It is also invalid if the user intended to loador reload the logical children belonging to the logicalparent.


Programmer responseEnsure that all work data sets are supplied as input.See DFS877A for information about the DFSURWF1records.


Module:DFSURG10

Related informationDFS877ADUPLICATE RECORD FOR LOGICAL PARENT(followed by one or more lines containing inputrecords in hexadecimal and EBCDIC format)“IMS problem determination” on page 11IMS messages and codes problemdetermination is accomplished by usingprocedures established by IBM.

DFS879A NO LOGICAL PARENT RECORDFOUND FOR LOGICAL CHILD

RECORD (followed by one or morelines containing input records inhexadecimal and EBCDIC format)

ExplanationThe issuing program expected to find a type 00 recordfor the type 10, 20, or 30 input work data set recorddisplayed. A type 00 record is generated for a logicalparent. A type 10 record is generated for each ofits logical children. Type 20 and type 30 records aregenerated for the logical twin forward and backwardpointers, respectively, of each logical child.

Programmer responseSame action as specified in message DFS877A.


Module:DFSURG10

Related information“DFS877A” on page 321DUPLICATE RECORD FOR LOGICAL PARENT(followed by one or more lines containing inputrecords in hexadecimal and EBCDIC format)“IMS problem determination” on page 11IMS messages and codes problemdetermination is accomplished by usingprocedures established by IBM.

DFS880A NO LOGICAL CHILD RECORDFOUND FOR LOGICAL TWINRECORD (followed by one or morelines containing input records inhexadecimal and EBCDIC format)

ExplanationThe issuing program expected to find a type 10 recordfor the type 20 or 30 input work data set recorddisplayed. Type 10, 20, and 30 records are generatedas indicated in the explanation of message DFS879A.

Programmer responseSame action as specified in DFS877A.


Module:DFSURG10



DUPLICATE RECORD FOR LOGICAL PARENT(followed by one or more lines containing inputrecords in hexadecimal and EBCDIC format)“DFS879A” on page 322NO LOGICAL PARENT RECORD FOUND FORLOGICAL CHILD RECORD (followed by oneor more lines containing input records inhexadecimal and EBCDIC format)“IMS problem determination” on page 11IMS messages and codes problemdetermination is accomplished by usingprocedures established by IBM.

DFS881I DUPLICATE RECORD FOR LOGICALCHILD (followed by one or morelines containing input records inhexadecimal and EBCDIC format)

ExplanationThe issuing program found an input work data setrecord that was for the same occurrence of a logicalchild as a previous input work data set record. Onlyone type 10 record can exist for an occurrence of alogical child.

Programmer responseSame action as specified for message DFS877A.


Module:DFSURG10

Related information“DFS877A” on page 321DUPLICATE RECORD FOR LOGICAL PARENT(followed by one or more lines containing inputrecords in hexadecimal and EBCDIC format)“IMS problem determination” on page 11IMS messages and codes problemdetermination is accomplished by usingprocedures established by IBM.

DFS882I ABNORMAL PROGRAMTERMINATION, number

ExplanationThe issuing program detected one or more errorconditions during its operation. The number indicatesin which SORT program phase the last-detectederror occurred. This message is issued when anothermessage with a return code greater than 5 or a returncode or abend from the SORT program occurs. Thismessage can also indicate an empty work file l input.

(For details, see the "Database Reorganization/LoadProcessing" topic, Database Scan Utility discussion inIMS Version 15 Database Utilities. Prefix resolutionmight be invalid if this message is issued. Any affecteddatabases should not be used.

Programmer responseDetermine the cause of the error (either return codesor error messages) and take appropriate action. Returncodes issued by z/OS SORT/MERGE are returned toz/OS by the Prefix Resolution program.


Module:DFSURG10


DFS883A ISAM KEY NOT FOUND INDATABASE FOR FUNCTION PUrecord

Explanation:The prefix update function tries to read the prefixupdate information for an ISAM data set, but it didnot find a matching key. The record (record) in error isdisplayed following the message.

System action:The prefix update function return code is set to RC08.

User response:Determine whether the record displayed in themessages should exist in the ISAM data set. Correctthe record.

Module:DFSURGP0

DFS884I DEVTYPE FAILURE

ExplanationThe issuing program issued a DEVTYPE macro toobtain information about an input or output device.The return code indicated that the attempt wasunsuccessful.

Operator response:Report this problem to the system support personnel.





DFS885I CAUTION-LIMIT CHECK FAILURE,database-name1, segment-name1database-name2 segment-name2

ExplanationThe issuing program detected a failure in the limitcheck for the concatenated logical child and logicalparent segment indicated by the named databaseand segment names. The limit check performed isdescribed in the "Database Prefix Resolution Utility"topic in IMS Version 15 Database Utilities. Thismessage is cautionary only, because the issuingprogram assumes worst case in computing the limitcheck.

Programmer responseDetermine the cause of limit check failure. If none ofthe components of the limit check can be omitted,consider (1) loading the logical parent or logical child,or both, with an update program, or (2) redefinition ofthe affected segments so that one or more of the limitcheck components can be omitted.


Module:DFSURPR0


DFS886I NO DATA IN SYSIN DATASET

ExplanationA SYSIN DD statement was supplied, but the data setwas empty. The step is terminated and a return code of16 is passed in register 15.

Programmer responseSupply valid data for this data set, and rerun the job.

Module:DFSURUL0

DFS0887A THE LOAD FOR DFSMDAMEMBER mmmmmmmm FAILED.REASON=xxxx

ExplanationThis message can be generated either during an onlinechange library switch process or at control regioninitialization.

During an online change library switch process, thePREPARE phase tries to load the DFSMDA member forthe inactive ACBLIB. That load failed. The reason forthe load failure is specified in xxxx. The member name,IMSACBA or IMSACBB, is displayed in mmmmmmmm.

At control region initialization, IMS tries to load theDFSMDA member for the active ACBLIB. That loadfailed. The reason for the load failure is specified inxxxx.

Possible reason codes that are passed in the messagetext are:0001

Invalid MDA member0002

Error reading member from STEPLIB0003

Error reading member from IMSDALIB0004

IMODULE GETMAIN failure0005

Load error from IMSDALIB0006

Load error from STEPLIB0007

This reason code means one of the following twothings:

• Member not found in STEPLIB or IMSDALIB

• OPEN processing for IMSDALIB timed out

System actionIf this event occurs at control region initialization, IMSterminates abnormally with user abend 0071. If thisproblem occurs during an online change library switch(INIT OLC PHASE (PREPARE)), completion code180 is returned to the SPOC. The message text isDFSMDA MEMBER LOAD FAILED.

System programmer response:Your responses are determined from the reason code.If the reason code indicates that DFSMDA member isnot found, add the member and restart the process.

Module:DFSDSSM0

DFS888I NO DATA BASE RECORDS FOUNDFOR PSB psbname (AFTERCHECKPOINT checkpoint id) (FORREGION region id)


ExplanationThe log data set supplied contained no database logrecords for the PSB specified.

If the input log was created by an online IMSsubsystem, this message means that no UOR wasfound which meets the requirements for backout bythe Batch Backout utility. If no control statementsare input to Batch Backout, the utility will back outonly deferred backouts for the PSB in the executestatement.

If the application being backed out is a batch job,database data sets that were opened by the failedbatch job but not successfully closed are reopenedand then closed by the Batch Backout utility, eventhough there are no log records requiring backout.

The text AFTER CHECKPOINT checkpoint-idappears only if the log is from a batch job usingcheckpoints, and a checkpoint record (type 41) isfound for the correct PSB. If a checkpoint is presentin the message, it is always the last checkpoint-idfound. If you specified a CHKPT statement in theSYSIN data set, and if the checkpoint in the messageis different from your checkpoint, then one of thefollowing occurred:

• IRLM was used during the update.• Another type 41 record exists after the one youspecified, and no type 5X records exist between yourcheckpoint-id and the end of the data set.

Programmer responseCheck the input log data sets to be sure that thecorrect log data sets are being supplied to the utility.A frequent cause for this message to be displayed isthe use of logs from the wrong job or the wrong timeperiod.


Module:DFSBACK0


DFS889I MULTIPLE LOGICAL CHILDRECORDS/LP NO LT PTRSSPECIFIED (followed by one ormore lines containing input recordsin hexadecimal and EBCDICformat)

ExplanationThe issuing program found a second logical childrecord for a logical parent record, but no logical twinpointers were specified for the logical child segmenttype. A return code of 8 is passed to DFSURG10 fromsort exit 35. Abnormal termination message DFS339Iis also issued.

Programmer responseThe user should determine if this condition isaccording to specification, make corrections, and rerunthe Prefix Resolution utility. A possible correctionmight be removal of input data which caused morethan one LC to point to the same LP or a new DBDGENto include LT pointers in the LC segment.


Module:DFSURG10

Related information“DFS339I” on page 121FUNCTION ff HAS COMPLETED{NORMALLY|ABNORMALLY}{rc=nn|x NO. OFUPDATES=nnnnnnnn}“IMS problem determination” on page 11IMS messages and codes problemdetermination is accomplished by usingprocedures established by IBM.

DFS890I BLKSIZE NOT SUPPLIED OR ISTOO SMALL FOR INPUT LOGddname

ExplanationThe specified input log DD statement did not specifya DCB BLKSIZE parameter and this field could not beobtained from the DSCB.

System actionThe Database Backout utility terminates.

Programmer responseSpecify the BLKSIZE value in the DD statement andresubmit the job.


Module:DFSBACK0




DFS891A DDNAME NOT FOUND OR DEVTYPEERROR

ExplanationAn OPEN macro or DEVTYPE macro was issued for theactive format data set with a ddname of FORMATA orFORMATB or a DEVTYPE macro was issued with aninvalid AREA address.

System actionIMS terminates abnormally with either abend 0889 orabend 0890.

Programmer responseRerun the job with the correct DD statement.

Module:DFSIINF0, DFSIING0


DFS892A NOT ENOUGH STORAGEAVAILABLE IN MFBP

ExplanationNot enough storage was available in the messageformat buffer pool (MFBP) to complete theinitialization of the pool.


Programmer responseRerun the job, giving more storage to the MFBP.The FBP symbolic parameter of the EXEC statementcontrols the amount of storage available for the pool.



DFS893A I/O ERROR READING $$IMSDIROR THE DIRECTORY {-nnn}

ExplanationAn I/O error occurred while issuing a FIND, POINT,or READ macro for the active FORMAT library duringinitialization of the message format block pool. This isprobably caused by an error in the PDS directory. Ifthe active FORMAT library has concatenated data sets,nnn indicates on which of the concatenated data setsthe error occurred.

System actionIMS terminates abnormally with either abend 0893 orabend 0894.




DFS894I INVALID RECORD ERROR nn ONINPUT LOG DD ddname

ExplanationOne of the following errors, with subcode=nn,occurred on the batch input log:Subcode

Meaning01

A variable-length record was read with a fieldlength of zero.

02A spanned record was encountered.

03End of block not equal to end of buffer.

04Next record beyond the end of buffer.

System actionThe Database Backout utility, DFSBBO00, terminatesunsuccessfully with a return code of RC36 (X'24').If the ABENDMSG control statement was specified,abend 0507 is issued.

Programmer responseThis error is issued only for a batch input log. Thiscondition can be caused by using an improperly closedlog data set as input. Run DFSULTR0 to close thelog, and then rerun the job. If the error persists, the







log data set is currently unusable for batch backoutor forward recovery utilities. Contact the systemprogrammer for database recovery options.

Module:DFSBACK0


DFS895I LTERM name STOPPED DUE TOCODE XXX

ExplanationIMS remote station support encountered an error. Thelogical terminal named in the message was stoppedby the receipt of an error message following thetransmission of a message to the remote station fromthe named logical terminal.


Module:DFSCR2Z0

DFS896A UNEXPECTED RECORDENCOUNTERED - SEQUENCEERROR nn on DDNAME ddname

ExplanationDuring the forward reading of an input log, BatchBackout performs context checks on log records. Oneof the context checks failed, implying that the log dataset with the identified ddname is out of order.

The following subcodes nn identify the error:Subcode

Meaning03

During forward read of a batch log, a TYPE5Xrecord was found with a date-time value lowerthan a previous record processed.

04During forward read of a batch log, a TYPE06record was found with a time stamp less than thecurrent saved.

System actionThe Database Backout Utility, DFSBBO00, terminatesunsuccessfully with a return code of RC40 (X'28').If the ABENDMSG control statement was specified,abend 0507 is issued.

Programmer responseRerun the backout, providing all of the needed log datasets, in the order they were created. If all the logswere provided in the correct order, save the log inputand the abend 0507. Then, contact the IMS systemprogrammer.

Module:DFSBACK0


DFS0897A STRUCTURE structure_name IS INTRANSITION. IT IS UNAVAILABLETO AREA area_name

ExplanationDuring an attempt to connect to the structure,IMS issued the IXCQUERY command to check forthe structure status. IMS received return codeQUASTRCFTRAN, which indicates that the structurewas in transition state. The structure was either beingallocated on the coupling facility or deleted from thecoupling facility.

System actionThe area is not loaded into the coupling facility.

Operator response:Check whether the structure is being allocated onor deleted from the coupling facility by using thecommand D XCF,STRUCTURE,STRNAME=. After thestructure is allocated, issue the STOP AREA commandfollowed by the START AREA command to connect tothe structure.

Module:DBFVXAS0

DFS898A INVALID OPTION STATEMENT INSYSIN - RECORD NUMBER nn

ExplanationBatch Backout detected a SYSIN data set record thatwas not a recognized control statement. nn indicatesthe record number of the invalid control statement inthe SYSIN data set.

System actionThe job terminates with a condition code of 72 beforeany backout is attempted.




Programmer responseCorrect or remove the indicated control statement andrerun Batch Backout.

Module:DFSBACK0

Related referenceBatch Backout utility (DFSBBO00) (DatabaseUtilities)

DFS899A RELOAD COMPLETED, BUTDBRC FUNC=nnnnnnnn HASTERMINATED WITH RC=xx

ExplanationThe database RELOAD occurred before anyreorganization call to DBRC (DFSBRLSC ID=REN). TheRELOAD completed and message DFS339I showeda return code of 00 or 04. The DBRC call function(DFSBRLSC FUNC=nnnnnnnn) failed with the returncode shown in this message.

System actionProcessing continues and the step terminates withcondition code 04.

Programmer responseIf the return code for message DFS339I was 00,the RELOAD was successful. If the return code forDFS339I was 04, then a prior warning message wasissued. In either case, there might be an inconsistencyin the RECON data sets. Examine the RECON for thereorganized database and respond to the DBRC DSPmessages issued.

Module:

DFSURGL0Related information“DFS339I” on page 121FUNCTION ff HAS COMPLETED{NORMALLY|ABNORMALLY}{rc=nn|x NO. OFUPDATES=nnnnnnnn}

DFS0900A INVALID COMBINATION OF DBILAND DBR OR DBS FOR DBDS lp/dbdname AND lc/dbdname FORFUNCTION PO

ExplanationThe Prereorganization utility (DFSURPR0) discoveredthat a database containing a logical parent is beinginitially loaded (DBIL=) and the logical child databaseis being reorganized or scanned (DBR= or DBS=). Ifthe logical child DBDname was not specified, function(DBS=) is assumed for that logical child database.

System actionModule DFSURPR0 returns a condition code of 8,indicating that the output control data set is notvalid, and continues processing the remaining controlstatements.

Programmer responseThe control data set is invalid and, if used, doesnot correctly resolve the logical pointers between theexisting logical children and the logical parent beinginitially loaded. Ensure if logical parents are initiallyloaded that logical children are initially loaded also.

Module:DFSURPR0


http://www.ibm.com/support/knowledgecenter/SSEPH2_15.1.0/com.ibm.ims15.doc.dur/ims_dfsbbo00.htm#ims_dfsbbo00




DFS0901A JJJJJJJJ - QCF/QSN WAIT QUEUEHAS WAITER

ExplanationThe dependent region was placed in a wait state byDFSQSPC0, the IBM IMS Queue Control Facility forz/OS version of the Queue Space Notification Exit. Thewait state occurred based on IMS queue usage, whichexceeded the user or default limits. As a result of thewait state, the wait queue went from empty to queuedrequests, resulting in this message.

In the message text, JJJJJJJJ identifies IMS job name.

System actionThe process is placed in a wait state, and is one of thefollowing:

• An input device• An MSC link• A region (MPP, BMP, Fast Path, or CPIC)• A terminal• APPC• OTMA

Operator responseIn the IMS Queue Control Facility TSO/ISPF panel,select the Queue Space Notification (QSN) option andlist the QSN waiters, then take the appropriate action.

Module:DFSQMRE0

DFS0901W RETURN CODE 4 FROMHDAM RANDOMIZER, SEGMENTSDROPPED

ExplanationWhile inserting a segment, the HDRELOAD Utilityreceived an FM status code as the result of receivingreturn code 4 from the HDAM randomizer. For moreinformation about the FM status code, see the DL/Istatus code information.

System actionThe segment name is printed to the job output,followed by the segment data on the next line. This

process is repeated for all dependent segments.If the number of segments dropped (drop count)exceeds 10,000, then message DFS0902W is issuedand HDRELOAD issues user abend 0355. If the dropcount is less than 10,000, then HDRELOAD continuesinserting segments and issues user abend 0355 whenit completes.

Programmer responseDetermine the cause of return code 4 from the HDAMrandomizer and correct the problem. Run HDRELOADagain or manually insert the segments. If you mustkeep the partially loaded data set (either you do notneed the dropped segments or you manually insertedthem), then use the DBRC NOTIFY.REORG commandto record the reorganization activity in the RECON.

Important: If message DFS0902A was issued asa result of the drop count exceeding the 10,000threshold, do not attempt to use the partially loadeddata set. Instead, run HDRELOAD again with a goodrandomizer.

Module:DFSURGL0

Related referenceDL/I status codes (Messages and Codes)Related information“DFS0902A” on page 329RELOAD TERMINATED - TOO MANY SEGMENTSDROPPED

DFS0902A RELOAD TERMINATED - TOO MANYSEGMENTS DROPPED

ExplanationThe HDRELOAD Utility received an FM status codebecause return code 4 was issued due to HDAMrandomizer failures. As a result, the number ofsegments dropped (drop count) exceeded the 10,000threshold. For more information about the FM statuscode, see the DL/I status code information.

System actionHDRELOAD terminates with abend 0355.



Programmer responseFix or replace the randomizer module with a differentone.

Module:DFSURGL0

Related referenceDL/I status codes (Messages and Codes)Related informationIMS abend 0355

DFS0903W PARTITION SELECTION ERRORSTATUS=FM, SEGMENTSDROPPED

ExplanationWhile inserting a segment, the HDRELOAD Utilityreceived an FM status code from the HALDB PartitionSelection Exit routine because of a HALDB partitionselection failure. For more information about the FMstatus code, see the DL/I status code information.

System actionThe segment name is printed to the job output,followed by the segment data on the next line. Thisprocess is repeated for all dependent segments.If the number of segments dropped (drop count)exceeds 10,000, then message DFS0902A is issuedand HDRELOAD issues user abend 0355. If the dropcount is less than 10,000, then HDRELOAD continuesinserting segments and completes with RC=08.

Programmer responseDetermine the cause of the partition selection errorand correct it. The most common causes are:

• An incorrect high key range specified for the lastpartition.

• A user-written partition selection exit rejecting thekey.

Run HDRELOAD again or manually insert thesegments. If you must keep the partially loaded dataset (either you do not need the dropped segments oryou manually inserted them), make an image copy ofthe data sets. The incomplete data sets are usable.

Module:DFSURGL0

Related referenceDL/I status codes (Messages and Codes)Related information“DFS0902A” on page 329RELOAD TERMINATED - TOO MANY SEGMENTSDROPPED

IMS abend 0355

DFS0904I SINGLE ADS AREA aaaaaaaaCLOSED DUE TO READ ERRORS.NO MISSING UPDATES.

ExplanationA single area in an area data set (ADS) encounteredmore than ten read errors. Because there is no updatebeing made to this data set, no data is lost in thecurrent ADS in the DASD.

System actionThe area is stopped.

Programmer responseIf the area is being shared among multiple IMSsystems, check message DFS0904I on all IMSsystems. If the DASD can be repaired without beingrestored, the ADS is usable as is.

If the DASD is to be restored, the data on the ADSmight get outdated. Recover the area by using the lastgood image copy and log records.

Module:DBFMPCL0

DFS0905E INSUFFICIENT STORAGE FOR PSBpsbname

ExplanationThere was not sufficient storage space for theapplication control block (ACB) utility to build thecontrol blocks for the program specification block(PSB) identified in the message text.

System actionAbend 0905 is issued if batch DL/I was running. If theACBGEN utility was running, it ends with return code 8.

Programmer responseIncrease the region or partition size, and rerun theprogram.

Module:DFSDLBL0


DFS0906I INVALID PROCOPT FOR SENSEGsenseg name IN PSB psbname







ExplanationThe named SENSEG statement in the named PSB hasan invalid PROCOPT specified.

System actionAbend 0906 is issued if batch DL/I was running.ACBGEN processing continues if the ACBGEN utilitywas being run.

Programmer responseCorrect the PSB, and rerun the program.

Module:DFSDLBL0


DFS0907I PSB psbname REFERENCESLOGICAL DBD dbdname FOR LOAD

ExplanationThe named PSB has a PCB statement that referencesthe named logical DBD with a PROCOPT of L. Onlyphysical DBDs can be used to load a database.


Programmer responseCorrect the PSB or DBD, and rerun the program.

Module:DFSDLBL0


DFS0908I PSB psbname IS NOT A VALID PSB

ExplanationThe PSB indicated was not in a recognizable format forIMS.


Programmer responseCreate the PSB using the IMS PSBGEN, and rerun theprogram.

Module:DFSDLBL0


DFS0909I DBD dbdname IS NOT A VALIDDBD

ExplanationThe database description (DBD) indicated by dbdnamewas not in a recognizable format for IMS; or theDBDLIB bind name and the assembled name of DBDare different.

There are cases where the DBD by itself is valid butit was invalidly referenced as a primary index or asecondary index by another database.

System actionAbend 0909 is issued if the online region or batch wasrunning. ACBGEN processing continues if the ACBGENutility was being run.

Programmer responseCreate the DBD using the IMS DBDGEN, and rerun theprogram. If the DBD defines a main storage database(MSDB) or a data entry database (DEDB), the IMSsystem must contain Fast Path support.

Go through each database program communicationblock (DB PCB) of the involved PSB to pick up thedata name. Then, search its DBD source for theLCHILD statement with PTR=INDX and with referenceto the database name specified in this error message.Correct the error.

Module:DFSDLBL0


DFS0910I INTERNAL PROG LOGIC ERRORPROCESSING PSB-psbname

ExplanationAn internal programming error has occurredprocessing the indicated PSB.







Programmer responseRemove the PSB from the processing list and rerunthe program. Before contacting IBM Software Support,have the associated PSB and DBDs available.

Module:DFSDLBL0


DFS0911I ENQ LIST LENGTH ERROR FORPSB psbname

ExplanationThe processing option intent list length was calculatedincorrectly for the named PSB.


Programmer responseThis problem is an internal program logic error.Remove the PSB, and rerun the program.


Module:DFSDLBL0


DFS0912I PSB psbname REFERENCES SEGMsegmname IN DBD dbdname.SEGM NOT FOUND.

ExplanationThe named PSB referenced the named SEGM in thenamed DBD. The named SEGM does not exist in thenamed DBD.


Programmer responseCorrect the PSB or DBD, and rerun the program.

Module:DFSDLBL0


DFS0913I DBD dbdname CONTAINS INVALIDACCESS METHOD

ExplanationThe named DBD contained an invalid or unknownaccess method.


Programmer responseCorrect the DBD, and rerun the program.

Module:DFSDLBL0


DFS0914I THE PCB FOR DATABASE -dbdname HAS PARTITIONED ANDNON PARTITIONED DATABASESSPECIFIED

ExplanationThis message can occur during the ACBGEN processif the database referenced by a PCB is related toone or more databases by a logical relationship, or asecondary index, and not all related databases are ofthe same type. The databases must all be partitioned,or they must all be nonpartitioned.

In the message text, dbdname can see a logicaldatabase. Use the name of the logical database todetermine the referenced physical databases wherethe type mismatch occurs.






System actionThe ACBGEN fails with a condition code 08.

Programmer responseCorrect the database in error so that all of thedatabases in the logical relationship are either allpartitioned or all nonpartitioned. Rerun the program.

Module:DFSDLB70

DFS0915I INDEX DBD-dbdname-HASINCORRECT SEQ FIELD LENGTH.LENGTH SHOULD BE-xxx BYTES.

ExplanationThe named INDEX DBD has a sequence field lengthspecified which is not equal to the indexed field length.The correct length is indicated.


Programmer responseCorrect the DBD in error, and rerun the program.

Module:DFSDLBL0


DFS0916I NON-UNIQUE OR NO SEQ FIELDSPECIFIED FOR DBD-dbdname

ExplanationThe named DBD requires a sequence field be specifiedfor the root segment. A sequence field was notspecified, or the field was specified as not unique.



Module:DFSDLBL0


DFS0917I DBD dbdname REFERENCES SEGMsegmname IN DBD dbdname.SEGM DOES NOT EXIST.

ExplanationThe first DBD referenced the named SEGM in thesecond DBD. The SEGM does not exist in the secondDBD.


Programmer responseCorrect one or both DBDs, and rerun the program.

Module:DFSDLBL0


DFS0918I UNABLE TO LOCATE PHYSICALPARENT. PSB psbname SENSEGsenseg name

ExplanationThe named PSB contained a SENSEG statement for thenamed segment. The SENSEG statement referenceda logical child segment as the first part of a segmentconcatenation. The second part of the concatenation,the logical or physical parent of the logical child, didnot have a valid physical parent.


Programmer responseCorrect the PSB or the DBDs in error, or both, andrerun the program.

Module:DFSDLBL0


DFS0919I PSB-psbname-PCB-pcbname-DBD-dbdname -KEYLEN






SPECIFICATION TOO SMALL.KEYLEN SHOULD BE-xxxxx BYTES

ExplanationThe named PCB in the named PSB contained a KEYLENparameter that was too small to hold the longest fullyconcatenated key. The correct length is indicated.

If the PCB label is not available, the pcbname can beeither blanks or the relative PCB number.

If you define a PCB with the PROCSEQD operand for aPSB using a Fast Path secondary index, make sure thatthe value of the KEYLEN parameter is the larger of thelongest physical concatenated key for a hierarchic pathof sensitive segments or the longest concatenated keyof the secondary data structure.

System actionAbend 0919 is issued if batch DL/I was running.ACBGEN processing continues if the ACB Maintenanceutility was being run.

Programmer responseCorrect the PSB and rerun the program.

Module:DBFUDLB0, DFSDLBL0


DFS0920I PSB psbname REFERENCES DBDdbdname WITH CONFLICTINGPROCOPTS

ExplanationThe named PSB contained at least one reference tothe named DBD with a PROCOPT of L and at least oneadditional reference to the same DBD with a PROCOPTof something other than L. The reference can be direct,such as in a PCB statement, or the reference can beindirect, such as in a DBD which references anotherDBD through logical or index relationships.


Programmer responseCorrect the PSB or one or more DBDs, or both, andrerun the program.

Module:

DFSDLBL0Related informationIMS abend 0920

DFS0921I PSB psbname IS NOT A PSB

ExplanationThe named PSB was loaded. Upon examination, it wasdiscovered the PSB was not a valid PSB.


Programmer responseCheck the JCL or control statements, or both. Correctthe error, and rerun the program.

Module:DFSDLBL0


DFS0922I DBD dbdname IS NOT A DBD

ExplanationThe named DBD was loaded. Upon examination, it wasdiscovered the DBD was not a valid DBD.


Programmer responseCheck the JCL or control statements, or both. Correctthe error, and rerun the program.

Module:DFSDLBL0


DFS0923I LC SEGM-segmname-IN DBD-dbdname-DATA LENGTH TOOSMALL. LENGTH SHOULD BE-xxxxxBYTES.

ExplanationThe indicated logical child segment in the indicatedDBD had a BYTES specification shorter than its


http://www.ibm.com/support/knowledgecenter/SSEPH2_15.1.0/com.ibm.ims15.doc.msgs/msgs/0919.htm#imsabends0919




logical parent's fully concatenated key. The minimumacceptable length is indicated.



Module:DFSDLBL0


DFS0924I INDEX SEGMENT IN DBD-dbdname-TOO SHORT. LENGTHSHOULD BE-xxxxx BYTES.

ExplanationThe root segment in the named INDEX DBD had a datalength that was too small to hold the required indexdata. The minimum acceptable length is indicated.



Module:DFSDLBL0


DFS0925I SEGM segmname IN DBD dbdnameHAS A SEQ FIELD IN VIRTUALLPCK AREA

ExplanationA named logical child segment had a sequencefield defined which fell within the logical parent'sconcatenated key area in the logical child and the keywas specified as VIRTUAL. The key must be specifiedas PHYSICAL if it is to be used as part of the physicaltwin sequence field.



Module:DFSDLBL0


DFS0926I INVALID ALT PROC SEQSPECIFIED FOR SENSEG-segnameIN PCB-pcbname IN PSB-psbname

ExplanationThe indicated PCB in the indicated PSB hadan alternative processing sequence specified. Thespecified secondary index is not valid for the specifiedSENSEG.


Programmer responseCorrect the PSB or the DBDs, or both, and rerun thejob.

Module:DFSDLBL0


DFS0927I INDEX DBD dbdname INDEXESNON-EXISTENT FIELD IN DBDdbdname

ExplanationThe named INDEX DBD specified an indexed field inthe INDEXED DBD that does not exist.

If the PSB contains only a Fast Path secondary indexPCB to access the Fast Path secondary index databaseas a separate database, the associated DEDB PCBmust be included in the PSB. The minimal DEDB PCBrequires a SENSEG statement for the root segment ofthe associated DEDB database.








If the PSB contains only a Fast path secondary indexPCB to access the Fast Path secondary index databaseas a separate database, include the associated DEDBPCB in the same PSB. The minimal DEDB PCB requiresa SENSEG statement for the root segment of theassociated DEDB database. Correct the PSB in error,and rerun the program.

Module:DFSDLBL0


DFS0928I INDEX DBD dbdname INDEXES AFIELD WHICH IS NOT A SEQ FIELD

ExplanationThe named INDEX DBD indexed a valid field, but thefield was not a sequence field.



Module:DFSDLBL0


DFS0929I BLDL FAILED FOR MEMBER --member name

ExplanationA BLDL was issued for the named member. Themember was not found in the DBD or PSB library.


Programmer responseCorrect the error in the appropriate library, and rerunthe program.

Module:DFSDLBL0


DFS0930I INVALID SEGMENT PAIRING FORSEGM segmname IN DBD dbdname

ExplanationThe named DBD contained an LCHILD statementwhich referenced the named SEGM in aPAIR=operand. The named SEGM could not be foundor the named SEGM was a virtual segment and thesource segment contained a PTR=PAIRED operand.



Module:DFSDLBL0

DFS0931I INVALID INDEX RELATIONSHIPBETWEEN INDEX DBD dbdnameAND INDEXED DBD dbdname INPSB psbname

ExplanationThe named INDEXED DBD had an index relationshipwith the named INDEX DBD. Either the INDEX DBDdid not have a similar relationship to the INDEXEDDBD (for example, the INDEX DBD specifies a symbolpointer PTR=SYMB and the INDEXED DBD specifies adirect pointer PTR=INDX), or another DBD referencedin the named PSB also had an index relationship withthe INDEX DBD.


Programmer responseCorrect the appropriate PSB or DBDs, or both, andrerun the program.





Module:DFSDLBL0


DFS0932I INDEX DBD dbdname HAS NO SEQFIELD

ExplanationThe named INDEX DBD does not have a sequence fielddefined for the index segment.


Programmer responseCorrect the INDEX DBD, and rerun the program.

Module:DFSDLBL0


DFS0933I INVALID INDICES=(index name)SPECIFIED FOR PSB-psbname

ExplanationThe indicated PSB contained an INDICES operandwhich was invalid. The indicated value of the INDICESoperand was not a valid index name for the associatedSENSEG statement.


Programmer responseCorrect the PSB or DBDs in error, and rerun the job.

Module:DFSDLBL0


DFS0934I PSB psbname REFERENCED SEGMsegmname IN DBD dbdname.SEGM HAS INVALID POINTERS

ExplanationThe named PSB referenced the named logical childSEGM in the named DBD. The logical child requires thelogical parent concatenated key to be stored physicallybut VIRTUAL was specified, or the LP segment couldnot be located in the specified DBD.


Programmer responseCorrect the appropriate DBD, and rerun the program.

Module:DFSDLBL0


DFS0935I INVALID LOGICAL STRUCTUREFOR SEGM segmname IN DBDdbdname, PSB psbname

ExplanationThe named PSB referenced the named DBD in aSENSEG statement. However, a logical structure orrelationship within this segment definition was invalid.


Programmer responseCorrect the named DBD or the logical DBD referencedby the PSB, and rerun the program.

Module:DFSDLBL0


DFS0936I SEGM segmname IN PSB psbnameSPECIFIED LOAD FOR VIRTUALSEGMENT

ExplanationThe named SEGM was referenced in the named PSBwith a PROCOPT of L or LS. The SEGM is a virtualsegment and as such cannot be loaded.








Programmer responseCorrect the PSB, and rerun the program.

Module:DFSDLBL0


DFS0937I MISSING PARENS ON SOURCEOPERAND-segname DBDNAME-dbdname

ExplanationThe named DBD specified the named segment as avirtual segment. The SOURCE operand in the SEGMstatement contained more than one SOURCE operand.The probable cause is a missing pair of parentheses onthe SOURCE operand.


Programmer responseCorrect the DBD, and resubmit the job.

Module:DFSDLBL0


DFS0938I DELETE PROCESSING COMPLETEFOR {DBD|PSB} membername

ExplanationThe named PSB or DBD was deleted from theIMS.ACBLIB by user request.


Module:DFSUACB0, DFSUAMB0


DFS0939I INVALID PARMS SPECIFIED INPARM FIELD

ExplanationThe EXEC statement parameters specified were invalidor inconsistent.


Programmer responseCorrect the PARM field on the EXEC statement, andresubmit the job.

Module:DFSUACB0


DFS0940I {PSB | DBD} (psbname | dbdname)HAS BEEN {ADDED | REPLACED}IN LIBRARY. {PSB SIZE | DMB}SIZE = xxxxxx BYTES

ExplanationThe named PSB or DBD has been modified in the ACBlibrary. If it did not exist, it has been added. If it didexist, it has been replaced. The size of the member isas indicated.

Module:DFSUACB0, DFSUAMB0

DFS0941I PSB XXXXXXXX IF USING DL/ISUBORDINATE ADDRESS SPACE,CSA SIZE = xxxxxx, SAS SIZE =yyyyyy

ExplanationPSB XXXXXXXX has been inserted or replaced inACBLlB. If using DL/I subordinate address space, thePSB will require xxxxxx bytes of space in CSA andyyyyyy bytes of space in DL/I subordinate addressspace private. If the PSB is defined as resident, theresident CSA PSB and DL/I PSB space is computedand obtained at initialization time. If not resident, thespace is obtained from each PSB pool when the PSB isfirst used.






The sum of CSA size and SAS size in this messageis not necessarily the same as the PSB size givenin message DFS0940I. The PSB size in messageDFS0940I includes the size of the intent list. The sizeof the CSA PSB and the SAS PSB do not include thesize of the intent list.

Module:DFSUAMB0

Related information“DFS0940I” on page 338{PSB | DBD} (psbname | dbdname) HAS BEEN{ADDED | REPLACED} IN LIBRARY. {PSB SIZE |DMB} SIZE = xxxxxx BYTES

DFS0942I IF USING DL/I SUBORDINATEADDRESS SPACE, MAX CSA =wwwwww MAX SAS = xxxxxxAVERAGE CSA = yyyyyy AVERAGESAS = zzzzzz

ExplanationIf using DL/I subordinate address space, wwwwwwis the largest CSA space requirement, and xxxxxx isthe largest DL/I private space requirement for anysingle PSB processed by this ACBGEN. For all PSBsprocessed by the ACBGEN, yyyyyy is the average CSAspace requirement, and zzzzzz is the average DL/Iprivate space requirement. The ratio of the averageCSA and average SAS might provide some basis fordetermining the relative size of the two PSB pools.The ideal ratio might, however, be different becauseof other PSBs not processed by this ACBGEN or thefrequency distribution of PSBs in the pool.

Module:DFSUACB0

DFS0943I PSB PsbName REQUIRES AMINIMUM OF xxxxxxxx AND AMAXIMUM OF xxxxxxxx BYTES OFSTORAGE IN THE EPCB POOL

or

PSB PsbName REQUIRES A MIN OF xxxxxxxx ANDA MAX OF xxxxxxxx BYTES OF STORAGE IN EPCBPOOL IF USING FAST PATH

ExplanationThe message describes the amount of storage that thePSB requires in the EPCB pool.

The first form of this message is used only in IMSVersion 10 and IMS Version 11.

You are attempting to size the EPCB pool. EachPCB with PROCOPT=H requires additional storage inthe EPCB pool for use by High Speed SequentialProcessing (HSSP). The information that is requiredto calculate the exact size of the additional storageneeded by HSSP was unavailable at the creation of thismessage. There is a minimum and maximum amountof additional HSSP work area storage obtained foreach HSSP-sensitive PCB. This additional HSSP workarea storage is used to present the minimum andmaximum amount of storage the PSB requires in theEPCB pool.

The MAXIMUM amount of storage the PSB requires inthe EPCB pool includes each IOPCB and ALTPCB in thePSB.

System programmer responseUse the maximum required EPCB size, because theHSSP work area is not large enough to accommodatethe required space for the PSB.

Module:DBFUAMA0

DFS0944W BUILD FOR dbdname FAILED. AREQUIRED DBD WAS NOT INDBDLIB

ExplanationAn explicit ACB Generation request was made tobuild a DMB using a BUILD DBD=dbdname controlstatement, but a required DBD was not in DBDLIB.The missing DBD could be either the named DBD or alogically related DBD. This message is preceded by aDFS0929I message for the missing DBD.

System actionThe DBD is not replaced or added, and a return code 8is set.

Programmer responseAdd the missing DBD to DBDLIB and rerun ACBGeneration.

Module:DFSUACB0

Related information“DFS0929I” on page 336BLDL FAILED FOR MEMBER -- member name

DFS0945I PSB-psbname-PCB-pcbname HASNO SENSITIVE SEGMENTS.


ExplanationThe named database PCB within the named PSB hadno SENSEG statements defined at PSBGEN time. ThePSBGEN was invalid.


Programmer responseCorrect the PSB source statements, and rerunPSBGEN.

Module:DFSDLBL0


DFS0946I INDEX DBD-dbdname INDEXES ASYSTEM RELATED FIELD

ExplanationThe indicated INDEX DBD contained an INDEX=operand that specified a field name with a /CK as thefirst 3 characters.


Programmer responseCorrect the DBD, and rerun the job.

Module:DFSDLBL0


DFS0947I DBD dbdname BUILD DID NOTFORCE PSB REBUILDS.

ExplanationThe database dbdname was specified in a BUILDDBD= statement but was unchanged in the areas thatrequired rebuild of referencing PSBs. These PSBs arenot automatically rebuilt. (All PSBs explicitly listed onBUILD DBD= statements will be rebuilt.) PSB SelectiveRebuild does not apply to Fast Path MSDBs.

System actionDBD is replaced in ACBLIB, but referencing PSBs arenot changed.


Module:DFSUAMB0

DFS0948I SEGM-segmname-IN DBD-dbdname-IS VARIABLE LENGTH.PHYSICAL PAIR OF SEGMENT ISFIXED LENGTH.

ExplanationThe indicated segment in the indicated DBD wasa physically paired logical child of variable length.The opposite pair was fixed length. Physically pairedsegments must have the same length attributes.


Programmer responseCorrect the DBD in error, and rerun the job.

Module:DFSDLBL0


DFS0949I INDEX DBD-dbdname-INDEXESITSELF

ExplanationThe indicated INDEX DBD contained an LCHILDstatement that contained the same database namefor the indexed database as the name for this indexdatabase.



Module:





DFSDLBL0Related informationIMS abend 0942

DFS0950I LOGICAL CHILD OR LOGICALPARENT IN DBD dbdnameREFERENCES SEGM segmentname. REFERENCED SEGMHAS NO CORRESPONDINGREFERENCE.

ExplanationAn invalid logical relationship exists:

• A logical child references the named segment in theindicated database and the named logical parentdoes not have an LCHILD statement.

• A logical parent references a logical child segment inthe named database and the logical child does nothave a reference for the logical parent.

• A logical DBD does not contain a reference tothe named segment in the SOURCE= operand thatreferences its corresponding logical child or logicalparent.



Module:DFSDLBL0







DFS0951I SEGM segment name ISPHYSICALLY PAIRED. ITS PAIRDOES NOT HAVE EQUALINTERSECTION DATA LENGTH.

ExplanationThe referenced segment is physically paired. Either thetwo intersection data lengths are not equal (for fixed-length segments); or the maximum intersection datalengths for the two paired segments are not equal.




Module:DFSDLBL0


DFS0952I INVALID PROCOPT SPECIFIEDFOR PRIMARY INDEX DBDnnnnnnn

ExplanationAn invalid PCB processing option was specified for aPCB which references either a primary or secondaryindex DBD. If a PCB references a primary index DBD,the only valid processing option is G, or GOx. If a PCBreferences a secondary index DBD, this message willbe returned if the PCB processing option is L or LS.For a secondary index DBD, processing option of I isalso invalid, but if I is specified, the processing optionis changed to exclude the I and warning messageDFS2438W is sent.

System actionIf this condition occurs while building the blocks ina batch 'DLI' region, abend 0958 is issued. If thiscondition occurs while doing an ACBGEN, the ACBGENcontinues and additional messages indicate the actiontaken regarding the PSB is in error.

Programmer responseChange the PSB to not reference the primary orsecondary index DBD; or change the processing optionof the PCB to a valid processing option for the indexDBD.


Module:DFSDLBL0


DFS0953I LOGICAL CHILD IN DATA BASExxxxxxxx HAS A L/P PTRSPECIFIED. LOGICAL PARENT ISIN HISAM ORG.

ExplanationAn error exists in the logical child SEGM statement indatabase xxxxxxxx. It is not permissible to specify adirect pointer to a database with HISAM organization.PTR=LP is the incorrect specification; only PTR=should be specified.

System actionIf running under DL/I, IMS terminates abnormally withabend 0959.

Programmer responseCorrect the logical child SEGM statement to removethe LP specification. Specify instead only PTR= andreassemble the DBD. Rerun the job.

Module:DFSDLBL0




DFS0954I LOGICAL PARENT IN DATA BASExxxxxxxx HAS AN L/C POINTER.THE REFERENCE L/C IS IN HISAMORG.

ExplanationAn error exists in the LCHILD statement in databasexxxxxxxx. You have specified either PTR=SNGL orPTR=DBLE; both specifications are incorrect. It is notpermissible to specify a direct pointer to a databasewith HISAM organization.


Programmer responseCorrect the LCHILD statement, reassemble the DBD,and rerun the job.

ModuleDFSDLBL0

DFS0955I DBD xxxxxxxx IS A SHARED INDEXWITH MORE THAN ONE XDFLDCONSTANT OF THE SAME VALUESPECIFIED

ExplanationAn error exists in the XDFLD statement in the DBDthat points to the shared Index. You have specifiedmore than one XDFLD constant of the same value.Each XDFLD statement for a shared index must havea unique CONST= specification.


Programmer responseCorrect the XDFLD statements in error, reassemble theDBDs, and rerun the job.

Module:DFSDLBL0


DFS0956I PSB psbname CONTAINS ANHIERARCHIC SEQUENCE ERRORAT SENSEG segname

ExplanationThe SENSEG statements within the named PSB werenot specified in hierarchic sequence (top to bottom,left to right).

System actionAbend 0962 is issued if batch DL/I was running.ACBGEN processing continues.

Programmer responseCorrect the order of the SENSEG statements, andrerun the job.

Module:DFSDLBL0


DFS0957W PSB psbname IS TOO LARGEFOR ACBGEN.SIZE=xxxxxxxxMAXIMUM=04194240

ExplanationACBGEN determined that PSB psbname exceededthe size allowed by IMS. The generated PSB sizeis xxxxxxxx. The maximum allowed PSB size is4,194,240 bytes.

System actionThe PSB is deleted from ACBLIB and a return code 8 isset. ACBGEN continues with the next PSB.

Programmer responseRedesign the PSB with fewer SENSEG and PCBstatements.

Module:DFSUAMB0

DFS958I CHKPT NOT FOUND ON LOG

ExplanationA checkpoint ID was specified by a CHKPT statementas a stopping point for the database-backout process,but a corresponding batch-checkpoint record was notfound on the log. No backout is performed.





Programmer responseEnsure that the correct ID is specified and the correctlog data set is mounted.


Module:DFSBACK0


DFS959I CHKPT NOT WITHIN LASTSCHEDULE OF PGM

ExplanationThe batch-checkpoint record specified by a CHKPTstatement was located on the log, but a subsequentscheduling of the program was found on the same logvolume. No backout is performed.

Programmer responseOnly database changes made during the most recentscheduling of a program should be backed out.


Module:DFSBACK0


DFS0960I WARNING DBD-dbdname-NOTREPLACED IN LIBRARY

ExplanationThe named DBD was processed as the result ofa BUILD PSB= request, but the DBD existed inthe ACBLIB. If BUILD DBD= was specified, a PSBreferenced the requested DBD and the named DBD.The named DBD was not rebuilt.

System actionIMS continues processing but generates a return codeof 4.

Programmer responseIf the named DBD requires replacement in the ACBLIB,the DBD must be processed with a BUILD DBD=control statement.

Problem determination:2, 4, 17d, 18, 19

Module:DFSUAMB0


DFS961W MULTIPLE OCCURRENCES OFLOGICAL TWIN SEQ FIELDDETECTED. FIELD DEFINED ASUNIQUE.

ExplanationA database with a logical child indicated a uniquelogical twin sequence field was already loaded withnonunique logical twin sequence fields.

System actionIMS continues processing. The Prefix Update utility(DFSURGP0) marks the nonunique logical twin recorddeleted on the logical path. The delete rules areignored.

Programmer responseDelete the affected segments and reinsert them withcorrected sequence fields during any subsequentupdate run.


Module:DFSURG10


DFS0962I DBD dbdname NOT PROCESSED.

ExplanationA BUILD DBD= control statement requestedprocessing of the named DBD, and the PSBs thatreference the DBD are not found in the PSBLIB.



Programmer responseVerify that the correct DBD name has been specifiedand that the PSBs that reference the DBD are in thePSBLIB.

Module:DFSUACB0

DFS0963W PURGE DATE CONFLICTS WITHINPUT ACCUM DATA FROM DDddname DATA BASE databasename FOR FUNCTION CA.

ExplanationThe old change-accumulation-data set header recordcontains a creation date and time. The specified purgedate is before the creation data and time. If the inputlog data set contains records created before the oldchange accumulation database, extra records will havebeen accumulated that cannot be used in recovery.

System actionIMS continues processing but generates a return codeof 4.

Programmer responseEnsure that the input log data set does not includeany records for the named database that were createdbefore the old change accumulation database.


Module:DFSUC350


DFS964I INVALID PROCOPT SPECIFIEDFOR PCB=pcbname, INPSB=psbname

ExplanationThe named PCB contained a PROCOPT of H but theDBD is not a DEDB. The PROCOPT H is only valid for aDEDB.

System actionAbend 0996 is issued if batch DL/I was running.ACBGEN processing continues if the ACBGEN utilitywas running.

Programmer responseCorrect the PSB and run the program again.

Module:DFSDLBL0


DFS965A DBD LRECL OR BLKSIZE DIFFERSFROM IMAGE HEADER

ExplanationThe Recovery utility compared the data set logicalrecord and the block size for the data set beingrecovered and detected a difference between the DBDvalues and the values in the input image copy headerrecord, or differences between CINV and LRECL (asdefined to VSAM) and the values in the input imagecopy header record.

System actionIf an ABEND control statement is provided, abend0302 is issued. Otherwise, processing continues, buta return code of 8 is generated.

Programmer responseThe DBD contains the data set logical record and theblock size that is different from the header values ofthe same data set. Verify that the DBD name andthe ddname are correct, and that the DBD was notchanged. If the output is a preallocated VSAM dataset, ensure that the CINV and LRECL values defined toVSAM agree with the DBD values.

Problem determination2, 3, 8, 35. If running under the Utility Control facility,rerun the job with a FUNCTION=OP, MSGNUM=965control statement in the DFSYSIN data set. Supply aSYSUDUMP DD statement to this step.

Module:DFSURDB0






DFS966W RECOVERY OF ROOT ONLY VSAMESDS HISAM DATA BASE ddnameNOT REQUIRED

ExplanationOne of the following conditions existed:

• You attempted to access the ESDS of a root-onlyVSAM HISAM database. This data set is not used byIMS and is not required for processing. It cannot beimage-copied or recovered.

• The specified ddname does not belong to thisdatabase.

System actionThe utility completes normally without image copyingthe ESDS or recovering the ESDS data set.

Operator response:If running under the Utility Control facility, rerunthe job with a FUNCTION=OP, MSGNUM=966 controlstatement in the DFSYSIN data set. Supply aSYSUDUMP DD statement to this step.

Programmer responseIf condition 1, above, does not pertain, verify that theddname belongs to this DBD and that it is spelledcorrectly. Correct any error and rerun the job.


Module:DFSRCP00


DFS967I WARNING-EMPTY DATASET-DDNAME-ddname

ExplanationThe Image Copy utility found the specified data set tobe empty.

System actionThe utility completes processing with a return code of4.

Programmer responseIf the empty data set condition is invalid, ensure thatall input is correct and resubmit the job.

Module:DFSUDMP0

DFS968I DBD=dbdname WITHINPSB=psbname SUCCESSFULLYBACKED OUT

ExplanationThis message identifies a successful backout for thenamed database.

Module:DFSRBOI0

DFS969I ERROR LOADING PSB xxxxxxxxFOR BACKOUT

ExplanationDL/I blocks could not be loaded for a PSB requiringbackout. The reason might be insufficient pool space,an I/O error (message DFS561 was issued), orerrors occurring during IMS initialization (appropriatemessages were issued).

System actionBackout is not done. The program and databasesrequiring backout are stopped. Processing continues.

Operator responseRun the Batch Backout Utility for the PSB namedbefore starting the PSB and databases.

Problem determination1, 5, 8, 11; and a memory dump taken with the /CHECKPOINT FREEZE ABDUMP command.

Module:DFSRBOI0

Related information“DFS561E” on page 202GETMAIN FAILED FOR QSAVE AREA, ACBLOAD/READ TERMINATED“DFS561A” on page 202ERROR READING ACBLIB, {PSB=psbname|DMB=dmbname}“IMS problem determination” on page 11



DFS970I (UNEXPECTED STATUS| OPNDST/OPNSESS FAILED| CLSDST/TRMSESS FAILED| GENCB/MODCBERROR| FORCED CLEANUP DONE|SESSION FAILURE), NODE nodename, USER/user name| N/A,(UNDEFN | SETLOG | SIMLOG |OPNDST | OPNSEC | CLSDST |SEND|RECEIV | TRMSES | RQR| RESTSR | INQUIR|SESSNC |******), RC=,FDB2=, LOSTERM=|NSEXIT=| UNBIND=, SENSE=,REASON=

ExplanationThe following explains the function and commands ofthis message:

Function: Indicates function being performed whenfailure occurred:UNEXPECTED STATUS

RC,FDB2, and RPLREQ field in the RPL hadan invalid combination (that is, SEND operationcompleted with an invalid return code beingreturned for SEND), or LOSTERM EXIT wasscheduled.

OPNDST/OPNSESSFailure occurred during OPNDST/OPNSESSprocessing.

CLSDST/TRMSESSFailure occurred during CLSDST/TRMSESSprocessing.

GENCB/MODCB ERRORA failure occurred during the attempt to set up theRPL or NIB for an OPNDST or CLSDST.

FORCED CLEANUP DONEA /CLS FORCE command was issued to simulatean NSEXIT with a cleanup RU to free a hung nodewith outstanding I/O. RC, FDB2, and RPLREQ arefrom the RPL with the outstanding I/O.

SESSION FAILEDNode connection terminated.

Command: Indicates type of command being runwhen failure occurred:UNDEFN

RPL has an undefined value in the RPLREQ field.SETLOG

Failure occurred during SETLOGON command.

SIMLOGFailure occurred during SIMLOGON command.

OPNDST|OPNSECFailure occurred during OPNDST or OPNSECcommand.

CLSDST|TRMSESSFailure occurred during CLSDST or TRMSESScommand.

SENDFailure occurred during SEND command.

RECEIVFailure occurred during RECEIVE command.

RESETSRFailure occurred during RESETSR command.

INQUIRFailure occurred in attempting to inquire for BINDparameters.

SESSNCFailure occurred during SESSIONC command.

RQRInvalid VTAM RQR command was received by IMSfor this node.

******Normal if there was no operation in progress, orLOSTERM has a hexadecimal value.

Error Data:

• RC=value in the RPLRTNCD field.• FDB2=value in the RPLFDB2 field.• LOSTERM=|NSEXIT=value passed to the IMS

LOSTERM or NSEXIT exit by VTAM.

– X'0C' - LOSTERM– X'29' - NSPE Cleanup RU– X'20' - NSPE Notify RU– X'B0' - Unbind received– X'00' - Neither LOSTERM nor SPE

• UNBIND=unbind code passed to IMS SCIP exit byVTAM.

• SENSE=sense code passed from VTAM, DEVICE, orNSEXIT.

• REASON=reason code generated by NSEXIT orUNBIND

See z/OS Communications Server SNA Programming(SC31-8829) for a more detailed description of VTAMindicators and sense values.

System actionACF/VTAM terminated the session, but IMS continuesprocessing.


Operator response:(master terminal) Try to start the session afterdiagnosing the problem.



Module:DFSCM7A0, DFSCVCS0, DFSCVHA0, DFSDN280

Related referencez/OS: Exception conditions and senseinformationRelated information“IMS problem determination” on page 11IMS messages and codes problemdetermination is accomplished by usingprocedures established by IBM.

DFS971I (I/O ERR|INT REQ) NODE nodename, ssbytes, error description

ExplanationAn I/O operation to an IBM 3270 device completedabnormally. The ssbytes are 3270 sense/status bytesout of the RPL as passed to IMS by VTAM. The error-description-field VTAM indicators are:PATH

A recoverable-path error occurred.CPM

An unrecoverable error occurred.STATE

An error occurred in the use of bracket indicatorsby the node.

FIA function-interpreter error occurred.

RRA request-reject error occurred.

The error-description-field sense/status indicatorsare:DB

Device BusyUS

Unit SpecifyDE

Device EndTC

Transmission CheckCR

Command Reject

IRIntervention Required

ECEquipment Check

DCData Check

CCControl Check

OCOperation Check

Tip: See z/OS Communications Server SNAProgramming (SC31-8829) for VTAM indicators andinformation about 3270 sense or status indicators.

System actionCLSDST the node except for intervention-requiredconditions. On intervention-required processing, theoperation continues normally after the node (terminal)is made ready.

Operator response:Attempt to OPNDST the node and continue operationif possible; if not possible, see Problem determination.For intervention-required processing, make the nodeready and processing should continue normally. ObtainIMS Transaction Manager trace of the failure.


Module:DFSCVEO0

Related referencez/OS: Exception conditions and senseinformationz/OS: Summary of control requests andindicatorsRelated information“IMS problem determination” on page 11IMS messages and codes problemdetermination is accomplished by usingprocedures established by IBM.

DFS972A *IMS (DCCTL) AWAITING MOREINPUT*

ExplanationA multisegment message was started from the systemconsole. More data is required to complete themessage. If (DCCTL) is displayed in the message, youare in the DCCTL environment.

System actionProcessing continues, but ITASK waits for input.






http://www-01.ibm.com/support/knowledgecenter/SSLTBW_2.4.0/com.ibm.zos.v2r4.istprg0/sumctl.htm?lang=en

http://www-01.ibm.com/support/knowledgecenter/SSLTBW_2.4.0/com.ibm.zos.v2r4.istprg0/sumctl.htm?lang=en

Operator response:Enter the required segments, ending the last segmentwith a period.

Module:DFSDNSC0

DFS973I LINE xxx, PTERM yyy, aaa, {G|S},tttt, ssss, conditions

ExplanationA remote 3271/3275 online aaa, which is IMS linexxx, physical terminal (PTERM) yyy, has sent IMS asense-status message containing information otherthan a device-end (X'C240'). The message was sentin response to a specific or general poll from IMS,as represented by an S or a G. The terminal addresssent by the 3270 is displayed in the field representedby tttt, and the sense-status bytes are displayed infield ssss. The sense-status bytes are interpreted andprinted in the conditions area. The interpretations havethe following meanings:Byte

MeaningDB

Device busyUS

Unit specifyDE

Device endTC

Transmission checkCR

Command rejectedIR

Intervention requiredEC

Equipment checkDC

Data checkCC

Control checkOC

Operation check

Operator response:If message DFS072I, DFS251I or DFS0253 is alsoreceived for the 3270 terminal, the information in thismessage should be given to the IBM representative.


Module:DFSC3270

Related information“DFS072I” on page 51UNABLE TO OUTPUT LINE x PTERM y“DFS251I” on page 95hh.mm.ss CONTROL UNIT INOPERABLE LINE xPTERM y-z aa,bbbb,cc,dd,ee,ff,gg,hh, iiii,jjjj“DFS253” on page 96TCU INOPERABLE LINE x PTERM y“IMS problem determination” on page 11IMS messages and codes problemdetermination is accomplished by usingprocedures established by IBM.

DFS0974I SEGMENT xxxxxxxx IN DATABASEyyyyyyyy HAS AN INVALID DELETERULE FOR SEGMENT DATA USEREXITS

ExplanationSegment xxxxxxxx in database yyyyyyyy has a deleterule that is not supported for exits defined on the DBD/SEGM statement as EXIT=.

System actionProcessing terminates with RC=8.

Programmer responseCorrect the EXIT= definition.

Problem determination:2, 3, 8, and 19

Module:DFSDLB00


DFS975W NON-RECOVERABLEDBD=xxxxxxxx WITHINPSB=yyyyyyyy STOPPED DUE TOUNKNOWN BACKOUT STATUS

ExplanationIMS encountered a situation in which the databasesmodified by application yyyyyyyy needed to be backedout. The backout could not be completed. Databasexxxxxxxx is stopped. Because this is a non-recoverabledatabase, IMS does not make any further attempt toback it out. It should not be started until it has beenrestored to an acceptable condition.


System actionThe database xxxxxxxx is stopped.

System programmer responseRestore the database.

Module:DFSRBOI0, DFSRBLB0

DFS976I nnn MESSAGES(S) PURGED, xPURGED MSG(S) REROUTED, DEQCMD SUPPRESSED BY MESSAGECONTROL ERROR EXIT

or

nnn MESSAGE(S) PURGED, x PURGED MSG(S)REROUTED

or

nnn MESSAGES(S) PURGED, DEQ CMD SUPPRESSEDBY MESSAGE CONTROL ERROR EXIT

ExplanationThe /DEQUEUE command for NODE, LTERM, andMSNAME causes the invocation of Message Control/Error Exit before the processing of each message. A /DEQUEUE command with the PURGE keyword causedthe number of messages (nnn) to be purged from themessage queue. A purged Fast Path message, if any, isincluded in the displayed count of purged messages.

The user exit requests to purge the messages fromthe queue and then reroute them to a differentdestination. The variable x is the number of purgedmessages that were rerouted.

System actionThe command completed successfully.

Operator response(master terminal) This message results when theMessage Control/Error Exit is customized in thereceiving system to specify an incorrect exit flag, orthe exit flag is correct but an error was found whileIMS was performing the requested action and theassociated default was performed. Inform the systemprogrammer

System programmer responseFind the default action from Message Control/ErrorExit DFSCMUX0. Look for the error description inthe MSNBMSG area of Message Control/Error Exitinterface block MSNB, which is a forced log entry inthe X'6701' CMEI record for send error, receive error,and the DEQ command. Correct the exit flag or thedestination for reroute, if appropriate.


Module:DFSICLJ0


DFS976I nnn MESSAGES(S) PURGED, xPURGED MSG(S) REROUTED, DEQCMD SUPPRESSED BY MESSAGECONTROL ERROR EXIT

or

nnn MESSAGE(S) PURGED, x PURGED MSG(S)REROUTED

or

nnn MESSAGES(S) PURGED, DEQ CMD SUPPRESSEDBY MESSAGE CONTROL ERROR EXIT

ExplanationThe /DEQUEUE command for NODE, LTERM, andMSNAME causes the invocation of Message Control/Error Exit before the processing of each message. A /DEQUEUE command with the PURGE keyword causedthe number of messages (nnn) to be purged from themessage queue. A purged Fast Path message, if any, isincluded in the displayed count of purged messages.

The user exit requests to purge the messages fromthe queue and then reroute them to a differentdestination. The variable x is the number of purgedmessages that were rerouted.

System actionThe command completed successfully.


Operator response(master terminal) This message results when theMessage Control/Error Exit is customized in thereceiving system to specify an incorrect exit flag, orthe exit flag is correct but an error was found whileIMS was performing the requested action and theassociated default was performed. Inform the systemprogrammer

System programmer responseFind the default action from Message Control/ErrorExit DFSCMUX0. Look for the error description inthe MSNBMSG area of Message Control/Error Exitinterface block MSNB, which is a forced log entry inthe X'6701' CMEI record for send error, receive error,and the DEQ command. Correct the exit flag or thedestination for reroute, if appropriate.


Module:DFSICLJ0


DFS977I INOP/NA: n n n n

ExplanationThe 2770 terminal recognized a component error andhas marked a component inoperable. After the errorhas been processed, this message is printed at the2770 terminal if there is an available printer or 2265component to receive the message. The messagedepicts the current terminal status. All inoperable ornot-attached component slots have their slot number(n) placed in the message.

Operator responseCorrect the error condition at the terminal, verify dataprocessed by the system. Then issue the appropriatecomponent restart command.

Module:DFSDN090

DFS978I PLEASE RESEND LAST LINE

ExplanationAn I/O error has occurred reading the last segment.

Explanation:

Reenter the last segment, or, if wanted, use a /CANCELcommand to cancel all previous segments.


Module:DFSCLMO0, DFSDS050


DFS979I BATCH MESSAGE PROGRAMpsbname WAS ACTIVE AT TIME OFFAILURE

ExplanationEmergency restart has determined that the batchmessage program indicated by psbname was active atthe time of the failure that necessitated the emergencyrestart.

This message can also occur from a failure during abackout process during other processing.

System actionBy restart - the program and its associated databasesare stopped. Message DFS981I accompanies thismessage to identify the stopped databases.

Operator response:(master terminal) Run the Batch Backout utility,DFSBBO00, as described in, using the same tapesas entered for the emergency restart. Then start theprogram and databases, and rerun the batch messageprogram.


Module:DFSRBLB0, DFSRBOI0


DFS980I hh:mm:ss BACKOUT PROCESSINGHAS ENDED FOR PSB psbname

ExplanationThe database backout facility has ended for the namedPSB. This situation can occur during emergency restart


or dynamic backout during online execution withprogram isolation.

Message DFS968I or DFS981I precedes this messagefor each database within the PSB involved in thebackout.


Module:DFSRBOI0

Related information“DFS968I” on page 347DBD=dbdname WITHIN PSB=psbnameSUCCESSFULLY BACKED OUT“DFS981I” on page 353DBD=dbdname WITHIN PSB=psbnameSTOPPED DUE TO (BACKOUT FAILURE|ERENOBMP START|COLDBASE START|REMOTETAKEOVER)

DFS981I DBD=dbdname WITHINPSB=psbname STOPPED DUE TO(BACKOUT FAILURE|ERE NOBMPSTART|COLDBASE START|REMOTETAKEOVER)

ExplanationThis message identifies a database that was stoppedfor the specified reason.

Programmer responseIn all cases, you must do a backout for the database.For the BACKOUT FAILURE and ERE NOBMP STARTreasons, you can do the backout by entering a /STARTDB or UPDATE DB START(ACCESS) command. Forthe COLDBASE START reason, you must do a batchbackout. For the REMOTE TAKEOVER, a forwardrecovery followed by a batch backout are required.

Module:DFSRBOI0, DFSRBLB0

DFS982I I/O ERROR READING BACKOUTQUEUE, BSN=bbbbbbbb RC=rr

or

I/O ERROR READING BACKOUT QUEUE COVERINGSYSTEM CHKPT=yyddd/hhmmss BSN=bbbbbbbbRC=rr

ExplanationThe first message is issued only in batch. The secondmessage is the online (TM and DBCTL) form of themessage, where yyddd/hhmmss is the last systemcheckpoint ID that occurred before the start of theunit-of-recovery being backed out. An error occurredwhile reading the log. If an I/O error occurred,message DFS0414I should be issued.

If DBRC is active, it must be notified when thedatabase is recovered. If DBRC is inactive, thismessage might be issued again, even though recoveryis no longer required. DBRC is notified automaticallywhen Batch Backout is run.

This message can also be issued when a problemoccurs and there is an excessive number of recordsto back out and some records needed for backout hadalready been archived.

In the message text:bbbbbbbb

Indicates the log block sequence number.rr

Indicates the log return code.

System actionIMS processing continues, but the backout fails.

For the first form of this message, take the X'67FF' logrecords to the IMS log.

For the second form of this message, take thesupervisor call (SVC) dump.

Module:DFSRBOI0

DFS983I I/O ERROR IN DATA BASExxxxxxxx, PROGRAM xxxxxxxxDURING BACKOUT.

ExplanationAn I/O error occurred while emergency restartor dynamic backout was attempting to back outincomplete transactions for the database and programspecified. The database is stopped, and processing isallowed to continue against the remaining databases.

This message can be issued with PURGE in the placeof the database name. This indicates that the call topurge the buffers used for this backout has failed.Subsequently, to protect database integrity and ensurethat all transactions against the database and PSB arebacked out, batch backout should be performed.


System actionThe database is stopped and normal processingcontinues.

Operator response:(master terminal) When the recovery and backoutare complete, the user should start the databaseand program with the appropriate master terminalcommands.

Programmer responseThe user should run the Data Base Recovery utilityagainst the database. When the recovery is complete,the Data Base Backout utility should be run, specifyingthe program indicated in the error message andthe same tapes used for input to the emergencyrestart. Running the Batch Backout utility after thiserror message might result in message DFS888Ibeing returned from batch backout indicating nobackouts exist for PSB xxxxxxxx. If the correct inputtapes were used, DFS888I indicates that the prioremergency restart or dynamic backout did successfullybackout the incomplete transactions for the database /program name, before the I/O error was incurred.


Module:DFSRBOI0

Related referenceRecovery utilities (Database Utilities)Related information“DFS888I” on page 324NO DATA BASE RECORDS FOUND FOR PSBpsbname (AFTER CHECKPOINT checkpoint id)(FOR REGION region id)“IMS problem determination” on page 11IMS messages and codes problemdetermination is accomplished by usingprocedures established by IBM.

DFS984I UNABLE TO OPEN DATA BASExxxxxxxx, PROGRAM xxxxxxxx FORBACKOUT.

ExplanationEmergency restart was unable to open a data set forbackout processing.

System actionThe database and the program are stopped andnormal processing continues.

Operator response(master terminal) After database recovery or backout,or both, are complete, the user should start thedatabase and the program with the appropriate masterterminal commands.

Programmer responseCheck the DD statement for the database involvedand make certain it is online. If the JCL is correct,the failure that prompted the emergency restartmight have damaged the database. If so, follow theprogrammer response for message DFS983I. If thisis not the case, run the Database Backout utilityspecifying the program indicated in the error messageand the same tapes used for input to the emergencyrestart.


Module:DFSRBOI0

Related referenceDatabase Recovery utility (DFSURDB0)(Database Utilities)Related information“IMS problem determination” on page 11IMS messages and codes problemdetermination is accomplished by usingprocedures established by IBM.

DFS985I SYSTEM ERROR DURINGBACKOUT FOR DB=dddddddd,PGM=pppppppp, LOGSEQ=yyyyyyyy, RC=zzzzzzzz

ExplanationAn error occurred while emergency restart or dynamicbackout was attempting to back out incompletetransactions for data base dddddddd and programpppppppp. The field yyyyyyyy is the hexadecimalsequence number of the data base change logrecord being processed. The field zzzzzzzz is either apseudoabend code that occurred during backout, thevalue 4, or the value 10. A value of 4 or 10 indicates anerror other than a pseudoabend occurred.

System actionThe database and the program are stopped, andprocessing continues. A type X'67FF' pseudoabend iswritten to the log data set.


http://www.ibm.com/support/knowledgecenter/SSEPH2_15.1.0/com.ibm.ims15.doc.dur/ims_dur04.htm#ims_dur-gen3

http://www.ibm.com/support/knowledgecenter/SSEPH2_15.1.0/com.ibm.ims15.doc.dur/ims_dfsurdb0.htm#ims_dfsurdb0

http://www.ibm.com/support/knowledgecenter/SSEPH2_15.1.0/com.ibm.ims15.doc.dur/ims_dfsurdb0.htm#ims_dfsurdb0

Operator response(master terminal) For the first case, reinitialize IMS;then retry the emergency restart. For the secondcase, start the database and the program withthe appropriate master terminal operator after thedatabase recovery or backout, or both, are complete.

Programmer responseThe following two cases should help determine andresolve the problem:

• If RC=00000004 is received during /ERE processing,a data management block (DMB) directory entrymight not have been found for the database beingbacked out. Be sure the IMS nucleus used to restartthe system is the same one in use at the time ofthe original system failure. If this is the problem,restart the IMS job specifying the correct nucleus;then rerun the emergency restart.

• If RC=00000010 is received, the most likely reasonis because register 3 contained a negative valuewhen the CSRCESRV macro was issued.

• If RC=Uxxxx (xxxx is the pseudoabend code thatoccurred during /ERE or Dynamic Backout), orRC=00000004 and the first case is not the problem,then the type X'67FF' pseudoabend record on thelog data set is needed to determine the cause of theproblem. Run the Database Backout utility specifyingprogram pppppppp and either the logs used for inputto the emergency restart or the logs in use at thetime of the dynamic backout.

Problem determination:1, 5, 8, 17b

Module:DFSRBOI0


DFS986A CANNOT OPEN SYSTEM DATASET-DD NAME-nnnnnnnn, RC=xx

ExplanationA DD statement was missing or a data set requiresformatting. During a restart with formatting, an I/Oerror might have occurred in the data set indicated bynnnnnnnn. Return code xx is defined as follows:Code (hex)

Meaning00

This condition is normal.

04The DCB is already being opened or closed.

08The DCB is already open.

0CThe DECBTYPE is invalid.

10A failure occurred in the IMS SVC. DCBWRK1indicates the reason. See message DFS0730I forerror subcodes.

14An I/O error occurred while the OSAM OPENroutine was scanning for a file mark, formatting,or writing a file mark. See DECBSTAT for additionalinformation.

18An invalid RBN was calculated. The RBN is either0 or greater than the maximum RBN for the dataset. When multiple data sets are defined for theshort or long message queue, the error mightbe caused by the incorrect space specificationof the multiple data sets. See the topic onIMS.QBLKS, IMS.SHMSG/1-9, and IMS.LGMSG/1-9in the installation information and the topic onmessage queue data set allocation in IMS Version15 System Administration.

24An error occurred during EOV processing for thedata set.

28While opening the Queue Manager system dataset, an invalid ddname was found.

System actionIMS waits for another restart command to be entered.

Operator response(master terminal) Reenter the restart command withBLDQ and FORMAT keywords, as appropriate.

Programmer responseMake sure that a DD statement exists for thereferenced data set, and if DISP=OLD, the data set isavailable to the system.


Module:DFSQDOC0

Related informationDFS0730I


CANNOT OPEN SYSTEM DATASET-DD NAME-nnnnnnnn, RC=xx“IMS problem determination” on page 11IMS messages and codes problemdetermination is accomplished by usingprocedures established by IBM.

DFS987I ERROR READING SLDSDURING BACKOUT WITHINPSB=XXXXXXXX DUE TO NON-RECOVERABLE DB

ExplanationIMS encountered an archived log record for a non-recoverable database while reading the SLDS duringdynamic backout. Because this record cannot be usedfor a backout, IMS makes no further attempt toback it out. The backout could not be completed. Donot restart the backout until the database has beenrestored to an acceptable condition.

Message DFS981I or DFS975W follows this messagefor each database within the PSB involved in thebackout.

System actionThe database is stopped. IMS processing continues,but the backout fails.

Programmer responseFor non-recoverable database, restore the database.For recoverable database, run the batch backoututility.

Module:DFSRBOI0

Related informationDFS975WNON-RECOVERABLE DBD=xxxxxxxx WITHINPSB=yyyyyyyy STOPPED DUE TO UNKNOWNBACKOUT STATUSDFS981IDBD=dbdname WITHIN PSB=psbnameSTOPPED DUE TO (BACKOUT FAILURE|ERENOBMP START|COLDBASE START|REMOTETAKEOVER)

DFS0988I GLOBAL rsrcstat STATUS UPDATEREQUEST FOR rsrctype COMPLETE

ExplanationA type-1 global command was issued, and thedatabase or DEDB status was updated in the ResourceManager (RM). The request can be successful for

some, all, or no resources. If the request is notsuccessful for some or all resources, messageDFS3308I precedes this message. The DFS3308Emessage includes the RM return and reason code andidentifies the database or DEDB area whose statuswas not updated. You can issue the command QRY DBSTATUS(GLOBAL) to verify the status of the resourcesin RM.rsrcstat

Indicates the status of the resource, as shown inthe following table:

Table 6. Resource status

rsrcstat Meaning

STA The resource is started globally.

STOACC The resource is stopped for accessglobally and is offline.

STOPPED The resource is stopped globally.

STOSCHD The resource is stopped globally.

STOUPDS The resource is stopped forupdates globally.

rsrctypeIdentifies the resource type as either database orDEDB area.

System actionIMS continues to process commands.


Module:DFSIUS10

Related information“DFS3308E” on page 928csltype REQUEST ERROR, macronameRC=xxnnnnnn RSN=ssssssss

DFS989I IMS (DBCTL) READY (CRC=x)

ExplanationThe Database Control (DBCTL) subsystem is ready forcommand input. Its command recognition character(CRC) is x.

Operator responseEnter the appropriate restart command.

Module:DFSXCIC0


DFS990I LAST number CARDS NOTPROCESSED

ExplanationThe 2770 terminal recognized an error and discardedthe data stream. number is the number of cards notprocessed.

Operator response(entering terminal operator) Correct the card in error,and resubmit the job from that point.

Module:DFSDN050, DFSDN090

DFS991I IMS SHUTDOWN

ExplanationThis message is sent to all active terminals when thesystem is shut down.

Module:DFSICIO0

DFS992I DMB POOL TOO SMALL, UNABLETO SCHEDULE PSB psbname

ExplanationThe named PSB cannot be scheduled because thedata management block pool is too small to hold allof the required data management blocks.

Programmer responseChange the appropriate parameter to make the poollarger, and restart the system.

Module:DFSDPDM0

DFS993I (CSA PSB|DLS PSB|PSBW) POOLTOO SMALL, UNABLE TOSCHEDULE PSB PSBNAME.


• The named PSB cannot be scheduled because it istoo large to fit in the indicated (CSA|DLS) PSB pool.If the DL/I subordinate address space option is notselected, the entire PSB is in the CSA PSB pool. IfDL/I subordinate address space is selected, part ofthe PSB is in the CSA PSB pool and part in the DLSPSB pool.

• The work area needed by this PSB is too large to fit inthe PSBW pool.

System actionThe PSB is stopped.


• For the first problem, use this information: The sizeof the PSB pool for non-DL/I subordinate addressspace environments is specified using the PSB=parameter on the control region JCL. In a DL/Isubordinate address space environment, CSAPSB=and DLIPSB= are the sizes of the CSA PSB pool andthe second PSB pool in DL/I subordinate addressspace local storage. The output of the ACBGEN utilityfor the PSB psbname indicate how much space isrequired in these pools.

• For the second problem, use this information:The size of the PSBW pool is specified on thePSBW= parameter in the control region JCL. Theoutput of the ACB Maintenance utility for the PSBpsbname (WORKAREA= ) indicates how much spaceis required in the PSBW pool.

Module:DFSDPDM0

DFS994I *CHKPT yyddd/hhmmss*ctype

or

rtype START COMPLETED

or

IMS SHUTDOWN COMPLETED

or

IMS SHUTDOWN (DBCTL) COMPLETED

or

IMS SHUTDOWN (DCCTL) COMPLETED

or

STATISTICS CHECKPOINT COMMAND COMPLETED


or

XRF TAKEOVER COMPLETED

ExplanationA checkpoint was written to the IMS system log, as theresult of one of the following:

• A restart command• A /CHECKPOINT command• A /DBRECOVERY command• A /DBDUMP command• Automatic initiation by the IMS system logger• A completed XRF takeover by the alternate IMS

system

Upon completion of restart, the restart type isprovided. During termination of IMS, the shutdowncompletion message is issued. The values of yyddd/hhmmss, ctype, and rtype are:

• yyddd/hhmmss is the time stamp that identifies thecheckpoint.

• ctype is the checkpoint type. Possible values are:*SIMPLE*, *FREEZE*, *DUMPQ**, *SNAPQ**, and*PURGE**.

• rtype is the restart type. Possible values are:

COLDWARMEMERGENCYBUILDQ WARM*BUILDQ* EMERGENCY*COLDBASE* EMERGENCY*COLDBASE* *BUILDQ* EMERGENCY*COLDCOMM* EMERGENCY*COLDSYS* EMERGENCY

System actionNormal processing continues or IMS terminates,depending upon the checkpoint type.

For the IMS SHUTDOWN (DBCTL) COMPLETED formof the message, the DBCTL terminates. For theIMS SHUTDOWN (DCCTL) COMPLETED form of themessage, the DCCTL terminates.

For the STATISTICS CHECKPOINT COMMANDCOMPLETED form of the message, IMS performancestatistics records are written to the system log. Thischeckpoint is not a restart checkpoint.

For the XRF TAKEOVER COMPLETED form of themessage, some of the recovery functions might still

be active. In this case, new transactions that are not inconflict with recovery processing are allowed to run inparallel with the recovery processing.


Module:DFSRCP00, DFSRST00, DFSTERM0

DFS0995A RECALL FAILED - DFHSM NOTACTIVE - REPLY: RETRY, ORCANCEL (CANCEL DISABLESRECALL FUNCTION)

ExplanationA RECALL request received a return code indicatingthat DFHSM was not active.

System actionIMS waits for a response to the message.

Operator responseEnter one of the following responses:RETRY

Triggers another recall request from IMS.CANCEL

Disables the recall function for the remainder ofthe IMS control region execution.

Module:DFSDYA00

DFS996I IMS (DCCTL) READY

ExplanationIf the environment is DCCTL, then (DCCTL) isdisplayed in the message. If the environment isTM/DB, then (DCCTL) is not displayed in the message.This message appears at the system console as aWTOR.

Operator response:(local/remote terminal) Reply to this message whenthe user wants to enter data through the systemconsole.

Module:DFSDNSC0

DFS997I MORE SEGMENTS REQUIRED

ExplanationA partial multisegment message was entered from anIBM 2740 Model 2 terminal.


System actionThe action is determined by the local/remote terminaloperator.

Operator response:(local/remote terminal) Complete the message, orcancel it.

Module:DFSDN040

DFS998I LINE xxx PTERM yyy ISINOPERABLE

or

VTAM NODE xxxxxxxx IS INOPERABLE

or

VTAM RC xx FEEDBACK yy REASON zz

ExplanationAttention: IMS no longer supports BTAMterminals.

This message has the following forms:For the first form of this message:

An I/O error occurred on LINE xxx PTERM yyyFor the second form:

An I/O error occurred on NODE xxxxxxxx.For the third form:

VTAM detected an error. See z/OS CommunicationsServer SNA Programming (SC31-8829) andz/OS Communications Server IP and SNACodes (SC31-8791) for descriptions of the RC,FEEDBACK, and the REASON codes supplied in theVTAM RPL control block.

System actionFor the first and second forms: The PTERM is markedPSTOPPED and inoperable and processing continues.

For the third form: this problem is an unrecoverableVTAM error. IMS stops all communication with VTAMand, therefore, all the NODEs associated with IMS.Communication cannot continue until IMS is shutdown and restarted.

Operator responseFor the first form: enter an /RSTART LINE x PTERMy command.

For the second from: enter an /RSTART NODE xxcommand.

Module:DFSICIO0, DFSCIOB0, DFSCMBP0

Related referencez/OS: RPL-Create a request parameter listz/OS: Return codes for VTAM macroinstructions

DFS999I HELD CONVERSATION ID IS xxxx

ExplanationThis message is the response to a /HOLD command.

Operator response:The identification (ID) given must be used to end (/EXIT) or resume (/RELEASE) the conversation.

Module:DFSICLH0

DFS1000I IMSrrr ABENDUaaaa MODULE=xxxxxxxxLABEL=xxxxxxxx R14=xxxxxxxx(DLA=xxxxxxxx)

ExplanationA processing error was detected by the extendedcheckpoint module (DFSZSC00), the extended restartpositioner (DFSZSR00, DFSZDC00) or the GSAM BSAMI/O MODULE (DFSZDC00). An attempt to write or readthe symbolic checkpoint records to or from the OLDSor IMSLOGR data set failed.

In the message text:IMSrrr

IMS release level.Uaaaa

IMS user abend code.MODULE=

Module that issued the abend.LABEL=

Unique label at which the abend was issued. Thislabel corresponds to the error reason code. Fora description of each code, see the appropriateabend code. For a description of each code, seethe appropriate abend code.

R14=BAL return register (to module that discovered theerror)


http://www-01.ibm.com/support/knowledgecenter/SSLTBW_2.4.0/com.ibm.zos.v2r4.idad500/x6j.htm?lang=en

http://www-01.ibm.com/support/knowledgecenter/SSLTBW_2.4.0/com.ibm.zos.v2r4.cs3cod0/return.htm?lang=en

DLA=The BAL return register (to module that issued theabend).

System actionThe program terminates abnormally with the abendcode identified as Uaaaa.

Operator responseDetermine the cause of the error, correct the problem,and rerun the job.

Module:DFSZSR00, DFSZDC00

Related conceptsIMS abend codes (Messages and Codes)Related informationIMS abend 0102






DFS1001I INVALID ALLOCATION FORSYSTEM DATA SET- DD NAME -NNNNNNNN, RC=xx

ExplanationWhile processing the Queue Manager system dataset's DD statements, an invalid allocation for thesystem data set was detected.

The reason codes and their meanings are:

Reason code (hex)Explanation

04The ddname information returned from theDEVTYPE macro indicates the DD statement ismissing.

08The ddname information returned from theDEVTYPE macro indicates a parameter of DUMMY.

0CThe ddname information returned from theDEVTYPE macro indicates a SYSIN/SYSOUTallocation.

System actionThe indicated ddname NNNNNNNN of the system dataset will not be used during the current execution ofIMS.

Operator responseContact the system programmer.

Programmer responseIf the referenced system data set is required, correctthe JCL, the system data set allocation, or both.

ModuleDFSIINO0, DFSQDOC0

DFS1002A IXLFORCE REQUEST TIMEOUT FORSTRUCTURE=xxx, CONNAME=yyy

ExplanationThe new, active IMS cannot delete the failed persistentconnection in the old IMS because it is still active.

System actionIMS processing continues.

System programmer responseIf the new, alternate IMS is restarted using thesame IMS ID as the failed IMS, the failed persistentconnection is changed to active. If the alternate XRFcannot be restarted, or the new IMS ID is not the sameas the old IMS ID, use the following XCF command todelete the connection after the old IMS terminates:

SETXCF FORCE,CONNECTION,STRNAME=xxx,CONNAME=YYY

DFS1003I LERUNOPT OVERRIDESINITIALIZED FROM imsidRC=rrrrrrrr, RSN=ssssssss

ExplanationIndicates the LERUNOPTS have been initialized. Whenthe phrase FROM imsid in the message, it indicatesthat the runtime options have been initialized fromanother IMS. The imsid indicates what IMS theinformation was received from. RC is the return codefor the process. RSN is the reason code for theprocess.

The following table shows the return and reason codesfor DFS1003I:

Table 7. Return and reason codes for DFS1003I

Return code Reason code Meaning

0 0 LERUNOPTS havebeen successfullyinitialized andprocessingcontinues normally.

X'02000014' X'5000' IMS encountereda storage failureduring theLERUNOPTS. LEruntime parametersare not initialized.LE parameteroverride processingis disabledand processingcontinues normally


System actionDepends on the return and reason codes.

Programmer responseIf there is a storage failure, allocate more ECSAstorage.

ModuleDFSLEP10

DFS1004I LE PARAMETER OVERRIDEPROCESSING state

ExplanationIndicates a change in LE parameter overrideprocessing for the system. State can be eitherENABLED, indicating overrides are allowed, orDISABLED, indicating overrides are not allowed.

Note: If you want to enable or disable theLERUNOPTS, use the keyword LEOPT=Y or N on theDFSCGxxx member of the PROCLIB.

The following table shows the return and reason codesfor DFS1004I:

Table 8. Return and reason codes for DFS1004I


0 0 LERUNOPTS havebeen successfullyinitialized andprocessingcontinues normally.

X'02000014' X'5000' IMS encountereda storage failureduring theLERUNOPTS. LEruntime parametersare not initialized.LE parameteroverride processingis disabledand processingcontinues normally



ModuleDFSLEP00, DFSLEP10

DFS1005E DFSFEBJ0 ERROR.INCORRECT ROUTING TABLE.LTERM=nnnnnnnn MESSAGETEXT=xxxxxxxxxxxxxxxxxxxx

ExplanationExit routine DFSFEBJ0 processed a reply to a frontend switching message. The system identification inthe message text does not match an entry in the userrouting table. LTERM nnnnnnnn was the source of theFES reply message. This error message displays thefirst 20 bytes of the input message.

System actionThe reply message is discarded.

System programmer responseCheck the routing table and correct invalid or missingentries. If the table is correct, check the displayedmessage text and identify the source of the incorrectrouting information.

ModuleDFSCIOB0

DFS1006E DFSFEBJ0 ERROR. INVALIDFEIB FIELD. LTERM=nnnnnnnnRC=x DATA=yyyyyyyy MESSAGETEXT=zzzzzzzzzzzzzzzzzzzz

ExplanationExit routine DFSFEBJ0 processed a front end switchingmessage. A field to be specified by the exit routinein the front end interface block is invalid or missing.LTERM nnnnnnnn was the source of the message. Fieldyyyyyyyy contains the invalid information or, if data ismissing, '--NONE--'. Field zz...zz displays the first 20bytes of the message, if applicable. Reason code x hasone of the following meanings:Code

Meaning0

The new destination is missing or invalid. The exitroutine might have exited with RC=4 or RC=8.

1For exit with RC=4, timeout is specified without anERP name.


2For exit with RC=4, timeout is specified without amessage number.

3For exit with RC=8, the LTERM name of the originalinput terminal is missing or invalid.

4For exit with RC=8, the destination for a latereply is missing or invalid. A timeout for theoriginal input terminal for this message has alreadyoccurred.

5For exit with RC=4, the transaction code specifiedfor an ERP was invalid. Timeout processing cannottake place. A message text is not displayed withthis reason code.

6For exit with RC=4, the user message numberspecified for timeout processing was invalid.Timeout processing cannot take place. A messagetext is not displayed with this reason code.

System actionThe system action depends on the reason code.Code

Meaning0

The message is discarded. If the message wasinput from an ISC session and the exit routinespecified a valid error transaction in the FEIBERPfield, this error transaction is scheduled. If thetimer facility was specified, the original inputterminal is released; otherwise it hangs.

1,2The input message is discarded.

3The reply message is discarded. If the exitroutine specified a valid error transaction in theFEIBERP field, this error transaction is scheduled.If the timeout facility was specified on input,the terminal is released from response mode;otherwise it hangs.

4The reply message is discarded. If the exit routinespecified a valid error transaction in the FEIBERPfield, this error transaction is scheduled.

5,6The original input terminal is released fromresponse mode by this message.

System programmer responseCheck the displayed information and determine thesource of the incorrect data.

ModuleDFSCIOB0

DFS1007E DFSFEBJ0 ERROR. INVALID RC INREG.15. LTERM=nnnnnnnn

ExplanationThe Front End Switch exit routine DFSFEBJ0 specifiedan invalid return code. LTERM nnnnnnnn was thesource of the FES message.

System programmer responseCorrect the exit routine.

ModuleDFSCIOB0

DFS1008I PSB psbname REFERENCESPHIDAM DBD dbdname FOR LOADMULTIPLE TIMES

ExplanationThe named PSB contains more than one explicitreference to the named PHIDAM DBD with a PROCOPTof L or LS.

System actionAbend 09067 is issued if batch DL/I was running.ACBGEN processing continues if the ACBGEN utilitywas running.

Programmer responseCorrect the PSB and run the program again.

ModuleDFSDLBL0

DFS1009I name HAS BEEN REPLACED

ExplanationThe block as identified by name has been replacedin the format library by Phase 2 of the MFS languageutility.


Note: name is an interpreted description of the blockbeing replaced. An interpreted description of the namecontains:

• FMT/MSG label.• Block type: DOF, DIF, or MSG.• Size of the block in hexadecimal.• If FMT: device type, device model if 3270 or 3270P,

device features in hexadecimal, device featuresinterpreted in EBCDIC, device screen size if 3270-An, version ID if DPM-An or DPM-Bn.

• Date and time the indicated block was created.


ModuleDFSUTLN0

DFS1010I name HAS BEEN DELETED -ddname

ExplanationThe block as identified by name has been deleted fromthe format library by symbolic name (ddname) of theDD statement by Phase 2 of the MFS Language utility.

Note: name is an interpreted description of the blockbeing deleted. An interpreted description of the namecontains:

• FMT/MSG label.• Block type: DOF, DIF or MSG.• If FMT: device type, device model if 3270 or 3270P,

device features in hexadecimal; device featuresinterpreted in EBCDIC; device screen size if 3270-An; version ID if DPM-An or DPM-Bn.

System action• For severity 4, processing continues normally.• For severity 20, phase 2 of the MFS Language utility

terminates.

Programmer responseIf severity 20, then $$IMSDIR has been deleted. Usethe MFS Service utility index function to rebuild $$IMSDIR.

ModuleDFSUTL40, DFSUTLN0

Severity• 4—"name" has been deleted.• 20—The special index directory, $$IMSDIR, has

been deleted as a result of an I/O error or anunexpected EOF while reading the directory.

DFS1011I name {ADDED | HAS BEEN ADDED- ddname}

ExplanationThe block as identified by name has been added tothe format library by Phase 2 of the MFS Languageutility. The ddname will be shown when the addedblock is the $$IMSDIR index and indicates the data setupdated.

Note: name is an interpreted description of the blockbeing added. An interpreted description of the namecontains:

• FMT/MSG label.• Block type: DOF, DIF or MSG.• Size of the block in hexadecimal.• When FMT: device type, device model if 3270

or 3270P, device features in hexadecimal; devicefeatures interpreted in EBCDIC; device screen sizeif 3270-An; version ID if DPM-An or DPM-Bn.

• Date and time the indicated block was created.



Severity0

DFS1012I name STOW ERROR OCCURREDFOR BLOCK - ddname

ExplanationA STOW operation for the block as identified by (name)resulted in an error. The STOW error occurred on thedata set identified by the symbolic name (ddname)of the DD statement of Phase 2 of the MFS languageutility. If ddname does not appear in the message,the error occurred on the data set identified by thesymbolic name "FORMAT"

Note: name is an interpreted description of theblock for which the error occurred. An interpreteddescription of the name contains:


• FMT/MSG label.• Block type: DOF, DIF or MSG.• If FMT: device type, device model if 3270 or 3270P,

device features in hexadecimal; device featuresinterpreted in EBCDIC.

System actionPhase 2 of the MFS Language utility abnormallyterminates with an IMS abend code of 3007.


ModuleDFSUTLN0, DFSUTL40

Severity20


DFS1013I EXECUTION TERMINATED BEFORECOMPLETION - ddname

ExplanationThis message is issued by the MFS Language utilityPhase 2 processor following an I/O error on theformat library. The I/O error occurred on the data setidentified by the symbolic name (ddname) on the DDstatement. If ddname does not appear in the message,the error occurred on the data set identified by thesymbolic name "FORMAT".

System actionPhase 2 of the MFS Language utility terminates withthe highest return code of 20 passed to z/OS.

Programmer responseCorrect the I/O error problem and rerun the job. If theSEQBLKS data set was allocated to a tape drive andthe tape saved, only Phase 2 need be rerun with thetape as input if, and only if, no other MFS Languageutility run has been run between the two runs. If theSEQBLKS data set was created using only a batchutility execution, the MFSBTCH2 routine should bererun.



Severity20


DFS1014I INDEX MAINTENANCE BYPASSED- ddname

ExplanationThe resident directory ($$IMSDIR) does not exist inthe data set associated with the identified ddname,or you have requested that $$IMSDIR not be updatedby using the NOUPDATE option. If ddname does notappear in the message, the directory was not foundor was not updated in the data set identified by theddname FORMAT.



Severity4

DFS1015I INDEX MAINTENANCE COMPLETE- ddname

ExplanationDuring Phase 2 of the MFS Language utility, memberswere deleted from the data set identified by thesymbolic name ("ddname") on the DD statement andfor which there were index entries in the residentdirectory ($$IMSDIR). The entries in $$IMSDIR weredeleted and $$IMSDIR was updated. No entries wereadded to the $$IMSDIR directory for members thatwere added to the format data set. If ddname doesnot appear in the message, the error directory updateoccurred on the data set identified by the symbolicname "FORMAT".



Programmer responseUse the MFS Service utility INDEX function to addentries to $$IMSDIR directory for members added tothe active format library.


Severity0

DFS1016I label FMT

ExplanationThis message is used to reflect the position of an FMTstatement as externally submitted to the format utilityprogram. label is an externally defined name on thestatement. If label is omitted, it is an internal namegenerated by the preprocessor. It is used to uniquelydefine the statement for possible error messagereference.

ModuleDFSUTLW0

Severity0

DFS1017I label DEV (PDB=pdbname)

ExplanationThis message is used to show the position of a DEVstatement as externally submitted to the format utilityprogram. label is an externally defined name on thestatement. If the label is omitted, the preprocessorgenerates a label. This generated label is used touniquely define the statement for possible errormessage reference. If the PDB keyword has beenspecified on the DEV statement, pdbname is theexternally defined name of the Partition DescriptorBlock (PDB).

ModuleDFSUTLW0

Severity0

DFS1018I label DIV

ExplanationThis message is used to reflect the position of a DIVstatement as externally submitted to the format utilityprogram. label is an externally defined name on thestatement. If label is omitted, it is an internal namegenerated by the preprocessor. It is used to uniquelydefine the statement for possible error messagereference.

ModuleDFSUTLW0

Severity0

DFS1019I label DPAGE (PD=pd)

ExplanationThis message is used to show the position of a DPAGEstatement as externally submitted to the format utilityprogram. label is an externally defined name on thestatement. If label is omitted, it is an internal namegenerated by the preprocessor. It is used to uniquelydefine the statement for possible error messagereference. If the PD keyword has been specified on theDPAGE statement, pd is the externally defined name ofthe Partition Descriptor (PD).

ModuleDFSUTLW0

Severity0

DFS1020I label PPAGE

or

label DFLD

Explanationlabel is used to reflect the position of a DFLD orPPAGE statement as externally submitted to the MFSLanguage utility or internally generated by the MFS


Language utility. label is an externally defined name onthe statement. If label is omitted, it is an internal namegenerated by the preprocessor. It is used to uniquelydefine the statement for possible error messagereference.

Module:DFSUTLW0

Severity:0

DFS1021I label MSG

ExplanationThis message is used to reflect the position of an MSGstatement as externally submitted to the format utilityprogram. label is an externally defined name on thestatement. If label is omitted, it is an internal namegenerated by the preprocessor. It is used to uniquelydefine the statement for possible error messagereference.

Module:DFSUTLW0

Severity:0

DFS1022I label LPAGE

ExplanationThis message is used to reflect the position of anLPAGE statement as externally submitted to theformat utility program. label is an externally definedname on the statement. If label is omitted, it is aninternal name generated by the preprocessor. It isused to uniquely define the statement for possibleerror message reference.

Module:DFSUTLW0

Severity:0

DFS1023I label PASSWORD

or

label SEG

ExplanationThe field label is used to reflect the position of aSEG or PASSWORD statement, as externally submittedto the MFS Language utility, or internally generatedby the MFS Language utility (SEG statement). label

is an externally defined name on the statement. Iflabel is omitted, it is an internal name generated bythe preprocessor. It is used to uniquely define thestatement for possible error message reference.

Module:DFSUTLW0

Severity:0

DFS1024I label MFLD

ExplanationThis message is used to reflect the position of an MFLDstatement as externally submitted to the format utilityprogram. label is an externally defined name on thestatement. If label is omitted, it is an internal namegenerated by the preprocessor. It is used to uniquelydefine the statement for possible error messagereference.

Module:DFSUTLW0

Severity:0

DFS1025I label ** UNKNOWN STATEMENTTYPE **

ExplanationUsed to reflect the position of an unknown statementtype which was found by the format language utilityprogram. label is a 6-digit hexadecimal number usedto uniquely define the statement internally for possibleerror message reference. This problem is a probableinternal logic error.

System actionProcessing continues with the next FMT or MSGdefinition.


Module:DFSUTLW0

Severity:16


DFS1026I name MESSAGE DESCRIPTORSTRUCTURE:


ExplanationThis message is used to define the beginning of alist of externally submitted statements that define aninput or output message descriptor. name is the 1- to8-character alphanumeric name provided by the MSGstatement.

Severity:0

DFS1027I name FORMAT DESCRIPTORSTRUCTURE:

ExplanationThis message is used to define the beginning of alist of externally submitted statements that define adevice format descriptor. name is the 1- to 6-characteralphanumeric name provided by the FMT statement.

Severity:0

DFS1028I END OF DESCRIPTOR STRUCTURE

ExplanationThis message is used to delimit a list of externallysubmitted statements that define a message, format,or Partition Descriptor Block (PDB) descriptor.

Severity:0

DFS1029I PARTITION DESCRIPTOR BLOCKSTRUCTURE:

ExplanationThis message identifies the beginning of a list ofPartition Descriptor Blocks (PDBs) and their associatedPartition Descriptors (PD) that are used within theformat set.

Severity:0

DFS1030I name REPLACES A DUPLICATELYNAMED BLOCK.

ExplanationAn interpreted description of the "name" contains:

• FMT/MSG label.• Block Type: DOF, DIF or MSG.• If FMT: device type; device model if 3270 or 3270P;

device features in hexadecimal, device featuresinterpreted in EBCDIC.

The block identified by name was replaced in theformat library by a block with the same name if MOD/MID, or with the same name, device type, and featuresif DOF/DIF in the processing of phase 2.


Severity4

DFS1031I name UNABLE TO STOW,DIRECTORY BLOCK IS FULL.

ExplanationThe partitioned data set directory entries are full forthe format library. The condition was detected whenattempting to STOW for the block identified by name.

Note: name is an interpreted description of the blockname.

An interpreted description of the "name" contains:

• FMT/MSG label.• Block Type: DOF, DIF or MSG.• If FMT: device type; device model if 3270 or 3270P;

device features in hexadecimal; device featuresinterpreted in EBCDIC.


Programmer responseThe format library must be saved (IEHMOVE/IEBCOPY), scratched, reallocated with more directoryspace, and stored. After this has been accomplished,rerun the job.

Severity20

DFS1032I name PERMANENT I/O ERROROCCURRED ON STOW - ddname

ExplanationA permanent I/O error occurred in the PDS directoryfor the data set identified by the symbolic name(ddname) on the DD statement while attempting toupdate the directory through a STOW operation for theblock identified by name. If ddname does not appear


in the message, the error occurred on the data setidentified by the symbolic name "FORMAT".


Programmer responseNotify your IMS system programmer.

Severity20

DFS1033I INVALID DIRECTORY BLOCKREAD, EXECUTION TERMINATE-ddname

ExplanationA directory block for the data set identified by thesymbolic name (ddname) on the DD statement isgreater than 256 bytes in length. If "ddname" does notappear in the message, the error occurred on the dataset identified by the symbolic name "FORMAT".

System actionPhase 2 of the MFS Language Utility abnormallyterminates with an IMS abend code of 3006.

Programmer responseNotify your IMS system programmer.

Severity20

DFS1034I label PDB (SYSMSG=pd)

ExplanationThis message identifies the beginning of a PartitionDescriptor Block (PDB). The label is the externallydefined name of the PDB. If the SYSMSG keywordis present, pd is the externally defined name of thePartition Descriptor (PD) that was defined to receivesystem messages.

Severity0

DFS1035I UTILITY TERMINATED FORREFERAL LIBRARY ERROR.RETURN CODE=return-code.

ExplanationThe MFS phase 1 processor has detected a permanentI/O error in the IMS REFERAL library. The return-codereturn-code in the message indicates the type offailure that occurred:Code

Meaning1

OPEN unsuccessful2

Permanent I/O error on directory search3

Unrecoverable I/O error, SYNAD exit taken4

Unexpected end of input reached, EODAD exittaken

System actionPhase 1 of the MFS Language utility terminates withthe highest return code of 20 passed to z/OS.

Programmer responseCorrect the error detected by the Step 1 preprocessor,and resubmit the job.

Severity:20

DFS1036I label PD PID=nn

ExplanationThis message identifies a Partition Descriptor (PD)defined within a Partition Descriptor Block (PDB). Thelabel is the externally defined name of the PD. The nnis the identifier (ID) of the partition used by this PD.

Severity0

DFS1037I LPAGE/DPAGE SYMBOL TABLELIST FOR name SET.

ExplanationThis is an informational header line generated toidentify subsequent output as the LPAGE/DPAGEsymbol table listing for the FMT description with label'name'. See also message DFS1039I.

Severity0


Related informationDFS1039Ifieldname use assign [ATTR] [PASSWORD][CURSOR] [EXTEND] [DPN] [RDPN] [PRN][RPRN] [FMT] [MSG] [****]

DFS1038I FIELD NAME SYMBOL TABLE LISTFOR name FMT SET.

ExplanationThis is an informational header line generated toidentify subsequent output as the symbol table listingfor all field names defined in the FMT set with the labelname. See also message DFS1039I.

Severity0

Related informationDFS1039Ifieldname use assign [ATTR] [PASSWORD][CURSOR] [EXTEND] [DPN] [RDPN] [PRN][RPRN] [FMT] [MSG] [****]

DFS1039I fieldname use assign [ATTR][PASSWORD] [CURSOR] [EXTEND][DPN] [RDPN] [PRN] [RPRN] [FMT][MSG] [****]

ExplanationThis message is used to display the attributesassociated with a symbol table entry. A symboltable entry can be for a named DPAGE or LPAGESOR=name. The entry can also be for a named DFLDor MFLD dfldname. The particular symbol table beingprocessed is identified by a previous message in theoutput. The following list shows the definitions for themessage:Name

Meaningfieldname

Symbolic name as defined by useruse

Number of occurrences of the specific name(decimal)

assignDecimal value assigned to the symbol forinterblock identification

[ATTR]Field has dynamic attribute information suppliedby at least one output message in the format set.

[PASSWORD]Internal entry for PASSWORD definition for theFMT

[CURSOR]This field is used to set dynamic cursor position orto receive cursor position information on input.

[EXTEND]Field has dynamic extended attribute informationsupplied by at least one output message in theformat set.

[DPN]*This field name has been referenced by adestination process name parameter on the DIVstatement.

[RDPN]*This field name has been referenced by a returndestination process name parameter on the DIVstatement.

[PRN]*This field name has been referenced by a primaryresource name parameter on the DIV statement.

[RPRN]*This field name has been referenced by a returnprimary resource name parameter on the DIVstatement.

*Note: The same field name can be referenced bymore than one of the last four parameters above,but those parameters must appear in different DIVsections of the FORMAT definition, or error messageDFS1160I will be issued.[FMT]

This field has been defined within a FMTdescriptor.

[MSG]This field has been referenced within a MSGdescriptor.

[****]Indicates a potential error. Either the field hasnot been defined within an FMT description andreferenced within an MSG descriptor, or the fieldwas defined within the FMT description and wasnot referenced within an MSG description.

Programmer responseIf the field is found to be in error, as indicated by [****],correct the definition and rerun the job.

Severity0, if no asterisks are in the message; 4, if four asterisks(****) are in the message.


DFS1040I DEVICE MAPPING FORFMT=name DEVICE=identificationDPAGE=dp PHYSICAL PAGE=ppPDB=pdbname PD= pdnamePID=nn

ExplanationThis header identifies a device image map as definedby the user for the format, device, device page, andphysical page. The image that follows this messageconforms to the following rules:

• Unprotected named fields have their location in theimage marked with underscore characters.

• Protected named fields have their location in theimage marked with colon characters.

• Literals in the image are moved and displayed attheir defined location.


The label on the FMT statement.identification

Consists of DEVICE=type (in which type is theparameter coded in the DEV TYPE= operand) andTYPE=name (in which name is either OUTPUT,INPUT, or INOUT coded in the DIV TYPE=operand).

dpThe DPAGE number within DIV.

ppThe physical page number within DPAGE.

pdbnameThe name of the Partition Descriptor Block (PDB)used by this device or the name of the PartitionDescriptor (PD) used by this DPAGE.

nnThe ID of the partition used by this DPAGE.


Severity:0

DFS1041 ABNORMAL TERMINATION -STATUS CODE DHxx

ExplanationThe command-level interface found a conditioncaused by a programming error, or DL/I returned astatus code to a command-level interface indicating anerror other than a programming error. The DH indicates

use of HLPI in DL/I batch. The xx value is the DL/I orcommand-level interface status code.


Programmer responseFor an explanation of the status codes, see IMSVersion 15 Application Programming and the DL/Istatus code information.

Problem determination:4, 11, 19, and obtain a listing of macro DFSHLPDS

Related referenceDL/I status codes (Messages and Codes)Related information1041 (Messages and Codes)“IMS problem determination” on page 11IMS messages and codes problemdetermination is accomplished by usingprocedures established by IBM.

DFS1042I label DPAGE PD NAME CANNOT BEFOUND

ExplanationThe Partition Descriptor (PD) specified in the PDkeyword on the DPAGE statement was not found in theREFERAL library. The label is the name of the DPAGEstatement referencing the PD statement.

System actionA return code of 12 is set, and processing continueswith the next DEV, MSG, or FMT definition.

Programmer responseMake sure the PD named in the PD keyword on theDPAGE statement has been defined in the REFERALlibrary.


Severity:12


DFS1043I THE DEV STATEMENT SPECIFIESPDB= , BUT THIS DPAGESTATEMENT DOES NOT SPECIFY




PD=. THIS COMBINATION ISINCOMPATIBLE.

ExplanationA PDB keyword was present on a DEV statement,but a PD keyword was not found on this DPAGEstatement. Whenever a DEV statement specifies aPDB keyword, partitioning and scrolling have beenselected. Each DPAGE statement must then see oneof the Partition Descriptor (PD) statements within thePartition Descriptor Block (PDB) definition referred toby the DEV statement.

System actionA return code of 12 is set, and processing of theDPAGE statement continues.

Programmer responseCode a PD keyword on each DPAGE statement, orremove the PDB keyword on the DEV statement.

Severity:12

DFS1044I label DEV PDB NAME CANNOT BEFOUND

ExplanationThe Partition Descriptor Block (PDB) specified in thePDB keyword on the DEV statement was not found inthe REFERAL library. The label is the name of the DEVstatement referencing the PDB.

System actionA return code of 12 is set, and processing continueswith the next MSG or FMT definition.

Programmer responseMake sure the PDB named in the PDB parameter onthe DEV statement has been defined in the REFERALlibrary.


Severity:12


DFS1045W label BACKOUT NOT PERFORMEDFOR NON-RECOVERABLE DBD=

ExplanationA non-recoverable database has been encounteredduring backout processing.



DFS1046E I/O BUFFER GETMAIN FAILED

Explanation:A call to GETMAIN to request a 32 K I/O buffer to readthe BSAM block failed.

System action:The utility terminates with a return code RC=36.

User response:Make sure that there is sufficient storage in SPOOL 0and that other jobs are not allocating too much of thestorage.

Module:DFSURDD0

DFS1047I label SYSMSG=DFLD LABEL NOTDEFINED IN EVERY PHYSICALPAGE [name IN DPAGE].

ExplanationThe DFLD label for SYSMSG (system message) must bedefined for every physical page. The name IN DPAGEpart of the message is printed if DPAGE is defined. Thelabel is an externally defined name on the statement.If the label is omitted, an internal name is generatedby the preprocessor.




Severity:12




DFS1048I name DATE=mm|dd|yyTIME=hh.mm.ss CREATED.

ExplanationThe name contains: FMT or MSG label; type of block—DOF, DIF, or MSG; size of block and features inhexadecimal, device type, model (if 3270 or 3270P),and interpreted features in EBCDIC. This messageidentifies the block and informs the user when theblock was created on the SEQBLKS data set. The DATEcontains: month (mm), day (dd), and year (yy). TheTIME contains: hour (hh), minute (mm), and second(ss).


Severity:0

DFS1049I name DATE=mm|dd|yyTIME=hh.mm.ss NOT CREATED.

ExplanationThe "name" contains: FMT or MSG label, type ofdescription: FMT or MSG. The named block was notcreated for online processing because of one or moreerrors encountered during build time indicated by oneor more preceding messages. DATE and TIME indicatewhen the block was being processed. The DATEcontains: month (mm), day (dd) and year (yy). TheTIME contains: hour (hh), minute (mm) and second(ss).

System actionProcessing continues with the next DEV,FMT set orwith the MSG definition.

Programmer responseCorrect the FMT or MSG in error, and rerun the job.


Severity:12


DFS1050I name DATE=mm|dd|yyTIME=hh.mm.ss NOT ADDED.

ExplanationThe name contains: FMT or MSG label; type of block—DOF, DIF, or MSG; size of block and features inhexadecimal; device type; model (if 3270 or 3270P),and interpreted features in EBCDIC. This messageis written when the blocks were created by a batchutility execution and a duplicate block was foundon SEQBLKS data set. It informs the user that theduplicate block created earlier is not added to theonline library. The DATE contains: month (mm), day(dd), and year (yy). The TIME contains: hour (hh),minute (mm), and second (ss).


Severity:4




DFS1051I name DATE=mm|dd|yyTIME=hh.mm.ss IGNORED.

ExplanationThe name contains: FMT or MSG label, type of block:FMT or MSG. The named block had build-time errorsduring MFSBTCH1 batch utility execution, and was notcreated for online processing. This message indicatesthat the block is not be added to the online library,and, if a duplicate block existed in the online library,it will be deleted. The DATE contains: month (mm),day (dd) and year (yy). The TIME contains: hour (hh),minute (mm) and second (ss).


Programmer responseCorrect the MSG or FMT definition if not correctedthrough a later MFSBTCH1 utility run, and resubmit thejob.

Severity:8

DFS1052I label TABLE NOT FOUND.

ExplanationThe operator control table name referenced in theDFLD OPCTL= operand was not found in the REFERALlibrary. label is an externally defined label on theTABLE macro.

System actionProcessing continues normally with the next DEV, FMT,or MSG definition.

Programmer responseDefine the TABLE in error, and resubmit the job.


Severity:12



DFS1053I label TABLE HAS NO ENTRIES.

ExplanationThe operator control table name referenced by theDFLD macro has no IF entries. label is an externallydefined name on the TABLE statement.

System actionProcessing continues with the next DEV, FMT, or MSGdefinition.

Programmer responseRedefine the TABLE in error, and resubmit the job.


Severity:12


DFS1054I label DEVICE LINES TOO SMALLFOR PDB REQUIREMENTS

ExplanationThe number of vertical lines (rows) defined forthe device is insufficient for the screen depthrequirements of the Partition Descriptor Block (PDB).The label is the name of the DEV statement requiringthe PDB.


Programmer responseThe 3270 symbolic name (3270-An) used in theTYPE keyword on the DEV statement might specify an


incorrect screen size. Alternately, the PDB used in thePDB keyword on the DEV statement might be in error.Correct the error, and rerun the job.


Severity:12


DFS1055I label DEVICE COLUMNS TOOSMALL FOR PDB REQUIREMENTS

ExplanationThe number of horizontal lines (columns) for thedevice is insufficient for the screen width requirementsof the Partition Descriptor Block (PDB). The label is thename of the DEV statement requiring the PDB.


Programmer responseThe 3270 symbolic name (3270-An) used in theTYPE keyword of the DEV statement might specify anincorrect screen size. Alternatively, the PDB used inthe PDB keyword of the DEV statement might be inerror. Correct the error, and rerun the job.


Severity:12


DFS1056I labell ** WARNING ** DEVICESCREEN SIZE AND PDB SCREENREQUIREMENTS CANNOT BEVERIFIED.

ExplanationThe label is the name of a DEV statement thatspecifies a Partition Descriptor Block (PDB). A partitionused by the PDB has a CELLSIZE specification of 00x 00. The Language utility cannot verify that the PDB

specifications fits on the screen size defined by the3270 symbolic name (3270-An).

System actionA return code of 4 is set, and processing continuesnormally.

Programmer responseVerify that the 3270 symbolic name (3270-An)specifies a screen size large enough for the specifiedPDB.

Severity:4

DFS1058E REASON = xxx - reason_text

ExplanationAn unexpected condition was encountered in moduleDFSTOCL0, DFSDVBH0, DFSNOTB0, DFSDVSM0, orDFSFXC50. This problem is an IMS system error.

The following table shows the reason code xxx in themessage and the reason text reason_text.

Table 9. Reason codes for DFS1058E

Reasoncode Reason text

010 NON-VSAM BQEL - BUFFER NOT WRITTEN, CANNOTFREE BQEL

015 WRITE ERROR - BUFFER NOT WRITTEN, CANNOTFREE BQEL



030 RPLI ACTIVE ON ENTRY TO DFSDVSM0

031 VSI UPDATE FAILED

032 BAD RETURN CODE ON SVC 109

033 NOT AN IMS RPLI

034 WRITE ERRORS ON EVERY BUFFER IN THE SUBPOOL

035 CI RDF/CIDF ARE BAD

036 CI CONTROL INFORMATION IS BAD

037 RPL NOT AN IMS RPL




System actionAfter the message is issued, IMS terminatesabnormally with an IMS abend 0845 and a memorydump is taken.

System programmer responseUse the reason code and text to determine the sourceof the problem.

You can also check the value in register 1 and refer tothe analysis information for IMS abend 0845.

Module:DFSDVSM0, DFSDVBH0, DFSTOCL0, DFSFXC50


DFS1060I name BUFFER SIZE=size

ExplanationThis message informs the user of the largest bufferspace requirements for this output or input message.As an output message, the name contains the FMTlabel, and the size contains the line buffer size (indecimal) for a 3270 display, or the work buffer size(in decimal) for all other device types. As an inputmessage, the "name" contains the MSG label, and thesize contains the work buffer size (in decimal).


System programmer responseUse this value for calculation of the I/O pool sizerequirements for MFS formatted messages.

DFS1061I NO STORAGE AVAILABLE FORCDE=xxxxxxxx PGM=yyyyyyyyJOB=zzzzzzzz

ExplanationSequential Buffering (SB) was unable to acquirevirtual storage for the control block whose CDE ID isxxxxxxxx.

System actionUse of SB is limited or impossible.

User responseFor IMS DB/DC with LSO=N, allocate more CSAstorage; for IMS DB/DC with LSO not equal to N, or IMS

batch, allocate more private storage. For DFSSBSCD,DFSSBPSS, and DFSBSCAR, allocate more privatestorage.

DFS1062I - CODE=x, NOT SUFFICIENTSBH BUFFER STORAGE FORPSB=aaaaaaaa; PCB=bbbbbbbb;DDN=ccccccccc

ExplanationIMS was unable to allocate virtual storage for the SBbuffers for the PCB/data set pair bbbbbbbb/ccccccccof PSB aaaaaaaa.

• If CODE=1, the failure occurred because IMSexceeded the MAXSB storage limit specified inmember DFSVSMxx of IMS.PROCLIB (for IMSonline). For the amount of storage IMS was tryingto allocate, see message DFS1063I.

• If CODE=2, the failure occurred because IMS wasunable to acquire the storage it requested from z/OS.

System actionThe system actions depends on the value of CODE:

• If CODE=1, IMS waits until another onlineapplication releases SB Handler buffer storagebefore activating Sequential Buffering (SB) for thelisted PCB/data set pair.

• If CODE=2, IMS does not activate SequentialBuffering for the listed PCB/data set pair.

User responseThe response depends on the value of CODE:

• If CODE=1, increase the MAXSB storage limit, ifappropriate.

• If CODE=2, allocate more CSA storage (for IMSDB/DC with LSO=N) or private storage (IMS DB/DCwith LSO≠N, IMS batch, and DBCTL).

DFS1063I - REQUESTED STORAGE=xx,xxx,xxx; AVAILABLE STORAGE=xx,xxx,xxx

ExplanationThis message specifies the amount of storage IMSwas trying to allocate and accompanies messageDFS1062I. See that message for an explanation of theallocation failure.




- CODE=x, NOT SUFFICIENT SBHBUFFER STORAGE FOR PSB=aaaaaaaa;PCB=bbbbbbbb; DDN=ccccccccc

DFS1064I - GETIOSB NOT SUCCESSFUL FORPSB=xxxxxxxx

ExplanationIMS was unable to allocate an IOSB control block forPSB xxxxxxxx.

System actionSequential Buffering (SB) does not use overlappedsequential read for some PCBs or some database datasets, or both.

User responseFor IMS DB/DC with LSO=N, allocate more CSAstorage; for IMS DB/DC with LSO≠N, IMS batch, orDBCTL, allocate more private storage.

DFS1065A - UNABLE TO WRITE SBH IMAGE-CAPTURE TO IMS LOG

ExplanationIMS was unable to write the requested SB Handlerimage capture records to the IMS log data set becausethe data set was not open.

System actionIMS does not write the Sequential Buffering (SB)image capture records to the IMS log data set.

User responseMake sure that the DD statement defining the IMS logdata set is present and correct.

DFS1066I -xx //DFSCTL CONTROL-STATEMENT ERROR: aaaaaaa

ExplanationA Sequential Buffering (SB) control statement containserrors. Subcode xx is unique for each type of error;aaaaaaa is a description for each subcode.

The list of subcodes and descriptions follows:Code (xx)

Description (aaaaaaa)01

PARAMETER VALUE IS NOT NUMERIC

02"=" IS MISSING IN KEYWORD PARAMETER

03INVALID STATEMENT-TYPE IN //DFSCTL

04INVALID PARAMETER VALUE

05PARAMETER VALUE IS TOO LONG

06INVALID KEYWORD

07STOP= KEYWORD NOT HIGHER THAN START=

08SBPARM STATEMENT HAS NO KEYWORDPARAMETERS

10EXTRANEOUS COMMA (,)

System actionIMS discards the SB control statement containing theerror. For more information about the error, see theaccompanying error messages that might be issued(DFS1067I, DFS1068I, DFS1069I).

User responseCorrect the error on the SB control statement based onthe error messages issued.

DFS1067I ERROR IS IN THIS KEYWORDPARAMETER: parameter

ExplanationA Sequential Buffering (SB) control statement containserrors. IMS has previously issued message DFS1066Idescribing the error.

System actionIMS discards the SB control statement containing theerror.

User responseCorrect the error based on information in messageDFS1066I.

Related information“DFS1066I” on page 378-xx //DFSCTL CONTROL-STATEMENT ERROR:aaaaaaa

DFS1068I ERROR IS IN CARD(S) LISTEDBELOW


ExplanationA Sequential Buffering (SB) control statement containserrors. IMS first issues message DFS1066I describingthe types of errors. It then issues this message, andfinally issues message DFS1069I listing the content ofthe incorrect control statement.

System actionIMS discards the control statement containing theerror.


Related information“DFS1066I” on page 378-xx //DFSCTL CONTROL-STATEMENT ERROR:aaaaaaa

DFS1069I records/lines in error

ExplanationThis message lists the records or lines of a SequentialBuffering (SB) control statement that contains errors.IMS has previously issued message DFS1066Idescribing the error.

System actionIMS discards the SB control statement containing theerror.


Related informationDFS1066I-xx //DFSCTL CONTROL-STATEMENT ERROR:aaaaaaa

DFS1070I SB-COMPARE-OPTION DETECTEDA MISMATCH FOR PSB=xxxxxxxx

ExplanationSee message DFS1070W for an explanation andactions.

Related informationDFS1070WSB-COMPARE-OPTION DETECTED A MISMATCHFOR PSB=xxxxxxxx

DFS1070W SB-COMPARE-OPTION DETECTEDA MISMATCH FOR PSB=xxxxxxxx

ExplanationThe Sequential Buffering (SB) COMPARE optiondetected that the buffer content that the SB bufferhandler wanted to return to the OSAM buffer handlerdid not match the contents of the block as it is storedon DASD.

Message DFS1070I is issued in a non-data-sharingenvironment indicating that the mismatch is an IMSerror.

Message DFS1070W is issued in a data-sharingenvironment, indicating that the mismatch might belegitimate.

System actionIMS creates SNAP dumps for problem determination.

In a non-data sharing environment, IMS issuespseudoabend 0152.

User responseSave all SNAP output for problem determination.

DFS1071I INVALID DATA SET ATTRIBUTESFOR //DFSCTL

ExplanationThe //DFSCTL data set has invalid data set attributes.

System actionIMS abnormally terminates the starting batch, oronline dependent region.

User responseCorrect the error by making sure that

• The data set is either a sequential file or an existingmember of a partitioned data set (PDS).

• The record format is F, FB, or FBS.• The record size is 80.

DFS1072I PAGE-FIXING FAILED FORPSB=aaaaaaaa; PCB=bbbbbbbb;DDN=cccccccc

ExplanationIMS was unable to page fix the storage for theSequential Buffering (SB) buffers or the control


blocks. The cause is probably that real storage wasunavailable.

IMS attempted this page fixing while trying toinitiate sequential buffering for the PCB/data set pairbbbbbbbb/cccccccc of PSB aaaaaaaaa.

System actionIMS does not use SB for the PCB/data set pairbbbbbbbb/cccccccc of PSB aaaaaaaa.

User responseDetermine if too much buffer space is allocated toSequential Buffering.

DFS1073I LCE ALLOCATION FAILED FORPSB=aaaaaaaa; PCB=bbbbbbbb;DDN=cccccccc

ExplanationIMS was unable to allocate any additional local cacheentries (LCEs) to this subsystem. The limit of 1200sequential buffering buffer sets (12000 buffers) wasexceeded. IMS attempted to allocate the LCEs whiletrying to initiate sequential buffering for the PCB/dataset pair bbbbbbbb/ cccccccc of PSB aaaaaaaa.

System actionIMS does not use sequential buffering for the PCB/data set pair bbbbbbbb/cccccccc of PSB aaaaaaaa

User responseDetermine if too many buffers are allocated tosequential buffering.

Module:DFSSBEV0

DFS1075A NO STORAGE AVAILABLE FORDFSSBSCD

ExplanationIMS was unable to acquire virtual storage for theSequential Buffering (SB) extension to the SystemContents Directory (SCD).


User responseFor IMS batch allocate more private storage; for IMSDB/DC or DBCTL, allocate more CSA storage.

DFS1076A xxxxxxxx CAN NOT BE LOADED,RC=nn

ExplanationThe IMODULE macro was unable to load modulexxxxxxxx. For an explanation of IMODULE return codenn, see the IMODULE return codes information.

System actionIMS issues abend 0153.

User responseCorrect the error based on the code returned from theIMODULE macro.

Related referenceIMODULE return codes (Messages and Codes)Related informationIMS abend 0153

DFS1077A ERROR ON SBONLINE CONTROLCARD: bbbbbbbbbbbbb

ExplanationThere is an error in a SBONLINE control statement inmember DFSVSMxx of IMS.PROCLIB (for IMS online).The variable bbbbbbbbbbbbb describes the type oferror. The error can be one of the following:

• SBONLINE is not followed by a blank or a comma.• A parameter other than MAXSB is specified.• The MAXSB parameter value is not numeric or is not

followed by at least one blank.

System actionIMS uses Sequential Buffering (SB), but it ignores anyparameter value specified on the incorrect SBONLINEcontrol statement.

User responseCorrect the error in the SBONLINE control statement.

DFS1078I (text of I/O error message)

ExplanationIMS detected an I/O error while processing the //DFSSTAT DD statement. This message contains thetext of the standard I/O error message provided by thez/OS SYNADAF macro.




System actionIMS stops writing information to the //DFSSTAT dataset.

User responseCorrect the error based on the content of thismessage.

Related referencez/OS: SYNADAF error descriptions

DFS1079A INSUFFICIENT STORAGE TOPROCESS //DFSCTL CONTROLSTATEMENTS

ExplanationIMS was unable to acquire enough virtual storage toprocess the control statements stored in the data setdefined by the //DFSCTL DD statement.

System actionIMS ignores some or all of the control statements.

User responseFor IMS batch or DBCTL, allocate more private storage;for IMS DB/DC, allocate more CSA storage.

DFS1080A INVALID region type

ExplanationThe Sequential Buffering (SB) test program(DFSSBHD0) was executed in an invalid regiontype. The batch region type specified in the firstsubparameter of the //EXEC PARM field must be DLI,DBB, or ULU.

System actionIMS abnormally terminates the test program.

User responseCorrect the region type.

DFS1081A SB ENVIRONMENT NOT SET-UP:DFSSBHD0 CAN NOT EXECUTE

ExplanationIMS was unable to set up the appropriate environmentfor executing the Sequential Buffering (SB) testprogram (DFSSBHD0). This message follows othermessages describing why the error occurred.

User responseCorrect the error based on the other error messagessent by IMS.

DFS1082A SYSPRINT COULD NOT BE OPENED

ExplanationThe Sequential Buffering (SB) test program(DFSSBHD0) was unable to open the //SYSPRINT dataset. This message follows z/OS messages describingwhy the error occurred.

System actionIMS abnormally terminates the SB test program.

User responseMake sure that the //SYSPRINT DD statement definingthe data set for the test program is present andcorrect. See the messages issued by z/OS as well.

DFS1083A SYSIN COULD NOT BE OPENED

ExplanationThe Sequential Buffering (SB) test program(DFSSBHD0) was unable to open the //SYSIN data set.This message follows z/OS messages describing whythe error occurred.


User responseMake sure that the //SYSIN DD statement defining thedata set for the test program is present and correct.See the messages issued by z/OS as well.

DFS1084A SYSUT1 COULD NOT BE OPENED

ExplanationThe Sequential Buffering (SB) test program(DFSSBHD0) was unable to open the //SYSUT1 dataset containing the SB image capture log records. Thismessage follows z/OS messages describing why theerror occurred.




User responseMake sure that the //SYSUT1 DD statement definingthe data set for the test program is present andcorrect. See the messages issued by z/OS as well.

DFS1085A RECORD FORMAT OF SYSUT1 ISNOT VARIABLE

ExplanationThe record format of the data set containingSequential Buffering (SB) image capture log records isnot variable-length.


User responseChange the record format of the data set to variable-length.

DFS1086A PSB HAS NO DB-PCB: DFSSBHD0CAN NOT EXECUTE

ExplanationThere is no database PCB in the PSB specified onthe JCL for the Sequential Buffering (SB) test program(DFSSBHD0).

The SB test program must be executed with the samePSB and DBDs that were used for the application thatgenerated the SB image capture records.


User responseExecute the SB test program with the same PSB andDBDs used for the application that generated the SBimage capture records.

DFS1087A INVALID PCB-NUMBER IN IMAGECAPTURE RECORD

ExplanationThe relative database PCB number in a SequentialBuffering (SB) image capture log record does notmatch any of the database PCBs of the PSB used toexecute the SB test program (DFSSBHD0).

System actionIMS issues message DFS1096I and abnormallyterminates the SB test program.

User responseMake sure that the PSB used to create the imagecapture records is the same PSB used to execute theSB test program.

Related information“DFS1096I” on page 384IC RECORD FOR: PCB-NBR=nnnn,DBD=aaaaaaaa, DSG-NBR=mmmm,DDN=bbbbbbbb

DFS1088A DBD-NAMES OF PSB AND INIMAGE-CAPTURE RECORDS ARENOT IDENTICAL

ExplanationThe DBD names in the SB image capture log recordsdo not match the DBD names of the database PCBsof the PSB used to execute the SB test program(DFSSBHD0).

System actionIMS issues messages DFS1096I and DFS1097I, andabnormally terminates the SB test program.

User responseMake sure that the PSB used to create the imagecapture records is the same PSB used to execute theSB test program.

Related information“DFS1096I” on page 384IC RECORD FOR: PCB-NBR=nnnn,DBD=aaaaaaaa, DSG-NBR=mmmm,DDN=bbbbbbbb“DFS1097I” on page 384DBD NAME ACCORDING TO PSB: aaaaaaaa

DFS1089A INVALID DSG-NUMBER IN IMAGECAPTURE RECORD

ExplanationThe relative DSG number in a Sequential Buffering(SB) image capture log record does not match any ofthe DSG control blocks used to execute the SB testprogram (DFSSBHD0).


System actionIMS issues message DFS1096I and abnormallyterminates the SB test program.

User responseEnsure that the PSB and DBDs used to create theimage capture records are the same as the ones usedto execute the SB test program.


DFS1090A DATA SET HAS BEEN CONVERTEDTO VSAM.

ExplanationAn OSAM database data set was changed to a VSAMdatabase data set after the Sequential Buffering (SB)image capture. SB does not support VSAM databasedata sets.

System actionIMS issues message DFS1096I, and abnormallyterminates the SB test program.



DFS1091W LOAD-PROCOPT FORDBD=xxxxxxxx, DB DATA SETSCANNOT BE OPENED.

ExplanationA PCB referencing DBD xxxxxxxx has a load processingoption, which the Sequential Buffering (SB) testprogram does not support.

System actionIn most cases, the test program neither opensthe database data sets referenced by the PCB norprocesses the image capture log records for thedatabase data sets referenced by the PCB that has the

load processing option. At program termination time,the test program might issue message DFS2346W.

User responseCheck to see if a DFS2346W message is written onthe //SYSPRINT data set at program termination. If so,be aware that the reprocessing of the image capturelog records by the SB test program will not match theprocessing of the application that generated the imagecapture log records. If message DFS2346W was notissued, ignore this message (DFS1091W).

Related information“DFS2346W” on page 678NBR OF SELECTED RECORDS SKIPPEDBECAUSE DB DATA SETS ARE NOT OPEN:nnnnnnnn

DFS1092A DD-NAMES IN PSB/DBD AND INIMAGE CAPTURE RECORDS ARENOT IDENTICAL

ExplanationThe ddnames in a Sequential Buffering (SB) imagecapture record do not match those in the DBDsreferenced by the PSB used to execute the SB testprogram.

System actionIMS issues messages DFS1096I and DFS1098I, andabnormally terminates the test program.

User responseMake sure that the PSB, DBDs, and DBD ddnamesused for the image capture are the same as the onesused to execute the SB test program.

Related information“DFS1096I” on page 384IC RECORD FOR: PCB-NBR=nnnn,DBD=aaaaaaaa, DSG-NBR=mmmm,DDN=bbbbbbbb“DFS1098I” on page 385DDNAME ACCORDING TO DBD: aaaaaaaa

DFS1093A INVALID SUBRECORD-TYPE INIMAGE CAPTURE RECORD

ExplanationThe Sequential Buffering (SB) image capture logrecords contain an invalid code in the subrecord-typefield.



User responseMake sure that the //SYSUT1 data set for the SB testprogram contains SB image capture log records.

DFS1094W PREMATURE END-OF-FILE ONSYSUT1

ExplanationThe Sequential Buffering (SB) test program(DFSSBHD0) reached the end of the //SYSUT1 data setbefore processing all of the image-capture records ofthe application.

System actionThe SB test program terminates normally at end-of-fileof //SYSUT1.

User responseMake sure that the //SYSUT1 data set contains allneeded image-capture records. If you wanted theSB test program to process only some of the imagecapture records, make sure that the correct ones wereprocessed.

DFS1095A APPLICATION-START RECORDNOT FOUND

ExplanationThe Sequential Buffering (SB) test program(DFSSBHD0) was unable to find the image capturelog record in the //SYSUT1 data set that describes thestart of the application.


User responseMake sure that:

• //SYSUT1 data set contains all required imagecapture records.

• The SB test program is run with the same PSB usedfor the application that created the image capturerecords.

• The image capture option was successfully activatedfor the application that was supposed to create theimage capture records.

• The specifications on the SELECT control statementfor the SB test program are correct (if this statementwas used to select the image capture records of aspecific execution of the application).

DFS1096I IC RECORD FOR: PCB-NBR=nnnn, DBD=aaaaaaaa, DSG-NBR=mmmm, DDN=bbbbbbbb

ExplanationThe Sequential Buffering (SB) test program detectedan error associated with an image capture record.

This message provides the relative PCB number, DBDname (as coded on the PCB macro), DSG number,and ddname for this record. The first database PCBand DSG have a relative number of 1. In some cases,the PCB number, DSG number, and DBD name fieldsare not initialized; for example, when DL/I issues I/Ooperations for internal PCBs that are not defined to theapplication program.


User responseFor information about the type of error the SB testprogram found, see a previously issued IMS messageand correct the error accordingly.

DFS1097I DBD NAME ACCORDING TO PSB:aaaaaaaa

ExplanationThe DBD name stored in the image capture recorddoes not match the one stored in the database PCB.This message provides the DBD name (as codedon the PCB macro), stored in the database PCBused to run the SB test program. IMS previouslyissued messages DFS1088A and DFS1096I to provideadditional information.


User responseCorrect the error based on messages DFS1088A andDFS1096I.



DBD-NAMES OF PSB AND IN IMAGE-CAPTURERECORDS ARE NOT IDENTICAL“DFS1096I” on page 384IC RECORD FOR: PCB-NBR=nnnn,DBD=aaaaaaaa, DSG-NBR=mmmm,DDN=bbbbbbbb

DFS1098I DDNAME ACCORDING TO DBD:aaaaaaaa

ExplanationThe ddname stored in the image capture record doesnot match the one stored in the IMS AMP control blockof the DMB/DBD. This message provides the ddname(as coded on the DATASET macro) stored in the IMSAMP control block of the DBD used to run the SB testprogram.

IMS previously issued messages DFS1092A andDFS1096I to provide additional information.


User responseCorrect the error based on messages DFS1092A andDFS1096I.

Related information“DFS1092A” on page 383DD-NAMES IN PSB/DBD AND IN IMAGECAPTURE RECORDS ARE NOT IDENTICAL“DFS1096I” on page 384IC RECORD FOR: PCB-NBR=nnnn,DBD=aaaaaaaa, DSG-NBR=mmmm,DDN=bbbbbbbb

DFS1099A DDNAME NOT FOUND IN ANY DBD

ExplanationThe Sequential Buffering (SB) test program(DFSSBHD0) was unable to find the ddname stored inan image capture record in any DBD referenced by thePSB.

System actionIMS issues message DFS1096I, and terminates the SBtest program abnormally.

User responseCorrect the error by making sure the PSBs/DBDs usedfor image capture are the same as the ones used torun the SB test program.


DFS1100I nnnnnn IS AN INVALID MESSAGEKEY.

ExplanationAn internal logic error has occurred. The format utilityis attempting to issue a message which does not existin its message table. nnnnnn is the message key of themessage. Probable cause is user modifications.


Programmer responseDetermine if failure occurred for a reason other thanuser modifications to the MFS Language utility.


Severity:4





DFS1101I label FORMAT BLOCK HAS NODEVICES.

ExplanationA format block was defined for which no DEVstatements were defined. label is an externally definedname on the statement. If label is omitted, it is aninternal name generated by the preprocessor for thestatement. See message DFS1027I.


Programmer responseCorrect the format definition, and rerun the MFSLanguage utility.

Severity:12

Related information“DFS1027I” on page 368name FORMAT DESCRIPTOR STRUCTURE:

DFS1102I GENERATION TERMINATED FORFORMAT SET.

ExplanationA user format definition had an error previously statedwith an error message. The format definition andrelated message definitions are deleted from furtherprocessing.

System actionProcessing continues with the next FMT set.

Programmer responseCorrect the format definition, and rerun the MFSLanguage utility.

Severity:12

DFS1103I label OUTPUT MESSAGE HAS NOSEGMENTS.

ExplanationAn output message description was encounteredwhich has no segments defined. label is an externallydefined name on the statement. If label is omitted, itis an internal name generated by the preprocessor forthe statement. See also message DFS1026I.

System actionProcessing continues with the next MSG or FMTdefinition.

Programmer responseCorrect the message description, and rerun the job.

Severity:12

Related information“DFS1026I” on page 367name MESSAGE DESCRIPTOR STRUCTURE:

DFS1104I label INPUT MESSAGE HAS NOSEGMENTS.

ExplanationThe block is deleted because the input message hasno segments. label is an externally defined name onthe statement. If label is omitted, it is an internal namegenerated by the preprocessor for the statement. Seealso message DFS1026I.


Programmer responseCorrect the message definition, and rerun the job.

Severity:12

Related information“DFS1026I” on page 367name MESSAGE DESCRIPTOR STRUCTURE:

DFS1105I label LPAGE HAS NO SEGMENTS.


ExplanationAn output message description defines an LPAGE withno SEG or MFLD statements following it. label is anexternally defined name on the statement. If labelis omitted, it is an internal name generated by thepreprocessor for the statement. See also messageDFS1022I.



Severity:12

Related information“DFS1022I” on page 367label LPAGE

DFS1106I label LPAGE DOES NOT HAVEDPAGE name.

ExplanationThe required SOR= dpagename parameter is missingon the LPAGE statement. label is an externally definedname on the statement. If label is omitted, it is aninternal name generated by the preprocessor for thestatement.



Severity:12


DFS1107I label LPAGE REQUIRED LITERALMISSING IN COND=.

Explanationlabel is an externally defined name on the statement.If label is omitted, it is an internal name generatedby the preprocessor for the statement. This messageis issued if the COND= parameter is not specified or

a literal is missing, or both, when it is required on anLPAGE statement. See also message DFS1022I.



Severity:12


DFS1108I label SEGMENT HAS NO FIELDS.

ExplanationAn input segment has no fields defined for it. labelis an externally defined name on the statement. Iflabel is omitted, it is an internal name generated bythe preprocessor for the statement. See also messageDFS1023I.



Severity:12

Related information“DFS1023I” on page 367label PASSWORD

DFS1109I MESSAGE HAS EXCEEDEDALLOWABLE LENGTH.

ExplanationThe input message has exceeded the maximumallowable length of 32,767 bytes.




Severity:12

DFS1110I label WARNING SEGMENT HASNO FIELDS. SEGMENT WILLBE SKIPPED BY ONLINEPROCESSING.

ExplanationAn output message segment has no fields definedfor it. label is an externally defined name on thestatement. If label is omitted, it is an internal namegenerated by the preprocessor for the statement. Seealso message DFS1023I.



Severity4

DFS1111I label MSG/LPAGE HAS NOSEGMENTS WITH FIELDS.

Explanationlabel is an externally defined name on the statement.If label is omitted, it is an internal name generatedby the preprocessor for the statement. MSG or LPAGEsegments have no fields defined. See also messageDFS1022I.



Severity12

DFS1112I label LPAGE COND= PARAMETERSPECIFIED AN MFLD LABEL THATCANNOT BE FOUND OR MFLDCONTAINS A LITERAL

ExplanationThe MFLD label referenced in CON label field is anexternally defined name on the statement. If labelis omitted, it is an internal name generated by thepreprocessor for the statement. See also messageDFS1022I.



Severity12

Related informationDFS1022Ilabel LPAGE

DFS1113I label DUPLICATE MFLD HAS BEENDELETED.

ExplanationA message field (MFLD) definition has been foundthat uses a definition field name (dfldname) alreadyreferenced in this MSG description. label is anexternally defined name on the statement. If labelis omitted, it is an internal name generated by thepreprocessor for the statement. See also messageDFS1024I.



Severity:12

Related information“DFS1024I” on page 367label MFLD

DFS1114I label DEVICE HAS NO DIVISIONS

ExplanationOne DIV statement must be defined for each DEVstatement. label is an externally defined name on the


statement. If label is omitted, it is an internal namegenerated by the preprocessor for the statement. Seealso message DFS1017I.


Programmer responseCorrect the format definition, and rerun the job.

Severity12

DFS1115I label DIV STATEMENTS AREINVALID.

ExplanationThis message is issued if any of the following occurs:

• DEV TYPE=3270, 3270P, 3600, 36DS, 36FP, 36JP or36PB is specified and more than one DIV statementfollows the above DEV statement.

• DEV TYPE=274X and more than two DIV statementsfollow the above DEV statement.

• DEV TYPE=274X, and either two DIV TYPE=INPUTor two DIV TYPE=OUTPUT follow the above DEVstatement.

label is the identifier of the DEV statement in error. Seealso message DFS1017I.


Severity12

Related information“DFS1017I” on page 366label DEV (PDB=pdbname)

DFS1116I label FORMAT HAD TERMINATINGDEVICE ERROR.

ExplanationThis message is printed when a formatting device erroroccurred and prevented the block from being created.This message will be preceded by one or more errormessages describing the terminating device error.label is an externally defined name on the statement.

If label is omitted, it is an internal name generated bythe preprocessor for the statement. See also messageDFS1016I.



Severity12

Related information“DFS1016I” on page 366label FMT

DFS1117I label DEVICE DOES NOT DEFINEALL DPAGE DESCRIPTIONS.

ExplanationThis message is printed if:

• An LPAGE of a MSG description references a"dpagename" in a SOR= parameter which is notdefined in a related FMT description.

• An FMT description contains several DEV statementsand does not contain identical labels on DPAGEstatements for each DEV statement.

label is an externally defined name on the statement.If label is omitted, it is an internal name generated bythe preprocessor for the statement. See also messageDFS1017I.



Severity12

Related information“DFS1017I” on page 366label DEV (PDB=pdbname)

DFS1118I label DPAGE ALREADY DEFINEDTHIS DEVICE.


ExplanationA duplicate DPAGE label has been found for this DEVstatement. label is an externally defined name on thestatement. If label is omitted, it is an internal namegenerated by the preprocessor for the statement. Seealso message DFS1019I.



Severity12

Related information“DFS1019I” on page 366label DPAGE (PD=pd)

DFS1119I label DUPLICATE FIELD WITHINDEVICE PAGE.

ExplanationA duplicate DFLD label has been found in the samephysical page for the device. label is an externallydefined name on the statement. If label is omitted, itis an internal name generated by the preprocessor forthe statement. See also message DFS1019I.



Severity12

Related information“DFS1019I” on page 366label DPAGE (PD=pd)

DFS1120I label DFLD OVERLAPS WITHFOLLOWING FIELD:

ExplanationThe POS= parameter specified for DFLD overlaps incolumn or line specification, or both, with anotherDFLD. label is an externally defined name on thestatement. If label is omitted, it is an internal namegenerated by the preprocessor for the statement.



Severity:12

Related information“DFS1020I” on page 366label PPAGE

DFS1121I label DFLD OVERLAPS WITHPREVIOUS FIELD.

ExplanationThe POS= parameter specified for DFLD overlaps incolumn or line specification, or both with another field.label is an externally defined name on the statement.If label is omitted, it is an internal name generated bythe preprocessor for the statement. See also messageDFS1020I.

System actionProcessing continues with the next DEV, FMT or MSGdefinition.


Severity12


DFS1122I label DFLD HAS INVALID STARTORIGIN WITHIN PAGE.

ExplanationThe starting position origin is either less than (1,2) for3270, or (1,1) for other devices. For SCS1, the starting


line position might be less than the top margin valuespecified in the VTAB= keyword on the DEV statement.The name of the statement label is an externallydefined name on the statement. If label is omitted, itis an internal name generated by the preprocessor forthe statement.



Severity:12

Related information“DFS1120I” on page 391label DFLD OVERLAPS WITH FOLLOWINGFIELD:

DFS1123I label DFLD EXCEEDSDEVICE BOTTOM MARGIN/PAGECAPABILITIES

ExplanationThe DFLD statement POS= specification will not fitwithin the bottom margin specification on the VTAB=keyword or on a device page (PAGE=). The name of thestatement label is an externally defined name on thestatement. If label is omitted, it is an internal namegenerated by the preprocessor for the statement. Seealso message DFS1020I.

System actionProcessing continues with the next DEV, FMT or MSGdefinition.


Severity12


DFS1124I label DFLD EXCEEDS DEVICE LINESIZE.

ExplanationThe literal defined for the true DFLD exceeds thedevice line size. label is an externally defined name onthe statement. If label is omitted, it is an internal namegenerated by the preprocessor for the statement. Forfurther explanation, see message DFS1020I.



Severity12

Related informationDFS1020Ilabel PPAGE

DFS1125I label *** WARNING *** DFLDWILL CAUSE COPY BUFFER LOCKON REMOTE 3270s.

Explanationlabel is an externally defined name on the statement.If label is omitted, it is an internal name generatedby the preprocessor for the statement. Indicated DFLDstatement will cause the display image to be locked forCOPY on remote 3270; that is, the display cannot becopied.


Programmer responseIf copy lock is not desired, redefine the field definitionso the field does not start in the first position of thebuffer (POS=(1,2)) or does not have the attributes ofALPHA and PROT (protected).

Severity4

DFS1126I label DPAGE HAS NO DFLDSTATEMENTS.


ExplanationThe DPAGE statement represented by the identifier,label, has no DFLD statements defined. At least oneDFLD must be defined for each DPAGE within a FMTdescriptor.


Programmer responseCorrect the definition error, and resubmit the job.

Severity12

DFS1127I label NXT= MESSAGE DOES NOTUSE SAME FORMAT OR IS NOTDEFINED.

Explanationlabel is an externally defined name on the statement.If label is omitted, it is an internal name generatedby the preprocessor for the statement. The specificstatement was previously identified with the samenumber in a DFS1021I or DFS1022I message. TheMSG or LPAGE statement contains a NXT=msgnameparameter. For the 3270, the referenced inputmessage description does not use the same sourceFMT description as the output message beingprocessed; the format name specified in the SOR=parameter is not the same.

The following conditions can cause this message to beproduced:

• The referenced name is not a name of an inputmessage description, but a name of an outputmessage description.

• The input message description does not exist in theIMS.REFERAL library.

• The input message description specifies a differentFMT name than the output message description inthe SOR= operand of the MSG statement.


Programmer responseIf the definition for the referenced input messagedescription is supplied in this run, correct the

definition and rerun the job. If the referenced inputmessage already exists in the IMS.REFERAL library,execute the MFS Service utility program using theRELATE function to determine the status of the inputmessage description in error. Correct the definition forthe referenced input message description, and rerunthe job.

Severity12

DFS1128I label LPAGE PROMPT=DFLDNAMEIS DUPLICATE.

ExplanationThe DFLD label referenced by the LPAGE statementmust be unique within LPAGE. label is an externallydefined name on the LPAGE statement. If the labelis omitted, an internal name is generated by thepreprocessor.


Programmer responseCorrect the source statements for the message inerror, and resubmit the job.


Severity12


DFS1129I label MSG DOES NOT DEFINE ALLDPAGE DESCRIPTIONS.

ExplanationThe INPUT MSG LPAGE statements do not referenceall DPAGE descriptions for the corresponding FMT.label is an externally defined name on the statement.





Severity12


DFS1130I label LPAGE ALREADY DEFINEDDPAGE.

ExplanationThe input message LPAGE statement references thesame DPAGE more than once.


Programmer responseCorrect the duplicate reference, and resubmit the job.


Severity12


DFS1131I label PASSWORD HAS NO FIELDS.

ExplanationThe input message PASSWORD segment has no fieldsdefined for it. label is an internally generated name forthe statement.


Programmer responseCorrect the PASSWORD segment, and resubmit thejob.


Severity12


DFS1132I label PASSWORD HAS EXCEEDEDALLOWABLE LENGTH.

ExplanationPassword length has exceeded maximum allowablelength of 8 bytes. label is an internally generatedname, which uniquely identifies the statement.


Programmer responseCorrect the PASSWORD segment, and resubmit thejob.


Severity12




DFS1133I label MFLD LENGTH INCORRECTWHEN ATTR= YES AND/OR nnSPECIFIED

ExplanationMFLD length specified is less than that required for theinclusion of the specified number of attributes and atleast 1 byte of data.


Programmer responseSpecify an MFLD length that is equal to the maximumlength of the data, plus 2 bytes if ATTR=YES isspecified, and plus 2 times nn bytes if ATTR=nn isspecified. Then resubmit the job.

DFS1134I label LPAGE PROMPT=DFLDNAMENOT DEFINED THIS FMT

ExplanationThe dfldname specified in PROMPT= parameter is notdefined in the corresponding format.




Severity12


DFS1135I label WARNING: INPUT FROMDUPLICATE DFLD WILL BEIGNORED.

ExplanationMULT=YES is defined for DPAGE and a duplicate DFLDis encountered in DPAGE. This is a warning diagnostic—the duplicate DFLD is ignored by online processing.label is an externally defined name on the DFLDstatement.



Severity4


DFS1136I label DPAGE COND=SPECIFICATION MISSING

ExplanationA COND= specification is required on all input DPAGEstatements except the last-defined or only-inputDPAGE statement. label is the externally defined labelon the DPAGE statement or an internal label generatedif the external label is omitted.

System actionProcessing continues with the next DIV, DEV, or FMTstatement.

Programmer responseCorrect the DPAGE definition and rerun the job.

Severity12

DFS1137I label FILL=NULL INVALID WHENGRAPHIC=NO SPECIFIED.


ExplanationA message field (MFLD) with FILL=NULL was definedin the SEG statement with GRAPHIC=NO. The inputmessage control block is not be created. In themessage text,label

The external or internal label generated on theMFLD statement


Programmer responseCorrect the MFLDs with FILL=NULL in a SEGstatement with GRAPHIC=NO, and resubmit the job.


Severity:12


DFS1138I label DFLD MUST NOT BE USED ASLABEL WITHIN THIS DEV/DIV

ExplanationDfldname specified in the PFK=, PEN=, or CARD=parameter on the DEV statement or in the DPN=,PRN=, RPRN=, or RDPN parameter on the DIVstatement is used also as a label on a DFLD statementwithin this DEV/DIV.

System actionProcessing continues with the next DIV, DEV, MSG, orFMT definition.

Programmer responseCorrect the DFLD statement, and resubmit the job.

Problem determination1, 2, 3, 4, 8, 12, 16

Severity12


DFS1139I label keyword= PARAMETERINVALID FOR THIS DIV TYPE ANDWILL BE IGNORED.

ExplanationThis warning diagnostic is issued for DEV type of 274X,SCS1, SCS2, or DPM. If DIV TYPE=INPUT, an invalidkeyword of DSCA, PAGE, or FORMS was specified. IfDIV TYPE=INPUT and DEV type is SCS1, an invalidkeyword of HTAB, VTAB, or VT was specified. If DIVTYPE=OUTPUT, an invalid keyword of FTAB, LDEL,CARD (if SCS1) or MODE (except for DPM-Bn) wasspecified.


Severity8

DFS1140I name FMT DOES NOTDEFINE DEVICE OUTPUTDESCRIPTION FOR OUTPUTMESSAGE DESCRIPTION. FMTNOT PROCESSED.

Explanationname is the external label defined on the FMTstatement. FMT set was not compatible—device inputdescriptions (that is, DIV TYPE=INPUT) is associatedthrough the MSG SOR= parameter to the MSGdescription with TYPE=OUTPUT. This message isfollowed by one or more DFS1144I error messagesand possibly by one or more DFS1145I errormessages. A return code of at least 12 is passed toz/OS from the execution of Step 1 of the MFS LanguageUtility.

System actionProcessing continues normally with the next FMT orMSG definition.

Programmer responseCorrect the MSG or FMT definition, or both, andresubmit the job.



2, 8, 16, 36

Severity:12

Related information“DFS1141I” on page 397name FMT DOES NOT DEFINE DEVICEINPUT DESCRIPTION FOR INPUT MESSAGEDESCRIPTION. FMT NOT PROCESSED.“DFS1145I” on page 398name INPUT MESSAGE NOT PROCESSED.“IMS problem determination” on page 11IMS messages and codes problemdetermination is accomplished by usingprocedures established by IBM.

DFS1141I name FMT DOES NOT DEFINEDEVICE INPUT DESCRIPTION FORINPUT MESSAGE DESCRIPTION.FMT NOT PROCESSED.

Explanationname FMT is the external label defined on theFMT statement. FMT set was not compatible-deviceoutput descriptions, (that is, DIV TYPE=OUTPUT) isassociated through the SOR= parameter to the MSGdescription TYPE=INPUT. This message is followed byone or more DFS1145I error messages and possibly byone or more DFS1144I error messages. A return codeof at least 12 is passed to z/OS from execution of Step1 of the MFS Language utility.

System actionProcessing continues normally with the next FMT orMSG definition.



Severity:12

Related information“DFS1144I” on page 398name OUTPUT MESSAGE NOT PROCESSED.“DFS1145I” on page 398name INPUT MESSAGE NOT PROCESSED.“IMS problem determination” on page 11IMS messages and codes problemdetermination is accomplished by usingprocedures established by IBM.

DFS1142I WARNING: NO OUTPUT MESSAGEDESCRIPTION FOR DEVICEOUTPUT DESCRIPTION IN nameFMT.

Explanationname is the external label defined on the FMTstatement. A device output description (that is, DIVTYPE=OUTPUT or DIV TYPE=INOUT) has no MSGdescription with TYPE=OUTPUT associated with itthrough the SOR= parameter.


Programmer responseThis error can produce undesirable blocks in the onlineformat library. If a MSG output description is required,define it and resubmit the job.


Severity4


DFS1143I WARNING: NO INPUT MESSAGEDESCRIPTION FOR DEVICE INPUTDESCRIPTION IN name FMT.

Explanationname is the external label defined on the FMTstatement. A device input description (that is, DIVTYPE=INPUT or DIV TYPE=INOUT) does not have aMSG description with TYPE=INPUT associated with itthrough the SOR= parameter. This error can produceundesirable blocks in the online format library.




Severity4


DFS1144I name OUTPUT MESSAGE NOTPROCESSED.

Explanationname is the external label defined on the MSGstatement. This error message is printed as a resultof a DFS1140I error message. It can also be printed asa result of a DFS1141I error message when the FMTset is not processed.

System actionProcessing continues normally with the next FMT set.



Severity12


DFS1145I name INPUT MESSAGE NOTPROCESSED.

Explanationname is the external label defined on the MSGstatement. This error message is printed as a resultof a DFS1141I error message. It can also be printed asa result of a DFS1140I error message when the FMTset is not processed.

System actionProcessing continues normally with the next FMT set.



Severity12


DFS1146I BAD COMPLETION CODERECEIVED FROM IEBCOPYSUBTASK ON COMPRESS OFDDNAME=FORMAT. EXECUTIONTERMINATED.

ExplanationThe z/OS Image Copy utility program (IEBCOPY)issues a return code that indicates either a conditionfrom which recovery might be possible or indicates anunrecoverable error.

System actionProcessing terminates.

Programmer responseDetermine the problem by using the IEBCOPYmessages previously received, and the associatedIEBCOPY program message documentation.


Severity:20

Related referencez/OS: IEBCOPY (Library Copy) ProgramRelated information“IMS problem determination” on page 11IMS messages and codes problemdetermination is accomplished by usingprocedures established by IBM.

DFS1147I label WARNING: DEV VT=/VTAB=IS INVALID WITH PAGE 'FLOAT'OPTION. VT=/VTAB= PARAMETERWILL BE IGNORED.


http://www-01.ibm.com/support/knowledgecenter/SSLTBW_2.4.0/com.ibm.zos.v2r4.ieab100/iea3b1_IEBCOPY.htm?lang=en

ExplanationThe VT= or VTAB= parameter and the PAGE FLOAToptions were specified in the same DEV statement.The VT= or VTAB= specification is ignored. The fieldlabel is the external or internally generated label onthe DEV statement.


Programmer responseIf the VT= or VTAB= option is desired, correct thePAGE option and rerun the job.


Severity8


DFS1148I label WARNING: DPAGEFILL=NONE OR NULL IS INVALIDWITH HTAB 'ONLINE' OR'OFFLINE'. HTAB OPTION RESETTO SET.

ExplanationDPAGE with FILL=NULL or FILL=NONE was specified inthe DEV statement with the HTAB OFFLINE or ONLINEoption. The OFFLINE or ONLINE option will be resetto SET. The field label is the external or internallygenerated label on the DPAGE statement.


Programmer responseIf the HTAB OFFLINE or ONLINE option is desired,correct the DPAGE fill character specification, andresubmit the job.


Severity8


DFS1149I label DPAGE HAS EXCEEDEDALLOWABLE LENGTH.

ExplanationThe DPAGE definition currently being processed hasexceeded the MFS buffer design limit of 32767 bytes.The work buffer contains literals, data fields, andcontrol characters for the entire DPAGE. The field labelis the name specified on the DPAGE statement. IfDPAGE was not externally defined, label is the nameof the DIV statement.


Programmer responseThe DPAGE definition cannot be processed in itscurrent form. Redefine the DPAGE definition asmultiple DPAGEs and resubmit.


Severity12


DFS1150I label WARNING: POTENTIALERROR IF THE CURSOR POSITIONON INPUT IS 63 (HEX'3F').THE SEGMENT IN WHICH THISMFLD EXISTS WILL HAVE ALLTHE NULL CHARACTERS (HEX'3F') REMOVED, INCLUDING THECURSOR POSITION.


ExplanationFor more information, see the topic titled "Messageformatting functions" in IMS Version 15 ApplicationProgramming APIs.

Severity:4




DFS1151I label WARNING: HEADER MAYNOT FIT WITHIN A RECORD.

ExplanationThe message output header maximum size, calculatedby the utility, exceeds the RCDCTL= value specifiedon the DIV statement for HDRCTL=VARIABLE. Thefield label is the externally-defined name on theFMT/DPAGE/PPAGE statement determined by theOPTIONS= specification on the DIV statement, or labelis an internally-generated statement label.

System actionProcessing continues with this statement.

Programmer responseVerify that the message output header to be sent tothe remote program fits in a record. If not, eitherdefine a larger record size or create smaller headersand resubmit the job.

DFS1152I label HEADER WILL NOT FITWITHIN A RECORD.

ExplanationThe message output header size, calculated by theutility, exceeds the RCDCTL= value specified on theDIV statement for HDRCTL=FIXED. The field labelis the externally-defined name on the FMT/DPAGE/PPAGE statement determined by the OPTIONS=specification on the DIV statement, or label is aninternally-generated statement label.

System actionProcessing continues with the next DIV, DEV, FMT orMSG definition.

Programmer responseDefine a larger record size or specify a VARIABLEparameter on the HDRCTL= parameter of the DIVstatement. Resubmit the job.

DFS1153I label WARNING: PPAGECONTAINS NO DATA.

ExplanationA PPAGE statement containing no DFLD statementswas encountered for OPTIONS=PPAGE specified onthe DIV statement. This causes MFS to generate amessage output header only (no data fields) to besent to the remote program as the only transmissionand causes the component to be protected. A pagingrequest must then be sent to IMS to receive data. Thefield label is the user-supplied or internally-generatedlabel on the PPAGE statement.

System actionProcessing continues with this statement.

Programmer responseVerify that only a message output header function isdesired for the remote program.

DFS1154I label PPAGE CONTAINS NO DATA.PPAGE IGNORED.

ExplanationA PPAGE statement containing no DFLD statementswas encountered. For DEV TYPE=DPM-An or DPM-Bn and DIV OPTIONS=MSG or DPAGE, this PPAGEbegins a new record and has no other effect on theremote program. For DEV TYPE=DPM-Bn and DIVOPTIONS=(PPAGE,NODNM), this PPAGE statementwould not result in any meaningful information for theremote program. The field label is the user-supplied orinternally-generated label on the PPAGE statement.

System actionThe PPAGE statement is ignored. Processing continueswith the next statement.

Programmer responseRemove the PPAGE statement from the input stream, ifdesired, and resubmit the job.

DFS1155I label THE RESULTING DIF/DOFBLOCK HAS EXCEEDED THEDESIGN LIMITS.


ExplanationThe DIF/DOF block currently being created hasexceeded the design limit of 32767 bytes for a block.


Programmer responseThe DIF/DOF must be made smaller by defining fewerDPAGE or DFLD statements, or both. Resubmit the job.

Severity16

DFS1156I label WARNING: DUPLICATE SCAFIELD IN DPAGE.

ExplanationOnly one SCA field should be defined in a DPAGEstatement. The field label is the user-supplied orinternally-generated label on the DFLD statement withthis SCA option.

System actionProcessing continues with the current statement.

Programmer responseIf duplicate SCA information within a DPAGE is notdesired, remove duplicate SCA fields in this DPAGEstatement and resubmit the job.

DFS1157I label NO. OF PPAGES EXCEEDSMAXIMUM.

ExplanationThe number of PPAGE statements defined in thisDPAGE, with OPTIONS=PPAGE specified in the DIVstatement, has exceeded the design limit of 256pages. The field label is the user-supplied orinternally-generated label on the PPAGE statement.


Programmer responseReduce the number of PPAGE statements in thisDPAGE to less than the maximum or define the

current DPAGE in two or more DPAGE statements, andresubmit the job.

Severity16

DFS1158I labell IMSSYSTEM MESSAGEDEFINED INCORRECTLY

ExplanationThe MFLD literal containing the IMS system messageDFS057I has been defined incorrectly. The length ofthe literal is greater than 62, thereby preventing MFSfrom properly inserting system information into thesystem message, or the MFLD containing the systemmessage is not in the default MOD DFSM03. The fieldlabel is the external or internally-generated label ofthe MFLD statement.


Programmer responseChange the MFLD length to be less than or equal to62, or remove the system message literal from theuser-supplied MOD.

DFS1159I label A MESSAGE CONTAINING ANIMS SYSTEM MESSAGE MAY NOTDEFINE OTHER LITERALS.

ExplanationThis message is issued for the DFSM03 message,the IMS MFS error default block. This message mustdefine only one literal: the IMS system message. Noother literal definitions are permitted. The field label isthe external or internally-generated label of the MFLDstatement.


Programmer responseRemove all MFLD literals except the IMS systemmessage from the MSG block. Rerun the job.

DFS1160I name DFLDNAME SPECIFIEDFOR MORE THAN ONE OF THEDPN, PRN, RDPN, AND RPRNPARAMETERS


ExplanationA dfldname (name) was specified in more than one ofthe following parameters on the DIV statement: DPN=,PRN=, RDPN, and RPRN=. The dfldname for each ofthese parameters, if specified, must be unique.

System actionThe specification is ignored for all duplicateparameters, and processing continues with the nextDEV, FMT, or MSG definition.

Programmer responseRedefine the dfldname for the conflicting parameters,and resubmit the job.


Severity:8


DFS1161I label DPAGE LABEL IS REQUIRED

ExplanationA label must be defined for each input DPAGEstatement if OPTIONS=DNM is specified on the DIVstatement. label is the internal label generated by theMFS preprocessor.

System actionProcessing continues with the next DIV, DEV, FMT, orMSG statement.

Programmer responseCorrect the DPAGE definition, and rerun the job.

Severity12

DFS1162I label WARNING: ATTR=nnSPECIFIED FOR DFLDNAMEWHICH HAD NO EATTR=SPECIFICATION

ExplanationA request has been made to dynamically modifythe extended attribute bytes for a dfldname (label)for which no extended attributes (using EATTR=)have been specified. The request will be honoredin expectation of other formats or future formatscontaining this dfldname that do have extendedattributes. IMS still assumes that (2x nn) additionalbytes have been included in the LTH= specification forthis MFLD to be used for the attribute modificationbytes that are specifiable by the IMS applicationprogram.


Programmer responseVerify that the ATTR=nn specification is really desired,or that the EATTR= parameter was not inadvertentlyomitted from the DFLD statement.

Problem determination2, 8 16

Severity4


DFS1163I label WARNING: ATTR=YESAND/OR nn SPECIFIED ONMFLD STATEMENT, BUT NOTON CORRESPONDING DFLDSTATEMENT

ExplanationFor DPM-An or DPM-Bn, a request has been made topass attribute data from an IMS application programto a remote program or subsystem by specifyingATTR=YES or nn, or both, on the MFLD statement.However, ATTR=YES or nn, or both, was not alsospecified on the corresponding DFLD statement. Therequest will be honored in expectation of otherformats or future formats containing this dfldnamewhich do have attributes. IMS still assumes that 2additional bytes for ATTR=YES and (2xnn) additionalbytes for ATTR=nn have been included in the LTH=specification for this MFLD to be used for the attribute


modification bytes specifiable by the IMS applicationprogram.


System programmer responseVerify that the ATTR=YES or nn, or both specificationon the MFLD statement is really desired, or that theATTR=YES or ATTR=nn specifications, or both, werenot inadvertently omitted from the DFLD statement.


Severity4


DFS1164 label WARNING: SPANNED EGCSFIELD MAY BE INCORRECTLYSPLIT

ExplanationThe EGCS field (label) spans multiple lines. This fieldshould contain an even number of characters on eachline. The line width (WIDTH=) and starting position ofthe field (POS=) are determining factors in the amountof data that will fit on each line.


Programmer responseIf the field is defined to have an even number ofcharacters on each line, ignore this warning message.If the field is defined so that one or more lineswill have an odd number of characters, correct thedefinitions and rerun the job.




DFS1165W DUPLICATE RDDS ENTRIESWERE FOUND FOR resource_typeresource_name

ExplanationThe resource definition data set (RDDS) containedmultiple entries for the indicated resource. Thissituation might occur in a non-system RDDSthat has been the target of an EXPORT DEFNOPTION(APPEND) command. If there are multipleresource entries, the latest entry is the one that isused when the definitions in the RDDS are imported.Possible values for resource_type are:

DBDBDESCPGMPGMDESCRTCRTCDESCTRANTRANDESC

System actionThe RDDS Extraction Utility (DFSURDD0) continuesprocessing. It terminates successfully with return code4.

Programmer responseIf multiple definitions for the same resource werenot expected, consider exporting a new set ofdefinitions to the RDDS by using the EXPORT DEFNOPTION(OVERWRITE) command.

Module:DFSURDD0

DFS1166I RC=08 MFLD LITERALINCONSISTENT WITH DFLDSPECIFICATION

ExplanationA DBCS/EBCDIC mixed field literal was specified onan MFLD statement, but was not specified on thecorresponding DFLD statement.

System actionMFS will not create MOD/MID and DOF/DIF blocks.


Programmer responseEither define DBCS/EBCDIC mixed field literals on bothstatements, or remove the DBCS/EBCDIC mixed fieldliteral specification from the MFLD statement; thenrerun the job.

DFS1167I RC=04 label DFLD HAS NO SPACEAT RIGHT SIDE FOR FIELDOUTLINING

ExplanationThe DFLD statement specifies right field outlining, butthere is no space to print the right outline.


Programmer responseIf field outlining is necessary for this field, change thefield outlining specification; then rerun the job.

DFS1168I RC=04 label DFLD HAS NOSPACE AT LEFT SIDE FOR FIELDOUTLINING

ExplanationThe DFLD statement specifies left field outlining, butthere is no space to print the left outline.


Programmer responseIf field outlining is necessary for this field, change thefield outlining specification; then rerun the job.

DFS1169I ABEND U0780 RC=yyCAUSED BY ABENDIN ASID=xxxx, JOBNAME=jjjjjjjj/UNKNOWN WHILE HOLDINGLATCH AT ADDRESS=aaaaaaaa

ExplanationA dependent region has abended while holding a latch,causing the IMS control region to abend 0780.yy

is the abend 0780 return code.xxxx

identifies the failing address space identifier(ASID)

jjjjjjjj/UNKNOWNeither the failing address space's jobname or thecharacter string UNKNOW when the jobname cannotbe determined.

aaaaaaaathe address of the latch header. This address canbe located in the abend 0780 memory dump.An EBCDIC character string preceding the headeridentifies the latch.

System actionAn abend 0780 is issued in the IMS control region andall the IMS-dependent regions terminates abnormallywith completion code 002.

Programmer responseLocate the abend 002 dump for the dependent regionidentified in message DFS1169I to isolate and correctthe original abend.


DFS1170I cccccccc HDC DICTIONARYCREATED IN DD HDCDOUT FILE

ExplanationThis message indicates that the Hardware DataCompression Dictionary (HDCD) utility programsuccessfully completed with a return code 0. The valuecccccccc is the dictionary name that was passed as aparameter to the HDCD utility.

System actionThe HDCD utility has terminated normally.



Problem determinationNone.

DFS1171W cccccccc HDC DICTIONARY NOTCREATED, BECAUSE POTENTIALSTORAGE SAVINGS WILL NOT BEREALIZED.



ExplanationThis message indicates that the HDCD utility programsuccessfully completed but did not create a dictionaryobject file and terminated with return code 4. Thevalue cccccccc is the dictionary name that was passedas a parameter to the HDCD utility.

System actionThe HDCD utility has terminated with return code 4.




DFS1172E cccccccc HDC DICTIONARY NOTCREATED, BECAUSE SOURCEDATA DOES NOT MATCHEXPANDED DATA. THE FIRST 10MISMATCHED RECORDS WILL BEPRINTED BEFORE COMPRESSIONSTATISTICS

ExplanationThis message indicates that the HDCD utility programhas detected mismatched source and expanded data.Therefore, it did not create a dictionary object file andterminated with a return code 8. The dictionary namethat was passed as a parameter to the HDCD utility isdenoted by cccccccc.

System actionThe HDCD utility has terminated with return code 8.


System programmer response:Contact your DBA.


DFS1173W HDC DICTIONARY NOT CREATED,BECAUSE MVS CSRCMPSCSERVICE IS NOT INSTALLED.

ExplanationThis message indicates that the HDCD utility programhas detected that the z/OS Compression/ExpansionService, CSRCMPSC, has not been installed. The HDCdictionary cannot be created.

System actionThe HDCD utility has terminated.


System programmer response:Install z/OS CSRCMPSC, if required, and rerun theHDCD utility.

Problem determination:None

DFS1174E HDC DICTIONARY NOT CREATED,BECAUSE MVS CSRCMPSCSERVICE HAD A LOGIC ERROR.

ExplanationThis message indicates that the HDCD utilityprogram has detected a logic error while usingthe z/OSCompression/Expansion Service (CSRCMPSC)macro. The HDC dictionary was not created.

System actionThe HDCD utility has terminated.


System programmer response:Contact IBM Software Support.

DFS1175I MADS I/O TIMING PROCESSINGERROR FOR AREA areanameDDN=ddname RC=xx

ExplanationIMS detected an error during MADS I/O timing. Thereason code indicates the cause of the failure. In themessage text:areaname

The name of the area that the long busy ADSbelongs to.



xxThe reason code:X'10'

MADS I/O timing cannot continue across anemergency restart.

System actionLong busy ADS is stopped during emergency restart;the identified area is stopped globally if the area isshared with block level.


DFS1176E THE program FAILED TOSTART BPE LIMITED FUNCTIONSERVICES, RC=xxxxxxxx

ExplanationAn error occurred trying to start the BPE LimitedFunction Services (LFS).

In the message text:program

Can be one of the following values:

RDDS EXTRACTION UTILITYGLOBAL ONLINE CHANGE UTILITYDFS3UCD0

xxxxxxxxThe return code from the BPESTARTFUNC=STARTLFS function

System actionThe RDDS Extraction Utility (DFSURDD0) terminatesabnormally with RC=56.

Programmer responseRefer to the BPE0042E message for details on whyBPE LFS could not be started.

Module:DFSURDD0, DFSUOLC0

Related informationBPE0042E (Messages and Codes)

DFS1177E THE RDDS EXTRACTION UTILITYFAILED TO OPEN THE ddnameDATA SET, OPEN RC=rc

ExplanationThe RDDS Extraction Utility (DFSURDD0) failed to openone of the required data sets.


The data set which encountered the openerror. Possible values for ddname are SYSPRINT,SYSOUT and RDDSDSN.

rcThe return code from the open request

System actionThe RDDS Extraction Utility (DFSURDD0) terminatesabnormally with one of the following return codes:

• RC=8 - An error occurred trying to open theSYSPRINT data set

• RC=12 - An error occurred trying to open theSYSOUT data set

• RC=40 - An error occurred trying to open the RDDSdata set

Programmer responseCheck to make sure the DD statement for the data setis defined correctly.

Module:DFSURDD0

DFS1178I THE RDDS EXTRACTION UTILITYIS PROCESSING RDDS dsname

ExplanationThe RDDS Extraction Utility (DFSURDD0) is in theprocess of reading the resource definition data set(RDDS) defined on the RDDSDSN DD statement.

In the message text:dsname

The name of the resource definition data set beingread

System actionThe RDDS Extraction Utility (DFSURDD0) continuesprocessing.


Module:DFSURDD0


http://www.ibm.com/support/knowledgecenter/SSEPH2_15.1.0/com.ibm.ims15.doc.msgs/msgs/bpe0042e.htm#bpe0042e

DFS1179E THE RDDS EXTRACTION UTILITYFAILED TO OBTAIN A 64-BITBUFFER, SIZE=strgsize, IARV64RC=rc

ExplanationAn error occurred trying to obtain 64-bit storage for aninternal buffer.

In the message text:strgsize

The amount of storage requestedrc

The return code returned from the 64-bit VirtualStorage Allocation (IARV64) request


Programmer response:Ensure that the MEMLIMIT parameter on either theEXEC or the JOB statement is set to 12 GB or higher.

Module:DFSURDD0

DFS1180E THE RDDS EXTRACTION UTILITYFAILED TO OBTAIN STORAGE,SIZE=strgsize, GETMAIN RC=rc

ExplanationAn error occurred while trying to obtain storage.

In the message text:strgsize

The amount of storage requestedrc

The return code returned from the MVS GETMAINrequest


Programmer response:Check the return code from the MVS GETMAIN requestto determine the cause of the failure.

Module:DFSURDD0

DFS1181E AN ERROR OCCURRED TRYINGTO READ THE SYSIN DATA SET,BPERDPDS RC=rc

ExplanationThe RDDS Extraction Utility (DFSURDD0) encounteredan error while trying to read the input parameters inthe SYSIN data set. The BPERDPDS macro opens andreads the SYSIN data set. In the message text:rc

The return code returned from the BPERDPDSrequest


Programmer response:Check to make sure that the SYSIN DD statement isdefined correctly.

Module:DFSURDD0

Related referenceBPERDPDS codes (Messages and Codes)

DFS1182E AN ERROR OCCURRED TRYINGTO PARSE THE SYSIN DATA,BPEPARSE RC=rc

ExplanationThe RDDS Extraction Utility (DFSURDD0) encounteredan error while trying to parse the data in the SYSINdata set. The BPEPARSE macro parses the SYSIN data.


The return code returned from the BPEPARSErequest


Programmer response:Ensure that the OUTPUT parameter is coded correctlyin the SYSIN data set.

Module:DFSURDD0

DFS1183E AN ERROR OCCURRED TRYINGTO PROCESS THE RDDSDSN DDSTATEMENT, RSNTEXT=rsntext

ExplanationAn error occurred trying to process the RDDSDSN DDstatement. rsntext indicates the reason for the error.Possible values for rsntext are:


http://www.ibm.com/support/knowledgecenter/SSEPH2_15.1.0/com.ibm.ims15.doc.msgs/compcodes/bperdpds.htm#bperdpds

RDJFCB REQUEST FAILED TO RETURN DSNAMEMULTIPLE RDDS DATA SETS DEFINED

System actionDFSURDD0 terminates abnormally with one of thefollowing return codes:

• RC=32 - The RDJFCB request failed to return thedsname of the RDDS data set

• RC=36 - More than one data set was specified for theRDDSDSN DD statement

Programmer response:Make sure that the RDDSDSN DD statement is codedcorrectly, and that it does not contain concatenateddata sets.

Module:DFSURDD0

DFS1184E AN ERROR OCCURRED TRYING TOREAD THE RDDS, GET RC=rc

ExplanationThe RDDS Extraction Utility (DFSURDD0) encounteredan error while trying to read the RDDS that wasspecified on the RDDSDSN DD statement.


The return code from the GET macro


Programmer response:Check the device on which the RDDS is located. Ifno permanent device error is detected, run the utilityagain.

Module:DFSURDD0

DFS1185E THE RDDS DOES NOT CONTAINVALID DATA, RSNTEXT=rsntext

ExplanationThe RDDS specified on the RDDSDSN DD statementis either not an RDDS or does not contain datafrom a successful export. rsntext in the message textindicates the reason for the error. Possible values forrsntext are:

DATA SET IS NOT AN RDDSDATA IS NOT FROM A SUCCESSFUL EXPORT

System actionDFSURDD0 terminates abnormally with one of thefollowing return codes:

• RC=48 - The data set specified on the RDDSDSN DDstatement is not an RDDS

• RC=52 - The RDDS specified on the RDDSDSN DDstatement does not contain data from a successfulexport

Programmer response:Update the RDDSDSN DD statement to point to anRDDS that contains valid data.

Module:DFSURDD0

DFS1186W THERE ARE NO TRANSACTIONSDEFINED FOR APPLICATIONapplname

ExplanationThere are no transactions defined for the application.If an application does not execute in a BMP typeregion and the application is not an IFP, you must havetransactions defined for the application in order for theapplication to be scheduled. applname in the messagetext is the name of the application with no transactionsdefined.

System action:Processing continues. Upon completion, DFSURDD0returns with a return code of 4.

Programmer response:The data in the RDDS might be corrupted. If theapplication should have transactions defined, rerunthe utility against an RDDS that contains data from asuccessful export.

Module:DFSURDD0

DFS1187W THERE ARE NO ROUTECODES DEFINED FOR FASTPATH EXCLUSIVE APPLICATIONapplname

ExplanationThere are no route codes defined in the RDDS for theFast Path exclusive application. applname is the nameof the application for which there are no route codesdefined.

System action:Processing continues. Upon completion, DFSURDD0returns with a return code of 4.

Programmer response:


The data in the RDDS might be corrupted. Rerun theutility against an RDDS that contains data from asuccessful export.

Module:DFSURDD0

DFS1188E HALDB yyyy CALL FAILED RC=ccccRS=ssss

ExplanationDuring processing a HALDB, a call to initialize one ormore partitions of a HALDB failed. An abend 0881 isissued.

In the message text:yyyy

the HALDB call, which can be:

• PINT – the call to initialize one or more partitionsof a HALDB failed

• UNLD – the call to insert the all X'FF' key for aHALDB failed

ccccthe return code, which can be:

0004 – unavailable data encountered0008 – environmental error detected0012 – logic error occurred0016 – a pseudoabend was already set

ssssthe reason code; for these codes, see messageDFS0832I.

System action:The current application terminates with an abend0881.

User responseLook for previous error messages related to thepartitions of this HALDB for the source of the error. Usethe return and reason codes in this message to correctthe problem.

If message DFS1188E HALDB PINT CALL FAILEDRC=0004 RS=4026 is received while loading theIMS catalog with DBRC=Y specified, check to seeif the UNREGCATLG= parameter is specified in theDFSDFxxx member of the IMS PROCLIB data setalthough the IMS catalog databases are registered inthe RECON data set. To correct the problem, removethe UNREGCATLG= parameter or specify DBRC=N.

Problem determination:1, 2, 3, 4, 8, 17a-f, 35, 40


ABEND Uwwww REASON CODE xxxx yyyyPARTITION | DATABASE zzzzzzzz“IMS problem determination” on page 11IMS messages and codes problemdetermination is accomplished by usingprocedures established by IBM.

DFS1189I INCONSISTENT LOCAL CONTROLBLOCKS USED FOR RM UPDATE

ExplanationThe Resource Manager (RM) update found an LTERMwith an owner control block name that is differentfrom the owner name passed in on the call. Thissituation might be due to a set of local blocks that donot match what is in RM. Generally, the local blocksin this circumstance have no status and are deleted atthe next simple checkpoint. After the local blocks aredeleted, the failing command should work.


Operator responseWait a few minutes and then attempt the commandagain.

Module:DFSIC450

DFS1190I REGION nnnn NOT WAITING ONyyyyyyyy xxxxxxxx

ExplanationA /PSTOP AOITOKEN or /PSTOP REGION SYNCcommand was entered, but the region was not waitingfor the specified AOI token or ICAL response.


nnnnThe region number entered on the command.

yyyyyyyyEither AOITOKEN or SYNC. AOITOKEN means thename that follows is an AOI token name. SYNCmeans that the name that follows is a TPIPE name(for a synchronous callout request) or a transactionname (for a synchronous program switch request).

xxxxxxxxThe AOI token name, TPIPE name, or transactionname entered on the command.



Operator responseEither the region number, AOI token name, orTPIPE name was specified incorrectly in the /PSTOPREGION command. Reenter the command with thecorrect values.

If yyyyyyyy is AOITOKEN, you can use the /DISPLAYACTIVE command to verify that the region issued aGMSG call with the wait option and is waiting fora message. You can use the /DISPLAY AOITOKENcommand to determine which AOI tokens areassociated with waiting regions.

If yyyyyyyy is SYNTPIPE, you can use the/DISPLAYACTIVE command to verify that the region issued anICAL call and is waiting for a synchronous calloutresponse. If the region is waiting for a synchronouscallout response (WAIT-CALLOUT), the TPIPE name isdisplayed in the display region continuation line.

Module:DFSSTOP0

DFS1191I AOITOKEN KEYWORDPARAMETER NOT FOUND

ExplanationA /DEQUEUE AOITOKEN command was entered, butthe parameter specified on the AOITOKEN keywordwas not found or is incorrect.


Operator responseIf the AOI token name was specified incorrectly,reenter the command with the correct name. Youcan use /DISPLAY AOITOKEN to find out which AOItokens have messages that can be dequeued.

DFS1192I NO MESSAGES TO DEQUEUEON AOITOKEN PARAMETERSPECIFIED

ExplanationA /DEQUEUE AOITOKEN command was entered, butthe specified AOI token had no messages to bedequeued.


Operator responseIf the AOITOKEN name was specified incorrectly,reenter the command with the correct name. Youcan use /DISPLAY AOITOKEN to find out which AOItokens have messages to be dequeued.

DFS1193I ccccc CMD FAILED FOR REGIONnnnnn tttt xxxxxxxx ssssssss RC=rrrrrrrr

ExplanationAn error occurred when the /PSTOP or /STOPcommand was processed.

In the message text:ccccc

Either PSTOP or STOP.nnnnn

The region number entered on the command.tttt

AOIT, TRAN, or SYNC. AOIT means that the namethat follows is an AOI token name. TRAN meansthat the name that follows is a transaction name.SYNC means that the name that follows is a TPIPEname.

xxxxxxxxThe AOI token name, transaction name, or TPIPEname entered in the command.

ssssssssThe service that failed during processing of thecommand.

rrrrrrrrThe return code from the failed service request.


Operator responseThe service failure might be a temporary problem. Tryto reenter the command. If the condition persists, aninternal IMS system error might exist.



DFS1194I LOGGING TO SECONDARYMASTER ERROR - CODE = x


ExplanationIMS found one of the following problems when loggingthe message or command segment to the secondarymaster terminal.Code

Meaning1

The queue manager handling a request returned anonzero code.

2A request for storage from the CIOP pool could notbe satisfied.

3An internal error was found while logging to thesecondary master terminal.

4The CBTS latch was held for an unexpected block-type during command processing.

5A request for storage from the HIOP for the LSMBcontrol block could not be satisfied.

System actionA 6701 trace record labeled LSM0 is written to theIMS log, except when code 5 is returned. In all cases,no further logging to the secondary master terminal isdone for this message or command segment.


DFS1195I /ASSIGN FAILED. OWNERS INDIFFERENT IMSs

ExplanationThe source resource being assigned was in a differentIMS from the destination resource, and both resourceswere owned by their respective IMS systems. Thiserror can only occur when IMS is using the IMSResource Manager in a sysplex environment. Thesource and destination resources must meet one ofthe following conditions:

• The source and destination resource must be in thesame IMS system.

• At least one of the resources must be known to theResource Manager and not owned by an IMS.


Operator responseEnsure that both resources are in the same IMS, orensure that at least one of the resources is known tothe Resource Manager and not owned by an IMS. Afterthe resource issue is resolved, reissue the /ASSIGNcommand.

Module:DFSICL70

DFS1196I /ASSIGN FAILED. SAVE KEYWORDREQUIRED IF USER DOES NOTEXIST WITH RM

ExplanationIf this IMS system is part of a sysplex using theIMS Resource Manager and the destination user doesnot exist, the /ASSIGN command is rejected. Also,the user might be immediately deleted, and theassignment would be incomplete. If the /ASSIGNcommand is issued with the SAVE keyword, theassignment persists for the user until another /ASSIGN command is issued with the NOSAVEkeyword.


Operator responseReenter the /ASSIGN command with the SAVEkeyword.

Module:DFSICL70

DFS1198I CONVERSATION UNUSABLE.COMMAND/TRANSACTION INPUTREJECTED

ExplanationThis error occurred for one of the following reasons:

• Conversational input data was entered to continuean IMS conversation. Due to the state of theterminal at the time the command was issued, theconversation cannot continue. The situation might betemporary if this conversation is being continued ona different IMS after the first IMS failed

• A /RELEASE command was entered for an IMSconversation that was being held. Due to the state ofthe terminal at the time the command was issued,the conversation cannot continue. The situationmight be temporary if the conversation is beingreleased on a different IMS system after the first IMSfailed.


• Conversational input data was entered to continuean IMS conversation. However, the conversationaltransaction does not exist. This situation can occurin a sysplex environment using the IMS ResourceManager. If a terminal logs off or a user signs offwhile still in an IMS conversation, and then logs onor signs on to a different IMS system where thetransaction is not defined properly, the conversationcannot be continued. Also, if the conversationaltransaction is deleted by an Online Change, then theconversation cannot be continued.

Terminal problems of this nature only occur whenIMS is using the IMS Resource Manager in a sysplexenvironment.

System actionThe transaction input or /RELEASE command isrejected.

Operator responseWait a short time, then reenter the input. If thecondition continues, you might need to issue the /EXIT command to clear the terminal and delete theconversation.

Module:DFSCON00, DFSICLH0

DFS1199I /CHANGE FAILED. SAVEKEYWORD REQUIRED IF USERDOES NOT EXIST WITH RM

ExplanationIf this IMS system is part of a sysplex using theIMS Resource Manager, and the user specified inthe /CHANGE USER AUTOLOGON command does notexist, the /CHANGE command is rejected unless youuse the SAVE keyword. The SAVE keyword specifiesthat the auto logon information persist until another /CHANGE command with the NOSAVE keyword is usedfor this user. Without the SAVE keyword, and anyother significant status, the user might be immediatelydeleted making the /CHANGE command ineffective.


Operator responseReenter the /CHANGE command with the SA keywordspecified.

Module:DFSICL60

DFS1200I MESSAGE/FORMAT SERVICEUTILITY DATE=mm/dd/yyTIME=hh.mm.ss PAGE nnnn

ExplanationThis message identifies the title or header line forSYSPRINT output from the MFS utility program.




DFS1201I UNABLE TO OPEN {SYSIN|SYSPUNCH|DCTIN|DEFLTS}

ExplanationThe DCB for the SYSIN, SYSPUNCH, DCTIN, or DEFLTSDD statement cannot be opened. The most probablecause is a missing DD statement.

System actionThe MFS Service utility processing continues with amissing SYSIN DD statement. The MFS DCT utility endswith a return code of 12 when any of the data setscannot be opened.


DFS1202I UNABLE TO OPEN SYSPRINT

ExplanationThe DCB for the SYSPRINT DD statement cannot beopened. The most probable cause is a missing DDstatement.

System actionThe MFS Service utility processing continues. The MFSDCT utility ends with a return code of 12.


DFS1203I STATEMENT LABEL IS TOO LONG.

ExplanationThe control statement label has exceeded 8 charactersin length.

System actionProcessing continues with the next statement.


DFS1204I STATEMENT HAS NO OPERATOR.

ExplanationA statement has been detected that did not contain anoperator.


Programmer responseMost probable cause is a blank statement in the inputstream.

DFS1205I OPERATOR LENGTH OR POSITIONERROR.

ExplanationA control statement has been detected whoseoperator exceeds eight characters or whose operatorend character falls in column 71.



DFS1206I COLUMNS 1 THROUGH -15 ARENOT BLANK ON CONTINUATION.

ExplanationColumns 1-15 must be blank in a continuationstatement.



DFS1207I COL 16 BLANK WHERECONTINUED OPERAND EXPECTED.


ExplanationOperands continued onto subsequent statement mustresume in column 16.



DFS1208I STATEMENT HASUNIDENTIFIABLE OPERATOR.

ExplanationThe control statement operator is invalid.



DFS1209I PROCESSING TERMINATED BYEOD ON SYSIN.

ExplanationNormal utility termination has occurred.

System actionThe job or step is terminated normally.

DFS1210I ACTION RTN FOR STATEMENT HASUNRESOLVED ADDRESS

ExplanationA valid statement type has been detected. However,the processing module for the statement type has anunresolved address constant.


Programmer responseEnsure correct binder input of all required actionmodules.



DFS1211I 1ST POSITIONAL PARAMETER ISUNIDENTIFIABLE.

ExplanationThe first positional parameter is probably misspelled.



DFS1212I STATEMENT HASUNIDENTIFIABLE KEYWORD.

ExplanationAn invalid keyword was detected for this controlstatement.



DFS1213I INTERNAL SCAN LOGIC ERROR,SNAP ID=127 TAKEN.

ExplanationAn internal scan logic error has occurred. A SNAPmemory dump has been taken to the SYSSNAP DDstatement.


Programmer responseAfter problem determination, visually scan thestatement causing the failure, correct the error, andresubmit the job.

Problem determination:1, 2, 3, 4, 8, 13, 24, 36



DFS1214I POSITIONAL PARAMETER ISINVALID.

ExplanationA positional parameter is probably misspelled.



DFS1215I EXPECTED KEYWORD NOTRECEIVED.

ExplanationA keyword was expected, but not found.



DFS1216I DELIMITER LENGTH ERROR.

ExplanationAn item with a length other than 1 was received wherea delimiter character was expected.


Programmer responseInsert the required delimiter and resubmit the job.

DFS1217I MISSING = AFTER KEYWORD.

ExplanationAn equal sign is required after the keyword.


Programmer responseInsert =, and resubmit the job.

DFS1218I UNEXPECTED STATEMENT ENDENCOUNTERED.

ExplanationThe control statement operand terminated wheremore information was required or expected.


Programmer responseComplete the operand, and resubmit the job.

DFS1220I EXPECTED KEY PARAMETER NOTRECEIVED.

ExplanationA keyword has been detected for which no parameterwas received.


Programmer responseSupply the desired parameter, and resubmit the job.

DFS1221I MSG=,TBL= OR PDB= PARAMETERTOO LONG.

ExplanationThe MSG, TBL, or PDB parameter exceeds 8characters.



DFS1222I MSG=, TBL= OR PDB= PARAMETERIS INVALID.


ExplanationEither the MSG, TBL, or PDB parameter containsan invalid character, or TBL=ALL or PDB=ALL wasspecified for a SCRATCH request.


Programmer responseIf the parameter contains an invalid character, correctthe parameter, and resubmit the job. If TBL=ALL orPDB=ALL was specified, change the parameter to theTBL or PDB name to be scratched, and resubmit thejob.

DFS1223I FMT= PARAMETER IS INVALID.

ExplanationThe FMT= parameter contains an invalid character orexceeds the 6-character maximum length.



DFS1224I KEYWORD PARAMETERDELIMITER IS INVALID.

ExplanationA character other than a blank or a comma followed aparameter in a control statement.


Programmer responseDelimit properly, and resubmit the job.

DFS1225I DEV= PARAMETER IS INVALID.

ExplanationDEV= specification is unknown.


Programmer responseSpecify the proper DEV= keyword, and resubmit thejob.

DFS1226I DIV= PARAMETER IS INVALID.

ExplanationDIV= specification is unknown.


Programmer responseSpecify the proper DIV= keyword, and resubmit thejob.

DFS1227I MDL= PARAMETER IS INVALID.

ExplanationMDL= specification is unknown.

System actionProcessing resumes with the next statement.

Programmer responseCorrect the parameter, and resubmit the job.

DFS1228I MISSING RIGHT PAREN ') ' INSUBLIST.

ExplanationA missing right parenthesis occurred in the sublist.



DFS1229I MUTUALLY EXCLUSIVEFEAT=PARAMETERS AND/ORDEV=PARAMETERS.

ExplanationConflicting parameter specifications have beenspecified.



Programmer responseRemove the conflicts, and resubmit the job.

DFS1230I FEAT= PARAMETER IS INVALID.

ExplanationFEAT= specification is unknown.



DFS1231I MUTUALLY EXCLUSIVE KEYWORDFOUND.

ExplanationTwo or more keywords on the control statement aremutually exclusive.


Programmer responseRemove the conflict, and resubmit the job.

DFS1232I FORMAT LIBRARY CONTAINS NOMEMBERS.

ExplanationThe active format library contains no members.



DFS1233I FORMAT LIBRARY FETCH ERRORON $$IMSDIR.

ExplanationAn error has occurred when attempting to read inthe special index directory, $$IMSDIR, from the activeformat library.


Programmer responseResubmit the job after determining the cause of theI/O error condition.

DFS1234I REQUESTED BLOCK DOES NOTEXIST IN $$IMSDIR.

ExplanationA delete request for a FMT/MSG descriptor has beenunsuccessful. The requested descriptors are not in $$IMSDIR.

System actionIf delete, processing continues with next statement. Ifscratch, continue with scratch processing.

Programmer responseIf delete, specify the correct descriptor name.Resubmit the job.

DFS1235I REQUEST IGNORED, $$IMSDIR ISFULL.

ExplanationAn INDEX request was ignored because the specialindex directory, $$IMSDIR, contains the maximumallowable number of entries.

System actionProcessing continues with the next action.

Programmer responseDelete $$IMSDIR entries, as applicable; then resubmitthe job.

DFS1236I REQUEST IGNORED, $$IMSDIR ISEMPTY.

ExplanationThe special INDEX directory, $$IMSDIR, contains noentries. The requested action could not be performed.



DFS1237I REQUESTED MSG DOES NOTEXIST IN FORMAT LIBRARY.

ExplanationThe requested action for a MSG descriptor requires theexistence of the descriptor.


Programmer responseSpecify the message name again and resubmit the job.

DFS1238 UNABLE TO COMPLETE INDEX ALLREQUEST

ExplanationThe index all request was not completed because ofa mismatch between the number of members on theformat library and the number of entries in the existingspecial index directory, $$IMSDIR.


Programmer responseDelete the existing special index directory, $$IMSDIRby entering /DELETE ALL; then resubmit the job.

DFS1239I ERROR OCCURRED ON WRITE FOR$$IMSDIR

ExplanationDuring termination processing of the MFS Languageutility, an error occurred when attempting to WRITEand STOW the final version of the INDEX directory intothe active format library.


Programmer responseAfter determining the cause of the I/O error, correct it,and resubmit the job.

DFS1240I INVALID COMMENT DELIMITER-POSSIBLE MISPUNCHEDSTATEMENT.

ExplanationYou must begin a comment on a control statementwith the 2-character sequence: /*.



DFS1241I END OF LIST FUNCTION.

ExplanationNormal LIST function has finished.


DFS1242I INSUFFICIENT STORAGEAVAILABLE FOR INDEX.

ExplanationThe special index directory, $$IMSDIR, cannot befetched into storage for processing because ofinsufficient real storage resources.


Programmer responseIncrease the region size for the operation, or specifythe positional parameter INDEX, or both.

DFS1243I INTERNAL FETCH ERROR, SNAPID=126 TAKEN.

ExplanationAn internal logic error has occurred in the blockservice module DFSUTSQ0. A SNAP memory dump hasbeen taken on the SYSSNAP data set.






DFS1244I NO OTHER KEYWORDS MAYBE SPECIFIED WITH FMT=WHEN ACTION IS AGAINST THEREFERAL LIBRARY.

ExplanationWhen you are running an action against the REFERALlibrary, no other keywords can be specified with FMT=.


Programmer responseRemove the extra DEV, DIV, MDL, or FEAT keywords,and resubmit the job.

DFS1245I REQUIRED KEYWORD NOTPRESENT.

ExplanationSCRATCH FORMAT cannot be requested withoutspecifying the FMT keyword.


Programmer responseSpecify the format name or ALL. Correct, and resubmitthe job.

DFS1246I INTERNAL INDEX/DELETE LOGICERROR. SNAP ID=125 TAKEN.

ExplanationAn internal logic error has occurred in the DIRMAINTsubroutine of the INDEX/DELETE action module,DFSUTSG0. A SNAP memory dump has been taken onthe SYSSNAP DD statement data set.





DFS1247I MEMBER= name RECEIVEDRETURN CODE= nnnn FROM STOWWITH DELETE OPERATION.

ExplanationA requested scratch action for the member with namereceived a return code of nnnn from the host systemSTOW function. nnnn is the hexadecimal return codereceived.


Programmer responseSee the host system STOW function return codes forthe interpretation of the nnnn value returned.

Related referencez/OS: STOW completion codes

DFS1248I REQUESTED FMT DOES NOT EXISTIN FORMAT LIBRARY.

ExplanationThe requested action for format (FMT) control blockdescriptors has been unsuccessful. The requesteddescriptors are not in the FORMAT library.


Programmer responseSpecify the correct format name, and resubmit the job.



DFS1249I REQUESTED MSG DOES NOTEXIST IN REFERAL LIBRARY.

ExplanationA SCRATCH request for a REFERAL library memberwas not performed for one of the following reasons:

• The member is unknown to the MFS Utility programDFSUTSO0.

• The member to be scratched is actually an FMT orTBL description.


Programmer responseSpecify the correct message name, and resubmit thejob.

DFS1250I REQUESTED FMT DOES NOT EXISTIN REFERAL LIBRARY.

ExplanationA SCRATCH request for a REFERAL library memberwas not successful for one of the following reasons:

• The member is unknown to the MFS Utility programDFSUTSO0.

• The member to be scratched is actually a MSG orTBL description.


Programmer responseSpecify the correct format name, and resubmit the job.




DFS1251I REQUESTED TBL DOES NOT EXISTIN REFERAL LIB.

ExplanationA scratch request for a REFERAL library member wasunsuccessful for one of the following reasons:

• The member is unknown to the MFS Utility.• The member to be scratched is actually an FMT or

MSG description.


Programmer responseCheck the REFERAL listing to correct the error, specifythe TBL again, and then resubmit the job.

DFS1252I I/O ERROR ON REFERAL, SNAPID=124 TAKEN.

ExplanationAn I/O error has occurred on the REFERAL library. ASNAP dump has been taken to the SYSSNAP DD dataset.

System actionProcessing continues with the next source statement.

Programmer responseDetermine the cause of the I/O error, correct the error,and resubmit the job.

DFS1253I LIBRARY CONTENTS AREINVALID, SNAP ID=124 TAKEN.

ExplanationThe contents of the REFERAL library PDS are incorrect.


Problem determinationSource, listing from failing run, list PDS of REFERAL.

DFS1254I REQUESTED PDB DOES NOT EXISTIN REFERAL LIBRARY

ExplanationA SCRATCH request for a Partition Descriptor Block(PDB) member in the REFERAL library was notperformed because the member was not found.


Programmer responseCorrect the PDB name, and rerun the job.

DFS1255I THE PARAMETER{DCTSUF=|DSCTSUF=|DSCMSUF=|DEVCHAR=}x SPECIFIED IN THEEXEC STATEMENT IS {WRONGLENGTH|INVALID|DUPLICATE}

ExplanationThe suffix 'x' given in the EXEC statement as anappendage to complete the Device CharacteristicsTable or descriptor member name (DFSUDT0x,DFSDSCTx, or DFSDSCMx) contain characters that donot allow a valid member name to be generated.

System actionExecution continues. The Device CharacteristicsTable member name defaults to DFSUDT00,unless otherwise specified in a subsequent MFSService Utility control statement. The MFS DeviceCharacteristics Table utility ends with a return code of4. The descriptor member name defaults to DFSDSCT0or DFSDSCM0.

Programmer responseIf the output produced is not satisfactory, specify avalid suffix in the EXEC statement parameter field, andresubmit the job.

DFS1256I THE PARAMETER DEVCHAR=xSPECIFIED IN THE CONTROLSTATEMENT IS {WRONG LENGTH|INVALID}


ExplanationThe suffix "x" given in the control statementas an appendage to complete the DeviceCharacteristics Table member name (DFSUDT0x)contained characters that would not allow a validmember name to be generated.

System actionThe control statement will be ignored, and executionwill continue with the control statement following.

Programmer responseEnter the correct suffix in the control statement, andresubmit the job.

DFS1257I BLDL ERROR, RETURN CODE=xx

ExplanationA nonzero return code was returned from the BLDL forthe Device Characteristics Table member. The membername is DFSUDT0x, where x is specified with theDCTSUF= keyword for the MFS Device CharacteristicsTable utility and with the DEVCHAR= keyword for theMFS Service utility. The default name is DFSUDT00.

System actionFor the MFS Service utility, the control statementis ignored, and execution continues with the controlstatement following. The MFS Device CharacteristicsTable utility ends with a return code of 12.

Programmer responseEnter the correct suffix in the control statement orEXEC statement keyword, and resubmit the job.


DFS1258I SYMBOLIC NAME 3270-Ann ISINVALID

ExplanationThe symbolic name 3270-Ann specified in the DEV=parameter is invalid. The number nn appended to3270-A was not within the range "1 to 15", or thelength of nn was less than 1 or more than 2.

System actionThe control statement will be ignored, and executionwill continue with the control statement following.

Programmer responseCorrect the specification in the control statement, andresubmit the job.

DFS1259I nnnn IS AN INVALID KEY NUMBER

ExplanationMessage generator module DFSUTSC0 has received arequest to generate a message with a key of nnnn Themessage requested does not exist in a known messagetable.



Problem determination1, 2, 3, 4, 8, 12, 13, 36


DFS1260I UNABLE TO OPEN FORMATLIBRARY

ExplanationOne of the DCBs for the FORMAT DD statement couldnot be opened.

System actionProcessing continues with the next utility controlstatement.

Programmer responseMake sure that the DD statement for FORMAT hasbeen included and is specified correctly. Resubmit thejob.

DFS1261I UNABLE TO OPEN REFERALLIBRARY



ExplanationOne of the DCBs for the REFIN DD statement could notbe opened.

System actionProcessing continues with the next utility controlstatement.

Programmer responseMake sure that the DD statement for REFIN has beenincluded and is specified correctly. Resubmit the job.

DFS1262I MESSAGE FORMAT SERVICEDCT UTILITY DATE=mm/dd/yyTIME=hh.mm.ss PAGE nnnn

ExplanationThis message is the title or header line for theSYSPRINT output data set from the MFS DeviceCharacteristics Table (DCT) utility program. Thismessage is written only when an error is found in thefirst step of the utility. An error message follows themessage.

DFS1263X FIND FAILED FOR DESCRIPTORMEMBER xxxxxxxx RETURNCODE=X'yyyyyyyy'

ExplanationThe FIND failed for descriptor member xxxxxxxx fromthe PROCLIB data set. The member name is eitherDFSDSCMa, where a is specified in the DSCMSUF=parameter, or it is DFSDSCTb, where b is specified inthe DSCTSUF= parameter.

System actionThe MFS Device Characteristics Table utility ends witha return code of 12.

Programmer responseDetermine why the MFS Device Characteristics Tableutility could not locate the specified descriptormember in the data set with the ddname PROCLIB.

DFS1264W DEVCHAR SUFFIX xx TRUNCATEDTO FIRST CHARACTER

ExplanationMore than one character was specified in theDEVCHAR= parameter of the EXEC statement. The

message displays only the first two characters thatwere specified.

System actionOnly the first character is used as the one-charactersuffix for the device characteristics table name. TheMFS Device Characteristics Table utility ends with areturn code of 4.

Programmer responseSpecify a valid single alphanumeric suffix for theDEVCHAR= parameter on the EXEC statement. Then,rerun the job.

DFS1265I IMS CONNECT CALL TO THE MVSWORKLOAD MANAGER FAILED,RETURN CODE= nn, REASONCODE=nnnn.

ExplanationThe z/OS Workload Management service returned anonzero return code when IMS attempted to connectto it.

System actionIMS continues with initialization, but will notparticipate with z/OS Workload Management services.

Programmer responseSee the z/OS documentation for an explanation of thereturn code and reason code.

Related informationz/OS: Introduction to the workloadmanagement servicesz/OS: IWMCONN — Connect to workloadmanagement

DFS1266 INCORRECT SPECIFICATION OFLU NAME

ExplanationThe network-qualified LU name in the command isspecified incorrectly. A network-qualified LU name hasa maximum length of 17 bytes that is composed of 8bytes maximum network ID, and 8 bytes maximumLU name separated by a period enclosed in singlequotation marks, for example, 'networkid.luname'Network-qualified LU names must be surrounded bysinge quotation marks when entered on a command,and there can be no blanks.


https://www-01.ibm.com/support/knowledgecenter/en/SSLTBW_2.4.0/com.ibm.zos.v2r4.ieaw200/ieaw20015.htm

https://www-01.ibm.com/support/knowledgecenter/en/SSLTBW_2.4.0/com.ibm.zos.v2r4.ieaw200/ieaw20015.htm

https://www-01.ibm.com/support/knowledgecenter/en/SSLTBW_2.4.0/com.ibm.zos.v2r4.ieaw200/conn.htm

https://www-01.ibm.com/support/knowledgecenter/en/SSLTBW_2.4.0/com.ibm.zos.v2r4.ieaw200/conn.htm

The command was rejected for one of the followingreasons:

• A period is missing between the network ID and theLU name.

• The length of the network ID or the LU name field isgreater than 8 bytes.

• The closing singe quotation mark is missing.• There is a blank somewhere between the singe

quotation marks .• Parameter ALL was specified either in the network

ID or the LU name field.• An invalid character was encountered in thenetwork-qualified LU name.

•


Operator responseReenter the command with the correct format of anetwork-qualified LU name.

DFS1267 PARAMETER CONTAINS INVALIDCHARACTERS

ExplanationThe parameters that are specified in the commandcontain invalid characters. Valid characters forparameters are the alphanumeric characters: 'A'through 'Z', 'a' through 'z', '0' through '9', the threenational characters '#','$','@', and the two genericcharacters '%', and '*'.


Operator responseReenter the command by using valid characters.

DFS1268 NO TPIPES ASSOCIATED WITHTMEMBER

ExplanationA command specified the TMEMBER, TPIPE, and ALLkeywords, but no OTMA Tpipes are associated with thespecified transaction member.


Module:DFSYC490, DFSYDPD0, DFSICLN3

DFS1269E SEVERE IMS INTERNAL FAILURE,REASON CODE=xxyy

ExplanationIMS experienced an internal error. See the followingtable for a list of reason codes xxyy.


xxA decimal number that identifies the module thatexperienced the error.

yyAn internal reason code.

If yy is 98 or 99, the error can occur in anymodule. For example: REASON CODE=4698 occursin module DFSYRST0, and REASON CODE=2898occurs in module DFSYGRX0.

Table 10. DFS1269E reason codes

xx yy Module Description

xx 98 DFSPOOL Failure to acquire storage for avariable with the DFSYMAGT macro.

xx 99 DFSPOOL Failure to release storage for avariable with the DFSYMARL macro.

16 01 DFSYSCP0 Release_Prefix_and_Syn_Blocks -Error releasing the prefix buffer.

16 02 DFSYSCP0 Release_Prefix_and_Syn_Blocks -Error releasing LUMP storage.

16 03 DFSYSCP0 Rel_Sync_AWE_Stg - Error releasingSync AWE storage.

16 04 DFSYSCP0 Delete_Sync_AWE_from_YQAB - NoSync AWE in chain.

16 05 DFSYSCP0 Delete_Sync_AWE_from_YQAB - Errordeleting AWE from the callout chain.

16 06 DFSYSCP0 Process_Request_Data - Errorreleasing LUMP storage.

19 DFSYLUS0 OTMA FAST SERVICES

20 DFSYSTO0 OTMA STORAGE MGR

21 DFSYRR00 OTMA DEST RE-ROUTE SETUPROUTINE

22 DFSYIO00 OTMA INPUT/OUTPUT SETUPROUTINE

23 DFSYCM20 OTMA COMMAND PROCESSOR

24 DFSYDP40 OTMA /DIS TRAN or QUERY TRAN

25 DFSYCLH0 OTMA /TRA SERVICES

26 DFSYRAC0 OTMA SECURITY

27 DFSYMGX0 OTMA XCF MESSAGE EXIT

28 DFSYGRX0 OTMA XCF GROUP EXIT


Table 10. DFS1269E reason codes (continued)


29 DFSYXMO0 OTMA ATTACH MEMBER OIM TCB

30 DFSYC480 OTMA STA/STO(JOIN/LEAVE) XFACE

31 01 DFSYFND0 FIND_LEGACY - Unknown return codefrom DFSFNDST

31 02 DFSYFND0 GET_PRPRIX - DFSPOOL unableobtained a buffer from a specifiedIMS/VS storage pool.

31 03 DFSYFND0 PROCESS_YPRX - OTMAYPRX, An userexit routine has not yet been defined,or unable to get an interface blockfrom BCB.

31 04 DFSYFND0 PROCESS_YDRU - DFSYDRUX, An userexit routine has not yet been defined,or unable to get an interface blockfrom BCB.

31 05 DFSYFND0 BUILD_OUPUT - User prefix length inerror.

32 01 DFSYFD00 Bad input PARM - YDSTTY.

32 02 DFSYFD00 Bad input PARM for TPIPE -YDSTFUNC.

32 03 DFSYFD00 Bad input PARM for YQAB -YDSTFUNC.

32 04 DFSYFD00 BAD INPUT PARM for TTIB -YDSTFUNC.

32 05 DFSYFD00 BUILD_TPIPE - DFSBCB GET failed.

32 06 DFSYFD00 BUILD_TPIPE - TPIPE DFSCIR ITASKfailed.

32 07 DFSYFD00 DELETE_TPIPE - TPIPE DFSCIRDTASK failed.

32 08 DFSYFD00 DELETE_TPIPE - DFSBCB RELEASEfailed.

32 09 DFSYFD00 RELEASE_YTIB - YTIB was not found.

32 10 DFSYFD00 Bad input parameter for RTIB -YDSTFUNC.

32 11 DFSYFD00 FIND_YTIB - YRTIB create failed.

32 12 DFSYFD00 FIND_YTIB - YTIB get storage poolfailed.

32 13 DFSYFD00 DELETE_TPIPE - DFSBCB REL TPIPE'squery anchor block (QAB) failed.

32 14 DFSYFD00 Release_Msceb - Release of userprefix failed.

32 15 DFSYFD00 Release_Msceb - Release of userprefix failed.

32 16 DFSYFD00 Release_Msceb - Release of MSCEBfailed.

32 17 DFSYFD00 Delete_Tpipe - Release of QAB holdqueue ITASK failed.

32 18 DFSYFD00 Delete_Tpipe - Release of hold queueQAB storage failed.



32 19 DFSYFD00 Delete_Tpipe - Release of QAB ITASKfailed.

32 20 DFSYFD00 Find_Tpipe - Release of hold queuefailed.

32 21 DFSYFD00 Find_Tpipe - Release of ITASK failed.

32 22 DFSYFD00 Move_Ytib_Chain - Release of YTIBstorage failed.

32 23 DFSYFD00 Move_Ytib_Chain - Deletion of YTIBITASK failed.

32 25 DFSYFD00 BUILD_YQAB - The YQAB create failed.

32 26 DFSYFD00 Failed to obtain DYNP storage forDFSYPSI0.

32 27 DFSYFD00 Failed to release DYNP storage forDFSYPSI0.

33 DFSYFD10 OTMA CONTROL BLOCK PROCESSOR

34 23 DFSYMOM0 NOTIFY_ONE_MEMBER - DFSBCB getfailed.

34 24 DFSYMOM0 PROCESS_AWES - Invalid AWOFUNCfunction requested.

34 25 DFSYMOM0 CHECK_SECURITY - Invalid security.

34 26 DFSYMOM0 CHECK_SECURITY - RACHECK systemfailed.

34 27 DFSYMOM0 CHECK_SECURITY - RACINIT failed.

34 30 DFSYMOM0 Do_oic_notify - Error on Get Uniquenotify.

34 31 DFSYMOM0 Do_oic_notify - Error on FINDDESTnotify.

34 32 DFSYMOM0 The load failed for the DRU exit.

35 03 DFSYMEM0 Check_Security - Resume TpipeRACINIT failed.

35 04 DFSYMEM0 Check_Security - Resume Tpipe is notauthorized.

35 24 DFSYMEM0 DO_MEM_PHASE3 - OTMA is notready shutdown in phase 3.

35 25 DFSYMEM0 ARE_QAB_READY - All QABs are notready for shutdown.

35 26 DFSYMEM0 ARE_TIBS READY - All TIBs are notready for shutdown.

35 27 DFSYMEM0 PERFORM_ON_TIB - Unable to postthe TIB.

35 28 DFSYMEM0 PERFORM_ON_QAB - Unable to postthe query anchor block (QAB).

35 29 DFSYMEM0 PROCESS_AWES - Invalid AWOFUNCfunction requested.

35 30 DFSYMEM0 FREE_AWE - Unsupported AWE type.

35 31 DFSYMEM0 Activate_Resume_Tpipe - System wasunable to post the query anchor block(QAB).




35 32 DFSYMEM0 DO_MEM_RSM_TPIPE - System wasunable to post the QAB for the supermember.

35 33 DFSYMEM0 OTMA failed to create or find a tpipefor the RESUME TPIPE call. Thisproblem can be caused by:

• The input tpipe name is incorrect sothat OTMA cannot use it to create atpipe.

• OTMA ran out of the storage tocreate the tpipe for the RESUMETPIPE call.

35 34 DFSYMEM0 RelStgBuf - OTMA failed to release thestorage of the response message forthe DL/I ICAL call.

35 35 DFSYMEM0 DO_MEM_RSM_TPIPE - Invalidcommunication line block (CLB)pointer.

35 36 DFSYMEM0 DO_MEM_RSM_MHQUE - Invalidcommunication line block (CLB)pointer.

35 41 DFSYMEM0 Are_TIBs_Ready - Unable to post thetransaction instance block (TIB).

35 42 DFSYMEM0 DO_MEM_RSM_TPIPE - Unable to postthe query anchor block (QAB).

35 43 DFSYMEM0 Are_TIBs_Ready - Unable to post theQAB.

35 44 DFSYMEM0 Do_mem_rep_resync - Unable to postthe QAB.

35 45 DFSYMEM0 Do_mem_rep_resync - Unable to postthe QAB.

35 46 DFSYMEM0 DO_MEM_RSM_TPIPE - Unable to postthe QAB.

35 47 DFSYMEM0 Queue_Resume_Tpipe - Unable topost the QAB.

35 48 DFSYMEM0 Do_Mem_Del_Resume_Tp - Unable topost the QAB.

35 49 DFSYMEM0 OTMA failed to initialize the holdqueue of a super member TPIPE forthe RESUME TPIPE call.

36 DFSYIMI0 OTMA GETTING STORAGE FOR NEWMBR.

37 28 DFSYPSI0 PROCESS_AWE - Unsupported AWEfunction type.

37 29 DFSYPSI0 FREE_AWE - Unsupported AWE type.

37 30 DFSYPSI0 No State Data.

38 DFSYPSOO TPIPE OUTPUT AWE SERV DFSYPSOO

39 DFSYSND0 OTMA XCF INTERFACE

40 01 DFSYTIB0 Normal_Cleanup - Release TIB failed.

40 02 DFSYTIB0 Find_Dest: Unable to find theTranCode destination.



40 03 DFSYTIB0 Check_Security - RACINIT failed.

40 04 DFSYTIB0 Check_Security - RACHECK verifiedTranCode/Command Verb failed.

40 05 DFSYTIB0 Reserved.

40 06 DFSYTIB0 Enqueue - Message Router DFSICLR0enqueued the message to thedestination, but failed.

40 07 DFSYTIB0 Process_Input - Get buffer pool failed.

40 08 DFSYTIB0 Normal_Cleanup - Unable to free thereceive buffer or command buffer ithad been allocated.

40 09 DFSYTIB0 Process_Input - DFSQMGR updatedthe Message Prefix to show thatmessage is unrecoverable and non-restartable, but failed.


40 11 DFSYTIB0 Inser_One_Seqgment - QMGR insertedthe segment, but failed.

40 12 DFSYTIB0 Process_cmd: DFSYCMD0 commandin error.


40 14 DFSYTIB0 Handle_Error - Canceled pendingQMGR, but failed.



40 17 DFSYTIB0 Process_FastPath - Fast Pathtransaction in error.


40 19 DFSYTIB0 Conv_Tran - Not a conversationaltransaction.

40 20 DFSYTIB0 Update_Msg_Prefix - Internal errorin DFSQMGR for Non_Fastpathtransaction.

40 21 DFSYTIB0 Update_Msg_Prefix - Response Moderror in DFSQMGR for Non_Fastpathtransaction.

40 22 DFSYTIB0 Free_Awe - Unsupported AWE type

40 23 DFSYTIB0 Find_Dest - Command invalid from anOTMA client. See DFS1285E.

40 24 DFSYTIB0 Find_Dest - Tran currently notavailable for use. See DFS3470.

40 25 DFSYTIB0 Find_Dest - SMB Tran/Lterm isstopped. See DFS065.

40 26 DFSYTIB0 Find_Dest - Invalid Transaction whichis CPIC. See DFS1286E.

40 27 DFSYTIB0 Find_Dest - Remote Destination(RCNT) invalid. See DFS1287E.

40 28 DFSYTIB0 Find_Dest - Invalid CNT name isspecified. See DFS1288E.




40 29 DFSYTIB0 Find_Dest - The SMB is not found. SeeDFS064.

40 30 DFSYTIB0 Check_Security - Invalid security. SeeDFS1292E.

40 31 DFSYTIB0 Conv_TRAN - System Error Requested.

40 32 DFSYTIB0 Process_FastPath - System ErrorMessage.

40 33 DFSYTIB0 Process_FastPath - User ErrorMessage.

40 34 DFSYTIB0 Insert_One_Segment - SingleSegment Message. See DFS1290E.

40 35 DFSYTIB0 Enqueue - All messages discarded.See DFS249.

40 36 DFSYTIB0 Insert_One_Segment - Sent nullsegment. See DFS249.

40 37 DFSYTIB0 Insert_One_Segment - Queueoverflow as unsuccessful insert.

40 38 DFSYTIB0 Find_Dest - Disallow CM0 forIMS conversational or Fast PathTransaction. See DFS1291E.

40 39 DFSYTIB0 Process_commit - Ending theconversation without an errormessage.

40 40 DFSYTIB0 Find_Dest - DFSMSCE0 TerminalRouting entry point requested toreroute message to a remote system,but failed. See DFS064.

40 41 DFSYTIB0 Find_Dest - DFSMSCE0 TerminalRouting entry point requested toreroute message to a remote system,but failed. See DFS070.

40 42 DFSYTIB0 Check_Seq_Num - Validate therecoverable sequence number forResynch, but failed with Segmentnumber.

40 43 DFSYTIB0 Check_Seq_Num - Validate therecoverable sequence number forResynch, but failed with Nack.

40 48 DFSYTIB0 An invalid message was received fromDFSYPSI0.

40 51 DFSYTIB0 When processing an input messagewithout an AWE control block, aninvalid AWE function code wasspecified.

40 54 DFSYTIB0 The attempt to insert a prefix failed forthe queue manager.

40 58 DFSYTIB0 An invalid APPC/OTMA shared queuesprefix data that was sent from theback-end IMS was detected in thefront-end IMS.

40 60 DFSYTIB0 Go_DFSYIO00 - IMS failed toobtain LUMP storage for calling theOTMAIOED user exit.



40 61 DFSYTIB0 Enqueue - IMS failed to release LUMPstorage.

40 63 DFSYTIB0 Process_Input - Get buffer pool failed.

40 64 DFSYTIB0 Process_Output - Error releasingasynchronous work element (AWE) forshared queues.

40 65 DFSYTIB0 Msg_Back_Queue - Release ofasynchronous work element (AWE)failed.

40 66 DFSYTIB0 Msg_Back_Queue - Conversationaltransaction in error.

40 67 DFSYTIB0 Msg_Back_Queue - Conversationaltransaction in error.

40 68 DFSYTIB0 Msg_Back_Queue - Release ofasynchronous work element (AWE)failed.

40 69 DFSYTIB0 Conv_Tran - Conversationaltransaction in error.

40 71 DFSYTIB0 Conv_Tran - Conversationaltransaction in error.

40 72 DFSYTIB0 Go_DFSYIO00 - IMS failed toobtain LUMP storage for calling theOTMAIOED user exit.

40 74 DFSYTIB0 Go_DFSYIO00 - IMS failed to releaseLUMP storage.

40 75 DFSYTIB0 Normal_Cleanup - IMS failed torelease LUMP storage.

40 76 DFSYTIB0 Setup_Security - IMS failed to obtainLUMP storage for RACF TOKENMAP.

40 77 DFSYTIB0 Setup_Security - IMS failed to releaseLUMP storage.

41 08 DFSYQAB0 Get_First_Segment - DFSQMGR getssegment failure.

41 28 DFSYQAB0 Check_System_Status - Member is notclear to send.

41 29 DFSYQAB0 Edit_N_Send - Segment has beencanceled.

41 30 DFSYQAB0 Move_Segment_Into_Buf - The LLZZof segment length has exceeded themaximum size.

41 50 DFSYQAB0 Check_System_Status - Systemshutdown is in progress.

41 51 DFSYQAB0 Check_System_Status - XCF group hasnot been enabled.

41 52 DFSYQAB0 Check_System_Status - Qab/PipeControl Block has not been stopped.

41 53 DFSYQAB0 Check_Init_Before_Send - Unable t0clear YQAB for work.

41 54 DFSYQAB0 Get_First_Segment - DFSQMGRcannot get the first segment.

41 55 DFSYQAB0 Reserved.




41 56 DFSYQAB0 Get_First_Segment - APPCTransaction has no prefix.

41 57 DFSYQAB0 Get_Storage - DFSPOOL allocatedstorage failure.

41 58 DFSYQAB0 Dispose_Msg - Wash the msg backafter sending.

41 59 DFSYQAB0 Free_Storage - DFSPOOL freed storageusing DFSPOOL failure.

41 60 DFSYQAB0 Check_System_Status - RESYNC flagis on.

41 61 DFSYQAB0 Proc_Sync_Callout_Msg - Sync AWEprocessing error.

41 62 DFSYQAB0 Proc_Sync_Callout_Msg - Sync AWEunknown state.

41 80 DFSYQAB0 Reroute_Msg - Unable to find YQAB formessage hold queue.

41 81 DFSYQAB0 Reroute_Msg - Unable to reroutemessage.

41 82 DFSYQAB0 Reroute_Msg - Bad return code frommessage router CLR1.

42 04 DFSYLUS0 Send_Service - Send out Sync output,but YQAB indicator is on.

42 08 DFSYLUS0 Send_Service - DFSYSLM0 issues XCFsend, but failed.

42 29 DFSYLUS0 Send_Deallocate - DFSYFMTE cannotfind corresponding input member.

42 30 DFSYLUS0 Do_Invalid_Service - Badaddressability or parameter area.

42 31 DFSYLUS0 Chng_Service - DFSYFND0 shouldreturn to DFSDLA30, but it is not.

42 32 DFSYLUS0 Find_QAB - Cannot find a QAB in theOTMA message prefix.

42 33 DFSYLUS0 Find_RTIB - Cannot find an RTIB inthe OTMA message prefix.

42 34 DFSYLUS0 Find_TIB - Cannot find a TIB in theOTMA message prefix.

42 35 DFSYLUS0 GetQabTib_Service - When OTMAreturns to CLB, which should haveYTIB/YQAB address, but DLAMSGINis not pointing to the OTMA messageprefix.

42 36 DFSYLUS0 Copypf_Service - When OTMA copiesa OTMA message prefix, DLAMSGIN ispointing to OTMA message prefix, butcannot find the TIB in the LUMBLK.

42 37 DFSYLUS0 Copypf_Service - When OTMA copiesa OTMA message prefix, DLAMSGIN ispointing to OTMA message prefix, butthe LUMBLK_Ptr is zero.

42 38 DFSYLUS0 Get_OTMA_Prefix - DFSPOOL cannotget storage for OTM prefix.



42 39 DFSYLUS0 TibInfo_Service - When OTMAreturns information in the YTIB, theLUMBLK_Ptr is pointing to the YTIB,but the address of LTERM (DLALTRMA)is zero.

42 40 DFSYLUS0 Inqy_Service - OTMA is not returnedinformation from OTMA Prefix orYQAB/YTIB.

42 43 DFSYLUS0 Sync_Output - Failure to get Sync AWEstorage.

42 45 DFSYLUS0 Sync_Output - Failure to release SyncAWE storage.

42 48 DFSYLUS0 Send_Deal_to_FE - Failure to get SyncAWE storage.

42 49 DFSYLUS0 Send_DFS_Msg_To_FE - Failure to getSync AWE storage.

42 50 DFSYLUS0 Send_DFS_Msg_To_FE - Failure to getSync AWE storage.

42 51 DFSYLUS0 Send_DFS_Msg_To_FE - Failure torelease Sync AWE storage.

43 06 DFSYCMD0 INIT_PRE - Fail to call QMGR insertmove message prefix.

43 23 DFSYCMD0 INIT_PRE - DFSPOOL gets the LUMPpool, but failed.

43 24 DFSYCMD0 INIT_PRE - DFSPOOL releases theLUMP pool, but failed.

44 DFSYCKP0 OTMA CHECK POINT

45 29 DFSYSLM0 Reserved.

45 30 DFSYSLM0 Move_Segment_Into_Buf - The LLZZof segment length is exceeded themaximum size of 32k.

45 57 DFSYSLM0 Get_Storage - DFSPOOL get LUMP, butfailed.

45 59 DFSYSLM0 Free_Storage - DFSPOOL releasesLUMP, but failed.

46 DFSYRST0 OTMA RESTART

46 01 DFSYRST0 Restart_4032 - A tpipe create failedfor the 4032 log record. Restartcontinues without these blocks, butmessages might be lost.

46 02 DFSYRST0 Restart_4032 - HOLDQ create failedfor the 4032 log record. Restartcontinues without these blocks, butmessages might be lost.

46 03 DFSYRST0 Restart_4032 - A YQAB tokenmismatch was found for a 4032log record. Restart continues withoutthese blocks, but messages might belost.




46 04 DFSYRST0 Restart_4032 - A HOLDQ tokenmismatch was found for a 4032log record. Restart continues withoutthese blocks, but messages might belost.

47 01 DFSYIDC0 Obtain storage below the Line forBPAM buffer and input block, but theinterface STORAGE routine failed.

47 02 DFSYIDC0 Get The Receive Buffer (3K), butDFSPOOL GET failed.

47 03 DFSYIDC0 Release The Allocated Buffer,DFSPOOL REL failed.

47 04 DFSYIDC0 Free the storage it has been allocated,but DFSPOOL REL failed.

48 01 DFSYQFX0 Ixctl_To_Yrtib - Create a TIB ITASK byusing the created RTIB, but failed.

48 02 DFSYQFX0 Ixctl_To_Yrtib - Call DFSDST to createa YRTIB, but failed.

48 03 DFSYQFX0 Ixctl_To_Yrtib - After creating RTIBITASK, IXCTL run under YTIB ITASK,but failed.

48 07 DFSYQFX0 Ixctl_From_Yrtib - IXCTL back to thePST, and delete the YRTIB ITASK, butfailed with deleting the YRTIB ITASK.

48 82 DFSYQFX0 If the OTMA was started, the MTOresponse is to issue /STOP OTMA,then issue /START OTMA.

49 OTMAYPRX OTMA Destination Resolution user exit

50 DFSYDRU0 OTMA DEFAULT DRU EXIT DFSYDRU0

51 DFSYJL00 OTMA JOIN/LEAVE-DFSYJL00


Programmer responseContact IBM Software Support and report the reasoncode xxyy and the output found in the OTMAtrace. For more information, see the IBM diagnosticdocumentation.

Module:DFSYIDC0, DFSYMEM0, DFSYTIB0, DFSYRAC0,DFSYFD00, DFSYTIB0, DFSYSND0, DFSYSLM0,DFSYRST0, DFSYRR00, DFSYRAC0, DFSYQFX0,DFSYQAB0, DFSYPSO0, DFSYPSI0, DFSYMOM0,DFSYMEM0, DFSYLUS0, DFSYIO00, DFSYIDC0,DFSYFND0, DFSYCMD0, DFSYCKP0

Related information“DFS064I” on page 46DESTINATION CAN NOT BE FOUND ORCREATED, DEST=destination [I: sss1/name1, D:sss2/name2]

“DFS070” on page 48UNABLE TO ROUTE MESSAGE RSN=xxyy (I:sss1/name1, D: sss2/name2)“DFS249” on page 94NO INPUT MESSAGE CREATED“DFS1285E” on page 434COMMAND INVALID FROM AN OTMA CLIENT“DFS1286E” on page 434DESTINATION NAME=destination IS CPIC ANDNOT ALLOWED FROM AN OTMA MEMBER“DFS1287E” on page 435DESTINATION NAME=destination IS RCNT ANDNOT ALLOWED FROM AN OTMA MEMBER“DFS1288E” on page 435DESTINATION NAME=destination IS CNT ANDNOT ALLOWED FROM AN OTMA MEMBER“DFS1291E” on page 435DESTINATION NAME=destination HAS ANINVALID COMMIT MODE“DFS3470” on page 976TRANSACTION CURRENTLY NOT AVAILABLEFOR USE (I:sss1/name1, D:sss2/name2)

DFS1270I MADS I/O TIMING STRUCTURECONNECT SUCCESSFUL

ExplanationIMS successfully allocated a structure for MADS I/Otiming.



DFS1271E IMPROPER MADS I/O PARAMETERSPECIFIED RSN=rc

ExplanationInvalid MADS I/O timing parameters were detected. Inthe message text, rc is one of the following:

Code (Dec)Meaning

1The length of MADS I/O structure is larger than 16bytes.

2More than 3 byte characters was given for I/Otime.


3An invalid character was detected in the structurename.

4An invalid character was detected in the I/O time.

5More than 256 seconds was written in the I/Otime.

System actionIMS terminates abnormally with user abend 0076.

ModuleDFSTRA00

DFS1271I MADS I/O TIMING STRUCTUREWAS DISCONNECTED. RSN=XX

ExplanationIMS disconnected the list structure for the followingreason:Code (Dec)

Meaning01

Structure failure02

A link error detected

DFS1272I NO ENTRY UNDER IMSID=ccccccccFOUND, LONG BUSY TKO ENDED

ExplanationThe XCF EVENT exit received notification that theIMSID identified by cccccccc terminated. The moduleDBFMLBI0 checked the list structure, but no long busyADS was found.



ModuleDBFMLBI0

DFS1273I USER SPECIFIED DBFMLBX0 ISUSED FOR HASHING MODULE

ExplanationThis message indicates that long busy logic will usethe user hash module, DBFMLBX0.



DFS1277W LUMx POOL STORAGE SHORTAGE.

ExplanationThe LUMP or the LUMC storage pool has less than 5MB of free storage remaining. In the message text, xcan be either P or C.


Programmer response:Specify a larger LUMP or LUMC pool limit at next IMSrestart.

DFS1278E LUMx POOL LIMIT REACHED, ALLAPPC INPUT WILL BE REJECTED.

ExplanationThe LUMP or LUMC storage pool has less than 1 MB offree storage. In the message text, x can be either P orC.

System actionIMS tells APPC/MVS to reject all advanced program-to-program communication (APPC) input until the poolhas more than 5 MB of storage. APPC input that isalready processing can continue.

Programmer response:Check whether there are any stopped resources thatprevent executing transactions. Make sure no clientfloods IMS with transactions. Consider specifying alarger LUMP or LUMC pool limit.

DFS1279I APPC INPUT PROCESSINGRESUMED.

ExplanationThe LUMP or LUMC storage shortage has beenreleased, and new input from advanced program-to-program communication (APPC) is allowed.


System actionIMS tells APPC/MVS to accept all APPC input;processing continues.


If the LUMP or LUMC storage shortage occursagain, follow the response steps in the DFS1278Einformation.

Related information“DFS1278E” on page 432LUMx POOL LIMIT REACHED, ALL APPC INPUTWILL BE REJECTED.

DFS1280E INVALID RESPONSE MESSAGEFROM MEMBER=client

ExplanationAn OTMA client sent an invalid response message toIMS. client is the 16-byte client name.

System actionThe OTMA response message is ignored.

Programmer responseEnsure the OTMA response message is either an ACKor a NACK message.

ModuleDFSYMEM0

DFS1281E (N)ACK ON NON-EXISTINGTPIPE=tpipe FROMMEMBER=member

ExplanationAn OTMA client sent a response message to IMS fora nonexisting transaction pipe. tpipe is the 8-bytetransaction pipe name. member is the 16-byte clientname.


System actionThe OTMA response message is ignored.

Programmer responseEnsure the OTMA transaction pipe associated with theclient is awaiting an OTMA response message.

ModuleDFSYMEM0

DFS1282E UNABLE TO CREATE ORUSE TPIPE=tpipe FORMEMBER=member

ExplanationAn OTMA client requested IMS to use an existing Tpipeor create a new Tpipe. One of two errors occurred:

• IMS was unable to allocate storage to create a newTpipe.

• The Synchronized Tpipe flag in the processing flagof the OTMA message-control-information prefix wasset incorrectly on or off for an existing tpipe.

After a tpipe is created for an input or output OTMAmessage, the Synchronized Tpipe setting for the Tpipecannot be changed for the subsequent input or outputOTMA message.

In the message text:tpipe

Identifies the 8-byte transaction pipe namemember

Identifies the 16-byte client name

System actionIMS responds to the original OTMA message with aNACK message.

Programmer responseEnsure the IMS system has enough availablestorage. Also, check the Synchronized Tpipe flag inthe processing flag of the OTMA message-control-information prefix.

ModuleDFSYMEM0

DFS1283E (N)ACK ON NON-EXISTING BLOCKIN TPIPE=tpipe MEMBER=memberTOKEN=token


ExplanationAn OTMA client sent a response message to IMS for anexisting transaction pipe but the control block did notexist.


The 8-byte transaction pipe name.member

The 16-byte client name.token

The 32 byte server token.


System actionThe message from the OTMA client is ignored. AnX'6701' error record with ID=YPSI or ID=YNAK islogged on IMS OLDS.

Programmer responseEnsure the OTMA transaction pipe associated with theclient is awaiting an OTMA response message and thatthe IMS token in the OTMA message is valid.

Module:DFSYPSI0

DFS1284E (N)ACK ON NON-WAITING BLOCKIN TPIPE=tpipe MEMBER=memberTOKEN=token

ExplanationAn OTMA client sent an acknowledgment message,ACK or NAK, to IMS for a transaction pipe (tpipe) thatis not waiting for the message.


The 8-byte transaction pipe namemember

The 16-byte client nametoken

The 32 byte server token

The client might have specified an incorrect tpipename or IMS OTMA already timed out the wait. Thetpipe might be in a hold state.


System actionThe message from the OTMA client is ignored. AnX'6701' error record with ID=YNAK is logged on theIMS OLDS.

Programmer responseEnsure the OTMA transaction pipe associated with theclient is awaiting an OTMA response message and thatthe IMS token in the OTMA message is valid.

Module:DFSYPSI0

DFS1285E COMMAND INVALID FROM ANOTMA CLIENT

ExplanationThe command cannot be entered from an OTMA client.The command can only be entered from an IMSterminal.

System actionThe IMS command is ignored.

Programmer responseDetermine if the correct command was entered. If so,there can be another IMS, XCF, or VTAM command thatwill give the desired results.

ModuleDFSYTIB0

DFS1286E DESTINATION NAME=destinationIS CPIC AND NOT ALLOWED FROMAN OTMA MEMBER

ExplanationThe specified destination is a CPI Communicationsdriven transaction and cannot be accepted forprocessing from an OTMA client.

System actionIMS sends the OTMA client a NACK message. Theoriginal message is discarded.

Programmer responseEnsure the OTMA client does not issue messages forCPI Communications driven transactions.


ModuleDFSYTIB0

DFS1287E DESTINATION NAME=destinationIS RCNT AND NOT ALLOWEDFROM AN OTMA MEMBER

ExplanationThe specified destination is an RCNT and cannot beaccepted for processing from an OTMA client.


Programmer responseEnsure the OTMA client does not issue messages forRCNT names.

ModuleDFSYTIB0

DFS1288E DESTINATION NAME=destinationIS CNT AND NOT ALLOWED FROMAN OTMA MEMBER

ExplanationThe specified destination is a CNT and cannot beaccepted for processing from an OTMA client.


Programmer responseEnsure the OTMA client does not issue messages forCNT names.

ModuleDFSYTIB0

DFS1290E DESTINATION NAME=destinationIS SINGLE SEGMENT, TPIPE=tpipe

ExplanationThe specified destination can only accept singlesegment messages. Because multiple segments weredetected, the message is discarded. tpipe is the 8-bytetransaction pipe name.

System actionThe OTMA client receives a NACK message.

Programmer responseEnsure the OTMA message has only a single segment.

ModuleDFSYTIB0

DFS1291E DESTINATION NAME=destinationHAS AN INVALID COMMIT MODE

ExplanationThe destination name specified had an invalid commitmode. Usually, the transaction is an IMS Fast Pathtransaction or an IMS conversational transaction andcannot queue messages for an OTMA client using theCommit-then-Send commit mode.


Programmer responseEnsure the OTMA message uses the proper commitmode, usually the Send-then-Commit commit mode.

ModuleDFSYTIB0

DFS1292E SECURITY VIOLATION

ExplanationIMS has rejected an OTMA transaction or commandbecause it failed the security check.


Programmer responseExamine the security data section of the OTMAmessage prefix to ensure a user token, userid or groupname was specified and valid. For example, if a usertoken contains an invalid value such as zero, thismessage will be issued.

ModuleDFSYTIB0


DFS1293E DESTINATION NAME=destinationIS IN DOWN LEVEL IMS

ExplanationThe destination name specified is an IMS remotetransaction name that is not valid. The likely cause isthat the destination IMS subsystem is not capable ofaccepting the OTMA transaction.


Programmer responseEnsure that the destination IMS subsystem is atVersion 5 or higher.

ModuleDFSYLUS0

DFS1294E OTMA OUTPUT SEGMENTSIZE EXCEEDED, MESSAGEDISCARDED, MEMBER=member,TPIPE=tpipe

ExplanationThe message segment length exceeded the limit of32,764 bytes. tpipe is the 8-byte transaction pipename. member is the 16-byte client name.

System actionThe OTMA message is canceled.

Programmer responseCheck the segment size of the OTMA message.

ModuleDFSYSLM0

DFS1295E DESTINATION NAME=destinationIS A REMOTE TRANSACTIONWHICH IS AN INVALIDDESTINATION FOR A PROTECTEDCONVERSATION

ExplanationThe OTMA client or the LU 6.2 device attempted toestablish a protected conversation with a remote IMStransaction.

System actionFor OTMA, the OTMA client receives a NACK message.For LU 6.2, IMS deallocates the conversation withATBCMTP_TP_NOT_AVAIL_NO_RETRY and sends thismessage back to the LU 6.2 device.

Programmer responseEstablish the protected conversation with a local IMStransaction.

ModuleDFSYTIB0, DFSRLM10

DFS1296E DESTINATION NAME=destinationIS NOT A TRANSACTION AND ISAN INVALID DESTINATION FOR APROTECTED CONVERSATION

ExplanationThe OTMA client or the LU 6.2 device attempted toestablish a protected conversation with a destinationthat is not an IMS transaction.

System actionFor OTMA, the OTMA client receives a NACK message.For LU 6.2, IMS deallocates the conversation withATBCMTP_TP_NOT_AVAIL_NO_RETRY and sends thismessage back to the LU 6.2 device.

Programmer responseEstablish the protected conversation with a local IMStransaction.

ModuleDFSYTIB0, DFSRLM10

DFS1297E OTMA TRANSACTIONCOMPLETED. OUTPUTSEGMENT SIZE EXCEEDEDFOR TRANS=trancode,MEMBER=member, TPIPE=tpipe

ExplanationThe OTMA commit-then-send output messagesegment length exceeded the limit of 32K (32,767)bytes. In the message text:member

The 16–byte client nametpipe

The 8–byte transaction pipe name


trancodeThe 8-byte original input transaction name


System actionThe OTMA commit-then-send output message iscanceled. However, any database updates arecommitted.

Programmer responseMake sure the segment size of the OTMA commit-then-send output message does not exceed thelimit of 32,767 bytes. Decrease the segment size ifnecessary.

ModuleDFSYQAB0

DFS1298E DESTINATION NAME=destinationIS A DYNAMIC TRAN ANDNOT ALLOWED FROM AN OTMAMEMBER

ExplanationThe OTMA client attempted to run a dynamictransaction in a shared queues environment. This isnot allowed for OTMA.


Programmer responseEnter the transaction on the IMS system in which it isdefined.

ModuleDFSYTIB0

DFS1299W FPBP64=Y IN DFDFDxxx IS NOTACCEPTED BY DCCTL

ExplanationYou have specified FPBP64=Y in the DFSDFxxxmember of the Data Communications Control (DCCTL).However, DCCTL does not accept FPBP64=Y.

In the message text, xxx is the DFSDF suffix.

System actionDCCTL restarts normally and uses the old FP buffersetup.

Programmer responseCorrect the specification in the DFSDFxxx member.

Module:DBFFATC1

DFS1300I SC=08 INVALID STATEMENT ORSTATEMENT SEQUENCE

ExplanationThis statement type does not occur in the validsequence. The system expected an FMT/FMTEND,MSG/MSGEND, TABLE/TABLEEND, or END operator.


Programmer responseInsert the proper statement, and rerun the job.




DFS1301I SC=04 MISSING END STATEMENT.EOD RECEIVED

ExplanationAn end-of-data (EOD) on SYSIN was assumed, but noEND statement was encountered.

System actionAn END statement is presumed, and end of job (EOJ)processing is done.

Programmer responseEnsure that all the input has been processed.

DFS1302I SC=04 IMPLEMENTATIONRESTRICTION, (parm-name)PARAMETER IGNORED

ExplanationThe parameter NO/REDEF or NO/TEST, included forplanning purposes, were specified; they are ignored.

System actionProcessing continues with next PARM field or SYSINrecord obtained.

Programmer responseDo not specify the following parameters: REDEFINE/TEST.

DFS1303I SC=08 INVALID STATEMENTLABEL/OPERATOR STARTSEQUENCE

ExplanationThe source item received does not conform to LABEL/OPERATOR syntax requirements. One or the other isrequired.

System actionProcessing continues with the next item on the inputstatement.

Programmer responseAfter examining the erroneous source, correct theerror, and resubmit the job.

DFS1304I SC=08 OPERATOR TOO LONG.STATEMENT SKIPPED

ExplanationThe order of occurrence requires LABEL/OPERATOR.However, the source item is greater than eightcharacters and does not qualify as either.


Programmer responseAfter examining the erroneous source, correct theerror, and resubmit the job.

DFS1305I SC=08 INVALID CHARACTERDELETED

ExplanationA character other than alphanumeric, national,arithmetic operator, or punctuation was detected.

System actionProcessing resumes with the next character in theinput buffer.

Programmer responseAfter examining the erroneous source, specify theinput again, and resubmit the job.

DFS1306I SC=08 END OF STATEMENTDURING STRING COLLECTIONPROCESSING

ExplanationAn end-of-statement condition was detected whilepreparing a collection of characters for the get itemprocessor.



Programmer responseAfter examining the erroneous source, specify theinput again, and resubmit the job.

DFS1307I SC=08 END OF FILEDURING STRING COLLECTIONPROCESSING

ExplanationAn end-of-file condition was detected while preparinga collection of characters for the get item processor.

System actionProcessing continues with the appropriate end-of-data(EOD) routines.

Programmer responseCorrect the erroneous source or re-create theoffending SYSLIB source, and rerun the job.

DFS1308I SC=08 ALPHANUMERIC ITEMOVERFLOW ON SCAN

ExplanationAn alphanumeric item exceeded 255 bytes in length.

System actionProcessing continues with the next source item.

Programmer responseAfter examining the erroneous source, specify the itemagain, and resubmit the job.

DFS1309I SC=08 NUMERIC ITEM OVERFLOWON SCAN

ExplanationA numeric item exceeded 255 bytes in length.

System actionProcessing continues with the next source character.


DFS1310I SC=08 alphanumeric ITEMOVERFLOW ON SCAN

ExplanationAn alphanumeric item exceeded 255 bytes in length.



DFS1311I SC=08 STRING ITEM OVERFLOWON SCAN

ExplanationA character string exceeded 255 bytes in length.


Programmer responseAfter examining the erroneous source, specify thestring again, and resubmit the job.

DFS1312I SC=08 INVALID LABEL STARTCHARACTER. $ SUBSTITUTED

ExplanationA LABEL began with other than an alphabetic ornational character.


Programmer responseSpecify the label again using alpha/national initialcharacters, and resubmit the job.

DFS1313I SC=08 INVALID CHARACTER INLABEL. $ SUBSTITUTED

ExplanationA LABEL contained other than an alphanumeric ornational character.



Programmer responseAfter removing or correcting the offending character,resubmit the job.

DFS1314I SC=08 INVALID OPERATOR STARTCHARACTER. $ SUBSTITUTED

ExplanationThe order of occurrence required OPERATOR, and thecurrent item had a non-alphabetic first character.


Programmer responsePreprocessor OPERATORS are all alphabetic characterstrings; specify the operator again, and rerun the job.

DFS1315I SC=08 INVALID OPERATORCHARACTER. $ SUBSTITUTED

ExplanationThe order of occurrence requires an OPERATOR, andthe current item contains a non-alpha character.


Programmer responsePreprocessor OPERATORS are all alphabetic characterstrings; specify the operator again, and rerun the job.

DFS1316I SC=08 INVALID OPERAND STARTCHARACTER. $ SUBSTITUTED

ExplanationAn OPERAND begins with other than a quotation markor alphabetic character.


Programmer responseSpecify the OPERAND in error again and rerun the job.

DFS1317I SC=08 INVALID CHARACTER INOPERAND. $ SUBSTITUTED

ExplanationAn OPERAND contained an invalid character.


Programmer responseSpecify the operand in error again and rerun the job.

DFS1318I SC=08 COLS 1-15 NOT BLANK ONCONTINUATION

ExplanationA continuation statement is not blank in columns 1through 15.

System actionProcessing continues with the next non-continuationstatement.

Programmer responseCorrect the erroneous continuation statement, leavingcolumns 1 through 15 blank, and resubmit the job.

DFS1319I SC=08 EXPECTED CONTINUATIONNOT RECEIVED

ExplanationThe previous source statement indicatedcontinuations on a subsequent statement; however, nocontinuation statement followed.

System actionProcessing continues as if no continuation wasspecified.

Programmer responseSupply the continuation statements or remove thecontinuation indicator, and rerun the job.

DFS1320I SC=08 COLUMN 16 BLANK ONCONTINUATION

ExplanationContinuation statements must begin in column 16.


System actionProcessing continues as if this statement werecomments.

Programmer responseSpecify the first character of the continuation data incolumn 16 again and rerun the job.

DFS1321I SC=04 INVALID CHARACTER X'hh'IN STRING

ExplanationAn invalid character has been detected in the literalstring. X'hh' is the hexadecimal representation of theinvalid character.

System actionProcessing continues with the next source character.The character is included in the generated literal—depending on the device and the character, it canadversely affect formatting.

Programmer responseVerify that the literal contains the correct content. Forsome characters, the ALPHA statement can be usedto eliminate this message. Omit or change the invalidcharacter, and rerun the job.

DFS1322I SC=08 EXCESSIVE LABEL LENGTH

ExplanationLABEL can never exceed 8 characters in length.

System actionTruncation occurs and processing continues with thenext source character.

Programmer responseShorten the LABEL specified to eight or fewercharacters, and rerun the job.

DFS1323I SC=08 NO OPERATOR FOUND

ExplanationThe order of occurrence of the operands requires thatOPERATOR occur next, but it was not found.


Programmer responseSpecify the input again; include a valid OPERATOR andrerun the job.

DFS1324I SC=08 CONTINUED OPERATORINVALID SYNTAX

ExplanationOPERATORs must be contiguous and on a singlestatement.


Programmer responseSpecify the input again according to continuationrequirements, and rerun the job.

DFS1325I SC=08 MISSING OPERAND.CONTINUED COMMENTSASSUMED

ExplanationAn OPERAND is missing.


Programmer responseProvide the missing operand, and rerun the job.

DFS1326I SC=04 EXCESSIVE LABELLENGTH. FIRST 8 CHARACTERSUSED

ExplanationLABELs can not exceed 8 characters in length.


Programmer responseShorten the LABEL specified to 8 or fewer characters,and rerun the job.

DFS1327I SC=08 NO OPERATOR FOUND


ExplanationNo OPERATOR was found on this statement. AnOPERATOR is required.


Programmer responseSpecify the OPERATOR you want, and rerun the job.

DFS1328I SC=08 EXPECTED STRINGCONTINUATION NOT RECEIVED

ExplanationContinuation of a literal string was indicated, but notfound.


Programmer responseSpecify the input again according to continuationrequirements, and rerun the job.

DFS1329I SC=04 END OF FILE DETECTEDWHERE CONTINUATION CARDWAS EXPECTED

ExplanationAn end-of-file condition has been sensed, when acontinuation statement was expected.

System actionProcessing continues with the appropriate EODroutines.

Programmer responseCorrect the erroneous source or re-create theoffending SYSLIB source, and rerun the job.

DFS1330I SC=20 I/O ERROR. INPUTPROCESSING TERMINATED

ExplanationAn I/O error on SYSIN or SYSLIB occurred. Thismessage is preceded by a z/OS message indicating thespecific type of error.

System actionThe preprocessor terminates with a forced end of job(EOJ).

Programmer responseDetermine the cause of the I/O error, correct it, andrerun the job.

DFS1331I SC=08 TEXT SUBSTITUTIONBUFFER FULL, TEXT LOST

ExplanationThe text substitution buffer size (4096 bytes) has beenexceeded; no further entries can be made.

System actionThe current text is not stacked; processing continueswith the next source statement.

Programmer responseRemove the unnecessary or lengthy equates (EQU),and rerun the job.

DFS1332I SC=04 POSITION MARKER

ExplanationThe position marker indicates the current sourcepointer at the time of error.

System actionProcessing continues with further error analysis.

Programmer responseSee message DFS1334I.

Related information“DFS1334I” on page 444SC=04 EXPECTED: any operand(s)

DFS1333I SC=04 REC'D: 'any operand'

Explanation"any operand" is the offending OPERAND.




Related information“DFS1334I” on page 444SC=04 EXPECTED: any operand(s)

DFS1334I SC=04 EXPECTED: any operand(s)

ExplanationThe operands valid for this keyword are listed.


Programmer responseSelect one or more of the valid options listed, specifythe selected options, and rerun the job.

DFS1335I SC=08 REC'D ITEM DELETED

ExplanationThe item indicated by message DFS1333I has beendeleted and no assumption will be made.

System actionProcessing continues with the next operand.

Programmer responseSpecify the proper OPERAND again and rerun the job.

DFS1336I SC=08 ITEM PREVIOUS TO REC'DITEM DELETED

ExplanationAn error condition exists that requires thepreprocessor to delete the previous item to resolve theconflict.

System actionProcessing continues with next operand.

Programmer responseSpecify the proper OPERAND again and rerun the job.

DFS1337I SC=04 FOLLOWING ASSUMED: anyoperand

ExplanationThe preprocessor has assumed the operand specifiedin any operand, which is valid.


Programmer responseSee message DFS1334I if the assumption made is notdesired.

Related informationDFS1334ISC=04 EXPECTED: any operand(s)

DFS1338I SC=08 NULL OPERAND RECEIVEDFOR ALPHA STATEMENT

ExplanationNo OPERAND has been provided on an ALPHAstatement.


Programmer responseAdd the desired operand, and rerun the job.

DFS1339I SC=08 INVALID CHARACTER INALPHA STRING IGNORED

ExplanationYou have attempted to use as alphabetic a characterreserved for a number or a delimiter.

System actionThe character is ignored and processing continueswith the next alphabetic string character.

Programmer responseIf the intended collating sequence is correct, none isrequired; if it is not, specify it again, and rerun the job.

DFS1340I SC=04 EQUATE LENGTHTRUNCATED TO 256 MAX

ExplanationA single EQU character string exceeded 256 bytes, andwas truncated.



Programmer responseBreak up the equate string into smaller logicalcomponents, and rerun the job.

DFS1341I SC=08 NO LABEL PROVIDED FOREQUATE PROCESSOR

ExplanationAn EQU has been encountered with no label, andconsequently cannot be referenced.


Programmer responseProvide a label, and rerun the job.

DFS1342I SC=08 LABEL IS TOO LONG FOREQUATE

ExplanationLABELs can be no more than 8 bytes in length.


Programmer responseAlter the LABEL and references to 8 characters or less,and rerun the job.

DFS1343I SC=08 NO RIGHT PART VALUEPROVIDED FOR EQUATE

ExplanationYou did not provide an equate string.


Programmer responseProvide a value to be equated to the LABEL, and rerunthe job.

DFS1344I SC=04 TITLE LENGTH EXCEEDSnnn CHARACTERS. FIRST kkkUSED

ExplanationThe TITLE literal exceeded the maximum number ofcharacters nnn, and was truncated to the first kkkcharacters.


Programmer responseSpecify the literal again and resubmit the job.

DFS1345I SC=04 NULL TITLE OPERAND.PREVIOUS TITLE REMAINS INEFFECT

ExplanationNo TITLE literal was provided; the statement wasignored.


Programmer responseProvide a literal for the TITLE, and resubmit the job.

DFS1346I SC=08 LPAGE SEQUENCE ERROR.NO 1ST LPAGE

ExplanationThe first LPAGE in an MSG containing more than oneLPAGE must be specified.


Programmer responseAdd an LPAGE statement to the source, and rerun thejob.

DFS1347I SC=04 MSGEND STATEMENTASSUMED

ExplanationThe statement order of occurrence requires anMSGEND statement. None was found; one is assumed.



Programmer responseInsert the MSGEND statement, and rerun the job.

DFS1348I SC=04 SEG STATEMENT ASSUMED

ExplanationThe statement order of occurrence requires the SEGstatement. None was found; one is assumed.


Programmer responseSupply the SEG statement, and rerun the job.

DFS1349I SC=08 MFLD STATEMENTASSUMED

ExplanationThe statement order of occurrence requires an MFLDstatement. None was found; one is assumed.


Programmer responseInsert the MFLD statement, and rerun the job.

DFS1350I SC=08 'nnnn' IS AN INVALIDMESSAGE NUMBER

ExplanationA message number was presented to the messageprocessor (DFSUPAK0), but the message number wasnot found in the message table (DFSUPAL0).








DFS1351I SC=08 MAXIMUM RESCANSUBSTITUTION COUNTEXCEEDED. SUBSTITUTION NOTPERFORMED

ExplanationA statement exceeded the maximum RESCANsubstitution count. The RESCAN default is 5 to avoidlooping.

System actionThe substitution is terminated. Processing resumeswith the next statement.

Programmer responseSpecify a larger number on the RESCAN statement forthe result you want.

DFS1352I SC=08 SCAN ABORTED DUETO SEVERE SYNTAX ERROR,CONTINUING WITH NEXTSTATEMENT

ExplanationThe current statement errors were not resolved; thestatement was discarded.


Programmer responseCorrect the erroneous operands using the supportingmessage numbers DFS1332I through DFS1337I, andrerun the job.

DFS1353I SC=04 RESCAN COUNT EXCEEDS5 SIGNIFICANT DIGITS. DEFAULTCOUNT OF 5 USED

ExplanationNo more than 5 significant digits are acceptable as theRESCAN count; it was set to 5.


Programmer responseCorrect the RESCAN specification; do not exceed 5significant digits. Rerun the job.

DFS1354I SC=04 RESCAN COUNT EXCEEDS32767. COUNT SET TO 32767

ExplanationThe RESCAN count exceeded 32767; it was set to thedefault 32767.


Programmer responseCorrect the RESCAN specification number, and rerunthe job.

DFS1355I SC=04 NUMBER FOR SPACEEXCEEDS 15 SIGNIFICANTDIGITS. THE PAGE WILL BEEJECTED

ExplanationThe SPACE count exceeded 15 significant digits. Apage eject occurred.


Programmer responseSpecify the SPACE count again; do not exceed 15significant digits. Rerun the job.

DFS1356I SC=12 FMTNAME AS LABELREQUIRED. FMT USED

ExplanationA LABEL is required on each FMT statement; thisformat is labeled FMT.



Programmer responseSpecify FMT with the appropriate label again and rerunthe job.

DFS1357I SC=08 FMTNAME EXCEEDS 6CHARACTERS. FIRST 6 USED

ExplanationFormat names cannot exceed 6 characters in length.The name was truncated to the first 6 characters.


Programmer responseSpecify the appropriate format name again and rerunthe job.

DFS1358I SC=08 DEV STATEMENT ASSUMED

ExplanationNo DEV statement followed an FMT statement; onehas been assumed.


Programmer responseInsert the appropriate DEV, and rerun the job.

DFS1359I SC=04 FMTEND STATEMENTASSUMED

ExplanationA format block should end with an FMTEND statement.None has been found; one has been assumed.


Programmer responseSupply an FMTEND statement, and resubmit the job.

DFS1360I SC=04 DIV STATEMENT ASSUMED

ExplanationA DEV statement was not immediately followed bya DIV statement. One has been assumed as follows:3270=INOUT, 3600=INPUT, ALL OTHERS=OUTPUT.


Programmer responseFor the results you want or for documentationpurposes, specify the DIV statement, and rerun thejob.

DFS1361I SC=08 DPAGE SEQUENCE ERROR.NO 1ST DPAGE

ExplanationYou must specify the first DPAGE in an FMT containingmore than one DPAGE.


Programmer responseAdd DPAGE statement to the source input, and rerunthe job.

DFS1362I SC=08 DFLD STATEMENTASSUMED

ExplanationThe statement order of occurrence requires a DFLDstatement as input. None was found; one wasassumed.


Programmer responseProvide the appropriate DFLD statement, and rerun thejob.

DFS1363I SC=08 POS=(lll,ccc,ppp)REQUIRED FOR RECORD MODE

ExplanationThe stream mode form of the DFLD POS=keyword was given when MODE=RECORD; the formPOS=(lll,ccc,ppp) is required. The default record mode


POS= keyword is used (line=1, column=left margin +1,page=1).


Programmer responseSpecify the MODE= keyword of the DEV statement orthe POS= keyword of the DFLD statement again andrerun the job.

DFS1364I SC=04 ENDDO STATEMENTASSUMED

ExplanationThe statement order of occurrence requires an ENDDOstatement. None was found; one was assumed.


Programmer responseProvide an ENDDO statement, and rerun the job.

DFS1365I SC=08 DFLD POS= KEYWORDDOES NOT ALLOW SPACE FORSIMULATED ATTRIBUTE

ExplanationThe POS= keyword specifies line 1 and the columnposition as the left margin. There was no available bytepreceding the field for the attribute byte. ATTR=YESwas therefore ignored.


Programmer responseSpecify the POS= keyword or the ATTR= keyword ofthe DFLD statement again and rerun the job.

DFS1366I SC=08 PS VALUE INVALID, X'00'USED

ExplanationThe value specified for PS was not a single character or2 hexadecimal characters, or was not in the range fromX'40' to X'FE'.

System actionThe default value of X'00' was used and processingcontinues with this operand.

Programmer responseSpecify the PS value as either a single character or2 hexadecimal characters in the range from X'40' toX'FE', or as PX'00'. Rerun the job.

DFS1367I SC=08 TABLENAME AS LABELREQUIRED. 'TEMPTABL USED'

ExplanationEach TABLE statement requires a label. None wasfound; it was assigned a label.


Programmer responseProvide the required label, and rerun the job.

DFS1368I SC=04 TABLENAME TRUNCATEDTO 8 CHARACTERS

ExplanationThe TABLE statement label exceeded 8 characters; thefirst 8 characters were used.


Programmer responseSpecify the appropriate label again and rerun the job.

DFS1369I SC=08 IF STATEMENT ASSUMEDAS: 'NOFUNC'

ExplanationAt least one IF statement is required for a TABLE; onewas assumed.


Programmer responseSpecify the appropriate statements or remove theTABLE, and rerun the job.


DFS1370I SC=04 TABLEEND STATEMENTASSUMED

ExplanationThe statement order of occurrence requires aTABLEEND. None was found; one was assumed.


Programmer responseInsert the TABLEEND statement as required, and rerunthe job.

DFS1371I SC=08 MSG NAME AS LABELREQUIRED

ExplanationEach MSG statement should be labeled. Nonewas found; one was generated. The form is MSGconcatenated to source statement number.


Programmer responseSpecify the appropriate label, and rerun the job.

DFS1372I SC=04 MSG NAME TOO LONG.TRUNCATED TO 8 BYTES

ExplanationAn MSG statement label exceeded 8 bytes; the first 8bytes were used.


Programmer responseSpecify the label again and rerun the job.

DFS1373I SC=08 SOR=FMTNAME, FMTNAMEMISSING

ExplanationThe SOR= specification was null; no format name wasused.


Programmer responseSpecify the appropriate format name, and rerun thejob.

DFS1374I SC=04 SOR=FMTNAME, FMTNAMEEXCEEDS 6 CHARACTERS. FIRST 6USED

ExplanationThe SOR= formatname exceeded 6 characters; thefirst 6 characters were used.


Programmer responseSpecify the format name again and rerun the job.

DFS1375I SC=08 NXT=MSGNAME,MSGNAME LTH=0. NONE USED

ExplanationThe NXT= specification was null; no message namewas used.


Programmer responseSpecify the appropriate message name, and rerun thejob.

DFS1376I SC=04 NXT=MSGNAME, MSGNAMEEXCEEDS 8 BYTES. TRUNCATEDTO 8 BYTES

ExplanationThe NXT= message name exceeded 8 bytes; the first 8bytes were used.


Programmer responseSpecify the appropriate message name again andrerun the job.


DFS1377I SC=04 FILL=C'.', TRUNCATED TO 1CHARACTER

ExplanationThe FILL= literal exceeded one character in length; thefirst character was used.


Programmer responseSpecify the literal again and rerun the job.

DFS1378I SC=04 FILL=C'.' CHARACTER NOTSUPPLIED

ExplanationThe FILL= specification was null; it was set to a blank.


Programmer responseSpecify the appropriate fill character again and rerunthe job.

DFS1379I SC=04 DUPLICATE TYPE=KEYWORDS INVALID

ExplanationOnly one TYPE= specification is allowable on a singleMSG statement; the second one was ignored.


Programmer responseResolve the multiple TYPE= specification, and rerunthe job.

DFS1380I SC=04 DUPLICATE SOR=KEYWORDS INVALID

ExplanationOnly one SOR= specification is allowed on a singleMSG statement; the second one was ignored.


Programmer responseResolve the multiple SOR= specifications, and rerunthe job.

DFS1381I SC=04 DUPLICATE OPT=KEYWORDS INVALID

ExplanationOnly one OPT= specification is allowable on a singleMSG statement; the second one was ignored.


Programmer responseResolve the multiple OPT= specifications, and rerunthe job.

DFS1382I SC=04 DUPLICATE NXT=KEYWORDS INVALID

ExplanationOnly one NXT= specification is allowable on a singleMSG statement; the second one was ignored.


Programmer responseResolve the multiple NXT= specifications, and rerunthe job.

DFS1383I SC=04 DUPLICATE PAGE=KEYWORDS INVALID

ExplanationOnly one PAGE= specification is allowable on a singleMSG statement; the second one was ignored.


Programmer responseResolve the multiple PAGE= specifications, and rerunthe job.


DFS1384I SC=04 DUPLICATE FILL=KEYWORDS INVALID

ExplanationOnly one FILL= specification is allowable in a singleMSG statement; the second one was ignored.


Programmer responseResolve the multiple FILL= specifications, and rerunthe job.

DFS1385I SC=04 SOR=FMTNAME NOTSPECIFIED. '$$$FMT' USED

ExplanationThe SOR= specification was not specified for this MSG;$$$FMT was used as format name.


Programmer responseSpecify the format name you want, and rerun the job.

DFS1386I SC=08 FILL= SPECIFICATIONINVALID FOR TYPE=INPUT

ExplanationThe FILL= specification was specified on an MSGstatement of TYPE=INPUT. However, it is only valid onMSG and DPAGE statements of TYPE=OUTPUT.


Programmer responseResolve the conflict, and rerun the job.

DFS1387I SC=08 PAGE= SPECIFICATIONINVALID FOR TYPE=INPUT

ExplanationThe PAGE= specification was specified on an MSGstatement of TYPE=INPUT. However, it is only valid onMSG statements of TYPE=OUTPUT.



DFS1388I SC=04 DUPLICATE SOR=SPECIFICATION INVALID

ExplanationOnly one SOR= specification is allowable in a singleLPAGE statement; the second one was ignored.


Programmer responseSpecify the SOR= specification again and rerun the job.

DFS1389I SC=08 SOR=DPAGENAME,DPAGENAME OMITTED

ExplanationThe SOR= specification is null; it was ignored.


Programmer responseSpecify a value for SOR=, and rerun the job.

DFS1390I SC=04 SOR=DPAGENAME,DPAGENAME EXCEEDS 8CHARACTERS. TRUNCATED TO 8CHARACTERS

ExplanationThe SOR= dpagename exceeds 8 characters; the first 8characters are used.


Programmer responseSpecify the desired dpagename again and rerun thejob.


DFS1391I SC=04 COMPARE OFFSETEXCEEDS 5 SIGNIFICANT DIGITS,LAST 5 DIGITS USED

ExplanationThe COND= offset parameter exceeds 5 digits; the last5 digits are used.


Programmer responseSpecify the desired offset again and rerun the job.

DFS1392I SC=04 COMPARE OFFSETEXCEEDS 32767. VALUE ALTEREDTO 32767

ExplanationThe COND= offset parameter value exceeds 32767; itis set to 32767.


Programmer responseSpecify the desired value again and rerun the job.

DFS1393I SC=08 COMPARE OFFSET DIGITCOUNT IS ZERO. VALUE OF ZEROUSED

ExplanationThe COND= offset parameter is null; it is set to zero.


Programmer responseSpecify the desired offset value, and rerun the job.

DFS1394I SC=04 MULTIPLE COND=KEYWORDS INVALID

ExplanationOnly one COND= specification is allowable on a singleLPAGE or DPAGE statement; the second specificationis ignored.



DFS1395I SC=04 COND= COMPARELOCATION NAME LENGTHEXCEEDS 8 CHARACTERS.TRUNCATED TO 8 CHARACTERS

ExplanationThe COND= fieldname exceeds 8 characters; the first 8characters are used.


Programmer responseSpecify the desired fieldname again and rerun the job.

DFS1396I SC=08 COND= COMPARELOCATION NAME LENGTH ISZERO. NAME SPECIFICATIONIGNORED

ExplanationThe COND= fieldname parameter is null; it is ignored.


Programmer responseSpecify the desired fieldname, and rerun the job.

DFS1397I SC=08 EXIT= SPECIFICATIONINVALID WITH 'LITERAL'PARAMETER. SPECIFICATIONIGNORED.

ExplanationThe EXIT= is not allowed when the LITERAL parameteris specified. EXIT= is ignored.




DFS1398 INPUT SELECTION ERROR

ExplanationThis message is displayed if you do not correctly enterone of the following analysis input selections:

• MAX=• KR=• NBR=

System actionThe system exits the utility.

User responseEnter the correct analysis option.

ModuleDFSMAID0

DFS1399I SC=08 COND= COMPARE. LITERALLENGTH IS ZERO. ' ' USED FORLITERAL

ExplanationThe literal in the COND= specification of the LPAGEstatement was omitted. A single blank is used as theliteral.


Programmer responseSpecify the desired literal, and rerun the job.

DFS1400I SC=04 PROMPT= FIELDNAMEEXCEEDS 8 CHARACTERS.TRUNCATED TO 8 CHARACTERS

ExplanationThe PROMPT= fieldname exceeds 8 characters; thefirst 8 characters are used.


Programmer responseSpecify a valid fieldname again and rerun the job.




DFS1401I SC=08 PROMPT= FIELDNAMELENGTH IS ZERO. SPECIFICATIONIGNORED

ExplanationThe PROMPT= specification was null; it was ignored.


Programmer responseSpecify a valid PROMPT= fieldname statement, andrerun the job.

DFS1402I SC=04 DUPLICATE PROMPT=KEYWORDS INVALID

ExplanationOnly one PROMPT= specification is valid on a singleLPAGE statement; the second one was ignored.



DFS1403I SC=04 PROMPT= LITERALSPECIFICATION CONTAINS NOTEXT. MSG.NXT=MSGNAME USED

ExplanationThe PROMPT= literal was null; the MSG/NXT=specification was used.


Programmer responseSpecify a valid literal, and rerun the job.

DFS1404I SC=04 NXT= MSGNAME EXCEEDS8 CHARACTERS. TRUNCATED TO 8CHARACTERS

ExplanationThe NXT= message name exceeded eight characters;the first eight characters were used.


Programmer responseSpecify a valid message name, and rerun the job.

DFS1405I SC=04 NXT= MSGNAMETEXT LENGTH IS ZERO.MSG.NEXT=MSGNAME USED

ExplanationThe NXT= specification was null; the MSG/NXT=message name was used.


Programmer responseSpecify a valid message name, and rerun the job.

DFS1406I SC=04 DUPLICATE NXT=KEYWORDS INVALID

ExplanationOnly one NXT= specification is valid on a single LPAGEstatement; the second one was ignored.



DFS1407 TEMPORARY IRLM FAILURE;UNABLE TO PROCESS GLOBALCOMMAND


ExplanationThe command processor, in an attempt to process aglobal command, encountered a problem with IRLM.This condition can be temporary.

System actionThe command is processed locally.

Programmer responseEnsure that the IRLM is active and then reenter theglobal command. If the command will not processglobally, proceed with the problem determination.



DFS1408I SC=08 EXIT= SPECIFICATIONINCOMPATIBLE WITHMSG.TYPE=OUTPUT

ExplanationThe EXIT= specification conflicts with message typeoutput; it was ignored.


Programmer responseResolve the SEG/MSG statement conflict, and rerunthe job.

DFS1409I SC=08 EXIT= EXITNUM EXCEEDS3 SIGNIFICANT DIGITS. LAST 3DIGITS USED

ExplanationThe EXIT= value parameter Exceeded 3 digits; the last3 digits were used.


Programmer responseSpecify a valid value, and rerun the job.

DFS1410I SC=08 EXIT= EXITNUM VALUEEXCEEDS 127. 127 USED

ExplanationThe EXIT= value parameter exceeds 127. The valuewas set to 127.


Programmer responseSpecify EXIT= with a valid value, and rerun the job.

DFS1411I SC=08 EXIT= EXITVECT EXCEEDS3 SIGNIFICANT DIGITS. LAST 3DIGITS USED

ExplanationThe EXIT= vector specification exceeds 3 digits; thelast 3 digits are used.


Programmer responseSpecify EXIT= vector with a valid value, and rerun thejob.

DFS1412I SC=08 EXIT= EXITVECT VALUEEXCEEDS 255. 255 USED

ExplanationThe EXIT= vector specification exceeds 255, The valuewas set to 255.


Programmer responseSpecify the EXIT= parameter with a valid value, andrerun the job.

DFS1413I SC=08 EXIT= EXITNUM HAS NODIGITS. VALUE OF ZERO USED

ExplanationThe EXIT= value specification is null. The value wasset to zero.



Programmer responseSpecify EXIT= with the appropriate value, and rerunthe job.

DFS1414I SC=08 EXIT= EXITVECT HAS NODIGITS. VALUE OF ZERO USED

ExplanationThe EXIT= vector specification is null. It was set tozero.


Programmer responseSpecify EXIT= with the appropriate vector, and rerunthe job.

DFS1415I SC=04 DUPLICATE EXIT=KEYWORDS INVALID

ExplanationYou can specify only one EXIT= specification on asingle SEG statement; the second one was ignored.



DFS1416I SC=04 DUPLICATE GRAPHIC=KEYWORDS INVALID

ExplanationOnly one GRAPHIC= specification is allowable on asingle SEG statement. The second one is ignored.



DFS1417I SC=04 MFLD LABEL LENGTHEXCEEDS 8 CHARACTERS.TRUNCATED TO 8 CHARACTERS

ExplanationThe message field (MFLD) statement label exceeds 8characters. The first 8 characters are used.


Programmer responseSpecify a valid label again and rerun the job.

DFS1418I SC=08 DO COUNT EXCEEDS 2SIGNIFICANT DIGITS. LAST 2DIGITS USED

ExplanationThe DO count exceeds 2 digits; the last 2 digits areused.


Programmer responseSpecify DO again using an appropriate count, andrerun the job.

DFS1419I SC=08 DO COUNT HAS NO DIGITS.VALUE OF 1 ASSUMED

ExplanationYou did not provide a count on a DO statement. One isassumed.


Programmer responseSpecify DO again using an appropriate count, andrerun the job.

DFS1420I SC=04 DFLDNAME EXCEEDS 8CHARACTERS. TRUNCATED TO 8CHARACTERS


ExplanationThe device field name (dfldname) specified on thisMFLD statement exceeded 8 characters; the first 8characters were used.


Programmer responseSpecify a valid dfldname again and rerun the job.

DFS1421I SC=08 DFLDNAME HAS NOCHARACTERS. NO NAME USED

ExplanationThe device field name (dfldname) parameter was null;it was ignored.


Programmer responseSpecify valid MFLD parameters, and rerun the job.

DFS1422I SC=04 LITERAL CONTAINS NOCHARACTERS. ' ' USED

ExplanationThe positional literal parameter is null for this MFLD orDFLD statement; a blank is assumed.


Programmer responseSpecify a valid literal or MFLD/DFLD parameter, andrerun the job.

DFS1423I SC=04 MULTIPLE LTH=KEYWORDS INVALID

ExplanationThe system encountered multiple LTH-specifications .Only one LTH= specification isallowable on a single MFLD statement. The second onewas ignored.


Programmer responseSelect one specification, and rerun the job.

DFS1424I SC=04 MULTIPLE JUST=KEYWORDS INVALID

ExplanationThe system encountered multiple JUST=specifications. Only one JUST= specification isallowable on a single MFLD statement. The second onewas ignored.



DFS1425I SC=04 MULTIPLE FILL=KEYWORDS INVALID

ExplanationThe system encountered multiple FILL= specifications.Only one FILL= specification is allowable on a singleMFLD or DPAGE statement. The second specificationwas ignored.



DFS1426I SC=04 MULTIPLE ATTR=KEYWORDS INVALID

ExplanationThe system encountered multiple ATTR=specifications. Only one ATTR= specification isallowable on a single MFLD statement. The second onewas ignored.



DFS1427I SC=04 MULTIPLE EXIT=KEYWORDS INVALID


ExplanationThe system encountered multiple EXIT=specifications. Only one EXIT= specification isallowable on a single MFLD statement, The second onewas ignored.



DFS1428I SC=08 LTH=nn, nn EXCEEDS 4SIGNIFICANT DIGITS. LAST 4DIGITS USED

ExplanationThe LTH= length parameter exceeded 4 digits; the last4 digits was used.


Programmer responseSpecify a valid value again and rerun the job.

DFS1429I SC=08 LTH=nn, nn'S VALUEEXCEEDS 8000. 8000 USED

ExplanationThe LTH= length value exceeded 8000; it was set to8000.


Programmer responseSpecify a valid value, and rerun the job.

DFS1430I SC=08 LTH=nn, nn HAS NODIGITS. VALUE OF 1 USED

ExplanationThe LTH= length specification was null; it was set to 1.


Programmer responseSpecify the length, and rerun the job.

DFS1431I SC=08 LTH=(pp,nn), pp EXCEEDS4 SIGNIFICANT DIGITS. LAST 4DIGITS USED

ExplanationThe LTH= position specification exceeded 4 digits; thelast 4 digits were used.


Programmer responseSpecify the appropriate position parameter again andrerun the job.

DFS1432I SC=08 LTH=(pp,nn), pp'S VALUEEXCEEDS 8000. 8000 USED

ExplanationThe LTH= position value exceeded 8000; it was set to8000.


Programmer responseSpecify a valid value again and rerun the job.

DFS1433I SC=08 LTH=(pp,nn), pp HAS NODIGITS. VALUE OF 2 USED

ExplanationThe LTH= position parameter was null; it was set to 2.


Programmer responseSpecify the appropriate position value, and rerun thejob.

DFS1434I SC=08 LTH=(pp,nn), nn EXCEEDS4 SIGNIFICANT DIGITS. LAST 4DIGITS USED


ExplanationThe LTH= length specification exceeded 4 digits; thelast 4 digits were used.


Programmer responseSpecify the length again and rerun the job.

DFS1435I SC=08 LTH=(pp,nn), nn'S VALUEEXCEEDS 8000. 8000 USED

ExplanationThe LTH= length value exceeded 8000; it was set to8000.


Programmer responseSpecify the value again and rerun the job.

DFS1436I SC=08 LTH=(pp,nn), nn HAS NODIGITS. VALUE OF 1 USED

ExplanationThe LTH= length parameter was null; it was set to 1.


Programmer responseSpecify the appropriate value, and rerun the job.

DFS1437I SC=08 FILL=C'', LITERAL LENGTHIS ZERO. BLANK USED

ExplanationThe FILL= literal specification was null; a blank wasused.


Programmer responseSpecify the appropriate literal, and rerun the job.

DFS1438I SC=04 FILL=C'', LITERAL LENGTHEXCEEDS 1 CHARACTER. FIRSTCHARACTER USED

ExplanationThe FILL= literal specification exceeded one character;the first character was used.


Programmer responseSpecify the literal again and rerun the job.

DFS1439I SC=04 FILL=X'hh', hh EXCEEDS2 CHARACTERS. FIRST 2CHARACTERS USED

ExplanationThe FILL= hexadecimal string exceeded twohexadecimal characters in length; the first twocharacters were used.


Programmer responseSpecify the hexadecimal string again and rerun the job.

DFS1440I SC=04 FILL=X'hh', hh HAS NOCHARACTERS. FILL=X'40' USED

ExplanationThe FILL= hexadecimal string specification is null; ablank is used.


Programmer responseSpecify the desired hexadecimal string, and rerun thejob.

DFS1441I SC=08 EXIT=(EXNUM,EXVEC),EXNUM EXCEEDS 3 SIGNIFICANTDIGITS. LAST 3 DIGITS USED


ExplanationThe EXIT= number exceeds 3 digits; the last 3 digitsare used.



DFS1442I SC=08 EXIT=(EXNUM,EXVEC),EXNUM'S VALUE EXCEEDS 127.VALUE OF 127 USED

ExplanationThe EXIT= number parameter exceeds 127; it is set to127.



DFS1443I SC=08 EXIT=(EXNUM,EXVEC),EXNUM HAS NO DIGITS. VALUE OFZERO USED

ExplanationThe EXIT= number parameter is null; it is set to zero.


Programmer responseSpecify the desired parameter, and rerun the job.

DFS1444I SC=08 EXIT=(EXNUM,EXVEC),EXVEC EXCEEDS 3 SIGNIFICANTDIGITS. LAST 3 DIGITS USED

ExplanationThe EXIT= vector specification exceeds 3 digits; thelast 3 digits are used.



DFS1445I SC=08 EXIT=(EXNUM,EXVEC),EXVEC'S VALUE EXCEEDS 255.VALUE OF 255 USED

ExplanationThe EXIT= vector parameter exceeds 255; it is set to255.



DFS1446I SC=08 EXIT=(EXNUM,EXVEC),EXVEC HAS NO DIGITS. VALUE OFZERO USED

ExplanationThe EXIT= vector parameter is null; it is set to zero.


Programmer responseSpecify the desired value, and rerun the job.

DFS1447I SC=08 COND= SPECIFICATIONINVALID FOR MSG.TYPE=INPUT.SPECIFICATION IGNORED

ExplanationThe COND= specification conflicts withMSG.TYPE=INPUT; COND= is ignored.


Programmer responseResolve the MSG/LPAGE conflicts, and rerun the job.

DFS1448I SC=08 PROMPT= SPECIFICATIONINVALID FOR MSG.TYPE=INPUT.SPECIFICATION IGNORED


ExplanationThe PROMPT= specification conflicts withMSG.TYPE=INPUT; PROMPT= is ignored.



DFS1449I SC=08 PASSWORD INVALID FORMSG.TYPE=OUTPUT. STATEMENTTREATED AS SEG STATEMENT

ExplanationThe PASSWORD statement conflicts withMSG.TYPE=OUTPUT; PASSWORD is ignored.


Programmer responseResolve the PASSWORD/MSG conflict, and rerun thejob.

DFS1450I SC=08 ONLY 1ST MFLD UNDERLAST PASSWORD STATEMENTUSED WHEN MSG.OPT=3SPECIFIED

ExplanationFor MSG/OPT=3 specification, only the first MFLDfollowing a PASSWORD statement can be used as apassword. Additional MFLD statements are ignored.


Programmer responseResolve the MSG/PASSWORD conflict, and rerun thejob.




DFS1451I SC=08 POSITIONAL PARAMETER1 REQUIRES DFLDNAMEFOR LITERAL WHENMSG.TYPE=OUTPUT SPECIFIED

ExplanationThe first MFLD parameter must be the devicefield name (dfldname) of a literal when theMSG.TYPE=OUTPUT. The parameter is ignored.


Programmer responseSupply the dfldname of the appropriate literal, andrerun the job.

DFS1452I SC=08 LTH=(pp,nn) INVALID FORMSG.TYPE=OUTPUT. pp VALUEIGNORED

ExplanationThe MFLD LTH=pp specification conflicts with theMSG.TYPE=OUTPUT; it is ignored.


Programmer responseResolve the MSG/MFLD conflict, and rerun the job.

DFS1453I SC=08 FILL= SPECIFICATIONINVALID FOR MSG.TYPE=OUTPUT.SPECIFICATION IGNORED

ExplanationThe FILL= specification conflicted withMSG.TYPE=OUTPUT; it was ignored.



DFS1454I SC=08 EXIT= SPECIFICATIONINVALID FOR MSG.TYPE=OUTPUT.SPECIFICATION IGNORED

ExplanationThe EXIT= specification conflicted withMSG.TYPE=OUTPUT; it was ignored.



DFS1455I SC=08 keyword= SPECIFICATIONINVALID FOR SCA FIELD.SPECIFICATION IGNORED

ExplanationThe SCA specification precluded ATTR= or JUST=specification on an MFLD statement. They wereignored.


Programmer responseSpecify the MFLD statement again, omitting thespecifications not needed, and rerun the job.

DFS1456I SC=08 keyword= SPECIFICATIONINVALID FOR SYSTEM LITERALFIELD. SPECIFICATION IGNORED

ExplanationThe system literal specification precluded ATTR=or JUST= specification on an MFLD statement. Thekeyword= specification was ignored.



Programmer responseSpecify the MFLD statement again, omitting thespecifications not needed, and rerun the job.

DFS1457I SC=08 LTH= SPECIFICATIONINVALID FOR SYSTEM LITERALFIELD. SPECIFICATION IGNORED

ExplanationThe system literal specification precluded LTH=specification on an MFLD statement; LTH= wasignored.


Programmer responseResolve the conflicts, and rerun the job.

DFS1458I SC=08 SYSTEM LITERAL FIELDINVALID FOR MSG.TYPE=INPUT.NULL FIELD CREATED

ExplanationThe system literal specification conflicted withMSG.TYPE=INPUT; it was ignored.


Programmer responseResolve the MFLD/MSG conflict, and rerun the job.

DFS1459I SC=08 SCA FIELD INVALID FORMSG.TYPE=INPUT. NULL FIELDCREATED

ExplanationThe SCA specification conflicted withMSG.TYPE=INPUT; it was ignored.


Programmer responseResolve the MFLD/MSG conflict, and rerun the job.

DFS1460I SC=08 LTH= SPECIFICATIONREQUIRED. VALUE OF 1 ASSUMED

ExplanationThe LTH= specification is required for this MFLD. Nonewas specified; LTH= is set to 1.


Programmer responseSpecify the desired LTH=, and rerun the job.

DFS1461I SC=04 MULTIPLE TYPE=KEYWORDS INVALID

ExplanationMore than one TYPE= specification has been madeon a single DIV or DEV statement; the second one isignored.


DFS1462I SC=04 MULTIPLE FEAT=KEYWORDS INVALID

ExplanationMore than one FEAT= specification has been made ona single DEV statement; the second one is ignored.


Programmer responseCorrect the FEAT= specification, and resubmit the job.

DFS1463I SC=04 MULTIPLE PEN=KEYWORDS INVALID

ExplanationMore than one PEN= specification has been made on asingle DEV statement; the second one is ignored.


Programmer responseCorrect the PEN= specification, and resubmit the job.

DFS1464I SC=04 MULTIPLE PFK=KEYWORDS INVALID


ExplanationMore than one PFK= specification has been made on asingle DEV statement; the second one is ignored.


Programmer responseCorrect the PFK= specification, and resubmit the job.

DFS1465I SC=04 MULTIPLE CARD=KEYWORDS INVALID

ExplanationMore than one CARD= specification has been made ona single DEV statement; the second one is ignored.


Programmer responseCorrect the CARD= specification, and resubmit the job.

DFS1466I SC=04 MULTIPLE DSCA=KEYWORDS INVALID

ExplanationMore than one DSCA= specification has been made ona single DEV statement; the second one is ignored.


Programmer responseCorrect the DSCA= specification, and resubmit the job.

DFS1467I SC=04 MULTIPLE MODE=KEYWORDS INVALID

ExplanationMore than one MODE= specification has been made ona single DEV statement; the second one is ignored.


Programmer responseCorrect the MODE= specification, and resubmit the job.

DFS1468I SC=04 MULTIPLE FTAB=KEYWORDS INVALID

ExplanationMore than one FTAB= specification has been made ona single DEV statement; the second one is ignored.


Programmer responseCorrect the FTAB= specification, and resubmit the job.

DFS1469I SC=04 MULTIPLE LDEL=KEYWORDS INVALID

ExplanationMore than one LDEL= specification has been made ona single DEV statement; the second one is ignored.


Programmer responseCorrect the LDEL= specification, and resubmit the job.

DFS1470I SC=04 MULTIPLE PAGE=KEYWORDS INVALID

ExplanationMore than one PAGE= specification was made on asingle DEV statement; the second one was ignored.


Programmer responseCorrect the PAGE= specification, and resubmit the job.

DFS1471I SC=04 MULTIPLE FORMS=KEYWORDS INVALID

ExplanationMore than one FORMS= specification has been madeon a single DEV statement; the second one is ignored.



Programmer responseCorrect the FORMS= specification, and resubmit thejob.

DFS1472I SC=04 MULTIPLE SYSMSG=KEYWORDS INVALID

ExplanationMore than one SYSMSG= specification was made on asingle DEV statement; the second one was ignored.


Programmer responseCorrect the SYSMSG= specification, and resubmit thejob.

DFS1473I SC=08 TYPE=OUTPUT INVALIDFOR DEV TYPE=3600

Explanation3600 device types are for input only.


Programmer responseCorrect DIV or DEV to reflect the appropriate results,and rerun the job.

DFS1474I SC=08 TYPE=INOUT INVALID FORSPECIFIED DEVICE TYPE

ExplanationOnly 3270s are INOUT device types.


Programmer responseCorrect DIV or DEV, and rerun the job.

DFS1475I SC=08 TYPE=INPUT INVALID FORSPECIFIED DEVICE TYPE

Explanation36XX are output only device types.


Programmer responseCorrect DIV or DEV, and rerun the job.

DFS1476I SC=04 MBRNAME EXCEEDS 8CHARACTERS. TRUNCATED TO 8CHARACTERS

ExplanationThe COPY member name exceeded 8 characters,which is not allowable; it was truncated.


Programmer responseCorrect the member name, if necessary, and rerun thejob.

DFS1477I SC=08 MBRNAME CONTAINSNO CHARACTERS. STATEMENTIGNORED

ExplanationNo member name was specified in a COPY statement.


Programmer responseCorrect the COPY statement, and rerun the job.

DFS1478I SC=08 RECURSIVE NESTED COPYOPERATIONS INVALID

ExplanationA COPY for a member, currently part of a nested copy,was invalid.

System actionProcessing continues; the COPY statement is ignored.

Programmer responseEnsure that the members to be copied do not referto members in a previously copied library. Correct theerror, and rerun the job.


DFS1479I SC=08 MBRNAME REQUESTEDNOT PRESENT IN SYSLIB

ExplanationNo member by this name was found in the SYSLIBcurrently pointed to.


Programmer responseSpecify the member name or PDS in the SYSLIB DDstatement again and rerun the job.

DFS1480I SC=12 PERMANENT I/O ERROR INSYSLIB DIRECTORY

ExplanationA permanent error condition was encountered onSYSLIB PDS directory.


Programmer responseRe-create the SYSLIB PDS directory, and rerun the job.

DFS1481I SC=12 SYSLIB DCB NOT OPENED.COPY IGNORED

ExplanationNo SYSLIB was specified; the COPY is ignored.


Programmer responseSpecify a SYSLIB or remove the COPY, and rerun thejob.

DFS1482I SC=08 SOR=DPAGENAMEREQUIRED

ExplanationNo SOR= specification was given for this LPAGE; SOR=was ignored.


Programmer responseSpecify SOR= DPAGE, and rerun the job.

DFS1483I SC=08 DO LINE INCREMENTEXCEEDS 2 DIGITS. LAST 2DIGITS USED

ExplanationThe DO line increment parameter exceeded 2 digits;the last 2 digits were used.


Programmer responseSpecify DO again using the appropriate line increment,and rerun the job.

DFS1484I SC=08 DO LINE INCREMENTCONTAINS NO DIGITS. VALUE OF1 USED

ExplanationThe DO line increment parameter was null; one wasassumed.


Programmer responseSpecify DO again using the appropriate line increment,and rerun the job.

DFS1485I SC=08 DO COLUMN INCREMENTEXCEEDS 3 DIGITS. LAST 3DIGITS USED

ExplanationThe DO column increment parameter exceeded 3digits; the last 3 digits were used.



Programmer responseSpecify DO again, using the column increment youwant, and rerun the job.

DFS1486I SC=08 DO COLUMN INCREMENTCONTAINS NO DIGITS. 'MAX'USED

ExplanationThe DO column increment parameter was null; MAXwas assumed.


Programmer responseSpecify DO again, using the column increment youwant, and rerun the job.

DFS1487I SC=04 NUMBER OF USERDEFINED FTAB CHARACTERSEXCEEDS MAXIMUM FORSPECIFIED DEVICE TYPE

ExplanationThe sum of the user-defined and predefined FTABcharacters was greater than the maximum allowed; itmust be 8. Predefined FTAB characters for device typeare as follows: 274X=HT,NL,LF; SCS1=HT,NL,LF,VT;SCS2=HT,NL,LF,VT,CR

System actionThe user-defined FTAB character string is truncated.Processing continues with the next operand.

Programmer responseSpecify the appropriate FTAB literal, within therestriction, and rerun the job.

DFS1488I SC=04 FTAB='LITERAL', LITERALHAS NO CHARACTERS. DEFAULTFTABS USED FOR APPLICABLEDEVICES

ExplanationThe FTAB literal specification was null. If predefinedFTAB characters are defined for a device, they areused.


Programmer responseSupply the appropriate FTAB= literal, and rerun thejob.

DFS1489I SC=04 MEMBER=mmmmmmmmNOT WRITTEN DUE TO SEVERITYCODE=ss

ExplanationThe member mmmmmmmm was not written to theREFERAL library because the highest severity code forthe member was equal to or greater than the valuespecified in the EXEC parameter STOPRC. Precedingmessages indicate errors and their respective severitycodes for the member.


Programmer responseCorrect the errors indicated, and rerun the job.

DFS1490I SC=08 SOR=, DPAGE NAME LISTINVALID FOR MSG.TYPE=OUTPUT.FIRST NAME USED

ExplanationThe SOR= specification conflicted withMSG.TYPE=OUTPUT; it was ignored.



DFS1491I SC=04 LINECNT=nnn, nnnEXCEEDS 3 DIGITS. LAST 3DIGITS USED

ExplanationThe LINECNT= parameter exceeded 999. The last 3digits were used as LINECNT.

System actionProcessing continues with next PARM field.


Programmer responseCorrect the LINECNT= parameter on the PARMstatement, and rerun the job.

DFS1492I SC=04 LINECNT=nnn, nnn HAS NODIGITS. VALUE OF 55 USED

ExplanationThe LINECNT= parameter was not numeric; lines perpage was set to 55.

System actionProcessing continues with the next PARM field.


DFS1493I SC=04 LINECNT=nnn, nnn IS LESSTHAN 25. VALUE OF 55 USED

ExplanationThe LINECNT= parameter was less than 25; lines perpage was set to 55.

System actionProcessing continues with the next PARM field.


DFS1494I SC=04 STOPRC=nnn, nnnEXCEEDS 3 DIGITS. LAST 3DIGITS USED

ExplanationThe STOPRC parameter exceeded 999; the last 3 digitswere used as STOPRC.


Programmer responseCorrect the STOPRC= parameter on the PARMstatement, and rerun the job.

DFS1495I SC=04 STOPRC=nnn, nnn HAS NODIGITS. VALUE OF 8 USED

ExplanationThe STOPRC= parameter was not numeric; STOPRCwas set to 8.


Programmer responseCorrect the STOPRC= parameter, and rerun the job.

DFS1496I SC=04 MULTIPLE CURSOR=KEYWORDS INVALID

ExplanationOnly one CURSOR= specification is allowed on asingle DPAGE statement; the second specification wasignored.

Programmer responseCorrect the specification, and rerun the job.

DFS1497I SC=04 MULTIPLE SELECT=KEYWORDS INVALID

ExplanationOnly one SELECT= specification is allowed on asingle DPAGE statement; the second specification wasignored.


DFS1498I SC=04 MULTIPLE ORIGIN=KEYWORDS INVALID

ExplanationOnly one ORIGIN= specification is allowed on asingle DPAGE statement; the second specification wasignored.


DFS1499I SC=04 MULTIPLE MULT=KEYWORDS INVALID

ExplanationOnly one MULT= specification is allowed on a singleDPAGE statement; the second specification wasignored.



DFS1500I SC=08 PDB STATEMENT NAMEREQUIRES A LABEL

ExplanationA label is required for each Partition Descriptor Block(PDB) statement. The DEV statement references thePDB statement by this label.

System actionA return code of 8 is set, and processing of the PDBstatement continues.

Programmer responseProvide a label for the PDB statement.

Severity:8




DFS1501I SC=08 PDB STATEMENT NAMEEXCEEDS 8 CHARACTERS

ExplanationThe label on the Partition Descriptor Block (PDB)statement exceeded 8 characters.


Programmer responseProvide a valid label for the PDB statement.

Severity:8

DFS1502I SC=12 NO PD STATEMENTSSPECIFIED

ExplanationEach Partition Descriptor Block (PDB) statement mustbe followed by at least one Partition Descriptor (PD)statement.

System actionA return code of 12 is set, and PDB definitioncontinues.

Programmer responseDefine at least one PD statement before the PDBENDstatement.

Severity:12

DFS1503I SC=08 PDBEND STATEMENT HASBEEN ASSUMED

ExplanationA PDBEND statement, which must terminate aPartition Descriptor Block (PDB) statement, was notfound; one has been assumed.


Programmer responseProvide a PDBEND statement to terminate the PDB.

Severity:8

DFS1504 SC=12 KEYWORD 'LUSIZE='IS REQUIRED ON THE PDBSTATEMENT BUT WAS NOTSPECIFIED

ExplanationThe required LUSIZE keyword was not present onthe Partition Descriptor Block (PDB) statement. TheLUSIZE keyword indicates the screen size to be usedfor validation of the view ports.


Programmer responseSpecify a LUSIZE keyword on the PDB statement.

Severity:12

DFS1505I SC=04 PD NAME SPECIFIEDON SYSMSG= TOO LONG, ISTRUNCATED TO 8 CHARACTERS

ExplanationThe Partition Descriptor (PD) name specified for theSYSMSG keyword on a Partition Descriptor Block(PDB) statement exceeded 8 characters; the first 8characters were used.



Programmer responseProvide a valid PD name for the SYSMSG keyword onthe PDB statement.


Severity:4


DFS1506I SC=08 SYSMSG= KEYWORD DOESNOT SPECIFY A NAME

ExplanationThe SYSMSG keyword was present on the PartitionDescriptor Block (PDB) statement, but was notfollowed by a required Partition Descriptor (PD) name.


Programmer responseProvide a valid PD name for the SYSMSG keyword.

Severity:8

DFS1507I SC=04 PDB NAME SPECIFIEDON PDB= IS TOO LONG, 1ST 8CHARACTERS USED

ExplanationThe Partition Descriptor Block (PDB) name in the PDBkeyword on the DEV statement exceeded 8 characters;the first 8 characters were used.

System actionA return code of 4 is set, and processing continues onthis definition.

Programmer responseCorrect the name specified in the PDB operand.


Severity:4


DFS1508I SC=08 PDB= NAME HAS NOCHARACTERS

ExplanationThe name of a Partition Descriptor Block (PDB) isrequired for the PDB keyword on the DEV statement,but a name was not specified.

System actionA return code of 8 is set, and processing continueswith the next definition.

Programmer responseProvide a name in the PDB keyword on the DEVstatement.


Severity:8


DFS1509W PSB/DBD name DELETE NOTALLOWED

Explanation:One of the catalog PSB or DBD resources (DFSCP000,DFSCD000, and DFSCX000) does not exist in thestaging ACBLIB. The catalog resources cannot bedeleted from the IMS online system while the catalogis enabled.

System action:The online change prepare phase is canceled.

System programmer response:Perform an ACBGEN with BUILD PSB=DFSCP000to the staging ACBLIB. Then, reissue the /MODIFYPREPARE ACBLIB command or INITIATE OLCPHASE(PREPARE) command.

DFS1510I SC=08 VALUE IN LUSIZE= TOOLONG, IS TRUNCATED TO 4 DIGITS


ExplanationThe LUSIZE value on the Partition Descriptor Block(PDB) statement exceeded 4 digits; the value wastruncated to 4 digits.


Programmer responseProvide a valid LUSIZE value on the PDB statement.

Severity:4

DFS1511I SC=08 NO VALUE WAS SPECIFIEDIN LUSIZE= ON PDB STATEMENTFOR WIDTH AND/OR DEPTH OFDISPLAY

ExplanationThe set of values specified for the LUSIZE keywordon the Partition Descriptor Block (PDB) statement todescribe the size of the display screen was not valid orwas missing.

System actionA return code of 8 is set, and processing of the (PDB)statement continues.

Programmer responseProvide a valid set of values for the LUSIZE keyword.

Severity:8

DFS1512E AN ALIAS CATALOG DATABASENAME dbname IS CODED IN THEPSB INSTEAD OF ITS STANDARDNAME

ExplanationThe ACB generation process encountered an errorbecause an alias name was used for the catalogdatabase or secondary index in the PSB. IMSautomatically performs alias translation for PCBs, soalias names are not allowed.

System actionThe BUILD PSB job for this PSB fails.

System programmer responseUse the prefix DFSC for the catalog database nameand secondary index name in your PCB.

DFS1513I SC=12 PD STATEMENT NAMEREQUIRES A LABEL

ExplanationEach Partition Descriptor (PD) statement requires alabel, but no label was found. The PD keyword on theDPAGE statement references the PD statement by thislabel.

System actionA label is generated for this PD statement, andprocessing of the PD statement continues. If moreerrors are found, the generated label is used toreference the PD statement.

Programmer responseProvide a label for the PD statement.


Severity:12


DFS1514I SC=04 PD STATEMENT NAMEIS TOO LONG, AND HAS BEENTRUNCATED TO 8 DIGITS

ExplanationThe label on the Partition Descriptor (PD) statementexceeded 8 characters; the first 8 characters wereused.

System actionA return code of 4 is set, and processing of the PDstatement continues.

Programmer responseProvide a valid label for the PD statement.

Severity:4


DFS1515I SC=12 KEYWORD 'PID=' ISREQUIRED ON THE PDSTATEMENT BUT WAS NOTSPECIFIED.

ExplanationThe required PID keyword, which identifies thepartition, was not specified on the Partition Descriptor(PD) statement.


Programmer responseProvide a PID keyword on the PD statement.

Severity:12

DFS1516I SC=12 KEYWORD 'VIEWPORT='IS REQUIRED ON THE PDSTATEMENT BUT WAS NOTSPECIFIED

ExplanationThe VIEWPORT keyword is required on each PartitionDescriptor (PD) statement, but was not specified. TheVIEWPORT keyword indicates viewport size.


Programmer responseProvide a VIEWPORT keyword on the PD statement.

Severity:12

DFS1517I SC=12 KEYWORD 'VIEWLOC='IS REQUIRED ON THE PDSTATEMENT BUT WAS NOTSPECIFIED.

ExplanationThe VIEWLOC keyword is required on each PartitionDescriptor (PD) statement, but was not specified. TheVIEWLOC keyword indicates the viewport location onthe screen.


Programmer responseProvide a VIEWLOC keyword on the PD statement.

Severity:12

DFS1518I SC=04 PDNAME SPECIFIED ONPD= IS TOO LONG, 1ST 8CHARACTERS USED

ExplanationThe Partition Descriptor (PD) name specified for thePD keyword on the DPAGE statement exceeded 8characters; the first 8 characters were used.

System actionA return code of 4 is set and processing of the DPAGEstatement continues.

Programmer responseProvide a valid PD name for the PD keyword on theDPAGE statement.

Severity:4

DFS1519I SC=08 PD= NAME HAS NOCHARACTERS

ExplanationA PD keyword was found on the DPAGE statement, butno Partition Descriptor (PD) name was specified.

System actionA return code of 8 is set, and processing of the DPAGEstatement continues.


Severity:8

DFS1520I SC=04 PDNAME SPECIFIED ONACTVPID= TOO LONG, 1ST 8CHARACTERS USED


ExplanationThe Partition Descriptor (PD) name specified for theACTVPID keyword on the DPAGE statement exceeded8 characters; the first 8 characters were used.



Severity:4

DFS1521I SC=08 ACTVPID= NAME HAS NOCHARACTERS

ExplanationAn ACTVPID keyword was found on the DPAGEstatement, but no name was specified.


Programmer responseProvide a valid name for the ACTVPID keyword on theDPAGE statement.

Severity:8

DFS1522I SC=08 DUPLICATE PID NUMBERSSPECIFIED ON TWO OR MOREPD STATEMENTS WITHIN A PDBDEFINITION

ExplanationA Partition Descriptor (PD) statement has a PIDnumber that was specified on a previous PD statementwithin this Partition Descriptor Block (PDB) definition.


Programmer responseProvide unique PID numbers for each PD statementwithin a PDB definition.

Severity:8

DFS1523I SC=08 PRESENTATION SPACEVALUE EXCEEDED, TRUNCATED TO5 DIGITS

ExplanationThe values specified on the PRESPACE keyword of thePartition Descriptor (PD) statement exceeded 5 digits;the first 5 digits were used.


Programmer responseProvide valid PRESPACE values on the PD statement.

Severity:8

DFS1524I SC=08 NULL PRESENTATIONSPACE VALUE IGNORED

ExplanationThe PRESPACE keyword was found on a PartitionDescriptor (PD) statement, but no presentation valueswere specified.


Programmer responseProvide valid values for the PRESPACE keyword, oromit the PRESPACE keyword, using the default for theVIEWPORT values.

Severity:8

DFS1525I SC=08 VIEWPORT ROWS VALUEEXCEEDED, TRUNCATED TO 5DIGITS

ExplanationThe VIEWPORT rows value on a Partition Descriptor(PD) statement exceeds 5 digits; the first 5 digits areused.



Programmer responseProvide a valid value for the VIEWPORT keyword onthe PD statement.

Severity:8

DFS1526I SC=08 VIEWPORT ROWS NULLVALUE IGNORED

ExplanationNo rows value was specified for the VIEWPORTkeyword on the Partition Descriptor (PD) statement.


Programmer responseProvide a valid rows value for the VIEWPORT keywordon the PD statement.

Severity:8

DFS1527I SC=08 PID VALUE EXCEEDED,TRUNCATED TO 2 DIGITS

ExplanationThe value specified for the PID keyword on thePartition Descriptor (PD) statement exceeds 2 digits;the first 2 digits are used.


Programmer responseProvide a valid value for the PID keyword.

Severity:8

DFS1528I SC=08 VIEWPORT ROWS VALUE ISZERO

ExplanationThe rows value on the VIEWPORT keyword on aPartition Descriptor (PD) statement must be greaterthan zero.


Programmer responseProvide a valid rows value for the VIEWPORT keyword.

Severity:8

DFS1529I SC=08 VIEWPORT COLS VALUEEXCEEDED, TRUNCATED TO 5DIGITS

ExplanationThe COLS value specified for the VIEWPORT keywordon a Partition Descriptor (PD) statement exceeded 5digits; the first 5 digits were used.


Programmer responseProvide a valid COLS value for the VIEWPORT keywordon the PD statement.

Severity:8

DFS1530I SC=08 VIEWPORT COLS NULLVALUE IS INVALID.

ExplanationNo value for COLS was specified for the VIEWPORTkeyword on a Partition Descriptor (PD) statement.





Severity:8


DFS1531I SC=08 PID NULL VALUE ISINVALID

ExplanationNo value was specified for the PID keyword on thePartition Descriptor (PD) statement.


Programmer responseProvide a value 0 - 15 for the PID keyword on the PDstatement.

Severity:8

DFS1532I SC=08 VIEWPORT COLS VALUE ISZERO

ExplanationThe value for COLS on the VIEWPORT keyword on aPartition Descriptor (PD) statement must be greaterthan zero.



Severity:8

DFS1533I SC=08 VIEWLOC ROWS= VALUEEXCEEDED, TRUNCATED TO 5DIGITS

ExplanationThe number of rows specified for the VIEWLOCkeyword on the Partition Descriptor (PD) statementexceeded 5 digits; the first 5 digits were used.


Programmer responseProvide a valid rows value for the VIEWLOC keywordon the PD statement.

Severity:8

DFS1534I SC=08 VIEWLOC ROWS NULLVALUE IS INVALID

ExplanationNo rows value was specified for the VIEWLOC keywordon the Partition Descriptor (PD) statement.


Programmer responseProvide a valid rows value for the location of theviewport before this PD statement can be accepted.

Severity:8

DFS1535I SC=08 SCROLLI= ROWS VALUEIS GREATER THAN THE NUMBEROF ROWS IN THE PRESENTATIONSPACE

ExplanationThe Partition Descriptor (PD) statement SCROLLIvalue was greater than the number of rows in thepresentation space. The scroll attempted to extendbeyond the presentation space.


Programmer responseProvide a valid SCROLLI value on the PD statement.


Severity:8



DFS1536I SC=08 VIEWLOC COLS= VALUEEXCEEDED, TRUNCATED TO 5DIGITS

ExplanationThe COLS value specified for the VIEWLOC keywordon the Partition Descriptor (PD) statement exceeded 5digits; the first 5 digits were used.


Programmer responseSupply a valid COLS value for the VIEWLOC keyword onthe PD statement.

Severity:8

DFS1537I SC=08 VIEWLOC COLS NULLVALUE IGNORED

ExplanationNo value for COLS was specified for the VIEWLOCkeyword on the Partition Descriptor (PD) statement.


Programmer responseProvide a valid COLS value on the VIEWPORT keywordfor the location of the viewport.

Severity:8

DFS1538I SC=04 PRESENTATION SPACEWAS SPECIFIED WITH FEWERROWS THAN THE VIEWPORT- HAS BEEN RESET TO THEVIEWPORT SIZE.

ExplanationThe PRESPACE rows value on the Partition Descriptor(PD) statement must not be smaller than theVIEWPORT rows value.

System actionThe PRESPACE rows value defaults to the VIEWPORTrows value. A return code of 4 is set, and processingcontinues with the next definition.

Programmer responseProvide a valid PRESPACE rows value on the PDstatement, or accept the default.


Severity:4


DFS1539I SC=08 INVALID PID NUMBERSPECIFIED, MUST BE FROM 0 TO15

ExplanationThe number specified for the PID keyword on thePartition Descriptor (PD) statement was invalid.


Programmer responseProvide a value 0 - 15 for the PID keyword on the PDstatement.

Severity:8

DFS1540I SC=08 WINDOWOF ROWS VALUEEXCEEDED, TRUNCATED TO 5DIGITS

ExplanationThe value specified for the WINDOWOF keyword onthe Partition Descriptor (PD) statement exceeded 5digits; the first 5 digits were used.



Programmer responseProvide a valid value for the WINDOWOF keyword onthe PD statement.

Severity:8

DFS1541I SC=04 WINDOWOF= KEYWORDHAS NO VALUE SPECIFIED

ExplanationNo value was provided for the WINDOWOF keyword onthe Partition Descriptor (PD) statement. A value of zerowas assumed

System actionThe hardware provides a default. A return code of 4 isset, and processing of the PD statement continues.

Programmer responseProvide a value for the WINDOWOF keyword.

Severity:4

DFS1542I SC=12 THE CELLSIZE WIDTHOR HEIGHT WAS SPECIFIED ASZERO, BUT NOT BOTH. THISCOMBINATION IS INVALID. BOTHSET TO ZERO.

ExplanationIf either the CELLSIZE width or the CELLSIZE heightwas specified as zero, then both must be specified aszero. Otherwise, both the CELLSIZE width and heightdefault to zero.

System actionA return code of 12 is set, and processing of thePartition Descriptor (PD) statement continues.

Programmer responseSpecify the values, or zero, for the CELLSIZE width andheight.

Severity:12

DFS1543I SC=08 CELLSIZE HORIZONTALVALUE EXCEEDED

ExplanationThe horizontal (character width) value specified forthe CELLSIZE keyword of the Partition Descriptor (PD)statement exceeded the maximum allowable value of12. If you specified more than two digits, only the firsttwo digits were used.


Programmer responseProvide a valid horizontal (character width) value forthe CELLSIZE keyword on the PD statement.

Severity:8

DFS1544I SC=04 CELLSIZE WIDTH NULLVALUE, A DEFAULT IS SET

ExplanationNo horizontal (character width) value was specified forthe CELLSIZE keyword on the Partition Descriptor (PD)statement; the value defaults to 6 pels.


Programmer responseProvide a horizontal (character width) value for theCELLSIZE keyword on the PD statement.

Severity:4

DFS1545I SC=08 CELLSIZE VERTICAL SIZEEXCEEDED, TRUNCATED TO 2DIGITS

ExplanationThe vertical (height) value specified for the CELLSIZEkeyword on the Partition Descriptor (PD) statementExceeded 2 digits; the first 2 digits were used.



Programmer responseProvide a valid vertical (height) value for the CELLSIZEkeyword on the PD statement.

Severity:8

DFS1546I SC=04 CELLSIZE VERTICAL SIZENULL VALUE, A DEFAULT IS SET

ExplanationNo vertical (height) value was specified for theCELLSIZE keyword on the Partition Descriptor (PD)statement; the value defaulted to 12 pels.


Programmer responseProvide a vertical (height) value for the CELLSIZEkeyword on the PD statement.

Severity:4

DFS1547I SC=08 SCROLLI ROWS VALUEEXCEEDED, TRUNCATED TO 5DIGITS

ExplanationThe value specified on the SCROLLI keyword of thePartition Descriptor (PD) statement exceeded 5 digits;the first 5 digits were used.


Programmer responseProvide a valid number for the SCROLLI keyword onthe PD statement.

Severity:8

DFS1548I SC=04 SCROLLI ROWS NULLVALUE IS IGNORED

ExplanationNo rows value was specified for the SCROLLI keywordon the Partition Descriptor (PD) statement.

System actionA value of zero is set, which causes the hardwareto provide a default. A return code of 4 is set, andprocessing of the PD statement continues.

Programmer responseProvide a rows value for the SCROLLI keyword on thePD statement.

Severity:4

DFS1549I SC=04 THE OFFSET + THEDEPTH OF THE WINDOW FORPD STATEMENT (pdname) DOESNOT FIT WITHIN THE PARTITION.OFFSET SET TO 00.

ExplanationThe WINDOWOF value, added to the VIEWPORT rowsvalue on the Partition Descriptor (PD) statement, wasgreater than the number of rows in the presentationspace. The viewport window would extend beyond thepresentation space.


Programmer responseProvide a valid value for the WINDOWOF keyword onthe PD statement. The value must be from 0 to thetotal number of rows in the presentation space.


Severity:4


DFS1550I SC=04 PRESENTATION SPACEWIDTH IS NOT EQUALTO THE VIEWPORT WIDTH.PRESENTATION SPACE WIDTH ISRESET TO THE VIEWPORT WIDTH.


ExplanationAn invalid value for the presentation space width wasencountered. If a value is specified, it must be equal tothe viewport width.


Programmer responseProvide a valid specification for the presentation spacewidth on the Partition Descriptor (PD) statement oraccept the default.


Severity:4





DFS1551I SC=08 MORE THAN 16PARTITIONS HAVE BEENSPECIFIED FOR PDB (pdname).ONLY 16 PD STATEMENTS AREALLOWED WITHIN A PDB.

ExplanationThe number of Partition Descriptor (PD) statementswithin a Partition Descriptor Block (PDB) must notexceed 16.

System actionA return code of 8 is set and processing continues withthe next definition.

Programmer responseEnsure that no more than 16 PD statements aredefined for each PDB statement.


Severity:8


DFS1552A MADS I/O TIMING STRUCTUREALLOCATION FAILURE, RC=rrrr,RSN=ssss

ExplanationIMS was not able to allocate a structure for long busytoleration in the coupling facility at startup. For anexplanation of the return codes, rrrr and ssss, seeIXLCONN return and reason codes information.


Programmer responseCorrect the problem and restart IMS. If MADS I/Otiming function is not required, delete the MADSIOT

specification from the DFSVSMxx PROCLIB memberand restart IMS.

Related referencez/OS: IXLCONN return and reason codes

DFS1553I MADS I/O TIMING INITIATED FORAREA areaname DDN=ddname

ExplanationAn ADS was treated as a MADS I/O timing condition.A physical read or write was inhibited by IMS. In themessage text:areaname



System actionIMS stops this ADS internally.

Programmer responseAfter the MADS I/O timing condition ends, run theCreate utility to create a new ADS.

DFS1554E MADS I/O TIMING INITIATIONFAILED FOR AREA areanameDDN=ddname RC=xx

ExplanationIMS detected a MADS I/O timing condition on this ADSbut failed to initiate MADS I/O Timing. The reasoncode, as specified by xx, indicates the cause of thefailure.






xxThe reason code that specifies the cause ofthe failure. The reason code can be one of thefollowing:Code

Meaning01

The AREA already has a MADS I/O timing ADS.02

An error occurred during the second CI update.03

This IMS is connected to the different liststructure.


System programmer responseAfter the MADS I/O timing condition ends, run thecreate utility to make a new ADS.

Module:DBFMLBI0

DFS1555E MADS I/O TIMING PROCESSINGERROR FOR AREA areanameDDN=ddname RC=xx

ExplanationIMS detected an error during MADS I/O timing. Thereason code indicates the cause of the failure. In themessage text:areaname



xxIndicates one of the following reasons:Reason code (hex)

Meaning01

The number of updated CIs in this AREAexceeded 1000, or the MADSIOT structureentry reached the limit of 1000.

02The allowable number of AREA exceeded 63.

03The MADS I/O timing did not terminate within60 seconds.

04A MADS I/O timing condition was detectedduring recovery.

05A read error occurred during recovery.

06A write error occurred during recovery.

07A lock failure occurred during recovery.

08A logical error occurred during recovery.

09Shutdown was initiated during MADS I/Otiming.

0AA read error was detected on the MADS I/Otiming ADS.

0BThe MADS I/O timing owner was not found inthe structure.

0CThe DMHR buffer was not obtained forrecovery.

0DADS was stopped by data sharer at thebeginning of recovery.

0EDBRC returned a nonzero return code. DBRCmight not have marked ADS as stopped.

0FIRLM returned a nonzero return code. The ADSstop request was not sent to data sharers.

11A deferred second CI refresh failed due to asecond CI error.

13The dummy read received a long busy error.ADS closes.

14Long busy recovery received a long busy erroror the second CI I/O received a long busy error.ADS closes.


Programmer responseCorrect the problem and run the Create utility to makea new ADS.


DFS1556E MADS I/O TIMING ISLLISTREQUEST FAILED FOR AREAareaname RC=rrrr RSN=ssss

ExplanationAn error occurred when IMS attempted handling thelong busy structure.

areaname is the name of the area that the long busyADS belongs to. For descriptions of the event codesand rrrr, see the IXLLIST return and reason codesinformation. The first two bytes of the reason code,rrrr, are can be one of the following codes:X'1001'

Request (WRITE) long busy owner if return code isgreater than 8.

X'1002'Request (WRITE) long busy entry if return code isequal to X'C' (DBFMLBI0 CF_UPDT).

X'1003'Request (WRITE) long busy entry if return code isgreater than X'C' (DBFMLBI0 CF_UPDT).

X'1004'Request (WRITE) new owner ID if reason code isnot equal to 0 or

IXLRSNCODESTATUSUNKNOWN

(DBFMLBI0 LONG_BUSY_TKO).X'1005'

Multiple entry case; request (WRITE) new ownerID if reason code is not equal to 0 or

IXLRSNCODESTATUSUNKNOWN

(DBFMLBI0 LONG_BUSY_TKO).X'3001'

Locking first list header; non-zero return code(DBFMLBR0 RECOVERY_PHASE1).

X'3002'Resetting lock on first list header; non-zero returncode (DBFMLBRO RECOVERY_PHASE1).

X'3003'A DELETE_LIST request received a non-zero returncode. DELETE or DELETE_ENTRYLIST is retriedwhen

RSN=IXLRSNTIMEOUT

(DBFMLBR0 RECOVERY_PHASE3).X'3004'

A request to delete owner entry receiveda non-zero return code (DBFMLBR0RECOVERY_PHASE3).

X'3005'A READ_LIST request received a non-zero returncode. The request is retried when

RSN=IXLRSNTIMEOUT

(DBFMLBR0 RECOVERY_PHASE3).

For X'1nnn' reason codes, this message is issued byDBFMLBI0; for X'3nnn' reason codes, it is issued byDBFMLBR0.

System actionIMS stops this ADS internally during IMS MADS I/Otiming.

Programmer responseIf the ADS stopped, run the Create utility to make anew ADS.

Module:DBFMLBI0, DBFMLBR0

DFS1558I MADS I/O TIMING ENDED FORAREA areaname DDN=ddname

ExplanationMADS I/O timing ended successfully. In the messagetext:areaname





DFS1559I MADS I/O TIMING STRUCTUREREBUILD INITIATED, RSN=rr

ExplanationThe rebuild of the long busy structure was initiated. rrindicates the cause for initiating the rebuild and can beone of the following codes:

Reason codeExplanation

01An error occurred in the coupling facility.


02A link error was detected.

03Operator entered the rebuild command.

System actionThe MADS I/O timing function is suspended while arebuild is in progress. After the rebuild completessuccessfully, the MADS I/O timing function continuesnormally. If the rebuild failed, MADS I/O timingfunction is disabled.

Operator responseEnsure that the rebuild completes successfully. Notifythe system programmer if a problem occurs duringthe rebuild. If the rebuild fails, contact the systemprogrammer to determine why.

DFS1560I SC=08 THE PDNAME SPECIFIEDON THE SYSMSG= KEYWORD ONTHE PDB STATEMENT DOES NOTEXIST IN THE PD STATEMENTSWITHIN THIS PDB.

ExplanationThe Partition Descriptor (PD) statement name,specified on the SYSMSG keyword, was not foundas a label (name) on any Partition Descriptor (PD)statement within this Partition Descriptor Block (PDB)definition.


Programmer responseMake sure that the PD statement name on the SYSMSGkeyword corresponds to a name on a PD statement.

Severity:8

DFS1561I SC=08 THE VIEWPORT POSITIONAND WIDTH FOR PD STATEMENT(pdname) DOES NOT FIT ON THESCREEN SPECIFIED BY THE PDB

ExplanationThe width of the screen required for this viewportexceeded the LUSIZE width specification on thePartition Descriptor Block (PDB) statement. This erroroccurs when the number of PELS or COLS, calculatedby adding the viewport's offset from the left of the

screen and the number of columns (width) of theviewport, is greater than the number of PELS or COLSspecified on the LUSIZE keyword.

System actionA return code of 8 is set, and validation of the PartitionDescriptor (PD) statement continues.

Programmer responseMake sure the dimensions of the viewport and itsoffsets (location on the screen) do not exceed theLUSIZE values.

Severity:8

DFS1562I SC=08 THE VIEWPORT POSITIONAND DEPTH FOR PD STATEMENT(pdname) DOES NOT FIT ON THESCREEN SPECIFIED BY THE PDB

ExplanationThe total depth of the screen required for this viewportexceeded the depth specified on the LUSIZE keywordon the Partition Descriptor Block (PDB) statement.This error occurs when the number of PELS or COLS,calculated by adding the viewport's offset from the topof the screen and the number of rows (depth) of theviewport, is greater than the number of PELS or COLSspecified on the LUSIZE keyword.

System actionA return code of 8 is set, and validation of the PartitionDescriptor (PD) statement continues.

Programmer responseMake sure the dimensions of the viewport and itsoffsets (location on the screen) do not exceed theLUSIZE value.

Severity:8

DFS1563I SC=08 THE AREA ON THE DISPLAYSPECIFIED FOR THE VIEWPORTSON PD STATEMENTS (pdname andpdname) OVERLAP.

ExplanationThe size and location specifications of the viewporton the named Partition Descriptor (PD) statementscaused the VIEWPORTS to overlap.


System actionA return code of 8 is set, and validation of the PDstatement continues.

Programmer responseCorrect the size and location specifications of theviewport on the named PD statements to eliminateoverlap.

Severity:8

DFS1564I SC=08 DUPLICATE PD NAME(pdname) DETECTED ON THE PDSTATEMENTS WITHIN THIS PDB

ExplanationDuplicate Partition Descriptor (PD) statement namesmust not be used within a Partition Descriptor Block(PDB) definition.


Programmer responseMake sure that each PD statement within a PDBdefinition has a unique name.

Severity:8

DFS1565I SC=04 WARNING - PD STATEMENT(pdname) CANNOT BE CHECKEDFOR OVERLAP WITH OTHERVIEWPORTS DUE TO CELLSIZE =ZERO

ExplanationThe identified viewport might overlap with otherVIEWPORTS. VIEWPORTS are checked for possibleoverlapping with other VIEWPORTS on the screen.However, when CELLSIZE is specified as zero, theviewport size is unknown and cannot be comparedwith the size of other VIEWPORTS.

System actionA return code of 4 is set, and processing of thePartition Descriptor (PD) statement continues.


Severity:4

DFS1566I SC=12 PDB DOES NOT SPECIFYLUDEFN=PELS, BUT VARIABLECELL SIZES EXIST IN PDSTATEMENTS. THIS IS INVALID.

ExplanationUnless LUDEFN=PELS is specified, the cell size ofevery Partition Descriptor (PD) statement within thePartition Descriptor Block (PDB) must be the same. Atleast two different cell sizes were detected.


Programmer responseEither specify the viewport offsets in pels, or ensurethat cell sizes are the same on all PD statements.

Severity:12

DFS1567I MADS I/O TIMING STRUCTUREREBUILD COMPLETED

ExplanationThe rebuild of the structure for multiple area data sets(MADS) I/O timing completed successfully.



DFS1568E MADS I/O TIMING STRUCTUREREBUILD FAILED, RSN=rr

ExplanationOne of the IMS systems failed to participate in therebuild of the structure for multiple area data sets(MADS) I/O timing. The reason code indicates thecause of the failure.

CodesExplanation

01This IMS connected to the structure, but anotherIMS failed to connect to the structure.


02This IMS cannot connect to the structure.

System actionMADS I/O timing function is disabled.

Programmer responseCorrect the problem and issue a /START MADSIOTcommand from an IMS (not the one that issued themessage) to restart MADS I/O timing. If the problemcannot be corrected, stop the IMS that generated theerror and issue the /START MADSIOT command.

DFS1569I SC=08 PDB= WAS SPECIFIED ONTHE DEV STATEMENT, BUT PD= ISNOT SPECIFIED ON THE DPAGESTATEMENT.

ExplanationWhen partitioning is used, the DEV statement mustspecify the PDB keyword and the DPAGE statementmust specify the PD keyword.

System actionProcessing continues with the next DEV, MSG, or FMTdefinition.

Programmer responseIf partitioning is used, specify the PDB keyword onthe DEV statement and the PD keyword on the DPAGEstatement. Otherwise, remove both keywords fromthese statements, and rerun the job.


Severity:8


DFS1570I SC=08 PD= WAS SPECIFIED ONTHE DPAGE STATEMENT, BUTPDB= IS NOT SPECIFIED ON THEDEV STATEMENT

ExplanationWhen partitioning is used, the DEV statement mustspecify the PDB keyword, and the DPAGE statementmust specify the PD keyword.


Programmer responseIf partitioning is used, specify the PDB keyword onthe DEV statement and the PD keyword on the DPAGEstatement. Otherwise, remove both keywords fromthese statements, and rerun the job.


Severity:8


DFS1571I SC=08 ACTVPID= WAS SPECIFIEDON THE DPAGE STATEMENT, BUTPDB= IS NOT SPECIFIED ON THEDEV STATEMENT.

ExplanationThe ACTVPID keyword can be specified on the DPAGEstatement only when the PDB keyword is specified onthe DEV statement.


Programmer responseIf partitioning is used, specify the PDB keyword onthe DEV statement. Otherwise, remove the ACTVPIDkeyword from the DPAGE statement, and rerun the job.


Severity:8


DFS1572I SC=08 PDB= WAS SPECIFIED ONTHE DEV STATEMENT, BUT THEREARE NO DPAGE STATEMENTS.


THERE MUST BE AT LEAST ONEDPAGE.

ExplanationThe PDB keyword can be specified on the DEVstatement only if at least one DPAGE statement hasbeen defined.


Programmer responseIf partitioning is used, verify that the PDB keyword isspecified on the DEV statement, define at least oneDPAGE statement, and rerun the job.


Severity:8


DFS1573I SC=04 THE PRESENTATION SPACEVALUE EXCEEDS 32767. VALUEALTERED TO 32767.

ExplanationThe rows or columns specification exceeded 32767;the value was set to 32767.


Programmer responseEnsure that the rows and columns specifications donot exceed 32767, and rerun the job.


Severity:4


DFS1586I SC=04 MIXED DATA FIELDSPANNING LINES MIGHT RESULTIN DATA TRUNCATION

ExplanationWhen DBCS data in a DBCS/EBCDIC mixed field startson an even boundary and continues on the next line,MFS replaces the last character with a blank and printsthe last DBCS character at the beginning of the nextline. As a result, one print position is lost on each lineand one character is truncated from each line.


Programmer responseSplit the DBCS/EBCDIC mixed field into two fields, ifnecessary; then rerun the job.

DFS1587I SC=04 EGCS FIELD SPECIFIED ONAN EVEN COLUMN

ExplanationThis is a warning message. An EGCS field wasspecified on an even column. Some devices requirethat extended graphic character set data be specifiedon an odd column. The first column of a line is column1.

System actionThe POS specification is accepted unchanged, andprocessing continues.

Programmer responseIf the specification is in error, correct the columnspecification on the POS keyword and rerun the job, ifnecessary. If the format is designed for the IBM 5550family, you can ignore this message.

DFS1588I SC=04 SO/SI CREATIONSUPERCEDED EGCS FIELD

ExplanationMIX or MIXS was specified together with EGCS'hh'.The MIX or MIXS value has priority over the EGCS'hh'value.

System actionIMS ignores the EGCS value, and uses the devicedefault.


Programmer responseIf the DFLD statement defines an EGCS or a DBCS/EBCDIC mixed field, either correct the keyword andrerun the job, or accept the device default value.

DFS1589I SC=04 OUTL'hh', BOX, RIGHT,LEFT, OVER, UNDER EXCLUSIVE

ExplanationThe field outlining keywords specified on the DFLDstatement were mutually exclusive.

System actionMFS uses the field outlining function specified first.

Programmer responseIf you do not want to use the default, correct the fieldoutlining specification; then rerun the job, if necessary.

DFS1590I SC=04 OUTL VALUE SHOULD BEX'00' to X'0F', X'00' ASSUMED.

ExplanationThe field outlining value specified on the OUTL'hh'keyword was not a number between X'00' and X'0F'.

System actionMFS uses the default value X'00'.

Programmer responseIf you do not want to use the default value, correctthe field outlining specification; then rerun the job, ifnecessary.

DFS1591I SC=08 SO CONTROL CHARACTERIS OPEN

ExplanationA DBCS/EBCDIC mixed field literal contained anunpaired SO control character.

System actionMFS does not create the MOD/MID or DOF/DIF blocks.

Programmer responseCorrect the DBCS/EBCDIC mixed field literal and rerunthe job.

DFS1592I SC=08 THERE IS A REDUNDANTTRAILING SI CHARACTER

ExplanationA DBCS/EBCDIC mixed field literal contained aduplicate closing SI control character

System actionMFS does not create the MOD/MID or DOF/DIF blocks.


DFS1593I SC=08 FIELD OUTLINING INVALIDFOR 3270P DEVICE TYPE

ExplanationField outlining was specified for a 3270P on a DFLDstatement, but was not valid for device type 3270P.

System actionMFS ignores the field outlining specification.

Programmer responseCorrect the device type or remove the field outliningspecification from the DFLD statement; then rerun thejob.

DFS1594I SC=08 MIX, MIXD, MIXS, MIX'nn',MIXS'nn' ARE EXCLUSIVE

ExplanationMIX, MIXD, MIXS, MIX'nn', and MIXS'nn' are mutuallyexclusive keywords, but more than one was specifiedon a DFLD statement.

System actionMFS does not create the DOF/DIF blocks.

Programmer responseSpecify only one of these keywords on the DFLDstatement; then rerun the job.

DFS1595I SC=04 MAXIMUM VALUE FOR MIX/MIXS'nn' is 31, DEFAULT SET AS xx

ExplanationThe value specified on the MIX/MIXS'nn ' keywordexceeded the maximum of 31; xx is used as thedefault.



Programmer responseIf the default MIX/MIXS'nn' value is not sufficient,correct the value; then rerun the job, if necessary.

DFS1596I SC=04 DEFAULT CALCULATED ISxx FOR MIX/MIXS

ExplanationMFS calculated the default for MIX/MIXS as xx.


Programmer responseIf the default MIX/MIXS'nn' value is not sufficient,correct the value; then rerun the job, if necessary.

DFS1597I SC=04 MIXD INVALID FOR MIXEDMODE LITERAL FOR SCS1

ExplanationThe MIXD keyword specified on a DFLD statement fora DBCS/EBCDIC mixed literal field was invalid for anSCS1 printer.

System actionMFS ignores the keyword MIXD and continuesprocessing.

Programmer responseCorrect the device type or the keyword; then rerun thejob, if necessary.

DFS1598I SC=04 MIXS and MIX/MIXS WITH'nn' VALID ONLY FOR TYPE=SCS1

ExplanationMIXS or MIX/MIXS'nn' was specified for a device otherthan an SCS1 printer, but is valid only for the SCS1printer.

System actionMFS ignores the invalid keyword and continuesprocessing.

Programmer responseRemove the MIXS or MIX/MIXS'nn' specification fromthe DFLD statement; then rerun the job, if necessary.

DFS1599I SC=08 MIXED MODE LITERALCONTAINS DBCS STRING WITHODD LENGTH

ExplanationOdd length DBCS data was specified in a DBCS/EBCDIC mixed field literal, but DBCS data must beeven length.

Programmer responseMFS does not create MOD/MID and DOF/DIF blocks.


DFS1600I SC=08 PFK= INVALID FORSPECIFIED DEVICE TYPE

ExplanationProgram function key specification for this device typeis not valid; it was ignored.


Programmer responseCorrect DEV or PFK=, and rerun the job.




DFS1601I SC=08 PEN= INVALID FORSPECIFIED DEVICE TYPE

ExplanationThe PEN= specification conflicted with the device type;the PEN= specification was ignored.


Programmer responseCorrect DEV or remove PEN=, and rerun the job.

DFS1602I SC=08 CARD= INVALID FORSPECIFIED DEVICE TYPE

ExplanationThe CARD= specification conflicted with the devicetype; the CARD= specification was ignored.


Programmer responseCorrect DEV or remove CARD=, and rerun the job.

DFS1603I SC=08 FTAB= INVALID FORSPECIFIED DEVICE TYPE

ExplanationThe FTAB= specification conflicted with the devicetype; the FTAB= specification was ignored.


Programmer responseCorrect DEV or remove FTAB=, and rerun the job.

DFS1604I SC=08 LDEL= INVALID FORSPECIFIED DEVICE TYPE

ExplanationThe LDEL= specification conflicted with the devicetype; the LDEL= specification was ignored.


Programmer responseCorrect DEV or remove LDEL=, and rerun the job.

DFS1605I SC=08 DSCA= INVALID FORSPECIFIED DEVICE TYPE

ExplanationThe DSCA= specification conflicted with the devicetype; the DSCA= specification was ignored.


Programmer responseCorrect DEV or remove DSCA=, and rerun the job.

DFS1606I SC=08 MODE= INVALID FORSPECIFIED DEVICE TYPE

ExplanationThe MODE= specification conflicted with the devicetype; the MODE= specification was ignored.


Programmer responseCorrect DEV or remove MODE=, and rerun the job.

DFS1607I SC=08 PAGE= INVALID FORSPECIFIED DEVICE TYPE

ExplanationThe PAGE= specification conflicted with the devicetype; the PAGE= specification was ignored.



Programmer responseCorrect DEV or remove PAGE=, and rerun the job.

DFS1608I SC=08 FORMS= INVALID FORSPECIFIED DEVICE TYPE

ExplanationThe FORMS= specification conflicted with the devicetype; the FORMS= specification was ignored.


Programmer responseCorrect DEV or remove FORMS=, and rerun the job.

DFS1609I SC=08 SYSMSG= INVALID FORSPECIFIED DEVICE TYPE

ExplanationThe SYSMSG= specification conflicted with the devicetype; the SYSMSG= specification was ignored.


Programmer responseCorrect DEV or remove SYSMSG=, and rerun the job.

DFS1610I SC=08 FEAT=IGNORE IS THE ONLYALLOWABLE SPECIFICATION FORSPECIFIED DEVICE TYPE

ExplanationFEAT= specification can only be IGNORE for thisdevice type; IGNORE was assumed.


Programmer responseExamine the conflicting statements, correct the error,and rerun the job.

DFS1611I SC=08 FEAT=VALUE(S) SPECIFIEDINVALID FOR SPECIFIED DEVICETYPE

ExplanationThe FEAT= specification conflicted with the devicetype; the FEAT= specification was ignored.


Programmer responseCorrect DEV or respecify FEAT=, and rerun the job.

DFS1612I SC=08 PAGE=EJECTPARAMETER(S) INVALID FORSPECIFIED DEVICE TYPE

ExplanationThe PAGE= specification conflicted with the devicetype; the PAGE= specification was ignored.


Programmer responseCorrect DEV or remove PAGE=, and rerun the job.

DFS1613I SC=08 FEAT=PFK FORCED FORPFK= SPECIFICATION

ExplanationFEAT=PFK was not specified, although PFK= was;FEAT=PFK was assumed.



DFS1614I SC=08 FEAT=PEN FORCED FORPEN= SPECIFICATION

ExplanationFEAT=PEN was not specified, although PEN= was;FEAT=PEN was assumed.




DFS1615I SC=08 FEAT=CARD FORCED FORCARD= SPECIFICATION

ExplanationFEAT=CARD was not specified although CARD= was;FEAT=CARD was assumed.



DFS1616I SC=08 FEAT=PARAMETERS AREMUTUALLY EXCLUSIVE

ExplanationThe features specified cannot coexist; they wereaccepted in the order of occurrence.


Programmer responseSelect the wanted features, and rerun the job.

DFS1617I SC=04 PEN=FIELDNAME,FIELDNAME TRUNCATED TO 8CHARACTERS

ExplanationPEN= field name exceeded 8 characters; the first 8characters were used.


Programmer responseCorrect the field name, and rerun the job.

DFS1618I SC=08 PEN=FIELDNAME,FIELDNAME HAS NO CHARACTERS

ExplanationNo field name was supplied for PEN= specification; itwas ignored.


Programmer responseSupply a field name, and rerun the job.

DFS1619I SC=04 PFK=(FIELDNAME,FIELDNAME TRUNCATED TO 8CHARACTERS

ExplanationPFK= field name exceeded 8 characters; the first 8characters were used.



DFS1620I SC=08 PFK=(FIELDNAME,FIELDNAME HAS NO CHARACTERS

ExplanationNo field name was provided for PFK= specification; itwas ignored.



DFS1621I SC=04 CARD=FIELDNAME,FIELDNAME TRUNCATED TO 8CHARACTERS

ExplanationCARD= field name exceeded 8 characters; the first 8characters were used.




DFS1622I SC=08 CARD=FIELDNAME,FIELDNAME HAS NO CHARACTERS

ExplanationNo field name was supplied for CARD= specification; itwas ignored.



DFS1623I SC=04 DSCA=X 'HEXSTRING',HEXSTRING TRUNCATED TO 4 HEXDIGITS

ExplanationThe DSCA= string was greater than 4 hexadecimaldigits; the first 4 hexadecimal digits were used.


Programmer responseLimit the DSCA= string to 4 hexadecimal digits, andrerun the job.

DFS1624I SC=08 DSCA=X 'HEXSTRING',HEXSTRING HAS NOCHARACTERS. X'0000' USED

ExplanationNo string was provided for the DSCA=X specification; itwas ignored.


Programmer responseCorect the DSCA=, and rerun the job.

DFS1625I SC=04 DSCA=nnnn, nnnnTRUNCATED TO LAST 15 DIGITS

ExplanationThe DSCA= integer exceeded 15 digits; the last 15digits were used.


Programmer responseCorrect the DSCA= integer, and rerun the job.

DFS1626I SC=04 DSCA=nnnn, nnnn HAS NODIGITS. DSCA=0 USED

ExplanationThe DSCA= specification had no digits; it was set tozero.


Programmer responseCorrect the DSCA= integer, and rerun the job.

DFS1627I SC=04 FORMS='LITERAL'EXCEEDS 16 CHARACTERS. FIRST16 CHARACTERS USED

ExplanationThe FORMS= literal specified exceeded 16 charactersin length; the first 16 characters were used.


Programmer responseCorrect the FORMS= specification, and rerun the job.

DFS1628I SC=04 PAGE=nnnn EXCEEDS 255.255 USED.

ExplanationThe PAGE= value exceeded the allowed limit of 255lines. A value of 255 lines was used.



Programmer responseCorrect the PAGE= value on the DEV statement, andrerun the job.

DFS1629I SC=04 PAGE=nnnn, nnnnTRUNCATED TO 4 DIGITS

ExplanationThe PAGE= value exceeded 4 digits; the last 4 digitswere used.


Programmer responseCorrect the PAGE= value, and rerun the job.

DFS1630I SC=04 PAGE=(nnnn, nnnn HAS NODIGITS. PAGE=55 USED

ExplanationNumber of lines in PAGE= specification of DEVstatement was null; 55 was used.

System actionProcessing continues with next source item.

Programmer responseIf number of lines other than 55 is wanted, correct thespecification and rerun the job.

DFS1631I SC=04 FORMS='LITERAL', LITERALHAS NO CHARACTERS. 4 BLANKSUSED

ExplanationThe FORMS= literal was null; four blanks were used.


Programmer responseCorrect the FORMS= literal, and rerun the job.

DFS1632I SC=04 SYSMSG=FIELDNAME,FIELDNAME TRUNCATED TO 8CHARACTERS

ExplanationThe SYSMSG= field name exceeded eight characters;the first eight characters were used.


Programmer responseCorrect the SYSMSG= field name, and rerun the job.

DFS1633I SC=08 SYSMSG=FIELDNAME,FIELDNAME HAS NO CHARACTERS

ExplanationSYSMSG= did not specify a field name; it was ignored.


Programmer responseCorrect the SYSMSG= field name, and rerun the job.

DFS1634I SC=08 CURSOR=((LINENO,LINENO HAS NO DIGITS. VALUEOF 1 USED

ExplanationThe line number parameter of the CURSOR=specification was blank (null); a value of one wasassumed.


Programmer responseCorrect the value, and rerun the job.

DFS1635I SC=08 CURSOR=((LINENO,LINENO EXCEEDS 3 DIGITS. LAST3 USED

ExplanationThe line number parameter of the CURSOR=specification exceeded 3 digits; it was truncated.




DFS1636I SC=08 CURSOR=((LINENO,LINENO VALUE EXCEEDSPHYSICAL PAGE LIMITS FORSPECIFIED DEVICE. LIMIT VALUEUSED

ExplanationThe line number parameter of the CURSOR=specification exceeded device limitations. The linesmaximum for the device type was used.


Programmer responseCorrect the CURSOR= specification, and rerun the job.

DFS1637I SC=08 CURSOR=((LINENO,COLNO,COLNO HAS NO DIGITS. VALUE OF2 USED

ExplanationThe column number parameter of the CURSOR= hadno digits; the value of 2 was used.



DFS1638I SC=08 CURSOR=((LINENO,COLNO,COLNO EXCEEDS 3 DIGITS. LAST 3DIGITS USED

ExplanationThe column number parameter of the CURSOR=specification exceeded 3 digits; it was truncated.



DFS1639I SC=08 CURSOR=((LINENO,COLNO,COLNO EXCEEDS DEVICE

CAPACITY. DEVICE CAPACITYLIMIT USED

ExplanationThe column number parameter of the CURSOR=specification exceeded device limitation. Themaximums of the column for the device type wasused.


Programmer responseCorrect the CURSOR= specification, and rerun the job.

DFS1640I SC=08 CURSOR=((LINENO,COLNO,FIELDNAME, FIELDNAME HASNO CHARACTERS. FIELDNAMEIGNORED

ExplanationThe field name parameter of the CURSOR=specification is null; it is ignored.


Programmer responseSpecify field name, if desired, and rerun job.

DFS1641I SC=08 CURSOR=((LINENO,COLNO,FIELDNAME,FIELDNAME,TRUNCATED TO 8 CHARACTERS

ExplanationThe field name parameter of the CURSOR=specification exceeds eight characters; it is truncated.


Programmer responseSpecify the field name again, and rerun the job.

DFS1642I SC=08 COND=(OFFSET, OFFSETHAS NO DIGITS. VALUE OF 0 USED


ExplanationThe offset value of the COND= specification has nodigits; it is set to 0.


Programmer responseSpecify the value, and rerun the job.

DFS1643I SC=08 COND=(OFFSET, OFFSETTRUNCATED TO LAST 5 DIGITS

ExplanationThe offset value of the COND= specification exceedsfive digits; it is truncated.


Programmer responseSpecify the value again, and rerun the job.

DFS1644I SC=08COND=(OFFSET,OPER,'LITERAL',LITERAL HAS NO CHARACTERS.SINGLE BLANK USED

ExplanationThe literal parameter of the COND= specification isnull; a blank is used.


Programmer responseSpecify the desired literal again, and rerun the job.

DFS1645I SC=08 CURSOR= SPECIFICATIONINVALID FOR DEVICE TYPESPECIFIED

ExplanationThe CURSOR= specification conflicts with the devicetype specified; it is ignored.



DFS1646I SC=08 COND= SPECIFICATIONINVALID FOR DEVICE TYPESPECIFIED

ExplanationThe COND= specification conflicts with the device typespecified; it is ignored.



DFS1647I SC=08 SELECT= SPECIFICATIONINVALID FOR DEVICE TYPESPECIFIED

ExplanationThe SELECT= specification conflicts with the devicetype specified; it is ignored.



DFS1648I SC=08 ORIGIN= SPECIFICATIONINVALID FOR DEVICE TYPESPECIFIED

ExplanationThe ORIGIN= specification conflicts with the devicetype specified; it is ignored.



DFS1649I SC=08 MULT= SPECIFICATIONINVALID FOR DEVICE TYPESPECIFIED


ExplanationThe MULT= specification was in conflict with thedevice type specified; it was ignored.



DFS1650I SC=08 FILL= SPECIFICATIONINVALID FOR DEVICE OR DIVTYPESPECIFIED

ExplanationThe FILL= specification was in conflict with the devicetype or DIVTYPE specified. FILL= is not permitted forDIV=INPUT or DEVTYPE=3600; it was ignored.






DFS1651I SC=04 MULTIPLE POS=KEYWORDS INVALID

ExplanationOnly one POS= parameter is allowable in a DFLDstatement; the second one was ignored.


Programmer responseCorrect the POS= specification, and rerun the job.

DFS1652I SC=04 MULTIPLE LTH=KEYWORDS INVALID

ExplanationOnly one LTH= parameter is allowable on a DFLDstatement; the second one was ignored.


Programmer responseCorrect the LTH= specification, and rerun the job.

DFS1653I SC=04 MULTIPLE ATTR=KEYWORDS INVALID

ExplanationOnly one ATTR= parameter is allowable in a DFLDstatement; the second one was ignored.


Programmer responseCorrect the ATTR= specification, and rerun the job.

DFS1654I SC=04 MULTIPLE PEN=KEYWORDS INVALID

ExplanationOnly one PEN= parameter is allowable in a DFLDstatement; the second one was ignored.


Programmer responseCorrect the PEN= specification, and rerun the job.

DFS1655I SC=04 MULTIPLE OPCTL=KEYWORDS INVALID

ExplanationOnly one OPCTL= parameter is allowable in a DFLDstatement; the second one was ignored.


Programmer responseCorrect the OPCTL= specification, and rerun the job.

DFS1656I SC=08 POS=(lll, lll TRUNCATED TOLAST 3 DIGITS

ExplanationThe POS=lll specification exceeded 3 digits; the last 3digits were used.


Programmer responseCorrect the POS= specification, and rerun the job.

DFS1657I SC=08 EATTR=(parm1,parm2),PARMS CONTAIN MUTUALLYEXCLUSIVE SPECIFICATIONS

ExplanationWithin the EATTR= specification there were conflictingparameters.


System actionAttributes are accepted and set in their order ofoccurrence. The second parameter (parm2) wasnot accepted. Processing continues with the nextparameter.

Programmer responseSelect the attributes you want, and rerun the job.

DFS1658I SC=08 POS=(lll, lll HAS NODIGITS. VALUE OF 1 USED

ExplanationThe POS=lll parameter had no digits; it was set to 1.



DFS1659I SC=08 POS=(lll,ccc, cccTRUNCATED TO LAST 3 DIGITS

ExplanationThe POS= column number exceeded 3 digits; the last 3digits were used.


Programmer responseSpecify the column you want, and rerun the job.

DFS1660I SC=08 POS=(lll,ccc ccc OUTSIDEDEFINED LINE BOUNDARIES FORDEVICE. ccc ADJUSTED TO LINE

ExplanationThe POS= column number falls outside the definedline boundaries for the device. Values that fall to theleft of the line are reset to the device left margin value+1. Values that fall to the right of the line are reset tothe device right margin value (-1 for DEV TYPE=3270Por 274X).


Programmer responseRespecify the POS= keyword, and rerun the job.

DFS1661I SC=08 POS=(lll,ccc ccc HAS NODIGITS. DEVICE LEFT MARGINVALUE +1 IS USED

ExplanationThe POS= column number had no digits; it was set tothe left margin value +1 for the specified device.


Programmer responseCorrect the POS= keyword, and rerun the job.

DFS1662I SC=08 POS=(lll,ccc,ppp, pppTRUNCATED TO LAST 3 DIGITS

ExplanationThe POS= page number exceeded 3 digits; the last 3digits were used.


Programmer responseSpecify the page number you want, and rerun the job.

DFS1663I SC=08 POS=(lll,ccc,ppp, ppp HASNO DIGITS. VALUE OF 1 USED

ExplanationThe POS= page number had no digits; it was set to 1.


Programmer responseSpecify the page number you want, and rerun the job.

DFS1664I SC=08 POS=nnn, nnn TRUNCATEDTO LAST 3 DIGITS

ExplanationThe POS= number exceeded 3 digits; the last 3 digitswere used.




DFS1665I SC=08 POS=nnn, nnn HAS NODIGITS. LEFT MARGIN VALUEUSED

ExplanationThe POS= number had no digits. It was set to the leftmargin value for the device.



DFS1666I SC=08 LTH=nnnn, nnnnTRUNCATED TO LAST 4 DIGITS

ExplanationThe LTH= specification exceeded 4 digits; the last 4digits were used.


Programmer responseCorrect the length, and rerun the job.

DFS1667I SC=08 LTH=nnn, nnn HAS NODIGITS. VALUE OF 1 USED

ExplanationThe LTH= specification had no digits; it was set to 1.



DFS1668I SC=08 ATTR=(parms), PARMSCONTAINS MUTUALLY EXCLUSIVESPECIFICATIONS

ExplanationWithin the ATTR= specification there were conflictingparameters. Attributes were accepted, and set in theirorder of occurrence.


Programmer responseCorrect the attributes, and rerun the job.

DFS1669I SC=08 PEN='LITERAL', LITERALHAS NO CHARACTERS. ' ' USED

ExplanationThe PEN= literal was null; it was set to a blank.


Programmer responseCorrect the literal, and rerun the job.

DFS1670I SC=04 OPCTL=TABLENAME,TABLENAME TRUNCATED TO 8CHARACTERS

ExplanationThe OPCTL= tablename exceeded 8 characters inlength; the first 8 characters were used.


Programmer responseCorrect the tablename specification, and rerun the job.

DFS1671I SC=08 OPCTL=TABLENAME,TABLENAME HAS NOCHARACTERS. OPCTL FUNCTIONNEGATED

ExplanationThe OPCTL= tablename was null; OPCTL= was ignored.



Programmer responseSupply the table name you want, and rerun the job.

DFS1672I SC=08 POS=(lll,ccc, cccDEFAULTED TO DEVICE LEFTMARGIN VALUE +1

ExplanationThe POS= column is set to the left margin value +1,if MODE=RECORD and no POS= column number wasspecified.


Programmer responseCorrect the parameter, and rerun the job.

DFS1673I SC=08 POS=nnn REQUIRED FORSTREAM MODE

ExplanationThe record mode form of the DFLD POS= keywordwas given when MODE=STREAM; the form POS=nnnis required. The next available stream position or theleft margin value was used.


Programmer responseSpecify the MODE= keyword of the DEV statement orthe POS= keyword of the DFLD statement, and rerunthe job.

DFS1674I SC=08 LTH=nnn OMITTED.DEFAULTED TO LTH=1

ExplanationNo LTH= parameter was specified for this DFLD; it wasset to 1.


Programmer responseCorrect the LTH= specification, and rerun the job.

DFS1675I SC=08 DFLD MUST HAVEDFLDNAME/LITERAL/SCA ORPASSWORD

ExplanationOne of the following DFLDNAME/LITERAL/SCA orPASSWORD must be specified for the DFLD statement.

System actionThe fixed name of DFLD ITB is set to TEMPNAME.

Programmer responseCorrect the DFLDNAME/LITERAL/SCA or PASSWORDspecification, and resubmit the job.

DFS1676I SC=08 LITERAL SPECIFICATIONINCOMPATIBLE WITH DFLDNAME

ExplanationThe literal type DFLD statements might not be labeled.

System actionThe literal is ignored, and processing continues withthe next operand.

Programmer responseRemove the label or the literal from the DFLDstatement, and rerun the job.

DFS1677I SC=08 PASSWORDSPECIFICATION INCOMPATIBLEWITH DFLDNAME

ExplanationThe DFLD statement, reserved for password input,might not be labeled.

System actionThe label is ignored, and processing continues with thenext operand.

Programmer responseCorrect the password specification, and rerun the job.

DFS1678I SC=08 keyword=operand INVALIDFOR SPECIFIED DEVICE TYPE


ExplanationThe operand on the specified keyword is not allowedfor the device type specified by the TYPE= operand ofthe DEV statement.

System actionThe keyword operand is ignored, and processingcontinues with the next operand.

Programmer responseRemove the operand, or correct the DEV TYPE=specification, and rerun the job.

DFS1679I SC=08 ATTR=(parms) INVALIDFOR THIS DEVICE

ExplanationThe ATTR=(parms) is valid only for 3270 display devicetypes; it was ignored.


Programmer responseCorrect the DEV/DFLD specification, and rerun the job.

DFS1680I SC=08 PEN= SPECIFICATIONINVALID FOR THIS DEVICE

ExplanationThe PEN= specification was invalid for this device type;it was ignored.


Programmer responseCorrect the DEV/DFLD specification, and rerun the job.

DFS1681I SC=08 PASSWORD INVALID FORTHIS DEV DIV TYPE

ExplanationThe PASSWORD parameter was in conflict with theDEV/DIV combination specified; it was ignored.


Programmer responseCorrect the PASSWORD conflict, and rerun the job.

DFS1682I SC=08 OPCTL= INVALID FOR THISDEV DIV TYPE

ExplanationThe OPCTL= parameter was in conflict with theDEV/DIV combination specified; it was ignored.


Programmer responseCorrect the OPCTL= conflict, and rerun the job.

DFS1683I SC=08 ATTR= INVALID FOR DEVDIV TYPE

ExplanationThe ATTR= parameter was in conflict with the DEV/DIVcombination specified; it was ignored.


Programmer responseCorrect the ATTR= conflict, and rerun the job.

DFS1684I SC=08 LITERAL INVALID FORTHIS DEV DIV TYPE

ExplanationThe DFLD literal specification was in conflict with theDEV/DIV combination specified.


Programmer responseCorrect the literal conflict, and rerun the job.

DFS1685I SC=04 DSCA=NUMBER, NUMBEREXCEEDS 65535. 0 USED

ExplanationThe DSCA=integer exceeded 65535; it was set to zero.



Programmer responseCorrect the DSCA= specification, and rerun the job.

DFS1686I SC=04 BRANCH TO LABEL,TRUNCATED TO 8 CHARACTERS

ExplanationThe IF statement labels cannot exceed 8 characters; itwas truncated.


Programmer responseCorrect the branch to label, and rerun the job.

DFS1687I SC=08 BRANCH TO LABEL HAS NOCHARACTERS. 'NOFUNC' USED

ExplanationThe IF statement branch to label was null; it was set toNOFUNC.


Programmer responseCorrect the branch to label, and rerun the job.

DFS1688I SC=04 COMPARAND LITERALTRUNCATED TO 255 CHARACTERS

ExplanationThe comparand literal exceeded 255 characters; thefirst 255 characters were used.



DFS1689I SC=08 COMPARAND LITERAL HASNO TEXT ' ' USED.

ExplanationThe comparand literal specified was null; it was set toone blank.



DFS1690I SC=08 LENGTH COMPARANDTRUNCATED TO 3 DIGITS

ExplanationThe length comparand exceeded 3 digits; the last 3digits were used.



DFS1691I SC=08 LENGTH COMPARAND HASNO DIGITS. VALUE OF 1 USED

ExplanationThe length comparand parameter was null; it was setto 1.



DFS1692I SC=08 POS=(lll, lll DEFAULTED TO1

ExplanationPOS=lll was set to 1 if MODE=RECORD, and no POS=parameter is specified.




DFS1693I SC=16 PERMANENT I/O ERRORUPDATING REFERAL LIBRARY.CONTINUING WITH SYNTAXCHECK ONLY

ExplanationIMS was unable to open the REFERAL data set, or anI/O error occurred while writing a block to the IMSREFERAL library.

System actionAll writes to the IMS REFERAL library are suppressed.Processing continues with syntax checking only.

Programmer responseEnsure that a DD statement is present and itsspecifications are correct. If a hardware failure isindicated, rerun the job.

DFS1694I SC=16 INSUFFICIENT DIRECTORYSPACE FOR UPDATE OF REFERALLIBRARY. CONTINUING WITHSYNTAX CHECK ONLY

ExplanationAn error occurred when no space was left in theREFERAL directory. The block could not be added orreplaced.

System actionProcessing continues with syntax checking only.

Programmer responseSpecify a larger quantity of space. Recreate the IMSREFERAL library, and rerun the job.

DFS1695I SC=20 PERMANENT I/O ERRORWRITING SYSTEXT DATA SET

ExplanationIssuing format or message control statements, orboth, resulted in a permanent I/O error on theSYSTEXT data set.

System actionProcessing terminates with a forced EOF.

Programmer responseEnsure that the DD statement is present, and itsspecifications are correct. If a hardware failure isindicated, rerun the job.

DFS1696I SC=04 MESSAGE 'mmmmmmmm'REASSIGNED TO FORMAT 'ffffff'

ExplanationA message was removed from a prior format set andchained to the new format set.

System actionProcessing continues as before.

Programmer responseEnsure that the new SOR=name is valid.

DFS1697I SC=12 REDEFINITION OF BLOCK'bbbbbbbb' ATTEMPTED, REFERALUPDATE ABORTED

ExplanationA block with the name bbbbbbbb exists on theIMS REFERAL library, but its name and type do notcorrespond.


Programmer responseCorrect the possibly wrong block name, or, ifvalid, scratch the old block; then rerun the sourcestatements.

DFS1698I SC=16 I/O ERROR WHILEPROCESSING DIRECTORY OFREFERAL LIBRARY. CONTINUINGWITH SYNTAX CHECK ONLY

ExplanationIMS was unable to open the REFERAL data set toprocess the directory entries, or an I/O error occurredwhile reading directory blocks.

System actionAll processing involving the IMS REFERAL library issuppressed, and processing continues with syntaxchecking only.


Programmer responseDetermine the nature of the I/O error, correct it, andrerun the job.

DFS1699I SC=16 REFERAL LIBRARYDIRECTORY CONTENTS INVALID.CONTINUING WITH SYNTAXCHECK ONLY

ExplanationIMS encountered an invalid directory entry whileprocessing the directory of the IMS REFERAL library.

System actionAll processing involving the IMS REFERAL library issuppressed, and processing continues with syntaxchecking only.

Programmer responseEnsure that the proper DD statement is presentwith the valid library before performing problemdetermination.

Problem determinationRun the MFS Service utility RELATE function, andinclude 11, 16.


DFS1700I SC=08 NO SEARCH TARGET LABELEXISTS FOR IF STATEMENT WITHTHE FOLLOWING LABEL: label

ExplanationThe label specified for conditional processing withinthis table was not valid.


Programmer responseCorrect the label for the appropriate conditionchaining, and rerun the job.




DFS1701I SC=04 FORMAT ffffff HASNO MESSAGES AND REQUIRESFURTHER COMPILATION

ExplanationFORMAT SET is incomplete; no valid message blockwas found.

System actionThe FMT block is stored in the referral library.Processing continues with the next FMT set, if any.If there is at least one valid FMT set at the end ofthe preprocessor phase, control is given to phase 1.Otherwise, control is returned to z/OS.

Programmer responseSpecify a valid input and output message block, andrerun FORMAT SET.

DFS1702I SC=04 MESSAGE mmmmmmmmHAS NO FORMAT AND REQUIRESFURTHER COMPILATION

ExplanationFORMAT SET is incomplete; no valid format block wasfound.

System actionMessage blocks are stored in the referral library.Processing continues with the next FMT set, if any.If there is at least one valid FMT set at the end ofthe preprocessor phase, control is given to phase 1.Otherwise, control is returned to z/OS.

Programmer responseSpecify a format block, and rerun FORMAT SET.

DFS1703I SC=08 FILL=PT INVALID FORSPECIFIED DEVICE TYPE C' 'USED

ExplanationDPAGE FILL=PT is valid only for 3270 video devices,for all others it is invalid and a blank is assumed.


Programmer responseCorrect the DEV/DPAGE, and rerun the job.

DFS1704I SC=04 IF LABEL TRUNCATED TO 8CHARACTERS

ExplanationAn IF statement was encountered whose labelexceeded 8 characters; the first 8 characters wereused.


Programmer responseCorrect the label and references, and rerun the job.

DFS1705I SC=08 DO COUNT OF 0. VALUE OF1 ASSUMED

ExplanationThe count omitted from MFLD or DFLD DO statement;a count of 1 was used.

System actionProcessing continues with next source item.

Programmer responseSpecify the count, and rerun the job.

DFS1706I SC=08 ATTR=operand INVALID IFLITERAL SPECIFIED ON MFLDSTATEMENT

ExplanationUse of attribute bytes in a field was in conflictwith the specification of a literal for that field. TheATTR=operand specification was ignored.



Programmer responseCorrect the MFLD statement; omit the specification notwanted. Then rerun the job.

DFS1707I SC=08 LTH=nnnn, nnnn EXCEEDS8000. 8000 USED

ExplanationDFLD field length exceeded maximum of 8000. 8000was used.


DFS1708I SC=04 STATEMENT LABEL TOOLONG

ExplanationStatement label exceeded 8 characters. No action wastaken at this time. Labels with a specific use can befurther diagnosed.

Programmer responseCorrect label, and rerun the job, if necessary.

DFS1709I SC=04 NO FTAB CHARACTERSDEFINED FOR 3600 DEVICE

ExplanationThe 3600 device does not have predefined FTABcharacters, and no user FTAB characters werespecified.


Programmer responseSpecify field tab characters if wanted, and rerun thejob.

DFS1710A AREA areaname TRIED TOCONNECT TO STR: structure_nameWRITE ERROR EEQE RBA 0FOUND- RECOVERY NEEDED.

ExplanationA new structure was being connect to this area.There were I/O toleration data on the last structureconnected as indicated by the write error EEQE atRBA 0. Those data were lost and the area must to berecovered.


The name of the area being connectedstructure_name

The name of the new structure

System actionAfter disconnecting from the new structure, the area isstopped and mark recovery needed.

Programmer responseEnsure the area data set (ADS) is marked unavailable.

Run the database recovery utility to recover the lostdata and delete the EEQE.

DFS1711I SC=16 DISP=SHR INVALID FORDDNAME=REFOUT. CONTINUINGWITH SYNTAX CHECK ONLY

ExplanationIMS REFERAL was to be altered, but either DISP=SHRor DD DUMMY was specified or the DD statement forREFOUT was missing.

System actionThe MFS Utility Preprocessor phase continues inputscan for syntax errors. No descriptions are stored inthe IMS REFERAL library. At the end of the input scan,the preprocessor returns to z/OS.

Programmer responseCorrect the DD statement in error, and resubmit thejob.

DFS1712I SC=04 MEMBER=mmmmmmmmNOT WRITTEN DUE TO INVALIDREFERAL DATA SET

ExplanationPrior IMS REFERAL library errors resulted in thesuppression of all processing involving the IMSREFERAL library. The member indicated was checkedfor valid syntax only.



Programmer responseDetermine the cause of the IMS REFERAL library error,check the source for syntax errors, and rerun the job.

DFS1713I SC=16 BAD COMPLETIONCODE FROM IEBCOPYSUBTASK COMPRESSION OFDDNAME=REFOUT. CONTINUINGWITH SYNTAX CHECK ONLY

ExplanationAn unexpected completion code was received fromIEBCOPY when compression of the IMS REFERALlibrary was requested.

System actionThe MFS Utility Preprocessor phase continuesscanning the input for syntax errors. No descriptionsare stored in the IMS REFERAL library. At the end ofthe input scan, the preprocessor returns to z/OS withthe highest return code for the phase.

Programmer response:3, 8, 12, 16, 36


DFS1714I SC=04 MULTIPLE SET/ONLINE/OFFLINE SPECIFICATIONS INHTAB= KEYWORD INVALID

ExplanationSET, ONLINE, or OFFLINE was specified more thanonce in a single HTAB= keyword.

System actionThe first SET, ONLINE, or OFFLINE specificationis used, multiple specifications are ignored, andprocessing continues with the next operand.

Programmer responseResolve the multiple specification conflict, and rerunthe job.

DFS1715I SC=04 MULTIPLE LEFT MARGINSPECIFICATIONS IN HTAB=KEYWORD INVALID

ExplanationA left margin value was specified more than once in asingle HTAB= keyword.

System actionThe first left margin value is used, multiplespecifications are ignored, and processing continueswith the next operand.


DFS1716I SC=04 MULTIPLE HT=SPECIFICATIONS IN HTAB=KEYWORDS INVALID

ExplanationThe HT= specification (tab stop values) was specifiedmore than once in a single HTAB= keyword.

System actionThe first HT= specification is used, multiplespecifications are ignored, and processing continueswith the next operand.


DFS1717I SC=04 DSCA= KEYWORD HAS NOMEANING AND IS IGNORED

ExplanationAt present, there are no DSCA-specified devicefunctions defined for the device type specified.

System actionThe DSCA= keyword is ignored, and processingcontinues with the next operand.

Programmer responseRemove the DSCA= keyword, and rerun the job.

DFS1718I SC=16 NO MEMBERS WRITTEN TOREFERAL LIBRARY. COMPILATION


TERMINATES WITH CURRENTPHASE

ExplanationThe IMS REFERAL library is input for the next phaseof the compilation process, so if the current phase(preprocessor) does not modify the IMS REFERALlibrary, the next phase is not executed.

System actionControl is returned to z/OS following termination of thepreprocessor phase of the utility.

Programmer responseExamine the preprocessor error messages and thevalue of the EXEC parameter STOPRC to determinewhy the members were not written to the IMSREFERAL library; then rerun the job.

DFS1719I SC=08 NO VALID HORIZONTALTAB STOPS SPECIFIED. HT=SPECIFICATION IGNORED

ExplanationThe HT= specification of the HTAB= keyword wasspecified, but the tab stop values were omitted orwere all invalid.

System actionThe HT= specification is ignored and processingcontinues with the next operand.

Programmer responseRespecify the HT= specification with valid horizontaltab stop values, and rerun the job.

DFS1720I SC=04 MULTIPLE BOUND=KEYWORDS INVALID

ExplanationMore than one BOUND= keyword is invalid on a singleDO statement.

System actionThe first BOUND= specification is used, multiplespecifications are ignored, and processing continueswith the next operand.


DFS1721I SC=04 MULTIPLE SUF=KEYWORDS INVALID

ExplanationMore than one SUF= keyword is invalid on a single DOstatement.

System actionThe first SUF= specification is used, multiplespecifications are ignored, and processing continueswith the next operand.


DFS1722I SC=04 SUF=nn, NN EXCEEDS 2DIGITS. LAST 2 DIGITS USED

ExplanationThe suffix value specified on the DO statementexceeded 2 digits.

System actionThe last 2 digits of the specified suffix value are used,and processing continues with the next operand.

Programmer responseCorrect the suffix value with 2 or fewer digits.

DFS1723I SC=04 SUF=nn, nn HAS NODIGITS. VALUE OF 01 USED

ExplanationThe suffix value was null.

System actionA suffix value of 01 is used, and processing continueswith the next operand.

Programmer responseSpecify a valid suffix value and rerun the job.

DFS1724I SC=04 DO STATEMENT SUFFIXWILL EXCEED MAXIMUM NUMBEROF DIGITS. COUNT IS ADJUSTED


ExplanationThe specified suffix value, when increased the numberof times specified by the count, results in thegeneration of suffix values greater than 2 digits.

System actionThe count is decreased such that the largest suffixgenerated is 2 digits, and processing continues.

Programmer responseAdjust the initial suffix value or count, and rerun thejob.

DFS1725I SC=04 BLANKS SPECIFIED ASLINE DELETE CHARACTERS

ExplanationTwo blank characters were specified on the LDELparameter. This situation forces the last 2 charactersof a line to be nonblank for a valid line.

System actionThe parameter is processed as specified.

Programmer responseMake sure that the LDEL specification is valid.

DFS1726I SC=04 VERTICAL TABBING MAYNOT BE VALID IF EJECT(BGNPP) OR EJECT (BGNMSG) NOTSPECIFIED

ExplanationVertical tabbing only has meaning relative to thebeginning of a new page. If the PAGE= parameterdoes not force a new page at either a new messageor physical page, vertical tabbing might not bevalid. Alternatively, all programs could specify EJECT(ENDMSG).

System actionThe statement is processed as specified.

Programmer responseVerify that the vertical tab stops position the pagecorrectly.

DFS1727I MADS I/O TIMING FUNCTIONRESUMED SUCCESSFULLY

ExplanationThe /START MADSIOT command completedsuccessfully. All IMS systems resumed long busytoleration support.

System actionLong busy toleration support is activated.


DFS1728E START MADSIOT COMMANDFAILED. RSN=rr

ExplanationThe /START MADSIOT command failed because oneIMS was unable to participate in the MADS I/O timingstructure. The reason code rr indicates the reason forfailure:Reason code

Meaning01

This IMS connected to the structure, but anotherIMS failed to connect to the structure.

02This IMS cannot connect to the structure.

System actionMADS I/O timing is still disabled.

Programmer responseCorrect the problem and reissue the /STARTMADSIOT command from an IMS (not the one thatoriginated the message) to restart MADS I/O timing.If the problem cannot be corrected, stop the IMS thatgenerated the error and reissue the /START MADSIOTcommand.

DFS1729I AREA CLOSE FOR AREA areanameREJECTED DUE TO MADS I/OTIMING

ExplanationIMS is in MADS I/O timing mode or MADS I/O timingrecovery mode and one of the following commandswas entered:

/STOP AREA/STOP ADS/DBRECOVERY DB/DBRECOVERY AREA


/VUNLOAD

areaname is the name of the area the command wasissued against.

System actionIMS rejected the command issued against the area.

Operator responseWait until recovery completes, then reissue thecommand.

DFS1730I SC=04 STACK IDENTIFIEREXCEEDS 8 CHARACTERS.TRUNCATED TO 8 CHARACTERS

ExplanationThe identifier specified on the STACK or UNSTACKstatement must be 8 or fewer characters in length.

System actionThe stack identifier is truncated to 8 characters, andprocessing continues with the next operand.

Programmer responseCorrect the stack identifier, check the correspondingSTACK or UNSTACK statement, and rerun the job.

DFS1731I SC=04 STACK IDENTIFIER HAS NOCHARACTERS. BLANKS USED

ExplanationThe preprocessor error recovery program has assumeda null identifier for the stack identifier.

System actionA stack identifier of eight blanks, indicating anunnamed stack, is used.

Programmer responseValidate the syntax of the STACK/UNSTACK statement,and rerun the job.

DFS1732I SC=08 UNEXPECTED 'STACK OFF'STATEMENT IGNORED

ExplanationA STACK OFF statement was encountered whenstacking was not in progress.

System actionThe STACK OFF statement is ignored, and processingcontinues with the next source statement.

Programmer responseEnsure that STACK ON and STACK OFF statements arebalanced and that STACK statements are not nested.

DFS1733I SC=08 NESTED 'STACK ON'STATEMENT IGNORED

ExplanationA STACK ON statement was encountered whilestacking was in progress for another STACK ONstatement. Nested stacking is not allowed.

System actionThe nested STACK ON statement is ignored, andstacking continues for the previous STACK ONstatement.

Programmer responseRearrange the source statements in the program sothat nested stacking is not required, and rerun the job.

DFS1734I SC=08 DUPLICATE STACKIDENTIFIER. PREVIOUS STACKDELETED; CURRENT STACK INEFFECT

ExplanationA STACK ON statement was encountered thatspecified the identifier of a stack that currently existedin real storage.

System actionThe stack that currently exists in real storage isdeleted, and stacking is initiated for the STACK ONstatement encountered.

Programmer responseSpecify unique identifiers for all stacks that currentlyexist in real storage.

DFS1735I SC=08 'UNSTACK' STATEMENTCANNOT BE STACKED. 'UNSTACK'STATEMENT IGNORED


ExplanationAn UNSTACK statement was encountered whilestacking was in progress. Nested stacking is notallowed.

System actionThe UNSTACK statement is ignored, and stackingcontinues for the current STACK ON statement.

Programmer responseRearrange the source statements in the program sothat nested stacking is not required, and rerun the job.

DFS1736I SC=08 STACK NOT FOUNDFOR IDENTIFIER SPECIFIEDIN 'UNSTACK' STATEMENT.'UNSTACK' STATEMENT IGNORED

ExplanationAn UNSTACK statement identified a stack that was notcurrently in real storage.

System actionThe UNSTACK statement is ignored and processingcontinues with the next source statement.

Programmer responseValidate the spelling of the stack identifier or specifythe KEEP option on a previous UNSTACK statementwith the same stack identifier.

DFS1737I SC=08 STACK REQUESTED IN'UNSTACK' STATEMENT IS EMPTY.'UNSTACK' STATEMENT IGNORED

ExplanationYou have attempted to create a stack but have notprovided any records for the stack.

System actionThe UNSTACK statement is ignored, and processingcontinues with the next source statement.

Programmer responseEnsure that at least one statement is included in thestack referenced by the UNSTACK statement.

DFS1738I SC=08 MISSING 'STACK OFF'STATEMENT. EOD RECEIVED

ExplanationA STACK OFF statement was not encountered for thecorresponding STACK ON statement before the end ofthe input stream source was encountered.

System actionA STACK OFF statement is assumed, and terminationprocessing continues.

Programmer responseDetermine if the last stack is needed and, if wanted,rerun the job.

DFS1739I SC=04 STACK 'ccccccc' WAS NOTDELETED

ExplanationAll stacks that were still in real storage when thepreprocessor terminates were deleted.

System actionTermination processing continues.

Programmer responseTo ensure that all stacks are deleted beforetermination processing, do not specify the KEEP optionon the last UNSTACK statement for each stack.

DFS1740I SC=08 DEV SPECIFICATIONEXCEEDS DESIGN LIMITS

ExplanationThe processing of this parameter can cause theDEV control block (DEVITB) to exceed the maximumdesign size. This situation normally only happenswhen you specify many long literals for PF keys.However, the check is made for FORMS literals, FTABS,horizontal tabs (HT), vertical tabs (VT), and all PF keyspecifications. The combined specification of theseparameters in one DEV statement cannot exceed 4064minus the basic size of the DEVITB (of approximately100 bytes).

System actionProcessing stops for the keyword that caused themessage to be issued and continues with the nextkeyword.


Programmer responseReduce the number and length of literals, or onlyspecify the maximum allowed number of horizontaland vertical tabs, or both. Rerun the job.

DFS1741I SC=04 MULTIPLE WIDTH=KEYWORDS INVALID

ExplanationMore than one WIDTH= keyword is invalid on a singleDEV statement.

System actionThe first WIDTH= specification is used, multiplespecifications are ignored, and processing continueswith the next operand.


DFS1742I SC=04 MULTIPLE HTAB=KEYWORDS INVALID

ExplanationMore than one HTAB= keyword is invalid on a singleDEV statement.

System actionThe first HTAB= specification is used, multiplespecifications are ignored, and processing continueswith the next operand.


DFS1743I SC=04 MULTIPLE VT= KEYWORDSINVALID

ExplanationMore than one VT= keyword is invalid on a single DEVstatement.

System actionThe first VT= specification is used, multiplespecifications are ignored, and processing continueswith the next operand.


DFS1744I SC=04 WIDTH=nnn; nnnTRUNCATED TO LAST 3 DIGITS

ExplanationThe width specified in the WIDTH= keyword exceeded3 digits.

System actionThe last 3 digits of the width are used and processingcontinues with the next operand.

Programmer responseSpecify a width of 3 or fewer digits, and rerun the job.

DFS1745I SC=04 WIDTH=nnn; nnn HAS NODIGITS. DEFAULT VALUE USED

ExplanationThe width specified in the WIDTH= keyword was null.

System actionThe default width for the specified device type is used,and processing continues with the next operand.

Programmer responseSpecify the appropriate width, and rerun the job.

DFS1746I SC=04 LEFT MARGIN VALUE OFHTAB= KEYWORD TRUNCATED TOLAST 3 DIGITS

ExplanationThe left margin value specified in the HTAB= keywordexceeded 3 digits.

System actionThe last 3 digits of the left margin value are used, andprocessing continues with the next operand.

Programmer responseSpecify a left margin value of 3 or fewer digits, andrerun the job.

DFS1747I SC=04 LEFT MARGIN VALUE OFHTAB= KEYWORD HAS NO DIGITS.VALUE OF 1 IS USED


ExplanationThe left margin value specified in the HTAB= keywordwas null.

System actionA left margin value of 1 is used, and processingcontinues with the next operand.

Programmer responseSpecify the appropriate left margin, and rerun the job.

DFS1748I SC=04 HORIZONTAL TAB STOPVALUE TRUNCATED TO LAST 3DIGITS

ExplanationA tab value in the HT= specification of the HTAB=keyword exceeded 3 digits.

System actionThe last 3 digits of the tab stop are used, andprocessing continues with the next operand.

Programmer responseSpecify the tab stop value with 3 or fewer digits, andrerun the job.

DFS1749I SC=08 NULL HORIZONTAL TABSTOP VALUE IGNORED

ExplanationA null horizontal tab stop value was encountered inthe HT= specification of the HTAB= keyword. Error-recovery procedures assumed a tab stop value with nodigits ($I$).

System actionThe null horizontal tab stop is ignored, and processingcontinues with the next operand.

Programmer responseEnsure that the syntax of the HTAB= keyword is valid,and rerun the job.

DFS1750I SC=04 VERTICAL TAB STOP VALUETRUNCATED TO LAST 3 DIGITS

ExplanationA tab stop value in the VT= keyword exceeded 3 digits.

System actionThe last 3 digits of the tab stop are used, andprocessing continues with the next operand.

Programmer responseSpecify the tab stop value with 3 or fewer digits, andrerun the job.




DFS1751I SC=08 NULL VERTICAL TAB STOPVALUE IGNORED

ExplanationA null vertical tab stop value was encountered in theVT= keyword. Error-recovery procedures can assume atab stop value with no digits ($I$).

System actionThe null vertical tab stop is ignored, and processingcontinues with the next operand.

Programmer responseEnsure that the syntax of the VT= keyword is valid, andrerun the job.

DFS1752I SC=08 SUB= VALUE INVALID,X'3F' USED

ExplanationThe value specified for SUB= was not a singlecharacter or 2 hexadecimal characters.

System actionThe default value of X'3F' is used, and processingcontinues with the next operand.

Programmer responseSpecify the SUB= value as either a single character oras 2 valid hexadecimal characters, and rerun the job.

DFS1753I SC=08 WIDTH= INVALID FORSPECIFIED DEVICE TYPE

ExplanationThe WIDTH= specification was in conflict with thespecified device type.

System actionThe WIDTH= specification is ignored, and processingcontinues with the next operand.

Programmer responseCorrect the DEV statement or remove the WIDTH=specification, and rerun the job.

DFS1754I SC=08 HTAB= INVALID FORSPECIFIED DEVICE TYPE

ExplanationThe HTAB= specification was in conflict with thespecified device type.

System actionThe HTAB= specification is ignored, and processingcontinues with the next operand.

Programmer responseCorrect the DEV statement or remove the HTAB=specification, and rerun the job.

DFS1755I SC=08 VT= INVALID FORSPECIFIED DEVICE TYPE

ExplanationThe VT= specification was in conflict with the specifieddevice type.

System actionThe VT= specification is ignored, and processingcontinues with the next operand.

Programmer responseCorrect the DEV statement or remove the VT=specification, and rerun the job.

DFS1756I SC=04 WIDTH=nnn; nnn EXCEEDSMAXIMUM VALUE. DEFAULT VALUEUSED

ExplanationThe width specified in the WIDTH= keywordexceeded the allowable maximum of 255 (249 forDEV.TYPE=SCS2).


System actionThe default width for the specified device type is used,and processing continues with the next operand.

Programmer responseSpecify a width of less than or equal to the maximum,and rerun the job.

DFS1757I SC=08 NO LEFT MARGIN ORTAB STOP VALUES. HTAB=SPECIFICATION IGNORED

ExplanationAn HTAB= keyword had no left margin or tab stopspecification.

System actionThe HTAB= keyword is ignored, and processingcontinues with the next operand.

Programmer responseSpecify a left margin or tab stops, or both, for theHTAB= keyword, or remove the HTAB= keyword, andrerun the job.

DFS1758I SC=08 LEFT MARGIN VALUEGREATER THAN PAGE WIDTH.VALUE OF 1 USED

ExplanationThe left margin value specified in the HTAB= keywordwas greater than the defined page width for thespecified device type.

System actionThe left margin value is set to 1, and processingcontinues with the next operand.

Programmer responseSpecify the left margin or page width value, and rerunthe job.

DFS1759I SC=08 INVALID HORIZONTAL TABSTOP(S) IGNORED

ExplanationOne or more invalid horizontal tab stop values wereencountered in the HT= specification of the HTAB=keyword. Tab stop values must be greater than or

equal to the left margin of the page and less than orequal to the right margin of the page.

System actionThe invalid tab stops are ignored, and processingcontinues with the next operand.

Programmer responseRemove the invalid tab stop values or change the leftor right margin values, or both, and rerun the job.

DFS1760I SC=04 DUPLICATE HORIZONTALTAB STOP(S) IGNORED

ExplanationTab stop values in the HT= specification of the HTAB=keyword must be distinct.

System actionRepeated occurrences of tab stop values are ignored,and processing continues with the next operand.

Programmer responseSpecify the tab stop values as distinct, and rerun thejob.

DFS1761I SC=08 NUMBER OF HORIZONTALTAB STOPS EXCEEDS MAXIMUM

ExplanationThe number of tab stop values, after invalid andduplicate values have been ignored, exceeds theallowable maximum of 10.

System actionThe first ten valid tab stops, sorted in ascending order,are used. Processing continues with the next operand.

Programmer responseSpecify the HTAB= keyword with 10 or fewer tab stopvalues in the HT= specification, and rerun the job.

DFS1762I SC=08 NO VALID VERTICALTAB STOPS SPECIFIED. VT=SPECIFICATION IGNORED

ExplanationThe VT= keyword was specified, but the tab stopvalues were omitted or were all invalid.


System actionThe VT= keyword is ignored, and processing continueswith the next operand.

Programmer responseSpecify the VT= keyword with valid vertical tab stopvalues and rerun the job.

DFS1763I SC=08 INVALID VERTICAL TABSTOP(S) IGNORED

ExplanationOne or more invalid vertical tab stop values wereencountered in the VT= keyword. Tab stop values mustbe greater than or equal to 1 and less than or equal tothe number of print lines per page and not to exceed avalue of 255.

System actionThe invalid tab stops are ignored, and processingcontinues with the next operand.

Programmer responseRemove the invalid tab stop values or specify thenumber of print lines per page, and rerun the job.

DFS1764I SC=04 DUPLICATE VERTICAL TABSTOP(S) IGNORED

ExplanationTab stop values in the VT= keyword must be distinct.

System actionRepeated occurrences of tab stop values are ignored,and processing continues with the next operand.

Programmer responseSpecify tab stop values as distinct, and rerun the job.

DFS1765I SC=04 NUMBER OF VERTICAL TABSTOPS EXCEEDS MAXIMUM

ExplanationThe number of tab stop values after invalid andduplicate values were ignored exceeded the allowablemaximum of 11.

System actionThe first 11 valid tab stops, sorted in ascending order,are used. Processing continues with the next operand.

Programmer responseSpecify the VT= keyword with 11 or fewer tab stopvalues, and rerun the job.

DFS1766I SC=04 POS=(lll,ccc,ppp), ppp NOTVALID FOR DIV TYPE=INPUT

ExplanationYou specified a page value in the POS= keyword of aninput DFLD, but it was invalid.

System actionThe page value is set to 0, and processing continueswith the next operand.

Programmer responseSpecify the POS= keyword of the DFLD statement, andrerun the job.

DFS1767I SC=04 VALIDATION ATTRIBUTESIGNORED

ExplanationThe validation attributes (VDFLD, VMFILL, or VMFLD)are ignored because the PROT attribute was eitherspecified or assumed (because a literal was specified).The validation attribute is not compatible with theprotect attribute.

System actionThe validation attributes are ignored, and processingcontinues.

Programmer responseCorrect the conflict either by removing the protect orthe validation attribute, and rerun the job.

DFS1768I SC=08 VALUE OF 0 INVALID,DEFAULT VALUE ASSUMED

ExplanationA value of 0 was specified for line (lll), column (ccc),page (pp), PAGE, WIDTH, LTH, or MFLD offset (pp).

System actionIn most cases a value of 1 is assumed except in thefollowing: the left margin value is assumed for ccc iflm was specified on the DEV statement; PAGE=55 isassumed; a WIDTH of 132 and 80 is assumed for SCS1


and SCS2, respectively. Processing continues with thenext operand.

Programmer responseCorrect the operand with the 0 specification, and rerunthe job.

DFS1769W CATALOG PCBS FAILED TOATTACH TO PSB psbnameERROR=xx

ExplanationThe application program using PSB psbname made itsfirst DL/I call to the catalog database. The PSB didnot have a DBPCB referencing the catalog database,so IMS attempted to dynamically attach the catalogPCBs. The attempt failed for one of the followingreasons:

01IRLM is defined but not active.

02IRLM is defined but not reachable.

03There is a PSB or PSBW pool space shortage.

04The catalog PSB or DBD resources are beingcommitted by an online change operation.

05The catalog PSB is unscheduled because thecatalog PSB is marked bad or is not available, orthe catalog database is stopped.

06The catalog database is unavailable becausea /DBD or /DBR command is in progress for thecatalog database.

System actionStatus code NA is returned to the application program.

System programmer responseFor error codes 01 and 02, check the availability ofIRLM in your IMS environment. For error code 03,increase the PSB or PSBW storage pool space. Forerror code 04, wait until the online change operation iscomplete and then issue the DL/I call again. For errorcode 05, ensure that the catalog PSB successfullycompleted ACBGEN and that the catalog databaseis started. For error code 06, wait until the DBD orDBR command completes processing and ensure thecatalog database is available.

Module:

DFSDBLM0

DFS1770I SC=16 NO FORMAT SETWRITTEN TO REFERAL LIBRARY.COMPILATION TERMINATES WITHCURRENT PHASE

ExplanationNo format sets were created or updated in thispreprocessor compilation.

System actionPhase 1 is not invoked in the preprocessor compilationas no valid blocks would be created. Compilationterminates.

Programmer responseCreate a valid format set consisting of an FMT and oneor more MSG statements. Rerun the job.

DFS1771I SC=08 NUMBER OF LITERALS ORCONTROL FUNCTIONS EXCEEDSDEVICE FEATURES. MAXIMUM NO.ASSUMED

ExplanationMore than the maximum allowable literals or controlfunctions were specified for the DEV statement.

System actionIf more than 36 literals or control functions arespecified on the PFK= operand, the first 36 are used.IMS continues with the next operand.

Programmer responseCorrect the syntax, and rerun the job.

DFS1772I SC=08 ONLY ONE PPAGESTATEMENT ALLOWED FOR DIVTYPE=INPUT

ExplanationMore than one PPAGE statement was supplied for DIVTYPE=INPUT.

System actionThis PPAGE statement is ignored, and processingcontinues with the next statement.


Programmer responseRemove the PPAGE statement from the input stream,and rerun the job.

DFS1773I SC=04 PPAGE STATEMENTASSUMED

ExplanationA PPAGE statement was assumed for the specifiedDEV.TYPE for DIV OPTIONS=MSG/DPAGE andTYPE=INPUT.

System actionA PPAGE statement is assumed and processingcontinues with the next statement.

Programmer responseSupply a PPAGE statement at this point in the inputstream, and rerun the job.

DFS1774I SC=08 PPAGE STATEMENT HASNO LABEL FOR OPTIONS=PPAGE.DIAGNOSTIC LABEL USED

ExplanationFor DIV OPTIONS=PPAGE, the PPAGE statement musthave a user-provided label so that a meaningful nameis sent to the remote program.

System actionIf no name is provided in the remote program, thediagnostic label is sent as the format name. ThePPAGE statement processing continues.

Programmer responseSpecify a label on the PPAGE statement, and rerun thejob.

DFS1775I SC=08 PPAGE STATEMENTINVALID FOR DEVICE TYPE.PPAGE STATEMENT IGNORED

ExplanationThe PPAGE statement was invalid for the specifiedDEV.TYPE.

System actionThe PPAGE statement is ignored, and processingcontinues with the next statement.

Programmer responseRemove the PPAGE statement from the input stream,and rerun the job.

DFS1776I SC=04 FEAT= TRUNCATED TOLAST 2 DIGITS

ExplanationMore than 2 digits were specified on the DEVstatement FEAT=number specification.

System actionThe FEAT=number specification is truncated to theright-most 2 digits. Processing continues with the nextoperand.

Programmer responseSpecify the FEAT=number to contain no more than 2digits. Rerun the job.

DFS1777I SC=08 NULL FEAT =number ; 1 ISASSUMED

ExplanationA null FEAT=number specification was supplied on theDEV statement. A feature number between 1 and 10must be provided.

System actionFEAT=1 is assumed, and processing continues with thenext operand.

Programmer responseSpecify a valid FEAT=number, and rerun the job.

DFS1778I SC=08 FEAT= INVALID. 1ASSUMED

ExplanationThe FEAT=number specification on the DEV statementmust be greater than or equal to 1 and less than orequal to 10. The number supplied was not in thisrange.

System actionFEAT=1 is assumed, and processing continues with thenext operand.

Programmer responseRespecify a valid FEAT=number, and rerun the job.


DFS1779I SC=12 MESSAGE LABEL ANDSOR= NAME CANNOT BEIDENTICAL. REFERAL UPDATEABORTED

ExplanationThe label on the MSG statement and the format nameon the SOR= keyword were identical; a valid directoryentry cannot be created.

System actionThe MSG block is not written to IMS REFERAL, andprocessing continues with the next source statement.

Programmer responseRename either the MSG label or the SOR= formatname parameter to ensure that the names aredifferent. Rerun the job.

DFS1780I SC=08 POS=nnn. nnn IS LESSTHAN 1 OR LEFT MARGIN

ExplanationThe POS= operand on the DFLD statement has beenspecified as 0 or is less than the left margin. In eithercase, the position of the DFLD is to the left of the leftmargin column.

System actionThe user-defined left margin is assumed as theposition of the DFLD. If no user-defined left marginwas supplied, a position of 1 is assumed. Processingcontinues with the next operand.

Programmer responseSpecify the wanted position number, and rerun the job.

DFS1781I SC=04 RCD STATEMENT CANNOTOCCUR IN THIS SEQUENCE IN THEINPUT STREAM. RCD STATEMENTIGNORED

ExplanationThe RCD statement can only appear after a PPAGE, DO,or DFLD statement, and within the scope of a DPAGEstatement.

System actionThe RCD statement is ignored, and processingcontinues with the next statement.

Programmer responseRemove the RCD statement from this point in the inputstream, and rerun the job.

DFS1782I SC=08 OPTIONS='option' INVALIDFOR SPECIFIED DEVICE TYPE

ExplanationThe option is not allowed for the device type specifiedby the TYPE= operand in the DEV statement, or thecombination of device type and DIV TYPE= operand.

System actionThe option indicated in the message is ignored, andprocessing continues with this statement.

Programmer responseCorrect the DEV TYPE= (or DIV TYPE=) specification,or remove this option, and rerun the job.

DFS1783 SC=08 'cccccccc' INVALID FOR DIVTYPE=OUTPUT

ExplanationOptions=/RDPN specification is valid only for DIVTYPE=INPUT for this device type.

System actionOptions=/RDPN specification reset and compilationcontinues.

Programmer responseRemove options=/RDPN parameter from DIVstatement or change to DIV TYPE= input. Resubmit thejob after making change.

DFS1784I SC=08 PPAGE STATEMENTASSUMED. DIAGNOSTIC LABEL OFASSUMED PPAGE USED

ExplanationA PPAGE statement was assumed for thespecified DEV.TYPE for DIV OPTIONS=PPAGE andTYPE=OUTPUT. The diagnostic label of the assumedPPAGE is sent to the remote program as the formatname.



Programmer responseSupply a PPAGE statement with a valid label at thispoint in the input stream, and rerun the job.

DFS1785I SC=04 RCD STATEMENT INVALIDFOR SPECIFIED DEVICE TYPE.RCD STATEMENT IGNORED

ExplanationThe RCD statement is invalid for the specifiedDEV.TYPE.


Programmer responseRemove the RCD statement from this point in the inputstream, and rerun the job.

DFS1786I SC=08 LINE INCREMENT ORPOSITION INCREMENT ISINVALID FOR DEVICE TYPE.SPECIFICATION IGNORED

ExplanationOn the DO statement, a line or position increment wasinvalid for the specified DEV.TYPE.

System actionThe DEV.TYPE specification is ignored, and processingcontinues with the next operand.

Programmer responseRemove the line or column increment from the DOstatement, and rerun the job.

DFS1787I SC=08 MAX OR COLUMNINCREMENT INVALID FOR DEVICETYPE. SPECIFICATION IGNORED

ExplanationOn the DO statement, a column increment or MAX wasinvalid for the specified DEV.TYPE.


Programmer responseRemove the column increment or MAX from the DOstatement, and rerun the job.

DFS1788I SC=08 BOUND= KEYWORDINVALID FOR DEVICE TYPE.SPECIFICATION IGNORED

ExplanationOn the DO statement, the BOUND= keyword wasinvalid for the specified DEV.TYPE.


Programmer responseRemove the BOUND= keyword from the DO statement,and rerun the job.

DFS1789I SC=04 MULTIPLE RCDSTATEMENTS WITH NOINTERVENING DFLDSTATEMENTS. LAST RCDSTATEMENT IGNORED

ExplanationMultiple RCD statements appeared consecutively inthe input stream.

System actionThe last RCD statement is ignored, and processingcontinues with the next statement.

Programmer responseRemove the RCD statement from the input stream, andrerun the job.

DFS1790I SC=08 ATTR= SPECIFICATIONINVALID FOR SPECIFIED DEVICETYPE

ExplanationOn a DFLD statement, only ATTR=YES or NO, andfor the specified device type, only ATTR=Yes andATTR=No are valid.

System actionThe ATTR= specification is ignored, and processingcontinues with the next operand.


Programmer responseCorrect the ATTR= specification on the DFLDstatement, and rerun the job.

DFS1791I SC=08 DPAGE STATEMENT HASNO LABEL FOR OPTIONS=DPAGE.DIAGNOSTIC LABEL USED

ExplanationFor DIV OPTIONS=DPAGE, the DPAGE statementmust have a user-provided label, so that the remoteprogram is sent a meaningful format name. If noneis provided, the diagnostic label is sent as the formatname.

System actionThe DPAGE statement processing continues.

Programmer responseSpecify a label on the DPAGE statement, and rerun thejob.

DFS1792I SC=08 DPAGE STATEMENTREQUIRED FOR DIVOPTIONS=DPAGE ANDTYPE=OUTPUT

ExplanationA DPAGE statement should be supplied forthe specified DEV.TYPE and DIV statement withOPTIONS=DPAGE and TYPE=OUTPUT. The label on theFMT statement is sent to the remote program as theformat name.


Programmer responseProvide a DPAGE statement with a valid label at thispoint in the input stream.

DFS1793I SC=08 SCA OPTION INVALIDFOR DEVICE TYPE. SCA OPTIONIGNORED

ExplanationOn the DFLD statement, the SCA option is invalid forthe specified DEV.TYPE.

System actionThe SCA option is ignored, and processing continueswith this operand.

Programmer responseRemove the SCA option from the DFLD, and rerun thejob.

DFS1794I SC=08 LTH=VALUE IS NOT2 FOR SCA OPTION. LTH=SPECIFICATION DEFAULTED TO 2

ExplanationThe SCA option had an LTH= value specified on theDFLD statement. other than 2.

System actionAn LTH=2 specification is assumed, and processingcontinues with this operand.

Programmer responseCorrect the LTH= specification to 2 on the DFLDstatement, and rerun the job, or omit the LTH=specification, and rerun the job.

DFS1795I SC=08 LABEL AND SCA OPTIONNOT COMPATIBLE. SCA OPTIONIGNORED

ExplanationA labeled DFLD statement cannot be reserved for SCAoutput.


Programmer responseRemove the label or the SCA option on the DFLDstatement, and rerun the job.

DFS1796I SC=08 LTH=VALUE GREATERTHAN 8 INVALID FOR PASSWORD.LTH=8 ASSUMED

ExplanationThe value specified for an LTH= operand was greaterthan 8 for the PASSWORD option on the DFLDstatement.


System actionLTH=8 is assumed, and processing continues with thisoperand.

Programmer responseSpecify LTH=8 or omit the LTH= operand on the DFLDstatement, and rerun the job.

DFS1797I SC=08 SCA OPTION INVALID FORDIV TYPE=INPUT. SCA OPTIONIGNORED

ExplanationThe SCA option is invalid on the DFLD for DIVTYPE=INPUT.


Programmer responseRemove the SCA option from the DFLD, and rerun thejob.

DFS1798I SC=04 MULTIPLE SEGEXIT/NOSEGEXIT SPECIFICATIONS INOPTIONS= KEYWORD INVALID

ExplanationMultiple SEGEXIT or NOSEGEXIT options weresupplied on the DIV statement OPTIONS=specification.

System actionThe first SEGEXIT or NOSEGEXIT option specified isused, and processing continues with this operand.

Programmer responseRemove the multiple SEGEXIT or NOSEGEXIT optionsfrom the OPTIONS= specification, and rerun the job.

DFS1799I SC=08 FLDEXIT/NOFLDEXIT/SEGEXIT/ NOSEGEXITPARAMETERS INVALID ONOPTIONS= KEYWORD FOR DIVTYPE=OUTPUT

ExplanationThe options FLDEXIT, NOFLDEXIT, SEGEXIT,NOSEGEXIT are invalid on the DIV statementOPTIONS keyword for DIV TYPE=OUTPUT.

System actionThese options are ignored, and processing continueswith this operand.

Programmer responseRemove FLDEXIT, NOFLDEXIT, SEGEXIT, orNOSEGEXIT from the OPTIONS keyword, or changeDIV TYPE to INPUT. Rerun the job.

DFS1800I SC=08 ATTR=operandINCOMPATIBLE WITH SCAOPTION. OPERAND IGNORED

ExplanationATTR=YES or ATTR=nn must not be specified on aDFLD statement when the SCA option is also specified.

System actionThe ATTR=YES or ATTR=nn specification is ignored,and processing continues with the next operand.

Programmer responseRemove ATTR=YES or ATTR=nn from the DFLDstatement, and rerun the job.




DFS1801I SC=16 NO DFLDS DEFINED INTHIS DPAGE. FMT MEMBER NOTWRITTEN TO REFERAL

ExplanationFor the specified DEV.TYPE and DIV TYPE=OUTPUT,at least one DFLD must be defined in this DPAGE. Aseverity code of 16 forces this FMT member not to bewritten to REFERAL.

System actionProcessing continues with the next statements with asyntax-only check for the remainder of this FMT.

Programmer responseDefine at least one DFLD statement in this DPAGE, andrerun the job.

DFS1802I SC=08 FIELD LENGTHCANNOT EXCEED DIV RCDCTLVALUE. LENGTH SPECIFICATIONDEFAULTED TO RCDCTL VALUE

ExplanationThis message is issued if RCDCTL=NOSPAN wasspecified and the LTH= specification on the namedDFLD has exceeded the DIV RCDCTL= value. Themessage is also issued if the literal DFLD length hasexceeded the DIV RCDCTL= value.

System actionThe RCDCTL value is assumed as the DFLD length, andprocessing continues with this operand.

Programmer responseChange either the DFLD LTH= specification or the DIVRCDCTL= specification such that the field length is lessthan or equal to the RCDCTL value. Rerun the job.

DFS1803I SC=04 POS= SPECIFICATIONIGNORED FOR DEVICE TYPE

ExplanationA POS= specification cannot be supplied on the DFLDfor the specified DEV.TYPE.

System actionThe POS= specification is ignored, and processingcontinues with this operand.

Programmer responseRemove the POS= specification from the DFLDstatement, and rerun the job.

DFS1804I SC=08 LDEL=X'HEXSTRING',HEXSTRING TRUNCATED TOFIRST 4 HEX CHARACTERS

ExplanationMore than 4 hexadecimal characters were suppliedon the LDEL= specification. The hexadecimal string istruncated to the left-most 4 hexadecimal characters.

System actionProcessing continues with this operand.

Programmer responseProvide 4 hexadecimal characters on the LDEL=specification on the DEV statement, and rerun the job.

DFS1805I SC=04 LDEL=X'HEXSTRING', HEXDIGITS OF X'0000' SPECIFIED

ExplanationLine delete characters of X'0000' can inadvertentlycause a segment to be deleted when the last field inthe segment contains EBCDIC nulls (X'00').


Programmer responseVerify that line delete characters of '0000' do notconflict with EBCDIC nulls.

DFS1806I SC=08 LDEL=X'HEXSTRING', NULLHEX STRING SPECIFIED. DEVICETYPE DEFAULT USED


ExplanationOn the DEV statement, LDEL= has a null hexadecimalstring.

System actionThe DEV.TYPE line delete default is assumed. Forthe device type defaults, see the DEV statementinformation. Processing continues with this operand.

Programmer responseProvide a valid LDEL= specification, and rerun the job.

Related referenceDEV statement (System Utilities)

DFS1807I SC=08 type-c INTEGERTRUNCATED TO FIRST 2 DIGITS

ExplanationThe DPM-An, DPM-Bn, or 3270-An of the DEVstatement n exceeded 2 digits.

System actionThe first 2 digits of n are used, and processingcontinues with this operand value.

Programmer responseSpecify a valid number on the TYPE= operand, andrerun the job.

DFS1808I SC=08 NULL NUMBER FOLLOWEDtype. type-identifier ASSUMED

ExplanationA number was not specified after the symbolic devicetype on the TYPE= operand.

System actionA device type identifier is assumed, and processingcontinues with this operand. Device types that can beassumed are: DPM-A1, DPM-B1, or 3270-A1.

Programmer responseSpecify a valid number on the TYPE= operand, andrerun the job.

DFS1809I SC=08 INVALID INTEGERSPECIFIED IN type DEVICE TYPE.type-identifier ASSUMED

ExplanationA device-type identifier must be specified as a 1- or2-digit number from 1 to 15 as part of the TYPE=operand in the DEV statement.

System actionA device type identifier is assumed, and processingcontinues with this operand. Device types that can beassumed are: DPM-A1, DPM-B1, or 3270-A1.

Programmer responseSpecify a valid integer for DEV TYPE= operand, andrerun the job.

DFS1810I SC=08 FTAB=X'HEXSTRING' TOOLONG. HEX STRING TRUNCATEDTO FIRST 16 DIGITS

ExplanationMore than 16 hexadecimal digits were found in theFTAB=X'HEXSTRING' specification.

System actionThe hexadecimal string is truncated to the first 16hexadecimal digits. Processing continues with thisoperand.

Programmer responseCorrect the hexadecimal string FTAB specification, andrerun the job.

DFS1811I SC=08 'HEXSTRING' CONTAINSODD NO. OF DIGITS. LAST BYTEPADDED ON RIGHT WITH 0

ExplanationAn odd number of hexadecimal digits was found in thespecification. The last hexadecimal digit is padded by ahexadecimal zero to complete the character.


Programmer responseSpecify an even number of hexadecimal digits in thehex string specification, and rerun the job.

DFS1812I SC=04 FTAB=X'HEXSTRING', HEXDIGIT OF X'00' MAY BE


http://www.ibm.com/support/knowledgecenter/SSEPH2_15.1.0/com.ibm.ims15.doc.sur/ims_mfslangdevstmt.htm#ims_mfslangdevstmt

INCOMPATIBLE WITH DIVNULL=DELETE

ExplanationSpecifying DIV NULL=DELETE causes removal oftrailing EBCDIC nulls (X'00') in a field until an FTABcharacter is reached. An FTAB character of X'00' wasnot treated as an FTAB, but is deleted as an EBCDICnull.


Programmer responseIf DIV NULL=DELETE is specified, change the DIVNULL=DELETE specification or do not define X'00' asa hexadecimal digit in an FTAB character. Rerun thejob.

DFS1813I SC=04 MULTIPLE FLDEXIT/NOFLDEXIT SPECIFICATIONS INOPTIONS= KEYWORD INVALID

ExplanationMultiple FLDEXIT or NOFLDEXIT options weresupplied on the DIV statement OPTIONS=specification.

System actionThe first FLDEXIT or NOFLDEXIT option specified isused, and processing continues with this operand.

Programmer responseRemove the multiple FLDEXIT or NOFLDEXIT optionsfrom the OPTIONS= specification, and rerun the job.

DFS1814I SC=08 USER FTAB CHARACTERSREQUIRED FOR MIX OR ALL. NONEDEFINED. FORCE ASSUMED

ExplanationInput data editing for the MIX or ALL options requireuser-defined FTAB characters. No FTAB characterswere defined.

System actionFORCE is assumed. Processing continues with thisoperand.

Programmer responseSupply FTAB characters or change the MIX or ALLoption to FORCE. Rerun the job.

DFS1815I SC=08 LDEL='LITERAL' LENGTHNOT EQUAL 2. DEVICE TYPEDEFAULT USED

ExplanationMore than 2 line-delete characters were specified onthe LDEL= operand.

System actionThe LDEL= operand is ignored and the devicetype default is used. Processing continues with thisoperand.

Programmer responseSpecify 2 line-delete characters, and rerun the job.

DFS1816I SC=04 MULTIPLE NULL=KEYWORDS INVALID

ExplanationMultiple NULL= keywords were coded on the DIVstatement.

System actionThe first specification is used, and processingcontinues with this operand.

Programmer responseRemove the multiple NULL= specifications, and rerunthe job.

DFS1817I SC=04 MULTIPLE OPTIONS=KEYWORDS INVALID

ExplanationMultiple OPTIONS= keywords were coded on the DIVstatement.


Programmer responseRemove the multiple OPTIONS= specifications, andrerun the job.


DFS1818I SC=04 MULTIPLE HDRCTL=KEYWORDS INVALID

ExplanationMultiple HDRCTL= keywords were coded on the DIVstatement.


Programmer responseRemove the multiple HDRCTL= specifications, andrerun the job.

DFS1819I SC=04 MULTIPLE keyword=KEYWORDS INVALID

ExplanationThe same keyword was specified more than once onthe same statement.

System actionThe first specification is used, and processingcontinues with this statement.

Programmer responseSpecify the keyword and its operand only once, andrerun the job.

DFS1820I SC=04 MULTIPLE SPAN/NOSPANSPECIFICATIONS IN RCDCTLKEYWORDS INVALID

ExplanationMultiple SPAN or NOSPAN options were found on thesame RCDCTL= specification.

System actionThe first SPAN or NOSPAN option specified is used,and processing continues with this operand.

Programmer responseRemove the multiple SPAN or NOSPAN options, andrerun the job.

DFS1821I SC=04 MULTIPLE NUMBERS INRCDCTL SPECIFICATION INVALID

ExplanationMultiple record size numbers were specified on theRCDCTL= specification.

System actionThe first record limit is used, and processing continueswith this operand.

Programmer responseRemove the multiple record size numbers, and rerunthe job.

DFS1822I SC=08 RCDCTL NUMBERTRUNCATED. LAST 5 DIGITS USED

ExplanationThe numeric record size has exceeded 5 digits in theDIV statement RCDCTL= specification.

System actionThe last 5 digits are used, and processing continueswith this operand.

Programmer responseSpecify a record size of no more than 5 digits. Rerunthe job.

DFS1823I SC=08 NULL RCDCTL NUMBER.256 USED

ExplanationA null record size number was supplied on the DIVstatement RCDCTL= specification.

System actionA record size of 256 is assumed, and processingcontinues with this operand.

Programmer responseSpecify a valid record size, and rerun the job.

DFS1824I SC=08 RCDCTL NUMBER OF 0INVALID. 256 USED

ExplanationA zero record size was supplied on the DIV statementRCDCTL= specification. The record size must bebetween 1 and 32000.


System actionA default record size of 256 is assumed, andprocessing continues with this operand.

Programmer responseSpecify a valid record size on the RCDCTL=specification and rerun the job.

DFS1825I SC=08 RCDCTL NUMBER EXCEEDS32000. 256 USED

ExplanationA record size greater than 32000 was supplied on theDIV statement RCDCTL= specification. The record sizemust be between 1 and 32000.

System actionA default record size of 256 is assumed, andprocessing continues with this operand.

Programmer responseSpecify a valid record size on the RCDCTL=specification, and rerun the job.

DFS1826I SC=04 MULTIPLE FIXED/VARIABLE SPECIFICATIONS INHDRCTL= KEYWORD INVALID

ExplanationMultiple FIXED or VARIABLE options were supplied onthe DIV statement HDRCTL= specification.

System actionThe first FIXED or VARIABLE option specified is used,and processing continues with this operand.

Programmer responseRemove the multiple FIXED or VARIABLE options fromthe HDRCTL= specification, and rerun the job.

DFS1827I SC=04 MULTIPLE HDRCTLNUMBER SPECIFICATIONSINVALID

ExplanationOnly one numeric-length specification is valid for theHDRCTL= keyword.

System actionThe first numeric-length specification is used, andprocessing continues with this operand.

Programmer responseSpecify only one numeric length on the HDRCTL=specification, and rerun the job.

DFS1828I SC=08 HDRCTL NUMBERTRUNCATED. LAST 2 DIGITS USED

ExplanationThe HDRCTL= specification length parameterexceeded 2 digits.

System actionOnly the last 2 digits are used, and processingcontinues with the next operand.

Programmer responseOmit the length specification or specify the HDRCTL=length you want, and rerun the job.

DFS1829I SC=08 NULL HDRCTL NUMBER.DEFAULT ASSUMED

ExplanationYou specified null for HDRCTL=.

System actionThe default of 7 is used, and processing continues withthis operand.

Programmer responseOmit the length specification or specify an appropriateHDRCTL= numeric length, and rerun the job.

DFS1830I SC=04 MULTIPLE SIM/NOSIM2SPECIFICATIONS IN OPTIONS=KEYWORD INVALID

ExplanationSIM or NOSIM2 was specified more than once in asingle OPTIONS= keyword.

System actionThe first SIM or NOSIM2 specification is used, andprocessing continues with this operand.


Programmer responseResolve the multiple SIM or NOSIM2 specificationconflict, and rerun the job.

DFS1831A SC=04 MULTIPLE operand/operand SPECIFICATIONS INOPTIONS= KEYWORD INVALID

ExplanationConflicting operands were specified in the OPTIONS=keyword.

System actionThe first operand specified by the user is used, andprocessing continues.

Programmer responseResolve the conflicting operands by selecting DNM orNODNM, or MSG, or both, DPAGE or PPAGE.

DFS1832I SC=08 RCDCTL= INVALID FORSPECIFIED DEVICE TYPE

ExplanationRCDCTL= is only valid for TYPE= DPM-A1 throughDPM-A10 on the DEV statement.

System actionThe RCDCTL= specification is ignored, and processingcontinues with the next operand.

Programmer responseCorrect the DEV.TYPE= statement or remove theRCDCTL= specification, and rerun the job.

DFS1833I SC=08 HDRCTL= INVALID FORSPECIFIED DEVICE TYPE

ExplanationHDRCTL= is only valid for TYPE= DPM-A1 throughDPM-A10 on the DEV statement.

System actionThe HDRCTL= specification is ignored, and processingcontinues with the next operand.

Programmer responseCorrect the DEV.TYPE= statement or remove theHDRCTL= specification, and rerun the job.

DFS1834I SC=08 keyword= INVALID FORSPECIFIED DEVICE TYPE

ExplanationThe keyword is not allowed for the device typespecified by the TYPE= operand in the DEV statement.

System actionThe keyword specification is ignored, and processingcontinues with the remaining keyword.

Programmer responseCorrect the DEV TYPE= specification or remove thiskeyword, and rerun the job.

DFS1835I SC=08 NULL= INVALID FORSPECIFIED DEVICE TYPE

ExplanationThe DIV statement NULL= specification is only valid forDEV TYPE=DPM-A1 through DPM-A10.

System actionThe NULL= specification is ignored, and processingcontinues with the next operand.

Programmer responseCorrect the DEV.TYPE= specification or remove theNULL= specification, and rerun the job.

DFS1836I SC=08 MSG/DPAGE/PPAGEPARAMETERS INVALID ONOPTIONS= KEYWORD FOR DIVTYPE=INPUT

ExplanationFor DIV TYPE=INPUT, the options MSG/DPAGE/PPAGEare invalid on the OPTIONS= keyword.

System actionThese options are ignored, and processing continueswith this operand.

Programmer responseRemove the MSG/DPAGE/PPAGE parameters fromthe OPTIONS= keyword or change the DIV TYPE toOUTPUT. Rerun the job.


DFS1837I SC=08 RCDCTL= INVALID FORDEV MODE=STREAM. RCDCTL=IGNORED

ExplanationThe DIV statement RCDCTL= specification was inconflict with DEV.MODE=STREAM.

System actionThe RCDCTL specification is ignored, and processingcontinues with the next operand.

Programmer responseResolve the RCDCTL= or DEV.MODE=STREAM conflict,and rerun the job.

DFS1838I SC=08 SPAN PARAMETERINVALID ON RCDCTL= KEYWORDFOR DIV TYPE=INPUT

ExplanationThe SPAN specification for the RCDCTL= keyword isonly valid for DIV TYPE=OUTPUT.

System actionThe SPAN parameter is ignored, and processingcontinues with the next operand.

Programmer responseResolve the SPAN or DIV TYPE=INPUT conflict, andrerun the job.

DFS1839I SC=08 keyword= INVALID FOR DIVTYPE=INPUT

ExplanationThe keyword is invalid in the DIV statement forTYPE=INPUT.

System actionThe keyword is ignored, and processing continues withthe remaining keywords.

Programmer responseRemove the invalid keyword from the statement, andrerun the job.

DFS1840I SC=08 HDRCTL NUMBER INVALID.DEFAULT ASSUMED

ExplanationThe length parameter of the HDRCTL= specificationwas not in the range of 7 to the RCDCTL length minusone.

System actionThe value of 7 is used, and processing continues withthe next operand.

Programmer responseSpecify a valid HDRCTL length parameter, and rerunthe job.

DFS1841I SC=08 NULL= INVALID FOR DIVTYPE=OUTPUT. NULL= IGNORED

ExplanationThe NULL= specification is only valid for DIVTYPE=INPUT.

System actionThe NULL= specification is ignored when used for DIVTYPE=OUTPUT. Processing continues with the nextoperand.

Programmer responseResolve the NULL= or DIV TYPE=OUTPUT conflict, andrerun the job.

DFS1842I SC=08 device-type IDENTIFIERDOES NOT BEGIN WITH A VALIDCHARACTER. type-A1 ASSUMED

ExplanationThe first character of the device type identifier wasspecified incorrectly in the TYPE= keyword of the DEVstatement.

System actionDPM-A1 or 3270-A1 is used as the device type, andprocessing continues with the next operand.

Programmer responseSpecify the wanted identifier, and rerun the job.

DFS1843I SC=08 LDEL=X'HEXSTRING',HEXSTRING LENGTH IS NOT 4.HEXSTRING PADDED ON RIGHTWITH 0'S


ExplanationThe LDEL= string was less than 4 hexadecimal digits.

System actionThe string is padded on the right with zeros to a lengthof 4 hexadecimal digits. Processing continues with thenext operand.

Programmer responseExpand the LDEL= string to 4 hexadecimal digits, andrerun the job.

DFS1844I SC=08 FTAB=X'HEXSTRING',HEXSTRING IS NULL. DEFAULTFTABS USED FOR APPLICABLEDEVICES

ExplanationA null hexadecimal string was supplied on the DEVstatement FTAB= specification. For a list of the devicetypes with default FTABs, see the "MFS Languageutility (DFSUPAA0)" topic.

System actionFTABs are assumed for applicable devices, andprocessing continues with the next operand.

Programmer responseSupply a valid FTAB specification, and rerun the job.

Related referenceMFS Language utility (DFSUPAA0) (SystemUtilities)

DFS1845I SC=04 RCD STATEMENTIS INVALID FOR DEVMODE=STREAM. RCD STATEMENTIGNORED

ExplanationYou cannot specify the RCD statement for STREAMmode.


Programmer responseRemove the RCD statement from the input stream orspecify RECORD mode. Rerun the job.

DFS1846I SC=08 HEXSTRING CONTAINSINVALID HEX DIGIT. HEX DIGITX'0' ASSUMED

ExplanationA string defined to be in hexadecimal digits containeda character other than A to F or 0 to 9.

System actionA zero is substituted for the invalid character, andprocessing continues with the next operand.

Programmer responseFind the invalid hexadecimal character on the string,specify a valid value, and rerun the job.

DFS1847I SC=08 SIM/NOSIM2 PARAMETERSINVALID ON OPTIONS= KEYWORDFOR DIV TYPE=INPUT

ExplanationThe options SIM/NOSIM2 are invalid on the DIVstatement OPTIONS= keyword for DIV TYPE=INPUT.

System actionThe SIM/NOSIM2 options are ignored, and processingcontinues with this operand.

Programmer responseRemove the SIM or NOSIM2 parameters from theOPTIONS keyword or change the DIV TYPE to OUTPUT.Rerun the job.

DFS1848I SC=08 DSCA=X'HEXSTRING',HEXSTRING IS NOT 4 HEX DIGITS.STRING PADDED ON RIGHT WITH0'S

ExplanationThe DSCA= keyword had fewer than 4 hexadecimaldigits specified. The specification is padded on theright with a hexadecimal zero to a length of 4hexadecimal digits.


Programmer responseSpecify 4 hexadecimal digits in the DSCA= operand,and rerun the job.


http://www.ibm.com/support/knowledgecenter/SSEPH2_15.1.0/com.ibm.ims15.doc.sur/ims_mfslang.htm#ims_mfslang

http://www.ibm.com/support/knowledgecenter/SSEPH2_15.1.0/com.ibm.ims15.doc.sur/ims_mfslang.htm#ims_mfslang

DFS1849E CHANGE NOT SUPPORTED BYALTER OPTION RS=rsnc PST=pstnoSEGMENT segmname

or

CHANGE NOT SUPPORTED BY ALTER OPTIONRS=rsnc PST=pstno SEGMENT segmname FIELDfld_name

ExplanationThe database definition (DBD) contains a change tothe database structure that cannot be applied to theonline database by using the ALTER option of theINITIATE OLREORG command.

In the message text:pstno

The program specification table (PST) number,relative to zero.

rsncThe reason code that identifies the DBD changethat is not supported by the ALTER option. See thefollowing list of reason codes for an explanation ofeach code.

segmnameThe name of the segment that contains theunsupported change.

fld_nameThe name of the field that contains theunsupported change.

Reason codeUnsupported change

1The access method of the database is changed. Forexample, the access method in use by the onlinedatabase is PHDAM, but the new DBD specifiesPHIDAM.

2The randomizer changed.

3The exit routine changed.

4The number of segments changed.

5The number of database data set groups changed.

6The length of a logical child or logical parentsegment changed.

7The segment level changed.

8The segment prefix changed.

9The segment changed from fixed-length tovariable-length or vice versa.

10The insert rule changed.

11The delete rule changed.

12The segment code changed.

13The length of the concatenated key changed.

14A logical relationship was added or changed.For example, changing the source segment of asecondary index is unsupported by the HALDBalter function.

15The segment length was decreased, which causedan existing field to be deleted.

16The field was deleted, moved to another segment,or its name was changed.

17The key length of the field changed.

18The field length changed.

19The value of the TYPE keyword on the FIELDstatement changed.

20The new field was added between existing fields inthe segment. The ALTER option can add new fieldsto a segment only after the existing fields.

21The parent of the segment changed.

22The segment length was decreased.

System actionThe ALTER operation terminates.

System programmer responseThe ALTER option cannot be used to apply the changeindicated by the reason code.


If the unsupported change is required, you can applyit to the database by taking the database offline andunloading and reloading it.

If the unsupported change is not required andyou need to continue to use the ALTER option toapply other changes to the database, remove theunsupported change from the database definition,regenerate the DBD and ACB library members, andissue the INITIATE OLREORG OPTION(ALTER)command again.

Module:DFS5DBB0

Related tasksAltering the definition of an online HALDBdatabase (Database Administration)Related referenceINITIATE OLREORG command (Commands)

DFS1850I SC=04 NULL DEVCHAR SUFFIX.DEVCHAR TABLE DFSUDT00 USED

ExplanationNo suffix was specified on the DEVCHAR= parameterof the EXEC statement.

System actionThe name of the device characteristic table that will beloaded is DFSUDT00.

Programmer responseSpecify a valid single alphanumeric suffix for theDEVCHAR= parameter on the EXEC statement, andrerun the job.


http://www.ibm.com/support/knowledgecenter/SSEPH2_15.1.0/com.ibm.ims15.doc.dag/ims_db_alter.htm#ims_dbalter


http://www.ibm.com/support/knowledgecenter/SSEPH2_15.1.0/com.ibm.ims15.doc.cr/imscmds/ims_initiateolreorg.htm#ims_cr1initiateolreorg



DFS1851I SC=04 DEVCHAR SUFFIX'suffix' TRUNCATED TO FIRSTCHARACTER

ExplanationMore than 1 character was specified on the DEVCHAR=parameter of the EXEC statement. The messagedisplays up to 8 of the characters that were present.

System actionOnly the first character is used as the 1 charactersuffix for the device characteristics table name.

Programmer responseSpecify a valid single alphanumeric suffix for theDEVCHAR= parameter on the EXEC statement, andrerun the job.

DFS1852W THE CATALOG PSB DFSCP000IS UNSCHEDULABLE ERRORCODE=xx

ExplanationIMS failed to build the application control blocks forthe catalog PSB DFSCP000, so the PSB can no longerbe scheduled.Error code

Explanation1

BLDL macro call for PSB DFSCP000 failed or theDFSCP000 member does not exist in the activeACB library.

2The DFSCP000 member exists in the active ACBlibrary, but the active member is not a PSB.

3The active version of the PSB DFSCP000 memberis not compatible with this version of IMS.

4The intent list of PSB DFSCP000 could not be readfrom the ACB library during IMS initialization.

5The catalog control blocks cannot be built becausethe program or database directory blocks could notbe created during IMS initialization.

8The catalog application control blocks cannot bebuilt because storage could not be obtained.

9The intent list of PSB DFSCP000 could not be readfrom the ACB library after an online change wascommitted.

10The catalog application control blocks cannot bebuilt because storage could not be obtained duringthe commit phase of an online change.

11The catalog application control blocks cannot bebuilt because the program or database directoryblocks could not be created during the commitphase of an online change.

12IMS failed to load the DFSXRBB0 module duringthe commit phase of an online change.

13The online change process failed to make DMBDFSCD000 or DFSCX000 resident.

14The online change process failed to make theintent list of PSB DFSCP000 resident.

15The online change process failed to make PSBDFSCP000 resident.

System action:The catalog PSB DFSCP000 cannot be scheduled. If anapplication program issues a DLI call for DFSCAT00,the catalog PCB, the required dynamic attachment ofDFSCP000 fails with a U0253 abend. If the applicationattempts to directly schedule DFSCP000, a U0456abend occurs.

System programmer response:For error codes 1, 2, 3, 4, 5, 9, 13, 14, and 15, performan ACBGEN with BUILD PSB=DFSCP000. For the othererror codes, resolve the underlying error.

DFS1853I ACBSHR = Y, SET USING CSLACBSHR VALUE

or

ACBSHR = N, SET USING CSL ACBSHR VALUE


or

ACBSHR = Y, SET USING CSL DEFAULT VALUE

or

ACBSHR = Y, SET AS THE DEFAULT VALUE

ExplanationIf the Common Service Layer (CSL) is used, during IMSinitialization, this message shows the source and theACBSHR value.

If the CSL is not used during IMS initialization, thefollowing message is issued when ACBSHR=Y is set asthe default ACBSHR value for <SECTION=FASTPATH>:ACBSHR = Y, SET AS THE DEFAULT VALUE.



Module:DBFFATC1

DFS1854I SC=08 VERSID LENGTH INVALID,X'hhhh' USED

ExplanationThe hexadecimal specification for version ID waseither less than, or greater than, 4 hexadecimalcharacters.

System actionThe 4 hexadecimal characters presented in theX'hhhh' part of the message are used for the versionID. If the specification is more than 4 hexadecimalcharacters, the first 4 specified are used. If thespecification is less than 4 characters, the value ispadded on the right with zeros to a length of 4characters.

Programmer responseCorrect the version ID specification by using exactly 4hexadecimal characters, and rerun the job.

DFS1855I SC=08 VERSID LENGTH INVALID,'cc' USED

ExplanationThe specification for version ID was either less than orgreater than 2 characters.

System actionThe 2 characters (cc) presented in the message areused for the version ID. If less than 2 characters arespecified, blanks are added. If more than 2 charactersare specified, the first 2 characters are used.

Programmer responseCorrect the version ID specification by using exactly 2characters and rerun the job.

DFS1856I SC=04 PF KEY NUMBER'nnnnnnnn' IS NOT AVALID INTEGER. SUBPARAMETERIGNORED

ExplanationThe specified PF key number was not a number from 1to 36.

System actionThis invalid PF key number and its operandare ignored. Processing continues without thissubparameter.

Programmer responseSpecify a PF key number from 1 to 36, and rerun thejob.

DFS1857I SC=04 PF KEY NUMBER 'nn' ISA DUPLICATE NUMBER AND ISIGNORED

ExplanationThe PF key number on this subparameter has beenpreviously specified.

System actionThe first specification is used, and processingcontinues with this subparameter.

Programmer responseCorrect the duplicate specification, and rerun the job.

DFS1858I SC=08 DEVCHAR TABLEDFSUDT0x NOT FOUND.DFSUDT00 USED


ExplanationThe member named in the message was not found inIMS.SDFSRESL.

System actionAn attempt is made to find DFSUDT00 and processingcontinues.

Programmer responseSpecify a device characteristics table suffix that agreeswith the member in the IMS.SDFSRESL, and rerun thejob.

DFS1859I SC=08 DEVCHAR TABLEDFSUDT00 NOT FOUND. NO TABLELOADED

ExplanationThe device characteristics table DFSUDT00 was notfound in IMS.SDFSRESL.

System actionThe system issues message DFS1861I, assumesan IBM 3270 model 2 device type, and continuesprocessing.

Programmer responseSpecify a device characteristics table suffix thatidentifies the desired member in IMS.SDFSRESLbefore using the symbolic device type 3270-An on theDEV statement.

Related information“DFS1861I” on page 541SC=08 DEVCHAR TABLE NOT LOADED. 3270ASSUMED

DFS1860I SC=08 PERMANENT I/O ERRORREADING SDFSRESL DIRECTORYFOR DEVCHAR TABLE. NO TABLEUSED

ExplanationThe BLDL macro returned a return code of 08,indicating a permanent input/output error wasdetected when the system attempted to search thedirectory.

System actionThe system issue message DFS1861I, assumes a3270 model 2 device type, and continues processing.


Related referencez/OS: BLDL completion codesRelated information“DFS1861I” on page 541SC=08 DEVCHAR TABLE NOT LOADED. 3270ASSUMED“IMS problem determination” on page 11IMS messages and codes problemdetermination is accomplished by usingprocedures established by IBM.

DFS1861I SC=08 DEVCHAR TABLE NOTLOADED. 3270 ASSUMED

ExplanationThe device characteristics table was not loaded. Errormessage DFS1859I or DFS1860I should precede thismessage.

System actionA 3270 model 2 device type is assumed, andprocessing continues.

Programmer responseCorrect the cause of message DFS1859I or DFS1860I,and rerun the job.

Related information“DFS1859I” on page 541SC=08 DEVCHAR TABLE DFSUDT00 NOTFOUND. NO TABLE LOADED“DFS1860I” on page 541SC=08 PERMANENT I/O ERROR READINGSDFSRESL DIRECTORY FOR DEVCHAR TABLE.NO TABLE USED

DFS1862I SC=08 3270-An DEVICE TYPE NOTFOUND IN THE DEVCHAR TABLE.3270 ASSUMED

ExplanationThe device type symbolic name, mentioned in themessage, was not found in the device characteristicstable that was loaded.

System actionA 3270 model 2 device type is assumed, andprocessing continues.



Programmer responseEnsure that the correct suffixed device characteristicstable was used, and that the symbolic name used inthe system definition is the same name used on theDEV statement. Correct any errors, and rerun the job.

DFS1863I SC=04 DEVICE FEATURESSPECIFIED NOT FOUND INDEVCHAR TABLE

ExplanationThe loaded device characteristics table did not have anentry for the symbolic name specified on the TYPE=keyword of the DEV statement with the same featuresthat were specified on the FEAT= operand of the DEVstatement.

System actionThe system uses the features that are specified orassumed for the DEV statement, rather than thosefound in the device characteristics table entry.

Programmer responseThe format for this symbolic device type and featureswill not be referenced in an online system becausethere will be no defined device and features thatmatch. Correct any errors, and rerun the job.

DFS1864I SC=04 RCDCTL=SPAN IS INVALIDFOR DPM-Bn

ExplanationRCDCTL=SPAN is not allowed when TYPE=DPM-Bn isspecified on the DEV statement.

System actionThe SPAN specification is ignored, and processingcontinues with the next operand.

Programmer responseChange the SPAN specification to NOSPAN, remove itfrom the RCDCTL= operand, or change the device typespecification, and rerun the job.

DFS1865I SC=08 PPAGE OPTION INVALIDON OPTIONS= KEYWORD FOR DIVTYPE=INPUT

ExplanationFor DIV TYPE=INPUT, the option PPAGE is invalid onthe OPTIONS= keyword.

System actionThe PPAGE option is ignored, and processingcontinues with this operand.

Programmer responseRemove PPAGE from the OPTIONS= keyword orchange the DIV TYPE to OUTPUT. Rerun the job.

DFS1866I SC=04 RDPN=DFLDNAMETRUNCATED TO 'cccccccc'

ExplanationThe return destination process name (dfldname) wasgreater than 8 characters.

System actionOnly the first 8 characters of the dfldname are used,and processing continues with this operand.

Programmer responseProvide a dfldname with no more than 8 characters,and rerun the job.

DFS1867I SC=08 name= 'LITERAL' INVALIDFOR DIV TYPE=INPUT

ExplanationEither the destination process name (DPN) or theprimary resource name (PRN) literal was not validwhen DIV TYPE=INPUT is specified.

System actionThe literal specification is ignored, and processingcontinues with the next operand.

Programmer responseRemove the literal specification or change DIV TYPE toOUTPUT.

DFS1868I SC=04 DPN='LITERAL'TRUNCATED TO 'cccccccc'

ExplanationThe destination process name literal was greater than8 characters.

System actionOnly the first 8 characters of the literal are used, andprocessing continues with this operand.


Programmer responseProvide a literal with no more than 8 characters, andrerun the job.

DFS1869I SC=04 DPN=DFLDNAMETRUNCATED TO 'cccccccc'

ExplanationThe destination process name (dfldname) was greaterthan 8 characters.



DFS1870I SC=04 PRN='LITERAL'TRUNCATED TO 'cccccccc'

ExplanationThe primary resource name (PRN) literal was greaterthan 8 characters.



DFS1871I SC=04 PRN=DFLDNAMETRUNCATED TO 'cccccccc'

ExplanationThe primary resource name (dfldname) was greaterthan 8 characters.



DFS1872I SC=04 RPRN='LITERAL'TRUNCATED TO 'cccccccc'

ExplanationThe return primary resource name (RPRN) literal wasgreater than 8 characters.



DFS1873I SC=04 RPRN=DFLDNAMETRUNCATED TO 'cccccccc'

ExplanationThe return primary resource name (dfldname) literalwas greater than 8 characters.



DFS1874I SC=08 name='LITERAL', NOTSPECIFIED OR ZERO LENGTH ' 'USED

ExplanationThe destination process name (DPN), the primaryresource name (PRN), or the return primary resourcename (RPRN) literal was null.

System actionA single blank is used as the literal, and processingcontinues with the next operand.

Programmer responseSpecify the appropriate literal, and rerun the job.

DFS1875I SC=08 name=DFLDNAME,DFLDNAME HAS NO CHARACTERSAND IS IGNORED


ExplanationThe destination process name (DPN), the primaryresource name (PRN), or the return primary resourcename (RPRN) dfldname specification was a null value.

System actionThe dfldname specification is ignored, and processingcontinues with the next operand.

Programmer responseSpecify the appropriate dfldname, and rerun the job.

DFS1876I SC=08 OFTAB LENGTH INVALID,X'hh' USED

ExplanationThe output field tab separator was not 2 hexadecimalcharacters in length.

System actionIf more than 2 hexadecimal characters are specified,the first 2 hexadecimal characters specified are used,and processing continues with the operand. If nohexadecimal characters are specified, then X'00' isused.

Programmer responseSpecify exactly 2 hexadecimal characters for outputfield tab separator character, and rerun the job.

DFS1877I SC=08 OFTAB LENGTH INVALID,C'c' USED

ExplanationThe output field tab separator was not 1 character.

System actionIf no valid character is specified, a comma is used.If more than one character is specified, the firstcharacter specified is used.

Programmer responseSpecify exactly one character as the output field tabseparator character, and rerun the job.

DFS1878I SC=08 OFTAB CHARACTERX'hh' INVALID, SPECIFICATIONIGNORED

ExplanationThe output field tab separator character was specifiedas either X'hh' or C'c' cannot be an X'3F' or a blankcharacter.

System actionThe specification is ignored, and processing continueswith the next operand.

Programmer responseProvide a valid character for the output field tabseparator, and rerun the job.

DFS1879I SC=04 keyword= SPECIFICATIONIGNORED

ExplanationThe specified keyword was in conflict with otherspecifications and is ignored.


Programmer responseIf the other parameters are correct, remove thiskeyword, and rerun the job.

DFS1880I SC=08 EGCS LITERAL STRINGINVALID

ExplanationA literal expressed as an extended graphic characterset (EGCS) literal was specified for a normal literal.The MFS design does not allow an EGCS literal for thisfunction.

System actionThe EGCS literal is ignored and processing continueswith the next operand.

Programmer responseSpecify the literal as a non-EGCS literal and rerun thejob.

Problem determinationNot applicable

DFS1881I SC=04 EGCS LITERAL CONTAINSAN ODD NUMBER OF BYTES


ExplanationThis warning message indicates that some devicesrequire that extended graphic character set (EGCS)data be an even number of bytes.

System actionThe EGCS literal is accepted unchanged andprocessing continues.

Programmer responseEnsure that the EGCS literal contains the correctnumber of bytes, and rerun the job, if required.

DFS1882I SC=08 ATTR=nn VALUE INVALID, 1USED

ExplanationThe value specified for the number of extendedattributes to be dynamically modifiable was not anumber in the range from 1 to 4.

System actionThe value of 1 is used and processing continues withthis operand.

Programmer responseSpecify the extended attribute value as a number inthe range from 1 to 4 and rerun the job.

DFS1883I SC=04 PS VALUE IGNORED

ExplanationFor device type SCS1, the extended graphic characterset (EGCS) attribute does not use a programmedsymbol value.

System actionMFS assumes a specification of EGCS, ignores theprogrammed symbol value, and continues processing.

Programmer responseSpecify the EGCS attribute as EGCS without aprogrammed symbol value and rerun the job.


DFS1884I SC=08 PS SPECIFICATIONINVALID WITH EGCS LITERAL,EGCS'F8' USED

ExplanationA programmed symbol attribute of PX'hh' or PC'c' wasspecified along with an extended graphic character set(EGCS) literal. An EGCS attribute was expected. For anSCS1 device type, the 'F8' will not be present in thecontrol block.

System actionFor 3270 devices, the extended attribute is changedto EGCS'F8'. For an SCS1 device type, the extendedattribute is changed to EGCS. Processing continues.

Programmer responseSpecify the extended attribute as EGCS'hh' (for EGCS,for SCS1) or specify the literal as a non-EGCS literal,and rerun the job.


DFS1885I SC=08 EGCS EXTENDEDATTRIBUTE IGNORED

ExplanationAn extended attribute of EGCS'hh' or EGCS wasspecified along with a non-EGCS literal.

System actionThe EGCS extended attribute is ignored. Anyprogrammed symbol value is reset, and processingcontinues.

Programmer responseSpecify the programmed symbol attribute as PX'hh' orPC'c' or change the literal specification to an EGCSliteral, and rerun the job.

DFS1886I SVC message

ExplanationOne or more of the following informational SVCmessages can be issued:DYNAMIC UPDATE OF IMS TYPE 2 SVC = STARTED

The utility has begun to update the IMS Type 2SVC. No response or action is required.

IMS TYPE 2 SVC NUMBER = xxxThe utility has identified the IMS Type 2 SVCnumber in the data set pointed to by theDFSRESLB DD card. Make note of this numberand ensure that it corresponds to the number


anticipated by the system administrator. Noresponse or action is required.

IMS TYPE 2 SVC DYNAMIC UPDATE = SUCCESSFULThe utility has successfully changed the entry inthe MVS SVC table to point to the new IMS Type 2SVC module. No response or action is required.

DYNAMIC UPDATE OF DBRC TYPE 4 SVC = STARTEDThe utility has begun to update the DBRC Type 4SVC. No response or action is required.

DBRC TYPE 4 SVC NUMBER =xxxThe utility has identified the DBRC Type 4SVC number in the data set pointed to by theDFSRESLB DD card. Make note of this numberand ensure that it corresponds to the numberanticipated by the system administrator. Noresponse or action is required.

DBRC TYPE 4 SVC DYNAMIC UPDATE = SUCCESSFULThe utility has successfully changed the entry inthe MVS SVC table to point to the new DBRC Type4 SVC module. No response or action is required.

DFS1886E SVC message

ExplanationOne or more of the following error SVC messages canbe issued:IMS TYPE 2 SVC DYNAMIC UPDATE = FAILED - RC xx

The utility has failed while updating the IMS Type2 SVC. Depending on the error, this messagemight be accompanied by another DFS1886E errormessage or a DFS1886A operator action message.Reason code xx is one of the following:Reason code

Explanation4

Open of DFSRESLB library failed.8

DFSRESLB library not APF authorized.12

DFSRESLB library does not contain moduleDFSVC000.

16DFSRESLB library does not contain moduleIGCxxx, where xxx = IMS Type 2 SVC number.

20Reply to WTOR was "NO" for message"DFS1886A MVS SVC TABLE ENTRY = EMPTY."

24Reply to WTOR was "NO" for message"DFS1886A MVS SVC TABLE ENTRY = ACTIVESVC THAT IS NOT AN IMS SVC."

28Reply to WTOR was "NO" for message"DFS1886A MVS SVC TABLE ENTRY = IMS SVCAT HIGHER RELEASE THAN RESLIB SVC."

32There is currently an active IMS using the SVCnumber specified in the IMS RESLIB.

36Nonzero return code from MVS SVC tableupdate services (see WTO for z/OS returncode).

56An invalid value was specified for the SVCTYPE= input parameter.

DBRC TYPE 4 SVC DYNAMIC UPDATE = FAILED - RC= xx

The utility has failed while updating the DBRCType 4 SVC. Depending on the error, this messagemight be accompanied by another DFS1886E errormessage or a DFS1886A operator action message.Reason code xx is one of the following:Reason code

Explanation4

Open of DFSRESLB library failed.8

DSRESLB library not APF authorized.20

Reply to WTOR was "NO" for message"DFS1886A MVS SVC TABLE ENTRY = EMPTY."

36Nonzero return code from MVS SVC tableupdate services (see WTO for z/OS returncode).

40DFSRESLB library does not contain moduleDSPSVC00.

44DFSRESLB library does not contain moduleIGC00xxx, where xxx is the signed decimal SVCnumber for the DBRC Type 4 SVC.

48Reply to WTOR was "NO" for message"DFS1886A MVS SVC TABLE ENTRY = ACTIVESVC THAT IS NOT A DBRC SVC."

52Reply to WTOR was "NO" for message"DFS1886A MVS SVC TABLE ENTRY = DBRCSVC AT HIGHER RELEASE THAN RESLIB SVC."

56An invalid value was specified for theSVCTYPE= input parameter.


DATA SET OPEN FAILED - SEE DFSRESLB DD CARDThere was a problem opening the data set pointedto by the DFSRESLB DD card. The utility terminateswith RC=0004. Resolve the problem with the dataset and resubmit the utility job.

DATA SET APF AUTHORIZATION FAILED - SEEDFSRESLB DD CARD

The RESLIB specified on the DFSRESLB DD cardis not APF authorized. The utility terminates withRC=0008. The RESLIB must be APF authorizedin order for the utility to run successfully. Ensurethat the DFSRESLB DD card is pointing to thecorrect data sets and that those data sets are APFauthorized.

MODULE DFSVC000 NOT FOUND - SEE DFSRESLBDD CARD

The secondary SCD (DFSVC000) cannot belocated. The utility terminates with RC=0012. TheIMS RESLIB contains the SSCD. Ensure that theDFSRESLB DD card is pointing to the correct datasets and resubmit the job.

MODULE xxxxxxxx NOT FOUND - SEE DFSRESLB DDCARD

xxxxxxxx is the name of the SVC module beingupdated. If the IMS Type 2 SVC is being updated,the module name is IGCxxx, where xxx is the IMSType 2 SVC number. If the DBRC Type 4 SVC isbeing updated, the module name is IGC00xxx,where xxx is the signed decimal SVC number forthe DBRC Type 4 SVC. The utility terminates withRC=0016 or RC=0044. The IMS RESLIB data setsshould contain the SVC modules. Ensure that theDFSRESLB DD card is pointing to the correct datasets and resubmit the job.

MVS SVC TABLE ENTRY WAS EMPTY - WTOR REPLYWAS NO

The MVS SVC table entry for the SVC was empty.There is a DFS1886A message preceding thismessage to which the operator replied "NO." Ifthe operator did not expect the entry to be empty,this reply is probably correct. The utility terminateswith RC=0020. Ensure that the correct IMS RESLIBdata sets are specified and resubmit the job. Thisis an unusual condition, unless you are expectingthis SVC entry to be empty. You might want toconsult your system administrator if this situationoccurs.

MVS SVC TABLE CONTAINS AN ACTIVE SVC THAT ISNOT AN IMS SVC

The MVS SVC table entry contains an active SVCthat is not an IMS SVC. The utility issues a WTORmessage to allow you to decide what to do.Ensure that the correct IMS RESLIB data sets arespecified and that the SVC number returned inthe previous "DFS1886I IMS TYPE 2 SVC NUMBER

= xxx" message or the "DFS1886I DBRC TYPE 4SVC NUMBER = xxx" message is correct. If youdo not wish to continue, reply "NO" to the WTORmessage. If you decide to continue, reply "YES"to the WTOR. See your system administrator todetermine the correct course of action.

IMS RELEASE LEVELS INCONSISTENT - RESLIB SVCIS AT A LOWER LEVEL THAN CURRENT SVC

The MVS SVC table entry points to a newer versionof the SVC than is found in the IMS RESLIB datasets. The utility issues a WTOR message to allowyou to decide what to do. Ensure that the correctIMS RESLIB data sets are specified. If you donot wish to continue, reply "NO" to the WTORmessage. If you decide to continue, reply "YES"to the WTOR. See your system administrator todetermine the correct course of action.

THERE IS CURRENTLY AN ACTIVE IMS USING THESAME SVC NUMBER

One or more IMS control regions are currentlyrunning and referencing the IMS Type 2 SVC. Theutility terminates with RC=0032. You must waituntil the currently active IMS control regions canbe scheduled to be brought down. At that time,resubmit the job.

MVS SVC TABLE UPDATE SERVICES FAILED - RC=xxA non-zero return code was returned from the MVSSVC Update service (SVCUPDTE). xx is the returncode. See the SVCUPDTE macro for return codeexplanations.

MODULE DSPSVC00 NOT FOUND - SEE DFSRESLBDD CARD

Module DSPSVC00, which contains the DBRCType 4 SVC number, cannot be located. Theutility terminates with RC=0040. The IMS RESLIBcontains module DSPSVC00. Ensure that theDFSRESLB DD card is pointing to the correct datasets and resubmit the job.

MVS SVC TABLE CONTAINS AN ACTIVE SVC THAT ISNOT A DBRC SVC

The MVS SVC table entry contains an active SVCthat is not a DBRC SVC. The utility issues a WTORmessage to allow you to decide what to do. Ensurethat the correct IMS RESLIB data sets are specifiedand that the SVC number returned in the previous"DFS1886I DBRC TYPE 4 SVC NUMBER = xxx"message is correct. If you do not wish to continue,reply "NO" to the WTOR message. If you decideto continue, reply "YES" to the WTOR. See yoursystem administrator to determine the correctcourse of action.

INVALID VALUE SPECIFIED FOR SVCTYPE= INPUTPARAMETER

An invalid value was specified for the SVCTYPE=input parameter. The utility terminates with


RC=0056. Resolve the problem with the inputparameter and resubmit the utility job.

Related information“DFS1886I” on page 545SVC message“DFS1886A” on page 548SVC message

DFS1886A SVC message

ExplanationOne or more of the following SVC messages can beissued. The operator should take the actions includedbelow:

MVS SVC TABLE ENTRY = EMPTY - DO YOU WISH TOCONTINUE? (YES or NO)

This is an unusual condition. Ensure that thecorrect IMS RESLIB data sets were specified. Youmight want to consult your system administratorif this situation occurs. To respond to the WTORmessage, enter REPLY xx,yyy from the z/OSoperator console, where:xx

WTOR number.yyy

The character string YES or NO:NO

The utility terminates abnormally withRC=0020.

YESThe utility continues and uses the emptyentry.

MVS SVC TABLE ENTRY = ACTIVE SVC THAT IS NOTAN IMS SVC - DO YOU WISH TO CONTINUE? (YESOR NO)

The MVS SVC table entry contains an active SVCthat is not an IMS SVC. Ensure that the correct IMSRESLIB data sets are specified. To respond to theWTOR message, enter REPLY xx,yyy from thez/OS operator console, where:xx

WTOR number.yyy



YESThe utility continues and reuses the MVSSVC table entry.

This is an unusual condition. Unless you areexpecting to reuse an SVC entry that is no longerneeded, you should respond with a reply of NO.See your system administrator for the correctcourse of action.

MVS SVC TABLE ENTRY = IMS SVC AT HIGHERRELEASE THAN RESLIB SVC - DO YOU WISH TOCONTINUE? (YES OR NO)

The MVS SVC table entry points to a newer versionof the SVC than is found in the IMS RESLIB datasets. Ensure that the correct IMS RESLIB datasets are specified. If you do not wish to continue,reply NO to the WTOR message. If you decide tocontinue, reply YES to the WTOR. See your systemadministrator to determine the correct course ofaction.

To respond to the WTOR message, enter REPLYxx,yyy from the z/OS operator console, where:xx

WTOR number.yyy



YESThe utility continues and uses an olderversion of the SVC.

MVS SVC TABLE ENTRY = ACTIVE SVC THAT IS NOTA DBRC SVC - DO YOU WISH TO CONTINUE? (YESOR NO)

The MVS SVC table entry contains an active SVCthat is not a DBRC SVC. Ensure that the correctIMS RESLIB data sets are specified. To respondto the WTOR message, enter REPLY xx,yyy fromthe z/OS operator console, where:xx

WTOR number.yyy



YESThe utility continues and reuses the MVSSVC table entry.

This is an unusual condition. Unless you areexpecting to reuse an SVC entry that is no longerneeded, you should respond with a reply of NO.See your system administrator for the correctcourse of action.


MVS SVC TABLE ENTRY = DBRC SVC AT HIGHERRELEASE THAN RESLIB SVC - DO YOU WISH TOCONTINUE? (YES OR NO)

The MVS SVC table entry points to a newer versionof the DBRC SVC than is found in the IMS RESLIBdata sets. Ensure that the correct IMS RESLIB datasets are specified. If you do not wish to continue,reply NO to the WTOR message. If you decide tocontinue, reply YES to the WTOR. See your systemadministrator to determine the correct course ofaction.

To respond to the WTOR message, enter REPLYxx,yyy from the z/OS operator console, where:xx

WTOR number.yyy



YESThe utility continues and uses an olderversion of the SVC.

DFS1887I SC=04 DPAGE FILL= IN CONFLICTWITH EGCS ATTRIBUTE

ExplanationThe FILL= specification on the DPAGE statementcaused an error indication from the terminal for EGCSfields that contain no data.


Programmer responseEnsure that this DFLD always has some data mappedto it, or specify FILL= PT or NULL on the DPAGEstatement, and rerun the job.

DFS1888I SC=04 EGCS FIELD LENGTH NOTEVEN

ExplanationSome devices require that extended graphic characterset (EGCS) data be an even number of bytes.

System actionThe field length is accepted as is, and processingcontinues.

Programmer responseEnsure that the field length is specified correctly orthat the EGCS literal contains the correct number ofbytes, and rerun the job.

DFS1889I SC=08 EGCS VALUE INVALID,EGCS'F8' USED

ExplanationThe programmed symbol value specified for theextended graphic character set (EGCS) attribute is notspecified as X'hh', the value is not an X'00', or in therange from X'40' through X'FE'.

System actionThe default value of EGCS'F8' is used, and processingcontinues with the next operand.

Programmer responseSpecify the EGCS attribute as EGCS, EGCS'00'EGCS'hh', where 'hh' is a valid value (normally 'F8'),and rerun the job.

DFS1890I SC=08 LINE DENSITYSPECIFICATION IS GREATERTHAN 72

ExplanationThe value specified for SLDI/SLDP was greater than72.

System actionThe SLDI/SLDP is reset, and processing continues withthe next operand.

Programmer responseSpecify a value for SLDI/SLDP from 1 to 72, and rerunthe job.

Severity:8

DFS1891I SC=08 LINE DENSITYSPECIFICATION EQUAL TO ZERO

ExplanationThe value specified for SLDI/SLDP equaled zero.

System actionThe SLDI/SLDP is reset, and processing continues withthe next operand.


Programmer responseSpecify a value for SLDI/SLDP from 1 to 72, and rerunthe job.

Severity:8

DFS1892I SC=04 LINE DENSITYSPECIFICATION IS INVALIDBETWEEN DO AND ENDDO

ExplanationThe SLDI/SLDP specification was invalid on a DFLDstatement between DO and ENDDO statements.

System actionThe SLDI/SLDP is reset and processing continues withthe next operand.

Programmer responseRemove the SLDI/SLDP specification from the DFLDstatement between DO and ENDDO. If a line densityis required, the DEV statement or a DFLD statementbefore the DO statement should be used.

Severity:4

DFS1893I SC=08 TOP MARGIN SPECIFIED ISLESS THAN 1

ExplanationThe value specified for top margin in the VTAB=keyword was less than 1.

System actionThe top margin is set to 1 and processing continueswith the next operand.

Programmer responseChange the value of top margin in VTAB= keyword to avalue equal to or greater than 1, and two less than thebottom margin value. Rerun the job.

Severity:8

DFS1894I SC=08 TOP MARGIN IS GREATERTHAN 253

ExplanationThe value specified for top margin in the VTAB=keyword was greater than 253.


Programmer responseChange the value of top margin in VTAB= keyword to avalue from 1 to 253 and rerun the job.

Severity:8

DFS1895I SC=08 BOTTOM MARGIN IS LESSTHAN 3.

ExplanationThe value specified for bottom margin in the VTAB=keyword was less than 3.

System actionThe bottom margin is set to the number of lines perpage on the PAGE= keyword, and processing continueswith the next operand.

Programmer responseChange the bottom margin value in the VTAB= keywordto a value from 3 to 255, and rerun the job.

Severity:8

DFS1896I SC=08 BOTTOM MARGIN ISGREATER THAN PAGE=

ExplanationThe value specified for bottom margin in the VTAB=keyword was larger than the number of lines per pagespecified in the PAGE= keyword. The bottom marginmust be two larger than the top margin and equal to orless than PAGE=.

System actionThe bottom margin is set to PAGE= value, andprocessing continues with the next operand.

Programmer responseChange the bottom margin value or the PAGE= valueso that the bottom margin is equal to or less than thePAGE= value. Rerun the job.

Severity:8


DFS1897I SC=08 VTAB= SPECIFIED ANDLINES PER PAGE LESS THAN 3.

ExplanationVTAB= was specified when the lines per pagespecification for the PAGE= keyword has a value lessthan 3.

System actionThe bottom margin is set to the maximum linesper page value from the PAGE= specification, andprocessing continues with the next operand.

Programmer responseChange the bottom margin value in the VTAB= keywordto a value from 3 to 255, and rerun the job.

Severity:8

DFS1898I SC=08 BOTTOM MARGIN IS LESSTHAN LARGEST VERTICAL TABSTOP

ExplanationThe bottom margin was less than the largest verticaltab (VT) specified.

System actionThe (VT) is set to zero and processing continues withthe next operand.

Programmer responseChange the bottom margin value in the VTAB= keywordor the VT= (,,,) values so that the bottom margin isgreater than or equal to the largest VT= specification.If the bottom margin was not specified, the PAGE=lines per page value might have to be changed.

Severity:8

DFS1899I SC=08 TOP MARGIN IS EQUALTO OR GREATER THAN LOWESTNONZERO VERTICAL TAB STOP

ExplanationThe top margin was equal to or greater than the lowestnonzero (VT) specified.

System actionThe (VT) is set to zero, and processing continues withthe next operand.

Programmer responseChange the top margin value in the VTAB= keyword orVT= specifications so that the top margin is smallerthan all nonzero VT= specifications.

Severity:8

DFS1900I SC=08 DUPLICATE VERTICAL TABSTOP(S) SET TO ZERO

ExplanationThe tab stop values in the VT= keyword must bedistinct or zero if VTAB= is specified.

System actionRepeated occurrences of tab stop values are set tozero, and processing continues with the next operand.

Programmer responseNonzero vertical tabs must be unique. Changeduplicate nonzero vertical tabs to unique valuesbetween top margin and bottom margin, and rerun thejob.

Severity:8




DFS1901I SC=08 TOP MARGIN IS NOT TWOLESS THAN BOTTOM MARGIN

ExplanationThe top margin specified in the VTAB= keyword wasnot two less than the bottom margin.


Programmer responseChange the top margin or the bottom margin on theVTAB= keyword so that the top margin plus 1 is lessthan the bottom margin.

Severity:8

DFS1902I SC=08 WIDTH SPECIFIED INFEAT= AND WIDTH= INVALID

ExplanationSpecification of a width value in both FEAT= andWIDTH= keywords for the DEV statement is invalid.

System actionThe WIDTH= keyword is ignored.

Programmer responseDEV statement should be corrected to a validspecification of either of the following values:

• FEAT=120, 126, or 132 without WIDTH=,• FEAT=1-10, WIDTH=nnn,

Then rerun the job.

Severity:8

DFS1903I SC=08 (keyword=,keyword=)KEYWORDS ARE MUTUALLYEXCLUSIVE

ExplanationThe two identified keywords specified in the DEVstatement are mutually exclusive.

System actionThe first keyword is accepted; the second keyword isignored. Processing continues with the next keyword.

Programmer responseRespecify only one of the two identified keywords, andrerun the job.

Severity:8

DFS1904I SC=04 (keyword=) SPECIFIEDWITH NULL VALUE

ExplanationThe displayed keyword was specified without a value.

System actionThe identified keyword is ignored, and processingcontinues with the next operand.

Programmer responseSpecify the identified keyword, and rerun the job.

Severity:4

DFS1905I SC=08 (SLDI/SLDP=) nnTRUNCATED TO LAST 2 DIGITS

ExplanationThe SLDI= or SLDP= keyword specified a value that islonger than 2 digits.

System actionThe last 2 digits of the set line density (SLD)specification are used, and processing continues withthe next operand.


Programmer responseRespecify an SLD value of 1 or 2 digits, and rerun thejob.

Severity:8

DFS1906I SC=08 VTAB= TOP MARGIN VALUETRUNCATED TO LAST 3 DIGITS

ExplanationThe VTAB= top margin value on the DEV statementexceeded 3 digits.

System actionThe last 3 digits of the top margin value are used.The left-most digits are truncated and processingcontinues with the next operand.

Programmer responseRespecify the identified keyword, and rerun the job.

Severity:8

DFS1907I SC=04 NULL TOP MARGIN VALUEWILL BE SET TO 1, THE DEFAULTVALUE

ExplanationVTAB= was specified with no top margin specificationand the default value of 1 is used.

System actionThe top margin value is set to 1, and processingcontinues.

Programmer responseRespecify the top margin value, and rerun the job.

Severity:4

DFS1908I SC=08 VTAB= BOTTOM MARGINVALUE TRUNCATED TO LAST 3DIGITS

ExplanationThe bottom margin value exceeded 3 digits.

System actionThe bottom margin value is set to the last 3 digits, andprocessing continues.

Programmer responseSpecify the bottom margin value not to exceed 3 digits,and rerun the job.

Severity:8

DFS1909I SC=04 NULL BOTTOM MARGINVALUE WILL BE SET TO MAXIMUMPAGE VALUE

ExplanationVTAB= was specified without a bottom margin value.

System actionThe bottom margin value is set to the maximum linesper page value from the PAGE= specification.

Programmer responseRespecify the VTAB= top margin value, and rerun thejob.


Severity:4

DFS1910I SC=08 WIDTH= SPECIFICATIONINVALID WITH FEAT= IGNORE ORIF FEAT= IS UNSPECIFIED

ExplanationThe WIDTH= was specified while FEAT= IGNORE wasspecified or FEAT= was unspecified.

System actionWIDTH= value is ignored. A default width of 120 isused, and processing continues.

Programmer responseSpecify the DEV statement with a valid combination ofWIDTH= and FEAT= values, and rerun the job.

Severity:8


DFS1911I SC=08 VERTICAL TAB STOPEXCEEDS PAGE LENGTH. TABSTOP SET TO ZERO

ExplanationThe DEV statement VT= specification exceeded thepage length. The specification must be equal to or lessthan PAGE= specification.

System actionThe specified value is reset to zero, and processingcontinues.

Programmer responseSpecify the vertical tab stop in error, and rerun the job.

Severity:8

DFS1912I SC=08 VTAB= BOTTOM MARGINVALUE EXCEEDS 255, THEMAXIMUM PAGE= VALUE

ExplanationThe DEV statement VTAB= specification has a bottommargin value greater than 255.

System actionThe bottom margin is reset to the maximum linesper page value from the PAGE= specification, andprocessing continues.

Programmer responseChange the bottom margin value, and rerun the job.

Severity:8

DFS1913I * FPBP64aa = b, SET AS THEDEFAULT VALUE *

ExplanationIMS might issue this message when the DFSDFXXXmember contains the Fast Path parameter FPBP64=Yin <SECTION=FASTPATH> (enabling the IMS Fast Path64-bit buffer manager).

In the message text:aa

The specific function. Valid values are FPBP64,FPBP64M, FPBP64C, FPBP64D, FPBP64E,FPBP64SR, FPBP64MIN, SDEPAUTO, SDEPEXP,SDEPFREQ, or SDEPTIME.

bOne of the following values:

• Y• N• Storage size for FPBP64M• Maximum age for SDEPEXP in minutes• Number of minutes between checks for

SDEPFREQ• Time of day for SDEPTIME

This message echoes the default parameters whenthey are not specified in the DFSDFxxx member.

This message can contain multiple lines. All the FastPath parameters specified are displayed in successiveDFS1913I messages. The output of this messagelooks like this example:

DFS1913I * FPBP64C = Y, SET AS THE DEFAULT VALUE * SYS3DFS1913I * FPBP64D = N, SET AS THE DEFAULT VALUE * SYS3DFS1913I * FPBP64E = Y, SET AS THE DEFAULT VALUE * SYS3DFS1913I * FPBP64SR = Y, SET AS THE DEFAULT VALUE * SYS3DFS1913I * SDEPAUTO = N, SET AS THE DEFAULT VALUE * IMS1DFS1913I * SDEPEXP = 00120 MINUTES, SET AS THE DEFAULT * IMS1DFS1913I * SDEPFREQ = 01440 MINUTES, SET AS THE DEFAULT * IMS1DFS1913I * SDEPTIME = 2300 SET AS THE DEFAULT VALUE * IMS1



Module:DBFFATC1

Related referenceFASTPATH section of the DFSDFxxx member(System Definition)

DFS1914I INQUIRE ERROR NODE xRTNFDBK y SENSE z

ExplanationAn INQUIRE for session parameters during the logonfor NODE x failed. The attempted session initiationwas terminated. VTAM provided the return code andfeedback (y) with sense information (z) as the reasonfor the failure.

System actionThe system continues.


http://www.ibm.com/support/knowledgecenter/SSEPH2_15.1.0/com.ibm.ims15.doc.sdg/ims_dfsdfxxx_proclib_fastpath.htm#ims_dfsdfxxx_proclib_fastpath


Operator responseSee the system programmer.

Programmer responseExamine the BIND parameters in the mode table forNODE x for correctness, and the VTAM return code andsense information for the recovery action to be taken.Try to initiate the session for NODE x again.



DFS1915I UNSUPPORTED SCIP EXIT/VTAMERROR

ExplanationVTAM drove the IMS SCIP exit with an invalidcommand or an invalid parameter list.

System actionIMS rejected VTAM entry to the SCIP exit and returnedto VTAM with an error code. IMS continues.


Programmer responseExamine and correct possible inconsistencies in theVTAM definitions.



DFS1916I hh:mm:ss ATTEMPT TO STARTSECONDARY SESSION BUT WASPRIMARY NODE xxx ims-id

ExplanationAn attempt to start a session with NODE xxx asthe secondary half-session resulted in an error anda termination of the attempt. The previous session

with NODE xxx initiated as a primary half-session,terminated abnormally.

System actionIMS rejected the attempt to start the session as asecondary. IMS continues.

Operator response:See the Programmer response.

Programmer responseExamine the session initiation process, and determinethe cause of the previous session failure. Correct theprocedure and attempt the session initiation again.



DFS1917I INVALID CID

ExplanationVTAM used an invalid control interval definition (CID),or the CID in the IMS control block was overlaid. TheNODE name cannot be found for the session initiation.

System actionIMS rejected the VTAM entry to one of the IMSexits and returned to VTAM with an error code. IMScontinues.


Programmer responseDetermine whether VTAM has operational problems. Ifpossible, create a snap memory dump of the IMS CLBcontrol blocks to determine if any of them are overlaid.



DFS1918A DFSURDB0 CANNOT PROCESSCONCATENATED INPUT DATASETS FOR DD DFSUCUM


ExplanationThe architecture of the recovery utility DFSURDB0does not permit the use of concatenated files as inputusing the DFSUCUM DD statement.

System actionProcessing terminates with return code 8 after issuingthis message.

Programmer responseSubmit individual jobs for the utility, each with onlyone data set as the DFSUCUM DD input.

DFS1919I * IMSFP DFSDFxxx PARAMETERSFROM <SECTION=FASTPATH>*

:* aa = b *

ExplanationIMS issues this message when the DFSDFxxxmember contains Fast Path parameters in<SECTION=FASTPATH>.

This message is multi-line; all the Fast Pathparameters specified are displayed in the followingDFS1919I messages.

If Common Service Layer (CSL) is not used,the message also shows the ACBSHR value in<SECTION=FASTPATH> as Y or N.

In the message text,aa

The specific function. Valid values are FPBP64,FPBP64M, FPBP64C, FPBP64E, FPBP64D,FPBP64SR, FPBP64MIN, FPBP6HOFF, ACBSHR,SDEPAUTO, SDEPEXP, SDEPFREQ, or SDEPTIME.

bOne of the following values:

• Y• N• Storage size for FPBP64M• N, T, or F for SDEPAUTO• Maximum age for SDEPEXP• Number of minutes between checks for

SDEPFREQ• Time of day for SDEPTIME

The output of this message looks like this example:

DFS1919I * DEF_NBA = nnnn * SYS3

DFS1919I * DEF_OBA = nnnn * SYS3

DFS1919I * IMSFP DFSDFSLS PARAMETERS FROM <SECTION=FASTPATH>* SYS3DFS1919I * FPBP64 = Y * SYS3DFS1919I * FPBP64M = 06400000 * SYS3DFS1919I * ACBSHR = Y * SYS3DFS1919I * SDEPAUTO = T * SYS3DFS1919I * SDEPEXP = 25530 MINUTES * SYS3DFS1919I * SDEPTIME = 1030 * SYS3



Module:DBFFATC1


DFS1920I PARAMETER VALUE INVALID,xxxxxxxx=yyyyyyyyzzzzz

ExplanationAn invalid parameter was found.


Parameter keyword (First 8 characters)yyyyyyyy

Parameter value (First 8 characters)zzzzz

ABEND, if an invalid value for this parametercauses abend 0083 during initialization.

IMS execution parameters can be specified with JCLor with the DFSPBxxx or DFSDCxxx members. TheJCL specified parameters override any parametersspecified with DFSPBxxx or DFSDCxxx, resulting in thefinal execution parameters. Message DFS1920I resultswhen values of the final parameters do not meet thesystem definition requirements.

With some parameters, this error results in abend0083 after all the final parameters have beenevaluated. The value zzzzz=ABEND identifies theparameters with the unrecoverable error.




System actionUser abend 0083 results when ABEND appears in atleast one DFS1920I message. If the abend does notoccur, all parameters identified by DFS1920I receivetheir default values.

Programmer responseDetermine if the system should continue operatingwith the default value. If not, shut down IMS and rerunthe system with a corrected parameter.

Module:DFSIIDC0


DFS1921I PARAMETER KEYWORD INVALID,xxxxxxxx=yyyyyyyy

ExplanationAn invalid keyword was found. In the message text,the variables and their meanings are:xxxxxxxx

Parameter keyword (First 8 characters)yyyyyyyy

Parameter value (First 8 characters)

IMS execution parameters can be specified withJCL or with the DFSPBxxx and DFSDCxxx members.Message DFS1921I results when invalid keywordsare in the parameters specified with DFSPBxxx,DFSDCxxx, or JCL. For example, invalid keywordsmight be misspelled or might be invalid for the typeof IMS control region being started.

The DFSPBxxx member might use all 80 columns ofthe record. If you have parameters names starting incolumn 1, be sure that you do not have sequencenumbers in columns 73 through 80.


Programmer responseDetermine if the system should continue operatingafter using a parameter that was not correctlyspecified and was ignored. If necessary, shut downIMS and correct the parameter in error.

DFS1922I GSAM OPEN OF DD xxxxxx FAILED,REASON CODE=reason

ExplanationAn attempt to open GSAM data set xxxxxx failed forone of the following reasons:X'20'

MVS OPEN call failed.X'24'

An OPEN call to a specific concatenated data setfailed. Most likely, there is a missing data set in theconcatenation.

X'28'An OBTAIN of the data set DSCB failed. Ensurethat the data set has been properly allocated.

X'2C'An OBTAIN of a concatenated data set DSCBfailed. Ensure that the data set has been properlyallocated.

X'30'A fixed data set block size is zero. Ensure that thedata set has been properly allocated.

X'34'A fixed data set logical record length is zero.Ensure that the data set has been properlyallocated.

X'38'A fixed data set block size is not a multiple ofthe logical record length. Change the block size orlogical record length so the block size is a multipleof the logical record length.

X'3C'A previous call to a dummy data set encounteredan error. The data set cannot be opened.

X'40'An attempt to open a striped data set was made;however, the DFSMS release level is not at DFSMS1.2.0 or later.

X'44'The volume number does not exist in JFCBNVOL.

X'48'Current volume serial number in UCB does notmatch in JFCBVOLS.

Problem determination:1, 3, 17a, 18


DFS1924 KEYWORD RESOURCE NOTDEFINED



ExplanationA command was entered requesting a specificresource when the keyword resource is not defined forthe IMS system.

Operator responseCorrect the command.

Programmer responseCheck the keyword resource against the IMSgenerated system to determine if the resource isinstalled.

DFS1925 CONVERSATION RESOURCE NOTDEFINED

ExplanationA command was entered requesting information froma conversation resource that is not defined in the IMSsystem.

Operator responseCorrect the command.

Programmer responseCheck the TRANSACT and SPAREA macro definitionsfor conversation resource.

DFS1927 UNABLE TO PROCESS SHAREDEMH DUE TO LTERMREGISTRATION FAILURE

ExplanationWhile using the shared expedited message handler(EMH) to process an input message, Fast Path triedto register LTERM interest to CQS. However, the LTERMregistration failed.


Programmer responseThis problem is temporary. If the problem persists,print X'67D0', subtype X'D00D' log records to identifythe return and reason codes for the registration failure.

Module:DBFHIEL0

DFS1928 DBRC RETURNED A ZERO LENGTHMESSAGE, CANNOT PROCESSCOMMAND

ExplanationA DBRC request submitted by the /RMxxxxxxcommand processor returned a zero-length message.

System actionThe /RMxxxxxx command is rejected. IMS issues thismessage and continues execution.

Programmer responseDetermine the reason for the DBRC failure. See thez/OS master console (SYSLOG) for DSP messages thatmight explain the cause of the condition.


Module:DFSICLW0


DFS1929I IMS SYSTEM PARAMETERSinit_activ FOR THIS V nn.n crtEXECUTION: * parameter *

ExplanationIMS issues these messages when IMS control regioninitialization completes and when IMS control regionrestart completes. The initial IMS system parametersthat are active from DFSPBxxx and EXEC parametersare displayed in this message when IMS initializationcompletes. The IMS system parameters that aredisplayed after initialization might not reflect theactual values that are used during online execution.However, when DFS1929I is issued after an IMSrestart completes, it displays the actual values that areused during online execution.

The message header that is issued when IMS controlregion initialization completes contains a keywordINITIAL. The message header that is issued when IMSrestart completes contains the keyword ACTIVE.

Fast Path parameters are suppressed if Fast Path isnot active (FP=N).



init_activOne of the following:

INITIAL when the message is issued duringinitializationACTIVE when the message is issued during arestart

nn.nIMS version number, such as 10.1

crtControl region type, such as DBDC, DBCTL, DCCTL,or FDBR

In the message text, parameters are the IMS systemparameters. An example of message DFS1929Ifollows:

DFS1929I * IMS SYSTEM PARAMETERS ACTIVE FOR THIS V15.2 DBDC EXECUTION:DFS1929I * ALOT = 1440 DFS1929I * AOIP = 2147483647 DFS1929I * AOIS = N DFS1929I * AOI1 = DFS1929I * APPC = N DFS1929I * APPCSE = F DFS1929I * APPLID1 = DFS1929I * APPLID2 = DFS1929I * APPLID3 = APPL7 . .DFS1929I * TCORACF = N DFS1929I * SVSODR = NONE DFS1929I * TRACK = NO DFS1929I * TRN = DFS1929I * TSR = L DFS1929I * UHTS = 256 DFS1929I * USERVAR = IMS1 DFS1929I * VAUT = 1 DFS1929I * VSPEC = 91 DFS1929I * WADS = S DFS1929I * WKAP = 40960 DFS1929I * YEAR4 = N



Module:DFSSDSP0

DFS1930I INVALID COMMAND DETECTEDIN PROCLIB MEMBER xxxxxxxx.RESTART PROCEEDS.

ExplanationDuring IMS control region initialization, memberxxxxxxxx contained characters other than START incolumns 1 to 5. Member xxxxxxxx is either &DLINMor &DBRCNM on the control region startup parameter.This message follows message DFS0578I.

System actionThe member is discarded. The control region attemptsto start either DBRC or DLISAS with an MVS STARTcommand for procedure &DLINM or &DBRCNM, asappropriate.

Operator responseAsk the system programmer to verify that the librariesin the PROCLIB for the control region concatenationare set up correctly.

Related information“DFS0578I” on page 206READ SUCCESSFUL FOR DDNAME xxxxxxxxMEMBER yyyyyyyy

DFS1931I SESSION RECOVERY INPROGRESS NODE x USER z,UNBIND CODE WAS yy

ExplanationVTAM terminated the session with an UNBIND code ofyy. An automatic session restart is being attempted forNODE x, USER z.


Operator response:No action is required unless this message occursfrequently for NODE x. In this case, examine theUNBIND code to determine whether a possiblenetwork error should be corrected, or a different modetable entry and COS list should be used for sessioninitiation.





DFS1932 CONVERSATION IN PROGRESS-CANNOT PROCESS COMMAND.

ExplanationA /DISPLAY, /RDISPLAY, or /FORMAT commandwas entered while a conversation transaction was inprogress. These commands generate queued outputthat cannot be sent while the terminal or node is inconversation mode.


Operator response:The conversation must be terminated by theapplication or the terminal operator (/EXIT) beforethe command is accepted.

DFS1933I REGION INITIALIZATIONTERMINATED - THIS ADDRESSSPACE CURRENTLY HAS ANACTIVE IMS IMAGE

ExplanationIMS region initialization rejected a request for the startof a second IMS image in an address space. An IMSimage is defined as a BMP, MPP, IFP, DBB, or DLIregion.

System actionThe z/OS job for the second IMS image terminateswith a nonzero return code. The first IMS image isunaffected and continues to run.

Operator response:(master terminal) Contact your IMS systemprogrammer.

Programmer responseThe purpose of this message is to inform the systemprogrammer of an IMS architectural constraint (onlyone IMS image to an address space). Contact theperson who submitted the second image and informthem that this is currently not a supported feature.

Problem determinationNone. This is an IMS architectural constraint.

DFS1934E module FAILED TOLOAD modulename ERRORCODE=xxxxxxxx.

ExplanationIMS issued the IMODULE LOAD macro to load amodule, but the load failed.

In the message text:module

The module that issued the loadmodulename

The name of the module that could not be loadedxxxxxxxx

The returned error code


Output destinationThe System Console

System programmer responseSee the IMODULE return codes information. If you areunable to resolve the problem, contact IBM SoftwareSupport.

Module:DFSLOAD0, DFSDFN00, DFSAINB0

Related referenceIMODULE return codes (Messages and Codes)

DFS1935E UNABLE TO TERMINATEFUNCTIONS FOR CQSCOMMUNICATION -FUNCTION=failing_function,RETURN CODE=xxxxxxxx, REASONCODE=yyyyyyyy

or

UNABLE TO TERMINATE FUNCTIONS FORCQS COMMUNICATION - FUNCTION=CQSDISCSTRUCTURE=cccc, COMPCODE=zzzzzzzz

or

UNABLE TO TERMINATE FUNCTIONS FORCQS COMMUNICATION - FUNCTION=CQSDISCSTRUCTURE=cccc, COMPCODE=zzzzzzzzSTRUCTURE=cccc, COMPCODE=zzzzzzzz



ExplanationIMS encountered an error while attempting toterminate functions required for CQS communication.

The first form of the message is issued if a completioncode is not returned.

The second form of the message is issued if thefunction is CQSDISC, only one structure (MSGQ orEMHQ) is in error, and a nonzero completion code isreturned.

The third form of the message is issued if the functionis CQSDISC, both the MSGQ and EMHQ structures arein error, and a nonzero completion code is issued.failing_function

The function request that failed:CQSDISC

Request to terminate IMS connections to oneor more coupling facility structures failed.

CQSDEREGRequest to unregister IMS from CQS failed.

xxxxxxxxThe return code from the failing function.

yyyyyyyyThe reason code from the failing function.

ccccMSGQ or EMHQ

zzzzzzzzThe completion code from the CQSCONN request.


System programmer responseThe return code and reason code are provided for IBMsupport representatives only. Report the problem toIBM Software Support.

Module:DFSSQ040

Related conceptsCQS client requests (System ProgrammingAPIs)

DFS1936E UNABLE TO IDENTIFY THEIMS CONTROL REGIONTO CQS AS A CLIENT- FUNCTION=failing_function,RETURN CODE=xxxxxxxx, REASONCODE=yyyyyyyy

or

UNABLE TO IDENTIFY THE IMS CONTROL REGIONTO CQS AS A CLIENT - FUNCTION=CQSCONN,STRUCTURE=cccc, COMPCODE=zzzzzzzz

or

UNABLE TO IDENTIFY THE IMS CONTROL REGIONTO CQS AS A CLIENT - FUNCTION=CQSCONN,STRUCTURE=cccc, COMPCODE=zzzzzzzzSTRUCTURE=cccc, COMPCODE=zzzzzzzz

ExplanationAn error occurred while attempting to identify the IMScontrol region to CQS as a client that will use sharedqueues on the coupling facility.

The first form of the message is issued if a completioncode is not returned.

The second form of the message is issued if thefunction is CQSCONN, only one structure (MSGQ orEMHQ) is in error, and a nonzero completion code isreturned.

The third form of the message is issued if the functionis CQSCONN, both the MSGQ and EMHQ structures arein error, and a nonzero completion code is issued.failing_function

The function request that failed:IMODULE GETMAIN

Request to obtain a work area failed.IMODULE LOAD

Request to load a module failed.CQSREG

Request to register IMS to CQS failed.CQSCONN

Request to connect IMS to one or morecoupling facility structures failed.

CQS MSGQ STR ATRThe WAITRBLD value for the MSGQ structure isnot correct.

CQS EMHQ STR ATRThe WAITRBLD value for the EMHQ structure isnot correct.

JOIN XCF GROUPThe MAXGROUP value specified for the XCFcouple data set is too small.

xxxxxxxxThe return code from the failing function.


http://www.ibm.com/support/knowledgecenter/SSEPH2_15.1.0/com.ibm.ims15.doc.spr/ims_clientcqs.htm#ims_clientcqs

http://www.ibm.com/support/knowledgecenter/SSEPH2_15.1.0/com.ibm.ims15.doc.spr/ims_clientcqs.htm#ims_clientcqs

• For a description of IMODULE GETMAIN orIMODULE LOAD return codes, see the IMSsystem services return code information.

• For a description of CQSREG and CQSCONNreturn codes, see CQSREG request (SystemProgramming APIs) and CQSCONN request(System Programming APIs).

• For a description of CQS MSGQ STR ATR or CQSEMHQ STR ATR return codes, see reason codeyyyyyyyy. Reason and return codes for thesefunctions are the same.

yyyyyyyyThe reason code from the failing function:

• When the failing function is IMODULE GETMAIN,the reason code is one of the following:X'00001002'

DFSSQM allocation failed.X'00001004'

SQ1 AWE allocation failed.X'00001005'

SQ2 AWE allocation failed.• When the failing function is IMODULE LOAD, the

reason code is:X'00001006'

DFSSQ010 load failed.• When the failing function is CQSREG, the reason

code is from the CQSREG macro.• When the failing function is CQSCONN, the

reason code is from the CQSCONN macro.• When the failing function is CQS MSGQ STR ATR,

the reason code is:X'00000106'

The WAITRBLD value for the MSGQ structureis incorrect. When this error occurs, youmight need to force the structure and rebuildbefore IMS can be brought up.

• When the failing function is CQS EMHQ STR ATR,the reason code is:X'00000107'

The WAITRBLD value for the EMHQ structureis incorrect. When this error occurs, youmight need to force the structure and rebuildbefore IMS can be brought up.

• When the failing function is JOIN XCF GROUP,the reason code is:X'00000000'

The MAXGROUP value specified for the XCFcouple data set is too small. When this erroroccurs, you might need to increase the valuespecified on the MAXGROUP keyword.

ccccMSGQ or EMHQ

zzzzzzzzThe completion code from the CQSCONN request.

System actionIMS initialization terminates with abend code 0071.

System programmer responseIf the WAITRBLD value for the MSGQ or EMHQstructure is incorrect, determine which addressspaces are connected to the structure through CQS.Disconnect all non-IMS control region clients. RestartIMS so an IMS control region makes the initialconnection to a structure in the sysplex. Thenreconnect the non-IMS clients.

Return and reason codes from all other functions areprovided for IBM support representatives only. ContactIBM Software Support for assistance.

Module:DFSSQ020

Related referenceCQSREG request (System Programming APIs)CQSCONN request (System Programming APIs)IMS system services return codes (Messagesand Codes)Related informationIMS abend 0071

DFS1937I USER EXIT DFSxxxx0 LOADED

ExplanationThe security exit routine identified in the message hasbeen loaded. If RACF is also active, RACF is calledbefore the exit routine. xxxx0 can be DFSCSGN0,DFSCTRN0, or DFSCTSE0.

System actionThe exit routine is called for signon or transactionsecurity, depending which exit routine is loaded.

Programmer responseNone. If you do not want the exit routine loaded andcalled, remove it from the STEPLIB concatenation.

Module:DFSAINB0

DFS1938 INVALID MODE TABLE NAME LINKx


http://www.ibm.com/support/knowledgecenter/SSEPH2_15.1.0/com.ibm.ims15.doc.spr/ims_cqsregreq.htm#ims_cqsregreq


http://www.ibm.com/support/knowledgecenter/SSEPH2_15.1.0/com.ibm.ims15.doc.spr/ims_cqsconnreq.htm#ims_cqsconnreq







ExplanationA VTAM session initiation attempt failed becauseVTAM did not recognize the mode table name used forLINK x.

System actionThe attempt to establish an MSC VTAM session failedfor LINK x.

Operator response:Specify the correct mode table name supplied by thesystem programmer, and try to initiate the session forLINK x.

Programmer responseSpecify the correct mode table name for LINK x.



DFS1939W hh:mm:ssxxxxxxxxxxxINTEREST ERROR,yyyyyyyyzzzzzzzzwwwwwww

ExplanationIMS attempted to register or unregister interest in oneor more shared queues for one or more resources.Either IMS experienced an internal error, or CQSrejected the request.

The message variables have the following meanings:hh:mm:ss

Time stampxxxxxxxx

REGISTER or DEREGISTERyyyyyyyy

One of the following values:ALLOTMA

Interest was being registered for all activesupermember TPIPEs following a CQS failure.

ALLLTERMInterest was being registered for all activeLTERMs following a CQS failure.

ALLTRANInterest was being registered for alltransactions during IMS initialization orfollowing a CQS failure.

LTERM =Interest was being registered or deregisteredfor one or more LTERMs.

NODE =Interest was being registered or deregisteredfor all LTERMs assigned to the indicatedterminal.

PROGRAM=Interest was being registered or deregisteredfor one or more program names.

REMOTE =Interest was being registered or deregisteredfor one or more LNB or RSMB names.

TRAN =Interest was being registered or deregisteredfor one or more transaction names.

zzzzzzzzResource name (present only for LTERM, NODE,PROGRAM, REMOTE, or TRAN)

wwwwwwwContains '...ETC' if more than one resource failed;otherwise, this field is blank.

System actionIMS continues normal processing, but the affectedresources might no longer be notified of outputavailable on the shared message queues.

Programmer responseIf the error message is the result of a command orother process, attempt to reissue the command orrestart the process. If the error persists, contact IBMSoftware Support.

Problem determination1, 6, 37 and a copy of log record type X'67D0'.

Module:DFSSQI00


DFS1940I RECORDS SKIPPED FOR DBD =xxxxxxxx DDN= xxxxxxxx FROMTIME = yydddhhmmsst TO TIME= yydddhhmmsst COUNT =ccccccccccc


ExplanationThe input log for the Database Recovery utilityincludes database change records for a periodfor which the updates to the database set wereinvalidated by a time stamp recovery. The utilityignored those change records. The FROM TIME is thetime stamp from the earliest of these skipped records.The TO TIME is the time stamp from the latest of theskipped records. The COUNT is the total number ofskipped records in that range.



Module:DFSURDB0

DFS1941I STOPPED PROCESSING LOGWHEN TIME = yydddhhmmsstENCOUNTERED

ExplanationThe Database Recovery utility stopped reading theinput log when it encountered a database changerecord beyond the point to which the recovery is tobe done. The TIME shown in the message is the timestamp from the first database change record that theutility did not use. This is normal for a partial recovery.


Module:DFSURDB0

DFS1942 DATA COMMUNICATIONSQMGR/CQS READ ERROR LINK xx

ExplanationAn error occurred during the data communicationQMGR or CQS read (GU/GN) process.

System actionIf the error occurred while processing a message foran MSC link, the destination (for example, MSNAME orREMOTE TRANSACTION) is stopped and a 6701-MER1record is written to the log data set.

If the error occurred while processing a MSC /MSVERIFY command, the command is terminated and

6701-CMT1 /CMT2 /CMT3 /CMT4 records are writtento the log data set.

For system-defined terminals, communication (forexample, a VTAM session) is terminated.

For ETO terminals, the user is signed off. A X'67D0'log record containing pertinent information about theerror is produced.

For a /DEQUEUE command, the command is rejected.No messages were dequeued.

For the system console, the terminal is stopped.

Operator responseReestablish the session or signon as explained in theProgrammer response. After the error is corrected,issue the /DISPLAY STATUS MSNAME and the /DISPLAY TRANSACTION or QUERY TRAN commandsto determine the destination that was stopped.Destination will display STOPPED, QERROR. Use the /START command to start the destination.

If error occurred while processing a /MSVERIFYcommand, reissue the MSVERIFY command.

If this message is a result of a /DEQUEUE command,reenter the /DEQUEUE command when CQS or thestructure is again available.

If the stopped terminal is the system console, issuinga subsequent IMS command will reset the stoppedstatus.

Programmer responseYou can isolate the error by using the DFSERA10program to print the 6701 records. When the problemis corrected, reestablish the session or signon by Nodex, an IMS /OPNDST command, or responding to theDFS3649A signon message, as appropriate.


Module:DFSICIO0, DFSICLJ0

Related information“DFS3649A” on page 1036/SIGN COMMAND REQUIRED.“IMS problem determination” on page 11IMS messages and codes problemdetermination is accomplished by usingprocedures established by IBM.

DFS1943 CQS OUTPUT QUEUEREGISTRATION ERROR


ExplanationAn error occurred during a logon or signon CQSINFORM call to register interest on one or moreoutput message queues (LTERMs) associated with theterminal logon or user signon.

System actionFor system-defined terminals, communication (forexample, a VTAM session) is terminated. For ETOterminals, the user is signed off. An X'67D0' log recordcontaining pertinent information about the error isproduced.

Operator response:Reestablish the session or signon as explained in theProgrammer response.

Programmer responseWhen the problem is corrected, reestablish thesession or signon by Node x, an IMS /OPNDSTcommand, or responding to the DFS3649A signonmessage, as appropriate.

Problem determination:1, 5, 6,12, 14, 15, 36

Module:DFSCMS00


DFS1944E APPC OUTPUT SEGMENT SIZEEXCEEDED, MESSAGE DISCARDEDFOR LU=nnnnnnnn, TPN=name,SIDE=name, TRANCODE=xxxxxxxx

ExplanationThe named transaction inserted an output messagesegment greater than 32767 to an LU6.2 destination.The maximum output message segment to an LU6.2device is 32767.

System actionThe output message is discarded.

Programmer responseChange the named transaction to insert messagesegments with a length no greater than 32767.

Change the TRANSACT macro SEGSIZE parameter to32767.

DFS1945 DATA COMMUNICATIONSQMGR/CQS WRITE ERROR LINK xx

ExplanationAn error occurred during the data communicationQMGR or CQS WRITE (PUT/ISRT) process.

System actionFor messages being received on an MSC link, themessage is canceled, a 6701 ID = MSSx (x = 1, 2,3) record is written to the log, and the partner IMSsystem is notified. The partner system issues messageDFS2140 DESTINATION name STOPPED, REASONCODE 1945, where name is the MSNAME of the MSCsend path. The message is returned to the messagequeue of the sending IMS system.

If a /MSVERIFY command was being processed, theinformation being inserted to the queue is discarded,and a 6701-AER1 record is written to the log data set.

If a message was being routed by the messagecontrol error exit DFSCMUX0, the rerouted messageis canceled, and a 6701 ID = AER1 record is written tothe log data set.

Operator response:When you have corrected the problem, use the /START command to start the destination (for example,MSNAME or REMOTE TRANSACTION). If the erroroccurred while processing a /MSVERIFY command,reissue the command.

Programmer responseYou can isolate the error by using the DFSERA10program to print the 6701 records.

Problem determinationContact the system programmer if the error persists.

If the error was encountered by an MSC link, thefollowing CLBTEMP fields are set in the LLB block inthe 6701 MSS1 record:

• CLBTEMP2 = R15 return code +8 from the QMGRPut-move call

• CLBTEMP3 = Message key = x'00000799' = decimal1945

• CLBTEMP4 = Module ID, that is C'CMS0' =DFSCMS00

Module:


DFSCMS00, DFSCMLA0, DFSCMLB0, DFSCM4L0,DFSCMSY0, DFSCMEI0


DFS1946W IMS CRC OF 'x' ALREADY EXISTSWITHIN SYSTEM OR SYSPLEX

ExplanationThe IMS command recognition character of 'x' is notunique within the registration scope of system orsysplex. The character has been registered by anothersystem.

System actionThe IMS system continues processing.

Programmer responseUsing the CRC= execution parameter, a different CRCcan be specified in the next IMS execution.

Module:DFSXSTM0

DFS1947I LOCKED MESSAGES EXISTEDDURING CQS DISCONNECT

ExplanationIMS issues this message during IMS shutdown. This isa normal condition when:

• IMS conversational messages (for conversations thathave not yet ended) exist.

• Response mode messages exist. This occurs whenresponse mode messages have been sent but anacknowledgment was not yet received.

• Messages for ISC, SLU P, and FINANCE devices exist.

IMS must retain these messages with this IMS until itrestarts. These messages is only accessible from thisIMS system.

If IMS is cold started, IMS will move the lockedmessages to the cold queue.



DFS1948 CQS READ FOUND ANOTHERSYSTEMS MESSAGE NODE x USERy

ExplanationIMS identified a Fast Path reply message thatbelonged to another IMS system in the sysplex duringa scheduled read to the Shared Queues facility.

When using the same LTERM name on multiplesystems in a shared queues sysplex, all Fast Path replymessages must be processed by the system at theoriginating terminal. This means that while a Fast Pathresponse mode operation is still in-progress on oneIMS system, the same LTERM name cannot be used,simultaneously or serially, by a terminal on anotherIMS system.

This is an IMS Transaction Manager restriction for FastPath in a shared queues environment.

System actionIMS writes a 6701-AER1 diagnostic record to the logand makes the message generally available again tothe sysplex through shared message queue support.For ETO sessions, the signon for USER y is failed.For non-ETO, the session established with NODE x isended.

Operator responseFurther attempts to sign on USER y or logon NODEx will repeat this error condition until the Fast Pathresponse mode is reset or the message is dequeuedfrom the shared queues facility. The originatingterminal might receive the message and terminate theFast Path response mode.



DFS1949 KEYWORD INVALID - SHAREDEMH QUEUES NOT ENABLED

ExplanationThe command was not processed because the EMHQkeyword is invalid in an IMS system without SharedEMH Queues.



System programmer responseReissue the command in an IMS system in whichShared EMH Queues is enabled.

Module:DFSIDP00

DFS1950 DESTINATION HAS NO OUTPUTQUEUED

ExplanationThe /ALLOCATE command was entered, but the LU6.2 destination has no output to be sent.





DFS1951 DESCRIPTOR KEYWORDPARAMETER IS INVALID

ExplanationThe descriptor parameter specified was not an LU 6.2descriptor and was invalid.


Programmer responseReenter the command with intended parameters.

DFS1952 DESTINATION NOT FOUND

ExplanationThe specified destination was invalid.


Programmer responseReenter the command with a valid destination.

DFS1953 COMMAND NOT APPLICABLE

ExplanationThe entered command was not applicable to thepresent state of the system. This message is issuedfor one of the following reasons:

• A command is entered that operates on LUNAME/TPNAME and the current IMS system is not operatingwith a z/OS supporting APPC.

• A command was entered to put IMS in a state whichIMS is already in. The command thus has no effect.

• The DFSAPPC message switching service wasentered on an IMS system that is not running witha z/OS supporting APPC.

• A command was entered to change the APPCtimeout value and the current z/OS release does notsupport APPC timeout.



Module:DFSICLN2

DFS1954 NO TPNAMES ASSOCIATED WITHLUNAME

ExplanationThe entered command specified the LUNAME andTPNAME keywords with parameter ALL, but noasynchronous output messages were associated withthe specified LUNAME.


DFS1955I APPC CONVERSATIONALLOCATION FAILURE. RC=nn,LU=name, TPN=name [,SIDE=name] or LU=xxxxxxxxSTOPPED

ExplanationThis message is issued if a failure otherthan TP_NOT_AVAILABLE occurs while sending anasynchronous response. The LU STOPPED form of themessage indicates the inputting LU is in STOPPEDstate. The return codes in this message are displayedas a hexadecimal value. If the LU name is network-qualified, it can be up to 17 bytes long.

System actionSystem operation continues normally. This errormessage is sent to the master terminal operator.For the LU STOPPED form of the message, themessage is sent to the incoming device, and theconversation is rejected with a reason code ofTP_NOT_AVAILABLE_RETRY.


Programmer responseIf the LU STOPPED message appears, the operator canissue /START LU xxxxxxxx INPUT for the LU NAMEspecified in the message.

Module:DFSALM00

Related referencez/OS: APPC/MVS - Explanation of return andreason codes

DFS1956E REQTEXT

ExplanationThis multiple-format message identifies IMSTP_PROFILE syntax errors, such as TRANCODE, CLASSAND MAXRGN IS OMITTED. It also identifies LU 6.2descriptors, such as INVALID LTERM NAME.

The following list contains the various formats forTP_PROFILE:

• DFS1956E TRANCODE, CLASS AND MAXRGN ISOMITTED

• DFS1956E KEYWORD IS MISSING, TOO LONG ORINVALID KEYWORD:

• DFS1956E MISSING "=" AFTER KEYWORD• DFS1956E VALUE MISSING OR TOO LONG• DFS1956E DUPLICATE OR INVALID TRANCODE:• DFS1956E INVALID CLASS, IT MUST BE BETWEEN 1

AND 255:• DFS1956E INVALID MAXRGN, IT MUST BE

BETWEEN 0 AND 255:• DFS1956E DUPLICATE OR INVALID CLASS• DFS1956E DUPLICATE OR INVALID MAXRGN• DFS1956E DUPLICATE CPUTIME• DFS1956E INVALID CPUTIME, IT MUST BE

BETWEEN 0 and 1440

The following list contains the various formats for LU6.2 descriptors:

• DFS1956E SYNTAX ERR ON PREVOUS CARD INCHAIN, SKIP THIS

• DFS1956E SYNTAX ERROR ON CARD card number• DFS1956E SYNTAX ERROR FOR DESCRIPTOR =

lterm name DUPLICATE OUTBND KEYWORD

The following are added to the prefix:

• CAN NOT CONTINUE IF COL(71) IS BLANK• FIRST COLUMN MUST BE EITHER "U" OR "*"• SECOND COLUMN MUST BE BLANK• LTERM NAME NOT GIVEN

• LTERM NAME LONGER THAN 8 CHAR• INVALID LTERM NAME• DIFFERENT LTERM NAME ON CONTINUED CARD• THE CONTINUED DATA MUST BEGIN IN COLUMN 12• ILLEGAL KEYWORD• SIDE MUST BE 1 TO 8 CHARACTER LONG• INVALID CHARACTER IN SIDENAME• DUPLICATE SIDE KEYWORD• LUNAME MUST BE 1 TO 17 CHARACTERS LONG• LUNAME MUST BEGIN WITH A-Z OR @,$,#• DUPLICATE LUNAME KEYWORD• INVALID CHARACTER IN LUNAME• TPNAME MUST BE 1 TO 64 CHARACTER LONG• DUPLICATE TPNAME KEYWORD• INVALID CHARACTER IN TPNAME• MODE MUST BE 1 TO 8 CHARACTER LONG• MODE MUST BEGIN WITH A-Z OR @,$,#• INVALID CHARACTER IN MODE• DUPLICATE MODE KEYWORD• SYNCLEVEL MUST BE 1 CHARACTER LONG• INVALID SYNCLEVEL VALUE• DUPLICATE SYNCLEVEL KEYWORD• CONVTYPE MUST BE 1 CHARACTER LONG• INVALID CONVTYPE VALUE• DUPLICATE CONVTYPE KEYWORD• DESCRIPTOR ENTRY ALREADY EXISTS

System actionThis error message is sent to the system console.

Programmer responseCorrect the errors identified in this message.

DFS1957E DFSAPPC ERROR: description

ExplanationAn input parameter error is found while processingthe DFSAPPC message request. The description field isreplaced by the appropriate error types. The followingare possible error types:

MISSING '('MISSING '=' AFTER KEYWORDINVALID OR DUPLICATE KEYWORDINVALID LTERM NAMEINVALID LU NAMEINVALID MODE NAME


http://www-01.ibm.com/support/knowledgecenter/SSLTBW_2.4.0/com.ibm.zos.v2r4.ieak500/rcdesc.htm?lang=en


INVALID TP NAMEINVALID SIDE NAMEINVALID CONVERSATION TYPEINVALID SYNC LEVELMISSING OR INVALID VALUE AFTER KEYWORDLTERM AND OTHER KEYWORDS ARE MUTUALLYEXCLUSIVETHE PARAMETER LENGTH IS TOO LONGNO MESSAGE TEXT AFTER ')'NO USERID OR USER IS NOT SIGNED ONDESTINATION NOT FOUND


Programmer responseCorrect the errors and retry DFSAPPC.

DFS1958I IMS CONNECTION TO APPC/MVSCOMPLETE, LUNAME= nnnnnnnn.

ExplanationThe connection between APPC/MVS and IMS wasestablished. APPC/MVS opened the local ACB of IMS.APPC/MVS LU 6.2 services are available to IMS. If theLU name is network-qualified, it can be up to 17 byteslong.

System actionIMS receives messages from LU 6.2 devices and sendsmessages to LU 6.2 devices using APPC/MVS services.

DFS1959E SEVERE IMS INTERNAL FAILURE,REASON CODE= xxyy

ExplanationThis message identifies an IMS internal error.


Programmer responseContact IBM Software Support and report the reasoncode xxyy provided by the message and the LUMItrace output. Also see the IMS diagnostic informationfor more information about this message and otherAPPC/IMS diagnostic aids.

Related referenceDFS1959E message information (Diagnosis)

DFS1960I IMS HAS REQUESTED ACONNECTION WITH APPC/MVS

ExplanationIMS issued the APPC/MVS verb ATBIDEN to connect toAPPC/MVS.

System actionIMS continues processing without APPC/MVS LU 6.2service. The service is unavailable until APPC/MVSdrives the IMS XCF exit indicating that the IMS LOCALLU 6.2 ACB was opened.

DFS1961W IMS CONNECTION WITHAPPC/MVS HAS FAILED

ExplanationA failure occurred while trying to start or maintain anAPPC/MVS connection.

System actionIMS continues processing without APPC enabled.

Programmer responseDetermine the reason for failure by analyzingall DFS1965E messages and VTAM or APPC/MVSmessages on the system console that might havepreceded this message. Restart APPC using the /START APPC command.

Related conceptsAPPC/IMS diagnostic aids (Diagnosis)Related information“DFS1965E” on page 573APPC/MVS CALL FAILURE,FUNCTION=aaaaaaaa, REASON CODE=xxyy,RETURN CODE=xxxxxxxx, LUNAME=nnnnnnnn

DFS1962 COMMAND INVALID FROM AN LU6.2 DEVICE

ExplanationThis command cannot be entered from an LU 6.2device. It is valid only from other IMS terminal types.

System actionThe IMS command is ignored.


http://www.ibm.com/support/knowledgecenter/SSEPH2_15.1.0/com.ibm.ims15.doc.dgr/ims_dfs1959e.htm#ims_dfs1959e_

http://www.ibm.com/support/knowledgecenter/SSEPH2_15.1.0/com.ibm.ims15.doc.dgr/ims_appc_diagnostic_aids.htm#ims_appc_diagnostic_aids

Operator responseThe IMS command entered has no meaning for anLU 6.2 device. Determine the reason for using thiscommand. Another IMS command might apply, oran APPC/MVS or VTAM command might exist for thewanted action.

DFS1963W XRF PARAMETERS MISSINGOR INVALID IN MVS APPCPMMEMBER

ExplanationThis message is issued because the USERVAR orALTLU parameters are missing or invalid in theAPPCPM member. The APPCPM member is used byz/OS during startup of the APPC subsystem to specifyoptions. z/OS also passes USERVAR and the ALTLUname to IMS when requested.

Programmer responseCheck the APPCPM member for validity of theUSERVAR and ALTLU parameters.

DFS1964E DESTINATION TMEMBERNAME=nnnnnnnn NOTACCESSIBLE, REASON CODE=xx,TPIPE NAME=yyyyyyyy

or

DESTINATION NAME=nnnnnnnn NOT ACCESSIBLE,REASON CODE=xx, LUNAME=yyyyyyyy

ExplanationThe specified destination cannot be accepted forprocessing from an LU 6.2 device and is discarded. Ifthe LU name is network-qualified, it can be up to 17bytes long. The reason codes and their meanings arethe following:

Code (dec)Explanation

01The destination name specified by the requestorfrom LUNAME= is for an IMS MSC destination.This type of destination is not valid for queuingmessages from an LU 6.2 application program thatis not on an IMS system that has MSC support forAPPC.

02The destination name specified by the requestorfrom LUNAME= is for a local LTERM. This type of

message switch function is not supported from anLU 6.2 application program.

03The destination name specified by the requestorfrom LUNAME= is for an IMS Fast Path transactionor an IMS response mode transaction. This type oftransaction is not valid for queuing messages froman LU 6.2 device with an asynchronous request(ALLOCATE, SEND_DATA, DEALLOCATE).

04The destination name specified by the requestorfrom LUNAME= can accept only single segments.Because multiple segments were detected fromthe requestor, the input is discarded (ALLOCATE,SEND_DATA, SEND_DATA).

05The destination name specified by the requestorfrom LUNAME= is an IMS remote transaction namethat is not acceptable. The cause could be thatthe destination IMS is not capable of accepting anAPPC transaction.

06If the first form of the message is issued,the reroute destination name for MessageControl/Error exit specified from LUNAME= andDESTINATION NAME=, or from DESTINATIONNAME=, is not accessible because the messageoriginated in this system and there is no base LUname in this system to receive an output message.

If the second form of the message is issued, thereroute destination name for the Message Control/Error exit specified on TMEMBER NAME= andTPIPE NAME= is not accessible.

07In a shared queues environment, the destinationname specified by the requester from LUNAME=is for a dynamic (non-CPIC and non-MSC-remote)transaction. This is not allowed because APPC-entered transactions must be run on the samelocal IMS on which the transaction was entered.Dynamic transactions represent transactions thatonly run on other IMS systems in the sharedqueues group.

09Rollback (ROLB) retry count was exceeded. Thesystem is unable to process transaction.


System actionThe reroute request is ignored and the associateddefault action is performed. See DFSCMUX0 for defaultactions.


Programmer responseTake the appropriate action for each reason code:Code (dec)

Action01

Do not attempt to use an MSC-defined transaction02

Use the DFSAPPC facility for message switchsupport

03Use the synchronous process (ALLOCATE,SEND_DATA, RECEIVE_AND_WAIT)

04Because multiple segments were detected fromthe requestor, the input is discarded (ALLOCATE,SEND_DATA)

05Verify that the destination IMS is at systemproduct level of Version 5.1

07Determine which IMS systems in the sharedqueues group have the transaction defined locally,and enter the transaction on one of these systems.

DFS1965E APPC/MVS CALLFAILURE, FUNCTION=aaaaaaaa,REASON CODE=xxyy,RETURN CODE=xxxxxxxx,LUNAME=nnnnnnnn

ExplanationA call to APPC/MVS had an unexpected return code.The call aaaaaaaa was issued, and a return codexxxxxxxx from APPC/MVS was the result.

A return code that is negative (for example, -1)indicates that the error occurred in processing thecall before APPC/MVS receiving control; these negativereturn code values are set by IMS. The possible valuesare:-1

Call unavailable (z/OS entry point not defined;probable cause is bind error with level of z/OS thatdoes not support APPC/MVS, for example, SP 4.1or earlier).

-2Call not known (probable cause is incorrectinstallation of IMS resulting in running modulesfrom 2 separate IMS releases).

See z/OS: APPC/MVS Allocate Queue Services for themeaning of positive values for this return code. Errorreturn codes that represent anticipated conditions arehandled by IMS, and do not result in this message.

This message is produced when an unexpected resultis encountered, which might represent an abnormalcondition in some system component.

The reason code variable xx is a decimal number thatidentifies the module associated with the code. SeeAPPC/IMS diagnostic aids in IMS Version 15 Diagnosis.Variable yy is the internal reason code.

If you contact the IBM support center, be preparedto supply the module number and reason code givenin the message, and if requested, the output from LUmanager trace.

If the LU name is network-qualified, it can be up to 17bytes long.

Programmer responseDetermine the error and whether the failingcomponent is either IMS, APPC/MVS, or VTAM. Checkthat IMS is running with the correct level of APPC/MVS.

Problem determinationCheck for any accompanying APPC/MVS and VTAMerror messages. Check the SYS1.LOGREC data set forsoftware failure records that might accompany thiscondition.

Related conceptsAPPC/IMS diagnostic aids (Diagnosis)Related referenceDFS1965E APPC/MVS call failures (Diagnosis)z/OS: APPC/MVS - Explanation of return andreason codes

DFS1966 IMS CONVERSATIONAL TRANENDED. INPUT DISCARDED

ExplanationThe remote LU 6.2 application program endedthe LU 6.2 conversation with an IMS-definedconversational transaction with pending input(SEND_DATA, DEALLOCATE).

System actionThe system continues processing. The pending inputis discarded, the IMS conversational transactionis terminated, and the LU 6.2 conversation isdeallocated.

Programmer responseCorrect the remote application program to receive theresponse before deallocating the LU 6.2 conversation.


http://www-01.ibm.com/support/knowledgecenter/SSLTBW_2.4.0/com.ibm.zos.v2r4.ieak500/allserv.htm?lang=en

http://www.ibm.com/support/knowledgecenter/SSEPH2_15.1.0/com.ibm.ims15.doc.dgr/ims_appc_diagnostic_aids.htm#ims_appc_diagnostic_aids

http://www.ibm.com/support/knowledgecenter/SSEPH2_15.1.0/com.ibm.ims15.doc.dgr/ims_dfs1965app.htm#ims_dfs1965app



DFS1967 MESSAGE SEGMENT BUFFEROVERLAY

ExplanationThe EDIT EXIT routine can change the messagecontents and can increase the message length by asmuch as 256 bytes. The total message length cannotexceed 32,764 bytes. If the message length exceedsthis limit, or if the message is increased by more than256 bytes, the message is truncated.

System actionThe message is truncated.

Programmer responseCorrect the Edit Exit routine to prevent an increase ofthe message of more than 256 bytes.

DFS1968 APPC IS NOT SUPPORTED FORTHE SPECIFIED MVSLEVEL

ExplanationThe z/OS level specified in the IMSCTRL IMS systemdefinition macro does not provide the correct z/OSlevel to use APPC.

System actionThe request is ignored, and IMS continues to function.

Programmer responseEnsure that the IMS JCL does not specify APPC=Y, andIMS commands do not specify LU 6.2 functions.

DFS1969W LU 6.2 DESCRIPTOR=xxxxxxxxNOT FOUND DURING MVS XRFRESTART

ExplanationThe specified descriptor name was found ina checkpoint record, but the descriptor blockrepresenting the descriptor was not found.

System actionThe request is ignored, and IMS continues to function.

Programmer responseCheck the DFS62DTx member used by the IMSsystem, and verify that the information for thespecified descriptor is not defined.

DFS1970 IMS SHUTTING DOWN-TRANSACTION DISCARDED

ExplanationThis message is sent to the partner LU thathas established a synchronous LU 6.2 or OTMAconversation with IMS. An IMS /CHE shutdowncommand was entered. This message informs thepartner application that IMS is shutting down.

System actionThe LU 6.2 or OTMA conversation is ended. IMScontinues with shutdown processing.

Module:DFS6ECT0, DFSYTIB0

DFS1971I CQCHKPT SYSTEM COMMANDREJECTED FOR STRUCTURE=structurename; THE STRUCTURENAME IS INVALID

or

CQCHKPT SHAREDQ COMMAND REJECTED FORSTRUCTURE= structurename; THE STRUCTURENAME IS INVALID

ExplanationThe command was not processed because thestructure named in the message is not a valid structurename.


System programmer responseReissue the command with a valid structure name.

Module:DFSSQCP0

DFS1972I CQCHKPT SYSTEM COMPLETE FORSTRUCTURE= structurename

or

CQCHKPT SHAREDQ COMPLETE FOR STRUCTURE=structurename


ExplanationThe /CQCHKPT SHAREDQ or /CQCHKPT SYSTEMcommand completed for the structure named in themessage.


Module:DFSSQCP0

DFS1973I CQCHKPT SYSTEM REQUESTREJECTED FOR REASONCODE=reasoncode

or

CQCHKPT SHAREDQ REQUEST REJECTED FORREASON CODE=reasoncode

ExplanationThe /CQCHKPT SHAREDQ or /CQCHKPT SYSTEMcommand was rejected. The reason codes(reasoncode) are as follows:


1CQS shutdown pending

2No CQS address space

3Invalid CQS registration token

4The function is invalid.

5The count is invalid.

6The list address is invalid.


System programmer responseCall IBM Software Support for assistance.

Module:DFSSQCP0

DFS1974I CQCHKPT SYSTEM REQUESTREJECTED FOR STRUCTURE=

structurename, REASONCODE=reasoncode

or

CQCHKPT SHAREDQ REQUEST REJECTEDFOR STRUCTURE= structurename, REASONCODE=reasoncode

ExplanationThe /CQCHKPT SHAREDQ or /CQCHKPT SYSTEMcommand failed for the structure named in themessage. The reason codes (reasoncode) for thefailure are:


1The checkpoint is already in progress for thestructure.

2A CQS restart is in progress.

3The connect token is invalid.

4CQSRSYNC is required for this structure.

5A CQS internal error occurred.

6The retry failed.


System programmer responseFor reason codes 1 and 2, reissue the command whenthe event completes.

For all other reason codes, call IBM Software Supportfor assistance.

Module:DFSSQCP0

DFS1975 COMMAND REJECTED AS CQS ISNOT AVAILABLE

ExplanationThe command was not processed because the CQSaddress space is unavailable.



System programmer responseReissue the command when CQS is available.

Module:DFSICM30, DFSICQ20, DFSIDP40

DFS1976 KEYWORD INVALID - SHAREDQUEUES NOT ENABLED

ExplanationThe command was not processed because thekeyword is invalid in an IMS system without SharedQueues.


System programmer responseReissue the command in an IMS system in whichShared Queues is enabled.

Module:DFSIDPR0, DFSIDP00

DFS1977 COMMAND REJECTED DUE TO CQSERROR

ExplanationThe command was not processed because IMSreceived an error return code from CQS.


System programmer responseReissue the command. If you receive the samemessage again, contact IBM Software Support.

Module:DFSICQ20, DFSIDP40

DFS1978I REQUEST FOR STORAGEFAILED DURING CQCHKPTCOMMAND PROCESSING, REASONCODE=reasoncode

ExplanationThe /CQCHKPT SHAREDQ or /CQCHKPT SYSTEMcommand processing terminated because IMS was

unable to acquire HIOP storage to process thecommand or to issue a message about the outcomeof the command. The reasons are:1

Unable to issue message DFS1971I to report aninvalid structure.

2Unable to obtain the storage required to processthe /CQSCHKPT command.

3Unable to issue message DFS1972I to report thatthe /CQSCHKPT command was successful for allstructures.

4Unable to issue message DFS1973I to report aparameter error.

5Unable to issue message DFS1972I to reportthat the /CQSCHKPT command was successful forsome structures.

6Unable to issue message DFS1974I to report thatthe /CQSCHKPT command failed for a structure.

7Unable to issue message DFS1973I to report anenvironmental error.


System programmer responseReissue the command.

Module:DFSSQCP0

Related information“DFS1972I” on page 574CQCHKPT SYSTEM COMPLETE FORSTRUCTURE= structurename“DFS1973I” on page 575CQCHKPT SYSTEM REQUEST REJECTED FORREASON CODE=reasoncode“DFS1974I” on page 575CQCHKPT SYSTEM REQUEST REJECTEDFOR STRUCTURE= structurename, REASONCODE=reasoncode

DFS1979I CHECKPOINT REQUESTREJECTED, CQS IS NOTAVAILABLE


ExplanationThe request was not processed because the CQSaddress space is unavailable.


System programmer responseReissue the command when CQS is available.

Module:DFSRCP00

DFS1980 TRANSACTION NOT STOPPED,CANNOT PROCESS COMMAND

ExplanationThe /DEQ command was rejected because thetransaction was not stopped.


System programmer responseIssue the /STOP TRAN or UPDATE TRANSTOP(Q,SCHD) command; then reenter thecommand.

Module:DFSICLJ0

DFS1981 COMMAND REJECTED DUE TO CQSERROR OR CQS UNAVAILABLE

ExplanationThe command was not processed because theCommon Queue Server (CQS) address space wasunavailable, or because IMS received an error returncode from CQS.


System programmer responseReissue the command when CQS is available. If CQSis available and you receive the same message again,contact IBM Software Support.

Module:DFSICLZ0

DFS1982I Reason Code = rcmessage

ExplanationAn error occurred during Index/ILDS Rebuild utilityprocessing, indicated by rc, with an accompanyingmessage issued by module DFSPREC0. Each reasoncode has its own explanation and response.

See the following reason codes (rc) to further identifythe type of error and appropriate action:

Reason Code = 05 Error processing SYSIN data set

Explanation: An error was found while processingthe DFSPREC0 input card.

System action: The job terminated with a returncode of 8.

Programmer response: Verify that the inputkeywords and parameters are correct. Keywordsand parameters are position-dependent.

Reason Code = 10 Recovery type specified inDFSPREC0 control card is invalid

Explanation: The recovery type specified in thecontrol card was not one of the three allowabletypes: INDEX, ILE, BOTH


Programmer response: Verify that the recoverytype is correct and rerun job. Keywords andparameters on the input control card are position-dependent.

Reason Code = 20 DDIR for partition specified inDFSPREC0 control card could not be found

Explanation: The list of DDIRs returned fromthe block builder did not include a DDIR for thepartition specified on the control card.


Programmer response: Verify that the DBDNAMEon the exec card and the partition name on thecontrol card are correct, then rerun the job.

Reason Code = 30 DB org. for partition specifiedin DFSPREC0 control card not supported inpartitioning.

Explanation: The partition specified was not for aPHDAM or PHIDAM database.


Programmer response: Verify that the partitionname specified on the control card is correct, thenrerun the job.


Reason Code = 40 Partition Select call failed

Explanation: The call to schedule the partition tobe recovered failed.


Programmer response: Verify that the partitionspecified on the control card is for a HALDB.

Reason Code = 50 The partition processed but noroot segments were found.

Explanation: The partition specified wasprocessed for INDEX recovery but no rootsegments were found.


Programmer response: This is an abnormalcondition. Contact IBM Software Support forassistance.

Reason Code = 60 DFSPREC0 control card specifiedILE recovery and no ILEs were required for thispartition

Explanation: An ILE rebuild request resulted in noentries being inserted into the ILE data set

System action: The job completed with a returncode of 4.

Programmer response: This situation can occurif no logical relationships exist for this partition.Verify that there are no logical relationshipsexisting in this partition.

Reason Code = 70 During ILE processing, theGETMAIN for a segment I/O area failed

Explanation: To complete an ILE rebuild, asegment I/O area is required for internal GNprocessing. This error results when space isunavailable to satisfy the GETMAIN.


Programmer response: Increase the region sizefor the batch job, then rerun it.

Reason Code = 80 ILE processing terminated priorto reaching the end of the database

Explanation: A GN call during ILE rebuildprocessing returned with an unexpected returncode. Expected return codes are: GA, GB, GK, orblank.


Programmer response: Determine the reason forthe unexpected return code and rerun job. For

information about DL/I status codes, see the DL/Istatus code information. For assistance, call IBMSoftware Support.

Reason Code = 90 Unable to perform INDEX/ILErebuild processing – DBRC not available

Explanation: DBRC is unavailable. INDEX/ILErebuild requires that DBRC is active during rebuildprocessing.


Programmer response: Ensure that DBRC=Y isspecified in the EXEC card, then rerun the job.

Reason Code = A0 Index/ILD rebuild requestnot honored - database specified NOT a HIDAMdatabase

Explanation: During an INDEX rebuild request,DDIR determined that the partition was not for aPHIDAM database.


Programmer response: Change the DBD on thejob parameter to a HALDB that is PHIDAM, thenrerun the job.

Reason Code = B0 Index rebuild was requested for aDBD that is not a HALDB DBD.

Explanation: During an INDEX rebuild request,DDIR determined that the partition was not for aHALDB database.


Programmer response: Change the DBD on thejob parameter to a HALDB DBD, then rerun the job.

Reason Code = C0 Index rebuild was requestedusing a PSB with a DBPCB that does not map to theMaster DBD specified on the JOB PARM card.

Explanation: During an INDEX rebuild request,DDIR determined that the partition was not for aHALDB database.


Programmer response: Change the DBD on thejob parameter to a HALDB DBD that is the masterdatabase containing the partition input on theSYSIN card, then rerun the job.

Reason Code = D0 OPEN/CLOSE failure - refer topreceding DFS0730I message

Explanation: OPEN or CLOSE failure occurred;refer to preceding DFS0730I message for thename of the data set.



Programmer response: Correct the problemidentified in DFS0730I and run the job again.

Reason Code = D4 OPEN/CLOSE failure refer topreceding DFS0730I message

Explanation: OPEN or CLOSE failure occurred;refer to preceding DFS0730I message for thename of the data set.


Programmer response: Correct the problemidentified in DFS0730I and run the job again.

Reason Code = E0 PSTBYTNM POINTS TO FREESPACE - TWIN BACKWARD POINTER IS BROKEN

Explanation: During an index rebuild request,a twin backward pointer was encountered thatpointed into free space.

System action: The job terminates.

Programmer response: Take one of the followingactions:

• Run Batch Backout to correct the incompletesegments.

• Run Pointer Checker, correct the broken pointers,and then run Index Build again.

REASON CODE = E1 PSTBYTNM POINTS TO FREESPACE - TWIN FORWARD POINTER IS BROKEN

Explanation: During an index rebuild request, atwin forward pointer was encountered that pointedinto free space.





REASON CODE = E2 TWIN BACKWARD POINTERDOES NOT POINT TO THE PREVIOUS ROOTSEGMENT

Explanation: During an index rebuild request,a twin forward pointer was encountered whilescanning the twin backward chain that did notpoint to the previously scanned root segment.





REASON CODE = E3 TWIN FORWARD POINTERDOES NOT POINT TO THE PREVIOUS ROOTSEGMENT

Explanation: During an index rebuild request, atwin forward pointer that did not point to thepreviously scanned root segment was encounteredwhile scanning the twin forward chain.





Reason Code = E4 DL/I GN processing returned anunexpected status code &statcode

Explanation: DL/I returned a status codeindicating an error. Usually other system messagesappear in the job output. You can check the statuscode in the DL/I status code information.

System action: The job step is terminated.

Programmer response: Correct the conditionsindicated by the status code and any other relatedmessages.

REASON CODE = F0 GETMAIN ERRORENCOUNTERED 1LOADING ILDS WITHDDNAME=ddname. GETMAIN RC=nnnnnnnnREASON= yyyyyyyy

Explanation: Module DFSURIT0 encountered anerror allocating storage while rebuilding the ILDSidentified in the message text. The error occurredwhile the HALDB Index/ILDS Rebuild utility 1(DFSPREC0) was loading the ILDS by using the freespace option.


The ILDS that encountered the error.nnnnnnnn

The return code in register 15 when the erroroccurred. If an abend occurred, this is theabend code.

yyyyyyyyThe reason code. If an abend occurred, thereason code is blank.


System action: Processing terminates with returncode 8. DBRC flags the ILDS as RecoveryNeeded in the RECON data set.

Programmer response: Correct the problemindicated or change the SYSIN statement to omitthe free space option by removing the suffix letterF from either the BOTHF parameter or the ILEFparameter, and run the DFSPREC0 utility again.

Module: DFSPREC0

REASON CODE = F1 FREEMAIN ERRORENCOUNTERED LOADING ILDS WITHDDNAME=ddname. FREEMAIN RC= nnnnnnnnREASON= yyyyyyyy

Explanation: Module DFSURIT0 encountered anerror freeing previously allocated storage whilerebuilding the ILDS identified in the message text.The error occurred while the HALDB Index/ILDSRebuild utility (DFSPREC0) was loading the ILDSby using the free space option.


The ILDS that encountered the error.nnnnnnnn





Module: DFSPREC0

REASON CODE = F2 VSAM ERROR ENCOUNTEREDLOADING ILDS WITH DDNAME=ddname. VSAM RC=nnnnnnnn REASON= yyyyyyyy

Explanation: Module DFSURIT0 encountered aVSAM error while rebuilding the ILDS identifiedin the message text. The error occurred while theHALDB Index/ILDS Rebuild utility (DFSPREC0) wasloading the ILDS by using the free space option.


The ILDS being loaded when the erroroccurred.

nnnnnnnnThe return code in register 15 when the erroroccurred. If an abend occurred, this is theabend code.


System action: Processing terminates with returncode 8. If the ILDS is not usable, DBRC flags theILDS as Recovery Needed in the RECON dataset.


Module: DFSPREC0

REASON CODE = F3 LOAD ERROR ENCOUNTEREDLOADING MODULE module name. LOAD RC=nnnnnnnn REASON= yyyyyyyy

Explanation: Module DFSURIT0 encountered anerror loading the module identified in the messagetext while rebuilding the ILDS identified in themessage text. The error occurred while the HALDBIndex/ILDS Rebuild utility (DFSPREC0) was loadingthe ILDS by using the free space option.






Module: DFSPREC0

REASON CODE = F4 INTERNAL SORT ERRORENCOUNTERED SORTING ILES, INTERNAL SORTRC= nnnnnnnn REASON= yyyyyyyy

Explanation: Module DFSURIT0 encountered aninternal sort error while the indirect list entries(ILEs) were being sorted before being loaded intoan ILDS by the HALDB Index/ILDS Rebuild utility(DFSPREC0) using the free space option.






Programmer response: Document the error andcontact IBM Software Support. Change the SYSINstatement to omit the free space option byremoving the suffix letter F from either the BOTHFparameter or the ILEF parameter, and run theDFSPREC0 utility again.

Module: DFSPREC0

REASON CODE = F5 DSPSERV ERRORENCOUNTERED, DSPSERV RC= nnnnnnnn REASON=yyyyyyyy

Explanation: Module DFSURIT0 encountered aDSPSERV data space error while the HALDB Index/ILDS Rebuild utility (DFSPREC0) was rebuilding anILDS using the free space option.





Programmer response: Correct the indicated erroror change the SYSIN statement to omit the freespace option by removing the suffix letter Ffrom either the BOTHF parameter or the ILEFparameter, and run the DFSPREC0 utility again.The DFSPREC0 utility requires four data spacesof 2 gigabytes each to execute when usingthe free space option. Check with your systemadministrator to ensure that the DFSPREC0 utilitycan allocate enough storage. In addition, ensurethat the paging subsystem is sufficient to handlethe paging that is required by the DFSPREC0 utilitywhen using the free space option.

Module: DFSPREC0


DFS1983W APPC/IMS OUTBOUND LUXXXXXXXX NOT DEFINED

ExplanationAn outbound LU has been defined to IMS but couldnot be activated because it is not one of the APPC/IMSscheduled LUs.



Module:DFS6ECT0

DFS1985I APPC/IMS OUTBOUND LUxxxxxxxx ACTIVE

ExplanationAn outbound logical unit (LU) was identified to IMS. Inthe message text, xxxxxxxx is the identified LU.

System actionThe LU specified by xxxxxxxx is used for outboundconversations.


Module:DFS6ECT0

DFS1986 KEYRANGE TOO LONG,TRUNCATING

ExplanationThis message is displayed when you input one or moreKEYRANGE values that are longer than the key valuesin the database.

System actionThe DFSMAID0 utility truncates the KEYRANGE to theappropriate size. Processing continues.




Module:DFSMAID0

DFS1987I REASON CODE = rc message_text

ExplanationAn error occurred running one of the following utilities:

• ACB Generation and Catalog Populate utility(DFS3UACB)

• HALDB Partition Data Set Initialization utility(DFSUPNT0)

For an explanation of the error and possible solutionsto the error, find the return code of the error messagein the following list.

REASON = 01 SYSPRINT DD STATEMENT REQUIREDFOR STAND ALONE EXECUTION

Explanation: The IMS program controller moduleDFSRRC00 did not start the utility because theutility JCL does not include a SYSPRINT DDstatement. A SYSPRINT data set is required.



Module: DFSUPNT0, DFS3UACB.

REASON = 02 SYSPRINT DD DUMMY NOT ALLOWEDFOR STAND ALONE EXECUTION

Explanation: The IMS program controller moduleDFSRRC00 did not start the utility because aSYSPRINT DD DUMMY is specified in the utility JCLinstead of a SYSPRINT data set. A SYSPRINT dataset is required.




REASON = 03 AN ERROR OCCURRED OPENING THESYSPRINT DATASET

Explanation: The utility encountered an erroropening the SYSPRINT data set.


User response: Check the system messages in thejob log to determine the cause of the error andcorrect it.


REASON = 04 A GETMAIN ERROR OCCURREDExplanation: The utility encountered an errorwhile obtaining storage.


User response: Increase the region size for the jobor decrease the number of SYSIN statements.


REASON = 05 ERROR LOADING MODULE&modulename

Explanation: The utility encountered an errorwhile loading the module &modulename.


User response: Place the specified module in theLOADLIB concatenation for this job step.


REASON = 06 DBRC INITIALIZATION FAILED FORPHASE 1

Explanation: The utility encountered an errorduring phase 1 initialization of DBRC.


User response: Examine the job log for additionalmessages to determine and correct the cause ofthe error.


REASON = 07 DBRC INITIALIZATION FAILED FORPHASE 2

Explanation: DFSUPNT0 encountered an errorduring phase 2 initialization of DBRC.

System action: Processing halts and return code isset to the internal DBRC error code.

User response: Contact IBM Software Support.

Module: DFSUPNT0.

REASON = 08 AN ERROR OCCURRED OPENING THEDFSOVRDS DATASET

Explanation: DFSUPNT0 encountered an erroropening the data set specified by the DFSOVRDSDD statement.


User response: Examine the job log for additionalinformation about the error and correct it.

Module: DFSUPNT0.


REASON = 09 AN ERROR OCCURRED OPENING THEDFSRESLB DATASET

Explanation: DFSUPNT0 encountered an erroropening the data set specified by the DFSRESLBDD statement.



Module: DFSUPNT0.

REASON = 10 IMS INTERNAL ERROR - DYNAMICPSB IS CORRUPTED

Explanation: DFSUPNT1 or DFSUPNT2encountered and invalid PCB control block in theparameter list passed by IMS. The error is returnedto DFSUPNT0.



Module: DFSUPNT1, DFSUPNT2.

REASON = 11 DL/I PINT CALL RETURNEDUNEXPECTED STATUS CODE = &statuscode

Explanation: DFSUPNT0, DFSUPNT1, orDFSUPNT2 encountered an invalid status code(&statuscode) returned from IMS for the internalDL/I PINT call.


User response: Examine the job log for additionalinformation about the error and correct it. Ifthe problem cannot be determined, contact IBMSoftware Support.

Module: DFSUPNT0, DFSUPNT1, DFSUPNT2.

REASON = 12 ESTAE HAS DETECTED AN ABENDRESULTING FROM ATTACH OF DFSRRC00

Explanation: The ESTAE routine was driven for theutility due to an abend of the attached IMS system.


User response: Examine the job log for additionalinformation about the error and correct it. Ifthe problem cannot be determined, contact IBMSoftware Support.


REASON = 13 A SYSIN DD CARD IS REQUIRED TOEXECUTE DFSUPNT0 STAND ALONE

Explanation: DFSUPNT0 was not started by theIMS program controller module DFSRRC00. ASYSIN data set is required, but no SYSIN DDstatement was found in the JCL.



Module: DFSUPNT0.

REASON = 14 SYSIN DD DUMMY NOT ALLOWED FORSTAND ALONE EXECUTION

Explanation: DFSUPNT0 was not started by theIMS program controller module DFSRRC00. ASYSIN data set is required, but a SYSIN DDDUMMY statement was found in the JCL.



Module: DFSUPNT0.

REASON = 15 NO SYSIN STATEMENTS FOUNDExplanation: DFSUPNT0 was not started by theIMS program controller module DFSRRC00. TheSYSIN data set is empty.



Module: DFSUPNT0.

REASON = 16 AN ERROR OCCURRED OPENING THESYSIN DATASET

Explanation: DFSUPNT0 encountered an erroropening the SYSIN data set.


User response: Check the job log for additionalmessages and correct the error condition.

Module: DFSUPNT0.

REASON = 19 THE DFSOVRDS DD CARD HAS ANINVALID INPUT

Explanation: You can only use DD DUMMY ora character string that contains INITALL in theDFSOVRDS DD card. Any other input is invalid.


User response: Enter a valid input string for theDFSOVRDS DD card.

Module: DFSUPNT0.


REASON = 20 PARTITION SELECTION FAILEDExplanation: Before initializing the partition,DFSPSEL was called to mark the partition asempty. This call was unsuccessful. The partitioninitialization could not be completed.



Module: DFSUPNT0.

REASON = nn UNEXPECTED ERROR -INITIALIZATION INTERNAL LOGIC ERROR

Explanation: The utility encountered anunexpected logic error.

System action: Processing halts and return codeis set to 99. The reason code has meaning only toIMS support personnel.



Module:DFS3UACB, DFSUPNT0, DFSUPNT1, DFSUPNT2

DFS1988W OTMA input messages frommember yyyyyyyy have reachedxx% of the maximum active inputmessage limit zzzz

ExplanationOTMA internally creates a Transaction Instance Block(TIB) to track each active input message from amember. A maximum number of TIBs can be specifiedby OTMA descriptor, client-bid protocol message,or /START TMEMBER INPUT command. The activeor queued input message from member yyyyyyyy isreaching xx percent of the limit indicated by zzzz.This message is issued at 80% of TIB limit and every5% thereafter. Potentially, an OTMA message floodcondition exists.

To view the current limit, issue the /DISPLAYTMEMBER command.

System actionIMS OTMA continues to process new input messageswith less storage.

Programmer responseDetermine whether the dependent regions are activeto process input messages, whether the remotetransactions insert back to the I/O PCB, and whetherthe OTMA clients are flooding the IMS. You mightneed to control or stop the OTMA clients to prevent

the flood conditions. Ensure that the IMS regions arestarted to run the OTMA transactions. You can usethe /DISPLAY TMEMBER TPIPE command to displaythe input message counts. If needed, contact your IMSsystem programmer for assistance.

Module:DFSYFD00

DFS1989E OTMA input messages frommember yyyyyyyy have reachedthe maximum active inputmessage limit zzzz

ExplanationAn OTMA message flood condition exists for memberyyyyyyyy. The input messages have reached a defaultor client specified Transaction Instance Block (TIB)limit, indicated by zzzz.

System actionIMS OTMA rejects any new input messages from themember until free TIBs are available.

Programmer responseDetermine the following:

• Whether the input transactions are processed bydependent regions

• Whether the remote transactions insert back to theI/O PCB

• Whether the OTMA clients are flooding the IMS

You might need to control or stop the OTMA clientsto prevent the flood conditions. Ensure that the IMSregions are started to run the OTMA transactions. Youmight need to contact the IMS system programmer forassistance. Also, you can use the /DISPLAY TMEMBERTPIPE command to display the input message counts.

Module:DFSYFD00

DFS1990I {LQB|RCNT} CONTROL BLOCKSINITIALIZATION FAILED

ExplanationA major error occurred while attempting to initializethe CNT/SPQB/RCNT control blocks within moduleDFSCLCms, DFSCLSms, DFSCLRms, or DFSCLIDs. TheLQB control block includes the CNT and SPQB controlblocks. The following modules are shown with theircorresponding control blocks, and the system ID table(SID).Module

Control block or table


DFSCLCmsCNT

DFSCLSmsSPQB

DFSCLRmsRCNT

DFSCLIDsSID

Variable m completes the module name and has avalue from 0 to 9 or A to F. Variable s representsthe nucleus suffix. Check for consistency between theexecution JCL and system definition for the correctnucleus suffix and the IMS.SDFSRESL name.


Programmer responseCorrect any inconsistency between system definitionand execution JCL.


Module:DFSIINU0


DFS1991I {LOAD|LOCATE} ERROR FORLQB/RCNT CONTROL BLOCKS(modulename), RC=xx.

ExplanationAn IMS IMODULE LOAD or LOCATE failed for moduleDFSCLCms, DFSCLSms, DFSCLRms, or DFSCLIDs thatis substituted for the variable modulename. Eachmodule contains a control block, or System ID table(SID), as shown in the following list. The LQB controlblock includes the CNT and SPQB control blocks.Module

Control block or tableDFSCLCms

CNTDFSCLSms

SPQBDFSCLRms

RCNT

DFSCLIDsSID

Variable m completes the module name and has avalue from 0 to 9 or A to F. Variable s represents thenucleus suffix.

The return code (xx) indicates the nature of the error.For the explanations of the IMODULE return codes, seethe IMODULE return code information.


Programmer responseCorrect the error condition indicated by the returncode.


Module:DFSIINU0


DFS1992I GETMAIN ERROR FOR UNIQUEVTAM HASH TABLE RC=rc

or

GETMAIN ERROR FOR {CNT/LNB/RCNT|SPQB}BLOCKS {HASH TABLE|BIT MAP} RC=rc

ExplanationThe first form of the message appears when thesystem attempts to acquire a block of storage for theunique VTAM hash table and receives a failing returncode from the GETMAIN routine. The VTAM hash tableis for static signon user IDs.

The second form of the message appears when IMSfails to obtain storage for the hash table shown duringinitialization. The return code is passed by the failingGETMAIN.





System actionIMS abnormally terminates with abend 0016.


System programmer responseFor the first form of the message, correct the storagecondition. For the second form of the message,increase the available storage to the IMS controlregion if dynamic resources are required.



DFS1993X GETMAIN ERROR FOR {LGND|USRD} BLOCKS HASH TABLE,RC=nn

or

GETMAIN ERROR LOADING DYNAMIC TERMINALDESCRIPTORS, RC=nn

ExplanationIMS initialization was unsuccessful attempting toobtain storage for one of three hash tables, for a workarea, or for the default logon and user descriptors fortemporary control blocks.

The first form of the message appears when storage isunavailable for the hash tables, and the second formappears when storage is unavailable for the work areaor descriptors. LGND is shown if the failure was forthe logon descriptor hash table. USRD is shown if thefailure was for either the user descriptor hash table orthe LTERM descriptor hash table.



System programmer responseIf dynamic resources are required, increase theavailable storage to the IMS control region.



DFS1994I UNRESOLVED CQSPUT FROMUOWE(S) DURING xxx.QNAME=nnnnnnnnnnnnnnnnUOWSTCK=ssssssssssssssssTIME=jjj,hh.mm.ss

ExplanationThis informational message is issued during IMScheckpoint or IMS shutdown.

In the message text:xxx

Indicates when this message is issued.CHECKPOINT

The message is issued during a simplecheckpoint if CQSPUT fails during UOWEcleanup.

SHUTDOWNThe message is issued during normal IMSshutdown if a UOWE occurs with a CQSPUTrequest.

nnnnnnnnnnnnnnnnThe destination queue for the oldest unresolvedCQSPUT UOW. If the destination queue namecontains all printable EBCDIC characters, QNAMEis an 8-byte value that contains this printablequeue name. If the destination queue namecontains any non-printable characters, QNAME isa 16-byte value that contains the queue name inhexadecimal.

ssssssssssssssssThe type 01/03 log record's UOW store clocktoken, MSGPROTK. This value corresponds to thetime that the message was inserted to QueueManager.

jjj,hh.mm.ssThe store clock value from UOWSTCK, converted tojjj,hh.mm.ss format, where jjj is the Julian day ofthe year, and hh.mm.ss is the time of day.




System actionIMS continues with checkpoint or shutdownprocessing.

Operator responseIf this message is issued during normal shutdown,restart IMS with a warm start. If a warm restart is notused, messages might be lost. If you must cold restartIMS, take a simple checkpoint before shutting down.

If you must cold restart IMS and this message isissued during simple checkpoint, do not shut downIMS until the problem processing the UOWE isresolved. For example, checkpoint processing mightnot resolve the problem if a CF overflow full conditionstill exists.

IMS might need to retrieve a message from the systemlog data set (SLDS) to try a failed CQSPUT. If theSLDS is unavailable, IMS might issue DFS1994I aftera simple checkpoint. You must resolve the situationwith the SLDS to allow the messages to be retrievedand PUT to the Message Queue Structure.

DFS1995E explanation

ExplanationThis message follows message DFS1965E andexplains the return and reason code of theprevious DFS1965E message. DFS1995E includes theAPPC/MVS error message, which starts with prefixATB, as provided by the APPC/MVS Error ExtractService.

Related referencez/OS: Types of error information thatError_Extract returnsRelated informationDFS1965EAPPC/MVS CALL FAILURE,FUNCTION=aaaaaaaa, REASON CODE=xxyy,RETURN CODE=xxxxxxxx, LUNAME=nnnnnnnn

DFS1996I GETMAIN ERROR FOR VTAMTERMINAL CONTROL BLOCKS<HASH TABLE|DREF STORAGE>,RC=xx

ExplanationIMS was unable to acquire enough storage in the IMScontrol region extended private area in one of thefollowing:

• In subpool 0 to build a VTCB hash table, or• In subpool 214 for loading the VTAM control blocks

(VTCBs).

For an explanation of the IMODULE GETMAIN returncode xx, see the IMODULE return code information.

System actionIMS terminates with 0016.

Programmer responseTry to restart IMS when more storage is available.

Related referenceIMODULE return codes (Messages and Codes)Related informationIMS abend 0016

DFS1997I INCOMPATIBLE COMPONENT OFACF/VTAM INSTALLED

ExplanationThe component identifier information from VTAMOPEN ACB processing showed that the ACF/VTAMcomponent is not compatible with the level of IMS.If IMS is generated for MVS/370, then an MVS/370component of ACF/VTAM is required; if IMS isgenerated for MVS, then an MVS component of ACF/VTAM is required.

System actionIMS issues a VTAM CLOSE ACB, making VTAMcommunication impossible.

Operator response:If the wrong component of ACF/VTAM is active, firstterminate ACF/VTAM and then initialize the correctcomponent. After the correct component of ACF/VTAMis active, issue the /START DC command.

Programmer responseEither redefine IMS to execute with the ACF/VTAMcomponent you are using, or install an ACF/VTAMcomponent that matches the IMS level.



DFS1998I VTAM TERMINAL CONTROL BLOCKINITIALIZATION FAILED


http://www-01.ibm.com/support/knowledgecenter/SSLTBW_2.4.0/com.ibm.zos.v2r4.ieac300/ieac300142.htm?lang=en

http://www-01.ibm.com/support/knowledgecenter/SSLTBW_2.4.0/com.ibm.zos.v2r4.ieac300/ieac300142.htm?lang=en



ExplanationAn error occurred while attempting to initialize theVTAM terminal control blocks contained in modulesDFSCLVyx where:

y is a value from 0 to 9.x is the IMS nucleus suffix.

The execution JCL might not be consistent withthe system definition for the nucleus suffix and theSDFSRESL name.


Programmer responseCorrect any inconsistency between the execution JCLand the system definition.



DFS1999I {LOAD|LOCATE|BLDL} ERROR FORVTAM TERMINAL CONTROLBLOCKS (modulename), RC=xx

ExplanationA BLDL or an IMS IMODULE LOAD or LOCATE failed formodule DFSCLVyx in subpool 251 where:

y is a value from 0 to 9 or A to F.x is the IMS nucleus suffix.

DFSCLVyx contains some or all of the IMS terminalcontrol blocks for VTAM sessions, except those forMSC/VTAM links. For an explanation of the IMODULEreturn code xx, see the IMODULE return codeinformation.


Programmer responseCorrect the error based on the IMODULE return code.



DFS2000I OPNDST ACQUIRE FAILED NODE x.SUBPOOL zzzzzzzz SENSE=yyyy

ExplanationAn OPNDST with the ACQUIRE option was issued forVTAM node x. The OPNDST was not successful. Thevariable zzzzzzzz is the subpool name or N/A if there isno subpool.

System actionThe IMS operation continues without the terminal.

Operator response(master terminal) Log the node onto IMS byusing the /OPNDST command or VTAM's 'VARYNET,ID=,LOGON=' command.

Problem determinationUse the VTAM D NET command to determine why thenode is not available for allocation to IMS.







DFS2001I OPNDST ACCEPT FAILED NODE x.USER zzzzzzzz SENSE=yyyy | |RCFBK=xxxx

ExplanationIMS tried to issue a VTAM OPNDST with the ACCEPToption, but it was unsuccessful. VTAM previously toldIMS that the terminal was available for OPNDST.

In the message text:zzzzzzzz

The user name or N/A if there is no useryyyy

The value is the VTAM sense codexxxx

The value is the VTAM return code and feedback(RCFBK=) if specified

System actionIMS operation continues without the node.

Operator response:(master terminal) Determine why VTAM refused theOPNDST by using the VTAM D NET command; then tryagain.

DFS2002I OPNDST RESTORE FAILED NODE x.SUBPOOL zzzzzzzz SENSE=yyyy

ExplanationIMS tried to issue a VTAM OPNDST with the RESTOREoption, but it was unsuccessful. VTAM previously toldIMS that the terminal was available for OPNDST. Theyyyy value is the VTAM SENSE CODE; zzzzzzzz is thesubpool name or N if there is no subpool.

System actionIMS operation continues without the node.

Master terminal operator response: Determine whyVTAM refused the OPNDST by using the VTAM D NETcommand; then retry.

DFS2003 CLSDST FAILED NODE x.

ExplanationIMS attempted to issue a VTAM CLSDST for NODE x,but was unsuccessful. The node is deactivated, and isno longer usable.

System actionNode x is deactivated, and is no longer usable.

Problem determinationDetermine why the CLSDST failed. If necessary,perform VTAM problem determination.

DFS2004 PERMANENT ERROR-CLSDSTREQUIRED NODE x.

ExplanationVTAM has informed IMS, either by RPL posting orscheduling of the IMS LOSTERM exit, that IMS shouldCLSDST the named terminal.

System actionIMS issues a CLSDST for the node.

DFS2005 PERMANENT ERROR-CLSDSTISSUED NODE x.

ExplanationAfter receiving input, the device-dependent modulehas determined that VTAM or the terminal has sent anincorrect or missing AID byte to IMS in the input bufferfor node x.

System actionIMS issues a VTAM CLSDST, and performs no furtheroperations.

Operator response:(master terminal) If appropriate, correct the cause ofthe error, and reconnect the terminal to IMS, usingthe /OPNDST command.

DFS2006 PERMANENT ERROR-NO CLSDSTALLOWED NODE x.


ExplanationA permanent error has occurred. VTAM's returncode or LOSTERM value indicates that no CLSDST isallowed.

System actionIMS processing continues without the terminal. Thenode is deactivated such that no further operations byIMS are possible.

Operator response:(master terminal) If appropriate, correct the error, andrestart IMS.

DFS2007 OPNDST PROCESSOR FAILURENODE x.

ExplanationModule DFSCVCLO has detected an unexpected returncode—FDB2 value on an OPNDST instruction. TheOPNDST was unsuccessful.

System actionIMS idles the terminal.

Operator response:(master terminal) Another /OPNDST, VTAM VARYNET, or LOGON command can be attempted.

Problem determinationTurn on IMS trace, and reproduce the problem.

DFS2008 INPUT IGNORED-ERRORMESSAGE CANCELED

ExplanationThis is caused by an operator error. Terminal inputwas attempted while IMS was trying to send an errormessage for the immediately-previous input operation.

For a bisync 3270 VTAM device, the operator mighthave entered input whose length was greater than thelength defined for that terminal.

System actionThe input is ignored. The terminal is available forfurther use.

Operator response:Do not enter data without waiting for a response to theprevious entry.

Problem determinationTurn on IMS trace for the node, and reproduce theproblem.

If the entered data was too long, verify that theRECEIVE ANY buffer size specified on the COMMmacro is large enough to handle the length of databeing entered.

DFS2009 INPUT IGNORED

ExplanationThis is caused by an operator error or input that is notsupported by IMS from a 3270 display.

For the case of invalid input, IMS has received triggerfield, input from the terminal when the MFS bypassis not being used. Trigger fields are not supported byMFS and trigger field input will be accepted by IMSonly if the MFS bypass facility is being used on inputreceived from the terminal.

For a bisync 3270 VTAM device, the operator mighthave entered input whose length was greater than thelength defined for that terminal.

System actionFor an invalid trigger field, the input is discarded andcommunication with the terminal continues normally.An error record is written on the IMS log data set at thetime of the failure.

Operator response:The screen should be reformatted with a format thatdoes not have trigger fields defined or the transactionentered must be one that uses the MFS bypass facilityof IMS.

Problem determinationIf reformatting the screen or entering anothertransaction is not possible, contact your systemprogrammer for assistance.

If the entered data is too long, verify that the RECEIVEANY buffer size specified on the COMM macro is largeenough to handle the length of data being entered.

DFS2010 VTAM NOT SUPPORTED

ExplanationThe NODE keyword was entered in a command, butVTAM is not included in the current system.



Operator response(terminal) Reenter the command correctly.

Problem determination36; also, if VTAM nodes are included during IMSsystem definition, perform a /DIS NODE ALL, savethe output.


DFS2011I IRLM FAILURE - IMS QUIESCING

ExplanationThe lock manager status exit is given control anddetects that the IRLM is terminating. This event causesthe discontinuation of the use of all databases.

System actionIMS pseudoabends all currently scheduledtransactions with abend 3303. Full-function databasesparticipating in data sharing (share level 1, 2, or3) and Fast Path databases participating in blocklevel data sharing (share level 1, 2, or 3) areclosed. Their authorization is discontinued. All furthertransaction scheduling, except Fast Path, is prohibited.All terminals inputting Fast Path transactions wait untilIRLM is restarted and IMS reconnects to it.

Every dependent region with an intent to usea database must go through terminate threadprocessing. That is, any such dependent region thatdoes not terminate prevents IMS from completingthe actions necessary to clean up from the IRLMfailure. IMS cannot be reconnected to the IRLM orterminated until all such region disconnect procedureshave occurred. Wait for input (WFI) transactions aregiven a QC status code or pseudoabended with aU3303 on their next database call. There are timing-related conditions at the time of the IRLM failure whenthe application programs currently running can receivethe BA, BB, or FH status code.

Programmer responseRestart the IRLM and have the system consoleoperator modify IMS specifying RECONNECT. The onlyother allowable response is to issue /CHECKPOINTFREEZE to terminate IMS.

When the IRLM has been restarted and IMSreconnected to it, start all databases stopped because

of this failure. Also, BMP regions might need to berestarted.



DFS2012I GLOBALLY SHARED DATA BASE|AREA - dbdname|areanameSTOPPED.

or

SHARING DATA BASE(S) STOPPED BECAUSE DATASHARING DISCONTINUED

ExplanationOne of the above two messages is generated. Thefirst message lists the sharing databases that stoppedbecause data sharing was discontinued.

The second message is generated for each databaseor area which is globally shared on multiple IRLMsand the IRLM has entered the IRLM FAILED or COMMFAILED state. When database integrity cannot beensured, databases or areas which are globally sharedand authorized by IMS systems on the other IRLM, arestopped using an internal /DBR or /STOP command,and all applications currently using these databases orareas are pseudoabended by abend 3303.

System actionIMS execution continues.

Programmer responseWhen the action is taken as described in messageDFS2011I, the databases listed by this messageshould be started using the /START command, toallow the scheduling of the transaction for thesedatabases or opening of the areas.

Related information“DFS2011I” on page 591IRLM FAILURE - IMS QUIESCING

DFS2013 NUMBER OF RECORDS IN QBLKSDATA SET HAS EXCEEDED UPPERTHRESHOLD


ExplanationIMS has established an upper threshold for thenumber of records which can be assigned to theQBLKS data set before warning message DFS2013is issued. This threshold is some percentage of themaximum number of records assignable before anautomatic shutdown is initiated.

System actionIMS continues execution.

Programmer responseYou might want to reduce the queue usage and avoida possible shutdown. To determine the effect of thisaction, examine the percentage of use displayed bythe /DIS POOL command. When the number ofrecords assigned to the QBLKS data set drops belowthe lower threshold established by IMS, messageDFS2016 will be issued.

DFS2014 NUMBER OF RECORDS IN SMSGQDATA SET HAS EXCEEDED UPPERTHRESHOLD

ExplanationIMS has established an upper threshold for thenumber of records that can be assigned to the SMSGQdata set before issuing this warning message. Thisthreshold is some percentage of the maximum numberof records assignable before an automatic shutdown isinitiated.


Programmer responseYou might want to reduce the queue usage and avoida possible shutdown. To determine the effect of thisaction, examine the percentage of use displayed bythe /DIS POOL command. When the number ofrecords assigned to the SMSGQ data set drops belowthe lower threshold established by IMS, messageDFS2017 is issued.

Related information“DFS2017” on page 592NUMBER OF RECORDS IN SMSGQ DATA SET ISNOW BELOW LOWER THRESHOLD

DFS2015 NUMBER OF RECORDS IN LMSGQDATA SET HAS EXCEEDED UPPERTHRESHOLD

ExplanationIMS has established an upper threshold for thenumber of records which can be assigned to theLMSGQ data set before the warning message DFS2015is issued. This threshold is some percentage of themaximum number of records assignable before anautomatic shutdown is initiated.


Programmer responseYou might want to reduce the queue usage and avoida possible shutdown. To determine the effect of thisaction, examine the percentage of use displayed bythe /DIS POOL command. When the number ofrecords assigned to the LMSGQ data set drops belowthe lower threshold established by IMS, messageDFS2018 will be issued.

DFS2016 NUMBER OF RECORDS IN QBLKSDATA SET IS NOW BELOW LOWERTHRESHOLD

ExplanationIMS has established a lower threshold which thenumber of records assigned to the QBLKS dataset must pass after the upper threshold has beenexceeded. Passing this lower threshold will resultin this message being issued. This threshold issome percentage of the maximum number of recordsassignable before an automatic shutdown is initiated.


Programmer responseThe action to reduce the queue usage may cease.

DFS2017 NUMBER OF RECORDS IN SMSGQDATA SET IS NOW BELOW LOWERTHRESHOLD

ExplanationIMS has established a lower threshold which thenumber of records assigned to SMSGQ data set mustpass after the upper threshold has been exceeded.Passing this lower threshold will result in this messagebeing issued. This threshold is some percentage ofthe maximum number of records assignable before anautomatic shutdown is initiated.




DFS2018 NUMBER OF RECORDS IN LMSGQDATA SET IS NOW BELOW LOWERTHRESHOLD

ExplanationIMS has established a lower threshold which thenumber of records assigned to LMSGQ data set mustpass after the upper threshold has been exceeded.Passing this lower threshold will result in this messagebeing issued. This threshold is some percentage ofthe maximum number of records assignable before anautomatic shutdown is initiated.



DFS2020 VTAM STORAGE ALLOCATIONFAILURE RTNCD=8.

ExplanationThe VTAM return code from SETLOGON macroindicated a storage allocation failure.

System actionThe IMS system continues; START DC failed.

Programmer responseCheck VTAM errors for SETLOGON macro.

DFS2021 VTAM INACTIVE TO THISAPPLICATION RTNCD=10 FDB2=D.

ExplanationThe VTAM return code from SETLOGON macroindicated that VTAM was inactive to this application.



DFS2022 VTAM ABEND CONDITIONOCCURRED ON THE USER TCBRTNCD=10 FDB2=E.

ExplanationThe VTAM return code from SETLOGON macroindicated that a user abend condition occurred.



DFS2023 NON-VTAM REQUEST RTNCD=14FDB2=0.

ExplanationThe VTAM return code from SETLOGON macroindicated a non-VTAM request was issued.



DFS2024 VTAM CONTROL BLOCK INVALIDRTNCD=14 FDB2=10.

ExplanationThe VTAM return code from SETLOGON macroindicated an invalid VTAM control block.



DFS2025 VTAM CID INVALID RTNCD=14FDB2=13.

ExplanationThe VTAM return code from SETLOGON macroindicated an invalid VTAM CID.




DFS2026 INSUFFICIENT STORAGEAVAILABLE IN MAIN POOL(WKAP) TO PROCESS COMMAND

ExplanationA command was not processed because of insufficientstorage in the main pool.

Important: The WKAP cannot be specified at systemdefinition time. System definition sets a value of5000. You can override the value at execution timeby the WKAP= operand on the IMS procedure or theDFSPBxxx member of IMS.PROCLIB.


Programmer responseDo one of the following actions:

• Increase the size of the main pool with the WKAPparameter in the JCL used to start IMS.

• Reenter the command later, since this problem canbe a temporary condition.

• Reduce storage requirements by reentering thecommand as multiple commands.

DFS2027I UNABLE TO OPEN VTAM ACBREG15=xx ACBERFLG=yyy.

ExplanationAn error code was returned when OPEN ACB wasattempted. xx is the OPEN return code in register 15and yyy is the ACB error field returned by VTAM. TheACBERFLG value yyy is displayed as a decimal number.

Important: If you are using multinode persistentsessions (MNPS), this message only refers to theAPPLID ACB.

System actionIMS continues without ACB being opened.

Programmer responseFor a detailed explanation of the error codes, see z/OSCommunications Server SNA Programming and z/OSCommunications Server IP and SNA Codes.

Related referencez/OS: OPEN-Open one or more ACBsz/OS: Open macroinstruction error fields

DFS2028 MONITOR KEYWORD PARAMETERMISSING.

ExplanationThe /TRACE SET ON or /TRACE SET OFF commandwas entered without any monitor parameters beingspecified.


Operator response:Reenter the command with the correct parametersspecified.

Module:DFSICLN4

DFS2029 MONITOR UNAVAILABLE.

ExplanationThe monitor cannot be used. The monitor log workarea was not successfully initialized.

Either an IMSMON DD statement is missing, or LOADmodules DFSIMNT0 or DFSMNTR0 are unavailable inthe proper library.


Operator response:Reenter the command after the monitor has beensuccessfully initialized.

Programmer responseEnsure that the monitor is successfully initialized.

Module:DFSICLN4

DFS2030 MONITOR ALREADY ACTIVE.

ExplanationThe /TRACE SET ON monitor command was enteredwhen the monitor was already activated.


http://www-01.ibm.com/support/knowledgecenter/SSLTBW_2.4.0/com.ibm.zos.v2r4.istprg0/opnacb.htm?lang=en

http://www-01.ibm.com/support/knowledgecenter/SSLTBW_2.4.0/com.ibm.zos.v2r4.cs3cod0/acbopen.htm?lang=en


Operator response:Use the /TRACE SET OFF MONITOR commandbefore repeating the /TRACE SET ON MONITORcommand.

Module:DFSICLN4

DFS2031 INVALID MONITOR KEYWORDPARAMETER.

ExplanationThe /TRACE SET ON MONITOR command wasentered with an invalid parameter for the monitorkeyword.


Operator response:Reenter the command using valid parameters.

Module:DFSICLN4

DFS2032 MONITOR NOT ACTIVE.

ExplanationThe /TRACE SET OFF MONITOR command wasentered when the monitor was not active.


Operator response:Do not use the /TRACE SET OFF MONITORcommand when the monitor is not on.

Module:DFSICLN4

DFS2033 PARLIM NOT DEFINED FOR THISTRANSACTION.

ExplanationThe PARLIM keyword was used in a command whenthe PARLIM option was not defined for the specifiedtransaction.


Remote terminal operator response: Correct thecommand, and reenter it.

DFS2034 INVALID PARLIM NUMBER.

ExplanationA parameter was entered for PARLIM keyword thatwas not 0 - 65535.


Remote terminal operator response: Correct thecommand, and reenter it.

DFS2035 UNABLE TO ASSIGN SPECIFIEDLTERM TO A PTERM DEFINEDMSGDEL=SYSINFO

ExplanationLTERM has messages queued on the system queue.


Terminal operator response: See that LTERM isassignable to specified PTERM.

DFS2036 UNABLE TO ASSIGN SPECIFIEDLTERM TO A PTERM DEFINEDMSGDEL=NONIOPCB

ExplanationLTERM has messages queued on the system orapplication output queue.


Operator response:See that LTERM is assignable to specified PTERM.

DFS2037 START DC HAS NOT BEENCOMPLETED

ExplanationA /START DC command must be completed before /OPNDST or /CLSDST can be done.


Operator response:Enter the /START DC command; then retry.


DFS2038 BUFFER POOL TOO SMALL FORCOMMAND

or

INSUFFICIENT STORAGE AVAILABLE TO PROCESSCOMMAND

ExplanationThe first form of the message is issued when acommand was not processed because of insufficientstorage.

The first form of this message can also be producedif there is insufficient CSA/ECSA available to hold theinternal tables associated with the/TRACE SET ONMONITOR command.


Programmer responseThis can be a temporary condition that can be resolvedby reentering the command later. If this fails, try toreduce the storage requirements by reentering thecommand as multiple commands or, if this is notpossible, notify the system programmer.

If this message is generated as a result of runningthe /TRACE SET ON MONITOR command, increasethe available CSA/ECSA.

Module:DFSICLN4

DFS2039I INSUFFICIENT STORAGE TOPROCESS GLOBAL STATUSUPDATE

ExplanationStorage is not available to process the global statusupdate after a DB or AREA GLOBAL command, thatwas not issued from the Operations Manager (OM) API.

System actionThe command is processed by each IMS to which themessage is sent. The global status is not updated.

Programmer responseThis condition can be temporary and might be resolvedby running the command again. If rerunning the

command fails, reduce the storage requirements byreentering the command as multiple commands. If thisis not possible, notify the system programmer.

Module:DBFARD10, DBFARD40, DFSDBDR0

DFS2040 DEVICE DEPENDENT LOGICERROR NODE x (USER y)

ExplanationA logic error was encountered during device-dependent processing of a VTAM I/O request. Theprobable causes of this problem are:

• A VTAM error occurred.• A hardware malfunction occurred.• A program logic error in the program at NODE x

occurred (programmable devices only).• An invalid specification to the IMS System Definition.• Unexpected VTAM system sense from the device.• Time expired on CLEAR request during RQR

processing.

System actionThe session established with NODE x or USER y isterminated. An IMS Log Record (X'67') containingpertinent information was produced with an ID ofCVCT.

Programmer responseWhen the problem is corrected the session can bereestablished by NODE x, USER y, or an IMS /OPNDSTcommand.



DFS2041 A PERMANENT ERRORENCOUNTERED NODE x

ExplanationThe SENSE information returned on a VTAM SEND/RECEIVE indicated NODE x was inoperable. Theprobable causes for this problem are:

• A VTAM logical unit status was received, or anexception response to a SEND command was


received with a SENSE command, indicating apermanent error (set by NODE x).

• Unsupported major or minor SENSE fields or the userSENSE indicated a component ID greater than 4.

• A hardware malfunction.

System actionThe session established for NODE x is terminated. AnIMS log record with an ID of CVCT containing pertinentinformation was produced.

Programmer responseWhen the problem is corrected, the session can bereestablished by a NODE x, or an IMS /OPNDSTcommand.



DFS2042 BAD VTAM RESPONSE,INDICATOR OR DATA [FMH | QEC| RELQ | QC | RSHUT | SHUTD| SHUTC | LUS (SENSE=xxxxxxxx)|RTR| SIG (SENSE=xxxxxxxx)|BID |SBI | BIS|UNDEF] NODE x (USER y)

ExplanationAn invalid or unsupported request was received asfollows:FMH

FM header parameter errorQEC

SNA quiesce-end-of-chain commandQC

Quiesce completeRELQ

SNA release quiesce commandRSHUT

SNA request shutdown commandSHUTD

SNA shutdown commandSHUTC

SNA shutdown complete commandLUS

SNA LUSTATUS command or associated sensecode (xxxxxxxx), or both

RTRSNA ready to receive command

SIGSNA signal command or associated sense code(xxxxxxxx), or both

BIDSNA BID command

SBISNA stop-bracket-initiation command

BISSNA bracket-initiation-stopped command

UNDEFAn undefined SNA command code was received

Possible causes of this problem are:

• A VTAM error occurred.• A hardware malfunction occurred.• A program logic error in the program at NODE

x occurred (programmable devices and remotesubsystems only).

• An invalid specification to the IMS system definition.

System actionThe session is terminated. An IMS log record(X'67') containing additional pertinent information wasproduced with an ID of CVCT.

Operator responseSee the Programmer response.

Programmer responseWhen the problem is corrected, the session can bereestablished by NODE x, USER y, or an IMS /OPNDSTcommand.



DFS2043 DATA CHAINING ERRORENCOUNTERED NODE x

ExplanationAn improper data chaining sequence was encounteredduring IMS output edit or on a VTAM Receive Any forNODE x. The probable causes of this problem are:

• A VTAM error occurred.


• A hardware malfunction occurred. A programlogic error in the program at NODE x occurred(programmable devices only).

• An IMS output message is either multisegment orlarger than the output buffer size for a device withoutchained output support.

System actionThe NODE x session was terminated. An IMS LogRecord with an ID of CVCT containing pertinentinformation was produced.

Operator responseSame as Programmer response.

Programmer responseWhen the problem is corrected, the session can bereestablished by a NODE x, or an IMS /OPNDSTcommand.



DFS2044 UNSUPPORTED RESPONSE WASREQUESTED NODE x (USER y)

ExplanationAn unsupported response was requested on a VTAMreceive. The probable causes of this error are:

• A hardware malfunction occurred.• A program logic error in the program at NODE x

occurred (programmable devices only).

System actionThe NODE x or USER y session is terminated. AnIMS Log Record (X'67') with an ID of CVCT containingpertinent information was produced.


Programmer responseWhen the problem is corrected, the session can bereestablished by a NODE x, USER y, or an IMS /OPNDST command.



DFS2045 AN INBOUND SEQUENCE ERRORDETECTED NODE x (USER y)

ExplanationThe sequence number received on a VTAMsynchronous request was not consecutive, that is, onegreater than the previous VTAM synchronization inputrequest received. The probable causes of this errorare:

• A VTAM error occurred.• A hardware malfunction occurred.• An error occurred within the control program at the

remote node.

System actionThe session established with NODE x or USER y isterminated. An IMS Log Record, containing pertinentinformation, was produced with an ID of CVCT.





DFS2046 ERROR FOUND WHILE WRITINGTO LOG NODE x (USER y)

ExplanationA device-dependent error was encountered whileattempting to create or write an IMS Log Record.The data being written contained VTAM sequencenumbers, the data necessary for emergency restartof NODE x or USER y, or both. For 3614 nodes,


the retention area might be too small to contain thecopy of a 3614 Transaction Request necessary for arecovery. The probable causes of this problem are:

• An I/O error occurred while writing to the IMS Log.• An invalid specification was made for the Receive

Any, Retention Area, or Output Buffer sizes duringIMS system definition.

For 3614 nodes, the retention area might be too smallto contain the copy of a 3614 Transaction Requestnecessary for recovery.

System actionThe NODE x or USER y session is terminated. An IMSLog Record with an ID of CVCT containing pertinentinformation was produced.


Programmer responseWhen the problem is corrected the session can bereestablished by a NODE x, USER y, or an IMS /OPNDST command.



DFS2047 A VTAM BRACKET ERROR WASENCOUNTERED NODE x (USER y)

ExplanationA VTAM bracket error was encountered on a VTAMreceive for NODE x or USER y. The probable cause ofthis error is that an only or first element in a chaineddata request did not include at least a VTAM begin-bracket indicator.

Under normal circumstances, this message doesnot occur for terminals that have successfullycommunicated with IMS. If this error occurs for a nodethat was recently added to the IMS network, ensurethat the terminal is properly defined. Also, ensure thatthe terminal has the correct VTAM log mode specifiedor defaulted through IMS or VTAM.

System actionThe NODE x or USER y session is terminated. AnIMS Log Record (X'67') with an ID of CVCT containingpertinent information was produced.

Operator response(entering terminal operator) Same as Programmerresponse.

Programmer responseWhen the problem is corrected, the session can bereestablished by a NODE x, USER y, or an IMS /OPNDST command.



DFS2048 UNABLE TO OUTPUT NODE x.

ExplanationIMS was unable to write to any component of NODE x.The probable cause of this error was that all availablecomponents have been set to an inoperative conditionas a result of user-supplied sense data in a previousVTAM exception RRN response or VTAM LU statusindicator. This condition is reset by a subsequentVTAM LU status indicator from the node or by IMS /STOP NODE x and /START NODE x commands.

System actionThe session established for NODE x is terminated. AnIMS Trace Log Record (X'67') with an ID of CVCT isproduced containing pertinent information.

Programmer responseWhen the problem is corrected, the session canbe reestablished by NODE x or an IMS /OPNDSTcommand.





DFS2049I PARALLEL SESSION NAME ERRORname1 name2 NODE x USER y ID z

ExplanationIMS detected an attempt to change a parallel sessionname on a negotiated bind reply received from aremote subsystem. The name sent on the bind isidentified by the user and ID names within themessage text. The name returned is identified by thename1 and name2 values within the message. Username and ID correspond to name1 and name2.

System actionThe attempt to initiate a session is rejected. An IMS logrecord (X'67'), containing pertinent information, wasprovided with an ID of CVCT.

Operator response:See Programmer response.

Programmer responseThe error might be in the initial session informationentered by the terminal operator, system definitioninformation within IMS or the remote subsystem, orboth. When the problem is corrected, the session canbe reestablished by NODE x, USER y, or an IMS /OPNDST command.



DFS2050 RESYNCHRONIZATION REJECTEDNODE x (USER y)

ExplanationNODE x or USER y rejected either the IMS sequencenumber or the sequence number of the IMS copy ofNODE xor USER y during session resynchronization.The probable cause of this error is that an invalidindication was returned on a VTAM set-and-testsequence number command to either the IMS Numberor the IMS copy of NODE x's or USER y's Number.

System actionThe NODE x or USER y session is terminated. An IMSTrace Log Record (X'67') with an ID of CVCT containingpertinent information was produced.

Operator response:(entering terminal operator) When the program iscorrected, the session can be reestablished by NODEx, USER y, or by an IMS /OPNDST command.

Programmer responseReview the CVCT log record to determine the cause ofthis resynchronization failure. After the source of theconflict has been corrected, reestablish the session. Itmight be necessary to reacquire the session cold fromboth sides and define the IMS terminal or link with theFORCSESS option.






DFS2051 RESYNCH FAILED DUE TO VTAMRC NODE x (USER y).

ExplanationResynchronization failed due to nonzero VTAM returncode, or feedback while sending a VTAM set-and-testor start-data-traffic indicator. The probable causes ofthis error are:

• A hardware malfunction occurred.• The program at NODE x (programmable devices only)

or the control program in NODE x sent an exceptionresponse to a VTAM set-and-test sequence numberor start-data-traffic indicator.

System actionThe session being established is terminated, and anIMS Trace Log Record (X'67') containing pertinentinformation was produced with an ID of CVCT.





DFS2052 UNSUPPORTED RESPONSE TORESYNCHRONIZATION NODE x

ExplanationNODE x returned an unsupported response toeither the IMS sequence number or the IMS copyof NODE x's sequence number during sessionresynchronization. The probable cause of this error isthat an unsupported request to a VTAM Set-and-Testsequence number command was received or a testnegative response was received as a response to theSet option on the IMS sequence number.

System actionThe NODE x session is terminated. An IMS trace logrecord (X'67') with an ID of CVCT containing pertinentinformation was produced.

Operator response:(entering terminal operator) When the problem iscorrected, the session can be reestablished by a NODEx, or an IMS /OPNDST command.

Programmer responseWhen the problem is corrected, the session can bereestablished by a NODE x, or an IMS /OPNDSTcommand. If the problem cannot be corrected atNODE x, an IMS /NRE is required before a session canuse NODE x.



DFS2053 UNRESOLVED REFERENCE TOREQUIRED USER EDIT NODE x.

ExplanationAn unresolved reference was encountered to arequired user edit routine.

System actionThe session attempting to be established for NODEx is terminated. An IMS trace log record (X'677')with an ID of CVCT is produced containing pertinentinformation.

Programmer responseThe IMS nucleus must be rebound with the correctuser edit routine.





DFS2054 SESSION TERMINATION FORCEDNODE x.

ExplanationA session termination was forced because of arecursive request for termination. The original requestwas made using the 3614 user edit routine as aresult of either an IMS /STOP NODE x or /CLSDSTcommand, or as a result of a VTAM Request Recoveryor Shutdown Request indicator received from the 3614user edit routine.

One of the following situations is the probable cause ofthis error:

• A hardware malfunction occurred.• A loop occurred between the 3614 user edit

routine and IMS because of improper use of returncode 8 (cancel I/O) for input or output data aftertermination was requested by entry vector 20 to the3614 user edit routine.

• After termination was requested from the 3614 useredit routine by entry vector 20, input was queuedby return code 0, 4, or 8. No output message wasproduced by the user message processing program.

System actionThe session established with NODE x is terminated.An IMS trace log record (X'67') containing pertinentinformation is produced with an ID of CVCT.

Programmer responseWhen the problem is corrected, the session can bereestablished by NODE x or by an IMS /OPNDSTcommand.



DFS2055 SESSION TERMINATED BY USEREDIT ROUTINE NODE x.

ExplanationA return vector from a user edit routine indicatedsession termination was required for NODE x.

System actionThe NODE x session is terminated. An IMS log recordwith an ID of CVCT containing pertinent informationwas produced.

Operator response:Same as Programmer response

Programmer responseWhen the problem, if any, is corrected, the sessioncan be reestablished by a NODE x or an IMS /OPNDSTcommand.



DFS2056 INPUT SEGMENT EXCEEDSMAXIMUM LENGTH.

ExplanationThe input deblocking routine has detected an inputmessage segment that spans more than two requestunits (no new line or forms feed character is detectedfor 3770/3767, or no deblock character detected forSLUTYPE1).

System actionThe input message is canceled and a record is writtenon the IMS log data set that contains the messagesegment in error.

Operator response:Reenter the message, ensuring that the correct formatis used.



DFS2057 DEBLOCKING CHARACTER NOTFOUND IN INPUT SEGMENT.

ExplanationInput was received from the 3770 card readercomponent and the deblocking routine scanned to theend of the input data without detecting a deblocking


character. Every card in the input data has to befollowed by an IRS character.

System actionThe input message in error is canceled, a recordcontaining the input message in error is written on theIMS log data set, and the session is terminated.

Operator response:Issue an /OPNDST command to the node, and trythe failing input message again. If the failure persists,follow the problem determination.



DFS2058 COMPONENT ID IN ERROR.

ExplanationInput was received. However the component ID inthe function management header (FMH) was invalid orthe input component was not defined on the terminalmacro at system definition, or an exception responsewas requested by a device on which IMS does notsupport the exception response request function.

System actionA record is written on the IMS log data set, containingthe input message in error, and the session isterminated.

Operator response:Try the failing input message again. If the errorpersists, follow the problem determination.

Programmer responseEnsure that the input device is defined properly to IMS.



DFS2059 FMH DID NOT INDICATE BODS OREODS.

ExplanationThe function management header in the input datastream from the 3770 did not indicate either thebeginning or the end of the data set.

System actionA record is written on the IMS log data set thatcontains the request unit in error, and the session isterminated.

Operator response:(master terminal) If the error persists, follow theproblem determination.



DFS2060 IPL REQUEST INVALID ON S/7BSC CONTENTION LINE xxxPTERM yyy.

ExplanationA System/7 attached to a bisynchronous (BSC)contention line transmitted an IPL request to IMS.

System actionIMS deactivates the transmitting System/7.

Operator response:Inform the system programmer.

Programmer responseCorrect the System/7 program or change the System/7attachment.

DFS2061I NODE NOT AVAILABLE FOROPNDST NODE x (USER y).

ExplanationAn unavailable condition was returned on a VTAMSIMLOGON issued due to an IMS /OPNDST commandfor NODE x or USER y. See VTAM For MVS/ESA, VM/ESA, VSE/ESA Programming (SC31-6496) and VTAMMessages and Codes (SC31-6418) for an explanationof this condition.


System actionThe attempt to establish a session with NODE x orUSER y has been terminated. (1) An IMS trace logrecord (X'67') containing pertinent information wasproduced with an ID of CVCT. (2) An IDC0 tracetable entry is created, if the IDC0 trace is active. (Fornonexisting dynamic terminals).


Programmer responseWhen the problem is corrected, session initiation canbe attempted again using an IMS /OPNDST command.The session can also be requested or initiated byNODE x or USER y.


Related referenceData communication service aids (Diagnosis)Related information“IMS problem determination” on page 11IMS messages and codes problemdetermination is accomplished by usingprocedures established by IBM.

DFS2062I MODENAME UNKNOWN TO VTAMNODE x (USER y).

ExplanationAn unknown mode name condition was returned ona VTAM SIMLOGON issued due to an IMS /OPNDSTcommand for NODE x or USER y. Either an incorrectmode name was specified on the IMS /OPNDSTcommand or a mode table entry was not defined toVTAM with the specified name.

System actionThe attempt to establish a session with NODE x orUSER y has been terminated. (1) An IMS trace logrecord (X'67') containing pertinent information wasproduced with an ID of CVCT. (2) An IDC0 tracetable entry is created if the IDC0 trace is active (fornonexisting dynamic terminals).

Programmer responseWhen the problem is corrected, session initiation canbe attempted again using an IMS /OPNDST command.The session can also be requested or initiated byNODE x or USER y.



DFS2063I SESSION TERMINATIONCOMPLETE NODE x (USER y).

ExplanationSession termination occurred for NODE x or USERy. Termination might have been solicited by an IMSterminal or node, depending upon security, by NODE xor USER y using VTAM/SNA commands, or by a VTAMnetwork operator command. If termination was due toan unusual condition, an error message for the specificcondition was enqueued for the IMS master terminaloperator before this message.

System actionA session with NODE x or USER y has been terminated.An IMS trace log record (X'67') containing pertinentinformation was produced with an ID of CVCT iftermination was due to an unusual condition.


Programmer responseA session for NODE x or USER y was terminated byan IMS command, upon request of NODE x or USERy, or by an unusual condition. The session can bereestablished using an IMS /OPNDST command, byNODE x, or by USER y after any outstanding problemsare corrected.



DFS2064I SESSION INITIATION COMPLETENODE x (USER y).

ExplanationSession initiation is complete for NODE x or USERy. Session initiation resulted from an IMS /OPNDST,VTAM network operator, or NODE x or USER yVTAM/SNA command.



System actionSession initiation is complete for NODE x or USER y.Any available output is sent, otherwise, IMS waits forinput.


Programmer responseContinue whatever action is appropriate for NODE x orUSER y following normal session initiation.

DFS2065I RESYNCHRONIZATION NOTPOSSIBLE NODE x (USER y).

ExplanationMessage resynchronization was required based on theprevious session termination with NODE x or USER y.However, the Get Unique call from the shared queueshas failed.

System actionThe attempt to establish a session with NODEx orUSER y has been terminated. An IMS trace log record(X'67') containing pertinent information was producedwith an ID of CVCT.


Programmer responseReinitialize NODE x or USER y to the appropriaterestart point, or override the IMS resynchronizationsystem definition option through the IMS /CHANGEcommand.

When the problem is corrected or overridden, sessioninitiation can be attempted again using an IMS /OPNDST command for NODE x or USER y. The sessioncan also be requested or initiated by NODE x or USERy.



DFS2066I BAD BIND PARM (DISP A, VALUEB) NODE x (USER y).

ExplanationIMS detected one or more invalid, unsupported, orconflicting parameters when receiving a VTAM/SNABIND command or when validating Bind parametersfrom LOGMODE table or USERDATA (after anINQUIRE). The parameters also might be in conflictwith the IMS system definition options specified forNODE x or ETO descriptor options specified for USER y.

DISP A is the displacement from the beginning of theBIND RU. VALUE B is the erroneous data. Both DISP Aand VALUE B are in hexadecimal.

System actionThe attempt to establish a session with NODE x orUSER y using a VTAM/SNA BIND command has beenrejected. An IMS trace log record (X'67'), containingpertinent information, was produced with an ID ofCVCT.


Programmer responseWhen the problem is corrected, session initiation canbe attempted again using an IMS /OPNDST commandfor NODE x or USER y. The session can also berequested or initiated by NODE x or USER y.



DFS2067I BEGIN-END BRACKET ERRORNODE x (USER y).

ExplanationIMS detected an error while processing an outputmessage. The message to be sent indicates beginbracket, but the node is in a "NOBB" (cannot beginan output bracket) shutdown state. The requestedmessage could not be sent.

The "NOBB" shutdown state is the result of OHSrequesting a symmetric shutdown or a /QUIESCENODE x (USER y) command.

System actionSession termination was forced for NODE x or USER y.An IMS trace log record (X'67'), containing pertinentinformation, was produced with an ID of CVCT.



Programmer responseThe session can be restarted to reset the shutdownstate if additional input or output is required. Sessioninitiation can be attempted using an IMS /OPNDSTcommand for NODE x or USER y. The session can alsobe requested or initiated by NODE x or USER y.



DFS2068 INPUT DATA FM HDR PARAMETERINVALID, UNSUPPORTED, OR NOTAVAILABLE

ExplanationAn input data function management (FM) headercontained an invalid, unsupported, or unavailableparameter. The output ERP FM header sent with thismessage might contain additional sense information toisolate the specific parameter.

System actionThe session with NODE x has encountered an inputerror, but the session was not terminated. Thismessage is sent to reject the input message. AnIMS trace log record (X'67'), containing pertinentinformation, was produced with an ID of CVCT.


Programmer responseContinue with input/output operations as appropriate.When the problem with the FM header is corrected,the input message can be resent.



DFS2069 END-BRACKET NOT SUPPORTEDON IMS INPUT SYNCHRONOUSMESSAGES.

ExplanationAn end-bracket was received on an input IMSresponse mode or conversational transaction, an IMScommand, or an input message while in IMS "testmode".

System actionA session with NODE x has encountered an input error.The session was terminated and message DFS2069 isleft on the queue. This message is sent to reject theinput message. An IMS trace log record (X'67'), whichcontains pertinent information, was produced.


Programmer responseTo continue the session without correcting the error,dequeue message DFS2069, and then restart thesession.

To correct the error before you restart the session,perform one or more of the following actions:

• Change the definition of the ISC TERMINAL macroto specify COMPT1=MULT to allow asynchronousprocessing and to eliminate the end-bracket fromthe input message.

• If IMS was in test mode when the error occurred,terminate test mode by using the /EXIT command.

• Change the value of the MSGTYPE= parameteron the TRANSACT macro from RESPONSE toNONRESPONSE. A value of NONRESPONSE onthe MSGTYPE= parameter changes the session toasynchronous and allows the end-bracket.



DFS2070 MESSAGE TERMINATION FORCEDFOLLOWING INPUT SNA CANCELOF MFS PAGE.

ExplanationA VTAM/SNA CANCEL command was received withoutreceiving a SUBSEQUENT VTAM/SNA LUSTATUS(message termination) following a sender detectederror during an MFS multiple page input message. IMSrequires the input message to be terminated if anysingle page is canceled.


System actionA session with NODE x has encountered an inputerror, but the session has not been terminated.This message is sent to force termination of theMFS multiple page input message. An IMS trace logrecord (X'67'), containing pertinent information, wasproduced with an ID of CVCT.


Programmer responseContinue with input/output operations as appropriate.The message can be resent to IMS after the problemthat caused the VTAM/SNA CANCEL command iscorrected.



DFS2071I EXPECTED ERP MESSAGE NOTRECEIVED NODE x (USER y).

ExplanationA VTAM/SNA exception response was received withouta subsequent ERP message explaining the reason forthe exception response.

System actionA session with NODE x or USER y has encounteredan input error, and the session is terminated. AnIMS trace log record (X'67'), containing pertinentinformation, was produced with an ID of CVCT.


Programmer responseAfter correcting the system logic in any other session,initiation can be attempted using an IMS /OPNDSTcommand for NODE x or USER y. The session can alsobe requested or initiated by NODE x or USER y.



DFS2072I LUname username (LTERM) FMH6|7 --- text ---.

ExplanationA system informational or error message, definedby the SNA FMH6 or FMH7 format, detected anasynchronous condition by the 'OTHER' system(LUname), which was received by IMS through the LU6session identified by the user name. The text followingthe FM header describes the asynchronous conditiondetected by the "OTHER" system.

System actionNormal input and output continues during the LU6session.

Operator responseSame as the Programmer response.

Programmer responseTake appropriate action as required by the messagetext.

Problem determination:1, 5, 6, 12, 14 25


DFS2073I NODE nodename SUBPOOLusername (ltermname) SOURCE(srclterm) fmh7 message_text.

ExplanationAn error message from the "OTHER" system (LUname)was received by IMS in response to output sent on anLU6 session identified by the user name. The outputqueue containing the message in error is identifiedby the user name LTERM name. The originating inputmessage source is identified by the source LTERMname. The text following the TYPE 7 FM headerdescribes the error condition.

System actionThis message is used to report error conditions forthe IMS master terminal operator or message sourceterminal operator.

The LU6 session is terminated after reporting theerror to the IMS master terminal operator. The output


message in error is returned to the queue for laterretransmission.

The output message in error is dequeued, and thesession is not terminated when reporting the errorcondition to a source terminal operator (for LU6message switch or when ERPKPSES=Y and the ERPsense code is X'0846xxxx').


Programmer responseTake appropriate action as required by the messagetext. The session can be restarted after correcting theerror condition by the "OTHER" system or by an IMS /OPNDST command.



DFS2074I SESSION ENDED; PURGE DURINGQUIESCE NODE x (USER y).

ExplanationA deadlock condition has occurred as a result ofa /CHE PURGE QUIESCE command. Quiesce logiccannot complete because of purging for the namednode or user.

System action:The node or user is closed (session terminated) as inan error situation.

Operator response:Display shut down status to be sure that session hasterminated.

DFS2075 INVALID QNAME IN QMODEL FMH.

ExplanationThe QNAME field in the QMODEL FMH (TYPE 6)received by IMS contains a name that did not matchthe DQN of the ATTACH FMH for the process, or did notmatch any valid QNAME for available output.

System actionA session has encountered an input QMODEL FMHerror, but the session was not terminated. Thismessage is sent to notify the sending half-session.


Programmer responseTry to continue with I/O operations as appropriate. TheFMH can be resent when the problem with QNAME hasbeen corrected or the FMH can be resent with QNAMEnot specified.



DFS2076 INVALID QORG PARAMETER INQMODEL FMH.

ExplanationThe QORG field in the QMODEL FMH (TYPE 6) receivedby IMS contained a QORG value that was greater thanX'02', or did not match the QORG in the QXFR FMHsent by IMS, or was invalid for the type of QMODELFMH received.

System actionA session has encountered an input QMODEL FMHerror, but the session was not terminated. Thismessage is sent to notify the sending half-session.


Programmer responseTry to continue with I/O operations as appropriate. TheFMH can be resent when the problem with QORG hasbeen corrected or the QORG can be set to X'00'.



DFS2077I DATA IS LONGER THAN BUFFERNODE x (USER y).


ExplanationAn error was encountered while attempting to movedata into a buffer. Either the segment received waslarger than the SEGSIZE specified in the IMS systemdefinition, or a VLVB block count was larger than theremaining buffer size.

System actionThe session for the node or user is terminated. Thedata that was to be blocked was lost.


Programmer responseRedefine the buffer size and regenerate the IMSsystem—or make sure the data generated for outputis not longer than the defined buffer.



DFS2078I OUTPUT REJECTED SENSExxxxxxxx LTERM yyyyyyyy. OUTPUTREJECTED SENSE xxxxxxxx LTERMyyyyyyyy Node zzzzzzzz

ExplanationA response was received indicating an invalidcharacter in the message being sent to the PTERM,or the terminal is not configured to properly accept themessage; for example, an address outside the range ofthe device buffer was contained in the data stream.The sense information received from the device iscontained in the sense field of the message. Fordevices that contain programmed symbols, output isrejected if the programmed symbols buffer is notproperly loaded.

System actionA record is written on the IMS log data set thatcontains the message. The message is put back onthe IMS message queues. Communications with thePTERM continue, unless the message was being sentin response mode. Then the terminal is disconnectedand this message is sent to the MTO.

Operator response(master terminal) This message is followed by aDFS998I message. Take the terminal out of responsemode (/STOP), then /START) and then restarted (/OPN).

(terminal) The message must be dequeued from theIMS message queues or the LTERM reassigned to aterminal capable of accepting the output. For devicesthat contain program symbols, a possible correctiveaction would be to properly load the program symbolbuffer at the device, then resend the message.


DFS2079I INVALID APPLICATION OUTPUTLTERM xxxxxxxx LINE yyy PTERMzzz. INVALID APPLICATIONOUTPUT LTERM xxxxxxxx NODEyyyyyyyy

ExplanationA non-supported command code was detected inapplication output using the MFS bypass.

System actionA log record type X'67', subrecord X'01' has beenwritten using the IMS trace facility, which provides asnap of the IMS control blocks and save areas. Theterminal involved will be made inoperable. A DFS998Imessage is sent to the MTO.

Operator response:(master terminal) The LTERM should be reassigned,or the message dequeued. Notify the systemprogrammer.

System programmer responseCorrect the application program to use valid commandcodes.


DFS2080I CONVER TRANSACTION INPUTNOT RECEIVED NODE x (USER y).

ExplanationAn incorrect session protocol was received whilein a conversational mode. This problem resulted indequeuing a conversational output reply message; themessage provided no valid reason to continue the IMS


conversation. The invalid session protocol caused bythe error indicated one of the following conditions:

1. LUSTATUS or CHASE with a changed direction inreply to a conversational output message.

2. Exceptional response sense code X'0864' to aconversational output message.

3. FMH 7 sense code X'0864' to a conversationaloutput message.

System actionThe NODE x (USER y) session was terminated. An IMSlog record (X'67'), containing pertinent information,was produced with an ID of CVCT.

Operator responseSee Programmer response.

Programmer responseWhen the problem is corrected, the session can bereestablished by NODE x, by USER y, or an IMS /OPNDST command.



DFS2081I UNABLE TO RESYNC SESSIONFP TRANCODE=nnnnnnnnNODE=xxxxxxxx.

or

TEMPORARILY UNABLE TO RESYNCH SESSIONNODE x (USER y).

or

UNABLE TO RESYNC SESSIONTRANCODE=nnnnnnnn NODE=xxxxxxxx

ExplanationIMS is temporarily unable to resynchronize during:

• An attempted session initiation. This conditionoccurs when a response mode transaction is

still processing during an attempt to initialize orresynchronize a session.

• RQR processing. A CLEAR request failed.

System actionThe attempt to initiate or resynchronize the sessionfails.

Operator responseSee Programmer response.

Programmer responseAllow the response mode transaction to complete andproduce an output reply message; then reestablishthe session from NODE x (USER y) or with an IMS /OPNDST command. The /DISPLAY command can beused to determine when the response mode reply isavailable for output.

Problem determination:1, 5, 6, 12 14


DFS2082 RESPONSE MODE TRANSACTIONTERMINATED WITHOUT REPLY.

ExplanationA response mode application terminated normallywithout having an output reply message returned tothe terminal.

An OTMA send-then-commit (CM1) or APPCsynchronous input message receives a DFS2082message when the IMS application did not reply to theIOPCB or do a message switch to another transaction.

When an OTMA commit-then-send (CM0) inputmessage has the TMAMHRSP flag specified in thestate data prefix, if the application did not reply tothe IOPCB or complete a message switch to anothertransaction, IMS issues a DFS2082 message. Thismessage is issued to the original input transaction,regardless of the transaction mode. No DFS2082message is issued to a switched-to transaction.

System actionThis IMS message is sent in lieu of the applicationoutput reply to prevent the terminal from being hung inresponse mode.


Programmer responseContinue communication with IMS or correct thetransaction logic to insert an appropriate reply.

Terminal operator response: See Programmerresponse.



DFS2083I NODE nodename SUBPOOLusername (ltermname) SOURCE(srclterm) fmh7 message_text.

ExplanationAn error message from the "OTHER" system (LUname)was received by IMS through the LU6 sessionidentified by the user name. The output queuecontaining the message in error is identified bythe user name LTERM name. The originating inputmessage source is identified by the Source LTERMname. The text following the FM header TYPE 7describes the error condition.

System actionThis message is used to report recoverable errorconditions to the IMS master terminal operator.Depending upon the FMH7 sense code, the type ofIMS message incurring the error, and the FMH7 LU6protocol used, the current output message is eitherdiscarded or retransmitted. The LU6 session is notterminated. For more information, see DFS2072I andDFS2073I.


Programmer responseTake appropriate action as required by the messagetext.

Problem determination:1, 5, 6, 12 14, 25

DFS2084 INVALID RETURN FROM SIMEXIT,EXIT DISABLED.

ExplanationThe DFSSIML0 exit routine, upon returning to IMScontrol with a return code of 8, did not provide a

transaction name in the area pointed to by registerone, or the transaction name is given is invalid.

System actionDFSSIML0 processing is bypassed by IMS, and a returncode of zero is assumed.

Operator responseContinue normal I/O activity.

DFS2085I HH:MM:SS SESSION TERMINATED,NODE=xxxxxxxx, USER=yyyyyyyy,SIGN ON FAILURE RC=zzz.

ExplanationSignon rejected due to indicated reason code. Thereason codes are documented in message DFS3649A.

System actionSignon is ignored. The session is terminated, andmessage DFS2085I is sent to the current MTO.

Operator responseAttempt the signon after diagnosing the problem.



DFS2086 /TRACE SET OFF FOR MONITORIN PROGRESS, CANNOT PROCESSCOMMAND

ExplanationThe /TRACE SET ON MONITOR command wasentered before a previous /TRACE SET OFFMONITOR command completed.


Operator responseReenter the command.


Programmer responseIf commands are entered through an automationprogram, change the program to increase the timebetween the /TRACE SET OFF MONITOR and /TRACE SET ON MONITOR commands.

Module:DFSICLN4

DFS2087 CANNOT TURN OFF TIMEOUTTRACE DURING SHUTDOWN,COMMAND IGNORED

ExplanationA /TRACE SET OFF TIMEOUT command was enteredwhile IMS was shutting down.


Operator responseDo not enter this command during shutdown.

Module:DFSICLN0

DFS2088I APPC/OTMA SMQ ENABLEMENTINACTIVE. REASON = xxx.

ExplanationThe APPC/OTMA shared message queue enablementis inactive.

The reason code is xxx. The reason codes are shown inthe following table:

Table 11. Possible reason codes for DFS2088I

Code Meaning

004 This is a non-shared queuesenvironment.

016 RRS is not active.

020 A member joined the group and cannotsupport APPC/OTMA shared messagequeue enablement.

024 Another member dropped support forAPPC/OTMA shared message queueenablement.

028 IMS disconnected from RRS.

032 AOS=N was specified in the DFSDCxxxmember.

Table 11. Possible reason codes for DFS2088I(continued)

Code Meaning

036 RRS=N has been specified as startupparameter.

040 A system with AOS= specified in theDFSDCxxx PROCLIB member joined anIMSplex that has a MINVERS level lowerthan 12.1. The APPC/OTMA sharedmessage queue enablement using XCFcommunication for standard transactionis inactive. Standard transactions aretransactions with sync level of NONE orCONFIRM.

System actionIMS forces every APPC/OTMA message to the front-end system.

Operator responseMake sure that all the requirements for APPC/OTMAshared message queue enablement are met.

DFS2089I APPC/OTMA SMQ ENABLEMENTACTIVE.

or

[RRS IS USED | XCF IS USED. | XCF AND RRS AREUSED].

ExplanationThe shared message queue support for synchronousAPPC/OTMA is active.

For the second line of the messages, the values canbe:RRS IS USED

RRS is active and is the synchronization point(sync point) manager for transactions withsynchronization levels of NONE, CONFIRM, andSYNCPT.

XCF IS USEDXCF communication is used and IMS is the syncpoint manager for transaction with synchronizationlevels of NONE and CONFIRM.

RRS AND XCF ARE USEDRRS is active and is the sync point manager onlyfor transactions with the synchronization level ofSYNCPT. XCF communication is used and IMS


is the sync point manager for transactions withsynchronization levels of NONE and CONFIRM.

System actionIMS allows every member within the IMSplex toprocess APPC/OTMA messages.


DFS2090I IMS TIMER SERVICE STIMERMSET|CANCEL FAILED, RC=xxx.

ExplanationThe IMS timer service issued a request to z/OS to setor cancel a STIMERM. z/OS returned a nonzero returncode in register 15.

System actionThe timer service shut downs. Requests for timerservices receive nonzero return codes. IMS does notterminate abnormally.

Operator response:(master terminal) Note the return code from themessage and notify your system programmer.

Problem determination1, 4 (if timer failure causes another part of IMS toabend), 6

Related referencez/OS: Return codes for the STIMERM macroRelated information“IMS problem determination” on page 11IMS messages and codes problemdetermination is accomplished by usingprocedures established by IBM.

DFS2091I IMS TIMER SERVICE SHUTDOWNCOMPLETED.

ExplanationThe IMS timer service has shut down and is no longerprocessing timer requests. This message is normallyissued during IMS shutdown. It is also issued aftermessage DFS2090I if a STIMERM SET or CANCELfailed.

System actionTimer service is no longer available in IMS.

Operator response:If you received this message during IMS shutdown, noresponse is necessary. If a STIMERM SET or CANCELfailed, see message DFS2090I.

Related information“DFS2090I” on page 613IMS TIMER SERVICE STIMERM SET|CANCELFAILED, RC=xxx.

DFS2092I INITIALIZATION FAILED FORTIMEOUT PROCESSOR RC=n.

ExplanationThe IMS VTAM I/O timeout processor (DFSASLT0) wasunable to obtain storage for the ASLTI ITASK or thetimer table required by the IMS VTAM I/O timeoutdetection facility.

The return codes and their meanings are:Code (hex)

Meaning01

Unable to get time AWE for front and switchinginitialization.

02Unable to get second AWE for front and switchinginitialization.

03Unable to get quick save area for timer tableinitialization.

04Unable to get storage for AS1T ITASK.

05Unable to create AS1T ITASK.

06Unable to get an AWE for AS1T ITASK initialization.

07Unable to get storage for timer tables.

08Unable to get time AWE for main timer.

System actionIMS initialization continues, but the VTAM I/O timeoutdetection facility is unavailable.


Programmer responseIf you need the time-out facility, increase the size ofthe IMS control region; then restart IMS.


http://www-01.ibm.com/support/knowledgecenter/SSLTBW_2.3.0/com.ibm.zos.v2r3.ieaa900/iea3a9_STIMERM_-_Execute_form.htm

DFS2093 TIMEOUT TRACE FACILITY NOTAVAILABLE, COMMAND IGNORED.

ExplanationYou entered a /TRA SET TIMEOUT command, butthe IMS VTAM I/O timeout detection facility was notavailable because the ASLTI ITASK failed during IMSinitialization. This message is also issued if you entera /DIS TIMEOVER command and the facility was notactivated.


Operator response:If you received this message after entering the /DISTIMEOVER command, issue the /TRA SET TIMEOUTcommand, if necessary. If you received this messageafter entering the /TRA SET TIMEOUT command,notify the system programmer.

Programmer responseIf the facility is not available, see message DFS2092I..

Module:DFSICLN0

Related information“DFS2092I” on page 613INITIALIZATION FAILED FOR TIMEOUTPROCESSOR RC=n.

DFS2094I NODE nodename USER usernameTIMED OUT AT hh:mmSENSE=xxxx.

or

NODE nodename TIMED OUT AT hh:mmSENSE=xxxx.

ExplanationThis node has an output response outstanding for aperiod greater than the time specified on the /TRASET TIMEOUT command used to activate the VTAMI/O timeout detection facility. The second form ofthe message is issued for ISC nodes. The messageincludes VTAM sense information, if available.

System actionThe action taken depends on what was specified onthe /TRA SET TIMEOUT command:

• If MSG was specified, the node is placed on a chainof timed-out nodes and continues to wait for aresponse.

• If AUTO was specified, IMS issues a VTAM VARYNET,INACT command followed by a VTAM VARYNET,ACT command for the node. An OPNDST isissued for the node if it was defined as non-sharedand is still operable. Messages DFS2095I andDFS2096I follow this message.

• If AUTO was specified and this is an ISC node,the node is placed on a chain of timed-out nodesand continues to wait for a response. No automaticrestart is performed.


Programmer response• If MSG was specified, issue the IMS /IDLE and /ACT

commands for the node to do a VTAM V NET,INACTand V NET,ACT. Then the node can be restarted.

• If AUTO was specified and this message was issuedfor an ISC node, see the previous response for MSG.

• If AUTO was specified and this message was issuedfor a non-ISC node, do an IMS /DISPLAY of thenode to make sure that it was restarted.

Remember: The VTAM TIMEOUT I/O facility isautomatically started during IMS shutdown. It isset for 1 minute and 'AUTO'. Effectively, the tracecommand would be: /TRACE TIMEOUT 1 AUTO. TheVTAM TIME I/O facility is also automatically startedduring IMS initialization.

Related information“DFS2095I” on page 614V NET,INACT PERFORMED FOR NODEnodename.“DFS2096I” on page 615V NET,ACT PERFORMED FOR NODE nodename.

DFS2095I V NET,INACT PERFORMED FORNODE nodename.

ExplanationIMS has issued a VTAM 'VARY NET,INACT' commandfor one of the following reasons:

• The IMS VTAM I/O timeout detection facilitydetected a VTAM node that has timed out, andis automatically deactivating it. This message ispreceded by message DFS2094I and followed bymessage DFS2096I.

• IMS TM shutdown processing has detected anoutstanding SIMLOGON for a dynamic terminal that


has not completed, and is automatically deactivatingthe node. This message is followed by messageDFS2096I.

Related information“DFS2094I” on page 614NODE nodename USER username TIMED OUTAT hh:mm SENSE=xxxx.“DFS2096I” on page 615V NET,ACT PERFORMED FOR NODE nodename.

DFS2096I V NET,ACT PERFORMED FOR NODEnodename.

ExplanationIMS has issued a VTAM 'VARY NET,ACT' command forone of the following reasons:

• The IMS VTAM I/O timeout detection facilitydetected a VTAM node that has timed-out, and isautomatically reactivating it. When IMS issues thismessage, it is preceded by messages DFS2094I andDFS2095I.

• IMS TM shutdown processing has detected anoutstanding SIMLOGON for a dynamic terminal thathas not completed, and is automatically reactivatingthe node. This message is preceded by messageDFS2095I.

Related information“DFS2094I” on page 614NODE nodename USER username TIMED OUTAT hh:mm SENSE=xxxx.“DFS2095I” on page 614V NET,INACT PERFORMED FOR NODEnodename.

DFS2097I DBDGEN REQUIRED FORDATABASE nnnnnnnn TO SETDATXEXIT INDICATOR

ExplanationWhile processing the first DL/I call for a database,with the DATXEXIT=YES flag off, the DL/I call analyzercalled the user data conversion exit. However, itwas returned to without SRCHFLAG being set toX'FF' (indicating that the user exit was required forthis database). The DL/I Call Analyzer dynamicallysets the DATXEXIT=YES flag on and continuesprocessing transactions for this database, but issuesa warning message to the user that a DBDGEN withDATXEXIT=YES must be done for this database.


Programmer responseThe database administrator must be notified that aDBDGEN is required for this database.

DFS2098 ERROR TRANSMITTING INPUT-RESEND INPUT DATA.

ExplanationThe Network Terminal Option (NTO) detected atemporary hardware error from the Network ControlProgram (NCP) during transmission of the input data.NTO sent sense code X'0827' to IMS to indicate thatthe data received was bad and must be resent.

System actionNTO processed sense code X'0827' and sent messageDFS2098 to the inputting terminal. If the message wasmulti-chained, NTO canceled the previous chains.

Operator response:Send the last input message again.

DFS2099 DATA EXCEEDS RECANY RU SIZENODE x.

ExplanationThe data length received from VTAM is larger than thesize of the RECEIVE ANY buffer.

System actionThe session is terminated. An IMS trace log record(X'6701' ID=CVCT) containing pertinent informationwas produced.

Programmer responseThe X'6701' ID=CVCT log record contains theRPL. RPLRLEN is greater than RPLBUFL. RPLBUFLis the RECEIVE ANY buffer size defined in theRECANY=(number,size) parameter of the COMMmacro.



DFS2100 END OF MESSAGE BEFORE END OFDATA-INPUT IGNORED.


ExplanationMFS reached the end of the message before reachingthe end of the data.


Operator response:Reenter the message in accordance with the messageinput description, and device input format.




DFS2101I DEACTIVATING NODE xxxxxxxx.

ExplanationIMS was unable to physically terminate the sessionin an orderly manner (CLSDST); It is necessary tologically terminate it. The possible causes of thisproblem are:

1. Console operator canceled VTAM2. VTAM abended3. CLSDST failed 25 times because of a VTAM short on

storage condition

System actionA deactivate indicator is turned on in the IMS controlblock representing the node.

Programmer responseDetermine which one of the above reasons causedthe problem, and take corrective action. To regain thenode, bring IMS down (/STOP DC-/CHExxxx) and upagain.

DFS2102 POSITIVE RESPONSE NOTREQUESTED FOR RECOVERABLEMESSAGE.

ExplanationA recoverable message was received from a 3600or 3790 terminal without a request for a positiveresponse.


Programmer responseCorrect the 3600 or 3790 program, or, if required,correct the definition of the transaction in IMS systemdefinition.

DFS2103 NODE KEYWORD PARAMETERMISSING.

ExplanationYou entered the NODE keyword without specifyingwhich nodes or all.

System actionThe IMS system continues, and the command isignored.

Operator responseReenter the command specifying the nodes to beoperated on.

Module:DFSICLN0

DFS2104 INVALID NODE NAME -NODEnodename

or

INVALID NODE NAME.

ExplanationA specified node name was not found in the system, orthere was an attempt to make a non-ISC node an IMSsecondary LU.

The first form of the message is issued by a commandprocessor if the command references an undefinednode.

The second form of the message is issued by theLOGON or SCIP exit if one of the following conditionsoccurred:

• A session initiation request references an undefinednode

• An ISC session request references a non-ISC node.

System actionThe command is ignored, or the LOGON/REQSESSrequest is denied.

Operator response:(terminal operator) If a command caused themessage, reenter the command using a valid nodename.


Module:DFSICLN0

DFS2105 NO NODE DEFINED IN SYSTEM.

ExplanationYou entered a command with the NODE keyword, butthere are no nodes defined.

System actionThe command is ignored, and processing continues.

Operator response:Correct the command and issue it again.

DFS2106 UNKNOWN TERMINAL TRIED TOCONNECT ON LINE x PTERM y.

ExplanationOn a line where ID verification is required, a 3275dial terminal, which was not authorized in the ID list,attempted to connect to IMS.

System actionThe connection is broken. The line is restarted and iswaiting for a connection attempt.

Programmer responseWhen the situation warrants it, use the Log PrintUtility (DFSERA10), with record type=X'69', to list theoffending terminal IDs and the lines they accessed.

DFS2107 NODE NOT PHYSICALLYDISCONNECTED, CANNOTPROCESS COMMAND.

ExplanationAn /EXIT command was issued for a remote terminalnode, which is not physically disconnected currently.

System action:The command is not processed.

Operator response:Try the command again when remote node isdisconnected.

DFS2108 INVALID COMMAND FROM NON-VTAM TERMINAL.

ExplanationA /RCLSDST command was entered from a terminalthat is not a VTAM node.

System action:

The command is ignored.

Operator response:Correct the command, and retry.

DFS2109 VTAM ACB NOT OPEN.

ExplanationThe command entered requires the VTAM ACB to beopen.


Operator response:Issue /START DC and retry.

DFS2110A NON-QUICK VTAM SHUTDOWNREQUESTED.

ExplanationThe VTAM operator has told VTAM to shut down. VTAMhas informed IMS of this using the TPEND exit.

ExplanationAn attempt has been made to CLOSE the VTAM ACB,and a return code of X'xx' was received.


Master terminal operator response: One of thefollowing actions can be taken:

• Enter /CLSDST command to disconnect any activenodes if there is no need to continue processing.

• Enter /CHECKPOINT command to close down IMS.• Ignore the message if processing must continue.• /STOP DC to close ACB


DFS2111I VTAM ACB CLOSED.

ExplanationThe VTAM ACB has been closed. IMS is disconnectedfrom VTAM.



DFS2112I UNABLE TO CLOSE VTAM ACB, REG15=rc, ACBERFLG=xx.

ExplanationAn attempt has been made to CLOSE the VTAM ACBusing a /STOP DC command or by VTAM driving theIMS TPEND exit routine. The attempt failed with thereturn code, rc, in register 15 and the ACB error flagsset as indicated by xx.

System actionIMS internally marks the VTAM ACB as closed andcontinues processing without its VTAM interface.

Programmer responseUse the provided information (return code and errorflags) to find out why the CLOSE failed. See VTAMV4R3 for MVS/ESA Programming (SC31-6496) for adescription of the CLOSE macro and an explanation ofthe return codes and error flags. VTAM Messages andCodes (SC31-6493) provides additional information.

DFS2113 NO DPAGE CONDITION WAS MET-INPUT IGNORED.

ExplanationNo conditional DPAGE was satisfied, andno unconditional DPAGE was specified. ForOPTIONS=DNM, all DPAGES are conditional.


Operator response:Reenter the correct input. If problem persists, haveyour programmer analyze the device input format forthat message.

DFS2114 OUTPUT ERROR LINE xxx PTERMxxx {, DO NOT REDIAL PTERM}.

ExplanationA permanent output error occurred while writingoutput messages to the terminal.

System actionThe current session terminates. The next session isinitiated ready for operator connection.

Operator response:(master terminal) Unless the error message indicatesotherwise, repeat the session. Otherwise, dial the nextrequired terminal.



DFS2115 PTERM DISC LINE xxx PTERMxxx {[SEQ NO xxxxx [SEGMID xxxxxxxx]] , DO NOT REDIALPTERM}.

ExplanationThe terminal issued a disconnect sequence duringinput or output.


Operator response:(master terminal) The current session cannot bereestablished without correcting the problem at theremote terminal.

Problem determinationDuring input, the message segment at the pointof error is identified by a sequence number, and,optionally, by an 8-character identifier. For both inputand output, the termination status is on the screen atthe remote terminal.

DFS2116 OUTPUT COMPLETE LINE xxxPTERM xxx.

ExplanationAll ready output messages have been successfullywritten to the terminal. This message is not issued ifno output messages are written during the session.

System actionThe current session is completed. The next session isinitiated ready for operator connection.

DFS2117 INPUT COMPLETE LINE xxx PTERMxxx.

ExplanationThe input message has been successfully read fromthe terminal. This message is not issued if there is noinput message to be read.


System actionThe current session continues with the output phase.If there are no output messages, the session iscomplete and the next session is initiated for operatorconnection.

DFS2118 DIAL REMOTE TERMINAL LINE xxxPTERM xxx.

ExplanationA session has been initiated after a start linecommand, or following a previous session.

System actionThe session waits until a terminal is physicallyconnected and the enabled control unit is posted.

Master terminal operator response: Dial the requiredterminal, and press DATA on the Modem when a toneis heard. If all sessions are completed, issue a STOPcommand and then press DATA on the Modem thatterminates the session and idles the line.

DFS2120 SET COMMAND ERROR LINE xxxPTERM xxx.

ExplanationThe internally created /SET command was rejected byIMS as invalid.


Operator response:(master terminal) If the problem persists, do notinitiate further sessions until the exit routine has beencorrected.

Programmer responseCorrect the user sign-on exit to create valid IMSnames.

Problem determinationRepeat the session using /TRACE (Level 3), and printthe log data set to show the set command in error.

DFS2121 USER EXIT REQUESTED DISC LINExxx PTERM xxx.

ExplanationThe user sign-on exit passed a return code requestingthat the terminal be disconnected.


Programmer responseCheck to determine that the user sign-on exit requestis valid; if not valid, take corrective action.

Master terminal operator response: Dial the requiredterminal.



DFS2122 INPUT ERROR LINE xxx PTERMxxx [SEQ NO xxxxx [SEGM IDxxxxxxxx]].

ExplanationA permanent input error occurred while reading theinput message from the terminal.

System actionThe current session terminates. The next session isinitiated, ready for operator connection.

Master terminal operator response: Repeat thesession. If the error persists, manual intervention maybe required at the remote terminal.

Problem determinationThe input message segment at the point of error isidentified by a sequence number and, optionally, by an8-character identifier. The termination status is on thescreen at the remote terminal.

DFS2123 STATUS MSG x LINE xxx PTERMxxx {[SEQ NO xxx [SEGM ID]xxxxxxxx], DO NOT REDIALPTERM}.


ExplanationAn error was detected at the remote terminal. A 1-character status message was read from the terminaland inserted into the error message.

System actionThe current session terminates. The next session isinitiated, ready for operator connection.

Operator response:(master terminal) Unless the error message indicatesotherwise or the status message indicates the problemis unrecoverable without manual intervention, repeatthe session. Otherwise, dial the required terminal.

Problem determinationDuring input, the message segment at the pointof error is identified by a sequence number and,optionally, by an 8-character identifier. For both inputand output, the termination status is on the screen atthe remote terminal. Check the 3741 status messagecharacter in the error message.

DFS2124 OUTPUT NOT COMPLETE.

ExplanationThe user issued a stop line and disconnected theterminal before all of the messages in the queue weresent.

System actionSystem continues processing.

Operator responseProceed with the normal terminal operation.

DFS2125 LOGICAL TERMINAL BECAMETRANS I: sss1/name1, D: sss2/name2

ExplanationIn the message text:sss1/name1



System actionIMS logs the message in error, using log record type"64", and removes the message from the system.

Operator responseThe error message sent to the input and themaster terminals indicates the type of message thatwas in error. Compare the two system definitionspecifications for this message and correct the one inerror.

Programmer responseCorrect the erroneous system definition.



DFS2126 TRANS BECAME LOGICALTERMINAL I: sss1/name1, D: sss2/name3










DFS2127 SPA IN MSG FOR NON-CONVTRANS I: sss1/name1, D: sss2/name2


The source SYSID and source LTERM namefor the input system. name1 is defined asnonconversational.

sss2/name2The destination SYSID and destination LTERM orTRAN code of the processing system. name2 isdefined as conversational.






DFS2128 NO SPA IN MSG FOR CONV TRANSI: sss1/name1, D: sss2/name2


The source SYSID and source LTERM namefor the input system. name1 is defined asnonconversational.

sss2/name2The destination SYSID and destination LTERM orTRAN code of the processing system. name2 isdefined as conversational.


Operator responseThe error message sent to the input and masterterminals indicates the type of message thatwas in error. Compare the two system definitionspecifications for this message and correct the one inerror.




DFS2129 MSG IS RECOV BUT DEST IS NOT I:sss1/name1, D: sss2/name2


The source SYSID and source LTERM name for theinput system. name1 is defined as recoverable.

sss2/name2The destination SYSID and destination LTERM orTRAN code of the processing system. name2 isdefined as unrecoverable.







DFS2130 MSG IS NOT RECOV BUT DEST IS I:sss1/name1, D: sss2/name2


The source SYSID and source LTERM name for theinput system. name1 is defined as recoverable.

sss2/name2The destination SYSID and destination LTERM orTRAN code of the processing system. name2 isdefined as unrecoverable.






DFS2131 DEST OF A RESPONSE IS A TRANSI: sss1/name1, D: sss2/name2




System actionIMS logs the message in error, using record type "64",and removes the message from the system.





DFS2132 INPUT LOGICAL TERMINAL NOTFOUND I: sss1/name1, D: sss2/name2

ExplanationThis system received a message that is a responseto the input. The input originated from an LTERM inthis system, but now that LTERM cannot be found,the system error, or the definition of sss1 is changed.name1 is not defined in sss1.





Operator response:


Inform the system programmer.

System programmer responseCheck the originating LTERM name (on the X'64'record) against the system definition to determine ifthe system was redefined before the response wasreceived. If the originating LTERM name was present,the CNTs might have been destroyed.



DFS2133 RESPONSE PTERM NOT INPUTPTERM I: sss1/name1, D: sss2/name2

ExplanationAn application program inserted a message to analternate response PCB specifying SAMETRM=YES.However, the logical terminal name2 does not pointto the same physical terminal as name1.





Operator responseThe error message sent to the input and themaster terminals indicates the logical terminalsinvolved. Check the logical terminal-to-physicalterminal assignments. If correct, check the applicationprogram that produced the response. Inform thesystem programmer.

System programmer responseCorrect the erroneous system definition applicationprogram, if required. Correct the logical-to-physicalterminal assignments, if required.


14Related information“IMS problem determination” on page 11IMS messages and codes problemdetermination is accomplished by usingprocedures established by IBM.

DFS2134 INVALID SYSID DETECTED LINK x

or

INVALID SYSID DETECTED I: sss1/name1,D: sss2/name2

ExplanationThe first form of this message results when thereceiving IMS detects that sss2 is invalid. sss2 is notdefined in the system generating the error.




The second form of this message results when thesending IMS detected that the source SYSID, thedestination SYSID, or both SYSIDs are invalid. Thissituation occurs during communication between aVersion 6 IMS system and a pre-Version 6 IMS system,which does not recognize a SYSID higher than 255.Possible errors are:

• A message with a source SYSID lower than 256 has adestination SYSID higher than 255.

• A message with a source SYSID higher than 255 hasa destination SYSID lower than 256.

• A message has both a source and destination SYSIDhigher than 255.

The source and destination SYSID are located in theMSNBOSID and MSNBDSID fields of the MSNB. Thelink number is x.

When any of the errors occurs, the Message Control/Error exit routine receives control. If the exit routinerequests the default action, the DFS2134 messageassociated with the error is issued.

This message can also be issued when the MessageControl/Error exit routine is customized in the sendingor receiving system to specify an incorrect exit flag, orthe exit flag is correct, but an error was encountered


while IMS was performing the requested action andthe associated default action was performed.

System actionIMS logs the message in error, using log record typeX'64', and removes the message from the system.

System programmer responseTo find and correct the error, take the followingactions, as appropriate.

• Correct the SYSID errors in the TRANSACT, LTERM,or MSNAME definitions in the system definition.

• Determine the default action from the MessageControl/Error exit routine, DFSCMUX0.

• Correct the exit flag or the destination for reroutein the Message Control/Error exit routine, ifappropriate.


Module:DFSCMS00, DFSCMEI0, DFSCMUX0


DFS2135 INVALID PARTNER ID LINK xxx.

ExplanationThe master terminal operator attempted to start amultiple systems support link and the partner IDs inthe two systems did not match.

System actionIMS stops the link.

Operator responseUse the /DISPLAY ASSIGNMENT command to displaythe logical link and the physical link assignments.Correct the logical-to-physical link assignments, if theyare in error. Otherwise, inform the system programmerthat an invalid partner ID was found. Also, verify theDD statements used for the physical links.

Programmer responseCorrect the system definition, if in error.

DFS2136 REQUIRED RESTART RESPONSENOT RECEIVED LINK xx.

ExplanationThis problem is a system error. IMS sent a restartrequest to the other partner of a multiple systemssupport connection, but did not receive a restartresponse.


Operator responseStart the IMS trace on both sides of the connection,and try again. Inform the system programmer that arequired restart response was not received.

Programmer responseVerify through the IMS trace that the appropriate linkswere connected.

Problem determination14 for both systems, 36


DFS2137 MSG IS INQ BUT DEST MAYUPDATE I: sss1/name1, D: sss2/name2


The source SYSID and source LTERM name forthe input system. name1 is defined as an inquirytransaction.

sss2/name2The destination SYSID and destination LTERM orTRAN code of the processing system. name2 isdefined as an update transaction.


Operator responseThe error message sent to the input and themaster terminals indicates the type of message thatwas in error. Compare the two system definition


specifications for this message and correct the one inerror.




DFS2138 INVALID BUFFER SIZE LINK xxx.

ExplanationThe master terminal operator attempted to start amultiple systems support link. However, because thesystem definition buffer sizes were not equal, thelink would not start. The partner assigned to the linkshown in the message has a different transmissionbuffer size than the link shown.


Programmer responseCorrect the definition of the links.

DFS2140 DESTINATION name STOPPED,REASON CODE xxx.

ExplanationIMS stopped the destination identified in the messageat the request of the partner. The reason code xxx isthe number of the IMS message read from the block,but not processed.

System actionIMS stops the indicated block. An error message, withthe number shown as the REASON CODE, is sent to themaster terminal in the partner system.

Operator responseRestart the MSNAME and notify the systemprogrammer.

System programmer responseIf the reason code xxx is 2146, the partner IMS systemdetected an INVALID DATA BLOCK error. Both sides of

the link discarded the message and the sending pathMSNAME was stopped.

For reason code 1945, the receiving IMS systemencountered a QMGR/CQS write error while puttingthe message to the message queue. The message isreturned to the message queue to be sent again, if theMSNAME path is restarted, or to be removed from thequeued by the operator.

For all DFS2140 errors, both sides logged type 6701ID=MSSx (x=1,2, or 3) log records. See messageDFS1945, DFS2146, or whatever message key equalsthe reason code, for more information.

Problem determinationContact the system programmer if the error persists.If the error was encountered by an MSC link, thefollowing CLBTEMP fields are set in the LLB block inthe 6701MSS1 record:

• CLBTEMP1 = Reason code for the DFS2140 message• CLBTEMP3 = Message key = x'0000085C' = decimal

2140• CLBTEMP4 = Module ID; that is, C'CMSI' =

DFSCMSI0 or C'CMSP' = DFSCMSP0• CLBTEMP5 = If applicable, R5 or R14 BALR offset

into the module that detected the error

Related information“DFS1945” on page 566DATA COMMUNICATIONS QMGR/CQS WRITEERROR LINK xx“DFS2146” on page 628INVALID DATA BLOCK RECEIVED LINK xx.“IMS problem determination” on page 11IMS messages and codes problemdetermination is accomplished by usingprocedures established by IBM.

DFS2141 INPUT SYSID NOT DEFINED I:sss1/name1, D: sss2/name2


The source SYSID and source LTERM name forthe input system. This information displays in themessage if sss1 and name1, are not defined in thesystem definition.





System programmer responseThe SYSID sss1 is not defined and is invalid. Correctthe SYSGEN.

Programmer response:Correct the erroneous system definition.



DFS2142 MSNAME xxxxxxxx STOPPED LINKyyy.

ExplanationA message was received on logical link yyy but theMSNAME xxxxxxxx was stopped.

System actionThe system rejects the message and informs thesending system with message DFS2140 REASONCODE 2142.

Operator responseRestart the logical link, (/START MSNAMExxxxxxxx). If the error persists, it might be necessaryto PSTOP the link (/PSTOP LINK yyy) on bothsystems, start the MSNAMES (/START MSNAMExxxxxxxx) on both systems, then restart (/RSTARTLINK yyy) both links again.

DFS2143 INCONSISTENT SPA LENGTH I:sss1/name1, D: sss2/name2

Explanationsss2 is defined with a different size SPA from sss1.





Operator responseInform the system programmer of this error and thecorrect SPA size.

System programmer responseCompare the two system definitions to determinewhich one has the incorrect SPA size. Correct thesystem definition in error.



DFS2144 CTC TRANSMISSION LENGTHERROR; LINK STOPPED. LINK nnn.

ExplanationA data transmission error was detected on link nnn.Link nnn is assigned to a channel-to-channel adapter.The X'FF' end-of-data marker was not received.

If it is an I/O error, z/OS error message IEA000Iappears on the system console. Otherwise it is aprobable logic error.

System actionLink nnn is stopped. Two X'67' trace records withrecord IDs MSS1 and MSS2 are logged.

Operator response(master terminal) Restart the link. If the problempersists, use a backup link, if available.

Problem determinationType X'67' log records were produced, containing allrelevant blocks.


Related referencez/OS: IEA000I

DFS2145 MESSAGE LOST DURING LINKRESTART LINK xxx.

ExplanationDuring synchronization of the link, IMS detected thatthis system has lost one or more messages that theother system has not yet received. The differencebetween the DEQ count on this system and thereceived count on the other system will be the count ofmessages lost.

System actionIMS logs the error information using a type X'6701' logrecord. The link is stopped by PSTOP. The restart blockis updated so that a subsequent restart link will work;however, the messages will remain lost.

Operator responseVerify that both IMS systems were correctly restarted(a cold start or restart from the wrong checkpointcould cause this). Restart the link again. The linkshould restart, but the messages will remain lost.

Programmer responseThe log data sets from both systems will have to beanalyzed to determine why the messages were lost.If the error occurred following an IMS warm start,then the restart log data set will also have to beanalyzed. (You will need to print type 40, 66, andX'6701' records.)

Problem determination36. Include as documentation the master terminaloutput and IMS log data sets from both systems. IfIMS was warm started, then include the restart logsalso.

DFS2146 INVALID DATA BLOCK RECEIVEDLINK xx.

ExplanationA data block was received on link xx that, whenchecked, was found to contain invalid or lost data, orthe conversational routines detected an error whileattempting to process a conversational type message.

System actionThe data block is rejected. If the data block was aresync, restart, or shutdown message, the link hasstopped. If the data block was a user or systemmessage, the message was discarded (dequeued)on the sending IMS. Also, the associated sendingMSNAME path was stopped on the sending IMS andmessage DFS2140 with a 2146 reason code wasissued on the sending IMS. Both sides write type 6701ID = MSSx (x = 1, 2, or 3) log records.

Operator response:(master terminal): Display the logical link in thepartner system (/DIS MSNAME) to see if the link wasstopped. If the partner was not stopped, the error wasrecovered. If it was stopped, restart the link (/STARTMSNAME).

System programmer responsePrint the type 6701 log records and analyze the error.

Problem determinationContact the system programmer if the error persists.

The following CLBTEMP fields will be set in the LLBblock in the 6701 MSS1 record:

• CLBTEMP1 = Pseudo abend code if this is aconversational error. CLBTEMP4 is CONM or CON2for conversational type errors.

• CLBTEMP2 = Return code if applicable• CLBTEMP3 = Message key = x'00000862' = decimal

2146• CLBTEMP4 = Module ID. i.e. C'CONM' = DFSCONM0,

C'CON2' = DFSCON20, C'CMSV' = DFSCMSV0, orC'CMSZ' = DFSCMSZ0.

• If applicable, R5 or R14 BALR offset into the modulethat detected the error

DFS2147I ACB CLOSE PENDING ON MASTERTERMINALS.

ExplanationA /STOP DC command was entered, but cannotcomplete until the VTAM ACB is closed. The ACBcannot be closed until all VTAM node sessions haveterminated. This message is issued to inform theoperator that the only remaining active nodes are themaster or secondary master terminals, or both.

Operator responseIssue a /CLSDST NODE or /IDLE NODE commandto close the nodes. This allows the VTAM ACB to



close and /STOP DC processing to complete. MessageDFS2111I will indicate a successful VTAM ACB close.

DFS2148I HH:MM:SS QERR=aabb REMOTEMSG xxxx FROM SYSID=yy.

ExplanationA queue error occurred while requesting function aa.The queue manager issued return code bb; SYSID yyissued command xxxx.

System actionThe message is dequeued and control is returned tothe dispatcher. A X'6701' record, which provides aSNAP of the relevant control blocks, is written to thelog.

Operator responseReenter a valid command.

System programmer responseSee Problem Determination for the correct response.

Problem determination1, 5, 6, 7, 17b


DFS2149 PARTNER IMS IN SAME SHAREDQUEUES GROUP - RESTARTABORTED LINK xxx

ExplanationThe master terminal operator attempted to start amultiple systems coupling (MSC) link and partner IMSis in the same shared queues group (SQG). MSC linktraffic between IMS systems in the same SQG is notsupported.


Operator response:The link is not restarted. Inform the systemprogrammer, if the link is not intended for backuppurposes, such as when IMS or the partner IMSis brought up in non shared queues mode or in adifferent shared queues group.

Programmer responseRemove the shared queues specification from one ofthe IMS systems (for example, the SHAREDQ= startupparameter) or place one of the IMS systems in adifferent SQG.

DFS2150A hh:mm:ss CTC IO ERR PC=xxREASON=xx OP=xx LINK nnnnSTOPPED.

Explanation:For an explanation and actions, see DFS2150I.

Related informationDFS2150IMTM I/O ERR PC=xxcccccc LINK=xxxx.

DFS2150I MTM I/O ERR PC=xxccccccLINK=xxxx.

or

CTC ERR RC=xx LINK=xxxx.

or

hh:mm:ss CTC IO ERR PC=xx REASON=xx OP=xxLINK nnnn RSTARTED.

or

MTM ERR RC=xx LINK=xxxx.

ExplanationAn I/O error has occurred.

In the message text:RC

The return codePC

The post codeREASON

The associated channel-to-channel reason codeLINK

The link numberOP

The attempted CTC operationhh:mm:ss

The time


If message DFS2150I...LINK nnnn RSTARTED isissued, the link was stopped and then restarted byIMS. If message DFS2150A...LINK nnnn STOPPED isissued, IMS attempted to restart the link, but wasunable to do so.

The following channel-to-channel operations apply:

Operation

Code (hex)Meaning

04WRITE: write a buffer.

08ACK: acknowledge input.

0CWRACK: write a buffer and acknowledge input.

10STARTUP: establish connection.

14SHACK: acknowledge input and shut down theconnection.

18SHUTDOWN: shut down the connection.

1CREAD: read input.

The following channel-to-channel return codes andmeanings are possible:

Return

Code (hex)Meaning

04Logic error: IOSB is not busy on ACK or WRACK.

08Logic error: ACK or WRACK is issued, and nomessage is received to acknowledge.

10Logic error: on STARTUP, there is an invalid value inDECWAREA, DECWLNG, DECAREA or DECLNGTH.

14Probable I/O error: on attention interrupt.

18Paging error: at STARTUP.

1CLogic error: in module DFSCMC50 at STARTUP.

20Logic error: STARTUP issued, but link is alreadyconnected.

24Logic error: SHUTDOWN issued, but link is alreadyshut down.

28An I/O error or an abnormal condition wasdetected during SHUTDOWN, and SHUTDOWN wassuccessfully executed.

The following table shows the possible post codes,associated reason codes, and their meanings:

Table 12. Possible post codes, associated reasoncodes, and meanings for DFS2150I

Postreasoncode

Code(hex)

Meaning

7F any I/O complete without error

7F 04 Startup: Link available for write

7F 08 Startup: message received

7F OC Message received

7F 10 Shutdown received

7F 1C Acknowledgement received

7F 20 Acknowledgement with datareceived

41 any I/O error detected

41 01 Error in attempting todetermine command inadapter

41 02 Invalid command in adapter

41 03 Error in reading message

The following real storage-to-real storage connectionreturn codes and meanings apply:

Return

Code (hex)Meaning

12Window is not open or not found.

16Window is allocated to two other systems.

20Invalid input.

24IEAMSCHD failed: partner has terminated.

28Buffer lock failure.

32Buffer lengths are not equal.

36Caller is not authorized.


40Main storage-to-main storage access routine isdefined for a different OS.

44Window queue header block is bad or is notinitialized.

48GET or GETMAIN failure.

52PGFIX or PGFREE error.

The following real storage-to-real storage post codesand meanings apply:Post code

Meaning41RD

Read error: partner already reading.41CLS

Read or write error: partner closed in mid-operation. The most probable cause is an abendof the partner.

41BUFRead or write error: I/O buffer lock failure.

Operator responseFor CTC message DFS2150A, assign a backup link, ifavailable. For MTM or CTC DFS2150I, when the link isnot restarted, attempt to restart the link.

Problem determinationCTC is an I/O or probable logic error. If it is an I/Oerror, z/OS error message IEA000I appears on thesystem console.

MTM is a probable real storage-to-real storage accessmethod logic error.

A type X'67' log record was produced, containing allrelevant blocks.

Related referencez/OS: IEA000IRelated informationDFS2150Ahh:mm:ss CTC IO ERR PC=xx REASON=xxOP=xx LINK nnnn STOPPED.





DFS2151 CURRENT MSPLINK NOT STOPPEDAND IDLE.

ExplanationA link that is currently assigned to MSPLINK is notstopped and idle.


Operator response(terminal operator) Issue a /PSTOP command to stopthe link currently assigned to the specified MSPLINK.

DFS2152 MSPLINK KEYWORD PARAMETERINVALID.

ExplanationThe MSPLINK parameter entered is not defined in thesystem.


Operator response:Reenter the command with a valid MSPLINK name.

DFS2153 MSNAME KEYWORD PARAMETERINVALID [RSN=xxyy].

ExplanationThe MSNAME that was entered is not defined in thesystem.

xxIMS MODULE THAT DETECTED THE ERROR01

MSVERIFY COMMAND (DFSCMLA0)yy

REASON FOR THE ERROR01

The specified MSNAME is not defined in thesystem.

02The SYSID that was defined as a remote SYSIDfor the specified MSNAME was overridden to alocal SYSID in a shared queues (SQ) group.


Operator response• If yy=01, correct the MSNAME and reenter the

command.• If yy=02, inform the system programmer.

System programmer response:Determine if the remote SYSID for the specifiedMSNAME is also defined as a local SYSID in anotherIMS system in an SQ group.

Module:DFSCMLA0, DFCML70, DFSICLJ0

DFS2154 SYSID KEYWORD PARAMETERINVALID [RSN=xxyy].

ExplanationThe SYSID that was entered is not defined as a remoteSYSID.

xxIMS MODULE THAT DETECTED THE ERROR01

MSVERIFY COMMAND (DFSCMLA0)yy

REASON FOR THE ERROR01

The specified SYSID is invalid.02

The specified SYSID that was defined as aremote SYSID was overridden to a local SYSIDin a shared queues (SQ) group.


Operator response• If yy=01, reenter the command with a valid SYSID.• If yy=02, inform the system programmer.

System programmer response:Determine if the specified SYSID is also defined as alocal SYSID in another IMS system in an SQ group.


Module:DFSCMLA0, DFCML70

DFS2155 INVALID LINK NUMBER.

ExplanationThe link number specified was not valid for the definedmultiple systems IMS system.

System actionThe command is not completed.

Operator response:Reenter the command with the correct link number.

Module:DFSICLN0

DFS2156 MSNAME/SYSID IN USE, UNABLETO ASSIGN.

ExplanationThe system that this link-to-link message wasaddressed to has not acknowledged receipt of themessage.


Operator responseUse the /MSASSIGN link to the MSPLINK, aftersynchronizing with the partner master terminaloperator.

DFS2157 ORIGINATING LOGICAL LINK NOTSTOPPED AND IDLE.

ExplanationThe MSNAME or the SYSID is assigned to a link that isnot stopped and idle.


Operator responseIssue a /PSTOP command to the link that MSNAME/SYSID is presently assigned to.

DFS2158 COMMAND INVALID FORTERMINAL TYPE.

ExplanationThe command that was entered is not valid for theterminal specified or implied by the command.

System actionThe command is ignored. IMS continues processing.

DFS2159I hh:mm:ss UNDEF REMOTE MSGxxxx FROM SYSID=yy.

ExplanationThe remote command xxxx from SYSID yy is invalid.

System actionThe message is dequeued and control is returned tothe dispatcher. A X'6701' record, which provides aSNAP of the relevant control blocks, is written to thelog.

Operator responseReenter a valid command.

System programmer responseSee Problem Determination for the correct response.



DFS2160I LINK nnn STARTED BY PARTNERXX NODE nodename.

ExplanationLink nnn was started at the request of the remotepartner system.





Problem determinationNot applicable.

DFS2161I LINK xxx STOPPED BY PARTNER.

ExplanationLink xxx was stopped at the request of the othersystem attached to it. The other system might beshutting down, or the master terminal operator mighthave entered a /PSTOP LINK command.

System actionOutput messages are queued on this link, but none aresent.

Operator response(master terminal) Issue a /RSTART LINK commandto put the link back into operation. The masterterminal operator in the other system must do thesame before message transfers will begin.

DFS2162 TERMINAL IN RESPONSE MODE-ENTER PA1 or PA2 THEN AWAITREPLY.

ExplanationThis terminal is in response mode either because it isdefined to operate in forced-terminal response mode,or because a terminal response type of transactionwas entered.

System actionIMS discards the entered data. The applicationprogram will respond to the last accepted input, unlessthe terminal is page protected.

Operator responsePage protection can be overridden by pressing PA1 orPA2. If no response is received, contact the masterterminal operator to have the operator issue the /STOP, /START commands for node or in the case ofa dynamic terminal, the /STOP, /START commands forthe user.

Programmer responseScreen protection has been specified as either aterminal option or an MFS option. Determine if this isnecessary for this transaction.

DFS2163 MSG IS UPDATE, DEST IS INQONLY I: sss1/name1, D: sss2/name2


The source SYSID and source LTERM name for theinput system. name1 is defined as inquiry-only.

sss2/name2The destination SYSID and destination LTERM orTRAN code of the processing system. name2 isdefined as an update.

System actionIMS logs the message in error, using log record type'64', and removes the message from the system.

Operator response(master terminal) The error message sent to the inputand master terminals indicates the type of messagethat was in error. Compare the two system definitionspecifications for this message and correct the one inerror. Inform the system programmer.


DFS2164 MSG IS SNGL SEG, DEST IS MULTID: sss1/name1, I: sss2/name2


The source SYSID and source LTERM name forthe input system. name1 is defined as a singlesegment.

sss2/name2The destination SYSID and destination LTERM orTRAN code of the processing system. name2 isdefined as a multisegment.



Operator response:The error message sent to the input and masterterminals indicates the type of message thatwas in error. Compare the two system definitionspecifications for this message and correct the one inerror. Inform the system programmer.

System programmer responseCorrect the erroneous system definition.



DFS2165 ROUTING LOOP DETECTED I: sss1/name1, D: sss2/name2

ExplanationThere is a routing loop in the IMS multiple systemscoupling configuration. A routing loop can be createdby either an incorrect system definition (the offlineverification utility points that out), or by improper useof the /MSASSIGN command. A routing loop existswhen a SYSID is not defined as local anywhere on thelogical link path. For example: in IMS System A, SYSID3 is defined as remote, and is assigned to a logical linkconnecting System A to System B. In IMS System B,SYSID 3 is again defined as remote, but is assigned toa logical link connecting System B to System A.





Operator response(terminal operator) Notify the master terminaloperator.

(master terminal operator) This is probably a usererror. Use the /DISPLAY ASSIGNMENT command to

display the current SYSID assignments involved. Ifthe looping message is a response destined for aninputting terminal that is in response, conversation, orexclusive mode, this error can result in the terminalremaining locked until restarted with a /STARTcommand or until the conversation is terminated withan /EXIT command.



DFS2166 EXTENDED SECURITY VIOLATIONFOR MSC LINK [I: sss/name, D:sss/name,U:name]

ExplanationWhile an MSC link was receiving an input messagedestined to a transaction, a security check todetermine if the input message was allowed for thetransaction destination failed. The failure occurred dueto an authorization check made by RACF or by the userexit DFSCTRN0.

If the optional part of the message is printed:

• name following D: is the transaction destination ofthe message. name following I: is the input systemLTERM name.

• sss following I: is the SYSID of the input system. sssfollowing D: is the SYSID of the processing system.

• name following U: is the USERID that failed theauthorization check. The CTL region ID will not bedisplayed if it is used for the authorization check.

The /DISPLAY ASSIGNMENT SYSID command canbe used to determine the MSNAME involved.

System actionIMS logs the message in error, using record type 64,and removes the message from the system.

System programmer responseCorrect the erroneous security error. Check theMSCSEC= parameter in the DFSDCxxx PROCLIBmember of the remote system. Also, check that thelink receive logic of the user exit DFSMSCE0 of theremote system determines the type of security checkthat was made. Using the information from the X'64F1'and X'64F2' log records and the DFS2166 errormessage determine why the security authorizationcheck failed.


An X'6701' log record with ID=CMEA is logged.CLBTEMP5 contains the return code (RC) fromDFSCAUT0, and CLBTEMP3 contains the RC from therequest that failed or zeros. These return codes areshown in the following table:

Table 13. CLBTEMP3 return codes

RC Label Description

4 CAUTRMSC RACF failure occurred; it was unable toobtain the ACEE for MSNAME.CLBTEMP3 = RACF RC

8 RACFERR RACROUTE failure.CLBTEMP3 = RACF RC.

C CAUT044 TRANAUTH was specified, but RACFwas not defined.

10 TESTE010 An error was returned from DFSCRTN0.CLBTEMP3 = DFSCTRN0 RC.

14 GETRACWE The GETRACW routine was unable toobtain storage.CLBTEMP3 = BCB RC.

18 CAUTRINT The CAUTRINT routine was unable toobtain storage.CLBTEMP3 = BCB RC.


Module:DFSCMS00


DFS2167 FAST PATH MSG REJECTED BYMSC I: sss1/name1, D: sss2/name2



sss2/name2The destination SYSID and destination LTERMor TRAN code of the processing system. name2is defined for exclusive Fast Path transactions.Multiple Systems Coupling does not supportexclusive Fast Path transactions.


Operator responseThe error message sent to the input and masterterminals indicates the type of message that was inerror. Compare the 2 system definition specificationsfor this message and correct the one in error. Informthe system programmer.

System programmer responseCorrect the erroneous system definition.



DFS2168I CONNECTION ESTABLISHED ONLINK xxx [CONT].

ExplanationAn /RSTART LINK or an automatic link restartcommand establishes connection between two IMSsystems with Multiple Systems Coupling over link xxxand messages queued for transmission over link xxxwill be sent. CONT indicates link (BSC only) is runningin continuous mode. (See /RST link command.) Themessages are received at the master terminal.


DFS2169I DISCONNECTION COMPLETED ONLINK xxx.

ExplanationTwo IMS systems with Multiple Systems Couplingare disconnected by a /PSTOP LINK command. Thismessage is generated when the linkage between thetwo systems has been disconnected. The message isreceived at the master terminal.

System actionOutput messages are queued on this link, but none aresent.

Master terminal operator response: Issue a /RSTARTLINK command to put the link back into operation.The master terminal operator in the other system mustdo the same before message transfer will begin.


DFS2170I MESSAGE QUEUED FOR xxxxxxxx

ExplanationA message was enqueued for transaction xxxxxxxx,and this transaction is currently stopped from beingscheduled. The message is queued and available forprocessing. If the transaction is already scheduled andwaiting for input (parameter = WFI on TRANSACTIONmacro), this message will be processed.

System actionThis message is sent only once and only for the firstmessage to be queued on a stopped transaction.

Master terminal operator response: Start thetransaction with the /START command.

DFS2171I NO RESPONSE. CONVERSATIONENDED.

ExplanationThe synchronization point processor found that aconversational program did not insert a messageto the IOPCB, ALT CONVERSATION PGM PCB, orALTRESP PCB.

System actionAfter terminating the conversation, the system issueserror message DFS2171I to the input terminal.

Operator response:The terminal in conversation can reenter theconversation with different input data.

Programmer responseCheck the input message against the applicationprogram logic. Determine why a message was notinserted after the SPA was inserted or after asuccessful GU call.



DFS2172 VERSION-ID IN FMH DOESN'TMATCH VERSION-ID IN DIF --INPUT IGNORED.

ExplanationThe version identification supplied in the FMH doesnot match the version identification generated in theDIF control block.


Programmer responseCorrect the remote program to supply the correctversion identification, supply a version identification ofzeros, or do not send the version identification.

DFS2173 UNEXPECTED EOD RECEIVED-TEST MODE RESET.

ExplanationWhile in MFS test mode, an unexpected end of data(EOD) indication was received.

System actionMFS test mode has been reset for this terminal.

Operator response:If problem persists, notify the IMS systemprogrammer.

Problem determinationLog record type X'67', subrecord X'01', ID 'FERR',which contains diagnostic information, is produced if /TRACE is set on for the physical terminal at the time offailure.

DFS2174 TRAN CODE FROM LINK EXITIS NON-LOCAL I: sss1/name1, D:sss2/name2

ExplanationThe transaction code updated by the Link Exit is notdefined as a local transaction in sss2.







System programmer responseCorrect the error either in the MSC Link Exit Routine, orin the System Definition.



DFS2175 MESSAGE CANCELED BY ROUTINGEXIT RSN=xxyy ROUTINE I:sss1/name1, D:sss2/name2.

ExplanationEither the Terminal Routing entry point or the LinkReceive Routing entry point in the DFSMSCE0 exitcanceled (rejected) this message.

If sss/name appears in the message, the messagewas canceled in a remote system by the Link ReceiveRouting entry point.


xxThe IMS module that detected the error:01

DC Communication Manager (DFSICIO0 -Terminal Routing)

02MSC Analyzer (DFSCMS00 - Link ReceiveRouting)

yyThe reason for error is 01. If xx=01, the messagewas canceled by the DFSMSCE0 Terminal Routingentry point. If xx=02, the message was canceledby the DFSMSCE0 Link Receive Routing entrypoint.



System actionIf xx=02, IMS logs the canceled message (using logrecord type '64') and removes the message from thesystem. If xx=01, IMS removes the message from thesystem.

System programmer responseDetermine which entry point in the DFSMSCE0 exitcanceled the message. See the user exit to determinewhy the exit canceled the message. If the LinkReceive Routing entry point canceled the message,use the MSC link trace to gather more information(/TRACE SET ON LINK x MODULE ALL LEVEL3). If the Terminal Routing entry point canceled themessage, use the exit trace to gather more information(/TRACE SET ON EXIT DFSMSCE0 ALL or TRBT|TRVT|TR62| TROT|LRTR|LRLT|LRDI|LRIN). Youcan also use UPDATE MSLINK NAME(linkname)START(TRACE). For more information about thesetraces and diagnosing routing errors, see the IMSdiagnostic information.

Note: The type-2 command UPDATE MSLINKNAME(linkname) START(TRACE) uses the same leveland module settings that were used the last time the /TRACE SET (ON) LINK command was issued. Ifa /TRACE SET (ON) LINK command has not beenissued since the last cold start, this command defaultsto MODULE=ALL and LEVEL=4.

ModuleDFSCMS00, DFSICIO0, DFSMSCE0

DFS2176 RESPONSE LTERM NOT LOCALLTERM I: sss1/name1, D: sss2/name2

ExplanationAn application program in response mode changed thedestination of the response and inserted a message toa modifiable alternate response PCB. But name2 is nota local CNT in the inputting system.






Operator responseThe error message sent to the input and the masterterminals indicates the logical terminals involved.Verify the need for the input terminal in responsemode. Inform the system programmer.

System programmer responseCorrect the erroneous application program. When theinput terminal is in response mode, the messageresponse must go to the input system.



DFS2177I LOAD ERROR FOR USER EXITDFSDBUX1

ExplanationThe user specified DATXEXIT=YES at DBDGEN time,but failed to linkedit DFSDBUX1 into an APF authorizedlibrary. At execution time, while processing a DBDrequiring the exit, DFSDLA00 determined that theexit could not be loaded and issued the loaderror message. This message can also result if theuser specified DATXEXIT=YES and the user exit setSRCHFLAG to X'FF' because the user exit determinedthe DBD did not require the exit.

System actionAfter issuing the message, the database requiring theexit is stopped and the transaction receives a U0885pseudoabend.

Programmer responseIf the user exit (DFSDBUX1) is required for theapplication, ensure that DFSDBUX1 is bound intoan APF authorized library, and restart IMS beforerestarting the application.

If the second option above applies, either remove theDATXEXIT=YES from the DBDGEN or change the userexit so that is does not set SRCHFLAG to X'FF'.



DFS2178I VTAM HAS BEEN CANCELED.

ExplanationThe system console operator canceled VTAM or VTAMabended.

System actionIMS will deactivate all active nodes and performcleanup as required.

Master terminal operator response: After VTAM hasbeen restarted, enter /START DC to establish aconnection to VTAM and start your nodes.

DFS2179I QUICK VTAM SHUTDOWNREQUESTED.

ExplanationThis informational message alerts the master terminaloperator of the fact that the system console operatoris terminating VTAM. It is issued for a HALT NET,QUICK command, or a VARY NET, INACT command.

System actionIMS will terminate all active sessions and idle thenodes. At this point the IMS VTAM ACB is closed.

DFS2180I AUTOMATED OPERATOR USEREXIT ERROR-CODE=x.

ExplanationIMS detected an error condition indicated by x in anautomated operator (AO) exit routine.

The following codes are issued for AO exit routineDFSAOUE0:Code (dec)

Meaning1

The user exit destination name was invalid. Thereis no TRAN/LTERM defined by that name. Nofurther exit routine processing takes place withthis message/command.


2The queue manager handling a request on behalfof the exit routine returned a nonzero return code.No further exit routine processing takes place forthis message/command.

3The return code in register 15 is invalid. Nofurther exit routine processing takes place for thismessage/command.

4There were multiple requests for storage. Nofurther exit routine processing takes place for thismessage/command.

5An exit routine request for storage could not besatisfied. Either the request is unreasonably largeor the CIOP buffer pool needs to be increased.

6The AO detected an error. The standard AO logrecord is produced, and exit routine processing forthe message in progress is terminated.

7The exit routine requested that the AO insert asegment to the alternate destination, but register 1is either zero or points to the UEHB. No further exitroutine processing takes place for this message/command.

The following codes are issued for AOIE type exitroutines (including DFSAOE00):

8The CBTS latch was held for an unexpected blocktype during command processing. Any segmentsthat were inserted or enqueued by the AOIexit to an alternate destination are canceled. Nofurther exit routine processing takes place for thecommand.

9A request for HIOP storage failed. Any segmentsthat were inserted or enqueued by the AOIexit to an alternate destination are canceled. Nofurther exit routine processing takes place for thecommand.

10The exit routine returned with an invalid reply codefor a command or a command response segment.

Command processing continues normally but theexit routine is not called for subsequent commandresponse segments for this command.

11

The exit routine requested that IMS pass themessage an AOIE type exit routine, but such aroutine does not exist.

Message processing continues normally but theexit routine is not called for subsequent messagesegments for this message.

12The exit routine returned with an invalid reply codefor a message segment.

Message processing continues normally but theexit routine is not called for subsequent messagesegments for this message.

13The exit routine returned with a return codeoutside the range of valid return codes. The returncode is changed to 0 (the exit processes themessage or command), and processing for themessage or command proceeds.

14The exit routine returned with a reply code otherthan 0 for a command entered either internally byIMS or by the DL/I ICMD call.

The processing for the command proceedsnormally. The exit routine is not called forcommand response messages for commandsentered either internally by IMS or by the DL/IICMD call.

20The AO User Exit Interface detected an error. AOtrace log record X'6701' is generated, and exitroutine processing for the command in progressproceeds.

21The AO User Exit Interface detected an error. AOtrace log record X'6701' is generated, and exitroutine processing for the message in progressproceeds.

22The AO User Exit Interface detected an error. AOtrace log record X'6701' is generated, and exitroutine processing terminates for the message orcommand in progress.

System actionFor errors in DFSAOUE0, IMS writes a trace recordlabeled AOI to the system log. For errors in the AOIEtype exit routines, IMS writes a trace record labeledAOIT to the system log for those codes that specifythat an X'6701' log record is generated.



ModuleDFSAOUE0, AOIE type exit routines (includingDFSAOE00)

DFS2182 USER NOT AUTHORIZED TORELEASE CONVERSATION.

ExplanationAn attempt was made to release (/REL) aconversational transaction that is not authorized to theuserid previously entered on the /SIGN command.


Operator response:Reenter the /REL command, specifying aconversational ID authorized to your user ID.

DFS2183 INVALID EXIT FLAG SPECIFIEDFOR GIVEN ENTRY FLAG BYMESSAGE CONTROL/ERROR EXIT.

ExplanationThe exit flag set by the Message Control/Error exitroutine is invalid. IMS cannot perform the requestedactions.

System actionIMS does the following:

• Ignores the exit flag and does not perform therequested actions.

• Discards the message that was partially processedwhen it called the exit routine.

• Logs the message in an X'64' trace record if a receiveerror caused it to call the exit routine.

• Logs the contents of the interface block before andafter it called the exit routine in an X'6701' tracerecord.

System programmer responseUse the information in the X'64' and X'6701' records tocorrect the error. Resend the message if wanted.


Related referenceValid flags and default actions (Exit Routines)Related information“IMS problem determination” on page 11


DFS2184 MESSAGE DISCARDED BYMESSAGE CONTROL/ERROR EXIT.

ExplanationThe exit flag set by the Message Control/Error exitroutine indicates a request for IMS to discard themessage.

System actionIMS does the following:

• Discards the message that was partially processedbefore it called the exit routine.

• Logs the message in an X'64' trace record if a receiveerror caused it to call the exit routine.

• Logs the contents of the interface block before andafter it called the exit routine in an X'6701' tracerecord.

Operator responseNotify the system programmer that message DFS2184was issued.

System programmer responseEnsure that the discarded message does not affect thedatabase.



DFS2185I DEQUEUE COMMANDSUPPRESSED BY MESSAGECONTROL/ERROR EXIT.

ExplanationThe exit flag set by the Message Control/Error exitroutine indicates a request for IMS to suppress theDEQUEUE command.

System actionThe DEQUEUE command is ignored.

DFS2186 INSUFFICIENT STORAGE TORESTART LINK link x.


http://www.ibm.com/support/knowledgecenter/SSEPH2_15.1.0/com.ibm.ims15.doc.err/ims_dfscmuc0_validflags.htm#ims_dfscmuc0_validflags

ExplanationThe link was not restarted because of insufficientstorage in the HIOP to allocate the Message Control/Error exit interface block associated with the link.

System actionThe link is not restarted.


• Try again later. This problem can be a temporarycondition.

• Increase the upper limit of the HIOP with the HIOPparameter in the JCL that is used to start IMS.

DFS2187 REROUTE FAILED,DESTINATION=xxxxxx, REASONCODE=n

ExplanationIMS detected one of the following error conditionsduring message reroute:Code (dec)

Meaning0

Invalid destination for reroute.1

Reroute destination was not found.2

Cannot reroute a conversational message to a non-conversational destination.

3Cannot reroute a non-conversational message to aconversational destination.

4Error while building a rerouted message.

5Cannot reroute a message switch to aconversational destination.

6Error during copy of LU 6.2 prefix while building arerouted message.

System actionThe message is not rerouted. The associated defaultaction is performed.

If a /DEQ command was entered and the reroutefails before IMS dequeues the message, the messageremains on the queue.

If the reroute fails after IMS dequeues the message,the default action is performed, and the message isdequeued.

If a STOPPED destination is provided by the MessageControl/Error exit routine to reroute a message, thedestination name is either LTERM followed by theLTERM name, or TRAN followed by the transactionname.

System programmer responseCheck the Message Control/Error exit (DFSCMUX0) forthe default action. Provide a good destination in theuser exit, if appropriate.

Local/remote terminal operator response: If thedestination was stopped, enter the /START commandto start the destination. The next message can then bererouted successfully.

DFS2191 UNABLE TO PROCESS SHAREDEMH DUE TO GLOBAL STORAGESHORTAGE

ExplanationWhile using the shared expedited message handler(EMH) to process an input message, Fast Path wasunable to obtain global storage from ECSA for thefollowing internal control blocks:

UOW table


Programmer responseIncrease ECSA storage on the next IMS restart.

Module:DBFHIEL0

DFS2192 UNABLE TO PROCESS SHAREDEMH DUE TO PRIVATE STORAGESHORTAGE

ExplanationWhile using the shared expedited message handler(EMH) to process an input message, Fast Path wasunable to obtain extended private storage for thefollowing internal control blocks:

FPWP



Programmer responseIncrease the region size on the next IMS restart.

Module:DBFHIEL0

DFS2193I SHARED EMH PROCESSINGFAILED: RC=nn PROCESSINGIMSID=xxxxxxxx

ExplanationAn IFP region was unable to process an inputmessage retrieved from the shared expedited messagehandler queue (EMHQ). This message is sent to theinputting terminal and the input message is deletedfrom the shared EMHQ. IMSID is the IMS ID of theprocessing IMS subsystem. In an XRF system, IMSIDis the RSENAME of the processing IMS subsystem. Apossible reason is that the transaction is not defined inthe processing IMS subsystem. The return code is oneof the following:01

The transaction code is not defined.02

The transaction code name is invalid.03

The input message is too large.04

The transaction is stopped at the processing IMS.05

The input terminal name is invalid. The processingIMS subsystem cannot locate the input LTERM.

System actionThe input message is discarded.

Module:DBFHGU10

DFS2194 SHARED EMHQ NOT AVAILABLE

ExplanationThe shared expedited messages handler (EMH)queues were temporarily unavailable to performshared EMH processing.

System actionThe input message is rejected.

Module:DBFHIEL0

DFS2195I INPUT MESSAGE DISCARDED DUETO REBUILD

ExplanationAn input message was put on the expedited messagehandler queue (EMHQ) to process. Before an IMS canprocess the message, a recovery rebuild was done torebuild the EMHQ. The input message was lost as aresult of the recovery rebuild process.


Module:DBFSEQS0

DFS2195W INPUT MESSAGE DISCARDEDDUE TO REBUILD WHILE IMSIS DOWN. TERMINAL xxxxxxxxMIGHT REMAIN LOCKED

ExplanationAn input message on a client queue was discardedbecause a coupling facility was rebuild and anemergency restart of the IMS was run. The inputtingterminal xxxxxxxx remains locked until next restart ofthe front-end IMS.


Module:DBFHCAS0

DFS2196 UNABLE TO PROCESS SHAREDEMH DUE TO RRS ERROR

ExplanationWhile using the shared expedited message handler(EMH) to process an input message, Fast Pathencountered an RRS error.



Module:DBFHIEL0

DFS2198E THE PROCSEQD OPERAND ISINVALID FOR A DEDB DATABASEWITH NO SECONDARY INDEXDEFINED FOR PCB pcbname INPSB psbname


ExplanationThe PCB statement for a DEDB database specifies thePROCSEQD operand, but the DEDB database does nothave a secondary index defined in its DBD.

System actionThe Application Control Blocks (ACB) Maintenanceutility terminates processing for the PSB. The PSB isdeleted from the ACB library. The utility continues torun and the return code is set to 8.

Programmer response1. Remove the PROCSEQD operand on the PCB

statement.2. Run the PSB Generation utility (PSBGEN) again.3. Run the ACB Maintenance utility with a BUILD

statement for the PSB.

ModuleDFSDLB00

DFS2199E THE PROCSEQD OPERAND ISINVALID FOR A FULL FUNCTIONDATABASE FOR PCB pcbname INPSB psbname

ExplanationThe PCB statement for a full-function databasespecifies the PROCSEQD operand. However, thePROCSEQD operand is valid only for a DEDB databasewith a secondary index defined.

System actionThe Application Control Blocks (ACB) Maintenanceutility terminates processing for the PSB. The PSB is

deleted from the ACB library. The utility continues torun and the return code is set to 8.

Programmer response1. Change the PROCSEQD operand to the PROCSEQ

operand for a full-function secondary index.2. Run the PSBGEN utility again3. Run the ACB Maintenance utility with a BUILD

statement for the PSB.

ModuleDFSDLB00

DFS2200I LOAD FAILED FOR DFSMNTB0.

ExplanationThe system was not able to load the monitor moduleDFSMNTB0.

System actionThe IMS batch job continues without monitor logging.

Programmer responseEnsure that DFSMNTB0 is available for loading into thesystem.

Problem determinationCheck JOBLIB and STEPLIB for DFSMNTB0.




DFS2201I PGFIX ERROR FOR IMSMON.

or

OPEN ERROR FOR IMSMON.

ExplanationIMS was not able to open the monitor log because ofan error in OPEN or PGFIX.

System actionIMS continues without monitor logging.

DFS2202I PERMANENT I/O ERROR ONIMSMON.

ExplanationThe logger attempted to write to the monitor log(ddname IMSMON). However, either a permanent I/Oerror occurred, or all space allocated to the monitordata set was used.

System actionIMS monitor logging is stopped.

Programmer responseThe IMS monitor must be restarted under eithercondition. You might have to restart IMS.

If a permanent I/O error occurred, scratch andreallocate the IMSMON data set. If the monitor dataset was allocated using the IMSMON DD statement inthe IMS startup job, restart IMS. IMS does not need tobe restarted if the data set is dynamically allocated.

If the data set ran out of space, DFSUTR20 can beused to report the current contents, and the monitorcan be restarted. IMS does not need to be restarted,regardless of the allocation method of the data set.

DFS2203I LOG INITIALIZATION FAILED-TRANSLATE ERROR.

ExplanationUsing a virtual control region, an error occurredtranslating virtual addresses to real addresses for thelog work area.




DFS2204I LOG INITIALIZATION FAILED-PAGE FIX ERROR.

ExplanationUsing a virtual control region, an error occurred whilepage fixing the log work area.





DFS2205I LOG INITIALIZATION FAILED -zzzz.

ExplanationEither the log or the DC monitor failed to initialize. zzzzhelps to identify the cause of the problem and can beone of these strings:


INSUFFICIENT VIRTUAL STORAGEA GETMAIN for the log or the DC WebSphere®

Business Monitor storage failed.MODULE xxxxxxxx, NOT LOADED

In an online IMS, an attempt to load a DCWebSphere Business Monitor module failed. Ina batch environment, an attempt to load a logmodule failed. In either case,xxxxxxxx is the nameof the module that could not be loaded.

DEVTYPE/RDJFCB/TRKCALC ERRORA z/OS service, DEVTYPE, RDJFCB, or TRKCALC,returned a nonzero return code. The abendmemory dump must be examined to determinewhich service failed and the reason for the error.

INVALID DEVICEFor an online IMS, an OLDS or WADS is allocated toa non-DASD device or all WADS are not allocatedto the same DASD device type. For a batchenvironment, the log is allocated to a tape deviceand a standard label is not specified.

NOT ENOUGH WADS OR OLDSNo WADS or less than three OLDS are specified foran online IMS.

LOG DATA SET REQUIREDThis is a batch job which declared that thedatabase should be updated. Either no log DDstatement is present or the log DD statementspecified a DD DUMMY data set and DBRC isactive.

LOG BLKSIZE INVALID (MIN yyyyy)For an online IMS, either the log data set block sizeis not in multiples of 2048 or the block size is notlarge enough to handle the maximum log recordcreated by IMS. yyyyy is the minimum log blocksize required.

BLKSIZE PARAMETER IS INVALIDThe BLKSIZE= parameter on the OLDSDEFstatement in the DFSDFxxx PROCLIB member wasinvalid. BLKSIZE must specify a value that is amultiple of 2048, and that is between 6144 and30,720.

LOGGER SECTION NOT FOUND IN DFSDFxxxThe required LOGGER section is not found in thespecified DFSDFxxx PROCLIB member. xxx is thespecified suffix.

REQUIRED DFSDFxxx MEMBER WAS NOTSPECIFIED

The DFSDFxxx member is required for IMS startup.At a minimum, it must contain the LOGGERsection.

System actionFor INSUFFICIENT VIRTUAL STORAGE, if this situationoccurs while initializing the log, IMS abends with

abend 0070. If this situation occurs during the DCmonitor initialization, IMS sends message DFS2206Iand continues processing.

For MODULE xxxxxxxx, NOT LOADED, if this situationoccurs while initializing the DC WebSphere BusinessMonitor, IMS sends message DFS2206I and continuesprocessing. If this situation occurs during loginitialization in a batch environment, IMS terminatesabnormally with abend 0071.

For DEVTYPE/RDJFCB/TRKCACL ERROR, if a DEVTYPEor TRKCALC error occurs, IMS terminates abnormallywith abend 0072. If an RDJFCB error occurs, IMSterminates with abend 0074.

For INVALID DEVICE, IMS abends with abend 0075.

For NOT ENOUGH WADS OR OLDS, LOG DATASET REQUIRED, LOG BLKSIZE INVALID (MIN yyyyy),and BLKSIZE PARAMETER INVALID, IMS terminatesabnormally with abend 0073.

Programmer responseFor zzzz value, DEVTYPE/RDJFCB/TRKCALC ERROR,the memory dump must be analyzed to determinethe cause of the failure. For all the other zzzz values,ensure the following:

• All required log DD statements are present.• Log DD statements specify device and data set

attributes that meet IMS requirements.• Sufficient virtual storage and all required load

modules are available.


Related information“DFS2206I” on page 648DC MONITOR LOGGING NOT AVAILABLE.IMS abend 0070IMS abend 0073IMS abend 0075“IMS problem determination” on page 11IMS messages and codes problemdetermination is accomplished by usingprocedures established by IBM.

DFS2206I DC MONITOR LOGGING NOTAVAILABLE.

ExplanationAn error occurred during initialization of the monitorlog.


http://www.ibm.com/support/knowledgecenter/SSEPH2_15.1.0/com.ibm.ims15.doc.msgs/msgs/0070.htm#imsabedn0070



System actionIMS continues processing without monitor logging.

Programmer responseIf you want DC monitor logging, make sure that theIMSMON data set is allocated correctly.

DFS2207I IMS LOG(S) BLOCKSIZE=xxxxx,BUFNO=yyyy

ExplanationThe DCB parameters for the log data sets areBLKSIZE=xxxxx, LRECL=xxxxx-4, and BUFNO=yyyy.All OLDS are assumed to be preallocated with thedisplayed DCB attributes.


DFS2208I xxxx LOGGING IN EFFECT ON IMSzzzz.

ExplanationThe value of xxxx is either SINGLE or DUAL. The valueof zzzz is either LOG or WRITE AHEAD DATA SET.From the execution parameters and DD statementsprovided, IMS establishes single or dual logging forthe log data set (OLDS or batch SLDS) or for the writeahead data set (WADS).

System action:IMS continues processing with single or dual logging.

Operator response:If the logging mode is different from what you want,correct the execution parameters or DD statements,or both, for the log data sets and restart IMS. If theDD= statements were specified incorrectly, messageDFS0413I might be issued.

Related information“DFS0413I” on page 142INCORRECT LOG DATASET xxxxxxxx -DISCARDED RC=zz

DFS2209I MONITOR INITIALIZATIONERROR-REASON x.

ExplanationA problem occurred while initializing a monitor. x canbe one of the following reason codes:Code (dec)

Meaning

00Invalid initialization request code.

01Monitor is already active.

04Logical log open failure.

05Physical log open failure.

System actionFor all reason codes, IMS continues processing.

Programmer responseIf the reason code is 02 or 04, you cannot restart themonitor for the duration of the current IMS session.If the reason code is 05, you might be able to restartthe monitor, depending on the type of open failure thatoccurred.

For reason code 02, increase the size of the IMScontrol region.

DFS2210I MONITOR TERMINATION ERROR-REASON x {RC=yyyy}

ExplanationA monitor encountered an error. The following reasoncodes and meanings apply:Code

Meaning02

Logical logger FEOV failure. RC=yyyy is displayedfor reason code 02 only and contains the IMSlogical logger return code.

System actionFor all reason codes, IMS continues processing, andthe monitor is stopped.

Programmer responseYou can attempt to restart the Monitor.

DFS2212I DC MONITOR STARTED.

ExplanationDC monitoring is activated.

System actionThe system continues processing as before.


DFS2213I DC MONITOR STOPPED - (TIMEINTERVAL ELAPSED)

ExplanationDC monitoring is terminated. If the command used tostart the monitor included the INTERVAL parameter,then Time Interval Elapsed is included inthe message to indicate that the system internallyterminated monitoring when the time elapsed.


DFS2214I ERROR-NO VALID RECORDS ONINPUT DATA SET.

ExplanationIncompatible input data set or no records on the dataset.


Programmer responseResubmit the job with the appropriate data set.

DFS2215A MONITOR INACTIVE, MODIFY TOSTART MONITOR.

ExplanationThe DB Monitor is inactive and is prompting for acommand to start the monitor.

System actionIMS continues, with the Monitor inactive.

Operator response:When the monitor is to be started, enter MODIFYjobname, START.

DFS2216A MONITOR ACTIVE, MODIFY TOSTOP MONITOR.

ExplanationThe DB Monitor is active and is prompting for acommand to stop the Monitor.

System actionIMS continues, with the Monitor active.

Operator response:

When the Monitor is to be stopped, enter MODIFYjobname,STOP, or MODIFY jobname,STOPEOV.

DFS2217I UNABLE TO OPEN MONLOG,MONITOR UNAVAILABLE.

ExplanationOpen failed for a separate IMS DB Monitor data set.

System actionThe Monitor is made unavailable for the duration of thebatch execution. IMS continues processing.

Programmer responseCorrect the IMSMON DD statement.

DFS2218I MONITOR MODIFYSPECIFICATION INCORRECT.

ExplanationThe previously entered MODIFY command was notSTOP, START or STOPEOV.

System actionThe operator is prompted to reenter a MODIFYcommand.

Operator response:Enter, using the MODIFY command with the keywordSTOP, START, or STOPEOV as appropriate.

DFS2219I I/O ERROR ON MONITOR LOG,MONITOR TERMINATED.

ExplanationA permanent I/O error occurred writing the Monitor logdata set.

System actionThe Monitor tries to ignore the abend. If successful,the Monitor is inactive for the remainder of thebatch execution, and IMS continues processing. Ifthe Monitor cannot ignore the abend, IMS terminatesabnormally.





DFS2220I INVALID FILE PARAMETER. NOREPORTS PRINTED.

ExplanationThe FILE parameter on a control statement forDFSUTR30, DB Monitor Report Print Program, was nota 1- or 2-digit decimal number.


Programmer responseResubmit the job with the corrected control statement.

DFS2221I MONITOR UNABLE TO WRITEOUTPUT.

ExplanationThe DB monitor is unable to write output records;the //IMSMON DD statement is missing or is a DUMMYstatement, and the IMS log is inactive because theprocessing option is a GET function.

System actionBatch execution continues; the monitor is unavailable.

Programmer responseInclude an //IMSMON DD statement in the IMSprocedure, and rerun the job.

Problem determinationIf monitor output is desired for a batch execution inwhich updates do not occur, a non-DUMMY //IMSMONDD statement must be included in the IMS procedure.

DFS2225E IMS ABEND SEARCH ANDNOTIFICATION FAILED

ExplanationIMS abend search and notification failed to completesuccessfully. This message is associated with anadditional message that describes the nature of thefailure.

System actionProcessing is terminated with a return code of 8.

System programmer responseCorrect the problem indicated. If you invoked IMSabend search and notification using ISPF, regeneratethe job and resubmit it.

Module:DFSIASNP

DFS2226E FAILED xxxxxxxx ALLOCATION

ExplanationA GETMAIN for storage for the indicated internalcomponent failed during IMS abend search andnotification processing. xxxxxxxx indicates one of thefollowing internal components:

URLS_ARRAYPARM_ARRAYRCPTTO_ARRAYPROCPARM_ARRAYDFS2226E


System programmer responseIf you invoked IMS abend search and notification usingISPF, regenerate and resubmit the job. If the problempersists, contact IBM Software Support for assistance.

Module:DFSIASNP

DFS2227E OPEN FAILURE ON xxxxxxxx DATASET

ExplanationThe data set associated with the DD statementindicated by xxxxxxxx could not be opened during IMSAbend Search and Notification processing. xxxxxxxx isone of the following DD statements:

SYSPRINTSYSUT1SYSUT2CONTROLINPARMSURLS



System programmer responseDetermine the nature of the problem with the DDstatement or the associated data set, and correctthe problem. If you invoked IMS Abend Search andNotification using ISPF, regenerate and resubmit thejob.

ModuleDFSIASNP

DFS2228E INVALID NUMERICENCOUNTERED

ExplanationA non-numeric character was found by IMS AbendSearch and Notification in a control statement;numeric characters were expected


System programmer responseCorrect the control statement in error. If you invokedIMS Abend Search and Notification using ISPF,regenerate and resubmit the job.

ModuleDFSIASNP

DFS2229E MAXIMUM NUMBER OFSTATEMENTS FOR URL ADDRESSEXCEEDED

ExplanationIn the URLS data set, a URL address in the data setidentified by the URLS DD statement had more thanfour lines associated with it.


System programmer responseReformat the URL address to fit on four or less lines. Ifyou invoked IMS Abend Search and Notification usingISPF, regenerate and resubmit the job.

ModuleDFSIASNP

DFS2231 HEXADECIMAL PARAMETERLONGER THAN 16 CHARACTERS.

ExplanationAn XKEY parameter was entered that contained morethan 16 characters.


Operator responseUse a valid parameter, and reenter the data.

DFS2232 INVALID HEXADECIMALPARAMETER.

ExplanationThe only valid characters for an XKEY parameter areA-F and 0-9.

System actionThe command is ignored. IMS continues processing.

Operator response:Use a valid parameter, and reenter the data.

DFS2233 ASSIGNMENT REDUNDANT.

ExplanationThe resource that you specified has already beenassigned to you.


DFS2234I MSVERIFY COMMAND INPROGRESS FOR LOCAL SYSID(S)P1, P2, P3...Pn. yyddd/hhmmss.

ExplanationP1, P2, P3...Pn are the local SYSID numbers defined inthe entering system. yyddd/hhmmss is the time stamp.This time stamp will be the same for all messagesrelated to this command.

System actionVerify the command that is in process.

DFS2235I SYSID nnnnnn IS DEFINED ASLOCAL IN BOTH SYSTEMS. yyddd/hhmmss


ExplanationThe resource was defined as local in both systems.yyddd/hhmmss is the time stamp.

System actionThe system will continue to process the command.When the last resource is verified, the command willterminate.

DFS2236I MSVERIFY COMMAND INPROGRESS FOR REMOTE SYSID(S)P1, P2, P3...Pn. yyddd/hhmmss

ExplanationP1, P2, P3...Pn are SYSID numbers defined as local inthe remote system. yyddd/hhmmss is the time stamp.This time stamp will be the same for messages relatedto this command.

System actionThe system will continue to process the command.

DFS2237I MSVERIFY COMPLETED FORSYSID Pn. yyddd/hhmmss

ExplanationThis message will be preceded by a warning messagefor any conflict in the specified SYSID Pn. Thismessage should be received for each SYSID specifiedin DFS2234I. If this message is not received for atleast one SYSID specified in DFS2234I, there mightbe a problem with the routing of the message. yyddd/hhmmss is the time stamp.

System actionThe system will continue to process the command.

DFS2238I DFSUTR30 INPUT FILE NOT FROMIMS n.n BATCH SYSTEM

or

DFSUTR20 INPUT FILE NOT FROM IM n.n ONLINESYSTEM.

ExplanationThe file used as input to an IMS monitor report utility,either DFSUTR20 for an online report or DFSUTR30for a batch monitor report, was not acceptable. Themessage was issued for one of two reasons:

• The release level of the IMS system producing theinput does not match the release level of the reportutility being used.

• A batch input file was supplied to DFSUTR20, or anonline input file was supplied to DFSUTR30.

System actionThe report utility is terminated. No reports areproduced.

Programmer responseEnsure that the release levels of the input file andreport utility match and that the appropriate reportutility is used for the input file.

DFS2239 TOO MANY ADS PARAMETERS

ExplanationToo many ADS parameters were entered for thiscommand; only one ADS parameter is allowed.


Operator responseReenter the command with only one ADS parameter.

DFS2240 TOO MANY MSNAMEPARAMETERS.

ExplanationToo many MSNAME parameters were entered for thiscommand; only one can be entered.


Operator responseReenter the command with only one MSNAMEparameter.

DFS2241I nnnnnn IS DEFINED AS REMOTETRANSACTION IN BOTH SYSTEMS.

ExplanationThe resource is defined as a remote transaction inboth systems.


System actionThe system continues to process the command. Ifthis resource is the last being verified, the commandterminates.

DFS2224I TRANSACTION ON A BACK-ENDSYSTEM ABENDED

ExplanationAn APPC or OTMA originated transaction executing ata back-end IMS system in a shared queue environmentterminated abnormally. The transaction has beenbacked out.

Programmer responseAnalyze the reason for the abend on the back-endsystem. This message gets generated for the followingreasons:

• The application program terminated abnormally duea program error.

• The back-end IMS system terminated abnormally.• RRS at the front-end or back-end IMS system

became inactive.• The operating system at the back-end terminated

abnormally.

ModuleDFSAOSW0, DFSYLUS0

DFS2242I nnnnnn IS NOT DEFINED ASLTERM IN BOTH SYSTEMS.

ExplanationThe resource is defined as a remote LTERM in onesystem and is not defined as an LTERM in the partnersystem.


DFS2243I nnnnnn IS NOT DEFINED ASTRANSACTION IN BOTH SYSTEMS.

ExplanationThe resource is defined as a remote transaction inone system and is not defined as a transaction in thepartner system.


DFS2244 TOO MANY SYSID PARAMETERS.

ExplanationYou specified too many SYSID parameters for thiscommand; only one can be specified.


Operator responseReenter the command with one SYSID parameter.

DFS2245I MULTISEGMENT TRANSACTIONFLAG FOR nnnnnn NOTCONSISTENT.

ExplanationFor resource nnnnnn, the multisegment transactionflag is on in one system, either remote or local, andoff in the other system.


DFS2246I NONINQUIRY ONLY FLAG FORnnnnnn NOT CONSISTENT.

ExplanationFor resource nnnnnn, the noninquiry only flag is on inone system, either local or remote, and off in the othersystem.


DFS2247I CONVERSATIONAL FLAG FORnnnnnn NOT CONSISTENT.

ExplanationFor resource nnnnnn, the conversational SMB flag is onin one system, either local or remote, and off in theother system.



DFS2248I NONRECOVERABLE FLAG FORnnnnnn NOT CONSISTENT.

ExplanationFor resource nnnnnn, the unrecoverable transactionflag is on in one system, either local or remote, and offin the other system.


DFS2249I FIXED LENGTH SPA FLAG FORnnnnnn IS NOT CONSISTENT.

ExplanationFor resource nnnnnn, the fixed-length SPA flag is onin one system (local or remote) and off in the othersystem.


DFS2250I THE SPA LENGTH FOR nnnnnn ISNOT THE SAME.

ExplanationFor resource nnnnnn, the lengths of the SPA in thelocal and the remote systems are not the same.

System actionThe system continues to process the command. Ifthis is the last resource being verified, the commandterminates.




DFS2251W INPUT FILE INCOMPLETE,REPORT MAY BE INVALID.

ExplanationThe IMSMON file used as input to DFSUTR20 isincomplete. The possible causes are:

• The IMS Monitor data set (IMSMON DD statement)used to capture the online monitor records might notbe large enough. Increase the data set size.

• The IMS Monitor was not terminated in a normalmanner (for example, IMS abended) and logging toIMSMON was halted.

• The IMSMON file resides on multiple volumes, andnot all VOLSERS have been concatenated in the inputjob stream.

• An IMSMON file produced by the DB Monitor (BatchIMS) is being used as input to DFSUTR20. Thecorrect utility is DFSUTR30.

System actionDFSUTR20 attempts to produce all requested reports,but the values might be invalid. The absence of thebuffer pool statistics reports is a clear indicator thatthe IMSMON file is incomplete.

DFS2252 LINK NOT STOPPED AND IDLE.

ExplanationAn /MSASSIGN command cannot be executed; one ofthe links involved is not stopped and idle.

System actionThe command is not executed.

Operator responseIssue a /PSTOP command to the busy link.

DFS2253 MSVERIFY COMMAND ABORTED.

ExplanationThe /MSVERIFY command is unable to executebecause the MSNAME or the SYSID specified has noreturn link in the partner system. The message isprinted in the partner system.


Operator responseReenter the command, specifying a different MSNAMEor remote SYSID.

DFS2254 COMPONENT COMMAND NOTVALID FOR THIS TERMINAL.

ExplanationA /COMPT or /RCOMPT command was entered for aterminal that does not support components.


DFS2255 INVALID COMPONENT NUMBER.

ExplanationA component parameter other than a 1, 2, 3, or 4 wasentered.


Operator responseReenter the command.

DFS2256 COMPONENT NOT ATTACHED.

ExplanationThe component number specified in a /COMPT or /RCOMPT command is not defined for this system.



DFS2257 COMPONENT SPECIFIED NOTDEFINED.


ExplanationThe component specified in a /COMPT or /RCOMPTcommand is not defined in this system.


Operator responseReenter the command correctly.

DFS2258 NO LINKS DEFINED IN SYSTEM.

ExplanationA LINK keyword was entered as part of a command,but there were no links defined for the system.



DFS2259 TOO MANY LINK PARAMETERS.

ExplanationMore than one link parameter was specified in an /MSASSIGN command.


Operator responseReenter the command with only one link parameter.

DFS2260 TOO MANY MSPLINKPARAMETERS.

ExplanationMore than one MSPLINK parameter was specified inan /MSASSIGN command.


Operator responseReenter the command with only one MSPLINKparameter.

DFS2261 NODE IS NOT IN SESSION

ExplanationThe command is not executed, because the VTAMnode is not currently in a session.


Operator response:(master terminal) Initiate a session, using the IMShost commands or host system commands, andreissue the command, if desired.

DFS2262 TOO MANY DATABASEPARAMETERS

ExplanationToo many database parameters were entered for thiscommand; only one can be entered.


Operator responseReenter the command with only one databaseparameter.

ModuleDFSORC10

DFS2263I UNABLE TO OPEN MNPS ACBREG15=xx ACBERFLG=yyy

ExplanationAn error code was returned when OPEN wasattempted for the MNPS ACB in an MNPS environment.xx is the OPEN return code in register 15 and yyy isthe ACB error field returned by VTAM. Both xx and yyyvalues are displayed in decimal number.

System actionIMS continues without the MNPS ACB being opened.If this message is issued during XRF takeover, sessionpersistence is lost, and VTAM class 1 sessions cannotbe restored.

System programmer responseFor a detailed explanation of the error codes, seez/OS Communications Server: SNA Messages, z/OS


Communications Server: SNA Programming, and z/OSCommunications Server IP and SNA Codes.

ModuleDFSHCI00, DFSIC460

Related referencez/OS: OPEN-Open one or more ACBs

DFS2264I IMS NOT ACCEPTING LOGONS -NODE xxxxxxxx

ExplanationWhen a LOGON was requested for the specified node,IMS was in one of the following states:

• /STOP DC was in progress.• /START DC was not complete.• IMS was out of receive-any buffers.


Operator responseFind out which of the above states caused the requestto be ignored; then take appropriate action.

DFS2265I SETLOGON FAILED RTNCD=xxFDB2=yy

ExplanationA VTAM return code was received for a SETLOGONmacro during XRF system takeover in an MNPSenvironment. Both xx and yy values are displayed inhexadecimal number.

System actionIMS continues processing; START DC failed. Sessionpersistence is lost, and VTAM class 1 sessions cannotbe restored.

Operator responseDetermine why the SETLOGON failed. Issue /STARTDC to complete the START DC process.

Programmer responseFor a detailed explanation of the error codes, seez/OS Communications Server: SNA Messages, z/OSCommunications Server: SNA Programming, and z/OSCommunications Server IP and SNA Codes.

Module:DFSHCI00

Related referencez/OS: SETLOGON-Modify an applicationprogram's capability to establish sessionsz/OS: RPL return code (RTNCD,FDB2)combinations

DFS2266I MULTINODE PERSISTENTSESSION TAKEOVER STARTED

ExplanationDuring XRF takeover processing, IMS has started theMultinode Persistent Session takeover process.




ModuleDFSVTPO0

DFS2267I ALL MULTINODE PERSISTENTSESSION TAKEOVERS HAVE BEENINITIATED

ExplanationDuring XRF takeover processing when using MultinodePersistent Sessions, all persistent session takeovershave been scheduled. The session takeover functionwill execute asynchronously with the normal IMSprocessing.





http://www-01.ibm.com/support/knowledgecenter/SSLTBW_2.4.0/com.ibm.zos.v2r4.istprg0/opnacb.htm?lang=en

http://www-01.ibm.com/support/knowledgecenter/SSLTBW_2.4.0/com.ibm.zos.v2r4.istprg0/setlog.htm?lang=en




ModuleDFSVTPO0

DFS2268I MULTINODE PERSISTENTSESSION TAKEOVER FAILED,INQUIRE|RESTORE RTNCD=xxFDB2=yy

ExplanationDuring XRF takeover processing when using MultinodePersistent Sessions (MNPS), VTAM INQUIRE orOPNDST RESTORE commands received an error returncode from VTAM. Both xx and yy values are displayedin hexadecimal.

System actionIMS continues normal processing, but terminatesMNPS session recovery. Session persistence is lost,and VTAM class 1 sessions cannot be restored.

Operator responseVTAM sessions can be restarted, as appropriate, usingnormal session initiation procedures. Depending onthe type of error, the MNPS ACB might hate to beclosed and reopened using /STOP DC and /STARTDC.

System programmer responseFor a detailed explanation of the error codes, seez/OS Communications Server: SNA Messages, z/OSCommunications Server: SNA Programming, and z/OSCommunications Server IP and SNA Codes.

Module:DFSVTPO0

Related referencez/OS: SETLOGON-Modify an applicationprogram's capability to establish sessionsz/OS: OPNDST-Establish sessions (applicationas PLU) or recover sessionsz/OS: RPL return code (RTNCD,FDB2)combinations

DFS2269I IMS CANNOT LOCATE NODEnodename DURING MULTINODEPERSISTENT SESSION TAKEOVER

ExplanationDuring the persistent session takeover process, VTAMnotifies IMS that all sessions are pending recovery. Torestore each individual session, IMS needs to locateits corresponding control block. If the control blockcannot be located, DFS2269I is issued to the MTO.

System actionIMS continues normal execution, but persistence isnot restored for the terminal.

Operator responseThe terminal can be restarted, as appropriate, usingnormal session initiation procedures.


ModuleDFSVTPO0

DFS2270 FORCE KEYWORD IS INVALID,LINK NOT VTAM

or

FORCE KEYWORD IS INVALID, LINK NOT VTAM ORTCP/IP

ExplanationA /PSTOP LINK FORCE command was entered, butthe link type is not VTAM or TCP/IP.


Master terminal operator response: If the link is aCTC link, you can issue the /PSTOP LINK PURGEcommand as an alternative to the /PSTOP LINKOPTION(FORCE) command. Otherwise, check thatyou are specifying the correct link number and thenreissue the command with only one link.

DFS2271I FAST PATH EXCLUSIVETRANSACTION FLAG FOR nnnnnnNOT CONSISTENT.

ExplanationFor resource nnnnnn, the Fast Path exclusivetransaction flag is on in one system (local or remote)and off in the other system.

System actionThe system continues to process the command. Ifthis is the last resource being verified, the commandterminates.




http://www-01.ibm.com/support/knowledgecenter/SSLTBW_2.4.0/com.ibm.zos.v2r4.istprg0/opndst.htm?lang=en

http://www-01.ibm.com/support/knowledgecenter/SSLTBW_2.4.0/com.ibm.zos.v2r4.istprg0/opndst.htm?lang=en



DFS2272 PURGE OR FORCE KEYWORDINVALID, ONLY ONE LINKALLOWED.

ExplanationThe PURGE keyword in the /PSTOP LINK commandcan be specified for only one physical channel-to-channel (CTC) link at a time.

Multiple links were specified (LINK ALL or LINKP1...Pn) on the /PSTOP LINK command. The FORCEkeyword can be specified for only one physical link at atime for:

VTAMTCP/IP

System actionThe command is not run.

Operator responseDo one of the following:

• Reenter the command with only one CTC, TCP/IP, orVTAM link specified.

• Omit the PURGE or FORCE keyword.

DFS2273 PURGE KEYWORD REJECTED,CURRENT STATUS OF LINK ISNORMAL.

ExplanationA /PSTOP LINK P1 PURGE command was rejectedbecause PURGE is not necessary. The link has not beenstopped or it is in the process of becoming stoppedand idle.


Master terminal operator response: Reenter the /PSTOP command without the PURGE keyword.

DFS2274 MSC FEATURE NOT DEFINED

ExplanationThe MSNAME, MSPLINK, or SYSID keyword wasentered in a command, but the MSC feature is notincluded in the current system.


Terminal operator response: Reenter the commandcorrectly.

DFS2275I SORT FAILED-INCREASE REGIONSIZE

ExplanationInsufficient storage is available for the SORT program.

System actionDFSISTS0 terminates with a return code from theGETMAIN macro.

Operator response:(system console) Increase the region size.

Problem determinationSee the SORT program error message.

DFS2276I INVALID PARM FIELD-DEFAULTSUSED.

ExplanationThe utility program (DFSISTS0) encountered an invalidparameter.

System actionDFSISTS0 continues.

Operator response:(system console) Check the JCL, If the defaults arenot wanted, cancel the job, correct the parameters,and rerun the job.

Related referenceStatistical Analysis utility (DFSISTS0) (SystemUtilities)

DFS2277I LOGIN IS NULL DATA SET.PROGRAM TERMINATES

ExplanationThe DFSISTS0 utility has determined that the LOGINDD data set either is a null data set or does not containany message records of type X'01' or X'03'.

System actionThe utility terminates with a return code of 0, and noreport is produced.

DFS2278I UTILITY ENDS WITH: SYSTEM LOGAT hh.mm.ss.th, yyddd


http://www.ibm.com/support/knowledgecenter/SSEPH2_15.1.0/com.ibm.ims15.doc.sur/ims_dfsists0.htm#ims_dfsists0

http://www.ibm.com/support/knowledgecenter/SSEPH2_15.1.0/com.ibm.ims15.doc.sur/ims_dfsists0.htm#ims_dfsists0

or

START RECOVERY WITH: SYSTEM LOG AThh.mm.ss.th, yyddd

ExplanationBoth forms of this message are issued by the OnlineImage Copy utility.

The first form of this message displays the timestamp of the last IMS checkpoint taken preceding thisdatabase data set image copy. This time stamp valuecan be used as the "purge date and time" specificationto the Change Accumulation utility.

The second form of this message displays the timestamp of the last IMS checkpoint taken before thecompletion of this database data set image copy.

The two time stamp values can be used to select thesystem log data sets (SLDSs) that contain log recordscreated during this execution of the Online ImageCopy utility.


DFS2279I MONITOR TERMINATING-BADTIME VALUE

ExplanationThe DC Monitor was attempting to obtain a timevalue using the STORE CLOCK instruction (STCK) andencountered either of the following two unacceptablestates as determined by the return code. Return code,2: Clock in the error state, or 3: Clock stopped or notoperational.

System actionIMS continues processing, but the DC Monitoring isterminated for the trace.

Programmer responseEnsure that the time-of-day clock is in either of thetwo valid states acceptable to the DC Monitor. The twoacceptable states to the Monitor result in conditioncode 0 or 1, which is clock set and running and clocknot set and running, respectively.

DFS2280I MONITOR TERMINATING-MONITOR LOG ERROR

ExplanationAn error was detected when the logger attempted towrite to the DC Monitor log.

System actionIMS continues processing, but DC Monitor tracing isterminated.

Programmer responseEither an I/O error occurred on the DC Monitor log dataset or all space allocated for the log data set has beenused. If all allocated space has been used, the MonitorReport Print utility (DFSUTR20) can be run and the DCMonitor can be restarted.



DFS2281I UPPER THRESHOLD REACHEDFOR xxxxx.

ExplanationThe device relative record number (DRRN) in-use-count for either LGMSG or SHMSG, as indicated byxxxxx, was greater than the high threshold count.

System actionAll messages being retrieved from Shared Queues willwait until the low threshold value is obtained.

Programmer responseDetermine why the DRRN count was so high. Problemareas could include the number of messages queuedto SMTO or BMP with a high transaction count.

Module:DFSQC020

DFS2282I LOWER THRESHOLD REACHEDFOR xxxxx.

ExplanationThe device relative record number (DRRN) in-use-count for either LGMSG or SHMSG (as indicated byxxxxx) was lower than the low threshold count afterthe high threshold count was reached.


System actionAll messages that were waiting from the upperthreshold being reached continue processing.

Module:DFSQC020

DFS2283I RESYNC UNIT OF RECOVERYIS IN DOUBT STATUS=COLD/UNRTKN=ccccccccxxxxxxxxxxxxxxxxPTKN=yyyyyyyy

ExplanationFor the displayed recovery token, IMS receivedrequest type UNknown or COLDstart during theresynchronization process. The resynchronizationprocess resolves in-doubt units of recovery betweenconnecting subsystems after a restart. An in-doubtunit of recovery is a unit of work (UOW) that hascompleted the prepare phase of sync point, but hasnot yet received the final action (ABORT or COMMIT).When this message is issued, either the transaction-management subsystem has no knowledge of the in-doubt unit of recovery or the coordinator controllerwas cold started. The first part (cccccccc) of therecovery token is the CCTL ID. Field yyyyyyyy is thepseudo token.


Programmer responseUse the DISPLAY command to display the units ofrecovery not resolved during the resynchronizationprocess. Determine the final action required for eachunresolved unit of recovery (ABORT or COMMIT).Use the IMS command/CHANGE CCTL nnnn PRTKNxxxx ABORT to resolve the UOR in most cases.Alternatively, you can issue the COMMIT command.

DFS2285I DURING MULTINODE PERSISTENTPROCESS, nodename WASREVERTED TO CLASS 2

ExplanationDuring the persistent session takeover process, VTAMloses session persistence CV29 for class 1 terminal,and IMS reverts session persistence to class 2.




ModuleDFSVTPO0

DFS2286I CLASS 1 TERMINALS BEINGREVERTED TO CLASS 2DURING MULTINODE PERSISTENTPROCESS

ExplanationDuring the persistent session takeover process, VTAMloses session persistence for class 1 terminal and IMSreverts session persistence to class 2. A diagnostic logrecord X'6710' is written to record the nodename ofclass 1 terminal being reverted to class 2.

System actionIMS continue normal execution, but persistence is notrestored for class 1 terminal.

Operator responseThe terminal can be restarted, as appropriate, usingnormal session initiation procedure.

System programmer responseLocate X'6710' log record and identify terminal thatneeded to be restarted.

ModuleDFSVTPO0

DFS2287I CLASS 2 AND 3 TERMINALSNOT BEING FOUND DURINGMULTINODE PERSISTENTPROCESS

ExplanationDuring the persistent session takeover process, VTAMnotifies IMS of session pending recovery for class 2and 3 terminal, but IMS cannot locate correspondingcontrol block in order to restore its session.

A diagnostic log record X'6710' is written to recordthe nodename of class 2 and 3 terminal whose controlblock was not found.


System actionIMS continues normal implementation, butpersistence is not restored for class 2 terminal.

Operator responseThe terminal can be restarted, as appropriate, usingnormal session initiation procedure.

System programmer responseLocate X'6710' log record and identify terminal thatneeded to be restarted.

ModuleDFSVTPO0

DFS2288W IMS CHECKPOINT PROCESSINGIS BEING DELAYED.

ExplanationThe checkpoint timer value expired before an IMScheckpoint completed its process.

System actionThe system continues running.

Operator responseThe terminal can be restarted, as appropriate, usingthe normal session initiation procedure.

System programmer responseThis message is a warning to the operator to look forsome process that is delaying checkpoint. If one isfound, the operator should take some action to ensurethat checkpoint gets completed quickly.

Module:DFSRCP00

DFS2290 INPUT MESSAGE CANNOT BECREATED SINCE NO OUTPUTMESSAGE IN PROGRESS.

ExplanationAn output message was not in progress when inputwas entered from the first physical page of a DPAGEwith multiple physical page input specified. The outputmessage was dequeued by a previous operator action:NXTMSG, or NXTMSGP.


Operator response:Issue a /FOR command for the current format tocreate a multiple physical page input message, a /FORcommand for a different format to create a singlephysical page input message, or clear the screen andenter the data.



DFS2291I Multi-line message with variablevalues

ExplanationA lock request timed out by IRLM and an IMS abend3310 was issued. This message supplies additionalinformation about the termination.

DS2291I is issued across multiple lines with variablevalues in the following format:

• DFS2291I LOCKNAME=resource_name• DFS2291I DBNAME=db_name

LOCKFUNC=lock_function• DFS2291I BLOCKER PST=PST_id TRAN=tran_name

PSB=PSB_name TYPE=region_type• DFS2291I BLOCKER TRANELAPSEDTIME=hr:mn:sc

IMSID=imsid• DFS2291I BLOCKER RECOVERY

TOKEN=recovery_token• DFS2291I WAITERxx PST=PST_number

TRAN=tran_name PSB=PSB_nameTYPE=region_type

• DFS2291I WAITERxx TRANELAPSEDTIME=hr:mn:sc• DFS2291I WAITERxx RECOVERY

TOKEN=recovery_token• DFS2291I WAITERxx PST=PST_number

TRAN=tran_name PSB=PSB_nameTYPE=region_type

• DFS2291I VICTIM TRANELAPSEDTIME=hr:mn:scIMSID=imsid

• DFS2291I VICTIM RECOVERYTOKEN=recovery_token


• DFS2291I TRANSACTION RETRY. DIAGNOSTICMESSAGE HAS REACHED MAXIMUM COUNT

The final line of the message, DFS2291ITRANSACTION RETRY. DIAGNOSTIC MESSAGE HASREACHED MAXIMUM COUNT, is issued only after thefifth retry of the same transaction. After receiving thismessage, no further instance of message DFS2291Iwill be issued on retries of the same transaction.

BLOCKERIndicates the transaction that was holding the lockresource identified by resource_name at the timewhen the long wait for the lock has timed out.

WAITERIndicates the transaction waiting on the same lockresource identified by resource_name at the timewhen the long lock exit is driven.

VICTIMIndicates the transaction that IRLM timed out. Thetransaction either abnormally terminates with a3310 abend, or receives status code BD becausethe LOCKTIME value has been exceeded for theIRLM lock request.

In the message text:resource_name

The 11- to 13-character identifier used by IMSto obtain a lock on the resource. resource_namecontains the data management block (DMB)number, data control block (DCB) number, orrelative byte address (RBA) of the resource thatthe transaction is requesting a lock for.

db_nameThe name of the database that IRLM is requestedto grant lock for.

lock_functionThe lock request function.

PST_idThe unique task ID that identifies the transaction.The ID refers one of the following options:number

The unique task number that identifies thetransaction.

SYSThe system ITASK lock owner.

IDTThe Residual Recovery Element (RRE) orIndoubt lock owner.

PST_numberThe unique task number that identifies thetransaction.

tran_nameThe transaction name.

PSB_nameThe PSB name used by the transaction.

region_typeThe type of IMS region that processes thetransaction.

hr:mn:scThe elapsed time, in hours, minutes and seconds.This value is between the time the transactionstarts (taken from PSTSPTIM) and the time the exitis called to gather IRLM long lock data for thistransaction.

imsidthe IMS ID.

recovery_tokenA 16-byte string that contains the IMS ID, a 4-byte origin application sequence number assignedat scheduling time, and a 4-byte count that isincremented at each commit process. For a batchapplication, the 16-byte string contains an 8-bytejob name and an 8-byte store clock value.

For batch jobs, the short form message DFS2291I isissued. The multi-line form of this message is usedin the log type X'67D0' subtype 1B records if theIEFRDER DD statement was specified.

For transactions being retried after the abend 3310,message DFS2291I is issued for a maximum offive times. When the maximum message count isreached, the message text is TRANSACTION RETRY.DIAGNOSTIC MESSAGE HAS REACHED MAXIMUMCOUNT is used.

System action:The dependent region terminates abnormally. Thetransaction is discarded, the transaction and PGM arenot stopped, and no memory dump is created.

System programmer responseExcept for protected messages, use the Non-Discardable Messages user exit (NDMX) to determinewhether to run the transaction again.

Terminate either the blocker (the application that isholding the lock) or the victim (the application waitingfor the lock). Use the blocker information in thismessage to terminate the application that is holdingthe lock or the application waiting for the lock. If morethan one application is waiting for the lock besidesthe victim, terminating the blocker causes IRLM togrant the lock to the next application waiting for theapplication, and it might not be the victim.


Problem determinationThe message provides information about thetransaction that is holding the lock as well astransactions that are waiting on the lock.

Module:DFSLMGR0


DFS2292E PTR=SYMB IS NOT SPECIFIED ONTHE LCHILD STATEMENT FOR DBDdbdname

ExplanationThe LCHILD statement to define a HISAM secondaryindex database or a SHISAM secondary index for aprimary DEDB database does not specify PTR=SYMBidentified in the DBD dbdname in the message.PTR=SYMB is the only valid pointer option for a FastPath secondary index database.

System actionThe ACB Maintenance utility stops processing for theDBD. The primary DEDB database and its secondaryindex databases are deleted from the ACB library.The ACB Maintenance utility continues to run and thereturn code is set to 8.

System programmer response1. Change PTR=SYMB on the LCHILD statements for

the DBD.2. Run the DBDGEN utility again.3. Run the ACB Maintenance utility with a BUILD

statement for the DBD.

ModuleDBFUDLB0

DFS2293E HISAM AND SHISAM INDEXESARE IN SAME PARTITON GROUPFOR DBD dbdname

ExplanationThe LCHILD statement specifies HISAM secondaryindex databases and SHISAM secondary indexdatabases in the same user data partition groupidentified in the DBD dbdname in the message. Auser data partition group must consist of all HISAMsecondary index partition databases or all SHISAMsecondary index partition databases.


Programmer response1. Change the user data partition group to contain all

HISAM secondary index databases or all SHISAMsecondary index databases in the NAME operandon the LCHILD statement for the DBD.

2. Run the DBDGEN utility again.3. Run the ACB Maintenance utility with a BUILD


ModuleDBFUDLB0

DFS2294E UNIQUE AND NON-UNIQUE KEYHISAM INDEXES ARE IN SAMEPARTITION GROUP FOR DBDdbdname

ExplanationThe LCHILD statement specifies unique key HISAMsecondary index databases and non-unique keyHISAM secondary index databases in the same userdata partition group identified in the DBD dbdname inthe message. A user data partition group must consistof all unique key HISAM secondary index partitiondatabases or all non-unique key HISAM secondaryindex partition databases.


Programmer response1. Change the user data partition group to contain all

unique key HISAM secondary index databases or allnon-unique key HISAM secondary index databasesin the NAME operand of the LCHILD statement forthe DBD.

2. Run the DBDGEN utility again.3. Run the ACB Maintenance utility with a BUILD




ModuleDBFUDLB0

DFS2295E SOME SENSEG STATEMENT ISINVALID FOR FAST PATHSECONDARY INDEX dbdname FORPCB pcbname IN PSB psbname

ExplanationOne or more SENSEG statements are invalid for FastPath secondary index dbdname for PCB pcbnamein PSB psbname. If the target segment is not aroot segment, only a subset of the segments areaccessible.

System actionThe ACB Maintenance utility stops processing for thePSB. The PSB is deleted from the ACB library. The ACBMaintenance utility continues to run and the returncode is set to 8.

Programmer responseUse the rules for SENSEG statements when the targetsegment is not a root segment to make the appropriatecorrections, run the PSBGEN utility again, and run theACBGEN utility with a BUILD statement for the PSB.

Correct the invalid SENSEG statements using thefollowing rules:

• If the target segment is not a root segment:

– All direct parent segments from the root segmentto the target segment must be specified inphysical order of the database structure.

– The direct parent segments of the target segmentare accessible. If you do not want a direct parentsegment of the target segment to be returned,specify the PROCOPT=K operand on the SENSEGstatement for that direct parent segment.

– The child segments of the target segmentare accessible. If you want to access a childsegment of the target segment, specify a SENSEGstatement for that child segment.

– Segments that are not the direct parent segmentsof the target segment or the child segments of thetarget segment are not accessible. The segmentsthat are not accessible cannot have a SENSEGstatement specified.

• If the target segment is a root segment, all segmentsunder the target segment are accessible.

ModuleDBFUDLB0

DFS2296A INCORRECT INPUT LOG DDSPECIFICATION


• A DD DUMMY was specified for an input log.• Multiple DD statements were specified, but a correct

ddname or order, or both was not specified.

System actionThe Database Backout utility, DFSBBO00, terminateswith a return code X'3C'.

Programmer responseCorrect the JCL and rerun the job.

DFS2297 PURGE KEYWORD IS INVALID,LINK NOT CTC

ExplanationA /PSTOP LINK PURGE command was entered, butlink is not channel-to-channel.


Master terminal operator response: Reenter thecommand with only one channel-to-channel link.

DFS2298A NEED MORE LOG DATA SETS FORBACKOUT OF PSB psbname

ExplanationA job that needs to be backed out does not have a syncpoint within the series of log data sets provided asinput to Batch Backout. Batch Backout must be rerunwith earlier log data sets included along with the logdata sets used in the run that gave this message.

System actionThe job terminates with a condition code of 64 beforeany backout is attempted.

Programmer responseRerun Batch Backout, and include earlier log data setsalong with the log data sets used in this run.

DFS2299A OPEN MNPS ACB WASNOT SUCCESSFUL REG15=xxACBERFLG=yyy, REPLY RETRY ORCANCEL


ExplanationAfter three attempts and still failing to open the MNPSACB during an MNPS XRF takeover, the alternate IMSsystem will issue the WTOR and await a reply from theoperator. xx is the OPEN return code in register 15,and yyy is the ACB error field returned by VTAM. Thesevalues are displayed as a decimal number. With a replyof RETRY, the alternate IMS will attempt another threetimes, if necessary, to open the ACB. With a reply ofCANCEL, the alternate system will stop attempting toopen the ACB and resume the takeover process. Anyreply other than RETRY or CANCEL is invalid, and theWTOR will be re-issued.

System actionIMS waits for a reply from the operator.

Operator responseCorrect the problem and reply to the WTOR.

System programmer responseFor a detailed explanation of the error codes, seez/OS Communications Server: SNA Messages, z/OSCommunications Server: SNA Programming, and z/OSCommunications Server IP and SNA Codes.

ModuleDFSHCI00

DFS2300I IMS-MS VERIFICATION UTILITY-RUN aaaaaaaa mm/dd/yyhh:mm:ss

Explanationaaaaaaaa is the day of the week, mm/dd/yy is thedate, and hh:mm:ss is the time.

System actionInput validation continues.




DFS2301I INPUT xxx...

Explanationxxx... is the input statement read from the SYSIN dataset.


DFS2302I SYSTEM MODULES

ExplanationThis message is a header. For a list of module namessee DFS2303I.


Related informationDFS2303Iaaaaaaaa

DFS2303I aaaaaaaa

Explanationaaaaaaaa is a module name built from valid input.


Programmer responseEnsure that these names are the modules to beverified.

DFS2304X xxx-CONTAINS A NON-NUMERICCHARACTER

Explanationxxx contained a character other than a digit. Validsuffixes are 1 to 255.

System actionValidation of input data is completed. No furtherprocessing occurs because the input data is invalid.

Programmer responseInput data must be numeric, from 1 to 255. Correctthe invalid input data and rerun the program.

DFS2305X aaaa-MORE THAN THREE DIGITS

ExplanationInput data aaaa contained more than three digits.

System actionValidation of input data is completed. No furtherprocessing occurs because input data is invalid.

Programmer responseInput data must be numeric, from 1 to 255, andexpressed as a 1 to 3-digit number.

DFS2306X aaa-IS NOT IN THE RANGE FROM1 TO 255

ExplanationInput data aaa was less than 1 or greater than 255; itmust be numeric from l to 255.


Programmer responseCorrect the invalid input data and rerun the program.

DFS2307X aaa-IS A DUPLICATE SUFFIX

ExplanationInput data aaa was already specified as input data.Input suffixes must appear only once for each programexecution.



Programmer responseCorrect the invalid input data and rerun the program.

DFS2308X AT LEAST TWO SYSTEMS MUST BESPECIFIED

ExplanationThere was no input data supplied, the input containedless than two valid suffix entries, or a blank wasencountered. Input processing on a statement isterminated when the first blank is found.


Programmer responseCheck that two or more valid suffixes were specified,that there are no embedded blanks in the input data,and that column 1 is not blank. Rerun the program.

DFS2309X PERMANENT I/O ERROR READINGDIRECTORY

ExplanationA return code of 8 resulted from a BLDL macro call.


Programmer responseSee the information on the BLDL macro completioncodes.


DFS2310X MODULE-DFSMSaaa-NOT FOUND

ExplanationThe BLDL searched the directory and did not findmodule DFSMSaaa. aaa represents the variableportion of the module name.


Programmer responseDetermine that the correct library is being accessed,the input data specifies the correct module suffixes tobe processed, and module DFSMSaaa is in the library.

DFS2311X PARTNER ID aa DEFINED MORETHAN TWICE AND IGNORED

ExplanationID aa was defined in logical links in three or moresystems.

System actionThe logical links are noted as being in error and, whenreferenced in the verification process, are treated asif they were not defined. The verification processcontinues.

Programmer responseSee DFS2312I. Correct this condition before thelogical links are included in the subsequent verificationprocess.

Related information“DFS2312I” on page 670aa IN LOGICAL LINK bbb DEFINED INDFSMSccc

DFS2312I aa IN LOGICAL LINK bbb DEFINEDIN DFSMSccc

ExplanationA partner ID can be referenced in only two systems,but one that appears in three or more was detected.aa is the 2-character partner ID. bbb is the logicallink number where the partner ID is defined. ccc isthe module suffix where the partner ID—logical linknumber—is defined. See DFS2311X. At least three ofthese messages are printed, one for each system thatdefines this partner ID.

System actionVerification continues without this logical link numberbeing included in the subsequent verification process.

Programmer responseDetermine which two references are correct andchange the rest.

Related information“DFS2311X” on page 670PARTNER ID aa DEFINED MORE THAN TWICEAND IGNORED

DFS2313X INCONSISTENT ATTRIBUTES INMSPLINKS ASSOCIATED WITHPARTNER ID aa



ExplanationPhysical links were defined in the logical linkdefinitions in two systems for partner ID aa, but theattributes of the physical links are not compatible.DFS2314I lists the incompatibility.

System actionVerification continues.

Programmer responseSee DFS2314I for more information.

Related information“DFS2314I” on page 671DFSMSaaa LOGICAL LINK bbbMSPLINK cccccccc DEFINED TYPE=ddd,BUFSIZE=eeeeefffffffffffff

DFS2314I DFSMSaaa LOGICAL LINKbbb MSPLINK ccccccccDEFINED TYPE=ddd,BUFSIZE=eeeeefffffffffffff

ExplanationDFSMSaaa is the system module name in which bbbis the logical link number. One of the attributesof the physical links assigned to the logical link isincompatible.aaa

is the system module suffixbbb

is the logical link numbercc...cc

is the physical link nameddd

is the physical link type which can be:BSC

stands for BISYNCMTM

stands for main storage-to- main storageCTC

stands for channel-to-channelVTAM

stands for synchronous data link control (SDLC)communications

eeeeeis the buffer size

ff...ffpresent only if the physical link type is BSC orVTAM

TYPE=BSCCONTROL=YES or CONTROL=NO (One BSCsystem must specify CONTROL=YES, and onemust specify CONTROL=NO.)

TYPE=VTAMSESSION=nnn (where nnn is the maximumnumber of parallel sessions allowed for thisMSC/VTAM link.)


Programmer responseSee message DFS2313X and correct the invalidattributes in the system.

Related informationDFS2313XINCONSISTENT ATTRIBUTES IN MSPLINKSASSOCIATED WITH PARTNER ID aa

DFS2315I DFSMSaaa LOGICAL LINK bbbID cc NOT ASSIGNED MSPLINKCORRESPONDING TO ddddddddIN DFSMSeee

ExplanationDFSMSaaa is the system module name in which bbbis the logical link number. This link does not have aphysical link assigned. The corresponding logical linkwith the partner ID cc in DFSMSeee has physical linkdddddddd assigned to it.

System actionVerification processing continues.

Programmer responseDetermine if the physical link is to be assigned atsystem definition or at execution. If it is to be assignedat definition, correct and rerun the program. If it is tobe assigned at execution, ignore this physical link errormessage.

DFS2316W DFSMSaaa MSPLINK bbbbbbbbNODENAME cccccccc DOES NOTMATCH APPLID dddddddd INDFSMSeee

ExplanationIn the MSVERIFY control block module DFSMSaaa, thephysical link bbbbbbbb defined with VTAM nodename(NAME=cccccccc) on the MSPLINK macro does not


match the APPLID=dddddddd defined on the COMMmacro of the partner MSVERIFY control block moduleDFSMSeee.

Either the VTAM APPLIDs of the IMS system and itspartner do not match or were statically specified (forexample, APPLID=NONE was specified on the COMMmacro) during system definition. This is not an error ifthe VTAM application program names that are resolvedat IMS execution-time match (for example, VTAMAPPLID of IMSA matches the partner nodename). Formore information about VTAM application programnaming conventions, see the VTAM publications.


Programmer responseVerify that the APPLID names conform to VTAMnaming conventions. If they do not, make thenecessary changes and rerun the verification program.

Problem determination:None.

DFS2317X PARTNER ID aa IN LOGICAL LINKbbb WITHIN DFSMSccc IS NOTDEFINED IN A SECOND SYSTEM

ExplanationA partner ID must be referenced in two systems.aa is the 2-character partner ID. bbb is the logicallink number where the partner ID is defined. ccc isthe module suffix where the partner ID—logical linknumber—is defined.

System actionThis path is flagged as not complete and verificationcontinues.

Programmer responseDetermine which system definition is incomplete.Correct and rerun the program.

DFS2318X SYSID sysid HAS AN INVALIDLOOP

Explanationsysid is the 4-digit SYSID in the SYSID tables for whichan invalid path has been found. DFS2319I furtherdescribes the error.


Programmer responseSee DFS2319I for SYSID aaa.

Related information“DFS2319I” on page 672DFSMSaaa MSNAME bbbbbbbb PARTNER ID ccLOGICAL LINK ddd INVOLVED IN LOOP

DFS2319I DFSMSaaa MSNAME bbbbbbbbPARTNER ID cc LOGICAL LINK dddINVOLVED IN LOOP

Explanationaaa is the module suffix. bbbbbbbb is the MSNAME. ccis the PARTNER ID. ddd is the logical link number forthe SYSID in this system. A loop means the logical linkpath defined loops back to itself without going to thelocal SYSID.

System actionThis path is flagged as invalid and verificationprocessing continues.

Programmer responseMore than one of these messages is issued, eachdescribing a SYSID path in a different system.Determine if the MSNAME references the wrongSYSIDs, if the MSNAME is connected to the wronglogical link number, or if the logical link definition usesthe wrong partner ID.

Correct, and rerun the program.

DFS2320X DFSMSaaa SYSID sysid IS NOTDEFINED

Explanationaaa is the module suffix name; sysid is the 4-digitSYSID. The referenced SYSID in system DFSMSaaawas not specified in an MSNAME definition. Eitherthe referencing system is in error by establishing apath to this DFSMSaaa system, or this DFSMSaaasystem definition is not correct because the MSNAMEdefinition does not correctly reference the SYSID sysid.



Programmer responseDetermine the system in error, correct the error, andrerun the program.

DFS2322I TRANSACTION DEQUEUED BYOPERATOR

ExplanationYou used the /DEQ or QUE TRAN OPTION(DEQxxx)command to dequeue the transaction before executingthe transaction.

System actionThe APPC or OTMA conversation has beendeallocated.

User response:Resubmit the transaction.

DFS2323X NO LOCAL DEFINED FOR SYSIDsysid

ExplanationWithin the total multiple systems configuration beingverified, sysid which is the 4-digit SYSID, has no localSYSID defined, and is referenced by another system.


Programmer responseDetermine where the local SYSID should be definedand define an MSNAME accordingly, or do not see thisSYSID in any system. Rerun the program.

DFS2324X MORE THAN ONE LOCAL DEFINEDFOR SYSID sysid

Explanationsysid is the 4-digit SYSID being scanned. In the scan ofthis SYSID for the total multiple systems configuration,the utility encountered more than one system wherethis SYSID is defined as local.


Programmer responseReview the total multiple systems configuration.Determine where the local for that SYSID should be

and redefine the systems referenced in DFS2325I,which follows this message.

Correct the error, and rerun the program.

Related information“DFS2325I” on page 673LOCAL DEFINED FOR DFSMSaaa

DFS2325I LOCAL DEFINED FOR DFSMSaaa

Explanationaaa is the suffix in which a local system is defined.This message is displayed with DFS2324X.


Programmer responseSee DFS2324X.

Related informationDFS2324XMORE THAN ONE LOCAL DEFINED FOR SYSIDsysid

DFS2326X DFSMSaaa SYSID sysid-MSNAMEcccccccc HAS NO PATH TO LOCALSYSID THROUGH DFSMSddd

Explanationaaa is the suffix of the system module. sysid isthe 4-digit SYSID. cccccccc is the MSNAME. IMSencountered a previous error that prevented systemDFSMSaaa from providing a path to the local systemthrough DFSMSddd at SYSID sysid.


Programmer responseA previous message references SYSID sysid, and isprobably the cause of the error. Alternatively, thepartner ID in the logical link assigned to SYSID sysidwas in error. Correct the previous errors for SYSIDsysid and rerun the program.

DFS2327I DFSMSaaa SYSID sysid ORMSNAME cccccccc SHOULD NOT BEASSIGNED TO LOGICAL LINK ddd


Explanationaaa is the system module suffix. sysid is the 4-digitSYSID. cccccccc is the MSNAME. ddd is the logical linknumber. Assigning SYSID sysid or MSNAME ccccccccto logical link ddd would cause an invalid path to thelocal SYSID. This message is only issued if PARM=ALLis specified in the execute statement.


Programmer responseDo not make the assignment specified.

DFS2330I DFSMSaaa SYSID sysid cccccdddddddd NOT VERIFIED

Explanationaaa is the system module suffix. sysid is the 4-digitSYSID. ccccc is either TRANS or LTERM. ddddddddis the TRANS/LTERM name. A previously determinederror condition caused this TRANS/LTERM not tobe verified. A DFS2323X message or a DFS2324Xmessage was displayed for the SYSID.


Programmer responseCorrect the original problem as referenced inDFS2323X or DFS2324X. Rerun the program.

Related information“DFS2323X” on page 673NO LOCAL DEFINED FOR SYSID sysid“DFS2324X” on page 673MORE THAN ONE LOCAL DEFINED FOR SYSIDsysid

DFS2331X DFSMSaaa SYSID sysid cccccdddddddd IS NOT DEFINEDWITHIN DFSMSeee LTERMdddddddd MAY BE A DYNAMICRESOURCE

ExplanationA remote TRANS or LTERM cannot be found inDFSMSeee, in which the SYSID, sysid, is defined aslocal.


sysidthe 4-digit SYSID

cccccTRANS or LTERM

ddddddddthe TRANS or LTERM name

If the resource not defined is an LTERM, the resourcecan be dynamically created in the remote system. Thisshould be verified manually.


System programmer responseThis message occurs when:

• The TRANS or LTERM references the wrong remoteSYSID.

• The TRANS or LTERM is not defined in the systemspecified.

• The LTERM is defined as remote in the specifiedsystem.

• The LTERM is a dynamically created resource in theremote system.

If the LTERM is intended to be a dynamically createdresource, this message can be ignored. Otherwise,determine why the LTERM was created dynamically,correct the erroneous condition, and rerun theprogram.



DFS2332X SYSID sysid TRANS bbbbbbbbHAS INCOMPATIBLE ATTRIBUTESBETWEEN SYSTEMS

ExplanationVariable sysid is the 4-digit remote SYSID referencedby transaction bbbbbbbb. This message will befollowed by two DFS2333I messages that display theattributes of transactions in the two systems.


System actionThe transaction description message will be displayedfor both systems; then verification processingcontinues.

Programmer responseSee the description for DFS2333I.

Related information“DFS2333I” on page 675DFSMSaaa bbbbbb,MSGTYPE=ccccccc,INQUIRY=ddd,eeeeeee, fffffffff,ggggg

DFS2333I DFSMSaaabbbbbb,MSGTYPE=ccccccc,INQUIRY=ddd,eeeeeee,fffffffff,ggggg

ExplanationIn the message text:aaa

System module suffix.bbbbbb

Either REMOTE or LOCAL.ccccccc

SNGLSEG or MULTSEG.ddd

YES or NO.eeeeeee

RECOVER or NORECOV.fffffffff

FPATH=YES or SPA=nnn, where nnn is the SPAsize.

gggggThe type of SPA—FIXED or BLANK.


Programmer responseDetermine which system has the incorrect attributesand correct them. Rerun the program.

DFS2334X DFSMSaaa SYSID sysid cccccdddddddd HAS NO RETURN PATHTO DFSMSeee

Explanationeee is the system module suffix in which ccccc (TRANSor LTERM), named dddddddd, has defined the 4-digit

SYSID, sysid, as the return path. SYSID sysid isundefined, or is defined as a local.


Programmer responseDetermine whether SYSID sysid should be defined asremote in system DFSMSaaa or if DFSMSeee (TRANSor LTERM dddddddd) defined the wrong SYSID forthe return path. Correct the system, and rerun theprogram.

DFS2335I DFSMSaaa SYSID sysid cccccdddddddd RETURN PATH TODFSMSeee NOT VERIFIED

Explanationaaa is the processing system module suffix. sysid isthe 4-digit return SYSID. ccccc is either TRANS orLTERM. dddddddd is the TRANS/LTERM name. eeeis the originating system module suffix. A previouslydetermined error condition caused this TRANS/LTERMreturn path not to be verified. A DFS2324X message isdisplayed for SYSID sysid.


Programmer responseCorrect the original problem referred to in DFS2324X.Rerun the program.

Related information“DFS2324X” on page 673MORE THAN ONE LOCAL DEFINED FOR SYSIDsysid

DFS2336A INSUFFICIENT STORAGE TOACQUIRE SBPSS CONTROL BLOCK

ExplanationIMS was unable to acquire enough storage from theCSA (Common Storage Area) to build the SBPSS, acontrol block used by Sequential Buffering (SB) in anIMS online environment.

System actionThe IMS online system can no longer use SequentialBuffering.


User responseProvide more virtual storage for IMS.

DFS2337A INSUFFICIENT STORAGE TOACQUIRE PST EXTENSION FORSEQUENTIAL BUFFERING

ExplanationIMS was unable to acquire a PST extension used forSequential Buffering.

System actionThe IMS online system can no longer use SequentialBuffering.

User responseFor IMS DB/DC with LSO=N, allocate more CSAstorage; for IMS DB/DC with LSO¬=N, IMS batch, orDBCTL, allocate more private storage.

DFS2338I xxxxxxxx CAN NOT BE LOADED,RC=nn

ExplanationThe IMODULE macro was unable to load modulexxxxxxxx. For an explanation of IMODULE return codenn, see the IMODULE return code information.

System actionIMS cannot use Sequential Buffering.

User responseCorrect the error based on the code returned from theIMODULE macro.


DFS2339I SEQUENTIAL BUFFERING UNABLETO ISSUE ERROR MESSAGE

ExplanationSequential Buffering was unable to acquire a workarea used for issuing an error message.

System actionIMS sends this message instead of the one it intendedto send.

User responseAllocate more virtual storage for IMS.

DFS2340I CONTROL CARDS IN //DFSCTL CONTAIN ERRORS,JOBNAME=xxxxxxxx

ExplanationThe Sequential Buffering (SB) control statements inthe //DFSCTL data set for JOB xxxxxxxx contained oneor more errors. DFS messages describing the errorswere previously written to the JES log for the job, aswell as to the z/OS consoles.

System actionDFS messages were written to the JES log for the joband to the z/OS consoles.

User responseSee the DFS messages written to the JES log for thejob and to the z/OS consoles.

DFS2341I SPARSE|PARTITION EXITexitname FOR DEDB dedbname ISLOADED|DELETED

ExplanationThe sparse routines or partition selection routineswere either deleted or reloaded.

In the message text:exitname

The name of the exit routine that was deleted orreloaded

dedbnameThe name of the DEDB



Module:DBFMSIU0

DFS2342E IMS ver.rel REQUIRES facility

ExplanationAn IMS address space could not be started becauseIMS required a system facility that was unavailable.Facilities that prevent IMS from starting can includehardware (including not having a particular hardware



level or facility) and software (including not havinga required software component installed or at thecorrect level).

The information in the messages is:ver.rel

The IMS version and release level.facility

The facility IMS needed that was unavailable. Thevalue of facility can be one of the following:Z/ARCHITECTURE MODE

IMS can only run on processors running in z/Architecture mode. ESA and below is no longersupported. You must either re-IPL your z/OSsystem in z/Architecture mode, or you mustmove the IMS address space to a differentmachine that is running in z/Architecturemode.

64-BIT VIRTUAL SUPPORTYou can only run IMS on a z/OS releasethat has 64-bit virtual storage support. If youreceive this message, then you are runningIMS under a non-supported z/OS level thatdoes not allow 64-bit virtual storage. You mustupgrade your z/OS to the minimum level for thecurrent release of IMS.

SYSTEM Z10 OR HIGHERIMS 15 and later can execute only on a Systemz10 processor (machine type 2097) or above.See the IMS Version 15 Release Planning for acomplete list of supported processors.

System actionIMS terminates with an abend 0684, and the addressspace does not start.

System programmer responseMake the facility indicated available on the machineon which you run IMS, or else run IMS on a differentmachine that has the indicated facility.

Module:DFSVCI00

Related referenceProcessor requirements (Release Planning)Related informationIMS abend 0684

DFS2343A - //SYSIN CONTROL CARDSCONTAINS ERROR(S)

ExplanationThe SB test program control statements in the //SYSINdata set contained one or more errors.

You can find more detailed error descriptions in the //SYSPRINT data set immediately after the listing of theincorrect control statements.


User responseCorrect the errors based on error descriptionsfollowing the listing of each incorrect controlstatement in the //SYSPRINT data set.

DFS2344I NBR OF SELECTED IMAGE-CAPTURE RECORDS FROMSYSUT1= nnnnnnnn

Explanationnnnnnnnn indicates the number of image capturerecords the Sequential Buffering (SB) test programselected to process, including the number of imagecapture records that cannot be processed.

DFS2345W NBR OF SELECTED RECORDSSKIPPED WITH BLOCK-NBROUTSIDE OF DB DATA SET:nnnnnnnn

ExplanationThe Sequential Buffering (SB) test program(DFSSBHD0) did not process some of the imagecapture records in the //SYSUT1 data set because therelative block number in the image capture recordswas outside the actual limits of the database data set.

This error can happen only when all of the followingconditions occur:

• The databases were reorganized between theoriginal image capture and the execution of the testprogram.

• The database reorganization reduced the number ofblocks in the database data sets.

• A DBIO YES control statement was provided in the //SYSIN data set.

System actionThe SB test program does not process those imagecapture records having relative block numbers outsidethe actual database data set limits.


http://www.ibm.com/support/knowledgecenter/SSEPH2_15.1.0/com.ibm.ims15.doc.rpg/ims_processors.htm#ims_processors


User responseThe reprocessing of the image capture records bythe SB test program will not match the processingof the application that generated the image capturelog records. Investigate running the SB test programwithout a DBIO YES control statement.

DFS2346W NBR OF SELECTED RECORDSSKIPPED BECAUSE DB DATA SETSARE NOT OPEN: nnnnnnnn

ExplanationThe Sequential Buffering (SB) test program(DFSSBHD0) did not process some of the imagecapture records in the //SYSUT1 data set because IMSwas unable to open some of the specified databasedata sets.

z/OS or IMS, or both, messages that usually precedethis message describe more fully why the databasedata sets could not be opened.

System actionThe SB test program does not process those imagecapture records belonging to the data sets that are notopen.

User responseThe reprocessing of the image capture log records bythe SB test program will not match the processingof the application that generated the image capturerecords.

Correct the error based on previously issued IMS orz/OS messages, or both. Make sure that all requiredDD statements for the database data sets and //DFSVSAMP specifications are present and correct.

DFS2347A INITIALIZATION ERROR

ExplanationIMS was unable to acquire enough virtual storage forsome smaller work areas at IMS initialization time.


User responseAllocate more private storage for IMS.

DFS2348W INTERFACE ERROR BETWEENDFSSBIO0 AND OSAM FORPSB=xxxxxxxx, DDN=yyyyyyyy

ExplanationIMS detected an interface error between theDFSSBIO0 module and the OSAM access method. Thisproblem is an IMS error.

System actionIMS creates SNAP dumps and deactivates the use ofSequential Buffering (SB) for the current application.If the application is running in a batch region, it isterminated abnormally.

User responseAllocate more virtual storage for IMS.

DFS2349W LENGTH OF NEXT AREA MIGHT BEINCORRECT

ExplanationAn IMS dump-formatting module was requested toformat an area that seems unreasonably long.

System actionThe IMS dump-formatting module formats only thebeginning of the requested area, if possible.


DFS2350I SNAP-WORKAREA CAN NOT BEGETMAINED

ExplanationIMS module DFSSBSN0 was unable to acquire a workarea to SNAP Sequential Buffering (SB) control blocksor areas.

System actionIMS abnormally terminates the application.





DFS2351A SB NOT OPERATIONAL:SOFTWARE PROBLEMS PREVENTUSAGE OF SB

ExplanationIMS software problems prevent further use ofSequential Buffering (SB) during the current IMS run.Previous messages to the z/OS or MTO consoles, orboth, describe the type of software problem.

System actionIMS does not use SB during the rest of the current IMSexecution.

User responseCorrect the problem based on the error messages IMSpreviously issued.

DFS2352W SOME SB CONTROL BLOCKSCOULD NOT BE GETMAINED

ExplanationIMS software problems prevented a successfulGETMAIN of some Sequential Buffering (SB) controlblocks.

System actionThe application program has partial or no benefit fromSequential Buffering.

User responseAllocate more virtual storage for IMS, if appropriate. Apreviously issued message tells what storage was notacquired by GETMAIN.

DFS2353W SOME SB BUFFERS COULD NOT BEGETMAINED

ExplanationIMS software problems prevented a successfulGETMAIN of some Sequential Buffering (SB) buffers.

System actionThe application program has partial or no benefit fromSequential buffering.


DFS2354W MAXSB= LIMIT EXCEEDED

ExplanationThe MAXSB storage limit specified in memberDFSVSMxx of IMS.PROCLIB (for IMS online) or the //DFSVSAMP data set (for batch) was exceeded. TheMAXSB limit specifies the maximum amount of storagethat IMS can allocate for Sequential Buffering (SB)buffers.

System actionThe application program has partial or no benefit fromSB.

User responseIncrease the MAXSB limit, if appropriate.

DFS2355W SOME SB BUFFERS OR BLOCKSCOULD NOT BE PAGE-FIXED

ExplanationIMS was unable to page fix Sequential Buffering(SB) buffers or control blocks, possibly because realstorage was unavailable.

System actionThe application program has partial or no benefit fromSB.

User responseIf too much buffer space is allocated to SB, decreasethis amount, if appropriate.

DFS2356W IOSB OR ITASK BLOCKS COULDNOT BE ACQUIRED


ExplanationSequential Buffering (SB) was unable to acquireenough OSAM IOSB or ITASK-related control blocks toprovide the maximum amount of overlapped I/O.

System actionThe amount of overlapped SB I/O for the applicationprogram or utility is limited.

User responseIf message DFS2342I was previously issued,investigate using a larger value for the IOB parameterwhen you start the IMS batch JCL procedure.

DFS2357W OPEN FOR DBD=xxxxxxxx NOTSUCCESSFUL

ExplanationIMS was unable to open a database PCB for DBDxxxxxxxx.

System actionThe Sequential Buffering (SB) test program(DFSSBHD0) continues to run. If the unopeneddatabase PCB is associated with image capturerecords in the //SYSUT1 data set, the SB test programdoes not process the records and prints the numberof unprocessed records at the end of the job step inmessage DFS2346W.

User responseCorrect the error based on messages related to OPENproblems if message DFS2346W is printed at the endof the job step. Otherwise, ignore this message.

Related information“DFS2346W” on page 678NBR OF SELECTED RECORDS SKIPPEDBECAUSE DB DATA SETS ARE NOT OPEN:nnnnnnnn

DFS2358I NO STORAGE AVAILABLE FORDFSERA20 - WORKAREA

ExplanationThe GETMAIN for the DFSERA20 dynamic work areafailed to acquire the required space.

System actionThe caller of DFSERA20 is returned to and IMS doesnot take a SNAP memory dump.

User responseIncrease address space to obtain the requested workarea.

DFS2359I - DFSCIR NOT SUCCESSFUL FORPSB=xxxxxxxx, ERROR CODE=yyy

ExplanationIMS was unable to initialize an ITASK for theoverlapped sequential I/O for PSB xxxxxxxx. TheDFSCIR macro returned error code yyy in register 15.

System actionSequential Buffering (SB) does not use overlappedsequential read for some PCBs or database data sets,or both.

User responseContact IBM Software Support for assistance indetermining the problem.

DFS2360I XCF GROUP JOINEDSUCCESSFULLY.

ExplanationIMS has joined the OTMA XCF group successfully.


Module:DFSYJL00

DFS2361I XCF GROUP CLOSEDSUCCESSFULLY.

ExplanationIMS has left the OTMA XCF group successfully.


Module:DFSYJL00

DFS2362I XCF GROUP JOIN FAILURE.ALREADY JOINED.

ExplanationIMS cannot join an OTMA XCF group if it is already amember of that group.


System actionProcessing continues using the original XCF group.

Programmer responseCheck the /START OTMA command and reissue ifnecessary.

Module:DFSYJL00

DFS2363I XCF GROUP CANNOT BE JOINED.NOT APF AUTHORIZED.

ExplanationIMS was not APF-authorized and therefore wasnotable to join the OTMA XCF group.

System actionProcessing continues with OTMA disabled.

System programmer responseEnsure IMS is APF-authorized.

Module:DFSYJL00

DFS2364E RC=rc REASON=reason XCF JOINFAILURE.

ExplanationIMS cannot join the OTMA XCF group due to theindicated four-byte XCF return and reason codes (fromIXCJOIN).

System actionProcessing continues with OTMA disabled.

Programmer responseCheck the meaning of the return and reason codes,and correct the error.

Module:DFSYJL00

Related referencez/OS: IXCJOIN return and reason codes

DFS2365I CANNOT LEAVE XCF GROUP. NOTJOINED.

ExplanationIMS cannot leave an OTMA XCF group if it is not amember of that group.


Programmer responseCheck the /STOP OTMA command and reissue ifnecessary.

Module:DFSYJL00

DFS2366E PARTITION SPECIFIED INPROCSEQD OPERAND IS NOTTHE FIRST PARTITION FOR PCBpcbname IN PSB psbname

ExplanationUser partitioning is requested for a Fast Path HISAMor SHISAM secondary index database. However, theuser partition database specified in PROCSEQD on thePCB statement is not the first user partition in theuser partition group as defined in NAME operand of theLCHILD statement in the primary DEDB database DBD.

System actionThe ACB Maintenance utility stops processing for thePSB. The primary PSB identified in the message isdeleted from the ACB library. The ACB Maintenanceutility continues to run and the return code is set to 8.

Programmer response1. Change the PROCSEQD operand on the PCB

statement to specify the first user partitiondatabase in the user partition group.

2. Run the PSBGEN utility again.3. Run the ACB Maintenance utility for the PSB.

Module:DBFUDLB0

DFS2367E DFS2367E PSELOPT OPERANDIS SPECIFIED BUT USERPARTITIONING IS NOTREQUESTED FOR PCB pcbname INPSB psbname

ExplanationUser partitioning is not requested for Fast Path HISAMsecondary index databases or Fast Path SHISAMsecondary index databases. Only one secondary indexdatabase is specified in the NAME operand on theLCHILD statement in the primary DEDB database DBD.However, the partition selection option (PSELOPT)



operand is specified on the PCB statement for theprimary DEDB database.

System actionThe ACB Maintenance utility stops processing for thePSB. The primary PSB identified in the message isdeleted from the ACB library. The ACB Maintenanceutility continues to run and the return code is set to 8.

Programmer response1. Remove the PSELOPT operand on the PCB

statement.2. Run the PSB Generation utility again.3. Run the ACB Maintenance utility for the PSB.

Module:DBFUDLB0

DFS2368I OIC TCB INITIALIZATIONCOMPLETE

ExplanationThe OTMA server task control block (TCB) is initializedand the OTMA server is ready for processing.


Module:DFSYCTL0

DFS2369I OIM TCB INITIALIZATIONCOMPLETE

ExplanationThe OTMA client task control block (TCB) is initializedand the OTMA client is ready for processing.

There is one OIM TCB for each TMEMBER. As theOTMA workload requires, new TCBs can be initializedduring an IMS session. Each time this processhappens, this message is issued.


Module:DFSYIM00

DFS2370I INVALID RETURN CODE rc FROMUSER EXIT exitname

ExplanationA user exit routine returned an invalid return code.


The 2-byte return code.exitname

The 8-byte user exit routine name. The routine isusually DFSYPRX0 or DFSYDRU0.

Programmer responseCorrect the exit routine.

Module:DFSYFND0

DFS2371I OTMA DRU OVERRIDE LIMITREACHED

ExplanationThe override limit was reached for a DFSYDRU0exit routine, and the routine attempted to specifya new client to which to route messages. Only oneDFSYDRU0 exit can specify a new client.

Programmer responseCorrect the DFSYDRU0 exit routine, especially theclient override logic.

Module:DFSYFND0

DFS2372I INVALID MEMBER NAME SET BYDFSYPRX0

ExplanationAn OTMAYPRX user exit routine specified an OTMAtransaction, but did not specify an OTMA client name.This message is issued only when the transaction isentered from a non-OTMA source.

Programmer responseCorrect the OTMAYPRX user exit, especially the clientoverride logic.

Module:DFSYFND0

DFS2373I OTMA DRU OVERRIDE TO INVALIDTMEMBER

ExplanationA DFSYDRU0 user exit routine requested to use a newclient. However, the client name specified was eithernot provided or was the same as the current client forwhich the exit was called.


Programmer responseCorrect the DFSYDRU0 exit routine, especially theclient override logic.

Module:DFSYFND0

DFS2374W OTMA GROUP NAME HASCHANGED FROM oldname TOnewname.

ExplanationDuring a warm or emergency restart, IMS wasjoining the XCF group newname for OTMA processing.However, this group is different from the group nameoldname contained in restart log records.


Programmer responseEnsure that the group name newname specified in thestartup procedure is correct.

Module:DFSYRST0

DFS2375W IMS HAS CHANGED ITS OTMAMEMBER NAME FROM oldname TOnewname.

ExplanationDuring a warm or emergency restart, IMS wasconnecting to an OTMA client newname which isdifferent than the client name oldname contained inrestart log records.


Programmer responseEnsure that the client name newname is known to allOTMA clients that connect to IMS.

Module:DFSYRST0

DFS2376W IMS OTMA MEMBER NAME nameIS THE SAME AS A PREVIOUSLYACTIVE CLIENT.

ExplanationDuring a warm or emergency restart, the IMS OTMAclient name name was the same as that of an existingOTMA client. That client is no longer able to connect toIMS.


Programmer responseEnsure that the IMS OTMA client name name iscorrect.

Module:DFSYRST0

DFS2377A SYSIN: end-of-file.

ExplanationThe SYSIN control statement of the HALDB MigrationAid utility (DFSMAID0) was missing.

System actionThe utility processing terminates.

System programmer responseAdd a SYSIN control statement to the JCL and rerunthe utility.

Module:DFSMAID1

DFS2378A Error parsing SYSIN.

ExplanationThe SYSIN control statement of the HALDB MigrationAid utility (DFSMAID0) was incorrect. Some of thethings to look for are missing blanks betweenparameters, or missing C' or X' immediately followingKR= field.


System programmer responseCorrect the error in SYSIN control statement and rerunthe utility.

Module:DFSMAID1

DFS2379A A single ' found in a characterstring.

ExplanationThe SYSIN control statement of the HALDB MigrationAid utility (DFSMAID0) had a single quotation markwithin the character string of KR= field; for example,KR=C'ZZZ'ZZ' instead of KR=C'ZZZZZZ'.



System programmer responseRemove the single quote in the character string andrerun the utility.

Module:DFSMAID1

DFS2380A Unsorted keys in SYSIN.

ExplanationThe SYSIN control statement of the HALDB MigrationAid utility (DFSMAID0) contained key ranges that arenot in ascending order.

For example, the user coded KR=C'J00400' followedby KR=C'J00200'.


System programmer responseList the key range fields in ascending order and rerunthe utility.

Module:DFSMAID1

DFS2381A CTDLI ('GSCD') returned status xx.

ExplanationThe C Language program to DLI macro with GSCDsystem service call returned a status code of xx.


System programmer responseSee an explanation of the xx status code received. Ifthe problem persists, call IBM Software Support.

Module:DFSMAID1

Related referenceEXEC DLI commands (Application ProgrammingAPIs)

DFS2382I THE NUMBER OF OTMA TYPE DDESCRIPTORS IS NOW BELOWTHE MAXIMUM OF nnn

ExplanationThe number of OTMA destination (type D) descriptorswas at the maximum value, but it is now less than themaximum.

In the message text,nnn

The maximum number of allowable OTMAdestination descriptors is 510.

Programmer responseOTMA destination (type D) descriptors can once againbe added by the CREATE OTMADESC command.

Module:DFSYCMR0

DFS2383E ENCOUNTERED DATABASERECORDS LARGER THAN 16M.PLEASE USE SAMPLING ANDRERUN THE UTILITY.

ExplanationThe HALDB Migration Aid Utility (DFSMAID0)encountered database records larger than 16 MB.Sampling should be used.

System actionThe utility terminates with RC = 103.

System programmer responseAdd SAMPLE=xxx in the SYSIN control statement andrerun the utility.

Module:DFSMAID0

DFS2384W THE NUMBER OF OTMA TYPEt DESCRIPTORS IN MEMBERmember HAS REACHED THEMAXIMUM OF nnn

or

THE NUMBER OF OTMA TYPE t DESCRIPTORS HASREACHED THE MAXIMUM OF nnn

ExplanationThe number of OTMA type-t descriptors that aredefined in the OTMA DFSYDTx PROCLIB member hasreached the maximum allowable number for type-tdescriptors.


http://www.ibm.com/support/knowledgecenter/SSEPH2_15.1.0/com.ibm.ims15.doc.apr/ims_execdlicmds.htm#ims_execdlicmds

http://www.ibm.com/support/knowledgecenter/SSEPH2_15.1.0/com.ibm.ims15.doc.apr/ims_execdlicmds.htm#ims_execdlicmds

tThe descriptor type, either D or M.

Type D descriptors are OTMA destinationdescriptors. Type M descriptors are OTMA clientdescriptors and the DFSOTMA descriptor, if it isdefined.

memberThe name of the OTMA DFSYDTx member inthe IMS.PROCLIB data set that contains thedescriptors.

nnnThe maximum allowable number of descriptors forthe descriptor type identified by t.

The second form of the message is displayed whenthe maximum value is reached as a result ofadding descriptors by using the CREATE OTMADESCcommand.

Programmer responseNo more descriptors of the listed type can be addedunless the maximum allowable number of descriptorsis increased or one or more existing descriptors aredeleted. Alternatively, existing descriptor definitionscan be changed to refer to new clients or destinations.

The maximum for client (type-M) descriptors isdefined by the MDESCMAX parameter in the DFSOTMAdescriptor. The default is 255.

The maximum for destination (type-D) descriptors isdefined by the DDESCMAX parameter in the DFSOTMAdescriptor. The default is 510.

For destination descriptors for ALTPCB destinations,if you cannot increase the maximum allowablenumber and you cannot delete or modify any existingdestination descriptors to accommodate the newdescriptor, you can code the definitions in theOTMA Destination Resolution exit routine (OTMAYPRX)and the OTMA User Data Formatting exit routine(DFSYDRU0).

Module:DFSYIDC0, DFSYCMR0

DFS2385E SYNTAX ERROR FOR DESCRIPTOR= descriptor errortext

ExplanationAn OTMA descriptor parsing error has occurred. Formore information, see the DFS1956E message forLU 6.2 descriptor parsing errors. descriptor is the 16byte descriptor name. errortext is one of the followingvalues:

• ABEND MUST BE YES OR NO

• ABEND ONLY VALID ON DFSOTMA• ALTPCBE NOT VALID FOR DFSOTMA DESCRIPTOR• DDESCMAX MUST BE 1 TO 4 CHARACTERS LONG• DDESCMAX ONLY VALID ON DFSOTMA• DRU COULD NOT BE LOADED• DRU MUST BE 1 TO 8 CHARACTERS LONG• DRU NOT VALID FOR DFSOTMA DESCRIPTOR• DSAP MUST BE 1 TO 3 CHARACTERS LONG• DSAPMAX MUST BE 1 TO 3 CHARACTERS LONG• DUPLICATE ABEND KEYWORD• DUPLICATE DDESCMAX KEYWORD• DUPLICATE DRU KEYWORD• DUPLICATE DESCRIPTOR NAME FOUND• DUPLICATE DSAP KEYWORD• DUPLICATE DSAPMAX KEYWORD• DUPLICATE EXIT KEYWORD• DUPLICATE LIMITRTP KEYWORD• DUPLICATE LITETP KEYWORD• DUPLICATE LOGSTR KEYWORD• DUPLICATE MDESCMAX KEYWORD• DUPLICATE MULTIRTP KEYWORD• DUPLICATE RMTSEC KEYWORD• DUPLICATE SYNTIMER KEYWORD• DUPLICATE WLMLTRM KEYWORD• EXIT MUST BE YES OR NO• ILLEGAL KEYWORD• INVALID MEMBER NAME• LIMITRTP MUST BE 1 TO 4 CHARACTERS LONG• LITETP ONLY VALID ON DFSOTMA• LITETP MUST BE YES OR NO• LOGSTR MUST BE YES OR NO• LOGSTR NOT VALID FOR DFSOTMA DESCRIPTOR• MAXTP MUST BE 1 TO 6 CHARACTERS LONG• MDESCMAX MUST BE 1 TO 4 CHARACTERS LONG• MDESCMAX ONLY VALID ON DFSOTMA• MEMBER NAME LONGER THAN 16 CHAR• MEMBER NAME NOT GIVEN OR BEGINS AFTER

COLUMN 3• MULTIRTP MUST BE YES OR NO• NO PARAMETER GIVEN FOR THIS KEYWORD• NON-NUMERIC CHARACTERS WERE FOUND IN THE

LIMITRTP PARAMETER• NON-NUMERIC CHARACTERS WERE FOUND IN THE

SYNTIMER PARAMETER


• NON-NUMERIC FOUND IN DDESCMAX PARAMETER• NON-NUMERIC FOUND IN DSAP PARAMETER• NON-NUMERIC FOUND IN DSAPMAX PARAMETER• NON-NUMERIC FOUND IN MDESCMAX PARAMETER• RMTSEC MUST BE 1 CHARACTER LONG• RMTSEC MUST BE N, C, OR F• RMTSEC ONLY VALID FOR TYPE=IMSCON• SECOND COLUMN MUST BE BLANK• SYNTIMER MUST BE 1 TO 6 CHARACTERS LONG• T/O NOT VALID FOR DFSOTMA DESCRIPTOR• UNRECOGNIZED CHARACTERS FOUND DURING

KEYWORD SEARCH• WLMLTRM MUST BE YES OR NO• WLMLTRM ONLY VALID FOR DFSOTMA• WLMLTRM ONLY VALID FOR TYPE M DESCRIPTOR

Note: Keywords displayed before the error text are8-characters in length, except for the following casesin which up to 10 characters might be displayed beforethe error text for the incorrect keyword specified:

• If the error text is ILLEGAL KEYWORD for OTMAclient descriptor or DFSOTMA descriptor

• If a duplicate keyword is parsed for OTMA clientdescriptor or DFSOTMA descriptor

Programmer responseCorrect the problem as described in the errortext..

Module:DFSYIDC0

Related information“DFS1965E” on page 573APPC/MVS CALL FAILURE,FUNCTION=aaaaaaaa, REASON CODE=xxyy,RETURN CODE=xxxxxxxx, LUNAME=nnnnnnnn

DFS2386I OTMA IS CONNECTING TO THEMEMBER xxxxxxxxxxxxxx

ExplanationIMS OTMA has received a connection request from amember with the XCF member name xxxxxxxxxxxxxx.


System actionOTMA makes the connection by initializing the OTMAmember blocks with the connection requests andsends a confirmation message (ACK) to the OTMAmember.

Programmer responseIMS automated operator interface (AOI) exits candetect this message to identify whether a particularmember has connected to IMS OTMA.

Module:DFSYMOM0

DFS2387X UNABLE TO OPEN SYSOUT DATASETS

ExplanationAn OPEN error occurred while attempting to open theSYSOUT data set.

System actionThe Multiple Systems Verification utility is terminated.

Programmer responseCorrect the OPEN failure, and rerun the job.

DFS2388X UNABLE TO OPEN SYSIN DATA SET

ExplanationAn OPEN error occurred while attempting to open theSYSIN data set.

System actionThe Multiple Systems Verification utility is terminated.

Programmer responseCheck the SYSIN DD statement. Correct the OPENfailure, and rerun the job.

DFS2389I XCF SEND RC=xxxxxxxxREASON=yyyyyyyy,

ExplanationOTMA called MVS/XCF IXCMSGO to issue a send, butthe send failed.

Programmer responseCheck the meaning of the return and reason codes.


Module:DFSYSND0

Related referencez/OS: IXCMSGO return and reason codes




DFS2390I FP TRAN tttttttt SEND FAIL.TPIPE=ppppppppMember=mmmmmmmmmmmmmmmm MSG:xxxxxxxx

ExplanationAn application program send failed or received a NACKmessage from the OTMA client during the processingof transaction tttttttt. MSG xxxxxxxx contains up to 40characters of the output message being processed.

System actionThe output transaction identified by this message isdeleted from the IMS system.

Programmer responseCorrect the cause of failed send or the NACK messagefrom the client.


ModuleDFSYSLM0


DFS2391I MESSAGE DEQUEUE FAILEDDURING RESYNCH FOR TMEMBER= xxxxxxxxxxxxxxxx TPIPE =xxxxxxxx

ExplanationAn IMS queue manager dequeue call that was issuedduring resynchronization failed.


System actionThe NACK X'0026' message is generated andresynchronization for the Tpipe is stopped.

Programmer responseContact the IBM Software Support for assistance indetermining the problem.

ModuleDFSYQAB0

DFS2392I COMMAND NOT ALLOWEDDURING RESYNCH

ExplanationIf the /DEQUEUE command is issued while OTMAresynchronization is in progress, this message isissued.


ModuleDFSYCLJ0

DFS2393I SRVRESYNCH REJECTED BYTMEMBER=xxxxxxxxxxxxxxxx

ExplanationThe OTMA client rejected the SRVresynch commandissued by IMS for OTMA resynchronization.


System actionOTMA resynchronization stops.

Programmer responseCheck the client's resynchronization logic and performthe resynchronization, if needed.

ModuleDFSYMEM0

DFS2394I CLBID RECEIVED FORTMEMBER=xxxxxxxxxxxxxxxxWITH SYNCHRONIZED TPIPES

ExplanationIMS received a client-bid request, but IMS has somesynchronized Tpipes that need to be resynchronizedwith the client.


System actionClient-bid request processing continues.

Programmer responseIf the client supports OTMA resynchronization, issuingthe CBresynch command is recommended.

ModuleDFSYMOM0

DFS2395I XCF MESSAGE EXIT HASUNEXPECTED RESPONSE

ExplanationThis message is issued when IMS unexpectedlyreceives a response message from the client.

System actionThe message is rejected.

Programmer responseTurn off the response bit (TMAMCRSP) in the messageprefix and resubmit the message.

ModuleDFSYMGX0

DFS2396I RESET SEQUENCE NUMBERFAILED DURING RESYNCH FORTMEMBER = xxxxxxxxxxxxxxxxTPIPE = xxxxxxxx

ExplanationThe IMS queue manager calls that were issuedto reset recoverable sequence numbers duringresynchronization failed.


System actionThe NACK X'0027' message is generated andresynchronization for the Tpipe is stopped.

Programmer responseContact IBM Software Support for assistance indetermining the problem.

ModuleDFSYQAB0

DFS2397E Error in writing record statistics todataspace.

ExplanationThe HALDB Migration Aid utility (DFSMAID0)encountered an error while writing statistics todataspace storage. The return code from the utilityindicates whether a failure occurred:Return code (hex)

Meaning00

Successful08

An error was encountered.

System actionThe utility processing terminates if an error occurred.

System programmer responseIf an error occurred, check the utility internal returncode. For information about the utility and its returncodes, see information about the HALDB Migration AidUtility (DFSMAID0).

Module:DFSMAID1

Related referenceHALDB Migration Aid utility (DFSMAID0)(Database Utilities)

DFS2398W OSAM SERVICES AREUNAVAILABLE

ExplanationThe parameter IOSCB=NO is specified on the OSAMOPstatement in a batch environment. This causesinitialization to bypass using the OSAM access method.

System actionProcessing continues without OSAM services. If OSAMservices are required, a subsequent OPEN data seterror results in an abend.

Programmer responseEnsure that the IOSCB=NO parameter is specifiedonly for those batch or CICS applications that do notrequire OSAM services.


http://www.ibm.com/support/knowledgecenter/SSEPH2_15.1.0/com.ibm.ims15.doc.dur/ims_dfsmaid0.htm#ims_dfsmaid0

http://www.ibm.com/support/knowledgecenter/SSEPH2_15.1.0/com.ibm.ims15.doc.dur/ims_dfsmaid0.htm#ims_dfsmaid0

DFS2399I JOB TERMINATED-RETURN CODEaa

ExplanationThe utility has terminated. aa is the return code.00 indicates only information (I) messages wereproduced; 12 indicates that one or more errors werefound and the program should be run again after theerrors are corrected.

System actionJob terminates.


DFS2400I ERROR WHILE ATTEMPTING TOFORMAT THE ccc...ccc

ExplanationDuring memory dump formatting, an error wasencountered while attempting to format a controlblock or data area. Field ccc...ccc, which can be up to16 bytes in length, identifies the control block or dataarea being formatted.

In an online environment, memory dump storage is inthe IMS memory dump Formatter.

Users of the memory dump formatter should be awarethat the original cause of the abnormal terminationof IMS might cause the memory dump formatter toprogram check.

Some of the common failures of the memory dumpformatter are:

• Invalid use of save areas and their linkages. Thememory dump formatter assumes that register 13always points to a save area. The forward andbackward pointers in the save area are valid. BALR14,15 is used as standard calling convention.

• Invalid IMS control block addresses. The memorydump formatter assumes that all addresses pointingto control blocks are valid. The memory dumpformatter does not validate addresses.

• Invalid IMS control block contents. The memorydump formatter assumes that all IMS control blockcontents are valid.

System actionFor most errors, a diagnostic memory dumpimmediately follows this message. This diagnosticmemory dump consists of the following:

• The contents of SDWA, which includes the PSW,completion code, module ID, registers, and amemory dump of the SDWA area.

• Instruction area, which includes 128 bytes of databefore and after the failing instruction (total of 256bytes).

• Communications area, which is the control blockused by the IMS memory dump Formatterfor intercommunication between the formattingmodules.

• Save area, which is a memory dump of the save areaset used by the memory dump formatter.

• The memory dump formatter module vector table.• Dump formatter storage buffer header and prefixes

(offline formatting only).• Dump option request block storage (offline

formatting only).

Following the diagnostic memory dump of the error,the memory dump formatter continues formatting thenext IMS control block requested.

A diagnostic memory dump is suppressed when any ofthe following forms of ccc...ccc is received:

'PSB' (and there is no DL/I storage in the memorydump)'AUTO OPTION PROC' (and debug was notrequested)'ABND DIAG. AREA''SA - EP ADDRESS''SAP''ECB PREFIX''SAVE AREA''REGISTER AREA''SA - INV FWD PTR''QUEUE BUFFERS''UEHB''LATCH LIST''ECB STORAGE''XMCI BLOCK''USE LIST (CULE)'

User responseDespite the failure of the IMS memory dumpFormatter, the output might still provide enoughinformation to help you diagnose your originalproblem. If the memory dump formatter output doesnot provide enough information, contact the IMSsystem programmer.


Programmer responseUse the diagnostic memory dump to determine thecause of the problem. If the diagnostic memory dumpis suppressed, contact the IMS system programmer.




DFS2401I UNABLE TO OPEN IMSUDUMPDATA SET

ExplanationThe STAE exit routine attempted to open the data setfor the Formatted Dump facility processing and wasunsuccessful.

System actionThe STAE exit routine continues with its processing;however, no formatted memory dump is provided.

Programmer responseMake sure that the IMSUDUMP DD statement wasspecified correctly.

DFS2402I jobname, stepname, unit addr,device type, ddname, op code, errordescription

ExplanationThe Formatted Dump facility attempted to write to theIMSUDUMP data set and an I/O error occurred.

System actionFormatted memory dump processing is discontinued.

Problem determinationDetermine the error condition from the message text.

DFS2403I DYNAMIC UNALLOCATE RC=rcERROR

or

DYNAMIC ALLOCATE INFORMATION CODE=xxxx

ExplanationIMS issued an ALLOCATE or UNALLOCATE commandfor a SYSABEND or SYSUDUMP data set. Either anonzero return code or a nonzero information codewas returned by SVC 99.

If RC=04, Error Code=0254 is returned by SVC 99, yourequested conditional ENQUEUE on a resource thatis currently unavailable. One reason for getting thisreturn and error code would be issuing an IMS MODIFYcommand while a mount for a log is pending.

System actionIMS continues execution (it might be in abnormaltermination processing).

Programmer responseContact the z/OS system programmer.


Related referencez/OS: Interpreting error reason codes fromDYNALLOCRelated information“IMS problem determination” on page 11IMS messages and codes problemdetermination is accomplished by usingprocedures established by IBM.

DFS2404A AN ERROR WAS ENCOUNTEREDWHEN ACCESSING THECOUPLING FACILITY STRUCTURExxxxxxxxxxxxxxxx RSN yyy

ExplanationA batch job encountered an error while attempting toaccess a coupling facility structure for structure namexxxxxxxxxxxxxxxx for a read and register operation or awrite operation.

The following list describes the reason codes andprovides recommended actions.

Code (hex) Meaning

238A loss of connection to the coupling facilityoccurred during a read and register operationwith no data transfer. See the system console foradditional connection error messages. Resolve thecoupling facility failure for the batch to continue.

239A coupling facility structure failure occurred duringa read and register operation with no data transfer.




See the system console for additional structurefailure messages. Resolve the coupling facilityfailure for the batch to continue.

241The read and register operation was purged withno data transfer. Determine why the connectorfailed. Resolve the coupling facility failure for thebatch to continue.

242The read and register operation failed for a reasonother than loss of connection, structure failure,and operation being purged with no data transfer.Resolve the coupling facility failure for the batch tocontinue.

243The structure was full during a read and registeroperation with a data transfer. See the systemconsole for additional error messages. Resolve thecoupling facility failure for the batch to continue.

244The read and register operation with data transferfailed for a reason other than the structure wasfull. See the system console for additional errormessages. Resolve the coupling facility failure forthe batch to continue.

245The structure was full during a write operation. Seethe system console for additional error messages.Resolve the coupling facility failure for the batch tocontinue.

246The write operation failed due to an environmentalerror for other reason than structure being full. Seethe system console for additional error messages.Resolve the coupling facility failure for the batch tocontinue.

247The cross invalidation operation failed due to anenvironment error. See the system console foradditional error messages. Resolve the couplingfacility failure for the batch to continue.

System actionThe batch application program waits for the couplingfacility to be available to continue processing. Thesystem log contains possible explanations of couplingfacility operation failure.

System programmer responseResolve the coupling facility failure for the batchapplication to continue processing.


Module:DFSDMAW0


DFS2406I THE HALDB PARTITIONSELECTION EXIT ROUTINE rnameFOR THE HALDB master name ISstatus

ExplanationIf the HALDB Partition Selection exit routine is notin storage and the HALDB partition DMB is allocatedsuccessfully, the status LOADED is displayed. If anexisting copy is found in storage and the HALDBpartition DMB is allocated successfully, the statusSHARED is displayed.

After IMS successfully deletes the exit routine, ifno more copies are in storage, the status GONE isdisplayed. Because the exit routine is re-entrant, acopy of it can remain in storage after it is deletedbecause it is still referenced by other databases. Inthis case, the status SHARED is displayed.

The following commands can load the partitionselection exit routine:

• /START DB HALDBpartition OPEN• UPDATE DB NAME(HALDBpartition)START(ACCESS) OPTION(OPEN)

The following commands can delete the partitionselection exit routine:

• UPDATE DB NAME(HALDBmaster) STOP(ACCESS)• UPDATE DB NAME(HALDBmaster) STOP(UPDATES)• /DBR DB HALDBmaster• /DBD DB HALDBmaster


Module:DFSPSM10

DFS2407W INVALID IMS OTMA OUTPUTPURGE AND REROUTE OPTIONSSPECIFIED

ExplanationIMS OTMA detected that both the CM0 output option,TMAMPCM0, and the CM0 output reroute option,


TMAMHRRQ, are specified in the OTMA messageprefix.

System actionNeither the CM0 output purge nor the CM0 outputreroute for the OTMA output message is performed.IMS OTMA take the default action to store the outputonto the asynchronous message hold queue of theinputting TPIPE.

Programmer responseHave the client of IMS OTMA examine the OTMAmessage prefix sent to IMS. Only one of theTMAMPCM0 or TMAMHRRQ options can be set in theOTMA state data prefix.

Module:DFSYPSI0, DFSYQAB0

DFS2408I UNABLE TO LOAD/LCT/FIX OSAMDRIVER/APPENDAGE OSAM INITFAILED FUNC REQ=xx R/C=yyyy

ExplanationThe OSAM I/O driver module (DFSAOS70) was notable to be loaded or located, or the entry point wasincorrect. For an explanation of the FUNC REQ=xx andR/C=yyyy values, see message DFS2411I.

System actionInitialization terminates with abend 0071 and register15 contains return code 8.

Programmer responseMake sure the DFSAOS70 module is in SDFSRESL withan entry point of DFSAOS70; then restart IMS.


Related information“DFS2411I” on page 693CANNOT OBTAIN IOB/IOSB-IOMA POOL-OSAMINIT FAILED FUNC REQ=xx R/C=yyyyIMS Abend 0071“IMS problem determination” on page 11IMS messages and codes problemdetermination is accomplished by usingprocedures established by IBM.

DFS2409I CANNOT OBTAIN FIX LISTS -OSAM INIT FAILED FUNC REQ=xxR/C=yyyy

ExplanationAn attempt to allocate storage for OSAM I/Oinitialization failed. For an explanation of FUNCREQ=xx and R/C=yyyy values, see message DFS2411I.

System actionInitialization is terminated with abend 0071. Register15 contains return code 12.

Programmer responseIncrease the IMS control region REGION size, andrestart IMS.

Related informationDFS2411ICANNOT OBTAIN IOB/IOSB-IOMA POOL-OSAMINIT FAILED FUNC REQ=xx R/C=yyyyIMS abend 0071

DFS2410I DATA TRANSLATION EXCEPTIONOCCURRED-OSAM INIT FAILEDFUNC REQ=xx R/C=yyyy

ExplanationAn attempt to translate fixed virtual storage addressesresulted in an error. For an explanation of FUNCREQ=xx R/C=yyyy values, see message DFS2411I.

System actionInitialization terminates with abend 0071. Register 15contains return code 16.


Related informationDFS2411ICANNOT OBTAIN IOB/IOSB-IOMA POOL-OSAMINIT FAILED FUNC REQ=xx R/C=yyyyIMS abend 0071“IMS problem determination” on page 11IMS messages and codes problemdetermination is accomplished by usingprocedures established by IBM.

DFS2411I CANNOT OBTAIN IOB/IOSB-IOMAPOOL-OSAM INIT FAILED FUNCREQ=xx R/C=yyyy

ExplanationAn attempt to allocate storage for the OSAM I/Opool was not successful. In an online environment,the storage is requested from CSA. In a batch





environment, the storage is requested from eitherCSA or private storage. FUNC REQ=xx and R/C=yyyycodes are described below. When R/C=yyyy is eitheran IMODULE or an IMSAUTH return code, see theIMODULE return code information for an explanationof these codes.xx

Description02

Unable to locate OSAM I/O module (DFSAOS70).R/C=yyyy is the IMODULE return code.

03Entry point of OSAM I/O module is invalid. R/C=4

04Unable to obtain storage. R/C=yyyy is theIMODULE return code.

05Unable to page fix OSAM I/O module (DFSAOS70).R/C=yyyy is the IMSAUTH return code.

06Unable to obtain storage for I/O pool. R/C=yyyy isthe IMODULE return code.

07Unable to release storage. R/C=yyyy is theIMODULE return code.

0AUnable to page fix I/O pool. R/C=yyyy is theIMSAUTH return code.

0BUnable to obtain storage for the key 7 QCB. R/C=yyyy is the IMODULE return code.

0CUnable to find the CBTE for the IOSB or OSWAblocks. R/C=yyyy is the DFSCBTS return code.

0DUnable to format the IPAGE. R/C=yyyy is the returncode from the DFSAOSF0 IOFORM routine.

17An attempt was made to obtain storage for aninvalid I/O pool.

System actionInitialization processing terminates with abend 0071,and IMODULE services places a return code in register15.

Operator response:Increase CSA size, if applicable.

Programmer response:Increase the region size; then restart IMS.



DFS2412I INSUFFICIENT STORAGE TOOBTAIN OSAM BUFFERINITIALIZATION WORK AREA-OSAM INITIALIZATION FAILED

ExplanationIMODULE GETMAIN failed for the work area space.Initialization of OSAM buffer pools cannot continue.


Operator response:Contact the system programmer.

Programmer responseEnsure that sufficient virtual storage exists so thatGETMAIN succeeds.



DFS2413I WARNING - OSAM SUBPOOLDEFINITION LIMIT HAS BEENEXCEEDED

ExplanationThe maximum number of OSAM subpools wasexceeded; 250 uniquely defined subpools are allowed.Any IOBF statements, found after the limit has beenreached, are ignored.

System actionThe initialization of IMS continues.

Programmer responseCombine or eliminate the OSAM subpool definitionstatements that exceed the limit.







DFS2414I WARNING-UNABLE TO FIX OSAMBUFFERS AS REQUESTED

ExplanationIMS was unable to page fix the buffers requestedbecause not enough read pages were available.

System actionIMS attempts to fix only the subpool headers andprefixes.


Programmer responseCheck allocation of pools.



DFS2415I WARNING-UNABLE TO FIX OSAMSUBPOOLS AS REQUESTED

ExplanationIMS was unable to fix the subpool headers andprefixes because not enough real pages wereavailable.

System actionNone of the subpool headers or prefixes are pagefixed.


Programmer responseCheck the pool allocation.



DFS2416I ENTRY POINT TO DFSDOBI0INVALID

ExplanationModule DFSDVBI0 called module DFSDOBI0 with aninvalid entry function code.

System actionOSAM initialization cannot continue so systemterminates abnormally.


Programmer response:This problem is an IMS system problem.



DFS2418 OUTPUT FROM NON-RECOVERABLE TRANSACTION(S)HAS BEEN DISCARDED

ExplanationModule DFSQFIX0 has removed one or moremessages from the message queues that weregenerated as output from transactions defined asunrecoverable.

System actionControl block changes resulting from the messageremoval have been written to the IMS log. Processingcontinues normally.

DFS2419A UNABLE TO ROUTE DL/I CALLTRACE OUTPUT TO IMS LOG

ExplanationAlthough log output for DL/I CALL TRACE wasspecified, the IMS log data set was not opened whenthe trace began.

Programmer responseEnsure that the DD statement defining the IMS logdata set is present and correct.

DFS2420I UNABLE TO OPEN FOR DDaaaaaaINSUFFICIENT STORAGE


ExplanationThe GETMAIN to permit the DL/I CALL TRACE routineto open for a sequential data set failed.

Programmer responseRerun the job with a larger region size.

DFS2421I UNABLE TO OPEN FORDDCARD=aaaaaa

ExplanationThe open for the DD statement specified in theDLITRACE control statement failed.

Programmer responseEnsure that the specified DD statement is present andcorrect.

DFS2422I DL/I TRACE TERMINATED-NOOUTPUT DATA SET PROVIDED

ExplanationAlthough DLITRACE was requested, no output devicewas provided or able to be opened.

System actionDL/I CALL TRACE is terminated, but the applicationprogram is not canceled.

Programmer responseRerun the job and ensure that the requested outputdevices are properly defined.

DFS2423I INVALID HEX CHARACTER ATOFFSET aa-DEFAULT VALUE USED

ExplanationAt the indicated offset, an invalid hexadecimal digitwas found for a numeric value.

System actionThe default value for the keyword is used andprocessing continues.

Programmer responseCorrect the control statement.

DFS2424I INVALID KEYWORD AT OFFSET aa

ExplanationAn invalid keyword was found in the DLITRACE controlstatement at the indicated offset.

System actionThe indicated keyword is bypassed and processingcontinues.

Programmer responseCorrect the DLITRACE control statement keyword.

DFS2425I INVALID SOURCE FOR SEGM-nnnnnnnn-IN DBD-nnnnnnnn-SOURCE DBD-nnnnnnnn

ExplanationA segment in a logical database specified a segmentin another logical database as its source. The messagespecifies the logical database containing the incorrectstatement, the segment name, and the incorrectsource logical database name.

System actionThe system issues abend 0986 if you were runningbatch DL/I. ACBGEN processing continues.

Programmer responseCorrect the DBD and rerun the job.

Problem determination:1, 2, 3, 5, 8, 11, 17a, 17d, 18, 19, 35


DFS2426I INDEX DBD-nnnnnnnn LCHILDFOR SEGM-nnnnnnnn IN DBD-nnnnnnnn SHOULD REFERENCE-nnnnnnnn

ExplanationThe Logical Child statement for the indicated segmentin the named index database specifies an incorrectsegment name for the indexed database segment.The segment name that should be referenced in thespecified indexed database is indicated.



System actionThe system issues abend 0987 if you are runningbatch DL/I. ACBGEN processing continues.




DFS2427I INDEX DBD-nnnnnnnn DOESNOT CONTAIN SEGM-nnnnnnnnREFERENCED BY LCHILDFOR SEGM-nnnnnnnn IN DBD-nnnnnnnn

ExplanationThe indicated index DBD does not contain thesegment specified. The index LCHILD statement forthe specified segment in the indexed DBD references asegment that does not exist.


Programmer responseCorrect the DBD and rerun the job.



DFS2428I THE INDEX DBD dbdname1 ISREFERENCED BY TWO INDEXEDSEGMENTS IN DBD dbdname2AND dbdname3

ExplanationIn resolving index relationships, one index wasreferenced by multiple indexed segment LCHILDstatements. This situation is not valid.


Programmer responseSpecify a UNIQUE index for each indexed segmentLCHILD statement.


DFS2429I SEGMENTS segname1 ANDsegname2 IN DBD dbdname AREACCESSED OUT OF HIERARCHICORDER IN THIS PSB

ExplanationThe order that sibling segments were referenced in alogical DBD or a PSB is in error. The sibling segmentdependents of a parent having PTR=HIER or in aHISAM DBD must be referenced in the same orderestablished in the physical DBD.

System actionThe system issues abend 0990 if batch DL/I was beingrun. ACBGEN processing continues.

Programmer responseCorrect the logical DBD or PSB, and rerun the job.


DFS2430I INVALID SOURCE=SPECIFICATION FOR SEGMENT-segname IN DBD-dbdname

ExplanationA logical child/destination parent concatenation hasbeen found to be invalid. The SOURCE= specificationimplies a logical relationship between the twosegments which does not exist. Possible reasons are:

1. The first segment referenced is not a logical childsegment

2. The second segment is not defined as the logicalparent of the first

3. The first is not defined as a logical child of thesecond segment.

4. The source segment for the named segment doesnot define a logical parent.







Programmer responseCorrect the SOURCE= specification or the physicalDBDs involved.


DFS2431I DBD1 dbdname1 REFERENCESDBD2 dbdname2 AS AN INDEXINVALIDLY

ExplanationA DBD was referenced in an LCHILD statement inanother DBD as an index DBD. The referenced DBDwas not coded as ACCESS=INDEX, and the reference istherefore invalid.


Programmer responseCorrect the DBDs, and rerun the job.


DFS2432I PSB-psbname-REFERENCESFIELD-fldname-IN SEGM-segname-IN DBD-dbdname. FIELDNOT FOUND

ExplanationAn invalid field name was referenced in a SENFLDstatement. The field name specified must be definedfor the segment during DBDGEN processing. Thesegment containing the intended field cannot bedefined as key-sensitive during logical DBDGEN.


Programmer responseCorrect the PSB, and rerun the job.


18, 19Related informationIMS abend 0993“IMS problem determination” on page 11IMS messages and codes problemdetermination is accomplished by usingprocedures established by IBM.

DFS2433I PSB-psbname-CONTAINSDESTRUCTIVE OVERLAP IN SEGM-segname-IN DBD-dbdname

ExplanationField mapping specified in PSBGEN caused adestructive overlap. Two or more fields were beingmoved to the same location.

System actionAbend 0994 is issued if batch DL/I was being run.ACBGEN processing continues.




DFS2434I SEGM-segname-IN DBD-dbdname-IN PSB-psbname-NOT SENSITIVETO KEY FIELD

ExplanationLoad or insert sensitivity was specified for the segmentin the PSB, but sensitivity to the sequence field wasnot specified.










DFS2435I FIELD SENSITIVITY INVALID FORLOGICAL CHILD WITH PROCOPT=Ior L; PSB-psbname-,PCB-dbdname-,SEGM-segname

ExplanationField level sensitivity was specified for the namedlogical child segment which has PROCOPT=I or L.




DFS2436I INTERNAL PROCESSING LIMITEXCEEDED FOR PSB=psbname,andPCB=pcbname

ExplanationThe required PSB control block cannot be builtbecause the logical relationships contained in thenamed PCB cause internal processing limits to beexceeded.


Programmer responseModify the PSB or DBDs, or both to reduce the numberof SENSEG statements in the PCB that referenceLOGICAL CHILD/LOGICAL PARENT concatenations.RE-EXECUTE PSBGEN, then RE-EXECUTE the job.




DFS2437I INVALID LOGICAL TWINSEQUENCE FIELD fieldname INDBD dbdname FOR LOGICALCHILD SEGMENT segment name INDBD dbdname

ExplanationThe referenced segment is virtually paired. The logicaltwin sequence field named cannot be contained withinthe real logical child segment named.


Programmer responseCorrect the DBD.



DFS2438W INVALID PROCOPT IN PCB FORDBD dbdname CHANGED TOEXCLUDE INSERT SENSITIVITY

ExplanationThis message indicates that an invalid processingoption was specified for any index database that wasbeing processed as a separate database. The BLOCKBUILDER module changes the PROCOPT to eliminateinsert sensitivity and continues processing.

System actionIMS continues processing with an altered processingoption in the PCB.

Programmer responseThe warning message can be avoided by changing theprocessing option to eliminate A or I. Check the PCB.

DFS2439W PROCOPT FOR SEGMENTsegname1 OF HSAM DBD dbdname






CHANGED TO ALLOW ONLY G, P, K,OR L PROCOPT

ExplanationThis message indicates that DL/I has revised thePROCOPTS specified in the PCB to conform with theallowable options for HSAM.

System actionProcessing continues normally after this message isissued.

Programmer responseRevise the PROCOPT options in the appropriate PCB orSENSEG statement for future runs.

DFS2440W INVALID PROCOPT FOR SEGMENTsegname IN DBD dbdnameCHANGED TO EXCLUDE DELETEAND INSERT SENSITIVITY

ExplanationWhen an alternate processing sequence is specified,the user cannot insert or delete the index targetsegment (alternate root segment) or any of its invertedparents. The processing option in the PCB or SENSEGstatement for one of these segments violates this ruleand the option has been changed in the SDB to reflectthe processing restriction.

System actionIf this message is issued because a PSB referencesa Fast Path secondary index, the ACB Maintenanceutility terminates with return code 8. The PSB in erroris identified by a DFS0587I message that follows thismessage. The PSB is deleted from the ACB library.

If the message is issued because a PSB referencesa full-function secondary index, the ACB Maintenanceutility sets return code 4 and continues processing theremaining input.

Programmer responseRevise the PCB to remove the insert or delete optionfrom the processing option field.

DFS2441W SYMB POINTER FROM L/C SEGM-segname IN DBD-dbdname TO L/PSEGM-segname IN DBD-dbdnameIS NON-UNIQUE

ExplanationThe logical child segment uses symbolic pointing tothe logical parent, but some segment on the path tothe logical parent has a missing, or it is not a uniquekey.

System actionProcessing continues, but problems can occur inaccessing the logical parent from the logical childsegment.

Programmer responseSpecify a unique key for each segment on the path to(and including) the logical parent segment, or specifylogical parent pointer for the logical child segment ifthe logical child/logical parent path is to be used.

DFS2442E DBFUCDB0 MSDB-TO-DEDBCONVERSION UTILITY ERROR,REASON CODE=nn

ExplanationAn error occurred while executing the MSDB-to-DEDBConversion utility. The reason code indicates the typeof failure that occurred:Code (dec)

Message subtext01

The TYPE= statement in the SYSIN stream ismissing or invalid.

02The database statement in the SYSIN stream ismissing or invalid.

03The MACBLIB indicates that the MSDB specified onthe input control statement is not an MSDB.

04The MSDB specified on the input control statementis not terminal-related without terminal-relatedkeys.

05The DACBLIB indicates that the DEDB specified onthe input control statement is not a DEDB.

06The MSDB= member specified was not found in theMACBLIB.

07The DEDB= member specified was not found in theDACBLIB.

08Error in loading randomizer module.


System actionThe utility terminates.

System programmer responseTake the following action to correct the errors.Code (dec)

Meaning or action01

The value specified for the TYPE= parameter is notCONVERT or FALLBACK or the TYPE= parameterwas not found on the first input statement readfrom SYSIN. Correct the input control statementsand rerun the job.

02The value specified for either the MSDB= or theDEDB= parameter has been coded incorrectly.Correct the input control statements and rerun thejob.

03The DMCB indicates that the database type of theMSDB= parameter is not MSDB. Either the incorrectACBLIB was specified or the MSDB name wasincorrect. Correct the input control statement andrerun the job.

04Only terminal-related MSDBs will be converted.All other types will be rejected. Correct the inputcontrol statement and rerun the job.

05The DMCB indicates that the database type of theDEDB= parameter is not DEDB. Either the incorrectACBLIB was specified or the DEDB name wasincorrect or not found. Correct the input controlstatement and rerun the job.

06The MSDB member specified was not found.Correct the input control statement and rerun thejob.

07The DEDB member specified was not found.Correct the input control statement and rerun thejob.

08The randomizer was not found in theIMS.SDFSRESL or an I/O error occurred whileloading the randomizing module. Verify therandomizer name and rerun the job.

ModuleDBFUCDB0

DFS2443I UNABLE TO OBTAIN VSO CONTROLBLOCK

ExplanationDuring area open or system initialization, a request fora VSO control block failed.

System actionThe data space is not obtained. IMS systeminitialization continues without VSO. Area open fails.

System programmer responseRe-submit job when ECSA use is lower. See messageDFS3702I.

ModuleDBFVIDS0

Related information“DFS3702I” on page 1057AREA/ADS OPEN FAILEDREASON CODE=nn message subtext

DFS2444I DSPSERV FAILED. RC=rc RSN =rrr

ExplanationA request for a new data space was issued but therequest failed. This situation can occur either duringIMS initialization or during area open.


The return code from the DSPSERV macrorrr

The rrrrrr reason code for the z/OS macroDSPSERV.

System actionThe data space is not acquired. IMS systeminitialization continues without VSO. Area open fails.This message is followed by either DFS2446I orDFS3702I (reason code 37).

System programmer responseCheck the return and reason codes for the DSPSERVmacro. If this message is issued during area open, seemessage DFS3702I.

Module:DBFVIDS0


Related referencez/OS: DSPSERV return and reason codesRelated information“DFS2446I” on page 702DATA SPACE NOT ACQUIRED. VIRTUALSTORAGE OPTION NOT ACTIVATED. rr“DFS3702I” on page 1057AREA/ADS OPEN FAILEDREASON CODE=nn message subtext

DFS2445I ALESERV FAILED. RC=nn.

ExplanationAuthorization to access a data space was requestedbut failed. This can occur either during IMSinitialization or during area open. The return code nnis the return code from the ALESERV macro.

System actionThe data space was not acquired. IMS systeminitialization continues without VSO. Area open fails.This is followed by either DFS2446I or DFS3702I(reason code 38).

System programmer responseSee the MVS/ESA System ProgrammingLibrary: Application Development Macro Reference(GC28-1822).

ModuleDBFVIDS0

DFS2446I DATA SPACE NOT ACQUIRED.VIRTUAL STORAGE OPTION NOTACTIVATED. rr

ExplanationAn error occurred while trying to obtain a data spaceduring control region initialization. rr is the reasoncode.Reason code

Description35

VSO control block failure; see message DFS2443I37

DSPSERV request for the data space failed; seemessage DFS2444I

38ALESERV request for the data space failed; seemessage DFS2445I

39VSO control block failure; see message DFS2443I

System actionControl region initialization completes without a dataspace's being acquired.

ModuleDBFINI20

DFS2447I AREA=aaaaaaaa UNABLE TOOBTAIN VSO CONTROL BLOCKRC=rc

ExplanationAn internal request for a VSO control block failed. Thiserror can occur during open of a VSO area or duringemergency restart log record processing of a VSO area.

System actionIf failure occurs during area open, open fails; messageDFS3702I is issued after this message. If failureoccurs during emergency restart and the area cannotbe restarted without the control block, the area isstopped and marked "recovery needed".

System programmer responseIf failure occurs during area open, rerun job when CSAuse is lower.

If failure occurs during emergency restart and the areais marked as "recovery needed", use the DatabaseRecovery utility to recover the Area.

ModuleDBFVSOP0

DFS2448I VSO AREA aaaaaaaa- ERESTORAGE REQUEST FAILED

ExplanationThis message is issued during local emergencyrestart, by an XRF alternate system during trackingor takeover, or by a Fast Database Recovery region ifthe system is unable to obtain storage that is neededto process log records for area aaaaaaaa, which isdefined as VSO. Emergency restart, the XRF alternatesystem, or the Fast Database Recovery region mightnot be able to recover the area after a failure withoutthe storage. If this occurs, the area is stopped andmarked "recovery needed".


http://www-01.ibm.com/support/knowledgecenter/SSLTBW_2.4.0/com.ibm.zos.v2r4.ieaa100/dspdesc.htm?lang=en

System actionRestart continues normally, except for area aaaaaaaa.If, at the end of restart log processing, the area hasCIs that require REDO processing (that is, updatedCIs that might not have been written to DASD prior tothe failure), the area is stopped and marked "recoveryneeded".

Operator responseIf the area becomes "recovery needed", use theDatabase Recovery utility.

ModuleDBFVSOP0

DFS2449I UNABLE TO SET UP EREDATA SPACE. REQ=cccccc RC=rcRSN=xxxx

ExplanationThis message is issued during local emergency restart,by the XRF alternate system during tracking ortakeover, or by the Fast Database Recovery region ifthe system is unable to obtain or set up the data spacethat is needed to process log records for VSO areas.

In the message text:cccccc

Is one of the following values:AUTH

The request for authorization of the new dataspace failed.

CBLKA request for storage for a control block failed.

CREATEThe request for the creation of a new dataspace failed.

PAGEFIXThe request to PAGEFIX storage in the VSOERE DATASPACE received a DSPSERV failure.

rcThe return code from the request.

xxxxThe hexadecimal reason code displays if theCREATE or PAGEFIX command receives aDSPSERV macro error. These codes are defined bythe DSPSERV macro.

System actionRestart continues. At the end of restart log processing,any areas that have control intervals (CI) that require

REDO processing (that is, updated CIs that might nothave been written to DASD before the failure) arestopped and marked recovery needed.

Operator responseIf the area is marked recovery needed, use theDatabase Recovery utility.

Module:DBFNRST0

Related referencez/OS: DSPSERV - Create, delete, and controldata spacesz/OS: DSPSERV return and reason codes

DFS2450I UNABLE TO ACQUIRE STORAGEFOR ENQ/DEQ BLOCKS,REASON=n

ExplanationModule DFSFXC10 was unable to acquire a block ofstorage for queuing control blocks. The reason codes nprovide further details:Code (dec)

Meaning0

A block was requested that is not the first block.The amount of storage that was specified bythe PIMAX parameter has not been exhausted,but a GETMAIN for another block of storagewas unsuccessful. If the failure was on anattempt to acquire the last block, this message isaccompanied by message DFS2451W.

8There is no storage available for the first ENQ/DEQblock. A standard abend occurs.

System actionIf the request was for the first block, the system isterminated abnormally with abend 0775. For otherblocks, the task is pseudoabended with abend 0775.

System programmer responseCode

Response0 & 8

IMS LSO=NIncrease CSA size

IMS LSO=Y or XIncrease control region local storage size


http://www-01.ibm.com/support/knowledgecenter/SSLTBW_2.4.0/com.ibm.zos.v2r4.ieaa100/datahd.htm?lang=en

http://www-01.ibm.com/support/knowledgecenter/SSLTBW_2.4.0/com.ibm.zos.v2r4.ieaa100/datahd.htm?lang=en

http://www-01.ibm.com/support/knowledgecenter/SSLTBW_2.4.0/com.ibm.zos.v2r4.ieaa100/dspdesc.htm?lang=en

IMS LSO=SIf your system is using Fast Path, increase theECSA size. If the system is not using Fast Path,then increase the DLI/SAS region local storagesize.

If there are one or more BMPs that have updatesrunning at the time of the failure, then have the BMPsissue checkpoints. Alternatively, if they already do,have them issue the checkpoints more frequently.

Related information“DFS2451W” on page 705THE LAST BLOCK OF ENQ/DEQ STORAGE ISBEING ACQUIREDIMS abend 0775





DFS2451W THE LAST BLOCK OF ENQ/DEQSTORAGE IS BEING ACQUIRED

ExplanationThe last allowable block of storage, as specified onthe PIMAX parameter in member DFSPBIMS in aDB/DC environment, or in member DFSPBDBC in aDBCTL environment, is being obtained. If the ENQ/DEQstorage requirements result in another block beingrequested, the task is terminated with a pseudoabend.


Programmer responseReevaluate the activity requiring ENQ/DEQ storage toensure that critical applications are not terminatedbecause of a lack of ENQ/DEQ storage.

DFS2452I AREA aaaaaaaa IS TOO LARGEFOR VSO

ExplanationThe Virtual Storage Option (VSO) was requested forarea aaaaaaaa, but the area exceeds the maximumsize allowed for VSO. The maximum allowable size is 2gigabytes (2 147 483 648 bytes), minus some storageused by z/OS and IMS.

The amount of space needed for an area in a dataspace is (rounded to the next 4 KB):

(CI size) × (number of CIs per UOW) × ((number of UOWs in the root addressable portion) + (number of UOWs in the independent overflow portion))

Expressed in terms of the parameters of the DBDGENAREA statement, this is (rounded to the next 4 KB):

(the value of the SIZE= parameter)× (the value of the UOW=number1 parameter) × (the value of the ROOT=number2 parameter)

The actual amount of space in a data space availablefor an area (or areas) is 2 gigabytes (524,288 blocks,4 KB each) minus an amount reserved by z/OS (from0 to 4 KB) minus an amount used by IMS Fast Path(approximately 100 KB). You can use the /DISPLAY

FPV command to determine the actual storage usageof a particular area.

System actionThe area is opened as DASD mode.

Module:DBFVSOP0

DFS2453A DATASPACE UOW CANNOT BEPINNED FOR I/O

ExplanationFast Path has begun the process of loading an areawhich is defined with the VSO and PRELOAD options,into a data space. An error occurred while attemptingto page fix storage in the data space.

System actionThe preload process terminates without finishing thepreload process.

Operator responseThis problem is a possible real storage shortageproblem. After real storage problem is resolved,issue the /START AREA or UPDATE AREASTART(ACCESS) command to initiate the preloadprocess.

Module:DBFVSPL0

DFS2453I PRELOAD PROCESSING xxxxxxxxFOR aaaaaaa STR1=strname1;STR2=strname2

or

PRELOAD PROCESSING STARTED FOR: aaaaaaaa

or

PRELOAD PROCESSING COMPLETED FOR:aaaaaaaa


or

PRELOAD PROCESSING ABORTED, UTILITY ACTIVE:aaaaaaaa

or

IMAGE COPY ITASK STARTED|COMPLETED|ABORTED FOR: aaaaaaaa

or

IMAGE COPY ITASK ABORTED FOR: aaaaaaaa[IMSSHUTDOWN | IMAGE COPY ERR | ABORT AT INIT]

ExplanationFast Path started or completed the process of loadingarea aaaaaaaa, which is defined with the VSO andPRELOAD options, into a data space.

For the third form of this message, PRELOADPROCESSING ABORTED, UTILITY ACTIVE:aaaaaaaa, following a /START AREA command forarea aaaaaaaa, which is defined as VSO and PRELOAD,Fast Path was unable to begin loading the area into adata space because HSSP or a utility is currently activeon the area.

For the fourth form of this message, IMAGECOPY ITASK STARTED|COMPLETED|ABORTED FOR:aaaaaaaa, either HSSP or another processdynamically created the image copy ITASK for areaaaaaaaaa. The image copy ITASK issues this messagewhen it starts, completes, or aborts.

For the IMAGE COPY ITASK ABORTED form of themessage, one of the following strings is appended:

• IMS SHUTDOWN means IMS is being shut down.• IMAGE COPY ERR means that an error occurred

during image copy that caused the termination of theimage copy and the ITASK.

• ABORT AT INIT means that an error occurredduring the initialization of the image copy dataset, and image copy is not possible. See messageDFS0531I or the relevant DBRC messages.

The sixth form of the message reports the status ofpreload processing for area aaaaaaa. Status xxxxxxxxcan be STARTED, ABORTED, or COMPLETED. STR1 andSTR2 are the z/OS cross-systems extended services(XES) structure names.


For the third form of this message, the preload processis aborted.

For the fourth and sixth forms of this message, theaction indicated was taken.

Operator responseFor the third form of this message, reissue the /STARTAREA or UPDATE AREA START(ACCESS) commandwhen HSSP or the utility has completed.

For the fourth form of this message, no action isrequired.

For the sixth form of the message, if the preloadprocess for an area aborted, correct the reason forthe failure. Then issue a /START AREA or UPDATEAREA START(ACCESS) command to start the preloadprocess again.

Module:DBFVSPL0, DBFPTIC0, DBFVXPL0

Related information“DFS0531I” on page 183IMAGE COPY DATASET OPEN FAILED

DFS2454I PRELOAD SEVERE ERROR FOR:aaaaaaaa RC=rc

ExplanationFast Path has begun the process of loading an area,which is defined with the VSO and PRELOAD options,into a data space. The return code rc indicates thereason for the error message.PIN

an error while attempting to page fix storage in thedata space

LOCKan error has occurred in trying to obtain a UOWlock

SHTDan IMS shut down

System actionThe preload process terminates without completing.

Operator responseA possible real storage shortage problem hasoccurred. After the real storage problem isresolved, issue the /START AREA or UPDATE AREA


START(ACCESS) command to have the preloadprocess initiate.

Module:DBFVSPL0

DFS2455A CANNOT RUN COMPARE UTILITYFOR AREA IN VIRTUAL STORAGE,AREA=aaaaaaaa

ExplanationThe DEDB ADS Compare utility was requested for anarea that is currently in virtual storage.

System actionThe utility request fails with return code 12 andmessage DFS2662A is issued.

Operator responseIssue the /VUNLOAD command to remove the areafrom virtual storage and resubmit the utility job. Thearea can be returned to virtual storage after theutility has completed by issuing the /START AREA orUPDATE AREA START(ACCESS) command.

Module:DBFUMRT0

DFS2456I AREA aaaaaaaa UNEXPECTEDPOINTER VALUE DURING VSOCLOSE

ExplanationA non-catastrophic internal logic error has occurred.During close of VSO area aaaaaaaa, a control blockwas found to contain a bad pointer value and itwas necessary to bypass the code that would havedeallocated the portion of a data space that wasallocated for the area. Bypassing the deallocationis not a problem for data integrity. It is possible,however, that part of a data space might be unusableuntil the next restart. If the data space deallocationis skipped, the /DIS FPV command might show thearea as being in a data space even after it is closed.

System actionArea close processing is allowed to continue.

Operator responseCall IBM Software Support.

Module:DBFVSCL0

DFS2457I DUE TO A STORAGE SHORTAGE,NOT ALL AREAS WILL BEPREOPENED OR PRELOADED,RETRY LATER

ExplanationDuring preopen or preload setup, there was a storageshortage and the preopen or preload processing wasnot attempted.

System actionIMS system continues processing without preload orpreopen.

Operator responseIdentify those areas that were not preopened orpreloaded by issuing a /DIS FPV command. Issue /START AREA or UPDATE AREA START(ACCESS)command when system storage becomes available.Message DFS2446I follows this message for IMSsystem initialization.

Module:DBFVTSK0

DFS2458A VSO AREA aaaaaaaa- ERE SEVEREERROR

ExplanationAn internal error occurred during emergency restart,XRF takeover, or the recovery phase of Fast DatabaseRecovery for area aaaaaaaa, which is defined as aVirtual Storage Option (VSO) area.

In addition to this message, some diagnosticinformation is output. Although this error does notabend IMS, the information has the same format asoutput from abend 1026.

This message, and the accompanying diagnosticinformation, is issued a maximum of three times.Message DFS2485I is issued at the end of emergencyrestart and shows the total number of times the errorcondition was detected.

System actionArea aaaaaaaa is stopped and marked "recoveryneeded".

Operator responseUse the Database Recovery utility to recover the area.

Module:DBFERS21



DFS2459I DUE TO A STORAGE SHORTAGE,PARDLI WILL NOT BE IN EFFECTFOR THIS REGION.

ExplanationDuring PARDLI setup processing, there was a storageshortage and the PARDLI option was not activated forthis region.

System actionIMS system continues processing without PARDLI.

System programmer responseIncrease the region size on the job and rerun.

DFS2460 ONLY ONE PSB NAME ALLOWED

ExplanationMore than one name was entered following PSBkeyword.


Operator response(local/remote terminal) Reenter the command withonly one PSB name.

Module:DFSICLN0

DFS2461 INVALID ENTRY FLAG-CALL NOTTRACED

ExplanationOn entry, the DL/I CALL TRACE routine could notdetermine if this was a trace or compare pass.


DFS2462 START VALUE EXCEEDS STOPVALUE-STOP DEFAULT USED

ExplanationThe start value in the DLITRACE control statement isgreater than the stop value. The default stop value isused.

Programmer responseCorrect the indicated value.

DFS2463 NEGATIVE VALUE ON INPUT ATOFFSET aa

ExplanationThe value at the indicated offset is a negative value.

System actionThe default value for the parameter is used andprocessing continues.

Programmer responseCorrect the indicated parameter.

DFS2464 OUTPUT ERROR, DL/I CALL TRACEIS TERMINATED

ExplanationWhile attempting to write a record, an I/O error wasencountered.

System actionIf output was routed to a sequential data set, thedata set is closed and the trace is terminated. Theapplication program is allowed to run to normalcompletion.

Programmer responseRerun the job.

DFS2466I AUTHORIZATION RACLISTFAILED, RACROUTE = aa, bb,cc, dd RACLIST = ee, ff, gg,hh REASON = ii , jj , kk ,ll. RACROUTE REQUEST=LISTFAILED, CLASS=xxxx, RC=xx. RACFOR ROUTER EXIT RC=xx, REASONCODE=xx.

ExplanationFor the first form of the message, a nonzero returncode was found, during initialization processing, forat least one of the four classes associated withthe authorization function. The variables have thefollowing meanings:aa

RACROUTE return code for DATABASE class.bb

RACROUTE return code for SEGMENT class.



ccRACROUTE return code for FIELD class.

ddRACROUTE return code for OTHER class.

eeRACLIST return code for DATABASE class.

ffRACLIST return code for SEGMENT class.

ggRACLIST return code for FIELD class.

hhRACLIST return code for OTHER class.

iiRACLIST reason code for DATABASE class.

jjRACLIST reason code for SEGMENT class.

kkRACLIST reason code for FIELD class.

llRACLIST reason code for OTHER class.

The second form of this message is produced whenIMS is attempting to build in-storage profiles forRACF defined resources, and a failure occurs in theRACROUTE, RACLIST, or ROUTER EXIT processing. Theclass of the failing resource is specified, and the returncode from the RACROUTE routine is also given. Thereturn code and reason code (if applicable) from RACFor the ROUTER EXIT is also given.

System actionWith the first form of the message, IMS restartcontinues.

With the second form of the message, IMS restartcontinues, and the RACF authorization function fortransactions, commands, PSBs, or LTERMS is disabled.

Operator response:With the second form of the message, see the MVS/XASPL Macros and Facilities Manual Volume 2 for adetailed description of the return codes and the reasoncode from the RACROUTE, RACLIST, and ROUTER EXITroutines.

DFS2466W RACROUTE REQUEST=LISTFAILED, CLASS=xxxxxxxx, RC=xx.RACF OR ROUTER EXIT RC=xx,REASON CODE=xx.

ExplanationA failure occurred in RACROUTE, RACLIST, or ROUTERexit processing while IMS was trying to build in-storage profiles for RACF-defined resources. Themessage displays:

• The class of the failing resource• The return code from the RACROUTE macro• The return and reason codes from the RACF or

ROUTER exit, if applicable.

System actionIMS restart continues. The RACF transactionauthorization function is disabled.

With the second form of the message, IMS restartcontinues, and the RACF authorization function fortransactions, commands, PSBs, or LTERMs is disabled.

Operator response:(master terminal) See z/OS MVS Programming:Authorized Assembler Services Guide for a detaileddescription of the return codes and reason codes forRACROUTE, RACLIST, and ROUTER exit processing.

DFS2467I /SIGN COMMAND REJECTED[reason]

Explanation/SIGN command rejected due to indicated reason. Seethe explanation of message DFS3649A for the possiblereason codes and their meanings.


Operator responseReenter command correctly based upon the indicatedreason.

Related information“DFS3649A” on page 1036/SIGN COMMAND REQUIRED.

DFS2469W TRANSACTION REJECTED reason

ExplanationThis message is sent to the terminal enteringa transaction when RACF determines that thetransaction failed security checking. The reasons forthe transaction rejection are:TRANS NOT AUTH; RC=08

User is not authorized to this transaction code byRACF.

SIGNON REQUIREDTransaction is RACF-protected and the user is notsigned on.

RACF NOT ACTIVE; RC=12


BY RACF EXIT; RC=16RACF exit gave an invalid return code.

INSTALL ERROR; RC=20RACF is not installed or an incorrect level of RACFis installed.

RACF POE ERROR; RC=24The RACF profile has a conditional access list, theport-of-entry field in the security token is filled byblanks, and the port-of-entry class is active.

RACF DS DELETED; RC=28The resource class was selected by RACROUTEREQUEST=LIST GLOBAL=YES, but the RACF dataspace was deleted.

NO PASSWORD; RC=36User verification required; no password supplied.

WRONG PASSWORD; RC=40User verification failed password.

USERID REVOKED; RC=44User verification failed because the user ID wasrevoked.

Note: RC = represents a decimal value.

Additional codes can be supplied by a user-writtenIMS exit routine.

System actionThe transaction entered is ignored.

Operator response:Reenter the transaction with the proper password,or enter another transaction that does not violatesecurity.



ModuleDFSCIOB0, DFSICIO0, DFSICLE0

DFS2470 /SIGN COMMAND REQUIRED

ExplanationThis message is sent to the terminal entering atransaction or /RELEASE command when no previousvalid sign-on has been done.

System actionThe transaction or /RELEASE command is ignored.

Operator response(local/remote terminal operator) Enter a valid sign-on, and then enter the transaction or /RELEASEcommand.


DFS2471 DUPLICATE CONTROL CARD ORKEYWORD FOR DLITRACE

ExplanationWhile processing the DLITRACE control statement,one of the following conditions occurred:

• More than one DLITRACE control statement in theinput stream.

• A keyword was used more than once in the controlstatement.

System action• The DL/I CALL TRACE options used were the ones

set by the first DLITRACE control statement in theinput stream.

• The value specified by the first keyword encounteredis the one set for DL/I CALL TRACE. Subsequent useof the keyword is overlooked.

Programmer responseEnsure that the DL/I CALL TRACE options usedwere the correct options, and ensure that duplicateparameters are removed.

DFS2472 INVALID AWE DETECTED ANDLOGGED

ExplanationAn invalid asynchronous work element (AWE) wasdetected by the processing IMS module. An invalidelement might mean conflicting parameters, missingaddresses, or a number of other things. It is entirelydependent upon the requirements for the processor.This message is accompanied by an X'67' FB logrecord on the IMS log data set. The log recordindicates which of the processors detected the invalidAWE. This message indicates a possible IMS or exitroutine logic error.

System actionThis message is issued and the X'67' FB log recordcontaining the invalid AWE and optional processorwork areas are logged. The log record is intended fordebug purposes.


Operator responseNotify the system programmer about the receipt of thismessage.

Programmer responseSave the log record information for debug.



DFS2473I ERROR; RPLREQ=xx, R0=xx,R15=xx,NODE nodename,CLSDSTSCHED

ExplanationOne of the following conditions exists:

1. IMS issued the VTAM EXECRPL macro and receivedan unrecognized return code from VTAM

2. A VTAM request (using EXECRPL) failed 25 timesbecause VTAM is short on storage. IMS attempts toCLSDST the node. R0 is X'08' and R15 is X'04'.

3. VTAM rejects the SEND request (RPLREQ= 22)because the session has already terminated. R0is X'14' and R15 is X'04'. This message is issuedinstead of DFS970I when VTAM drives NSEXIT orLOSTERM after IMS has started output messageprocessing.

RPLREQ code and the other codes are in hexadecimal.

System actionThe node is either closed or deactivated. If the nodeis deactivated, DFS2101I is displayed at the masterterminal. An IMS log record (X'67') with an ID of AER2containing pertinent information was produced.

Programmer responseThe contents of the message aid in determining whichof the problem conditions has occurred.


Related information“DFS970I” on page 348(UNEXPECTED STATUS| OPNDST/OPNSESSFAILED| CLSDST/TRMSESS FAILED| GENCB/MODCB ERROR| FORCED CLEANUP DONE|SESSION FAILURE), NODE node name, USER/

user name| N/A, (UNDEFN | SETLOG | SIMLOG| OPNDST | OPNSEC | CLSDST | SEND|RECEIV| TRMSES | RQR | RESTSR | INQUIR|SESSNC| ******), RC=,FDB2=, LOSTERM=|NSEXIT=|UNBIND=, SENSE=, REASON=“DFS2101I” on page 617DEACTIVATING NODE xxxxxxxx.“IMS problem determination” on page 11IMS messages and codes problemdetermination is accomplished by usingprocedures established by IBM.

DFS2474I RECEIVE ANYS EXHAUSTED, REG0=xx, CLOSING VTAM ACB

ExplanationIMS cannot receive data from the network due toVTAM being short on storage. Every issuance of theVTAM RECEIVE macro has resulted in the short onstorage return code.

System actionSince IMS can no longer communicate with its VTAMnetwork, it causes an orderly shutdown of the VTAMnetwork.

Operator response:(master terminal) Restart the VTAM network withthe /START DC command.

Programmer responseIncrease the size of the appropriate VTAM buffer pool.

Problem determinationDetermine the VTAM buffer pool that is running shorton storage, and enlarge it.

DFS2475 /STOP DC COMMAND INPROGRESS, CANNOT PROCESSCOMMAND

ExplanationA /START DC command is not allowed if a previous /STOP DC command has not yet completed.


Operator response:(master terminal) Use the /DISPLAY ACTIVEcommand to determine the state of the VTAM network.Reenter the command when the VTAM ACB is closed.


DFS2476 EXTENDED SECURITY FUNCTIONNOT ALREADY DEFINED

ExplanationThe USER, TRANAUTH, CMDAUTH, or CMDAUTHEkeyword is invalid in the /NRE or /ERE COLDSYScommand when the system definition and EXECparameters did not request any extended security.

Extended security can be specified by the initializationEXEC parameter RCF=A | Y | T | C | S.

System actionThe command is ignored. IMS waits for another restartcommand.

Operator response:(master terminal) Re-enter the command properly.Notify your IMS programmer for assistance.

DFS2477 /RCL COMMAND REJECTED-TERMINAL IN CONVERSATION

ExplanationThe /RCL command was rejected. The terminal fromwhich the /RCL command was entered is currently inan active conversation.


Programmer responseEnter /EXIT to terminate the conversation, or HOLD tohold the conversation across a sign-off; then reenterthe /RCL command.

DFS2478I MIGRATED RESOURCE xxxxxxxxHAS BEEN RECALLED

ExplanationA recall for either database name or area name, asdesignated by xxxxxxxx, has finished.

System actionThe system issues an internal /START DB or /STARTAREA command to allocate the resource.

DFS2479W ISAM ACCESS METHOD ISNO LONGER SUPPORTED. DBD-dbdname MUST BE CORRECTEDFOR IT TO BE USABLE

ExplanationThe database listed in this message requires the ISAMaccess method for processing. ISAM is unavailableunder IMS Version 10 or later


Programmer responseConvert the database to a valid access method.

DFS2480I BATCH DYNAMIC ALLOCATIONDISABLED

ExplanationIMS detected a card image in the DFSVSAMP dataset with the character string NODYNALLOC. This cardimage disables dynamic allocation in batch IMS.

This job does not allow any databases to participate indynamic allocation. References to these databases failunless DD card images have been included in the jobstep.

Programmer responseIf you do not want dynamic allocation, no action isrequired. If you want dynamic allocation, delete theNODYNALLOC control card image in the DFSVSAMPdata set and rerun the job.

DFS2481I DATA BASE RECOVERY CONTROLFEATURE NOT OPERABLE

ExplanationThe BLDL macro encountered an error while locatingthe module required to access the Database RecoveryControl Feature.


Operator responseContact your IMS system programmer for assistance.If the Database Recovery Control Feature has beeninstalled, determine the cause of the locate error. Youmight need to enter database log data set or utilityinformation into the RECON data set since it was notaccessible.




DFS2482I DBRC LOG xxxx EXIT FAILED (yy)

ExplanationA DBRC request submitted by the IMS logger wasunsuccessful. The specific type of DBRC exit invokedis indicated by xxxx. xxxx can be one of the followingvalues:

OPENCLOSESWITCHSTATUSARCHIVEEOVSYNADLOGREC

When xxxx indicates EOV or SYNAD, either a returncode of X'00' or X'04' indicates that it was successful,or a return code of X'12' indicates that it wasunsuccessful.

The DBRC return code is displayed as yy (hexadecimal)in the message. See the DBRC request return codeinformation.

When xxxx indicates OPEN and yy indicates RC(4),and you are trying to cold start an IMS systemthat previously failed, the correct procedure is todo an emergency restart of IMS. If you are coldstarting IMS because of an emergency restart failure,you must close the log stream of the previous IMSinstances and clean up the subsystem record by usingthe NOTIFY.PRILOG and CHANGE.SUBSYS commands.Also ensure that you have completed necessary stepssuch as batch backout for full-function databases, andsome method of forward recovery for Fast Path DEDBs,before you cold start IMS. (However, if FDBR wasactive when IMS abended, and successfully completedrecovery processing, batch backout and DEDB forwardrecovery are not necessary.)

Message DFS4168I is an indication that FDBRsuccessfully completed recovery processing. IfDFS0693I messages are received during FDBRrecovery processing, indicating that resolve indoubtstructures were built for in-doubt units of work, coldstart is possible but you must manually resolve the in-doubt units of work using commands from the commitcoordinator side (for example, CICS or RRS).

For ESS processing such as DB2® or IBM MQ,IMS is the commit coordinator and you will notnormally receive messages from FDBR indicatingan in-doubt condition. IMS provides a sample exit,DFSFIDN0, which will issue a DFS3722I message withrecommended recovery actions for each in-doubt ESSunit of work. The in-doubt UOWs will also be visiblefrom the ESS participant subsystem, and in the eventof IMS cold start, must be resolved using appropriateparticipant subsystem commands.

IMS might build Extended Error Queue Elements(EEQEs) and register them with DBRC during FDBRrecovery processing of in-doubt units of work. TheseEEQEs protect the in-doubt IMS database resourcesfrom being accessed by other data-sharing IMSsubsystems. If IMS is cold started, in-doubt EEQEswill require manual processing. For DEDBs, it is safeto delete such EEQEs using DBRC commands becauseDEDBs are never updated before commit processing.For full-function databases, you might need to performdatabase recovery on the databases that have in-doubt EEQEs.

System actionWhen the ARCHIVE exit fails, IMS issues this messageand continues execution. An error return code fromany of the other DBRC exits results in IMS issuingabend 0071.

Programmer responseAn analysis is required to determine the reason forthe DBRC exit failure. See the z/OS master console(SYSLOG) for DSP messages that might explain thecause of the condition.

If this problem is an archive exit failure, determine ifan emergency restart (/ERE) was issued after a normalIMS shutdown. If it was, the automatic archive jobsubmitted by the emergency restart processing willfail, and you can ignore this message.


Related referenceDBRC request return codes (Messages andCodes)Related informationIMS abend 0071“IMS problem determination” on page 11IMS messages and codes problemdetermination is accomplished by usingprocedures established by IBM.

DFS2483A DBRC INITIALIZATION ERROR






ExplanationAn INIT call was made to the database recoverycontrol (DBRC) module DSPFLT00. The return codewas 12, indicating a serious error condition in the exit.

System actionThe IMS control region terminates abnormally.

DFS2484I JOBNAME=nnnnnnnn GENERATEDBY LOG AUTOMATIC ARCHIVING

ExplanationAutomatic log archiving is active. DBRC has generateda JCL for an execution of the Log Archive utility.nnnnnnnn is the name of the job generated by DBRC.


Operator responseIf the log archive job is to run concurrently with theonline IMS system, ensure that a z/OS initiator isavailable to process the log archive job.

DFS2485I FP ERE TOTAL ALTERATIONCOUNT ERRORS = n

ExplanationThis message is preceded by one to three instancesof message DFS2458A and shows the total number nof times the error condition described in DFS2458Aoccurred.

System actionNone.


Module:DBFERST0

Related information“DFS2458A” on page 707VSO AREA aaaaaaaa- ERE SEVERE ERROR

DFS2486I FP ERE TOTAL VSO LOG ERRORS =n

ExplanationThis message is preceded by one to three instancesof message DFS2489I and shows the total number nof times the error condition described in DFS2458Aoccurred.

System actionNone.


Module:DBFERST0

Related information“DFS2458A” on page 707VSO AREA aaaaaaaa- ERE SEVERE ERROR“DFS2489I” on page 715ERE VSO LOG RECORD ERROR

DFS2487I UNABLE TO COMPLETE REDODURING XRF TKO - AREAaaaaaaaa- RSN cccc

ExplanationDuring XRF takeover, DEDB REDO processing includesthe following:

• Refreshing the second CI for all block-level sharedareas to pick up the changes from the sharingsubsystem that might not have been sent to therestarting subsystem.

• Notifying the sharing subsystem if utility or HSSPcleanup was done during takeover.

This message indicates that REDO processing wasunable to perform these tasks for area aaaaaaaa. ccccidentifies the reason and can be one of the followingvalues:ER2L

REDO was unable to obtain the lock needed.ER2R

REDO was unable to refresh successfully thesecond CI.

ER2UREDO was unable to notify successfully the sharingsubsystem that utility or HSSP cleanup was doneduring takeover. This condition can be caused byeither an I/O error or by a problem with the notifyprocess.

At the time this message is issued, area aaaaaaaahas successfully completed all other REDO processing.The problem indicated in the message might be


resolved by closing the area and allowing it to gothrough normal area open processing when it is nextaccessed. Therefore, it is not necessary to mark thearea as "recovery needed" and, except in the case of anotify error, it is not necessary to prohibit the sharingsubsystem from accessing the area.

System actionIf an error occurred while notifying a sharingsubsystem, the sharing subsystem is notified tostop the area. The area is closed on the restartingsubsystem and message DFS3705I is issued. If theerror recurs when the area is next opened, the area isstopped and marked "recovery needed".

System programmer responseIf REDO processing was unable to complete utilityor HSSP cleanup, the area must be reopened onthe restarting subsystem (or stopped, started andreopened on the sharing subsystem) before a utilityor HSSP can be started for the area.

Module:DBFERS20

Related information“DFS3705I” on page 1061AREA=areaname DD=ddname CLOSED

DFS2488A VSO AREA aaaaaaaa- ERE SEVEREERROR

ExplanationRestart log processing was unable to obtain storagenecessary to track updates made to area aaaaaaaa,which is defined as a Virtual Storage Option (VSO)area.

System actionArea aaaaaaaa is stopped and marked "recoveryneeded".

System programmer responseUse the Database Recovery utility to recover the area.

Module:DBFERSY1

DFS2489I ERE VSO LOG RECORD ERROR

ExplanationRestart log processing encountered a VSO DEDB arealog record that did not match any area known tothe restarting system. This problem happens during

emergency restart, XRF tracking, XRF takeover, or FastDatabase Recovery processing,

The log record should contain the VSO DEDB areaname and a time stamp. The presence of thelog record signifies that area updates, which werecommitted before the logged time, were written toDASD before failure. Based on this log record, restartlog processing can ignore updates that were writtento DASD, but without a valid area name it cannotdetermine which updates to ignore and which toprocess.

In most cases restart can tolerate this error, althoughperformance might be degraded. A subsequent logrecord might correct the problem (that is, might showwhich updates were written to DASD for the area),otherwise restart does additional REDO processing.

If this problem recurs, IMS restart can run out ofresources to track VSO area updates. If this happens,any affected areas are stopped and marked "recoveryneeded".

In addition to this message, some diagnosticinformation is output. Although this error does notterminate IMS, the information has the same formatas output from abend 1026.

This message and the accompanying diagnosticinformation are issued a maximum of three times.Message DFS2686I is issued at the end of emergencyrestart and shows the total number of times the errorcondition was detected.

System actionRestart continues.

System programmer responseDuring local emergency restart of XRF takeover, noaction is required. If the problem occurs during XRFtracking, restart the XRF alternate to relieve resourceshortage and performance degradation.

Problem determination1, 5, 11, and a memory dump of the restarted systemafter restart finishes.

Module:DBFERSY0

Related information1026 (Messages and Codes)“IMS problem determination” on page 11




DFS2490A UNLOCK SYSTEM COMMANDREQUIRED BEFORE SHUTDOWN.

ExplanationFollowing an XRF takeover, either the IMS /UNLOCKSYSTEM command or the z/OS Availability Manager(AVM) UNLOCK command must be entered to purge I/Otolerated data before IMS can be shut down.

System actionShutdown command is rejected.

System programmer responseEnter either the IMS /UNLOCK SYSTEM or the AVMUNLOCK command.

Module:DFSICM30

DFS2491I A DIVIDE EXCEPTION HASOCCURRED-NEXT LINE OF DATAMAY BE IN ERROR

ExplanationA divide exception (ABEND0C9 or ABEND0CB)occurred while dividing two fields. The usual reasonsfor this message are:

1. One of the fields being used for the divide isincomplete because either the input tape wasnot completely processed or the input tape wasincomplete;

2. The DC monitor was active too long causing thedividend field to be so large that the quotient andremainder did not fit into the assigned work area.


DFS2492I AREA aaaaaaaa HAS IOT EEQE -CANNOT ACTIVATE VSO

ExplanationA /START AREA was entered for area aaaaaaaa.At the time of the command, the Virtual StorageOption (VSO) was not active for the area, but the areawas defined to DBRC as VSO. Normally, the /STARTAREA command would put the area into a data space(activate VSO), but area aaaaaaaa has one or more

I/O toleration EEQEs from an XRF takeover. It is notpossible to activate VSO for the area until the EEQEsare purged.

System actionVSO is not activated for the area.

Operator responseEnter either the IMS /UNLOCK SYSTEM or the AVMUNLOCK command to purge I/O toleration EEQEs.Then reenter the /START AREA or UPDATE AREASTART(ACCESS) command.

Module:DBFVPR00

DFS2493W A CENTRAL/EXPANDED STORAGESHORTAGE EXISTS. VSO WILLBE ACTIVATED FOR areaname.BLOCKS REQ/AVAIL rrrrrr/aaaaaa

ExplanationThe data entry database (DEDB) area was defined asa Virtual Storage Option (VSO) area. While opening thearea, IMS determined that the amount of central andexpanded storage available was not enough to satisfythe size of the area. Normal VSO processing is allowedfor the area.

System actionThe area is opened with the Virtual Storage Option.

Operator responseThis warning message indicates that a potential VSOstorage shortage exists. For the area indicated in themessage, not enough VSO storage exists to hold theentire area. Accessed CIs are loaded into VSO, but itis possible that storage constraint problems, such aspaging, might exist. If constrained storage representsa problem in your environment, you can remove thearea from VSO by issuing the /VUN command. You canreactivate VSO processing for the area at any time byreissuing the /START AREA or by issuing an UPDATEAREA START(ACCESS) command.

Module:DBFVSOP0

DFS2494I DFHSM RECALL DSN=datasetname- RC=xxx

ExplanationA RECALL request for migrated data setname receivedthe nonzero return code xxx. For information on


the return codes, see the DFHSM User's Guide andthe DFHSM Messages manuals. Appropriate messagesfrom DFHSM can also be issued. This message is onlyissued after three attempts of the recall.

System actionIMS stops any further attempts to retrieve themigrated resource.

Operator responseSee the DFHSM User's Guide and the DFHSM Messagesmanuals for the appropriate action, based on thereturn code you received. After taking any actionrecommended by these manuals, issue a /STARTDB, UPDATE DB START(ACCESS)/START AREA, orUPDATE AREA START(ACCESS) command for IMS toretry the recall.

DFS2495I RESOURCE name NOT ALLOCATED- MIGRATED AND BEINGRECALLED

ExplanationThe system was attempting to dynamically allocate theFast Path area or DL/I database, as identified by nameand found either the area data set or one of the datasets in the database was migrated to auxiliary storage.

System actionThe allocation process is terminated and the internalcaller of the allocation is given a nonzero return code.An attempt is made to asynchronously recall the dataset from auxiliary storage.

DFS2497W ICH408I MESSAGES ARESUPPRESSED FOR REGIONYYYYYYYY FOR TRAN ZZZZZZZZBY RAS SECURITY

ExplanationIMS RAS security is suppressing additional ICH408Imessages because there is a RACF definition error forthe identified transaction for the identified dependentregion.

In the message text:YYYYYYYY

The dependent region nameZZZZZZZZ

The transaction name

System actionIMS RAS security suppresses additional ICH408Imessages for the transaction and dependent region.The transaction is still in the message queue and couldbe processed by another eligible dependent regionor another IMS system in the IMSplex. Processingcontinues.

Programmer responseDetermine whether it is appropriate to grant the regionaccess to process the transaction. If so, grant theregion access to process the transaction, and updatethe appropriate RACF definitions. Otherwise, removethe transaction from the region.


Module:DFSSCHR0


DFS2498W IMS SYSTEM ERROR DURINGfunction_type FOR DATABASE|DATASET REASON x

ExplanationA system error occurred during function_typeprocessing.

The function_type can be one of the following:

• ALLOCATE• DEALLOCATE

The error occurred for one of the following reasons:


01An invalid AWE was passed to the dynamicallocation routine.

02An attempt was made to deallocate a databasewithout stopping its index.

03The DDIR for the database was found to be inNOTINIT status.

04An attempt was made to deallocate a databasewhile the schedule bit was on.


05An attempt was made to deallocate a databasewhile one of its DCBs was still open.

06The data management block (DMB) for thedatabase could not be loaded.

07An attempt was made to deallocate a database,but a DDNAME for one of its data sets was notfound in the TIOT.

08A data set of a database resides on a device notsupported by IMS.

System actionThe request is terminated.

Programmer responseContact IBM Software Support for assistance.


Module:DFSMDA00


DFS2499W INVALID function_type REQUESTFOR DATABASE | DATASET FORREASON x

ExplanationThe function_type can be one of the following:

• ALLOCATE• DEALLOCATE

The identified function was invalid for one of thefollowing reasons:Code (hex)

Meaning01

The DFSMDA dynamic allocation member was notpresent in SDFSRESL or was incomplete.

02Some, but not all, of the data sets of a databasewere allocated by JCL. The entire database mustbe allocated by JCL or by the DFSMDA member,but not both. Mixed allocations are invalid.

03The SIOT for the data set indicates a SYSOUT dataset which cannot be deallocated by IMS.

04The SIOT for the data set indicates a VIO data setwhich cannot be deallocated by IMS.

05An attempt was made to deallocate a database,but the job file control block (JFCB) for one of thedata sets indicated no volumes.

06Concatenation of the staging IMSACB DDstatement is not allowed.

System actionThe request is terminated.

Programmer responseCorrect the condition to allow future requests to beprocessed successfully.

Module:DFSMDA00

DFS2500I DATABASE|DATASET xxxxxxxx{DSN=yyyyyyyy} SUCCESSFULLYaction_type

ExplanationProcessing for the identified function completed forthe database or data set name, where xxxxxxxx isthe database or data set name, where xxxxxxxx isthe name. For allocation of a monitor data set or anarchived log (SLDS), the data set name is also provided(yyyyyyyy).

The action_type can be one of the following:

• ALLOCATED• DEALLOCATED

Module:DFSMDA00




DFS2501W INSUFFICIENT VIRTUAL STORAGEAVAILABLE FOR ALLOCATION/DEALLOCATION FOR RESOURCExxxxxxx IN PROCESS y

ExplanationInsufficient virtual storage was available to completeallocation or deallocation of a resource during theprocess identified by y.

This problem can occur in the IMS control region or theDLISAS region. For additional information about thiserror, see the explanations for the z/OS system abends878 and 80A.

In the message text:xxxxxxx

The resource for which there was insufficientvirtual storage for action requested.

yThe process.Code y

Allocation process1

GETMAIN failed for work area (batch only)2

GETMAIN failed for a temporary parameter list(deallocation of JCL-allocated database)

3BLDB failed on IMSDALIB

4BLDB failed on STEPLIB

5GETMAIN failed for storage for DFSMDAmember

Insufficient virtual storage was available to completeallocation or deallocation of a database. This problemcan occur in the IMS control region or the DLISASregion. For additional information about this error, seethe explanations for the z/OS system abends 878 and80A.

System actionSystem processing continues.

Programmer responseEvaluate the private storage usage in the IMScontrol region or the DLISAS region to ensurethat unused storage is not being allocated ora process is not looping in acquiring storage.If this message continues to occur, create aconsole memory dump of the IMS CTL and DLISASregions by using the MVS DUMP command withSDATA=(CSA,PSA,RGN,SQA,SUM,TRT), then callIBM Software Support.

Module:DFSMDA00

Related referencez/OS: System code 878z/OS: System code 80A

DFS2502W INSTALLATION EXITPREVENTS DYNAMICALLOCATION|DEALLOCATION

ExplanationThe IMS user has an installation exit routine fordynamic allocation requests that prevents IMS fromdynamically allocating or deallocating databases.


Programmer responseChange the installation exit routine to allow allrequests from an IMS control region.

DFS2503W DYNAMIC action_type FAILEDFOR DATA SET NAMExxxxxxxx.xxxxxxxx.xxxxxxxxDATABASE NAME dbdnameREASON CODE yyyyy

ExplanationProcessing for the identified function failed for thedatabase and data set name represented by dbdnameand xxxxxxxx. The phrase WITHIN PSB psbnameis added only if the PSB is known at the time ofthe allocation attempt. The phrase DATABASE NAMEdbdname is issued in the message only if the data setis an IMS database. If a function for a dataset fails, a


http://www-01.ibm.com/support/knowledgecenter/SSLTBW_2.4.0/com.ibm.zos.v2r4.ieah700/m015281.htm?lang=en

http://www-01.ibm.com/support/knowledgecenter/SSLTBW_2.4.0/com.ibm.zos.v2r4.ieah700/m015272.htm?lang=en

short form of the message showing the DDNAME andDATA SET xxxxxxxx will be issued instead.

The action_type can be one of the following:

• ALLOCATION• DEALLOCATION

System actionProcessing is terminated for the request.

If one area data set (ADS) of a multiple-area-data-set(MADS) area of a Fast Path DEDB fails allocation, thearea is stopped and the status of the ADS is notchanged in the RECON data set. If the failure occursduring emergency restart, the ADS is set to unavailablestatus and the other ADSs are recovered.

Programmer responseIn most cases, the description of the reason codeidentifies the action to take before you can retry therequest. Correct the error and retry the request.

Module:DFSMDA00


DFS2504I ERROR PROCESSING variable text:SPECIFIED AREA NAMES DO NOTMATCH

ExplanationIn the message text, variable text refers to one ofthe following targets, depending on whether the IMSmanagement of ACBs is enabled:ACBLIB

An area name in the parameter list did not existin the ACBLIB, or the names in the parameter listwere not in the same sequence as the DBD dataset statements.

This form of message text is the default.

CATALOGAn area name in the parameter list did not existin the IMS catalog, or the area names in theparameter list were not in the same sequence asthe database definition statements.

This form of message text is issued when the IMSmanagement of ACBs is enabled in an IMS CatalogDefinition exit routine (DFS3CDX0).

System actionThe utility terminates with a return code of 08.

Programmer responseCorrect the names in the parameter list or thesequence of the names.

Problem determinationCompare the area names that are supplied in theparameter list with the names and sequence in thedatabase definition statements.

Related referenceIMS Catalog Definition exit routine (DFS3CDX0)(Exit Routines)

DFS2505I ERROR PROCESSING variable text:OPEN ERROR


The program DBFUMIN0 was not able to open thespecified ACBLIB data set.


CATALOGThe program DBFUMIN0 was not able to open thespecified IMS catalog directory data set.



Programmer responseThis problem normally results from a JCL error. If so,correct the JCL and resubmit the job.

If this message is issued for the IMS catalog, revisitthe steps that were taken to create and populate thecatalog directory.






http://www.ibm.com/support/knowledgecenter/SSEPH2_15.1.0/com.ibm.ims15.doc.err/ims_catalogdefexit.htm#ims_catalogdefexit




IMS Catalog Populate utility (DFS3PU00)(System Utilities)Related information“IMS problem determination” on page 11IMS messages and codes problemdetermination is accomplished by usingprocedures established by IBM.

DFS2506I ERROR OPENING CONTROL FILE

ExplanationThe program DBFUMIN0 was not able to open thespecified control file.


Programmer responseMake sure that a DD statement is present and thatits specifications are correct. If a hardware failure isindicated, correct the problem and rerun the job.

DFS2507I ERROR PROCESSING DATA SETINFO: {MACRO=MODCB | SHOWCB| RDJFCB}, R15=xxx [R0=]

ExplanationProgram DBFUMIN0 encountered an error whileprocessing data set information. A MODCB, SHOWCB,or RDJFCB macro did not complete successfully. Thereturn code from the macro in R15 is shown and thereason code in R0 is given if the MODCB or SHOWCBhad a return code of 4.


Programmer responseSee an explanation of the VSAM return and reasoncodes. Correct any user errors, and resubmit the job.


Related referencez/OS: VSAM macro return and reason codesRelated information“IMS problem determination” on page 11IMS messages and codes problemdetermination is accomplished by usingprocedures established by IBM.

DFS2508I ERROR PROCESSING variabletext: INCORRECT MEMBER TYPESPECIFIED


Program DBFUMIN0 determined that the memberspecified in the ACBLIB was not for a DEDB DBD.


CATALOGProgram DBFUMIN0 determined that the memberspecified in the IMS catalog was not for a DEDBDBD.



Programmer responseSpecify the correct member in the ACBLIB or the inIMS catalog.

Related referenceIMS Catalog Definition exit routine (DFS3CDX0)(Exit Routines)IMS Catalog Populate utility (DFS3PU00)(System Utilities)

DFS2509I DEFINED (CI SIZE | RECSIZE) INCATALOG NOT CONSISTENT WITHDBD SIZE PARM

ExplanationThe defined control interval (CI) size or LRECL sizein the catalog was not consistent with the DBD sizeparameter.


Programmer responseChange the CI size or LRECL size in the DBD or thecatalog so that they are equal.


http://www.ibm.com/support/knowledgecenter/SSEPH2_15.1.0/com.ibm.ims15.doc.sur/ims_catalog_pop_utility.htm#ims_catalog_pop_utility







DFS2510I INSUFFICIENT SPACE DEFINEDFOR AREA=areaname DD=ddname

ExplanationThe space allocated for the data set, specified byddname, is not sufficient to hold the database area asdefined in the DBD.

System actionThe Fast Path utility being used terminates.

Programmer responseDecrease the space required for an ADS of the dataset indicated by ddname by altering the DBD. As analternative, increase the space allocated for an ADS ofthe data set indicated by ddname by altering the VSAMdefinition. If areaname has multiple data sets, ensurethat enough space is also defined for the other datasets.

DFS2511I CONTROL BLOCK MANIPULATIONERROR DURING FORMATPROCESSING

ExplanationAn error occurred during a control block manipulationmacro.


Programmer responseEnsure that all DD statements for DEDB areas arecorrect.



DFS2512I AREA=areaname DD=ddname(OPEN|CLOSE) ERROR

ExplanationAn error occurred during OPEN or CLOSE processing ofthe data set.


Programmer responseEnsure that the DD statement for the area is correct.



DFS2513I AREA=areaname DD=ddnameWRITE ERROR

ExplanationAn I/O write error occurred while writing a formattedcontrol interval (CI).


Programmer responseA possible hardware error has occurred, and it mightbe necessary to allocate space for the DEDB data seton a different DASD device.

This error might also be the result of attempting toallocate an ADS greater than 4 GB, the maximum sizeof a DEDB area.

Verify the UOW, ROOT and SIZE parameters from theDBDGEN. Do not allocate a DEDB area that is greaterthan 4 GB in size.

Verify that the initial size for the VSAM CLUSTER is notgreater than 4 GB.



DFS2514I SYSPRINT OPEN ERROR

ExplanationProgram DBFUMIN0 could not successfully open theSYSPRINT data set.



Programmer responseThis problem is probably due to a JCL error. Correctthe JCL, and resubmit the job.

DFS2515I SYSPRINT WRITE ERROR

ExplanationProgram DBFUMIN0 attempted to write to theSYSPRINT data set and an I/O error occurred.




DFS2516I INVALID PARM SPECIFIED INPARM FIELD-MORE THAN 2048PARMS SPECIFIED

ExplanationMore than 2048 AREA= utility control statements weregiven in the CONTROL DD statement for the DEDBinitialization utility (DBFUMIN0).


Programmer responseCorrect the parameters, and resubmit the job.

DFS2517I I/O ERROR READING CONTROLFILE

ExplanationUtility program DBFUMIN0 encountered an I/O error.


Programmer responseResubmit the job after hardware error is fixed.

DFS2518I INVALID PARM SPECIFIEDIN PARM FIELD-INVALIDCHARACTER IN PARM

ExplanationThe DEDB initialization utility (DBFUMIN0) foundan invalid character in a utility control statement.Names following the AREA= control statement mustbe one to eight characters in length and composedof alphanumeric characters (A-Z, 0-9) or the specialcharacters '$', '#', and '@'.


Programmer responseCorrect the invalid character, and resubmit the job.

DFS2519I ERROR PROCESSING variable text:READ ERROR


An I/O error has occurred, or a block read from theACBLIB did not contain the DMCB and all DMACs.


CATALOGAn I/O error has occurred, or a block read fromthe IMS catalog did not contain the DMCB and allDMACs.



Programmer responseEnsure that the JCL for the ACBLIB or for the IMScatalog is correct and that the ACBGEN is correct.







DFS2520I MULTI-POSITIONING CANNOT BESPECIFIED FOR A MSDB. - PCBdbdname IN PSB psbname.

ExplanationThe PCB for an MSDB DBD specified multi-positioning(POS=M). This option is invalid for MSDBs.

System actionIMS continues processing the PCB, but does notprocess the remaining PCBs in the PSB. The PSB isdeleted from ACBLIB. Normal execution continues,and the return code is set to 8.

Programmer responseCorrect the POS= parameter on the PCB statement,rerun PSBGEN, and rerun ACBGEN with a BUILDstatement for this PSB.

DFS2521I INVALID SENSEG-sensegnameSPECIFIED IN PCB-dbdname INPSB-psbname

ExplanationThe named sensitive segment in the indicated PSB isnot defined in the indicated DBDGEN.

System actionIMS continues processing the PCB and does notprocess the remaining PCBs in the PSB. The PSB isdeleted from the ACBLIB. Normal execution continuesand the return code is set to 8.

Programmer responseCorrect or remove the SENSEG name on the SENSEGstatement in the indicated PCB and PSB. Then rerunthe PSBGEN, and rerun the program with a BUILDstatement for this PSB.



DFS2522I INVALID PROCOPT SPECIFIEDFOR SENSEG-senseg name INPCB-dbdname IN PSB-psbname

ExplanationThe named sensitive segment has an invalidprocessing option specified in the indicated PCB andPSB.

System actionIMS continues processing the PCB and does notprocess the remaining PCBs in the PSB. The PSB isdeleted from the ACBLIB. Normal execution continues,and the return code is set to 8.

Programmer responseCorrect the error processing option on the SENSEGstatement in the indicated PCB and PSB. Then rerunthe PSBGEN, and rerun the program with a BUILDstatement for this PSB.



DFS2523I INVALID SENSEG HIERARCHICALSTRUCTURE SPECIFIED IN PCB-dbdname IN PSB-psbname

ExplanationOne or more sensitive segments within the named PCBhave an invalid sensitive segment level specification inthe indicated PSB. The valid sensitive segment levelsare:

• MSDB access is 1.• DEDB access is 2.

System actionIMS continues processing the PCB and does notprocess the remaining PCBs in the PSB. The PSB isdeleted from the ACBLIB. Normal execution continues,and the return code is set to 8.

Programmer responseCorrect the PARENT parameter on the SENSEGstatements in the indicated PCB and PSB. Then rerun


the PSBGEN, and rerun the program with a BUILDstatement for this PSB.



DFS2524I AREA=areaname, DD=ddname,READ ERROR. EEQE ALREADYEXISTS, CI-RBA=nnnnnnnn

ExplanationA READ ANY request was rejected because an I/OToleration extended error queue element (EEQE)exists for control interval (CI) nnnnnnnn, and I/Oprevention is in effect.

System actionStatus code AO is returned to the application program.If data has already been modified on this call, theapplication program is terminated with IRLM abend3303. Status code BA might be returned if an INIT callwas issued.

Programmer responseIf the application program terminates with abend3303, see the last paragraph of the Operator responsefor abend 3303 for the appropriate response.


DFS2525I FAST PATH DATA BASE DEFINEDIN A NON-FP SYSTEM: dbname

Explanation:For information about this message, see DFS2525W.

Related information“DFS2525W” on page 725FAST PATH TRANSACTION tranname IS NOTCREATED IN A NON-FP SYSTEM system

DFS2525W FAST PATH TRANSACTIONtranname IS NOT CREATED IN ANON-FP SYSTEM system

Explanation:The transaction tranname is defined as Fast Pathexclusive or Fast Path potential, but this IMS did nothave Fast Path enabled (FP=N). Transaction trannameis not created. The Fast Path database dbname is

defined in an IMS system that does not have Fast Pathenabled (FP=N). Database dbname is not created.

System actionNormal execution continues. The transactiontranname was not created.

Programmer responseFor databases, no action is required unless access tothe Fast Path database is wanted. The IMS systemmust be cold started with Fast Path enabled, withFP=Y defined as an execute parameter.

For transactions, no action is required, unless youwant to use a Fast Path transaction. To use thetransaction, you must cold start the IMS systemwith Fast Path enabled (FP=Y defined as an executeparameter). If automatic export is enabled and anexport of the systems resource definitions has beendone, the Fast Path resource definitions are not in theRDDS. To restore the Fast Path resources, you can doone of the following:

1. Cold start IMS with FP=Y specified as an executeparameter and AUTOIMPORT=MODBLKS specifiedin the DYNAMIC_RESOURCES section of theDFSDFxxx PROCLIB member. Fast Path resourcesdefined in the MODBLKS data set are createdduring cold start. Resources that were createddynamically and are not in the MODBLKS data setare lost.

2. Cold start IMS with FP=Y specified as an executeparameter and AUTOIMPORT=RDDS specifiedin the DYNAMIC_RESOURCES section of theDFSDFxxx PROCLIB member. Issue CREATEcommands to create the Fast Path resources thatare needed.


Related information“DFS2525I” on page 725FAST PATH DATA BASE DEFINED IN A NON-FPSYSTEM: dbname“IMS problem determination” on page 11IMS messages and codes problemdetermination is accomplished by usingprocedures established by IBM.

DFS2526I DATA SET NOT EMPTY FORAREA=areaname DD=ddname

ExplanationAn attempt was made to format a DEDB data set whichwas not empty.




Programmer responseUse the appropriate VSAM options to SCRATCH,DELETE, ALLOCATE, and DEFINE the data set, andrerun the Initialization utility.



DFS2527I NUMBER OF FAST PATH DATABASE BUFFERS TO BE PAGE-FIXED EXCEEDS LIMIT.

ExplanationDuring region initialization, the number of Fast Pathdatabase buffers page-fixing exceeded the totalnumber of buffers currently available.

System actionThe PSB is not initialized and the region terminatesabnormally with abend 1006. In a DBCTL environment,if the failing PSB is a thread, a return code ise passedback to the CCTL. No abend is issued from the DBCTLregion.

Operator response:Contact your IMS system programmer.

Programmer responseFor BMPs, MPPs and IFPs, increase the DBBFparameter in the IMS control region job step EXECPARM during the next IMS execution, decrease theNBA or OBA parameter in the job step EXEC PARM, orwait for a region using Fast Path buffers to terminateand rerun the job. For threads in a DBCTL environment,increase the CNBA parameter in DFSPRP, decrease theFPBUF or FPBOF parameter, or wait for a currentlyscheduled thread using Fast Path buffers to terminateand rerun the job.




DFS2528A DUPLICATE AREA NAME-areaname FOUND IN DEDB-databasename1-AND-database name2

ExplanationA duplicate area name was found in the named DEDBDBD defined in the IMS system. The area name, thatwas defined in the DD1 operand on one of the AREAstatements in the DBDGEN, is defined in another DEDBDBDGEN or is defined within the DEDB DBDGEN.

System actionIf the message is received following the /MODIFYPREPARE or INITIATE OLC PHASE(PREPARE)command, the command is terminated.

Operator response:(master terminal) If the error occurred followingthe /MODIFY PREPARE or INITIATE OLCPHASE(PREPARE) command, contact your IMSsystem programmer.

Programmer responseIf the error occurred during initialization, correct theDBD in error, run the Application Control BlocksMaintenance utility again, and rerun the job.

If the error occurred following the /MODIFY COMMITor INITIATE OLC PHASE(COMMIT) command,correct the DBD in error, run the Application ControlBlocks Maintenance utility again, and run the OnlineChange utility.


Module:DBFINI20, DBFOLC02


DFS2529I NO FAST PATH REGION IS ACTIVE.

ExplanationA Fast Path input message was queued in the loadand balancing group. However, the last region that wasscheduled to process the message had terminated.The terminal user is informed that no Fast Path regionis available to process an input message at this time.




Operator response(master terminal) Restart the designated Fast Pathregion.

(terminal) Make sure the Fast Path region has beenrestarted and then reenter the input message.



DFS2530 FAST PATH EXCLUSIVETRANSACTION FROM NON-FPTERMINAL

ExplanationA message destined for a Fast Path exclusivetransaction was received from a terminal that didnot have a Fast Path message buffer defined duringsystem definition or from the master terminal.


Programmer responseRegenerate the system, specifying a Fast Pathmessage buffer for all terminals requiring Fast Pathsupport.



DFS2531 MESSAGE ROUTED TO UNDEFINEDTRANSACTION CODE

ExplanationThe Fast Path user input exit directed Fast Path tosearch the routing code table using the transactionidentification as the argument. Program DBFHIEL0searched the table and did not find an equalcomparison.


Programmer responseAdd the transaction code to the routing code tableor correct the user input exit to provide the correctrouting information.



DFS2532 MESSAGE ROUTED TO UNDEFINEDROUTING CODE

ExplanationThe Fast Path user input exit directed Fast Path tosearch the routing code table with a routing code theexit supplied. Program DBFHIEL0 searched the tableand did not find an equal comparison.


Programmer responseIf the correct routing code is being generated, addthe routing code to the routing code table. Otherwise,modify the user input exit to generate the correctrouting code.



DFS2533 ROUTING CODE NOT ACTIVE

ExplanationNo message processing programs were scheduled forthis routing code. The master terminal operator mustschedule the message processing program before FastPath can accept any messages for that destination.



Operator response:Notify the master terminal operator that the routingcode is not active.



DFS2534 TRANSACTION CODE NOT ACTIVE

ExplanationNo message processing programs were scheduledfor the routing code table entry representing thistransaction. At least one message processing programmust be started by the master terminal operatorbefore Fast Path can allow messages to be scheduledto this destination.


Operator response:Notify the master terminal operator that thetransaction code is not active.



DFS2535 FUNCTION NOT AVAILABLE TOINQUIRY ONLY TERMINAL

ExplanationThe routing code table entry was defined as updateat IMS system definition and the input terminal wasdefined as inquiry only.


Operator response:Reenter the transaction from an update terminal.

DFS2536 FAST PATH EXCLUSIVE TRANROUTED TO IMS

ExplanationThe Fast Path user input exit directed Fast Path toreturn a message destined for a Fast Path exclusivetransaction to IMS for scheduling.


Programmer responseCorrect the user input exit to route Fast Path exclusivetransactions to Fast Path.



DFS2537 INVALID KEYWORD-FAST PATHNOT INSTALLED

ExplanationA Fast Path keyword, MSDBLOAD, was entered in an /NRESTART command, but Fast Path was not installed.

System actionThe /NRESTART command is ignored.

Operator response:(master terminal) Reenter the command without theFast Path keyword.

DFS2538 MSDBLOAD KEYWORD INVALID INERESTART COMMAND

ExplanationAn invalid keyword, MSDBLOAD, was entered in an /ERESTART command.


Operator response:Reenter the command without the Fast Path keywordMSDBLOAD.

DFS2539I OPEN ERROR ON INPUT DATA SET,NO MSDBS LOADED


ExplanationThe main storage database (MSDB) input data set wasnot able to be opened successfully. Possible causes forthis problem are:

• There is a missing DD statement. z/OS prints amessage identifying the problem.

• The JCL is incorrect.• A hardware error exists. The system terminates

abnormally if such a problem is encountered.

System actionIf the DD statement is missing, IMS continues, but noMSDBs are loaded. If the JCL is incorrect. The resultsare unpredictable.

Programmer responseEnsure that a DD statement is present and thespecifications are correct. Shut down IMS and restartthe system with MSDBLOAD. If a hardware failure isindicated, rerun the job.

DFS2540I DBDNAME dbdname SEQUENCEERROR, NO MSDBS LOADED

ExplanationThe database names in the MSDB input data set werenot in ascending order.

System actionIMS continues processing, but no MSDBs are loaded.

Programmer responseSort the input data set, and reload all MSDBs.

DFS2541I SEGMENT LENGTH ERROR INMSDB dbdname

ExplanationThe input segment length of this MSDB was not equalto the length specified.

System actionThe segment is ignored and the MSDB is stopped.

Programmer responseCorrect the input by running the MSDB Maintenanceutility. Reload all MSDBs.

Important: For operational convenience, the MSDBcan be started, but the segments with invalid fieldswill not be available and status GE or GB will beissued. These segments cannot be altered, replaced,or deleted until the MSDB data set has been correctedand the MSDBs have been reloaded.

DFS2542I KEY SEQUENCE ERROR IN MSDBdbdname

ExplanationThe segments within an MSDB were not in ascendingkey order.

System actionThe segment is ignored and this MSDB is stopped.

Programmer responseSort the input data set, and reload all MSDBs.

DFS2543I INSUFFICIENT SPACE FOR MSDBdbdname

ExplanationThere were more input segments than numbers ofsegments defined in the MSDB PROCLIB member.

System actionAll excessive segments are ignored, and this MSDB isstopped.

Programmer responseCheck the MSDB Maintenance utility output for thenumber of segments in this MSDB, and update thePROCLIB member accordingly. Reload all MSDBs.

DFS2544I MSDB dbdname CONTAINSINVALID DATA

ExplanationDuring the loading process, module DBFDBIL0detected invalid packed data in this MSDB.

System actionSegments with invalid data are flagged, and the MSDBis stopped.

Programmer responseCorrect the input for this MSDB by running the MSDBMaintenance utility. Reload all MSDBs.


DFS2545I INVALID MSDB TYPE IN INPUT,MSDB dbdname

ExplanationThe MSDB type was not valid. The MSDB was notterminal-related, or it was nonterminal-related withand without the terminal key.

System actionAll segments of this MSDB are ignored. The MSDB isstopped.

Programmer responseCorrect all segments in this MSDB and reload allMSDBs.

DFS2546I INVALID KEY LENGTH IN MSDBdbdname

ExplanationThe key length of this segment must be equal to thelength of the LTERM name (eight characters) if theMSDB type is terminal-related or nonterminal-relatedwith the terminal key.

System actionThe segment is ignored and this MSDB is stopped.

Programmer responseCorrect the input, and reload all MSDBs.

DFS2547I KEY (LTERM) xxxxxxxx NOT FOUNDIN SYSTEM

ExplanationAn LTERM name was used as a key. However, it wasnot able to be located in this IMS system.

System actionThe segment is ignored and the MSDB is stopped.

Programmer responseCorrect the input by running the MSDB Maintenanceutility or redefine IMS with this LTERM name. Reloadall MSDBs.

DFS2548I ERRORS IN MSDB dbdname, MSDBSTOPPED

ExplanationModule DBFDBIL0 attempted to load the MSDBsand detected an error. For further information,see messages DFS2541I, DFS2542I, DFS2543I,DFS2544I, DFS2545I, DFS2546I, DFS2547I, andDFS2550I.

System actionThe MSDB is stopped.

Programmer responseCorrect all errors described in the referencedmessages. Reload all MSDBs.

Related information“DFS2541I” on page 729SEGMENT LENGTH ERROR IN MSDB dbdname“DFS2542I” on page 729KEY SEQUENCE ERROR IN MSDB dbdname“DFS2543I” on page 729INSUFFICIENT SPACE FOR MSDB dbdname“DFS2544I” on page 729MSDB dbdname CONTAINS INVALID DATA“DFS2545I” on page 730INVALID MSDB TYPE IN INPUT, MSDBdbdname“DFS2546I” on page 730INVALID KEY LENGTH IN MSDB dbdname“DFS2547I” on page 730KEY (LTERM) xxxxxxxx NOT FOUND IN SYSTEM“DFS2550I” on page 731TYPES DO NOT MATCH IN MSDB dbdname

DFS2549I I/O ERROR ON INPUT DATA SET,NO MSDBS LOADED

ExplanationAn I/O problem was encountered. This message ispreceded by message DFS2552I.

System actionThe MSDB loading process is stopped.

Programmer responseCheck the information in the DFS2552I message. Tryloading from a different unit, or re-create the inputdata set. Reload all MSDBs.



SYNAD error message buffer

DFS2550I TYPES DO NOT MATCH IN MSDBdbdname

ExplanationA discrepancy was found between the MSDB type inthe input data set and the type specified in the DBD.

System actionThe segment is ignored and the database is stopped.

Programmer responseCorrect the input data set, or rerun DBDGEN. Reloadall MSDBs.




DFS2551I MSDB dbdname IS EMPTY

ExplanationThe main storage database (MSDB) identified bydbdname was specified in the MSDB PROCLIBmember, but module DBFDBIL0 found no input in thedata set.

Programmer responseIf the MSDB is dynamic, insert commands (ISRT) canbe used to load the database.

DFS2552I SYNAD error message buffer

ExplanationThis message contains the MVS SYNAD errormessage buffer. For further information, see DataAdministration: Macro Instruction Reference for MVS/DFP.

This message is followed by message DFS2549I.

System actionThe MSDB loading process is stopped.

Programmer responseTry loading from a different unit, or re-create the inputdata set.

Related information“DFS2549I” on page 730I/O ERROR ON INPUT DATA SET, NO MSDBSLOADED

DFS2553I DBDNAME dbdname NOT FOUNDIN SYSTEM

ExplanationProgram DBFDBIL0 found the database namedbdname in the input data set. However, that namewas not defined in the MSDB PROCLIB member, orprogram DBFINTEO found a PCB that references aDBD that could not be found in the system.

System actionThe segment is ignored. For the second case, replacethe PSB or the DBD, or both.

Programmer responseCorrect the PROCLIB member. Reload all MSDBs.

DFS2554I MSDB dbdname LOADED

ExplanationThis message verifies that this database was loadedwithout errors.

DFS2555I NO SUFFIX FOR MSDB MEMBERDEFINED.

ExplanationThere was no suffix defined in the IMS startupprocedure for the MSDB member.


Programmer responseBe sure that the current IMS system does not requireany MSDBs. If the system does require MSDBs, stopIMS, and update or override the startup procedure.

DFS2558I THE INTENT LIST LENGTHEXCEEDS LIMIT IN PSB psbname.

ExplanationThe PSB identified by psbname has large numbers ofDBPCBs, causing the intent list length to exceed the64 K limit.

System actionThe ACBGEN utility terminated due to this error.

Programmer responseDecrease the number of DBPCBs in the PSB, and rerunthe PSBGEN and the ACBGEN.

Module:DFSUAMB0


DFS2559A GETMAIN FAILED.

ExplanationThe IMS control region did not have sufficient storageto build a work area.


Programmer responseIncrease the size of the IMS control region by 4096bytes.


DFS2560I WAITING FOR THE OLCSTAT DATASET

ExplanationThe global online change allocated the OLCSTAT dataset. This batch job is waiting until the global onlinechange deallocates the OLCSTAT.

System actionProcessing continues when the global online changedeallocates the OLCSTAT data set.


Module:DFSBIND0

DFS2561A FORMAT ERROR IN COMMANDFROM DBFMSDBn ENCOUNTEREDIN POSITIONxx

ExplanationModule DBFINI10 encountered a format error inmember DBFMSDBn of the ddname=PROCLIB dataset.


Programmer responseCorrect the format of the MSDB parameter inDBFMSDBn, and rerun the job.


DFS2562A DUPLICATE DBD NAME SPECIFIED

ExplanationA duplicate DBD name was specified in the MSDB loaddetermination member in DBFMSDBn.


Programmer responseCheck and correct the DBD names defined in PROCLIBmember DBFMSDBn.


DFS2563I NO MSDBS FOUND-MSDBLOADIGNORED


• The Fast Path keyword MSDBLOAD was entered withan /NRESTART command, but no PROCLIB memberwas defined in the IMS procedure, or

• No DBD exists in ACBLIB for the MSDB.

Message DFS2706A or DFS0579W is issued beforethis message.

System actionThe MSDBLOAD keyword is ignored.

Programmer responseIf you want to use MSDBs:

• Add an MSDB member to PROCLIB.• Make sure a DBD for the MSDB. exists in ACBLIB.• Change the IMS procedure.

Related information“DFS0579W” on page 206FIND FAILED FOR DDNAME xxxxxxxxMEMBER=yyyyyyyy RC=zz“DFS2706A” on page 768





MSDB xxxxxxxx {NOT SPECIFIED AT SYSGEN|HAS NO DBD GENERATED IN ACBLIB|NOTDEFINED AS A MSDB AT DBDGEN}.

DFS2564I ERROR IN OBTAINING DEVICETABLE, DDNAME ddname,RC=return code

ExplanationProgram DBFDBTC0 detected an error when an MVSDEVTYPE macro was issued.Code

Meaning04

An incorrect ddname exists.08

There is an invalid area address.

System actionThe MSDB CHKPT/DUMP data is not formatted ifthe error occurred during a cold start. The MSDBimage copy is not loaded if the error occurred in anemergency restart or in a normal restart.

Programmer responseIf the return code was 04, check and correct theddname.



DFS2565I BLOCK LENGTH EXCEEDS TRACKCAPACITY, DDNAME=ddname

ExplanationThe block length specified in the DCB exceeds thetrack capacity of this device type. This error mightoccur if the block size of the DCB was changed.




ERROR IN OBTAINING DEVICE TABLE,DDNAME ddname, RC=return code

DFS2566I BUFFER LENGTH IS ZERO,DDNAME=ddname

ExplanationThe buffer length of this DCB was modified to zero.



Related informationDFS2564IERROR IN OBTAINING DEVICE TABLE,DDNAME ddname, RC=return code

DFS2567I DUMMY/INCORRECT ALLOCATIONFOR DDNAME ddname-DATA SETCANNOT BE USED

ExplanationThe DD statement referenced a dummy allocation or aSYSIN/SYSOUT data set.


Programmer responseCorrect the DD statement, and resubmit the job.


DFS2568I ddname IS NOT ON DIRECTACCESS STORAGE DEVICE

ExplanationThe UCBTYPE pointed to by this DD statement did notindicate a direct access storage device.



Programmer responseCorrect the DD statement and the allocation, andresubmit the job.


DFS2569I AREA=areaname DD=ddnameCONNECT|EXTEND ERROR

or

AREA=areaname DD=ddname SAF ACCESS DENIED

ExplanationThe module DBFMMIT0 was unable to connect or openthe data set associated with the ddname. VSAM errormessage IEC161I was issued before this message.

System actionIf a request is made to open an ADS for theDEDB Create utility, the utility attempts to openthe next ADS. If the next ADS is unavailable, theDEDB Create utility terminates and the named areacontinues processing. If a request is made to openan ADS for other than the DEDB Create utility,messages DFS3702I and DFS2574I are issued afterthis message. The named area is terminated andmarked as stopped.

Programmer responseCheck VSAM error message IEC161I, correct theerror, and follow the appropriate restart procedure.To select the appropriate restart procedure, checkthe Programmer response in messages DFS3702I andDFS2574I, which follow this message.

Related referenceFor information about IEC161IRelated information“DFS2574I” on page 737AREA=aaaaaaaa CLOSED|STOPPED,(RECOVERY NEEDED, RSN=nn)“DFS3702I” on page 1057AREA/ADS OPEN FAILEDREASON CODE=nn message subtext

DFS2570I AREA=areaname DD=ddnameDISCONNECT ERROR

ExplanationThe module DBFMMIT0 was unable to disconnect(close) the data set associated with the identifiedddname. VSAM error message IEC251I was issuedbefore this message.

System actionClose processing is discontinued for the data set.


Programmer responseCheck VSAM error message IEC251I to determine thecause of the error, then run a VSAM access methodservice program to determine if the named ADS isusable. If the named ADS is not usable, run the DEDBCreate utility or the Database Recovery utility.

Related referencez/OS: IEC251I

DFS2571I (ccccffss) AREA=areanameDD=ddname, READ ERROR,CI-RBA=nnnnnnnn, REMAININGEQE=nn, EEQE=nnnn

ExplanationA read error occurred in the data set at controlinterval (CI) RBA nnnnnnnn. The error queue element(EQE=nn) represents the number of consecutive readerrors in the data set. The maximum number ofEQEs for read errors is EQE=03. For a single areadata set (SADS), EEQE=nnnn is also displayed inthe message if there are existing EEQEs for writeerrors for the area. The extended error queue element(EEQE=nnnn) represents the number of existing writeerrors for the area. The variable ccccffss representsthe Media Manager error return code used for problemdetermination.

System actionIf the named area did not read the other data sets, thesystem tries to read from other data sets. Otherwise,a status code AO is returned to the applicationprogram. If a permanent I/O error (indicated by aMedia Manager error return code of X'0020FF10'),has not occurred, an MVS SDUMP can be taken tothe SYS1.DUMP data set by the Media Manager FRRroutine or the Fast Path I/O error routine.


http://www-01.ibm.com/support/knowledgecenter/SSLTBW_2.4.0/com.ibm.zos.v2r4.ieam700/iecmsg.htm?lang=en


Operator responseIf the read errors persist, run the DEDB Create utility orthe Database Recovery utility for this area.

Problem determination1, 6, 11, 20. Problem determination is effective whenthe Media Manager return code is not X'0020FF10'.


DFS2572I (ccccffss) AREA=areanameDD=ddname, WRITE ERROR,CI-RBA=nnnnnnnn, REMAININGEQE=nn, EEQE=nnnn

ExplanationA write error occurred in the data set at controlinterval (CI) RBA=nnnnnnnn. The error queue element(EQE=nn) represents the number of write errors inthe data set. The maximum number of EQEs forwrite errors is EQE=10. For a single area data set(SADS), EEQE=nnnn is also displayed in the message.The extended error queue element (EEQE=nnnn)represents the number of existing write errorsfor the area. The variable ccccffss represents theMedia Manager error return code used for problemdetermination.

The error return code of X'40CF4040' indicates awrite error on the coupling facility structure. MessageDFS2830I is issued before this return code.

System actionThe system produces an error queue element (EQE)for multiple area data sets (MADS) and the CI on theerror data set is deactivated. The system producesan extended error queue element (EEQE) for a singlearea data set (SADS) and the CI in error is availablein the IO Toleration (IOT) buffer for the system thatencountered the write error. If a permanent I/O error(indicated by a Media Manager error return code ofX'0020FF10'), has not occurred, a z/OS SDUMP canbe taken to the SYS1.DUMP data set by the MediaManager FRR routine or Fast Path I/O error routine.

Operator responseIf this control interval is critical CI, run the DEDBCreate utility or the Database Recovery utility for thisarea to restart the area with a /START command.

Problem determination1, 6, 11, 20. Problem determination is effectivewhen the Media Manager error return code is notX'0020FF10'.

Related information“DFS2830I” on page 790CF READERROR, RBA rrrrrrrr, AREAareaname,STR strname RC=xxxxxxxxRSN=yyyyyyyy“IMS problem determination” on page 11IMS messages and codes problemdetermination is accomplished by usingprocedures established by IBM.

DFS2573I AREA=areaname, DD=ddname,READ ERROR. CI-RBA=nnnnnnnn

ExplanationA read error occurred in the data set at control interval(CI) RBA nnnnnnnn. An EQE exists for this data set.

System actionA status code AO is returned to the applicationprogram.

Operator responseIf the read errors persist, run the DEDB Create utility orthe Database Recovery utility for this area.

DFS2574I AREA=aaaaaaaa CLOSED|STOPPED, (RECOVERY NEEDED,RSN=nn)

ExplanationWhen the named area is terminated by an area openfailure, a severe I/O error, a /STOP command, or a /DBRECOVERY command, the named area is markedas stopped. If the return code from DBRC indicateda recovery-needed status, that status is added tothe message. If this message is issued during anemergency restart, recovery-needed status is alwaysadded to the message, even though the named areais not registered with DBRC. The following are thereasons (RSN=) for the problem:00

Reason code unavailable for message. This code isthe default.

01VSO area aaaaaaaa had a severe error duringemergency restart.



03Emergency restart could not process areaaaaaaaaa because a severe error had occurred onthe area before failure.

04Area aaaaaaaa must be recovered followingan /ERE COLDBASE command.

05Area open failed during emergency restart.


07Area aaaaaaaa had a read error during emergencyrestart.

08Area aaaaaaaa had a write error duringemergency restart.

09VSO Area aaaaaaaa could not be recovered acrossan XRF takeover because a storage request failed.

10Either Emergency Restart or XRF Takeoverdetermined that DASD writes failed to completefor a unrecoverable DEDB area. The area must berestored from an Image Copy.

12Emergency restart could not process areaaaaaaaaa due to insufficient storage required forthe area private buffer pool.

13During an /ERE or XRF TAKEOVER process, aninconsistency was noted in the VSO options for anAREA. The AREA is stopped. Message DFS2574I isissued with reason code 13. Issue a /START AREAor UPDATE AREA START(ACCESS) command tocorrect the inconsistency.

14An area has been stopped and marked as recoveryneeded due to one of the SVSODR options.These options take effect at emergency restartprocessing for SVSO areas.

15Emergency restart could not process areaaaaaaaaa due to an inconsistency in the SVSOprivate buffer pool. The preceding message,DFS2835I, identifies the inconsistency.

System actionProcessing is terminated for the named area. TheProhibit Authorization flag is set for the database orarea, unless the message is in response to a /DBRcommand that includes the NOPFA option.

Operator responseIf message DFS3712A or message DFS3713Apreceded this message, correct any VSAM errorsbefore restarting the area; then run recovery, ifnecessary.

If the area is indicated as recovery-needed, recoverthe area using the Database Recovery utility beforerestarting the area.

If the area is in recovery-needed status because anextended error queue element (EEQE) still exists,issue a LIST.DBDS command to find the EQERBA.If a write error EEQE with a null EQERBA exists,it was created because IMS lost connectivity withthe coupling facility, causing CASTOUT to fail. Thearea is marked as temporary recover-needed. Whenconnectivity is re-established and CAST is successful,the status is reset. If you find anything other than nullEQERBA, recover the area using the /UNLOCK SYSTEMcommand.

Module:DBFERST0, DBFE2CI0, DBFMOPC0, DBFMLCL0

Related information“DFS2835I” on page 791ERROR IN VSPEC DEDB STMT: statement_textREASON= reason_text“DFS3712A” on page 1067(ccccffss) AREA=areaname DD=ddname READERROR, CI-RBA=nnnnnnnn SEVERE ERROR“DFS3713A” on page 1067(ccccffss) AREA=areaname DD=ddname WRITEERROR, CI-RBA=nnnnnnnn SEVERE ERROR

DFS2575I PROCSEQ IS INVALID FOR DEDBPCB dbdname IN PSB psbname

ExplanationThe PCB for a DEDB DBD identified by dbdname in themessage specified PROCSEQ. This option is not validfor DEDBs.

System actionIMS continues processing the PCB and does notprocess the remaining PCBs in the PSB. The PSB isdeleted from ACBLIB. Normal execution continues andthe return code is set to 8.


Programmer responseCorrect the PROCSEQ parameter on the PCBstatement, run the PSBGEN utility again, and run theACBGEN with a BUILD statement for this PSB.

DFS2576A MEMBER=xxxxxxxx IS EMPTY

ExplanationThe system found member DBFMSDBn in theprocedure library specified by ddname=PROCLIB, butthe member was empty (all blanks). The MSDBparameter of the IMS control region EXEC statementis used to specify the suffix in DBFMSDBn.


Programmer responseDefine MSDBs in member DBFMSDBn correctly in theprocedure library, or correct the suffix on the IMScontrol region EXEC statement.


DFS2577 INELIGIBLE MESSAGE TO FPEXCLUSIVE TRAN ID

ExplanationThe message is multisegment. Fast Path supports onlysingle-segment messages.


Operator response:Reenter the message in the correct format.

DFS2578I ddname OPEN ERROR

ExplanationProgram DBFDBFM0 was unable to open the DCB forthis data set. Possible causes are:

• There is a missing DD statement.• The JCL is incorrect.• A hardware error exists.

System actionOnly one MSDB checkpoint is used if an MSDBcheckpoint data set cannot be opened. No MSDBcheckpoint is taken if both data sets cannot be

opened. The DUMP facility of the MSDBs is canceledif the memory dump data set cannot be opened.

Programmer responseMake sure that a DD statement is present and thatits specifications are correct. If a hardware failure isindicated, rerun the job.

DFS2579I xxxxx TRACKS ALLOCATED FORddname, BUT yyyyy REQUIRED

ExplanationInsufficient direct access storage device space wasallocated for the given data set to hold an MSDBcheckpoint or memory dump.

System actionOnly one or no MSDB checkpoint is used, or thememory dump facility is suppressed.

Programmer responseCorrect the allocation for the given data set and coldstart IMS.


ExplanationThis message contains the MVS SYNAD error messagebuffer.


Programmer responseTry from a different unit, or reallocate the data set onanother direct access storage device.

Related informationDFS2579Ixxxxx TRACKS ALLOCATED FOR ddname, BUTyyyyy REQUIRED

DFS2581I ddname FORMATTED

ExplanationThis message verifies that the given data set wasformatted without errors.

DFS2582I ERROR IN MSDB DUMP DATA SET,DUMP FACILITY CANCELED



ExplanationProgram DBFDBFM0 found an error in the MSDBmemory dump data set. The memory dump facility iscanceled.

System actionSee the message that was issued before this message.

Programmer responseSee the message that was issued before this message.

DFS2584I ERRORS IN MSDB CHKPT DATASETS, NO MSDB CHKPT WILL BETAKEN

ExplanationProgram DBFDBFM0 found errors in the MSDBcheckpoint data sets, and no MSDB checkpoint wastaken.

System actionSee the messages that were issued before thismessage.

Programmer responseSee the messages that were issued before thismessage.

DFS2585I NO MSDBS FOUND-FORMATTINGIGNORED


• Program DBFDBFM0 requested Fast Path keywordMSDBLOAD in an /NRESTART command, but noPROCLIB member was defined in IMS, or

• No DBD exists in ACBLIB for the MSDB.

Message DFS2706A or DFS0579W is issued beforethis message.

System actionThe data sets are not formatted.

Programmer responseIf you want to use MSDBs, make sure that a DBD forthe MSDB exists in ACBLIB, or change the IMS startupprocedure, or do both.

Related information“DFS0579W” on page 206FIND FAILED FOR DDNAME xxxxxxxxMEMBER=yyyyyyyy RC=zz“DFS2706A” on page 768MSDB xxxxxxxx {NOT SPECIFIED AT SYSGEN|HAS NO DBD GENERATED IN ACBLIB|NOTDEFINED AS A MSDB AT DBDGEN}.

DFS2586I ALLOCATION FOR ddname DOESNOT START ON CYLINDERBOUNDARY

ExplanationThe allocation for ddname=bb does not start on thecylinder boundary.

System actionThe data set is not used.

Programmer responseReallocate space for this data set, using SPACE=(CYL,(xx),,CONTIG).

DFS2588W FP WAS DEFINED AS KEYWORD,BUT FP IS NOT INSTALLED

ExplanationFast Path (FP) was defined as a keyword in the IMS fixlist, but Fast Path is not installed.


Programmer responseCheck and correct the DFSFIXnn member in the IMSPROCLIB.


ExplanationProgram DBFDBDL0 could not open the DCB for thisdata set. Possible causes are:


System actionThe MSDB image copy is not loaded.


Programmer responseMake sure that there is a DD statement and thatits specifications are correct. If hardware failure isindicated, rerun the job, using a different unit.

DFS2590I INVALID CHECKPOINT ID FOUNDIN ddname

ExplanationThe checkpoint identification in the MSDB image copycontrol record was not the same as the identificationfrom which the system was restarted. A possible causeis that a wrong checkpoint was entered or the DDstatement points to the wrong data set.

System actionNo MSDB image copy is loaded.

Programmer responseRestart IMS with the correct checkpoint identificationor correct the JCL.

DFS2591I NO MSDB HEADERS FOUND,IMAGE COPY LOAD IGNORED

ExplanationIMS was restarted with no main storage databases(MSDB) from a checkpoint of a system with MSDBs.

System actionNo MSDB image copy is loaded.

Programmer responseIf MSDBs are to be used, change the IMS startupprocedure.

DFS2592I NO MSDBS LOADED DUE TOPREVIOUS ERROR(S)

ExplanationProgram DBFDBDL0 found previous errors, and noMSDBs were loaded.

System actionNone.

Programmer responseSee the messages that were issued before thismessage.

DFS2593I INVALID MSDB HEADER dbdname

ExplanationA change to the system between shutdown and restartcaused an error. The DBD dbdnameindicates the firstDBD in the MSDB checkpoint that does not match theACBLIB.

System actionNo MSDB image copy is loaded, and the MSDBs cannotbe used.

Programmer responseCheck and correct the database name, segmentlength, or length of the data area. Make sure that noother changes were made to the DBD specified in themessage. Also make sure that the ACBLIB has notbeen changed. If it has, restart the system with a coldstart.

DFS2594I NO CONTROL RECORD FOUND INddname RC=XX

ExplanationProgram DBFDBDL0 attempted to load the MSDBimage copy from a data set. However it failed. Thereturn code XX identifies the problem:Code

Meaning01

A data set does not contain an MSDB checkpoint orthe checkpoint was incomplete.

02If the active system is taking the checkpoint,the alternate system cannot use the same MSDBcheckpoint data set. This condition is temporary.

System actionThe system takes action based on the return code:01

No MSDB copy is loaded, and the MSDBs cannot beused.

02The system rereads the MSDB data set every 3seconds until it successfully reads.

Programmer responseTake action based on the return code:


01Make sure that the JCL is correct. Otherwise,restart IMS from another checkpoint data set, ifpossible, or run the MSDB recovery utility to createa new initial load data set, and restart the systemwith MSDBLOAD.

02The system rereads the checkpoint data set. Ifmessage RC=02 is issued only once, no responseis required. If message RC=02 is issued more thanonce, check the status of active IMS. If active IMSis down, or an I/O error occurred on the MSDBcheckpoint data set in active IMS, enter the /STOPBACKUP command to stop the alternate IMS.

DFS2595I MSDB IMAGE COPY LOADED FROMCHKPT DATA SET ddname

ExplanationThis message verifies that the MSDB image copy wasloaded from the checkpoint data set ddnamebb.

DFS2596I I/O ERROR INddname,cc,co,stat,sens,cchhr

ExplanationProgram DBFDBDL0 attempted to read the MSDBcheckpoint data set, and an I/O error occurred. Thefollowing information is given in the message text:cc

The ECB completion codeco

The command code of the CCW that caused theerror

statStatus information

sensSense bytes

cchhrThe disk address where the error occurred

System actionIMS stops the load process, and the MSDBs cannot beused.

Programmer responseTry these steps:

1. Try loading from a different unit.2. Create an initial load data set using the MSDB

Recovery utility and restart the system withMSDBLOAD.

DFS2597I INVALID MSDB POOL LENGTH INddname, IMAGE COPY IGNORED

ExplanationProgram DBFDBDL0 detected a difference in thelengths of the fixed or pageable main storage database(MSDB) pool as specified in the MSDB checkpoint dataset control record and in the ESCD. No MSDBs areloaded from the MSDB checkpoint data set.

System actionProcessing continues except in an emergency restartwhen IMS terminates with abend 0168.

Programmer responseMake sure that no MSDB definitions were changedbetween the IMS shutdown and restart.


DFS2598I (ccccffss) AREA=areanameDD=ddname UNEXPECTED MEDIAMANAGER MMCALL ERROR

ExplanationAn unexpected Media Manager MMCALL erroroccurred because Media Manager used invalidcontrol blocks. The variable ccccffss represents theMedia Manager error return code used for problemdetermination.

System actionAn error from an I/O read request is treated the sameas an error from a physical read I/O. IMS blocks furtheraccess to the failing CI and records the CI-RBA in thesecond CI of the area. The data set remains open, butthe error log (type X'24') is not produced. If the errorresulted from an I/O request for update, IMS closesthe data set and stops the area if the data set is theonly one available in this area. An MVS SDUMP is takento the SYS1.DUMP data set for problem determination.

Operator responseIf the data set is closed but the area is not stopped,run the DEDB Area Data Set Create utility to recoverthe data set. If the area is stopped, run the DatabaseRecovery utility to recover the area.



System programmer responseIf the error persists and if the data set is needed,contact IBM Software Support for additional analysis.

Programmer responseThe application program receives status code AO ifaccess to the failing CI is attempted. The CI can beaccessed after the Database Recovery or DEDB AreaData Set Create utility is run.


Related referencez/OS: Media Manager return codesRelated information“IMS problem determination” on page 11IMS messages and codes problemdetermination is accomplished by usingprocedures established by IBM.

DFS2599I BLDL FAILED FOR RAND. MODULExxxxxxxx DEFINED IN DMCBxxxxxxxx

ExplanationProgram DBFINI24 was not able to find therandomizing module defined at database generationfor the DEDB master control block (DMCB) identifiedby xxxxxxxx.

System actionIMS continues running. However, the defined DMCB isunusable for the present IMS system. Access to thisDEDB results in a status code FH.

Programmer responseTo correct this problem, perform the following steps:

1. Install the missing randomizing module with thecorrect BIND time specification of RMODE in one ofthe searched libraries.

2. Issue the /STO DB or UPDATE DBSTOP(ACCESS) command against the DEDB.

3. Issue the /START DB or UPDATE DBSTART(ACCESS) command against the DEDB toreload the randomizer.

DFS2600A OPEN ERROR FOR DEDB UTILITY,DB xxxxxxxx

ExplanationA SYSIN or a SYSPRINT open error occurred.

System actionThe utility is stopped.

Operator response:See the OS/VS Data Management error messageissued before this message for information to correctthe problem.


https://www.ibm.com/support/knowledgecenter/SSLTBW_2.2.0/com.ibm.zos.v2r2.idar100/mmdi2.htm



DFS2601I DEDB UTILITY xxxxxxxx STARTED,DB xxxx AREA xxxx

ExplanationThe DEDB utility was successfully started in the nameddatabase and area.

DFS2602I DEDB UTILITY xxxxxxxx ENDED,DB xxxx AREA xxxx

ExplanationThe DEDB utility has completed processing in thenamed database and area.

DFS2603A SYSPRINT ERROR FOR DEDBUTILITY

ExplanationAn I/O error occurred in the system output of a utility,as shown in message DFS2604A.

System actionThe utility is terminated.

Programmer responseCorrect the error according to the z/OS DataManagement error message issued before thismessage.

Related information“DFS2604A” on page 745DB xxxx AREA xxxx

DFS2604A DB xxxx AREA xxxx

ExplanationThis message identifies the database and area wherethe I/O error referenced in message DFS2603Aoccurred.


Related information“DFS2603A” on page 745SYSPRINT ERROR FOR DEDB UTILITY

DFS2605I AREA=areaname DD=ddname,ERROR IN RBA OF CI READ, CI-RBA=xxxxxxxx

ExplanationThe relative byte address (RBA) in the buffer, whichwas returned from the VSAM read, is not equal to theRBA requested.

System actionThe buffer is returned, and the data entry database(DEDB) remains available.

Programmer responseCheck the area for valid data in the RBA field of thecontrol interval (CI). An error might have occurredduring an unload or reload operation.

DFS2606I ERROR IN CIDF OF CI READ

ExplanationThe control interval definition field (CIDF) in the buffer,which was returned from the VSAM read, did notindicate a full control interval (CI) for the record sizeof this area.

System actionThe buffer is returned, and the data entry database(DEDB) remains available.

Programmer responseCheck the area for valid data in the CIDF field of theCI. An error might have occurred during an unload orreload operation.

DFS2607I SYSIN I/O ERROR FOR DEDBUTILITY

ExplanationAn I/O error occurred in the SYSIN data set whilerunning a DEDB utility.



Programmer responseTake appropriate action to correct the error; then rerunthe utility.

DFS2608W MSDBS NOT AVAILABLE - NOMSDBCPX DATA SET NAMESFOUND IN CHECKPOINT

ExplanationNo main storage databases (MSDB) were available foruse. During IMS warm restart or emergency restartprocessing, one or more MSDB database definitionswere found in the checkpoint log records. However, thecheckpoint log records did not include the names ofthe MSDB checkpoint data sets (MSDBCPx) from whichIMS loads the MSDBs during restart.

The restart of the previous execution of IMS did notload any MSDBs. MSDB database runtime resourcedefinitions were later added by online change ordynamic resource definition from the CREATE DBor the IMPORT DEFN command. The MSDB runtimeresource definitions were included in the checkpointlog records during system checkpoint, but since therewere no MSDB databases loaded during the previousexecution of IMS, no MSDBs were written to theMSDB checkpoint data sets (MSDBCPx) at IMS systemcheckpoint time.

System actionIMS continues processing, but no MSDB databases areavailable for use.

Programmer responseTo make the MSDB databases available for use,cold start or warm restart IMS with the MSDBLOADkeyword. This loads the MSDB databases from theMSDBINIT data set. The MSDBINIT data set mustinclude MSDB databases for all newly created MSDBresources.

Module:DBFINI21

DFS2609 CONTROL BLOCK ERRORS.CONVERSATION TERMINATED.

ExplanationAt the end of a warm or emergency restart, theIMS control blocks related to IMS conversations arevalidated. However errors were found; IMS terminatedthe affected conversations.

One or more IMS conversations were terminatedbecause of invalid control blocks. IMS writes an X'3C'log record containing diagnostic information.

System actionRestart processing continues.


Module:DFSCFIX0


DFS2610 MSG-Q ERRORS FOUND/CORRECTED. MSG MAY BE LOST.

ExplanationModule DFSQFIX0 detected invalid data orinconsistencies, or both, between messages andcontrol blocks in the message queues and made thequeues valid. The process might have caused somemessages or conversations, or both to be lost.

System actionThe invalid data, corrected control blocks, and anypurged messages were written to the IMS log.Processing continues with the corrected queues.

Problem determination:1, 5, 25, 26, 36 (if conversations are involved)


DFS2611I COMMAND NAME NOT FOUND

ExplanationThe program looked for a DEDB utility command name.However, there was no command name on the inputline, or the program could not find the name in its tableof valid command names.

System actionThe DEDB utility program stops scanning the currentinput line. Further processing is as specified by theuser in the ERRORACTION command.


Programmer responseCorrect the DEDB utility input, and rerun the DEDButility.

DFS2612I OPERAND DATA LEFT OVER

ExplanationThe program has processed all the operands itexpected for this command. However, there was stillmore operand data on the input line.



DFS2613I UNABLE TO INTERPRET OPERAND

ExplanationThe operand field was omitted, or it was supplied butwas not recognized as any of the valid choices for thiscommand.


Programmer responseCorrect the DEDB utility input. Then rerun the DEDButility.

DFS2614I UNUSABLE NAME

ExplanationThe program scanned a name to be used with theoperating system. The name that the program foundwas not usable for one of the following reasons:

• The name was longer than 8 characters• The first character was not alphabetic• One of the later characters was not alphanumeric.



DFS2615I UNABLE TO CONVERTSEQUENTIAL DEPENDENTADDRESS

ExplanationThe program expected a sequential dependentaddress in hexadecimal, in the form X"hex digits". TheX or the starting quotation mark was missing.



DFS2616I UNABLE TO RECOGNIZEKEYWORD

ExplanationThe program looked for a keyword, followed byan equal sign. One of the following problems wasencountered:

• The keyword was missing.• The keyword was not in the table of keywords for

this command.• The equal sign was missing.



DFS2617I UNABLE TO FIND STARTINGQUOTE


ExplanationThe program was unable to find a string in quotationmarks.



DFS2618I UNABLE TO SCAN FIELD VALUE

ExplanationThe program looked for a value specification of theform C"characters", X"hex digits", or P"decimal digits".The first character was not a C, an X, or a P; or thesecond character was not a quotation mark.



DFS2619I UNABLE TO SCAN FULLWORDVALUE

ExplanationThe program tried to scan a 32-bit value. The fieldwas omitted, or the field began with an X without afollowing quotation mark.



DFS2620I UNABLE TO FIND ENDING QUOTE

ExplanationThe program scanned a value that started with aquotation mark and expected it to end with a quotationmark. However, the end of the operand field wasencountered first.



DFS2621I VALUE IS TOO LARGE

ExplanationThe program found too many characters of input, ortoo many bits were evaluated to fit into the space thatwas set aside to store this value.



DFS2622I CHARACTER NOT RECOGNIZED ASHEXADECIMAL DIGIT

ExplanationThe program recognizes the decimal digits 0 through 9and the uppercase letters A through F as hexadecimaldigits. Some other character were found as part of ahexadecimal field.




DFS2623I CHARACTER NOT RECOGNIZED ASDECIMAL DIGIT

ExplanationThe program scanned a decimal value, but one of thecharacters was not a decimal digit.



DFS2624I UNABLE TO HANDLE FIELD OFLENGTH ZERO

ExplanationThe input contained a specification with nothingbetween the quotation marks, such as X' ' or C' '. Theprogram needs at least one character of data, as inX'3'.



DFS2625I COMMA OR BLANK IS EXPECTED.

ExplanationThe program reached the end of an operand field, andit expected to find a blank or a comma. The commashows the presence of another operand. The errormight be in the previous operand, or in the delimiter.



DFS2626I THIS SPECIFICATION CANNOT BECHANGED

ExplanationThe program encountered a TYPE command afterthe utility type had already been specified. Theprogram cannot change utility types. The DEDButility program stops scanning the current input line.Further processing is as specified by the user in theERRORACTION command.


DFS2627I ERROR IN INITIALIZINGXCI RANDOMIZER, rrrrrrrr,FOR DEDB=dddddddd,RETURN CODE=xxxx, REASONCODE=yyyyyyyy

ExplanationAn error was detected during the initialization call toan Extended Call Interface (XCI) randomizer routine.Both the return code and reason code are specific toyour initialization routine.

System actionThe randomizer is deleted from storage.

Programmer responseCorrect the initialization routine and reissue the /START DB or UPDATE DB START(ACCESS)command for the DEDB.

Module:BFDBAC0, DBFINI24, DBFMSIU0

DFS2628I ERROR IN TERMINATINGXCI RANDOMIZER, rrrrrrrr,FOR DEDB=dddddddd,RETURN CODE=xxxx, REASONCODE=yyyyyyyy

ExplanationAn error was detected during the termination call to anExtended Call Interface (XCI) randomizer routine. Boththe return code and reason code are specific to yourtermination routine.

System actionThe randomizer is deleted from storage.


Programmer responseCorrect the termination routine for subsequent /DBRDB or UPDATE DB STOP(ACCESS) commands to theDEDB.

Module:DBFARD30, DBFMSIU0

DFS2629A DELETE: INVALID SDEP CI PACICOUNT

ExplanationThe Database Delete utility running with the V5COMPkeyword specified has reached a preallocated SDEP CI(PACI) count that is unexpected when attempting tologically delete the current CI. In this case, DFS2630Icould not be issued.

• If QUITCI was used on the Database Scan utility,this message indicates that the DELETE utility wasrun previously with a STOP value that advanced thecurrent CI as far as possible on the high water mark(HWM) owning partner without any further SDEPinserts having taken place on that partner to create anew PACI set.

• If QUITCI was not used on the Database Scan utility,this message indicates that the DELETE utility wasrun previously with a STOP value that advancedthe current CI as far as possible on the non-HWMowning partners without any further SDEP insertshaving taken place on those partners to create newPACI sets.

System actionThe utility terminates. A STATUS UL is issued alongwith message DFS2662A.

Programmer responseTo complete the utility operation, perform one of thefollowing actions:

• Use the QUITCI option of the Database Scan utility tocause the IMS partners to release their current andpreallocated CIs before running the DELETE utility.

• Wait until SDEPs are inserted before running theDELETE utility again.

Module:DBFCSTS0

Related information“DFS2662A” on page 759UTILITY NOT EXECUTED AS REQUESTED

DFS2630I DELETE: V5COMP MOVED OFFCURRENT CI

ExplanationThe Database Delete utility, running with the V5COMPkeyword specified and a STOP value that is greaterthan the current CI, has logically deleted the existingcurrent CI and established a new one.



Module:DBFCSTS0

DFS2631A PARTNER CURRENT CI NOT LESSTHAN HWM FOR AREA = areaname

ExplanationA must-not-occur condition was detected by a datasharing partner. The SDEP utility function to QUITCI isnot performed by the IMS issuing this message and aSTATUS UL is issued by the SDEP utility.

System actionThe utility is terminated for this area.

Operator responseIf this problem is not a user error, call IBM SoftwareSupport for assistance.

Programmer responseCheck the SDEP utility control statements and try thecommand again.


Module:DBFCSTS0


DFS2632A STOPRBA VALUE LESS THAN SDEPLOGICAL BEGIN FOR AREA =areaname


ExplanationThe specified RBA value for the STOPRBA parameter inthe sequential dependent (SDEP) utility using V5COMPwas less than the SDEP logical begin CI RBA. TheIMS detecting the problem issues this message anda STATUS UL is issued by the SDEP utility.

System actionThe utility is terminated for this area. This message isaccompanied by STATUS UL and message DFS2662A.

Programmer responseCheck the SDEP utility control statement for STOPRBA.

Module:DBFCSTS0


DFS2632I REDO SKIPPED FOR DB dbnameAREA areaname AREA NOT FOUNDIN ACBLIB

ExplanationRestart found database updates to this area, but itwas not able to validate because these updates needredo. There is no subsequent log TYPE5926 record orTYPE5927 record to indicate that the area has beendeleted by OLC. This condition occurs if the user haschanged the IMS block structure since the specifiedcheckpoint was taken.

The area specified in this message is marked asrecovery needed in DBRC.

System actionI/O redo and restart continue.

Programmer responseEnsure that there is no data integrity problem, causedby the user changing the IMS block structure since thespecified checkpoint was taken.

Module:DBFERS10

DFS2633I DMAC SYNCHRONIZATIONREJECTED FOR AREA=areaname

ExplanationDMAC synchronization was rejected because theDMAC offset was invalid.



Module:DBFCSTS0, DBFDMAC, DBFNCBS0

DFS2634I AREA=areaname HWM CI OWNED,SDEP HARDENED LOCALLY

ExplanationWhen SDEP SCAN/DELETE runs, sharer needs toharden update buffers. When SDEP SCAN/DELETE hasQUITCI in SYSIN, but the sharer does not own HWM CIand RBA of HWM CI is greater than the one of currentCI, this message is written on the sharer.



DFS2635I AREA=areaname HWM CIHardened Remotely

ExplanationThis message is issued when the SCAN or DELETEutility runs on non-HWM-owned partners.



DFS2636I AREA=areaname PARTNER QCIFREE LOCKS

ExplanationThis message is written when I/O request of FP utilitydetects CI locks on preallocated CIs.




DFS2637I DEFAULT DELETE WITH V5COMPFREES PARTNER QCI LOCKSDELETE + V5COMP + SHAREDAREA: FORCED QCI

ExplanationThe SDEP Delete utility with V5COMP specified wasgiven no STOP value. Consequently, the default endbecame the stopping point and all partners have theirpreallocated and current SDEP CIs logically deleted.



Module:DBFUMDL0, DBFUMRT0

DFS2638I THERE ARE NO CIS TO DELETE

ExplanationProgram DBFUMDLO, the SDEP Delete utility, found nosequential dependent (SDEP) segments in the area todelete. Segments can exist in buffers, but if they arenot written to DASD, the segments are not eligible fordelete processing.

System actionThe Delete utility continues processing normally.


DFS2639I SDEP CI LOCKED, CI xxxxxxxxSKIPPED

ExplanationProgram DBFUMRI0, the Area Data Set Create utility,attempted to access a CI that is currently locked andunavailable. The CI is written to both area data setswhen the data is committed.

System actionThe Area Data Set Create utility continues processingnormally.


DFS2640A I/O ERROR IN ddname OUTPUTDATA SET

ExplanationProgram DBFUMCL0 attempted to close the DCB forthis scan utility data set and an error occurred.


Operator responseCorrect the error and rerun the job.

Programmer responseTo determine the cause of the error, check the z/OSaccess methods error message issued before thismessage.

Module:DBFUMCL0, DBFUMMS0

DFS2641A UTILITY ERROR

ExplanationThe DEDB utility attempted to free space. The requestwas rejected.

System actionThe utility is terminated for this area.

Operator response:If this problem is not a user error, call IBM SoftwareSupport.

Programmer responseCheck whether an exit routine in the Delete utilityactivated the utility.

DFS2642I NUMBER OF CI'S FORSEQUENTIAL DEPENDENTSEGMENTS xxxxxxx

ExplanationThis message shows the space allocated forsequential dependent segments for the area in use.

DFS2643I NUMBER OF CI'S USEDBY SEQUENTIAL DEPENDENTSEGMENTS xxxxxxx


or

DELETE STOPPED PREMATURELY ON CI OWNED BYPARTNER id

ExplanationThere are two forms of this message.

The first form of the message shows the numberof control intervals (CIs) used by the sequentialdependent segments listed in the message text.

The second form of the message is issued only if aDEDB Sequential Dependent Delete utility does notdelete up to the user-specified CI RBA or the defaultCI RBA.

Processing of the DEDB Sequential Dependent Deleteutility stopped because the identified IMS sharingpartner holds an SDEP CI. This situation can occurwhen:

• A partner IMS failure retains a CI for its emergencyrestart.

• A partner IMS is not inserting SDEP segments intothe area at a rate that fills the preallocated CIencountered by the Delete utility.

• A program or transaction is stopped after an abend.

System actionUtility processing stops.

System programmer responseDetermine why the partner is holding the CI. Issuea /DISPLAY AREA or QUERY AREA command toshow the SDEP CI utilization for one partner. TheIMS partner might be waiting for some resource (forexample, a log data set, a resource with which toschedule a program, a DBRC request, or a lock). Thehardware and operating system on which the IMSpartner is executing might be constrained or not havesufficient capacity to keep up with the rest of thesharing group.

To make the CIs following the held CI available to theDelete utility, you can take one of these actions:

• Use the QUITCI option of the Database Scan orDelete utility to cause the IMS partner that owns theCI to release the CI.

Make sure that any SDEP segments contained in thisCI are retrieved by the SCAN utility and put in anoutput file before rerunning the DELETE utility afterthe QUITCI option was used.

Attention: After a CI is deleted, any data thatit contained is not accessible.

• Wait until the partner releases the CI and run theDelete utility again.

DFS2644I NUMBER OF CI'S NOT USEDBY SEQUENTIAL DEPENDENTSEGMENTS xxxxxxxx

ExplanationThis message prints the number of control intervals(CIs) that are not used by the sequential dependentsegments listed in the message text.

DFS2645I UTILITY STOP CI RBA xxxxxxxxyyyyyyyy

or

UTILITY STOP SEG TS clock value

or

UTILITY STOP USEDCI xxxxxxxx yyyyyyyy

or

UTILITY STOP io/ci# xxxxxxxx yyyyyyyy

or

UTILITY STOP SEGEND xxxxxxxx yyyyyyyy

ExplanationThe sequential dependent utility stopped processingat time stamp xxxxxxxx yyyyyyyy. The reason the utilitystopped processing is based on one of the following:

SCAN

• UTILITY STOP CI RBA is the cycle count andcontrol interval (CI) boundary where the SCANstopped.

• UTILITY STOP SEG TS is the time stampassociated with the SCAN stoppage.

• UTILITY STOP SEGEND is the cycle countand RBA of the last SDEP (non-dummy) datasegment read by the SCAN.


• UTILITY STOP USEDCI is the cycle count and CIboundary that SCAN encountered as not markedfull. If QUITCI is not specified, SCAN does not gopast this CI.

• UTILITY STOP io/ci# is the number of I/Ooperations performed and the number of CIsprocessed.

DELETE

• UTILITY STOP CE RBA is the cycle count andRBA of the CI boundary where the DELETEstopped.

• UTILITY STOP SEG TS is the time stampassociated with the DELETE stop time plus 3microseconds.

• UTILITY STOP io/ci# is the number of I/Ooperations performed and the number of CIsprocessed.

System actionThe utility completes normally.


Module:DBFUMPR0

DFS2646A OPEN ERROR FOR ddnameOUTPUT DATA SET

ExplanationProgram DBFUMOP0 attempted to open the DCBfor this scan utility data set and an error occurred.Possible causes are:

• There is a missing DD statement• The JCL is incorrect• A hardware error exists• SYSOUT was specified for SCANCOPY


Operator responseCorrect the error and rerun the job.

Programmer responseTo determine the cause of the error, check the z/OSaccess methods error message issued before thismessage.

Module:DBFUMOP0, DBFUMMS0

DFS2647I SEGMENTS EXPANDED WITHexitname EXIT: nnnnnnnn

System actionExecution normal, expanded compressed segmentswith exit.


Module:DBFUMSC0

DFS2648A PAGE FIX NOT POSSIBLE

ExplanationProgram DBFUMOP0 was unable to page fix becausenot enough space was available in the CSA.

System actionThe utility is terminated for the current area.

System programmer response:Rerun the job at a time when the CSA requirements inthe system are lower.

DFS2649I NUMBER OF SEGMENTS SCANNEDIN areaname = nnnnnnnn

ExplanationThe Sequential Dependent Scan utility has retrievedthe number of SDEP segments specified in themessage (nnnnnnnn).

System actionThe utility completes normally.


Module:DBFUMSC0

DFS2650A AREA xxxxxxxx DOES NOT EXIST

ExplanationYou specified an area name that does not exist in thedatabase.


System actionThe utility is not invoked for this area.

Programmer responseCorrect the parameter statements, and rerun the job.


Chapter 57. DFS messages, DFS2651A - DFS2700A


DFS2651A OTHER UTILITY ACTIVE IN AREAaaaaaaaa

ExplanationProgram DBFUMRT0 could not be started becauseanother utility, HSSP, or VSO preloading was active forthe same area.

System action:The utility was not invoked for this area.

Operator responseRerun this utility when the other utility, HSSP, orVSO preloading has finished processing the area.This message might also be issued if a previousutility did not complete successfully. If this situationoccurs, issue a /STOP AREA or UPDATE AREASTOP(SCHD) and a /START AREA or UPDATE AREASTART(ACCESS) for the area to allow the requestedutility to run.

Module:DBFUMRT0

DFS2652A REORGANIZATION HAS TO BERESTARTED IN AREA xxxxxxxx

ExplanationA Reorganization utility terminated abnormally in thisarea.


Programmer responseRun a Reorganization utility.

DFS2653I UTILITY IN AREA=areanamePREVIOUSLY ABNORMALLYTERMINATED

or

UTILITY IN AREA=areaname STILL ACTIVE DURINGSHUTDOWN

ExplanationThe first form of the message indicates that apreviously run Scan, Delete, Compare, or Create utilityabnormally terminated in the named area. This form ofthe message is for information only.

The second form of the message indicates thatHSREORG or HSSP is active for the area duringshutdown. Shutdown waits for the utility to terminate.If shutdown completes, the message is for informationonly. If shutdown does not complete, a utilityterminated abnormally for the area, but the utility wasnot rerun to complete cleanup.

System actionFor the first form of the message, the Fast Path utilitybeing used continues execution with the next area.

Programmer responseIf you received the second form of the message andshutdown did not complete, cancel IMS and do anemergency restart.

DFS2654A CHANGE OF UTILITY FOR THISAREA

ExplanationA run in different areas must be made with one utilitytype only.


Programmer responseCorrect the control statements, and rerun the job.

DFS2655A OPEN FAILED FORAREA=areaname

ExplanationAn open error occurred in the named area whilethe Fast Path Base Module utility, DBFUMRT0, wasrunning.

System action:The Fast Path Base Module utility is stopped for thenamed area.


System programmer response:Check message DFS3702I to find the reason for theerror. After correcting the error, rerun the job.

Related information“DFS3702I” on page 1057AREA/ADS OPEN FAILEDREASON CODE=nn message subtext

DFS2656A INVALID DISCONNECT CALL

ExplanationProgram DBFUMRT0 tried to disconnect an area thatwas not connected.

Programmer responseAn error occurred previously. Correct that error, andrerun the job.

DFS2657I UTILITY EXECUTED ASREQUESTED

or

UTILITY EXECUTED AS REQUESTED VSPECSDEPQCI STATEMENT FORCED QUITCI

ExplanationThis message verifies that no errors were detectedduring the utility run.

DFS2658A WRONG PROGRAM NAME

ExplanationAn invalid parameter was used with the TYPE macro.



DFS2659A xx UNEXPECTED RETURN CODE,yy

ExplanationThe Fast Path Base Module utility (DBFUMRT0) madea positioning ('POS') call and received a non-blankstatus code (xx). In the message text, yy is the FastPath status code.

You can receive this message when you run theSDEP scan or delete utility, but you have incompatiblecombinations of parameters or a missing SDEP SCAN/DELETE card. For example, if you have STARTROOTdefined, but STOPROOT was not specified, orSTOPSEQ was specified and V5COMP was notspecified.

System actionThe utility is not invoked for the requested area.

Programmer responseCheck the positioning status codes for an explanation.Correct the error, and rerun the job.

Related referenceFast Path utility status and reason codes(Messages and Codes)

DFS2660A ROOT SEGMENT HAS NOSEQUENTIAL DEPENDENTSEGMENTS

ExplanationIMS was unable to determine the processing limits.


Programmer responseCorrect the parameter input, using only root segmentswith sequential segments.

DFS2661A INVALID VALIDATION CALL, CODExx

ExplanationIMS Fast Path attempted to validate the inputparameter for the Fast Path utility program being usedand discovered an error. There was a previous error(no code printed) or a parameter error concerningexisting processing limits.

System actionThe Fast Path utility being used is not invoked on thisarea.



http://www.ibm.com/support/knowledgecenter/SSEPH2_15.1.0/com.ibm.ims15.doc.msgs/compcodes/ims_fastpathstatuscodes.htm#ims_fastpathstatuscodes


DFS2662A UTILITY NOT EXECUTED ASREQUESTED

ExplanationAn error prevented the utility from executing.

Programmer responseCorrect the environment error, resubmit the job, andcheck the ADS status in LIST.RECON:

• If the shadow ADS is not changed to active ADS,correct the environment error and resubmit the job.

• If the shadow ADS is changed to active ADS, it isimpossible to rerun.

• If all new active ADSs are made unavailable, recoverthe ADS from the Shadow Image Copy data set byusing the USEAREA option.

DFS2663A SYSIN RECORD SIZE EXCEEDSMAXIMUM LIMIT OR RECORDFORMAT NOT ALLOWED

ExplanationYou specified a record size that exceeded themaximum limit of 120, or specified an invalid recordformat.

System actionThe utility is not started for this area.

Programmer responseCorrect the SYSIN DD statement, and rerun the job.

DFS2664A UNIT OF WORK NUMBER NOTWITHIN LIMITS OR LOGICALORDER

ExplanationThe parameter specifying the unit-of-work limits forthe reorganization utility had one of the followingerrors:

• The upper limit was lower than the lower limit.• The limits in the DBD were not consistent with the

area description.• More than one STARTUOW or STOPUOW wasspecified within one request.



DFS2665I UTILITY SKIPPED IN AREAxxxxxxxx DUE TO RESTARTREQUEST

ExplanationYou requested to skip this area because of a restartrequest.


DFS2666A WRITE ERROR ON SCANIDT DATASET

or

WRITE ERROR ON SCANCOPY DATA SET

ExplanationProgram DBFUMSC0 was unable to write to the scandata set.

System actionThe Scan utility is stopped.

Operator response:Correct the error, and resubmit the job.

Programmer responseTo determine the cause of the error, check the z/OSdata management error message issued before thismessage.

DFS2667A xx STATUS FROM I/O PROCESS INAREA

ExplanationA Fast Path utility encountered the condition definedby the status code xx, while processing a database.

System actionThe utility is stopped for this area.


Operator responseTake the appropriate action according to the z/OSData Management error message issued before thismessage. For more information, refer to the Fast Pathutility status codes and the z/OS data managementerror message, if one was issued before this message.


DFS2668A OUTPUT TOO LONG FOR SCANBUFFER

ExplanationThe message returned to the user was too long.

System actionThe utility is stopped for this area.

Programmer responseCorrect the exit routine.

DFS2669A GET AREA LOCK FAILED,AREA=areaname

Explanation:An area lock request failed while processing an areaconnect call from DBFUMRT0. STATUSUL is set.

System action:The utility terminates and message DFS2662A isissued.

Programmer response:Determine the cause of the error and rerun the utility.


DFS2670I DATA BASE NAME dbnameSPECIFIED FOR FAST PATH DEDBUTILITY IS INVALID

ExplanationThe Fast Path (IFP) region was not initialized becausethe PSB name in the third positional operand wasspecified as DBFFPU0 and the database name in thesecond positional operand of the PARM field on theEXEC control statement was not defined as a DEDB atthe IMS system definition.

System actionThe dependent region is abnormally terminated withabend 0458.

Programmer responseCorrect the database name, and rerun the job.

Problem determination:8, 9, 10, 17d


DFS2671I UNABLE TO UPDATE UTILITYCONTROL DATA: AREA xxxxxxxx,UOW nnnnnnn

ExplanationThe DEDB Direct Reorganization utility, DBFUMDR0,did not release ownership of resources nor update thecount of independent overflow control intervals. Theunit of work number and its area name are provided.

System actionThe DEDB Direct Reorganization utility terminates witha return code of 8. The database is usable.

Programmer responseRestart the utility.

DFS2672A (LOG|CHNG) REQUEST FAILED:AREA xxxxxxxx, UOW nnnnnnn

ExplanationThe DEDB Direct Reorganization utility, DBFUMDR0,was unable to satisfy the indicated internal request.


The area namennnnnnn

The number of the affected unit of work

The LOG request is made at the end of the build phaseto log the "copy phase reached" indicator. The CHNGrequest is made at the end of the copy phase to resetthe "copy phase" indicator.





System actionThe utility terminates with a return code of 24. Thedatabase is not usable.

Programmer responseRestart the utility must at the failing unit of work.

DFS2673I UTILITY STOPPED AFTER AREAxxxxxxxx, UOW nnnnnnn

ExplanationThe DEDB Direct Reorganization utility, DBFUMDR0,was stopped at the request of the operator.


The area namennnnnnn

The last unit of work that was reorganized

System actionThe DEDB Direct Reorganization utility terminates witha return code of 4. The database is usable.

Programmer responseRestart the utility at the next unit of work, if you want.

DFS2674A I/O ERROR OCCURRED WHENATTEMPTING TO WRITE TOAREA=areaname UOW=nnnnnnnnIN (BUILD|COPY) PHASE

ExplanationIn attempting to write onto the area and unit of work(UOW) nnnnnnnn, the DEDB Direct Reorganizationutility, DBFUMDRO, encountered an I/O error.

BUILD in the message text indicates that it wasissued during the build phase of the DEDB DirectReorganization utility. An error occurred while writingon the reorganized UOW. The area is still usable,but all the data sets have unwritten control intervals(CI) with the same relative byte address (RBA) in thereorganized unit of work (UOW) of each data set.

COPY in the message text indicates that it was issuedin the copy phase of the DEDB Direct Reorganizationutility. An error occurred while writing on the originalUOW. The DEDB Direct Reorganization utility continuesits operation for the original UOW.

System actionFor the BUILD phase, the utility terminates. The usercan stop the area and recover it later. For the COPYphase, the utility continues its operation.


You can recover the area after stopping the area.

DFS2675A I/O ERROR OCCURRED WHENATTEMPTING TO READ FROMAREA=areaname UOW=nnnnnnnnIN (BUILD|COPY) PHASE

ExplanationThe DEDB Direct Reorganization utility, DBFUMDR0,attempted to read from the area and unit of work,nnnnnnn, and encountered an I/O error.

BUILD in the message text indicates that this messagewas issued during the build phase of the DEDB DirectReorganization utility. An error occurred while readingfrom the original UOW. The area is still usable, but allthe data sets have unreadable control intervals withthe same relative byte address (RBA) in the originalUOW of each data set.

COPY in the message text indicates that this messagewas issued in the copy phase of the DEDB DirectReorganization utility. An error occurred while readingfrom a reorganized UOW. The system stops the areaand set the area to a recovery-needed status.


Operator responseIn the BUILD phase, you can stop the area and thenrecover it later. After a successful recovery, resubmitthe job. In the COPY phase, you must recover the areaimmediately.

DFS2676A UNABLE TO GET CONTROL OF ARESOURCE FOR AREA xxxxxxxx,UOW nnnnnnn

ExplanationThe DEDB Direct Reorganization utility, DBFUMDR0,was unable to get exclusive control of an independentoverflow control CI.

System action:The utility terminates with a return code of 24.


Programmer responseRestart the utility at the failing unit of work.

Issue /STOP AREA or UPDATE AREA STOP(SCHD)followed by /START AREA or UPDATE AREASTART(ACCESS) before restarting the utility. Ifyou do not issue /STOP AREA, UPDATE AREASTOP(SCHD), /START AREA, or UPDATE AREASTART(ACCESS), message DFS2651A might appearwhen the utility is restarted.

Related information“DFS2651A” on page 757OTHER UTILITY ACTIVE IN AREA aaaaaaaa

DFS2677A UNABLE TO FREE CONTROL OF ARESOURCE FOR AREA xxxxxxxx,UOW nnnnnnn

ExplanationThe DEDB Direct Reorganization utility, DBFUMDR0,attempted to allocate or deallocate independentoverflow space, but was unable to release exclusivecontrol of an independent overflow control CI.

System actionThe utility terminates with a return code of 24. Thedatabase is not usable.

Programmer responseRestart the utility at the failing unit of work.

DFS2678I UNABLE TO ALLOCATESUFFICIENT OVERFLOW SPACEFOR AREA xxxxxxxx, UOWnnnnnnn

ExplanationThe DEDB Direct Reorganization utility, DBFUMDR0,was unable to allocate independent overflow spacefor the referenced unit of work because there was nospace available. The unit of work is not reorganized.

System actionAny independent overflow space allocated to thereferenced unit of work by the utility is freed. Theutility continues to process with the next unit of work.

Programmer responseRerun the utility to reorganize the referenced unit ofwork if sufficient independent overflow space wasfreed by the reorganization of other units of work.

DFS2679A TYPE AND/OR AREA NOTSPECIFIED

Explanationor

TYPE AND/OR AREA, ADDAREA, ALTERAREA,REPLRAND, ALTERDB NOT SPECIFIED

ExplanationAt least one of the following required values was notspecified or has no value:

• Parameter type (AREA or ALTER). If the ALTERtype is specified, a DEDB Alter utility parameter(ALTERDB, ADDAREA, ALTERAREA, REPLRAND)must also be specified.

• DEDB name.

System actionThe utility is not activated for this area.

Programmer responseCorrect the input and resubmit the job.

Module:DBFUMMS0

Related referenceDEDB Alter utility (DBFUDA00) (DatabaseUtilities)


ExplanationThis message contains the MVS SYNAD error messagebuffer.

System actionFast Path is made unavailable if the control records ofthe MSDB checkpoints cannot be read.

Programmer responseTry from a different unit, or copy the data set to adifferent direct access storage device.

Related referencez/OS: SYNADAF error descriptions



http://www.ibm.com/support/knowledgecenter/SSEPH2_15.1.0/com.ibm.ims15.doc.dur/ims_dbfuda00.htm#ims_dbfuda00



ExplanationProgram DBFNRST0 was unable to open the DCB forthis data set. Possible causes are:


System actionThe system tries to open the second MSDB data set.Fast Path is made unavailable if the second openingfails too.

Programmer responseMake sure that there is a DD statement and itsspecifications are correct. If hardware failure isindicated, rerun the job, using a different unit.

DFS2682W MSDBS NOT LOADED DUE TOPREVIOUS ERROR(S)

ExplanationEither program DBFNRST0 found no valid MSDBcheckpoint control record, or other errors as specifiedin messages DFS2780A and DFS2781A previouslyoccurred.

System actionFast Path is made unavailable.

Programmer responseFind out if IMS was cold started without MSDBsspecified. If so, issue the /NRE MSDBLOAD commandon the next warm start to load the MSDBs from theMSDBINIT data set.

Related information“DFS2780A” on page 781CONFLICT WITH PRIOR DATA= KEYWORD.“DFS2781A” on page 781DATA= KEYWORD EXPECTED.

DFS2683I PRELOAD AREA area_nameSTR: structure_name ALTERSUCCESSFUL

ExplanationDuring the preload for a Fast Path shared virtualstorage option (VSO) area, the current structureallocation was not large enough to hold the rootaddressable area (RAA) portion of the area. IMS issued

IXLALTER to increase the structure size. The IXLALTERcall was successful.


Operator responseTo avoid the IXLALTER call for this area, increase theINITSIZE of the structure in the CFRM policy.

Module:DBFVXAS0

DFS2684A PRELOAD AREA area_nameSTR:structure_name ALTER FAILED.RETURN CODE=xxxx REASONCODE=yyyy

ExplanationDuring the preload for a Fast Path shared virtualstorage option (VSO) area, the current structureallocation was not large enough to hold the rootaddressable area (RAA) portion of the area. IMS issuedIXLALTER to increase the structure size. However, theIXLALTER call failed. In the message text, xxxx is theIXALTER return code and yyyy is the reason code.

System actionThe area stopped. then IMS disconnected from thestructure.

Operator responseIncrease the INITSIZE for the structure in the CFRMpolicy, or remove the PRELOAD specification for thearea.

Module:DBFVXAS0

Related referencez/OS: IXLALTER return and reason codes

DFS2685I SDEP DISCREPANCY DURINGRESTART AREA xxxxxxxx - AREASTOPPED

ExplanationDuring an emergency restart, restart log processingfound a problem with the log records relating to thesequential dependents of area xxxxxxxx. Specifically,due to a missing log record, restart log processing wasunable to determine the correct buffer for one or morecommitted SDEP updates.



System actionArea xxxxxxxx is stopped. If the area is registered withDBRC, it is marked as recovery needed.

Programmer responseUse the Database Recovery utility to recover the area.

DFS2686I DDNAME EOF ON OPEN ERROR

ExplanationProgram DBFNRS20 found file DDNAME empty. Thedata set might have been redefined.

System actionThe system closes this data set and tries to open thenext MSDB data set. Fast Path is made unavailable ifall the MSDB data sets fail open or are empty.

Programmer responseFormat the empty MSDB data set or copy from a validMSDB data set.

DFS2687A GETMAIN FAILED, AREA =AREANAME

ExplanationAn IMODULE GETMAIN request failed whileprocessing an area connect call from DBFUMRT0.

System actionThe utility terminates and this message is issued.

Programmer responseDetermine the cause of the error and rerun the utility.

DFS2688I SDEP SCAN UTILITY FOUND RBAxxxxxxxx INDOUBT

ExplanationThe DEDB Sequential Dependent Scan utility found anin-doubt segment in the range of segments requestedto be processed.

System actionThe utility continues.

Module:DBFUMSC0, DBFUMMS0

DFS2689I UTILITY START TIME xxxxxxxxyyyyyyyy

ExplanationThe sequential dependent utility started processing attime stamp xxxxxxxx yyyyyyyy.

System actionThe utility starts normally.


Module:DBFUMSC0

DFS2690I OPEN FAILED DDNAME=xxxxxxxx

ExplanationThe DBFDBDZ0 utility was unable to open theindicated data set.

System actionThe utility terminates and no output is generated.

Programmer responseMake the necessary changes, and resubmit the job.

DFS2691A LOG DATA SET IS INVALID,TERMINATE. CURRENT CHKPTID=xxxxxxx, PROCESSING CHKPTID=xxxxxxx


• Log data set checkpoint IDs were not in ascendingorder.

• The main storage database (MSDB) or extendedcommunications node table (ECNT) definition did notmatch the definition in the MSDBCP1/CP2/DMP dataset.

Two checkpoint IDs are printed. If the IDs are thesame, then the problem is either a mismatch in theMSDB or ECNT definition, or the checkpoint IDs are outof sequence. The second checkpoint ID is the one inerror.

Note: The ECNT definition is the result of theTERMINAL macros in IMS system definition.

System actionThe utility terminates with return code 4. The databaseis not usable.


Programmer responseMake sure that the log data sets are specified in thecorrect sequence, and that all log data sets are fromIMS sessions that have identical MSDB and TERMINALdefinitions.

DFS2692I CKPT/DUMP DATA SET NOT VALIDDDNAME=xxxxxxxx

ExplanationCheckpoint data was specified for the utility, butneither of the two checkpoint data sets was valid. AnIMS startup failure is the probable cause.


Programmer responseIMS must be restarted to obtain valid checkpoint datasets.

DFS2693I INVALID DBDNAME SUPPLIED.DBDNAME=xxxxxxxx.

ExplanationThe DBD name xxxxxxxx was submitted as controlinput to the utility, but there is no MSDB by this namein the primary input file (checkpoint or dump).

System actionThe utility terminates without creating an output file.

Programmer responseCorrect the control input, and resubmit the job.

DFS2694I O/P LRECL INSUFFICIENT TOHOLD RECORD

ExplanationThe logical record length that you specified in theJCL was too small for the utility output data set. Theddname is MSDBINIT.

System actionThe utility terminates, and no output is generated.


DFS2696I MSDB NAME EXCEEDS 8 BYTES

ExplanationAn MSDB name in a control statement was too long.The statement is printed immediately before thismessage.


Programmer responseCorrect the input, and resubmit the job.

DFS2698I INVALID CONTINUATION SYNTAX

ExplanationThe control statement should have a character incolumn 72 and it contained a blank. Alternatively, thefirst 15 columns of a continuation statement containedcharacters and must be blank.



DFS2699I LOG END OF FILE BEFORE IMSSTART CKPT RCD

ExplanationThe utility scanned the log data set for the start ofthe IMS checkpoint. An end-of-file condition occurredbefore the checkpoint was found.


Programmer responseResubmit the job, using an alternate log.

DFS2700A MORE THAN 255 MSDBS DEFINED

ExplanationThe number of possible main storage databases(MSDB) in IMS was exceeded. The maximum numberof MSDBs that can be specified is 255.



Programmer responseReduce the number of MSDBs in MSDB memberDBFMSDBn in the IMS PROCLIB






DFS2701W ERROR ENCOUNTERED DURINGSHARED VSO AREA PRELOAD

ExplanationDuring Fast Path shared Virtual Storage Option (VSO)preload processing, one or more shared VSO areasfailed to load.


Operator response:Identify the failing shared VSO areas with errormessages and take corrective action. MessageDFS2453I or DFS3702I accompanies this messageand helps identify the failing shared VSO and theproblem.

Module:DBFVXPL0

Related information“DFS2453I” on page 705PRELOAD PROCESSING xxxxxxxx FOR aaaaaaaSTR1=strname1; STR2=strname2“DFS3702I” on page 1057AREA/ADS OPEN FAILEDREASON CODE=nn message subtext

DFS2702A GETMAIN FAILED. INSUFFICIENTSTORAGE FOR DMCB/DMACAND/OR BHDR BLOCKS.

ExplanationThe IMS control region did not contain sufficientstorage to build the temporary DMCB/DMAC or BHDRblocks, or both.


Programmer responseIncrease the IMS control region size.


DFS2703A GETMAIN FAILED. INSUFFICIENTSTORAGE FOR FP CONTROLBLOCKS.

ExplanationThere was not enough storage to load and build allof the Fast Path control blocks in the CSA or ECSA.For Fast Database Recovery (FDBR) region, the storageshortage is in ECSA only if FPBUFF=ECSA is specifiedin DFSFDRxx member. Otherwise the storage shortageis in the FDBR region private storage; FPBUFF=LOCALor FPBUFF was not specified in DFSFDRxx member.


Operator response:(master terminal) After increasing CSA or ECSA,restart IMS. For an FDBR region, increase the regionsize if you used extended private to allocate FP controlblocks. Then restart FDBR.

Programmer responseConsult your MVS system programmer. Increase theCSA or ECSA size as needed. If the abend occurredunder FDBR region, the storage shortage might bein ECSA or in FDBR extended private. Verify theoptional FPBUFF parameter in the DFSFDRxx memberof IMS.PROCLIB. If the FDBR region private storageis the problem, the FDBR REGION size should beincreased.

Module:DBFOLC02, DBFINI21, DBFINI23, DBFINI24,DBFINI25, DBFINI26, DBFINI27


DFS2704A BSIZ NOT SPECIFIED

ExplanationThere were DEDBs or MSDBs in use, but no data buffersize was specified.





Programmer responseUpdate the BSIZ parameter in the IMS procedure oroverride the parameter at IMS startup time. If neitheran MSDB nor a DEDB is in use, no suffix for an MSDBcan be defined, and no DBD should be on the IMSACBLIB for any DEDB.


DFS2705A DBBF NOT SPECIFIED

ExplanationThere are DEDBs or MSDBs in use, but no number isspecified for the data buffers.


Programmer responseUpdate the DBBF parameter in the IMS procedure oroverride it at IMS startup time.


DFS2705W DBBF NOT SPECIFIED

or

DBBF SPECIFICATION INVALID, DBBF=10 ISASSUMED

ExplanationYou specified a DBBF value less than 10. That value isnot suitable for using Fast Path. IMS has changed theDBBF value to 10.



Module:DBFINI20

DFS2706A MSDB xxxxxxxx {NOT SPECIFIEDAT SYSGEN|HAS NO DBDGENERATED IN ACBLIB|NOTDEFINED AS A MSDB AT DBDGEN}.


• The MSDB name is specified in the DBFMSDBnmember, but was not defined in the DATABASEparameter at system definition.

• No ACBGEN is done for the MSDB.• The name entry specified in DBFMSDB is not defined

as an MSDB at DBDGEN.

System actionIMS continues running but the named MSDB is markedas not accessible in the first two cases listed above.

If the named entry is not defined as an MSDB atDBDGEN, the entry is ignored.

Programmer responseCheck and correct the IMS system definition or MSDBload determination member DBFMSDBn.

DFS2707W INVALID OTHR VALUE SPECIFIED.SYSDEF VALUE USED.

ExplanationThe OTHR parameter was specified, but not as adecimal value from 1 to the value of the MAXPSTparameter in the control region procedure.


Programmer responseCorrect the OTHR value in the IMS procedure.

DFS2708W NUMBER OF DATA BUFFERSEXCEEDED THE MAXIMUMALLOWED FOR THE SPECIFIEDBSIZ. DBBF HAS BEEN ADJUSTED.

ExplanationThe DBBF parameter in the IMS startup procedureexceeded the maximum value based upon BSIZ. DBBFis adjusted to the maximum allowed value for thespecified BSIZ as specified in the following table:

BSIZ (buffer size)Maximum number ofbuffers

512 1,800,000

1,024 1,200,000

2,048 780,000




BSIZ (buffer size)Maximum number ofbuffers

4,096 440,000

8,192 230,000

12,288 160,000

16,384 130,000

20,480 100,000

24,576 80,000

28,672 70,000


Programmer responseCorrect the DBBF value in the IMS procedure.

DFS2709W UNABLE TO INITIALIZE ANY DEDBAS SPECIFIED.

ExplanationBecause of previous errors no DEDBs (or MSDBs) wereinitialized.


Programmer responseIf DEDBs (or MSDBs) are required, shut downIMS, correct any errors indicated by previous errormessages, and restart IMS.

DFS2710W DBFX GREATER THAN DBBF, ORDBFX LESS THAN 10. DBFX=10 ISASSUMED.

ExplanationThe number of data buffers, page fixed at regionstartup, exceeded the number of data buffersavailable. Alternatively, the page fixed data buffer wasspecified as less than 10 and the number of databuffer was greater than 0. The DBFX value is set to10. In addition, if the number of data buffers availablewas less than 10, DBBF=10 was assumed.


Programmer responseCorrect the DBFX parameter in the IMS procedure.

DFS2711A BSIZ VALUE WRONG

ExplanationThe BSIZ value specified in the IMS startup procedureis invalid. The data buffer size (BSIZ) must be amultiple of 4 KB unless the BSIZ value is 512, 1024, or2048. The maximum BSIZ value is 28 672.


Operator response:(master terminal) Restart IMS.

Programmer responseCorrect the BSIZ parameter value in the IMSprocedure.


DFS2712I MODULE NAME: module_namecommentary_from_the_moduleABEND SUBCODE:hex_subcode register_dumpdump_of_storage_area AREANAME: area_name

ExplanationThis message accompanies abend 1026 and providesdebugging data for conditions.

In the message text:module_name

This field contains the name of the module thatdetected the problem, and issued the DBFDEBUGrequest.

commentary_from_the_moduleThis commentary usually describes the nature ofthe difficulty.

hex_subcodeIf present, this subcode identifies the type of errorthat caused the program to terminate abnormally.For a description of the subcodes, see the abendinformation.

register_dumpThis memory dump contains the registers of themodule that issued the debugging request.



dump_of_storage_areaThis memory dump describes the control blockrelated to the logical inconsistency.

area_nameName of area that was being processed when theabnormal condition was detected.

System actionProcessing continues or abend 1026 occurs.

Problem determinationControl blocks in the Fast Path region memory dumpare immediately preceded by the appropriate EBCDICeye catchers. For security reasons, the buffer datadoes not normally appear in a memory dump. If youwant a diagnostic copy of the buffer data printed inthe memory dump, use SUPERZAP to reset the flagcalled MAYBE from its normal value of X'FF' to X'00' inmodule DBFACDI0.

In addition, problem diagnosis can be done with theregister contents and a listing of the module thatissued the DBFDEBUG request.

The information for abend 1026 contains moredetailed diagnostic information.



ExplanationProgram DBFDBDP0 was unable to open the DCB forthis data set. Possible causes are:


System actionNo MSDB checkpoint or memory dump is created.

Programmer responseMake sure that a DD statement is present and itsspecifications are correct. If a hardware error isindicated, rerun the job, using a different unit.

DFS2714I xxxxx TRACKS ALLOCATED FORddname, BUT yyyyy REQUIRED

ExplanationInsufficient direct access storage device space wasallocated for this MSDB checkpoint or memory dumpdata set.

System actionNo checkpoint or memory dump is created.

Programmer responseReallocate the data set, and cold start IMS.

DFS2715I NO MSDBS FOUND-MSDB DUMPIGNORED

ExplanationA memory dump request was entered with a /DBDUMPcommand but the system had been started with noMSDBs.

System actionThe MSDB memory dump is ignored.

DFS2717 MSDB CHKPT IN PROGRESS,CANNOT PROCESS COMMAND

ExplanationAn MSDB checkpoint from a previously enteredcommand or an automatic system checkpoint iscurrently in process.


Operator response:(master terminal) Wait for message DFS2719I to bedisplayed, and reenter the command.

Related information“DFS2719I” on page 771MSDB CHECKPOINT WRITTEN TO ddname

DFS2718I ERRORS IN MSDB CHKPT DATASET, NO SYSTEM/MSDB CHKPTTAKEN

ExplanationProgram DBFDBDP0 found errors in one of the mainstorage database (MSDB) checkpoint data sets, and noMSDB checkpoint is taken.



System actionNo further checkpoint (system and MSDB) is takenexcept for a shutdown checkpoint, if requested. NoMSDB checkpoint are taken as part of the shutdowncheckpoint.

Operator responseIf a write error occurs in one of the MSDB checkpointdata sets in the initial checkpoint after the IMS restart,and the restart checkpoint is written to the OLDS, theMSDBs cannot be recovered in an emergency restart.If this problem occurs during restart, take action B.Otherwise, you can take either of these actions:

A. Recovery through an emergency restart action:

1. Force termination of IMS by issuing a MODIFYIMS,STOP command.

2. Scratch the failing MSDB checkpoint data set,and reallocate a new data set.

3. Copy the valid MSDB checkpoint data set to thenewly allocated data set.

4. Emergency restart the system from the lastvalid system checkpoint.

B. Recovery through a warm start action:

1. Shut down IMS. Message DFS2762A should beexpected.

2. Follow the actions documented in messageDFS2762A.

Related information“DFS2762A” on page 779SYSTEM SHUTDOWN-MSDB RECOVERYREQUIRED

DFS2719I MSDB CHECKPOINT WRITTEN TOddname

ExplanationThe MSDB checkpoint was written to ddname.

DFS2720I I/O ERROR INddname,cc,co,stat,sens,cchhr

ExplanationProgram DBFDBDP0 attempted to write to an MSDBcheckpoint and an I/O error occurred. The followinginformation is given in the message text:Field

Contentscc

The ECB completion code

coThe command code of the CCW where the erroroccurred

statStatus information

sensSense bytes

cchhrThe disk address where the error occurred

Message DFS2718I is also issued.

System actionThe MSDB checkpoint is stopped.

Programmer responseShut down IMS and emergency restart the systemfrom the last valid system checkpoint.

Related informationDFS2718IERRORS IN MSDB CHKPT DATA SET, NOSYSTEM/MSDB CHKPT TAKEN

DFS2721I MSDBS SUCCESSFULLY DUMPED

ExplanationThis message verifies that the MSDBs were dumpedsuccessfully.

DFS2722I ERROR IN MSDB DUMP-NO DUMPTAKEN

ExplanationProgram DBFDBDP0 discovered an error in the MSDBmemory dump.

System actionThe memory dump is terminated and no furthermemory dump is created.

Programmer responseTry a different unit or copy the data set to anotherdirect access storage device.

If the new active IMS system receives this messagein an XRF environment, the operator might not haveentered the 'MD' option for the FORMAT keyword inthe /ERE command for the IMS alternate system.

DFS2723I UNABLE TO OPEN DD=LOGTAPE.ANALYSIS TERMINATED.


ExplanationA permanent I/O error might have occurred whileopening the input log data set, which resides on tapeor DASD.

System actionThe IMS Fast Path Log Analysis utility, DBFULTA0,terminates.

Programmer responseEnsure that the LOGTAPE ddname is allocatedproperly.

DFS2724I MORE THAN 100 TRANSACTIONCODES SPECIFIED FOREXCEPTIONAL TRANSIT TIME.EXCESS IGNORED.

ExplanationMore than 100 statements were read from the SYSINdata set specifying exceptional transit times fortransaction codes. A maximum of 100 specificationstatements is permitted.

System actionExecution continues and the excessive transit-timespecifications are ignored.

Programmer responseRemove the excessive transit-time specificationstatements from the SYSIN data set, and resubmit thejob.

DFS2725I UNABLE TO OBTAIN ADDITIONALVIRTUAL STORAGE. ANALYSISTERMINATED.

ExplanationMore virtual storage than was available was requiredfor the job.

System actionModule DBFULTA0 terminates prematurely, presentingany summary reports prepared to the time of thefailure.

Programmer responseAllocate more virtual storage space, and resubmit thejob.

DFS2726I PARAMETER CARD FORMATINCORRECT, VALUE NOT USED.

ExplanationThe format of a parameter statement in the SYSINdata is incorrect.

System actionThe statement is skipped, the data is not used, andprocessing continues.

Programmer responseCorrect the format of the parameter statement andresubmit the job. See the description of the formats tobe used for module DBFULTA0.

Related referenceFast Path Log Analysis utility (DBFULTA0)(System Utilities)

DFS2727I LOG BUFFER CONTROL RECORDNOT FOUND ON INPUT LOG.ANALYSIS TERMINATED.

ExplanationThe IMS Fast Path Log Analysis utility, DBFULTA0, wasunable to find the IMS log buffer control record on thedata set specified by LOGTAPE ddname.

System actionExecution terminates.

Programmer responseEnsure that the LOGTAPE ddname is correctlyallocated.

DFS2728I UNABLE TO OPEN DD=SYSUT1(2).ANALYSIS TERMINATED.

ExplanationA data definition statement with the ddname SYSUT1or SYSUT2 was included in the JCL, but either or bothdata sets could not be successfully opened.

System actionExecution terminates.

Programmer responseEnsure that ddname SYSUT1(2) is allocated properly.


http://www.ibm.com/support/knowledgecenter/SSEPH2_15.1.0/com.ibm.ims15.doc.sur/ims_dbfulta0.htm#ims_dbfulta0

http://www.ibm.com/support/knowledgecenter/SSEPH2_15.1.0/com.ibm.ims15.doc.sur/ims_dbfulta0.htm#ims_dbfulta0

DFS2729I PERMANENT I/O ERROR READINGLOG DATA SET. ANALYSISTERMINATED.

ExplanationModule DBFULTA0 attempted to read a log record,and the access method returned control to the SYNADaddress specified in the log data set DCB, indicating anuncorrectable I/O error on the log data set.

System actionAnalysis is terminated prematurely with presentationof the results accumulated up to the point of the error.

Problem determinationCheck the accompanying IEA or IEC messages fordetails.

DFS2730A UNABLE TO LOAD FP INPUTROUTING EXIT: DBFHAGU0

ExplanationDuring IMS system initialization, Fast Path initializationwas unable to load DBFHAGU0, the required Fast Pathinput routing exit.

System actionAfter issuing this message, IMS Fast Path initializationterminates with the user abend 1011.

System programmer response1. Make sure that the default or customer written

version of DBFHAGU0 is in the IMS.SDFSRESLSTEPLIB concatenation.

2. Restart IMS.


DFS2732E SVSO CASTOUT PROCESS FAILEDDUE TO TIMEOUT. AREA=xxxxxxxx

ExplanationThis message is generated when the CASTOUT for anSVSO area has timed out. The maximum number ofretries has been exhausted.

System actionArea xxxxxxxx is stopped and marked as recoveryneeded.

System programmer responseUse the Database Recovery utility to recover the area.

Module:DBFVXOC0

DFS2731I MSDB xxxxxxxxxx STARTED

ExplanationThis information message alerts you that MSDBxxxxxxxxxx started, where xxxxxxxxxx is eitherCHECKPOINT or DUMP.



Module:DBFDBDP0

DFS2733I OPEN FAILED. DDNAME=xxxxxxxx

ExplanationThere was a faulty DD statement, or a DD statementwas missing.

System actionProcessing continues. However, abnormal terminationis likely if an attempt is made to read or write the dataset.

Programmer responseCheck the DD statement, and resubmit the job.

DFS2735A MORE THAN ONE RUN CARD

ExplanationMore than one run card was supplied, and only onecard is valid.

System actionProgram DBFDBMA0 continues processing untilmessage DFS2740A appears.

Programmer responseRemove the extra run cards, and resubmit the job.




ERRORS IN CONTROL FILE. TERMINATE

DFS2736A INVALID ACTION CARD

ExplanationThere was a syntax error in the listed statement.


Programmer responseCorrect the statement, and resubmit the job.

Related information“DFS2740A” on page 774ERRORS IN CONTROL FILE. TERMINATE

DFS2737A NO RUN CARD

ExplanationNo run card was supplied.


Programmer responseInsert a run card, and resubmit the job.


DFS2738A NO ACTION CARDS

ExplanationProgram DBFDBMA0 requires at least one action card,and none was supplied.

System actionThe program continues processing until messageDFS2740A appears.

Programmer responseSupply one action statement for each MSDB, andresubmit the job.


ERRORS IN CONTROL FILE. TERMINATE

DFS2739A DUPLICATE ACTION CARDS

ExplanationDuplicate action card were supplied; however, onlyone is allowed for each MSDB.


Programmer responseCorrect the file, and resubmit the job.


DFS2740A ERRORS IN CONTROL FILE.TERMINATE

ExplanationThis message is always preceded by one or moredetailed messages.

System actionProgram DBFDBMA0 terminates.

Programmer responseCorrect the errors in the control file. Resubmit the job.

DFS2741A CHANGE RECORD SYNTAX ERROR

ExplanationThere was a syntax error in the last-listed record of thestatement image change file.


Programmer responseCorrect the change file, and resubmit the job.

DFS2742A CHANGE RECORD DATA INVALIDOR TOO LONG

ExplanationThe specified change record contained invalid data.




DFS2743I READING THE OLCSTAT MDAMEMBER

ExplanationAn OLCSTAT DD statement was coded in the batch JCL;however, the system cannot access the data set. Anattempt was being made to read the MDA member ifone exists.



Module:DFSBIND0

DFS2744E MESSAGE(S) MAY HAVE BEENLOST DURING IMS/CQS RESYNC

ExplanationDuring checkpoint or IMS/CQS Resync process, one ormore CQSPUTs were not performed. IMS was eithernot able to determine the status of the CQSPUT (aprior CQSPUT might not have been successful), or anerror occurred during the rebuild of a message forthe CQSPUT. One type 67D00F diagnostic record islogged per unresolved CQSPUT. This is an IMS internalerror. Contact IBM Software Support as indicated inthe programmer response.

System actionThe CQSPUT was not performed and the message wascleaned up locally.

Programmer responsePull all type 67D0 and 3F log records from IMSlog for the system on which the IMS message wasreceived by using the utility DFSERA10 with optionEXITR=DFSERA30. Save all the IMS logs; then call IBMSoftware Support to report the problem.

Problem determinationCheck type 67D00F diagnostic records to determinethe status of the CQSPUT. The header of the 67D00Frecord should contain the function and description ofthe error.

Module:DFSQURS0

DFS2745A MSDB TO BE INSERTED ALREADYEXISTS. DBD=name

ExplanationThe action statement called for an MSDB to beinserted, but the previous load-image file contained anMSDB with the same name. The intended action mighthave been to replace the MSDB.



DFS2746A MSDB TO BE DELETED REPLACEDOR MODIFIED DOES NOT EXIST.DBD=name

ExplanationThe action statement specified DELETE, REPLACE, orMODIFY but there was no such MSDB on the priorload-image file of MSDBs. The intended action mighthave been to insert the MSDB.


Programmer responseCorrect the input and resubmit the job.

DFS2747A ERRORS DETECTED IN CHANGEFILE. TERMINATE

ExplanationThis message is always preceded by one or moredetailed messages.



Programmer responseCorrect the errors in the change file, and resubmit thejob.

DFS2748A NO CHANGE RECORDS DBD=name

ExplanationThe action statement indicated the action INSERT orREPLACE, but there were no change records supplyingthe segment data for the database named in themessage.


Programmer responseChange records must be supplied in sequence by mainstorage database (MSDB). Within each MSDB, changerecords must be supplied by key. Correct the input,then resubmit the job.

DFS2749A NO CHANGE RECORDS FORMODIFY. DBD=name

ExplanationThe action statement specified MODIFY, but no changerecords were supplied for this MSDB.



DFS2750A ATTEMPT TO MODIFYNONEXISTENT MSDB. DBD=name.

ExplanationA MODIFY change record specified a key that does notexist in the prior load-image copy of MSDBs.






DFS2751A NO ACTION CARD. DBD=name

ExplanationA change record was provided for the named MSDB,but the associated ACTION statement was missing.

System actionProcessing continues until message DFS2747A isissued; then the MSDB Maintenance utility terminates.

Programmer responseProvide an ACTION statement for the MSDB andresubmit the job.

Related information“DFS2747A” on page 775ERRORS DETECTED IN CHANGE FILE.TERMINATE

DFS2752A UNKNOWN FIELD NAME.

ExplanationThe last-listed card image change file statementcontained an unknown field name.



DFS2753I nnnn MSDBS COPIED

ExplanationThis summary message shows the count of MSDBshas been copied intact from the load-image data setsMSDBINIT(0) to MSDBINIT(+1).

DFS2754I nnnn MSDBS REPLACED

ExplanationThis summary message shows the count of the MSDBsthat were replaced.

DFS2755I nnnn MSDBS DELETED

ExplanationThis summary message shows the count of the MSDBsthat were deleted.

DFS2756I nnnn MSDBS MODIFIED

ExplanationThis summary message shows the count of the MSDBsthat were modified.

DFS2757E QUEUE MANAGER DETECTEDAN ERROR - UOWID:SSSSSSSSTTTTTTTTTTTTTTTT

ExplanationAn IMS internal error was encountered by QueueManager. One or more type 67D0 diagnostic recordswere logged. This error message is used whenpossible in place of the Queue Manager abend 0757.

In the message text:SSSSSSSS

SMQ NAME of originating IMSTTTTTTTTTTTTTTTT

Represents the 8 hex bytes of the originating UOWtoken.

System actionQueue Manager performs the appropriate cleanup andcontinues processing.

Programmer responsePull all type 67D0 log records from IMS Log forthe system that the IMS message was receivedon by using the IMS utility DFSERA10 with optionEXITR=DFSERA30. Save all IMS logs, then call IBMSoftware Support to report the problem.

Problem determinationType 67D00A diagnostic records with matching UOWtoken from the message describe the error conditionand contain diagnostic information.

DFS2758I STARTING QFIX PROCESSING

:QFIX - PROCESSING cccc


or

QFIX - PROCESSING cccc. QFIX ddd.d%COMPLETED.

ExplanationThis message provides information about currentprocessing status of QFIX.

In the message text:cccc

The current block type. The block types areprocessed in the following order:

SMBCNTAPPCOTMARREMSCCCBBITMAP

ddd.dThe percentage of the message queue records thathave been processed since the start of QFIX. TheQFIX ddd.d% COMPLETED. version is generatedwith all the cccc types except BITMAP.

System actionA message is generated at the start of QFIX. Additionalmessages are generated approximately every 10minutes. These messages note the current block typethat QFIX is processing and the percentage of themessage queue records processed so far.


DFS2759I INVALID SYNTAX. DBN=EXPECTED

ExplanationThe MSDB DUMP/RECOVERY utility processed acontrol statement which contained a value other thanDBN=.

System actionProgram DBFDBDR0 terminates.


DFS2760I INVALID SYNTAX. BLANKFOLLOWING DBN=(

ExplanationThe first character in the list of MSDB names suppliedin the control file was a blank. It must be an alphabeticcharacter.



DFS2761W ERROR IN MSDB CHKPT - NOIMS CHKPT TAKEN - SHUT DOWNSYSTEM

ExplanationProgram DBFDBDP0 found an error in a main storagedatabase (MSDB) checkpoint data set and no MSDBcheckpoint was taken. The system must be shut downto recover.

System actionNo system or MSDB checkpoint is taken, except for anyshutdown checkpoint that you requested. An MSDBcheckpoint is not taken as part of the shutdowncheckpoint.

Operator response(master terminal) If a write error occurs in an MSDBcheckpoint data set during the initial checkpoint afterthe IMS restart, and the restart checkpoint is written tothe OLDS, perform a warm start recovery. Otherwise,perform either a warm start recovery or an emergencyrestart recovery.

Warm start recovery:

1. Shut down IMS.2. Message DFS2762A is issued. Follow the actions

documented in message DFS2762A.

Emergency restart recovery:

1. Force termination of IMS by issuing a MODIFYIMS,STOP command.

2. Scratch the failing MSDB checkpoint data set, andreallocate a new data set.


3. Copy the valid MSDB checkpoint data set to thenewly allocated data set.

4. Emergency restart the system from the last validsystem checkpoint.

Related information“DFS2762A” on page 779SYSTEM SHUTDOWN-MSDB RECOVERYREQUIRED

DFS2762A SYSTEM SHUTDOWN-MSDBRECOVERY REQUIRED

ExplanationThe master terminal operator requested a shutdownof IMS after message DFS2718I or DFS2761W wasissued.

System actionA shutdown checkpoint is taken without taking anMSDB checkpoint.


1. Run the Log Archive utility (DFSUARC0).2. Run the MSDB DUMP RECOVERY utility

(DBFDBDR0) to recover the MSDBs from thevalid MSDB checkpoint data set and the SLDSscontaining MSDB changes since the last validsystem checkpoint.

3. Discard the failing MSDB checkpoint data set, andreallocate a new data set.

4. Warm start IMS with the MSDBLOAD keyword.

Related information“DFS2718I” on page 770ERRORS IN MSDB CHKPT DATA SET, NOSYSTEM/MSDB CHKPT TAKEN“DFS2761W” on page 778ERROR IN MSDB CHKPT - NO IMS CHKPTTAKEN - SHUT DOWN SYSTEM

DFS2763I REQUIRED CHECKPOINT RECORDNOT FOUND ON LOG

ExplanationThe Fast Path restart modules read the control recordsfrom the MSDB checkpoint data set to determinefrom which checkpoint to restart the MSDB, but theselected checkpoint was not found on the IMS log.

System actionIMS continues without Fast Path.

Programmer responseSelect a checkpoint from which to restart thatmatches, or is prior to, one of the checkpoints on theMSDB data set, and specify all log data sets up to thelatest checkpoint.

DFS2764W MSDB ARITHMETIC OVERFLOWMSDB=xxxxxxxx FIELD=xxxxxxxxKEY=xxxxxxxx

ExplanationArithmetic overflow occurred in the database indicatedin the message text.

System actionThe input message is reprocessed so that the overflowwill be detected at call time.

Operator response:(master terminal) Contact the IMS systemprogrammer.

Programmer responseCorrect the database generation to allow a appropriatefield size for the segment type.

DFS2765W OUT OF SPACE INDATA SET DATABASE=xxxxxxxxAREA=yyyyyyyy ss RM: tttt

ExplanationThe DEDB area described in the message has run outof space in the sequential dependent portion of thearea. No more additions of sequential dependents tothe area are possible.


The DEDB containing the area which ran out ofspace.

yyyyyyyyThe area that ran out of space.

ssThe DL/I call status code. For these codes, see theDL/I status code information.

ttttThe type of DL/I status call that was issued. Thevalid types for this message are:


ISRTThe message was issued by moduleDBFMSRT0 when attempting to pre-allocateSDEP CIs for SDEP insert activity.

SDEPThe message was issued by moduleDBFSYN10 when processing SDEPs duringsync point.

For more information about sequential dependentspace management, see the IMS Version 15 DatabaseAdministration.

System actionThe input message is reprocessed so that thecondition will be detected at call time.

Operator response:Contact the IMS system programmer.

Programmer responseDetermine which data is no longer required in thedatabase and run the Delete utility to reclaim usablespace for the online system.

Module:DBFMSRT0, DBFSYN10


DFS2766I PROCESS FAILED

ExplanationThe application program has abnormally terminated.This general message is accompanied by one of anumber of messages to the master terminal detailingthe reason for the failure.


Operator response:Contact the IMS database administrator or the systemprogrammer, or both.

DFS2767I AREA=xxxxxxxx DEDB AREA FULL

ExplanationThe space management module could not findadequate space in the root portion of the area for anISRT request.

Note: This message is sent to the Master Terminaloperator.

System actionFor an IFP or MPP, the transaction requesting theISRT is canceled, the dependent region from whichthe request originated is brought down, and if thethreshold value has not been reached, the dependentregion is brought back up. If the region is a BMP, itcompletes normally but receives a STATUSFS for theISRT call.

DFS2768W FAST PATH RESTART ERROR-FPUNAVAILABLE

ExplanationModule DBFNRST0 detected an error during Fast Pathrestart.

System actionIMS continues without Fast Path.

Programmer responseCold start the system after all of the IMS queues areprocessed and all of the messages are sent to theirdestination.

DFS2769I INVALID SYNTAX. DELIMITEREXPECTED BEFORE 72

ExplanationThe utility was scanning the control file for a blank orcomma, indicating the end of an MSDB name. Column72 was reached before the delimiter was found.



DFS2770I FAST PATH DBD dbdnameIGNORED

ExplanationInitialization for database backout found a Fast PathDBD. All Fast Path DBDs are ignored.

System actionProcessing continues and bypasses the Fast PathDBDs.

DFS2771 APDB KEYWORD HAS INVALIDPARAMETER



ExplanationYou entered an invalid parameter for this keyword.


Operator response:(master terminal) Reenter the command and keywordusing valid parameters.

Module:DFSICL30, DFSICLN4

DFS2772 REGION KEYWORD HAS INVALIDPARAMETER



Operator response:Reenter the command and keyword using validparameters.


DFS2773 INTERVAL KEYWORD HASINVALID PARAMETER



Operator response:Reenter the command and keyword using validparameters.


DFS2779I INVALID MSDB (or DEDB)APPLICATION CONTROL BLOCKS-xxxxxxxx WERE FOUND IN ACBLIB

ExplanationThe named Fast Path MSDB or DEDB applicationcontrol block in ACBLIB is incompatible with thecurrent level of the system. The block is not usableuntil it is brought up to current level.

System actionIMS continues running and the named MSDB or DEDBis marked as not accessible.

Operator response:(master terminal) Notify system programmer.

Programmer response:Rerun ACBGEN with a BUILD DBD=xxxxxxxx controlstatement.

DFS2780A CONFLICT WITH PRIOR DATA=KEYWORD.

ExplanationThe card image change file contained DATA= without aprior associated FIELD=, and following another DATA=for the same key.



DFS2781A DATA= KEYWORD EXPECTED.

ExplanationThe FIELD= keyword was not followed by DATA=keyword, or KEY= was not followed by DATA=.



DFS2782A INCORRECT DATA LENGTH

ExplanationThe DATA= keyword was followed by a character stringinconsistent with the DBD-specified field or segmentlength.




DFS2783A UNABLE TO DELETE FAILED-PERSISTENT CONNECTIONTO STR: Structure_NameREASON=xxxx

ExplanationAfter IMS processes a /VUNLOAD command,DBFXVUN0 issues an IXLFORCE macro call to deletethe failed persistent connection to the Shared VSOstructure. This message is issued when the IXLFORCEcall fails with a return code that is greater than 4.


Programmer responseDetermine if the failed persistent connection existsand delete it manually.

Module:DBFXVUN0

DFS2785A INVALID CONTINUATION CARD

ExplanationA continuation statement contained a nonblankcharacter in the first 15 columns.



DFS2786A DBDNAME=xxxxxxxx NOT INACBLIB

ExplanationAn action statement specified a DBD name not knownto the system.



DFS2787A I/O ERROR IN BLDL. ACBLIB

ExplanationProgram DBFDBMA0 attempted to process the BLDLmacro against the ACBLIB and an I/O error occurred.


Programmer responseRestore or rebuild the ACBLIB, and resubmit the job.

DFS2788I nnnn MSDBS INSERTED

ExplanationThis summary message contains the count of MSDBsthat were inserted.

System actionExecution continues.

DFS2789A CHANGE FILE SEQUENCE ERROR

ExplanationA DBD name in one of the change files, or a key withina DBD was out of sequence.



DFS2790A SAME RECORD APPEARS IN BOTHCHANGE DATA SETS.

ExplanationBoth change data sets contained the same key for thesame MSDB.



DFS2791A INVALID HEX DATA


ExplanationThe DATA= keyword contained invalid hexadecimaldata.



DFS2792A KEY= KEYWORD EXPECTEDAFTER DBN=

ExplanationThe card change data set contained a DBN= keywordwhich was not immediately followed by a KEY=keyword.



DFS2793I NEW STARTUP PROC MEMBER.NAME=xxxxxxxx

ExplanationThis message is the header for a list of the newSTARTUP PROCEDURE MEMBER entries. It is forinformation only.

DFS2794I MSDB DUMP/RECOV UTIL NORMALTERMINATION

ExplanationThis message confirms that the utility was successful.

System actionThe utility terminates normally.

DFS2795I WRONG LOG VOLUME WASMOUNTED. TERMINATE. CKPTREQUIRED=xxxxxxxx, FIRST IDFOUND=xxxxxxxx

ExplanationThe first checkpoint identification on the log data setmounted was later than the required checkpoint.


Programmer responseResubmit the job with the previous log data set and alllater data sets.

DFS2796I REQUIRED CKPT ID=xxxxxxxx,NOT IN LOG

ExplanationAn end-of-file condition occurred before the requiredcheckpoint was found.


Programmer responseResubmit the job, using an alternate log data set.

DFS2797I NO APPLICABLE UPDATES IN LOG

ExplanationNo MSDB updates were performed since thecheckpoint that the utility was restored from.

System actionNormal utility processing continues.

DFS2798I MSDBINIT DATA SET IS EMPTY

ExplanationThe primary output from the MSDB memory dumprecovery utility is a new MSDBINIT data set. Thisdata set is used for loading the MSDBs during a coldstart or a warm start with MSDBLOAD option. Thenew MSDBINIT data set does not contain and MSDBrecords.

System actionThe utility terminates normally.

Programmer responseVerify that the MSDBINIT data set is empty.

DFS2799I INVAL OPER. MUST BE UNLOAD,UNLOADCP, RECOVERY, ORRECOVCP


ExplanationThe first word in the control data set was not UNLOAD,UNLOADCP, RECOVERY, or RECOVCP.



DFS2800I **CHANGE ACCUMULATION FORDATA BASE dbname DCB NAME/NUMBER [ddname] n

ExplanationDatabase change records have been accumulated forthe database data set. DCB name is only displayed

if accumulation was done by database data set. nindicates the data set number as follows:1

The prime data set2

The overflow data set0

The VSAM sequence set for KSDSThe value n is the relative number of the data setgroup corresponding to ddname. If n=0, the data set isthe index of a VSAM KSDS. n=0 records are used onlyfor the Track Recovery option of database recovery.


Chapter 60. DFS messages, DFS2801A - DFS2850E


DFS2801A ERROR RETURN CODE nn INRESPONSE TO A DL/I REQUESTdd ON DDNAME ddname FORFUNCTION ff

ExplanationThe issuing program attempted to read from or writeto the database data set. The PST DSECT return codesare found in labels PSTFNCTN and PSTRTCDE. See theIMS return code and function code information for themeaning of the PST DSECT return codes.

Programmer responseCorrect the problem, and resubmit the job.



DFS2802A ERROR FEEDBACK = nnnnnn INRESPONSE TO A VSAM (PUT|GET|VERIFY|POINT) REQUEST ONDDNAME ddname FOR FUNCTION(IM|RV), R15=xx

ExplanationAn error occurred when the issuing program attemptedto read from or write to the database data set. TheVSAM request in support of the IMS function (IM forimage copy and RV for recovery) is supplied in themessage text.

Programmer responseCorrect the problem, and resubmit the job.

Related referencez/OS: VSAM macro return and reason codes

DFS2803I RECORD COUNT=nnnn FORddname [NET DECREASE|NETINCREASE|ERLG RECORDS]

ExplanationThe record count indicates the number of logicalrecords processed for the specified data set/area.After processing all input logs or Change Accumulationdata sets, the Database Recovery utility (DFSURDBO)indicates the net increase or decrease in size of theKSDS data sets since the last image copy.

The Change Accumulation Utility (DFSUCMNO)indicates the total number of IMS I/O error log records(ERLG records) found for the named data set.

Database Image Copy utility (DFSUDMP0) indicatesAREA instead of DDNAME when it processes a DEDB.

DFS2804A HEADER RECORD ON DDNAMEddname IS NOT CONSISTENTWITH cccc FOR FUNCTION ff

ExplanationThe header record of the input data set contains data-base-organization, creation-date-time, and purge-date-time information.

This information might be inconsistent betweenchange data (Change Accum or logs) and dump dataset, or change data header does not agree with theDBPCB, or the memory dump data set header does notagree with the DBPCB.

Programmer responseAn examination of the header record might indicatethe corrective action necessary. The memory dumpmight not be current or was created with an invalidpurge time specified, and must be re-created.



DFS2805A RECORD RBN nnnnnnnn ISINVALID






ExplanationAn RBN greater than the EOF plus one block hasbeen encountered. While executing, recovery tracksthe current EOF. This current EOF is the last blockwritten. Each image copy, change accumulation, or logrecord is matched to the EOF. The input record cannever exceed the EOF plus one block unless blocks arebeing skipped, which is not allowed.

A second situation, causing this message, isperforming a HISAM unload but not a reload, and usingthe unload file and subsequent log data sets as inputto recovery.

A third situation can cause this message. If the dataset has an embedded EOF, image copy stops when thefirst EOF is encountered. Records could exist on thelog data set for database records residing between thetwo EOFs. This is most likely caused by executing twoIMS control regions simultaneously against the samedatabase. Failure to scratch and reallocate the datasets during a recovery or reorganization could causethe embedded EOF.

Programmer responseEnsure that all supplied input is correct.

Check for missing log data sets. This is the mostcommon cause for this message. Supply any missinglog data sets to a change accumulation or log input torecovery.

If the second situation occurs, supply a previousunload or image copy and log data sets produced sincethat time.

If the third situation occurs, notify systemprogramming for a resolution. There is norecommended solution to this problem.

When all input is checked, resubmit the job.

Problem determination:2, 3, 4, 8, 17g, 36


DFS2806A SYSIN CONTROL CARD NOTSUPPLIED

ExplanationA control statement is required, but none wasavailable from the SYSIN data set. If this message wasissued from the Database Image Copy 2 utility, it might

indicate that a group statement was not followed by atleast one DBDS Select statement.

Programmer responseInclude at least one control statement and resubmitthe job.

Module:DFSUDMP0, DFSUDMT0

DFS2807I PURGE DATE-TIMESPECIFIED=timestamp

ExplanationThe date and time specified on the SYSIN controlstatement is repeated here.

DFS2808I RECOVER TRACK CCHH=cccchhhh,VOLSER=volser

ExplanationThe track recovery option of the Database Data SetRecovery utility (DFSURDB0) was started for thedesignated tracks.

DFS2809I ATLAS CALL RC=rc FOR TRACKCCHH=cccchhhh, VOLSER=volser

ExplanationSee Data Administration: Macro Instruction Referencefor MVS/DFP (SC26-4506) for the meaning of ATLASreturn codes.

DFS2810I TRACK UPDATE WASUNSUCCESSFUL FOR CIRBA=aaaaaaaa, CCHH=cccchhhh,VOLSER=volser-REASON r(f)

ExplanationThe track recovery option of the Database Data SetRecovery utility was unsuccessful for the reasonslisted below:Code (hex)

Meaning44

The CCHHR in ERLG is not in the data spaceextents.

48The RBA in ERLG is not in the target data setextents.

4CAn error return code was received from ATLAS.


50An error return code was received from VSAM aftera GET/GETIY request (f indicates VSAM feedback).

54An error return code was received from VSAM aftera PUT/PUTIY request (f indicates VSAM feedback).

58The CI RBA=00 was not updated since HISAMunload was used as input to recover an ISDS.


Programmer responseIf possible, correct the problem and rerun trackrecovery. If the problem cannot be corrected, theentire data set must be recovered.

DFS2811A TRACK RECOVERY TERMINATEDABNORMALLY, REASON r(f)

ExplanationIn the message, r indicates the reason code and (f), ifpresent, is the VSAM feedback code. The values of thereason codes and their meanings are as follows:Code (hex)

Meaning04

Unable to open ACB for target data set. Seemessage IEC161I to determine cause of error.

08Error detected while reading VSAM index. (f) is theVSAM feedback code.

0CControl interval RBA in type X'24' error log recordnot found in VSAM index.

14Invalid request. Parameter list passed during trackrecovery call had unidentified request value.

18Record passed by caller did not fit in controlinterval.

1CNo volumes mounted for target data set.

20Unable to open DCB for Data Space.

System actionThe program is terminated abnormally.

Programmer responseIf error is correctable, correct it and rerun the job.If error cannot be corrected, recover the database. Ifreason codes X'14' or X'18' occur, rerun the job withan ABEND control statement.



DFS2812I IMAGE COPY INPUT CREATEDBY ONLINE IMAGE COPY FORFUNCTION RV

ExplanationThe image copy data set used as input to the Recoveryutility was created by the Online Image Copy utility.

DFS2813I nnnnnnnn RECORDS WITHDATE-TIME,SEQUENCE NUMBERyydddhhmmsst; seqno WEREIGNORED ON DDNAME dddddddd

ExplanationIf DDNAME=DFSUCUM, then change accumulationrecords with a date-time less than the image copydate-time were ignored; if DDNAME=DFSULOG, thenlog records with a date-time less than the image copydate-time or the date-time, sequence number of thehighest change accumulation record were ignored.

System actionThe Recovery utility completes and a warning errorcode is returned.

Programmer responseExamine input to recovery to determine why themessage was issued. If an image copy was takenduring (in the middle of) online system operation, thenrecords are expected to be dropped during recovery.Otherwise, this message probably indicates a usererror. Correct the input, and resubmit the job.

DFS2814A TRACK RECOVERY REQUESTEDBUT NOT POSSIBLE

Chapter 60. DFS messages, DFS2801A - DFS2850E 787

ExplanationThe input change accumulation data set does notcontain the error log records required for trackrecovery, therefore, track recovery is not possible.

System actionThe job step terminates abnormally.

Programmer responseEnsure that the change accumulation input is thecorrect accumulation for the log data sets that containthe error log records for the database data set beingrecovered. If change accumulation has not been run,then it must be run. Make the necessary corrections,and resubmit the job.

Problem determinationRerun the job and make the first control statementan ABEND control statement. Supply a SYSUDUMP DDstatement to this step.

Also, submit a copy of the change accumulation dataset and a copy of the logs used to create the changeaccumulation data set.

DFS2815A VSAM KSDS NOT SUPPORTED

ExplanationA concurrent image copy of a VSAM KSDS cannot becreated.

System actionThe Image Copy utility terminates this image copy andreads the next control statement.

Programmer responseRerun the Image Copy utility without specifying CICin the EXEC statement PARM= field. This image copymust run only against databases that are offline,deallocated from any other address space or job, orboth.

DFS2816A ISAM ACCESS METHOD NOTSUPPORTED

ExplanationAn image copy of an ISAM data set cannot be created.

System actionThe Image Copy utility terminates this image copy andreads the next control statement.

Programmer responseSee IMS Version 15 System Definition.

DFS2817A CIC ATTEMPTED WITHOUT DBRC

ExplanationA concurrent image copy cannot be created withoutusing DBRC.

System actionThe Image Copy utility terminates without performingany actions; it requires DBRC.

Programmer responseRerun the Image Copy utility with DBRC or withoutspecifying CIC in the EXEC statement PARM= field.

DFS2818I UPDATES MADE USING PSBpsbname TO UPDATE DATABASEdbname ARE IN DOUBTTHE UNIT OF RECOVERYFOR RECOVERY TOKENaaaaaaaaxxxxxxxxxxxxxxxx IS INDOUBT

ExplanationFor the first part of the message, some RecoveryTokens in the log were in doubt during execution ofthe Database Recovery utility. The following list is the16-byte recovery token in printable format:aaaaaaaa

8-byte character part of the recovery token.xxxxxxxxxxxxxxxx

8-byte hexadecimal part of the recovery token.

The Fast Path unit of recovery was not resolved duringthis run of the Database Recovery utility.

For the second form of the message, the psbnameis the name of the PSB associated with a specificrecovery token. The dbname is the DBD name of all thedatabases updated by the PSB for a recovery token.

A list containing multiple occurrences of the secondpart of the message might be issued. This list cancontain several UOR tokens that are not involved inthe Database Recovery process, but are generatedbecause the input log is incomplete, as far as thesetokens are concerned.

System actionThe Database Recovery utility completes with a returncode of 4.


Programmer responseThis message can be ignored if it is issued for adatabase that is not being recovered. Otherwise, in-doubt data should be resolved as soon as possible.

DFS2819A AREA areaname CONNECT TOSTR: strname FAILED. DUPLICATESTRUCTURE NAME FOUND.

ExplanationAn identical structure name for the VSO area wasalready defined in the coupling facility.

System actionThe OPEN process for the area fails.

System programmer responseSpecify a unique structure name for the area.

Module:DBFVSOP0

DFS2821I PRELOAD COMPLETED FOR ALLSHARED VSO AREAS

ExplanationThe preload process for all shared VSO areas hascompleted.

System actionNone.


Module:DBFVXPL0

DFS2822I AREA areaname CONNECT TO STR:strname SUCCESSFUL

ExplanationArea areaname was successfully connected to cachestructure strname.

Module:DBFVXCS0

DFS2823I AREA areaname DISCONNECTFROM STR: strname SUCCESSFUL

ExplanationArea areaname was successfully disconnected fromcache structure strname.

Module:DBFVXCS0

DFS2824A AREA areaname CONNECTTO STR: strname FAILED.4K BLKS REQUIRED=xxxxx,ALLOCATED=yyyyy.

ExplanationThe actual cache structure size created was less thanthe actual structure size required. The required size,indicated by xxxx, and the allocated size, indicated byyyyy, are displayed in hexadecimal.

System actionThe open process for the area fails.

System programmer responseDesignate a new coupling facility or specify thestructure size correctly. The formula to determine thestructure size can be found in PR/SM Planning Guide,(GA22-7236), or (GA22-7123).

DFS2825A AREA areaname CONNECT TOSTR: strname FAILED. VECTORLENGTH REQUESTED=xxxxx,ALLOCATED=yyyyy.

ExplanationThe actual vector length created was less than therequested length.


System programmer responseContact IBM Software Support.

DFS2826A AREA areaname CONNECTTO STR: strname FAILED.INTERNAL PARAMETER ERROR.XES RC=xxxx.

ExplanationA z/OS cross-system extended services (XES) internalerror occurred. The XES return code is xxxx.




DFS2827A AREA areaname CONNECT TOSTR: strname FAILED. INTERNALXES ERROR. CONDIAG0=xxxxxxxx,CONDIAG1=yyyyyyyy,CONDIAG2=zzzzzzzz.

ExplanationAn internal z/OS cross-system extended services (XES)error occurred. The message provides XES diagnosticinformation.



Module:DBFVXCS0

DFS2828A AREA areaname DISCONNECTFROM STR: strname FAILED.INTERNAL XES ERROR. XESRC=xxxx.

ExplanationAn internal z/OS cross-system extended services (XES)error occurred. The XES return code is xxxx. TheXES return and reason codes are documented in theIXLDISC macro.

System actionThe area is stopped


ModuleDBFVXCS0

Related referencez/OS: IXLDISC return and reason codes

DFS2829I AREA areaname CONNECT TOCF FAILED; INCONSISTENTSTRUCTURE SIZES

ExplanationAn area is defined with the VSO, NOPRELOAD options.Dual structures are defined. The structure sizes mustbe the same to prevent inconsistencies between thetwo structures.


System programmer responseAllocate the two structures with the same size.

Module:DBFVXCS0

DFS2830I CF READERROR, RBA rrrrrrrr,AREA areaname,STR strnameRC=xxxxxxxx RSN=yyyyyyyy

or

CF WRITEERROR, RBA rrrrrrrr, AREA areaname,STRstrname RC=xxxxxxxx RSN=yyyyyyyy

ExplanationThe read or write of the control interval (CI) to thecoupling facility failed. An internal z/OS cross-systemextended services (XES) error occurred. The returnand reason codes provide XES diagnostic information.These return and reason codes are documented in theIXLCACHE macro.

System actionFast Path continues processing the area from DASD, ifa single cache structure is defined, or from the otherstructure, if multiple structures are defined.


Module:DBFVSOW0, DBFMSRB0

Related referencez/OS: Return and reason codes for theIXLCACHE macro (for read)





z/OS: Return and reason codes for theIXLCACHE macro (for write)

DFS2831I POOLNAME XXXXXXXX; BUFFERSHORTAGE. POOL EXPANDEDBEYOND MAX

ExplanationA buffer pool, indicated by XXXXXXXX, is experiencinga buffer shortage. The buffer pool will be expandedbeyond the specified limit by the secondary amount.

Operator responseUse the /DIS POOL FPDB command to display theprivate pool usage.

DFS2832I CANNOT ADD/CHANGE dedbname-CI SIZE OF areaname EXCEEDSBSIZ

ExplanationAn attempt to add area areaname to DEDB dedbnamefailed. The area control interval (CI) size exceeds theFast Path buffer size (BSIZ=) of the IMS online controlregion.

System actionThe /MODIFY PREPARE or INITIATE OLCPHASE(PREPARE) command fails.

Programmer responseDecrease the CI size of the added area.

Module:DBFOLC01

DFS2833I CANNOT ADD DEDB dedbname-FAST PATH NOT INSTALLED

ExplanationAn attempt was made to add a data entry database(DEDB) to an IMS system that does not have Fast Pathinstalled.


Programmer responseRemove the DEDB from the system definition or installFast Path.

Module:DFSRMDM0

DFS2834I PSB psbname HAS BEENRESCHEDULED BECAUSE OFONLINE CHANGE

ExplanationAn IMS Fast Path program (IFP) or messageprocessing program (MPP) attempted to update a dataentry database (DEDB) that was changed using onlinechange.

System actionThe application program is terminated with apseudoabend, and the PSB is rescheduled.

Module:DBFIRCI0

DFS2835I ERROR IN VSPEC DEDBSTMT: statement_text REASON=reason_text

or

ERROR IN VSPEC DEDB STMT: POOLNAME text; text;SPECIFICATION ERROR

or

ERROR IN VSPEC SDEPQCI STMT: statement_textREASON= reason_text

ExplanationThe DEDB or SDEPQCI VSPEC statement text isincorrect. The message displays the text for amaximum of two pools in error, however, there mightbe more pools in error than those included in thismessage.

For the variant with statement_text, the statement_textshows partial error statement. The reason_text offersthe explanation for the error.

System actionIMS continues processing without the buffer poolin error or accounting for the DEDB or SDEPQCIstatement in error.


http://www-01.ibm.com/support/knowledgecenter/SSLTBW_2.4.0/com.ibm.zos.v2r4.ieai700/wda.htm?lang=en

http://www-01.ibm.com/support/knowledgecenter/SSLTBW_2.4.0/com.ibm.zos.v2r4.ieai700/wda.htm?lang=en

System programmer responseStop IMS and restart with a corrected VSPEC member.

Module:DBFVSOP0, DBFPVTS0, DBFDVBI0

DFS2837I CANNOT ADD DEDB dedbname-OTHREADS NOT INITIALIZED

ExplanationAn attempt was made to add a data entry database(DEDB) to an IMS system that was not initializedwith DEDBs. No output threads (OTHREADS) wereinitialized and no I/O is possible to the added DEDB.

System actionThe /MODIFY PREPARE or INITIATE OLCPHASE(PREPARE) processing stops.

Programmer responseDefine DEDBs to the system and restart IMS.

Module:DFSRMDM0

DFS2838I RANDOMIZER name FORdedbname IS DELETED AND status

or

RANDOMIZER name FOR dedbname/FFdatabase/HALDBpartition IS DELETED AND status

ExplanationIf IMS successfully deleted the database randomizerand no more copies are in storage, the status GONE isdisplayed. If the randomizer is reentrant and a copyis found in storage after being deleted, the statusSHARED is displayed.

The following commands can delete the randomizer:

• /DBR DB dbname• /DBR DB FFdatabase• /STO DB FFdatabase• /STA DB FFdatabase• UPDATE DB NAME(dedbname) STOP(ACCESS)• UPDATE DB NAME(FFdatabase) STOP(ACCESS)• UPDATE DB NAME(FFdatabase) STOP(UPDATES)• UPDATE DB NAME(FFdatabase) START(ACCESS)

System action:

The randomizer is physically deleted from storagewhen the status is GONE. The randomizer is notdeleted from storage when the status is SHARED.


Module:DBFDBAC0, DBFOLC02, DBFARD30, DBFERDB0,DBFMSIU0, DFSDOCA0

DFS2839I ERROR TRYING TO GETMAINSTORAGE FOR DMCBS

ExplanationThe /MODIFY PREPARE or INITIATE OLCPHASE(PREPARE) command failed to get enoughCommon Service Area (CSA) and the ExtendedCommon Service Area (ECSA) storage for adding orchanging data entry databases (DEDBs).


Programmer responseStop IMS and increase the size of CSA or ECSA.

Module:DBFOLC01

DFS2840W ERROR IN LOADING RANDOMIZERname FOR DEDB dedbname, RC=zz

ExplanationRandomizer name cannot be loaded.

System actionThe command (/MODIFY PREPARE, INITIATE OLCPHASE(PREPARE), /START DB, or UPDATE DBSTART(ACCESS)) continues without loading therandomizer. Subsequent DL/I calls to this dataentry database (DEDB) receive an FH status code.Hexadecimal return code zz from the IMODULEfunction of IMS is explained in the IMODULE returncode information.

Programmer responseIf the return code is 0, the randomizer module was notreentrant. Rerun the bound JCL to make it reentrant.

Also verify that:


• The randomizer was correctly linked into the IMSsystem.

• The DEDB was correctly defined with the randomizername.

Correct any errors and issue the UPDATE DBSTART(ACCESS) or /START DB command to reloadthe randomizer.

Module:DBFDBAC0, DBFINI24, DBFERDB0, DBFMSIU0


DFS2841A ERROR TRYING TO GETMAINSTORAGE FOR LTERM KEYWORD

ExplanationGETMAIN failed while trying to allocate storage for theLTERM keyword of the /MODIFY command.

System actionThe /MODIFY PREPARE command is terminated.

Operator responseAfter increasing CSA size, restart IMS. Or after freeingup some common storage area (CSA), reenter the /MODIFY PREPARE command.

Programmer responseConsult your z/OS system programmer. Determinewhat resources are using the CSA and attempt to freesome CSA for use. You must issue an IPL to increaseCSA.

Module:DBFOLC01

DFS2842I RANDOMIZER name FORdedbname IS LOADED/SHARED

or

RANDOMIZER name FOR dedbname/FFdatabase/HALDBpartition IS LOADED/SHARED

ExplanationIf the randomizer is not in storage and IMSsuccessfully loaded it, the status LOADED is displayed.If an existing copy is found in storage and the samecommand is entered, the status SHARED is displayed.

The following commands can load the randomizer:

• /START DB dedbname• /START DB FFdatabase OPEN• /START DB HALDBpartition OPEN• UPDATE DB NAME(dedbname) START(ACCESS)• UPDATE DB NAME(FFdatabase) START(ACCESS)OPTION(OPEN)

• UPDATE DB NAME(HALDBpartition)START(ACCESS) OPTION(OPEN)

• INIT OLREORG NAME(partname)• /INIT OLREORG NAME(partname)

System action:The randomizer is physically loaded in storage for thestatus LOADED. The randomizer is logically loaded instorage for the status SHARED.


Module:DBFDBAC0, DBFERDB0, DBFMSIU0, DFSDOCA0

DFS2843 DATASET service FAILED FORds_type

DSN=dsn

SYNAD BUFFER FOLLOWS: dev#,devtype,DDname,operation,error description,blocknumber,access method

Operator responseFor information about this message, see DFS2843E.

Related information“DFS2843E” on page 793DATASET service FAILED FOR ds_type,RC=rrrrrrrr/ssssssssDSN=dsnSYNAD BUFFER FOLLOWS: dev#,devtype,DDname,operation,,block number,access method

DFS2843E DATASET service FAILED FORds_type, RC=rrrrrrrr/ssssssssDSN=dsnSYNAD BUFFERFOLLOWS: dev#,devtype,DDname,operation,,blocknumber,access method

ExplanationA data set failure occurred.



The third line of this message, which begins withSYNAD BUFFER FOLLOWS, is displayed only whenpassed on by the BSAM data set access method. Whenthe line is displayed, it contains the contents of theSYNAD buffer, including the device number, the devicetype, the DDname, the operation attempted, the errordescription, the block number, and the access method,which is BSAM. For information about the mapping andmeaning of the SYNAD buffer, see the description forthe SYNADAF macro. BSAM might or might not returnthe SYNAD buffer, depending upon the error.

In the message text:service

The service that failed, which can be:

OPENCLOSEREADWRITE

ds_typeIdentifies the online change data set specified inthe DFSCGxxx PROCLIB member.

rrrrrrrrThe return code from the MVS/DFP service. Thisreturn code is not displayed when the SYNADbuffer is displayed.

ssssssssThe reason code from the MVS/DFP service. Thisreason code is not displayed when the SYNADbuffer is displayed.

dsnThe name of the data set.

If an OM command encounters this error, this messageis sent to the OM output exit as an unsolicitedmessage.

If IMS initialization or IMS restart encounters thiserror, this message is sent to the system console.

If a utility encounters this error, this message is sent tothe utility's job log.

System actionThe system action depends on the IMS function thatencountered the error:

• IMS initialization fails with abend 2800, subcodeX'0002' or X' 0003'.

• IMS restart fails with abend 2801, subcode X'0002'or X'0003'.

• IMS online change commands are rejected.

Operator responseCorrect the data set problem and try IMS initialization,IMS restart, or the online change command again.

If the error description of the DFS2843 messagecontains the text WRNG.LEN.RECORD, the OLCSTATdata set might not have been allocated correctly. Verifythat you allocated the OLCSTAT data set with an endof file (EOF) mark. If you used IEFBR14 to allocatethe OLCSTAT data set, it does not have an EOF markand cannot be read. You must allocate the OLCSTATdata set with an EOF mark to correct this problem. Youcan use IEBGENER or the ALLOCATE function of ISPFutilities to allocate the OLCSTAT data set

Module:DFSIIOC0, DFSIQ040, DFSOLC00, DFSROLC0

Related referencez/OS: SYNADAF error descriptionsRelated information“DFS2843” on page 793DATASET service FAILED FOR ds_type

DFS2844E DATASET ds_type CONTENTSINVALID ERROR=errortext

ExplanationThe data set contents are invalid. In the message text:ds_type

Identifies the online change data set specified inthe DFSCGxxx PROCLIB member.

errortextContains a description of the error, and might beone of the following values:Term

MeaningNOT INIT

The OLCSTAT data set is not initialized.INVALID ENVIRONMENT

The OLCSTAT data set is invalid for thisenvironment. IMS was defined with RMENV=N,which means that the OLCSTAT data set cannotbe shared. One or more IMS member namesare defined in the data set.

Use the OLC utility, DFSUOLC0, to correct theOLCSTAT data set.

INVALID HDR LENThe OLCSTAT data set header length is invalid.The header length must be non-zero and nolarger that the maximum OLCSTAT data setsize.

INVALID OLCINPThe OLCSTAT data set lock word is invalid.



ACBLIB SUFFIXThe ACBLIB suffix is invalid. The suffix must beA or B.

FMTLIB SUFFIXThe FMTLIB suffix is invalid. The suffix must beA or B.

MODBLKS SUFFIXThe MODBLKS suffix is invalid. The suffix mustbe A or B.

If an OM command encounters this error, this messageis sent to the OM output exit as an unsolicitedmessage.

If IMS initialization or IMS restart encounters thiserror, this messages is sent to the system console.

If a utility encounters this error, this message is sent tothe utility job log.


• IMS initialization abends with 2800, subcodeX'0007'.

• IMS restart abends with 2901, subcode X'0007'.• Online change commands fail.

System programmer responseRun the global online change utility (DFSUOLC0)to initialize the OLCSTAT data set. Then try IMSinitialization, IMS restart, or the online changecommand again.

Module:DFSIIOC0, DFSIQ040, DFSOLC00, DFSROLC0

DFS2845A rsrcdesc rsrctype DEFINITIONINCONSISTENT, ENTERCONTINUE OR CANCEL

ExplanationIMS initialization determined that a resource definedby this IMS is inconsistent with a resource defined bythe IMS systems in the IMSplex.

In the message text:rsrcdesc

A description type, which is DATASET.rsrctype

A resource type, which can be:

ACBLIBFMTLIBMODBLKS

System actionIMS waits for a reply to the message.

Operator responseEnter one of the following responses:CONTINUE

Continue with IMS initialization even though one ormore resources that were checked for consistencyon this IMS do not match the resources defined byother IMS systems in the IMSplex.

CANCELCancel IMS initialization. IMS initializationterminates with an abend 2800, subcode X'0008'.

This message is sent to the system console.

System programmer responseMake sure all of your IMS systems are using the sameresource definitions, or disable resource consistencychecking using the DFSCGxxx NORSCCC= parameter.

Module:DFSCSL40


DFS2846E rsrcdesc rsrctype DEFINITIONINCONSISTENT

ExplanationIMS initialization determined that a resource definedby this IMS is inconsistent with a resource defined byother IMS systems in the IMSplex.

In the message text:rsrcdesc

A resource description, that is DATASET.rsrctype

A resource type, that is OLCSTAT.

This message is sent to the system console.

System actionIMS initialization fails with abend 2800, subcodeX'0009'.

Programmer responseSee abend 2800 for response details.

Module:DFSCSL40





DFS2847I MODIFY COMMAND REJECTED- GLOBAL ONLINE CHANGEENABLED

ExplanationYou used a /MODIFY command for a local onlinechange, but it was rejected because global onlinechange is enabled. Global online change is enabledusing the DFSCGxxx PROCLIB member keywordOLC=GLOBAL.

This message is sent to the terminal that entered the /MODIFY command.

System actionThe /MODIFY online change command is rejected.

Operator responseIssue an INITIATE OLC command to initiate a globalonline change.

Module:DFSICV10

DFS2848E DYN service FAILED for ds_type,RC=rrrrrrrr/ssssssssDSN=dsn

ExplanationA dynamic allocation failure occurred.

In the message text:service

The failing service, which is either ALLOC orUNALLOC.

ds_typeThe online change data set specified in theDFSCGxxx PROCLIB member, which is OLCSTAT.

rrrrrrrrThe return code from the dynamic allocationservice.

ssssssssThe reason code from the dynamic allocationservice.

dsnThe data set name, which can be up to 44characters.

If an OM command encounters this error, thismessage is sent to the OM output exit as anunsolicited message. If IMS initialization or IMS restartencounters this error, this message is sent to thesystem console. If a utility encounters this error, thismessage is sent to the job log of the utility.


• IMS initialization fails with abend 2800, subcodeX'0001' or X'0003'.

• IMS restart fails with abend 2801, subcode X'0001'.• IMS online change command fails.

System programmer responseCorrect the dynamic allocation problem and tryIMS initialization, IMS restart, or the online changecommand again.

Module:DFSIIOC0, DFSIQ040, DFSROLC0


DFS2849A AREA areaname CONNECT TOSTR: strname FAILED. CASTOUTCLASS REQUESTED=xxxxx,ALLOCATED=yyyyy

ExplanationThe maximum cast-out class number is inconsistentbetween structure and connector. The allocated valueis the value of the structure from first connector.


The area that failed.strname

The structure to which the area attempted aconnection.

xxxxxThe requested cast-out class value.

yyyyyThe cast-out class value allocated from the firstconnector to the structure.

System actionThe area does not open.

System programmer responseDisplay the structure and delete all connections beforerestarting.

Module:DBFVXCS0




DFS2850E COLDSTART REQUIRED DUE TOGLOBAL ONLINE CHANGE

ExplanationAn attempt to warm start or emergency restart thisIMS system failed because a global online change wasperformed while this IMS was down. This IMS musthave a cold start if:

• This IMS was down during two or more global onlinechanges.

• This IMS was down during the last global onlinechange and this IMS restart type conflicts with thelast global online change that was performed.

This message is sent to the system console inresponse to a restart command such as /NRE or /ERE.

System actionIMS terminates abnormally with abend 2801, subcode12.

Operator responseStart IMS again and enter either a cold start command(/NRE CHECKPOINT 0), or enter a restart commandthat does not conflict with the last online change type.

The following table shows the types of IMS restartsthat are permitted for an IMS that was down duringonline change, with the online change type that wasperformed while the IMS was down:

Table 14. Types of online change and types of restartfor DFS2850E

Online change type Restart commands permitted

ACBLIB /NRE CHECKPOINT 0/ERE COLDBASE

ALL /NRE CHECKPOINT 0

FORMAT /NRE CHECKPOINT 0/NRE/ERE/ERE COLDCOMM/ERE COLDBASE

MODBLKS /NRE CHECKPOINT 0

Module:DFSOLCS0






DFS2851I AREA areaname (ASSOCIATETO|DISASSOCIATE FROM) STRstructure name SUCCESSFUL

ExplanationThe action on the area was successful.ASSOCIATE TO

The area areaname has started using the multi-area structure structure name. An XES connectionexists for the structure, so only association isrequired for the area.

DISASSOCIATE FROMThe area areaname has stopped using the multi-area structure structure name.

System actionVSO processing is either started or stopped for thearea.


Module(For ASSOCIATE TO) DBFVXAS0

(For DISASSOCIATE FROM) DBFVXCS0

DFS2852I AREA areaname ASSOCIATE TOSTR structure name FAILED. STRCISIZE=xx, AREA CISIZE=yy

ExplanationAssociation to the area failed because the CI size (yy)of the area is different from the CI size (xx) of the otherareas in the structure.

System actionArea open process fails.

System programmer responseChange the structure name on the DBRC registration ofthe area to a structure that has the same CI size as thearea.

Module:DBFVXAS0

DFS2853A A NEW STRUCTURE WAS CREATEDFOR AREA AAAAAAAA. REPLY 'C'TO CONTINUE OR 'R' TO RECOVER.

ExplanationThis message is generated because the user specifiedthe SVSODR startup option of WTOR. This option isused at a remote site to provide the user with anoption whether an SVSO area needs to be marked asrecovery needed or not. The user is given an optionwhenever a new structure is created for an SVSOarea at emergency restart or first area open after anemergency restart, and SVSODR=WTOR is specified.

System actionIf you select option C, IMS opens the area specified,connect to a new structure and normal processingresumes for that area. If you select option R, thespecified area is stopped and marked as recoveryneeded.

Programmer responseReply C to continue with normal processing for thearea. Reply R if the area is to be marked as recoveryneeded.

Module:DBFVXCS0

DFS2854A jobname, stepname, region,reason-FAILED SECURITY CHECK

ExplanationThis message notifies the IMS master terminaloperator that a security violation occurred. Thejobname and stepname of the user who attempted thesecurity violation are indicated. reason indicates thereason code, as shown in the following list:Code (hex)

Meaning040

The GETMAIN call failed.080

Unable to get storage (RACW) for RAS processing.084

IMS resource is not authorized for this dependentregion per SAF (RACF) check.


088IMS resource is not authorized for this dependentregion per Resource Access Security user exit(RASE) check.

08CDuring RAS security authorization processing, theinput transaction name could not be found, or IMSRACROUTE REQUEST=VERIFY,ENVIR=CREATE tobuild ACEE for a dependent region was rejectedby RACF. A security problem with the user ID fora dependent region accessing the APPL=IMSIDmight cause this problem.

090IMS RACROUTE REQUEST=VERIF, ENVIR=CREATEto build ACEE for a dependent region was rejectedby RACF.

114The find-destination routine (DFSICLF0) was notable to find the SYMBOLIC output transaction codeor logical terminal name.

System actionThe dependent region is terminated abnormally withabend 0437.

Programmer responseEnsure that your dependent region user ID isauthorized to access the IMS resources (transaction,PSBs, and LTERMs) that it is attempting to use.

Module:DFSASK00, DFSDASP0


DFS2855A APSB SECURITY CHECK FAILEDFOR odbaidid USERID=uuuuuuuuPSB=pppppppp SAF RC=xxRACROUTE=AUTH RC(yyyy,zzzz)

ExplanationThe USERID has failed SAF security check for thenamed PSB from an ODBA application.

In the message text:odbaidid

The ID of the ODBA address space connected toIMS.

uuuuuuuuUserid associated with the APSB request.

ppppppppPSB named on the APSB request.

xxSAF return code.

yyyyRACF or equivalent return code.

zzzzRACF or equivalent reason code.

System actionThe APSB request is unsuccessful. The call ends withpseudoabend 0438.


Module:DFSDASP0


DFS2855I OLCSTAT DATASET LOCKED FORGLOBAL ONLINE CHANGE

ExplanationThe DBBBATCH region failed because the OLCSTATdata set is locked for global online change.

System actionThe DBBBATCH region terminated with an 0821abend.

User responseRun the DBBBATCH region again after global onlinechange is completed.


DFS2856W DFSCGXXX OLC=olctype ONLINECHANGE TYPE MISMATCH

ExplanationAn online change type mismatch was detected duringIMS restart, XRF alternate tracking, DBCTL warmstandby emergency restart, or FDR region tracking.The checkpoint log record that this IMS is restartingfrom is defined with an online change type (local orglobal) that does not match the online change typedefined by the DFSCGxxx PROCLIB member OLC=parameter that this IMS initialized with.

This situation might be a serious error, unless youintended to change the online change type to enable





or disable global online change across an IMS warmstart or emergency restart.

Important: Perform a cold start of IMS when enablingglobal online change or falling back to local onlinechange. You should not change the online change typeacross an emergency restart or a warm start.

In the message text:olctype

The online change type defined in the DFSCGxxxPROCLIB member for this IMS.LOCAL

Local online change is enabled on this IMS.Global online change is enabled on the activeIMS.

GLOBALGlobal online change is enabled on this IMS.Local online change is enabled on the activeIMS.

System actionIMS continues processing. IMS might terminateabnormally, if it detects an error because of thismismatch.

System programmer responseIf this mismatch did not result in an IMS abend,and you did not intend to change the online changetype across an IMS emergency restart, an IMS warmstart, an XRF alternate, a DBCTL warm standby, or anFDBR region, shutdown the IMS, XRF alternate, DBCTLwarm standby, or FDBR region, change the DFSCGxxxPROCLIB member OLC= parameter to match the IMSactive, then bring the IMS, XRF alternate, DBCTL warmstandby, or FDBR region back up.

DFS2857E DIAGNOSE COMMAND INTERNALERROR - MOD=name, RSN=nnnn

ExplanationAn unrecoverable internal error was encountered whileprocessing a /DIAGNOSE command. The message isissued at any point in the code that a severe errorcondition is encountered whose root cause is internal.


The name of the module that issued the message.nnnn

A reason code. Each internal error has a uniquereason code. Generally, the reason code takesthe form xxyy, where xx is the last 2 charactersof the issuing module name, and yy is a 2-character sequential number (starting with 01 for

each module) that identifies the error that wasencountered in that module. The exception iscertain common messages issued by the SNAPresource modules, which use the form ZZyy.

System actionThe specified /DIAGNOSE command does notcomplete.


Module:DFSDGSA0, DFSDGSP0, DFSDGSZ5, DFSDGS82,DFSDGSA1, DFSDGSR0, DFSDGSZ6, DFSDGS84,DFSDGSB0, DFSDGSS0, DFSDGSZ7, DFSDGS9A,DFSDGSD0, DFSDGST0, DFSDGSZ8, DFSDGS9C,DFSDGSL0, DFSDGSU0, DFSDGSZ9, DFSDGS92,DFSDGSL1, DFSDGSZ0, DFSDGS00, DFSDGS94,DFSDGSL2, DFSDGSZ1, DFSDGS10, DFSDGS96,DFSDGSM0, DFSDGSZ2, DFSDGS20, DFSDGS98,DFSDGSM1, DFSDGSZ3, DFSDGS40, DFSDGSN0,DFSDGSZ4, DFSDGS80

DFS2858E DIAGNOSE COMMAND SEVEREERROR-reason text

ExplanationThis message indicates that an unrecoverable externalerror was encountered during process of a /DIAGNOSEcommand. The message is issued at any point in thecode that a severe error condition is encounteredwhose root cause is external.

In the message text:reason text

Identifies the specific error encountered. Thereason text can be one of the following:BCB AWE GET FAILED RC=rc

A /DIAGNOSE SNAP command was issuedwith OPTION(SYSOUT), and the command wasunable to acquire an AWE to enqueue theSNAP results to the DGS AWE processor. Thefailing return code from the BCB AWE GETcall is captured in rc in the message text. Thecommand fails and no output is written to theSYSOUT data set. This might be a temporarystorage constraint problem, or IMS might beexperiencing more serious storage problems. Ifno other storage problems are evident, reissuethe command. If the command fails again andno other storage problems are evident, contactIBM Software Support.


BLOCK STORAGE NOT AVAILABLEA /DIAGNOSE SNAP BLOCK() command wasissued and the requested primary block wasnot available.

COPY BUFFER FREESTOR FAILEDA /DIAGNOSE SNAP command was issued,diagnostic information was captured in a copybuffer, and the FREESTOR call for the copybuffer failed.

COPY FAILED: DESTRUCTIVE OVERLAPA /DIAGNOSE SNAP command was issued,diagnostic information was found, a call wasmade to the storage copy routine withouttolerate copy failures in effect, and thecopy failed because of a destructive overlapbetween the storage and the copy buffer.

COPY FAILED: INVALID STORAGE KEYA /DIAGNOSE SNAP command was issued,diagnostic information was found, a call wasmade to the storage copy routine withouttolerate copy failures in effect, and the copyfailed because of an invalid storage key.

COPY FAILED: STORAGE UNAVAILABLEA /DIAGNOSE SNAP command was issued,diagnostic information was found, a call wasmade to the storage copy routine withouttolerate copy failures in effect, and the copyfailed because of an invalid address.

DGSS BUFFER FREESTOR FAILEDA /DIAGNOSE SNAP command was issued,a DGSS storage table was allocated, and theFREESTOR call for the DGSS storage tablefailed.

ENQUEUE AWE FAILED RC=rcA /DIAGNOSE SNAP command was issuedwith OPTION(SYSOUT), and the command wasunable to enqueue the SNAP results to theDGS AWE processor. The failing return codefrom the enqueue process is captured in rcin the message text. The command fails andno output is written to the SYSOUT data set.If the problem persists, contact IBM SoftwareSupport.

NUCLEUS ADDR TABLE NOT AVAILABLEA /DIAGNOSE SNAP MODULE() commandwas issued and the DIAGNOSE CommandNucleus Module Address Table was notavailable.

STORAGE COPY FAILEDA /DIAGNOSE SNAP command was issued,diagnostic information was found, a call wasmade to the storage copy routine withouttolerate copy failures in effect, and the copyfailed.

TRACE FACILITY START FAILEDA /DIAGNOSE SNAP command was issuedwith OPTION(TRACE) and the internal call tostart tracing facilities for a DIAG trace tablefailed.



Module:DFSDGSA0, DFSDGSP0, DFSDGSZ5, DFSDGS82,DFSDGSA1, DFSDGSR0, DFSDGSZ6, DFSDGS84,DFSDGSB0, DFSDGSS0, DFSDGSZ7, DFSDGS9A,DFSDGSD0, DFSDGST0, DFSDGSZ8, DFSDGS9C,DFSDGSL0, DFSDGSU0, DFSDGSZ9, DFSDGS92,DFSDGSL1, DFSDGSZ0, DFSDGS00, DFSDGS94,DFSDGSL2, DFSDGSZ1, DFSDGS10, DFSDGS96,DFSDGSM0, DFSDGSZ2, DFSDGS20, DFSDGS98,DFSDGSM1, DFSDGSZ3, DFSDGS40, DFSDGSN0,DFSDGSZ4, DFSDGS80

DFS2859I DIAGNOSE COMMANDUNSUCCESSFUL - reason text

ExplanationA non-fatal error was encountered that preventedthe /DIAGNOSE command from completingsuccessfully. The message is issued at any point in thecode that a non-fatal, non-serious error condition isencountered.

In the message text:reason text

Identifies the specific error encountered:AOS=N WAS SPECIFIED

A /DIAGNOSE SET AOSLOG() command wasissued where AOS logging was prohibited by anIMS startup parameter.

block UNAVAILABLEA /DIAGNOSE SNAP BLOCK(block) commandwas issued when the block control block wasnot available or not defined.

CLASS INVALID WITH OUTPUT OPTIONA /DIAGNOSE SNAP command was issuedwith the CLASS() parameter, but the outputOPTION() parameter was not SYSOUT.The CLASS() option is valid only withOPTION(SYSOUT). Change the command touse OPTION(SYSOUT) or delete CLASS(), andthen reissue the command.


CLASS(class) INVALIDA /DIAGNOSE SNAP command was issuedwith the CLASS() parameter, and an invalidclass was specified. Valid values for the classare: A-Z and 0-9. Change the class to one ofthe valid values and reissue the command.

FORMAT INVALID WITH OPT(OLDS)A /DIAGNOSE SNAP command was issuedwith OPTION(OLDS) and the FORMAT keyword.The FORMAT keyword is not valid withOPTION(OLDS).

FORMAT INVALID WITH OPT(TRACE)A /DIAGNOSE SNAP command was issuedwith OPTION(TRACE) and the FORMATkeyword. The FORMAT keyword is not validwith OPTION(TRACE).

INVALID ADDRESS VALUE SPECIFIEDA /DIAGNOSE SNAP command was issuedwith ADDRESS(address) where the addressspecified was beyond the maximum addressallowed: X'7FFFFFFF'.

INVALID LENGTH VALUE SPECIFIEDA /DIAGNOSE SNAP command was issuedwith ADDRESS(address) LENGTH(length) wherethe length specified was beyond the maximumlength allowed: address + length <=X'7FFFFFFF'.

INVALID LIMIT(limit) MAX=maximumA /DIAGNOSE SNAP command was issuedwith the LIMIT() parameter, and the limitvalue was out of range for the OPTION()specified. Change the output option fromOPTION(DISPLAY) to OPTION(SYSOUT), orchange the limit to be less than or equal tothe maximum value in the message text; andthen reissue the command. See the LIMIT()parameter description for more informationabout the valid ranges for LIMIT() withOPTION(DISPLAY) and OPTION(SYSOUT).

INVALID OLR resource SHOW OPTIONA /DIAGNOSE SNAP command was issued foran OLR region where an invalid block namewas specified. The VTD, ASCB, ASSB, DPDIR,IWALE, LESEP, DRAT, and IDT blocks are notavailable, and therefore not valid, for an OLRregion.

INVALID resource SHOW OPTIONA /DIAGNOSE SNAP command was issuedwhere the SHOW option keyword or blockname was invalid for the specified resourcetype.

LIMIT INVALID WITH OPT(OLDS)LIMIT INVALID WITH OPTION(OLDS)

A /DIAGNOSE SNAP command was issuedwith OPTION(OLDS) and a LIMIT(linecount)

was specified. The LIMIT parameter is not validwith OPTION(OLDS).

LIMIT INVALID WITH OPT(TRACE)LIMIT INVALID WITH OPTION(TRACE)

A /DIAGNOSE SNAP command was issuedwith OPTION(TRACE) and a LIMIT(linecount)was specified. The LIMIT parameter is not validwith OPTION(TRACE).

NO VALID BLOCKS FOR resourceNo valid blocks were found for the specifiedresource and SHOW() options. Ensure thatthe correct resource was specified and thatvalid SHOW() options for that resource werespecified.

resource(parameter) NOT FOUNDA /DIAGNOSE SNAP command was issuedwhere the parameter for the specified resourcetype was not found.

RM(ONLY) INVALID, RM UNAVAILABLEA /DIAGNOSE SNAP command was issuedwith the RM(ONLY) parameter, and a ResourceManager is not available. Change or remove theRM() parameter and reissue the command.

SNAP RESOURCE NOT FOUNDA /DIAGNOSE SNAP command was issuedwhere the parameter for the specified resourcetype was not found.

SNAP RESOURCE NOT SPECIFIEDA /DIAGNOSE SNAP command was issuedwithout a SNAP resource type specified.

UNABLE TO GET DIAG TRACE TABLEA /DIAGNOSE SNAP command was issuedwith OPTION(TRACE) when a DIAG trace tablewas not available for use.


Operator responseCheck the command text, correct any errors, and issuethe command again.


Module:DFSDGSA0, DFSDGSP0, DFSDGSZ5, DFSDGS82,DFSDGSA1, DFSDGSR0, DFSDGSZ6, DFSDGS84,DFSDGSB0, DFSDGSS0, DFSDGSZ7, DFSDGS9A,DFSDGSD0, DFSDGST0, DFSDGSZ8, DFSDGS9C,DFSDGSL0, DFSDGSU0, DFSDGSZ9, DFSDGS92,DFSDGSL1, DFSDGSZ0, DFSDGS00, DFSDGS94,


DFSDGSL2, DFSDGSZ1, DFSDGS10, DFSDGS96,DFSDGSM0, DFSDGSZ2, DFSDGS20, DFSDGS98,DFSDGSM1, DFSDGSZ3, DFSDGS40, DFSDGSN0,DFSDGSZ4, DFSDGS80, DFSDGS90

DFS2860W EXTERNAL TRACE DATA SETLOGGING NOT AVAILABLE -REASON - N.

ExplanationIMS cannot use the external trace data sets. Nspecifies one of the following reasons:

• No storage is available for the output buffers incontrol region 24-bit private storage.

• The block size of the output data sets is less than4008 bytes.

• No external trace data sets are left. This message isusually preceded by another message reporting anerror condition.

System actionIMS external trace is started, but is not permanentlydisabled if error cleanup is successful.

Operator responseNotify the IMS system programmer.

DFS2861W TAPE/DISK DYNAMICALLOCATION FAILED FOREXTERNAL TRACE DATA SETxxxxxxxx.

ExplanationDynamic allocation failed for the ddname listed asxxxxxxxx. Verify that the DFSMDA member accuratelydescribes the data set and where it resides.

System actionIf disk data sets are used, IMS tries to log the tracetables to the remaining data set. If no disks or tapeare left for external trace use, IMS asks the operatorfor permission to log trace tables to the OLDS. SeeDFS2867A for more information.

Related information“DFS2867A” on page 805EXTERNAL TRACE NOT USABLE, REPLY "Y" TOUSE OLDS, "N" TO TRACE INCORE

DFS2862W OPEN/CLOSE ERROR ONEXTERNAL TRACE DATA SETxxxxxxxx.

ExplanationAn open or close failed for the listed data set. Thismessage should have been preceded by a system errormessage.

System actionIf disk data sets are used, IMS tries to continue usingthe remaining disk. If no more disks are available or iftape is used, IMS asks the operator for permission tolog IMS trace tables to the OLDS. If the failing data setcannot be closed and deallocated, the failing data setis unusable until IMS is restarted. See DFS2867A formore information about logging IMS trace tables to theOLDS.

Related information“DFS2867A” on page 805EXTERNAL TRACE NOT USABLE, REPLY "Y" TOUSE OLDS, "N" TO TRACE INCORE

DFS2863I LOGGING IMS TRACE TABLESTO EXTERNAL TRACE DISK/TAPEDATA SET.

ExplanationThis is a notification that IMS is logging the IMS tracetables to an external trace data set and not to theonline log (OLDS).

DFS2864I EXTERNAL TRACE DATA SETxxxxxxxx FULL - SWITCHING TOyyyyyyyy.

ExplanationDisk data set xxxxxxxx is full, and IMS is switching tothe data set yyyyyyyy.

Programmer responseIf the data on the full data set is wanted, it mustbe copied to another data set or printed. As soon asdata set yyyyyyyy is full, IMS switches back to data setxxxxxxxx.

DFS2865I OVERWRITING EXTERNAL TRACEDATA SET xxxxxxxx

ExplanationOnly one disk data set is available, and it is full. IMScloses it and reopens it. Any data currently on the dataset is lost.

DFS2866W PERMANENT WRITE ERROR ONEXTERNAL TRACE DATA SETxxxxxxxx.


ExplanationA permanent write error has occurred on the data setlisted. An operating system error should have beenissued before receiving this message.

System actionIf disk data sets are used, IMS switches to theremaining disk and continues. If no disks are availableor if tape is used, IMS stops using the external tracefacility. The operator is asked if IMS trace tables are tobe written to the OLDS. If the failing data set cannot beclosed and deallocated, the data set is unusable untilIMS is restarted.

DFS2867A EXTERNAL TRACE NOT USABLE,REPLY "Y" TO USE OLDS, "N" TOTRACE INCORE

ExplanationIMS cannot use the external trace data sets for one ofthe following reasons:

• No external trace dynamic allocation members werefound, or dynamic allocation of the found membersfailed.

• The block size of the output data set is less than4008 bytes.

• Open, close, or write errors forced the termination ofthe external trace services.

This message is usually preceded by other IMSExternal Trace error messages explaining why ExternalTrace is not usable.

Operator responseRespond with "Y" for IMS trace tables to be logged toOLDS. When OLDS logging is external, tracing to OLDScontinues until all trace logging stops. Respond with"N" for IMS tracing to be in memory only. Externaltrace initialization is attempted again if a trace issubsequently started with the LOG option.

DFS2868W INVALID BLOCKSIZE SPECIFIEDFOR EXTERNAL TRACE DATA SETnnnnnnnn

ExplanationEither of the following situations occurred:

• One of the external trace disk data sets has a blocksize smaller than the other data set

• The block size of the two external trace disk datasets is smaller than the minimum size

Both external trace data sets must have the sameblock size of at least 4020.


The DD name of the external trace data set whoseblock size is in error.

System actionIMS does not use the external trace data set in error.If both data sets have errors, message DFS2867A isissued; you can send the trace tables to the IMS log orkeep them in storage.


DFS2869W EXTERNAL TRACE TCB NOTAVAILABLE - TRACING TO OLDS

ExplanationA /TRACE SET ON TABLE cc OPTION LOGcommand was entered, but the External Trace taskcontrol block (TCB) is unavailable for use.

Operator responseIf you do not want OLDS tracing, reissue the TRACEcommand without the LOG option.

DFS2870W ABEND WHILE WRITING TOEXTERNAL TRACE DATASETddname

ExplanationAn abend occurred while writing to one of the externaltrace data sets.


The DD of the dataset for which the abendoccurred.

System actionDFSTRA40 refreshes the DCB, switches to the otherexternal trace data set and rewrites the buffers thatwere not already CHECKed. If another abend occurswith the same data set without a successful write, thedata set is marked as not usable and the system takesthe action described in message DFS2866W.


System programmer responseNothing needs to be done if the data set is usableafter DFSTRA40 recovers from the abend. If anotherabend occurs, the data set is marked as not usable. Ifthe data set is successfully deallocated, the data setcan be reused by stopping and restarting the externaltrace.

Module:DFSTRA40

Related information“DFS2866W” on page 804PERMANENT WRITE ERROR ON EXTERNALTRACE DATA SET xxxxxxxx.

DFS2900I LOG EOF BEFORE REQUIREDCKPT=xxxxxxxx FOUND

ExplanationThe utility scanned the log data set for checkpointidentification indicated by the checkpoint data set. Anend-of-file condition intervened.


Programmer responseResubmit the job with an alternate log data set.




DFS2901I I-O ERROR. SYNADAF MSGFOLLOWS:

ExplanationA SYNAD exit was taken for the data set associatedwith the ddname displayed.


Programmer responseResubmit the job after normal recovery procedures forthe particular data set have been performed.

DFS2902I AUTOMATIC SYSTEMCHECKPOINT INITIATED

ExplanationThis message is sent two minutes after an XRFtakeover if a checkpoint has not been taken bythat time. The message is sent to both the IMSMTO console and the z/OS console. A checkpoint isnormally initiated when the last terminal is switchedto the new active IMS. The new active IMS is notrestartable until the checkpoint is complete. Thismessage indicates terminal switching errors, and thatone or more terminals have not switched or have notbeen counted as switched.

System actionIMS takes a checkpoint.

Programmer responseBecause one or more terminals were not counted asswitched, an IMS logic error, VTAM logic error or timingcondition occurred during the takeover. Collect alllogs, take a console memory dump of the new activeIMS if possible, and save all other data necessary todiagnose the problem.

DFS2904A ATTEMPT TO CHANGE SEQUENCEFIELD

ExplanationThe MSDB maintenance card change file has a FIELD=keyword specifying the sequence field.

System actionThe utility terminates after issuing this message.

Programmer responseCorrect the input, and resubmit the utility run.Sequence fields cannot be altered.

DFS2905I RECOVERY FROMCHECKPOINT=yyddd/hhmmss

ExplanationThe MSDB Dump/Recovery Utility started processingthe IMS log data set at the indicated checkpoint.

System actionThe utility continues by processing all MSDB logrecords found on the log data set following theindicated checkpoint.


DFS2906I UPDATES APPLIED TO SYNCPOINT=yyddd/hhmmss

ExplanationThe MSDB Dump/Recovery utility has completedprocessing of the IMS log data set. The last Fast Pathsync point log record read by the utility was created atthe indicated date and time.

System actionThe utility continues processing.


DFS2907A LOG DATA SET MISSING ORINVALID, TERMINATE. LAST SYNCPOINT PROCESSED=xxxxx/xxxxx


ExplanationDuring main storage database (MSDB) recovery, abreak in the log sequence was detected. A log dataset is missing or invalid.

System actionThe utility terminates with return code 4.

Programmer responseMake sure that all log data sets are specified and are inthe correct sequence.

DFS2930I INITIALIZATION FAILURE -mmmmmmmm,xxxx,yyyyyyyy,zzzzzzzz- ccccc

ExplanationIMS initialization failed for module mmmmmmmm.


The failure reason code (also found in register 15at the time of abend).

yyyyyyyyThe failure return code from the requested service.

zzzzzzzzThe failure subcode from the requested service (ifapplicable).

cccccOptional text that provides further explanation ofthe error.

The following list describes the reason codes and theirassociated requested service for message DFS2930I.

Reason code (Requested service)Description

0001 (DFSXDBI0)Unable to load IMS system control blocks (IMSSCD) in members DFSBLK0x and DFSFXC0x.

0002 (IMSAUTH)Unable to authorize this IMS image to anchor itsSCD address in the SSCT.

0003 (DFSVCI0Unable to perform SVC vector table initializationwith the SCD address for this IMS image.

0004 (MVS ESTAE)Unable to establish an ESTAE routine for the IMSjob step TCB.

0005 (DFSIIN10)Unable to preload the modules specified in IMSload list.

0006 (DFSXCB00)Initialization failed for IMS DFSBCB storagemanagement services.

0007 (DFSMINI0)Initialization failed for IMS dispatcher services.

0008 (DFSCDSP)Unable to build IMS dispatcher services controlblocks for the IMS job step TCB.

0009 (DFSCIR)Unable to create the Common System ServicesITASK, DFSCSS00 (either IMODULE GETMAIN orLOAD failed).

000A (DFSCIR)Unable to create the Common Control ServicesITASK, DFSCNS00 (either IMODULE GETMAIN orLOAD failed).

000B (DFSCIR)Unable to create the Master Services (z/OSroutine) ITASK (either IMODULE GETMAIN or LOADfailed).

000C (DFSCIR)Unable to create the Storage ManagementCompression Services ITASK, DFSSTC00 (eitherIMODULE GETMAIN or LOAD failed).

000D (DFSCIR)Unable to create the Latch Management RecoveryITASK, DFSCLM20 (either IMODULE GETMAIN orLOAD failed).

000E (DFSCIR)Unable to create the Use Management RecoveryITASK, DFSUSE20 (either IMODULE GETMAIN orLOAD failed).

000F (IMSAUTH)Unable to store SSVT address in the SSCT.

0010 (DFSSCPI0)Unable to initialize the System Control Program(SCP) and related IMS control blocks. Possiblereason codes are:00000001

IMODULE GETMAIN failed for IMS systemcontrol program block (SCPB). zzzzzzzzcontains the return code from IMODULEGETMAIN.

00000002LOAD failed for TSO environment module,IKJTSOEV. zzzzzzzz contains the return codefrom MVS LOAD.

Ensure that you are running on a level of z/OSthat supports the TSO environment service.


00000003TSO environment service initialization failed.zzzzzzzz contains the return code from the TSOenvironment service.

00000004BPESTART failed to start BPE limited functionservices. zzzzzzzz contains the return codefrom BPESTART.

00000005The z/OS TCBTOKEN service failed. zzzzzzzzcontains the return code from TCBTOKEN.

0011 (DFSDREF0)Unable to process the DFSDRFxx member of theIMS PROCLIB data set.

0012 (DFSXRLM0)Unable to initialize the IRLM.

0013 (DFSSTKI0)Unable to initialize the IMS Stack Storage Manager.Possible reason codes are:00000001

IMODULE GETMAIN failed for the main stackstorage control block (SCDSTK). zzzzzzzzcontains the return code from IMODULEGETMAIN.

00000002IMODULE LOAD failed for the messageservice modules (DFSMSGC0 and DFSMSGF0).zzzzzzzz contains the return code fromIMODULE LOAD.

0014 (DFSMSGI0)Unable to initialize IMS message services. Possiblereason codes are:00000001

IMODULE GETMAIN failed for the messageservice control block (MSCB). zzzzzzzz containsthe return code from IMODULE GETMAIN.

00000002IMODULE LOAD failed for the messageservice modules (DFSMSGC0 and DFSMSGF0).zzzzzzzz contains the return code fromIMODULE LOAD.

00000003IMODULE LOAD failed for the message servicetext module (DFSMSGTX). zzzzzzzz contains thereturn code from IMODULE LOAD.

0016 (DFSSQ000)Unable to initialize shared queues. Possible errorcodes identifying the failing function are:X'1001'

Work area allocation failed.X'1004'

SQ1 AWE allocation failed.

X'1005'SQ2 AWE allocation failed.

X'1008'DFSXRPS read failed.

X'100A'CQSREG request failed.

X'100B'Loading of shared queues modules failed.

X'100C'Join of XCF group failed.

0017 (DFSRSMD0)Unable to perform resource manager initialization.Possible reason codes are:00000004

LOAD failed for IMS resource manager moduleDFSRSMR0. zzzzzzzz contains the return codefrom MVS LOAD.

00000008STORAGE OBTAIN failed for the IMS ResourceManager Parameter list block (IRMP). zzzzzzzzcontains the return code from STORAGEOBTAIN.

0000000CRESMGR ADD failed for the IMS resourcemanager DFSRSMR0. zzzzzzzz contains thereturn code from RESMGR ADD.

00000010DFSRSMD0 was passed a region identifier codethat was not valid.

0018 (DFSCSL00)Unable to initialize the Common Service Layerand related IMS control blocks. In the registersat entry to the abend, register 3 contains theDFSCSL00 return code, and register 4 contains thefailing function return code. Possible error codesidentifying the failing function are:X'1004'

IMODULE GETMAIN for DFSCSLA failed.X'1008'

IMODULE LOAD for DFSCSL10 failed.X'100C'

DFSLOADL failed for CSL module preload.X'1010'

DFSBCB GET for an AWE failed to attach SL0TCB DFSFMOD0.

X'1014'DFSSQPP ENQ failed for attach for SL0 TCB.

X'1018'DFSBCB GET for an AWE failed to attach SL1TCB DFSFMOD0.

X'101C'DFSSQPP ENQ failed for attach for SL1 TCB.


X'2nnnn'The return code from DFSCSL10.X'2004'

Parse error. A DFS3305E message isissued.

X'2008'Error reading PROCLIB member.

X'200C'Parameter validation error.

0020 (IMODULE GETMAIN)Unable to obtain storage.

0021 (IMODULE LOAD)Unable to load a module.

0022 (IMODULE DELETE)Unable to delete a module.

0023 (DFSBCB GET)Unable to obtain a control block.

0024 (DFSBCB REL)Unable to release a control block.

0025 (DFSXSTM0)Reason codes include:00000001

No LM certificate for DB feature.00000002

No LM certificate for TM feature.00000003

No LM certificate features.0026 (DFSIMPL0)

Unable to preload IMS modules. Reason codesinclude:00000004

Work area allocation failed.00000008

EPB block allocation failed.0000000C

Load of the modules failed.0027 (DFSDFN00)

Unable to initialize either the environment for thedynamic resource definition or the diagnostics andstatistics. Additional reason codes returned asyyyyyyyy and zzzzzzzz include:X'1008'

IMODULE LOAD failed for a resourceprocessing module. The reason code is thereturn code from IMODULE LOAD.

X'100C'The system was unable to get storage for theDFSDGA control block. The reason code is thereturn code from IMODULE GETSTOR.

X'1010'The system was unable to get storage for theDFSRDDA control block. The reason code is thereturn code from IMODULE GETSTOR.

X'2008'An error occurred parsing theDYNAMIC_RESOURCES section of theDFSDFxxx member of the IMS PROCLIB dataset. The reason code is the return code fromBPEPARSE.

X'200C'The system was unable to get storage for acopy of the BPEPARSE grammar. The reasoncode is the return code from IMODULEGETMAIN.

X'2010'The system was unable to get storage forBPEPARSE output area. The reason code is thereturn code from IMODULE GETMAIN

X'2014'The system was unable to get storage fordata set names defined on the RDDSDSN=parameter. The reason code is the return codefrom IMODULE GETMAIN.

X'2018'An error was detected parsing theDIAGNOSTICS_STATISTICS section of theDFSDFxxx member of the IMS PROCLIB dataset. The reason code is the return code fromBPEPARSE.

X'201C'The system was unable to get storage fora copy of the BPEPARSE grammar to parsethe DIAGNOSTICS_STATISTICS section of theDFSDFxxx member of the IMS PROCLIB dataset. The reason code is the return code fromIMODULE GETMAIN.

X'2020'The system was unable to get storagefor BPEPARSE output area for parsing theDIAGNOSTICS_ STATISTICS section of theDFSDFxxx member of the IMS PROCLIB dataset. The reason code is the return code fromIMODULE GETMAIN.

X'2024'Error parsing the REPOSITORY section of theDFSDFxxx PROCLIB member. The reason codeis the return code from BPEPARSE.

X'2028'Unable to get storage for a copy of theBPEPARSE grammar to parse the REPOSITORYsection of the DFSDFxxx PROCLIB member.The reason code is the return code fromIMODULE GETMAIN.


X'202C'Unable to get storage for the BPEPARSE outputarea for parsing the REPOSITORY section ofthe DFSDFxxx PROCLIB member. The reasoncode is the return code from IMODULEGETMAIN.

X'2030'IMS is unable to load a trace services module.Message DFS4561E contains the name of themodule and the reason code that are returnedfrom the IMODULE service.

X'2034'An unknown return code was received from thetrace services initialization.

X'2104'You specified fewer than 2 RDDSDSNson the RDDSDSN= parameter of theDFSDFxxx member of the IMS PROCLIBdata set when AUTOIMPORT=(RDDS) orAUTOEXPORT=(RDDS) were set.

X'2108'You specified AUTOIMPORT=REPO in theDFSDFxxx member of the IMS PROCLIB dataset, but no REPOSITORY section was specified,or no REPOSITORY= statement was specifiedfor the IMSRSC repository.

X'210C'You specified AUTOIMPORT=REPO andRMENV=N in the DFSDFxxx member of the IMSPROCLIB data set. IMS is not enabled to useRM services to access the IMSRSC repository,because RMENV=N is specified.

0028 (DFSDFS40)Unable to read the DFSDFxxx PROCLIB member.Possible reason codes are:00000104

IMODULE GETSTOR failed for the DFSDFAcontrol block. zzzzzzzz contains the return codefrom IMODULE GETSTOR.

00000114The DFSDFxxx PROCLIB member could not beread. zzzzzzzz contains the return code fromBPERDPDS.

0029 (DFSUSRXI)Unable to initialize the IMS user exit services.Possible reason codes are:00000004

DFSBCB GET failed for an AWE control block.zzzzzzzz contains the return code from DFSBCBGET.

00000008IMODULE GETMAIN failed for the UXDT controlblock. zzzzzzzz contains the return code fromIMODULE GETMAIN.

0000000CIMODULE LOAD failed for DFSUSRX0. zzzzzzzzcontains the return code from IMODULE LOAD.

00000104IMODULE GETMAIN failed for the CSVT controlblock. zzzzzzzz contains the return code fromIMODULE GETMAIN.

00000108IMODULE LOAD failed for DFSCSIE0. zzzzzzzzcontains the return code from IMODULE LOAD.

0000010CIMODULE LOAD failed for a callable servicesmodule (DFSCSF10, DFSCSF20, or DFSCSF30).zzzzzzzz contains the return code fromIMODULE LOAD.

00000180IMODULE LOAD failed for DFSDFN20. zzzzzzzzcontains the return code from IMODULE LOAD.

0000018CIMODULE LOAD failed for DFSUSX00. zzzzzzzzcontains the return code from IMODULE LOAD.

00000190IIMODULE LOAD failed for DFSUSX10. zzzzzzzzcontains the return code from IMODULE LOAD.

00000194DFSBCB GET failed for a USXC block. zzzzzzzzcontains the return code from DFSBCB GET.

00000198DFSBCB REL failed for a USXC block. zzzzzzzzcontains the return code from DFSBCB REL.

0000019CIMODULE GETMAIN failed for parameter liststorage. zzzzzzzz contains the return code fromIMODULE GETMAIN.

000001A0IMODULE LOAD failed for the DFSUSX90.zzzzzzzz contains the return code fromIMODULE LOAD.

For more information about what to do when thismessage appears, see abends 0070, 0071, 0077,0081, 0315, and 0718.

System actionIMS terminates with a memory dump.

Operator responseDetermine the cause of the initialization failure basedon the module name and return codes. Resubmit theIMS job after the problem has been corrected.

Module:DFSXSTM0


Related referencez/OS: LOAD return and reason codesz/OS: Return codes from the ADD function(RESMGR)Related informationAbend 0070Abend 0071Abend 0077Abend 0081Abend 0315Abend 0718

DFS2950A A CHECKPOINT REQUIRED TOSATISFY RESTART IS NOTAVAILABLE ON SYSTEM LOG

ExplanationAn attempt was made to start a subsystem, activeor tracker, but the checkpoint required to satisfy the

request, usually the cold start checkpoint, is not on thesystem log. This situation can happen because PRILOGrecords were deleted from the RECON or from remotetakeover scenarios.

System actionThe restart is terminated and the system waits foranother restart command.

Programmer responseIssue another restart command as appropriate.

Module:DFSRBCP0





http://www.ibm.com/support/knowledgecenter/SSEPH2_15.1.0/com.ibm.ims15.doc.msgs/msgs/0070.htm#imsabedn0070








DFS2957W OLCSTAT DATA SET DYNAMICALLOCATION ENCOUNTEREDAN ERROR; RETRYING THEALLOCATION

ExplanationYour attempt to warm start or emergency restart thisIMS system is in a wait state during dynamic allocationof the OLCSTAT data set. This wait occurs because theOLCSTAT data set is being held by another user. TheIMS system tries the dynamic allocation of the data setagain and continues trying until one of the followingoccurs:

• The OLCSTAT data set is no longer in use by theother user.

• The maximum number of retry attempts has beenreached.

System actionIf the OLCSTAT data set is freed by the user holding it,processing continues.

If the maximum number of attempts has beenreached, IMS terminates abnormally with 2801,subcode 1, accompanied by message DFS2848E.

Operator response:If IMS terminates with and abend code of 2801,subcode 1, determine the user that has a hold on theOLCSTAT data set. Free the data set and start IMSagain.

ModuleDFSOLCS0

Related information“DFS2848E” on page 796DYN service FAILED for ds_type, RC=rrrrrrrr/ssssssssDSN=dsnAbend 2801

DFS2958A AN ONLINE CHANGE INPROGRESS WAS DETECTEDDURING TAKEOVER, ACTION ISREQUIRED TO COMPLETE THE OLC

ExplanationThis message is issued when the OLCSTAT is lockedor not accessible during an XRF takeover. The XRFtakeover completes, but you must take action as listedin the user action section at the end of takeover.If the OLCSTAT data set was not accessible duringthe takeover and no online change commit was inprogress, the XRF takeover is allowed to proceedanyway. However, the new XRF active was unable toreplace the IMSID of the old XRF active with its IMSID.

If a MODBLKS, FMTLIB or ACBLIB online change isin progress during the takeover, and the new activesubsystem determines that it is not in sync with theOLCSTAT, an internal online change is performed at theend of the takeover. The system writes an X'70' logrecord for this internal online change.

If an ACBMBR online change is in progress during thetakeover and the new active subsystem determinesthat it is not in sync with the OLCSTAT, the unit of work(UOW) is committed at the end of takeover. DFS3497Imessages are issued with the status of the UOW. TheX'7004' and X'7005' log records are written.


User responseAfter the takeover is complete, perform these actions:

1. Issue a QUERY MEMBER TYPE(IMS) SHOW(ALL)or QUERY MEMBER TYPE(IMS) SHOW(STATUS)command and note the status of the IMS systemsin the IMSplex.

2. If the QUERY MEMBER TYPE(IMS) indicates thatone or more IMS systems in the IMSplex have thefollowing status:

• No online change state• OLCPREPC status• OLCCMT1C state and OLCSTAT are not updated

issue a TERMINATE OLC command to cleanupthe online change in the IMSplex. If you tryto complete the online change with anotherINIT OLC PHASE(COMMIT) command, it will fail,because the new active subsystem is not in anonline change state.



3. If the QUERY MEMBER TYPE(IMS) indicates thatone or more IMS systems in the IMSplex have thefollowing status:

• OLC COMMIT states of OLCCMT1C and OLCSTATis updated

• OLCCMT2C state

issue another INITIATE OLC PHASE(COMMIT)command to complete the online change in theIMSplex. Route this command to an IMS that hasthe OLCCMT1C or OLCCMT2C status.

If you route the INITIATE OLC PHASE(COMMIT)to the new active subsystem, it will fail because thenew active subsystem is not in an online changestate.

If you issue a TERMINATE OLC command toterminate the OLC, it will fail as the online change iscommitted and the OLCSTAT is updated.

4. If the QUERY OLC LIBRARY(OLCSTAT)SHOW(MBRLIST) command displays the IMSID ofthe old XRF active in the member list, but not theIMSID of the new XRF active, then the old XRFactive IMSID must be deleted from the OLCSTATdata set and the new XRF active IMS ID mustbe added to the OLCSTAT data set. You mustmake this change before you run the next INITOLC PHASE(PREPARE) command. Run the GlobalOnline Change utility (DFSUOLC0) to add the IMSIDof the new XRF active. If you are using ACBMBRonline change, run DFSUOLC0 to delete the oldIMSID. If you are using global online change, youcan either run DFSUOLC0 to delete the old IMS ID,or specify OPTION(FRCABND) on the INIT OLCPHASE(PREPARE) command.

Module:DFSOLCS0

DFS2970I OLR STARTED |RESUMED FOR NAME=partnameMASTER=masternamePST=pstnumber

ExplanationHALDB Online Reorganization has started or resumedfor the named partition. The message text includes thename of the master (mastername) and the programspecification block number (pstnumber).

Important: This message is issued after the type-1or type-2 INIT OLREORG command is processed tothe extent that OLREORG ownership is established inRECON. If the online reorganization cursor is activethen RESUMED is indicated; otherwise, STARTED isindicated.


Module:DFSORP00

DFS2971W OLR INITIALIZATION|RESUMPTION FAILEDFOR NAME=partnameMASTER=masternamePST=pstnumber RC=xx RS=yy

or

OLR TERMINATED FOR NAME=partnameMASTER=mastername PST=pstnumber RC=xx RS=yy

or

DFS2971W OLR WILL NOT BE RESUMEDFOR NAME=partname MASTER=masternamePST=pstnumber RC=xx RS=yy

ExplanationFirst form of the message: For the reason indicatedby the return and reason codes, the HALDB onlinereorganization did not complete the OLR initializationprocess to either start or resume the OLR.

Second format of the message: For the reasonindicated by the return and reason codes, the OLRterminated before all records were copied from theinput to the output set of data sets.

The message text includes the name of themaster (mastername), the program specification blocknumber (pstnumber), and the return and reason codes.For the exact cause of the termination, see the returnand reason codes in the following table:


Table 15. Return and reason codes for DFS2971W

Returncode(hex)

Reason code(dec)

Description

04(modul

e:DFSOR

P00)

04 Unexpected return code fromISWITCH

08 DFSBCB GET for QSAV failed

12 DFSCWU create work unit failed

16 IMS was restarted with COLDSYS,COLDBASE, or COLD START.

20 Restart authorization failed.

24 Deferred stop or close due to errorduring XRF takeover

28 LCRE enqueue failed.

32 The SET ownership call failed;possible causes:

• The partition database is notcapable of having OLR runagainst it.

• The REORG INTENT flag is seton in the partition database. Thepartition is being reorganized.

36 The OLR was terminated becauseFFROLR=D was specified.

40 LSO=Y environment is invalid.

08(modul

e:DFSORP00 orDFSOR

P10)

01 GETMAIN for OLR work area failed.Issued by module DFSORP10.

02 Scheduling of the OLR PSB failed.Issued by module DFSORP10.

03 Output data set creation orvalidation failed. Issued by moduleDFSORP10.

04 DFSBCB GET for QSAV failed.Issued by module DFSORP10.

05 Timer ITASK creation failed. Issuedby module DFSORP10.

06 Database in error becausebackout failed. Issued by moduleDFSORP10.

17 Another command is in progress.Issued by module DFSORP00.

C6 OLR scheduling failed. Issued bymodule DFSORP00.

1ED Required internal HALDB controlblocks were not initialized or

Table 15. Return and reason codes for DFS2971W(continued)

Returncode(hex)

Reason code(dec)

Description

accessible. Issued by moduleDFSORP00.

1EE Alter processing could not beresumed on this IMS systembecause all partitions that remainto be altered are owned by one ormore other IMS systems. Issued bymodule DFSORP00.

8031 Open error for partition. Issued bymodule DFSORP10.

0C(modul

e:DFSOR

P10)

Partition selection failed

8031 Open error for partition

C030 Authorization failure

Cxxx Other partition selection failures

10(modul

e:DFSOR

P10)

nnnn Pseudoabend during partitionselection (decimal value). Thevalue of nnnn is the abend codereturned by the issuing module.For more information about thecause of the abend, see IMS abendcodes (Messages and Codes).

14(modul

e:DFSORP10, forerrors

detected in

DFSORP20)

01 A /TERMINATE OLREORGcommand with no options wasinitiated.

02 Buffer handler call for PHDAMfailed

03 Buffer handler call for PHIDAMfailed

04 GBIDP lock failure during cursorupdate

05 GZIDP lock failure during cursorupdate

06 Buffer handler failure during cursorupdate

07 Notify failure during cursor update

0A Duplicate key found during key-sequenced data set (KSDS) insertin the primary index database

0B Update Data Set Control Block(DSCB) failed





Returncode(hex)

Reason code(dec)

Description

18(modul


detected in

DFSORP20)

nnnn Pseudoabend during DFSORP20processing (decimal value). Thevalue of nnnn is the abend codereturned by the issuing module.For more information about thecause of the abend, see IMS abendcodes (Messages and Codes).

1C(modul


detected in

DFSORP30)

nnnn Backout failure. The value of nnnnis the abend code returned bythe issuing module. For moreinformation about the cause ofthe abend, see IMS abend codes(Messages and Codes).

02 OLR terminated by a /TERMINATEOLREORG command with theFORCE option

03 Key with all X'FF' found, or errordoing chain maintenance

04 OLR termination with the ABORTwas initiated.

20(modul


detected in

DFSORP30)

nnnn Pseudoabend during DFSORP30processing (decimal value). Thevalue of nnnn is the abend codereturned by the issuing module.For more information about thecause of the abend, see IMS abendcodes (Messages and Codes).

24(modul


detected in

DFSORP30)

statuscode

Unexpected status code frominternal DL/I call

28 LCRE enqueue failed

28 nnnn HALDB online reorganizationerror occurred. Termination wasinitiated. A pseudoabend was set.


Returncode(hex)

Reason code(dec)

Description

The value of nnnn is the abendcode returned by the issuingmodule. For more informationabout the cause of the abend, seeIMS abend codes (Messages andCodes).

28(modul

e:DFSOR

P10,DFSDO

CA0)

04 The OLR for the named partition isnot automatically resumed duringthe restart of the failed subsystemdue to Fast Database Recoveryprocessing.

Important: A PST=00000 indicates the DFS2971Wmessage was issued when not running under adependent region PST, such as during Fast DatabaseRecovery processing or during OLR initialization beforeITASK creation.

System actionFirst format of the message: For an INITIATEOLREORG command that tried to start a new onlinereorganization, the cursor-active status is not recordedin the RECON. In this case, the database records inthe partition are still contained in the original set ofdata sets that were in use before the command wasentered.

For an automatic or command-initiated resumptionof an online organization for which the cursor-activestatus was already recorded in the RECON:

• The cursor-active status is still in effect.• The database records in the partition are still

contained in two sets of data sets, both of which arerequired for continued use of the partition.

• No additional database records were copied fromthe input to the output set of data sets.

Second form of the message: The cursor-active statusfor the partition was already recorded in the RECON,and the database records in the partition are stillcontained in two sets of data sets, both of which arerequired for continued use of the partition.

System programmer responseAfter the problem is corrected, start or resumethe HALDB online reorganization with the INITIATE










OLREORG command or else run an offlinereorganization.


Module:DFSORP00, DFSORP10 (For errors detected inDFSORP20, DFSORP30)

Related conceptsIMS abend codes (Messages and Codes)Related information“IMS problem determination” on page 11IMS messages and codes problemdetermination is accomplished by usingprocedures established by IBM.

DFS2972E OLR PSB BUILD FAILED. reason

ExplanationIMS was building an internal PSB for an onlinereorganization. This process encountered the errorindicated by reason, which is one of the following:

• DATA BASE IS NOT A PARTITION• MASTER IS NOT PARTITIONED• GETMAIN FAILED FOR PSB• DMB LOAD FAILED• HALDB STRUCTURE NOT ACTIVE

System actionThe online reorganization is abandoned, and the must-complete status is not recorded in the RECON.

Programmer responseFor DMB LOAD FAILED, ensure that the ACBLIBcontains the DMB with the name of the HALDB master.

For GETMAIN FAILED FOR PSB, storage might beconstrained so run the online reorganization later.

For HALDB STRUCTURE NOT ACTIVE, if the OnlineReorganization (OLR) is being resumed during IMS /ERE, ensure that the ACBLIB used at restart is thesame ACBLIB used by IMS before termination.

The other errors are probably IMS errors, so contactIBM Software Support.

Module:DFSOPSB0

DFS2973W NO RESPONSE FROM SHARINGIMS AFTER ONLINE REORG.PART=partname

ExplanationHALDB online reorganization has completed thecopying phase for the named HALDB partition and theinactive data sets are to be deleted. Data set deletionwas attempted because OPTION(DEL) was specifiedor defaulted on the INITIATE OLREORG command orwas subsequently specified on the UPDATE OLREORGcommand. However, before data set deletion wasattempted, all sharing IMS systems were notified. Allsharing IMS systems must indicate that they are nolonger using these data sets. One or more of thesesystems did not respond even after three requests.

System actionIMS already reset the cursor-active status for thepartition in the RECON and the database records inthe partition are now contained in the single set ofdata sets to which these records were copied. Tocomplete the processing, IMS attempts to delete theinactive data sets even though not all sharing IMSsystems responded. An error might result during dataset deletion if some job, such as an IMS batch job,has the data sets allocated but is unable to respondwithin the time allowed for a response. If this situationhappens, one or more of the inactive data sets arenot deleted, but the online reorganization completesanyway.

System programmer responseCheck the MVS system console log to determinewhether error messages indicate that any ofthe inactive data sets from the HALDB onlinereorganization were not deleted. After these data setsare no longer in use, delete them.

Module:DFSORP40

DFS2974I OLR COMPLETEDFOR NAME=partnameMASTER=masternamePST=pstnumber

ExplanationHALDB Online Reorganization has completed for thenamed HALDB partition. The message text includesthe name of the master (mastername) and the programspecification block number (pstnumber).


Module:DFSORP10



DFS2990E macro MACRO,RETURN=X'returncode',[ REASON=X'reasoncode', ],PART=partname DSN=dsname

ExplanationIMS internally started a macro instruction to gatherinformation about the data set dsname for the HALDBpartition partname as part of either:

• Starting a HALDB OLR for the HALDB partitionpartname.

This macro instruction completed with a register 15return code value of returncode and a register 0 valueof reasoncode. These values were not expected byIMS.

System actionIf this error occurred in starting the HALDB OLR,then the HALDB OLR is not started, but the partitionremains accessible with the original active set of datasets -- either the A-through-J and X or the M-through-V and Y data sets.

In the first two cases, one or more of the output datasets could have already been created automatically.

Programmer responseBased on the macro indicated in the message, seethe appropriate publication in the following table todetermine the cause of the error, and follow anyrecommended actions:

Table 16. Publications that contain macroinformation

Macro Publication

DEVTYPE z/OS: DEVTYPE macro specificationin z/OS DFSMSdfp Advanced Services(SC26-7400)

GETDSAB z/OS: GETDSAB - Accessing the DSABchain in z/OS MVS Programming:Authorized Assembler Services ReferenceVol 2 (SA22-7610)

LOCATE z/OS: Return codes from LOCATEin z/OS DFSMSdfp Advanced Services(SC26-7400)

OBTAIN z/OS: Reading DSCBs from the VTOCusing OBTAIN in z/OS DFSMSdfpAdvanced Services (SC26-7400)

SWAREQ z/OS: SWAREQ macro in z/OS MVSProgramming Authorized AssemblerServices Guide (SA22-7608)

Table 16. Publications that contain macroinformation (continued)

Macro Publication

TRKCALC z/OS: TRKCALC macro specificationin z/OS DFSMSdfp Advanced Services(SC26-7400)

If the error was detected in processing the INITIATEOLREORG command, reissue the command forpartition partname.

Module:DFSORA00, DFSORA10

DFS2991E UNACCEPTABLE DATA SET,REASON CODE reasoncode.PART=partname DSN=dsname

ExplanationIn determining whether to create the data set dsnamefor the HALDB partition partname, IMS found either:

• A data set of that same name. However, because ofcertain characteristics of this preexisting data set,the data set could not be used for the intendedpurpose.

• No data set of that name when there should havebeen a preexisting data set.

Case 1:In starting a HALDB online reorganization for theHALDB partition partname, IMS determined thatthe data set that was to be used as the output ofthe reorganization:

• Was not of a type that could be used for theapplicable data set

• Had certain characteristics that did not matchthose of the corresponding input data set

• Did not exist

Case 2:In loading the IMS catalog, the IMS CatalogPopulate utility found that for the HALDB partitionpartname the data set that was to be used either:

• Was not of a type that could be used for theapplicable data set

• Had certain characteristics that did not matchthe requirements of the DBD of the IMS catalog

In all of the preceding cases, reasoncode is a reasoncode for the specific problem.

The following table shows the definitions of thepossible reason codes.


http://www-01.ibm.com/support/knowledgecenter/SSLTBW_2.4.0/com.ibm.zos.v2r4.idas300/devms.htm?lang=en

http://www-01.ibm.com/support/knowledgecenter/SSLTBW_2.4.0/com.ibm.zos.v2r4.ieaa200/iea3a2_GETDSAB_____Accessing_the_DSAB_chain.htm?lang=en

http://www-01.ibm.com/support/knowledgecenter/SSLTBW_2.4.0/com.ibm.zos.v2r4.ieaa200/iea3a2_GETDSAB_____Accessing_the_DSAB_chain.htm?lang=en

http://www-01.ibm.com/support/knowledgecenter/SSLTBW_2.4.0/com.ibm.zos.v2r4.ikjb700/ikjb700_Return_Codes_from_LOCATE.htm?lang=en

http://www-01.ibm.com/support/knowledgecenter/SSLTBW_2.4.0/com.ibm.zos.v2r4.idas300/s3048.htm?lang=en


http://www-01.ibm.com/support/knowledgecenter/SSLTBW_2.4.0/com.ibm.zos.v2r4.ieaa800/iea3a8_The_SWAREQ_macro.htm?lang=en


In the table, the Environment column indicateswhether the error is detected at the beginning of oneor more of the following activities:

• HALDB online reorganization• HALDB online reorganization with the ALTER option• The loading of an IMS catalog

Table 17. Reason codes, environments, and errors detected for messageDFS2991I

Reason code

Environment Errors detected for preexisting data set

1 Any The data set is not a DASD data set.

2 Any The data set is a VSAM data set, but thedatabase is defined to use OSAM.

3 Any The data set is a PDS, PDSE, or a member of aPDS or PDSE.

4 Tracking,Reorganization

The data set is not a VSAM ESDS, but thedatabase is defined to use VSAM.

5 Any The VSAM data set does not have the REUSEattribute.

6 Reorganization The VSAM data set has a different record lengththan that of the corresponding input data set.

7 Reorganization The VSAM data set has a different controlinterval size than that of the correspondinginput data set.

8 Reorganization The VSAM ESDS has a different control intervalsize than that of the corresponding input dataset.

9 Reorganization The data set is not a VSAM KSDS. The primaryindex data set of a PHIDAM database must be aVSAM KSDS.

10 Reorganization The primary index data set of a PHIDAMdatabase (the KSDS), is defined with a differentkey offset or key length than that of thecorresponding input data set.

11 Tracking The VSAM data set has a different record lengththan that of the tracked output data set at theactive site.

12 Tracking The VSAM data set has a different controlinterval size than that of the tracked output dataset at the active site.

13 Tracking The primary index data set of a PHIDAMdatabase (the KSDS), is defined with a differentkey offset or key length than that of the trackedoutput data set at the active site.

15 Loading IMScatalog

The VSAM KSDS has a different record lengththan what is required by the DBD that definesthe IMS catalog.

17 Loading IMScatalog

The VSAM KSDS is defined with a different keyoffset or key length than what is required by theDBD that defines the catalog.

18 Any Either:

• The data set is cataloged but it is not on thevolume to which the catalog entry refers.

or

• The data set was allocated with a DDstatement that had a VOLUME parameter,but the data set was not on the referencedvolume.

19 Any The data set was allocated with a DD statement,but the data set name in the DSNAME

Table 17. Reason codes, environments, and errors detected for messageDFS2991I (continued)

Reason code

Environment Errors detected for preexisting data set

parameter does not follow the data set namingconvention defined for the data sets of thispartition.

20 Tracking,Reorganization

The output data set does not exist, butthe corresponding input data set resides onmultiple volumes and is not an SMS-manageddata set.

22 Any An unexpected condition involving the HSM-migrated data set occurred after it was recalled.This condition is likely caused by an internalerror.

23 Reorganizationwith the ALTERoption

The VSAM data set has a different controlinterval size than what is specified for thedata set in the ALTER BLOCK SIZE field of thepartition record in the RECON data set.

24 Reorganizationwith the ALTERoption

The data set has a block or control intervalsize that is not large enough to hold the largestdatabase segment that can be stored in thisdata set.

System actionIf this error occurred in starting the reorganization,then the reorganization is not started, but the partitionremains accessible with the original active set of datasets -- either the A-through-J and X or the M-through-V and Y data sets.

If this error occurred in loading the IMS catalog, thecatalog is not loaded, message DFS4483E is written,and the IMS Catalog Populate utility ends with returncode 12.

In any of these cases, one or more of the output datasets could have already been created automatically.

Programmer responseCase 1:

Before restarting the HALDB online reorganization,do one of the following:

• Delete the preexisting output data set, thusallowing IMS to create it automatically. WhenIMS creates the data set, the size, andplacement of the data set is determinedautomatically by IMS, MVS, and DFSMS/MVS,and also by parameters defined by your storageadministrator. Therefore, do not let IMS createthe data set if you need precise control over thesize and placement of the data set.

• Create a data set that is acceptable as the outputof the reorganization. Ensure that for an OSAM-defined database the output data set for thedatabase segments (one of the A-through-J orthe M-through-V data sets) is:

– A DASD data set


– Not a VSAM data set– Neither a PDS, PDSE, or a member of a PDS or

PDSE

Ensure that for a VSAM-defined database theoutput data set for the database segments (oneof the A-through-J or the M-through-V data sets)has the following characteristics:

– VSAM entry-sequenced data set (ESDS)– The REUSE attribute– A fixed-length record length identical to that of

the input data set– A control interval size that is identical to that

of the input data set

Ensure that for a PHIDAM database the outputdata set for the primary index (the X or Y dataset) has the following characteristics:

– A VSAM key-sequenced data set (KSDS)– The same key offset, key length, and record

length as the corresponding input data set– The REUSE attribute

Then reissue the INITIATE OLREORG commandto start the HALDB online reorganization forpartition partname.

Case 2:Before rerunning the IMS Catalog Populate utilityto load the IMS catalog, do one of the following:

• Delete the preexisting output data set, thusallowing IMS to create it automatically. WhenIMS creates the data set, the size, andplacement of the data set is determinedautomatically by IMS, MVS, and DFSMS/MVS,by parameters in your DFSDFxxx member thatactivates the catalog, and also by parametersdefined by your storage administrator. Therefore,do not let the IMS Catalog Populate utility createthe data set if you need precise control over thesize and placement of the data set.

• Create a data set that is acceptable as a dataset for the catalog. Ensure that a data set for thedatabase segments (one of the A-through-J datasets) is:

– A DASD data set– Not a VSAM data set– Neither a PDS, PDSE, or a member of a PDS or

PDSE

Ensure that a data set for the primary index, ILEdata set, or secondary index has the followingcharacteristics:

– VSAM key-sequenced data set (KSDS).

– The key offset, key length, and record lengthrequired by the DBD for the IMS catalog.

– These requirements are shown above. TheREUSE attribute.

Then, rerun the IMS Catalog Populate utility to loadthe catalog.

Module:DFSORA00

DFS2992E CSI RETURN CODE=4, [ { CATALOGERROR, | DATA SET ERROR, } ]CATALOG MANAGEMENTRETURN CODE=cmreturncodeREASON CODE=cmreasoncodeMODULE=cmmoduleidPART=partname DSN=dsname

or

CSI RETURN CODE=csireturncode [ REASONCODE=csireasoncode ] PART=partnameDSN=dsname

ExplanationIMS internally invoked the Catalog Search Interface(CSI) to gather information about the data set dsnamefor the HALDB partition partname as part of either:

• Starting a HALDB online reorganization for thepartition.

• Loading the IMS catalog

The CSI completed with a CSI return code value asshown in the message text. Information about theseCSI return codes is in z/OS DFSMS Managing Catalogs(SC26-7409).

For the first form of the message (when the CSIreturn code is 4), a Catalog Management error wasdetected. In this case, cmreasoncode, cmreturncode,and cmmoduleid are the Catalog Managementreason code, return code, and two-character moduleidentification, respectively. Information about thisCatalog Management error information is in z/OS MVSSystem Messages Vol 6 (SA22-7636) under messageIDC3009I.

For the second form of the message (when the CSIreturn code, csireturncode is other than 4), a CSI errorwas detected. For CSI return code 8, csireasoncode isthe CSI reason code. Information about this CSI errorinformation is in z/OS DFSMS Managing Catalogs.

These values were not expected by IMS.


System actionIf this error occurred in starting the reorganization,then the reorganization is not started, but the partitionremains accessible with the original active set of datasets: either the A-through-J and X or the M-through-Vand Y data sets.

If this error occurred while loading the IMS catalogwith the IMS Catalog Populate utility (DFS3PU00),the IMS catalog is not loaded, message DFS4483Eis written, and the DFS3PU00 utility ends with returncode 12.

In any of these cases, one or more of the data sets thatwere to have been created automatically could havebeen created already.

Programmer responseBased on value of the CSI return code, refer to z/OSDFSMS Managing Catalogs to determine the cause ofthe error, and follow any recommended actions.

Then if the error was detected in processing theINITIATE OLREORG command, reissue the commandfor partition partname.

If this error occurred while loading the IMS catalogwith the DFS3PU00 utility, rerun the utility.

Module:DFSORA80

Related referencez/OS: CSI return codes for general purposeregister 15z/OS: CSI return codes 4 and 8Related informationz/OS: IDC3009I

DFS2993E NON-DASD DATA SET.DEVICE CLASS=X'devclass'PART=partname DSN=dsname

ExplanationThe data set dsname, which is one of the data setsof the HALDB partition partname, is not a DASD dataset. This data set was being used by a HALDB onlinereorganization or by the IMS Catalog Populate utility(DFS3PU00) to load the IMS catalog. (The deviceclass reported by the internally executed DEVTYPEmacro instruction is devclass (hexadecimal) ratherthan X'20'.) This is inconsistent with its use as part of adatabase.

System actionIf this error occurred in starting the reorganization,then the reorganization is not started.

If this error occurred while running the CatalogPopulate utility to load the catalog, the catalog is notloaded, message DFS4483E is written, and the utilityends with return code 12.

In any of these cases, one or more of the required datasets might have been created.

Programmer responseChange the data set dsname to refer to a DASD dataset that can be used for a HALDB.

After the corrections are complete, restart the HALDBonline reorganization or rerun the DFS3PU00 utility,whichever was running at the time of the error.

Module:DFSORA00

DFS2994E IDCAMS RETURN CODEreturncode CREATING AN ONLINEREORG OUTPUT DATA SET.PART=partname DSN=dsname

ExplanationIMS tried to create the VSAM data set dsname for theHALDB partition partname as part of either:

• Starting a HALDB online reorganization for thepartition.

• Loading the IMS catalog

Access Method Services (IDCAMS) gave a return codeof returncode.

System actionThe message, if any, produced by IDCAMS wasdisplayed before this message.

For return code 4, the data set is assumed to havebeen created. In this case, none of the followingactions apply, and processing continues.

If this error occurred in starting the reorganization,then the reorganization is not started, but the partitionremains accessible with the original active set of datasets -- either the A-through-J and X or the M-through-V and Y data sets.

If this error occurred while loading the IMS catalogwith the IMS Catalog Populate utility (DFS3PU00),the IMS catalog is not loaded, message DFS4483E iswritten, and the utility ends with return code 12.

In any of these cases, if the data sets were to becreated automatically, one or more of the data setsmight have been created.


http://www-01.ibm.com/support/knowledgecenter/SSLTBW_2.4.0/com.ibm.zos.v2r4.idac100/c1055.htm?lang=en



https://www-01.ibm.com/support/knowledgecenter/en/SSLTBW_2.4.0/com.ibm.zos.v2r4.ieam600/idc3009i.htm

Programmer responseSee the z/OS MVS System Messages Vol 6 (GOS - IEA)(SA22-7636) to determine the cause of the error, andfollow any recommended actions.


If this error occurred while loading the IMS catalogwith the DFS3PU00 utility, after the error is correctedrerun the DFS3PU00 utility.

Module:DFSORA20

DFS2995E IDCAMS RETURN CODE returncodeDELETING AN ONLINE REORGINPUT DATA SET. PART=partnameDSN=dsname

ExplanationIMS tried to delete the VSAM input data set dsnamefor the HALDB partition partname as part of either:

• Completing a HALDB online reorganization for thepartition.

Access Method Services (IDCAMS) gave a return codeof returncode.

System actionThe message, if any, produced by IDCAMS wasdisplayed before this message.

The reorganization is still considered to havecompleted successfully, and there is now a single newactive set of data sets for partition partname--eitherthe A-through-J and X or the M-through-V and Y datasets.

Programmer responseSee z/OS MVS System Messages, V6 (GOS-IEA) todetermine the cause of the error, and follow anyrecommended actions, then delete the data set if ithas not already been deleted.

Module:DFSORA20

DFS2996E NOT ENOUGH DASD SPACE.ERROR REASON=X's99errorcode'[ SMS REASON=s99ersn ]BLOCKS=blocks BLKSIZE=blksizeVOLUMES=volcount{ UNIT=SYSALLDA | STORAGECLASS=storageclassname }PART=partname DSN=dsname

ExplanationIMS tried to create the OSAM data set dsname for theHALDB partition partname as part of either:

• Starting a HALDB OLR for the partition.• Loading the IMS catalog

The internally executed DYNALLOC macro instruction(SVC 99) that was used for this purpose reported thatthe data set could not be created because of DASDspace or DASD volume constraints. The requestedspace was blocks blocks, each with a block size ofblksize. There were volcount volumes requested.

If the text showing the group name (SYSALLDA)appears in the message text, the attempt was tocreate a non-SMS-managed data set because thecorresponding input data set was not SMS-managed.If the text showing the storage class appears, thenthe attempt was to create an SMS-managed dataset using storage class storageclassname because thecorresponding input data set was SMS-managed andwas created using that storage class.

If the reorganization was being started, these spaceallocation values were derived from the correspondinginput data set.

For further information of this error, see the z/OSMVS Programming: Authorized Assembler ServicesGuide (SA22-7608). The value s99errorcode is thehexadecimal value of the error reason code (fieldS99ERROR in the SVC 99 request block) that isprovided when the DYNALLOC macro instruction (SVC99) fails with return code 4. In the SMS case,s99ersn is the SMS reason code (field S99ERSN inthe SVC 99 request block extension). The SMS reasoncode corresponds to the message number of an IGDmessage describing the error. For further informationabout the IGD message, see the z/OS MVS SystemMessages Vol 8 (IEF - IGD) (SA22-7638).


If this error occurred while loading the IMS catalogwith the IMS Catalog Populate utility (DFS3PU00), thecatalog is not loaded, message DFS4483E is written,and the utility ends with return code 12.

In any of these cases, if the data sets were to havebeen created automatically, one or more data setsmight have been created before the error occurred.


Programmer responseDetermine whether the requested space (blocksblocks of size blksize) is required for the output dataset. In some cases, this space allocation request couldinclude space acquired in a secondary allocation forthe input data set and might not be required for thereorganized database. Then either:

• Ensure that there is sufficient DASD space on thevolumes referenced by the group name SYSALLDA(for the non-SMS-managed case) or referenced bythe storage class storageclassname (for the SMS-managed case), possibly by scratching unneededdata sets. The primary allocation amount (blocksblocks of size blksize) must be available in a total ofno more than five extents on a single volume. In theSMS-managed case, if the storage class definitionincludes the GUARANTEED SPACE attribute, then theprimary allocation amount must be available and isallocated on each of the volumes (rather than on justthe first volume).

• Create and catalog this output data set yourself. Inthis case, you can reserve whatever amount of spaceyou choose, and you can control the number ofvolumes. See Allocating OSAM data sets (DatabaseAdministration), for information about allocatingOSAM data sets along with a technique for pre-allocating multi-volume data sets.


If this error occurred while running the DFS3PU00utility to load the IMS catalog, rerun the utility.

Module:DFSORA20

Related referencez/OS: Interpreting error reason codes fromDYNALLOCz/OS: IGD messages

DFS2997E DATA SET ALLOCATED TOANOTHER JOB AND CANNOTBE CREATED. PART=partnameDSN=dsname



Creating the data set required that the data set beallocated as though DISP=NEW had been specified ona DD statement through JCL. However, a data set of

the same name was already in use by another job,causing the allocation to fail.



In any of these cases, other data sets might have beencreated before the error occurred.

Programmer responseEnsure that no other job is using a data set of the namedsname even if that data set is not cataloged and evenif that data set is not intended to be the same dataset as the output of the reorganization or as an IMScatalog data set.



Module:DFSORA20

DFS2998E [ DATA SET CREATION ERROR.| UNALLOCATION FAILURE. ]RETURN=returncode [ { INFO.REASON=X's99infocode' | ERRORREASON=X's99errorcode' } ][ SMS REASON=s99ersn ]BLOCKS=blocks BLKSIZE=blksizeVOLUMES=volcount{ UNIT=SYSALLDA | STORAGECLASS=storageclassname }PART=partname DSN=dsname



As indicated by the message text, the internallyexecuted DYNALLOC macro instruction (SVC 99)reported one of these two problems:


http://www.ibm.com/support/knowledgecenter/SSEPH2_15.1.0/com.ibm.ims15.doc.dag/ims_allocateosamds.htm#ims_allocateosamds

http://www.ibm.com/support/knowledgecenter/SSEPH2_15.1.0/com.ibm.ims15.doc.dag/ims_allocateosamds.htm#ims_allocateosamds



http://www-01.ibm.com/support/knowledgecenter/SSLTBW_2.4.0/com.ibm.zos.v2r4.ieam800/iea3m8_IGD_messages.htm?lang=en

1. The data set could not be created.2. The data set that was just created successfully

could not be unallocated from the IMS job.

The requested space was blocks blocks, each witha block size of blksize. There were volcount volumesrequested.

When the text showing the group name (SYSALLDA)appears in the message text, the attempt was tocreate a non-SMS-managed data set. If the textshowing the storage class appears, then the attemptwas to create an SMS-managed data set using storageclass storageclassname.

If this error occurred during a HALDB onlinereorganization, the choice of creating an SMS-managed or non-SMS-managed data set is based onthe corresponding input data set.

If this error occurred during the loading of anIMS catalog by the IMS Catalog Populate utility(DFS3PU00), then the choice of creating an SMS-managed or non-SMS-managed data set is based onthe presence or absence of the STORCLAS parameterin the DFSDFxxx member that activated the IMScatalog.

If the reorganization was being started, these spaceallocation values were derived from those of thecorresponding input data set.

In the message text:returncode

Is the decimal value of the register 15 return codeprovided by the DYNALLOC macro instruction (SVC99).

s99infocodeIs the hexadecimal value of the information reasoncode (field S99INFO in the SVC 99 request block).

s99errorcodeIs the hexadecimal value of the error reason code(field S99ERROR in the SVC 99 request block).

s99ersnIs, for the SMS case, the SMS reason code (fieldS99ERSN in the SVC 99 request block extension).The SMS reason code corresponds to the messagenumber of an IGD message describing the error.



In any of these cases, other data sets might have beencreated before the error occurred.

Programmer responseDetermine the meaning of returncode, s99info,s99errorcode, and s99ersn, as applicable. Follow anyrecommended actions to correct the error.



Module:DFSORA20

Related referencez/OS: Interpreting error reason codes fromDYNALLOCz/OS: IGD messages

DFS3000I SUCCESSFUL COMPLETION OF DBREORG

ExplanationPartial Database Reorganization has completedsuccessfully.

System actionProcessing terminated normally.


http://www-01.ibm.com/support/knowledgecenter/SSLTBW_2.3.0/com.ibm.zos.v2r3.ieaa800/erc.htm


http://www-01.ibm.com/support/knowledgecenter/SSLTBW_2.3.0/com.ibm.zos.v2r3.ieam800/iea3m8_IGD_messages.htm



DFS3001W INVALID FORMAT. STATEMENTDID NOT BEGIN BEFORE COLUMN17

ExplanationStatement did not begin in a column between 1 and16.

System actionProcessing continues until all control statements havebeen analyzed. Then the step terminates.

Programmer responseCorrect the error in the control statement, and rerunthe job.

DFS3002W INVALID KEYWORD INPRECEDING STATEMENT COLUMN= nn

ExplanationKeyword beginning in column nn is invalid.

System actionProcessing continues until all control statements havebeen analyzed. Then the step terminates.


DFS3003W ILLEGAL CONTINUATION

ExplanationEither the ending character in the input string was acomma and a blank was found in column 72, or theending character was not a comma and a nonblankcharacter was found in column 72.

System actionProcessing continues until all control statements havebeen analyzed. The step then terminates.


DFS3004A FROMAREA INVALID FOR HIDAMOR KEYRANGE INVALID FORHDAM

ExplanationFROMAREA can only be specified for HDAM andKEYRANGE can only be specified for HIDAM.


Programmer responseCorrect the error in the control statements, and rerunthe job.

DFS3005A REQUIRED KEYWORD MISSING,KEYWORD = keyword

ExplanationThe indicated required keyword is missing.



DFS3006A INVALID KEYWORD FOR THISSTEP ON PRECEDING STATEMENT,KEYWORD = keyword

ExplanationThe keyword indicated is invalid for this step.




DFS3007I SORT CORE SIZE NOT SPECIFIEDON THE EXEC PARMS, SORT MAINSTORAGE SIZE IS DEFAULTED TOCORE=MAX

ExplanationYou did not specify a parameter for the sort core sizeon the EXEC statement for the DFSUCUM0 utility or theDFSURG10 utility. The default CORE=MAX is used.

System actionProcessing continues. The default sort core value sizeis used.

ModuleDFSUCMN0, DFSURG10

DFS3008W KEYWORD PREVIOUSLYSPECIFIED, KEYWORD = keyword

ExplanationThe keyword indicated has been specified previouslyin another input statement and only one keyword ofthis type is allowed.



DFS3009W FROMAREA AND KEYRANGEARE MUTUALLY EXCLUSIVEKEYWORDS

ExplanationFROMAREA and KEYRANGE have both been specified.FROMAREAs can only be used with HDAM databasesand KEYRANGEs may only be used with HIDAMdatabases.



DFS3010W INVALID OPERAND INPRECEDING STATEMENT FORKEYWORD = keyword, COLUMN =nn

ExplanationAn invalid operand has been found for the keywordindicated in the previous statement.



DFS3011W MORE THAN 10 RANGESSPECIFIED

ExplanationNo more than 10 KEYRANGEs or FROMAREAs areallowed. No more than 10 TOAREAs are allowed aftereach FROMAREA or KEYRANGE.



DFS3012W DBDLIB DOES NOT CONTAINdbdname

ExplanationThe DBD named is not contained in the DBDLIB.




DFS3013W DBD dbdname DOES NOT HAVE HDACCESS METHOD

ExplanationThe DBD named is not a HDAM or HIDAM database.



DFS3014W DATA SET GROUP(S) SPECIFIEDON INPUT STATEMENTS DO NOTMATCH DBD dbdname DSGs

ExplanationThe data set groups used in the TOAREA inputstatements are not the same as found in the DBD.



DFS3015A INTERNAL ERROR IN DFSPRDBD

ExplanationModule DFSPRDBD has encountered an error thatprevents further processing.

System actionThe step is abnormally terminated with abend 0310.

Problem determination2, 3, 8, 17a, 18, 19 35


DFS3016A LCHILD ENTRY DOES NOT EXISTIN DBD dbdname FOR segment-name

ExplanationNo LCHTAB entry was found in related database forlogical child in primary database.



Problem determination2, 3, 8, 17a, 18, 19, 35


DFS3017A MORE THAN 49 RELATED DATABASES

ExplanationThe limit of 49 related databases has been exceeded.Partial Database Reorganization cannot be used forthis reorganization.




DFS3018A MORE THAN 500SEGMENTS PARTICIPATING INREORGANIZATION


ExplanationThe limit of 500 segments participating inreorganization has been exceeded. Partial DatabaseReorganization cannot be used for this reorganization.




DFS3019 INSUFFICIENT STORAGEAVAILABLE IN HIOP

ExplanationA command was not processed because there isinsufficient storage in the communication input/outputpool, which resides above the 16 megabyte line(HIOP).


Programmer responseThis condition can be a temporary condition that canbe resolved by reentering the command later. If thisfails, notify the system programmer.

Module:DFSICLN2


DFS3020 UNABLE TO OBTAIN AN AWEFROM DFSBCB

ExplanationA command was not processed because anAsynchronous Work Element (AWE) could not beobtained from IMS BCB services.


Programmer responseThis problem can be a temporary condition that canbe resolved by reentering the command later. If thisattempt fails, notify the system programmer.

DFS3021W DIRECT ADDRESS POINTERSIN RELATED HISAM DATABASEdbdname NOT ALLOWED

ExplanationA related HISAM database has direct addresspointers to the primary database. Partial DatabaseReorganization cannot be used to do thisreorganization.

System actionThe step is terminated.

DFS3022W SYNCPOINT PHASE 1 FAILED DUETO FAILURE IN OBTAINING SPACEFOR 5612 LOG RECORD.

ExplanationProgram DBFSYN10 received a return code 16(RC=16) from the Fast Path log processing module(DBFSLOG0). It could not obtain a control block forthe 5612 log record using the storage manager servicemacro DFSBCB.


Programmer response:Increase Common Service Area (CSA) storageallocation.

DFS3023A MORE THAN 500 SCAN ANDRELOAD ACTIONS REQUIRED FORPOINTER RESOLUTION

ExplanationThe limit of 500 scan and reload actions forlogically related segment pointer resolution has beenexceeded. Partial Database Reorganization cannot beused for this reorganization.


Problem determination:2, 3, 8, 17a, 18, 19, 35





DFS3024W RAS SECURITY HAS SUPPRESSEDNNNNNNNN ICH408I MESSAGESFOR REGION YYYYYYYY

ExplanationRAS security has suppressed multiple ICH408Imessages because there is a RACF definition errorfor the identified dependent region. This messageis issued to let you know that RAS security isstill performing ICH408I message suppression forthe dependent region and the number of ICH408Imessages suppressed.

In the message text:NNNNNNNN

The number of ICH408I suppressedYYYYYYYY

The dependent region name

System action:The unauthorized transaction remains in the messagequeue and could be processed by another eligibledependent region or another IMS system in anIMSplex. Processing continues.

Programmer response:Locate the preceding DFS2497W, message, whichspecified the unauthorized transaction for thespecified region. Follow the response in theinformation for DFS2497W to resolve the problem.


Module:DFSSCHR0

Related information“DFS2497W” on page 717ICH408I MESSAGES ARE SUPPRESSED FORREGION YYYYYYYY FOR TRAN ZZZZZZZZ BYRAS SECURITY“IMS problem determination” on page 11IMS messages and codes problemdetermination is accomplished by usingprocedures established by IBM.

DFS3025A INTERNAL ERROR IN DFSPRABC

ExplanationModule DFSPRABC has encountered an error thatprevents further processing.


Problem determination:2, 3, 8, 17a, 19, 35


DFS3026A DFSPRCOM DATA SET CANNOT BEOPENED

ExplanationOpen failed for the communication data set, DDNAMEDFSPRCOM.


Programmer responseEnsure that the communication data set exists and hasbeen included in the DD statements for this step.



DFS3027I NO PSB GENERATED FORTHIS EXECUTION OF PARTIALREORGANIZATION

ExplanationThe PSB parameter was not included in the input. Thedefault for this parameter is no PSB generation.

System actionNo PSB is generated for this execution.

Programmer responseIf a PSB is required, rerun step 1 with PSB=psbnamespecified.

DFS3028A UNSUCCESSFUL OPEN OF ddnameDATA SET




ExplanationThe system could not open the data set identified inthe message text by ddname.


Programmer responsePerform IMS backout facility to undo changes madein step 2 of Partial Database Reorganization (PDBR).Ensure that DD statements for this data set areincluded, and specifications are correct.


DFS3029A UNSUCCESSFUL WRITE TOddname DATA SET

ExplanationThe named data set had a write error.




DFS3030A UNSUCCESSFUL READ FROMddname DATA SET

ExplanationThe named data set had a read error.


Programmer responsePerform IMS backout facility to undo changes madeduring step 2 of Partial Database Reorganization(PDBR).

Problem determination2, 3, 8, 17c, 18, 19, 35


DFS3031A UNSUCCESSFUL CLOSE OFddname DATA SET

ExplanationThe named data set could not be closed.


Problem determination2, 3, 8, 17c, 18, 19, 35


DFS3032A INTERNAL ERROR IN DFSPRWFM

ExplanationModule DFSPRWFM has encountered an error thatprevents further processing.


Programmer responsePerform IMS backout facility to undo changes.



DFS3033A DBDS DO NOT MATCH, STEP1 DBD=dbdname, STEP 2DBD=dbdname





ExplanationThe DBD specified in the step 2 input is not the sameas the DBD specified in step 1.

System actionPSBGEN is terminated because of specification error.


DFS3034A PREMATURE END OF FILE ONCOMMUNICATIONS DATA SET

ExplanationEnd of file was reached before all the records passedfrom step 1 to step 2 on the communication data set(DFSPRCOM) were read by step 2.


Programmer responseRerun step 1 to recreate the communications data set.



DFS3035A STEP 1 HAS TERMINATED AFTERPHASE phase-name

ExplanationThe phase shown in the message text encountered anerror that prevents further processing.



DFS3036W UNSUCCESSFUL COMPLETIONOF PARTIAL DATA BASEREORGANIZATION

ExplanationAn error has occurred that prevents successfulcompletion of Partial Database Reorganization.




DFS3037A STATUS CODE cc RETURNED FROMDL/I CALL ON RESTART ATTEMPT

ExplanationAn error status code of 'cc' was returned by DL/I on arestart call.





DFS3038A CHECKPOINT nnn NOTSUCCESSFULLY TAKEN; RESTARTNOT POSSIBLE

ExplanationThe checkpoint identified in the message text by nnnwas not successful. Therefore a restart is not possible.




Programmer responseYou must recover the database and rerun a PartialDatabase Reorganization from the beginning.



DFS3039A INSUFFICIENT REGION SIZE

ExplanationThere was not enough storage available for step 2 tobuild its control blocks.

System actionThe step is abnormally terminated with abend U0310.

Programmer responseIncrease the region size and rerun step 2.



DFS3040A INVALID PCB LIST-TOO [SHORT|LONG]

ExplanationThe PSB contained too few or too many PCBs andcannot be used for this run of Partial DatabaseReorganization.


Programmer responseCorrect the error in the PSB, and rerun the job.

Problem determinationIf PSB was generated from step 1 of Partial DatabaseReorganization (PDBR), then do 2, 3, 8, 17a, 18, 19, 35


DFS3041W TOAREA rbn-number TO rbn-number FOR DSG data set-group-name EXTENDS BEYONDCURRENT END OF DATA BASE

ExplanationThe TOAREA specified extends beyond the current endof the database.


Programmer responseCorrect the error in the control statements, and rerunthe job.

DFS3042A RELOAD COUNT NOT EQUALTO UNLOAD COUNT FOR ALLSEGMENTS

ExplanationThe number of segments loaded does not equal thenumber of segments unloaded. See the range reloadstatistics for further information.



Problem determination:2, 3, 5, 8, 17a, 18, 19, 35








DFS3043A NO PRIME INDEX ENTRY IN DBDFOR ddname

ExplanationNo primary index data set was found for the HIDAMdatabase identified by ddname.





DFS3044A RBA IN PRIME INDEX NOT EQUALTO RBA OF UNLOADED SEGMENT

ExplanationThe relative byte address (RBA) in the primary indexwas not equal to the relative byte address of theunloaded segment.


Programmer responsePerform IMS backout facility to undo changes madeduring step 2 of the Partial Database Reorganization(PDBR).



DFS3045W FROM AREA rba-number TOrba-number NOT IN ROOTADDRESSABLE AREA

ExplanationThe FROMAREA specified was not wholly contained inthe root addressable area.



DFS3046W NO DATABASE RECORDS INFROMAREA/KEYRANGE STARTINGAT rba-number/key-value

ExplanationNo records were found in the range indicated.



DFS3047A SORT xx FAILEDIMS messages

ExplanationA bad return code was returned from the PartialDatabase Reorganization sort. xx identifies the SORTSTEP where the problem occurred.


Programmer responseUse IMS backout facility to undo changes made duringstep 2 of Partial Database Reorganization (PDBR).








DFS3048A END OF DBT WITHOUT IMRMATCH

ExplanationA specific database was not found in the databasetable, based on an index maintenance record.





DFS3049A UNEXPECTED EOF ON WF4

ExplanationAn end of file condition occurred for work file 4 whiletrying to locate a B index work record that matchesthe IMS index maintenance record currently beingprocessed.


Programmer responseUse IMS Database Backout utility to undo changesduring step 2 of Partial Database Reorganization(PDBR).



DFS3050A INVALID RECORD TYPE xx IN DWR

ExplanationA data work record was encountered that contained aninvalid record type identified by xx in the message text.This record type is not defined to the system.


Programmer responseUse IMS backout facility to undo changes during step 2of Partial Database Reorganization (PDBR).









DFS3051A NO DMB FOR DATABASE ddname

ExplanationThe data management block was not found in thedirectory (DDIR). This problem is an IMS internal error.




DFS3052A PERMANENT READ ERROR FORSEGMENT AT RBA rba-number

ExplanationA permanent read error has occurred for the relativebyte address (RBA) indicated.


Programmer responseUse IMS backout facility to undo changes made duringstep 2 of PDBR.



DFS3053A INVALID RETURN FROM DL/ICALL function, dbdname,procopt,segment-name,level

ExplanationA return code other than bb, GA, or GK was returnedfrom a DL/I GU call.





DFS3054A INTERNAL ERROR IN MODULEDFSPRIMS

ExplanationModule DFSPRIMS has encountered an error thatprevents further processing.





DFS3055A INVALID PHYSICAL TWIN CHAIN






ExplanationAn invalid physical twin chain was encounteredunloading a HIDAM root.





DFS3056I STATUS CODE cc RETURNEDFROM DL/I CALL ON CHECKPOINTATTEMPT

ExplanationA status code of cc was returned on a DL/I checkpointcall.


DFS3057I ATTEMPT TO WRITE TO DPRWF6FAILED; CHECKPOINT 'nnn' NOTTAKEN

ExplanationA write error occurred writing checkpoint nnn.Restarting, if needed, is not possible.


DFS3058A STATUS CODE cc RETURNED FROMDL/I ON OPEN ATTEMPT

ExplanationOpen error on the index maintenance file hasoccurred.


Programmer responsePerform IMS Backout utility to undo changes madeduring step 2 of Partial Database Reorganization(PDBR).



DFS3059A INVALID RECORD TYPE xx IN XWR

ExplanationAn index work record was encountered whichcontained a record type code that is not defined to thesystem.


Programmer responsePerform IMS Backout utility to undo changes madeduring step 2 of PDBR.



DFS3060I UNRESOLVED IN DOUBTIN AREA=xxxxxxxx, COMMANDREJECTED

ExplanationA command that sent a DEDB area offline (suchas, /STOP AREA, UPDATE AREA STOP(SCHD), /DBRAREA or UPDATE AREA STOP(ACCESS)) was enteredfor area xxxxxxxx. This area has unresolved in-doubtdata. The command is rejected to protect dataintegrity.






Programmer responseResolve in-doubt data and reissue the command.

DFS3061I VSO AREA aaaaaaaa HASI/O TOLERATED CI, COMMANDREJECTED

ExplanationThe area aaaaaaaa is a VSO area and has I/Otolerated data from an XRF takeover. A command thattook the area offline (such as /STOP AREA, /DBRAREA, UPDATE AREA STOP(ACCESS), or /VUNLOADAREA) was entered for the area, and the command wasrejected to protect data integrity.


Operator responseEnter either the IMS /UNLOCK SYSTEM or the AVMUNLOCK command to purge I/O toleration EEQEs. Thenenter the command again.

Module:DBFARDC0

DFS3062I PRELOAD ACTIVE INAREA=areaname, COMMANDREJECTED

ExplanationPRELOAD is active for area, areaname, and thecommand was rejected to avoid an abend.


Programmer responseReissue the command.

DFS3063A DYNAMIC UNALLOCATION FAILEDFOR DD ddname

ExplanationDuring database recovery, the Database Recoveryutility was unable to deallocate the target data setidentified by ddname.

System actionThe Database Recovery utility terminates abnormallywith user code 0302. Register 15 contains theDYNALLOC error reason code for unallocation failure.

Programmer responseEnsure that the image copy data set was correct. Ifnot, correct the JCL and resubmit the job.

Module:DFSURT00

Related referencez/OS: Interpreting error reason codes fromDYNALLOCRelated informationIMS abend 0302

DFS3064A DYNAMIC ALLOCATION FAILEDFOR DD ddname

ExplanationDynamic allocation failed for the referenced ddname.

System actionProcessing involving this data set is halted.

Programmer responseEnsure that the data set exists and resides in thecurrent catalog structure.

Module:DFSURT00, DFSUDMP0, DFSUDMT0

DFS3065I UTILITY ACTIVE INAREA=areaname, COMMANDPENDING UTILITY TERMINATION

ExplanationFast Path utility active for area. At utility I/O, status FHor AO is issued, and the command is processed. Theutility terminates before completion.

System actionThe /DBR or /STOP command is processed bututility cleanup and disconnect occur before commandexecution.


Module:DBFARDA0





DFS3067A IMS xxxxxxxx WAITING FORSYNCHRONIZATION WITH OTHERFAILED IMS SYSTEMS. REPLY"OK" TO CONTINUE

ExplanationThis message is generated at an IMS emergencyrestart when the OPTION SYNCPLEX keyword andparameter have been entered.

System actionThe IMS system waits for a reply before startingnormal processing.

Programmer responseWhen the IMS systems that failed have all beenrestarted and are waiting at the WTOR, reply OK to theWTOR.

Module:DFSRST00

DFS3069I MINIMUM VALUE SUBSTITUTEDFOR LOW/HIGH BLOCK NUMBER

ExplanationLow or high block number for SURVEYOR TOAREAprocessing was less than the minimum value of 2.

System actionThe low/high block number takes on the minimumvalue of 2.

DFS3070A UNSUCCESSFUL OPEN OF ddnameDATA SET

ExplanationThe system was not able to open the data setindicated in the message.

System actionProcessing terminates with abend 0311.

Programmer responseEnsure that a DD statement is present andspecifications are correct. Make corrections, and rerunjob.


DFS3071A DBDNAME IN DBPCB DOES NOTMATCH DBDNAME ENTERED

ExplanationEither the DBNAME from the input statement or thePCB is incorrect.


Programmer responseCorrect input statement.

DFS3072I NO KEY IS DEFINED IN THE DBDFOR THE ROOT SEGMENT OF THISDATABASE

ExplanationThe DBD is invalid.



Problem determination:2, 3, 4, 8, 9, 11, 17a, 18, 19, 35


DFS3073I INTERNAL ERROR IN DFSPRSUR

ExplanationModule DFSPRSUR has encountered an error thatprevents further processing.








DFS3074A INVALID RETURN FROM OLICWHILE PROCESSING ANINITIALIZE DSG CALL

ExplanationEither there was an error in opening and initializing thedatabase or the OLIC parameter in the PCB was notset.


Programmer responseEnsure that OLIC=YES specified on PSB and DDstatement is present for database being surveyed.Make corrections, and resubmit job.



DFS3075I INVALID STATUS CODE FROM DL/Ifunction CALL-STATUS = statuscode

ExplanationAn invalid return code was returned from a DL/I call.


Programmer responseEnsure that the IMS system and all control statementsare valid, and resubmit the job.




DFS3076W FROMAREA INVALID FOR HIDAMOR KEYRANGE INVALID FORHDAM

ExplanationFROMAREA can only be specified for HDAM andKEYRANGE can only be specified for HIDAM.



DFS3077A LOW BLOCK NUMBER FOR DSGddname IS NOT WITHIN THE DATASET GROUP

ExplanationThe low block number specified for TOAREAprocessing was beyond the current end of the DSG.

System actionProcessing continues after bypassing the errorparameter.

Programmer responseLower the low block number so that it falls within theDSG, and rerun the job.

DFS3078I INVALID RETURN CODE FROMOLIC WHILE PROCESSING ABLOCK LOCATE CALL

ExplanationA nonzero return code was returned from an OnlineImage Copy block locate call.

System actionSURVEYOR is abnormally terminated with abend 0311.









DFS3079I INVALID RETURN CODE FROMOLIC WHILE PROCESSING A GETRBA CALL

ExplanationA nonzero return code was returned from an OnlineImage Copy get RBA call.




DFS3080I INVALID RETURN CODE FROMBUFFER HANDLER WHILEPROCESSING A LOCATE BLOCKCALL

ExplanationA nonzero return code was returned from the bufferhandler block locate call.




DFS3081W STATEMENT DOES NOT BEGINBEFORE COL 17

ExplanationStatement did not begin in a column between 1 and16.

System actionProcessing continues until all control statements havebeen analyzed. Then processing terminates.


DFS3082W UNKNOWN KEYWORD keyword

ExplanationKeyword was not recognized for control statementindicated.



DFS3083W INVALID SYNTAX error description

ExplanationSyntax error has been found in the user controlstatement.



DFS3084W INCOMPLETE STATEMENT

ExplanationThe previous control statement was incomplete.





DFS3085W ILLEGAL CONTINUATION

ExplanationEither the ending character in the input string was acomma and a blank was found in column 72, or theending character was not a comma and a nonblankcharacter was found in column 72.



DFS3086W KEYWORD PREVIOUSLYSPECIFIED KEYWORD: keyword

ExplanationThe keyword indicated has been specified previouslyin another input statement and only one keyword ofthis type is allowed.



DFS3087W INVALID OPERAND

ExplanationAn invalid operand has been found for the keywordindicated in the previous statement.



DFS3088W MISSING KEYWORD: keyword

ExplanationThe indicated keyword is missing.



DFS3089W FROMAREA, KEYRANGE, ANDTOAREA ARE MUTUALLYEXCLUSIVE

ExplanationTwo of the keyword types, listed in the message, havebeen specified.



DFS3090W MORE THAN THE MAXIMUM OF 10TOAREAS SPECIFIED

ExplanationYou can specify no more than 10 TOAREAs.



DFS3091W DBDLIB DOES NOT CONTAINdbdname

ExplanationThe DBD for the database identified by dbdname wasnot found in DBDLIB.



Programmer responseCorrect the error in control statement or DBDLIB, andrerun the job.

DFS3092W DBD dbdname DOES NOT HAVE HDACCESS METHOD

ExplanationThe DBD identified by dbdname is not an HDAM orHIDAM database.



DFS3093W DATA SET GROUPS(S) SPECIFIEDON INPUT STATEMENTS DO NOTMATCH DBD dbdname

ExplanationThe data set groups used in the TOAREA inputstatements are not the same as found in the DBD.



DFS3094W FROMAREA low block number TOhigh block number NOT IN ROOTADDRESSABLE AREA

ExplanationThe FROMAREA range specified is not within the rootaddressable area of this database.



DFS3095W NO RECORDS IN RANGE

ExplanationNo records were found in the range specified by usercontrol statement.



DFS3096A INVALID RETURN CODE FROM SVC

ExplanationAn error condition was detected by SVC processing.




DFS3097W INPUT KEY LENGTH DOES NOTMATCH DATA BASE KEY LENGTH

ExplanationThe length of the keys specified for the KEYRANGE arenot the same as the DBD key length.



DFS3098A SURVEYOR IS UNABLE TOLOCATE RECORD AT BEGINNING



OF RANGE AND/OR PARTITIONBOUNDARY

ExplanationThe first key in a FROMAREA range or partition cannotbe located. Either significant deletion or insertionactivity was occurring at range/partition boundarywhile Surveyor was running, or there is a databaseerror.

System actionProcessing terminates with a user abend 0311.

Programmer responseCheck for the possibility of either significant insert/delete activity against the database at the range/partition boundary or a database pointer error. Rerunjob when problem is resolved.



DFS3099W LOW KEY/RBN IS GREATER THANHIGH KEY/RBN

ExplanationThe low key or low block number entered was greaterthan the high key or block number entered on aFROMAREA, KEYRANGE, or TOAREA statement.



DFS3100I UNABLE TO START SESSION,NODE nodename IN FP INPUTMODE

or

UNABLE TO START SESSION, USER OR NODE IN FPINPUT MODE

ExplanationA session initiation request was refused. The first formof the message is issued by the /OPNDST commandprocessor if a referenced user or node is in Fast Pathinput mode. The user or node cannot be used to start asession.

The second form of the message is issued by a LOGONor SCIP exit if a session initiation request referencesa node in Fast Path input mode. The referenced useror node has RCVYFP=NO specified and the Fast Pathinput is in local mode. In the message text, nodenameidentifies the name of the node in Fast Path inputmode.

System actionThe command is ignored or the LOGON or SCIPrequest is denied.

Operator responseUse the /DISPLAY USER or /DISPLAY NODEcommands to determine the status of the user ornode.

Module:DFSICLQ0, DFSCNXA0





DFS3101I MAXIMUM SESSIONS REACHED -NODE nodename

or

MAXIMUM SESSIONS REACHED

ExplanationThe first form of the message is issued by the /OPNDST command processor. The second form of themessage is issued by the LOGON or SCIP exit. Eitherall available parallel sessions are in use or a singlesession device is still active. This condition can occurif the half-session is allocated, stopped, or not idle.If a /OPN command was entered, this condition canalso occur if OPTION=NOPNDST was specified on theTERMINAL macro.

System actionThe command is not run, or a LOGON/REQSESS isdenied.

Operator responseWait until a session becomes available, and reenterthe command.

If the problem persists for a single session device, theterminal might be hung in IMS as a result of an internalsession cleanup problem. If the terminal remainshung after a VTAM VARY INACT and /CLSDST NODEFORCE, create a console memory dump and report theproblem to IBM Software Support. The receipt of thismessage for many terminals often indicates a moreserious system wait, hang, or loop problem. If so, takea console memory dump before bringing the systemdown.

DFS3102I UNABLE TO ASSIGN, MSGDELOPTIONS DO NOT MATCH

ExplanationThis message is issued by the /ASSIGN commandprocessor. The MSGDEL options for the user namereferred to in the /ASSIGN command do not match.

System actionThe command is not run.

Operator responseReenter the command with a valid value.

DFS3103 USER IS NOT ALLOCATED

ExplanationThe specified user is not allocated, or the specifieddynamic terminal has no user allocated to it.


User responseAttempt the command after the user is logged on.

DFS3104 USER ALLOCATED TO SESSION

ExplanationThe specified users are currently allocated to a "nodesession" or are in the process of allocation by a /OPNDST command. Therefore, the /ASSIGN or /STOPcommand is not valid for an allocated user. /DEQUEUELTERM P1 PURGE is not allowed at this time, sincethe dequeue might not occur.


Operator responseFor /ASSIGN or /STOP, wait for the session toterminate, then reenter the command. For /DEQUEUELTERM P1 PURGE, the user was in the allocationprocess. When the user is allocated, the /DEQUEUELTERM P1 PURGE command is accepted if the nodehalf-session is stopped and idle (for example, using /STOP NODE USER).

DFS3105I USER HAS NO LTERMS

Explanation:For information and actions, see message DFS3105.


Related informationDFS3105SUBPOOL HAS NO LTERMS - NODE nodenameSUBPOOL sbplname

DFS3105 SUBPOOL HAS NO LTERMS - NODEnodename SUBPOOL sbplname

ExplanationA session initiation request was refused.

The first form of the message is issued by the /OPNDST command processor. It is issued If no logicalterminals are currently assigned to the first userspecified in the command.

The second form of the message is issued by theLOGON or SCIP exit if an ISC session initiation requestreferences a node and a subpool, and the referencedsubpool has no LTERMs associated with it.

System actionThe command is ignored or the LOGON/REQSESSrequest is denied.

DFS3106I USER KEYWORD IS INVALID

ExplanationThe USER keyword is invalid or inappropriate for thecommand being entered.

If this IMS system is part of a sysplex using the IMSResource Manager, the user might be actively on orowned by another IMS system. As a result, the userwould not be found on this IMS, even if it was staticallydefined to this system.


Operator responseCheck the valid syntax and restrictions of thecommand, noting restrictions of the use of the USERkeyword.

Module:DFSICLN0

DFS3107I USER NOT AVAILABLE, IN USEBY /ASSIGN OR /DEQUEUE


For a detailed explanation and actions, see DFS3107.

Related informationDFS3107USER NOT AVAILABLE, IN USE BY /ASSIGNOR /DEQUEUE

DFS3107 USER NOT AVAILABLE, IN USEBY /ASSIGN OR /DEQUEUE

or

USER NOT AVAILABLE - NODE nodename USERusername


The first form of the message is issued by the /OPNDST command processor that referenced a username that was involved in an assignment with a /ASSIGN command or a dequeue with a /DEQUEUELTERM P1 PURGE.

The second form of the message is issued by theLOGON or SCIP exit if an ISC session initiation requestreferences an unavailable user.

A user is unavailable if it was STOPPED; is currentlyreferenced by an /ASSIGN, /DEQUEUE, or a /SIGNcommand; or is currently in use.


Operator responseEnter a /DIS USER command to determine the statusof the user. If the user is STOPPED, issue a /STARTUSER command, if appropriate. If the user is the objectof an /ASSIGN, /DEQUEUE, or /SIGN command,wait for the command to complete before reenteringthe /OPN command.

DFS3108I USER KEYWORD PARAMETER ISINVALID OR MISSING

ExplanationThe USER keyword parameter was missing, was nota valid name, or was used in an invalid context. Thename might be valid, but it might be a duplicate ofanother entered user name, or a name used with anode name to which the user is not allocated.


If this IMS system is part of a sysplex using the IMSResource Manager, the user might be actively on orowned by another IMS system. As a result, the namewould not be found on this IMS, even if it was staticallydefined to the system.


Operator responseCheck the syntax and restrictions of the command.Use the /DISPLAY ASMT command to note currentassignments of users.

Module:DFSICLN0

DFS3109 INVALID NODE TYPE

ExplanationThe form of the command entered is not applicable forthe node type specified by the command.


Operator responseCheck the allowable formats and restrictions of thecommand and rerun the command.

DFS3110I INVALID KEYWORD SEQUENCE

ExplanationThe command editor (DFSICL30) detected a commandin which the NODE keyword was entered following theUSER keyword and its parameters. When both thesekeywords are used, the user name must be specifiedafter the node.


Operator responseResubmit the command with the keywords in thecorrect sequence.

Module:DFSICLN2, DFSICLN3, DFSICLN4

DFS3111I UNABLE TO START SESSION -NODE nodename STOPPED

or

UNABLE TO START SESSION -USER OR NODESTOPPED


The first form of the message is issued by the /OPNDST command processor if a referenced useror node is STOPPED. The user or node cannot bereferenced to start a session.

The second form of the message is issued by theLOGON or SCIP exit if a session initiation requestreferences a STOPPED node.


Operator responseUse the /DISPLAY USER and /DISPLAY NODEcommands to determine the status of the user andnode.

DFS3112I USER NOT AVAILABLE, CANNOTPROCESS COMMAND

ExplanationThe specified user name is already allocated andin session with another node, or is allocated tothe specified node, but with a different half-sessionqualifier than the one specified in the ID= keyword forthis command.


Operator responseUse the /DISPLAY ASMT USER command todetermine if the user name is allocated and the nodename to which it is allocated. If the user name isallocated to the same node name specified in the /OPNDST command, then reenter the command withthe correct half-session qualifier (ID=). If the username is allocated to a different node from the onespecified in the /OPNDST command, wait until theuser name becomes available or enter the /STOPUSER command to prevent further allocation when thecurrent allocated session ends.


DFS3113I SESSION ALREADY ACTIVE

ExplanationThe NODE and USER parameters in the commandspecify a LUTYPE6 session that has already beenestablished, or is in the process of being established.


Operator responseUse the /DISPLAY NODE USER command todetermine the state of the session.

DFS3114I MULTIPLE NODE PARAMETERSARE INVALID

ExplanationNeither the USER keyword nor the FORCE keyword canbe specified if a generic node name, ALL, or range ofnode names is specified for the NODE keyword in thecommand.


Operator responseCorrect the syntax of the command and rerun.

DFS3115I NODE IN USE, CANNOT PROCESSCOMMAND

ExplanationThe /ASSIGN failed because:

1. When attempting to /ASSIGN the USER back toVTAMPOOL, the half-session node, to which thespecified user name is allocated, is in session inconversational mode, preset mode, or responsemode; or the half-session node is not stopped andidle.

2. When attempting to /ASSIGN the LTERM or username to another (target) USER, the half-sessionnode, to which the specified target USER isallocated, is in session or is not idle.


Operator responseRespond to the failures as follows:

1. For the first failure mentioned above, issue the /STOP NODE P1 USER P2 command to stop thespecified half-session. Use the /DISPLAY NODEUSER command to verify that the half-session nodeis stopped and idle, and reenter the original /ASSIGN command. If the half-session node wasin conversational mode, preset mode, or responsemode, issue a /START NODE P1 USER P2command (after the /STOP) to clear those specialmodes, then issue another /STOP.

2. For the second failure mentioned above, issuethe /STOP NODE P1 USER P2 command for thehalf-session node to which the specified targetUSER is allocated. Use the /DISPLAY NODE USERcommand to verify that the half-session node isidle and not in session, and reenter the original /ASSIGN command.

DFS3116I USER AND TERMINAL MSGDELOPTIONS DO NOT MATCH

ExplanationThe user name and terminal message delete optionsdo not match when attempting an /OPNDST NODEUSER.


Operator responseSelect a user name with appropriate message deleteoptions, and reenter the /OPNDST command.

DFS3117 SESSION NOT ACTIVE, CANNOTDEQUEUE

ExplanationThe /DEQUEUE command was entered without thePURGE keyword, but no session was active thatinvolved the specified node and user names (andLTERM, if used), or specified LTERM.


Operator responseDetermine whether the PURGE keyword shouldbe used. The /DISPLAY NODE P1 or /DISPLAY


ASSIGNMENT LTERM P1 command can be used todetermine what sessions are active.

DFS3118 MESSAGE CANNOT BEPROCESSED SYNCHRONOUSLY

ExplanationThe message cannot be processed synchronously. Itmust follow one of the following modes.

• Test mode• Command• Conversational transaction• Response mode

System actionThe session is terminated. An IMS Log Record withan ID of CVCT containing pertinent information wasproduced.

System programmer responseEither change the destination type to one of the above,or change the ATTACH to asynchronous form.



DFS3119I NO USERS ARE ALLOCATED TONODE

ExplanationThe command specified the NODE keyword and theUSER keyword with parameter ALL, but no user namesare currently allocated to the specified node, or thenode is not in the system.


DFS3120I MSC IN SYSTEM BUT DFSCMR00NOT AVAILABLE

ExplanationDuring IMS restart, module DFSCRM00 is needed toreinstate the MSC control blocks but it is not available.

System actionThis message will be followed by an IMS 3120 abend.

Programmer responseMake sure that DFSCMR00 is linked into DFSRST00load module.


DFS3121A LOGICAL COPY COMPLETE FORGROUP|DB/AREA groupname |dbname - n OF m DATA SETSFAILED

ExplanationSee explanation under DFS3121I.

Related informationDFS3121ICOPIED DB/AREA dbname DDN ddname DSNdsname

DFS3121I COPIED DB/AREA dbname DDNddname DSN dsname

ExplanationThis message is issued by the Database Image Copy2 utility (DFSUDMT0) when image copy processingfor the database data sets contained in the identifiedgroup, database, or area is logically complete. If agroup name was specified as input to the utility,the message identifies the group. Otherwise, oneDFS3121A message is issued for each database orarea for which data sets are being copied.

nThe number of data sets for which image copyprocessing failed.

mThe total number of data sets to be copied by thisrun of the utility.

DFS3121I messages identify the individual databasedata sets for which the image copies are now logicallycomplete.

System actionThe utility continues processing. When the imagecopies are physically complete, they are recorded inthe RECON data set.



Programmer responseIf you stopped update processing for the data group,database, or area with a /DBD or /DBR command torun the utility with the exclusive (X) option, you cannow resume update processing by issuing a /STARTDATAGROUP, UPDATE DATAGRP START(ACCESS), /START DB, UPDATE DB START(ACCESS), /STARTAREA or UPDATE AREA START(ACCESS) command.

ModuleDFSUDUI1

Related information“DFS3121A” on page 849LOGICAL COPY COMPLETE FOR GROUP|DB/AREA groupname | dbname - n OF m DATA SETSFAILED

DFS3122A LOGICAL COPY FAILED FOR DB/AREA dbname DDN ddname DSNdsname

ExplanationDFSMSdss notified the Database Image Copy 2 utility(DFSUDMT0) that the attempt to initialize a concurrentcopy session for the named data set was unsuccessful.For more information about the failure, see theADR734I message and other ADRnnn messages thatwere issued by DFSMSdss.

System actionImage copy processing fails for the database data setnamed in the message. The utility terminates unlessthere are other database data sets for which imagecopy processing has not completed.

Operator responseSee the ADRnnn messages that were issued byDFSMSdss to determine how to correct the problem.See z/OS MVS System Messages Vol 1 (SA22-7631) fora description of ADR messages.

If the data set is not on hardware that supports theconcurrent copy function, or if you do not want to useconcurrent copy, use the Database Image Copy utility(DFSUDMP0) to create the image copy.

Module:DFSUDUI1

Related referencez/OS: ADR734I

DFS3124A DBRC IS REQUIRED TO EXECUTETHIS UTILITY

ExplanationThe Database Image Copy 2 utility (DFSUDMT0) mustbe run with DBRC present, but DBRC=Y was notspecified for this execution.


Programmer responseSpecify DBRC=Y in the execution parameters andrerun the job.

ModuleDFSUDMT0

DFS3125A PRIMER SAMPLE TEST, REPLYCONT, LOOP, ABEND OR CANCELJOB

ExplanationThis message is issued by sample program DFS0AER.Using a batch or online transaction, the user requestedoperator intervention for synchronization of a recoverytest. A write to z/OS operator with reply (WTOR) isused. This action provides an environment to forciblyterminate the application program or system, or both,in order to test recovery procedures.

System actionNone.

Operator responseAs requested by user. Reply CONT to continue, ABENDto cause abnormal termination, LOOP to cause aprogram loop, or cancel the job using the z/OS CANCELcommand.

DFS3126W RDS DATA SET REFORMATREQUIRED DURING NEXTRESTART

ExplanationA write error occurred on the restart data set (RDS)during a checkpoint. The operation continues becausethe RDS data set is not required during onlineexecution except to save information needed for thenext restart. However, the next restart will access thedisk log to obtain information to restart the system. Atthis time a reformat of the RDS data set must be done.



System actionThe operation continues, but the system will stoplogging data to the RDS data set. The system will shutdown normally when instructed to do so.

Programmer responseCheck the allocation of the restart data set. The RDSallocation needs to be large enough to contain at least90 blocks reserved for RDS1 components BCPT, RRE,SIDX, and LCRE.

During the next restart of the system, reformat theRDS data set by specifying FORMAT RS in the restartcommand. If this problem persists, you must performa scratch, reallocation, and reformat of the RDS.

DFS3127I READ|WRITE ERROR OCCURREDON THE RESTART DATA SET xxxxxx

ExplanationAn error occurred while attempting to read or writethe restart data set (RDS), or during or after an IMScheckpoint.

The variable xxxxxx has one of the following values:

IMSRDSThe error occurred on the data set defined by theIMSRDS DD statement.

IMSRDS2The error occurred on the data set defined by theIMSRDS2 DD statement.

System actionIf a read error occurred, IMS terminates the restart. Ifa write error occurred, IMS continues processing.

Operator responseCheck the allocation of the restart data set. The RDSallocation needs to be large enough to contain at least90 blocks reserved for RDS1 components BCPT, RRE,SIDX, and LCRE.

For a read error, delete and reallocate the RDS; thenretry the restart by specifying FORMAT RS.

For a read error in the Fast Database Recovery region,terminate the active IMS, scratch and reallocate theRDS, and restart IMS by specifying FORMAT RS. Thenstart the Fast Database Recovery region.

For a persistent write error, terminate IMS, scratchand reallocate the RDS, and restart IMS by specifyingFORMAT RS. For the appropriate recovery actionsin an XRF environment, see IMS Version 15 SystemAdministration.

DFS3128A OPEN FAILED ON RESTART DATASET, xxxxxxxx.

ExplanationOSAM was unable to open the restart data set. Thevariable xxxxxxxx has one of the following values:IMSRDS

The error occurred on the data set defined by theIMSRDS DD statement.


IMSRDS2 NOT DEFINEDThe IMSRDS2 DD statement is invalid or missing.

System actionIf an XRF alternate system is being started, abendU0970 with RC=1 occurs. If this message is issuedby the Fast Database Recovery region, abend 0574occurs. Any other IMS start terminates, and IMS waitsfor another /START command.

Operator response(master terminal) See the Programmer response forthe appropriate action.

Programmer responseIf the problem is not in the system hardware orsoftware (for example, the JCL is in error or the dataset is not formatted), the restart data set must bereallocated. The subsequent IMS must format therestart data set. In an XRF and Fast Database Recoveryenvironment, only the active system can format therestart data set.



DFS3129I RUNNING IN SHARED QUEUESENVIRONMENT - BUILDQPARAMETER IGNORED

ExplanationThe online system is being started with a commandthat included the BUILDQ parameter; however, the


system is running in the shared queues environment.The BUILDQ parameter has no meaning in a sharedqueues environment.

System actionThe BUILDQ parameter is ignored, and the restartprocess continues.

ModuleDFSRBCP0

DFS3130I ABEND 970 SCHEDULED RC=01yyy

or

ABEND 970 SCHEDULED RC=xx

ExplanationThe first form of the message is issued when IMSabend 0970 is scheduled The contents of register10 are displayed in field xx. The second form isissued when abend 0970 is scheduled, and register10 contains 01. Field yyy contains an AWE return codethat is documented in the 0970 information.

System actionThe system abnormally terminates with abend 0970.


DFS3131A A COLD START OR EMERGENCYRESTART REQUIRED

ExplanationA normal restart command was submitted, butthe system was not terminated after a shutdowncheckpoint command, or the system was never startedcold. The originating module is DFSRBCP0.


Operator response:(master terminal) Enter either a cold startor emergency restart command with appropriateparameters.

Module:DFSRBCP0

DFS3132A CANNOT BUILDQ. SHUTDOWNWAS FREEZE.

ExplanationNormal restart command parameter for BUILDQ wasspecified, but system was not terminated with amemory dump of the message queues. Originatingmodule is DFSRBCP0.


Master terminal operator response: Enter the restartcommand with appropriate parameters.

DFS3133 FATAL DFSMS ERROR DURINGRESTORE PROCESSING

ExplanationThe DFSMS restore of a data set failed.

System actionThe system abnormally terminates with abend 0225.

Programmer responseTo determine the cause of the failure, see the DFSMSADRnnnn messages.

Module:DFSURDB0

Related referencez/OS: ADR messagesRelated informationIMS abend 0225

DFS3134W GSAM PCB (NUM=nnn) IS NOTDECODED IN PSB psb_name

ExplanationEither the Library Utility (DFS3LU00) or CatalogPopulate Utility (DFS3PU00) was unable to decode theGSAM PCB from ACB format.psb_name

The PSB-type ACB member name.nnn

The GSAM PCB number.




http://www-01.ibm.com/support/knowledgecenter/SSLTBW_2.4.0/com.ibm.zos.v2r4.ieam100/adr.htm?lang=en




DFS3135A KSDS DEFINITION DOESNOT ALLOW IMAGE COPYCONCURRENT WITH UPDATEACCESS

or

KSDS DEFINITION DOES NOT ALLOW IMAGE COPYONLINE FAST REPLICATION WITH UPDATE ACCESS

ExplanationA control statement supplied to the Database ImageCopy 2 utility (DFSUDMT0) tried to take an imagecopy of a KSDS data set using concurrent copyor fast replication, and that update access to thedata set is allowed (S was specified in column 58or defaulted to). However, the DEFINE CLUSTERattribute, BWO(TYPEIMS), was not specified for theKSDS.

System actionMessage DFS3144A with reason code 0C is also issuedto identify the database data set for which image copyprocessing has failed. The utility terminates unlessthere are other database data sets for which imagecopy processing has not completed.

System programmer responseReview the option specified on the control statementfor the KSDS. If image copy processing concurrentwith updating or with fast replication is to be allowed,notify the database administrator that the accessmethod services (IDCAMS) ALTER command mustbe used to specify BWO(TYPEIMS) for the dataset. See DFSMS/MVS Access Method Services for ICF(SC26-4906).

ModuleDFSUDUI1

Related information“DFS3144A” on page 855IMAGE COPY PROCESSING FAILED FOR DB/AREA dbname DDN ddname, REASON = nn

DFS3136I NORMAL RESTART IN PROCESS

ExplanationIMS has determined that normal restart is requiredunder the automatic restart option.

System actionIMS proceeds with normal restart. Originating moduleis DFSRBCP0.

Master terminal operator response: None required.

DFS3137I EMERGENCY RESTART INPROCESS

ExplanationIMS has determined that emergency restart is requiredunder the automatic restart option.

System actionIMS proceeds with emergency restart.

DFS3138I INSUFFICIENT PSB|PSBW POOLSPACE

ExplanationAn XRF alternate system or a Fast Database Recoveryregion tried to schedule a PSB while tracking the activesystem. The schedule failed because of insufficientpool space.

System actionThe system terminates with abend 0593.

Programmer responseIncrease the PSB pool space to at least equal that ofthe active system.



DFS3139I IMS (DCCTL) INITIALIZED,AUTOMATIC RESTARTPROCEEDING



ExplanationAutomatic restart option selected. If (DCCTL) isdisplayed in the message, the DCCTL environment hasbeen initialized.

System actionThe system waits for reply to continue IMS normal oremergency restart, as appropriate.

Operator response(master terminal) Respond with any appropriateinstallation-defined reply. The reply is not processed.

DFS3140A SDEP SCAN UTILITY FAILED DUETO INDOUBT SEGMENT IN THESCAN RANGE

or

SDEP UTILITY FAILED DUE TO IN-DOUBT SEGMENTIN UTILITY RANGE

or

SDEP DELETE UTILITY FAILED DUE TO IN-DOUBTSEGMENT IN DELETE RANGE

ExplanationThe DEDB Sequential Dependent Scan utility found anin-doubt segment in the range of segments requestedto be scanned.

For the SDEP UTILITY FAILED DUE TO IN-DOUBT SEGMENT IN UTILITY RANGE versionof this message, the DEDB Sequential Dependentutility found an in-doubt segment in the range ofsegments requested to be scanned or deleted andthe command INDOUBT was not specified as a utilitycontrol statement. Only aborted and committed SDEPsegments can be scanned or deleted. They will beskipped if INDOUBT is specified.

For the SDEP DELETE UTILITY FAILED DUE TOIN-DOUBT SEGMENT IN DELETE RANGE version ofthis message, the DEDB Sequential Dependent Deleteutility found an in-doubt segment in the range ofsegments requested to be deleted. Only aborted andcommitted SDEP segments can be deleted.


User responseIf you are prevented from scanning segments, theoptional parameter INDOUBT must be included in theSYSIN record and a SCANIDT data set specified forin-doubt segment output. An in-doubt segment cannotbe deleted, so RBAs in SCANIDT will need to beresolved if they are intended to be deleted after scan.

If you are prevented from scanning or deletingsegments because of an old unresolved segment, youshould resolve the segment. After you resolve thesegment and write it to the database, you can scanor delete the segment.

ModuleDBFUMDL0, DBFUMRT0, DBFUMSC0, DBFUMMS0

DFS3141A PHYSICAL COPY COMPLETEFOR GROUP|DB/AREA groupname|dbname - n OF m DATA SETSFAILED

ExplanationSee the explanation under DFS3141I.

Related information“DFS3141I” on page 854COPIED DB/AREA dbname DDN ddname DSNdsname

DFS3141I COPIED DB/AREA dbname DDNddname DSN dsname

ExplanationThe DFS3141A message is issued by the DatabaseImage Copy 2 utility (DFSUDMT0) when image copyprocessing for the database data sets contained inthe identified group, database, or area is physicallycomplete. If a group name was specified as inputto the utility, then groupname identifies the group.Otherwise one DFS3141A message is issued for eachdatabase or area for which data sets were copied.

DFS3141I messages identify the individual databasedata sets that were successfully copied.

In the message text:groupname

The name specified on the group name controlstatement. Image copies for all database data setsbeing copied are physically complete.

dbnameThe name of a database or area for which imagecopies are physically complete.


nThe number of data sets for which image copyprocessing failed.

mThe total number of data sets to be copied by thisexecution of the utility.

ddnameThe ddname or area name for the data set that wascopied.

dsnameThe data set that was copied.

System actionAll image copies for the group, database, or areawere recorded in the RECON. The utility continuesprocessing if there are other data sets still beingprocessed.

Programmer responseIf you stopped update processing for the data group,database, or area with a /DBD or /DBR commandto run the utility with the exclusive (X) option, youcan resume update processing by issuing a /STARTDATAGROUP, UPDATE DATAGRP START(ACCESS), /START DATABASE, UPDATE DB START(ACCESS), /START AREA, or UPDATE AREA START(ACCESS)command.

ModuleDFSUDUI1

Related information“DFS3141A” on page 854PHYSICAL COPY COMPLETE FOR GROUP|DB/AREA groupname|dbname - n OF m DATA SETSFAILED

DFS3142I DFSMSDSS MESSAGE ADR974IWAS ISSUED FOR DB dbname DDNddname DSN dsname

ExplanationThe Database Image Copy 2 utility (DFSUDMT0) issuesthis message to the system console when it is notifiedthat DFSMSdss is writing an ADR974I message.


System programmer responseSee z/OS MVS System Messages Vol 1 (SA22-7631)for a description of the ADR974I message. You shouldverify that the identified data set is good.

Module:DFSUDUI1

Related referencez/OS: ADR974I

DFS3143A SAME DATASET ("S")SPECIFICATION ERROR.

ExplanationThe utility control statements supplied for theDatabase Image Copy 2 utility contains one of thefollowing syntax errors:

• More than 255 database data sets were specifiedto be copied to the same output data set. Themaximum is 255.

• The Same Data Set (S) option was specified, butthere is no previous control statement specifying theoutput data set(s).


System programmer responseCorrect the utility control statements before rerunningthe utility. The first control statement specifying theSame Data Set option must be preceded by a controlstatement that specifies the output ddnames. Specifyno more than 255 database data sets to be copied tothe same output data set(s).


Module:DFSUDMT0


DFS3144A IMAGE COPY PROCESSINGFAILED FOR DB/AREA dbnameDDN ddname, REASON = nn



ExplanationThe Database Image Copy 2 utility was unable tocreate an image copy for the specified database dataset or area.

(nn) is one of the following reason codes:Reason code

Meaning01

DBRC AUTH request failed.

The request to DBRC for database authorizationfailed.

02DBRC INIT request failed.

The INIT request to DBRC for image copyprocessing failed. See the DSP message that wasalso issued.

03Input DD statement is missing.

A DD statement for the database data set was notsupplied.

04Output DD statement is missing.

A DD statement for an image copy output data setwas not supplied.

05The area data set has Error Queue Elements(EQEs).

EQEs exist for all area data sets for the identifiedarea. See the DFS3726A message that was alsoissued.

06The DFSMSdss DUMP initialization failed.

DFSMSdss did not schedule a memory dump taskfor the dump command for this database data set.See the DFSMSdss ADR messages issues for thedump command.

07No VOLSER for the image copy data set.

DFSMSdss has notified the utility of successfulcompletion for the database data set, however,during dump processing, volume serial numbersfor the output data sets were not received fromDFSMSdss.

08Invalid VOLSER for image copy data set.

An output volume serial number received fromDFSMSdss is invalid. An abend U0225 withsubcode 4 was issued. See the abend description.

09Fast Path error was detected.

The Fast Path image copy module set anunexpected return code during image copyprocessing. See the error message issued for theFast Path area.

0AAttempt to copy KSDS concurrent with updateaccess failed.

A concurrent copy session for a fuzzy KSDS imagecopy was not successfully initialized. See theDFS3145A message that was also issued.

0BDatabase/area is not registered with DBRC.

The identified database or area is not registeredwith DBRC.

0CBWO(TYPEIMS) was not specified for KSDS.

A fuzzy image copy of a KSDS data set wasrequested, however, BWO(TYPEIMS) was notdefined for KSDS. See the DFS3135A message thatwas also issued.

0DDBRC EOD request failed.

The EOD request to DBRC for image copyprocessing failed. See the DSP message that wasalso issued.

0EI/O error on image copy data set.

The last or only image copy output data set hasexperienced an I/O error.

0FDFSMSdss DUMP processing failed.

The data set complete notification from DFSMSdssindicated that the data set was not successfullydumped. See the DFSMSdss ADR messages todetermine the cause of the failure.

10Dynamic allocation error.

Dynamic allocation for the database data setfailed.

11Unauthorization failed.

The request to DBRC to unauthorize a database orarea failed.

12UIM abend or unexpected DFSMSdss processing.


Either an abend occurred in the user interactionmodule (UIM), DFSUDUI1, during DFSMSdssdump command processing, or dump commandprocessing ended without the UIM being drivenfor data set complete notification. If there wasno abend, check the DFSMSdss ADR messages forthis dump command.

You might encounter this code when a DFSMSserver is going into QUIESCE mode. You cansuppress this code in these situations byconfiguring a DFSMS server which does not shutdown.

13Output data set was not successfully closed.

Close was unsuccessful or was not attempted forthe primary or secondary image copy data set. ADFS0300I message was issued for the data set.Because the data set was not successfully closed,it might be unusable. Image copy processing failsfor the DBDS because there is no valid image copyto record in the RECON.

14The system created a list of the volumes that arecandidates for copying. However, no volume couldbe found in the list that fulfilled the requirementsfor DFSMSdss fast replication.

System actionThe utility continues processing if there are otherdatabase data sets that are being copied that have notcompleted. The return code for this run of the utility is8 or higher.

For reason code 14, utility processing terminates withreturn code 16.

System programmer responseCorrect the problem indicated and submit anotherDatabase Image Copy 2 job to copy the database dataset. For reason codes 07, 08, and 12 (with abend),contact IBM Software Support for assistance if you areunable to resolve the problem.

Module:DFSUDMT0, DFSUDUI1, DFSUDMT1

Related information“DFS0300I” on page 107OUTPUT DATA SET SPECIFIED BY DDNAMEddname WAS NOT SUCCESSFULLY CLOSED“DFS3145A” on page 857ATTEMPT TO COPY KSDS CONCURRENT WITHUPDATE ACCESS FAILED“DFS3726A” on page 1070

FPE AREA IMAGE COPY TERMINATEDABNORMALLY FOR AREA=areaname REASONCODE=nnIMS abend 0225

DFS3145A ATTEMPT TO COPY KSDSCONCURRENT WITH UPDATEACCESS FAILED

ExplanationA control statement supplied to the Database ImageCopy 2 utility (DFSUDMT0) specified that a KSDS dataset was to be copied concurrent with update access (Swas specified or defaulted to in column 58). However,because of current update activity to the data set,a concurrent copy session required to copy the dataset was not successfully initialized. If the KSDS wasthe only data set being copied, this utility attemptedthe DFSMSdss dump operation several times beforeissuing this message.

System actionMessage DFS3144A with reason code 0A is alsoissued to identify the database data set forwhich image copy processing has failed. The utilityterminates unless there are other database data setsfor which image copy processing has not completed.

Operator responseThe condition encountered might be momentary.Retry image copy processing for the KSDS after anappropriate amount of time.

ModuleDFSUDUI1


DFS3146A READJFCB FAILED FOR DDddname

ExplanationThe Database Recovery utility (DFSURDB0) cannotcontinue recovery processing of the Fast Path areadata set because there is no matching DD statementin the JCL for the identified DD name.




Operator responseUse the LIST.ADS command to obtain a current list ofADDN/ADSN pairs and change the JCL accordingly.

ModuleDFSURT00

DFS3147A ATTEMPT TO READ THE CATALOGFAILED FOR DBDS dbdsname

ExplanationAn attempt was made to read the catalog entry for theindicated dbdsname to determine the volume serialnumbers associated with this dataset, but the attemptto read the catalog failed.

System actionProcessing is terminated. The return code for theutility is 16.

System programmer responseMake sure that the data set is cataloged and resubmitthe job.

ModuleDFSURFR0

DFS3148A DATABASE dbname IS NOTREGISTERED WITH DBRC

ExplanationThe Database Image Copy 2 utility (DFSUDMT0)cannot process the named database or area becauseit is not registered with DBRC. An invalid dbdnamesupplied in the JCL will also cause DBRC to return a"not registered" indication, since it does not match theRECON.

System actionDFS3144A messages with reason code 0B arealso issued to identify the database data sets forwhich image copy processing has failed. The utilityterminates unless there are other database data setsfor which image copy processing has not completed.

Operator responseUse the appropriate commands (for example,INIT.DB) to register the database or area beforeretrying image copy processing or use the Database

Image Copy utility (DFSUDMP0) to create the imagecopy.

ModuleDFSUDMT0


DFS3149A DFSUDMT0 CANNOT BE RUN INSTAND-ALONE MODE

ExplanationThe Database Image Copy 2 utility (DFSUDMT0) mustbe executed using the region controller (DFSRRC00).

System actionThe Database Image Copy 2 utility (DFSUDMT0)terminates abnormally.

Operator responseChange the EXEC statement to executePGM=DFSRRC00 with appropriate parameters for theutility job, and resubmit the job.

ModuleDFSUDMT0

DFS3150 UNABLE TO LOCATE/FREERESTART COMMAND BUFFER

ExplanationIMS restart rebuilds the condensed command byaccumulating type X'02' log record segments inthe restart command buffer before reprocessing thecommand. IMS was unable to locate the requiredrestart command buffer during accumulation of thetype X'02' log records, or was unable to free a bufferupon completion of restart processing.

System actionEither restart does not reprocess the loggedcommand, or does not free the restart commandbuffer.

Operator responseNotify the system programmer that this error occurred.


Programmer responseTo determine what to do, read the "IMS ProblemDetermination" topic for the numbers listed below.






DFS3151 UNABLE TO OBTAIN STORAGE FORRESTART COMMAND BUFFER

ExplanationIMS restart rebuilds the condensed command byaccumulating type X'02' log record segments in therestart command buffer. Restart was unable to obtainstorage from the WKAP (MAIN) pool for this buffer.

System actionThe command to be reprocessed at restart is ignored.

Operator responseEnter the command /DIS POOL MAIN, save theconsole listing with the response, and notify thesystem programmer.

Programmer responseTo determine what to do, read the "IMS ProblemDetermination" topic for the numbers listed below.



DFS3152 CONDENSED COMMAND BUFFERTOO SMALL FOR COMMAND

ExplanationWhile building the condensed command, IMSdiscovered that the buffer was too small to contain thecommand input. This is an internal IMS error causedby IMS miscalculating the amount of storage neededfor the condensed command buffer.


Operator responseNote the command that caused this error message tobe issued, and notify the system programmer.

Programmer responseTo determine what to do, read "IMS problemdetermination" for the numbers listed below.



DFS3153 CONDENSED COMMAND BUFFEREXCEEDS LIMIT

ExplanationExpansion of the ALL parameter or an inclusiveparameter caused the condensed command buffer toexceed the allowable maximum.


Operator responseReenter the command as multiple commands. Forexample, reenter /DISPLAY LINE ALL as twocommands: /DISPLAY LINE 1-1000 and /DISPLAYLINE 1001-2000.

DFS3154E CONDENSED BUFFER FORCOMMAND xxx REMAINS AT THEEND OF RESTART

ExplanationIMS restart rebuilds the condensed command byaccumulating type X'02' log records in the restartcommand buffer. After the command is reprocessed,the restart buffer is freed. At the end of restart, therestart command buffer for command xxx remained,indicating that the log did not contain all the type X'02'log record segments required for the command.


System actionCommand xxx is not reprocessed during restart.

Operator responseNotify the system programmer that this error occurred.

Programmer responseTo determine what to do, read "IMS problemdetermination" for the numbers listed below.



DFS3155A AREA DATA SET NOT FOUNDADSN= dsname AREA NAME=areaname DDNAME= ddnameREASON= rc

ExplanationThe Database Recovery utility (DFSURDB0) was unableto recover the area data set (ADS) identified in themessage. The hexadecimal reason code is:8

A data set name from the input data set was foundin the ADS list in the RECON, but the area data setwas not preallocated.

System actionThe execution is terminated with an error code.

Operator responseFor reason code 4, use the DBRC command,INIT.ADS, to add the data set name to the ADS list.Then run the GENJCL.RECOV command again.

For reason code 8, allocate the data set using IDCAMSand run the GENJCL.RECOV command again.

ModuleDFSURUI0

DFS3156I RESTORING ADDN= ddnameADSN= dsname FROM INPUTCOPY DATA SET

ExplanationThe Database Recovery utility used the ADDN andADSN in the message as the target data set. ThisADDN and ADSN from the input copy data set matchesthe ADS list in the RECON data set for the DEDB ADSbeing recovered. These might be different from theADDN and ADSN in the JCL because the data setnamed in the messages was found by searching theICF catalog to determine if ADSN was preallocated.The named ADDN and ADSN are recorded in theRECON data set as available when the Data BaseRecovery utility completes normally.

System actionThe Data Base Recovery utility continues.

ModuleDFSURUI0

DFS3157A IMAGE COPY FOR AREA areanameNOT FOUND ON INPUT DATA SET

ExplanationThe Database Recovery utility (DFSURDB0) was unableto recover the indicated area because an image copyfor the area was not found on the input data set.


Operator responseIf the area uses multiple area data sets (MADS) andthe area data set (ADS) that was copied to the imagecopy data set is no longer defined in the RECON,redefine that ADS and add it to the ADS list inthe RECON before rerunning the utility. Otherwise,rerun the utility with the correct image copy data setspecified.

ModuleDFSURUI0

DFS3158A INVALID IMAGE COPY CONTROLSTATEMENT SYNTAX, REASON=nn

ExplanationA control statement for the Database Image Copy 2utility (DFSUDMT0) is invalid. This message followsmessages DFS310A and DFS391E. The controlstatement is invalid for one of the following reasons:


CodesExplanation

01An invalid combination of replication options wasfound for a full-function non-HALDB databaseor HALDB partition must use the same imagecopy option: DFSMS fast replication or DFSMSconcurrent copy.

02DFSMS fast replication does not support the samedata set option.

03The SET PATCH control statement containedsyntax errors.

04An invalid number of copies was specified.

05An invalid value for position 3 (the time stampspecification for the low-level qualifier) wasspecified in the HLQ specification statement.

07Neither a high-level qualifier in the HLQspecification statement nor an OUTPUT ddname inthe DBDS SELECT statement was specified.

08The GROUP statement must be the first statementspecified, but it was specified as the second orsubsequent statement.

09The generated output data set name exceeded 44characters or contained an invalid qualifier.

10The high-level qualifier (HLQ) of the output dataset name specified in columns 4 - 29 on the HLQspecification statement is in error. The error couldbe the result one of the following causes:

• The output data set name high-level qualifierwas not syntactically correct for a data set high-level qualifier.

• You specified a Y in column 3 of the HLQspecification statement, indicating that a timestamp be appended to the output data set name.However, the total length for the output data setname exceeds 44 characters.

11You specified an H in column 63 of a DBDSselect statement, indicating that an image copydata set high-level qualifier is specified on asubsequent HLQ specification statement. However,this statement did not directly follow the DBDSselect statement.

System actionControl statement processing terminates with utilityreturn code 16.

System programmer responseCorrect the problem and submit another DatabaseImage Copy 2 utility job to copy the database data set.

Module:DFSUDMT1

DFS3160I IMS CMD=xxxxxxxxxxxxxxxx

ExplanationAn informational message issued by IMS Adapterfor REXX, when the IMSRXTRC level is greater than0. Show environment command being executed. Amaximum of 65 command characters are shown.

System actionNone.

DFS3161I eeeeeeee Call=xxxx RC=yyyyReason=zzzz[Status="xx"]

ExplanationAn informational message issued by IMS Adapterfor REXX, when the IMSRXTRC level is greater than0. Show last status from the eeeeeeee environment,where eeeeeeee is either REXXTDLI or REXXIMS. Theeeeeeeee value will be REXXTDLI or REXXIMS.

System actionNone.

DFS3162E Parm=xx Invalid on eeeeeeeeCommand "yyyyyyyy"

ExplanationA syntax error while running EXEC with IMS Adapterfor REXX was encountered. You provided an invalidparameter on eeeeeeee environment command. The xxvalue represents the parameter in error, where 1 is thefirst parameter after the command. For example, if thePCB parameter is invalid, the xx value would be 1 forDL/I calls.

The eeeeeeee value is either REXXTDLI or REXXIMS.In the message text, yyyyyyyy identifies the IMScommand you issued.


System actionEnvironment command is not executed; however,EXEC execution continues with a -5 return code fromthe command.

Programmer responseVerify parameters and correct application.

DFS3163E Excess Parameters on eeeeeeeeCommand "xxxxxxxx"

ExplanationSyntax Error while running EXEC with IMS Adapterfor REXX. Invalid number of parameters on eeeeeeeeenvironment command. The eeeeeeee value will beeither REXXTDLI or REXXIMS.

System actionNo processing is done. EXEC execution continues witha -8 return code from the call/command.

Programmer responseVerify parameters using IMS Adapter for REXXReference Materials and correct application.

DFS3164E Unknown eeeeeeee Command:xxxxxxxx

ExplanationA syntax error was encountered while running EXECwith IMS Adapter for REXX. The command xxxxxxxxwas not recognized by the Language Environmenteeeeeeee. Possible reasons for nonrecognition include:

• The command should be issued to REXXIMS and notREXXTDLI.

• The command should be issued to z/OSenvironment.

• The command was misspelled.

In the message text, eeeeeeee can be one of thefollowing values:

REXXTDLIREXXIMS

System actionNo processing is done. EXEC execution continues witha -3 return code from the call/command.

Programmer responseCorrect the application EXEC issuing the unrecognizedcommand.

DFS3165E Invalid Parameter to FunctionREXXIMS

ExplanationSyntax error occurred while running EXEC with IMSAdapter for REXX. Invalid function parameters werepassed on the REXXIMS function call.

System actionAn invalid function call is signaled to theREXX interpreter where it processes the conditionappropriately.

Programmer responseVerify usage of REXXIMS function call. If problempersists, verify that you are in an IMS Adapter for REXXenvironment by issuing the following command andgetting a return code 0.

Address MVS 'SUBCOM REXXIMS'

DFS3166I Var-f:vvvv= (lllll):xxxx

ExplanationAn informational message issued by IMS Adapter forREXX, when the IMSRXTRC level is greater than 1 forset/drop or IMSRXTRC greater than 2 for fetch. ShowREXX variable manipulation by REXXTDLI or REXXIMS.Function F will be f, s or d for Fetch, Store, or Drop. Thefirst 12 characters of variable name is shown in thevvvv field. The LLLL value is the length of the contents.Up to the first 40 characters are shown in the xxxxfield. For the F=d (drop) case, the llll and xxxx fieldsare not shown. If the variable was not initialized andit was specified in a MAPPUT then it is "Skipped" andthat form of the message is given.

System actionNone.

DFS3167E Var:vvvvvvvvvvvv Too Long,Max=yyy

ExplanationSyntax error occurred while running EXEC with IMSAdapter for REXX. Variable/Parameter length is invalidfor variable vvvvvvvvvvvv. The maximum allowedlength is yyy.


System actionVariable manipulation is aborted. EXEC executioncontinues with a -7 return code from the call/command.

Programmer responseDetermine failing line by prior messages or by turningon REXX tracing,

TRACE "R"

for diagnosis.

DFS3168E EXECCOMM VAR=vvvvvvvvvvvvRCODE=xxxxxxxx

ExplanationSyntax error occurred while running EXEC with IMSAdapter for REXX. This is an unexpected error thatoccurred while manipulating REXX variable throughthe IRXEXCOM interface.


System programmer responseIf you cannot resolve the problem, look up the returncode on IRXSUBCM in TSO/E REXX/MVS Reference.

Programmer responseVerify that variable vvvvvvvvvvvv is a proper REXXvariable. Verify that the value to be assigned does notexceed 32K.

DFS3169E Invalid Token Name: xxxxxxxx

ExplanationSyntax error occurred while running EXEC with IMSAdapter for REXX. Error in EXEC on STORAGE typestatement or DL/I call specifying a token name. Invalidtoken names are those of less than 1 or more than 16characters in length.


Programmer responseCorrect the token name.

DFS3170E Invalid Map Definition: xxxxxxxx atoffset yyyy

ExplanationData Mapping error while running EXEC with IMSAdapter for REXX. Error in EXEC on MAPDEF statementfor map xxxxxxxx in actual definition variable at theyyyy offset in the message.


Programmer responseExamine the mapping input and correct the applicationerror. The yyyy value is a character offset in the originalmap definition string.

DFS3171E Invalid Map Name: xxxxxxxx

ExplanationData Mapping error while running EXEC with IMSAdapter for REXX. Error in EXEC on MAP typestatement or DL/I call specifying a map name. Invalidmap names are those of less than 1 or more than 16characters in length.


Programmer responseCorrect the map name.

DFS3172I Invalid MAPGET Var: xxxx Map:yyyyyyyy

ExplanationData Mapping error while running EXEC with IMSAdapter for REXX. Error in EXEC on MAPGET statementor DL/I "GET" call while decoding/extracting variablexxxx in map yyyyyyyy. Common causes include whenthe Map defined is larger than the input segment tothe map and data conversion error of packed or zoneddecimal.


System actionProgram continues. The failing variable's valueis dropped. (See IMS Version 15 ApplicationProgramming APIs for more details).

Programmer responseCorrect application and verify mapping definition(MAPDEF).

DFS3173E Invalid MAPPUT Var: xxxxxxxxMap: yyyyyyyy

ExplanationData Mapping error while running EXEC with IMSAdapter for REXX. Error in EXEC on MAPPUT statementor DL/I "PUT" call packing/concatenating variable yyyyin map xxxxxxxx. Common cause is Map data, whenpackaged, is larger than output segment/buffer.

System actionVariable manipulation is aborted, EXEC executioncontinues with a -10 return code from the call/command.

Programmer responseCorrect application, verify correct variable spelling.

DFS3174A INVALID DATABASE RECOVERYUTILITY CONTROL STATEMENTSYNTAX, REASON=nn

ExplanationA control statement for the Database Recovery utility(DFSURDB0) is invalid for the following reason:01

The Database Recovery utility must retrieve thedatabase data set name from DBRC, but DBRC isnot active.

System actionControl statement processing terminated with a utilityreturn code of 8.

System programmer responseCorrect the problem and resubmit the job.

Module:

DFS3175E AN MSC CSLSCMSG REQUESTFAILED, active_process, RETCODE= rc, RSNCODE = rsn, LOSTSESS =

cause, MODULE =m , LINK = nnn ,linkname

ExplanationSCI returned a non-zero return code or reason code toMSC in response to a CSLSCMSG request for servicesfor an MSC logical link that is assigned to a TCP/IPphysical link. The logical link is shut down.

In the message text:active_process

The MSC process that was active when the erroroccurred. Possible values include:RESTART

When SCI encountered the error, MSC wasattempting to notify IMS Connect and theremote IMS system of the restart of the logicallink identified in the message text.

SENDMSGWhen SCI encountered the error, MSC wasattempting to send an MSC message to aremote IMS system by way of the logical linkidentified in the message text.

SHUTDOWNWhen SCI encountered the error, MSC wasattempting to notify IMS Connect and theremote IMS system that the logical link wasshutting down.

UNKNOWNDisplayed when the error occurred duringan unidentifiable MSC process. Thetroubleshooting and recovery procedure is thesame as for the regular active process types.

causeThe cause of a lost session, as reported either bySCI through the CSL SCI Notify Client exit routineor by IMS.

The possible values include:

FORCESTOA /PSTOP LINK FORCE or UPDATE MSLINKSTOP(COMM) OPTION(FORCE) command wasissued by the operator.

ICONABEThe local IMS Connect instance terminatedunexpectedly.

ICONSTOPThe local IMS Connect instance was shutdown.

NONENeither IMS nor the CSL SCI Notify Client exitroutine recorded a cause for the lost session.


SCIABEThe SCI instance that is managingcommunications between IMS and thelocal IMS Connect instance terminatedunexpectedly.

SCISTOPThe SCI instance that is managingcommunications between IMS and the localIMS Connect instance was shut down.

linknameThe name of the affected MSC logical link.

nnnThe number of the affected MSC logical link.

rcThe CSLSCMSG return code issued by SCI.

rsnThe CSLSCMSG reason code issued by SCI.

Possible cause: The cause of this message is identifiedby the SCI return and reason codes and possibly bythe value that is displayed in the LOSTSESS field in themessage text.

System actionThe MSC link session is terminated. IMS logs 6701-MSS1, MSS2, and MSS3 records.

Depending on the status of the connection to theremote IMS system, IMS might attempt to notify theremote IMS system. If notification is successful, theremote IMS system terminates the logical link, placesthe link in the PSTOPPED IDLE ERE state, and issuesmessage DFS2169I DISCONNECTION COMPLETEDON LINK xxx at the remote site.

If the notification is not successful and the linkremains in an IDLE ACTIVE state at the remote site,a /PSTOP LINK xxx FORCE or UPDATE MSLINKNAME(linkname) STOP(COMM) OPTION(FORCE) mightneed to be issued to terminate the link.

Even if the notification to the remote system is notsuccessful, the notification to the local IMS Connectmight succeed, in which case the local IMS Connectcleans up the associated sockets.

System programmer responseIf the remote IMS system was not notified of thetermination of the logical link, someone at the remotesite might need to issue a /PSTOP LINK x FORCEor UPDATE MSLINK NAME(linkname) STOP(COMM)OPTION(FORCE).

Determine the cause of the error from the RETCODE,RSNCODE, and LOSTSESS values. The problem couldbe in either the local or remote IMSplex network. Look

up the return and reason codes for the CSLSCMSGrequest. Check for other messages from SCI, IMSConnect, or TCP/IP that might help with the diagnosis.Collect the X'6701' error records from the IMS log.

After the cause of the error is corrected, restart thelink.

ModuleModule Description

DFSTCER0 DFSxxxx message interface

DFSTCPE0 Execute CSLSCMSG request

DFSTCP20 Receive Post handler

DFSTCRC0 Validate post codes

DFSTC1A0 Send output controller

DFSTC1B0 Send output buffer setup

DFSTC2A0 Process send completion

DFSTC3A0 Receive input controller

DFSTC4A0 Process receive completion

DFSTC7A0 Restart and shutdown router

DFSTC7B0 Restart processor

DFSTC7C0 Shutdown processor

DFSTC7D0 Shutdown cleanup

DFSCMSG0 Bandwidth output edit

DFSCMSP0 Bandwidth input error messageprocessor

DFSCMSR0 Bandwidth response messagebuilder

DFSCMSU0 Bandwidth output bufferheader builder

DFSCMSX0 Bandwidth response messagebuilder

DFSCMSZ0 Bandwidth input messageprocessor

DFSCMS00 MSC analyzer

Related referenceCSLSCMSG: send message request (SystemProgramming APIs)

DFS3176E IMS CONNECT ERROR MESSAGERECEIVED, active_process,RETCODE = rc, RSNCODE = rsn,LOSTSESS = cause, MODULE =m,LINK = nnn, linkname


http://www.ibm.com/support/knowledgecenter/SSEPH2_15.1.0/com.ibm.ims15.doc.spr/ims_cslsci_req_cslscmsg.htm#ims_cslsci_req_cslscmsg


ExplanationIMS Connect detected an error while processing arequest or message from MSC and returned a non-zero return or reason code to IMS. The error mighthave been detected by either the local IMS Connectinstance or the remote IMS Connect instance. Theerror message is returned to the local IMS system thatissued the request or message.



When IMS Connect encountered the error, MSCwas attempting to notify IMS Connect and theremote IMS system of the restart of the logicallink identified in the message text.

SENDMSGWhen IMS Connect encountered the error, MSCwas attempting to send an MSC message to aremote IMS system by way of the logical linkidentified in the message text.

SHUTDOWNWhen IMS Connect encountered the error, MSCwas attempting to notify IMS Connect and theremote IMS system that the logical link isshutting down.


causeThe cause of a lost session, as reported either bySCI through the CSL SCI Notify Client exit routineor by IMS. The possible values include:FORCESTO

A /PSTOP LINK FORCE or UPDATE MSLINKSTOP(COMM) OPTION(FORCE) command wasissued by the operator.




SCIABEThe local SCI instance that is managingcommunications between the local IMS system

and the local IMS Connect instance terminatedunexpectedly.

SCISTOPThe local SCI instance that is managingcommunications between the local IMS systemand the local IMS Connect instance was shutdown.

STOPCLNTThe receive socket between a local IMSConnect instance and a remote IMS Connectinstance was terminated.

The following list includes some of the possiblecauses:

• An IMS Connect STOPCLNT command or itsequivalent type-2 UPDATE command wasissued.

• An IMSplex, MSC, or RMTIMSCON entity in aremote IMS Connect was stopped.

• A remote IMS Connect was terminated.• A remote IMS was terminated.

STOPIPThe communication between a local IMSConnect instance and an IMSplex was stopped.This is caused by an IMS Connect STOPIPcommand or its equivalent type-2 UPDATEcommand.

STOPLINKThe MSC logical link in a local IMS Connectinstance was stopped. This is caused byan IMS Connect STOPLINK command or itsequivalent type-2 UPDATE command.

STOPMSCThe MSC physical link in a local IMS Connectinstance was stopped. This is caused byan IMS Connect STOPMSC command or itsequivalent type-2 UPDATE command.

STOPRMTThe communication between a local IMSConnect instance and a remote IMS Connectinstance was stopped. This is caused byan IMS Connect STOPRMT command or itsequivalent type-2 UPDATE command.



rcThe return code issued by IMS Connect. TheIMS Connect return and reason codes that areassociated with this message are documented inthe following table. These and other IMS Connect


return and reason codes are also documented inthe HWSHRR macro.

rsnThe reason code issued by IMS Connect. TheIMS Connect return and reason codes that areassociated with this message are documented inthe following table.

Possible cause: The cause for this message can bedetermined by reviewing the return and reason codesand the value of LOSTSESS.

Table 18. IMS Connect return and reason codes for messageDFS3176E

Returncode Reason code Meaning

X'0C000018'

X'00006000' Receive from IMS failed.

X'00006004' Link not found.

X'00006008' Link being restarted is alreadyrestarted.

X'0000600C' Failed to get a send socket.

X'00006010' Invalid directive received on theCSLSCMSG request.

X'00006014' IMS Connect failed to get a linkblock.

X'00006018' The local IMS Connect instancedetected an invalid restart linkrequest.

X'0000601C' The local IMS Connect couldnot restart a link because IMSConnect is disconnected fromMSC.

X'00006020' The local IMS Connect could notrestart a link because MSC is notactive.

X'00006024' The local IMS Connect could notrestart a link because the restartrequest contains an invalid IMS IDfor the local IMS system.

X'00006028' The local IMS Connect detectedan invalid link shutdown request.

X'0000602C' The local IMS Connect could notshutdown a link because IMSConnect is disconnected fromMSC.

X'00006030' The local IMS Connect could notshutdown a link because MSC isnot active.

X'00006034' The local IMS Connect couldnot restart a link because theshutdown request contains aninvalid IMS ID for the local IMSsystem.

X'00006038' The local IMS Connect instancereceived an invalid message fromMSC.

Table 18. IMS Connect return and reason codes for messageDFS3176E (continued)


X'0000603C' IMS Connect cannot processa message from the remoteMSC because the local MSC isdisconnected.

X'00006040' IMS Connect cannot process amessage from the remote MSCbecause the local MSC is notactive.

X'00006044' IMS Connect cannot process amessage from the remote MSCbecause the message contains aninvalid IMS ID.

X'00006048' An attempt was made to starta logical link, but the valueof the GENIMSID parameter inthe DFSDCxxx PROCLIB memberof the IMS system does notmatch the value of the GENIMSIDparameter in the correspondingMSC configuration statement inthe IMS Connect configurationPROCLIB member. The startrequest is rejected. To resolvethe problem, make the twoGENIMSID values match.

X'0000604C' An attempt was made to starta logical link from an IMSsystem that does not specify theGENIMSID parameter to enableTCP/IP generic resources, butthe MSC definitions for the linkin IMS Connect do specify theGENIMSID parameter for TCP/IPgeneric resources. IMS Connectrejected the restart link request.

You can resolve the problem inone of the following ways:

• In IMS, specify the GENIMSIDparameter on the DFSDCxxxmember of this IMS system,restart IMS, and then restartthe link.

• In IMS Connect, deletethe specification for theGENIMSID parameter in theMSC statement of the IMSConnect configuration member,restart IMS Connect, and thenrestart the link.




X'00006050' An attempt was made to start alogical link from an IMS system ina TCP/IP generic resource group,but one or more logical linksthat use the same physical linkalready have affinity with anotherIMS system in the TCP/IP genericresource group. IMS Connectrejected the start request.

To resolve the problem, eitherrestart the logical link from theIMS system in the TCP/IP genericresource group that has affinity, orterminate the logical links on theother IMS system and, after IMSConnect has cleared the existingaffinities, restart the link on thisIMS system.

X'00006054' The IMS system notified IMSConnect that it would accepta restart link request from aremote IMS system, but anotherIMS system in the TCP/IPgeneric resource group alreadyaccepted the link request. IMSConnect rejected the notificationof acceptance from this IMSsystem. This is not an error.

X'00006058' The local IMS Connect could notshutdown a link because thespecified link is not found. Checkfor any IMS Connect HWSF3355Emessage.

X'0000605C' An attempt was made to start alogical link from an IMS systemthat specifies the GENIMSIDparameter to enable TCP/IPgeneric resources, but the MSCdefinitions for the link in IMSConnect do not specify theGENIMSID parameter for TCP/IPgeneric resources. IMS Connectrejected the restart link request.

You can resolve the problem inone of the following ways:

• In IMS, delete the specificationof the GENIMSID parameter onthe DFSDCxxx member of thisIMS system, restart IMS, andthen restart the link.

• In IMS Connect, specify theGENIMSID parameter in theMSC statement of the IMSConnect configuration member,restart IMS Connect, and thenrestart the link.

X'00006100' Send to the remote IMS Connectfailed.



X'00006200' The receive failed on the TCP/IPread from a remote IMS Connectinstance.

X'00006204' Send to data store failed. This ismost likely an internal error.

X'00006300' Send to IMS failed. The remoteIMS system is probably notavailable.

X'00006400' An MSC link was stopped in thelocal IMS Connect instance by aSTOPLINK command.

X'00006404' MSC communications stopped inthe local IMS Connect instance bya STOPMSC command.

X'00006408' Communications on a connectionto a remote IMS Connect instancewas stopped in the local IMSConnect by a STOPRMT command.

X'0000640C' Communications with the localIMSplex was stopped in thelocal IMS Connect by a STOPIPcommand.

X'00006410' IMS Connect shutdown.

System actionThe MSC link connection is terminated and placed inthe PSTOPPED IDLE ERE state. IMS writes type 6701-MSS1, MSS2, and MSS3 records.

Depending on the status of the connection to theremote IMS system, IMS might attempt to notify theremote IMS system. If notification is successful, theremote IMS system terminates the logical link, placesthe link in the PSTOPPED IDLE ERE state, and issuesmessage DFS2169I DISCONNECTION COMPLETEDON LINK xxx at the remote site.


Even if the notification to the remote system is notsuccessful, the notification to the local IMS Connectmight succeed, in which case the local IMS Connectcleans up the associated sockets.

Output destinationThe z/OS system console and the master terminals.


System programmer responseIf the remote IMS system could not be notified of thetermination of the logical link, someone might need toissue a /PSTOP LINK xxx FORCE or UPDATE MSLINKNAME(linkname) STOP(COMM) OPTION(FORCE) at theremote site.

Determine the cause of the error from the RETCODE,RSNCODE, and LOSTSESS values. The problem couldbe in either the local or remote IMSplex network.Check for other messages from SCI, the IMS Connectinstances, or TCP/IP that might help with thediagnosis. Collect the X'6701' error records from theIMS log.



DFSTCER0 DFSxxxx message interface

DFSTCPE0 Execute CSLSCMSG request







DFSTC4A0 Process receive completion

DFSTC7A0 Restart and shutdown router





DFSCMSP0 Bandwidth input error message processor

DFSCMSR0 Bandwidth response message builder

DFSCMSU0 Bandwidth output buffer header builder

DFSCMSX0 Bandwidth response message builder

DFSCMSZ0 Bandwidth input message processor


Related referenceHWS messages (IMS Connect) (Messages andCodes)Related information“DFS2169I” on page 637DISCONNECTION COMPLETED ON LINK xxx.HWSF3355E (Messages and Codes)

DFS3177E MSC DETECTED AN ERROR,active_process, RETCODE = rc,RSNCODE = rsn, LOSTSESS =cause, MODULE =m, LINK = nnn,linkname

ExplanationThe MSC TCP/IP device dependent module (DDM)detected an error while processing a message orrequest associated with the MSC logical link identifiedin the message text.




SENDMSGWhen IMS Connect encountered the error, MSCwas attempting to send an MSC message to aremote IMS system by way of the logical linkidentified in the message text.

SHUTDOWNWhen IMS Connect encountered the error, MSCwas attempting to notify IMS Connect and theremote IMS system that the link is shuttingdown.








http://www.ibm.com/support/knowledgecenter/SSEPH2_15.1.0/com.ibm.ims15.doc.msgs/nondfs/ims_hwsmessages.htm#hws_messages


http://www.ibm.com/support/knowledgecenter/SSEPH2_15.1.0/com.ibm.ims15.doc.msgs/msgs/hwsf3355e.htm#hwsf3355e


SCIABEThe SCI instance that is managingcommunications between the local IMS systemand the local IMS Connect instance terminatedunexpectedly.

SCISTOPThe SCI instance that is managingcommunications between the local IMS systemand the local IMS Connect instance was shutdown.



rcThe return code issued by the MSC DDM. The MSCDDM return and reason codes that are associatedwith this message are documented in the followingtable.

rsnThe reason code issued by the MSC DDM. The MSCDDM return and reason codes that are associatedwith this message are documented in the followingtable.

Possible cause: The possible cause is indicated by thereturn and reason codes included in the message text.

IMS MSC DDM return and reason codes for messageDFS3177E

The following return and reason codes are also listedin the SCIWORK DSECT in the DFSMSCWA macro inthe IMS.SDFSMAC data set.

Return codeReasoncode Meaning

DFSPOOLRC

X'00000004'

DFSPOOL GET storageerror

DFSPOOLRC

X'00000008'

DFSPOOL releasestorage error

CELL POOLRC

X'0000000C'

Cell pool (CPOOL) geterror

CELL POOLRC

X'00000010'

Cell pool (CPOOL) freeerror

X'00000014'

Invalid post code or postcondition detected

X'00000018'

Invalid AWE detected


X'0000001C'

Invalid MSC directive(DFSMSDIR) detected

X'00000020'

Invalid bufferheader control block(BUFMSHDR) detected

X'00000024'

Invalid message controlblock (BUFMSCB)detected

X'00000028'

Immediate shutdownrequest received frompartner IMS

X'0000002C'

Invalid or unexpectedMSC Link (MSLINK)status detected

X'00000030'

Unexpected bracketinitiation stop (BIS)message received

X'00000034'

Unexpected errormessage control block(BUFMSCB) received

X'00000038'

Invalid restartmessage control block(BUFMSCB) received

X'0000003C'

Invalid shutdownmessage control block(BUFMSCB) received

X'00000040'

Unexpected return codereceived from internalroutine

X'00000044'

SCIWORK area error

X'00000048'

Queue error detected(CTB5QERR set)

X'0000004C'

Queue buffer chainingerror detected

X'00000050'

AWE chaining errordetected

X'00000054'

Output edit error

X'00000058'

Input edit error

QMGR RC X'0000005C'

Unexpected return codefrom the message queuemanager



X'00000060'

DFSMGPL macro error,message prefix bad

X'00000064'

Invalid response MSCB(BUFMSCB) received

X'00000068'

Invalid internal conditiondetected

X'0000006C'

Internal control blockerror

X'00000070'

Lost session errorposted by SCI notifyexit for SCI/ICONabends or /PSTOPLINK FORCE or UPDATEMSLINK STOP(COMM)OPTION(FORCE)command

X'00000074'

Cannot issue CSLSCMSGrequest because CSLis not initialized. CheckCSLG= parameter on theIMS startup procedure.CSLG=000 is minimumrequired.

X'00000078'

CSLSCMSG requestfailed. Nonzero returncode was returned bySCI on the request.

X'000000FC'

Undetermined error

X'0000007C'

(RSNOLLB) LXB wasposted by the SCI MSGexit, DFSSXIN0, but theLXBTCLBP field waszero.

X'00000080'

(RSN_BUFFER)CSLSCBFR RELEASErequest failed to freean SCI buffer. For moreinformation about theRETCODE and RSNCODEcodes, see the CSLSRRmacro. For MSPLINK-related errors, theRETCODE and RSNCODEcodes are stored in theLXBRET and LXBRSNfields of the LXB block.For MSLINK-relatederrors, the RETCODE


and RSNCODE codes arestored in the CLBTEMP4and CLBTEMP5 fields ofthe LLB block. Thesecontrol blocks are loggedin the 6701-MSS1 logrecord.

X'00000084'

(RSN_NOMSC) Messageinput routine DFSSXIN0received an MSC TCPIPmessage, but no MSCwas defined.

X'00000088'

(RSN_NOLLBS) Messageinput routine DFSSXIN0received an MSC TCPIPmessage, but no MSCLLBs were defined.

X'0000008C'

(RSN_NOLXBS) Messageinput routine DFSSXIN0received an MSC TCPIPmessage, but the targetlink had no availableLXBs to start a session.

X'00000090'

(RSN_NOTCPIP)Message input routineDFSSXIN0 received anMSC TCPIP messagebut the target link wasnot of TCPIP type.For example, this erroroccurs when the targetlink is assigned to theMSPLINK type.

X'00000094'

(RSN_NOLCB) LLB wasnot assigned to anMSPLINK LCB controlblock.

X'0000009C'

(RSN_NOPRTNR)Message input routineDFSSXIN0 received anMSC TCPIP message, butno target link was foundfor the specified partnerID.


DFSPOOLRC

X'00000004'




DFSPOOLRC

X'00000008'

DFSPOOL releasestorage error

CELL POOLRC

X'0000000C'

Cell pool (CPOOL) geterror

CELL POOLRC

X'00000010'

Cell pool (CPOOL) freeerror

X'00000014'


X'00000018'


X'0000001C'


X'00000020'


X'00000024'


X'00000028'


X'0000002C'

Invalid or unexpectedMSC Link (MSLINK)status detected

X'00000030'


X'00000034'


X'00000038'

Invalid restartmessage control block(BUFMSCB) received

X'0000003C'


X'00000040'


X'00000044'

SCIWORK area error

X'00000048'



X'0000004C'


X'00000050'


X'00000054'

Output edit error

X'00000058'

Input edit error

QMGR RC X'0000005C'


X'00000060'


X'00000064'


X'00000068'


X'0000006C'


X'00000070'

Lost session errorposted by SCI notifyexit for SCI/ICONabends or /PSTOPLINK FORCE or UPDATEMSLINK STOP(COMM)OPTION(FORCE)command

X'00000074'

Cannot issue CSLSCMSGrequest because CSLis not initialized. CheckCSLG= parameter on theIMS startup procedure.CSLG=000 is minimumrequired.

X'00000078'

CSLSCMSG requestfailed. Nonzero returncode was returned bySCI on the request.

X'000000FC'

Undetermined error

X'0000007C'

(RSNOLLB) LXB wasposted by the SCI MSGexit, DFSSXIN0, but theLXBTCLBP field waszero.



X'00000080'

(RSN_BUFFER)CSLSCBFR RELEASErequest failed to freean SCI buffer. For moreinformation about theRETCODE and RSNCODEcodes, see the CSLSRRmacro. For MSPLINK-related errors, theRETCODE and RSNCODEcodes are stored in theLXBRET and LXBRSNfields of the LXB block.For MSLINK-relatederrors, the RETCODEand RSNCODE codes arestored in the CLBTEMP4and CLBTEMP5 fields ofthe LLB block. Thesecontrol blocks are loggedin the 6701-MSS1 logrecord.

X'00000084'

(RSN_NOMSC) Messageinput routine DFSSXIN0received an MSC TCPIPmessage but no MSCwas defined.

X'00000088'

(RSN_NOLLBS) Messageinput routine DFSSXIN0received an MSC TCPIPmessage but no MSCLLBs were defined.

X'0000008C'

(RSN_NOLXBS) Messageinput routine DFSSXIN0received an MSC TCPIPmessage but the targetlink had no availableLXBs to start a session.

X'00000090'

(RSN_NOTCPIP)Message input routineDFSSXIN0 received anMSC TCPIP messagebut the target link wasnot of TCPIP type.For example, this erroroccurs when the targetlink is assigned to theMSPLINK type.

X'00000094'

(RSN_NOLCB) LLB wasnot assigned to an


MSPLINK LCB controlblock.

System actionThe MSC link connection is terminated and placed inthe PSTOPPED IDLE ERE state. IMS logs type 6701-MSS1, MSS2, and MSS3 records.

IMS attempts to notify the remote IMS system. Ifnotification is successful, the remote IMS systemterminates the logical link, places the link in thePSTOPPED IDLE ERE state, and issues messageDFS2169I DISCONNECTION COMPLETED ON LINKxxx at the remote site.


Output destination:The z/OS system console and the IMS masterterminals.

System programmer responseIf the remote IMS system could not be notified of thetermination of the logical link, someone might need toissue a /PSTOP LINK x FORCE or UPDATE MSLINKNAME(linkname) STOP(COMM) OPTION(FORCE) at theremote site.

Determine the cause of the error from the RETCODE,RSNCODE, and LOSTSESS values. The moduleidentified in the message text is where the erroroccurred. Check for other messages from SCI, IMSConnect, or TCP/IP to help with the diagnosis. Collectthe X'6701' error records from the IMS log.



DFSTCER0 DFSxxxx messageinterface

DFSTCPE0 Execute CSLSCMSGrequest





Module Description




DFSTC4A0 Process receivecompletion

DFSTC7A0 Restart and shutdownrouter





DFSCMSP0 Bandwidth input errormessage processor

DFSCMSR0 Bandwidth responsemessage builder


DFSCMSX0 Bandwidth responsemessage builder

DFSCMSZ0 Bandwidth inputmessage processor


DFS3178E MSC DETECTED AN INTERNALLOGIC ERROR, active_process,RETCODE = rc, RSNCODE = rsn,LOSTSESS = cause, MODULE =m,LINK = nnn, linkname

ExplanationAn MSC device dependent module (DDM) detected aninternal logic error.




SENDMSGWhen IMS Connect encountered the error, MSCwas attempting to send an MSC message to a

remote IMS system by way of the logical linkidentified in the message text.

SHUTDOWNWhen IMS Connect encountered the error, MSCwas attempting to notify IMS Connect and theremote IMS system that the logical link isshutting down.

TCPPOSTThe device dependent routine post handler(DFSTCP20) was processing a post of amessage received from the CSL SCI Inputmessage exit routine (DFSSXIN0) but thelogical link that the message was targeted forcould not be determined, or an error occurredon the CSLSCBFR RELEASE buffer request.








SCIABEThe local SCI instance that is managingcommunications between the local IMS systemand the local IMS Connect instance terminatedunexpectedly.





rcThe return code issued by the MSC DDM. The MSCDDM return and reason codes that are associatedwith this message are documented in the followingtable.

rsnThe reason code issued by the MSC DDM. The MSCDDM return and reason codes that are associatedwith this message are documented in the followingtable.


IMS MSC device dependent module return and reasoncodes for message DFS3178E

The following return and reason codes are also listedin the SCIWORK DSECT in the DFSMSCWA macro inthe IMS.SDFSMAC data set.

Returncode

Reasoncode Meaning

DFSPOOLRC

X'00000004'


DFSPOOLRC

X'00000008'

DFSPOOL release storageerror

CELLPOOL RC

X'0000000C'

CEll pool (CPOOL) geterror

CELLPOOL RC

X'00000010'

CEll pool (CPOOL) freeerror

X'00000014'


X'00000018'


X'0000001C'


X'00000020'


X'00000024'


X'00000028'


X'0000002C'

Invalid or unexpectedMSC Link (MSLINK) statusdetected

X'00000030'


Returncode

Reasoncode Meaning

X'00000034'


X'00000038'

Invalid restart messagecontrol block (BUFMSCB)received

X'0000003C'


X'00000040'


X'00000044'

SCIWORK area error

X'00000048'


X'0000004C'


X'00000050'


X'00000054'

Output edit error

X'00000058'

Input edit error

QMGR RC X'0000005C'


X'00000060'


X'00000064'


X'00000068'


X'0000006C'


X'0000007C'

LXB (Link extension block)was posted by the SCIMSG exit, DFSSXIN0, butthe LXBTCLBP was zero.This problem should notoccur.

X'000000FC'

Undetermined error


Returncode

Reasoncode Meaning

X'00000098'

An AWE was detectedafter IMS already de-registered with SCI.

System actionThe MSC link connection is terminated. IMS logs type6701-MSS1, MSS2, and MSS3 records.

IMS attempts to notify the remote IMS system. Ifnotification is successful, the remote IMS systemterminates the logical link, places the link in thePSTOPPED IDLE ERE state, and issues messageDFS2169I DISCONNECTION COMPLETED ON LINKxxx at the remote site.


System programmer responseIf the remote IMS system could not be notified of thetermination of the logical link, someone might need toissue a /PSTOP LINK x FORCE or UPDATE MSLINKNAME(linkname) STOP(COMM) OPTION(FORCE) at theremote site.

Determine the cause of the error from the RETCODE,RSNCODE, and LOSTSESS values. The moduleidentified in the message text is where the erroroccurred. Check for other messages from SCI, IMSConnect, or TCP/IP to help with the diagnosis. Collectthe X'6701' error records from the IMS log.

DFS3178E is issued for internal logic errors. If theproblem persists, call IBM Software Support.



DFSTCER0 DFSxxxx messageinterface

DFSTCPE0 Execute CSLSCMSGrequest




Module Description




DFSTC4A0 Process receivecompletion

DFSTC7A0 Restart and shutdownrouter





DFSCMSP0 Bandwidth input errormessage processor

DFSCMSR0 Bandwidth responsemessage builder


DFSCMSX0 Bandwidth responsemessage builder

DFSCMSZ0 Bandwidth inputmessage processor


DFS3179I TTTTTPP=(AAAAAAAA:SSSS-LLLL)= XXXXXXXX=CCCCCCCC

ExplanationAn informational message issued by IMS Adapter forREXX, when the IMSRXTRC level is greater than 7.Show parameter list passed to and received fromthe standard IMS language interface on AIBTDLI orASMTDLI call.

• TTTTT is the type of trace, "Entry" when tracedbefore the DL/I call, "Exit" when traced after theDL/I call.

• PP is the parameter number, where number 1 is theactual DL/I call.

• AAAAAAAA is the address of the parameter.• SSSS is the size of the parameters buffer.• LLLL is the assumed length of the parameter.• XXXXXXXX is the first 8 bytes of the parameter in

hexadecimal.• CCCCCCCC is the first 64 bytes of the parameter in

EBCDIC.


System actionNone.

DFS3180I INQY ENVIRON Region=rrrrrrrrNumber=nnnn PGM=pppppppp

ExplanationAn informational message issued by IMS Adapter forREXX, when the IMSRXTRC level is greater than 0. Thismessage describes the environment in which the EXECwill be executed.


DFS3181I DFSREXX Starting and BuildingEnvironment

ExplanationAn informational message indicating an IMS REXXenvironment is being built for the IMS dependent orbatch region because a REXX transaction is starting.


DFS3182I REXX EXEC: xxxxxxxxCOMPLETED, RC=yyyyyyyy

ExplanationAn informational message issued by IMS Adapter forREXX, when the IMSRXTRC level is greater than 0.States return code the scheduled EXEC ended with.


DFS3183E EXEC: xxxxxxxx NOT FOUND

ExplanationEXEC to be executed by IMS Adapter for REXX wasnot found in available data sets. The EXEC identifiedby xxxxxxxx can be either the IMS scheduled programname or might have been overridden by the user exitroutine (DFSREXXU).

System actionNo EXEC execution occurs.

Programmer responseVerify that SYSEXEC DD on dependent region includesthe correct concatenation for the EXECs.

DFS3184I NO EXEC NAME SELECTED TOEXECUTE

ExplanationAn informational message issued by IMS Adapter forREXX, when the IMSRXTRC level is greater than 0.There was no EXEC name specified to execute. TheEXEC name is defaulted to the Program Name butwas overridden by the IMS Adapter for REXX user exitroutine (DFSREXXU).


System programmer responseIf unexpected, verify the user exit routine DFSREXXUand see IMS Version 15 Application Programming APIsfor more information.

DFS3185I LARGE BLOCK INTERFACEDETECTED, IT WILL BE USED FORDDNAME .......

ExplanationThe Image Copy Utility has determined that the imagecopy output data set is on a device that supports theLarge Block Interface. However, no explicit block sizewas specified.

System actionThe Image Copy Utility uses the Large Block Interfacewith a system determined block size to write the imagecopy.


Module:DFSUDMP0

DFS3187I RACF NOT ACTIVE FOR RESUMETPIPE CLASS=RIMS RC=XX. RACFEXIT RC=YY REASON CODE=ZZ.

ExplanationA failure occurred in the RACROUTE exit processingwhile IMS was trying to build in-storage profiles forRACF-defined resources.


In the message text:XX

The return code from the RACROUTE macroYY

The return code from the RACF exitZZ

The reason code from the RACF exit

System actionIMS restart continues. RACF OTMA resume tpipeauthorization is disabled.

Operator response:(master terminal) See the RACROUTE return andreason codes for information on the problem.

Related referencez/OS: RACROUTE return codes and reasoncodesz/OS: RACROUTE STAT return codes and reasoncodes

DFS3189W RDS BLOCK ALLOCATIONINSUFFICIENT FOR: type

ExplanationThe number of blocks in the restart data set that wereinternally allocated and reserved for logging additionalrecoverable information was insufficient.

An UPDATE POOL TYPE(DBAS) command was issuedto dynamically change one or more definitions. Thecommand was issued successfully; however, thesystem was not able to log this information in therestart data set to be retained across emergencyrestart. This message lists one or more of the followingtypes of information that were not logged astype:ODBP

The OSAM subpool definitionsODBD

The OSAM database definitionsVDBP

The VSAM subpool definitionsVDBD

The VSAM database definitions

System actionIMS continues to process normally.

Operator responseThe types of information listed in the message arenot retained across an emergency restart. You can

reissue the UPDATE POOL TYPE(DBAS) command ifthe previously made changes are wanted.

If the problem persists, contact IBM Software Support.

DFS3190E CALL xxxx RC=yyyy REASON=zzzzSTATUS="SS"

ExplanationUnexpected status was returned from an IMS Adapterfor a REXX internal DL/I call, such as INQY ENVIRONor INQY FIND.

System actionThe EXEC or DL/I call execution is terminated.

Programmer responseVerify the parameters passed on the last REXXTDLIcall run. The cause is probably an invalid PCBNAME.

DFS3191E INVALID CALL TO DFSREXX1,ENV=xxxxxxxx

ExplanationA problem occurred during the execution of theIMS Adapter for REXX. Direct calls to DFSREXX1are invalid. If ENV=NotInit, a probable cause isDFSREXX1 was not bound correctly (REUS required).Or, DFSREXX1 was aliased or copied to be theapplication and DFSREXX0 was the stub took the placeof the application.


System programmer responseVerify your REXX installation. If the problem recurs,contact IBM Software Support.

DFS3192E IRXINOUT ERROR DD=xxxxxxxx,RC=yyyyy

ExplanationA problem prevented a WRITE to the DD xxxxxxxx fromthe IMS Adapter for REXX.


Programmer responseVerify the DD definition in the IMS Region.




http://www-01.ibm.com/support/knowledgecenter/SSLTBW_2.4.0/com.ibm.zos.v2r4.ichc600/racrout.htm%23racrout?lang=en

http://www-01.ibm.com/support/knowledgecenter/SSLTBW_2.4.0/com.ibm.zos.v2r4.ichc600/racrout.htm%23racrout?lang=en

DFS3193E ERROR LOADING MODULExxxxxxxx RC=yyyyyyyy

ExplanationThe module xxxxxxxx was not able to be loaded for theIBM Adapter for REXX.


System programmer responseVerify your REXX installation. If the problem continues,contact IBM Software Support.

DFS3194E ERROR EXECUTING IRXINIT,RC=xxxxxxxx

ExplanationThe system was unable to build a REXX environmentfor the IBM Adapter for REXX.


System programmer responseVerify your REXX installation. If the problem continues,contact IBM Software Support with the message textand return code.

DFS3195E ERROR EXECUTING IRXSUBCMADD: xxxxxxxx RC=yyyyyyyy

ExplanationThe system was unable to add the specified REXXsubcommand environment for the IBM Adapter forREXX.


System programmer responseVerify your REXX installation, If the problem continues,contact IBM Software Support.

DFS3196E ERROR LOADING INTERFACEMODULE DFSREXX1

ExplanationThe system was unable to load the IMS Adapter for theREXX module (DFSREXX1).


Programmer responseVerify IMS module DFSREXX1 is in a library accessibleto your dependent region that is running REXX. Verifyyour STEPLIB.

DFS3197I HALDB ALTER STARTED FORNAME=mastername PARTITIONNUMBER=nnnn

or

HALDB ALTER RESUMED FOR NAME=masternamePARTITION NUMBER=nnnn

or

HALDB ALTER ACTIVE FOR NAME=masternamePARTITION NUMBER=nnnn

ExplanationIn response to an INITIATE OLREORG command withthe ALTER option, this IMS system started or resumedALTER processing of the number of partitions shown inthe nnnn position of the message text.

In the message text:mastername

The name of the HALDB master database that isbeing altered.

nnnnIf the message reads HALDB ALTER STARTED,nnnn shows the total number of partitions in theHALDB database.

If the message reads HALDB ALTER ACTIVE, nnnnshows the total number of partitions in the HALDBdatabase.

If the message reads HALDB ALTER RESUMED,nnnn shows the total number of partitions whichhave not completed alter processing.

For either version of this message, nnnn does notinclude disabled partitions. Disabled partitions willnot be altered.


System actionThe IMS proceeds to alter the number of partitionsshown in the message text.


Module:DFSORP00

Related tasksAltering the definition of an online HALDBdatabase (Database Administration)

DFS3198I HALDB ALTER COMPLETED FORNAME=mastername PARTITIONNUMBER=nnnn STARTED=ssssCOMPLETED=cccc

or

HALDB ALTER ENDED FOR NAME=masternamePARTITION NUMBER=nnnn STARTED=ssssCOMPLETED=cccc

ExplanationThe IMS system exited alter processing.

If the message text reads HALDB ALTER ENDED, theIMS system either did not finish altering one or moreof the partitions that it started or one or more ofthe partitions in the HALDB database were altered byanother IMS system. In the message text, the valueof COMPLETED= is less than the value of PARTITIONNUMBER=.

Possible causes for the HALDB ALTER ENDED messageinclude:

• The TERMINATE OLREORG command was issuedbefore alter processing was complete for one ormore partitions.

• An error occurred during the alter processing of oneor more partitions

• In a data sharing environment, one or more of thepartitions in the HALDB database were altered byanother IMS system.

If the message text reads HALDB ALTER COMPLETED,alter processing completed successfully for all of thepartitions in the HALDB database. In the message text,the values of COMPLETED= and PARTITION NUMBER=are equal.


masternameThe name of the HALDB master database that isbeing altered.

nnnnShows the total number of partitions contained inthe named HALDB database.

ssssShows the number of partitions that this IMSsystem attempted to alter. If both ssss and ccccare 0, this IMS system did not alter any partitionsin a data sharing environment.

ccccShows the number of partitions that this IMSsystem successfully altered. If both ssss and ccccare 0, this IMS system did not alter any partitionsin a data sharing environment.

System actionFor HALDB ALTER ENDED, the IMS system exits alterprocessing. If the HALDB ALTER ENDED message wasissued due to the interruption of the alter process forone or more partitions, the alter process is incomplete.

If the HALDB ALTER ENDED message was issued ina data sharing environment and the STARTED andCOMPLETED values are equal, this IMS system hascompleted all of the partitions that it started. If theSTARTED and COMPLETED values are less than thePARTITION NUMBER value, other IMS systems arealtering other partitions in the HALDB database.

For HALDB ALTER COMPLETE, all of the partitions inthe HALDB database were successfully altered.

System programmer responseFor HALDB ALTER ENDED, determine why this IMSdid not alter all of the partitions in the database. Ifalter processing was interrupted for any partitions,check the messages that preceded this messageto determine the cause of the interruption. Afteryou resolve the problems, resume the alter processby issuing the INITIATE OLREORG command withOPTION(ALTER).

If the HALDB ALTER ENDED messages was issuedbecause one or more partitions were altered byanother IMS system, check to see if the other IMSsystems have completed alter processing also. If theyhave, you can perform online change.

For HALDB ALTER COMPLETE, you can perform onlinechange.

Module:DFSORP00




Related tasksAltering the definition of an online HALDBdatabase (Database Administration)

DFS3199E INTERNAL ERROR xxxxx

ExplanationAn internal error has occurred in the IBM Adapter forREXX. Results cannot be determined.


System programmer responseContact IBM Software Support and supply themessage text.

DFS3200 MSPLINK NOT STOPPED

ExplanationIn order to process the /MSASSIGN LINK command,the MSPLINK specified must be stopped.

System actionThe command is not run. Processing continuesnormally.

Operator responseUse the /PSTOP MSPLINK or UPDATE MSPLINKNAME(msplinkname) STOP command to temporarilystop the physical link. Then reenter the /MSASSIGNcommand.








DFS3201 MAXIMUM SESSIONS REACHEDLINK nnn

ExplanationThe maximum number of parallel sessions wasreached for the MSPLINK specified for the localsystem.

See also message DFS3213I, reason code=32.

System actionThe command is not run. Processing continuesnormally.


System programmer responseAn IMS system definition or temporary JCL changemight be appropriate if more sessions are warranted.


Related informationDFS3213IREMOTE INITIATED LINK START FAILED,REASON CODE=nn. PARTNER ID xx. INITIATORIS NODE nodename.

DFS3202 BIND REJECTED DUE TOINCOMPATIBLE BUFFER/RU SIZELINK nnn

ExplanationThe partner system has rejected the bind because itsoutput buffer size exceeds the current system inputbuffer size, or its input buffer size is less than thecurrent system's output buffer size.


System actionIMS prevents the link from starting.


System programmer responseAn IMS system definition is appropriate.


Related informationDFS3213IREMOTE INITIATED LINK START FAILED,REASON CODE=nn. PARTNER ID xx. INITIATORIS NODE nodename.“IMS problem determination” on page 11IMS messages and codes problemdetermination is accomplished by usingprocedures established by IBM.

DFS3203 BIND REJECTED DUE TO INVALIDSESSION PARAMETERS LINK nnn

ExplanationThe partner system has rejected the bind becauseit is a negotiable bind and MSC/VTAM requiresnonnegotiable type bind.



Operator responseThis problem is possibly a transient error. Try again byrestarting the link from the current system or partnersystem.

System programmer responseA VTAM trace of the bind


Related informationDFS3213IREMOTE INITIATED LINK START FAILED,REASON CODE=nn. PARTNER ID xx. INITIATORIS NODE nodename.“IMS problem determination” on page 11



DFS3204 LINK TYPE NOT VTAM OR TCP/IP

ExplanationThe /CHANGE command specified a link that was noteither a TCP/IP or VTAM type.

System actionThe /CHANGE command is not run. Processingcontinues normally.

Operator responseEnter the correct link.

DFS3206 REMOTE LOGICAL LINK NOTASSIGNED LINK nnn

ExplanationThe partner ID specified in the bind identifies a logicallink belonging to a different physical link at the remoteIMS.

See also message DFS3213I, reason code 04 and 08.


Operator responseUse the /DISPLAY ASMT command at the remote IMSto display the logical-to-physical link assignments,and correct them using the /MSASSIGN MSLINK orUPDATE MSLINK command if in error. Notify thesystem programmer of the problem.

System programmer responseAn IMS system definition is appropriate if the sysdef isincorrect.



DFS3207 REMOTE LINK HAS REACHEDTHE MAX NO. OF ALLOWABLESESSIONS LINK nnn

ExplanationThe maximum number of active sessions allowed atthe remote IMS was reached for this physical link.

See also message DFS3213I, reason code 12.


Operator responseNotify the system programmer at the remote site ifmore sessions are warranted.

System programmer responseIf more sessions are warranted, an IMS systemdefinition or temporary JCL change is appropriate.



DFS3208 REMOTE PHYSICAL LINK ISPSTOPPED LINK nnn

ExplanationThe physical link has been PSTOPPED at the remoteIMS by the remote terminal operator entering theUPDATE MSPLINK STOP or /PSTOP MSPLINKcommand.

See also message DFS3213I, reason code 16.


Operator response(master terminal) Use the /RSTART MSPLINK orUPDATE MSPLINK START command at the remotesite if the PSTOPPED status is unwarranted.


Related informationDFS3213IREMOTE INITIATED LINK START FAILED,REASON CODE=nn. PARTNER ID xx. INITIATORIS NODE nodename.

DFS3209 MULTI-RU ERP OR SYSMSGRECEIVED LINK nnnn

ExplanationAn error recovery procedure (ERP) message orSYSMSG that was not an only-in-chain message wasreceived on the specified link.

System actionThe MSC and link session for the indicated link ID isterminated.


System programmer responseSee Problem Determination.

Problem determination:1, 5, 6, 7, 17b


DFS3210I AREAS RESTART DURING IRLMRECONNECT HAS COMPLETED

ExplanationThe restart portion of the restart or reopen processduring IRLM reconnect has completed. The reopenprocess has initiated.

System actionArea restart/reopen process continues.


DFS3211I MISMATCH RESYNCH CONDITION.THIS SYSTEM IS PRIMARY|SECONDARY STSN: aabbxxxxyyyyRESP: ccddwwwwzzzz LINK nnn

ExplanationAn STSN exchange between partners indicated acold/warm mismatch, or an illogical condition atthe time indicated. This message normally appearson both the local and remote master terminals. Insome cases, however, only one side can differentiatean illogical from a wraparound situation, and thismessage appears only on that side's Master Terminal.The following values are in hexadecimal:aa

Outbound action code of the primarybb

Inbound action code of the primaryxxxx

Outbound sequence number of the primaryyyyy

Inbound sequence number of the primarycc

Ooutbound action code of the secondarydd

Inbound action code of the secondarywwww

Outbound sequence number of the secondaryzzzz

Inbound sequence number of the secondary

System actionThis is an informational message only. Processingcontinues normally.





DFS3212I MISMATCH RESYNCH CONDITIONACCEPTABLE|UNACCEPTABLE TOPRIMARY|SECONDARY LINK nnn

ExplanationThe FORCSESS/SYNCSESS MSLINK macro parameterand recovery logic has determined that the session


initiation might not proceed following the mismatchindicated by the DFS3211I message.

System actionIMS might not permit the session to be initiated, asindicated by the message.

Operator responseNotify the system programmer. If initiation does notproceed and synchronization is not critical, initiationcan be forced by first issuing the /CHANGE or UPDATEMSLINK command on the local or remote systems, orboth.



Related informationDFS3211IMISMATCH RESYNCH CONDITION. THISSYSTEM IS PRIMARY|SECONDARY STSN:aabbxxxxyyyy RESP: ccddwwwwzzzz LINK nnn“IMS problem determination” on page 11IMS messages and codes problemdetermination is accomplished by usingprocedures established by IBM.

DFS3213I REMOTE INITIATED LINK STARTFAILED, REASON CODE=nn.PARTNER ID xx. INITIATOR ISNODE nodename.

ExplanationA remote IMS system, identified by node (nodename)and partner ID (xx), attempted to start a link and failedfor the following reason code (nn):Code

Reason04

The Partner ID specified does not exist on thissystem, or the logical link for NODENAME =nodename could not be found.

08The Partner ID specified is under a differentphysical link on this system, or it exists, but isunassigned to a physical link.

12The maximum number of sessions has beenreached for the associated local physical link.

16The associated local physical link has beenPSTOPPED.

20The buffer size specified for the requested link isincompatible with partner's.

24Bind parameters received are invalid.

28There is a Primary to Secondary LU polaritymismatch. The side that came up cold wassecondary at time of last session failure.Alternatively, if both sides came up warm, at leastone of them restarted after the wrong checkpoint.

32The partner ID specified is already in session.

36Polarity mismatch. Both sides are requestingsecondary LU status.

System actionIMS prevents the link from starting. Processingcontinues normally.

Operator responseUse a QUERY MSLINK or /DISPLAY LINK commandto determine the status of the link or links. Dependingon the reason code, continue as follows:Code

Response04

Notify the system programmer.08

Use /DISPLAY ASMT to display logical-to-physicallink assignments, and correct them with /MSASSIGN LINK or UPDATE MSLINK if in error.Notify the system programmer.

12Notify the system programmer.

16Restart the link from this system if a session iswarranted.

20Notify the system programmer.

24Notify the system programmer. Try again fromeither system.

28Restart the partner with a warm restart (/ERE),cold restart both sides, or restart the link from thisside, or restart following the correct checkpoint.


32Terminate the prior session using /PSTOP tostop the link or VARY NET INACT APPLID.Establishing a new session.

36Verify that both sides were restarted from theproper checkpoint. This problem can happen onlyif both sides are warm started. To get around theproblem, one side must be either set to warmprimary, or set to cold status.

System programmer responseDepends upon reason code, as follows:Code

Response04

An IMS system definition is required.08

An IMS system definition might be required.12

An IMS system definition or temporary JCL changemight be required if more sessions are warranted.

16Not applicable

20An IMS system definition is required.

24Take a VTAM trace of the bind.

28None.

32If the link, in session status, is unwarranted, thencreate a memory dump. You might also have to runan IMS link trace and a VTAM trace to determinewhy the link is being left in the session.

36If the link, in session status, is unwarranted, thencreate a memory dump. You might also have to runan IMS link trace and a VTAM trace to determinewhy both links are requesting secondary status.



DFS3214 COMMAND COMPLETED WITHEXCEPTIONS

ExplanationOne or some of the transactions did not satisfy all ofthe following:

1. Transaction stopped2. No message queued for this transaction code3. Local APPLCTN defined in the SYSDEF

System actionThe command is completed for all but thosetransactions.

Operator responseDetermine which transactions were not reassignedand which of those were not stopped or had messagesqueued by using a QUERY TRAN SHOW(ALL) or /DISTRAN ALL command.



DFS3215W QMGR DISCARDED NON-RECOVERABLE MESSAGE(S) DUETO CQSPUT COMMIT FAILURE

ExplanationOne or more nonrecoverable messages wereunsuccessfully committed. The messages werediscarded. The IMS DFS3215W message is issuedonly once per checkpoint interval, regardless of thenumber of the discarded messages. One set oftype 67D00A diagnostic records is logged for eachdiscarded message.

System actionThe message is deleted from the local IMS. Any partsof the message that was put to the staging queue onthe shared queue are deleted. If the deletion from thestaging queue fails, it will be tried again at the nextcheckpoint.

Programmer responseThe DFS3215W message is expected in certainsituations, such as when the IMS message queueprimary or overflow structure becomes full, andmessages can no longer be put onto the queue orstructure. For such cases, fix the structure full problemeither by making the structure larger or by stopping


the source of the large number of messages that filledthe structure (for runaway message cases).

If the cause of the DFS3215W message is notexplainable, save the IMS logs from at least twocheckpoints before the DFS3215W message, up tothe checkpoint after DFS3215W, and contact IBMSoftware Support to report the problem.

Problem determination:Check type 67D00A diagnostic records to determinethe status of the CQSPUT request. The header ofthe 67D00A record should contain the function anddescription of the error.

Module:DFSQXF00

DFS3216A STRUCTURE structure_name ISBEING DELETED. IT WILL BEREMOVED FROM AREA area_name

ExplanationDuring an attempt to connect to the structure,IMS issued the IXCQUERY command to check forthe structure status. IMS received return codeQUASTRCFHOLD, which indicates that the structurewas being deleted.

System action:The area is not loaded into the coupling facility.

Operator response:If this structure's deletion is correct, remove thestructure from the coupling facility policy. Otherwise,allocate the structure again, and issue the STOP AREAcommand followed by the START AREA command toconnect to the structure.

Module:DBFVXAS0

DFS3217 POLARITY MISMATCH ONSESSION RESTART

ExplanationThis message appears on the master terminal of acold-started IMS system, because of a warm partnerthat was previously the primary partner. Sessionrestart requires that this system be properly restarted(/ERE), or that you enter the /RSTART command onthe warm partner. It is also possible that both sideswere warm started, in which case at least one of thesides restarted after the wrong checkpoint.

See also message DFS3213I, REASON CODE=28 and36.


Operator responseSee explanation above.



Related information“DFS3213I” on page 888REMOTE INITIATED LINK START FAILED,REASON CODE=nn. PARTNER ID xx. INITIATORIS NODE nodename.

DFS3218 INVALID RESTART MESSAGE ORRESTART RESPONSE MESSAGERECEIVED RSN=xxyy, LINK link#

ExplanationThe MSC link was restarted. During the exchangeof the restart messages, an invalid or unexpectedmessage was detected, or the values in the restartmessage indicated incompatible MSC link definitionsbetween the partner IMS systems.

In the messages:xx

Identifies the module.01

DFSCM7D0, a VTAM restart routine02

DFSCMSW0, the CTC or MTM restart routine03

DFSCM7A0, a VTAM restart routine04

DFSCM7B0, a VTAM restart routine05

DFSTC7B0, a TCP/IP restart routineyy

Reason code.01

The partner IMS release is zero or invalid.MSC generally supports two lower or higherversions; for example, Version 10 supportsVersions 8 and 9 and two higher versions.Ensure that the partner is a supported release.If the releases are supported, this problem isan IMS internal error.


02The partner IMS does not support extendedprefixes. Extended prefix support wasintroduced in IMS Version 5 and is requiredif you are connecting to an IMS Version 8 orabove. Ensure that the partner is a supportedrelease. If the release is supported, thisproblem is an IMS internal error.

03The partner IMS ID is invalid. Both sides of thelink must have the same two-character partnerID.

04An invalid restart message was detected; likelythe restart message ID is invalid. This problemis an IMS internal error.

05Bandwidth is incompatible. The partner IMSsystems must both be either BANDWIDTH(OFF) or BANDWIDTH (ON).

06Invalid FMH5. For MSC VTAM, the restartmessage must be proceeded by an FMH5block. This problem is an IMS internal error.

07FMH5 contained an invalid DPN field. For MSCVTAM, the FMH5 block must have DFSCMS00.This problem is an IMS internal error

08The buffer sizes were not equal. Both sides ofthe link must have the same MSLINK buffersize.

09An error occurred getting storage duringbandwidth restart for a QMBA or QLST blockused by QMGR. This problem most likely is aninsufficient storage error. If not, then it is anIMS internal error.

10V10 VTAM link encountered an error rebuildingthe buffers and VTAM control blocks werecompatible with the Version 8 or Version 9partner. This problem might be an IMS internalerror.

11An attempt was made to start a logical link onan MSC TCP/IP physical link that specifies thegeneric IMS ID of a TCP/IP generic resourcegroup, but parallel logical links are alreadyactive or in ERE status on another physical linkthat specifies the IMS ID of the IMS system.All physical links to the same IMS system mustspecify either the same generic IMS ID of aTCP/IP generic resource group or the IMS ID ofthe IMS system.

12An attempt was made to start a logical link onan MSC TCP/IP physical link that specifies theIMS ID of the IMS system, but parallel logicallinks are already active or in ERE status onanother physical link that specifies the genericIMS ID of a TCP/IP generic resource group. Allphysical links to the same IMS system mustspecify either the same generic IMS ID of aTCP/IP generic resource group or the IMS ID ofthe IMS system.

13An attempt was made to start a logical link onan MSC TCP/IP physical link that specifies ageneric IMS ID of a TCP/IP generic resourcegroup, but the IMS system has active physicallinks that specify conflicting IMS ID values. Allphysical links to the same IMS system mustspecify either the same generic IMS ID of aTCP/IP generic resource group or the IMS IDof the IMS system. This problem is an internallogic error.

14An attempt was made to start a logical link onan MSC TCP/IP physical link that specifies theIMS ID of the IMS system, but the IMS systemhas active physical links that specify conflictingIMS ID values. All physical links to the sameIMS system must specify either the samegeneric IMS ID of a TCP/IP generic resourcegroup or the IMS ID of the IMS system. Thisproblem is an internal logic error.

15An attempt was made to start a logical link onan MSC TCP/IP physical link that specifies ageneric IMS ID of a TCP/IP generic resourcegroup, but the STOGENLGN status is set for thephysical link in either the local IMS system orthe remote IMS system.

16An attempt was made to start a logical link onan MSC TCP/IP physical link, but the STOLGNstatus is set for the physical link in either thelocal IMS system or the remote IMS system.

17The value of the GENIMSID= parameter in IMSDFSDCxxx PROCLIB member and the value ofthe GENIMSID= parameter in the IMS ConnectPROCLIB member are not the same. Applies toMSC TCP/IP links.

18The GENIMSID= parameter in the IMSDFSDCxxx PROCLIB member is not specified,but the value of the GENIMSID= parameter inIMS Connect HWSCFGxx PROCLIB member isnot blanks.


19A remote partner IMS system attemptedto logon to an IMS system in a TCP/IPgeneric resource group by using an IMS ID.To logon to an IMS system in a TCP/IPgeneric resource group, remote IMS systemsmust use the generic IMS ID of the TCP/IPgeneric resource group, as specified onthe GENIMSID parameter of the DFSDCxxxPROCLIB members of the participating IMSsystems.

20The GENIMSID in parmlib member DFSDCxxxwas the same value as either the realsubsystem ID (IMSID) or the XRF resourcename (RSENAME). These must be different.

21A restart message was received from a remoteIMS to a XRF alternate IMS. The restartwas rejected with a DFS3218 RSN=0521.This event is a normal condition in a XRFenvironment using a GENIMSID. The errorcondition was issued internally to notify IMSConnect to reject this restart. The restartmessage to the active IMS will be accepted.This message is not issued to the MTO.

link#Identifies the link.


Operator responseRefer to the reason code for possible causesand actions. The DFS3218 reason codes are alsodocumented in the DFSKEYRC macro.

Use the QUERY MSLINK, /DISPLAY LINK, or /DISPLAY LINK OPTION BUFSIZE command oneach side of the link to determine whether the linksare compatible. If error is due to incompatible linkparameters, use the UPDATE MSLINK or /UPDATEMSLINK command to set the parameters compatible.Notify the system programmer if the error persists.

System programmer responseIf the error is not due to incompatible link optionsbetween this side of the link and its partner, or theincompatibility cannot be determined or correctedwith the UPDATE MSLINK command, analyze the6701 MSSx log records produced when the erroroccurred.

To print the type 6701-MSSx (x = 1, 2, 3, and 4) logrecords, use the DFSERA10 log print utility with thefollowing control cards:

CONTROL CNTLOPTION PRINT O=5,V=6701,L=2,C=M,E=DFSERA30OPTION PRINT O=9,V=MSS,L=3,T=C,C=E,E=DFSERA30

If the error is related to the use of TCP/IP genericresources, make sure that all MSC TCP/IP physicallinks to the IMS systems specify either the genericIMS ID of the TCP/IP generic resource group, or theIMS ID of the IMS system. If the link you are startinguses TCP/IP generic resources, you might try directingthe link to another IMS system in the TCP/IP genericresource group.

If the error is related to any of the following linkstatuses, issue the /RSTART LINK command orthe UPDATE MSPLINK command with either theSTART(LOGON) or the START(GENLOGON) keyword:

• PSTOPPED• PSTOPGEN• STOLGN• STOGENLGN

The type-1 /PSTOP MSPLINK command setsthe appropriate stop status, either PSTOPPED orPSTOPGEN, depending on the specification of theGENIMSID parameter in the DFSDCxxx PROCLIBmember. If status is ACTIVE, PSTOPGEN is set, ifDISABLED, PSTOPPED is set. This status can bedisplayed by either the /DISPLAY ASMT MSPLINKor QUERY MSPLINK NAME(msplink_name)SHOW(STATUS) commands.


Module:DFSCMSW0, DFSCM7D0, DFSCM7A0, DFSCM7B0,DFSTC7B0


DFS3220I RECEIVED ERROR RETURN CODE.REQ CODE=xx, REG 0=yy,REG 15=zz, LINK=nnn, CLSDSTSCHEDULED.

ExplanationOne of two conditions exists.

1. An RPL request has failed.


2. A VTAM request (using EXECRPL) failed 25 timesbecause VTAM is short on storage. IMS willterminate the MSC/VTAM link. REG15 is X'04' andREG0 is X'08'.

The following information is given:Code

Meaningxx

Decimal request codeyy

Value (in decimal) placed in Register 0 by VTAMupon returning control to IMS

zzValue (in decimal) placed in Register 15 by VTAMupon returning control to IMS

nnnMSC/VTAM link ID for which the request failed

System actionThe MSC/VTAM link session for the indicated link isterminated. An IMS log record (X'67') with an IDof MSSx (where x=1, 2 or 3) containing pertinentinformation was written.

Operator responseNotify the IMS System Programmer.

Programmer responseSee VTAM V4R3 for MVS/ESA Programming and VTAMMessages and Codes for an explanation of what causedthis return code.

Problem determination1, 5, 6, 7, 17b.


DFS3221 SHOULD NOT OCCUR TYPE LOGICERROR LINK nnn

ExplanationAn illogical condition has been detected by the MSC/VTAM device dependent module for the specified linknnn.

System actionThe MSC/VTAM link session for the indicated link isterminated. An IMS log record (X'67') with an IDof MSSx (where x = 1, 2 or 3) containing pertinentinformation was written.

Operator responseNotify the IMS System Programmer.


Problem determination1, 5, 6, 7 17b


DFS3222I UNEXPECTED STATUS|FORCECLEANUP DONE| LINK=nnn,UNDEFN | SIMLOG | OPNDST |CLSDST | SESSNC | RECEIV |SEND | RESTR | RQSESS | OPNSEC| TRMSESS | ******, RC=xx,FDB2=yy, LOSTERM | NSEXIT |UNBIND=zz, SENSE=wwww

ExplanationIf UNEXPECTED STATUS is present in the message,an RPL request (indicated by one of the values inbrackets, including ****** if unknown) resulted in anunexpected return status from VTAM.

If FORCE CLEANUP DONE is present in the message,an RPL request (indicated by one of the values inbrackets, including ****** if unknown) was canceledby a /PSTOP LINK FORCE command and an NSEXITevent was simulated by IMS to cause the link to bePSTOPPED and IDLE.

The message includes the following information:Code

Meaningnnn

MSC/VTAM link ID for which condition occurredxx

Hexadecimal value of RPLRTNCD field of RPLyy

Hexadecimal value of RPLFDB2 field of RPL


zzHexadecimal IMS LOSTERM/NSEXIT/UNBINDindicator (See message DFS970I for anexplanation of the zz values.)

wwwwHexadecimal value of RPLSSNSI field of RPL

System actionThe MSC/VTAM session is terminated for the specifiedlink.


System programmer responseSee VTAM Messages and Codes (SC31-6493) for anexplanation of the code meanings.


Related information“DFS970I” on page 348(UNEXPECTED STATUS| OPNDST/OPNSESSFAILED| CLSDST/TRMSESS FAILED| GENCB/MODCB ERROR| FORCED CLEANUP DONE|SESSION FAILURE), NODE node name, USER/user name| N/A, (UNDEFN | SETLOG | SIMLOG| OPNDST | OPNSEC | CLSDST | SEND|RECEIV| TRMSES | RQR | RESTSR | INQUIR|SESSNC| ******), RC=,FDB2=, LOSTERM=|NSEXIT=|UNBIND=, SENSE=, REASON=“IMS problem determination” on page 11IMS messages and codes problemdetermination is accomplished by usingprocedures established by IBM.

DFS3223 INVALID EXCP RESPONSERECEIVED LINK nnn

ExplanationAn exception response was received on the specifiedMSC/VTAM link nnn and was not an 0846 typeexception response.

System actionThe MSC/VTAM link session is terminated for thespecified link ID.




DFS3224 EXCP RESPONSE RECEIVED FORWRONG RU NUMBER LINK nnn

ExplanationAn 0846 exception response was received on thespecified link nnn, for an invalid RU number.

System actionThe link session is terminated for the specified MSC/VTAM link ID.





DFS3225 UNEXPECTED RRN RESPONSERECEIVED LINK nnn

ExplanationAn unexpected VTAM RRN response was received onthe specified link nnn.

System actionThe link session is terminated for the specified MSC/VTAM link.






DFS3226 CHAINING ERROR ON DATARECEIVED LINK nnn

ExplanationAn SNA chaining error was encountered in an RUreceived on the specified link nnn.

System actionThe session is terminated for the indicated MSC/VTAMlink.





DFS3227 RU SEQUENCE ERROR ON DATARECEIVED LINK nnn

ExplanationAn SNA sequence error was encountered on an RUreceived on the specified link nnn.






DFS3228 BRACKETS ERROR ON DATARECEIVED LINK nnn

ExplanationAn SNA brackets error has been encountered on an RUreceived on the specified link nnn.






DFS3229 UNEXPECTED FMH ON DATARECEIVED LINK nnn

ExplanationAn RU with FMH was received on the specified MSC/VTAM link nnn when no FMH was expected.







DFS3230 EXPECTED FMH7 NOT RECEIVEDLINK nnn

ExplanationA selective receiver ERP message was expected on thespecified MSC/VTAM link nnn, but something differentwas received.






DFS3231 INVALID FMH5 RECEIVED LINKnnn

ExplanationAn RU with invalid FMH Type 5 was received on thespecified MSC/VTAM link nnn.






DFS3232 EXPECTED FMH5 NOT RECEIVEDLINK nnn

ExplanationAn expected FMH Type 5 did not occur in the RUreceived on the specified link nnn.








DFS3233 INVALID FMH6 RECEIVED LINKnnn

ExplanationAn invalid Type 6 FMH was received on the specifiedlink nnn.






DFS3234 DR1 RESPONSE RECEIVED FORWRONG RU LINK nnn

ExplanationA DR1 received for a SNA command did not carry theVTAM sequence number of the command.

System actionThe session is terminated for the indicated link.





DFS3235 BIS/SBI RECEIVED TWICE LINKnnn

ExplanationAn SNA BIS or SBI command was received twice onthe specified link nnn.






DFS3236 DR2 RESPONSE RECEIVED FORWRONG RU NUMBER LINK nnn

ExplanationA DR2 received for SNA data did not carry the VTAMsequence number of the OIC/LIC.







DFS3237 UNEXPECTED FME RESPONSERECEIVED LINK nnn

ExplanationAn unexpected SNA FME response occurred on theindicated MSC/VTAM link nnn.






DFS3238 INVALID/UNEXPECTEDINFORMATION RECEIVED LINKnnn

ExplanationA SNA command or LU was received that is notsupported by MSC/VTAM.




Problem determination1, 5, 6, 6, 7, 17b


DFS3239 CLSDST/TERMSS ISSUED LINKnnn

ExplanationA VTAM CLSDST or TERMSESS has been issued onthe specified MSC/VTAM link nnn as a result of eitheran operator request or error situation encounteredpreviously.





DFS3240 DATA RECEIVED EXCEEDSALLOCATED INPUT BUFFER LINKnnn

ExplanationData received on the specified MSC/VTAM link nnnexceeded the input buffer allocation.







DFS3241 DATA FRAME COUNT DOESNOT AGREE WITH RPL BYTES-RECEIVED COUNT LINK nnn

ExplanationThe MSC data frame count (first 2 bytes of the MSCRU) does not agree with the value indicated by VTAMin the RECEIVE RPL for the specified MSC/VTAM linknnn.






DFS3242I PARTNER SHUTTING DOWN LINKnnn

ExplanationThe last message sent to the link partner has beenrejected because the partner commenced shutdownjust as the message arrived.

System actionThe message is returned to queue by the currentsystem.


Problem determinationNone

DFS3243I PARTNER SHUTTING LINK DOWNLINK nnn

ExplanationThe last message sent to the link partner hasbeen rejected, because the partner commenced linkshutdown just as the message arrived.




Problem determinationNone

DFS3244I PARTNER NOT ACCEPTING INPUTLINK nnn

ExplanationThe last message sent to the link partner wasrejected, because the partner just encountered anerror situation which prevented further accepting ofinput on this link.


Operator responseContact the system operator of the partner for cause ofthe error.




DFS3245 INVALID RESPONSE TYPEREQUESTED BY RU RECEIVEDLINK nnn

ExplanationAn RU received has violated the MSC/VTAM protocolby requesting an incorrect type of SNA response.






DFS3246 INVALID CD INDICATOR SET ONRU RECEIVED LINK nnn

ExplanationAn RU received carries a CD indicator, in violation ofthe MSC/VTAM protocol.






DFS3247I UNEXPECTED FME AND RRNRESPONSE RECEIVED ON LINKnnnn

ExplanationAn unexpected SNA FME plus RRN response wasreceived on the indicated VTAM link.

System actionThe MSC and link session for the indicated link ID isterminated.





DFS3248W A LONG DELAY IN LOGSURVEILLANCE

Explanation:The logging activity in the XRF active IMS is suspendedlonger than the limit specified in the LOG= parameterin the DFSHSBxx member of the IMS PROCLIB dataset.

System action:IMS continues processing normally.

Operator response:Check the XRF active IMS system to determine whythe logging activity has been suspended excessively,and correct it if any abnormal condition exists.

Module:DFSHTKO0

DFS3249W A LONG DELAY IN LINKSURVEILLANCE

Explanation:XRF LINK surveillance in the active IMS is suspendedlonger than the limit specified in the LNK= parameterin the DFSHSBxx member of the IMS PROCLIB dataset.



Operator response:Check the XRF active IMS system to determinewhy XRF ISC LINK surveillance has been suspendedexcessively, and correct it if any abnormal conditionexists.

Module:DFSHTKO0

DFS3250 COMMAND NOT ENTERED FROMMASTER TERMINAL OR SYSTEMCONSOLE

ExplanationA restricted version of a /LOCK or an /UNLOCKcommand was entered from a remote terminal, but

is only allowed from the master terminal or systemconsole. The /LOCK command with keyword DB,PROG, or TRAN, and the /UNLOCK command withkeyword DB, PROG, TRAN, or SYSTEM can only beentered from the master terminal or system console.

System actionThe /LOCK or /UNLOCK command is ignored.

Operator response:(local/remote terminal operator) Reenter thecommand on the system console or master terminal.




DFS3251W A LONG DELAY IN RDSSURVEILLANCE

Explanation:XRF RDS (restart data set) surveillance in the activeIMS is suspended longer than the limit specified in theLNK= parameter in the DFSHSBxx member of the IMSPROCLIB data set.


Operator response:Check the XRF active IMS system to determine whyRDS surveillance has been suspended excessively, andcorrect it if any abnormal condition exists.

Module:DFSHTKO0

DFS3252I DATA EXISTS ON yyy LOG THATDOES NOT EXIST ON zzz LOG.

ExplanationDuring the processing of the Log Recovery utility inCLS mode, DFSULG20 found that data existed on oneinput log but did not exist on the other log. Also, whenDFSFDLW0 was called to copy log records from theWADS, all the records already existed on one of theinput logs. This scenario can happen, for instance, ifthere is a write error on one of the OLDSs. This is notnecessarily an error condition because the Log Archiveutility also detects this inconsistency and creates SLDSor RLDS from the OLDS that has all of the data.

In the message text, the values of yyy and zzz canbe either PRIMARY and SECONDARY or vice versa,depending upon which is appropriate in which spot.

System actionThe utility dumps the error block, which might be theend-of-file marker if a write error was encountered,and continues processing in CLS mode. Neither OLDSis flagged as being in error in DBRC.

User responseNo response is necessary. This message is put outas informational to make you aware that one OLDSdoes not contain all of the data that it is supposed to.You might have already known before running the LogRecovery utility that the OLDS encountered a problemsuch as a write error.

Problem determination:To determine which blocks are on one OLDS and noton the other, you can use a tool such as IMS ProblemInvestigator for z/OS or DFSERA10 to check type 4800log records. There is one type 4800 log record perblock and it contains fields such as the block sequencenumber.

DFS3253W WADS PROCESSING WARNING.FUNCTION = XX. REASON = YY.

ExplanationWhen Data Facility Storage Management Subsystem(DFSMS) opens WADS, DFSMS issues IEC messagesin the job log. The DFS3253W message indicates thatthe IEC messages in the job log do not require furtheraction.

The following table lists the possible values forfunction XX and the corresponding reason YY:


Function XX Reason YY Explanation

04 (OPEN) Contents ofACBERFLG

Opening theWADS producedan informationalmessage. FormoreinformationaboutACBERFLG, seez/OS: OPENreturn andreason codes forVSAM macroinstructions

The mostcommon reasoncode forACBERFLGwhen XX = 04 isx'74', whichindicates thatthe data set wasnot closedproperly. Thishappens, forexample, whenthe log recoveryutility(DFSULTR0)runs after anIMS abendbecause theWADS cannot beclosed whenIMS abends.

System actionIMS continues processing normally.



Module:DFSFDLW0

Related referencez/OS: OPEN return and reason codes for VSAMmacro instructions

DFS3254I BUFSTOR FORCED TO 31 BECAUSEBLKSIZE NOT A MULTIPLE OF 4K

ExplanationBefore obtaining 64-bit addressable storage for OLDSlog buffers, IMS verifies the value of the BLKSIZEparameter defined on the OLDSDEF statement of theDFSDFxxx member of the IMS PROCLIB data set. IMSissues this message if the BLKSIZE parameter value isnot a multiple of 4096.

System actionIMS obtains 31-bit addressable storage for thelog buffers, overriding the BUFSTOR=64 parameterspecifying 64-bit addressable storage on the OLDSDEFstatement, and continues processing.


IMS always obtains 31-bit addressable storage forOLDS log buffers unless the value given for BLKSIZE isa multiple of 4096. Ensure that the value given for theBLKSIZE parameter is a multiple of 4096 if you want touse 64-bit addressable storage for OLDS log buffers.

Module:DFSPRSL0

DFS3255I MAXSESS TOO LARGE FOR MSC/VTAM LINK nnn, DEFAULTING TO676

ExplanationThe sum of the MAXSESS field defined at systemdefinition time and the NLXB JCL parameter exceeds676 for the specified nnn MSC/VTAM link. The largestMAXSESS allowed is 676.

System actionThe MAXSESS field in the associated LCB is set to 676,and processing continues.


System programmer responseCheck the MAXSESS field in system definition for thislink, and check the NLXB parameter in the IMS controlregion JCL.

DFS3256I OPEN FAILED ON ddname -DURING ONLINE LOG READ (xx)


http://www-01.ibm.com/support/knowledgecenter/SSLTBW_2.3.0/com.ibm.zos.v2r3.idad500/x1cb.htm







or

OPEN/ALLOCATION FAILED ON ddname

or

OPEN FAILED ON ddname - DD CARDSPECIFICATION ERROR

ExplanationThe log data set specified on the ddname could notbe opened or allocated for logging, because the DDstatement was not correctly specified or because thepreallocated data set had inconsistent DCB attributes.

The first form of this message applies to log writeoperations for either an online log data set (OLDS), or awrite-ahead data set (WADS).

The second form of this message is issued under theseconditions:

• When an OLDS is opened that has a different blocksize (BLKSIZE) from the value displayed in messageDFS2207I.

• When a write-ahead data set (WADS) is openedwhich does not have sufficient space allocated.

• When the RECFM is not VB.• When an extended format OLDS was found and this

release of IMS cannot use an extended format OLDS.

The third form of the message appears when theGETMAIN storage is not available for the OSAMDCB required for a log read operation. It is alsoissued when the OSAM OPEN function fails. When theGETMAIN storage is not available, xx contains a valueof x'FF'. When the OSAM OPEN function fails, xx isthe return code value returned by the OSAM OPENfunction.

System actionIf the error occurred while opening a WADS andone or more WADS was still available, IMS continuesprocessing. If no WADS was available, messageDFS3262I is issued and IMS continues processing.

If the error occurred while opening an OLDS and3 or more OLDS are still available, IMS continuesprocessing. If 2 or less OLDS are available, messageDFS3260I is issued. See the system action formessage DFS3260I.



Related information“DFS2207I” on page 649IMS LOG(S) BLOCKSIZE=xxxxx, BUFNO=yyyy“DFS3260I” on page 906ONLINE LOG DATA SET SHORTAGE - NEEDANOTHER DATA SET“DFS3262E” on page 907NO DATA SET AVAILABLE FOR LOG WRITEAHEAD

DFS3257I ONLINE LOG NOW OPENED ONddname

or

ONLINE LOG NOW SWITCHED - FROM ddname1 TOddname2

or

ONLINE LOG CLOSED ON ddname

or

OLDS|WADS DEALLOCATED ON ddname

ExplanationThe first form of the message appears when IMSrestart takes place and the online log data set (OLDS)is ready for use.

The second form of the message is issued eachtime the OLDS (ddname1) becomes full, EOV wasforced, or OLDS (ddname1) incurred an I/O error andwas closed. The next OLDS (ddname2) is opened forfurther logging. During an XRF takeover, the secondform of the message appears. ddname1 is the OLDSthat is terminated from the WADS when takeover isrequested.

The third form of this message appears when normalshutdown is scheduled and OLDS is closed.

The fourth form of this message is issued o the masterterminal when some OLDS are forced to stop, by a /STOP command or because of I/O error. The log dataset is no longer needed for online database backout,and the log data set is removed from the candidate list


for future use. This OLDS is dynamically deallocatedfrom the control address space.


Operator responseIf automatic archiving is not specified, display theOLDS status to determine whether to submit anarchive job.

When the fourth form of the message appears, thespecified OLDS is ready for repair. After the OLDShas been archived, the data set can be scratchedand reallocated on another volume. Then the /STARTOLDS command can be entered to reconnect the OLDSto the online IMS.


DFS3258A LAST ONLINE LOG DATA SET ISBEING USED - NEED ARCHIVE

or

SYSTEM WAITING FOR AN ONLINE LOG DATA SET -NEED ARCHIVE

ExplanationThe first form of this message is sent when IMS™

detects that the last unarchived online log data set(OLDS) was being used. All the other OLDS are notreusable for output operation, because they have notyet been archived or have been stopped.

The second form of this message is sent when all non-stopped OLDS require archiving. The second messageis repeated at 5 minute intervals until the situation isresolved by archive completion.

System actionFor the first form, IMS continues processing. For thesecond form, IMS is in a wait state until some OLDSbecome usable.

Operator response:If an archive job is not currently running, submitan archive job to free up OLDS. Also in a z/OSenvironment, a new data set can be added with the /START OLDS command only if there is Log bufferavailable.


DFS3259I ONLINE LOG DATA SET NOT YETARCHIVED FOR ddname

ExplanationThe online log data set (OLDS), identified by ddname,would normally have been archived and be ready forreuse. However, it was not archived.

System actionIMS will use another available OLDS and continueprocessing.

System operator response: If an archive job for thespecified log data set is not executing, submit anarchive job.


DFS3260I ONLINE LOG DATA SET SHORTAGE- NEED ANOTHER DATA SET

ExplanationBecause of I/O errors or /STOP OLDS commands, twoor less online log data sets (OLDS), are available whichcan be used by IMS.

System actionIf two OLDS remain, IMS continues processing. If thereis only one, IMS initiates a /CHE FREEZE.

Operator responseThe /DISPLAY OLDS command can be used todisplay the status of all OLDS. When two datasets remain, any one of the following responses isacceptable:

• No response, IMS continues processing.• In a z/OS environment, additional OLDS can be

activated using the /START OLDS command.• The checkpoint command can be used to initiate an

IMS shutdown.


DFS3261I WRITE AHEAD DATA SET NOW ONddname


ExplanationThe log write-ahead function is now using the dataset identified by ddname. During IMS execution, thismessage might follow a WADS I/O error message.




DFS3262E NO DATA SET AVAILABLE FOR LOGWRITE AHEAD

ExplanationEither the WAD's are too small, or errors have occurredOPENing or writing to the WADS, and no more WADSare available.

System actionIMS continues processing. However, the systemperformance can be degraded because the log write-ahead support will cause the online log buffers to betruncated.

System operator response: No response is required.The checkpoint command can be used to shutdownIMS. Writing to the WADS will be reattempted after thenext restart of IMS.

Programmer responseAllocate new WADs.

DFS3263I ARCHIVE UTILITY ENDEDUNSUCCESSFULLY (rrrrrrrr)

or

ARCHIVE UTILITY ENDED SUCCESSFULLY

or

ARCHIVE UTILITY ENDED SUCCESSFULLY (rrrrrrrr)

ExplanationThe Log Archive Utility terminated either successfullyor unsuccessfully. A reason for termination is given incases where a programmer response is required. Thevalues for rrrrrrrr are:

• SUCCESSFULLY - (BUT NOT ALL OLDS WEREARCHIVED)

• UNSUCCESSFULLY - (OPEN ERROR) (DBRCVERIFICATION FAILED: INPUT LOG(S), SSID ORRECON(S) ARE INVALID)

• (EXEC PARAMETER ERROR)• (CONTROL STATEMENT ERROR)• (DATA SET SPECIFICATION ERROR)• (ERROR IN SINGLE INPUT LOG)• (DUPLICATE ERROR IN DUAL INPUT LOG)• (OUTPUT DATA SET I/O ERROR)• (OUT-OF-SPACE IN OUTPUT DATA SET)• (UNSUCCESSFUL EXCHANGE BETWEEN DUAL

INPUT DATA SETS)• (USER EXIT ROUTINE ERROR)• (DEVICE TYPE ERROR)• (OUTPUT DATA SET BLOCK/TRACK SIZE IS TOO

SMALL)• (DBRC MODULE NOT FOUND)• (NON-ZERO RETURN CODE FROM ISITMGD)

System actionIf the Log Archive Utility ended SUCCESSFULLY witha return code of 0 and no accompanying reason,then all online log data sets (OLDS) were archivedas identified in the SYSPRINT output messages. Theutility terminated normally.

If the Log Archive Utility ended SUCCESSFULLY with areturn code of 4 and the accompanying reason "(BUTNOT ALL OLDS WERE NOT ARCHIVED)", then one orboth of the following reasons apply to this archive job:

• The system encountered a recovery point in anOLDS, archived that OLDS, and terminated withoutarchiving any more OLDS. A recovery point results atevery /DBR or /DBD command that forces an OLDSswitch.

• An OLDS specified as input to the Archive utility wasalready archived when this job ran. The SYSPRINToutput messages will identify the OLDS that werealready archived.

If the Log Archive Utility ended UNSUCCESSFULLY,then the accompanying reason, additional DFSmessages, and messages in the SYSPRINT outputidentify the reason for abnormal termination.


Programmer responseIf all OLDS were not archived because theyencountered a recovery point, then run the Log ArchiveUtility for the unarchived OLDS.

If the utility ended UNSUCCESSFULLY, correct theerror and rerun the Log Archive Utility.

DFS3264I ARCHIVE UNABLE TO OPEN zzzz

or

ARCHIVE UNABLE TO OPEN|CLOSE xxxx ddname

ExplanationThe xxxx value in the first message is the online logdata sets (OLDS), system log data sets (SLDS), orUSER. Field xxxx indicates the type of data set thatcould not be opened or closed. ddname is the name ofthe DD statement for the data set.

The zzzz value in the second message is SYSIN orSYSPRINT, which indicates that the data set could notbe successfully opened.

System actionIn the case of dual input or user output data sets,the processing continues. In any other case, the LogArchive utility will be terminated with a return code.


Programmer responseIf the Log Archive utility fails, ensure that the DDstatements are present and that the specifications arecorrect; then rerun the job.

DFS3265I xxxxxx ERROR DURING WADSPROCESSING

or

xxxxxx ERROR IN WADS DD - ddname

ExplanationThe specified write-ahead data sets (WADS) errorwas encountered while the Log Recovery Utility was

performing in CLS or DUP mode with the CLOSE option.The values for xxxxxx can be:OPEN

An error occurred while opening the WADS.READ

An error occurred while reading the WADS.DEVICE TYPE

The device type of the data set specified as aWADS is not DASD.

SEQUENCE #Data required to properly close the online log datasets (OLDS) is missing from WADS.

CLOSEAn error occurred while closing the WADS.

TRKCALCAn error occurred in the MVS TRKCALC function.

LOGICAn internal logic error was detected by the WADSread module (DFSFDLW0).

VERIFYAn error was found in the WADS DD statement(DFSWADS0).

MISSING RCDA sequence of WADS records had fewer recordsthan it should.

System actionThe Log Recovery utility, DFSULTR0, terminates withabend 3265.

DFS3266I CONTROL STATEMENT ERRORrrrrrr

ExplanationThe control statement contains an error. rrrrrrdescribes the type of error, and one of the values ofrrrrrr will appear depending on the type of error. Thevalues of rrrrrr are:

(NO OPERATION CODE)(INVALID OPERATION CODE OR PARAMETER)(NO DDNOUT1 OR DDNAME LENGTH ERROR INCOPY)(INVALID SPECIFICATION IN NOLOG)(NO NAME OR NAME LENGTH ERROR IN EXIT)(NO NOLOG AND NO FEOV IN SLDS)('MUST BE WRITTEN' LOG IN NOLOG)(CONCATENATION ERROR)(DUPLICATE SPECIFICATION)(PARENTHESIS ERROR)(INVALID OFFSET SPECIFICATION)(INVALID FLDLEN SPECIFICATION)


(INVALID FLDTYP SPECIFICATION)(INVALID COND SPECIFICATION)(INVALID VALUE SPECIFICATION)(INVALID FEOV SPECIFICATION)(INVALID DBRECOV SPECIFICATION)(INVALID DDNAME SPECIFIED IN COPYSTATEMENT)

System actionThe Log Archive utility will be terminated with a returncode.


Programmer responseCorrect the control statement and rerun the job.

DFS3267I USER EXIT ROUTINE entrynameFAILED AT zzzz EXIT RC=xx

ExplanationThe value of zzzz is INITIALIZATION, PROCESSING,or TERMINATION. An exit routine returned to the logArchive utility with a return code other than a binaryzero. xx is the decimal return code value returned bythe named (entry point) exit routine.

System actionThe Log Archive utility processing terminates.

Operator responseNone.

Programmer responseThe required response is a function of the exitroutine's processing.

DFS3268I DD CARD ERROR - rrrr

ExplanationDuring the processing of the Log Recovery utility,a data set specification error was found. rrrr is adescriptive error reason. The values for rrrr are:

• NO OUTPUT LOG IS SPECIFIED• NO INPUT LOG IS SPECIFIED• BOTH OLDS AND SLDS ARE SPECIFIED• INPUT LOG DEVICE TYPE ERROR

• OUTPUT LOG DEVICE TYPE ERROR• PRIMARY AND SECONDARY SLDS HAVEDIFFERENT BLOCK SIZE

• NO PRIMARY NEXT OLDS IS SPECIFIED• BOTH WADS AND NEXT OLDS ARE SPECIFIED• INCORRECT NEXT OLDS IS SPECIFIED• WADS IS SPECIFIED, BUT NO WADS WASAVAILABLE AT TIME OF LAST OLDS WRITE

• WADS IN USE AT TIME OF LAST OLDS WRITENOT SPECIFIED

• DUP OR REP MODE AND PRIOR OLDS ARESPECIFIED

• OLDS INPUT IS REQUIRED• NO PRIMARY INPUT IS SPECIFIED• WADS OR NEXT OLDS SPECIFIED WITHDUP/REP MODE

• OUTPUT LOG SHOULD NOT BE SPECIFIED• PRIOR OLDS NEEDED BUT NOT SPECIFIED• CLS FAILS - PRIOR OLDS INVALID• CLS FAILS - PRIOR OLDS POSITIONINGFAILED

• INVALID INPUT DATA SET ATTRIBUTES ONdsname

dsname is a variable describing which input dataset had invalid attributes. Some examples include:DFSOLP, DFSOLS, IEFRDER and IEFRDER2.

• PSB MODE REQUIRES IEFRDER INPUT DD CARD

System actionThe Log Recovery utility fails.

Programmer responseCorrect the JCL and rerun the job.

DFS3269I TRACK SIZE OF xxxx ddname ISTOO SMALL, OLDS BLKSIZE=yyyy

or

BLOCK SIZE OF xxxx ddname IS TOO SMALL, OLDSBLKSIZE=yyyy

ExplanationThe block or track size of the specified output data setis too small to contain a log record that must be copiedfrom the input data set. The value xxxx is the systemlog data set (SLDS), user data set (USER) or recovery


log data set (RLDS). The value yyyy is the block size ofthe input data set.

System actionThe Log Archive utility is terminated.

Programmer responseSpecify a block size equal to the displayed OLDS blocksize for the data set which encountered this error, andrerun the job.

DFS3270I INVALID INPUT LOG IS SPECIFIED

ExplanationThe DBRC verification of the input log failed. The inputlog might have already been closed, or DBRC cannotfind the RECON record for the specified input log.

System actionThe Log Recovery utility, DFSULTR0, failed.

Programmer responseSYSPRINT should contain a DBRC error message. Seethe explanation in message DSP0311I. Verify that thecorrect IMSID was specified in the EXEC parametersand that the correct data set name was specified onthe input log DD statement. If the wrong IMSID orinput log was specified, correct the JCL, and rerun thejob.

Related informationDSP0311I (Messages and Codes)

DFS3271I zzzzzz = LOG DATA DOES NOTSATISFY LSN KEYWORD

or

zzzzzz = REQUIRED LOG DATA NOT FOUND

or

zzzzzz = LOG DATA EXISTS BEYOND EXPECTEDCLOSE POINT

ExplanationThe first form of this message, where the zzzzzz valueis REQUIRED LOG DATA NOT FOUND, indicates that

the Log Recovery utility has encountered one of thefollowing conditions:

• NOWADS is specified.

The DFSWADSn DD card may still be present in theexecution JCL.

• NEXT OLDS and CLS specified.

The last block successfully written to the input OLDShas been located. Its block sequence number is notone less than the block sequence number of the firstblock in the NEXT OLDS.

• NEXT OLDS and DUP specified.

The block corresponding to the ERRC value or end-of-file has been encountered on the input OLDS. Itsblock sequence number is not one less than theblock sequence number of the first block in the NEXTOLDS.

• WADS is specified.

The first error was encountered in CLS mode or inthe ERRC number of errors in DUP mode, but theinput OLDS was not positioned so that its blocksequence number is one less than the first block inthe WADS.

CLS mode end-of-file checking could notsuccessfully reread the last good block on the OLDS.

The second form of this message, where the zzzzzzvalue is LOG DATA EXISTS BEYOND EXPECTED CLOSEPOINT, indicates that the Log Recovery utility hasencountered the following condition:

• Input data set is a SLDS.

ERRC number of errors were encountered on theinput SLDS, but the SLDS contains additional blockswith later time stamp values. This indicates thatSLDS is not correctly positioned for close.

• CLS mode.

The first error was encountered in CLS mode, butend-of-file checking found additional blocks withlater time stamp values.

The third form of this message, where the zzzzzzvalue is LOG DATA DOES NOT SATISFY LSN KEYWORD,indicates that the last log sequence number read byCLS or DUP mode is less than the value specified forthe LSN keyword.

System actionThe Log Recovery utility, DFSULTR0, terminatesunsuccessfully. For the REQUIRED LOG DATA NOTFOUND and end-of-data detected cases, abend U3271is issued.



Programmer responseIf CLS mode was specified, change it to DUP modewith an error count other than zero. If DUP mode wasspecified, increase the error count value, and rerunthe job. If NOWADS was specified assure that noDFSWADSn DD card is present, if present remove andrerun the job.

DFS3272I OLDS ERROR. ACTIVE PSBMESSAGES NOT GENERATED.

or

X'47' LOG RECORD NOT FOUND. RECOVERYREQUIREMENTS NOT GENERATED.

or

X'47' LOG RECORD NOT FOUND. ACTIVE PSBMESSAGES NOT GENERATED.

Explanation:This message is related to DFS3272E. See theinformation on that message for a detailed explanationand actions.

Related informationDFS3272EINTERNAL ERROR DURING LOG RECOVERY

DFS3272E INTERNAL ERROR DURING LOGRECOVERY

ExplanationThe write-ahead data set, WADS, was specified asinput to the Log Recovery utility. The Log Recoveryutility could not determine the active PSBs from thelog data processed.

The first and second forms of this message are issuedwhen a X'47', an active PSTs log record written atcheckpoint time, was not found in the input (online logdata sets (OLDS) and WADS).

The X'47' record contains a list of all active PSBs, andis required to ensure that the PSB report is complete.

The third form of this message is issued when an OLDSerror is encountered. This means that the log recordsare missing, and therefore, the analysis of the activePSBs cannot be correctly performed.

The fourth form of this message is issued whenan internal error occurs during Log Recovery utilityprocessing.

System actionIf this is not a "rerun" of the Log Recovery utilityin PSB mode, the OLDS close process is completed.Otherwise, the Log Recovery utility simply terminates.

Programmer responseIf you received the first two forms of this message andyou need the active PSB information, do the following:

• Rerun the job in CLS mode, specifying the previousand current OLDS as concatenated data sets in yourinput.

• Specify PSBLIST=YES and DBRC=NO as execparameters so that DBRC processing will bebypassed.

For the third form of this message, ensure that theprevious and current OLDS were concatenated in thecorrect sequence. If OLDSs are specified correctly, usethe Log Recovery utility in DUP mode to create a validOLDS.

If you received the fourth form of this message,check your log record concatenation in your IEFRDERDD statement. A possible log record sequence erroroccurred.

DFS3273I UNABLE TO PROCESS xxxCOMMAND FOR ddname, REASONCODE nn

ExplanationA /START OLDS, /START WADS, /STOP OLDS, /STOP WADS, or /SWITCH WADS command could notbe processed. The value of xxx is /START, /STOP,or /SWI indicating which command could not beprocessed. The reason code nn is a hexadecimalnumber.

For a /START command failure, one of the followingreason codes occurs:Code (hex)

Meaning04

The OLDS or WADS could not be dynamicallyallocated. Either no DFSMDA member exists forthe specified OLDS or WADS, or the dynamicallocation request failed.

08One of these errors occurred: The specified OLDSis already allocated to this IMS and encountereda write error, the OLDS or WADS encountered adevice-type error, or the WADS was allocated asDD DUMMY.


0CThe specified WADS is already allocated to thisIMS, or the OLDS DSET table is full.

10The WADS device type is not the same asthe WADS device type established at DLOGinitialization.

14A permanent I/O error occurred while attemptingto format the specified WADS.

For a /STOP command failure, one of the followingreason codes occurs:Code (hex)

Meaning04

The specified OLDS or WADS is currently in useand cannot be stopped.

08Less than 2 OLDS are currently available to thisIMS. If this command is executed, it will result inan internal checkpoint freeze shutdown.

0CThe specified OLDS or WADS is not currentlydefined to this IMS.

For a /SWI command failure, one of the followingreason codes occurs:Code (hex)

Meaning01

Insufficient WADS for switch. There must be atleast one spare WADS, or two spare WADS if IMS isrunning with dual WADS.

02IMS is not currently using WADS. Some WADSmust be started before a switch command ismeaningful.

03A failure occurred opening the spare WADS.


Operator responseIf less than 2 OLDS are currently available, it mightbe possible to use the /START OLDS command tostart additional OLDS and then retry the /STOP OLDScommand. If the current OLDS should be stopped, itmust first be closed with a command, such as /DBR,that causes a switch to the next OLDS.

In the case of a /START OLDS failure, notify thesystem programmer.



DFS3274I DBRC LOG xxxx EXIT FAILED (yy)

ExplanationEither a DBRC request submitted by the IMS LogArchive utility or by the Log Recovery utility wasunsuccessful, or a request to access or update theRECON data sets failed. The specific type of DBRC exitinvoked is indicated by xxxx. The value of xxxx can beone of the following:

ARCHIVE INITARCHIVE COMPLETERECOVERY INITRECOVERY OPENRECOVERY EOVRECOVERY CLOSE

The DBRC return code value is displayed as yy(hexadecimal) in the message. Convert this valueto decimal and see the DBRC request return codeinformation.

System actionThe Log Archive utility or Log Recovery utility issuesabend 3274.

Programmer responseIf the wrong RECON data sets have been identified, orthe RECON 1 and RECON 2 DD statements are missing,correct them. Otherwise, an analysis is required todetermine the reason for the DBRC exit failure.


Related referenceDBRC request return codes (Messages andCodes)Related information“IMS problem determination” on page 11IMS messages and codes problemdetermination is accomplished by usingprocedures established by IBM.

DFS3275I EXEC PARAMETER ERROR




ExplanationEither an EXEC parameter is incorrectly specified, orthe specified combination of EXEC parameters, DDstatements, and control statements is invalid.

System actionThe Log Recovery utility failed.

Programmer responseCorrect the parameter and rerun the job. See IMSVersion 15 System Utilities and IMS Version 15Operations and Automation for an explanation of theLog Recovery utility EXEC parameter.

DFS3276I PRIMARY OR SECONDARY OLDSHAS BAD CONTENTS

ExplanationThe contents of the primary input OLDS is differentfrom the secondary OLDS. The primary or thesecondary OLDS encountered a write error and wasnot reused, whereas the other data set was reused,but was not closed successfully.


Programmer responseRemove the DD statement for the OLDS which hasthe bad contents and specify the other OLDS as theprimary input log; then rerun the job.

DFS3277I END OF PRIMARY EXTENTDURING OLDS WRITE OPERATION

ExplanationA DUP mode or CLS mode for OLDS with WADS wasspecified. There was not enough room to write the logblocks from WADS, an accounting log record (X'06') inthe primary extent of the output log (DUP mode) or theinput log (CLS mode).


Programmer responseIf CLS mode was specified, change it to DUP mode andspecify an output log with enough space. If DUP modewas specified, specify more space for the output logand rerun the job.

DFS3278A DATA ERROR nn IN INPUT LOG DDddname

ExplanationWhile reading a batch log input, Batch Backoutdetected one of the following errors, where code=nn:Code

Meaning02

During backward processing of a DASD log, BatchBackout was unable to interpret the data in thefield lengths.

03During backward processing of a DASD log, anattempt was made to process beyond the lasttrack. The log is not properly closed.

05The log record sequence BCKSEQNR number(LGSEQNR), of the last log record read during theforward read does not match the log sequencenumber (BCKSEQNR) of the first record read duringthe backward read for an IMS batch log input dataset. The possible cause of this error is a JCL erroron the IMSLOGR DD statement.

System actionThe Database Backout utility, DFSBBO00, terminatesunsuccessfully with a return code of RC=68 (X'44').If the ABENDMSG control statement was specified,abend U507 is issued.

Programmer responseThe log input might not be properly closed. Verify thatthe log is properly closed and rerun the backout job. Ifthe log is properly closed, keep the log input and theabend U0507 dump. Then, contact the IMS systemsprogrammer.

DFS3279I INCOMPLETE DEDB LOG CHAINMAY REMAIN IN PREVIOUS LOGDATA SET

ExplanationThe Log Recovery utility terminated successfully.Because no "sync point complete" log record (X'5937'or X'37') was found, an incomplete DEDB might remainin the log record chain in the previous log data set(OLDS or SLDS).

System actionThe Log Recovery utility terminates with return codeX'04'


Programmer responseIf the previous log is OLDS, rerun the job in CLS modeand include the previous OLDS as a concatenated dataset with the current OLDS. Also, specify PSBLIST=YESand DBRC=NO as EXEC parameters.

If the previous OLDS was already archived into anSLDS, run a Log Recovery utility job in DUP mode andspecify the SLDS as an input data set. Also, specifyPSBLIST=YES and DBRC=YES as EXEC parameters.

Note: If the closed OLDS is the only OLDS used sincecold start, ignore this message.

DFS3280W REORG# updated for partitionyyyyyyy

ExplanationIMS has detected a lower reorganization number inthe data set when compared to the reorganizationnumber in the RECON data set for the HALDB partitionidentified byyyyyyyy. The data set has been updated.

System actionIMS has updated the partition data set with thereorganization number from the RECON data set.

System programmer responseYou must rebuild the indirect list data set (ILDS) if theindirect list entries (ILEs) were created with the samereorganization number as the data set.

ModuleDFSDDUI0

DFS3281A CONTROL STATEMENT NOT VALIDFOR INPUT LOG: statement -logtype

ExplanationThe SYSIN data set contains a control statement thatis not compatible with the type of input log. Thismessage identifies the control statement and the inputlog type.

System actionThe job is terminated before backout begins.

Programmer responseRemove the identified control statement and resubmitthe job. See a description of the control statements forthe Batch Backout utility.


DFS3282W REORG# needs update forpartition yyyyyyy

ExplanationIMS has detected a lower reorganization number in thedata set as compared to the reorganization numberin the RECON for the named HALDB partition. Thepartition data set cannot be updated with the correctreorganization number because the dataset is openonly for input. IMS issues this message when thepartition data set is opened.

System actionIMS updates the reorganization number in the internalcontrol blocks, but the data set still contains a lowerreorganization number until the data set is opened forupdate.

System programmer responseChange the partition access to allow the reorganizationnumber to be updated on the dataset. The ILDS mustbe rebuilt if the ILE's were created with the samereorganization number as the data set.

ModuleDFSDDUI0

DFS3283A BACKOUT INCOMPLETE FOR PSBpsbname DATABASES dbname1dbname2...

ExplanationWhen Batch Backout is run in multiple steps usingthe DATABASE control statement, this message is thenormal response for all but the last step. The dbnamesshown in the message are all the databases specifiedon the DATABASE control statements. If a COLDSTARTstatement was used with the DATABASE statements,the word ALL appears in place of the dbnames.

System actionBatch Backout backed out any updates to theidentified databases for the named PSB that werefound in the series of input log data sets. A conditioncode of 88 is returned.




Programmer responseContinue the backout by running Batch Backoutagainst the previous set of log data sets. Use the sameDATABASE control statements.

DFS3284A INCOMPATIBLE CONTROLSTATEMENTS: s1 - s2

ExplanationThe SYSIN data set contains two control statements,s1 and s2, which cannot be used together.

System actionThe job is terminated before backout begins.

Programmer responseRemove the inappropriate control statement andresubmit the job. For descriptions of all controlstatements see IMS Version 15 Database Utilities.

DFS3285E AN INTERNAL ERROR OCCURREDDURING BATCH BACKOUT.DIAG1=XX; DIAG2=YY.

ExplanationAn internal processing error occurred during batchbackout.

The following table shows the meanings of the DIAG1and DIAG2 fields.

Table 19. DFS3285E message text

DIAG1 DIAG2 Meaning

01 Hexadecimal returncode from OBTAINmacro for IMSLOGR orIMSLOGxx data set(s).

See "DFSMSdfpAdvancedServices" for thedescription ofthe return code.

System action:The Database Backout utility, DFSBBO00, terminatesunsuccessfully with a return code of RC=100 (X'64').If the ABENDMSG control statement was specified,abend 0507 is issued.

System programmer response:If the cause of the error can be determined from theDIAG1 and DIAG2 values above, correct the error andre-run the utility. If not, contact IBM Software Support.

Related referencez/OS: Reading DSCBs from the VTOC usingOBTAINBatch Backout utility (DFSBBO00) (DatabaseUtilities)


DFS3286W REORG# NOT FOUND FORPARTITION yyyyyyy

ExplanationThe reorganization number for a HALDB partitioncannot be determined during reload when new recordshave been moved into the partition. The reorganizationnumber from the primary data set and the RECONcannot be determined or are null.

When IMS is unable to determine the correctreorganization number during reload, it is possible thatthe reorganization number has been set incorrectly forthis partition. An incorrect reorganization number cancause failures during resolution of the indirect pointersfor segments involved in a logical relationship or thetarget of a secondary index or both. This failure cancause IMS to follow a bad pointer and cause a dataintegrity failure.

System actionThe reorganization number was set in the data setusing the reorganization number of the first recordloaded into the partition.

System programmer responseIf the database does not have any logical relationshipsor secondary index databases, then no action isrequired.

If the database has logical relationships or asecondary index target, then determine if thereorganization number was regressed. Follow thesesteps to determine if the number was regressed:

1. Determine the key of the first record in the partitionafter reload.

2. Determine the reorganization number for thepartition of the first record before reload.

3. Determine the reorganization number for thepartition of the first record after reload.

If the reorganization number after reload is less thanor equal to the reorganization number before reload,a data integrity failure might occur. To prevent a dataintegrity failure take the following steps:

1. Reverse the changes in the partition boundaries,restoring the partitions to their original partitions.

2. Enable the reorganization number verificationfunction. You can do this using the DBRCCHANGE.RECON REORGV command.







3. Set the reorganization number in the RECON, bymaking updates to the partition or by executing theHD Unload utility.

4. Redo the changes to the partition boundaries.

Attention: If you cannot enable reorganizationnumber verification, then IMS can prevent theregression of the reorganization number duringreload as long as the primary database dataset is not scratched and reallocated, or thepartition is not reinitialized to empty.

Module:DFSPSEL0

DFS3287E STORAGE NOT AVAILABLE FORBLOCK SERIALIZATION TABLE,RETURN CODE X'xx'

ExplanationAn error was encountered while attempting toGETMAIN storage for the Block Serialization Latchtable.


The return code from the IMODULE GETMAIN. Fora description of these codes, see the IMODULEreturn codes.

System action:IMS terminates abnormally with abend 0430.

System programmer response:If insufficient storage is available, increase the mainstorage available to IMS.


Module:DFSDVBI0

Related referenceIMODULE return codes (Messages and Codes)Related information“IMS problem determination” on page 11IMS messages and codes problemdetermination is accomplished by usingprocedures established by IBM.

DFS3288I INPUT LOG RECORD LENGTHERROR - SEQ NUMBER = nnnnnnnnINPUT LOG SEQUENCE NUMBERERROR - SEQ NUMBER = nnnnnnnnINPUT LOG CONTAINS RECORDGAPS - SEQ NUMBER = nnnnnnnn

ExplanationDuring the Log Recovery Utility (DFSULTR0) runningPSB mode, an error was detected on the input log(IEFRDER).

System actionThe first version of the message is issued when a logrecord is read that has a record length that is less thanthe minimum record length. The SEQ NUMBER valueis the log record sequence number of the last validrecord read. The utility processing is terminated.

The second version of the message is issued when alog record is read that has a sequence number thatis less than the prior record sequence number. TheSEQ NUMBER value is the log record sequence numberof the last valid record read. The utility processing isterminated.

The third version of the message is issued when alog record is read that has a sequence number that ismore than 1 greater than the prior record's sequencenumber. This indicates a gap in the log records. TheSEQ NUMBER value is the log record sequence numberof the last valid record read. The utility will continueto process, but the output report might be incompletedue to the gap in the input data.

Operator responseThe message is issued for information purposes. Ifconcatenated log input is used, verify that the logs arein the sequence that they were created. If OLDS andSLDS are mixed, there must not be any overlap in logrecord content. If the input is RLDS or any other logthat does not include all records written to the OLDS,then the third version of the message is likely to bereceived. In this case the OLDS or SLDS should beused instead.

DFS3289A LOG RECORD SEQUENCE ERRORIN INPUT LOG-nnnnnnnnmmmmmmmm dddddddd

ExplanationWhile reading the input log data set associatedwith DDNAME dddddddd, Batch Backout found a logrecord that was out of sequence. The log record withsequence number nnnnnnnn was expected. The logrecord with sequence number mmmmmmmm wasfound in its place. The error can be caused by one ofthe following:

• The log data sets are not in the correct order in theJCL.

• The log data set has invalid data.



• A user-written program modified the log.

System actionBatch Backout terminates with condition code 108before any backout is attempted.

Programmer responseMake sure the order of the log data sets in the JCL iscorrect. If the order is right, correct the log data setidentified in the message by using DUP mode of theLog Recovery utility; then rerun the job.

If you are confident that the input log contains all therecords needed by Batch Backout, in the correct order,you can use the BYPASS SEQVER statement to skip thesequence check.

DFS3290I NO PENDING BACKOUT FITSCRITERIA - RSN= r1[,r2[,r3[,r4[,r5[,r6]]]]]

ExplanationNo unit of recovery (UOR) in the RECON Backoutrecord fits the requirements for this run of the BatchBackout utility. The reason codes appended to themessage identify the reasons for not performing thebackouts. The reason codes and their meanings are:Code (Dec)

Meaning0

No backout is pending for this subsystem.1

UOR has already been backed out.2

UOR is not for the PSB named in the Batch BackoutEXEC statement.

3UOR is in doubt. Cold start has not been done, andthe COLDSTART statement was not used.

4UOR is not in flight, and the ACTIVE statement wasused.

5UOR is in flight. Restart is not implied by anycontrol statement. Restart is not complete.

6UOR is in flight or in doubt. The most current logdata is not included in input.

System actionThe Batch Backout utility terminates withoutperforming any backout.

Programmer responseIf there is an outstanding backout that should havebeen performed, determine the problem from thereason codes listed in the Explanation; correct the JCL;and rerun Batch Backout.

DFS3291I UORS IDENTIFIED TO DBRC - IN-FLIGHTS=nnn, IN-DOUBTS=mmm

ExplanationBatch Backout has given DBRC a list of UORS thatwere in flight or in doubt at the end of the input log.There were nnn in-flights and mmm in-doubts. If acold start is done, this information is used to protectthe registered databases until the needed backoutsare performed. If there are any in-doubts, cold startshould not be done because they cannot be properlyresolved by Batch Backout.

System actionA RECON Backout record has been created or modifiedfrom the information supplied to DBRC by BatchBackout. The information remains in the RECONregardless of the outcome of the Batch Backout run.

DFS3292I RESTART IN PROGRESSCONFLICTS WITH BBO CONTROLSTATEMENT - ssssssss

ExplanationThe control statement ssssssss tells Batch Backout toperform backouts; but a restart is in progress that willperform the backouts.

System actionBatch Backout terminates without attempting anybackout.

Programmer responseIf the restart failed, close its output log beforererunning Batch Backout.

DFS3293W PERFORMED BACKOUT NOTNEEDED

ExplanationBatch Backout successfully completed. Batch Backouttold DBRC which backouts were completed. At leastone of the databases backed out, for one of theUORS did not need to be backed out, according tothe information in the RECON Backout record. If theBYPASS LOGVER control statement was not used, this


means that the RECON Backout record was modifiedby a different process while Batch Backout wasrunning.

System actionThe required changes have been successfully backedout of the databases associated with the PSB for whichthe Batch Backout utility was executed.

DFS3294A LOG VERIFICATION FAILUREnn- rrrrrrrrrr[DSN= DSNExamined[,VOL=VOLSERExamined]]EXPECTED= [DSNExpected |VOLSERExpected]

ExplanationUsing information from DBRC, the Batch Backoututility determined that the log data sets specifiedin the JCL are not appropriate for performing therequested backout. A general reason rrrrrrrrrr and asubcode nn are shown in the message. Each subcodeis associated with a specific test in the Batch Backoutmodule. Subcodes 20 - 40 identify specific errors.

The variables in the message and their meanings are:nn

A subcode which identifies a specific test in theBatch Backout module.

rrrrrrrrrrA general description of the problem.

The possible values are:

• DATA SET NOT FOUND IN RECON• CONTINUITY• LATER DATA SET OR VOLUME NEEDED• DATA SET NOT CLOSED.• LOG INCLUDES RESTART

DSNExaminedThe DSN, from 1 to 44 characters, of theDD statement examined when the problem wasdetected. The problem exists in this DD statementor the preceding one.

VOLSERExaminedThe VOLSER examined when the problem wasdetected. The problem exists in this VOLSER or thepreceding one.

DSNExpectedThe DSN, from 1 to 44 characters, of the DDstatement that was expected when the problemwas detected.

VOLSERExpectedThe VOLSER that was expected when the problemwas detected.

The following describes the most likely problem foreach subcode:

Note: For subcodes less than 20, the problem can beany one of the following:

• The log data set was not identified to DBRC (It wascreated by means other than IMS.)

• The log data set was removed from the RECON dataset.

• The DSNAME or VOLSER is invalid or out of order inthe JCL.

• A log data set or VOLSER was skipped.

Code (hex)Meaning

01The first log data set was created by some meansother than IMS.

02DSNExamined was encountered whereDSNExpected was expected.

03VOLSERExamined was found whereVOLSERExpected was expected.

10A complete data set was specified, but the nextVOLSER of the previous log data set should havebeen specified instead.

11The last VOLSERs of the previous log data set wereskipped.

12Invalid VOLSERs were either specified or repeated.

13VOLSERExamined was found whereVOLSERExpected was expected.

14The log data set that should precede the log dataset specified by dd statement DSNExamined ismissing from the input.

20The input log is from batch. VOLSERs are missingat the end.

21The backout is related to a restart. VOLSERs aremissing at the end.

22The input log is from a batch job, and the DBRCinformation shows a more recent log for that jobname. This code can also mean that logs werespecified from more than one execution of a batchjob.


23A control statement indicates that the backout isrelated to a restart. The last log data set before therestart is not included in the input.

30The log data set specified in DD statementDSNExamined has not been closed.

40One of the input log data sets other than thefirst data set includes a successful restart. BatchBackout cannot handle log data from both sides ofa restart in one run when it does log verification.

System actionBatch Backout terminates without performing anybackout.

Programmer responseCorrect the JCL and rerun Batch Backout.

DFS3295A READ BACKWARD NOT ALLOWEDFOR BACK OUT FROM IMSCHECKPOINT

ExplanationBatch Backout is executing with the READBACKoption. At an IMS checkpoint, Batch Backoutencountered a UOR and attempted to back it out.However, Batch Backout did not find the original logrecords for that UOR.

Batch Backout cannot use the read-backwardtechnique to perform a backout from the informationin the system checkpoint. Batch Backout terminateswithout performing a backout.

Programmer responseDo either of the following:

• Remove the READBACK statement from the SYSINdata set. Batch Backout will perform the backout bybuffering the changes in virtual storage.

• In the input to Batch Backout, include the log dataset that was active when the application needingbackout was run.

DFS3296A DBRC=C REQUIRES BYPASSLOGVER

ExplanationYou specified DBRC=C in an attempt to back out asuccessfully completed job that used DBRC. Since thejob completed successfully, a subsequent job mighthave modified the databases. The logs you provided

might not be the last logs used by this subsystem andlog verification will fail. The Batch Backout utility andDBRC cannot verify that you provided the correct logsand cannot protect your database from being damagedif it was modified after the job completed.

System actionBatch Backout terminates without performing anybackouts.

Programmer responseYou must ensure that no other program has modifiedthe databases to be backed out before running theBatch Backout utility using DBRC=C. If you are certainthat no other job has modified the database and youstill want to back out this completed job, you mustinclude the BYPASS LOGVER utility control statementin your SYSIN data set. Batch Backout will back outthe completed job if all other necessary conditions aremet.

ModuleDFSBACK0

DFS3298E CICS IPIC ERROR DURING ISCTCP/IP SESSION INITIATIONRC=ipicrc TEXT=cics_rs_codeUSER=isc_user

ExplanationDuring the initiation of an ISC TCP/IP session withIBM CICS Transaction Server for z/OS, IMS receiveda capability exchange response (type X'02') thatindicated an IP interconnectivity (IPIC) exceptionerror. The session initiation failed.

The TEXT field contains text that briefly describes themeaning of the error message.

In the message text:ipicrc

The 2-byte response code that was returned byCICS.

The possible response codes are described in thefollowing list.02

An exception03

A disaster event04

The message is not valid for CICS05

A kernel error


06CICS purged the error

cics_rs_codeText of up to 12 characters that briefly describesthe reason code that CICS returned to IMS for theerror. For a description of the possible values ofcics_rs_code, see the following table.

isc_userThe user name that is associated with the sessioninitiation request.

The following table shows the reason codes that canbe displayed in the TEXT field.

Table 20. Description of CICS reason codes that can be displayedby DFS3298E

Servicecode

HTTPstatuscode

IPICreason code

Meaning

APPLID X'06' In the capability exchangemessage was received by CICS,the server_applid or its high-levelqualifier does not match APPLIDand high-level qualifier of the CICSsubsystem.

This error is most likely caused bya value on the CICSAPPL keywordof an ISC statement that does notmatch the APPLID of the remoteCICS subsystem.

Correct the value of the CICSAPPLkeyword on the ISC statementin the IMS Connect configurationmember in the IMS.PROCLIB dataset.

CICS reason text:ISCE_INVALID_APPLID

AUTOINSTALL

X'01' The CICS autoinstall function couldnot create the required IPCONNresource in the CICS subsystem.

The autoinstall function can failif the name of the new IPCONNresource is the same as the nameof an existing IPCONN resource.

Because the name of the IPCONNresource that is created by theautoinstall function is generatedfrom the user ID that is specifiedon an IMS session initiationrequest, such as the /OPNDSTNODE command, try initiating thesession with a different user ID.

CICS reason text:AUTOINSTALL_FAILED

CAPEXRACE

X'15' Capability exchange race. Thesession between IMS and CICSwas initiated by IMS and CICSat the same time, which createda race condition between thetwo capability exchange requests.Try issuing the IMS /OPNDSTcommand again.

Table 20. Description of CICS reason codes that can be displayedby DFS3298E (continued)

Servicecode

HTTPstatuscode

IPICreason code

Meaning

Try initiating the session again fromeither IMS or CICS.

CICS reason text: CAPEX_RACE

DFHxxxxx API conversation error.

DFHxxxxx is the CICS API errormessage that was returned to IMSConnect, where xxxxx is a number,and DFH is the CICS messageprefix.

This error is probably an internalerror. Contact IBM SoftwareSupport.

HTTPRQST X'400' Defined by the HTTP protocolor the TCP/IP server, indicatesthat the request could not beunderstood by the server becausethe syntax was malformed.

The session initiation request isprobably invalid and could notbe understood by the receivingsubsystem.

Check that the ISC TCP/IP sessioninitiation request is configuredproperly in the subsystem that isinitiating the session.

If the problem persists, contactIBM Software Support.

HTTPERR X'0B' A capability exchange responsethat is related to a callbackconnection contained an HTTPstatus code that indicates an error.

CICS reason text:ISCER_HTTP_ERROR

IPCONNNO

X'13' No IPCONN resource.

An attempt to acquire orrelease a connection for aCICS TCPIPSERVICE resource wasmade, but the TCPIPSERVICEresource does not have anassociated IPCONN resource.

The error is probably caused byan incorrect TCPIPSERVICE orIPCONN resource definition in theCICS subsystem. Correct any errorsin the resource definitions and tryto initiation the session again.

CICS reason text: NO_IPCONN



Servicecode

HTTPstatuscode

IPICreason code

Meaning

IPCONNNOTFND

X'04' IPCONN not found.

An attempt to acquire or release aconnection with a CICS subsystemwas made, but the requiredIPCONN resource no longer existsor cannot be found.

CICS reason text:IPCONN_NOT_FOUND

IPCONNONEWAY

X'14' The ISC TCP/IP session requires atwo-way connection, but the CICSIPCONN resource is defined to usea one-way connection.

Correct the CICS IPCONN resourcedefinition.

CICS reason text:ISCER_ONE_WAY_IPCONN

IPCONNSTATE

X'02' Invalid IPCONN state.

An ISCO ACQUIRE_CONNECTIONwas issued, but failed because theCICS IPCONN resource is not in thecorrect state.

The state of the IPCONNresource must be INSERVICE andRELEASED.

Try to initiate the session again. Ifthe problem persists, contact theCICS system administrator.

CICS reason text:INVALID_IPCONN_STATE

OPENERR X'0D' Open session error.

IMS attempted to initiate an ISCTCP/IP session with CICS throughIMS Connect, but the capabilityexchange between the IMS andCICS subsystems failed.

The following scenarios areexamples of how this error mightoccur:

• The IMS Connect port isstopped.

• The value that is specified on thePORT keyword of the IPCONNresource definition in the CICSDFHCSD data set does not matchthe value that is specified onthe ID subparameter of theCICSPORT keyword in the TCPIPstatement in the IMS ConnectHWSCFGxx PROCLIB member.

This error is probably caused by aconfiguration or definition problem.

Verify that all IMS, IMS Connect,and CICS PROCLIB members andresources are defined correctly.


Servicecode

HTTPstatuscode

IPICreason code

Meaning

Correct any errors in the definitionstatements.

CICS reason text:SESSION_OPEN_FAILED

PARTNERSTATE

X'03' Invalid partner state.

CICS received a capabilityexchange request for an IPCONNresource that is in an invalid state.

The state of the IPCONN resourcemust be INSERVICE and notalready acquired.


CICS reason text:INVALID_PARTNER_STATE

RECOVERR X'08' Capability exchange recovery error.

CICS received a capabilityexchange request thatcontains an unsupportedisce_preferred_recovery valueand no matchingisce_supported_protocols flags areset to fallback to.

This error is probably an internalerror. Contact IBM SoftwareSupport.

CICS reason text:ISCE_BAD_RECOV

RESPBAD X'09' A CICS IPIC response is bad.

The callback capability exchangeresponse that was received byCICS contains a bad response andreason code.

This error can occur during acapability exchange if the portdefined on the PORT attributein the CICS IPCONN resourcedefinition is not also defined to IMSConnect on the ID subparameterof the CICSPORT keyword inthe TCPIP statement in the IMSConnect PROCLIB configurationmember.

Verify that all IMS, IMS Connect,and CICS PROCLIB members andresources are defined correctly.

CICS reason text:ISCER_BAD_RESPONSE



Servicecode

HTTPstatuscode

IPICreason code

Meaning

RESPERR X'0A' Capability exchange responseerror.

The callback capability exchangeresponse was determined to beinvalid.

This error is an internal error ineither IMS, IMS Connect, or CICS.Contact IBM Software Support.

CICS reason text: ISCER_ERROR

RESPTIMEOUT

X'0C' Capability exchange responsetimed out.

A response to a capabilityexchange request was not receivedwithin the timeout period specified.

Increase the CICS IPIC requesttimeout value (RTIMOUT) in thesystem profile DFHCICSC.

The RTIMOUT value is inmmss, where mm is minutes,ss is seconds. For example,to change the timeoutvalue to 1 minute, specify:ALTER PROFILE(DFHCICSx)GROUP(IMSISCIP)RTIMOUT(0100).

Use CICS transaction CEDA todisplay or update the timeout value

CICS reason text:ISCER_TIMED_OUT

RQSTERR X'05' Capability exchange request error.

The capability exchange requestwas determined to be invalid andwas rejected by the partner CICSsubsystem. IMS or IMS Connectbuilt an incorrect capabilityexchange request message toinitiate a session.

Contact IBM Software Support.

CICS reason text:

RQSTTIMEOUT

X'07' The CICS IPIC request timed out.

The TCPIPSERVICE transaction(CISS by default) was attachedto initialize a connection for anIPCONN resource but did notreceive a capability exchangerequest within the timeout periodthat is defined in its transactionprofile.

Increase the CICS IPIC requesttimeout value (RTIMOUT) in thesystem profile DFHCICSC.

The RTIMOUT value is inmmss, where mm is minutes,ss is seconds. For example,to change the timeout


Servicecode

HTTPstatuscode

IPICreason code

Meaning

value to 1 minute, specify:ALTER PROFILE(DFHCICSC)GROUP(IMSISCIP)RTIMOUT(0100).

Use CICS transaction CEDA todisplay or update the timeout value

CICS reason text:ISCE_TIMED_OUT

SECURITY X'16' Security error. The securitycredentials of the caller are notacceptable to the partner system.

CICS reason text:ISCER_SECURITY_VIOLATION

SHUTDOWN

X'0E' CICS is shutting down.

A call was made to DFHISCO toacquire or initialize an IPCONNresource, but CICS was shut downbefore the call was completed.

Verify that CICS is active. If CICS isnot active, start it.

CICS reason text: SHUTDOWN

SOCKETERR

X'18' Client socket error. The clientconnection is closed.

CICS reason text:ISCER_CLIENT_CONNECTION_CLOSED

SOCKETSECERR

X'19' Secondary socket error. An erroroccurred when an attempt wasmade to obtain a secondary socket.

CICS reason text:ISCER_SEC_SOCK_ERROR

SRVCCLOSED

X'0F' TCP/IP services are unavailable.

An attempt to acquire a connectionfailed because no TCP/IP support isavailable.

Start the TCP/IP service and tryinitiating the ISC TCP/IP sessionagain.

CICS reason text: TCPIP_CLOSED



Servicecode

HTTPstatuscode

IPICreason code

Meaning

SRVCMISMATCH

X'10' TCPIPSERVICE mismatch.

A capability exchange requestwas received for an IPCONNresource that is defined to use adifferent TCPIPSERVICE from theTCPIPSERVICE that was used forthe capability exchange.

This error can occur if the portsdefined on the CICS TCPIPSERVICEand IPCONN resource definitionsdo not match.

Verify that all IMS, IMS Connect,and CICS PROCLIB members andresources are defined correctly.Correct any errors.

CICS reason text:TCPIPSERVICE_MISMATCH

SRVCNOTFOUND

X'11' The TCPIPSERVICE resource thatis referenced by the IPCONNresource was not found in the CICSsubsystem.

CICS could not acquire or releasethe connection because theTCPIPSERVICE resource that isreferenced in the IPCONN resourcedefinition is either not installed orwas deleted.

Try to initiate the session again.If the problem persists, contactthe CICS system administrator.The TCPIPSERVICE resource mightneed to be reinstalled and opened.

CICS reason text:TCPIPSERVICE_NOT_FOUND

SRVCNOTOPEN

X'12' The TCPIPSERVICE resource in theCICS subsystem is not open.

The CICS subsystem attemptedto acquire a connection foran IPCONN resource, but theTCPIPSERVICE named in theIPCONN resource definition is notopen.


CICS reason text:TCPIPSERVICE_NOT_OPEN

SRVCUNAVAIL

X'503' Defined by the HTTP protocolor the z/OS TCP/IP server,indicates that the TCP/IP serveris temporarily unavailable eitherbecause it is overloaded or downfor maintenance.

Verify that the TCP/IP server isactive. If the TCP/IP server is notactive, start it.


Servicecode

HTTPstatuscode

IPICreason code

Meaning

SRVRERR X'500' Defined by the HTTP protocol orthe z/OS TCP/IP server, indicatesthat the TCP/IP server encounteredan unexpected condition thatprevented it from fulfilling therequest.

Hypertext Transfer Protocol --HTTP/1.1

UNKNOWN X'63' Unknown error. This error isprobably an internal error. ContactIBM Software Support.

System action:The attempt to initiate an ISC TCP/IP session withCICS fails. IMS continues processing.

System programmer responseReview the explanations of the CICS response andreason codes that were included in the DFS3298Emessage. For more information about the codes andthe possible actions to take to correct the error,consult with your CICS support personnel.

Confirm that the following elements are configuredcorrectly:

• The ISC terminal in IMS, by either an ETO logondescriptor or stage-1 system definition macros suchas TYPE, TERMINAL, and SUBPOOL

• The ISC link in IMS Connect, by the ISC andRMTIMSCON statements

• The TCPIPSERVICE and IPCONN statements in CICS

Module:DFSIPIC0

Related tasksISC support for TCP/IP (Communications andConnections)Related referenceQUERY IMSCON TYPE(PORT) command(Commands)CICS: ISMF - ISC IP Message Formats

DFS3299I FPBP64M INCREASED FROMxxxxxxx TO yyyyyyyy DUETO SYSTEM REQUIREMENTSRSN=rrrrrrrr


http://www.ibm.com/support/knowledgecenter/SSEPH2_15.1.0/com.ibm.ims15.doc.ccg/ims_isc_tcpip.htm#ims_isc_tcpip


http://www.ibm.com/support/knowledgecenter/SSEPH2_15.1.0/com.ibm.ims15.doc.cr/imscmds/ims_queryimscon_port.htm#queryimscon_port


http://www-01.ibm.com/support/knowledgecenter/SSGMCP_5.2.0/com.ibm.cics.ts.doc/dfhs4/DFHISMFK.html

ExplanationIMS detected that the value calculated by systemfor FPBP64M was below the minimum range andincreased FPBP64M.

In the message text:xxxxxxx

The initial value of FPBP64Myyyyyyyy

The new value of FPBP64Mrrrrrrrr

For service use

System actionA new value for FPBP64M was calculated by IMS andapplied to FPBP64M.


Module:DBFBPN61

DFS3300I aaaa IGNORED, FPBP64PARAMETER USED

ExplanationYou specified both the Fast Path-64 bit buffer manager(FPBP64=Y), and the current buffer Fast Path manager(DBBF, DBFX, BSIZ).

In the message text:aaaa

The parameter being ignored: DBBF, DBFX, andBSIZ.

System action:The Fast Path 64–bit buffer manager is used andDBBF, DBFX, and BSIZ are ignored.

Operator responseIf you intended to use the Fast Path 64–bit buffermanager, no action is necessary. If the current buffermanager was the intended buffer manager, removeFPBP64=Y from the DFSDFxxx member and cold startIMS.

Module:DBFINI20


Chapter 70. DFS messages, DFS3301W - DFS3350E


DFS3301W AN INVALID REQUEST WAS MADETO DELETE A SUBPOOL

ExplanationAn internal request was made to delete a subpoolor extent which had not been quiesced and logicallydeleted. This problem is an internal system error.

System actionIMS ignored the delete request.

Programmer responseObtain a memory dump of the IMS subsystem,and contact IBM Software Support for assistance indetermining the specific problem.

DFS3303I PSB psbname PCB pcbnameDBD dbdnamexxxx JOBNAMEjobnameRGN nnn

ExplanationThis message precedes pseudoabend 3303 when anapplication program scheduled with PSB psbnametries to make an incompatible DL/I call to databasePCB psbname. During DL/I scheduling of the PSB,database dbdname had condition xxxx. Depending onthe condition, DL/I calls to this database are partiallyor totally restricted.

This message precedes only those 3303 abendscaused by DL/I attempts to access data in adatabase that was unavailable when the program wasscheduled, and the program had not issued the DL/IINIT STATUS call.

xxxx is one of the following:CF FAIL

A coupling facility failure occurred. The databasecannot be accessed until recovery is done and datasharing resumes.

INVDBVERAn invalid version number for a full-functiondatabase was specified on a PCB or an INITVERSION call that was issued by the applicationprogram. The specified database version numbermust be equal to or less than version numberof the current database that is active in theIMS system. Also, a database version cannot

be specified on a PCB if database versioning isnot enabled. Database versioning is enabled byspecifying DBVERSION=Y in the database sectionof the DFSDFxxx PROCLIB member.

INVDBCHGThe current database structure of a full-functiondatabase contains a change that is not supportedby database versioning. Prior versions of thedatabase are incompatible with the current versionand can not be accessed. The changes that aresupported by database versioning are:

• Increasing the size of a segment• Adding new fields without changes made to

existing fields

LOCKEDThe identified database was security locked usingthe /LOCK command.

NOACCESSThe database ACCESS was set to "RO" and the PCBprocessing intent (PROCOPT) was greater than"GO". Since ACCESS "RO" only allows databaseread without integrity, any processing intentimplying integrity is not valid.

NOCATALGThe IMS catalog is not enabled. Databaseversioning requires the IMS catalog.

NO DBRCThe PCB pcbname refers to a HALDB, but the useof DBRC was suppressed for this batch job.

NODELETEDL/I DLET calls to this database were not allowedat scheduling because a restricted or unavailabledatabase was involved in a logical relationshipor a secondary index. Delete calls cannot beprocessed because they can require updating of alogically related or secondary index database thatis unavailable or is unavailable for update.

NOTAUTHDAt the time of DL/I scheduling, the database wasnot authorized, or could not be authorized byDBRC. Message DFS047A was issued. DL/I doesnot allow any calls to this database.

NOUPDATEEither the database ACCESS for the identifieddatabase was RD, or a /DBD command was issuedfor the database. When the database ACCESS is RD(either explicitly, or implicitly because of a /DBDcommand), DL/I calls such as ISRT, REPL, or DLET


are not allowed. This condition can also be causedby unavailable or restricted access to a logicallyrelated or secondary index database that mighthave to be updated on an ISRT, REPL, or DLET call.

NOSTORAGA storage error occurred while building the internalblocks that are required to satisfy a request for aversion of a full-function database other than thecurrent version.

NOVERFNDThe requested version of a full-function databasecannot be found in the IMS catalog.

PARTUNAVAn attempt was made to reference a partition inthe HALDB database indicated by dbdname, butthe partition was unavailable.

STOPPEDA /STOP or a /DBR command was issued againstthe identified database. DL/I does not allowdatabase access when the database is stopped.

SYSTEMThe IMS system made the database temporarilyunavailable. One possible reason is that an XRFtakeover occurred, and the database must bereverified.

System actionThe IMS online dependent region identified by OSjobname and region number is abnormally terminated.

If a BMP, the region is terminated with abend 3303,but for an MPP, the database is stopped, but the regionis not terminated.

The message being processed is placed on thesuspend queue unless the SERIAL=YES option wasspecified on the TRANSACT macro. In this case, thetransaction is stopped. When a message is placed onthe suspend queue for the first time, a counter for thetransaction is incremented by one.

Operator response(master terminal) Correct the database condition;then start the database.

To drain the suspend queue and reset USTOPPEDstatus for those transactions processed by programsauthorized to access the started database, issue the /START DATABASE or UPDATE DB START(ACCESS)command.

To drain the suspend queue for the started transactionand reset the USTOPPED status, issue the /STARTTRAN or UPDATE TRAN START(SUSPEND) command.

To drain the suspend queue for all transactions, issuethe /DEQ SUSPEND command.

For more information about how the suspend queueworks, see IMS Version 15 System Administration.

Related referenceINIT call (Application Programming APIs)Related informationIMS abend 3303

DFS3304I IRLM LOCK REQUEST REJECTED.PSB=psb_name DBD=dbd_nameJOBNAME=job_name RGN=nnnSUBSYSTEM=subsystem

ExplanationThis informational message precedes pseudoabend3303 when an application program attempts to obtaina retained lock through IRLM. The variables in themessage text are:psb_name

The name of the PSB issuing the failed calldbd_name

The name of the database with the retained lockjob_name

The name of the z/OS job receiving the 3303abend

nnnThe number (decimal) of the PST receiving the3303 abend

subsystemThe name of the IMS subsystem that holds thelock

System actionSee the description of abend 3303 for system action.

Module:DFSLRH00


DFS3305E DEFINITION ERROR IN PROCLIBMEMBER nameSTMNT (nnn),'xxxxxxxxxxxxxxxxxxx'(yyyyyyyyyy)

ExplanationIf one or more errors were found while processingexternal subsystem definitions, this message is issued.For each definition error, a message is issued thatindicates which statement was in error and the textin the error. One STMNT error message is issued for


http://www.ibm.com/support/knowledgecenter/SSEPH2_15.1.0/com.ibm.ims15.doc.apr/ims_hinitcall.htm#ims_hinitcall



each error in the PROCLIB member. Multiple errors in asingle statement produce multiple messages.


Indicates the name of the PROCLIB member thatwas being processed.

nnnThe statement number within the member.

xxxxxxxxxxxxxxxxxxxThe text in error.

yyyyyyyyyyThe reason codes, which can be one of thefollowing values:OMITTED

A required parameter was omitted from thedefinition. The definition was invalid.

IGNOREDA parameter that is not applicable wasspecified in the definition. The parameter isignored and processing continues.

INVALIDThe error text represents invalid data in thestatement. If the character string KEYWORDproceeds the error text, then the value for theparameter is invalid. Otherwise, the error textrepresents data that could not be interpretedas part of the definition. The definition wasinvalid.

DUPLICATEA specific value for a parameter was specifiedfor more than one definition. The definition wasconsidered invalid and is ignored.

System actionIMS initialization terminates with a 0071 abend.

Programmer responseCorrect the PROCLIB member definition, and try IMSinitialization again.

Module:DFSCSL10


DFS3306A CTL REGION WAITING FOR csltype

ExplanationThis write to operator (WTO) message indicates thatone of the following problems was encountered:

• IMS when SCI, OM, or RM is unavailable at firstregistration.

• IMS online processing when there are no RM, OM, orSCI systems ready in the IMSplex (for example, allRMs, OMs, or SCIs have terminated or quiesced).

In the message text:csltype

The CSL type; either SCI, OM, or RM.

System actionIMS continues processing. However, functions thatrequire the CSL address space that is not activewill not be available. The following list shows someexamples.

• Type-2 commands are not be available until OM isrestarted.

• Access to the IMS Repository is not available untilRM is restarted.

• No CSL services are available until SCI is restarted.

Programmer responseStart the CSL that was not available. If you did notwant to start the CSL during IMS initialization, youmust cancel IMS.

Module:DFSCSL20, DFSCSL30, DFSCSL40, DFSSNTF0

DFS3307E OM CMD REG ERROR,VERB =vvvvvvvvvvvvvvvKEYWORD=kkkkkkkkkkkkkkkCC=cccccccc

ExplanationThis write-to-operator (WTO) message is issued by theIMS control region when an Operations Manager (OM)command registration failed. One DFS3307E messageis issued for each command and keyword combinationthat failed.

In the message text:vvvvvvvvvvvvvvv

The command that was registered with OMkkkkkkkkkkkkkkk

The keyword that was registered with OMcccccccc

The completion code for the command andkeyword registration. The cccccccc values aredefined in the CSLORR macro.

Chapter 70. DFS messages, DFS3301W - DFS3350E 927


System actionIMS attempts to register the rest of the commandsin the list. A DFS3307E message is printed for eachone that fails. After all attempts are completed,a DFS3308E message is printed and then IMSterminates abnormally.

Programmer responseIf the condition is temporary, try the failed processagain.

Module:DFSCSL30

Related informationDFS3308Ecsltype REQUEST ERROR, macronameRC=xxnnnnnn RSN=ssssssss

DFS3308E csltype REQUEST ERROR,macroname RC=xxnnnnnnRSN=ssssssss

ExplanationThis message is issued when an IMS process receivesan unexpected return code, reason code, or both froma CSL service request.

In the message text:csltype

The CSL type is CQS, OM, RM, or SCI.macroname

The name of the failing service macro.xx

Indicates which IMSplex components the error isassociated with:00

IMS Subsystems (DB/DC, DBCTL, DCCTL)01

SCI (Structured Call Interface)02

OM (Operations Manager)03

RM (Resource Manager)nnnnnnn

The return code from the service.ssssssss

The reason code from the service identified bymacroname . For information about the servicemacro reason and return codes, see IMS Version15 System Programming APIs.

Important: When the CSLTYPE shows other thanan SCI, but the return code (xx) is X'01', check

the CSLSRR macro to find out what is the reasonmeans. Many OM and RM request can result in aSCI return code and reason code.

System actionIf this error occurs during IMS initialization, thesystem might abend with 3308. Otherwise, the currentprocess is rejected and online processing continues.An abend can also occur if a new OM address spacejoins the IMSplex, IMS registers to it, and one of thecommand registration calls fails.

Operator responseIf the condition is temporary, try the failed processagain.

Module:DFSCSL20, DFSCSL30, DFSCSL40, DFSOLC30,DFSRMCL0, DFSRMD00, DFSRMFD0, DFSRMIU0,DFSRMSR0, DFSSLGF0, DFSSLON0

DFS3311I DFS3311I USER EXIT, XXXXXXXX,WAS NOT FOUND

ExplanationThe Data Capture exit routine XXXXXXXX was specifiedin DBDGEN, but a load module with this name was notfound.

System actionThe job is terminated with abend 3314.

Programmer responseDetermine why the load module was not found, correctthe error, and rerun the job.



DFS3312A DBRC PROCESSING FAILED -REASON = nn.

ExplanationA DBRC request failed for the one of the followingreasons:Code

Meaning



04DBRC sign-on request was not successful.

08BLDL failed for DSPCRTR0, an IMS/DBRC module.

12Database recovery control initialization first pass(INIT-0) was not successful.

16Database recovery control initialization first pass(INIT-0) was not successful.

20DBRC sign-off request was not successful.

System actionThis message is followed by abend 3312.

Programmer responseSee the information about abend 3312.



DFS3313I xxxxxxxx USER EXIT HASTERMINATED

ExplanationExit xxxxxxxx abnormally terminated during theprocessing of changed data due to the applicationprogram updating a segment with an exit defined onthe DBD statement.

System actionThe application program terminated.

Operator responseCorrect the situation that caused the exit to terminate.

Problem determination:2, 3, 8 and a listing of the exit routine


DFS3314W RETURN CODE xxx, REASON CODEyyy FROM EXIT zzzzzzzz INREGION n

ExplanationExit zzzzzzzz in region n returned an xxx return codeand a yyy reason code to IMS, so exception processingis done based upon the return code.

There is a limit of six DFS3314W messages thatcan be issued per Data Capture exit. This limit canbe removed by specifying the ALL3314W controlstatement in the DFSVSMxx member of the IMSPROCLIB data set, for online, or the DFSVSAMP DDdata set, for batch.

Programmer responseCorrect the situation that caused the exit to return thereturn code.


Related referenceRemoving the limit for the numberof DFS3314W messages issued (SystemDefinition)Related information“IMS problem determination” on page 11IMS messages and codes problemdetermination is accomplished by usingprocedures established by IBM.

DFS3315 ACCESS INVALID FOR GLOBALCOMMAND

ExplanationThe keyword ACCESS was invalid for globalcommands.



DFS3315W xxxxxxxx USER EXIT HASTERMINATED

ExplanationExit xxxxxxxx terminated during the processing ofchanged data due to the application program updatinga segment with an exit defined on the DBD statement.



http://www.ibm.com/support/knowledgecenter/SSEPH2_15.1.0/com.ibm.ims15.doc.sdg/ims_dfsvsmxx_proclib_remove_limit.htm#ims_dfsvsmxx_proclib_remove_limit



System actionThe application program terminated.

Programmer responseCorrect the situation that caused the exit to terminate.



DFS3316 DATABASE|AREA ALL INVALIDFOR GLOBAL COMMANDS

ExplanationThe global commands do not support DATABASE orAREA ALL.



DFS3317I ACCESS INVALID FOR FAST PATHMSDB dbname

ExplanationThe database access cannot be changed for the FastPath main storage databases (MSDB).

System actionThe named databases are removed from thecommand, and the remaining databases, if any, areprocessed.


DFS3318I FAST PATH MSDB dbname NOTSUPPORTED BY GBL COMMANDS

ExplanationThe Fast Path main storage database (MSDB) is notsupported by global commands.

System actionThe named database is removed from the command,and the remaining databases, if any, are processed.


DFS3319 IRLM NOT ACTIVE.

ExplanationIRLM must be active in the system when globalcommands or /DEQ SUSPEND are entered.


Operator responseEnsure that IRLM is active before entering globalcommands or /DEQ SUSPEND.

DFS3320I DBRC INDICATES DATA BASE|AREA xxxxxxxx NEEDS BACKOUT/RECOVERY

ExplanationThe named database or area must be recovered beforethe command can be processed against the databaseor area.

System actionThe named database or area is removed from thecommand, and the remaining database or areas, if any,are processed.


DFS3321I DBRC INDICATES DATA BASE x ISAUTHORIZED BY AT LEAST ONEBATCH SUBSYSTEM.

ExplanationThere was at least one batch subsystem that isauthorized to use database x.

System actionThe named database is processed locally and globally(if SCOPE = GLOBAL).



DFS3322 DBRC NOT ACTIVE.

ExplanationA /RMx command was entered, but DBRC is notpresent.


Operator responseEnter the recovery management commands (/RMx)only when DBRC is present.

DFS3323E TRANSACTION REQUEST WASDISCARDED BY BACKEND IMSxxxxxxxx DUE TO MAX TPIPECONDITION

ExplanationThe following explanation applies to non-Fast-Pathtransactions only.

IMS shared-queues back-end IMS detected a tpipeflood condition for an OTMA front-end initiatedtransaction at the application GU time. The limit, whichis specified in the OTMA client descriptor, can be theMAXTP limit for an OTMA client or for DFSOTMA.


xxxxxxxxIMS ID for the shared-queues back-end IMS.

This message is issued only when both front-end andback-end IMS systems have the MAXTP enhancementAPAR PM71035 applied.

System action:IMS shared-queues back-end system discards thistransaction without stopping it. This DFS3323Emessage is sent to the front-end IMS for OTMA client.

Programmer response:Issue the /DISPLAY OTMA command to view theTPCNT value, which is the total TPIPEs in use, andthe MAXTP value, which is the TPIPE limit specifiedin the OTMA client descriptor. You can issue the IMS /CHECKPOINT command three times to force the tpipecleanup so that idle tpipes in the system can bedeleted.

Module:DFSYLUS0, DFSDLA30

DFS3324I TRAN tttttttt SUSPENDED

ExplanationThe input message being processed by transactiontttttttt was placed on the suspend queue becauseIRLM pseudoabend 3303 occurred. The explanationfor 3303 lists possible reasons for the abend. Thismessage is issued along with message DFS554A whenabend 3303 occurs. However, be aware that DFS3324Iis only issued the first time this input message isplaced on the suspend queue.

The application program has incurred a pseudoabend,and the next applicable transaction for the region isscheduled.

System actionThe input message being processed when abend 3303occurred is placed on the suspend queue. If it is thefirst time this particular input message is placed onthe suspend queue, a counter for the transaction isincreases by one. The counter is decremented by twofor each message successfully processed. When thecounter exceeds 10, the transaction stops.

The input message is scheduled for processing againwhen the messages on the suspend queue aretransferred to the normal queue for this transactiontype. This situation occurs under either of the followingcircumstances:

1. A /START TRAN or UPDATE TRANSTART(SUSPEND) for this transaction type isissued.

2. A /START DATABASE or UPDATE DBSTART(ACCESS) is issued for a database whichcan be accessed during processing of thistransaction type.

The messages on suspend queues for all transactionsare transferred to the normal queues by the /DEQSUSPEND command.

Operator response(Master terminal operator) If the originating terminalwas in conversational mode, exclusive mode, orresponse mode, notify the terminal operator of thefailing condition. Enter the /EXIT command to freethe terminal, or wait until the failing subsystemcompletes its recovery and allows the rescheduling ofthe suspended messages.

(Terminal operator) If the mode of operation isconversation, the operator is notified by the masterterminal operator. Enter the /EXIT command to freeyour terminal, or wait until the suspended messagecan be rescheduled.


Related information“DFS554A” on page 197jobname.region.stepname. prog PSBname(x)transaction-codesys-completion-code user-completion-code PSBSMBLTERM:|LUNAME:|RTKN=tokenREASON=reason originating terminalIMS abend 3303

DFS3325I DBRC INDICATES AREA xxxxxxxxIS NOT ELIGIBLE FOR LCL CMD

or

DBRC INDICATES DB xxxxxxxx IS NOT ELIGIBLEFOR LCL CMD

ExplanationDBRC indicates that the named database or area hasa PREVENT FURTHER AUTHORIZATION flag set. Thissituation continues until a global /START DB or /START AREA command is issued.

System actionThe command is ignored for the named area.

Operator responseNotify the database administrator that a global /START DB or /START AREA command should beentered.

DFS3326I TEMPORARY IRLM FAILURE,UNABLE TO PROCESS GLOBALCOMMAND

Explanation:The IRLM has encountered a temporary problem whileprocessing the GLOBAL command.

System actionThe command has been processed on the localsubsystem, but has not been sent to the receivingsubsystems.

Operator responseReissue the global command, or issue the commandon each sharing subsystem.



DFS3327 MORE THAN 29 DB or 27 AREANAMES NOT SUPPORTED BYGLOBAL COMMANDS

ExplanationA maximum of 29 database names or 27 area namescan be supplied on a global command.


Operator responseCorrect the entered command, and reenter it.

DFS3328I GLOBAL cmd COMMAND seqno INPROGRESS

ExplanationThe seqno is a sequential number used to tie thismessage with the global command that initiated theaction.


DFS3329I CHECKPOINT IN PROGRESS,CANNOT PROCESS GLOBALCOMMAND seqno

ExplanationA checkpoint from a previously entered commandor an automatic system checkpoint is currently inprogress. Seqno is the sequence number of the globalcommand that initiated the action.


Operator response:(master terminal) Reenter the command when thecurrent checkpoint is completed.

DFS3330I ERESTART IN PROGRESS,CANNOT PROCESS GLOBALCOMMAND seqno



ExplanationA restart command is currently being processed.seqno is the sequential number of the global commandthat initiated the action.


Master terminal operator response: Wait forthe /ERE command to be completed, and reenter thecommand.

DFS3331I DBDUMP ALREADY IN PROGRESS,CANNOT PROCESS GLOBALCOMMAND seqno

ExplanationA /DBDUMP command previously entered has not yetbeen completed. Seqno is the sequence number of theglobal command that initiated the action.


Operator response:(master terminal) Wait for the dump command to becompleted, and reenter the command.

DFS3332I DBRECOVERY ALREADY INPROGRESS, CANNOT PROCESSGLOBAL COMMAND seqno

ExplanationA database recovery command previously entered hasnot yet completed. Seqno is the sequential number ofthe global command that initiated the action.


Master terminal operator response: Wait for thedatabase recovery command to be completed andreenter the command.

DFS3333I MSDB CHKPT IN PROGRESS,CANNOT PROCESS GLOBALCOMMAND seqno

ExplanationThis is the global command equivalent to DFS2717I.An MSDB checkpoint from a previously enteredcommand or an automatic system checkpoint iscurrently in progress. Seqno is the sequence numberof the global command that initiated the action.


Operator response:(master terminal) Wait for the checkpoint tocomplete, and reenter the command.

DFS3334I hh:mm:ss GLOBAL cmdCOMMAND seqno INITIATEDBY SUSBYSTEM=ssid FOR THEFOLLOWING DATA BASES|AREA|ADS(s)

ExplanationThe indicated global command, initiated from anothersubsystem, is being processed in this subsystem. Thefollowing defines cmd, seqno and ssid:Keyword

Meaningcmd

The command being processed.seqno

A sequential number assigned to this commandthat will be used in the response to the commandissued by this subsystem.

ssidThe subsystem ID of the indicating subsystemwhich issued the global command.



DFS3335A LOG INPUT IS NOT IN SEQUENCEFOR FUNCTION CA; REASONCODE=r

ExplanationThe log input is not in sequence for the CA function.The return code r has one of the following values:01

The error occurred during the creation of a log dataset using the Change Accumulation utility. Therewas a log input from both the DB sharing releaseIMS system and from an IMS system previous toDB sharing.

02The error occurred during the creation of a changeaccumulation data set. There was a log input from


both a DB sharing release IMS system and from anIMS system previous to data sharing.


Programmer responseDetermine the correct sequence of the log input, andcorrect the JCL so that the log input is in the correctsequence.

Problem determination2, 3, 8, 36. If running under the utility control facility,rerun the job with a FUNCTION=OP, MSGNNN=3335control statement in the DFSYSIN data set. Supply aDFSUDUMP DD statement to this step.

If a DFSUSNAP DD statement is specified, thendiagnostic information is written to that data set indump format to help locate the log record in error. Theinformation is dumped in four parts:

1. Partial Log Record Data. Contains the last 4 bytesof the previous log record followed by 246 bytes ofthe error log record.

2. Log Record Sequence Number Data. Contains thelast 8 bytes of data for the error log record.

3. UCSTAT Table Entry. Contains the entire UCSTATtable entry data used by module DFSUC150 toperform the log sequence checking.

4. DFSULOG JFCB Information. Contains the JFCBdata for the DFSULOG data set being processed.Use this information to determine the data setname and volume serial number.


DFS3336I SUSPEND QUEUE DRAINED

ExplanationThe transactions that were suspended have beenremoved from the suspend queue and reenqueued ontheir original transaction queue.

System actionThose transactions that were suspended are noweligible to be processed.


DFS3337W DBRC IS NOT ACTIVE, BUT WASACTIVE WHEN THE INPUT LOGWAS CREATED.

ExplanationThe issuing utility program discovered an indicationfrom the X'42' log record that DBRC was activeat the time the input log data set was created.However, DBRC is not active during this utility programexecution.

System actionProcessing continues normally, but DBRC is notnotified about the utility execution.

Programmer responseVerify whether DBRC should have been active duringthe execution of the utility. If DBRC notification isrequired, then use DBRC commands to manuallyupdate RECON data set records to reflect the currentlog information.

DFS3338A OLIC AUTHORIZATION FAILURE -nnnncccc ALREADY AUTHORIZED

ExplanationThis error occurs when restart is requested for a dataset copy and the indicated subsystem name is notsigned-on to DBRC. It can also occur when restartwas not requested and the indicated subsystemname was already signed-on to DBRC. The namennnncccc represents the global data managementblock number, DCB number, and the IMSID for theonline IMS subsystem to which the online image copyis connected.

System actionThe execution is terminated with an error.

Programmer responseIf restart was not requested, online image copy shouldbe rerun, specifying restart. If restart was specified,online image copy should be rerun without specifyingrestart. If the checkpoint-restart facilities are notbeing used, the DBRC command CHANGE.SUBSYSmust be issued to do an abnormal sign off for thename nnnncccc, and online image copy rerun to copythe complete data set again.


DFS3339A DATABASE AUTHORIZATIONFAILURE. CODE - n

ExplanationCode n identifies the reason for the authorizationfailure.Code (hex)

Meaning4

IMS online subsystem could not obtain a databaseauthorization for the database to be copied. If youissued the /DBR command for the database, makesure that it is available to the online system byissuing a /START command.

8An authorization for the Online Image Copyfailed. Another IMS subsystem (batch or online),other than the online IMS subsystem whichOnline Image Copy is connected to, has updateauthorization for the database to be copied.

COnline Image Copy authorization failed becausethe database is not recoverable.

System actionThe execution is terminated with an error.

Programmer responseThe online IMS subsystem to which the Online ImageCopy is connected, must be the only subsystemauthorized for updating capability. This error alsoindicates that another Online Image Copy, connectedto another online IMS subsystem, currently has theauthorization to make a copy of this data set inthe database. If the database is a HALDB partitionand the master database has been deallocated, thenthe database must be started before authorization isgranted at the partition level.

ModuleDFSUICP0

DFS3340I DFS3340I - IRLM VERIFYREQUEST FAILED. RC=xxx,yyy

ExplanationDuring a database authorization processing, IRLM wascalled to verify the subsystems which were previouslyauthorized to use the database with an update or readintent. The IRLM verification request failed becauseof a nonzero return code from IRLM. The return codexxx represents the IRLM return code and the return

code yyy represents the IRLM feedback subcode.If XXX=012 and YYY='zz', the value indicates thatthe number of subsystem entries for the verificationrequest exceeds the maximum capacity currentlysupported.

System actionThe IMS subsystem continues while online, but thescheduled application terminates. For batch or utility,the subsystem terminates and receives messageDFS047A with a reason code of 09.


Related information“DFS047A” on page 35UNABLE TO OBTAIN AUTHORIZATION FORDATA BASE xxxxxxxx. REASON CODE = zz. PSB=psbname.

DFS3341I DATA BASE dbname IS USINGDATA SETS NOT REGISTEREDWITH DBRC

ExplanationThe DDNAME or DSNAME identified by dbname in themessage was passed to DBRC, but did not matchthe names registered to DBRC. When IMS authorizesthe use of a database with DBRC, the DDNAME andDSNAME of the first database data set are passedto DBRC. DBRC compares these names with thoseregistered for the database.

System actionIMS treats the database as though it were notregistered to DBRC at all (that is, no DBRCauthorization protection is provided for this database).This means that no database or block level datasharing can take place for this database.

Programmer responseIf you want to use data sets that do not matchthose registered in the DBRC RECON, then no actionis required. If the intent is to use the correctdatabase data sets, correct the startup JCL or dynamicallocation member, or the DBRC registration.

DFS3342I AREA areaname IS NOTREGISTERED WITH DBRC.INVALID FOR GLOBAL CMND


ExplanationA global command was issued to register an area thatwas not registered with DBRC. A global commandis accepted only if an area is registered to DBRC;otherwise, the command is considered invalid.

System actionIMS ignores the command and continues processing.

Operator responseAsk the database administrator if the named areashould be registered to DBRC. If the area is notregistered, enter the correct command.

DFS3343E CANNOT PROCESS DFSTCF LOADCOMMAND, REASON=xx

ExplanationIMS was unable to process the DFSTCF LOADcommand. The reason code explains why IMS wasunable to process this command:Reason code

Meaning01

The queue module could not enqueue the TCOlogical terminal DFSTCFI on the new line or node.

02TCO logical terminal DFSTCFI was having amessage dequeued and sent. It cannot bereassigned until it is finished.

03Either the physical terminal that is associated withthe LTERM specified in the DFSTCF LOAD OUTPUTcommand or the physical terminal that TCO LTERMDFSTCFI is assigned to was in conversationalmode, preset mode, response mode, or is in asigned-on subpool.

04The physical terminal that is associated with theLTERM specified in the DFSTCF LOAD OUTPUTcommand or the physical terminal that TCO LTERMDFSTCFI is assigned to was switched line.

05The TCO LTERM DFSTCFI cannot be assigned toa PTERM defined MSGDEL=SYSINFO. For example,TCO LTERM DFSTCFI has messages queued on thesystem queue.

06The TCO LTERM DFSTCFI cannot be assignedto a PTERM defined MSGDEL= NONIOPCB. Forexample, TCO LTERM DFSTCFI has messagesqueued on the system or application output queue.

07A request for another script member was alreadyin progress.

System actionThe DFSTCF LOAD command is not processed. IMScontinues.

Programmer responseTake the action associated with the reason codereceived:Reason code

Action01

This code denotes a system error. Shut down thesystem and create a memory dump at the earliestpossible time for analysis of the problem. Notifythe IMS system programmer.

02Reenter the DFSTCF LOAD command after thecurrent message is completed, or reenter theDFSTCF LOAD command without the OUTPUToption.

03Wait for the terminal to be freed, or reenter theDFSTCF LOAD command with a different LTERMname.

04Reenter the DFSTCF LOAD command with anLTERM that is associated with a valid line.

05Reenter the DFSTCF LOAD command with adifferent LTERM name.

06Reenter the DFSTCF LOAD command with adifferent LTERM name.

07Reenter the DFSTCF LOAD command.

DFS3344E DFSTCF LOAD CONTAINS INVALIDCHARACTER IN FIELD x

ExplanationThe DFSTCF LOAD command is incorrect. FIELD xidentifies the invalid keyword or parameter.

The format for the DFSTCF LOAD command is:

DFSTCF LOAD XXXXXXXX (OUTPUT YYYYYYYY) (CONT ZZ)

The value of x (FIELD x) can be one of the following:01

The first positional keyword is not DFSTCF.


02The second positional keyword is not LOAD.

03The third positional parameter was not specified.The third positional parameter xxxxxxxx is a 1-8character script name.

04The fourth (optional) positional keyword is notOUTPUT.

05The fifth positional parameter was not specified oris greater than eight characters. yyyyyyyy is a 1-8character LTERM name.

06The sixth (optional) positional keyword is notCONT.

07The seventh positional parameter was notspecified or is a number greater than two digits.zz is a number from 1 to 99.

System actionThe DFSTCF LOAD command is ignored. Processingcontinues.

Operator responseCorrect the DFSTCF LOAD command and resubmit.

DFS3345E DFSTCF DOES NOT CONTAINMEMBER name

ExplanationThe data set specified on the DFSTCF DD statementdid not contain the timetable member identified in themessage.

System actionIf the Time-Controlled Operations Verification utilitywas running, the utility terminates. If IMS online wasrunning, the DFSTCF LOAD command fails, but IMSprocessing continues.

Programmer responseVerify that the timetable member is specified correctlyand that the timetable member resides in the dataset specified on the DFSTCF DD statement. Rerun theutility or reissue the DFSTCF LOAD command.

DFS3346E TCO EXIT RECEIVED STATUS CODEstatus code

ExplanationThe Time-Controlled Operations (TCO) languageinterface routine returned a status code to the TCO exitroutine.

System actionThe TCO message was not processed. TCO processesthe next time request.

DFS3347A CHANGE ACCUM PROCESSING INDFSUCMN0 FAILED - REASON = n.

ExplanationA change accumulation request failed because anerror was detected in module DFSUCMN0 for one ofthe following reasons:Code (hex)

Meaning1

An error was detected in the SYSIN control card.2

DBRC initialization failed.3

Log processing in DFSUC150 failed.


Programmer responseFor reason code 1, correct the error in SYSIN controlcard and rerun the utility.

For reason code 2, find DBRC message DSP0351I inthe job output for additional information. Examine theRECON data set and the JCL for any inconsistencies.Then, rerun the utility.

For reason code 3, ensure that all input logs arecorrect and rerun the utility.

ModuleDFSUCMN0

Related informationDSP0351I (Messages and Codes)

DFS3348E UNABLE TO ESTABLISH ESTAECreated by ActiveSystems12/24/96 Entity not defined. TCOUNAVAILABLE



ExplanationThe Time-Controlled Operations (TCO) ESTAE routinewas not established.

System actionTCO terminates, but IMS continues processing.

Programmer responseMake sure that the ESTAE routine was bound correctlyand that enough storage is available.

DFS3349I UNABLE TO INITIALIZE TIMECONTROL OPTION, REASON=....

ExplanationIMS was unable to initialize the Time-ControlledOperations (TCO). The reason code tells why TCOinitialization failed.Reason code

MeaningOPEN

Unable to OPEN a data set.CTT

Unable to find Communication Terminal Table(CTT) for TCO.

CTBUnable to find Communication Terminal Block(CTB) for TCO.

GET0Unable to acquire storage from subpool 0.

GETCUnable to acquire storage from subpool 231.

NODDDFSTCF DD card does not exist.

CIRLUnable to create an ITASK for TCO CLB.

LOADUnable to load user exit DFSTCNT0.

System actionTCO is not initialized. IMS processing continues.

Programmer responseTake one of the following actions based on the reasoncode you received:

Reason codeAction

OPENVerify that the DFSTCF DD statement specifies thecorrect data set for TCO, or that the data set exists.

CTTCheck the link of the IMS nucleus to confirm thatthe TCO device-dependent module was included.

CTBCheck the IMS system definition to determine if aterminal block was accidentally deleted.

GET0If sufficient storage is unavailable, increase thesize of the control region.

GETCIf sufficient storage is unavailable, increase thesize of the control region.

NODDInformation only. To use TCO now, stop and restartIMS to include the DFSTCF DD card.

CIRLDetermine why the ITASK creation is notsuccessful and run IMS.

LOADCheck that DFSTCNT0 is in the system.

DFS3350E TCO ABNORMALLY TERMINATED,SEE DUMP

ExplanationA failure occurred in a Time-Controlled Operations(TCO) exit routine module.

System actionThe IMS spin-off memory dump facility SNAPs theTCO environment. TCO then waits for the operatorto issue the DFSTCF LOAD command. IMS continuesprocessing.

Operator responseTry issuing the DFSTCF LOAD command to reloadthe same timetable member or a different timetablemember.

Programmer responseUse the SNAP dump of the TCO environment todetermine the cause of the problem.


Chapter 71. DFS messages, DFS3351E - DFS3400I


DFS3351E TCO ABNORMALLY TERMINATED,SYSTEM ABEND, SEE DUMP

ExplanationA system abend terminated the Time-ControlledOperations (TCO).

System actionThe IMS spin-off memory dump facility SNAPs the TCOenvironment and TCO terminates.

Programmer responseUse the SNAP dump of the TCO environment todetermine the cause of the problem.

DFS3352E INCOMPLETE MESSAGEENCOUNTERED, SEQUENCENUMBER=nnnnnnnn

ExplanationWhile processing a message set, the Time-ControlledOperations (TCO) or the TCO Verification utilityencountered a time schedule request when acontinued segment or message was expected. Thesequence number identifies the statement containingthe error.

System actionTCO or the TCO Verification utility discards the entiremessage set and processing continues.

Programmer responseCorrect the error in the message set. Check for a straycontinuation character in the message or an omittedsegment or message.

DFS3353E INVALID CONTINUATIONCHARACTER, SEQUENCENUMBER=nnnnnnnn

ExplanationThe Time-Controlled Operations (TCO) or the TCOVerification utility found a character other than ablank (end of message), S (end of segment), or X(segment continued) in column 72 of a message

set statement. The sequence number identifies thestatement containing the error.

System actionTCO or the TCO Verification utility discards themessage set and processing continues.

Programmer responseCorrect the error in column 72 of the message setstatement.

DFS3354E TOO MANY SEGMENTCONTINUATIONS, SEQUENCENUMBER=nnnnnnnn

ExplanationOnly 10 statements can be continued into a singlesegment (710 characters). The sequence numberidentifies the statement containing the error.

System actionThe Time-Controlled Operations (TCO) or the TCOVerification utility discards the message set andprocessing continues.

Programmer responseDelete as many statements as necessary so themaximum is not exceeded.

DFS3355E I/O ERROR READING DFSTCFscript-member name

ExplanationAn I/O error occurred while reading the data setspecified on the DFSTCF DD statement. The messageidentifies the name of the timetable member thatthe Time-Controlled Operations (TCO) was processingwhen the error occurred.

System actionProcessing of the timetable member terminates. TCOmight have processed part of the list and processesthe rest of the list, if possible.


Programmer responseCorrect the error and reload the timetable member, orload a different timetable member.

DFS3356E END TIME PRIOR TO START TIME,SEQUENCE NUMBER=nnnnnnnn

ExplanationThe time to stop scheduling (columns 21-24) wasearlier than the time to start scheduling (columns7-10). The sequence number identifies the statementcontaining the error.

System actionThe Time-Controlled Operations (TCO) or the TCOVerification utility rejects the time schedule requestand processing continues.

Programmer responseCorrect the time schedule request error. Make surethat:

• The start time is earlier than the end time.• The start time is in columns 7-10 and the end time is

in columns 21-24.

Then rerun the TCO Verification utility for thistimetable member.

DFS3357E RESIDENT INDICATORINCORRECT, SEQUENCENUMBER=nnnnnnnn

ExplanationThe resident indicator in column 31 of a time schedulerequest must be either a blank (resident exit routine)or a D (dynamic load). The sequence number identifiesthe statement containing the error.

System actionTCO rejects the time schedule request and processingcontinues.

Programmer responseCorrect the time schedule request. Make sure that:

• The resident indicator is valid.• The resident indicator is specified in column 31.

Rerun the TCO Verification utility for this timetablemember.

DFS3358E DISPATCH INDICATORINCORRECT, SEQUENCENUMBER=nnnnnnnn

ExplanationOnly a blank (schedule at same time each day), anO (schedule first day and delete), or an S (scheduleat startup) are valid codes in column 32 of the timeschedule request. The sequence number identifies thestatement containing the error.


Programmer responseCorrect the time schedule request error. Make surethat:

• The dispatch indicator is in column 32.• The dispatch indicator is valid.

Rerun the TCO Verification utility for this librarymember.

DFS3359E MESSAGE SET INDICATED, NOMESSAGE FOUND SEQUENCENUMBER=nnnnnnnn

ExplanationThe time schedule request specified the use of aprevious message set (**** in columns 56-59), but themessage set was not provided. The sequence numberidentifies the statement containing the error.


Programmer responseAdd the missing message set, or delete the timeschedule request. Rerun the TCO Verification utility forthis library member.

DFS3360E USER EXIT xxxxxxxx REQUESTEDNOT FOUND, SEQUENCENUMBER=nnnnnnnn


ExplanationIMS.SDFSRESL did not contain exit routine xxxxxxxxspecified in columns 12-19 of a time schedulerequest. The sequence number identifies thestatement containing the error.

System actionThe Time-Controlled Operations (TCO) rejects the timeschedule request and processing continues.

Programmer responseCheck the spelling or the justification, or both, of thename. Names with fewer than 8 characters must beleft-aligned and padded with blanks. Rerun the TCOVerification utility for this timetable member.

DFS3361E INSUFFICIENT VIRTUAL STORAGEFOR TABLES

ExplanationThe Time-Controlled Operations (TCO) was unableto acquire enough storage to build the message orrequest tables.

System actionThe Time-Controlled Operations (TCO) terminates thetimetable member load and frees all storage.

Programmer responseSpecify more storage and then restart the job. Seethe Summary Report produced by the TCO Verificationutility to determine the amount of storage needed for aspecific timetable member.

DFS3362E TIME tttt SPECIFIED IS INVALID,SEQUENCE NUMBER=nnnnnnnn

ExplanationOne of the time fields of a time schedule request(columns 7-10, 21-24, or 26-29) did not containeither blanks or a value between 0001 and 2359.tttt identifies the invalid time. The sequence numbernnnnnnnn identifies the statement containing theerror.


Programmer responseMake sure that the time is valid and is specified in thecorrect columns. Valid HH values are 00-23; valid MMvalues are 00-59. Rerun the TCO Verification utility forthis timetable member.

DFS3363E UNABLE TO OPEN SYSIN

ExplanationThe TCO Verification utility was unable to open theSYSIN input data set.

System actionThe TCO Verification utility terminates.

Programmer responseMake sure that the SYSIN DD statement is present,and if present, the SYSIN data set exists. Rerun theTCO Verification utility for this timetable member.

DFS3364E UNABLE TO OPEN SYSPRINT

ExplanationThe TCO Verification utility was unable to open theSYSPRINT output data set.

System actionThe TCO Verification utility terminates.

Programmer responseMake sure that the SYSPRINT DD statement is presentand the SYSOUT class is valid. Rerun the TCOVerification utility for this timetable member.

DFS3365I TCO MESSAGE MODULE REQUIRESMAINTENANCE

ExplanationThe Time-Controlled Operations (TCO) utility wasunable to display a message.

System actionThe system performs the action described in themessage TCO was unable to display.

Programmer responseBind the TCO message module again.

Chapter 71. DFS messages, DFS3351E - DFS3400I 941

DFS3366E NO TIMER ELEMENT FOUND.SCRIPT WILL NEVER BEEXECUTED. MEMBER name

ExplanationProcessing for a TCO script finished, but no timerelement was specified. The script requires that an*TIME statement be included.


The name of the script member

System actionThe TCO or the TCO Verification utility discards thescript and processing continues.

Programmer responseCorrect the error by adding the required *TIMEstatement to the TCO script member.

DFS3367E TIMER ELEMENT NOT FOUNDFOLLOWING THE LASTMESSAGE ELEMENT, SEQUENCENUMBER=nnnnnnnn

ExplanationThe last statement in the TCO script was not a *TIMEstatement. The last message element is not scheduledfor processing.

System actionThe TCO or the TCO Verification utility discards the lastmessage statement and processing continues.

Programmer responseCorrect the error by verifying that the *TIMEstatement is not in the wrong place. Add a *TIMEstatement as the last statement in the TCO script.

DFS3368E ERROR PROCESSING RDDS,RC=rc, RDDSDSN =dsname

ExplanationThe system encountered an error while trying toaccess a resource definition data set (RDDS).Codes

Explanation4

An error occurred trying to read data from anRDDS.

8An error occurred trying to write data to an RDDS.

12An error occurred trying to allocate an RDDS.

16An error occurred trying to open an RDDS.

20The RDDS is owned by another IMS.

24The RDDS RECFM is not variable blocked (VB).

28The RDDS BLKSIZE value is invalid. One of thefollowing conditions exist:

• The RDDS BLKSIZE is greater than 32 760.• The RDDS BLKSIZE is less than 4096.

System actionIf automatic import is in progress, and you hadspecified RDDSERR=ABORT in the DFSDFxxx PROCLIBmember, IMS terminates with a 3368 abend.

If you had specified RDDSERR=NOIMPORT , IMScontinues cold start processing without importingany resource or descriptor definitions. IMS startswithout any runtime resource definitions or descriptordefinitions from the RDDS.

If automatic export is in progress, the automaticexport process terminates abnormally.

Programmer responseReturn codes 4, 8, 12, and 16 indicate errors in openor close, dynamic allocation, or reading and writing tothe RDDS named in the message. Look for supportingmessages from IOS or dynamic allocation to furtherdefine and correct the error condition.

Return code 20 indicates that another IMS systemhas claimed this RDDS. Remove this RDDS from theRDDSDSN= parameter of the DFSDFxxx IMS.PROCLIBmember on the system reporting the error.

Return code 24 indicates that an RDDS wasallocated using an LRECL other than variable blocked.Correct this condition by reallocating the RDDS withRECFM=VB.

Return code 28 indicates that an RDDS was allocatedusing a block size larger than 32 760 or smallerthan 4096. Reallocate the RDDS with a BLKSIZE inthe range of 4096 to 32 760 inclusive. Performancemight be affected during autoexport when all RDDSsare not allocated with the same BLKSIZE. UsingBLKSIZE=32760 for all RDDSs is recommended.

In addition, see the information about abend 3368 foractions to take.


Module:DFSRDD00


DFS3369I RDDS INITIALIZATIONCOMPLETED

Explanation:Initialization processing for the resource definitiondata sets (RDDS) has completed.

System action:IMS continues processing.


Module:DFSRDD10

DFS3370E NO SYSTEM RESOURCEDEFINITION DATA SETSAVAILABLE FOR AUTOMATICEXPORT

Explanation:There were no valid system resource definition datasets that can be used for automatic export processing.This message is highlighted and remains highlighteduntil a resource definition data set becomes available.

System action:IMS continues processing. The automatic exportprocess is disabled until one or more of the systemresource definition data sets are fixed.

Programmer response:Refer to any DFS3368E messages that were issuedbefore this message to determine why the data setsare unavailable. Make sure that the failing data setsare available.

Module:DFSRDD00

Related informationDFS3368EERROR PROCESSING RDDS, RC=rc, RDDSDSN=dsname

DFS3371I SUCCESSFUL AUTO EXPORTTO RDDSDSN=dsnameTIME=timestamp-UTC

Explanation:Automatic export completed successfully. dsnameidentifies the name of the system resource definitiondata set (RDDS) to which the resource and descriptordefinitions were exported. timestamp identifies theUTC time value that is used to identify the most recentRDDS. This value is placed in the RDDS header record;

you can view the value in an RDDS data set using ISPFor similar read utility.



Module:DFSXP000

DFS3372E AUTOMATIC EXPORT FAILED,RC=rc

ExplanationAn automatic export failed. rc indicates the reason forthe failure. The return code rc values are as follows:Codes

Explanation4

An I/O error occurred while trying to access aresource definition data set (RDDS).

8No RDDS data sets are available.

12An error occurred trying to obtain a 64-bit buffer.


Programmer response:To determine the cause of the failure, see anyDFS3368E messages that were issued before thismessage.

Module:DFSXP000

Related informationDFS3368EERROR PROCESSING RDDS, RC=rc, RDDSDSN=dsname

DFS3373I AUTOMATIC EXPORT IS ENABLEDTO target

ExplanationAutomatic export processing is enabled to target,where target can be:RDDS

Indicates that the MODBLKS resource anddescriptor definitions will be automaticallyexported to a system resource definition data set(RDDS) at checkpoint time.



REPOSITORYIndicates that any MODBLKS resource anddescriptor definitions that have been newlycreated or modified since the last successfulexport (by using a command or automatic export)will be automatically exported to the IMSRSCrepository at checkpoint time.

If AUTOEXPORT=AUTO is defined and IMS is enabledwith both the IMSRSC repository and the RDDS,the DFS3373I message is issued twice, once withtarget=RDDS and once with target=REPOSITORY.



Module:DFSDFN10

Related conceptsMaintaining your dynamic resource definitionenvironment (System Definition)Exporting MODBLKS resource and descriptordefinitions to an RDDS (System Definition)Exporting MODBLKS resource and descriptordefinitions to an IMSRSC repository (SystemDefinition)

DFS3374W AUTOMATIC EXPORT IS DISABLEDRC=rc

ExplanationAutomatic export processing is disabled. rc identifiesthe reason automatic export is disabled. Possiblereasons are as follows:Codes

Explanation4

You specified AUTOEXPORT=NO.8

You specified AUTOEXPORT=AUTO, but you havenot defined any RDDSs and the IMSRSC repositoryis not enabled.

12You have not defined the DFSDFxxx IMS.PROCLIBmember.

16You have not defined the DYNAMIC_RESOURCEsection of the DFSDFxxx IMS.PROCLIB member.

20IMS cannot automatically export to the IMSRSCrepository because AUTOEXPORT=AUTO was

defaulted to and the AUTOEXPORT=AUTOparameter was not specified.

24You specified AUTOEXPORT=REPO, but theIMSRSC repository is not enabled.


Programmer responseIf you do not want to use automatic export processing,no action is necessary.

If you want automatic export processing, use thereturn code to identify and correct the specificationerror in the DFSDFxxx IMS.PROCLIB member.

Module:DFSDFN10, DFSRDD10

DFS3375 UNABLE TO ACQUIRE STORAGEIN SUBPOOL 0 FOR MODIFYCOMMAND

ExplanationThe /MODIFY or INITIATE OLC command processorfailed to get storage in the private region.


Operator responseReenter the command when there is less activity inthe private region and more storage is available. If theproblem occurs often, increase the size of availablestorage in the private region.

DFS3376 UNABLE TO ACQUIRE STORAGEIN THE WORK AREA POOL FORMODIFY

ExplanationThe /MODIFY or INITIATE OLC command processorfailed to get storage in the work area pool (WKAP).


Operator responseReenter the command when there is more spaceavailable in the WKAP.

DFS3377 INSUFFICIENT STORAGEAVAILABLE IN CIOP


http://www.ibm.com/support/knowledgecenter/SSEPH2_15.1.0/com.ibm.ims15.doc.sdg/ims_maintainyourdynamicresourcedefinitionenvironment.htm#maintainyourdynamicresourcedefinitionenvironment

http://www.ibm.com/support/knowledgecenter/SSEPH2_15.1.0/com.ibm.ims15.doc.sdg/ims_maintainyourdynamicresourcedefinitionenvironment.htm#maintainyourdynamicresourcedefinitionenvironment

http://www.ibm.com/support/knowledgecenter/SSEPH2_15.1.0/com.ibm.ims15.doc.sdg/ims_exporting_resources_drd_rdds.htm#exportingresourceanddescriptordefinitionstoanrdds

http://www.ibm.com/support/knowledgecenter/SSEPH2_15.1.0/com.ibm.ims15.doc.sdg/ims_exporting_resources_drd_rdds.htm#exportingresourceanddescriptordefinitionstoanrdds

http://www.ibm.com/support/knowledgecenter/SSEPH2_15.1.0/com.ibm.ims15.doc.sdg/ims_exporting_resources_drd_repo.htm#exportingresourceanddescriptordefinitionstotheimsrepository



ExplanationThe command processor failed to get storage in thecommunication input or output pool (CIOP).


Operator responseReenter the command when there is more spaceavailable in the CIOP.

DFS3378W BLDL FAILED FOR xxxxxxx DURINGONLINE CHANGE

ExplanationWhile processing a /MODIFY or INITIATE OLCcommand, IMS encountered an error building adirectory entry list. The error occurred for ACBLIBxxxxxxx.


Operator responseIf the error occurred on the ACBLIB that is currently inuse by the online IMS system, the error can recur onthat online system. If the error occurred for an inactiveACBLIB, recreate that ACBLIB.

DFS3379E DFSTCF LOAD CONTAINS INVALIDOUTPUT LTERM

ExplanationThe LTERM in the DFSTCF LOAD command is notrecognized by IMS.

System actionIMS ignores the command and continues processing.

Operator responseCheck the LTERM name and reissue the command.

DFS3380 TCO INACTIVE, CANNOT LOAD/PROCESS SCRIPTS

ExplanationA message switch to LTERM DFSTCF was issued. Themessage switch might have been a DFSTCF LOADcommand to load TCO scripts; however, TCO is notcurrently active and cannot handle requests.

Usage of LTERM DFSTCF is restricted to the TCOfunction. Any message switched to DFSTCF is assumedto be a request to load a TCO script.

System actionThe message switch is ignored; IMS continues.

Programmer responseIf you want to load and process TCO scripts, bringdown IMS. Then bring it up again and include the //DFSTCF DD card to activate the TCO function.

DFS3381E CF INITIALIZATION FAILED,DATA=aa bbbbbbbb ccccccccddeeffgg

ExplanationThe coupling facility services function was notinitialized. The DATA portion of the message identifiesthe reason for the failure:aa

The place code, which identifies when the errorwas found. aa can have the following values:Code (hex)

Meaning10

While connecting to an OSAM structure20

While connecting to an OSAM structure forsequential buffering

30During connection to a VSAM structure

40While passing connection data to VSAM fordata shared resource pool

50While passing connection data to VSAM forindex shared resource pool

bbbbbbbbThe return code from the last service started. Seez/OS MVS Programming: Sysplex Services Reference(SA22-7618) for the values of this code.

ccccccccThe associated reason code. See z/OSMVS Programming: Sysplex Services Reference(SA22-7618) for the values of this code.

ddeeffggThe associated flag bytes.

dd can have the following values:Code (hex)

Meaning


80Invalid function was requested.

40Connection to the OSAM structure failed.

20Too few OSAM buffers were returned duringconnection to the OSAM structure.

10Connection to the VSAM structure failed.

08Attempt to pass connection data to VSAM fordata shared resource pool failed.

04Attempt to pass connection data to VSAM forindex shared resource pool failed.

02Disconnection from the OSAM structure failed.

01Disconnection from the VSAM structure failed.

ee can have the following values:Code (hex)

Meaning80

A dummy PST was obtained during couplingfacility services initialization or execution.

40Connection to the OSAM structure wassuccessful.

20Disconnection from the OSAM structure wassuccessful.

10Connection to the VSAM structure wassuccessful.

08Disconnection from the VSAM structure wassuccessful.

ff can have the following values:Code (hex)

Meaning80

A request was received to stop data sharingbecause coupling facility services initializationfailed.

gg can have the following values:Code (hex)

Meaning80

A read-and-register operation for the OSAMbuffer failed.

20Buffer invalidation for the OSAM buffer failed.

System actionSee system action for message DFS3384I.

Programmer responseIf aa is 10, 20, or 30, see z/OS MVS Programming:Sysplex Services Reference (SA22-7618) for errorreturn and reason codes that identify the cause offailure. If aa is 40 or 50, see the appropriate DFSMSpublication for error return codes that identify thecause of failure.


Related information“DFS3384I” on page 947DATA SHARING STOPPED“IMS problem determination” on page 11IMS messages and codes problemdetermination is accomplished by usingprocedures established by IBM.

DFS3382I CF INITIALIZATION COMPLETE

ExplanationThe coupling facility services function was successfullyinitialized.



DFS3383E STOP DATA SHARING FAILED,DATA=aa bbbbbbbb ccccccccddeeffgg

ExplanationThe attempt to disconnect from the VSAM or OSAMstructure, or both, in the coupling facility failed. TheDATA part of the message defines the reason for thefailure.aa

The place code, which identifies where the errorwas found. aa can have the following values:Code (hex)

Meaning




bbbbbbbbThe return code from the last service started. Seez/OS MVS Programming: Sysplex Services Reference(SA22-7618) for the values of this code.

ccccccccThe associated reason code. See z/OSMVS Programming: Sysplex Services Reference(SA22-7618) for the values of this code.

ddeeffggthe associated flag bytes.

dd can have the following values:Code (hex)

Meaning80

Invalid function was requested.40

Connection to the OSAM structure failed.20

Too few OSAM buffers were returned duringconnection to the OSAM structure.

10Connection to the VSAM structure failed.

08Attempt to pass connection data to VSAM fordata shared resource pool failed.

04Attempt to pass connection data to VSAM forindex shared resource pool failed.



ee can have the following values:Code (hex)

Meaning80

A dummy PST was obtained during couplingfacility services initialization or execution.

40Connection to the OSAM structure wassuccessful.

20Disconnection from the OSAM structure wassuccessful.

10Connection to the VSAM structure wassuccessful.

08Disconnection from the VSAM structure wassuccessful.

ff can have the following values:Code (hex)

Meaning80

A request was received to stop data sharingbecause coupling facility services initializationfailed.

gg can have the following values:Code (hex)

Meaning80

A read-and-register operation for the OSAMbuffer failed.

20Buffer invalidation for the OSAM buffer failed.

System actionAlthough the IMS attempt to disconnect from thecoupling facility failed, data sharing was successfullystopped.

Programmer responseSee z/OS MVS Programming: Sysplex ServicesReference (SA22-7618) for error return and reasoncodes that identify the cause of the failure.



DFS3384I DATA SHARING STOPPED

ExplanationData sharing was successfully stopped. Data sharingstops under these circumstances:

• Connection to the coupling facility is lost.• Rebuild of the coupling facility fails.• Coupling facility initialization fails.


System actionRegardless of whether the connection was lost foran OSAM or VSAM structure, if both structures werespecified on the CFNAMES control statement, datasharing is stopped for both and connection to bothstructures is lost. If only one of the structures wasspecified, the other can continue data sharing usingthe notify protocol.


DFS3385I DUPLICATE CF STRUCTURE NAMESPECIFIED

ExplanationDuplicate coupling facility structure names werespecified in the CFNAMES control statement. Structurenames for the IRLM, OSAM, and VSAM structures mustall be different when specified.


Programmer responseCorrect the CFNAMES control statement, and resubmitthe job.



DFS3386I OSAM CF CACHING RATIO =ddd:eeer

ExplanationA coupling facility structure was defined for OSAM.The values specified for ddd and eee representthe coupling facility directory-to-element ratio. Thedirectory-to-element ratio is active for the issuingIMS. These values might be used to configure theOSAM structure. The ratio values active for the firstIMS that connects to the coupling facility establishesthe directory-to-element ratio. Other IMS regionsconnecting to the same structure will use the structurepreviously configured.

The value represented by r indicates whether a defaultratio or an externally-specified ratio is active. r has thefollowing values:1

The CFOSAM= keyword on the CFNAMESstatement did not specify the directory-to-elementratio. IMS supplies a default ration of 999:1.

2The directory-to-element ratio was specified withthe CFOSAM= keyword and is active.

3The directory-to-element ratio was specified withthe CFOSAM= keyword, but defines an incorrectratio and cannot be used. The result of dividingthe element value by the directory value must notexceed the maximum number of 16 elements. Theratio IMS provided is used instead of the externallyspecified ratio.

4The element portion of the directory-to-elementratio as specified by the CFOSAM= keyword is zero.The resultant ratio becomes 1:0. This ratio causesthe OSAM structure to be configured for directory-only processing. No data elements will be availablefor data caching.

System actionIMS initialization processing continues. The ratiospecified is active for the issuing IMS.

Programmer responseNo response is required unless the directory-to-element ratio used to configure the OSAM structure isnot the ratio you want. In this case, specify or changethe directory and element values on the CFNAMESstatement and restart the IMS sysplex.

DFS3387I DUPLICATE xxxxxx KEYWORDSPECIFIED FOR CFNAMES

ExplanationA keyword on the CFNAMES control statement(CFIRLM, CFOSAM, or CFVSAM) was specified morethan once. Each keyword can only be specified once.

System actionThe duplicate keyword is ignored, and the rest of thestatement is bypassed.



Programmer responseSee member DFSVSMxx in IMS system definitioninformation. Verify the CFNAMES control statement,and make appropriate changes if necessary.


Related referenceDFSVSMxx member of the IMS PROCLIB dataset (System Definition)Related information“IMS problem determination” on page 11IMS messages and codes problemdetermination is accomplished by usingprocedures established by IBM.

DFS3388I ALL CF KEYWORDS AREREQUIRED ON CFNAMES CARD

ExplanationAll keywords (CFIRLM, CFOSAM, and CFVSAM) mustbe specified on the CFNAMES control statement. Allkeywords must be specified even if their respectivestructures are not to be used.

System actionIMS terminates with 0430.

Programmer responseFix the CFNAMES control statement, and resubmit thejob.



DFS3389I MISMATCH - xxxxyyyyyyyyyy zzzzzzzzzzzzzzzz ++wwwwwwwwwwwwwwww

ExplanationThe IDENTIFY request to the IRLM failed. The IRLMdetected a mismatch between one of the following:

• The coupling facility structure name it was using andthe one specified in the IDENTIFY request

• The DBRC RECON time stamp it was using and theone specified in the IDENTIFY request


Is one of the following:

OSAMVSAMIRLMMADSIOT

yyyyyyyyyyIs one of the following:CFNAME++

Indicates a coupling facility structure namemismatch

DBRC RECONIndicates a DBRC RECON time stampmismatch

MADSIOFUNCIndicates a MADSIOT function specificationmismatch

zzzzzzzzzzzzzzzzThe structure name specified on the CFNAMEScontrol statement or blanks if the mismatchinvolved the DBRC RECON time stamp.

wwwwwwwwwwwwwwwwThe structure name the IRLM has in use or blanksif the mismatch involved the DBRC RECON timestamp.


Programmer responseVerify that all IMS subsystems sharing a couplingfacility specify the same names to the IRLM for anyOSAM, VSAM, or IRLM structure that was used. Allsharing subsystems must also use the same RECONdata set.



DFS3390I NO CF CONNECTION EXISTS. /EREBACKUP NOT ALLOWED.

ExplanationThe /ERE command entered on the XRF alternatesubsystem was rejected. This is because connection tothe coupling facility did not exist when the commandwas processed.


http://www.ibm.com/support/knowledgecenter/SSEPH2_15.1.0/com.ibm.ims15.doc.sdg/ims_dfsvsmxx_proclib.htm#ims_dfsvsmxx_proclib

http://www.ibm.com/support/knowledgecenter/SSEPH2_15.1.0/com.ibm.ims15.doc.sdg/ims_dfsvsmxx_proclib.htm#ims_dfsvsmxx_proclib



System actionThe /ERE BACKUP command is rejected untilconnection to the coupling facility is established.

Programmer responseRetry the /ERE BACKUP command when the couplingfacility connection is established.



DFS3391I CFNAMES SPECIFIED BUT IRLM ISNOT USED

ExplanationThe CFNAMES control statement was specified in theDFSVSMxx member of IMS.PROCLIB or in a data setwith ddname DFSVSAMP, but IRLM is not present forthis execution.

System programmer responseMake sure that IRLM is used during this execution.

Certain IMS utilities might not require IRLM; in thosecases, this message can be ignored.

ModuleDFSTRA00, DFSXRLM0

DFS3392W DL/I CF DATACACHING INOPERATIVE FORNNNNNNNNNNNNNNNN

ExplanationData caching has been disabled for the OSAMstructure named NNNNNNNNNNNNNNNN. Thissituation occurred because the IMS that connectedto the CF structure first established a non-cachingenvironment.

System actionIMS continues running without DL/I data caching.

System programmer responseEnsure that all IMS data sharing subsystems, whetherBatch or Online, use the same structure and CachingOptions (CO) when using OSAM DL/I Data Caching(ODC). These options are defined in either theDFSVSMxx PROCLIB members for Online, or in theDFSVSAMP DD cards for Batch with the CFNAMES andIOBF statements.

Failure to ensure structure consistency across IMSsubsystems can result in data integrity or performanceproblems.

If all IMS subsystems are running with IMS Version6.10 or later, IMS attempts to use the structurewith the characteristics defined by the IMS thatconnected first. A subsequent IMS renders its ownODC inoperative when it detects, during connection,that the structure has no data elements for caching.

If you run IMS Version 6.10 subsystems withIMS Version 5.10 subsystems, the earlier versionof IMS must connect to the structure first. ODCwas not introduced until IMS Version 6.10, andIMS Version 5.10 cannot access cached data. Dataintegrity problems can result from different IMSsubsystems using different copies of IOBF statementsin DFSVSMxx/DFSVSAMP.

Problem determination1, and save a copy of all DFSVSMxx or DFSVSAMPstatements for all IMS sharing subsystems.


DFS3394W OSAM/VSAM CF STRUCTURENAME IS SPECIFIED WITH NOIOBF/VSRBF

ExplanationIn DFSVSAMP or DFSVSMxx, the structure namefor OSAM, VSAM, or both was specified but therewas no IOBF statement, VSRBF statement, or bothrespectively.

System actionIn the online environment, the presence of an OSAMstructure name in the CFNAMES statement requiresan IOBF statement to pass the number of buffersto the IXLCONN macro. In batch, however, the IOBFstatement is not required because IMS defaults to fourbuffers. For VSAM, the presence of a VSAM structure


name in the CFNAMES statement always requires aVSRBF statement to pass the number of buffers to theIXLCONN macro.

Programmer responseReview the CFNAMES statement in DFSVSAMP orDFSVSMxx and the corresponding IOBF statements,VSRBF statements, or both.

ModuleDFSDMAW0

DFS3395I AUTOMATIC IMPORT STARTEDFROM xxxxxxxxxxxxxx

ExplanationAutomatic import has started. Valid values forxxxxxxxxxxxxxx are:MODBLKS

Indicates that the resource definitions are to beimported from the MODBLKS data set.

RDDSDSN=dsnameIndicates that the resource and descriptordefinitions are to be imported from a resourcedefinition data set (RDDS). In the message text,dsname identifies the name of the RDDS.

REPOSITORY REPOTYPE=repotypeREPONAME=reponame

Indicates that Resource Manager (RM) isconnected to the IMSRSC repository and that theresource definitions are to be imported from therepository. repotype indicates the repository typeand reponame indicates the repository name. Theonly valid value for repotype is IMSRSC.

If automatic import is from the repository and therepository is empty, IMS issues the DFS4405Wmessage and another DFS3395I message toindicate where the resource definitions areimported from: RDDS or MODBLKS.



Module:DFSIP000, DFSIP300, DFSRRSC0

DFS3396I AUTOMATIC IMPORT COMPLETED,RC=rc

ExplanationAutomatic import has completed. The return codes,indicated by rc, are as follows:Codes

Explanation0

All resource and descriptor definitions weresuccessfully imported.

4All resource and descriptor definitions wereimported, but one or more resources or descriptorscould not be initialized completely. You hadspecified IMPORTERR=CONTINUE in the DFSDFxxxPROCLIB member.



Module:DFSRIMP0

DFS3397E AUTOMATIC IMPORT FAILED,RC=rc

ExplanationAutomatic import failed. rc indicates the reason for thefailure. The return code values are as follows:Codes

Explanation4

An I/O error occurred while trying to access aresource definition data set (RDDS).

8An error occurred trying to obtain a 64-bit buffer.

12None of the RDDSs that you defined containexported data.

32An error occurred trying to read the resourcedefinitions from the IMSRSC repository.

40All resource and descriptor definitions wereimported, but one or more resources or descriptorscould not be initialized due to an error in thedefinition. You had specified IMPORTERR=ABORTin the DFSDFxxx PROCLIB member.

44No resources were imported from the IMSRSCrepository for one of these reasons:


• The repository is empty andAUTOIMPORT=REPO was specified. The IMScold start continues with no resources imported.

• There was an error processing resourcedefinitions read from the IMSRSC repository.

Action is taken based on IMPORTERR=specification.

System actionIf an error occurred trying to access a system resourcedefinition data set and you had RDDSERR=ABORTspecified in the DFSDFxxx PROCLIB member, IMSterminates with a 3368 abend.

If IMS detected an error with a resource or descriptordefinition and you had IMPORTERR=ABORT specifiedin the DFSDFxxx PROCLIB member, IMS terminateswith a 3397 abend.

If the error occurred when trying to read the resourcedefinitions from the IMSRSC repository, see theDFS4401E message issued before this message fordetails on the error. If you had REPOERR=ABORTspecified in the DFSDFxxx PROCLIB member, IMSterminates with a 3368 abend.

Programmer responseTo identify the cause of an I/O error, check anyDFS3368E messages that were issued before thismessage. If none of the RDDSs contain exporteddata ensure automatic export is enabled. To identifyresources that could not be initialized because of anyerrors in definition, check any DFS3423E messagesthat were issued before this message.

To identify the cause of the repository error, check theDFS4401E message issued before this message.

Module:DFSIP000, DFSRIMP0, DFSIP300

Related information“DFS3368E” on page 942ERROR PROCESSING RDDS, RC=rc, RDDSDSN=dsname“DFS3423E” on page 962RESOURCE ERROR TYPE=resourcetypeSERVICE=servicename FUNC=functionRC=returncode NAME=resourcenameMODULE=modulename“DFS4401E” on page 1209RM requestname ERROR, RC=rc RSN=rsnERRORTEXT=errortextIMS abend 3368

DFS3398E LOAD FAILED FOR TRANSACTIONINPUT EDIT ROUTINE xxxxxxxx,RC=rc

ExplanationAn input edit routine that was defined for one or moretransactions could not be loaded.


Identifies the name of the routinerc

Return code from the IMODULE LOAD call(DFSMODU0). For these return codes, see theIMODULE return code information.

System actionTransactions defined with the input edit routine arestopped for queuing and scheduling, and given aNOTINIT status. If automatic import is in progress andIMPORTERR=ABORT was specified in the DFSDFxxxPROCLIB member, the automatic import process isterminated and IMS terminates with a 3397 abend.

If automatic import is in progress andIMPORTERR=CONTINUE was specified, IMS continuescold start processing.


Programmer response:Make sure that the transaction input edit routine existsin one of the IMS.SDFSRESL concatenated data sets.After you have identified the cause of the load failureand corrected it, you can issue an UPDATE TRANSTART(Q,SCHD) command to start the transaction forqueuing and scheduling. IMS attempts to load the editroutine module. If the module is successfully loaded,the NOTINIT status is reset and the transaction isstarted for queuing and scheduling.

Module:DFSIP000, DFSRTR20, DFSRRSC0


DFS3399I AUTOMATIC IMPORT IS ENABLEDFROM xxxxxxxx

ExplanationAutomatic import processing is enabled. xxxxxxxxidentifies the data source from which the resource anddescriptor definitions are to be imported. xxxxxxxx canbe one of the following values:




MODBLKSRDDSREPOSITORY

The DFS3399I message is not issued during IMSinitialization if AUTOIMPORT=AUTO is specifiedin the DFSDFxxx PROCLIB member, along withthe REPOSITORY section and the REPOSITORY=statement for the IMSRSC repository. The DFS3409Imessage is issued instead of DFS3399I during IMSinitialization because it is not yet determined whetherIMS has connected to the repository or if therepository has stored resource definitions for the IMS.

During cold start, IMS issues the DFS3399I andDFS3395I messages to indicate where the resourcedefinitions are read for cold start. DFS3395I indicateswhether automatic import is enabled from therepository, MODBLKS, or RDDS. If the automaticimport is from the repository and the repositoryis empty, IMS issues the DFS4405W message andanother DFS3395I message to indicate where theresource definitions are imported from: RDDS orMODBLKS.



Module:DFSRDD10, DFSDFN10, DFSDFN00, DFSIP300

DFS3400I RETURN CODE rrrr FROMRACROUTE MACRO FUNCTIONffffffff FOR CLASS cccccccc

or

RACLIST FAILED, AUTHORIZATION RACROUTERETURN CODES aa, bb, cc, dd RACLIST RETURNCODES ee, ff, gg, hh RACLIST REASON CODES ii, jj,kk, ll.

ExplanationDuring online change prepare processing, a nonzeroreturn code was found for at least one of the fourclasses associated with the authorization function.This message does not indicate a failure of the prepareprocess. The codes have the following meanings:

CodesExplanation

aaRACROUTE return code for DATABASE class.

bbRACROUTE return code for SEGMENT class.

ccRACROUTE return code for FIELD class.

ddRACROUTE return code for OTHER class.

eeRACLIST return code for DATABASE class.

ffRACLIST return code for SEGMENT class.

ggRACLIST return code for FIELD class.

hhRACLIST return code for OTHER class.

CodesExplanation

iiRACLIST reason code for DATABASE class.

CodesExplanation

jjRACLIST reason code for SEGMENT class.

kkRACLIST reason code for FIELD class.

llRACLIST reason code for OTHER class.

System actionOnline change prepare processing continues.




DFS3401I RACF NOT AVAILABLE

ExplanationA /MODIFY PREPARE command specified RACF orALL and the RACF product was not currently active inIMS.


DFS3402W NO bbbbb IN THE INACTIVELIBRARY

ExplanationControl blocks were missing from the inactivelibrary during /MODIFY PREPARE or INITIATE OLCPHASE(PREPARE) processing.

The field bbbbb is a particular IMS control block typesuch as DMBs from ACBLIB or DDIRs from MODBLKS.

System action/MODIFY PREPARE or INITIATE OLCPHASE(PREPARE) processing terminates.

Programmer responseInclude the database definitions in the library by usingthe Online Change Utility. Be sure that the library isAPF authorized. IMS requires at least one DMB inACBLIB for an IMS DB/TM system.

DFS3403W AUTOMATIC IMPORT ISDISABLED, RC=rc

ExplanationAutomatic import processing is disabled. rc indicatesthe reason automatic import is disabled. Possiblereasons are as follows:Codes

Explanation4

You had specified AUTOIMPORT=NO.8

You specified AUTOIMPORT=AUTO, but you didnot have any resource definition data sets (RDDS)defined and no MODBLKS data set exists. If IMS is

defined with the IMSRSC repository, the repositoryis empty.

12Two or more RDDSs are defined, but the RDDSs areempty and no MODBLKS data set exists.

16RDDS errors were encountered during RDDSinitialization preventing automatic import fromoccurring from an RDDS. Message DFS3368identifies the RDDSs and their associated errors.

If you specify AUTOIMPORT=RDDS orAUTOIMPORT=AUTO in the Dynamic_Resourcessection of the DFSDFxxx IMS.PROCLIB memberand IMS is started cold (/NRE CHKPT 0 or /ERECOLDSYS), the value specified for the RDDSERR=parameter in the Dynamic_Resources section ofthe DFSDFxxx IMS.PROCLIB member determinesthe action that IMS takes.

When you specify RDDSERR=NOIMPORT, IMS isrestarted with a cold start without importing anystored resources.

When you use RDDSERR=ABORT, IMS terminatesabnormally with an IMS abend 3368 with an RC=4.


Programmer responseIf you do not want automatic import processing, noaction is necessary.

If you want automatic import processing, use thereturn code rc to identify the reason automatic importwas disabled. If necessary, correct the specificationerror in the DFSDFxxx IMS.PROCLIB member. If theresource definition data sets (RDDS) are expectedto contain exported data, make sure that automaticexport is enabled. If you intended to import definitionsfrom a MODBLKS data set, make sure that theMODBLKS DD statement exists in your IMS controlregion JCL.

Related information“DFS3368E” on page 942ERROR PROCESSING RDDS, RC=rc, RDDSDSN=dsnameAbend 3368

DFS3404I EXPORT COMMAND COMPLETEFOR xxxx, DSN=dsname



ExplanationThe EXPORT command completed.


Indicates whether the EXPORT command wascompleted for all of the specified resource anddescriptor definitions. xxxx can be ALL, SOME orNONE.

dsnameIndicates the name of the resource definition dataset (RDDS) to which the resource and descriptordefinitions were exported.


Programmer responseIf the EXPORT command did not complete successfullyfor all the resource and descriptor definitions youspecified, determine the cause of the error and reissuethe EXPORT command.

Module:DFSXP100

DFS3405I IMPORT COMMAND COMPLETEFOR xxxx, DSN=dsname

ExplanationThe IMPORT command completed.


Indicates whether the IMPORT command wascompleted for all of the specified resource anddescriptor definitions. xxxx can be ALL, SOME orNONE.

dsnameIndicates the name of the resource definition dataset (RDDS) from which the resource and descriptordefinitions were imported.


Programmer responseIf the IMPORT command did not complete successfullyfor all of the resource and descriptor definitions thatyou specified, determine the cause of the error andreissue the IMPORT command.

Module:DFSIP100

DFS3406I cmd COMMAND COMPLETE FORALL, REPOTYPE=repotype,

REPONAME=reponame

ExplanationThe command identified cmd in the message hascompleted.

In the message text:cmd

Indicates the command verb that is processed.cmd can be DELETE, EXPORT, or IMPORT.

reponameIndicates the 44-byte IMSRSC repository namefrom which the resource definitions are processed.

• For DELETE, this name indicates the repositoryfrom which the stored resource definitions aredeleted.

• For EXPORT, this name indicates the repositoryto which the runtime resource definitions areexported.

• For IMPORT, this name indicates the repositoryfrom which the stored resource definitions areimported.

repotypeIndicates the 8-byte repository type to which RM isconnected. The only supported value is IMSRSC.

System actionIMS continues processing



Module:DFSIP100, DFSXP100, DFSDEL00

DFS3407E cmd COMMAND COMPLETEFOR NONE, REQUEST=rqstnameRC=retcode, RSN=rsncode,ERRORTEXT=errtext,MBR=mbr, REPOTYPE=repotype,REPONAME=reponame

or

cmd COMMAND COMPLETE FOR var1,REPOTYPE=repotype, REPONAME=reponame


ExplanationThe specified command was completed with an error.The rqstname, retcode, rsncode, errtext, and mbrvalues are returned only if the error is due to an RMrequest error.

In the message text:cmd

Indicates the command verb that is processed.cmd can be DELETE, EXPORT, IMPORT, or QUERY.

var1Can be SOME or NONE.

reponameIndicates the 44-byte IMSRSC repository namefrom which the resource definitions are processed.

• For DELETE, this is the repository namefrom which the stored resource definitions aredeleted.

• For EXPORT, this is the repository name to whichthe runtime resource definitions are exported.

• For IMPORT, this is the repository namefrom which the stored resource definitions areimported.

• For QUERY, this is the repository name fromwhich the stored resource definitions are queriedfrom.

repotypeIndicates the repository type. The valid value forrepotype is IMSRSC.

rqstnameIndicates the RM request that was not successful.rqstname can be:

• CSLRPDEL for the DELETE command• CSLRPUPD for the EXPORT command• CSLRPQRY for the IMPORT or QUERY command

retcodeIndicates the RM request return code. See theCSLRRR or CSLSRR macro for the description ofthe return code.

rsncodeIndicates the RM request reason code. See theCSLRRR or CSLSRR macro for the description ofthe reason code.

errtextIndicates the error text from the repositoryrequest. The error text can be null or six words oftext.

mbrIndicates the type of request in error. The valuecan be either LST or RSC.

System actionIMS continues processing

Operator responseDetermine the reason for the failed request. Try thecommand again after the error is resolved.


DFS3409I AUTOIMPORT=AUTODETERMINATION IS DEFERRED

ExplanationThe DFS3399I message is not issued during IMSinitialization if AUTOIMPORT=AUTO is specified inthe DFSDFxxx member, along with the REPOSITORYsection and the REPOSITORY= statement for theIMSRSC repository. The DFS3409I message is issuedinstead of DFS3399I during IMS initialization becauseit is not yet determined whether IMS has connectedto the repository or whether the repository has storedresource definitions for the IMS.

During cold start, IMS issues the DFS3399I andDFS3395I messages to indicate where the resourcedefinitions are read for cold start. The DFS3395Imessage indicates whether automatic import isenabled from the repository, MODBLKS, or RDDS. Ifautomatic import is enabled from the repository andthe repository is empty, IMS issues the DFS4405Wmessage and another DFS3395I message to indicatewhere the resource definitions are to be importedfrom: RDDS or MODBLKS.

System programmer responseModify any automation programs that expect theDFS3399I message during IMS initialization.

Module:DFSRDD10

Related information“DFS3395I” on page 951AUTOMATIC IMPORT STARTED FROMxxxxxxxxxxxxxx“DFS3399I” on page 952AUTOMATIC IMPORT IS ENABLED FROMxxxxxxxx

DFS3410I DATA SETS USED AREDDNAME acblib-name format-name 'MODBLKS-name' (time/datestamps if they exist)


ExplanationThe indicated ddnames are the ones which are usedfor IMS online processing. If time/date stamps exist,they indicate when the last successful INITIATEOLC PHASE(PREPARE) or /MODIFY PREPAREand INITIATE OLC PHASE(COMMIT) or /MODIFYCOMMIT commands were issued.

In the message text:acblib-name

The active IMSACB DD in the IMS JCL, whichidentifies the active ACBLIB library. The acblib-name ddname is either IMSACBA or IMSACBB.

Note: If the IMS management of ACBs is enabledin this IMS system by the specification ofACBMGMT=CATALOG in the DFSDFxxx PROCLIBmember, disregard the ACB library ddname. IMSsystems that manage ACBs do not use either theIMSACBA or IMSACBN ddnames for any libraries.

format-nameThe active FORMAT DD in the IMS JCL, whichidentifies the active MFS format library. Theformat-name is either FORMATA or FORMATB. Ifthis system is DBCTL, format-name is blank.

modblks-nameThe active MODBLKS DD in the IMS JCL,which identifies the active MODBLKS library. Themodblks-name is either MODBLKSA or MODBLKSB.

modblks-name can be blank. If modblks-name isblank, then MODBLKS DD is not defined in the IMSJCL. The MODBLKS DD statements are optionalwhen dynamic resource definition is enabled.



DFS3411X UNABLE TO OPEN THE MODSTATDATA SET

ExplanationIMS encountered an error trying to open the data setwith the ddname of MODSTAT. Either the MODSTATDD statement does not exist, or the operating systemencountered an I/O error during open processing.


Programmer responseProvide the missing DD statement or create the dataset, or both, referenced by the MODSTAT DD statementusing the INITMOD procedure and run IMS. SeeIMS system definition information for the INITMODprocedure.


DFS3412 ERROR READING MODSTAT DATASET

Explanation:An I/O error was detected while attempting to read theMODSTAT data set.


Programmer responseReconstruct the MODSTAT data set, using theINITMOD procedure with the ddnames indicated onthe last successful DFS3410I, or DFS3499I message,and run IMS. For a description of the INITMODprocedure, see the IMS system definition information.For the appropriate recovery actions in an XRFenvironment, see the information about ExtendedRecovery Facility. If this message is issued by the FastDatabase Recovery region, terminate the active IMSand reconstruct the MODSTAT data set. Then restartIMS, and start the Fast Database Recovery regionagain.

Related conceptsExtended Recovery Facility Overview (SystemAdministration)Related informationIMS abend 3412

DFS3413X INVALID CONTENTS IN THEMODSTAT DATA SET

ExplanationThe MODSTAT data set contains invalid data.

The MODSTAT data set must contain the followingfields in such order:

modifyid,MODBLKSx,IMSACBx,FORMATx

Values must be separated by commas, with noimbedded blanks.modifyid

The MODSTAT identifier number, which is variablelength with no limit. This field is usually initializedto 1.



http://www.ibm.com/support/knowledgecenter/SSEPH2_15.1.0/com.ibm.ims15.doc.sag/system_recovery/ims_xrf_bigover.htm#ims_xrf_bigover

http://www.ibm.com/support/knowledgecenter/SSEPH2_15.1.0/com.ibm.ims15.doc.sag/system_recovery/ims_xrf_bigover.htm#ims_xrf_bigover


MODBLKSxThe ddname for the active MODBLKS data set,either IMS.MODBLKSA or IMS.MODBLKSB data setthat contains the IMS system definition output. .This field is usually initialized to MODBLKSA. Youmust define the MODBLKSx field even for an IMSsystem that does not define the MODBLKS datasets.

IMSACBxThe possible values for the data set suffix xare Aand B.

FORMATxThe possible values for the data set suffix xare Aand B. This field is usually initialized to FORMATA.You must define the FORMATx field even for anIMS DBCTL environment that does not use theFORMAT libraries.

Note: For more information on the fields, seeInitializing the IMS.MODSTAT data set (SystemUtilities).

If at least one online change has been successfullycommitted, these fields are followed by an onlinechange prepare timestamp and an online changecommit timestamp in the following format: YYYYDDDHHMMSS offset. In the timestamp:

• YYYY - the year• DDD - the Julian day• HH - the hour• MM - the minutes• SS - the seconds• offset - the UTC time offset in the format -xx:xx or

+xx:xx

Note: The timestamps, if applicable, must be in thecorrect format to avoid IMS restart failure.

The following example shows the values of a validMODSTAT data set:

108,MODBLKSA,IMSACBA,FORMATA 2016099 191653 -07:00 2016100 041751 -07:00


Programmer responseCheck the MODSTAT data set content to ensurethat the modifyid, the online change fields and thetimestamps are in the correct format.

If this message is issued because of an error in themodify identifier number or the online change fields in

the MODSTAT data set, use the INITMOD procedure tocorrect the error and retry.

If this message is issued because of an error in thetimestamp in the MODSTAT data set, use the TimeSharing Option (TSO) to correct the error and retry.

In other cases, reconstruct the MODSTAT data set,using the INITMOD procedure with the ddnamesindicated on the last successful DFS3410I, orDFS3499I message, and run IMS.

Related referenceInitializing the IMS.MODSTAT data set (SystemUtilities)Related informationIMS abend 3413DFS3410I (Messages and Codes)DFS3499I (Messages and Codes)

DFS3414X NOT ENOUGH STORAGE TOINITIALIZE

ExplanationIMS was unable to allocate storage.


Programmer responseIncrease the amount of storage available to the region,and run IMS.


DFS3415X LIBRARY xxxxxxxx IN USE BYANOTHER OS/VS TASK

ExplanationThe library associated with ddname xxxxxxxx couldnot be used because it was already in use by anotherOS/VS task.


Programmer responseWait until the other task has released the library, andrun IMS.



http://www.ibm.com/support/knowledgecenter/SSEPH2_15.1.0/com.ibm.ims15.doc.sur/ims_dfsuocu0initialize.htm#ims_dfsuocu0initialize





http://www.ibm.com/support/knowledgecenter/SSEPH2_15.1.0/com.ibm.ims15.doc.msgs/msgs/dfs3410i.htm#dfs3410i




DFS3416X OPEN FAILED FOR LIBRARYxxxxxxxx

ExplanationThe library associated with ddname xxxxxxxx could notbe opened at IMS initialization time.


Programmer responseDetermine why open failed, and then run IMS.


DFS3417E CICS IPIC ERROR ONACTIVE ISC TCP/IPSESSION SENSE=sensecodeTEXT=cicsmsgnm

ExplanationDuring the exchange of messages between IMS andIBM CICS Transaction Server for z/OS on an active ISCTCP/IP session, IMS received an IP interconnectivity(IPIC) conversation error (IS7) message from CICS.

The sense code indicates the type of error. If CICSpassed an error message ID to IMS, the message ID isdisplayed in the TEXT field.

In the message text:cicsmsgnm

A nine-character field that contains the CICS errormessage number, if CICS returned it to IMS. Thistext is the CICS error message that was issued tothe CICS job log.

sensecodeA 4-byte code that indicates the nature of theerror. These codes are issued by CICS.080F0983

Access denied.080F6051

Security not valid.08240000

Conversation identifier no longer valid; the taskwas backed out in CICS.

08390000The transaction attach was rejected; the IMSsystem is quiescing.

084C0000The transaction attach was rejected;transaction is known but disabled in CICS.

08640001The mirror transaction abended in CICS.

1008600BCICS system error.

10086021The transaction attach was rejected;transaction is unknown to CICS.

System actionFor sense code 08640001, IMS dequeues the outputmessage. The session remains active.

For all other sense codes, IMS puts the outputmessage back on the message queue and terminatesthe session.

IMS continues processing.

System programmer responseIn cases where IMS puts the output message back onthe message queue and terminates the session, beforeyou attempt to reestablish the session, determine thecause of the problem and correct it to prevent thesame error from occurring again.

For more information about the sense codes, seethe CICS documentation or consult with your CICSadministrator. Look up the CICS error message in theCICS documentation.

Module:DFSIPIC0

Related tasksISC support for TCP/IP (Communications andConnections)Related referenceQUERY IMSCON TYPE(PORT) command(Commands)CICS: ISMF - ISC IP Message FormatsCICS messages

DFS3418X UNABLE TO DELETE MODULExxxxxxxx

ExplanationThe modulexxxxxxxx could not be deleted from theactive MODBLKSA(B) data set.


Programmer responseThis is probably an IMS internal error.







http://www-01.ibm.com/support/knowledgecenter/SSGMCP_5.2.0/com.ibm.cics.ts.doc/dfhs4/DFHISMFK.html

http://www-01.ibm.com/support/knowledgecenter/SSGMCP_5.2.0/com.ibm.cics.ts.messages.doc/DFHmessages.html



DFS3419X UNABLE TO LOAD MODULExxxxxxxx RC=xx

ExplanationThe module xxxxxxxx could not be found in the activeMODBLKSA(B) data set, or the data set was not APF-authorized. Alternatively, this message indicates thatthere was not enough virtual storage available in theIMS control region. For a description of the IMODULELOAD return codes, see IMS system services returncode information.


Programmer responseDetermine why the module is missing, and run IMS.Ensure that the active MODBLKSA(B) data set is APF-authorized.

Related referenceIMS system services return codes (Messagesand Codes)Related informationIMS abend 3419

DFS3420X RESIDUAL MESSAGES EXIST FORDELETED TRANSACTIONS

ExplanationIMS detected existing messages for a transaction thatdoes not exists. The transaction definition does notmatch the message activity indicated on the IMSsystem log.


Programmer responseThe log data set is inconsistent with the definition inthe MODBLKS data set. The SMB blocks, which wereloaded from MODBLKS during initialization, are notthe same as those which were last active during theprior IMS execution. This situation can occur if the

MODSTAT data set was reconstructed specifying anincorrect ddname of the active MODBLKS data set.It can also occur by changing the contents of theMODBLKS data set while IMS was not active. Use thesame copy of MODBLKS that was in use during the lastIMS execution, and restart IMS with a /ERE from thelast checkpoint that was taken with a memory dumpQ.


DFS3421X UNABLE TO FIND xxxx CONTROLBLOCK NAMED yyyyyyyy.

ExplanationThis message is issued during an IMS cold start ifa PDIR or RCTE cannot be found because either noPDIRs exist or no RCTEs exist. xxxx is the control blocktype, PDIR or RCTE. yyyyyyyy is set to DFSHSHT toindicate the internal resource control block hash tableis empty.

These blocks can be loaded from MODBLKS, or usingan automatic import from the resource definition dataset (RDDS).

System actionIMS issues an abend 3421 following messageDFS3421X. IMS terminates abnormally.

Programmer responseIf dynamic resource definition (DRD) is not enabled,check that IMS.MODBLKSx contains the correctcontrol block modules, DFSSMB0x, DFSPDIRx,DFSDDIRx, and DFSRCTEx. If these checks do notindicate a problem, contact IBM Software Support forassistance.

If DRD is enabled, and resource definitions are beingimported from the IMS.MODBLKSx data set during acold start, check that IMS.MODBLKSx contains thecorrect control block modules, DFSSMB0x, DFSPDIRx,DFSDDIRx, and DFSRCTEx. If resource definitions arebeing imported from an RDDS during a cold start,check that the correct RDDS is being used and thatthe RDDS has a complete set of resource definitions. Ifthese checks do not indicate a problem, contact IBMSoftware Support for assistance.









DFS3422X INSUFFICIENT STORAGE FORresource_type CONTROL BLOCKS.

ExplanationIMS was unable to acquire enough storage in therequired subpool. Subpool 231 (Common CSA/ECSA)is used for most resources; however, some resourcesuse subpools 0 or 251. These blocks might be a groupof control blocks loaded into an IPAGE from MODBLKS,or an individual resource that is dynamically created.

In the message text:resource_type

The resource type can be one of the following:DBBD

Database descriptor.DDIR.

Database.HSMB

Hash SMB. The SMB hash table is full. Thereare not enough hash table slots, including freepool slots, to add an SMB to the hash table.

PDIRProgram.

PGMDProgram descriptor.

RCNTRemote lterm block.

RSCXResource extension block.

RTCDRouting code descriptor.

RTCERouting code.

SMBTransaction resource.

TRNDTransaction descriptor.


System programmer responseFor all resource types except RCNT and RSCX, increasethe amount of storage in subpool 231.

If RSCX is the resource type, increase the amount ofstorage in subpool 0.

If RCNT is the resource type, increase the amount ofstorage in subpool 251.


Module:DBFRRT00, DFSCPDM0, DFSIINM0, DFSRDB00,DFSRMC00, DFSRPG00, DFSRTR00


DFS3423E RESOURCE ERRORTYPE=resourcetypeSERVICE=servicenameFUNC=function RC=returncodeNAME=resourcenameMODULE=modulename

ExplanationIMS encountered an error initializing a resourcecontrol block.

In the message test:resourcetype

The resource type can be one of the following:

• DBBD – database descriptor• DDIR – database• LLB – Multiple Systems Coupling (MSC) logical

link control block• LNB – MSC logical link path (msname) control

block• MSCL – MSC logical link control blocks• MSCP – MSC physical link control blocks• PDIR – program• PGMD – program descriptor• RCNT – Remote logical terminal• RSCX – resource extension block• RTCD – routing code descriptor• RTCE – routing code• SMB – transaction• TRND – transaction descriptor

servicenameName of the service that encountered an error.Other than DFSBCB, the services are internal toIMS.



functionName of the service function that encountered anerror.

returncodeService return code. If the servicename is DFSBCB,see the DFSBCB return codes.

resourcenameName of the resource that encountered the error

modulenameName of the module that encountered the error

System actionIn some cases, IMS terminates abnormally with abend3423. In other cases, IMS continues processingwithout the use of the resource.

System programmer responseCheck whether your MODBLKS data set is generated atthe appropriate IMS release level. If you are startingan IMS that references a MODBLKS data set generatedat an older IMS release level, the mismatch usuallyresults in the DFS3423E message.

If the MODBLKS data set is generated at the sameIMS release level, copy the SYSLOG and IMS memorydump and contact IBM Software Support for help. Alsosave the servicename, function, returncode, and otherinformation from the message.

Module:DBFNRST0, DBFRRT00, DFSIP300, DFSRDB00,DFSRPG00, DFSRTR00

Related referenceDFSBCB return codes (Messages and Codes)Related informationIMS abend 3423

DFS3424I DFSINSX0 CREATEresourcetype ERRORRC=returncode RSN=reasoncodeCC=completioncodeNAME=resourcename

ExplanationThe DFSINSX0 user exit attempt to dynamically createa program or a transaction failed. The failure wascaused by an invalid attribute or attribute combination.Examples of attribute errors:

• The transaction has an invalid program name.• Fast Path transaction is defined as non-response

mode.• A transaction that was not defined as Fast Path

references a Fast Path program.

In the message text:resourcetype

The resource type can be one of the following:

PGM - application programTRAN - transaction

returncodeThe CREATE command return code. See the returnand reason codes table for the CREATE PGM orCREATE TRAN command.

reasoncodeThe CREATE command reason code.

completioncodeThe CREATE command completion code (ifapplicable).

resourcenameThe resource name of program or transaction thatencountered the error.

System actionThe program or transaction creation fails. IMS issuesmessage DFS064I indicating that the destination wasnot found or created.

System programmer responseCorrect the error in the DFSINSX0 user exit.The DFS3424I message provides the diagnosticinformation needed to determine the error.

Module:DFSPGS00, DFSTRS00

Related referenceCREATE PGM command (Commands)CREATE TRAN command (Commands)

DFS3425I PLEXPARM INIT VALUErrrrrrrr=vvvvvvvv OVERRIDDENWITH GLOBAL PLEXPARM VALUErrrrrrrr=vvvvvvvv

ExplanationThe PLEXPARM value for resource rrrrrrrr did notmatch the value in the Global Plex Parm entry. Thevalue from the Global Plex Parm entry was used.

In the message text:rrrrrrrr

The Global Plex Parm whose PLEXPARM value isoverridden with the value in the Global Plex Parmentry.

vvvvvvvvThe value of the Global Plex Parm.


http://www.ibm.com/support/knowledgecenter/SSEPH2_15.1.0/com.ibm.ims15.doc.msgs/compcodes/ims_dfsbcbretcodes.htm#ims_dfsbcbretcodes


http://www.ibm.com/support/knowledgecenter/SSEPH2_15.1.0/com.ibm.ims15.doc.cr/imscmds/ims_createpgm.htm#ims_cr1createpgm

http://www.ibm.com/support/knowledgecenter/SSEPH2_15.1.0/com.ibm.ims15.doc.cr/imscmds/ims_createtran.htm#ims_cr1createtran

System actionThe value from the Global Plex Parm entry is used forthe specified resource.


If the value for the specified resource does not matchwhat is wanted for the IMSplex, use the UPD IMS SETcommand to change the Global Plex Parm value.

Module:DFSGPM00

DFS3426A CTL REGION WAITINGCOMPLETION OF RM PROCESSpppppppp

ExplanationThe IMS control region initialization is waiting forthe IMS initiated Resource Manager (RM) processpppppppp to complete.

In the message text:pppppppp

The IMS initiated RM process on which the IMSinitialization is waiting. Possible values are:UPDIMS

IMS detected that an UPD IMS command is inprogress.

System actionIMS continues to wait until the process is completeor until there are no other active IMS systems in theIMSplex.

System programmer responseFor RM process UPD IMS, if a UPD IMS commandis currently in progress, wait for the command tocomplete. If a previous UPD IMS command did notcomplete because of an error condition, resolve theerror condition. Then use the CONTINUE option on thecommand to complete the previous command.

Module:DFSGPM00

DFS3427W RM REQUEST ERROR - PLEXPARMPARAMETERS NOT OBTAINEDFROM RM

ExplanationThe system could not read the PLEXPARM parametersfrom RM due to an error from the Resource Manager

(RM). The RM error return and reason codes arelisted in the DFS3308 issued before this message. Youcannot use the same IMS PLEXPARM values as thevalues in RM.


System programmer responseIf you want to ensure IMS and RM are in sync, take thefollowing action:

1. After IMS restart is complete, issue a QRY IMSTYPE(PLEXPARM) SHOW(ALL) command.

2. If the IMS and RM values in the QRY IMS outputare identical, no further action is required.

3. If there is a mismatch in the PLEXPARM valuesbetween IMS and RM from the QRY IMS commandoutput, the user can choose to:Option 1

Cancel or shut down IMS, fix the RM errorreported in the DFS3308 message, and restartIMS.

Option 2Take the following actions:

• If the RM value for PLEXPARM GSTSTRANis an N and the IMS value is a Y, issue aUPD IMS SET(PLEXPARM(GSTSTRAN(N)))command to ensure IMS is in sync with RM.

• If the RM value for PLEXPARM GSTSDB is anN and the IMS value is a Y, issue a UPD IMSSET(PLEXPARM(GSTSDB(N))) command toensure IMS is in sync with RM.

• If the RM value for PLEXPARM GSTSAREAis an N and the IMS value is a Y, issue aUPD IMS SET(PLEXPARM(GSTSAREA(N)))command to ensure IMS is in sync with RM.

• If the RM value for PLEXPARM GSTSTRANis a Y and the IMS value is an N, issue aUPD IMS SET(PLEXPARM(GSTSTRAN(Y)))command to ensure IMS is in sync with RM. Inaddition, issue a QRY TRAN SHOW(GLOBAL)command, and then issue the appropriateUPD TRAN SCOPE(ACTIVE) commands toensure that the IMS resources have samestatus as RM.

• If the RM value for PLEXPARM GSTSDB is a Yand the IMS value is an N, issue an UPD IMSSET(PLEXPARM(GSTSDB(Y))) command toensure IMS is in sync with RM. In additionissue a QRY DB SHOW(GLOBAL) command,and then issue the appropriate UPD DB


SCOPE(ACTIVE) commands to ensure thatthe IMS resources have same status as RM.

• If the RM value for PLEXPARM GSTSAREAis a Y and the IMS value is an N, issue aUPD IMS SET(PLEXPARM(GSTSAREA(Y)))command to ensure IMS is in sync with RM. Inaddition, issue a QRY AREA SHOW(GLOBAL)command, and then issue the appropriateUPD AREA SCOPE(ACTIVE) commands toensure that the IMS resources have samestatus as RM.

Module:DFSGPM00


DFS3428W THE TOTAL OTMA INPUTMESSAGES(TIB) HAVE REACHEDXX% OF THE GLOBAL LIMIT ZZZZ

ExplanationOTMA internally creates a transaction instance block(TIB) to track each active input message from allmembers. The YTIB will be freed or released afterOTMA completes the CM1 message processing orenqueues the CM0 message. This warning messageis intended to inform you that the total number ofTIBs from all the OTMA members is reaching themaximum limit, where xx represents 80, 85, 90, or95 percentages, and zzzz represents the global floodlimit specified from OTMA client descriptor or /STARTTMEMBER ALL INPUT command. With this warningmessage, there could be a potential OTMA globalmessage flood condition.

System actionIMS OTMA continues to process new input messagesfrom all the members until the maximum number ofmessages is reached.

System programmer responseDetermine whether:

• The dependent regions are active to process OTMAmessages.

• The remote program inserts back to the i/o PCB forOTMA messages.

• The OTMA clients are flooding IMS.

You might need to reroute OTMA input messages toa different IMS or stop the OTMA clients to preventthe IMS message flood condition. Make sure that the

IMS regions are started to run the OTMA transactions.You might need to contact the system programmer forassistance.

Module:DFSYMOM0

DFS3429E THE TOTAL OTMA INPUTMESSAGES(TIB) HAVE REACHEDTHE GLOBAL LIMIT ZZZZ

ExplanationThere are too many unprocessed OTMA messages inthe system. This is a severe message flood condition.All of the new OTMA transactions, including IMSsynchronous program switches, are rejected.

System actionIMS OTMA will reject any new input messages from allthe members until the flood condition is relieved.

System programmer responseDetermine whether:

• The dependent regions are active to process OTMAmessages.

• The remote program inserts back to the I/O PCB forOTMA messages.

• The OTMA clients are flooding IMS.

Make sure that the IMS regions are started to runthe OTMA transactions. You might need to contact thesystem programmer for assistance.

Module:DFSYMOM0

DFS3430I THE FOLLOWING MODIFICATIONSWILL OCCUR DURING /MODIFYCOMMIT: resource-type 8 charsresource-name 13 chars action 40chars

ExplanationThe indicated resources represent the modificationsthat are brought online during a subsequentsuccessful /MODIFY COMMIT command. Thismessage is generated only if you specified theoptional LTERM keyword. The resource-type (8characters), resource-name (13 characters) and action(40 characters) are preceded by blanks.resource-type

DDIR, DMB, AREA, FORMAT, PDIR, PSB, RCT, SMB


resource-nameName given to SYSDEF, formats with non-graphic symbols are converted to a 2-characterhexadecimal equivalent.

action

• ADDED• CHANGED• CHANGED (DSID CHANGED)• DELETED• NONE• NOT CHANGED (PDIR/PSB CHANGE ONLY)• REPLACED• SAME (DSI CHANGED)

Programmer responseIf the DSIDs have changed, enter the /DBR AREAcommand with keyword GLOBAL in a Block Level DataSharing environment. Unload the area and take animage copy. Remove the old DSID in the RECON dataset using a DELETE.DBDS command. Reinitialize thearea in the RECON data set using the INIT.DBDScommand. The INIT.DBDS command can fail if aduplicate DSID is found in the same DEDB. Use aspecific user-developed application program or OEMutility to reload the DEDB through the change systemdefinitions for the DEDB. Take an image copy after thereload process completes.

Module:DFSICV20

DFS3431 /MODIFY PROCESSING ALREADYACTIVE

ExplanationThis online change command (/MODIFY, /DISPLAYMODIFY is rejected because one of the followingsituations exists:

• Another online change command (/MODIFY,INITIATE OLC, TERMINATE OLC, or /DISPLAYMODIFY) is in progress

• IMS is already in an online change prepare statedue to a previous successful /MODIFY PREPARE orINITIATE OLC PHASE(PREPARE) command.

• If you are using global online change and a previousonline change command is taking far longer thanexpected, the online change command might behung due to an internal error. The only way toget out of this situation is to cancel the IMScommand master. Issue the query member type(IMS) command to find out which IMS is master ofthe online change phase.

• A CREATE DB or DELETE DB command that isadding a DEDB or deleting a DEDB is currently active.Try the /DIS MODIFY or the /MODIFY commandagain after the CREATE DB or DELETE DB hascompleted.


Operator responsePerform one of the following actions:

• If another online change command is in progress,wait for the online change command (/MODIFY or /DISPLAY MODIFY) to complete before entering thisonline change command.

• If IMS is already in an online change preparestate, terminate or commit the online change beforeattempting the /MODIFY PREPARE or INITIATEOLC PHASE(PREPARE) commands again.

Module:DFSICVD0, DFSICLV0, DFSICV10, DFSIDPG0

DFS3432 RACF PARAMETER INVALID IFRACF DATA SPACE USED

ExplanationWhen RACF (or equivalent product) with theGLOBAL=YES support is used, the RACF-defined IMStransactions and command profiles are loaded into aRACF data space. The IMS online change command /MODIFY PREPARE RACF cannot be used to refreshthese profiles when they are in a RACF data space.


Operator responseThe RACF-defined IMS profiles in the RACF dataspace can be refreshed by using the RACF commandSETROPTS RACLIST (classname) REFRESH. Anexample of a classname is TIMS. TIMS is the RACFclassname for IMS transaction profiles.

Module:DFSICVF0

DFS3433W ACBLIB MEMBER OLC IDMISMATCH MOLCID=yyyydddhhmmss


ExplanationOne or more ACB library member online changesoccurred while IMS was not active in the IMSplex.IMS restart processing detected that the value inthe MOLCID field in the restart checkpoint log record(X'4001') is not the same value as in the MOLCID fieldin the OLCSTAT data set. MOLCID=yyyyddd hhmmss isthe local time stamp of the last member online changeprocess that was committed while IMS was not activein the IMSplex.

System actionIMS restart continues normally.

System programmer responseIf ACBSHR=Y, then the ACB library member onlinechange has been included and the restarting IMS doesnot need to take any action.

If ACBSHR=N, then its ACB library does not include anyACB member online changes while the restarting IMSis down.

When this message is issued because ACBSHR=N isspecified for this IMSplex, it means that:

• IMS systems in the OLCSTAT data set do not shareACB libraries.

• One or more ACB library member online changeprocesses occurred while this IMS was not active inthe IMSplex.

• The ACB member online changes that occurred whilethis IMS was not active in the IMSplex are not in theactive ACB library of this IMS.

Manually update the ACB members in the ACB libraryso that the 1MOLCID field in the X'4001' log recordmatches the MOLCID field in the OLCSTAT data set.

Attention: If you run this IMS before theMOLCID values match, IMS might havedata integrity problems or might terminateabnormally.

To make the MOLCID values match, performone of the following tasks:

1. Perform one or more ACB member onlinechange processes to synchronize theMOLCID field in the X'4001' log record withthe MOLCID field in the OLCSTAT data set.

2. Shut down IMS and run the ACBMaintenance utility.

a. Shut IMS down normally.b. Run the ACB Maintenance utility for

those member online changes and applythe changed ACBs directly to the active

ACB library. Ensure that the ACB libraryincludes all the ACB library membersonline up to the time of the MOLCID inDFS3433W.

c. Restart IMS.

Module:DFSRLP00

DFS3434W UNABLE TO OPEN DDNAME'ddname'

ExplanationIMS encountered an error trying to open the data setwith ddname. Either the DD statement does not existor the operating system has encountered an I/O errorduring open processing.


Programmer responseThe data set for ddname was probably not created.You must create the data set, if it is an I/O error.

DFS3435A UNABLE TO LOAD MODULEDFSnnnns. SYSTEM CODE=abcd.REASON CODE=efgh.

ExplanationImportant: If you have not installed APAR PH04751,the message text of this message may be:DFS3435A UNABLE TO LOCATE OR LOAD MODULE DFSnnnns.RETURN CODE=abcd

IMS is unable to locate or load the indicated moduleDFSnnnns from the inactive MODBLKS data set.


Represents the MODBLKS member name, eitherDDIR, PDIR, RCTE, or SMB0.

sRepresents the member name suffix.

abcdAfter APAR PH04751 is installed, represents the4-digit z/OS LOAD system completion code for theabend that would have been issued had the callernot provided an ERRET exit.

If you have not installed APAR PH04751, abcdmay represent the 4-digit return code, where abis the IMODULE LOAD return code, and cd is theIMODULE LOCATE return code.


efghRepresents the z/OS LOAD reason code associatedwith the system completion code.

See the IMODULE LOAD and IMODULE LOCATE returncodes documented in the IMS system services returncode information.

System actionIf the module is necessary for continued operations,the /MODIFY or INITIATE OLC preparation isterminated. Otherwise, the message is a warning andthe command attempts to complete.

Programmer responseBe sure that the library is APF authorized. Run theoffline MODBLKS system definition steps to build therequired modules or run the Online Change utility tocopy the MODBLKS data set.

Related referenceIMS system services return codes (Messagesand Codes)

DFS3436E INTERNAL BLOCKS MISSING:ERROR CODE= errcode PST=pstnoPSB psbname DBD=dbname

ExplanationAn internal error has caused an IMS abend U1143.

In the message text:dbname

The name of the database that was being alteredor accessed by an application program when themissing blocks were detected.

psbnameThe name of the PSB that specifies that databaseand version that the application program is tryingto access.

pstnoThe program specification table (PST) numberrelative to zero.

errcodeThe error code that identifies when the missingblocks were detected. See the following list oferror codes for an explanation of each code.

Error CodeExplanation

01At the start of the transformation process, IMSdetected that the delta blocks that are required forthe HALDB alter function were not built.

02Missing database versioning table.

03Missing entry in the database versioning table.

05During the data transformation on a DL/I callthat reads the database, IMS detected that thedelta blocks that are required for the HALDB alterfunction were not built.

06During the data transformation on a DL/I call thatupdates the database, IMS detected that the deltablocks that are required to access a version of thedatabase other than the current version were notbuilt.

07During the data transformation on a DL/I call thatreads the database, IMS detected that the deltablocks that are required to access a version of thedatabase other than the current version were notbuilt.

08An application program attempted to update avariable length segment with data that is longerthan the maximum segment length that is definedin the altered DMB for the new database definition.

09Storage for block DBVW cannot be obtained duringPSB scheduling time.

0AThe size of the delta blocks grew larger thanits expected size during HALDB online alterprocessing.

0BThe size of the delta blocks grew larger thanits expected size for a database with databaseversioning enabled.

0CThe HALDB alter function failed to obtain thestorage that is required to reformat the segmentdata from the format defined in the existingdatabase definition to the format defined in thenew database definition.

0DThe internal delta blocks that are required to altera segment from the format defined by the existingdatabase definition to the format defined by thenew database definition were not built.

System actionThe application program terminates with abendU1143.




System programmer responseFor error code 08, determine the maximum lengthfor the variable length segment by reviewing theDBD source. Either change the maximum lengththat is defined in the DBD source and commit thechanges with the Online Change function or modifythe application program to reduce the length of thedata that the application program uses to updatethe segment so that it is equal to or less than themaximum segment length.

For other error codes, contact IBM Software Support.

Module:DFS5DBB0, DFSDFLS0


DFS3437E ERROR PROCESSING variable textRELEASE iii INVALID

ExplanationUtility program DBFUMIN0 detected a mismatch in theIMS release level between the system and the ACBmember.

In the message text, variable text refers to one ofthe following targets, depending on whether the IMSmanagement of ACBs is enabled:ERROR PROCESSING ACBLIB - ACBLIB DMBMEMBER RELEASE iii INVALID

Issued when the release level of IMS that is beingused does not match the level of the member inthe ACBLIB.


ERROR PROCESSING CATALOG: CATALOG MEMBERRELEASE iii INVALID

Issued when the release level of IMS that is beingused does not match the level of the member inthe IMS catalog.


iiiThe IMS release level that is defined in the ACBmember.


System programmer responseResubmit the job after correcting the IMS release leveldefined in the ACBLIB or in the IMS catalog.

Module:DBFUMIN0

Related referenceIMS Catalog Definition exit routine (DFS3CDX0)(Exit Routines)IMS Catalog Populate utility (DFS3PU00)(System Utilities)

DFS3438 RESERVED INDEX AREA IN MFSBUFFER POOL TOO SMALL.

ExplanationThe area in the message format buffer pool (MFBP)reserved during IMS initialization for increasing thetwo indexes used by the MFBP manager is notlarge enough to accommodate the increased PDSdirectory index resulting from the /MODIFY PREPAREor INITIATE OLC PHASE(PREPARE) command.


Programmer responseEither increase the reserved area in the MFBP atthe next IMS restart, or reduce the requirements toincrease the PDS directory index. The PDS directoryindex contains one 12-byte entry per format librarydirectory block. The reserved area is specified as anEXEC parameter (FBPR=) in the IMS procedure. Theadditional space requirement can be calculated asfollows:

(12 x (1 + number of additional MFS format blocks/10))plus (14 x (number of new $$IMSDIR entries))

DFS3439W I/O ERROR READING THEDIRECTORY FOR ddname {-nnn}

ExplanationAn I/O error occurred while reading the data set,indicated by ddname, during processing of one of thefollowing commands:

• /MODIFY PREPARE• INITIATE OLC PHASE(PREPARE)• /MODIFY COMMIT• INITIATE OLC PHASE(COMMIT)







If the error occurred on a FORMAT library that hasconcatenated data sets, nnn indicates on which of theconcatenated data sets the error was received.


Programmer responseIf the I/O error occurred on a data set currently in useby the online IMS system, that system might shortlyencounter a similar condition. If the error occurred foran inactive data set, you should recreate that data set.

DFS3440E CHECKPOINT IS REJECTED -ONLINE CHANGE COMMIT IS INPROGRESS

ExplanationA /CHECKPOINT command was rejected becauseonline change commit was in progress.

System actionThe /CHECKPOINT command is rejected.

Operator responseTry the /CHECKPOINT command again after onlinechange commit is completed.

Module:DFSICM30, DFSRCP00

DFS3441 NOT ENOUGH STORAGE INSUBPOOL 231 FOR MODIFY

ExplanationThe /MODIFY or INITIATE OLC command processorwas unable to get storage from subpool 231.


Operator responseReenter the command when the system activity isdecreased and more storage is available.

DFS3442I CHECKPOINT IS DEFERRED -ONLINE CHANGE COMMIT IS INPROGRESS

ExplanationA simple checkpoint was initiated but is deferredbecause online change commit is in progress.The simple checkpoint was initiated either by a /CHECKPOINT command or internally by IMS becausethe CPLOG value was reached.

System actionThe simple checkpoint is deferred. When onlinechange commit completes, IMS initiates a simplecheckpoint internally.


Module:DFSRCP00

DFS3443I /DISPLAY MODIFY ACTIVE

ExplanationA /MODIFY COMMIT or /MODIFY ABORT commandwas entered while a /DISPLAY MODIFY commandwas in progress.


Operator responseWait, then reissue the command.

DFS3444W TRAN tranname CONFLICTSWITH DYNAMIC LTERM, /MODIFYABORTED

ExplanationA /MODIFY PREPARE or INITIATE OLCPHASE(PREPARE) command was entered thatattempted to add a transaction name that conflictswith a dynamic LTERM name. The tranname variablenames the transaction that already exists as adynamically created LTERM.

System actionThe /MODIFY PREPARE or INITIATE OLCPHASE(PREPARE) command is aborted.

Programmer responseDetermine whether tranname should be a LTERMor a transaction. If it should be an LTERM, removetranname from the inactive MODBLKS you are trying


to change to and retry the online change. If trannameshould be a transaction, delete the dynamic LTERMby removing status and queue counts and initiatinga simple checkpoint. To do this, issue the followingcommands:

/STOP USER tranname/DEQ USER tranname PURGE (or /DEQ LTERM tranname PURGE)/START USER tranname/CHE

After the dynamic LTERM is deleted, retrythe /MODIFY PREPARE or INITIATE OLCPHASE(PREPARE) command.

DFS3445 INACTIVE FORMAT LIBRARY ISEMPTY

ExplanationThe inactive format library has no members.

System actionThe /MODIFY PREPARE or INITIATE OLCPHASE(PREPARE) command is aborted.

Programmer responseCopy the updated staging format library to the inactiveformat library and reissue the command.

DFS3446I INDEX AREA IN MFS BUFFERPOOL TOO SMALL. nnnn ENTRIESTRUNCATED

ExplanationThe area in the message format buffer pool (MFBP)reserved during IMS initialization for the two indexesused by the MFBP manager is not large enoughto accommodate the increased indexes that wouldresult from the /MODIFY PREPARE or INITIATE OLCPHASE(PREPARE) command being entered.


System programmer responseIf the /MODIFY PREPARE or INITIATE OLCPHASE(PREPARE) command completes successfully,enter one of the following commands:

• /MODIFY ABORT• TERMINATE OLC• /MODIFY COMMIT• INITIATE OLC PHASE(COMMIT)

If you enter the /MODIFY ABORT command followedby the /MODIFY PREPARE , or the TERMINATEOLC command followed by the INITIATE OLCPHASE(PREPARE) command, the resident index ($$IMSDIR) might be made smaller.

If you enter the /MODIFY COMMIT or INITIATE OLCPHASE(COMMIT) command, the resident index will betruncated by the number of entries indicated in thismessage, but the switch to the inactive format librarywould continue. The reserved area for expansion of theindexes in the MFS buffer pool should be increasedat the next IMS restart, or the requirements of thetwo indexes should be reduced. The reserved areais specified as an EXEC parameter (FBP=) in the IMSprocedure.

The additional space requirement can be calculatedas:

12 x (1 + number of added MFS format blocks/12) plus14 x (number of new $$IMSDIR entries)

DFS3447 UNABLE TO ACQUIRE STORAGEFOR INACTIVE FORMAT LIBRARYDIRECTORIES

ExplanationStorage in the IMS extended private area isunavailable for the hash table, for the prime area ($$IMSDIR), or index area of the MFS Dynamic Directory,or for the PDS directory index during /MODIFYCOMMIT or INITIATE OLC PHASE(COMMIT).

System actionThe /MODIFY COMMIT or INITIATE OLCPHASE(COMMIT) command is ignored.

Programmer responseReenter the command at a time when system activityhas decreased and more storage is available.

DFS3448W UNEXPECTED EOF ON DDNAMEddname -nn

ExplanationThe library referenced by the DD statement with thename ddname does not contain the expected data.This can be because the DD statement specified "DDDUMMY". If the EOF occurred on a FORMAT librarywhich has concatenated data sets, nn indicates onwhich of the concatenated data sets of the EOF wasreceived.



Programmer responseCorrect the DD statement, or recreate the data set,and reenter the command.

DFS3449W AN INVALID DIRECTORY BLOCKWAS READ FOR xxxxxxx - nn

ExplanationDuring a /MODIFY PREPARE or INITIATE OLCPHASE(PREPARE) command for an online changeoperation that included changing the MFS formatlibrary, an invalid directory block was read for a dataset that has the DDNAME indicated in the messageby xxxxxxx (FORMATA or FORMATB) and a number nnindicating the concatenated data set for that DDNAME.


Operator responseThe data set indicated in this message has an errorin the partitioned data set directory. This data set willneed to be restored from a backup, or be recreated.

DFS3450 /DBR NEEDED BEFOREPARTITIONED DATABASE CAN BECHANGED/DELETED

ExplanationOnline change was initiated to either change or deleteone or more HALDBs which have not been taken offlinewith a /DBR command.

Operator responseIssue a /DBR command for any HALDBs being changedor deleted, along with any logically related databases,primary indexes, or secondary indexes.

Module:DFSICV30


Chapter 73. DFS messages, DFS3451 - DFS3500W


DFS3451 A /MODIFY PREPARE COMMANDIS NOT IN EFFECT

ExplanationA /MODIFY PREPARE command must be in effectbefore a /MODIFY COMMIT or ABORT, or a /DISPLAYMODIFY command can be processed.


Operator responseIssue a /MODIFY PREPARE command which specifiesthe requested changes.

DFS3452 WORK IN PROGRESS FORRESOURCES TO BE CHANGED/DELETED

ExplanationThe INITIATE OLC PHASE(COMMIT) or /MODIFYCOMMIT command processing found that theresources to be changed or deleted have activework pending and are directly affected by this onlinechange.


Operator responseIssue the /DISPLAY MODIFY command or the /DISPLAY MODIFY ALL command to determinewhich resources still have active work pending. Whenthe /DISPLAY MODIFY command indicates thatall resources are to be changed or deleted andno longer have any active work pending, reissuethe INITIATE OLC PHASE(COMMIT) or /MODIFYCOMMIT command.

Module:DFSICV30

DFS3453 ERROR WRITING MODSTAT DATASET

ExplanationAn I/O error was detected while attempting to writethe MODSTAT data set.


Programmer responseReconstruct the MODSTAT data set with the ddnamesindicated on the last successful DFS3410I orDFS3499I message. See the IMS system definitioninformation about reconstruction of MODSTAT. For theappropriate recovery actions in an XRF environment,see the IMS system administration information.

Related conceptsRecovery in an XRF complex (SystemAdministration)

DFS3454I I/O ERROR READING RESIDENTDIRECTORY ($$IMSDIR) ddname{-nn}

ExplanationAn I/O error occurred while the /MODIFY COMMITor INITIATE OLC PHASE(COMMIT) command wasreading the resident directory ($$IMSDIR) memberfrom the inactive FORMAT library. If the error occurredon a FORMAT library that has concatenated data sets,nn indicates on which of the concatenated data setsthe error was received. ddname is the name of theDD statement for the library for which the I/O erroroccurred.


Programmer responseRecreate the resident directory ($$IMSDIR) on theinactive FORMAT library. Copy the $$IMSDIR memberfrom the active FORMAT library to the inactive dataset, and the updates then reapplied, using the MFSService utility.

DFS3455I /MODIFY ABORT IN PROGRESS


http://www.ibm.com/support/knowledgecenter/SSEPH2_15.1.0/com.ibm.ims15.doc.sag/system_intro/ims_recov_xrfcomplex.htm#ims_recov_xrfcomplex

http://www.ibm.com/support/knowledgecenter/SSEPH2_15.1.0/com.ibm.ims15.doc.sag/system_intro/ims_recov_xrfcomplex.htm#ims_recov_xrfcomplex

ExplanationA /DISPLAY MODIFY, /MODIFY PREPARE, or /MODIFY COMMIT was entered while a /MODIFYABORT was in progress.


Operator responseWait for the termination to finish, then resubmit thecommand.

Module:DFSICVD0

DFS3457 CHECKPOINT IN PROGRESS.COMMAND REJECTED.

ExplanationA checkpoint is in progress; the command cannotsucceed and a commit cannot be performed.


Operator responseReenter the /MODIFY COMMIT or INITIATE OLCPHASE(COMMIT) command at a later time.

DFS3458 INSUFFICIENT STORAGEAVAILABLE IN AOIP POOL

ExplanationThe Automated Operator Interface (AOI) exit interfacemodule was called to pass a command to the Type-1Automated Operator exit routine (DFSAOUE0), but theinterface module failed to obtain storage from theAutomated Operator Interface buffer pool (AOIP).


Output destinationThe error message is returned to the console that thecommand was entered from.

User responseThis condition can be a temporary condition that canbe resolved by reentering the command later. If thecommand fails again, notify the system programmer.

Problem determinationUse the /DISPLAY POOL command to display theprocessor storage utilization statistics for AOIP.

Module:DFSICLP0, DFSICM20, DFSYCM20

Related reference/DISPLAY POOL command (Commands)

DFS3459 MODIFY COMMIT TERMINATED -ALL DATABASE IN-DOUBTS MUSTBE RESOLVED

ExplanationYou cannot perform an online change until all in-doubtdata in the system is resolved.

System actionIMS processing continues but no online change isperformed.

Programmer responseYou can resolve the in-doubts either by reconnectingthe coordinator controller and IMS or by using anoperator command. Then you can perform the onlinechange.

DFS3460 /MODIFY PREPARE IN PROGRESS

ExplanationThe IMS command module is currently processing a /MODIFY PREPARE command and the IMS commandmodule has not yet acknowledged completion of thecommand to the entering terminal.


Operator responseReenter the command after the command response tothe /MODIFY PREPARE command is received.

ModuleDFSICVD0

DFS3461 /MODIFY COMMIT IN PROGRESS

ExplanationThe IMS command module is currently processinga /MODIFY COMMIT command and it has not yet


http://www.ibm.com/support/knowledgecenter/SSEPH2_15.1.0/com.ibm.ims15.doc.cr/imscmds/ims_displaypool.htm#ims_cr1displaypool

acknowledged completion of the command to theentering terminal.


Operator responseReenter the command after the command response tothe /MODIFY COMMIT command is received.

ModuleDFSICVD0

DFS3462I DEDB xxxxxxxx NOT VALIDFOR /DBD COMMAND.

ExplanationThe /DBDUMP command does not apply to DEDBs.

System actionThe named database will be removed from thecommand, and the remaining databases, if any, will beprocessed.


DFS3463I SPECIFIC MSDB xxxxxxxx NOTVALID FOR /DBD COMMAND

ExplanationThe /DBDUMP command is used to dump all theMSDBs to the MSDB dump data set by specifying thespecial parameter MSDB with the DATABASE keywordwhen entering the /DBDUMP DB command, or byentering the /DBDUMP DB ALL command.



DFS3464I MSDB xxxxxxxx NOT VALIDFOR /DBR COMMAND.

ExplanationThe /DBRECOVERY command does not apply to FastPath MSDBs.



DFS3465I DATABASE xxxxxxxx IN ERROR

ExplanationThe /START DB command did not process becausea dynamic backout failure occurred for the specifieddatabase.

System actionThe named database will be removed from thecommand and the remaining databases, if any, will beprocessed.

Programmer responseIssue the /DBR command to get the specifieddatabase offline, perform a batch backout, andthen issue the /START DB or UPDATE DBSTART(ACCESS) command.

DFS3466I DDIR FOR DATABASE ddddddddNOT FOUND

ExplanationThe database keyword parameter dddddddd in the /START, /STOP, /DBD, or /DBR command is not knownto the IMS system. A DDIR could not be foundfor database dddddddd by a command processingmodule.

System actionIMS ignores the invalid parameter and continues toprocess any other database keyword parameters onthe command.

Programmer responseReenter the command, specifying the correcteddatabase parameters.

Chapter 73. DFS messages, DFS3451 - DFS3500W 975

DFS3467I ERROR READING MODSTAT DATASET

ExplanationAn I/O error occurred while reading the MODSTATdata set or the contents of the MODSTAT data set areinvalid. The error was encountered during initializationfor a batch DBD type IMS region.

System actionIMS terminates abnormally with abend U821.

Programmer responseReconstruct the MODSTAT data set with the correctedddnames before executing the batch job.



DFS3468I UNABLE TO OPEN DDNAMEddname IN DLS REGION

ExplanationThe DL/I subordinate address space option wasselected. As part of processing a /MODIFY PREPAREor INITIATE OLC PHASE(PREPARE) command,the indicated DDNAME cannot be opened in theDL/I subordinate address space. Either the indicatedDDNAME was not defined in the DL/I subordinateaddress space region JCL, or the operating systemencountered an error during OPEN processing.

System actionThe /MODIFY PREPARE or INITIATE OLCPHASE(PREPARE) command is ignored.

Programmer responseThe indicated DDNAME might not be defined in theDL/I subordinate address space JCL, or the data setspecified might not exist.

DFS3469I IN= PARAMETER IGNORED FORTYPE=ACTVACB

ExplanationThe IN= parameter in the OLCUTL procedure is notrequired when TYPE=ACTVACB.

System actionThe Online Change Copy utility (DFSUOCU0) ignoresthe IN= parameter and continues processing.

ModuleDFSUOCU0

DFS3470 TRANSACTION CURRENTLY NOTAVAILABLE FOR USE (I:sss1/name1, D:sss2/name2)

ExplanationThe transaction is in the process of being modified,or the application program and databases associatedwith the transaction are currently being modified.




System actionThe entered transaction is rejected by IMS.

Operator responseReenter the transaction at a later time when thetransaction or its resources are not being modified,and are available for use.

DFS3471 ROUTING CODE CURRENTLY NOTAVAILABLE FOR USE

ExplanationThe routing code selected for this transaction iscurrently being modified.

System actionThe entered transaction is rejected by IMS.

Operator responseReenter the transaction at a later time when therouting code is not being modified, and is available foruse.



DFS3472 DEVICE FORMAT CHANGED,MESSAGE RETURNED TO QUEUE

ExplanationIMS MFS detected that the format currently used toformat this device was dynamically modified by theOnline Change function.

System actionThe output message that was in progress has beenreturned to the IMS message queue.

Operator responseThe message can be requested again; however, thenew MFS format can result in some data beingformatted differently.

DFS3476I UPDATE MSLINK COMMANDCOMPLETED, CC= xx

ExplanationThe /UPDATE MSLINK command you issued froman IMS terminal has completed. xx identifies thecompletion code.

When you issue an UPDATE MSLINK commandthrough the Operations Manager (OM), it processes asa type-2 command and does not issue this message.

System action:If the completion code is 00, the /UPDATE MSLINKcommand completed successfully. If the completioncode is non-zero, the command encountered aproblem.

Operator responseIf the completion code is 00, no action is required.

If the completion code is non-zero, see the completioncode table in the information for the UPDATE MSLINKcommand. Correct the problem and reissue thecommand.

System programmer response:See the Operator response.

Module:DFSIU100

Related referenceUPDATE MSLINK command (Commands)

DFS3478 OUTPUT MESSAGE CANCELED BYSTATICOUTSEC OPTION

ExplanationIMS canceled the transaction output message forstatic VTAM terminals because the current userdoesn't match the user who initiated the transaction.This action is at the request of the STATICOUTSECparameter that is specified in the DFSDCxxx PROCLIBmember. If the terminal is in response mode and thecurrent user has a different ID than the user ID thatinitiated the transaction, IMS sends this message inplace of the transaction output message.

System action:IMS sends this message instead of the canceledmessage. The processing continues.

Output Destination:3270 user terminal.

User response:This is an informational message. Check yourprocedures to determine if you must take any actions.


Module:DFSCOFC0, DFSCFEO0

Related referenceDFSDCxxx member of the IMS PROCLIB dataset (System Definition)Related information“IMS problem determination” on page 11IMS messages and codes problemdetermination is accomplished by usingprocedures established by IBM.

DFS3480I INVALID LIBRARY TYPEPARAMETER

ExplanationThe library type parameter was not one of thefollowing values for the Online Change utility:

ACBFORMATMODBLKS

System actionThe copy is not done and the utility is terminated.

Programmer responseCorrect the parameter, and rerun the utility.

Module:DFSUOCU0


http://www.ibm.com/support/knowledgecenter/SSEPH2_15.1.0/com.ibm.ims15.doc.cr/imscmds/ims_updatemslink.htm#ims_cr2updatemslink

http://www.ibm.com/support/knowledgecenter/SSEPH2_15.1.0/com.ibm.ims15.doc.sdg/ims_dfsdcxxx_proclib.htm#ims_dfsdcxxx_proclib


DFS3481I INVALID INPUT DDNAMEPARAMETER

ExplanationThe input ddname parameter for the Online Changeutility is not one of the following values:

SI



DFS3482I INVALID OUTPUT DDNAMEPARAMETER

ExplanationThe output ddname parameter for the Online Changeutility is not one of the following values:

BAOU



DFS3483 ERROR DURING ENQUEUEDDNAME=dddddddd

ExplanationAn error was detected while attempting to enqueue DDname dddddddd before copying.

System actionThe copy is not done, and the utility is terminated.

System programmer responseCorrect the DD statement.

DFS3484I ERROR READING THE MODSTATDATA SET

ExplanationAn error occurred while attempting to read theMODSTAT data set before copying.


Programmer responseDetermine whether the content of MODSTAT is correct.If the data set has been destroyed, recreate it basedon the last DFS3499I message, and resubmit the job.

Related information“DFS3499I” on page 989ACTIVE DDNAMES: modblks-name acblib-nameformat-name MODSTAT ID: nnnn

DFS3485I jobname WAITING FOR DATASETdata set name

ExplanationThe data set indicated by the message was already inuse by another task. It has caused the indicated job towait for the release of the data set.

System actionThe indicated job waits until the data set becomesavailable.


When the data set becomes available, the indicatedjob will run.

DFS3486 IEBCOPY PARAMETER ERROR

ExplanationOne of the IEBCOPY parameters specified (WORK,SIZE, or LIST) contained an invalid parameter. Thefollowing are error examples:

• One or more IEBCOPY parameters are specified onthe PROC and EXEC statements, but not specified asinput parameters.

• One or more IEBCOPY parameters are specified onthe PROC and EXEC statements, but not specified asinput parameters.

System actionThe Online Change Copy utility fails.


System programmer responseCorrect the IEBCOPY parameter on the Online ChangeCopy utility and try running the utility again.

Module:DFSUOCU

DFS3487 ALL KEYWORD INVALID

ExplanationThe ALL keyword is invalid when both dynamicresource definition (DRD) and the IMS directoryare enabled. The IMS system rejects the /MODIFYcommand.


User responseReissue the /MODIFY command without the ALLkeyword.

Module:DFSICV10

Related reference/MODIFY command (Commands)

DFS3488 ERROR DURING ENQUEUE FORDDNAME dddddddd

ExplanationAn error was encountered while attempting toenqueue the inactive library dddddddd duringthe /MODIFY PREPARE or INITIATE OLCPHASE(PREPARE) command. The library does notexist or was in use by the copy utility.

System actionIf the library is MATRIXA or MATRIXB, processingof the /MODIFY PREPARE or INITIATE OLCPHASE(PREPARE) command continues; otherwise, itis terminated.

Operator responseIf the /MODIFY PREPARE or INITIATE OLCPHASE(PREPARE) command was terminated andno message DFS3499I was issued, resubmit thecommand when the data set is available.

DFS3489 OUTPUT MESSAGE CANCELED BYUSER OUTPUT EDIT ROUTINE

ExplanationIMS canceled the output message at the requestof your physical terminal output edit routine. If theterminal is in response mode, IMS sends this messagein place of the output message that would havesatisfied response mode. If a system restart occurred,then IMS resets response mode and does not sendmessage DFS3489 after a request to discard theresponse message.

System actionIMS sends this message instead of the canceledmessage.

Operator responseThis is an informational message. Consult yourprocedures to determine if you must take any action.



DFS3490I APPC TIMEOUT ACTIVE,MVS=xxxx MINS, yy SECS,IMS=zzzz MINS.

ExplanationAPPC timeout is active. xxxx is the number of minutesand yy is the number of seconds for the APPC MVStimeout value. zzzz is the number of minutes for theAPPC IMS timeout value. These values are definedby the APPCIOT parameter in the DFSDCxxx PROCLIBmember.

System actionIMS checks every xxxx minutes or yy seconds todetermine whether an APPC call issued under thedependent region task control block (TCB) is inactiveafter more than xxxx minutes. See the message textfor DFS3492W for additional information.

zzzz is the number of minutes an application is allowedto remain inactive. Inactive means that the applicationcould not respond within the time out limit.

Programmer responseThis message is for information only.


http://www.ibm.com/support/knowledgecenter/SSEPH2_15.1.0/com.ibm.ims15.doc.cr/imscmds/ims_modify.htm#ims_cr1modify

Related informationDFS3492WAPPC/IMS TIMEOUT LIMIT REACHED FOR LUluname, TP-ID tp-id, ASYNC. CONVERSATION.INACTIVE SINCE xxxx SECONDS.

DFS3491I APPC/IMS TIMEOUTDEACTIVATED. (SYSTEMSHUTDOWN) (TIMER CANCELED)(DFSTIMER ERROR, RC=xx) (APPCNOT ACTIVE (APPCIOT = 0) (NOMVS SUPPORT)

ExplanationAPPC/IMS timeout is inactive. The message includesthe reason why APPC/IMS timeout is inactive.

If the reason is NO MVS SUPPORT, APPC/MVS doesnot support the timeout service. The current z/OS leveldoes not support the APPC/MVS timeout service.

When APPCIOT = 0 is listed, the APPCIOT parameterin DFSDCxxx member has been defined as zero, or hasbeen changed to zero by the /CHANGE command.

Programmer responseIf the reason is (DFSTIMER ERROR), report theproblem to IBM Software Support. Otherwise, this isan informational message.

DFS3492W APPC/IMS TIMEOUT LIMITREACHED FOR LU luname, TP-ID tp-id, ASYNC. CONVERSATION.INACTIVE SINCE xxxx SECONDS.

or

APPC/IMS TIMEOUT LIMIT REACHED FOR LUluname, TP-ID tp-id, REGION region-id. INACTIVESINCE xxxx SECONDS.

ExplanationAPPC/IMS timeout detected a dependent region or anasynchronous conversation that might have hung. Thevalues of the message text are:luname

The VTAM LU name of the session.tp-id

The TP-ID of the APPC conversation.region-id

The IMS-dependent region ID or ASYNC. For anasynchronous conversation, the region ID is CONV.

xxxxThe number of seconds the conversation is waitingfor a response to an APPC call.

Programmer responseIssue a V NET,INACT command for the luname toclean up the dependent region or an asynchronousconversation that is potentially hung. V NET,INACTstops all conversations for the luname, which could bemore than just the hung conversation.

If the hung conversation is a batch-job, the lunamewill be APPC/MVS; in this case, issuing a VNET,INACT stops all APPC/MVS sessions. Use thetp-id to determine the job-name by issuing the DAPPC,TP,ALL command, and cancel the batch job.

DFS3493I MODBLKS KEYWORD INVALIDWHEN DYNAMIC RESOURCEDEFINITION ENABLED

ExplanationThe command was not processed because thekeyword is invalid in an IMS system with dynamicresource definition (DRD) enabled.


Programmer responseUse DRD commands to modify resources online.

DFS3494E OTMA HAS TIMED OUT FORTMEMBER/TPIPE xxxx/yyyy

or

OTMA HAS TIMED OUT FOR TMEMBER/TPIPE xxxx/yyyy RT=rt_token

or

OTMA HAS TIMED OUT FOR TMEMBER/TPIPE xxxx/yyyy AND MOVED THE OUTPUT TO zzzz

ExplanationOTMA timed out waiting for an ACK or NAK from theOTMA target member (tmember or client) xxxx withthe transaction pipe (tpipe) yyyy has initiated a CM0timeout action for a missing ACK or NAK.

If the OTMA tpipe supports multiple active RESUMETPIPE requests, the hexadecimal token number,


rt_token, that identifies the RESUME TPIPE call is alsodisplayed.

If the zzzz field is present, the CM0 output messagehas been rerouted to the output tpipe zzzz. If themember supports the hold queue, the message ismoved to the hold queue of the tpipe zzzz.

For an IMS callout message through ICAL, theIMS application that issues the synchronous calloutrequest receives a return code of X'100' and a reasoncode of X'104'. The message is discarded.

In the message text:rt_token

The identifying hexadecimal token number of theRESUME TPIPE call.

xxxxThe name of the OTMA client.

yyyyThe name of the TPIPE on which the time outoccurred.

zzzzThe TPIPE name to which the output was rerouted.


Operator responseIdentify the cause of the missing ACK or NAK for thistimeout condition. It could be an application programor a failure in the network component.

Programmer responseMake sure that your program issues an ACK or NAK toIMS for the received CM0 output message. Also, it ispossible that there is a network failure so that the ACKor NAK cannot arrive at IMS OTMA.

If the OTMA client is IMS Connect, you can issuethe IMS command QUERY IMSCON TYPE(CLIENT)RTTOKEN(rt_token) to identify the IMS Connect client.

Problem determinationExamine the network trace to identify whichcomponent in the network did not forward the ACKor NAK to IMS. Make sure that your program issuesan ACK or NAK to IMS for the received CM0 outputmessage or synchronous callout message.

A possible cause of this problem is that there is anetwork failure so that the ACK or NAK cannot arrive atIMS OTMA.

Module:DFSYPSO0

DFS3495W OTMA HAS BEEN WAITINGFOR AN ACK FROM TMEMBER/TPIPE xxxx/yyyy FOR OVER zzzzSECONDS.

ExplanationOTMA detected that member xxxx with transactionpipe (tpipe) yyyy has been waiting for anacknowledgment for more thanzzzz seconds. Becausethe OTMA CM0 ACK timeout function has been turnedoff, OTMA does not take the timeout action to reroutethe output message.

System action:Processing continues. The tpipe remains in a hangstatus. All of the queued output messages on the tpipeare not delivered until the ACK or NAK is received.

Operator responseIdentify the cause of the missing ACK or NAK forthis timeout condition. The problem might be anapplication program, or a failure in the networkcomponent. You can restart the tpipe manuallywith a /STOP TMEMBER tpipe and then a /STARTTMEMBER tpipe command.

Programmer responseMake sure that your program issues an ACK or NAK toIMS for the received CM0 output message. Also, it ispossible that there is a network failure so that the ACKor NAK cannot arrive at IMS OTMA.

Problem determination:Examine the network trace to identify whichcomponent in the network did not forward the ACK orNAK to IMS.

Module:DFSYPSO0

DFS3496W DMB XXXXXXXX IN INACTIVEACBLIB NOT COMPATIBLE WITHIMS

ExplanationThe level of the inactive library is not compatible withthe current IMS release.

System actionThe /MODIFY PREPARE ACBLIB or INITIATE OLCPHASE(COMMIT command terminates.


Programmer responseVerify that the JCL specifies the correct library and thatACBGEN is performed at the appropriate level for thecurrent release of IMS

DFS3497A AN INVALID MOLC LOG RECORDDETECTED AND IGNORED RSN=aaaaaaaa RC=bbbbbbbbTOKEN=cccccccccccccccc

or

A PRIOR MOLC UOW FOUND, THE UOW ISBEING IGNORED RSN=aaaaaaaa RC=bbbbbbbbTOKEN=cccccccccccccccc

or

INTERNAL MOLC ERROR RSN=aaaaaaaaRC=bbbbbbbb TOKEN=cccccccccccccccc

or

INTERNAL MEMBER ONLINE CHANGEERROR RSN=aaaaaaaa RC=bbbbbbbbTOKEN=cccccccccccccccc

or

MOLC ERROR PROCESSING AN INCOMPLETEUOW RSN=aaaaaaaa RC=bbbbbbbbTOKEN=cccccccccccccccc

or

MOLC ERROR, PDIR BLOCK COULD NOTBE FOUND PDIR=dddddddd RSN=aaaaaaaaRC=bbbbbbbb TOKEN=cccccccccccccccc

or

MOLC ERROR, DDIR BLOCK COULD NOTBE FOUND PDIR=eeeeeeee RSN=aaaaaaaaRC=bbbbbbbb TOKEN=cccccccccccccccc

ExplanationDuring IMS restart, Extended Recovery Facility (XRF)or Fast Database Recovery (FDR) tracking, an

unrecoverable error was encountered while processingmember online change log records. The memberonline change unit of work was most likely notcompleted, and the member online change must beredone. See the explanation of the reason codes fordetailed information.


The name of the missing PDIReeeeeeee

The name of the missing DDIRaaaaaaaa

The reason codebbbbbbbb

The return codecccccccccccccccc

The member online change unit of work token

The reason code can be one of the following:

CodesExplanation

01Internal error. An invalid log record type 70xx waspassed to the member online change processingmodule and was ignored.

02, 03, 05, 06, 07, or 0AA type 70xx (7002, 7003, 7004 or 7005) logrecord was read for a new member online changeunit of work, while the previous member onlinechange unit of work did not contain the unit ofwork termination log record (a type 7006 or 7010).The previous member online change unit of work isterminated and cleanup is performed, and the newunit of work is initialized. Missing log records or logtapes can cause this problem.

04A 7002 log record contained no members toprocess. This member online change unit of workgenerated no work. This situation is most likelydue to a member online change which did notupdate any ACBLIB members.

08A 7005 log record was processed for a memberonline change indicating the user terminated themember online change unit of work. The memberonline unit of work is terminated.

09A 7005 log record was processed, indicating theuser committed the member online change unit ofwork. If this problem is an XRF tracking IMS withFDBR and ACBSHR=N is specified, the memberonline unit of work is committed. If this problemis an XRF tracking IMS with FDBR and ACBSHR=Y


is specified, no action is required by this IMS; thecommit on the active IMS completed successfully.

0BA 7010 log record was found as the only log recordin this unit of work. See the subsequent DFS3497Ito determine how IMS handled this member onlinechange unit of work.

0CA 7010 log record was found by the tracking IMSat the end of a unit of work log stream, indicatingyou aborted the member online change unit ofwork. ACBSHR=N was specified so IMS aborted themember online unit of work.

0DA 7010 log record was found at the end of a unitof work log stream, indicating you aborted themember online change unit of work. ACBSHR=Ywas specified, so no IMS action is required. Thisis an informational message only.

0EA 7002 was the only log record found in thelog stream for this member online change unit ofwork. The existence of the 7002 indicated the unitof work was initiated, but the subsequent 7004,7005, and 7010 were not found. IMS read theOLCSTAT data set and found the member onlinechange unit of work had been aborted, so IMSaborted the member online change unit of work.

0FA 7003 was the last log record found in the logstream for this member online change unit ofwork. The existence of the 7003 indicated the unitof work was initiated, but the subsequent 7004,7005, and 7010 were not found. IMS read theOLCSTAT data set and found the member onlinechange unit of work had been aborted, so IMSaborted the member online change unit of work

10A 7003 was the last log record found in the logstream for this member online change unit ofwork. The existence of the 7003 indicated the unitof work was initiated, but the subsequent 7004,7005, and 7010 were not found. IMS read theOLCSTAT data set and found the member onlinechange unit of work had been completed, so IMScommitted the member online change unit of work.

11A 7004 was the last log record found in the logstream for this member online change unit ofwork. The existence of the 7004 indicated theunit of work had completed; however, because thesubsequent 7010 was missing, the state of theresources being changed is unknown. The memberonline change unit of work is committed.

12This is due to an internal error, where part of theinternal control block structure is missing. Themember online change process is aborted.

1B or 21This problem is due to a get main failure. Themost likely cause is a lack of available storage.The return code for the get main is included in themessage.

1CThe member online change process could not readthe OLCSTAT data set; the member online changeprocess is aborted.

1DA DDIR was missing from the library duringmember online change processing. The onlinechange process skips this member and themember online change process continues.

1EA PDIR was missing from the library duringmember online change processing. The onlinechange process skips this member and themember online change process continues.

1F or 20An internal error occurred during initializationprocessing for a member online change. Themember online change process is aborted.

13, 15, 17, or 19During tracking with ACBSHR=NO, the memberonline change process was attempting to deletea member from the tracking ACBLIB, but themember does not exist. This code indicates theACBLIBs are now out of sync between the activeand the tracker. IMS terminates abnormally.

22A 7002 was the only log record found in thelog stream for this member online change unit ofwork. The existence of the 7002 indicated the unitof work was initiated, but the subsequent 7004,7005, and 7010 were not found. IMS read theOLCSTAT data set and found the member onlinechange unit of work had been committed, so IMSrecommitted the member online change unit ofwork.

2D, 2E, 2F, 30, 31, 32, 33, 34, 35, 41, or 42A a previous unit of work for member onlinechange still existed when one of the following logrecords was processed: 7002, 7003, 7004, 7005,7007, 7008, 7012, 7013, 7014, 7015. No actionis required. Missing log records or log tapes cancause this problem.

36, 37, 38, 39, 3A, 3B, 3C, 3D, 43 or 44On of the following log records was processed, butthere was no associated 7002 record in the log:7003, 7004, 7005, 7007, 7008, 7012, 7013, 7014


or 7015. No action is required. Missing log recordsor log tapes can cause this problem.

System actionThe member online change incomplete unit of workis committed or aborted. See the description ofthe reason code under Programmer response foradditional information.

Programmer responseThe responses depend on the reason codes as follows:01

An invalid log record was passed to the modulesthat process the member online change logrecords. To assist in correcting this internal error,run DFSERA10 to extract all 7002, 7003, 7004,7005, 7006, 7010, and 70FF log records andcontact IBM Software Support.

02, 03, 05, 06, 07, or 0ARun DFSERA10 to extract all 7002, 7003, 7004,7005, 7006, 7010, and 70FF log records for thetoken described in the message. The 7002 forthe incomplete member online change unit ofwork contains the member names which were notprocessed. To process these, the member onlinechange must be redone for the missing members;also contact IBM Software Support.

04Run DFSERA10 to extract all 7002, 7003, 7004,7005, 7006, 7010, and 70FF log records andcontact IBM Software Support. This problem is aninternal error, as the 7002 must contain membernames to process. If any member online changeswere performed in this time frame, verify allmember online changes for completeness. If anymember online changes were found to have failed,the member online change must be redone.

12Run DFSERA10 to extract all 7002, 7003, 7004,7005, 7006, 7010, and 70FF log records for thetoken described in the message, and contact IBMSoftware Support. This problem is an internal error.The member online change unit of work is notcompleted and must be redone. If you feel youreceived these messages in error, contact IBMSoftware Support.

1DRun DFSERA10 to extract all 7002, 7003, 7004,7005, 7006, 7010, and 70FF log records for thetoken described in the message, and contact IBMSoftware Support. The PDIR or DDIR to memberonline change was missing from the staging oractive ACBLIB. The member online change forthese missing members must be redone. If you

feel you received these messages in error, contactIBM Software Support.

1ERun DFSERA10 to extract all 7002, 7003, 7004,7005, 7006, 7010, and 70FF log records for thetoken described in the message, and contact IBMSoftware Support. The PDIR or DDIR to memberonline change was missing from the staging oractive ACBLIB. The member online change forthese missing members must be redone. If youfeel you received these messages in error, contactIBM Software Support.

1F or 20To help IBM correct this internal error, runDFSERA10 to extract all 7002, 7003, 7004, 7005,7006, 7010, and 70FF log records and contact IBMSoftware Support.

08, 09, 0B, 0C, 0D, 0E, 0F, 10, or 11No response required, as these are informationalmessages only. If you feel you received thesemessages in error, or that there is an issue, contactIBM Software Support.

1CVerify that the OLCSTAT data set exists, and isavailable for member online change in read onlymode. The member online change unit of workmust be redone. Run DFSERA10 to extract the7002 for the token described in the message toobtain a list of the members to redo.

1BFree ECSA storage for the member online changeprocess. The member online change unit of workmust be redone. Run DFSERA10 to extract the7002 for the token described in the message toobtain a list of the members to redo.

21Free private storage for the member online changeprocess. The member online change unit of workmust be redone. Run DFSERA10 to extract the7002 for the token described in the message toobtain a list of the members to redo.

13, 15, 17, or 19The missing member name was contained in themessage. The member online change for thismember must be redone for the tracking IMSACBLIB. Run DFSERA10 to extract the 7002 forthe token described in the message to obtain alist of the members that were part of this memberonline change. Then verify that the member onlinechange has completed for the other members inthe type 7002 log record.

Module:DFSMOL10, DFSMOL20


DFS3497I MOLC 7005 LOG RECORDFOUND, UOW ABORTED RSN=aaaaaaaa RC=bbbbbbbbTOKEN=cccccccccccccccc

MOLC 7005 LOG RECORD FOUND, UOWCOMMITTED RSN=aaaaaaaa RC=bbbbbbbbTOKEN=cccccccccccccccc

or

MOLC 7010 LOG RECORD FOUND, NO PROCESSINGREQUIRED RSN=aaaaaaaa RC=bbbbbbbbTOKEN=cccccccccccccccc

or

MOLC 7010 LOG RECORD FOUND,UOW ABORTED RSN=aaaaaaaa RC=bbbbbbbbTOKEN=cccccccccccccccc

or

MOLC 7003 LOG RECORD FOUND,UOW ABORTED RSN=aaaaaaaa RC=bbbbbbbbTOKEN=cccccccccccccccc

or


or


or


ExplanationDuring IMS restart, Extended Recovery Facility(XRF) or Fast Database Recovery (FDR) tracking,an incomplete member online change unit-of-work

was encountered. The most likely cause was IMSabnormally terminating while member online changewas active, or XRF/FDBR tracking. The member onlinechange log records contained enough information toallow IMS to determine if the user had committed orterminated the member online change unit of work(UOW). Based upon this information the unit-of-workwas recommitted or terminated. See the explanationof the reason codes for detailed information.


The reason codebbbbbbbb

The return codecccccccccccccccc

The member online change unit of work token

The reason code can be one of the following:

CodesExplanation

01Internal error. An invalid log record type 70xx waspassed to the member online change processingmodule and was ignored.

02, 03, 05, 06, 07, or 0AA type 70xx (7002, 7003, 7004 or 7005) logrecord was read for a new member online changeunit-of-work, while the previous member onlinechange unit of work did not contain the unit-of-work termination log record (a type 7006 or 7010).The previous member online change unit-of-workis terminated and cleanup is performed, and thenew unit-of-work is initialized. Missing log recordsor log tapes can cause this problem.

04A 7002 log record contained no members toprocess. This member online change unit of workgenerated no work. The cause is likely a memberonline change that did not update any ACBLIBmembers.

08A 7005 log record was processed for a memberonline change indicating that you terminated themember online change unit-of-work. The memberonline unit-of-work is terminated.

09A 7005 log record was processed, indicatingthe user committed the member online changeunit-of-work. If this problem is an XRF trackingIMS with FDBR and ACBSHR=N is specified, themember online unit-of-work is committed. If thisproblem is an XRF tracking IMS with FDBR andACBSHR=Y is specified, no action is required


by this IMS as the commit on the active hascompleted successfully.

0BA 7010 log record was found as the only logrecord in this unit-of-work. See the subsequentDFS3497I for information about how IMS handledthis member online change unit of work.

0CA 7010 log record was found by the tracking IMSat the end of a unit-of-work log stream, indicatingyou terminated the member online change unit-of-work. ACBSHR=N was specified so IMS terminatedthe member online unit-of-work.

0DA 7010 log record was found at the end of a unit-of-work log stream, indicating you terminated themember online change unit-of-work. ACBSHR=Ywas specified, so no IMS action is required.

0EA 7002 was the only log record found in thelog stream for this member online change unit-of-work. The existence of the 7002 indicated the unit-of-work was initiated, but the subsequent 7004,7005, and 7010 were not found. IMS read theOLCSTAT data set and found the member onlinechange unit of work had been terminated, soIMS terminated the member online change unit ofwork.

0FA 7003 was the last log record found in thelog stream for this member online change unit-of-work. The existence of the 7003 indicated the unit-of-work was initiated, but the subsequent 7004,7005, and 7010 were not found. IMS read theOLCSTAT data set and found the member onlinechange unit of work had been terminated, so IMSterminated the member online change unit of work

10A 7003 was the last log record found in thelog stream for this member online change unit-of-work. The existence of the 7003 indicated the unit-of-work was initiated, but the subsequent 7004,7005, and 7010 were not found. IMS read theOLCSTAT data set and found the member onlinechange unit of work had been completed, so IMSrecommitted the member online change unit ofwork.

11A 7004 was the last log record found in thelog stream for this member online change unit-of-work. The existence of the 7004 indicated theunit-of-work had completed. However, becausethe subsequent 7010 is missing, the state of theresources being online changed are unknown. Themember online change unit of work is committed.

12This problem is due to an internal error, where partof the internal control block structure is missing.The member online change process is terminated.

1B or 21This problem is due to a get main failure. Themost likely cause is a lack of available storage.The return code for the get main is included in themessage.

1CThe member online change process could not readthe OLCSTAT data set, the member online changeprocess is terminated.

1DA DDIR was missing from the library duringmember online change processing. The onlinechange process skips this member and themember online change process continues.

1EA PDIR was missing from the library duringmember online change processing. The onlinechange process skips this member and themember online change process continues.

1F or 20An internal error occurred during initializationprocessing for a member online change. Themember online change process is terminated.

13, 15, 17, or 19During tracking with ACBSHR=NO, the memberonline change process was attempting to deletea member from the tracking ACBLIB, but themember does not exist. This indicates the ACBLIBsare now out of sync between the active and thetracker. IMS is abnormally terminated.

22A 7002 was the only log record found in thelog stream for this member online change unit-of-work. The existence of the 7002 indicated the unit-of-work was initiated, but the subsequent 7004,7005, and 7010 were not found. IMS read theOLCSTAT data set and found the member onlinechange unit of work had been committed, so IMScommitted the member online change unit of work.

System actionThe member online change incomplete unit of workis committed or terminated. See the description ofthe reason code under Programmer response foradditional information.

Programmer responseThe responses depend on the reason codes as follows:


01An invalid log record was passed to the modulesthat process the member online change logrecords. To help in correcting this internal error,run DFSERA10 to extract all 7002, 7003, 7004,7005, 7006, 7010, and 70FF log records andcontact IBM Software Support.

02, 03, 05, 06, 07, or 0ARun DFSERA10 to extract all 7002, 7003, 7004,7005, 7006, 7010, and 70FF log records forthe token described in the message. The 7002for the incomplete member online change unit-of-work contains the member names that werenot processed. To process these members, themember online change must be redone for themissing members along with contacting IBMSoftware Support.

04Run DFSERA10 to extract all 7002, 7003, 7004,7005, 7006, 7010, and 70FF log records andcontact IBM Software Support. This problem is aninternal error, as the 7002 must contain membernames to process. If any member online changeswere performed in this time frame, verify allmember online changes for completeness. If anymember online changes were found to have failed,the member online change must be redone.

12Run DFSERA10 to extract all 7002, 7003, 7004,7005, 7006, 7010, and 70FF log records for thetoken described in the message, and contact IBMSoftware Support. This problem is an internal error.The member online change unit-of-work is notcompleted and must be redone. If you feel youreceived these messages in error, contact IBMSoftware Support.

1DRun DFSERA10 to extract all 7002, 7003, 7004,7005, 7006, 7010, and 70FF log records for thetoken described in the message, and contact IBMSoftware Support. The PDIR or DDIR to memberonline change was missing from the staging oractive ACBLIB. The member online change forthese missing members must be redone. If youfeel you received these messages in error, contactIBM Software Support.

1ERun DFSERA10 to extract all 7002, 7003, 7004,7005, 7006, 7010, and 70FF log records for thetoken described in the message, and contact IBMSoftware Support. The PDIR or DDIR to memberonline change was missing from the staging oractive ACBLIB. The member online change forthese missing members must be redone. If youfeel you received these messages in error, contactIBM Software Support.

1F or 20To help in correcting this internal error, runDFSERA10 to extract all 7002, 7003, 7004, 7005,7006, 7010, and 70FF log records and contact IBMSoftware Support.

08, 09, 0B, 0C, 0D, 0E, 0F, 10, or 11No response required, as these are informationalmessages only. If you feel you received thesemessages in error, or that there is an issue, contactIBM Software Support.

1CVerify that the OLCSTAT data set exists, and isavailable for member online change in read onlymode. The member online change unit-of-workmust be redone. Run DFSERA10 to extract the7002 for the token described in the message toobtain a list of the members to redo.

1BFree up ECSA storage for the member onlinechange process. The member online change unit-of-work must be redone. Run DFSERA10 to extractthe 7002 for the token described in the message toobtain a list of the members to redo.

21Free private storage for the member online changeprocess. The member online change unit-of-workmust be redone. Run DFSERA10 to extract the7002 for the token described in the message toobtain a list of the members to redo.

13, 15, 17, or 19The missing member name was contained in themessage. The member online change for thismember must be redone for the tracking IMSACBLIB. Run DFSERA10 to extract the 7002 for thetoken described in the message to obtain a list ofthe members that were part of this member onlinechange and verify that the member online changehas completed for the other members in the type7002 log record.

Module:DFSMOL10, DFSMOL20

DFS3498W bbbb nnnnnnnn eeeeeeeeee....

Explanation/MODIFY PREPARE, INITIATE OLCPHASE(PREPARE), or /MODIFY COMMIT processingdetected an invalid condition in the MODBLKS orACBGEN output. This problem or situation occurredduring prepare processing, unless otherwise noted ascommit processing.



bbbbBlock type, if applicable DMB represents a DMB inACBLIB. DDIR represents a database in MODBLKS.PSB represents a PSB in ACBLIB. SMB representsa transaction in MODBLKS.

nnnnnnnnThe name of the block, if applicable.

eeeeeeeeee....The problem or situation encountered, whichmight be one of the following:ALREADY DEFINED AS PARTITION CHANGE

Issued when a database defined in theMODBLKS data set is already defined as aHALDB partition. Once a database is definedas a HALDB partition to DBRC and IMS, itremains defined to IMS as a HALDB partitionuntil you cold start IMS and cannot be changedinto a MODBLKS database, even if the HALDBpartition is deleted from DBRC.

ALREADY DEFINED AS DATABASE CHANGEIssued when the online change preparedetects that a DDIR in the MODBLKS data setthat is being added exists. If this situation doesoccur, it is probably an internal error. Onlinechange prepare is rejected.

ALREADY DEFINED AS DATABASE COMMITIssued when the online change commit detectsthat a DDIR in the MODBLKS data set that isbeing added exists. If this situation does occur,it is probably an internal error. Online changecommit proceeds in spite of this error. Oncea database is defined as a HALDB partition toDBRC and IMS, it remains defined to IMS as aHALDB partition until you cold start IMS andcannot be changed into a MODBLKS database,even if the HALDB partition is deleted fromDBRC.

ALREADY DEFINED AS PARTITION COMMITIssued when the online change commit detectsthat a member in the MODBLKS data set isdefined using the same name as an existingHALDB partition added since the preparephase. The HALDB partition definition prevails.Online change commit proceeds in spite ofthis error. Subsequent PREPARE commandsfail with DFS3498W DDIR dbname ALREADYDEFINED AS PARTITION CHANGE as long asthe database remains in the inactive MODBLKSdata set.

ALREADY DEFINED AS TRANSACTIONThis string is issued when a /MODIFY COMMITor INITIATE OLC PHASE(COMMIT) detectsthat a transaction being added by an onlinechange was added as a CPIC transaction bythe same name since prepare. Online Change

proceeds in spite of this error. The transactionremains a CPIC transaction. If you prefer theMODBLKS definition, define the transactionagain in the inactive MODBLKS dataset and doanother online change.

NOT IN ACTIVE LIBRARYIssued when /MODIFY PREPARE or INITIATEOLC PHASE(PREPARE) is specified with theBLDL option, to cause information messageDFS3498I to be issued for each PSB or DMBnot found in the inactive ACBLIB. This messagedoes not affect the success of the command.

NOT IN INACTIVE LIBRARYIssued when /MODIFY PREPARE or INITIATEOLC PHASE(PREPARE) is specified with theBLDL option, to cause information messageDFS3498W to be issued for each PSB or DMBnot found in the active ACBLIB. This messagedoes not affect the success of the command.

PDIR NAME IS INVALIDIssued when a transaction being added orchanged defines an application program namethat does not exist.

SID NUMBER IS INVALIDIssued when a transaction being added orchanged defines a SYSID that is larger thanthe maximum SYSID that was used at IMS coldstart.

SNO - COMPAREIssued when the online change comparefunction detects that a DMB or PSB inACBLIB is being changed, but cannot find theassociated local control block (DDIR or PDIR).This error should not occur (SNO), since thelocal control block did exist when the BLDL listwas built.

SNO - INSERT CHANGEIssued when online change tries to insert achanged DMB or PSB into the change list, butcannot find the associated local control block(DDIR or PDIR). This error should not occur(SNO) and usually indicates that the wrongMODBLKS data set is being used. It might alsoindicate an internal error.

SNO - INSERT DELETEIssued when online change tries to insert adeleted DMB or PSB into the delete list, butcannot find the associated local control block(DDIR or PDIR). This error should not occur(SNO) and usually indicates that the wrongMODBLKS data set is being used. It might alsoindicate an internal error.

SYSID CHNG IS INVALIDIssued when a transaction is being changedfrom local to remote and at least one other


type of change to the transaction or applicationprogram is being attempted as well.

UNSUPPORTED MSDB ADDITIONIssued when online change attempts to add,change, or delete an MSDB database inMODBLKS or DMB in ACBLIB, which is notsupported.

UNSUPPORTED MSDB CHANGEIssued when online change attempts to changean MSDB database in MODBLKS or DMB inACBLIB, which is not supported.

UNSUPPORTED MSDB DELETIONIssued when online change attempts to deletean MSDB database from MODBLKS or DMBfrom ACBLIB, which is not supported.

System actionFor a /MODIFY PREPARE or INITIATE OLCPHASE(PREPARE) command, the command isterminated. For a /MODIFY COMMIT command, theonline change commit succeeds, except for thespecified database. The database remains a HALDBpartition.

Programmer responseCorrect the problem, run the MODBLKS GEN orACBGEN again, run the Online Change utility, and retryonline change.

For a /MODIFY COMMIT command that failed withDFS3498W DDIR dbname ALREADY EXISTS ASPARTITION COMMIT, perform an online change toremove this database definition from your MODBLKSgen. Otherwise, each subsequent attempt to do anonline change will fail on the /MODIFY PREPAREcommand with DFS3498W DDIR dbname ALREADYEXISTS AS PARTITION CHANGE. Also, the databasereverts to a non-HALDB database at the next IMS coldstart.

For the warning SID NUMBER IS INVALID, generatea transaction with a SYSID that does not exceed themaximum SYSID. Or, cold start IMS with the MODBLKSdata set that contains the transaction defined with thehighest SYSID.

Module:DFSCPDD0, DFSRMDD0, DFSRMDM0, DFSRMPS0,DFSRMSM0

DFS3499I ACTIVE DDNAMES: modblks-name acblib-name format-nameMODSTAT ID: nnnn

ExplanationThis message indicates online change status includingthe active online change libraries and the currentmodify ID. IMS issues this message when the followingIMS commands are entered from the master terminalor system console:

• IMS restart• Simple checkpoint• /MODIFY PREPARE, to indicate the current active

online change libraries before the new definitionsare committed

• /MODIFY COMMIT, to indicate the new active onlinechange libraries, after online change is committed

In the message text:modblks-name

Active MODBLKS DD in the IMS JCL, that identifiesthe active MODBLKS library. modblks-name iseither MODBLKSA or MODBLKSB. If the MODBLKSDD cards are omitted from the IMS JCL and onlinechange for MODBLKS is disabled, this variable isblank.

acblib-nameActive IMSACB DD in the IMS JCL, that identifiesthe active ACBLIB library. acblib-name is eitherIMSACBA or IMSACBB.

format-nameActive FORMAT DD in the IMS JCL, that identifiesthe active MFS format library. format-name iseither FORMATA or FORMATB. If this system isDBCTL, format-name is blank.

nnnnModify ID number. When you initialize theMODSTAT data set, you decide what number toassign as the modify ID. Every time online changeis successful, this number increments by 1. If youinitialized this number to 0, the value indicateshow many online changes have been successfulsince cold start. The modify ID is used to recoversecurity status during an emergency restart.

This message is also issued after:

• Simple checkpoint invoked by /DBD• Simple checkpoint invoked by /DBR• Simple checkpoint invoked by /CHE

DFS3500W GLOBAL STATUS FOR rsrctypeRESOURCES IS DISABLED

ExplanationThe global status for database, DEDB area, ortransaction resources is disabled at this IMS. rsrctypecan be DB (database), AREA, or TRAN (transaction).


Any DB, AREA, or TRAN commands that are issued withSCOPE(ALL) are treated as SCOPE(ACTIVE), andglobal status is not updated. If a DB or AREA commandis issued as GLOBAL, global status is not updated.

System actionIMS continues restart processing.


If you want to maintain global status for commandsprocessed from this IMS, take the following actions:

1. Cancel IMS or shut down IMS after the restartcompletes After the error condition reported in theDFS3308 message is fixed, restart IMS. IMS is thensynchronized with the RM status and no additionalaction is required.

2. Allow IMS restart to complete. Then do thefollowing:

a. Correct the error condition reported in theDFS3308 message.

b. Issue the appropriate UPDATE IMSSET(PLEXPARM) command to enable globalstatus at this IMS.

c. Issue QRY TRAN (or DB or AREA)SHOW(GLOBAL) commands to see the resourceswith global status.

d. Issue the appropriate SCOPE(ACTIVE)commands to ensure this IMS is synchronizedwith RM status.

Module:DFSGST20





DFS3501W GLOBAL STATUS NOT OBTAINEDFOR xxxx RESOURCES ADDEDWITH ONLINE CHANGE

ExplanationOnline Change processing encountered an error tryingto determine the global status for added transaction ordatabase resources.


DB or TRAN, indicating either a database or atransaction

The added database or transaction status mightbe different from the status maintained in the RMresource structure.

A DFS3308 message might accompany this message,containing additional error information of any resourcemanager (RM) request errors and the RM return andreason codes.

System actionThe databases or transactions added by the onlinechange are available for use without the global statusfrom RM applied.

User response:Get the global status for the added transactionand database resources by issuing a QRY TRANSHOW(GLOBAL) or QRY DB SHOW(GLOBAL) to obtainthe information from RM. You can then use an UPDTRAN or UPD DB command with SCOPE(ACTIVE) andthe appropriate START or STOP to ensure that IMS issynchronized with RM global status.

Module:DFSGST40


DFS3503 Resource initialization is notcomplete, try the command again

ExplanationYour command cannot be completed because theresource needed has not been fully initialized.


Programmer responseTry the command again.

Module:DFSICL30

DFS3505E parmname=value IS NOTSPECIFIED IN PROCLIB MEMBERproclibmem, JOBNAME=job_name

ExplanationIf an error was found while processing DFSDFparameters from the PROCLIB data set, this messageis issued. If a required parameter is not enabled duringIMS or Batch initialization, then this message will betriggered.

If IMS management of ACBs is enabled, this messageis issued in the following scenarios:

• CATALOG=Y is specified in the CATALOG section ofthe DFSDFxxx member for a DCCTL environment.

• CATALOG=N is specified in the CATALOG sectionof the DFSDFxxx member for a non-DCCTLenvironment.

In the message text:parmname=value

Indicates the name of parameter in the PROCLIBmember that was not enabled.

proclibmemIndicates the name of the PROCLIB member.

job_nameIndicates the name of the job for whichinitialization failed.

System actionIMS initialization terminates with a 0071 abend.

System programmer responseCorrect the PROCLIB member definition, and try IMSinitialization again.

Module:DFS3DF00, DFS3DF10


Related referenceCATALOG and CATALOGxxxx sections of theDFSDFxxx member (System Definition)

DFS3507E parmname=value IS NOTSPECIFIED IN USER EXIT userexit,JOBNAME=job_name

ExplanationIf an error was found while processing Catalogdefinition User Exit, this message is issued. If arequired parameter is not enabled by the User Exitduring Batch initialization, then this message will betriggered.

If IMS management of ACBs is enabled withoutCATALOG being enabled, this message is also issued.

In the message text:parmname=value

Indicates the name of parameter in the User Exitdefinitions that was not enabled.

userexitIndicates the name of the PROCLIB member.

job_nameIndicates the name of the batch job for whichinitialization failed.

System actionBatch Job initialization terminates with a 0071 abend.

System programmer responseCorrect the User Exit parameter definition, and tryBatch Job again.

Module:DFS3DF10


DFS3511I ODBA failed to connect to ODBMfor reason: xxxxxxxxxxxx RC=nnnn

ExplanationDuring initialization of the database resource adapter(DRA), ODBA attempted to connect to ODBM. However,the attempt failed for one of the following reasons,which is indicated in the message after "reason":UNABLE TO OBTAIN STORAGE

Indicates that storage could not be obtained forthe DFSCDA block.

RRMS REGISTRATION FAILEDIndicates that the request to register to RRMSfailed.

ODBM REGISTRATION FAILEDIndicates that the request to register to ODBMfailed.

SCI REGISTRATION FAILEDIndicates that the request to register to SCI failed.

The return code nnnn provides additional informationabout the cause of the error:

• If the reason text is UNABLE TO OBTAIN STORAGE,nnnn is the return code from the STORAGE OBTAINservice.

• If the reason text is RRMS REGISTRATION FAILED,nnnn is 4 if the failure occurred because no CDA waspresent, or 8 if the error occurred because an invalidIMSplex name was specified.

• If the reason text is ODBM REGISTRATION FAILED,nnnn is the return code from the CSLSCQRY requestor 8 if the CSLSCQRY request is not the cause of thefailure.

• If the reason text is SCI REGISTRATION FAILED,nnnn is the return code from the CSLSCREG request.

System actionInitialization continues using the normal ODBA path.Transactions are sent directly to ODBA instead ofbeing routed through ODBM.


Severity:8

DFS3513E THE DIRECTORY DATA SETNAMES IN THE FAILED IMSAND THE TRACKING IMS DONOT MATCH. UOW ABORTED.TOKEN=cccccccccccccccc.

ExplanationThe high level qualifier in the name of the IMSdirectory data set of the failed IMS does not matchthe high level qualifier in the name of the IMS directorydata set of the Fast Database Recovery (FDBR) region.

In the message text:cccccccccccccccc

The member online change (MOLC) unit of work(UOW) token.


http://www.ibm.com/support/knowledgecenter/SSEPH2_15.1.0/com.ibm.ims15.doc.sdg/ims_dfsdfxxx_proclib_catalog.htm#ims_dfsdfxxx_proclib_catalog




System actionThe FDBR region cannot complete the member onlinechange unit of work (UOW). When the failed IMS isrestarted, IMS will commit the unit of work.

System programmer responseThe content of the <CATALOG> section of theDFSDFxxx member that is used by the restarted IMSmust be identical to the DFSDFxxx member that wasused by the failed IMS. Correct any discrepancy andrestart IMS.

Module:DFSMOL20

Related conceptsIMS directory data sets (System Definition)Related referenceCATALOG and CATALOGxxxx sections of theDFSDFxxx member (System Definition)

DFS3515E BLDL PROCESSING FOR rsc_nameENCOUNTERED AN I/O ERROR INTHE DIRECTORY DATA SET THATIMS CANNOT FIX.

ExplanationWhile the system was searching the IMS directory, anI/O error occurred that IMS cannot fix.

In the message text:rsc_name

The name of the DBD or PSB resource that isassociated with the I/O error.

System actionThe IMPORT command or the automatic activation ofthe DDL definitions ends abnormally.

System programmer responseThe IMS directory data sets must be rebuilt by runningthe IMS Catalog ACB Recovery utility.

Module:DFSMOLS0

Related informationIMS directory data sets (System Definition)

DFS3521W CHECKPOINT IS REJECTED –DEDB ALTER IS IN PROGRESS

ExplanationThe checkpoint request was rejected because theDEDB Alter utility was running.

System actionThe /CHECKPOINT command fails.

Programmer responseEnter the /CHECKPOINT command after the DEDBAlter utility ends.

ModuleDFSRCP00, DFSICM30

Related referenceDEDB Alter utility (DBFUDA00) (DatabaseUtilities)/CHECKPOINT command (Commands)

DFS3523W CA RECEIVED RC mmmm RSNnnnn FROM INIT DBRC DUE TOEXTRA LOGS IN JCL

ExplanationChange Accumulation utility module DFSUCMN0 madean Init DBRC call and received reason code 1, whichindicates that there are more logs in the DFSULOG DDstatement than DBRC allows.

In the message text:mmmm

Indicates the return code that is returned fromDBRC.

nnnnIndicates the reason code that is returned fromDBRC.

This condition is a result of the time that is elapsedbetween execution of the GENJCL.CA command andthe Change Accumulation utility, during which thestate of the RECON data set changed. If the two stepsare run one after the other, this condition should notoccur.

System actionProcessing terminates with RC=03.

Programmer response:Rerun the GENJCL.CA command and the ChangeAccumulation utility in succession.

Module:DFSUCMN0

Related referenceDatabase Change Accumulation utility(DFSUCUM0) (Database Utilities)


http://www.ibm.com/support/knowledgecenter/SSEPH2_15.1.0/com.ibm.ims15.doc.sdg/ims_catalog_directory.htm#ims_catalog_directory






http://www.ibm.com/support/knowledgecenter/SSEPH2_15.1.0/com.ibm.ims15.doc.cr/imscmds/ims_checkpoint.htm#ims_cr1checkpoint

http://www.ibm.com/support/knowledgecenter/SSEPH2_15.1.0/com.ibm.ims15.doc.dur/ims_dfsucum0.htm#ims_dfsucum0

http://www.ibm.com/support/knowledgecenter/SSEPH2_15.1.0/com.ibm.ims15.doc.dur/ims_dfsucum0.htm#ims_dfsucum0

DFS3525E IMS COULD NOT REGISTERWITH ENF FOR RACF EVENTNOTIFICATION, RC=ret_code.

ExplanationDuring IMS initialization, IMS attempted to registerwith the z/OS event notification facility (ENF) to listenfor notifications of changes to the OTMA securitydefinitions in RACF, but the attempt to register failed.IMS registers with ENF so that the OTMA cachedACEEs can be automatically refreshed when changesto the RACF definitions occur.

In the message text:ret_code

The ENFREQ return code that is received fromz/OS. The z/OS ENFREQ macro is used by z/OSsubsystems to register with ENF.

System actionInitialization continues, but OTMA cached ACEEs willnot be refreshed automatically when changes aremade to their corresponding RACF definitions.

System programmer responseLook up the ENFREQ return code in z/OSMVS Programming: Authorized Assembler ServicesReference Vol 2.

Module:DFSYCTL0

DFS3527E THE OLCSTAT DATA SET NAME ISNOT SPECIFIED

ExplanationDFSUOCU0 is invoked with the &OUT parameter G,which indicates that the target library is indicated bythe OLCSTAT data set. However, the OLCSTAT data setname is not specified. Either the OLCSTAT data set isnot specified with the OLCSTAT DD statement or theSYSIN DD statement, or the SYSIN DD statement isspecified, but the OLCSTAT data set name does notstart in column 1.

System actionThe copy is not done, and the utility is terminated.

System programmer responseSpecify the OLCSTAT data set name in the SYSIN DDstatement data area, starting in column 1, so that theOLCSTAT data set can be dynamically allocated.

Alternatively, specify the OLCSTAT data set name withthe OLCSTAT DD statement so that the job allocatesthe OLCSTAT data set.

Module:DFSUOCU0

DFS3529 /TRACE SET ON FOR MONITORIN PROGRESS, CANNOT PROCESSCOMMAND

ExplanationThe /TRACE SET OFF MONITOR command wasentered before a previous /TRACE SET ON MONITORcommand completed.


Operator response:Reenter the command.

Programmer response:If commands are entered through an automationprogram, change the program to increase the timebetween the /TRACE SET ON MONITOR commandand the /TRACE SET OFF MONITOR command.

Module:DFSICLN4

DFS3531E MAXIMUM NUMBER OF OTMATMEMBERS REACHED. NO NEWTMEMBERS CAN BE CREATED

ExplanationIMS OTMA has reached the maximum number ofTMEMBERs and will not allow any more to join.

System actionNew client bid requests will be rejected with OTMANAK X'0007'. IMS transactions on shared queuesback-end systems that require a new TMEMBER willbe rejected with abend U0367.

System programmer responseOTMA TMEMBERs are rebuilt across IMS warm andemergency restarts. It requires an IMS cold start toreset the OTMA TMEMBERs. Until then, route requeststhat require a new TMEMBER to other IMS systems.

Module:DFSYMOM0

DFS3535E DFS3535E BLDL PROCESSING FORrsc_name ENCOUNTERED AN I/O


ERROR IN THE STAGING DATA SETTHAT IMS CANNOT FIX.

ExplanationWhile the system was searching the staging data set,an I/O error occurred that IMS cannot fix.


The name of the DBD or PSB resource that isassociated with the I/O error.


System programmer responseThe IMS staging data set must be rebuilt by runningthe IMS Catalog ACB Recovery utility.

Module:DFSMOLS0

DFS3537E AUTOMATIC ACTIVATION OF DDLDEFINITIONS FAILED. CHANGEDPSB psb_name REFERENCES ADELETED DBD dbd_name. REGIONregionname

ExplanationThe PSB psb_name references a database that wasdeleted from IMS.

In the message text:dbd_name

The name of the database that was deleted.psb_name

The psb_name that is being changed thatreferences the deleted database.

System actionThe automatic activation of the PSB change failed. Anyuncommitted work is backed out from the IMS catalog.

Programmer responseIn the statement psb_name, delete the statementsthat reference the deleted database. After youcomplete the corrections, resubmit the DDL or thechange to the PSB.

Module:DFSOLC70

Related referenceCREATE PROGRAMVIEW (ApplicationProgramming APIs)

DFS3539E AN I/O ERROR OCCURRED FORMEMBER rsc_name ON THESTAGING DATA SET.

ExplanationAn I/O error occurred when IMS attempted to accessthe staging data set.


The name of the DBD or PSB resource thatexperienced the I/O error.

System actionThe IMPORT command or the DDL activation processends abnormally.

Programmer responseIf the staging data set was taken offline by the z/OSsystem administrator, have the data set brought backonline. Otherwise, restore or rebuild the IMS directorydata sets. After the data set is online or the IMSdirectory is restored, resubmit the IMPORT commandor the DDL definition statements.

Module:DFSMOLS0


DFS3541E AN I/O ERROR OCCURRED FORRESOURCE rsc_name ON THEDIRECTORY DATA SET.

ExplanationAn I/O error occurred when IMS attempted to accessthe directory data set.


The name of the DBD or PSB resource thatexperienced the I/O error.



http://www.ibm.com/support/knowledgecenter/SSEPH2_15.1.0/com.ibm.ims15.doc.apr/ims_sql_create_programview.htm#ims_sql_create_programview

http://www.ibm.com/support/knowledgecenter/SSEPH2_15.1.0/com.ibm.ims15.doc.apr/ims_sql_create_programview.htm#ims_sql_create_programview


Programmer responseIf the IMS directory data set is offline, bring it online.Otherwise, restore or rebuild the IMS directory datasets.

Resubmit the IMPORT command or the DDL definitionstatements. During the processing of the resubmittedchanges it is normal to see reason code 121 (resourcehas no change) in the SPOC output or messageDFS4387I.

Module:DFSMOLS0


DFS3542I THE NAME OPERAND ISOMITTED OR INVALID ONTHE FOLLOWING MSPLINKSTATEMENT(S): STATEMENT NOS -nnn,...

ExplanationOne of the following occurred on each statementindicated by nnn:

• The NAME keyword parameter was specified butTYPE=VTAM was not indicated.

• The NAME keyword parameter was not specified byTYPE=VTAM was indicated.

• More than one NAME operand was specified.• The operand did not begin with an alphabetic

character or contained more than 8 alphanumericcharacters.

System actionThe NAME parameter is ignored on the indicatedstatement, and processing continues.

Programmer responseSpecify the NAME parameter with TYPE=VTAM or, ifspecified, ensure that it begins with an alphabeticcharacter and contains no more than 8 alphanumericcharacters.

Severity:8

DFS3543I UOW IGNORED. TIMESTAMP INTHE DIRECTORY DATA SETS DOESNOT MATCH THE LOG RECORD7002. TOKEN=cccccccccccccccc

ExplanationThe timestamp of a member in the IMS directorydoes not match the timestamp in log record 7002.This UOW might have been completed by another taskwhile this IMS was down.



System actionDuring the IMS restart or the FDBR take over, theprocessing of the UOW from either an IMPORTcommand or an automatic DDL activation is skipped.


Module:DFSMOL20

DFS3544I DUPLICATE VTAM NODENAMES ARE SPECIFIED ONTHE FOLLOWING MSPLINKSTATEMENTS: NAME - name1STATEMENT NOS - nnn,... NAME -name2 STATEMENT NOS - nnn,...

ExplanationThe remote system VTAM node name indicated bynamex was specified on multiple MSPLINK macros onstatements nnn.


Programmer responseCorrect VTAM node name specifications on indicatedMSPLINK statements to remove duplicates.

Severity:8

DFS3545 ACBLIB KEYWORD IS INVALIDWHEN THE IMS DIRECTORY ISENABLED

ExplanationThe ACBLIB keyword is invalid on the /MODIFYcommand because the IMS system is configured touse the IMS directory instead of an ACB library.




User responseReissue the /MODIFY command without the ACBLIBkeyword.

Module:DFSICV10

Related reference/MODIFY command (Commands)

DFS3547E UNABLE TO LOAD ALTEREDDEFINITIONS FOR DATABASEdb_name, RSN=rsn

ExplanationIn an attempt to satisfy a request to access a databasethat is currently being altered, IMS was unable to loadthe data management block (DMB) that contains thenew structure of the database from the ACB staginglibrary.

In the message text:rsn

The reason code that identifies the cause of theload error. See the list below for an explanation ofeach reason code.

Possible cause: The possible cause is indicated bythe reason code included in the message text. Thepossible causes include:

1Dynamic allocation of the staging ACB libraryfailed. See message DFS2503W for moreinformation.

2Dynamic deallocation of the staging ACB libraryfailed. See message DFS2503W for moreinformation.

3The staging ACB library failed to open. SeeDFS0730I for more information.

4An I/O error occurred while attempting to loadfrom the staging ACB library. Check the volumewhere the data set is located.

5The requested DMB was not found in the stagingACB library or the staging ACB library is empty.Ensure that the staging ACB library contains theACB member for the database identified in themessage text.

6An error occurred while reading the requestedDMB from the staging ACB library. Check thevolume where the data set is located.

7An error occurred while resolving the DMB inmemory. The DMB loaded from the stagingACB library is not in the expected format. Tryregenerating the ACB member by using an IMSVersion 13 or later system.

8Unable to obtain storage. This is probably aninternal error.

9The requested member does not appear to bedefined to IMS. This is probably an internal error.

10Internal parameter list error occurred. This isprobably an internal error.

System action:The DMB for the altered database is not loaded.The database authorization attempt fails. IMS issuesDFS047A.

System programmer responseLook up the reason code in the preceding list todetermine the cause of the error. Check for any z/OSmessages that indicate the cause of the failure.

Ensure that the necessary members are in thestaging ACB library. Ensure the staging ACB library isaccessible to IMS and included in the MDA member.

If the problem persists, call IBM Software Support.

Problem determination:1, 9, 18, 19, 36, 40.

Module:DFS5OP00

Related information“DFS047A” on page 35UNABLE TO OBTAIN AUTHORIZATION FORDATA BASE xxxxxxxx. REASON CODE = zz. PSB=psbname.“DFS2503W” on page 719DYNAMIC action_type FAILEDFOR DATA SET NAMExxxxxxxx.xxxxxxxx.xxxxxxxxDATABASE NAME dbdname REASON CODEyyyyy“DFS0730I” on page 257


http://www.ibm.com/support/knowledgecenter/SSEPH2_15.1.0/com.ibm.ims15.doc.cr/imscmds/ims_modify.htm#ims_cr1modify

UNABLE TO OPEN OR CLOSE DATASET WITHDDNAME ddname FOR REASON x, yy, zDATABASE dbdname programid“IMS problem determination” on page 11IMS messages and codes problemdetermination is accomplished by usingprocedures established by IBM.

DFS3549E DB VERSIONING ERROR:RS=rsnc PST=pstno PSB=psbnameDB=dbname VERSN=vernumSEGM=segmname

or

DB VERSIONING ERROR: RS=rsnc PST=pstnoPSB=psbname DB=dbname VERSN=vernumSEGM=segmname FIELD=fld_name

ExplanationAn application program attempted to access a priorversion of a High Availability Large Database (HALDB),but IMS cannot build the internal blocks that arerequired to access prior versions of the database,because the latest version of the database containsa change in the database definition (DBD) that is notsupported by database versioning.



The name of the database that contains theunsupported change.

fld_nameThe name of the field that contains theunsupported change.

psbnameThe name of the PSB that specifies that databaseand version that the application program is tryingto access.

pstnoThe PST number relative to zero.

rsncThe reason code that identifies the DBD changethat is not supported by the ALTER option. See thefollowing list of reason codes for an explanation ofeach code.

segmnameThe name of the segment that contains theunsupported change.

vernumThe version number of the database version thatthe application program was trying to access.

Reason codeUnsupported change

3The exit routine changed.

4The number of segments changed.

9The segment was changed from fixed length tovariable length or vice versa.

10The insert rule changed.

11The delete rule changed.

12The segment code changed

14A secondary index was added or changed. Eitherthe SRCH operand, the SUBSEQ operand, or theDDATA operand references the newly added fields.

16The name of the segment was changed, or a fieldin the segment was either deleted or moved toanother segment.

17The key length of the field changed.

18The field length changed.

19The value of the TYPE keyword on the FIELDstatement changed.

22The segment length is truncated.

23Either the length of a fixed-length segment thatis involved in a logical relationship changed(excluding secondary index) or the minimum ormaximum length of a variable-length segmentchanged.

System actionIMS cannot build the internal blocks that are requiredto provide access to prior versions of the database.Only the most recent version of the database can beaccessed.


IMS returns a status code to the application programor the application code abends.

System programmer responseDetermine whether you need to keep the changes inthe database or remove them.

Keeping the changes requires all application programsto be modified to access the new database structure.The prior versions of the database cannot be accessedanymore.

Removing the changes allows you to enable databaseversioning. However, if the database was updatedsince the changes were made, you must recover the

physical database to the prior version. Any updates tothe database that were made by application programsthat used the current version of the database are lost.

Module:DFS5DBB0

Related conceptsDatabase modifications supported by databaseversioning (Database Administration)Related information“IMS problem determination” on page 11IMS messages and codes problemdetermination is accomplished by usingprocedures established by IBM.






DFS3551E CATALOG=Y CANNOT BESPECIFIED IN A DCCTL SYSTEM.

ExplanationA DCCTL IMS system was brought online with aDFSDFxxx member that has ACBMGMT=CATALOGand CATALOG=Y specified. The IMS catalog is notsupported in DCCTL systems.

System actionThe IMS system terminates with a U0071 abend.

Programmer responseCorrect the above parameters from the DFSDFxxxmember and bring up the DCCTL IMS system again.

Module:DFSRDB30

Related conceptsDCCTL environment (System Administration)Related referenceCATALOG and CATALOGxxxx sections of theDFSDFxxx member (System Definition)

DFS3553E AN ISC TCPIP SESSION FAILEDTO INITIATE - NODE = nodenameUSER = username RSNCD=nnn

ExplanationAn ISC TCP/IP session failed to start. The request tostart the session might have originated in IMS or in aremote session partner, such as a CICS subsystem.

In the message text:nodename

The node name used in the request to start the ISCTCP/IP session.

For requests that originate from IMS, the nodename displayed in the message text might beprovided by a Logon exit routine (DFSLGNX0),a logon descriptor, the NODE keyword in an /OPNDST command, or by the NAME keyword in aTERMINAL system definition macro.

For requests that originate from the sessionpartner, the node name displayed in the messagetext is provided by the session partner.

usernameThe user name associated with the sessioninitiation request.

nnnThe reason code that describes the possiblecause of the failure. The possible codes and theirmeanings include:003

IMS data communications processing has notbeen started. Issue the /START DC commandand attempt to initiate the session again.

004An SOPB storage request failed for a newlycreated IMS terminal control block. This erroris an internal error. Collect the documentationindicated in the problem determination sectionand contact IBM Software Support forassistance.

005An installation-supplied Logon exit routine(DFSLGNX0) specifies both AUTOSIGN andNOAUTSGN for a static ISC TCP/IP terminal.The AUTOSIGN and NOAUTSGN values aremutually exclusive.

007The session partner attempted to start anISC TCP/IP session with a terminal that isnot statically defined to IMS and ETO is notenabled in this IMS system. Either staticallydefine a terminal by coding the TYPE andTERMINAL system definition macros and theISCTCPIP keyword in the DFSDCxxx PROCLIBmember, or enable ETO dynamic terminals byspecifying ETO=Y in the IMS or DCC startupprocedure and coding an ETO logon descriptorfor the terminal.

009The system latch cannot be obtained.This error is an internal error. Collect thedocumentation indicated in the problemdetermination section and contact IBMSoftware Support for assistance.

010An installation-supplied Logon exit routine(DFSLGNX0) rejected the logon attempt of arequest to start an ISC TCP/IP session. Reviewthe code of the DFSLGNX0 exit routine todetermine why the logon attempt was rejected.


http://www.ibm.com/support/knowledgecenter/SSEPH2_15.1.0/com.ibm.ims15.doc.sag/system_intro/ims_dcctl_over.htm#ims_dcctl_over



011No logon descriptor was found.

012An IMS terminal control block cannot beobtained. This error is an internal error.Collect the documentation indicated in theproblem determination section and contactIBM Software Support for assistance.

013The internal dispatcher prefix block cannotbe located. This error is an internal error.Collect the documentation indicated in theproblem determination section and contactIBM Software Support for assistance.

014IMS failed to hash the IMS terminal controlblock. This error is an internal error. Collectthe documentation indicated in the problemdetermination section and contact IBMSoftware Support for assistance.

015The session partner attempted to start an ISCTCP/IP session with a node that does notsupport ISC TCP/IP.

016The ISC TCP/IP node is stopped.

017A /CLSDST command was issued todisconnect the target node.

018A TCPWORK storage request failed for a newlycreated IMS terminal control block. This erroris an internal error. Collect the documentationindicated in the problem determination sectionand contact IBM Software Support forassistance.

019A TCPWORK storage request failed for anexisting IMS terminal control block. This erroris an internal error. Collect the documentationindicated in the problem determination sectionand contact IBM Software Support forassistance.

022The request to start a session specified a nodename that has one or more existing sessions.The logon descriptor specified in this requestis different from the logon descriptor in useby the existing sessions that are active withthis node. Change the logon descriptor thatis used in the request to start a session orspecify a different node name. To see the logondescriptor that is currently in use by this node,use the QUERY NODE command.


System programmer responseFind the reason code that was displayed in themessage text in the preceding list for an explanationof the possible cause of the error and what actions youcan take.


Module:DFSTCPS0

Related tasksISC support for TCP/IP (Communications andConnections)Related referenceQUERY NODE command (Commands)Related information“IMS problem determination” on page 11IMS messages and codes problemdetermination is accomplished by usingprocedures established by IBM.

DFS3555E AN INTERNAL ISC TCPIP ERRORWAS DETECTED - NODE =nodename USER = usernameRSNCD=nnn

ExplanationAn ISC TCP/IP session failed.

In the message text:nodename

The node name of the ISC TCP/IP session.

For sessions that are initiated from IMS, the nodename displayed in the message text might beprovided by a Logon exit routine (DFSLGNX0),a logon descriptor, the NODE keyword in an /OPNDST command, or by the NAME keyword in aTERMINAL system definition macro.

For sessions that initiated from the sessionpartner, the node name displayed in the messagetext is provided by the session partner.

usernameThe user name associated with the session.

nnnThe reason code that describes the possiblecause of the failure. The possible codes and theirmeanings include:001

An invalid message was received from theremote system. This error is an internal error




http://www.ibm.com/support/knowledgecenter/SSEPH2_15.1.0/com.ibm.ims15.doc.cr/imscmds/ims_querynode.htm#ims_querynode

encountered by IMS or the session partner.Collect the documentation indicated in theproblem determination section and contactIBM Software Support for assistance.

002The IPIC request segment IS-06 was notfound in the input message received fromthe remote system. This error is an internalerror. Collect the documentation indicated inthe problem determination section and contactIBM Software Support for assistance.

008A destination IMS terminal control blockcannot be found. Either the target terminal isnot statically defined or its dynamic terminalcontrol block does not exist.

021IMS received a negative response from eitherIMS Connect or the session partner.


System programmer responseFind the reason code that was displayed in themessage text in the preceding list for an explanationof the possible cause of the error and what actions youcan take.


Module:DFSTCPS0

Related tasksISC support for TCP/IP (Communications andConnections)Related referenceQUERY NODE command (Commands)Related information“IMS problem determination” on page 11IMS messages and codes problemdetermination is accomplished by usingprocedures established by IBM.

DFS3561E INSUFFICIENT STORAGE ABOVE16 MEG FOR PSB xxxxxxxx.

ExplanationThe block builder was unable to obtain sufficientstorage above 16 MB to build the required PSB controlblock. In the message text, xxxxxxxx identifies the PSBblock.


Programmer responseIncrease the region or partition size, and run theprogram again.

DFS3563I bbb NAME nnnnnnnn NOT FOUND.

ExplanationDFSIIRS0 was not able to find the name nnnnnnnn ofcontrol block bbb. The possible control blocks are CNT,CLB, or LNB.

System actionThe IMS initialization is terminated with an abend codeof 0220.

Programmer responseEnsure that the correct set of control blocks from asystem definition is being used. Verify the SUFFIXspecification in System Definition, and the SUFspecification in the IMS procedure.

Severity:8


DFS3565E INSUFFICIENT STORAGE ABOVE16 MEG FOR DBD xxxxxxxx.

ExplanationThe block builder was unable to obtain sufficientstorage above 16 MB to build the required DBD controlblock. In the message text, xxxxxxxx identifies theDBD block.


Programmer responseIncrease the region or partition size, and run theprogram again.

DFS3571A THE OPCODE ON THE FOLLOWINGSTATEMENT IS INVALID.

ExplanationAn OPCODE that exceeded eight characters was found.




http://www.ibm.com/support/knowledgecenter/SSEPH2_15.1.0/com.ibm.ims15.doc.cr/imscmds/ims_querynode.htm#ims_querynode


System actionNames checking continues, but the Stage 2 input is notgenerated.

Programmer responseCorrect the OPCODE in error and re-execute thepreprocessor.

Severity:8

DFS3573A MISSING PARM FIELD ERRORDETECTED.

ExplanationOne of the input parameters was missing from theDFSLGD00 utility JCL.

System actionProcessing terminates with return code 8.

Programmer responseCorrect the proper parameter and rerun the job.

Severity:8

DFS3575I UOW IGNORED. TIMESTAMP INSTAGING DATA SET DOES NOTMATCH THE LOG RECORD 7002.TOKEN=cccccccccccccccc

ExplanationThe member timestamp of a member in the stagingdata set of the IMS directory does not match thetimestamp in log record 7002. This UOW might havebeen completed by another task while this IMS wasdown.



System actionDuring the IMS restart or the FDBR take over, theprocessing of the UOW from either an IMPORTcommand or an automatic DDL activation is skipped.


Module:

DFSMOL20

DFS3576A OPEN ERROR FOR DDNAMExxxxxxxx

ExplanationAn open error occurred in module DFSLGD00.

System actionProcessing terminates with return code 12.

Programmer responseCorrect the DDNAME in error and rerun the job.

Severity:12

DFS3578A OPEN ERROR FOR DDNAME =ddname RETURN CODE = 12

ExplanationAn attempt to open a BPAM data set failed. Returncode 12 is a Sort/Split utility return code, not a returncode from OPEN.

System actionThe utility function was terminated.

Programmer responseSee Data Administration: Macro Instruction Referencefor MVS/DFP (SC26-4506).

DFS3579I USER EXIT2 REQUEST = 90FROM DFSSS060. INPUT IS NOTIN STANDARD FORMAT, ENDSTATEMENT MISSING. RESOURCETYPE = resource type.

ExplanationReturn code 90 signals the SORT/SPLIT utility toprocess the current user resource type as a standardresource. In this case, the exit routine is not called forthe remainder of the current user resource type. Thismessage warns you that the END statement is missing,which might cause compiler errors after the Sort/Splitutility completes. A report is generated.

System actionThe SORT/SPLIT utility generates return code 02.Processing continues.


Programmer responseIf a compiler error occurs, you must add an ENDstatement either through the initial input to Stage 1or through exit routine 2. If you add the END statementthrough the exit routine, you must also put it at the endof each member.

DFS3580A READ ERROR IN RESOURCEINFORMATION FILE. MEMBERNAME = member name RETURNCODE = 12

ExplanationA read error in the resource information file (RIFL) iscaused by the one of the following:

• The record was not found.• An I/O error occurred.• The first record is not the RIFL record.

A report is not generated. Return code 12 is a Sort/Split utility return code, not an I/O return code.


Programmer responseReview the RIFL to ensure that the first recordis the RIFL record and that it contains thenumber of resource types found in the RIFL. Formore information, see Data Administration: MacroInstruction Reference for MVS/DFP.

DFS3581A READ ERROR. MEMBER NAME =member name RETURN CODE = 12

ExplanationAn I/O error occurred during the read of a block froman input member. Return code 12 is a Sort/Split utilityreturn code, not an I/O return code.

System actionProcessing is terminated.

Programmer responseSee the Data Administration: Macro InstructionReference for MVS/DFP.

DFS3581W READ ERROR. MEMBER NAME =member name RETURN CODE = 04

ExplanationPremature end of file. One of the following conditionsoccurred. End of file was reached while: reading thefirst block of a member; there were no more blocks toread, but the record count in the Resource InformationFile has not yet been met; a complete multi-recordresource has not been read.

Return code 04 is a Sort/Split utility return code, notan I/O return code.

System actionStop processing this resource type. The Sort/Splitutility does not sort or write any further resourcetypes. However, the utility continues to read theresource types and verify the read counts. A report isgenerated.

Programmer responseDetermine if the resource read count in the RIFL iscorrect. Verify the input resource record count anddetermine if records are missing or the count is wrong.

DFS3582W WRITE ERROR. MEMBER NAME =member name RETURN CODE = 04

ExplanationAn I/O error occurred while attempting to write ablock.

Return code 04 is a Sort/Split utility return code, notan I/O return code.


Programmer responseSee Data Administration: Macro Instruction Referencefor MVS/DFP for more information.

DFS3583A GETMAIN FAILED. STORAGEREQUESTED = bytes of storageSTORAGE ALREADY GETMAINEDlocation of storage 16M LINE= accumulated bytes of storageRETURN CODE = 12


ExplanationThe amount of storage already obtained by GETMAINplus the amount requested exceeds the total storageavailable. A report is generated. Return code 12 is aSort/Split utility return code, not a return code fromGETMAIN.


Programmer responseIncrease the region size and re-execute the utilityfunction.

DFS3584A FIND ERROR. MEMBER NAME =member name RETURN CODE = 12

ExplanationThe resource information file (RIFL) member was notfound. Return code 12 is a Sort/Split utility returncode, not a return code from FIND.


Programmer responseEnsure that the member name, including the suffix ofthe RIFL member name, is correct in Stage 1.

DFS3584W FIND ERROR. MEMBER NAME =member name RETURN CODE = 04

ExplanationA member for a resource type was not found. Returncode 04 is a Sort/Split utility return code, not a returncode from FIND.


Programmer responseEnsure that the correct number of members, andmember names, are generated by Stage 1.

DFS3585I STOW DELETE FAILED. MEMBERNAME = member name RETURNCODE = 02

ExplanationSTOW DELETE failed while deleting a user resourcetype member from the input data set as a clean-upprocedure. Return code 02 is a Sort/Split utility returncode, not a return code from STOW.

System actionThe utility function continues.


DFS3585W STOW stow function FAILED.MEMBER NAME = member nameRETURN CODE = 04


• STOW ADD return code is greater than 4.• A return code greater than 8 was returned from a

STOW REPLACE after a STOW ADD returned a returncode of 4.

• STOW REPLACE return code is greater than 8.• STOW DELETE return code is greater than 8.

Return Code 04 is a Sort/Split utility return code, not areturn code from STOW.

System actionStop processing this resource type. The Sort/Splitutility does not sort nor write any further resourcetypes. However, the utility continues to read theresource types and verify the read counts. A report isgenerated.

Programmer responseSee Data Administration: Macro Instruction Referencefor MVS/DFP.

DFS3586W SORT ERROR. RESOURCE TYPE =resource type RETURN CODE = 04

ExplanationThe count passed to DFSSS030 was either greaterthan the maximum allowable or less than theminimum allowable. Return code 04 is from the Sort/Split utility.


System actionStop processing this resource type. The Sort/Splitutility does not sort nor write any further resourcetypes. However, the utility continues to read theresource types and verify the read counts. A report isgenerated.

Programmer responseRerun the Stage 2 from beginning. If the problempersists, then rerun Stage 1 from the beginning.

DFS3587I MEMBER ALREADY EXISTS ANDWAS REPLACED. MEMBER NAME =member name.

ExplanationThis message is issued during a cleanup procedure.Return code 02 is from the Sort/Split utility.



DFS3588W EXPECTED record type RECORDNOT FOUND AT input RECORDLOCATION resource read countRESOURCE TYPE = resource typeRETURN CODE = 04

ExplanationA record type of CSECT, GEN, END, or LAST was notfound where expected in the input file.

Return code 04 is from the Sort/Split utility.

System actionStops processing this resource type. The Sort/Splitutility does not sort or write any further resourcetypes. However, the utility continues to read theresource types and verify the read counts. A report isgenerated.

Programmer responseEnsure that the record specified is in the correctlocation in the input file during Stage 1. Stage 1 mighthave passed an incorrect count, whereby the numberof records is either greater or less than the actualcount.

DFS3589A INVALID RESOURCE TYPE FROMRESOURCE INFORMATION FILE.RESOURCE TYPE = resource typeRETURN CODE = 12

ExplanationAn unrecognized resource type was passed by Stage 1.Return code 12 is from the Sort/Split utility.


Programmer responseEnsure that the resource types passed to Sort/Splitutility conform with guidelines.

DFS3590A INVALID COUNT(S) FROMRESOURCE INFORMATION FILE.RESOURCE TYPE = resource typeRETURN CODE 12

ExplanationA problem was encountered with a resourceinformation file. One or more of the following stringsshown in the message indicate what was incorrect:

• RECORD COUNT: Count is not greater than zero.• RECORDS PER RESOURCE: Count is less than one or

greater than nine.• MEMBER COUNT: Count is less than one or greater

than nine.• SPLIT COUNT: Count is not greater than zero.

Return code 12 is from the Sort/Split utility.


Programmer responseEnsure that the input counts are within the guidelines.

DFS3591W INVALID RETURN CODE URC =user exit return code FROM userexit module. RESOURCE TYPE =resource type RETURN CODE = 04

ExplanationDFSSS050 or DFSSS060 issued a return code that wasnot in the guidelines. Return code 04 is from the Sort/Split utility.


System actionStop processing this resource type. The Sort/Splitutility does not sort nor write any further resourcetypes. However, the utility continues to read theresource types and verify the read counts. The exitroutines are not called for this job. A report isgenerated.

Programmer responseEnsure that only those return codes allowed from theexit routines are used.

DFS3592A THE RECFM FORDDNAME=ddname IS NOT F OR FBRETURN CODE=12

ExplanationThe LGENIN and LGENOUT data sets must have a DCBparameter of RECFM=F or RECFM=FB.


Programmer responseRedefine the indicated data set with a RECFM=F orRECFM=FB.

Severity:12

DFS3594E AN ISC CSLSCMSG REQUESTFAILED, active_process, RETCODE= rc, RSNCODE = rsn, LOSTSESS= cause, MODULE =mod_name ,NODE = nodename , USER =username

ExplanationSCI returned a non-zero return code or reason code toIMS in response to a CSLSCMSG request for servicesfor an ISC TCP/IP parallel session. The terminalsession is terminated.


The ISC process that was active when the erroroccurred. Possible values include:SENDMSG

When SCI encountered the error, ISC wasattempting to send an ISC message to aremote CICS system by way of the parallelsession identified in the message text.

SESSTERMWhen SCI encountered the error, ISC wasattempting to notify IMS Connect and theremote CICS subsystem that the terminalsession was terminated.

SESSINITWhen SCI encountered the error, ISC wasattempting to notify IMS Connect and theremote CICS system of the session initiationof the parallel session terminal identified in themessage text.

UNKNOWNDisplayed when the error occurredduring an unidentifiable ISC process. Thetroubleshooting and recovery procedure is thesame as for the regular active process types.






SCIABEThe SCI instance that is managingcommunications between IMS and thelocal IMS Connect instance terminatedunexpectedly.

SCISTOPThe SCI instance that is managingcommunications between IMS and the localIMS Connect instance was shut down.

usernameThe name of the affected user..

mod_nameThe name of the module that detected the error.

nodenameThe name of the affected parallel session..

rcThe CSLSCMSG return code issued by SCI.

rsnThe CSLSCMSG reason code issued by SCI.

Possible cause: The cause of this message is identifiedby the SCI return and reason codes and possibly by


the value that is displayed in the LOSTSESS field in themessage text.

System actionThe terminal session is terminated. IMS processingcontinues.

System programmer responseDetermine the cause of the error from the RETCODE,RSNCODE, and LOSTSESS values. The problem couldbe in either the local or remote IMSplex network. Lookup the return and reason codes for the CSLSCMSGrequest. Check for other messages from SCI, IMSConnect, or TCP/IP that might help with the diagnosis.Collect the X'6701' error records from the IMS log.


Module:DFSCTER0

Related referenceCSLSCMSG: send message request (SystemProgramming APIs)Related information“IMS problem determination” on page 11IMS messages and codes problemdetermination is accomplished by usingprocedures established by IBM.

DFS3595E IMS CONNECT ERROR MESSAGERECEIVED, active_process,RETCODE = rc, RSNCODE =rsn, LOSTSESS = cause, MODULE=mod_name, NODE = nodename,USER = username

ExplanationIMS Connect detected an error while processing arequest or message from ISC and returned a non-zeroreturn or reason code to IMS. The error messageis returned to the local IMS system that issued therequest or message.



When IMS Connect encountered the error, ISCwas attempting to send an ISC message toa remote CICS system by way of the parallelsession identified in the message text.

SESSTERMWhen IMS Connect encountered the error, ISCwas attempting to notify IMS Connect and theremote CICS system that the terminal sessionwas terminated.

SESSINITWhen IMS Connect encountered the error, ISCwas attempting to notify IMS Connect and theremote CICS system of the session initiation ofthe parallel session terminal identified in themessage text.


causeThe cause of a lost session, as reported either bySCI through the CSL SCI Notify Client exit routineor by IMS. The possible values include:ICONABE

The local IMS Connect instance terminatedunexpectedly.






nodenameThe name of the affected parallel session terminal.

rcThe return code issued by IMS Connect. Some ofthe return codes that are more likely to be returnedby IMS Connect are documented in the followingtable. All of the IMS Connect return and reasoncodes are documented in the HWSHRR macro.

rsnThe reason code issued by IMS Connect. Someof the reason codes that are more likely to bereturned by IMS Connect are documented in the




following table. All of the IMS Connect return andreason codes are documented in the HWSHRRmacro.

Possible cause: The cause for this message can bedetermined by reviewing the return and reason codesand the value of LOSTSESS.

The following table lists some of the more likely returnand reason codes that IMS Connect might return toIMS. The explanations of any IMS Connect return andreason codes that are not in the following table can befound in the IMS Connect HWSHRR macro.

Table 21. Common IMS Connect return and reason codes formessage DFS3595E


X'0C00001C' X'0000700C' A message could not be sentto CICS. Usually messageHWSG4040W or HWSG4080Wis also issued.

X'0C00001C' X'00007020' The ISC datastore in IMSConnect has been stopped.Use UPDATE IMSCONTYPE(ISC) START(COMM) tostart it.



X'0C00001C' X'00007060' The ISC datastore inIMS Connect cannot befound. Check the ISCstatement in the IMS Connectconfiguration.


System action:The parallel session is terminated. IMS processingcontinues.

System programmer responseDetermine the cause of the error from the RETCODE,RSNCODE, and LOSTSESS values. The problem couldbe in the IMSplex network. Check for other messagesfrom SCI, the IMS Connect instances, or TCP/IP thatmight help with the diagnosis. Collect the X'6701'error records from the IMS log.


Module:DFSCTER0

Related referenceHWS messages (IMS Connect) (Messages andCodes)Related information“IMS problem determination” on page 11IMS messages and codes problemdetermination is accomplished by usingprocedures established by IBM.

DFS3596E ISC TCPIP DETECTED AN ERROR,active_process, RETCODE = rc,RSNCODE = rsn, LOSTSESS =cause, MODULE =mod_name,NODE = nodename, USER =username

ExplanationThe ISC TCP/IP device dependent module (DDM)detected an error while processing a message orrequest associated with the ISC logical link identifiedin the message text.


The ISC process that was active when the erroroccurred. Possible values include:SENDACK

When ISC TCP/IP encountered the error, ISCwas attempting to send an ISC ACK/NACKmessage to a remote CICS system by way ofthe parallel session identified in the messagetext by the nodename and username values.

SENDMSGWhen ISC TCP/IP encountered the error, ISCwas attempting to send an ISC message toa remote CICS system by way of the parallelsession identified in the message text by thenodename and username values.

SESSTERMWhen ISC TCP/IP encountered the error, ISCwas attempting to notify IMS Connect and theremote CICS system that the terminal sessionwas terminated. The session is identified in themessage text by the nodename and usernamevalues.

SESSINITWhen ISC TCP/IP encountered the error, ISCwas attempting to notify IMS Connect and theremote CICS system of the session initiation ofthe ISC TCP/IP parallel session identified in themessage text by the nodename and usernamevalues.










SCIABEThe SCI instance that is managingcommunications between the local IMS systemand the local IMS Connect instance terminatedunexpectedly.

SCISTOPThe SCI instance that is managingcommunications between the local IMS systemand the local IMS Connect instance was shutdown.

nodenameThe name of the affected parallel session terminal.


rcThe return code issued by the ISC devicedependent module (DDM). The ISC DDM returnand reason codes that are associated with thismessage are documented in the following table.

rsnThe reason code issued by the ISC DDM. The ISCDDM return and reason codes that are associatedwith this message are documented in the followingtable.

usernameThe name of the affected user.

Possible cause: The possible cause is indicated by thereturn and reason codes included in the message textand described in the following table.

The return and reason codes are also listed inthe TCPWORK DSECT in the LU6WA macro in theIMS.SDFSMAC data set.

Table 22. IMS ISC DDM return and reson codes for message DFS3596E


X'00000004' X'00000004' DFSPOOL GET storage error.(DFSCT7B0)

X'00000004' X'00000064',

X'00000068',

X'00000070',

X'0000009C',

X'000000C8',

X'000000D0',

X'000000D4',

X'000000DC',

X'000000E0',

X'000000EC',

X'000000F0',

X'00000104'

IMS detects an error during asession initiation. Refer to thereason codes for DFS3649A formore information. (DFSCT7B0)

X'00000004' Sense codeX'08640001'from IS07 IPICrequest

IMS receives a sense codeof DEALLOCATE_ABEND_SVC foran output message that is beingsent. The output message isdequeued. (DFSCT2A0)

X'00000008' Other sensecode from IS07IPIC request

IMS receives a sensecode other than theDEALLOCATE_ABEND_SVC foran output message that is beingsent. The output message iswashed back on the messagequeues and the session isterminated. (DFSCT2A0)

X'00000008' X'00000000' An error occurs when IMSattempts to send a responsefor an input message that isbeing received. The session isterminated. (DFSCT3B0)

X'0000000C' X'00000004' DFSPOOL GET storage error.(DFSCT7F0)

X'00000014' X'00000004' DFSPOOL GET storage error.(DFSCT7C0)

X'00000216' X'00000000' IMS detects a securityspecification in the IS02 CAPEXresponse message from CICS.(DFSCT7B0)

X'0000xxyy'

Where:

xxResponse fromIS02 CAPEXmessage

yyReason fromIS02 CAPEXmessage

X'00000000' IMS detects non-zeroed valuesof response and reason in theIS02 CAPEX response messagefrom CICS. (DFSCT7B0)


System programmer responseDetermine the cause of the error from the RETCODE,RSNCODE, and LOSTSESS values. The moduleidentified in the message text is where the error


occurred. Check for other messages from SCI, IMSConnect, or TCP/IP to help with the diagnosis. Collectthe X'6701' error records from the IMS log.


Problem determination:1, 5, 6, 14, 36.

Module:DFSTCER0


DFS3597E ISC DETECTED AN INTERNALLOGIC ERROR, active_process,RETCODE = rc, RSNCODE =rsn, LOSTSESS = cause, MODULE=mod_name, NODE = nodename,USER = username

ExplanationAn ISC device dependent module (DDM) detected aninternal logic error.



When ISC encountered the error, ISC wasattempting to send an ISC message to aremote CICS system by way of the parallelsession that is identified in the message textby the nodename and username values.

SESSTERMWhen ISC encountered the error, ISC wasattempting to notify IMS Connect and theremote CICS system that the parallel sessionwas terminated. The parallel session isidentified in the message text by the nodenameand username values.

SESSINITWhen ISC encountered the error, ISC wasattempting to notify IMS Connect and theremote CICS system of the initiation ofthe parallel session that is identified in themessage text by the nodename and usernamevalues.

UNKNOWNDisplayed when the error occurredduring an unidentifiable ISC process. The

troubleshooting and recovery procedure is thesame as for the regular active process types.









nodenameThe name of the affected ISC TCP/IP parallelsession terminal.

rcThe return code issued by the ISC DDM. The ISCDDM return and reason codes that are associatedwith this message are documented in the followingtable.

rsnThe reason code issued by the ISC DDM. The ISCDDM return and reason codes that are associatedwith this message are documented in the followingtable.

usernameThe name of the user associated with the affectedISC TCP/IP parallel session terminal.


IMS ISC device dependent module return and reasoncodes for message DFS3597E

The following return and reason codes are also listedin the TCPWORK DSECT in the LU6WA macro in theIMS.SDFSMAC data set.


Returncode

Reasoncode Meaning

DFSPOOLRC

X'00000004'


DFSPOOLRC

X'00000008'

DFSPOOL release storageerror

CELLPOOL RC

X'0000000C'

CEll pool (CPOOL) geterror

CELLPOOL RC

X'00000010'

CEll pool (CPOOL) freeerror

X'00000014'


X'00000018'


X'0000001C'

Invalid ISC directive(DFSMSDIR) detected

X'00000020'


X'00000024'


X'00000028'


X'0000002C'

Invalid or unexpectedISC Link (MSLINK) statusdetected

X'00000030'


X'00000034'


X'00000038'

Invalid restart messagecontrol block (BUFMSCB)received

X'0000003C'


X'00000040'


X'00000044'

SCIWORK area error

Returncode

Reasoncode Meaning

X'00000048'


X'0000004C'


X'00000050'


X'00000054'

Output edit error

X'00000058'

Input edit error

QMGR RC X'0000005C'


X'00000060'


X'00000064'


X'00000068'


X'0000006C'


X'0000007C'

LXB (Link extension block)was posted by the SCIMSG exit, DFSSXIN0, butthe LXBTCLBP was zero.This problem should notoccur.

X'000000FC'

Undetermined error


System programmer responseDetermine the cause of the error from the RETCODE,RSNCODE, and LOSTSESS values. The moduleidentified in the message text is where the erroroccurred. Check for other messages from SCI, IMSConnect, or TCP/IP to help with the diagnosis. Collectthe X'6701' error records from the IMS log.

DFS3597E is issued for internal logic errors. If theproblem persists, call IBM Software Support.

Problem determination:1, 5, 6, 14, 36.

Module:


DFSCTER0Related information“IMS problem determination” on page 11IMS messages and codes problemdetermination is accomplished by usingprocedures established by IBM.

DFS3600I UNABLE TO INITIALIZEEXTERNAL SUBSYSTEM(S)- member, RC=mm,JOBNAME=JJJJJJJJ

or

SUBSYSTEM DEFINITION SPECIFICATION ERRORFOR SSM = member, JOBNAME=JJJJJJJJ

or

STMNT (nnn), 'xxxxxxxxxxxxxxxxxxx' (yyyyyyyyyy)

or

STMNT (nnn), (DB2AF DEF INVALID FOR DEP REG)

or

STMNT (nnn), KEYWORD 'xxxxxxxxx' (yyyyyyyyyy)

ExplanationIMS found an error while processing the ExternalSubsystem PROCLIB Member (SSM). The membername consists of the 4-byte IMSID followed by the 4-byte SSM parameter. The SSM parameter is specifiedeither as an execute parameter in the member,DFSPBxxx or on the /START SUBSYS SSM xxxxcommand. The JOBNAME value where applicablespecifies the job name of the region where the errorwas detected. At least one of three versions of theDFS3600I messages is displayed depending on thetype of error. The versions are the following:

• UNABLE TO INITIALIZE

This message indicates that IMS found an errorwhich prevented the PROCLIB member from beingprocessed. Any external subsystem defined in themember is not connected to IMS. The characterstring, member, indicates the name of the PROCLIBmember which was being processed. The value mmis one of the following return codes:

Code (hex)Meaning

04A failure occurred while attempting to read thePROCLIB member. Ensure the member namespecified is correct and resides in PROCLIB.

08Storage could not be obtained for a buffer tocontain the PROCLIB member statements.

0CStorage could not be obtained for an externalsubsystem definition element.

18The PROCLIB member did not contain any validsubsystem definitions.

Note: If RC=18 is received from a dependentregion, the SSM= parameter might point to aPROCLIB member which contained no entries.This problem prohibits the dependent regionfrom any subsystem connections. In thiscase, this message is for information only.The dependent region initialization continuesnormally.

• SUBSYSTEM DEFINITION SPECIFICATION ERROR

If one or more errors were found while processing anexternal subsystem definition, then this message isissued. The variable member, indicates the name ofthe PROCLIB member which was being processed.For each definition error, a message is issued toindicate which statement was in error and the textin error. One STMNT error message is issued foreach error in the PROCLIB member. Multiple errorsin a single statement produces multiple messages.The value nnn is the statement number within themember. The character string xxxxx is the text inerror. If the character string, KEYWORD, precedesthe error text, then the error text represents akeyword parameter. The character string yyyyyyyy isone of the following error reason codes:OMITTED

A required parameter was omitted from theexternal subsystem definition. The subsystemdefinition is found to be invalid, therefore, asubsystem connection is not established.

IGNOREDA parameter is specified in the externalsubsystem definition which is not applicableto the type of subsystem being defined. Thisparameter is ignored and processing continues.If the rest of the subsystem definition is valid,a subsystem connection is established at theappropriate time.


INVALIDThe error text represents invalid data in thesubsystem definition statement. If the characterstring, KEYWORD, precedes the error text,then the value for the parameter was invalid.Otherwise, the error text represents data thatcould not be interpreted as part of a subsystemdefinition. The subsystem definition was found tobe invalid, therefore, a subsystem connection isnot established.

DUPLICATEA specific value for a parameter was specifiedfor more than one subsystem definition. Thesubsystem definition is considered invalid andis ignored. All SSN parameter values must beunique within a member.

• DB2AF DEF INVALID FOR DEP REG

An SSM parameter was provided to the dependentregion job; the parameter identified the PROCLIBmember that included a definition for a DB2subsystem to be accessed with the DB2 AttachFacility. This definition is unavailable in an MPP orBMP region and is ignored. Processing continues.Definitions for the DB2 Attach Facility can only beprovided to the control region in the SSM parameter.

System actionIf the UNABLE TO INITIALIZE message is displayed,IMS external subsystem initialization processing failed.

None of the external subsystems defined in themember are connected to IMS.

If a statement is processed and an error occurs thatcauses the subsystem definition to become invalid,then that external subsystem are not connected toIMS.

Programmer responseCorrect the errors in the SSM PROCLIB member.

For UNABLE TO INITIALIZE errors, use the /START SUBSYS SSM command to start the externalsubsystem initialization process, which starts all validsubsystems defined in the member.

For STMNT errors, use the /START SUBSYS commandto start one or more external subsystem connections.

Problem determination:1, 3, 34 and save the SSM PROCLIB member





DFS3601 EXTERNAL SUBSYSTEM(S) NOTDEFINED. COMMAND REJECTED.

ExplanationThe external subsystem was not defined, and thecommand was rejected. One of the following errorsoccurred:

1. The external subsystem name specified on the IMScommand has not been defined to IMS.

2. The SUBSYS keyword was used on a /START, /STOP, /DISPLAY, or /CHANGE command, but IMSwas not made aware of the presence of externalsubsystems using the SSM parameter.

3. SSM was specified, but the SSM PROCLIB membercontained no valid subsystem definitions.


Operator responseEnsure that the subsystem name specified is correct,and reenter the command. If the problem persists,notify the system programmer about the receipt of thismessage.

Programmer responseCorresponding to the error conditions in theExplanation, take one of the following actions:

1. The subsystem name was defined incorrectly ormisspelled in the IMS SSM PROCLIB member.Correct the subsystem name, and update the SSMPROCLIB member.

2. Specify the IMS parameter SSM with a validmember name.

3. In this case, an IMS abend 3041 occurredpreviously. This problem is an indication thatthe subsystem PROCLIB member specified usingthe SSM execute parameter contains no invalidexternal subsystem definitions. When there areno subsystems to support, the task (TCB)that supports the subsystem structure is thenterminated with abend 3041. Correct the PROCLIBmember definitions. If IMS is running when themember is corrected, enter the /START SUBSYS

command to cause IMS to read the new definitionsand establish subsystem connections.



DFS3602I xxxx SUBSYSTEM RESOLVE-IN-DOUBT FAILURE, RC=yyyy

ExplanationThe indicated external subsystem (xxxx), resolve-in-doubt exit, indicated that the resolution of recoverywas unsuccessful. There are outstanding recoveryunits. IMS and the external subsystem cannot resolve(that is, COMMIT|ABORT), previously active recoveryunits (that is, work requests).

System actionIMS terminates the external subsystem connection.IMS continues to function minus that externalsubsystem connection.

Operator responseEnsure that the database administrator is aware ofthis message. Upon the request of the databaseadministrator, you can issue either the /CHANGEcommand or cold start IMS. Remember that the coldstart method erases from IMS memory the fact thatthese recovery units are outstanding.

System programmer responseYou can correct the problem with the IMS /CHANGEcommand and restart the failing subsystem connectionwith the IMS /START command, or cold start IMS.

DFS3603I xxxxxxxx RESOURCE FAILURE FORSUBSYSTEM zzzz REASON CODE -yyzzaaaa



or

xxxxxxxx LOAD FAILED FOR SUBSYSTEM zzzzREASON CODE - yyzz

ExplanationDuring the initial processing of the external subsystemstructure, the allocation or processing of a requiredresource xxxxxxxx failed. zzzz specifies the subsystemname of the module to which it is related. IMSattempts to load the subsystem module when the SSMparameter is specified.

One of the following code numbers, represented bythe yy value, indicates the reason for the failure.


01The resource named in the message was not found- the zz value is the IMODULE LOAD return code.

02Insufficient storage available - the zz value equalsthe IMODULE GETMAIN return code.


04Insufficient storage available - the zz value equalsthe IMODULE GETMAIN return code.

05Open failure for DFSESL DD statement - the zzvalue equals the OPEN return code.


07The resource named in the message was not found(DFSESI40) - the zz value equals the OS LOADmacro return code.

08The resource named in the message was not found- the zz value equals the BLDL return code.

09The resource named in the message was notloaded - the zz value equals the return codeassociated with the MVS system code aaaa.

0AThe data set type cannot be determined - the zzvalue is the return code from the ISITMGD macrocall. The aaaa value is the ISITMGD reason code.

See the IMODULE return code information.

System actionSubsystem connections between IMS and thespecified subsystem are not established, andinitialization processing continues.


System programmer responseEnsure that the subsystem load library is accessibleto IMS. IMS provides a DD statement (DFSESL)to alleviate this problem. The external subsystemmodules can be in any z/OS authorized libraryaccessible by IMS (that is, JOBLIB, STEPLIB orDFSESL).

Increase the region size to accommodate theexternal subsystem modules, and document thestorage requirements in the external subsystemdocumentation.

Related referenceIMODULE return codes (Messages and Codes)z/OS: ISITMGD completion codes

DFS3604I /STA COMMAND FAILED WITHRETURN CODE xxxx

ExplanationAn attempt to create the external subsystem mothertask by the /START command processor failed withone of the following return codes:Code

Meaning0050

The subsystem member name was alreadyspecified by a previous /START SUBSYS SSMxxxx command, or the SSM= EXEC parameter wasspecified on the IMS JCL.

0051The SSM keyword parameter length was not 1 - 4characters.

0052No parameter was specified following the SSMkeyword.

0053A parameter was specified for the SUBSYSkeyword. If the SSM keyword is specified, theSUBSYS keyword cannot have any parameters.



http://www-01.ibm.com/support/knowledgecenter/SSLTBW_2.4.0/com.ibm.zos.v2r4.idad500/isrc.htm?lang=en

0054Too many parameters were specified following theSSM keyword.

0401An invalid return code was received from thePROCLIB processor.

0403An IMODULE GETSTOR request failed to obtain asubsystem definition element. No subsystems canbe connected to IMS.

0404No valid SSM entries were specified.

0501No ESET prefix

0502Attach list count is zero

0503No ESET exists for subsystem

0504Unable to obtain SIDX block

0505Unable to obtain quick save area

0506Global ESET already attached

05FFIMS in SHUTDOWN/ESS task in process ofabending—request rejected


0101No list passed to build routine

0103Unable to obtain quick save area

0104Unable to obtain the Global External SubsystemEntry




System programmer responseTake one of the following actions based on the code:

CodeMeaning

0050External subsystem connection processing hasalready been done. To start a specific subsystem,use the /START SUBSYS xxxx command.

0051Reenter the /START SUBSYS SSM xxxxcommand with a parameter xxxx of 1 to 4characters.

0052Reenter the /START SUBSYS SSM xxxxcommand with a parameter xxxx of 1 to 4characters.

0053Reenter the /START SUBSYS SSM xxxxcommand without any additional parameters.

0054Reenter the /START SUBSYS SSM xxxxcommand without any additional parameters.

0401The subsystem PROCLIB member name is invalidor an error occurred while trying to read themember. Verify that the PROCLIB member name iscorrect and resides on IMS.PROCLIB, then reenterthe command.

0403IMS was unable to get private storage for a workarea. The /START SUBSYS command can bereentered. If the resource shortage is temporary,storage might be available at a later time. If astorage shortage still exists, more working storagemight be allocated to IMS by increasing the region(RGN) parameter on the IMS startup procedure.

0404The IMS.PROCLIB member specified by the SSMparameter does not contain any valid entries.Message DFS3600I was issued for each specificerror.

0501IMS logic error: follow the procedures for softwareproblems.



0504IMS was unable to get working storage. Thiscondition can temporary; reenter the command. Ifthe condition persists, more working storage mightbe allocated to IMS by increasing the region (RGN)parameter on the IMS procedure.


0505Take the same action indicated in return code0504.

0506IMS logic error; follow the procedures for softwareproblems.

05FFNo action required.








DFS3605I ESS/ESI MODIFY COMMANDREJECTED, code xx (y)

ExplanationDuring an attempt to modify the external subsystemwith the MVS MODIFY command, an error wasdetected. The reason code xx describes the error.The value y represents up to 12 bytes of the MODIFYcommand input data. The following reason codes andtheir meanings can appear:Code (hex)

Meaning04

The subsystem name specified in the MODIFYcommand does not have an active subtask. Notask control block (TCB) exists for the externalsubsystem daughter task.

08No external subsystems have been attached toIMS.

0CThe external subsystem name in the MODIFYcommand is not defined to IMS.

10The IMS ID is invalid.

14The external subsystem name in the MODIFYcommand is too long. The name must be from 1to 8 characters.

18The external subsystem in the MODIFY commandis not waiting for a notify message.

1CThe IMSID/RSENAME in the internal MODIFYcommand does not match the name in the SCD/FRB.

20The external subsystem name was not specified inthe MODIFY command. The name must be from 1to 8 characters.

System actionIMS cannot perform the requested action. Thecommand is rejected.

Operator responseNotify the system programmer that this message hasbeen received.

Programmer responseTake one of the following actions:Code (hex)

Meaning04

Check the spelling and format of the MODIFYcommand.

08Either SSM was not specified in the EXECparameters or there was a failure in theinitialization of the external subsystem.

0CIf the command was entered by the operator,check the spelling and format of the MODIFYcommand. Otherwise, the MODIFY command wasan internal command sent from the externalsubsystem to notify IMS that the externalsubsystem was ready to continue the identifyprocess. Make sure that the SSM PROCLIBmember has not been changed.




18This return code can result if IMS has been upand down without a connection to the externalsubsystem.

1CIMS logic error; follow the procedures for softwareproblems.




DFS3606I wwww EXTERNAL SUBSYSTEMINITIALIZATION FAILED, FC =xxxx, RC = yy, JOBNAME = zzzzzzzz

ExplanationInitialization exit processing was unsuccessful for theexternal subsystem (wwww). The external subsystemreturned a nonzero return code. The function code,xxxx, indicates the module that detected the error.This module can be an IMS or external subsystem exitmodule. For the function code value and the modulename that detected the error, see the IMS returncodes and function codes information. The return codeyy, set by the detecting module, indicates the functionthat failed in the detecting module.

To distinguish one region from another, JOBNAME= zzzzzzzz is also provided. This information isnecessary because all the supported regions must doinitialization processing.

For the function code values defined in IMS DSECTDFSESFC, see the IMS return code and function codeinformation.

System actionIMS initialization continues. Subsystem connectionsare not established. In the IMS control region,when the initialization exit processing fails in thismanner, the TCB representing the external subsystemconnection is terminated without an abend.

In the dependent region case, the following list ofreturn codes indicates the IMS action:

yy = 08Initialization unsuccessful - IMS does not initiatea connection to the subsystem for the life of thisIMS-dependent region execution.

yy = 20The external subsystem supplied exit hasencountered an invalid condition while processingthe request. If an application is involved, itterminates with a 3044 abend.

yy = ??Unsupported return code received from theinitialization exit. If an application is involved, itterminates with a 3049 abend.

Operator responseNotify the proper installation personnel about thereceipt of this message, then follow the installationaction.

Programmer responseCorrect the indicated problem, and restart the failingexternal subsystem connection using the IMS /STARTSUBSYS command, or, if an application programwas involved, restart the application using /STARTTRAN, UPDATE TRAN START(Q,SCHD), and /STARTPROGRAM commands.yy = 08

The error was encountered by the externalsubsystem initialization exit; see the externalsubsystem documentation for the action to take.

yy = 20The error was encountered by the externalsubsystem initialization exit; see the externalsubsystem documentation for the action to take.

yy = ??The error was encountered by the externalsubsystem initialization exit; see the externalsubsystem documentation for the action to take.



DFS3607I xxxx SUBSYSTEM yyyy EXITFAILURE, FC = ww, RC = zz,JOBNAME = nnnnnnnn





ExplanationIMS was not able to finish processing successfullyfor external subsystem (xxxx) exit (yyyy). The externalsubsystem attachment package returned a nonzeroreturn code. The function code, ww, is the ID forthe module that indicates the detected error. Forthe function code values and the module name thatdetected the error, see the IMS return code andfunction code information. The return code, zz, ispassed back by the external subsystem exit.

To distinguish one region from another, JOBNAME= nnnnnnnn is also provided. This informationis necessary because the required connectionmanagement routines run in the control as well as inthe dependent regions. Without JOBNAME, it wouldbe impossible to determine which region had theproblem.

System actionThe TCB representing external subsystem connectioncontinues to run without the TCB representing thefailing external subsystem.

For the return code value, the following action occurs:Return code

DescriptionX'08'

TERMINATE IDENTIFY unsuccessful. IMScontinues termination processing as if the functioncompleted normally.

X'08'SUBSYSTEM TERMINATE unsuccessful. IMScontinues termination processing. Futureconnection requests will be honored.

X'0C'IDENTIFY unsuccessful. Because of the failurein the external subsystem, IMS terminates theapplication program with abend 3044, if one isinvolved.

X'20'IMS terminates the application program withabend 3044, if one is involved.

X'??'Unsupported return code. IMS terminates theapplication program with abend 3049, if one isinvolved.

Operator responseNotify the proper installation personnel about thereceipt of this message, then follow the installationaction.

Programmer responseCorrect the indicated problem and restart the failedexternal subsystem by using the IMS /START SUBSYScommand. Or if an application program was involved,restart the application program with a /STARTTRAN, UPDATE TRAN START(Q,SCHD), and /STARTPROGRAM commands.Return code

DescriptionX'08'

TERMINATE IDENTIFY unsuccessful. See theexternal subsystem documentation for action.

X'08'SUBSYSTEM TERMINATE unsuccessful. See theexternal subsystem documentation for action.

X'0C'IDENTIFY unsuccessful. See the externalsubsystem documentation for action.

X'20'See the external subsystem documentation foraction.

X'??'Unsupported return code; save all documentation(that is, console logs, log data set, memorydumps).



DFS3608I xxxx SUBSYSTEM REQUIRED EXITMISSING yyyy, JOBNAME =zzzzzzzz.

ExplanationIMS was not able to finish processing successfullyfor external subsystem (xxxx). A required exit (yyyy)was unavailable. zzzzzzzz is the name of the jobthat encountered the problem. JOBNAME is requiredbecause more than one region can have connectionsto the external subsystem. yyyy can be one of thefollowing values:ID

ID IDENTIFY EXIT





RIDRESOLVE-IN-DOUBT EXIT

SNONSIGNON EXIT

CRTCREATE THREAD EXIT

CMPCOMMIT PREPARE EXIT

CMCCOMMIT CONTINUE EXIT

ABCABORT AND CONTINUE EXIT

TRTDTERMINATE THREAD EXIT

SNOFSIGNOFF EXIT

TERMTERMINATE IDENTIFY EXIT

SNOSUBSYSTEM NOT OPERATIONAL EXIT

STESUBSYSTEM TERMINATION EXIT

NORCNORMAL CALL EXIT

ECHOECHO EXIT

CMDCOMMAND EXIT

System actionA subsystem connection is not established. If aconnection exists, it is terminated in the normaltermination sequence, and the task structure (TCB) iscollapsed for the control region. If an application isinvolved, it terminates with abend 3049.

Operator responseNotify the installation personnel about the receipt ofthis message, then follow the installation action.

Programmer responseEnsure that the subsystem load library is accessibleto IMS. IMS provides a DD statement (DFSESL)to alleviate this problem. The external subsystemmodules must be in a z/OS authorized libraryaccessible by IMS (that is, JOBLIB, STEPLIB orDFSESL). Use the IMS /START SUBSYS command torestart the failing external subsystem connection whenthe problem has been resolved. If this action does notsolve the problem, then check the External subsystem

documentation to determine which exits are provided.The Explanation identifies the required exits.



DFS3609 EXTERNAL SUBSYSTEM TASKABENDING/ABENDED. COMMANDREJECTED.

ExplanationThe IMS external subsystem task terminatedabnormally or was in the process of terminating whenthe /START SUBSYS command was entered.

System actionThe command is rejected. IMS continues processing.


System programmer responseEnter the /START SUBSYS command as soon as thetermination has completed to restart the connection.

DFS3610 SUBSYSTEM STOPPED, COMMANDREJECTED.

ExplanationThe external subsystem is already in a stopped state.The stopped state can be the direct result of:

• A previous /STOP SUBSYS command.• An external subsystem termination.• Either the mother or daughter task abended.• The existence of outstanding recovery elements

from a previous IMS execution.• An IMS abnormal termination.

System actionThe command is rejected. IMS continues to process.

Operator responseNotify the system programmer of this message.



System programmer response:If you want to restart the external subsystemconnection, enter the /START SUBSYS command.If the external subsystem connection is already ina stopped state, reentering the /STOP SUBSYScommand has no affect.

DFS3611I EXTERNAL SUBSYSTEM xxxxCONNECTION TERMINATED RC=y

Explanation:See message DFS3611W for the explanation.

Related informationDFS3611WEXTERNAL SUBSYSTEM xxxx CONNECTIONTERMINATED RC=y

DFS3611E EXTERNAL SUBSYSTEM xxxxCONNECTION TERMINATED RC=y

Explanation:See message DFS3611W for the explanation.

Related informationDFS3611WEXTERNAL SUBSYSTEM xxxx CONNECTIONTERMINATED RC=y

DFS3611W EXTERNAL SUBSYSTEM xxxxCONNECTION TERMINATED RC=y

ExplanationThe daughter task control block (subtask TCB)attached for subsystem xxxx terminated.

Reason code y, a single character value, indicates thecause of the termination, represented by one of thefollowing codes:Reason code

MeaningB

The IMS external subsystem daughter task(TCB attached for each connected subsystem)terminated abnormally. Some of the abendconditions can prohibit the invocation of the exit.

CThe external subsystem notified IMS that it isterminating in a quiesce fashion. IMS ensures thatnew connections are not established and permitsexisting ones to terminate normally.

DThe external subsystem notified IMS that itis terminating abnormally (catastrophic). IMSensures that new connections are not attemptedand terminates existing ones.

EThe connection between the subsystems is beingquiesced by IMS. IMS does not shut down,

but remains available. The termination of theconnection is the result of the IMS /STOPcommand, a bad return code from an exit, or amissing required exit.

FThe connection between the subsystemsterminated because the IMS termination serviceexit was started by an external subsystem exit, andallowed the external subsystem code to requestthat the connection be terminated.

System actionIMS continues normal termination processing.

Operator responseThe external subsystem can be restarted using the /START command.

Programmer responseTake one of the following actions based on the reasoncode:Reason code

MeaningB

The external subsystem TCB terminated. A spin-offmemory dump is created for debugging purposesif the spin-off memory dump facility is active.Determine the cause of the abend, and takecorrective action.

CThe external subsystem quiesced by IMSterminated. No action required.

DThe external subsystem terminated abnormally.Determine the cause of the shutdown of theexternal subsystem (that is, forced shutdowncommand). The external subsystem should provideadequate problem determination material.

EThe connection stopped. No action is required.

FThe connection terminated internally. An externalsubsystem exit instigated the termination ofthe connection and provided adequate problemdetermination information by the external exit.





DFS3612I OPTIONAL xxxxxxxx SUBSYSTEMEXIT NOT PRESENT.

ExplanationIMS attempted to start an optional external subsystemexit and found that the external subsystem did notsupply that exit. This message is sent when thefollowing exit is absent:

xxxxxxxx = command

System actionIf one of the optional exits are not present, IMSperforms this command:

xxxxxxxx = command

IMS runs the command exit when a valid /SSRcommand is entered from a terminal or an automatedoperator interface (AOI) application. If the exit isnot present, IMS indicates this problem by thismessage. The /SSR command and the externalsubsystem command are ignored. IMS continuesnormal operation.


Programmer responseThis problem might be an external symptom of anIMS or external subsystem logic error. First check theexternal subsystem documentation to ensure that itfurnishes a command exit. If it does, ensure that thesubsystem in question is started. If the problem stillexists, a memory dump is required to aid in isolatingthe problem. Use the OS MODIFY (F) command toterminate the IMS external subsystem mother task(ESSM).



DFS3613I xxx TCB INITIALIZATIONCOMPLETE.

ExplanationThe component identified by xxx has completed itsinitial processing.

In the message text, xxx indicates:ALC

LU 6.2 task control block (TCB): allocate the LUMTCB

ALMLU 6.2 TCB: Asynchronous LUM TCB

CTLControl region TCB (primarily data communication)

CTXControl region auxiliary TCB

DCData communications TCB

DGSDiagnostic Services TCB

DLGDASD log TCB (writing and reading of the log)

DLIDLI serialization TCB

DRCDatabase recovery, DBRC, TCB

DYCDynamic allocation TCB

DYC RECALLDynamic allocation recall subtask

ESSExternal subsystem TCB (appears only if SSM isspecified on the EXEC statement)

FPFast Path TCB (appears only if Fast Path isinstalled)

FP2Fast Path TCB 2 (appears only if Fast Path isinstalled)

LSOLocal storage option TCB

LUMLU 6.2 TCB: logical unit manager master TCB

MODIMS control, MODIFY TCB

RCFRACF sign on and sign-off TCB

ODMODBA Syncpoint task manager TCB

ODSODBA Syncpoint request processing TCB


OIDAn OTMA server task control block TCB

RDSRestart data set TCB (writing/reading of the restartdata set)

RLMLU 6.2 TCB: receive LUM TCB

RRSResource Recovery Service TCB

RSTRestart TCB, an IMS restart and checkpointprocessing

STCStorage compression TCB

STMStorage management TCB (job step TCB)

SQ1Shared queues TCB 1

SQ2Shared queues TCB 2

TCOTime-controlled operations TCB

TMCTransaction Manager TCB

TRAExternal trace TCB

XCFCross-system coupling facility TCB

Multiple instances of the TCBs (RRS, DYx, and RCF,for example) can be created during the life of an IMSsession as the workload requires. The initialization ofeach new TCB produces this message.

System actionAfter sending this message, the identified componentwill process any queued work requests.

System programmer responseIf IMS fails during or immediately after theinitialization process, the absence of this messagehelps in identifying the component in which the failureoccurred.

Module:DFSXDGS0, DFSYDTL0 for OID TCB

DFS3614I DFSTRA (TRACE CONTROL BLOCK)CANNOT BE INITIALIZED

ExplanationDuring the initial processing of the tracing functionto obtain storage for DFSTRA, there was not enoughshareable CSA storage available.

System actionThe IMS tracing function is not activated during thisrun of IMS. No other action is taken by this failure, andthe initial processing continues.


System programmer responseIncrease the size of CSA.

DFS3615I UNABLE TO IMODULE LOADDFSTRA10

ExplanationDuring the initial processing of the tracing function,an IMODULE LOAD was unsuccessful for moduleDFSTRAxx, where xx can be 10, 20 or 30.

System actionThis message is issued during the initialization. TheIMS tracing function is not activated during this run ofIMS, and the initial processing continues.


Programmer responseEnsure that all IMS modules are contained in theauthorized libraries concatenated in the job stream.

DFS3616I - THE cccc PARM IS INVALID - THETRACE IS ON IN CORE

ExplanationIMS encountered an invalid trace table optionstatement for the cccc trace table. Valid trace optionsare listed in the IMS system definition information.

An example of a valid DFSVSMxx trace line is OPTIONSDISP=OUT

System actionThe invalid parameter is ignored and IMS continuesinitialization.


Operator responseIf you want the trace to go to the OLDS, issuethe /TRACE SET ON TABLE cccc OPTION LOGcommand. Inspect the DFSVSMxx member and correctany trace specifications that are incorrect or notifyyour IMS system programmer.

DFS3618 SPECIFIED COMMANDRECOGNITION CHARACTER (CRC)NOT FOUND

ExplanationThe command recognition character (CRC) specifiedon the /SSR command was either not defined to IMSor incorrectly specified on the command. Therefore,IMS could not associate it with an external subsystem.


Operator responseNotify the installation personnel about the receipt ofthis message to ensure that you have the correct CRCfor the subsystem. Then reenter the command.

Programmer responseEnsure that the CRC defined for the externalsubsystem is correct in the external subsystemPROCLIB member entry.

DFS3619I UNABLE TO LOAD MODULEDFSESI70 DUE TO RC xx

ExplanationDuring the processing of the /CHA SUBSYS command,an IMODULE LOAD for module DFSESI70 was issued.The load failed indicated by return code xx.

System actionThe command is rejected. IMS continues to process.

Operator responseFor an explanation of IMODULE LOAD return code xx,see the IMS system services return code information.This problem might be caused by a concatenation oflibraries in the job stream. Tell the system programmerthat you received this message.

Related referenceIMS system services return codes (Messagesand Codes)

DFS3620I REQUIRED RESOURCEUNAVAILABLE - RC=uu - FC=vvRESOURCE ID=xxxxxxxx - SUBSYSNAME = yyyy - JOBNAME =zzzzzzzz.

ExplanationThe IMS system encountered a resource constraintwhile processing a request to connect to an externalsubsystem.

The following values for the return code (RC-uu),function code (FC-vv), resource ID-xxxxxxxx, subsysname-yyyy and jobname-zzzzzzzz are defined:uu

The return code is passed back to the caller.For information about return codes and functioncodes, see the IMS Return code and function codeinformation.

vvThe function code indicates the module name thatencountered the problem. For information aboutreturn codes and function codes, see the IMSReturn code and function code information.

xx..xxThe resource ID indicates that a resource wasrequired but could not be obtained or wasnonexistent. The possible values are:GESE

Indicates that the external subsystem, towhich IMS was attempting to connect, didnot have an external subsystem entry definedin the subsystem PROCLIB member specifiedin the control region JCL or the procedure(SSM=). IMS allows different SSM valuesto be specified, each containing a differentsubsystem definition for the control anddependent regions (MPP, BMP, IFP). However,a connection is attempted by IMS only forthose PROCLIB members specified in thecontrol region. The PROCLIB member which isspecified by the SSM parameter for the region(indicated by JOBNAME), contains a subsystemdefinition that did not exist in the controlregion.

AWEIndicates that an IMS module was unable toacquire an asynchronous work element (AWE)to initialize processing.

yyyyIndicates the subsystem where the connectionfailed.




zzzzzzzzIndicates the region where the connectionfailed. The PROCLIB member specified usingthe SSM parameter for this region contains asubsystem definition which is not contained inthe control region member.

System actionThe attempt to connect to the external subsystemis stopped, and this message is issued to assist indetermining the problem.


Programmer responseThe installation action is dependent upon the resourceID. Take one of the following actions, dependent uponthe resource ID.GESE

If you want to connect to the external subsystem,then add the subsystem definition to the controlregion subsystem PROCLIB member.

AWEIncrease the size of the shareable storage (CSA) by4 K increments until IMS runs successfully.

Related referenceReturn and function codes associated withthe external subsystem support (Messages andCodes)

DFS3621I RECOVERY OUTSTANDING FORSUBSYSTEM xxxx

ExplanationThe external subsystem xxxx has outstanding recoveryunits, network identifier (NIDs), but is not defined bythe SSM PROCLIB member. Because the entries areundefined, IMS and the external subsystem cannotresolve the COMMIT or ABORT of previous active workrequests.

System actionIMS retains the outstanding recovery units until theprogrammer takes corrective action.


• Define the external subsystem to IMS using the SSMPROCLIB member and start by using the /STARTcommand or the IMS restart command.

• Delete the outstanding recovery units using the /CHANGE command.

• Perform a cold start.

DFS3622I STORAGE COMPRESSIONDISABLED - STIMER FAILED, RC=y

ExplanationThe online storage compression function issued theSTIMER macro. The return code y indicates that clockdamage occurred.

System actionIMS processing continues. The storage compressionfunction is now inoperative.

Operator responseNotify the system programmer about the receipt ofthis message, then refer the problem to hardwarepersonnel.



DFS3623E STRG-COMP IMODULE ERR=aBLK=b, ADDR=c, RTN=d, SP=e

ExplanationThe online storage compression function issuedthis message before terminating abnormally. Storagecompression was unable to FREEMAIN storage. Thevalues of a, b, c, d, and e are:Value

Meaninga

A hexadecimal IMODULE delete return code.b

The 4-character name of the storage pool thatowns the storage.

cThe address of the storage IMS tried to FREEMAIN.

dAn indicator as to which IMODULE delete,DFSBCB60, issued X'00' - routine at label FREE.





eThe subpool number specified on IMODULE indecimal.

System actionIMS terminates abnormally and module DFSBCB60issues IMS abend 3058, subcode 12.


Programmer responseFor problem analysis, see the description in abend3058, for subcode 12.



DFS3624I jobname- psbname- pstid- code -bbcc

ExplanationThis informational message accompanies several IMSpseudoabends. It provides diagnostic informationfor the pseudoabended application. This messagecontains the following information:Value

Descriptionjobname

The name of the job that encountered thepseudoabend.

psbnameThe application program name (PSB).

pstidThe PST ID.

codeThe pseudoabend code.

bbbbA hexadecimal return code, bbbb, which identifiesthe cause of the abend, as well as the module thatdetected the condition.

ccccA hexadecimal return code, cccc, which identifiesthe function of the module that detected thecondition.

For example:

JOBNAME PSBNAME PSTID CODE RC FC

DFS3624I IMF4MPR1 RCDBS4 00006 3045 0004 0293

System actionThis message does not cause IMS to take anyadverse action; it is informational. The accompanyingpseudoabend indicates the action IMS will take.

Programmer responseFor the possible combinations of the return codes andfunction codes this message can return, see the IMSReturn code and function code information. The returncode (RC) is the value set in register 15 at the pointwhere the error was detected. It represents the errorcondition for debugging purposes. The function code(FC) represents the module that detected the problem.The module name and the return code help determinewhy the application program was pseudoabendedwithout looking at a memory dump.


Module:DFSESPR0


DFS3625E STRG-COMP PAGE FREE ERRORRC=z

ExplanationThe online storage compression function issuedthis error message before terminating abnormally.Storage compression attempted to unfix one or moreIPAGEs using IMSAUTH FUNC=PGFREE and received anonzero return code.

System actionIMS terminates abnormally and module DFSBCB60issues abend 3058, subcode 13.






Operator responseNotify the system programmer of the receipt of thismessage.

Programmer responseFor problem analysis for the description of subcode13, see 3058 information.


DFS3626I RESTART HAS BEEN ABORTED

ExplanationIMS terminated the restart process. Error messagesissued before this one indicate the problem.

System actionThe restart is terminated and awaits anothercommand.

Operator response:After correcting the problem, restart the IMS system.



DFS3627I DYC|DYS TCB RETRY INPROGRESS DUE TO SYS|IMS xxxx

ExplanationThe dynamic control services TCB ESTAE has receivedcontrol and is attempting a retry of the process thatencountered an error. DYC is the dynamic allocationservice in the IMS control region. DYS is the dynamicallocation service in the DL/I subordinate addressspace. The reason for the retry is abend code xxxx,which is either a system (SYS) or IMS code.

System actionA retry of the request issued to the dynamic controlservices TCB is attempted. In addition, a softwarelog record containing a copy of the System DiagnosticWork Area (SDWA) is written to the SYS1.LOGREC dataset. The log record contains an eye-catcher field thatidentifies the failure as "IMS DYN ALLOCATE".


Programmer responseIn most cases, receiving this message is no causefor alarm, although a database or data set mightnot have been allocated or deallocated. External useraction might be required to process the request.However, if the problem persists, an investigation ofthe SYS1.LOGREC data set might be necessary toobtain diagnostic information about the failure.

DFS3628E DOUBLE AWE RELEASE DETECTEDIN MODULE DFSBCB30

ExplanationThe IMS control block storage manager, DFSBCB30,detected a double release of an IMS internal controlblock called an AWE. IMS collects internal diagnosticinformation for this problem and issues this messageto document that this condition occurred.

This message is issued only one time per IMScheckpoint interval, regardless of how many doubleAWE frees occurred.

System actionIMS processing continues, however, a double free ofan AWE is a symptom of an internal processing errorwithin IMS, and unpredictable results might occur.

System programmer responseTake a memory dump of the IMS control and DLIregions and contact IBM Software Support.

Module:DFSBCB30

DFS3628I DB2 RRSAF SETUP FAILED -xxxxxxxxxx

ExplanationThe DB2 Attach Facility could not be established in theJava™ region for the reason given by xxxxxxxxxx. Thepossible reasons for the failure are:

• GETMAIN FOR AFB FAILED• ACCESS TO db2id STOPPED• UNABLE TO OPEN DFSDB2AF

System actionThe dependent region terminates abnormally witha 3056 except for the reason, ACCESS TO db2id



STOPPED, where db2id is the subsystem name whichwas provided in a /STOP SUBSYS command.

System programmer responseFor UNABLE TO OPEN DFSDB2AF, ensure that accessto the defined data set is available to the dependentregion. Also ensure that the DB2 library is APF-authorized. For ACCESS TO db2id STOPPED, if thedependent region needs access, stop the region, issuea /STA SUBSYS command and restart the region. Ifaccess is not needed, nothing need be done.

Module:DFSD2AF0


DFS3629I DB2 RRSAF FUNC=xxxx FAILED -RC=yyyy, RS=zzzz

ExplanationThe DB2 Attach Facility function xxxx failed withreturn code yyyy and reason code zzzz. The possiblefunctions are:

IDENTFYSIGNONCREATE THDTERM THD

System actionThe dependent region terminates abnormally with a3056.

Programmer responseContact the system programmer.

Module:DFSD2AF0

Related conceptsDB2 codesRelated informationIMS abend 3056

DFS3630 GENERIC PARAMETER IS NOTALLOWED

ExplanationA generic parameter was entered for a command orkeyword that does not allow generic parameters.


Programmer responseReenter the command with non-generic parameters.

Module:DFSICLN0

DFS3631E MSC=Y IS SPECIFIED BUT NOSYSID IS DEFINED.

ExplanationMSC=Y is specified in the IMS execution parameters,but no MSC system identifiers (SYSIDs) are assigned tothe IMS system. At least one SYSID must be assignedto the IMS system when MSC=Y is specified in the IMSexecution parameters.


User responseAssign at least one SYSID to the IMS system or specifyMSC=N in the IMS execution parameters. When thechanges are complete, cold start IMS.

Assign a SYSID to the IMS system by specifying theSYSID parameter in the MSC section of the DFSDFxxxPROCLIB member.

Alternatively, you can assign a SYSID to the IMSsystem by coding the MSNAME macro as inputduring the IMS stage-1 system definition process. Thestage-1 input must also include an MSPLINK macroand an MSLINK macro.

Module:DFSRMC10

Related referenceMSC section of the DFSDFxxx member (SystemDefinition)MSNAME macro (System Definition)

DFS3632 COMMAND ONLY VALID FOR ISCSESSIONS

ExplanationA command with the keyword combination NODEor NODE and USER was entered, where the NODEparameter was not ISC. This command, with the NODEor NODE and USER keywords included, is valid only forISC nodes.



http://www-01.ibm.com/support/knowledgecenter/SSEPEK_11.0.0/com.ibm.db2z11.doc.codes/src/codes/db2z_codes.htm


http://www.ibm.com/support/knowledgecenter/SSEPH2_15.1.0/com.ibm.ims15.doc.sdg/ims_dfsdfxxx_proclib_msc.htm#ims_dfsdfxxx_proclib_msc


http://www.ibm.com/support/knowledgecenter/SSEPH2_15.1.0/com.ibm.ims15.doc.sdg/ims_msname_macro.htm#ims_msname_macro


Programmer responseReenter the command without the USER keyword orwith a NODE parameter that is ISC.

DFS3633 GENERIC PARAMETERRESOURCES NOT FOUND, NOACTION TAKEN

ExplanationA command with only generic parameters wasentered. None of the generic parameters applied toexisting resources. For example, if the command /IDLE NODE ABC* CD%F were entered, this messageis issued if there were no resources whose namesstarted with ABC or no resources whose first, second,and fourth characters were C, D, and F.

Operator responseCheck whether the generic parameter applies to theintended resource.

Module:DFSICLN0

DFS3634 LOGOND OR USERD NOT VALIDWITH STATIC RESOURCE

ExplanationThe /OPNDST NODE command erroneously includedthe keyword LOGOND or USERD with a static terminalor user, or a dynamic ISC terminal or user. TheLOGOND keyword applies only to dynamic non-ISCterminals and the USERD keyword applies only todynamic non-ISC users.


Operator responseRe-enter the command, omitting the LOGONDkeyword, if the terminal is static or dynamic and ISC.Re-enter the command, omitting the USERD keyword,if the user is static or dynamic and ISC.

DFS3635 COMMAND NOT ALLOWED FORSTATIC USERS

ExplanationA command with the keyword USER that applies onlyto dynamic users was issued for a static user. Thecommand is one of the following:

/BRO USER/END USER/EXC USER/EXIT CONV USER/RSTART USER/TEST USER


Operator responseReenter the command for a dynamic user.

DFS3636 INVALID ASSIGNMENT BETWEENSTATIC AND DYNAMIC USERS

ExplanationOne of the following incorrect forms of the /ASSIGNcommand was attempted:

• /ASSIGN LTERM static {TO} USER dynamic• /ASSIGN LTERM dynamic {TO} USER static• /ASSIGN USER static {TO} USER dynamic• /ASSIGN USER dynamic {TO} USER static


Operator responseIssue one of the following correct forms of the /ASSIGN command:

• /ASSIGN LTERM dynamic {TO} USER dynamic• /ASSIGN LTERM static {TO} USER static• /ASSIGN USER dynamic {TO} USER dynamic• /ASSIGN USER static {TO} USER static

DFS3637 USER IN USE, CANNOT PROCESSCOMMAND

ExplanationThe user referred to in the /ASSIGN command cannotbe reassigned because the user is signed on or is inconversation mode, preset mode, or response mode.



Operator responseWait for the user to sign off or to terminateconversation mode, preset mode, or response mode,and then try the /ASSIGN command again.

DFS3638 IMPROPER REASSIGNMENTFOR LUTYPE6 OR DYNAMICTERMINALS

ExplanationAn attempt was made to improperly assign anLUTYPE6 or dynamic terminal, user, or LTERM. Theassignment is incorrect for one of the followingreasons:

• The /ASSIGN INPUT LTERM and /ASSIGNOUTPUT LTERM forms of the /ASSIGN commandare not allowed for dynamic or LUTYPE6 logicalterminals.

• An LUTYPE6 or dynamic LTERM cannot be assignedto a node because these types of logical terminalsare associated with users.

• An LUTYPE6 LTERM or user cannot be assigned to anon-LUTYPE6 user.

• A non-LUTYPE6 LTERM or user cannot be assignedto an LUTYPE6 user.

• An LTERM cannot be assigned to a dynamic orLUTYPE6 terminal.


Operator responseMake an appropriate reassignment for LUTYPE6 ordynamic nodes, LTERMs, or users.

DFS3639 USER KEYWORD INVALID IF NODEPARAMETER IS GENERIC

ExplanationA command with the keyword combination NODE andUSER was supplied with a generic NODE parameter.


User responseEnter a nongeneric NODE parameter with the USERkeyword.

Module:DFSICLN0

DFS3640W xxxxxxxx HAS ANINVALID DYNAMIC TERMINALDESCRIPTOR TYPE OF y

ExplanationWhile processing ETO descriptors, IMS found adescriptor that cannot be identified as a LOGON, MSC,USER, or DEVICE descriptor type.

System actionThe descriptor is ignored.

System programmer responseLocate the descriptor with the resource name ofxxxxxxxx. Correct the descriptor type of y to L, M, U,or D. If this descriptor must be present, restart IMS.



DFS3641W xxxxxxxx HAS AN INVALIDPARAMETER FOR KEYWORDyyyyyyyy. DEFAULTS FOR THISKEYWORD WERE USED.

ExplanationWhile processing ETO descriptors, IMS found anincorrect parameter for keyword yyyyyyyy.

System actionThe parameters specified for the keyword are ignored,and the default values are used.

System programmer responseLocate the descriptor with the resource name ofxxxxxxxx. Correct the parameter in error. If thedefaults selected for the keyword are incorrect, restartIMS.




DFS3642E THE STAGING DATA SET IS FULL.

ExplanationThe staging data set of the IMS directory is full. Thestaging data set is used to hold resource changesthat are waiting to be written to the IMS directory foractivation in the online IMS system.


User responseThe staging data set must be expanded by runninga catalog utility. Resubmit the IMPORT command orreactivate the DDL definitions.

Module:DFSMOLS0


DFS3643I USER xxxxxxxx HAS EXCEEDEDDLQT VALUE. LAST ACCESSED ONyyyyddd.

ExplanationUser xxxxxxxx has queued messages or outstandingstatus and has not been accessed since yyddd, whichexceeds the time period specified on the DLQT JCLparameter. User xxxxxxxx was last accessed whenit was created, signed on, or signed off. Otherpossibilities are when messages were dequeued, orqueues were assigned away. User xxxxxxxx has beenmarked as having a status of DEADQ.

System programmer responseVerify that the time period specified on the DLQT JCLparameter is not unreasonably short.

For ISC users, determine why the ISC user was notallocated to a node for the DLQT time period.

For dynamic users, if the user name is defined toenhanced security such as RACF, verify that userxxxxxxxx can access the queue by signing on. Ifthe dynamic user name is not defined to enhancedsecurity such as RACF, and thus cannot be signed

on, determine why messages were queued or statusapplied to that user.

To aid the investigation of why messages were queuedand to remove the status of DEADQ, use the /ASSIGNcommand to reassign queues and retrieve the data forevaluation.

To purge the data and to remove the DEADQ status,use the /DEQUEUE command. If status no longerapplies to the user, remove the status using acommand or by signing the user on and taking thenecessary actions to reset the undesired status.

Delete dynamic users who were created inadvertently.To cause the user structure to be deleted, all themessages must be dequeued or the queues assignedaway, and the status must be removed. Then, theuser structure will be deleted at the next simplecheckpoint.



DFS3644 NO RESOURCES FOR NODEnnnnnnnn


• IMS could not acquire the control blocks required forthe creation of a dynamic terminal structure.

• The created terminal structure could not be added tothe IMS hash table for such structures.

Both reasons represent serious system failures.

System actionThe command or logon attempt is ignored andprocessing continues.


System programmer responseUse the information in the DFS3672I message tofurther identify the nature of the problem. Consult theIMS diagnostic information for the meanings of theindicated code and qualifier. Contact the IMS supportrepresentative for further action.



User responseTry the action that generated this message again.



DFS3645I LOGON REJECTED - NODEnnnnnnnn

ExplanationA terminal attempted to establish a session with IMSbut the attempt was unsuccessful.



System programmer responseThis message appears when:

• The terminal is defined as the primary or secondarymaster terminal for the alternate system in an XRFenvironment.

• ETO=NO was in effect, thus precluding sessionestablishment attempts from terminals not definedto IMS. If ETO=YES was specified at startup,verify that ETOFEAT=YES was specified in theIMSCTRL macro and that message DFS3648I wasnot issued by any installation-supplied initializationexit, DFSINTX0.

• Required user data was not provided for parallelsession ISC and ETO FIN/SLU P terminals. The userdata was not provided, or an installation-suppliedlogon exit, DFSLGNX0, cleared the user data. Makesure that the user data is supplied or not cleared.See the "Format for CINIT user data parameters"topic in IMS Version 15 System Programming APIs forCINIT user data parameters.

• An installation-supplied logon exit, DFSLGNX0,rejected the logon attempt without issuing its ownmessage to indicate why the session was rejected.

• No logon descriptor was found describing thecharacteristics of the terminal attempting sessionestablishment.

• An ISC session was initiated using the genericresource name but the IMS initialization user exitspecified the option to disable VGR for ISC.


Related referenceFormat for CINIT user data parameters (SystemProgramming APIs)Related information“IMS problem determination” on page 11IMS messages and codes problemdetermination is accomplished by usingprocedures established by IBM.

DFS3646I UNRECOGNIZED ORINCONSISTENT DEVICEATTRIBUTES. DESC = nnnnnnnn -NODE = xxxxxxxx

or

UNRECOGNIZED OR INCONSISTENT DEVICEATTRIBUTES. DESC = LLLLLLLL, NODE =NNNNNNNN, SCR/USE = AABBCCDDXXYY/Z1Z2

ExplanationFor the first message form, either the IMS logondescriptor name for the given node was incompatiblewith the characteristics of that node as specified inthe CINIT, or the Device Characteristics Table was notfound.

For the second message form, the SCR field refers tothe screen size information presented to IMS by thelogging-on terminal.AABB

The default screen size (AA = lines, BB = columns)in hexadecimal.

CCDDThe alternate screen size (CC = lines, DD =columns) in hexadecimal.

XXThe screen size control byte in hexadecimal.

YYThe video/printer identifier (applicable to non-SNA3270 devices only).

The USE field identifies the actual screen size used byIMS in searching the Device Characteristics Table for amatching entry.Z1

Number of lines of screen size in hexadecimal.


http://www.ibm.com/support/knowledgecenter/SSEPH2_15.1.0/com.ibm.ims15.doc.spr/ims_cinit.htm#ims_cinit

http://www.ibm.com/support/knowledgecenter/SSEPH2_15.1.0/com.ibm.ims15.doc.spr/ims_cinit.htm#ims_cinit

Z2Number of columns of screen size in hexadecimal.

IMS also searches the DCT for a match on featureinformation. The feature information from the ETOlogon descriptor is compared with the featureinformation in the DCT entry.



System programmer responseFor the first message form, determine whetherdescriptor nnnnnnnn correctly describes nodexxxxxxxx. Correct the named descriptor, or createa new one specifically for the named node. Verifyexistence of Device Characteristics Table.

For the second message form, the MFS Service utilitycan be used to list the entries in the DCT to see whatentries are currently defined. The feature informationin the ETO logon descriptor (the descriptor LLLLLLLL isidentified in the message) and the 'USE' screen sizevalues (identified in the message) must both matcha single entry in the DCT. Most likely, the MFS DCTutility needs to be used to add an entry to the DCT forthe screen size and feature combination that was notfound.


Related conceptsLU2 and non-SNA 3270 screen size and modelinformation (Communications and Connections)MFS device descriptors (System Definition)Related tasksAdministering the Extended Terminal Option(Communications and Connections)Related referenceMFS Device Characteristics Table utility(DFSUTB00) (System Utilities)Related information“IMS problem determination” on page 11IMS messages and codes problemdetermination is accomplished by usingprocedures established by IBM.

DFS3647W MISPLACED OR DUPLICATEDESCRIPTOR xxxxxxxx. CONTENTSARE IGNORED.

ExplanationIMS initialization has already processed descriptorrecords for descriptor name xxxxxxxx. However, adescriptor with the same resource name was foundand ignored.

System actionThe descriptor records in error are ignored andprocessing continues.

System programmer responseCorrect the error by discarding or repositioningdescriptors in IMS.PROCLIB as required.



DFS3648 ETO SUPPORT NOT AVAILABLE -DISABLED VIA DFSINTX0

ExplanationThe initialization exit routine DFSINTX0 returned areturn code of 4 to IMS. A return code of 4 indicatesthat dynamic terminal support is not wanted, even ifit was requested using the ETO= parameter in the JCLor the DFSPByyy member. Since output security is onlyavailable for ETO terminals, none of the terminals inthe system has output security.

System actionIMS does not allow the creation of any ETO terminalsor users until the next IMS restart.

Operator response• If ETO terminal support is not wanted, no action is

required.• If ETO terminal support is required, contact the IMS

system programmer for assistance.

DFS3649A /SIGN COMMAND REQUIRED.

(3270/SLU2 type devices) IMS Sign on panel

or


http://www.ibm.com/support/knowledgecenter/SSEPH2_15.1.0/com.ibm.ims15.doc.ccg/ims_eto_pln_devcs_lu2nonsna.htm#ims_eto_pln_devcs_lu2nonsna

http://www.ibm.com/support/knowledgecenter/SSEPH2_15.1.0/com.ibm.ims15.doc.ccg/ims_eto_pln_devcs_lu2nonsna.htm#ims_eto_pln_devcs_lu2nonsna

http://www.ibm.com/support/knowledgecenter/SSEPH2_15.1.0/com.ibm.ims15.doc.sdg/ims_ie0i2tla1041561.htm#ie0i2tla1041561

http://www.ibm.com/support/knowledgecenter/SSEPH2_15.1.0/com.ibm.ims15.doc.ccg/ims_eto_admin.htm#ims_eto_admin

http://www.ibm.com/support/knowledgecenter/SSEPH2_15.1.0/com.ibm.ims15.doc.ccg/ims_eto_admin.htm#ims_eto_admin

http://www.ibm.com/support/knowledgecenter/SSEPH2_15.1.0/com.ibm.ims15.doc.sur/ims_dfsutb00.htm#ims_dfsutb00

http://www.ibm.com/support/knowledgecenter/SSEPH2_15.1.0/com.ibm.ims15.doc.sur/ims_dfsutb00.htm#ims_dfsutb00

(Non-3270/SLU2 devices) /SIGN COMMANDREQUIRED FOR IMS imsid. NODE node name. (NO)OUTPUT SECURITY AVAILABLE (,REJECTED reason.)

ExplanationThe user of a terminal requiring sign on, whichincludes all ETO terminals except ISC, SLU P, andFINANCE terminals, must enter valid sign-on databefore IMS will accept other input data, such astransactions, commands, and message switches. Theonly commands permitted at this time are /SIGNand /RCLSDST.

For 3270 terminals, the first form of the messageappears and the sign-on data can be entered intothe panel displayed. For non-3270 terminals, thesecond form of the message appears; use the /SIGNcommand when permitted.

If this message is sent again due to the rejection ofa sign-on attempt, the reason for the rejection will beshown after the word REJECTED.

The last form of this message, the key message, isdisplayed when the pre-edit message was unable tobe built. For all the conditions that cause DFS3649 tobe sent, see “Conditions for signon for DFS3649” onpage 1040.

See the following list for the reason codes reason andtheir meanings:Code (dec)

Meaning04

User profile is not defined to RACF.08

Password is not authorized, or was not specified.12

Password has expired.16

New password is invalid.20

User is not defined to the group.24

RACINIT was failed by the installation exit routine.28

User access has been revoked.32

RACF is not active.36

The user's access to the specified group has beenrevoked.

40OIDCARD parameter is required but not supplied.

44OIDCARD parameter is invalid for specified user.

48User is not authorized to use the terminal.

52User is not authorized to use the application.

56Reserved.

60Reserved.

64Reserved.

68Reserved.

72Reserved.

76SIGNON internal error

80Terminal is in conversation.

84Reserved.

88Terminal is in Preset Mode.

92Terminal is in Response Mode.

96The terminal is not authorized to this conversation.

For a static terminal or a dynamic terminal with theSPQBname the same as the node name, you arenot allowed to sign on unless all conversations areheld, or you are authorized to use the transactionfor the active conversation.

100Rejected by DFSCSGNO exit routine.

104Storage unavailable to process request.

108Reserved.

112Rejected by DFSSGNX0 exit routine.

116The structure of the /SIGN command is in error.

120Resources unavailable for command.

124The LTERM name returned by DFSSGNXO exitexists as LU 6.2 descriptor name

128Syntax error detected by IMS.


132Storage unavailable to IMS while processingsignon or signoff parameters, or one of theparameters is invalid.

136Return code 104 from ARM call. Storage wasunavailable to complete this call.

140Return code 108 from ARM call. A system errorcaused this call to fail.

144User ID has more than eight characters.

148Descriptor specified by the USERD parametercould not be found, or no user descriptor could befound (DFSUSER could not be found).

152User descriptor specified has more than eightcharacters.

156User structure is already allocated to a terminalstructure.

160Associated printer user structure exists and istemporary.

164Descriptor name returned in the associated printeroutput buffer by DFSSGNX0 does not exist in thesystem.

168DFSUSER user descriptor does not exist in thesystem, and no other descriptor was specified tobuild the associated printer structure.

172Associated printer structures could not beobtained using DFSBCB.

176Specified user ID is currently in use as a dynamicuser. It is unavailable at this time as a static userID. Or, the specified user ID is not valid for thisterminal type because it was statically definedwith the system definition SUBPOOL macro for usewith static ISC parallel session nodes.

180USERD parameter cannot be specified by a staticterminal.

184Queues returned in the user output queue bufferthat modify the existing user structure do notbelong to the existing user.

188Queues returned in the user output queue bufferthat modify the existing user structure are notdefined in the system.

192User ID returned in the user output queue bufferfrom DFSSGNX0 contains invalid characters.

196Associated print user name returned in theassociated print output buffer from DFSSGNX0contains invalid characters.

200Queues returned in the user output queue bufferfrom DFSSGNX0 contain special prefixes reservedto IMS or contain invalid characters. If no bufferdata is returned by DFSSGNX0, the parameter inerror might have been entered as signon data.

204Queues returned in the user output queue bufferfrom DFSSGNX0 are not unique in this IMS system.If no buffer data is returned by DFSSGNX0, thenDFSUSER is used as the descriptor but an LTERMwith the same name as the user ID exists.

208Queues returned in the user output queue bufferfrom DFSSGNX0 contain names that are currentlydefined as transaction names in this IMS system.

212User structure blocks could not be obtained usingDFSBCB.

216User is allocated, but it is not ISC/SLU P/FINANCE.

220User is allocated, and though it is ISC/SLU P/FINANCE, the user address does not match thenew user address.

224User exists and is trying to sign on, but sign-on hasthe status of having the stopped bit turned on bythe /STOP USER command.

228Sign-on exit routine DFSSGNX0 returned an invalidICOMPT value that was not between 1 and 4.

232Signon exit routine DFSSGNX0 returned an invalidCOMPT value that was not between 1 and 4.

236User existed as a real user and not a temporaryuser, but the user does not have any queues.

240Static or dynamic terminal with this user ID existson the system.


244LU6, SLU P, or FINANCE ETO terminal entered a /SIGN command, but there are no user structuresavailable under this terminal.

248Associated printer buffer from DFSSGNX0 has aLUNAME that does not follow the correct namingconventions.

252Associated Printer buffer from DFSSGNX0 has alogon descriptor which does not follow the correctnaming conventions.

256Associated Printer buffer from DFSSGNX0 hasa mode table name which does not follow thecorrect naming conventions.

260Static user was not found for the user allocation ofa static ISC parallel session. A dynamic user wasused for the user allocation of a static ISC parallelsession, or a static user was used for the sign-on toan ETO terminal session.

264Session initiation occurred for an ETO terminalthat is an output-only device, but no sign-ondata (user ID and optionally user password anduser descriptor) was included. The session isterminated.

268MSGDEL specifications for the USER and static ISCparallel session terminal did not match. They mustbe the same.

272The user structure name has been overriddenby DFSSGNXO exit, either because a name wasprovided in USEQUSTN or as a result of suffixing.This name exists as a user descriptor and,therefore, cannot be used as a user structure nameby the user signing on.

276The user exists and is currently being used byas part of an /ASSIGN, /STOP, or /OPNDSTcommand.

280An LTERM name with a suffix added containedmore than eight characters.

284Temporary user structure is currently in use byanother ITASK. Wait a moment and try again.

288The user sign-on exit, DFSSGNX0, has returnedan invalid value in either the SGNOSRM1 orSGNOSRM2 field.

292A static terminal attempted to sign on and registerthe user ID to RM. However, the sign-on is rejecteddue to an error in RM registration.

296The user exists, but the user has Fast Path inputin progress and the user was defined with noFast Path recovery (RCVYFP=NO). The Fast Pathprogram must complete before the user is allowedto sign on.

300Password verification is required.

304Password verification failed.

308A failure occurred in obtaining CTBWORK.

312The user is stopped from signing on.

316A user in Fast Path response mode attempted tosign on to an IMS system that is not Fast Pathcapable or is not using an EMHQ structure.

320A mismatch occurred between the local IMS andRM: user type.

324A mismatch occurred between the local IMS andRM: number of assigned CNTs.

328The user resource in RM does not have a fixedsegment.

332The user is currently active.

336The limit has been reached for user updateattempts.

340The user is owned by another IMS.

344The user update failed.

348The user ID is owned by an active IMS.

352The assigned CNT was not found.

356The node query produced no RM output.

360The node query failed.

364User signon failed. The user attempted to log on asa static terminal, but the node is already defined toRM as a dynamic terminal; or the user attempted


to log on as a dynamic terminal, but the node isalready defined as static.

368A mismatch occurred between the local IMS andRM: session manager session.

372A mismatch occurred between the local IMS andRM: user or subpool support.

376A mismatch occurred between the local IMS andRM: device type.

380A mismatch occurred between the local IMS andRM: output-only.

384A mismatch occurred between the local IMS andRM: output-only.

388A mismatch occurred between the local IMS andRM: output edit.

392The node update did not produce RM output.

396The node update failed.

400®There is no storage.

404Node cleanup has no RM output.

408Node cleanup failed.

412Node delete has no RM output.

416Node delete failed.

420There is no LTERM for this signon.

428The user currently allocates to a different node.

432An error in the RACF database occurred. For moreinformation, see system abend 483-4C in z/OSMVS System Codes (SA22-7626).

436CQS is unavailable, which causes the registrationof interest to fail.

• For ETO terminal, the user is signed off.• For static non-stsn terminal that requires signon,

the session persists. The user is signed off ifalready signed on.

440The user is allocated to a different node on thelocal IMS system.

444Sign-on was unable to update the node resourcein RM. This condition is temporary; try the sign-onagain.

448An application is using an LTERM associated withthis user. This condition is a temporary. Please trythe sign-on again.

500Either the user profile is not defined to RACF,or the password is not authorized or was notspecified.

Attention: For reason codes 4-52, see z/OSSecurity Server RACF System Programmer'sGuide (SA22-7681) for further details.

Conditions for signon for DFS3649Message DFS3649 is sent for various reasons. Thefollowing table contains the conditions under whichthese messages are sent to different devices.

In the table, a "Y" in the cell indicates that thecondition is valid for the device listed at the top ofthat column. An "N" indicates that this condition willnot cause message DFS3649 to be sent to the devicelisted at the top of that column. Blank cells in thetables indicate that the condition is not applicable tothe device listed at the top of that column.

Because 3270 printers are output-only devices, theynever receive message DFS3649.

Numbers 058, 064, 165, 2467, 2469, 3650, 3662,and 3664 in the table indicate that messages DFS058,DFS064, DFS165, DFS2467, DFS2469, DFS3650,DFS3662, and DFS3664 are received instead ofDFS3649.

A sign-on failure for an output-only device causesmessage DFS2085 to be sent to the MTO with thereason code from the DFS3649 message.

Table 23. Conditions that message DFS3649 is sent to certaindevices

Condition 3270

3270P

FIN

SLU1

SLU2

SLU4

SLU P

LU6

NTO

Sessioninitiation(simple)

Y Y Y Y Y

Sessioninitiation-NOTERMspecified, staticterminal

N N N N N


Table 23. Conditions that message DFS3649 is sent to certaindevices (continued)

Condition 3270

3270P

FIN

SLU1

SLU2

SLU4

SLU P

LU6

NTO

Sessioninitiation-NOTERMspecified, ETOterminal,without userdata1

Y Y Y Y Y

Sessioninitiation withsign-on data

3650

3650

3650

3650

3650

Sessioninitiation(unattachedmode)

N N

Sessioninitiation(autologgedon)

N N N N N

Sessioninitiation withbad sign-ondata

Y Y Y Y Y Y

/SIGN ONfailure, staticterminal, sign-on not required

Y 2467 Y Y Y 24

672467 Y

/SIGN ONfailure, staticterminal, sign-on required

Y Y Y Y Y Y Y

/SIGN ONfailure,dynamicterminal

Y 2469 Y Y Y 24

692469 Y

Tran orcommandentered beforesign-on whensign-onrequired-staticterminal

Y Y Y Y Y Y Y

Tran orcommandentered beforesign-on whensign-onrequired-dynamicterminal

Y

165

2469064

3662

Y Y Y

165

2469064

3662

165

2469064

3662

Y

/SIGN OFF,static terminal,sign-on notrequired

058

058

058

058

058

058

058

058

/SIGN OFF,static terminal,sign-onrequired

Y Y Y Y Y Y Y

Table 23. Conditions that message DFS3649 is sent to certaindevices (continued)

Condition 3270

3270P

FIN

SLU1

SLU2

SLU4

SLU P

LU6

NTO

/SIGN OFF,dynamicterminal

Y 058 Y Y Y 05

8058 Y

Remember:1

OPTION=NOTERM does not affect the issuance of theDFS3649 message for dynamic terminals because NOTERM isspecified on the USER descriptor. DFS3649 is not suppressedwhen NOTERM is specified on the USER descriptor becauseNOTERM is not reflected in the blocks for the node until aftersign-on.

System actionIMS processes signon input data when entered. If thesign-on is successful, message DFS3650I is sent tothe terminal. Message DFS3650I provides the statusof the terminal session and user.

Operator responseEnter valid signon data as requested. For RACF, thesign-on data consists of the following strings:User ID

A user identification of eight characters or less.User Descriptor

An optional keyword indicating a user descriptorname of eight characters or less that is used byIMS to build a user control block structure.

PasswordAn optional keyword indicating a password of eightcharacters or less (or, if supported, a passwordphrase of 100 characters or less) that is associatedwith the user identification. This field will havea non-display attribute. The password is requiredwhen RACF is used to verify the sign-on.

GroupAn optional keyword indicating a group name ofeight characters or less that is associated with theuser ID.

New PasswordAn optional keyword indicating a new userpassword of eight characters or less (or, ifsupported, a password phrase of 100 charactersor less) that replaces the current user passwordspecified in the password field. This field will havea non-display attribute.

Related referencez/OS: System code 483


http://www-01.ibm.com/support/knowledgecenter/SSLTBW_2.4.0/com.ibm.zos.v2r4.icha600/gk00013.htm?lang=en

Related information“DFS3650I” on page 1042SESSION STATUS.IMS Session Status Summary for 3270/SLU2Devices

DFS3650I SESSION STATUS.IMS Session Status Summary for3270/SLU2 Devices

ExplanationSession initiation was successfully completed for IMSterminals. For terminals requiring sign-on security,including dynamically defined terminals, the user hassuccessfully signed on to IMS. This message detailsthe status of the session and the user. The statusconditions indicated under current session status are:

ASR RESP RESP-INP LOCKMFST TEST RESP-INP-FP TRAC1/C2/C3/C4INOP CONV-HLD EXCL ACTIVINC-LTRM *PWD-CHG* CONV-ACT

The definitions of these terminal status indicators arein Status and attributes for the /DISPLAY command(Commands).

The status condition *PWD-CHG* indicates that thepassword for the current user was changed duringsignon processing.

The status condition INC-LTRM indicates thatthe LTERMs requested by the user signon exit(DFSSGNX0), or defined as part of the user descriptorused to build the user structure, were not allsuccessfully allocated to the user. Normally, therequested LTERM could not be obtained because aCNT exists by that name and is currently assigned toa different user. A /DIS ASMT USER command canbe issued to determine which LTERMs were allocatedsuccessfully to the user.

For ACF/VTAM terminals with 6 to 11 lines, thePRESET DESTINATION and CURRENT SESSIONSTATUS lines are omitted. For ACF/VTAM terminalswith less than six lines and the MFS formatted masterterminal, only the first line are displayed.

The third form of the message, the key message, isdisplayed when the pre-edit message was unable tobe built. For all of the conditions that cause DFS3650to be sent, see Session status for DFS3650I.

Session status for DFS3650I

This message is sent for various reasons. The followingtable contains the conditions under which thesemessages are sent to different devices.

In the following table, a Y in the cell indicates thatthe condition is valid for the device listed at the topof that column. An N indicates that this condition doesnot cause message DFS3649A to be sent to the devicelisted at the top of that column. Blank cells in thetables indicate that the condition is not applicable tothe device listed at the top of that column.

Table 24. Conditions for the DFS3650 message

Condition 3270

3270P

FIN

SLU1

SLU2

SLU4

SLUP

LU6

NTO

Sessioninitiation,staticterminal,sign-on notrequired

Y Y Y Y Y Y

Sign-oncompleted-NOTERMspecified

N N N N N N

Sessioninitiationwith goodsign-on data

Y Y Y Y Y Y

Sessioninitiation(unattachedmode)

N N

Sessioninitiation(autologgedon)

N N N N N N

/SIGN ON,staticterminal

Y Y Y Y Y Y Y Y

/SIGN ON,dynamicterminal

Y Y Y Y Y Y Y Y

System actionThe IMS system continues processing.

Operator responseVerify the status of the session and user. It is possibleto enter input such as transactions, commands, andmessage switches.


http://www.ibm.com/support/knowledgecenter/SSEPH2_15.1.0/com.ibm.ims15.doc.cr/imscmds/ims_statusattribtable.htm#ims_cr1statusattribtable

http://www.ibm.com/support/knowledgecenter/SSEPH2_15.1.0/com.ibm.ims15.doc.cr/imscmds/ims_statusattribtable.htm#ims_cr1statusattribtable



DFS3651I LOGON REJECTED - NODEnnnnnnnn. DEFAULT LOGONDESCRIPTOR xxxxxxxx REQUIREDBUT NOT FOUND.

ExplanationWhile creating the correct session control blocks fornode nnnnnnnn, IMS determined that the defaultlogon descriptor xxxxxxxx was required but not found.

System actionThe logon attempt is rejected.

System programmer responseDetermine if the node was rejected because it was ofan LU type not supported by the installation. If thenode is a valid type, determine why the default logondescriptor for that type could not be located.

User responseContact the system programmer.

DFS3652X DYNAMIC TERMINALDESCRIPTORS NOT AVAILABLE

ExplanationIMS initialization or the MFS Device CharacteristicsTable utility was unable to locate the ETO descriptorsfrom the library with the ddname PROCLIB. IMSinitialization requires at least one valid logondescriptor and one valid user descriptor whenETO=YES is requested. The MFS Device CharacteristicsTable utility requires at least one device descriptor.

System actionIMS initialization abnormally terminates with abend0015. The MFS Device Characteristics Table utilityends with a return code of 12.


System programmer responseDetermine whether the descriptor members thatshould contain ETO descriptors exist in the dataset with the ddname PROCLIB. The member namesare DFSDSCMa and DFSDSCTb, where a is the IMSnucleus suffix and b is from the DSCT parameter,during IMS initialization. If running the MFS DeviceCharacteristics Table utility, a and b are from theDSCMSUF and DSCTSUF parameters.

If the members do not exist, create them. If they doexist, determine why IMS was not able to locate themembers in the data set with the ddname PROCLIB,or why the required descriptors do not exist in themembers.



DFS3653 ATTRIBUTE MIXED WITHSPECIFIC PARAMETER.

ExplanationA command was entered with a mix of attributesand parameters. If an attribute is specified, all otherparameters must be attributes. If a non-attributeparameter is specified, all other parameters must benon-attribute parameters.


Operator responseReenter the command with all attribute parameters orall non-attribute parameters.

DFS3654 COMMAND NOT ALLOWED FORDYNAMIC TERMINALS.

ExplanationAn /EXCLUSIVE NODE or /TEST NODE commandwas entered for a node that is an ETO terminal.



Commands /EXCLUSIVE NODE and /TEST NODE areinvalid for ETO terminals.


Operator responseEnter the command again with a node parameter thatis static, or enter /EXCLUSIVE USER or /TEST USERto associate exclusive or test status with the user.

Module:DFSICL50

DFS3655 USER SIGNED ON, /EXIT USERCOMMAND INVALID

ExplanationIn the /EXIT command with only the CONV and USERkeywords (the NODE is not specified), the specifieduser is signed on. This format of the /EXIT commandis valid only when the user is not signed on.


Operator responseReenter the /EXIT command with the NODE keyword.

DFS3656A IMS PASSWORD VERIFICATION

Explanation:For an explanation and actions, see DFS3656.

Related informationDFS3656IMS PASSWORD VERIFICATION, PLEASE RE-ENTER NEW PASSWORD:

DFS3656 IMS PASSWORD VERIFICATION,PLEASE RE-ENTER NEWPASSWORD:

or

IMS PASSWORD VERIFICATION, SIGN ON WITHVERIFY KEYWORD

ExplanationThe user of a VTAM terminal is attempting to changethe password or password phrase during a signon.When password or password phrase verification is

enabled, this message prompts the user to reenter thenew password or password phrase.

The first form of the message, which contains thetext PLEASE RE-ENTER NEW PASSWORD: is the onenormally received by the user, and prompts the userto reenter the new password or password phrase. Thepassword or password phrase is not displayed to theterminal.

The second form of the message, which containsthe text SIGN ON WITH VERIFY KEYWORD, isthe one normally received when there are resourceconstraints, and it is not possible for IMS to issue thefirst form. In this case, the user is prompted to reenterthe password or password phrase using the /SIGN ONcommand.

System actionIMS verifies that the new password or passwordphrase entered as a response to this messagematches the password or password phrase originallyentered. If verification is successful, signon completessuccessfully, and message DFS3650I is displayed withthe status, *PWD-CHG*, to indicate the passwordor password phrase was changed. If verification isunsuccessful, signon fails with DFS3649A, return code304.

Operator responseIf the first form of the message is received, reenter thenew password or password phrase. The new passwordor password phrase is not displayed on the terminal.

If the second form of the message is received, enterthe /SIGN ON VERIFYxxxxxxxx command, wherexxxxxxxx is the new password or password phrase.

Related information“DFS3649A” on page 1036/SIGN COMMAND REQUIRED.“DFS3650I” on page 1042SESSION STATUS.IMS Session Status Summary for 3270/SLU2Devices

DFS3657 DESCRIPTOR yyyyyyyyyyyyyyyyIN MEMBER DFSYDTC EXCEEDSTHE MAXIMUM OF 50 RECORDS.DESCRIPTOR IGNORED.

ExplanationIMS was initializing dynamic descriptors and found adescriptor which had more than the maximum of 50records.



System programmer responseIf the descriptor must be present, shorten it to 50records or less. Then restart IMS.


Module:DFSYIDC0


DFS3658X GET REQUEST FAILED FORxxxxxxxx DESCRIPTOR BLOCK.

ExplanationIMS was unsuccessful in obtaining a storage fordescriptor block xxxxxxxx while initializing the ETOterminal or LU 6.2 descriptor.



System programmer responseIf dynamic resources are required, increase theavailable storage to the IMS control region.



DFS3659X SYN ERROR OCCURRED READINGDESCRIPTOR yyyyyyyyyyyyyyyy INMEMBER DFSYDTC

or

I/O ERROR OCCURRED READING DESCRIPTORyyyyyyyyyyyyyyyy IN MEMBER DFSYDTC

ExplanationIMS initialization or the MFS Device CharacteristicsTable utility received an I/O error while reading thedescriptor records for descriptor name xxxxxxxxxfrom the member yyyyyyyy of IMS.PROCLIB. Whenthis message is received from the MFS DeviceCharacteristics Table utility, xxxxxxxx containsDCTABLE.

System actionIMS initialization abnormally terminates with abend0015. The MFS DCT Utility ends with a return code of12.


System programmer responseRebuild member yyyyyyyy of IMS.PROCLIB for whichthe I/O error occurred.


Module:DFSYIDC0


DFS3660W EDIT ROUTINE xxxxxxxx DEFINEDBY DESCRIPTOR yyyyyyyyCANNOT BE FOUND. DESCRIPTORIGNORED.

ExplanationIMS was processing the EDIT= parameter of logondescriptor yyyyyyyy when the search for the physicaledit routine xxxxxxxx was unsuccessful. If the editroutine xxxxxxxx is not used by any static terminalsdefined in the IMS system definition, you must bind itinto IMS.SDFSRESL.





System programmer responseCorrect the physical edit routine name on descriptoryyyyyyyy, if it is incorrect. If the physical edit routinename xxxxxxxx is correct, link edit the module into theIMS.SDFSRESL. The descriptor yyyyyyyy is unavailableuntil the problem is corrected and IMS is restarted.



DFS3661W DESCRIPTOR xxxxxxxx HASAN INVALID OR DUPLICATEKEYWORD yyyyyyyy. THEKEYWORD IS IGNORED.

ExplanationWhile IMS was processing the definition forETO descriptor xxxxxxxx, an invalid keyword(unrecognizable string or invalid for this device type)or duplicate keyword yyyyyyyy was found.

System actionThe invalid or duplicate keyword string is ignored.

System programmer responseLocate the descriptor having the resource nameof xxxxxxxx. Correct the keyword in error. If thedefault selected by IMS for the erroneous keyword isincorrect, restart IMS with the corrected descriptor.



DFS3662W COMMAND REJECTED BY reason

ExplanationThis message is issued when a command from aterminal is rejected by security checking.

If enhanced command security is included in the IMSsystem, the command initially goes through a RACFsecurity check.

reason can be one of the following:

RACF; return codeDFSCCMD0DEFAULT COMMAND SECURITY

If RACF rejected the command, and the DFSCCMD0user exit routine did not override the RACF rejection,IMS displays the message: COMMAND REJECTED BYRACF; return code.

Possible return codes from RACF:USER NOT AUTH; RC=08

User is not authorized for the command by RACF.SIGNON REQUIRED

Command is RACF-protected and the user is notsigned on.

RACF NOT ACTIVE; RC=12RACF is not active, and RACF transaction orcommand class is active.

INVALID EXIT RC; RC=16RACF installation exit routine returned an invalidreturn code.



NO PASSWORD; RC=36RACF password verification is required but nopassword was given.


Operator responseYou are not authorized to use the command thatwas rejected. See the system programmer if youbelieve you should be authorized to use the rejectedcommand.

Module:DFSCIOB0

DFS3663I UNSUPPORTED DEVICE-TYPELOGON REJECTED- NODE xxxxxxxx

ExplanationThe LU type, as specified in the CINIT of the logging-on terminal, is not allowed by IMS.




System programmer responseVerify that the mode table entry for the indicated LUspecifies an LU type acceptable to IMS. Verify that themode table entry for the indicated LU specifies devicecharacteristics correctly.

DFS3664I DFSDFxxx SYSID nnnn ISIGNORED BECAUSE IT ISALREADY DEFINED AS A SYSIDFOR A REMOTE SYSTEM

ExplanationThe nnnn value specified in the SYSID= parameter inthe MSC section of the DFSDFxxx PROCLIB member isalready defined as a SYSID for a remote IMS system inan MSC network. IMS rejects this nnnn value becauseit is an invalid local SYSID override value.

System actionThis message is issued to report error conditions forthe IMS master terminal operator.

System programmer responseCorrect the SYSID= value and restart IMS.

Module:DFSRMC00

Related tasksDefining a SYSID (Communications andConnections)Related referenceMSC section of the DFSDFxxx member (SystemDefinition)

DFS3665W DESCRIPTOR MSNAME xxxxxxxxCONTAINS DUPLICATE REMOTELTERM yyyyyyyy.

ExplanationIMS initialization detected that descriptor xxxxxxxxcontains a remote LTERM name of yyyyyyyy that is aduplicate of another remote LTERM in the system.

System actionThe remote LTERM xxxxxxxx is ignored and processingcontinues.

Operator response:

Remove the duplicate remote LTERM from theMSNAME descriptor.

DFS3666W DESCRIPTOR NAME xxxxxxxxCONTAINS INVALIDCHARACTERS. DESCRIPTOR ISIGNORED.

ExplanationIMS initialization detected that descriptor xxxxxxxxcontains invalid characters and does not conform tothe IMS rules for valid resource names. All descriptornames must be 1 to 8-alphanumeric characters, thatis, letters A through Z, digits 0 through 9, and nationalcharacters #, $, and @. For logon and user descriptors,the first character must be alphabetic (A-to-Z, #, $, or@).

System actionThe descriptor xxxxxxxx is ignored and processingcontinues.

System programmer responseCorrect the name in error.



DFS3667W DESCRIPTOR xxxxxxxx CONTAINSAN INVALID NAME OF yyyyyyyy.THIS REMOTE LTERM IS IGNORED.

ExplanationIMS initialization detected that descriptor xxxxxxxxcontains a remote LTERM name yyyyyyyy that does notconform to IMS rules for valid LTERM names.

The rules for the LTERM name are:

• It cannot match a transaction name or an MSNAMElink name.

• It cannot start with the characters INQU.• It cannot be WTOR or DFSMTCNT.• All remote LTERM names must be 1 to 8-

alphanumeric characters, that is, letters A throughZ, digits 0 through 9, and national characters #, $,and @.

If the queue name is omitted in the LTERM parameter,field yyyyyyyy contains N/A.


http://www.ibm.com/support/knowledgecenter/SSEPH2_15.1.0/com.ibm.ims15.doc.ccg/ims_msc_admin_defining_sysid.htm#DefiningASystemIdentifierSYSID

http://www.ibm.com/support/knowledgecenter/SSEPH2_15.1.0/com.ibm.ims15.doc.ccg/ims_msc_admin_defining_sysid.htm#DefiningASystemIdentifierSYSID



System actionThe remote LTERM xxxxxxxx is ignored and processingcontinues.

System programmer responseChange the name in error.



DFS3668W DESCRIPTOR xxxxxxxx CONTAINSQUEUE yyyyyyyy WITH ANINVALID NAME.

ExplanationIMS initialization detected that descriptor xxxxxxxxcontains a queue name yyyyyyyy that does notconform to the IMS rules for valid LTERM names.

The rules for the LTERM name are:

• It cannot match a transaction name or an MSNAMElink name.

• It cannot start with the characters INQU.• All LTERM names must be 1 to 8-alphanumeric

characters, that is, letters A through Z, digits 0through 9, and national characters #, $, and @.

If the queue name is omitted in the LTERM parameter,field yyyyyyyy contains N/A.

System actionDescriptor xxxxxxxx is ignored, and processingcontinues.

System programmer responseChange the queue name in error.



DFS3669W DESCRIPTOR xxxxxxxx CONTAINSQUEUE ALREADY DEFINED BYDESCRIPTOR yyyyyyyy.

ExplanationIMS initialization processed descriptor records fordescriptor name yyyyyyyy. A subsequent descriptor,xxxxxxxx, attempted to build a control block with thesame name as the control block built by descriptoryyyyyyyy.

System actionDescriptor xxxxxxxx is ignored, and processingcontinues.

System programmer responseRemove the duplicate queue name from eitherdescriptor.



DFS3670W DESCRIPTOR xxxxxxxx HASINVALID PARAMETER yyyyyyyyFOR KEYWORD zzzzzzzz. THEDEFAULT WAS USED.

ExplanationIMS initialization detected an error in descriptorxxxxxxxx for parameter yyyyyyyy on keyword zzzzzzzz.

System actionThe default for this parameter is used. The remainingparameters for this keyword are skipped, and thedefaults are used instead.

System programmer responseCorrect the invalid parameter in descriptor xxxxxxxx.



DFS3671I INVALID DESCRIPTORSPECIFIED. DESC = aaaaaaaaNODE = bbbbbbbb


ExplanationIMS did not recognize the logon descriptor name asspecified in the user data field of the logging-on nodeCINIT. This message is also issued for an invaliddescriptor name override provided by the logon exit(DFSLGNX0).



System programmer responseVerify that the descriptor name specified in the logonrequest is defined to IMS.

DFS3672I SESSION ERROR. TYPE=aaaCODE=bb QUAL.=cc MSG=ddddIPADDR..PORT=eee.eee.eee.eee..fffff

ExplanationA session establishment or disconnection erroroccurred. This message supplies information to assistin diagnosing the problem indicated by messageDFSdddd.

In the message text:aaa

The VTAM exit driven when the error occurred.bb

The location code of the error.cc

The location qualifier of the error.dddd

The DFS message number.eee.eee.eee.eee

The TCP/IP address.fffff

The TCP/IP port number.



System programmer responseUse the indicated information to further identify thenature of the problem.

Related referenceQualifier codes (Diagnosis)

DFS3673W DESCRIPTOR xxxxxxxx CONTAINSLTERM yyyyyyyy WHICH ISSTATICALLY DEFINED.

ExplanationThis message is issued when a remote LTERM or aqueue for the descriptor xxxxxxxx is already defined tothe system. If yyyyyyyy is already defined, then it musthave been defined during the system definition.

System actionFor a remote LTERM, then it is ignored. If this is aqueue for a descriptor, the user descriptor is ignored.

System programmer responseRemove the descriptor or the LTERM definition in thesystem definition.



DFS3674W MNPS SPECIFIED, USERVARIGNORED

ExplanationIn an extended recovery facility (XRF) environment,the MNPS and USERVAR keywords were both specifiedduring IMS initialization, in IMS execution parameters,or DFSHSBxx PROCLIB member. These are mutuallyexclusive keywords, and MNPS overrides the USERVARkeyword.

System actionIMS operates XRF using MNPS. The USERVAR isignored.

Operator responseVerify that MNPS is the environment you want, andreinitialize IMS if necessary.


http://www.ibm.com/support/knowledgecenter/SSEPH2_15.1.0/com.ibm.ims15.doc.dgr/ims_qualif_codes.htm#ims_qualif_codes

System programmer responseVerify MNPS and USERVAR are defined correctly in theIMS execution parameters or PROCLIB members, orboth.

Module:DFSAINB0

DFS3675I INVALID LOGON TO THE APPLIDACB - NODE nodename

ExplanationIn an extended recovery facility (XRF) environment,IMS was using MNPS for session persistence. As aresult, there were two VTAM application control blocks(ACB) in use - the MNPS ACB and the APPLID ACB.The APPLID ACB can only be used by the MTO andthe XRF surveillance link. However, a VTAM terminalnodename, which is not the MTO or surveillance link,attempted to logon to the APPLID ACB.

System actionIMS rejects the logon attempt.

Operator responseLog the terminal onto the MNPS ACB. Use /OPNDST command to automatically use this ACB, oruse /DISPLAY ACTIVE DC or /DISPLAY HSB todetermine the MNPS ACB name.


Module:DFSCNXA0

DFS3676I ETO SUPPORT NOT AVAILABLE-FEATURE NOT INSTALLED ORLICENSED.

ExplanationInitialization of the Extended Terminal Option (ETO)had been requested using the execution parameterETO=Y. However, initialization detected that the ETOfeature has not been installed or licensed.


Operator responseSee system programmer response.

System programmer responseYou can suppress this message by changing the IMSexecution parameter to ETO=N. If ETO is required, itmust be installed or licensed.



DFS3677W aaaaaaaa HAS AN INVALIDPARAMETER FOR KEYWORDbbbbbbbb. KEYWORD ISIGNORED, DEFAULT NOT USED.

ExplanationIMS was processing dynamic terminal descriptorswhen it encountered an invalid parameter for keywordbbbbbbbb.

System actionThe keyword is ignored, but the default is not used.

System programmer responseLocate the descriptor with the resource nameaaaaaaaa. Correct the invalid parameter. If IMScannot run without this keyword, IMS must berestarted.



DFS3678E TYPE t DESCRIPTOR desc_id INMEMBER member EXCEEDS THEMAXIMUM OF nnn. IT WASIGNORED.

ExplanationThe number of type-t descriptors in the DFSYDTxPROCLIB members exceeds the maximum number,nnn, that can be defined for the descriptor type. Thedescriptor identified in the message text is ignored.

OTMA initializes descriptors in the order in which theyare coded in the DFSYDTx PROCLIB member. The



descriptor identified in the message text by desc_idmight not be the descriptor that was added to causethe maximum number to be exceeded.

In the message text:t

The descriptor type, either D or M.

Type D descriptors are OTMA destinationdescriptors. Type M descriptors are OTMA clientdescriptors and the DFSOTMA descriptor, if it isdefined.

desc_idThe ID of the descriptor. For type D descriptors,this is the destination name. For type Mdescriptors, this is the OTMA client name.

memberThe name of the OTMA DFSYDTx member inthe IMS.PROCLIB data set that contains thedescriptors.

nnnThe maximum allowable number of descriptors forthe descriptor type that is identified by t.

System actionThis message is issued, OTMA ignores the descriptor,and IMS continues to run normally. The clientor destination definitions in the descriptor that isidentified in the message text are not available for use.

Programmer responseEither adjust the maximum allowable number ofdescriptors for the descriptor type that is identified inthe message text or delete or reuse any descriptorsthat are no longer required.

The maximum for client (type-M) descriptors isdefined by the MDESCMAX parameter in the DFSOTMAdescriptor. The default is 255.

The maximum for destination (type-D) descriptors isdefined by the DDESCMAX parameter in the DFSOTMAdescriptor. The default is 510.

For destination descriptors for ALTPCB destinations,if you cannot increase the maximum allowablenumber and you cannot delete or modify any existingdestination descriptors to accommodate the newdescriptor, you can code the definitions in theOTMA Destination Resolution exit routine (OTMAYPRX)and the OTMA User Data Formatting exit routine(DFSYDRU0).

If you modified any client descriptors or the DFSOTMAdescriptor, restart IMS to add the changes to theonline IMS system.

If you modified any destination descriptors in theDFSYDTx member, you must cold start IMS to add thechanges to the online system.

If you modified or replaced any destination descriptorsby using the UPDATE OTMADESC, DELETE OTMADESC,and CREATE OTMADESC commands, you do not needto restart IMS.

Module:DFSYIDC0

Related referenceDFSYDTx member of the IMS PROCLIB data set(System Definition)

DFS3679E THE DIRECTORY DATA SET ISFULL.

ExplanationThe IMS directory data set is full.

System actionThe processing for the IMPORT DEFNSOURCE(CATALOG) command or the automaticactivation of the DDL definitions ends abnormally.Upon resubmission of the IMPORT command or DDLstatements, IMS allocates a new data set for the IMSdirectory internally automatically.

User responseResubmit the IMPORT command or DDL statements.Because some resource changes might have beenprocessed already, it is normal to see reason code 121(resource has no change) or message DFS4387I.

Module:DFSMOLS0


DFS3680W UNABLE TO ADD EDIT ROUTINExxxxxxxx IN DESCRIPTORyyyyyyyy TO TABLE. DESCRIPTORIGNORED.

ExplanationIMS issues this message during initialization whenit cannot expand the size of the dynamic user editroutine name and address table.

System actionThe descriptor ignored.


http://www.ibm.com/support/knowledgecenter/SSEPH2_15.1.0/com.ibm.ims15.doc.sdg/ims_dfsydtx_proclib.htm#ims_dfsydtx_proclib

http://www.ibm.com/support/knowledgecenter/SSEPH2_15.1.0/com.ibm.ims15.doc.sdg/ims_dfsydtx_proclib.htm#ims_dfsydtx_proclib


System programmer responseIncrease the amount of virtual storage available toIMS.



DFS3681W DESCRIPTOR NAME XXXXXXXXSAME AS TRANSACTION NAME.

ExplanationThis message is issued when the LU 6.2 descriptorinitialization routine attempts to create a descriptorwhich has the same name as a transaction nameinitialized by the ETO initialization routine.

System actionThis LU 6.2 descriptor is ignored.

System programmer responseRemove the descriptor definition from the input.



DFS3682W DESCRIPTOR NAME XXXXXXXXSAME AS STATIC LTERM NAME.

ExplanationThis message is issued when the LU 6.2 descriptorinitialization routine attempts to create a descriptorwhich has the same name as a static LTERM nameinitialized by the ETO initialization routine.





DFS3683W DESCRIPTOR NAME XXXXXXXXSAME AS DESCRIPTOR LTERMNAME.

ExplanationThis message is issued when the LU 6.2 descriptorinitialization routine attempts to create a descriptorwhich has the same name as a descriptor LTERM nameinitialized by the ETO initialization routine.





DFS3684W DESCRIPTOR xxxxxxxx EXCEEDSTHE MAXIMUM OF 8 LTERMS.DESCRIPTOR IGNORED.

ExplanationIMS was initializing dynamic descriptors and found auser descriptor which had more than the maximum of8 LTERM= keywords.


System programmer responseReduce the number of LTERM keywords specified onthe user descriptor to 8 or less, then restart IMS.





DFS3685I variable output headings

ExplanationThis message is issued to improve the readability ofthe output written by the ACB Generation and CatalogPopulate utility (DFS3UACB).

In the message text:variable output headings

The output headings printed with this messageinclude:

• C O M B I N E D A C B G E N & P O P U L A T E U TI L I T Y

• *** P O P U L A T I O N I N P U T P A R M S ***• *** E N D O F P O P U L A T I O N P A R M S ***

System actionThe DFS3UACB utility continues processing andwriting additional output to the console.


Module:DFS3UACB

Related referenceACB Generation and Catalog Populate utility(DFS3UACB) (System Utilities)

DFS3686I variable message text RC=rc

ExplanationThis message is issued to indicate the processingstatus of the ACB Generation and Catalog Populateutility (DFS3UACB).


The return code, if any, issued by the DFS3UACButility.

variable message textThe output headings printed with this messageinclude:

• DFS3UACB ACBGEN PROCESS COMPLETEDSUCCESSFULLY, RC=00

• DFS3UACB ACBGEN PROCESS COMPLETE,RETURN CODE RC=xx

• DFS3PPRM DD CARD FOUND, DEFAULT PARMSBEING OVERRIDDEN

• DFS3UACB CATALOG POPULATE PROCESSCOMPLETED SUCCESSFULLY, RC=00

• DFS3UACB CATALOG POPULATE PROCESSCOMPLETE, RETURN CODE RC=xx

System actionProcessing continues until the final status message isissued.


Module:DFS3UACB


DFS3687E variable message text

ExplanationThe ACB Generation and Catalog Populate utility(DFS3UACB) encountered an error.

In the message text:variable message text

The message text that follows the messagenumber. The message text can be one of thefollowing:

• DFS3PPRM DD DUMMY NOT ALLOWED• AN ERROR OCCURRED OPENING THE

DFS3PPRM DATASET• NO DFS3PPRM STATEMENTS FOUND• UNEXPECTED ERROR - UNABLE TO DETERMINE

SOURCE

System actionProcessing continues until the final status message isissued.

Programmer responseIf you intended to provide a DFS3PPRM DD statement,correct the error and rerun the utility.

If you the default settings of the IMS Catalog Populateutility (DFS3PU00) are acceptable, you do not need totake any action.

Module:DFS3UACB


http://www.ibm.com/support/knowledgecenter/SSEPH2_15.1.0/com.ibm.ims15.doc.sur/ims_catalog_dfs3uacb.htm#ims_catalog_dfs3uacb





DFS3688I Transaction aaaaaaaaexpired: EXPRTIME=nnnnnn,ELAPSE=ssssss

or

Transaction expired

or

Transaction aaaaaaaa expired: ELAPSE=ssssssTPIPE=pp TMEMBER=mm

ExplanationA transaction has been discarded because it hasexpired. This message is sent to the terminal as aninformational message. The decision to cause thetransaction to expire was based on the differencebetween the transaction arrival time and the storeclock (STCK) value at GU time. The difference iscompared with the EXPRTIME value of the schedulermessage block (SMB). If the difference is equal to orgreater than the EXPRTIME value, the transaction isdiscarded and log record X'67D0' is written. In themessage, TRAN is the SMBNAME, EXPRTIME is theEXPRTIME parameter of the TRANSACT macro, andELAPSE is the difference between the STCK value atGU time and the transaction arrival time.


The transaction code.mm

The tmember name for the OTMA input message.nnnnnn

The time specified in the SMB.pp

The tpipe name for the OTMA input message.ssssss

The difference between the transaction arrivaltime and the STCK value at GU time. The elapsedtime is represented in hexadecimal number.

The second version of this message is sent to theterminal only when a DFSPOOL GET fails.

System actionAfter discarding the transaction, the system retrievesthe next transaction in the message queue and

processes it. If no message exists, a QC status codeis returned to the message processing program (MPP).


DFS3689W USE OF {TRAN|LTERM|DB|PROG}resourcename BY {LOCK|UNLOCK}REJECTED; reason

ExplanationThe transaction, LTERM, database, or programresource entered as a parameter on the /LOCK or /UNLOCK command is not authorized for use by the userentering the command. The reason for the rejection is:RESOURCE NOT AUTH; RC=08

User is not authorized to this IMS resource byRACF.

RACF NOT ACTIVE; RC=12RACF is not active.

BY RACF EXIT; RC=16RACF exit gave an invalid return code.



RACF DS DELETED; RC=28The resource class was selected by RACROUTEREQUEST=LIST GLOBAL=YES, but the RACF dataspace was deleted.

NO PASSWORD; RC=36User verification is required; no password wassupplied.

WRONG PASSWORD; RC=40User verification failed password.

IMS EXIT CD; RC=xxThe IMS resource was not authorized. xx is thereturn code.

Note: RC= represents a decimal value.

Additional codes can be supplied by a user-writtenIMS exit routine.

System actionThe command entered is ignored.

Operator response:




Reenter the command with the correct password,or enter another IMS resource that does not violatesecurity.



Module:DFSICL90

DFS3690 XRF CLASS 1 RECOVERYCHANGED TO CLASS 2 NODE X(USER Y)

ExplanationNode X was defined for XRF class 1 support, but thesession could not be recovered successfully duringthe takeover process by the alternate IMS system.Takeover for node X is changed to that of class 2.

System actionThe session with node X is terminated and thenautomatically restarted by IMS as defined for XRFclass 2 support. Additional information is availableusing IMS trace records (X'6701' with IDs of 'HCSW','CVCV', and 'CVCT'). If sign-on was required, then aDFS3649A /SIGN COMMAND REQUIRED message issent.

Operator response:(entering terminal operator) The terminal operatormight be required to sign on again as appropriate.Enter the last input again and the last output mightbe sent again by IMS.

Programmer responseIMS automatically terminates the session with nodeX and then automatically attempt to reestablish it.If subsequent session failures occur, the session canalso be reestablished by node x or by an IMS /OPNDSTcommand.


Module:DFSCMT50

Related informationDFS3649A/SIGN COMMAND REQUIRED.“IMS problem determination” on page 11


DFS3691W GENERIC RESOURCES START/STOP FAILED, SETLOGONRC=xx,FDB2=yy

ExplanationAn IMS system attempted to join a generic resourcegroup, but failed.

System programmer responseFor an explanation of the RC and FDB2 fields,see z/OS Communications Server IP and SNACodes (SC31-8791) or VTAM Messages and Codes(SC31-6493). Correct the problem before retrying.

If RC=14x and FDB2=86x, the problem is caused byexisting VTAM sessions with IMS. Issue a /CLSDSTNODE command from a non-VTAM terminal (such asthe system console) for any active VTAM terminals,including the MTO.

Related referencez/OS: RPL RTNCD and FDB2 return codecombinations

DFS3692W GENERIC RESOURCES INVALIDFOR XRF SYSTEMS, GRSNAMEIGNORED.

ExplanationA generic resources command was attempted on anExtended Recovery Facility (XRF)-capable system. IMSXRF systems cannot participate as members of ageneric resources group.

DFS3693W SYSTEM NOT GENERICRESOURCES CAPABLE -COMMAND REJECTED

ExplanationA generic resources command, such as /DISPLAYAFFIN, was issued on an IMS system that is notcurrently configured to support generic resources.


Programmer responseEnable either TCP/IP generic resources or VTAMgeneric resources, and then reenter the command.




DFS3694W START GENERIC RESOURCESTERMINATED, VTAM FUNCTIONNOT ENABLED

ExplanationIMS attempted to join a Generic Resource Group,but VTAM is not enabled for the generic resourcesfunction.


System programmer responseEnsure that VTAM is sysplex capable, and connected tothe generic resource CF structure ISTGENERIC. Aftermaking this corrections, you can attempt to start IMSgeneric resources using the /START VGRS command.

Programmer responseEnable generic resources, then reenter the command.

DFS3700 PARAMETER ALL NOT VALID WITHKEYWORD

ExplanationThe parameter ALL is not allowed for the keywordspecified in the command. The IMS keyword table(DFSCKWD0) was modified to prevent the use of theALL parameter with this keyword for IMS commands(except for commands entered by an AOI application)by specifying ALL=NO on the KEYWD macro.


Operator response:(master terminal) Reenter the command specifyingindividual resource names or a range of resourcenames, if applicable.

Related referenceIMS Command Language Modification facility(DFSCKWD0) (Exit Routines)


http://www.ibm.com/support/knowledgecenter/SSEPH2_15.1.0/com.ibm.ims15.doc.err/ims_dfsckwdo.htm#ims_dfsckwdo

http://www.ibm.com/support/knowledgecenter/SSEPH2_15.1.0/com.ibm.ims15.doc.err/ims_dfsckwdo.htm#ims_dfsckwdo



DFS3701I INSUFFICIENT STORAGE TORESTART AREA areaname-AREASTOPPED

ExplanationDuring an emergency restart, the emergency restartprocessor, DBFERSTO, was unable to obtain storagefor an internal control block, ADSC, used to recover thenamed DEDB area data set. Consequently, DBFERSTOwas not able to restart the area.

System actionThe indicated area is stopped and emergency restartcontinues.

Programmer responseEither restart IMS with more virtual storage orcontinue with the current restart, and run theDatabase Recovery utility, DFSURDB0, for theindicated area.

DFS3702I AREA/ADS OPEN FAILEDREASON CODE=nn messagesubtext

ExplanationIMS is shutting down or IRLM is being disconnectedfrom this IMS.

The DEDB area or ADS failed to open. The reasoncode indicates the cause of the failure. The secondmessage contains one of the following reason codesand message subtext (nn) which briefly explains thecause for the error.Code (Dec)

message subtext01

AREA=areaname DD=ddname DEVICE TYPE NOTSUPPORTED

02AREA=areaname DD=ddname EQE EXISTS

03LOCK FOR UPDATE TO AREA=areaname FAILED

04AREA=areaname CI SIZE > USER DEFINEDBUFFER SIZE

05AREA=areaname BUFFER PAGE-FIXING FAILED

06AREA=areaname AUTHORIZATION FAILED

07UNLOCK FOR UPDATE TO AREA=areaname FAILED

08LOCK FOR READ TO AREA=areaname FAILED

09AREA=areaname HAS NO AVAILABLE ADS

10AREA=areaname DD=ddname DUPLICATE ddnameFOUND

11AREA=areaname SPACE FOR ADSC(S)UNAVAILABLE

12AREA=areaname RECEIVED A BAD RETURN CODEFROM DBRC

13AREA=areaname DD=ddname MEDIA MANAGERCONNECT FAILED

14AREA=areaname DD=ddname INCONSISTENTDSN SPECIFIED BETWEEN IN RECON AND INALLOCATED DATA SET

16AREA=areaname VSO I/O TOLERATED DATA LOST

17AREA=areaname DD=ddname ALLOCATIONFAILED

18AREA=areaname UPDATE LEVEL INCONSISTENCYEXISTS

19AREA=areaname DD=ddname 2ND CI I/O ERROROCCURRED

20AREA=areaname DD=ddname RDJFCB/MODCBERROR

21AREA=areaname ACCESS INTENT IS NOT UP/EXFOR REORGANIZATION RECOVERY

22AREA=areaname REORGANIZATIONIDENTIFICATION FAILED


23AREA=areaname ALL THE ADS'S ENCOUNTERED2ND CI ERROR

24AREA=areaname NOTIFY TO OTHERSUBSYSTEM(S) FAILED

25AREA=areaname SOME ADS ENCOUNTERED 2NDCI ERROR

26AREA=areaname ACBLIB AREA NUMBER NOTEQUAL DMAC

27AREA=areaname DD=ddname GETMAIN FORMEDIA MANAGER CONTROL BLOCKS FAILED

28AREA=areaname DBD AND DATA SETDEFINITIONS INCONSISTENT

29AREA=areaname IMS LEVEL OF AREA NOTSUPPORTED

30AREA=areaname CALC. NEXT SDEP NOT WITHINSDEP RANGE.

31AREA=areaname DD=ddname THE HIGH RBA ISLESS THAN THE END OF THE AREA

34AREA=areaname 2ND CI EEQE OWNED BYSHARING SYSTEM

35AREA=areaname UNABLE TO OBTAIN VSOCONTROL BLOCK


37AREA=areaname REQUEST FOR DATA SPACEFAILED

38AREA=areaname DATA SPACE AUTHORIZATIONFAILED


40AREA=areaname IMODULE GETMAIN FAILUREOCCURRED

41AREA=areaname COUPLING FACILITY CONNECTFAILED

42AREA=areaname VSO AREA HAS IOT EEQES

44AREA=areaname DD=ddname MADS I/O timing isdetected

45AREA=areaname REQUEST FOR VLOCK FAILED.

46AREA=areaname IS IN A QUIESCE STATE.

System actionWhen an open ADS failure occurs during theprocessing of the DEDB area data set Create utility, thenamed area continues processing. An invalid returncode is returned to the utility. Otherwise, the area isstopped.

Programmer responseCode (dec)

Meaning01

Check the appropriate VSAM catalog or JCL DDstatements if a disk device is specified for thenamed ADS. If dynamic allocation occurs, checkthe dynamic allocation parameter list to find adevice type specified for the named ADS. If adifferent device type was specified, correct thedevice type to the disk device and rerun the job.

02This condition should not occur. Check why thenamed ADS was changed to an available status.After changing the named ADS status to anunavailable status, rerun the job.

03The application program terminates when thedependent region abends. After preparing thetracing facilities for lock, rerun the job.

This reason code can be issued if a Fast Patharea open failed because the PI limit of 63 activewaiters was reached.

04Check the database definition (DBD) and the VSAMdefinition for the named area. Also, check theBSIZ in the startup procedure. Correct the controlinterval (CI) size or buffer size (BSIZ), and rerunthe job.

05The number of allocated buffers is not sufficientto fill the buffer allocation request. The number ofallocated buffers is defined by the DBBF parameterin the IMS EXEC parameters.


For a description of the dbbf value, see the IMSsystem definition information.

06Follow the Programmer response of messageDFS3709A or DFS3711A either of which mightprecede this message.

07See the description for reason code 03 in thismessage.

08See the description for reason code 03 in thismessage.

09Check an ADS list of the DBRC RECON data set andchange at least one ADS to an available status byusing the CHANGE.ADS command.

10The named ddname exists in the IMS subsystem,which means the ADS has been opened. If theADS to be opened is already open, delete the DDstatement for the named ddname. If the namedddname was incorrect, and thus coincidentallymatched another ddname in the IMS subsystem,correct the input ddname and then rerun the job.

11Rerun the job later when the common service area(CSA) usage is low.

12Check the information given for the DBRC RECONdata set for the named area. If the information isincorrect, correct the error and rerun the job.

13Follow the programmer response in messageDFS2569I, which precedes this message.

14Either the dsname specified in the ADS list of theDBRC RECON data set, the JCL DD statement, orthe dynamic allocation parameter list is incorrectlyspecified. Correct the specified dsname and rerunthe job.

16Case 1

The area had the virtual storage option activewhen an XRF takeover occurred, and an EEQEwas created to show that the area had I/Otolerated data in its data space. Before the I/Otoleration purge, one of the following eventsoccurred:

• The area was shut down internally due to asevere error and has not yet been recovered.

• IMS failed and was restarted with a coldstart; the area has not yet been recovered

Case 2The VSO area lost connection to its structure,and an EEQE for RBA 0 was created toindicate area has I/O tolerated data in the oldstructure. If an area is able to reconnect to theold structure, IMS resolves the I/O tolerationdata and deletes the EEQE. If the area wasconnected to a new structure, the I/O tolerateddata in the old structure is lost.

In either case, the I/O tolerated data has beenlost and the area must be recovered. Ensure theADS marks unavailable. Run the database recoveryutility to recover the lost data and delete the EEQE.

17If a DD statement is specified, specify the correctddname. If the DD statement is missing, specify aDD statement. (The DD statement is located in thecontrol region JCL.) If a dynamic allocation failed,follow the programmer response for DFS2502W orDFS2503W. Then, rerun the job.

18Run your database print program or a VSAMaccess method service program to print all thearea data sets. Find at least one correct ADS,issue a CHANGE.ADS command for those ADSsthat are incorrect, change the available status toan unavailable status, and rerun the job. Or followyour recovery procedure.

19, 20Check the DBRC RECON data set if the named ADSis set to an unavailable status. If the named ADSwas set to an available status, change the statusby the CHANGE.ADS command and rerun the job.

21Reorganization recovery is requested, but ACCESSINTENT is neither UP nor EX. Set ACCESS INTENTto UP or EX with /START DB ACCESS orUPDATE DB START(ACCESS) SET(ACCTYPE())command and rerun the job.

22The system tried to check whether thereorganization utility was running or had beenrunning among subsystems, but failed. Either IMSor IRLM might not be working correctly, thuscausing a notify error. Rerun the job, and if thesame error persists, restart IMS, IRLM, or both.

23In a block level sharing environment,reorganization recovery ended successfully, andthe system then tried to update the second CI orthe area, but failed. Run the database recoveryutility to recover the area, and then rerun the job.

24In a block level sharing environment,reorganization recovery ended successfully. The


system then tried to update the second CI of thearea for the other subsystems, but failed. EitherIMS or IRLM might not be working correctly, thuscausing a notify error. Rerun the job, and if thesame error persists, restart IMS or IRLM, or both,then rerun the job.

25Check which area data sets are not available in theDBRC RECON data set. If you want to recover thearea data set, run the DEDB Area Data Set Createutility, or rerun the job.

27Start the area when the common service area(CSA) usage is low.

28DBD information in the DMAC is inconsistent withthe area definition as found in the second CI of thearea or area data set.

Note: This message could be seen if the DEDBAlter utility was run, and PREOPEN opened thearea before restart or the XRF tracker processedthe log records to complete the DEDB Alter basedon the log record stream. Verify that the DMACfrom the IMS memory matches the DMAC on theADS before attempting to recover the DEDB area.This verification can be accomplished by manuallyinspecting the DMACs, or by forcing the area toopen by issuing /STO AREA , /STA AREA, andrunning a job to access the DEDB area. If theDMACs match or the area can be accessed, nofurther action is required.

One of the following events occurred:

1. An area definition was changed by a DBDGEN(for example, CISIZE, number of UOWelements, number of RAPS). If the DBDGEN isto be changed, redefine it and rerun the job.

2. An area was redefined with differentcharacteristics, such as CISIZE or CYLINDERS.If an area definition is to be changed, thearea must be reorganized by an UNLOAD/LOAD operation. Check the last DBDGEN andVSAM DEFINE for consistency with the currentcharacteristics or the area data set.

29During area open, the second CI of the area wasfound to have a structure for an IMS Release levelearlier than Version 1 Release 3. Determine whythe identifier is incorrect. Rerun the job with thecorrect data set.

The area must be reinitialized. Unload the area, runthe Initialization utility, and then reload the area.

30The RBA calculated as the next position to insertsequential dependents (DMACNXTS) is not withinthe range of valid RBAs for sequential dependentsfor the area. Print the second CI for the area. If theerror is not apparent from the second CI (DMAC),contact IBM Software Support for assistance.

31The high used RBA of the AREA/ADS was not equalto the high allocated RBA. The Fast Path AREAmight have been defined to VSAM, but the FastPath format/initialization program might not havebeen run, or the Database Image Copy utility or theDEDB Area Data Set Create utility might not havecompleted successfully.

Use the list catalog (LISTCAT) command to findthe high used and high allocated values. Deleteand redefine the AREA/ADS. Then, recover theAREA/ADS by either using the DEDB Initializationutility and an application to restore the data, orthe Database Image Copy utility and a forwardrecovery method.

34During Open processing of the specified Area, itwas determined that an EEQE exists for the secondCI of the Area and that the EEQE is owned by asharing IMS subsystem. On the sharing subsystem,use the /UNLOCK SYSTEM command to eliminatethe EEQE.

35During Area open, a request for a VSO controlblock failed. Rerun job when CSA use is lower.

36During Area open, a request for a new VSO controlblock failed. Rerun job when CSA use is lower.

37A request for a new data space was issued duringopen processing of the Area, but the request failed.See DFS2444I, which precedes this message.

38A new data space was obtained during openprocessing of the Area, but the request forauthorization of the data space failed. SeeDFS2445I, which is precedes this message.

39During Area open, a request for a new VSO controlblock failed. Rerun job when CSA use is lower.

40Determine if insufficient CSA/ECSA storage hasbeen allocated to IMS, or if excessive storage isbeing used.


41The area is not loaded into the Coupling Facility.This situation does not prevent access to the areaunless preceded by message DFS2819A.

42A /START AREA or UPDATE AREASTART(ACCESS) command was issued but thearea was not started because it has IOT EEQEs.Message DFS2492I is generated before messageDFS3702I RSN=42. See message DFS2492I foradditional information.

45ADS is still in long busy mode at open time. Duringopen processing for an SVSO area, a request toget the VLOCK failed. This lock serializes the SVSOprocessing across a data sharing environment.

46Stop the quiesce by issuing a UPDATE AREASTOP(QUIESCE) command.

Related information“DFS2492I” on page 716AREA aaaaaaaa HAS IOT EEQE - CANNOTACTIVATE VSO“DFS3709A” on page 1062UNABLE TO OBTAIN AUTHORIZATION FORDATA BASE dbname AREA areaname. REASONCODE=nn“DFS3711A” on page 1066NONRECOVERABLE DEDB AUTHORIZATIONERROR DEDB=dddddddd AREA=aaaaaaaa

DFS3704E DFSFIDN0 VER/REL=vvvv/rrrr,DFSRNID VER/REL=vvvv/rrrr

ExplanationThe ESAF In-Doubt Notification exit routine module(DFSFIDN0) is not at a compatible release or versionlevel with DFSRNID, the input parameter list for theexit routine. In the message text:vvvv

Version numberrrrr

Release number

The version and release numbers for the DFSFIDN0exit routine must match those of the DFSRNIDparameter list.

System action:The exit routine reports the failure and returns controlto IMS.

User response:Verify that the correct DFSFIDN0 exit routine moduleis defined to IMS.

Problem determination:This message indicates that DFSRNID is trying to passinput data to the exit routine module and that the exitroutine module is unable to interpret the data becauseit is not at the same level.

DFS3703I SIZE OF INDEPENDENTOVERFLOW HAS BEEN INCREASEDFOR AREA xxxxxxxx AREA DATASET DDN adsname

ExplanationDuring open processing of DEDB area xxxxxxxx,differences were found between the DBD from theACBLIB and the area data set. These differencesindicate that the size of the independent overflow partof the area was increased by the user with a DBDGEN.

System actionThe control block containing information from theACBLIB is updated with the information from the ADS,and normal open processing continues.

User responseIf the size of the area's IOVF was increased by aDBDGEN, no action is necessary.

DFS3705I AREA=areaname DD=ddnameCLOSED

ExplanationThe data set was closed normally by an internal stoprequest by the /STOP ADS or /STOP AREA commandto the area or ADS.


Programmer responseIf the ADS is closed because of error conditions orbecause an internal stop request was issued, andif message DFS2574I with a recovery-needed statusis issued to the master terminal operator followingthis message, submit an area or ADS recovery utility.No action is required if message DFS2574 is notaccompanied with a recovery-needed status.



AREA=aaaaaaaa CLOSED|STOPPED,(RECOVERY NEEDED, RSN=nn)

DFS3706I AUTOMATIC SDEP BUFFERMANAGEMENT DID NOT RUN ONAREA areaname OF DATABASEdatabase DUE TO UTILITYRUNNING ims_id

ExplanationThe area that is being examined currently has a utilitythat is running against it.


The name of the area that SDEP buffermanagement is processing.

databaseThe database for the area that SDEP buffermanagement is processing.

ims_idThe ID for the IMS that contains the area thatSDEP buffer management is processing.

System action:SDEP buffer management processing against this areawill not occur until the next SDEP buffer managementcycle.

System programmer response:Allow the utility to complete. This area will beprocessed during the next SDEP buffer managementcycle.

Module:DBFAQC00

DFS3707A PROCESSING INTENTVALIDATION ERROR BECAUSENO DMCB FOUND. DBD=dbdnamePSB=psbname

ExplanationDuring the PSB PROCOPT validation process at thedependent region schedule time, the internal controlblock, DMCB, was unable to find the IMS onlinesubsystem. The internal control block, DMCB of thenamed DEDB, is referenced by the named PSB.

System actionThe named PSB is stopped. For an MPP, the inputmessage is not processed. For a BMP or an IFP, thedependent region terminates abnormally with abend0046.

Programmer responseThis problem can occur if the DEDB is not defined inthe database statement for the IMS online subsystem.If required, the IMSGEN listing must be checked andthe IMS online subsystem must be regenerated.



DFS3708W DATA BASE=dbnameAREA=areaname IS NOTREGISTERED WITH DBRC

ExplanationThe named database or area was not registered withDBRC. IMS treats the area as though you specifiedexclusive use for the subsystem.

System actionOPEN processing continues for the area.

Programmer responseIf the area integrity protection is wanted in thedata sharing environment, register the area to DBRC.If registration is not wanted, make sure that noapplication program currently updates the area acrossthe IMS subsystems.

DFS3709A UNABLE TO OBTAINAUTHORIZATION FOR DATA BASEdbname AREA areaname. REASONCODE=nn

ExplanationThe IMS online subsystem failed to acquire thedatabase usage authorization through DBRC during theDEDB area open time. The following list indicates theexplanation and action for each reason code (nn):

CodesExplanation

For nn=01The requested authorization and currentauthorization are incompatible. If you are tryingto use data sharing, some possible causes of thiserror are:

• The DBRC database SHARELVL might be invalid.



• The database access intent among subsystemsis conflicting.

• IRLM are incorrectly connected to one anotherand to IMS.

System action: The named area is stopped forthe online subsystem, and the status code 'FH' isreturned to the application programs.

Programmer response: One of the followingresponses should be made:

1. Close the area in the other subsystems holdingthe incompatible database authorization byentering a /STOP or /DBR command, andrestart the area by entering a /STARTcommand in this subsystem.

2. Wait until the other subsystems close the area,and restart the area by entering a /STARTcommand in this subsystem.

For nn=02The database is not registered in the RECON dataset.

For nn=03The DEDB or area status prohibits furtherauthorization in the DBRC RECON data set becauseof a global /DBR, /STOP command or because ofan internal database or area stop command.


Programmer response: The following responsesshould be made:

1. Analyze the reason for the status that prohibitsfurther authorization, and take the requiredaction if necessary.

2. Reset the authorization status for the databaseor area by using the DBRC command,CHANGE.DB, or DBDS, and restart the area byentering a /START command in this subsystem.

For nn=05The area is marked as needing an image copy inthe DBRC RECON data set.


Programmer response: Run the Database ImageCopy utility, DFSUDMP0, for the named area, andrestart the area by using the /START commandafter the utility has run successfully.

For nn=06The area is marked as needing recovery in theDBRC RECON data set, or there are no area datasets in AVAIL status for the area.


Programmer response: Run the DatabaseRecovery utility, DFSURDB0, for the named area,and restart the area by using the /STARTcommand after the utility has run successfully.

For nn=08The requesting online subsystem is not authorizedto share the named area with other subsystems.


Programmer response: One of the followingresponses should be taken:

1. If an environment with inter-system datasharing and two IRLMs is required, change theSHARELVL from 2 to 3 by using the DBRCCHANGE.DB command for the named databaseand restart the area by using the /STARTcommand.

2. If an environment with intrasystem data sharingand a single IRLM is required, run the onlinesubsystem under the host processor authorizedfor the named area.

For nn=09The DBRC RECON data set indicates that thenamed area has been previously authorized inone or more online subsystems. Because theexit verification indicates that the subsystems areinactive, the named area cannot be authorized.


Programmer response: Wait until another onlinesubsystem ends restart processing and closes thearea, and then restart the area by using the /START command in the subsystem.

If the area was involved in data sharing with morethan one IRLM, the IRLMs must be reconnected.

For nn=10The area was previously authorized to thesubsystem.


Programmer response: Close the area holding theincompatible database authorization by enteringa /STOP or /DBR command; then restart the areaby entering a /START command.


For nn=11An invalid parameter was found in the databaseusage compatibility evaluation process. Probably,the database/area record in the DBRC RECON dataset is corrupted.


Programmer response: This condition is unlikely.Correct the problem associated with DBRC,and contact IBM Software Support for furtherassistance.

For nn=18The DBRC RECON data set indicates that thenamed area has "Alter Count" set.The named area cannot be authorized either aDEDB Alter for the area is currently in progressor the master IMS which the previous DEDBAlter utility for the named area ran under hasbeen abnormally terminated and has not yet beenrestarted.

System action: The named area is stopped forthe online system, and the status code "FH" isreturned to the application.

Programmer response: If the DEDB Alter utility iscurrently in progress, wait until the utility finishesand retry. If the DEDB Alter utility is not currentlyin progress, restart the master IMS so that theRECON status will be cleaned when processingrestarts, or use the following DBRC commands:

• CHANGE.DB with NOALTER to reset "Alter"status.

• CHANGE.DBDS with NODBQUI to reset"Quiesce" status.

For nn=20The named database or area is not registered withDBRC, and the FORCER option is specified in theDBRC RECON data set record.


Programmer response: Register the namedarea and area data sets with DBRC usingthe INIT.DBDS and INIT.ADS commands, andrestart the named area by using the /STARTcommand in this subsystem.

For nn=22The database or area is currently authorized toanother subsystem.

System action: Authorization for the requestedactivity is denied.

Programmer response: You must issue a /DBRcommand for the database or area for all IMSsubsystems at that site before trying the actionagain.

For nn=41The area is quiesced or in the process of beingquiesced.


Programmer response: Wait for the quiesce toend and rerun the job which failed authorization.The status of the area can be determined byissuing the /DISPLAY AREA QSC, the QUERYAREA command, or LIST.DBDS DBD(dbname)AREA(areaname) and examining the output.

For nn=42The area is not quiesce held and image copy isattempting authorization.


Programmer response: Wait for the quiesce toend and rerun the job which failed authorization.The status of the area can be determined byissuing the /DISPLAY AREA QSC command,the QUERY AREA command, or LIST.DBDSDBD(dbname) AREA(areaname) and examining theoutput.

If the image copy failed, wait for the quiesce toend or until the QUIESCE HELD flag is set on.You can set the QUIESCE HELD flag on usingthe UPD START(QUIESCE) OPTION(HOLD)command processing when quiesce has occurred.

For nn=43The DBRC RECON data set indicates that thenamed area has a randomizer name that isdifferent from the ACBLIB randomizer name thatwas passed in the ACBSHR=N environment. Thenamed area cannot be authorized because therandomizer names are different.

System action: The named area is stopped forthe online system, and the status code "FH" isreturned to the application.

Programmer response: Update the ACB library toreflect the DEDB ACB member change by usinglocal online change, member online change, orglobal online change.

DFS3710A UNABLE TO OBTAINAUTHORIZATION IN UTILITYFOR DATA BASE=dbnameAREA=areaname. REASONCODE=nn


ExplanationThe nn value in the message indicates the reasonfor the authorization failure in the DEDB utility. Thefollowing list indicates the explanation and action foreach nn code:

For nn=01The requested state and the current authorizationstate are incompatible.

System action: The Fast Path utility being used isnot invoked for this area.

Programmer response: One of the followingactions should be taken:

• Close the area in other subsystems holdingthe database authorization by entering a /STOPor /DBR command.

• Wait until other IMS subsystems close the area,and rerun the job.

For nn=06Either there is no available ADS, or the areais marked as needing recovery in the DBRCRECON data sets. The Database Image Copy utility,DFSUDMP0, is unable to obtain authorization for arecovery-needed area.

System action: The utility is not invoked for thisarea.

Programmer response: Run the DatabaseRecovery utility, DFSURDB0, before running theDatabase Image Copy utility to get a correctmemory dump.

For nn=07The ACCESS parameter of the online subsystem isunacceptable for running the DEDB Online utility.

System action: Processing is terminated for area.

Programmer response: Verify the ACCESSparameter of the online subsystem. Ask the masterterminal operator to change the database ACCESSparameter by using the /START command. Changeit to a level which is compatible with the currentDEDB Online utility.

For nn=08The requesting online subsystem is not authorizedto share the named area with other subsystems.

System action: The named area is stopped forthe online subsystem, and the status code FH isreturned to the application programs.

Programmer response: One of the followingactions should be taken:

• If an environment with intersystem datasharing and two IRLMs is required, change the

SHARELVL from 2 to 3 by using the DBRCCHANGE.DB command for the named database;then restart the area by using the /STARTcommand.

• If an environment with intrasystem data sharingand a single IRLM is required, run the onlinesubsystem under the host processor authorizedfor the named area.

For nn=10The area has been previously authorized to thesubsystem.

System action: The offline utility is not invoked forthis area.

Programmer response: Duplicate job namesmight have been used for the same area. Waituntil another IMS subsystem closes the area, andresubmit the job.

For nn=15The Database Recovery utility is run against aDEDB area when all other subsystems are notmarked abnormally terminated for the DatabaseRecovery utility.

System action: The Database Recovery utility isnot invoked for this area. The Database Recoveryutility terminates.

Programmer response: Make sure that there isno subsystem that has already authorized thisarea and that has not abnormally terminated. If asubsystem has authorized the area, wait until thatsubsystem unauthorizes the area, and then rerunthe Database Recovery utility.

For nn=16The area is not marked as recovery-needed in theDBRC RECON data sets. The DEDB Initializationutility is unavailable to obtain authorization for arecovery-not-needed area.

System action: The DEDB Initialization utilityterminates.

Programmer response: Make sure that the areais valid for initialization. If the area should beinitialized, then force the area to a recovery-needed status using a CHANGE.DBDS command,redefine the area using a VSAM access methodservice command, specify the utility area controlstatements again except for the ones alreadyinitialized, and rerun the utility.

For nn=20The named database or area is not registered withDBRC and FORCER option is specified in the DBRCRECON record.

System action: The Fast Path utility being used isnot invoked for this area.


Programmer response: Register the named areaand area data sets with DBRC using INIT.DBDSand INIT.ADS commands, and resubmit the job.

For nn=22The area is currently authorized to anothersubsystem.


System programmer response: Issue a /DBRcommand for the area for all IMS subsystems.

For nn=41The area is quiesced or in the process of beingquiesced.


Programmer response: Wait for the quiesce toend and rerun the job which failed authorization.The status of the area can be determined byissuing the /DISPLAY AREA QUIESCE command,the QUERY AREA command, or LIST.DBDSDBD(dbname) AREA(areaname) and examining theoutput.

For nn=42The area is not quiesce held and image copyattempting authorization.


Programmer response: Wait for the quiesce toend and rerun the job which failed authorization.The status of the area can be determined byissuing the /DISPLAY AREA QSC command,the QUERY AREA command, or LIST.DBDSDBD(dbname) AREA(areaname) and examining theoutput.

If the image copy failed, wait for the quiesce toend or until the QUIESCE HELD flag is set on.You can set the QUIESCE HELD flag on usingthe UPD START(QUIESCE) OPTION(HOLD)command processing when quiesce has occurred.


Module:DBFDBAU0


DFS3711A NONRECOVERABLE DEDBAUTHORIZATION ERRORDEDB=dddddddd AREA=aaaaaaaa

ExplanationDEDB authorization determined that a unrecoverableDEDB contains a sequential dependent (SDEP)segment type.


The database that experienced the error.aaaaaaaa

The area that experienced the error.

System actionAuthorization fails.

Programmer responseChange the DEDB database definition (DBD) to removethe Sequential Dependent (SDEP) segment type.

Module:DBFDBAU0

DFS3711W NONRECOVERABLE DEDBINTEGRITY WARNINGDEDB=dddddddd AREA=aaaaaaaa

or

NONRECOVERABLE DEDB INTEGRITY WARNINGzzzzzzzzzzz

ExplanationEmergency Restart or XRF Takeover determined thatone or more DASD writes failed to complete for areaaaaaaaaa. The area might be corrupted.


The database that experienced the error.aaaaaaaa

The area that experienced the error.zzzzzzzzzzz

The warning text. This text can be:REGISTRATION INCLUDED SDEPS

One or more of the DEDBs that usesequential dependent segments (SDEP) hasbeen registered as unrecoverable, and the


SDEP segments in the current control interval(CI) might be corrupted.

System actionThe errors are ignored and ERE or XRF takeoverprocessing continues.

Programmer responseSchedule the area or database to either be reinitializedor restored from a backup. Continued use might resultin errors (for example, abend 1026).

Module:DBFERS20

DFS3712A (ccccffss) AREA=areanameDD=ddname READ ERROR, CI-RBA=nnnnnnnn SEVERE ERROR

ExplanationA read error occurred in the data set at controlinterval (CI) RBA nnnnnnnn. ccccffss represents theMedia Manager error return code used for problemdetermination.

System actionIMS closes the data set and stops the area if thedata set is the only one available in this area. Ifa permanent I/O error (indicated by Media Managererror return code X'0020FF10') has not occurred, anMVS SDUMP can be taken to the SYS1.DUMP data setby the Media Manager FRR routine or the Fast Path I/Oerror routine.

Programmer responseRun the DEDB Create utility for this data set, or run theDatabase Recovery utility for this area, if the area is inrecovery-needed status.

Problem determination1, 6, 11, 20 Problem determination is effective whenthe error return code is not X'0020FF10'.


DFS3713A (ccccffss) AREA=areanameDD=ddname WRITE ERROR, CI-RBA=nnnnnnnn SEVERE ERROR

ExplanationA write error occurred in the data set at control interval(CI) RBA nnnnnnnn. The number of deactivatedrecords reached the system-defined data set errorthreshold, or a DEDB control CI (second CI) writeerror occurred. The variable ccccffss represents theMedia Manager error return code used for problemdetermination.

System actionIMS closes the data set. IMS stops the area if thedata set is the only one available in this area. Ifa permanent I/O error (indicated by Media Managererror return code X'0020FF10') has not occurred, anMVS SDUMP can be created to the SYS1.DUMP dataset by the Media Manager FRR routine or the Fast PathI/O error routine.

Programmer responseRun the DEDB Create utility for this data set, or run theDatabase Recovery utility for this area, if the area is inrecovery needed status.

Problem determination1, 6, 11, 20 Problem determination is effectivewhen the Media Manager error return code is notX'0020FF10'.


DFS3714I RECORD DEACTIVATIONINITIATED BY SUBSYSTEM=ssidFOR AREA=areaname DD=ddnameCI-RBA=nnnnnnnn

ExplanationThe deactivation of records by subsystem ssid wascompleted for control interval (CI) RBA nnnnnnnn(hexadecimal). The value of nn in the error queueelement (EQE) indicates the number of acceptabledeactivated records. ssid is the subsystem ID of theoriginating subsystem.


DFS3715I DEDB AREA xxxxxxxx PROCESSSTARTED, RSN=rr


ExplanationDEDB area open startup processing started formultiple areas, based on the values for the FPOPN andFPRLM startup parameters. The process xxxxxxxx canbe:

• PREOPEN• REOPEN• RESTART• CLOSE• RLM REVR

The processing had the following result:Code (hex)

Meaning00

Startup successful.01

Startup terminated due to shutdown close startup.02

Startup terminated due to IRLM disconnectstartup.

03Startup failed due to out of storage condition.

Note: In rare cases, this message can be issued uponan IMS cold start if the FULLSEG option is specified fora DEDB via DBRC.

System actionArea open startup processing completes.

DFS3717I DEDB AREA CONTROLBLOCK NOTIFY FAILURE -AREA STOPPED. DBD=dbdnameAREA=areaname

ExplanationIMS encountered a problem with IRLM whenmodifying the area status for the named area andattempting to notify other subsystems to synchronizethe area status.

System actionThe indicated DEDB area is stopped globally and setsthe prohibit further authorization status in the DBRCRECON data sets.

Programmer responseCheck the status of IRLM. If IRLM is active, restart thearea using the /START AREA GLOBAL command. If

IRLM is not active, restart the area using the /STARTAREA GLOBAL command after emergency restart.

DFS3718I WAITING FOR AREA READ I/ODURING DISCONNECT

ExplanationDuring an area disconnect, there was an outstandingREAD I/O that did not complete. IMS waits a maximumof two minutes before continuing with the disconnect.

Only one message per area is issued to the console forthe disconnect, although a check is performed at one-second intervals to see if the disconnect can continuefor the outstanding READ I/O against the area.

System actionSystem action continues.


DFS3719I DEDB AREA xxxxxxxx PROCESSCOMPLETED, RSN=rr

ExplanationDEDB area open startup processing completed. Theprocess xxxxxxxx can be:

• PREOPEN• REOPEN• RESTART• CLOSE• RLM REVR

The processing had the following result:Code (hex)

Meaning00

The process completed successfully.01

The process terminated before completionbecause of a /CHE FREEZE command toterminate the IMS subsystem.

02The process terminated before completionbecause of an IRLM disconnect.

03The process did not run because of an inability toobtain sufficient storage.


Note: In rare cases, this message can be issued uponan IMS cold start if the FULLSEG option is specified fora DEDB via DBRC.

System actionArea open startup processing completes.

DFS3720I NOTIFIED AREA|ADS=areaname|adsname NOT FOUND IN THISSUBSYSTEM

ExplanationThe named area or ADS was not found in the receivingsubsystem.


DFS3721I STOP ADS REJECTED DUETO ONLY 1 AVAIL ADS.AREA=xxxxxxxx DD=xxxxxxxx

ExplanationThe /STOP ADS command was invalid for the namedADS in the area because the named ADS is the onlyavailable ADS in the area.

System actionThe /STOP ADS command is ignored for the namedADS.


DFS3722I IMS=iiiiiiii SSID=ssssSSTYPE=tttttttt ACTION=yyyyyyyRECOVERYTOKEN='aaaaaaaaxxxxxxxxxxxxxxxx'

ExplanationThe FDBR In Doubt Notification user exit routinereceived an in doubt unit of recovery (UOR). Thismessage indicates the IMS system where the workoriginated, the name of the external subsystem wherethe UOR needs to be resolved, the type of externalsubsystem (such as DB2, MQ, or WOLA), the requiredresolution action (either COMMIT or ABORT), and therecovery token for the UOR.


iiiiiiiiThe 8-character IMS system name.

ssssThe 8-character external subsystem name.

ttttttttThe 8-character external subsystem type.

yyyyyyyyThe in-doubt action that the exit routine musttake to resolve the UOR: COMMIT, ABORT, orUNKNOWN.

aaaaaaaaxxxxxxxxxxxxxxxxThe 16-byte recovery token for the UOR inprintable format. The token is enclosed with singlequotation marks because it might contain blanks.In the recovery token:aaaaaaaa

8-byte character section of the recovery token.The character data is left-aligned and paddedwith blanks.

xxxxxxxxxxxxxxxx8-byte hexadecimal section of the recoverytoken.



DFS3723E DFSFIDN0 GETSTORE FAILURE

Explanation:A GETSTORE request from the ESAF indoubtnotification user exit routine (DFSFIDN0) failed toacquire storage.

System action:The exit routine reports the failure and returns controlto IMS.

Operator response:The exit routine requires a small amount of storage,which indicates that the storage pool is close toexhaustion. Examine the system console log and anyrelevant dumps produced around the time of the errorto determine what is consuming storage.

DFS3724I ERROR OCCURRED WHENPROCESSING DBRC RECONvariable text

ExplanationThe DEDB Initialization utility (DBFUMIN0) was unableto successfully complete the DBRC call.

In the message text, variable text refers to one ofthe following targets, depending on whether the IMSmanagement of ACBs is enabled:


ERROR OCCURRED WHEN PROCESSING DBRCRECON AREA=areaname FUNC=function RC=nn

This form of message text is the default.ERROR PROCESSING DBRC RECON ALLOCATINGIMS DIRECTORY RC=nn


The meanings of the functions are:Function

MeaningSIGNON

Sign-on callSIGNOFF

Sign-off callAUTH

Area authorization callUNAUTH

Area unauthorization callINIT

INIT function callINIT0

INIT0 function callINIT1

INIT1 function callEOD

EOD function callEOJ

EOJ function call

A previous DBRC message might be issued to furtherexplain the DFS3724I message.


Programmer responseCheck the DBRC message (if issued) that preceded thismessage and follow the programmer response in thatmessage.

Related referenceReturn codes from Sign-on Normal call(Messages and Codes)Return codes from Sign-off Normal call(Messages and Codes)Return codes from Authorization calls(Messages and Codes)Return codes from Unauthorization call(Messages and Codes)IMS Catalog Definition exit routine (DFS3CDX0)(Exit Routines)

DFS3725I AREA=areaname JCL DDSTATEMENT DOES NOT EXIST

ExplanationThe DEDB Area Initialization utility, DBFUMIN0, wasunable to find a JCL DD statement corresponding tothe ddnames in the ADS list of the DBRC RECON dataset.


Programmer responseEnsure that all DD statements for the DEDB areas(or multiple area data sets) are correct. If you areinitializing the multiple area data sets of an area, thearea must be registered in the DBRC RECON data setand these area data sets must be in an unavailablestatus in the RECON data set. The use of DBRC musteither default to YES, or be specified as DBRC=Y in theEXEC parameter for DBFUMIN0.



DFS3726A FPE AREA IMAGE COPYTERMINATED ABNORMALLYFOR AREA=areaname REASONCODE=nn

ExplanationDatabase Image Copy utility processing failed for thenamed area. The following nn values indicate thereason for the failure.Code (dec)

Meaning00

Loading of the area authorization module,DBFDBAU0, from the IMS SDFSRESL to the mainstorage failed.

04The DBRC interface failed.

08The area authorization failed.

12No DATAIN DD statement was specified in the JCL.The ddname specified in the DATAIN DD statement


http://www.ibm.com/support/knowledgecenter/SSEPH2_15.1.0/com.ibm.ims15.doc.msgs/compcodes/ims_signonretcodes.htm#ims_signonretcodes


http://www.ibm.com/support/knowledgecenter/SSEPH2_15.1.0/com.ibm.ims15.doc.msgs/compcodes/ims_signoffretcodes.htm#ims_signoffretcodes

http://www.ibm.com/support/knowledgecenter/SSEPH2_15.1.0/com.ibm.ims15.doc.msgs/compcodes/ims_signoffretcodes.htm#ims_signoffretcodes

http://www.ibm.com/support/knowledgecenter/SSEPH2_15.1.0/com.ibm.ims15.doc.msgs/compcodes/ims_authorizationretcodes.htm#ims_authorizationretcodes

http://www.ibm.com/support/knowledgecenter/SSEPH2_15.1.0/com.ibm.ims15.doc.msgs/compcodes/ims_authorizationretcodes.htm#ims_authorizationretcodes





of the Database Image Copy utility must match thenames registered in the ADS list of the target area.

16The consistency check for the input data setsfailed. This check compares the CUSN of thesecond control interval for each data set entered.

20No input ADS is available and the DatabaseImage Copy utility cannot take a backup copyfrom any of the data sets in the area. Beforethis message, messages DFS3727I, DFS3728I,DFS3729I, DFS3730I, or DFS3762I might beissued.

24The IC utility either cannot find a clean ADS (noEQE) for the area, or the only ADS specified asinput has EQE.

28The area status changed to a recovery-neededstatus in the DBRC RECON data set during theimage copy operation. This problem can occurduring an XRF takeover, when recovery-neededstatus is temporary. The status is reset to indicaterecovery not needed, once takeover is complete.

This situation can also occur if IMS losesconnectivity with the coupling facility, causingCASTOUT to fail. The write error, EEQE with anull EQERBA, is registered to DBRC and the areais marked as temporary recovery-needed. AfterCASTOUT is successful, the status is reset toindicate that recovery is not needed.

32An invalid data set name is specified in the DATAINDD statement. The data set name specified in theDATAIN DD statement of the Database Image Copyutility must match the names registered in the ADSlist of the target area.

36No available ADS was found in the ADS listof the DBRC RECON data set. When ADSs areunavailable, the area cannot be specified as inputto the Database Image Copy utility.

40Only one ADS is specified as input when the MADSI/O timing environment (MADSIOT) is enabled.

System actionThe program terminates.

Programmer responseTake the appropriate action based on the code youreceived.

Code (Dec)Action

00Check if DBFDBAU0 exists in the SDFSRESL.

04See the DBRC message related to this message.

08Check the message for the area authorizationrelated to this message.

12Specify the correct ddname in the DATAIN DDstatement, and resubmit the job.

16Check to see if all the input data sets are at thesame level, specify the correct data sets in theDATAIN DD statement, and resubmit the job.

20Check messages DFS3727I, DFS3728I, DFS3729I,DFS3730I, or DFS3762I and correct the error.Then resubmit the job.

24Recover the area and create a data set which doesnot have any EQE, and resubmit the job.

28List the RECON to determine if the area is inrecovery-need status; if so, recover the area andcreate a data set which does not have any EQE.Resubmit the job.

32Specify the correct dsname in the DATAIN DDstatements, and resubmit the job.

36Specify the correct area name or recover the AREA,and resubmit the job.

40Resubmit the job with at least two ADSs specifiedas input.

Module:DBFUMDP0

DFS3727I (OPEN ERROR | RECORD SIZEERROR) FOR AREA=areanameDD=ddname

ExplanationThe Database Image Copy utility failed to open a dataset or found a record size inconsistent with the controlinterval (CI) size for the named DEDB area and ADS.This ADS cannot be used any longer.


System actionThe Database Image Copy utility tries to open the nextdata set.

DFS3728I VSAM ERROR REQUEST=(GET|VERIFY|POINT) FORAREA=areaname DD=ddname

ExplanationThe VSAM request failed for the named area and ADSbut did not fail when the EQEON request was made.EQEON indicates that a Database Image Copy utility,finding an error queue element (EQE), avoids readingthe control interval from ADS. ADS is still used as theinput DEDB to a Database Image Copy utility.

System actionThe Database Image Copy utility attempts to get thenext available data set.

DFS3729I (RDJFCB|MODCB) ERROR FORAREA=areaname DD=ddname

ExplanationThe Database Image Copy utility issued an RDJFCBor MODCB OS macro to the named ADS and failed.The named ADS is not used for the input DEDB to theDatabase Image Copy utility.


DFS3730I SECOND CI (READ|POINT) ERRORFOR AREA=areaname DD=ddname

ExplanationThe Database Image Copy utility tried to read or pointto the DEDB second control interval (second CI) andfailed. The ADS of the ddname is not used as inputDEDB to the Database Image Copy utility.


DFS3731I REORGANIZATION (BUILD|COPY)PHASE ENTERED FORAREA=areaname UOW=nnnnnnnn

ExplanationThe Reorganization utility entered into the build orcopy phase.



DFS3732I DUPLICATE DDNAME STATEMENTSPECIFIED

ExplanationThe program encountered a DDNAME statement thatwas previously specified.

System actionThe DEDB utility program stops scanning the currentinput line. Further processing, such as scanningthe next input line, is done according to the userspecification in the ERRORACTION statement.

Programmer responseCorrect the DEDB utility input and rerun the job.

DFS3733A FPE AREA OFFLINE RECOVERYTERMINATED ABNORMALLY FORAREA=areaname (DD=ddname)REASON CODE=nn

ExplanationThe offline database recovery for a DEDB failed. Thefollowing nn values indicate the reason for the failure:Code (dec)

Meaning00

The area authorization module, DBFDBAU0, wasnot found in the IMS resident library.

04A DBRC call and FUNC=INIT failed.

08The area authorization failed.

12No data set1 DD statement specified in the JCL.If DBRC is used and the Area is registered, theddname specified in data set1 DD statement mustmatch the names registered in the ADS list of thetarget Area.


If DBRC is used, but the Area is not registered, or ifDBRC is not used, the ddname specified in the dataset1 DD statement must match the areaname.

16The area status conflicted with the requestedrecovery mode. The area status does not matchthe requested recovery mode. For DEDB recovery,the area must be in one of the following status:

• If in full recovery, the area must be in therecovery-needed status.

• If in track recovery, the area must be in therecovery-not-needed status and the data setmust be available.

20Unable to open the ACB for the target data set.

24Unable to read the second control interval for thetarget data set.

28DBRC was not initialized for this region and wasunable to authorize the area. If the system doesnot have DBRC, this message is issued.

36Unable to get the control interval size for the targetdata set. For DEDB track recovery, SHOWCB isissued to get the length of the CI for a later readingof the second CI, but it failed.

40Unable to change the VSAM control block (RPL).For DEDB track recovery, MODCB Is issued to setthe relative byte address of the second controlinterval for reading, but it failed.

44An invalid data set name was issued. For aDEDB, the dsname specified in the data set1 DDstatement of the Database Recovery utility mustmatch the names registered in the ADS list of thetarget area.

48The RDJFCB macro failed. Check the IEC131Imessage.

52No ADS record is found in the DBRC RECON dataset.

System actionThe program terminates. For reason code 32, thesystem sets the data set unavailable status in the ADSlist of the DBRC area record. The area status is set tothe recovery-needed status if the data set is the lastone in the area.

Programmer responseRespond based on the return code nn as follows:Code (dec)

Meaning00

Check if DBFDBAU0 exists in SDFSRESL.04

See the DBRC message related to this messageand check it.

08Check the message related to the areaauthorization.

12First check to see if DBRC is used or not. (Thiscan be done by checking the DBRC positionalparameter in the EXEC parameter or the IMSCTRLDBRC parameter in the IMS system definitionmacro.)

If DBRC is used and the Area is registered, specifyone of the ddnames of the ADS list in the dataset1 DD statement. If DBRC is used, but the Areais not registered, or if DBRC is not used, specifythe areaname in the data set1 DD statement thenresubmit the job.

16Specify the correct recovery mode according to thearea status in DBRC RECON data set and resubmitthe job.

20Check the other message related to this message.

24Check other messages related to this message.

28Check if the system has DBRC.

32Recover the data set and the area if the area is inrecovery-needed status.

36Rerun the job.

40Rerun the job.

44Specify the correct dsname in the data set1 DDstatement and resubmit the job.

48Follow the operator response described in theIEC131I message.

52Print the DBRC RECON data set and check theADS list of the named area. If there is notany ddname in the ADS list, register at least


one ddname in the DBRC RECON data set usingan INIT.ADS command. After the registration,recover the named area by a Database Recoveryutility and rerun the job.

Related referencez/OS: IEC131I

DFS3734I AUTOMATIC SDEP BUFFERMANAGEMENT HAS BEGUN ONims_id

Explanation:Automatic SDEP buffer management startedprocessing areas for this IMS.



Module:DBFAQC00

DFS3735I AUTOMATIC SDEP BUFFERMANAGEMENT HAS COMPLETEDWITH RETURN CODE xx sysid

ExplanationAutomatic SDEP buffer management completedprocessing the areas for this IMS. The return code isfor diagnostic purposes.Code (dec)

Meaning00

Successful execution.04

No areas.08

Unable to get storage.12

Area list changed.

System action:These are all terminating errors for that instance ofautomatic SDEP buffer management execution. Theautomatic SDEP buffer management will be triggeredat the next execution.


Module:DBFAQC00

DFS3736A VALIDATION CALL FAILED FORAREA=areaname DD=ddnameCode=xx

ExplanationIMS Fast Path attempted to validate the status of theddname specified in the DDNAME control statementsand discovered an error condition. In the messagetext, the code xx can have one of the following values:Code

MeaningIA

The status of ADS in the DDNAME statementconflicts with the one in the ADS list in the DBRCRECON data set. If the DEDB Create utility isrequested, the status of the ADS is available inthe RECON data set. If the DEDB Compare utility isrequested, the status of the ADS is unavailable inthe RECON data set.

IBThe ddname is not found in the RECON data set.

System actionThe utility is not activated for the requested area.

Programmer responseSpecify the correct ddname in the DDNAME statement,and resubmit the job.

DFS3737A DMAC SYNCHRONIZATION FAILEDFOR AREA=areaname

ExplanationIn the environment of sharing an area amongsubsystems at the block level, DMAC, which containsthe area information, must be identical among thesubsystems. Because of some error in the lock failure,second control interval write failure, notify failure, andso on, DMAC synchronization cannot be maintained onthe area.

System actionThe Fast Path utility being used terminates and thearea is marked as stopped.

Programmer responseAfter the area is restarted, resubmit the job.

DFS3738A TOO MANY DDNAME STATEMENTSSPECIFIED



ExplanationThe program encountered too many ddnamestatements. The count of the ddname statementsmust be less than or equal to 6 for the DEDB Createutility and less than or equal to 7 for the Compareutility.

System actionThe DEDB utility program stops scanning the currentinput line and further processing is specified by theuser in the ERRORACTION command.

Programmer responseCorrect the input, and rerun the DEDB utility.

DFS3739A I/O ERROR OCCURRED WHENATTEMPTING TO READ FROMAREA=areaname

ExplanationThe utility, DBFUMRI0, attempted to read from one ofthe opened data sets of the area, and encountered anI/O error.

System actionThe DEDB Create utility, DBFUMRI0, terminates.

Programmer responseRecover the defected control interval using the offlineDatabase Recovery utility, DFSURDB0, and rerun thejob.

DFS3740I IN AREA=areaname, CI'S WITHMATCHED CONTENT=mmm, CI'Swith UNMATCHED CONTENT=nnn

ExplanationThe utility compared all records in the area and foundthat mmm control intervals (CI) had identical contents,and nnn control intervals had different contents.


Programmer responseIf any CI has a different content, check the memorydump record listing on the SYSPRINT data set.

DFS3741I EITHER ADS IN ERROR.COMPARE IMPOSSIBLE FOR

AREA=areaname DD1=ddname1DD2=ddname2

ExplanationA read error occurred on either the ddname1 orddname2 area data sets and comparison of the controlinterval content is impossible. Message DFS3739A isissued before this message and specifies on whichADS the read error occurred.



Related information“DFS3739A” on page 1075I/O ERROR OCCURRED WHEN ATTEMPTING TOREAD FROM AREA=areaname

DFS3742A INTERNAL COMMAND TO STOP ANADS FAILED FOR AREA=areanameDD=ddname

ExplanationAn internal command to stop an area data set (ADS)failed because of a system error (area lock failureor notify failure), and ADS cannot be stopped. Thecommand is issued after an I/O error occurred on thenamed area and ADS during the copy phase of theDEDB Create utility, DBFUMRI0. The ADS is not usable.

System actionThis utility terminates.

Programmer responseEnter a /STOP ADS command to stop this ADSglobally, and rerun the job. This error can occur dueto a lock or notify failure.

DFS3743A SETTING AN ADS TOAVAILABLE STATUS FAILED FORAREA=areaname DD=ddname

ExplanationIn the available phase, the DEDB Create utility,DBFUMRI0, set the named area data set (ADS) to anavailable-failed status since the ADS is stopped ordeleted from the ADS list in the DBRC RECON data set.



Programmer responseCheck if ADS is correctly stopped or deleted from theDBRC RECON data set. Add the entry for the namedADS to the DBRC RECON data set if the ADS entry isdeleted, and rerun the job.

DFS3744A FORMATTING OF ALL NEW ADS(S)FAILED FOR AREA=areanameREASON CODE=nn

ExplanationThe Create utility, DBFUMRI0, in its format phase,failed to format all of the area data sets (ADS) of thenamed area because of error code nn. The reason codenn can be one of the following values:Code (dec)

Meaning01

Area lock failed.02

The DBRC interface failed. Reading the ADS listfrom the RECON data set or writing the ADS listonto the RECON data set failed.

04The formatting of all new ADSs failed.

05An internal command to stop an ADS failedbecause of a system error (area lock or notifyfailure).

06The VSAM control block (RPL) manipulation andMODCB RPL failed.

07The data set verification failed and this message isissued when:

1. Defined control interval (CI) size is inconsistentwith the DBD parameter.

2. Insufficient space is defined for the new ADS.

08The dynamic allocation or opening of the new ADSfor formatting failed. You can also receive this errorwhen the VSAM cluster was not defined.

09The storage GETMAIN for the VSAM control block(RPL) work area failed.

0AThe AREA has EEQE.


Programmer responseEnsure that all newly issued ADSs are stopped amongall the subsystems. If they are not stopped, enter the /STOP ADS command to stop the area data set globally.When this action is done, take the following action:Code (dec)

Meaning01

Rerun the job.02

Ensure that the area record exists in the DBRCRECON data set and rerun the job.

03Remove EQE from the current active ADSs usingthe offline Database Recovery utility, DFSURDB0.When this action is done, rerun the job.

04Define another VSAM data set for any new ADS,and rerun the job.

05Rerun the job.

06Rerun the job.

07Define another VSAM data set with the correctcontrol interval size and space and rerun the job.

08The application program terminates when thedependent region abends. After preparing thetracing facilities for lock, rerun the job. Onepossible cause is that the VSAM cluster was notdefined.

09Rerun the job.

0ARemove EQE from the current active ADS using theoffline database recovery utility, DFSURDB0. Thenrerun the job.

DFS3745I CREATE FAILED BECAUSE REGIONSTOP FOR AREA=areaname

ExplanationThe /STOP REGION command was entered and theutility region was stopped.




DFS3746A FORMATTING OF AN ADS FAILEDFOR AREA=areaname DD=ddnameREASON CODE=nn

ExplanationIn the format phase in Create utility, DBFUMRI0, theformatting of a new area data set (ADS) failed. One ofthe following reason codes nn indicates the cause forthe failure:Code (dec)

Meaning01

The dynamic allocation or opening of the new ADSfor formatting failed.

02I/O error or long busy error occurred during theformatting of a new ADS.

03To format a new ADS, the ADS must be registeredin the DBRC RECON data set first. In this case, theADS was not registered in the DBRC RECON dataset.

04The control interval (CI) size of the new VSAM dataset is not the same as the one specified in DBD.

05The defined VSAM data set space is smaller thanthe current active ADS VSAM data set. The newADS VSAM data set must be equal to or larger thanthe current active ADS.

06After formatting the new VSAM data set, the utility,DBFUMRI0, closes the data set to reopen thedata set with the ICIP option, but a close erroroccurred.

07After closing the new VSAM data set, the utility,DBFUMRI0, opened the data set with the ICIPoption, but an open error occurred.

08The ADS of the named ddname was stopped by theoperator and formatting of the ADS failed.

System actionThe utility stops formatting the ADS of the namedddname.

Programmer responseCheck the RECON data set if the named ADS isstopped or inadvertently deleted from the RECON dataset. If it is not stopped, add the ADS entry to the DBRCRECON data set, and rerun the job.

DFS3747A OPEN PROCESS IN COPY PHASEFAILED FOR AREA=areanameREASON CODE=nn

ExplanationThe Create utility, DBFUMRI0, in its copy phase, failedto open all of the area data sets (ADS) among all ofthe subsystems sharing the area at the block level,because of the reason code nn.Code (dec)

Meaning01

The area lock failed.02

Notifying other subsystems to open an ADS failed.03

Stopping an ADS failed due to system failure.04

Opening of all ADSs among all the subsystemsfailed.

System actionThis Fast Path utility being used terminates.

Programmer responseEnsure that all new ADSs to be created are stoppedamong all the subsystems sharing the area in blocklevel. If not, enter the /STOP ADS command to stopall new ADSs globally. When this action is done, takethe following action.Code (dec)

Meaning01

Rerun the job.02

Rerun the job.03

Rerun the job.04

Check the reason for the failure of the ADS to openand correct the error. When this action is done,rerun the job.


DFS3748A OPENING AN ADS AMONGOTHER SUBSYSTEMS FAILED FORAREA=areaname DD=ddname

ExplanationAt the beginning of the copy phase in the DEDBCreate utility, DBFUMRI0, the utility requested othersubsystems sharing the area in block level to open thearea data set (ADS) of the named ddname, but the ADSfailed to open in some of the subsystems.

System actionThe DEDB Create utility terminates the operation onthis ADS and continues to create new ADSs.

Programmer responseCheck the reason why the ADS opened unsuccessfully,correct the error, and rerun the job.

DFS3749I CREATE (FAILED|COMPLETED)FOR AREA=areaname DD=ddname

ExplanationThe create operation for the area data set (ADS) withareaname and ddname failed or completed.

System actionNone.


DFS3750A I/O ERROR OR LONG BUSYOCCURRED WHEN ATTEMPTINGTO WRITE TO AREA=areanameDD=ddname

ExplanationThe DEDB Create utility, DBFUMRI0, attempted towrite onto the target data set ddname and areaname,and encountered an I/O error.

System actionThe DEDB Create utility terminates the createoperation on this ADS, and continues to create newADSs.



Chapter 79. DFS messages, DFS3751A - DFS3800


DFS3751A CREATE FAILED INAVAILABLE PHASE FAILEDFOR AREA=areaname REASONCODE=nn

ExplanationThe DEDB Create utility, DBFUMRI0, in its availablephase, in attempting to set all area data sets (ADS) toan available status, failed because of reason code nn.Code (dec)

Meaning01

The area lock failed.02

The notification to other subsystems to set ADSs toan available status failed.

03The DBRC interface failed. Reading the ADS listfrom the RECON data set or writing the ADS listonto the RECON data set failed.

04All ADSs were not found in the ADSC chain or theADS list in the RECON data set.

05ADSC chain is invalid because of a system failure.

06A /STOP ADS command failed because of asystem failure.

System actionThis DEDB Create utility terminates. All the new ADSsare still unavailable and cannot be used.

Programmer responseEnsure that all new ADSs to be created are stoppedamong all of the other subsystems. If they are not,enter the /STOP ADS command to stop the new ADSglobally. When this action is done, take the followingaction:Code (dec)

Meaning01

Rerun the job.02

Rerun the job.

03Ensure that the area record exists in the RECONdata set, and rerun the job.

04Ensure that new ADSs to be created are registeredin the RECON data set, and rerun the job.

05Rerun the job.

06Rerun the job.

DFS3752A CREATE FAILED IN COPY PHASEFOR AREA=areaname

ExplanationAn I/O error occurred on the last new-active area dataset (ADS), and no new ADS are to be created.


Programmer responseDo the following steps:

1. Ensure that all new ADSs to be created are stoppedamong all the other subsystems. If the ADSs arenot stopped, then enter the /STOP ADS commandto stop the new ADSs globally.

2. Define the new VSAM data set.3. Rerun the job.

DFS3753I COMPARE NOT PERFORMEDBECAUSE I/O ERROR ORLONG BUSY OCCURRED FORAREA=areaname DD=ddnameRBA=nnnnnnnn

ExplanationThe DEDB AREA Data Set Compare utility tried to reada control interval (CI) from all of the requested ADSsto compare each CI. The Compare utility excluded theindicated control interval from the compare operation,because an I/O error occurred on the CI in the ADS ofthe ddname.



DFS3754A UTILITY=utility-nameTERMINATED BECAUSEAREA=areaname STOPPED

or

UTILITY=utility-name SKIPPED PROCESSING FORAREA=areaname BECAUSE AREA IS STOPPED |QUIESCED

ExplanationIn the first form of this message, the named FastPath utility being used terminated because the namedarea stopped. In the second form, utility-name skippedprocessing the area because the area is stopped.

If the area is quiesced, the second form ofthis message is issued and the utility-name skipsprocessing the area.

System actionIn the first form of this message, the Fast Path utilitybeing used terminates. In the second form, the FastPath utility continues with the next area in the inputstream.

Operator responseRestart the area using a /START AREA or UPDATEAREA START(ACCESS) command, and rerun thenamed utility.

If the area is quiesced, stop the quiesce by issuing aUPDATE AREA STOP(QUIESCE) command, and rerunthe named utility.

DFS3755E AN ERROR OCCURRED DURINGA STOW OPERATION ON THEDIRECTORY DATA SET FORRESOURCE rsc_name RC=xxRSN=yy.

ExplanationAn error occurred while the system attempted a z/OSSTOW operation.


System programmer responseSee the STOW Completion Codes in z/OS DFSMSMacro Instructions for Data Sets for a detailedexplanation of return codes and reason codes.

Run the catalog utility to rebuild the IMS directorydata sets or otherwise restore the IMS directory. Afterthe IMS directory is restored, resubmit the IMPORTcommand or the DDL definition statements.

Module:DFSMOLS0

Related referencez/OS: Return and reason codes for the DFSMSSTOW macroRelated informationIMS directory data sets (System Definition)

DFS3756A COMPARE UTILITY TERMINATEDBECAUSE COMPARABLE ADSCOUNT IS LESS THAN 2

ExplanationDuring the compare processing, the DEDB Compareutility terminated because the comparable area dataset (ADS) count was less than 2. This might havebeen caused by a /STOP ADS command or an internalcommand issued to stop an ADS. The ADS to becompared was stopped.

System actionThe DEDB Compare utility terminates.

DFS3757I NO DATA SET REGISTERED INDBRC RECON ADS LIST FORAREA=areaname

ExplanationThe IMS DEDB Initialization utility (DBFUMIN0) foundthat no area data set (ADS) is registered correspondingto the area in the ADS list of the DBRC AREA record.


Programmer responseRegister the ADSs in the DBRC RECON record by usingthe DBRC INIT.ADS command, and then rerun theutility.



http://www.ibm.com/support/knowledgecenter/SSLTBW_2.3.0/com.ibm.zos.v2r3.idad500/d5167.htm




DFS3758I DD=ddname DATA SET NAMEMISMATCH IN DBRC RECON ADSLIST AND IN JCL DD STATEMENTFOR AREA=areaname DD=ddname

ExplanationThe IMS DEDB Initialization utility (DBFUMIN0) foundthat the data set name in the DBRC RECON ADS listdoes not match the one in the JCL DD statement.


Programmer responseEnsure that the data set names in the DBRC RECONrecord and in the JCL DD statement are correct, andthen rerun the job.

DFS3759I COMPARE NOT PERFORMEDBECAUSE ADS IS STOPPEDFOR AREA=areaname DD=ddnameRBA=nnnnnnnn

ExplanationThe DEDB Compare utility tried to read a controlinterval (CI) from all of the requested area datasets (ADS) to compare each CI. Because the ADSof the named ddname is stopped by a /STOP ADScommand or an internal command, the utility excludedthe indicated CI from the compare operation. Theremaining CIs for this ADS are read nor compared.


DFS3760A AREA=areaname NOTREGISTERED IN DBRC RECONDATA SET

ExplanationFor the DEDB Create utility, DBFUMRI0, or DEDBcompare utility, DBFUMMH0, the area name must beregistered in the DBRC RECON data set.


Programmer responseRegister the named area and its ADSs in the DBRCRECON data set, and rerun the job.

DFS3761I OPEN/CLOSE RECOVERY FAILEDFOR AREA=areaname, (READ|WRITE) ERROR, RBA=nnnnnnnn

ExplanationA read or write error occurred in the named area at theindicated CI number during the open/close recoveryprocessing. Messages DFS2571I or DFS2572I mightbe issued before this message.

System actionOpen or close recovery processing terminates. Thenamed area is stopped and set to a recovery-neededstatus in the DBRC RECON data set.

Operator responseRun the Database Recovery utility to recover thenamed area. Then rerun the job.

DFS3762I CI-RBA=nnnnnnnn ERRORFEEDBACK=xxxxxxxx INRESPONSE TO A VSAM(GET|POINT) REQUEST ONAREA=areaname DD=ddname

ExplanationAn error occurred when the Database Image Copyutility attempted to read from or point to a DEDBarea. The VSAM GET or POINT macro encountered aproblem.

System actionThe Database Image Copy utility tries to read from orpoint to a DEDB area in the next available data set.


Related referencez/OS: GET--Retrieve a record (VSAM macro)z/OS: POINT--Position for access (VSAM macro)z/OS: VSAM macro return and reason codes

DFS3763I DEDB AREA DATA SET CONTROLBLOCK NOTIFY FAILURE -AREA STOPPED. DBD=dbdnameAREA=areaname DD=ddname

Chapter 79. DFS messages, DFS3751A - DFS3800 1081

http://www-01.ibm.com/support/knowledgecenter/SSLTBW_2.4.0/com.ibm.zos.v2r4.idad500/x4yyyy.htm?lang=en

http://www-01.ibm.com/support/knowledgecenter/SSLTBW_2.4.0/com.ibm.zos.v2r4.idad500/x5vv.htm?lang=en


ExplanationIMS encountered a problem with IRLM whenmodifying the status of the area data set for thenamed area data set and attempting to notify theother subsystems to synchronize the status duringemergency restart. The status change had beenrequested in the failing system.

System actionThe indicated DEDB area is stopped, and theemergency restart continues.

Programmer responseRestart the area using the /START AREA GLOBALcommand after emergency restart.



DFS3764I DEDB AREA DATA SETSTOP SYNCHRONIZATION NOTAVAILABLE - AREA STOPPED.DBD=dbname AREA=areanameDD=ddname

ExplanationIMS attempted to stop the area data set duringemergency restart. This situation can occur if an I/Oerror existed for the named area data set duringemergency restart or if an external or internal stoparea data set (ADS) was processing when the systemfailed. If an external or internal stop ADS wasprocessing, the stop ADS was not available during theemergency restart. Therefore, IMS forced the area tostop.


Programmer responseRestart the area using the /START AREA GLOBALcommand after emergency restart. You must run eitherthe DEDB Area Data Set Create utility, DBFUMRI0,or the Database Recovery utility, DFSURDB0, for theindicated data set.

DFS3765I DEDB AREA CONTROLBLOCK NOTIFY FAILURE -AREA STOPPED. DBD=dbnameAREA=areaname

ExplanationDuring emergency restart IMS encountered a problemwith IRLM when modifying the area status for thenamed area and attempting to notify other subsystemsto synchronize the status. The status change had beenrequested in the failing system.


Programmer responseRestart the area using the /START AREA GLOBALcommand after the emergency restart.

DFS3766A NOTIFY REQUEST TO STOP ANADS FAILED FOR AREA=xxxxxxxxDD=yyyyyyyy

ExplanationDuring ERE processing the system tried to stopthe specified area data set (ADS) in each of thesubsystems sharing the ADS, but failed. The statusof the ADS in all subsystems remains in copy phasestatus or in format phase status.

System actionSystem continues its operation.

Operator responseThe user must stop the ADS in all subsystems sharingthis ADS by /STOP ADS command.

DFS3766W PSB pppppppp REQUIRESSTOPPED DEDB DATA BASEdddddddd, PSB STOPPED.

ExplanationBecause a required Fast Path DEDB, dddddddd, wasunavailable, scheduling ended and PSB, pppppppp,stopped.



DFS3767A NOTIFY REQUEST TO SET AN ADSTO AVAILABLE STATUS FAILEDFOR AREA=xxxxxxxx DD=yyyyyyyy

ExplanationDuring ERE processing the system tried to set thespecified area data set (ADS) to available status inall subsystems sharing the ADS, but failed. The statusof the ADS in each subsystem remains in copy phasestatus. The status of the ADS in RECON D/S is inavailable status.


Operator responseAs there is a difference in the ADS status betweeneach subsystem and the RECON D/S, the operatorshould stop the area which accesses this ADSby /STOP AREA or UPDATE AREA STOP(SCHD)command, then restart the area.

DFS3768A DBRC REQUEST TO SET AN ADSTO UNAVAILABLE STATUS FAILEDFOR AREA=xxxxxxxx DD=yyyyyyyy

ExplanationDuring ERE processing, the system tried to set thespecified area data set (ADS) to unavailable status inthe RECON data set, but failed. The status of the ADSin the RECON data set remains in copy phase status.


Operator responseThe operator must set the status of the ADS tounavailable status by a DBRC command. Make sure thestatus of the ADS is in unavailable status, both in theRECON data set and in each subsystem.

DFS3769I INVALID SYNTAX IN START ORSTOP TIME PARM

ExplanationThe program encountered an error in a start time orstop time parameter.

System actionThe DEDB utility program terminates with a returncode of 08.

Operator responseCorrect the invalid input parameter and rerun theutility.

DFS3770W SYNCHRONIZING PROCESS TIMEOUT DURING START AREAPROCESSING FOR AREA areaname

or

SYNCHRONIZING PROCESS TIME OUT DURINGSTOP AREA PROCESSING FOR AREA areaname

or

SYNCHRONIZING PROCESS TIME BETWEENSUBSYSTEMS HAS BEEN EXCEEDED

or

SYNCHRONIZING PROCESS TIME EXCEEDED -(reason) areaname

or

SYNCHRONIZING PROCESS TIME EXCEEDED -CTLBLK SYNC areaname

or

SYNCHRONIZING PROCESS TIME EXCEEDED -ALLOC/OPEN ADS areaname

or

SYNCHRONIZING PROCESS TIME EXCEEDED - UOWLOCK INIT areaname

or

SYNCHRONIZING PROCESS TIME EXCEEDED - STOPADS areaname

or


SYNCHRONIZING PROCESS TIME EXCEEDED - STOPAREA areaname

or

SYNCHRONIZING PROCESS TIME EXCEEDED -START AREA areaname

or

SYNCHRONIZING PROCESS TIME EXCEEDED -SHVSO SYNC

or

SYNCHRONIZING PROCESS TIME EXCEEDED -SHSDEPS SYNC

ExplanationSubsystem resource synchronization did not finishwithin a reasonable amount of time. This situationmight be a valid condition and might resolve itself.If IMS determines that a hang exists, IMS attemptsto resolve the wait. IMS might reject the processand issue the second form of the message, or itmight have resolved the hang (allowing the processto retry). In either instance, if the first form of themessage terminates without outside intervention, thenno action is necessary.

If the first version of the message persists, then ahang condition exists and must be resolved manually.In the message text, you might receive the followingvariables:reason

Identifies the cause of the exceeded time, and isone of the following situations:CTLBLK SYNC

IMS must synchronize internal information.ALLOC/OPEN ADS

An ADS is opening as part of an area open orADS create action.

UOW LOCK INITIMS is converting to UOW lock mode due tostarting a utility.

STOP AREAAn area is being stopped. This stop might bedue to a command or internal stop.

START AREAAn area is starting.

SHVSO SYNCSHVSO information has been internally datasynchronized.

SHSDEPS SYNCSHSDEP information has been internally datasynchronized.

areanameIdentifies the affected area.

System actionIf the first form of the message persists, then theoriginating system (the system receiving the message)is waiting for an action from a sharing partner that isnot completing. This situation indicates a hang. Theonly way to resolve the hang is based on the reasonfrom the first form of the message.

Operator responseDetermine if any subsystem participating in block levelsharing is experiencing problems. If a subsystem isin a busy state because the processor load is heavyor the processor STOP key was pressed, no action isnecessary. If a subsystem is in a wait or loop condition,that subsystem must be terminated by entering a /STOP or MVS MODIFY command; otherwise, the waitor loop condition can continue indefinitely.

Programmer responseIf this message has been issued multiple times, theother subsystem is not in a processor-busy condition,the processor STOP key was not pressed, and theother subsystem has a severe problem. ContactIBM Software Support after appropriate data hasbeen collected. Capture memory dumps of all IMSsubsystems in the sysplex.

Problem determination:1, 3, 4, 5, 6, 8, 10, 11, 14


DFS3771I AREA areaname CANNOT BEPROCESSED DUE TO 2ND CI EEQE(BUFFER)

ExplanationThe AREA areaname could not be processed for one ofthese reasons:


• The /STO AREA (LOCAL) or UPDATE AREASTOP(SCHD) command was not processed becausethe AREA has a second CI EEQE buffer.

• The /STOP AREA GLOBAL, UPDATE AREASTOP(SCHD), /STOP ADS, /DBR DB, UPDATE DBSTOP(ACCESS), or /DBR AREA command was notprocessed because the AREA has a second CI EEQE.

System actionCommand processing for the AREA terminates.

Operator responseEnter the /UNLOCK command or the OS GO replycommand to purge all EEQEs after I/O prevention isresolved. Then reenter the failed command.

DFS3772I AREA areaname STOPPED.RECOVERY NEEDED DUE TO 2NDCI EEQE BUFFER

ExplanationDuring /CHECKPT FREEZE processing the namedAREA was stopped and its status marked as recovery-needed, if the AREA was registered in DBRC. Thiscondition occurred because the AREA has a second CIEEQE buffer, which could not be written to the physicaldata set.

System actionAfter stopping the AREA, the system continuesprocessing.

Programmer responseRecover the AREA using the Database Recovery utility.

DFS3773I AREA=areanameDD=ddnameSTOP AREAGENERATED BY ADS CLOSEERROR.

ExplanationDuring the close of an ADS data set of a multiplearea data set (ADS) area that is being shared bytwo or more IMS subsystems, an I/O error occurredwhile updating the second CI of that ADS data set.This situation causes internal /STOP AREA commandsto be generated and sent to the IMS subsystemscurrently sharing the area. After stopping the area, thesystem continues processing.

System actionThe system closes the area, issues this message, andcontinues processing.

Operator responseRestart the area just closed to allow processing of thearea to resume using its remaining ADS data sets.

Module:DBFMPCL0

DFS3774A INSUFFICIENT STORAGE FORCONTROL BLOCKS

ExplanationThe GETMAIN macro failed due to a shortage inmemory for SP=0. Because of this condition, the inputstatements in the DFSHALDB data set are not read andtherefore, not validated.

System actionThe job terminates with pseudoabend 0201 and thefollowing reason code:REASON=00000028

GETMAIN failure for control block storage.

Programmer responseIncrease the size value of the REGION parameter.

Module:DBFSHSPI0


DFS3775A OPEN FAILURE OF DDNAMEDFSHALDB

or

DATASET ATTRIBUTES FOR DDNAME DFSHALDBARE NOT VALID

ExplanationA DFSHALDB data set failed to open, the RECFM is notfixed block format, or the LRECL is not equal to 80.

System actionThe job terminates abnormally with pseudoabend0201 and one of the following reason codes:



REASON=00000016Indicates RECFM

REASON=00000020Indicates LRECL

REASON=00000024Indicates DFSHALDB failed to open.

Programmer response• For a reason code of 16, make sure the RECFM is FB.• For a reason code of 20, make sure the LRECL is 80.• For a reason code of 24, use the accompanying

DFS0730I message to determine the cause of theopen failure.

Module:DFSHSPI0

Related information“DFS0730I” on page 257UNABLE TO OPEN OR CLOSE DATASET WITHDDNAME ddname FOR REASON x, yy, zDATABASE dbdname programidIMS abend 0201

DFS3776A HALDB SELECTIVE PARTITIONPROCESSING NOT ALLOWED INxxx REGION

ExplanationData set DFSHALDB, containing input statements, isnot allowed in a job for either an IFP, JMP, or MPP. Inthe message text, xxx is either an IFP, JMP, or MPP

System actionThe job terminates abnormally with pseudoabend0201 and the following reason codes:REASON=00000012

Indicates IFP, JMP, or MPP.

Programmer responseEither remove the input statements while retainingdata set DFSHALDB, or exclude data set DFSHALDBfrom the JCL.

Module:DFSHSPI0


DFS3777A HALDB STATEMENTS READ ANDVALIDATED FOR SELECTIVEPARTITION PROCESSING RC=xx

ExplanationFor message DFS3777A, the return code (xx) is one ofthe following:04

At least one statement was validated andaccepted. However, at least one other statementhad a syntax error or there were more than 20statements whose syntax was correct.

08All statements were validated and rejected due tosyntax errors.

System actionThe job terminates with pseudoabend 0201 and areason code of either 04 or 08.

Programmer responseCorrect the syntax error and resubmit the job.

Module:DFSHSPI0


DFS3777I HALDB STATEMENTS READ ANDVALIDATED FOR SELECTIVEPARTITION PROCESSING RC=xx

ExplanationFor message DFS3777I, the return code (xx) isequal to 00, meaning that all statements have beenvalidated and accepted.

System actionThe job continues processing.


Module:DFSHSPI0

DFS3778A INSUFFICIENT STORAGE TOACQUIRE HSPB CONTROL BLOCK

ExplanationThere was no storage available in SP=241 for theHSPB control block in key 7.

System actionNone.





Programmer responseRequest assistance from an operating systemprogrammer to correct the condition.

Module:DFSHSPK0

DFS3779A PCB=(yyyyyyyy,pppppppp),xxxxxxxxxxxxxx

or

PCB=(nnnn,pppppppp,NUM=yyy), xxxxxxxxxxxxxx

ExplanationFor the first form of this message, in the message text:yyyyyyyy

The NAME/LABEL.pppppppp

The partition name that was found on a statementprovided by DFSHALDB.

xxxxxxxxxxxxxxOne of the following error conditions:

• DBPCB NUMBER IN ERROR• PARTITION NAME IN ERROR• NAME/LABEL IN ERROR• PCB FOR NON-HALDB

For the second form of this message, in the messagetext:nnnn

The DBPCB numberyyy

The range, if specifiedpppppppp

The partition name that was found on a statementprovided by DFSHALDB.

xxxxxxxxxxxxxxOne of the following error conditions:

• DBPCB NUMBER IN ERROR• PARTITION NAME IN ERROR• NAME/LABEL IN ERROR• PCB FOR NON-HALDB

For a further explanation of this message, seemessage DFS3779E.

Related informationDFS3779E

HALDB SELECTIVE PARTITION PROCESSINGABEND U0202

DFS3779E HALDB SELECTIVE PARTITIONPROCESSING ABEND U0202

ExplanationIn at least one of the cards that were successfullyvalidated as "Syntactically correct," the reasons for theerror conditions are:

• There is a DBPCB number greater than the numberof DBPCBs in the list found in the PSB.

• The partition name is either misspelled or it cannotbe found in the database referenced by the DBPCBnumber or the NAME/LABEL. This condition could bethe case if a partition name in the target database issupplied when using a DBPCB which has PROCSEQ.

• The NAME or LABEL supplied cannot be found in anyDBPCB in the list found in the PSB.

• The DBPCB number or NAME/LABEL references anon-HALDB PCB.

System actionPseudoabend 0202 is issued.

Programmer responseCorrect the DBPCB number, the NAME/LABEL, thepartition name, or remove the entry that is specifying atarget partition name, and resubmit the job.

Module:DFSHSPP0


DFS3780I ACTIVE DDNAMES: modblks-nameDFSDIRC format-name MODSTATID: nnnn

ExplanationThis message indicates online change status includingthe active online change libraries and the currentmodify ID. IMS issues this message in the followingcases:

• IMS restart• Simple checkpoint• /MODIFY PREPARE or INITIATE OLCPHASE(PREPARE), to indicate the current activeonline change libraries before the new definitionsare committed


http://www.ibm.com/support/knowledgecenter/SSEPH2_15.1.0/com.ibm.ims15.doc.msgs/msgs/0202.htm#imsaben0202

• /MODIFY COMMIT or INITIATE OLCPHASE(COMMIT), to indicate the new active onlinechange libraries, after online change is committed

In the message text:modblks-name

Active MODBLKS DD in the IMS JCL, that identifiesthe active MODBLKS library. modblks-name iseither MODBLKSA or MODBLKSB. If the MODBLKSDD cards are omitted from the IMS JCL and onlinechange for MODBLKS is disabled, this variable isblank.

DFSDIRCThe data set ddname of the internally managedIMS directory data set.

format-nameActive FORMAT DD in the IMS JCL, that identifiesthe active MFS format library. format-name iseither FORMATA or FORMATB. If this system isDBCTL, format-name is blank.

nnnnModify ID number. When you initialize theMODSTAT data set, you decide what number toassign as the modify ID. Every time online changeis successful, this number increments by 1. If youinitialized this number to 0, the value indicateshow many online changes have been successfulsince cold start. The modify ID is used to recoversecurity status during an emergency restart.

This message is also issued after:

• Simple checkpoint invoked by /DBD• Simple checkpoint invoked by /DBR• Simple checkpoint invoked by /CHE

DFS3781 DB:name AREA:name DAMAGEAT RBA:xxxxxxxx OFFSET:nnnnnLENGTH:aa

ExplanationDuring emergency restart, XRF takeover, or therecovery phase of Fast Database Recovery, damageto the control interval (CI) was detected. The area isstopped.

In the message text, the variables and their meaningsare:DB

Database nameAREA

Area nameDAMAGE AT RBA

Relative byte address of the damaged controlinterval

OFFSETRelative offset of the damage within the CI

LENGTHLength of the damage

System actionIMS issues the normal area-stopped messages.

Programmer responseThe area must be recovered.

DFS3782I DB:O'name' AREA:nameADS:name 2ND CI DAMAGEDETECTED

ExplanationDamage to the second control interval (CI) wasdetected during DMAC refresh at the first openfollowing an XRF takeover.

User responseTake one of the following actions:

• If multiple area data sets (MADS) are defined,change the ADS copy damaged by the second CI tounavailable status for a subsequent recovery Startthe area with the remaining valid ADS copies.

• If multiple area data sets (MADS) are not defined,recover the area.

DFS3784I PCB=(nnnn,ppppppp) ISREPLACED BY DFS3784IPCB=(dddddddd,ppppppp,NUM=yyy)

ExplanationAfter associating the DBPCB number nnnn of theHALDB statement with the DBPCB label or namespecified in the DBPCB control block, the processingdetected duplicate HALDB statements with a DBPCBlabel or name of dddddddd. When this occurs theDBPCB label or name takes precedence over theDBPCB referenced by the nnnn number. yyy indicatesthe range, if specified.



Module:


DFSHSPP0

DFS3785E DIAGNOSE AWE INITIALIZATIONFAILED – reason_text

ExplanationAn unrecoverable error was encountered whileinitializing the diagnostic AWE processor. Servicesoffered by this AWE processor will not be availableuntil the problem is corrected and IMS is restarted.


reason_textUsed to identify the specific error encountered.The reason text can be:DGSW GETSTOR FAILED RC=retcode

During initialization of the diagnostic AWEprocessor DGS TCB, a GETSTOR call was madeto allocate storage for the DGSW (DiagnosticsWork Area). However, the GETSTOR callreturned with a nonzero return code: retcode.

System actionIMS continues processing, but the services offered bythe diagnostic AWE processor will not be availableuntil the problem is resolved and IMS is restarted.

System programmer response:If this is the only storage shortage error encounteredwhile starting IMS, contact IBM Software Support.

Module:DFSDGS80

DFS3786E DIAGNOSE AWE PROCESSINGERROR – reason_text

ExplanationAn unrecoverable error was encountered duringprocessing of a diagnostic AWE. This message isissued during diagnostic AWE processing when anunrecoverable error or an invalid AWE request isencountered.


reason_textIdentifies the specific error:DUPLICATE INITIALIZATION AWE

A duplicate initialization AWE request wasreceived. Because only one initialization AWErequest is allowed, the duplicate request isignored.

DUPLICATE TERMINATION AWEA duplicate termination AWE request wasreceived. Because only one termination AWE

request is allowed, the duplicate request isignored.

request QUEUED PRIOR TO INITAn AWE request was received before theinitialization AWE request was received andprocessed. The initialization AWE request mustbe the first AWE that is queued and processed.In the reason text, request identifies the typeof AWE request that was received. The AWE isignored.

UNKNOWN AWE FUNCTION: hex_idAn AWE request was received that is unknownto the diagnostic AWE processor. In thereason text, hex_id identifies the hexadecimalidentifier of the unknown AWE function thatwas requested. The AWE is ignored.

System actionIMS continues processing, but the diagnostic AWEservice requested did not complete successfully.


Module:DFSDGS80

DFS3787E DIAGNOSE SYSOUT PROCESSINGERROR – reason_text

ExplanationAn unrecoverable error was encountered duringprocessing of the SYSOUT request of a /DIAGNOSEcommand. The message is issued during /DIAGNOSEcommand SYSOUT processing when an unrecoverableerror is encountered.


reason_textIdentifies the specific error:INVALID FUNCTION CODE SPECIFIED

A call that was made to /DIAGNOSE commandSYSOUT I/O services requested an invalidfunction. The invalid request is ignored.Contact IBM Software Support to report theerror.

INVALID STATE FOR function REQUESTA call that was made to /DIAGNOSE commandSYSOUT I/O services requested the out-of-sequence function identified in the reason text.The invalid request is ignored. Contact IBMSoftware Support to report the error.

ALLOCATION FAILED RC=retcodeAn error was encountered while allocating therequested SYSOUT data set. Ensure that avalid SYSOUT class was specified and that JES


services are available. If the error persists,note the return code in the reason text:retcode. Contact IBM Software Support toreport the error, and save the IMS system logthat contains a diagnostic X’67D0’ log record,which provides more detailed informationabout the error.

DCBB GETSTOR FAILED RC=retcodeAn error was encountered while allocatingthe requested SYSOUT data set. A GETSTORcall was made to allocate DCBB storage,and GETSTOR returned with a nonzero returncode: retcode. If the IMS storage problem istemporary, issue the request again later. Ifthe problem persists, contact IBM SoftwareSupport.

SIOB GETSTOR FAILED RC=retcodeAn error was encountered while allocatingthe requested SYSOUT data set. A GETSTORcall was made to allocate SIOB storage, andGETSTOR returned with a nonzero returncode: retcode. If the IMS storage problem istemporary, issue the request again later. Ifthe problem persists, contact IBM SoftwareSupport.

DECB GETSTOR FAILED RC=retcodeAn error was encountered while allocatingthe requested SYSOUT data set. A GETSTORcall was made to allocate DECB storage,and GETSTOR returned with a nonzero returncode: retcode. If the IMS storage problem istemporary, issue the request again later. Ifthe problem persists, contact IBM SoftwareSupport.

DATASET OPEN FAILED RC=retcodeAn error was encountered while opening therequested SYSOUT data set. System OPENservices returned with a nonzero return code:retcode. Save the IMS system log that containsa diagnostic X'67D0' log record, which providesmore detailed information about the error.Also, retain the system or IMS job log thatmight contain the z/OS IEC message relatedto the error. Contact IBM Software Support toreport the error.

DATASET CHECK FAILED RC=retcodeAn error was encountered while checking awrite buffer for the SYSOUT data set. SystemCHECK services returned with a nonzeroreturn code: retcode. Contact IBM SoftwareSupport to report the error, and save the IMSsystem log that contains a diagnostic X'67D0'log record, which provides more detailedinformation about the error. Also, retain thesystem or IMS job log that might contain thez/OS IEC message related to the error.

DATASET CLOSE FAILED RC=retcodeAn error was encountered while closing theSYSOUT data set. System CLOSE servicesreturned with a nonzero return code: retcode.Contact IBM Software Support to report theerror, and save the IMS system log thatcontains a diagnostic X'67D0' log record, whichprovides more detailed information about theerror. Also, retain the system or IMS job logthat might contain the z/OS IEC messagerelated to the error.

DATASET WRITE FAILED RC=retcodeAn error was encountered while writing tothe SYSOUT data set. System WRITE servicesreturned with a nonzero return code: retcode.Contact IBM Software Support to report theerror, and save the IMS system log thatcontains a diagnostic X'67D0' log record, whichprovides more detailed information about theerror. Also, retain the system or IMS job logthat might contain the z/OS IEC messagerelated to the error.

DATASET SYNAD/ABEND EXIT CALLEDAn error was encountered with the SYSOUTdata set. Contact IBM Software Support toreport the error, and save the IMS system logthat contains a diagnostic X'67D0' log record,which provides more detailed informationabout the error. Also, retain the system orIMS job log that might contain the z/OS IECmessage related to the error.

DATASET WRITING PAST LAST BLOCKA call that was made to /DIAGNOSE commandSYSOUT I/O services requested an out-of-sequence WRITE function. The invalid requestis ignored. Contact IBM Software Support toreport the error.

System actionIMS continues processing, but the /DIAGNOSEcommand SYSOUT requested did not completesuccessfully.


Module:DFSDGS82

Related reference/DIAGNOSE SNAP command (Commands)

DFS3788I DIAGNOSE SYSOUT DATA SETdsname action FOR SNAP resourceTKN(token)


http://www.ibm.com/support/knowledgecenter/SSEPH2_15.1.0/com.ibm.ims15.doc.cr/imscmds/ims_diagnose_snap.htm#ims_cr1diagnose_snap

ExplanationThe requested SYSOUT data set for the /DIAGNOSEcommand was opened or closed.


dsnameName of the SYSOUT data set.

actionAction to be taken for the data set: OPENED orCLOSED.

resourceName of the /DIAGNOSE SNAP commandresource that is associated with the SYSOUT dataset request.

tokenUnique 8-byte hexadecimal token that isassociated with the SYSOUT request of the /DIAGNOSE SNAP command. This token is thesame as the token that is included in messageDFS3789I and can be used to correlate commandactions and SYSOUT results.

System actionThe SYSOUT data set for the /DIAGNOSE command isopened or closed successfully.


Module:DFSDGS82


DFS3789I DIAGNOSE COMMAND SNAPresource QUEUED TO SYSOUTTKN(token)

ExplanationA /DIAGNOSE command with OPTION(SYSOUT) wasissued, the SNAP data capture process has completed,and the results have been successfully enqueued tothe DGS AWE processor for SYSOUT processing.


resourceSNAP resource type that is specified in thecommand.

tokenUnique 8-byte hexadecimal token that isassociated with the SYSOUT request of the /DIAGNOSE SNAP command. This token is thesame as the token that is included in message

DFS3788I and can be used to correlate commandactions and SYSOUT results.

System actionThe requested /DIAGNOSE command has beensuccessfully processed, and the requested SNAP datahas been enqueued for SYSOUT processing.


Module:DFSDGS9C


DFS3792 QCNT KEYWORD INVALID WITHDISPLAY BY ATTRIBUTE OPTION

ExplanationThe QCNT keyword cannot be used on a /DISPLAYUSER command if the users are to be displayed byattribute. The QCNT keyword cannot be used on a /DISPLAY NODE command if the nodes are to bedisplayed by attribute.


Operator responseEither specify a specific user or node, or omit theQCNT keyword. Then reenter the command.

Module:DFSIDPE0, DFSIDPB0

DFS3793E AN EMERGENCY RESTARTCANNOT BE USED TO INTRODUCETHE CURRENT CHANGE TOACBMGMT SUPPORT.

ExplanationDuring an emergency restart, IMS detected a changeto the IMS management of ACBs (ACBMGMT) supportthat cannot be introduced into an online IMS systemduring an emergency restart.

System actionIMS restart terminates and IMS issues abend U0071.




System programmer responseUse a cold start or normal restart with no checkpoint(/NRE CHECKPOINT 0) to activate the current changeto the IMS management of ACBs support.

Module:DFSRDB30

Related conceptsIMS directory data sets (System Definition)Related informationCATALOG and CATALOGxxxx sections of theDFSDFxxx member (System Definition)0071 (Messages and Codes)

DFS3794W AN INCOMPLETE SNAPQCHECKPOINT MAKES TAKEOVERIMPOSSIBLE. ALTERNATE SYSTEMIS TERMINATED.

ExplanationAn XRF alternate system began reading the SNAPQcheckpoint necessary to achieve its tracking phase,and the checkpoint was found to be incomplete.

System actionThe alternate IMS is shut down.

Programmer responseRestart the active and alternate systems.

DFS3795I IOT EEQE PURGE FAILED.AREA=areaname RBA=xxxxxxxxRC=yy

ExplanationDuring I/O toleration EEQE purge processing, at leastone EEQE could not be purged. For each EEQE thatis not purged, IMS issues this message followed bymessage DFS0488I. areaname identifies the name ofthe associated area; xxxxxxxx identifies the RBA ofthe associated CI. Reason code yy has the followingmeanings.Code (dec)

Meaning04

The request to get the CI lock failed.08

The request to get the area lock failed.12

The area OPEN request failed.

16I/O error occurred while attempted to purge theEEQE.

20I/O toleration purge was preparing to writetolerated data for a VSO area, but an area data setwas stopped (or in the process of being stopped)due to a write error on the second CI. The areadata set stop can cause the entire area to stop; inthis case, if purge continues it can abend.

System actionIMS continues processing, but skips the EEQE purge.

Operator responseIssue the /UNLOCK SYSTEM command later to purgethe EEQEs.

If the return code is 12, issue the /START AREA orUPDATE AREA START(ACCESS) command for thenamed areas; then issue the /UNLOCK SYSTEM again.

IMS issues return code 16 only if XRF takeoverprocessing has not completed when you request theEEQE purge. If you reenter the /UNLOCK commandafter the takeover processing is complete, the purge isusually successful. To display any EEQEs that were notpurged, enter the /DIS DB ALL BKERR.

If the area is stopped, recover the area.

DFS3796W AT LEAST ONE FAST PATH EEQESTILL EXISTS.

ExplanationWhile processing a normal shutdown, IMS detectedthat at least one EEQE (Extended Error QueueElement) still exists.

System actionNormal shutdown processing continues.


Programmer responseSee message DFS3867I to determine the appropriateaction to take.

Related information“DFS3867I” on page 1110AUTOMATIC /UNLOCK SYSTEM WILL BE DONE

DFS3798 SB NOT INITIALIZED






ExplanationA /START SB command was not processed becausea SBONLINE control statement was not provided inmember DFSVSMxx of IMS.PROCLIB.

System actionIMS has not loaded any Sequential Buffering (SB)modules and does not process the /START SBcommand.

User responseProvide a SBONLINE control statement in theappropriate DFSVSMxx member of IMS.PROCLIB if youwant to use SB.

DFS3799 SB NOT FUNCTIONAL

ExplanationThe /START SB command was not processedbecause previous IMS software problems preventedthe use of Sequential Buffering (SB).

System actionIMS discards the /START SB command.

User responseCheck for previously issued error messages describingthe software problem that caused IMS to deactivateSB.

DFS3800 UNABLE TO ACQUIRE STORAGEFOR MFS DYNAMIC DIRECTORYEXPANSION

ExplanationStorage in the IMS extended private area isunavailable for expanding the MFS Dynamic Directoryduring initialization.

System actionThe MFS Dynamic Directory will be stabilized. Nomore format blocks will be added. The directorywill remain stabilized, and this message will not bereissued until after the next IMS restart or after thesuccessful completion of a /CHANGE DIRECTORYMFS command. This command will restore the MFSDynamic Directory back to the "primed" state thatexisted just after IMS initialization.

Programmer responseAllow the IMS system to run with the MFS DynamicDirectory stabilized until the next restart, or if feasible,issue the /CHANGE DIRECTORY MFS command.


Chapter 80. DFS messages, DFS3801 - DFS3850A


DFS3801 CHKPT SNAPQ REQUIRED ONACTIVE SYSTEM

ExplanationAn alternate system in the XRF complex sends thismessage to the master terminal operator (MTO) if thealternate system fails to locate the SNAPQ checkpointof the active system after thirty seconds.

System actionThe alternate system continues.

Operator response:(master terminal) Determine whether the activesystem has taken a SNAPQ checkpoint. If not, forcea manual SNAPQ checkpoint by entering a /CHESNAPQ command on the active system. If this messagepersists after the active system has taken a SNAPQcheckpoint, a problem might exist with the alternatesystem. Cancel the alternate system with a memorydump.


DFS3802W XRF NOT POSSIBLE - ONLY ONERDS ALLOCATED.

ExplanationAn XRF-defined IMS system was started, but only onerestart data set (RDS) DD statement was included inthe JCL.

System actionThe IMS alternate system being started terminatesabnormally. Any other IMS system starts continue, butthe system will not be XRF-capable.

Programmer responseIf you want an XRF-capable system, shut down theIMS system. Include the IMSRDS and the IMSRDS2 DDstatements for the restart data sets; then restart theIMS system.

DFS3803I ENTER /SWITCH TO CAUSE THEBACKUP TO TAKEOVER

ExplanationThe alternate (backup) system detected a potentialfailure of the active system, but the operator mustapprove all takeovers.

System actionThe alternate system continues tracking the activesystem.

Operator response:(master terminal) To initiate a takeover, enter /SWITCH SYSTEM FORCE on the alternate system.


DFS3804I LATEST RESTART CHKPT: yyddd/hhmmss, LATEST BUILDQ CHKPT:yyddd/hhmmss

or

[LATEST] [RESTART] CHKPT: yyddd/hhmmss,HSBID=xx – [LATEST] BUILDQ CHKPT: yyddd/hhmmss, HSBID=xx

or

LOG READ CHKPT: yyddd/hhmmss – RESTARTCHKPT: yyddd/hhmmss, HSBID=xx – BUILDQCHKPT: yyddd/hhmmss, HSBID=xx

ExplanationAt the completion of each IMS checkpoint, IMS issuesthis message to inform you of the last checkpoint IDthat is valid for loading DC blocks. When running inan XRF environment, it indicates which IMS system(HSBID) wrote the CHKPT. The latest RESTART orRESTART CHKPT indicates which IMS system must berestarted when an XRF system abends. The exceptionto this is a BLDQ restart, which can be done by eitherIMS system.

The first form of this message is issued in a non-XRFenvironment.


The second form of this message is typically issuedwhen running in XRF. For XRF systems following ashutdown checkpoint or a restart, the word LATESTdoes not appear in the message, and the wordRESTART is abbreviated to RST.

The third form of this message is issued only aftera takeover occurs, and when the system checkpointneeded for IMS recovery was written before theLAST DC CHKPT and before the takeover. The newcheckpoint ID, LOG READ CHKPT, indicates only thecheckpoint at which IMS starts reading the input log.The checkpoint ID does not have an HSBID and mustnot be used when determining which IMS system torestart.

In some circumstances, IMS might not be have beenable to issue this message with a latest checkpointduring a shutdown or cancel. In such circumstances, alater restart might show a different CHKPT.


Operator response:(master terminal) This information is useful fordetermining which IMS system to restart after an XRFtakeover.

DFS3805 SURVEILLANCE KEYWORDINVALID - NO XRF CAPABILITY

ExplanationA /CHANGE SURVEILLANCE command was enteredon a system that is not XRF-capable.


Operator response:(master terminal) Contact the system programmer.

Programmer response:If you want XRF capability, define the IMS system asan XRF-capable system.

DFS3806 BACKUP KEYWORD INVALID - NOXRF CAPABILITY

ExplanationYou entered an /ERE BACKUP command or a /STOP BACKUP command on a system that is not XRF-capable.


Programmer responseIf you want XRF capability, define the IMS system asan XRF-capable system.

DFS3807 MORE THAN 1 PARAMETERIN /STA OR /STO SURVEILLANCECOMMAND

ExplanationA /START or /STOP SURVEILLANCE commandwas entered with more than one SURVEILLANCEparameter. The SURVEILLANCE parameter must beone of these:

LNKRDSLOGALL


Programmer responseReenter the command with a single SURVEILLANCEparameter.

DFS3808I RDS|LNK|LOG SURVEILLANCEALREADY STARTED|STOPPED


• A /START SURVEILLANCE command was entered,but the specified type of surveillance had alreadybeen started

• A /STOP SURVEILLANCE command was entered,but the specified type of surveillance had alreadybeen stopped.



DFS3809 NO LINK SURVEILLANCE - LINKNOT DEFINED

ExplanationA /START or /STOP SURVEILLANCE LNK commandwas entered, but an Intersystem Communication (ISC)


link between the active and the alternate IMS systemsis not defined to IMS.



Programmer responseDefine an ISC link to the XRF-capable IMS system ifyou want this type of surveillance.

DFS3810 KEYWORD ACTIVE OR BACKUPDOES NOT MATCH SYSTEM OR ISMISSING


• The keyword indicating whether the /SWITCHSYSTEM command is being entered on the activeor the alternate (backup) system (ACTIVE/BACKUP)does not correspond to the actual system.

• The keyword ACTIVE is missing. The keywordACTIVE must be specified when the /SWITCHSYSTEM command is entered on the active system.


Programmer responseBe sure of the status (active or alternate) of the systemon which you are entering the command.

DFS3811I LNK|RDS|LOG SURVEILLANCEACTIVE|INACTIVE; INTERVAL|TIMEOUT VALUE CHANGED FROMxx TO yy

ExplanationThis informational message responds to the /CHANGESURVEILLANCE command, and is issued with theDFS058I CHANGE COMMAND COMPLETED message.The following information is given in the message:

• which type of surveillance was changed (LNK|RDS|LOG)

• whether that type of surveillance was active orinactive

• the original (xx) and new (yy) interval or timeoutvalues.


Programmer responseCheck that the command produced the intendedresults.

Related information“DFS058I” on page 44CCC COMMAND COMPLETED EXCEPT KKK P01,P02, P03, P04, P05, P06, P07, ...ETC.

DFS3812I BACKUP LNK|RDS|LOG INTERVALVALUE OF xx HAS BEEN FORCEDTO ACTIVE VALUE OF yy

ExplanationThis informational message, issued in response tothe /CHANGE SURVEILLANCE command, indicatesthat IMS modified system data in order to continueprocessing the command. When the timeout or theinterval value is being changed by entering /CHANGESURVEILLANCE on the alternate (backup) system, andthe alternate interval value is less than the activeinterval value, the alternate interval value defaultsto the active interval value. This message is issuedwith the DFS058I CHANGE COMMAND COMPLETEDmessage.

System actionIMS continues processing the command with themodified data.


Programmer responseCheck the command produced the intended results.If you want different results, reenter the /CHANGESURVEILLANCE command.


DFS3813 SYSTEM NOT XRF CAPABLE -COMMAND REJECTED

ExplanationThe /DIS HSB or /UNLOCK SYSTEM command wasentered on a system that is not XRF-capable.

Chapter 80. DFS messages, DFS3801 - DFS3850A 1097



Module:DFSICLN0

DFS3814 FORCE KEYWORD IS REQUIRED

ExplanationThe FORCE keyword is required when entering /SWITCH from an alternate system.


Operator response:(master terminal) If you want to switch processingfrom the current active system to the alternate system,add the FORCE keyword, and reenter the command.


DFS3815 RDS SURVEILLANCE NOTSTARTED DUE TO WRITE ERRORON THE ACTIVE

ExplanationThe command to start restart data set (RDS)surveillance was rejected because a previous writeerror was encountered on the active system.

System actionThe command to start RDS surveillance is rejected.


Programmer responseDetermine the cause of the write error. The restartdata set (RDS) might have to be reformatted.

DFS3816 COMMAND REJECTED - SNAPQCHECKPOINT NOT YET FOUND

ExplanationYou cannot start or stop surveillance before thealternate system is synchronized with the active

system by processing a SNAPQ checkpoint from theactive system.


Operator response:(master terminal) Wait until the active system issuesthe INSYNCH message, DFS3858I. Then reenter theSURVEILLANCE command.


Related information“DFS3858I” on page 1108INSYNCH ARRIVED FROM THE BACKUPSYSTEM

DFS3817 SURVEILLANCE KEYWORDPARAMETER IS MISSING ORINVALID

ExplanationA /CHANGE SURVEILLANCE, /STARTSURVEILLANCE, or /STOP SURVEILLANCE commandwas rejected for one of the following reasons:

• The SURVEILLANCE parameter was missing orinvalid.

• More than one SURVEILLANCE parameter wasentered.

Valid SURVEILLANCE parameters are LNK, restart dataset (RDS), LOG, and ALL.


Programmer responseCorrect the SURVEILLANCE parameter; then enter thecommand again.

DFS3818 INTERVAL KEYWORD PARAMETERIS MISSING OR INVALID

ExplanationA /CHANGE SURVEILLANCE command was rejectedfor one of the following reasons:

• The INTERVAL value was missing or invalid.• More than one INTERVAL value was entered.


The INTERVAL value must be greater than 0 and lessthan 100.


Programmer responseCorrect the INTERVAL value; then reenter thecommand.

DFS3819 TIMEOUT KEYWORD PARAMETERIS MISSING OR INVALID

ExplanationA /CHANGE SURVEILLANCE command was rejectedfor one of the following reasons:

• The TIMEOUT value was missing or invalid.• More than one TIMEOUT value was entered.

The TIMEOUT value must be greater than 0 and lessthan 100.


Programmer responseCorrect the TIMEOUT value; then reenter thecommand.

DFS3820 TOD NOT OPERATIONAL/AVAILABLE

ExplanationThe Time-of-Day (TOD) clock was unavailable for useby the surveillance function.

System actionNormal processing continues, but ISC surveillance andrestart data set (RDS) surveillance are disabled.


DFS3821 GETMAIN FAILED FOR TIMERWORKAREAS

ExplanationThe surveillance does not function because temporarystorage for a work area was unavailable.

System actionProcessing continues without ISC and restart data set(RDS) surveillance.

Operator response:(master terminal) Retry the command. If it fails again,increase the size of the control region before the nextstartup.


DFS3822 INVALID SURVEILLANCEREQUEST

ExplanationA /START or /STOP SURVEILLANCE command wasentered with an invalid parameter. The SURVEILLANCEparameter must be one of the following: LNK, RDS,LOG, or ALL.


Operator response:Reenter the command with the correct parameter.


DFS3823 I/O ERROR DURINGSURVEILLANCE READ/WRITE ONxxxxxxxx

ExplanationA read or write error occurred on the restart data set(RDS) while RDS surveillance was active. The variablexxxxxx has one of the following values:IMSRDS

The error occurred on the data set defined by theIMSRDS DD statement.


System actionProcessing continues, but RDS surveillance stops andno longer participates in the takeover decision.

Operator response:(master terminal) Determine the cause of the I/Oerror and reformat the RDS, if necessary. You can doRDS formatting only when restarting the active system.


DFS3824 COMMAND INVALID FOR BACKUPSYSTEM

ExplanationAn invalid command was entered on the alternate(backup) system or the command syntax was notcorrect for the alternate system.


Programmer responseReenter the command on the active system or correctthe command syntax and reenter on the alternatesystem.

DFS3825 COMMAND INVALID FOR ACTIVESYSTEM

ExplanationThe /STOP BACKUP command was entered on anactive system. The /STOP BACKUP command is onlyvalid if entered on an alternate (backup) system.


Programmer responseIf you intended to terminate the alternate system,reenter the command on the alternate system.

DFS3826 TRANSACTION KEYWORDPARAMETER IS MISSING ORINVALID

ExplanationThe TRANSACTION parameter on a /CHANGETRANSACTION MAXRGN command was invalid ormissing. The TRANSACTION parameter was invalid forone of the following reasons:

• The transaction code was greater than 8 characters.• The transaction code was not known to IMS.• Load balancing was not in effect for the specified

transaction.


Operator response:

Check the transaction code; then reenter thecommand.


DFS3827 MAXRGN KEYWORD PARAMETERIS MISSING OR INVALID

ExplanationA /CHANGE TRANSACTION MAXRGN command wasrejected because the MAXRGN parameter was invalidor missing. The MAXRGN parameter was invalid forone of the following reasons:

• The MAXRGN parameter must be in the range of 0and 255 inclusive.

• Multiple MAXRGN parameters were entered.


Programmer responseCorrect the MAXRGN parameter; then reenter thecommand.

DFS3828 UNABLE TO PROCESS /DISPLAYOLDS COMMAND - LOG NOTAVAILABLE

ExplanationA /DISPLAY OLDS command was entered during theinitialization or tracking phase of the alternate system,when log data sets are unavailable.


Programmer responseDelay entry of the /DIS OLDS command until thealternate system has taken over and has become theactive system. Only at this time is the log data setsavailable.

DFS3829 NOBACKOUT KEYWORD INVALIDWITH DATABASE ALL

ExplanationThe DATABASE parameter ALL cannot be used with theparameter NOBACKOUT.



Programmer responseReenter the command with one or more specificDATABASE parameters.

DFS3830 NO DEFERRED PAGE FIXING WASDONE

ExplanationThe active system found no requests for deferred pagefixing for IMS systems in an XRF complex.

System actionThe system continues with normal processing.

Programmer responseIf you want deferred page-fixing, see informationabout defining IMS.PROCLIB members for XRF.

Related referenceDefining IMS.PROCLIB members for XRF(System Administration)

DFS3831 MODETABLE KEYWORD INVALIDWITH DISPLAY BY ATTRIBUTEOPTION

ExplanationThe MODETABLE keyword cannot be used on a /DISPLAY NODE command if the nodes are to bedisplayed by attribute.

System actionThe command is rejected

Operator response:Reenter the command with the ALL keyword ratherthan specific node names.


DFS3832I LNK|RDS|LOG TIMEOUT VALUE OFxx HAS BEEN FORCED TO yy

ExplanationThis informational message, issued in response tothe /CHANGE SURVEILLANCE command, indicatesthat IMS changed system data in order to continue

processing the command. It is issued in the followingcases:

• When the timeout value is being changed byentering /CHANGE SURVEILLANCE on the alternatesystem and the new timeout value is less than twicethe alternate interval value

• When the timeout value is being changed byentering /CHANGE SURVEILLANCE on the activesystem and the new timeout value is less than twicethe active interval value

• When the interval value is being changed byentering /CHANGE SURVEILLANCE on the alternatesystem and twice the new interval value is greaterthan the alternate timeout value

• When the interval value is being changed byentering /CHANGE SURVEILLANCE on the activesystem and twice the new interval value is greaterthan the active timeout value.

This message is issued with the DFS058I CHANGECOMMAND COMPLETED message.


Operator response:(master terminal) Be sure the command produced theintended results. If you want different results, reenterthe /CHANGE SURVEILLANCE command.



DFS3833I BACKUP LNK|RDS|LOG INTERVALVALUE OF xx HAS BEEN FORCEDTO LNK|RDS|LOG INTERVALVALUE OF yy

ExplanationThis message can be issued in response to a /CHANGE SURVEILLANCE command to indicate thatIMS changed system data in order to continueprocessing the command. It is issued in the followingcases:

• When the interval value is being changed byentering /CHANGE SURVEILLANCE LNK or /CHANGE SURVEILLANCE RDS on the alternate


http://www.ibm.com/support/knowledgecenter/SSEPH2_15.1.0/com.ibm.ims15.doc.sag/system_recovery/ims_xrf_prolibmembers.htm#ims_xrf_prolibmembers

http://www.ibm.com/support/knowledgecenter/SSEPH2_15.1.0/com.ibm.ims15.doc.sag/system_recovery/ims_xrf_prolibmembers.htm#ims_xrf_prolibmembers

(backup) system and the new alternate interval valueis less than the alternate LOG interval value.

• When the interval value is being changed byentering /CHANGE SURVEILLANCE LOG on thealternate system and the new alternate intervalvalue is greater than the alternate RDS and LNKinterval values.

• When the interval value specified on the LOGparameter is greater than the interval value specifiedon the RDS or LNK parameter. The interval value forthe LOG parameter must be less than or equal to therestart data set (RDS) and LNK interval values. Thisrestriction applies to original specifications madein member DFSHSBxx, or to specifications changedwith a /CHANGE SURVEILLANCE command.

This message is issued together with the DFS058ICHANGE COMMAND COMPLETED message.


Operator response:(master terminal) Be sure the command produced theintended results. If you want different results, reenterthe /CHANGE SURVEILLANCE command.



DFS3834W ALTERNATE IS (IN DANGER OF)FALLING BEHIND

ExplanationThe IMS XRF alternate subsystem has fallen behind oris in danger of falling behind in the processing of logrecords produced by the active IMS XRF subsystem.

Statistics are gathered over one minute intervalsto determine if either of these conditions hasoccurred. When either condition occurs, the messageis highlighted and frozen on the system console untilthe condition clears up.

The "falling behind" condition might extend the time ofa takeover should one be necessary.

System actionThe IMS alternate continues tracking the active andcan catch up over time. This message is frozen andhighlighted on the system console until the alternatehas caught up sufficiently. At that time, the message isno longer highlighted and rolls off the screen.

Operator responseAlert the system programmer of continued "in danger"messages so that appropriate preventive action canbe taken. When the alternate is falling behind, theelapsed time of a takeover can be extended. You canestimate the time lag behind the active by enteringthe /DISPLAY HSB command.

System programmer responseDetermine the cause of the "falling behind" periods,take any appropriate preventive actions, and contactIBM Software Support for assistance, if necessary.

Some actions to consider are:

• Assure a good balance between the use of Short andLong Message Queue data sets.

• Assure that the message queues are not filling up fora device that has been turned off.

• Increase the number of Message Queue buffersassigned to the Active and XRF Alternate systems.

• If you are experiencing high I/O rates on any of thedevices that contain the Message Queue data sets,consider splitting up those data sets with the highestI/O activity across different devices.

DFS3835W WAITING FOR THE FDBR REGIONRECOVERY FOR IMSID imsid

ExplanationThe indicated IMS subsystem is restarting after a priorfailure, but is in a wait state until the associated FastDatabase Recovery region (FDBR) completes cleanupfrom the prior failure. One of the following conditionsmight have occurred:

• The FDBR region is running and performing recovery.• The FDBR region is waiting for some action as

indicated on the FDBR region syslog.• A failure (such as XCF communications breakdown)

occurred in the central processing complex (CPC) onwhich the FDBR region is running.

• The FDBR region is in an abnormal wait or loop.


System actionThis message remains on the operator consoleduring recovery processing by the FDBR region. Uponcompletion the system removes this message from theconsole

Operator responseIf the FDBR region for the indicated imsid is runningand performing recovery, it is generating messagesindicating recovery progress; no action is required.

If the FDBR region is waiting for some action asindicated on the FDBR region SYSLOG, perform theaction specified in the related messages.

If a failure (such as XCF communications breakdown)has occurred in the central processing complex(CPC), initiate database recovery by entering the z/OSMODIFY command (F fdrproc,RECOVER).

If the FDBR region is in an abnormal wait or loop,cancel the FDBR region.

Module:DFSRST00

DFS3838I XRF INITIAL DB PRE-OPENCOMPLETE

ExplanationIn an XRF complex, the alternate system attempted topreopen all DL/I databases and all DEDB area datasets that were open at the time the active systemprocessed the initial SNAPQ checkpoint.



DFS3839I XRF INITIAL DC PRE-OPENCOMPLETE

ExplanationIn an XRF complex, the alternate IMS system checkedthe status of all terminals and opened and scheduledbackup session initiation for all Class 1 terminals thatare logged on to the active system at the time of theinitial SNAPQ checkpoint.



DFS3840 OPEN ERROR FORDDNAME=PROCLIB

ExplanationThe data set defined by the PROCLIB DD statementcould not be opened.

System actionProcessing continues without XRF capability.


Programmer responseCorrect the PROCLIB DD statement.

DFS3841I LNK|RDS|LOG SURVEILLANCEINTERVAL VALUE EXCEEDSALLOWABLE LIMIT.

ExplanationAn interval value for LNK, restart data set (RDS),or LOG surveillance in PROCLIB member DFSHSBxxexceeded 99 seconds.

System actionThe default interval values for LNK, RDS, or LOGsurveillance are used.


Programmer responseDefine the correct values in PROCLIB memberDFSHSBxx.

DFS3842I LNK|RDS|LOG SURVEILLANCETIMEOUT VALUE EXCEEDSALLOWABLE LIMIT

ExplanationA timeout value for LNK, restart data set (RDS), or LOGsurveillance in PROCLIB member DFSHSBxx exceeded999 seconds.

System actionThe default timeout values for LNK, RDS, or LOGsurveillance are used.



Programmer responseDefine the correct values in PROCLIB memberDFSHSBxx.

DFS3843I START COMMAND REJECTED-xxxSURV. NOT STARTED ON ACTIVESYSTEM.

ExplanationAn attempt was made to start LNK, LOG, restart dataset (RDS), or ALL surveillance on the alternate system,but the corresponding surveillance was not started onthe active system.


Operator response:(master terminal) Be sure the appropriatesurveillance is started on the active system first.


DFS3844I MSDB DDNAME= MSDBCPxSUCCESSFULLY UNALLOCATED

ExplanationIn an XRF-capable system, two MSDB checkpoint dataset pairs are allocated for startup. After the MSDBsare loaded, only one of the two data set pairs is used.The MSDB checkpoint data set pair that is not used isdeallocated. This message is issued after deallocationfor each of the two data sets in the pair.

System actionz/OS dynamically deallocated (SVC 99) the data setassociated with the ddname identified in the message.Normal operation continues.


DFS3845 NO SURVEILLANCE VALUESSPECIFIED, DEFAULTS WILL BEUSED

ExplanationThe XRF-related parameters in the DFSHSBxx memberof PROCLIB did not contain SURV (surveillance) values.

System actionProcessing continues using default surveillance values.

Operator response:If this message was unexpected, contact the systemprogrammer.

Programmer responseVerify that the default surveillance values areacceptable. If not, create a SURV entry in memberDFSHSBxx.

DFS3846I SURVEILLANCE FUNCTION NOTSUPPORTED IN A NON-XRFENVIRONMENT

ExplanationSurveillance cannot be performed on a system that isnot XRF-capable.

System actionSurveillance is not performed.



DFS3847 FORMAT ERROR IN READINGFROM PROCLIB PARAMETER INCOLUMN xx

ExplanationThe parameters in the PROCLIB data set memberDFSHSBxx or DFSFDRxx are formatted incorrectly.Value xx identifies the column number where the errorwas detected.

System actionProcessing continues, but any parameters inDFSHSBxx that follow the format error are ignored. Forerrors in DFSFDRxx, Fast Database Recovery (FDBR)terminates with an IMS abend 0574.



Programmer responseCorrect the format of the parameters in the PROCLIBmember DFSHSBxx or DFSFDRxx.


DFS3848 BLDL FAILED FOR FOLLOWINGMODULES

ExplanationOne or more user-written preinitialization routineswere not found. The routines that could not be foundare listed in the message.

System actionThe dependent region is terminated with abend 0588.


Programmer responseThe load modules listed in the error message arespecified in the DFSINTxx member in PROCLIB, butcannot be found in any of the program librariesavailable to the job step. If these load modules donot need to be executed, they should be removedfrom DFSINTxx. If they are to be executed, the loadmodules must be linked to a library accessible to thejob step.



DFS3849 PERMANENT I/O ERROR ON JOB/LINK/SVCLIB FOR FOLLOWINGMODULES

ExplanationA permanent I/O error was detected while attemptingto locate the user-written preinitialization routines.

The load modules not located because of the I/O errorare listed in the message.

System actionThe dependent region is terminated with pseudoabend0588.


Programmer responseSee the information about abend 0588.


DFS3850A ENTER /STA DC COMMAND TOOPEN VTAM ACB

ExplanationThe alternate IMS system in an XRF complex could notopen VTAM ACB during system initialization, althoughthe active system could open its VTAM ACB.


Operator response:(master terminal) Be sure the VTAM minor node(APPLID) referred to by the VTAM ACB is correctlyinitialized; then issue /START DC on the alternatesystem.


Problem determination1, 3, 6, 10 and the VTAM definition of the VTAM minornode (APPLID) referred to by the VTAM ACB for theIMS system.








DFS3851I YOU CANNOT CHANGE XRFSPECIFICATIONS IN THISRESTART

ExplanationThis message is issued only in an XRF environment forone of the following reasons:

• The HSBID parameter is incorrect.

The HSBID parameter in the JCL of the system beingrestarted (NRE/ERE) must be the same as the HSBIDparameter in the JCL of the failing system in theXRF complex. To determine the correct JCL (active/alternate) to use:

1. On the secondary console (hardcopy device), findthe last "DFS3804I LAST CHKPT ID VALID FORRESTART: yyddd/hhmmss" message.

2. Determine the date and time from theDFS3804Imessage.

3. On the secondary console (hardcopy device),find the "DFS994I *CHKPT yyddd/hhmmss*ctypertype START COMPLETED" message whose dateand time match the DFS3804I message.

4. Determine the IMS ID from the DFS994Imessage.

5. Use this IMS ID JCL for the emergency restart.• The RSENAME parameter is incorrect.

The RSENAME parameter in the JCL of the alternatesystem being restarted (/ERE BACKUP) must be thesame as the RSENAME parameter in the JCL of theactive system in the XRF complex. The RSENAMEparameter is located in IMS PROCLIB memberDFSHSBxx. The xx represents the two characters ofthe HSMBR=xx parameter in the IMS control regionJCL.

• The USERVAR parameter is incorrect.

The USERVAR parameter in the JCL of the alternatesystem being restarted (/ERE BACKUP) must be thesame as the USERVAR parameter in the JCL of theactive system in the XRF complex. The USERVARparameter is found in the IMS PROCLIB memberDFSHSBxx. The xx represents the two characters ofthe HSMBR=xx parameter in the IMS control regionJCL.


Operator response:(master terminal) Correct the error based on theinformation in the Explanation of this message.


DFS3852I THE OTHER SYSTEM IS NOT THEACTIVE SYSTEM

ExplanationWhile bringing up an alternate system, the X'4001' logrecord from the active system contained an HSBIDvalue of zero. A zero value is invalid for an IMS activesystem in an XRF complex.


Operator response:(master terminal) Be sure that the correct log file wasselected for the restart.


Problem determination5, 8 (for both the active system and the alternatesystem)


DFS3853I DEDB AREA IS NOT AUTHORIZEDWITH DBRC. AREA STOP HASBEEN REQUESTED FOR AREA = ,DB = .

ExplanationDuring a takeover, the alternate system verifies thatall Fast Path areas opened by processing the failing




system log are authorized with DBRC. The area namedin this message is not authorized with DBRC.

System actionThe Fast Path area is internally stopped and closed.

Operator response:(master terminal) Look for other error messagesdescribing problems with this area. If none are found,the area can be restarted.


DFS3854A WHEN THE PREVIOUS ACTIVEIMS SUBSYSTEM TERMINATES,REPLY 'UNLOCK' [IMSID=imsidASID=asid RSE=rsename]

ExplanationAn IMS system in an XRF complex is terminating inI/O toleration mode. Unless the previous active systemhas terminated, the termination of the current IMSsystem threatens the integrity of the databases.

The information in brackets will not be displayed ifinsufficient storage is available to display the completemessage.

System actionThe termination of the IMS system is waiting for theoperator to guarantee that the previous active systemhas terminated.


Master terminal operator response: Reply UNLOCKonly after the previous active system has terminated.

Note: UNLOCK does not purge IOT EEQEs.

DFS3855I DEDB AREA HAS NO OPEN ADSCSAT TIME OF TAKEOVER. AREASTOP REQUESTED FOR AREA = ,DB = .

ExplanationDuring the tracking phase in an XRF complex, thealternate system could not open all area data sets(ADS) that were opened by the active system. Sincethere were no valid ADSs open at takeover time, thearea was stopped.

System actionThe area is closed and stopped. An error messagedescribing the ADS open failure should have beenissued before this message.


Programmer responseLook for another error message that describes theADS open failure. Correct the error as indicated in themessage; then restart the area.



DFS3856I REQSYNC WAS PROCESSED TOTAKE SNAPQ CHKPT

ExplanationThe REQSYNC (SNAPQ checkpoint request) sent fromthe alternate system was processed, and SNAPQcheckpoint process was scheduled in the activesystem.



DFS3857I OKTOSYNC ARRIVED FROM THEACTIVE SYSTEM

ExplanationThe alternate system received a signal that indicatesthe active system began taking the SNAPQ checkpointprocess from the active system.



DFS3858I INSYNCH ARRIVED FROM THEBACKUP SYSTEM


ExplanationThe active system received a signal indicating thealternate (backup) system synchronized with theactive system by processing the SNAPQ checkpointrecords from the alternate system.



DFS3859I PRIORITY n TERMINAL SESSIONSSWITCHED

ExplanationThe former alternate system (now the active system)has taken over all terminal sessions with priority leveln that were active at the time the previous activesystem failed.



DFS3860I ALL TERMINAL SESSIONSSWITCHED

ExplanationThe former alternate system (now the active system)has taken over all terminal sessions that were active atthe time the previous active system failed.



DFS3861 SYSTEM TAKEOVER OCCURRED

ExplanationThis message is issued when the former alternatesystem (now the active system) informs the terminaluser at session takeover that system takeovercompleted in the host system.



DFS3862 INVALID LOGON REQUEST IN THEALTERNATE SYSTEM

Explanation:For information and actions, see message DFS3862I.

Related informationDFS3862IINVALID LOGON REQUEST IN THE ALTERNATESYSTEM - NODE nodename

DFS3862I INVALID LOGON REQUEST INTHE ALTERNATE SYSTEM - NODEnodename

ExplanationThe alternate system in an XRF complex can accept aLOGON request from one of the following during thetracking phase:

• MTO terminal• ISC link between the active and alternate IMS

systems• Class 1 terminal that is eligible for a backup session,

has an active session on the active system, andhas no backup session currently active. For an ETOterminal, both the physical terminal and the terminaluser's control blocks must exist and be coupledtogether.

The first form of the message is issued bythe /OPNDST command processor. The commandreferences an invalid node (not the MTO or ISC link).The second form of the message is issued by theLOGON or SCIP exit if a LOGON represents a node IDthat is not one of the valid node names.

System actionThe LOGON request is rejected.

Operator response:(master terminal) Log on from an acceptable terminal.


DFS3863 FORMAT RDS CONFLICTS WITHBACKUP KEYWORD


ExplanationFORMAT RDS is invalid in a /ERE command thatcontains the keyword BACKUP.


Operator response:If you are trying to bring up an alternate (backup)system, reenter the command specifying BACKUPwithout FORMAT RDS. Only SM, LM, QC, and SP areallowed.


DFS3864 FORMAT WADS CONFLICTS WITHBACKUP KEYWORD

ExplanationFORMAT WADS is invalid in a /ERE command thatcontains the keyword BACKUP.


Operator response:If you are trying to bring up an alternate (backup)system, reenter the command specifying BACKUPwithout FORMAT WADS. Only SM, LM, QC, and SP areallowed.


DFS3865 FORMAT ALL CONFLICTS WITHBACKUP KEYWORD

ExplanationFORMAT ALL is invalid in a /ERE command thatcontains the keyword BACKUP.


Operator response:(master terminal) If you are trying to bring upan alternate (backup) system, reenter the commandspecifying BACKUP without FORMAT ALL. Only SM, LM,QC, and SP are allowed.


DFS3866 BACKUP KEYWORD INVALID - NOMODSTAT2

ExplanationThe XRF alternate (backup) IMS system issues thismessage if an /ERE command with the BACKUP optionis entered, but no MODSTAT2 is available.

System actionThe /ERE command is rejected.


System programmer responseMake sure the MODSTAT2 ddname is specified in theJCL procedure and the data set exists.

DFS3867I AUTOMATIC /UNLOCK SYSTEMWILL BE DONE

ExplanationAt least one Fast Path EEQE (unwritten buffer) was notwritten out by the I/O Toleration Purge function. Afteremergency restart processing completes, IMS willinternally process the /UNLOCK SYSTEM command torerun the I/O Toleration purge function.

System actionAs long as the EEQEs exist, normal transaction I/Orequests continue to be honored, but the results aremaintained in the EEQE buffer. The actual I/O from theEEQE buffer takes place after the /UNLOCK SYSTEMcommand processing is complete.


DFS3868 THE IMSID NAME DOES NOTMATCH THE CHECKPOINT RSENAME

ExplanationSince the previous IMS startup was an XRF-capablesystem, the following ERE startup, even though notXRF-capable, must specify an IMSID that matches


the checkpointed recoverable service element (RSE)name.


Operator response:Change the IMSID PROCLIB parameter in the JCLof the system being restarted to match that of thecheckpointed RSE name.

Problem determination5, 8 (for both the failing system and the system beingrestarted)


DFS3869I THE ACTIVE SYSTEM MAY HAVEFAILED REASON CODE=xx.

ExplanationThe alternate system detected a potential failure ofthe active system, but the operator must approveall takeovers. This message is issued only whennonautomatic takeover has been requested byspecifying AUTO=NO in member DFSHSBxx. Theoperator must enter /SWITCH SYSTEM FORCE toenable takeover to proceed. This message is issuedevery 30 seconds, as long as the takeover remainspending.

Reason code xx is defined below. The codes can beissued by themselves, or in combination. For example,X'82' combines X'80' and X'02'.Code (hex)

Meaning02

ESTAE exit entered04

IRLM failure08

/SWITCH entered10

LOG surveillance20

System LNK surveillance40

Restart data set (RDS) surveillance

80VTAM termination

System actionThe alternate system continues tracking the activesystem.

Operator responseEnter the /SWITCH SYSTEM FORCE command if youwant takeover to continue.

DFS3870I RDS|LNK|LOG INTERVAL VALUEHAS BEEN FORCED TO nnn

ExplanationThe interval values for restart data set (RDS), LNK,or LOG surveillance specified on the alternate systemwere less than the interval values specified on theactive system. The alternate interval values must begreater than or equal to the active interval values. Theinterval values are checked during the synchronizationphase, and when an interval value is changed on theactive system and a type X'6D' record is written to thesystem log.

User response:Check the interval values.

DFS3871I JOINAVM WAS SUCCESSFUL

ExplanationIn an XRF complex or a Fast Database Recoveryenvironment, the connection with the z/OScomponent, the Availability Manager, was establishedsuccessfully with the JOINAVM call.



DFS3872I AVM CONNECTION FAILED

ExplanationIn an XRF complex or a Fast Database Recoveryenvironment, the connection with the z/OScomponent, the Availability Manager, failed. AVMfunctions such as I/O prevention is not performedduring a takeover.








DFS3873I JOINRSE MODE=ACTIVE|BACKUPWAS SUCCESSFUL

ExplanationAn IMS system was successfully registered with theAvailability Manager as either the active system or thealternate (backup) system of an XRF complex. To theAvailability Manager, the XRF-capable IMS system is arecoverable service element (RSE) consisting of bothan active system and an alternate system. The name ofthe RSE that this IMS system is "joining" can be foundon the RSENAME parameter in the DFSHSBxx memberof PROCLIB.

In a Fast Database Recovery environment, thesubsystem name of the active IMS is used as theRSE. When an IMS system that is enabled for FastDatabase Recovery issues this message, it is ready forI/O prevention invocation. The Fast Database Recoveryregion does not issue this message.



DFS3874I LEAVERSE MODE=IOP|TAKEOVERWAS ISSUED

ExplanationThe Availability Manager was notified that the IMSsystem issuing this message is no longer consideredpart of the XRF recoverable service element (RSE).The name of the RSE can be found on the RSENAMEparameter in the DFSHSBxx member of PROCLIB. In

an FDBR environment, the subsystem name of theactive IMS is used as the RSE.

When this message is issued by the active IMS, I/Oprevention or Takeover was requested.



DFS3875I LEAVEAVM MODE=NORMAL|ABEND WAS ISSUED

ExplanationA LEAVEAVM call with normal mode or abnormal modewas issued to reset the connection with the availabilitymanager.



DFS3876 AVM I/O COMPLETEDUNSUCCESSFULLY

ExplanationThe I/O request against the availability managercompleted unsuccessfully.





DFS3877I JOINRSE FAILED


ExplanationThe IMS system failed to register as either the activesystem or the alternate system of an XRF complex. Thename of the recoverable service element (RSE) can befound on the RSENAME parameter in the DFSHSBxxmember of PROCLIB.

In a Fast Database Recovery environment, thesubsystem name of the active IMS is used as the RSE.When this message is issued by the active IMS, I/Oprevention is not invoked in case of IMS failure. TheFast Database Recovery region does not issue thismessage.





DFS3878I AVM RECEIVE THREADINITIALIZATION FAILED

ExplanationThe ITASK creation for the availability managerRECEIVE THREAD failed.





DFS3879I RDS|LNK|LOG INTERVAL VALUEHAS BEEN FORCED TO MINIMUM

ExplanationEither an interval value of 0 or no interval valuewas defined for restart data set (RDS), LNK, orLOG surveillance. A value of 1 is set during systeminitialization.

User response:Check the interval value.

DFS3880I RDS|LNK|LOG TIMEOUT VALUEHAS BEEN FORCED TO MINIMUM

ExplanationA timeout value of 0, 1, or no timeout value wasdefined for restart data set (RDS), LNK, or LOGsurveillance.

System action:A value of 2 is set during system initialization.

User response:Check the timeout value.

DFS3881I RDS|LNK|LOG TIMEOUT VALUEHAS BEEN FORCED TO nnn

ExplanationThe timeout values for restart data set (RDS), LNK, orLOG surveillance on the alternate system were lessthan twice the interval values. The timeout value wasforced to nnn. Values are checked for validity duringthe synchronization phase, and when the timeoutvalue or the interval value on the active system ischanged and a type X'6D' record is written to the log.

User response:Check the timeout values.

DFS3882I DEPENDENT REGIONPROCESSING ENABLED

ExplanationIf critical event messages were requested in theKEYEVENT parameter in the DFSHSBxx member ofPROCLIB, this message is sent when transactionprocessing in the IMS-dependent regions is enabled.

System actionTakeover processing continues.


DFS3883I ALL BACKOUTS COMPLETE


ExplanationIf critical event messages were requested in theKEYEVENT parameter in the DFSHSBxx member ofPROCLIB, this message is sent when all restartdynamic backouts for all accessible databases havecompleted. All databases that were not accessible arestopped.


Programmer responseTake one of these actions:

• Enter the LIST.DB ALL command to determinewhich databases have the backout-needed flag on.

• Enter the DISPLAY DATABASE command with theBKERR parameter to determine which databaseswere not backed out.

DFS3884I NO BACKOUTS NEEDED

ExplanationIf critical event messages were requested in theKEYEVENT parameter in the DFSHSBxx member ofPROCLIB, this message is sent if restart dynamicbackouts are not needed.



DFS3885I NO FAST PATH FORWARDRECOVERY NEEDED

ExplanationIf critical event messages were requested in theKEYEVENT parameter in the DFSHSBxx member ofPROCLIB, this message is sent if Fast Path forwardrecovery is not needed.



DFS3886I FAST PATH FORWARD RECOVERYCOMPLETE

ExplanationIf critical event messages were requested in theKEYEVENT parameter in the DFSHSBxx member ofPROCLIB, this message is sent when Fast Path forwardrecovery processing has completed.



DFS3887I IRLM TAKEOVER ISSUED

ExplanationIf critical event messages were requested in theKEYEVENT parameter in the DFSHSBxx member ofPROCLIB, this message is sent when IRLM TAKEOVERis issued.



DFS3888I NORMAL IRLM OPERATIONRESUMED

ExplanationIf critical event messages were requested in theKEYEVENT parameter in the DFSHSBxx member ofPROCLIB, this message is sent when normal IRLMoperation has resumed following an IRLM PURGETAKEOVER.



DFS3889A SYSTEM DATA SETSINCONSISTENT DDNAME-NNNNNNNN, RC=xx

ExplanationWhile processing an X'4001' log record from theprevious (or active) IMS system during a normal or anemergency restart, a conflict was detected between a


data set name and volume in the previous (or active)system and a data set name and volume in the restartsystem.Code (hex)

Meaning04

During a normal or an emergency restart of theactive system, the DSNAMES or VOLIDs used weredifferent. They must be the same unless a coldstart or a BLDQ option is specified.

08During an emergency restart, the number of datasets for the short and long message data sets mustbe consistent. If a change is required, either a coldstart or the BLDQ option is required.

0CDuring an emergency restart in an XRFenvironment, the Queue Manager System DataSets (qblks-shmsg-lgmsg) for the backup systemwere different. They must be different than theSystem Data Sets used by the active system.

10During an emergency restart in an XRFenvironment, the system data sets for the backupsystem online change and restart data set weredifferent. They must be the same as the activesystem.



Programmer responseCorrect the JCL so that the ddname given in themessage is no longer in conflict.


DFS3890I TAKEOVER REQUESTED REASONCODE=rc

ExplanationThe alternate system sends this message when itdetermines that a takeover should occur. The reasoncodes (rc) are:Code (hex)

Meaning80

VTAM termination

40Restart data set (RDS) surveillance

20System LNK surveillance

10LOG surveillance

08/SWITCH entered

04IRLM failure

02ESTAE exit entered

These reason codes can be issued by themselves or incombination. For example, X'82' combines X'80' andX'02', VTAM termination and ESTAE exit entered.

System actionTakeover processing begins.


DFS3891I TAKEOVER IN PROGRESS

ExplanationThe alternate system sends this message after the IMSsystem log from the active system has been processedby the alternate system.



DFS3892 WAITING FOR I/O PREVENTIONTO COMPLETE

ExplanationTakeover by the alternate system cannot proceed untilI/O prevention on the active system has completed.

System actionThe alternate system is waiting to be notified that I/Oprevention is complete in the active system: eitherthe response /UNLOCK to message AVM005A or the /UNLOCK SYSTEM command from the alternate systemMaster Terminal Operator (MTO).

Operator response:



(master terminal) Make sure that the failing systemcan no longer generate I/O requests. When this istrue, the alternate system MTO can either enter the /UNLOCK SYSTEM command or reply /UNLOCK to theMVS AVM message to allow takeover to proceed.


DFS3893I F NET, USERVAR, ID=varname,VALUE=value FAILED WITHRTNFDBK=nnnn, SENSE=mmmm

ExplanationA MODIFY USERVAR command resulted in anunexpected return code from VTAM. The followinginformation is given in the message:nnnn

Hexadecimal value of RPLRTNCD/RPLFDB2 fieldsof RPL

mmmmHexadecimal value of RPLSSNSI field of RPL

System actionThe IMS XRF system continues.


System programmer responseThe return codes are explained in z/OSCommunications Server SNA Programming(SC31-8829) and VTAM Messages and Codes(SC31-6418). Also, verify that SPO (Secondaryprogram operator) or PPO (Primary program operator)is specified in the VTAM definition library for thisapplication.

Related referencez/OS: RPL return code (RTNCD,FDB2)combinations

DFS3894I THE HOTID FOR THE XRFPRIMARY AND THE ALTERNATECANNOT BE EQUAL

ExplanationThis message is issued only by an IMS alternatesystem during the synchronization phase of an XRFcomplex. The HSBID parameter of the alternatesystem is compared to the HSBID parameter of theprimary system. (The HSBID parameter is referred to

in the message text as the HOTID parameter.) TheseIDs must be different. The HSBID for the alternatesystem is obtained from the initialization JCL; theHSBID for the primary system is obtained from thecheckpoint SNAPQ currently being read.

System actionThis message precedes a 3141 abend.

Programmer responseThere are three possible causes and solutions for thisproblem.

• The primary system JCL has been submitted on thealternate central processor complex (CPC). Submitthe correct job.

• The primary/alternate HSBIDs have been changed.Correct the HSBID parameters.

• The active system has not taken a checkpoint sincea takeover occurred. Enter a /CHE SNAPQ commandon the active system.


DFS3895 TAKEOVER OCCURRED - NO REPLYAVAILABLE

ExplanationAnother system was to process a front-end switchmessage entered at a terminal. The reply is lostbecause takeover occurred before the reply arrived.

System actionIf the reply comes after takeover, the reply message isnot sent to the terminal.

User responseReenter the input message.

DFS3896I ATTEMPTING TO PURGE OLDSBUFFERS

ExplanationIMS is beginning to purge the OLDS buffers.

System actionThe system attempts to purge the OLDS buffers. Ifthe purge is successful, message DFS616I, OLDSBUFFERS SUCCESSFULLY PURGED, is printed, andIMS termination continues. If the purge fails, messageDFS616I, OLDS BUFFER PURGE FAILED, is printed,





and the termination of IMS continues. If one of thesemessages does not appear immediately, the failedactive system is probably hanging on the reserve of theOLDS by the alternate system. No further action occursuntil the system is canceled again.

Programmer responseIf this message is followed by message DFS616I,no operator intervention is required. If the systemhangs, the operator must issue a second cancel, whichresults in I/O Prevention and the continuation of IMStermination.

Module:DFSFDLF0

Related information“DFS616I” on page 219SYSTEM LOG DATASET NOT CLOSED- LOGWRITE ERROR

DFS3897W SCP LEVEL MUST BE AT LEASTMVS/XA 2.1.3 - NO XRFCAPABILITY

ExplanationThe z/OS level you are running is not capable ofsupporting XRF. This message was generated becausethis IMS system was defined with XRF. If the SCP levelis 2.1.3, be sure that the availability manager is systemdefined with z/OS.



Programmer responseIf XRF capability is wanted, re-IPL with the correctlevel of z/OS.

DFS3898W NO HSB PROCLIB MEMBER - NOXRF CAPABILITY

ExplanationThe data set defined by the PROCLIB DD statementdid not contain the member DFSHSBxx, whichprovides the XRF parameters for the IMS system.



Programmer responseIf XRF capability is wanted, create a PROCLIB data setmember called DFSHSBxx.

DFS3899W HSBID NOT SPECIFIED IN EXECPARM - NO XRF CAPABILITY

ExplanationAn IMS system is not XRF-capable unless the HSBIDparameter is specified in the EXEC parameter of thecontrol region. Only a value of 1 or 2 is accepted.Processing with XRF capability is bypassed.



DFS3900I DFSACCS0 PARAMETER ERROR,nnnnnnnn, cccccccc

ExplanationThe IMS Offline Dump Formatter storage accessmodule (DFSACCS0) detected an invalid storageaccess request parameter: The variable nnnnnnnnis the invalid parameter field name; cccccccc is theinvalid parameter field.

System actionDFSACCS0 does the following:

1. Issues this message.2. Calls DFSATRY0 to issue message DFS2400I.3. Snaps the formatter control blocks.4. Returns to the formatter retry routine with storage

access return code 12.

User responseUse the diagnostic output to determine the cause ofthe problem.




DFS3901W IMS DUMP REQUEST ERROR- INVALID PARAMETER,aaaaaaaa,bbbbbbbb

ExplanationThe IMS dump assist module (DFSFDMP0) detectedan invalid IMS memory dump request parameter whileanalyzing the DFSDPARM control block passed witha DFSDUMP request. Either the error initiating thememory dump request or an IMS internal error mighthave caused this memory dump request error: Thevariable aaaaaaaa is the invalid parameter field name;bbbbbbbb is the invalid parameter field.

System actionDFSFDMP0 ignores the error field contents andcontinues with the IMS memory dump request.

Operator responseYou do not need to act immediately, but tell the IMSsystem programmer that you received this message.

DFS3902W IMS DUMP REQUEST ERROR-INVALID CALLER TYPE, xx

ExplanationThe caller type passed to the IMS memory dump assistmodule (DFSFDMP0) in the DFSDPARM control blockfor an IMS memory dump request was invalid. Thehexadecimal field xx identifies the caller type. One ofthe following conditions caused this error:

• The level of DFSOFMD0 was not the same as thelevel of the DFSDUMP macro and the DFSDPARMcontrol block.

• The DFSDPARM control block was overlaid.• The IMS memory dump requester did not use the

DFSDUMP macro to insert the caller ID field in theDFSDPARM control block.

System actionDFSFDMP0 creates a memory dump of the caller'saddress space and the control region address spaceonly.


DFS3903W IMS DUMP REQUEST ERROR -INVALID DUMP TITLE LENGTH, yy

ExplanationThe IMS dump assist module (DFSFDMP0) detectedan invalid memory dump title length while processingan IMS memory dump request. The length precedesthe actual title and cannot exceed 98 decimal bytes,excluding the length byte. Field yy shows the invalidlength.

System actionDFSFDMP0 uses the first 98 bytes of the title andcontinues processing.


DFS3904I A DUPLICATE DUMP WASSUPPRESSED BY DAE

ExplanationThe IMS dump assist module (DFSFDMP0) received areturn code of X'08' with a reason code of X'0B' fromSDUMP while processing an IMS DUMP request.

System actionThe operating system did not take an SDUMP. IMSdoes not retry the memory dump.


DFS3905W IMS DUMP REQUEST ERROR -t SDUMP PROCESSING ERROR,RC=r-ccc

ExplanationThe IMS dump assist module (DFSFDMP0) received anonzero return code from SDUMP while processing an


IMS SDUMP request. The meanings of the variablesare:t

P or S, indicating whether the request was aprimary or secondary SDUMP request

rSDUMP return code

04=partial memory dump created08=no dump created

cccThe reason code taken from SDUMP (the value isUNK, if no reason code was available). For a partialmemory dump (return code=04), the value of ccc isN/A. In this case, obtain the reason code from z/OSmessage IEA911E or IEA611E.

System actionIf this is the primary SDUMP request (t=P), IMS retrieswith a secondary SDUMP for the following conditions:

• A partial memory dump was created (return code 4)which was not due to a QUIESCE=YES request thatcould not be honored.

• No memory dump was created (return code 8), butthe reason code is one of the following: 001, 255,005 through 009. A retry is not attempted if theinternal parameter list passed by the caller of thedump assist routine specifies no secondary memorydump.

If the secondary SDUMP fails, this message is issuedwith (t=S) when the SDUMP return code is 4; orwhen the reason code does not indicate that theSVC memory dump was suppressed either becauseof another SVC dump in progress or because aSYS1.DUMP data set was unavailable.

When both SDUMP requests fail, IMS online memorydump formatting is permitted if the FMTO parameteryou specified allows it.

Operator responseSee the SDUMP message issued before this messageto determine if any action must be taken. Make surethat the dump produced is processed according toyour installation procedures.

Related referencez/OS: SDUMP return and reason codes

DFS3906A REPLY "S" TO SKIP, OR "U" TORETRY AFTER CLEARING A DUMPDATA SET

ExplanationAn IMS SDUMP request failed because all systemmemory dump data sets are currently full.

System actionThe operating system did not create an SDUMP.

IMS waits for the operator to respond.

Operator responseYou can retry the request, skip taking a memory dump,or reissue the equivalent of a primary memory dump.

To retry the SDUMP request, clear one or morememory dump data sets and reply U.

To skip creating a memory dump, reply S, but be awarethat IMS does not try to create any more SDUMPs forthis IMS error.

To reissue the equivalent of the primary SDUMPrequest, enter an operator DUMP command for the IMSCTL, DL/I, DBRC, and IRLM address spaces; then replyS to the message you receive.

If the FMTO parameter specified allows onlineformatting, and if you replied S, online formatting canbe initiated.

Related informationDFS3906IDFSDUMP FAILED BECAUSE ALL SYSTEM DUMPDATA SETS ARE FULL

DFS3906I DFSDUMP FAILED BECAUSE ALLSYSTEM DUMP DATA SETS AREFULL

ExplanationFor a detailed explanation and actions, see DFS3906A

Related informationDFS3906AREPLY "S" TO SKIP, OR "U" TO RETRY AFTERCLEARING A DUMP DATA SET

DFS3907A REPLY "S" TO SKIP, OR "U" TORETRY AFTER CURRENT DUMPCOMPLETES.

ExplanationAn SDUMP for another task not belonging to this IMSsystem was being taken at the time the SDUMP wasissued.



System actionThe operating system did not satisfy the IMS SDUMPrequest because it can create only one SDUMP at atime.

IMS action: IMS waits for the operator to respond.

Operator responseIf you receive one of the following messages, reply "U"to retry the SDUMP request:

IEA911E COMPLETE DUMP ON SYS1.DUMPxx.... orIEA911E PARTIAL DUMP ON SYS1.DUMPxx.....

If you are not sure if the current memory dump hascompleted, reply U. IMS reissues message DFS3907Aif the current memory dump has not completed.

If you want to skip taking a memory dump, reply S.However, be aware that IMS does not try to createany more SDUMPs for the current error. IMS triesto produce alternative diagnostic information (suchas online memory dumps, spin-off memory dumps,software LOGREG entries, and dependent regionmemory dumps).

Related informationDFS3907IDFSDUMP FAILED BECAUSE A DUMP IS INPROGRESS.

DFS3907I DFSDUMP FAILED BECAUSE ADUMP IS IN PROGRESS.

ExplanationFor a detailed explanation and actions, see DFS3907A

Related informationDFS3907AREPLY "S" TO SKIP, OR "U" TO RETRY AFTERCURRENT DUMP COMPLETES.

DFS3908E ABEND code IN OTMA SVCINIT MODULE DFSYSVI0,PSW=psw1psw2

ExplanationAn abend occurred while module DFSYSVI0 wasin control. Module DFSYSVI0 is the module thatinitializes the OTMA Callable Services SVC service, andis typically run as a stand-alone job before runningapplications that use the OTMA Callable Services.DFSYSVI0 processing is protected by an internalESTAE, which attempts to retry from the abend and

clean up any global resources (such as commonstorage) that DFSYSVI0 obtained. This message isissued to alert the operator that an abend occurred.

In the message text:code

The abend code. For system abends, the format ofcode is Sxxx, where xxx is the 3-digit abend code inhexadecimal. For user abends, the format of codeis Udddd, where dddd is the 4-digit abend code indecimal.

psw1The first word of the PSW at abend.

psw2The second word of the PSW at abend.

System actionThe DFSYSVI0 ESTAE collects diagnostic data aboutthe abend, and then resumes execution in a cleanuproutine within DFSYSVI0. This routine attempts torelease any global resources that DFSYSVI0 obtainedas a part of its processing. DFSYSVI0 then issuesmessage DFS3911E and returns to its caller. Typically,unless the abend occurred at the very end ofDFSYSVI0 processing, the OTMA SVC routine is notinitialized.

The first time that DFSYSVI0 abends, its ESTAEcreates an SDUMP of the address space, and causesa record to be written to the SYS1.LOGREC data setto document the abend. If DFSYSVI0 abends a secondtime or more (within one execution), its ESTAE doesnot create another SDUMP. However, it does writeanother record to SYS1.LOGREC.

System programmer responseSave any memory dump, SYSLOG, and SYS1.LOGRECinformation and contact IBM Software Support.

Module:DFSYSVI0

Related information“DFS3911E” on page 1122ERROR INITIALIZING OTMA SVC - details

DFS3909A CQS SUBSYSTEM IS UNAVAILABLEFOR <MSGQ|EMHQ> - REPLYRETRY WHEN READY OR ABORTTO TERMINATE IMS

ExplanationDuring an IMS restart, an unsuccessful attempt wasmade to resynchronize with the CQS subsystem for theshared queues structures identified in the message.The CQS subsystem was unavailable.


System actionIMS waits for the reply to this message. If the reply isRETRY, IMS attempts to connect to CQS. If the replyis ABORT, IMS terminates with abend 0231, returncode 01. This message is reissued if the reply is notrecognized.

Operator responseEither enter RETRY when CQS is ready or ABORTto terminate IMS. This message can be issued forthe message queue (MSGQ) and for the expeditedmessage handler queue (EMHQ).

Module:DFSRLP00 (for MSGQ), DBFHCAS0 (for EMHQ)


DFS3910I IMS IN A SHARED QUEUEENVIRONMENT IS UNABLE TORESYNC WITH CQS

ExplanationDuring a warm or emergency restart, IMS failed toresynchronize with the CQS subsystem.

System actionIMS terminates with abend 0231-xx. See abend 0231for an explanation of subcode xx.

User responseCorrect the identified error and restart IMS.

Module:DFSRST00, DFSRLP00


DFS3911E ERROR INITIALIZING OTMA SVC -details

ExplanationAn error occurred in module DFSYSVI0. DFSYSVI0 isthe module that initializes the OTMA Callable ServicesSVC service, and is typically run as a stand-alonejob before running applications that use the OTMACallable Services. When DFSYSVI0 cannot completethe OTMA callable services initialization, it issuesmessage DFS3911E to indicate why initializationfailed.


detailsA short summary of the reason why the OTMACallable Services SVC initialization failed. detailscorresponds with the return code issued by theDFSYSVI0 module, and might be one of thefollowing codes:NOT EXECUTING IN PSW KEY 7

DFSYSVI0 was not given control in PSW key 7.DFSYSVI0 must run as an authorized programin PSW key 7. Add DFSYSVI0 to the programproperties table. See IMS Version 15 SystemProgramming APIs for instructions.

ESTAE CREATE FAILED, RC=rcDFSYSVI0 attempted to establish a z/OSrecovery routine (ESTAE), but the create ESTAEcall failed. rc is the return code from the MVSESTAE macro.

BPESVC INIT FAILED, RC=rcDFSYSVI0 could not initialize the BPE SVCservice. rc is the return code from the BPESVCinitialization call.

BLDL FOR DFSYSVC0 FAILED, RC=rcAn MVS BLDL call for module DFSYSVC0 failed.Ensure that DFSYSVC0 is included in the libraryfrom which you are running DFSYSVI0. rc is thereturn code from the MVS BLDL macro call.

GET FOR STORAGE FAILED, RC=rcDFSYSVI0 could not get storage required forthe OTMA Callable Services SVC module. rc isthe return code from the MVS STORAGE macrocall.

LOAD FOR DFSYSVC0 FAILED, RC=rcAn MVS LOAD call for module DFSYSVC0 failed.rc is the return code from the MVS LOAD macrocall.

BPESVC REGISTRATION FAILED, RC=rcRegistration of the OTMA Callable ServicesSVC routine with BPESVC (BPE SVC services)failed. rc is the return code from the BPESVCREGISTER macro call.

ABEND OCCURRED DURING INITIALIZATIONAn abnormal termination occurred duringDFSYSVI0 processing. This message can bepreceded by a DFS3908E message indicatingthe abend code and PSW, and by an SDUMP ofthe address space of the DFSYSVI0 job.

System actionModule DFSYSVI0 terminates. The OTMA CallableServices SVC is not initialized (or, if it was previouslyinitialized, is not replaced).




System programmer responseFor environmental errors (such as DFSYSVC0 notbeing in the same library as the one from which youare running DFSYSVI0), correct the error and rerunDFSYSVI0. For NOT EXECUTING IN PSW KEY 7 error,ensure that the library where DFSYSVC0 resides is APFauthorized. For other problems contact IBM SoftwareSupport.

Module:DFSYSVI0

Related referenceBPESVC codes (Messages and Codes)z/OS: ESTAE return and reason codesz/OS: BLDL completion codesz/OS: STORAGE OBTAIN return and reasoncodesz/OS: LOAD return and reason codesRelated information“DFS3908E” on page 1121ABEND code IN OTMA SVC INIT MODULEDFSYSVI0, PSW=psw1psw2

DFS3912W IMS DUMP FORMAT CONTROLPARAMETER ERROR, cccccccc

ExplanationIMS Offline Dump Formatter initialization (DFSOFMD0)did not recognize or process option cccccccc in thememory dump format control data set.

System actionDFSOFMD0 continues scanning the format options,ignoring the invalid options. If more than 3 invalidoptions are detected, DFSOFMD0 closes the memorydump format control data set and processes any validoptions received.

User responseCorrect the invalid options by ensuring that:

• The option is correctly spelled.• The option has only one qualifier (although the

option can be repeated.)

Then rerun the memory dump formatting job forthese options. This message is followed by messageDFS3913I, which indicates whether IMS offlineformatting will continue.

Related information“DFS3913I” on page 1123IMS DUMP FORMATTING DISCONTINUED

DFS3913I IMS DUMP FORMATTINGDISCONTINUED

or

IMS DUMP FORMATTING CONTINUING

ExplanationThis message indicates whether IMS offline memorydump formatting is continuing after a previous error.

System action:IMS offline dump formatting either continues or stops.

User responseIf offline memory dump formatting stopped, correctthe errors based on previous messages, and rerun theformatting job for any options that did not format.

DFS3914I IMS DUMP FORMATTER BUFFERCONTROL BLOCK INTERNALERROR DETECTED

ExplanationOne of the following internal IMS Dump Formatterprocessing errors (related to IMS dump storagebuffers) occurred:

• The memory dump storage buffer prefixes wereoverlaid.

• IMS memory dump formatting was interrupted whileprefix rechaining was in progress.

• An error occurred in the IMS memory dump formatstorage access routine.

System actionIMS snaps the memory dump formatter control blocksand then returns control to AMDPRDMP/IPCS withRC=8.

User responseUse the diagnostic output to determine the cause ofthe problem.

DFS3915I GETMAIN FAILED FOR AN IMSFORMATTING DUMP BUFFER.

or


http://www.ibm.com/support/knowledgecenter/SSEPH2_15.1.0/com.ibm.ims15.doc.msgs/compcodes/bpesvc.htm#bpesvc

https://www.ibm.com/support/knowledgecenter/SSLTBW_2.2.0/com.ibm.zos.v2r2.ieaa700/iea3a7_Description17.htm





FREEMAIN FAILED FOR AN IMS FORMATTING DUMPBUFFER.

ExplanationThe IMS Dump Formatter was unable to get or freestorage for IMS memory dump storage buffers.

System actionAfter a GETMAIN or FREEMAIN failure, the PrintService Routine prints a SNAP of the memorydump formatting control blocks, IMS memory dumpformatting terminates, and AMDPRDMP receivescontrol with RC=4.

User responseIf the error occurred during a FREEMAIN, use thediagnostic output to determine the cause of theproblem. If the error occurred during a GETMAIN,rerun the job with a larger region size.

DFS3916W RC=01,DFSOFMD0 UNABLE TOGETMAIN STORAGE FOR -REGISTER SAVEAREA

or

RC=02, DFSOFMD0 UNABLE TO GETMAIN STORAGEFOR - COMMUNICATION AREA

or

RC=03, DFSOFMD0 UNABLE TO GETMAIN STORAGEFOR - DUMP BUFFER PREFIXES

or

RC=04, DFSOFMD0 UNABLE TO GETMAIN STORAGEFOR - DUMP BUFFERS

or

RC=06, DFSOFMD0 UNABLE TO GETMAIN STORAGEFOR - RELOCATED SCD

ExplanationIMS Offline Dump Formatter initialization (DFSOFMD0)received a nonzero return code from GETMAIN while

trying to get storage for a required IMS offline memorydump formatting control block.

System actionThe memory dump formatter is unable to continue andreturns control to AMDPRDMP with RC=4.

User responseIncrease the storage provided for AMDPRDMP; thenrerun the failing job. If the problem continues, notifyyour IMS system programmer.

DFS3917W RC=07, DFSOFMD0 UNABLE TOGETMAIN STORAGE FOR - IMSDUMP FORMATTER MODULES.

ExplanationIMS Offline Dump Formatter initialization (DFSOFMD0)was unable to get storage needed to relocate the IMSOffline Dump Formatter modules.

System actionDFSOFMD0 tries to load the needed modules fromcurrent libraries to continue processing.

User responseIf you want to format the memory dump using theOffline Dump Formatter modules in the memory dump,increase the storage provided for AMDPRDMP, andrerun the job. If the problem continues, check theDFSAVECT vector table control block to make sure thatit was not overlaid. The address of this control blockis at the beginning of load module DFSABND0, whichis pointed to by field SCDCABN0 or SCDDABN0 in theSCD.

If you do not want to use the IMS OfflineDump Formatter modules in the memory dump forformatting, make sure that the Offline Dump Formattermodules are available in load module DFSABND0.

For more help, contact the IMS system programmer.

DFS3918W RC=05, DFSOFMD0 UNABLE TOGETMAIN STORAGE FOR -RELOCATED FP ESCD.

or

RC=08, DFSOFMD0 UNABLE TO GETMAIN STORAGEFOR - RELOCATED CBT HEADER


or

RC=10, DFSOFMD0 UNABLE TO GETMAIN STORAGEFOR - RELOCATED CBT TABLE

or

RC=310, DFSOFMD0 UNABLE TO GETMAINSTORAGE FOR - FAST PATH EPST WORK BUFFER

ExplanationIMS Offline Dump Formatter initialization (DFSOFMD0)was unable to get storage needed to relocate the FastPath ESCD, the Fast Path work buffer, Control BlockTable Header, or the Control Block Table (CBT). TheIMS Offline Dump Formatter is unable to format theCBT or CBTE subset options or any other option thatuses CBT FIND services to locate control blocks.

System actionIMS memory dump formatting continues, but Fast Pathcontrol blocks are not formatted.

DFSOFMD0 disables all CBT use and continues withIMS Offline Dump Formatter initialization.

User responseIncrease the storage provided for AMDPRDMP andrerun the job. If the problem continues, notify yourIMS system programmer.

DFS3919W RC=rc, reason_test

ExplanationIMS Offline Dump Formatter initialization (DFSOFMD0)was attempting to locate the SCD with the TCBFSApointer, but was unable to access the needed dumpstorage. This situation might be the result of using aninvalid or incomplete dump, or by specifying an invalidIMS job name.

In the message text, rc and reason_test can be one ofthe following values:

• RC=00, UNKNOWN ERROR• RC=01, RESERVED FOR FUTURE USE• RC=02, RESERVED FOR FUTURE USE• RC=03, UNABLE TO FIND IMS SCD• RC=04, DUMP BUFFERS• RC=05, RELOCATED FP ESCD• RC=06, RELOCATED SCD

• RC=07, DUMP FORMATTER MODULES• RC=08, RELOCATED CBT HEADER• RC=09, SAP SORT WORK AREA• RC=10, RELOCATED CBT TABLE• RC=11, DFSOFMD0 ENCOUNTERED ERROR WITH

DUMP - UNABLE TO FIND CVT• RC=13, DFSOFMD0 ENCOUNTERED ERROR WITH

DUMP - UNABLE TO FIND JESCT• RC=14, DFSOFMD0 ENCOUNTERED ERROR WITH

DUMP - UNABLE TO FIND SSCT• RC=27, DFSOFMD0 ENCOUNTERED ERROR WITH

DUMP - UNABLE TO FIND ASVT• RC=45, DFSOFMD0 ENCOUNTERED ERROR WITH

DUMP - UNABLE TO FIND IMS TCB

System actionIMS Offline Dump Formatting terminates.

User responseBe sure that you are using the correct level ofDFSOFMD0. If you are using a SYSMDUMP, anoperator-requested dump, or a stand-alone dump,check with the system programmer that all necessarystorage areas are being dumped. If the problemcontinues, notify your IMS system programmer.

DFS3920W RC=15, DFSOFMD0ENCOUNTERED ERROR WITHDUMP - UNABLE TO FIND CBTHEADER

or

RC=18, DFSOFMD0 ENCOUNTERED ERROR WITHDUMP - UNABLE TO FIND CBT TABLE

or

RC=25, DFSOFMD0 ENCOUNTERED ERROR WITHDUMP - UNABLE TO FIND FP ESCD

ExplanationIMS Offline Dump Formatter initialization (DFSOFMD0)was unable to find the IMS CBT control blocks or theFast Path ESCD control block in the dump.


System actionIMS dump formatting continues with all Fast Path-related formatting or CBT-related services aredisabled.

User responseCheck that you are using a level of DFSOFMD0compatible with the level of your IMS system. If youare using a SYSMDUMP, an operator-requested dump,or a stand-alone dump, check with your z/OS systemprogrammer to be sure that all necessary storageareas are being dumped. If the problem continues,notify your IMS system programmer.

DFS3921W RC=26, DFSOFMD0ENCOUNTERED ERROR WITHDUMP - UNABLE TO FINDDFSABND0

ExplanationIMS Offline Dump Formatter initialization (DFSOFMD0)was unable to find the named module in the dump.

System action:DFSOFMD0 tries to load a new copy of the namedmodule from current libraries to continue processing.

User responseIf you are using a SYSMDUMP, an operator-requesteddump, or a stand-alone dump, check with your z/OSsystem programmer to ensure that all necessarystorage areas are being dumped. Then examine thedump to be sure that IMS was not in early initializationor late termination. For additional help, see your IMSsystem programmer.

DFS3922W RC=16, DFSOFMD0 LOAD FAILEDFOR - LOAD MODULE DFSABND0,ENTRY POINT = DFSABND0

ExplanationIMS Offline Dump Formatter initialization (DFSOFMD0)was unable to load new copies of the IMS OfflineDump Formatter modules from current librariesbecause the dump formatter load module was missingor did not contain a DFSABND0 entry point.

System actionIMS offline dump formatting stops, and control isreturned to AMDPRDMP with RC=8.

System programmer responseBe sure that DFSABND0 is available for the correctIMS release and is correctly bound with an entry pointof DFSABND0.

User responseUse the IMS dump formatter modules in the dump, ormake sure that load module DFSABND0 is available inthe current libraries; then rerun the job.

DFS3923I OTMA SVC INITIALIZATIONCOMPLETE - DFSYSVC0A=xxxxxxxx L=yyyyyyyy

ExplanationModule DFSYSVC0 was successfully loaded andregistered with BPE.


The address where DFSYSVC0 was loadedyyyyyyyy

The length of module DFSYSVC0

System actionDFSYSVC0 is successfully loaded and registered withBPE.



Module:DFSYSVI0

DFS3924W RC=19, DFSOFMD0 ERROR WITHDFSFRMAT DATA SET- UNABLE TOFIND DD STMNT

or

RC=20, DFSOFMD0 ERROR WITH DFSFRMAT DATASET - UNABLE TO OPEN DATA SET

or


RC=21, DFSOFMD0 ERROR WITH DFSFRMAT DATASET - READ/CHECK FAILED

or

RC=36, DFSOFMD0 ERROR WITH DFSFRMAT DATASET - "FMTIMS" KEYWORD NOT FOUND

or

RC=41, DFSOFMD0 ERROR WITH DFSFRMAT DATASET - RECFM FORMAT INVALID

or

RC=42, DFSOFMD0 ERROR WITH DFSFRMAT DATASET- LRECL/BLKSIZE INCOMPATIBLE

ExplanationEither DFSOFMD0 was unable to find, open, orread the IMS dump format control data set, orthe DFSFRMAT DD statement or data set containedinvalid data. The specific form of the message issuedindicates the problem.

System actionIMS dump formatting continues using the SUMMARYoption.

User responseMake sure that

• A valid DFSFRMAT DD statement is included for IMSoffline dump formatting.

• The dump format control data set is present andvalid.

• The DFSFRMAT data set specifies RECFM=F orRECFM=FB with valid LRECL and BLKSIZE values.

• The FMTIMS control statement is specified first inthe DFSFRMAT data set.

For more help, contact your IMS system programmer.

DFS3925W RC=22, DFSOFMD0 AMDPRDMPPARMLIST ERROR - UNABLE TOFIND EXTENSION

or

RC=23, DFSOFMD0 AMDPRDMP PARMLIST ERROR -NO JOBNAME PARAMETER FOUND

ExplanationIMS Offline Dump Formatter initialization (DFSOFMD0)was unable to find the AMDPRDMP exit parameter listextension that contains the IMS job name required forIMS dump formatting.

System actionIMS offline formatting stops, and control is returned toAMDPRDMP with RC=8.

User responseBe sure that you have provided a valid IMSDUMP verbwith a valid job name. If the problem continues, notifyyour z/OS system programmer.

DFS3926W RC=24, DFSOFMD0 EXITPARAMETER LIST ERROR -JOBNAME IS NOT AN IMSSUBSYSTEM

or

RC=28, DFSOFMD0 EXIT PARAMETER LIST ERROR -JOBNAME ASCB NOT FOUND

ExplanationEither the address space control block (ASCB) for theIMSDUMP jobname in the AMDPRDMP exit parameterlist was missing in the current dump, or an ASCB forthe jobname was present but did not have a matchingSSCT entry for subsystem type "DB" or "DC". The errorcan happen when any of these conditions occur:

• The necessary storage was not dumped.• The jobname was incorrect.• The IMS job terminated before the memory dump

was created.• A jobname was provided for a non-IMS job.

System actionIMS dump formatting stops, and control is returned toAMDPRDMP with RC=8.

User responseBe sure that:

• You provide the correct dump.


• The IMS jobname is valid.• All necessary storage is dumped.• IMS was in the dump.• IMS was not in early initialization or late termination.

For additional help, see your z/OS system programmer.

Related referenceOffline Dump Formatter utility (DFSOFMD0)(System Utilities)

DFS3927W DFSDPARM PARAMETER LIST NOTALLOCATED, PARTIAL OFFLINEDUMP MAY RESULT.

ExplanationYou did not pass a DFSDPARM control block containingcertain DFSDUMP options to the IMS dump assistmodule (DFSFDMP0). DFSFDMP0 used the defaultoptions instead.

System actionDFSFDMP0 returns to the issuer of DFSDUMP withRC=8. SDUMP processing continues.

Operator responseNo immediate action is necessary, but tell your IMSsystem programmer that you received this message.

DFS3928W UNRECOVERABLE ERROR DURINGIMS DUMP REQUEST MAY RESULTIN NO OFFLINE DUMP.

ExplanationIMS SDUMP processing stopped because problemswere encountered during request processing in IMSSDUMP. If a memory dump was not already produced,no memory dump is created.

System actionDFSFDMP0 returns to the issuer of DFSDUMP withRC=8. Alternate online diagnostics, such as spin-off memory dumps, software LOGREG entries, anddependent region memory dumps, are allowed.

Operator responseNo immediate action is necessary, but tell the IMSsystem programmer that you received this message.

System programmer responseExamine the diagnostic output, including the LOGRECentries created for the memory dump processingerrors, to determine the cause of the problem.

DFS3929W name ADDRESS SPACE STORAGEIS NOT IN THIS DUMP

ExplanationThe private address space storage for the nameaddress space was not dumped. In the message text,name can be one of the following:

CTLDLIDBRC

System actionIMS offline memory dump formatting continues, butsome options can be bypassed, and some blocksmight not be formatted.

User responseBe sure that you provided the correct memory dump.This situation can be valid for:

• Any IMS memory dump in which the CTL, DL/I, orDBRC address space was not requested.

• SYSMDUMPs, secondary-request IMS memorydumps, operator-initiated SVC memory dumps thatdid not request the CTL or DL/I, or both, addressspaces.

• z/OS-initiated SVC memory dumps.

For more help, see your IMS system programmer.

DFS3930I DFSOFMD0 WAS NOT ASSEMBLEDAT THE SAME MVS SP LEVEL ASTHE IMS DUMPED OR THE DUMPIS NOT MACHINE READABLE

Explanationz/OS control blocks cannot be analyzed correctlybecause either the IMS Offline Dump Formatterinitialization module was not assembled at the samez/OS SP level as the dumped IMS system, or thememory dump was not machine readable, or the dataset is not a memory dump.

System actionIMS memory dump formatting is terminated.


http://www.ibm.com/support/knowledgecenter/SSEPH2_15.1.0/com.ibm.ims15.doc.sur/ims_dfsofmd0.htm#ims_dfsofmd0

http://www.ibm.com/support/knowledgecenter/SSEPH2_15.1.0/com.ibm.ims15.doc.sur/ims_dfsofmd0.htm#ims_dfsofmd0

User responseBe sure that DFSOFMD0 is assembled at the correctz/OS level for this memory dump and that the memorydump is machine readable. For more help, see yourIMS system programmer.

DFS3930W DFSOFMD0 ENCOUNTERED ERRORWITH DUMP- RC45, DFSOFMD0IMS LEVEL DOES NOT MATCHDUMP

ExplanationThe version or release level of DFSOFMD0 isincompatible with the level of IMS found in thememory dump. IMS dump formatting initializationcode must be compatible with the IMS control blocksin the memory dump. IMS Offline Dump Formatting isnot performed.

System actionMake sure that a compatible library is used and rerunthe memory dump formatting job.

DFS3931W DFSFDMP0 UNABLE TO GETSRB BLOCK STORAGE, NO IMSOFFLINE DUMP ATTEMPTED.

or

DFSFDMP0 UNABLE TO GET WORK AREA STORAGE,NO IMS OFFLINE DUMP ATTEMPTED.

ExplanationThe IMS dump assist module was unable to obtaineither private storage needed for the internal workarea or CSA storage needed for the SDUMP SRBinterface. Message DFS629I was not sent, and no IMSSDUMP memory dump was created.

System actionDFSFDMP0 returns to the issuer of DFSDUMP withRC=36. Online memory dump formatting is notsuppressed.


If the message indicates that work area storageis unavailable, tell the IMS system programmerto provide additional virtual storage for the failingaddress space. If the message indicates that SRB

block storage is unavailable, the system might needto be inspected to determine what is causing theshortage of global storage.

Related information“DFS629I” on page 225IMS ttt TCB <action> IMS|SYS sss|uuuuvvvvIMSttt TCB <action> IMS|SYS sss|uuuuvvvv

DFS3932I IMS DUMP REQUEST COMPLETED- RETURN CODE = ccc

ExplanationDFSFDMP0 completed an IMS SDUMP request. Themeanings of ccc are:00

Successful completion04

DFSDUMP parameter error; memory dump created08

No parameter list or GETMAIN failed; memorydump created

12Multiple address space identifier (ASID) dumpfailed; simple memory dump created

20DFSDUMP already in progress; no memory dumpcreated

24Dump already created or not allowed

28DFSDUMP parameter error; memory dump created

32Dump not created because operator replied 'S'(SKIP) to an operator WTOR message

36Internal processing error; no memory dumpcreated

40No dump attempted because a previous offlinememory dump failed

48SDUMP processing error; see message DFS3905Wfor a description of the SDUMP reason code.

System actionDFSFDMP0 returns to the issuer of DFSDUMP with thereturn code listed in the message.



DFS3933W THIS APPEARS TO BE ADUMP OF IMS DURING EARLYIMS INITIALIZATION. DUMPFORMATTING WILL BE ALLOWEDTO CONTINUE, BUT FORMATTINGERRORS MAY OCCUR BECAUSECONTROL BLOCKS ARE NOT FULLYBUILT.

ExplanationThe IMS Offline Dump Formatter initialization routinedetermined that one or more of the IMS addressspaces was not fully initialized so that some of the IMScontrol blocks might not be fully built and initialized.Message DFS3934W follows to indicate which IMSaddress spaces were not fully initialized.

System actionIMS memory dump formatting continues, butunpredictable formatting errors can occur.

User responseUse the formatted output with caution, rememberingthat control blocks that were not fully initialized cancontain formatting errors.

Related information“DFS3934W” on page 1130RC=38 CTL ADDRESS SPACE WAS NOT FULLYINITIALIZED.

DFS3934W RC=38 CTL ADDRESS SPACE WASNOT FULLY INITIALIZED.

or

RC=39 DL/I ADDRESS SPACE WAS NOT FULLYINITIALIZED.

or

RC=40 DBRC ADDRESS SPACE WAS NOT FULLYINITIALIZED.

ExplanationThe named IMS address space was not fully initializedwhen the memory dump was created so that some ofthe IMS control blocks in this address space might notbe fully built and initialized.

System actionIMS memory dump formatting continues, butunpredictable formatting errors can occur.

User responseUse the formatted output with caution, rememberingthat formatting errors can occur for control blocks thatwere not fully initialized.

DFS3935I IMS SYMBOL SERVICE ERROR,RC=nn

ExplanationIPCS returned a nonzero return code for an IMS createsymbol request, where nn is the IPCS symbol createservice return code.

System actionThe IMS Offline Dump Formatter proceeds with thenext IMS symbol.

User responseHowever, the noted symbol does not exist for thecurrent memory dump.

Related referencez/OS: Symbol service

DFS3936I IMS SYMBOL SERVICESUNAVAILABLE

ExplanationSymbol create services are unavailable for the currentformatting invocation. One of the other symbol serviceerror messages might precede this message.

System actionSymbol create services are unavailable for the currentformatting invocation.

User responseSee the previous symbol create service messages.

DFS3937I UNABLE TO ACCESS STORAGEWHILE FORMATTING THE ccc...ccc

ExplanationDuring memory dump formatting, an error wasencountered while attempting to access dumpedstorage. The field ccc...ccc, which can be up to 16


http://www-01.ibm.com/support/knowledgecenter/SSLTBW_2.4.0/com.ibm.zos.v2r4.hasc300/iazsymbl.htm?lang=en

bytes in length, identifies the control block or dataarea being formatted.

In an online environment, memory dump storage is inthe IMS Dump Formatter.

The most common memory dump storage accesserrors are:

• STORAGE NOT AVAILABLE. The requested storagewas not in the memory dump.

• PARTIAL STORAGE AVAILABLE. A portion of therequested storage was in the memory dump.

System actionFor most errors, a diagnostic memory dumpimmediately follows this message. This diagnosticmemory dump consists of the following:

• The contents of SDWA, which includes the PSW,completion code, module ID, registers, and amemory dump of the SDWA area.

• Instruction area, which includes 128 bytes of databefore and after the failing instruction (total of 256bytes).

• Communications area, which is the controlblock used by the IMS Dump Formatterfor intercommunication between the formattingmodules.

• Save area, which is a memory dump of the save areaset used by the memory dump formatter.

• The memory dump formatter module vector table.• Dump formatter storage buffer header and prefixes

(offline formatting only).• Dump option request block storage (offline

formatting only).

Following the diagnostic memory dump of the error,the dump formatter continues formatting the next IMScontrol block requested.

A diagnostic memory dump is suppressed when any ofthe following forms of ccc...ccc is received:

'PSB' (and there is no DL/I storage in the memorydump)'AUTO OPTION PROC' (and debug was notrequested)'ABND DIAG. AREA''SA - EP ADDRESS''SAP''ECB PREFIX''SAVE AREA''REGISTER AREA''SA - INV FWD PTR''QUEUE BUFFERS'

'UEHB''LATCH LIST''ECB STORAGE''XMCI BLOCK''USE LIST (CULE)'

User responseDespite the failure of the IMS Dump Formatter, theoutput might still provide enough information to helpyou diagnose your original problem. If the memorydump formatter output does not provide enoughinformation, contact the IMS system programmer.

Programmer responseUse the diagnostic memory dump to determine thecause of the problem. If the diagnostic memory dumpis suppressed, contact the IMS system programmer.

DFS3938W TRACE TABLE WITH NAME ccREQUESTED -- NOT FOUND

ExplanationThe requested trace table could not be found foran IMS Offline Dump Formatter TRACE request. Thisusually indicates an invalid name was requested. Thisdoes not indicate a valid trace exists and was notstarted.

System actionThe TRACE option formatter terminates the currentrequest and continues with the next trace request.

User responseEnsure that a appropriate IMS trace table name hasbeen requested. For assistance, see the IMS systemprogrammer.

Related referenceType-1 trace table interface (Diagnosis)

DFS3939I cccccccc FORMATTINGTERMINATED -- WORKAREASTORAGE UNAVAILABLE

ExplanationThe IMS Offline Dump Formatter internal work areasneeded to process the request could not be obtained,where cccccccc was the formatter option requested.An inadequate amount of storage to GETMAIN workarea space causes the failure. The message alsooccurs if more than 63 dump formatter low-level


http://www.ibm.com/support/knowledgecenter/SSEPH2_15.1.0/com.ibm.ims15.doc.dgr/ims_common_trace_table_inter.htm#ims_common_trace_table_inter.dita

option requests are made during the same formatterinvocation.

System actionThe IMS Offline Dump Formatter skips the currentrequest and attempts to process the next formattingrequest.

User responseEnsure that the IMS Offline Dump Formatter hassufficient storage and reissue the request. For TSOuse, make sure that the region size is adequate. Forbatch jobs, increase the region size and rerun the job.See the IMS system programmer for assistance.

When requesting memory dump formatter optionsfrom a user TSO CLIST facility, use no more than 63options at one invocation.

DFS3940I cccccccc FORMATTINGTERMINATED -- UNEXPECTEDDUMP STORAGE ACCESS ERROR

ExplanationThe IMS Offline Dump Formatter was unable to accessstorage while searching or processing control blocksfor the named option's request, where cccccccc wasthe formatter option requested. A nonzero return codefrom IPCS storage access service routine indicatedthis condition. One of the following caused thiscondition:

• An attempt was made to format memory dumps thatdo not contain the requested control block storage.

• Errors in the dumped storage with invalid addressesprevented the requested formatting.

• An invalid formatter request caused the formatter torequest unavailable memory dump storage.

The request header line, which contains the requestedformatter request type and argument that caused thismessage to be generated, precedes the error message.Obtain the required information by requestingthe format output with the associated high-levelformatting option, such as DC, DB, or SPST. MessageDFS3937I and a SNAP of the memory dump formatterblocks precede the error message.

System actionThe IMS memory dump formatter skips furtherrequests for the option and continues with the nextformatter option.

User responseEnsure that the storage is present (CTL, DL/I, or CSAas needed). Ensure that the formatter request wasvalid. For assistance, see the IMS system programmer.

Related information“DFS3937I” on page 1130UNABLE TO ACCESS STORAGE WHILEFORMATTING THE ccc...ccc

DFS3941I TRACE TABLE FORMATTINGTERMINATED DUE TO BAD TRACECONTROL BLOCK ADDRESS -cccccccc

ExplanationThe IMS Offline Dump Formatter found an invalid tracetable control block while processing a TRACE optionrequest, where cccccccc is the bad address.

System actionTRACE option formatting terminates, and the IMSOffline Dump Formatter continues with the nextoption.


However, some of the requested trace tables were notformatted.

DFS3942I IMS DUMP FORMAT REQUESTINCOMPLETE OR IN ERROR -cccccccc

ExplanationThe IMS Offline Dump Formatter found an error in aformat request requiring types or arguments, wherecccccccc is the text in error.

System actionThe IMS Offline Dump Formatter ignores the currentrequest, purges remaining recognizable qualifiers, andcontinues parsing the next format request.

User responseCorrect the format request error and resubmit thefailing request. For assistance, see the IMS systemprogrammer.

DFS3944I cccccccc FORMATTINGTERMINATED -- NO REQUESTCHAIN FOUND


ExplanationThe named IMS formatting option was selected, but novalid formatting requests were found, where ccccccccwas the formatter option requested.

The request header line which contains the requestedformatter request type and argument that caused thismessage to be generated precedes the error message.The argument might have been an invalid request (noARGUMENT, or invalid TYPE).

System actionThe IMS Dump Formatter skips the named optionrequests and continues with the next memory dumpformatter option.

User responseEnsure that the named option requests are valid, likethe request type, argument, and qualifier keywords.For assistance, see the IMS system programmer.

DFS3945I CLB/LLB FORMATTINGTERMINATED -- NO BLOCKSFOUND

ExplanationCLB/LLB option requests were made, but a requestedblock did not occur in the system that was dumped.The error message is issued if the dumped IMS wasdamaged, and CLB/LLB block pointers are no longervalid, or the dumped IMS was not generated to haveany of the requested blocks.

The request header line, which contains the requestedformatter request type and argument that caused thismessage to be generated, precedes the error message.

System actionThe IMS Dump Formatter skips the current requestand continues with the next request. Either CLBs existwithout LLBs, or LLBs exist without CLBs.

User responseEnsure that the CLB or LLB option requests were validand the memory dump is formatting. For assistance,see the IMS system programmer.

DFS3946I PST NOT FORMATTED --REQUESTED PST IS NOT A SYSTEMPST

ExplanationThe requested PST was not an active system PST.An invalid SYSPST request (the PST might be a DPSTinstead) caused this condition.

System actionThe SYSPST option formatter terminates the currentrequest and continues with the next request.

User responseEnsure that all SYSPST formatting requests are valid.For assistance, see the IMS system programmer.

DFS3947I cccccccc FORMATTINGTERMINATED -- UNEXPECTEDFORMATTER PROGRAM ERROR

ExplanationThe IMS Offline Dump Formatter ESTAE was enteredwhile processing the named option, where ccccccccwas the requested formatter option. A DFS2400Imessage and a SNAP of the IMS Offline DumpFormatter control blocks usually precede this errormessage. The request header line, which containsthe requested formatter request type and argumentthat caused the messages to be generated, usuallyprecedes the DFS2400I message.

System actionThe memory dump formatter skips all requests for thenamed option and continues with the next option.

User responseSave the memory dump that was being processed andreport the problem to the IMS system programmer.


Problem determinationRerun with DIAG option; then: 2, 4, 8, 11.

Related information“DFS2400I” on page 689ERROR WHILE ATTEMPTING TO FORMAT THEccc...ccc“IMS problem determination” on page 11



DFS3948E OTMA C/I CLIENTS ARE STILLACTIVE

ExplanationThe OTMA C/I initialization utility DFSYSVI0 was runwhile OTMA C/I clients were still active. Running SVCinitialization with existing OTMA C/I clients can resultin XCF errors.

System actionThe utility issues DFS3950A and waits for a response.

Operator response:The OTMA C/I clients can be identified by using DGRS,RES=(DFSOTMA,*).

User response:Terminate the OTMA C/I clients, and respond toDFS3950A.

Module:DFSYSVI0

Related information“DFS3950A” on page 1134REPLY RETRY, BYPASS OR CANCEL

DFS3949W INSUFFICIENT VIRTUAL STORAGEFOR COMPLETE SB DUMP-FORMATTING

ExplanationThe Sequential Buffering (SB) dump formattingmodule was unable to GETMAIN a work area requiredfor formatting all SB control blocks and SB buffers.

System actionDump formatting continues; however, some SB controlblocks or buffers, or both, are not formatted.

User responseIncrease the amount of virtual storage available to IMSmemory dump formatting.

DFS3950A REPLY RETRY, BYPASS ORCANCEL

ExplanationThe OTMA C/I initialization utility DFSYSVI0 was runwhile OTMA C/I clients were still active. Running SVCinitialization with existing OTMA C/I clients can resultin XCF errors.

System actionThe utility waits for a response.

Operator response:The OTMA C/I clients can be identified by using DGRS,RES=(DFSOTMA,*).

User responseTerminate the clients, and reply "RETRY" to try toinitialize the SVC again.

If the clients cannot be terminated, reply "CANCEL" tostop the utility without initializing the SVC.

If the clients are orphaned and will not be used again,reply "BYPASS" to proceed with the SVC initialization.

Attention: Extreme care must be taken withthis option because it might cause XCF errors ifthose existing clients try to use OTMA C/I again.

Module:DFSYSVI0




DFS3951 TAKEOVER OCCURRED--ENTERPA2 FOR RESPONSE MODE REPLY

ExplanationThis message is issued when the former alternatesystem (now the active system) informs the terminaluser that system takeover has completed. The user isin response mode.


Programmer responseEnter PA2 to receive the response mode reply.

DFS3952 TAKEOVER OCCURRED--ENTERPA2 FOR CONVERSATION MODEREPLY

ExplanationThis message is issued when the former alternatesystem (now the active system) informs the terminaluser that system takeover completed. The user is inconversation mode.


Programmer responseEnter PA2 to continue the conversation mode.

DFS3953 TAKEOVER OCCURRED--ENTERPA2 FOR OUTPUT MESSAGE

ExplanationThis message is issued when the former alternatesystem (now the active system) informs the terminaluser that system takeover completed.


Programmer responseEnter PA2 to receive the output message.

DFS3954 TAKEOVER OCCURRED--REENTERTHE LAST INPUT (/FORMAT MAYBE NECESSARY)

ExplanationThis message is issued when the former alternatesystem (now the active system) informs the terminaluser that system takeover has completed. It alsoindicates the action that the user must take tocontinue the session.

The last input entered before the takeover has beenlost. The input could be data, a PA key, a PF key, or aclear key.


Programmer responseEnter the /FORMAT command to get the last format.If the next input generates unexpected output, enterPA2.

DFS3955 TAKEOVER OCCURRED--ENTERPA2, THEN REENTER THE LASTINPUT

ExplanationThis message is issued when the former alternatesystem (now the active system) informs the terminaluser that system takeover has completed. The user isin conversation mode.


Programmer responseEnter PA2, then reenter the last input. If the next inputgenerates unexpected output, enter PA2.

DFS3956I SYSTEM PST FORMATTINGTERMINATED -- NO SYSTEM PSTSCOULD BE FOUND


ExplanationIMS Offline Dump Formatter SYSPST option requestswere made, but the dumped system does not appearto have any SYSPSTs. This condition is valid only ifthe dumped IMS system was in early initialization atthe time of the memory dump. Storage errors in thedumped IMS system cause this condition.

System actionSYSPST option formatting terminates and theformatter continues with the next option.


However, no SYSPST formatting is possible.

DFS3957I cccccccc FORMATTINGTERMINATED -- INVALIDADDRESS CHARACTERS INARGUMENT

ExplanationThe named option ADDRESS argument containednon-hexadecimal characters, where cccccccc is theformatter option requested. The request header line,which contains the requested formatter request typeand argument that caused this message to begenerated, precedes the error message.

System actionThe IMS Dump Formatter skips the current request forthe named option.

User responseEnsure that option request arguments are valid.Valid hexadecimal values are 0-9, A-F. The addressargument must be 1 to 8 hexadecimal charactersin length. For assistance, see the IMS systemprogrammer.

DFS3958I CLB FORMATTING TERMINATED-- INVALID CHARACTERS IN CIDARGUMENT

ExplanationThe IMS Offline Dump Formatter CLB request,the VTAM communication identifier (CID) argument,contained non-hexadecimal characters. The requestheader line, which contains the requested formatterrequest type and argument that caused this messageto be generated, precedes the error message.

System actionThe IMS Offline Dump Formatter skips the current CLBrequest and continues with the next request.

User responseEnsure that the CID arguments are valid. Validhexadecimal values are 0-9, A-F. The CID is 8hexadecimal characters in length and is the nodenetwork address. For assistance, see the IMS systemprogrammer.

DFS3959I cccccccc FORMATTINGTERMINATED -- ADDRESSARGUMENT IS INVALID

ExplanationThe IMS Offline Dump Formatter named requestADDRESS argument was determined to be in an invalidstorage address range for option cccccccc. Errors inthe dumped storage, or an invalid formatting request,might have caused this condition.

The request header line, which contains the requestedformatter request type and argument that caused thismessage to be generated, precedes the error message.

System actionThe memory dump formatter terminates the currentrequest.

User responseEnsure that the ADDRESS arguments are valid. IMScontrol blocks cannot occur in the first 4 K of storage.For assistance, see the IMS system programmer.

DFS3960I cccccccc FORMATTINGTERMINATED -- INVALID NUMBERARGUMENT REQUESTED

ExplanationThe IMS Offline Dump Formatter request for thenamed option had a NUMBER argument that waslarger than the largest system definition number or 0,where cccccccc was the formatter option requested.An invalid formatting request NUMBER argument orerrors in the dumped IMS system might have causedthis condition.

The request header line, which contains the requestedformatter request type and argument that generatedthis message, precedes the error message.


System actionThe memory dump formatter terminates the currentrequest and continues with the next request.

User responseEnsure that the requested that NUMBER argumentsare valid. Numbers must be nonzero, decimal, andvalid for the IMS system dumped. For assistance, seethe IMS system programmer.

DFS3961I THE REQUESTED PST IS EITHER ASYSTEM PST OR A DPST THAT HASNEVER BEEN USED

ExplanationThe IMS Offline Dump Formatter DPST option found aPST to satisfy a request, but was unable to confirm itsDPST/SYSPST status. If an unused DPST was selected,this condition is valid. But an invalid request for asystem PST under the DPST formatting option mighthave caused this condition.

System actionThe request is terminated, and DPST option formattingcontinues with the next request.

User responseEnsure that all DPST formatting requests are valid. Youcan format the requested PST as a SYSTEM PST. Forassistance, see the IMS system programmer.

DFS3962I cccccccc FORMATTINGTERMINATED -- NO BLOCKSFOUND

ExplanationIMS Offline Dump Formatter requests were made forthe named option, but the dumped IMS system doesnot seem to have any blocks where cccccccc is therequested option. If no blocks were generated, thiscondition is valid. Storage errors in the dumped systemcause this condition.

System actionThe IMS memory dump formatter skips the namedoption and continues with the next option.

User responseEnsure that option request arguments are valid. Forassistance, see the IMS system programmer.

DFS3963I CLB FORMATTING TERMINATED --REQUESTED LTERM NOT FOUND

ExplanationWhile processing an IMS Offline Dump Formattercommunication line block (CLB), no communicationname table (CNT) was found with an LTERM name tomatch the request. An invalid LTERM name argumentfor the request usually causes this condition. But arequest for an LTERM that is not active can cause thiscondition.

System actionThe memory dump formatter terminates the currentCLB formatting request and continues with the nextrequest.

User responseEnsure that the CLB option requests are valid. Ensurethat the CLB LTERM argument refers to a valid IMSLTERM name. For assistance, see the IMS systemprogrammer.

DFS3964I CLB FORMATTING TERMINATED-- REQUESTED NODE NAME NOTFOUND

ExplanationNo communication line block (CLB) was found with anode name to match the CLB request NODE argument.An invalid NODE argument for the request usuallycauses this condition. But requests for dynamicallycreated terminal blocks when the terminal is notcurrently connected to IMS can also cause thiscondition.

The request header line which contains the requestedformatter request type and argument that caused thismessage to be generated precedes the error message.

System actionThe IMS Dump Formatter terminates the currentCLB formatting request and continues with the nextrequest.

User responseEnsure that the CLB option requests are valid. Ensurethat the CLB NODE argument refers to a valid IMSnode name. For assistance, see the IMS systemprogrammer.


DFS3965I cccccccc FORMATTINGTERMINATED -- BLOCK FAILEDVALIDITY CHECK

ExplanationThe control block that was requested for optioncccccccc failed to pass a control block validity check.An invalid request (an address argument) usuallycauses this condition. Errors in the dumped IMS canalso cause this condition.


The validity check ensures a given pointer in thecontrol block points to the expected target location.For example, it verifies that the requested CLB pointsto a valid CTB in the requested CLB.

System actionThe IMS Dump Formatter terminates the currentrequest and continues with the next request.

User responseEnsure that the option requests and their argumentsare valid. For assistance, see the IMS systemprogrammer.

DFS3966I CLB FORMATTING TERMINATED --REQUESTED CID NOT FOUND

ExplanationWhile processing an IMS Offline Dump Formatter CLBoption, no CLB was found with a VTAM CommunicationID (CID) to match the CID request argumentrequested. One of the following situations caused thiscondition:

• The CID argument is invalid.• Dynamically created terminal blocks were requested

when the terminal was not connected to IMS.• Storage errors were in the dumped IMS system.• VTAM terminals were requested that are not

currently connected to IMS.


System actionThe IMS memory dump formatter terminates thecurrent CLB formatting request and continues with thenext request.

User responseEnsure that the CLB option requests are valid. Ensurethat the CID qualifier refers to a valid, connected IMSnode. For assistance, see the IMS system programmer.

DFS3967I INVALID SAP ADDRESS INCLB/LLB -- SAP NOT FORMATTED

ExplanationThe IMS Offline Dump Formatter detected an invalidsave area prefix address while attempting to format asave area prefix associated with a requested CLB/LLB.Storage errors in the dumped IMS system cause thiscondition. The invalid address is found in the CLB/LLBECB prefix that is formatted after this message.

System actionThe IMS Offline Dump Formatter skips the save areaprefix formatting for the current CLB/LLB.

User responseFor assistance, see the IMS system programmer.



DFS3968I cccccccc FORMATTINGTERMINATED -- INVALID NUMBERCHARACTERS IN ARGUMENT

ExplanationThe named option NUMBER argument contained non-decimal characters, where cccccccc is the formatteroption requested.


System actionThe IMS Dump Formatter skips the current request forthe named option.

User responseEnsure that option request arguments are valid. Validdecimal values are 0-9. The number argument must be


one to four decimal numbers in length. For assistance,see the IMS system programmer.

DFS3970 FAST PATH EXECUTION NOTPOSSIBLE.

ExplanationThis message is issued when a terminal that cannotprocess a Fast Path transaction attempts to entera Fast Path transaction. To process a Fast Pathtransaction, a terminal must support response mode.

System actionThe system rejects the attempt and does not schedulethe transaction.

Programmer responseWhen this message is issued, check the relationshipbetween the terminal and transaction to make surethat all system definitions are correct.

DFS3971 UNABLE TO PROCESS FAST PATHDUE TO EMH SHORTAGE

ExplanationIMS was unable to obtain an Expedited MessageHandling (EMH) buffer for the size requested toprocess the Fast Path transaction.

System actionIMS rejects the Fast Path transaction and sends thismessage to the terminal user.

System programmer responseDetermine the current EMH buffer usage. Stop orclose terminals and sessions that currently have EMHbuffers but do not need them. This action frees EMHbuffers for use by terminals and sessions that requirethem.

The next time you restart IMS, increase the EMH bufferpool definitions for the buffer sizes needed.

DFS3974W UNABLE TO WRITE OUTPUTRECORDS FROM THE IMS DUMPFORMATTER TO DATA SET:data_set_name

ExplanationThe IMS Dump Formatter was unable to open orallocate the data set identified in the message text bydata_set_name. It was trying to use the data set forwriting log records from dump log buffers.

System actionIf you provided an existing data set, check that it wascreated in the proper format. If you did not create thedata set, then the system was unable to allocate thedata set.

System programmer responseProvide a valid data set to be used to write the records,or allow the formatter to create one.

Module:DFSAAED1

DFS3975W UNABLE TO WRITE REPORT DATAFROM THE IMS DUMP FORMATTERTO THE OUTPUT DATA SET:data_set_name

ExplanationThe IMS Dump Formatter was unable to open orallocate the data set identified in the message text bydata_set_name for use in writing report data.

System actionIf you provided an existing data set, check that it wascreated in the correct format. If you did not create thedata set, then the system was unable to allocate thedata set.

System programmer responseProvide a valid data set to be used to write the records,or allow the formatter to create one.

Module:DFSAAED1

DFS3976E utility nameUTILITY FAILED TOOPEN THE ddname DATA SET

ExplanationA utility failed to open one of the required data sets.

In the message text:utility name

The utility that encountered the problem.ddname

The data set that failed to open. Possible values forddname are:

SYSUT1REPORTSYSPRINTCONTROLRDDSDSN


System actionThe indicated utility fails with a return code 8.

Programmer responseMake sure that the DD statement for the data set isdefined correctly.

Module:DFSKJOB0, DFSURCM0, DFSURCL0, DFSURST0

DFS3977E routine name ROUTINE FAILED TOOPEN THE ddname DATA SET

ExplanationA routine failed to open one of the required data sets.The routine is started by utility DFSURCM0.

In the message text:routine name

The routine that encountered the problem.ddname

The data set that failed to open. Possible values forddname are:

MODBLKSJOBLIBSTEPLIBSDFSRESL

System actionThe indicated routine fails with a return code 8.


Module:DFSKMOD0, DFSKNUC0

DFS3978E utility name UTILITY FAILED TOCLOSE THE ddname DATA SET

ExplanationA utility failed to close one of the required data setssuccessfully.


The utility that encountered the problem.ddname

The data set that failed to close. Possible valuesfor ddname are:

SYSUT1

REPORSYSPRINTCONTROLMODBLKSRDDSDSN



Module:DFSURCM0, DFSURCL0

DFS3979E routine name ROUTINE FAILED TOCLOSE THE ddname DATA SET

ExplanationA routine failed to close one of the data setssuccessfully. The routine is started by utilityDFSURCM0.


The routine that encountered the problem.ddname

The data set that failed to close. Possible valuesfor ddname are:


System actionThe indicated routine fails with a return code 8.



DFS3980E utility name UTILITY FAILED TOLOAD MODULE module name,RC=rc

ExplanationA utility was unable to load a module.



utility nameThe utility that encountered the problem.

module nameThe module for which load failed. Possible valuesfor module name are:

DFSCNVT0DFSKMOD0

rcThe return code from the load request.


Programmer responseCheck to make sure one of the data sets listed inthe JOBLIB or STEPLIB concatenation contains theindicated module name.


DFS3981E utility name UTILITY FAILED TOOBTAIN STORAGE,SIZE=strgsize,COMPONENT=component

ExplanationA utility encountered an error when trying to obtainstorage for the component.


The utility that encountered the problemstrgsize

The amount of storage requestedcomponent

The component for which the storage requestfailed


Programmer responseIncrease the region size available to the utility.

Module:DFSURCM0, DFSURCL0, DFSURST0

DFS3982W utility name UTILITYFAILED TO FREE STORAGE,SIZE=strgsize, FREEMAINRC=rc,COMPONENT=component

ExplanationAn error occurred when a utility tried to free storagefor a component.


The utility that encountered the problemstrgsize

The amount of storage to be freedrc

The return code from the MVS FREEMAIN requestcomponent

The component for which the storage requestfailed

System actionThe utility terminates successfully with a return code4.

Programmer responseThis is probably an internal error. Search the problem-reporting databases to find a correction for theproblem. If none exists, contact IBM SoftwareSupport. Provide the JCL, SYSLOG, and memory dumpif available.

Module:DFSURCM0, DFSURCL0, DFSURST0

DFS3983E THE DFSURCM0 UTILITY FAILEDTO FIND THE TRANSACTION EDITROUTINE FOR TRANSACTIONCODE transaction code

ExplanationThe Create RDDS from MODBLKS utility (DFSURCM0)was unable to determine the transaction edit routineto be associated with the transaction identified in themessage text by transaction code. This message mightbe the result of one of the following:

1. An IMS.SDFSRESL data set was not supplied, or didnot contain a nucleus member DFSVNUCx with asuffix matching the value specified on the SUFFIX=control statement.

2. If the resource definition data set (RDDS) isbeing created from the system definition input,the CONTROL DD statement does not referencethe data set created by the DFSURST0 utilityOUTPARMS DD statement.

3. The data set referenced by the CONTROL DDstatement does not contain EDITRTN controlstatements for the indicated transaction code.


System actionThe Create RDDS from MODBLKS utility fails with areturn code 8.

Programmer responseBased on the possible cause of the problem, performone of these actions:

For 1, ensure that an IMS.SDFSRESL data setis supplied which contains the nucleus memberDFSVNUCx with a suffix matching the valuespecified on the SUFFIX= control statement.For 2, ensure that data set created by theDFSURST0 utility OUTPARMS DD statement isincluded in the data set concatenation for theCONTROL DD statement code.For 3, ensure that EDITRTN control statements aresupplied for transaction code.

Module:DFSURCM0

DFS3984I DUMP FOR ABEND xxxxxSUPPRESSED BY DUMP OVERRIDETABLE.

or

DUMP FOR ABEND xxxxx FORCED BY DUMPOVERRIDE TABLE.

ExplanationThere is an entry for abend xxxxx in the memorydump override table (DFSFDOT0) to force/suppressthe memory dump generated for this abend.

System actionWhen FORCE is specified a memory dump is takenif that abend occurs. When SUPPRESS is specified amemory dump is not generated. After this procedureis processed the regular post-abend procedure willoccur.

Programmer responseWhen the information is incorrect, modify the memorydump override table entry in DFSFDOT0. When themessage is correct then no further action is necessary.

DFS3985W NO CBTE ENTRY FOUND FOR SAPS- SUMMARY ENDS

Explanation:

Save area prefixes (SAP) storage was not obtained, orthe pointer to the storage is damaged.

System action:The save area summary option terminates, and theIMS Offline Dump Formatter continues with the nextoption.

User response:For assistance, see the IMS system programmer.

DFS3986 IMS SYSTEM IS NOT FDR CAPABLE- COMMAND REJECTED

ExplanationThe /DIS FDR or /CHA FDR command was enteredon an IMS system that is not enabled for Fast DBRecovery.


Operator responseIf you want to run the IMS system with FastDB Recovery, rerun the job with the correct EXECparameters and DFSFDRxx IMS.PROCLIB member.

Module:DFSCMT50

DFS3987 FDR CAPABLE ENVIRONMENTNOT COMPLETED - COMMANDREJECTED

ExplanationAn IMS system was enabled for Fast DB Recovery.However, the Fast DB Recovery environment is notcompleted because restart is in progress and the XCFJOIN request has not been performed yet.


Operator responseAfter the restart operation or cold start completes,enter the command again.

Module:DFSCMT50

DFS3988E THE DFSKMOD0 ROUTINE ISMISSING THE MODBLKS DDSTATEMENT OR DD DUMMY ISSPECIFIED


ExplanationThe JCL specified for the Create RDDS from MODBLKSutility (DFSURCM0) was missing the DD MODBLKSstatement, or a DD DUMMY was specified forMODBLKS.

System actionThe Create RDDS from MODBLKS utility fails with areturn code 8.

Programmer responseMake sure that the MODBLKS DD statement isspecified in the JCL and that a valid data set isspecified.

Module:DFSKMOD0

DFS3989W THE DATA SET SPECIFIED FORTHE dd_name DD STATEMENTDOES NOT CONTAIN MEMBERmember name

ExplanationThe data set specified in a DD statement in the JCL forthe Create RDDS from MODBLKS utility did not containthe indicated member.

In the message text:dd_name

The data set that is missing the member. Valuesinclude:


member nameThe missing member.

System actionProcessing continues. This message is accompaniedby message DFS3990E, if this problem is a terminatingerror.

Programmer responseIf the indicated DD statement is MODBLKS, ensurethat you specified the correct MODBLKS data setassociated with the MODBLKS DD statement. Ensurethat the value specified for the SUFFIX= controlstatement specifies the correct suffix for the membersyou want in the MODBLKS data set.

If the indicated DD statement is JOBLIB, STEPLIBor SDFSRESL, ensure that the data set contains theDFSVNUCx member with a suffix value matching thevalue specified with the SUFFIX= control statement.If the data set containing the DFSVNUCx memberwith a suffix value matching the value specified withthe SUFFIX= control statement does not containthe executable modules for the Create RDDS fromMODBLKS utility, do not specify this data set with theJOBLIB or STEPLIB DD statement, but specify thisdata set with the SDFSRESL DD statement.


Related information“DFS3990E” on page 1143NO MEMBERS WITH SUFFIX: suffix WEREFOUND IN THE MODBLKS DATA SET.

DFS3990E NO MEMBERS WITH SUFFIX: suffixWERE FOUND IN THE MODBLKSDATA SET.

ExplanationThe data set specified in the MODBLKS DDstatement for the Create RDDS from MODBLKS utility(DFSURCM0) did not contain any MODBLKS memberswhose names contained a value for suffix thatmatched the suffix supplied in a control statementor the default value. These members are required forprocessing. This message is accompanied by one ormore occurrences of message DFS3989W, identifyingthe missing members.

System actionThe Create RDDS from MODBLKS utility fails withreturn code 8.

Programmer responseEnsure that the correct MODBLKS data set has beenspecified with the MODBLKS DD statement. Also,ensure that the value specified for the SUFFIX= controlstatement indicates the correct suffix for the membersin the MODBLKS data set.

Module:DFSURCM0

Related information“DFS3989W” on page 1143


THE DATA SET SPECIFIED FOR THE dd_nameDD STATEMENT DOES NOT CONTAIN MEMBERmember name

DFS3991E RECORDS FOR THE SELECTEDCHECKPOINT ARE INCOMPLETE.THE RDDS WAS NOT CREATED.

ExplanationThe checkpoint records in the control statementsor the default specification processed by the CreateRDDS from Log Records utility (DFSURCL0) did notcontain an X'4098' record. That record identifies theend of the checkpoint records. This situation mightresult from one of the following circumstances:

• You specified an incorrect checkpoint ID forprocessing.

• Log data sets might be missing from the SYSUT1 DDstatement concatenation.

System actionThe Create RDDS from Log Records utility fails with areturn code 8.

Programmer responseIf a checkpoint ID is specified with the CHKPTID=statement, ensure that this checkpoint contains boththe X'4001' record (beginning of checkpoint) and theX'4098' record.

If no checkpoint ID was specified, ensure that the logdata set that includes the X'4098' record is includedin the SYSUT1 DD statement concatenation of the logdata sets at the end of the log data sets.

Module:DFSURCL0

DFS3992E utility name UTILITYENCOUNTERED AN ERRORPARSING THE CONTROL DATA

ExplanationThe utility identified by utility name in the messagetext encountered an error while trying to parse thecontrol statements in the CONTROL data set. Thismessage is accompanied by a more specific errormessage describing the problem.

System actionThe Create RDDS from MODBLKS utility (DFSURCM0)fails with a return code 8.

Programmer responseCheck the accompanying messages to determine theparsing errors that you must correct in the CONTROLdata set.


DFS3993E AN INVALID VALUE WASENCOUNTERED BY THEDFSURCM0 UTILITY FOR THESYSTYPE CONTROL STATEMENT

ExplanationAn invalid value was supplied for the SYSTYPE=keyword on a statement in the CONTROL data set. Theallowable values are:

DBDCDBDC


Programmer responseCorrect the invalid value for the keyword.

Module:DFSURCM0

DFS3994I IMS SYNC WITH RM GLOBALSTATUS COMPLETE- yyyy.dddhh:mm:ss.ms

ExplanationGlobal status is read from Resource Manager (RM)during IMS initialization. This message indicates thatIMS is in sync with RM global status.

In the message:

yyyy - the yearddd - the dayhh:mm:ss.ms - local time

System actionIMS continues processing. Any global status updatedin RM after this message and before an IMS restart iscomplete is not applied at this IMS that is restarting.All commands sent to this IMS are not processed asrestart is not complete.



After restart is complete, issue commands withSCOPE(ACTIVE) to ensure this IMS is in sync with RMstatus.

ModuleDFSGST10

DFS3995E REQUIRED KEYWORDMODBLKSHLQ= WAS NOTSUPPLIED

ExplanationThe JCL specified for the Stage 1 pre-parser(DFSURST0) was missing the DD MODBLKS statement,or a DD DUMMY was specified for MODBLKS.

System actionThe Stage 1 pre-parser fails with a return code 8.

Programmer responseEnsure that the MODBLKSHLQ= control statement isspecified with the CONTROL DD statement.

Module:DFSURST0

DFS3996E ONLY ONE SPECIFICATION OFCHKPTID IS ALLOWED

ExplanationThe system found multiple values for the CHKPTID=keyword in the CONTROL data set.

System actionThe utility fails with a return code 8.

Programmer responseSupply a single specification of the CHKPTID= keywordand resubmit the job.

Module:DFSURCL0

DFS3997E CHECKPOINT ID checkpoint id NOTFOUND IN THE LOG. THE RDDSDATA SET WAS NOT WRITTEN

ExplanationThe checkpoint ID checkpoint id, specified in theCHKPTID= control statement, did not match anycheckpoint in the log.

System actionThe Create RDDS from Log Records utility (DFSURCL0)fails with a return code 8.

Programmer responseSpecify a valid checkpoint ID if processing a specific IDis required, or omit this control statement. In this casethe last checkpoint ID on the log will be processed.

Module:DFSURCL0

DFS3998E NO COMPLETE CHECKPOINTSWERE FOUND IN THE LOG IN THEINDICATED TIME RANGE

ExplanationThe log did not include both the begin and endcheckpoint log records. The checkpoint records wereincomplete. Possible reasons include:

• The records for a checkpoint span multiple log datasets.

• A value for STARTTIME was specified which wasafter the time stamp on any beginning checkpointrecord on the log.

• A value for STOPTIME was specified which occurredbefore the time stamp on the end checkpoint recordfor the checkpoint being processed.


Programmer responseEnsure that sufficient log data sets are concatenatedto contain all the records for a checkpoint. If youspecify a STARTTIME, ensure that the value doesnot represent a time later than the time after thelast beginning checkpoint on the log. If you supplya STOPTIME, ensure that the value specified doesnot occur before the end of the checkpoint beingprocessed.

Module:DFSURCL0

DFS3999W A STOP TIME WAS SUPPLIEDWHICH EXCEEDS THE TIMERANGE IN THE LOG.STOP TIME: stop time TIME ONLAST RECORD: record time


ExplanationA value for the STOPTIME keyword was supplied inthe CONTROL data set. The stop time value exceededthe latest time stamp on the last processed log record.This situation might be valid; however, it might indicatethat the concatenation of log data sets in DD SYSUT1 isincomplete.

System actionThe Create RDDS from Log Records utility (DFSURCL0)continues processing. It terminates successfully with areturn code 4.

Programmer responseEnsure that all of the log data sets you want areincluded in the SYSUT1 DD concatenation.

Module:DFSURCL0

DFS4000I OFFLINE DUMP FORMATTINGINITIALIZATION action

ExplanationAfter detecting an error in offline dump formattinginitialization, IMS indicates what action it will take.

Depending on the severity of the error, the action willbe either CONTINUING or DISCONTINUED.

System actionIMS takes the action indicated in the message.

Operator responseIf the action is DISCONTINUED, contact the systemprogrammer. If the action is CONTINUING, noresponse is necessary.

System programmer responseVerify that the input data set, input parameters, andJCL are correct.




Chapter 84. DFS messages, DFS4001 - DFS4050A


DFS4002E FAILURE ENCOUNTEREDPROCESSING TYPE-2 COMMANDLOG RECORDSDFSURCL0 ROUTINE: routine nameRESOURCE: resource nameTYPE:type nameFUNCTION:function typeVERB:verb type

ExplanationThe routine, identified in the message text, wasprocessing type-2 command log records for theindicated resource.


The routine associated with DFSURCL0 that wasprocessing the resource. Possible values are:

DFSKDB20DFSKPG20DFSKTR20DBFKRT20

resource nameThe name of the resource that was beingprocessed at the time of failure.

type nameThe type of resource that was being processed atthe time of failure. Possible values are:

DDIRPDIRSMBRCTE

function typeThe type of process that was being performed atthe time of failure. Possible values include:

• FINDFAIL – an error retrieving data for theresource.

• CREFAIL – an error creating the resource.• DUP – a resource being created already exists.

verb typeThe type of processing that was indicated by theType-2 Command Log record. Possible values forverb type are:

CREDEL

UPD

System actionThe indicated routine fails with return code 8.

Programmer responseThis message indicates an internal error in moduleDFSURCL0. Contact IBM Software Support.

Module:DFSURCL0

DFS4003E FAILURE EXTENDING THE ARRAYFOR RECORD TYPE record type.RC:rc

ExplanationAn error occurred trying to obtaining additional storagefor an internal array used to process the indicatedrecord type.

In the message text:record type

The type of record. Possible values are:

X4004X4006X4007X4083

rcThe return code from the MVS GETMAIN.

System actionThe routine fails with the return code rc.

Programmer responseCheck the return code from the MVS GETMAIN requestto determine the cause of the failure.

Module:DFSURCL0

DFS4004W LOG WRAPS AFTER RECORDrecord numberCURRENT RECORD TIME STAMP:time stampPRIOR RECORD TIME STAMP :time stamp


ExplanationThe value for the store clock time on the currentrecord is earlier than the store clock time on the priorrecord. Time stamps must always be in ascendingorder. The possible reasons for this problem include:

• The log being processed is an open OLDS data set.An Open OLDS data set does not have an end-of-filemark, such that records following the current entryin the OLDS are residual from the last time the logwas used.

• Multiple logs have been concatenated as input andare out of sequence.

System actionThe Create RDDS from Log Records utility (DFSURCL0)treats the prior record, with the larger time stampvalue, as the end of file and performs end-of-logprocessing. It terminates successfully with return code4.

Programmer responseIf multiple log data sets are being processed, ensurethat the log data sets are concatenated in theproper order. If this message was issued because ofprocessing an open OLDS, even if the processing wassuccessful, close the OLDS by issuing a /SWI OLDScommand. Then run the utility again to avoid themessage.

Module:DFSURCL0

DFS4005E THE DFSKNUC0 ROUTINE ISMISSING THE dd_name DDSTATEMENT

ExplanationThe JCL specified for the DFSKNUC0 routine, invokedby utility DFSURCM0, was missing the indicated DD KSstatement. Possible values for dd_name are:

JOBLIBSTEPLIBSDFSRESL

System actionThe Create RDDS from MODBLKS utility (DFSURCM0)fails with a return code 8.

Programmer responseEnsure that you have a JOBLIB, STEPLIB or SDFSRESLDD statement specified in the JCL, and that a validdata set is specified.

Module:DFSKMOD0

DFS4006E AN INVALID CHKPTID (chkptid)WAS SUPPLIEDIT MUST BE OF THE FORMAT:yyddd/hhmmss

ExplanationThe value supplied for the CHKPTID= keyword in theCONTROL data set was invalid. The value was not ofthe format yyddd/hhmmss.


Programmer responseCorrect the specification for the CHKPTID= keywordand resubmit the job.

Module:DFSURCL0

DFS4007E AN INVALID STARTTIME ORSTOPTIME WAS SUPPLIED

ExplanationThe value you supplied for the STARTTIME= orSTOPTTIME= keyword in the CONTROL data set wasinvalid.


Programmer responseCorrect the specification for the STARTTIME orSTOPTIME= keyword and resubmit the job.

Module:DFSURCL0

DFS4008E THE STOPTIME PRECEDES THESTARTTIME


ExplanationThe value you supplied for the STOPTIME= keywordrepresents an earlier time than the value supplied forthe STARTTIME= keyword in the CONTROL data set.The STOPTIME must be later than the STARTTIME.


Programmer responseCorrect the specification for the STARTTIME orSTOPTIME= keyword and resubmit the job.

Module:DFSURCL0




DFS4138E utility name UTILITY RDDSINSPECIFIES AN INVALID RDDS.

ExplanationThe data set specified by the RDDSIN DD statementis invalid. It might be invalid for one of the followingreasons:

• The data set may not be an RDDS.• The data set may be an RDDS, but a status of GOOD

was not contained in the header record.

System actionThe indicated utility fails with return code 8.

Programmer responseSpecify a valid RDDS for the RDDSIN DD statement.

Module:DFSURCP0

DFS4139E IMSID IS MISSING OR INVALID.imsid WAS SPECIFIED.

ExplanationThe value supplied for the IMSID= keyword in theCONTROL data set was missing or was invalid. Thevalue for IMSID must be a string containing 1 to 4characters.

Utilities DFSURCL0 and DFSURCP0 do not require thiskeyword. This error situation is triggered only in thesetwo utilities if the value is incorrectly specified. Thiskeyword is required by utility DFSURCM0.

System actionThe utility fails with a return code 8.

Programmer responseCorrect the specification for the IMSID= keyword andresubmit the job.

Module:DFSURCL0, DFSURCM0, DFSURCP0

DFS4140E NULL VALUES ARE NOT ALLOWEDIN UTILITY utility name FORKEYWORD keyword.

ExplanationThe indicated keyword was supplied in the CONTROLor SYSIN data set without an associated value. A valuefor this keyword must be supplied.


The name of the utility that encountered theproblem

keywordThe keyword that is missing a value


Programmer responseSupply a value for the indicated keyword and resubmitthe job.


DFS4141E A NUMERIC VALUE EXCEEDING7 CHARACTERS WAS SUPPLIEDTO UTILITY utility name FORKEYWORD keyword.

ExplanationThe numeric value that you supplied in the CONTROLor SYSIN data set for the indicated keyword exceeded7 characters. The maximum number of numericcharacters allowable is 7.



keywordThe keyword that exceeded 7 characters


Programmer responseSupply a valid value for the indicated keyword andresubmit the job.



DFS4142E YOU SUPPLIED NON-NUMERICDATA TO UTILITY utility name FORKEYWORD keyword.

ExplanationThe value that you supplied in the CONTROL or SYSINdata set for the indicated keyword was non-numeric;however, the keyword requires a numeric value to besupplied.



keywordThe keyword that requires a numeric value


Programmer responseSupply a value for the indicated keyword and resubmitthe job.


DFS4143E AN EMPTY INPUT FILE TO UTILITYDFSKJOB0 WAS FOUND; CHECKTHAT IMS SYSTEM STAGE 1FAILED

ExplanationThe file referenced by the INFILE DD statement shouldcontain the JCL stream created by a prior successfulrun of a IMS System Stage 1; however, this file isempty. It might be invalid for one of the followingreasons:

• The IMS System Stage 1 step did not completesuccessfully.

• The INFILE DD statement for DFSKJOB0 does notreference the data set containing the output fromIMS System Stage 1.

System actionThe utility fails with return code 8.

Programmer responseEnsure that IMS System Stage 1 runs successfully andthat the INFILE DD references the data set containingthe output from IMS System Stage 1.

Module:DFSKJOB0

DFS4144E utility name UTILITY WAS UNABLETO PROCESS MODBLKS: member

ExplanationThe utility identified by utility name in the messagetext encountered an error while trying to process themember identified by member from the MODBLKSdata set. This message is accompanied by a morespecific error message describing the problem. Theseadditional error messages include:

DFS3977EDFS3981EDFS3988E

System actionThe Create RDDS from MODBLKS utility (DFSURCM0)fails with return code 8.

Programmer responseCheck the accompanying messages to determine theproblem encountered during the processing of theindicated member in MODBLKS data set.

Module:DFSURCM0

Related information“DFS3977E” on page 1140routine name ROUTINE FAILED TO OPEN THEddname DATA SET“DFS3981E” on page 1141utility name UTILITY FAILEDTO OBTAIN STORAGE,SIZE=strgsize,COMPONENT=component“DFS3988E” on page 1142THE DFSKMOD0 ROUTINE IS MISSING THEMODBLKS DD STATEMENT OR DD DUMMY ISSPECIFIED

DFS4145I THE DDL-DEFINED PSB psb_nameIS BEING INSERTED INTO THEIMS DIRECTORY DATA SET. PSTpst_name.


ExplanationThe partition specification table (PST) task that isidentified in the message text is adding the programview (PSB) that is identified in the message text to theIMS directory data set. The PSB was not previously inthe IMS directory data set.

In the message text:psb_name

The program view (PSB) that is added to the IMSdirectory data set.

pst_nameThe PST name of the task that is processing theinstructions from the DDL stream.

System actionThe PST task adds the PSB to the IMS directory dataset and continues processing the instructions from theDDL stream.

Depending on whether the application program thatuses the PSB was created in the online IMS systembefore the DDL was submitted, the PSB might or mightnot be active and ready for use.

If the application program was created before the DDLwas issued, the PSB is active and ready for use.

If the application program was not created before theDDL was issued, the PSB remains inactive until theapplication program is created.

Programmer responseDetermine if the application program was alreadycreated in the IMS system by issuing either of thefollowing commands:

• QUERY PGM• /DISPLAY PGM

If the application program does not yet exist for thePSB, you can create one either by either issuing theCREATE PGM IMS type-2 command or by coding theAPPLCTN stage-1 system definition macro, performingsystem definition, and restarting IMS.

Module:DFSOLC70

Related referenceQUERY PGM command (Commands)/DISPLAY PGM command (Commands)CREATE PGM command (Commands)

DFS4146W THE DIRECTORY DATA SET WASUPDATED WHILE THIS IMS WASOFFLINE.

ExplanationWhile this IMS system was offline, another IMS systemupdated the active application control blocks ACBs inthe IMS directory data set of the IMS catalog that isshared by this IMS system.

System actionThis IMS system restarts and uses the updated ACBs.

System programmer responseDetermine whether the updated ACBs have any impacton the application programs that this IMS systemsupports and take appropriate action.

Module:DFSRDB30

Related informationThe IMS catalog in multi-system configurations(System Definition)

DFS4148I THIS IMS REGION IS REGISTEREDAS AN IMS VUE PRODUCT

ExplanationThe IMS region is registered with the SystemManagement Facility (SMF) as an IMS Database ValueUnit Edition (VUE) product. IMS regions are registeredwith SMF during initialization. This message is issuedduring IMS control region initialization and IMS batchregion initialization if the region is registered with SMFas an IMS Database VUE product.

IMS control regions and IMS batch regions areregistered as IMS Database VUE products if the termsand conditions of the IMS Database VUE productsare accepted and each region is running in a zNALC(System z® New Application License Charges) LPAR.

System action:The IMS control region or the IMS batch region isregistered with SMF as an IMS Database VUE product.


Module:DFSSMF00


http://www.ibm.com/support/knowledgecenter/SSEPH2_15.1.0/com.ibm.ims15.doc.cr/imscmds/ims_querypgm.htm#ims_cr2querypgm

http://www.ibm.com/support/knowledgecenter/SSEPH2_15.1.0/com.ibm.ims15.doc.cr/imscmds/ims_displaypgm.htm#ims_cr1displaypgm


http://www.ibm.com/support/knowledgecenter/SSEPH2_15.1.0/com.ibm.ims15.doc.sdg/ims_catalog_definition_multisystem.htm#ims_catalog_definition_multisystem




DFS4151I THE DDL-DEFINED PSB psb_nameIS INSERTED INTO THE IMSDIRECTORY DATA SET. PSTpst_name

ExplanationAfter the database specified by dbdname was stoppedand restarted at the tracking site, the database trackerdetermined that a database update log record wasbeing applied out of the expected sequence.

In most cases, no error exists.

In the message text:dbdname

The name of the shadow database.imsid

The IMS system from which the log was routed.pri

The PRILOG time of the log.lsn

The log sequence number of the database (X'50')log record being applied to the shadow database.

usnThe update sequence number (USN) in thedatabase update log record being applied to theshadow database.

System actionDatabase tracking continues.

Operator responseIf it is unclear whether or not an error exists, contactIBM Software Support for programming assistance.

ModuleDFSDT210, DFSDT240

DFS4154W The number of active APPCconversations has reached xx% ofthe maximum limit of limit.

ExplanationThe number of active APPC/IMS conversations that arecurrently being processed in 31-bit storage by IMS

reached xx percent of the maximum allowable numberof active APPC/IMS conversations.


The percentage of the 31-bit limit for activeAPPC/IMS requests that the current number ofactive APPC/IMS conversations represents.

limitThe maximum allowable number of activeAPPC/IMS conversations that can be processedconcurrently by IMS.

The default limit for active APPC conversations is5,000.

System actionIMS continues normal processing.


Determine if either IMS is having a problem processingAPPC/IMS transaction requests or if there is a suddenflood of incoming APPC/IMS transactions.

If both IMS processing performance and the numberof incoming APPC/IMS requests are within acceptableranges, consider increasing the APPC/IMS limitsthat are currently in effect. The APPC/IMS limitsare specified on the APPCMAXC parameter in theDFSDCxxx member of the IMS PROCLIB data set.

Module:DFS62FD0

Related informationDFSDCxxx member of the IMS PROCLIB dataset (System Definition)

DFS4155W Maximum limit for active APPCconversations has been reached.New requests will be queued in 64bit storage.

ExplanationThe number of active APPC conversations in 31-bitstorage reached the limit that is currently in effect.




System actionIMS queues any new APPC /IMS conversation requestsin 64-bit storage until IMS can accept them forprocessing.




Module:DFS62FD0


DFS4156W The number of APPC requests in64 bit storage has reached xx% ofthe maximum limit of yyyyyyyy.

ExplanationThe number of APPC/IMS requests that are currentlyqueued in 64-bit storage reached the xx percent of themaximum allowable number yyyyyyyy.


The percentage of the maximum allowable numberthat the current number of queued APPC/IMSrequests represents.

yyyyyyyyThe maximum allowable number of APPC/IMSrequests that can be queued in 64-bit storage.

System actionIMS continues normal processing. Incoming APPC/IMSrequests continue to be queued to 64-bit storage untilthey can be accepted for processing by IMS.




Module:DFS62FD0


DFS4157W The number of queued APPCrequests reached the maximumlimit. All input from APPC clientsis stopped.

ExplanationThe number of APPC/IMS conversation requests thatare queued in 64-bit storage waiting to be accepted byIMS for processing reached the limit that is currently ineffect.

System actionIMS issues a request to z/OS to stop further input fromAPPC clients.




Module:DFS62FD0


DFS4158I Queuing of APPC requests to 64bit storage has been stopped.

ExplanationAPPC/IMS stopped using 64 bit storage to queueAPPC requests. Enough 31 bit storage is available tocontinue normal processing.








System actionIMS receives and processes APPC/IMS conversationsin 31-bit storage normally without queuing incomingAPPC/IMS requests to 64-bit storage.


Module:DFS62FD0


DFS4159E ACBSHR= CAN ONLY BE CHANGEDBY IMS xxxx

ExplanationThis IMS system is attempting to change the sharingcharacteristic for the IMS catalog directory byspecifying a value for ACBSHR= that is different thanwhat was specified when the first IMS started usingthe IMS catalog directory. The IMS catalog directorycan be used by another IMS system. Only the specifiedsystem can change the sharing characteristic of theIMS catalog directory.

System actionIMS terminates with abend U0071.


Operator responseCheck that the specification of the ACBSHR and ALIASparameters for this IMS are correct.

Module:DFSRDB30

DFS4160E ACBSHR=N IS SPECIFIED, BUTTHE DIRECTORY IS SHARED BYOTHER IMS SYSTEMS.

ExplanationThis IMS system is referencing an IMS catalog thatis shared by other IMS systems, but this IMS systemcannot share the IMS catalog because ACBSHR=N isspecified in a PROCLIB member that this IMS systemuses. When the IMS management of applicationcontrol blocks (ACBs) is enabled, ACBSHR=N indicatesthat the IMS catalog and the ACBs in the IMS directorydata set are not shared.

The ACBSHR=N can be specified in either theDFSCGxxx member or the COMMON_SERVICE_LAYERsection of the DFSDFxxx member of the PROCLIB dataset.

Either the ACBSHR specification of the IMS systemis incorrect, the IMS system is referencing the wrongIMS catalog, or the IMS catalog was set up by an IMSsystem that specified ACBSHR=Y.

System actionIMS terminates with abend U0071.

Operator responseCheck that the specification of the ACBSHR and ALIASparameters for this IMS are correct.

If this IMS system must share the IMS catalog, specifyACBSHR=Y in the appropriate PROCLIB member. TheACBSHR parameter can be specified in the followinglocations:

• COMMON_SERVICE_LAYER section of the DFSDFxxxmember (System Definition)

• DFSCGxxx member of the IMS PROCLIB data set(System Definition)

If the IMS system is referencing the wrong IMScatalog, correct the specification of the ALIAS=parameter in the CATALOG section of the DFSDFxxxmember. If necessary, run one of the IMS Catalogpopulation utilities to load the ACBs that are requiredby this IMS system into the IMS catalog and itsassociated IMS directory data sets.

If the ACBSHR and ALIAS specifications for the IMSsystem are correct, the IMS catalog must be re-created to set it up as a non-shared IMS catalog.

Module:DFSRDB30

Related conceptsThe IMS catalog in multi-system configurations(System Definition)Related tasksSetting up the IMS catalog (System Definition)Related referenceCATALOG and CATALOGxxxx sections of theDFSDFxxx member (System Definition)DFSCGxxx member of the IMS PROCLIB dataset (System Definition)COMMON_SERVICE_LAYER section of theDFSDFxxx member (System Definition)

DFS4161I FDR FOR (imsid) TRACKINGSTARTED




http://www.ibm.com/support/knowledgecenter/SSEPH2_15.1.0/com.ibm.ims15.doc.sdg/ims_dfsdfxxx_proclib_csl.htm#ims_dfsdfxxx_proclib_csl


http://www.ibm.com/support/knowledgecenter/SSEPH2_15.1.0/com.ibm.ims15.doc.sdg/ims_dfscgxxx_proclib.htm#ims_dfscgxxx_proclib




http://www.ibm.com/support/knowledgecenter/SSEPH2_15.1.0/com.ibm.ims15.doc.sdg/ims_catalog_definition_overview.htm#ims_catalog_definition_overview







ExplanationThe Fast DB Recovery region is established and istracking the IMS system identified by imsid.


ModuleDFSFDR10

DFS4162E ERROR OPENING THE IMSDIRECTORY DATA SET

ExplanationThe IMS directory data set failed to open.

System actionThe IMS restart or cold start failed with abend 071.

System programmer responseCheck for other error messages, such as z/OS messageIEC143I, that might indicate the cause of the problem.After the error is corrected, restart IMS.

Module:DFSRDB30

DFS4164W FDR FOR (imsid) TIMEOUTDETECTED DURING LOG AND XCFSURVEILLANCE

ExplanationThe Fast DB Recovery region detected a timeout statusduring log and XCF surveillance. One of followingconditions might have occurred:

• The identified IMS system is in a wait.• The identified IMS system is in a loop.• A failure occurred on the z/OS on which theidentified IMS system is running.

• A failure occurred in the central processing complex(CPC) on which the identified IMS system is running.

System actionThis message is retained in the operator console. TheFast DB Recovery region continues tracking. If the FastDB Recovery region is able to read a new log record,or if XCF surveillance detects the IMS system resumednormal processing, this message is deleted from theconsole.

Operator responseIf the IMS system is in a wait or loop, cancel IMS,if necessary. If z/OS or the CPC failed, reset thesystem and enter the MVS MODIFY command (Ffdrproc,RECOVER) to initiate database recovery inthe Fast DB Recovery region.

Module:DFSFDR90

DFS4165I FDR FOR (imsid) XCF DETECTEDACTIVE SYSTEM RESUMED

ExplanationXCF notified the Fast DB Recovery region that theidentified IMS system exited timeout status indicatedin message DFS4165W and has resumed normalprocessing.


ModuleDFSFDR80

Related information“DFS4165W” on page 1158FDR FOR (imsid) XCF DETECTED TIMEOUT ONACTIVE IMS SYSTEM, REASON = reason

DFS4165W FDR FOR (imsid) XCF DETECTEDTIMEOUT ON ACTIVE IMS SYSTEM,REASON = reason

ExplanationXCF notified the Fast DB Recovery region that atimeout occurred on the IMS system identified byimsid. The variable reason is one of the following:IMS SURV., DIAGINFO = nnnnnnnn

XCF reported the timeout. At least one IMS TASKor ITASK might be in a loop or wait state in the IMSsystem. The nnnnnnnn indicates which TASK orITASK might have caused the timeout. nnnnnnnnis made of two parts. The first 2 bytes indicate theTASK or ITASK getting the timeout, and the second2 bytes indicate whether another TASK or ITASKmight be involved, as shown in the following table:

Table 25. TASK or ITASK involvement

TASK or ITASK intimeout

TASK or ITASKpossibly involved

Bit 0 x'8000' CTL TCB IMS Control Task


Table 25. TASK or ITASK involvement (continued)

TASK or ITASK intimeout

TASK or ITASKpossibly involved

Bit 1 x'4000' XFP TCB Fast Path Control Task

Bit 2 x'2000' CST ITASK Common ServicesITASK

Bit 3 x'1000' CHKITASK

Checkpoint ITASK

Bit 4 x'0800' SAS ITASK DLISAS ITASK

Bit 5 x'0400' FP CST00 Fast Path CommonServices ITASK

Bit 6 x'0200' FP CSTS0 Fast Path CommonServices dependentITASK

Bit 7 x'0100' reserved

IMS SURV., DIAGINFO = N/AXCF detected the timeout. The IMS address spacemight be non-dispatchable or the status exitroutine might have failed.

SYSTEM, DIAGINFO = nnnnnnnnXCF detected the timeout. The failure or eventwas at the z/OS-system level. The nnnnnnnnrepresents the GEPLFLGS word of the list ofinput parameters from the XCF group exit routine.The values are documented in z/OS MVS DataAreas, Vol 3 (IVT-RCWK) (GA22-7583), undermacro IXCYGEPL. In addition, you might findthis information in the IXCYGEPL macro inSYS1.MACLIB.


If log surveillance also detects a timeout status,DFS4164W follows this message.

Operator responseCheck the status of the IMS and z/OS systems. If IMSis in a loop or a wait state, terminate IMS with the MVSMODIFY command (F activeims,DUMP) to initiatedatabase recovery in the Fast DB Recovery region.

If a z/OS or hardware failure occurred, reset thesystem and enter the MVS MODIFY command (Ffdrproc,RECOVER) to initiate database recovery.

System programmer responseCall IBM Software Support for assistance.

Module:

DFSFDR80Related referencez/OS: IXCYGEPL heading informationRelated information“DFS4164W” on page 1158FDR FOR (imsid) TIMEOUT DETECTED DURINGLOG AND XCF SURVEILLANCE

DFS4166I FDR FOR (imsid) DB RECOVERYPROCESS STARTED, REASON =reasonid

ExplanationThe Fast DB Recovery region stopped tracking theidentified IMS system and started database recoveryfor the reason indicated in reasonid, which is one ofthe following:IMS FAILURE

An IMS system failure was detected by a X'06' logrecord. The Fast DB Recovery region automaticallyinitiated recovery.

RECOVER COMMANDRecovery was initiated by the MVS MODIFYcommand (F fdrproc,RECOVER).

XCF NOTIFICATIONRecovery was initiated by MVS XCF notification.

System actionThe Fast DB Recovery region started databaserecovery.

ModuleDFSFDR00

DFS4167A FDR FOR (imsid) WAITINGFOR ACTIVE SYSTEM TOCOMPLETE I/O PREVENTION.REPLY "UNLOCK" WHEN I/OPREVENTION COMPLETES.

ExplanationThe Fast DB Recovery region cannot continue until theidentified IMS system completes I/O prevention.

System actionThe Fast DB Recovery region waits for the operator'sreply.

Operator responseMake sure that the failing IMS system completed I/Oprevention, as follows:


http://www-01.ibm.com/support/knowledgecenter/SSLTBW_2.4.0/com.ibm.zos.v2r4.ieai800/xcl.htm

• Look for message AVM006E with an rsename thatmatches the imsid in this message.

• If message AVM006E does not appear, manuallystop I/O for the IMS system. To do this, manuallyswitch DASD or reset the system.

Then reply UNLOCK in response to this message.

ModuleDFSFDR00

DFS4168I FDR FOR (imsid) DATABASERECOVERY COMPLETED

ExplanationThe Fast DB Recovery region completed databaserecovery.

System actionThe Fast DB Recovery region terminates normally.

Operator responseRestart the identified IMS system.

ModuleDFSFDR00

DFS4169I FDR FOR (imsid) PROCESSTERMINATED

ExplanationThe Fast DB Recovery region terminated because theidentified IMS system terminated normally or becausethe MVS MODIFY TERM command (F fdrproc,TERM)was issued.

System actionThe Fast DB Recovery region terminates normally.

ModuleDFSFDR00

DFS4170I FDR FOR (imsid) NORMALTERMINATION DETECTED FORACTIVE SYSTEM

ExplanationThe Fast DB Recovery region detected that theidentified IMS system terminated normally.

System actionThe Fast DB Recovery region stops tracking andterminates normally.

Module:DFSFDR10

DFS4171I FDR FOR (imsid) ACTIVE IMSTERMINATION NOTIFIED BY XCF.OPERATION RESUMED.

ExplanationMVS XCF notified the Fast DB Recovery region thatthe active IMS system terminated. Message DFS4167Awas issued.

System actionMessage DFS4167A is cleared from the consoleand the Fast DB Recovery region resumes databaserecovery.

Module:DFSFDR00

Related information“DFS4167A” on page 1159FDR FOR (imsid) WAITING FOR ACTIVESYSTEM TO COMPLETE I/O PREVENTION.REPLY "UNLOCK" WHEN I/O PREVENTIONCOMPLETES.

DFS4172I FDR FOR (imsid) ACTIVE SYSTEMNOT FOUND OR IN FAILED STATUS

ExplanationThe imsid of the IMS system was verified by the FastDB Recovery region. However, either the imsid was notidentified to IRLM, or the identified system has a failedstatus.

System actionThe Fast DB Recovery region waits for the activesystem to join the group.

Operator responseUse the IRLM MODIFY command (Firlmproc,STATUS) to display the status of theidentified IMS system. To ensure that the IMS systemis active, check that the imsid specified in the IMSIDparameter of the EXEC statement is identical to theimsid of the active system. Correct any errors andrestart, or let ARM restart, the IMS active system.


If the IMS system is XRF capable, RSENAME is usedfor the identifier instead of imsid, which causes thismessage and an abend.

Module:DFSFDR70

DFS4173E FDR FOR (imsid) CHECKPOINTLOG HAS INCONSISTENCY

ExplanationThe checkpoint log records created by the identifiedIMS system have one of the following inconsistencies:

• The identified IMS system was not enabled for FastDB Recovery.

• The identified IMS system did not use IRLM.

Possible reasons for this problem are:

• Incorrect parameter specification of the IMS systemor the Fast DB Recovery region

• Incorrect DD statements in the OLDS or IMSRDS inan IMS or Fast DB Recovery procedure.

System actionThe Fast DB Recovery region is terminated.

Operator responseMake sure that the IMS system is enabled for Fast DBRecovery, and that Fast DB Recovery reads the correctOLDS. Correct any errors. Then restart the IMS systemand the Fast DB Recovery region.

Module:DFSFDR10

DFS4174E NO FDRMBR EXEC PARAMETERSPECIFIED

ExplanationThe FDRMBR parameter was not specified on the EXECstatement in the Fast DB Recovery procedure or onthe control statement in the DFSPBxxx IMS.PROCLIBmember.


Operator responseSpecify the correct FDRMBR parameter in the Fast DBRecovery procedure or on the control statement in theDFSPBxxx IMS.PROCLIB member. Then rerun the job.

Module:

DFSZINT0

DFS4175E NO ACTIVEIMSID PARAMETERSPECIFIED

ExplanationThe imsid was not specified in the ACTIVEIMSIDparameter on the control statement in memberDFSFDRxx of IMS.PROCLIB.

System actionIf the Fast DB Recovery region issues this message,the Fast DB Recovery region is terminated. If theIMS system issues this message, processing continueswithout Fast DB Recovery.

Operator responseSpecify the correct ACTIVEIMSID parameter inmember DFSFDRxx, or specify the correct suffix ofmember DFSFDRxx on the FDRMBR parameter in theprocedure. Restart the Fast DB Recovery region, orterminate the IMS system and rerun it with Fast DBRecovery.

Module:DFSZINT0

DFS4176E FDR FOR (imsid) UNABLE TOESTABLISH CHKPT - reason

ExplanationThe Fast DB Recovery region could not establish acheckpoint ID from which to start. reason identifiesthe cause and can be one of the following reasons:ACTIVE SYSTEM ALREADY SHUTDOWN

The IMS restart data set indicated the identifiedIMS system was already terminated.

CHKPT ID NOT FOUND IN IMSLOGThe Fast DB Recovery region could not locate acheckpoint ID that the IMS system with Fast DBRecovery had written.

If neither of these reasons was shown, see thedocumentation for the messages issued before thismessage for more information.

System actionThe Fast DB Recovery region terminates abnormally.

Operator responseMake sure that all of the following are true:

• The identified IMS system is running.


• The correct restart data set (RDS) is being used forthe Fast DB Recovery region, and it is the same RDSthat the IMS system with Fast DB Recovery is using.

• The DBRC RECON data set and OLDSs are thecorrect ones, properly allocated in shared DASDenvironment, and accessible from both the IMSsystem and the Fast DB Recovery region.

Correct the error and restart the job.

Module:DFSFDR00

DFS4177E FDR FOR (imsid) XCF JOIN FAILED.

ExplanationAn XCF JOIN failed. The second line of this messagefurther explains the problem. It can be one of thefollowing strings:MORE THAN ONE MEMBER JOINED XCF GROUPgroupname

The Fast DB Recovery region found that more thanone member attempted to join the XCF group withthe identified imsid and groupname. An XCF groupcan have only one IMS system and one Fast DBRecovery region. A Fast DB Recovery region isalready tracking the IMS system represented byimsid.

XCF GROUP groupname XCF MEMBER STATE IS NOTACTIVE

The Fast DB Recovery region found that the IMSsystem joined the XCF group, but the status is notactive.


Operator responseFor the first form of this message:

If the IMS system represented by imsid is the oneyou want to track and a Fast DB Recovery regionis already tracking it, no action is necessary. If theIMS system is not the one you want to track, specifythe correct GROUPNAME, ACTIVEIMSID, or both, inmember DFSFDRxx in IMS.PROCLIB, or specify thecorrect suffix of member DFSFDRxx in the FDRMBRparameter in the Fast DB Recovery procedure. Restartthe Fast DB Recovery region.

For the second form of this message:

Make sure that the IMS system is enabled forFast DB Recovery. Specify the correct GROUPNAME,ACTIVEIMSID, or both, in member DFSFDRxx.Alternatively, specify the correct suffix of memberDFSFDRxx on the FDRMBR parameter in the Fast DB

Recovery procedure. Restart the Fast DB Recoveryregion.

Module:DFSFDR70

DFS4178E FDR FOR (imsid) IMSID OR XCFGROUP NAME IN CHECKPOINTRECORD AND FDR PROCEDUREARE NOT IDENTICAL

ExplanationThe Fast DB Recovery region found an inconsistency inthe imsid, XCF group name, or both, of the IMS systemin the X'4001' checkpoint begin log record and in theFast DB Recovery procedure. They were not identical.


Operator responseSpecify the correct GROUPNAME parameter in theDFSFDRxx member of IMS.PROCLIB, or specify thecorrect suffix of member DFSFDRxx in the FDRMBRparameter in the Fast DB Recovery procedure. Thenrestart the Fast DB Recovery region.

Module:DFSFDR10

DFS4179E FDR FOR (imsid) IRLM requestFAILED, RC=nn, REASON=xxxx

ExplanationThe IRLM request request issued by the Fast DBRecovery region failed with return code nn and reasoncode xxxx.


Operator responseSee the IRLM request return and reason codeinformation to determine the cause of the error. Aftercorrecting the error, restart the Fast DB Recoveryregion.

Module:DFSFDR00, DFSFDR70

Related tasksIRLM return and reason codes

DFS4180E UNEXPECTED RETURN CODEFROM request, RC=nn



REASON=xxxxxxxx. IMS IS NOTFDR CAPABLE.

or

FDR FOR (imsid) UNEXPECTED RETURN CODE FROMrequest, RC=nn REASON=xxxxxxxx

ExplanationThe Fast DB Recovery region or the identified IMSsystem issued the named XCF request, but the requestfailed with the return code nn and reason codexxxxxxxx. The first form of the message is issued bythe Fast DB Recovery region; the second form is issuedby the IMS system.

System actionIf the Fast DB Recovery region issued this message,the Fast DB Recovery region is terminated. If the IMSsystem issued this message, IMS continues processingwithout Fast DB Recovery.

Operator responseSee the XCF return and reason codes in z/OSMVS Programming: Sysplex Services Reference(SA22-7618). Correct the cause of the error.

Module:DFSFDRA0, DFSFDR70

Related informationz/OS: Abstract for MVS Programming: SysplexServices Reference

DFS4181W FDR FOR (imsid) DB RECOVERYCANNOT START BECAUSE ACTIVESYSTEM IS STILL RUNNING

Explanation:For the explanation and actions, see DFS4181A.

Related informationDFS4181AFDR FOR (imsid) FOR DB RECOVERY, ENTER"RECOV". TO CONTINUE TRACKING, ENTER"TRACK".

DFS4181A FDR FOR (imsid) FOR DBRECOVERY, ENTER "RECOV". TOCONTINUE TRACKING, ENTER"TRACK".

ExplanationDatabase recovery was initiated by the MVS MODIFYcommand (F fdrproc RECOVER). The Fast DBRecovery region issued an IDENTIFY RECOVERYrequest to IRLM to start database recovery, but theidentified IMS system was still running.

System actionThe Fast DB Recovery region waits for the operator'sreply.

Operator responseIf database recovery was invoked by the F fdrprocRECOVER command, make sure that you entered thecorrect command for the correct Fast DB Recoveryregion.

If the correct command was entered for the correctFast DB Recovery region, reply RECOVER to theDFS4181A message.

If the command was not correct or was entered for thewrong region, reply TRACK to the DFS4181A message.

Module:DFSFDR00

DFS4182W FDR FOR (imsid) DB RECOVERYCANNOT START BECAUSE ACTIVESYSTEM IS STILL RUNNING

ExplanationAfter an X'06' log record was detected, the Fast DBRecovery region issued an IRLM IDENTIFY RECOVERYrequest to initiate database recovery. However, theIRLM indicated that the identified IMS system did notissue an IRLM QUIT request.

System actionThe Fast DB Recovery region attempts to issue theIDENTIFY RECOVERY request to IRLM again.

Operator responseIf this message continues to be issued, make surethat the active IMS system has terminated. If it hasnot terminated, force termination of IMS. If the activeIMS system has terminated, issue a MODIFY command(F irlmproc, STATUS) on the active system todetermine the status of the IRLM. If the IRLM is notworking correctly, create an SDUMP and terminate it.If the IRLM is working correctly, it is probably a FastDB Recovery error. Create an SDUMP of the Fast DBRecovery region and terminate it with an MVS MODIFY


https://www-01.ibm.com/support/knowledgecenter/en/SSLTBW_2.4.0/com.ibm.zos.v2r4.ieai700/abstract.htm?lang=en

https://www-01.ibm.com/support/knowledgecenter/en/SSLTBW_2.4.0/com.ibm.zos.v2r4.ieai700/abstract.htm?lang=en

(F) STOP command. Contact IBM Software Support, ifnecessary.

Module:DFSFDR00

DFS4183E FDR FOR (imsid) MODIFYcmdname COMMAND REJECTED.FDR IS IN INITIALIZATION ORRECOVERY PHASE.

ExplanationThe identified MODIFY command was rejectedbecause the Fast DB Recovery region was beinginitialized or was already in a recovery process.

System actionThe Fast DB Recovery region continues its currentprocessing.

Module:DFSFDR60

DFS4185E FDR FOR (imsid) UNEXPECTEDRETURN CODE FROM DBRCSIGNON REQUEST, RC=return code

ExplanationFDR issued a SIGNON request to DBRC and receivedan unexpected return code.


Operator responseResolve the problem; then restart the Fast DBRecovery region.

Module:DFSFDR10

Related referenceReturn codes from Sign-on Normal call(Messages and Codes)

DFS4186E THE HOUR VALUE FOR SDEPTIMEMUST BE BETWEEN 0 AND 23ims_id

Explanation:The SDEPTIME parameter is in 24-hour format, so thehour value must be 00 - 23.

System action:The SDEPTIME parameter is rejected and the defaultvalue of 2300 is taken.


Correct the SDEPTIME parameter in the FASTPATHsection of the DFSDFxxx member. The change takeseffect the next time that IMS is restarted.

Module:DBFFATC1


DFS4187E THE MINUTE VALUE FORSDEPTIME MUST BE BETWEEN 0AND 59 ims_id

Explanation:The minutes value of the SDEPTIME parameter mustbe 0 - 59.


System programmer response:Correct the SDEPTIME parameter in the FASTPATHsection of the DFSDFxxx member. The change takeseffect the next time that IMS is restarted.

Module:DBFFATC1


DFS4188E NON-NUMBER SPECIFIED ASHOUR OR MINUTE FOR SDEPTIMEims_id

Explanation:The hour or minute value of the SDEPTIME parameteris not a valid decimal number.


System programmer response:Correct the SDEPTIME parameter in the FASTPATHsection of the DFSDFxxx member. The change takeseffect the next time that IMS is restarted.

Module:DBFFATC1


DFS4190I IMS SYSTEM IS FDR CAPABLE

ExplanationThis IMS system is enabled for Fast DB Recovery.










System actionProcessing continues with Fast DB Recovery.

Module:DFSZINT0

DFS4191E FDR PROCLIB MEMBER DFSFDRxxCOULD NOT BE ACCESSED

ExplanationThe system was not able to access the data setdefined on the DD statement in member DFSFDRxx ofIMS.PROCLIB.

System actionIf this message is issued by the Fast DB Recoveryregion, the Fast DB Recovery region is terminated. Ifthis message is issued by the IMS system, processingcontinues without Fast DB Recovery.

Operator responseSpecify the correct data set on the IMS.PROCLIB DDstatement. Alternatively, specify the correct suffix ofmember DFSFDRxx on the FDRMBR parameter in theFast DB Recovery procedure. Then restart the IMSsystem or the Fast DB Recovery region.

Module:DFSZINT0

DFS4192E ACTIVEIMSID PARAMETER ISINCORRECT

ExplanationThe imsid specified on the ACTIVEIMSID parameter inIMS.PROCLIB member DFSFDRxx was not identical tothe imsid of the IMS control region being started.

System actionProcessing continues without Fast DB Recovery.

Operator responseIf you want to run the system with Fast DB Recovery,shut down the IMS system. Specify the correctimsid on the ACTIVEIMSID parameter in IMS.PROCLIBmember DFSFDRxx. Then restart the IMS system.

Module:DFSZINT0

DFS4194E IMSCATHLQ HIGH LEVELQUALIFIER INVALID OR MISSING.

ExplanationEither the value that is specified on the IMSCATHLQ=statement in the utility JCL is invalid or no value isspecified.

System actionThe utility terminates. No output is generated.

Operator responseEnsure that the high level qualifier of the IMS catalogis correctly specified on the IMSCATHLQ= statement.For example, IMSCATHLQ=IMS.DFSCD000.

Module:DFS3LU00

Related informationIMS Catalog Library Builder utility (DFS3LU00)(System Utilities)

DFS4195E dd__name DD STATEMENTMISSING.

ExplanationThe JCL for the IMS Catalog Library Builder utility ismissing a required DD statement. The DD statement isidentified in the message text.

In the message text:dd__name

The name of the DD statement that is missing. Thepossible values include:

• ACBLIB• DBDLIB• DBDSOR• PSBLIB• PSBSOR• LUSYSPRT• SYSAIN• SYSLIB• SYSLIN


Operator responseAdd the missing DD statement to the utility JCL.

For the following DD statements, if you do not requirethe associated output, you can correct the error by


http://www.ibm.com/support/knowledgecenter/SSEPH2_15.1.0/com.ibm.ims15.doc.sur/ims_catalog_dfs3lu00.htm#ims_catalog_dfs3lu00


removing the corresponding control parameter fromthe SYSIN DD statement:

• ACBLIB• DBDLIB• DBDSOR• PSBLIB• PSBSOR

After the JCL is corrected, run the utility again.

Module:DFS3LU00

Related informationIMS Catalog Library Builder utility (DFS3LU00)(System Utilities)

DFS4196E THE variable text DATA SET FAILEDTO OPEN. OPEN RC = yy.

ExplanationThe data set that is identified in the message textfailed to open. The return code that is included inthe message text is issued by the IMS catalog API(DFS3CATQ) (System Programming APIs).

In the message text:variable text

Describes the data set that failed to open. Thepossible text values are:

• ACB LIBRARY• CATALOG DIRECTORY• DBD LIBRARY• DBD SOURCE LIBRARY• PSB LIBRARY• PSB SOURCE LIBRARY• SYSAIN• SYSLIN

rcThe return code that was issued by the IMS catalogAPI (DFS3CATQ) (System Programming APIs).

A return code of 20 is an internal error thatindicates that the catalog API returned without anoutput area pointer.


Operator responseConfirm that the data sets are available and correctlyspecified in the JCL.

Look up the return code in the IMS catalog APIdocumentation.

After the problem is corrected, run the utility again.

Module:DFS3LU00

Related referenceIMS Catalog Library Builder utility (DFS3LU00)(System Utilities)IMS catalog API (DFS3CATQ) (SystemProgramming APIs)

DFS4197E UNABLE TO GET CATALOGMEMBER LIST, RC = xxxx.

ExplanationThe IMS Catalog Library Builder utility issued a LISTrequest to the IMS catalog API to retrieve a list ofresources in the IMS catalog. The LIST request failed.


The return code issued by the IMS catalog APILIST request.


Operator responseLook up the return code in the IMS catalog API LISTrequest documentation.


Module:DFS3LU00

Related referenceList request (LIST) for the IMS catalog API(System Programming APIs)IMS catalog API (DFS3CATQ) (SystemProgramming APIs)

DFS4198E UNABLE TO GET CATALOGMEMBER mbr_name, RC = rcUNABLE TO GET CATALOGMEMBER mbr_name, RC = rc, RSN= rsn

ExplanationThe IMS Catalog Library Builder utility issued a GETrequest to the IMS catalog API to retrieve a specificresource from the IMS catalog. The GET request failed.





http://www.ibm.com/support/knowledgecenter/SSEPH2_15.1.0/com.ibm.ims15.doc.spr/ims_spr_ims_catalog.htm#ims_spr_ims_catalog








http://www.ibm.com/support/knowledgecenter/SSEPH2_15.1.0/com.ibm.ims15.doc.spr/ims_catalog_api_list.htm#ims_catalog_api_list

http://www.ibm.com/support/knowledgecenter/SSEPH2_15.1.0/com.ibm.ims15.doc.spr/ims_catalog_api_list.htm#ims_catalog_api_list



mbr_nameThe name of the ACB, DBD, or PSB resource thatthe IMS Catalog Library Builder utility was trying toget from the IMS catalog.

rcThe return code issued by the IMS catalog API GETrequest.

rsnThe reason code issued by the IMS catalog APIGET request.

Table 26. Return and reason codes for DFS4198E


20 An internal errorthat indicates thatthe output areaaddress that wasreturned was zero.

40 8 An invalid ACBLIBmember erroroccurred.


Operator responseLook up the return code in the IMS catalog API GETrequest documentation.


Module:DFS3LU00

Related referenceGet request (GET) for the IMS catalog API(System Programming APIs)IMS catalog API (DFS3CATQ) (SystemProgramming APIs)

DFS4199W A new mode of Resume TPIPErequest needs to be submittedfor IMS synchronous calloutmessages

ExplanationThere were IMS synchronous callout messages in theOTMA TPIPE queue waiting to be retrieved. However,the Resume TPIPE request received was only targetedfor asynchronous output messages.

System actionProcessing continues for only asynchronous calloutmessages.

Operator responseIssue a new Resume TPIPE request with the correctprocessing mode for synchronous callout messagesthat are waiting to be processed.

The byte-3 of OTMA state data prefix can be used toset the Resume TPIPE processing mode. When the flagX'80' is set in the byte, it means the Resume TPIPEcan be issued to retrieve only the synchronous calloutmessages.

When the flag X'40' is set in the byte, it meansthe Resume TPIPE can be issued to retrieve bothsynchronous callout messages and asynchronousmessages. The synchronous callout messages areprocessed and delivered before the asynchronousmessages.

Module:DFSYQAB0

DFS4200I - tcbtype TCB INITIALIZATIONCOMPLETE

ExplanationThe database recovery service completed initializationof the Database Recovery Manager or Recovery DataManager master task control block (TCB). The tcbtypecan be:RWM

The master TCB for database recovery hascompleted initialization.

RWDA daughter TCB for database recovery hascompleted initialization

If the message is issued by the Database RecoveryManager, the message destination is the z/OS systemconsole and the IMS master terminal. If the messageis issued by Recovery Data Manager, the messagedestination is only the z/OS system console.


Module:DFSRVM00, DFSRWM00


http://www.ibm.com/support/knowledgecenter/SSEPH2_15.1.0/com.ibm.ims15.doc.spr/ims_catalog_api_get.htm#ims_catalog_api_get






DFS4201I ttt TASK INITIALIZATION FAILED,reason, RC=return code

ExplanationThe IMS Database Recovery Facility detected an errorduring initialization. The message destination is thez/OS system console and the IMS master terminal (ifthis IMS is DB/DC).

In the message text:ttt

Identifies which class of task detected theproblem.

reasonIdentifies the problem, and is one of the following:

• LOAD module• OBTAIN control block• CREATE DISPATCHER WORK AREA• CREATE WORK UNIT• RELEASE QSAV

return codeRepresents internal diagnostic information.

System actionThe IMS Database Recovery Facility terminatesnormally.

System programmer responseTake the appropriate action for the reason youreceived:OBTAIN control block

Increase the region size in the startup JCL.LOAD module

Ensure that the module named is in the RESLIB forthe IMS.

If the problem is not alleviated by the appropriateaction or if no action is listed for the reason in themessage, record the return code and call IBM SoftwareSupport.

DFS4214I aaaaaaa PIPE FAILUREDETECTED: bbbbbbb, rc =nnnnnnnn

ExplanationAn error occurred for one of two reasons:

• During processing of the initial /RECOVER command,the database recovery service was unable to createan IMS pipe.

• During termination of the Recovery Data Manager,the database recovery service experienced an errorwhile attempting to close or deallocate an IMS pipe.

The message destination is the system console andthe IMS master terminal (if this IMS is DB/DC).

In the message text:aaaaaaa

The type of IMS pipe that experienced the error,which is either CONTROL or RECORD.

bbbbbbbIndicates the pipe failure that was detected and isone of the following:

• ALESERV• BUFSIZE• DSPSERV• ESTAEX• LOAD BUFSIZE• STORAGE• Any other value indicates a z/OS failure.

nnnnnnnnThe return code of the failing service.

System actionThe database recovery service function shuts down.

System programmer responseThe Recovery Data Manager component of databaserecovery service experienced an error whileattempting to obtain storage related to pipeprocessing. Increase your region size.

If bbbbbbb is LOAD BUFSIZE, a module is probablymissing from your SDFSRESL and must be added.

If bbbbbbb is any other value, record the errorinformation and call IBM Software Support forassistance.

Module:


DFSRWMI0, DFSRVWP0, DFSRWPR0, DFSRWPW0

DFS4215I UNABLE TO WRITE TO type PIPE,RC=return code

ExplanationOne of the write-to-pipe subcomponents of thedatabase recovery service detected an error writing toan IMS pipe. The message destination is the systemconsole and the IMS master terminal (if this IMS isDB/DC ).

In the message text:type


return codeThe return code of the failing service.

System actionThe database recovery service terminates the currentrecovery instance.

System programmer responseRecord the error information and call IBM SoftwareSupport for assistance.

Module:DFSRWPR0, DFSRWPW0

DFS4216I DATABASE RECOVERY SERVICEDISABLED FOR type: reason

ExplanationThe database recovery service is unable to detect fullfunction database data sets or Fast Path areas. Themessage destination is the system console and theIMS master terminal (if this IMS is DB/DC).


Indicates one of the following:FULL FUNCTION

The DLISAS region has not been detectedFAST PATH

Fast Path has not been generated into thesystem.

reasonIndicates the reason for failure, and is one of thefollowing functions:

• DLISAS REGION NOT DETECTED• FAST PATH NOT DETECTED

System actionThe database recovery service rejects recoveryprocessing.

System programmer responseTo recover either the FULL FUNCTION or FASTPATH function, enter the /RECOVER and /DISPLAYRECOVERY database recovery service commands onan IMS with the appropriate function enabled.

Module:DFSRWM00

DFS4217I DATABASE RECOVERY SERVICEDISABLED: reason RETURN CODE=return code

ExplanationThe database recovery service is unable to performrecovery on the IMS processing the /RECOVERcommand. The message destination is the systemconsole and the IMS master terminal (if this IMS isDB/DC).

In the message text:reason

Indicates the cause of the error, and is one of thefollowing:

• FACILITY NOT INSTALLED• DLISAS REGION AND FAST PATH NOT

DETECTED• UNABLE TO ATTACH ORS TCB• CREATE ADDRESS SPACE ERR• UNABLE TO LOAD MODULES• GET ORS STORAGE FAILURE

return codeA macro return code.

System actionThe database recovery service rejects recoveryprocessing.

System programmer responseTake the appropriate action based on the reasonreceived:UNABLE TO LOAD MODULES

Increase the region size for the IMS processingthe /RECOVER command.

FACILITY NOT INSTALLEDThe recovery facility was not detected duringprocessing of the /RECOVER command. RETURN


CODE = 0 means the database recovery service isnot installed. Issue the /RECOVER command on anIMS where the recovery facility is installed.

DLISAS REGION AND FAST PATH NOT DETECTEDRun the database recovery service on an IMS thathas the function in the message.

UNABLE TO ATTACH ORS TCBCheck the return code for the ATTACH macro andtake appropriate action.

CREATE ADDRESS SPACE ERRCheck the return code for the ASCRE macro andtake appropriate action.

GET ORS STORAGE FAILUREIncrease the region size for the IMS processingthe /RECOVER command.

If you followed the specified action for the reasonlisted in the message and the problem did not resolve,record the error information and contact IBM SoftwareSupport for assistance.

Module:DFSRWMI0, DFSRWM00

Related referencez/OS: ATTACH return codesz/OS: ASCRE macro return and reason codes

DFS4218I UNABLE TO READ FROM typePIPE, RC =return code

ExplanationThe database recovery service detected an error whilereading from the pipe indicated by type. The messagedestination is the system console and the IMS masterterminal (if this IMS is DB/DC).



return codeThe return code of the failing service.

System actionThe database recovery service terminates the currentrecovery instance.

System programmer responseRecord the error information and call IBM SoftwareSupport for assistance.

Module:DFSRWPR0, DFSRVPR0






DFS4260I ERROR DETECTED FORCOMMAND: RECOVER ADD,REASON=reason

ExplanationA command error was detected for an databaserecovery service related command.


If the reason is NOTHING TO ADD, processingcontinues. If the reason is DBRC STORAGEFAILURE, recovery processing terminates for thisrecovery instance.

System programmer responseThis message indicates an internal IMS error. Thecommand is ignored.

Problem determinationSet a SLIP TRAP on the error message, then call IBMSoftware Support for assistance.

ModuleDFSRWCM0, DFSRWCR0, DFSRWCD0, DFSRWCP0,DFSRWCA0, DFSRWME0

DFS4261I UNABLE TO ADD TO rcvlistentrytype entryname: reason

ExplanationThe entryname specified in the /RECOVER ADDcommand could not be added to the specified recoverylist. If a recovery list was not specified in the /RECOVER ADD command, "To rcvlist" is notincluded in the message text.

If a duplicate entry was detected, the duplicate isignored. The message destination is the z/OS systemconsole and the IMS master terminal (if this is a DB/DCIMS). This message is also sent to the issuer of thecommand.

In the message text:rcvlist

The specified recovery list.

entrytypeIf a member of a group is not part of theACBGEN for the IMS processing the /RECOVERADD command or is not defined in the RECON,"entrytype" is not included in the message.

entrytype is one of the following:

• DBDS• AREA• DATABASE• GROUP (if DBDSGRP, CAGRP, DATAGROUP, or

RECOVGRP was specified in the /RECOVERcommand)

entrynameA keyword specified on the /RECOVER ADDcommand and is one of the following: DB, DBDS,DBGRP, DBDSGRP, or CAGRP.

reasonThe reason can be one of the following:ALREADY ON RECOVERY LIST

The entry listed is already on the recovery listspecified by rcvlist.

ALREADY STARTEDThe recovery list specified by rcvlist alreadystarted recovery processing.

COMMAND TOO LONGThe number of elements specified on the /RECOVER ADD command is larger than thatallowed by the recovery product for a single /RECOVER ADD command. Split the /RECOVERADD command into multiple commands.

DATABASE IS OLR CAPABLEThe object specified by entryname is OLRcapable and the /RECOVER ADD commandwas issued to a release of IMS that doesnot support recoveries with OLR capabledatabases. Rerun the recovery on a level ofIMS that supports OLR capable databases.

DATABASE HAS NO DATA SETSThe database does not have any database datasets defined to it.

DATABASE IS DEFINED AS GSAMThe database recovery service cannot recoverGSAM database types.


DLI/SAS REGION UNDETECTEDThe /RECOVER ADD command attempted toadd a full function DBDS to the recovery list ona system that does not have a DL/I SAS region.

FAST PATH NOT INSTALLEDThe /RECOVER ADD command attempted toadd a Fast Path AREA to the recovery list on asystem that does not have FP installed.

INDEX OR ILE DATA SETThe DBDS has not been added to the recoverylist because it is either a Primary index or ILDSdata set and cannot be recovered. These datasets are recovered by the Index/ILDS Rebuildutility.

NOT DEFINED IN RECONThe entry specified by entryname is not definedfor RECON.

NOT FOUND IN ACBGENThe entry specified by entryname is not definedto the IMS issuing the message. It is possiblethat the entry is not defined in IMS Stage 1.

NOTHING ADDEDNothing was added to the recovery list.

UNKNOWN REASON FROM DBRCDBRC encountered an unexpected conditionand returned an unknown reason code to theDatabase Recovery Manager.

INVALID SMSOPTS PARAMETERAn unsupported or incorrect SMSOPTSparameter is detected. Message DFS4289follows this message. For more information,see DFS4289.

System actionThe database data sets that make up the entrynameare not added to the recovery list. The databases,areas, or both are not recovered by the databaserecovery service.

System programmer responseExamine the /RECOVER ADD command and compareit with the corresponding ACBGEN or RECON entries.Reissue the command with the correct entry names.

If reason is UNKNOWN REASON FROM DBRC, call IBMSoftware Support for assistance.

ModuleDFSRWCA0

Related information“DFS4289” on page 1184SMS_OPTION IGNORED

DFS4262I INVALID RESPONSE FROM DBRCFOR COMMAND RECOVER ADD,REASON=reason

ExplanationDBRC returned an invalid response due to a databaserecovery service related command. The messagedestination is the z/OS system console and the IMSmaster terminal (if this is a DB/DC IMS). This messageis also sent to the issuer of the command.


The reason code returned by DBRC, which isinternal diagnostic information.

System programmer responseThis message indicates an internal IMS error. Thecommand is ignored.

Problem determinationSet a SLIP TRAP on the error message, and call IBMSoftware Support for assistance.

ModuleDFSRWCR0, DFSRWCD0, DFSRWCP0, DFSRWCA0

DFS4263I THE FOLLOWING ENTRIES AREADDED TO THE RECOVERY LISTtoken:

ExplanationThis message is followed by a series of DFS4265Imessages. It indicates that one or more entries wereadded to the recovery list as a result of the /RECOVERADD command. token is supplied by the user on the /RECOVER ADD command or generated by IMS.

The message destination is the z/OS system consoleand the IMS master terminal (if this is a DB/DCIMS). This message is also sent to the issuer of thecommand.

System actionThe database data set or area name listed in thesubsequent DFS4265I messages are added to therecovery list.



ModuleDFSRWCA0

Related information“DFS4265I” on page 1175name AUTHORIZED BY ssid

DFS4264I RECOVERY STARTED FOR(options):

ExplanationThe /RECOVER START command was issued andno errors were detected. Database recovery serviceprocessing started for the database data set andareas listed in the subsequent DFS4265I messages.options specifies parameters on the /RECOVERSTART command. If no parameters were specified, thefollowing default values for the options are listed:

ERRORCONTSTAGLOBALSTALOCALNOSTA


System action/RECOVER START command processing continues.


ModuleDFSRWCS0

DFS4265I name AUTHORIZED BY ssid

ExplanationThis message lists the database data set or area thatthe database recovery service started a recovery for.Either DFS4263I or DFS4264I follows this message.The message destination is the z/OS system consoleand the IMS master terminal (if this is a DB/DCIMS). This message is also sent to the issuer of thecommand.


Indicates the database data set name (dbnameddname) or area name for recovery.

ssidIf the database data set or area is authorized byan IMS, ssid identifies the authorizing ssid. Thismessage is issued for each IMS that authorized adatabase data set or area in the recovery list.

System action/RECOVER command processing continues.


ModuleDFSRWCA0, DFSRWCS0, DFSRWCR0, DFSRWCP0

DFS4266I UNABLE TO RECOVER: dbname,reason

ExplanationA database recovery service /RECOVER STARTcommand was issued, but the database data set orarea cannot be recovered. The message destination isthe z/OS system console and the IMS master terminal(if this is a DB/DC IMS). This message is also sent tothe issuer of the command.


Identifies the database data set or area that couldnot be recovered.

reasonIndicates the cause of the error and is one of thefollowing:AUTHORIZATION FAILED, RC = XX

Authorization processing failed to properlyauthorize one or more of the database datasets or areas in the recovery list. XX identifiesthe DBRC return code.

HALDB MASTER IS STOPPEDThe master database for a HALDB partitionhas been stopped. Although the databaserecovery service requires that the partitionsbeing recovered be stopped, the masterdatabase must be started. Start the masterdatabase, and then reissue the /RECOVERSTART command.

IMAGE COPY NOT AVAILABLEDBRC was unable to locate a usable imagecopy for the database data set.


INVALID RCVTIMEDBRC determined that the RCVTIME specifiedfalls in the middle of an ALLOC for this entry,and the PITR option was not specified.

LOGS MARKED IN ERRORDBRC determined that none of the log datasets are usable. They may be marked in error.

NEEDS HIGHER RELEASE LOGDBRC detected logs created by a higherrelease IMS. The database cannot be selectedif it was updated by an IMS operating at ahigher release.

NO IC TAKEN AFTER A PITRRecovery for the database data set or areafailed because a point-in-time (PITR) recoverywas performed earlier and no image copy wastaken afterward. Because backout informationmay have been deleted from the RECON dueto the prior PITR recovery, a new recovery mayresult in a corrupted database.

NO PRILOG FOUNDDBRC was unable to locate a PRILOG record.This condition should not occur. Call IBMSoftware Support for assistance.

NO RECOV RECORD FOUNDThe USEDBDS option was specified on the /RECOVER ADD command, but the latestrecovery recorded in RECON was not for atime stamp recovery, or the DBDS or AREA ismarked in RECON as needing recovery.

NOT FOUND

One or more of the database data sets or areasin the recovery list is not listed in the RECONdata set.

If the database data set or area has beenremoved from the system in Online Changeand no longer needs to be recovered, usethe /RECOVER REMOVE command to removethe data set or area from the recovery list.If the database data set or area has beenremoved from the system in Online Change andnow must be recovered, use Online Change toadd it back to the system; then re-issue the /RECOVER START command.

NOT OFFLINEOne or more of the database data sets or areasin the recovery list was not taken offline withan IMS /DBR command. When the database isin this state, proper operation of the databaserecovery service cannot be guaranteed.

RECOV RECORD UNUSABLEThe USEDBDS option was specified on the /RECOVER ADD command, but the DBDS or

AREA has been updated or reorganized sincethe latest recovery recorded in the RECON.

REORG LATER THAN IMAGE COPYThe REORG utility ran against the databasedata set but there is no subsequent image copydata set registered in the RECON.

System actionIf ERRORCONT was specified for the database dataset or area, processing continues for the remainingmembers in the database recovery service recoverylist. If ERRORCONT was not specified, recovery stops.

System programmer responseTake the appropriate action based on the specifiedreason:AUTHORIZATION FAILED

Determine which IMS did not stop the appropriatedatabase or area, then stop the database or areawith the IMS /DBR command.

HALDB MASTER IS STOPPEDThe master database for a HALDB partition mustbe started for recovery. Start the master databaseand reissue the /RECOVER START command.

IMAGE COPY NOT AVAILABLEVerify that an image copy is available for thedatabase data set and not migrated to another site.

INVALID RCVTIMENon-PITR time stamp recoveries cannot fall in themiddle of an ALLOC boundary. Adjust the timeused for the time stamp recovery or reissue the /RECOVER START command specifying PITR.

LOGS MARKED IN ERRORVerify that the log data sets are available and notmigrated to another site.

NEEDS HIGHER RELEASE LOGSLogs created on a higher release IMS cannot beused for recovery on a lower release IMS. Thissituation can occur when running multiple IMSsystems in coexistence mode. Rerun the recoveryon the level of IMS in which the logs were created.

NO PRILOG FOUNDContact IBM Software Support for assistance.

NO IC TAKEN AFTER A PITRAfter a point-in-time recovery, take an image copyso that subsequent recoveries have a valid startingpoint. If you know the integrity of the database willnot be compromised, delete the RECOV record byusing the DBRC DELETE.RECOV command, thenrerun the recovery.


NO RECOV RECORD FOUNDRecover the DBDS or AREA using a nonstandardimage copy. Then inform DBRC of the recovery witha NOTIFY.RECOV command specifying the timethat the recovery was run (current), and the time towhich the DBDS or AREA was recovered. Then thedatabase recovery service can be used to recoverthe DBDS or AREA with the USEDBDS parameter.

NOT FOUNDThe database data set or area was deleted fromthe RECON data set after the /RECOVER ADDcommand was issued. If the database data setor area is legitimate and needs to be recovered,define it in RECON.

NOT OFFLINEThe database data set or area was not stopped onthe IMS performing recovery. Stop the database orarea with the IMS /DBR command.

RECOV RECORD UNUSABLEChanges have been made to the DBDS or AREAsince the last recovery; as a result, you must runthe recovery again. Recover the DBDS or AREAusing a nonstandard image copy. Then informDBRC of the recovery with a NOTIFY.RECOVcommand specifying the time that the recoverywas run (current) and the time to which theDBDS or AREA was recovered. Then the databaserecovery service can be used to recover the DBDSor AREA with the USEDBDS parameter.

REORG LATER THAN IMAGE COPYA DBDS or AREA cannot be recovered using animage copy taken prior to a reorganization.

ModuleDFSRWCS0

DFS4267I RECOVERY NOT STARTED, reason

ExplanationThe database recovery service /RECOVER STARTcommand was issued but recovery cannot continue,as indicated by reason:DBRC AUTHORIZATION FAILURE

An IMS has one or more database data sets orareas authorized in the recovery list.

DBRC RECOVER START FAILUREAn IMS internal error in DBRC caused the recoveryto fail.

ERRORABORT SPECIFIEDAn error was detected with one database dataset or area while the database recovery serviceattempted to start recovery, and ERRORCONT wasspecified on the /RECOVER START command. For

more information about the type of failure, seeDFS4266I.

INCOMPLETE RECOVERY GROUPRecovery failed because one or more members ofa recovery group were not included in the recoverylist. This message is followed by one or moreDFS4284I messages listing the members of therecovery group that are not in the recovery list.

NO RECOVERABLE ENTRIESNone of the entries in the recovery list can berecovered due to one or more errors.

ONLINE CHANGE IN PROGRESSA /MODIFY COMMIT or INITIATE OLCPHASE(COMMIT) command was in progress whenthe /RECOVER START command was issued.The /RECOVER START command is rejected.

RECOVERY LIST NOT FOUNDNo recovery list was found with a token matchingthe one provided with the command.

RECOVERY NOT STARTED, ALREADY IN PROGRESSThe recovery was not started because it is alreadyprocessing.

RECOVERY NOT STARTED, OTHER RECOVERY INPROGRESS

The recovery was not started because anotherrecovery is currently in progress.

RECOVERY TIME GREATER THAN RUN TIMEThe input recovery time on a /RECOVER STARTcommand is greater than the current time.

UNABLE TO CREATE ITASKAn IMS internal error caused the recovery to fail.Report the problem to IBM Software Support.

UNABLE TO GET CCCCCCCCCCAn IMS internal error caused the recovery to fail.Report the problem to IBM Software Support.CCCCCCCCCC is one of the following IMS internalresources:

• QSAV• PST• EPST• APSB LATCH• PSBP LATCH• AUTHORIZATION PARM LIST


System actionThe current database recovery service recoveryinstance is aborted.


System programmer responseTake the appropriate action based on the reasonreceived:DBRC AUTHORIZATION FAILURE

Either the IMS is out of storage or an internalIMS failure occurred. See previously issued DBRCmessages for additional information. If you cannotdetermine the cause of the error, call IBM SoftwareSupport for assistance.

DBRC RECOVER START FAILUREEither the IMS is out of storage or an internalIMS failure occurred. See previously issued DBRCmessages for additional information. If you cannotdetermine the cause of the error, call IBM SoftwareSupport for assistance.

ERRORABORT SPECIFIEDCorrect the error and restart recovery. SeeDFS4266I for the proper action.

INCOMPLETE RECOVERY GROUPSpecify the whole group, redefine the group, donot specify PITR (point in time recovery), orspecify NOCHECK. See DFS4284I for additionalinformation.

NO RECOVERABLE ENTRIESPrior messages should have been issued regardingfailures for each entry. See the previous messagesfor the appropriate action.

ONLINE CHANGE IN PROGRESSReissue the /RECOVER START command whenthe /MODIFY COMMIT or INITIATE OLCPHASE(COMMIT) command completes.

RECOVERY LIST NOT FOUNDCreate a recovery list with the name you specifiedor enter the name of an existing list.

RECOVERY NOT STARTED, ALREADY IN PROGRESSThe recovery is running. No action is necessary.

RECOVERY NOT STARTED, OTHER RECOVERY INPROGRESS

Stop the other recovery or wait until it finishes.RECOVERY TIME GREATER THAN RUN TIME

Enter the command /RECOVER START with thecorrect time to start recovery.

UNABLE TO CREATE ITASKEither the IMS is out of storage or an internalIMS failure occurred. If you cannot determine thecause of the error, call IBM Software Support forassistance.

UNABLE TO GET CCCCCCCCCCEither the IMS is out of storage or an internalIMS failure occurred. If you cannot determine thecause of the error, call IBM Software Support forassistance.

ModuleDFSRWCI0

Related information“DFS4266I” on page 1175UNABLE TO RECOVER: dbname, reason“DFS4284I” on page 1183RECOVERY GROUP grpname MEMBER memberNOT IN RECOVERY LIST

DFS4268I THE FOLLOWING ENTRIES WEREREMOVED FROM THE RECOVERYLIST:

ExplanationThis message is followed by a series of DFS4265Imessages. It indicates that one or more entrieswere removed from the recovery list as a result of /RECOVER REMOVE command.

System actionThe names listed in the subsequent DFS4265Imessages are removed from the recovery list.



ModuleDFSRWCR0

DFS4269I RECOVERY LIST IS NOW EMPTY

ExplanationOne of the following instances occurred:

• The /RECOVER REMOVE command processed andremoved the last database data set or area from therecovery list.

• The /RECOVER REMOVE ALLENTS commandprocessed.

• The /RECOVER STOP command processed andstopped the last database data set or area in therecovery list.

• The /RECOVER STOP ALLENTS commandprocessed.

The message destination is the z/OS system consoleand the IMS master terminal (if this is a DB/DC


IMS). This message is also sent to the issuer of thecommand.

System actionThe recovery instance is deleted.


ModuleDFSRWCR0, DFSRWCP0

DFS4270I UNABLE TO REMOVE resource_typeresource_name: reason

ExplanationAn database recovery service /RECOVER REMOVEcommand was issued but could not process. Themessage destination is the z/OS system console andthe IMS master terminal (if this is a DB/DC IMS). Thismessage is also sent to the issuer of the command.

In the message text:resource_type

Identifies the type of resource the /RECOVERREMOVE command was issued against, and is oneof the following:

• LIST• DBDS• AREA• DB

resource_nameIdentifies the name of the resource specified inthe /RECOVER REMOVE command.

reasonIndicates one of the following causes for thefailures:COMMAND TOO LONG

The number of elements specified on the /RECOVER REMOVE command is larger thanthat allowed by the recovery product fora single /RECOVER REMOVE command.Split the /RECOVER REMOVE command intomultiple commands.

NOT IN RECOVERY LISTThe database data set or area specified in thecommand was not part of the recovery list.

NOT DEFINED IN RECONThe DB, CAGRP, DBDSGRP, or DATAGROUPresource types could not be found in RECON.

NOTHING REMOVEDNo database data set or area was removed as aresult of the /RECOVER REMOVE command.

RECOVERY IN PROGRESSA /RECOVER REMOVE command was issuedwhen recovery was in progress for the recoverylist.

RECOVERY LIST DOES NOT EXISTA /RECOVER REMOVE command was issued,but the identified recovery list does not exist.

THIS IS A FAST PATH AREAA /RECOVER REMOVE DBDS was specified inthe command, but the entry was a Fast Patharea.

THIS IS NOT A FAST PATH AREAA /REC REMOVE AREA AREA name commandwas entered and the AREA name identified anFF DBDS in the recovery list.

Determine the appropriate AREA name, orenter /RECOVER REMOVE DBDS dbd dbds.

System actionIf the resource_type is LIST, the /RECOVER REMOVEcommand is aborted. Otherwise, processing continuesfor those resources not identified by the error.

System programmer responseDetermine why the command failed and if necessary,reissue the command.

ModuleDFSRWCR0

DFS4273I RECOVER command COMMANDREJECTED, rsn

ExplanationA /RECOVER command is rejected because of the rsnlisted in the message.

In the message text:command


• ADD• REMOVE• START• STOP

rsnOne of the following:


DRF WAS UNABLE TO STARTA failure during database recovery initializationresulted in the /RECOVER command beingrejected. See accompanying messages andcorrect the problem before issuing the /RECOVER command.

RECOVERY ADDRESS SPACE FAILEDA failure during database recovery addressspace initialization resulted in the /RECOVERcommand being rejected. See accompanyingor related messages and correct the problembefore issuing the /RECOVER command.

TERMINATION IN PROGRESSThe recovery environment is terminating dueto a /RECOVER TERMINATE command. Waitfor termination processing to complete beforeissuing the /RECOVER command.

FEATURE NOT INSTALLEDIMS is unable to detect the presence ofa database recovery product. If a databaserecovery product is installed, ensure that IMShas access to the libraries containing thedatabase recovery product before issuing the /RECOVER command.

System actionThe /RECOVER command is rejected.

System programmer responseTake the appropriate action described in the messageexplanation section. If the rsn indicates that aninternal error exists, report the symptom and alldiagnostic data to IBM. If the rsn indicates acorrectable condition, correct the error and issue the /RECOVER command.

ModuleDFSRWM00

DFS4274I UNABLE TO STOPresource_typeresource_name:reason

ExplanationAn database recovery service /RECOVER STOPcommand was issued but could not process. Themessage destination is the z/OS system console andthe IMS master terminal (if this is a DB/DC IMS). Thismessage is also sent to the issuer of the command.


resource_typeIdentifies the type of resource the /RECOVERSTOP command was issued against, and is one ofthe following:

• LIST• DBDS• AREA• DB

resource_nameIdentifies the name of the resource specified inthe /RECOVER STOP command.

reasonIndicates the cause of the error, and is one of thefollowing:RECOVERY NOT IN PROGRESS

A /RECOVER STOP command was issuedwhen recovery was not in progress.

NOT IN RECOVERY LISTThe database data set or area specified in thecommand is not in the recovery list.

NOT IN RECONThe DB, CAGRP, DBDSGRP or DATAGROUPresource type was not found in RECON.

SAVE REQUIRES ALLENTA /RECOVER STOP command was issued withthe SAVE option, but ALLENTRIES was notspecified.

NOTHING REMOVEDNo database data set or area was stopped as aresult of the /RECOVER REMOVE command.

THIS IS A FAST PATH AREAA /RECOVER STOP command was issued withthe DBDS option, but the entry is a Fast Patharea.

System actionIf the resource_type is LIST, then the /RECOVER STOPcommand aborts. Otherwise, processing continues forother resources.

System programmer responseDetermine why the command failed and if necessary,reissue the command.

ModuleDFSRWCP0

DFS4275I THE FOLLOWING ENTRIES WILLHAVE RECOVERY STOPPED:


ExplanationThis message is followed by a series of DFS4265Imessages. It indicates that one or more entries willhave recovery stopped as a result of the /RECOVERSTOP command. The message destination is the z/OSsystem console and the IMS master terminal (if this isa DB/DC IMS). This message is also sent to the issuerof the command.

System actionThe name listed in the subsequent DFS4265Imessages will have their recovery stopped.


ModuleDFSRWCP0

DFS4277I RECOVERY COMPLETE FOR:dbdname ddname

ExplanationThe database recovery service issues this messagefor each entry in the recovery list for which recoverycompleted. dbdname ddname represents the DBDS orAREA that completed recover.


System actionIf STAGLOBAL was specified in the original /RECOVER command for name, the DBDS or AREAis automatically started globally. If STALOCAL wasspecified, it is automatically started in the IMS issuingthe message.


Module:DFSRWME0

DFS4278I UNABLE TO COMPLETE RECOVERYFOR: dbdname ddname

ExplanationThe database recovery service is unable to completerecovery for the DBDS or AREA specified dbdname and

ddname. This can be a result of a DBDS or AREA failurethat occurred during recovery, or failure to restore theImage Copy for the DBDS or AREA.


System actionNone.

System programmer responseDetermine the cause of the failure and rerun recoverywhen corrected.

ModuleDFSRWME0

DFS4279I THE FOLLOWING ENTRIES AREAUTHORIZED TO AN IMS:

ExplanationThe database recovery service detected full functiondatabase data sets, Fast Path areas, or both duringrecovery to any time-stamp recovery that might needto be recovered. The database data sets and areasbeing recovered are updated by units of recoverythat also update the ones identified in subsequentDFS4265I messages.


System actionNone.

System programmer responseDetermine if the database data sets, areas, or bothlisted in subsequent DFS4265I messages need to berecovered to the same point in time as the recoverythat caused this message.

Module:DFSRWPR0

Related information“DFS4265I” on page 1175name AUTHORIZED BY ssid

DFS4280I UNABLE TO START type FOR THERECOVERY LIST token, RC=returncode


ExplanationThe database recovery service is unable to start theareas or databases, indicated by type, associated withthe recovery token The message destination is thez/OS system console.

System actionThe areas or databases are recovered but not started.

System programmer responseIssue the /START AREA, UPDATE AREASTART(ACCESS) or /START DATABASE command.Report this failure to IBM Software Support.

Module:DFSRWME0

DFS4282A ERROR PROCESSING PROCLIBMEMBER DFSORSXX: error

ExplanationAn error was detected while processing the IMSPROCLIB member DFSORSxx. One or more DFS4282Amessages might be issued, depending on the numberof errors detected. The /RECOVER command that wasprocessing fails.

In the message text, error is one of the followingproblems:FAILURE PARSING, IKJPARS RC = rc

The TSO IKJPARS service detected an error in theparameters specified in the DFSORSxx member.IKJPARS returned the code shown as rc.

PARAMETER IN ERROR: yyyyAn invalid value was detected on a parameter inDFSORSxx. The incorrect parameter is indicated byyyyy.

TSO ENVIRONMENT IS NOT AVAILABLEThe TSO environment was not available. As aresult, the DFSORSxx member could not beprocessed.

UNABLE TO DELETE STORAGE, IMODULE RC = rcThe DFSORSxx member parsing module,DFSRWPP0, was unable to free working storageit had obtained to process the member. IMODULEGETMAIN returned the code shown as rc. Forinformation about IMODULE return codes, see theIMS system services return code information.

UNABLE TO OBTAIN STORAGE, IMODULE RC = rcThe DFSORSxx member parsing module,DFSRWPP0, was unable to obtain the storagenecessary to process the member. IMODULEGETMAIN returned the code shown as rc. For

information about IMODULE return codes, see theIMS system services return code information.

System actionThe /RECOVER command that was processing fails.

Operator responseTake the appropriate action for the error you received:FAILURE PARSING, IKJPARS RC = rc

From the messages in the SYSTSPRT dataset, determine the parameters in error in theDFSORSxx member. Correct the parameters andreissue the /RECOVER command.

PARAMETER IN ERROR: yyyyCorrect the parameters indicated in DFSORSxx andreissue the /RECOVER command.

TSO ENVIRONMENT IS NOT AVAILABLEEnsure that the TSO environment is available andresubmit the job.

UNABLE TO DELETE STORAGE, IMODULE RC = rcMake note of the message and IMODULE returncode and report the problem to IBM SoftwareSupport. No immediate corrective action isrequired; however, this message might be a sign ofan internal logic error within IMS or problem with(IMS or z/OS) storage management.

UNABLE TO OBTAIN STORAGE, IMODULE RC = rcDetermine the reason for IMODULE GETMAINfailure based on the reason code. If the problemis due to fragmented storage, you might need toissue an z/OS IPL.

Module:DFSRWPP0

Related referencez/OS: Checking return codes from the ParseService RoutineIMS system services return codes (Messagesand Codes)

DFS4283I EARLY END OF RECOVERY FOR:token

ExplanationThe database recovery service is ending early due toa failure that was encountered during the recovery.This error occurs if ERRORABORT was specified onthe /RECOVER START command and a DBDS or AREAfailure occurred during recovery, or the image copy forthe DBDS or AREA failure to restore.

The message destination is the z/OS system consoleand the IMS master terminal (if this is a DB/DC IMS).


http://www-01.ibm.com/support/knowledgecenter/SSLTBW_2.4.0/com.ibm.zos.v2r4.ikjb700/pretc.htm?lang=en

http://www-01.ibm.com/support/knowledgecenter/SSLTBW_2.4.0/com.ibm.zos.v2r4.ikjb700/pretc.htm?lang=en



This message is also sent to the LTERM that issuedthe /RECOVER START command.

System action:None.

System programmer responseDetermine the cause of the failure, correct it, thenrerun the recovery.

Module:DFSRWME0

DFS4284I RECOVERY GROUP grpnameMEMBER member NOT INRECOVERY LIST

ExplanationThe /RECOVER START command was issued withmembers of the recovery group indicated in themessage by grpname. However, not all members ofthe recovery groups are in the recovery list. DFS4284Iis issued for each member of the recovery list. Thismessage follows message DFS4267I.

In the message text:grpname

The name of the recovery groups.member

The database or area name in the recovery group.


System programmer responseAdd all the members of the recovery groups to therecovery list using the /RECOVER ADD command, thenissue /RECOVER START, or issue /RECOVER STARTwith the NOCHECK parameter specified.

DFS4285I END OF RECOVERY FOR: token

ExplanationThe Online Recovery Service issues this messagewhen all recovery processing for the current recoverycompletes. token represents the recovery list tokenspecified on the /RECOVER START command whichinitiated this recovery.



ModuleDFSRWME0

DFS4286I DATABASE RECOVERY SERVICE ISBEING TERMINATED

ExplanationA /RECOVER TERMINATE command was issued, andthe database recovery service is being removed fromthe system.

System actionThe database recovery service resources are releasedby IMS.


ModuleDFSRVM00

DFS4287I DATABASE RECOVERY SERVICEHAS TERMINATED

ExplanationA /RECOVER TERMINATE command was issued, andthe database recovery service terminated.

System actionThe database recovery service resources are released.


ModuleDFSRVM00

DFS4288I DATABASE RECOVERY SERVICE ISUNABLE TO TERMINATE

ExplanationA /RECOVER TERMINATE command was issued whilea recovery was in progress.



System programmer responseWait until the current recovery completes beforeissuing the /RECOVER TERMINATE command. Youcan use the /REC STOP ALLENT command to stopthe current recovery if you do not need it to complete.

ModuleDFSRVM00

DFS4289 SMS_OPTION IGNORED

ExplanationThe SMS_OPTION is not supported and was rejected.The /RECOVER ADD command failed. This messagefollows DFS4261I.

System actionORS recovery does not start.

System programmer responseIssue the /RECOVER ADD command with supportedSMSOPTS parameters.

ModuleDFSRWCA0

Related information“DFS4261I” on page 1173UNABLE TO ADD TO rcvlist entrytype entryname:reason

DFS4299I xxxx

ExplanationA message was issued by the IMS Online RecoveryService ORS. The 'message-id' and 'message-text' aredocumented in the IMS Online Recovery Service forz/OS, User's Guide (SC27-0944).

System actionThe system response is documented in the IMS OnlineRecovery Service for z/OS, User's Guide.

Operator response:(master terminal) Take the appropriate actionidentified for the 'message-id' in the IMS OnlineRecovery Service for z/OS, User's Guide.

User responseTake the appropriate action identified for the'message-id' in the IMS Online Recovery Service forz/OS, User's Guide.

ModuleDFSRWPR0


Chapter 89. DFS messages, DFS4301E - DFS4350E


DFS4304E CALL TO DBRC FAILED. RC=retcode

ExplanationDBRC was called from DFSKARC0, but the processingdid not complete successfully.

System actionProcessing terminates with condition code of 8.

User responseDetermine the problem and resubmit the job. Theproblem might be due to one of the following:

• The SYSIN input should consist of the characterstring LIST.LOG; however, the SYSIN input could beinvalid or omitted.

• DD statements for the RECON data sets might nothave been included in the JCL.

• The IMS level of the RECON data sets might notmatch the level of the IMS.SDFSRESL included in theJOBLIB or STEPLIB DD statements in the JCL.

You can use the SYSPRINT output from DFSKARC0 todetermine the problem.

Module:DFSKARC0

DFS4305W THE MAXIMUM NUMBER OFVOLSERS WAS EXCEEDED FORTHE DATA SET: data set name

Explanation:The indicated data set spans multiple volumes. Themaximum number of volumes that are automaticallyextracted by utility DFSKARC0 is 8; however in thiscase, the number of VOLSERS exceeds this value. Thefirst 8 VOLSERS are included in the generated JCL;however any subsequent VOLSERS are omitted.

System action:Processing continues. At the end of processing, acondition code of 4 is returned.

System programmer response:Update the generated JCL to supply the omittedVOLSER values to the DD statement associated withthe indicated data set name before submitting the JCL.

Module:DFSKARC0

DFS4309E REQUIRED KEYWORD keyword/HAS NOT BEEN SPECIFIED

ExplanationThe indicated keyword is required, but was notincluded with the control statements for the utility.


User responseSpecify a value for the keyword and resubmit the job.

Module:DFSKARC0

DFS4310E PREVIOUS CONTROL STATEMENTCONTAINED NO VALIDKEYWORDS

ExplanationA control statement was encountered that did notcontain any valid keywords.


User responseCorrect or remove the control statement and resubmitthe job.

Module:DFSKARC0

DFS4311E TIMESTAMP CONTROLSTATEMENTS MUST INCLUDECENTURY

ExplanationStart or Stop of date-related keywords that containedvalues which did not begin with the century portion ofa date.



User responseCorrect the control statement and resubmit the job.

Module:DFSKARC0

DFS4312E NO LOG DATASETS FOUNDMATCHING SELECTION CRITERIA

ExplanationNo entries in RECON match the combination ofSSID, STRTTIME, or STOPTIME that was specified inCNTLCRDS.


User responseDetermine what the appropriate selection criteriashould be and resubmit the job. The SYSPRINT outputfrom DFSKARC0 can be used to determine whichsubsystems and time periods are appropriate.

Module:DFSKARC0

DFS4313I FEWER LOGS MATCHEDSELECTION CRITERIA THANWERE REQUESTED

ExplanationThe LOGCOUNT= parameter specified a number of logdata sets to be selected; however, fewer log data setsmatched the selection criteria specified in the controlstatements.



Module:DFSKARC0

DFS4320E SOME LOG DATA SET NAMES AREUNAVAILABLE BECAUSE THEYWERE CHANGED BY DBRC PRILOGRECORD COMPRESSION. THE LOGDATA SET NAMES WERE NOTEXTRACTED.

ExplanationDBRC PRILOG record compression replaced the dataset name for sets of log data sets with the characterstring DSN=**** COMPRESSED DATA SET **** inthe RECON data sets for the time range specified forprocessing by utility DFSKARC0. Because the data setnames are no longer present in RECON, DFSKARC0 isnot able to extract them.


If a range of log data set names are found withinthe time range specified for processing by DFSKARC0that have not been subject to DBRC PRILOG recordcompression, an indication of this subset of timeranges is included in the summary report generatedby DFSKARC0. At end of processing, a condition codeof 8 is returned.

Programmer responseSupply STRTTIME and STOPTIME control statementsto restrict the utility to a range for which log data setnames are available, and resubmit the utility.

Module:DFSKARC0

DFS4321I ACTIVE OLDS DATA SET: data setname WAS NOT INCLUDED IN THESELECTED DATA SETS

ExplanationThe Online Log Data Sets (OLDS) were selectedfor processing by the RECON Query of Log DataSet Names utility. You specified the NOACTIVEOLDScontrol statement to exclude the active OLDS from thelist of data set names extracted by the utility.

In the message text:data set name

The name of the active OLDS that was excludedfrom the list

System actionThe RECON Query of Log Data Set Names utilitycontinues processing.


Module:DFSKARC0


DFS4324E PSB psb_name REFERENCED ADELETED DBD dbd_name. PSTpst_name.

ExplanationThe program view (PSB) psb_name cannot be deletedfrom the IMS directory data set because there is noDROP PROGRAMVIEW DDL statement for this PSB inthis work unit.


The name of the database that is to be deleted bythe DROP DATABASE DDL statement in this workunit.

psb_nameThe name of the program view (PSB) that containsthe reference to the database dbd_name, but isnot deleted in this work unit.


System actionThe program view (PSB) psb_name is not deleted fromthe directory. The database dbd_name in the DROPDATABASE statement is not deleted from the directory.

User responseIf the PSB is still needed, submit aDROP PROGRAMVIEW statement and a CREATEPROGRAMVIEW statement to remove the reference tothe database dbd_name from the PSB.

If the PSB is no longer needed, submit aDROP PROGRAMVIEW statement to delete the PSBcompletely.

Module:DFSOLC70

Related informationDROP DATABASE (Application ProgrammingAPIs)DROP PROGRAMVIEW (ApplicationProgramming APIs)

DFS4325W MEMBER mbr_name WASALREADY DELETED FROM THEIMS DIRECTORY DATA SET. PSTpst_name.

ExplanationA DDL DROP statement was submitted to delete theDBD or PSB member that is identified in the message

text, but the DBD or PSB does not exist in, or wasalready deleted from, the IMS directory data set.

In the message text:mbr_name

The name of the DBD or PSB member as it wasspecified in the DDL DROP statement.


System actionThe request to remove this member from the IMSdirectory data set is ignored.


Module:DFSOLC70

DFS4326E AUTOMATIC ACTIVATION OFDDL DEFINITIONS SUBMISSIONABORTED. PST pst_name

ExplanationThe DDL definitions cannot be activated. This messageis preceded by an error message that indicates theerror, such as DFS4328E, DFS4344E, DFS4340E,DFS4341E, DFS4349E, or DFS3537E.

In the message text:pst_name

The PST name of the task that is processing theinstructions from the DDL stream.

System actionThe processing of the instructions from the DDLstream is terminates.

Operator response:Look for any previous error messages, suchas DFS4328E, DFS4344E, DFS4340E, DFS4341E,DFS4349E, or DFS3537E, to determine the cause offailure.

Operator response:Resolve the error and resubmit the DDL statementsagain.

Module:DFS3DL40, DFS3DL50

DFS4328E DDL CHANGES COULD NOT BEACTIVATED. OTHER CHANGES INPROGRESS. REGION regionname

Chapter 89. DFS messages, DFS4301E - DFS4350E 1187

http://www.ibm.com/support/knowledgecenter/SSEPH2_15.1.0/com.ibm.ims15.doc.apr/ims_sql_drop_database.htm#ims_sql_drop_database

http://www.ibm.com/support/knowledgecenter/SSEPH2_15.1.0/com.ibm.ims15.doc.apr/ims_sql_drop_database.htm#ims_sql_drop_database

http://www.ibm.com/support/knowledgecenter/SSEPH2_15.1.0/com.ibm.ims15.doc.apr/ims_sql_drop_programview.htm#ims_sql_drop_programview

http://www.ibm.com/support/knowledgecenter/SSEPH2_15.1.0/com.ibm.ims15.doc.apr/ims_sql_drop_programview.htm#ims_sql_drop_programview

ExplanationIMS is already processing other changes to databaseresources and cannot process the current DDLsubmission.

The resource changes in progress might have beeninitiated by the submission of DDL statements or theexecution of any of the following commands:

• IMPORT DEFN SOURCE(CATALOG)• CREATE DB• DELETE DB

In the message text:regionname

EXPLANATION

System actionThe automatic activation of the DDL definition failed.Any uncommitted work is backed out.


Wait for the change in progress to complete andresubmit the DDL statements to IMS.

If another online change command is in progress, waitfor it to complete before performing the automaticactivation of the DDL definitions again.

If IMS is already in an online change prepare statefrom an online change command and the commandis not IMPORT DEFN SOURCE(CATALOG), terminateor commit the online change before performing theautomatic activation of the DDL definitions again.

Module:DFS3DL40

DFS4329I THE DDL-DEFINED DBD dbd_nameIS INSERTED INTO THE IMSDIRECTORY DATA SET. PSTpst_name

ExplanationThe partition specification table (PST) task that isidentified in the message text is adding the database(DBD) that is identified in the message text to the IMSdirectory data set. The DBD was not previously in theIMS directory data set.


The database (DBD) that is added to the IMSdirectory data set.

pst_nameThe name of the PST task that is processing theinstructions from the DDL stream.

System actionThe PST task adds the DBD to the IMS directory dataset and continues processing any further instructionsfrom the DDL stream.

Depending on the activation options specified, thedatabase might be in a stopped state or might still beunknown to the online system.

Programmer responseDetermine if the database is known to the onlinesystem by issuing either of the following commands:

• QUERY DB• /DISPLAY DB

If the database is not found, issue the CREATE DBIMS type-2 command or code the DATABASE stage-1system definition macro, perform system definition,and restart IMS.

Module:DFSOLC70

Related referenceQUERY DB command (Commands)/DISPLAY DB command (Commands)CREATE DB command (Commands)

DFS4330I ACBLIB KEYWORD IS INVALIDWHEN DIRECTORY IS ENABLED.

ExplanationThe /MODIFY PREPARE ACBLIB command is notprocessed because the ACBLIB keyword is invalidin an IMS system with IMS management of ACBsenabled.


Programmer responseUse DDL commands to make changes in the IMSCatalog and activate them in the directory using theIMPORT DEFN commands to bring the changes online.

DFS4331E ERROR ALLOCATING THE IMSDIRECTORY BOOTSTRAP DATASET FOR REASON rc


http://www.ibm.com/support/knowledgecenter/SSEPH2_15.1.0/com.ibm.ims15.doc.cr/imscmds/ims_querydb.htm#ims_cr2querydb

http://www.ibm.com/support/knowledgecenter/SSEPH2_15.1.0/com.ibm.ims15.doc.cr/imscmds/ims_displaydb.htm#ims_cr1displaydb

http://www.ibm.com/support/knowledgecenter/SSEPH2_15.1.0/com.ibm.ims15.doc.cr/imscmds/ims_createdb.htm#ims_cr1createdb

or

ERROR READING THE IMS DIRECTORY BOOTSTRAPDATA SET FOR REASON rc

ExplanationThe following reason codes can be returned withDFS4331E:

CodesExplanation

1Failed to obtain storage.

2Failed to enqueue the data set.

3Waiting to allocate the data set. Either the data setis already allocated or another job is using it.

4Failed to set up a timer to detect when the data setis available for allocation.

5Failed to open the data set.

6An End-Of-Data occurred while reading the dataset.

7An I/O error occurred while reading the data set.

8An error occurred while closing the data set.

9An error occurred while de-allocating the data set.

10Failed to allocate the data set. The sub codesc is described in z/OS MVS ProgrammingAuthorized Assembler Services Guide or inMVS/ESA Programming Authorized AssemblerServices Guide under dynamic allocation errorcodes.

11Error when dequeuing the data set.

12The high level qualifier name of the data set cannotbe determined. The high level qualifier name isfrom the catalog database data set name. It isretrieved from DBRC if DBRC=Y is specified or theIMS Catalog HALDB Partition Definition data set ifDBRC=N is specified.

13The data set is not created yet.

14Waiting to allocate. The data set is in use.

15Exceeded specified wait time.

16The contents are incompatible or invalid.

System actionFor reason code 3, the IMS online system waits upto 150 seconds and the batch job waits with no limituntil the data set is available for allocation. For otherreason codes, the IMS online system terminates withan abend U071 and the batch job terminates with anabend U0821.

System programmer responseFor a problem caused by data set contention, correctthe problem and restart IMS or rerun the batch job.

Module:DFSDSSM0


DFS4332E ERROR ALLOCATING THE IMSDIRECTORY DATA SET FORREASON rc or ERROR ALLOCATINGTHE IMS DIRECTORY DATA SETFOR REASON rc SUBCODE scSPECIFIED IN BSDS

ExplanationIn the message text:rc

The reason code for the error.

The following reason codes can be issued withDFS4332E:

CodesExplanation


2Waiting to allocate the data set. Either the data setis already been allocated or another job is using it.






5Failed to allocate the data set. The sub codesc is described in z/OS MVS ProgrammingAuthorized Assembler Services Guide or inMVS/ESA Programming Authorized AssemblerServices Guide under dynamic allocation errorcodes. The IMS directory data set name that couldnot be allocated is specified in the bootstrap dataset (BSDS).


7An error occurred while closing the data set.

8An error occurred while dequeuing the data set.

9An error occurred while de-allocating the data set.

For dynamic allocation, look up the explanation ofthe MVS dynamic allocation reason code in z/OS MVSProgramming: Authorized Assembler Services Guide.

System actionFor reason code 2, the IMS online system waits upto 150 seconds and the batch job waits with no limituntil the data set is available for allocation. For otherreason codes, the IMS online system terminates withan abend U071 and the batch job terminates with anabend U0821.

System programmer responseFor a problem caused by data set contention, correctthe problem and restart IMS or rerun the batch job.

For dynamic allocation, look up the systemprogrammer response for the MVS dynamic allocationreason code in z/OS MVS Programming: AuthorizedAssembler Services Guide.

Module:DFSDSSM0 DFSRDB30 DFSBIND0 DFSMOLS0


DFS4333E ERROR ALLOCATING THE IMSDIRECTORY STAGING DATA SETFOR REASON rc

ExplanationThe staging data set for the IMS directory contains IMSapplication control blocks that are to be imported intothe directory. While processing either a DDL requestor an IMPORT command, an error occurred when IMSattempted to read the staging data set.


The reason code for the error.

The following reason codes can be issued withDFS4333E:

CodesExplanation


3The wait time of 150 seconds has expired for IMSonline. The DDL process terminates.




System actionThe DDL request or the IMPORT DEFNSOURCE(CATALOG) command fails.

System programmer responseFor dynamic allocation, look up the explanation ofthe MVS dynamic allocation reason code in z/OS MVSProgramming: Authorized Assembler Services Guide.

Module:DFSDSSM0


DFS4334W WAITING TO READ THE IMSDIRECTORY BOOTSTRAP DATASET. IT IS EITHER IN USE ORALREADY ALLOCATED.

ExplanationDuring the startup of an online IMS system or a batchjob, IMS or the batch job could not read the bootstrapdata set of the IMS directory because it was beingused by another job.

System actionIMS or the batch application program waits until thedata set becomes available and then resumes startupprocessing.






For an online IMS system, if the contention persists formore than 150 seconds, the IMS system terminateswith abend U0071.

For a batch application program, IMS does not imposea limit on the amount of time that the applicationprogram can wait. If the data set does not becomeavailable, the application program will wait foreverunless it implements its own timer or someonemanually terminates the application program.

System programmer responseIf the data set becomes available and startupprocessing resumes within an acceptable amount oftime, no action is necessary.

For a batch job, if the data set does not becomeavailable within an acceptable amount of time and thebatch application program does not time out on itsown, resolve the contention for the data set and, ifnecessary restart the batch job.

For an online IMS system, if the data set does notbecome available within 150 seconds, the IMS systemissues DFS4331E and terminates with abend U0071.

Module:DFSDSSM0

DFS4335E ACBMGMT=CATALOG ISSPECIFIED, BUT THE IMSDIRECTORY DOES NOT EXIST.

ExplanationDuring the startup of an online IMS system or a batchjob, the IMS directory was enabled by the specificationof ACBMGMT=CATALOG, but either the IMS directory isnot created yet or, in rare cases, the bootstrap data setfor the IMS directory cannot be found.

System actionIMS startup terminates with abend U0071 or the batchjob terminates with abend U0821.

System programmer responseTo restart IMS from an ACB library without the IMSdirectory, change the ACBMGMT specification in the<CATALOG> section of the DFSDFxxx member back toACBMGMT=ACBLIB and restart IMS.

If the error occurred while you are attempting toenable the IMS management of ACBs for the firsttime, see Enabling IMS management of ACBs (SystemDefinition).

If error occurred while running with an existing IMSdirectory, the error is probably caused by a missing or

corrupted bootstrap data set. If the bootstrap data setis missing or corrupted, the IMS directory needs to berebuilt.

You can use either the IMS Catalog Database Libraryutility (DFS3LU00) to rebuild the IMS directory fromthe IMS catalog or the IMS Catalog Populate utility(DFS3PU00) to rebuild the IMS directory from ACBlibrary data sets.

Module:DFSDSSM0

Related tasksEnabling IMS management of ACBs (SystemDefinition)Related referenceCATALOG and CATALOGxxxx sections of theDFSDFxxx member (System Definition)IMS Catalog Library Builder utility (DFS3LU00)(System Utilities)IMS Catalog Populate utility (DFS3PU00)(System Utilities)

DFS4336W WAITING TO READ THE IMSDIRECTORY DATA SET. IT ISEITHER IN USE OR ALREADYALLOCATED.

ExplanationDuring the startup of an online IMS system or abatch job, IMS or the batch job could not read theIMS directory data set because it was being used byanother job.

System actionIMS or the batch job waits until the data set becomesavailable and then resumes startup processing.

For an online IMS system, if the contention persists formore than 150 seconds, the IMS system terminateswith abend U0071.

For a batch application program, IMS does not imposea limit on the amount of time that the applicationprogram can wait. If the data set does not becomeavailable, the application program will wait foreverunless it implements its own timer or someonemanually terminates the application program.

System programmer responseIf the data set becomes available and startupprocessing resumes within an acceptable amount oftime, no action is necessary.

For a batch job, if the data set does not becomeavailable within an acceptable amount of time, resolve


http://www.ibm.com/support/knowledgecenter/SSEPH2_15.1.0/com.ibm.ims15.doc.sdg/ims_catalog_acb_mgmt_enabling.htm#ims_catalog_acb_mgmt_enabling










the contention for the data set and, if necessary restartthe batch job.

For an online IMS system, if the data set does notbecome available within 150 seconds, the IMS systemissues DFS4332E and terminates with abend U0071.

Module:DFSDSSM0

DFS4337E THE IMS DIRECTORY DATA SETCANNOT BE FOUND.

ExplanationDuring the startup of an online IMS system or a batchjob, IMS or the batch job could not find the directorydata set of the IMS catalog. Either the directory dataset was not created yet or it cannot be found for someother reason.

System actionIMS startup terminates with abend U0071. Batch jobsterminate with abend U0821.

System programmer responseDetermine why the directory data set was not found.

If the directory data set is not created yet, create it byrunning the IMS Catalog Populate utility (DFS3PU00).

Module:DFSDSSM0

DFS4338W WAITING TO READ THE IMSDIRECTORY STAGING DATA SET.IT IS EITHER IN USE OR ALREADYALLOCATED.

ExplanationDuring the processing of a DDL request or the IMPORTcommand, IMS was unable to read the staging data setof the IMS directory because it was already allocatedor in use by another job.

System actionIMS waits and resumes processing of the DDL requestor the IMPORT command when the data set becomesavailable.

If the contention persists for 150 seconds, IMS issuesmessage DFS4333E and terminates the processing ofthe DDL request or IMPORT command. Any updates tothe IMS catalog that were made during the processingof a DDL request are backed out.

System programmer responseAfter the contention has been resolved, attempt theprocess again.

Module:DFSDSSM0

DFS4339E THE IMS DIRECTORY STAGINGDATA SET CANNOT BE FOUND.

ExplanationWhile processing either a DDL request or an IMPORTcommand that updates database or program viewdefinitions, IMS attempted to read the staging dataset for the IMS directory, but the data set could notbe found. Either the data set was not created yet or itotherwise cannot be found.

System actionThe DDL request or IMPORT command fails.

System programmer responseDetermine why the staging data set was not found.

If the staging data set is not created yet, create it byrunning the IMS Catalog Populate utility (DFS3PU00).

Module:DFSDSSM0

DFS4340E AUTOMATIC ACTIVATION OF DDLDEFINITIONS FAILED FOR DBDdbd_name. REASON=reason_textPST pst_name.

ExplanationUpdates to the database that is identified by theDBD name in the message could not be activatedautomatically because of the reason that is identifiedin the message text by the reason code.


The name of the database (DBD) that could not beactivated.

pst_nameThe PST name of the process that was updatingthe IMS directory data set.

reason_textText that describes the reason that the DDLrequest could not be activated.



Administrator responseReview the reason code, correct the problem, andresubmit the DDL statements to IMS.

Module:DFSOLC70

DFS4341E AUTOMATIC ACTIVATION OF DDLDEFINITIONS FAILED FOR PSBpsb_name. REASON=reason_textPST pst_name.

ExplanationUpdates to the definition of the program view (PSB)that is identified in the psb_name field in the messagecould not be activated automatically because of thereason that is described in the reason_text field in themessage.


The name of the program view (PSB) that could notbe activated.

pst_nameThe PST name of the process that was updatingthe IMS directory data set.

reason_textText that describes the reason that the DDLrequest could not be activated.


System programmer responseReview the reason code, correct the problem, andresubmit the DDL statements to IMS.

Module:DFSOLC70

DFS4342E IMODULE INIT FAILED; RC=xxRSN=yyyyyyyy

ExplanationAn error occurred during the initialization of the IMSIMODULE service. IMS initialization cannot continue.


xxA return code that indicates the specificinitialization function that failed. Possible valuesare:04

Unable to load the IMS storage managementmodule DFSMODU0. The reason code isa combination of the two values that arereturned from the z/OS LOAD macro. The tophalf of the reason code is the abend code thatthe z/OS LOAD service would have issued if ithad been called unconditionally. The lower halfof the reason code is the reason code that isassociated with the abend code. For example,08060004 means system abend 806, reasoncode 04.

08Unable to obtain storage for the IMODSTATblock (the internal IMS storage manager maincontrol block). The reason code is the returncode from the z/OS STORAGE macro.

0CUnable to obtain storage for the internalIMODULE trace table. The reason code is thereturn code from the z/OS STORAGE macro.

10Unable to obtain storage for the dynamicstorage for the IMODULE service initializationmodule DFSMODX0. The reason code is thereturn code from the z/OS STORAGE macro.

14Unable to obtain storage for the 64-bit storagetracking object for private storage. The reasoncode is the return code from the z/OS IARV64macro.

18Unable to obtain storage for the 64-bit trackingobject for common storage. The reason code isthe return code from the z/OS IARV64 macro.

1CUnable to load the IMS storage cleanupmodule DFSMODU2. The reason code isa combination of the two values that arereturned from the z/OS LOAD macro. The tophalf of the reason code is the abend code thatthe z/OS LOAD service would have issued if ithad been called unconditionally. The lower halfof the reason code is the return code that isassociated with the abend code. For example,08060004 means system abend 806, reason04.

20Unable to obtain storage for a work area for theIMS storage cleanup routine DFSMODU2. The


reason code is the return code from the z/OSSTORAGE macro.

24A DL/I separate address space (DLISAS) regionattempted to initialize IMS IMODULE services;however, the associated IMS control regionwas not running with DLISAS and did notallocate an IMODULE IMODASCT block forDL/I. This error can be caused by erroneouslystarting a DL/I address space directly, outsideof IMS system's control, when the associatedcontrol region is a DCCTL IMS or is running withLSO=Y (no DL/I).

28A DLISAS region attempted to initializeIMS IMODULE services; however, anotherDL/I region had already initialized IMODULEservices for the same control region. Thiserror can be caused by erroneously starting asecond DL/I address space directly, outside ofIMS system's control, when there is already aDL/I address space started for the same IMScontrol region.

yyyyyyyyA reason code that is the return code of the servicethat failed. For IARV64 return codes, see z/OSMVS Programming: Authorized Assembler ServicesReference Vol 2 (SA22-7610). For codes fromSTORAGE, see z/OS MVS Programming: AuthorizedAssembler Services Reference Vol 4 (SA22-7612).For information about the abend code and thereason code from LOAD, see z/OS MVS SystemCodes (SA22-7626).


System programmer response:If the error described in this message is caused byenvironmental conditions, such as insufficient storageor module missing from IMS.SDFSRESL, correct theproblem. Then, restart the address space. Otherwise,save ay memory dump and SYSLOG information andcontact IBM Software Support.

Module:DFSMODX0

Related referencez/OS: IARV64 macro return and reason codesz/OS: STORAGE OBTAIN return and reasoncodesz/OS: z/OS MVS System CodesRelated informationIMS abend 0684

DFS4343E IMS STORAGE CLEANUPABENDabend_code PSW=psw RSN=rsnmodname=module_address

ExplanationAn abnormal termination occurred in IMS storagecleanup processing during IMS termination.


abend_codeThe abend code that was received; Sxxx for asystem abend, Uxxxx for a user abend.

pswThe PSW (program status word) content at thetime of the termination.

rsnThe abend reason code, if any; N/A if there is none.

modnameThe name of the IMS cleanup module thatdetected the termination. This module might notbe the one in which the termination occurred.

module_addressThe address of the module identified withmodname.

System actionWhen an abnormal termination occurs during IMSstorage cleanup, the storage cleanup recovery routinereceives control from z/OS. The recovery routineanalyzes the abend, takes appropriate action, andgathers diagnostic data. The recovery routine will takean SDUMP for the first abend that occurs duringprocessing. If possible, the recovery routine willrecover from the termination and return control to thestorage cleanup routine to continue releasing storage.

For abends after the first, the recovery routine willissue message this message and create an error entryin LOGREC, but does not take another SDUMP.

System programmer response:Save a copy of the memory dump and the LOGRECrecords pertaining to this termination. Then contactIBM Software Support.

Module:DFSMODX0

DFS4344E AUTOMATIC ACTIVATION OFDDL DEFINITIONS FAILED.REASON=reason_text PSTpst_name.

ExplanationUpdates to a database or program view that weresubmitted to IMS via DDL statements could not be


http://www-01.ibm.com/support/knowledgecenter/SSLTBW_2.4.0/com.ibm.zos.v2r4.ieaa200/iv64rr.htm?lang=en



http://www-01.ibm.com/support/knowledgecenter/SSLTBW_2.4.0/com.ibm.zos.v2r4.ieah700/toc.htm?lang=en


activated automatically because of the reason that isidentified in the message text by the reason code.


The PST name of the process that was updatingthe IMS directory data set.

reason_textThe code that indicates the reason that the DDLrequest could not be activated.


Administrator responseReview the reason code, correct the problem, andresubmit the DDL statements to IMS.

Module:DFS3DL40, DFS3DL50, DFSOLC70

DFS4349E AUTOMATIC ACTIVATION OFDDL DEFINITIONS FAILED. PSBpsb_name NOT REBUILT FOR DBDdbd_name. REGION pst_name

ExplanationThe DDL definitions cannot be activated. The programview (PSB) that is shown in the psb_name fieldreferences a database, dbd_name, but the PSB wasnot rebuilt for the DBD changes.


The name of the database that was modified.psb_name

The program view (PSB) that was not rebuilt.pst_name


System actionThe automatic activation of the DDL definitions fails.

Administrator responseAdd the DDL definition changes for this PSB along withthe DDL definitions for this changed DBD and submitthe DDL again.

Module:DFSOLC70

DFS4350E ddname function ERROR, RC=rc

ExplanationThe identified function failed for the ddname data set.The return codes for the OPEN and CLOSE functionsare in z/OS DFSMS Macro Instructions for Data Sets.RDJFCB return codes are in z/OS DFSMSdfp AdvancedServices.


ddnameData set name.

function

Any of the following functions can result in thismessage:

• OPEN• CLOSE• RDJFCB

rcReturn code from the function.


System programmer response:Ensure that the DD statement for the data set isdefined correctly.

Module:DFS3UCD0

Related referencez/OS: OPEN--Connect Program and Data(BDAM, BISAM interface to VSAM, BPAM, BSAM,QISAM interface to VSAM, and QSAM)z/OS: CLOSE--Disconnect Program and Data(BDAM, BISAM, BPAM, BSAM, QISAM, andQSAM)z/OS: RDJFCB macro specification








http://www-01.ibm.com/support/knowledgecenter/SSLTBW_2.4.0/com.ibm.zos.v2r4.idas300/rdjfcb.htm?lang=en

Chapter 90. DFS messages, DFS4351E - DFS4400E


DFS4351E pgmname ENCOUNTERED ANERROR TRYING TO READ THEddname DATA SET RC=rc

ExplanationThe utility identified by pgmname attempted to readthe data set identified by ddname but encountered anerror in the BPERDPDS macro that opens and readsthe data set.


pgmnameThe module ID.

ddnameThe data set that encountered the read error.

rcThe return code from BPERDPDS.

System action:The utility terminates.


System programmer response:Ensure that the data set name is correct.

Module:DFS3UCD0

DFS4352E pgmname ENCOUNTERED ANERROR TRYING TO READ THEddname DATA SET RC=rc

ExplanationThe utility identified by pgmname encountered anerror while trying to parse the information in the dataset identified by ddname. The BPEPARSE service isused to parse the data set.



ddnameThe data set that encountered the parsing error.

rcThe return code from BPEPARSE.

System action:

The utility terminates.

System programmer response:Additional BPE messages are generated at the sametime as this message. See those messages for moreinformation about the parsing error.

Module:DFS3UCD0

DFS4353I pgmname PROCESSINGCOMPLETED, RC=rc RSN=rsn

ExplanationThe pgmname utility completed processingsuccessfully. This message is typically followed byadditional utility or macro messages.



rcThe return code from the utility.

rsnThe reason code from the utility.


Programmer response:If the return code is not zero, errors might haveoccurred during processing. Examine the othermessages generated by the utility to determine iftroubleshooting is necessary.

Module:DFS3UCD0

Related referenceIMS catalog partition definition data set utility(DFS3UCD0)

DFS4354E FAILURE OBTAINING STORAGE,RC=rc RSN= rsn

ExplanationThe utility identified by pgmname encountered anerror while obtaining storage. This error usually occursbecause the region size is not large enough.




http://www.ibm.com/support/knowledgecenter/SSEPH2_15.1.0/com.ibm.ims15.doc.sur/ims_catalog_partdef_utility.htm#ims_catalog_partdef_utility

http://www.ibm.com/support/knowledgecenter/SSEPH2_15.1.0/com.ibm.ims15.doc.sur/ims_catalog_partdef_utility.htm#ims_catalog_partdef_utility

rcReason code from the STORAGE OBTAIN macro.

rsnIdentifies the type of storage block:1

Grammar2

Parsed output3

Definition control block


Programmer response:Increase the region size where the utility is runningand run the job again.

Module:DFS3UCD0

DFS4355E HIKEY=YES CANNOT BESPECIFIED WITH PARTSEL,HALDB=dbname

ExplanationA HALDB can either use a partition selection exit orhigh key values, but not both.


Programmer response:Correct the HALDB SYSIN statement for theDFS3UCD0 utility and run the job again.

Module:DFS3UCD0

DFS4356I HALDB dbname SUCCESSFULLYDEFINED

ExplanationThe DFS3UCD0 utility successfully created thepartition definition data set for the dbname database.



Module:DFS3UCD0

DFS4357E NO PART STATEMENT SPECIFIEDIN SYSIN FOR HALDB=dbname

ExplanationThe SYSIN statement for the DFS3UCD0 utility doesnot contain any PART statements for the HALDBidentified by dbname.


Programmer response:Either add a PART statement for the database orremove the HALDB statement for the database and runthe job again.

Module:DFS3UCD0

DFS4358E PART STATEMENT HASNO CORRESPONDING HALDBSTATEMENT, HALDB=dbnamePART=partname

ExplanationThere is no HALDB statement specified for theidentified partition.


Programmer response:Correct the SYSIN statement for the DFS3UCD0 utility.Either add an appropriate HALDB statement or removethe identified PART statement and run the job again.

Module:DFS3UCD0

DFS4359E KEYWORDS KEYSTCHARAND KEYSTHEX CANNOTBE SPECIFIED TOGETHER,HALDB=dbname PART=partname

ExplanationThe KEYSTCHAR and KEYSTHEX parameters of theHALDB PART statement for the DFS3UCD0 utilityare mutually exclusive. Either specify the partitionhigh key value or selection string in character format(KEYSTCHAR) or in hexadecimal format (KEYSTHEX).


Programmer response:Correct the HALDB PART statement for the DFS3UCD0utility and run the job again

Module:DFS3UCD0

DFS4360E statement STATEMENT CONTAINSAN INVALID VALUE IN KEYWORD


keyword, HALDB=dbnamePART=partname

ExplanationThe indicated keyword value is invalid. This typicallyoccurs because an illegal character was used, becausethe value is too long or too short, or because a numericvalue was outside the valid range.


statementThe statement containing the invalid parametervalue.

keywordThe keyword for which the invalid parameter valuewas specified.

dbnameThe HALDB database name specified for the utility.

partnameThe HALDB partition name specified for the utility.

System action:The DFS3UCD0 utility terminates.

Programmer response:Correct the keyword value and run the utility again.

Module:DFS3UCD0

DFS4361E MORE BLOCKSZE VALUES ARESPECIFIED THAN THE NUMBEROF DATA SET GROUPS (nn),HALDB=dbname PART=partname

ExplanationThe HALDB named dbname uses nn data set groups.The PART statement of the DFS3UCD0 utility jobspecified more than nn block size values for theBLOCKSZE parameter.


nnThe number of data set groups the dbname HALDBuses.

dbnameThe database name.

partnameThe HALDB partition name.


Programmer response:Correct the BLOCKSZE parameter and run theDFS3UCD0 utility again.

Module:DFS3UCD0

DFS4362E A HIGH KEY IS REQUIRED FORTHIS PARTITION, HALDB=dbnamePART=partname

ExplanationThe PART statement for the identified HALDB partition(partname) did not specify a high key value. TheHALDB identified by dbname does not use a partitionselection exit routine, so a high key value is required.





Programmer response:Specify a high key value with either the KEYSTCHARparameter or the KEYSTHEX parameter and run theDFS3UCD0 utility again.

Module:DFS3UCD0

DFS4363E A PARTITION SELECTION EXIT ISREQUIRED WHEN HIKEY=NO ISSPECIFIED, HALDB=dbname

ExplanationA HALDB statement for the DFS3UCD0 utility with thekeyword HIKEY=NO must use a partition selection exitroutine. No PARTSEL keyword was included, or thename was not valid.




Programmer response:Specify a partition selection exit routine with thePARTSEL keyword and run the DFS3UCD0 utility again.You can specify the exit routine name in either theSYSIN statement for the utility or in the DBDLIBmember for the database.

Module:DFS3UCD0

DFS4364E statement STATEMENT SPECIFIESA DUPLICATE nametype NAME,HALDB|PART=name


ExplanationHALDB names and HALDB partition names must beglobally unique.


statementThe SYSIN statement where the duplicate name islocated.

nametypeThe type of resource that is using a duplicatename.

nameThe database or database partition name.


Programmer response:Correct the duplicate name and run the DFS3UCD0utility again.

Module:DFS3UCD0

DFS4365E INVALID KEY OR STRING VALUESPECIFIED IN PART STATEMENT,HALDB=dbname PART=partnameRSN=reason

ExplanationThe partname PART statement for the DFS3UCD0utility specified an invalid high key value with eitherthe KEYSTCHAR or KEYSTHEX keyword.


dbnameThe HALDB name.


reasonThe reason why the specified key value is invalid:KEY TOO LONG

The specified high key value is longer than theroot key length for the HALDB.

ODD NUMBER HEXAn odd number of characters was specified forthe KEYSTHEX parameter. Hexadecimal valuesmust contain an even number of characters.

INVALID HEXAn invalid character was specified for theKEYSTHEX parameter. Hexadecimal values caninclude the numerals 1-9 and the letters A-F.

DUPLICATE KEYHigh key values for each partition of a HALDBmust be unique within that HALDB. The

specified key value was used in a previousPART statement.


Programmer response:Correct the KEYSTCHAR or KEYSTHEX parameter valueand run the DFS3UCD0 utility again.

Module:DFS3UCD0

DFS4366E TOO MANY PARTITIONSSPECIFIED FOR HALDB=dbname

ExplanationHALDBs cannot have more than 1001 partitions.


dbnameThe HALDB name.


Programmer response:Reduce the number of HALDB partitions defined forthis HALDB and run the DFS3UCD0 utility again.

Module:DFS3UCD0

DFS4367E ddname CANNOT CONTAINCONCATENATED DATA SETS

ExplanationA DD statement submitted for the DFS3UCD0 utilitycontains multiple data sets. Multiple data sets are notsupported by the utility.


ddnameThe DD statement name


Programmer response:Correct the DD statement and run the DFS3UCD0utility again.

Module:DFS3UCD0

DFS4368E DBDLIB PROCESSING ERROR,RSN=rsncode DB=dbname


ExplanationThe IMS catalog partition definition data set utilityencountered an error while processing the IMSDBDLIB.


rsncodeOne of the following reason codes:1

No IMS DD statement2

IMS DD open error3

Database not found in DBDLIB4

Specified DB is not a HALDBdbname

For reason codes 3 and 4, this field indicates thedatabase name that was either not found or that isnot a HALDB. For reason codes 1 and 2, this field isblank.


Programmer response:Correct the DD statement and run the DFS3UCD0utility again.

Module:DFS3UCD0

DFS4369I THE DDL-DEFINED DBD dbd_nameREPLACED A PRIOR INSTANCE OFTHE DBD IN THE IMS DIRECTORYDATA SET. PST pst_name

ExplanationThe partition specification table (PST) task that isidentified in the message text is replacing an existinginstance of the database (DBD) that is named in themessage text with an updated, DDL-defined instanceof the DBD.


The database (DBD) that is replaced in the IMSdirectory data set.


System actionThe PST task replaces the DBD in the IMS directorydata set with the updated DBD and continuesprocessing the instructions from the DDL stream.

The database remains in a stopped state.


Module:DFSOLC70

Related referenceQUERY PGM command (Commands)/DISPLAY PGM command (Commands)

DFS4370I SHUTDOWN IS CHECKINGRESOURCES FOR AUTOEXPORTTO REPOSITORY TYPE=repotype.NAME=reponame.

ExplanationWhen an IMS shutdown command is issued to anIMS system that has automatic export (autoexport) tothe IMSRSC repository enabled, IMS shutdown firstprocesses automatic export to the repository beforestarting the IMS shutdown processing. The DFS4370Imessage is issued before the automatic export to theIMSRSC repository is started by IMS.

The DFS4370I message indicates that IMS shutdownis starting to check for resource and descriptordefinitions that have been created or updated sincethe last EXPORT or automatic export and should bewritten to the repository. The main IMS shutdownprocess does not start until after the resourcechecking is done and the automatic export (if needed)has successfully completed.

The DFS4370I message is issued to the systemconsole and MTO even if the shutdown command isissued from the OM API. The message indicates IMSsystem action and is not a command response.

After the DFS4370I message is issued, the IMS systemstarts the autoexport processing, which can result inone of the following:

• The autoexport processing during IMS shutdownwaits because another automatic export, EXPORTcommand, IMPORT command, or a CREATE, UPDATEor DELETE IMS command is in progress.

• The autoexport during IMS shutdown finds resourcedefinitions to be exported and initiates theautoexport. In this case, the DFS4390I INITIATEDmessage is issued followed by the DFS4390ICOMPLETED | FAILED message. If autoexport during




IMS shutdown fails, the DFS4391I message isissued indicating that IMS shutdown processing isterminated. Refer to the user actions in messageDFS4391I for actions that can be taken.

• The autoexport during IMS shutdown finds noresource definitions to be exported. In this case,no other autoexport messages are issued and IMSshutdown begins.

When another autoexport or other IMS EXPORT,IMPORT, CREATE, UPDATE, or DELETE commands arein progress it is possible for there to be delay betweenthe DFS4370I message and either IMS shutdownstarting or the DFS4390I messages. If the autoexportor EXPORT command is long running because of thenumber of resource definitions being written to therepository, the delay might be significant.

In the message text:repotype

The repository type. The only valid value isIMSRSC.

reponameThe repository name.

System actionRefer to the previous explanation in this topic onIMS actions after the DFS4370I is issued. IMSshutdown processing will start after automatic exportto repository is successful or there are no resourcedefinitions to autoexport. IMS shutdown will fail ifthere is an error during autoexport.

User responseIf the DFS4370I message is issued by IMS and IMSdoes not start IMS shutdown processing or IMS doesnot issue the DFS4390I AUTOEXPORT messages, thenIMS is waiting for automatic export at shutdownprocessing to start. Check to see whether any priorautomatic export is in progress or if other IMPORT,EXPORT, CREATE, UPDATE, or DELETE commands arein progress.

Also look for any highlighted messages in RM to see ifautoexport from IMS is waiting for any locks.

IMS cannot start shutdown processing until theautoexport is completed.

Module:DFSICM30

DFS4371W IMS STOPPED TRANSACTION ORPROGRAM TO ACTIVATE DDLDEFINITIONS FOR PSB psb_name.

ExplanationDDL statements that change the definition of theprogram view (PSB) that is identified in the messagetext were submitted to IMS. To activate these changes,IMS stopped a transaction or a program.

System actionThe transaction or program associated with the PSBidentified in the message text is stopped. The PSBdefinition changes are activated. The transaction orprogram remains stopped.

Operator responseAfter IMS finishes activating the PSB changes,restart the transaction or program. For a transaction,use either the type-2 command UPDATE TRANSTART(SCHD) or the type-1 /START TRAN command.For a program, use either the type-2 commandUPDATE PGM START(SCHD) or the type-1 /START PGMcommand.

Module:

DFS4372I THE DDL-DEFINED PSB psb_nameREPLACED A PRIOR INSTANCE OFTHE PSB IN THE IMS DIRECTORYDATA SET. PST pst_name

ExplanationThe partition specification table (PST) task that isidentified in the message text is replacing an existinginstance of the program view (PSB) that is identifiedin the message text with an updated, DDL-definedinstance of the PSB.


The program view (PSB) that is replaced in the IMSdirectory data set.


System actionThe PST task replaces the PSB in the IMS directorydata set with the updated PSB and continuesprocessing the instructions from the DDL stream.


Module:DFSOLC70


Related referenceQUERY PGM command (Commands)/DISPLAY PGM command (Commands)

DFS4373I IMS INITIALIZATION IS WAITINGFOR IMS ims_id TO COMPLETE ANIMPORT FROM THE SHARED IMSCATALOG

ExplanationThis IMS system is waiting for IMS ims_id to finishprocessing an IMPORT DEFN SOURCE(CATALOG)command.

System actionThe IMS system waits.

Programmer responseIssue the QUERY MEMBER TYPE(IMS)SHOW(STATUS) command to determine the currentstatus of import processing.

Module:DFSRDB30

Related referenceIMPORT DEFN SOURCE(CATALOG) command(Commands)QUERY MEMBER command (Commands)

DFS4374W I/O ERROR READING MEMBERDFSIMSL.

ExplanationThe IMS system could not read the DFSIMSL memberof the IMS directory data set of a shared IMS catalog.The DFSIMSL member is an automatically generatedlist of the IMS systems that share the IMS catalog.

System actionThe IMS system attempts to rebuild memberDFSIMSL.

Programmer responsePerform a warm start of the other IMS systems thatshare this same IMS catalog to ensure the list IMS IDin the DFSIMSL member is current before issuing theIMPORT command again.

ModuleDFSRDB30

DFS4375I UOW ABORTED FOR ONLINEACTIVATION OF ACB RESOURCE:FOUND LOG RECORD 70nn.TOKEN=cccccccccccccccc.

ExplanationDuring IMS restart or an FDBR takeover, updates werefound in the IMS catalog database that were notcommitted.



nnThe last two digits of the four digit log recordnumber. For example, possible log records thatmight be displayed include:

• 7005• 7007• 7008• 7014• 7015

System actionIMS backs out all updates to the IMS directory dataset for the UOW that corresponds to the uncommittedupdates in the IMS catalog.

System programmer responseIssue the IMPORT command again or resubmit theDDL statements.

Module:DFSMOL20

DFS4376I UOW COMMITTED FOR ONLINEACTIVATION OF ACB RESOURCE:FOUND LOG RECORD 70nn.TOKEN=cccccccccccccccc.

ExplanationThe updates to both the catalog database and thedirectory data sets have been committed.






http://www.ibm.com/support/knowledgecenter/SSEPH2_15.1.0/com.ibm.ims15.doc.cr/imscmds/ims_import_catalog.htm#ims_import_catalog


http://www.ibm.com/support/knowledgecenter/SSEPH2_15.1.0/com.ibm.ims15.doc.cr/imscmds/ims_querymember.htm#ims_cr2querymember

nnThe last two digits of the four digit log recordnumber. For example, possible log records thatmight be displayed include:

• 7005• 7007• 7008• 7014• 7015

System actionAt IMS restart or at FDBR take over, becausethe updates to the catalog database have beencommitted, IMS also committed all changes to the IMSdirectory data sets for this UOW.


Module:DFSMOL20

DFS4377I AUTOMATIC ACTIVATION OF DDLSUBMISSION COMPLETE. RC=00.PST pst_name

ExplanationAll of the instructions in a DDL stream weresuccessfully applied to the IMS directory data set.



rcThe return code issued by the PST task.

System actionDepending on the type of resource updates and theactivation options specified, the resource changesmight be activated immediately or the resources mightrequire additional steps, such as issuing the IMStype-2 CREATE command, before they are active in theIMS system.

Administrator response:Confirm that the resources are active by using IMStype-2 QUERY commands and, if they are not, take anyadditional necessary steps to activate the resources.

Module:DFS3DL50

Related referenceQUERY DB command (Commands)QUERY PGM command (Commands)CREATE DB command (Commands)CREATE PGM command (Commands)

DFS4379W IMS STOPPED DATABASEdbd_name TO ACTIVATE DDLDEFINITION CHANGES.

ExplanationDDL statements that change the definition of thedatabase that is identified in the message text weresubmitted to IMS. To activate these changes, IMSstopped the database.

System actionThe database identified in the message text isstopped. The database definition changes areactivated. The database remains stopped.

Operator responseAfter IMS finishes activating the database changes,restart the database by issuing either the type-2command UPDATE DB START(ACCESS) or the type-1 /START DB command.

Module:

DFS4380W OTMA XCF MESSAGES FROMmember name HAVE REACHED80% OF THE MAXIMUM MESSAGELIMIT nnn

Explanation:OTMA processing could slow down because a problemwith RACF I/O, queue manager I/O, or other unknowninternal component was encountered by the IMSsystem. XCF messages from an OTMA client, suchas IMS Connect or IBM MQ, can pile up in theIMS causing a potential flood condition. When OTMAdetects this condition, OTMA issues this warningmessage. It then sends out a protocol messageto the OTMA client so that the client can reroutethe subsequent transactions to a different IMS. TheXCF messages from the OTMA client eventually areprocessed by the IMS when the slow down conditionis relieved or resolved. If the OTMA transactionexpiration function is activated in the IMS system,these XCF messages could be discarded.

System action:Processing continues. An OTMA protocol message withthe warning status is sent to the OTMA client.



http://www.ibm.com/support/knowledgecenter/SSEPH2_15.1.0/com.ibm.ims15.doc.cr/imscmds/ims_querydb.htm#ims_cr2querydb


http://www.ibm.com/support/knowledgecenter/SSEPH2_15.1.0/com.ibm.ims15.doc.cr/imscmds/ims_createdb.htm#ims_cr1createdb


A potential XCF message flood has occurred in thisIMS. Reroute new transaction requests to a differentIMS.

Module:DFSYSND0

DFS4381I OTMA XCF MESSAGE FLOODCONDITION HAS BEEN RELIEVEDFOR MEMBER name

Explanation:The OTMA XCF message count has reached 50% of themaximum limit. OTMA has considered this conditionas a relieve condition and issued this informationalmessage.

System action:Processing continues. An OTMA protocol message withthe OK status is sent to the OTMA client.

System programmer response:An XCF message flood has been resolved. This IMS isOK to process new transactions from OTMA clients.

Module:DFSYSND0

DFS4382W THE TOTAL OTMA TPIPE COUNTnnnnnnn HAS REACHED 80% OFmmmmmm for MEMBER name

ExplanationOTMA detected that the number of transaction pipes(tpipe) has reached or exceeded 80% of the maximumnumber mmmmmm, which you set in the descriptorfile. OTMA issues this warning message for each OTMAmember.


nnnnnnnThe current number of tpipes

mmmmmmThe limit number of tpipes you set for this member

nameThe name of the member

System action:The system continues to create tpipes.

System programmer response:Start monitoring the number of tpipes for eachmember. Issue a checkpoint three times to clean theidle tpipes.

Module:DFSYFD00

DFS4383E THE TOTAL OTMA TPIPE COUNTnnnnnnn HAS REACHED 100% OFmmmmmm for MEMBER name

ExplanationOTMA detected that the number of transactionpipes (tpipe) has reached or exceeded the maximumlimit indicated by mmmmmm, which you set in thedescriptor file. OTMA issues this message for eachOTMA member.

In the message text:nnnnnnn

The current number of tpipesmmmmmm

The limit number of tpipes you set for this membername

The name of the member

System action:Processing stops. IMS ceases creating tpipes andissues this message.

System programmer response:An OTMA tpipe overflow has occurred in this IMS.OTMA stops creating new tpipes. Issue a checkpointthree times to clean the idle tpipes. The system canthen continue to create new tpipes.

Module:DFSYFD00

DFS4384I THE TOTAL OTMA TPIPE COUNTnnnnnnn HAS DECREASED BELOWxx% OF mmmmmm for MEMBERname

ExplanationOTMA detected that the number of transaction pipes(tpipes) has fallen below xx percentage of themaximum limit indicated by mmmmmm, which you setin the descriptor file. OTMA issues this relief messagefor each OTMA client.


nnnnnnnThe current number of tpipes

xxThe relief level of the maximum limit. This relieflevel can be set in the OTMA client descriptor. Thedefault is 50.

mmmmmmThe limit number of tpipes you set for this member

nameThe name of the member




Module:DFSYFD00

DFS4385W THE GLOBAL OTMA TPIPECOUNNT nnnnnnn HAS REACHED100% OF kkkkkk

ExplanationOTMA detected that the total number of transactionpipes (tpipe) has reached or exceeded the monitoringpoint indicated by kkkkkk.


nnnnnnnThe current global number of tpipes.

kkkkkkThe global monitoring point. This number is thehighest number of tpipes you set for all members.


System programmer response:Start monitoring the number of tpipes for eachmember. Issue a checkpoint three times to clean theidle tpipes.

Module:DFSYFD00

DFS4386I THE GLOBAL OTMA TPIPE COUNTnnnnnnn HAS DECREASE BELOW80% OF kkkkkk

ExplanationOTMA detected that the total number of transactionpipes (tpipe) has fallen below 80% of monitoring pointindicated by kkkkkk.


The current global number of tpipes.kkkkkk

The global monitoring point. This number is thehighest number of tpipes you set for all members.



Module:DFSYFD00

DFS4387I MEMBER rsc_name HAS NOCHANGE

ExplanationDuring the processing of an IMPORT command or theDDL activation, found a member in the staging data setthat is the same as the one in the directory data set.


The name of the DBD or PSB resource that has nochange.

System actionThe IMPORT command or the DDL activation processcontinues. A rerun of the IMPORT command or DDLactivation due to data set I/O error or data set fullcondition may cause the member to be copied to thedirectory again.


Module:DFSOLC70

DFS4388W THE TOTAL OTMA INPUTMESSAGES(TIB) HAVE REACHEDOR EXCEEDED THE GLOBAL LIMITnnn

Explanation:OTMA detected that the total number of commitmode 1 (CM1) message blocks (YTIB) has reachedor exceeded the warning limit indicated by nnn inthe message text. OTMA considers this message floodcondition as a global warning for all the OTMA clients.

System action:Processing continues. An OTMA protocol message withthe warning status is sent to all OTMA clients.

System programmer response:An OTMA message flood has occurred in this IMS.Reroute the new transaction requests to a differentIMS.

Module:DFSYFD00

DFS4390I AUTOMATIC EXPORT functypeFOR REPOSITORY TYPE=repotype,NAME=reponame

ExplanationThe DFS4390I message indicates the start,completion, or failure of the automatic export to theIMSRSC repository.


In the message text:functype

INITIATED, COMPLETED, or FAILED.

A DFS4390I message with functype=INITIATED isissued when the automatic export processing tothe repository was started.

A DFS4390I message with functype=COMPLETEDis issued when the automatic export processing tothe repository was completed successfully.

A DFS4390I message with functype=FAILED isissued when the automatic export processing tothe repository failed due to an error.

typeThe repository type.

nameThe repository name.


User responseIf a DFS4390I message with functype of bothINITIATED and COMPLETED is issued, the resourcedefinitions in IMS and the repository are insynchronization. No action is needed.

If a DFS4390I message with functype of bothINITIATED and FAILED is issued, there was anerror during automatic export to the repository. Formore information about the error, see the DFS4401Emessage. After the error is resolved, issue the EXPORTDEFN TARGET(REPO) OPTION(CHANGESONLY)command or wait for the next automatic export.

If you need to cold start IMS when automatic exporthas not been done, refer to the procedures forretrieving the resources to be exported from the IMSlog by using the Create RDDS from Log Records utility(DFSURCL0) with the EXPORTNEEDED parameter.

Module:DFSXP000

Related referenceCreate RDDS from Log Records utility(DFSURCL0) (System Utilities)Related information“DFS4401E” on page 1209RM requestname ERROR, RC=rc RSN=rsnERRORTEXT=errortext

DFS4391E IMS SHUTDOWN CANNOTCOMPLETE DUE TO reasontext


reasontextExplains the reason for the error. reasontext can beone of the following:AUTOEXPORT ERROR

The IMS shutdown checkpoint cannot bestarted due to an error while automaticexporting to the IMSRSC repository.

System action:Shutdown is canceled.

User responseThe user response depends on the reasontext value, asfollows:AUTOEXPORT ERROR

See the DFS4401E message, which indicates theerror during automatic export. Fix the error and trythe IMS shutdown again.

Alternatively, you can turn off AUTOEXPORTwith the UPDATE IMS SET(AUTOEXPORT(N))command and then try the IMS shutdowncommand again. Because AUTOEXPORT is notenabled, IMS will not automatically export anyresource definitions that were created or modifiedsince the last EXPORT command or automaticexport to the IMSRSC repository.

Module:DFSICM30

Related referenceUPDATE IMS command (Commands)Related information“DFS4401E” on page 1209RM requestname ERROR, RC=rc RSN=rsnERRORTEXT=errortext

DFS4400E RM IS NOT ENABLEDTO USE REPOSITORY FORREPOTYPE=repotype

ExplanationIMS is defined to import stored resourcedefinitions automatically from the IMSRSCrepository, as specified with AUTOIMPORT=REPO orAUTOIMPORT=AUTO and the REPOSITORY section.However, Resource Manager (RM) is not enabled touse the repository for the defined repository type. Youmust take one of the following actions:

• Enable RM with the repository before IMS isrestarted

• Modify IMS to disable automatic import from therepository

• Remove the definitions in the REPOSITORY section



http://www.ibm.com/support/knowledgecenter/SSEPH2_15.1.0/com.ibm.ims15.doc.sur/ims_dfsurcl0.htm#ims_dfsurcl0

http://www.ibm.com/support/knowledgecenter/SSEPH2_15.1.0/com.ibm.ims15.doc.sur/ims_dfsurcl0.htm#ims_dfsurcl0

http://www.ibm.com/support/knowledgecenter/SSEPH2_15.1.0/com.ibm.ims15.doc.cr/imscmds/ims_updateims.htm#ims_cr2updateims

repotypeIndicates the repository type. The valid value forrepotype is IMSRSC.

System actionIMS terminates abnormally with abend code 0400,subcode 01.


System programmer responseModify the AUTOIMPORT option in the dynamicresource definition section of the DFSDFxxx PROCLIBmember to disable automatic import from therepository, or enable RM to use the repository.



Related conceptsIMS initialization with the IMSRSC repository(System Administration)Related informationIMS abend 0400“IMS problem determination” on page 11IMS messages and codes problemdetermination is accomplished by usingprocedures established by IBM.


http://www.ibm.com/support/knowledgecenter/SSEPH2_15.1.0/com.ibm.ims15.doc.sag/system_admin/ims_admin_repo_init.htm#ims_admin_repo_init





DFS4401E RM requestname ERROR, RC=rcRSN=rsn ERRORTEXT=errortext

ExplanationAn error occurred while processing the specified RMrequest type.

If the error message is issued during IMS autoexportto the IMSRSC repository, then the autoexport was notsuccessful. The error return and reason code indicatethe error. Once the error is resolved, you can issuean EXPORT DEFINITION(CHANGESONLY) commandor wait for the next autoexport to trigger the writeof the changed resource definitions to the IMSRSCrepository.

In the message text:requestname

Indicates the RM request type that failed orthat an IMS, OM, RM, or SCI function failedwhen automatic import or automatic export waspreparing to issue an RM request.

rcThe high-order byte of the return code helps youidentify the address space that returned the error.X'00'

Identifies an IMS error, where the return codeand reason code is mapped by the DFSCMDRRmacro.

X'01'Identifies an SCI error, where the return codeand reason code is mapped by the CSLSRRmacro.

X'02'Identifies an OM error, where the return codeand reason code is mapped by the CSLORRmacro.

X'03'Identifies an RM error, where the return codeand reason code is mapped by the CSLRRRmacro.

After you determine the address space thatreturned the error, you can further investigate thereturn and reason codes returned from the sourcemacro.

rsnIndicates the reason code from the specified RMrequest type. For a description of the reason code,see the CSLSRR or CSLRRR macro.

errortextIndicates error text. errortext can be blank orthe error text from the RM request type, whichprovides more information about the error.

errortext can have the following value:CHANGE LIST

Indicates that the attempt to delete the changelist failed. If the change list exists, it isprocessed the next time IMS warm starts oremergency restarts, or deleted the next timeIMS cold starts.

This message can be issued in any of the followingsituations:

• During IMS cold start• While the IMS change list is being imported

internally during IMS warm or emergency restart• While the IMS change list is being deleted during

IMS warm start, emergency restart, or cold start• During IMS automatic export to the IMSRSC

repository

System actionIf this message is issued during IMS cold start whileresource definitions are being imported automaticallyfrom the IMSRSC repository, the IMS system endsabnormally with abend code 3368. If the messageis issued during IMS change list processing, the IMSsystem continues processing.

If the DFS4401E message with ERRORTEXT=CHANGELIST is issued after the IMS restart is complete, IMSinitiates a simple checkpoint to be able to log thechange list time in the checkpoint log record. The IMScheckpoint is taken so that the residual change listthat was not deleted is not reprocessed at IMS restart.

The DFS4401E message might be accompanied by aDFS4744E message to provide additional informationfor an RM error that occurred.

If the DFS4401E message is issued duringthe autoexport processing after the DFS4390IAUTOEXPORT INITIATED message, then IMScontinues processing. The resource definitions are


not yet exported to the IMSRSC repository. If theDFS4401E message is issued during autoexportprocessing during IMS shutdown processing, the IMSshutdown is aborted. You cannot shut down IMS untilthe resource definitions are successfully exported tothe repository or automatic export to the repository isturned off.

System programmer responseThe RM return and reason codes are described in theCSLRRR macro.

If this message resulted in termination of IMS, fixthe problem that resulted in the RM error and thenrestart IMS. If this message is issued while IMS isprocessing the change list, the resource definitionsthat were being imported might be in NOTINIT-xx-REPOCHGLIST state. The resources and descriptorsremain NOTINIT until IMS is restarted and the nextinternal import from the change list succeeds, oruntil you issue an IMPORT DEFN SOURCE(REPO)command to successfully import the resource andthe descriptor definitions from the repository. Youcan issue the QUERY DB, QUERY PGM, QUERYRTCODE, and QUERY TRAN commands to display theresources that are in the NOTINIT-xx-REPOCHGLISTstate. There are no QUERY commands for displayingdescriptors in NOTINIT state because descriptors donot have status. See message DFS4414I for names ofthe descriptors that are still in NOTINIT state if theinternal import from the change list failed.

If the DFS4401E message with ERRORTEXT=CHANGELIST is issued by IMS during restart processing, itindicates that IMS was not able to delete the IMSchange list from the IMSRSC repository. You mustissue a DELETE DEFN TYPE(CHGLIST) command todelete the change list from the repository.

If the DFS4401E message is issued duringthe autoexport processing after the DFS4390IAUTOEXPORT INITIATED message, then IMScontinues processing. Because the resourcedefinitions are not yet exported to the IMSRSCrepository, after the error is resolved, youcan issue an EXPORT DEFN TARGET(REPO)OPTION(CHANGESONLY) command to manuallyexport the resource definitions or wait for the nextautomatic export.

If the DFS4401E message is issued during autoexportprocessing during IMS shutdown processing, the IMSshutdown is aborted. You cannot shut down IMS untilthe resource definitions are successfully exported tothe repository or automatic export to the repositoryis turned off. After the error is resolved, you canattempt to shut down IMS so that the automatic exportis successful or you can turn off automatic export

by using the UPDATE IMS SET(AUTOEXPORT(N))command.

Module:DFSIP300, DFSRPS60, DFSICM30, DFSRPS50

Related conceptsIMS initialization with the IMSRSC repository(System Administration)Related tasksCold starting an IMS system that usesthe IMSRSC repository (Operations andAutomation)Related referenceDFSDFxxx member of the IMS PROCLIB dataset (System Definition)Related information0400 (Messages and Codes)“IMS problem determination” on page 11IMS messages and codes problemdetermination is accomplished by usingprocedures established by IBM.

DFS4402W THE REPOSITORY SECTION ISIGNORED BECAUSE IMS ISENABLED WITH variabletext

ExplanationThe REPOSITORY section of the DFSDFxxx member ofthe IMS PROCLIB data set is ignored because IMS isnot enabled with DRD (MODBLKS=OLC) or IMS is notusing RM services (RMENV=N).

In the message text:variabletext

Can be one of the following values:

MODBLKS=OLCRMENV=N

The DFS4402W message is issued only if theREPOSITORY section is defined in the DFSDFxxxmember of the IMS PROCLIB data set along withMODBLKS=OLC and RMENV=N.

System actionIMS continues processing with MODBLKS=OLC orRMENV=NO. IMS is not enabled to use the IMSRSCrepository.

System programmer response:If IMS will be enabled with MODBLKS=OLC orRMENV=NO, remove the REPOSITORY= statementfrom the DFSDFxxx member so that the DFS4402Wmessage is not issued at the next restart. Or, if theIMSRSC repository is to be enabled, modify IMS to be




http://www.ibm.com/support/knowledgecenter/SSEPH2_15.1.0/com.ibm.ims15.doc.oag/ims_coldstart_drd_repo.htm#ims_coldstart_drd_repo



http://www.ibm.com/support/knowledgecenter/SSEPH2_15.1.0/com.ibm.ims15.doc.sdg/ims_dfsdfxxx_proclib.htm#ims_dfsdfxxx_proclib



enabled with DRD if MODBLKS=OLC and to use RMservices by removing the RMENV=NO statement.

Module:DFSDFN10

Related conceptsIMS initialization with the IMSRSC repository(System Administration)Related referenceDFSDFxxx member of the IMS PROCLIB dataset (System Definition)Related information“IMS problem determination” on page 11IMS messages and codes problemdetermination is accomplished by usingprocedures established by IBM.

DFS4403E REPOSITORY= STATEMENT ISNOT DEFINED FOR REPOSITORYTYPE=repotype

ExplanationDuring IMS initialization, it was detected that theREPOSITORY= statement was not coded in theREPOSITORY section of the DFSDFxxx member of theIMS.PROCLIB data set.


Indicates the repository type.

When repotype is IMSRSC, the REPOSITORY=statement is not defined in the DFSDFxxx memberand the repository section header might notbe defined. If AUTOIMPORT=AUTO is specified,IMS issues this message and AUTOIMPORT fromRDDS or MODBLKS. If AUTOIMPORT=REPO isspecified, IMS initialization terminates abnormallywith abend 0071 and RC=27,2108.

System actionIf AUTOIMPORT=REPO is specified, IMS initializationends abnormally with IMS abend code 0071 andreturn code 27,2108.

If AUTOIMPORT=AUTO is specified, IMS initializationresource definitions are read from RDDS or MODBLKSif they are defined and not empty.


System programmer responseFor AUTOIMPORT=REPO, add the REPOSITORY=statement to the DFSDFxxx member of the IMSPROCLIB data set and restart IMS.

For AUTOIMPORT=AUTO, if the resource definitionsare to be imported from the repository, add theREPOSITORY= statement to the DFSDFxxx member ofthe IMS PROCLIB data set and restart IMS.

If using RDDS or MODBLKS is valid, no action isneeded.



Module:DFSDFN10

Related referenceDFSDFxxx member of the IMS PROCLIB dataset (System Definition)Related informationIMS abend 0071“IMS problem determination” on page 11IMS messages and codes problemdetermination is accomplished by usingprocedures established by IBM.

DFS4404I IMS CONNECTED TORMNAME=rmname FORREPOSITORY TYPE=repotypeREPOSITORY NAME=reponame

ExplanationIMS successfully connected to the repository whosename and type are shown in the message.

In the message text:rmname

Indicates the Resource Manager (RM) name.repotype

Indicates the repository type. The only valid valueis IMSRSC.

reponameIndicates the repository name.













Related conceptsIMS initialization with the IMSRSC repository(System Administration)Related tasksCold starting an IMS system that usesthe IMSRSC repository (Operations andAutomation)Related referenceDFSDFxxx member of the IMS PROCLIB dataset (System Definition)

DFS4405W REPOSITORY FORREPOTYPE=repotype IS EMPTY,REPONAME=reponame

ExplanationIMS connected successfully to the repository whosename and type are indicated in the message. However,Resource Manger (RM) indicated that the repositorywas empty. No resources are imported from therepository.

At the end of IMS cold start, you must issue theEXPORT DEFN TARGET(REPO) command or run theRDDS-to-Repository utility (CSLURP10) to populatethe runtime resource definitions to the repository.





System programmer responseIssue the EXPORT DEFN TARGET(REPO) commandor use CSLURP10 to export the runtime resourcedefinitions to the repository.

User responseIssue the EXPORT DEFN TARGET(REPO) commandor use CSLURP10 to export the runtime resourcedefinitions to the repository.


Module:DFSIP300

Related tasksCold starting an IMS system that usesthe IMSRSC repository (Operations andAutomation)Related referenceDFSDFxxx member of the IMS PROCLIB dataset (System Definition)

DFS4406E REPOSITORY= STATEMENTFOR REPOTYPE=repotypeINCONSISTENT OVER RESTART

ExplanationThe IMS.PROCLIB member DFSDFxxxwas inconsistent with REPOSITORY forREPOTYPE=repotype usage before the restart.


The repository type

System actionIMS terminates with abend 0168 and code X’1C’.

Programmer responseCorrect the IMS.PROCLIB member DFSDFxxxto include or not include REPOSITORYusage by adding or deleting thestatement: REPOSITORY=(TYPE=repotype) in the<SECTION=REPOSITORY> section.

Non-XRF and XRF active systems need come up withrepository usage as follows:

1. Changing from REPO(Yes) to REPO(No) is onlyallowed on a cold start

2. Changing from REPO(No) to Repo(Yes) is allowedon NRE. It is also allowed on ERE if an UPDIMS command was used before the restart tosuccessfully connect to the repository.

3. Changing Repo(No) to Repo(No) is always allowedunless an UPD IMS command was used before therestart to connect to the repository.

4. Changing Repo(Yes) to Repo(Yes) is alwaysallowed.

XRF alternate systems need to come up withrepository usage consistent with the SNAPQcheckpoint from which it was restarted.

Module:














DFSRLP00Related informationIMS abend 0168

DFS4407A IMS IS NOT ENABLED TOUSE THE REPOSITORY FORREPOTYPE=repotype

ExplanationA TAKEOVER (TKO) occurred on an XRF alternatesystem that has failed processing a type22 recordfor the command: UPD IMS SET(LCLPARM(REPO(Y)REPOTYPE(repotype))). The command was successfulon the XRF active system.


The repository type

System actionProcessing continues, but the DFS4407A messageremains highlighted on the console until an UPDcommand to connect to the repository is processed onthe new XRF active system.


Programmer responseCorrect any problems that might cause repositoryconnection failures, and issue the UPD command onthe new XRF active system again.

Module:DFSIU130

DFS4407E IMS IS NOT ENABLED TOUSE THE REPOSITORY FORREPOTYPE=repotype

ExplanationAn extended recovery facility (XRF) alternatesystem failed processing a type22 record forcommand UPD IMS SET(LCLPARM(REPO(Y)REPOTYPE(repotype))) . The command was successfulon the XRF active system.


The repository type

System actionProcessing continues, but the XRF active is now usingthe repository while the XRF alternate is not.

Programmer responseCorrect any problems that might cause repositoryconnection failures, and issue the UPD IMS commandon the active IMS again.

Module:DFSIU130

DFS4408I REPOSITORY CHANGE LISTPROCESSING INITIATED

ExplanationThis message is issued at the end of IMS restart(warm start or emergency restart), after log recordprocessing, if the restarting IMS is enabled with theIMSRSC repository. If the restarting IMS is enabledwith the IMSRSC repository, IMS determines whethera change list exists and should be processed.

If a change list exists, all change list resourcesand descriptors are quiesced and imported internallyfrom the repository asynchronously from IMS restart.The change list resources and descriptors aremarked as NOTINIT, with a status of NOTINIT-xx-REPOCHGLIST, so that no work can be processed forthem until the change list resources are imported intoIMS. If any of the resources on the change list donot exist, a new resource is created with no attributesdefined, taking the default value if any, and markedNOTINIT.

If a change list does not exist, this message is followedby message DFS4412I.

System action:IMS reads the change list from the repository andstarts processing the list by importing the storedresource definitions into IMS as runtime resourcedefinitions. Change list processing might be finishedafter IMS restart completes. If change list processingis successful, message DFS4412I is issued.


Module:DFSRPS20

DFS4409A REPOSITORY CHANGE LISTIS NOT ACCESSIBLE - IMSRESOURCES MAY BE OUT OF SYNC



ExplanationDuring IMS restart (warm start or emergency restart),IMS was unable to access the IMSRSC repository todetermine whether a change list existed.

This message is preceded by the following message:DFS4401E RM CSLRPxxx REQUEST FAILED, RC=xxxxxxxx RSN=xxxxxxxx ERRORTEXT=

The DFS4401E message indicates why the repositoryis not accessible. For example, the repository is notaccessible if the repository is stopped, the RepositoryServer is down, or RM is down.

If the change list does not exist in the repository, thereis no problem.

If the change list exists in the repository, the IMSruntime resource definitions are out of synchronizationwith the stored resource definitions in the repository.The change list contains the list of resources anddescriptors that were imported while IMS was down.

System action:During IMS restart, IMS does not create or updateresources and descriptors that are listed in the changelist. The change list in the IMSRSC repository is notdeleted. The change list will be processed and deletedthe next time IMS restarts.

User responseCorrect the problem, shut down the IMS, and thenrestart it, so that the change list processing can becompleted successfully and the change list is deleted.

Alternatively, if you do not want to shut down IMS, youcan take one of the following actions:

• Issue the QUERY DB, QUERY DBDESC, QUERYPGM, QUERY PGMDESC, QUERY RTC, QUERYRTCDESC, QUERY TRAN, or QUERY TRANDESCcommand by using time stamps to determinewhich resource definitions are outdated. Then,import those resources by using the IMPORT DEFNSOURCE(REPO) command.

• Import all resources again, by issuing thecommand: IMPORT DEFN SOURCE(REPO)NAME(*) TYPE(ALL) OPTION(UPDATE).

If an IMPORT DEFN SOURCE(REPO) command isissued to update the IMS runtime definitions with thestored resource definitions in the repository, a DELETEDEFN TYPE(CHGLIST) command must be issued todelete the IMS change list from the repository.

Module:DFSRPS60

DFS4410I REPOSITORY CHANGE LISTPROCESSING SUCCEEDED FORRSCTYPE=rsctype COUNT=count

ExplanationRuntime resource definitions for IMS resources anddescriptors are now synchronized with the storeddefinitions in the IMSRSC repository.

During IMS restart, IMS detected a change list forthe IMS in the repository and applied the changes bycreating and updating resources or descriptors for thespecified resource type.

One DFS4410I message is issued for each resourcetype that is processed. For example, if only programsand transactions are in the change list, you receivetwo of these messages, one for PGM and the other forTRAN.

The IMS change list contains resources or descriptorsthat were imported while IMS was down. It does notcontain resources or descriptors that were deletedwhile IMS was down.

In the message text:rsctype

Indicates the resource type, which can be DB,DBDESC, PGM, PGMDESC, RTCODE, RTCDESC,TRAN, or TRANDESC.

countIndicates the count of resources that werecreated, updated, or both.

System action:Resources are created or updated, and the NOTINITstatus is reset. At the end of successful IMS changelist processing, the change list is deleted from therepository.

User response:Start the databases that were updated so that they areusable.

Module:DFSIP100

DFS4411E REPOSITORY CHANGE LISTPROCESSING FAILED RC=rcRSN=rsn

ExplanationIMSRSC repository change list processing encounteredan error. The change list contains the names ofresources and descriptors that were imported whilethe IMS was down.

In the message text,rc

Indicates the IMPORT command return code,which is documented in the DFSCMDRR macro.

rsnIndicates the IMPORT command reason code,which is documented in the DFSCMDRR macro.


System actionAll of the database, program, routing code, andtransaction resources that are named in the changelist will continue to have a status of NOTINIT-xx-REPOCHGLIST. This status prevents these resourcesfrom being used until the situation that caused changelist processing to fail is corrected and the resourcesare imported successfully from the repository.

The change list is not deleted from the repository;it will be processed and deleted the next time IMSrestarts.

User responseCorrect the problem, and take one of the followingactions:

• Shut down IMS, and then restart it, so thatthe change list processing can be completedsuccessfully and the change list is deleted.

• Alternatively, if you do not want to shut down IMS,you can take one of the following actions:

– Issue the following commands to determinewhich resources are in NOTINIT status becausethe change list processing failed: QUERY DB STATUS(NOTINIT) QUERY PGM STATUS(NOTINIT) QUERY RTC STATUS(NOTINIT) QUERY TRAN STATUS(NOTINIT)

For every resource that has a status of NOTINIT-XX-REPOCHGLIST, import the resource by usingthe IMPORT DEFN SOURCE(REPO) command.When you issue the IMPORT command, importdatabases and programs before routing codes andtransactions.

Find the DFS4414I REPOSITORY CHANGE LISTPROCESSING INITIATED FOR DESCRIPTORmessages and import those descriptors fromthe repository by using the IMPORT DEFNSOURCE(REPO) command.

– Issue the QUERY DB, QUERY DBDESC, QUERYPGM, QUERY PGMDESC, QUERY RTC, QUERYRTCDESC, QUERY TRAN, or QUERY TRANDESCcommand by using time stamps to determinewhich resource definitions are outdated. Then,import those resources by using the IMPORTDEFN SOURCE(REPO) command.

– Import all the resources and descriptors fromthe IMS change list so that the IMS runtimedefinitions can be updated with the storedresource definitions from the IMSRSC repository.For example, you can issue the following IMPORTcommand:

IMPORT DEFN SOURCE(REPO) NAME(*)TYPE(ALL) OPTION(UPDATE)

– After the resource definitions are imported toupdate the IMS runtime definitions with the storedresource definitions from the repository, youmust issue a DELETE DEFN TYPE(CHGLIST)command to delete the IMS change list from therepository. If the DELETE DEFN command is notissued, the change list will be processed at thenext IMS restart.

Module:DFSIP100, DFSRPS60

Related referenceIMPORT DEFN SOURCE(REPO | RDDS)command (Commands)

DFS4412I REPOSITORY CHANGE LISTPROCESSING COMPLETED

ExplanationIMS restart completed processing the IMSRSCrepository change list.

If the restarting IMS is enabled with the repositoryand the change list does not exist, message DFS4412Ifollows a DFS4408I message.

If the restarting IMS is enabled with the repositoryand the change list exists, message DFS4412I followszero or more DFS4410I messages. Message DFS4412Iindicates that all of the resource types have beensuccessfully processed. Because IMS change listprocessing is done in parallel with IMS restart, thismessage might be issued after IMS restart completes.

Message DFS4412I is not issued if DFS4411Emessage, which indicates that change list processingfailed, is issued.

System action:The change list, if one existed, is deleted from therepository.


Module:DFSRPS60

DFS4413E REPOSITORY CHANGELIST PROCESSING FAILEDFOR RSCNAME=rscnameRSCTYPE=rsctype CC=cc

ExplanationImport from the change list failed for the specifiedresource.



http://www.ibm.com/support/knowledgecenter/SSEPH2_15.1.0/com.ibm.ims15.doc.cr/imscmds/ims_import_repo_rdds.htm#ims_import_repo_rdds


rscnameIndicates the name of the resource.

rsctypeIndicates the resource type, which can be DB,DBDESC, PGM, PGMDESC, RTC, RTCDESC, TRAN,or TRANDESC.

ccIndicates the IMPORT command completion code,which is documented in the DFSCMDRR macro.

System action:Import from the change list fails. The resources remainmarked NOTINIT.

User responseCorrect the problem, shut down IMS, and then restartit, so that the change list processing can be completedsuccessfully and the change list is deleted.

Alternatively, if you do not want to shut down IMS, youcan take one of the following actions:

• Issue the following commands to determine whichresources are in NOTINIT status because thechange list processing failed: QUERY DB STATUS(NOTINIT) QUERY PGM STATUS(NOTINIT) QUERY RTC STATUS(NOTINIT) QUERY TRAN STATUS(NOTINIT)

For every resource that has a status of NOTINIT-XX-REPOCHGLIST, import the resource by using theIMPORT DEFN SOURCE(REPO) command. Whenyou issue the IMPORT command, import databasesand programs before routing codes and transactions.

Find the DFS4414I REPOSITORY CHANGE LISTPROCESSING INITIATED FOR DESCRIPTORmessages and import those descriptors fromthe repository by using the IMPORT DEFNSOURCE(REPO) command.

• Issue the QUERY DB, QUERY DBDESC, QUERYPGM, QUERY PGMDESC, QUERY RTC, QUERYRTCDESC, QUERY TRAN, or QUERY TRANDESCcommand by using time stamps to determinewhich resource definitions are outdated. Then,import those resources by using the IMPORT DEFNSOURCE(REPO) command.

• Import all resources again, by issuing thecommand: IMPORT DEFN SOURCE(REPO)NAME(*) TYPE(ALL) OPTION(UPDATE).

Module:DFSIP100, DFSIP200

Related referenceIMPORT DEFN SOURCE(REPO | RDDS)command (Commands)

DFS4414I REPOSITORY CHANGE LISTPROCESSING INITIATED FORDESCRIPTOR NAME=descnameTYPE=desctype

ExplanationIMSRSC repository change list processing is initiatedfor the specified descriptor name. If change listprocessing fails after this message is issued, thedescriptor remains in NOTINIT status and cannot beupdated, referenced as a model, or exported to therepository or an RDDS.

In the message text:descname

Indicates the name of the descriptor.desctype

Indicates the descriptor type, which can beDBDESC, PGMDESC, RTCDESC, or TRANDESC.



Module:DFSRPS60

DFS4419I RESOURCE DEFINITIONS NOTEXPORTED FOR REPOSITORYTYPE=repotype, NAME=reponame

ExplanationIf IMS is shut down normally with a /CHECKPOINTFREEZE, /CHECKPOINT DUMPQ, or /CHECKPOINTPURGE command and there are new or updatedresource definitions that have not been exported tothe IMSRSC repository, the DFS4419I message isissued during the shutdown process. This messageindicates that the definitions stored in the repositoryare not in synchronization with the IMS system'sonline definitions at the time of shutdown. After theDFS4419I message is issued, IMS continues to shutdown.




System action:IMS continues to shut down.





User responseIf IMS is warm started after a normal shutdownduring which the DFS4419I message was issued,its online resource definitions are recovered fromthe log and are the same as they were atshutdown time. The EXPORT DEFN TARGET(REPO)OPTION(CHANGESONLY) command must be issuedafter IMS is up to ensure that the latest resourcedefinitions are exported to the IMSRSC repository.

If IMS is cold started after a normal shutdown duringwhich the DFS4419I message was issued, and itsresource definitions are imported from the repository,the online definitions will not be the same as theywere at the time of shutdown unless the repositorywas updated before the cold start. The Create RDDSfrom Log Records utility (DFSURCL0) and the RDDSto Repository utility (CSLURP10) can be used toupdate the repository with the most current MODBLKSresource definitions in the IMS log before cold startingthe IMS. The RDDS and CSLURP10 utility do notsupport MSC resources, so MSC resources must be re-created by using the IMS type-2 CREATE commands.

If an RDDS was created by the Create RDDS from LogRecords utility (DFSURCL0) with the EXPORTNEEDEDparameter to hold any new or modified resources thatwere not exported to the IMSRSC repository beforeIMS was shut down, you can specify that RDDS onthe IMPORT command after IMS cold starts from therepository.


Module:DFSICM30

DFS4420E THE JCL IS MISSING A SYSIN DDSTATEMENT.

Explanation:The IMS Catalog Record Purge utility (DFS3PU10)requires a SYSIN DD statement, but one was notprovided.

User response:Provide a SYSIN statement with the name of the dataset that contains the input parameters for the utility.The DCB parameters for the data set are RECFM=FBand LRECL=80.

Module:DFS3PU10

DFS4421E THE JCL IS MISSING A SYSUT1 DDSTATEMENT.

Explanation:The IMS Catalog Record Purge utility requires aSYSUT1 data set for output from the analysis functionand input to the purge function.

User response:Provide a SYSUT1 DD statement and run the utilityagain.

Module:DFS3PU10

DFS4422E THE SYSIN DATA SET FAILED TOOPEN. OPEN RC = 666666.

ExplanationThe MVS open operation failed for the IMS CatalogRecord Purge utility SYSIN data set. 666666 is thereturn code from the request.


User response:Determine the underlying problem with the data setand resubmit the job.

Module:DFS3PU10

DFS4423E THE SYSUT1 DATA SET FAILED TOOPEN. OPEN RC = 666666.

ExplanationThe MVS open operation failed for the IMS CatalogRecord Purge utility SYSUT1 data set. 666666 is thereturn code from the request.


User response:Determine the underlying problem with the data setand resubmit the job.

Module:DFS3PU10

DFS4424E UPDATE STATEMENTS WEREPROVIDED IN PURGE MODE.

Explanation:Both MODE PURGE and one or more UPDATEstatements were specified at the same time. UPDATEstatements are not supported by the IMS CatalogRecord Purge utility when MODE PURGE is specified.The utility supports UPDATE statements when eitherthe MODE statement is omitted or when either MODEANALYSIS or MODE BOTH is specified.


User response:Either remove the UPDATE statements from the SYSINdata set or change the MODE statement to eitherANALYSIS or BOTH. When the changes are complete,run the utility again.

Module:DFS3PU10

DFS4425E UNEXPECTED STATUS CODE 22ON A 4444 CALL FOR CATALOGRECORD 88888888.

ExplanationThe IMS Catalog Record Purge Utility received anunexpected status code from a catalog DL/I call.


22Status code from the DL/I call

4444DL/I call type

88888888Catalog resource name

System action:The utility ends with a U1002 abend.

User response:Ensure that no duplicate DELETE statements areincluded in the SYSUT1 data set and that the DBnames in any UPDATE statements are correct. If noerrors are found in the utility input data sets, consultthe troubleshooting information for the specific DL/Istatus code.

Module:DFS3PU10


DFS4426I A DELETE STATEMENT WASWRITTEN TO THE SYSUT1DATA SET FOR PSB mbr-nameINSTANCE=yydddhhmmssth

or

A DELETE STATEMENT WAS WRITTEN TOTHE SYSUT1 DATA SET FOR DBD mbr-nameINSTANCE=yydddhhmmssth DBVER=version

ExplanationThe utility generated a DELETE statement in theSYSUT1 data set for the instance of the DBD or PSBmember that is identified in the message text. The

instance is uniquely identified by the timestamp valueyydddhhmmssth. When the utility is run in PURGEmode, the utility reads the DELETE statement from theSYSUT1 data set and deletes the instance from theIMS catalog.

In the message text:mbr-name

The name of the DBD or PSB member.version

The DBD version number of the DBD instance. ForPSB instances, this field is not included in themessage text.

yydddhhmmssthThe ACBGEN timestamp that uniquely identifiesthe instance of the DBD or PSB member.


Module:DFS3PU10

DFS4427E INQY ENVIRON CALLFAILED, RC=xxxx REASON=yyyySTATUS=aa

ExplanationAn unexpected status code was returned whileprocessing the INQY ENVIRON call. This message canoccur when you run the IMS Catalog Recovery utility(DFS3RU00) in an environment that does not havethe IMS database code installed, such as in a DCCTLenvironment.


AIB return codeyyyy

AIB reason code

System actionThe utility ends with a U0071 abend and return code16.

System programmer response:Ensure that proper environment is being used to runthe utility.

Module:DFS3PU10

Related referenceAIB return and reason codes (Messages andCodes)



http://www.ibm.com/support/knowledgecenter/SSEPH2_15.1.0/com.ibm.ims15.doc.msgs/compcodes/ims_aibretandreasoncodes_ims.htm#ims_aibretandreasoncodes_ims


Related informationIMS abend 10020071 (Messages and Codes)

DFS4428E STATUS CODE 22 ON A 4444 CALLWAS RECEIVED FOR dbdpsbnmsegnamee timestamppppp.

ExplanationAn unexpected status code was returned for a DL/Icall made by the IMS Catalog Record Purge utility toretrieve a record from the IMS catalog database.


22Status code

4444DL/I call type

dbdpsbnmResource type

segnameeMember name

timestampppppACB generation timestamp for the record

System action:The utility terminates with a U1002 abend.

User response:Verify that the version of the record associated withthe indicated timestamp was not previously deleted bythe utility. Correct the cause of the status code andresubmit the job.

Module:DFS3PU10

DFS4429E RETURN CODE rc WAS SET DUE TOAN ERROR. CORRECT THE ERRORAND RERUN THE JOB.

or

CONTROL STATEMENT ERROR. REASON CODE=rs.

ExplanationThe IMS Catalog Record Purge utility encountered aproblem with the utility control statements in eitherthe SYSIN or SYSUT1 data set. If the problem is inthe SYSIN data set, in most cases the utility continuesto process the remaining statements; however, ifMODE BOTH is specified, in most cases the utilityterminates before the purge function executes. If theproblem is in the SYSUT1 data set, for most errors the

utility terminates immediately without processing thesubsequent statements.

In the message text:rs

The reason code that identifies the cause of theerror. Depending on the severity of the error, thereturn code that is issued by the utility upontermination might be 4 or 8.

DFS4429E can include any one of the followingpossible reason codes.

01More than one MODE statement was found in theSYSIN DD statements.

02The MODE type is either missing or invalid.

03An UPDATE statement was submitted withouteither the DBD or PSB keyword.

04The member name in either an UPDATE statementor a DELDBVER statement is missing, too long, orotherwise invalid.

05More than one wildcard character (*) was used in amember name.

06Either the number of instances to retain wasnot specified or the number was longer than 5characters.

07The specified number of DBD or PSB instances toretain is invalid.

08The specified number of DBD or PSB instances toretain is greater than the maximum of 65535.

09The specified number of days to retain DBD or PSBinstances is longer than 5 characters.

10The specified number of days to retain DBD or PSBinstances is an invalid number.

11The specified number of days to retain DBD or PSBinstances is greater than the maximum of 65535.

12The UPDATE statement for the utility containsa duplicate member name but with a differentnumber of instances or days. The retention criteriain the member record was not updated.

13Invalid statement in the SYSIN data set. Thestatement might be specified incorrectly or two or




more statements might be incompatible with eachother.

14Missing input for the SYSIN statement.

15Invalid DELETE statement. Any statements thatwere specified before this one in the SYSUT1data set were executed successfully. Subsequentstatements were not processed.

16Invalid DELDBVER statement. With MODE PURGE,any statements that were specified before thisone in the SYSUT1 data set were executedsuccessfully. Subsequent statements were notprocessed.

17No matching records for the UPDATE statement.Execution continues normally and the utility issuesreturn code 4 upon completion.

18Invalid use of a wildcard character (*).

19Invalid statement in the SYSUT1 data set.

20An error occurred that generated one of thefollowing messages:

• DFS4420E• DFS4421E• DFS4422E• DFS4423E• DFS4424E• DFS4485E

This code is no longer issued with DFS4429E.24

Open print_DCB failure.This code is no longer issued with DFS4429E.

System actionIf the error was encountered in the SYSIN dataset, in most cases the utility continues processingthe remaining control statements in the SYSIN dataset; however, if MODE BOTH is specified, the utilityterminates before the purge function executes. If theerror was encountered in the SYSUT1 data set, in mostcases, the utility terminates without processing theremaining control statements in the SYSUT1 data set.

Depending on the severity of the reason code inDFS4429E, the utility issues return code 4 or, in mostcases, 8 upon termination.

User response:

Review the explanation for the code, correct theunderlying error, and run the utility again.

Module:DFS3PU10

DFS4430I NO MEMBERS WERE ADDED TOTHE SYSUT1 DATA SET DUE TO ANERROR OR CURRENT RETENTIONCRITERIA.

or

AN ANALYSIS OF THE IMS CATALOG DID NOT FINDANY DBD OR PSB INSTANCES THAT ARE ELIGIBLEFOR DELETION.

ExplanationThe IMS Catalog Record Purge utility analyzed therecords in the IMS catalog and did not find any DBD orPSB instances that are eligible for deletion. The utilitydid not write any DELETE statements to the SYSUT1data set.

Neither the age of each DBD and PSB instance northe quantity of DBD and PSB instances in each recordexceed the retention criteria values set in either theheader segment of a record or in the CATALOG sectionof the DFSDFxxx PROCLIB member.

If a DELDBVER statement was specified in the SYSINdata set, either the utility did not find the versionnumber in the DBD record or the utility did not findthe DBD record in the IMS catalog.


Module:DFS3PU10

DFS4431I NO MEMBERS WERE DELETED DUETO AN ERROR OR NONE MATCHEDTHE DELETE STATEMENT.

Explanation:The DELETE statements in the SYSUT1 data set did notmatch any records in the IMS catalog database. TheIMS Catalog Record Purge utility did not delete anyrecords.

User response:Ensure that the DELETE statements in the SYSUT1data set match existing catalog records by running theIMS Catalog Record Purge utility in analysis mode.

Module:DFS3PU10


DFS4432E UNEXPECTED STATUS CODE sc ONA GHNP CALL FOR AN INSTANCEOF mbr-type mbr-name.

ExplanationWhile attempting to retrieve DBD or PSB segments formember mbr-name from the IMS catalog, the CatalogRecord Purge utility received an unexpected DL/Istatus code. The receipt of the status code indicateseither a problem with the utility or a corruption of theIMS catalog.

In the message text:mbr-name

The name of the DBD or PSB member that theGHNP call attempted to access.

mbr-typeType of the member, DBD or PSB, that the GHNPcall attempted to access.

scThe DL/I status code that was returned.

User response:Consult the status code information and, if possible,correct the underlying problem. If the problem cannotbe resolved, contact IBM Software Support.

Module:DFS3PU10

Related referenceDL/I status code explanations (Messages andCodes)IMS Catalog Record Purge utility (DFS3PU10)(System Utilities)

DFS4433E THE SYSIN DATA SET CONTAINSDELDBVER STATEMENTS WITHA MODE PURGE STATEMENT ORWITHOUT A MODE STATEMENT.

ExplanationOne or more DELDBVER statements were specified inthe SYSIN data set, but either a MODE statement wasnot specified or MODE PURGE was specified. WhenDELDBVER statements are specified in the SYSIN dataset, either MODE ANALYSIS or MODE BOTH must alsobe specified.

When MODE PURGE is specified in the SYSIN data set,DELDBVER statements can be specified only in theSYSUT1 data set.

User responseDepending on your needs take either of the followingactions:

• Add or modify the MODE statement in the SYSINdata set to specify either ANALYSIS or BOTH.

• Remove the DELDBVER statement from the SYSINdata set. When MODE PURGE is specified,DELDBVER can be specified only in the SYSUT1 dataset.

Module:DFS3PU10

Related referenceIMS Catalog Record Purge utility (DFS3PU10)(System Utilities)

DFS4434I INSTANCE yydddhhmmssth OFDBD name WAS ADDED TO ANEWLY CREATED RECORD IN THEIMS CATALOG.

or

INSTANCE yydddhhmmssth OF PSB name WASADDED TO A NEWLY CREATED RECORD IN THE IMSCATALOG.

ExplanationThe IMS Catalog Populate utility successfully added aninstance of metadata for the DBD or PSB name to theIMS catalog. This was the first instance of metadatafor this DBD or PSB; that is, a root segment had to beadded for this name. The DBD or PSB segment (plusits dependents) with time stamp yydddhhmmssth wasadded under this new root.

System action:Processing continues. Message DFS4437I is issuedwhen all changes since the previous checkpoint or thestart of the utility have been committed.


Module:DFS3PU00

Related referenceIMS Catalog Populate utility (DFS3PU00)(System Utilities)

DFS4435I INSTANCE yydddhhmmssth OFDBD name WAS ADDED TO ANEXISTING RECORD IN THE IMSCATALOG.

or


http://www.ibm.com/support/knowledgecenter/SSEPH2_15.1.0/com.ibm.ims15.doc.msgs/compcodes/ims_dlistatuscodesxpl.htm#ims_dlistatuscodesxpl

http://www.ibm.com/support/knowledgecenter/SSEPH2_15.1.0/com.ibm.ims15.doc.msgs/compcodes/ims_dlistatuscodesxpl.htm#ims_dlistatuscodesxpl

http://www.ibm.com/support/knowledgecenter/SSEPH2_15.1.0/com.ibm.ims15.doc.sur/ims_catalog_cleanuputility.htm#ims_catalog_cleanuputility






INSTANCE yydddhhmmssth OF PSB name WASADDED TO AN EXISTING RECORD IN THE IMSCATALOG.

ExplanationThe IMS Catalog Populate utility successfully addedan instance of metadata for the DBD or PSB nameto the IMS catalog. This was not the first instanceof metadata for this DBD or PSB; that is, a rootsegment already existed for this name. The DBD orPSB segment (plus its dependents) with time stampyydddhhmmssth was added under this existing root.

System action:Processing continues. Message DFS4437I is issuedwhen all changes since the previous checkpoint or thestart of the utility have been committed.


Module:DFS3PU00


DFS4436I INSTANCE yydddhhmmssth OFDBD name IS ALREADY IN THEIMS CATALOG AND WAS NOTADDED.

or

INSTANCE yydddhhmmssth OF PSB name ISALREADY IN THE IMS CATALOG AND WAS NOTADDED.

ExplanationThe IMS Catalog already contained a root segmentfor the DBD or PSB name, and under this root therewas an existing DBD or PSB segment with time stampyydddhhmmssth. Because DBDs or PSBs with thesame name and the same time stamp are assumedto represent identical instances of the DBD or PSB,nothing was added to the catalog.



Module:

DFS3PU00Related referenceIMS Catalog Populate utility (DFS3PU00)(System Utilities)

DFS4437I UPDATES TO THE IMS CATALOGHAVE BEEN COMMITTED.CHECKPOINT ID nnnnnnnn

ExplanationThe IMS Catalog Populate utility issued a CHKP(checkpoint) call to commit the prior updates to theIMS catalog. If the utility subsequently fails, updatesup to this point, as indicated by messages DFS4434Iand DFS4435I, do not have to be backed out.



Module:DFS3PU00


DFS4438E THE CONTROL STATEMENT DATASET (DDNAME SYSINP) FAILED TOOPEN. OPEN RC = rc

ExplanationIn opening the data set referred to by the DDstatement with the ddname SYSINP, the IMS CatalogPopulate utility encountered return code rc from anOPEN macro instruction.


The return code received by the DFS3PU00 utilityfrom the z/OS DFSMS OPEN macro instruction.

System action:The utility ended with return code 12. The catalog wasnot updated.

System programmer response:Ensure that the DD statement with the ddname IMSrefers to a sequential data set with 80-character fixed-length records.

Module:DFS3PU00











DFS4439E AN INVALID OPTION WASSPECIFIED IN THE CONTROLSTATEMENT DATA SET (DDNAMESYSINP)

ExplanationThe IMS Catalog Populate utility did not recognize theinformation in the data set that was referred to by theDD statement with ddname SYSINP.


System programmer response:You can specify several options by separating eachother with blanks or commas.

Module:DFS3PU00


DFS4440I THE DFS3PU00 UTILITY WILLLIST THE DBD AND PSBINSTANCES THAT ARE ADDED TOTHE IMS CATALOG.

ExplanationThe IMS Catalog Populate utility found no controlstatement data set (ddname SYSINP) in the JCL or nooption NOISRTLIST in the data set.

System action:For each instance of a DBD or PSB added to theIMS catalog, the IMS Catalog Populate utility issuesmessage DFS4434I or DFS4435I, which identifies thenew DBD or PSB segment.


Module:DFS3PU00


DFS4441I THE DFS3PU00 UTILITY WILLNOT LIST THE DBD AND PSBINSTANCES THAT ARE ADDED TOTHE IMS CATALOG.

ExplanationThe IMS Catalog Populate utility found theNOISRTLIST option in the control statement data set(ddname SYSINP).

System action:The utility does not issue message DFS4434I orDFS4435I for the DBD and PSB segments inserted inthe IMS catalog.


Module:DFS3PU00


DFS4442I THE DFS3PU00 UTILITY WILLLIST THE DBD AND PSBINSTANCES THAT ALREADY EXISTIN THE IMS CATALOG.

ExplanationThe IMS Catalog Populate utility found the optionDUPLIST in the control statement data set (ddnameSYSINP).

System action:For each instance of a DBD or PSB that was notadded to the IMS catalog because it was a duplicateof an existing instance, the utility issues messageDFS4436I, which identifies the duplicate DBD or PSBsegment that was not inserted.


Module:DFS3PU00


DFS4443I THE DFS3PU00 UTILITY WILLNOT LIST THE DBD AND PSBINSTANCES THAT ALREADY EXISTIN THE IMS CATALOG.

ExplanationThe IMS Catalog Populate utility found no controlstatement data set (ddname SYSINP) in the JCL or nooption DUPLIST in the data set.










System action:The utility does not issue DFS4436I messages forinstances of DBDs and PSBs that were not addedto the IMS catalog because they were duplicates ofexisting instances in the catalog.


Module:DFS3PU00


DFS4444I DISPLAY FROM ID=xxxx

Explanationxxxx is the IMSID. For DBCTL, specifying the executionparameter keyword PREMSG=N causes messages tobe issued without DFS000I as a prefix message. TheIMSID is appended to the end of the message. Displaycommand output includes prefix message DFS4444Iin order to include the IMSID.

Module:DFSDQMG0

DFS4445I CMD ACCEPTED ON SUBSYSTEMINTERFACE: command text imsid

or

CMD FROM MCS/E-MCS CONSOLEUSERID=xxxxxxxx:command text imsid

or

CMD FROM INTERNAL READER: command text imsid

ExplanationThis message displays a command that was enteredfrom an MCS or E-MCS console, the internal reader,or from another source such as an MGCR macro. Allthree forms of the message can be issued in a DBCTLsystem. A DB/DC or DCCTL system (which specifiesCMDMCD=Y,C,R or B) sees only the first form of themessage. The message variables are:xxxxxxxx

The user ID of the console from which thecommand was entered

command textThe command that was entered

imsidThe name of the system processing the command

Commands that are entered as a reply to anoutstanding WTO are included in the job log. If thecommand text is not required for commands enteredfrom an MCS or E-MCS console, the message might besuppressed.

Module:DFSDQMG0

DFS4446E xxxxxxxxxx yyyyyyyy DEFINED TORM AS zzzzzzzzzz

ExplanationIMS attempted to register a resource (yyyyyyyy)with the Resource Manager (RM) as resource typexxxxxxxxxx,. However, the resource was alreadyregistered as a different resource type (zzzzzzzzzz)within the same name type group.

In RM, a name type is a group of resource typesin which a given resource cannot be registeredconcurrently as more than one resource type.

In IMS, the finddest name type is the resource that isnormally the destination of a message. The followingresource types are associated with the "finddest"name type:

CPICA CPIC-defined transaction for APPC.

DESCRIPTORThe APPC descriptor.

LTERMThe VTAM logical terminal name.

MSNAMEThe MSC logical link path.

TRANA statically defined transaction.

System actionIf this error occurs during IMS initialization, the systemmight issue abend 3308. Otherwise, the currentprocess is rejected and online processing continues.

Operator responseIf the rejected resource is correct, try deleting theexisting resource in RM. For example, use the /CLScommand to remove LTERM resources. Otherwise,contact the system programmer.




System programmer responseRedefine the rejected resource to ensure that it isdefined correctly and consistently in the IMSplex.

Module:DFSRMD00, DFSRMIU0, DFSSLON0

DFS4447E RM REQUEST ERROR, rmreqRC=nnnnnnnn RMRC=xxxxxxxxRMRSN=yyyyyyyy

ExplanationThis message is issued asynchronously by an IMScontrol region command or other process when aResource Manager (RM) access service request fails.

In the message text:rmreq

The type of RM request, and is one of the followingvalues:

• QUERY• CLEANUP• UPDATE (for an update or delete request)

nnnnnnnnThe return code from the RM access service:Return code

MeaningX'10000004'

Input parameter is invalid.X'10000008'

No storage for AWE control block.X'1000000C'

No storage for blocks or buffer.X'10000010'

Update failed. No hidden block returned.X'10000012'

Update failed. Version mismatch. Hidden blockreturned.

X'10000014'Query failed.

X'10000018'Delete failed.

X'1000001C'No hidden blocks created.

X'10000020'Hidden blocks returned.

X'10000024'Update failed for a resource owned by the localIMS. No hidden block is returned.

X'10000028'Update bypassed because duplicate locallterm control blocks (CNTs) exist for the nodeor user.

xxxxxxxxThe return code from the RM call.

yyyyyyyyThe reason code from the RM call.

System actionThe command parameter is rejected.

Operator responseA problem exists with the retrieval or update of theresource in RM that is associated with the failedparameter. This command, and other commands,might continue to fail with the parameter in error untilthe resource problem is corrected.

For return code X'10000028', attempt to delete theuser by signing off the user or by taking a simplecheckpoint. Gather type 72 log records to determinethe process that created the duplicate local lterms.

ModuleDFSICLC0, DFSICLE0, DFSICLJ0, DFSICLN0,DFSICLP0, DFSICL50, DFSICL60, DFSICL70,DFSIC440, DFSIC450, DFSIDPB0, DFSIDPE0,DFSIDP10, DFSIDP40, DFSIDP70, DFSIDP80,DFSOCM30, DFSRMCL0, DFSRMSR0, DFSRMS00

Related conceptsIssue CSL RM requests to manage globalresources (System Programming APIs)

DFS4448A RM RESOURCE STRUCTUREUSAGE MISMATCH

ExplanationWhen IMS registers with a Resource Manager (RM)during IMS initialization or when an RM joins theIMSplex, IMS is informed whether RM is usinga resource structure or not. Afterward, messageDFS4448A is issued if RM changes the resourcestructure usage.

System actionOnline processing continues. IMS does not changeits use of the resource structure. If IMS was notusing a resource structure, it ignores the new resourcestructure. If IMS was using a resource structure,limited terminal processing continues. However, nonew terminals or users are allowed access to IMS,


http://www.ibm.com/support/knowledgecenter/SSEPH2_15.1.0/com.ibm.ims15.doc.spr/ims_writingcslrmclient_cslrmreqmanage.htm#ims_writingcslrmclient_cslrmreqmanage

http://www.ibm.com/support/knowledgecenter/SSEPH2_15.1.0/com.ibm.ims15.doc.spr/ims_writingcslrmclient_cslrmreqmanage.htm#ims_writingcslrmclient_cslrmreqmanage

and certain processes (including IMS shutdown) hangsuntil a resource structure is enabled.

If a /NRESTART or /ERESTART command wasprocessing (other than COLDCOMM or COLDSYS), andIMS issues message DFS4448A, IMS abends with0233.

Operator responseDetermine if RM was started properly; if not, terminateRM and restart it. Otherwise, terminate IMS and coldstart TM so the resource structure change will berecognized by TM.

Module:DFSCSL40, DFSRLP00

DFS4449W SNGLSIGN|MULTSIGN FORCED BYRESOURCE MANAGER

ExplanationA starting IMS system in an IMSplex environmentattempted to specify a value for single or multiplesignons (SGN= keyword in the IMS startup parameters,or as a keyword on the /NRE or /ERE command).The value conflicts with the value maintained by theResource Manager (RM). To ensure consistency foreach system in the IMSplex, RM maintains the signonspecification of the first IMS that joins the IMSplex.Every IMS that joins afterward must also use the firstvalue specified.

System actionIMS processing continues. Single and multiple signonsuse the global specification from RM.

Operator responseIf you want to use the signon value from the local IMS,shut down all IMS systems. Restart the local IMS firstwith the correct signon specification.

Module:DFSIRAC0

DFS4450I RESOURCE STRUCTUREREPOPULATION STARTING|COMPLETE

ExplanationIn an IMSplex environment, IMS received a structurerepopulate directive from the Resource Manager. IMSis either starting or has completed repopulating theresource structure with all locally known resources.



Module:DFSRMSR0


Chapter 92. DFS messages, DFS4451I - DFS4500E


DFS4451I LOGON REJECTED, NODExxxxxxxx, RC=yy

ExplanationIn an IMSplex environment, a VTAM terminal(xxxxxxxx) attempted to log on to IMS and IMSattempted to register the terminal to ResourceManager (RM). However, IMS rejected the logonattempt. Most logon failures are the result of the nodealready being registered to RM due to a previous logonor a command issued and state data verification failed.


The VTAM terminal IMS attempted to register ontoRM.

yyThe reason code for the failure. The following listprovides the reason codes and their meanings.Reason

Meaning01

The node was stopped.02

A mismatch occurred between the local andRM definition: a static terminal as opposed to adynamic terminal.

04A mismatch occurred between the local andRM definition: a single session as opposed to aparallel-session.

05A mismatch occurred between the local andRM definition: node device type.

06A mismatch occurred between the local andRM definition: output-only (CTB4OUTP).

07A mismatch occurred between the local andRM definition: output-only (CTBCPRT1).

08A mismatch occurred between the local andRM definition: MFS use (CTT2DIT).

09The node is already logged on to another activeIMS system.

0AThe node is already logged on to another IMSsystem, but this IMS cannot determine thestate of the owning system.

0BThe data in the static-node-user resourceDATA2 is invalid.

0CThe data in the static-node-user resource isinvalid.

0DThe data in the static-node-user resource isinvalid.

0EA mismatch occurred between the local andRM definition: the number of assigned LTERMS.Static terminal and LTERM definitions must beconsistent, and the /ASSIGN command mustbe used consistently in each IMS system.

0FA mismatch occurred between the local andRM definition: node device type.

10A mismatch occurred between the local andRM definition: the order of assigned LTERMs.Static terminal and LTERM definitions must beconsistent, and the /ASSIGN command mustbe used consistently in each IMS system.

11The node with LOCAL status recovery mode isowned by another system in the IMSplex. TheIMS that owns the node failed, but the userlogon exit, DFSLGNX0, has not indicated thatthe logon can continue in this situation.

12The node is already logged on to another IMSsystem, but this IMS cannot determine thestate of the owning system.

13The node is already logged on to another activeIMS system.

14A mismatch occurred between the local andRM definition: an assigned LTERM in RM isnot found in the local system. Static terminaland LTERM definitions must be consistent,and the /ASSIGN command must be usedconsistently in each IMS system.


15A mismatch occurred between the local andRM definition: static/dynamic LTERM.

16A mismatch occurred between the local andRM definition: an assigned LTERM in the localsystem exists in RM but is assigned to adifferent node. Static terminal and LTERMdefinitions must be consistent, and the /ASSIGN command must be used consistentlyin each IMS system.

17A system error occurred. The DFSPOOL GETstorage request failed.

18An RM system error occurred. RM did notreturn output on a CSLRMUPD request.

19An RM system error occurred. Output that wasreturned on a CSLRMUPD request containedinvalid data.

1AIMS attempted to register a node or LTERM butit was already registered to RM as a differentresource type within the same name typegroup. Message DFS4446E is also be issued.

1BAn unrecognized condition code was returnedon a CSLRMUPD output list entry.

1CAn unrecognized return or reason code wasreturned on a CSLRMUPD request. MessageDFS3308E should also be issued.

1DIMS attempted to register the node andLTERMs but failed after certain recoverableerrors occurred. IMS retried the registrationsbut reached the retry limit.

1EThe node had user information in RM, but theuser resource could not be found in RM. Thisis a temporary condition. Retry the terminallogon.

1FThe STSN node with LOCAL status recoverymode is owned by another system in theIMSplex. The owning IMS failed but the userlogon exit, DFSLGNX0, did not indicate that thelogon can continue in this situation.

20A user in Fast Path response mode attemptedto log on to an IMS system that is not Fast Pathcapable or is not using an EMHQ structure.

21The Resource Manager is unavailable.

22The resource structure is unavailable.

23A dynamic SLUP or FINANCE terminalattempted a warm session initiation, but therewas an error in processing the informationfrom RM. Retry the terminal logon.

24An ISC terminal attempted a warm sessioninitiation, but there was an error in processingthe information from RM. Retry the terminallogon.

25IMS has received an error return code from theResource Manager, but the error is consideredtemporary. Try logging on again.

System actionThe logon attempt is rejected.

Operator responseAttempt to correct the problem that is preventinglogon indicated by the return code, then retry thelogon. Use the /DISPLAY commands to determine thestatus of each terminal on each system in the IMSplex.

Module:DFSSLON0

DFS4452I RESOURCE CLEANUP STARTING|COMPLETE FOR xxxx

ExplanationWhen an IMS terminates in an IMSplex environment,the resources it maintained in the Resource Manager(RM) must be cleaned up. When IMS terminatesnormally, IMS cleans up during shutdown. When IMSterminates abnormally, a surviving IMS in the IMSplexperforms the cleanup. If there is no other active IMS,the failed IMS cleans up when it restarts.

This message indicates when an IMS starts andcompletes the cleanup process for the terminatingIMS. The terminating IMS is indicated by its IMS ID,xxxx.

System actionWhen clean up is performed by a different IMS, thecleanup processing is performed asynchronously andnormal online processing continues. When clean upis performed by the terminating or restarting IMS,


normal shutdown or restart resumes after cleanupcompletes.


Module:DFSRMCL0

DFS4453I LTERM MSGQ|EMHQ MESSAGESUNLOCKED FOR xxxx

ExplanationWhen an IMS terminates abnormally in an IMSplexenvironment, the LTERM messages that were lockedfrom the MSGQ or EMHQ structures must beunlocked so that they can be made available toterminals or users accessing another IMS systemin the IMSplex. The surviving IMS in the IMSplexunlocks the messages with cleaning up resources. Inaddition, when a restarting IMS connects with CQS, itunlocks any remaining messages, which also results inappropriate CQS cleanup.

The message text indicates which messages wereunlocked, MSGQ or EMHQ. The variable xxxx indicatesthe system for which messages were unlocked.

System actionWhen the unlock process is performed by a differentIMS, the unlocking is performed asynchronously andnormal online processing continues. When the unlockprocess is performed by the restarting IMS, normalrestart resumes after unlocking is complete.

Module:DFSRMCL0

DFS4454A WAITING FOR xxxx TO COMPLETERESOURCE CLEANUP, REPLY,RETRY OR CANCEL

ExplanationWhen another IMS in the IMSplex is cleaning up forthe initializing IMS, this Write to Operator with Reply(WTOR) message is issued during IMS initialization.IMS cannot continue initializing until cleanup iscomplete.

If you reply with RETRY, IMS attempts to completeinitialization. If you reply with CANCEL, IMS terminatesabnormally with user abend 3308.

System actionIMS waits until a response to the WTOR is entered.

Operator responseDetermine the status of the system that isperforming the cleanup; that system should issuemessage DFS4452I when it completes. After messageDFS4452I is issued, enter RETRY. If the system cannotcomplete the cleanup, terminate the system, whichpermits the initializing IMS to restart.

Module:DFSRMCL0


DFS4455E RESOURCE CLEANUP ERROR FORxxxx, RC=yy

ExplanationAn error occurred while resources were being cleanedup or messages unlocked for a terminating orinitializing IMS system.


The IMS ID of the terminating or initializing systemyy

The reason code for the error. The following listprovides the reason codes and their meanings.Reason

Meaning01

A system error occurred. A DFSPOOL GETstorage request failed.

02An error return code issued by CQS whenMSGQ LTERM messages are being unlocked.

03An error issued by CQS when EMHQ LTERMmessages are being unlocked.

04An error occurred while node resources inResource Manager (RM) were being cleanedup.

05An error occurred while user resources in RMwere being cleaned up.

06An error occurred while user ID resources inRM were being cleaned up.

07MSGQ and EMHQ messages could not beunlocked because IMS is not registered withCQS.



08MSGQ LTERM messages could not be unlockedbecause IMS is not connected to the MSGQstructure.

09EMHQ LTERM messages could not be unlockedbecause IMS is not connected to the EMHQstructure.

System actionIMS continue processing.

Programmer responseYou can perform cleanup processing again by issuing asimple checkpoint. If the problem persists, restart theIMS system that was not cleaned properly, or contactIBM Software Support.

Module:DFSRMCL0

DFS4456A RESOURCE STRUCTURE FAILED

ExplanationIMS received a "resource structure failed" directivefrom the Resource Manager.

System actionLimited online processing can continue, but terminaland user resource status cannot be committed untilthe resource structure becomes available. Until then,no new terminals or users can access IMS, andterminals or user access might hang (including duringIMS shutdown).

Operator responseDetermine and correct the problem with the resourcestructure.

Module:DFSRMSR0

DFS4457E RM REGISTRATION FAILED,NAME=xxxxxxxx

ExplanationIMS attempted to register to a Resource Manager(RM) in the IMSplex, but the registration was rejected.Message DFS3308E is also issued with the error returnand reason codes.

In the message text, xxxxxxxx is the name of theResource Manager for which registration failed.

System actionIMS continues processing. If there are other RMsystems active, IMS can continue communicating withthem.

Operator responseDetermine why RM rejected the registration.Determine if SCI, RM, and CQS are operating properlyon the affected RM's system. Restart RM if required.

Module:DFSCSL40


DFS4461E NEITHER AN ACB LIBRARY OR ACATALOG IMPORT DATA SET ISSPECIFIED IN THE UTILITY JCL.

ExplanationThe IMS Catalog Populate utility (DFS3PU00) requireseither an ACB library or a catalog import data setas input, but the utility JCL does not include a DDstatement for either type of input.

To specify an ACB library as input, an IMSACB01 DDstatement is required. To specify a catalog import dataset as input, a CCUCATIM DD statement is required.

System actionThe utility ended with return code 12. No records wereloaded or inserted into the IMS catalog.

Programmer responseSpecify either the IMSACB01 DD statement or theCCUCATIM DD statement in the DFS3PU00 utility JCL.

The IMSACB01 DD statement must refer to asingle ACB library or to a concatenation of ACBlibraries. If you specify additional IMSACBnn DDstatements, the ddnames must use increasing numericvalues in the last two character positions with nomissing intermediate values. For example, IMSACB02,IMSACB03, IMSACB04, and so on.

The CCUCATIM DD statement must refer to a catalogimport data set that contains a copy of an IMS catalog.

Module:DFS3PU00





DFS4462E FAILURE OPENING THE ACBLIBWITH DDNAME IMSACBxx. OPENRC = rc.

ExplanationAn ACB library data set failed to open for the IMSCatalog Populate utility (DFS3PU00). The ACB libraryis referenced in the utility JCL by the ddname,IMSACBxx, shown in the message.


The return code received by the DFS3PU00 utilityfrom the z/OS OPEN macro instruction when theACB library failed to open.

xxThe numbers that make up the final two charactersof the ddname that references the ACB library thatfailed to open.

System actionThe utility ends with return code 12. No records areloaded or inserted into the IMS catalog.

Programmer responseCheck that the DD statement identified in the messagetext references the ACB library data set correctly. Afterthe error is corrected, rerun the DFS3PU00 utility

Module:DFS3PU00


DFS4463E FAILURE OPENING THE ACBLIBWITH DDNAME IMSACBxx TOREAD THE DIRECTORY. OPEN RC= rc.

ExplanationIn opening the ACBLIB referred to by the DDstatement with the ddname IMSACBxx to identifyACBLIB members from the directory, the CatalogPopulate utility encountered return code rc from anOPEN macro instruction

System actionThe utility ended with return code 12. The catalog wasnot updated.

Programmer responseEnsure that the DD statement with the ddnameIMSACBxx refers to an ACBLIB.

Module:DFS3PU00


DFS4464E FAILURE OPENING THE ACBGENCATALOG WORK FILE. (DDNAMEACBCATWK) OPEN RC = rc

ExplanationThe IMS Catalog Populate utility (DFS3PU00) receivedreturn code rc from an OPEN macro instruction whenattempting to open the ACB generation work file that isreferred to by the ACBCATWK DD statement.




Programmer responseEnsure that the DD statement with the ddnameACBCATWK refers to the sequential file created duringACB generation. The work file has a list of the ACBlibrary members from which the catalog records arecreated. No DCB information needs to be provided onthe DD statement.

Module:DFS3PU00

Related referenceIMS Catalog Populate utility (DFS3PU00)(System Utilities)z/OS: OPEN return codes

DFS4465W THE JCL IS MISSING AN IMSDD STATEMENT FOR THE PSBLIBRARY THAT CONTAINS PSBpsb-name

ExplanationThe PSB identified by psb-name in the message textreferences a GSAM database, but the JCL for the IMSCatalog Populate utility (DFS3PU00) does not includean IMS DD statement for the PSB library. When a








http://www-01.ibm.com/support/knowledgecenter/SSLTBW_2.4.0/com.ibm.zos.v2r4.idad500/x1cb.htm?lang=en

PSB references a GSAM database, the utility JCL mustcontain an IMS DD statement to identify the PSBlibrary data set that contains the original PSB member.

The DFS3PU00 utility requires access to the originalPSB member to create a PSB record in the IMS catalogfor a PSB that references a GSAM database.

In the message text:psb-name

The PSB that contains PCBs that reference a GSAMdatabase.

System actionNo catalog record is built for PSB psb-name or for anyof the GSAM databases that are referenced by PCBs inthe PSB. The utility continues inserting other recordsin the catalog and ends with return code 4.

Programmer responseRerun the Catalog Populate utility with a DD statementthat has ddname IMS and that refers to yourIMS.PSBLIB and IMS.DBDLIB containing PSB psb-name and any referenced GSAM DBDs.

Module:DFS3PU00


DFS4466W PSB psb-name WAS NOT FOUNDIN PSBLIB. BLDL RC = rc. THEPSB WAS NOT ADDED TO THECATALOG.

ExplanationIn order to build the catalog record for PSB psb-name, which has GSAM PCBs, the IMS CatalogPopulate utility (DFS3PU00) tried to read the PSB fromIMS.PSBLIB but encountered return code rc from aBLDL macro instruction, most likely because the PSBwas not in IMS.PSBLIB.



rcThe return code received by the DFS3PU00 utilityfrom the z/OS DFSMS BLDL macro instruction.

System actionNo catalog record was built for PSB psb-name or forany of the GSAM databases that were referenced byPCBs in the PSB. The utility continues inserting otherrecords in the catalog and ends with return code 4.

Programmer responseRerun the Catalog Populate utility with a DD statementthat has ddname IMS and that refers to yourIMS.PSBLIB and IMS.DBDLIB containing PSB psb-name and any referenced GSAM DBDs.

Module:DFS3PU00

Related referenceIMS Catalog Populate utility (DFS3PU00)(System Utilities)z/OS: BLDL completion codes

DFS4467W ERROR LOADING PSB psb-nameFROM PSBLIB. LOAD RC = rc. THEPSB WAS NOT ADDED TO THECATALOG.

ExplanationIn order to build the catalog record for PSB psb-name, which has GSAM PCBs, the IMS CatalogPopulate utility (DFS3PU00) tried to read the PSBfrom IMS.PSBLIB but encountered return code rc froma LOAD macro instruction, most likely because themember psb-name was not a load module created bythe standard PSBGEN process.



rcThe return code received by the DFS3PU00 utilityfrom the z/OS DFSMS LOAD macro instruction.

System actionNo catalog record was built for psb-name or for anyof the GSAM databases that are used by PCBs in thePSB. The DFS3PU00 utility continues inserting otherrecords in the catalog and ends with return code 4.

Programmer responseCode an IMS DD statement that refers to yourIMS.PSBLIB and IMS.DBDLIB data sets that containthe PSB psb-name and any referenced GSAM DBDs.

Module:DFS3PU00







Related referenceIMS Catalog Populate utility (DFS3PU00)(System Utilities)z/OS: LOAD - Bring a load module into virtualstorage

DFS4468E THE PSB OR DBD LIBRARY DATASET FAILED TO OPEN. OPEN RC =rc.

ExplanationIn opening the PSBLIB and DBDLIB referred to by theDD statement with the ddname IMS, the IMS CatalogPopulate utility (DFS3PU00) encountered return coderc from an OPEN macro instruction.




Programmer responseEnsure that the DD statement with the ddname IMSrefers to a concatenation of your IMS.PSBLIB andIMS.DBDLIB.

Module:DFS3PU00

Related referenceIMS Catalog Populate utility (DFS3PU00)(System Utilities)z/OS: OPEN return codes

DFS4469W THE JCL IS MISSING AN IMSDD STATEMENT FOR THE DBDLIBRARY THAT CONTAINS DBDdbd-name

ExplanationThe IMS Catalog Populate utility (DFS3PU00)attempted to build the catalog record for the logicalDBD dbd-name, but the JCL for the DFS3PU00 utilitydoes not include an IMS DD statement for the DBDlibrary.

In the message text:dbd-name

The DBD that the DFS3PU00 utility could notcreate a record for in the IMS catalog.

System actionNo catalog record was built for the DBD dbd-nameor for any PSB with a PCB that references thisdatabase. The DFS3PU00 utility continues insertingother records in the catalog and ends with return code4.

Programmer responseRerun the DFS3PU00 utility with a DD statement thathas ddname IMS and that refers to your IMS.DBDLIBcontaining DBD dbd-name.

Module:DFS3PU00


DFS4470W GSAM DBD dbd-name NOT INDBDLIB. BLDL RC =rc. DBD ANDREFERENCING PSBS WERE NOTADDED TO THE CATALOG.

ExplanationIn order to build the catalog record for the GSAMDBD dbd-name, the IMS Catalog Populate utility(DFS3PU00) tried to read the DBD from IMS.DBDLIBbut encountered return code rc from a BLDL macroinstruction, most likely because the DBD was not inIMS.DBDLIB.

Important: In a managed ACBs environment, the errortype of the message, DFS4470E is issued, becausethis GSAM PSB is unusable without the DBD existingin the directory. In a catalog-only environment, thewarning type of this message, DFS4470W is issued,because IMS still uses the DBDLIB.


The GSAM DBD that the DFS3PU00 utility couldnot create a record for in the IMS catalog.

System actionNo catalog record was built for DBD dbd-name. Theutility continues inserting other records in the catalogand ends with return code 4.

Programmer responseMake sure that the required DBD library is referencedcorrectly by an IMS DD statement in the JCL forthe DFS3PU00 utility. If the DBD library is correctlyreferenced, make sure that the required DBD member




http://www-01.ibm.com/support/knowledgecenter/SSLTBW_2.4.0/com.ibm.zos.v2r4.ieaa900/load.htm?lang=en

http://www-01.ibm.com/support/knowledgecenter/SSLTBW_2.4.0/com.ibm.zos.v2r4.ieaa900/load.htm?lang=en






has been generated by the DBD Generation utility.After the corrections are complete, rerun the utility.

Module:DFS3PU00


DFS4470E GSAM DBD dbd-name NOT INDBDLIB. BLDL RC = rc. DBD ANDREFERENCING PSBS WERE NOTADDED TO THE CATALOG.

ExplanationTo build the catalog record for the GSAM DBD dbd-name, the IMS Catalog Populate utility (DFS3PU00)tried to read the DBD from the directory (if managedACBs is enabled) or IMS.DBDLIB (if managed ACBs isnot enabled) but encountered return code rc from aBLDL macro instruction, most likely because the DBDwas not in the directory or IMS.DBDLIB.

Important: In a managed ACBs environment, the errortype of the message, DFS4470E is issued, becausethis GSAM PSB is unusable without the DBD existingin the directory. In a catalog-only environment, thewarning type of this message, DFS4470W is issued,because IMS still uses the DBDLIB.


The GSAM DBD that the DFS3PU00 utility couldnot create a record for in the IMS catalog.

System actionIn a managed ACBs environment, the utility ends witha return code 8. In a catalog-only environment, theutility continues inserting other records in the catalogand ends with return code 4.

Programmer responseIn a managed ACBs environment, ensure that the DBDexists in the directory. In a catalog-only environment,make sure that the required DBD library is referencedcorrectly by an IMS DD statement in the JCL forthe DFS3PU00 utility. If the DBD library is correctlyreferenced, ensure that the required DBD member hasbeen generated by the DBD Generation utility. Afterthe corrections are complete, rerun the utility.

Module:DFS3PU00


DFS4471W LOGICAL DBD dbd-name NOT INDBDLIB. BLDL RC =rc. THE DBDAND REFERENCING PSBS WERENOT ADDED TO THE CATALOG.

ExplanationIn order to build the catalog record for the logicalDBD dbd-name, the IMS Catalog Populate utility(DFS3PU00) tried to read the DBD from IMS.DBDLIBbut encountered return code rc from a BLDL macroinstruction, most likely because the DBD was not inIMS.DBDLIB.


The name of the logical DBD that the DFS3PU00utility did not find in any DBD library referenced inthe utility JCL.

rcThe return code received by the DFS3PU00 utilityfrom the z/OS DFSMS BLDL macro instruction.

System actionNo catalog record was built for DBD dbd-name or forany PSB with a PCB that references this database. TheDFS3PU00 utility continues inserting other records inthe catalog and ends with return code 4.

Programmer responseMake sure that the required DBD library is referencedcorrectly by an IMS DD statement in the JCL forthe DFS3PU00 utility. If the DBD library is correctlyreferenced, make sure that the required DBD memberhas been generated by the DBD Generation utility.After the corrections are complete, rerun the utility.

Module:DFS3PU00


DFS4472W ERRORS READING dbd-countGSAM OR LOGICAL DBDS.METADATA FOR PSB psb-nameWAS NOT WRITTEN IN THE IMSCATALOG.











ExplanationIn order to build the catalog record for PSB psb-name, the IMS Catalog Populate utility (DFS3PU00)tried to read one or more GSAM or logical DBDmembers from the IMS.DBDLIB data set becausethese databases were referenced by PCBs in the PSB.The DBD members either could not be read from theIMS.DBDLIB data set or encountered errors in beingconverted into catalog records. The number of DBDmembers errors is shown in the dbd-count position inthis error message.

Error messages issued by the DFS3PU00 utility beforethis error message identify the specific errors of theDBDs members.

In the message text:dbd-count

The number of GSAM or logical DBD members thatcould not be read or that contained errors.

psb-nameThe name of the PSB that the DFS3PU00 utilitycould not create a PSB record for in the IMScatalog.

System actionNo record was built in the IMS catalog for the PSBmember psb-name or for any of the DBDs that couldnot be processed correctly. The DFS3PU00 utilitycontinues inserting other records in the catalog andends with return code 4.

Programmer responseCheck the error messages that were issued by theDFS3PU00 utility before this message. Look for atleast as many preceding error messages as thenumber shown in this error in the dbd-count position.After all errors have been corrected, rerun theDFS3PU00 Catalog Populate utility.

Module:DFS3PU00


DFS4473E DCPL RETURN CODE ret_codeFROM DECODER-BUILDERPROCESSING MEMBER resource-name

ExplanationThe IMS Catalog Populate utility (DFS3PU00) receivedan unrecognized return code in an internal decoder-builder parameter list (DCPL) while processing the

DBD or PSB member resource-name. This is an internalIMS error.

In the message text:ret_code

The unrecognized return code from the DCPL.resource-name

The DBD or PSB member that the DFS3PU00 utilitywas processing when the error was encountered.

System actionThe DFS3PU00 utility continues processing the otherDBD and PSB members and ends with return code 8.

Programmer responseContact IBM Software Support.

Module:DFS3PU00


DFS4475E ERROR ATTACHING DFSRRC00,PROGRAM pgm-name. ATTACH RC=rc.

ExplanationAn MVS ATTACH macro instruction gave returncode of rc when the IMS Catalog Populate utility(DFS3PU00) was attaching an internal instance of anIMS system called pgm-name, where pgm-name iseither DFS3PU01 or DFS3PU03.

In the message text:pgm-name

The name of the program that the DFS3PU00utility was attempting to attach when the erroroccurred.

rcThe return code received by the DFS3PU00 utilityfrom the z/OS MVS ATTACH macro.

System actionThe DFS3PU00 utility ends with return code 16.

Programmer responseLook up the MVS ATTACH macro return code in thez/OS publications. Ensure that the JCL to run theDFS3PU00 utility is correct. If the problem persists,contact IBM Software Support.

Module:






DFS3PU00Related referenceIMS Catalog Populate utility (DFS3PU00)(System Utilities)z/OS: ATTACH and ATTACHX return and reasoncodes

DFS4476E ERROR ATTACHING DFSUPNT0.ATTACH RC = rc.

ExplanationAn MVS ATTACH macro instruction gave return code ofrc when the IMS Catalog Populate utility (DFS3PU00)was attaching an internal instance of an IMS systemto do partition initialization for one of the catalog’spartitions.


The return code received by the DFS3PU00 utilityfrom the z/OS MVS ATTACH macro.


Programmer responseLook up the MVS ATTACH macro return code in thez/OS publications. Ensure that the JCL to run theDFS3PU00 utility is correct. If the problem persists,contact IBM Software Support.

Module:DFS3PU00

Related referenceIMS Catalog Populate utility (DFS3PU00)(System Utilities)z/OS: ATTACH and ATTACHX return and reasoncodes

DFS4477E ABEND cccc COLLECTINGCATALOG STRUCTUREINFORMATION FOR DBD|PSBname

ExplanationThe abend cccc occurred in a subtask of the IMSCatalog Populate utility (DFS3PU00).


The number of the abend that occurred in theDFS3PU00 utility subtask.

nameThe name of the DBD or PSB being processed atthe time of the abend. The text "FOR DBD|PSBname" is not present when the abend cannot beattributed to a specific DBD or PSB name.


Programmer responseLook up the abend in the appropriate documentation.Ensure that the JCL to run the DFS3PU00 utility iscorrect. If the problem persists, contact IBM SoftwareSupport.

Module:DFS3PU00

Related conceptsIMS abend codes (Messages and Codes)Related referenceIMS Catalog Populate utility (DFS3PU00)(System Utilities)

DFS4478E ABEND cccc INSERTING ACATALOG RECORD FOR DBD|PSBname

or

DFS4478E ABEND cccc DUE TO SOME UNKNOWNERROR.

ExplanationThe abend cccc occurred in the subtask of the IMSCatalog Populate utility (DFS3PU00) that inserts orupdates catalog records into the catalog, such asabend U1002.



nameThe name of the DBD or PSB for which an instancewas being inserted at the time of the abend. Thetext "INSERTING A CATALOG RECORD FOR DBD|PSB name" is not present when the abend cannotbe attributed to a specific DBD or PSB name.














Programmer responseLook up the abend in the appropriate documentation.Ensure that the JCL to run the DFS3PU00 utility iscorrect. After you correct the error, run the job again. Ifthe problem persists, contact IBM Software Support.

Module:DFS3PU00

Related conceptsIMS abend codes (Messages and Codes)Related referenceIMS Catalog Populate utility (DFS3PU00)(System Utilities)Related information1002 (Messages and Codes)

DFS4479E ABEND cccc IN PARTITIONINITIALIZATION SUBTASK.

ExplanationThe abend cccc occurred in the subtask of theIMS Catalog Populate utility (DFS3PU00) that doespartition initialization for one of the catalog’spartitions.




Programmer responseLook up the abend in the appropriate documentation.Ensure that the JCL to run the DFS3PU00 utility iscorrect. If the problem persists, contact IBM SoftwareSupport.

Module:DFS3PU00

Related conceptsIMS abend codes (Messages and Codes)Related referenceIMS Catalog Populate utility (DFS3PU00)(System Utilities)

DFS4480E INCORRECT EXECUTIONPARAMETERS PASSED TODFS3PU00.

ExplanationThe IMS Catalog Populate utility (DFS3PU00) wasinvoked with an incorrect JCL EXEC statement. Therewas either an incorrect name in the PGM parameter orincorrect information in the PARM parameter.


Programmer responseCorrect the JCL and rerun the DFS3PU00 utility. ThePGM parameter on the EXEC statement must specifyDFS3PU00, not DFSRRC00. The PARM parameter mustspecify:

• A region type of DLI, DBB, or BMP• A PSB name of DFSCPL00, DFSCP001, or DFSCP000• A program name of DFS3PU00

For example:

EXEC PGM=DFS3PU00,PARM=(DLI,DFS3PU00,DFSCPL00,,,,,,,,,,,Y,N,,,,,,,,,,,,'DFSDF=001')

Module:DFS3PU00


DFS4481E UNEXPECTED STATUS CODEstatus-code ON PARTITIONINITIALIZATION OF CATALOGDATABASE catalog-dbd.

ExplanationThe IMS Catalog Populate utility (DFS3PU00) receivedan unexpected PCB status code after issuing a DL/Icall to initialize a partition in the IMS catalog database.The status code could indicate one of the followingerrors:

• An IMS error• A structural error in one of the DBDs that define the

IMS catalog or in one of the PSB provide access tothe IMS catalog

• Unsupported manipulation of the contents of theIMS catalog

In the message text:catalog-dbd

The name of the IMS catalog database thatcontains the partition that the DFS3PU00 utility











was attempting to initialize when the status codewas received.

status-codeThe name of the logical DBD that the DFS3PU00utility did not find in any DBD library referenced inthe utility JCL.


Programmer responseEnsure that the IMS catalog DBDs, DFSCD000and DFSCX000, were installed correctly in yourIMS.DBDLIB and that the IMS catalog PSBs,DFSCP000, DFSCP001, and DFSCPL00, were installedcorrectly in your IMS.PSBLIB. If the problem persists,contact IBM Software Support.

Module:DFS3PU00

Related referenceIMS Catalog Populate utility (DFS3PU00)(System Utilities)About DL/I status codes (Messages and Codes)

DFS4482E THE PSB USED TO INVOKE THEDFS3PU00 UTILITY REFERS TO ACATALOG WITH AN UNEXPECTEDSTRUCTURE.

ExplanationThe IMS Catalog Populate utility (DFS3PU00)encountered an inconsistency between its internallogic and the IMS catalog DBD that is referenced bythe PSB specified on the PARM parameter in the EXECstatement of the DFS3PU00 utility JCL. For example,the DBD might not have the expected segment names,number of segments, or number of secondary indexes.

System actionThe DFS3PU00 utility did not update the catalog andends with return code 20.

Programmer responseEnsure that the IMS catalog DBDs, DFSCD000and DFSCX000, were installed correctly in yourIMS.DBDLIB and that the IMS catalog PSBs,DFSCP000, DFSCP001, and DFSCPL00, were installedcorrectly in your IMS.PSBLIB.

Confirm that the JCL for the DFS3PU00 utility iscorrectly coded. The JCL must specify one of theIMS catalog PSBs and must refer to the IMS.DBDLIB,

IMS.PSBLIB, and IMS.ACBLIB data sets that containthe DBDs and PSBs of the IMS catalog itself. If theproblem persists, contact IBM Software Support.

Module:DFS3PU00


DFS4483E CATALOG DATA SET CREATIONOR VALIDATION FAILED FOR THEDATA SET WITH DDNAME catalog-dbds

ExplanationThe IMS Catalog Populate utility (DFS3PU00)attempted to create the database data sets for the IMScatalog, but encountered one of the following errors:

• Data set creation failed for the database data setidentified by the ddname in the error message

• An IMS catalog database data set with the ddnameshown in the error message already exists, but itscharacteristics do not meet the new requirementsfor the data set

The job output has one or more messages describingthe exact problem.

In the message text:catalog-dbds

The ddname of the database data set that couldnot be created or validated for the IMS catalog.

System actionThe DFS3PU00 utility did not load the catalog andends with return code 12.

Programmer responseCheck the messages in the job output and make thenecessary corrections.

Module:DFS3PU00


DFS4484E THERE WAS NO VOLUME SERIALNUMBER TO CREATE THE DATASET WITH DDNAME catalog-dbds




http://www.ibm.com/support/knowledgecenter/SSEPH2_15.1.0/com.ibm.ims15.doc.msgs/compcodes/ims_dlistatuscodestables.htm#ims_dlistatuscodestables





ExplanationThe IMS Catalog Populate utility (DFS3PU00)attempted to create the IMS catalog database dataset identified by the ddname shown in the errormessage. Because the data set is a non-SMS managedVSAM key-sequenced data set (KSDS), a volume serialnumber is required, but none was specified.

In the message text:catalog-dbds

The ddname of the database data set that couldnot be created by the DFS3PU00 utility.

System actionThe DFS3PU00 utility did not load the catalog andends with return code 12.

Programmer responseCode a volume serial number on the IXVOLSERparameter in the catalog section of the applicableDFSDFxxx member of the IMS.PROCLIB data set or setthe IXVOLSER in the IMS Catalog Definition user exitroutine (DFS3CDX0). The IXVOLSER parameter definesa single volume serial number that the DFS3PU00utility uses to create all of the following VSAM KSDSsof the IMS catalog database:

• The indirect list data set (ILDS)• The primary index data set• The secondary index data set

For greater control over the placement of the IMScatalog database data sets, to do such things asspread the data sets across different volumes, you cancreate the data sets yourself. To estimate the spacerequirements of the IMS catalog data sets, you can runthe DFS3PU00 utility in analysis-only mode.

Another option is to specify that the data set beSMS-managed. In this case, instead of providing avolume serial number, code the SMS storage class,data class, and management class parameters in theDFSDFxxx PROCLIB member or in the DFS3CDX0 userexit routine.

Module:DFS3PU00

Related referenceIMS Catalog Populate utility (DFS3PU00)(System Utilities)DFSDFxxx member of the IMS PROCLIB dataset (System Definition)IMS Catalog Definition exit routine (DFS3CDX0)(Exit Routines)

DFS4485E THE CATALOG WAS NOT ENABLED.

ExplanationThe IMS catalog is not enabled in this IMS system.

System actionThe IMS Catalog Populate utility (DFS3PU00) endswith return code 20.

Programmer responseEnable the IMS catalog in one of the following ways:

• For an online IMS system, in the IMS catalog sectionof the DFSDFxxx member of the IMS.PROCLIB dataset.

• For a DLI or DBB batch job, in the IMS catalogsection of the DFSDFxxx member that is specifiedon the PARM parameter of the EXEC statement in theDFS3PU00 utility JCL.

• For a DLI or DBB batch job, in the IMS CatalogDefinition user exit routine (DFS3CDX0) that yourinstallation has installed in the IMS.SDFSRESL dataset.

Module:DFS3PU00


DFS4486E THERE IS NO CATALOG PARTITIONFOR THE RECORD WITH ROOT KEY"root-key".

ExplanationWhile analyzing the input ACB libraries prior toupdating or loading the IMS catalog, the IMS CatalogPopulate utility (DFS3PU00) found a DBD or PSBmember that requires a record key that is higher thanthe highest high key of any partition in the IMS catalog.Based on the current partition definitions, the IMScatalog cannot contain the record identified in theerror message.

In the message text:root-key

The key of the root segment that is higher than thehighest high key that is defined for any partition inthe IMS catalog.

System actionThe DFS3PU00 utility ends abnormally with abendcode U1002-0C.










Programmer responseCorrect the definition of the partitions of the IMScatalog, such that the highest partition high key canaccommodate the highest possible root key of thecatalog record required for any DBD or PSB member.

The root keys of IMS catalog records consist of an8-character string beginning with "DBD" or "PSB"followed by the 8-character DBD or PSB name. For thelast or only partition there must be a high-key valuehigh enough to include all of your possible PSB names.

Module:DFS3PU00

Related tasksChanging the high key of a partition (DatabaseAdministration)Related referenceIMS Catalog Populate utility (DFS3PU00)(System Utilities)

DFS4487E THERE IS A PARTITIONSELECTION EXIT FOR THECATALOG, BUT THIS IS NOTALLOWED.

ExplanationThe IMS Catalog Populate utility (DFS3PU00) foundthat a HALDB Partition Selection exit routine isspecified in the HALDB master database definition ofthe IMS catalog database. The IMS catalog does notsupport HALDB Partition Selection exit routines.

System actionThe Catalog Populate utility ends with return code 20.

Programmer responseChange the HALDB master database definition tospecify key-range partition selection instead of aPartition Selection exit routine. You can use the DBRCcommand CHANGE.DB.

When you define the high-key value of the last or onlypartition in the IMS catalog, the value must be highenough to include all possible PSB names. The rootkeys in the catalog consist of an eight-character stringbeginning with "DBD" or "PSB", followed by an eight-character member name.

Module:DFS3PU00


DFS4488W THE FORMAT OF THE DBD OR PSBMEMBER member-name IS NOTRECOGNIZED.

ExplanationThe format of the member identified in the member-name position of the error message is inconsistentwith the expected format.

Possible causes for receiving this message include:

• DBD or PSB members use an obsolete format.• Members in the target data set are not DBD or PSB

members.• The number of GSAM PCBs exceeds 255.

System actionThe IMS Catalog Populate utility (DFS3PU00) does notcreate a record in the IMS catalog for the memberidentified in the error message. The DFS3PU00 utilitycontinues inserting other records in the IMS catalogand ends with return code 4.

Programmer responseVerify that the IMS DD statement references thecorrect IMS.DBDLIB and IMS.PSBLIB data set. Verifythat the IMSACBnn DD statement references thecorrect IMS.ACBLIB data set. If necessary, rerun theDFS3PU00 utility after the error is corrected.

If the problem persists, contact IBM Software Support.

Module:DFS3PDBD, DFS3PPSB, DFS3PU00


DFS4489W AN ACB MEMBER CONTAINSINCOMPLETE INFORMATION FORA VIRTUALLY PAIRED SEGMENT:DBD=dbd-name

ExplanationWhile processing an ACB library, the IMS CatalogPopulate utility (DFS3PU00) encountered a DBD thatcontains incomplete information about a virtuallypaired segment. The DBD is identified in the errormessage.

The DBD in the ACB library is incomplete because theACB member was built by an IMS system that does notsupport the IMS catalog.


http://www.ibm.com/support/knowledgecenter/SSEPH2_15.1.0/com.ibm.ims15.doc.dag/ims_changehighkey.htm#ims_changehighkey

http://www.ibm.com/support/knowledgecenter/SSEPH2_15.1.0/com.ibm.ims15.doc.dag/ims_changehighkey.htm#ims_changehighkey







System actionThe DFS3PU00 utility does not create a record inthe IMS catalog for the DBD identified in the errormessage. The DFS3PU00 utility continues insertingother records in the IMS catalog and ends with returncode 4.

Programmer responseRebuild the ACB member for the DBD that is identifiedin the error message by running an ACB generationutility with the following utility control statementspecified:

BUILD DBD=(dbd-name),BLDPSB=NO

After the ACB member is rebuilt, rerun the DFS3PU00utility.

Module:DFS3DBD0, DFS3PU00

Related referenceIMS Catalog Populate utility (DFS3PU00)(System Utilities)Application Control Blocks Maintenance utility(System Utilities)

DFS4490W AN ACB MEMBER CONTAINSAN INCOMPLETE REFERENCE TOA SECONDARY INDEX: PSB=psb-name

ExplanationWhile processing an ACB library, the IMS CatalogPopulate utility (DFS3PU00) found a PSB that hasincomplete information about a reference to asecondary index. The PSB is identified in the errormessage.

The PSB in the ACB library is incomplete because itwas built by an IMS system that does not support theIMS catalog.

System actionThe DFS3PU00 utility does not create a record inthe IMS catalog for the PSB identified in the errormessage. The DFS3PU00 utility continues insertingother records in the catalog and ends with return code4.

Programmer responseRebuild the ACB member for the PSB that is identifiedin the error message by running the ACB Maintenanceutility with the following utility control statementspecified:

BUILD PSB=psb-name

After the ACB member is rebuilt, rerun the DFS3PU00utility.

Module:DFS3PCTL, DFS3PU00

Related referenceIMS Catalog Populate utility (DFS3PU00)(System Utilities)Application Control Blocks Maintenance utility(System Utilities)

DFS4491W AN INVALID DBD NAME WASFOUND IN MEMBER member-name

ExplanationWithin the DBD or PSB identified in the error message,the IMS Catalog Populate utility (DFS3PU00) found areferenced DBD name that did not follow the namingrequirements for a DBD. This error is probably an IMSsoftware error.

System actionNo catalog record was built for member. TheDFS3PU00 utility continues inserting other records inthe catalog and ends with return code 4.

Programmer responseRerun the DFS3PU00 utility with a DD statement thathas ddname IMS and that refers to your IMS.DBDLIBor IMS.PSBLIB containing the invalid DBD name. If theproblem persists, contact IBM Software Support.

Module:DFS3DBD0, DFS3DEDB, DFS3GSAM, DFS3INDX,DFS3LOG0, DFS3MSDB, DFS3SDBD, DFS3PU00


DFS4492W AN INVALID SEGMENT NAME WASFOUND IN MEMBER member-name

ExplanationWithin the DBD or PSB identified in the error message,the IMS Catalog Populate utility (DFS3PU00) founda segment name that did not follow the namingrequirements for a segment. This error is probably anIMS software error.




http://www.ibm.com/support/knowledgecenter/SSEPH2_15.1.0/com.ibm.ims15.doc.sur/ims_acbgen.htm#ims_acbgen








System actionNo catalog record was built for member. TheDFS3PU00 utility continues inserting other records inthe catalog and ends with return code 4.

Programmer responseRerun the DFS3PU00 utility with a DD statement thathas ddname IMS and that refers to your IMS.DBDLIBor IMS.PSBLIB containing the member. If the problempersists, contact IBM Software Support.

Module:DFS3DBD0, DFS3INDX, DFS3PU00


DFS4493W AN INTERNAL ERROR OCCURREDBUILDING CATALOG SEGMENTSFOR member-name

ExplanationThe IMS Catalog Populate utility (DFS3PU00)encountered an internal error building a catalog recordfor the member identified in the error message.

System actionNo catalog record was built for the member. TheDFS3PU00 utility continues inserting other records inthe catalog and ends with return code 4.

Programmer responseEnsure that your JCL to run the DFS3PU00 utility iscorrect. If the problem persists, contact IBM SoftwareSupport.

Module:DFS3DDB0, DFS3DPB0, DFS3PU00


DFS4494E member-name IS A BACK-LEVELACBLIB MEMBER.

ExplanationThe IMS Catalog Populate utility (DFS3PU00)encountered an ACB library member that wasgenerated by an IMS system that does not support theIMS catalog.

System actionNo catalog record was built for the member. The utilitycontinues to insert other records in the catalog andends with return code 4.

Programmer responseEnsure that your JCL to run the DFS3PU00 utilityrefers to ACB libraries that were generated by aversion of IMS that supports the IMS catalog. If theproblem persists, contact IBM Software Support.

Module:DFS3DDB0, DFS3DPB0, DFS3PU00


DFS4495E THE CATALOG IMPORT DATA SETFAILED TO OPEN. OPEN RC = rc.

ExplanationIn opening the catalog import data set referred toby the CCUCATIM DD statement, the IMS CatalogPopulate utility (DFS3PU00) encountered return coderc from an OPEN macro instruction.




Programmer responseEnsure that the CCUCATIM DD statement refers to acatalog import data set.

Module:DFS3PU00

Related referenceIMS Catalog Copy utilities (DFS3CCE0,DFS3CCI0) (System Utilities)z/OS: OPEN return codes

DFS4496E THE CATALOG IMPORT DATA SETDOES NOT CONTAIN CATALOGRECORDS.








http://www.ibm.com/support/knowledgecenter/SSEPH2_15.1.0/com.ibm.ims15.doc.sur/ims_catalog_copy_utility.htm#ims_catalog_copy_utility



ExplanationThe import function of the IMS Catalog Copy utility didnot find any catalog records in the catalog import dataset referred to by the CCUCATIM DD statement.

System actionThe utility ends with return code 8. The catalog is notupdated.

Programmer responseVerify that the export function of the IMS CatalogCopy utility successfully copied the catalog records tothe export data set referred to by the CCUCATEX DDstatement.

Verify that the export data set created by the exportfunction of the IMS Catalog Copy utility is the data setthat is now referenced by the CCUCATIM DD statementin the JCL for the import function of the IMS CatalogCopy utility.

Module:DFS3PU00

Related referenceIMS Catalog Copy utilities (DFS3CCE0,DFS3CCI0) (System Utilities)

DFS4497E DBD MEMBER dbd_name USESISAM, WHICH IS NOT ASUPPORTED ACCESS METHOD.

ExplanationThe IMS Catalog Populate utility (DFS3PU00)encountered a DBD member for a database that usesthe ISAM access type. IMS does not support the ISAMaccess type.

System actionThe DFS3PU00 utility does not create a record inthe IMS catalog for the DBD member. The DFS3PU00utility continues inserting other records in the IMScatalog and ends with return code 4.

Programmer responseNo action is necessary; however, no metadata aboutthe ISAM database is stored in the IMS catalog. If theISAM database is no longer used by your installation,consider removing the input statements for the ISAMdatabase from the input to the DBD Generation utilityso that the next time you rebuild the DBD and ACBlibraries, you do not receive this message.

Module:

DFS3DDB0, DFS3DPB0, DFS3PU00Related referenceIMS Catalog Populate utility (DFS3PU00)(System Utilities)

DFS4498W AN ACB MEMBER CONTAINS AREFERENCE TO A DBD THATIS NOT FOUND IN ACBLIB:MBR=mbrname

ExplanationAn ACB member references one or more DBDmembers that are missing from the ACB library.The IMS Catalog Populate utility (DFS3PU00) cannotcreate a record for the ACB member in the IMScatalog.

System actionThe DFS3PU00 utility does not create a record in theIMS catalog for the ACB member identified in the errormessage. The DFS3PU00 utility continues insertingother records in the catalog and ends with return code4.

Programmer responseRun the ACB Maintenance utility to rebuild any missingmembers in the ACB library. After the ACB membersare rebuilt, rerun the DFS3PU00 utility.

Module:DFS3PU00

Related referenceIMS Catalog Copy utilities (DFS3CCE0,DFS3CCI0) (System Utilities)

DFS4499E ERROR IN CALL TO DFS3DATEcause

ExplanationThe IMS Catalog Populate utility (DFS3PU00)encountered an internal error while calling moduleDFS3DATE. DFS3DATE converts ACB membertimestamps into the timestamp format that is used inthe IMS catalog records.

In the message text:cause

The cause of the error. Possible causes include:LESS THAN 3 PARMS SPECIFIED

The parameter list that the calling modulepassed to module DFS3DATE was missing oneor more of the following required elements:

• A status code area








• A function code• A timestamp area

TOO MANY PARMS SPECIFIEDThe parameter list that the calling modulepassed to module DFS3DATE contained morethan five parameters.

UNKNOWN FUNCTION CODEThe calling module specified an invalidfunction code to module DFS3DATE.

INSUFFICENT PARMS FOR FUNCTIONThe calling module did not supply all therequired parameters to module DFS3DATE forthe specified function code.

INVALID DATE SPECIFIED IN CALLThe calling module provided an invalid dateformat to module DFS3DATE.

ERROR IN ROUTINE DT03Module DFS3DATE unexpectedly failed inroutine DT03 while attempting to validate auser-supplied timestamp.

System actionThe DFS3PU00 utility terminates abnormally withreturn code 16 and issues an ABENDU1002 fordiagnostic purposes.

Programmer responseCapture a memory dump of the DFS3PU00 job andcontact IBM Software Support.

Module:

DFS3DATE, DFS3PU00Related referenceIMS Catalog Populate utility (DFS3PU00)(System Utilities)

DFS4500E THE MAXIMUM NUMBER OFERROR MESSAGES SPECIFIED BYTHE ERRORMAX OPTION HASBEEN EXCEEDED.

ExplanationThe ERRORMAX=n option was present in the controlstatement data set, and the IMS Catalog Populateutility encountered more than n occurrences ofproblems that suppressed writing DBD and PSBmetadata in the IMS catalog.

System action:The IMS Catalog Populate utility terminated withreturn code 8.

Programmer responseTo increase the allowed number of diagnosticmessages, increase the value for the ERRORMAXoption in the control statement data set. Otherwise,correct the problems reported by the previousmessages.

Module:DFS3PU00









DFS4503A INVALID IMSID ON SYSINRECORD

Explanation:An IMSID specified in a SYSIN record is invalid. TheIMSID must start in column 1, be 1-4 characters inlength, contain alphanumeric characters, and containblanks in the rest of the record.

System action:The Global Online Change Utility fails.

Operator response:Correct the IMSID and run the DFSUOLC0 utility again.

Module:DFSUOLC0

DFS4504A INVALID PARAMETER xxxx=yyyy

ExplanationGlobal Online Change utility (DFSUOLC0) encounteredan error in the input parameter.


xxxxThe keyword for which the parameter is invalid. Itcan be one of the following:

FUNCACBSMDBSFMTSMDIDPLEXVERS

yyyyThe parameter.

System action:The system does not perform any validity checking onthe SYSIN records as the input parameters are notvalid. The DFSUOLC0 utility terminates with a returncode of 4.

User response:Correct the error parameter and retry the utilityfunction.

Module:DFSUOLC0

DFS4505A DUPLICATE IMSID ON SYSINRECORD

Explanation:You specified an IMSID more than once in the SYSINrecords. You can specify a particular IMSID only oncein a SYSIN record. Multiple IMSIDs are supportedin the SYSIN records, but they must all be differentnames.

System action:The global online change utility DFSUOLC0 fails.

Operator response:Delete the duplicate IMSID or correct the name. Thenrun the DFSUOLC0 utility again.

Module:DFSUOLC0

DFS4506A OLC IN PROGRESS. CANNOTACCESS OLCSTAT

Explanation:The Global Online Change utility (DFSUOLC0) failed toinitialize the OLCSTAT dataset because a global onlinechange is in progress. Global online change locks theOLCSTAT data set so that nothing else can update itwhile it is being changed.

System action:The Global Online Change Utility fails.

Operator response:Wait for the global online change to complete orterminate the global online change, before running theGlobal Online Change utility.

Module:DFSUOLC0

DFS4507A SYSPRINT OPEN FAILED

Explanation:The Global Online Change utility (DFSUOLC0)encountered an error in opening the OLCSTAT data set.

System action:The DFSUOLC0 utility terminates with a return code of4.

User response:This problem is likely the result of a JCL error. Checkthat your DD statements for the data set are definedcorrectly. Correct the problem and rerun the utility.

Module:DFSUOLC0

DFS4508A FUNC=UNL, NO LOCK HELD

Explanation:


The Global Online Change utility (DFSUOLC0) could notunlock the OLCSTAT data set because the data set isnot locked with the lock word OLCINP.


User responseThe UNLOCK function is not required because theOLCSTAT data set is not locked. An online changein progress might have completed and unlocked theOLCSTAT data set.

You should continue processing with the nextDFSUOLC0 action that you want to take.

Module:DFSUOLC0

DFS4509A FUNC=ADD, IMSID ALREADY INOLCSTAT, SYSIN RECORD

Explanation:The Global Online Change utility (DFSUOLC0)encountered an error while adding an IMSID to theOLCSTAT data set, because the ID already exists in theOLCSTAT.


User response:The IMSID that you are trying to add is already in theOLCSTAT. Correct the IMSID to be added by changingto an IMSID not in the OLCSTAT data set, and retry theADD function.

Module:DFSUOLC0

DFS4510A FUNC=DEL, IMSID NOT INOLCSTAT, SYSIN RECORD

Explanation:The Global Online Change utility (DFSUOLC0)encountered an error in deleting the IMSID you hadspecified from the OLCSTAT data set because the IDdoes not exist in the OLCSTAT.


User response:The IMSID that you are trying to delete is not inthe OLCSTAT. Change the IMSID to be deleted to anIMSID that is in the OLCSTAT data set, and try the DELfunction again.

Module:DFSUOLC0

DFS4511A SYSIN RECORD COUNT EXCEEDSMAX OF nn

Explanation:The count of IMSIDs specified as SYSIN recordsexceeded the maximum supported value of nn.


Operator response:Remove the excess IMSIDs and run the DFSUOLC0utility again.

Module:DFSUOLC0

DFS4512A NO SYSIN RECORDS FORFUNC=xxx

ExplanationThe Global Online Change utility (DFSUOLC0)encountered an error because it did not find any SYSINrecords for xxx.

In the message text, xxx can be:

ADDDEL


User response:Modify the JCL to add the SYSIN record with the IMSIDthat you want to add or delete, and try the utilityfunction again.

Module:DFSUOLC0

DFS4513A FUNC=ADD, ADDING SYSINIMSIDS TO OLCSTAT nn

Explanation:The Global Online Change utility was attempting toadd IMSIDs to the OLCSTAT data set with FUNC=ADD;the IMSIDs were specified in the SYSIN records.However, the count of IMSIDs already defined inthe OLCSTAT data set plus the IMSIDs to be addedexceeds the maximum supported value of nn.


Operator response:Remove the excess IMSIDs and run the DFSUOLC0utility again.

Module:DFSUOLC0

DFS4514A MISMATCH IN UTILITY ANDMACRO VERSION# DETECTED


Explanation:An attempt was made to initialize the OLCSTAT dataset with the Global Online Change utility (DFSUOLC0).The system detected a mismatch between the utilityand the DFSOLCS parmlist versions.

System action:The Global Online Change utility fails with return code04.

User response:This problem is an IMS internal error. Apply correctivemaintenance so that the levels for the utility and theDFSOLCS macro match.

Module:DFSUOLC0

DFS4515W THE GLOBAL OTMA TPIPE COUNTHAS REACHED THE 80% OF THEGLOBAL LIMIT OF nnnnnn.

ExplanationOTMA detected that the total number of transactionpipes (tpipes) has reached or exceeded the 80% of themonitoring point indicated by nnnnnn.


nnnnnnThe global TPIPE warning threshold. This numberis the MAXTP value that is specified for DFSOTMAin the OTMA client descriptor.


System programmer response:Start monitoring the number of tpipes for all themembers. Issue a checkpoint three times to clean theidle tpipes.

Module:DFSYFD00

DFS4516E THE GLOBAL OTMA TPIPE COUNTHAS REACHED THE GLOBAL LIMITOF nnnnnn.

ExplanationThe MAXTP limit is specified for the DFSOTMAdescriptor entry in the OTMA client descriptor tomonitor the growth of TPIPE for all of the OTMAclients. When the number of TPIPEs in use hasreached this limit, IMS issues this error.


nnnnnnThe global TPIPE warning threshold, which is theMAXTP limit specified for DFSOTMA in the OTMAclient descriptor.

System action:IMS rejects any subsequent TPIPE creation requestsfrom OTMA clients and IMS applications. The /DISPLAY OTMA command will display MAX TPIPE forthe USER-STATUS of the OTMA server.

Programmer response:Issue the /DISPLAY OTMA command to view theTPCNT value, which is the total TPIPEs in use, andthe MAXTP value, which is the TPIPE limit specifiedin the OTMA client descriptor. You can issue the IMS /CHECKPOINT command three times to force the tpipecleanup so that idle tpipes in the system can bedeleted.

Module:DFSYFD00

DFS4517I THE GLOBAL OTMA TPIPE COUNTHAS DECREASED BELOW xx% OFTHE GLOBAL LIMIT OF nnnnnn.

ExplanationOTMA detected that the total number of transactionpipes (tpipes) for all the OTMA members has fallenbelow xx% of the monitoring point indicated by theMAXTP value of the DFSOTMA descriptor entry.


xxThe relief level, which is specified through theMAXTP parameter for DFSOTMA in the OTMA clientdescriptor.

nnnnnnThe global TPIPE warning threshold, which is theMAXTP limit specified in the DFSOTMA member ofthe OTMA client descriptor.



Module:DFSYFD00

DFS4518I UPDATES TO THE IMS CATALOGHAVE BEEN COMMITTED.CHECKPOINT ID nnnnnnn

ExplanationThe IMS Catalog Record Purge utility (DFS3PU10)issued a CHKP (checkpoint) call to commit the priorupdates to the IMS catalog. This call occurs after every200 updates.



nnnnnnnIndicates the checkpoint ID.



The checkpoint frequency of 200 updates may bechanged by specifying the RESOURCE_CHKP_FREQparameter for the utility.

Module:DFS3PU10

DFS4519E BOTH THE LOAD PSBDFSCPL00 AND THE STATEMENTMANAGEDACBS=UPDATE ORMANAGEDACBS=STAGE ARESPECIFIED.

ExplanationWhen the load PSB DFSCPL00 is specified in theEXEC parameters in the utility JCL neither UPDATE norSTAGE can be specified on the MANAGEDACBS utilitycontrol statement.

System actionThe IMS Catalog Populate utility terminates withreturn code 8.

System programmer responseEither change the PSB in the EXEC parameters orchange the value of the MANAGEDACBS utility controlstatement to SETUP.

Module:DFS3DU10


DFS4520I INSTANCE yydddhhmmssth OFDBD|PSB name WAS ADDED TOTHE IMS DIRECTORY.

ExplanationThe IMS ACBLIB member name with timestampyydddhhmmssth was copied from the ACBLIB to theIMS catalog directory.


The ACLIB member name.

yydddhhmmssthThe timestamp of the ACBLIB member.

System actionExecution of the IMS Catalog Populate utilitycontinues.


You can suppress this and other similar informationalmessages by specifying NOISRTLIST in the inputcontrol statements for the IMS Catalog Populate utilityin a data set referenced by the ddname SYSINP.

Module:DFS3DU10


DFS4521I INSTANCE acb-yydddhhmmssthOF DBD|PSB name REPLACEDINSTANCE dir-yydddhhmmssth INTHE IMS CATALOG DIRECTORY.

ExplanationThe IMS catalog directory already containedan existing member name with timestamp dir-yydddhhmmssth. This member was deleted, andthe ACBLIB member name with timestamp acb-yydddhhmmssth was successfully copied from theACBLIB to the IMS catalog directory to replace it.


The ACBLIB member name.acb-dddhhmmssth

The timestamp of the ACBLIB member that wasadded to the IMS catalog directory.

dir-yyddhhmmssthThe timestamp of the ACBLIB member that wasalready in the IMS catalog directory.



You can suppress this and other similar informationalmessages by specifying NOISRTLIST in the input






control statements for the IMS Catalog Populate utilityin a data set referenced by the ddname SYSINP.

Module:DFS3DU10


DFS4522I INSTANCE acb-yydddhhmmssthOF DBD|PSB name WAS NOTADDED TO THE DIRECTORY.A LATER INSTANCE dir-yydddhhmmssth EXISTS

ExplanationThe IMS catalog directory already contains existingan existing member name with timestamp dir-yydddhhmmssth. This member was retained in thedirectory because the timestamp acb-yydddhhmmssthfor ACBLIB member name is earlier than thetimestamp of the member already in the directory.


The member name in the directory and in theACBLIB.

acb-dddhhmmssthThe timestamp of the ACBLIB member that wasrejected for inclusion in the directory.

dir-yyddhhmmssthThe timestamp of the ACBLIB member that isalready in the IMS catalog directory.



For ACBLIB members with earlier timestampswho want to replace their corresponding directorymembers with later timestamps, provide theMANAGEDACBS=(UPDATE,ACBLIB) parameter in thecontrol statements data set (ddname SYSINP) as inputto the IMS Catalog Populate utility.

To suppress this and other similar informationalmessages, specify NODUPLIST in the input controlstatements for the IMS Catalog Populate utility in adata set that is referenced by the ddname SYSINP.

Module:DFS3DU10


DFS4523E AN I/O ERROR OCCURREDREADING ACBLIB INSTANCEyydddhhmmssth OF DBD|PSBname system-produced-SYNAD-message-text

ExplanationThe IMS Catalog Populate utility tried to read membername from the ACBLIB in order to copy it to theIMS directory. However, the internal BPAM macroinstructions that the utility used detected an I/O error.


The ACLIB member name.yydddhhmmssth

The timestamp of the ACBLIB member.system-produced-SYNAD-message-text

The I/O error message produced by DFSMS.

System actionThe member name was not added to the IMSdirectory, and execution of the IMS Catalog Populateutility terminated with return code 8.

System programmer responseFor an explanation of system-produced-SYNAD-message-text refer to the description of the SYNADAFmacro in z/OS DFSMS Macro Instructions for DataSets, and take any actions suggested.

Module:DFS3DU10

Related referenceIMS Catalog Populate utility (DFS3PU00)(System Utilities)z/OS: DFSMS SYNADAF macro

DFS4524E AN I/O ERROROCCURRED WRITING INSTANCEyydddhhmmssth OF DBD|PSBname system-produced-SYNAD-message-text

ExplanationThe IMS Catalog Populate utility tried to write membername to the IMS directory. However, the internal BPAMmacro instructions that the utility used detected anI/O error.








http://www.ibm.com/support/knowledgecenter/SSLTBW_2.3.0/com.ibm.zos.v2r3.idad500/syndf.htm



The timestamp of the ACBLIB member.system-produced-SYNAD-message-text

The I/O error message produced by DFSMS.


System programmer responseFor an explanation of the system-produced-SYNAD-message-text that was issued by DFSMS, refer to thedescription of the SYNADAF macro in z/OS DFSMSMacro Instructions for Data Sets, and take any actionssuggested.

Module:DFS3DU10


DFS4525E ADDING THE MEMBER DBD|PSBname IN IMS DIRECTORY DATASET nn FAILED WITH STOWRETURN CODE rc REASON CODE rs

ExplanationThe IMS Catalog Populate utility tried to write membername to one of the IMS directory data sets. However,the internal STOW macro instruction that the utilityused detected an error.


The ACLIB member name.nn

The data set position in the concatenation of datasets comprising the IMS directory.

rcThe return code given by the STOW macroinstruction.

rsThe reason code given by the STOW macroinstruction.

rscThe return code given by the STOW macroinstruction.


System programmer responseFor an explanation of the return and reason codesrefer to the description of the completion codes ofthe STOW macro in z/OS DFSMS Macro Instructions forData Sets. Take the appropriate actions to remedy theproblem.

Module:DFS3DU10

Related referenceIMS Catalog Populate utility (DFS3PU00)(System Utilities)z/OS: Return and reason codes for the DFSMSSTOW macro

DFS4526E THE IMS DIRECTORY DATA SET nnFAILED TO OPEN. OPEN RC =rc

ExplanationAs part of building the IMS directory the IMSCatalog Populate utility tried to open one of the IMSdirectory data sets. However, the internal OPEN macroinstruction that the utility used detected an error.



rcThe return code given by the OPEN macroinstruction.

System actionThe IMS directory was not built, and execution of theIMS Catalog Populate utility terminated with returncode 8.

System programmer responseFor an explanation of the return codes of thenon-VSAM OPEN macro, see z/OS DFSMS MacroInstructions for Data Sets. Take the appropriate actionsto remedy the problem.

Module:DFS3DU10











z/OS: Return codes for the DFSMS non-VSAMOPEN macro

DFS4527E THE IMS DIRECTORY BOOTSTRAPDATA SET FAILED TO OPEN. OPENRC =rc

ExplanationAs part of building the IMS directory the IMS CatalogPopulate utility tried to open the bootstrap data set forthe IMS directory. However, the internal OPEN macroinstruction that the utility used detected an error.


The return code given by the OPEN macroinstruction.

System actionThe IMS directory was not built, and the IMS CatalogPopulate utility terminated with return code 8.


Module:DFS3DU10

Related referenceIMS Catalog Populate utility (DFS3PU00)(System Utilities)z/OS: Return codes for the DFSMS non-VSAMOPEN macro

DFS4529E DELETING MEMBER DBD|PSBname FROM IMS DIRECTORY DATASET nn FAILED WITH STOWRETURN CODE rc REASON CODE rs

ExplanationThe IMS Catalog Populate utility tried to deletethe existing member name from one of the IMSdirectory data sets. However, the internal STOW macroinstruction that the utility used detected an error.





rsThe return code given by the STOW macroinstruction.

System actionThe member name was not added to the IMSdirectory. The execution of the IMS Catalog Populateutility terminates with return code 8.


Module:DFS3DU10


DFS4530E RENAMING MEMBER DBD|PSBname IN IMS DIRECTORY DATASET nn FAILED WITH STOWRETURN CODE rc REASON CODE rs

ExplanationThe IMS Catalog Populate utility tried to rename anencrypted form of member name in one of the IMSdirectory data sets to the true name. However, theinternal STOW macro instruction that the utility useddetected an error.







http://www-01.ibm.com/support/knowledgecenter/SSLTBW_2.3.0/com.ibm.zos.v2r3.idad500/x1b.htm










System actionThe member name was not added to the IMSdirectory. The execution of the IMS Catalog Populateutility terminates with return code 8.


Module:DFS3DU10


DFS4531I INSTANCE yydddhhmmssth OFDBD|PSB name IS ALREADY INTHE IMS CATALOG DIRECTORYAND WAS NOT ADDED.

ExplanationThe IMS catalog directory already containsexisting an existing member name with timestampyydddhhmmssth, so this member was not added to orreplaced in the directory.


The member name in the directory and in theACBLIB.

yydddhhmmssthThe timestamp of the ACBLIB member that wasrejected for inclusion in the directory.




Module:DFS3DU10


DFS4532E THE IMS CATALOG DIRECTORYDATA SET nn FAILED TO CLOSE.CLOSE RC =rc

ExplanationNear the completion of processing IMS directory theIMS Catalog Populate utility tried to close one of theIMS directory data sets. However, the internal CLOSEmacro instruction that the utility used detected anerror.



rcThe return code given by the CLOSE macroinstruction.

System actionExecution of the IMS Catalog Populate utilityterminated with return code 8.

System programmer responseFor an explanation of the return codes of thenon-VSAM CLOSE macro, see z/OS DFSMS MacroInstructions for Data Sets. Take the appropriate actionsto remedy the problem.

Module:DFS3DU10

Related referenceIMS Catalog Populate utility (DFS3PU00)(System Utilities)z/OS: Return codes for the DFSMS non-VSAMCLOSE macro

DFS4533I nnn MEMBERS WERE ADDED TOTHE IMS CATALOG DIRECTORY.

ExplanationA total of nnn ACBLIB members were copied as newmembers into the IMS catalog directory from theACBLIBs used as input to the IMS Catalog Populateutility.

In the message text:nnn

The total number of resources added to the IMSdirectory.










http://www.ibm.com/support/knowledgecenter/SSLTBW_2.3.0/com.ibm.zos.v2r3.idad500/x1ca.htm

http://www.ibm.com/support/knowledgecenter/SSLTBW_2.3.0/com.ibm.zos.v2r3.idad500/x1ca.htm

System actionThe IMS Catalog Populate utility continues to run.


Module:DFS3DU10


DFS4534I nnn MEMBERS WERE REPLACEDIN THE IMS CATALOG DIRECTORY.

ExplanationA total of nnn ACBLIB members were copied asreplacement members into the IMS catalog directoryfrom the ACBLIBs used as input to the IMS CatalogPopulate utility.


The total number of existing resources in the IMSdirectory that were replaced by instances of thoseresources from the ACB library.



Module:DFS3DU10


DFS4535I nnn MEMBERS WERE STAGED TOBE ADDED TO THE IMS CATALOGDIRECTORY.

ExplanationA total of nnn ACBLIB members were copied from theACBLIBs used as input to the IMS Catalog Populateutility to the IMS catalog directory staging data set tobe subsequently added as new members in the IMScatalog directory.


nnnThe total number of ACBs that were written to thestaging data set.

System actionThe IMS Catalog Populate utility continues normalprocessing.


Module:DFS3DU10


DFS4536I nnn MEMBERS WERE STAGEDTO BE REPLACED IN THE IMSCATALOG DIRECTORY.

ExplanationA total of nnn ACBLIB members were copied from theACBLIBs used as input to the IMS Catalog Populateutility to the IMS catalog directory staging data set tobe subsequently added as replacement members inthe IMS catalog directory.


The total number of resource instances that werecopied from the input ACB libraries into the stagingdata set of the IMS directory.



Module:DFS3DU10


DFS4537I INSTANCE yydddhhmmssth OFDBD|PSB name IS HELD FORINSERTION INTO THE IMSDIRECTORY BY THE IMPORTCOMMAND.










ExplanationThe IMS ACBLIB member name with timestampyydddhhmmssth was copied from the ACBLIBs usedas input to the IMS Catalog Populate utility to the IMScatalog directory staging data set to be subsequentlyadded as a new member in the IMS catalog directory.



The timestamp of the ACBLIB member.


System programmer responseYou can suppress this and other similar informationalmessages by specifying NOISRTLIST in the inputcontrol statements for the IMS Catalog Populate utilityin a data set referenced by the ddname SYSINP.

Module:DFS3DU10


DFS4538I INSTANCE acb-yydddhhmmssthOF DBD|PSB name IS HELDFOR IMPORT INTO THE IMSDIRECTORY TO REPLACE dir-yydddhhmmssth.

ExplanationThe IMS catalog directory already contains an existingmember name with timestamp dir-yydddhhmmssth.The ACBLIB member name with timestamp acb-yydddhhmmssth was copied to the IMS catalogdirectory staging data set to subsequently replace theIMS catalog directory member.


The ACBLIB member name.dir-yydddhhmmssth

The timestamp of the ACBLIB member that isalready in the IMS catalog directory.

acb-yydddhhmmssthThe timestamp of the ACBLIB member that wasadded to the IMS catalog directory staging dataset.


System programmer responseYou can suppress this and other similar informationalmessages by specifying NOISRTLIST in the inputcontrol statements for the IMS Catalog Populate utilityin a data set referenced by the ddname SYSINP.

Module:DFS3DU10


DFS4539I INSTANCE acb-yydddhhmmssthOF DBD|PSB name WAS NOTSTAGED. A LATER DIRECTORYINSTANCE dir-yydddhhmmssthEXISTS.

ExplanationThe IMS catalog directory already contains an existingmember name with timestamp dir-yydddhhmmssth.The ACBLIB member name with timestamp acb-yydddhhmmssth was not copied to the IMS catalogdirectory staging data set as a replacement for thedirectory member because its timestamp was earlierthan the directory members timestamp.


The ACBLIB member name.dir-yydddhhmmssth


acb-yydddhhmmssthThe timestamp of the ACBLIB member that wasnot added to the IMS catalog directory stagingdata set.


System programmer responseTo suppress this and other similar informationalmessages, specify NODUPLIST in the input controlstatements for the IMS Catalog Populate utility in adata set that is referenced by the ddname SYSINP.

Module:DFS3DU10







DFS4540E ADDING MEMBER DBD|PSB nameIN THE DIRECTORY STAGINGDATA SET FAILED WITH STOWRETURN CODE rc REASON CODE rs

ExplanationThe IMS Catalog Populate utility tried to write membername to the IMS directory staging data set. However,the internal STOW macro instruction that the utilityused detected an error.


The return code given by the STOW macroinstruction.


nameThe ACLIB member name.



Module:DFS3DU10


DFS4541E THE IMS CATALOG DIRECTORYSTAGING DATA SET FAILED TOOPEN. OPEN RC =rc

ExplanationAs part of building the IMS directory the IMS CatalogPopulate utility tried to open the IMS directory

staging data set. However, the internal OPEN macroinstruction that the utility used detected an error.


The return code given by the OPEN macroinstruction.

System actionThe IMS directory was not built, and the IMS CatalogPopulate utility terminated with return code 8.


Module:DFS3DU10

Related referenceIMS Catalog Populate utility (DFS3PU00)(System Utilities)z/OS: Return codes for the DFSMS non-VSAMOPEN macro

DFS4542I INSTANCE yydddhhmmssth OFDBD|PSB name IS ALREADY INTHE IMS CATALOG DIRECTORYAND WAS NOT STAGED.

ExplanationThe IMS catalog directory already contains an existingmember name with timestamp dir-yydddhhmmssth, sothe ACBLIB member name with the same timestampwas not copied to the IMS catalog directory stagingdata set as a replacement for the directory member.


The ACBLIB member name.yydddhhmmssth
















Module:DFS3DU10


DFS4545I DBD|PSB name WAS DELETEDFROM THE IMS DIRECTORY.

ExplanationAs part of processing a DELETE or DELDBVERstatement, the IMS Catalog Record Purge utilitydeleted member name from the IMS directory.


The ACB name in the IMS directory.

System action:None.


Module:DFS3DU10


DFS4546I DBD|PSB name WAS DELETEDFROM THE IMS DIRECTORYSTAGING DATA SET.

ExplanationAs part of processing a DELETE or DELDBVERstatement, the IMS Catalog Record Purge utilitydeleted member name from the IMS directory stagingdata set.


The ACB name in the IMS directory staging dataset.

System action:None.


Module:DFS3DU10


DFS4547W name WAS NOT PURGED BECAUSEIT IS RESERVED AS THE NAME OFAN IMS CATALOG RESOURCE.

ExplanationAs part of processing a DELETE statement, the IMSCatalog Record Purge utility found that member namewas to be deleted from the IMS catalog and the IMSdirectory. However, the first four characters of namematch the alias name of the IMS catalog and causeconflicts with the names of the catalog PSBs andDBDs. These names are reserved for the catalog PSBsand DBDs and cannot be purged.


The ACB name in the IMS catalog and IMSdirectory.

System action:Deletion of the member name from the IMS catalogand IMS directory is suppressed.

User response:Do not delete the PSB or DBD instances from the IMScatalog.

Module:DFS3PU10

Related referenceIMS Catalog Record Purge utility (DFS3PU10)(System Utilities)

DFS4548E THE IMS DIRECTORY CANNOTBE UPDATED BY THE CATALOGPURGE UTILITY EXCEPT IN ABATCH JOB.

Explanation:The IMS Catalog Purge utility must update the IMSdirectory, but the IMS system under which the utilityis running might also be using the directory withoutany serialization with the utility. To prevent conflictsbetween the online IMS system and the utility, theutility is not permitted to run.

System action:The IMS directory was not updated, and the IMSCatalog Purge utility ended with return code 12.

System programmer response:Run the IMS Catalog Purge utility as a batch jobin a DL/I or DBB region, and ensure that no active










IMS systems with ACBMGMT=CATALOG specified in theDFSDFxxx member of the IMS PROCLIB data set arealso running.

Module:DFS3PU10

Related referenceIMS Catalog Record Purge utility (DFS3PU10)(System Utilities)CATALOG and CATALOGxxxx sections of theDFSDFxxx member (System Definition)

DFS4549E VALIDATION OF DDccccccccFAILED. REASON CODE=rc [ERRORCODE=ec]

ExplanationValidation of the data set associated with DD ccccccccfailed for the reason indicated in reason code rc.Optionally, the service identified by reason code rcfailed with the error code indicated by error code ec.

System actionProcessing of the utility terminated.

Output destination:The Systems console

System programmer responseCorrect the problem as indicated by the reason code orerror code and restart the job.

Table 27. Reason or error code

Code Explanation

1 The data set hasmembers in it. The dataset must be empty inorder to proceed.

2 More than one data set isconcatenated to the DD.Only one data set can beassociated with the DD.

3 The data set is not a PDS-E.

4 The data set name doesnot match the namingconvention for the IMSCatalog Directory.

5 A DCB attribute of thedata set is improper forDD cccccccc.

Table 27. Reason or error code (continued)

Code Explanation

6 You cannot setDISP=SHR because theutility needs exclusiveuse of the data set.

10 The call to the DEVTYPEmacro failed with errorcode ec. Check theDEVTYPE return code forthe possible causes forerror code ec.

11 The call to the ISITMGDAmacro failed with errorcode ec. Check theISITMGD return code forthe possible causes forerror code ec.

DFS4550W INSTANCE yydddhhmmssth OFDBD | PSB name WAS NOTPURGED FROM THE IMS CATALOGBECAUSE IT CONTAINS ANACTIVE | A PENDING INSTANCE

ExplanationIn the message text:name

The DBD or PSB member name that could not bepurged.

yyydddhhmmssthThe time stamp of the DBD or PSB member activeor pending instance that could not be purged inthe format of yyyy for year, ddd for the Julian day,hh for the hour, mm for the minutes, ss for theseconds, and th for the thousands of a second.

The DELETE statements attempted to purge active orpending instances from the IMS Catalog while IMS wasonline. The IMS Catalog Record Purge utility did notdelete any records.

System actionThe DFS3PU10 utility fails with a return code 4.

User response:If the PSB or DBD has been removed from theACBLIB, then manually delete the member from theDIRECTORY PDSE dataset.

Module:DFS3PU10






DFS4551E THE MSC= EXECUTIONPARAMETER CANNOT CHANGEWITHOUT A COLD START

ExplanationA warm or emergency restart was attempted after thevalue of the MSC= execution parameter was changed.The restart failed because a cold start is required tochange the value of the MSC= execution parameter.

The value of the MSC= parameter might have beenchanged explicitly in a startup procedure or, ifthe MSC= parameter is not specified in a startupprocedure, IMS might have changed the effective valueof the MSC= execution parameter automatically basedon the presence or absence of a DFSCLL3x member forMSC resources in the IMS.SDFSRESL data set.

System actionIMS terminates with abend 0168 and reason codeX’1E’.

User responseEither change the value of the MSC= executeparameter to its value at the last cold start of the IMSsystem, or cold start IMS. The second DFS1929I thatis issued to the SYSLOG during restart indicates theincorrect value of the MSC= execute parameter.

Module:DFSRLP00

Related tasksEnabling MSC with the MSC= executionparameter (Communications and Connections)Related referenceMSC= parameter for procedures (SystemDefinition)

DFS4552W I/O ERROR WRITING MEMBERDFSIMSL.

ExplanationThe IMS system could not write to the DFSIMSLmember of the IMS directory data set of a sharedIMS catalog. The DFSIMSL member is an automaticallygenerated list of the IMS systems that share the IMScatalog.

System actionThe IMS system attempts to rebuild member DFSIMSLafter the restart process completes.


ModuleDFSRDB30

DFS4553W MEMBER xxxxxxxx PROCESSED.AN IMPROPER CONDITION WASDETECTED. REASON nnnnn.

ExplanationAn error occurred while IMS was processing a memberin the IMS catalog directory data set.


The name of the member being processed.nnnnn

The reason code for the error. The following listprovides the reason codes and their meanings.Reason

Meaning1

The named member was found in a dataset other than the first data set of the IMScatalog directory data sets concatenation. Thisis an unexpected condition and might cause aproblem with other IMS processes.

System actionFor reason code 1, IMS initialization proceeds.

Programmer responseFor reason code 1, contact IBM Software Support todetermine how this situation should be resolved.

ModuleDFSRDB30

DFS4554E UNABLE TO WRITE TO LIBRARY

ExplanationAn error occurred while the IMS Catalog LibraryBuilder utility was attempting to write to an outputdata set.



http://www.ibm.com/support/knowledgecenter/SSEPH2_15.1.0/com.ibm.ims15.doc.ccg/ims_msc_admin_enable_with_exec_parm.htm#ims_msc_admin_enable_with_exec_parm

http://www.ibm.com/support/knowledgecenter/SSEPH2_15.1.0/com.ibm.ims15.doc.ccg/ims_msc_admin_enable_with_exec_parm.htm#ims_msc_admin_enable_with_exec_parm

http://www.ibm.com/support/knowledgecenter/SSEPH2_15.1.0/com.ibm.ims15.doc.sdg/ims_proc_parms_msc.htm#ims_proc_parms_msc

http://www.ibm.com/support/knowledgecenter/SSEPH2_15.1.0/com.ibm.ims15.doc.sdg/ims_proc_parms_msc.htm#ims_proc_parms_msc

Operator responseReview the error messages that were written to theconsole to identify the cause of the error and the dataset that the utility was trying to write to.


Module:DFS3LU00

Related referenceGet request (GET) for the IMS catalog API(System Programming APIs)

DFS4555W [DBD | PSB] MEMBER xxxxxxxx ISIGNORED

ExplanationThe IMS Catalog Library Builder utility (DFS3LU00)encountered a member that uses the GSAM accesstype. The DFS3LU00 utility does not support the GSAMaccess type.

System actionThe DFS3LU00 utility does not process the member.The DFS3LU00 utility continues processing othermembers and ends with return code 4.

Programmer response:No action is required.

Module:DFS3LU00

Related referenceIMS Catalog Library Builder utility (DFS3LU00)(System Utilities)

DFS4560E TRACE TABLE nnnn IS NOT AVALID TRACE TABLE.

ExplanationThe type-2 trace table name that is specified in theTRCLEV statement in the DIAGNOSTICS_STATISTICSsection of the DFSDFxxx member is not a valid tracetable name.


The trace table name that is specified in theTRCLEV statement.

System action:IMS continues processing. You can use the UPDATETRACE command to start tracing.

System programmer response:Specify a valid trace table name in the TRCLEVstatement. See the TRCLEV parameter in the

DIAGNOSTICS_STATISTICS section of the DFSDFxxxmember (System Definition) topic for the valid tracetable names.

Module:DFSDFN10

DFS4561E ERROR LOADING TRACESERVICES MODULE mmmmmmmmIMODULE LOAD RC= nnnnnnnn

ExplanationIMS was unable to load the specified module.

In the message text:mmmmmmmm

The name of the module for which the erroroccurred.

nnnnnnnnThe return code from the IMODULE service.

System action:IMS abends with a U0630 abend.

System programmer response:Determine the reason for the IMODULE LOAD failurefrom the RC value returned and correct the problem.If you are unable to resolve the problem, save theSYSLOG and the dump, and call IBM Software Supportfor assistance.

Module:DFSTRI00


DFS4562E ERROR ALLOCATING SPACE FORTHE tttt TRACE TABLE. BLOCKTYPE bbbb BCB SERVICE RC=nnnnnnnn

ExplanationIMS was unable to allocate space for type-2 tracetable by using BCB services.


ttttThe name of the trace table for which space couldnot be allocated.

bbbbThe BCB block type that could not be allocated.

nnnnnnnnThe return code from BCB services.








http://www.ibm.com/support/knowledgecenter/SSEPH2_15.1.0/com.ibm.ims15.doc.sdg/ims_dfsdfxxx_proclib_diagnostics_and_statistcs.htm#ims_dfsdfxxx_proclib_diagnostics_and_statistcs

http://www.ibm.com/support/knowledgecenter/SSEPH2_15.1.0/com.ibm.ims15.doc.sdg/ims_dfsdfxxx_proclib_diagnostics_and_statistcs.htm#ims_dfsdfxxx_proclib_diagnostics_and_statistcs


If you are unable to resolve the problem, save theSYSLOG and the dump and call IBM Software Supportfor assistance.

Module:DFSTRSV0

DFS4570E USER EXIT LOAD FAILURE. EXITTYPE - tttttttt MODULE NAME -mmmmmmmm IMODULE LOAD RC- rr

or

USER EXIT SETUP FAILED. EXIT TYPE -tttttttt MODULE NAME - mmmmmmm REASON -rrrrrrrrrrrrrrrrr RC - rr

ExplanationIMS was unable to load a user exit routine. The exitroutine name is defined in the USER_EXITS section ofthe DFSDFxxx member.

In the message text:tttttttt

The user exit type. If this field is USRXINIT, theerror is from user exit initialization services andnot related to an individual user exit routine.In this case, mmmmmmmm is blank. If thisfield is USRXRFSH, the error is during REFRESHUSEREXIT command processing and not related toa particular user exit type.

mmmmmmmmThe name of the user exit routine or the controlblock for which the error occurred.

If the user exit routine name is USXGRAMR, themessage refers to storage required for the parsedgrammar output of the user exit definitions in theDFSDFxxx member of the IMS PROCLIB data set.

rrrrrrrrrrrrrrrrrThe reason the user exit setup failed. This can beone of the following strings:BCB RELEASE ERROR

Storage for the USXI or USXS control blockscould not be released by BCB services.

BCB GET ERRORStorage for the USXI or USXS control blockscould not be obtained from BCB services.

BLDL ERRORBLDL failed for the indicated module name.If RC=04, the specified module could not befound.

IMOD FREE ERRORStorage for the indicated module could not bereleased using IMODULE FREE.

IMOD GETM ERRORStorage for the indicated module could not beobtained using IMODULE GETMAIN.

IMOD GETS ERRORStorage for the indicated module could not beobtained using IMODULE GETSTOR.

LOAD ERRORLOAD failed for the indicated module name.

NO EXITDEF STMTNo EXITDEF statement in the DFSDFxxxmember for the specified exit type.

PARSE ERRORAn error was encountered while parsingthe DFSDFxxx member. If the error was aparse error (as opposed to an error in theparsing service), BPE003E messages give moreinformation on the error.

PDS READ ERRORAn error was encountered while reading theDFSDFxxx member. The MODULE NAME fieldindicates the member that was read.

STOR OBTN ERRORStorage for the indicated module could not beobtained using STORAGE.

rrThe return code issued by the services that areassociated with the reason text of this message. Ifthere is no return code from the service, this fieldis blank.

This message is also issued while processing theoutput EXITDEF parameter in the USER_EXITS sectionof the DFSDFxxx member during IMS initialization orduring the processing of the REFRESH USEREXITcommand.


System programmer responseIf the user exit setup failed because of a storage error,check that the region size of the address space islarge enough. Increase the region size by changing theREGION= parameter on the IMS control region JCLand restart IMS.

If the user exit setup failed because of a BLDL or aLOAD error, check the PROCLIB member to ensure theexit routine name is correct. If the name is correct inthe PROCLIB member, ensure that the load module isavailable to the control region.


ModuleDFSUSRXI, DFSUSX00

Note: If the Module field is **NONE**, the error doesnot have a user exit module associated with it.


DFS4571E USER EXIT TYPE tttttttt IS NOT AVALID USER EXIT TYPE

ExplanationThe user exit type specified on the EXITDEF statementin the USER_EXITS section of the DFSDFxxx memberis not a valid user exit type.


The user exit type specified on the EXITDEFstatement

This message is also issued while processing theoutput EXITDEF parameter in the USER_EXITS sectionof the DFSDFxxx member during IMS initialization orduring the processing of the REFRESH USEREXITcommand.


System programmer response:Specify a valid user exit type on the EXITDEFstatement. See the IMS system definition informationfor the valid user exit types.

Module:DFSUSRXI

DFS4572E USER EXIT TYPE IS NOT ELIGIBLEFOR MULTI-EXIT ROUTINESUPPORT

ExplanationThe user exit type tttttttt is a valid user exit type, but itis not eligible for multi-exit routine support.


ttttttttThe user exit type


System programmer response:Check the PROCLIB member to ensure that all of theexits that are listed are eligible for multi-exit support.Remove any that are not.

Module:DFSUSRXI

DFS4573E UNABLE TO CALL USER EXITTYPE – tttttttt FUNCTION - ffffffffREASON - cccccccccccccccc RC - rr

ExplanationIMS was unable to call any exit routines of thespecified user exit type.


ttttttttThe user exit type.

ffffffffThe function code that was to be passed to theexit. If there is no function code, this part is blank.

ccccccccccccccccThe reason the exit type could not be called.Possible reasons are:IMOD GETM ERROR

An IMODULE GETMAIN error was encountered.NO DPST STORAGE

The PSTDUXIB field that is supposed to pointto the pre-allocated storage for the interfaceblock and parameter list for dependent regionPSTs (DPSTs) was 0. Return code rr is 8.

rrThe return code from the service that received anerror. If the error does not have a return code, thisfield is blank.

System action:Regardless of the reported reason, IMS does not callthe IMSMON exit type, and IMS continues processing.This message is issued only once for the lifetime ofIMS. If the storage shortage is eventually relieved, thecalling of the IMSMON exit type resumes.

System programmer responseIf this is a storage shortage, the region size of theaddress space might be too small. Increase the regionsize by changing the REGION= parameter on the IMScontrol region JCL and restart IMS.

If the problem persists, save any memory dumpsand IMS logs and contact IBM Software Support. Ifno memory dumps were produced, create a consoledump of the IMS control region.


Module:DFSFSTM0, DFSTRM00, DFSMNTR0

Related referenceIMODULE return codes (Messages and Codes)Related information“IMS problem determination” on page 11





DFS4574W DUPLICATE USER EXIT ROUTINEDEFINED. TYPE- ttttttt MODULENAME - mmmmmmmm

ExplanationA duplicate user exit routine was defined in the EXITSparameter of the EXITDEF statement for the indicateduser exit type. The exit is only loaded one time and iscalled only one time.


ttttttttThe user exit type

mmmmmmmmThe user exit module name

System action:The second user exit module name is ignored and IMScontinues processing.

System programmer response:Check the EXITS parameter that is in error and eithercorrect or remove the user exit routine name.


Module:DFSUSX00


DFS4575E ERROR IN ADD ROUTINE FOREXIT TYPE tttttttt. SERVICE -sssssssssssssssss SERVICE RC -rrrr

ExplanationAn error was encountered in the add routine for userexit type tttttttt. The add routine for a user exit type isrun when the user exit type is added by the REFRESHUSEREXIT command.tttttttt

The user exit type.sssssssssssssssss

The service in which the error was encountered.rrrr

The reason code received from the service thatfailed.

System action:The user exit type is not added.

System programmer responseIf the error is a storage error, check that the regionsize of the address space is large enough. Increasethe REGION= parameter on the IMS control region JCLand restart IMS.

If the problem persists, create a console dump of theIMS control region and contact IBM Software Support.

Module:DFSIR010, DFSUSX90

DFS4576W ERROR IN DEL ROUTINE FOREXIT TYPE tttttttt. SERVICE -sssssssssssssssss SERVICE RC -rrrr

ExplanationAn error was encountered in the delete routine for userexit type tttttttt.

The delete routine for a user exit type is run when theuser exit type is deleted by the REFRESH USEREXITcommand.

ttttttttThe user exit type.

sssssssssssssssssThe service in which the error was encountered.

rrrrThe reason code received from the service thatfailed.

System action:The user exit type is deleted. If the error is a storagerelease error, the storage is still allocated. If the userexit type is added at a later time by the REFRESHUSEREXIT command, the storage will be reused.

System programmer responseYou can use the REFRESH USEREXIT command toadd the user exit type and then delete the user exittype again with the REFRESH USEREXIT command.IMS will run the delete routine for the user exit typeand retry the failing service.

If the problem persists, create a console dump of theIMS control region and contact IBM Software Support.

Module:DFSIR010, DFSUSX90

DFS4585W RASE SECURITY USER EXITDELETED. NO RASE SECURITYUSER EXIT CALL WITHpppppppppppppppp


ExplanationThe Resource Access Security user exit (RASE) wasdeleted with the REFRESH USEREXIT command.pppppppppppppppp

The ISIS, ODBASE, and ODBMSECURE parametervalues.

An ISIS value of A or C specifies that resource securitychecking is to be done using RACF and the RASE userexit (ISIS=A) or the user exit only (ISIS=C).

ODBASE=Y specifies that the RASE user exit is called ifit exists.

An ODBMSECURE value of A specifies that resourcesecurity checking is to be done using both RACFand the RASE user exit. An ODBMSECURE value of Especifies that resource security checking is to be doneusing only the RASE user exit.


System programmer response:If you do not want to run with the RASE user exit, noaction is necessary. If you want to run with the RASEuser exit, modify the DFSDFxxx member to defineyour RASE user exit routine and reissue the REFRESHUSEREXIT command for the RASE user exit type.

Module:DFSIR010

DFS4586E LOGEDIT USER EXIT COULD NOTBE ADDED. NO LOG RECORDSSELECTED FOR EDITING.

ExplanationNo log records are selected to be passed to theLOGEDIT user exit, so the LOGEDIT user exit isnot added. This message can be issued during IMSinitialization or as a result of the REFRESH USEREXITcommand.

If it is issued during IMS Initialization, the LOGEDITuser exit is defined with the EXITDEF statement in theDFSDFxxx member. The LOGEDIT user exit is deleted.

If the message is issued as a result of the REFRESHUSEREXIT command, the LOGEDIT user exit is notadded.

The log record types that are to be passed to theLOGEDIT user exit are identified with the LOGEDITstatement in the DFSVSMxx member.


System programmer response:You must identify the log record types to be passedto the LOGEDIT user exit in the LOGEDIT statement in

the DFSVSMxx member at IMS start up. IMS must berestarted to pick up the log record types.

Module:DFSIR010, DFSXLGI0

DFS4587E IMSMON EXIT PROCESSINGERROR - eeeeeeeeeeeeeeee RC = rr

ExplanationIMS encountered a problem that is related to callingthe IMSMON exit type or managing associated storage.eeeeeeeeeeeeeeee

Reason text for the failure. Possible reason textsare as follows:FREESTR MONEXTBL

IMODULE FREESTOR error for the storage ofthe array that is passed to the exits for themto register interest in SLOG (DC monitor workarea) codes. Return code rr is the IMODULEreturn code.

FREESTR LMONARRYIMODULE FREESTOR error for the storage forthe SLOG interest array that is checked by IMSto see whether any exit registered interest ina particular SLOG code. Return code rr is theIMODULE return code.

GETSTOR SLOG ARYIMODULE GETSTOR error for obtaining theSLOG interest array that is used by IMS. Returncoderr is the IMODULE return code.

rrThe return code that is associated with the reasontext.

System actionSystem action differs depending on the reason text.FREESTR MONEXTBL

IMS continues processing.FREESTR LMONARRY

IMS continues processing.GETSTOR SLOG ARY

The IMSMON exit type will not be called. TheLMONNSLA flag is set to indicate the condition.

System programmer responseIf the reason text is GETSTOR SLOG ARY, the regionsize of the address space might be too small. Increasethe region size by changing the REGION= parameteron the IMS control region JCL and restart IMS.

If the problem persists, save any memory dumpsand IMS logs and contact IBM Software Support. Ifno memory dumps were produced, create a consoledump of the IMS control region. If the IMSMON exit


in question is a vendor product, contact the vendor forguidance.

Problem determination1, 2, 3, 4, 5, 15, 25, 36, 41.

Module:DFSMNTR0


DFS4591E THE DIRECTORY DATA SETNAMES IN THE FAILED IMSAND THE RESTARTED IMS DONOT MATCH. UOW ABORTED.TOKEN=cccccccccccccccc.

ExplanationThe <CATALOG> section of the DFSDFxxx PROCLIBmember of the failed IMS and the restarted IMS isnot the same. The high level qualifier in the name ofthe IMS directory data set of the failed IMS does notmatch the high level qualifier in the name of the IMSdirectory data set of the restarted IMS.



System actionIMS restart terminates abnormally with abend 0053.

System programmer responseThe content of the <CATALOG> section in theDFSDFxxx member that is used by the restarted IMSmust be identical to the DFSDFxxx member that wasused by the failed IMS. Correct any discrepancy andrestart IMS.

Module:DFSMOL20

Related referenceCATALOG and CATALOGxxxx sections of theDFSDFxxx member (System Definition)Related informationIMS directory data sets (System Definition)

DFS4593E ACBSHR=Y IS SPECIFIED, BUTTHE DIRECTORY DATA SET IS FORA NON SHARED IMS SYSTEM.

ExplanationThis IMS system is configured to share applicationcontrol blocks (ACBs) with other IMS systems in anIMSplex, by a specification of ACBSHR=Y in either theDFSCGxxx member or the DFSDFxxx member of theIMS.PROCLIB data set. However, the sharing attributeindicators in the IMS directory data set memberDFSIMSL indicate that the IMS directory is set up forexclusive use by another IMS system.

System actionIMS terminates abnormally with abend U0071.

System programmer responseConfirm that the ACBSHR parameter is correctlyspecified in the restarting IMS system. TheACBSHR parameter might be specified in either theDFSCGxxx member or the DFSDFxxx member of theIMS.PROCLIB data set.

If the ACBSHR specification in the PROCLIB member isincorrect, change the specification to ACBSHR=N.

If the ACBSHR specification in the PROCLIB member iscorrect, either the restarting IMS system is referencingthe wrong IMS catalog, or the IMS catalog was not setup with the correct ACBSHR specification.

If the IMS system is referencing the wrong IMScatalog, specify the alias name of the correct IMScatalog on the ALIAS parameter in the <CATALOG>section of the DFSDFxxx member of the restarting IMSsystem.

The IMS directory sharing attributes are maintainedin the DFSIMSL member in the IMS directory andwere initially set by the first IMS system that usedthe IMS directory. The sharing attributes were setbased on the conditions that existed when the firstIMS that was using the directory data sets wasstarted. If the first IMS had specified ACBSHR=Y, hada COMMON_SERVICE_LAYER section in the DFSDFxxxmember, and had specified RMENV=Y in that section,then the directory sharing attributes were set to allowthe directory to be shared by other IMS systems. OnlyIMS systems specifying ACBSHR=Y are allowed to usesuch a directory.

If the first IMS did not meet all of those conditions,either by specifying ACBSHR=N or did not have aCOMMON_SERVICE_LAYER section in the DFSDFxxxmember or had specified RMENV=N, then the directorysharing attributes were set to allow only use bythe first IMS. No other IMS is allowed to share thedirectory.

If the directory sharing attributes need to be changed,the first IMS system that set the sharing attributes in





the DFSIMSL member must be configured to satisfythe conditions for sharing the directory and then thatIMS system must be restarted.

Module:DFSRDB30

Related conceptsThe IMS catalog in multi-system configurations(System Definition)Related tasksSetting up the IMS catalog (System Definition)Related referenceCATALOG and CATALOGxxxx sections of theDFSDFxxx member (System Definition)DFSCGxxx member of the IMS PROCLIB dataset (System Definition)COMMON_SERVICE_LAYER section of theDFSDFxxx member (System Definition)Related information0071 (Messages and Codes)

DFS4594W THE CURRENT CHANGETO ACBMGMT SUPPORT ISINADVISABLE WITH A RESTARTUSING CHECKPOINT

ExplanationWhile the IMS system was restarting, IMS detectedthat the IMS catalog changed since the applicationcontrol blocks (ACBs) were last loaded into the onlineIMS system. If the changes that were made to theIMS catalog introduce a mismatch between the ACBsin the online IMS system and the ACBs in the IMSdirectory data set, IMS abends when the mismatch isencountered.

System actionIMS continues processing. If IMS encounters amismatch between the ACB blocks in the IMSdirectory and the ACB blocks that IMS loaded intomemory from the logs during the emergency restart,IMS abends.

System programmer responseConfirm that the IMS system is referencing the correctIMS catalog. The parameters in the <CATALOG>section in the DFSDFxxx member that is used bythe restarted IMS must be identical to the DFSDFxxxmember that was used by the failed IMS. Correct anydiscrepancy and restart IMS.

Confirm that the changes to the IMS catalog areintentional.

If the IMS system is referencing the correct IMScatalog and the changes are intentional, use a coldstart to add the current changes to the IMS cataloginto the IMS system.

Module:DFSRDB30

Related conceptsIMS directory data sets (System Definition)Related referenceCATALOG and CATALOGxxxx sections of theDFSDFxxx member (System Definition)

DFS4596E OLC COMMIT REJECTED. INVALIDMEMBER IN FMTLIB ddname -nnmbrname

ExplanationAn online change commit command, /MODIFYCOMMIT, was rejected because an invalid member wasdetected in the inactive FMTLIB data set. The memberis invalid because it contains an invalid directory size;that is, the directory size is negative or greater than32767 bytes.


The 7-character FMTLIB DD name, which is eitherFORMATA or FORMATB.

nnThe 2-byte FMTLIB data set concatenation numberwithin the FMTLIB DD statement.

mbrnameThe 8-character invalid member name in theFMTLIB data set.

For example, if a module is erroneously copied intothe inactive FMTLIB before the /MODIFY COMMITcommand is issued, the /MODIFY COMMIT commandmight fail with this error. If the member is an actualMFS format with an invalid directory size, the firsttwo characters of the format name are unprintablehexadecimal values that might appear as blanks orother non-alphanumeric characters in this output.The first two characters of the format name mightappear as different non-alphanumeric characterswhen browsing the FMTLIB with TSO.

System action:The online change commit command is rejected.

Output destination of messageThe message is sent to the z/OS system console.

Operator response:Delete the invalid member from the FMTLIB data setand either reissue the /MODIFY COMMIT command or




http://www.ibm.com/support/knowledgecenter/SSEPH2_15.1.0/com.ibm.ims15.doc.sdg/ims_catalog_definition_overview.htm#ims_catalog_definition_overview











abort the online change by using the /MODIFY ABORTcommand.

Module:DFSICV50

DFS4597I DBD dbd_name IS DELETEDFROM THE CATALOG AND THEDIRECTORY. PST pst_name.

ExplanationThe database was deleted from both the catalogdatabase and the directory data set by a DROPDATABASE DDL statement.


The name of the database that was deleted.pst_name


System actionIMS continues.


Module:DFSMOLS0

DFS4598I PSB psb_name IS DELETEDFROM THE CATALOG AND THEDIRECTORY. PST pst_name

ExplanationThe program view (PSB) was deleted from both thecatalog database and the directory data set by a DROPPROGRAMVIEW DDL statement.


The name of the program view (PSB) that wasdeleted.




Module:DFSMOLS0

DFS4599E RECOVERY UTILITY FAILEDTO CLEANUP DIRECTORYREASON=reasontext

ExplanationThe recovery utility to clean up the directory failed andthe cause of failure was explained in the reason text.

System actionThe cleanup job failed.

System programmer responseCorrect the cause of failure and run the cleanup utilityagain.

Module:DFSOLC80 DFSPCC30

DFS4600E RSN=02 AREA areanameSERIALIZATION PROCESS FAILED

ExplanationThe area serialization process failed. One or morepreceding DFS4600I messages describe the reasonfor the area serialization failure.

During the DEDB Alter process, the DEDB area isserialized and unserialized for one or more instances.When the DEDB area fails serialization, the DFS4600ERSN=02 message is issued for the last serializationinstance.

System actionThe DEDB Alter utility terminates processing withoutperforming the requested DEDB Alter function.

Module:DBFDAQA0


DFS4600I RSN=00 AREA areanameSERIALIZATION PROCESSSTARTED

or

RSN=01 AREA areaname SERIALIZATION PROCESSENDED SUCCESSFULLY




or

RSN=03 AREA areaname SERIALIZATION FAILED –THREAD yyyyyyyy UPDATED THE AREA BUT WASNOT SERIALIZED

or

RSN=04 AREA areaname SERIALIZATION FAILED –THREAD yyyyyyyy WITH UPDATE INTENT FOR THEAREA WAS NOT SERIALIZED

or

RSN=06 AREA areaname SERIALIZATION TIMEDOUT WHILE ATTEMPTING TO SERIALIZE THE AREA

or

RSN=07 AREA areaname SERIALIZATION TIMEDOUT – RETRY STARTING

or


or


or

RSN=0A AREA areaname SERIALIZATION TIMEDOUT – RETRY STARTING

or

RSN=0B AREA areaname SERIALIZATION TIMEDOUT – RETRY STARTING

or

RSN=0C AREA areaname SERIALIZATION TIMEDOUT WHILE ATTEMPTING TO SERIALIZE THE AREA

ExplanationDuring the DEDB Alter process, the DEDB area neededto be serialized with application threads.

• If the serialization process completes successfully,RSN=01 is the last message in the stream.

• If the serialization process fails, the last message inthe stream is DFS4600E RSN=02 with a precedingDFS4600I message to explain the failure.

During the DEDB Alter process, the DEDB area isserialized and unserialized for one or more instances.The DFS4600I RSN=00 and DFS4600I RSN=01messages are issued when the DEDB area is serializedsuccessfully for each instance. When the DEDBarea fails serialization, the DFS4600I RSN=00 andDFS4600E RSN=02 messages are issued for the lastserialization instance.

Reason codeMeaning

RSN00The area serialization process started for areaareaname.

RSN01The area serialization process ended successfully.The area was serialized by the DEDB Alter utility.

RSN03The area serialization process failed. Threadyyyyyyyy updated area areaname, but areaareaname was not correctly serialized.

RSN04The area serialization process failed. Threadyyyyyyyy was not involved with serializing areaareaname, but the task was unable to determineif this was acceptable.

RSN06, RSN0CThe area serialization process timed out whileattempting to serialize the area in exclusive mode.

RSN07, RSN08, RSN09, RSN0A, RSN0BThe area serialization process timed out whileattempting to serialize the area in exclusive mode.Another attempt to serialize the area will be madebecause RETRY YES or RETRY retry_value wasspecified as a DEDB Alter utility input option.

System actionIf the area serialization is successful, the DEDB Alterutility continues processing. If the area serializationis unsuccessful, the DEDB Alter utility terminatesprocessing without performing the requested DEDBAlter function.

Module:DBFDAQA0




DFS4601E RSN=02 DEDB dedbnameSERIALIZATION PROCESS FAILED

ExplanationThe DEDB serialization process failed. One or moreDFS4601I messages that precede describes thereason for the DEDB serialization failure.


Module:DBFDAQA0


DFS4601I RSN=00 DEDB dedbnameSERIALIZATION PROCESSSTARTED

or

RSN=01 DEDB dedbname SERIALIZATION PROCESSENDED SUCCESSFULLY

or

RSN=03 DEDB dedbname SERIALIZATION FAILED– THREAD yyyyyyyy UPDATED THE DEDB BUT WASNOT SERIALIZED

or

RSN=04 DEDB dedbname SERIALIZATION FAILED –THREAD yyyyyyyy WITH UPDATE INTENT FOR THEDEDB WAS NOT SERIALIZED

or

RSN=06 DEDB dedbname SERIALIZATION TIMEDOUT WHILE ATTEMPTING TO SERIALIZE THE DEDB

or

RSN=07 DEDB dedbname SERIALIZATION TIMEDOUT – RETRY STARTING

or


or


or

RSN=0A DEDB dedbname SERIALIZATION TIMEDOUT – RETRY STARTING

or

RSN=0B DEDB dedbname SERIALIZATION TIMEDOUT – RETRY STARTING

or

RSN=0C DEDB dedbname SERIALIZATION TIMEDOUT WHILE ATTEMPTING TO SERIALIZE THE DEDB

ExplanationDuring the DEDB Alter process, the DEDB databaseneeded to be serialized with application threads.

• If the process completed successfully, RSN=01 willbe the last message in the stream.

• If the serialization process fails, the last messagein the stream will be DFS4601E RSN=02 with apreceding DFS4601I message to explain the failure.

Reason codeMeaning




RSN00The DEDB serialization process started for DEDBdedbname.

RSN01The DEDB serialization process endedsuccessfully. The area was serialized by the DEDBAlter utility.

RSN03The DEDB serialization process failed. Threadyyyyyyyy updated DEDB dedbname, but DEDBdedbname was not correctly serialized.

RSN04The area serialization process failed. Threadyyyyyyyy was not involved with serializing DEDBdedbname, but the task was unable to determinewhether this was acceptable.

RSN06, RSN0CThe DEDB serialization process timed out whileattempting to serialize the area in exclusive mode.

RSN07, RSN08, RSN09, RSN0A, RSN0BThe DEDB serialization process timed out whileattempting to serialize the DEDB in exclusivemode. Another attempt to serialize the DEDB willbe made because RETRY YES or RETRY retry_valuewas specified as a DEDB Alter utility input option.

System actionIf the DEDB serialization is successful, the DEDB Alterutility continues processing. If the DEDB serializationis unsuccessful, the DEDB Alter utility terminatesprocessing without performing the requested DEDBAlter function.

Module:DBFDAQA0


DFS4602E BOTH ACTIVE AND SHADOW ARESPECIFIED

ExplanationBoth ACTIVE and SHADOW control statementsare specified for the DEDB Initialization utility(DBFUMIN0). These control statements are mutuallyexclusive, because the utility cannot format bothactive area data sets and shadow data sets in thesame execution.

System actionThe DEDB Initialization utility terminates withoutprocessing the function.

System programmer responseSpecify the ACTIVE control statement to format activearea data sets in one execution. Specify the SHADOWcontrol statement to format shadow area data sets andshadow image copy data sets in another execution.

Module:DBFUMIN0

Related referenceDEDB Initialization utility (DBFUMIN0)(Database Utilities)

DFS4603I DBRC QUIESCE ENDERROR FOR DEDB ALTER,DEDB=dddddddd RC=rrrrrrrrRSN=rrrrrrrr MODULE=bbbbbbbb

or

DBRC QUIESCE END ERROR FOR DEDBALTER, AREA=aaaaaaaa RC=rrrrrrrr RSN=rrrrrrrrMODULE=bbbbbbbb

ExplanationDuring IMS restart, IMS detected that the DEDB Alterutility was running when IMS abnormally terminated.The QUIESCE in progress flag was still active in DBRC,and when IMS attempted to reset the QUIESCE flag,the DBRC call failed. The RC is set by DBRC for theDSPDBQ END call. The RSN code identifies from wherein the code the message was issued.

System actionEmergency restart continues.

System programmer responseList the RECON data sets and verify if the QUIESCE inprogress flag is still on. If it is, reset the quiesce inprogress flag.

Module:DBFEDA00

DFS4604I DBRC ALTER EOJ ERROR FORDEDB ALTER AREA=aaaaaaaaRC=rrrrrrrr MODULE=bbbbbbbb

ExplanationDuring IMS restart, IMS detected that the DEDB Alterutility was running when IMS abnormally terminated.The DEDB ALTER flag was on in the RECONS forthe AREA=aaaaaaaa. The RC is set by DBRC for the




http://www.ibm.com/support/knowledgecenter/SSEPH2_15.1.0/com.ibm.ims15.doc.dur/ims_dbfumin0.htm#ims_dbfumin0


ALTEREOJ call. The RSN code identifies from where inthe code the message was issued.


System programmer responseList the RECON data sets and verify if the DEDB ALTERin progress flag is still on. If it is, reset the ALTER inprogress flag.

Module:DBFEDA00

DFS4605I RESTART ERROR PROCESSING5961 LOG RECORD, COULDNOT FIND AREA=aaaaaaaaMODULE=bbbbbbbb

ExplanationDuring IMS restart, IMS detected that the DEDB Alterutility was running when IMS abnormally terminated.IMS could not find the AREA=aaaaaaaa and could notprocess related 5961 log records.


System programmer responseIf the AREA was validly removed, no action isnecessary. If it was not, contact IBM Software Supportfor assistance.

Module:DBFEDA00

DFS4606I COULD NOT DELETE THE BLOCKSFOR DEDB ALTER DEDB=ddddddddRC=rrrrrrrr RSN=aaaaaaaaMODULE=bbbbbbbb

ExplanationDuring IMS restart, IMS detected that the DEDB Alterutility was running when IMS abnormally terminated.The ACTIVE ACBLIB contained an encrypted member,which IMS was unable to delete. The RC is set byDBFMOLS0 during the UNDO COPYLBOCKs call. TheRSN code identifies from where in the code themessage was issued.


System programmer responseVerify that the encrypted member is no longer needed.If it is not, delete it from ACBLIB. If you are usinga shared ACBLIB, all restarting data sharing IMSsubsystems attempt cleanup, but only the first IMS tolock the ACBLIB finds the blocks to delete.

Module:DBFEDA00

DFS4607I COULD NOT FIND THE DDIRFOR DEDB ALTER DEDB=ddddddddRC=rrrrrrrr MODULE=bbbbbbbb

ExplanationDuring IMS restart, IMS detected that the DEDB Alterutility was running when IMS abnormally terminated.IMS could not find the DEDB=dddddddd and could notprocess related 5961 log records. The RC is set byDFSCBTS when the DDIR cannot be found.


System programmer responseIf the AREA was properly removed, no action isnecessary. If it was not, contact IBM SoftwareSupport.

Module:DBFEDA00

DFS4608E COULD NOT UNDO MOLC FORDEDB ALTER DEDB=dddddddRC=rrrrrrrr RSN=aaaaaaaaMODULE=bbbbbbbb

ExplanationDuring IMS restart, IMS detected that the DEDB Alterutility was running when IMS abnormally terminated.IMS detected that the STAGING member for theDEDB=dddddddd had been copied into the activelibrary at the time of the IMS failure. The attemptto restore the ACTIVE ACBLIB member failed. TheRC is set by DBFMOLS0 during the UNDO MOLC call.The RSN code identifies from where in the code themessage was issued.



System programmer responseVerify that the DEDB member in the ACTIVE ACBLIB isfrom the STAGING member. If it is, the DEDB memberin the ACTIVE ACBLIB must be manually restored fromthe backup ACBLIB of active members.

Module:DBFEDA00

DFS4609I THE DEDB ALTER MOLC PROCESSWAS CLEANED UP DURINGRESTART DEDB=ddddddddMODULE=aaaaaaaa

ExplanationDuring IMS restart, IMS detected that the DEDB Alterutility was running when IMS abnormally terminated.IMS detected that the STAGING member for theDEDB=dddddddd had been copied into the activelibrary at the time of the IMS failure. The attempt torestore the ACTIVE ACBLIB completed successfully.



Module:DBFEDA00

DFS4610E ONLY ONE keyword KEYWORDIS ALLOWED PER UTILITYEXECUTION

ExplanationIn the message text, keyword is one of the followingcontrol statements: ADDAREA, ALTERAREA, ALTERDB,REPLRAND, RETRY, RETRYWAIT, TIMEOUT, TYPE, orUNKEYSEG.

The DEDB Alter utility supports only one of eachof these control statements per utility execution.However, one or more of these control statements wasspecified multiple times.

System actionThe DEDB Alter utility terminates without processingthe function.

System programmer responseDelete all except one of each of the control statementsthat are listed in the message explanation, andresubmit the job.

Module:DBFUMMS0

Related referenceControl statements for the DEDB Alter utility(DBFUDA00) (Database Utilities)

DFS4611E TIMEOUT VALUE SPECIFIED ISINCORRECT

ExplanationThe TIMEOUT value must be a 1- to 3-digit numericvalue from 1 - 999.

System actionThe DEDB Alter utility terminates without completingthe requested function.

System programmer responseCorrect the TIMEOUT value or delete it so that thedefault TIMEOUT value of 15 seconds will be used,and then resubmit the job.

Module:DBFUMMS0


DFS4613E DEDB ALTER TERMINATEDBECAUSE EEQE EXISTS

ExplanationThe DEDB Alter utility was run with the ALTERAREAfunction to alter an area online. However, the areato be altered has one or more extended error queueelements (EEQEs).


System programmer responseRecover the area to be altered and resolve the EEQEs.

Module:DBFUMMS0

Related conceptsDL/I I/O errors and recovery (DatabaseAdministration)Related referenceDEDB Alter utility (DBFUDA00) (DatabaseUtilities)


http://www.ibm.com/support/knowledgecenter/SSEPH2_15.1.0/com.ibm.ims15.doc.dur/ims_dbfuda00utility.htm#ims_dbfuda00utility




http://www.ibm.com/support/knowledgecenter/SSEPH2_15.1.0/com.ibm.ims15.doc.dag/ims_dliioerrors.htm#ims_dliioerrors




DFS4614E DEDB ALTER REQUIRES A 2 STAGERANDOMIZER

ExplanationThe DEDB Alter utility detected that the DEDBdatabase to be altered does not use a 2-stagerandomizer. The DEDB Alter utility supports only DEDBdatabases that use a 2-stage randomizer.


System programmer responseConvert the DEDB database to use a 2-stagerandomizer:

• If the randomizer is a 1-stage randomizer, unloadand reload the DEDB database using a 2-stagerandomizer. Perform an online change to change therandomizer from a 1-stage randomizer to a 2-stagerandomizer.

• If the randomizer is a 2-stage-randomizer-likerandomizer (defined as 1-stage randomizer butbehaves as a 2-stage randomizer), perform an onlinechange to change the randomizer from a 1-stagerandomizer to a 2-stage randomizer.

Module:DBFUMMS0

Related conceptsDL/I I/O errors and recovery (DatabaseAdministration)Related referenceDEDB Alter utility (DBFUDA00) (DatabaseUtilities)

DFS4615E ADDAREA, ALTERAREA,REPLRAND AND ALTERDB AREMUTUALLY EXCLUSIVE

ExplanationThe DEDB Alter utility detects that more than oneof the following control statements are specified.However, the following control statements aremutually exclusive and only one of the statements canbe specified:

• ADDAREA• ALTERAREA• REPLRAND• ALTERDB

System actionThe DEDB Alter utility terminates without performingthe requested DEDB Alter function.

System programmer response:Correct the error caused by specifying more than onemutually exclusive control statement, and rerun theDEDB Alter utility.

Module:DBFUMMS0


DFS4616E RETRY VALUE SPECIFIED ISINCORRECT

ExplanationRETRY specifies the number of times the DEDB Alterutility retries the commit process after the TIMEOUTvalue expires. The RETRY value must be NO (donot retry), YES (retry until the utility succeeds), or anumeric value from 1 through 99.


System programmer responseCorrect the RETRY value or delete it so that the defaultvalue of NO is used, and then resubmit the job.

Module:DBFUMMS0


DFS4617E RETRYWAIT VALUE SPECIFIED ISINCORRECT

ExplanationRETRYWAIT specifies the length of time that the DEDBAlter utility waits to retry the commit process after theTIMEOUT value expires. The RETRYWAIT value mustbe a 1- to 3-character numeric value from 1 - 999(which represents seconds).











System programmer responseCorrect the RETRYWAIT value or delete it so that thedefault value of 60 seconds is used, and then resubmitthe job.

Module:DBFUMMS0


DFS4618E ANOTHER DEDB ALTER UTILITYIS ALREADY RUNNING AGAINSTDEDB dedb_name

ExplanationAnother DEDB Alter utility is already running againstthe same DEDB database. Only one DEDB Alter utilitycan be active on one DEDB database in IMS data-sharing systems.


System programmer responseWait until the other DEDB Alter utility completes, andthen resubmit the job.

Module:DBFUMMS0


DFS4619E MINVERS NOT MATCHINGREQUIREMENT

ExplanationThe DEDB Alter utility cannot be run because theMINVERS value is not set to 13.1 or higher in theRECON data set. To run the DEDB Alter utility, theMINVERS value must be 13.1 or higher.


System programmer responseSet the MINVERS value in the RECON data to at least13.1 by issuing the CHANGE.RECON command, andthen resubmit the job.

Module:DBFUMMS0

Related referenceDEDB Alter utility (DBFUDA00) (DatabaseUtilities)CHANGE.RECON command (Commands)

DFS4620E DEDB ALTER VALIDATION ERROR:Cause

ExplanationThe DEDB Alter utility detected an invalid condition inthe DEDB DBD member in the staging ACB library forthe DEDB database to be altered.

In the message text, Cause is one of the followingconditions:

• DEDB ALTER REQUIRES A 2-STAGE RANDOMIZER• SAME RANDOMIZER NAME BUT ATTRIBUTE

CHANGE• SAME RANDOMIZER NAME FOUND FOR REPLRAND• ALTERAREA ONLY SUPPORTS CHANGING ONE AREA• AREA CHANGE FOUND FOR REPLRAND FUNCTION• NUMBER OF AREAS IN DEDB CHANGE FOUND• ORDER OF AREAS IN DEDB CHANGE FOUND• AREA ATTRIBUTE CHANGE NOT SUPPORTED• FIELD ATTRIBUTE CHANGE NOT SUPPORTED• SECONDARY INDEX CHANGE NOT SUPPORTED• SEGM ATTRIBUTE CHANGE NOT SUPPORTED• ATTRIBUTE CHANGE NOT SUPPORTED• STAGING ACBLIB IS EMPTY• AREA area_name DOES NOT EXIST• DEDB dedb_name MEMBER NOT IN STAGING

ACBLIB• DEDB dedbname MEMBER NOT IN STAGING

DIRECTORY• SHADOW AREA SDEP PART IS LESS FOR ALTERAREA

FUNCTION• SHADOW RANDOMIZER IS NOT REENTRANT• SEGMENT EDIT/COMPRESSION EXIT NOT

SUPPORTED• INCONSISTENCY FOUND IN DEDB AND RECON

DEFINITIONS• ADDED AREAS ARE NOT TO THE END OF DEDB

dedbname









http://www.ibm.com/support/knowledgecenter/SSEPH2_15.1.0/com.ibm.ims15.doc.cr/compcmds/ims_chgrecon.htm#ims_cr3chgrecon

System programmer responseCorrect the error in the DEDB DBD definition, rerun theDBDGEN utility and the ACBGEN utility to the stagingACB library, and then rerun the DEDB Alter utility.

Module:DBFDASP0

Related referenceDEDB Alter utility (DBFUDA00) (DatabaseUtilities)Database Description (DBD) Generation utility(System Utilities)Application Control Blocks Maintenance utility(System Utilities)

DFS4621E DEDB ALTER SYSTEM ERROR:Cause

ExplanationThe DEDB Alter utility encountered a system error.


• GET STORAGE ERROR• IMS INTERNAL ERROR• DATA SHARING ERROR


System programmer responseResubmit the DEDB Alter utility to gather diagnosticinformation: a dump of the IMS and the DEDB Alterutility regions. Contact IBM Software Support.

Module:DBFDASP0, DBFDAI60


DFS4622E DEDB ALTER ENVIRONMENTERROR: Cause

ExplanationEither the DEDB Alter utility encountered anenvironment error accessing the staging ACB libraryor the DEDB Alter was run concurrently with onlinechange. The DEDB Alter utility and online changeprocess cannot be run concurrently.


• ONLINE CHANGE PHASE IN PROGRESS• STAGING ACBLIB ACCESS ERROR• STAGING ACBLIB ALLOCATION ERROR• STAGING ACBLIB OPEN ERROR• STAGING DIRECTORY ACCESS ERROR• STAGING DIRECTORY ALLOCATION ERROR• STAGING DIRECTORY OPEN ERROR ERROR• DIRECTORY ACCESS ERROR• DIRECTORY ALLOCATION ERROR• DIRECTORY OPEN ERROR• ACTIVE ACBLIB ACCESS ERROR• ACTIVE ACBLIB ALLOCATION ERROR• ACTIVE ACBLIB OPEN ERROR• DRD OR DB QUIESCE COMMAND IN PROGRESS• AUTHORIZED SUBSYSTEM ims_name IS NOT A

MEMBER OF ALTERGRP alter_group• ACBSHR= VALUE DOES NOT MATCH


System programmer responseCorrect the environment error, and then resubmit thejob.

Module:DBFDASP0, DBFDAI60


DFS4623W NO AREA ATTRIBUTE CHANGEFOUND FOR ALTERAREAFUNCTION

ExplanationThe DEDB Alter utility was run to alter the attributesfor the area specified in area_name. However, theDEDB Alter utility detected that there were no areaattribute changes.

System actionThe DEDB Alter utility continues to perform therequested function.




http://www.ibm.com/support/knowledgecenter/SSEPH2_15.1.0/com.ibm.ims15.doc.sur/ims_dbdgen.htm#ims_dbdgen

http://www.ibm.com/support/knowledgecenter/SSEPH2_15.1.0/com.ibm.ims15.doc.sur/ims_dbdgen.htm#ims_dbdgen







System programmer responseIf area attribute change was omitted, rerun theDBDGEN utility and the ACBGEN utility to reflect thearea attribute change, and then resubmit the DEDBAlter utility.

Module:DBFDASP0


DFS4624I DEDB ALTER SHADOWRANDOMIZER randname LOADEDFOR DEDB dedbname

ExplanationThe DEDB Alter utility was run to alter an area witha randomizer change or to replace a randomizer. Theshadow randomizer specified in randname was loadedsuccessfully for DEDB dedbname.

System actionThe DEDB Alter utility continues to perform therequested function.


Module:DBFDASP0

DFS4625E DEDB ALTER SHADOWRANDOMIZER randnameUNLOADED FOR DEDB dedbname

ExplanationThe DEDB Alter utility was run to alter an area witha randomizer change or to replace a randomizer.However, the DEDB Alter utility encountered aterminating error. The shadow randomizer specifiedin randname was unloaded successfully for DEDBdedbname.


System programmer responseCorrect the error that caused the DEDB Alter utility toterminate, and then resubmit the DEDB Alter utility.

Module:

DBFDASP0

DFS4626I DEDB ALTER SHADOWRANDOMIZER randnameREPLACED ACTIVE RANDOMIZERrandname FOR DEDB dedbname

ExplanationThe DEDB Alter utility was run to alter an area witha randomizer change or to replace a randomizer,and completed successfully. The shadow randomizerspecified in randname was replaced by the activerandomizer randname for DEDB dedbname.

System actionThe DEDB Alter utility successfully completed therequested action.


Module:DBFDASP0

DFS4627E DEDB ALTER SHADOWRANDOMIZER randname LOADFAILED FOR DEDB dedbname

or

DEDB ALTER SHADOW RANDOMIZER randnameUNLOAD FAILED FOR DEDB dedbname

or

DEDB ALTER OLD ACTIVE RANDOMIZER randnameUNLOAD FAILED FOR DEDB dedbname

ExplanationThe DEDB Alter utility was run to alter an area witha randomizer change or to replace a randomizer, butterminated without performing the requested function,for one of the following reasons:

• The utility could not load the shadow randomizerspecified in randname.

• The utility could not unload the shadow randomizerspecified in randname.

• The utility could not unload the old activerandomizer specified in randname.




System actionThe DEDB Alter utility terminates with or withoutcompleting the requested action.

System programmer responseResolve the randomizer load failure and resubmit theDEDB Alter utility.

Module:DBFDASP0


DFS4628I IMS ims_name JOINED | LEFTALTERGRP alter_group

ExplanationIMS system ims_name joined or left the DEDB Alterdata-sharing group alter_group defined in DBFxxxxx bythe ALTERGRP parameter in the FASTPATH section ofthe DFSDFxxx PROCLIB member.

System actionThe IMS system joined or left the DEDB Alter DBFxxxxxdata-sharing group.


Module:DBFDAI60

DFS4629E IMS ims_name ERROR JOINING |LEAVING ALTERGRP alter_group,RC=return_code, RSN=reason_code

ExplanationIMS system ims_name encountered an error whenit joined or left the DEDB Alter data-sharing groupalter_group defined in DBFxxxxx by the ALTERGRPparameter in the FASTPATH section of the DFSDFxxxPROCLIB member.

System actionIMS encountered an error joining or leaving the DEDBAlter DBFxxxxx data-sharing group.

After an XRF takeover, the new active IMS systemwould get DFS4629E when it tried to join theALTERGRP group while the old active IMS system hadnot left the ALTERGR group yet.

After the new active IMS system join error, the newactive IMS would retry joining the ALTERGRP group atIMS system checkpoint time until it successfully joinsthe ALTERGRP group.


Module:DBFDAI60

DFS4630E AN UNEXPECTED STATUSCODE OF status_codeWAS ENCOUNTERED WHENATTEMPTING AN call_type CALLFOR SEGMENT segment_name INTHE SHADOW ADS.

ExplanationDuring DEDB Alter utility processing of the ALTERAREAfunction, a status code was returned on the indicatedcall, which was attempting to update the shadow areadata sets.

In the message text:status_code

The DL/I status code returned on the call type.call_type


• DELETE• INSERT• LOCATE• UPDATE

System actionThe DEDB Alter utility terminates without performingthe requested function.

Programmer responseContact IBM Software Support. Rerun the DEDBAlter utility with FPTRACE to collect documentationthat might be necessary to determine the problem.If the problem persists, consider using an offlinereorganization method.

Module:DBFDARD0, DBFDARI0, DBFDARR0, DBFDAR20







DFS4631E UTILITY FAILED DUE TO ANUPDATE TO UNKEYED SEGMENTsegname

ExplanationThe DEDB alter utility has specified the optionUNKEYSEG=ISRTFILA which indicates the utilityshould terminate if updates involving unkeyedsegments are made during the processing of the utility.In this case, one of the following conditions occurredduring the processing of the utility.

1. A unkeyed segment was replaced or deleted.2. An unkeyed segment with an insert rule of HERE

was inserted.

System actionThe utility terminates and the shadow area datasetsare marked in error.

System programmer responseConsider rerunning the utility during a period of lessactivity, or change the UNKEYSEG option to allowupdates to unkeyed segments during DEDB alter.

Module:DBFDAR00

DFS4632E DEDB ALTER TERMINATEDBECAUSE SEGMENT segmnameHAS AN UNKEYED PARENT

ExplanationThe DEDB alter utility has specified the optionUNKEYSEG=ISRTFILA which indicates the utilityshould terminate if updates involving unkeyedsegments are made during the processing of the utility.In this case at least one segment in the hierarchicalpath to the segment that was updated is unkeyed.

System actionThe utiltiy terminates and the shadow area datasetsare marked in error.

System programmer responseConsider rerunning the utility during a period of lessactivity, or change the UNKEYSEG option to allowupdates to unkeyed segments during DEDB alter.

Module:DBFDAR00

DFS4634I THE DEDB ALTER COPYBLK PROCESS WAS

CLEANED UP DURINGRESTART DEDB=ddddddddMODULE=aaaaaaaa

ExplanationDuring IMS restart, IMS detected that the DEDB Alterutility was running when IMS abnormally terminated.The ACTIVE ACBLIB contained an encrypted member,which IMS was able to delete.



Module:DBFEDA00

DFS4635I THE DEDB ALTER QUIESCEFLAGS WERE CLEANEDUP IN DBRC DURINGRESTART DEDB=ddddddddMODULE=aaaaaaaa

ExplanationDuring IMS restart, IMS detected that the DEDB Alterutility was running when IMS abnormally terminated.The QUIESCE in progress flag was still active in DBRC,which IMS was able to reset.



Module:DBFEDA00

DFS4636I THE DEDB ALTER ALTEREOJ FLAGS WERE CLEANEDUP IN DBRC DURINGRESTART DEDB=ddddddddMODULE=aaaaaaaa

ExplanationDuring IMS restart, IMS detected that the DEDB Alterutility was running when IMS abnormally terminated.The DEDB ALTER flag was on in the RECONS data set,which IMS was able to reset.




Module:DBFEDA00

DFS4637E RSN=06 type name FAILED TOSYNCHRONIZE WITH THE ONLINEENVIRONMENT - UTILTIY TO BETERMINATED

ExplanationThe utility failed to serialize with online activity and isbeing terminated.

In the message text, type and name can be either ofthe following combinations:AREA areaname

Indicates the name of the DEDB area.DEDB dedbname

Indicates the name of the DEDB.


A failure to serialize is caused by a thread not issuing acommit while DEDB ALTER is attempting to serializewith online activity. This is normally caused by along-running BMP or some type of conversationaltransaction that did not issue a commit due to a lack ofactivity.


Module:DBFDAQ00

DFS4637I RSN=00 type name WAS ABLE TOSYNCHRONIZE WITH THE ONLINESYSTEM SYS3

or

RSN=01 type name WAS NOT ABLE TOSYNCHRONIZE WITH THREAD yyyyyyyy SYS3

or

RSN=02 type name WAS NOT ABLE TOSYNCHRONIZE AS DEDB ALTER WAS STOPPEDSYS3

or

RSN=03 type name WAS NOT ABLE TOSYNCHRONIZE WITH THREAD yyyyyyyy SYS3

or

RSN=04 type name FAILED TO SYNCHRONIZE WITHTHE ONLINE ENVIRONMENT - RETRY ATTEMPTEDSYS3

or

RSN=05 type name TIMED OUT ATTEMPTING TOSYNCHRONIZE WITH THE ONLINE ENVIRONMENTSYS3

ExplanationIn the message text, type and name can be either ofthe following combinations:AREA areaname

Indicates the name of the DEDB area.DEDB dedbname

Indicates the name of the DEDB.

The meaning of this message depends on the reasoncode (RSN=), as follows:

Reason codeMeaning

RSN00The area or DEDB serialization process finished forarea areaname.

RSN01The area or DEDB serialization process failed.Thread yyyyyyyy was accessing area areaname anddid not issue a commit in a timely manner, allowingthe DEDB Alter utility to serialize with the thread.

RSN02The area or DEDB serialization process failed. TheDEDB Alter utility was stopped (internally or byusing the /STO RGN command) while serializationwas in progress.


RSN03The area or DEDB serialization process failed.Thread yyyyyyyy was accessing area areaname anddid not issue a commit in a timely manner, allowingthe DEDB Alter utility to serialize with the thread.

RSN04The area or DEDB serialization process failed forarea areaname. Another attempt to serialize thearea will be made because TIMEOUT or RETRYYES or both, or because RETRY retry_value wasspecified as a DEDB Alter utility input option.

RSN05The area or DEDB serialization process timed outwhile attempting to serialize the area with activethreads.

System actionIf the area or DEDB serialization is successful, theDEDB Alter utility continues processing. If the areaor DEDB serialization is unsuccessful, the DEDB Alterutility terminates processing without performing therequested DEDB Alter function.

A failure to serialize is caused by a thread not issuinga commit while the DEDB Alter utility is attempting toserialize with online activity. This is normally causedby a long running BMP, or some type of conversationaltransaction that did not issue a commit due to a lack ofactivity.


Module:DBFDAQ00

DFS4639E REQUESTED VERSION req_v_nmbrOF DEDB dedbname WAS NOTFOUND IN THE CATALOG

ExplanationIMS was unable to find the specified version of thedata entry database (DEDB) in the catalog.

In the message text:req_v_nmbr

The version number.dedbname

The name of the data entry database (DEDB).

System action:IMS cannot build the internal blocks that are requiredto provide access to prior versions of the database.Only the most recent version of the database can beaccessed.


Determine whether the catalog is online andconfigured properly. If the catalog is available,determine whether the version requested by yourapplication is in the catalog. If the catalog was notpopulated with the information about the old versionof the database, this version of the database cannot beaccessed.

Module:DBFVER00

DFS4640E SPECIFIED AREA IS NOTREGISTERED TO RECON

ExplanationThe DEDB area specified in the ALTERAREAarea_name function of the DEDB Alter utility is notregistered to DBRC in the RECON data sets. The DEDBAlter utility supports only DEDB databases that areregistered in the RECON data sets.


System programmer responseRegister the DEDB database to DBRC in the RECONdata sets, and then resubmit the DEDB Alter utility.

Module:DBFUMMS0

Related referenceDEDB Alter utility (DBFUDA00) (DatabaseUtilities)CHANGE.RECON command (Commands)

DFS4641E AT LEAST ONE AVAILABLESHADOW AREA DATA SET ANDONE AVAILABLE SHADOW IMAGECOPY DATA SET ARE REQUIRED

ExplanationAt least one shadow area data set, or the one shadowimage copy data set, is not defined or marked asavailable to DBRC in the RECON data sets.

The DEDB Alter utility requires at least one shadowarea data set and one shadow image copy data setto be defined and marked as available to DBRC in theRECON data sets for ALTERAREA function.





http://www.ibm.com/support/knowledgecenter/SSEPH2_15.1.0/com.ibm.ims15.doc.cr/compcmds/ims_chgrecon.htm#ims_cr3chgrecon

System programmer responseCorrect the data set availability error, and thenresubmit the DEDB Alter utility.

Module:DBFUMMS0


DFS4642E SPECIFIED DEDB dedb_name ISNOT REGISTERED TO RECON

ExplanationThe DEDB database specified in the DBD parameter ofthe DEDB Alter utility is not registered to DBRC in theRECON data sets.

The DEDB Alter utility supports only DEDB databasesthat are registered in the RECON data sets.


System programmer responseRegister the DEDB database to DBRC in the RECONdata sets by using the INIT.DB command, and thenresubmit the DEDB Alter utility.

Module:DBFUMMS0

Related referenceINIT.DB command (Commands)

DFS4643E PRIVATE BUFFER ALLOCATIONFAILED

ExplanationThe DEDB Alter utility cannot get private buffers forthe ALTERAREA function.


System programmer responseCorrect the private buffer allocation error, and thenresubmit the DEDB Alter utility.

Module:DBFUMMS0

Related conceptsDefining a private buffer pool using theDFSVSMxx IMS.PROCLIB member (DatabaseAdministration)Related referenceDEDB Alter utility (DBFUDA00) (DatabaseUtilities)

DFS4644E DEDB ALTER SHADOW AREA DATASET OR IMAGE COPY DATA SETOPEN FAILED

ExplanationThe DEDB Alter utility cannot open the shadow areadata set or the shadow image copy data set for theALTERAREA function.


System programmer responseFor the specific OPEN failure, locate the OPEN errormessage in the SYSLOG to take the appropriate actionfor the shadow area data set or the shadow imagecopy data set. Correct the OPEN failure, and thenresubmit the DEDB Alter utility.

Module:DBFUMMS0

DFS4645W RETRYWAIT IS IGNOREDBECAUSE RETRY IS SPECIFIED ORDEFAULTED TO NO

ExplanationThe DEDB Alter utility ignored the RETRYWAITretrywait_value control statement because the RETRYcontrol statement was specified (or defaulted to NO).The RETRYWAIT and RETRY control statements aremutually exclusive.

System actionThe DEDB Alter utility continues processing withoutusing the RETRYWAIT retrywait_value controlstatement.

System programmer responseIf you want the RETRYWAIT retrywait_value controlstatement to be used, change the RETRY controlstatement to RETRY retry_value or RETRY YES, andthen resubmit the DEDB Alter utility.




http://www.ibm.com/support/knowledgecenter/SSEPH2_15.1.0/com.ibm.ims15.doc.cr/compcmds/ims_initdb.htm#ims_cr3initdb

http://www.ibm.com/support/knowledgecenter/SSEPH2_15.1.0/com.ibm.ims15.doc.dag/ims_defprivbuffpool.htm#ims_defprivbuffpool





Module:DBFUMMS0

DFS4646I DEDB ALTER SHADOW XXX =shadow_dataset_name

ExplanationThe DEDB Alter utility runs using the ALTERAREAfunction. Message DFS4646I is issued for eachshadow area data set name and the shadow imagecopy data set name that is used for the utility.

XXX is either ADS for area data set or IDS for imagecopy data set.

System actionThe DEDB Alter utility continues processing.


Module:DBFUMMS0

DFS4648E DEDB ALTER TERMINATEDBECAUSE SORT FAILED

ExplanationThe DEDB Alter utility terminated because thesort processing encountered an error or abnormaltermination.

System actionThe DEDB Alter utility terminated without completingthe requested function.

System programmer response:Check for the cause of the error by reviewing DFSORTmessages issued on the job log or system log. Afterfixing any environmental errors, rerun the DEDB Alterutility.

Module:DBFDAU70

DFS4649E DEDB ALTER CANNOT ALLOCATETEMPORARY DATA SETS FOR SORTMESSAGES

ExplanationDuring DEDB Alter utility execution, IMS cannotallocate a temporary data set for sort messagesbecause a data set with a duplicate data set nameexists.

System actionA system output data set is allocated for sortmessages instead, and processing continues.

Programmer responseIf sort messages need to be issued in DEDB Alterutility job log, delete the duplicate data set on thevolume.

ModuleDBFDAS10

DFS4650I DEDB ALTER SHARING IMSLATE REPLY IS RECEIVED ANDIGNORED

ExplanationThe DEDB Alter utility was run in the IMS system. Asharing IMS system sent a reply to the master IMSsystem. When the master IMS received the reply, theDEDB Alter utility had already been terminated in themaster IMS. The DEDB Alter sharing IMS late replywas ignored.

System actionThe IMS where the DEDB Alter utility was run receivedand ignored the late reply from a sharing IMS system.

Module:DBFDAI60





Chapter 95. DFS messages, DFS4651E - DFS4700


DFS4651E ALTERGRP GROUP NAME IS NOTDEFINED OR INVALID, BUT DBDdedbname IS SHRLEVEL=2|3

ExplanationDuring DEDB Alter utility processing of the ALTERAREAfunction, an unexpected status code was returnedon the specified call, which attempted to updatethe shadow area data sets. The DEDB Alter utilitywas run against a DEDB database that is definedas SHRLEVEL=2 or SHRLEVEL=3 in DBRC. However,the ALTERGRP=xxxxx parameter, which defines theDEDB Alter data-sharing group, is not defined in theFASTPATH section of the DFSDFxxx PROCLIB member.

When the ALTERGRP=xxxxx is not defined, the DEDBdatabase is changed only in the local IMS system.Because the DEDB database is defined as a shareddatabase, the DEDB Alter function is not allowed.


System programmer responseAdd the ALTERGRP=xxxxx parameter to the<SECTION=FASTPATH> section of the DFSDFxxxPROCLIB member. Restart the IMS system to jointhe ALTERGRP=xxxxx DEDB Alter data-sharing group.Rerun the DEDB Alter utility.

Module:DBFDAU70


DFS4652E DEDB ALTER DATA SHARINGERROR: error AT imsid

ExplanationThe DEDB Alter utility encountered either aserialization failure, a commit failure, an initializationfailure, or a no response failure at imsid.


errorOne of the following:

• SERIALIZATION FAILED• COMMIT FAILED• ONE OR MORE DATA SHARING IMS SYSTEMS

DID NOT RESPOND• INITIALIZATION FAILED

imsidThe IMS ID of the IMS subsystem thatencountered this error.

System action:The DEDB Alter utility terminates without completingthe requested function.

System programmer response:Correct the environment error, and resubmit the job.

Module:DBFDAU70

DFS4660E DEDB ALTER WAS UNABLE TOREAD DATA FROM THE ORIGINALAREA: STATUS CODE XX RSNCODE XX RETURN CODE nnnn

ExplanationWhile attempting to read data from the area that alteris being run against, an error occurred. This might bedue to a long-running BMP holding the lock against thearea that is being altered.

Status CodeExplanations for status codes can be found on theFast Path utility status and reason codes page.

RSN CodeExplanations for reason codes can be found on theFast Path utility status and reason codes page.

Return CodeThis is for internal diagnostic purposes.

Module:DBFDAU70


DFS4661E DEDB ALTER WAS UNABLE TOCOMMIT DATA TO THE SHADOWAREA: STATUS CODE XX RETURNCODE nnnn








ExplanationDEDB Alter encountered an error when issuing asyncpoint against the new area.

Status CodeExplanations for status codes can be found on theFast Path utility status and reason codes.

Return CodeThis is for internal diagnostic purposes.

Module:DBFDAU70


DFS4662E DEDB ALTER WAS UNABLE TOCOPY DATA TO THE SHADOWAREA: STATUS CODE xx RETURNCODE nnnn

ExplanationThe DEDB Alter utility encountered an error whencopying data to the new area. This is an internal error.Contact IBM Software Support.


xxExplanations for status codes can be found in theFast Path utility status and reason codes.

nnnnThis return code is for internal diagnosticpurposes.

The DEDB Alter utility can return the following reasoncodes. You can find the reason codes within messagesin the Alter job log.Reason code

Explanation200

Cannot find a non-IOVF CI. This is an internal errorand should be reported to IBM. A U1026 abendmight also be issued.

204A bad segment code was found. This is an internalerror and should be reported to IBM. A U1026abend might also be issued.

208A bad segment code was found. This is an internalerror and should be reported to IBM. A U1026abend might also be issued.

212A thread detected a randomizer error during DEDBAlter processing. Status was set, and DEDB Alterdetected it. The shadow and active randomizers

randomized the same key to different areas, whichis not allowed.

216A thread detected an I/O error on the shadow areadata set.

Module:DBFDAU70

Related referenceFast Path utility status and reason codes(Messages and Codes)Related information1026 (Messages and Codes)

DFS4663E DEDB ALTER INITIALIZATIONFAILED

ExplanationThe DEDB Alter utility found other dependent regionsthat are holding the DEDB area on which the DEDButility works. It might also be the result of anotherinitialization failure. For more information, see the joblog.

System actionUtility job fails with return code 8.

System programmer responseCorrect any errors indicated in the job log and rerunthe utility job later.

Module:DBFUDA00


DFS4664I ALL SHADOW ADS/IDS AREMARKED UNAVAILABLE

ExplanationThe DEDB Alter utility made shadow data setsunavailable due to a severe error.


System programmer responseDelete / define / format shadow data sets. Check thereason for the error by using the SYSLOG and JOB LOG.After fixing the error, rerun the utility job.











Module:DBFUDA00


DFS4665I ALL SHADOW ADS/IDS REMAINAVAILABLE

ExplanationThe DEDB Alter utility left shadow data sets availablebecause the error did not affect shadow data sets.


System programmer responseCheck the reason for the error by using the SYSLOGand JOB LOG. After fixing the error, rerun the utilityjob.

Module:DBFUDA00


DFS4666E CONNECT SETUP FAILED

ExplanationThe DEDB Alter utility detected a logging error whileconnecting the AREA data set.


System programmer responseCheck the reason for the error by using the SYSLOGand JOB LOG. After fixing the error, rerun the utilityjob.

Module:DBFUDA00


DFS4667I MEMBER imsname LEFTALTERGRP GROUPNAME=grpname

ExplanationDuring the DEDB Alter utility is running, the sharingIMS imsname left the specified ALTERGRP.

System actionThe DEDB Alter utility terminated without completingthe requested function.

System programmer responseResubmit the job after the sharing IMS is restarted if itwas abnormally terminated. Resbmit the job anytime ifthe sharing IMS was not abnormally terminated.

Module:DBFDAU70

DFS4668I MEMBER imsname DID NOTPARTICIPATE IN DEDB ALTER FORDEDB dedbname

ExplanationWhen the DEDB Alter utility is running, the sharing IMSimsname joins the ALTERGRP at DEDB Alter committime. The sharing IMS did not participate in the DEDBAlter process for DEDB dedbname.

System actionThe DEDB Alter utility completed the requestedfunction without the sharing IMS participation.

System programmer responseMake the local online change at the sharing IMS toreflect the DEDB Alter change, if necessary.

Module:DBFDAI60

DFS4669E A FAILED IMS SUBSYSTEM HASAUTHORIZED AT LEAST ONE AREAOF DEDB dedbname

ExplanationThe DEDB Alter utility attempted to alter an area ofa DEDB database that has at least one area that isauthorized by a failed IMS subsystem.

System actionThe DEDB Alter utility is terminated withoutcompleting the requested function.

Chapter 95. DFS messages, DFS4651E - DFS4700 1285







System programmer responseResubmit the job after the failed subsystem isrestarted.

Module:DBFUMMS0

DFS4671I COULD NOT CLEAN UP AFTERDEDB ALTER DUE TO MISSINGDATA IN LOGS. ALTER TOKEN=tttttttt

ExplanationDuring IMS restart, IMS detected that the DEDB Alterutility was running when IMS abnormally terminated.Not all log records for the DEDB Alter utility run weredetected, so clean up could not be performed. Thissituation can occur when a restart checkpoint, an XRFstart checkpoint, or a FDBR start checkpoint spans theDEDB ALTER execution.

Reason codes:

01While processing the emergency restart commandagainst DEDB ALTER, the restart checkpointspanned the DEDB ALTER run. The data requiredfor the /ERE command to complete DEDB ALTERwas on log records that were logged beforethe restart checkpoint. The /ERE command wasunable to find the required data.

02During Extended Recovery Facility (XRF) tracking,an internal error occurred during DEDB ALTER ADDAREA processing. The data required for XRF tocomplete DEDB ALTER was on log records thatwere logged before the restart checkpoint. XRFwas unable to find the required data.

03During Fast Database Recovery (FDBR) tracking, aninternal error occurred during DEDB ALTER ADDAREA processing. The data required for FDBR tocomplete DEDB ALTER was on log records thatwere logged before the restart checkpoint. FDBRwas not able to find the required data.


System programmer responseThe DEDB Alter utility was not completed, so manualcleanup must be performed before the AREA can beused. Instruct USER DFSERA10 to pull all log recordsfor this IMS with the specified token to determinewhich log records were processed. To determine

which DEDB/AREA needs to be cleaned up beforeuse, compare this information with the DEDB Alterutility jobs that were active when the IMS abnormallyterminated.

Module:DBFEDA00

DFS4672E NO SHADOW AREAS EXIST forDEDB dedbname

ExplanationThe DEDB Alter utility is run with the ADDAREAfunction to add one or more DEDB areas to the endof a DEDB database. However, there are no shadowareas defined in the RECON for the dedbname DEDBdatabase.


System programmer responseDefine shadow areas for the dedbname DEDBdatabase and DEDB area data sets for each shadowarea. Format DEDB area data sets using the ACTIVEcontrol statement for the DEDB Initialization utility(DBFUMIN0). Then rerun the DEDB Alter utility.

Module:DBFUMMS0

Related tasksAdding a DEDB area online with the DEDB Alterutility (Database Administration)Related referenceDEDB Alter utility (DBFUDA00) (DatabaseUtilities)DEDB Initialization utility (DBFUMIN0)(Database Utilities)

DFS4673E NO AREA DATA SETS EXIST FORSHADOW AREA areaname FORDEDB dedbname

ExplanationThe DEDB Alter utility is run with the ADDAREAfunction to add one or more DEDB areas to the endof a DEDB database. However, there are no area datasets defined in the RECON for the areaname shadowarea for the dedbname DEDB database.



http://www.ibm.com/support/knowledgecenter/SSEPH2_15.1.0/com.ibm.ims15.doc.dag/ims_adddedbarea.htm#ims_adddedbarea






System programmer responseDefine DEDB area data sets for each shadow areafor the dedbname DEDB database. Format DEDB areadata sets using the ACTIVE control statement for theDEDB Initialization utility (DBFUMIN0). Then rerun theDEDB Alter utility.

Module:DBFUMMS0


DFS4674E NUMBER OF SHADOW AREAEXCEEDED UNDER DEDBdedbname

ExplanationThe DEDB Alter utility is run with the ADDAREAfunction to add one or more DEDB areas to the endof a DEDB database. However, the maximum of 100areas that can be added for a single execution of theDEDB Alter utility is exceeded.


System programmer responseReduce the number of areas to be added to 100 orless, and rerun the DEDB Alter utility.

Module:DBFUMMS0


DFS4675E DEDB ALTER FAILED TO ADDAREAS

ExplanationThe DEDB Alter utility is run with the ADDAREAfunction to add one or more DEDB areas to the end of aDEDB database. However, the DEDB Alter utility failedto add the areas and terminated without performingthe requested function.


System programmer responseDetermine the cause of the DEDB Alter utility failure.Correct the problem, and rerun the DEDB Alter utility.

Module:DBFUDA00


DFS4676E ANOTHER DEDB ALTER WITHADDAREA FUNCTION IS ALREADYRUNNING

ExplanationThe DEDB Alter utility is run with the ADDAREAfunction to add one or more DEDB areas to the endof a DEDB database. However, there is already anotherDEDB Alter utility running with the ADDAREA function.The DEDB Alter utility terminated without performingthe requested function, because only one DEDB Alterutility running with the ADDAREA function can be runin an IMSplex at a time.


System programmer responseWait until the DEDB Alter utility that is already runningcompletes, and rerun the DEDB Alter utility.

Module:DBFUMMS0





















DFS4677E DEDB ALTER DOES NOT SUPPORTDBRC REUSE ATTRIBUTE FORAREA XXXXXXXX

ExplanationDBRC detected the REUSE attribute on the DEDBarea (XXXXXXXX) specified by the DEDB Alter utility(DBFUDA00) ALTERAREA control statement.

System actionThe DEDB Alter utility terminates with RC=8 withoutcompleting the requested function.

System programmer responseChange the REUSE attribute of the area that the DEDBAlter utility is to be executed on to NOREUSE. Changethe attribute by issuing the command CHANGE.DBDSDBD (name) AREA (name) NOREUSE.

Module:DBFUDA00

Related referenceDEDB Alter utility (DBFUDA00) (DatabaseUtilities)CHANGE.DBDS command (Commands)

DFS4678E DBRC ENCOUNTERED ERRORSRECORDING THE IMAGE COPYCREATED BY DEDB ALTER

ExplanationWhile attempting to record a user image copy createdby DEDB Alter utility (DBFUDA00) processing, DBRCencountered a severe error.

System actionThe DEDB Alter utility terminates with RC=8. TheALTER IN PROGRESS status remains on for the DEDB.

System programmer responseRefer to any supporting DBRC messages and addressthe problems as appropriate. Because the DEDB Alter

utility terminated abnormally, the alter status of theDEDB will need to be reset before the utility can be runagain.

1. Reset the ALTER IN PROGRESS flag for the DEDBby issuing the CHANGE.DB DBD(name) NOALTERcommand.

2. Issue the CHANGE.ADS command to mark theshadow ADSs as unavailable.

3. Reformat the shadow ADSs.4. Run the DEDB Alter utility again.

Module:DBFUDA00

Related referenceDEDB Alter utility (DBFUDA00) (DatabaseUtilities)CHANGE.DB command (Commands)

DFS4679E DEDB ALTER FAILED TO LOADMAIN PROGRAM

ExplanationThe DEDB Alter utility failed to load DBFDAU70 fromthe STEPLIB.

System actionThe DEDB Alter utility terminates with RC=8.

System programmer responseEnsure that the libraries on STEPLIB are accessibleand that the DBFDAU70 library is properly built.


DFS4682I DEDB ALTER SHADOW AREAareaname ADS = area_dsn

or

DEDB ALTER SHADOW AREA areaname

ExplanationThe DEDB Alter utility is run with the ADDAREAfunction to add one or more DEDB areas to the endof a DEDB database.

For the first version of the message, the DEDB areato be added is areaname and the area data set name










http://www.ibm.com/support/knowledgecenter/SSEPH2_15.1.0/com.ibm.ims15.doc.cr/compcmds/ims_chgdbds.htm#ims_cr3chgdbds



http://www.ibm.com/support/knowledgecenter/SSEPH2_15.1.0/com.ibm.ims15.doc.cr/compcmds/ims_chgdb.htm#ims_cr3chgdb



is area_dsn. This message is issued in the DEDB Alterutility job output.

For the second version of the message, the DEDB areato be added is areaname. This message is issued in theIMS job output.

System actionThe DEDB Alter utility continues to process therequested DEDB Alter function.


Module:DBFDAU70, DBFDASP0

Related tasksAdding a DEDB area online with the DEDB Alterutility (Database Administration)Related referenceControl statements for the DEDB Alter utility(DBFUDA00) (Database Utilities)

DFS4683I DEDB ALTER ADDED AREAareaname for DEDB dedbname

Explanation:The DEDB Alter utility is run with the ADDAREAfunction to add one or more DEDB areas to the endof a DEDB database. The DEDB area to be added isspecified as areaname, and the DEDB data set name isspecified as dedbname.

System actionThe DEDB Alter utility continues to process therequested DEDB Alter function.


Module:DBFDASP0


DFS4684I DEDB ALTER SHADOWSEGMENT EDIT/COMPRESSIONEXIT exitname LOADED FORSEGMENT segmname FOR DEDBdedbname

Explanation:The DEDB Alter utility was run to alter an area, toadd an area, or to replace a randomizer, by adding aSegment Edit/Compression exit routine for segment

segmname. The shadow Segment Edit/Compressionexit routine exitname has been loaded successfully forsegment segmname for DEDB database dedbname.

System actionThe DEDB Alter utility continues to perform therequested DEDB Alter function.


Module:DBFDASP0


DFS4685I DEDB ALTER SHADOWSEGMENT EDIT/COMPRESSIONEXIT exitname UNLOADED FORSEGMENT segmname FOR DEDBdedbname

Explanation:The DEDB Alter utility was run to alter an area, toadd an area, or to replace a randomizer, by adding aSegment Edit/Compression exit routine for segmentsegmname. The shadow Segment Edit/Compressionexit routine exitname has been unloaded successfullyfor segment segmname for DEDB database dedbname.


System programmer response:Correct the error that caused the DEDB Alter utility toterminate, and rerun the DEDB Alter utility.

Module:DBFDASP0


DFS4686E DEDB ALTER SHADOWSEGMENT EDIT/COMPRESSIONEXIT exitname LOAD FAILED FORSEGMENT segmname FOR DEDBdedbname

Explanationor












DEDB ALTER SHADOW SEGMENT EDIT/COMPRESSION EXIT exitname UNLOAD FAILED FORSEGMENT segmname FOR DEDB dedbname

ExplanationThe DEDB Alter utility was run to alter an area, toadd an area, or to replace a randomizer, by adding aSegment Edit/Compression exit routine.

The first version of the message is issued when theDEDB Alter utility cannot load the shadow SegmentEdit/Compression exit routine exitname for segmentsegmname for DEDB database dedbname.

The second version of the message is issued when theDEDB Alter utility cannot unload the shadow SegmentEdit/Compression exit routine exitname for segmentsegmname for DEDB database dedbname.


System programmer response:Correct the error that caused the failure to load orunload the Segment Edit/Compression exit routine,and rerun the DEDB Alter utility.

Module:DBFDASP0


DFS4687E ERROR PROCESSING SYNCPROGRAM SWITCH - details

ExplanationAn error occurred during synchronous program switchprocessing for a DL/I ICAL call.


detailsA summary of the underlying cause of the error.This description corresponds with the return codeissued by the IMS module that threw the error andis one of the following:INTERNAL POST FAILED, RC=

IMS module DFSYSCS0 examined the PSTfields and determined that it cannot post theICAL for the synchronous program switch.IMS issues this error message to the systemconsole and MTO with the return code fromDFSYSCS0. IMS also creates an X'67D0' logrecord with the error details.

System action:

IMS attempts to issue a timeout for this synchronousprogram switch request.

Programmer response:Collect the X'6701' and X'67D0' log records andcontact IBM Software Support.

Module:DFSYTIB0 or DFSYSCS0

Related referenceFormat of X'67' log record (Diagnosis)

DFS4688E ERROR PROCESSING ICAL -details

ExplanationAn error occurred in the synchronous calloutprocessing for DL/I ICAL.

In the message text:details

A short summary of the reason why IMS failedto process this ICAL. details corresponds with thereturn code issued by an IMS module, and mightbe one of the following values:

• INTERNAL POST FAILED, RC= rc

IMS module DFSYSCS0 examined the programspecification table (PST) fields and determined that itcannot post ICAL. IMS issues this error message tosystem console and MTO with RC from the DFSYSCS0.IMS also generates a 67D0 log record to show theerror information.

System actionThe IMS timer routine later tries to timeout this ICAL.

System programmer response:Prepare the 6701 and 67D0 log records and contactIBM Software Support.

Module:DFSYSCS0, DFSYMEM0

DFS4690I DEDB ALTER DATABASE STARTEDFOR DEDB xxxxxxxx: Text

ExplanationThe ALTERDB control statement was specified to addfields to existing free space in a segment for DEDBxxxxxxxx.

In the message text, Text is one of the followingconditions:

• ADD NEW FIELDS

System action:None.




http://www.ibm.com/support/knowledgecenter/SSEPH2_15.1.0/com.ibm.ims15.doc.dgr/ims_x67_format_logrecord.htm#ims_x67_format_logrecord


Module:DBFDASP0


DFS4691I DEDB ALTER DATABASECOMPLETED FOR DEDB xxxxxxxx

Explanation:The add new fields function for DEDB xxxxxxxxcompleted successfully.

System action:None.


Module:DBFDASP0

Related referenceDEDB Alter utility (DBFUDA00) (DatabaseUtilities)Control statements for the DEDB Alter utility(DBFUDA00) (Database Utilities)

DFS4692E DEDB ALTER DATABASE FAILEDFOR DEDB xxxxxxxxorDEDB ALTER DATABASE FAILEDFOR DEDB xxxxxxxx: Text

ExplanationThe ALTERDB function failed to add new fields toDEDB xxxxxxxx.

In the message text, Text is one of the followingconditions:NEW FIELD OVERLAYS EXISTING FIELD

Issued when the new fields overlay existing fields.EXISTING FIELD CHANGE NOT SUPPORTED

Issued when the location or length of existingfields is changed.

NO ALTERDB ATTRIBUTES CHANGEIssued when no new fields are found.

FAILED TO GET WORKAREAIssued when work storage could not be obtainedfor the new fields.

System action:The DEDB Alter utility ends with RC=8

System programmer responseIn the DBDGEN utility input that is used to alter theDEDB DBD definitions to the staging ACBLIB, ensurethat all of the following conditions are met. Then, rerunthe DEDB Alter utility by using the ALTERDB function.

• New fields do not overlay each other or overlayexisting fields, or both.

• Existing fields are not modified.• Attributes are changed for the ALTERDB function.• Sufficient space exists for the new fields.

If message DFS4692E does not contain Text, checkassociated error messages to identify the correctiveaction.

Module:DBFDASP0, DBFDAU70













DFS4701I THE DEDB ALTER MOLC PROCESSWAS COMPLETED BY THETRACKING IMS, DEDB=ddddddddMODULE=DBFEDA00

ExplanationDuring XRF or FDBR tracking of a DEDB ALTER withACBSHR=N, the required updates to the ACBLIB fromthe STAGING ACBLIB completed successfully. This isan informational message only.

System actionNone

Programmer responseNone

Module:DBFEDA00

DFS4703I DEDB ALTER COULD NOTFIND THE SHADOW DEDB,DEDB=dedbname RC=nnnnnnnnRSN=cccc MODULE=DBFEDA00

ExplanationDuring extended recovery facility (XRF) or FastDatabase Recovery (FDBR) region tracking of a DEDBAlter utility processing, the DEDB shadow area dataset cannot be found. This is because the DEDB Alterutility fails to open the ACBLIB staging library to obtainthe definition of the shadow area data set.


The return code from the DEDB Alter utility, whichcan be one of the following codes:00000008

Parameter error.00000010

Environment error.00000014

System error.cccc

The reason code for the error, which can be one ofthe following opitons:

64Getting storage failure.

90Internal error.

ADDynamic deallocation failure.

C1Database not found.

CFParameter value conflict.

120Empty ACBLIB staging library.

130ACBLIB staging library allocation failure.

132Opening ACBLIB staging library failure.

135ACBLIB staging library I/O error.

1FDIMS staging directory data set I/O error.

235Empty staging directory.

System actionThe XRF or FDBR region continues tracking.

Output destinationThe systems console

System programmer responseEnsure that the DEDB definition in the ACB library ofthe XRF or FDBR region is consistent with that in theactive ACB library.

Module:DBFEDA00


DFS4704E THE SYSIN DATA SET FAILED TOOPEN.




ExplanationThe MVS open operation failed for the IMS CatalogAlias Names utility (DFS3ALI0) SYSIN data set.


User response:Determine the underlying problem with the data set,and submit the job again.

Module:DFS3ALI0

DFS4705E ALIAS THAT BEGINS WITH nnnnIS INVALID.

ExplanationAn alias that approaches column 72 of the SYSINrecord is invalid.


User response:Examine the alias near column 72 of the SYSINrecord. Make sure that it is a 4-character alias that isalphanumeric and does not exceed column 72. Updatethe SYSIN control card and submit the job again.

Module:DFS3ALI0

DFS4706E ALIAS nnnn DOES NOT BEGINWITH AN ALPHA CHARACTER.

ExplanationThe nnnn alias prefix must have an alphabeticcharacter in the first position.


User response:Update the SYSIN control card and submit the jobagain.

Module:DFS3ALI0

DFS4707E ALIAS nnnn CONTAINS NON-ALPHANUMERIC CHARACTER.

ExplanationThe nnnn alias prefix must contain alphanumericcharacters in the second through fourth position.



Module:DFS3ALI0

DFS4708E NUMBER OF ALIASES IN SYSINEXCEEDED 250.

ExplanationThe utility allows up to 250 aliases in the SYSIN dataset.



Module:DFS3ALI0

DFS4709E ALIAS THAT BEGINS WITH nnnnHAS MORE THAN 4 CHARACTERS.

ExplanationAn alias with more than 4 characters was detected.



Module:DFS3ALI0

DFS4710E ERROR FOUND ON SYSIN RECORD.

ExplanationThe utility could not run because of an error in theSYSIN data set as indicated by an accompanied errormessage.




Module:DFS3ALI0

DFS4711E THE SYSLIN DATA SET FAILED TOOPEN.

ExplanationThe MVS open operation failed for the IMS CatalogAlias Names utility SYSLIN data set.



Module:DFS3ALI0

DFS4712E DDL [GET STORAGE | LOAD | DFSDFREAD] FAILURE OCCURRED

ExplanationThe DDL CREATE function encounters a system errorduring Auto Import or Auto Create processing. Thestatus for the new resources is different depending onwhether the DDL system failure occurs before or afterAuto Import processing. The following are the possiblescenarios:

• Scenario 1: If the DDL system failure occurs beforeAuto Import processing, the new definitions from theDDL CREATE job remain pending in the IMS Catalog.

• Scenario 2: If the DDL system failure occurs afterAuto Import processing, the new resources from theDDL CREATE job is created and activated in the IMSsystems and catalog.

System actionIn scenario 1, the DDL CREATE function for AutoImport or Auto Create processing terminates, butthe requested function is not complete. The newdefinitions from DDL CREATE remain in the IMScatalog in "Pending" state.

In scenario 2, the DDL CREATE function for AutoImport or Auto Create processing terminates. TheAuto Import function is completed to create andactivate the new resources in the IMS systems andIMS catalog.

System programmer responseFor scenario 1, perform all the necessary steps tocreate and activate the new resources manually by

using the new definitions in the IMS catalog in the"Pending" state as required by the IMPORT DEFNcommand. See IMPORT DEFN SOURCE(CATALOG)command (Commands)

For scenario 1 and 2, perform all the steps thatare required for data set creation for the databaseresources newly created by DDL. See Automationoptions for DDL CREATE statements (DatabaseAdministration)

Module:DFS3DD00, DFS3DD40, DFS3DD60

DFS4713E CYLINDERS, TRACKS ORDATACLAS REQUIRED IN PROCLIBTO CREATE DEDB SDEP DATA SETS

ExplanationThe DDL CREATE function has successfully auto-imported the newly DDL created resources to the IMSsystem and catalog.

During the creation of the data set, the DDL data setcreation failed because the CYLINDERS or TRACKSkeyword is required when DATACLAS is not specifiedin <SECTION=DDL> of DFSDFxxx PROCLIB member forDEDB with SDEP.

System actionThe DDL data set creation stops processing this DEDBwithout completing the requested function and startsprocessing the next DEDB.

System programmer responsePerform the steps to create data sets for the DDLcreated databases manually.

For DDL CREATE DATABASE data set creation,correct the <SECTION=DDL> of DFSDFxxx PROCLIBmember. For non-SMS managed data sets, specify theCYLINDERS or TRACKS keyword. If both CYLINDERSand TRACKS keywords are specified, the CYLINDERSkeyword is used. For SMS-managed data sets, specifythe DATACLAS keyword.

When PREALLOC=Y is specified for Fast Path DEDBADS with SDEP defined and the ADS is pre-allocated,you must specify the following parameters:

• CYLINDERS= or TRACKS=• SMS class: DATACLAS= or STORCLAS= orMGMTCLAS=

Module:DFS3DD00

DFS4714E VOLUME IS NEEDED WHENSTORCLAS IS NOT SPECIFIED




http://www.ibm.com/support/knowledgecenter/SSEPH2_15.1.0/com.ibm.ims15.doc.dag/ims_imspldbdes_ddl_create_ext.htm#ims_imspldbdes_ddl_create_ext




During the creation of the data set, the DDL dataset creation failed because the VOLUME keywordis required when STORCLAS is not specified in<SECTION=DDL> of DFSDFxxx PROCLIB member.

System actionThe DDL data set creation terminates withoutcompleting the requested function.


For DDL CREATE DATABASE data set creation, correctthe <SECTION=DDL> of DFSDFxxx PROCLIB member.For non-SMS managed data sets, specify the VOLUMEkeyword. For SMS-managed data sets, specify theSTORCLAS keyword.

Module:DFS3DD00

DFS4715E AREA DATA SET cluster_nameALLOCATION FAILED


During the creation of the data set, the DDL data setcreation failed to allocate the DEDB Area data setusing cluster_name.



Refer to accompanying IDC messages for allocationdetails.

Module:DFS3DD00

DFS4716E DDL SECTION IS NOT FOUND INDFSDFxxx PROCLIB

ExplanationAUTOCREATE=YES in <SECTION=CATALOG>: TheDDL CREATE function detects that <SECTION=DDL>is not found in DFSDFxxx member of the IMSPROCLIB data set.<SECTION=DDL> is required forAUTOCREATE=YES.

System actionThe DDL CREATE function for Auto Create processingterminates without completing the requested function.The new definitions from DDL CREATE remain pendingin the IMS Catalog.

System programmer response1. Perform all the necessary steps to create and

activate the new resources by manually using thenew definitions that are pending in the IMS catalogas required by the IMPORT DEFN command.See IMPORT DEFN SOURCE(CATALOG) command(Commands)

2. Perform all the steps that are required for dataset creation for the database resources that arecreated by DDL. Automation options for DDLCREATE statements (Database Administration)

For future DDL CREATE DATABASE data set creation,add <SECTION=DDL> to DFSDFxxx PROCLIB member.

Module:DFS3DD00

DFS4716I DDL SECTION IS NOT FOUND INDFSDFxxx PROCLIB

ExplanationAUTOCREATE=NO in <SECTION=CATALOG>: the DDLCREATE function detects that <SECTION=DDL> isnot found in the DFSDFxxx member of the IMSPROCLIB data set. <SECTION=DDL> is not required forAUTOCREATE=NO.

System actionThe DDL CREATE function continues to process therequested function.

System programmer response• If the DDL CREATE function for Auto Import

processing completes successfully, no action isrequired.

• If the DDL CREATE function for Auto Importprocessing terminates without completing therequested function, the new definitions from DDLCREATE remain pending in the IMS catalog. Perform






all the necessary steps to create and activate thenew resources manually by using the new definitionsthat are pending in the IMS catalog as required byusing the IMPORT DEFN command. See IMPORTDEFN SOURCE(CATALOG) command (Commands).

Module:DFS3DD00

DFS4717E DDL SECTION PARAMETER ISINVALID

ExplanationThe DDL Auto Import or Auto Create processingdetects an invalid parameter in <SECTION=DDL> ofthe DFSDFxxx member of the IMS PROCLIB data set.

The DDL section parameter in error is identified inBPE0003D messages.

System actionThe DDL CREATE function for Auto Import or AutoCreate processing terminates without completing therequested function.

The new definitions from the DDL CREATE functionremain pending in the IMS catalog.

System programmer responseResolve <SECTION=DDL> parameter errors. Performall the necessary steps to create and activate newresources manually by using the new definitionsthat are pending in the IMS catalog as required bythe IMPORT DEFN command. See IMPORT DEFNSOURCE(CATALOG) command (Commands).

Module:DFS3DD00

DFS4718E AREA areaname REGISTRATIONFAILED


During the creation of the data set, the DDL data setcreation failed because the database registration tothe DBRC failed for the newly DDL created database.


System programmer responseCorrect the DBRC database registration error andperform the database registration to DBRC manually.

Module:DFS3DD00

DFS4719E TYPEFP ONLY CREATE DEDBAREAS

Explanation:An invalid type was specified for the DSN= orDSNDATA= parameter in the DDL section of theDFSDFxxx member of the IMS.PROCLIB data set.

System action:Processing for the DDL statement that was issued tocreate the data set is terminated.

System programmer responseUse one of the following methods to create the DEDBarea data set:

• Create the DEDB area data set manually by using theIMS generation utilities.

• If you use the CREATE DATABASE DDL statementto create the DEDB area data set, in the DDLsection of the DFSDFxxx member, correct the DDLtype to specify TYPEFP in the DSN= or DSNDATA=parameter.

Module:DFS3DD00

DFS4720I DRA open thread option active/inactive

ExplanationThis message indicates whether DRA open threadsupport is active or inactive.

When DRA open thread support processing is active,the DRA does not attach dedicated IMS DRA threadtask control blocks (TCBs). Instead, the DRA usesCICS TCBs that are intended for increased parallelismwithin the CICS/DRA environment.

DRA open thread support is active if it is enabled bythe OPENTHRD=CCTL option and uses CICS Version4.2 or later.

DFS4721I DRA monitoring of thread CPUusage is active/inactive

ExplanationThe DRA will (active) or will not (inactive) monitorand report to IMS, the accumulated CPU usagestatistics related to DRA threads. The time is reportedin IMS 07 log record DLRTIME field, and to the






CCTL in DRA thread statistics field PAPLCTM1.This option is set through the DFSPRP parameter,TIMETHREADCPU. Thread CPU usage timing can beinactive only when Open Thread is enabled (See theOPENTHRD parameter). When monitoring is inactive(TIMETHREADCPU=NO), timers are not set, and theaccumulated time of 0 (zero) is reported to IMS atthread completion. It is recommended that the usagemonitoring be turned off only if you know that:

• CCTL accumulates the thread time that includes IMSprocessing time, or

• IMS 07 log record DLRTIME field is not used todetermine thread CPU usage time

System action

System programmer response

Module:

DFS4722I CTL RGN U0785 DUE TO SsssUuuuu AND A CRITICAL WAITNOTCOMPLETING IN MPP|JMP|BMP|JBP|IFP|DBT nnnnnnnn

ExplanationAn abend occurred in a dependent region thread whilethe thread was in system critical wait.

sssRepresents the system abend of the dependentregion abend code. If the abend is a user abend,the system code is represented by S000.

uuuuRepresents the user abend of the dependentregion abend code. If the abend is a system abend,the user code is represented by 0000.

nnnnnnnnJob name of the terminating dependent region.

ModuleDFSASK00, DFSDTTA0

DFS4723A SETI NOT ALLOWED DUE TOFPSISETI=N

ExplanationThe FPSISETI=N statement is specified in theDFSDFxxx member of the IMS.PROCLIB data set.Therefore, the Set Index Maintenance Off (SETI)control statement on the //DFSCTL DD statement doesnot take effect.

System actionThe maintenance suppression job terminates with userabend code 1060 (U1060).

Output destinationThe master terminal

Programmer responseChoose one of the following actions:

• Remove the SETI statement and resubmit the job.• Change FPSISETI=N to FPSISETI=Y, restart IMS,

and resubmit the job.• Remove the FPSISETI statement , restart IMS, and

resubmit the job.

ModuleDBFCPY00

Related referenceFASTPATH section of the DFSDFxxx member(System Definition)Set Index Maintenance Off (SETI) controlstatement (System Definition)

DFS4725I CHANGE DATA CAPTURE FORUPDATES MADE BY jobname WILLBE SUPPRESSED.

ExplanationWherejobname

The job name of a CCTL or ODBM address space.

Database or database segment updates made by theCCTL or ODBM job jobname are not captured, even ifa Data Capture exit routine is specified on the EXIT=parameter of the DBD for the database. The updatesare not captured despite any DBD specificationsbecause the CCTL or ODBM job jobname is specifiedon the SUPPDCAPNAME= parameter, which is in theDATABASE section of the DFSDFxxx member.

System action:Processing continues without capture of the databaseor database segment updates made by the CCTL orODBM job jobname.

Output destination of message:The message is sent to the z/OS system console.

System programmer response:No user action required if this was the intendedbehavior. Otherwise, update the SUPPDCAPNAME=parameter in the DATABASE section of the DFSDFxxx




http://www.ibm.com/support/knowledgecenter/SSEPH2_15.1.0/com.ibm.ims15.doc.sdg/ims_seti_control_statement.htm#ims_seti_control_statement

http://www.ibm.com/support/knowledgecenter/SSEPH2_15.1.0/com.ibm.ims15.doc.sdg/ims_seti_control_statement.htm#ims_seti_control_statement

member and restart IMS. Or, change the CCTL orODBM job name so that change capture is notsuppressed.

Module:DFSDASI0

Related referenceDATABASE section of the DFSDFxxx member(System Definition)

DFS4730E AREA DATA SET dataset_nameFORMAT FAILED


During the creation of the data set, the DDL dataset creation failed because the DEDB Area dataset initialization failed for the newly DDL createddatabase.


System programmer responsePerform the steps to format data sets and register thedatabase for the DDL created databases manually.

Module:DFS3DD00

DFS4731E UNABLE TO OBTAIN STORAGE FOR[PARM|ALLOC|UNALLOC]


During the creation of the data set, the DDL dataset creation failed because the DEDB Area data setinitialization failed to get work storage.



Module:

DFS3DD90

DFS4732E DYNAMIC [ALLOCATION|UNALLOCATION] FAILED RC=xxRS=yyyy FOR dataset_name


During the creation of the data set, the DDL dataset creation failed because the DEDB Area dataset initialization failed to dynamically allocate orunallocate Area data set.xx

DYNALLOC return code.yyyy

DYNALLOC reason code.



Module:DFS3DD90

DFS4733E FORMATTER LOAD FAILED RC=xx


During the creation of the data set, the DDL dataset creation failed because the DEDB Area data setinitialization failed to load DBFUMIN0.xx

return code from IMODULE LOAD call.



Module:DFS3DD90


http://www.ibm.com/support/knowledgecenter/SSEPH2_15.1.0/com.ibm.ims15.doc.sdg/ims_dfsdfxxx_proclib_database.htm#ims_dfsdfxxx_proclib_database

http://www.ibm.com/support/knowledgecenter/SSEPH2_15.1.0/com.ibm.ims15.doc.sdg/ims_dfsdfxxx_proclib_database.htm#ims_dfsdfxxx_proclib_database

DFS4734E FORMATTER FAILED RC=xx


During the creation of the data set, the DDL dataset creation failed because the DEDB Area data setinitialization failed to format AREA data set.xx

return code from DBFUMIN0


System programmer responseSee DEDB Initialization utility (DBFUMIN0) (DatabaseUtilities) for the meaning of the return code andDBFUMIN0 messages in SYSPRINT output.

Perform the steps to format data sets and register thedatabase for the DDL created databases manually.

Module:DFS3DD90

DFS4735I cluster_name IS ALLOCATED

ExplanationA data set is allocated by using DDL.

In the message text:cluster_name

The name of VSAM cluster.



Module:DFS3DD40

DFS4736I DATA COMPONENT NAME isdata_component_name

ExplanationIf the DSNDATA= parameter is specified in the DDLsection of DFSDFxxx member of the IMS.PROCLIBdata set, this message follows message DFS4735I toshow the data component name. If the DSNDATA=parameter is not specified, this message is not issued.

Instead, the data component name is shown in theprevious IDC0512I message.

In the message text:data_component_name

The name of VSAM data component name



Module:DFS3DD40

Related information“DFS4735I” on page 1300cluster_name IS ALLOCATED

DFS4741I PSB psb_name IS UPDATEDIN THE CATALOG AND THEDIRECTORY. PST pst_name

ExplanationThe program view (PSB) was added to both thecatalog database and the directory data set by anADD PROGRAMVIEW DDL statement, or changed inboth the catalog database and the directory data setby DROP PROGRAMVIEW and CREATE PROGRAMVIEWstatements.


The name of the program view (PSB) that wasadded or changed.




Module:DFSMOLS0

DFS4742E DBD dbd_name2 MUST BECHANGED TO REMOVE THELOGICAL TIE TO A DELETED DBDdbd_name1. PST pst_name




ExplanationThe database dbd_name1 cannot be deleted bya DROP DATABASE DDL statement because thedatabase dbd_name1 has a logical tie to the databasedbd_name2, and the database dbd_name2 is notdeleted in this work unit.

In the message text:dbd_name1

The name of the database that is to be deleted bythe DROP DATABASE DDL statement.

dbd_name2The name of the database that has a logical tie todbd_name1 but is not deleted in this work unit.


System actionThe database dbd_name1 is not deleted from thedirectory.

User responseIf the database dbd_name2 is still needed, submitan ALTER DATABASE DDL statement to remove thereference to the database dbd_name1 from the DBD.

If the database dbd_name2 is no longer needed,submit a DROP DATABASE DDL statement to deletethe DBD.

Module:DFSOLC70

DFS4743I DBD dbd_name IS DELETED FROMTHE STAGING DATA SET. PSTpst_name

ExplanationDatabase dbd_name has been deleted from both theIMS catalog database and the IMS directory data set.

System actionIMS completed the automatic activation of DDLstatement successfully.

System programmer responseNone.

Module:DFSOLC70

DFS4744E RM errortypeERROR, RSCNAME=rscname

RSCTYPE=rsctype CC=ccCCTEXT=cctext

ExplanationThis message is issued after message DFS4401E toprovide additional information for an RM error thatoccurred.

If the RM error occurred during IMS autoexportto the IMSRSC repository, the autoexport was notsuccessful. The type of error that occurred is indicatedin message DFS4744E. The RM return and reasoncode can be found in the second and third words ofthe ERRORTEXT= field of message DFS4401E. For adescription of the RM return and reason code, see theCSLRRR macro.

In the message text:errortype

Indicates the type of RM error that occurred.

errortype can have the following value:

• RESOURCE VALIDATION

rscnameIndicates the name of the resource that was beingprocessed when the RM error occurred.

rsctypeIndicates one of the following types of resourcesthat was being processed when the RM erroroccurred:

• DB• DBDESC• LTERM• MSLINK• MSNAME• MSPLINK• PGM• PGMDESC• RTC• RTCDESC• TRAN• TRANDESC

ccIndicates the four character IMS completion codethat represents the error. For a list of IMScompletion codes, see the DFSCMDRR macro.

cctextIndicates completion code text that explains theerror.

System action:


If messages DFS4401E and DFS4744E are issuedduring autoexport processing, IMS continuesprocessing even though the autoexport failed. Ifmessages DFS4401E and DFS4744E are issued whenautoexport is processed during IMS shutdown, IMSshutdown is aborted.

System programmer responseComplete one of the following actions:

• If an RM error occurs during autoexport processingand the autoexport fails, after the error isresolved, issue the EXPORT DEFN TARGET(REPO)OPTION(CHANGESONLY) command to manuallyexport the new or updated MODBLKS resourcedefinitions. Or, you can wait for the next autoexportto export the new or updated MODBLKS or MSCresource definitions, or both.

• If messages DFS4401E and DFS4744E are issuedwhen autoexport is processed during IMS shutdown,you must either enable the resources to besuccessfully exported to the repository or disablethe repository for IMS to shut down successfully.

Module:DFSXP000"

Related referenceEXPORT command (Commands)Related information“DFS4401E” on page 1209RM requestname ERROR, RC=rc RSN=rsnERRORTEXT=errortext

DFS4745I PSB psb_name IS DELETED FROMTHE STAGING DATA SET. PSTpst_name

ExplanationPSB psb_name has been deleted from the stagingdata set as part of the DDL DROP program viewsprocessing.



Module:DFSOLC70

DFS4746I PSB psb_name IS DELETED FROMTHE STAGING DATA SET. IT

REFERENCED A DELETED DBDdbd_name PST pst_name

ExplanationPSB psb_name referenced a deleted databasedbd_name and it has been deleted from the stagingdata set as part of the DDL DROP database processing.



Module:DFSOLC70

DFS4747E AUTOMATIC IMPORT FAILED FORRESOURCE=resourcename AS ANLNB / RCNT / SMB BECAUSE ITALREADY EXISTS AS AN LNB /RCNT / SMB

ExplanationAutomatic import from the IMSRSC repository failedfor the resource named resourcename as messagedestination resource type LNB / RCNT / SMB, becauseit already exists with the same name as a differentmessage destination resource type of LNB / RCNT /SMB. Message destination types of resources includeremote logical terminals (LTERMs), transactions, andMSC logical link paths (MSNAMEs).

In the message text:resourcename

Indicates the name of the resource for which theerror occurred.

The message destination type of resource can be oneof the following:LNB

MSC logical link path (MSNAME) control blockRCNT

MSC remote LTERM control blockSMB

Transaction control block

System actionIMS cold start continues with automatic importwithout creating the resource resourcename for thedifferent message destination resource type of LNB /RCNT / SMB. Instead, the resource resourcename of


http://www.ibm.com/support/knowledgecenter/SSEPH2_15.1.0/com.ibm.ims15.doc.cr/imscmds/ims_export.htm#ims_cr1export

the original message destination resource type ofLNB / RCNT / SMB is automatically imported.

System programmer responseAfter automatic import and IMS cold start havecompleted, do all of the following tasks to preventmessage DFS4747E from being issued at the next IMScold start:

• Determine which message destination resource type(LTERM, MSNAME, or transaction) you want to definefor resource resourcename.

• For every message destination resource typethat you do not want defined for resourceresourcename, issue the DELETE DEFNTARGET(REPO) TYPE(LTERM | MSNAME |TRAN) NAME(resourcename) command.

• If the message destination resource type you wantto define for resource resourcename failed duringautomatic import, either cold start IMS again, ordelete the resource locally and create it again locallywith the correct message destination resource type.

Module:DFSIP300

DFS4748E STOW ERROR, NO STORAGEAVAILABLE

ExplanationNo more virtual storage was available for a STOWmacro to update the PDSE directory of the IMS Catalogdirectory.

This error is in effect only when ACBMGMT=CATALOG isspecified in either the DFSDFxxx PROCLIB member orthe equivalent DFS3CDX0 user exit to enable the IMSmanagement of ACBs.

Programmer responseCorrect the condition that led to the storage error, andrerun the program. Consider increasing the region sizeon the JOB card.

If the problem persists, contact IBM service.

Module:DFSUAMB1

DFS4749E STOW ERROR RC = xxxxxxxx

ExplanationAn error occurred during a STOW macro update to thePDSE directory of the IMS Catalog directory.

This error is in effect only when ACBMGMT=CATALOG isspecified in either the DFSDFxxx PROCLIB member orthe equivalent DFS3CDX0 user exit to enable the IMSmanagement of ACBs.

Programmer responseCorrect the condition that led to the STOW error, andrerun the program.

For more information about STOW completion codes,see z/OS DFSMS Macro Instructions for Data Sets -non-VSAM Macro Instructions.

Module:DFSUAMB1

Related referencez/OS: Return and reason codes for the DFSMSSTOW macro

DFS4750W USING IRLM IS RECOMMENDEDFOR DIRECTORY CLEANUP

ExplanationIRLM was not used when the batch recovery utilitywas running to clean up the directory. IRLM is used toserialize the update of the directory data set betweenthe online and batch processing.

System actionThe batch recovery utility continues the directorycleanup.

Programmer responseEnsure that the batch recovery utility is runningonly when the IMPORT DEFN SOURCE(CATALOG)command and the DDL definition activation are notrunning at the same time. Issue IMPORT MEMBERTYPE(IMS) SHOW(ALL) to determine whether animport processing is in progress.

Module:DFSOLC10






DFS4751I utilityname READING MEMBERmbrname FROM IMS CATALOGDIRECTORY

ExplanationThis message indicates whether the utility that iscalled is reading from the IMS catalog directoryinstead of from the DBD, PSB, or ACB libraries.

This is in effect only when CATALOG=YES andACBMGMT=CATALOG are specified in either theDFSDFxxx member of the IMS PROCLIB data set orIMS™ Catalog Definition exit routine (DFS3CDX0) toenable the IMS management of ACBs.

In the message text, the variables have the followingmeanings:

utilitynameIndicates one of the following utilities is called:

• DBFUMIN0• DFSBBO00• DFSUDMP0• DFSURDB0• DFSUDMT0

mbrnameIndicates the name of the DBD resource that isbeing read from the IMS catalog directory.

System action:The utility continues to process the requestedfunction.

Output destinationThe system console.


Module:DBFUMIN0, DFSBACK0, DFSUDMP0, DFSURDB0

DFS4755E DATABASE RESOURCE STATEERROR. DBD dbd_name REASON=reason_text PST pst_name

ExplanationThere are work still in progress for databasedbd_name that is changed or deleted on a single IMSsystem.

System actionThe automatic activation for DDL statements failed.

System programmer responseCorrect the problem stated on the reason text andresubmit the DDL statements.

Module:DFSOLC70

DFS4756E PROGRAM RESOURCE STATEERROR. PSB psb_name REASON=reason_text PST pst_name

ExplanationThere are work still in progress for PSB psb_name thatis changed or deleted on a single IMS system.

System actionThe automatic activation for DDL statements failed.


Module:DFSOLC70

DFS4757I NON-RETRYABLE tttttttt REQUESTFAILURES AT CHKPT yyddd/hhmmss. COUNT:ccccccccccOLDEST UOWSTCK:ssssssssssssssss OLDEST QNAME:nnnnnnnnnnnnnnnn OLDESTUOWE TIME: yyyy.jjj hh.mm.ssGMT

ExplanationDuring IMS system checkpoint unit of work (UOW)retry processing, one or more CQS requests failed withnon-retryable return codes for UOWs with deferredCQS actions. IMS writes X'3F' log records containing


the UOW IDs that are associated with the failedCQS requests, and then deletes its internal record ofthe UOWs. This message indicates that this situationoccurred.

This message also can be issued during IMSemergency restart (ERE) processing when IMSencounters X'3F' records for discarded UOWs froman earlier checkpoint. Thus, two separate DFS4757Imessages might be received for the same discardedUOWs - one at checkpoint, and one during emergencyrestart. This ensures that this message either is notmissed or is not lost if IMS abends after discarding theUOWs but before being able to issue the message.


The type of the CQS request that failed as therequest was retried and can be one of the followingvalues:

• CQSPUT• CQSUNLCK

yyddd/hhmmssThe timestamp, which identifies the checkpointthat invoked the retries of the CQS requests.

ccccccccccThe number of the CQS requests that failed for thespecified CQS request type.

ssssssssssssssssThe type 01/03 log record's UOW store clocktoken, MSGPROTK. This value indicates the timewhen the message was inserted into the queuemanager.

nnnnnnnnnnnnnnnnThe destination queue for the oldest CQSPUTor CQSUNLCK UOW. If the destination queuename contains only printable EBCDIC characters,QNAME is an 8-byte value that contains thisprintable queue name. If the destination queuename contains non-printable characters, QNAMEis a 16-byte hexadecimal value that contains thequeue name.

yyyy.jjj hh.mm.ssThe store clock value from UOWSTCK, converted toyyyy.jjj hh.mm.ss format, where yyyy is the year, jjjis the Julian day of the year , and hh.mm.ss is thetime of day in GMT.


Output destinationThe Master Terminal and System Console

Programmer responseCollect IMS log data between OLDEST UOWE TIMEand the time DFS4757I is issued and contact IBMSoftware Support. If DFS4757I is issued with CQSPUT,the discarded message can be re-enqueued; if it isissued with CQSUNLCK, a warm start of IMS or CQScan unlock the message from the shared queues.

Module:DFSQURS0 and DFSQRSQ0

Related referenceCQSPUT request (System Programming APIs)CQSUNLCK request (System Programming APIs)

DFS4760E UNABLE TO ALLOCATE CTCDEVICE, MSPLINK msplink, ADDRaddr

ExplanationIMS restart processing attempted to re-create adynamic MSC channel-to-channel (CTC) physicallink (MSPLINK) that was created during a previousinstance of IMS by using a CREATE MSPLINKcommand. However, the request to dynamicallyallocate the CTC device failed. The followingconditions are some of the possible reasons that causethis error:

• Another IMS system on the same logical partition(LPAR) has created a dynamic MSPLINK that usesthe same CTC address.

• The CTC device was modified offline or detachedfrom the IMS system.

• Available storage is not enough to process thedynamic allocation request.

In the message text:msplink

The name of the physical link.addr

The CTC device address.

System actionIf the problem is internal to the IMS system, such asstorage unavailability, IMS restart processing abends,usually with the abend code U0168.

If the problem is external to the IMS system,IMS restart processing continues and the dynamicMSPLINK is created. However, the new dynamicMSPLINK is not usable for MSC communications, andthe status of the dynamic MSPLINK is NOTOPEN.


http://www.ibm.com/support/knowledgecenter/SSEPH2_15.1.0/com.ibm.ims15.doc.spr/ims_cqsputreq.htm#ims_cqsputreq

http://www.ibm.com/support/knowledgecenter/SSEPH2_15.1.0/com.ibm.ims15.doc.spr/ims_cqsunlckreq.htm#ims_cqsunlckreq

Output destinationThe z/OS system console.

Operator responseUse appropriate MVS commands to determine why theCTC address is not available.

To enable communications for the dynamic CTCMSPLINK, complete the following steps:

1. Delete the existing MSPLINK by using a DELETEMSPLINK command.

2. Create the MSPLINK by using a CREATE MSPLINKcommand to allocate the CTC device again.

Module:DFSRMP20

Related referenceCREATE MSPLINK command (Commands)

DFS4761E OPEN DCB FAILURE FOR CTCDEVICE, MSPLINK msplink, ADDRaddr

ExplanationThe request to dynamically allocate the channel-to-channel (CTC) device during the IMS restart processingwas successful, but the DCB that is associated with thedevice could not be opened. One possible reason forthis error is that the available storage is not enough toprocess the dynamic allocation request.

In the message text:msplink

The name of the physical link.addr

The CTC device address.

System actionIf the problem is internal to the IMS system, such asstorage unavailability, IMS restart processing abends,usually with the abend code U0168.

If the problem is external to the IMS system,IMS restart processing continues and the dynamicMSPLINK is created. However, the new dynamicMSPLINK is not usable for MSC communications, andthe status of the dynamic MSPLINK is NOTOPEN.

Output destinationThe z/OS system console.

Operator responseUse appropriate MVS commands to determine why theCTC address is not available.

To enable communications for the dynamic CTCMSPLINK, complete the following steps:

1. Delete the existing MSPLINK by using a DELETEMSPLINK command.

2. Create the MSPLINK by using a CREATE MSPLINKcommand to allocate the CTC device again.

Module:DFSRMP20

Related referenceCREATE MSPLINK command (Commands)

DFS4764A ONLINE CHANGE COMMIT PHASE2 FAILED, SO IMS IS STUCK IN ANONLINE CHANGE STATE

ExplanationAn error occurred during online change commit phase2. The error might be a result of an internal error. TheIMS system can neither commit the online change norabort it.

System actionThe /MODIFY command is rejected. IMS is stuck in anonline change state. Resources that were deactivatedfor the online change remain inactive.

Output destination:The system console.

User responsePerform the following steps:

• Issue the /DISPLAY MODIFY MODS command andsave the output.

• Produce an IMS dump.• Save the X'22' and X'70' log records.• Contact IBM and provide the documentations: the

output of the /DISPLAY MODIFY MODS command,the system dumps, and the X'22 and X'70' logrecords.

• Use the /CHE FREEZE command to shut down IMSand then restart IMS. If that doesn't work, cancelIMS and perform an emergency restart.

It is likely that some of the resource changes didnot take effect if the commit phase 2 internal erroroccurred before those resources could be changedand log a X'22' log record. You can use the /DISPLAYcommand for the resources that are named in the /


http://www.ibm.com/support/knowledgecenter/SSEPH2_15.1.0/com.ibm.ims15.doc.cr/imscmds/ims_create_msplink.htm#ims_create_msplink

http://www.ibm.com/support/knowledgecenter/SSEPH2_15.1.0/com.ibm.ims15.doc.cr/imscmds/ims_create_msplink.htm#ims_create_msplink

DISPLAY MODIFY MODS command output before IMSshut down to determine whether some of the changesdid not take effect.

If all changes took effect, the output of the /DISPLAYcommand includes the newly added resources, omitsthe deleted resources, and shows the new values ofthe changed resources.

If some of the changes did not take effect, you canretry the online change that failed or perform an IMScold start from the current libraries.

Module:DFSICLV0

Related reference/DISPLAY ACT command (Commands)/DISPLAY MODIFY command (Commands)

DFS4768E ERROR DETECTED DURINGAUTOMATIC IMPORT OF MSCCTC LINK, MSPLINK=msplink,ADDR=addr, RC=rc

ExplanationAn error occurred during the automatic import of anMSC CTC physical link definition from the IMSRSCrepository during IMS cold start.

In the message text:addr

The CTC adapter device ID that is used for the MSCCTC physical link.

msplinkThe CTC physical link name that is imported fromthe IMSRSC repository.

rcIndicates the reason for the failure.8

The CTC device is not available.12

The CTC adapter device number is not a CTCdevice.

16Dynamic allocation of CTC device failed.

20Failed to open the CTC DCB

24No DDNAME is available.

System actionIMS cold start continues and the CTC physical linkdefinition is imported, but the CTC link is not usablefor IMS communications.

Output destination:This message is sent to the z/OS system console.

Operator responseComplete one of the following actions to enablecommunications for a CTC physical link that is notusable:

• Delete the CTC physical link by using the DELETEMSPLINK command, and then re-create the CTC linkwith a valid CTC adapter device number by using theCREATE MSPLINK command.

• Use the UPDATE MSPLINK command to update theexisting definition with a valid CTC adapter devicenumber.

Before you create a new CTC physical link or updatethe existing CTC physical link, ensure that the CTCadapter device number is prepared in your system andthat the CTC physical link in the partner system is alsoprepared.

Problem determination• For return code 8, use MVS commands to determine

why the CTC adapter device ID failed for dynamicallocation. The device might be offline or used byanother system.

• For return code 12, check the system and ensurethat a device is a CTC device.

• For return code 16, this is a system error.• For return code 20, open DCB failed.• For return code 24, all DDNAMEs from DFSM0000 to

DFSM9999 are in use.

Module:DFSMPS00

DFS4770I THE CTC DDNAME ddnameWAS DEALLOCATED AFTER ITSASSOCIATED MSPLINK WASDELETED

ExplanationThe specified DD name was associated with astatically defined channel-to-channel (CTC) MSCphysical link (MSPLINK). However, the MSPLINK wasdeleted in a prior instance of IMS.

This message is issued during IMS warm start oremergency restart to indicate that IMS has deallocatedthe indicated DD name and that its CTC device addressis now available.


The DD statement name


http://www.ibm.com/support/knowledgecenter/SSEPH2_15.1.0/com.ibm.ims15.doc.cr/imscmds/ims_displayact.htm#ims_cr1displayact

http://www.ibm.com/support/knowledgecenter/SSEPH2_15.1.0/com.ibm.ims15.doc.cr/imscmds/ims_displaymodify.htm#ims_cr1displaymodify

System action:IMS restart continues.



Module:DFSRMP20

DFS4771E DATABASE RESOURCE STATEERROR ON ims_id DBD dbd_nameREASON= reason_text PSTpst_name

ExplanationThere are work still in progress for databasedbd_name that is changed or deleted on IMS ims_id.

System actionThe coordinated automatic activation for DDLstatement failed across all IMSs.


Module:DFSOLC70

DFS4772E PROGRAM RESOURCE STATEERROR ON ims_id PSB psb_nameREASON= reason_text PSTpst_name

ExplanationThere are work still in progress for program psb_namethat is changed or deleted on IMS ims_id.



Module:DFSOLC70

DFS4774E AUTOMATIC ACTIVATION OF DDLFAILED FOR DBD dbd_name ON

ims_id RSN= reason_text PSTpst_name

ExplanationDatabase dbd_name failed to be added or changed ordeleted on IMS ims_id. The cause of error is specifiedon the reason_text.



Module:DFSOLC70

DFS4775E AUTOMATIC ACTIVATION OF DDLFAILED FOR PSB psb_name ONims_id RSN= reason_text PSTpst_name

ExplanationPSB psb_name failed to be added or changed ordeleted on IMS ims_id. The cause of error is specifiedon the reason_text.



Module:DFSOLC70

DFS4776E AUTOMATIC ACTIVATION OFDDL DEFINITIONS FAILED ONims_id REASON= reason_text PSTpst_name

ExplanationThe coordinated automatic activation failed on IMSims_id. The cause of error is specified on thereason_text.



System programmer responseCorrect the problem stated on the reason textand resubmit the DDL statements. Look forerror messages DS4753E, DFS4771E, DFS4774E,DSF4756E, DFS4772E and DFS4775E.

Module:DFSOLC70

DFS4777I THE DDL-DEFINED PSB psb_nameIS REFRESHED IN THE IMSDIRECTORY DATA SET. PSTpst_name

ExplanationPSB psb_name has been copied to the directory dataset from the staging data set. There is no contentchange to the PSB except ACB generated timestampchange only.



Module:DFSOLC70

DFS4778I THE CTC DDNAME ddname WASDEALLOCATED BECAUSE THE CTCADDRESS WAS CHANGED FORMSPLINK msplink

ExplanationThe specified DD name was associated with astatically defined channel-to-channel (CTC) MSCphysical link (MSPLINK). However, the CTC deviceaddress assigned to the link was changed by usingthe UPDATE MSPLINK command in a prior instance ofIMS.

This message is issued during IMS warm start oremergency restart to indicate that IMS has deallocatedthe indicated DD name and that its device address isnow available.


The DD statement name

msplinkThe name of the CTC physical link

System action:IMS restart continues.



Module:DFSRMP20

DFS4779I THE DDL-DEFINED PSB psb_nameIS COPIED TO THE IMSDIRECTORY DATA SET. PSTpst_name

ExplanationPSB psb_name has been copied to the directory dataset from the staging data set.



Module:DFSOLC70

DFS4780I THE DDL-DEFINED DBD dbd_nameIS COPIED TO THE IMSDIRECTORY DATA SET. PSTpst_name

ExplanationDatabase dbd_name has been copied to the directorydata set from the staging data set.



Module:DFSOLC70


DFS4781I AUTOMATIC ACTIVATION OF DDLDEFINITIONS COMPLETE ONims_id RC=00. PST pst_name

ExplanationThe coordinated automatic activation of DDLstatements has completed successfully on IMS ims_id.

System actionIMS completed the automatic activation of DDLstatement successfully across active sharing IMSs inthe plex.


Module:DFSOLC70

DFS4782E AUTOMATIC ACTIVATION OFDDL DEFINITIONS FAILED ONims_id REASON= reason_text PSTpst_name

ExplanationThe coordinated automatic activation of DDLstatements failed on IMS ims_id.

System actionThe coordinated automatic activation of DDLstatements failed across active sharing IMSs in theplex.

System programmer responseCorrect the problem and resubmit the DDL statements.

Module:DFSOLC70

DFS4783I AUTOMATIC ACTIVATION OF DDLDEFINITIONS NOT DONE ONims_id REASON= reason_text PSTpst_name

ExplanationThe coordinated automatic activation of DDLstatements was not done on IMS ims_id. This IMS isbeing either shutdown or abended. Or, it no longerwants access to the shared directory and has changedits ACBSHR parameter from a Yes to a NO.

System actionThe automatic activation of DDL statement completedsuccessfully. IMS ims_id has been removed from thelist of IMS accessing this shared directory data set.


Module:DFSOLC70

DFS4784E UNSUPPORTED KEYWORDSSPECIFIED IN DSN OR DSNDATA

ExplanationIn the DDL section of the DFSDFxxx member of theIMS.PROCLIB data set, invalid keywords, except forthe &DBNAME and &AREANAME symbols if used, werespecified in the DSN= or DSNDATA= parameter.

System actionCreation of a DEDB area data set by using DDLterminates without completing the requested function.

System programmer responseUse one of the following methods to create the DEDBarea:

• Create the DEDB area data set manually by using theIMS generation utilities.

• If you use the CREATE DATABASE DDL statementto create the DEDB area data set, in the DDLsection of the DFSDFxxx member, modify the DSN=or DSNDATA= parameter to use valid keywords.

Module:DFS3DD00

Related referenceDDL section of the DFSDFxxx member (SystemDefinition)

DFS4785W DEDB dedb_name AREAarea_name DATASETdataset_name ALREADY EXISTS

ExplanationA DDL statement was submitted to createdataset_name, but the data set already exists.

In the message text:dedb_name

Name of the DEDB.area_name

Name of the DEDB area.


http://www.ibm.com/support/knowledgecenter/SSEPH2_15.1.0/com.ibm.ims15.doc.sdg/ims_dfsdfxxx_proclib_ddl.htm#ims_dfsdfxxx_proclib_ddl

http://www.ibm.com/support/knowledgecenter/SSEPH2_15.1.0/com.ibm.ims15.doc.sdg/ims_dfsdfxxx_proclib_ddl.htm#ims_dfsdfxxx_proclib_ddl

dataset_nameName of the DEDB area data set.

System actionBecause the DEDB area data set dataset_namealready exists, the /START DB and /START AREAcommands are issued by IMS.

System programmer responseCheck whether the DEDB area data set dataset_nameis the data set that you require. If the dataset_namedata set that is being used by IMS is not the dataset that you require, undo the resources or manuallychange the data set.

Module:DFS3DD00

DFS4787I DEF_NBA=nnnn, DEF_OBA=nnnnWERE SPECIFIED BUT NOT USEDDUE TO 64-BIT BUFFER MODE NOTACTIVATED.


Programmer responseThe default NBA and default OBA are not appliedto the BMP procedure, and NBA= and OBA= ofthe BMP cannot be omitted. The DEF_NBA andDEF_OBA parameters are valid only when FPBP64=Yis specified. Enable the Fast Path 64-bit buffer modeand restart IMS.

ModuleDBFFATC1


DFS4794I AFTER ABEND OF MASTER IMSims_id THIS IMS COMPLETEDIMPORT COMMAND PROCESSING.

ExplanationThe IMS system that is identified in the ims_id fieldof the message text abended during the processingof an IMPORT DEFN SOURCE(CATALOG) command.Another IMS system that shares the IMS catalog tookover the processing. This IMS system committed theimport processing and the resources are active in thesystem.


The IMS system that abended.

System action:The IMPORT DEFN SOURCE(CATALOG) wascommitted and the resources are active in this IMSsystem.



Module:DFSOLC80

DFS4795I AFTER ABEND OF MASTER IMSims_id THIS IMS COMPLETED THEACTIVATION OF DDL-DEFINEDSOURCES. PST pst_name

ExplanationThe IMS system that is identified in the ims_id field ofthe message text abended while serving as the mastersystem for the activation of DDL-defined databaseresources for PST pst_name. Another IMS systemtook over the processing. The import processing wascommitted by this IMS system.


The master IMS system that abended.pst_name


System action:The DDL definition activation was committed.



Module:DFSOLC80

DFS4796E AFTER ABEND OF MASTER IMSims_id THE IMPORTED PSBS ANDDMBS ARE NOT USABLE.

ExplanationThe command master IMS system that is identifiedin the ims_id field of the message text abended




during the processing of a global IMPORT DEFNSOURCE(CATALOG) command. Another IMS systemtook over processing, but failed to back out theupdates that were made to the IMS directory datasets. The affected databases and program viewscannot be scheduled. See the previously issuedDFS4894E message for more details.



System action:IMS was unable to back out the updates to the IMSdirectory data sets.


System programmer response:Issue the IMPORT DEFN SOURCE(CATALOG) again.You can also issue the QUERY MEMBER TYPE(IMS)SHOW(STATUS) command to determine the statusof activation processing and, if necessary, how torespond.

Module:DFSOLC80

Related referenceQUERY MEMBER command (Commands)

DFS4797E AFTER ABEND OF MASTER IMSims_id THE DDL-DEFINED PSBSAND DMBS ARE NOT USABLE. PSTpst_name

ExplanationThe IMS system that is identified in the ims_id fieldof the message text abended during the activation ofDDL resource definitions. Another IMS system tookover processing, but could not back out the updatesthat were made to the IMS directory data sets.The affected databases and program views cannotbe scheduled. See the previously issued DFS4895Emessage for more details.


The IMS system that abended.pst_name


System action:IMS was unable to back out the updates to the IMSdirectory data sets.


System programmer response:Issue the QUERY MEMBER TYPE(IMS)SHOW(STATUS) command to determine the status ofactivation processing and how to respond.

Module:DFSOLC80


DFS4798I AFTER ABEND OF MASTER IMSims_id THIS IMS CANCELLED THEIMPORT COMMAND PROCESSING.

ExplanationThe IMS system that is identified in the ims_id fieldof the message text abended during the processingof an IMPORT DEFN SOURCE(CATALOG) command.Another IMS system that shares the IMS catalog tookover the processing. The catalog import processingwas canceled on this IMS.



System action:The IMPORT DEFN SOURCE(CATALOG) commandwas aborted.


System programmer response:Correct the error identified in the reason text.You can issue the QUERY MEMBER TYPE(IMS)SHOW(STATUS) command to determine the statusof activation processing and, if necessary, how torespond.

Module:DFSOLC80


DFS4799I AFTER ABEND OF MASTER IMSims_id THIS IMS CANCELLED THEACTIVATION OF DDL-DEFINEDRESOURCES. PST pst_name

ExplanationThe IMS system that is identified in the ims_id fieldof the message text abended during the activation ofDDL resource definitions. Another IMS system tookover processing. The catalog import processing wascanceled on this IMS.






ims_idThe IMS system that abended.


System action:The DDL definition activation was aborted.



Module:DFSOLC80






DFS4810I ALL MEMBERS IN THE SYSUT1DATA SET WERE SUCCESSFULLYDELETED.

or

ALL OF THE MEMBER INSTANCES THAT AREREFERENCED IN THE SYSUT1 DATA SET WEREDELETED FROM THE IMS CATALOG.

Explanation:The IMS Catalog Record Purge utility successfullydeleted the outdated records from the IMS catalogdatabase.



Module:DFS3PU10

DFS4830I OTMA ENDED RESUME TPIPE FORTMEMBER/TPIPE xxxx/yyyy RT=zzzz


While OTMA was waiting for an ACK or NAKfrom the OTMA target member (tmember or client)xxxx with the transaction pipe (tpipe) yyyy, a CM0timeout action or an IMS command such as /STOPTMEMBER TPIPE canceled the wait for an ACK orNAK and ended a resume tpipe request from thetarget member. IMS also sends out the protocolmessage "cancel resume output for tpipehold queue request protocol command" to thetarget member.

When the DL/I ICAL call has a large amount of requestdata (greater than 32000 bytes) with a small timeoutvalue, it is likely to trigger the timeout action. Thismessage was issued and the resume tpipe requestwas canceled.

ExplanationIn the message text:xxxx

Name of the OTMA client.yyyy

Name of the tpipe.zzzz

Resume tpipe token set by the OTMA client (suchas IMS Connect).


Operator response:Identify the cause of the missing ACK or NAK forthe resume tpipe request. The cause might be anapplication program or a failure in the networkcomponent.

Programmer responseThe programmer response can be one of the following:

Ensure that your program issues an ACK or NAK toIMS for the received CM0 output message. Also, it ispossible that the ACK or NAK cannot arrive at IMSOTMA because of a network failure. You can submitmultiple resume tpipe requests to IMS. When oneends, the other can continue to retrieve messagesfrom IMS.

A system delay in IMS might slow down the ICALprocessing. Increase the DL/I ICAL call timeoutvalue by changing the AIBRSFLD value in the ICALcall. If AIBRSFLD is not specified, use the UPDATEOTMADESC command or code the DFSYDTx memberof the IMS.PROCLIB data set to increase the timeoutvalue for the ICAL call.

Problem determinationThe problem determination can be one of thefollowing:

Examine the network trace to identify whichcomponent in the network did not forward the ACKor NAK to IMS. Ensure that your application programissues an ACK or NAK to IMS for the received CM0output message or synchronous callout message.


Examine the 67D0 log record to find out the rootcause.

Module:DFSYQAB0

DFS4831E NO STORAGE IN SUBPOOL 230FOR OTMA INPUT.

Explanation:IMS XCF message exit for OTMA received an inputmessage. However, IMS failed to allocate an IMS AWEblock from subpool 230 to process the input message.

System action:IMS OTMA might not be able to function properly toprocess the rest of messages from the client.

Programmer response:You might need to contact your DBA or systemprogrammer for assistance.

Module:DFSYMGX0

DFS4832E IMS DIRECTORY NOT CLEANEDUP AFTER IMS ims_idABENDED AND THIS IMSCOMPLETED ACTIVATION OF DDLDEFINITIONS. PST pst_name.

ExplanationThe IMS system that is identified in the ims_id field ofthe message text abended during the commit phaseof activation processing of DDL-defined resources.Another IMS took over the processing. The processingwas committed in this IMS system, but the clean up ofthe IMS directory could not complete.




System action:The automatic activation of the DDL defined resourceswas committed in this IMS system.



Module:DFSOLC80

DFS4833E IMS DIRECTORY NOT CLEANED UPAFTER IMS ims_id ABENDED ANDTHIS IMS CANCELLED IMPORTPROCESSING.

ExplanationThe IMS system that is identified in the ims_id field ofthe message text abended during the processing of aglobal IMPORT DEFN SOURCE(CATALOG) command.Another IMS took over the backout processing and theimport processing was canceled on this IMS system,but the clean up of the IMS directory did not complete.



System action:The updates made to the directory were aborted.



Module:DFSOLC80

DFS4834E IMS DIRECTORY NOT CLEANED UPAFTER IMS ims_id ABENDED ANDTHIS IMS COMPLETED IMPORTCOMMAND PROCESSING.

ExplanationThe master IMS system that is identified in theims_id field of the message text abended duringcommit processing of a global IMPORT DEFNSOURCE(CATALOG) command. Another IMS systemtook over the processing and the updates are reflectedin this IMS system, but the clean up of the IMSdirectory cannot complete.



System action:The updates made to the IMS directory werecommitted.




Module:DFSOLC80

DFS4835I IMS INITIALIZATION IS WAITINGFOR IMS ims_id TO COMPLETEA DDL DEFINITION ACTIVATIONFROM THE SHARED IMS CATALOG

ExplanationThis IMS system is waiting for the IMS systemidentified in the ims_id of the message text tofinish processing a DDL definition activation task.After this task ends, the initialization of this IMSsystem continues. If there is no active DDL definitionactivation task in progress, this indicates the directorydata sets were not cleaned up.



System action:The IMS system waits.


System programmer response:Issue the QUERY MEMBER TYPE(IMS)SHOW(STATUS) command to check the status ofactivation processing and, if necessary, how torespond.

Module:DFSRDB30


DFS4840E THE JCL IS MISSING A SYSIN DDSTATEMENT

ExplanationThe JCL for the IMS Catalog Directory Recoveryutility (DFS3RU00) is missing the required SYSIN DDstatement.

System actionThe IMS Catalog Directory Recovery utility failed.

System programmer responseAdd the missing SYSIN DD statement to the JCL andrun the utility again.

Module:DFS3RU00

DFS4841E AN INVALID OPTION WASSPECIFIED IN THE CONTROLSTATEMENT. DATA SET (DDNAMESYSIN).

ExplanationThe member name specified on the SYSIN DDstatement in JCL was invalid.


Programmer responseCorrect the SYSIN DD statement to MBR=ALL and runthe utility again.

Module:DFS3RU00

DFS4842E THE SYSIN DATA SET FAILED TOOPEN. OPEN RC = nnnnnn.

ExplanationError occurred when the IMS Catalog DirectoryRecovery utility opens the SYSIN data set. nnnnnn isthe return code.


Programmer responseCorrect the SYSIN data set and run the utility again.

Module:DFS3RU00

DFS4843E CONTROL STATEMENT ERROR

ExplanationThe SYSIN control statement specified in the JCL forIMS Catalog Directory Recovery utility is invalid.


System programmer responseCorrect the SYSIN data set and run the utility again.

Module:DFS3RU00

DFS4844E MEMBER NAME INVALID



ExplanationThe member name specified on the SYSIN controlstatement in JCL was invalid.


System programmer responseCorrect the member name to MBR=ALL and run theutility again.

Module:DFS3RU00

DFS4845E MEMBER NAME IS LONGER THAN3 CHARACTERS

ExplanationThe member name specified on the SYSIN controlstatement in JCL is longer than 3 characters.


System programmer responseCorrect the member name to MBR=ALL and run theutility again.

Module:DFS3RU00

DFS4846E UTILITY ONLY RUNS AS DLIBATCH REGION

ExplanationThe IMS Catalog Directory Recovery utility runs only asDL/I batch.


System programmer responseSet the EXEC parameter to DL/I and run the utilityagain.

Module:DFS3RU00

DFS4847E METADATA UNAVAILABLE FORTHE RESOURCE nnnnnnnn

ExplanationMetadata information is unavailable for the targetresource in the IMS catalog. nnnnnnnn is the name ofthe target resource.

System actionThe IMS Catalog Directory recovery utility failed.

System programmer responseEnsure that all resources are recovered during theIMS catalog recovery process, and then run the utilityagain.

Module:DFS3RU00

DFS4848E NOT ENOUGH STORAGE TO BUILDMETADATA FOR nnnnnnnn

ExplanationThe IMS system ran out of storage to build metadatainformation for the target IMS resource. nnnnnnnn isthe name of the target resource.


System programmer responseIncrease the system storage and then run the utilityagain.

Module:DFS3RU00

DFS4849E DIRECTORY DATA SETS ALREADYIN USE

ExplanationThe IMS directory data sets cannot be rebuilt becausethey are open or in use.


System programmer responseClose the IMS directory data sets and then run theutility again.

Module:DFS3RU00


DFS4850E nnnnnnnn DATABASE TYPE NOTSUPPORTED

ExplanationThe IMS Catalog Directory recovery utility tried toaccess resources in MSDB or Shared Secondary IndexDatabase, which are not supported by the utility.nnnnnnnn is the resource name.


System programmer responseTo restore the ACBs in databases of non-supportedaccess type databases and programs that refer them,perform ACBGEN and then run the Catalog Populateutility (DFS3PU00) with directory setup option torecover these members to directory data sets.

Module:DFS3RU00

DFS4851E INVALID PSB

ExplanationThe PSB that was specified on the EXEC parameters inthe JCL is invalid.

System actionThe issuing IMS catalog utility failed.

System programmer responseCorrect the PSB name and run the utility again.Specify DFSCP000 (ACBMGMT=ACBLIB) or DFSCP001(ACBMGMT=CATALOG) and run the utility again.

Module:DFS3RU00 and DFS3LU00

DFS4852E NOT ENOUGH STORAGE TORECOVER RESOURCE nnnnnnnn

ExplanationWhile the IMS Catalog Directory Recovery utility(DFS3RU00) was processing to recover a target IMSresource, the IMS system ran out of storage to build aninternal block.


Is the name of the target IMS resource that wasnot recovered.

System action:

The IMS Catalog Directory Recovery utility(DFS3RU00) fails.

Output destination of messageThe job output of the DFS3RU00 utility.

Programmer response:In the JCL for the region that the DFS3RU00 utilityis running in, increase the region size. Then, run theDFS3RU00 utility again.

Module:DFS3RU00

Related referenceIMS Catalog Directory Recovery utility(DFS3RU00) (System Utilities)

DFS4861W EDIT ROUTINE DFSCNTE0UNAVAILABLE FOR LTERMxxxxxxxx

ExplanationThe static logical terminal was defined with EDIT=YESon the NAME macro, but the message switching inputedit routine, DFSCNTE0, was not loaded successfullyby the IMS system.


Indicates the logical terminal (LTERM) name.

System actionStatic terminals that are defined to use the messageswitching input edit routine (EDIT=YES was definedon the NAME macro) will not have access to theDFSCNTE0 routine. The terminal will be treated as ifEDIT=NO was specified on the NAME macro. IMS willhave previously issued DFS1934E to indicate that theedit routine was not loaded.

IMS continues initialization.


System programmer responsePerform the following steps:

1. Check message DFS1934E that was previouslyissued. This message indicates that DFSCNTE0could not be loaded.

2. Make sure that DFSCNTE0 exists in one of theIMS.SDFSRESL concatenated data sets.


http://www.ibm.com/support/knowledgecenter/SSEPH2_15.1.0/com.ibm.ims15.doc.sur/ims_catalog_dfs3ru00.htm#ims_catalog_dfs3ru00

http://www.ibm.com/support/knowledgecenter/SSEPH2_15.1.0/com.ibm.ims15.doc.sur/ims_catalog_dfs3ru00.htm#ims_catalog_dfs3ru00

3. Identify the cause to the load failure and correctthe failure.

4. Cold or warm start the IMS system again for the exitroutine to be loaded.

Module:DFSAINB0

Related information“DFS1934E” on page 561module FAILED TO LOAD modulename ERRORCODE=xxxxxxxx.

DFS4862W EDIT ROUTINE xxxxxxxxUNAVAILABLE FOR NODE yyyyyyyy

ExplanationThe physical terminal input or output edit routine thatwas defined for the terminal could not be loadedduring IMS initialization. The routine was defined bythe EDIT= keyword in the IMS System Definition TYPEmacro associated with the indicated terminal for staticterminals, or in the EDIT= keyword of the ETO nodedescriptor for dynamic terminals.


Indicates the physical terminal edit routine name.yyyyyyyy

Indicates the terminal node name.

System actionStatic terminals that are defined to use the physicalterminal edit routine (EDIT=YES specified on theTERMINAL macro) do not have access to the input oroutput routine. The terminal is treated as if EDIT=NOwas specified on the TERMINAL macro. MessageDFS1934E is issued to indicate that the edit routinewas not loaded.

Dynamic terminals that are defined to use the physicalterminal edit routine (EDIT= was defined on thenode descriptor) do not have access to the input oroutput routine. The terminal is treated as if EDIT=was not specified on the node descriptor. If the nodedescriptor is properly defined in the DFSDSCMx orDFSDSCTy member of the IMS.PROCLIB data set,message DFS3660W is issued to indicate that the editroutine is ignored for the descriptor.

IMS continues initialization or is restarted.



1. Check message DFS1934E or DFS3660W that wasissued previously. Both messages indicate whichphysical terminal edit routines could not be loaded.

2. Make sure that the physical terminal edit routineexists in one of the IMS.SDFSRESL concatenateddata sets.


4. For dynamic terminals, delete the terminal. ForSLUP and FINANCE terminals, issue the CHANGENODE CLODESESS command to allow the terminalto be deleted if necessary.

5. Warm or cold start the IMS system again for the exitroutine to be loaded.

Module:DFSAINB0, DFSCRPB0, DFSCRPD0

Related referenceTERMINAL macro (System Definition)DFSDSCMx member of the IMS PROCLIB dataset (System Definition)DFSDSCTy member of the IMS PROCLIB dataset (System Definition)Related information“DFS1934E” on page 561module FAILED TO LOAD modulename ERRORCODE=xxxxxxxx.“DFS3660W” on page 1045EDIT ROUTINE xxxxxxxx DEFINED BYDESCRIPTOR yyyyyyyy CANNOT BE FOUND.DESCRIPTOR IGNORED.

DFS4863W EDIT ROUTINE xxxxxxxxUNAVAILABLE FOR LINE yyyyPTERM zzzz

ExplanationThe physical terminal input or output edit routine thatis defined for the terminal cannot be loaded duringthe IMS initialization. The routine was defined by theEDIT= keyword in the IMS System Definition LINEGRPmacro associated with the indicated terminal.


Indicates the physical terminal edit routine name.yyyy

Indicates the communication line number.zzzz

Identifies the physical terminal number.


http://www.ibm.com/support/knowledgecenter/SSEPH2_15.1.0/com.ibm.ims15.doc.sdg/ims_terminal_macro.htm#ims_terminal_macro

http://www.ibm.com/support/knowledgecenter/SSEPH2_15.1.0/com.ibm.ims15.doc.sdg/ims_dfsdscmx_proclib.htm#ims_dfsdscmx_proclib

http://www.ibm.com/support/knowledgecenter/SSEPH2_15.1.0/com.ibm.ims15.doc.sdg/ims_dfsdscmx_proclib.htm#ims_dfsdscmx_proclib

http://www.ibm.com/support/knowledgecenter/SSEPH2_15.1.0/com.ibm.ims15.doc.sdg/ims_dfsdscty_proclib.htm#ims_dfsdscty_proclib

http://www.ibm.com/support/knowledgecenter/SSEPH2_15.1.0/com.ibm.ims15.doc.sdg/ims_dfsdscty_proclib.htm#ims_dfsdscty_proclib

System actionStatic terminals that are defined to use the physicalterminal edit routine (EDIT=YES specified on theTERMINAL macro) do not have access to the inputor output edit routine. The terminal is treated asif EDIT=NO was specified on the TERMINAL macro.Message DFS1934E is issued to indicate that the editroutine is not loaded.

IMS continues initialization.



1. Check message DFS1934E that was issuedpreviously. The message indicates which physicalterminal edit routines cannot be loaded.

2. Make sure that the physical terminal edit routineexists in one of the IMS.SDFSRESL concatenateddata sets.


4. Warm or cold start the IMS system again for the exitroutine to be loaded.

Module:DFSAINB0

Related information“DFS1934E” on page 561module FAILED TO LOAD modulename ERRORCODE=xxxxxxxx.

DFS4864W FRONT END SWITCHUNAVAILABLE FOR NODE xxxxxxxx

ExplanationThe physical terminal is defined with OPTION=FES onthe TERMINAL macro, or on the Extended TerminalOption (ETO) node descriptor. However, the Front-End-Switch exit routine, DFSFEBJ0, was not loadedsuccessfully by the IMS system. The load failure is dueto one of the following causes:

• DFSFEBJ0 is not available• FESEXIT=Y is not specified in the IMS startup

parameters.


Indicates the physical terminal node name.

System actionTerminals that are defined to use the Front-End-Switch exit routine (OPTIONS=FES specified on theTERMINAL macro or on the ETO node descriptor)do not have access to the DFSFEBJ0 routine.The terminal is treated as if OPTIONS=NOFES isspecified. If FESEXIT=Y is specified in the IMS startupparameters, then message DFS1934E is issued toindicate that DFSFEBJ0 is not loaded correctly.

IMS continues initialization or is restarted.



1. Make sure that FESEXIT=Y is specified in the IMSstartup parameters.

2. Check message DFS1934E that was issued. Thismessage indicates that DFSFEBJ0 cannot beloaded correctly.

3. Make sure that DFSFEBJ0 exists in one of theIMS.SDFSRESL concatenated data sets.


5. Warm or cold start the IMS system again for the exitto be loaded.

Module:DFSAINB0, DFSCRPB0, DFSCRPD0

Related referenceFront-End Switch exit routine (DFSFEBJ0) (ExitRoutines)TERMINAL macro (System Definition)Related information“DFS1934E” on page 561module FAILED TO LOAD modulename ERRORCODE=xxxxxxxx.

DFS4865E MODULE IRRSPW00 IS REQUIREDFOR SGNGENRC=Y, BUT IT ISUNAVAILABLE.

Explanation:SGNGENRC=Y was specified, but IMS was unable toload the required SAF load module IRRSPW00.

System action:IMS initialization terminates abnormally with abend0718.


http://www.ibm.com/support/knowledgecenter/SSEPH2_15.1.0/com.ibm.ims15.doc.err/ims_dfsfebj0.htm#ims_dfsfebj0

http://www.ibm.com/support/knowledgecenter/SSEPH2_15.1.0/com.ibm.ims15.doc.err/ims_dfsfebj0.htm#ims_dfsfebj0

http://www.ibm.com/support/knowledgecenter/SSEPH2_15.1.0/com.ibm.ims15.doc.sdg/ims_terminal_macro.htm#ims_terminal_macro

System programmer responseEnsure that the IRRSPW00 module, which is providedby RACF, is included in one of the following locations:

• LPA• A library in LINKLIST• One of the IMS.SDFSRESL concatenated data sets

Then, cold or warm start the IMS system to load theIRRSPW00 module.

Module:DFSAINB0

DFS4866E SGNGENRC=Y IS INVALIDBECAUSE RACF IS NOT ENABLED.SGNGENRC=N WILL BE USED.

Explanation:SGNGENRC=Y is specified but cannot not take effectbecause RACF is not enabled for IMS.

System action:IMS initialization continues with the default value, N,for the SGNGENRC= parameter.

Output destination:The System Console.

System programmer response:Ensure that the RACF= parameter is specified.

Module:DFSAINB0

DFS4867A OPEN FAILED ON ddname -ENCRYPTED OLDS REQUIRES ICSF

ExplanationThe IMS logger attempted to open the encryptedonline log data set (OLDS) with the data definitionname ddname. A return code indicated that the dataset could not be opened because the IntegratedCryptographic Service Facility (ICSF) subsystem, whichis required, was not active.


The data definition name for the encrypted OLDSthat could not be opened.

System actionThe ddname in the message identifies either a datacontrol block (DCB) for an OLDS that is being writtento (DFSOLPxx) or a DCB for an OLDS that is being readfrom (DFSOLRxx).

For an encrypted OLDS that is being written to, IMScontinues processing normally with the current activeOLDS until this OLDS becomes full. At 10-secondintervals, IMS will retry the OPEN request on the

OLDS that could not be opened until it successfullyopens or until the request fails with a different returncode. After the current active OLDS becomes full, IMSprocessing stops until another OLDS is successfullyopened.

For an encrypted OLDS that is being read from, IMScontinues processing normally. At 10-second intervals,IMS will also retry the OPEN request to read the OLDSuntil it successfully opens or until the request failswith a different return code.

Output destination of messageThis message is displayed in the systems console andthe master terminal.

Programmer response:Start the ICSF subsystem so that IMS can successfullyopen the encrypted OLDS.

Module:DFSFDLS0

DFS4874I THE ALLOCATION OF THE IMSCATALOG DIRECTORY DATA SETSFAILED

ExplanationThe IMS Catalog Library Builder utility (DFS3LU00)could not allocate the system data sets of the IMScatalog by using the data set high level qualifier namethat is specified on the IMSCATHLQ utility controlstatement.

System action:The utility terminates without building any output.


System programmer response:Input the correct HLQ name or DFSMDA member nameand rerun the utility.

Module:DFS3LU00, DFS3LU10, DFS3LU20

DFS4876E CSL IS NOT ENABLED IN THISIMS. CSL IS REQUIRED TO ACCESSA SHARED IMS CATALOG.

ExplanationThis IMS system attempted to access an IMS catalogthat is shared by one or more other IMS systems,but the required IMS Common Service Layer (CSL)components are not enabled in this IMS. The CSLOperations Manager (OM), Resource Manager (RM),and the Structured Call Interface (SCI) must be


enabled in all IMS systems that access a shared IMScatalog.

System action:IMS terminates with abend U0071.


System programmer response:Activate IMS CSL with OM, RM, and SCI.

Module:DFSRDB30

DFS4877E RM IS NOT ENABLED IN THIS IMS.CSL WITH RM IS REQUIRED TOACCESS A SHARED IMS CATALOG.

ExplanationThis IMS system attempted to access an IMS catalogthat is shared by one or more other IMS systems,but the Resource Manager (RM) component of theIMS Common Service Layer (CSL) is not enabled inthis IMS. The CSL Operations Manager (OM), ResourceManager (RM), and the Structured Call Interface (SCI)must be enabled in all IMS systems that access ashared IMS catalog.

System action:IMS terminates with abend U0071.


System programmer response:Activate IMS CSL with OM, SCI, and RM.

Module:DFSRDB30

DFS4878I THE CURRENT IMS VERSION ISvv.r.m FUNCTION LEVEL nnnnnnnn

ExplanationThis message is issued during IMS cold start andIMS restart to indicate the current IMS version andfunction level. The current IMS function level identifiesthe latest PTF that contains one or more new IMSfunctions that are delivered by IMS. The IMS functionlevel can change across an IMS restart, if a PTF with anupdated IMS function level in the IMS function table(DFSFNCT0) is applied.

This message appears before the DFS994I messagefor COLD START COMPLETED, WARM STARTCOMPLETE, or EMERGENCY START COMPLETED(including COLDCOMM, COLDBASE, and COLDSYS).


mIndicates the IMS modification level within the IMSversion and release. If the IMS modification levelis greater than 9, 2 characters is used for thisvariable (mm).

nnnnnnnnIndicates the current IMS function level as a fullword decimal number represented as 8 characters.The current IMS function level identifies the latestPTF that contains new or changed IMS function.The first IMS function level is 00000001. The 15thIMS function level is decimal 00000015, whichis represented as X'0000000F' in log records anddumps.

rIndicates the IMS release within the version. If theIMS release number is greater than 9, 2 charactersare used for this variable (rr).

vvIndicates the IMS version.

System action:IMS proceeds normally.

Output destination of message:This message is sent to the z/OS system console


Module:DFSRST00

DFS4879I THE IMS FUNCTION functionnameIS ENABLED

ExplanationThis message is issued by the UPDATE IMSFUNCcommand when an IMS function is successfullyenabled.

In the message text:functionname

Indicates the name of the IMS function that wassuccessfully enabled. The function name can be upto 16 characters in length.


Output destination of message:This message is sent to the z/OS system console


Module:


DFSIU210

DFS4880W AUTOMATIC ACTIVATION OF DDLSUBMISSION NOT DONE ONims_id REASON= reason_text PSTpst_name

ExplanationResource definition changes that were submitted byusing DDL could not be activated automatically onthe IMS system that is identified in the ims_id fieldbecause the IMS system was either shut down orit abended. If another IMS system committed theresource changes in the IMS directory, the IMS systemwill load the updated ACB blocks when it restarts.


The IMS ID of the system in which automaticactivation did not complete.

pst_nameThe name of the task that submitted the DDLstatement.

reason_textEither SHUTDOWN or ABENDED.

System action:The command master system continues the automaticactivation of the DDL statements.

Output destination of message:The message is sent to the z/OS operator console.

System programmer response:Take any appropriate action that is needed to ensurethat the application programs are in sync with ACBchanges when IMS ims_id is restarted.

Module:DFSOLC70

DFS4881I THE IMS FUNCTION functionnameIS DISABLED

ExplanationThis message is issued by the UPDATE IMSFUNCcommand when an IMS function is successfullydisabled.

In the message text:functionname

Indicates the name of the IMS function that wassuccessfully disabled. The function name can beup to 16 characters in length.


Output destination of message:

This message is sent to the z/OS system console


Module:DFSIU210

DFS4882A ISSUE QUERY MEMBER TYPE(IMS)SHOW(ALL) FOR WAIT ANALYSISIF OTHER IMS ACTIVE

ExplanationIssue the recommended QUERY command on activeIMSs to determine the status of the shared catalogdirectory data sets and take action to allow IMS restartto proceed.

System actionThe IMS system waits for the completion of catalogimport cleanup processing.


Programmer responseIf the output of the QUERY command shows statusIMPABORT, a master IMS abnormally ended while it isprocessing the catalog import. Other IMS participantsmight have taken over the cleanup of the shareddirectory data sets but failed, or there is no active IMSto clean up the shared directory data sets. If thereare other active IMSs that share the directory datasets, issue the IMPORT DEFN SOURCE(CATALOG)command on one of the active IMSs to clean up theshared directory data sets. If there are no other activeIMSs, run the batch recovery utility (DFS3RU00) toclean up the shared directory data sets.

Module:DFSRDB30

Related referenceQUERY commands (Commands)IMPORT DEFN SOURCE(CATALOG) command(Commands)

DFS4883A TO EXIT WAIT, TAKEACTION RECOMMENDED UNDERPROGRAMMER RESPONSE OFMESSAGE DFS4883A


http://www.ibm.com/support/knowledgecenter/SSEPH2_15.1.0/com.ibm.ims15.doc.cr/imscmds/ims_querycmds.htm#ims_cr2querycmds



ExplanationA master IMS abended during a catalog importprocessing. Other IMS participants might have takenover the cleanup of the shared directory data sets butfailed, or there is no active IMS to clean up the shareddirectory data sets.

System actionThis IMS waits for the completion of catalog importcleanup processing.


Programmer responseIf there are other active IMSs that share the directorydata sets in the IMSplex, issue the IMPORT DEFNSOURCE(CATALOG) command on one of the activeIMSs to clean up the shared directory data sets. Ifthere are no other active IMSs, run the batch recoveryutility (DFS3RU00) to clean up the shared directorydata sets.

Module:DFSRDB30

Related referenceIMPORT DEFN SOURCE(CATALOG) command(Commands)

DFS4888I UOW LOCK NOTIFY RECEIVEDTIMEOUT RESPONSE FROM ims_id

ExplanationIn a Fast Path environment, the IRLM notify processis used to notify all of the IMS subsystems in anIMS sysplex of a request. An IMS system waits untilall other IMS systems in the sysplex respond to theIRLM notify process. Or, an IMS system waits until atimeout response is returned to the notify process, andthen the request is terminated by the IMS system thatinitiated the request.

This message was issued because an IMS system inan IMS sysplex sent a unit of work (UOW) lock modetransition message to other members of the sysplexfor high-speed sequential processing (HSSP) or high-speed reorganization (HSR). A timeout then occurredin the UOW lock mode transition process, and atimeout response was returned by the IMS systemims_id to the IRLM notify process. This indicates thatthe IMS system ims_id is holding CI locks on the areadata set.


ims_idThe IMS system that returned a timeout responseto the UOW lock mode transition message.

Output destinationThis message is displayed on the terminal of the IMSsystem that initiated the UOW lock request.

System programmer responseUse local diagnostic tools to find the lock owner andtake appropriate action.

Module:DBFICLI0

DFS4890E THE DFS3PU00 UTILITY CANNOTBE RUN AS A BMP FORMANAGEDACBS=SETUP

ExplanationThe IMS™ Catalog Populate utility (DFS3PU00) cannotbe run as a BMP in an ACBMGMT=ACBLIB environmentwhen the MANAGEDACBS=SETUP utility controlstatement is specified.

System action:The IMS Catalog Populate utility terminateswith return code 12 without performing theMANAGEDACBS=SETUP function.

Output destination of message:The message is sent to DFS3PU00 utility job output.

System programmer response:Rerun the IMS Populate utility as a batch job in a DL/Ior DBB region.

Module:DFS3PU00

Related tasksEnabling IMS management of ACBs (SystemDefinition)Related referenceIMS Catalog Populate utility (DFS3PU00)(System Utilities)

DFS4891E THE DFS3PU00 UTILITY FAILEDDUE TO AN UNKNOWN ERROR

ExplanationThe IMS™ Catalog Populate (DFS3PU00) utility faileddue to an unknown error.

System action:The IMS Catalog Populate utility terminates withreturn code 12 without performing the requestedfunction.








Output destination of message:The message is sent to DFS3PU00 utility job output.

System programmer response:Ensure that the JCL to run the IMS Catalog Populateutility is correct. If the problem persists, contact IBMSoftware Support.

Module:DFS3PU00


DFS4892E UNEXPECTED STATUS CODEsc RECEIVED FOR FUNCTIONfunction

ExplanationAn unexpected status code occurred while a functionis being processed.

This message can occur when you run the IMS CatalogPopulate utility (DFS3PU00) in a system that doesnot have the IMS database code installed, such as aDCCTL system.

In the message text:sc

Indicates the status code that occurred.function

Indicates the name of the function that was beingcalled.

System actionThe process terminates with a U0071 abend withreturn code 88.

Output destinationDFS3PU00 utility job output

System programmer response:Ensure that the proper environment is being used torun the process.

Module:DFS3PU00

DFS4894E AFTER ABEND OF MASTER IMSims_id THE TAKE OVER OF PSBAND DMB IMPORT PROCESSINGFAILED. REASON= reason_text

ExplanationThe IMS system that is identified in the ims_id fieldof the message text abended during the processing

of an IMPORT DEFN SOURCE(CATALOG) command.Another IMS system attempted to take over theprocessing, but the take over attempt failed.


The IMS system that abended.reason_text

Text that describes the reason for the failure.

System action:The IMPORT DEFN SOURCE(CATALOG) commandfailed.


System programmer response:Correct the error identified in the reason text.You can issue the QUERY MEMBER TYPE(IMS)SHOW(STATUS) command to determine the statusof activation processing and, if necessary, how torespond.

Module:DFSOLC80


DFS4895E AFTER ABEND OF MASTER IMSims_id THE TAKE OVER OF THEDDL DEFINITION ACTIVATIONFAILED. REASON= reason_text PSTpst_name

ExplanationThe master IMS system that is identified in the ims_idfield of the message text abended during the activationprocessing of DDL-defined resources. Another IMSsystem attempted to take over the processing, but thetake over attempt failed.




reason_textText that describes the reason for the failure.

System action:The activation of the DDL-defined resources failed.







Correct the error identified in the reason text.You can issue the QUERY MEMBER TYPE(IMS)SHOW(STATUS) command to determine the statusof activation processing and, if necessary, how torespond.

Module:DFSOLC80


DFS4896I IMPORT DEFN SOURCE(CATALOG)PROCESSED ONE ORMORE RESOURCES, COMMANDTOKEN=command_token

ExplanationIf the IMPORT DEFN SOURCE(CATALOG) commanddoes not detect any prepare phase errors, DFS4896I isissued at each sharing IMS system indicating IMPORTDEFN SOURCE(CATALOG) is in progress.

command_token is the 8-byte command token thatcan be used to find its associated 70 log records in theIMS log data sets.

System action:IMS continues the IMPORT DEFN SOURCE(CATALOG)processing.

System programmer responseDFS4896I is the first of two messages issuedfor IMPORT DEFN SOURCE(CATALOG) command.DFS4896I is issued at each sharing IMS system whenthere is no prepare phase error detected.

If the command is successful, DFS4897I is the secondof the two messages issued that indicates that thecommand completed.

If the command fails, DFS4898E is the second of thetwo messages that indicates that the command failed.

For processing details, see the IMPORT DEFNSOURCE(CATALOG) command log, commandresponse, and its associated 70 log records that isidentified by the command_token in the IMS log datasets.

Module:DFSOLC70

DFS4897I IMPORT DEFN SOURCE(CATALOG)COMPLETED, COMMANDTOKEN=command_token

ExplanationIMPORT DEFN SOURCE(CATALOG) commandprocessed one or more resources and the import

command completed successfully. DFS4897I is issuedat each sharing IMS system.

The command_token is the 8-byte command token canbe used to find its associated 70 log records in the IMSlog data sets.

System action:IMPORT DEFN SOURCE(CATALOG) commandsuccessfully imported one or more resources.

System programmer responseDFS4897I is the second of two messages issuedfor IMPORT DEFN SOURCE(CATALOG) command thatindicates that the command completed successfully.


Module:DFSOLC00, DFSOLC20

DFS4898E IMPORT DEFN SOURCE(CATALOG)FAILED, COMMANDTOKEN=command_token

ExplanationIMPORT DEFN SOURCE(CATALOG) commandprocessed one or more resources, but the commandencountered an error, and the import process failed.DFS4898E is issued at each sharing IMS system.

The command_token is the 8-byte command tokenthat can be used to find its associated 70 log recordsin the IMS log data sets.

System action:IIMPORT DEFN SOURCE(CATALOG) encountered anerror, and the command failed.

System programmer responseDFS4898E is the second of two messages issuedfor IMPORT DEFN SOURCE(CATALOG) command. Thecommand encountered an error, and the commandfailed.


Module:DFSOLC00, DFSOLC20

DFS4899W GSAMPCB WAS SPECIFIED ONTHE MANAGEDACBS CONTROL



STATMENT BUT NO GSAMRESOURCES FOUND

ExplanationThe Catalog Populate utility runs as DLI using PSBDFSCP001. The GSAMPCB parameter was specifiedon the MANAGEDACBS= control statement to indicatethe GSAM resources that were included so that thecatalog members information gather task does not usethe IEFRDER batch log data set. However, no GSAMresources were found.

System action:The Catalog Populate utility continuous without batchlogging.

System programmer responseIf the Catalog Populate utility completes successfully,no action is needed.

If the Catalog Populate utility fails, resolve thereported error that caused the utility failure andrerun the utility. To request batch logging, removethe GSAMPCB parameter on the MANAGEDACBS=control statement to show that no GSAM resources areincluded.

Module:DFS3PU00




DFS4901E THE LOAD FOR DFSMDA MEMBERname FAILED FOR IMS CATALOGHLQ. REASON=reason_text

ExplanationWhen IMS attempted to access the IMS directory datasets of the IMS catalog, an error occurred when IMSattempted to retrieve the high-level qualifier of theIMS directory data sets from an IMSCATHLQ DFSMDAmember.


The name of the IMSCATHLQ DFSMDA macrostatement that defines the high-level qualifier ofthe IMS directory data sets.

If the error occurred when the IMS Catalog LibraryBuilder utility (DFS3LU00) was running, the namethat is displayed in the message is the value thatis specified on the IMSCATHLQ control statementin the utility JCL. The name that is specified onthe IMSCATHLQ control statement must match thename that is specified on the DDNAME parameterof the IMSCATHLQ DFSMDA member that containsthe HLQ of the IMS directory data sets.

If the error occurred when an application programattempted to access a GSAM database, the namethat is displayed is the alias name of the IMScatalog with HLQ appended. IMS uses this valueto retrieve the IMSCATHLQ DFSMDA member thatdefines the HLQ of the IMS directory data sets.The alias name is specified in either the CATALOGsection of the DFSDFxxx PROCLIB member or inthe DFS3CDX0 exit routine.

reason_textThe reason can be one of the following strings:GETMAIN FAILURE

A request for storage failed.DFSMDA MEMBER NOT FOUND

A DFSMDA member that matches the MDAmember name displayed in the message textcould not be found.

BLDL ERRORAn error occurred during a BLDL macro call forthe DFSMDA member.

INVALID DFSMDA MEMBERThe DFSMDA member that is identified in themessage text contains an error. Check theDFSMDA statements that define the member.

LOAD ERRORAn error occurred while attempting to load theDFSMDA member.

BSDS FAILED OPENThe boot strap data set of the IMS directoryfailed to open.

BSDS FAILED ALLOCThe boot strap data set of the IMS directoryfailed to allocate.

System action:The process terminates abnormally.


System programmer response:Correct the error and resubmit the job.

Module:DFS3LU00, DFS3LU10, DFS3LU20, DFS3DF00,DFS3DF10

DFS4902W UNABLE TO CLOSE THE CATALOGDIRECTORY

Explanation:An attempt was made to close the IMS directorydata set during GSAM initialization. This message isreturned when the IMS directory data set cannot beclosed.

System action:The IMS dependent region continues to run with theIMS directory data set open.

System programmer response:Check for error messages, such as z/OS messageIEC2xxI, that might indicate the cause of the problem.After the error is corrected, restart the dependentregion.

Module:DFSZDI00

DFS4913E IMS DIRECTORY NOT CLEANEDUP AFTER IMS ims_idABENDED AND THIS IMSCANCELLED ACTIVATION OF DDLDEFINITIONS. PST pst_name.


ExplanationThe master IMS ims_id abended while activating DDL-defined resources. Another IMS system took overprocessing and this IMS aborted the DDL activation ,but the clean up of the IMS directory could not bedone.




System action:The automatic activation for DDL definition statementswas aborted.



Module:DFSOLC80


DFS4930I OTMA ENDED CONVERSATIONALTRANSACTION CONVID=convIDFOR TMEMBER/TPIPEtmember_name/tpipe_name

ExplanationA conversational transaction was ended by IMS OpenTransaction Manager Access (OTMA) because thetransaction is idle, and IMS resources that wereallocated to the transaction are released.

In the message text:convID

The ID of the conversational transaction.tmember_name

The name of the OTMA target member (tmember).tpipe_name

The name of the transaction pipe (tpipe) queuethat holds the conversational transaction.

System action:IMS processing continues.

Output destination of message:This message is sent to the z/OS system console.


Tip: To control the timeout interval for idleconversational transactions and to ensure resourcesthat were allocated to the idle transactions areremoved from IMS storage, specify a value for theENDCONV= parameter in the DFSOTMA descriptor ofthe DFSYDTx member of the IMS PROCLIB data set.

Module:DFSYTIB0

Related referenceDFSOTMA descriptor syntax and parameters(System Definition)

DFS4934I CATALOG IMPORT COMMAND INPROGRESS ON IMS ims_id. WAITFOR COMPLETION.

ExplanationA PSB that is used by this batch job is being modifiedby an IMPORT DEFN SOURCE(CATALOG) commandon the IMS system identified in the ims_id field of themessage text.


The IMS system that is processing the IMPORTDEFN SOURCE(CATALOG) command that ismodifying the PSB.

System action:The batch job waits for the IMPORT DEFNSOURCE(CATALOG) command to complete.

Output destination of message:The message is sent to the z/OS system console forthe batch job.

System programmer response:No action is necessary; however, to check thestatus of IMPORT command processing you can issuethe QUERY MEMBER TYPE(IMS) SHOW(STATUS)command.

Module:DFSBIND0


DFS4965E CSVQUERY FOR MODULE xxxxxxxxFAILED WITH RC=yyyy




http://www.ibm.com/support/knowledgecenter/SSEPH2_15.1.0/com.ibm.ims15.doc.sdg/ims_dfsydtx_proclib_dfsotma_dscrp.htm#ims_dfsydtx_proclib_dfsotma_dscrp



xxxxxxxxIs a module in the MODBLKS data set.

yyyyIs a return code.

The CSVQUERY request was issued by IMS at coldstart to determine the size of a module xxxxxxxx in theMODBLKS data set, but the request failed with returncode yyyy.



System programmer response:Use the return code yyyy to determine why theCSVQUERY request failed and to correct the problem.Then, cold start IMS.

Problem determination:1,4

Module:DBFRRT00, DFSRDB00, DFSRPG00, DFSRTR00


DFS4994I nnnnnn MESSAGE(S) MOVED TOTHE type COLD QUEUE DURINGIMS/CQS RESYNC

ExplanationDuring IMS/CQS resync, IMS attempts to resolve thestatus of messages that CQS has moved to the coldqueue. In some cases, the status cannot be resolvedbecause there is not enough information on the IMSand CQS logs. When this happens, IMS leaves themessages on the cold queue. This can occur when:

• IMS is cold started (messages are in COLD status), or• The double-failure situation occurs where both the

structure fails (and has to be rebuilt from the log)and CQS also fails (messages are in UNKNOWNstatus).

IMS issues the DFS4994I message when one or moremessages is in either "COLD" or "UNKNOWN" statusand is left on the CQS cold queue.

In the message text:nnnnnn

A six digit decimal number indicating the numberof messages that were moved to the cold queue.

typeThe IMS structure type - either MSGQ for theshared message queue structure, or EMHQ forthe shared expedited message handler queuestructure.


System programmer response:Messages on the CQS cold queue may or may not havebeen processed by the prior instance of IMS. You canuse a queue management tool (for example, the IBMIMS Queue Control Facility for z/OS or equivalent) toexamine the messages on the cold queue and eitherdelete or unlock them as appropriate.

Module:DFSSQ030, DBFSQ030

DFS4997I AFTER ABEND OF MASTER IMSims_id THIS NEW MASTER IMSABORTED THE ACTIVATION OFDDL-DEFINED RESOURCES. PSTpst_name.

ExplanationThe IMS system that is identified in the ims_id fieldof the message text abended while processing thecoordinated activation of DDL-defined resources. ThisIMS system took over the processing and aborted theactivation of the resources.




System action:IMS aborts the activation of the DDL-definedresources.


System programmer response:Resubmit the DDL statements for activation. To checkthe status of activation processing, you can issuethe QUERY MEMBER TYPE(IMS) SHOW(STATUS)command.

Module:DFSOLC80


DFS4998I AFTER ABEND OF MASTER IMSims_id THIS NEW MASTER IMSCOMMITTED THE ACTIVATION OFDDL-DEFINED RESOURCES. PSTpst_name.




ExplanationThe IMS system that is identified in the ims_id fieldof the message text abended while processing thecoordinated activation of DDL-defined resources. ThisIMS system took over the processing and committedthe activation of the resources.




System action:The activation of the DDL-defined resourcescompletes.



Module:DFSOLC80

DFS4999I AFTER ABEND OF MASTER IMSims_id THIS NEW MASTER IMSABORTED IMPORT COMMANDPROCESSING.

ExplanationThe master IMS system that is identified inthe ims_id field of the message text abendedduring the processing of a global IMPORT DEFNSOURCE(CATALOG) command. This IMS system tookover the processing and aborted the updates to thecatalog directory data sets.



System action:IMS aborts the processing of the IMPORT DEFNSOURCE(CATALOG) command.


System programmer response:Resubmit the command.

Module:DFSOLC80

DFS5000I AFTER ABEND OF MASTER IMSims_id THIS NEW MASTER IMSCOMMITTED IMPORT COMMANDPROCESSING.

ExplanationThe master IMS system that is identified inthe ims_id field of the message text abendedduring the processing of a global IMPORT DEFNSOURCE(CATALOG) command. This IMS system tookover the processing and committed the updates to theIMS catalog directory data sets.



System action:The IMPORT DEFN SOURCE(CATALOG) commandcompleted.



Module:DFSOLC80




DFS5002I RECOVERY UTILITY WAITS FORIRLM RECONNECT TO PROCEEDWITH CLEANUP OF DIRECTORY

ExplanationIRLM was not active when the utility is running.

System actionThe batch recovery utility waits for IRLM to reconnectto proceed.

Programmer responseRestart IRLM and modify the IMS system to reconnectto IRLM.

Module:DFSOLC80

DFS5003I BATCH DIRECTORY CLEANUPUTILITY COMPLETE

ExplanationThe recovery utility to clean up the directory wassuccessful.

System action:No action.

Output destinationThe systems console

Module:DFSPCC30

DFS5004I IMS DIRECTORY RECOVERYUTILITY ABORTED UPDATESMADE BY IMPORT DEFNSOURCE(CATALOG) COMMAND ONims_idDFS5004I TOKEN=token_id

ExplanationIMS ims_id abended in the middle of processing anIMPORT DEFN SOURCE(CATALOG) command. An IMSdirectory recovery utility was run and the cleanupto the directory data sets was successfully. A list ofresource names that were backout from the directorydata sets can be extracted from the log x7002. Run

the DFSERA30 utility with the following control card toprint out the log x7002.

OPTION PRINT OFFSET=13,FLDTYP=X,FLDLEN=8,VALUE=token_id

System actionThe IMPORT DEFN SOURCE(CATALOG) commandwas aborted.

System programmer responseRun the IMPORT DEFN SOURCE(CATALOG)command again.

Module:DFSOLC80

DFS5005I IMS DIRECTORY RECOVERYUTILITY ABORTED UPDATESMADE BY DDL DEFINITIONACTIVATION PST pst_name onims_idDFS5005I TOKEN=token_id

ExplanationIMS ims_id abended in the middle of processing aDDL definition activation for PST pst_name. An IMSdirectory recovery utility was run and the cleanupto the directory data sets was successful. A list ofresource names that were backout from the directorydata sets can be extracted from the log x7002. Runthe DFSERA30 utility with the following control cardsto print the log x7002.


System actionThe DDL DEFINITION activation was aborted.

System programmer responseRun the DDL DEFINITION activation command again.

Module:


DFSOLC80

DFS5006I IRLM IS NOT ACTIVE ANDCATALOG LOCK NOT OBTAINEDFOR UPDATES TO DIRECTORY

ExplanationThe internal resource lock manager (IRLM) is notactive when the IMPORT DEFN SOURCE (CATALOG)command or DDL definition activation process is inprogress. The IMS directory data sets are not cleanedup.


Output destinationThe z/OS system console

Programmer response:Issue the QUERY MEMBER TYPE(IMS)SHOW(STATUS) command to determine the status ofactivation processing and how to respond.

Module:DFSOLC80

DFS5006W IRLM IS NOT ACTIVE ANDCATALOG LOCK NOT OBTAINEDFOR UPDATES TO DIRECTORY

ExplanationThe master IMS system abended duringthe processing of either an IMPORT DEFNSOURCE(CATALOG) command or DDL statements.This IMS system attempted to take over processing,but could not get a lock on the IMS catalog directorybecause IRLM was not active. The directory data setswere not cleaned up.

System action:Cleanup processing continues locally, but the IMSdirectory was not cleaned up.


System programmer response:Check the status of activation processing by issuingthe QUERY MEMBER TYPE(IMS) SHOW(STATUS)command and take any actions necessary as requiredby the displayed status.

Module:DFSOLC80

DFS5007I {PSB | DBD} (psbname | dbdname)EXTENDED OPERAND TABLE SIZE= xxxxxxxx BYTES

Explanation:The PSB or DBD named in the message has beeninserted or replaced in the ACBLIB. The member hasxxxxxxxx bytes of database metadata for the IMScatalog stored in the external operand table.

System action:None.

System programmer responseTo estimate the total size of the member that is storedin the ACBLIB, complete one of the following tasks:

• Add the control block size that is contained inmessage DFS0940I to the size of the extendedoperand table that is displayed in messageDFS5007I.

• See the member with this name that was generatedby ACBGEN to the ACBLIB.

Module:DFSUAMB0

Related informationDFS0940I (Messages and Codes)

DFS5008W CATALOG RESOURCE IGNOREDFOR PSB=ALL psb_member

ExplanationIn an environment where the IMS managementof application control blocks (ACBs) is enabled,the Application Control Blocks Maintenance utility(DFSUACB0) is run with PSB=ALL specified andan IMS catalog program specification block (PSB)is encountered during application control blockgeneration. The PSB member is ignored and is notgenerated to the IMS.ACBLIB data set.

In the message text:psb_member

The PSB member that is ignored.


Output destinationThe job log of the Application Control BlocksMaintenance utility (DFSUACB0)



System programmer responseTo generate the PSB member to the IMS.ACBLIB dataset for the IMS catalog, specify the names of the PSBson the PSB= statement.

Module:DFSUACB0

DFS5010I IMS DIRECTORY RECOVERYUTILITY COMMITTED UPDATESMADE BY IMPORT DEFNSOURCE(CATALOG) COMMAND ONims_idDFS5010I TOKEN=token_id

ExplanationIMS ims_id abended in the middle of processing anIMPORT DEFN SOURCE(CATALOG) command. An IMSdirectory recover utility(DFS3RU00) was run and thedirectory data sets were cleaned up successfully. Alist of resource names that were committed to thedirectory data sets can be extracted from the logx7002. Run the DFSERA30 utility with the followingcontrol card to print the log x7002.


System actionThe IMPORT DEFN SOURCE(CATALOG) commandwas committed.


Module:DFSOLC80

DFS5011I IMS DIRECTORY RECOVERYUTILITY COMMITTED UPDATESMADE BY DDL DEFINITIONACTIVATION PST pst_name ONims_idDFS5011I TOKEN=token_id

ExplanationPSt pst_name abended in the middle of processing aDDL definition activation. An IMS directory recoveryutility was run and the cleanup of the directory datasets were successfully. A list of resource names thatwere committed to the directory data sets can beextracted from the log x7002. Run the DFSERA30

utility with the following control cards to print the logx7002.

OPTION PRINT OFFSET=5,FLDTYP=X,FLDLEN=2,VALUE=7002


System actionThe DDL DEFINITION activation command wascommitted.


Module:DFSOLC80

DFS5013I DDL DEFINITION ACTIVATION INPROGRESS. PST pst_name ON IMSims_id. WAIT FOR COMPLETION.

ExplanationA PSB that is used by this batch job is being changedonline by DDL statements that are being processed bythe IMS system identified in the ims_id field of themessage text.


The IMS system that is processing the DDLstatements.


System action:The batch job waits for the DDL definition activationprocess to complete.

Output destination of message:The message is sent to the z/OS system console forthe batch job.

System programmer response:No action is necessary; however, to check the status ofthe processing of the DDL statements you can issuethe QUERY MEMBER TYPE(IMS) SHOW(STATUS)command.

Module:DFSBIND0




DFS5055I RESTART LOG RECORD READ PASSn status; LSN=lsn

ExplanationThe IMS emergency restart or normal restart logread is in progress or is completed. This messageis issued when the IMS log is first read at IMSrestart, then every 30 seconds after that to indicateprogress, displaying the log sequence number of thelog record just read. The IMS log contains log recordswith log sequence numbers that increase by 1 foreach subsequent log record. The DFS5055I messageis issued a final time when the log read process iscomplete.

In the message text:n

The restart log read pass number, which can eitherbe 1 or 2 for emergency restart, or 1 for normalrestart.

Normal restart reads through the IMS log onlyonce, so this value is 1.

Emergency restart (except for /ERE COLDSYS)reads through the IMS log twice. Pass 1 processesthe MODBLKS resource (DDIRs, PDIRs, RCTEs,and SMBs) checkpoint log records (type4004,type4006, type4007, type4083) to create theMODBLKS resource control blocks before applyinglog records to those resource control blocks. Pass2 processes the remaining log records to returnIMS to its state before IMS went down. Pass 2starts over reading from the beginning of the log,so the log sequence number might be lower thanthe last log sequence number seen in pass 1.The type40 log records processed in pass 1 areskipped in pass 2.

statusThe restart log read status.

IS IN PROGRESS means the restart log readprocess is in progress for PASS 1 or PASS 2.

HAS COMPLETED means that the restart log readprocess is completed for PASS 1 or PASS 2.

lsnThe log sequence number (LSN), which is ahexadecimal log sequence number that identifiesan individual log record. Each IMS log recordcontains its unique log sequence number at theend of the log record. An underscore is printedto separate the two halves of the 8-byte LSN forreadability even though the LSN does not containan underscore.

An example log sequence number is00000000_00000171.

The first DFS5055I message that is issued whenIMS reads the log does not display a log sequencenumber of 00000000_00000001 because loggerand statistics log records that are not needed forrestart come before the first type40 checkpoint logrecord on the IMS log. These include log recordssuch as type42, type06, type43, type48, type27,and type45.

System action:IMS restart continues to read and process log records.

Output destinationThis message appears on the write-to-operator (WTO)terminal.

Operator responseIf IMS restart is making progress, no action is required.

If this message does not appear at regular 30-secondintervals, IMS restart is not making progress. IMSrestart might be hung. Take a dump of the IMS systemand contact IBM support.

Module:DFSRLP00

DFS5060I STOP REGION COMMAND NOTPROCESSED FOR REGION nnnnn;REASON TEXT=xxxxxx{UP TO 32BYTES OF MESSAGE}

ExplanationA /STOP REGION command for the dependent regiondid not complete successfully. The reason text willindicate the reason of the error.

AnalysisFor a reason text of REGION-STATUS-INVALID, The /STOP REGION ABDUMP FORCE command was issuedfor a region not in WAIT-INIT-INPROG or TERM-PENDING status.

System actionThe entered command is ignored. The IMS andthe dependent region, which is identified by nnnnn,continue running.

Programmer responseIssue a /DIS ACTIVE REGION command and issuethe appropriate command for stopping the region notin WAIT-INIT-INPROG or TERM-PENDING status.


ModuleDFSSTOP0

DFS5386I OTMA IS DISCONNECTING FROMMEMBER tmembername

ExplanationIMS Open Transaction Manager Access (OTMA)received a disconnection request from an OTMA targetmember (tmember).

IMS automated operator interface (AOI) exits can usethis message to identify whether an OTMA tmemberhas disconnected from OTMA.

In the message text:tmembername

The z/OS cross-system coupling facility (XCF)member name of the OTMA tmember.

System action:OTMA stops XCF communication with the tmember.

Output destination:This message appears on the IMS master terminal andthe write-to-operator (WTO) terminal.





DFS7411I OTMA lightweight TPIPE functionis activated. TPIPE weightingfactor (WGF) is nn%.

ExplanationThe OTMA lightweight tpipe support is enabled afterthe user specifies LITETP=YES in the DFSYDTxIMS.PROCLIB member. This support allows lessstorage to be used for tpipes that are created ina shared queues back-end IMS system to processfront-end input transactions. Because of the reductionin storage size, a weighting factor (WGF) is used tocalculate the adjusted tpipe count for tpipe floodcontrol.


The percentage of the weight factor, which isused in calculating the adjusted tpipe count fortpipe flood control. It is also the percentage ofthe storage size that a lightweight tpipe uses incomparison to a regular tpipe. This percentage isusually 28%, which means a lightweight tpipe uses28% of the storage size that a regular tpipe uses.

System action:None.




DFS7412I ADJUSTED OTMA TPIPE COUNTFOR MEMBER member IS nnnnnnn(FETP=xxxxxxx, BETP=yyyyyyy,WGF=zz%).

ExplanationThe DFS7412I message is an additional informationalmessage that is issued after an OTMA member’s flood-related messages are issued, such as DFS4382W,DFS4383E, or DFS4384I. It shows the adjustedmember tpipe count that is used for detecting theflood condition for the specified OTMA member.

This message is issued only after the OTMA lightweighttpipe function is enabled by specifying LITETP=YES inthe DFSYDTx member of the IMS.PROCLIB data set.

In the message text:member

The OTMA client member.nnnnnnn

The adjusted tpipe count that accounts for the lessstorage used by back-end tpipes.

This value is calculated as follows:

adjusted tpipe count = xxxxxxx + (yyyyyyy * zz)

xxxxxxxThe front-end tpipe count.

yyyyyyyThe back-end tpipe count.

zzThe percentage of the weighting factor incalculating the adjusted tpipe count for tpipe floodcontrol.

System action:None.




DFS7413I ADJUSTED GLOBAL OTMATPIPE COUNT IS nnnnnnn(FETP=xxxxxxx, BETP=yyyyyyy,WGF=zz%).

ExplanationThe DFS7413I message is an additional informationalmessage issued after global flood-related messagesare issued, such as DFS4515W, DFS4516E, DFS4517I,DFS4385W, or DFS4386I. It shows the adjusted globaltpipe count that is used for detecting global floodcondition.

This message is issued only after the OTMA lightweighttpipe function is enabled by specifying LITETP=YES inthe DFSYDTx member of the IMS.PROCLIB data set.







The adjusted global tpipe count that accounts forthe less storage used by back-end tpipes.

This value is calculated as follows:

adjusted tpipe count = xxxxxxx + (yyyyyyy * zz)

xxxxxxxThe front-end tpipe count.

yyyyyyyThe back-end tpipe count.

zzThe percentage of the weighting factor incalculating the adjusted tpipe count for tpipe floodcontrol.

System action:None.




DFS7414I INSTANCE yydddhhmmssth OFGSAM DBD|PSB name IS ALREADYIN THE IMS CATALOG AND WASNOT ADDED.

Explanation:The IMS Catalog already contained a root segment forthe GSAM DBD or PSB name, and under this root, therewas an existing GSAM DBD or PSB segment with thetimestamp yydddhhmmssth. Because GSAM DBDs orPSBs with the same name and the same timestampare assumed to represent identical instances of theGSAM DBD or PSB, nothing was added to the catalog.


System programmer response:No action is required.

Module:DFS3PU00

DFS7415I INSTANCE yydddhhmmssth OFGSAM DBD|PSB name NOTADDED TO THE IMS Catalog.LATER INSTANCE yydddhhmmssthEXISTS.

ExplanationIn a managed ACB environment, this GSAM membername with timestamp yydddhhmmssth was not addedto the IMS Catalog because the later instance withtimestamp yydddhhmmssth already exists in the IMSCatalog and directory.


The GSAM member name.yydddhhmmssth

The timestamp of the GSAM member that was notinserted to IMS Catalog.

yydddhhmmssth represents the timestamp in theformat of yy for year, ddd for day, hh for hour, mmfor minutes, ss for seconds, and th for thousands ofa second.

yyddhhmmssthThe timestamp of the active GSAM member that isalready in the IMS Catalog and directory.

System action:Execution of the IMS Catalog Populate utility continuesand the job finishes with a return code of 4.

System programmer response:To override this behavior, specify UNCOND in the inputcontrol statements for the IMS Catalog Populate utilityin a data set that is referenced by the ddname SYSINP.

Module:DFS3PU00

DFS7416I INSTANCE yydddhhmmssth OFGSAM DBD|PSB name IS ALREADYIN THE IMS CATALOG DIRECTORYAND WAS NOT ADDED

ExplanationThe IMS Catalog directory already contains anexisting GSAM member name with timestamp ofyydddhhmmssth, so this member was not added to orreplaced in the directory.


The member name in the directory.yydddhhmmssth

The timestamp of the GSAM member that wasrejected for inclusion in the directory.





System action:Execution of the IMS Catalog Populate utilitycontinues.

System programmer response:No action is required. However, to suppress thisand other similar informational messages, specifyNODUPLIST in the input control statements for theIMS Catalog Populate utility in a data set that isreferenced by the ddname SYSINP.

Module:DFS3DU10

DFS7417I INSTANCE yydddhhmmssth OFGSAM DBD|PSB name NOT HELDFOR DIRECTORY IMPORT. IT ISALREADY IN THE IMS DIRECTORY

ExplanationThe IMS Catalog directory already contains anexisting GSAM member name with timestampyydddhhmmssth, so the GSAM member name with thesame timestamp was not copied to the IMS Catalogdirectory staging data set as a replacement for thedirectory member.


The GSAM member name.yydddhhmmssth

The timestamp of the GSAM member that isalready in the IMS catalog directory.


System action:Execution of the IMS Catalog Populate utilitycontinues.

System programmer response:No action is required. However, to suppress thisand other similar informational messages, specifyNODUPLIST in the input control statements for theIMS Catalog Populate utility in a data set that isreferenced by the ddname SYSINP.

Module:DFS3DU10

DFS7419E INSTANCE yydddhhmmssth OFGSAM DBD name IS ALREADY INTHE IMS CATALOG


nameThe GSAM database name.

yydddhhmmssth

The time stamp of the GSAM DBD that was notinserted to the IMS catalog.

yydddhhmmssth represents the time stamp in theformat of yy for year, ddd for day, hh for hour, mmfor minutes, ss for seconds, and th for thousandthsof a second.

The IMS catalog already contains a root segment forthe GSAM DBD name, and under this root, there wasan existing GSAM DBD segment with time stamp ofyydddhhmmssth.

Because a GSAM DBD with the same name and thesame time stamp are assumed to represent identicalinstances of the GSAM DBD, nothing was added to theIMS catalog.

System action:The DFS3PU00 continues, and the job finishes withreturn code 12.

System programmer responsePerform a DBDGEN on the GSAMdatabase that is specified onthe MANAGEDACBS=(STAGE,GSAM=dbname) orMANAGEDACBS=(UPDATE,GSAM=dbname) controlcard.

Important: The DBDGEN time stamp precision is onlyto the minute (MM/DD/YYHH.MM). Therefore, changesto the same GSAM DBD should not be done until afterone minute.

Module:DFS3PU00

DFS7420E GSAM DBD name IS NOT IN THEDBDLIB. THE BLDL RC = rc. THEDBD WAS NOT ADDED TO THECATALOG

ExplanationThe GSAM DBD specified in the GSAM parameter doesnot exist in the DBDLIB.


The GSAM database name.rc

The return code returned by the DFS3PU00 utilityfrom BLDL macro call.

System action:The IMS Catalog Populate utility DFS3PU00 fails withreturn code 12.


System programmer response:Rerun the DFS3PU00 utility with a DBDLIB on the IMSDD card that contains the DBD specified on the GSAMparameter of the MANAGEDACBS control statement.

Module:DFS3PU00

DFS7421E THE MANAGEDACBS CONTROLSTATEMENT DOES NOT SUPPORTTHE GSAM PARAMETER

ExplanationThe GSAM parameter on the MANAGEDACBS controlcard that is specified with the STAGE or UPDATEparameter is only valid for the DFS3PU00 utility.DFS3UACB does not support the GSAM parameterwith the MANAGEDACBS control statement becauseACBGEN is not required for a GSAM database.

System action:The DFS3UACB utility ended with return code 12.

System programmer response:Remove the GSAM parameter from theMANAGEDACBS control statement, or run the CatalogPopulate utility (DFS3PU00) instead with the GSAMparameter specified in the STAGE or UPDATEparameter.

Module:DFS3PU00

DFS7422E DBD name SPECIFIED ONTHE GSAM PARAMETER OFTHE MANAGEDACBS CONTROLSTATEMENT IS NOT A GSAM DBD

ExplanationThe GSAM parameter on the MANAGEDACBS controlcard that is specified with the STAGE or UPDATEparameter is only valid for a GSAM database.


The non-GSAM DBD name.

System action:The DFS3PU00 utility ended with return code 12.

System programmer response:Run the Catalog Populate utility (DFS3PU00) with aGSAM DBD specified on the GSAM parameter of theMANAGEDACBS control statement parameter.

Module:DFS3PU00

DFS7423E IF START= OR END= PARAMETERIS SPECIFIED, STARTDAY=

OR ENDDAY= PARAMETER ISREQUIRED.

ExplanationThe IMS Fast Path Log Analysis utility, DBFULTA0,expects the STARTDAY= parameter if the START=parameter is provided. The utility also expectsthe ENDDAY= parameter if the END= parameter isspecified.

System action:Execution terminates.

System programmer response:Correct the input parameters as required.

DFS7424E IF STARTDAY= PARAMETER ISSPECIFIED, START= PARAMETERIS REQUIRED

ExplanationThe IMS Fast Path Log Analysis utility, DBFULTA0,expects the START= parameter if the STARTDAY=parameter is specified.

System action:Execution terminates.

System programmer response:Correct the input parameters as required.

DFS7429E CATALOG RESOURCE NOT FOUNDFOR CATRSCS=YES, catalog-psb

ExplanationThe Application Control Blocks Maintenance utilityfound that an IMS catalog PSB is missing fromthe PSB library when the utility runs with BULDPSB=ALL,CATARSCS=YES.

In the message text:catalog-psb

The name of the IMS catalog PSB that is missingfrom the PSB library.


Output destination

The job log of the Application Control BlocksMaintenance utility(DFSUACB0).

System programmer response:Ensure that the PSB library contains all the IMScatalog PSBs. If all the IMS catalog PSBs are in thePSB library, rerun the job.

Module:


DFS3PU00

DFS7430W CATALOG RESOURCE catalog-resource IS NOT PROCESSEDWHEN MANAGEDACBS=STAGE.

ExplanationThe IMS Catalog Populate utility found that the catalogresources other than DFSCD000 exist in the ACBLIBwhen STAGE is specified on the MANAGEDACBS utilitycontrol statement.

In the message text:catalog-resource

The name of the IMS catalog PSBs, DFSCPL00,DFSCP000, DFSCP001, DFSCP002, DFSCP003, orthe IMS catalog DBD, DFSCX000 that are in theACB library.

System action:The utility continues processing but generates a returncode of 4.

System programmer response:No action is required.

Module:DFS3PU00

DFS7431I IFAWIC connection failed - RC=xxxxxxxx, RSN= yyyyyyyy

ExplanationIMS attempted to register with IBM z/OS WorkloadInteraction Correlator and received a nonzero returncode xxxxxxxx with a reason code yyyyyyyy. The valuefor xxxxxxxx can be one of the following values:

RC 00000004The combined length of the persistent componentand activity areas, together with the BPE overhead,was larger than the maximum number of pagesthat are allowed for an IBM z/OS WorkloadInteraction Correlator buffer. An IBM z/OSWorkload Interaction Correlator buffer currentlyallows 16 4K pages at maximum. For INITMT, thereason might also be either one of the lengths ofthe persistent component or activity areas, or thelengths of both, were negative.

RC 00000008One or both of the persistent component lengthand activity areas length were not a multiple of 16.The length is required to be a multiple of 16 topreserve quadword alignment for instructions likeCDSG. This return code is only for INITMT.

RC 0000000CThe SMF 98 subtype value was zero. This returncode is only for INITMT.

RC 00000010The address that was passed inBPEMTSRV_OUTBUFPTR was zero. This returncode is only for INITMT.

RC 00000030IBM z/OS Workload Interaction Correlator (Micro-Trend) services are not available on this system.

RC 00000034The LOAD request of BPEMTX00 failed. yyyyyyyycontains the return code from the LOAD request.

RC 00000038The LOAD request of BPEMTEN0 failed. yyyyyyyycontains the return code from the LOAD request.

RC 0000003CThe ENFREQ request for BPEMTEN0 failed.yyyyyyyy contains the return code from theENFREQ request.

RC 00000040IFAWIC registration received higher than a warningRC. yyyyyyyy contains the reason code returnedby IFAWIC. See the IFAWIC documentation inthe z/OS MVS Programming: Authorized AssemblerServices Reference EDT-IXG manual for details.

RC 00000044The BPEMTSRV call is not supported in a clonedcopy of BPE.

RC 000000F8The function requested is unknown.

RC 000000FCThe parmlist version is not supported byBPEMTSV0.

Note: This message will be suppressed when IMSruns on a pre-z14 machine, or if IBM z/OS WorkloadInteraction Correlator is not available, or both.

System actionIMS continues processing with no statics being passedto IBM z/OS Workload Interaction Correlator.

Programmer responseIf IBM z/OS Workload Interaction Correlatorparticipation is needed, see the return and reasoncodes to determine the cause of failure, fix theproblem and restart IMS.

Related informationz/OS: IFAWIC — IBM z/OS Workload InteractionCorrelator

DFS7432I DFS7432I xxxx ADDRESS SPACELEVEL RACF DB2 SECURITYREQUESTED FOR JOBNAME =zzzzzzzz


https://www.ibm.com/support/knowledgecenter/SSLTBW_2.4.0/com.ibm.zos.v2r4.ieaa200/IFAWIC.htm

https://www.ibm.com/support/knowledgecenter/SSLTBW_2.4.0/com.ibm.zos.v2r4.ieaa200/IFAWIC.htm

ExplanationAn IMS dependent region with jobname zzzzzzzz wasinitialized with RLA=Y for external subsystem (xxxx).This message is sent to system console and IMS MTO.

System actionThe dependent region address space level ACEEwill be passed to Db2 for ESAF calls ifESAF_SIGNON_ACEE and TCB level ACEE are notpresent.

Operator response:None

System programmer response:None


Module:DFSESD10

DFS7433E IMPORT PHASE phase FAILEDBECAUSE RM PROCESSSTEP SENT TO IMS imsidTIMED OUT, COMMANDTOKEN=command_token

ExplanationAn IMS IMPORT DEFN SOURCE(CATALOG) commandor DDL automatic import phase failed because the RMprocess step that was sent to the IMS to perform theonline change phase timed out. This can occur if SCI isdown, RM is down, or the IMS or RM could not respondto the RM process step in time. For the IMPORTcommand, the timeout value is the OM timeout valuethat is specified with the command.

In the message text:phase

A 4-character string that identifies the internalonline change phase that failed. If the phase isCMT2 or CMT3, the directory was successfullyupdated and the import was committed.

imsid

The ID of the IMS for which the RM request timedout. It is unknown whether the IMS participated inthis online change phase.

command_tokenThe 8-byte import start STCK time stamp that canbe used to find its associated 70 log records in theIMS log data sets.

System programmer responseIf the online change phase is CMT2 or CMT3, thedirectory update was successful and the import wascommitted. Issue the QUERY MEMBER TYPE(IMS)SHOW(STATUS) command to see the state of the IMSs.Issue the QUERY IMSPLEX SHOW(STATUS) commandto see whether any IMS, SCI, or RM address spacesare down.

Start IMS, SCI, or RM again, if applicable.

If one or more IMSs are in an online changestate of commit phase 2 or later, the directoryupdates are committed. Issue the IMPORT DEFNSOURCE(CATALOG) command that is routed to theprevious import command master to finish the importand get all of the IMSs out of an online change state.

For a DDL error, issue the DDL request again.

Module:DFSOLC00

Related conceptsWhat to do if the IMPORT DEFNSOURCE(CATALOG) command or DDL automaticimport times out in a managed ACBsenvironment (Operations and Automation)

DFS7434W UNEXPECTED AIB RETURN CODExxxx REASON CODE yyyy FORnnnnnnnn

ExplanationAn unexpected AIB return code was returned whileprocessing a GUR DL/I call. This message can occurwhen you run the IMS Catalog Recovery utility(DFS3RU00).


AIB return code.yyyy

AIB reason code.

nnnnnnnDBD or PSB for the GUR request.

System action:The utility continues processing with a return code of4.

System programmer response:Check the utility job output or system log for additionalmessages and to determine whether the object wasrecovered.

Module:DFS3RU00


http://www.ibm.com/support/knowledgecenter/SSEPH2_15.1.0/com.ibm.ims15.doc.oag/ims_15_import_status_after_command_timeout.htm#ims_15_import_status_after_command_timeout





DFS7435E VALIDATION FAILED FOR THEACBGEN CATALOG WORK FILE(DDNAME ACBCATWK)

ExplanationThe validation failed because one of the followingconditions occurred:Condition 1: concatenated data sets

The DD name ACBCATWK contains concatenateddata sets that are not supported by the IMSCatalog Populate utility.

Condition 2: insufficient working storageThere was a failure obtaining working storage forthe ACB generation work data set validation.

Condition 3: could not read the job file control blockThere was a failure reading the job file controlblock for the ACB generation work data setvalidation.


Programmer responseTake the following actions depending on the conditionthat occurred:Condition 1: concatenated data sets

Correct the ACBCATWK DD statement and run theIMS Catalog Populate utility again.

Condition 2: insufficient working storageContact IBM Software Support.

Condition 3: could not read the job file control blockContact IBM Software Support.

Module:DFS3PU00

DFS7436E STEPLIB IS NOT APF AUTHORIZED

ExplanationAll or some libraries on STEPLIB of the DEDB ALTERJOB are not APF-authorized.

System action:The DEDB Alter utility terminates with RC=8.

Operator response:No action is required.

System programmer response:APF authorize libraries on STEPLIB of the DEDB ALTERJCL and rerun.

DFS7438E SEQUENCE NUMBER ERROR ONTPIPE=tpipe MEMBER=member.TPIPE HAS BEEN STOPPED.

ExplanationA sequence number error occurred on an MQsynchronized tpipe. This error message is issuedbecause of one of the following reasons:

• Input sequence number is too high. This is issued byDFSYTIB0.

• Output sequence number is invalid and purge is notrequested. This is issued by DFSYACK0.

• Invalid sequence number during client-bidresynchronization. This is issued by DFSYMEM0.


The tpipe on which the error is detected.member

The OTMA client member on which the error isdetected.

System action:The tpipe is stopped. For more information, see MQCSQxxxxx error messages.

System programmer response:Use the MQ RESET TPIPE command to resetrecoverable sequence numbers and restart the tpipe.If required, use the MQ RESET TPIPE commandto resolve the unit of recovery. Refer to MQdocumentation for command syntax.

Module:DFSYACK0, DFSYMEM0, DFSYTIB0

Related referenceRESET TPIPE on z/OS

DFS7439E ERROR ATTACHING PROGRAMpgm-name. ATTACH RC=rc.

ExplanationAn MVS ATTACH macro instruction gave a return codeof rc when it attempted to attach a task to run aprogram.

In the message text:pgm-name

The name of the program that the DFS3RU00utility was attempting to attach when the erroroccurred.

rc

The return code received by the DFS3RU00 utilityfrom the z/OS MVS ATTACH macro.

System action:




https://www.ibm.com/docs/en/ibm-mq/9.2?topic=commands-reset-tpipe-zos

The DFS3RU00 utility ends with return code 16.

System programmer response:Look up the MVS ATTACH macro return code in thez/OS publications. Ensure that the JCL to run theDFS3RU00 utility is correct. If the problem persists,contact IBM Software Support.

Module:DFS3RU00


DFS7440W UNEXPECTED STATUS CODE sc ONA dli CALL FOR AN INSTANCE OFtype name

ExplanationAn unexpected DL/I status code was received on aDL/I call.

In the message text:sc

The status code that was received.dli

The DL/I call.

typeThe type of resource (DATABASE or PROGRAM).

nameThe name of the database or program.

System action:The utility continues processing with a return code of8.

System programmer response:Check the utility job output or system log for additionalmessages and to determine whether the object wasrecovered.

Module:DFS3RU00

DFS7441I xxxxxxxx DBD=aaaaaaaaaaa PSB=bbbbbbbbbbb RECOVERED: DBD=ccccccccccc PSB=ddddddddddd

ExplanationThis message is issued as a heartbeat message whilethe IMS Catalog Directory Recovery utility (DFS3RU00)is running.


ACTIVE or PENDING, which indicates whichobjects are being recovered.

aaaaaaaaaaa

The number of active or pending DBDs are to berecovered.

bbbbbbbbbbbThe number of active or pending PSBs are to berecovered.

cccccccccccThe number of active or pending DBDs that wereprocessed so far.

dddddddddddThe number of active or pending PSBs that wereprocessed so far.

System action:The utility continues processing.


Module:DFS3RU13

DFS7442W aaaaaaaaaaa bbbbbbbbbbbNOT RECOVERED. RELATEDccccccccccc ddddddddddd WASNOT eeeeeeeee.

ExplanationA resource cannot be recovered because a requiredrelated object is not being recovered.

In the message text:aaaaaaaaaaa

The type of resource: DBD or PSB.

bbbbbbbbbbbThe name of the resource.

cccccccccccThe related object type: DBD or PSB.

dddddddddddThe related object name.

eeeeeeeeeFOUND or RECOVERED indicates that the relatedobject was not found in the recover scope or thatthe related object was found but could not berecovered.

System action:The utility continues processing.

System programmer response:Take appropriate action as necessary to rebuild theunrecovered resource.

Module:DFS3RU1A




DFS7443E CATALOG RESOURCESUNAVAILABLE. UNABLE TO BRINGUP IMS.

ExplanationThe DFS7443E message is issued in a managedACB environment if IMS does not find the requiredIMS catalog DBD and PSB resources in the directoryduring IMS initialization. The resources that needto be present in the directory to bring up IMS areDFSCD000, DFSCP000, DFSCP001, DFSCX000, andDFSCPL00.

Operator response:Ensure that the following catalog data basedescriptors (DBDs) and program specification blocks(PSBs) are present in the directory: DFSCD000,DFSCP000, DFSCP001, DFSCX000, and DFSCPL00.

DFS7444E OTMA CANNOT PROCESS ARESUME TPIPE FOR TMEMBER/TPIPE xxxx/yyyy DUE TO A TIMINGERROR

ExplanationWhen OTMA ran into a timing error for the internalcontrol block creation for a RESUME TPIPE requestfrom a client such as IMS Connect, OTMA did a quickretry on the RESUME TPIPE request but failed.


The name of the OTMA client that sends theRESUME TPIPE request.

yyyyThe name of the transaction pipe (tpipe) to becreated.

System action:The RESUME TPIPE request is rejected with a NAKmessage with sense code x'28' and reason code x'07'.

Operator response:None.

System programmer response:Resubmit the RESUME TPIPE request from the OTMAclient.

Problem determination:Take an IMS dump to examine the tpipe related controlblocks for the client or use the OTMA trace bytes totrace the creation of the tpipe and its hold queue forthe timing error.

Module:DFSYMEM0

Related tasksOTMA diagnostic aids (Diagnosis)

DFS7445A IMPORT TIMED OUTAFTER DIRECTORY UPDATESCOMMITTED. CHECK IF IMPORTNEEDS TO BE RETRIED.

ExplanationThe IMPORT DEFN SOURCE(CATALOG) command orDDL automatic import timed out after the directoryupdates were committed.

Operator responseCheck whether the import succeeded by using one ormore of the following methods:

• Issue the QUERY MEMBER TYPE(IMS)SHOW(STATUS) command to see whether any IMSsremain in an online change state and if so, whetherthe online change is committed.

• Issue the QRY IMSPLEX SHOW(STATUS) commandto see whether any IMSs, SCIs, or RMs are downin the IMSplex. Timeouts can be caused by an IMSaddress space involved in the import failing.

If one or more IMSs are stuck in an online changestate, you can resolve this by doing the following tasks:

• Address the reason for the failure; for example, startSCI again, start RM again, or start other componentsthat failed.

• Issue the IMPORT DEFN SOURCE(CATALOG)command to finish the import and remove theIMSs out of an online change state. The IMPORTcommand should be routed to the IMS thatwas the import command master of the previousIMPORT DEFN SOURCE(CATALOG) command or DDLautomatic import that timed out because it knowsthe state of the import. This is the IMS that issuedthe DFS7445A message.

Module:DFSOLC00

Related conceptsWhat to do if the IMPORT DEFNSOURCE(CATALOG) command or DDL automaticimport times out in a managed ACBsenvironment (Operations and Automation)

DFS7447E CHKPT STATEMENT INVALID INIRLM ENVIRONMENT

Explanation:The CHKPT statement specified via SYSIN is not validwithin an IRLM environment.

System action:The Batch Backout utility (DFSBBO00) terminates withreturn code 8.


http://www.ibm.com/support/knowledgecenter/SSEPH2_15.1.0/com.ibm.ims15.doc.dgr/ims_otma_diag_aids.htm#ims_otma_diag_aids





Operator response:Resolve the CHKPT statement and the IRLMenvironment and restart the Batch Backout utility(DFSBBO00).

Programmer response:Determine if the Batch Backout utility (DFSBBO00)needs to be ran within an IRLM environment. If the

IRLM environment is necessary, remove the CHKPTstatement; if not, correct the JCL for the BatchBackout utility (DFSBBO00) before restarting.





Chapter 102. DFSD messages (DRD utilities)The ISPF interface for the dynamic resource definition (DRD) utilities issues messages beginning withDFSD.

DFSD001E Invalid data set specified for panelselection field

ExplanationYou specified a data set name as a value on an ISPFpanel; however, this data set name was not found inthe system catalog. One of the following might be areason for why the data set could not be found:

• The data set name might be incorrect.• The data set name is correct, but the data set is not

cataloged.

System actionISPF panel processing awaits correction of the error.


• If the data set name was incorrect, supply a validdata set name.

• If the data set is not cataloged, catalog the dataset or supply a different data set that has beencataloged.

Module:REXX programs DFSRRDD1, DFSRRDD2, DFSRRDD3,DFSRRDD4

DFSD002E panel field is required for thisfunction

ExplanationYou omitted the specification of a value on an ISPFpanel; however, this value is required by the functionwhich is being performed. panel field in the messagetext identifies the field that requires a value.


System programmer responseSupply a value for the indicated field.

Module:REXX programs DFSRRDD2, DFSRRDD3, DFSRRDD4

DFSD003E You must select a step to perform

ExplanationYou tried to invoke an ISPF panel that requires theselection of a specific step to be performed; however,you neglected to indicate which step you wanted toperform. The panel displays the steps you could selectto perform.


System programmer responseIndicate the step you want to perform.

Module:REXX programs DFSRRDD1, DFSRRDD2

DFSD004E You must specify at least onefunction

ExplanationYou attempted to invoke an ISPF panel that allows theselection of one or more functions to be performed;however, you neglected to indicate which functionsyou wanted to perform. The panel displays thefunctions you could chose to perform.


System programmer responseIndicate the functions you want to perform.

Module:REXX program DFSRRDD4

DFSD005E You must specify UNIT andVOLUME as a set

ExplanationOn the Enter Log Data Set Names panel, you selectedthe step to make a list of log data sets. For one or moredata set entries on the panel, you specified either aunit or a volume, but not both. If you specify eitherone, you must also specify the other.



System programmer responseFor an uncataloged data set, specify both unit andvolume.

For a cataloged data set, specify neither unit norvolume.

Module:REXX program DFSRRD1A

DFSD006E You must specify a log dataset name if volume or unit arespecified

ExplanationOn the Create RDDS from Log Records panel, youselected the step to make a list of log data sets. Forone or more data set entries, you specified the unitand volume but did not specify the log data set name.


System programmer responseSpecify the log data set name associated with the unitand volume that you specified.


DFSD007E log data set name is not cataloged

ExplanationOn the Create RDDS from Log Records panel, youselected the step to make a list of log data sets.For one or more data set entries on the panel, youspecified a log data set name that was not found inthe system catalog. One of the following might be areason:

• The data set name might be incorrect.• The data set name is correct, but the data set is not

cataloged.



• Supply a valid data set name, if the data set namewas incorrect.

• If the data set is not cataloged, catalog the dataset or supply a different data set that has beencataloged.


DFSD008E The list of log data sets was notfound

ExplanationOn the Create RDDS from Log Records panel, youselected the step to create the resource definitiondata set (RDDS) from log data set contents. For theselection of technique for making the list, you haveindicated that you have entered a list of log data sets;however, this list cannot be found. One of the followingmight be a reason:

• The PDS member which would contain the data setname list is missing.

• The PDS member which would contain the data setname list is empty


System programmer responseOn the Create RDDS from Log Records panel, performthe step to enter the list of logs and ensure that thisstep completes without any panel errors.

Module:REXX program DFSRRD1

DFSD009E The list of log data set namesextracted from RECON was notfound

ExplanationOn the Create RDDS from Log Records panel, youselected the step to create resource definition data set(RDDS) from log data set contents. For the selectionof technique for making the list, you have indicatedthat you have extracted the list of log data setsfrom RECON; however, this list cannot be found. Inthis case, the PDS member that would contain theextracted data set names is missing.



System programmer responseOn the Create RDDS from Log Records panel, performthe step to extract the list from RECON, and ensurethat this step completes without any panel or runtimeerrors.


DFSD010E Member containing logs fromRECON is empty

ExplanationOn the Create RDDS from Log Records panel, youselected to create the resource definition data set(RDDS) from log data set contents. For the selectionof the technique to use creating the list, you indicatedthat you have extracted the list of log data sets fromRECON; however, this list was not found. The PDSmember that would contain the extracted data setnames is empty.


System programmer responseOn the Create RDDS from Log Records panel, performthe step to extract the list from RECON, and ensurethat this step completes without any panel or runtimeerrors.


DFSD011E The Stage 2 data set was notfoundDSN: data set nameSelect the Create Stage 2 JCL stepto create it

ExplanationOn the Create RDDS from SYSGEN panel, you selectedthe step to Create Temporary MODBLKS. However, thedata set indicated in the message text by data setname, which should have been created by your priorprocessing of the Create Stage 2 JCL step, was notfound.


System programmer responseOn the Create RDDS from SYSGEN panel, performthe Create Stage 2 JCL step. Ensure that itruns successfully. Then retry the Create TemporaryMODBLKS step.


DFSD012E The MODBLKS data set was notfoundDSN: data set nameSelect the Create TemporaryMODBLKS step to create it

ExplanationOn the Create RDDS from SYSGEN panel, you selectedthe step to Process Temporary MODBLKS. However,the data set indicated in the message text by data setname, which should have been created by your priorprocessing of the Create Temporary MODBLKS step,was not found.


System programmer responseOn the Create RDDS from SYSGEN panel, performthe Process Temporary MODBLKS step. Ensure thatthe step runs successfully, and then retry the ProcessTemporary MODBLKS step.


DFSD013E Data Sets were not found for IMSHLQ: ims hlq

ExplanationOn the Create RDDS from System Definition panel, youspecified a value for IMS HLQ. The value specifiedfor this field should represent the high level qualifierthat was used by the IMS systems installer to nameyour IMS installation data sets used during the sysgenprocess; for example, hlq.ADFSMAC. However, thesystem could not find any IMS installation data setswith this high level qualifier.


Chapter 102. DFSD messages (DRD utilities) 1351

System programmer responseVerify with the IMS systems installer that the correctvalue for IMS HLQ is being used.


DFSD014E CHKPTID must contain allnumerics and a slash in position 6

ExplanationOn the Create RDDS from log records panel, youspecified a invalid value for CHKPTID. The valuespecified for this field must exactly match thecheckpoint value used in IMS log records. It must beof the format yyddd/hhmmss where: yyddd representsthe Julian date and hhmmss represents the time.The / is required.

All of the characters used for the date and time mustbe numeric.


System programmer responseEnsure that you use the correct syntax for CHKPTID.


DFSD015E CHKPTID must be 12 characterslong

ExplanationOn the Create RDDS from log records panel, youspecified a invalid value for CHKPTID. The valuespecified for this field must exactly match thecheckpoint value used in IMS log records. It mustbe 12 characters long with this format yyddd/hhmmsswhere: yyddd represents the Julian date and hhmmssrepresents the time. The / is required.

All of the characters used for the date and time mustbe numeric.


System programmer responseEnsure that you use the correct syntax for CHKPTID.


DFSD016E Full Julian date is required

ExplanationOn the Create RDDS from log records panel, youspecified an invalid value for the Start or Stop date.The value you specify must be the Julian date in theformat yyyyddd.


System programmer responseSpecify a valid value for the Start or Stop date.

Module:REXX programs DFSRRDD1, DFSRRD1B

DFSD017E Century is required

ExplanationOn the Create RDDS from log records panel, youspecified an invalid value for the century in the Start orStop date. The value you specify for the century mustbe 19 or greater.


System programmer responseSpecify a valid value for the century in the Start or Stopdate.

Module:REXX programs DFSRRDD1, DFSRRD1B

DFSD018E Invalid specification for Day

ExplanationOn the Create RDDS from log records panel, youspecified an invalid value for the day in the Start orStop date. The value you specify for the day must bebetween 1 and 366.


System programmer responseSpecify a valid value for the day in the Start or Stopdate.

Module:


REXX programs DFSRRDD1, DFSRRD1B

DFSD019E Stop date/time cannot be beforestart date/time

ExplanationOn the Create RDDS from log records panel, youentered a stop date and time; however, the stop dateand time are before the start date and time.


System programmer responseEnsure that the stop date and time is after the startdate and time.

Module:REXX program DFSRRD1B

DFSD020E A start time is required for log typeSLDS

ExplanationOn the Create RDDS from Log Records panel, youspecified a log type of SLDS; however, you did notspecify a start time. You must specify a start time withlog type SLDS.


System programmer responseSpecify a start time if log type SLDS is specified.

Module:REXX program DFSRRD1B

DFSD021E HLQ fields must not contain quotes

ExplanationOn one of the RDDS panels associated with theManage Resources selection from the IMS ApplicationMenu panel, You entered a high level qualifier for adata set. However, quotes were included in the name.Quotes must not be included in the specification ofa high level qualifier. Fields where you specify a highlevel qualifiers include:

IMS HLQTemp MODBLKS HLQWork Data Set HLQDS


System programmer responseRemove the quotes in the high level qualifier names.

Module:REXX programs DFSRRDD1, DFSRRDD2, DFSRRDD3,DFSRRDD4

DFSD022E Invalid specification for ASM

ExplanationOn the Create RDDS from SYSGEN panel, you entereda value for the ASM parameter that did not use thecorrect syntax. The error could be one of the following:

• You entered multiple parameters, but did notseparate them with commas.

• You entered multiple parameters, but did notenclose them within parentheses.


System programmer responseCorrect the syntax error.

Module:REXX programs DFSRRDD2

DFSD023E Data set volume and storage classare mutually exclusive

ExplanationOn one of the RDDS panels from the ManageResources selection on the IMS Application Menupanel, you have entered values for both the RDDS dataset volume and DFSMS. These two specifications aremutually exclusive.


System programmer responseSpecify either RDDS data set volume or STORCLAS, butnot both.

Module:REXX programs DFSRRDD1, DFSRRDD2, DFSRRDD3,DFSRRDD4 DFSRRDD5

Chapter 102. DFSD messages (DRD utilities) 1353

Chapter 103. DFSIX messages (InstallationVerification Program dialog)

Messages that are issued from the Installation and Verification Program (IVP) dialog begin with DFSIX.

For information about using the IVP, see IMS installation verification program (IVP) overview(Installation).

unnumbered INPUT PARM parameter IS TOOLONG

ExplanationThe value of the parameter identified by keywordparameter is too long. The value of the parameter mustbe no longer than 26 characters. parameter can be oneof the following values:

• HLQDL• HLQIPO• HLQIV• HLQSY

System actionThe IVP Install dialog terminates.

Programmer responseChange the parameter value so that it is no longer than26 characters and rerun the IVP Install dialog.

ModuleDFSIXC01

unnumbered PARAMETER DLTA1, DLTA2,DLTA3, DLTA5, DLTA6, or DLTA7 ISTOO LONG

ExplanationOne or more of the DLTA parameters is too long. Theparameters must be no longer than 44 characters.


Programmer responseChange the parameter so that it is no longer than 26characters and rerun the IVP Install dialog.

ModuleDFSIXC01

unnumbered PARAMETER DLTA5 MUST NOT BETHE SAME AS DLTA1, DLTA2, ORDLTA3

ExplanationThe DLTA5 parameter cannot have the same value asDLTA1, DLTA2 or DLTA3.


Programmer responseChange the parameter to a unique value then rerun theIVP Install dialog.

ModuleDFSIXC01





ModuleDFSIXC01


http://www.ibm.com/support/knowledgecenter/SSEPH2_15.1.0/com.ibm.ims15.doc.ins/ims_ivp.htm#ims_ivp

http://www.ibm.com/support/knowledgecenter/SSEPH2_15.1.0/com.ibm.ims15.doc.ins/ims_ivp.htm#ims_ivp

unnumbered SYSISPF=NOT ACTIVE - THISCLIST MUST BE INVOKED FROMWITHIN ISPF

ExplanationThe IVP Install dialog was not started from withinISPF.


Programmer responseRun the IVP Install dialog from within ISPF.

ModuleDFSIXC01





ModuleDFSIXC01

DFSIX000 aaaaaaaa THE INSTALL/IVPDIALOG DOES NOT SUPPORTMULTIPLE USERS

or

aaaaaaaa mmmmmmmmmmmmm

ExplanationThis is a general sever error message. TheINSTALL/IVP Dialog can only be used by one user ata time. Someone is currently using IVP.


Identifies the module in which the error occurred.mmmmmmmmmmmmm

Is the error message. If mmmmmmmmmmmmmis THE INSTALL/IVP DIALOG DOES NOTSUPPORT MULTIPLE USERS, see messageDFSIX000 for an explanation.

System actionIVP stops processing.

Programmer responseMake sure that IVP is not in use on another ISPFscreen. If IVP is in use on another ISPF screen, tryagain later.

If the problem persists, contact IBM Software Supportfor assistance.

ModuleDFSIXX01, DFSIXX07, DFSIXX08, DFSIXX09,DFSIXX10, DFSIXX11, DFSIXX14, DFSIXX15,DFSIXX16

DFSIX001 aaaaaaaa ENT ACTION COMPLETE

ExplanationThe entry (ENT) action completed. You are now in ENTmode where one variable displays at a time with helptext.

In the message text, aaaaaaaa is the module that wasrunning when this message was issued.



ModuleDFSIXX08, DFSIXX09, DFSIXX10

DFSIX002 aaaaaaaa LST ACTION COMPLETE

ExplanationThe list (LST) action completed. You are now in LSTmode where multiple variables display without helptext.






DFSIX006 aaaaaaaa - NXT ACTIONWRAPPED TO TOP OF TABLE

ExplanationThe next (NXT) action was requested, but the end ofthe table was reached. Instead of paging forward tothe next job, task, or variable, NXT wrapped to the topof the table.





DFSIX007 aaaaaaaa - PRV ACTIONWRAPPED TO BOTTOM OF TABLE

ExplanationThe previous (PRV) action was requested, but the topof the table was reached. Instead of paging backwardto the previous job, task, or variable, PRV wrapped tothe bottom of the table.





DFSIX010 aaaaaaaa - CHG ACTIONCOMPLETE

ExplanationThe change (CHG) action completed successfully. Thechanged variables were saved.




ModuleDFSIXX08

DFSIX019 aaaaaaaa - LST ACTIONREJECTED - TABLE IS EMPTY

ExplanationThe list (LST) action could not be completed. Theprogram has not switched to LST mode. An ISPF Tableis empty.


System actionThe display switches to entry (ENT) mode.

Programmer responseYou might be able to continue processing in ENTmode. If problems persist, contact IBM SoftwareSupport to report the problem and for assistance.


DFSIX023 aaaaaaaa - PRIOR SESSIONCOMPLETED SUCCESSFULLY FORivpenv

ExplanationThe prior IVP session for environment ivpenvcompleted successfully. In the message text,

Chapter 103. DFSIX messages (Installation Verification Program dialog) 1357

aaaaaaaaThe module that was running when this messagewas issued.

ivpenvThe IMS environment you were creating, which isone of the following:

• DBB• DBC• DBT• DCC• XRF



ModuleDFSIXX01

DFSIX024 aaaaaaaa - PRIOR SESSIONCOMPLETED UNSUCCESSFULLYFOR ivpenv

ExplanationThe prior IVP session for the environment ivpenvcompleted unsuccessfully. This situation occurredbecause the phase in which you were working isincomplete.


The module that was running when this messagewas issued.

ivpenvThe IMS environment you were creating, which isone of the following:

• DBB• DBC• DBT• DCC• XRF


Programmer responseContinue processing IVP where you last stopped.

ModuleDFSIXX01

DFSIX025 aaaaaaaa - vvvvvvvv - MUST BE INTHE RANGE mnnnn TO mxxxx MAX

ExplanationThe vvvvvvvv variable is not in the required range. Thevariable must be between mnnnn and mxxxx.



vvvvvvvvThe name of the variable out of range.

mnnnnThe minimum value for the variable.

mxxxxThe maximum value for the variable.

System actionThe variable vvvvvvvv action field is set to ERR, whichindicates that the variable is invalid.

Programmer responseChange the vvvvvvvv variable to a value betweenmnnnn and mxxxx.

ModuleDFSIXX11

DFSIX026 aaaaaaaa - REPORT GENERATIONIN PROCESS FOR item

ExplanationThe report requested by the document (DOC) action isbeing generated.



itemThe job, task, or variable currently beingprocessed.





DFSIX029 aaaaaaaa - VARIABLEGATHERING PHASE ENDED FORivpenv

ExplanationThe variable gathering phase (which resolves all input)for the ivpenv environment completed. In the messagetext:aaaaaaaa


ivpenvThe IVP environment.



ModuleDFSIXX08

DFSIX030 aaaaaaaa - RFR ACTIONCOMPLETE - DEFAULT VALUERESTORED

ExplanationThe restore (RFR) action completed successfully. Thevariable has been restored to the default value. Inthe message text, aaaaaaaa is the module that wasrunning when this message was issued.



ModuleDFSIXX08

DFSIX031 aaaaaaa - RFR ACTION FAILED -TBMOD FAILED

ExplanationThe restore (RFR) action failed. The variable was notrestored to the default value. In the message text,aaaaaaaa is the module that was running when thismessage was issued.

System actionProcessing continues. The default value is notrestored.

Programmer responseSet the variable to the desired value and continueprocessing. If problems persist, contact IBM SoftwareSupport for assistance.

ModuleDFSIXX08

DFSIX032 aaaaaaaa - CHG/RFR ACTIONFAILED - DEFAULT VALUE NOTFOUND

ExplanationThe change (CHG) or restore (RFR) action failed. Thevalue of the variable was not changed, or the valuewas not changed to the default.


System actionProcessing continues. The default value is notrestored.

Programmer responseSet the variable to the desired value and continueprocessing. If problems persist, contact IBM SoftwareSupport for assistance.

ModuleDFSIXX08

DFSIX033 aaaaaaaa - FILE TAILORINGPHASE ENDED FOR ivpenv


ExplanationThe File Tailoring phase (which resolves variablesbefore running a job) for the ivpenv environmentcompleted.



ivpenvThe IVP environment.



ModuleDFSIXX09

DFSIX034 aaaaaaaa - FTL ACTIONCOMPLETE

ExplanationThe file-tailoring (FTL) action completed successfully.The job, task, or variable has been file-tailored.




ModuleDFSIXX09

DFSIX035 aaaaaaaa - BRM ACTIONCOMPLETE

ExplanationThe browse (BRM) action completed successfully. AnINSTALIB member has been browsed. In the messagetext, aaaaaaaa is the module that was running whenthis message was issued.



ModuleDFSIXX09, DFSIXX10

DFSIX036 aaaaaaaa - BRS ACTIONCOMPLETE

ExplanationThe browse (BRS) action completed successfully. Asource member (DFSSLIB or DFSISRC) has beenbrowsed.




ModuleDFSIXX09

DFSIX037 aaaaaaaa - EDM ACTIONCOMPLETE

ExplanationThe edit (EDM) action completed successfully. AnINSTALIB member has been edited.






DFSIX038 aaaaaaaa - vvvvvvvv - INVALIDSUBPARM - LENGTH EXCEEDSmxxx

ExplanationThe length of the subparameter vvvvvvvv exceeds themaximum length, mxxx.



vvvvvvvvThe subparameter that exceeds the maximumlength.

mxxxThe maximum allowed length for the vvvvvvvvsubparameter.

System actionThe variable action field is set to ERR, which indicatesthat the variable is invalid.

Programmer responseChange the subparameter to a value at or below themaximum value of mxxx.

ModuleDFSIXX11

DFSIX039 aaaaaaaa - ISPF/PDF EDITRECOVERY IS NOT SUPPORTED BYINSTALL/IVP

ExplanationThis message is issued when you edit a member inIVP. IVP does not support ISPF EDIT recovery. TheISPF EDIT profile recovery settings are not used byIVP. This message is displayed each time you edit amember with IVP to remind you that edit recovery isnot supported.





DFSIX040 aaaaaaaa - BRM ACTIONIGNORED - NOT AVAILABLE FORjtname

ExplanationThe browse (BRM) action is not available for use onthe jtname job or task. The INSTALIB member was notbrowsed.



jtnameThe name of the job or task for which BRM is notvalid.


Programmer responseReissue the command with a valid job or task.


DFSIX041 aaaaaaaa - BRS ACTION IGNORED- NOT AVAILABLE FOR jtname

ExplanationThe browse (BRS) action is not available for use on thejtname job or task. The source members DFSSLIB andDFSISRC were not browsed.



jtnameThe name of the job or task for which BRM was notavailable.




ModuleDFSIXX09

DFSIX042 aaaaaaaa - EDM ACTIONIGNORED - NOT AVAILABLE FORjtname

ExplanationThe edit (EDM) action is not available for use on thejtname job or task. The INSTALIB member was notedited.



jtnameThe name of the job or task for which EDM was notavailable.



ModuleDFSIXX10

DFSIX043 aaaaaaaa - vvvvvvvv subparm -INVALID DATATYPE

ExplanationThe subparm subparameter of variable vvvvvvvvis not the correct data type, and it contains aninvalid character. For example, the variable should benumeric, but it might contain a letter.



vvvvvvvvThe variable containing the subparm subparameterwith an incorrect data type.

subparmThe subparameter that is the incorrect data type.


Programmer responseChange the subparm subparameter so that itcontains only valid characters. For information onvalid characters, switch to entry (ENT) mode, whichprovides help text.

ModuleDFSIXX11

DFSIX044 aaaaaaaa - FTL ACTION IGNORED- NOT AVAILABLE FOR jtname

ExplanationThe file tailoring (FTL) action is not available for usewith the jtname job or task. File tailoring for the jtnamejob or task did not complete.



jtnameThe job or task for which file tailoring did notcomplete.



ModuleDFSIXX09

DFSIX045 aaaaaaaa - VARIABLE vvvvvvvv ISUNKNOWN - ACCEPTED ASIS

ExplanationThis message should not occur. If this message doesoccur, it is the result of a programming error. Thevariable vvvvvvvv has not been checked for the correctvalue but is accepted as it is and processing continues.



vvvvvvvvThe unknown variable.


System actionThe variable is accepted as it is, and processingcontinues.

Programmer responseContact IBM Software Support and report the error.

ModuleDFSIXX11

DFSIX046 aaaaaaaa - EXECUTION PHASEENDED FOR ivpenv

ExplanationThe execution phase (EXE) for the ivpenv environmentcompleted. The IVP job ran successfully.



ivpenvThe environment in which IVP is running.



ModuleDFSIXX10

DFSIX047 aaaaaaaa - EXE ACTION IGNORED- NOT AVAILABLE FOR jtname

ExplanationThe execution (EXE) action is not available for thejtname job or task. An INSTALIB job or task was notsubmitted.



jtnameThe name of the job or task that was notsubmitted.



ModuleDFSIXX10

DFSIX048 aaaaaaaa - EXE ACTIONCOMPLETE FOR jtname

ExplanationThe execution (EXE) action completed successfully forthe jtname job or task. An INSTALIB job or task wassubmitted.



jtnameThe name of the job or task that was submitted.



ModuleDFSIXX10

DFSIX049 aaaaaaaa - ALL ACTIONCOMPLETE

ExplanationThe ALL action completed successfully. File tailoringcompleted for all jobs, tasks, or variables, starting withthe current item.





ModuleDFSIXX09

DFSIX052 aaaaaaaa - DOC ACTIONCOMPLETE

ExplanationThe documentation (DOC) action completedsuccessfully. The job or task documentation you justsubmitted printed.





DFSIX054 aaaaaaaa - CPYSPECL FAILEDDURING OPEN FOR &ixfmsgt

ExplanationAn IVP ISPF table failed to open during CPYSPECLprocessing.



&ixfmsgtThe IVP ISPF table that failed to open.

System actionProcessing of the current option terminates. You arereturned to previous selection panel.


ModuleDFSIXX07

DFSIX055 aaaaaaaa - CPYSPECL FAILEDDURING TBADD FOR &ixfmsgt

ExplanationAn ISPF table add (TBADD) command failed duringCPYSPECL processing.



&ixfmsgtThe IVP ISPF table that failed the TBADDcommand.

System actionProcessing of the current option terminates. You arereturned to previous selection panel.


ModuleDFSIXX07

DFSIX056 aaaaaaaa - vvvvvvvv - PLEASESPECIFY Y (YES), OR N (NO)

ExplanationThe variable vvvvvvvv must be specified as Y or N.



vvvvvvvvThe name of the variable that needs to bespecified.


Programmer responseChange the vvvvvvvv variable to either Y or N.

ModuleDFSIXX11

DFSIX057 aaaaaaaa - vvvvvvvv - PLEASESPECIFY 6250, 3480, OR 3490


ExplanationThe tape device format, vvvvvvvv, must be 6250,3480, or 3490.



vvvvvvvvThe name of the variable that needs to bespecified.


Programmer responseChange the vvvvvvvv variable to 6250, 3480, or 3490.

ModuleDFSIXX11

DFSIX058 aaaaaaaa - vvvvvvvv - MUST BEALPHNUMERIC (A-Z, 0-9)

ExplanationThe vvvvvvvv variable must be in alphanumericcharacters: A-Z, 0-9.



vvvvvvvvThe name of the variable that must be specified inalphanumeric characters.


Programmer responseChange the vvvvvvvv variable to alphanumericcharacters only.

ModuleDFSIXX11

DFSIX059 aaaaaaaa - vvvvvvvv - INVALIDLENGTH - MIN/MAX = mnnnn /mxxxx

ExplanationThe vvvvvvvv variable is not the correct length. Thevariable must be between mnnnn and mnnnn.



vvvvvvvvThe name of the variable with an incorrect length.

mnnnnThe maximum allowable length for the vvvvvvvvvariable.

mxxxxThe minimum allowable length for the vvvvvvvvvariable.


Programmer responseCorrect the vvvvvvvv so that it is between mnnnn andmxxxx.

ModuleDFSIXX11

DFSIX060 aaaaaaaa - vvvvvvvv - PLEASESPECIFY EITHER JES2 OR JES3

ExplanationThe z/OS program variable, vvvvvvvv, muse bespecified as either JES2 or JES3.



vvvvvvvvThe name of the variable that must be specified.



Programmer responseChange the vvvvvvvv variable to either JES2 or JES3.

ModuleDFSIXX11

DFSIX061 aaaaaaaa - vvvvvvvv - PLEASESPECIFY A NON-BLANK VALUE

ExplanationThe vvvvvvvv variable must be a non-blank value.



vvvvvvvvThe name of the variable that needs a non-blankvalue specified.


Programmer responseChange the vvvvvvvv variable to a non-blank value.

ModuleDFSIXX11

DFSIX062 aaaaaaaa - vvvvvvvv - VALUEMUST BE OF THE FORM nnnnnnnK OR nnnn M

ExplanationThe variable vvvvvvvv must be in the form of nnnnnnnkilobytes or nnnn megabytes.



vvvvvvvvThe name of the variable that needs to berespecified in the correct format.

nnnnnnnThe kilobyte format for vvvvvvvv.

nnnnThe megabyte format for vvvvvvvv.


Programmer responseChange the vvvvvvvv variable to the format of nnnnnnnK or nnnn M.

ModuleDFSIXX11

DFSIX063 aaaaaaaa - vvvvvvvv - VALUERANGE - mnnn K THROUGH mxxxK

ExplanationThe vvvvvvvv variable must be between mnnnkilobytes and mxxx kilobytes.



vvvvvvvvThe name of the variable that must be specified inthe proper range.

mnnnThe minimum value that can be specified for thevvvvvvvv variable.

mxxxThe maximum value that can be specified for thevvvvvvvv variable.


Programmer responseChange the vvvvvvvv variable to between mnnn K andmxxx K.

ModuleDFSIXX11

DFSIX064 aaaaaaaa - vvvvvvvv - VALUERANGE - mnnn M THRU mxxx M


ExplanationThe variable vvvvvvvv is out of the required range. Thevariable must be within the range of mnnn megabytesto mxxx megabytes.


The program name.vvvvvvvv

The name of the variable that is out of the requiredrange.

mnnnThe minimum value to which vvvvvvvv can be set.

mxxxThe maximum value to which vvvvvvvv can be set.


Programmer responseChange the variable vvvvvvvv to a value between mnnnM and mxxx M.

ModuleDFSIXX11

DFSIX065 aaaaaaaa - vvvvvvvv - TOTALLENGTH WILL EXCEED mxxxxBYTES

ExplanationThe total length of the values in the JOBstatement accounting information variables exceedsthe maximum allowable size.



vvvvvvvvThe variable that exceeded the size limitation.

mxxxxThe maximum number of bytes allowed in theaccounting field.


Programmer responseChange the vvvvvvvv variable so that it is at or belowmxxxx.

ModuleDFSIXX11

DFSIX066 aaaaaaaa - vvvvvvvv - VALUECONTAINS ILLEGAL CHARACTERS

ExplanationThe variable vvvvvvvv contains characters that are notallowed.



vvvvvvvvThe variable containing illegal characters.


Programmer responseChange the vvvvvvvv variable so that it contains onlyvalid characters. For information on valid characters,switch to entry (ENT) mode, which provides help text.

ModuleDFSIXX11

DFSIX067 aaaaaaaa - vvvvvvvv - JESXSTATEMENTS MUST BEGINWITH /* or //

ExplanationThe variable vvvvvvvv is a JESx statement andtherefore must begin with /* or //.



vvvvvvvvThe name of the variable that must start witheither /* or //.



Programmer responseChange the vvvvvvvv variable so that it starts with /*or //.

ModuleDFSIXX11

DFSIX068 aaaaaaaa - SPR ACTIONCOMPLETE

ExplanationThe special processing routine (SPR) completedsuccessfully. In the message text, aaaaaaaa is themodule that was running when this message wasissued.



ModuleDFSIXX10

DFSIX069 aaaaaaaa - vvvvvvvv - subparm -MAY NOT BE BLANK

ExplanationThe subparm parameter for the vvvvvvvv variable isblank and needs to be specified.



vvvvvvvvThe variable containing the blank parameter.

subparmThe blank parameter that needs to be specified.


Programmer responseSpecify a value for the subparm parameter.

ModuleDFSIXX11

DFSIX070 aaaaaaaa - vvvvvvvv - HLQ GROUPgroup IS UNKNOWN

ExplanationThis message should not occur. If this message doesoccur, it is the result of a programming error.



vvvvvvvvvariable containing unknown HLQ group.

groupGroup name.

System actionProcessing of the variable vvvvvvvv is terminated.

Programmer responseContact IBM Software Support for assistance and toreport the problem.

ModuleDFSIXX11

DFSIX071 aaaaaaaa - vvvvvvvv - VOL GROUPvol grp IS UNKNOWN




vvvvvvvvvariable contains unknown volume group.

vol grpvolume group.




ModuleDFSIXX11

DFSIX072 aaaaaaaa - vvvvvvvv - subparm -MIN/MAX = mnnn / mxxx

ExplanationThe parameter subparm in the vvvvvvvv variable isnot the correct length. The parameter length must bebetween mnnn and mxxx.



vvvvvvvvThe variable containing the subparm parameterwith the incorrect length.

subparmThe parameter with the incorrect length.

mnnnThe minimum length of the parameter.

mxxxThe maximum length of the parameter.


Programmer responseChange the subparm parameter to a value betweenmnnn and mxxx.

ModuleDFSIXX11

DFSIX073 aaaaaaaa - vvvvvvvv - CYL / TRK /nnnnn / REC

ExplanationOne of the options will be displayed. The vvvvvvvvvariable contains an incorrect parameter type. Theparameter must be one of the following types:CYL

Space allocated in cylinders.

nnnnnSpace allocated in records, which is the averageblock size.

RECSpace allocated in records. Use this value only forVSAM.

TRKSpace allocated in tracks.



vvvvvvvvThe variable containing the parameter with anincorrect type.

nnnnnSpace allocated in records, which is the averageblock size.


Programmer responseChange the parameter in the vvvvvvvv variable to oneof the allowable types.

ModuleDFSIXX11

DFSIX074 aaaaaaaa - vvvvvvvv - BLK GROUPblk grp IS UNKNOWN




vvvvvvvvvariable containing unknown BLK group.

blk grpThe block group.




ModuleDFSIXX11

DFSIX075 aaaaaaaa - DOC ACTION FAILED -NO RECORDS TO PRINT

ExplanationThe documentation (DOC) action did not find anyrecords to print. No documentation has been printedfor variables, jobs, or tasks.


System actionNo records were printed.


ModuleDFSIXX08, DFSIXX09,DFSIXX10

DFSIX076 aaaaaaaa - vvvvvvvv - MUST BE AMULTIPLE OF reclen

ExplanationThe vvvvvvvv variable is a block size parameter andmust be a multiple of the record length, reclen.



vvvvvvvvThe variable with an incorrect record length.

reclenThe record length by which the value for vvvvvvvvmust be multiplied.


Programmer responseChange the vvvvvvvv variable so that it is a multiple ofreclen.

ModuleDFSIXX11

DFSIX078 aaaaaaaa - SPR ACTION NOTAVAILABLE FOR JOB/TASK jtname

ExplanationThe special processing routine (SPR) was not availablefor the jtname job or task.



jtnameThe job or task for which the special processingroutine was not available.



ModuleDFSIXX10

DFSIX079 aaaaaaaa - REPOSITIONINGFAILED - DEFAULTING TO TOP OFTABLE

ExplanationIVP was unable to reposition the table to the desiredentry.


System actionThe table displays from the top.


If the message persists, contact IBM Software Supportfor assistance.



DFSIX080 aaaaaaaa - BRS ACTION FAILED -DFSISRC IS NOT AVAILABLE

ExplanationThe browse (BRS) action cannot access the SDFSISRCdata set. The source member was not browsed.


System actionBRS does not run. Processing continues.

Programmer responseDetermine why the SDFSISRC data set was notavailable and correct the problem.

ModuleDFSIXX09

DFSIX081 aaaaaaaa - MUST CORRECTERROR IN VG BEFOREPROCEEDING

ExplanationAn error occurred in the variable gathering (VG) phaseof the installation and verification process.


System actionIVP will not proceed to the next phase until the errorsare corrected.

Programmer responseThe variables in error are displayed. Correct thevariables.


DFSIX082 aaaaaaaa - vvvvvvvv - INVALIDVALUE SPECIFIED

ExplanationThe vvvvvvvv variable contains an invalid value orincorrect format.



vvvvvvvvThe variable containing the invalid value.


Programmer responseChange the vvvvvvvv variable to a valid value or format.For information on valid variables, switch to entry(ENT) mode, which provides help text.

ModuleDFSIXX11

DFSIX085 aaaaaaaa - CHG/RFR ERROREXISTS

ExplanationErrors have occurred during the processing of one ormore variables.



Programmer responseCorrect the errors.


DFSIX086 aaaaaaaa - DOC ACTION FAILED -INCOMPLETE SELECTION

ExplanationThe documentation (DOC) action failed because not allof the required selection was created on the DocumentOptions panel. No variable, job, or task documentationwas printed.



System actionThe DOC action terminates.

Programmer responseReissue DOC and supply complete input to all options.


DFSIX087 aaaaaaaa - VALUES MUST BEEITHER YES OR NO

ExplanationThe variable must be either YES or NO.



Programmer responseCorrect the variable to an acceptable value.

ModuleDFSIXX11

DFSIX088 aaaaaaaa - PLEASE SPECIFYHIR2101

ExplanationThe variable must be set to HIR2101.



Programmer responseCorrect the variable to HIR2101.

ModuleDFSIXX11

DFSIX089 aaaaaaaa - TCP/IP host name isinvalid

ExplanationAn invalid TCP/IP host name was specified.



Programmer responseCorrect the TCP/IP host name value.

ModuleDFSIXX11

DFSIX090 ivpenv ENVIRONMENT NOTAVAILABLE (envmemb)

ExplanationThe selected IVP environment is not available in theIVP INSTATBL data set. This means environment hasnever been created.

In the message text:ivpenv

The IVP environment (DBB, DBC, DBT, XRF, DCC).envmemb

The member name of the environment.

System actionThe IVP Variable Export utility panel is displayed withthis message.

Programmer responseChoose an environment that has been created in theIVP INSTATBL.

ModuleDFSIVPEX

DFSIX091 IVP TABLE DATASET ivptbl notfound

ExplanationThe IVP INSTATBL data set is not found. The IVP highlevel qualifier entered in the IVP Variable Export utilitymain panel is concatenated with INSTATBL to createthe data set name.



ivptblThe IVP INSTATBL data set name.


Programmer responseCorrect the IVP high level qualifier.

ModuleDFSIVPEX

DFSIX092 errmsg DSN: ivpdsn MEMBER:ivpmem

ExplanationAn error has occurred accessing the IVP INSTATBLdata set.

In the message text:errmsg

Contains the error:

• MEMBER SPECIFIED, BUT DATASET IS NOTPARTITIONED

• ERROR PROCESSING REQUESTED DATASET• PROTECTED DATASET• VOLUME NOT ON SYSTEM• INVALID DATASET NAME, ivpdsn• MISSING DATASET NAME• UNAVAILABLE DATASET

ivpdsnThe IVP INSTATBL data set name.

ivpmemThe IVP INSTATBL member name.


System programmer responseCorrect the IVP high level qualifier.

ModuleDFSIVPEX, DFSIXX08, DFSIXX22

DFSIX093 EXPORT DATASET expdsn NOTALLOCATED

ExplanationThis message is displayed on the IVP Export allocationpanel. The export data set did not exist so the IVPexport allocation panel was displayed giving the useran option of allocating the data set using TSO allocateor the ISPF Dataset Utility Panel (3.2). For somereason the export data set panel did not get allocated.

In the message text:expdsn

The IVP Export data set name.

System actionThe IVP export allocation panel is displayed with thismessage giving the user the options to allocate thedata set.

Programmer responseResolve any problems associated with the allocation ofthe export data set, then try again.

ModuleDFSIXX22

DFSIX094 ALLOCATION ERROR. RC=rc DSN:expdsn

ExplanationThe IVP was unable to allocate the export data setbecause of an allocation error.


The TSO allocation error.expdsn

The export data set name.

System actionMessage is displayed on export data set name panelwaiting for user input.

Programmer responseCorrect the export data set problem, then retry.


DFSIX095 EXPORT DATASET expdsn.MEMBER NOT FOUND.


or

EXPORT DATASET expdsn DOES NOT EXIST

ExplanationThe export data set does not exist or if a PDS, themember does not exist.

In the message text:expdsn

The export data set name

System actionMessage is displayed on export data set name panelwaiting for user input.

Programmer responseCorrect the export data set problem, then retry.

ModuleDFSIXX08

DFSIX096 EXPORT OF VARIABLESCOMPLETED SUCCESSFULLY

ExplanationThe export of the IVP variables is successful.

System actionInformational message.

ModuleDFSIVPEX, DFSIXX08

DFSIX097 IMPORT OF VARIABLESCOMPLETED SUCCESSFULLY

ExplanationThe import of the IVP variables is successful.


ModuleDFSIXX08

DFSIX098 aaaaaaaa - vvvvvvvv - MUST BE AMULTIPLE OF reclen + 4

ExplanationThe vvvvvvvv variable is a BLKSIZE parameter andmust be a multiple of the record length, reclen, plus4 additional bytes for the block descriptor word.



vvvvvvvvThe variable.

reclenThe record length.


Programmer responseChange the vvvvvvvv variable so that it is a multiple ofreclen + 4.

ModuleDFSIXX11

DFSIX100 (C) COPYRIGHT IBM CORP. 2003.ALL RIGHTS RESERVED.

ExplanationThis message issues IBM's copyright statement.



ModuleREXX program DFSAPPL

DFSIX101 THE HLQ PARAMETER IS MISSING

ExplanationA required parameter was not specified.


System actionThe program ends without performing the desiredfunction.

Programmer responseReissue the command and provide the HLQ parameter.The HLQ is the high level qualifier for IMS data sets.

Module(REXX programs) DFSAPPL, DFSHDSRT, DFSKBSRT,DFSSCSRT, DFSSPSRT

DFSIX102 AN UNKNOWN PARAMETER WASSPECIFIED: parm

ExplanationAn extra parameter was provided. The parameter isnot recognized.

System actionThe program continues with the desired function.

Programmer responseEnsure that the parameter was spelled correctly.Exit and start the program again with the correctparameter if applicable.

Module(REXX programs) DFSAPPL, DFSHDSRT, DFSKBSRT,DFSSCSRT, DFSSPSRT

DFSIX103 IPCS is not set up correctly.Please EXIT from ISPF andissue this command: EXEC'&hlq.SDFSEXEC(DFSDFSRT)''HLQ(&hlq)'

ExplanationThe IMS Dump Formatter requires IPCS and IPCShas not yet been started. Where&hlq is the high levelqualifier defined by the user.

System actionThe IMS Dump Formatter is not started.

System programmer responseIssue the command recommended by this message orstart IPCS using your local procedures.

ModuleDFSDFSRT

DFSIX104 Enter a VOLID for the allocation ofthe IPCS dump directory or null toexit.

ExplanationA ddname of IPCSDDIR was not found allocated to theuser.

System actionThe user is prompted for a VOLID. The program waitsuntil the user responds with a VOLID. If the userpresses Enter without typing a VOLID, the programends without starting the IMS Dump Formatter.

System programmer responseType a VOLID and press Enter.

ModuleDFSDFSRT

DFSIX105 The VOLID specified is not valid:&volid

ExplanationThe VOLID typed by the user is not valid. The namecan be 1 to 6 alphanumeric characters.

System actionThe system prompts the user again with messageDFSIX104.

System programmer responseRespond to message DFSIX104. Type a VOLID andpress Enter.

ModuleDFSDFSRT

DFSIX106 Allocation of IPCS dump directoryfailed.

ExplanationThe system attempted to issue a DEFINE CLUSTERcommand on your behalf and it did not completesuccessfully.


System actionThe IMS Dump Formatter is not started.

System programmer responseDetermine why a define cluster command could notwork successfully and resolve.

As a circumvention, the user may allocate anIPCS dump directory data set manually. The dumpdirectory is allocated to ddname IPCSDDIR. For moreinformation, see z/OS MVS Interactive Problem ControlSystem (IPCS) User's Guide.

DFSIX107 THE DBDLIB WAS NOT FOUND:dddddd

ExplanationThe IMS DD statement is not allocated, and the dataset name is not in the form of xxx.DBDLIB, where xxx isthe high-level qualifier.

In the message text, dddddd represents the DBDLIBdata set name that is missing.

System actionThe Partition Definition utility is started.

System programmer responseTo view the IMS DD statement, select Option 6 onthe PDU panel. You can either allocate the IMS DDstatement that contains the DBDLIB, or change theDBDLIB data set name to xxx.DBDLIB, where xxx is thehigh-level qualifier.


Chapter 104. DFSI messages (Syntax Checker)The Syntax Checker issues messages beginning with DFSI.

DFSI920E Parameter value invalid xxxxxxxxx

ExplanationThe parameter at the top of the screen is invalid.xxxxxxxxx is optional and gives more information.

System actionNone.

System programmer responseCorrect the error. Use F1 (Help key) to view theparameter’s description.

ModuleDFSWPBVP

DFSI921W (C) Copyright IBM Corp. 2002. AllRights reserved.

ExplanationIMS Syntax Checker copyright statement appearswhen Syntax Checker is started.

System actionNone.


ModuleDFSWSMBC

DFSI922I Member xxxxxxxx is new or empty.All parameters are displayed.

ExplanationThe member requested is empty. All possibleparameters will be displayed.

System actionNone.


ModuleDFSWMBLD

DFSI923I No errors found in a parametervalue.

ExplanationNo errors were found in any parameter values.



ModuleDFSWMBLD

DFSI924I Member xxxxxxxx not currentlyprocessed by Syntax Checker

ExplanationThe member xxxxxxxx is not processed by SyntaxChecker.

System actionNone.

System programmer responseTo use Syntax Checker to process a member, themember must be supported by Syntax Checker.

ModuleDFSWSMBC

DFSI925I Member xxxxxxxx has no newkeywords


ExplanationUser has requested the new keyword display. Thereare no new keywords in the member.

System actionNone.


ModuleDFSWMBLD

DFSI926W Keyword kkkkkk not valid inRelease rrrrr

ExplanationThe user has chosen to process the PROCLIB memberin IMS release rrrrr. The keyword kkkkkk currently inthe member is not valid in release.

System actionNone.

System programmer responseDelete the keyword.

ModuleDFSWPBKP

DFSI927W Keyword kkkkkk is not valid forControl Region ccccc

ExplanationThe user has chosen a process the PROCLIB memberin IMS control region ccccc. The keyword kkkkkkcurrently in the member is not valid in the controlregion.

System actionNone.

System programmer responseDelete the keyword.

ModuleDFSWPBKP

DFSI930I Member xxxxxxxx saved in dsn

ExplanationThe member has been successfully saved in dns.

System actionNone.


ModuleDFSWMSAV

DFSI932I Command cccccc is undefined

ExplanationThe command cccccc on the command line is notknown to Syntax Checker.

System actionNone.

System programmer responseCorrect the command.

ModuleDFSWSMBM, DFSWUPCR, DFSWUPDM, DFSWUPNR,DFSWUPSA, DFSWUPSV

DFSI933I No keywords selected for cccccccccommand

ExplanationThe command cccccccc on the command line needsto operate on the selected keyword. No keywordsselected.

System actionNone.

System programmer responseSelect the keywords by placing a / in the SEL field.

ModuleDFSWSMBM


DFSI934I No command selected for keywordkkkkkk

ExplanationA keyword has been selected but no command hasbeen entered on the command line.

System actionNone.

System programmer responseEnter the command on the command line.

ModuleDFSWSMBM

DFSI935I Invalid keyword selected option: o

ExplanationThe selected option o is not valid.

System actionNone.

System programmer responseCorrect the selected option.

ModuleDFSWSMBM

DFSI937I Equal sign in same line commentchanged to dash

ExplanationThe user has entered a same line comment thatcontains an equal sign (=). Equal Signs are not allowedin same line comment. It is changed to a dash (-).

System actionInformation message.


ModuleDFSWPBKP

DFSI938I P COMMAND IGNORED. KEYWORDDOES NOT IDENTIFY A MEMBER.

ExplanationThe keyword selected with the P command does notidentify a member of IMS.PROCLIB. The P commandcannot be processed.

System actionThe processing of the P command is terminated.

System programmer responseSelect a keyword that identifies a member ofIMS.PROCLIB. Valid keywords are underlined in thekeyword display panel.

ModuleDFSWKOPR

DFSI939I P COMMAND IGNORED. KEYWORDDOES NOT HAVE A VALUE ORVALUE IS IN ERROR

ExplanationThe keyword selected with the P command does nothave a value or the value is in error. The P commandcannot be processed.

System actionThe processing of the P command is terminated.

System programmer responseCorrect the problem and retry.

ModuleDFSWKOPR

DFSI998I MEMBER memb WILL BEPROCESSED UNDER IMS rel(ctlreg)

ExplanationProcessing has been requested for member memb.The member is processed under the same IMS releaseand control region as the original member. Thisproblem is an informational message informing youwhich IMS region and control region the member willbe processed under.

Chapter 104. DFSI messages (Syntax Checker) 1379

membMember name of the member being processed.

relIMS release.

ctlregIMS control region. This field is only displayed ifthe member varies by control region.



Module:DFSWSMBM

DFSI999I MEMBER memb PROCESSINGCONTINUES

ExplanationThe processing of member memb continues followingthe completion of the processing of another memberwith the P option.memb

Member name.



ModuleDFSWSMBM

DFSI991I Member name must be entered aspart of the DSN

ExplanationThe member name must be entered as part of the dataset name.

System actionNone.

System programmer responseEnter the member name as part of the data set namein TSO format.

ModuleDFSWUPSA

DFSI992I Member must be 1-8 characters

ExplanationMember name is invalid. It must be 1-8 characters.

System actionNone.

System programmer responseCorrect the member name.

ModuleDFSWUICR, DFSWUIDH, DFSWUIDM, DFSWUOSA

DFSI993I No members in dataset dsn

ExplanationThe data set that Syntax Checker was requested toprocess is empty.

System actionNone.

System programmer responseEnter a new member to process or select another dataset.

ModuleDFSWIOOI

DFSI994I Member is being used by you oranother user

ExplanationThe member is in use either by another user or thecurrent user on another ISPF screen.

System actionNone.



ModuleDFSWPBMC

DFSI995I Change release option cancelled -user request

ExplanationThe user canceled (F3) the change of release process.

System actionThe previous keyword display panel is displayed.


ModuleDFSWSMBM

DFSI996I Exit of member cancelled - userrequest

ExplanationThe user requested to exit or cancel the execution ofSyntax Checker but was notified that the member hadbeen modified. The user selects not to exit.

System actionNone.


ModuleDFSWSMBM

DFSI997I Comment not allowed on "blank",Unknown or keywords withoutvalues

ExplanationA comment "C" select code was entered on the "blank:or unknown keyword. Comments are not allowed onthe keywords.

System actionNone.


ModuleDFSWPBMC

DFSI998I MEMBER memb WILL BEPROCESSED UNDER IMS rel(ctlreg)

ExplanationProcessing has been requested for member memb.The member is processed under the same IMS releaseand control region as the original member. Thisproblem is an informational message informing youwhich IMS region and control region the member willbe processed under.memb

Member name of the member being processed.rel

IMS release.ctlreg

IMS control region. This field is only displayed ifthe member varies by control region.



Module:DFSWSMBM

DFSI999I MEMBER memb PROCESSINGCONTINUES

ExplanationThe processing of member memb continues followingthe completion of the processing of another memberwith the P option.memb

Member name.



Chapter 104. DFSI messages (Syntax Checker) 1381

ModuleDFSWSMBM


Chapter 105. DFSS messages (IMS abend search andnotification)

Messages that are issued from the IMS abend search and notification function begin with DFSS.

For information about using the IMS abend search and notification function, see the IMS system definitioninformation.

For the IMS abend search and notification function, you can get these messages when running frombatch:

DFS2225EDFS2226EDFS2227EDFS2228EDFS2229E

You can receive the messages in this topic when using the IMS abend search and notification ISPF panels.

DFSS001E "Skeleton lib" DS and "Runtime"DS must not be the same

ExplanationYou use the skeleton library to make the memberthat contains the name of the IMS abend search andnotification procedure available to users. The memberis included in the JCL generated by IMS abendsearch and notification for ISPF-driven invocation.The runtime data set is specified in all of the JCLthat invokes the IMS abend search and notification,whether this invocation is abend-driven or ISPF-driven.

System actionProcessing is terminated and a message is displayed.

System programmer responseProvide two different valid data set names for theskeleton library data set and the runtime data set.

Provide an email address in the Recipient e-mailaddress field or enter a Y in the Specify additionaladdresses? field to specify email addresses in theCONTROL member.

Module:DFSRASN1

DFSS002E e-mail address must be specified

ExplanationWhen setting up IMS abend search and notification,either specify an email address on the System Setup

panel in the Recipient e-mail address field or specifya Y in the Specify additional addresses? field.


System programmer responseProvide an email address in the Recipient e-mailaddress field or enter Y in the Specify additionaladdresses? field to specify email addresses in theCONTROL member.

Module:DFSRASN1, DFSRASN2

DFSS003E Data set xxxxxxxx not found

ExplanationA data set specified on the System Setup panel wasnot found on the z/OS system. xxxxxxxx identifies thedata set name.


System programmer responseSpecify a valid, existing data set on the System Setuppanel.

Module:DFSRASN1

DFSS004E No search argument has beenprovided


ExplanationFor the On demand interface panel to generate theemail, you must provide at least one search argument.


System programmer responseProvide at least one web search argument on the Ondemand interface panel in one of the following fields:

• PSP for FMID• Abend Code• Return Code (RC)• Module Name• APAR Number (PE or other)• Message ID• Generic Search Argument

Module:DFSRASN2

DFSS005E APAR search and MSG search aremutually exclusive

ExplanationYou cannot specify both the APAR number andMessage ID fields on the On demand interface panelat the same time.


System programmer responseSpecify either the APAR number or the Message ID,but not both.

Module:DFSRASN2

DFSS006E Abend prefix must be an S or a U

ExplanationWhen entering an abend code, use either an S for asystem abend or a U for an IMS abend code (userabend) as a prefix.


System programmer responseEnter a valid prefix for the abend code in the AbendCode field.

Module:DFSRASN2

DFSS007E The edit of the Abend Search andNotification generated JCL failedwith RC=xx

ExplanationThe REXX program failed to open certain members foredit.


System programmer responseMake sure that your user ID has the correct authorityto access the data sets.

Module:DFSRASN1, DFSRASN2

DFSS008I xxxxxxxx member already exists

ExplanationThe member you specified in the System Setup panelexists and is up-to-date.

In the message text, xxxxxxxx identifies the member,and can be one of the following:

URLSSYSUT1CONTROLSMSSMSCNTLPROCLIBDFSDFXXX

.


System programmer responsePress Enter to continue.

Module:DFSRASN1

DFSS009I xxxxxxxx member was updated


ExplanationThe member xxxxxxxx that you specified in the SystemSetup panel has been updated. xxxxxxxx can be one ofthe following:

URLSSYSUT1CONTROLSMSSMSCNTLPROCLIBDFSDFXXX



Module:DFSRASN1

DFSS100E Abend code must be specifiedwith return code (RC)

Explanation:If you specify a value for the return code (RC)parameter, you must also specify a value for the Abendcode parameter. You did not specify a value for theAbend code.

System action:Processing stops.

System programmer response:Make sure that specifications of Return code (RC) areaccompanied by specifications of Abend code.

Module:DFSRASN2

DFSS101I Change to recipient info: xxxxxxxxmember is copied again

ExplanationYou changed the recipient information, and theupdates must be propagated to certain members. Theexisting members are replaced with copies containingthe new information.


The member; this can be CONTROL or SMSCNTL.



Module:DFSRASN1

DFSS102I PROCLIB member has beenupdated due to change to xxxxxxxx

ExplanationThe PROCLIB member contains information that canbe modified using the System Setup panel. Thechanges you make on this panel are propagated to themember by creating a copy of the PROCLIB membercontaining the updated information.



Module:DFSRASN1

DFSS103E The HLQ parameter is missing

ExplanationYou must provide the high-level qualifier used to installIMS to access the appropriate data sets.

System actionProcessing terminates, and IMS abend search andnotification is not started.

System programmer responseProvide the high-level qualifier used to install IMS.

Module:DFSRASN0

DFSS104E An unknown parameter wasspecified: xxxxxxxx

ExplanationThe only valid parameter that you can specify for IMSabend search and notification is HLQ. The parameterindicated by xxxxxxxx was not recognized.

System actionProcessing terminates, and IMS abend search andnotification is not started.

Chapter 105. DFSS messages (IMS abend search and notification) 1385

System programmer responseEnsure that you use HLQ as a parameter and alsoprovide the high-level qualifier used to install IMS.

Module:DFSRASN0

DFSS105E Member DFSKCAT0 in data set"dsname" not found

ExplanationThe program is trying to start DFSKCAT0 to verify thatdata sets you specified on an ISPF panel are valid.However, the data set named in the error messagedoes not contain the module. You specify the nameof the data set that should contain DFSKCAT0 on thepanel as the value for the IMS.SDFSRESL parameter.

In the message text:dsname

The data set that should contain the memberDFSKCAT0


System programmer responseCheck that the correct data set name is specified asthe IMS.SDFSRESL parameter and that the data setexits.

Module:DFSRASN1

DFSS106E Skeleton skeleton not found

ExplanationYou selected IMS ASN On-Demand Interface and thesystem tried to validate that the control statementskeletons are available to the program. The programcould not access the skeleton identified in themessage. These skeletons were created as part of thesetup of the IMS Abend Search and Notification. Theyreside in the data set specified as the Skeleton lib DSon the IMS ASN System Setup panel (Option 1).

In the message text:skeleton

The name of the skeleton that was unavailable.This can be DFSSPCLI or DFSSPRCI


System programmer responseVerify that the skeletons exist in the data set and thatyour IMS Abend Search and Notification installation isconfigured correctly to access to the skeleton librarydata set.

Module:DFSRASN2


Notices

This information was developed for products and services offered in the US. This material might beavailable from IBM in other languages. However, you may be required to own a copy of the product orproduct version in that language in order to access it.

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 inyour area. Any reference to an IBM product, program, or service is not intended to state or imply thatonly that IBM product, program, or service may be used. Any functionally equivalent product, program, orservice that does not infringe any IBM intellectual property right may be used instead. However, it is theuser's 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 thisdocument. The furnishing of this document does not grant you any license to these patents. You cansend license inquiries, in writing, to:

IBM Director of LicensingIBM CorporationNorth Castle Drive, MD-NC119Armonk, NY 10504-1785US

For license inquiries regarding double-byte character set (DBCS) information, contact the IBM IntellectualProperty Department in your country or send inquiries, in writing, to:

Intellectual Property LicensingLegal and Intellectual Property LawIBM Japan, Ltd.19-21, Nihonbashi-Hakozakicho, Chuo-kuTokyo 103-8510, Japan

INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS PUBLICATION "AS IS"WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITEDTO, THE IMPLIED WARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR APARTICULAR PURPOSE. Some jurisdictions do not allow disclaimer of express or implied warranties incertain transactions, therefore, this statement may not apply to you.

This information could include technical inaccuracies or typographical errors. Changes are periodicallymade to the information herein; these changes will be incorporated in new editions of the publication.IBM may make improvements and/or changes in the product(s) and/or the program(s) described in thispublication at any time without notice.

Any references in this information to non-IBM websites are provided for convenience only and do not inany manner serve as an endorsement of those websites. The materials at those websites are not part ofthe materials for this IBM product and use of those websites is at your own risk.

IBM may use or distribute any of the information you provide in any way it believes appropriate withoutincurring any obligation to you.

Licensees of this program who wish to have information about it for the purpose of enabling: (i) theexchange of information between independently created programs and other programs (including thisone) and (ii) the mutual use of the information which has been exchanged, should contact:

IBM Director of LicensingIBM CorporationNorth Castle Drive, MD-NC119Armonk, NY 10504-1785US


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 byIBM under terms of the IBM Customer Agreement, IBM International Program License Agreement or anyequivalent agreement between us.

The performance data and client examples cited are presented for illustrative purposes only. Actualperformance results may vary depending on specific configurations and operating conditions.

Information concerning non-IBM products was obtained from the suppliers of those products, theirpublished announcements or other publicly available sources. IBM has not tested those products andcannot confirm the accuracy of performance, compatibility or any other claims related to non-IBMproducts. Questions on the capabilities of non-IBM products should be addressed to the suppliers ofthose products.

Statements regarding IBM's 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 illustratethem as completely as possible, the examples include the names of individuals, companies, brands, andproducts. All of these names are fictitious and any similarity to actual people or business enterprises isentirely coincidental.

COPYRIGHT LICENSE:

This information contains sample application programs in source language, which illustrate programmingtechniques on various operating platforms. You may copy, modify, and distribute these sample programsin any form without payment to IBM, for the purposes of developing, using, marketing or distributingapplication programs conforming to the application programming interface for the operating platformfor which the sample programs are written. These examples have not been thoroughly tested underall conditions. IBM, therefore, cannot guarantee or imply reliability, serviceability, or function of theseprograms. The sample programs are provided "AS IS", without warranty of any kind. IBM shall not beliable for any damages arising out of your use of the sample programs.

Each copy or any portion of these sample programs or any derivative work must include a copyright notice as follows: © (your company name) (year). Portions of this code are derived from IBM Corp. Sample Programs. © Copyright IBM Corp. _enter the year or years_.

Programming interface informationThis information is intended to help programmers, operators, and system support personnel diagnoseIMS problems. This information also documents Diagnosis, Modification or Tuning Information providedby IMS.

Diagnosis, Modification or Tuning information is provided to help you diagnose, modify, or tune IMS. Donot use this Diagnosis, Modification or Tuning information as a programming interface.

Diagnosis, Modification or Tuning Information is identified where it occurs, either by an introductorystatement to a section or topic, or by the following marking: Diagnosis, Modification or TuningInformation.

TrademarksIBM, the IBM logo, and ibm.com® are trademarks or registered trademarks of International BusinessMachines Corp., registered in many jurisdictions worldwide. Other product and service names might betrademarks of IBM or other companies. A current list of IBM trademarks is available on the web at"Copyright and trademark information" at http://www.ibm.com/legal/copytrade.shtml.

1388 Notices

http://www.ibm.com/legal/copytrade.shtml

Adobe, the Adobe logo, and the PostScript logo are either registered trademarks or trademarks of AdobeSystems Incorporated in the United States, and/or other countries.

Linux® is a registered trademark of Linus Torvalds in the United States, other countries, or both.

Microsoft, Windows, Windows NT, and the Windows logo are trademarks of Microsoft Corporation in theUnited States, other countries, or both.

Java and all Java-based trademarks and logos are trademarks or registered trademarks of Oracle and/orits affiliates.

UNIX is a registered trademark of The Open Group in the United States and other countries.

Terms and conditions for product documentationPermissions for the use of these publications are granted subject to the following terms and conditions.

ApplicabilityThese terms and conditions are in addition to any terms of use for the IBM website.

Personal useYou may reproduce these publications for your personal, noncommercial use provided that all proprietarynotices are preserved. You may not distribute, display or make derivative work of these publications, orany portion thereof, without the express consent of IBM.

Commercial useYou may reproduce, distribute and display these publications solely within your enterprise providedthat all proprietary notices are preserved. You may not make derivative works of these publications, orreproduce, distribute or display these publications or any portion thereof outside your enterprise, withoutthe express consent of IBM.

RightsExcept as expressly granted in this permission, no other permissions, licenses or rights are granted, eitherexpress or implied, to the publications or any information, data, software or other intellectual propertycontained therein.

IBM reserves the right to withdraw the permissions granted herein whenever, in its discretion, the useof the publications is detrimental to its interest or, as determined by IBM, the above instructions are notbeing properly followed.

You may not download, export or re-export this information except in full compliance with all applicablelaws and regulations, including all United States export laws and regulations.

IBM MAKES NO GUARANTEE ABOUT THE CONTENT OF THESE PUBLICATIONS. THE PUBLICATIONSARE PROVIDED "AS-IS" AND WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED,INCLUDING BUT NOT LIMITED TO IMPLIED WARRANTIES OF MERCHANTABILITY, NON-INFRINGEMENT,AND FITNESS FOR A PARTICULAR PURPOSE.

IBM Online Privacy StatementIBM Software products, including software as a service solutions, (“Software Offerings”) may use cookiesor other technologies to collect product usage information, to help improve the end user experience,to tailor interactions with the end user or for other purposes. In many cases no personally identifiableinformation is collected by the Software Offerings. Some of our Software Offerings can help enable youto collect personally identifiable information. If this Software Offering uses cookies to collect personallyidentifiable information, specific information about this offering’s use of cookies is set forth below.

Notices 1389

This Software Offering does not use cookies or other technologies to collect personally identifiableinformation.

If the configurations deployed for this Software Offering provide you as customer the ability to collectpersonally identifiable information from end users via cookies and other technologies, you should seekyour own legal advice about any laws applicable to such data collection, including any requirements fornotice and consent.

For more information about the use of various technologies, including cookies, for these purposes,See IBM’s Privacy Policy at http://www.ibm.com/privacy and IBM’s Online Privacy Statement at http://www.ibm.com/privacy/details the section entitled “Cookies, Web Beacons and Other Technologies”and the “IBM Software Products and Software-as-a-Service Privacy Statement” at http://www.ibm.com/software/info/product-privacy.


http://www.ibm.com/privacy

http://www.ibm.com/privacy/details

http://www.ibm.com/privacy/details

http://www.ibm.com/software/info/product-privacy

http://www.ibm.com/software/info/product-privacy

Bibliography

This bibliography lists all of the publications in the IMS 15 library.

Title Acronym Order number

IMS Version 15 Application Programming APG SC27-6778

IMS Version 15 Application Programming APIs APR SC27-6779

IMS Version 15 Commands, Volume 1: IMS CommandsA-M

CR1 SC27-6780

IMS Version 15 Commands, Volume 2: IMS CommandsN-V

CR2 SC27-6781

IMS Version 15 Commands, Volume 3: IMS Componentand z/OS Commands

CR3 SC27-6782

IMS Version 15 Communications and Connections CCG SC27-6783

IMS Version 15 Database Administration DAG SC27-6784

IMS Version 15 Database Utilities DUR SC27-6785

IMS Version 15 Diagnosis DGR GC27-6786

IMS Version 15 Exit Routines ERR SC27-6787SC19-4208

IMS Version 15 Installation INS SC27-6788

IMS Version 15 Licensed Program Specifications LPS GC27-6799

IMS Version 15 Messages and Codes, Volume 1: DFSMessages

MC1 GC27-6789

IMS Version 15 Messages and Codes, Volume 2: Non-DFSMessages

MC2 GC27-6790

IMS Version 15 Messages and Codes, Volume 3: IMSAbend Codes

MC3 GC27-6791

IMS Version 15 Messages and Codes, Volume 4: IMSComponent Codes

MC4 GC27-6792

IMS Version 15 Operations and Automation OAG SC27-6793

IMS Version 15 Release Planning RPG GC27-6794

IMS Version 15 System Administration SAG SC27-6795

IMS Version 15 System Definition SDG GC27-6796

IMS Version 15 System Programming APIs SPR SC27-6797

IMS Version 15 System Utilities SUR SC27-6798


IBM®

Product Number: 5635-A06 5655-DS5 5655-TM4

GC27-6789-00

IMS: Messages and Codes, Volume 1 - IBM

Documents

Transcript of IMS: Messages and Codes, Volume 1 - IBM