z/OS code module messages

Explanation

This informational message indicates that initialization of zDC has started or ended. The subsystem ID and the version of the product are displayed.

System action

Processing continues.

User response

None

Explanation

At zDC system startup the was an attempt to load all the processing modules into storage. This load was unsuccessful for the module named (@@) in this message.

System action

zDC terminates.

User response

Ensure that the //STEPLIB or //JOBLIB DD statements in the JCL executing zDC point to the correct data sets and that these data sets contain the correct release of zDC.

Explanation

This message follows ZDC001 and gives the module name as well as the contents of R15 and R1 at the completion of the LPAD operation.

System action

zDC terminates.

User response

Save the information in this message if you have to contact your systems programmer or Dynatrace ONE. Please contact a Dynatrace ONE product specialist by selecting the chat button in the upper-right corner of the Dynatrace menu bar.

Explanation

This message indicates that the attempt to load the module named in the message into extended common storage has failed because there is not enough available storage to hold the module.

System action

zDC terminates.

User response

Increase the amount of common storage, specifically subpool 241, and start zDC again.

Explanation

At zDC system startup there was an attempt to load all the processing modules into storage. The BLDL for this load was unsuccessful for the module named in the message.

System action

zDC terminates.

User response

Ensure that the //STEPLIB or //JOBLIB DD statements in the JCL executing zDC point to the correct data sets and that these data sets contain the correct release of zDC.

Explanation

This message follows ZDC004 and gives the module name, and the contents of R15 and R1 at the completion of the BLDL operation.

System action

zDC terminates.

User response

Save the information in this message if you have to contact your systems programmer or Dynatrace ONE. Please contact a Dynatrace ONE product specialist by selecting the chat button in the upper-right corner of the Dynatrace menu bar.

Explanation

This message indicates that the 4-character subsystem ID you specified in the //SYSIN DD parameter data set already exists in your system and it is an active zDC subsystem.

System action

zDC terminates.

User response

Ensure that the subsystem ID you have specified is unique in your system. Then restart zDC or stop the instance of zDC that holds this name.

Explanation

This message indicates that the attempt to obtain storage for the subsystem control block has failed. There is not enough storage above the line in extended CSA subpool 241 for these blocks.

System action

zDC terminates.

User response

Increase the amount of extended CSA subpool 241 storage and restart zDC.

Explanation

This message is displayed only at zDC startup. It names the columns shown below in multiple message numbers ZDC009. The module name, highest problem tracking number, the date and time the module was last assembled, the version of the module and the main storage address where it is loaded are shown.

System action

Processing continues.

User response

None

Explanation

This message lists one module loaded by zDC. See the ZDC008 message for a description of the columns.

System action

Processing continues.

User response

None

Explanation

This message is displayed on the system console by the zDC dump routines. It names the abend code.

System action

Execution terminates.

User response

Prepare the dump for examination by your systems staff or for transmission to Dynatrace ONE. Please contact a Dynatrace ONE product specialist by selecting the chat button in the upper-right corner of the Dynatrace menu bar. Re-execute zDC.

Explanation

This message is displayed on the system console by the zDC dump routines. It indicates that the attempt to obtain a system dump has failed. The return and reason code for the failure are shown in the message.

System action

Execution terminates.

User response

Examine the return and reason codes or supply this message to Dynatrace ONE. Please contact a Dynatrace ONE product specialist by selecting the chat button in the upper-right corner of the Dynatrace menu bar. Re-execute zDC.

Explanation

This message is the title for all SDUMPX macros issued by zDC. This title indicates the abend code that caused the dump to be taken.

System action

Execution terminates.

User response

Ensure that the dump is preserved and can be given to your systems programming staff or Dynatrace ONE. Please contact a Dynatrace ONE product specialist by selecting the chat button in the upper-right corner of the Dynatrace menu bar. Re-execute zDC.

Explanation

This message indicates that a non-zero return code has resulted from a VSAM zDC log request. The name of the request is contained in the message.

System action

The log task terminates but execution of zDC continues.

User response

Examine the subsequent messages, which contain detailed information about the nature of the error. Keep this information for your systems programming staff or for Dynatrace ONE. Please contact a Dynatrace ONE product specialist by selecting the chat button in the upper-right corner of the Dynatrace menu bar. Try to and re-attach and re-open the log (MVS command: Modify ZdcStcName,LOG OPEN).

Explanation

This message contains the value of the VSAM RPL feedback word following a VSAM PUT to the log data set.

System action

The log task terminates but execution of zDC continues.

User response

Examine the subsequent messages, which contain detailed information about the nature of the error. Keep this information for your systems programming staff or for Dynatrace ONE. Please contact a Dynatrace ONE product specialist by selecting the chat button in the upper-right corner of the Dynatrace menu bar. Try to re-attach and re-open the log (MVS command: Modify ZdcStcName,LOG OPEN).

Explanation

This message contains the value of the VSAM ACB error flag following a VSAM OPEN or CLOSE of the log data set.

System action

The log task terminates but execution of zDC continues.

User response

Examine the subsequent messages, which contain detailed information about the nature of the error. Keep this information for your systems programming staff or for Dynatrace ONE. Please contact a Dynatrace ONE product specialist by selecting the chat button in the upper-right corner of the Dynatrace menu bar.. Enter the ISPF zDC control system. Then re-attach and re-open the log.

Explanation

This message indicates that an abend has occurred at the displacement shown into the SRB routine named ZDCSRBRT.

System action

Execution terminates.

User response

If a dump is produced, save it for your systems staff or for transmission to Dynatrace ONE. Please contact a Dynatrace ONE product specialist by selecting the chat button in the upper-right corner of the Dynatrace menu bar. Re-execute zDC.

Explanation

This message indicates that a STORAGE OBTAIN has failed to report that extended CSA storage from subpool 241 is not available.

System action

Execution terminates.

User response

Report this condition to your systems programmer who may want to increase the amount of extended CSA storage in the system.

Explanation

This message indicates that the initialization routines have failed. It also shows the return and reason codes describing this failure.

System action

zDC execution terminates.

User response

Examine the SYSPRINT data set for any other messages that may be relevant to the failure. Please contact a Dynatrace ONE product specialist by selecting the chat button in the upper-right corner of the Dynatrace menu bar.

Explanation

This message confirms that the STOP command entered by an operator has been accepted by zDC and end of job processing has commenced.

System action

Execution terminates.

User response

None

Explanation

This message confirms that the MODIFY command entered by an operator has been received by zDC and is processing. Any errors encountered during parsing or execution of the command are indicated later.

System action

Execution continues.

User response

None

Explanation

This message contains a copy of the entire command entered by the operator in the console. Only the first 120 bytes of the command are displayed.

System action

Execution continues.

User response

None

Explanation

This message indicates that the ECB for TCPSP subtask is busy and unavailable to receive the shutdown request.

System action

Execution terminates.

User response

If a dump is produced, save it for your systems staff or for transmission to Dynatrace ONE. Please contact a Dynatrace ONE product specialist by selecting the chat button in the upper-right corner of the Dynatrace menu bar. Re-execute zDC.

Explanation

The command you just entered in the operator console was invalid and wasn't processed.

System action

The command is ignored and processing continues.

User response

Re-enter a valid command if possible. If the command was valid, refer this problem to Dynatrace ONE. Please contact a Dynatrace ONE product specialist by selecting the chat button in the upper-right corner of the Dynatrace menu bar.

Explanation

This message indicates that you have selected ARM processing and this is the first time the element named in this message has been armed. This means the execution is not due to an automatic restart.

System action

Processing continues.

User response

None

Explanation

This message indicates that this zDC has been automatically restarted by the system. The reason code indicates whether the JCL or START command has been changed (RSNCD=108) or has not been changed (RSNCD=104).

System action

Processing continues.

User response

None

Explanation

An attempt to issue IXCARM macro has resulted in a return code greater than 4. This indicates that the request did not complete. The actual return and reason codes are shown in this message.

System action

Processing continues but without ARM support.

User response

See the z/OS MVS Sysplex Services Reference for a complete list of the possible return and reason codes. Correct any environmental errors or report this problem to Dynatrace ONE. Please contact a Dynatrace ONE product specialist by selecting the chat button in the upper-right corner of the Dynatrace menu bar.

Explanation

An attempt to issue IXCARM macro has resulted in a return code greater than 4. This indicates that the request did not complete. The actual return and reason codes are shown in this message.

System action

Processing continues but without ARM support.

User response

See the z/OS MVS Sysplex Services Reference for a complete list of the possible return and reason codes. Correct any environmental errors or report this problem to a Dynatrace ONE product specialist by selecting the chat button in the upper-right corner of the Dynatrace menu bar.

Explanation

An attempt to issue IXCARM macro has resulted in a return code indicating that ARM support is not available on this system, or it may be available but stopped.

System action

Processing continues but without ARM support.

User response

See the z/OS MVS Sysplex Services Reference for a complete list of the possible return and reason codes. You may need to issue the operator command SETXCF START,POLICY,TYPE=ARM to activate ARM processing.

