Version 2 Release 3 z/OS - IBM€¦ · 24/06/2019 · ROUTCDE and DESC keyword parameters on WTO and WTOR macros, which are the primary methods that programs use to issue messages

z/OSVersion 2 Release 3

MVS System Messages Volume 9 (IGF -IWM)

IBM

SA38-0676-30

Note

Before using this information and the product it supports, read the information in “Notices” on page1767.

This edition applies to Version 2 Release 3 of z/OS (5650-ZOS) and to all subsequent releases and modifications untilotherwise indicated in new editions.

Last updated: 2019-06-24© Copyright International Business Machines Corporation 1988, 2017.US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contract withIBM Corp.

Contents

About this document..............................................................................................v

How to send your comments to IBM.......................................................................ix

Summary of changes.............................................................................................xi

Chapter 1. IGF messages....................................................................................... 1

Chapter 2. IGGHC messages................................................................................ 33

Chapter 3. IGGN messages.................................................................................. 43

Chapter 4. IGV messages..................................................................................... 63

Chapter 5. IGVH messages...................................................................................69

Chapter 6. IGW messages.................................................................................... 91

Chapter 7. IHJ messages................................................................................... 705

Chapter 8. IKJ messages................................................................................... 721

Chapter 9. IKM messages...................................................................................777

Chapter 10. ILM messages................................................................................. 819

Chapter 11. ILR messages..................................................................................821

Chapter 12. ILRH messages............................................................................... 845

Chapter 13. IOP messages................................................................................. 857

Chapter 14. IOS messages................................................................................. 861

Chapter 15. IOSHC messages...........................................................................1297

Chapter 16. IPD messages............................................................................... 1335

Chapter 17. IQP messages............................................................................... 1355

Chapter 18. IRA messages............................................................................... 1383

Chapter 19. IRD messages............................................................................... 1427

Chapter 20. ISG messages............................................................................... 1433

iii

Chapter 21. ISGH messages.............................................................................1615

Chapter 22. ISN messages............................................................................... 1643

Chapter 23. ITT messages................................................................................1653

Chapter 24. ITV messages................................................................................1691

Chapter 25. ITZ messages................................................................................1693

Chapter 26. IWM messages..............................................................................1705

Appendix A. Accessibility.................................................................................1763

Notices............................................................................................................1767

Index.............................................................................................................. 1771

iv

About this document

MVS System Messages primarily describe messages that are issued to the system operator at the systemconsole and system messages that are logged. The following messages are included:

• Operator messages that are issued by the BCP and DFSMS.• Log messages that are issued by the BCP and DFSMS.• Some SYSOUT messages that are issued by the BCP and DFSMS. SYSOUT messages are issued by

utilities that normally run in batch, such as SPZAP.• Batch job messages that are issued by the BCP. Messages that are issued by JES2 or JES3 for batch jobs

are in the JES messages documents.

Usually, messages that are issued at interactive terminals (like TSO/E and CICS® terminals) aredocumented by the specific elements and products that support those terminals.

The titles of the MVS™ System Messages indicate the range of message prefixes in the documents:

• z/OS MVS System Messages, Vol 1 (ABA-AOM)• z/OS MVS System Messages, Vol 2 (ARC-ASA)• z/OS MVS System Messages, Vol 3 (ASB-BPX)• z/OS MVS System Messages, Vol 4 (CBD-DMO)• z/OS MVS System Messages, Vol 5 (EDG-GFS)• z/OS MVS System Messages, Vol 6 (GOS-IEA)• z/OS MVS System Messages, Vol 7 (IEB-IEE)• z/OS MVS System Messages, Vol 8 (IEF-IGD)• z/OS MVS System Messages, Vol 9 (IGF-IWM)• z/OS MVS System Messages, Vol 10 (IXC-IZP)

Some of the other types of message information include the following titles.

• z/OS MVS Dump Output Messages• z/OS MVS System Codes• z/OS and z/VM HCD Messages• z/OS JES3 Messages• z/OS TSO/E Messages• z/OS UNIX System Services Messages and Codes

For a list of message information that is sorted by message prefix, see the "Introduction" section in z/OSMVS System Messages, Vol 1 (ABA-AOM).

This information also contains the routing and descriptor codes that IBM® assigns to the messages thatz/OS® components, subsystems, and products issue. Routing and descriptor codes are specified by theROUTCDE and DESC keyword parameters on WTO and WTOR macros, which are the primary methods thatprograms use to issue messages. The routing code identifies where a message is displayed. Thedescriptor code identifies the significance of the message and the color of the message on operatorconsoles with color.

Who uses MVS System Message informationMVS System Messages are for programmers who receive messages from the system. Usually, these peopleare system operators, system programmers, and application programmers who do any of the followingtasks.

© Copyright IBM Corp. 1988, 2017 v

• Initialize the operating system and its subsystems.• Monitor system activity.• Keep the system correctly running.• Diagnose and correct system problems.• Diagnose and correct errors in problem programs.

How to use message informationThe system messages contain descriptions of messages. For details about z/OS message formats, prefixby component, descriptions, and more see the "Introduction" section in z/OS MVS System Messages, Vol 1(ABA-AOM).

Where to find more informationThis information explains how z/OS references information in other documents and on the web.

When possible, this information uses cross-document links that go directly to the topic in reference usingshortened versions of the document title. For complete titles and order numbers of the documents for allproducts that are part of z/OS, see z/OS Information Roadmap.

To find the complete z/OS library, including the IBM Knowledge Center for z/OS, see the followingresources.

z/OS Internet library (www.ibm.com/servers/resourcelink/svc00100.nsf/pages/zosInternetLibrary)IBM Knowledge Center (www.ibm.com/support/knowledgecenter/SSLTBW/welcome)

Many message descriptions refer to the following terms. You need to consult the reference listed belowfor more information:

• Data areas and control blocks: See z/OS MVS Data Areas in the z/OS Internet library (www.ibm.com/servers/resourcelink/svc00100.nsf/pages/zosInternetLibrary) or IBM Knowledge Center(www.ibm.com/support/knowledgecenter/SSLTBW/welcome).

• Dumps: For examples of ABEND, stand-alone, and SVC dumps and how to read them, see z/OS MVSDiagnosis: Tools and Service Aids. For examples of component output from dumps and how to read andrequest it, see z/OS MVS Diagnosis: Reference.

• Identification of a component, subsystem, or product: See the z/OS MVS Diagnosis: Reference toidentify the component, subsystem, or product from the name of an IBM module or for a macro. Themodule prefix and macro tables give the program identifier to be used in a PIDS symptom in a searchargument.

• System completion and wait state codes: See z/OS MVS System Codes.• Logrec data set error records: For the formatted records, see z/OS MVS Diagnosis: Reference.• Trace output: For the formats and the meaning of the information in the generalized trace facility (GTF)

trace, instruction address trace, master trace, system trace, and component trace, see z/OS MVSDiagnosis: Tools and Service Aids.

• Hardware: Use the appropriate Principles of Operation document for the hardware you have installed.

Where to find the most current message informationThe MVS System Messages documents are cumulative. As messages are added to the system, they areadded to the documents. Similarly, when messages are changed on the system, they are changed in thedocuments. However, when a message is deleted from the system (no longer issued), the message is notdeleted from the document. You can always look in the most recent message information for thedescriptions of all system messages.

To find the most current edition of a message or document, see the following resources.

vi About this document

http://www.ibm.com/servers/resourcelink/svc00100.nsf/pages/zosInternetLibraryhttp://www.ibm.com/support/knowledgecenter/SSLTBW/welcomehttp://www.ibm.com/servers/resourcelink/svc00100.nsf/pages/zosInternetLibraryhttp://www.ibm.com/servers/resourcelink/svc00100.nsf/pages/zosInternetLibraryhttp://www.ibm.com/support/knowledgecenter/SSLTBW/welcomehttp://www.ibm.com/support/knowledgecenter/SSLTBW/welcome

z/OS Internet library (www.ibm.com/servers/resourcelink/svc00100.nsf/pages/zosInternetLibrary)IBM Knowledge Center (www.ibm.com/support/knowledgecenter/SSLTBW/welcome)

About this document vii

http://www.ibm.com/servers/resourcelink/svc00100.nsf/pages/zosInternetLibraryhttp://www.ibm.com/support/knowledgecenter/SSLTBW/welcome

viii z/OS: MVS System Messages Volume 9 (IGF - IWM)

How to send your comments to IBM

We invite you to submit comments about the z/OS product documentation. Your valuable feedback helpsto ensure accurate and high-quality information.

Important: If your comment regards a technical question or problem, see instead “If you have a technicalproblem” on page ix.

Submit your feedback by using the appropriate method for your type of comment or question:Feedback on z/OS function

If your comment or question is about z/OS itself, submit a request through the IBM RFE Community(www.ibm.com/developerworks/rfe/).

Feedback on IBM Knowledge Center functionIf your comment or question is about the IBM Knowledge Center functionality, for example searchcapabilities or how to arrange the browser view, send a detailed email to IBM Knowledge CenterSupport at [email protected].

Feedback on the z/OS product documentation and contentIf your comment is about the information that is provided in the z/OS product documentation library,send a detailed email to [email protected]. We welcome any feedback that you have, includingcomments on the clarity, accuracy, or completeness of the information.

To help us better process your submission, include the following information:

• Your name, company/university/institution name, and email address• The following deliverable title and order number: z/OS MVS System Messages, Vol 9 (IGF-IWM),

SA38-0676-30• The section title of the specific information to which your comment relates• The text of your comment.

When you send comments to IBM, you grant IBM a nonexclusive right to use or distribute the commentsin any way appropriate without incurring any obligation to you.

IBM or any other organizations use the personal information that you supply to contact you only about theissues that you submit.

