ibmtivoli event pump for z/os version 4.2 · ibm tivoli event pump for z/os library this following...

IBM Tivoli Event Pump for z/OSVersion 4.2.2

Message Reference

GC27-2310-05

��

NoteBefore using this information and the product it supports, read the information in “Notices” on page 127.

This edition applies to Version 4.2.2 of IBM Tivoli Event Pump for z/OS (product number 5698-B34) and to allsubsequent versions, releases, and modifications until otherwise indicated in new editions.

This edition replaces GC27-2310-04.

© Copyright IBM Corporation 2008, 2011.US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contractwith IBM Corp.

Contents

About this publication . . . . . . . . vIntended audience . . . . . . . . . . . . vPublications . . . . . . . . . . . . . . v

IBM Tivoli Event Pump for z/OS library . . . . vRelated publications . . . . . . . . . . . vAccessing terminology online. . . . . . . . vAccessing publications online . . . . . . . viOrdering publications . . . . . . . . . . vi

Accessibility . . . . . . . . . . . . . . viTivoli technical training . . . . . . . . . . viTivoli user groups . . . . . . . . . . . . viiSupport information . . . . . . . . . . . vii

Conventions used in this publication . . . . . . viiTypeface conventions . . . . . . . . . . viiOperating system-dependent variables andpaths . . . . . . . . . . . . . . . viii

Chapter 1. GPZ prefix messages . . . . 1

Chapter 2. GTM prefix messages . . . 21

Notices . . . . . . . . . . . . . . 127Trademarks . . . . . . . . . . . . . . 128

© Copyright IBM Corp. 2008, 2011 iii

iv Message Reference

About this publication

IBM® Tivoli® Event Pump for z/OS® is an enterprise management product thatmonitors the z/OS data processing resources in an enterprise. You can use it tomonitor the z/OS systems, subsystems, applications, and other resources that arecritical to your business. This publication, the IBM Tivoli Event Pump forz/OS Message Reference, describes the messages for Event Pump for z/OS.

Intended audienceThis publication is for system programmers, system administrators, networkoperators, and others who need message information for Event Pump.

PublicationsThis section lists publications in the IBM Tivoli Event Pump for z/OS library andrelated documents. It also describes how to access Tivoli publications online andhow to order Tivoli publications.

IBM Tivoli Event Pump for z/OS libraryThis following documents are in the IBM Tivoli Event Pump for z/OS library:v Command Reference, SC27-4040, describes the commands for Event Pump for

z/OS.v Configuration Reference, SC27-4041, describes the configuration statements for

Event Pump for z/OS.v Event Reference, SC27-2895, lists the events (exceptions and messages) that are

integrated with Event Pump for z/OS.v Installation and Configuration Guide, SC27-4042, describes how to install and

configure Event Pump for z/OS.v Message Reference, GC27-2310, describes the messages for Event Pump for z/OSv Troubleshooting Guide, GC27-4043, provides information for use in diagnosing and

solving problems that occur in Event Pump for z/OS.v Program Directory for IBM Tivoli Event Pump for z/OS, GI11-8920, contains

information about the material and procedures that are associated with installingEvent Pump for z/OS.

Related publicationsFor information about the IBM Tivoli Business Service Manager product, link tothe product information center from http://www.ibm.com/developerworks/wikis/display/tivolidoccentral/Tivoli+Business+Service+Manager.

For information about the IBM Tivoli Netcool/OMNIbus product, link to theproduct information center from http://www.ibm.com/developerworks/wikis/display/tivolidoccentral/OMNIbus.

Accessing terminology onlineThe IBM Terminology website consolidates the terminology from IBM productlibraries in one convenient location. You can access the Terminology website athttp://www.ibm.com/software/globalization/terminology.

© Copyright IBM Corp. 2008, 2011 v

http://www.ibm.com/developerworks/wikis/display/tivolidoccentral/Tivoli+Business+Service+Manager

http://www.ibm.com/developerworks/wikis/display/tivolidoccentral/Tivoli+Business+Service+Manager

http://www.ibm.com/developerworks/wikis/display/tivolidoccentral/OMNIbus

http://www.ibm.com/developerworks/wikis/display/tivolidoccentral/OMNIbus

http://www.ibm.com/software/globalization/terminology/

The following terms are used in this library:

AOPxxLOGFor the AOPxxLOG system log in the 2-address-space environment or theAOPLOG system log in the 3-address-space environment. AOPxxLOG iseither AOPEDLOG (event distributor log) or AOPSCLOG (source collectorlog).

AOPLOGFor the AOPxxLOG system log in the 2-address-space environment or theAOPLOG system log in the 3-address-space environment. AOPxxLOG iseither AOPEDLOG (event distributor log) or AOPSCLOG (source collectorlog).

Accessing publications onlineIBM posts publications for this and all other Tivoli products, as they becomeavailable and whenever they are updated, to the Tivoli Documentation Centralwebsite at http://www.ibm.com/tivoli/documentation.

Note: If you print PDF documents on other than letter-sized paper, set the optionin the File → Print window that allows Adobe Reader to print letter-sizedpages on your local paper.

Ordering publicationsYou can order many Tivoli publications online at http://www.ibm.com/e-business/linkweb/publications/servlet/pbi.wss

You can also order by telephone by calling one of these numbers:v In the United States: 800-879-2755v In Canada: 800-426-4968

In other countries, contact your software account representative to order Tivolipublications. To locate the telephone number of your local representative, performthe following steps:1. Go to http://www.ibm.com/e-business/linkweb/publications/servlet/pbi.wss.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.

AccessibilityAccessibility features help users with a physical disability, such as restrictedmobility or limited vision, to use software products successfully. Event Pump forz/OS has no user interface or user interactions except through the interfaces ofother products. For information about accessibility features for those products, seethe applicable product information.

Visit the IBM Accessibility Center at http://www.ibm.com/alphaworks/topics/accessibility/ for more information about IBM's commitment to accessibility.

Tivoli technical trainingFor Tivoli technical training information, refer to the following IBM TivoliEducation website at http://www.ibm.com/software/tivoli/education.

vi Message Reference

http://www.ibm.com/tivoli/documentation

http://www.ibm.com/e-business/linkweb/publications/servlet/pbi.wss



http://www.ibm.com/alphaworks/topics/accessibility/

http://www.ibm.com/alphaworks/topics/accessibility/

http://www.ibm.com/software/tivoli/education

Tivoli user groupsTivoli user groups are independent, user-run membership organizations thatprovide Tivoli users with information to assist them in the implementation ofTivoli Software solutions. Through these groups, members can share informationand learn from the knowledge and experience of other Tivoli users.

Access the Tivoli Users Group at http://www.tivoli-ug.org.

Support informationIf you have a problem with your IBM software, you want to resolve it quickly. IBMprovides the following ways for you to obtain the support you need:

OnlineAccess the Tivoli Software Support site at http://www.ibm.com/software/sysmgmt/products/support/index.html?ibmprd=tivman. Access the IBMSupport Portal at http://www.ibm.com/support/entry/portal/software .

IBM Support AssistantIBM Support Assistant is a free local software serviceability workbenchthat you can use to resolve questions and problems with IBM softwareproducts. Support Assistant provides quick access to support-relatedinformation and serviceability tools for problem determination. To installthe Support Assistant software, go to http://www.ibm.com/software/support/isa/.

After you install Support Assistant, you can install the IBM Tivoli EventPump for z/OS add-on. In Support Assistant, click Update > Find new. Inthe Find New Product Add-ons window, click Tivoli and then find andinstall the IBM Tivoli Event Pump for z/OS add-on.

Troubleshooting GuideFor more information about resolving problems, see the Event Pump forz/OS Troubleshooting Guide.

Conventions used in this publication

Typeface conventionsThis publication uses the following typeface conventions:

Bold

v Lowercase commands and mixed case commands that are otherwisedifficult to distinguish from surrounding text

v Interface controls (check boxes, push buttons, radio buttons, spinbuttons, fields, folders, icons, list boxes, items inside list boxes,multicolumn lists, containers, menu choices, menu names, tabs, propertysheets), labels (such as Tip:, and Operating system considerations:)

v Keywords and parameters in text

Italic