Explanation

This message indicates that an IXCARM has been issued in order for the server to go to a normal end of job.

System action

Processing continues.

User response

None

Explanation

This message is printed in the SYSPRINT data set and indicates that all modules named next via ZDC009I messages were loaded into ECSA.

System action

Processing continues.

User response

None

Explanation

This message is printed in the SYSPRINT data set and indicates that all modules named next via ZDC009I messages were loaded into the private area of zDC.

System action

Processing continues.

User response

None

Explanation

This informational message indicates the name and release level on which this zDC is running.

System action

Processing continues.

User response

None

Explanation

This informational message indicates the name of the LPAR on which this zDC is running and the name of the operating system on which this zDC is running.

System action

Processing continues.

User response

None

Explanation

This message indicates that during the process of establishing a new zDC subsystem on this LPAR, a previous subsystem named in the message was already active and marked as the default subsystem.

System action

zDC execution ends.

User response

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.

Explanation

This message is written to SYSPRINT indicating that the user ID you specified in TCPIP_USERID is now in control of the main task of zDC.

System action

Processing continues.

User response

None

Explanation

This message is written to SYSPRINT indicating that the action you requested in a LOG command has been successfully executed.

System action

Processing continues.

User response

None

Explanation

This message is written to SYSPRINT indicating that the USERIDunder which zDC is running does not have the necessary security access to the log data set. This access must be ACCESS(ALTER) in order that the log data set can be created and/or extended and be available.

System action

Processing continues but without the log.

User response

Either grant the user ID under which zDC is running ACCESS(ALTER) to the log data set or supply a user ID that has this access level. Note that the log data set must be defined as a generic entity in order to pass the RACROUTE used in zDC.

Explanation

This message is written to SYSPRINT indicating that the log subtask has failed to initialize.

System action

zDC processing continues but without the log.

User response

Scan the system console and the JES job log for messages relating to this problem. Look carefully for any system access (RACF, ACF/2, TOPSECRET) messages relating to the log data set.

Explanation

This message is written to SYSPRINT indicating that the queue subtask has failed to initialize.

System action

zDC terminates.

User response

Please contact a Dynatrace ONE product specialist by selecting the chat button in the upper-right corner of the Dynatrace menu bar.

Explanation

This message is written to SYSPRINT indicating that initialization of zDC has been successful.

System action

Processing continues.

User response

None

Explanation

This message is written to SYSPRINT indicating that the queue subtask has failed. Return and reason codes are contained in this message.

System action

zDC terminates.

User response

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. Please contact a Dynatrace ONE product specialist by selecting the chat button in the upper-right corner of the Dynatrace menu bar.

Explanation

This message is written to SYSPRINT indicating that the log subtask has failed. Return and reason codes are contained in this message.

System action

Processing continues but without the log.

User response

Scan the system console and the JES job log for messages relating to this problem. Look carefully for any system access (RACF, ACF/2, TOPSECRET) messages relating to the log data set.

Explanation

This message indicates that the queue is filling. New internal events are not accepted once the queue reaches 100%. This message first displays when the queue reaches 75% and it re-displays at each 5% interval. When the queue drops below 75%, this message is no longer displayed. This message appears on the system console as well as in the SYSPRINT data set.

System action

Execution continues.

User response

Please contact a Dynatrace ONE product specialist by selecting the chat button in the upper-right corner of the Dynatrace menu bar.

Explanation

This message indicates that the ZDCSDUMP module could not create a symptom record to be included in the SDUMP that it was about to write.

System action

The dump is created but without a symptom record.

User response

None

Explanation

This message indicates that the process to create an WLM enclave has not been successful. The function name is shown in the message along with the return and reason codes from execution of this function. This is a warning message only because execution of zDC continues. See below.

System action

zDC execution continues but all processing is performed in task mode and the enclave SRB is not dispatched. Hence there is no execution on any zIIP.

User response

Report this message to your systems programmer who may need to contact Dynatrace ONE. Please contact a Dynatrace ONE product specialist by selecting the chat button in the upper-right corner of the Dynatrace menu bar.

Explanation

This message indicates that the process to create an WLM enclave has been successful and zDC is a member of the enclave named in the message.

System action

Processing continues.

User response

None

Explanation

This message indicates that the process to delete an WLM enclave has not been successful. The function name is shown in the message along with the return and reason codes from execution of this function.

System action

zDC execution ends.

User response

Report this message to your systems programmer who may need to Dynatrace ONE. Please contact a Dynatrace ONE product specialist by selecting the chat button in the upper-right corner of the Dynatrace menu bar.

Explanation

This message indicates that the enclave SRB has failed to execute correctly. If the RETCODE in this message is 1C, then message ZDC077 is written next with the details concerning the failure.

System action

zDC execution ends.

User response

Report this message to your systems programmer who may need to Dynatrace ONE. Please contact a Dynatrace ONE product specialist by selecting the chat button in the upper-right corner of the Dynatrace menu bar.

Explanation

The three codes in this message correspond to the IEAMSCHD SYNCHCOMPADDR, SYNCHCODEADDR and SYNCHRSNADDR values.

System action

zDC execution ends.

User response

Report this message to your systems programmer who may need to Dynatrace ONE. Please contact a Dynatrace ONE product specialist by selecting the chat button in the upper-right corner of the Dynatrace menu bar.

Explanation

This message is written to SYSPRINT indicating that the zDC appears to be getting insufficient processor service to handle messages in a timely fashion.

System action

Processing continues.

User response

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.

Explanation

This message indicates that and internal release function didn't complete properly.

System action

Processing continues.

User response

If the issue persists, save the information in this message and contact your systems programmer or Dynatrace ONE. Please contact a Dynatrace ONE product specialist by selecting the chat button in the upper-right corner of the Dynatrace menu bar.

Explanation

This message indicates that the 4-character subsystem ID you specified in the //SYSIN DD parameter data set already exists on your system but is used by some other program that is not Dynatrace's zDC.

System action

zDC terminates.

User response

Ensure that the subsystem ID you have specified is unique on your system then restart zDC.

Explanation

This message indicates that the //SYSIN parameters specified by the customer are listed next.

System action

Processing continues.

User response

None

Explanation

This message indicates that the //SYSIN parameters specified by the customer have all been previously listed.

System action

Processing continues.

User response

None

Explanation

During the parsing of the //SYSIN DD data, the z/OS system variable substitution routine is called for each parameter. A non-zero return code resulted from one of these calls.

System action

zDC execution ends.

User response

Correct the parameter in error and re-execute zDC.

Explanation

The attempt to open the SYSIN data set failed. There is no return code associated with this error but a message may be displayed in the job log that better explains the error.

System action

zDC execution ends.

User response

Ensure that the //SYSIN DD statement exists in the JCL used to invoke zDC and ensure that it points to a data set with DCB characteristics of LRECL=80.

Explanation

Comment control characters are "/" to begin a comment and "/" to end a comment. These must be paired; one of each. All statements between this pair are treated as a comment. This message indicates that the pairing of these control sequences is not correct.

System action

zDC execution ends.

User response

Correct the comment pairing error and re-execute zDC.

Explanation

The SYSIN keyword shown in the message text is not one of the valid keywords.

System action

zDC execution ends.

User response

Correct the keyword in the SYSIN data set and re-execute zDC.

Explanation

The SUBSYSTEM_ID parameter names a unique 4-character name for this zDC instance. This name must not be duplicated on this LPAR, and must NOT be defined in the SYS1.PARMLIB IEFSSNxx member.

System action

zDC execution ends.

User response

Add the SUBSYSTEM_ID parameter to the //SYSIN data set and re-execute zDC. This 4-character name must be unique across all subsystems running on this LPAR but may be the same on different LPARs. You may name all your zDC subsystems with the same name on each LPA. But on any one LPAR this name must be unique. Do not define this name in the IEFSSNxx SYS1.PARMLIB member.

Explanation

The NAME parameter is required and must specify a name for this zDC that is meaningful to personnel in your enterprise who may see messages from this zDC. The value you specify in the NAME parameter is not used for any purpose except to uniquely identify this instance of zDC.

System action

zDC execution ends.

User response

Add the NAME parameter and re-execute zDC.

Explanation