If you have a technical problemIf you have a technical problem or question, do not use the feedback methods that are provided forsending documentation comments. Instead, take one or more of the following actions:

• Go to the IBM Support Portal (support.ibm.com).• Contact your IBM service representative.• Call IBM technical support.

© Copyright IBM Corp. 1988, 2017 ix

http://www.ibm.com/developerworks/rfe/http://www.ibm.com/developerworks/rfe/mailto:[email protected]:[email protected]://support.ibm.com

x z/OS: MVS System Messages Volume 9 (IGF - IWM)

Summary of changes

This information includes terminology, maintenance, and editorial changes. Technical changes oradditions to the text and illustrations for the current edition are indicated by a vertical line to the left ofthe change.

Summary of changes for z/OS MVS System Messages, Vol 9 (IGF-IWM) forVersion 2 Release 3 (V2R3) and its updates

Message changes for z/OS MVS System Messages, Vol 9 (IGF-IWM)The following messages are new, changed, or no longer issued in V2R3.

New

The following messages are new.

IGV011IIGVH113I for APAR OA53355IGVH114E for APAR OA53355IGW285I for APAR OA54822IGW286I for APAR OA54822IGW287I for APAR OA54822IGW288I for APAR OA56745IGW10120IIGW10121IIGW10122IIGW345I for APAR OA46787IGW346I for APAR OA51165IGW584I for APAR OA55552IGW585I for APAR OA55552IGW634EIGW705I for APAR UA82464IGW10121I for APAR OA48404IKJ598I for APAR OA50265ILR040WIOS060I for APAR OA53082IOS061I for APAR OA53082IOS279I for APAR OA52379IOS280I for APAR OA52379IOS282I for APAR OA52379IOS637E for APAR OA50653IOS639E for APAR OA50653IOS640I for APAR OA50653IOS641I for APAR OA54600IOS642I for APAR OA54600IOS643I for APAR OA54600IOSHC160I for APAR OA51982IOSHC161E for APAR OA51982

© Copyright IBM Corp. 1988, 2017 xi

IOSHC162I for APAR OA51982IOSHM0201I for APAR OA53082IOSPF119I for APAR OA48188IOSPF165I for APAR OA48188IOSPF219I for APAR OA48188IOSPF265I for APAR OA48188IOSPF319I for APAR OA48188IOSPF365I for APAR OA48188IOSPF700I for APAR OA53156IOSPF704I for APAR OA53156IOSPF705E for APAR OA53156IOSPF706I for APAR OA53156IOSPF720I for APAR OA53156IOSPF721I for APAR OA53156IOSPF722I for APAR OA53156IOSPF751I for APAR OA53156IOSPF752I for APAR OA53156IOSPF753I for APAR OA53156IOSPF754I for APAR OA53156IOSPF755I for APAR OA53156IOSPF756I for APAR OA53156IOSPF757I for APAR OA53156IOSPF758I for APAR OA53156IOSPF759I for APAR OA53156IOSPF760I for APAR OA53156IOSPF761I for APAR OA53156IOSPF762I for APAR OA53156IOSPF763I for APAR OA53156ISN014I for APAR OA49692IWM068I for APAR OA50403

Changed

The following messages are changed.

IGF512IIGF513IIGWRH0202EIGX031I for APAR OA50850IGW467IIGW700IIGW705I for APAR OA50442IGW803I for APAR OA50489IGW1001TIGW1003TIGW1004TIGW1005TIGW1006TIGW1007TIGW1009TIGW1010TIGW1011TIGW1012T

xii z/OS: MVS System Messages Volume 9 (IGF - IWM)

IGW1013TIGW1015TIGW1016TIGW1017TIGW1019TIGW1030TIGW1031TIGW1033TIGW1034TIGW1035TIGW1036TIGW1037TIGW1038TIGW1039TIGW1040TIGW1041SIGW1043TIGW1044SIGW1045SIGW1046SIGW1047SIGW1048SIGW1051SIGW1052EIGW1053TIGW1054TIGW1056TIGW1057SIGW1058EIGW1059TIGW1060EIGW1061IIGW1062IIGW1064SIGW1065SIGW1066SIGW1071SIGW1072EIGW1073SIGW1075TIGW1076EIGW1077EIGW1078EIGW1079EIGW1080TIGW1081TIGW1087TIGW1103SIGW1104SIGW1106SIGW1107S

Summary of changes xiii

IGW1108SIGW1121TIGW1122TIGW1123SIGW1125TIGW1129SIGW1130TIGW1150TIGW1151TIGW1152TIGW1153TIGW1155TIGW1156WIGW1157TIGW1159TIGW1160TIGW1161EIGW1162EIGW1163EIGW1164EIGW1165TIGW1170WIGW1202WIGW01595EIKJ143IIOS000I for APAR OA48710IOS078IIOS085I for APAR OA51327, APAR OA50653 and APAR OA53143IOS090I for APAR OA51327IOS098IIOS281I FOR APAR OA52379IOS290I FOR APAR OA52379IOS500IIOS506I for APAR OA49090IOS634I for APAR OA50653IOS635I for APAR OA53083IOSHM0201IIOSHC133IIOSPF108I for APAR OA51327IOSPF154I for APAR OA51327IOSPF208I for APAR OA51327IOSPF308I for APAR OA51327IOSPF354I for APAR OA51327IOSPF254I for APAR OA51327IOSPF205IIQP022I for APAR OA51289IQP024I for APAR OA51289 and APAR OA50653IQP041IIRA127IIRA205I for APAR OA54554ISG343I

xiv z/OS: MVS System Messages Volume 9 (IGF - IWM)

IWM002IIWM025IIWM064I for APAR OA50403IWM066IIWM075I

Deleted

The following messages are no longer issued.

IGW10081IIOSPF351I for APAR OA51327IWM070IIWM077EIWM078EIWM079EIWM080EIWM081EIWM082EIWM083EIWM084I

Summary of changes for z/OS MVS System Messages, Vol 9 (IGF-IWM) forVersion 2 Release 2 (V2R2) and its updates

The following lists indicate the messages that are new, changed, or no longer issued in z/OS V2R2 and itsupdates. Messages that have been added, updated, or that are no longer issued in an updated edition ofV2R2 are identified by the quarter and year that the message was updated, in parentheses. For example,(4Q2015) indicates that a message was updated in the fourth quarter of 2015.

Message changes for z/OS MVS System Messages, Vol 9 (IGF-IWM)The following messages are new, changed, or no longer issued in V2R2.

New


IGGHC114IIGGHC115IIGGHC116EIGGHC118IIGGHC119IIGGHC120IIGGHC121IIGW029IIGW048AIGW423IIGW705IIGW710IIGW10081IIGW01185EIGW01186TIGW01187T

Summary of changes xv

IGW01188TIGW01212EIGW10120IIOS128IIOS083I (1Q2016)IOS128I (1Q2016)IOS584I (1Q2016)IOSHC150I (2Q2016)IOSHC151E (2Q2016)IOSHC152I (2Q2016)IOSHC155I (2Q2016)IOSHC156E (2Q2016)IOSHC157I (2Q2016)IOSHM0818IIOSHM0819IIOSHM0820E (1Q2016)IRA260E (1Q2016)IRA262I (1Q2016)IRA265I (1Q2016)ISG382IISG383IISG384IISG385IISG386IIRA450EIRA452IIRA459IIRA866IIWM066IIWM067I

Changed


IGW040I (1Q2016)IGW467IIGW700I (1Q2016)IGW01011T (1Q2016)IOS000I (1Q2016)IOS051I (1Q2016)IOS080I (1Q2016)IOS085I (1Q2016)IOS087I (1Q2016)IOS202E (1Q2016)IOS500I (1Q2016)IOSHM0201IIOSHM0303IIOSHM0304IIOSHM0399IIOSHM0401IIOSHM0420IIOSHM0806I

xvi z/OS: MVS System Messages Volume 9 (IGF - IWM)

IQP001I (1Q2016)IQP002I (1Q2016)IQP022I (1Q2016)IQP023I (1Q2016)IQP024I (1Q2016)IRA200E (1Q2016)IRA201E (1Q2016)IRA202I (1Q2016)IRA206I (1Q2016)ISG343I - Indicates the active GRSMONxx parmlib member.ISG365I - Indicates errors related to the GRSMONxx parmlib member.IWM001IIWM005WIWM054IIWM063IIWM064I

Deleted

The following messages were deleted.

IOS583I

Summary of message changes for z/OS MVS System Messages, Vol 9 (IGF-IWM) for Version 2 Release 1, as updated February 2015

The following messages are new, changed, or no longer issued for z/OS MVS System Messages, Vol 9(IGF-IWM) in the February 2015 update of z/OS V2R1. For more information, see z/OS MVS SystemMessages, Vol 9 (IGF-IWM).

New


IGF960IIOS634IIOSHC099IIOSHC140IIOSHC141IIOSHC142EIOSHC143IIOSHC144IIOSHC145IIOSHM0316IIOSHM0433IIOSHM0434IIOSHM0818IIOSHM0819I

Changed


IOS087IIOS090I

Summary of changes xvii

IOS156IIOS157IIOS158IIOS500IIOS502IIOS1500IIOSHM0201IIOSHM0303IIOSHM0304IIOSHM0399IIOSHM0401IIOSHM0416IIOSHM0420IIOSHM0427IIOSHM0806I

Deleted

The following messages are no longer issued.

IOS583I

Summary of changes for z/OS Version 2 Release 1 as updated March 2014The following changes are made to z/OS Version 2 Release 1 (V2R1) as updated March 2014.

New

ILRH0112I

Changed

No messages were changed in this document.

Deleted

No content was removed from this document.

Summary of changes for z/OS Version 2 Release 1 as updated December2013

This information summarizes the changes for z/OS Version 2 Release 1 (V2R1) as updated December2013.