v Citations (examples: titles of publications, diskettes, and CDsv Words defined in text (example: a nonswitched line is called a

point-to-point line)

About this publication vii

http://www.tivoli-ug.org

http://www.ibm.com/software/sysmgmt/products/support/index.html?ibmprd=tivman/

http://www.ibm.com/software/sysmgmt/products/support/index.html?ibmprd=tivman/

http://www.ibm.com/support/entry/portal/software

http://www.ibm.com/software/support/isa/

http://www.ibm.com/software/support/isa/

v Emphasis of words and letters (words as words example: "Use the wordthat to introduce a restrictive clause."; letters as letters example: "TheLUN address must start with the letter L.")

v New terms in text (except in a definition list): a view is a frame in aworkspace that contains data.

v Variables and values you must provide.

Monospace

v Examples and code examplesv File names, directory names, and path namesv Message text and prompts addressed to the userv Text that the user must typev Values for arguments or command options

Operating system-dependent variables and pathsThis publication uses the UNIX convention for specifying environment variablesand for directory notation.

When using the Windows command line, replace $variable with %variable% forenvironment variables and replace each forward slash (/) with a backslash (\) indirectory paths. The names of environment variables are not always the same inthe Windows and UNIX environments. For example, %TEMP% in Windowsenvironments is equivalent to $TMPDIR in UNIX environments.

Note: If you are using the bash shell on a Windows system, you can use the UNIXconventions.

viii Message Reference

Chapter 1. GPZ prefix messages

The GPZ prefix messages are issued by the components that make up the serviceson a z/OS mainframe systems. These messages include the source collector, eventdistributor, and data space.

Some of the messages are issued from other address spaces that use thecomponents.

GPZ0000W NO num MESSAGE ENTRY FOUNDFOR prefix WITH PARMS parms

Explanation: The message identified with messagenumber num and message prefix prefix is not in theGPZMSG message file. The message used theparameters passed in parms.

Message variables:

num The 4-digit message number

prefix The 3-character message prefix

parms The additional parameters that are used toform the message

System action: The message is ignored and processingcontinues.

Administrator response: Verify that the data setassociated with GPZMSG DD has an entry point for theindicated message. Otherwise, contact IBM SoftwareSupport.

GPZ0204E USRMASK KEYWORD REQUIRED

Explanation: A keyword for the USRMASK statementis required.

System action: Processing continues.

GPZ0320W UNABLE TO LOCATE INTERVALSETTINGS FOR MAINVIEW SYSPROGSAMPLES

Explanation: The initialization routine for BMCMainView SYSPROG services was unable to locate theBMC MainView SYSPROG address space.

System action: Processing stops.

Administrator response: Check that the job nameassigned to the JOBNAME= keyword of the registrationentry is the correct job name for the BMC MainViewSYSPROG services address space. If it is correct,unregister and register the BMC MainView for z/OSmonitoring.

GPZ0321E UNABLE TO ALLOCATE DD ddnameRC=return_code

Explanation: The temporary DD data set was unableto be allocated for the BMC MainView SYSPROGServices PARMLIB DD data set.

Message variables:

ddname The name of the temporary DD data set

return_codeThe return code


Administrator response: Contact IBM SoftwareSupport with the return code from the message.

GPZ0322E ERROR READING MAINVIEWSAMPLE MEMBER member_name FROMddname

Explanation: Event Pump cannot read or locate thePWSCPMxx member from the PARMLIB data set fromthe BMC MainView SYSPROG Service address space.

Message variables:

member_nameThe name of the PWSCPMxx member

ddname The DD name

System action: Processing continues. A default of 60seconds is used for all of the BMC MainViewSYSPROG samples.

GPZ0323I UNABLE TO DEALLOCATE DD ddnameRC=return_code

Explanation: The temporary DD data set is notdeallocated for the BMC MainView SYSPROG ServicesPARMLIB DD data set.

Message variables:

ddname The name of the temporary DD data set



© Copyright IBM Corp. 2008, 2011 1

GPZ0330W DATASET DSN=dsname VOL=volumeFAILED READ-ONLY CHECKRC=return_code

Explanation: The source collector is not authorized forREAD access to DB2® libraries in the RACF® product.

Message variables:

dsname The data set name

volume The volume name

return_codeThe RACF return code


Administrator response: Authorize the sourcecollector for READ access to DB2 libraries in RACF.Restart the source collector.

GPZ0337E ROUTINE routine_nameENCOUNTERED UNEXPECTEDRETURN CODE FROM subroutine_name,RC=return_code

Explanation: The routine in the message textattempted to call the subroutine_name and received anunexpected return code.

Message variables:

routine_nameThe name of the routine

subroutine_nameThe name of the subroutine

return_codeReturn codes

0 The routine completed successfully

4 The routine does not fully supportthis release of the DB2 program. Onlyminimal information was returned.

8 An error occurred when creatingsome of the REXX variables.

12 No parameters were provided.

16 The target DB2 program was notfound.

Administrator response: If you cannot resolve theproblem, contact IBM Software Support.

GPZ0394E DSIGET FAILURE

Explanation: A routine received a return code otherthan 0 from the DSIGET macro.

Message variables:

name The name of the routine

System action: Issues a secondary message.

Administrator response: The REXX program thatcalled the routine issues another message. Complete theactions that are recommended for that message

GPZ0395E THE DB2 SUBSYSTEM NAME MUST BE1 TO 4 CHARACTERS LONG

Explanation: The subsystem name passed to theGPZBFIND program was not 1 - 4 characters in length.


Administrator response: The REXX program thatcalled the assembler routine issues another message.Complete the actions that are recommended for thatmessage.

GPZ0396E CONNECT TO DB2 SUBSYSTEM nameFAILED. RETURN CODES return_codereason_code

Explanation: The GPZBFIND program did not connectto the DB2 subsystem.

Message variables:

name The DB2 subsystem name

return_codeThe return code from the DB2 interface that iscalled by the GPZBIFIC program

return_codeThe reason code from the DB2 interface that iscalled by the GPZBIFIC program



GPZ0397E CALL TO DB2 DSNWLI FAILED. DB2RETURN CODES return_code reason_code

Explanation: The GPZBFIND program did not call theDSNWLI link-edit step.

Message variables:




Administrator response: Probable configuration error.See the DB2 library for an explanation of the returncode and reason code; the return code and reason codeindicate which configuration step was unsuccessful.

2 Message Reference

GPZ0398E CALL TO DB2 DSNWLI FAILED. DB2RETURN CODES return_code reason_code

Explanation: The program did not call the DB2interface that is called by the GPZBIFIC program.

Message variables:




Administrator response: The REXX program thatcalled the routine issues another message. Complete theactions that are recommended for that message.

GPZ0402I debug_text

Explanation: This message is issued in DEBUG modeto display diagnostic internal data and is for use onlyby IBM Software Support.

GPZ0451I pgm COMPLETED WITH RETURNCODE return_code called_mod call_mod_rcsubsystem

Explanation: This message is issued to indicatewhether the program completed successfully orunsuccessfully with a return code value of return_code.It might also indicate a called subsidiary module, thereturn code from that module, and the name of asubsystem.

Message variables:

pgm The program name, which might includeadditional identification parameters inparentheses

return_codeThe return code from the program

called_modThe module that is called from the program

call_mod_rcThe return code from the module

subsystemThe subsystem name


Administrator response: If the return code is not 0,contact IBM Software Support.

GPZ0580E GPZMSG FAILED WITH RETURNCODE return_code ACTION action_codeOBJECT TYPE object_type SUBSYSTEMDB2_subsys_name

Explanation: An internal API failed to complete.

Message variables:

return_codeThe return code from the GPZMSG program

action_codeThe action code that was defined within themessage

object_typeThe type of resource to which the messagewas being sent

SUBSYSTEMThe DB2 subsystem that owns the resource


Administrator response: This message indicates aninternal error. Contact IBM Software Support.

GPZ0582I GPZBINIT COMPLETED WITHRETURN CODE return_code

Explanation: Initialization of DB2 instrumentation forthe Event Pump completed.

Message variables:


Administrator response: If the return code is not 0,examine the log that precedes this message for moredetailed error messages and respond to them.

GPZ0589W FORMAT OF MAINVIEW MESSAGEmsgid NOT VALID FOR IBM TIVOLIEVENT PUMP.

Explanation: An unexpected message was received.

Message variables:

msgid The unique identifier of the message

System action: The message is not processed.


GPZ0606E pgm subsystem DISCOVERYABANDONED, CUSTOMIZATIONERRORS FOUND

Explanation: The named program determined that thenominated DB2 subsystem cannot be discovered due toerrors that are related to Event Pump or DB2customization.

Message variables:

Chapter 1. GPZ prefix messages 3

pgm The program that issued the message

subsystemThe program that issued the message

System action: The name of the subsystem beingprocessed

Administrator response: See the Event Pump forz/OS Installation and Configuration Guide for moreinformation. Run the DB2 IVP program for thenominated DB2 subsystem and correct any errors. TheDB2 subsystem is discovered at the next subsystem orwhen the source collector is started again.

GPZ0607I pgm REDISCOVERY FOR object nameROUTED TO domain

Explanation: The named program determined that thenominated DB2 subsystem or Data Sharing Group ismonitored by another domain, which is responsible forprocessing the discovery.

Message variables:


object The SSNAME literal for the DB2 subsystem orthe DSGNAME literal for the DB2 data-sharinggroup

name The name of the DB2 subsystem or DataSharing group

domain The name of the Event Pump domain thatperforms the discovery

System action: The discovery continues on thenominated domain.

Administrator response: No response is necessaryunless the discovery does not complete successfully. Inthat case, examine the log for more information.

GPZ0608E pgm MONITORING DOMAIN FORobject name IS NOT KNOWN

Explanation: The named program did not determinethe domain that performs the discovery of thenominated Data Sharing Group (DSG).

Message variables:


object The literal SUBSYSTEM or DSG

name The name of the DB2 subsystem or DSG

System action: The discovery is bypassed.


GPZ0609I pgm status DISCOVERY OF classOBJECTS

Explanation: The named program either started orfinished the process of discovering the named class ofresources.

Message variables:


status The status, either STARTED or FINISHED

class The name of the class of resources

System action: The discovery process continues.

GPZ0620W pgm - NO DB2 SUBSYSTEMSCURRENTLY ACTIVE FOR DSG name

Explanation: An attempt was made to issue a DB2command to a Data Sharing Group, but there were noactive members available to process the command.

Message variables:

pgm The program that detected the situation

name The DB2 Data Sharing Group name

System action: The program ends without issuing therequested command.

Administrator response: Ensure that at least one DB2subsystem in the Data Sharing Group is active andissue the command again. If the command was issuedthrough the GUI from a DB2 subsystem resourceinstead of a Data Sharing Group resource, name mightbe null. This situation occurs if the host did notmonitor members of the Data Sharing Group. Thesubsystem or subsystems might be inactive, or theymight be active but excluded from monitoring.

GPZ0621E CALL TO GPZEVENT FROM pgmFAILED WITH RETURNCODE=return_code ACTION=action_codeOBJECT TYPE=object_typeSUBSYSTEM=name

Explanation: The GPZEVENT program did not sendan event.

Message variables:


return_codeThe return code from the GPZEVENT program

action_codeThe action code that was defined within theevent

object_typeThe type of resource to which the event wasbeing sent

name The DB2 subsystem that owns the resource

4 Message Reference

System action: The program ends without sending theevent.

Administrator response: Identify the host event to bebuilt, and report the problem to IBM Software Support.

GPZ0622E CALL TO GPZEVENT FROM pgmFAILED WITH RETURN CODE =return_code ACTION = action_codeOBJECT_TYPE = object_type DSG NAME= name

Explanation: The GPZEVENT program did not sendan event.

Message variables:


return_codeThe return code from the GPZEVENT program

action_codeThe action code that was defined within theevent

object_typeThe type of resource to which the event wasbeing sent

name The DB2 subsystem that owns the resource

System action: The program ends without sending theevent.

Administrator response: Identify the host event to bebuilt, and report the problem to IBM Software Support.

GPZ0623W pgm: MESSAGE message_id FROM nameIGNORED. MESSAGE NOT VALIDFOR A STAND-ALONE DB2SUBSYSTEM

Explanation: A message related to a group buffer poolwas issued from a DB2 subsystem. Event Pumpconsiders this subsystem to be a stand-alone subsystemand does not participate in a data sharing group.

Message variables:


message_idThe DB2 message being processed

name The name of the DB2 subsystem that issuedthe message

System action: Processing continues. The DB2message is not processed.

Administrator response: If the subject DB2 subsystemis part of a data sharing group, it was incorrectlyidentified as a stand-alone subsystem. Report theproblem to IBM Software Support.

GPZ0624E pgm: IRLM CGLOBAL NOT FOUNDFOR SUBSYSTEM name WHENPROCESSING MESSAGE text

Explanation: When processing a message from asubsystem resource, the program did not identify theIRLM resource to which the message is posted. Thissituation can occur during DB2 subsystem initializationif an exception is received while during a discovery.

Message variables:


name The name of the subsystem resource

text The system message being processed by theprogram

System action: The program ends without sending themessage.

Administrator response: If this message was issuedduring DB2 discovery, it can be ignored. Otherwise,report the problem to IBM Software Support.

GPZ0625E pgm DATA SHARING GROUPCGLOBAL NOT FOUND FORSUBSYSTEM name WHENPROCESSING MESSAGE text

Explanation: When processing a message from asubsystem resource, the program did not identify theIRLM resource to which the message is posted. Thissituation can occur during DB2 subsystem initializationif an exception is received during a discovery.

Message variables:



text The system message that was being processedby the program


Administrator response: If this message was issuedduring DB2 discovery, it can be ignored. Otherwise,report the problem to IBM Software Support.

GPZ0626E pgm - UNSUCCESSFUL CALL TOGPZBSQL FOR SUBSYSTEM name.PROCESSING TERMINATED. info

Explanation: The GPZBSQL program did notsuccessfully perform the requested function.

Message variables:

pgm The program, and optionally, the subroutine,that detected the situation



info Variable return information from theGPZBSQL program


Administrator response: This message indicates aprobable configuration error. The return informationfrom the GPZBSQL program might include a standardSQL error code. See the DB2 library for explanations ofthe return code and reason code to determine theconfiguration step that was unsuccessful. If the returninformation is not an SQGL error code, report theproblem to IBM Software Support.

GPZ0627E pgm - UNSUCCESSFUL CALL TOGPZBFIND FOR SUBSYSTEM name.PROCESSING TERMINATED.

Explanation: The GPZBSQL program did notsuccessfully perform the requested function.

Message variables:

pgm The program that called the GPZBFINDprogram

name The name of the subsystem resource that isbeing processed

System action: Processing continues with the nextdefined subsystem.


GPZ0628I pgm - FINISHED PROCESSINGSUBSYSTEM name WITH RETURNCODE return_code.

Explanation: The initialization or ending process wascompleted for a DB2 subsystem.

Message variables:


name The name of the subsystem resource that isbeing processed

return_codeThe return code set by the issuing program

System action: Processing continues with the nextrelevant subsystem.

Administrator response: If the return code is 0, noaction is necessary. For return codes other than 0,analyze the log for earlier messages and take therecommended action.

GPZ0630I SUBSYSTEM name IS status; UNABLETO ISSUE COMMAND: command

Explanation: The GPZBIFIC program attempted toissue a DB2 command to a subsystem, but did not doso.

Message variables:

name The DB2 subsystem to which the commandwas directed

status The status of the DB2 subsystem:v API_ERRORv DOWNv EXCLUDEDv MAINT_MODEv NOT_MONITOREDv NOT_REGISTEREDv SSUPv UNCONTACTABLEv UNDEFINEDv UNKNOWNv UNSUPPORTED

commandThe command that was being issued


Administrator response: Note the explanation of eachstatus type and take the appropriate action as needed.

API_ERROR or NOT_REGISTEREDExamine the log that precedes this message formore detailed error messages and respond toany messages.

DOWNVerify that the DB2 subsystem successfullyinitialized before issuing the command again.

EXCLUDEDThe subsystem was defined in the GPZ$EXCLmember for exclude processing.

MAINT_MODEReport the problem to your DB2 administrator.

NOT_MONITORED or UNCONTACTABLEExamine the log that precedes this message formore detailed error messages and respond toany messages. This status is probably theresult of a configuration problem.

SSUP The subsystem is currently being processed byEvent Pump, and the final status is notdetermined. Try the command again after ashort interval to allow the process to complete.If the message occurs again, report theproblem to IBM Software Support.

UNDEFINED or UNKNOWNReport the problem to your DB2 administrator.

6 Message Reference

UNSUPPORTEDThe software level of the DB2 subsystem is notsupported by Event Pump.

GPZ0632E SUBSYSTEM name IS INCOMPATIBLE;UNABLE TO ISSUE COMMAND:command


Message variables:

name The DB2 subsystem to which the commandwas directed

commandThe command that was being issued


Administrator response: This message is probably aconfiguration error. The version, release, ormaintenance level (or any combination of these items)of the DSNALI/DSNWLI2 load module in the DB2STEPLIB statements that are used by the issuing EventPump region is incompatible with the STEPLIBstatements that are used by the specified DB2subsystem.

GPZ0636E GPZBIFIC REQUIRES AT LEASTTHREE KEYWORDS. ONLY numberRECEIVED: parameter1 parameter2


Message variables:

number The number of parameters received

parameter1The keyword parameter 1 (if specified)

parameter2The keyword parameter 2 (if specified)

System action: The command is rejected.

Administrator response: Specify the additionalparameters required and issue the command again. Ifthe GPZBIFIC program was called by a system routine,report the problem to IBM Software Support.

GPZ0637E GPZBIFIC UNABLE TO LOADDSNALI/DSNWLI2: ABEND CODEabend_code sub_code

Explanation: The GPZBIFIC program did not load theDB2 command interface module or its alias.

Message variables:

abend_codeThe abend code as returned by the LOADmacro

sub_codeThe sub code as returned by the LOAD macro

System action: The command is rejected. Event Pumpcannot communicate with any DB2 subsystems.

Administrator response: This message indicates aprobable configuration error. Follow the problemdetermination that is relevant to the abend codes andsubcodes.

GPZ0638E GPZBIFIC RETURNED AN ERRORRESPONSE AND numberLINES OFOUTPUT FOR: command

Explanation: The GPZBIFIC program issued acommand to a DB2 subsystem, which accepted thecommand but only partially processed it.

Message variables:

number The number of lines of command responsereturned by the DB2 subsystem

commandThe command being processed

System action: Command processing was completed.

Administrator response: Examine the commandresponse for the reason why the DB2 subsystem didnot fully process the command.

GPZ0639E GPZBIFIC ENCOUNTERED THE : text

Explanation: The GPZBIFIC program encountered asituation that is described in the message variable text.

Message variables:

text The variable response from the GPZBIFICprogram

System action: The command ends.

Administrator response: This message indicates aprobable system error. Report the problem to IBMSoftware Support.

GPZ0640E pgm ERROR: REQUIRE PARMS - REG|DEREG |PUSHCMD |PUSHGLOB|PULLGLOB |QUERY DSG

Explanation: The program was called with insufficientparameters.

Message variables:


System action: The program ends.

Administrator response: This message indicates aprobable system error. If the program was called by the


user, ensure that sufficient parameters are specified. Ifthe program was not called by the user, report theproblem to IBM Software Support.

GPZ0641E pgm ERROR: UNSUPPORTED PARM:parameter

Explanation: The program was called with aparameter that was not valid.

Message variables:


parameterThe parameter that was not valid


Administrator response: This message indicates aprobable system error. If the program was called by theuser, ensure that sufficient parameters are specified. Ifthe program was not called by the user, report theproblem to IBM Software Support.

GPZ0642E pgm ERROR: parameter REQUIRESSUBSYS PARAMETER: command

Explanation: The program was called with aparameter that also requires a subsystem specification.

Message variables:


parameterThe valid parameter that requires theadditional subparameter

commandA sample of a valid command


Administrator response: This message indicates aprobable system error. If the program was called by theuser, ensure that sufficient parameters are specified. Ifthe program was not called by the user, report theproblem to IBM Software Support.

GPZ0643E pgm ERROR: parameter BAD RCreturn_code ON queue_name resource_name

Explanation: The program received a return codeother than 0 from the lock function.

Message variables:

pgm The program that detected the error

parameterThe primary parameter that was passed to theGPZ$LOCK function

return_codeThe return code from the lock function

queue_nameThe queue name for locking

resource_nameThe resource name for locking

System action: The enqueue is not performed.

Administrator response: This error is probably asystem error. Report the problem to IBM SoftwareSupport.

GPZ0645E pgm ERROR: action NOT VALID: THISDOMAIN IS THE ACTIVE MONITORFOR resource


Message variables:


action The action that was requested

resource The Data Sharing Group that was specified


Administrator response: This message indicates aprobable system error. If the program was called by theuser, ensure that the correct parameters are specified. Ifthe program was not called by the user, report theproblem to IBM Software Support.

GPZ0646E pgm ERROR: action NOT DONE: NOACTIVE MONITORING DOMAINFOR resource


Message variables:


action The action requested

resource The Data Sharing Group specified


Administrator response: This message indicates aprobable system error. If the program was called by theuser, ensure that the correct parameters are specified. Ifthe program was not called by the user, report theproblem to IBM Software Support.

GPZ0647I pgm function RETURNED: response

Explanation: This message is displayed if a programlogs the response to a request.

Message variables:


function The function being that is being run

8 Message Reference

responseThe response from the program. This responseis highly variable and is for informationalpurposes only.

GPZ0648E pgm ERROR: UNABLE TOCOMMUNICATE WITH DOMAIN:name OPERATOR: operator

Explanation: The program did not issue theGTMRMTEX command to the specified domain.

Message variables:


name The remote domain

operator The operator in the remote domain

System action: The GTMRMTEX command cannot beissued. An exception in the format GZP0648_% is sent tothe relevant DB2 Data Sharing Group. Discovery andevent processing are degraded or disabled.

Administrator response: Examine the log thatprecedes the error message and respond to the errormessage or messages. Ensure that all relevant domainsthat monitor DB2 subsystems that belong to theaffected data sharing group are authorized to issue theGTMRMTEX program to each other. Ensure also thatthey have functional network connections at all times.When the error condition is corrected, the programresumes communications. See the GPZ0649I message.

GPZ0649I pgm RESUMED COMMUNICATIONSWITH DOMAIN: pgm OPERATOR:operator

Explanation: The program issued the GTMRMTEXcommand to the specified domain after a previousfailure that was identified in the GPZ0648E message

Message variables:


name The remote domain

operator The operator in the remote domain

System action: The system resolves the GPZ0648E_%exception against the relevant DB2 Data Sharing Group.

Administrator response: If the situation occurs on aregular basis, the communication links among therelevant domains might require an upgrade.

GPZ0680W THRESHOLD VALUE FOR name1 INSUBSYSTEM name2 REJECTED.DEFAULT VALUE OF number MINUTESWILL BE USED

Explanation: The interval that was specified for amonitor was unacceptable. An acceptable default wasassigned.

Message variables:

name1 The monitor name

name2 The subsystem name

number The default interval in use

System action: The monitor is set to the defaultinterval.

Administrator response: Ensure that the requestedinterval is acceptable for the specified monitor.

GPZ0681E pgm GLOBAL VARIABLE FOR name INkeyword subsys NOT FOUND

Explanation: A required Event Pump global variablewas not defined for the subsystem.

Message variables:


name The variable name

keyword A keyword indicating whether the variablebelongs to a DB2 subsystem or Data SharingGroup

subsys The subsystem or Data Sharing Group name

System action: Processing of the message ends.

Administrator response: This message indicates aprobable system error. Report the problem to IBMSoftware Support.

GPZ0684E pgm ERROR: KEYWORD keyword MUSTBE DSGNAME OR SSNAME.

Explanation: A keyword that was not valid waspassed to the program.

Message variables:

pgm The program that detected the situation.

keyword The keyword that was not valid.

System action: The command is rejected.

Administrator response: Ensure that the commandparameters are correctly specified.

GPZ0685W pgm WARNING: type name ISEXCLUDED FROM MONITORING.

Explanation: While processing an event, the programdetermined that the specified resource was excludedfrom monitoring.

Message variables:


type The type of resource

name The name of the resource

System action: Events related to the specified resource


are not processed. If the program is GPZBSSUP,discovery processing is not performed for the resource.

Administrator response: Confirm that you do notwant to monitor the resource.

GPZ0686W pgm WARNING: UNABLE TOMONITOR type name.

Explanation: The named resource is not monitored.

Message variables:



name The name of the resource

System action: Events related to the specified resourceare not processed.

Administrator response: This message is issued toalert the administrator to a potential error condition. Ifthe situation is expected, ignore this message.Otherwise, examine the related messages which werewritten to the log and respond to them.

GPZ0688E member: INVALID TOKEN tokenDETECTED IN MESSAGE message_id.MESSAGE NOT PROCESSED.

Explanation: The named resource is not monitored.

Message variables:

member The name of the REXX program issuing thismessage

token The token parsed from the incoming message

message_idThe message ID of the incoming messagecontaining the token that was not valid

System action: Processing continues and the incomingmessage is ignored. No event is created.

Administrator response: If you do not want tomonitor this message, remove all references to it.Otherwise, notify IBM Software Support of this error.

GPZ0689E pgm UNABLE TO PARSE RESPONSEvar_1 var_2 var_3 var_4 var_5

Explanation: The named program did not parse theresponse to a command or query

Message variables:


var_1 through var_5The summary information describing theparsed response

System action: The program performs additional errorrecovery.

Administrator response: Examine the log thatprecedes the error message for more detailed messages.If there are no additional error messages, contact IBMSoftware Support.

GPZ0710I LOADING GPZ$EXCL SINCE IT ISNOT CURRENTLY LOADED

Explanation: This message is displayed when theGPZ$EXCL member is loaded from the GTMMON DDdata set for the first event that matches the Excluderules that were generated since the source collectorstartup.

GPZ0711I GPZ#EXCL VALID OPTIONS ARE:options

Explanation: This multiline message results when theGPZ#EXCL command is issued with an option that isnot valid.

Message variables:

optionsSHOW Shows the current loaded filter and

statisticsREFRESH

Refreshes the filter from theGPZ$EXCL DSIPARM member

CHECKChecks the type, resource name, andevent ID

Administrator response: Enter the command againwith a valid option.

GPZ0712E RESOURCE_TYPE type IS NOTSUPPORTED.

Explanation: This message is issued when anunsupported resource_type is specified in theGPZ$EXCL member, or in the GPZ#EXCL CHECKcommand.

Message variables:


Administrator response: See the GPZ$EXCLGTMMON member for a list of supported resourcetypes.

GPZ0714I GPZ$EXCL GTMMON HAS NOFILTERS FOR SYSNAME sys_name

Explanation: This message is issued when theGPZ#EXCL SHOW command is used and no filters areactive for this system.

Message variables:

sys_nameThe z/OS system name

Administrator response: If this message is

10 Message Reference

unexpected, review the GPZ$EXCL GTMMON member.Issue the GPZ#EXCL REFRESH command to load theGPZ$EXCL member from the GTMMON DD data set.

GPZ0715I GPZ$EXCL WAS LOADED date timeFROM dsn

Explanation: This message is issued when theGPZ#EXCL SHOW command is used. The currentloaded filters and statistics are also listed as part of thismultiline message.

Message variables:

date The date that the GPZ$EXCL member wasloaded from the DSIPARM DD

time The time that the GPZ$EXCL member wasloaded from the DSIPARM DD

dsn The DSN where the GPZ$EXCL member wasloaded

GPZ0716E VALID PARMS ARE: Resource_TypeResource_Name {Event_ID}

Explanation: The GPZ#EXCL CHECK command wascalled with incorrect parameters. The followingparameters are valid:

Resource_Type(Required) Valid resource type as documentedin the GPZ$EXCL SGTMSAMP member

Resource_Name(Required) The name of the resource

Event_ID(Optional) The ID of the event

For more information about the parameters, see theGPZ$EXCL sample in the SGTMSAMP data set. Theseexamples show the correct GPZ#EXCL CHECK calls:

* GPZ#EXCL CHECK DBSS DB6A* GPZ#EXCL CHECK IMPG PGM1 DFS1234

Administrator response: If this message is a responseto a user command, enter the command again withvalid parameters. If not, contact IBM Software Support.

GPZ0724I DISCOVERY REQUEST FOR resourceHAS BEEN ACCEPTED.

Explanation: The system accepted a request todiscover a resource.

Message variables:

resourceThe resource that is discovered.

System action: Discovery operates asynchronously.Requests to perform discovery are first validated andthen queued for processing. This process enables theconsole to be used for other processing while thediscovery continues.

Administrator response: If a request was acceptedand queued, but not completed, examine the log forrelated error messages and respond to them.

GPZ0750I OUTPUT DISPLAY FOLLOWS:

Explanation: This message is issued as a headermessage that precedes the display of data from anEvent Pump process. This message is preceded byanother Event Pump error or informational message.


Administrator response: Review the data that followsthis message, together with any relevant previousmessages, and perform any action as required.

GPZ0751I COMMAND IN module_name TIMEDOUT

Explanation: The module_name routine received noresponse from an attempt to issue a command toanother subsystem

Message variables:

module_nameThe name of the module

Administrator response: Contact IBM SoftwareSupport.

GPZ0817I module disc_type REDISCOVERYSTARTING FOR resource_typeresource_name (FROM datetime).

Explanation: The named routine started rediscovery ofthis resource.

Message variables:

module The name of a module that is performing therediscovery.

disc_typeThe type of discovery, which is either FULL orPARTIAL.

resource_typeThe type of resource being rediscovered.

resource_nameThe name of the resource being rediscovered.

datetimeFor partial rediscoveries, resources that aremodified or added only after this date andtime are rediscovered. For full rediscoveries,this variable is not displayed.

System action: Rediscovery of this resource continues.


GPZ0829I (module) feed_name REDISCOVERY FORname DEFERRED.

Explanation: The installation specified thatrediscovery be deferred.

Message variables:

module The name of the module

feed_nameThe name of the Event Pump data resource.For example, DB2 systems

name The name of the DB2 subsystem beingrediscovered

System action: The scope of the rediscovery isreduced and processing continues.

Administrator response: None

GPZ3010E required KEYWORD REQUIRED

Explanation: A required keyword in the ZEVENTblock was not entered.

Message variables:

required USRMASK

System action: Processing stops and no event isgenerated.


GPZ3030E PROCESSING FAILED RC=return_codeMSG=message

Explanation: Processing of the ZEVENT block for thistrap entry failed. The return code identifies the majorfunction and the specific return code causing the error.

Message variables:

return_codeReturn code that caused this event processingto stop.

message The text of the message being processed.

System action: Processing stops and no event isgenerated.


GPZ3031I TRAP type - value

Explanation: Information message that is displayedwith other error messages. The type of information andthe value is displayed.

Message variables:

type Types of variables for the trap:ZEVENT

The ZEVENT block definitionsSET VARIABLES

Variables pasted to the trap

USER VARIABLESUSER9X fields set for this trap

value The value of the variable list in type.

System action: Processing stops, and no event isgenerated.


GPZ3040E REQUIRED DATA MISSING ORINVALID

Explanation: The information passed to thecustomizer from the monitor registration does notinclude the required information. This error can occur ifthe customizer was called outside of the standardregistration process.


Administrator response: If the customizer was calledfrom the registration process, contact IBM SoftwareSupport.

GPZ3041E keyword KEYWORD INVALID

Explanation: The keyword is invalid on the user call.This error can occur if the customizer was calledoutside of the standard registration process.

Message variables:

keyword The name of the keyword on the MONITORregistration entry that is in error:

MONITOR TYPENUMBER VALUEDEBUG


Administrator response: If the customizer was calledfrom the registration process, contact IBM SoftwareSupport.

GPZ3042E NO DATA FOUND FOR COMMAND

Explanation: Additional required information ismissing from the REQUEST variable.


GPZ3043E keyword INVALID SYNTAX

Explanation: Invalid syntax was found for the keywordon the user call.

Message variables:

keyword The name of the keyword on the MONITORregistration entries that are in error:

FORMATACTIONDEBUG




GPZ3044E SUBSTITUTION LOOP COUNTEXCEEDED

Explanation: The substitution process tried 5 times toresolve the variables.

System action: The substitution ended.

Administrator response: Ensure that the variablenames are correct. Correct the variable names andunregister and register the registration entry.

GPZ3045W CANNOT RESOLVE SUBSTITUTIONVARIABLE variable IN TRAP trap_name

Explanation: Variable variable cannot be located forsubstitution.

Message variables:

variable The variable that cannot be resolved.

trap_nameThe trap containing the error.


Administrator response: Verify that the ZEVENTblock contains valid variable names for substitution.

GPZ3046E NAME OF THE SUBSTITUTIONVARIABLE variable EXCEEDSMAXIMUM SIZE

Explanation: The name of the variable exceeds themaximum length of 16 characters.

Message variables:

variable The name of the variable in error.


Administrator response: Correct the variable name toa length of 16 or less.

GPZ3047E VALUE OF THE SUBSTITUTIONVALUE variable_name EXCEEDSMAXIMUM SIZE

Explanation: The value of the variable exceeds themaximum length of 80 characters.


Administrator response: Correct the variable name toa length of 80 or less. An additional variable might berequired.

GPZ3048E UNABLE TO OBTAIN BUFFERSTORAGE FOR storage_area RETURNCODE = return_code

Explanation: Storage cannot be obtained for thespecified area.

Message variables:

storage_areaThe name of the storage area for whichstorage is to be obtained:v CELL BUFFERv RETURN VALUEv USERxx PARAMETERv VARIABLE PARAMETERv VARIABLE POOLv WORKAREA

return_codeReturn code from the request



GPZ3049E CANNOT RESOLVE trap_data FOROBJECT

Explanation: The customizer cannot retrieve thespecified trap information.

Message variables:

trap_dataThe name of the trap data variable that cannotbe retrieved:

JOB TYPEMESSAGETRAP NAME



GPZ3050E INVALID KEYWORD: syntax_desc FORTRAP trap_name

Explanation: The syntax processing identified aninvalid keyword

Message variables:

syntax_descAdditional information from the syntax callrelating to the error

trap_nameThe trap containing the error




GPZ3051E INVALID OPTION: syntax_desc FORTRAP trap_name

Explanation: The syntax processing identified aninvalid option.

Message variables:





GPZ3052E INVALID STATE: syntax_desc FORTRAP trap_name

Explanation: The syntax processing identified aninvalid state.

Message variables:





GPZ3053E KEYWORD CONFLICT: syntax_desc FORTRAP trap_name

Explanation: The syntax processing identifiedconflicting keywords.

Message variables:





GPZ3054E CONFLICTING OPTION: syntax_descFOR TRAP trap_name

Explanation: The syntax processing identifiedconflicting options.

Message variables:





GPZ3055E MISSING KEYWORD: syntax_desc FORTRAP trap_name

Explanation: The syntax processing identified amissing keyword.

Message variables:





GPZ3056E MISSING OPERAND: syntax_desc FORTRAP trap_name

Explanation: The syntax processing identified amissing operand.

Message variables:






GPZ3057E NON_NUMERIC DATA: syntax_descFOR TRAP trap_name

Explanation: The syntax processing identifiednon-numeric data.

Message variables:





GPZ3058E SYNTAX ERROR: syntax_desc FORTRAP trap_name

Explanation: The syntax processing identified a syntaxerror.

Message variables:





GPZ3060E PREDEFINED VARIABLE variable_nameCANNOT BE SET, REQUESTIGNORED

Explanation: The name used in the SET command is areserved predefined variable name.

Message variables:

variable_nameThe name of the predefined reserved variable

System action: The request is ignored.

Administrator response: Ensure that the variablenames are correct. Correct the variable names andunregister and register the registration entry.

GPZ3061E ERROR OCCURRED FOR KEYWORDkeyword

Explanation: An error occurred processing keywordkeyword. Additional messages are displayed foradditional information about the error.

Message variables:

keyword The name of the keyword that caused theerror to occur. Additional messages detail theerror.


Administrator response: Correct the ZEVENTkeyword and register the monitoring.

GPZ3062W SEVERITY NOT SET, USING DEFAULTSEVERITY MINOR FOR TRAPtrap_name

Explanation: Severity was not set; the default severityof MINOR is used.

Message variables:


System action: Processing continues; the defaultseverity is used.


GPZ3063W INVALID SEVERITY DEFINED severity,USING DEFAULT SEVERITY MINORFOR TRAP trap_name

Explanation: An invalid severity was set to asubstitution that is invalid.

Message variables:

severity The severity that is invalid

trap_nameThe trap containing the error.

System action: Processing continues, the defaultseverity is used.

Administrator response: Correct the SEVERITYkeyword or verify that the value of the substitution is avalid severity.

GPZ3064W MESSAGE TEXT: message_text

Explanation: Message text is displayed for additionalinformation that is related to another error message.The GPZ0365I message is also displayed.

Message variables:

message_textThe message text that is being processed




GPZ3065W MESSAGE MASK: message_mask

Explanation: Message mask is displayed for additionalinformation related to another error messages. TheGPZ0364I message is also displayed.

Message variables:

message_maskThe mask that is to be used to parse the inputmessage



GPZ3066E END OF STRING ENCOUNTEREDUSING MESSAGE MASK

Explanation: All of the mask tokens were processed,but additional message text was not processed. TheGPZ0364I and GPZ3065I messages are also displayed.



GPZ3067E NO MATCH IN MESSAGE FORLITERAL search_string

Explanation: The literal in the mask does not matchthe literal in the message text. The GPZ0364I andGPZ3065I messages are also displayed.

Message variables:

search_stringThe text that does not match within themessage text



GPZ3068E MISMATCH OF SCAN ITEMS ANDMESSAGE TEXT

Explanation: The message text was processed, butadditional mask tokens were not processed. TheGPZ0364I and GPZ3065I messages are also displayed.



GPZ3069E FORMAT %S+ MISSING REQUIREDNUMBER OF CONSTANTS

Explanation: The mask for this trap has %S+ butmatching of the mask tokens determined that there is anull string. %S+ requires at least one message token fora successful match. The GPZ0364I and GPZ3065I

messages are also displayed. For information about %S+and other component specifiers, see the Event Pump forz/OS Installation and Configuration Guide.



GPZ5700I SOURCE MANAGER STARTED

Explanation: The source manager started during theEvent Pump initialization process.



GPZ5701I SOURCE MANAGER STOPPED

Explanation: The source manager stopped during theEvent Pump end process.



GPZ5702I JOBLOG JES monitor started forjobname.ddname SPOOL DD

Explanation: Monitoring of the specified spool DDdata set started.

Message variables:

jobname The Job name that the user specified formonitoring

ddname The DD name that the user specified formonitoring



GPZ5703I JOBLOG JES MONITOR STOPPEDFOR jobname.ddname SPOOL DD

Explanation: Monitoring of the specified spool DDdata set stopped.

Message variables:

jobname The job name that the user specified formonitoring

ddname The DD name that the user specified formonitoring




GPZ5704E SOURCE MANAGER NOT STARTED

Explanation: The user requested the source managerfor an action, but the source manager is not started.

System action: Processing continues, but the requestedtask failed.

Administrator response: Contact IBM SoftwareSupport for more instructions.

GPZ5705E ALLOCATION FAILED FORjobname.ddname SPOOL DD

Explanation: Allocation of a specified spool DD dataset failed.

Message variables:


ddname The name of the DD data set that the userspecified for monitoring

System action: The JOBLOG monitor task stopped.


GPZ5706E DEALLOCATION FAILED FORjobname.ddname SPOOL DD

Explanation: Deallocation of the specified spool DDdata set failed.

Message variables:





GPZ5707E I/O INITIALIZATION FAILED FORjobname.ddname SPOOL DD

Explanation: The specified spool DD data set failed toopen.

Message variables:





GPZ5708E ERROR READING jobname.ddnameSPOOL DD

Explanation: An error occurred while reading a recordfrom the specified spool DD data set.

Message variables:





GPZ5709E I/O TERMINATION FAILED FORjobname.ddname SPOOL DD

Explanation: The specified spool DD data set failed toclose.

Message variables:





GPZ5710I JOBLOG DID NOT FIND ACTIVE JOBIN COMPLIANCE WITH SPECIFIEDCRITERIA FOR jobname.ddname SPOOLDD

Explanation: The JOBLOG monitor task tried to findthe active jobs that the user specified for monitoring,but no spool DD data set matches the specified filter.

Message variables:





GPZ5711I JOBLOG ALREADY MONITOREDSPECIFIED jobname.ddname SPOOL DD

Explanation: The user requested that the JOBLOGmanager monitor a specified spool DD data set, butthis DD data set was already monitored.

Message variables:






GPZ5712E JOBLOG FAILED FOR SPECIFIEDjobname.ddname SPOOL DD

Explanation: The JOBLOG manager failed to process auser request for a specified spool DD data set.

Message variables:



System action: The user task fails, and the JOBLOGmanager continues.


GPZ5713I JOBLOG DID NOT MONITORSPECIFIED jobname.ddname SPOOL DD

Explanation: The user requested that the JOBLOGmanager manipulate a particular spool data set, but theJOBLOG manager did not find the specified spool dataset in its list of monitored spool data sets.

Message variables:





GPZ5714E SYNTAX ERROR FOR parmPARAMETER IN JOBLOG CARD: card

Explanation: A syntax error was found for theindicated parameter in the specified JOBLOGstatement.

Message variables:

parm The JOBLOG statement parameter

card The JOBLOG statement


Administrator response: Ensure that the indicatedparameter has the correct format.

GPZ5715I MONITORING STARTED FORSOURCE source, COUNT=count, RC=rc

Explanation: Monitoring was started for the specifiedsource. The monitored information includes optionalstatistics from the specified source.

Message variables:

source Source type

count Total number of messages registered from aconfiguration member for the specified sourcetype

rc Maximum return code for the specified sourcetype


Administrator response: None.

GPZ5716I MONITORING STOPPED FORSOURCE source

Explanation: Monitoring was stopped for the specifiedsource.

Message variables:

source Source type



GPZ5801I HEALTH CHECKER IS ACTIVE,MONITORING HAS RESUMED

Explanation: The Health Checker product is startedand is detected by Event Pump; monitoring starts.



GPZ5802I HEALTH CHECKER IS NOT ACTIVE,MONITORING HAS BEENSUSPENDED

Explanation: Event Pump detected that the HealthChecker function is not active.

System action: Processing is suspended until theHealth Checker function starts.


GPZ5803I HEALTH CHECKER MONITORSTARTED

Explanation: The Health Checker monitor is started.




GPZ5804I HEALTH CHECKER MONITORSTOPPED

Explanation: The Health Checker monitor is stopped.



GPZ5805I HEALTH CHECKER MONITORALREADY STARTED

Explanation: The Health Checker monitor is alreadystarted.

System action: Processing continues, and the startrequest is ignored.


GPZ5806I HEALTH CHECKER MONITORALREADY STOPPED

Explanation: The Health Checker monitor is alreadystopped.

System action: Processing continues, and the stoprequest is ignored.


GPZ5807E HEALTH CHECKER REQUEST FAILEDmessage

Explanation: The source manager failed to process aclient request for the Health Checker function.

message Additional message text, if available

System action: The client task fails, and the sourcemanager continues processing.


GPZ5808E UNABLE TO ESTABLISH ENFLISTENER FOR HEALTH CHECKERRC=rc

Explanation: The Health Checker monitor cannot setup a listener for ENF events.

Message variables:

rc The return code from the ENFREQ LISTENmacro




Chapter 2. GTM prefix messages

The GTM prefix messages are issued by the components that make up the serviceson a z/OS mainframe system. These messages include the source collector, eventdistributor, and data space.

Some of the messages are issued from other address spaces that use thecomponents.

GTM0001I ITZP INITIALIZATION STARTED datetime

Explanation: The application level code within thesource collector started initialization.

Message variables:

date The current date

time The current time


GTM0002I SYSTEM WAS IPL'D ON date1 date ATtime

Explanation: The source collector displays the dateand time of the last initial program load of the system.

Message variables:

date1 The date in the form mm/dd/yyyy

date The date in the form mmddyy

time The time in the form hh:mm:ss


GTM0003I ITZP IS RUNNING ON SYSTEM smfid

Explanation: The source collector displays the SMFIDof the system on which it is running.

Message variables:

smfid The system identifier (SMFID) of the MVS™

image on which the source collector is running


GTM0008E ITZP INITIALIZATION FAILED.PLEASE SEE SYSLOG. REPLY 'OK' TOTHIS MESSAGE.

Explanation: An error occurred during sourcecollector initialization. A previous message describesthe cause of the failure.

System action: The source collector stops.

User response: Reply OK to the outstanding WTORmessage. Contact the administrator.

Administrator response: Check the messages in thesystem log to resolve the cause of the error. Restart thesource collector.

GTM0009E ITZP INITIALIZATION ISTERMINATED. TERMINATIONRETURN CODE = return_code

Explanation: An error occurred during sourcecollector initialization. A previous message describesthe cause of the failure.

Message variables:

return_codeThe return code from the function that failed


Administrator response: Reply OK to the outstandingWTOR message. Contact the administrator.


GTM00010E error_text

Explanation: An error occurred and the text of themessage describes the error. The source collector cannotdetermine the event distributor state or cannot querythe parameter variable that is indicated.

Message variables:

error_textThe text is one of these messages:

v UNABLE TO DETERMINE SERVER STATE

v UNABLE TO QUERY PARAMETERparm_variable


Administrator response: Check the messages in thesystem log to resolve the cause of the error. Restart thesource collector. If the error continues, contact IBMSoftware Support.

GTM0100I INVALID VALIDATION TYPE: value

Explanation: The validation value of the PARM_VAL.n


startup parameter was incorrectly coded.

Message variables:

value The validation value from the PARM_VAL.nstartup parameter



GTM0101I FOR PARAMETER : parameter

Explanation: This message is a continuation of theGTM0100I message.

Message variables:

parameterThe parameter name that is in error


Administrator response: See the GTM0100I message.

GTM0104I INVALID OBJECT TYPE ID typePASSED TO pgm AT INITIALIZATION

Explanation: An invalid object type was received fromthe Windows system in the global shared variableregistration data. Valid object types are as follows:

ENT Defines the global variable for the enterprise

COMP Defines the global variable for the complex

LPAR Defines the global variable for the LPAR

MACH Defines the global variable for the system

OS Defines the global variable for the operatingsystem

Message variables:

type The object ID that was not valid

pgm The program name of the global sharedvariable registration data



GTM0108E SEVERE ERROR RESETTING SHAREDVARIABLE POOL, RC = return_code

Explanation: The deletion of all initialization-sharedvariables did not successfully complete. Additionalinformation is in this message.

Message variables:

return_codeThe return code from the shared variabledelete operation



GTM0109E SHARED VARIABLE POOL MAYBEUNUSABLE

Explanation: This message is a continuation of theGTM0108E message.



GTM0110E ERROR WRITING SHAREDVARIABLE variable_name IN pgm

Explanation: An error occurred writing the sharedvariable program to the global pool. See the GTM0111Emessage.

Message variables:

variable_nameThe name of the variable that is being written

pgm The name of the program that is writing thevariable


Administrator response: Check the messages in thesystem log and the AOPxxLOG system log to see whythe function failed. Resolve the cause of the error andrestart the source collector. Contact IBM SoftwareSupport.

GTM0111E RC = return_code INITIALIZATIONPROCESSING HAS BEENTERMINATED

Explanation: This message displays the return codefrom the error that is described by the GTM0110Emessage. If the return code is 16, an error message isdisplayed in the AOPOUT error message log.

Message variables:

return_codeThe return code from the error described bythe GTM0110E message




GTM0112E ERROR READING SHAREDVARIABLE variable_name IN pgm

Explanation: An error occurred reading the sharedvariable from the global pool.

Message variables:

variable_nameThe name of the variable that is being read

pgm The name of the program that is reading thevariable




Explanation: This message displays the return codefrom the error that is described by the GTM0112Emessage. If the return code is 16, an error message isdisplayed in the AOPOUT error message log.

Message variables:

return_codeThe return code of the error described by theGTM0112E message



GTM0116E ERROR PROCESSING SYSTEMVARIABLE variable_name IN pgm

Explanation: An error occurred setting the@ACLOGSW global variable while processing a SETLOG ON or SET LOG OFF command. See theGTM0117E message.

Message variables:


pgm The name of the program that is reading thevariable

System action: Processing of the command stops.

Administrator response: Look in the source collectorjob log and the AOPxxLOG system log output forrelated messages that might indicate why the functionfailed. Contact IBM Software Support.

GTM0117E PROCESSING HAS BEENTERMINATED

Explanation: Processing ended for the SET LOG ONor SET LOG OFF command. This message follows theGTM0116E message.

System action: Processing of the command stops.


GTM0120E VALIDITY CHECK FAILED FORPARM: object_type IN pgm

Explanation: During initialization, the SMFID valueand the operating system name in the parameter filedid not agree. Additional information can be found inthe GTM0121E, GTM0122E, GTM0123E, or GTM0124Emessages.

Message variables:

object_typeThe object type, for example, an operatingsystem

pgm The REXX initialization program

System action: Processing of the command mightstop. The GTM0123E message or the GTM0124Imessage indicates the action of the source collector.

Administrator response: Correct the member in theparameter file and restart the source collector.

GTM0121E DATASET NAME IS dataset_name

Explanation:

Message variables:

dataset_nameThis message is a continuation of theGTM0120E message.

Administrator response: See the GTM0120E message.

GTM0122E PARM FILE VALUE IS: smfid_parm,SYSTEM VALUE IS: smfid


Message variables:

smfid_parmThe SMFID value in the parameter file

smfid The SMFID value from the system variable


Chapter 2. GTM prefix messages 23

GTM0123E PROCESSING HAS TERMINATED



GTM0124I PROCESSING IS CONTINUING



GTM0130E VALIDITY CHECK FAILED FORPARM: parameter IN pgm

Explanation: Indicates that the data for the sourcecollector startup parameter is not in the correct format.See the GTM0131E message.

Message variables:

parameterThe name of the parameter

pgm The name of the program reading theparameter


Administrator response: Check the messages in thesystem log to resolve the cause of the error. Restart thesource collector. If the error continues, contact IBMSoftware Support

GTM0131E PARM VALUE IS: data, ERROR IS:error_text

Explanation: This message is a continuation of theGTM0130E message and displays the parameter dataand reason for the error.

Message variables:

data The data that is in error

error_textThe description of the error


Administrator response: Check the messages in thesystem log. Resolve the cause of the error and restartthe source collector. If the error continues, contact IBMSoftware Support.

GTM0200E INVALID RETURN CODE FROM pgm -FUNCTION = function, RETURN CODE= return_code, CALLER = caller_pgm

Explanation: The GTMRX014 REXX exec returned areturn code that was not valid during source collectorinitialization or shutdown. The GTMRX014 program isstarted during log on processing of the 3270OMEGAMON® sessions.

Message variables:

pgm The GTMRX014 program

function The OBJSRV function

return_codeThe return code from the GTMRX014 program

caller_pgmThe REXX exec which called the GTMRX014program

Administrator response: Check the AOPxxLOGsystem log and the AOPOUT error message log for anymessages that might indicate why the logon or logoffprocessing programs returned an error. Resolve thecause of the error and try establishing the sessionagain. If the error continues, contact IBM SoftwareSupport.

GTM0210E AN ERROR error_type OCCURRED INPROGRAM pgm ON LINE: error_line

Explanation: A runtime error occurred in theGTMRX014 REXX exec. This error occurred during thelogon or logoff processing of a 3270 OMEGAMONsession.

Message variables:

error_typeThe type of error


error_lineThe line number of the REXX exec that causedthe error

System action: Processing continues. TheOMEGAMON session manager is not initialized.

Administrator response: Check the AOPxxLOGsystem log and the AOPOUT error message log for anymessages that might indicate why the GTMRX014program returned an error. Resolve the cause of theerror and try to establish the session again. If the errorcontinues, contact IBM Software Support.

GTM0211E THE SOURCE LINE IS: error_text

Explanation: Displays the source line associated withthe error described by the GTM0210E message.

Message variables:

error_textThe source line in the GTMRX014 REXX execwhere the error occurred

System action: Processing continues. TheOMEGAMON session manager is not initialized.

Administrator response: Check the AOPxxLOGsystem log and the AOPOUT error message log for anymessages that might indicate why the GTMRX014program returned an error. Resolve the cause of the


error and try to establish the session again. If the errorcontinues, contact IBM Software Support.

GTM0220I ITZP LOGON PROCESSINGINITIALIZATION STARTED

Explanation: The source collector is startingprocessing of OMEGAMON 3270 sessions.


GTM0222E INVALID LOGON TYPE SPECIFIED:

Explanation: The source collector received a sessiontype that was not valid while attempting to establish a3270 OMEGAMON session.

System action: Processing continues. The session isnot connected.

Administrator response: See the GTM0223E message,which describes the parameters that are not valid.Determine why the invalid session type was sent forthe logon request. Resolve the cause of the error andtry to establish the session again. If the error continues,contact IBM Software Support.

GTM0223E TYPE = session_type, NAME =session_name, APPLID = applid

Explanation: Describes the invalid session parametersthat were received by the source collector from theWindows system. See the GTM0222E message.

Message variables:

session_typeThe type of session received

session_nameThe name of the session

applid The VTAM® application ID of the targetapplication


Administrator response: Determine why an invalidsession type was sent for the logon request. Resolve thecause of the error and try to establish the session again.If the error continues, contact IBM Software Support.

GTM0225E BAD RETURN CODE FROM LOGONREQUEST, RC = return_code

Explanation: A logon request to a 3270 applicationfailed.

Message variables:

return_codeThe return code from the logon request

System action: Processing continues. The sourcecollector did not log on to an OMEGAMON session.

Administrator response: See the GTM0226E messagefor more information about the logon request.Determine why the logon request might have failed.For example, the OMEGAMON monitor might not beactive. Resolve the cause of the error and try toestablish the session again.

GTM0226E TYPE = session_type, NAME =session_name, APPLID = applid

Explanation: Displays the session type, the sessionname, and the VTAM application ID that failed to logon.

Message variables:

session_typeThe type of session received


applid The VTAM application ID of the targetapplication


Administrator response: Refer also to the GTM0225Emessage. Determine why the logon request might havefailed. For example, the OMEGAMON monitor mightnot be active. Resolve the cause of the error and try toestablish the session again.

GTM0228E ERROR action SHARED VARIABLEvariable_name IN pgm RC = return_code

Explanation: An error occurred retrieving or setting aglobal shared variable. This message is issued duringthe logon or logoff processing of a 3270 OMEGAMONsession.

Message variables:

action The action, which is either setting or gettingthe variable

variable_nameThe variable name

pgm The name of the program issuing the message

return_codeThe return code from the variable service


Administrator response: Check the AOPxxLOGsystem log and the AOPOUT error message log for anymessages that might indicate this failure. Resolve thecause of the error and restart the source collector. If theerror continues, contact IBM Software Support.


GTM0236I ITZP SESSION LOGOFF PROCESSINGaction

Explanation: Logoff processing started or ended for a3270 OMEGAMON session.

Message variables:

action The action, which is either started or ended


GTM0238I BAD RETURN CODE FROM LOGOFFREQUEST, RC = return_code

Explanation: Logoff processing for a 3270OMEGAMON session failed.

Message variables:

return_codeThe return code from the logoff request


Administrator response: See the GTM0239I messagefor more information about the session that receivedthe error. Check the AOPxxLOG system log and theAOPOUT error message log for any messages thatmight indicate why the logoff processing failed.Resolve the cause of the error and try logging on andoff the same session again. If the error continues,contact IBM Software Support.

GTM0239I SESSION ID = session_name, TYPE =session_type - SESSION might NOTHAVE BEEN ACTIVE

Explanation: This message displays additionalinformation about the logoff failure that is displayed bythe GTM0238I message.

Message variables:

session_nameThe session ID name

session_typeThe type of session


Administrator response: Check the AOPxxLOGsystem log and the AOPOUT error message log for anymessages that might indicate why the logoff processingfailed. Resolve the cause of the error and try logging onand off the same session again. If the error continues,contact IBM Software Support.

GTM0240E INVALID FUNCTION function PASSEDTO pgm

Explanation: The GTMRX014 REXX exec was passed afunction that was not valid.

Message variables:

function The function that was passed to theGTMRX014 REXX exec

pgm The GTMRX014 REXX exec

System action: Processing continues. The sourcecollector session manager is not initialized.

Administrator response: Collect messages from thesystem log and the AOPxxLOG system log. ContactIBM Software Support.

GTM0241E VALID FUNCTIONS ARE START,STOP, QUERY, LOG ON, LOG OFF

Explanation: This message is a continuation of theGTM0240E message and lists the valid functions thatcan be passed to the GTMRX014 REXX exec.

System action: Processing continues. The sourcecollector session manager is not initialized.

Administrator response: Collect messages from thesystem log and the AOPxxLOG system log. ContactIBM Software Support.

GTM0242I SESSNAME TYPE APPLID INTERVALSTATUS

Explanation: This message is part of a multilinemessage from the QUERY LOGONS command.


GTM0243I session_name, session_type, applid, interval,session_status


Message variables:

session_nameThe session name

session_typeThe session type

applid The VTAM application ID

interval The polling interval in the format hh:mm:ss

session_statusThe session status


GTM0244I session_count SESSIONS LISTED


Message variables:

session_countThe number of sessions listed by the command



GTM0246E CONNECTION TO OMEGAMON HASFAILED

Explanation: A 3270 session to an OMEGAMONapplication failed.


Administrator response: See the GTM0247E messagefor details of the session that failed. The OMEGAMONmonitor might have shut down. Check the messages inthe system log and the AOPxxLOG system log todetermine why the session might have failed. Resolvethe cause of the error and try to establish theconnection again.

GTM0247E SESSION NAME = session_name,SESSION TYPE = session_type

Explanation: Displays information about the failed3270 OMEGAMON session.

Message variables:

session_nameThe session name

session_typeThe session type


Administrator response: The OMEGAMON monitormight have shut down. Check the messages in thesystem log and the AOPxxLOG system log todetermine why the session might have failed. Resolvethe cause of the error and try to establish theconnection again.

GTM0300I INVALID RETURN CODE FROM@AEVNTMG - RETURN CODE =return_code

Explanation: The GTMRX013 REXX exec issued areturn code other than 0 during source collector startupor shutdown.

Message variables:

return_codeThe return code received from the GTMRX013REXX exec

System action: The source collector is not ready toprocess events.

Administrator response: Review the console, theAOPxxLOG system log, and the AOPOUT errormessage log logs for any messages that might indicatewhy the function failed.

If the error occurred during startup, you might have torestart the source collector.

If the error occurred during shutdown, you might have

to issue the STOP command again to stop the sourcecollector.

If the error continues, contact IBM Software Support.

GTM0400I INVALID RETURN CODE FROM@ACCCMDS - RETURN CODE =return_code

Explanation: During source collector initialization orshutdown, the REXX command processor issued areturn code other than 0.

Message variables:

return_codeThe return code received from the GTMRX003REXX exec

System action: Processing continues. The commandfacility is not started.

Administrator response: Check the messages in theAOPxxLOG system log and the AOPOUT errormessage log. Resolve the cause of the error and restartthe source collector. If the error continues, contact IBMSoftware Support.


Explanation: A runtime error occurred in theGTMRX004 REXX exec. The error occurred duringsource collector initialization.

Message variables:




System action: Processing continues. The sourcecollector is not available.

Administrator response: Check the AOPxxLOGsystem log and the AOPOUT error message log for anymessages that might indicate why the GTMRX004program returned an error. Resolve the cause of theerror and restart the source collector. If the errorcontinues, contact IBM Software Support.



Message variables:

error_textThe source of the line in error


System action: Processing continues. The sourcecollector is not available.

Administrator response: Check the AOPxxLOGsystem log and the AOPOUT error message log for anymessages that might indicate why the GTMRX004program returned an error. Resolve the cause of theerror and restart the source collector. If the errorcontinues, contact IBM Software Support.

GTM0990I ITZP INITIALIZATION COMPLETED

Explanation: The source collector initializationcompleted. The source collector is ready to processregistration data from the Windows system.


GTM1001I ITZP EVENT MANAGERINITIALIZATION STARTED

Explanation: Event manager initialization started.



Explanation: An error occurred in the event managerGTMRX013 REXX exec.

Message variables:




System action: Processing continues. The sourcecollector is not available to process events.

Administrator response: Check the AOPxxLOGsystem log and the AOPOUT error message log for anymessages that might indicate why the GTMRX013program failed. Resolve the cause of the error andrestart the source collector. If the error continues,contact IBM Software Support.



Message variables:

error_textThe source of the line in the GTMRX013 REXXexec where the error occurred


Administrator response: Check the AOPxxLOG

system log and the AOPOUT error message log for anymessages that might indicate why the GTMRX013program failed. Resolve the cause of the error andrestart the source collector. If the error continues,contact IBM Software Support.

GTM1030E ERROR GETTING SHAREDVARIABLE variable_name IN pgmRC=return_code

Explanation: An error occurred while retrieving theglobal variable name in the program.

Message variables:

variable_nameThe name of the variable that is beingretrieved

pgm The name of the program that is issuing themessage

return_codeThe return code from the GBLVGET function


Administrator response: Check the AOPxxLOGsystem log and the AOPOUT error message log for anymessages that might be related to this error. Verify thatthe variable name by issuing the source collectorSHOW VARS command. Resolve the cause of the errorand restart the source collector. If the error continues,contact IBM Software Support.

GTM1050E INVALID FUNCTION function PASSEDTO GTMRX013

Explanation: The GTMRX013 REXX exec was calledwith a function that was not valid.

Message variables:

function The name of the function


Administrator response: Check the AOPxxLOGsystem log and the AOPOUT error message log for anymessages that might be related to this error. If the errorcontinues, contact IBM Software Support.

GTM1051E VALID FUNCTIONS ARE START,STOP, QUERY

Explanation: This message is a continuation of theGTM1050E message and lists the valid functions thatcan be passed to the GTMRX013 REXX exec.


Administrator response: Check the AOPxxLOGsystem log and the AOPOUT error message log for any


messages that might be related to this error. If the errorcontinues, contact IBM Software Support.

GTM1060E INVALID SUBFUNCTION PASSED TOGTMRX013

Explanation: A subfunction that was not valid waspassed to the GTMRX013 REXX exec. See theGTM1061E message, which lists the function andsubfunction routine names.



GTM1061E FUNCTION=function SUBFUNCTION=subfunction

Explanation: This message is a continuation of theGTM1060E message and lists the function andsubfunction passed to the GTMRX013 REXX exec.

Message variables:

function The name of the function

subfunctionThe name of the subfunction



GTM1591I ITZP EVENT MANAGERTERMINATING

Explanation: The source collector is shutting down inresponse to a STOP command.



Explanation: An error occurred in the REXX execspecified in the program.

Message variables:

error_typeThe error type

pgm The name of the program issuing the message



Administrator response: Check the AOPxxLOGsystem log and the AOPOUT error message log for anymessages that might indicate why the error occurred.Resolve the cause of the error and restart the sourcecollector. If the error continues, contact IBM SoftwareSupport.



Message variables:

error_textThe source of the line in error


Administrator response: Check the AOPxxLOGsystem log and the AOPOUT error message log for anymessages that might indicate why the error occurred.Resolve the cause of the error and restart the sourcecollector. If the error continues, contact IBM SoftwareSupport.

GTM1620I OBJECT PUMP TO OBJECT SERVERHANDSHAKE STARTED

Explanation: The source collector detects the eventdistributor address space.


GTM1630I OBJECT PUMP TO OBJECT SERVERHANDSHAKE ENDED

Explanation: The source collector is ending itsmonitoring of the event distributor address space.


GTM1640E INVALID FUNCTION function PASSEDTO GTMRX019

Explanation: A function that was not valid waspassed to the GTMRX019 REXX exec.

Message variables:

function The name of the function that was passed


Administrator response: Check the AOPxxLOGsystem log and the AOPOUT error message log for anymessages that might indicate why the error occurred. Ifthe error continues, contact IBM Software Support.

GTM1641E VALID FUNCTIONS ARE START,STOP, QUERY, FAILURE, TAKEOVER,INFORM

Explanation: This message is a continuation of theGTM1640E message and lists the valid functions that


can be passed to the GTMRX019 REXX exec.


Administrator response: Check the AOPxxLOGsystem log and the AOPOUT error message log for anymessages that might indicate why the error occurred. Ifthe error continues, contact IBM Software Support.

GTM1655I RESTART OF THE OBJECT SERVERjobname - JOBNAME type WASSUCCESSFUL

Explanation: The event distributor was stopped andsuccessfully restarted.

Message variables:

jobname The job name of the event distributor

type The type of the event distributor

GTM1660E FAILURE PROCESSING CALLEDWITH INVALID MSGID msgidMESSAGE IGNORED ANDPROCESSING CONTINUES

Explanation: The source collector detected that theevent distributor is ending or failed, but cannotdetermine the actual condition.

Message variables:

msgid The ID of the message trapped by the sourcecollector


Administrator response: Check the messages in thesystem log that might be related to this error.Determine why the event distributor is ending. Restartthe event distributor and source collector if required.

GTM1680E ERROR READING SHAREDVARIABLE variable_name IN pgm

Explanation: An error occurred reading the sharedvariable specified in the GTMRX019 program.

Message variables:




Administrator response: Check the messages in theAOPxxLOG system log and the AOPOUT errormessage log that might be related to this error. See theGTM1681E message to identify the return code relatedto this error. Resolve the cause of the error and restartthe source collector. If the error continues, contact IBMSoftware Support.

GTM1681E RC return_code PROCESSINGTERMINATED

Explanation: Displays the return code from the readfailure that is indicated by the GTM1680E message.

Message variables:

return_codeThe return code from the variable get routine

System action: The routine cannot process events.

Administrator response: Check the messages in theAOPxxLOG system log and the AOPOUT errormessage log that might be related to this error. Resolvethe cause of the error and restart the source collector. Ifthe error continues, contact IBM Software Support.

GTM1682E ERROR READING GLOBALVARIABLE variable_name IN pgm

Explanation: An error occurred reading the globalvariable from the variable pool that is specified in theGTMRX019 REXX exec.

Message variables:



System action: The program cannot process events.

Administrator response: Check the messages in thesystem log and the AOPxxLOG system log that mightbe related to this error. Resolve the cause of the errorand restart the source collector. If the error continues,contact IBM Software Support.

GTM1683E RC return_code ATTEMPTED RESTARTOF jobname TERMINATED

Explanation: While processing a normal or abnormalshutdown of the event distributor, the source collectorreceived the error that is described in the GTM1682Emessage.

Message variables:

return_codeThe return code from the error listed in theGTM1682E message

jobname The job name of the event distributor addressspace

System action: The program shuts down.

Administrator response: Check the messages in theAOPxxLOG system log that might be related to thiserror. Resolve the cause of the error and restart thesource collector. If the error continues, contact IBMSoftware Support.


GTM1687E OBJECT SERVER OUTSTANDINGVTAM REPLY IS NOT AVAILABLE

Explanation: The source collector detected that theevent distributor lost the connection to TBSM. Thesource collector is attempting to restart the connectionbut the WTOR reply number is not found for the eventdistributor.


Administrator response: The outstanding VTAM replymight have been removed from the console, but mightstill be outstanding. Issue the MVS D R,L operatorcommand to view any outstanding requests. Reply tothe command appropriately. If the WTOR messagecannot be found, restart the event distributor.

GTM1688E PLEASE STOP AND RESTART jobname


Message variables:

jobname The event distributor job name


Administrator response: The outstanding VTAM replymight no longer be available on the console but mightstill be outstanding. Issue the MVS D R,L operatorcommand to view any outstanding requests. Reply tothe command appropriately. If the WTOR messagecannot be found, restart the event distributor.

GTM1690E OBJECT SERVER ADDRESS SPACEHAS ABENDED - JOBNAME = jobname

Explanation: The source collector detected that theevent distributor address space ended abnormally.

Message variables:

jobname The event distributor job name

System action: Processing continues. The eventdistributor shuts down.

Administrator response: Check the messages in thesystem log to determine why the event distributoraddress space ended abnormally. Correct the problemand restart the event distributor. If the problemcontinues, contact IBM Software Support.

GTM1691E RC = return_code REASON CODE =reason_code

Explanation: Displays the return and reason codesassociated with the GTM1690E message.

Message variables:


reason_codeThe reason code

System action: Processing continues. The eventdistributor shuts down.


GTM1692E RESTART FOR OBJECT SERVERADDRESS SPACE jobname NOTATTEMPTED

Explanation: The source collector detected that theevent distributor ended abnormally and does notattempt to restart the event distributor. The abend codeis listed in the GTM1693E message.

Message variables:

jobname The event distributor component addressspace name

System action: The event distributor shuts down.


GTM1693E SYSTEM COMPLETION CODEIS=abend_code

Explanation: The abend code that is associated withthe GTM1692E message is displayed.

Message variables:

abend_codeThe abend code


Administrator response: Check the messages in thesystem log to determine why the event distributoraddress space received a X'X22' or X'0C4' abend code.Correct the problem and restart the event distributor.The abend codes are as follows:

v X'X22': Resolve the issue as described in z/OS MVSSystem Codes.

v X'0C4': If the problem continues, contact IBMSoftware Support.

GTM1695I THE OBJECT SERVER ADDRESSSPACE jobname HAS TERMINATED

Explanation: The source collector determined that theevent distributor ended.

Message variables:



GTM1696E THE OBJECT SERVER ADDRESSSPACE jobname HAS LOST ITS VTAMCONVERSATION

Explanation: The source collector determined that theevent distributor lost its VTAM connection to EventPump.

Message variables:


System action: Processing continues. The eventdistributor is waiting to establish the connection again.

Administrator response: Check the messages in thesystem log to determine why the event distributor lostcommunication. Correct the problem and restart theevent distributor. If the problem continues, contact IBMSoftware Support.

GTM1697E A RESTART WILL BE ATTEMPTED INnumber MINUTES

Explanation: The source collector detected that theevent distributor lost its VTAM connection to EventPump. The source collector attempts to establish theconnection again on the next time interval specified inminutes.

Message variables:

number The number of minutes until source collectorattempts to establish the connection again


Administrator response: Check the messages in thesystem log to determine why the event distributor lostcommunication. Correct the problem and restart theevent distributor. If the problem continues, contact IBMSoftware Support.

GTM1698I A STOP COMMAND HAS BEENISSUED FOR THE OBJECT SERVERADDRESS SPACE jobname

Explanation: A shutdown request was issued for theevent distributor.

Message variables:



GTM1699I A CANCEL COMMAND HAS BEENISSUED FOR THE OBJECT SERVERADDRESS SPACE jobname

Explanation: A CANCEL command for the eventdistributor was issued from the console.

Message variables:



Administrator response: Determine why the eventdistributor was canceled.

GTM1700I OBJECT PUMP VALIDATIONMODULE HAS BEGUN PROCESSING

Explanation: The source collector received controlstatements from Event Pump.


GTM1705I OBJECT PUMP VALIDATIONMODULE HAS ENDED PROCESSING

Explanation: The source collector completed theprocessing of all received data.


GTM1710E ERROR request SHARED VARIABLEvariable_name IN pgm RC = return_code

Explanation: An error occurred in using a sharedvariable that is associated with a console trap.

Message variables:

request The variable request function

variable_nameThe shared variable name

pgm The name of the REXX exec program issuingthe message


System action: Processing continues. The trap thatstarted did not complete.

Administrator response: Check the messages in thesystem log and the AOPxxLOG system log to see whythe function failed. The processing of the event isstopped. Resolve the cause of the error and restart thesource collector. If the error continues, contact IBMSoftware Support.

GTM1711E INITIALIZATION PROCESSING HASBEEN TERMINATED


Administrator response: Check the messages in thesystem log and the AOPxxLOG system log to see whythe function failed. The processing of the event isstopped. Resolve the cause of the error and restart thesource collector. If the error continues, contact IBMSoftware Support.


GTM1715I THE END OF BLOCK INDICATOR (~)WAS MISSING

Explanation: A single record was read by the sourcecollector and did not contain an end-of-record indicator(~).

System action: Processing continues. The eventmessage is not processed.


GTM1716I PROCESSING CONTINUES


GTM1717I text


Message variables:

text The entire record that was received from EventPump

GTM1720E ERROR OCCURRED CALLING THEOBJECT SERVER. RETURN CODE =return_code

Explanation: An error occurred while attempting towrite a record to the event distributor queue by thesource collector. The event distributor did not receivethe information described in the GTM1721E message.

Message variables:

return_codeThe return code of the error that occurredduring an attempted write to the eventdistributor queue

System action: Processing continues. The eventmessage was not sent to the event distributor.

Administrator response: Check the messages in thesystem log and the AOPxxLOG system log todetermine the cause of the error. The record is notwritten to the event distributor. Resolve the cause ofthe error and restart the event distributor and sourcecollector. If the problem continues, contact IBMSoftware Support.

GTM1721E DATA ITEM IS: text


Message variables:

text The record that was not written to the eventdistributor

System action: Processing continues. The event

message was not sent to the event distributor.


GTM1722E PROCESSING FOR THIS DATAELEMENT HAS BEEN TERMINATED


System action: Processing continues. The eventmessage was not sent to the event distributor.


GTM1760E MISSING NATIVE KEY FORresource_type SHARED VARIABLE

Explanation: A high-level resource type (ENT, COMP,MACH, LPAR, or OS) is not properly defined to thesource collector. The resource is missing its databasekey.

Message variables:

resource_typeThe high-level resource type

System action: Processing continues. The sourcecollector is not properly started to collect events.

Administrator response: The environment is not setup correctly. Determine why the native key for theobject is missing. No other data is processed until thissituation is corrected. If the problem continues, contactIBM Software Support.

GTM1761E PROCESSING IS BEINGTERMINATED FOR DATA JUSTRECEIVED


System action: Processing continues. The recent eventmessage is not processed.

Administrator response: The environment is not setup correctly. Determine why the native key for theobject is missing. No other data is processed until thissituation is corrected. If the problem continues, contactIBM Software Support.


GTM1770I ALL REQUIRED SHARED VARIABLESHAVE BEEN REGISTERED,PROCESSING CONTINUES

Explanation: The shared variables that are requiredfor the startup procedure were successfully created.Additional registration data can now be processed.


GTM1780I OBJECT PUMP/OBJECT SERVER ISREQUESTING OBJECTS

Explanation: The source collector, through the eventdistributor, is requesting that Tivoli Business ServiceManager forward registration information.


GTM1790E RECEIVED OBJECT DATA BEFORESHARED VARIABLES HAVE BEENBUILT

Explanation: Registration data was received before thehigh-level resource types (ENT, COMP, MACH, LPAR,or OS) were properly defined to the source collector.



GTM1800E INVALID RETURN CODE FROMpgm_called - FUNCTION = function,RETURN CODE = return_code, CALLER= pgm

Explanation: There was an unsuccessful call to aREXX exec specified in the program that was called.

Message variables:

pgm_calledThe REXX exec program that was called

function The passed variable; typically START or STOP

return_codeThe return code from the call

pgm The REXX exec issuing the call


Administrator response: Check the messages in theAOPxxLOG system log and the AOPOUT errormessage log that might be related to this error. Resolvethe cause of the error and restart the source collector. Ifthe error continues, contact IBM Software Support.

GTM1805E FIRST RECORD IN QUEUE IS NULL

Explanation: On a READ request of the eventdistributor queue by the source collector, a null recordwas discovered.


Administrator response: An event message that isbeing sent is not formatted correctly. A generated eventrecord that contains only a control statementtermination character (~) can cause this error. ContactIBM Software Support.

GTM1810E RECORD IS NULL - LAST VALIDRECORD WAS...

Explanation: On a READ request other than the initialREAD request from the event distributor queue by thesource collector, a null record was discovered on theserver queue.

Read the GTM1811E message for known informationabout the previous record in the stack.


Administrator response: An event message that isbeing sent is not formatted correctly. A generated eventrecord containing only a control statement terminationcharacter (~) can cause this error. Contact IBM SoftwareSupport.

GTM1811E previous_event_msg


Message variables:

previous_event_msgThe event message preceding the null record


Administrator response: An event message that isbeing sent is not formatted correctly. A generated eventrecord containing only a control statement terminationcharacter (~) can cause this error. Contact IBM SoftwareSupport.

GTM1815E UNRECOGNIZABLE DATA FROMOBJECT SERVER - BAD FORMAT ORACTION CODE

Explanation: The Format or Action codes received ona registration message are not supported. Theregistration message is not processed by the sourcecollector. The registration message is displayed in theGTM1816E message.




GTM1816E error_text


Message variables:

error_textThe registration message that was not valid



GTM1820E UNEXPECTED DATA TYPE VALUE ORCONTINUATION (\) WAS FOUND INRECORD

Explanation: An unsupported data type that isassociated with a data value was found in the datarecord that was received from Tivoli Business ServiceManager. Each value in the record is defined with aspecific data type indicating the type of data thatimmediately follows. The registration messagecontaining the invalid data type is not processed by thesource collector.



GTM1821E error_type error_text


Message variables:

error_typeThe data type and value that was not valid

error_textThe entire record containing the data type thatwas not valid



GTM1825I VALID BUT UNEXPECTEDFORMAT/ACTION TYPE WAS FOUNDIN RECORD

Explanation: The source collector received a formattype that is not valid or a data type value that is notvalid for the type of object to be registered.

System action: The registration message is notprocessed, but processing continues. The registrationmessage is displayed in the GTM1826I message.


GTM1826I error_type error_text


Message variables:

error_typeThe format or action type that was not valid

error_textThe entire record containing the code that wasnot valid



GTM1835E INVALID OR UNEXPECTED name =error_value

Explanation: A value associated with a data type wasnot valid.

Message variables:

name The name of the data type

error_valueThe value that was not valid



GTM1836E error_text


Message variables:

error_textThe registration message containing the datatype that was not valid



GTM1840E MISSING DATA. SEE NULL FIELDBELOW FOR MISSING VALUE:

Explanation: A registration message was receivedwithout a value in a mandatory field.

System action: The registration message is notprocessed by the source collector. Processing continues.



GTM1841E OBJECT ID = object_id NATIVE KEY =value


Message variables:

object_idA valid object name or a problem null value

value A valid 10-character native key for the objector a problem null value



GTM1842E OBJECT NAME = object_name


Message variables:

object_nameA valid object name or a problem null value



GTM1843E error_text


Message variables:

error_textThe registration message containing themissing data



GTM1845E UNACCEPTABLE RECORDSEXCEEDED TOLERANCE

Explanation: The number of records in error that werereceived by the source collector that exceeded thetolerance count or error tolerance percentage.


Administrator response: Determine why an excessivenumber of unacceptable records are attempting to getregistered by the source collector. Either the data wasimproperly generated from the database or data wasnot aligned during the communications phase. If theproblem continues, contact IBM Software Support.

GTM1846E UNACCEPTABLE TOLERANCECOUNT = number


Message variables:

number The threshold count for errors tolerated by thesource collector



GTM1847E UNACCEPTABLE TOLERANCEPERCENT = percent


Message variables:

percent The threshold percentage of bad recordsversus good records tolerated by the sourcecollector



GTM1848E GOOD REC COUNT = number; ERRORREC COUNT = error_number


Message variables:

number The number of acceptable records that wereprocessed by the source collector

error_numberThe number of error records that wereprocessed by the source collector


Administrator response: Determine why an excessivenumber of unacceptable records is attempting to getregistered by the source collector. Either the data wasimproperly generated from the database or data wasnot aligned during the communications phase. If theproblem continues, contact IBM Software Support.


GTM1849E PROCESSING IS BEINGTERMINATED



Administrator response: Determine why an excessivenumber of unacceptable records is attempting to getregistered by the source collector. Either the data wasimproperly generated from the database or data wasnot aligned during the communications phase. If theproblem continues, contact IBM Software Support.

GTM1850E WILDCARD (*) IS NOT ACCEPTABLEFOR MONITOR/RE-DISCOVEROPERATION

Explanation: A wildcard was used in the object namevalue for an object monitor request. A wildcard cannotbe used for this type of operation.



GTM1851E OR CHILD AUTO-DISCOVER (TRAN,FILE, LU, DB CONN)

Explanation: This message is a continuation of theGTM1850E message. Also, child object names cannotcontain a wildcard for the TRAN, FILE, LU, DB, andCONN object types.



GTM1852E OBJECT ID = object_id NATIVE KEY =value


Message variables:

object_idA valid object ID such as CICS, STC, and IMS

value A valid 10-character native key for the objectID




Message variables:

object_nameThe name of the resource



GTM1854E error_text


Message variables:

error_textThe registration message containing the objectname with the wildcard



GTM1855E THE TRAP NAME EXCEEDED 24CHARACTERS

Explanation: A console trap name generated andexceeded 24 characters in length. The source collectordid not generate the trap.


Administrator response: Identify the trap name thatfailed in the GTM1856E message and determine if itwas generated based on a source collector keyword orsent from Tivoli Business Service Manager. If the trapgenerated was derived from one of the source collectorkeywords, such as SA390, the administrator mustcorrect this error. If this error is generated as a result ofa registration message, contact IBM Software Support.

GTM1856E TRAP NAME = trap_name


Message variables:

trap_nameThe trap name that is not valid



GTM1857E trap_text


Message variables:


trap_textThe trap text that is associated with the trapname



GTM1860E UNACCEPTABLE ACTION TYPERECEIVED: action_type

Explanation: The source collector for processingreceived action type that is not valid. Action typesindicate operations such as monitoring andauto-discovery.

Message variables:

action_typeThe action type that is not valid



GTM1861E OBJECT TYPE ID = object_id


Message variables:

object_idA valid object ID such as CICS, STC, or IMS





Message variables:

object_nameThe object name that is associated with theinvalid action type



GTM1865E OMEGAMON LOG ON RECEIVEDFOR OS NAME: OS_name

Explanation: An OMEGAMON logon request wasreceived by one operating system and the results weredirected to another operating system. This request isnot an acceptable transaction because exceptions can beposted to an incorrect operating system. The sourcecollector rejects the logon request.

Message variables:

OS_nameThe name of the operating system that is toreceive the exceptions for the OMEGAMONsession


Administrator response: Verify that the configurationmatches the logon connections of the source collector tothe OMEGAMON programs and that they areestablished on the target operating systems. If this errorcontinues, contact IBM Software Support.

GTM1866E THIS PROCESSOR IS OS NAME:OS_name


Message variables:

OS_nameThe name of the operating system thatreceived the OMEGAMON log on request


Administrator response: Verify that the configurationmatches the Logon connections of the source collectorto the OMEGAMON programs and that they areestablished on the target operating systems. If this errorcontinues, contact IBM Software Support.

GTM1867E LOGON REQUEST WILL NOT BEPROCESSED



Administrator response: Verify that the configurationmatches the logon connections of the source collector tothe OMEGAMON programs and that they areestablished on the target operating systems. If this errorcontinues, contact IBM Software Support.


GTM1870E PEER START PROCESS FAILEDcomm_link

Explanation: Peer communications between the sourcecollector and the event distributor cannot be started.

Message variables:

comm_linkThe name of the failing communications link

Administrator response: Contact the administrator

GTM1872E FAILURE STARTING PEER-PEERAPPLICATION comm_link

Explanation: The application ID between the sourcecollector and the event distributor was not properlystarted.

Message variables:

comm_linkThe name of the failing communications link

Administrator response: Contact the administrator.

GTM1874E FAILED TO ESTABLISH ACONNECTION WITH applid

Explanation: A connection cannot be establishedbetween the source collector and the event distributor.

Message variables:

applid The application ID of the communications link

Administrator response: Contact the administrator

GTM1900I OBJECT PUMP/OBJECT SERVER HASENDED PROCESSING

Explanation: The record or batch of records sent to thesource collector for processing is completed.

GTM1905E MESSAGE DATA OUT OF SEQUENCEOR AN EXPECTED...

Explanation: A registration record that was received isnot well formed.



GTM1906E CONTINUATION (\) WAS NOTRECEIVED - EXPECTED DATAPATTERN IS...




GTM1907E 46MESSAGE\46MESSAGE\46MESSAGE




GTM1908E ALSO, MESSAGE DATA MUST BELAST DATA IN REC




GTM1909E error_text


Message variables:

error_textThe registration record that is in error



GTM1910E STATE/MESSAGE DATA OUT OFSEQUENCE OR AN EXPECTED

Explanation: State and Message data types (45 and 46,respectively) must be the last data types in a recordthat requests object monitoring and must follow thepattern of State-Message-State-Message-State-Message.



GTM1911E CONTINUATION (\) WAS NOTRECEIVED - EXPECTED DATAPATTERN IS



Administrator response: A backslash character (\)might be missing at the end of a State or Messagevalue. See the acceptable pattern in the GTM1912Emessage. Contact IBM Software Support.


GTM1912E 45STATE\46MESSAGE\45STATE\46MESSAGE



Administrator response: The pattern for State andMessage values is defined in this message. An actualexample looks as follows:

\45ACTIVE\46IEF403I\45INACTIVE\46IEF404I...

Contact IBM Software Support.

GTM1913E ALSO, STATE AND MESSAGE DATAMUST BE LAST DATA IN REC



Administrator response: The combination ofState/Message patterns must be at the end of therecord. No other data types are accepted after thispattern. Contact IBM Software Support.

GTM1914E error_text


Message variables:

error_textThe registration text



GTM1915E NO MATCHING MESSAGE TYPE FORSTATE OR (\) MISSING

Explanation: State and Message data types (45 and 46)must be the last data types in a record for monitoringand must follow the pattern of State-Message-State-Message-State-Message. State and Message fields mustbe separated by a backslash (\). A data type of 46(Message) was probably missing in the record that isdisplayed in the GTM1916E message.



GTM1916E msg_type


Message variables:

msg_typeThe registration message



GTM1917E 46MESSAGE\46MESSAGE\46MESSAGE



GTM1918E ALSO, MESSAGE DATA MUST BELAST DATA IN REC



GTM1919E error_text


Message variables:

error_textThe record that is in error


GTM1920E NO DATA VALUE FOR field_type TYPEdata_type

Explanation: No data value was found for a State orMessage data type.

Message variables:

field_typeIndicates whether the missing value is for aState or for a Message field

data_typeThe data type for the missing value. A State isrepresented as data type (45) and a Message isrepresented as data type (46).



GTM1921E error_text


Message variables:

error_textThe registration record




GTM1925E SUSPECT THIS PROGRAM WASMODIFIED - THE VALUE FOR

Explanation: A REXX exec program (GTMRX020) waschanged and is not accepting the correct state andmessage combination.



GTM1926E EXPECTED DATA VALUE CAN ONLYBE 45 OR 46 - CHECK PROGRAM




GTM1930E AN OBJECT FOR keyword WASRECEIVED WITHOUT STATES ORMESSAGES

Explanation: A record for some form of monitoringwas received that did not contain states or messages tomonitor.

Message variables:

keyword The name of the keyword, which can beMONITORING, REDISCOVER, SET_UP_IND,or MESSAGE_TRAP



GTM1931E error_text


Message variables:

error_textThe registration message



GTM1935E THE OBJECT NAME EQUALS THEOBJECT SERVER JOB NAME

Explanation: A trap for monitoring the eventdistributor STC cannot be created. During initializationof the mainframe components, special traps formonitoring the event distributor are generated andmust not be overwritten.


Administrator response: Remove the object from thedatabase that has the same name as the eventdistributor started task. Restart the source collector.



Message variables:

object_nameThe name of the object that requestsmonitoring. This name is also the eventdistributor job name.


Administrator response: Remove the object from thedatabase with the same name as the name of the eventdistributor started task. Restart the source collector.

GTM1937E RECORD = error_text


Message variables:

error_textThe registration record



GTM1938E THIS COULD CAUSE AN INTERNALTBSM MONITORING FAILURE





GTM1939E PLEASE SEE THE MESSAGES ANDCODES MANUAL FOR MORE DETAIL



Administrator response: Remove the object from thedatabase that has the same name as the name of theevent distributor started task. Restart the sourcecollector.

GTM1940I VALIDATION MODULE INVOKEDNO DATA RECEIVED

Explanation: The source collector was instructed toread the source collector data queue but no data wasfound. This error can be caused by a tilde (~) missingat the end of the record forwarded from Tivoli BusinessService Manager. Another possibility is that a non-USAEnglish-language character was received in place of thetilde (~) character, causing the same symptom.


Administrator response: If a console code page otherthan 437 is used on the source collector servers, reviewthe comments in the cconv.tbl file in theTivoliManager\Lang\language_ID directory. Theconsole code page can be determined by using theSetConsoleCodePage command. Issue this commandfrom a Windows command prompt and note the valueof the current console code page.

GTM1955I A SHUTDOWN HAS BEENREQUESTED - SYSTEMTERMINATING

Explanation: The source collector was instructed toshut down. All events ended correctly.

System action: The tasks are shut down.

GTM1960E UNKNOWN SUB-FUNCTIONRECEIVED FROM A PASSEDARGUMENT

Explanation: A subfunction that is not valid waspassed to the GTMRX018 module. The validsubfunctions include JOB, CYLCE, STATUSA, STATUSI,CHILD_DISCOVER, ID, REQUEST_OBJECTS, andSHIP_MESSAGE.


GTM1961E EXPECTED FORMAT OF ARGUMENT(FUNCTION SUB-FUNCTION)



GTM1962E ARGUMENT = error_text


Message variables:

error_textThe argument that was passed to theGTMRX018 module. The first two fieldsrepresent the function and subfunction.


GTM1965E ERROR PROCESSING SYSTEMVARIABLE variable_name IN pgm

Explanation: An error occurred retrieving the jobname of the source collector from the system variablepool.

Message variables:

variable_nameSYS_AOPJOBNAME

pgm The REXX exec GTMRX018 program


Administrator response: Check the system messagesand the AOPxxLOG system log to see if any relatedmessages are available that might indicate why thefunction failed. The source collector initialization isshut down. Resolve the cause of the error and restartthe source collector. If the problem continues, contactIBM Software Support.

GTM1966E PROCESSING HAS BEENTERMINATED


System action: The task is shut down.

Administrator response: Check the system messagesand the AOPxxLOG system log to see if any relatedmessages are available that might indicate why thefunction failed. The source collector initialization isshut down. Resolve the cause of the error and restartthe source collector. If the problem continues, contactIBM Software Support.

GTM1970E THERE CAN ONLY BE ONETDQ/BATCH CYCLE MESSAGE (TYPE46) IN THE RECORD

Explanation: The source collector received a singlerequest to capture more than one generic message thatis related to batch/TDQ processing. Only one genericmessage (data type 46) can be coded in a request.




GTM1971E error_text


Message variables:

error_textThe TDQ/BATCH CYCLE in error



GTM1975E MISSING DATA. SEE NULL FIELDBELOW FOR MISSING VALUE:

Explanation: The creation of a console trap for a TDQor Batch Cycle message is missing a key value.



GTM1976E OBJECT ID = object_id SET UPINDICATOR = value

Message variables:

object_idThe value of the Object_ID or NULL

value The value of the Set Up Indicator (expected tobe TDQ) or NULL



GTM1977E MESSAGE-ID = msgid


Message variables:

msgid The value of the message-ID to be trapped orNULL



GTM1978E error_text


Message variables:

error_textThe value of the message-ID to be trapped orNULL



GTM1980E THERE CAN ONLY BE ONE TIMEDURATION CODE data_type IN THERECORD

Explanation: There was more than one start/stop timeduration value for a TDQ or Batch Cycle record.

Message variables:

data_typeThe data type in error. Data type 68 is the starttime for trap collection and data type 69 is thestop time for trap collection.



GTM1981E error_text


Message variables:

error_textThe registration record that contains the error



GTM1985E BATCH JOB SUBMISSION FAILED,UNABLE TO LOCATE[MEMBER|jobname] or[DDCARD|GTMJCL]

Explanation: The READMEM function failed in theGTMRXJOB program. The batch job is not submitted.

Message variables:

jobname The PDS member containing the job namecannot be located


Administrator response: Verify that the batch jobexists in the library of the source collector where batchjobs might be submitted. If the batch job exists but wasnot submitted, check the resources under the JES2system to ensure that internal readers are available.Resubmit the batch job.


GTM1986E BATCH JOB SUBMISSION FAILED,INVALID JCL RECORD LENGTHrecord_length

Explanation: A record that is read from theREADMEM function to retrieve a JCL record is toolong. The batch job is not submitted.

Message variables:

record_lengthThe length of a JCL record


Administrator response: Verify that the JCL recordsare 80 characters in length. Resubmit the batch job.

GTM2010E INVALID NUMBER OF ARGUMENTSPASSED TO MESSAGE MANAGER:

Explanation: The REXX exec GTMRX016 MessageManager received a request to generate a message, butthe request did not contain the correct number ofarguments.



GTM2011E NUMBER OF ARGUMENTS = number


Message variables:

number The number of arguments received by theGTMRX016 Message Manager



GTM2012E CORRECT NUMBER OF ARGUMENTS>= 2 OR <= 8




GTM2013E CALLING PROGRAM NAME IS SETTO pgm


Message variables:

pgm The name of the REXX exec that is calling theGTMRX016 Message Manager



GTM2080E A SYNTAX ERROR OCCURREDWHICH might BE DUE TO ANINVALID MESSAGE ID

Explanation: The REXX exec GTMRX016 MessageManager received a request to generate a message for amessage ID that is either not valid or undefined.



GTM2081E THE MESSAGE ID = msgid


Message variables:

msgid The message ID that is being sent to theGTMRX016 program



GTM2082E THIS PROCESS WAS STOPPED ONLINE: error_line


Message variables:

error_lineThe line number where processing stopped



GTM2083E THE SOURCE LINE IS: source_line


Message variables:

source_lineThe source line where processing stopped




GTM2084E THIS PROGRAM IS: pgm THECALLING PROGRAM IS: pgm_called


Message variables:

pgm The name of the REXX exec program thatencountered the syntax error

pgm_calledThe name of the REXX exec program thatcalled the program in error



GTM2085E THIS PROCESS WAS HALTED ONLINE: error_line

Explanation: The GTMRX016 module encountered anerror that it cannot correct.

Message variables:

error_lineThe line number in the GTMRX016 module





Message variables:

error_textThe source line that encountered the error inthe GTMRX016 module



GTM2087E THIS PROGRAM IS:pgm, THECALLING PROGRAM IS: pgm_called


Message variables:

pgm The name of the program that encountered theerror

pgm_calledThe name of the program that called theprogram in error



GTM2088E AN ERROR OCCURRED ON LINE:error_line

Explanation: The line where the error occurred.

Message variables:

error_lineThe line number of the program thatencountered the error





Message variables:

error_textThe source code that encountered the error



GTM2090E THIS PROGRAM IS: pgm, THECALLING PROGRAM IS: pgm_called


Message variables:

pgm The program in error

pgm_calledThe program that called the program in error



GTM2100E ERROR DETERMINING LOG FILENAME. LOGGING IS DISABLED

Explanation: The name of the log file cannot beretrieved.




GTM2101I LOG PROCESSING IS AVAILABLE.DDNAME = ddname

Explanation: Informational message indicating thatthe log file is operational.

Message variables:

ddname The DD name that is associated with the logfile



GTM2102I DSNAME = dsname


Message variables:

dsname The data set name of the log file


GTM2103E UNABLE TO DETERMINE LENGTHOF LOG RECORD - LOGGING ISDISABLED

Explanation: The logical record length of the log filecannot be determined. Logging is disabled butprocessing continues.


Administrator response: Check the log file to ensurethat it is available. Verify that the log file is catalogedand the DASD volume used is online. If the problemcontinues, contact IBM Software Support.

GTM2104I THE LOG WILL BE CLOSED ANDOPENED ON THE INTERVAL:time_interval

Explanation: To prevent the loss of data, the log file isclosed and reallocated based on the interval that isdescribed at the end of the message.

Message variables:

time_intervalThe time interval in hh:mm:ss


GTM2110E COULD NOT ALLOCATE THE LOGFILE ddname

Explanation: The log file cannot be allocated.Processing stops.

Message variables:

ddname The DD name of the log file attemptingallocation


Administrator response: Determine why the log filecannot be allocated. Resolve the cause of the error andrestart the source collector. If the error continues,contact IBM Software Support.

GTM2111E FILE NAME IS dsname


Message variables:

dsname The data set name of the log file that cannotbe allocated



GTM2112E RETURN CODE = return_code -LOGGING IS HALTED


Message variables:

return_codeThe data set name of the log file that cannotbe allocated



GTM2120E COULD NOT OPEN THE LOG FILEddname

Explanation: The log file for the source collectorcannot be opened, and log data is not processed.

Message variables:

ddname The DD name of the file that is allocated tothe log


Administrator response: Determine why the log filecannot be opened. Resolve the cause of the error andrestart the source collector. If the error continues,contact IBM Software Support.

GTM2121E FILE NAME IS dsname


Message variables:


dsname The data set name of the log file that cannotbe opened



GTM2122E RETURN CODE = return_code -LOGGING IS HALTED


Message variables:

return_codeThe return code from the open operationfailure



GTM2130E COULD NOT WRITE TO THE LOGFILE ddname

Explanation: The log file cannot be written for thesource collector.

Message variables:

ddname The DD name of the log file that was allocatedand opened


Administrator response: Determine why the log filecannot be written to. Resolve the cause of the error andrestart the source collector. If the error continues,contact IBM Software Support.

GTM2131E FILE NAME CAN BE FOUND INMESSAGE GTM210I

Explanation: This message is a continuation of theGTM2130E message. The data set name for the log filecan be found in the GTM210I message.



GTM2132E RETURN CODE = return_codeLOGGING IS HALTED


Message variables:

return_codeThe return code that is associated with thewrite operation error



GTM2140I COULD NOT CLOSE THE LOG FILERETURN CODE=return_code

Explanation: The log file for the source collectorcannot be closed after use.

Message variables:

return_codeThe return code from the attempted closeoperation failure


Administrator response: Determine why the log filecannot be closed. Resolve the cause of the error andrestart the source collector. If the error continues,contact IBM Software Support.

GTM2141I FILE NAME CAN BE FOUND INPREVIOUS MESSAGE GTM210I

Explanation: This message is a continuation of theGTM2140I message. The data set name can be found inthe GTM2101I message.


Administrator response: Determine why the log filecannot be closed. Resolve the cause of the error andrestart the source collector. If the error continues,contact IBM Software Support.

GTM2150I COULD NOT FREE THE LOG FILE -RETURN CODE=return_code

Explanation: After the close of the source collector logfile, it cannot be dynamically freed.

Message variables:

return_codeThe return code from the free operationattempt


Administrator response: Determine why the log file


cannot be freed. Resolve the cause of the error andrestart the source collector. If the error continues,contact IBM Software Support.

GTM2151I FILE NAME CAN BE FOUND INPREVIOUS MESSAGE GTM2101

Explanation: This message is a continuation of theGTM2150I message. The data set name of the file notfreed can be found in the GTM2101 message.


Administrator response: Determine why the log filecannot be freed. Resolve the cause of the error andrestart the source collector. If the error continues,contact IBM Software Support.

GTM2155I LOG PROCESSING HAS BEENTERMINATED

Explanation: The source collector shut down and thelogging is stopped.


GTM2160I INVALID FUNCTION function PASSEDTO pgm

Explanation: An invalid function name was passed tothe GTMRX006 REXX exec.

Message variables:

functionThe value of the function that is not valid thatwas passed

pgm The name of the REXX program (GTMRX006)



GTM2161I VALID FUNCTIONS ARE INIT, SHUTOR LOG




GTM2170E ERROR WRITING SHAREDVARIABLE variable_name IN pgm

Explanation: The source collector cannot set theshared variable.

Message variables:

variable_nameThe name of the shared variable

pgm The name of the program attempting to set thevariable


Administrator response: Increase the REGIONparameter and restart the source collector. If the errorcontinues, contact IBM Software Support.



Message variables:

return_codeThe return code that is associated with theSET variable write failure



GTM2175E ERROR request SHARED VARIABLEvariable_name IN pgm RC = return_code

Explanation: The source collector logging facilityencountered an error in processing the shared variablename.

Message variables:

request The request (either a GET or a PUT) thatindicates reading from or writing to

variable_nameThe name of the shared variable that cannot beread from or written to

pgm The name of the REXX program having theproblem

return_codeThe return code from the read/write failure




Explanation: This global message is used when aREXX program encounters a program error.

Message variables:

error_typeThe type of error, such as syntax


pgm The name of the REXX program where theerror occurred

error_lineThe line number in the program where theerror occurred


Administrator response: Check the system messagesand the AOPxxLOG system log to see if any relatedmessages are available that might indicate why thefunction failed. Resolve the cause of the error andrestart the source collector. If the problem continues,contact IBM Software Support.



Message variables:

error_textThe source line that was in error




Explanation: This global message is issued when aREXX program encounters a program error.

Message variables:

error_typeThe type of error, such as syntax

pgm The name of the REXX program

error_lineThe line number in the program where theerror occurred





Message variables:

error_textThe source line where the error occurred



GTM3000I Reading registration data fromGTMINPUT

Explanation: One of the following conditionsoccurred:

v At startup, the source collector detected that aGTMINPUT DD statement was present in the JCLand is reading the registration data from thereinstead of receiving it from the event distributor.

v The user issued the REGISTER command, and thesource collector is reading the registration data.

v RODM is reconnected, and the source collector isprocessing the RODM registration data.



GTM3001E Expected continuation not received inrecord

Explanation: The last statement in the GTMINPUT fileindicated that it has a non-blank character in column72, but there was no statement. The statements in errorare displayed in this message.


Administrator response: Correct the input file.

GTM3002E Unknown card_type type on card(s) : card

Explanation: The statement type (first word) of thelisted registration data statements is not valid. Anystatements in error are displayed in this message.

Message variables:

card_typeThe type of registration statement: record orsource

card The GTMINPUT registration statement


Administrator response: Correct the input file.


GTM3003E Received registration data but no globaldata

Explanation: No GLOBAL entries were seen in theregistration data that was read from the GTMINPUTfile.


Administrator response: Correct the input file to addthe required GLOBAL entries.

GTM3004E GTMINPUT processing ending

Explanation: No GLOBAL entries are in theregistration data that was read from the GTMINPUTfile. This message follows the GTM3003E message.


Administrator response: Correct the input file to addthe required GLOBAL entries.

GTM3005E Unexpected return code from name,RC=return code, DD name=ddname

Explanation: While attempting to determine if thespecified DD name is allocated to the source collectoraddress space, the named routine gave an unexpectedreturn code.

Message variables:

name The name of the routine. Valid values areIHS$SRB1 and IHS$DDN.

return codeThe following return codes can be issued bythe IHS$SRB routine:

Table 1. IHS$SRB return codes

Returncode Description

0 Requested variables were created.

8 The SRB routine name or Target Addressname is not in the parameter list.

10 A job name or ASID that was providedfor the target is not valid.

12 Target Address Space name was notfound.

16 The user routine cannot be loaded (notfound or authorization/reentrancy error).

18 The IHS$SRB1 routine cannot be loaded(not found or authorization/reentrancyerror).

20 An error was returned by CSVQUERY.

24 An error was received from the IHS$DDNroutine.

28 The user routine ended abnormally.

Table 1. IHS$SRB return codes (continued)

Returncode Description

32 The IHS$SRB1 routine did not post back.

36 Attempts to redrive SRB exceeded theREDRIVE_LIM value.

40 An error occurred in generating variables.

The following return and reason codes can beissued by IHS$DDN (IHS$SRB return code is24):

Table 2. IHS$DDN return and reason codes

Returncode

Reasoncode Description

0 0 Successful.

4 0 Successful, but more data ispending. Redrive of routinerequired.

12 n/a Routine was not called fromwithin the IHS$SRB routine.

8 x Return code other than 0 receivedfrom initialize subroutine. Thereason code is the return code.

8 12 DDname was not passed or wasnot valid.

12 x Return code other than 0 wasreceived from the Process_ddsubroutine. The reason code is thereturn code.

ddname The name of the DD


Administrator response: Correct the cause of theerror, or contact IBM Software Support for additionalassistance in diagnosing the problem.

GTM3006E Registration data is being logged toGTMOUT

Explanation: The source collector detected that theGTMOUT DD statement is present in the startup JCLand writes all received registration data to the file.


GTM3007E RODM registration data found butpump not running with RODM support

Explanation: The source collector detected RODMregistration data in the registration data stream that isbeing read from the GTMINPUT file, but the sourcecollector is not configured to connect to a RODMsystem.



Administrator response: Remove the RODM inputfrom the registration data or configure the sourcecollector to connect to a RODM system.

GTM3008E An error occurred writing to GTMOUT.Logging of registration data suspended

Explanation: An error occurred writing registrationdata to the file that is associated with the GTMOUTDD statement. No additional logging of registrationdata is attempted during this running of the sourcecollector. Normal source collector operation continues.


Administrator response: Review the console and theAOPOUT error message logs to determine the cause ofthe failure. Typical causes are file full conditions orRACF security failures.

GTM3009I Processing of GTMINPUT datacomplete. Max RC = return code

Explanation: The source collector completedprocessing of the registration data in the file that isallocated to the GTMINPUT DD statement.

Message variables:

return codeThe return code for the operation


Administrator response: If the return code is 0, noaction is required. The source collector continuesstandard operation.

If the return code is not 0, review the console and theAOPxxLOG system log messages to determine thecause of any errors.

GTM3010I First name on REGISTER startupparameter not GLOBAL, added

Explanation: The user specified a list of element typesand group names in the REGISTER source collectorstartup parameter, but the first entry is not GLOBAL.


Administrator response: Correct the data that isspecified for the REGISTER source collector startupparameter to specify GLOBAL as the first element typeto register.

GTM3011I Missing group name on card numbernumber

Explanation: A GROUP statement was found in theGTMINPUT file but no group name was specified onthe statement. The number specifies the statementnumber in the GTMINPUT file.

Message variables:

number The statement number


Administrator response: Correct the indicatedstatement in the GTMINPUT file.

GTM3012W A error type error occurred at line linenumber in program name

Explanation: An unexpected processing or operationalerror of the error type type occurred at line number linenumber in the program name program.

Message variables:

error typeThe type of processing error

line numberThe line number where the error occurred

program nameThe name of the program affected by the error


Administrator response: Contact IBM SoftwareSupport for assistance.

GTM3013W Unable to process RODM data. Pumpnot connected to RODM : name

Explanation: The source collector encountered RODMregistration data but is not currently connected to thespecified RODM system.

Message variables:

name The RODM name


Administrator response: Check that the specifiedRODM system is correct. Because the name of theaddress space can be different from the RODM name,check that the named RODM is running.

GTM3014W Element or group name was not found inGTMINPUT

Explanation: The element or group name was notfound during a registration processing request.

Message variables:

name The element or group name


Administrator response: If the registration requestwas created by a REGISTER console command, reviewthe named elements and groups on the command orcorrect the GTMINPUT file and rerun the command.

If the registration request occurred during sourcecollector startup, review the element and group names


that are specified for the REGISTER source collectorstartup parameter, or correct the GTMINPUT file andrestart the source collector or use the REGISTERcommand to register the elements or groups.

If the registration request was the result of a RODMreconnect event, review the RODM_GROUPS sourcecollector startup parameter, or correct the GTMINPUTfile and use the REGISTER command to register theelements or groups.

GTM3021E No data found in $fieldname field forrecord $registration

Explanation: The $fieldname in the $registrationstatement does not contain a value.

Message variables:

$fieldnameThe field in error

registrationThe registration statement in error

System action: The registration statement is ignoredand processing continues.

Administrator response: Correct the registrationstatement and reissue the registration request.

GTM3023E Name specified in $fieldname field is toolong in record $registration

Explanation: The $fieldname value length in the$registration statement is too long.

Message variables:

$fieldnameThe field in error.

registrationThe registration statement in error.



GTM3024E Invalid $qualifier specified in $keyword inrecord $registration

Explanation: The $keyword of the $qualifier type in the$registration statement is not correct.

Message variables:

$qualifierthe qualifier of the keyword in error

$keywordThe keyword in error

$registrationThe registration statement in error



GTM3025E No data found in CONFIG field forrecord $registration

Explanation: A CONFIG keyword was specified, butno value was supplied.

Message variables:

$registrationThe registration statement in error.



GTM3026E Value specified in FORMAT field is notwithin range $registration

Explanation: The specified format code is outside thevalid range for the user-defined variables.

Message variables:




GTM3027W Handler required $registration

Explanation: A handler is required in the specifiedregistration statement.

Message variables:




GTM3028W Default handler used for userregistration record $registration.

Explanation: The default handler is used for thespecified registration statement.

Message variables:

$registrationThe registration statement in process


System action: Processing continues with the defaulthandler.

GTM3030E Error reading configuration member$config for $monitortype $SUBSYS=$subsys

Explanation: The $config configuration file for the$monitortype type experienced a read error. Thesubsystem defined by $subsys is optionally provided.

Message variables:

$config The name of the configuration member

$monitortypeThe monitor type

$subsys (Optional) The subsystem name


Administrator response: Ensure that the file that isspecified by the $config member exists and that the dataset that contains the configuration member is allocatedby the GTMMON DD statement in the source collector.Correct the registration statement, and reissue theregistration request.

GTM3031W Mask required $registration

Explanation: The message mask is required for thisregistration statement.

Message variables:



Administrator response: Ensure that the file that isspecified by the $registration statement exists. Correctthe registration statement and reissue the registrationrequest.

GTM3032W INVALID SEVERITY value value found,default default used.

Explanation: An invalid value was found; because thevalue is not valid, a default value was used instead.

Message variables:

value The value that is not valid

default The default value that is used instead of theinvalid value


Administrator response: Ensure that the file that isspecified by the $config member exists. Correct theregistration statement and reissue the registrationrequest.

GTM3040E Config member smsconfig containswrong number of exceptions excepnum

Explanation: The configuration member must containthe correct number of exceptions for each exceptiontype.

Message variables:

smsconfigThe CONFIG member name

excepnumThe number of exceptions in the smsconfigmember


Administrator response: Check that the number andsequence of exceptions correspond to the exceptiontype. Correct the configuration member and reissue theregistration request. Use a sample member for atemplate.

GTM3041E Exception Name ExcpName is not correctin smsconfig config member

Explanation: The configuration member must containa predefined list of exceptions for each exception type.

Message variables:

ExcpNameThe name of exception that is in error

smsconfigThe configuration member name


Administrator response: Check that the names of theexceptions correspond to the exception type. Correctthe configuration member and reissue the registrationrequest. Use a sample configuration member for atemplate.

GTM3042E Length of resource_type_keyword valueresource_type_value exceeds max_value inrecord registration

Explanation: The resource_type_keyword value length istoo long.

Message variables:

resource_type_keywordThe keyword that is in error

resource_type_valueThe value of the keyword that is in error

max_valueThe maximum length of the value

registrationThe registration statement that is in error


System action: The keyword value that is in error isignored and processing continues.

Administrator response: Correct the keyword valuethat is in error. Unregister and then register theregistration entry.

GTM3044E No resources found to be registered inresource_type_keyword in record registration

Explanation: The resource_type_keyword keyword doesnot contain a value.

Message variables:

resource_type_keywordThe keyword that is in error



Administrator response: Correct the keyword valuethat is in error. Reissue the registration request.

GTM3045E DKDV keyword value is not validhexadecimal number unit in recordregistration

Explanation: The DKDV keyword value must be avalid hexadecimal address.

Message variables:

unit The DKDV keyword value that is in error




GTM3046W Invalid decimal number unit_number inDKDV_keyword in record registrationignored

Explanation: The value of DKDV keyword must bedefined as a hexadecimal unit address followed by adecimal number in brackets. The decimal numberdefines how many valid unit addresses are to beregistered, starting from the first hexadecimal address.This message is generated when the value in brackets isnot a valid decimal number.

Message variables:

unit_numberThe number that is in error

DKDV_keywordThe DKDV keyword value that is in error


System action: The unit_number number that is inerror is ignored. Only the first valid hexadecimaladdress is registered. Processing continues.


GTM3050I Monitoring started for monitor $monitorCount=$countBase; User=$countUser;ID=$msgmaskID; SUBSYS=$subsys;JOBNAME=$jobname; User=$userMask}

