z/OS code module messages

Only one zDC subsystem at a time can be marked as the default. Change the parameter specification of this zDC to indicate DEFAULT(NO) and re-execute zDC.

You can also stop the zDC job with the named subsystem, which allows another subsystem to specify it as the default one. Note, that if the zDC instance with the subsystem named is unable to be cancelled or if it has been cancelled and its subsystem remains active, then you can specify DEFAULT(YES,FORCE). The existing subsystem is marked as not the default and the new one is marked as the default.

If "QUEUE"=DtAgt, in the message, review the following:

• The zDC task tries to connect to the zRemote. One of the first things it does is bootstrap the zLocal from the server using the zRemote. If the bootstrapping fails, meaning that the zLocal can't be loaded, the zDC task tries three times then issues a user abend. The fallback is that if this happens, the zDC tries to load the most recently bootstrapped zLocal. If it is the first time the zDC has been started in a new work area on the OMVS filesystem, and there is no previously downloaded zLocal, then this user abend is issued.
• Check that the zRemote code module parameter in the zDC //SYSIN is correct. This needs to point to the zRemote instance, which needs to be up and running, and connected to a server, so that the zLocal bootstrapping can happen.
• Review the zDC spool output for bootstrap messages.

If "QUEUE"=QUEUE, in the message, report this message to Dynatrace ONE product specialist by clicking the chat button in the upper-right corner of the Dynatrace menu bar.

There are 2 formats of the message followed by 4 hex words:

• {QueRt.StaWDGp Unexpected GP dispatch delay}
• {QueRt.StaWZSp Unexpected ZIIP dispatch delay}

GP is general processor delay, while ZIIP is IBM's Systems Integrated Information Processor.
The first 2 hex words are a 64bit number in STCK format with the sum of the unexpected delays.
(Convert to decimal and divide by 4096 to getmicro-seconds) The 3rd and 4th word are a count of unexpected delays and a count of how may times the delay has been evaluated. The average unexpected delay is the 64bit sum divided by the unexpected delay count.

For example: ZDC078W QueRt.StaWDGp Unexpected GP dispatch delay 00000000 F7E0822C 00000003 000019E2. xF7E0822C/x00000003=1.015sec/3=.338sec average unexpected delay base on x19E2/6,626 observations.

By default, he message will display at most once every 10 minutes. An unexpected delay defaults to .25 sec. That is, a task goes into a wait for 2 seconds and gets control back after over 2.25 seconds.

zDC parm: ZDCDISPATCHDELAYWARN(25) sets delay threshold in .01 second units e.g. 25=250 milli-sec.

zDC parm: ZDCDISPATCHDELAYRPTM(10) sets reporting interval in minutes.

Generally, use your performance tools to look for workflow delays in the 10 minute window before the warning message (for example, IBM's RMF monitor III). Also, check PARMLIB member IEAOPTxx parameter:
IIPHONORPRIORITY=NO.

NO can cause ZIIP eligible work to be delayed if GP processors are available.

The EVENT_WAIT parameter can only specify YES or NO.

If this parameter is omitted YES is assumed. An EVENT_WAIT specified as YES or allowed to default to YES indicates that when events are processed, programs are kept from continuing their execution until the event has been successfully processed by the zDC address space. In most cases this is the desirable option. If it is determined that too much time is lost while zDC is processing the event, then specify NO to this parameter. The liability is that events may be lost if zDC terminates abnormally.

The LOG_INITIAL parameter must specify either (OPEN) (CLOSED) or (). Any other values are invalid.

If you omit this parameter or specify () the default isLOG_INITIAL(CLOSED). Specify all the other parameters for logging that are applicable to your SMS environment, and also specify LOG_INITIAL(CLOSED). You can dynamically start logging using the specified parameters if the need arises. With the log in a CLOSED state no system resources are consumed.

The ARM_ELEMENT_NAME parameter specifies a 1- to 16- character name to be used by z/OS in identifying this program to the Automatic Restart Management system.

Only letters and numbers and the special characters _, $, # and @ are valid. In addition, the first byte must not be numeric.

ZDCDISPATCHDELAYRPTM specifies a minimum report interval for unexpected dispatch delay in minutes. If no exceptions occur, no warning is reported.

For example, ZDCDISPATCHDELAYRPTM(15) reports delays at most every 15 minutes.

The default is (10) =10Minutes
The minimum is (1) (not recommended, small)
The maximum is (32000) (over 533Hours)

The ZEDC_COMPRESS parameter may specify a 1- or 2-digit number representing the minimum size for a data block to be eligible for zEDC hardware assisted data compression.

Smaller blocks will be sent without compression.

A null argument may be specified to enable hardware data compression using the 8K default minimum block size.

The minimum interval is 10 (seconds).
The maximum interval is 600 (seconds).
Specify a zero value to disable metrics processing.

The minimum interval is 10 (seconds).
The maximum interval is 600 (seconds).
Specify a zero value to disable AutoDisplay processing.

The DTMSG_TRANBUFSIZE parameter specifies a Transaction buffer total size in thousands of buffers and either a 2K or 4K buffer size. The default is (1,2), which stands for 1 thousand 2K buffers. This 64-bit SMO is used to buffer messages related to a transaction before being sent to the zLocal. The minimum value is (1,2), maximum is (126,4) or (248,2) (512Megabytes).

This message indicates that the queue is filling and you should be aware that, if it reaches 100%, new messages won't be sent to the zLocal, possibly causing PurePath corruption.

This message first displays when the queue reaches 70% and re-displays at five percent increments. When utilization drops below 70%, this message no longer displays. Note that this message appears on the system console as well as in the SYSPRINT data set.

Monitor these messages carefully.

• If the {Buffer----Type}; is Trans Buffer Que, consider increasing zDC parameter: DTMSG_TRANBUFSIZE().
• If the {Buffer----Type}; is SMO Buffer Space, consider increasing zDC parameter: DTMSG_SMOSIZE().

Missing MQ Queue manager name in CICS attachment details.

User response

With the help of resp and resp2 codes, determine why INQUIRE MQCONN failed. If the problem persists, contact a Dynatrace ONE product specialist by clicking the chat button in the upper-right corner of the Dynatrace menu bar.

DTAX STATUS console command was issued. This can be used for Automated Operations to see if Dynatrace Hooks/Exits are enabled. Field descriptions:

• V.R: DT Version
• PLT-PTF: PLT PTF
• AGT-PTF: Agent PTF
• TRUE-STS: TRUE Status
• XPC-STS: XPCREQ/C Status
• RMI-STS: RMIIN/R
• ZDC-NAME: zDC Name
• AGT-ID: Agent ID