Changed

The following message is restored in this publication:

IGW702I

z/OS Version 2 Release 1 summary of changesSee the Version 2 Release 1 (V2R1) versions of the following publications for all enhancements related toz/OS V2R1:

xviii z/OS: MVS System Messages Volume 9 (IGF - IWM)

• z/OS Migration• z/OS Planning for Installation• z/OS Summary of Message and Interface Changes• z/OS Introduction and Release Guide

Summary of changes xix

xx z/OS: MVS System Messages Volume 9 (IGF - IWM)

Chapter 1. IGF messages

IGF500D REPLY ‘YES’, DEVICE, OR ‘NO’

Explanation

The swap request (operator-initiated or system-initiated, as per message IGF500I) will not complete until theoperator responds YES or NO to this message.

This message is issued at the start of a swap sequence.

Note: This message will not be issued for tape devices attached to a tape library, and it will also not be issued forSMS managed mountable devices.

System action

The system continues processing. The operator-initiated request will not complete until the operator respondsto the message. The ‘YES’ or ‘DEVICE’ reply invokes the DDR function. The ‘NO’ reply causes a permanent I/Oerror to be posted for device dev1, operator SWAP command to be canceled as appropriate.

Operator response

• If a SWAP to device dev2 is desired, reply ‘YES’. For tape devices, message IGF502E will be issued and a tapemust be mounted on dev2 before swap can successfully complete. This must be done in a timely manner.Resources during this time may be restricted and can potentially cause hangs until this tape mount is satisfied.

• If a SWAP is desired, but device dev2 is not acceptable, enter the device number of the device to which thevolume on dev1 is to be moved. Make sure that the device has an available path before entering this reply.

• If a SWAP is not desired, enter reply ‘NO’.• If PAGING I/O ERROR appears in the message text, one or more jobs will almost certainly be ended if a ‘NO’

response is given.

Note:

1. When continuing with the SWAP, either by answering ‘YES’ or a device number, do not move the volume untilthe ‘PROCEED’ message, IGF502E, is issued or data set integrity may be lost.

2. If device dev1 is a 3340/3344 device with the fixed-head feature, device dev2 must also have the fixed-headfeature.

3. If you are using magnetic tape units and dev1 contains reels of different tape densities for input, be sure thatdev1 and dev2 have the same dual density capability.

4. If device dev2 was offline, the system might request operator intervention (via message IEA000A) before itcan issue message IGF502E. If so, mount a scratch tape. It will be unloaded, and then message IGF502E willbe issued.

Caution: If the volume is a direct access storage device, care must be taken to ensure that no head-diskinterference ("head crash") problem exists.

Source

Dynamic device reconfiguration (DDR)

Module

IGFDV0

Routing code

1,3,4,7,11

© Copyright IBM Corp. 1988, 2017 1

Descriptor code

2

IGF500I SWAP dev1 TO dev2 - {text}

Explanation

text is one of the following:

• OPERATOR• I/O ERROR• PAGING I/O ERROR

This message is issued at the start of a swap sequence.

The message is a repeat for verification of a SWAP command entered by the operator or a request to move avolume as a result of a permanent I/O error on the device with a device number of dev1. PAGING I/O ERRORindicates that a duplexed paging request has received an I/O error.

If JES3 is in use on your system and device dev1 is the same as device dev2, see the restrictions for using DDR(dynamic device reconfiguration) that are documented in z/OS JES3 Initialization and Tuning Reference.

If the device number is not allowed in reply, dev1 is a shared direct access storage device. It can only beremoved and replaced on a spare drive on the same control unit and readied with the device number dev1.

System action

The system issues message IGF500D to prompt the operator for a reply.

Note: Message IGF500D will not be issued for tape devices attached to a tape library, and it will also not beissued for SMS managed mountable devices.

Operator response

See the operator response for message IGF500D.

Source


Module

IGFDV0

Routing code

1

Descriptor code

2,7

IGF501I WARNING - dev1 AND dev2 ARE OF UNEQUAL BUT COMPATIBLEDENSITIES

Explanation

While processing a tape swap, DDR chose a ‘TO’ device that can operate at the density of the tape beingswapped. However, the densities of the ‘TO’ and ‘FROM’ devices, though compatible, are unequal.

2 z/OS: MVS System Messages Volume 9 (IGF - IWM)

System action

The system issues message IGF500D and waits for the operator to reply.

Operator response

Reply to message IGF500D. If you do not want to swap between densities you can use the DEVICE reply andchoose an alternate device of equal density.

Source


Module

IGFDV0

Routing code

1,3,11

Descriptor code

4

IGF502E PROCEED WITH SWAP OF dev1 TO dev2

Explanation

DDR is waiting for the operator to swap volumes.

System action

The system continues operation.

Operator response

For tape swaps, move the volume on the device with device number dev1 to dev2 and DO NOT mount any tapeon dev1 as this will cause the loss of buffered write data. For disk swaps, move the volume on the device withdevice number dev1 to dev2, and if a volume is on dev2, move that volume to dev1 and make both devices ready.For disk swaps, when dev1 and dev2 are the same device, make the device not ready and then make it ready.

Note: The tape must be mounted in a timely manner. This will ensure resources that are currently held will befreed. If a tape is not able to be mounted, some event must occur to allow the DDR swap to complete. Examplesof such events are (1) Manually mounting a tape (if in an automated environment), (2) Cancelling the job thatinitiated the DDR swap, (3) Issuing the VARY OFFLINE,dev2,FORCE operator command to force the dev2 deviceoffline.

Source


Module

IGFDV0

Routing code

1,3,4,7,11

IGF messages 3

Descriptor code

11

IGF503I ERROR ON dev, SELECT NEW DEVICE

Explanation

A permanent I/O error has occurred during DDR tape repositioning, which was in process in response to a SWAPrequest to dev. The error occurred positioning the tape from load point on dev. This message is followed byIGF509D to allow the operator to respond.

System action

The tape is rewound and unloaded. The system continues operation.

Operator response

Specify a new device number to replace dev, in response to message IGF509D, or reply ‘NO’. If the reply is ‘NO’,the associated job must be canceled by the operator because the tape is not positioned correctly.

Source


Module

IGFDT2

Routing code

1,3,11

Descriptor code

4

IGF505I SWAP FROM dev1 TO dev2 COMPLETE

Explanation

The tape SWAP requested for the volume originally on dev1 is now complete. This message does not appear fordirect access devices or for unit record devices.

System action


Source


Module

IGFDI1

Routing code

1,3,11


Descriptor code

4

IGF508A MOUNT AN UNLABELED SCRATCH TAPE ON dev TO EXIT SWAPPROCESSING

Explanation

Following a DDR tape repositioning error (after the tape was mounted on dev), and the operator replied "NO" toIGF509D, an unlabeled scratch tape needs to be mounted on dev before DDR swap processing can successfullycomplete.

System action

The system continues processing. The swap will not complete until a tape is mounted on dev or the device isforced offline.

Operator response

Do one of the following:

1. Mount a unlabeled scratch tape on dev.2. Force the device offline by issuing VARY dev,OFFLINE,FORCE.

Source


Module

IGFDV0

IGF509D REPLY DEVICE, OR ‘NO’

Explanation

The swap request (operator-initiated or system-initiated, as per message IGF509I) will not complete until theoperator responds with a device number or NO to this message.

This message is issued if there is another error during the original swap sequence.

System action

The system continues processing. The SWAP will not complete until the operator responds with one of theindicated replies.

Operator response

If the DDR function is desired, reply with a device number for a device of the same type as dev (in messageIGF503I or IGF509I). The device number can be optionally preceded with a slash to differentiate a devicenumber from a device (for example, /3480). A deallocated device on a different channel is usually preferred.Make sure that the device has an available path before replying to this message. If the DDR function is notdesired, reply ‘NO’.

Note:

1. If PAGING I/O ERROR appears in the message text, a ‘NO’ reply to the request will almost certainly result inan abnormal ending for one or more jobs.

2. When continuing with the swap by answering a device number, do not move the volume until the ‘PROCEED’message, IGF502E, is issued or data set integrity may be lost.

IGF messages 5

3. When swapping a 3340/3344 device with the fixed-head feature, be sure that the "TO" device also has thefixed-head feature installed.

Caution: If the volume is a direct access storage device, care must be taken to ensure that no head-diskinterference ("head crash") problem exists.

For tape swaps, if you reply 'NO' to this message and this message was preceded by message IGF503I, DDR willunload the tape. The UCB indicator of the drive is set to describe that the correct tape positioning has been lost.When this bit is set after a BSAM SYNAD routine indicates to restart tape IO write operations, the system issuesABEND001. BEcasue tape positioning has been compromised, no further attempt is made in the EOV forcecomments : e ESTAE routine to issue any writes to the volume since tape positioning has been compromised.

For a D/T3480 ACL drive running in AUTO mode, if you reply ‘NO’ to this message, DDR will unload the tape andload the next available tape in the hopper. The drive will become ready. CLOSE processing will be satisfied withthe newly loaded tape (most likely a labeled scratch tape) and the label will be written over. You should load anon-labeled scratch tape before replying ‘NO’ to this message.

Source


Module

IGFDV0

Routing code

1,3,4,7,11

Descriptor code

2

IGF509I SWAP dev - {text}

Explanation


• OPERATOR• I/O ERROR• PAGING I/O ERROR

This message is issued if there is another error during the original swap sequence.

If OPERATOR appears in the message text, the SWAP was requested by the operator. No valid ‘TO’ device isknown and a response is required. This message follows a SWAP command when the ‘TO’ device is not valid fora SWAP.

If I/O ERROR or PAGING I/O ERROR appears in the message text, the SWAP is a result of a permanent I/O error.The I/O recovery procedures may be repeated on a new device. PAGING I/O ERROR indicates that a duplexedrequest has received an I/O error.