Default=$countDefault}Exceptions=$countExceptions}

Explanation: Indicates that monitoring started for thespecified monitor. Information about optional statisticsfrom the monitor request is listed.

Message variables:

$monitorThe monitor type

$countBase(Optional) The total messages registered froma configuration member for the monitor type

$countUser(Optional) The total messages registered fromuser-defined messages for the monitor type

$msgmaskID(Optional) The unique ID for this monitor type

$subsys (Optional) The name of the subsystem withinthe monitoring type

$jobname(Optional) The job name that is associatedwith the registration

$userMask(Optional) The total messages that areregistered from user defined monitor types

$countDefault(RMF™ only, optional) The total number ofdefault monitors that are registered

$countExceptions(RMF only, optional) The total number ofexception monitors that are registered


GTM3051I Monitoring stopped for monitor $monitorID=$msgmaskID SUBSYS=$subsys

Explanation: Monitoring has stopped for the specifiedmonitor, including information about optional statisticsfrom the monitor request.

Message variables:



$msgmaskID(Optional) The unique ID for this monitor type

$subsys (Optional) The name of the subsystem withinthe monitoring type


GTM3052E Invalid %INCLUDE member formatinclude for montype subsys

Explanation: The %INCLUDE directive specified aninvalid format for the member that is included

