IBM Tivoli Event Pump for z/os Version Message Reference GC

Transcription

1 IBM Tivoli Event Pump for z/os Version Message Reference GC

2

3 IBM Tivoli Event Pump for z/os Version Message Reference GC

4 Note Before using this information and the product it supports, read the information in Notices on page 127. This edition applies to Version of IBM Tivoli Event Pump for z/os (product number 5698-B34) and to all subsequent versions, releases, and modifications until otherwise indicated in new editions. This edition replaces GC Copyright IBM Corporation 2008, US Government Users Restricted Rights Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.

5 Contents About this publication v Intended audience v Publications v IBM Tivoli Event Pump for z/os library.... v Related publications v Accessing terminology online v Accessing publications online vi Ordering publications vi Accessibility vi Tivoli technical training vi Tivoli user groups vii Support information vii Conventions used in this publication vii Typeface conventions vii Operating system-dependent variables and paths viii Chapter 1. GPZ prefix messages Chapter 2. GTM prefix messages Notices Trademarks Copyright IBM Corp. 2008, 2011 iii

6 iv Message Reference

7 About this publication Intended audience Publications IBM Tivoli Event Pump for z/os is an enterprise management product that monitors the z/os data processing resources in an enterprise. You can use it to monitor the z/os systems, subsystems, applications, and other resources that are critical to your business. This publication, the IBM Tivoli Event Pump for z/os Message Reference, describes the messages for Event Pump for z/os. This publication is for system programmers, system administrators, network operators, and others who need message information for Event Pump. This section lists publications in the IBM Tivoli Event Pump for z/os library and related documents. It also describes how to access Tivoli publications online and how to order Tivoli publications. IBM Tivoli Event Pump for z/os library This following documents are in the IBM Tivoli Event Pump for z/os library: v v v v v v v Command Reference, SC , describes the commands for Event Pump for z/os. Configuration Reference, SC , describes the configuration statements for Event Pump for z/os. Event Reference, SC , lists the events (exceptions and messages) that are integrated with Event Pump for z/os. Installation and Configuration Guide, SC , describes how to install and configure Event Pump for z/os. Message Reference, GC , describes the messages for Event Pump for z/os Troubleshooting Guide, GC , provides information for use in diagnosing and solving problems that occur in Event Pump for z/os. Program Directory for IBM Tivoli Event Pump for z/os, GI , contains information about the material and procedures that are associated with installing Event Pump for z/os. Related publications For information about the IBM Tivoli Business Service Manager product, link to the product information center from wikis/display/tivolidoccentral/tivoli+business+service+manager. For information about the IBM Tivoli Netcool/OMNIbus product, link to the product information center from display/tivolidoccentral/omnibus. Accessing terminology online The IBM Terminology website consolidates the terminology from IBM product libraries in one convenient location. You can access the Terminology website at Copyright IBM Corp. 2008, 2011 v

8 Accessibility The following terms are used in this library: AOPxxLOG For the AOPxxLOG system log in the 2-address-space environment or the AOPLOG system log in the 3-address-space environment. AOPxxLOG is either AOPEDLOG (event distributor log) or AOPSCLOG (source collector log). AOPLOG For the AOPxxLOG system log in the 2-address-space environment or the AOPLOG system log in the 3-address-space environment. AOPxxLOG is either AOPEDLOG (event distributor log) or AOPSCLOG (source collector log). Accessing publications online IBM posts publications for this and all other Tivoli products, as they become available and whenever they are updated, to the Tivoli Documentation Central website at Note: If you print PDF documents on other than letter-sized paper, set the option in the File Print window that allows Adobe Reader to print letter-sized pages on your local paper. Ordering publications You can order many Tivoli publications online at Tivoli technical training You can also order by telephone by calling one of these numbers: v In the United States: v In Canada: In other countries, contact your software account representative to order Tivoli publications. To locate the telephone number of your local representative, perform the following steps: 1. Go to 2. Select your country from the list and click Go. 3. Click About this site in the main panel to see an information page that includes the telephone number of your local representative. Accessibility features help users with a physical disability, such as restricted mobility or limited vision, to use software products successfully. Event Pump for z/os has no user interface or user interactions except through the interfaces of other products. For information about accessibility features for those products, see the applicable product information. Visit the IBM Accessibility Center at accessibility/ for more information about IBM's commitment to accessibility. For Tivoli technical training information, refer to the following IBM Tivoli Education website at vi Message Reference