You have specified ARM(YES) but have not specified the name to be used for Automatic Restart Management. This name must be from 1 to 16 bytes long. zDC registers with the z/OS automatic restart management and is then eligible for this facility. This name can consist of uppercase letters, numbers, and the following special characters: underscore (_), dollar sign ($), pound sign(#), or At sign (@). The first character cannot be numeric.

System action

zDC execution ends.

User response

See z/OS V1Rn.0 MVS Setting Up a Sysplex for a complete discussion of how an installation invokes this facility. When all of the steps outlined in this manual have been followed, then add the ARM_NAME parameter and re-execute zDC. In the meantime, specify ARM(NO) or omit the parameter.

Explanation

The SUBSYSTEM_ID parameter has been specified, but is not valid. The value for this parameter must be 4 bytes long consisting only of uppercase letters and numbers and dollar sign ($), pound sign(#), or At sign (@). The first character must be a letter.

System action

zDC execution ends.

User response

Correct the SUBSYSTEM_ID parameter and re-execute zDC.

Explanation

The DISPLAY_NAME parameter has been specified, but is not valid. The value for this parameter must be from 1 to 40 bytes long. Any displayable characters are valid.

System action

zDC execution ends.

User response

Correct the DISPLAY_NAME parameter and re-execute zDC.

Explanation

The DEFAULT parameter has been specified, but is not valid. Only two values are allowed: YES or NO. Only one zDC instance in a given LPAR may specify that it is the default; all others must specify NO.

System action

zDC execution ends.

User response

Correct the DEFAULT parameter and re-execute zDC.

Explanation

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.

System action

zDC execution ends.

User response

Correct the EVENT_WAIT parameter and re-execute zDC.

Explanation

The TCPIP_USERID parameter must specify a 1- to 8-character valid user ID. You may omit this parameter in which case the user ID under which zDC was submitted is used.

System action

zDC execution ends.

User response

Either correct the user ID parameter or omit it entirely. Re-execute zDC.

Explanation

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

If you omit this parameter or specify () the default is LOG_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.

System action

zDC execution ends.

User response

Correct the LOG_INITIAL parameter and re-execute zDC.

Explanation

The LOG_DSNAME parameter must specify a 1 to 35- character data set name for the optional logging. Be sure you haven't specified more than 35 characters because IDCAMS appends a .DATA and a .INDEX to this name when the cluster is defined.

System action

zDC execution ends.

User response

Correct the LOG_DSNAME and re-execute zDC.

Explanation

The LOG_VOLSER parameter must specify a 6-character volume serial number for the volume on which the log is to be defined. You must specify this parameter only if your SMS environment dictates it, else you may omit this parameter and take your system defaults.

System action

zDC execution ends.

User response

Correct the LOG_VOLSER and re-execute zDC.

Explanation

The LOG_TRKS parameter must specify a 1 to 8-digit number representing the number of tracks you want defined in the primary and secondary extents of the log data set. The maximum value for this parameter is 65535 and the minimum value is 1.

System action

zDC execution ends.

User response

Correct the LOG_TRKS and re-execute zDC.

Explanation

The LOG_CYLS parameter must specify a 1 to 8-digit number representing the number of cylinders you want defined in the primary and secondary extents of the log data set. The maximum value for this parameter is 65535 and the minimum value is 1.

System action

zDC execution ends.

User response

Correct the LOG_CYLS and re-execute zDC.

Explanation

The LOG_MGMTCLASS parameter must specify a 1- to 8-character name for the management class SMS parameter that is defined in your installation for the log data set.

System action

zDC execution ends.

User response

Correct the LOG_MGMTCLASS parameter and re-execute zDC.

Explanation

The LOG_DATACLASS parameter must specify a 1- to 8-character name for the data class SMS parameter that is defined in your installation for the log data set.

System action

zDC execution ends.

User response

Correct the LOG_DATACLASS parameter and re-execute zDC.

Explanation

The LOG_STORCLASS parameter must specify a 1- to 8-character name for the storage class SMS parameter that is defined in your installation for the log data set.

System action

zDC execution ends.

User response

Correct the LOG_STORCLASS parameter and re-execute zDC.

Explanation

The ARM parameter must specify either ARM(YES), if you want Automatic Restart Management to restart this zDC in case of abnormal termination, or ARM(NO), if you do not want the zDC restarted. Initially you should specify ARM(NO) until you have assured yourself that the zDC is working correctly under normal circumstances. When this is the case you can request ARM support.

System action

zDC execution ends.

User response

Correct the ARM parameter and re-execute zDC

Explanation

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.

System action

zDC execution ends.

User response

Correct the ARM_ELEMENT_NAME parameter and re-execute zDC.

Explanation

The PROTECT parameter must specify PROTECT(YES) if pages in extended common storage are to be protected from inadvertent alteration by other programs running in the LPAR or PROTECT(NO) if this protection is not to occur. If this parameter is omitted then no protection exists. Any program running in key 0 can alter this storage.

System action

zDC execution ends.

User response

Correct the PROTECT parameter and re-execute zDC.

Explanation

The DEFAULT parameter is required as either DEFAULT(YES) or DEFAULT(NO). Only one zDC subsystem in the LPAR can specify DEFAULT(YES). All others must specify DEFAULT(NO).

System action

zDC execution ends.

User response

Add the DEFAULT parameter and re-execute zDC.

Explanation

The OPERATING_SYSTEM parameter should never be specified at a customer parameter. Its use is only for emulating releases of z/OS earlier than the current one.

System action

zDC ends.

User response

Remove this parameter from the SYSIN data set.

Explanation

The zIIP_ENABLE parameter can specify YES or NO. If zIIP_ENABLE(YES) is specified, then the SRB under which all XML creation and TCP/IP SOCKET(SEND) routines run is zIIP enabled. This SRB is not run on your zIIP if set to NO.

System action

zDC execution ends.

User response

Correct the zIIP_ENABLE parameter and resubmit zDC.

Explanation

The DTMSG_QSIZE parameter specifies a Data Space size in Kilobyte. The default is 1024 (1024K). This Data Space used to queue messages from the CICS code module of OneAgent to the zLocal. The minimum value is 8 and the maximum is 262144K (256Megabytes).

System action

zDC execution ends.

User response

Specify a value in the range given.

Explanation

The DTMSG_SMOSIZE parameter specifies a 64-bit SMO size in MB. The default is 1 MB. This 64-bit SMO is used to queue messages from the CICS code module to the zLocal. The minimum value is 1 and the maximum is 256 MB. (256Megabytes).

System action

zDC execution ends.

User response

Choose a correct value for SMOSIZE and then resubmit zDC.

Explanation

The DT_UMASK parameter specifies user file-creation mask. The default is 0022(octal) and corresponds to rwxr-xr-x permission for new files. Error is generated if the parameter is over 3 characters, or contain non-octal characters (o:7).

System action

zDC execution ends.

User response

Choose a correct value for DT_UMASK and then resubmit zDC.

Explanation

The DTMSG_TBCSIZE parameter specifies a 64-bit Transaction buffer total size in MB and either a 2K or 4K buffer size. The default is (1,2), which stands for 1MB and 2K buffer. This 64-bit SMO is used to buffer messages related to a transaction before being sent to OneAgent. The minimum value is 1 and the maximum is 256 MB (256Megabytes).

System action

zDC execution ends.

User response

Choose a correct value for TBCSIZE and then resubmit zDC.

Explanation

The DTMSG_QSIZE parameter specified DataSpace size in Kilobytes It is replace by DTMSG_SMOSIZE(Megabytes) The parameter has been converted to Megabytes and used to set the SMO size.

System action

zDC execution continues.

User response

Use DTMSG_SMOSIZE in the future.

Explanation

ZDCLOGBUFFERSIZE specifies a log buffer in kilobytes. It is a SMO memory are areas to buffer the zDC .log file. The zDC .log file in the same directory as the ZLocal code module .log files. The default is (64) - 64K. The minimum is 16K, the maximum is 10240K =10M.

System action

zDC execution ends.

User response

Correct value for ZDCLOGBUFFERSIZE and resubmit.

Explanation

ZDCMAXLOGFILESIZE specifies the log file size limit. It is used to rotate to a new log file when exceeded. The ZDClogfile pattern: .._ZDCID_PID_.#.log, for example: dt_DTV1ZDC4_MEPC_33620088.1.log. The default is (10240) =10M. The minimum is 10K; the maximum is 1048576K =1G.

System action

zDC execution ends.

User response

Correct value for ZDCMAXLOGFILESIZE and resubmit.

Explanation

ZDCDISPATCHDELAYWARN specifies an unexpected dispatch delay threshold in units of .01sec. For example, ZDCDISPATCHDELAYWARN(100) specifies 1sec. The default is (25) =.25sec. The minimum non-zero valuse is 10 =.1sec. The maximum is (32000) =320sec. Disable delay checking: ZDCDISPATCHDELAYWARN(0)

System action

zDC execution ends.

User response

Correct value for ZDCDISPATCHDELAYWARN and resubmit.

Explanation

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)

System action

zDC execution ends.

User response

Correct value for ZDCDISPATCHDELAYRPTM and resubmit.

Explanation

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.

System action

zDC execution ends.

User response

Correct the ZEDC_COMPRESS parameter and re-execute the zDC.

Explanation

The TCP_BUFFER parameter specifies a 1- to 4-digit number representing the size of the buffer that is used to pass OneAgent data to TCP/IP.

System action

zDC execution ends.

User response

Correct the TCP_BUFFER parameter and re-execute the zDC.

Explanation

The minimum compression threshold must be smaller than the size of the TCP/IP buffer.

System action

zDC execution ends.

User response

Correct one of the parameters and re-execute the zDC.

Explanation

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

System action

Processing continues.

User response

Correct the parameter and re-execute the zDC.

Explanation

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

System action

Processing continues.

User response

Correct the parameter and re-execute the zDC.

Explanation

This informational message indicates that the TERMAPI macro was successfully executed to terminate TCP/IP communications.

System action

Processing continues.

User response

None

Explanation

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).