Message variables:

include The input %INCLUDE statement

montypeThe monitor type

subsys The optional subsystem name

System action: The registration statement is ignoredand processing continue.

Administrator response: Ensure that the syntax forthe member is valid. Correct the %INCLUDE directivestatement and reissue the registration request.

GTM3052I Total count of SMS exceptions added=count

Explanation: This message specifies the total numberof registered SMS exceptions for the DSE, DPE, andCPE types.

Message variables:

count The number of registered SMS exceptions


GTM3053E %INCLUDE member is missing formontype subsys

Explanation: The %INCLUDE directive is missing thename of the include member

Message variables:




Administrator response: Ensure that the name of theinclude member is specified. Correct the %INCLUDEdirective statement and reissue the registration request.

GTM3053I Total count of SMS exceptions stopped=count

Explanation: This message specifies the total numberof unregistered SMS exceptions for the DSE, DPE, andCPE types.

Message variables:

count The number of unregistered SMS exceptions


GTM3054E %INCLUDE member member is too longfor montype subsys

Explanation: The %INCLUDE directive specified amember name that is too long

Message variables:

member The name of the include member




Administrator response: The maximum length of thename of the include member is 8 characters. Correct the%INCLUDE directive statement and reissue theregistration request.

GTM3055E %INCLUDE ddname is missing formontype subsys

Explanation: The specified %INCLUDE directive ismissing the DD name to locate the include member.

Message variables:





GTM3056E %INCLUDE ddname ddname is too longfor montype subsys

Explanation: The %INCLUDE directive specified a DDname that is too long

Message variables:

ddname The DD name where the include member islocated






GTM3057E Including duplicate member at level levelfor montype subsys

Explanation: The %INCLUDE directive is alreadyincluded for this registration entry, which can causerecursive processing.

Message variables:

member The name of the include member

level The level of inclusion for this member




Administrator response: Ensure that the name iscorrect on the %INCLUDE directive. Correct the%INCLUDE directive statement and reissue theregistration request.

GTM3058E Error reading configuration membermember from ddname for montype subsys

Explanation: The %INCLUDE member for montypeexperienced a read error.

Message variables:

member The member that is being included. Thisincludes the DD name and the member name.

ddname The DD name that is used to read the member




Administrator response: Ensure that the memberspecified by the %INCLUDE directive does exist.Correct the %INCLUDE directive statement and reissuethe registration request.

GTM3059E Invalid directive directive specified formontype subsys

Explanation: The registration process encountered adirective that is identified by the % but is notsupported.

Message variables:

directiveThe directive that was found




Administrator response: Ensure that the syntax of thedirective is valid. Correct the %INCLUDE directivestatement and reissue the registration request.

GTM3060E End of file encountered in configuration$config for $monitor $subsys

Explanation: The $config configuration file statementfor the $monitor $subsys subsystem contains a verticalbar ( | ) continuation character, but no continuationstatement exists.

Message variables:

$config The name of the configuration member


$subsys The subsystem name

System action: The configuration statement is ignored,and processing continues.

Administrator response: Correct the configurationstatement.

GTM4007I LOG DATASET PARAMETERMISSING, PARM=parameter

Explanation: The event distributor task was startedwithout the LOG1 or LOG2 data sets specified.

Message variables:

parameterIndicates the Log parameter that is missing

System action: Processing continues. Logging is notattempted.

Administrator response: Correct the data set nameparameter that is in error.

GTM4010I ITZP INITIALIZATION COMPLETED

Explanation: The event distributor initializationcompleted.


GTM4030I INTERFACE ESTABLISHED, CONSOLECOMMUNICATION AVAILABLE

Explanation: The event distributor MODIFY commandinterface is now available.


System action: Processing continues. The addressspace can now receive MODIFY commands.

GTM4032I STOP COMMAND RECEIVED, ITZPTERMINATING

Explanation: The event distributor received a STOPcommand and is ending.

System action: The address space begins theshutdown process.

GTM4033I OBJECT SERVER SENSED, SERVERname

Explanation: The event distributor detected the dataspace address space.

Message variables:

name The name of the data space address space


GTM4084E ADDRESS SPACE NOT APFAUTHORIZED, ITZP TERMINATING

Explanation: The event distributor is not APFauthorized.

System action: The address space shuts down.

Administrator response: APF authorize all thelibraries in the STEPLIB DD statement of the eventdistributor JCL.

GTM4085E INVALID DATASPACE ORIGINFOUND, ITZP TERMINATING

Explanation: The event distributor found that the dataspace was not correctly initialized or was corrupted.


Administrator response: Restart the data space andevent distributor. If the problem continues, contact IBMSoftware Support.

GTM4087E SERVER ADDRESS SPACE NOTSTARTED, ITZP TERMINATING

Explanation: The event distributor cannot locate thedata space address space.


Administrator response: Ensure that the data spaceaddress space is fully initialized on the same imagebefore starting the event distributor.

GTM4088E RETURN FROM CIB FREE,R15=return_code

Explanation: An error occurred in the eventdistributor issuing a QEDIT macro instruction.

Message variables:



Administrator response: Determine why the QEDITmacro failed. If necessary, contact IBM SoftwareSupport.

GTM4089E OPEN FAILED FOR ACC1PARM, ITZPTERMINATING, RETURNCODE(R15)=return_code

Explanation: An error occurred in the eventdistributor while opening the ACC1PARM data set.

Message variables:

return_codeThe return code from the OPEN macro


Administrator response: Determine why the OPENmacro failed. For more details, see the Event Pump forz/OS Installation and Configuration Guide. If necessary,contact IBM Software Support.

GTM4090E INSUFFICIENT VIRTUAL STORAGE,MEMBER=name, ITZP TERMINATING,RETURN CODE (R15)=return_code,REASON CODE (R0)=reason_code

Explanation: An error occurred in the eventdistributor while locating a member in the ACC1PARMdata set.

Message variables:

name The member name

return_codeThe return code from the FIND macro

reason_codeThe reason code from the FIND macro


Administrator response: Determine why the FINDmacro failed. Increase the region size of the eventdistributor address space. If necessary, contact IBMSoftware Support.


GTM4091E PERMANENT I/O ERROR IN PARMDATASET, ITZP TERMINATING,RETURN CODE (R15)=return_code,REASON CODE (R0)=reason_code

Explanation: A permanent I/O error occurred in theevent distributor locating a member in the ACC1PARMdata set.

Message variables:




Administrator response: Determine why the FINDmacro failed. For more details, see z/OS DFSMS MacroInstructions for Data Sets. If necessary, contact IBMSoftware Support.

GTM4092E FIND MACRO FAILED FOR MEMBERname, ITZP TERMINATING, RETURNCODE (R15)=return_code, REASONCODE (R0)=reason_code

Explanation: An error occurred in the eventdistributor that issued the FIND macro for the P1member against the ACC1PARM data set.

Message variables:





Administrator response: Determine why the FINDmacro failed. For more details, see z/OS DFSMS MacroInstructions for Data Sets. If necessary, contact IBMSoftware Support.

GTM4093E PARM MEMBER name NOT FOUND,ITZP TERMINATING, RETURN CODE(R15)=return_code, REASON CODE(R0)=reason_code

Explanation: The parameter member name was notfound in the ACC1PARM library.

Message variables:




System action: The data space shuts down.

Administrator response: Determine why the memberwas not found. Verify that the parameter members arein the correct library. For more details, see the MVSauthorized assembler services information in the z/OSlibrary. If necessary, contact IBM Software Support.

GTM4094E TIOT ADDRESS INVALID,ADDRESS=address, ITZPTERMINATING

Explanation: The Task Input Output Table (TIOT)address returned by the extract macro was 0. The eventdistributor did not locate the TIOT.

Message variables:

address The address name of TIOT returned by theEXTRACT macro

Administrator response: Determine why the TIOTaddress was 0. If necessary, contact IBM SoftwareSupport.

GTM4095E MODULE name NOT LOADED, ITZPTERMINATING

Explanation: The event distributor did not load thename module.

Message variables:

name The module name


Administrator response: Determine why the eventdistributor did not load the specified module. Ensurethat the STEPLIB DD concatenation contains theSGTMMODS library. This message probably indicatesan installation problem. If necessary, contact IBMSoftware Support.

GTM4110I name USING ID id

Explanation: Displays the ID characters from theACC1IDxx DD statement. The ID value defaults to 01 ifno ACC1IDxx DD statement is found. The sourcecollector, data space, and event distributor must all usethe same ID characters to find each other.

Message variables:

name The source collector, event distributor, or dataspace address space name (job or started taskname)

id The ID characters



GTM4120E ACC1XMCM: XCOMCOMMUNICATION AREA NOTESTABLISHED

Explanation: The source collector or the eventdistributor did not initialize the communication areabetween the source collector and the event distributor.


Administrator response: Determine why Event Pumpdid not initialize the communications area. If necessary,contact IBM Software Support.

GTM4121E ACC1XMCM: NAME/TOKEN CREATEFAILED FOR XCOM AREARC=return_code

Explanation: The source collector or the eventdistributor did not create the name token that isassociated with the communication area between thesource collector and the event distributor.

Message variables:

return_codeThe return code from the call to IEANTCR, thename token create routine

System action: The source collector or eventdistributor shuts down.

Administrator response: Determine why the call tothe IEANTCR routine failed. See the MVS authorizedassembler services information in the z/OS library. Ifnecessary, contact IBM Software Support.

GTM4123E ACC1XMCM: RESMGR ADD FORXCOM COMMUNICATION FAILEDRC=return_code

Explanation: The source collector or the eventdistributor did not create the resource manager that isassociated with the communication area between thesource collector and the event distributor.

Message variables:

return_codeThe return code from the RESMGR ADD call


Administrator response: Determine why the RESMGRADD macro failed. See the MVS authorized assemblerservices information in the z/OS library. If necessary,contact IBM Software Support.

GTM4124E ACC1XMCM RESMGR ROUTINELOAD FAILED FOR ACC1XRSMRC=return_code

Explanation: The source collector or the eventdistributor did not load the GTMACC52 manager that

is associated with the communication area between thesource collector and the event distributor.

Message variables:

return_codeThe return code from the LOAD macro


Administrator response: Determine why the load ofthe GTMACC52 manager failed. Ensure that theSTEPLIB DD concatenation contains the SGTMMODSlibrary. The problem might be an installation problem.If necessary, contact IBM Software Support.

GTM4125E ACC1XMCM: LINK FAILED TOACC1ID RC=return_code

Explanation: The source collector or the eventdistributor did not link to the GTMACC19 ID module.

Message variables:

return_codeThe return code from the LINK macro


Administrator response: Determine why theGTMACC19 module did not load. Ensure that theSTEPLIB DD concatenation contains the SGTMMODSlibrary. The problem might be an installation problem.If necessary, contact IBM Software Support.

GTM4126E ADDRESS SPACE TYPE IS NOTVALID

Explanation: The task issuing this error cannotidentify the type of task that is running. This messageindicates an internal error.

System action: The started address space shuts down.

Administrator response: If necessary contact IBMSoftware Support.

GTM4200I ALLOCATION SUCCESSFUL,DDNAME=ddname,S99ERROR=error_textS99INFO=reason_code, DSNAME=dsname

Explanation: The specified data set was allocated tothe named DD name by using the SVC 99(DYNALLOC) service.

Message variables:

ddname The DD name

error_textThe error information from the SVC 99 call

reason_codeThe reason code from the SVC 99 call


dsname The data set name that was allocated


GTM4207E FREE FAILED, DDNAME=ddname,RC=return_code, S99ERROR=error_text,S99INFO=reason_code

Explanation: Deallocation of the specified DD namefailed. The message displays return code informationfrom the SVC 99 (DYNALLOC) macro.

Message variables:

ddname The DD name

return_codeThe return code from the SVC 99 call




Administrator response: Determine why thedeallocation failed. See the MVS authorized assemblerservices information in the z/OS library for adescription of DYNALLOC return codes. If necessary,contact IBM Software Support.

GTM4208E ALLOCATION ERROR,DDNAME=ddname, RC=return_code,S9ERROR=error_text,S99INFO=reason_code, DSNAME=dsname

Explanation: Allocation of the specified data set failed.The message displays return code information from theSVC 99 (DYNALLOC) macro.

Message variables:

ddname The DD name

return_codeThe return code from the SVC 99 call



dsname The data set that is being allocated


Administrator response: Determine why thedeallocation failed. See the MVS authorized assemblerservices information in the z/OS library for adescription of DYNALLOC return codes. If necessary,contact IBM Software Support.

GTM4209E INVALID FUNCTION PASSED TOALLOCATE, FUNCTION=function_code

Explanation: A request that is not valid was made tothe dynamic allocation module.

Message variables:

function_codeThe hexadecimal function code that waspassed



GTM4219E MODULE name NOT LOADED. ITZPTERMINATING

Explanation: Event Pump did not load the specifiedmodule. Processing ends.

Message variables:

name The module name


Administrator response: Determine why the modulecannot be loaded. Ensure that the STEPLIB DDconcatenation contains the SGTMMODS library. Thisproblem might be an installation problem. If necessary,contact IBM Software Support.

GTM4300I ACC1TERM IN CONTROL

Explanation: The event distributor ending module isstopping the event distributor.


GTM4303W LATCHES NOT PURGED, LATCHPURGE RC=return_code, TERMINATIONCONTINUING

Explanation: No latches were found during thestopping of the event distributor.

The ending process continues.

Message variables:


System action: The shutdown process continues.


GTM4439E CELL FREE FAILED, CELLADDR=address, RC=return_code

Explanation: An error occurred during the call to theCSRPFRE function to release a cell in the data space.

Message variables:


address The address of the cell that is being released

return_codeThe return code from the call to the CSRPFREfunction

System action: Processing continues. The results areunpredictable.

Administrator response: Determine why the call tothe CSRPFRE function failed. See the MVS authorizedassembler services information in the z/OS library. Ifnecessary, contact IBM Software Support.

GTM4459E CELL GET FAILED, RC=return_code

Explanation: An error occurred during the call to theCSRPGET function to obtain a cell in the data space.

Message variables:

return_codeThe return code from the call to the CSRPGETfunction


Administrator response: Determine why the call tothe CSRPGET function failed. See the MVS authorizedassembler services information in the z/OS library. Ifnecessary, contact IBM Software Support.

GTM4485I QUEUE queue HAS EXCEEDED percentPERCENT OF CAPACITY

Explanation: A queue exceeded the threshold valuethat is assigned to it. This message is initially issuedwhen a queue reaches 50% of capacity and again whenthe queue reaches 60%. This message typically indicatesthat the communication between the event distributorand the MVS Listener component on the Windowssystem is not functioning correctly.

Message variables:

queue The name of the queue

percent The current percentage value that is beingexceeded, either 50% or 60%

System action: Processing continues. When the queuereaches 100%, new records cannot be added to thequeue and are discarded.

Administrator response: Check the event distributorjob log for messages that indicate a problem with thecommunication.

GTM4486W QUEUE queue HAS EXCEEDED percentPERCENT OF CAPACITY

Explanation: A queue exceeded the threshold valuethat is assigned to it. This message is initially issuedwhen a queue reaches 70% of capacity, and again whenthe queue reaches 80% and 90%. This message typically

indicates that the communication between the eventdistributor and the MVS Listener component on theWindows system is not functioning correctly. Thismessage indicates that the situation is approaching apoint where data can be lost.

Message variables:


percent The current percentage value that is beingexceeded is either 70%. 80%, or 90%

System action: Processing continues. When the queuereaches 100%, new records cannot be added to thequeue and are discarded.

Administrator response: Check the event distributorjob log and look for messages that indicate a problemwith the communication.

GTM4495E SUBSEQUENT RECORDS TOQID=queue WILL BE DISCARDED

Explanation: This message is issued subsequent to theGTM4499E message, which indicates that a queue isfull. This message indicates data is lost. This messageusually indicates that the communication between theevent distributor and the MVS Listener component onthe Windows system is not functioning correctly.

Message variables:


System action: No more records can be added to thequeue until the full queue condition is resolved.

Administrator response: Check the event distributorjob log and look for messages that indicate a problemwith the communication.

GTM4497E INVALID QUEUE FOUNDADDR=address, ALERT=alert,HEADER=data

Explanation: When accessing a queue, the issuingaddress space found that the queue header was notcorrectly initialized.

Message variables:

address The address of the queue header in the dataspace

alert The ALERT of the queue in the data space

data The current data in the queue header eyecatcher


Administrator response: Determine why the queuewas not initialized. Typically, the data space wasrestarted, and the address space that creates therequired queue is not started. If necessary, contact IBMSoftware Support.


GTM4498E INVALID CELL ADDRESS RECEIVEDADDRESS=address, ALERT=alert

Explanation: When accessing a cell in a queue, theissuing address space found that the cell header wasnot correctly initialized.

Message variables:

address The address of the cell header in the dataspace

alert The ALERT of the cell in the data space


Administrator response: Determine why the queuewas not initialized. Typically, the data space wasrestarted and the address space that creates therequired queue is not started. If necessary, contact IBMSoftware Support.

GTM4499E QUEUE FULL, ID=queue_name QADDRESS=queue_header ALERT=alert,DATA=address

Explanation: When adding a cell to the specifiedqueue, the issuing address space found that the queuewas full.

Message variables:

queue_nameThe name of the queue that is full

queue_headerThe address of the queue header in the dataspace

alert The ALERT of the cell in the data space

address The address of the cell that was being added

System action: No more records can be written to thequeue until a subsequent GTM4515I message is issued.

Administrator response: Increase the queue size forthe specified queue. The mainframe components mustbe restarted for a change of the queue size to becomeeffective. If the problem continues, contact IBMSoftware Support.

GTM4515I QUEUE queue IS NOW AVAILABLE,RECORDS LOST =number

Explanation: This message is issued as a result of aqueue full condition being resolved. This messageoccurs when the queue utilization is below 40% of totalcapacity or as a result of a QUEUE RESET command.

Message variables:


number The number of records that were discarded asa result of the queue full condition

System action: The queue full condition is resolvedand subsequent records can be added to the queue.

Administrator response: This message indicates that aprior condition was resolved.

GTM4519E INVALID QUEUE FOUNDADDR=address, ALERT=alert,HEADER=data

Explanation: When accessing a queue, the issuingaddress space found that the queue header was notcorrectly initialized.

Message variables:

address The address of the queue header in the dataspace

alert The ALERT of the queue in the data space

data The current data in the queue headereye-catcher


Administrator response: Determine why the queuewas not initialized. Typically, the data space wasrestarted, and the address space that creates therequired queue is not started. If necessary, contact IBMSoftware Support.

GTM4522W INVALID QUEUE SIZEENCOUNTERED, TYPE=queue_name,VALUE=value, DEFAULTING TOdefault_value BLOCK(S)

Explanation: When initializing a queue, the issuingaddress space found that the queue size specificationwas not valid.

Message variables:

queue_nameThe queue name

value The value input

default_valueThe default value used

System action: Processing continues. The queue sizethat is used to create the queue is the default value.

Administrator response: Correct the parameter valuefor the specified queue size. If necessary, contact IBMSoftware Support.

GTM4538E STORAGE OBTAIN FAILED, QUEUENOT ALLOCATED, RC=return_code

Explanation: When initializing a queue, a GETMAINrequest for the queue storage failed.

Message variables:


return_codeThe return code from the STORAGE OBTAINfunction

System action: Processing continues. Results areunpredictable.

Administrator response: Determine why theGETMAIN request failed. If necessary increase theregion size of the data space or reduce the queue size.Contact IBM Software Support.

GTM4539E INVALID QUEUE TYPE REQUESTED,QTYPE=queue_type

Explanation: When initializing a queue, theACC1QCRE routine was called with a queue type thatis not valid.

Message variables:

queue_typeThe queue type indicator that was passed



GTM4559E INVALID NULL DATA LENGTHSUPPLIED

Explanation: A call was made to the ACC1QLPTroutine with a data element with a length of 0.



GTM4575E BUFFER STORAGE UNAVAILABLE,LENGTH REQUESTED=length

Explanation: While retrieving a record from a queue,the ACC1QLGT module did not obtain sufficientstorage to hold the record.

Message variables:

length The length of the storage requested


Administrator response: The error indicates that thesource collector exhausted the available virtual storage.Use the REGION parameter of the JCL EXEC statementto increase the amount of available virtual storage. Ifthe problem continues, contact IBM Software Support.

GTM4576E CONTINUATION CELL NULL,CELLADDR=cell_address,QADDR=queue_address, SEQUENCEDATA=cell_size

Explanation: While retrieving a record from a queuespanning multiple cells within the data space, theACC1QLGT module found that the current cellindicated a continuation cell, but the next cell addresswas 0.

Message variables:

cell_addressThe address of the cell in the data space

queue_addressThe address of the queue in the data space

cell_size The cell size field from the last cell processed



GTM4577E CELL LENGTH ERROR,CELLADDR=cell_addressQADDR=queue_address, SEQUENCEDATA=field, LENGTH=length

Explanation: While retrieving a record from a queuespanning multiple cells within the data space, theACC1QLGT module found a cell that had an incorrectdata length specified.

Message variables:



field The sequence field from the cell

length The length of data within the cell



GTM4578E CELL OUT OF SEQUENCE,CELLADDR=cell_addressQADDR=queue_address SEQUENCEDATA=field EXPECTING=seq_number

Explanation: While retrieving a record from a queuespanning multiple cells within the data space, theACC1QLGT module found a cell that had an incorrectsequence number.

Message variables:




field The sequence field from the cell

seq_numberThe expected sequence number



GTM4579E INVALID CELL ADDRESS FOUND,CELLADDR=cell_addressQADDR=queue_address

Explanation: While retrieving a record from a queuespanning multiple cells within the data space, theACC1QLGT module found a cell that had an incorrectheader.

Message variables:





GTM4600I EXTENDED RECOVERYENVIRONMENT ESTABLISHED

Explanation: The issuing address space successfullycreated the automatic recovery environment.


GTM4601I STANDBY ADDRESS SPACEWAITING FOR TAKEOVER FROMaddress_space

Explanation: The issuing address space detected thatit is running as a backup to the current active addressspace and is standing by to take over processing if theactive address space fails.

Message variables:

address_spaceThe name of the matching active addressspace

System action: Initialization of the standby addressspace waits for either a takeover or a shutdownrequest.

GTM4602I SHUTDOWN OF STANDBY ADDRESSSPACE REQUESTED

Explanation: The active address space is stoppingnormally and requested that the standby address spacealso shut down.

System action: The standby address space shutsdown.

GTM4603I TAKEOVER BY STANDBY ADDRESSSPACE REQUESTED

Explanation: The active address space requested thatthe standby address space take over its operation. Thisprocess can be initiated either by operator command orautomatically if the active address space endedabnormally.

System action: The standby address space resumesinitialization and assumes the role of the primaryaddress space.

Administrator response: Determine if this takeovershould have occurred. If the original active addressspace ended abnormally, determine why. If necessary,contact IBM Software Support.

GTM4604I SWITCH TO STANDBY ADDRESSSPACE REQUESTED

Explanation: The active address space requested thatthe standby address space take over its operation. Thisprocess can be initiated by operator command.

System action: The standby address space resumesinitialization and assumes the role of the primaryaddress space. The primary address space shuts down.

GTM4605I DUPLICATE STANDBY ADDRESSSPACE standby_name IS CURRENTLYWAITING FOR ADDRESS SPACEactive_name

Explanation: A second standby address space started.Only one standby address space can be active. Thesecond instance ends.

Message variables:

standby_nameThe current standby address space

active_nameThe current active address space name


Administrator response: Determine why the secondstandby address space was started.


GTM4608E UNABLE TO LOAD RESOURCEMANAGER INTO ECSA RC=return_code

Explanation: The issuing address space did not loadthe extended AOPXRRSM recovery resource managerinto extended common service area (ECSA) storage.

Message variables:



Administrator response: Determine why the modulecannot be loaded. Ensure that the STEPLIB DDconcatenation contains the SGTMMODS library. Thismessage often indicates an installation problem. Ifnecessary, contact IBM Software Support.

GTM4609E NAME TOKEN CREATE FORSTANDBY ADDRESS SPACE FAILED.RC=return_code

Explanation: The issuing address space did not createthe name token that is associated with the addressspace when in standby mode.

Message variables:

return_codeThe return code from the call to the IEANTCRroutine


Administrator response: Determine why the call tothe IEANTCR, the name token create routine, failed.See the MVS authorized assembler services informationin the z/OS library. If necessary, contact IBM SoftwareSupport.

GTM4610E INVALID POST CODE RECEIVED,CODE=return_code

Explanation: The standby recovery manager in theissuing address space cannot determine the reason forthe request.

Message variables:

return_codeThe value from the event control block (ECB)on which the recovery manager was waiting



GTM4611E NAME TOKEN CREATE FORPRIMARY ADDRESS SPACE FAILED.RC=return_code

Explanation: The issuing address space did not createthe name token that is associated with the addressspace.

Message variables:




GTM4612E NAME TOKEN CREATE FORRESOURCE MANAGER FAILED.RC=return_code

Explanation: The issuing address space cannot createthe name token that is associated with the recoveryresource manager for the address space.

Message variables:




GTM4613E RESOURCE MANAGER CREATEFAILED. RC=return_code

Explanation: The issuing address space cannot createthe recovery resource manager for the address space.

Message variables:

return_codeThe return code from the RESMGR ADDmacro


Administrator response: Determine why the RESMGRADD macro failed. See the MVS authorized assemblerservices information in the z/OS library. If necessary,contact IBM Software Support.


GTM4614E UNABLE TO LOAD RESOURCEMANAGER INTO ECSA

Explanation: The issuing address space cannot loadthe recovery resource manager into extended commonservice area (ECSA) storage.


Administrator response: Determine the cause of thefailure. If necessary, contact IBM Software Support.

GTM4615E UNABLE TO OBTAIN ECSA STORAGEFOR RESOURCE MANAGER

Explanation: The issuing address space cannot use aGETMAIN request to obtain sufficient storage inextended common service area (ECSA) storage to holdthe recovery resource manager.


Administrator response: Determine the cause of thefailure. If necessary, contact IBM Software Support.

GTM4616E AMODE INVALID FOR MODULEAOPXRRSM

Explanation: The recovery manager for the issuingaddress space determined that the resource recoverymanager module, the AOPXRRSM module, is notlink-edited as AMODE 31.


Administrator response: Determine why theAOPXRRSM module linked incorrectly. If necessary,contact IBM Software Support.

GTM4617E UNABLE TO LOAD RESOURCEMANAGER

Explanation: The issuing address space cannot loadAOPXRRSM, the resource recovery manager module.


Administrator response: Determine why theAOPXRRSM module cannot be loaded. If necessary,contact IBM Software Support.

GTM4618E LOAD OF MODULE module_nameFAILED, RC=return_code

Explanation: The issuing address space cannot loadthe specified module.

Message variables:

module_nameThe module name



Administrator response: Determine why the specifiedmodule cannot be loaded. If necessary, contact IBMSoftware Support.

GTM4619E UNABLE TO OBTAIN WORKINGSTORAGE

Explanation: The recovery manager in the issuingaddress space cannot obtain working storage.


Administrator response: The error indicates that thesource collector exhausted the available virtual storage.Use the REGION parameter of the JCL EXEC statementto increase the amount of virtual storage that isavailable. If the problem continues, contact IBMSoftware Support.

GTM4620I EXTENDED RECOVERYENVIRONMENT SUCCESSFULLYREMOVED

Explanation: The recovery manager successfullyended.


GTM4628E LOAD OF MODULE module_nameFAILED, RC=return_code

Explanation: The issuing address space cannot loadthe specified module.

Message variables:




Administrator response: Determine why the specifiedmodule cannot be loaded. If necessary, contact IBMSoftware Support.


