The z/OS code module of OneAgent can issue the following types of system message:
zDC system messages
ZDC000I INITIALIZATION @@ FOR zDC @@ VER @@.@@.@@
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 |
ZDC001E AN ERROR HAS OCCURRED DURING LOAD FOR MODULE @@
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. |
ZDC002E MODULE=@@ R15=@@ R1=@@
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 a Dynatrace ONE product specialist. To contact Dynatrace ONE, select the chat button in the upper-right corner of the Dynatrace menu bar). |
ZDC003E COMMON AREA STORAGE NOT AVAILABLE FOR MODULE @@
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. |
ZDC004E AN ERROR HAS OCCURRED DURING BLDL FOR MODULE @@
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. |
ZDC005E MODULE=@@ R15=@@ R1=@@
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 a Dynatrace ONE product specialist. To contact Dynatrace ONE, select the chat button in the upper-right corner of the Dynatrace menu bar. |
ZDC006E SUBSYSTEM @@ ALREADY EXISTS AND IS ACTIVE
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. |
ZDC007E ECSA STORAGE NOT AVAILABLE FOR SUBSYSTEM @@, R15=@@
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. |
ZDC008I MODULE P/T DATE TIME VERSION ADDRESS LENGTH
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 |
ZDC009I @@ @@ @@ @@ @@ @@ @@
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 |
ZDC010E SDUMPX TAKEN SUCCESSFULLY FOR zDC @@ ABEND
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 a Dynatrace ONE product specialist. Re-execute zDC. |
ZDC011E SDUMPX FAILED FOR zDC @@ ABEND. RETCODE=@@/@@
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 a Dynatrace ONE product specialist by selecting the chat button in the upper-right corner of the Dynatrace menu bar. Re-execute zDC. |
ZDC012E @@ ABEND DUMP IN DYNATRACE 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 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. |
ZDC014E ZDCLOGER VSAM @@ ERROR
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 product specialist. Try to and re-attach and re-open the log (MVS command: Modify ZdcStcName,LOG OPEN ). |
ZDC015E ZDCLOGER VSAM RPL FEEDBACK WORD @@
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 a Dynatrace ONE product specialist. Try to re-attach and re-open the log (MVS command: Modify ZdcStcName,LOG OPEN ). |
ZDC016E ZDCLOGER VSAM ACB ERROR FLAG @@
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 a Dynatrace ONE product specialist. Enter the ISPF zDC control system. Then re-attach and re-open the log. |
ZDC017E SRB ABEND @@ AT DISPLACEMENT @@ INTO ZDCSRBRT
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 a Dynatrace ONE product specialist. Re-execute zDC. |
ZDC018E EXTENDED CSA STORAGE NOT AVAILABLE FOR SRB ROUTINE
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. |
ZDC019E zDC INITIALIZATION FAILED. RETCODE=@@/@@
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. Report this message to a Dynatrace ONE product specialist by selecting the chat button in the upper-right corner of the Dynatrace menu bar. |
ZDC026I STOP COMMAND ACCEPTED
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 |
ZDC027I MODIFY COMMAND RECEIVED
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 |
ZDC028I @@
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 |
ZDC033E INVALID COMMAND. PLEASE REENTER
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 a Dynatrace ONE product specialist by selecting the chat button in the upper-right corner of the Dynatrace menu bar. |
ZDC035I @@ ARMED FOR AUTOMATIC RESTART
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 |
ZDC036I @@ RESTARTED DUE TO PREVIOUS ABEND. RSNCD=@@
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 |
ZDC037E @@ IXCARM REGISTER FAILURE. RETCD=@@. RSNCD=@@
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. |
ZDC038E @@ IXCARM READY FAILURE. RETCD=@@. RSNCD=@@
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. |
ZDC039I @@ AUTOMATIC RESTART NOT SUPORTED ON THIS SYSTEM
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. |
ZDC048I THE FOLLOWING MODULES ARE LOADED INTO ECSA
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 |
ZDC052I zDC IS RUNNING ON @@ RELEASE @@
Explanation |
This informational message indicates the name and release level on which this zDC is running. |
System action |
Processing continues. |
User response |
None |
ZDC053I LPAR NAME @@ CVTSNAME @@
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 |
ZDC054E zDC ACTIVE SUBSYSTEM @@ ALREADY MARKED AS DEFAULT
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. |
ZDC059I zDC NOW EXECUTING UNDER USERID @@
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 |
ZDC060I LOG @@ @@ SUCCESSFULLY
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 |
ZDC061E INSUFFICIENT ACCESS TO LOG DATA SET. SEE JOBLOG
Explanation |
This message is written to SYSPRINT indicating that the USERID under 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. |
ZDC062E LOG TASK INITIALIZATION FAILURE RC=@@/@@
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. |
ZDC064E QUEUE TASK INITIALIZATION FAILURE
Explanation |
This message is written to SYSPRINT indicating that the queue subtask has failed to initialize. |
System action |
zDC terminates. |
User response |
Report this message to a Dynatrace ONE product specialist by selecting the chat button in the upper-right corner of the Dynatrace menu bar. |
ZDC066E QUEUE TASK FAILURE RETCODE=@@/@@
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 product specialist by clicking the chat button in the upper-right corner of the Dynatrace menu bar. |
ZDC067E LOG TASK FAILURE RETCODE=@@/@@
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. |
ZDC069W zDC QUEUE IS AT @@% OF CAPACITY
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 |
Report this message to Dynatrace ONE product specialist by clicking the chat button in the upper-right corner of the Dynatrace menu bar. |
ZDC071W UNABLE TO CONSTRUCT SDUMPX SYMREC RETCODE=@@/@@
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 |
ZDC072W WLM ENCLAVE CREATION FAILED. @@ @@/@@
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 product specialist by clicking the chat button in the upper-right corner of the Dynatrace menu bar. |
ZDC073I WLM ENCLAVE @@ CREATED SUCCESSFULLY
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 |
ZDC074E WLM ENCLAVE DELETION FAILED. @@ @@/@@
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 product specialist by clicking the chat button in the upper-right corner of the Dynatrace menu bar. |
ZDC076E WLM ENCLAVE SRB EXECUTION FAILED. RETCODE=@@
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 product specialist by clicking the chat button in the upper-right corner of the Dynatrace menu bar. |
ZDC077E WLM ENCLAVE SRB REASON CODES=@@ @@ @@
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 product specialist by clicking the chat button in the upper-right corner of the Dynatrace menu bar. |
ZDC078W QUERT.STAWXXX UNEXPECTED @@ DISPATCH DELAY @@ @@ @@ @@)
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. |
ZDC079W IEAVRLS ERROR, RETURN CODE @@
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 product specialist by clicking the chat button in the upper-right corner of the Dynatrace menu bar. |
ZDC083E SUBSYSTEM @@ ALREADY EXISTS BUT IS NOT A zDC SUBSYSTEM
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. |
ZDC100I SYSIN PARAMETER LISTING
Explanation |
This message indicates that the //SYSIN parameters specified by the customer are listed next. |
System action |
Processing continues. |
User response |
None |
ZDC102E SYSTEM VARIABLE SUBSTITUTION FAILED. @@
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. |
ZDC103E UNABLE TO OPEN //SYSIN DATA SET
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 . |
ZDC106E UNKNOWN SYSIN KEYWORD @@
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. |
ZDC107E SUBSYSTEM_ID PARAMETER MISSING
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. |
ZDC110E NAME PARAMETER MISSING
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. |
ZDC116E AUTOMATIC RESTART MANAGEMENT NAME MISSING
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. |
ZDC121E SUBSYSTEM_ID PARAMETER INVALID
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. |
ZDC122E DISPLAY_NAME PARAMETER INVALID
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. |
ZDC123E DEFAULT PARAMETER INVALID
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. |
ZDC125E EVENT_WAIT PARAMETER INVALID
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. |
ZDC126E TCPIP_USERID PARAMETER INVALID
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. |
ZDC127E LOG_INITIAL PARAMETER INVALID
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 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. |
ZDC128E LOG_DSNAME PARAMETER IS INVALID
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. |
ZDC130E LOG_VOLSER PARAMETER IS INVALID
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. |
ZDC131E LOG_TRKS PARAMETER IS INVALID
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. |
ZDC132E LOG_CYLS PARAMETER IS INVALID
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. |
ZDC133E LOG_MGMTCLASS PARAMETER IS INVALID
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. |
ZDC135E LOG_STORCLASS PARAMETER IS INVALID
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. |
ZDC155E ARM PARAMETER INVALID
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 |
ZDC156E ARM_ELEMENT_NAME PARAMETER INVALID
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. |
ZDC185E PROTECT PARAMETER INVALID
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. |
ZDC187E DEFAULT PARAMETER MISSING
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. |
ZDC189E OPERATING_SYSTEM PARAMETER INVALID
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. |
ZDC194E zIIP_ENABLE PARAMETER INVALID
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. |
ZDC196E DTMSG_QSIZE PARAMETER IS INVALID
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. |
ZDC197E DTMSG_SMOSIZE PARAMETER IS INVALID
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. |
ZDC198E DT_UMASK PARAMETER IS INVALID
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. |
ZDC199E DTMSG_TBCSIZE PARAMETER IS INVALID
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. |
ZDC200I DTMSG_QSIZE PARAMETER IS DEPRECATED
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. |
ZDC201E ZDCLOGBUFFERSIZE PARAMETER IS INVALID
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. |
ZDC202E ZDCMAXLOGFILESIZE PARAMETER IS INVALID
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. |
ZDC203E ZDCDISPATCHDELAYWARN PARAMETER IS INVALID
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. |
ZDC204E ZDCDISPATCHDELAYRPTM PARAMETER IS INVALID
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. |
ZDC205E ZEDC_COMPRESS PARAMETER IS INVALID
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. |
ZDC206E TCP_BUFFER PARAMETER IS INVALID
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. |
ZDC208I METRIC_INTERVAL PARAMETER IS INVALID
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. |
ZDC209I DISPLAY_INTERVAL PARAMETER IS INVALID
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. |
ZDC210I zDC NO LONGER LINKED TO TCP/IP
Explanation |
This informational message indicates that the TERMAPI macro was successfully executed to terminate TCP/IP communications. |
System action |
Processing continues. |
User response |
None |
ZDC211E DTMSG_TRANBUFSIZE PARAMETER IS INVALID
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. |
ZDC212E zremoteagent= IS REQUIRED IN DTAGTCMD
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. |
ZDC213W TCP_BUFFER PARAMETER IS OUT OF RANGE, SETTING 8K or 256K
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. |
ZDC215I TERMINATION STARTED FOR zDC @@
Explanation |
This informational message indicates that termination processing has started for this zDC. |
System action |
Termination processing continues. |
User response |
None |
ZDC217I LONG TERM STORAGE STATISTICS FOLLOW
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 |
ZDC218I PAGEABLE PRIVATE STORAGE @@
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 |
ZDC219I PAGEABLE COMMON STORAGE - CSA: @@ ECSA: @@
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 |
ZDC221I NUMBER SP 241 PAGES PROTECTED: @@
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 |
ZDC302E Message @@ - BAD REC ADDRESS PASSED
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 |
Report this message to Dynatrace ONE product specialist by clicking the chat button in the upper-right corner of the Dynatrace menu bar. |
ZDC8XXW INTERNAL MESSAGES FROM TCP MODULE ZDCTCPSP
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 |
ZDC950E DT PARAMETER INVALID
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. |
ZDC952W zDC zLocal.... {Buffer----Type} is at @@% of capacity
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 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() .
|
ZDC954W DT PARAMETER SYSLOG INVALID
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. |
ZDC974E Unexpected failure checking agent executable, Abort
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 product specialist by clicking the chat button in the upper-right corner of the Dynatrace menu bar. |
ZDC975E zLocal attach failed, Abort
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 product specialist by clicking the chat button in the upper-right corner of the Dynatrace menu bar. |
ZDC976E Unexpected failure during change directory, Abort
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 product specialist by clicking the chat button in the upper-right corner of the Dynatrace menu bar. |
ZDC977E Unexpected failure during z/OS Unix API, Abort
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. |
ZDC978E Failed ZDC.FML Name/Token operation, Abort
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 product specialist by clicking the chat button in the upper-right corner of the Dynatrace menu bar. |
ZDC979E Waiting for Que Data Space failed, Abort
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. |
ZDC980E Waiting for OMVS failed, Abort
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. |
ZDC981E DtmD.FlagBad internal error, Abort
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 product specialist by clicking the chat button in the upper-right corner of the Dynatrace menu bar. |
ZDC982E DtmD.LenBad internal error, Abort
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 product specialist by clicking the chat button in the upper-right corner of the Dynatrace menu bar. |
ZDC983E Timer routine critical error, Abort
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 product specialist by clicking the chat button in the upper-right corner of the Dynatrace menu bar. |
ZDC984E Critical error in Wait routine, Abort
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 product specialist by clicking the chat button in the upper-right corner of the Dynatrace menu bar. |
ZDC985E Poll for data failed, Abort
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 product specialist by clicking the chat button in the upper-right corner of the Dynatrace menu bar. |
ZDC986E Unnamed pipe required, Abort
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 product specialist by clicking the chat button in the upper-right corner of the Dynatrace menu bar. |
ZDC987E Internal error unknown ECB, Abort
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 product specialist by clicking the chat button in the upper-right corner of the Dynatrace menu bar. |
ZDC988E Unexpected PC return, Abort
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 product specialist by clicking the chat button in the upper-right corner of the Dynatrace menu bar. |
ZDC989E \*Dbg*Developer build test message
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. |
ZDC990I Internal DynaDiag
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. |
ZDC991I Internal DynaDiag
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. |
ZDC992I Internal DynaDiag
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. |
ZDC993I Internal DynaDiag
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. |
ZDC994I Internal DynaDiag
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. |
ZDC995W Internal DynaDiag
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. |
ZDC996E Internal DynaDiag
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. |
ZDC997I Internal DynaDiag
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. |
ZDC998I @@ @@ @@ @@
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. |
ZDC999I Internal DynaDiag: @@ @@ @@ @@
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. |
DTAX messages
ZDTP001S Persistent Storage allocation failed.
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 contact a Dynatrace ONE product specialist by clicking the chat button in the upper-right corner of the Dynatrace menu bar. |
ZDTP002S Message Block allocation failed.
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. |
ZDTP003S ZDTSOAPH Load failed.
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 contact a Dynatrace ONE product specialist by clicking the chat button in the upper-right corner of the Dynatrace menu bar. |
ZDTP004S ZDTDCCAL final block send failed. rc:<xx>.
Explanation |
Message transfer from CICS code module to zDC has failed. |
System action |
CICS code module operation continues but with missing nodes in the PurePath. |
User response |
Contact a Dynatrace ONE product specialist by clicking the chat button in the upper-right corner of the Dynatrace menu bar. |
ZDTP005S START DTAX ICE failed.
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, contact a Dynatrace ONE product specialist by clicking the chat button in the upper-right corner of the Dynatrace menu bar. |
ZDTP006S Inquire MQCONN <QMGR Name> returned with resp:<xx> resp2:<xx>.
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, contact a Dynatrace ONE product specialist by clicking the chat button in the upper-right corner of the Dynatrace menu bar. |
ZDTP007S Enable of temporary LE sensor failed no zDC.
Explanation |
Indicates that the LE sensor could not be enabled because zDC is unavailable. |
System action |
LE sensor is not enabled. CICS code module doesn't monitor LE dynamic calls. |
User response |
Start the zDC for CICS code module to reconnect. |
ZDTP008S GETMAIN PLT Workarea failed.
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. |
ZDTP009S PLT Name/Token storage not found rc: <xx>.
Explanation |
Persistent storage for PLT program is not found. |
System action |
The PLT program terminates and the CICS code module is disabled. |
User response |
Contact a Dynatrace ONE product specialist by clicking the chat button in the upper-right corner of the Dynatrace menu bar. |
ZDTP012S GWA Storage unavailable.
Explanation |
Global work area storage for PLT program is unavailable. |
System action |
Hooks don't initialize successfully. |
User response |
Contact a Dynatrace ONE product specialist by clicking the chat button in the upper-right corner of the Dynatrace menu bar. |
ZDTP016S ZDTHKIDR failed with rc: <xx>.
Explanation |
Hook operation has failed. |
System action |
CICS code module don't initialize successfully. |
User response |
Contact a Dynatrace ONE product specialist by clicking the chat button in the upper-right corner of the Dynatrace menu bar. |
ZDTP017S zDC INIT Failed.
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, contact a Dynatrace ONE product specialist by clicking the chat button in the upper-right corner of the Dynatrace menu bar. |
ZDTP018S CONF block allocation failed.
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. |
ZDTP019S Message buffer allocation failed.
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. |
ZDTP023S Inquire DB2Entry failed. resp:<xx>, resp2:<xx>, rcode:<xx>.
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, contact a Dynatrace ONE product specialist by clicking the chat button in the upper-right corner of the Dynatrace menu bar. |
ZDTP025S Inquire System failed. resp:<xx>, resp2:<xx>, rcode:<xx>.
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, contact a Dynatrace ONE product specialist by clicking the chat button in the upper-right corner of the Dynatrace menu bar. |
ZDTP028S Disable RMI Exit failed. resp:<xx>, resp2:<xx>, rcode:<xx>.
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, contact a Dynatrace ONE product specialist by clicking the chat button in the upper-right corner of the Dynatrace menu bar. |
ZDTP029S START Exit failed. resp:<xx>, resp2:<xx>, rcode:<xx>.
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, contact a Dynatrace ONE product specialist by clicking the chat button in the upper-right corner of the Dynatrace menu bar. |
ZDTP030S FREEMAIN failed. resp:<xx>, resp2:<xx>, rcode:<xx>.
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, contact a Dynatrace ONE product specialist by clicking the chat button in the upper-right corner of the Dynatrace menu bar. |
ZDTP031S Enable Exit failed. resp:<xx>, resp2:<xx>, rcode:<xx>.
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, contact a Dynatrace ONE product specialist by clicking the chat button in the upper-right corner of the Dynatrace menu bar. |
ZDTP032S STOP Exit failed. resp:<xx>, resp2:<xx>, rcode:<xx>.
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, contact a Dynatrace ONE product specialist by clicking the chat button in the upper-right corner of the Dynatrace menu bar. |
ZDTP033S Cancel ReqID failed. resp:<xx>, resp2:<xx>, rcode:<xx>.
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, contact a Dynatrace ONE product specialist by clicking the chat button in the upper-right corner of the Dynatrace menu bar. |
ZDTP034S Inquire ReqID failed. resp:<xx>, resp2:<xx>, rcode:<xx>.
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, contact a Dynatrace ONE product specialist by clicking the chat button in the upper-right corner of the Dynatrace menu bar. |
ZDTP035S GETMAIN failed. resp:<xx>, resp2:<xx>, rcode:<xx>.
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, contact a Dynatrace ONE product specialist by clicking the chat button in the upper-right corner of the Dynatrace menu bar. |
ZDTP036S START DTAX ICE failed. resp:<xx>, resp2:<xx>, rcode:<xx>.
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, contact a Dynatrace ONE product specialist by clicking the chat button in the upper-right corner of the Dynatrace menu bar. |
ZDTP037S LOAD Agent failed. resp:<xx>, resp2:<xx>, rcode:<xx>.
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, contact a Dynatrace ONE product specialist by clicking the chat button in the upper-right corner of the Dynatrace menu bar. |
ZDTP038S LOAD ZDTSOAPH failed. resp:<xx>, resp2:<xx>, rcode:<xx>.
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, contact a Dynatrace ONE product specialist by clicking the chat button in the upper-right corner of the Dynatrace menu bar. |
ZDTP039S Release code module failed. resp:<xx>, resp2:<xx>, rcode:<xx>.
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, contact a Dynatrace ONE product specialist by clicking the chat button in the upper-right corner of the Dynatrace menu bar. |
ZDTP040S CICS Receive failed. resp:<xx>, resp2:<xx>.
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, contact a Dynatrace ONE product specialist by clicking the chat button in the upper-right corner of the Dynatrace menu bar. |
ZDTP041S zOS SMFid unavailable.
Explanation |
Error retrieving zOS SMFid. |
System action |
CICS code module doesn't initialize. |
User response |
Contact a Dynatrace ONE product specialist by clicking the chat button in the upper-right corner of the Dynatrace menu bar. |
ZDTP043S Unknown AUTHTYPE:<xx>.
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 Purepath. |
User response |
Contact your DB2 administrator. |
ZDTP048S Config block retrieval failed. rc:<xx>.
Explanation |
CICS code module could not find the configuration data with sensor settings. |
System action |
CICS code module doesn't initialize. |
User response |
Contact a Dynatrace ONE product specialist by clicking the chat button in the upper-right corner of the Dynatrace menu bar. |
ZDTP049S Config block not found.
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. |
ZDTP050S DTAX Enable failed. rc:<xx>.
Explanation |
Couldn't enable CICS code module. |
System action |
CICS code module doesn't initialize successfully. |
User response |
Contact a Dynatrace ONE product specialist by clicking the chat button in the upper-right corner of the Dynatrace menu bar. |
ZDTP051S ZDTAGT Copyright Info not found.
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 |
Contact a Dynatrace ONE product specialist by clicking the chat button in the upper-right corner of the Dynatrace menu bar. |
ZDTP054S Turn ON Trace Hooks failed with rc: @@
Explanation |
Couldn't enable Trace hook. |
System action |
Trace hook is not installed. |
User response |
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. |
ZDTP055S Turn OFF Trace Hooks failed with rc: @@
Explanation |
Couldn't disable trace hook. |
System action |
Trace hook is not installed. |
User response |
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. |
ZDTP057S Getmain failed for DSA area
Explanation |
Storage allocation for DSA area has failed. |
System action |
Dynatrace hooks are not enabled. |
User response |
Check CICS log and correct the problem. |
ZDTP058S DSASTK address is Zero can not free GWA: @@
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. |
ZDTP059S Freemain failed for DSA area @@
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, contact a Dynatrace ONE product specialist by clicking the chat button in the upper-right corner of the Dynatrace menu bar. |
ZDTP060S Invalid ICE value, resetting to 5
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. |
ZDTP061S This upgrade requires a CICS restart
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. |
ZDTP063S Turn OFF LE Hook failed with rc: <xx>
Explanation |
Couldn't disable LE hook. |
System action |
LE sensor is not turned off, CICS code module continues to monitor LE events. |
User response |
Contact a Dynatrace ONE product specialist by clicking the chat button in the upper-right corner of the Dynatrace menu bar. |
ZDTP065S Disable EXITALL failed
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. 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. |
ZDTP001W Please update PLT, INITPARM and RDO to ZDTPLT.
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. |
ZDTP002W Extract Exit failed. resp:<xx>, resp2:<xx>, rcode:<xx>.
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. 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. |
ZDTP003W zDC <name> and GWA unavailable.
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. 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. |
ZDTP004W zDC <zDC Name> unavailable.
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. 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. |
ZDTP005W Config block retrieval failed. Attempt re-retrieval during ICE.
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. 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. |
ZDTP008W Too many configuration parameters to display.
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 |
ZDTP010W Temporary LE sensor enable failed
Explanation |
Couldn't enable LE sensor. |
System action |
CICS code module doesn't monitor LE events. |
User response |
Contact a Dynatrace ONE product specialist by clicking the chat button in the upper-right corner of the Dynatrace menu bar. |
ZDTP011W Temporary LE sensor disable failed
Explanation |
Couldn't disable LE sensor. |
System action |
CICS code module continues to monitor LE events which might cause overhead. |
User response |
Contact a Dynatrace ONE product specialist by clicking the chat button in the upper-right corner of the Dynatrace menu bar. |
ZDTP001I DTAX User Command: PING.
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 |
ZDTP002I DTAX User Command: DISABLE.
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 |
ZDTP004I DTAX User Command: CONF.
Explanation |
User issued a DTAX CONF command. |
System action |
Display the active CICS Sensor configuration in the DTAX panel. |
User response |
None |
ZDTP005I DTAX User Command: ENABLE.
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 |
ZDTP009I INIT failed during PLT. Trying to reconnect...
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 |
ZDTP010I Screen size unavailable.
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 |
ZDTP011I DISABLE TRUE(ZDTAGTxx) with ENTRYNAME(ZDTAGENT).
Explanation |
The exit program ZDTAGTxx associated with entryname ZDTAGENT is disabled. xx represents the CTS version. |
System action |
None |
User response |
None |
ZDTP012I ENABLE TRUE(ZDTAGTxx) with ENTRYNAME(ZDTAGENT).
Explanation |
The exit program ZDTAGTxx associated with entryname ZDTAGENT is enabled. xx represents the CTS version. |
System action |
None |
User response |
None |
ZDTP014I START TRUE(ZDTAGTxx) with ENTRYNAME(ZDTAGENT).
Explanation |
Start the user exit ZDTAGENT associated with the exit program ZDTAGTxx . |
System action |
None |
User response |
None |
ZDTP019I Config block retrieved successfully.
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 |
ZDTP021I CICS Sensors updated.
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 |
ZDTP022I Inquire DB2Conn failed. resp:<xx>, resp2:<xx>, rcode:<xx>.
Explanation |
EXEC CICS INQUIRE DB2CONN has failed. |
System action |
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. |
ZDTP024I Trace Hook is being enabled
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 |
ZDTP025I Trace Hook is being disabled
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 |
ZDTP026I Temporary LE sensor is enabled
Explanation |
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. |
System action |
None this is for information only. |
User response |
None |
ZDTP029I DTAX User Command: LEENAB
Explanation |
User issued a DTAX LEENAB command to turn on the LE sensor. |
System action |
LE sensor is turned on temporarily. CICS code module starts monitoring LE dynamic calls. |
User response |
None |
ZDTP030I DTAX Status:V.R PLT-PTF AGT-PTF TRUE-STS XP RMI-STS ZDC-NAME AGT-ID ).
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 |
ZDTP131I Install of Soap Hook Completed Return Code: xxxx
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. Contact a Dynatrace ONE product specialist by clicking the chat button in the upper-right corner of the Dynatrace menu bar. |
ZDTP132I Removal of SOAP Hook Completed Return Code: xxxx
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. Contact a Dynatrace ONE product specialist by clicking the chat button in the upper-right corner of the Dynatrace menu bar. |
ZDTP133I Install of MRO Hook Completed Return Code: xxxx
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. Contact a Dynatrace ONE product specialist by clicking the chat button in the upper-right corner of the Dynatrace menu bar. |
ZDTP134I Removal of MRO Hook Completed Return Code: xxxx
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. Contact a Dynatrace ONE product specialist by clicking the chat button in the upper-right corner of the Dynatrace menu bar. |
ZDTP135I Install of ERM Hook Completed Return Code: xxxx
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. Contact a Dynatrace ONE product specialist by clicking the chat button in the upper-right corner of the Dynatrace menu bar. |
ZDTP136I Removal of ERM Hook Completed Return Code: xxxx
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. Contact a Dynatrace ONE product specialist by clicking the chat button in the upper-right corner of the Dynatrace menu bar. |
ZDTP137I Install of PL1 Hook Completed Return Code: xxxx
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. Contact a Dynatrace ONE product specialist by clicking the chat button in the upper-right corner of the Dynatrace menu bar. |
ZDTP138I Removal of PL1 Hook Completed Return Code: xxxx
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. Contact a Dynatrace ONE product specialist by clicking the chat button in the upper-right corner of the Dynatrace menu bar. |
ZDTP139I Install of <COBOL routine> Hook Completed Return Code: xxxx
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. Contact a Dynatrace ONE product specialist by clicking the chat button in the upper-right corner of the Dynatrace menu bar. |
ZDTP140I Removal of COBOL Hook Completed Return Code: xxxx
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. Contact a Dynatrace ONE product specialist by clicking the chat button in the upper-right corner of the Dynatrace menu bar. |
IMS Code Module system messages
ZDTI032W Recovery routine entered.
Explanation |
The IMS code module's ABEND recovery routine was invoked by RTM. |
System action |
The ABEND recovery process continues. |
User response |
Contact a Dynatrace ONE product specialist by clicking the chat button in the upper-right corner of the Dynatrace menu bar. |
ZDTI033W Successful ABEND recovery, agent disabled.
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 |
Contact a Dynatrace ONE product specialist by clicking the chat button in the upper-right corner of the Dynatrace menu bar. |
ZDTI034E Unable to obtain dynamic storage.
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. Contact a Dynatrace ONE product specialist by clicking the chat button in the upper-right corner of the Dynatrace menu bar. |
ZDTI035W Retry not permitted, must percolate.
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 |
Contact a Dynatrace ONE product specialist by clicking the chat button in the upper-right corner of the Dynatrace menu bar. |
ZDTI036W ZDTIIInn zzzzzzzz yyyymmdd hh.mm VER vv.rr.mm ABEND at offset xxxxxx.
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. Contact a Dynatrace ONE product specialist by clicking the chat button in the upper-right corner of the Dynatrace menu bar. |
ZDTI037W ZDTIIInn zzzzzzzz yyyymmdd hh.mm VER vv.rr.mm ABEND offset N/A, no SDWA provided.
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 |
Contact a Dynatrace ONE product specialist by clicking the chat button in the upper-right corner of the Dynatrace menu bar. |
ZDTI038W Recovery routine of recovery routine entered.
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 |
Contact a Dynatrace ONE product specialist by clicking the chat button in the upper-right corner of the Dynatrace menu bar. |