System action

The system issues message IGF509D to prompt the operator for a reply.

Operator response

See the operator response for message IGF509D.


Source


Module

IGFDV0

Routing code

1,3,4,7,11

Descriptor code

2,7

IGF511A WRONG VOLUME MOUNTED ON dev, MOUNT ser, {text}, nnn

Explanation


• AL• NL• NSL• SL

In performing a swap, the volume that had been on the "FROM" device was not put on dev. This messageappears only for tape swaps.

System action


Operator response

Remove the volume on the device with device number dev and replace it with the correct volume serial, labeltype (AL, NL, NSL, or SL), and sequence number (nnn). This message can be repeated as many as five times if awrong volume is consistently mounted, then IGF509D is issued allowing you to reply ‘NO’ to the swap request orselect another device.

Source


Module

IGFDT2

Routing code

1,3,11

Descriptor code

2

IGF512I SWAP FROM dev TERMINATED - textBUFFERED DATA EXCEEDS XXXXM-BYTES

IGF messages 7

Explanation

During a swap, DDR has encountered an error, preventing successful completion of the swap request from adevice. The various errors are indicated by the variable portion of the message text.

In the message text:BUFFERED DATA EXCEEDS XXXX M-BYTES

The amount of buffered data in the failing device that needs to be recovered by DDR is larger than the DDRstorage limit set in the DEVSUPxx member of SYS1.PARMLIB. Swap processing from dev is terminated.

devThe device number of the device being swapped from.

textThe possible message texts and their meanings:NO USER FOUND

DDR was unable to locate the user of the device after the swap commenced. The user of the device hasended, or the user's control blocks could not be located.

ERP IN PROGRESSWhile attempting to rewind and unload the "FROM" tape involved in an operator-requested swap, anerror recovery procedure (ERP) was found to be in progress.

OPEN/CLOSE/EOV IN PROGRESSDDR has found that the user of the "FROM" tape is in the process of OPEN, CLOSE, or EOV. The positionof the tape is not known.

BLOCKCOUNT UNRELIABLEIf the user of the tape is using the EXCP macro for I/O, he did not code the REPOS=Y parameter in hisDCB macro. As a result, the block count is not considered to be accurate and DDR cannot reposition thetape.

If the user of the tape is using the basic sequential access method, DDR has encountered a conditionwhere the tape is open for the CNTRL macro format and the block count is zero.

As a consequence, DDR cannot determine the position of the tape. This message also appears for allaccess methods if an attempt is made to SWAP a NL tape opened for the MOD disposition.

CANCELED BY OPERATORThis message is confirmation that the operator has replied ‘NO’ to message IGF500D or IGF509D. Theswap from dev is not completed.

INVALID USER EXITThe installation-written NSLREPOS routine has returned an incorrect return code to DDR.

CATASTROPHIC ERRORDDR has encountered a machine check, program check, ABEND, an I/O error that it cannot retry, orcontention exists for an MIH resource. The current swap from the indicated device is ended.

INVALID DEVICEThe device dev entered as the "FROM" device in the swap command is not valid.

CANCELED BY USERThe installation-written NSLREPOS routine has indicated that the swap is to be ended.

JES3 ERRORAn error occurred in a DDR/JES3 subsystem exit routine. The current swap from dev abnormally ends.

BY DEVICE SUPPORT MODULEThe device support module could not validate the swap.

RD BLKID ERRORDDR received a unit check in response to a Read Block ID command before the actual swap. The tapeposition cannot be determined, nor can the degree of data buffering be calculated.


RD BUFFER ERRORDDR received a unit check in response to a Read Buffer command before the actual swap. The buffereddata, which had not yet been written to tape, but had been sent from the host processor, cannot beretrieved.

GETMAIN FAILEDDuring DDR processing before the actual swap, the storage for saving the buffered data was insufficient.

DEVICE FORCED OFFLINEAn unrecoverable I/O error occurred which resulted in a loss of data. The tape subsystem is boxed(forced offline).

ACTIVATE IN PROGRESSThe direct access storage device (DASD) swap ended because an I/O configuration change is in progress.

PAGE FIX ERRORDuring DDR processing before the actual swap, the storage for saving the buffered data was unable to bepage fixed for the read buffer operation.

UNSUPPORTED RECORD LENGTHDuring DDR processing before the actual swap, it was determined that records buffered in the deviceexceed the 64 kilobytes maximum record length supported by the 3480/3490 device support module.

FAILURE DURING LIBRARY PROCESSINGDDR encountered an error associated with the mount or dismount services performed by the libraryautomation communication services (LACS), or an error during the volume verification services for asystem-initiated swap in a 3495 Tape Library Dataserver.

READ ERROR IN LIBRARYDDR encountered an error while attempting to read the label on the tape mounted on the 'TO' deviceduring a system-initiated swap in a 3495 Tape Library Dataserver.

REPOSITIONING ERROR IN LIBRARYDDR encountered an error while attempting to reposition the tape on the 'TO' device during a system-initiated swap in a 3495 Tape Library Dataserver.

EXIT I/O ERROR IN LIBRARYThe Device Service Exit performed the read of the volume label and the repositioning of the tape on thedevice. The swap is a system-initiated swap in a 3495 Tape Library Dataserver. The exit returned an errorcode to DDR indicating a failure during the read or repositioning stage.

SWITCH FAILED DUE TO I/O ERRORWhile attempting to terminate a PPRC pair, an I/O error was encountered.

NOT A VALID PPRC PAIRThe 'FROM' and 'TO' devices are permanent resident DASD but are not a valid PPRC pair. Only permanentresident DASD that are part of a PPRC pair can be swapped.

GETMAIN FAILED - SP245During DDR processing before the actual swap, the storage to read attention messages could not beobtained.

SWAP TERMINATED BY OPERATORThe operator indicated that the swap should be terminated in response to IGF520A, IGF521A, orIGF522A.

ERROR ACQUIRING TAPE FORMAT INFODDR was unable to obtain tape format information from the FROM device. The swap is ended.

ERROR ACQUIRING MODE CNTL INFORMATIONDDR was unable to obtain mode control information from the FROM device. The swap is ended.

ERROR SETTING MODE CNTL INFORMATIONDDR was unable to set mode control information to the FROM device. The swap is ended.

CATASTROPHIC ERROR - RSN=xxDDR encountered an error and cannot retry. The current swap from device dev ended. The reason codedisplayed indicates the specific reason for the failure.

IGF messages 9

See operator response for the description of the reason codes.

UCB SWAP FAILURE - RSN=xxThe attempt to swap UCBs failed. xx is the reason code which describes the failure. For a list of reasoncodes, see mapping macro IOSDSWAP in z/OS MVS Data Areas in the z/OS Internet library(www.ibm.com/servers/resourcelink/svc00100.nsf/pages/zosInternetLibrary).

System action

Processing continues.

Operator response

The response by the operator depends on the text of the message. Responses to each of the conditions aredetailed as follows:NO USER FOUND

Issue a DISPLAY U command to determine if the "FROM" tape is allocated. If it is not, no one is using thetape and you need not use DDR to move the volume on it. If the tape is allocated, reenter the swap commandto retry the swap. For a swap requested by the system as a result of a permanent error, no further action isnecessary.

ERP IN PROGRESSIf a system-initiated DDR request does not occur as a result of a permanent error, reenter the SWAPcommand to retry the swap.

OPEN/CLOSE/EOV IN PROGRESSReenter the SWAP command after the OPEN, CLOSE, or EOV processing is complete. This would involvemaking required volume mounts prior to issuing the SWAP command.

BLOCKCOUNT UNRELIABLEIf the user is using EXCP level I/O, he must correct the program so that it maintains an accurate block countand ensure that the DCB macro is coded with REPOS=YES. This will allow DDR to support the I/O for bothoperator requests and upon the occurrence of errors.

If the user is known to be using BSAM, or the tape is NL, opened for the MOD disposition, you may attempt toreenter the SWAP command after tape motion has taken place.

CANCELED BY OPERATORIf the tape is an emulator tape, no action is required since DDR does not support emulator tape.

INVALID USER EXITContact the system programmer to make sure that the NSLREPOS program is in the system. If it is, m surethat a valid return code (0, 4, 8, 12, 16, or 20) is being returned to DDR and that no programming errors existin NSLREPOS.

CATASTROPHIC ERRORThis may result when the application that had originally held an allocation for device dev either ends orissues a close against dev while DDR is processing the swap. If this is the case, then a SVC dump for aprogram check in DDR accompanies this message. Give this dump to the system programmer.

This may result when an I/O error occurs for the device being swapped to. In this case, no additionalmessages are issued (i.e., IOS000I) or LOGREC entries recorded to report this error as the DDR I/O driverbypasses error recovery procedure under certain conditions when handling I/O, such as rewind unload inpreparation for a swap. If the DDR swap was operator-initiated, reissue the command specifying a new TOdevice. If the DDR swap was system-initiated, the application holding an allocation for device dev is postedback with a permanent error.

This may also occur if a DISPLAY IOS, MIH or SETIOS or SET IOS=xx command is active at the time of theDDR swap. If the DDR swap was operator-initiated, reissue the SWAP command. If the DDR swap wassystem-initiated, the application holding an allocation for device dev is posted back with a permanent error.

INVALID DEVICEReenter the SWAP command using a valid device for the "FROM" device.


http://www.ibm.com/servers/resourcelink/svc00100.nsf/pages/zosInternetLibraryhttp://www.ibm.com/servers/resourcelink/svc00100.nsf/pages/zosInternetLibrary

CANCELED BY USERNo action is required.

JES3 ERRORIf the swap was initiated through a SWAP command, you may attempt to reenter the command. If, however,the swap was requested by the system as a result of a permanent error, the affected user has been postedwith a permanent error.