Explanation: The recovery manager shutdown modulein the issuing address space cannot obtain workingstorage.




GTM4630I XRCMD COMMAND COMPLETE

Explanation: The XRCMD command completed.


GTM4637E AOPXRCMD GETMAIN FAILED FORWORKING STORAGE

Explanation: The recovery manager commandprocessor in the issuing address space cannot obtainworking storage.

System action: The command is not processed.


GTM4638E DATA TYPE MISSING FROM XRCMDCOMMAND

Explanation: The target address space for the XRCMDcommand is not valid; specify ACTIVE, STANDBY, orBOTH.


Administrator response: Correct the XRCMDcommand operands and enter the command again. Seez/OS DFSMS Macro Instructions for Data Sets for moreinformation.

GTM4639E address_space IS INVALID FOR XRCMDCOMMAND

Explanation: The action or target address space for theXRCMD command is not valid. Specify SHUT,TAKEOVER, or SWITCH for the action and PUMP,SRVR, or DSPC for the target address space.

Message variables:

address_spaceThe name of the target or action address space


Administrator response: Correct the XRCMDcommand operands and enter the command again. Seethe Event Pump for z/OS Installation and ConfigurationGuide for more information.

GTM4996E name NOT LOADED, ITZPTERMINATING

Explanation: The issuing address space cannot loadthe specified message module.

Message variables:

name The name of the message module that was notloaded


Administrator response: Determine why the specifiedmessage module cannot be loaded. Ensure that theSGTMMODS library is specified in the STEPLIBconcatenation. If necessary, contact IBM SoftwareSupport.

GTM4997W FREEMAIN FAILED,MODULE=ACC1WTO

Explanation: A FREEMAIN request failed in theACC1WTO module.


Administrator response: Determine why theFREEMAIN request failed. If necessary, contact IBMSoftware Support.

GTM4998W MESSAGE number IS MISSING

Explanation: The specified message number was notfound in the message module.

Message variables:

number The message number that was not found



GTM4999W MESSAGE number IS INVALID

Explanation: The specified message number is notnumeric and therefore is not valid.

Message variables:

number The message number that was not valid



GTM5000I DATA SPACE INITIALIZATIONSTARTING

Explanation: Data space initialization is starting.


GTM5002I PROCESSING PARMLIB MEMBER:name

Explanation: The data space is processing thespecified initialization member from the parameter dataset.

Message variables:




GTM5005I INVALID PARM PASSED,PROCESSING CONTINUING,PARM=parameter

Explanation: The specified parameter is not valid forthe data space.

Message variables:

parameterThe parameter in error


Administrator response: Correct or remove theparameter that is not valid. See the Event Pump forz/OS Installation and Configuration Guide for moreinformation. If necessary, contact IBM SoftwareSupport.

GTM5010I ITZP address_space INITIALIZATIONCOMPLETE

Explanation: The specified address space completedits initialization.

Message variables:

address_spaceSpecifies the data space or event distributor


GTM5030I MODIFY INTERFACE ESTABLISHED,CONSOLE COMMUNICATIONAVAILABLE

Explanation: The data space is ready to acceptMODIFY and STOP commands.


GTM5031I COMMAND ACCEPTED:text

Explanation: The command that was entered wasaccepted.

Message variables:

text The command text


GTM5040I OBJECT SERVER TERMINATIONCOMPLETE, RC=return_code

Explanation: The data space ended with the specifiedreturn code.

Message variables:



GTM5084E ADDRESS SPACE NOT APFAUTHORIZED, DATA SPACE SERVERTERMINATING

Explanation: The data space server stopped becausethe data space is not APF authorized.


Administrator response: Check that all the loadlibraries in the STEPLIB concatenation are APFauthorized. If necessary, contact IBM Software Support.

GTM5087E MODULE: module_name NOT LOADED,OBJECT SERVER TERMINATING

Explanation: The specified module cannot be loaded.

Message variables:



Administrator response: Determine why the modulecannot be loaded. Ensure that the SGTMMODS libraryis specified in the STEPLIB concatenation. If necessary,contact IBM Software Support.

GTM5088E RETURN FROM CIB FREE,R15=return_code

Explanation: A return code other than 0 was receivedfrom the QEDIT macro when it tried to release the CIBassociated with a MODIFY or STOP command.Processing continues.

Message variables:

return_codeThe return code from the QEDIT macro


Administrator response: Determine why the QEDITmacro issued a return code other than 0. See the MVSauthorized assembler services information in the z/OSlibrary. If necessary, contact IBM Software Support.

GTM5089E OPEN FAILED FOR ACC1PARM,OBJECT SERVER TERMINATING,RETURN CODE (15)=return_code

Explanation: The OPEN of the ACC1PARM DD failed.

Message variables:

return_codeThe return code from the OPEN macro


Administrator response: Determine why the OPENmacro failed. See z/OS DFSMS Macro Instructions forData Sets. If necessary, contact IBM Software Support.


GTM5090E INSUFFICIENT VIRTUAL STORAGE,MEMBER=name, ITZP TERMINATING,RETURN CODE (R15)=return_code,REASON CODE (R0)=reason_code

Explanation: While processing the ACC1PARMparameter library, the FIND macro returned an error.

Message variables:

name The member name that is being processed




Administrator response: Determine why the FINDmacro failed. See z/OS DFSMS Macro Instructions forData Sets. If necessary, contact IBM Software Support.

GTM5091E PERMANENT I/O ERROR IN PARMDATASET, ITZP TERMINATING,RETURN CODE (R15)=return_code,REASON CODE (R0)=reason_code


Message variables:




Administrator response: Determine why the FINDmacro failed. See z/OS DFSMS Macro Instructions forData Sets. If necessary, contact IBM Software Support.

GTM5092E FIND MACRO FAILED FOR MEMBERmember_name, DATA SPACE SERVERTERMINATING, RETURN CODE(15)=return_code, REASON CODE(0)=reason_code


Message variables:

member_nameThe member name that is being processed

return_codeThe reason code from the FIND macro



Administrator response: Determine why the FIND

macro failed. See z/OS DFSMS Macro Instructions forData Sets. If necessary, contact IBM Software Support.

GTM5093E PARM MEMBER member_name NOTFOUND, OBJECT SERVERTERMINATING, R15=return_code,R0=reason_code

Explanation: While processing the ACC1PARMparameter library, the FIND macro cannot locate theindicated member name.

Message variables:

member_nameThe member name that is being processed

return_codeThe reason code from the FIND macro



Administrator response: Determine why the membername was not found. Verify that the value that isspecified on the PARM statement for the GTMDSPCprogram is the name of a member in the library that ispointed to by the ACC1PARM DD statement. See z/OSDFSMS Macro Instructions for Data Sets. If necessary,contact IBM Software Support.

GTM5094E TIOT ADDRESS INVALID,ADDRESS=address, OBJECT SERVERTERMINATING

Explanation: The Task Input Output Table (TIOT)address that was returned by the EXTRACT macro was0.

Message variables:

address The address that was returned



GTM5095E MODULE module_name NOT LOADEDITZP TERMINATING

Explanation: The specified module cannot be loaded.The issuing address space stops.

Message variables:


System action: The data space stops.

Administrator response: Determine why the modulecannot be loaded. Ensure that the STEPLIBconcatenation contains the SGTMMODS library. Ifnecessary, contact IBM Software Support.


GTM5096E ACC1PARM DD STATEMENTMISSING OBJECT SERVERTERMINATING

Explanation: The ACC1PARM parameter library DDstatement was missing. The data space address spaceended.


Administrator response: Determine why theACC1PARM DD statement cannot be located. Ifnecessary, contact IBM Software Support.

GTM5098W DEFAULT PARM MEMBER NOTENTERED, DEFAULTING TOMEMBER: SYSIN

Explanation: Because a member name parameter wasnot entered on the data space JCL EXEC statement, thedefault member name of SYSIN is used.


Administrator response: Specify a member name onthe JCL EXEC statement for the data space if you wantto use a member name other than SYSIN for the dataspace startup parameters.

GTM5099W PARM TOO LONG, FORCINGLENGTH OF 8

Explanation: A member name parameter on the JCLEXEC statement was longer than 8 characters. Theparameter is truncated to 8 characters.

System action: The parameter is truncated to 8characters

Administrator response: Correct the member nameparameter on the JCL EXEC statement in the data spacestartup JCL.

GTM5101I DATA SPACE CREATED, SIZE=size,ORIGIN=address

Explanation: The data space was successfully created.

Message variables:

size The size of the data space in bytes

address The original address of the data space


GTM5114E DATASPACE SIZE NOT ENTERED,DEFAULTING TO size BYTES

Explanation: The data space size was not specified inthe input parameters. The default size is used.

Message variables:

size The default size used for the data space

System action: The default size is used.

Administrator response: Specify the data space size(in bytes) in the data space input parameters if youwant to use a value other than the default. See theEvent Pump for z/OS Installation and Configuration Guidefor more information.

GTM5115E INVALID DATASPACE SIZEENCOUNTERED, VALUE=size,DEFAULTING TO default_size BYTES

Explanation: The data space size that is specified inthe input parameters is not valid. The default value isused.

Message variables:

size The data space size that is entered

default_sizeThe default size that is used for the data space

System action: The default size is used.

Administrator response: Correct the data space sizeentered in the input parameters. See the Event Pump forz/OS Installation and Configuration Guide for moreinformation.

GTM5116E DATASPACE CREATE FAILED,RC=return_code, SERVERTERMINATING

Explanation: The DSPSERVE CREATE macro used tocreate the data space issued a return code other than 0.

Message variables:

return_codeThe return code from DSPSERVE CREATEmacro


Administrator response: Determine why the dataspace create function failed. See the MVS authorizedassembler services information in the z/OS library. Ifnecessary, contact IBM Software Support.

GTM5117E ALESERV FAILED, RC=return_code,OBJECT SERVER TERMINATING

Explanation: The ALESERV ADD macro that is usedto create the data space issued a return code other than0.

Message variables:

return_codeThe return code from ALESERV ADD macro


Administrator response: Determine why the macrocall failed. See the MVS authorized assembler servicesinformation in the z/OS library. If necessary, contactIBM Software Support.


GTM5118E NAME/TOKEN CREATE FAILED,RC=return_code OBJECT SERVERTERMINATING

Explanation: The call to IEANTCR, the name tokencreate routine, to create the name token that isassociated with the data space failed.

Message variables:



Administrator response: Determine why the call toIEANTCR, the name token create routine, failed. Seethe MVS authorized assembler services information inthe z/OS library. If necessary, contact IBM SoftwareSupport.

GTM5119E SYSEVENT FAILED, RC=return_code,OBJECT SERVER TERMINATING

Explanation: While making itself non-swappable, theSYSEVENT TRANSWAP macro issued a return codeother than 0.

Message variables:

return_codeThe return code from the SYSEVENT macro


Administrator response: Determine why the call tothe SYSEVENT macro failed. See the MVS authorizedassembler services information in the z/OS library. Ifnecessary, contact IBM Software Support.

GTM5120I OBJECT SERVER DISCONNECTEDFROM DATASPACE

Explanation: The data space address spacedisconnected from the data space. This message is astandard message during the shutdown of the eventdistributor.


GTM5121I DATA SPACE DELETED

Explanation: The data space address space deleted thedata space environment.


GTM5127E DATA SPACE NOT DELETED,RC=return_code, DATASPACE WILL BEDELETED AT ADDRESS SPACETERMINATION, SHUTDOWNCONTINUING

Explanation: The data space environment deletionfailed.

Message variables:

return_codeThe return code from the DSPSERVE DELETEmacro


Administrator response: Determine why the dataspace delete process failed. See the MVS authorizedassembler services information in the z/OS library. Ifnecessary, contact IBM Software Support.

GTM5128E ALESERV DELETE FAILED, SERVERSTILL CONNECTED, RC=return_code,SHUTDOWN CONTINUING

Explanation: While deleting the data space, theALESERVE DELETE macro issued a return code otherthan 0.

Message variables:

return_codeThe return code from the ALESERVE DELETEmacro


Administrator response: Determine why the dataspace deletion failed. See the MVS authorizedassembler services information in the z/OS library. Ifnecessary, contact IBM Software Support.

GTM5129E CLIENT jobname STILL ACTIVE,OBJECT SERVER WILL NOT SHUTDOWN UNTIL ALL CLIENTS ARETERMINATED

Explanation: An attempt was made to stop the dataspace while either the event distributor or sourcecollector was still active.

Message variables:

jobname The job name of the event distributor orsource collector that was found active

System action: The shutdown request is ignored.

Administrator response: Ensure that the sourcecollector and event distributor are both stopped beforeattempting to shut down the data space address space.

GTM5156E CELL POOL EXTEND FAILED,RC=return_code

Explanation: The call to create the cell pool extentwithin the data space failed.

Message variables:


return_codeThe return code from the call to the CSRPEXPservice


Administrator response: Determine why the call tothe CSRPEXP service failed. See the MVS authorizedassembler services information in the z/OS library. Ifnecessary, contact IBM Software Support.

GTM5157E INVALID QUEUE SIZEENCOUNTERED, TYPE=queue_typeVALUE=value, DEFAULTING TOdefault_value BLOCKS

Explanation: The queue size parameter for thespecified queue is not valid.

Message variables:

queue_typeThe queue type

value The value entered


System action: Processing continues. The defaultvalue is used.

Administrator response: Correct the queue sizeparameter for the specified queue. See the Event Pumpfor z/OS Installation and Configuration Guide for moreinformation about event distributor startup parameters.If necessary, contact IBM Software Support.

GTM5158W QUEUE SIZE NOT ENTERED,TYPE=queue_type DEFAULTING TOdefault_value BLOCKS

Explanation: A queue size parameter was not enteredfor the specified queue. The default size is entered.

Message variables:

queue_typeThe queue type



Administrator response: Correct the queue sizeparameter for the specified queue. See the Event Pumpfor z/OS Installation and Configuration Guide for moreinformation about event distributor startup parameters.If necessary, contact IBM Software Support.

GTM5159E CELL POOL CREATE FAILED,RC=return_code

Explanation: The call to the CSRPBLD module tocreate the cell pool failed.

Message variables:

return_codeThe return code from the call to the CSRPBLDmodule


Administrator response: Determine why the call tothe CSRPBLD module failed. See the MVS authorizedassembler services information in the z/OS library. Ifnecessary, contact IBM Software Support.

GTM5161I IPL SENSED

Explanation: This is the first time the address spacewas run with this ACC1ID DD statement setting sincethe last IPL.


GTM5175E NAME/TOKEN CREATE FAILED,RC=return_code TOKEN=namePROCESSING CONTINUING,MULTIPLE LINKAGE INDEXES WILLBE CREATED

Explanation: The call to IEANTCR, the name tokencreate routine, to create the name token that isassociated with the linkage index for the data spacefailed. Because the linkage index information cannot besaved, each JCL EXEC statement of the data space usesan additional linkage index from the linkage indexesavailable.

Message variables:


name The token name that was being created



GTM5176E LXRES FAILED, RC= return_code,OBJECT SERVER TERMINATING

Explanation: The system cannot create a systemlinkage index for the data space.

Message variables:

return_codeThe return code from the LXRES macro



Administrator response: Determine why the LXRESmacro failed. See the MVS authorized assemblerservices information in the z/OS library. If necessary,contact IBM Software Support.

GTM5177E AXSET FAILED, RC=return_code,OBJECT SERVER TERMINATING

Explanation: The system cannot set the authorizationindex for the data space.

Message variables:

return_codeThe return code from the AXSET macro


Administrator response: Determine why the AXSETmacro failed. See the MVS authorized assemblerservices information in the z/OS library. If necessary,contact IBM Software Support.

GTM5178E ETCON FAILED, RC=return_code,OBJECT SERVER TERMINATING

Explanation: The system cannot connect the entrytable for the data space to the linkage index.

Message variables:

return_codeThe return code from the ETCON macro


Administrator response: Determine why the ETCONmacro failed. See the MVS authorized assemblerservices information in the z/OS library. If necessary,contact IBM Software Support.

GTM5179E ETCRE FAILED, RC=return_code,OBJECT SERVER TERMINATING

Explanation: The system cannot create the entry tablefor the data space.

Message variables:

return_codeThe return code from the ETCRE macro


Administrator response: Determine why the ETCREmacro failed. See the MVS authorized assemblerservices information in the z/OS library. If necessary,contact IBM Software Support.

GTM5199E LATCH SET CREATE FAILED,RC=return_code, OBJECT SERVERTERMINATING

Explanation: The system cannot create the latch setthat is associated with the cells in the data space.

Message variables:

return_codeThe return code from the call to the ISGLCRTservice


Administrator response: Determine why the ISGLCRTservice failed. See the MVS authorized assemblerservices information in the z/OS library. If necessary,contact IBM Software Support.

GTM5300I ACC1DTRM, SERVER TERMINATION,IN CONTROL

Explanation: The data space address space endednormally.

System action: The event distributor shuts

GTM5399E DATASPACE DELETE FAILED,RC=return_code

Explanation: ACC1DSDE, the data space deletemodule, issued a return code other than 0.

Message variables:

return_codeThe return code from the ACC1DSDE module


Administrator response: Determine why the dataspace deletion failed. Examine the data space outputfor prior messages. If necessary, contact IBM SoftwareSupport.

GTM5400I DISCOVERING OF ITZP PARTNERSSTARTED

Explanation: The discovery of the Event Pumppartners was started.


GTM5401E ERROR WRITING GLOBAL VARIABLEvariable_name

Explanation: An error occurred when writing thevariable_name global variable.

Message variables:

variable_nameThe global variable that is being written

System action: Actions depend on the variable that isbeing written. In some cases, the source collector stops.

Administrator response: Restart the source collector. Ifthe error continues, contact IBM Software Support.


GTM5402E ERROR READING GLOBALVARIABLE variable_name

Explanation: An error occurred reading thevariable_name global variable.

Message variables:

variable_nameThe global variable that is being read

System action: Actions depend on the variable that isbeing read. In some cases, the source collector stops.


GTM5403E ERROR DURING PUBLISHING ITZPEXISTENCE

Explanation: An error occurred during the publishingof the Event Pump existence.



GTM5404E ERROR DURING DISCOVERY OFPARTNERS

Explanation: An error occurred during the discoveryof partners.



GTM5405I ITZP PARTNER ON ip_address PORTport DETECTED

Explanation: The Event Pump partner on the port portwith an IP address of ip_address was detected.

Message variables:

port The port on which the Event Pump partnerwas detected

ip_addressThe IP address for which the Event Pumppartner was detected


GTM5406I DISCOVERY OF ITZP PARTNERSCOMPLETED

Explanation: The discovery of the Event Pumppartners was completed.


GTM5407E HTTP SERVER : TCP/IP PORT NOTSPECIFIED

Explanation: A TCP/IP port was not specified for theHTTP server.


Administrator response: Specify the source collectorPORT parameter and then restart it. If the errorcontinues, contact IBM Software Support.

GTM5408I HTTP SERVER : SERVICE STARTED

Explanation: Service was started for the HTTP server.


GTM5409E HTTP SERVER : INVALID TCP/IPPORT NUMBER

Explanation: The HTTP server received an invalidTCP/IP port number.


Administrator response: Correct the source collectorPORT parameter and restart it. If the error continues,contact IBM Software Support.

GTM5410E TCP/IP JOB NAME NOT SPECIFIED

Explanation: The TCPIP_JOBNAME parameter is notspecified. The source collector attempted to obtain thename of the TCP/IP procedure dynamically, but it wasnot available.


Administrator response: Specify theTCPIP_JOBNAME parameter and restart the sourcecollector. If the error continues, contact IBM SoftwareSupport.

GTM5411E HTTP SERVER : SOCKET INITIALIZECALL FAILED WITH RC=return_code,RS=reason_code

Explanation: The call to initialize the socket failed.

Message variables:

return_codeThe return code resulting from the attempt toinitialize the Socket.

reason_codeThe reason code resulting from the attempt toinitialize the Socket.

System action: Actions depend on the request that isbeing processed. In some cases, the source collectorstops.

Administrator response: Check the system TCP/IPconfiguration. Restart the source collector. If the error


continues, contact IBM Software Support.

GTM5412I HTTP SERVER : NO CLEANUPNEEDED FOR ID = socket_id

Explanation: No cleanup was needed for the socket_idsocket.

Message variables:

socket_idThe ID of the socket


GTM5413E HTTP SERVER : SOCKET NOTCREATED, RC=return_code,RS=reason_code

Explanation: A socket was not created.

Message variables:

return_codeThe return code resulting from the attempt tocreate a socket.

reason_codeThe reason code resulting from the attempt tocreate a socket.


Administrator response: Check the system TCP/IPconfiguration. Restart the source collector. If the errorcontinues, contact IBM Software Support.

GTM5414E HTTP SERVER : UNABLE TO SETSOCKET OPTIONS, RC=return_code,RS=reason_code

Explanation: The HTTP server cannot set the socketoptions.

Message variables:

return_codeThe return code resulting from the attempt toset the socket options.

reason_codeThe reason code resulting from the attempt toset the socket options.



GTM5415E HTTP SERVER : UNABLE TO BINDSOCKET, RC=return_code, RS=reason_code

Explanation: The HTTP server cannot bind the socket.

Message variables:

return_codeThe return code resulting from the attempt tobind the socket.

reason_codeThe reason code resulting from the attempt tobind the socket.



GTM5416E HTTP SERVER : UNABLE TORETRIEVE CLIENT ID, RC=return_code,RS=reason_code

Explanation: The HTTP server cannot retrieve theClient ID.

Message variables:

return_codeThe return code resulting from the attempt toretrieve the Client ID

reason_codeThe reason code resulting from the attempt toretrieve the Client ID



GTM5417E HTTP SERVER : UNABLE TO ENTERIN LISTEN MODE, RC=return_code,RS=reason_code

Explanation: The HTTP server cannot enter intoLISTEN mode.

Message variables:

return_codeThe return code resulting from the attempt toenter into LISTEN mode

reason_codeThe reason code resulting from the attempt toenter into LISTEN mode



GTM5418E HTTP SERVER : UNABLE TO CLOSESOCKET socket_id, RC=return_code,RS=reason_code

Explanation: The HTTP server cannot close the socket.

Message variables:


socket_idThe ID of the socket for which the CLOSE wasissued

return_codeThe return code resulting from the attempt toclose the socket

reason_codeThe reason code resulting from the attempt toclose the socket



GTM5419E HTTP SERVER : UNABLE TOTERMINATE SOCKET SET,RC=return_code, RS=reason_code

Explanation: The HTTP server cannot stop the socketset.

Message variables:

return_codeThe return code resulting from the attempt tostop the socket set

reason_codeThe reason code resulting from the attempt tostop the socket set



GTM5420E HTTP SERVER : UNABLE TORESOLVE LOCAL HOST IP ADDRESS,RC=return_code, RS=reason_code

Explanation: The HTTP server cannot resolve the localhost IP address.

Message variables:

return_codeThe return code resulting from the attempt toresolve the local host IP address

reason_codeThe reason code resulting from the attempt toresolve the local host IP address



GTM5421E HTTP SERVER : UNABLE TO GETLOCAL HOST NAME, RC=return_code,RS=reason_code

Explanation: The HTTP server cannot obtain the localhost name.

Message variables:

return_codeThe return code resulting from the attempt toget the local host name

reason_codeThe reason code resulting from the attempt toget the local host name



GTM5422W component_name : INVALIDPARAMETER parameter_namePARAMETER, USE DEFAULTdefault_value VALUE

Explanation: The source collector received an invalidvalue for the parameter_name parameter; thedefault_value was used instead.

Message variables:

component_nameEvent Pump or the name of the componentthat issued the message

parameter_nameThe parameter name that was determined tobe invalid

default_valueThe default value that was used instead of theinvalid value that is specified forparameter_name


Administrator response: Check the system parametersvalue, make corrections, and restart the source collector,if necessary.

GTM5423E HTTP SERVER : UNABLE TO SETSOCKET IN NONBLOCKING MODE,RC=return_code, RS=reason_code

Explanation: The HTTP server cannot set a socket innon-blocking mode.

Message variables:

return_codeThe return code from the SET SOCKETstatement


reason_codeThe reason code from the SET SOCKETstatement

System action: Actions depend on the request that isbeing processed. In some cases, the source collectorstops.


GTM5424E HTTP SERVER : UNEXPECTEDTIMEOUT ERROR

Explanation: The HTTP server received an unexpectedtimeout error.



GTM5425E HTTP SERVER : SOCKET ACCEPTFAILED WITH RC=return_code,RS=reason_code

Explanation: The HTTP server SOCKET ACCEPTfailed with return_code and reason_code.

Message variables:

return_codeThe return code from the SOCKET ACCEPTstatement

reason_codeThe reason code from the SOCKET ACCEPTstatement



GTM5426E HTTP SERVER : GIVESOCKET FORSOCKET socket_id FAILED WITHRC=return_code, RS=reason_code

Explanation: The HTTP server issued a GIVESOCKETrequest for the socket_id socket and failed with a returncode of return_code and a reason code of reason_code.

Message variables:

socket_idThe socket ID

return_codeThe return code from the GIVESOCKETrequest

reason_codeThe reason code from the GIVESOCKETrequest



GTM5427I HTTP SERVER : DETECTINGSHUTDOWN REQUEST AT dd mmmyyyy hh:mm:ss

Explanation: The HTTP server detected a shutdownrequest at dd mmm yyyy hh:mm:ss. The followingexample shows the message content:

GTM5427I HTTP SERVER : DETECTINGSHUTDOWN REQUEST AT 26 Oct 2009 11:00:48

Message variables:

dd Number of days

mmm Number of months

yyyy Number of years

hh Number of hours

mm Number of minutes

ss Number of seconds


GTM5428E HTTP SERVER : TAKESOCKET FORSOCKET socket_id FAILED WITHRC=return_code, RS=reason_code

Explanation: The HTTP server TAKESOCKET socket_idfailed with return_code return code and reason_codereason code.

Message variables:

socket_idThe socket ID for which the TAKESOCKETstatement was issued

return_codeThe return code from the TAKESOCKETstatement

reason_codeThe reason code from the TAKESOCKETstatement


GTM5429E HTTP SERVER : READ SOCKETsocket_id RETURN ERROR CODEreturn_code

Explanation: The HTTP server received a non-zeroreturn code for a READ SOCKET statement.

Message variables:

socket_idThe socket ID for which the READ SOCKETstatement was issued


return_codeThe return code from the READ SOCKETstatement


GTM5430E HTTP SERVER : INVALID DATARECEIVED

Explanation: The HTTP server received invalid data.


GTM5431E GTMIPCRH : ERROR DURINGSENDING 404 NOT FOUNDRESPONSE

Explanation: An error occurred during sending. A 404Not Found response resulted.


GTM5432I ITZP BRODCAST INTERNAL QUEUEPROCESSING STARTED

Explanation: Event Pump BRODCAST internal queueprocessing started.


GTM5433I ITZP BRODCAST INTERNAL QUEUEPROCESSING INITIALIZATIONCOMPLETED

Explanation: Event Pump BRODCAST internal queueprocessing initialization ended.


GTM5434I ITZP BRODCAST INTERNAL QUEUEPROCESSING ENDED

Explanation: Event Pump BRODCAST internal queueprocessing ended.


GTM5435I ITZP GTMDTLDS INTERNAL QUEUEPROCESSING STARTED

Explanation: Event Pump GTMDTLDS internal queueprocessing started.


GTM5436I ITZP GTMDTLDS INTERNAL QUEUEPROCESSING INITIALIZATIONCOMPLETED

Explanation: Event Pump GTMDTLDS internal queueprocessing initialization ended.


GTM5437I ITZP GTMDTLDS INTERNAL QUEUEPROCESSING ENDED

Explanation: Event Pump GTMDTLDS internal queueprocessing ended.


GTM5438W ITZP UNABLE TO LOCATE USERID.SOAP REQUEST WILL NOT CONTAINUSERID AND PASSTICKET

Explanation: Event Pump cannot locate the user ID.The SOAP request does not contain a user ID or aPassTicket.


GTM5439W ITZP UNABLE TO GENERATEPASSTICKET FOR user_name, RACFSERVICE RETURN RC = return_code

Explanation: Event Pump did not generate aPassTicket for the specified user. The RACF programreturned a return code of return_code.

Message variables:

user_nameThe user name for which the PassTicket was tobe written

return_codeThe return code from the RACF SERVICE


GTM5440I HTTP SERVER : SERVICE STOPPED

Explanation: The HTTP server was stopped.


GTM5441W ERROR WRITING DATA TO AOPLOG

Explanation: Event Pump failed to write data to theAOPxxLOG file.


GTM5442I EXPECTED DELAY BEFORE ITZPHTTP SERVER WILL SHUT DOWN ISss SECONDS.

Explanation: The expected delay before the EventPump HTTP server shuts down is approximately ssseconds.

Message variables:

ss The time in seconds before the Event Pumpserver shuts down



GTM5443I ITZP REMOTEDT INTERNAL QUEUEPROCESSING STARTED

Explanation: The Event Pump REMOTEDT internalqueue processing initialization started.


GTM5444I ITZP REMOTEDT INTERNAL QUEUEPROCESSING INITIALIZATIONCOMPLETED

Explanation: The Event Pump REMOTEDT internalqueue processing initialization ended.


GTM5445E ITZP REMOTEDT INTERNAL QUEUEPROCESSING ENDED

Explanation: The Event Pump REMOTEDT internalqueue processing ended.


GTM5446E ERROR DURING PROCESSING SENDSOCKET FUNCTION FOR SOCKETsocket_id

Explanation: An error occurred during the SendSocket function for the socket_id socket.

Message variables:

socket_idThe ID of the socket for which the erroroccurred


GTM5447E ERROR PLACING RECORDS ONqueue_name INTERNAL QUEUE

Explanation: An error occurred when placing recordson the queue_name internal queue.

Message variables:

queue_nameThe name of the queue for which the erroroccurred


GTM5448E ERROR DELETING GLOBALVARIABLE variable_name

Explanation: An error occurred when deleting thevariable_name global variable.

Message variables:

variable_nameThe global variable that is being deleted

System action: Actions depend on the variable that is

deleted. In some cases, the source collector stops.

Administrator response: Restart the source collector.Check the system parameters value, make corrections,and restart the source collector, if necessary.

GTM5449E ITZP REQUIRED DD:dd_name NOTALLOCATED

Explanation: The required DD name was notallocated.

Message variables:

dd_nameThe required DD name


Administrator response: Restart the source collector.Check the system parameters value, make corrections,and, if necessary, restart the source collector.

GTM5450E ITZP ERROR READING DD:dd_name

Explanation: An error reading from the DD nameoccurred.

Message variables:

dd_nameThe DD name that was not read


Administrator response: Check that the required datadefinition has the right format, make any corrections,and restart the source collector. If the error continues,contact IBM Software Support.

GTM5451E ITZP ERROR WRITING DD:dd_name

Explanation: An error writing to the DD nameoccurred.

Message variables:

dd_nameThe DD name that is being written to


Administrator response: Check that the required datadefinition has the right format, make any corrections,and restart the source collector. If the error continues,contact IBM Software Support.

GTM5452W HTTP SERVER : CLIENTUNEXPECTEDLY CLOSEDCONNECTION

Explanation: The connection unexpectedly closed.



GTM5453E HTTP SERVER : SERVICETERMINATED

Explanation: Service was stopped for the HTTP server.



GTM5454E HTTP SERVER : SOCKET OPERATIONTIMEOUT

Explanation: The socket operation timed out.


GTM5455E HTTP SERVER : SELECT SOCKETsocket_id RETURN ERROR CODEreturn_code

Explanation: An error occurred. See the return_codereturn code for the specified socket.

Message variables:

return_codeThe return code from this event

socket_idThe ID of the socket


GTM5456I HTTP SERVER : STARTING SERVICE

Explanation: The HTTP server is starting service.


GTM5457W ERROR DURING REMOVING ITZPEXISTENCE

Explanation: An error occurred during removal of theEvent Pump existence.


Administrator response: If the error continues, contactIBM Software Support.

GTM5500W COMMAND QUEUE ENTRY ISINVALID

Explanation: The entry put for processing to thecommand queue has an invalid format.

System action: Processing of the failing commandqueue entry stopped. Source collector processingcontinues.

Administrator response: Obtain an output of thesource collector SHOW TRAPS command. Contact IBMSoftware Support.

GTM5501E COMMAND QUEUE INTERFACE ISINACTIVE

Explanation: The command queue interface was notstarted.



GTM5502E SYNTAX ERROR IN COMMANDTASK NAME

Explanation: The command queue name has a syntaxerror.



GTM5503E NO COMMAND TASK NAME PASSEDTO COMMAND TASK MANGER.TERMINATE

Explanation: The command queue interface was notstarted.



GTM5504E SYNTAX ERROR – INVALIDCOMMAND TASK PREFIX

Explanation: The command task prefix parameter hasincorrect syntax.


Administrator response: Correct the CMD_TASKSvalue. Restart the source collector. If the errorcontinues, contact IBM Software Support.

GTM5505E SYNTAX ERROR – INVALIDCOMMAND TASK COUNT

Explanation: The command task prefix countparameter has incorrect syntax.


Administrator response: Correct the CMD_TASKSvalue to a valid number in the range 1 - 99. Restart thesource collector. If the error continues, contact IBMSoftware Support.

GTM5506E SPECIFIED COMMAND TASKqueue_name ALREADY EXISTS

Explanation: The command task parameter hasduplicate entries.

Message variables:


queue_nameThe name of the failing command queue


Administrator response: Correct the CMD_TASKSvalue. Restart the source collector. If the errorcontinues, contact IBM Software Support.

GTM5507E ENTRY PUT TO queue_nameCOMMAND QUEUE FAILED

Explanation: The put of a new entry to the commandqueue failed.

Message variables:

queue_nameThe name of the failing command queue

System action: Processing of the failing commandqueue entry stops. The source collector continues.

Administrator response: Obtain an output of thesource collector SHOW TRAPS command. Contact IBMSoftware Support.

GTM5508E NO CORRESPONDING QUEUE FORMASK mask_name FOUND

Explanation: The put of a new entry to the commandqueue failed.

Message variables:

mask_nameThe name of the failing queue name mask

System action: Processing of the failing commandqueue entry stops. The source collector continues.

Administrator response: Obtain output of the sourcecollector SHOW TRAPS command. Contact IBMSoftware Support.

GTM5600E NO QUEUE NAME PASSED IN QUEUEMANAGER. TERMINATE

Explanation: A queue name was not passed in theQueue Manager. The process ends.



GTM5601I PUBLISHING queue_name QUEUECOMPLETED

Explanation: The queue_name was completed.

Message variables:

queue_nameThe name of the queue that was deactivated


GTM5602I DEACTIVATE queue_name QUEUE

Explanation: The queue_name was deactivated.

Message variables:

queue_nameThe name of the queue that was deactivated


GTM5603W SHUTDOWN_EXEC PARAMETER WASNOT FOUND

Explanation: The SHUTDOWN_EXEC parametercannot be found.



GTM5604E SYNTAX ERROR INSHUTDOWN_EXEC PARAMETER

Explanation: A syntax error occurred in theSHUTDOWN_EXEC parameter.



GTM5605E UNABLE TO EXECUTE exec_nameSHUTDOWN REXX EXEC

Explanation: The exec_name program cannot be run.

Message variables:

exec_nameThe program that was requested to run



GTM5606I SYSPLEX SUPPORT ENABLED

Explanation: Sysplex support was enabled.


GTM5607I SYSPLEX SUPPORT DISABLED

Explanation: Sysplex support was disabled.


GTM5608W INVALID SYSPLEX_SUPPORTPARAMETER, USE DEFAULT VALUE

Explanation: An invalid sysplex support parameterwas supplied. The default value is used.



GTM5609E RACROUTE EXTRACT REQUESTFAILED WITH SAF RC saf_rc, RACF RCracf_rc, RACF RS racf_rs

Explanation: An error occurred during RACROUTEREQUEST=EXTRACT call to the active security system.

Message variables:

saf_rc Security system return code

racf_rc RACF return code

racf_rs RACF reason code

System action: The source collector ends.

Administrator response: Check the SAF productconfiguration response. Restart the source collector. Ifthe error continues, contact IBM Software Support.

GTM6001I OBJECT PUMP CSA ALLOCATED AT:address

Explanation: Specifies the address of the sourcecollector common area.

Message variables:

address The source collector common area address


GTM6033I OBJECT SERVER SENSED,SERVER=name

Explanation: The event distributor found the dataspace environment in data space address space.

Message variables:

name The event distributor name


GTM6036I EXECUTING AS SHADOW PUMP

Explanation: The source collector detected the mainsource collector and is running as a secondary shadowsource collector.


GTM6041I CONNECTION TO DATASPACESUCCESSFUL, SERVER=name, STARTDATE=date, START TIME=time

Explanation: The source collector that is connected tothe data space.

Message variables:

name The name of the data space address spacename server

date The date the data space started

time The time the data space started


GTM6044E DATASPACE NOT FOUND, ITZPTERMINATING

Explanation: The source collector cannot locate thecorresponding data space.


Administrator response: Check that the data space isrunning and that it is using the same ACC1ID DDstatement, if used, as the source collector. If necessary,contact IBM Software Support.

GTM6085E INVALID ORIGIN FOUND,ORIGIN=data, ADDRESS=address,ALERT=alert

Explanation: The source collector located the dataspace, but the data space storage was not correctlyinitialized.

Message variables:

data The data at the data space origin