System action

zDC execution ends.

User response

Choose a correct value for DTMSG_TRANBUFSIZE and resubmit.

Explanation

A zRemote code module parameter is required. The zRemote code module properties such as host and port are not specified in the DTAGTCMD parameter.

System action

zDC is terminated.

User response

Add zremoteagent= to DTAGTCMD resubmit zDC.

Explanation

The TCP_BUFFER parameter must be in range from 8k to 256k. If less than 8k is specified, 8k is used. If more than 256k is specified, 256k is used.

System action

Processing continues.

User response

Correct the TCP_BUFFER parameter for next ZDC execution.

Explanation

This informational message indicates that termination processing has started for this zDC.

System action

Termination processing continues.

User response

None

Explanation

This informational message is followed by messages that show the number of bytes of storage allocated in each of the designated areas. These numbers may only be approximate as dynamic storage areas are not included in them.

System action

Processing continues.

User response

None

Explanation

The number of bytes of private zDC storage that is allocated long term is shown in this message. This number may only be approximate as dynamic storage areas are not included. Storage allocated both over and under the 16M line are included in this number.

System action

Processing continues.

User response

None

Explanation

The number of bytes of subpool 241 (pageable common) storage that has been allocated for the duration of zDC execution.

System action

Processing continues.

User response

None

Explanation

The number of bytes of subpool 245 (fixed common) storage that has been allocated for the duration of zDC execution.

System action

Processing continues.

User response

None

Explanation

The number of pages in subpool 241 that have had the PGSER PROTECT macro issued against them. This message displays only if you have specified PROTECT(YES) in the SYSIN parameter data set.

System action

Processing continues.

User response

None

Explanation

Validation routines invoked to ensure that each message to the zLocal is valid has detected an error in the data.

System action

If logging is active, the event is logged. This message is written to the user's JOBLOG and the event is discarded.

User response

Please contact a Dynatrace ONE product specialist by selecting the chat button in the upper-right corner of the Dynatrace menu bar.

Explanation

Generally, these are internal diagnostic messages issued when the DTLOGLEVEL 2 or less (fine). They may be requested by Dynatrace software support to diagnose an issue.

System action

Processing continues.

User response

None

Explanation

The parameters DTPIPEPATH, DTCHDIR, DTAGTCMD, or DTLOG are invalid. See comments in the supplied sample config member for a description of these parameters.

System action

zDC execution ends.

User response

Correct the parameter and re-execute zDC.

Explanation

There is a limit on how frequently the internal tables that contain CICS properties can be updated. The current limit is 30 seconds.

System action

Informational, processing continues.

User response

Re-apply the update later.

Explanation

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 distribute trace 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.

System action

Execution continues.

User response

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().

Explanation

ZIIP enablement requires remote agent option.

System action

Informational, processing continues.

User response

ZIIP enablement requires both the zremoteagent= in the DTABGCMT command line and ZIIP_ENABLE(YES) in the zDC SYSIN parameters.

Explanation

Dynatrace parameter SYSLOG is invalid. Only CONNECTSTATUS or () to disable the option are allowed.

System action

Informational, processing continues.

User response

Remove the parameter or code allowed values.

Explanation

zLocal code module has connected though the zRemote code module to the Dynatrace server.

System action

Informational, processing continues.

User response

None

Explanation

zLocal code module has disconnected from the Dynatrace server.

System action

Informational, processing continues.

User response

If this is not planned, investigate the outage.

Explanation

Ignore if expected, otherwise check Settings > Server-side service monitoring > Deep monitoring > Troubleshooting.

System action

Informational, processing continues.

User response

None

Explanation

ZDC has completed sending INIT msg and received an AgentId response.

System action

Informational, processing continues.

User response

None

Explanation

ZDC could not find the V4 IP address in the SMO. Verify your zLocal is current.

System action

Informational, processing continues.

User response

Confirm zLocal verion is current.

Explanation

This message is written to the SYSPRINT and Oper. Check that the agent file exists and is executable. See DTAGTCMD() parameter.

System action

Processing terminates.

User response

Check job log for additional error messages, correct them if possible. If still unresolved, refer this problem to Dynatrace ONE. Please contact a Dynatrace ONE product specialist by selecting the chat button in the upper-right corner of the Dynatrace menu bar.

Explanation

This message is written to the SYSPRINT and Oper. Check that the DTAGTCMD parameter references an accessible and executable OneAgent.

System action

Processing terminates.

User response

Check job log for additional error messages, correct them if possible. If still unresolved, refer this problem to Dynatrace ONE. Please contact a Dynatrace ONE product specialist by selecting the chat button in the upper-right corner of the Dynatrace menu bar.

Explanation

This message is written to the SYSPRINT and Oper. Check that the zDC has read+write access to the DTCHDIR directory.

System action

Processing terminates.

User response

Check job log for additional error messages, correct them if possible. If still unresolved, refer this problem to Dynatrace ONE. Please contact a Dynatrace ONE product specialist by selecting the chat button in the upper-right corner of the Dynatrace menu bar.

Explanation

This message is written to the SYSPRINT and Oper. Check that the user ID that is running the zDC is defined to the security product. The userid is either the normally assigned ID, or overriden by the TCPIP_USERID parameter.

System action

Processing terminates.

User response

Check job log for additional error messages, correct them if possible. If still unresolved, refer this problem to Dynatrace ONE product specialist by clicking the chat button in the upper-right corner of the Dynatrace menu bar.

Explanation

This message is written to the SYSPRINT and Oper. The MVS Name/Token is used for internal processing. The operation failed.

System action

Processing terminates with a dump.

User response

Check job log for additional error messages, correct them if possible. If still unresolved, refer this problem to Dynatrace ONE. Please contact a Dynatrace ONE product specialist by selecting the chat button in the upper-right corner of the Dynatrace menu bar.

Explanation

This message is written to the SYSPRINT and Oper. The Data Space used to pass messages to the ZDC has not initialized.

System action

Processing terminates with a dump.

User response

Check job log for additional error messages, correct them if possible. If still unresolved, refer this problem to Dynatrace ONE product specialist by clicking the chat button in the upper-right corner of the Dynatrace menu bar.

Explanation

This message is written to the SYSPRINT and Oper. The OMVS kernel is not ready.

System action

Processing terminates with a dump.

User response

Check why the OMVS address space is not operational. Restart OMVS or delay zDC startup until OMVS is ready.

Explanation

This message is written to the SYSPRINT and Oper. A critical Data Space process has failed.

System action

Processing terminates with a dump.

User response

Check job log for additional error messages, correct them if possible. If still unresolved, refer this problem to Dynatrace ONE. Please contact a Dynatrace ONE product specialist by selecting the chat button in the upper-right corner of the Dynatrace menu bar.

Explanation

This message is written to the SYSPRINT and Oper. A critical Data Space process has failed.

System action

Processing terminates with a dump.

User response

Check job log for additional error messages, correct them if possible. If still unresolved, refer this problem to Dynatrace ONE. Please contact a Dynatrace ONE product specialist by selecting the chat button in the upper-right corner of the Dynatrace menu bar.

Explanation

This message is written to the SYSPRINT and Oper. A critical timer wait function has failed.

System action

Processing terminates with a dump.

User response

Check job log for additional error messages, correct them if possible. If still unresolved, refer this problem to Dynatrace ONE. Please contact a Dynatrace ONE product specialist by selecting the chat button in the upper-right corner of the Dynatrace menu bar.

Explanation

This message is written to the SYSPRINT and Oper. A Unix wait to check zLocal status has failed.

System action

Processing terminates with a dump.

User response

Check job log for additional error messages, correct them if possible. If still unresolved, refer this problem to Dynatrace ONE. Please contact a Dynatrace ONE product specialist by selecting the chat button in the upper-right corner of the Dynatrace menu bar.

Explanation

This message is written to the SYSPRINT and Oper. A Unix poll for zLocal messages has failed.

System action

Processing terminates with a dump.

User response

Check job log for additional error messages, correct them if possible. If still unresolved, refer this problem to Dynatrace ONE. Please contact a Dynatrace ONE product specialist by selecting the chat button in the upper-right corner of the Dynatrace menu bar.

Explanation

This message is written to the SYSPRINT and Oper. A Unix unnamed pipe is needed for zLocal communication.

System action

Processing terminates with a dump.

User response

Check job log for additional error messages, correct them if possible. If still unresolved, refer this problem to Dynatrace ONE. Please contact a Dynatrace ONE product specialist by selecting the chat button in the upper-right corner of the Dynatrace menu bar.

Explanation

This message is written to the SYSPRINT and Oper. A critial internal call function has failed.

System action