BY DEVICE SUPPORT MODULENo action is required.

ERROR ON RD BLKIDNo action is required.

ERROR ON RD BUFFERNo action is required.

GETMAIN FAILEDNo action is required.

PAGE FIX ERRORNo action is required.

FAILURE DURING LIBRARY PROCESSINGIf there is a tape or library hardware problem, contact hardware support.

READ ERROR IN LIBRARYIf there is a tape or library hardware problem, contact hardware support.

REPOSITIONING ERROR IN LIBRARYIf there is a tape or library hardware problem, contact hardware support.

EXIT I/O ERROR IN LIBRARYIf there is a tape or library hardware problem, contact hardware support.

SWITCH FAILED DUE TO I/O ERRORIf there is a hardware problem, contact hardware support.

NOT A VALID PPRC PAIRReenter the swap command, specifying 'FROM' and 'TO' devices that are the primary and secondary devicesin the same PPRC pair.

GETMAIN FAILED - SP245No action is required.

SWAP TERMINATED BY OPERATORNo action is required.

ERROR ON MEDIUM SENSE COMMANDNo action is required.

ERROR WRITING DATANo action is required.

ERROR ACQUIRING MODE CNTL INFORMATIONReenter the SWAP command. If the error continues to occur, contact your service representative.

ERROR SETTING MODE CNTL INFORMATIONNo action is required.

ERR ON SYNC CMD - DEV FORCED OFFLINENo action is required.

ERROR ON LOCATE CMDNo action is required.

CATASTROPHIC ERROR - RSN=xxThe reason code in xx specifies what failure occurred.01

A program check occurred during DDR execution. The recovery routine of DDR swap should have takenan SVC dump for this condition.

IGF messages 11

02A terminating condition occurred early in DDR swap processing.

03An internal error in DDR logging occurred.

04An I/O error occurred on the TO device making it not usable for swapping. For operator and system-initiated swaps, it is possible to select a new TO device to be used for the SWAP.

05An internal error occurred. The device type recognized by DDR swap was not a tape, DASD, or unit recorddevice type.

06An internal error in DDR device validation occurred.

07An internal error occurred. An attempt to pagefix a DDR module failed.

08A required resource could not be obtained. This condition will most likely occur when a DISPLAY IOS,SETIOS, or SET IOS=xx command is active at the time of the swap. For an operator swap, reissue theSWAP command. For a system-initiated swap, the application holding an allocation for device dev isposted back with a permanent error.

Unless otherwise noted, obtain a console dump which includes both the MASTER and IOS address spaces(IOSAS) and contact the IBM Support Center for dump assistance.

UCB SWAP FAILURE - RSN=xxFor a list of reason codes, see mapping macro IOSDSWAP in z/OS MVS Data Areas in the z/OS Internet library(www.ibm.com/servers/resourcelink/svc00100.nsf/pages/zosInternetLibrary). If IBM support is required,obtain a console dump which includes both the MASTER and IOS address spaces (IOSAS) and contact theIBM Support Center for dump assistance.

Source


Module

IGFDT2

Routing code

1,3,4,7,11

Descriptor code

4

IGF513I DEVICE dddd INVALID FOR SWAP - [text] [NAME=name CODE=code]

Explanation

The value of text is one of the following lines:

• MOUNT PENDING• UNIT REFERENCE INVALID• UNSUPPORTED USE• INCOMPATIBLE• NOT ALLOCATED• DEVICE TYPE INVALID


http://www.ibm.com/servers/resourcelink/svc00100.nsf/pages/zosInternetLibraryhttp://www.ibm.com/servers/resourcelink/svc00100.nsf/pages/zosInternetLibrary

• JES3 INCOMPATIBLE• JES3 DEVICE IS IN USE• JES3 DEVICE IS ONLINE• JES3 DEVICE IS OFFLINE• COULD NOT BE BROUGHT ONLINE• DYNAMIC/STATIC INCOMPATIBLE• VOLSER DOES NOT MATCH• MUST BE QUIESCED WITH IOACTION• DEVICE MUST BE OFFLINE• ACTIVE PAGING DATASET• MUST SWAP TO A 3490• MUST SWAP TO A 3590-1• MUST SWAP TO A 3590-E• MUST SWAP TO A 3590-H• MUST SWAP TO A 3590-J• MUST SWAP TO A 3590-1 IN 3490 MODE• MUST SWAP TO A 3590-E IN 3490 MODE• MUST SWAP TO A 3590-E OR 3590-H• MUST SWAP TO A WORM-CAPABLE 3592-J• MUST SWAP TO A 60GB-CAPABLE 3592-J• MUST SWAP TO A 3592-3E• MUST SWAP TO A 3592-J OR 3592-2• MUST SWAP TO A 3592-2 OR 3592-3E• MUST SWAP TO A 3592-3E OR 3592-4E• MUST SWAP TO A 3592-4E• ERROR ACQUIRING TAPE FORMAT INFO• PAGE FIX ERROR• UNSUPPORTED RECORD LENGTH• DEV LIB MISMATCH• NO DEV LIB INFO• BLOCKED BY HYPERSWAP• DEVICE DOES NOT SUPPORT SWAP TO SELF• DEVICE IS MARKED UNAVAILABLE

A device was specified for a swap either in the SWAP command or in response to message IGF500D or IGF509D.However, the device cannot be used for one of the reasons listed above.

This message can be issued in a multiline message, in which case name and code will be specified.

In the message text:dddd

The device specified for a swap.MOUNT PENDING

Dynamic device reconfiguration (DDR) found that the TO device has a mount outstanding for it. The devicecannot be used as an alternate for the FROM device because of a conflict with device allocation.

IGF messages 13

UNIT REFERENCE INVALIDA device was specified in response to message IGF500D or IGF509D or was entered as the TO device in aSWAP command; however, no corresponding device could be found in the list of devices defined at systemgeneration.

UNSUPPORTED USEA condition exists on device ddd that temporarily prevents a swap from taking place, although the indicateddevice is supported for a swap.

INCOMPATIBLEThe TO device specified in response to message IGF500D or IGF509D or in the original SWAP command wasnot compatible with the FROM device. The device selected as the TO device does not have the same featuresas the FROM device or is not in the same device class. This message also appears if an attempt is made toswap a shared direct access storage device (DASD) to an address other than itself.

NOT ALLOCATEDThe FROM tape ddd in the SWAP command is not allocated to any user.

DEVICE TYPE INVALIDDevice ddd is of a device type not supported by DDR for swaps.

JES3 INCOMPATIBLEThe TO device specified in response to message IGF500D or IGF509D or in the original SWAP command wasnot compatible with the FROM device from the JES3 point of view.

JES3 DEVICE IS IN USEThe TO device specified in response to message IGF500D or IGF509D or in the original SWAP command iscurrently in use from the JES3 point of view.

JES3 DEVICE IS ONLINEThe TO device specified in response to message IGF500D or IGF509D or in the original SWAP command iscurrently online from the JES3 point of view but should be offline.

JES3 DEVICE IS OFFLINEThe TO device specified in response to message IGF500D or IGF509D or in the original SWAP command iscurrently offline from the JES3 point of view but should be online.

COULD NOT BE BROUGHT ONLINEThe vary command processor failed the vary online request issued by DDR.

DYNAMIC/STATIC INCOMPATIBLEThe TO device does not have the same configuration status as the FROM device. Either one of the devices is astatic device and the other a dynamic device, or one device is static supporting dynamic and the other isstatic not supporting dynamic.

VOLSER DOES NOT MATCHThe TO device does not have the same volume serial as the FROM device.

MUST BE QUIESCED WITH IOACTIONThe FROM device is a shared DASD but the device was found not to be quiesced by the IOACTION command.

DEVICE MUST BE OFFLINEThe TO device is a permanent resident DASD but was found to be online.

ACTIVE PAGING DATASETThe TO device is a permanent resident DASD that contains an active paging data set.

MUST SWAP TO A 3490The operator attempted to swap a non-3490. This is an error. The operator must swap to a 3490.

MUST SWAP TO A 3590-1The operator attempted to swap to a drive other than a native 3590-1. This is an error. The operator mustswap to a native 3590-1.

MUST SWAP TO A 3590-EThe operator attempted to swap to a drive other than a 3590-E. This is an error. The operator must swap to a3590-E.


MUST SWAP TO A 3590-HThe operator attempted to swap to a drive other than a 3590-H. This is an error. The operator must swap to a3590-H.

MUST SWAP TO A 3592-JThe operator attempted to swap to a drive other than a 3592-J. This is an error. The operator must swap to a3592-J.

MUST SWAP TO A 3590-1 IN 3490 MODEThe operator attempted to swap to a drive other than a 3590-1 in 3490 mode. This is an error. The operatormust swap to a 3590-1 in 3490 mode.

MUST SWAP TO A 3590-E IN 3490 MODEThe operator attempted to swap to a drive other than a 3590-E in 3490 mode. This is an error. The operatormust swap to a 3590-E in 3490 mode.

MUST SWAP TO A 3590-E OR 3590-HThe operator attempted to swap to a drive other than a 3590-E or 3590-H. This is an error. The operatormust swap to a 3590-E or 3590-H.

MUST SWAP TO A 3590-HThe operator attempted to swap to a drive other than a 3590-H. This is an error. The operator must swap to a3590-H.

MUST SWAP TO A 3592-2The operator attempted to override the system and selects the wrong type. This is an error. The operatormust swap to a 3592-2.

MUST SWAP TO A WORM-CAPABLE 3592-JThe operator attempted to swap to a drive other than a WORM-CAPABLE 3592-J. This is an error. Theoperator must swap to a WORM-CAPABLE 3592-J.