address The address of the origin

alert The alert for the data space origin


Administrator response: Determine why the dataspace initialization did not complete. If necessary,contact IBM Software Support.

GTM6095E MODULE module_name NOT LOADEDITZP TERMINATING

Explanation: The source collector cannot load thenamed module.

Message variables:

module_nameThe name of the module


Administrator response: Determine why the modulecannot be loaded. If necessary, contact IBM SoftwareSupport.

GTM6114E IEANTRT NOT LOADED, ACC1TSQPTERMINATING

Explanation: The source collector cannot load theIEANTRT module.

Administrator response: Determine why the modulecannot be loaded. If necessary, contact IBM SoftwareSupport.


GTM6115E NAME/TOKEN RETRIEVE FAILED,ACC1TSQP TERMINATED

Explanation: The source collector cannot retrieve thename token for the data space.


Administrator response: Determine why the nametoken cannot be located. Check that the data space isrunning and using the same ACC1ID DD statement ifused. If necessary, contact IBM Software Support.

GTM6116E NO DATA PASSED, PROCESSTERMINATING, DATA NOT QUEUED

Explanation: No data was passed to ACC1TSQP, thequeue routine, by the source collector REXX exec.

Administrator response: Determine why there was nodata. If necessary, contact IBM Software Support.

GTM6119E NO ALERT PASSED, PROCESSTERMINATING, DATA NOT QUEUED

Explanation: The source collector queue put routinecannot find an ALERT command for the data space inthe name token that is associated with the data space.


Administrator response: Determine why the ALERTcommand was missing. If necessary, contact IBMSoftware Support.

GTM7037W INVALID COMMAND ENTERED,COMMAND=command

Explanation: The event distributor did not recognizethe command that was entered.

Message variables:

commandThe name of the command

System action: Processing continues. The command isnot processed.

Administrator response: Correct the command andenter it again. For more information, see the EventPump for z/OS Command Reference.

GTM7064E LOG RECORD LENGTH IS INVALID,LENGTH=length

Explanation: The record length for the data set is notlarge enough to receive the data event message fromthe source collector task.

Message variables:

length The length of the event message that cannot bewritten to the log file

System action: Logging is halted.

Administrator response: Create a log file with anLRECL size that is larger than indicated in the message.For more information, see the Event Pump forz/OS Installation and Configuration Guide.

GTM7065E OPEN FILE ERROR FOR LOGDATASET, DSNAME=dsname

Explanation: The LOG data set cannot be opened

Message variables:

dsname The data set name that cannot not be opened


Administrator response: Determine why the data setcannot be opened. Correct the problem and restart theevent distributor.

GTM7066I LOGGING IS NOT ACTIVE

Explanation: The LOG service function for the eventdistributor is disabled and not used. The LOGparameters are not specified or used correctly.

System action: Logging ends.

Administrator response: Correct the LOG parametersand data sets. For more information, see the EventPump for z/OS Installation and Configuration Guide.Restart the event distributor.

GTM7067E CLOSE FILE ERROR FOR LOGDATASET, DSNAME=dsname

Explanation: The active log data set failed to closeduring log switching. The LOG1 and LOG2 data setsswitch automatically when the active log is full or ismanually switched with the LOGSWITCH command.

Message variables:

dsname The log data set that failed to close


Administrator response: Determine why the data setcannot close. Correct the problem and restart the eventdistributor.

GTM7070I GTMLOG MGR TERMINATED

Explanation: The event distributor ended the logservice task manager during shutdown processing.

System action: The log task shuts down. Logging ishalted.

GTM7120I LOG SWITCH ACKNOWLEDGED

Explanation: The LOGSWITCH command wasreceived.

System action: The event distributor switches fromthe active log to the inactive log.


GTM7137E INVALID QUEUE FOUND,QADDR=queue_address, HEADERDATA=data

Explanation: The event distributor LOGSWITCHcommand processor found that the event distributorLOG queue was not valid.

Message variables:

queue_addressThe queue address

data The data from the queue header


Administrator response: Determine why the logqueue is not available. Try restarting all address spaces.If necessary, contact IBM Software Support.

GTM7138E ERROR OCCURRED ON QPUT TOLOGQ, QADDR=queue_address,RC=return_code

Explanation: An error occurred when writing to theevent distributor log queue.

Message variables:

queue_addressThe queue address

return_codeThe return address from QPUT processing



GTM7139E INVALID CELL ACQUIRED,CELLADDR=address, CELLHEADER=data

Explanation: The event distributor LOGSWITCHcommand processor found that a cell in the data spacewas not valid.

Message variables:

address The cell address

data The data in the cell header



GTM7140I LOG SWITCH PROCESSING INCONTROL

Explanation: The event distributor LOGSWITCHcommand is being processed


GTM7141I LOG SWITCH SUCCESSFUL, NOWLOGGING TO: dsname

Explanation: The event distributor is now logging tothe specified data set.

Message variables:

dsname The data set name


GTM7142I SWITCHING FROM: current_dsname TO:active_dsname

Explanation: The event distributor is switching thelogging function from the current active data set to thenew active data set.

Message variables:

current_dsnameThe current active data set name

active_dsnameThe new active data set name


GTM7145I EIF INTERFACE NOT AVAILABLE

Explanation: A EIF command was issued to the eventdistributor, but the EIF interface is not enabled in theevent distributor.


Administrator response: Determine if the IBM TivoliEnterprise Console® EIF interface is active in the eventdistributor. If so, add the required DD statements to theevent distributor or determine why the interface wasnot enabled during event distributor initialization.

GTM7146I EIF INTERFACE ALREADY STARTED| STOPPED

Explanation: The EIF START or EIF STOP commandto the event distributor was issued, but the interface isalready started or stopped.



GTM7147I EIF INTERFACE STARTED | STOPPED

Explanation: The EIF START or EIF STOP commandto the event distributor was issued. The interface isnow started or stopped.


GTM7148I message_text

Explanation: The EIF STATUS or EIF LOG commandwas issued to the event distributor.

This message is issued with one of the followingmessage texts:

v EIF CONNECTION STATUS IS: AVAILABLE |UNAVAILABLE | UNKNOWN

Explanation: The EIF STATUS command was enteredto the event distributor. The message displays thelast known state of the connection to the TivoliEnterprise Console server.

A status of AVAILABLE indicates that the last recordwas successfully sent to the Tivoli Enterprise Consoleprogram.

A status of UNAVAILABLE indicates that the lastattempt to send an event to the Tivoli EnterpriseConsole program failed.

A status of UNKNOWN indicates that no recordswere sent to the Tivoli Enterprise Console programthrough the EIF interface.


Administrator response: If the status isUNAVAILABLE, determine why the event was notsent to the Tivoli Enterprise Console program byreviewing the console and SYSOUT logs.

v EIF INTERFACE IS STARTED | STOPPED |HALTED

Explanation: The EIF STATUS command was enteredto the event distributor. The status of the interface isstarted, stopped, or halted.


Administrator response: Determine if the status iscorrect. If the status is HALTED, determine why theEIF interface cannot build the select table from theGTMEIFSL DD input by viewing console messagesand the GTMEIFSP DD output.

v EIF LOG STATUS IS: YES | NO

Explanation: The operator entered the EIF STATUSor EIF LOG command to the event distributor. Themessage shows the current setting of the EIF LOGoption.

YES indicates that Tivoli Enterprise Console eventsand the return code from the EIF call are displayedin the system log file. NO indicates that logging ofevents and return codes is not done.

System Action: Processing continues.

Administrator Response: If required, use the EIFLOG command to change the current setting of theLOG option for Tivoli Enterprise Console events.

v RECORDS FAILED: total_number

Explanation: The EIF STATUS command was enteredto the event distributor. The message displays thetotal number of Tivoli Enterprise Console eventrecords that were not sent.

Message Variables:

total_numberThe total number of Tivoli EnterpriseConsole event records that were not sent


Administrator response: If this number is not 0,determine why the sending of records to the TivoliEnterprise Console server failed. Review the SYSLOGand SYSOUT output of the event distributor for anymessages that might indicate the cause of the failure.

v RECORDS SENT: total_number

Explanation: The EIF STATUS command was enteredto the event distributor. The message displays thetotal number of Tivoli Enterprise Console eventrecords that were sent to the Tivoli EnterpriseConsole program.

Message Variables:

total_numberThe total number of Tivoli EnterpriseConsole event records that were successfullysent


v TOTAL RECORDS SELECTED: number

Explanation: The EIF STATUS command was enteredto the event distributor. The message displays thetotal number of records that were selected forsending to the Tivoli Enterprise Console program asTivoli Enterprise Console events.

Message Variables:

number The number of records that were selected tosend to the Tivoli Enterprise Consoleprogram


GTM7149E EIF STATUS IS HALTED CANNOTCHANGE

Explanation: The EIF START or EIF STOP commandwas issued against the event distributor, but theprevious attempt to initialize the EIF interface failed.The interface was marked as halted.

System action: Processing continues. The EIF interfacestatus is unchanged.


Administrator response: To determine why the EIFinterface cannot initialize, review the SYSLOG andSYSOUT output of the event distributor.

GTM7150I EIF INTERFACE REFRESHED

Explanation: The EIF REFRESH command was issuedagainst the event distributor. The EIF SELECT tablewas successfully rebuilt.


GTM7151E EIF INTERFACE REFRESH FAILEDINTERFACE HALTED

Explanation: The EIF REFRESH command was issuedto the event distributor. The rebuild of the TivoliEnterprise Console EIF interface select table failed.

System action: The interface is marked as halted andis unavailable until the error is corrected and the selecttable successfully rebuilt.

Administrator response: Review the SYSLOG andSYSOUT output to determine why the interface failedto build the select table. Correct any errors in the selecttable input and reissue the EIF REFRESH command.

GTM7152E UNABLE TO LOAD GTMEIF01CANNOT REFRESH EIF INTERFACE

Explanation: The EIF REFRESH command was issuedto the event distributor. The interface cannot load theGTMEIF01 program.

System action: The interface select table cannot berefreshed.

Administrator response: Review the SYSLOG andSYSOUT output to determine why the interface cannotload the GTMEIF01 program. Correct the error andreissue the REFRESH command.

GTM7153I event

Explanation: This message is issued whenEIF_LOG=YES is coded in the event distributor startupparameters. The message contains the Tivoli EnterpriseConsole event that is sent to the Tivoli EnterpriseConsole program using the EIF interface.

Message variables:

event The Tivoli Enterprise Console event


GTM7154I EIF RETURN CODE=return_code

Explanation: This message is issued whenEIF_LOG=YES is coded in the event distributor startupparameters. The message shows the return code fromthe call to the EIF interface to send the event to theTivoli Enterprise Console program.

Message variables:

return_codeThe return code from the call to the EIFinterface


GTM7155I OPEN ERROR FOR DDNAMEGTMEIFSP | GTMEIFSL

Explanation: While building the select table for theTivoli Enterprise Console EIF interface, the interfacecannot open the specified DD name.

System action: The event distributor address spaceshuts down.

Administrator response: Review the SYSLOG andSYSOUT output to determine why the interface cannotopen the specified DD name. Correct the error andissue the EIF REFRESH command to rebuild the selecttable. See the Event Pump for z/OS Installation andConfiguration Guide for more information.

GTM7180I TRACE STATUS CHANGED,TRACE=status

Explanation: The event distributor trace status ischanged.

Message variables:

status The new trace status

System action: Processing continues with the newtrace status.

GTM7190E GTF OPTION MUST BE START, STOPOR STATUS

Explanation: The option entered with the GTFcommand was not recognized.


Administrator response: Enter the command againwith the correct option. See the Event Pump forz/OS Installation and Configuration Guide for moreinformation about the GTF command.

GTM7191I GTF TRACE STATUS IS STARTED |STOPPED

Explanation: Displays the status of the GTF interfacewithin the address space, or the resulting status after aGTF START or GTF STOP command was issued.

System action: Processing continues with the newtrace status.


GTM7400I ITZP APPC MGR: INITIALIZATION INPROGRESS

Explanation: The APPC LU 6.2 communicationmanager within the event distributor is initializing.


GTM7401E ITZP APPC MGR: GETMAIN FAILEDFOR type

Explanation: A GETMAIN request for the specifiedstorage failed within the APPC LU 6.2 communicationsmanager.

Message variables:

type The type of storage that was being obtained

System action: Communication between the eventdistributor and the Windows system is not possible.


GTM7402E ITZP APPC MGR: VTAM APPLIDMISSING IN ITZP CSA

Explanation: The VTAM application ID (APPLID) forthe APPC LU 6.2 communication manager was notfound.


Administrator response: Add the VTAM APPLID forthe APPC manager to the event distributor startupparameters in the REMOTE_APPLID=name parameter.If necessary, contact IBM Software Support.

GTM7403E ITZP APPC MGR: VTAM MODCBFAILED FOR name

Explanation: A VTAM MODCB macro failed for thespecified control block type.

Message variables:

name The control block name that was beingmodified



GTM7404I ITZP APPC MGR: OPENING VTAMAPPLID applid

Explanation: The event distributor communicationsmanager is opening the specified VTAM application ID(APPLID).

Message variables:

applid The name of the VTAM APPLID


GTM7405E ITZP APPC MGR: VTAM OPENFAILED, RC=return_code

Explanation: The event distributor cannot open theVTAM application ID (APPLID) as indicated by theREMOTE_APPLID parameter.

Message variables:

return_codeThe error code from the VTAM OPENinstruction

System action: Communication between the eventdistributor and the Windows components cannotinitialize.

Administrator response: Determine if the APPLIDthat is defined in the REMOTE_APPLID parameter isdefined in the VTAM program and is available for useby the event distributor. See Event Pump forz/OS Installation and Configuration Guidez/OSCommunications Server SNA Programming forinformation about the return codes from the VTAMOPEN macro instruction. Start the event distributoragain.

GTM7406I ITZP APPC MGR: SESSIONS.TOTAL=total, WINNERS=total_winners,LOSERS=total_losers

Explanation: The event distributor communicationsmanager established a session with the partner LU.

Message variables:

total The total number of sessions available

total_winnersThe number of contention winner sessions thatare currently active

total_losersThe number of contention loser sessions thatare currently active


Administrator response: Check that at least onecontention winner and one contention loser session isactive. If not, review the VTAM APPLID definition forthe APPC manager and partner LU. If necessary,contact IBM Software Support.

GTM7408E ITZP APPC MGR: UNABLE TO LOADSERVICE PROGRAM pgm

Explanation: The event distributor communicationsmanager cannot load the specified service program.

Message variables:


pgm The name of the service program that cannotbe loaded

System action: Communication between the eventdistributor and Windows components cannot initialize.

Administrator response: Determine why the specifiedprogram cannot be loaded. Ensure that theSGTMMODS library is in the STEPLIB concatenation. Ifnecessary, contact IBM Software Support.

GTM7409E ITZP APPC MGR: SERVICE PGM pgmISSUED ALLOCATE WHEN ALREADYIN SESSION

Explanation: The specified communication serviceprogram attempted to allocate a session with thepartner LU while it was already in session.

Message variables:

pgm The name of the service program that issuedthe allocate request

System action: Communication between the eventdistributor and the Windows operating system is notpossible.


GTM7410E ITZP APPC MGR: SERVICE PGM pgmISSUED SEND WHEN NOT IN SENDSTATE

Explanation: The specified communication serviceprogram attempted to issue a SEND command when itwas not in the SEND state

Message variables:

pgm The name of the service program that issuedthe send

System action: Communication between the eventdistributor and the Windows operating system is notpossible.


GTM7411E ITZP APPC MGR: DATA BUFFERGETMAIN FAILED FOR SERVICEPROGRAM pgm

Explanation: A GETMAIN command for a data bufferfor the specified service program failed.

Message variables:

pgm The name of the service program for whichthe GETMAIN command failed

Administrator response: The error indicates that thesource collector exhausted the available virtual storage.Use the REGION parameter of the JCL EXEC statementto increase the amount of virtual storage that is

available. If the problem continues, contact IBMSoftware Support.

GTM7412E ITZP APPC MGR: SERVICE PGM pgmISSUED RECEIVE WHEN NOT INSESSION

Explanation: The specified service program issued areceive, but it was not in session with the partner LU.

Message variables:

pgm The name of the service program that issuedthe receive



GTM7413E ITZP APPC MGR: SERVICE PGM pgmPASSED A BAD WAIT LIST

Explanation: The specified service program passed await list that was not valid to the communicationsmanager.

Message variables:

pgm The name of the service program that issuedthe wait



GTM7414E ITZP :parameter PARAMETER IS NOTSPECIFIED

Explanation: The remote application ID or local LUname indicated by parameter is not specified in thestartup parameters for the event distributor.

Message variables:

parameterThe REMOTE_APPLID or LOCAL_LUNAME

System action: The event distributor ends.

Administrator response: Add the REMOTE_APPLIDand LOCAL_LUNAME keywords that are required tobe used for the LU 6.2 connection. See the Event Pumpfor z/OS Installation and Configuration Guide.

GTM7422E ITZP APPC MGR: STIMERM FAILED.CANCELLING WAIT FORCONNECTION

Explanation: While waiting for a connection to thepartner LU, a STIMERM macro failed.

System action: Processing continues. The


communications manager stops the wait for aconnection.

Administrator response: Determine why theSTIMERM macro failed. If necessary, contact IBMSoftware Support.

GTM7423E ITZP APPC MGR: PROGRAM pgmDETECTED AN INVALID OR BADCMCB

Explanation: The specified service program cannotmap the Communications Manager Control Block(CMCB) correctly.

Message variables:

pgm The name of the service program


Administrator response: This message represents aservice level mismatch between the APPCcommunications manager and the service program.Ensure that the SGTMMODS library is in the STEPLIBconcatenation. If the problem continues, contact IBMSoftware Support.

GTM7424I ITZP APPC MGR: INITIALIZINGPROGRAM pgm

Explanation: The APPC communication manager isinitializing the specified service program.

Message variables:



GTM7425I ITZP APPC MGR: PROGRAM pgmHAS ENDED

Explanation: The APPC communication managerdetected that the specified service program ended.

Message variables:



Administrator response: Other than the eventdistributor ending, the service APPC service programsshould not end. Determine if the session was lost to thepartner LU. If necessary, contact IBM Software Support.

GTM7426I ITZP APPC MGR: PROGRAM pgmIGNORED SHUTDOWN REQUESTTERMINATION FORCED

Explanation: The APPC communication managerdetected that the specified service program ignored ashutdown request. The APPC communications managerforcibly stops the service program.

Message variables:




GTM7427I ITZP APPC MGR: CANCELLINGVTAM REQUEST FOR PROGRAM pgm

Explanation: The APPC communication managerdetected that a VTAM request other than a SENDrequest was in progress for the specified serviceprogram when the shutdown request was received. TheVTAM request is canceled.

Message variables:



GTM7428I ITZP APPC MGR: SESSION LIMITS(WINNERS) REACHED FORPROGRAM pgm

Explanation: The APPC communication managerdetected that the specified service program issued anALLOCATE, but no more contention winner sessionsare available.

Message variables:


System action: The session is not allocated. Processingcontinues. Results are unpredictable.

Administrator response: If this session request is thefirst one from the event distributor, ensure that theVTAM APPLID definition for the event distributorAPPLID and partner LU is correct. If necessary, contactIBM Software Support.

GTM7429E ITZP APPC MGR: PROGRAM pgmISSUED ALLOCATE WITH BLANKNAME OPERAND

Explanation: The APPC communication managerdetected that the specified service program issued anALLOCATE command, but the process name parameteris missing.

Message variables:


System action: The session is not allocated. Processingcontinues. Results are unpredictable.



GTM7430I ITZP APPC MGR: RECEIVED FMH5HAD ZERO LENGTH PROCESSNAME, FMH5 REJECTED

Explanation: The APPC communication managerreceived an FMH5 from the partner LU to initiate asession, but the process name within the FMH5 wasmissing.

Administrator response: Consider using VTAM tracefacilities to determine the origin of the invalid FMH5request. If the problem continues contact IBM SoftwareSupport.

GTM7493I ITZP APPC MGR: TERMINATION INPROGRESS

Explanation: The APPC communication managerreceived a shutdown command and is stopping.

System action: The shutdown process continues.

GTM7494E ITZP APPC MGR: functionRTNCD=return_code FDBK2=reason_codeFOR PROGRAM pgm

Explanation: The APPC communication managerreceived an error from the specified VTAM APPCfunction.

Message variables:

function The function name that was issued

return_codeThe return code from the function

reason_codeThe reason code from the function (FDBK2)

pgm The name of the service program thatrequested the function

System action: Processing continues, but the resultsare unpredictable.

Administrator response: Determine why the requestfailed. See the IBM SNA library for more information. Ifthe problem continues, contact IBM Software Support.

GTM7495E ITZP APPC MGR: functionRTNCD=return_code FDBK2=reason_codeFOR PROGRAM pgm


Message variables:


return_codeThe return code from the function RPL(RPL6RCPR)

reason_codeThe reason code from the function(RPL6RCSC)

pgm The name of the service program thatrequested the function



GTM7496E ITZP APPC MGR: functionRTNCD=return_code FDBK2=reason_code


Message variables:


return_codeThe return code from the function

reason_codeThe reason code from the function


Administrator response: Determine why the requestfailed. See the appropriate manual in the IBM SNAlibrary for more information. If the problem continues,contact IBM Software Support.

GTM7497E ITZP APPC MGR: functionRCPRI=return_code RCSEC=reason_code


Message variables:


return_codeThe return code from the function RPL(RPL6RCPR))

reason_codeThe reason code from the function RPL(RPL6RCSC)




GTM7498I ITZP APPC MGR: CLOSING VTAMACB

Explanation: The APPC communication manager isclosing the VTAM access method control block (ACB).

System action: The VTAM ACB is closed.Communication is no longer possible.

GTM7499I ITZP APPC MGR : TERMINATED

Explanation: The APPC communication managerended. This message is a standard message whenissued as a part of the source collector shutdownsequence.


GTM7500I INITIALIZATION IN PROGRESS

Explanation: The source collector address space isstarting.


GTM7501I RUNNING INITIAL REXX EXEC: pgm

Explanation: The initial REXX exec that is run whenthe source collector is started.


Message variables:

pgm Indicates the name of the REXX exec program

GTM7502E GETMAIN FAILED FOR name

Explanation: The GETMAIN command failed, andsufficient storage is not available.

Message variables:

name Identifies the name of the storage area thatcannot be obtained



GTM7503E LOAD FAILED FOR module_name

Explanation: The module cannot be loaded intomemory.

Message variables:

module_nameThe module name that cannot be loaded


Administrator response: Determine why the modulecannot be loaded. Ensure that the STEPLIB DDconcatenation contains the SGTMMODS library. Themessage probably indicates an installation problem. Ifnecessary, contact IBM Software Support.

GTM7505E NOT RUNNING AUTHORIZED

Explanation: The source collector address space is notauthorized in the authorized program facility (APF).


Administrator response: Verify that the load librariesthat are used in the STEPLIB concatenation of thesource collector address space are APF authorized.

GTM7506E SYSEVENT TRANSWAP FAILED,RC=return_code

Explanation: The source collector cannot run thenon-swappable procedure.

Message variables:

return_codeThe return code from the source collector


Administrator response: Determine why the sourcecollector address space cannot run the non-swappableprocedure. See the MVS authorized assembler servicesinformation in the z/OS library. If necessary, contactIBM Software Support.

GTM7507I UNABLE TO LOCATE OBJECTSERVER

Explanation: The source collector address space isstarted with the request to connect to the data space.The data space that is to be used is not running.


Administrator response: Start the data space beforestarting the event distributor and source collectoraddress spaces.

GTM7508I OBJECT SERVER DETECTED,JOBNAME=jobname

Explanation: The source collector address space foundthe data space that is to be used.

Message variables:

jobname The job name of the data space



GTM7509E ALREADY EXECUTING,JOBNAME=jobname

Explanation: A second copy of the source collectoraddress space is attempting to use the same data space.This error is an internal error.

Message variables:

jobname The job name of the data space



GTM7510E UNABLE TO LOCATE TIOT

Explanation: The TIOT control block cannot beobtained. This error is an internal error.



GTM7511E UNABLE TO CREATE NAME TOKEN,RC=return_code

Explanation: The name token that was used for crossmemory support cannot be created.

Message variables:

return_codeThe return code from a call to the IEANTCTfunction


Administrator response: Determine the cause of thefailure to create the name token. See the MVSauthorized assembler services information in the z/OSlibrary. If the problem continues, contact IBM SoftwareSupport.

GTM7513E INVALID ORIGIN DETECTED INSERVER

Explanation: The source collector detected a dataspace that might be corrupted.

System action: The source collector shuts down.

Administrator response: Restart the three addressspaces in the following order:1. The source collector2. The event distributor3. The data space

If the problem continues, contact IBM SoftwareSupport.

GTM7514E UNABLE TO ESTABLISH CONSOLECOMMUNICATIONS, RC=return_code

Explanation: The source collector address space is notinitialized with console communication support.

The MODIFY command cannot be used to issue acommand for the source collector address space.

Message variables:

return_codeThe return code from the QEDIT macro

System action: The source collector address spaceshuts down.

Administrator response: Investigate the return codethat is reported by the QEDIT macro. See the MVSauthorized assembler services information in the z/OSlibrary. Contact IBM Software Support if the problemcannot be resolved.

GTM7517I CMD=text

Explanation: The MODIFY command that was issuedfrom the console.

Message variables:

text The text of the command


GTM7520I AOPLOG LOG OUTPUT NOTAVAILABLE

Explanation: The AOPxxLOG DD name is notspecified in the JCL of the Event Pump procedure.


Administrator response: Apply the AOPxxLOG DDname in the JCL of the Event Pump procedure.Processing continues, and results can be unpredictable.

GTM7521I AOPSYSIN OPEN FAILURE, USINGDEFAULT SETTINGS

Explanation: The AOPSYSIN DD name cannot openthe file that contains the source collector startupparameters. The default settings are used.


Administrator response: If any of the source collectorparameters require changing, a file tha is referenced bythe DD name AOPSYSIN must be used. See the EventPump for z/OS Installation and Configuration Guide.

GTM7524I VTAM 3270 SERVICES ARE NOTAVAILABLE

Explanation: A source collector parameter, eitherTERMINAL_PREFIX or NUMBER_OF_TERMINALS, isnot valid. The 3270 interface is not usable. A VTAM


3270 session is required only for Tivoli OMEGAMONevent feeds, which are available only if you are usingEvent Pump with TBSM Version 3.1.

System action: Processing continues. Some data mightbe unavailable.

Administrator response: See the Event Pump forz/OS Installation and Configuration Guide for informationabout configuring the keywords for theTERMINAL_PREFIX and NUMBER_OF_TERMINALSoperands.

GTM7525E VTAM SHOWCB FAILED FOR function,RC=return_code

Explanation: During initialization of the Event Pump3270 interface, an error occurred on the SHOWCBfunction for the area that is identified in the $P1operand. The Event Pump 3270 interface is not usable.

Message variables:

function The area that the SHOWCB function cannotsuccessfully obtain

return_codeThe return code that was returned from theSHOWCB function call

System action: Processing continues. Some data mightnot be available.

Administrator response: See the appropriate manualin the SNA Programming library to identify the returncodes from the SHOWCB function. See the Event Pumpfor z/OS Installation and Configuration Guide forinformation about setting up the Event Pump 3270interface. If necessary, contact IBM Software Support.

GTM7526E VTAM function FAILED FOR block,R15=return_code, R0=reason_code

Explanation: The VTAM function that is indicated inthe function variable cannot successfully complete whenattempting to establish a 3270 session. Event Pumpcannot log on to any 3270 applications.

Message variables:

function The VTAM function (GENCB) that cannotsuccessfully create the area that is specified inblock

block The access method control block (ACB) that isnot generated

return_codeThe return code that is returned from theGENCB function call

reason_codeThe reason code that is returned from theGENCB function call

System action: Processing continues. Some data mightbe unavailable.

Administrator response: For information about thereturn codes from the SHOWCB function, see z/OSCommunications Server SNA Programming. Forinformation about setting up the Event Pump 3270interface, see the Event Pump for z/OS Installation andConfiguration Guide. If necessary, contact IBM SoftwareSupport.

GTM7527E VTAM function FAILED FOR blockR15=return_code

Explanation: The VTAM function that is indicated infunction cannot successfully complete when attemptingto establish a 3270 session. Event Pump cannot log onto any 3270 applications.

Message variables:

function The VTAM function (GENCB) that cannotsuccessfully create the area specified in block

block The VTAM control block that is not generated

return_codeThe return code that is returned from theGENCB function call

System action: Processing continues. Some data isunavailable.

Administrator response: See the Event Pump forz/OS Installation and Configuration Guide for informationabout setting up the 3270 interface. If necessary, contactIBM Software Support.

GTM7528E VTAM OPEN FAILED RC=return_codeFOR LU name

Explanation: The VTAM OPEN cannot open theaccess method control block (ACB) for the session.

Message variables:

return_codeThe return code value that was returned fromthe OPEN ACB call

name The LU name that represents the logicalterminal for this 3270 session


Administrator response: See the Event Pump forz/OS Installation and Configuration Guide for informationabout setting up the Event Pump 3270 interface. Ifnecessary, contact IBM Software Support.

GTM7529E PVI MESSAGE: error

Explanation: An error occurred on an active 3270session.

Message variables:

error The error that occurred



Administrator response: Depending on the errormessage that is returned, take appropriate action. Seethe Event Pump for z/OS Installation and ConfigurationGuide for information about using the Event Pump 3270interface.

If necessary, contact IBM Software Support.

GTM7530I AOPLEXSY ATTACH FOR SESSIONname FAILED

Explanation: The Event Pump LEXSY manager cannotinitialize on the 3270 session.

Message variables:

name The 3270 session name

System action: The session was not connected.


GTM7531E AOPLEXSY NOT VALID FOR SESSIONname

Explanation: The session type that is used on theEvent Pump 3270 session is not supported. This error isan internal error.

Message variables:

name The name of the session for which AOPLEXSYis not a valid session type. AOPLEXSYsessions are supported for the OMEGAMONCICS®, OMEGAMON MVS, OMEGAMONDB2, and OMEGAMON IMS™ products.

System action: The session is closed.


GTM7532I VTAM SESSION ENDED - name

Explanation: The Event Pump 3270 session is loggedoff.

Message variables:

name The session name that ended


GTM7534E EDI CROSS MEMORY INIT ERRORCODE code

Explanation: The cross memory resources required forthe EDI interface cannot be initialized. Programs thatuse the EDI exit services are not usable.

Message variables:

code The code that identifies the cross memoryresource that was not initialized. The followingvalues are valid:X'01' LXCREATEX'02' LXTOKENX'03' ETCREATEX'04' ETCONNECTX'05' PCTOKEN

System action: Processing continues. Event Pumpcannot receive events from EDI sources.


GTM7535E INVALID COMMAND: text

Explanation: A command that was issued by theMODIFY command from an MVS console is notsupported.

Message variables:

text The command text that was issued


Administrator response: See the Event Pump forz/OS Installation and Configuration Guide for thecommands that are supported by Event Pump.

Issue the command again.

GTM7536E EXEC NAME MISSING FROMREFRESH COMMAND

Explanation: The REFRESH command was issuedwithout providing an exec name.


Administrator response: Reissue the command,referencing the exec name. See the Event Pump forz/OS Installation and Configuration Guide for the syntaxof the REFRESH command.

GTM7537E REFRESH NOT VALID WHENEXEC_REFRESH=YES

Explanation: The REFRESH command is issued for anexec, but Event Pump is running withEXEC_REFRESH=YES. An exec cannot be refreshedwhen Event Pump is configured with this setting on.


Administrator response: See the Event Pump forz/OS Installation and Configuration Guide for informationabout using a refreshing exec.

GTM7538I EXEC name NOT LOADED, NOTREFRESHED

Explanation: The REFRESH command is issued for anexec that was not previously loaded, and Event Pumpis configured to run with EXEC_REFRESH=NO.


Message variables:

name The name of the exec


Administrator response: Run the exec from EventPump to enable the exec to be loaded. If the EXEC ischanged, use the REFRESH command to reload thenew copy.

See the Event Pump for z/OS Installation andConfiguration Guide for information about when to usethe REFRESH command.

GTM7539I EXEC name REFRESHED

Explanation: The specified exec was successfullyrefreshed by the REFRESH command.

Message variables:

name The name of the exec


GTM7540E REXX ENVIRONMENT CREATEFAILED, RC=return_code,REASON=reason_code

Explanation: The REXX environment is not created.

Message variables:

return_codeThe return code from the IRXINIT call thatwas used to create the REXX environment

reason_codeThe reason code from the IRXINIT call



GTM7541E REXX HOST ENVIRONMENT CREATEFAILED, RC=return_code

Explanation: The REXX AOP host commandenvironment is not created.

Message variables:

return_codeThe return code from the call to theIRXSUBCM routine that is used to create theREXX AOP host command environment



GTM7542E REXX VAR SETRC=return_code,VAR=name

Explanation: The Local REXX variable specifiedcannot be used.

Message variables:

return_codeThe return code from the IRXEXCOM call

name The name of the Local REXX variable



GTM7545E name SUBSYSTEM INITIALIZED

Explanation: The subsystem interface successfullyinitialized.

Message variables:

name The name of the Event Pump subsystem


GTM7546E name SUBSYSTEM INITIALIZATIONFAILED

Explanation: The Event Pump subsystem is notinitialized and cannot be used.

Message variables:


Administrator response: Review the console log foradditional messages that might indicate why thesubsystem initialization failed. If necessary, contact IBMSoftware Support.

GTM7547I name SUBSYSTEM QUIECING

Explanation: The Event Pump subsystem is in theprocess of shutting down.

Message variables:


System action: The subsystem starts the shutdown.

GTM7548I name: SUBSYSTEM COMMUNICATIONENDED

Explanation: The Event Pump subsystemcommunication is stopped.

Message variables:

name The name of the subsystem

System action: The subsystem stops.


GTM7550E name: LINK TO module_name FAILED

Explanation: The named module cannot be linked toduring subsystem initialization. This error is an internalerror.

Message variables:


module_nameThe name of the module that cannot be linkedto during the initialization

System action: The subsystem ends. Some commandsmight not be available.


GTM7551E name: IEFSSI function ERROR,RC=return_code REASON=reason_code

Explanation: The IEFSSI function failed with errorsduring subsystem initialization.

Message variables:


function The function call that is used on the IEFSSIservice

return_codeThe return code from the IEFSSI function call

reason_codeThe reason code from the IEFSSI function call


Administrator response: Determine the reason for thefailure. See the MVS authorized assembler servicesinformation in the z/OS library. If the problemcontinues, contact IBM Software Support.

GTM7552E name: IEFSSVT function ERROR,RC=return_code REASON=reason_code

Explanation: The IEFSSVT function failed with errorsduring dynamic subsystem initialization.

Message variables:


function The function call that is used on the IEFSSVTservice

return_codeThe return code from the IEFSSVT functioncall

reason_codeThe reason code from the IEFSSVT functioncall


Administrator response: Determine the reason for thefailure. See the MVS authorized assembler servicesinformation in the z/OS library. If the problemcontinues, contact IBM Software Support.

GTM7553E name: AOPAUTH DD OPEN ERROR

Explanation: The source collector cannot open theAOPAUTH library during subsystem initialization.

Message variables:



Administrator response: Verify that the Event Pumpload library is referenced by the AOPAUTH DD name.If the problem continues, contact IBM SoftwareSupport.

GTM7554E name LOAD FAILED FOR module_name:value

Explanation: The named module cannot be loadedduring the subsystem initialization.

Message variables:


module_nameThe module name that cannot be loaded

value A numeric reference value indicating whichoccurrence of the LOAD macro failed


Administrator response: Verify that the Event Pumpload library is referenced by the AOPAUTH DD name.If the problem continues, contact IBM SoftwareSupport.

GTM7555E name: MODULE module_name NOTAMODE 31

Explanation: The named module is not link-editedwith addressing mode 31. This message indicates aproblem with the installation of components.

Message variables:


module_nameThe name of the module in error


Administrator response: Determine why the modulehas the incorrect AMODE module. Ensure that the


application was installed correctly.


GTM7556E name: IEFSSREQ value R15=return_code_1SSOBRETN=return_code_2SFDA_RC=return_code_3

Explanation: An IEFSSREQ error occurred whileprocessing a subsystem request.

Message variables:

name The name of the Event Pump subsystem.

value The function request for the IEFSSREQ service.

return_code_1The return code from the IEFSSREQ service.

return_code_2The return code value that is provided in theSSOB area.

return_code_3The return code value that is provided in thesubsystem functional dependent area (SFDA)internal area. Possible return_code_3 values forsubsystem user call 250 (init) to the subsystemare as follows:v 4: An SSCB address was not supplied.v 8: The SS010 address was 0.v 12: The SS010 length was 0.v 16: Subsystem status is not currently

inactive.v 20: The 0 Subsystem user-count is not 0.


Administrator response: For SFDA_RC values of 16 or20, ensure that a copy of the source collector is notalready running with the same subsystem name. If thesource collector is not running, check that the last execended normally. Run the source collector with adifferent subsystem name or use the AOPUTIL utilityin the SGTMMODS library to reset the subsystem.


GTM7557E name: IEFSSREQ function R15=return_codeSSOBRETN=value

Explanation: An IEFSSREQ error occurred duringsubsystem stop processing.

Message variables:


function The function request made to the subsystem

return_codeThe return code from the requested service

value The return code that is provided in the SSOBarea


Administrator response: Determine why the RESMGRrequest failed. For more information, see the MVSauthorized assembler services information in the z/OSlibrary.


GTM7558E name: module_name RESMGR ADDRC=return_code

Explanation: The RESMGR ADD failed. Thesubsystem is ended.

Message variables:


module_nameThe module name of the resource manager

return_codeThe return code from the RESMGR ADDmacro


Administrator response: Determine why the RESMGRADD request failed. For more information, see the MVSauthorized assembler services information in the z/OSlibrary. If necessary, contact IBM Software Support.

GTM7560I name MAX THREADS REACHED,REPLY 1 - 9 TO INCREASE, 0 TOIGNORE

Explanation: The maximum number of threads thatcan be processed concurrently was reached within theEvent Pump subsystem interface. No threads areavailable to process any more commands using theEvent Pump subsystem.

Message variables:


System action: Processing stops while waiting for aresponse.

Administrator response: To increase the number ofavailable threads, reply with a number in the range1 - 9.

If you reply with a value in the range 1 - 9 and thismessage continues to be issued, it indicates a problemwith the Event Pump subsystem interface.

Reply 0 to suppress the message.

If possible, obtain a system dump of the sourcecollector address space including the CSA using theSDUMP parameter SDATA=(CSA, RGN, PSA, LSQA).

See the Event Pump for z/OS Installation andConfiguration Guide for information about the


SUBSYSTEM_MAXTHREADS operand.

GTM7561I name: REPLY TO ACC7560I MUST BENUMERIC, 0-9

Explanation: The reply to the GTM7560I messagemust be a single numeric digit in the range 0 - 9

Message variables:


System action: The GTM7560I message is issuedagain.

Administrator response: Correct the reply to theGTM7560I message.

GTM7562I name: THREAD LIMIT REACHED (100)

Explanation: The number of threads processingsimultaneously within the Event Pump subsystemreached 100. This number is the maximum allowed bythe subsystem.

Message variables:


System action: Processing continues, but no newthreads are attached. Some data can be lost.

Administrator response: Obtain a system dump of thesource collector address space including the CSA usingthe SDUMP parameter SDATA=(CSA, RGN, PSA,LSQA).

Contact IBM Software Support.

GTM7563E DATA TYPE MISSING FROM SHOWCOMMAND

Explanation: The DATA TYPE operand is notprovided on the SHOW command.


Administrator response: Reissue the SHOW commandwith a supported DATA TYPE operand.

See the Event Pump for z/OS Installation andConfiguration Guide for more information about theSHOW command.

GTM7564E type IS INVALID FOR SHOWCOMMAND

Explanation: The DATA TYPE operand that is used onthe SHOW command is not supported.

Message variables:

type The value that was specified on the DATATYPE operand


Administrator response: Reissue the SHOW command

with a supported DATA TYPE operand.

See the Event Pump for z/OS Installation andConfiguration Guide for more information about theSHOW command.

GTM7565E error_text

Explanation: The error message that was returnedfrom the SHOW TRAPS command.

Message variables:

error_textThe error message text


Administrator response: Depending on the errormessage that was received from issuing the SHOWTRAPS command, take appropriate action. If necessary,contact IBM Software Support.

GTM7566E TRAP MANAGER IS NOT ACTIVE

Explanation: The Event Pump Trap Manager interfaceis not available. The SHOW TRAPS command cannotbe run.

System action: Processing continues. Many functionsmight not be available.

Administrator response: If the source collector isshutting down, this message is standard. Otherwise,contact IBM Software Support.

GTM7567I text

Explanation: This message displays the output from aSHOW command.

Message variables:

text The display line text


GTM7568E PVI MANAGER IS NOT ACTIVE

Explanation: The Event Pump programmable VTAMinterface is not available. The SHOW SESSIONScommand cannot be issued.

System action: Processing continues. Some functions,such as OMEGAMON monitoring, might not beavailable.

Administrator response: If the source collector isshutting down this message is standard; otherwise,contact IBM Software Support.


GTM7570I text

Explanation: Displays the output from the SHOWTRAPS command.

Message variables:

text The display line text


GTM7571E AOPDAY STIMERM SET FAILED,RC=return_code

Explanation: The STIMERM macro in AOPDAY, thechange of day program, failed.

Message variables:

return_codeThe return code from the STIMERM macro


Administrator response: Determine why theSTIMERM macro failed. For more information, see theMVS authorized assembler services information in thez/OS library.


GTM7574I LOGSCREENS IS state

Explanation: If the state is ON,, the 3270 informationthat is retrieved from each active session is written tothe AOPxxLOG system log.

Message variables:

state The value of the state, either ON or OFF


GTM7575I SHOW COMMAND COMPLETE

Explanation: An informational message issued at theend of a set of display messages resulting from issuinga SHOW command.


GTM7576I text

Explanation: The summary message text of a SHOWTRAPS command.

Message variables:

text Displays the summary output from a SHOWTRAPS command


GTM7577E GLOBAL VARIABLE MANAGER NOTACTIVE

Explanation: The global variable interface is notavailable. The SHOW VARS and SHOW POOLcommands are not available.


Administrator response: If the source collector is notshutting down, contact IBM Software Support.

GTM7578E CONSOLE MANAGER NOT ACTIVE

Explanation: The console manager interface is notavailable. The SHOW MSGCOUNT command is notavailable.


Administrator response: If the source collector is notshutting down, contact IBM Software Support.

GTM7579I CONSOLE MESSAGES RECEIVED:number

Explanation: The total number of console messagesthat were received is displayed on the console whenthe SHOW MSGCOUNT command is issued.

Message variables:

number The number of messages that were received


GTM7580I REXX NOT ACTIVE IN THIS REGION

Explanation: The REFRESH command was issued fora REXX exec, but no REXX environment to supportrunning execs is available.

System action: Processing continues, but results areunpredictable.


GTM7581E CANNOT RUN REXX EXECS, REXXNOT INITIALIZED

Explanation: An attempt was made to run a REXXexec, but no REXX environment to support runningexecs is available.

System action: Processing continues, but results areunpredictable.

Administrator response: Determine why no REXXenvironment is available within the address space. Ifnecessary, contact IBM Software Support.


GTM7582E INIT TABLE SUFFIX NOT PASSED TOAOPPARM

Explanation: The suffix value that identifies theparameter to be used for the Event Pump componentwas not provided. This message indicates an internalerror.



GTM7583E INIT TABLE IS EMPTY

Explanation: The parameter table module for theregion contains no entries. This message indicates aninternal error.



GTM7584I AOPLEXSY DETECTED LROWSOVERFLOW ON session_name

Explanation: A 3270 session collecting data fromOMEGAMON products cannot find the delimiter valuespecified. This value is used by Event Pump to controlscrolling during the 3270 session.

Message variables:


System action: Processing continues, but some datamight be lost.

Administrator response: Increase the number oflogical rows (LROWS) used by the session.

GTM7585I ENTER PARAMETERS, END TOFINISH

Explanation: This message indicates that additionalparameters for the source collector or the eventdistributor can be specified. It is issued only if theparameter field of the JCL EXEC PGM statement for thesource collector or event distributor contains the.CONSOLE keyword.

System action: The source collector or eventdistributor waits for a reply.

Administrator response: Reply with additional orchanged startup parameters. You can continue to enteradditional parameters until you enter the .ENDparameter in reply to this message. If you specifymultiple parameters in one reply, separate eachparameter with a comma. A trailing comma is not

required when you continue input on a subsequentline.

GTM7586E KEYWORD TOO LONG, FOUND:keyword

Explanation: The specified keyword is too long. Theprogram prints out the part that it can hold. The sourcecollector or event distributor stopped.

Message variables:

keyword The part of the keyword name that theprogram prints

System action: The source collector or eventdistributor waits for a reply.

Administrator response: Restart the source collectoror event distributor, enter the parameters again, andcorrect the parameter that is in error.

GTM7587E CLOSING QUOTE MISSING FROMDATA FOR KEYWORD

Explanation: The data for the specified keyword wasstarted with a single or double quotation mark, but theprogram cannot find a matching closing quotationmark. This message indicates a syntax error.


Administrator response: Restart the source collectoror event distributor, and enter the correct parameters.

GTM7588E NON NUMERIC DATA FOUND FORKEYWORD keyword

Explanation: The data for the specified keyword mustbe numeric. The source collector or the eventdistributor stopped.

Message variables:

keyword The part of the keyword name that theprogram prints


Administrator response: Restart the source collectoror event distributor, enter the parameters again, andcorrect the parameter in error.

GTM7589E message_text

Explanation: An error occurred in processing theparameter data that was entered with the PARMoperand of the JCL EXEC PGM statement.

This message is issued with one of the followingmessage texts:

v DATA MISSING FOR KEYWORD keyword


Explanation: No data was entered for the specifiedkeyword. The keyword is ignored. A default valuemight be used if one exists.

Message Variables:

keyword The keyword for which data is missing

Administrator response: Stop the address space andrestart it, specifying a valid value for the keyword.

v DATA VALUE TOO SMALL FOR KEYWORDkeyword

Explanation: The data that was entered for thespecified keyword is not within the valid range (datathat was entered is less than the minimum allowed).The default value is used.

Message Variables:

keyword The keyword for which the data value is toosmall


v DATA VALUE TOO LARGE FOR KEYWORDkeyword

Explanation: The data that was entered for thespecified keyword is not within the valid range (datais greater than the maximum allowed). The defaultvalue is used.

Message Variables:

keyword The keyword for which the data value is toogreat


v PARAMETER SET FAILED FOR KEYWORDkeyword

Explanation: An error occurred in storing theparameter data.

Message Variables:

keyword The keyword for which the parameter setfailed

Administrator response: Determine why the erroroccurred. If necessary, contact IBM Software Support.

GTM7597I STOP COMMAND DETECTED

Explanation: The STOP command was issued to shutdown the address space.

System action: The address space initiates theshutdown process.

GTM7598I TERMINATION IN PROGRESS

Explanation: The address space is shutting down.

GTM7599I TERMINATION COMPLETE

Explanation: The address space ended successfully.

GTM7600E IBM Tivoli Business Systems ManagerMCS CONSOLE ALREADY EXISTS

Explanation: The source collector is attempting to startwith an MCS console name that is already used.


Administrator response: Change the console name inthe CONSOLE=console_name statement in the sourcecollector start parameters to a name that is unique. Ifthe problem continues, contact IBM Software Support.

GTM7601E CONSOLE ACTIVATION FAILED,RC=return_code REASON=reason_code

Explanation: The source collector cannot activate anMCS console during initialization of the consoleinterface.

Message variables:

return_codeThe return code from the MSCOPERACTIVATE service

reason_codeThe reason code from the MSCOPERACTIVATE service

System action: Processing continues. Event Pumpcannot monitor console messages.

Administrator response: Determine why the MCSconsole cannot be activated. If necessary, contact IBMSoftware Support.

GTM7602E CONSOLE DEACTIVATION FAILED,RC=return_code REASON=reason_code

Explanation: The source collector cannot deactivate anMCS console during shutdown of the console interface.

Message variables:

return_codeThe return code from the MSCOPERDEACTIVATE service

reason_codeThe reason code from the MSCOPERDEACTIVATE service


Administrator response: Determine why the MCS


console cannot be deactivated. If necessary, contact IBMSoftware Support.

GTM7604I text

Explanation: This message indicates the status of theMCS console queuing.

Message variables:

text The status as indicated by one of the followingmessage texts:v * MCS QUEUING STOPPED, MESSAGE

DATASPACE FULLv * MCS QUEUING STOPPED, MAX

MESSAGES QUEUEDv * MCS QUEUING STOPPED, MCS

INTERNAL ERRORv * MCS QUEUED MSGS AT 80%


Administrator response: Determine why the MCSconsole interface is not processing messages. Ifnecessary, contact IBM Software Support.

GTM7605E MCS MESSAGE QUEUING RESUMEFAILED RC=return_codeREASON=reason_code

Explanation: The MCS console failed to resumemessage queuing.

Message variables:

return_codeThe return code from the MCSOPMSGRESUME service

reason_codeThe reason code from the MCSOPMSGRESUME service

System action: Processing continues. Event Pumpcannot monitor console messages.

Administrator response: Determine why the MCSconsole cannot resume processing. If necessary, contactIBM Software Support.

GTM7606I MCS MESSAGE QUEUING RESUMED

Explanation: The MCS console is receiving messages.This message indicates that a prior error condition nolonger exists.


GTM7607E MCS ERROR RETRIEVING MESSAGERC=return_code REASON=reason_code

Explanation: An error occurred while the MCSconsole interface was retrieving a message.

Message variables:

return_codeThe return code from the MCSOPMSGGETMSG service

reason_codeThe reason code from the MCSOPMSGGETMSG service


Administrator response: Determine why the MCSconsole cannot receive messages. If necessary, contactIBM Software Support.

GTM7610E INVALID pgm PARAMETERSSUPPLIED parameters

Explanation: Event Pump discovered that parametersthat were supplied to the monitoring program were notvalid.

Message variables:

pgm The name of the monitoring program

parametersThe parameters that were in error

System action: Processing continues. Some DASD andCACHE performance exceptions might be unavailable.

Administrator response: Keep all job logs and contactIBM Software Support.

GTM7611E SYSPLEX DATA SERVICES HAS NOBUFFERS AVAILABLE FOR DATACOLLECTION

Explanation: Event Pump cannot monitor DASD orcache performance because z/OS ResourceMeasurement Facility™ (RMF) was started with no SMFbuffers.

System action: Processing continues. Some DASD andcache performance exceptions might be unavailable.

Administrator response: Restart RMF specifying theSMFBUF parameter.

GTM7612E NOT AUTHORIZED TO ACCESSSYSPLEX DATA SERVICES

Explanation: Event Pump cannot monitor DASD orcache performance because the Event Pump addressspace cannot use sysplex data services.


Administrator response: Ensure that the sourcecollector address space can use ERBSDS.SMFDATA inthe FACILITY resource class.


GTM7613E SYSPLEX DATA SERVICES typeREQUEST FAILED RETURNCODE=return_code REASONCODE=reason_code

Explanation: An error occurred while processing thespecified sysplex data services request type.

Message variables:

type The type of request

return_codeThe failing return code

reason_codeThe failing reason code



GTM7614I UNABLE TO USE SYSPLEX DATASERVICES RMF IS NOT ACTIVE

Explanation: Event Pump cannot monitor DASD orcache performance because z/OS ResourceMeasurement Facility (RMF) is not active.


Administrator response: Start the RMF address space.

GTM7615E LOAD FAILED FOR MODULE pgm

Explanation: Event Pump cannot load the programthat is required to monitor DASD and cacheperformance.

Message variables:

pgm The name of the program that Event Pumpcannot load


Administrator response: Check for the program thatis named in the LPALIB or LINKLST concatenation. Ifyou cannot determine the cause of the failure, contactIBM Software Support.

GTM7616E UNABLE TO OBTAIN STORAGE FORSYSPLEX DATA SERVICES BUFFER sizereturn_code

Explanation: Event Pump cannot obtain a buffer tocontain the information for DASD and cacheperformance monitoring.

Message variables:

size The amount of storage that was requested

return_codeThe storage return code


Administrator response: Try to determine the cause ofthe failure. If you cannot resolve the problem, keep alljob logs and contact IBM Software Support.

GTM7620I QUEUE MAX RECS CURRENT RECSPCT USED CURRENT THRES/PCTLOST RECS TOTAL RECS

Explanation: This message is issued in response to theQUEUE command. The message forms a heading forthe subsequent GTM7621I messages that describe thequeues.

GTM7621I queue max_recs curr_recs pct_usedcurr_thresh lost_recs total_recs full

Explanation: This message is issued in response to theQUEUE command. It is issued once for every queuethat is contained in the event distributor.

Message variables:

queue The name of the queue that is reported

max_recsThe maximum number of records that can beheld by the queue

curr_recsThe current number of records on the queue

pct_usedThe percentage of the queue currently in use

curr_threshThe threshold value that, when exceeded,results in a message being issued

lost_recsThe number of records that are discarded as aresult of the queue being in a full condition

total_recsThe total number of records that are written tothe queue

full FULL or a blank, indicating whether the queueis currently in a full condition


GTM7622I QUEUE queue HAS BEEN RESET

Explanation: The queue was successfully reset as aresult of the QUEUE RESET command.

Message variables:

queue The name of the queue that is reset

System action: The queue is reset to turn off the full


condition and to permit new records to be written tothe queue.

GTM7624I UNABLE TO RESET QUEUE queue THEQUEUE IS AT 100 PERCENT

Explanation: The QUEUE RESET command wasissued, but the queue cannot be reset because it iscurrently at its maximum capacity.

Message variables:


System action: The queue is not reset and subsequentnew records cannot be written to the queue.

GTM7625E LATCH ERROR ON QUEUE queue

Explanation: An error occurred when attempting toobtain the latch for the indicated queue.

Message variables:

queue The name of the queue for which the error isbeing reported

System action: The queue is not reset. Regularprocessing continues.

Administrator response: This message indicates aninternal error. Obtain a dump of the data space and theaddress space that reports the error. Keep all logs andcontact IBM Software Support.

GTM7626I QUEUE queue NOT FOUND

Explanation: The QUEUE RESET command wasissued with a queue name that does not exist.

Message variables:

queue The name of the queue that was entered in thecommand

System action: No queue is reset and processingcontinues.

Administrator response: Verify that the name of thequeue entered was correct. Issue the QUEUE commandwith no parameters to obtain a list of valid queuenames. Enter the command again with the correctqueue name.

GTM7627I QUEUE COMMAND TERMINATED,SYNTAX ERROR

Explanation: The QUEUE command was enteredincorrectly. The only currently supported option of theQUEUE command is the RESET option.

System action: No action is taken and processingcontinues.

Administrator response: Enter the command againwith the correct syntax, either QUEUE or QUEUERESET queue_name. See the Event Pump for

z/OS Command Reference for more information.

GTM7628I QUEUE COMMAND TERMINATED,DATASPACE NOT CONNECTED

Explanation: The QUEUE command was entered on asource collector or an event distributor that is notconnected to a data space.

System action: No action is taken and processingcontinues.

Administrator response: The QUEUE command canbe used only on an event distributor or a sourcecollector that is currently connected to a data space.Ensure that the object data space is started andconnected to the event distributor or source collectorbefore using the QUEUE command.

GTM7629I QUEUE COMMAND COMPLETE

Explanation: The QUEUE command successfullycompleted.

GTM7702E REXX ENVIRONMENT CREATEFAILED RC=return_codeREASON=reason_code

Explanation: An error occurred when attempting tocreate a REXX environment.

Message variables:

return_codeThe return code from the AOPRXENV macro

reason_codeThe reason code from the AOPRXENV macro


Administrator response: Determine if the addressspace can load the necessary REXX modules.

Ensure that sufficient region storage is allocated to theissuing address space. If this procedure does notresolve the problem, contact IBM Software Support.

GTM7703E REXX HOST ENVIRONMENT CREATEFAILED RC=return_code

Explanation: An error occurred creating the REXXhost environment.

Message variables:

return_codeThe return code from the AOPRXENV macro

System action: Processing continues but the resultsare unpredictable.

Administrator response: Determine if the addressspace can load the necessary REXX modules.

Ensure that sufficient region storage is allocated to theissuing address space. If this action does not resolve the


problem, contact IBM Software Support.

GTM7705E DATASPACE QPUT FAILED WITHRC=return_code

Explanation: An error occurred attempting to store arecord to a data space queue.

Message variables:

return_codeThe return code from the operation


Administrator response: Determine if the data spaceaddress space is available. If the problem continues,collect all logs and contact IBM Software Support.

GTM7707E CROSS MEMORY POST FAILED WITHRC=return_code

Explanation: An error occurred attempting across-memory post.

Message variables:

return_codeThe return code from the cross-memory postrequest

System action: Processing continues but the resultsare unpredictable.

Administrator response: Ensure that the sourcecollector exhausted the available virtual storage. If theproblem continues, contact IBM Software Support.

GTM7800E UNABLE TO OBTAIN TRAPSTORAGE

Explanation: Insufficient virtual storage was availableto create a trap.


Administrator response: The error indicates that thesource collector exhausted the available virtual storage.Use the REGION parameter of the JCL EXEC statementto increase the amount of available virtual storage.

GTM7801I STORAGE ALLOCATED FOR numberTRAPS

Explanation: Displays the maximum number of trapsthat can be created.

Message variables:

number The maximum number of traps that can becreated


GTM7802E UNABLE TO OBTAIN TRAP QUEUEHEADER STORAGE

Explanation: Insufficient virtual storage was availableto create a trap queue header.



GTM7803E UNABLE TO OBTAIN TRAP INDEXSTORAGE

Explanation: Insufficient virtual storage was availableto create a trap queue index.



GTM7811E AOPPARM GET FAILURE FORparameter

Explanation: An error occurred when attempting toobtain the indicated parameter.

Message variables:

parameterThe parameter that is being requested at thetime of the error

System action: Processing continues but the RODMinterface functions are unavailable.

Administrator response: This message is an indicationof a prior failure. Examine previous messages for theappropriate course of action.

GTM7812E EKG_CONNECT RC=return_codeREASON=reason_code

Explanation: An invalid return code was receivedfrom the EKG_CONNECT call.

Message variables:

return_codeThe EKG_CONNECT return code value

reason_codeThe EKG_CONNECT reason code value

System action: Processing continues but the RODMinterface functions are unavailable.

Administrator response: Determine the source of theincorrect message. See the IBM Tivoli NetView for z/OSResource Object Data Manager and GMFHS Programmer’sGuide for more information.


If the problem cannot be resolved, collect all logs andcontact IBM Software Support.

GTM7813I type RC=return_codeREASON=reason_code

Explanation: An error occurred during a request toRODM.

Message variables:

type The type of RODM request

return_codeThe return code from the request

reason_codeThe reason code from the request

System action: Processing continues but results areunpredictable.



GTM7815I ITZP HAS CONNECTED TO RODM :name

Explanation: Event Pump successfully connected tothe named RODM system.

Message variables:

name The name of the RODM system


GTM7816I ITZP HAS DISCONNECTED FROMRODM : name

Explanation: Event Pump successfully disconnectedfrom the named RODM system.

Message variables:



GTM7817I ITZP RODM: name TERMINATIONDETECTED.

Explanation: Event Pump detected that the namedRODM system stopped.

Message variables:


System action: Processing continues. Event Pumpautomatically reconnects to RODM when it is available.

GTM7818I ITZP RODM : MISSING OR INVALIDDATA IN NOTIFY MSG : text

Explanation: Processing continues and results can beunpredictable. Event Pump detected data that is notvalid in the notify message received from RODM.

Message variables:

text The text of the message that is being processed

System action: Processing continues. The message isignored.



GTM7819I ITZP: state

Explanation: This message is a RODM status message.

Message variables:

state The state of the RODM connection


GTM7820I ITZP: COMMAND OPTION MUST BESTART OR STOP

Explanation: An incorrect option was specified on theRODM command to start or stop the RODM interface.


Administrator response: Enter the command again inthe correct format. See the IBM Tivoli NetView for z/OSResource Object Data Manager and GMFHS Programmer’sGuide for more information.

GTM7821E ITZP: ALREADY CONNECTED TORODM

Explanation: An attempt was made to start theRODM connection when it was already active.


GTM7822E ITZP: ALREADY DISCONNECTEDFROM RODM

Explanation: A request was made to stop the RODMconnection when it was not active



GTM7823E ITZP: RODM NOT AVAILABLE.AWAITING RODM: name

Explanation: An attempt was made to start theRODM connection when RODM was not available.

Message variables:


System action: Event Pump suspends the RODMprocessing until the named RODM system becomesavailable.

Administrator response: Ensure that the RODM taskis activated.

GTM7831E ABEND DETECTED PROGRAM=pgmEXCEPTION TERMINATEDEXCEPTION NAME=exception

Explanation: A program that is being used by thenamed exception ended abnormally.

Message variables:

pgm The name of the program that endedabnormally

exceptionThe name of the exception for which theprogram was being run

System action: The exception is no longer processed.

Administrator response: Keep the SVC dump that isprovided and all job logs and contact IBM SoftwareSupport.

GTM7832E ERROR REMOVING REPORTERPROGRAM pgm

Explanation: An error was encountered whileremoving a definition for the program. This messageindicates an internal error.

Message variables:

pgm The program name from which the removerequest was running



GTM7833E ERROR REMOVING COLLECTORPROGRAM pgm

Explanation: An error was encountered whileremoving a definition for the program. This messageindicates an internal error.

Message variables:

pgm The program name from which the removerequest was running



GTM7835E UNABLE TO OBTAIN STORAGE FORAOPMNEXP

Explanation: The system cannot allocate enoughvirtual storage to add an exception.

System action: Processing continues. Some exceptionsmight be unavailable.

Administrator response: The error indicates that thesource collector has used all the available virtualstorage. Use the REGION parameter of the JCL EXECstatement to increase the amount of available virtualstorage.

GTM7836E ERROR DEFINING REPORTERPROGRAM pgm

Explanation: An error was encountered while addinga definition for a program. This message indicates aninternal error.

Message variables:

pgm The name of the program that is being defined



GTM7837E ERROR DEFINING COLLECTORPROGRAM pgm

Explanation: An error was encountered while addinga definition for a program.

Message variables:

pgm The name of the program that is being defined



GTM7838E EXCEPTION PREVIOUSLY DEFINED,EXCEPTION=exception

Explanation: An attempt was made to add anexception which exists. This message indicates aninternal error.

Message variables:

exceptionThe name of the exception for which therequest was made


System action: Processing continues. The existingexception is not affected.


GTM7839E INVALID MONITOR REQUEST TYPEREQUEST IGNORED

Explanation: A request that was not valid was madeto the monitor subtask. This message indicates aninternal error.

System action: Results are unpredictable.


GTM7840E INVALID MONITOR REQUESTBLOCK REQUEST QUEUE CLEARED

Explanation: A request that was not valid was madeto the monitor subtask. This message indicates aninternal error.

System action: Results are unpredictable.


GTM7841E LOAD OF MODULE AOPMNPRGFAILED RC=return_code

Explanation: The load of the AOPMNPRG modulewas unsuccessful. This module is required for thesuccessful operation of the monitor subtask.

Message variables:

return_codeThe return code from the load request

System action: Processing continues. No exceptionsare available.



Explanation: The monitor subtask cannot obtain therequired working storage.


Administrator response: The error indicates that thesource collector has used all the available virtualstorage. Use the REGION parameter of the JCL EXECstatement to increase the amount of available virtualstorage.

GTM7843E GLOBAL VARIABLE RETRIEVEFAILED RC=return_code

Explanation: An error was encountered whileaccessing a global variable required during eventnotification.

Message variables:

return_codeThe return code from the global variableretrieve


Administrator response: This message is preceded byother messages. Use those messages to investigate thecause of the failure. If a problem continues, keep all joblogs and contact IBM Software Support.

GTM7844E DATASPACE QPUT FAILED WITHRC=return_code

Explanation: A failure occurred while writing anotification to the data space.

Message variables:

return_codeThe return code from the queue put operation




Explanation: A failure occurred during cross memorypost processing.

Message variables:

return_codeThe return code from the post operation


Administrator response: Check that the eventdistributor address space is active. If a problemcontinues, keep all job logs and contact IBM SoftwareSupport.

GTM7851E UNABLE TO OBTAIN LOCAL AREAFOR PROGRAM pgm LENGTH=length

Explanation: The monitor subtask cannot obtain therequired storage.

Message variables:


pgm The program for which the request was beingmade

length The amount of virtual storage that is beingrequested

System action: Processing continues, but someexceptions might not be available.

Administrator response: The error indicates that thesource collector used all the available variable storage.Use the REGION parameter of the JCL EXEC statementto increase the amount of available virtual storage.

GTM7852E INVALID AOPMNPRG REMOVEREQUEST

Explanation: The monitor subtask program managerreceived a remove program request that was not valid.This message indicates an internal error.



GTM7853E LOAD FAILED FOR MONITORPROGRAM pgm RC=return_code

Explanation: The system cannot load the requiredmonitor program.

Message variables:

pgm The name of the program that the system wasattempting to load

return_codeThe return code from the load request



GTM7854E UNABLE TO OBTAIN AOPMNPRGSTORAGE LENGTH=pgm


Message variables:

pgm The length of the virtual storage that wasrequested


Administrator response: The error indicates that thesource collector has used all the available virtualstorage. Use the REGION parameter of the JCL EXECstatement to increase the storage amount.

GTM7855E INVALID AOPMNPRG ADD REQUEST

Explanation: The monitor subtask program managerreceived an add program request that was not valid.This message indicates an internal error.



GTM7856E INVALID MONITOR PROGRAMREQUEST TYPE SUPPLIED

Explanation: The monitor subtask program managerreceived a request that is not valid.



GTM7857E UNABLE TO OBTAIN WORKINGSTORAGE FOR AOPMNMPG


System action: Processing continues, but noexceptions are available.

Administrator response: The error indicates that thesource collector used all the available virtual storage.Use the REGION parameter of the JCL EXEC statementto increase the amount of available virtual storage.

GTM7858E ERROR RECEIVED FROM PROGRAMpgm DURING INIT|TERM.RC=return_code

Explanation: A return code that was not valid wasreceived during an Initialize or Terminate request to amonitoring program.

Message variables:

pgm The name of the program

return_codeThe return code received



GTM7860E text

Explanation: This message was issued during theprocessing of a SHOW EXCPS command. The text canbe one of the following messages:


MONITOR SUBTASK IS NOT ACTIVEThe monitor subtask was not active.

AOPMONS : UNABLE TO OBTAIN AOPSTGSTORAGE

The source collector cannot obtain sufficientvirtual storage.

OPTION command_option IS INVALID, SPECIFYLONG OR NOLIST

An invalid option was detected.

Message variables:

command_optionThe option that is not valid

System action: The SHOW EXCPS command ends.

Administrator response: If the Monitor subtask wasnot active, keep all job logs and contact IBM SoftwareSupport.

If the source collector cannot obtain sufficient virtualstorage, use the REGION parameter of the JCL EXECstatement to increase the amount of available virtualstorage.

If the command option was invalid, correct the syntaxand issue the command again.

GTM7861I exception STATUS status MATCHEDcount OF processed

Explanation: The status of an exception is displayed.

Message variables:

exceptionThe exception name

status The status (True or False) of the exception

count The number of times that the exceptionevaluated

processedThe number of times that the exception wasrun


GTM7862I text

Explanation: This message displays detailedinformation about an exception when the SHOWEXCPS command is issued.

Message variables:

text The detail about the exception


GTM7863I TOTAL NUMBER OFEXCEPTIONS=count

Explanation: The number of exceptions that wereprocessed by the SHOW command are displayed.

Message variables:

count The parameter that is being processed


GTM7870E AOPPARM GET FAILURE FORparameter

Explanation: A failure occurred while attempting toread a parameter for the z/OS Resource MeasurementFacility (RMF) collector.

Message variables:

parameterThe parameter that is being processed



GTM7871E INVALID parameter PARM SPECIFIEDDATA WAS value

Explanation: The value that is specified for theparameter is invalid.

Message variables:

parameterThe parameter that is being processed

value The value specified


Administrator response: Correct the parameter andrestart the source collector.

GTM7872E REQUIRED parameter PARM NOTFOUND

Explanation: A required parameter was not specified.

Message variables:

parameterThe name of the parameter that was notspecified


Administrator response: See the Event Pump forz/OS Installation and Configuration Guide for parameter


information. Correct the parameter and restart theaddress space.

GTM7873I TCP/IP INTERFACE UNAVAILABLE

Explanation: The initialization of the Internet Protocolinterface did not complete. The z/OS ResourceMeasurement Facility (RMF) collector ends.

System action: Processing continues. RMF monitoringis not available.

Administrator response: This error can occur if theInternet Protocol is not available on this system. If so,this message is an informational message.

If this message is issued because of an error, it ispreceded by other messages. Use those messages toinvestigate the error.

GTM7874E ERROR DURING TCP/IP typeREQUEST RC=return_codeREASON=reason_code

Explanation: An Internet Protocol request failed.

Message variables:

type The type of request that failed

return_codeThe hexadecimal representation of the returncode

reason_codeThe hexadecimal representation of the reasoncode


Administrator response: Investigate the meaning ofthe return and reason codes. If this procedure does notresolve the problem, keep all job logs and contact IBMSoftware Support.

GTM7875E INTERNAL ERROR UNABLE TOLOCATE TCP/IP GLOBAL AREA

Explanation: The z/OS Resource MeasurementFacility (RMF) collector cannot locate the InternetProtocol global error.

System action: Processing continues. Some RMFmonitoring might not be available.


GTM7876E INTERNAL ERROR TCP/IP GLOBALAREA INACTIVE

Explanation: The z/OS Resource MeasurementFacility (RMF) collector found the Internet Protocolglobal area was inactive.



GTM7877E UNABLE TO OBTAIN BUFFERSTORAGE FOR RMF PROCESSING

Explanation: The z/OS Resource MeasurementFacility (RMF) collector cannot obtain the requiredstorage.



GTM7878E UNABLE TO LOCATE TCP/IPADDRESS SPACE

Explanation: The z/OS Resource MeasurementFacility (RMF) collector cannot locate an active InternetProtocol address space with which to communicate.

System action: Processing continues. RMF monitoringis not available.

Administrator response: Ensure that an InternetProtocol is active on the system. Specify theTCPIP_TASKNAME parameter to direct the RMFmonitor to a specific address space.

GTM7879E TCP/IP INDICATES THATTCPIP_TASKNAME=value IS INVALID

Explanation: The value that is specified in theTCPIP_TASKNAME parameter is rejected by theInternet Protocol interface.

Message variables:

value The TCPIP_TASKNAME value that is rejected

System action: Processing continues. z/OS ResourceMeasurement Facility (RMF) monitoring is notavailable.

Administrator response: Ensure that an InternetProtocol is active on the system. Ensure that the valuespecified in the TCPIP_TASKNAME parameter is validand corresponds to the name of the TCP/IP addressspace on the operating system where the sourcecollector is running.

GTM7880E INVALID RMF REPORTER PARMSUPPLIED parameter

Explanation: The parameter that was passed to thez/OS Resource Measurement Facility (RMF) reporterduring the registration process was not valid.


Message variables:

parameterThe parameter that was passed to the RMFreporter program

System action: The exception, which is in the processof being defined, is not added.


GTM7881E PPI INTERFACE IS INACTIVE

Explanation: The PPI Manager task is not running.

System action: Processing continues. Event Pumpcannot receive information through the NetView®

program-to-program interface (PPI).

Administrator response: Verify that the sourcecollector startup parameter (PPI=YES) is specified.

GTM7882E GETMAIN FAILED FOR PPI RECEIVEBUFFER

Explanation: Event Pump cannot allocate virtualstorage for a receive buffer.

System action: Processing continues. Event Pumpcannot receive information through the NetViewprogram-to-program interface (PPI).

Administrator response: The error indicates that theavailable virtual storage was exhausted by the sourcecollector. Use the REGION parameter of the JCL EXECstatement to increase the amount of available virtualstorage.

GTM7883E PPI RECEIVER LOSTCOMMUNICATION

Explanation: The NetView program-to-programinterface (PPI) lost communication with the NetViewsubsystem interface (SSI).

Administrator response: Start the NetView SSI. Enablethe PPI by issuing the following command:

F source_collector,PPI ENABLE

GTM7884I category MESSAGES RECEIVED: count

Explanation: This message identifies the number ofmessages received from the NetViewprogram-to-program interface (PPI). See the SHOW PPIcommand.

Message variables:

category The category of messages

count The count of messages received


GTM7885E type FAILED FOR PPI - DTR=valueRC=return_code

Explanation: A NetView program-to-program interface(PPI) function failed for the requested PPI datatransport request (DTR).

Message variables:

type The type of PPI function

value The DTR value from the request

return_codeThe count of messages that were received


Administrator response: See the IBM Tivoli NetViewfor z/OS Application Programmer’s Guide to identify thereturn code for the DTR type. Also, see the NetViewtroubleshooting information for appropriate action.

GTM7887E PPI OPTION IS INVALID

Explanation: A NetView program-to-program interface(PPI) command that was not valid was entered.

System action: Processing continues, and no action istaken.

Administrator response: See the source collectorcommand usage documentation referencing the PPIcommands.

GTM7888I PPI TRACE IS status

Explanation: This message indicates the status of theNetView program-to-program interface (PPI) tracefacility.

Message variables:

status The status of the PPI trace facility. Thepossible values are as follows:* ACTIVE

The PPI trace is enabled. The PPImessages that were received arewritten to the AOPxxLOG DD name.

* INACTIVEThe PPI trace is disabled.


GTM7881I PPI BUFFER QUEUE LIMIT IS limit

Explanation: The Buffer Queue Limit number isdisplayed when the PPI RESET queue_limit command isissued. See the IBM Tivoli NetView for z/OS libraryregarding NetView program-to-program interface (PPI)usage to determine when it might be appropriate tochange this value. The PPI_BUFFER_QUEUE_LIMITstartup parameter for the source collector initially setsthis value.

Message variables:


limit The buffer queue limit


GTM7890I PPI RECEIVER IS status

Explanation: This message indicates the status of theNetView program-to-program interface (PPI) receiver.

Message variables:

status The status of the PPI receiver as follows:* ACTIVE

