ZBEVF DISPLAY: Display business event processing information
Use this command to display information about the business event environment on the z/TPF system.
Last updated
Added in 2023.
Requirements and restrictions
None.
Format
- FILe-descriptor
- Specifies the name of a business event specification or business event dispatch adapter specification, where descriptor is the
case-sensitive, alphanumeric file name or a wildcard pattern for descriptor file names. Only file
extensions .evspec.xml and .evda.xml are supported. If you
specify the name (descriptor) with a leading slash (/), command processing treats
the value as a fully qualified file name. If you specify descriptor without a
leading slash (/), command processing uses the standard file path for common deployment (/sys/tpf_pbfiles/tpf-fdes).Note: If the file name contains special characters such as a space or dollar sign ($), enclose the name in single quotation marks (') or dollar signs ($). For example, if the file name is my dd.evspec.xml, you must specify FILE-'my dd.evspec.xml'. If you want to use the single quotation mark (') as part of the string, you must enclose the string in dollar signs ($) or use two single quotation marks, one after the other ('').
- DETail
- Displays information for the specified business event
or business event dispatch adapter. Specify one of the following values:
- No
- Displays a summary of the information.
- Yes
- Displays detailed information.
- EVent
- Displays information about the business events that are loaded to the z/TPF system at the current activation level. The information that is displayed depends on the additional parameters that are specified. If you do not specify any parameters after the EVENT parameter, all business events that are loaded and activated are displayed.
- eventname
- The case-sensitive name of a specific business event or a wildcard pattern that resolves to 0 or more business event names.
- DISPAdapter
- Displays all business events that use the specified business event dispatch adapter name.
- daname
- The case-sensitive name of a specific business event dispatch adapter or a wildcard pattern that resolves to 0 or more dispatch adapter names. If you do not specify this parameter with the DISPATCH and ADAPTER parameters, all business event dispatch adapters that are loaded and activated are displayed.
- DISPQueue-dispatchQueueName
- Displays one of the following items, where dispatchQueueName is the name of a
dispatch queue or a wildcard pattern that resolves to 0 or more dispatch queues:
- If you specify this parameter with the EVent parameter, displays all business events that use the specified business event dispatch queue.
- If you specify this parameter without the EVent parameter, displays all specified business event dispatch queues on the z/TPF system.
- QType-queueType
- Displays all business event dispatch queues for the specified queue
type, where queueType is the type of a dispatch queue. Specify one of the
following values:
- ALL
- Displays all business event dispatch queues.
- ORDered
- Displays all ordered business event dispatch queues.
- REMote
- Displays all remote business event dispatch queues.
- UNOrdered
- Displays all unordered business event dispatch queues, including the system default dispatch queue.
- EVType
- Displays all business events for the specified
business event type. Specify one of the following values:
- DATADf
- Displays all data events for z/TPFDF files.
- DATATpf
- Displays all data events for z/TPF files.
- SIGnal
- Displays all signal events.
- ID-id
- Displays all data events at the current activation level for the specified ID or a wildcard pattern that resolves to 0 or more IDs, where id is a 4-digit hexadecimal z/TPF record ID or z/TPFDF file ID. Literal indicators on this value (for example, ID-''id'') are ignored.
- Dispatch Adapter
- Displays information about the business event dispatch adapters that are loaded on the z/TPF system at the current activation level. Responses show both deployed and undeployed dispatch adapters.
- SETtings
- Displays business event processing control values.
- USage
- Displays the usage information for business events and business event dispatch adapters for the specified time period.
- TIMe-seconds
- Specifies the time period that you want to collect usage information for, where seconds is the number of seconds in the range 0 - 99. If you specify a value of 0, the usage information is collected for 1 second. Usage counts are collected at the start of the time period and at the end of the time period. The actual usage information is the difference between the counts at the start and end of the interval.
- ACTivation
- Displays information based on the activation level. Specify one of the following values:
- CURrent
- Displays information for business events and business event dispatch adapters at their latest activation level.
- ALL
- Displays information for each business event and business event dispatch adapter at all activation levels.
- STatus
- Displays information based on status. Specify one of the following values:
- DEPloyed
- Displays information for deployed items.
- UNDeployed
- Displays information for undeployed items.
- ALL
- Displays information for both deployed and undeployed items.
- TYPe
- Displays information based on type. Specify one of the following values:
- ALL
- Displays information for both business events and business event dispatch adapters that are loaded on the z/TPF system.
- Dispatch
- Displays information for the business event dispatch adapters that are loaded on the z/TPF system.
- EVent
- Displays information for the business events that are loaded on the z/TPF system.
- ERRors
- Displays the number of errors that were received. For business events, the number of errors represents the number of times that the event could not be added to the dispatch queue. For business event dispatch adapters, the number of errors represents the number of times that the data format program or the data transport program received errors.
Additional information
- Online help information is available for this command. To display the help information, enter
one of the following commands:
- ZBEVF HELP
- ZBEVF ?
- The ZBEVF commands rely on the following business event
deployment descriptors:
- Business event specification, which is a z/TPF-specific XML file that is a valid instance of the specific business event specification schema.
- Business event dispatch adapter specification, which is a z/TPF-specific XML file that is a valid instance of the specific business event dispatch adapter specification schema.
- The supported wildcard characters are asterisks and question marks at any position in a wildcard-enabled name. Use an asterisk (*) to match zero or more characters, use a question mark (?) to match exactly one character; for example, "my*name0?*".
- If the name of a wildcard-enabled name on your system contains a wildcard-designated character and you want to reference that name in a ZBEVF DISPLAY command display, enclose the name in two single quotation marks, for example, ''event*?name''.
Examples
The following example shows latest activation level information about the business event files
with names that contain the number 2 and end with evspec.xml or
evda.xml in the /sys/tpf_pbfiles/tpf-fdes
directory. This display is sorted by file name in the FILE IN /sys/tpf_pbfiles/tpf-fdes column.
User: ZBEVF DISPLAY FILE-*2*
System: BEVF0063I 09.09.43 DISPLAY OF BUSINESS EVENT FILES
FILTERS: FILe-*2*
NAME TYPE STATUS FILE IN /sys/tpf_pbfiles/tpf-fdes
AIRFandAIRT2 DISPATCH DEPLOY AIRFandAIRT2.evda.xml _
TPFDEVTC1F2 DATATPF UNDEP DEB5_C1F2_A2_destination.de.evspec.xml
TPFDEVTE8C2 DATATPF UNDEP DEB5_E8C2_YB_destination.de.evspec.xml
TPFDEVTE8F2 DATATPF UNDEP DEB5_E8F2_Y2_destination.de.evspec.xml
AIRFa?dA*RT2 DISPATCH DEPLOY dsq2.evda.xml
flyt2abraham SIGNAL UNDEP flyt2.evspec.xml _
Purchas?Update2 DATADF UNDEP PurchaseUpdate2.evspec.xml
7 FILES MATCH FILTERS
END OF DISPLAY+
The following example shows information about the specified event message signal event.
User: ZBEVF DISPLAY FILE-sendLetter.se.evspec.xml
System: BEVF0046I 14.06.31 DISPLAY OF EVENT MESSAGE SIGNAL EVENT sendLetter IN
FILE-/sys/tpf_pbfiles/tpf-fdes/sendLetter.se.evspec.xml
STATUS: SIGNAL EVENTS ENABLED ON PROCESSOR B
DEPLOYED: YES
EVENT NAME: sendLetter
APPLICTN ENRICHMNT PGM: AIRA
DISPATCH ENRICHMNT PGM:
PERSISTENCE: NO
PRIORITY: 9
EXPIRY TIME: -1
DISPATCH QUEUE NAME: IBEV.UNORDERED.DISPATCH.QUEUE
REMOTE DISPATCH:
ERROR QUEUE NAME:
EVENT ERROR PROGRAM:
DISPATCH ADAPTER: AIRFandAIRT
EVENT MSG FORMAT FILE: sendLetter.se.dfdl.xsd
END OF DISPLAY+
The following example shows detailed information about the specified event message signal event.
User: ZBEVF DISPLAY FILE-sendLetter.se.evspec.xml DETAIL-YES
System: BEVF047I 14.06.57 DISPLAY OF EVENT MESSAGE SIGNAL EVENT sendLetter IN
FILE-/sys/tpf_pbfiles/tpf-fdes/sendLetter.se.evspec.xml
STATUS: SIGNAL EVENTS ENABLED ON PROCESSOR B
DEPLOYED: YES
EVENT NAME: sendLetter
DESCRIPTION: Initially to test custom formatter
APPLICTN ENRICHMNT PGM: AIRA
DISPATCH ENRICHMNT PGM:
PERSISTENCE: NO
PRIORITY: 9
EXPIRY TIME: -1
DISPATCH QUEUE NAME: IBEV.UNORDERED.DISPATCH.QUEUE
REMOTE DISPATCH:
ERROR QUEUE NAME:
EVENT ERROR PROGRAM:
DISPATCH ADAPTER: AIRFandAIRT
EVENT MSG FORMAT FILE: sendLetter.se.dfdl.xsd
END OF DISPLAY+
The following example shows information about the specified event message data event for a z/TPFDF
file.
User: ZBEVF DISPLAY FILE-pnrupdate.de.evspec.xml
System: BEVF0048I 14.57.45 DISPLAY OF DATA EVENT PNRUpate FOR z/TPFDF IN
FILE-/sys/tpf_pbfiles/tpf-fdes/pnrupdate.de.evspec.xml
STATUS: DATA EVENTS ENABLED ON PROCESSOR B
DEPLOYED: NO
EVENT NAME: PNRUpate
APPLICTN ENRICHMNT PGM:
DISPATCH ENRICHMNT PGM: QPRD
PERSISTENCE: YES
PRIORITY: 1
EXPIRY TIME: -1
DISPATCH QUEUE NAME: IBEV.UNORDERED.DISPATCH.QUEUE
REMOTE DISPATCH:
ERROR QUEUE NAME:
EVENT ERROR PROGRAM:
z/TPFDF FILE NAME: RR01XX
z/TPFDF FILE ID: D7D9
COLLECTION TYPE: SUBFILE
DISPATCH ADAPTER: WMQAdNoneFormat
EVENT MSG FORMAT FILE: pnrupdate.de.dfdl.xsd
END OF DISPLAY+
The following example shows detailed information about the specified event message data event for a z/TPFDF
file.
User: ZBEVF DISPLAY FILE-Credit_Trxns.de.evspec.xml DETAIL-YES
System: BEVF0057I 14.53.46 DISPLAY OF DATA EVENT Credit_Trxns FOR z/TPFDF IN
FILE-/sys/tpf_pbfiles/tpf-fdes/Credit_Trxns.de.evspec.xml
STATUS: DATA EVENTS ENABLED ON PROCESSOR B
DEPLOYED: NO
EVENT NAME: Credit_Trxns
DESCRIPTION: Event message data event to capture just the updat
ed LRECs in the CREDIT database representing credi
t transactions
APPLICTN ENRICHMNT PGM: QCRA
DISPATCH ENRICHMNT PGM:
PERSISTENCE: YES
PRIORITY: 1
EXPIRY TIME: -1
DISPATCH QUEUE NAME: IBEV.UNORDERED.DISPATCH.QUEUE
REMOTE DISPATCH:
ERROR QUEUE NAME:
EVENT ERROR PROGRAM: QCRE
z/TPFDF FILE NAME: DR12ED
z/TPFDF FILE ID: B212
COLLECTION TYPE: UPDATES
DISPATCH ADAPTER: PrintAdapter
WMQAdCBEFormat
EVENT MSG FORMAT FILE: Credit_Trxns.de.dfdl.xsd
LREC INCLUDE LIST:
ID ATTRIBUTES NAME
80 COLLECTOPEN DR12N80
D4 UNIQUE AuthUsers
D7 COLLECTOPEN,UNIQUE Purchases
D8 Credit
END OF LREC INCLUDE LIST
END OF DISPLAY+
The following example shows information about the specified event message data event for a z/TPF
file.
User: ZBEVF DISPLAY FILE-SampleDBEvent.de.evspec.xml
System: BEVF0055I 11.01.21 DISPLAY OF DATA EVENT SampleDBEvent FOR z/TPF IN
FILE-/sys/tpf_pbfiles/tpf-fdes/SampleDBEvent.de.evspec.xml
STATUS: DATA EVENTS ENABLED ON PROCESSOR B
DEPLOYED: YES
EVENT NAME: SampleDBEvent
APPLICTN ENRICHMNT PGM:
DISPATCH ENRICHMNT PGM:
PERSISTENCE: YES
PRIORITY: 7
EXPIRY TIME: -1
DISPATCH QUEUE NAME: IBEV.UNORDERED.DISPATCH.QUEUE
ERROR QUEUE NAME:
EVENT ERROR PROGRAM:
z/TPF COLLECTION NAME: SampleDB
z/TPF RECORD ID: C1C2
RECORD TYPES: FIXED: Y LTPOOL: Y STPOOL: N
DISPATCH ADAPTER: PrintAdapter
EVENT MSG FORMAT FILE: SampleDB_EvtMsg.de.dfdl.xsd
END OF DISPLAY+
The following example shows detailed information about the specified event message data event for a z/TPF
file.
User: ZBEVF DISPLAY EVENT SampleDBEvent DETAIL-YES
System: BEVF0056I 11.05.32 DISPLAY OF DATA EVENT SampleDBEvent FOR z/TPF IN
FILE-/sys/tpf_pbfiles/tpf-fdes/SampleDBEvent.de.evspec.xml
STATUS: DATA EVENTS ENABLED ON PROCESSOR B
DEPLOYED: YES
EVENT NAME: SampleDBEvent
DESCRIPTION: Data event for the SampleDB TPF file
APPLICTN ENRICHMNT PGM:
DISPATCH ENRICHMNT PGM:
PERSISTENCE: YES
PRIORITY: 7
EXPIRY TIME: -1
DISPATCH QUEUE NAME: IBEV.UNORDERED.DISPATCH.QUEUE
ERROR QUEUE NAME:
EVENT ERROR PROGRAM:
z/TPF COLLECTION NAME: SampleDB
z/TPF RECORD ID: C1C2
RECORD TYPES: FIXED: Y LTPOOL: Y STPOOL: N
DISPATCH ADAPTER: PrintAdapter
EVENT MSG FORMAT FILE: SampleDB_EvtMsg.de.dfdl.xsd
END OF DISPLAY+
The following example shows information about the specified business event dispatch adapter specification.
User: ZBEVF DISPLAY FILE-evda7.evda.xml DETAIL-NO
System: BEVF0018I 21.28.51 DISPLAY OF DISPATCH ADAPTER Test_DA7 IN
FILE-/sys/tpf_pbfiles/tpf-fdes/evda7.evda.xml
STATUS: ALL EVENTS DISABLED ON PROCESSOR B
DEPLOYED: NO
DISPATCH ADAPTER NAME: Test_DA7
DATA FORMAT: CBE
TRANSPORT: CUSTOM
TRANSPORT CUSTOM PGM: ABC1
END OF DISPLAY+
The following example shows detailed information about the specified business event dispatch adapter specification.
User: ZBEVF DISPLAY FILE-evda7.evda.xml DETAIL-YES
System: BEVF0058I 21.28.56 DISPLAY OF DISPATCH ADAPTER Test_DA7 IN
FILE-/sys/tpf_pbfiles/tpf-fdes/evda7.evda.xml
STATUS: ALL EVENTS DISABLED ON PROCESSOR B
DEPLOYED: NO
DISPATCH ADAPTER NAME: Test_DA7
DESCRIPTION: This is a test file that is used to validate ZBEVF
DISPLAY commands.
DATA FORMAT: CBE
TRANSPORT: CUSTOM
TRANSPORT CUSTOM PGM: ABC1
TRANSPORT CUSTOM PARM: This.is.a.very.long.user.parameter.in.order.to.tes
t.multiple.line.output.messages.in.the.ZBEVF.DISPL
AY.DISPATCH.ADPATER.command.
END OF DISPLAY+
The following example shows information about the specified business event dispatch adapter specification with data events enabled. The
DATA FORMAT
line
displays the EVENTCUSTOM
format, which indicates that this dispatch adapter was
defined by using the <afEventCustomFormat> element in the dispatch adapter specification.
User: ZBEVF DISPLAY DISPATCH ADAPTER EVNTAdEvntFormat
System: BEVF0018I 11.49.55 DISPLAY OF DISPATCH ADAPTER EVNTAdEvntFormat IN
FILE-...s/tpf_pbfiles/tpf-fdes/EVNTAdapterCustomFormat.evda.xml
STATUS: DATA EVENTS ENABLED ON PROCESSOR B
DEPLOYED: YES
DISPATCH ADAPTER NAME: EVNTAdCustFormat
DATA FORMAT: EVENTCUSTOM
DATA FORMAT CUSTOM PGM: QFLF
TRANSPORT: CUSTOM
TRANSPORT CUSTOM PGM: QFLA
END OF DISPLAY+
The following example shows the settings for business events. The UNORDERED USER-DEFINED DISPATCH QUEUES
IN IBEVCNTL section represents the number of unordered user-defined dispatch queues that you specified for the
MAXECBS parameter and the maximum number of unordered user-defined dispatch queues that can be set based on the size of the
IBEVCNTL format-2 global record. To increase the maximum number of
unordered user-defined dispatch queues, see Increasing the size of the IBEVCNTL format-2
global.
User: ZBEVF DISPLAY SETTINGS
System: BEVF0071I 09.47.32 DISPLAY OF BUSINESS EVENT SETTINGS
MAXEVENTS: 0
MAXERRORS: 10
QDEPTHWARN: 2000
SIGNAL EVENTS ENABLED ON PROCS: B C D E Z 0 F G H I J K
L M N O P Q R S T U V W
X Y 1 2 3 4 5 6
DATA EVENTS ENABLED ON PROCS: B C D E Z 0 F G H I J K
L M N O P Q R S T U V W
X Y 1 2 3 4 5 6
UNORDERED USER-DEFINED DISPATCH QUEUES IN IBEVCNTL
CURRENT: 3
MAXIMUM: 20
MAXECB SETTINGS:
DISPATCH QUEUE MAXECBS
IBEV.UNORDERED.DISPATCH.QUEUE (SYSTEM DEFAULT) 10
IBEV.UNORDERED.FLYT 4
IBEV.UNORDERED.MY.QUEUE 25
IBEV.UNORDERED.ZBEVF.EXAMPLE 7
END OF DISPLAY+
The following example shows the usage statistics for deployed business event dispatch adapters in a 3-second time interval. This display is
sorted by usage rate in the RATE column, and then by name in the NAME
column.
User: ZBEVF DISPLAY USAGE TIME-3 TYPE-DISPATCH STATUS-DEPLOYED
System: BEVF0021I 09.36.50 COLLECTION OF BUSINESS EVENT USAGE STARTED.
DISPLAY WILL BE IN 3 SECONDS.+
BEVF0059I 09.36.53 DISPLAY OF BUSINESS EVENT USAGE DURING THE 3-SECOND INTERVAL
FILTERS: ACTivation-CURrent STatus-DEPloyed TYPe-Dispatch
NAME TYPE STATUS LOADSET RATE TOTAL _
AIRFandAIRT DISPATCH DEPLOY BASE 10 26250074
AIRFandAIRT2 DISPATCH DEPLOY BASE 1 605769
CBEandAIRT DISPATCH DEPLOY BASE 0 48850
CBEFileAdapter DISPATCH DEPLOY BASE 0 0 _
CustJSONtoFile DISPATCH DEPLOY BASE 0 0
CustXMLtoFile DISPATCH DEPLOY BASE 0 0
StdXJSONtoFile DISPATCH DEPLOY BASE 0 0
StdXMLtoFile DISPATCH DEPLOY BASE 0 0 _
StdXXMLtoFile DISPATCH DEPLOY BASE 0 0
WMQAdCBEFormat DISPATCH DEPLOY BASE 0 0
WMQAdCustFormat DISPATCH DEPLOY BASE 0 0
WMQAdNoneFormat DISPATCH DEPLOY BASE 0 0 _
12 DISPATCH ADAPTERS MATCH FILTERS TOTALS: 11 26904693
END OF DISPLAY+
The following example shows the number of errors that were received by deployed and undeployed
business events and business event dispatch adapters during business event processing. This display is sorted by number of errors in the
LAST MIN column, and then by name in the NAME
column.
User: ZBEVF DISPLAY ERRORS TYPE-ALL STATUS-ALL
System: BEVF0060I 09.43.34 DISPLAY OF BUSINESS EVENT ERRORS
FILTERS: ACTivation-CURrent STatus-ALL TYPe-ALL
NAME TYPE STATUS LOADSET LAST MIN TOTAL
AIRFandAIRT DISPATCH DEPLOY BASE 0 0
ArrUEnrWMQCBEFmt SIGNAL DEPLOY BASE 0 0 _
ArrUserCBECustAd SIGNAL DEPLOY BASE 0 0
CBEandAIRT DISPATCH UNDEP BASE 0 0
EventCounter DISPATCH DEPLOY BASE 0 0
HotelGuests DATADF UNDEP BDIRT2 0 0 _
HOTR_C8E3 DATATPF DEPLOY BASE 0 0
rocky DISPATCH DEPLOY BASE 0 0
RockyDetails DATADF DEPLOY BASE 0 0
sendLetter SIGNAL DEPLOY BDIRT2 0 0 _
sendLetterRemote SIGNAL DEPLOY BDIRT2 0 0
SixtyFourAdapts SIGNAL DEPLOY BASE 0 0
TPFDEVTE8F3 DATATPF DEPLOY BASE 0 0
TPFDEVTE8F7 DATATPF DEPLOY BASE 0 0 _
WMQAdNoneFormat DISPATCH UNDEP BASE 0 0
10 BUSINESS EVENTS MATCH FILTERS TOTALS: 0 0
5 DISPATCH ADAPTERS MATCH FILTERS TOTALS: 0 0
END OF DISPLAY+
The following example shows information for all business events that are loaded on the z/TPF system.
User: ZBEVF DISPLAY EVENT
System: BEVF0014I 22.17.50 DISPLAY OF ALL BUSINESS EVENTS
NAME STATUS FILE NAME
Event1 DEPLOYED /sys/tpf_pbfiles/tpf-fdes/eves1.evspec.xml
Event3 UNDEPLOYED /sys/tpf_pbfiles/tpf-fdes/eves3.evspec.xml
END OF DISPLAY+
The following example shows all business events with names that begin with
Del followed by any single character, followed by the characters
oc, and ending there or ending with any other characters. This display is
sorted by event name in the NAME column.
User: ZBEVF DISPLAY EVENT Del?oc*
System: BEVF0061I 09.59.23 DISPLAY OF BUSINESS EVENTS
FILTERS: Del?oc*
NAME EVTYPE STATUS FILE IN /sys/tpf_pbfiles/tpf-fdes
DelLocCBECustAd SIGNAL DEPLOY FLYTDelayLocalNoEnrichCBECustAd.evspec.xml _
DelLocCBEWMQAd SIGNAL DEPLOY FLYTDelayLocalNoEnrichCBEWMQAd.evspec.xml
DelLocEnCustCust SIGNAL DEPLOY FLYTDelayLocalEnrichCustFormCustAd.evspec.xml
DelLocEnrCustWMQ SIGNAL DEPLOY FLYTDelayLocEnrichCustomFormatWMQAd.evspec.xml
DelLocStdCustAd SIGNAL UNDEP FLYTDelayLocalNoEnrichStdCustAd.evspec.xml _
5 BUSINESS EVENTS MATCH FILTERS
END OF DISPLAY+
The following examples illustrate ZBEVF command support of event names that
contain one or more wildcard characters. Without quotation marks, the name is interpreted as a
wildcard pattern and the BEVF0061I message is
displayed in response.
User: ZBEVF DISPLAY EVENT Purchas?Update2
System: BEVF0061I 10.12.40 DISPLAY OF BUSINESS EVENTS
FILTERS: Purchas?Update2
NAME EVTYPE STATUS FILE IN /sys/tpf_pbfiles/tpf-fdes
Purchas?Update2 DATADF UNDEP PurchaseUpdate2.evspec.xml
1 BUSINESS EVENTS MATCH FILTERS
END OF DISPLAY+
With the event name enclosed in two single quotation marks, the name is interpreted as an
actual event name and the BEVF0048I message is
displayed in response.User: ZBEVF DISPLAY EVENT ''Purchas?Update2''
System: BEVF0048I 10.12.48 DISPLAY OF DATA EVENT Purchas?Update2 FOR z/TPFDF IN
FILE-/sys/tpf_pbfiles/tpf-fdes/PurchaseUpdate2.evspec.xml
STATUS: DATA EVENTS DISABLED ON PROCESSOR B
DEPLOYED: NO _
EVENT NAME: Purchas?Update2
APPLICTN ENRICHMNT PGM: AIRA
DISPATCH ENRICHMNT PGM: AIRD
PERSISTENCE: NO
PRIORITY: 9
EXPIRY TIME: -1
DISPATCH QUEUE NAME: BLUEBERRY.DISPATCH.QUEUE
REMOTE DISPATCH:
ERROR QUEUE NAME: FLYT.DRIVER.ERROR.QUEUE _
EVENT ERROR PROGRAM: AIRE
z/TPFDF FILE NAME: DR12BI
z/TPFDF FILE ID: B412
COLLECTION TYPE: UPDATES
DISPATCH ADAPTER: AIRFandAIRT2
EVENT MSG FORMAT FILE: PurchasesFolder.de.dfdl.xsd
END OF DISPLAY+
The following example shows information for all business event dispatch adapters that are loaded on the z/TPF system.
User: ZBEVF DISPLAY DISPATCH ADAPTER
System: BEVF0017I 22.17.53 DISPLAY OF ALL DISPATCH ADAPTERS
NAME STATUS FILE NAME
Test_DA1 UNDEPLOYED /sys/tpf_pbfiles/tpf-fdes/evda1.evda.xml
Test_DA2 DEPLOYED /sys/tpf_pbfiles/tpf-fdes/evda2.evda.xml
Test_DA3 DEPLOYED /sys/tpf_pbfiles/tpf-fdes/evda3.evda.xml
Test_DA5 UNDEPLOYED /sys/tpf_pbfiles/tpf-fdes/evda5.evda.xml
Test_DA6 UNDEPLOYED /sys/tpf_pbfiles/tpf-fdes/evda6.evda.xml
Test_DA7 UNDEPLOYED /sys/tpf_pbfiles/tpf-fdes/evda7.evda.xml
END OF DISPLAY+
The following example shows all business event dispatch adapters with names that contain the
string JSON. This display is sorted by dispatch adapter name in the NAME
column.
User: ZBEVF DISPLAY DISPATCH ADAPTER *JSON*
System: BEVF0065I 10.55.48 DISPLAY OF BUSINESS EVENT DISPATCH ADAPTERS
FILTERS: *JSON*
NAME STATUS FILE IN /sys/tpf_pbfiles/tpf-fdes
CustAdJSONFormat DEPLOY FLYTCustomAdapterJSONFormat.evda.xml _
CustAdJSONXForm DEPLOY FLYTCustomAdapterJSONXFormat.evda.xml
CustJSONtoFile DEPLOY CustJSONtoFile.evda.xml
JSONtoOpsMyMQ DEPLOY SendJSONtoOperationsWMQ.evda.xml
StdJSONtoFile DEPLOY StdJSONtoFile.evda.xml
StdXJSONtoFile DEPLOY StdXJSONtoFile.evda.xml
6 DISPATCH ADAPTERS MATCH FILTERS
END OF DISPLAY+
The following example shows information for the specified business event dispatch adapter.
User: ZBEVF DISPLAY DISPATCH ADAPTER CustJSONtoFile
System: BEVF0018I 11.00.11 DISPLAY OF DISPATCH ADAPTER CustJSONtoFile IN
FILE-/sys/tpf_pbfiles/tpf-fdes/CustJSONtoFile.evda.xml
STATUS: SIGNAL EVENTS ENABLED ON PROCESSOR B
DEPLOYED: YES
DISPATCH ADAPTER NAME: CustJSONtoFile _
DATA FORMAT: EVENTCUSTOM
DATA FORMAT CUSTOM PGM: QBEJ
TRANSPORT: CUSTOM
TRANSPORT CUSTOM PGM: QBEF
END OF DISPLAY+
The following example shows the information for business event dispatch adapter SendJSONtoOpsWMQ. This business event dispatch adapter uses the standard JSON format option to format event message business events as JSON documents and sends the documents to
SEND.QUEUE.TO.OPERATIONS IBM® MQ
queue.
User: ZBEVF DISPLAY DISPATCH ADAPTER SendJSONtoOpsWMQ DETAIL-YES
System: BEVF0058I 13.06.35 DISPLAY OF DISPATCH ADAPTER SendJSONtoOpsWMQ IN
FILE-...sys/tpf_pbfiles/tpf-fdes/SendJSONtoOperationsWMQ.evda.xml
STATUS: ALL EVENTS DISABLED ON PROCESSOR B
DEPLOYED: YES
DISPATCH ADAPTER NAME: SendJSONtoOpsWMQ
DESCRIPTION: Send event message business events formatted as JS
ON documents to the Websphere MQ Queue used by Ope
rations.
DATA FORMAT: JSON
TRANSPORT: WMQ
WMQ QUEUE NAME: SEND.QUEUE.TO.OPERATIONS
WMQ CHARACTER SET NAME: UTF8
END OF DISPLAY
The following example shows all business events that
use dispatch queues with a queue name that begins with the characters FLYT.
This display is sorted by dispatch queue name in the DISPATCH QUEUE NAME column, and then by event
name in the NAME column.
User: ZBEVF DISPLAY EVENT DISPQUEUE-FLYT*
System: BEVF0066I 11.03.57 DISPLAY OF BUSINESS EVENTS
FILTERS: DISPQueue-FLYT*
NAME EVTYPE STATUS DISPATCH QUEUE NAME
ArrRemXMLCust SIGNAL DEPLOY FLYT.DRIVER.REMOTE.DISPATCH.QUEUE
DelRemJSONCust SIGNAL DEPLOY FLYT.DRIVER.REMOTE.DISPATCH.QUEUE _
sendLetterRemote SIGNAL UNDEP FLYT.DRIVER.REMOTE.DISPATCH.QUEUE
ArrivalUsrEnrich SIGNAL DEPLOY FLYT.DRIVER.USER.DISPATCH.QUEUE
ArrUEnrWMQCBEFmt SIGNAL DEPLOY FLYT.DRIVER.USER.DISPATCH.QUEUE
ArrUserCBECustAd SIGNAL DEPLOY FLYT.DRIVER.USER.DISPATCH.QUEUE
CreateAdapErrors SIGNAL DEPLOY FLYT.DRIVER.USER.DISPATCH.QUEUE _
CreateFormatErrs SIGNAL DEPLOY FLYT.DRIVER.USER.DISPATCH.QUEUE
CustAdapNotInPAT SIGNAL DEPLOY FLYT.DRIVER.USER.DISPATCH.QUEUE
CustAdapReturns0 SIGNAL DEPLOY FLYT.DRIVER.USER.DISPATCH.QUEUE
CustFormNotInPAT SIGNAL DEPLOY FLYT.DRIVER.USER.DISPATCH.QUEUE
CustFormReturns0 SIGNAL DEPLOY FLYT.DRIVER.USER.DISPATCH.QUEUE _
DelUEnrCBECustAd SIGNAL DEPLOY FLYT.DRIVER.USER.DISPATCH.QUEUE
DepUEnrCBECustAd SIGNAL DEPLOY FLYT.DRIVER.USER.DISPATCH.QUEUE
DepUEnrCustCust SIGNAL DEPLOY FLYT.DRIVER.USER.DISPATCH.QUEUE
DepUEnrCustWMQAd SIGNAL DEPLOY FLYT.DRIVER.USER.DISPATCH.QUEUE
EnrichProgNotPAT SIGNAL DEPLOY FLYT.DRIVER.USER.DISPATCH.QUEUE _
SixtyFourAdapts SIGNAL UNDEP FLYT.DRIVER.USER.DISPATCH.QUEUE
UsrCustAdCBEFmt SIGNAL DEPLOY FLYT.DRIVER.USER.DISPATCH.QUEUE
UsrCustAdCustFmt SIGNAL DEPLOY FLYT.DRIVER.USER.DISPATCH.QUEUE
UsrWMQAdapCBEFmt SIGNAL DEPLOY FLYT.DRIVER.USER.DISPATCH.QUEUE
UsrWMQAdCustFmt SIGNAL DEPLOY FLYT.DRIVER.USER.DISPATCH.QUEUE _
22 BUSINESS EVENTS MATCH FILTERS
END OF DISPLAY+
The following example shows all business events that
use the system default business event dispatch queue. In this display, long file names wrap to the
next line. This display is sorted by event name in the NAME
column.
User: ZBEVF DISPLAY EVENT DISPQUEUE-IBEV.UNORDERED.DISPATCH.QUEUE
System: BEVF0061I 11.14.02 DISPLAY OF BUSINESS EVENTS
FILTERS: DISPQueue-IBEV.UNORDERED.DISPATCH.QUEUE
NAME EVTYPE STATUS FILE IN /sys/tpf_pbfiles/tpf-fdes
ArrLocEnrCBECust SIGNAL DEPLOY FLYTArrivalLocalEnrichCBECustAd.evspec.xml _
Credit_Trxns DATADF UNDEP Credit_Trxns.de.evspec.xml
DelLocCBECustAd SIGNAL DEPLOY FLYTDelayLocalNoEnrichCBECustAd.evspec.xml
DelLocCBEWMQAd SIGNAL DEPLOY FLYTDelayLocalNoEnrichCBEWMQAd.evspec.xml
DelLocEnCustCust SIGNAL DEPLOY FLYTDelayLocalEnrichCustFormCustAd.evspec.xml _
DelLocEnrCustWMQ SIGNAL DEPLOY FLYTDelayLocEnrichCustomFormatWMQAd.evspec.xml
DelLocStdCustAd SIGNAL DEPLOY FLYTDelayLocalNoEnrichStdCustAd.evspec.xml
DepartLocEnrich SIGNAL DEPLOY FLYTFlightDepartingLocalEnrichMultipleAdapters.
evspec.xml
DFTDdev DATADF DEPLOY DFTDdev_define.de.evspec.xml _
DFTDdevIRAA DATADF DEPLOY DFTDdevIRAA.de.evspec.xml
DFTDdevIRAB DATADF DEPLOY DFTDdevIRAB.de.evspec.xml
DFTDdevIRA9 DATADF DEPLOY DFTDdevIRA9.de.evspec.xml
HotelGuests DATADF UNDEP Hotel.evspec.xml
HOTR_C8E3 DATATPF UNDEP HOTR_c8e3_HT_record.de.evspec.xml _
LocCustAdCBEFmt SIGNAL DEPLOY FLYTLocalQueueCustAdapterCBEFormat.evspec.xml
LocCustAdCustFmt SIGNAL DEPLOY FLYTLocalQueueCustAdapterCustFormat.evspec.xml
LocWMQAdapCBEFmt SIGNAL DEPLOY FLYTLocalQueueWMQAdapterCBEFormat.evspec.xml
LocWMQAdCustFmt SIGNAL DEPLOY FLYTLocalQueueWMQAdapterCustomFormat.evspec.xml
_
PerfUpdate DATADF UNDEP PerfUpdate.evspec.xml
PurchaseUpdate DATADF UNDEP PurchaseUpdate.evspec.xml
QKFK_signal SIGNAL UNDEP QKFK_signal.se.evspec.xml
RECPdrvr_trxns DATATPF UNDEP RECPdriverEvents.de.evspec.xml
RockyDetails DATADF UNDEP RockyDetails.de.evspec.xml _
sendLetter SIGNAL UNDEP sendLetter.evspec.xml
TPFDEVTC1F1 DATATPF UNDEP DEB5_C1F1_A1_destination.de.evspec.xml
TPFDEVTC1F2 DATATPF UNDEP DEB5_C1F2_A2_destination.de.evspec.xml
TPFDEVTC1F3 DATATPF UNDEP DEB5_C1F3_A3_destination.de.evspec.xml _
TPFDEVTC1F4 DATATPF UNDEP DEB5_C1F4_A4_destination.de.evspec.xml
TPFDEVTE8C1 DATATPF UNDEP DEB5_E8C1_YA_destination.de.evspec.xml
TPFDEVTE8C2 DATATPF UNDEP DEB5_E8C2_YB_destination.de.evspec.xml
TPFDEVTE8F2 DATATPF UNDEP DEB5_E8F2_Y2_destination.de.evspec.xml _
TPFDEVTE8F3 DATATPF UNDEP DEB5_E8F3_Y3_destination.de.evspec.xml
TPFDEVTE8F7 DATATPF UNDEP DEB5_E8F7_Y7_destination.de.evspec.xml
TPFDEVTE8F8 DATATPF UNDEP DEB5_E8F8_Y8_destination.de.evspec.xml
34 BUSINESS EVENTS MATCH FILTERS
END OF DISPLAY+
The following example shows all business events that
use business event dispatch adapters with names that begin with
AIR. This display is sorted by dispatch adapter name in the DISPATCH ADAPTER
NAME column, and then by event name in the NAME
column.
User: ZBEVF DISPLAY EVENT DISPADAPTER-AIR*
System: BEVF0068I 11.17.46 DISPLAY OF BUSINESS EVENTS
FILTERS: DISPAdapter-AIR*
NAME EVTYPE STATUS DISPATCH ADAPTER NAME
HOTR_C8E3 DATATPF UNDEP AIRFandAIRT
TPFDEVTC1F1 DATATPF UNDEP AIRFandAIRT _
TPFDEVTC1F2 DATATPF UNDEP AIRFandAIRT
TPFDEVTC1F3 DATATPF UNDEP AIRFandAIRT
TPFDEVTC1F4 DATATPF UNDEP AIRFandAIRT
TPFDEVTE8C1 DATATPF UNDEP AIRFandAIRT
TPFDEVTE8C2 DATATPF UNDEP AIRFandAIRT
TPFDEVTE8F2 DATATPF UNDEP AIRFandAIRT
TPFDEVTE8F3 DATATPF UNDEP AIRFandAIRT _
TPFDEVTE8F7 DATATPF UNDEP AIRFandAIRT
TPFDEVTE8F8 DATATPF UNDEP AIRFandAIRT
PurchaseUpdate DATADF UNDEP AIRFandAIRT2
sendLetter SIGNAL UNDEP AIRFandAIRT2
sendLetterRemote SIGNAL UNDEP AIRFandAIRT2
14 BUSINESS EVENTS MATCH FILTERS
END OF DISPLAY+
The following example shows all business events that
use business event dispatch adapter AIRFandAIRT2. This display is sorted
by event name in the NAME column.
User: ZBEVF DISPLAY EVENT DISPADAPTER-AIRFandAIRT2
System: BEVF0061I 11.20.27 DISPLAY OF BUSINESS EVENTS
FILTERS: DISPAdapter-AIRFandAIRT2
NAME EVTYPE STATUS FILE IN /sys/tpf_pbfiles/tpf-fdes
PurchaseUpdate DATADF UNDEP PurchaseUpdate.evspec.xml _
sendLetter SIGNAL UNDEP sendLetter.evspec.xml
sendLetterRemote SIGNAL UNDEP sendLetterRemote.evspec.xml
3 BUSINESS EVENTS MATCH FILTERS
END OF DISPLAY+
The following example shows all z/TPFDF
data events. This display is sorted by event name in
the NAME column.
User: ZBEVF DISPLAY EVENT EVTYPE-DATADF
System: BEVF0061I 11.21.51 DISPLAY OF BUSINESS EVENTS
FILTERS: EVType-DATADf
NAME EVTYPE STATUS FILE IN /sys/tpf_pbfiles/tpf-fdes
Credit_Trxns DATADF UNDEP Credit_Trxns.de.evspec.xml
DFTDdev DATADF DEPLOY DFTDdev_define.de.evspec.xml _
DFTDdevIRAA DATADF DEPLOY DFTDdevIRAA.de.evspec.xml
DFTDdevIRAB DATADF DEPLOY DFTDdevIRAB.de.evspec.xml
DFTDdevIRA9 DATADF DEPLOY DFTDdevIRA9.de.evspec.xml
HotelGuests DATADF UNDEP Hotel.evspec.xml
PerfUpdate DATADF UNDEP PerfUpdate.evspec.xml _
PurchaseUpdate DATADF UNDEP PurchaseUpdate.evspec.xml
RockyDetails DATADF UNDEP RockyDetails.de.evspec.xml
9 BUSINESS EVENTS MATCH FILTERS
END OF DISPLAY+
The following example shows all z/TPF
data events. This display is sorted by event name in
the NAME column.
User: ZBEVF DISPLAY EVENT EVTYPE-DATATPF
System: BEVF0061I 11.21.51 DISPLAY OF BUSINESS EVENTS
BEVF0061I 11.23.01 DISPLAY OF BUSINESS EVENTS
FILTERS: EVType-DATATpf
NAME EVTYPE STATUS FILE IN /sys/tpf_pbfiles/tpf-fdes
HOTR_C8E3 DATATPF UNDEP HOTR_c8e3_HT_record.de.evspec.xml _
RECPdrvr_trxns DATATPF UNDEP RECPdriverEvents.de.evspec.xml
TPFDEVTC1F1 DATATPF UNDEP DEB5_C1F1_A1_destination.de.evspec.xml
TPFDEVTC1F2 DATATPF UNDEP DEB5_C1F2_A2_destination.de.evspec.xml
TPFDEVTC1F3 DATATPF UNDEP DEB5_C1F3_A3_destination.de.evspec.xml _
TPFDEVTC1F4 DATATPF UNDEP DEB5_C1F4_A4_destination.de.evspec.xml
TPFDEVTE8C1 DATATPF UNDEP DEB5_E8C1_YA_destination.de.evspec.xml
TPFDEVTE8C2 DATATPF UNDEP DEB5_E8C2_YB_destination.de.evspec.xml
TPFDEVTE8F2 DATATPF UNDEP DEB5_E8F2_Y2_destination.de.evspec.xml _
TPFDEVTE8F3 DATATPF UNDEP DEB5_E8F3_Y3_destination.de.evspec.xml
TPFDEVTE8F7 DATATPF UNDEP DEB5_E8F7_Y7_destination.de.evspec.xml
TPFDEVTE8F8 DATATPF UNDEP DEB5_E8F8_Y8_destination.de.evspec.xml
12 BUSINESS EVENTS MATCH FILTERS
END OF DISPLAY+
The following example shows all data events because the ID-* parameter
matches all z/TPF record IDs and z/TPFDF file IDs. This display is sorted by ID in the ID
column, and then by event name in the NAME column.
User: ZBEVF DISPLAY EVENT ID-*
System: BEVF0067I 11.53.24 DISPLAY OF DATA EVENTS
FILTERS: ID-*
NAME EVTYPE STATUS ID FILE IN /sys/tpf_pbfiles/tpf-fdes
oneDigitID DATADF UNDEP 0002 oneDigitID.evspec.xml
twoDigitID DATADF UNDEP 0023 twoDigitID.evspec.xml _
3dig*it(232)ID DATADF UNDEP 0232 3digitID.evspec.xml
DFTDdev DATADF DEPLOY B0A8 DFTDdev_define.de.evspec.xml
DFTDdevIRA9 DATADF DEPLOY B0A9 DFTDdevIRA9.de.evspec.xml
DFTDdevIRAA DATADF DEPLOY B0AA DFTDdevIRAA.de.evspec.xml
DFTDdevIRAB DATADF DEPLOY B0AB DFTDdevIRAB.de.evspec.xml _
Credit_Trxns DATADF UNDEP B212 Credit_Trxns.de.evspec.xml
aPurch*3 DATADF UNDEP B412 PurchaseUpdate3.evspec.xml
Purchas?Update2 DATADF UNDEP B412 PurchaseUpdate2.evspec.xml
PurchaseUpdate DATADF UNDEP B412 PurchaseUpdate.evspec.xml
HotelGuests DATADF UNDEP B431 Hotel.evspec.xml _
PerfUpdate DATADF UNDEP B491 PerfUpdate.evspec.xml
RockyDetails DATADF UNDEP B4FE RockyDetails.de.evspec.xml
TPFDEVTC1F1 DATATPF UNDEP C1F1 DEB5_C1F1_A1_destination.de.evspec.xml
TPFDEVTC1F2 DATATPF UNDEP C1F2 DEB5_C1F2_A2_destination.de.evspec.xml _
TPFDEVTC1F3 DATATPF UNDEP C1F3 DEB5_C1F3_A3_destination.de.evspec.xml
TPFDEVTC1F4 DATATPF UNDEP C1F4 DEB5_C1F4_A4_destination.de.evspec.xml
HOTR_C8E3 DATATPF UNDEP C8E3 HOTR_c8e3_HT_record.de.evspec.xml
RECPdrvr_trxns DATATPF UNDEP D1D7 RECPdriverEvents.de.evspec.xml _
TPFDEVTE8C1 DATATPF UNDEP E8C1 DEB5_E8C1_YA_destination.de.evspec.xml
TPFDEVTE8C2 DATATPF UNDEP E8C2 DEB5_E8C2_YB_destination.de.evspec.xml
TPFDEVTE8F2 DATATPF UNDEP E8F2 DEB5_E8F2_Y2_destination.de.evspec.xml
TPFDEVTE8F3 DATATPF UNDEP E8F3 DEB5_E8F3_Y3_destination.de.evspec.xml _
TPFDEVTE8F7 DATATPF UNDEP E8F7 DEB5_E8F7_Y7_destination.de.evspec.xml
TPFDEVTE8F8 DATATPF UNDEP E8F8 DEB5_E8F8_Y8_destination.de.evspec.xml
26 BUSINESS EVENTS MATCH FILTERS
END OF DISPLAY+
The following example shows all data events with
record IDs that have F in the second to last digit. Hexadecimal characters are converted to
uppercase. The FILTERS line in the display indicates the actual pattern that is used to find the
list of data events. This display is sorted by ID in
the ID column, and then by event name in the NAME
column.
User: ZBEVF DISPLAY EVENT ID-*f?
System: BEVF0067I 11.58.25 DISPLAY OF DATA EVENTS
FILTERS: ID-*F?
NAME EVTYPE STATUS ID FILE IN /sys/tpf_pbfiles/tpf-fdes
RockyDetails DATADF UNDEP B4FE RockyDetails.de.evspec.xml _
TPFDEVTC1F1 DATATPF UNDEP C1F1 DEB5_C1F1_A1_destination.de.evspec.xml
TPFDEVTC1F2 DATATPF UNDEP C1F2 DEB5_C1F2_A2_destination.de.evspec.xml
TPFDEVTC1F3 DATATPF UNDEP C1F3 DEB5_C1F3_A3_destination.de.evspec.xml
TPFDEVTC1F4 DATATPF UNDEP C1F4 DEB5_C1F4_A4_destination.de.evspec.xml _
TPFDEVTE8F2 DATATPF UNDEP E8F2 DEB5_E8F2_Y2_destination.de.evspec.xml
TPFDEVTE8F3 DATATPF UNDEP E8F3 DEB5_E8F3_Y3_destination.de.evspec.xml
TPFDEVTE8F7 DATATPF UNDEP E8F7 DEB5_E8F7_Y7_destination.de.evspec.xml
TPFDEVTE8F8 DATATPF UNDEP E8F8 DEB5_E8F8_Y8_destination.de.evspec.xml _
9 BUSINESS EVENTS MATCH FILTERS
END OF DISPLAY+
The following example shows all data events with
a record ID of 2. Leading zeros are not required when you specify the record ID. The FILTERS line in
the display shows how the record ID value is interpreted (0002). This display is sorted by event
name in the NAME column.
User: ZBEVF DISPLAY EVENT ID-2
System: BEVF0061I 11.41.09 DISPLAY OF BUSINESS EVENTS
FILTERS: ID-0002
NAME EVTYPE STATUS FILE IN /sys/tpf_pbfiles/tpf-fdes
oneDigitID DATADF UNDEP oneDigitID.evspec.xml
1 BUSINESS EVENTS MATCH FILTERS
END OF DISPLAY+
The following information is displayed in the dispatch queue display examples:
- DISPATCH QUEUE
- Specifies the name of the dispatch queue.
- TYPE
- Specifies the type of the dispatch queue.
- ECBS
- Indicates the number of dispatch ECBs that are currently processing events for each dispatch queue.
- ECBHI
- Indicates the highest number of dispatch ECBs that were processing events for each dispatch queue since the last IPL or data collection run.
- MAXECBS
- Indicates the maximum number of dispatch ECBs that can be used to process events on each dispatch queue.
Note: A hyphen in the ECBS and ECBHI columns indicates that the ZBEVF SET
command was used to set the MAXECBS value for that dispatch queue, but you did
not load an event specification that uses that dispatch queue to the z/TPF system.
The following example shows information for all business event dispatch queues on the z/TPF system.
User: ZBEVF DISPLAY DISPQUEUE-*
System: BEVF0075I 11.58.46 DISPLAY OF BUSINESS EVENT DISPATCH QUEUES
FILTERS: DISPQueue-* QType-ALL
DISPATCH QUEUE TYPE ECBS ECBHI MAXECBS
FLYT.DRIVER.REMOTE.DISPATCH.QUEUE REM N/A N/A N/A _
FLYT.DRIVER.USER.DISPATCH.QUEUE ORD 0 1 1
IBEV.UNORDERED.DEB5.A.ODD.SHARED.DQ UNO 0 1 1
IBEV.UNORDERED.DEB5.Y.ODD.SHARED.DQ UNO 0 1 1
IBEV.UNORDERED.DEB5.YA.DQ UNO 0 1 1
IBEV.UNORDERED.DISPATCH.QUEUE SYS 0 10 10 _
IBEV.UNORDERED.FLYT.DRIVER UNO 0 1 1
IBEV.UNORDERED.UF84.BIZEVENT.DQ UNO 0 1 1
IBEV.UNORDERED.UF84.FULLSUBFILE.DQ UNO 0 1 1
IBEV.UNORDERED.USER.QUEUE UNO - - 20
10 DISPATCH QUEUES MATCH FILTERS
END OF DISPLAY+
The following example shows information for all unordered business event dispatch queues on the z/TPF system.
User: ZBEVF DISP DISPQUEUE-* QTYPE-UNORDERED
System: BEVF0075I 12.02.28 DISPLAY OF BUSINESS EVENT DISPATCH QUEUES
FILTERS: DISPQueue-* QType-UNOrdered
DISPATCH QUEUE TYPE ECBS ECBHI MAXECBS
IBEV.UNORDERED.DEB5.A.ODD.SHARED.DQ UNO 0 1 1
IBEV.UNORDERED.DEB5.Y.ODD.SHARED.DQ UNO 0 1 1
IBEV.UNORDERED.DEB5.YA.DQ UNO 0 1 1
IBEV.UNORDERED.DISPATCH.QUEUE SYS 0 10 10 _
IBEV.UNORDERED.FLYT.DRIVER UNO 0 1 1
IBEV.UNORDERED.UF84.BIZEVENT.DQ UNO 0 1 1
IBEV.UNORDERED.UF84.FULLSUBFILE.DQ UNO 0 1 1
IBEV.UNORDERED.USER.QUEUE UNO - - 20
8 DISPATCH QUEUES MATCH FILTERS
END OF DISPLAY+