MUST SWAP TO A 60GB-CAPABLE 3592-JThe operator attempted to swap to a drive other than a 60GB ECONOMY 3592-J. This is an error. Theoperator must swap to a 60GB ECONOMY 3592-J.

3592-3E DRIVE DETECTED BUT NOT ALL 3592-3E SUPPORT IS PRESENTSupport for the 3592 Model E06 was shipped as program temporary fixes (PTFs) on z/OS DFSMS V1R7 andlater releases. If these PTFs are not installed, DFSMSdfp issues this message.

System Programmer Response: Install the required maintenance.

MUST SWAP TO A 3592-4EThe operator attempted to swap to a drive other than a 3592-4E. This is an error. The operator must swap toa 3592-4E.

PAGE FIX ERRORDDR was unable to page fix storage to retrieve buffered data. The swap is ended.

UNSUPPORTED RECORD LENGTHDDR could not retrieve a buffered record because the length was greater than 64 KB. The swap is ended.

DEV LIB MISMATCHThe operator attempted to swap to a device that is outside the automated tape library. The swap must be toa device within the same library.

NO DEV LIB INFOThe device is an automated tape library and DDR was unable to obtain the library ID to ensure that the FROMand TO devices are in the same library. The swap is ended.

ERROR ACQUIRING TAPE FORMAT INFODDR was unable to obtain tape format information from the FROM device. The swap is ended.

BLOCKED BY HYPERSWAPDynamic device reconfiguration (DDR) has found that either the FROM or TO device is currently beingmonitored by hyperswap processing and is therefore ineligible for DDR swap processing.

IGF messages 15

DEVICE DOES NOT SUPPORT SWAP TO SELFThe operator attempted to swap back to the same drive address. This is an error. The operator must swap toa different drive address.

DEVICE IS MARKED UNAVAILABLEA device in the UNAVAILABLE state cannot be chosen as the swap TO device.

System action

The system rejects the command and continues processing.

Operator response

The response depends on the message text. Respond as follows for each of the message texts:MOUNT PENDING

For swaps initiated by a SWAP command, reenter the command after the mount request is satisfied if thedevice is the FROM device. If the device is the TO device either for swaps requested by the system or forthose initiated by a SWAP command, reenter another device or NO to the IGF509D message, which followsthis one.

UNIT REFERENCE INVALIDReenter a device number known to the system or NO to the IGF509D message, which follows this one. Youcan determine what devices are known to the system by using the DISPLAY U command.

UNSUPPORTED USEReenter the SWAP command using a supported device if ddd is the FROM device. Otherwise, reenter theaddress of a device supported by DDR to the IGF509D message, which follows this one, or enter NO.

DDR does not permit swaps for the following devices:

• Offline FROM devices• Devices under control of the online test executive program (OLTEP)• Integrated emulator tapes in original second-generation format (RECFM=U) coded on the device control

block (DCB)• Nonstandard label (NSL) tapes, if the user exit NSLREPOS is unavailable• Tape swaps in which the TO device is allocated• Unit record devices in ready status• A TO device about which outstanding messages that might require operator action exist

INCOMPATIBLEReply to message IGF509D, which follows this message, with a device compatible to the FROM device, orreply NO. Compatible devices follow.

Disk swaps supported:

• 3330 to 3330• 3330 mod 11 to 3330 mod 11• 3340 to 3340

Unit record swaps supported:

• 1403 to 1403• 1443 to 1443• 3211 to 3211• 3505 to 3505• 3525 to 3525

Tape swaps supported:

• 7-track to 7-track


• 9-track (single or dual density) to 9-track (single or dual density), provided that the density in use on thexxx unit is a valid density specification for the yyy unit.

If a 7-track tape drive is being used at 200 BPI, you must ensure that the TO device has 200 BPI feature.

Volumes on 3400 series tape drives can be moved only to other 3400 series drives. However, volumes on2400 series tape drives can be moved either to 2400 series drives or to 3400 series drives.

NOT ALLOCATEDBecause the tape is not allocated, you need not use DDR to move the tape.

DEVICE TYPE INVALIDReply to the IGF509D messages with the control unit address of one of the following devices:

• Tape: 3410, 3411, 3420 (all models)• Disk: 3330, 3330 model 11, 3340• Unit record: 1403, 1443, 3211, 3505, 3525

JES3 INCOMPATIBLEReply to message IGF509D, which follows this message, supplying a device compatible with the FROM devicefrom the JES3 point of view, or reply NO. For information on JES3 device compatibility, see z/OS JES3Initialization and Tuning Reference.

JES3 DEVICE IS IN USEReply to message IGF509D, which follows this message, supplying a device that is not in use from the JES3point of view, or reply NO. For information on JES3 device requirements for DDR swap, see z/OS JES3Initialization and Tuning Reference.

JES3 DEVICE IS ONLINEReply to message IGF509D, which follows this message, supplying a device that is offline from the JES3point of view, or reply NO. For information on JES3 device requirements for DDR swap, see z/OS JES3Initialization and Tuning Reference.

JES3 DEVICE IS OFFLINEReply to message IGF509D, which follows this message, supplying a device that is online from the JES3point of view, or reply NO. For information on JES3 device requirements for DDR swap, see z/OS JES3Initialization and Tuning Reference.

COULD NOT BE BROUGHT ONLINEEnter the address of a new TO device or NO in response to message IGF509D.

DYNAMIC/STATIC INCOMPATIBLEReply to message IGF509D, which follows this message, with a device that has the same configurationstatus as the FROM device. If the FROM device is dynamic, respond with a device defined as dynamic. If theFROM device is static supporting dynamic, respond with a device defined as static supporting dynamic. If theFROM device is static not supporting dynamic, respond with a device defined as static not supportingdynamic.

VOLSER DOES NOT MATCHReenter the SWAP command, selecting a TO device that is the secondary device for the peer-to-peer remotecopy (PPRC) pair to which the FROM device belongs.

MUST BE QUIESCED WITH IOACTIONIssue the IOACTION command to quiesce the FROM device, and reenter the SWAP command.

DEVICE MUST BE OFFLINEVary the TO device offline and reenter the SWAP command.

ACTIVE PAGING DATASETReenter the SWAP command, selecting a TO device that is the secondary device for the PPRC pair to whichthe FROM device belongs.

MUST SWAP TO A 3490Reenter the SWAP command, specifying a 3490.

MUST SWAP TO A 3590Reenter the swap command, specifying a 3590.

IGF messages 17

MUST SWAP TO A 3590-1 IN 3490 MODEReenter the SWAP command, specifying a 3590-1.

MUST SWAP TO A 3590-E IN 3490 MODEReenter the SWAP command, specifying a 3590-E.

MUST SWAP TO A 3590-E OR 3590-HReenter the SWAP command, specifying a 3590-E or 3590-H.

MUST SWAP TO A 3590-HReenter the SWAP command, specifying a 3590-H.

GETMAIN FAILEDReenter the SWAP command. DDR might be able to obtain storage on subsequent attempts.

PAGE FIX ERRORReenter the SWAP command.

UNSUPPORTED RECORD LENGTHNo action required. The swap is ended.

DEV LIB MISMATCHReenter the SWAP command, selecting a TO device that is within the same automated tape library.

NO DEV LIB INFOReenter the SWAP command. DDR might be able to obtain the library information on subsequent attempts. Ifthe error continues to occur, contact your service representative.

ERROR ACQUIRING TAPE FORMAT INFOReenter the SWAP command. If the error continues to occur, contact your service representative.

BLOCKED BY HYPERSWAPEnd hyperswap monitoring for both the FROM and TO devices and reissue the SWAP command.

DEVICE IS MARKED UNAVAILABLEVARY the device to the available state and then re-enter the SWAP command.

Source


Routing code

1,3,4,7,11

Descriptor code

4

IGF514I CAUTION: ENSURE THAT THERE IS NO HEAD OR DISK PACKINTERFERENCE

Explanation

The permanent I/O error occurring on a direct access storage device (in the previous message) with channel unitaddress xxx may be due to a defective disk drive or pack.

System action

The system continues operation. The SWAP request does not complete until the operator responds to thesucceeding reply message.

Operator response

The disk drive or pack may be defective. If so, moving the pack or installing a different pack on the same drivewill propagate the damage. Do not physically move the pack until both the pack and the drive have beeninspected. Damage is indicated by a strange noise prior to turning the drive off. Another indication of damage to


the device is a brown powder (dust) on disk surfaces or within the pack enclosure. Visually inspect the disksurfaces before removing the pack from the drive.

If after SWAP, an additional permanent I/O error occurs, or if there are additional indications of problems, do notswap the pack again.

System programmer response

Contact hardware support if there is any indication of damage.

Source


Module

IGFDV0

Routing code

1,4

Descriptor code

4

IGF515I SWAP FROM dev1 TO dev2 FAILED

Explanation

While swapping devices, dynamic device reconfiguration (DDR) encountered an error associated with either themount or dismount services. This message might be accompanied by other messages describing the error.

In the message text:dev1

The device number of the device being swapped from.dev2

The device number of the device being swapped to.

System action

The system abnormally ends the swap and issues message IGF512I.


See the accompanying messages for information about the cause of the swap failure.

Source

Dynamic device reconfiguration

Module

IGFDT2

Routing code

1,3,11

IGF messages 19

Descriptor code

4

IGF516I SWAP IN PROGRESS IN LIBRARY libname, NO ONLINE DEVICES CANBE FOUND

Explanation

In the environment, dynamic device reconfiguration (DDR) could not find any online devices to swap to.

In the message text:libname

Library name in which the swap is occurring.

System action

This message will be accompanied by messages IGF509I and IGF509D, which prompt the operator for a 'TO'device. DDR processing will then continue.

Operator response

Vary a device online in the named library, and then answer message IGF509D with the new 'TO' device.

Source


Module