Processing terminates with a dump.

User response

Check job log for additional error messages, correct them if possible. If still unresolved, refer this problem to Dynatrace ONE. Please contact a Dynatrace ONE product specialist by selecting the chat button in the upper-right corner of the Dynatrace menu bar.

Explanation

This message is written to the SYSPRINT and Oper. A critial internal call function has failed.

System action

Processing terminates with a dump.

User response

Check job log for additional error messages, correct them if possible. If still unresolved, refer this problem to Dynatrace ONE. Please contact a Dynatrace ONE product specialist by selecting the chat button in the upper-right corner of the Dynatrace menu bar.

Explanation

This message is written to the SYSPRINT and Oper. It is intended for internal diagnostic for Dynatrace loglevel:finer(1).

System action

Informational, processing continues.

User response

Informational, processing continues.

Explanation

This message is written to the SYSPRINT. It is intended for internal diagnostic for loglevel:finest(0).

System action

Informational, processing continues.

User response

Informational, processing continues.

Explanation

This message is written to the SYSPRINT. It is intended for internal Dynatrace diagnostic for Dynatrace loglevel:finer(1).

System action

Informational, processing continues.

User response

Informational, processing continues.

Explanation

This message is written to the SYSPRINT. It is intended for internal Dynatrace diagnostic for Dynatrace loglevel:fine(2).

System action

Informational, processing continues.

User response

Informational, processing continues.

Explanation

This message is written to the SYSPRINT. It is intended for internal Dynatrace diagnostic for Dynatrace loglevel:config(3).

System action

Informational, processing continues.

User response

Informational, processing continues.

Explanation

This message is written to the SYSPRINT. It is intended for internal Dynatrace diagnostic for Dynatrace loglevel:info(4)

System action

Informational, processing continues.

User response

Informational, processing continues.

Explanation

This message is written to the SYSPRINT. It is intended for internal Dynatrace diagnostic for Dynatrace loglevel:warn(5).

System action

Informational, processing continues.

User response

If a connection issue, investigate the status of the zRemote code module. Otherwise, informational, processing continues.

Explanation

This message is written to the SYSPRINT. It is intended for internal Dynatrace diagnostic for Dynatrace loglevel:severe(6).

System action

Informational, processing continues.

User response

Informational, processing continues.

Explanation

This message is written to the SYSPRINT. It is intended for internal Dynatrace diagnostic for Dynatrace loglevel:debug(7).

System action

Informational, processing continues.

User response

Informational, processing continues.

Explanation

This message is written to the SYSPRINT. It is intended for internal Dynatrace. Dynatrace ONE product specialist may ask that system parameters be changed to cause these messages.

System action

Informational, processing continues.

User response

Informational, processing continues.

Explanation

This message is written to the SYSPRINT. It is intended for internal Dynatrace diagnostic and shouldn't appear under normal operation. Dynatrace ONE product specialist may ask that system parameters be changed to cause these messages.

System action

Informational, processing continues.

User response

Informational, processing continues.

Explanation

The CICS PLT program was unable to allocate a required persistent storage area.

System action

The PLT program terminates and the CICS code module is not enabled.

User response

Determine why the CICS region is unable to provide storage for the DTAX transaction. If the problem persists Please contact a Dynatrace ONE product specialist by selecting the chat button in the upper-right corner of the Dynatrace menu bar.

Explanation

The PLT program was unable to allocate a required Message block storage area.

System action

The PLT program terminates and the CICS code module is disabled.

User response

Determine why the CICS region is unable to provide storage for the PLT program.

Explanation

CICS could not load ZDTSOAPH.

System action

The PLT program terminates and the CICS code module is disabled.

User response

Determine why the CICS region is unable to provide storage for the DTAX transaction. If the problem persists Please contact a Dynatrace ONE product specialist by selecting the chat button in the upper-right corner of the Dynatrace menu bar.

Explanation

Message transfer from CICS code module to zDC has failed.

System action

CICS code module operation continues but with missing nodes in the distributed trace.

User response

Please contact a Dynatrace ONE product specialist by selecting the chat button in the upper-right corner of the Dynatrace menu bar.

Explanation

The EXEC CICS START command used to initiate the DTAX ICE transaction in 5 minutes interval has failed.

System action

None

User response

Examine the more detailed message in the appropriate CICS job log to look at the precise EIBRESP code that indicates why this EXEC CICS START command failed. If the problem persists, Please contact a Dynatrace ONE product specialist by selecting the chat button in the upper-right corner of the Dynatrace menu bar.

Explanation

EXEC CICS INQUIRE for MQ Connection information has failed.

System action

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, Please contact a Dynatrace ONE product specialist by selecting the chat button in the upper-right corner of the Dynatrace menu bar.

Explanation

Indicates that the Language Environment sensor could not be enabled because zDC is unavailable.

System action

Language Environment sensor is not enabled. CICS code module doesn't monitor LE dynamic calls.

User response

Start the zDC for CICS code module to reconnect.

Explanation

Storage allocation for PLT work area failed.

System action

The PLT program terminates and the CICS code module is disabled.

User response

Determine why the CICS region is unable to provide storage for the PLT program.

Explanation

Persistent storage for PLT program is not found.

System action

The PLT program terminates and the CICS code module is disabled.

User response

Please contact a Dynatrace ONE product specialist by selecting the chat button in the upper-right corner of the Dynatrace menu bar.

Explanation

RMI hook initialization failed.

System action

CICS code module not initialized successfully.

User response

Please contact a Dynatrace ONE product specialist by selecting the chat button in the upper-right corner of the Dynatrace menu bar.

Explanation

Disabling RMI hook failed.

System action

CICS code module not disabled successfully.

User response

Please contact a Dynatrace ONE product specialist by selecting the chat button in the upper-right corner of the Dynatrace menu bar.

Explanation

Global work area storage for PLT program is unavailable.

System action

Hooks don't initialize successfully.

User response

Please contact a Dynatrace ONE product specialist by selecting the chat button in the upper-right corner of the Dynatrace menu bar.

Explanation

SOAP hook enable/disable has failed.

System action

Hook operation fails.

User response

Please contact a Dynatrace ONE product specialist by selecting the chat button in the upper-right corner of the Dynatrace menu bar.

Explanation

Language Environment sensor enable/disable has failed.

System action

Hook operation fails.

User response

Please contact a Dynatrace ONE product specialist by selecting the chat button in the upper-right corner of the Dynatrace menu bar.

Explanation

MRO hook enable/disable has failed.

System action

Hook operation fails.

User response

Please contact a Dynatrace ONE product specialist by selecting the chat button in the upper-right corner of the Dynatrace menu bar.

Explanation

Hook operation has failed.

System action

CICS code module don't initialize successfully.

User response

Please contact a Dynatrace ONE product specialist by selecting the chat button in the upper-right corner of the Dynatrace menu bar.

Explanation

The PLT program is unable to connect to the collection system.

System action

Execution continues. The PLT program tries to re-connect with the collection system during the next 5 minutes window.

User response

Check if the zRemote code module is up and running and connected to Dynatrace. If not, start the service that is down. If the problem persists, Please contact a Dynatrace ONE product specialist by selecting the chat button in the upper-right corner of the Dynatrace menu bar.

Explanation

Storage allocation for config block has failed.

System action

CICS code module doesn't initialize successfully.

User response

Determine why the CICS region is unable to provide storage for the DTAX transaction.

Explanation

Storage allocation for message buffer has failed.

System action

CICS code module doesn't initialize successfully.

User response

Determine why the CICS region is unable to provide storage for the DTAX transaction.

Explanation

EXEC CICS ASSIGN for APPLID retrieval has failed.

System action

CICS Applid is not displayed in DTAX screen and in log messages.

User response

Determine the cause of the problem from resp and resp2 codes.

Explanation

EXEC CICS ASSIGN for program start code retrieval has failed.

System action

CICS code module doesn't initialize successfully.

User response

Determine the cause of the problem from resp and resp2 codes.

Explanation

EXEC CICS DELAY has failed.

System action

None

User response

Determine the cause of the problem from resp and resp2 codes.

Explanation

EXEC CICS INQUIRE DB2ENTRY has failed.

System action

CICS code module operation continues.

User response

Determine the cause of the problem from resp and resp2 codes. If the problem persists, Please contact a Dynatrace ONE product specialist by selecting the chat button in the upper-right corner of the Dynatrace menu bar.

Explanation

CICS code module didn't get a valid AgentId after initialization.

System action

CICS code module is disabled.

User response

Check for error messages in zRemote log. If the zRemote service is not running, start it.

Explanation

EXEC CICS INQUIRE SYSTEM for CICS version retrieval has failed.

System action

By default CICS code module for CICS Version 4.2 is loaded.

User response

Determine the cause of the problem from resp and resp2 codes. If the problem persists, Please contact a Dynatrace ONE product specialist by selecting the chat button in the upper-right corner of the Dynatrace menu bar.

Explanation

EXEC CICS INQUIRE PROGRAM has failed.

System action