9 Tivoli user groups Support information Tivoli user groups are independent, user-run membership organizations that provide Tivoli users with information to assist them in the implementation of Tivoli Software solutions. Through these groups, members can share information and learn from the knowledge and experience of other Tivoli users. Access the Tivoli Users Group at If you have a problem with your IBM software, you want to resolve it quickly. IBM provides the following ways for you to obtain the support you need: Online Access the Tivoli Software Support site at sysmgmt/products/support/index.html?ibmprd=tivman. Access the IBM Support Portal at IBM Support Assistant IBM Support Assistant is a free local software serviceability workbench that you can use to resolve questions and problems with IBM software products. Support Assistant provides quick access to support-related information and serviceability tools for problem determination. To install the Support Assistant software, go to support/isa/. After you install Support Assistant, you can install the IBM Tivoli Event Pump for z/os add-on. In Support Assistant, click Update > Find new. In the Find New Product Add-ons window, click Tivoli and then find and install the IBM Tivoli Event Pump for z/os add-on. Troubleshooting Guide For more information about resolving problems, see the Event Pump for z/os Troubleshooting Guide. Conventions used in this publication Typeface conventions This publication uses the following typeface conventions: Bold Italic v v v v v Lowercase commands and mixed case commands that are otherwise difficult to distinguish from surrounding text Interface controls (check boxes, push buttons, radio buttons, spin buttons, fields, folders, icons, list boxes, items inside list boxes, multicolumn lists, containers, menu choices, menu s, tabs, property sheets), labels (such as Tip:, and Operating system considerations:) Keywords and parameters in text Citations (examples: titles of publications, diskettes, and CDs Words defined in text (example: a nonswitched line is called a point-to-point line) About this publication vii

10 v Emphasis of words and letters (words as words example: "Use the word that to introduce a restrictive clause."; letters as letters example: "The LUN address must start with the letter L.") v New terms in text (except in a definition list): a view is a frame in a workspace that contains data. v Variables and values you must provide. Monospace v Examples and code examples v File s, directory s, and path s v Message text and prompts addressed to the user v Text that the user must type v Values for arguments or command options Operating system-dependent variables and paths This publication uses the UNIX convention for specifying environment variables and for directory notation. When using the Windows command line, replace $variable with %variable% for environment variables and replace each forward slash (/) with a backslash (\) in directory paths. The s of environment variables are not always the same in the Windows and UNIX environments. For example, %TEMP% in Windows environments is equivalent to $TMPDIR in UNIX environments. Note: If you are using the bash shell on a Windows system, you can use the UNIX conventions. viii Message Reference

11 Chapter 1. GPZ prefix messages The GPZ prefix messages are issued by the components that make up the services on a z/os mainframe systems. These messages include the source collector, event distributor, and data space. Some of the messages are issued from other address spaces that use the components. GPZ0000W NO num MESSAGE ENTRY FOUND FOR prefix WITH PARMS parms The message identified with message number num and message prefix prefix is not in the GPZMSG message file. The message used the parameters passed in parms. num prefix parms continues. The 4-digit message number The 3-character message prefix The additional parameters that are used to form the message The message is ignored and processing Verify that the data set associated with GPZMSG DD has an entry point for the indicated message. Otherwise, contact IBM Software GPZ0204E is required. GPZ0320W USRMASK KEYWORD REQUIRED A keyword for the USRMASK statement UNABLE TO LOCATE INTERVAL SETTINGS FOR MAINVIEW SYSPROG SAMPLES The initialization routine for BMC MainView SYSPROG services was unable to locate the BMC MainView SYSPROG address space. Processing stops. Check that the job assigned to the JOBNAME= keyword of the registration entry is the correct job for the BMC MainView SYSPROG services address space. If it is correct, unregister and register the BMC MainView for z/os monitoring. The temporary DD data set was unable to be allocated for the BMC MainView SYSPROG Services PARMLIB DD data set. dd The of the temporary DD data set The return code Processing stops. Support with the return code from the message. GPZ0322E ERROR READING MAINVIEW SAMPLE MEMBER member_ FROM dd Event Pump cannot read or locate the PWSCPMxx member from the PARMLIB data set from the BMC MainView SYSPROG Service address space. member_ The of the PWSCPMxx member dd The DD A default of 60 seconds is used for all of the BMC MainView SYSPROG samples. GPZ0323I UNABLE TO DEALLOCATE DD dd RC= The temporary DD data set is not deallocated for the BMC MainView SYSPROG Services PARMLIB DD data set. dd The of the temporary DD data set The return code GPZ0321E UNABLE TO ALLOCATE DD dd RC= Copyright IBM Corp. 2008,

12 GPZ0330W DATASET DSN=ds VOL=volume FAILED READ-ONLY CHECK RC= The source collector is not authorized for READ access to DB2 libraries in the RACF product. ds volume The data set The volume The RACF return code Authorize the source collector for READ access to DB2 libraries in RACF. Restart the source collector. GPZ0337E ROUTINE routine_ ENCOUNTERED UNEXPECTED RETURN CODE FROM subroutine_, RC= The routine in the message text attempted to call the subroutine_ and received an unexpected return code. routine_ The of the routine subroutine_ The of the subroutine Return codes 0 The routine completed successfully 4 The routine does not fully support this release of the DB2 program. Only minimal information was returned. 8 An error occurred when creating some of the REXX variables. 12 No parameters were provided. 16 The target DB2 program was not found. If you cannot resolve the problem, contact IBM Software GPZ0394E DSIGET FAILURE A routine received a return code other than 0 from the DSIGET macro. The of the routine Issues a secondary message. The REXX program that called the routine issues another message. Complete the actions that are recommended for that message GPZ0395E THE DB2 SUBSYSTEM NAME MUST BE 1 TO 4 CHARACTERS LONG The subsystem passed to the GPZBFIND program was not 1-4characters in length. Issues a secondary message. The REXX program that called the assembler routine issues another message. Complete the actions that are recommended for that message. GPZ0396E CONNECT TO DB2 SUBSYSTEM FAILED. RETURN CODES reason_code The GPZBFIND program did not connect to the DB2 subsystem. The DB2 subsystem The return code from the DB2 interface that is called by the GPZBIFIC program The reason code from the DB2 interface that is called by the GPZBIFIC program Issues a secondary message. The REXX program that called the assembler routine issues another message. Complete the actions that are recommended for that message. GPZ0397E CALL TO DB2 DSNWLI FAILED. DB2 RETURN CODES reason_code The GPZBFIND program did not call the DSNWLI link-edit step. The return code from the DB2 interface that is called by the GPZBIFIC program The reason code from the DB2 interface that is called by the GPZBIFIC program Issues a secondary message. Probable configuration error. See the DB2 library for an explanation of the return code and reason code; the return code and reason code indicate which configuration step was unsuccessful. 2 Message Reference

13 GPZ0398E CALL TO DB2 DSNWLI FAILED. DB2 RETURN CODES reason_code The program did not call the DB2 interface that is called by the GPZBIFIC program. The return code from the DB2 interface that is called by the GPZBIFIC program The reason code from the DB2 interface that is called by the GPZBIFIC program Issues a secondary message. The REXX program that called the routine issues another message. Complete the actions that are recommended for that message. GPZ0402I debug_text This message is issued in DEBUG mode to display diagnostic internal data and is for use only by IBM Software GPZ0451I COMPLETED WITH RETURN CODE called_mod call_mod_rc subsystem This message is issued to indicate whether the program completed successfully or unsuccessfully with a return code value of. It might also indicate a called subsidiary module, the return code from that module, and the of a subsystem. The program, which might include additional identification parameters in parentheses The return code from the program called_mod The module that is called from the program call_mod_rc The return code from the module subsystem The subsystem If the return code is not 0, contact IBM Software GPZ0580E GPZMSG FAILED WITH RETURN CODE ACTION action_code OBJECT TYPE object_type SUBSYSTEM DB2_subsys_ An internal API failed to complete. The return code from the GPZMSG program action_code The action code that was defined within the message object_type The type of resource to which the message was being sent SUBSYSTEM The DB2 subsystem that owns the resource This message indicates an internal error. GPZ0582I GPZBINIT COMPLETED WITH RETURN CODE Initialization of DB2 instrumentation for the Event Pump completed. The return code If the return code is not 0, examine the log that precedes this message for more detailed error messages and respond to them. GPZ0589W msgid FORMAT OF MAINVIEW MESSAGE msgid NOT VALID FOR IBM TIVOLI EVENT PUMP. An unexpected message was received. The unique identifier of the message The message is not processed. This message indicates an internal error. GPZ0606E subsystem DISCOVERY ABANDONED, CUSTOMIZATION ERRORS FOUND The d program determined that the nominated DB2 subsystem cannot be discovered due to errors that are related to Event Pump or DB2 customization. Chapter 1. GPZ prefix messages 3

14 The program that issued the message subsystem The program that issued the message processed The of the subsystem being See the Event Pump for z/os Installation and Configuration Guide for more information. Run the DB2 IVP program for the nominated DB2 subsystem and correct any errors. The DB2 subsystem is discovered at the next subsystem or when the source collector is started again. GPZ0607I REDISCOVERY FOR object ROUTED TO domain The d program determined that the nominated DB2 subsystem or Data Sharing Group is monitored by another domain, which is responsible for processing the discovery. object domain The program that issued the message The SSNAME literal for the DB2 subsystem or the DSGNAME literal for the DB2 data-sharing group The of the DB2 subsystem or Data Sharing group The of the Event Pump domain that performs the discovery The discovery continues on the nominated domain. No response is necessary unless the discovery does not complete successfully. In that case, examine the log for more information. GPZ0608E MONITORING DOMAIN FOR object IS NOT KNOWN The d program did not determine the domain that performs the discovery of the nominated Data Sharing Group (DSG). object The program that issued the message The literal SUBSYSTEM or DSG The of the DB2 subsystem or DSG The discovery is bypassed. This message indicates an internal error. GPZ0609I status DISCOVERY OF class OBJECTS The d program either started or finished the process of discovering the d class of resources. status class GPZ0620W The program that issued the message The status, either STARTED or FINISHED The of the class of resources The discovery process continues. - NO DB2 SUBSYSTEMS CURRENTLY ACTIVE FOR DSG An attempt was made to issue a DB2 command to a Data Sharing Group, but there were no active members available to process the command. The program that detected the situation The DB2 Data Sharing Group The program ends without issuing the requested command. Ensure that at least one DB2 subsystem in the Data Sharing Group is active and issue the command again. If the command was issued through the GUI from a DB2 subsystem resource instead of a Data Sharing Group resource, might be null. This situation occurs if the host did not monitor members of the Data Sharing Group. The subsystem or subsystems might be inactive, or they might be active but excluded from monitoring. GPZ0621E an event. CALL TO GPZEVENT FROM FAILED WITH RETURN CODE= ACTION=action_code OBJECT TYPE=object_type SUBSYSTEM= The GPZEVENT program did not send The program that detected the situation The return code from the GPZEVENT program action_code The action code that was defined within the event object_type The type of resource to which the event was being sent The DB2 subsystem that owns the resource 4 Message Reference

15 The program ends without sending the event. Identify the host event to be built, and report the problem to IBM Software GPZ0622E an event. CALL TO GPZEVENT FROM FAILED WITH RETURN CODE = ACTION = action_code OBJECT_TYPE = object_type DSG NAME = The GPZEVENT program did not send The program that detected the situation The return code from the GPZEVENT program action_code The action code that was defined within the event object_type The type of resource to which the event was being sent event. The DB2 subsystem that owns the resource The program ends without sending the Identify the host event to be built, and report the problem to IBM Software GPZ0623W : MESSAGE message_id FROM IGNORED. MESSAGE NOT VALID FOR A STAND-ALONE DB2 SUBSYSTEM A message related to a group buffer pool was issued from a DB2 subsystem. Event Pump considers this subsystem to be a stand-alone subsystem and does not participate in a data sharing group. The program that issued the message message_id The DB2 message being processed The of the DB2 subsystem that issued the message The DB2 message is not processed. If the subject DB2 subsystem is part of a data sharing group, it was incorrectly identified as a stand-alone subsystem. Report the problem to IBM Software GPZ0624E : IRLM CGLOBAL NOT FOUND FOR SUBSYSTEM WHEN PROCESSING MESSAGE text When processing a message from a subsystem resource, the program did not identify the IRLM resource to which the message is posted. This situation can occur during DB2 subsystem initialization if an exception is received while during a discovery. text message. The program that detected the situation The of the subsystem resource The system message being processed by the program The program ends without sending the If this message was issued during DB2 discovery, it can be ignored. Otherwise, report the problem to IBM Software GPZ0625E DATA SHARING GROUP CGLOBAL NOT FOUND FOR SUBSYSTEM WHEN PROCESSING MESSAGE text When processing a message from a subsystem resource, the program did not identify the IRLM resource to which the message is posted. This situation can occur during DB2 subsystem initialization if an exception is received during a discovery. text message. The program that detected the situation The of the subsystem resource The system message that was being processed by the program The program ends without sending the If this message was issued during DB2 discovery, it can be ignored. Otherwise, report the problem to IBM Software GPZ0626E - UNSUCCESSFUL CALL TO GPZBSQL FOR SUBSYSTEM. PROCESSING TERMINATED. info The GPZBSQL program did not successfully perform the requested function. The program, and optionally, the subroutine, that detected the situation The of the subsystem resource Chapter 1. GPZ prefix messages 5

16 info message. Variable return information from the GPZBSQL program The program ends without sending the This message indicates a probable configuration error. The return information from the GPZBSQL program might include a standard SQL error code. See the DB2 library for explanations of the return code and reason code to determine the configuration step that was unsuccessful. If the return information is not an SQGL error code, report the problem to IBM Software GPZ0627E - UNSUCCESSFUL CALL TO GPZBFIND FOR SUBSYSTEM. PROCESSING TERMINATED. The GPZBSQL program did not successfully perform the requested function. The program that called the GPZBFIND program The of the subsystem resource that is being processed Processing continues with the next defined subsystem. The REXX program that called the assembler routine issues another message. Complete the actions that are recommended for that message. GPZ0628I - FINISHED PROCESSING SUBSYSTEM WITH RETURN CODE. The initialization or ending process was completed for a DB2 subsystem. The program that issued the message The of the subsystem resource that is being processed The return code set by the issuing program Processing continues with the next relevant subsystem. If the return code is 0, no action is necessary. For return codes other than 0, analyze the log for earlier messages and take the recommended action. GPZ0630I SUBSYSTEM IS status; UNABLE TO ISSUE COMMAND: command The GPZBIFIC program attempted to issue a DB2 command to a subsystem, but did not do so. status The DB2 subsystem to which the command was directed The status of the DB2 subsystem: v API_ERROR v DOWN v EXCLUDED v MAINT_MODE v NOT_MONITORED v NOT_REGISTERED v SSUP v UNCONTACTABLE v UNDEFINED v UNKNOWN v UNSUPPORTED command The command that was being issued The program ends without issuing the requested command. Note the explanation of each status type and take the appropriate action as needed. API_ERROR or NOT_REGISTERED Examine the log that precedes this message for more detailed error messages and respond to any messages. DOWN Verify that the DB2 subsystem successfully initialized before issuing the command again. EXCLUDED The subsystem was defined in the GPZ$EXCL member for exclude processing. MAINT_MODE Report the problem to your DB2 administrator. NOT_MONITORED or UNCONTACTABLE Examine the log that precedes this message for more detailed error messages and respond to any messages. This status is probably the result of a configuration problem. SSUP The subsystem is currently being processed by Event Pump, and the final status is not determined. Try the command again after a short interval to allow the process to complete. If the message occurs again, report the problem to IBM Software UNDEFINED or UNKNOWN Report the problem to your DB2 administrator. 6 Message Reference

17 UNSUPPORTED The software level of the DB2 subsystem is not supported by Event Pump. GPZ0632E SUBSYSTEM IS INCOMPATIBLE; UNABLE TO ISSUE COMMAND: command The GPZBIFIC program attempted to issue a DB2 command to a subsystem, but did not do so. The DB2 subsystem to which the command was directed command The command that was being issued The program ends without issuing the requested command. This message is probably a configuration error. The version, release, or maintenance level (or any combination of these items) of the DSNALI/DSNWLI2 load module in the DB2 STEPLIB statements that are used by the issuing Event Pump region is incompatible with the STEPLIB statements that are used by the specified DB2 subsystem. GPZ0636E GPZBIFIC REQUIRES AT LEAST THREE KEYWORDS. ONLY number RECEIVED: parameter1 parameter2 The GPZBIFIC program attempted to issue a DB2 command to a subsystem, but did not do so. number The number of parameters received parameter1 The keyword parameter 1 (if specified) parameter2 The keyword parameter 2 (if specified) The command is rejected. Specify the additional parameters required and issue the command again. If the GPZBIFIC program was called by a system routine, report the problem to IBM Software GPZ0637E GPZBIFIC UNABLE TO LOAD DSNALI/DSNWLI2: ABEND CODE abend_code sub_code The GPZBIFIC program did not load the DB2 command interface module or its alias. abend_code The abend code as returned by the LOAD macro sub_code The sub code as returned by the LOAD macro The command is rejected. Event Pump cannot communicate with any DB2 subsystems. This message indicates a probable configuration error. Follow the problem determination that is relevant to the abend codes and subcodes. GPZ0638E GPZBIFIC RETURNED AN ERROR RESPONSE AND numberlines OF OUTPUT FOR: command The GPZBIFIC program issued a command to a DB2 subsystem, which accepted the command but only partially processed it. number The number of lines of command response returned by the DB2 subsystem command The command being processed Command processing was completed. Examine the command response for the reason why the DB2 subsystem did not fully process the command. GPZ0639E GPZBIFIC ENCOUNTERED THE : text The GPZBIFIC program encountered a situation that is described in the message variable text. text The variable response from the GPZBIFIC program The command ends. This message indicates a probable system error. Report the problem to IBM Software GPZ0640E parameters. ERROR: REQUIRE PARMS - REG DEREG PUSHCMD PUSHGLOB PULLGLOB QUERY DSG The program was called with insufficient The program that detected the situation The program ends. This message indicates a probable system error. If the program was called by the Chapter 1. GPZ prefix messages 7

18 user, ensure that sufficient parameters are specified. If the program was not called by the user, report the problem to IBM Software GPZ0641E ERROR: UNSUPPORTED PARM: parameter The program was called with a parameter that was not valid. The program that detected the situation parameter The parameter that was not valid The program ends. This message indicates a probable system error. If the program was called by the user, ensure that sufficient parameters are specified. If the program was not called by the user, report the problem to IBM Software GPZ0642E ERROR: parameter REQUIRES SUBSYS PARAMETER: command The program was called with a parameter that also requires a subsystem specification. The program that detected the situation parameter The valid parameter that requires the additional subparameter command A sample of a valid command The program ends. This message indicates a probable system error. If the program was called by the user, ensure that sufficient parameters are specified. If the program was not called by the user, report the problem to IBM Software GPZ0643E ERROR: parameter BAD RC ON queue_ resource_ The program received a return code other than 0 from the lock function. The program that detected the error parameter The primary parameter that was passed to the GPZ$LOCK function The return code from the lock function queue_ The queue for locking resource_ The resource for locking The enqueue is not performed. This error is probably a system error. Report the problem to IBM Software GPZ0645E ERROR: action NOT VALID: THIS DOMAIN IS THE ACTIVE MONITOR FOR resource The program was called with a parameter that also requires a subsystem specification. action The program that detected the situation The action that was requested resource The Data Sharing Group that was specified The program ends. This message indicates a probable system error. If the program was called by the user, ensure that the correct parameters are specified. If the program was not called by the user, report the problem to IBM Software GPZ0646E ERROR: action NOT DONE: NO ACTIVE MONITORING DOMAIN FOR resource The program was called with a parameter that also requires a subsystem specification. action The program that detected the situation The action requested resource The Data Sharing Group specified The program ends. This message indicates a probable system error. If the program was called by the user, ensure that the correct parameters are specified. If the program was not called by the user, report the problem to IBM Software GPZ0647I function RETURNED: response This message is displayed if a program logs the response to a request. The program that issued the message function The function being that is being run 8 Message Reference

19 response GPZ0648E The response from the program. This response is highly variable and is for informational purposes only. ERROR: UNABLE TO COMMUNICATE WITH DOMAIN: OPERATOR: operator The program did not issue the GTMRMTEX command to the specified domain. The program that detected the situation The remote domain operator The operator in the remote domain The GTMRMTEX command cannot be issued. An exception in the format GZP0648_% is sent to the relevant DB2 Data Sharing Group. Discovery and event processing are degraded or disabled. Examine the log that precedes the error message and respond to the error message or messages. Ensure that all relevant domains that monitor DB2 subsystems that belong to the affected data sharing group are authorized to issue the GTMRMTEX program to each other. Ensure also that they have functional network connections at all times. When the error condition is corrected, the program resumes communications. See the GPZ0649I message. GPZ0649I RESUMED COMMUNICATIONS WITH DOMAIN: OPERATOR: operator The program issued the GTMRMTEX command to the specified domain after a previous failure that was identified in the GPZ0648E message The program that detected the situation The remote domain operator The operator in the remote domain The system resolves the GPZ0648E_% exception against the relevant DB2 Data Sharing Group. If the situation occurs on a regular basis, the communication links among the relevant domains might require an upgrade. GPZ0680W THRESHOLD VALUE FOR 1 IN SUBSYSTEM 2 REJECTED. DEFAULT VALUE OF number MINUTES WILL BE USED The interval that was specified for a monitor was unacceptable. An acceptable default was assigned. 1 2 number interval. The monitor The subsystem The default interval in use The monitor is set to the default Ensure that the requested interval is acceptable for the specified monitor. GPZ0681E GLOBAL VARIABLE FOR IN keyword subsys NOT FOUND A required Event Pump global variable was not defined for the subsystem. The program that detected the situation The variable keyword A keyword indicating whether the variable belongs to a DB2 subsystem or Data Sharing Group subsys The subsystem or Data Sharing Group Processing of the message ends. This message indicates a probable system error. Report the problem to IBM Software GPZ0684E ERROR: KEYWORD keyword MUST BE DSGNAME OR SSNAME. A keyword that was not valid was passed to the program. The program that detected the situation. keyword The keyword that was not valid. The command is rejected. Ensure that the command parameters are correctly specified. GPZ0685W WARNING: type IS EXCLUDED FROM MONITORING. While processing an event, the program determined that the specified resource was excluded from monitoring. type The program that issued the message The type of resource The of the resource Events related to the specified resource Chapter 1. GPZ prefix messages 9

20 are not processed. If the program is GPZBSSUP, discovery processing is not performed for the resource. Confirm that you do not want to monitor the resource. GPZ0686W type WARNING: UNABLE TO MONITOR type. The d resource is not monitored. The program that issued the message The type of resource The of the resource Events related to the specified resource are not processed. This message is issued to alert the administrator to a potential error condition. If the situation is expected, ignore this message. Otherwise, examine the related messages which were written to the log and respond to them. GPZ0688E member token member: INVALID TOKEN token DETECTED IN MESSAGE message_id. MESSAGE NOT PROCESSED. The d resource is not monitored. The of the REXX program issuing this message The token parsed from the incoming message message_id The message ID of the incoming message containing the token that was not valid Processing continues and the incoming message is ignored. No event is created. If you do not want to monitor this message, remove all references to it. Otherwise, notify IBM Software Support of this error. GPZ0689E UNABLE TO PARSE RESPONSE var_1 var_2 var_3 var_4 var_5 The d program did not parse the response to a command or query The program that detected the situation var_1 through var_5 The summary information describing the parsed response recovery. The program performs additional error Examine the log that precedes the error message for more detailed messages. If there are no additional error messages, contact IBM Software GPZ0710I LOADING GPZ$EXCL SINCE IT IS NOT CURRENTLY LOADED This message is displayed when the GPZ$EXCL member is loaded from the GTMMON DD data set for the first event that matches the Exclude rules that were generated since the source collector startup. GPZ0711I GPZ#EXCL VALID OPTIONS ARE: options This multiline message results when the GPZ#EXCL command is issued with an option that is not valid. options SHOW Shows the current loaded filter and statistics REFRESH Refreshes the filter from the GPZ$EXCL DSIPARM member CHECK Checks the type, resource, and event ID with a valid option. GPZ0712E Enter the command again RESOURCE_TYPE type IS NOT SUPPORTED. This message is issued when an unsupported resource_type is specified in the GPZ$EXCL member, or in the GPZ#EXCL CHECK command. type The type of resource See the GPZ$EXCL GTMMON member for a list of supported resource types. GPZ0714I GPZ$EXCL GTMMON HAS NO FILTERS FOR SYSNAME sys_ This message is issued when the GPZ#EXCL SHOW command is used and no filters are active for this system. sys_ The z/os system If this message is 10 Message Reference

21 unexpected, review the GPZ$EXCL GTMMON member. Issue the GPZ#EXCL REFRESH command to load the GPZ$EXCL member from the GTMMON DD data set. If a request was accepted and queued, but not completed, examine the log for related error messages and respond to them. GPZ0715I GPZ$EXCL WAS LOADED date time FROM dsn This message is issued when the GPZ#EXCL SHOW command is used. The current loaded filters and statistics are also listed as part of this multiline message. date time dsn GPZ0716E The date that the GPZ$EXCL member was loaded from the DSIPARM DD The time that the GPZ$EXCL member was loaded from the DSIPARM DD The DSN where the GPZ$EXCL member was loaded VALID PARMS ARE: Resource_Type Resource_Name {Event_ID} The GPZ#EXCL CHECK command was called with incorrect parameters. The following parameters are valid: Resource_Type (Required) Valid resource type as documented in the GPZ$EXCL SGTMSAMP member Resource_Name (Required) The of the resource Event_ID (Optional) The ID of the event For more information about the parameters, see the GPZ$EXCL sample in the SGTMSAMP data set. These examples show the correct GPZ#EXCL CHECK calls: * GPZ#EXCL CHECK DBSS DB6A * GPZ#EXCL CHECK IMPG PGM1 DFS1234 If this message is a response to a user command, enter the command again with valid parameters. If not, contact IBM Software GPZ0724I DISCOVERY REQUEST FOR resource HAS BEEN ACCEPTED. The system accepted a request to discover a resource. resource The resource that is discovered. Discovery operates asynchronously. Requests to perform discovery are first validated and then queued for processing. This process enables the console to be used for other processing while the discovery continues. GPZ0750I OUTPUT DISPLAY FOLLOWS: This message is issued as a header message that precedes the display of data from an Event Pump process. This message is preceded by another Event Pump error or informational message. Review the data that follows this message, together with any relevant previous messages, and perform any action as required. GPZ0751I COMMAND IN module_ TIMED OUT The module_ routine received no response from an attempt to issue a command to another subsystem module_ The of the module GPZ0817I module disc_type REDISCOVERY STARTING FOR resource_type resource_ (FROM datetime). The d routine started rediscovery of this resource. module The of a module that is performing the rediscovery. disc_type The type of discovery, which is either FULL or PARTIAL. resource_type The type of resource being rediscovered. resource_ The of the resource being rediscovered. datetime For partial rediscoveries, resources that are modified or added only after this date and time are rediscovered. For full rediscoveries, this variable is not displayed. Rediscovery of this resource continues. Chapter 1. GPZ prefix messages 11

22 GPZ0829I (module) feed_ REDISCOVERY FOR DEFERRED. The installation specified that rediscovery be deferred. module The of the module feed_ The of the Event Pump data resource. For example, DB2 systems The of the DB2 subsystem being rediscovered The scope of the rediscovery is reduced and processing continues. GPZ3010E None required KEYWORD REQUIRED A required keyword in the ZEVENT block was not entered. required USRMASK generated. GPZ3030E Processing stops and no event is None PROCESSING FAILED RC= MSG=message Processing of the ZEVENT block for this trap entry failed. The return code identifies the major function and the specific return code causing the error. Return code that caused this event processing to stop. message The text of the message being processed. generated. GPZ3031I Processing stops and no event is None TRAP type - value Information message that is displayed with other error messages. The type of information and the value is displayed. type Types of variables for the trap: ZEVENT The ZEVENT block definitions SET VARIABLES Variables pasted to the trap value generated. USER VARIABLES USER9X fields set for this trap The value of the variable list in type. GPZ3040E Processing stops, and no event is None REQUIRED DATA MISSING OR INVALID The information passed to the customizer from the monitor registration does not include the required information. This error can occur if the customizer was called outside of the standard registration process. generated. Processing stops, and no event is If the customizer was called from the registration process, contact IBM Software GPZ3041E keyword KEYWORD INVALID The keyword is invalid on the user call. This error can occur if the customizer was called outside of the standard registration process. keyword The of the keyword on the MONITOR registration entry that is in error: MONITOR TYPE NUMBER VALUE DEBUG generated. Processing stops, and no event is If the customizer was called from the registration process, contact IBM Software GPZ3042E NO DATA FOUND FOR COMMAND Additional required information is missing from the REQUEST variable. GPZ3043E keyword INVALID SYNTAX Invalid syntax was found for the keyword on the user call. keyword The of the keyword on the MONITOR registration entries that are in error: FORMAT ACTION DEBUG 12 Message Reference

23 Processing stops, and no event is generated. GPZ3044E None SUBSTITUTION LOOP COUNT EXCEEDED The substitution process tried 5 times to resolve the variables. The substitution ended. Ensure that the variable s are correct. Correct the variable s and unregister and register the registration entry. GPZ3045W substitution. variable CANNOT RESOLVE SUBSTITUTION VARIABLE variable IN TRAP trap_ Variable variable cannot be located for The variable that cannot be resolved. trap_ The trap containing the error. generated. Processing stops, and no event is Verify that the ZEVENT block contains valid variable s for substitution. GPZ3046E NAME OF THE SUBSTITUTION VARIABLE variable EXCEEDS MAXIMUM SIZE The of the variable exceeds the maximum length of 16 characters. variable generated. The of the variable in error. a length of 16 or less. GPZ3047E Processing stops, and no event is Correct the variable to VALUE OF THE SUBSTITUTION VALUE variable_ EXCEEDS MAXIMUM SIZE The value of the variable exceeds the maximum length of 80 characters. generated. Processing stops, and no event is Correct the variable to a length of 80 or less. An additional variable might be required. GPZ3048E UNABLE TO OBTAIN BUFFER STORAGE FOR storage_area RETURN CODE = Storage cannot be obtained for the specified area. storage_area The of the storage area for which storage is to be obtained: v CELL BUFFER v RETURN VALUE v USERxx PARAMETER v VARIABLE PARAMETER v VARIABLE POOL v WORKAREA Return code from the request generated. GPZ3049E Processing stops, and no event is CANNOT RESOLVE trap_data FOR OBJECT The customizer cannot retrieve the specified trap information. trap_data The of the trap data variable that cannot be retrieved: JOB TYPE MESSAGE TRAP NAME generated. GPZ3050E Processing stops, and no event is INVALID KEYWORD: syntax_desc FOR TRAP trap_ The syntax processing identified an invalid keyword syntax_desc Additional information from the syntax call relating to the error trap_ The trap containing the error generated. Processing stops, and no event is Chapter 1. GPZ prefix messages 13

24 GPZ3051E INVALID OPTION: syntax_desc FOR TRAP trap_ The syntax processing identified an invalid option. syntax_desc Additional information from the syntax call relating to the error trap_ The trap containing the error generated. GPZ3052E invalid state. Processing stops, and no event is INVALID STATE: syntax_desc FOR TRAP trap_ The syntax processing identified an syntax_desc Additional information from the syntax call relating to the error trap_ The trap containing the error generated. GPZ3053E Processing stops, and no event is KEYWORD CONFLICT: syntax_desc FOR TRAP trap_ The syntax processing identified conflicting keywords. syntax_desc Additional information from the syntax call relating to the error trap_ The trap containing the error generated. Processing stops, and no event is GPZ3054E CONFLICTING OPTION: syntax_desc FOR TRAP trap_ The syntax processing identified conflicting options. syntax_desc Additional information from the syntax call relating to the error trap_ The trap containing the error generated. GPZ3055E Processing stops, and no event is MISSING KEYWORD: syntax_desc FOR TRAP trap_ The syntax processing identified a missing keyword. syntax_desc Additional information from the syntax call relating to the error trap_ The trap containing the error generated. GPZ3056E Processing stops, and no event is MISSING OPERAND: syntax_desc FOR TRAP trap_ The syntax processing identified a missing operand. syntax_desc Additional information from the syntax call relating to the error trap_ The trap containing the error generated. Processing stops, and no event is 14 Message Reference

25 GPZ3057E NON_NUMERIC DATA: syntax_desc FOR TRAP trap_ The syntax processing identified non-numeric data. syntax_desc Additional information from the syntax call relating to the error trap_ The trap containing the error generated. GPZ3058E error. Processing stops, and no event is SYNTAX ERROR: syntax_desc FOR TRAP trap_ The syntax processing identified a syntax syntax_desc Additional information from the syntax call relating to the error trap_ The trap containing the error generated. GPZ3060E Processing stops, and no event is PREDEFINED VARIABLE variable_ CANNOT BE SET, REQUEST IGNORED The used in the SET command is a reserved predefined variable. variable_ The of the predefined reserved variable The request is ignored. Ensure that the variable s are correct. Correct the variable s and unregister and register the registration entry. GPZ3061E ERROR OCCURRED FOR KEYWORD keyword An error occurred processing keyword keyword. Additional messages are displayed for additional information about the error. keyword The of the keyword that caused the error to occur. Additional messages detail the error. generated. Processing stops, and no event is Correct the ZEVENT keyword and register the monitoring. GPZ3062W SEVERITY NOT SET, USING DEFAULT SEVERITY MINOR FOR TRAP trap_ Severity was not set; the default severity of MINOR is used. trap_ The trap containing the error Processing continues; the default severity is used. GPZ3063W None INVALID SEVERITY DEFINED severity, USING DEFAULT SEVERITY MINOR FOR TRAP trap_ An invalid severity was set to a substitution that is invalid. severity The severity that is invalid trap_ The trap containing the error. Processing continues, the default severity is used. Correct the SEVERITY keyword or verify that the value of the substitution is a valid severity. GPZ3064W MESSAGE TEXT: message_text Message text is displayed for additional information that is related to another error message. The GPZ0365I message is also displayed. message_text The message text that is being processed generated. Processing stops, and no event is None Chapter 1. GPZ prefix messages 15

26 GPZ3065W MESSAGE MASK: message_mask Message mask is displayed for additional information related to another error messages. The GPZ0364I message is also displayed. message_mask The mask that is to be used to parse the input message generated. GPZ3066E Processing stops, and no event is None END OF STRING ENCOUNTERED USING MESSAGE MASK All of the mask tokens were processed, but additional message text was not processed. The GPZ0364I and GPZ3065I messages are also displayed. generated. GPZ3067E Processing stops, and no event is None NO MATCH IN MESSAGE FOR LITERAL search_string The literal in the mask does not match the literal in the message text. The GPZ0364I and GPZ3065I messages are also displayed. search_string The text that does not match within the message text generated. GPZ3068E Processing stops, and no event is None MISMATCH OF SCAN ITEMS AND MESSAGE TEXT The message text was processed, but additional mask tokens were not processed. The GPZ0364I and GPZ3065I messages are also displayed. generated. GPZ3069E Processing stops, and no event is None FORMAT %S+ MISSING REQUIRED NUMBER OF CONSTANTS The mask for this trap has %S+ but matching of the mask tokens determined that there is a null string. %S+ requires at least one message token for a successful match. The GPZ0364I and GPZ3065I messages are also displayed. For information about %S+ and other component specifiers, see the Event Pump for z/os Installation and Configuration Guide. generated. GPZ5700I Processing stops, and no event is None SOURCE MANAGER STARTED The source manager started during the Event Pump initialization process. GPZ5701I None SOURCE MANAGER STOPPED The source manager stopped during the Event Pump end process. GPZ5702I None JOBLOG JES monitor started for job.dd SPOOL DD Monitoring of the specified spool DD data set started. job The Job that the user specified for monitoring dd The DD that the user specified for monitoring GPZ5703I None JOBLOG JES MONITOR STOPPED FOR job.dd SPOOL DD Monitoring of the specified spool DD data set stopped. job The job that the user specified for monitoring dd The DD that the user specified for monitoring None 16 Message Reference

27 GPZ5704E SOURCE MANAGER NOT STARTED The user requested the source manager for an action, but the source manager is not started. task failed. Processing continues, but the requested Support for more instructions. GPZ5705E set failed. ALLOCATION FAILED FOR job.dd SPOOL DD Allocation of a specified spool DD data job The Job that the user specified for monitoring dd The of the DD data set that the user specified for monitoring The JOBLOG monitor task stopped. Support for more instructions. GPZ5706E DEALLOCATION FAILED FOR job.dd SPOOL DD Deallocation of the specified spool DD data set failed. job The Job that the user specified for monitoring dd The of the DD data set that the user specified for monitoring The JOBLOG monitor task stopped. Support for more instructions. GPZ5707E open. I/O INITIALIZATION FAILED FOR job.dd SPOOL DD The specified spool DD data set failed to job The job that the user specified for monitoring dd The of the DD data set that the user specified for monitoring The JOBLOG monitor task stopped. Support for more instructions. GPZ5708E ERROR READING job.dd SPOOL DD An error occurred while reading a record from the specified spool DD data set. job The job that the user specified for monitoring dd The of the DD data set that the user specified for monitoring The JOBLOG monitor task stopped. Support for more instructions. GPZ5709E close. I/O TERMINATION FAILED FOR job.dd SPOOL DD The specified spool DD data set failed to job The job that the user specified for monitoring dd The of the DD data set that the user specified for monitoring The JOBLOG monitor task stopped. Support for more instructions. GPZ5710I JOBLOG DID NOT FIND ACTIVE JOB IN COMPLIANCE WITH SPECIFIED CRITERIA FOR job.dd SPOOL DD The JOBLOG monitor task tried to find the active jobs that the user specified for monitoring, but no spool DD data set matches the specified filter. job The job that the user specified for monitoring dd The of the DD data set that the user specified for monitoring GPZ5711I None JOBLOG ALREADY MONITORED SPECIFIED job.dd SPOOL DD The user requested that the JOBLOG manager monitor a specified spool DD data set, but this DD data set was already monitored. Chapter 1. GPZ prefix messages 17