IGFDV0

Routing code

1,3,11

Descriptor code

4

IGF517I DEVICE ACCEPTED, SWAP PROCESSING RESUMED

Explanation

A system-initiated swap in is in progress but no online devices were found. This message is issued when theoperator has responded to messages IGF516I, IGF509I, and IGF509D and entered a valid online device for theswap.

System action

processing continues normally.

Source


Module

IGFDV0


Routing code

1,3,11

Descriptor code

4

IGF518I WARNINGS ISSUED DURING LIBRARY DEMOUNT PROCESSING

Explanation

Warning messages were issued during the demount of the 'FROM' or 'TO' device. This message may beaccompanied by other messages describing these warnings.

System action

processing continues normally.

Source


Module

IGFDT2

Routing code

1,3,11

Descriptor code

4

IGF519I WARNINGS ISSUED DURING LIBRARY MOUNT PROCESSING

Explanation

Warning messages were issued during the mount of the 'TO' device. This message may be accompanied by othermessages describing these warnings.

System action

Processing continues normally.

Source


Module

IGFDT2

Routing code

1,3,11

Descriptor code

4

IGF messages 21

IGF520A VERIFICATION COMPLETE: REPLY 1 TERMINATE PAIR, AND SWAP | 2SWITCH PAIR, AND SWAP | 3 CONTINUE SWAP | 4 TERMINATE SWAP

Explanation

The 'FROM' and 'TO' DASD devices were verified as a PPRC pair with the 'FROM' device being the source and the'TO' device being the target. The operator is provided with three options for continuing processing or the optionto terminate processing.

System action

Depends on the option selected by the operator.

• Reply 1: The PPRC pair is terminated and processing continues.• Reply 2: The PPRC pair is terminated. A PPRC pair is then reestablished in the opposite direction, the 'TO'

device becomes the source device and the 'FROM' device becomes the target device. This PPRC pair is thensuspended with change recording enabled, and processing is allowed to continue.

• Reply 3: Processing continues with no action taken on the PPRC pair.• Reply 4: Processing is terminated.

Operator response

The operator must choose one of the four options.

Source


Module

IECLDDRD

IGF521A NO PATH IN OPPOSITE DIRECTION: REPLY 1 TO CONTINUE SWAP | 2TRY AGAIN | 3 TERMINATE SWAP

Explanation

This message is in response to option 2 of IFG520A when an ESCON logical path does not exist from the 'TO'device to the 'FROM' device. This message is issued prior to any action being taken that would change the statusof the PPRC pair.

System action


• Reply 1: The PPRC pair is terminated and processing continues.• Reply 2: The PPRC pair is terminated. A PPRC pair is then reestablished in the opposite direction, the 'TO'

device becomes the source device and the 'FROM' device becomes the target device. This PPRC pair is thensuspended with change recording enabled, and processing is allowed to continue.

Operator response

The operator must establish an ESCON logical path from the 'TO' device to the 'FROM' device before selectingoption 2. If a path is not established, then only option 1 or option 3 may be used.

Source



Module

IECLDDRD

IGF522A UNABLE TO SWITCH, FROM DEVICE IS SMALLER THAN TO DEVICE:REPLY 1 TO CONTINUE SWAP | 2 TO TERMINATE SWAP

Explanation

This message is in response to option 2 of IFG520A when the 'TO' device has a greater physical capacity thanthe 'FROM' device and therefore cannot establish a PPRC pair between the 'TO' device and the 'FROM' device.This is a limitation of the hardware. This message is issued prior to any action being taken that would change thestate of the PPRC pair.

System action


• Reply 1: The PPRC pair is terminated and processing continues.• Reply 2: Processing is terminated.

Operator response

The operator may continue processing or terminate processing.

Source


Module

IECLDDRD

IGF523A WARNING THE DEVICES SELECTED ARE NOT A VALID PPRC PAIRREPLY 1 TO CONTINUE SWAP | 2 TERMINATE SWAP

Explanation

The 'FROM' device and 'TO' device are not a valid PPRC pair. This means that there is no guarantee that data onthe 'TO' device is a mirror copy of data on the 'FROM' device.

System action


• Reply 1: Processing continues.• Reply 2: Processing is terminated.

Operator response

The operator should use caution when using option 1 since there is no guarantee that the 'TO' device is a mirrorcopy of the 'FROM' device.

Source


Module

IECLDDRD

IGF912W EXTENDED STORAGE FAILURE, RE-IPL THE SYSTEM

IGF messages 23

Explanation

A hardware error exists in expanded (extended) storage.

System action

The system enters a wait state.

Operator response

See the operator response for the accompanying wait state.

Source

Machine check handler (MCH)

Module

IGFPMAIN

Routing code

2,10

Descriptor code

4

IGF913W MACHINE CHECK HANDLER INITIALIZATION FAILED -- text

Explanation

Machine check handler initialization failed during the nucleus initialization program (NIP).

In the message text:REQUIRED DATA AREAS COULD NOT BE ALLOCATED

The system could not allocate the loaded request block (LRB) and processor work area (PWA) data areas formachine check handler.

CONTROL REGISTERS COULD NOT BE INITIALIZEDThe system could not initialize the required control registers during machine check handler initialization.

System action

The system loads nonrestartable wait state X'0E8' with a reason code of X'81xxx' or X'82xx'.

Operator response

See the operator response for wait state X'81xxx' or X'82xx'.


See the system programmer response for wait state X'81xxx' or X'82xx'.

Source


Module

IGFRIM00


Routing code

1,10

Descriptor code

1

IGF931E nnn {SR | DG} EVENTS HAVE OCCURRED ON CPU x, STATUS={ QUIET |RECORD}

Explanation

This message shows the number and types of system recovery or degradation machine check interruptions thatoccurred on a processor, and whether future interruptions will be recorded.

In the message text:nnn

The number of machine check interruptions.SR

Indicates a system recovery type of machine check interruption.DG

Indicates a degradation type of machine check interruption.x

The processor identifier.QUIET

Further machine check interruptions of the indicated type will not be recorded.RECORD

Further machine check interruptions of the indicated type will be recorded.

System action

If QUIET appears in the message, the system stopped recording machine check interruptions and continuedprocessing. If RECORD appears in the message, the system continues recording machine check interruptions inthe logrec data set.

Operator response

Contact hardware support if the machine check interruptions are excessive. Provide the logrec data set errorrecords.

Source


Module

IGFPMTHA

Routing code

2,10

Descriptor code

11

IGF953I EVENT-type {CPU=x} MODE-{QUIET | RECORD=nnn |RECORD=ALL} CNT=ccc[INTERVAL=iiiii][REPORT=rrr]

IGF messages 25

Explanation

In response to the MODE STATUS command, this message displays the hardware error recovery status for eacherror type for each online processor.

In the message text:type

The type of event, which is one of the following:SR

System recoveryDG

DegradationPD

Instruction processing damageSD

System damageIV

Machine check interrupt indicates an incorrect PSW or registerTC

Time-of-day clock damagePT

Processor timer damageCC

Clock comparator damagePS

Primary synch damageAD

External time reference (ETR) attachment damageSC

ETR synch checkSL

ETR switch-to-local synchSS

STP Sync CheckIC

Island ConditionCO

CTN Configuration ChangeCS

Clock Source ErrorCPU=x

The address of the processor on which the event occurred.QUIET

Further machine check interruptions of this type will not be recorded.RECORD=rrr

The system will record hardware errors of this type until the number of errors is rrr. When the number oferrors equals rrr, the system does one of the following:SR and DG

The system issues message IGF931E and places the indicated processor in QUIET mode for therespective event.


PD, SD, IV, TC, PT, CC, PS, AD, and SLIf the time interval has not expired, the system invokes alternate CPU recovery (ACR) to take theindicated processor offline.

SCThe system switches to local mode.

RECORD=ALLThe system will record all hardware errors of this type. For SR and DG events, the system issues messageIGF931E whenever the count reaches a multiple of rrr.

CNT=cccThe number of events that occurred since the current timing interval began. For SR and DG events, thecurrent counting interval began at the last IPL or the last time the operator entered the mode command.ForPD, SD, IV, TC, PT, CC, PS, AD, SL and SC events, the counting interval is controlled by the value of INTERVAL.

INTERVAL=iiiiiThe length of time (in seconds) comprising a timing interval elapsed for PD, SD, IV, TC, PT, CC, PS, AD, SL, orSC events.

If the counting interval elapses before the specified number of events occurs, the system resets the elapsedtime to 0. If a hardware error occurs, the event count is set to 1.

REPORT=rrrThe number of SR or DG hardware errors which can occur before the operator is notified. Whenever thecount for the SR or DG event reaches a multiple of rrr, the system issues message IGF931E.

System action


Source


Module

IGF2603D

Routing code

2

Descriptor code

5

IGF955I MODE {QUIET | RECORD=ALL | RECORD=nnn} FOR typeEVENTS ON {CPU=x | CPU=ALL}{INTERVAL=iiiii SECS}{REPORT=rrr}

Explanation

In response to a MODE command, the machine check handler changed the mode of the indicated event class onthe specified processor to the indicated state:QUIET

The system will not record hardware failures of the specified type. QUIET applies only to SR and DG events.RECORD=rrr

The system will record hardware errors of this type until the number of errors is rrr. When the number oferrors equals rrr, the system does one of the following:SR and DG

The system issues message IGF931E and places the indicated processor in QUIET mode for therespective event.

IGF messages 27

PD, SD, IV, TC, PT, CC, PS, AD, and SLIf the time interval has not expired, the system invokes alternate CPU recovery (ACR) to take theindicated processor offline.

SCThe system switches to local mode.

RECORD=ALLThe system will record all hardware errors of this type. For SR and DG events, the system issues messageIGF931E whenever the count reaches a multiple of rrr.

