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.
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 a Dynatrace ONE product specialist. To contact Dynatrace ONE, select the chat button in the upper-right corner of the Dynatrace menu bar).
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.
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.
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 a Dynatrace ONE product specialist. To contact Dynatrace ONE, select the chat button in the upper-right corner of the Dynatrace menu bar.
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.
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.
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.
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 a Dynatrace ONE product specialist by selecting the chat button in the upper-right corner of the Dynatrace menu bar. Re-execute zDC.
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 sent to a Dynatrace ONE product specialist by selecting the chat button in the upper-right corner of the Dynatrace menu bar. Re-execute zDC.
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 product specialist. Try to and re-attach and re-open the log (MVS command: Modify ZdcStcName,LOG OPEN).
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 a Dynatrace ONE product specialist. Try to re-attach and re-open the log (MVS command: Modify ZdcStcName,LOG OPEN).
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 a Dynatrace ONE product specialist. Enter the ISPF zDC control system. Then re-attach and re-open the log.
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. Report this message to a Dynatrace ONE product specialist by selecting the chat button in the upper-right corner of the Dynatrace menu bar.
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.
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 a Dynatrace ONE product specialist by selecting the chat button in the upper-right corner of the Dynatrace menu bar.
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.
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).
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.
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.
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.
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.
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.
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.
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.
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.
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 product specialist by clicking the chat button in the upper-right corner of the Dynatrace menu bar.
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.
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
Report this message to Dynatrace ONE product specialist by clicking the chat button in the upper-right corner of the Dynatrace menu bar.
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 product specialist by clicking the chat button in the upper-right corner of the Dynatrace menu bar.
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 product specialist by clicking the chat button in the upper-right corner of the Dynatrace menu bar.
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 product specialist by clicking the chat button in the upper-right corner of the Dynatrace menu bar.
The three codes in this message correspond to the IEAMSCHDSYNCHCOMPADDR, SYNCHCODEADDR and SYNCHRSNADDR values.
System action
zDC execution ends.
User response
Report this message to your systems programmer who may need to Dynatrace ONE product specialist by clicking the chat button in the upper-right corner of the Dynatrace menu bar.
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.
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 product specialist by clicking the chat button in the upper-right corner of the Dynatrace menu bar.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
The LOG_INITIAL parameter must specify either (OPEN)(CLOSED) or (). Any other values are invalid.
If you omit this parameter or specify () the default isLOG_INITIAL(CLOSED). Specify all the other parameters for logging that are applicable to your SMS environment, and also specify LOG_INITIAL(CLOSED). You can dynamically start logging using the specified parameters if the need arises. With the log in a CLOSED state no system resources are consumed.
System action
zDC execution ends.
User response
Correct the LOG_INITIAL parameter and re-execute zDC.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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).
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.
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.
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).
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
The parameters DTPIPEPATH, DTCHDIR, DTAGTCMD, or DTLOG are invalid. See comments in the supplied sample config member for a description of these parameters.
This message indicates that the queue is filling and you should be aware that, if it reaches 100%, new messages won't be sent to the zLocal, possibly causing PurePath corruption.
This message first displays when the queue reaches 70% and re-displays at five percent increments. When utilization drops below 70%, this message no longer displays. Note that this message appears on the system console as well as in the SYSPRINT data set.
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().
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 product specialist by clicking the chat button in the upper-right corner of the Dynatrace menu bar.
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 product specialist by clicking the chat button in the upper-right corner of the Dynatrace menu bar.
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 product specialist by clicking the chat button in the upper-right corner of the Dynatrace menu bar.
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.
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 product specialist by clicking the chat button in the upper-right corner of the Dynatrace menu bar.
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.
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 product specialist by clicking the chat button in the upper-right corner of the Dynatrace menu bar.
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 product specialist by clicking the chat button in the upper-right corner of the Dynatrace menu bar.
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 product specialist by clicking the chat button in the upper-right corner of the Dynatrace menu bar.
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 product specialist by clicking the chat button in the upper-right corner of the Dynatrace menu bar.
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 product specialist by clicking the chat button in the upper-right corner of the Dynatrace menu bar.
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 product specialist by clicking the chat button in the upper-right corner of the Dynatrace menu bar.
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 product specialist by clicking the chat button in the upper-right corner of the Dynatrace menu bar.
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 product specialist by clicking the chat button in the upper-right corner of the Dynatrace menu bar.
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.
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.
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 contact a Dynatrace ONE product specialist by clicking the chat button in the upper-right corner of the Dynatrace menu bar.
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 contact a Dynatrace ONE product specialist by clicking the chat button in the upper-right corner of the Dynatrace menu bar.
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, contact a Dynatrace ONE product specialist by clicking the chat button in the upper-right corner of the Dynatrace menu bar.
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, contact a Dynatrace ONE product specialist by clicking the chat button in the upper-right corner of the Dynatrace menu bar.
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, contact a Dynatrace ONE product specialist by clicking the chat button in the upper-right corner of the Dynatrace menu bar.
Determine the cause of the problem from resp and resp2 codes. If the problem persists, contact a Dynatrace ONE product specialist by clicking the chat button in the upper-right corner of the Dynatrace menu bar.
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, contact a Dynatrace ONE product specialist by clicking the chat button in the upper-right corner of the Dynatrace menu bar.
Determine the cause of the problem from resp and resp2 codes. If the problem persists, contact a Dynatrace ONE product specialist by clicking the chat button in the upper-right corner of the Dynatrace menu bar.
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, contact a Dynatrace ONE product specialist by clicking the chat button in the upper-right corner of the Dynatrace menu bar.
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, contact a Dynatrace ONE product specialist by clicking the chat button in the upper-right corner of the Dynatrace menu bar.
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, contact a Dynatrace ONE product specialist by clicking the chat button in the upper-right corner of the Dynatrace menu bar.
Determine the cause of the problem from resp and resp2 codes. If the problem persists, contact a Dynatrace ONE product specialist by clicking the chat button in the upper-right corner of the Dynatrace menu bar.
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, contact a Dynatrace ONE product specialist by clicking the chat button in the upper-right corner of the Dynatrace menu bar.
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, contact a Dynatrace ONE product specialist by clicking the chat button in the upper-right corner of the Dynatrace menu bar.
Determine the cause of the problem from resp and resp2 codes. If the problem persists, contact a Dynatrace ONE product specialist by clicking the chat button in the upper-right corner of the Dynatrace menu bar.
Determine the cause of the problem from resp and resp2 codes. If the problem persists, contact a Dynatrace ONE product specialist by clicking the chat button in the upper-right corner of the Dynatrace menu bar.
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, contact a Dynatrace ONE product specialist by clicking the chat button in the upper-right corner of the Dynatrace menu bar.
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, contact a Dynatrace ONE product specialist by clicking the chat button in the upper-right corner of the Dynatrace menu bar.
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, contact a Dynatrace ONE product specialist by clicking the chat button in the upper-right corner of the Dynatrace menu bar.
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, contact a Dynatrace ONE product specialist by clicking the chat button in the upper-right corner of the Dynatrace menu bar.
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, contact a Dynatrace ONE product specialist by clicking the chat button in the upper-right corner of the Dynatrace menu bar.
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, contact a Dynatrace ONE product specialist by clicking the chat button in the upper-right corner of the Dynatrace menu bar.
Look in CICS log for problems. If nothing, contact a Dynatrace ONE product specialist by clicking the chat button in the upper-right corner of the Dynatrace menu bar.
Look in CICS log for problems. If nothing, contact a Dynatrace ONE product specialist by clicking the chat button in the upper-right corner of the Dynatrace menu bar.
The storage chain is broken or corrupt. If this repeats, contact a Dynatrace ONE product specialist by clicking the chat button in the upper-right corner of the Dynatrace menu bar.
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. If the problem is not resolved, contact a Dynatrace ONE product specialist by clicking the chat button in the upper-right corner of the Dynatrace menu bar.
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.
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. If the problem persists, contact a Dynatrace ONE product specialist by clicking the chat button in the upper-right corner of the Dynatrace menu bar.
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. If the problem persists, contact a Dynatrace ONE product specialist by clicking the chat button in the upper-right corner of the Dynatrace menu bar.
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. If the problem persists contact a Dynatrace ONE product specialist by clicking the chat button in the upper-right corner of the Dynatrace menu bar.
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. If the problem persists contact a Dynatrace ONE product specialist by clicking the chat button in the upper-right corner of the Dynatrace menu bar.
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.
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.
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.
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.
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.
CICS code module operation continues. No DB2 attachment details provided in the Purepath.
User response
Determine the cause of the problem from resp and resp2 codes. If the problem persists, contact a Dynatrace ONE product specialist by clicking the chat button in the upper-right corner of the Dynatrace menu bar.
Indicates that the LE sensor has been turned on for the current DTAX ICE interval. Note that the LE sensor will be automatically turned off during the following DTAX ICE cycle.
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. Contact a Dynatrace ONE product specialist by clicking the chat button in the upper-right corner of the Dynatrace menu bar.
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. Contact a Dynatrace ONE product specialist by clicking the chat button in the upper-right corner of the Dynatrace menu bar.
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. Contact a Dynatrace ONE product specialist by clicking the chat button in the upper-right corner of the Dynatrace menu bar.
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. Contact a Dynatrace ONE product specialist by clicking the chat button in the upper-right corner of the Dynatrace menu bar.
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. Contact a Dynatrace ONE product specialist by clicking the chat button in the upper-right corner of the Dynatrace menu bar.
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. Contact a Dynatrace ONE product specialist by clicking the chat button in the upper-right corner of the Dynatrace menu bar.
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. Contact a Dynatrace ONE product specialist by clicking the chat button in the upper-right corner of the Dynatrace menu bar.
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. Contact a Dynatrace ONE product specialist by clicking the chat button in the upper-right corner of the Dynatrace menu bar.
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. Contact a Dynatrace ONE product specialist by clicking the chat button in the upper-right corner of the Dynatrace menu bar.
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. Contact a Dynatrace ONE product specialist by clicking the chat button in the upper-right corner of the Dynatrace menu bar.
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. Contact a Dynatrace ONE product specialist by clicking the chat button in the upper-right corner of the Dynatrace menu bar.
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. Contact a Dynatrace ONE product specialist by clicking the chat button in the upper-right corner of the Dynatrace menu bar.
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
Contact a Dynatrace ONE product specialist by clicking the chat button in the upper-right corner of the Dynatrace menu bar.
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
Contact a Dynatrace ONE product specialist by clicking the chat button in the upper-right corner of the Dynatrace menu bar.