The PPI receiver is running.* INACTIVE

The PPI receiver is not running.


Administrator response: When the PPI receiver statusis ACTIVE, no action is necessary. When the PPIreceiver status is INACTIVE, see the IBM Tivoli NetViewfor z/OS Troubleshooting Guide.

GTM7891E UNABLE TO DETERMINECOMMAND NAME

Explanation: GTMAOPH4, the REXX consolecommand handler program, was called but it cannotdetermine the command name from the input data.


Administrator response: Contact IBM SoftwareSupport for assistance in determining why thecommand handler was called without data.

GTM7892E UNABLE TO DETERMINECOMMAND NAME, RC= return code

Explanation: GTMAOPH4, the REXX consolecommand handler program, received a return codeother than 0 when retrieving the configurationparameter for the command. The parameter name is asfollows, where name is the command name that wasentered on the console:

GTMAOPH4_name

Message variables:

return codeThe return code from the request


Administrator response: Return code 4 indicates thatthe required parameter was not defined to the sourcecollector. Any return code other than 0 indicates thatthe parameter service experienced an error retrievingthe parameter. Contact IBM Software Support forassistance in determining why the failure occurred.

GTM7893E UNABLE TO DETERMINECOMMAND NAME

Explanation: No data was defined for the commandparameter that was retrieved by the command handlerprogram, GTMAOPH4. The parameter name is asfollows, where name is the command name that wasentered on the console:

GTMAOPH4_name


Administrator response: Contact IBM SoftwareSupport for assistance in determining why theparameter is empty.

GTM7900W FREEMAIN FAILED CSECT=pgmOFFSET=address R15=return_codePROCESS CONTINUING

Explanation: A FREEMAIN macro failed.

Message variables:

pgm The program name

address The address that was being released

return codeThe return code from the FREEMAIN macro


Administrator response: Determine why theFREEMAIN macro failed. If necessary, contact IBMSoftware Support.

GTM8000E SEND - NO DATA TO SEND

Explanation: The data address and length was notprovided on the AOPIPR SEND function call.

System action: Processing continues but the data isnot sent.

Administrator response: Check the data that wasprovided to the GTMAOPE0 utility. If this message isissued when the GTMAOPE0 utility is not being used,collect all logs and contact IBM Software Support.

GTM8001E function - NO CONNECTION EXISTS

Explanation: An attempt was made to perform thespecified AOPIPR function, but it was not connected.

Message variables:

function The function, which can be DISCONNECT,SEND, or RECEIVE


Administrator response: Collect all logs and contactIBM Software Support.


GTM8002E SEND - GETMAIN identifier FAILEDFOR SEND BUFFER

Explanation: The amount of storage was insufficient.

Message variables:

identifierA unique number specifying which GETMAINrequest failed


Administrator response: Check the region size todetermine if it must be increased.

GTM8003E function - TCPIP_SERVICE FAILED TOLOAD

Explanation: The TCPIP_SERVICE API cannot loadand process the Internet Protocol function.

Message variables:

function The function, either CONNECT,DISCONNECT, SEND, RECEIVE, orGETIPADDRESS


Administrator response: Check the TCP/IP addressspace. The address space might not be available.

GTM8005E function - NO CARRIAGE CONTROLCHARACTER FOUND

Explanation: The AOPIPR interface processed a dataelement that did not end with the ASCII carriagecontrol character X'0A'.

Message variables:

function The function, which can be SEND or RECEIVE



GTM8006E SEND - DATA LENGTH EXCEEDSBUFFER SIZE

Explanation: An attempt was made to send a dataelement that exceeded the maximum buffer size.


Administrator response: Collect all logs and contactIBM Software Support.

GTM8007E RECEIVE - CONVERT NOT SPECIFIED

Explanation: The CONVERT option was not specifiedon the AOPIPR RECEIVE function call. The AOPIPRRECEIVE function did not receive a correct responsemessage from the socket that is communicating on theother end.


Administrator response: Specify CONVERT=’YES’ on thereceive function call.

GTM8008E CONNECT - GETMAIN FAILED FORiprstg STORAGE

Explanation: Storage is insufficient because the iprstgstorage area was not obtained during the CONNECTfunction request.

Message variables:

iprstg The name of the storage area, which is IPST orTCCB

System action: The connection fails.

Administrator response: Check the region size. Theregion size might need to be increased.

GTM8009E CONNECT - IP ADDRESS AND PORTREQUIRED

Explanation: An IPADDR or PORT value was notprovided for the AOPIPR CONNECT function.


Administrator response: Provide a valid InternetProtocol address and port number.

GTM8010E CONNECT - INVALID BUFFER SIZE

Explanation: The BUFFER_SIZE operand that wasspecified on the AOPIPR CONNECT function isincorrect.


Administrator response: Verify that the value for theBUFFER_SIZE operand is in the range 1 - 33.

GTM8011E GET IP ADDRESS - HOST NAME NOTFOUND

Explanation: The name that was provided with theTCPIP_SERVER_NAME operand for the AOPIPRGETIPADDRESS function cannot be found.


Administrator response: Verify that the name for theTCPIP_SERVER_NAME operand is configured in theLOCAL.HOST data set that is used by TCP/IP.


GTM8012E GET IP ADDRESS - INVALID TCPIPNAME

Explanation: The name that was provided with theTCPIP_SERVER_NAME operand for the AOPIPRGETIPADDRESS function is incorrect.


Administrator response: Verify that theTCPIP_SERVER_NAME operand is alphanumeric. Theoperand can be 1 - 24 characters in length.

GTM8013E CONVERT IP ADDRESS - INVALIDTCPIP ADDRESS

Explanation: The IP address that is provided with theTCPIP_SERVER_ADDRESS operand for the AOPIPRCONVERTIPADDRESS function is not valid.


Administrator response: Verify that theTCPIP_SERVER_ADDRESS operand contains a validTCP/IP address in character-based format.

GTM8014E CONVERT PORTNUM - INVALIDTCPIP PORT NUMBER

Explanation: The port number that is provided withthe TCPIP_SERVER_PORT operand for the AOPIPRCONVERTIPADDRESS function is incorrect.


Administrator response: Verify that theTCPIP_SERVER_PORT operand contains a validTCP/IPl port number. The number is in the range1 - 32767.

GTM8015E function - STIMER SET FAILED FORTCPIP_SERVICE return_code

Explanation: The requested function failed whenattempting to start the timer for the tcpip_service call.

Message variables:

function The function that failed:v CONNECTv DISCONNECTv SENDv RECEIVEv GETIPADDRESS



Administrator response: See the MVS macro servicesfor the return code that is associated with the STIMERfunction.

GTM8016E function - TIMEOUT OCCURRED FORTCPIP_SERVICE

Explanation: The tcpip_service service call did notcomplete processing before the TIMEOUT valuespecified on the function request.

Message variables:



Administrator response: Verify that the receiving endof the TCP/IP connection is available for use. Check toensure that TBSM=NO is specified if you are runningwithout Tivoli Business Service Manager Release 3.1.

GTM8017E function - UNRECOGNIZED EVENTOCCURRED FOR TCPIP_SERVICE

Explanation: The AOPIPR interface cannot process theevent for the specified function request.

Message variables:




GTM8018E function - INVALID TIMEOUT VALUE

Explanation: The specified TIMEOUT value isincorrect.

Message variables:



Administrator response: Verify that the TIMEOUTvalue. The number is represented in seconds in therange 30 - 86400.


GTM8019E RECEIVE - NO RESPONSE MESSAGERECEIVED

Explanation: The receiving application is designed toreturn a specific message back to the sender applicationupon sending the last data element. This messageincludes the return code that is processed by thereceiving application. The response message is notreceived.


Administrator response: Verify that a commandrequest is sent to the receiving application as the lastdata element. See the AOPIPR macro specifications.

GTM8020E INVALID PARAMETERS SUPPLIEDparameters

Explanation: Parameters that are not valid weresupplied to the GTMDCOLV utility.

Message variables:

parametersThe parameters that are in error

System action: The GTMDCOLV utility ends.

Administrator response: See the Event Pump forz/OS Installation and Configuration Guide for moreinformation.

GTM8021E ERROR OBTAINING SMSINFORMATION FOR VOLUME volserRC=return_code

Explanation: The GTMDCOLV utility cannot collectsystem managed storage (SMS) information for thevolser volume.

Message variables:

volser The serial number of the volume for which theerror occurred

return_codeThe return code from the SMS facility

System action: The GTMDCOLV utility ends.


GTM8030I PROCESSING COMPLETEDSUCCESSFULLY

Explanation: The TCP/IP application transmitted allthe data to the receiving application. The receivingapplication processed all the data successfully.

System action: Processing ends.

GTM8031I PROCESSING TERMINATEDUNSUCCESSFULLY

Explanation: The TCP/IP application did notcomplete.

System action: Processing ends.

Administrator response: See the previous errormessages that were written to the SYSPRINT log.

GTM8032E OPEN FILE FAILURE FOR DDNAMEddname

Explanation: The file to be used for the DD name thatwas requested cannot be opened.

Message variables:

ddname The DD name

System action: The GTMAOPE0 utility ends.

Administrator response: Verify that the data set oroutput specification is valid in the JCL. See the EventPump for z/OS Installation and Configuration Guide formore information.

GTM8033E KEYWORD IS TOO LONG INPREVIOUS CONTROL CARD

Explanation: The specified keyword is not codedcorrectly.


Administrator response: Verify that the syntax for thespecified keyword in the previous control statement.See the Event Pump for z/OS Installation andConfiguration Guide for more information.

GTM8034E KEYWORD IS MISSING IN PREVIOUSCONTROL CARD

Explanation: The specified keyword is missing theequal sign (=) to separate the operand.


Administrator response: Verify the syntax for thespecified keyword in the previous control statement.See the Event Pump for z/OS Installation andConfiguration Guide for more information.

GTM8035E KEYWORD IS NOT SUPPORTED INPREVIOUS CONTROL CARD

Explanation: An invalid keyword was detected on acontrol statement to the GTMAOPE0 utility.

System action: The keyword is not used.

Administrator response: Verify that all controlstatement keywords are valid before running the utility.See the Event Pump for z/OS Installation andConfiguration Guide for more information.


GTM8036E KEYWORD OPERAND IS MISSING INPREVIOUS CONTROL CARD

Explanation: The data operand for the requestedkeyword is not specified.

System action: The keyword is not used.

Administrator response: Verify that a proper value isspecified for the requested keyword. See the EventPump for z/OS Installation and Configuration Guide formore information.

GTM8037E TCPIP_ADDRESS OR TCPIP_NAMECONTROL CARD IS REQUIRED

Explanation: The TCPIP_ADDRESS or TCPIP_NAMEcontrol statement is not specified.


Administrator response: Add one of the indicatedcontrol statements to establish a connection. See theEvent Pump for z/OS Installation and Configuration Guidefor more information.

GTM8038E TCPIP_PORT CONTROL CARD ISREQUIRED

Explanation: The TCPIP_PORT control statement isnot specified.


Administrator response: Add the indicated controlstatement to establish the connection. See the EventPump for z/OS Installation and Configuration Guide formore information.

GTM8039E COMMAND CONTROL CARD ISREQUIRED

Explanation: The COMMAND control statement is notspecified.


Administrator response: Add the COMMAND controlstatement specifying the command alias name to be runby the ASIMVSIPListenerSvc service for Event Pump.See the Event Pump for z/OS Installation andConfiguration Guide for more information.

GTM8040I source_data TRANSMISSION STARTED

Explanation: The data is now being sent to thereceiving application.

Message variables:

source_dataThe name of the source data


GTM8041I ddname RECORDS SENT

Explanation: The ddname records were successfullysent.

Message variables:

ddname The DD name


GTM8042I DUPLICATE keyword CONTROL CARDPREVIOUS CARD IS IGNORED

Explanation: The specified control statement isentered more than once.

Message variables:

keyword The keyword name


Administrator response: The first control statement isread, processed, and used. Remove the duplicatestatements.

GTM8043I TCPIP ADDRESS IS ALREADY USEDPREVIOUS CARD IS IGNORED

Explanation: Both the TCPIP_ADDRESS andTCPIP_NAME control statements are specified.


Administrator response: Remove the controlstatement that is not required and not used.

GTM8044I BUFFER SIZE IS OUT OF RANGESETTING DEFAULT BUFFERSIZE TO 1

Explanation: The BUFFERSIZE value that wasspecified is outside of the supported range.


Administrator response: Change the BUFFERSIZE toa supported value in the range 1 - 33. See the EventPump for z/OS Installation and Configuration Guide formore information.

GTM8045I BUFFER SIZE IS NOT NUMERICSETTING DEFAULT BUFFERSIZE TO 1

Explanation: The BUFFERSIZE value is specifiedincorrectly.


Administrator response: Correct the BUFFERSIZEvalue to a valid number in the range 1 - 33. See theEvent Pump for z/OS Installation and Configuration Guidefor more information.


GTM8046I TIMEOUT IS OUT OF RANGESETTING DEFAULT TIMEOUT VALUETO 30

Explanation: The TIMEOUT value that was specifiedis outside of the supported range.


Administrator response: Change the TIMEOUT valueto a supported value in the range 1 - 86400. See theEvent Pump for z/OS Installation and Configuration Guidefor more information.

GTM8047I TIMEOUT IS NOT NUMERICSETTING DEFAULT TIMEOUT TO 30

Explanation: The TIMEOUT value is specifiedincorrectly.


Administrator response: Change the TIMEOUT valueto a valid number in the range 1 - 86400. See the EventPump for z/OS Installation and Configuration Guide formore information.

GTM8049E CODEPAGE NUMBER IS INVALID

Explanation: The CODEPAGE operand is not a validnumber.

System action: The GTMOPE0 utility ends.

Administrator response: Change the CODEPAGEoperand to the numeric value that is to be used. See theEvent Pump for z/OS Installation and Configuration Guidefor more information.

GTM8050E CODEPAGE CONTROL CARD ISREQUIRED

Explanation: The CODEPAGE control statement is notspecified.


Administrator response: Add the CODEPAGE controlstatement to request the correct translation table to beused. See the Event Pump for z/OS Installation andConfiguration Guide for more information.

GTM8051E message_text

Explanation: A failure occurred during processing ofthe transmitted data.


Administrator response: See the Event Pump log filefor the ASIIPMVSListenerSvc service. Depending on themessage text that was specified, different actions arerequired, as follows:

v COMMAND ALIAS command_name NOT FOUND

Explanation: The command alias name that wastransmitted to the ASIMVSListenerSvc service cannotbe found in the command registry key.

Administrator Response: Verify that the commandalias name is entered into the command registry key.

v REMOTE CODEPAGE IS INVALID

Explanation: The code page that was transmitted tothe ASIMVSListenerSvc service is not a supportedcode page.

Administrator response: Correct the code page andretransmit the data.

v CLIENT HOST VALIDATION FAILED ON HOSThost_name port

Explanation: The MVS client for the host name or IPaddress is not configured in the ValidClient registrykey for the ASIMVSListenerSvc service.

Administrator Response: Add the client host nameor IP address to the ValidClient registry key andrestart the service. Run the discovery job again.

GTM8052E FORMAT_TYPE VALUE IS INVALID

Explanation: The value that was specified for theFORMAT_TYPE option is not valid.


Administrator response: See the Event Pump forz/OS Installation and Configuration Guide and correct thedata operand value.

GTM8053E data_separator BYTE VALUE IS INVALID

Explanation: The data separator byte that wasspecified is too long or has a value that exceeds 255(X'FF')

Message variables:

data_separatorThe name of the data separator


Administrator response: Correct the data operand toindicate the data separator to be used for thetransmission process. See the Event Pump forz/OS Installation and Configuration Guide for moreinformation.

GTM8054E INVALID TCPIP JOBNAME SPECIFIED

Explanation: The TCP/IP job name that is coded isincorrect and cannot be processed.


Administrator response: Verify that the TCP/IP jobname is correct. Ensure that the length does not exceed8 characters.


GTM8055E CONVERT REQUESTED WITH TEXTMODE ON

Explanation: The CONVERT option can be used onlywhile sending character data. The text mode must beset to OFF.


Administrator response: Set the option to TEXT=NO,or you can delete the TEXT keyword control statement.The default value is NO.

GTM8060E NO COMMAND CONTROL CARDSPROCESSED RODM DATA WILL NOTBE COLLECTED

Explanation: No COMMAND NAME controlstatements were specified. At least one commandkeyword statement must be specified or theAOPRODMD utility does not run.

System action: The RODM unload utility ends.

Administrator response: Add a COMMAND controlstatement specifying the RODM source that is to betransmitted to Event Pump. See the GTMOPE1 utilitydocumentation.

GTM8070I INVALID TRACE OPERANDSPECIFIED SETTING DEFAULT TOTRACE BUFFERS

Explanation: The TRACE operand can be specifiedonly with the BUFFERS or RECORDS option. TheBUFFERS option is used as the default value if anoption is not correctly specified.


Administrator response: Specify a valid TRACEoperand.

GTM8071I TRACE RECORDS OPTION IN EFFECT

Explanation: The records that are read in are writtento the TRACE DD file.


GTM8072I TRACE BUFFERS OPTION IN EFFECT

Explanation: The buffers that are populated with therecords that are read in are written to the TRACE DDfile.


GTM8200E name : PRIMARY TCPIP_ADDRESS ORTCPIP_NAME IS NOT SPECIFIED

Explanation: The TCP/IP parameter identifying the IPlistener host system that is to receive the eventmessages is not specified.

Message variables:

name The name of the IP service task

System action: The event distributor address spaceends.

Administrator response: Specify the TCP/IP hostaddress or host name in the event distributor startupparameters. Restart the event distributor.

GTM8201E name : PRIMARY PORT NUMBER ISNOT SPECIFIED

Explanation: The TCP/IP port number identifying theIP listener host system that is to receive the eventmessages is not specified.

Message variables:



Administrator response: Specify the TCP/IP portnumber in the event distributor startup parameters.Restart the event distributor.

GTM8202I name : BACKUP TCPIP ADDRESS ANDPORT IS NOT SPECIFIED

Explanation: The primary connection failed and theevent distributor switched to use the backup IP hostsystem. The retry parameters were specified and thebackup IP parameters were not specified.

Message variables:



Administrator response: Specify the TCP/IP backupIP host and port number to be used in the event theprimary connection fails. Restart the event distributor.

GTM8203E name MGR : INITIALIZATION FAILED

Explanation: The IP service task did not initialize.

Message variables:



Administrator response: Identify preceding messagesthat might indicate why the service task cannotinitialize. Check to ensure that TBSM=NO is specified ifyou are running without Tivoli Business ServiceManager Release 3.1. Correct the problem and restartthe event distributor.


GTM8204I name MGR : TERMINATED

Explanation: The event distributor ended the servicetask manager during shutdown processing.

Message variables:



GTM8205I name : READY TO TRANSMIT TO name

Explanation: The event distributor is waiting forevents to send to the Netcool/OMNIbus probe.

Message variables:


name The IP address or host name of the IP listenersystem to which the event distributorconnected and is ready to sendNetcool/OMNIbus probe event data


GTM8206I name : SWITCHING OVER TO name

Explanation: The event distributor switched over andconnected to the backup IP listener host system, eitherautomatically as a result of a connection failure orbecause the SWITCH command was issued. The eventdistributor is now ready to send event data to thissystem.

Message variables:


name The IP address or host name of the IP listenersystem to which the event distributor switchedover and connected


GTM8207I name : CONNECTIONREESTABLISHED

Explanation: The event distributor reconnected to theIP listener host system.

Message variables:



GTM8208E name : function STIMERM SERVICEFAILED RC=return_code

Explanation: The event distributor failed while issuinga STIMERM service call.

Message variables:


function The name of the function that was running theSTIMERM service

return_codeThe return code indicating the failure of theSTIMERM service call



GTM8209E name : GETMAIN FAILED FORRECEIVE RESPONSE MESSAGEBUFFER

Explanation: The event distributor failed to obtainstorage while receiving a response message from TivoliBusiness Service Manager.

Message variables:




GTM8250E name : SERVER TCPIP_ADDRESS ORTCPIP_NAME IS NOT SPECIFIED

Explanation: The TCP/IP parameter identifying the IPserver address is not specified. The event distributorcannot receive registration data from Tivoli BusinessService Manager.

Message variables:


System action: The address space ends.

Administrator response: Specify the IP server addressor name for the system on which the event distributoris running. Restart the event distributor.

GTM8251E name : SERVER PORT NUMBER ISNOT SPECIFIED

Explanation: The TCP/IP parameter identifying the IPserver port number is not specified. The eventdistributor cannot receive registration data from TivoliBusiness Service Manager.

Message variables:



Administrator response: Specify the IP server portnumber for the system on which the event distributoris running. Restart the event distributor.


GTM8252I name : LISTENING ON PORT name

Explanation: The TCP/IP server port number isreceiving registration data from Tivoli Business ServiceManager.

Message variables:


name The listening port number


GTM8270E name : UNABLE TO OBTAIN STORAGEFOR THE RECEIVE BUFFER number

Explanation: The storage is insufficient for the receivebuffer.

Message variables:


number A number indicating which GETMAIN callfailed

System action: The Receive function ends and resultscan be unpredictable.


GTM8271I CLIENT CONNECTED FROM PORT:host_name address port

Explanation: The event distributor IP Listener serviceobtained a connection from Tivoli Business ServiceManager.

Message variables:

host_nameThe Tivoli Business Service Manager hostname of the system that connected to theevent distributor

address The Tivoli Business Service Manager IPaddress of the system that connected to theevent distributor

port The Tivoli Business Service Manager portnumber of the system that connected to theevent distributor


GTM8272E CLIENT IS NOT AUTHORIZED:host_name

Explanation: A Tivoli Business Service Manager hostsystem attempted to connect to the event distributorbut the IP address or host name of the client is notauthorized to register events for monitoring.

Message variables:

host_nameThe Tivoli Business Service Manager hostname or IP address of the client system


Administrator response: Add a VALIDCLIENTparameter to the startup parameters of the eventdistributor specifying the Tivoli Business ServiceManager Client host name or IP Address. Restart theevent distributor.

GTM8300I COMMUNICATION WITH TBSMDISABLED BY USER REQUEST

Explanation: A user requested that Event Pump nottry to start communication with Tivoli Business ServiceManager (TBSM) on a Windows system.

System action: Event Pump does not try to startcommunication with TBSM on a Windows system.Registration, which is required by some TBSM feedsincluding RMF and OMEGAMON feeds, does notoccur.

Administrator response: This message is usuallyissued when the TBSM=NO parameter is specified. Ifcommunication with TBSM on a Windows system isrequired, change this parameter to YES and restartEvent Pump.

GTM8542E GTMSEND: GETMAIN FAILED FORWORKING STORAGE

Explanation: The event distributor failed to obtainstorage while sending a message to Tivoli BusinessService Manager.



GTM8544I GTMSEND: SESSION NOTESTABLISHED

Explanation: The event distributor failed to allocate anLU 6.2 session to communicate with Tivoli BusinessService Manager.

System action: Processing continues. A subsequentattempt might be made to reallocate the session if aretry is allowed.

Administrator response: Ensure that the LU asspecified in the REMOTE_APPLID parameter isavailable.


GTM8545E GTMSEND: STIMERM SERVICEFAILED

Explanation: A request to the STIMERM service failed.



GTM8546I GTMSEND: WAITING FORCONNECTION

Explanation: The event distributor SENDcommunications program is waiting for the LU 6.2connection to the Windows system to be established.


Administrator response: Determine why theconnection to the Windows system is not available. Ifnecessary, contact IBM Software Support.

GTM8547I GTMSEND: SESSION ESTABLISHED

Explanation: The event distributor communicationsSEND program established an LU 6.2 connection withthe partner session.


GTM8550E AUTO DISCOVERY IS NOT ABLE TOACCESS OMEGAMON: name INPROGRAM program_name

Explanation: A CICS autodiscovery request cannotcomplete because the OMEGAMON session is not inthe correct state.

Message variables:

name The name of the OMEGAMON session

program_nameThe name of the program that detected theerror

System action: The CICS autodiscovery request ends.

Administrator response: Use the SHOW SESSIONScommand to determine the status of the session. Trythe CICS autodiscovery request again while the sessionis active.

GTM8550I GTMSEND: SHUTDOWN DETECTED

Explanation: The event distributor communicationsSEND program received a shutdown request.

System action: The session is ended.

GTM8551E GTMSEND: EXCEEDED NUMBER OFRETRY ATTEMPTS TO ESTABLISHLU62 SESSION

Explanation: When the event distributor attempted toconnect to the partner LU, the initial attempt failed. Aretry was allowed, but the retry also failed.


Administrator response: Determine why the eventdistributor cannot connect to the partner LU. Ifnecessary, contact IBM Software Support.

GTM8552E GTMSEND: RESOURCE LIMITATION,UNABLE TO ATTEMPT TOESTABLISH LU62 CONNECTION

Explanation: The event distributor cannot connect tothe partner LU because the VTAM program indicatedthat sufficient resources are not available for thesession.


Administrator response: Check that the VTAM APPLdefinitions for the session on the host and partner LUare correctly defined. If necessary, contact IBM SoftwareSupport.

GTM8553E GTMSEND : request function FAILED

Explanation: The specified function within theACC1SEND program failed.

Message variables:

request The name of the program that detected theerror

function Possible function values are as follows:

v QCREATE

Explanation: Queue creation failed for theworkstation queue within the data space.

Administrator Response: Review the eventdistributor job log to see if it has anyadditional messages that are related to thefailure. Review the WSQUEUESIZEparameter of the event distributor and theDATASPACESIZE parameter of the dataspace. If necessary, restart the data spaceand event distributor.

v QINIT

Explanation: Queue initialization failed forthe workstation queue within the dataspace.

Administrator response: Review the eventdistributor job log to see if it has anyadditional messages that are related to thefailure. Review the WSQUEUESIZE


parameter of the event distributor and theDATASPACESIZE parameter of the dataspace. If necessary, restart the data spaceand event distributor.

v NOTIFY

Explanation: An error occurred when thesend communications program within theevent distributor requested that it benotified when a session was establishedwith the partner LU over the LU 6.2communications session.

Administrator response: Review the eventdistributor and system console logs to see ifthey have any additional messages that arerelated to the failure. Review the logs on theSNA Server system for any error messages.If necessary, restart the SNA server and theevent distributor.

v WAIT

Explanation: An error occurred when thesend communications program issued a waitrequest to the event distributorcommunications manager while waiting fora NOTIFY request to complete (wait forsession to be established).

Administrator Response: Review the eventdistributor and system console logs to see ifthey have any additional messages that arerelated to the failure. If necessary, restart theevent distributor.

v DATAWAIT

Explanation: An error occurred whilerequesting a wait for data to be placed onthe workstation queue.

Administrator response: Review the eventdistributor log to see if it has any additionalmessages that are related to the failure. Ifnecessary, restart the event distributor.

v SEND

Explanation: An error occurred whilesending data to the partner LU over the LU6.2 session.

Administrator response: Review the eventdistributor and system console logs to see ifthey have any additional messages that arerelated to the failure. If necessary, restart theevent distributor and the SNA server.

v WAITSEND

Explanation: An error occurred when thesend communications program issued a waitrequest to the event distributorcommunications manager while waiting fora NOTIFY request to complete (wait for thesession to be established).

Administrator response: Review the eventdistributor and system console logs to see if

they have any additional messages that arerelated to the failure. If necessary, restart theevent distributor.

v WAITALLO

Explanation: An error occurred when thesend communications program attempted tostart a session with the partner LU.

Administrator response: Review the eventdistributor and system console logs to see ifthey have any additional messages that arerelated to the failure. Review the SNAserver system logs to see if any errors werereported there. Check that the ACC1RCVprocess is correctly defined to the SNAserver and that the associated processes arerunning.


GTM8554E GTMSEND: SESSIONDISCONNECTED

Explanation: The session with the partner LU waslost.


Administrator response: Determine why the sessionwas lost and correct the problem. If necessary, contactIBM Software Support.

GTM8559I GTMSEND: TERMINATED

Explanation: The event distributor communicationsSEND program ended.

System action: The session ends.

GTM8660E ACC1RECV: GETMAIN FAILED FORtype

Explanation: A GETMAIN request failed for thespecified storage within the RECEIVE communicationsprogram.

Message variables:

type The type of storage requested

System action: The receive function ends and resultscan be unpredictable.

Administrator response: Determine why theGETMAIN request failed. If necessary, contact IBMSoftware Support.

GTM8662I SHUTDOWN DETECTED

Explanation: The event distributor communicationsRECEIVE program received a shutdown request.



GTM8663E name: SESSION DISCONNECTED

Explanation: The session with the partner LU waslost.

Message variables:

name The name of the issuing program

System action: The system attempts to reestablish thesession. The event distributor waits for the session tobecome available again and attempts to reconnect thepartner LU.

Administrator response: Determine why the sessionwas lost and correct the problem. If necessary, contactIBM Software Support.

GTM8664E name : type FAILED

Explanation: The request service failed.

Message variables:

name The name of the issuing program

type The type of request that is being processed




Explanation: This post failure indicates that the eventmessages cannot be received by the event distributor.

Message variables:

return_codeThe return code of the POST failure



GTM8670I EDR INTERFACE NOT AVAILABLE

Explanation: An EDR command was issued to theEvent Pump event distributor, but the event drivenregistration (EDR) interface was not enabled in theEvent Pump event distributor.

System action: Processing continues, and the EDRinterface is not available.

Administrator response: Determine if you want theEDR interface to be active in the Event Pump eventdistributor. If so, add the required DD statements to theEvent Pump event distributor or determine why theinterface was not enabled during Event Pump eventdistributor initialization.

GTM8671I INTERFACE ALREADY status

Explanation: The EDR START or EDR STOP commandto the Event Pump event distributor was issued, butthe interface is already started or stopped.

Message variables:

status The status of the interface, which is eitherSTARTED or STOPPED

System action: Processing continues, the command isignored.

GTM8672I

Explanation: The EDR STATUS or EDR LOGcommand was entered to the Event Pump eventdistributor. This message provides the results of thecommand.

Message variables:

status The status of the interface, which is eitherSTARTED or STOPPED


GTM8673I statustype status

Explanation: The EDR STATUS or EDR LOGcommand was entered to the Event Pump eventdistributor. This message provides the results of thecommand. START or EDR STOP command to the EventPump event distributor was issued.

Message variables:

statustypeThe status type is as follows:v EDR INTERFACE IS :v EDR LOG STATUS IS :v RECORDS PROCESSED :v RECORDS SELECTED FOR EDR :v SENT FOR REGISTRATION :v RECORDS FAILED TO QUEUE :v ALREADY SENT FOR REGISTRATION :v RECORDS INCORRECT :

status The status for the given status type, as follows:v For EDR INTERFACE IS, the status shows

the status of the interface, which is eitherSTARTED, STOPPED, or HALTED.

v For EDR LOG STATUS IS, the status showsthe current setting of the EDR LOG option.– YES indicates that EDR events and the

return code from the EDR call aredisplayed in the system log file.

– NO indicates that logging of events andreturn codes is not done.

v For RECORDS PROCESSED, the statusshows the total number of records that wereprocessed.


v For RECORDS SELECTED FOR EDR, thestatus shows the total number of recordsthat were selected by the EDR.

v For SENT FOR REGISTRATION, the statusshows the total number of Event Pumpevent records that were successfully sent forregistration.

v For RECORDS FAILED TO QUEUE, thestatus shows the total number of EventPump event records that were not sent

v For ALREADY SENT FOR REGISTRATION,the status shows the total number of recordsthat were already sent for registration asEvent Pump events.

v For RECORDS INCORRECT, the statusshows the total number of incorrect records.


GTM8674E EDR STATUS IS HALTED CANNOTCHANGE

Explanation: The EDR START or EDR STOP commandwas issued against the Event Pump event distributor,but the previous attempt to initialize the EDR interfacefailed. The interface was marked as halted.

System action: Processing continues. The EDRinterface status is unchanged.

Administrator response: Determine why the EDRinterface did not initialize by reviewing the SYSLOGand SYSOUT output of the Event Pump eventdistributor.

GTM8675I EDR INTERFACE REFRESHED

Explanation: The EDR REFRESH command wasissued against the Event Pump event distributor. TheEDR select table was successfully rebuilt.


GTM8676E EDR INTERFACE REFRESH FAILEDINTERFACE HALTED

Explanation: EDR REFRESH command was issued tothe Event Pump event distributor. The rebuild of theTivoli Enterprise Console EDR interface select tablefailed.


Administrator response: Review the SYSLOG andSYSOUT output to determine why the interface failedto build the select table. Correct any errors in the selecttable input and reissue the EDR REFRESH command.

GTM8677E UNABLE TO LOAD GTMEDR01CANNOT REFRESH EDR INTERFACE

Explanation: The EDR REFRESH command wasissued to the Event Pump event distributor. Theinterface cannot load the GTMEDR01 program. Theinterface select table cannot be refreshed.

System action: The interface select table cannot berefreshed.

Administrator response: Review the SYSLOG andSYSOUT output to determine why the interface cannotload the GTMEDR01 program. Correct the error andreissue the REFRESH command.

GTM8678I OPEN ERROR FOR DDNAME ddname

Explanation: While building the select table for theEDR interface, the interface cannot open the specifiedDD name.

Message variables:

ddnameThe DD name, which is either GTMEDRSP orGTMEDRSL


Administrator response: Review the SYSLOG andSYSOUT output to determine why the interface cannotopen the specified DD name. Correct the error, andthen stop and restart the event distributor


Notices

This information was developed for products and services offered in the U.S.A.

IBM may not offer the products, services, or features discussed in this document inother countries. Consult your local IBM representative for information on theproducts and services currently available in your area. Any reference to an IBMproduct, program, or service is not intended to state or imply that only that IBMproduct, program, or service may be used. Any functionally equivalent product,program, or service that does not infringe any IBM intellectual property right maybe used instead. However, it is the user's responsibility to evaluate and verify theoperation of any non-IBM product, program, or service.

IBM may have patents or pending patent applications covering subject matterdescribed in this document. The furnishing of this document does not give youany license to these patents. You can send license inquiries, in writing, to:

IBM Director of LicensingIBM CorporationNorth Castle DriveArmonk, NY 10504-1785U.S.A.

For license inquiries regarding double-byte (DBCS) information, contact the IBMIntellectual Property Department in your country or send inquiries, in writing, to:

Intellectual Property LicensingLegal and Intellectual Property LawIBM Japan, Ltd.1623-14, Shimotsuruma, Yamato-shiKanagawa 242-8502 Japan

The following paragraph does not apply to the United Kingdom or any othercountry where such provisions are inconsistent with local law:

INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THISPUBLICATION "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHEREXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIEDWARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY OR FITNESSFOR A PARTICULAR PURPOSE.

Some states do not allow disclaimer of express or implied warranties in certaintransactions, therefore, this statement might not apply to you.

This information could include technical inaccuracies or typographical errors.Changes are periodically made to the information herein; these changes will beincorporated in new editions of the publication. IBM may make improvementsand/or changes in the product(s) and/or the program(s) described in thispublication at any time without notice.

Any references in this information to non-IBM web sites are provided forconvenience only and do not in any manner serve as an endorsement of those web


sites. The materials at those web sites are not part of the materials for this IBMproduct and use of those web sites is at your own risk.

IBM may use or distribute any of the information you supply in any way itbelieves appropriate without incurring any obligation to you.

Licensees of this program who wish to have information about it for the purposeof enabling: (i) the exchange of information between independently createdprograms and other programs (including this one) and (ii) the mutual use of theinformation which has been exchanged, should contact:

IBM Corporation2Z4A/10111400 Burnet RoadAustin, TX 78758U.S.A.

Such information may be available, subject to appropriate terms and conditions,including in some cases payment of a fee.

The licensed program described in this document and all licensed materialavailable for it are provided by IBM under terms of the IBM Customer Agreement,IBM International Program License Agreement or any equivalent agreementbetween us.

Information concerning non-IBM products was obtained from the suppliers ofthose products, their published announcements or other publicly available sources.IBM has not tested those products and cannot confirm the accuracy ofperformance, compatibility or any other claims related to non-IBM products.Questions on the capabilities of non-IBM products should be addressed to thesuppliers of those products.

All statements regarding IBM's future direction or intent are subject to change orwithdrawal without notice, and represent goals and objectives only.

This information contains examples of data and reports used in daily businessoperations. To illustrate them as completely as possible, the examples include thenames of individuals, companies, brands, and products. All of these names arefictitious and any similarity to the names and addresses used by an actual businessenterprise is entirely coincidental.

TrademarksIBM, the IBM logo, and ibm.com are trademarks or registered trademarks ofInternational Business Machines Corp., registered in many jurisdictions worldwide.Other product and service names might be trademarks of IBM or other companies.A current list of IBM trademarks is available on the web at "Copyright andtrademark information" at http://www.ibm.com/legal/copytrade.shtml .

Adobe is a trademark of Adobe Systems Incorporated in the United States, and/orother countries.

Windows is a trademark of Microsoft Corporation in the United States, othercountries, or both.


http://www.ibm.com/legal/copytrade.shtml

UNIX is a registered trademark of The Open Group in the United States and othercountries.

Other company, product, and service names may be trademarks or service marksof others.

Notices 129

��

Product Number: 5698-B34

Printed in USA

GC27-2310-05

ibmtivoli event pump for z/os version 4.2 · ibm tivoli event pump for z/os library this following...

Documents