CICS code module operation continues.

User response

Determine the cause of the problem from resp and resp2 codes. If the problem persists, Please contact a Dynatrace ONE product specialist by selecting the chat button in the upper-right corner of the Dynatrace menu bar.

Explanation

EXEC CICS DISABLE PROGRAM for all exits has failed.

System action

CICS code module is not disabled successfully.

User response

Determine the cause of the problem from resp and resp2 codes. If the problem persists, Please contact a Dynatrace ONE product specialist by selecting the chat button in the upper-right corner of the Dynatrace menu bar.

Explanation

EXEC CICS DISABLE PROGRAM for RMI exit has failed.

System action

RMI exit is not disabled successfully.

User response

Determine the cause of the problem from resp and resp2 codes. If the problem persists, Please contact a Dynatrace ONE product specialist by selecting the chat button in the upper-right corner of the Dynatrace menu bar.

Explanation

EXEC CICS ENABLE START for XPCREQC/XRMIIN/XRMIOUT exit has failed.

System action

Exits are not started successfully.

User response

Determine the cause of the problem from resp and resp2 codes. If the problem persists, Please contact a Dynatrace ONE product specialist by selecting the chat button in the upper-right corner of the Dynatrace menu bar.

Explanation

EXEC CICS FREEMAIN has failed.

System action

Global Work Area for PLT program FREEMAIN fails.

User response

Determine the cause of the problem from resp and resp2 codes. If the problem persists, Please contact a Dynatrace ONE product specialist by selecting the chat button in the upper-right corner of the Dynatrace menu bar.

Explanation

EXEC CICS ENABLE PROGRAM for enabling exits failed.

System action

CICS code module exits are not enabled successfully.

User response

Determine the cause of the problem from resp and resp2 codes. If the problem persists, Please contact a Dynatrace ONE product specialist by selecting the chat button in the upper-right corner of the Dynatrace menu bar.

Explanation

EXEC CICS DISABLE stop for exits failed.

System action

CICS code module exits are not stopped successfully.

User response

Determine the cause of the problem from resp and resp2 codes. If the problem persists, Please contact a Dynatrace ONE product specialist by selecting the chat button in the upper-right corner of the Dynatrace menu bar.

Explanation

EXEC CICS CANCEL REQID has failed.

System action

DTAX ICE transaction is not cancelled.

User response

Determine the cause of the problem from resp and resp2 codes. If the problem persists, Please contact a Dynatrace ONE product specialist by selecting the chat button in the upper-right corner of the Dynatrace menu bar.

Explanation

EXEC CICS INQUIRE REQID has failed.

System action

DTAX ICE transaction is not started successfully.

User response

Determine the cause of the problem from resp and resp2 codes. If the problem persists, Please contact a Dynatrace ONE product specialist by selecting the chat button in the upper-right corner of the Dynatrace menu bar.

Explanation

EXEC CICS GETMAIN for Global Work Area has failed.

System action

Global Work Area for PLT program is not allocated. CICS code module doesn't initialize successfully.

User response

Determine the cause of the problem from resp and resp2 codes. If the problem persists, Please contact a Dynatrace ONE product specialist by selecting the chat button in the upper-right corner of the Dynatrace menu bar.

Explanation

EXEC CICS START has failed.

System action

DTAX Interval control transaction is not started every 5 minutes.

User response

Determine the cause of the problem from resp and resp2 codes. If the problem persists, Please contact a Dynatrace ONE product specialist by selecting the chat button in the upper-right corner of the Dynatrace menu bar.

Explanation

EXEC CICS LOAD PROGRAM for ZDTAGTxx module has failed.

System action

ZDTAGTxx PTF and build date is not printed in the log messages.

User response

Determine the cause of the problem from resp and resp2 codes. If the problem persists, Please contact a Dynatrace ONE product specialist by selecting the chat button in the upper-right corner of the Dynatrace menu bar.

Explanation

EXEC CICS LOAD PROGRAM for ZDTSOAPH module has failed.

System action

ZDTSOAPH build date and version information are not printed in the log messages.

User response

Determine the cause of the problem from resp and resp2 codes. If the problem persists, Please contact a Dynatrace ONE product specialist by selecting the chat button in the upper-right corner of the Dynatrace menu bar.

Explanation

EXEC CICS RELEASE PROGRAM for ZDTAGTxx/ZDTSOAPH module has failed.

System action

CICS code module operation continues.

User response

Determine the cause of the problem from resp and resp2 codes. If the problem persists, Please contact a Dynatrace ONE product specialist by selecting the chat button in the upper-right corner of the Dynatrace menu bar.

Explanation

EXEC CICS RECEIVE DATA has failed.

System action

User command for DTAX transaction is not received and hence is not processed successfully.

User response

Determine the cause of the problem from resp and resp2 codes. If the problem persists, Please contact a Dynatrace ONE product specialist by selecting the chat button in the upper-right corner of the Dynatrace menu bar.

Explanation

Error retrieving zOS SMFid.

System action

CICS code module doesn't initialize.

User response

Please contact a Dynatrace ONE product specialist by selecting the chat button in the upper-right corner of the Dynatrace menu bar.

Explanation

CICS code module initialization has failed.

System action

CICS code module doesn't initialize.

User response

Please contact a Dynatrace ONE product specialist by selecting the chat button in the upper-right corner of the Dynatrace menu bar.

Explanation

EXEC CICS INQUIRE DB2CONN retreives an AUTHTYPE that is not one of GROUP, TERM, TX, OPID, USERID.

System action

Authtype not specified in DB2 attachment data in distributed trace.

User response

Contact your DB2 administrator.

Explanation

Sending DB2 connection pool information from CICS code module to zDC has failed.

System action

DB2 attachment details in distributed trace is empty.

User response

Please contact a Dynatrace ONE product specialist by selecting the chat button in the upper-right corner of the Dynatrace menu bar.

Explanation

Sending DL1 connection pool information from CICS code module to zDC has failed.

System action

DLI attachment details in distributed trace is empty.

User response

Please contact a Dynatrace ONE product specialist by selecting the chat button in the upper-right corner of the Dynatrace menu bar.

Explanation

CICS code module could not send message to zDC.

System action

No data passes from CICS to zDC.

User response

Please contact a Dynatrace ONE product specialist by selecting the chat button in the upper-right corner of the Dynatrace menu bar.

Explanation

The RDO definition for DTAX transaction is not found.

System action

CICS code module not enabled and the PLT program execution terminates.

User response

Define DTAX transaction for the PLT program. Refer to CICRDO member in SZDTSAMP installation library for sample definition.

Explanation

CICS code module could not find the configuration data with sensor settings.

System action

CICS code module doesn't initialize.

User response

Please contact a Dynatrace ONE product specialist by selecting the chat button in the upper-right corner of the Dynatrace menu bar.

Explanation

CICS code module could not find the config block with CICS sensor settings.

System action

CICS code module is disabled.

User response

Check if the CICS Transaction Server sensor is placed in the CICS code module Mapping.

Explanation

Couldn't enable CICS code module.

System action

CICS code module doesn't initialize successfully.

User response

Please contact a Dynatrace ONE product specialist by selecting the chat button in the upper-right corner of the Dynatrace menu bar.

Explanation

Could not find the Copyright block in ZDTAGTxx module.

System action

CICS code module continues. No PTF/Build date is printed in the zRemote log.

User response

Please contact a Dynatrace ONE product specialist by selecting the chat button in the upper-right corner of the Dynatrace menu bar.

Explanation

Configuration block with the CICS sensor information is not found.

System action

CICS code module is disabled.

User response

Check if the CICS transaction server sensor is placed in the CICS code module mapping.

Explanation

This message is an extention of ZDTP052S.

System action

CICS code module is disabled.

User response

Follow ZDTP052S.

Explanation

Couldn't enable Trace hook.

System action

Trace hook is not installed.

User response

Look in CICS log for problems. If nothing, Please contact a Dynatrace ONE product specialist by selecting the chat button in the upper-right corner of the Dynatrace menu bar.

Explanation

Couldn't disable trace hook.

System action

Trace hook is not installed.

User response

Look in CICS log for problems. If nothing, Please contact a Dynatrace ONE product specialist by selecting the chat button in the upper-right corner of the Dynatrace menu bar.

Explanation

Bad address for DSA storage

System action

Dynatrace hooks are not enabled.

User response

CICS getmain failed. Check CICS logs and correct problem.

Explanation

Storage allocation for DSA area has failed.

System action

Dynatrace hooks are not enabled.

User response

Check CICS log and correct the problem.

Explanation

Bad address for DSA storage free

System action

No attempt to free main storage.

User response

This is usually not a problem as Dynatrace code module usually just didn't get any storage for this configuration.

Explanation

Bad address for DSA storage free from CICS chain.

System action

No attempt to free main storage.

User response

The storage chain is broken or corrupt. If this repeats, Please contact a Dynatrace ONE product specialist by selecting the chat button in the upper-right corner of the Dynatrace menu bar.

Explanation

