EYUNL0151I I    date time applid Get Topology for resource {UNKNOWN | AUTINSTMODEL | CONNECTION | DB2 CONNECTION | DB2 ENTRY | DB2 TRANSACTION | DOCUMENT TEMPLATE | DATA SET NAMES | ENQUEUE MODEL | GLOBAL EXITS | TASK EXITS | FEPI CONNECTIONS | FEPI NODE | FEPI POOL | FEPI TARGET | FILE | JOURNAL | JOURNALNAMES | MODENAME | PARTNER | PROCESS TYPE | PROFILE | PROGRAM | REQUEST MODEL | SYSTEM DUMP CODES | TCP/IP SERVICE | TDQUEUE | TERMINAL | TRANSACTION | TRANSACTION DUMP CODES | TRANCLASS | TEMP STORAGE MODEL | IP CONNECTION | LIBRARY | WEB SERVICE | URIMAP | PIPELINE | ATOMSERVICE | BUNDLE | EVENT BINDING | JVM SERVER | CAPTURE SPEC | XML TRANSFORM | EP ADAPTER | CAPTURE SPEC OPT PRED | CAPTURE SPEC DATA PRED | CAPTURE SPEC INFO SRC | OSGI BUNDLE | OSGI SERVICE | EP ADAPTER SET | DB2 PACKAGESET | MQ MONITOR} has zero data records.

Explanation

Topology data collection for the specified resource returned no data. Either no data was available, or a problem occurred during the data collection process, where:

restype

Identifies the type of resource for which no data was returned as one of the following:

  • ATOMSERVICE

  • AUTINSTMODEL

  • BUNDLE

  • CAPTURE SPEC

  • CAPTURE SPEC OPT PRED

  • CAPTURE SPEC DATA PRED

  • CAPTURE SPEC INFO PRED

  • CFDT POOL

  • CONNECTION

  • DATA SET NAMES

  • DB2 CONNECTION

  • DB2 ENTRY

  • DB2 PACKAGESET

  • DB2 TRANSACTION

  • ENQUEUE MODEL

  • EVENT BINDING

  • EVENT PROCESSING ADAPTER

  • EVENT PROCESSING ADAPTER SET

  • FEPI CONNECTIONS

  • FEPI NODE

  • FEPI POOL

  • FEPI TARGET

  • FILE

  • GLOBAL EXITS

  • IP CONNECTION

  • JOURNAL

  • JOURNALNAMES

  • JVM SERVER

  • LIBRARY

  • MODENAME

  • MQMONITOR

  • PARTNER

  • PIPELINE

  • PROCESS TYPE

  • PROFILE

  • PROGRAM

  • REQUEST MODEL

  • SYSTEM DUMP CODES

  • TASK EXITS

  • TCP/IP SERVICE

  • TDQUEUE

  • TEMP STORAGE MODEL

  • TERMINAL

  • TRANCLASS

  • TRANSACTION DUMP CODES

  • TRANSACTION

  • URIMAP

  • WEB SERVICE

  • XML TRANSFORM

System action

Topology data collection continues with the next resource.

User response

If no topology data was expected for the specified resource, no action is required.

If topology data was expected, a problem may have occurred during data collection. In that case, this message is preceded by one of three messages, either EYUNL0150W, EYUNL0152W or EYUNL0153W. Refer to the appropriate message for details on the cause of the problem.

Module

EYU0NLGT, EYU1NLGT

XMEOUT parameters/Message inserts

  1. date
  2. time
  3. applid
  4. Value chosen from the following options:

Destination

COLG



EYUNL0151II.html | Timestamp icon Last updated: Sunday, 4 June 2017