typeThe type of event, which is one of the following:SR

System recoveryDG

DegradationPD

Instruction processing damageSD

System damageIV

Machine check interrupt indicates an incorrect PSW or registerTC

Time-of-day clock damagePT

Processor timer damageCC

Clock comparator damagePS

Primary synch damageAD

External time reference (ETR) attachment damageSC

ETR synch checkSL

ETR switch-to-local synchEVENTS ON CPU = x

The system is monitoring the indicated event on processor x.EVENTS ON CPU = ALL

The system is monitoring the indicated event on all processors.INTERVAL=iiiii

The length of time (in seconds) comprising a timing interval elapsed for PD, SD, IV, TC, PT, CC, PS, AD, SL, orSC events.

If the counting interval elapses before the specified number of events occurs, the system resets the elapsedtime to 0. If a hardware error occurs, the event count is set to 1.

REPORT=rrrThe number of SR or DG hardware errors which can occur before the operator is notified. Whenever thecount for the SR or DG event reaches a multiple of rrr, the system issues message IGF931E.

System action



Source


Module

IGF2603D

Routing code

2

Descriptor code

5

IGF957A MANUALLY STOP PROCESSOR(x) SO THAT ACR CAN PROCEED. REPLY UWHEN THE STOP HAS BEEN PERFORMED

Explanation

A processor issued a malfunction alert, but the system was unable to stop the processor. The operator must stopthe processor manually so alternate CPU recovery (ACR) can remove the processor from the system.

System action

The system waits for the operator to reply.

Operator response

• If you stop processor x, reply U to the message.• If you are unable to stop processor x, do not reply U. Retain the error records from the logrec data set and

contact hardware support.

Source


Module

IGFPXMFA

Routing code

1, Note 12

Descriptor code

2

IGF958I MODE COMMAND REJECTED, prm PARAMETER INVALID

Explanation

The indicated parameter is not valid for the MODE command as specified.

System action

Processing continues. The system rejects the MODE command.

IGF messages 29

Operator response

Enter the MODE command again.

Source


Module

IGF2603D

Routing code

2

Descriptor code

5

IGF959I MODE COMMAND REJECTED, CPU SPECIFIED IS {INVALID|OFFLINE}

Explanation

The MODE command was rejected. Either the processor specified was not valid, or the processor specified wasoffline.

System action

Processing continues; the MODE command is rejected and has no effect.

Operator response

Reenter the MODE command. Be sure that the processor specified is online, that the processor number specifiedis 0 through F, and that the processor supports the parameter specified. See z/OS MVS System Commands todetermine which processor(s) support the specified parameter.

Source


Module

IGF2603D

Routing code

3

Descriptor code

5

IGF960I MODE COMMAND REJECTED. PROCVIEW CORE IS IN EFFECT.

Explanation

The MODE command for this type of machine check was rejected because machine check thresholding is notsupported with PROCVIEW CORE and this type of machine check. The MODE command for this type of machinecheck only accepts RECORD=ALL,CPU=ALL and cannot be changed. For more information on the types ofmachine checks that no longer support machine check thresholding with PROCVIEW CORE, see the MODEcommand in z/OS MVS System Commands.


System action

Processing continues; the system rejects the MODE command.

Operator response

None.

Source


Module

IGF2603D

Descriptor code

5

IGF970E VF x NOW OFFLINE. UNRECOVERABLE ERROR DETECTED

Explanation

The machine check handler detected a failure in a vector facility (VF).

In the message text:x

The VF identifier.

System action

The system takes the failing VF offline, and then continues processing. The system ends any vector work thatwas running at the time of the failure.

• If other VFs are in the configuration, the system will dispatch the VF work on a processor with an available VF.• If other VFs are not available, the system cannot run the VF work. The system then issues message IRA700I.

Operator response

Enter the DISPLAY M=CPU command to find out if the configuration has other VFs for existing jobs. If the systemissues message IRA700I, see its operator response.

Source


Module

IGFPMHCA

Routing code

2,10

Descriptor code

11

IGF messages 31

Chapter 2. IGGHC messages

IGGHC103I CHECK(IBMCATALOG,CATALOG_IMBED_REPLICATE) ran successfullyand found no exceptions.

Explanation

The check was successful and found no catalogs defined with the IMBED attributes, REPLICATE attributes, orboth.

System action

The system continues processing.

Source

DFSMS Catalog

Module

IGG0CLHY

IGGHC104E The health check has detected one or more catalogs defined with theIMBED and/or REPLICATE attributes.

Explanation

CHECK(IBMCATALOG,CATALOG_IMBED_REPLICATE) found one or more catalogs defined with the IMBEDattributes, REPLICATE attributes, or both. The IMBED and REPLICATE attributes were intended as performanceimprovements but have proven to be otherwise. They have proven to waste DASD space and degradeperformance. They have been obsoleted by the newer, cached DASD devices. In some cases, unplanned outageshave occurred. No supported release of z/OS allows you to define a user catalog or master catalog with eitherthe IMBED or REPLICATE attributes. IBM intends to drop support for these attributes in the future.AVAILABILITY

Column reports the status of the catalog.YES

Catalog was processed by the check.NO

Catalog was not available for processing either because the volume was offline or the volume wasreinitialized. Attribute information could not be returned.

ERRORCSI reported that the catalog entry was in error. Attribute information could not be returned. Running aDIAGNOSE on the catalog could help diagnose the problem. For more information about the DIAGNOSEcommand, see z/OS DFSMS Access Method Services Commands.

System action


Operator response

Report this message to the System Programmer.

© Copyright IBM Corp. 1988, 2017 33


Perform EXPORT/IMPORT on the affected catalogs reported by message IGGHC106I to remove the IMBED andREPLICATE attributes. For more information about EXPORT/IMPORT of a catalog, see "Backing up andRecovering Catalogs" in z/OS DFSMS Managing Catalogs.

Problem determination

See IGGHC106I in the message buffer that identifies the catalogs defined with the obsolete attributes.

Source

DFSMS Catalog

Routing code

See Note 35.

Descriptor code

12 is the default set by this check. See Note 1.

Reference Documentation

"Backing up and Recovering Catalogs" in z/OS DFSMS Managing Catalogs.

IGGHC106I Following catalog(s) were inspected by the health check. CATALOGNAME ATTRIBUTE COMPONENT AVAILABILITYcatname attribute component status

Explanation

In the message text:catname

Name of the catalog defined with the obsolete attributeattribute

Obsolete attribute catalog is defined with (IMBED or REPLICATE)component

The name of the component of the catalog (Data/Index)availability

Whether the catalog is available for processing or not because the volume was offline, or was reinitialized inwhich case there is an orphan UCON in the master catalog.

Exception message IGGHC104E follows in the message buffer that describes the error condition and steps toresolve the exceptions.

System action



Resolve the exception reported for each catalog listed in the report.

Source

DFSMS Catalog


Module

IGG0CLHY


See IGGHC104E.

IGGHC107I CSI has encountered an error in its processing while attempting toreturn data from the Catalog Address Space. Check message HZS1002Efor diagnostic information. The check is disabled.

Explanation

CHECK(IBMCATALOG,CATALOG_IMBED_REPLICATE) encountered an error in the processing of CSI.

This message provides additional information for the CSI error that follows HZS1002E.

System action

The check does not run.

Operator response

Report this message to the system programmer.


Check message HZS1002E for diagnostic information. The first 4 bytes contain the CSI return code, and the next4 bytes contain the CSI reason code. For an explanation on the return and reason codes from CSI, see ‘ReturnCodes for General Purpose Register 15’ in Appendix C of z/OS DFSMS Managing Catalogs.


Check the diagnostic information returned to diagnose the error.

Source

DFSMS Catalog

Module

IGG0CLHY


Appendix C of z/OS DFSMS Managing Catalogs.

IGGHC108I No user catalog connector entries were found in the master catalog.

Explanation

CHECK(IBMCATALOG,CATALOG_IMBED_REPLICATE) found no user catalogs in the master catalog.

System action


Source

DFSMS Catalog

IGGHC messages 35

Module

IGG0CLHY

IGGHC109I IMBED/REPLICATE Health Check Summary Report:A total of TOTCAT catalogs were processed by the Health Check.TOTSUC catalogs did not have either IMBED or REPLICATE attributes on them.TOTECXEP catalogs were not processed by the Health Check either because the catalog volume was offline or the catalog entry was in error.TOTERR catalogs were detected with either IMBD and/or REPLICATE attributes on them.

Explanation

CHECK(IBMCATALOG,CATALOG_IMBED_REPLICATE) summary report describes the findings of the check.

System action


Source

DFSMS Catalog

Module

IGG0CLHY

IGGHC110I CHECK(IBMCATALOG,CATALOG_RNLS) ran successfully and found noexceptions.

Explanation

The configuration of resources SYSIGGV2, SYSZVVDS and SYSVTOC conforms to IBM recommendations. IBMrecommends that ALL reserves be converted unless you are sharing DASD outside the sysplex. These resourcesshould be included on the GRS conversion list (CON RNL), and none should be found on the GRS inclusion list(INCL RNL) or the GRS exclusion list (EXCL RNL).

System action


Operator response

N/A


N/A


N/A

Source

DFSMS VSAM RLS


Module

IGG0CLHR

IGGHC111E CHECK(IBMCATALOG,CATALOG_RNLS) found that the Catalog/DADSMresources do not conform to IBM recommendations.

Explanation

IBM now recommends that ALL reserves be converted. Resources SYSIGGV2, SYSZVVDS and SYSVTOC shouldall be listed on the GRS conversion list

Documents

Version 2 Release 3 z/OS - IBM€¦ · 24/06/2019 · ROUTCDE and DESC keyword parameters on WTO and WTOR macros, which are the primary methods that programs use to issue messages