DTAX time value was not in the range from 1 to 5.

System action

The value is reset to 5.

User response

If you are changing ICE values in the DTAX transaction make sure it is value from 1 to 5.

Explanation

CICS code module has been updated. A CICS restart is required to run the new code.

System action

None

User response

Restart CICS when you can to pick up new code module versions.

Explanation

CICSPlex name not found for the CICS region due to an unexpected error indicated by the error code “xx”

System action

CICS code module continues initialization.

User response

None

Explanation

Couldn't disable Language Environment sensor.

System action

Language Environment sensor is not turned off, CICS code module continues to monitor LE events.

User response

Please contact a Dynatrace ONE product specialist by selecting the chat button in the upper-right corner of the Dynatrace menu bar.

Explanation

Couldn't enable Language Environment sensor.

System action

CICS code module doesn't monitor LE events.

User response

Please contact a Dynatrace ONE product specialist by selecting the chat button in the upper-right corner of the Dynatrace menu bar.

Explanation

Couldn't disable the TRUE and GLUE exits after two consecutive attempts.

System action

CICS code module might cause an AKEA abend.

User response

Examine CICS log for DISABLE EXITALL failure. Please contact a Dynatrace ONE product specialist by selecting the chat button in the upper-right corner of the Dynatrace menu bar.

Explanation

CICS code module has detected an unsupported version of CICS.

System action

CICS code module is disabled.

User response

Upgrade your CICS region to a version supported by Dynatrace.

Explanation

Loading of the CICS code module has failed.

System action

CICS code module is disabled.

User response

Examine the CICS job output for any other messages that may be relevant to the failure. Please contact a Dynatrace ONE product specialist by selecting the chat button in the upper-right corner of the Dynatrace menu bar.

Explanation

The EXEC CICS RETRIEVE command used to control the Language Environment sensor interval has failed.

System action

None.

User response

Examine the more detailed message in the appropriate CICS job log to look at the precise EIBRESP code that indicates why this EXEC CICS RETRIEVE command failed. Please contact a Dynatrace ONE product specialist by selecting the chat button in the upper-right corner of the Dynatrace menu bar.

Explanation

The EXEC CICS START command used to initiate the Language Environment sensor interval has failed.

System action

None.

User response

Examine the more detailed message in the appropriate CICS job log to look at the precise EIBRESP code that indicates why this EXEC CICS START command failed. Please contact a Dynatrace ONE product specialist by selecting the chat button in the upper-right corner of the Dynatrace menu bar.

Explanation

During CICS startup or DTAX command processing, the Agent program was not marked ThreadSafe. ThreadSafe is required for CICS performance.

System action

Processing is terminated and the CICS region is not setup to run Dynatrace.

User response

Check that the Dynatrace CICS resource definitions has been added to the CICS region. Sample resource definitions can be found in installation sample dataset member(CICRDO).

Please contact a Dynatrace ONE product specialist by selecting the chat button in the upper-right corner of the Dynatrace menu bar.

Explanation

RDO definition for ZDTPLT with suffix (67/68/69/70/71/72/73) found.

System action

Execution continues.

User response

Update the RDO definitions for ZDTPLTxx and DTAX to refer to ZDTPLT without suffix. Refer to CICRDO member in SZDTSAMP installation library for sample RDO definitions.

Explanation

There was a problem in retrieving the Global Work Area storage for exit program. EXEC CICS EXTRACT EXIT operation failed. This is also possible when an attempt was made to look up DTAX CONF when the CICS code module is disabled.

System action

None

User response

Determine the cause of the problem from resp and resp2 codes. Please contact a Dynatrace ONE product specialist by selecting the chat button in the upper-right corner of the Dynatrace menu bar.

Explanation

Exits are enabled but there was a problem in retrieving the Global work area because there was no zDC available.

System action

None

User response

Check if the zDC is up and connected to zRA. Please contact a Dynatrace ONE product specialist by selecting the chat button in the upper-right corner of the Dynatrace menu bar.

Explanation

There was no zDC available for CICS code module to connect to.

System action

CICS code module is disabled.

User response

Start zDC and check if the zDC connects successfully to zRA. Please contact a Dynatrace ONE product specialist by selecting the chat button in the upper-right corner of the Dynatrace menu bar.

Explanation

CICS code module could not retrieve CICS Sensor configuration block.

System action

DTAX transaction attempts to retrieve CICS Sensor configuration block in the next 5 minutes interval.

User response

Check if the CICS code module is successfully enabled in the next 5 minutes interval. Please contact a Dynatrace ONE product specialist by selecting the chat button in the upper-right corner of the Dynatrace menu bar.

Explanation

DTAX ICE command was issued with an invalid value.

System action

DTAX transaction sets the ICE value to the default 5 minutes.

User response

If you want to change the default DTAX ICE value, enter a value between 1 to 5.

Explanation

No CICSplex name is available for the CICS region.

System action

CICS code module continues initialization.

User response

None

Explanation

DTAX CONF option couldn't display all the configuration settings in the DTAX panel, because there's not enough screen area for the display.

System action

Configuration settings are truncated in the DTAX display

User response

None

Explanation

Check all CICS code module configuration parameters in Dynatrace UI.

System action

None

User response

To view all the CICS code module configuration settings, go to Settings > Server-side service monitoring > Deep monitoring > CICS, IMS and MQ monitoring.

Explanation

Couldn't enable Language Environment sensor.

System action

CICS code module doesn't monitor Language Environment events.

User response

Please contact a Dynatrace ONE product specialist by selecting the chat button in the upper-right corner of the Dynatrace menu bar.

Explanation

Couldn't disable Language Environment sensor.

System action

CICS code module continues to monitor Language Environment events which might cause overhead.

User response

Please contact a Dynatrace ONE product specialist by selecting the chat button in the upper-right corner of the Dynatrace menu bar.

Explanation

Dynatrace CICS code module versions are different.

System action

None.

User response

Perform CEMT SET NEWCOPY for the version that is older. For example:

If PLT is older

plaintextcopydownload
CEMT SET PROG(ZDTPLT) NEWCOPY

If CICS code module version is older (zz is the CTS version)

plaintextcopydownload
CEMT SET PROG(ZDTAGTzz) NEWCOPY

Explanation

Invalid minute value entered for the Language Environment sensor.

System action

None.

User response

Enter a valid interval, between 1-1000 minutes, to enable the Language Environment sensor.

Explanation

The Language Environment sensor interval value entered is out of range.

System action

None.

User response

Enter a valid interval value between 1-1000 minutes to enable the Language Environment sensor.

Explanation

User issued a DTAX PING command.

System action

Check if the connection exists between the z/OS CICS code module and the zRemote code module.

User response

None

Explanation

User issued a DTAX DISABLE command.

System action

Disable all the exits used by CICS code module and terminate the 5 minutes DTAX cycle.

User response

None

Explanation

User issued a DTAX CONF command.

System action

Display the active CICS Sensor configuration in the DTAX panel.

User response

None

Explanation

User issued a DTAX ENABLE command.

System action

CICS code module registers with the collection system. On successful connection, respective EXITs and Hooks are enabled.

User response

None

Explanation

This message is displayed in zRemote log file when the CICS code module connects during CICS startup. This message gives ZDTPLT compilation and version information.

System action

None

User response

None

Explanation

This message is logged in zRemote log file when the CICS code module connects during CICS startup. This message gives CICS code module module (ZDTAGT) compilation and version information.

System action

None

User response

None

Explanation

This message is logged in zRemote log file when the CICS code module connects during CICS startup. This message gives ZDTSOAPH compilation and version information.

System action

None

User response

None

Explanation

The PLT program is unable to establish connection with the zRemote code module during PLT time.

System action

Reconnect attempted during the next DTAX cycle, which starts immediately after the CICS region comes up.

User response

None

Explanation

There was a problem in retrieving the screen attributes.

System action

Screen attributes are defaulted to Screen Width=80 and Screen Height=24.

User response

None

Explanation

The exit program ZDTAGTxx associated with entryname ZDTAGENT is disabled. xx represents the CTS version.

System action

None

User response

None

Explanation

The exit program ZDTAGTxx associated with entryname ZDTAGENT is enabled. xx represents the CTS version.

System action

None

User response

None

Explanation

Enable the global exit point specified by [exit name] associated with the ZDTAGTxx exit.

System action

None

User response

None

Explanation

Start the user exit ZDTAGENT associated with the exit program ZDTAGTxx.

System action

None

User response

None

Explanation

Start the global exit point specified by [exit name] associated with the exit program ZDTAGTxx.

System action

None

User response

None

Explanation

Stop and disable all the exit points associated with the exit ZDTAGTxx.

System action

None

User response

None

Explanation

Disable the global exit point [exit name] associated with the exit ZDTAGTxx.

System action

None

User response

None

Explanation

Indicates that CICS sensor configuration has been retrieved successfully after there was a problem in configuration block access. This message follows after ZDTP049S when the CICS transaction server sensor has been placed.

System action

CICS code module is initialized.

User response

None

Explanation

Indicates the CICS Sensors that are placed and active.

System action

None

User response

None

Explanation

Indicates that the CICS Sensors have been updated and the CICS code module honored the changes during DTAX 5 minutes cycle.

System action

None

User response

None

Explanation

EXEC CICS INQUIRE DB2CONN has failed.

System action

CICS code module operation continues. No DB2 attachment details provided in the distributed trace.

User response

Determine the cause of the problem from resp and resp2 codes. Please contact a Dynatrace ONE product specialist by selecting the chat button in the upper-right corner of the Dynatrace menu bar.

Explanation

DTAX ICE value was changed.

System action

None this is for information only.

User response

None

Explanation

Indicates that the Trace hook is being turned on in the CICS code module.

System action

None this is for information only.

User response

None

Explanation

Indicates that the Trace hook is being turned off in the CICS code module.

System action

None this is for information only.

User response

None

Explanation

Indicates that the Language Environment sensor has been turned on for the current DTAX ICE interval. Note that the Language Environment sensor will be automatically turned off during the following DTAX ICE cycle.

System action

None this is for information only.

User response

None

Explanation

Indicates that the Language Environment sensor has been automatically turned off at the end of the current ICE interval.

System action

None this is for information only.

User response

None

Explanation

Displays the Start TX sensor setting in Deep Monitoring in the web UI for the CICS regions.

System action

None: this is only informational.

User response

None

Explanation

User issued a DTAX LEENAB command to turn on the Language Environment sensor.

System action

Language Environment sensor is turned on temporarily. CICS code module starts monitoring LE dynamic calls.

User response

None

Explanation

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

System action

None, this is informational only.

User response

None

Explanation

Indicates that the DSA at location addr, used by CICS code module, has been freed.

System action

DSA memory is freed.

User response

None

Explanation

CICS code module has completed installing SOAP hook for SOAP request monitoring. Return code 0 indicates successful SOAP hook installation.

System action

CICS code module is ready to monitor SOAP events with successful SOAP hook installation.

User response

If the Return code is a non-zero value, SOAP hook installation has failed. Please contact a Dynatrace ONE product specialist by selecting the chat button in the upper-right corner of the Dynatrace menu bar.

Explanation

CICS code module has completed removing SOAP hook. Return code 0 indicates successful SOAP hook removal.

System action

CICS code module stops monitoring SOAP events if the SOAP hook has been removed successfully.

User response

If the Return code is a non-zero value, SOAP hook removal has failed. Please contact a Dynatrace ONE product specialist by selecting the chat button in the upper-right corner of the Dynatrace menu bar.

Explanation

CICS code module has completed installing MRO hook for multi region call monitoring. Return code 0 indicates successful MRO hook installation.

System action

CICS code module is ready to monitor MRO events with the successful MRO hook installation.

User response

If the Return code is a non-zero value, MRO hook installation has failed. Please contact a Dynatrace ONE product specialist by selecting the chat button in the upper-right corner of the Dynatrace menu bar.

Explanation

CICS code module has completed removing MRO hook. Return code 0 indicates successful MRO hook removal.

System action

CICS code module stops monitoring MRO events if the MRO hook has been removed successfully.

User response

If the Return code is a non-zero value, MRO hook removal has failed. Please contact a Dynatrace ONE product specialist by selecting the chat button in the upper-right corner of the Dynatrace menu bar.

Explanation

CICS code module has completed installing ERM hook for DB2 call monitoring. Return code 0 indicates successful ERM hook installation.

System action

CICS code module is ready to monitor DB2 calls from the CICS region with the successful ERM hook installation.

User response

If the Return code is a non-zero value, ERM hook installation has failed. Please contact a Dynatrace ONE product specialist by selecting the chat button in the upper-right corner of the Dynatrace menu bar.

Explanation

CICS code module has completed removing ERM hook. Return code 0 indicates successful ERM hook removal.

System action

CICS code module stops monitoring DB2 calls if the ERM hook has been removed successfully.

User response

If the Return code is a non-zero value, ERM hook removal has failed. Please contact a Dynatrace ONE product specialist by selecting the chat button in the upper-right corner of the Dynatrace menu bar.

Explanation

CICS code module has completed installing PL1 hook for monitoring PL1 dynamic calls. Return code 0 indicates successful PL1 hook installation.

System action

CICS code module is ready to monitor PL1 dynamic calls with the successful PL1 hook installation.

User response

If the Return code is a non-zero value, PL1 hook installation has failed. Please contact a Dynatrace ONE product specialist by selecting the chat button in the upper-right corner of the Dynatrace menu bar.

Explanation

CICS code module has completed removing PL1 hook. Return code 0 indicates successful PL1 hook removal.

System action

CICS code module stops monitoring PL1 dynamic calls if the PL1 hook has been removed successfully.

User response

If the Return code is a non-zero value, PL1 hook removal has failed. Please contact a Dynatrace ONE product specialist by selecting the chat button in the upper-right corner of the Dynatrace menu bar.

Explanation

CICS code module has completed installing COBOL hooks IGZCFCC, IGZCLNK and IGZXFCAL (indicated by “COBOL routine”) for monitoring COBOL dynamic calls. Return code 0 indicates successful COBOL hooks installation.

System action

CICS code module is ready to monitor COBOL dynamic calls with the successful COBOL hooks installation.

User response

If the Return code is a non-zero value, COBOL hook installation has failed. Please contact a Dynatrace ONE product specialist by selecting the chat button in the upper-right corner of the Dynatrace menu bar.

Explanation

CICS code module has completed removing COBOL hook. Return code 0 indicates successful COBOL hook removal.

System action

CICS code module stops monitoring COBOL dynamic calls if the COBOL hook has been removed successfully.

User response

If the Return code is a non-zero value, COBOL hook removal has failed. Please contact a Dynatrace ONE product specialist by selecting the chat button in the upper-right corner of the Dynatrace menu bar.

Explanation

The IMS code module's ABEND recovery routine was invoked by RTM.

System action

The ABEND recovery process continues.

User response

Please contact a Dynatrace ONE product specialist by selecting the chat button in the upper-right corner of the Dynatrace menu bar.

Explanation

The IMS code module's ABEND recovery process was successful.

System action

The IMS code module is disabled and the IMS system continues to function.

User response

Please contact a Dynatrace ONE product specialist by selecting the chat button in the upper-right corner of the Dynatrace menu bar.

Explanation

The IMS code module's ABEND recovery routine was unable to obtain the dynamic storage required to produce ABEND diagnostics.

System action

The ABEND recovery process continues but some diagnostic information may not be available. A Software (SFT) Error Record further describing the ABEND is written to the z/OS system SYS1.LOGREC data set.

User response

Run the z/OS EREP utility program to print the Software (SFT) Error Record associated with the ABEND. Please contact a Dynatrace ONE product specialist by selecting the chat button in the upper-right corner of the Dynatrace menu bar.

Explanation

The z/OS system doesn't allow the IMS code module's ABEND recovery process to continue.

System action

The recovery process terminates and percolates (returns control to RTM).

User response

Please contact a Dynatrace ONE product specialist by selecting the chat button in the upper-right corner of the Dynatrace menu bar.

Explanation

An ABEND occurred at offset xxxxxx in the ZDTIIInn module of the IMS code module, where nn corresponds to the IMS version (for example, 12). The remaining fields describe the maintenance level of the IMS code module.

System action

A Software (SFT) Error Record further describing the ABEND is written to the z/OS system SYS1.LOGREC data set. Optionally, an SVC dump may be taken. The ABEND recovery process continues.

User response

Run the z/OS EREP utility program to print the Software (SFT) Error Record associated with the ABEND. Please contact a Dynatrace ONE product specialist by selecting the chat button in the upper-right corner of the Dynatrace menu bar.

Explanation

An ABEND occurred in the ZDTIIInn module of the IMS code module, where nn corresponds to the IMS version (for example, 12). The remaining fields describe the maintenance level of the IMS code module. The ABEND offset could not be determined because no SDWA was provided by RTM.

System action

The recovery process terminates and percolates (returns control to RTM).

User response

Please contact a Dynatrace ONE product specialist by selecting the chat button in the upper-right corner of the Dynatrace menu bar.

Explanation

While recovering from an ABEND in the IMS code module, the recovery routine encountered an ABEND.

System action

The ABEND recovery process continues but does not attempt to produce further diagnostics. The IMS code module is disabled and the IMS system continues to function.

User response

Please contact a Dynatrace ONE product specialist by selecting the chat button in the upper-right corner of the Dynatrace menu bar.

Explanation

The ODIN zOS stub is returning a diagnostic code.

System action

Processing continues.

User response

Please contact a Dynatrace ONE product specialist by selecting the chat button in the upper-right corner of the Dynatrace menu bar.

Explanation

The ODIN zOS stub can not find the vendor table.

System action

Processing fails.

User response

Restart zDC with a current maintaince level (at least the same as Java-ODIN). Then restart the Java process.