z/OS code module messages
The zDC subsystem, CICS code module, IMS code module, and z/OS Java code module can issue the following types of system message.
zDC system messages
Explanation | This informational message indicates that initialization of zDC has started or ended. The subsystem ID and the version of the product are displayed. |
System action | Processing continues. |
User response | None |
Explanation | At zDC system startup the was an attempt to load all the processing modules into storage. This load was unsuccessful for the module named ( |
System action | zDC terminates. |
User response | Ensure that the |
Explanation | This message follows |
System action | zDC terminates. |
User response | Save the information in this message if you have to contact your systems programmer or Dynatrace ONE. Please contact a Dynatrace ONE product specialist by selecting the chat button in the upper-right corner of the Dynatrace menu bar. |
Explanation | This message indicates that the attempt to load the module named in the message into extended common storage has failed because there is not enough available storage to hold the module. |
System action | zDC terminates. |
User response | Increase the amount of common storage, specifically subpool 241, and start zDC again. |
Explanation | At zDC system startup there was an attempt to load all the processing modules into storage. The |
System action | zDC terminates. |
User response | Ensure that the |
Explanation | This message follows |
System action | zDC terminates. |
User response | Save the information in this message if you have to contact your systems programmer or Dynatrace ONE. Please contact a Dynatrace ONE product specialist by selecting the chat button in the upper-right corner of the Dynatrace menu bar. |
Explanation | This message indicates that the 4-character subsystem ID you specified in the |
System action | zDC terminates. |
User response | Ensure that the subsystem ID you have specified is unique in your system. Then restart zDC or stop the instance of zDC that holds this name. |
Explanation | This message indicates that the attempt to obtain storage for the subsystem control block has failed. There is not enough storage above the line in extended CSA subpool 241 for these blocks. |
System action | zDC terminates. |
User response | Increase the amount of extended CSA subpool 241 storage and restart zDC. |
Explanation | This message is displayed only at zDC startup. It names the columns shown below in multiple message numbers |
System action | Processing continues. |
User response | None |
Explanation | This message lists one module loaded by zDC. See the |
System action | Processing continues. |
User response | None |
Explanation | This message is displayed on the system console by the zDC dump routines. It names the abend code. |
System action | Execution terminates. |
User response | Prepare the dump for examination by your systems staff or for transmission to Dynatrace ONE. Please contact a Dynatrace ONE product specialist by selecting the chat button in the upper-right corner of the Dynatrace menu bar. Re-execute zDC. |
Explanation | This message is displayed on the system console by the zDC dump routines. It indicates that the attempt to obtain a system dump has failed. The return and reason code for the failure are shown in the message. |
System action | Execution terminates. |
User response | Examine the return and reason codes or supply this message to Dynatrace ONE. Please contact a Dynatrace ONE product specialist by selecting the chat button in the upper-right corner of the Dynatrace menu bar. Re-execute zDC. |
Explanation | This message is the title for all SDUMPX macros issued by zDC. This title indicates the abend code that caused the dump to be taken. |
System action | Execution terminates. |
User response | Ensure that the dump is preserved and can be given to your systems programming staff or Dynatrace ONE. Please contact a Dynatrace ONE product specialist by selecting the chat button in the upper-right corner of the Dynatrace menu bar. Re-execute zDC. |
Explanation | This message indicates that a non-zero return code has resulted from a VSAM zDC log request. The name of the request is contained in the message. |
System action | The log task terminates but execution of zDC continues. |
User response | Examine the subsequent messages, which contain detailed information about the nature of the error. Keep this information for your systems programming staff or for Dynatrace ONE. Please contact a Dynatrace ONE product specialist by selecting the chat button in the upper-right corner of the Dynatrace menu bar. Try to and re-attach and re-open the log (MVS command: |
Explanation | This message contains the value of the VSAM RPL feedback word following a VSAM PUT to the log data set. |
System action | The log task terminates but execution of zDC continues. |
User response | Examine the subsequent messages, which contain detailed information about the nature of the error. Keep this information for your systems programming staff or for Dynatrace ONE. Please contact a Dynatrace ONE product specialist by selecting the chat button in the upper-right corner of the Dynatrace menu bar. Try to re-attach and re-open the log (MVS command: |
Explanation | This message contains the value of the VSAM ACB error flag following a VSAM OPEN or CLOSE of the log data set. |
System action | The log task terminates but execution of zDC continues. |
User response | Examine the subsequent messages, which contain detailed information about the nature of the error. Keep this information for your systems programming staff or for Dynatrace ONE. Please contact a Dynatrace ONE product specialist by selecting the chat button in the upper-right corner of the Dynatrace menu bar.. Enter the ISPF zDC control system. Then re-attach and re-open the log. |
Explanation | This message indicates that an abend has occurred at the displacement shown into the SRB routine named |
System action | Execution terminates. |
User response | If a dump is produced, save it for your systems staff or for transmission to Dynatrace ONE. Please contact a Dynatrace ONE product specialist by selecting the chat button in the upper-right corner of the Dynatrace menu bar. Re-execute zDC. |
Explanation | This message indicates that a |
System action | Execution terminates. |
User response | Report this condition to your systems programmer who may want to increase the amount of extended CSA storage in the system. |
Explanation | This message indicates that the initialization routines have failed. It also shows the return and reason codes describing this failure. |
System action | zDC execution terminates. |
User response | Examine the SYSPRINT data set for any other messages that may be relevant to the failure. Please contact a Dynatrace ONE product specialist by selecting the chat button in the upper-right corner of the Dynatrace menu bar. |
Explanation | This message confirms that the STOP command entered by an operator has been accepted by zDC and end of job processing has commenced. |
System action | Execution terminates. |
User response | None |
Explanation | This message confirms that the MODIFY command entered by an operator has been received by zDC and is processing. Any errors encountered during parsing or execution of the command are indicated later. |
System action | Execution continues. |
User response | None |
Explanation | This message contains a copy of the entire command entered by the operator in the console. Only the first 120 bytes of the command are displayed. |
System action | Execution continues. |
User response | None |
Explanation | This message indicates that the ECB for TCPSP subtask is busy and unavailable to receive the shutdown request. |
System action | Execution terminates. |
User response | If a dump is produced, save it for your systems staff or for transmission to Dynatrace ONE. Please contact a Dynatrace ONE product specialist by selecting the chat button in the upper-right corner of the Dynatrace menu bar. Re-execute zDC. |
Explanation | The command you just entered in the operator console was invalid and wasn't processed. |
System action | The command is ignored and processing continues. |
User response | Re-enter a valid command if possible. If the command was valid, refer this problem to Dynatrace ONE. Please contact a Dynatrace ONE product specialist by selecting the chat button in the upper-right corner of the Dynatrace menu bar. |
Explanation | This message indicates that you have selected ARM processing and this is the first time the element named in this message has been armed. This means the execution is not due to an automatic restart. |
System action | Processing continues. |
User response | None |
Explanation | This message indicates that this zDC has been automatically restarted by the system. The reason code indicates whether the JCL or START command has been changed (RSNCD=108) or has not been changed (RSNCD=104). |
System action | Processing continues. |
User response | None |
Explanation | An attempt to issue IXCARM macro has resulted in a return code greater than 4. This indicates that the request did not complete. The actual return and reason codes are shown in this message. |
System action | Processing continues but without ARM support. |
User response | See the z/OS MVS Sysplex Services Reference for a complete list of the possible return and reason codes. Correct any environmental errors or report this problem to Dynatrace ONE. Please contact a Dynatrace ONE product specialist by selecting the chat button in the upper-right corner of the Dynatrace menu bar. |
Explanation | An attempt to issue |
System action | Processing continues but without ARM support. |
User response | See the z/OS MVS Sysplex Services Reference for a complete list of the possible return and reason codes. Correct any environmental errors or report this problem to a Dynatrace ONE product specialist by selecting the chat button in the upper-right corner of the Dynatrace menu bar. |
Explanation | An attempt to issue IXCARM macro has resulted in a return code indicating that ARM support is not available on this system, or it may be available but stopped. |
System action | Processing continues but without ARM support. |
User response | See the z/OS MVS Sysplex Services Reference for a complete list of the possible return and reason codes. You may need to issue the operator command |
Explanation | This message indicates that an |
System action | Processing continues. |
User response | None |
Explanation | This message is printed in the |
System action | Processing continues. |
User response | None |
Explanation | This message is printed in the |
System action | Processing continues. |
User response | None |
Explanation | This informational message indicates the name and release level on which this zDC is running. |
System action | Processing continues. |
User response | None |
Explanation | This informational message indicates the name of the LPAR on which this zDC is running and the name of the operating system on which this zDC is running. |
System action | Processing continues. |
User response | None |
Explanation | This message indicates that during the process of establishing a new zDC subsystem on this LPAR, a previous subsystem named in the message was already active and marked as the default subsystem. |
System action | zDC execution ends. |
User response | Only one zDC subsystem at a time can be marked as the default. Change the parameter specification of this zDC to indicate 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 |
Explanation | This message is written to SYSPRINT indicating that the user ID you specified in |
System action | Processing continues. |
User response | None |
Explanation | This message is written to |
System action | Processing continues. |
User response | None |
Explanation | This message is written to |
System action | Processing continues but without the log. |
User response | Either grant the user ID under which zDC is running ACCESS(ALTER) to the log data set or supply a user ID that has this access level. Note that the log data set must be defined as a generic entity in order to pass the RACROUTE used in zDC. |
Explanation | This message is written to |
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 |
Explanation | This message is written to |
System action | zDC terminates. |
User response | Please contact a Dynatrace ONE product specialist by selecting the chat button in the upper-right corner of the Dynatrace menu bar. |
Explanation | This message is written to SYSPRINT indicating that initialization of zDC has been successful. |
System action | Processing continues. |
User response | None |
Explanation | This message is written to |
System action | zDC terminates. |
User response | If
If |
Explanation | This message is written to |
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 |
Explanation | This message indicates that the queue is filling. New internal events are not accepted once the queue reaches 100%. This message first displays when the queue reaches 75% and it re-displays at each 5% interval. When the queue drops below 75%, this message is no longer displayed. This message appears on the system console as well as in the SYSPRINT data set. |
System action | Execution continues. |
User response | Please contact a Dynatrace ONE product specialist by selecting the chat button in the upper-right corner of the Dynatrace menu bar. |
Explanation | This message indicates that the |
System action | The dump is created but without a symptom record. |
User response | None |
Explanation | This message indicates that the process to create an WLM enclave has not been successful. The function name is shown in the message along with the return and reason codes from execution of this function. This is a warning message only because execution of zDC continues. See below. |
System action | zDC execution continues but all processing is performed in task mode and the enclave SRB is not dispatched. Hence there is no execution on any zIIP. |
User response | Report this message to your systems programmer who may need to contact Dynatrace ONE. Please contact a Dynatrace ONE product specialist by selecting the chat button in the upper-right corner of the Dynatrace menu bar. |
Explanation | This message indicates that the process to create an WLM enclave has been successful and zDC is a member of the enclave named in the message. |
System action | Processing continues. |
User response | None |
Explanation | This message indicates that the process to delete an WLM enclave has not been successful. The function name is shown in the message along with the return and reason codes from execution of this function. |
System action | zDC execution ends. |
User response | Report this message to your systems programmer who may need to Dynatrace ONE. Please contact a Dynatrace ONE product specialist by selecting the chat button in the upper-right corner of the Dynatrace menu bar. |
Explanation | This message indicates that the enclave SRB has failed to execute correctly. If the RETCODE in this message is |
System action | zDC execution ends. |
User response | Report this message to your systems programmer who may need to Dynatrace ONE. Please contact a Dynatrace ONE product specialist by selecting the chat button in the upper-right corner of the Dynatrace menu bar. |
Explanation | The three codes in this message correspond to the |
System action | zDC execution ends. |
User response | Report this message to your systems programmer who may need to Dynatrace ONE. Please contact a Dynatrace ONE product specialist by selecting the chat button in the upper-right corner of the Dynatrace menu bar. |
Explanation | This message is written to |
System action | Processing continues. |
User response | There are 2 formats of the message followed by 4 hex words:
GP is general processor delay, while ZIIP is IBM's Systems Integrated Information Processor. For example: 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: zDC parm: 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 NO can cause ZIIP eligible work to be delayed if GP processors are available. |
Explanation | This message indicates that and internal release function didn't complete properly. |
System action | Processing continues. |
User response | If the issue persists, save the information in this message and contact your systems programmer or Dynatrace ONE. Please contact a Dynatrace ONE product specialist by selecting the chat button in the upper-right corner of the Dynatrace menu bar. |
Explanation | This message indicates that the 4-character subsystem ID you specified in the |
System action | zDC terminates. |
User response | Ensure that the subsystem ID you have specified is unique on your system then restart zDC. |
Explanation | This message indicates that the |
System action | Processing continues. |
User response | None |
Explanation | This message indicates that the |
System action | Processing continues. |
User response | None |
Explanation | During the parsing of the |
System action | zDC execution ends. |
User response | Correct the parameter in error and re-execute zDC. |
Explanation | The attempt to open the |
System action | zDC execution ends. |
User response | Ensure that the |
Explanation | Comment control characters are "/" to begin a comment and "/" to end a comment. These must be paired; one of each. All statements between this pair are treated as a comment. This message indicates that the pairing of these control sequences is not correct. |
System action | zDC execution ends. |
User response | Correct the comment pairing error and re-execute zDC. |
Explanation | The |
System action | zDC execution ends. |
User response | Correct the keyword in the |
Explanation | The |
System action | zDC execution ends. |
User response | Add the SUBSYSTEM_ID parameter to the |
Explanation | The |
System action | zDC execution ends. |
User response | Add the |
Explanation | You have specified |
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 |
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 ( |
System action | zDC execution ends. |
User response | Correct the |
Explanation | The |
System action | zDC execution ends. |
User response | Correct the |
Explanation | The |
System action | zDC execution ends. |
User response | Correct the |
Explanation | The EVENT_WAIT parameter can only specify If this parameter is omitted |
System action | zDC execution ends. |
User response | Correct the |
Explanation | The |
System action | zDC execution ends. |
User response | Either correct the user ID parameter or omit it entirely. Re-execute zDC. |
Explanation | The If you omit this parameter or specify |
System action | zDC execution ends. |
User response | Correct the |
Explanation | The |
System action | zDC execution ends. |
User response | Correct the |
Explanation | The |
System action | zDC execution ends. |
User response | Correct the |
Explanation | The |
System action | zDC execution ends. |
User response | Correct the |
Explanation | The |
System action | zDC execution ends. |
User response | Correct the |
Explanation | The |
System action | zDC execution ends. |
User response | Correct the |
Explanation | The |
System action | zDC execution ends. |
User response | Correct the |
Explanation | The |
System action | zDC execution ends. |
User response | Correct the |
Explanation | The |
System action | zDC execution ends. |
User response | Correct the |
Explanation | The Only letters and numbers and the special characters |
System action | zDC execution ends. |
User response | Correct the |
Explanation | The |
System action | zDC execution ends. |
User response | Correct the |
Explanation | The |
System action | zDC execution ends. |
User response | Add the |
Explanation | The |
System action | zDC ends. |
User response | Remove this parameter from the |
Explanation | The |
System action | zDC execution ends. |
User response | Correct the |
Explanation | The |
System action | zDC execution ends. |
User response | Specify a value in the range given. |
Explanation | The |
System action | zDC execution ends. |
User response | Choose a correct value for |
Explanation | The |
System action | zDC execution ends. |
User response | Choose a correct value for |
Explanation | The |
System action | zDC execution ends. |
User response | Choose a correct value for |
Explanation | The |
System action | zDC execution continues. |
User response | Use |
Explanation |
|
System action | zDC execution ends. |
User response | Correct value for |
Explanation |
|
System action | zDC execution ends. |
User response | Correct value for |
Explanation |
|
System action | zDC execution ends. |
User response | Correct value for |
Explanation |
For example, The default is (10) =10Minutes |
System action | zDC execution ends. |
User response | Correct value for |
Explanation | The Smaller blocks will be sent without compression. A null argument may be specified to enable hardware data compression using the 8K default minimum block size. |
System action | zDC execution ends. |
User response | Correct the ZEDC_COMPRESS parameter and re-execute the zDC. |
Explanation | The |
System action | zDC execution ends. |
User response | Correct the |
Explanation | The minimum compression threshold must be smaller than the size of the TCP/IP buffer. |
System action | zDC execution ends. |
User response | Correct one of the parameters and re-execute the zDC. |
Explanation | The minimum interval is 10 (seconds). |
System action | Processing continues. |
User response | Correct the parameter and re-execute the zDC. |
Explanation | The minimum interval is 10 (seconds). |
System action | Processing continues. |
User response | Correct the parameter and re-execute the zDC. |
Explanation | This informational message indicates that the TERMAPI macro was successfully executed to terminate TCP/IP communications. |
System action | Processing continues. |
User response | None |
Explanation | The |
System action | zDC execution ends. |
User response | Choose a correct value for |
Explanation | A zRemote code module parameter is required. The zRemote code module properties such as host and port are not specified in the |
System action | zDC is terminated. |
User response | Add |
Explanation | The TCP_BUFFER parameter must be in range from 8k to 256k. If less than 8k is specified, 8k is used. If more than 256k is specified, 256k is used. |
System action | Processing continues. |
User response | Correct the TCP_BUFFER parameter for next ZDC execution. |
Explanation | This informational message indicates that termination processing has started for this zDC. |
System action | Termination processing continues. |
User response | None |
Explanation | This informational message is followed by messages that show the number of bytes of storage allocated in each of the designated areas. These numbers may only be approximate as dynamic storage areas are not included in them. |
System action | Processing continues. |
User response | None |
Explanation | The number of bytes of private zDC storage that is allocated long term is shown in this message. This number may only be approximate as dynamic storage areas are not included. Storage allocated both over and under the 16M line are included in this number. |
System action | Processing continues. |
User response | None |
Explanation | The number of bytes of subpool 241 (pageable common) storage that has been allocated for the duration of zDC execution. |
System action | Processing continues. |
User response | None |
Explanation | The number of bytes of subpool 245 (fixed common) storage that has been allocated for the duration of zDC execution. |
System action | Processing continues. |
User response | None |
Explanation | The number of pages in subpool 241 that have had the PGSER PROTECT macro issued against them. This message displays only if you have specified |
System action | Processing continues. |
User response | None |
Explanation | Validation routines invoked to ensure that each message to the zLocal is valid has detected an error in the data. |
System action | If logging is active, the event is logged. This message is written to the user's JOBLOG and the event is discarded. |
User response | Please contact a Dynatrace ONE product specialist by selecting the chat button in the upper-right corner of the Dynatrace menu bar. |
Explanation | Generally, these are internal diagnostic messages issued when the |
System action | Processing continues. |
User response | None |
Explanation | The parameters |
System action | zDC execution ends. |
User response | Correct the parameter and re-execute zDC. |
Explanation | There is a limit on how frequently the internal tables that contain CICS properties can be updated. The current limit is 30 seconds. |
System action | Informational, processing continues. |
User response | Re-apply the update later. |
Explanation | This message indicates that the queue is filling and you should be aware that, if it reaches 100%, new messages won't be sent to the zLocal, possibly causing distribute trace corruption. This message first displays when the queue reaches 70% and re-displays at five percent increments. When utilization drops below 70%, this message no longer displays. Note that this message appears on the system console as well as in the |
System action | Execution continues. |
User response | Monitor these messages carefully.
|
Explanation | ZIIP enablement requires remote agent option. |
System action | Informational, processing continues. |
User response | ZIIP enablement requires both the zremoteagent= in the DTABGCMT command line and ZIIP_ENABLE(YES) in the zDC SYSIN parameters. |
Explanation | Dynatrace parameter |
System action | Informational, processing continues. |
User response | Remove the parameter or code allowed values. |
Explanation | zLocal code module has connected though the zRemote code module to the Dynatrace server. |
System action | Informational, processing continues. |
User response | None |
Explanation | zLocal code module has disconnected from the Dynatrace server. |
System action | Informational, processing continues. |
User response | If this is not planned, investigate the outage. |
Explanation | Ignore if expected, otherwise check Settings > Server-side service monitoring > Deep monitoring > Troubleshooting. |
System action | Informational, processing continues. |
User response | None |
Explanation | ZDC has completed sending INIT msg and received an AgentId response. |
System action | Informational, processing continues. |
User response | None |
Explanation | ZDC could not find the V4 IP address in the SMO. Verify your zLocal is current. |
System action | Informational, processing continues. |
User response | Confirm zLocal verion is current. |
Explanation | This message is written to the |
System action | Processing terminates. |
User response | Check job log for additional error messages, correct them if possible. If still unresolved, refer this problem to Dynatrace ONE. Please contact a Dynatrace ONE product specialist by selecting the chat button in the upper-right corner of the Dynatrace menu bar. |
Explanation | This message is written to the SYSPRINT and Oper. Check that the DTAGTCMD parameter references an accessible and executable OneAgent. |
System action | Processing terminates. |
User response | Check job log for additional error messages, correct them if possible. If still unresolved, refer this problem to Dynatrace ONE. Please contact a Dynatrace ONE product specialist by selecting the chat button in the upper-right corner of the Dynatrace menu bar. |
Explanation | This message is written to the |
System action | Processing terminates. |
User response | Check job log for additional error messages, correct them if possible. If still unresolved, refer this problem to Dynatrace ONE. Please contact a Dynatrace ONE product specialist by selecting the chat button in the upper-right corner of the Dynatrace menu bar. |
Explanation | This message is written to the |
System action | Processing terminates. |
User response | Check job log for additional error messages, correct them if possible. If still unresolved, refer this problem to Dynatrace ONE product specialist by clicking the chat button in the upper-right corner of the Dynatrace menu bar. |
Explanation | This message is written to the |
System action | Processing terminates with a dump. |
User response | Check job log for additional error messages, correct them if possible. If still unresolved, refer this problem to Dynatrace ONE. Please contact a Dynatrace ONE product specialist by selecting the chat button in the upper-right corner of the Dynatrace menu bar. |
Explanation | This message is written to the |
System action | Processing terminates with a dump. |
User response | Check job log for additional error messages, correct them if possible. If still unresolved, refer this problem to Dynatrace ONE product specialist by clicking the chat button in the upper-right corner of the Dynatrace menu bar. |
Explanation | This message is written to the |
System action | Processing terminates with a dump. |
User response | Check why the OMVS address space is not operational. Restart OMVS or delay zDC startup until OMVS is ready. |
Explanation | This message is written to the |
System action | Processing terminates with a dump. |
User response | Check job log for additional error messages, correct them if possible. If still unresolved, refer this problem to Dynatrace ONE. Please contact a Dynatrace ONE product specialist by selecting the chat button in the upper-right corner of the Dynatrace menu bar. |
Explanation | This message is written to the |
System action | Processing terminates with a dump. |
User response | Check job log for additional error messages, correct them if possible. If still unresolved, refer this problem to Dynatrace ONE. Please contact a Dynatrace ONE product specialist by selecting the chat button in the upper-right corner of the Dynatrace menu bar. |
Explanation | This message is written to the |
System action | Processing terminates with a dump. |
User response | Check job log for additional error messages, correct them if possible. If still unresolved, refer this problem to Dynatrace ONE. Please contact a Dynatrace ONE product specialist by selecting the chat button in the upper-right corner of the Dynatrace menu bar. |
Explanation | This message is written to the |
System action | Processing terminates with a dump. |
User response | Check job log for additional error messages, correct them if possible. If still unresolved, refer this problem to Dynatrace ONE. Please contact a Dynatrace ONE product specialist by selecting the chat button in the upper-right corner of the Dynatrace menu bar. |
Explanation | This message is written to the |
System action | Processing terminates with a dump. |
User response | Check job log for additional error messages, correct them if possible. If still unresolved, refer this problem to Dynatrace ONE. Please contact a Dynatrace ONE product specialist by selecting the chat button in the upper-right corner of the Dynatrace menu bar. |
Explanation | This message is written to the |
System action | Processing terminates with a dump. |
User response | Check job log for additional error messages, correct them if possible. If still unresolved, refer this problem to Dynatrace ONE. Please contact a Dynatrace ONE product specialist by selecting the chat button in the upper-right corner of the Dynatrace menu bar. |
Explanation | This message is written to the |
System action | Processing terminates with a dump. |
User response | Check job log for additional error messages, correct them if possible. If still unresolved, refer this problem to Dynatrace ONE. Please contact a Dynatrace ONE product specialist by selecting the chat button in the upper-right corner of the Dynatrace menu bar. |
Explanation | This message is written to the |
System action | Processing terminates with a dump. |
User response | Check job log for additional error messages, correct them if possible. If still unresolved, refer this problem to Dynatrace ONE. Please contact a Dynatrace ONE product specialist by selecting the chat button in the upper-right corner of the Dynatrace menu bar. |
Explanation | This message is written to the |
System action | Informational, processing continues. |
User response | Informational, processing continues. |
Explanation | This message is written to the |
System action | Informational, processing continues. |
User response | Informational, processing continues. |
Explanation | This message is written to the |
System action | Informational, processing continues. |
User response | Informational, processing continues. |
Explanation | This message is written to the |
System action | Informational, processing continues. |
User response | Informational, processing continues. |
Explanation | This message is written to the |
System action | Informational, processing continues. |
User response | Informational, processing continues. |
Explanation | This message is written to the |
System action | Informational, processing continues. |
User response | Informational, processing continues. |
Explanation | This message is written to the |
System action | Informational, processing continues. |
User response | If a connection issue, investigate the status of the zRemote code module. Otherwise, informational, processing continues. |
Explanation | This message is written to the |
System action | Informational, processing continues. |
User response | Informational, processing continues. |
Explanation | This message is written to the |
System action | Informational, processing continues. |
User response | Informational, processing continues. |
Explanation | This message is written to the |
System action | Informational, processing continues. |
User response | Informational, processing continues. |
Explanation | This message is written to the |
System action | Informational, processing continues. |
User response | Informational, processing continues. |
DTAX messages
Explanation | The CICS PLT program was unable to allocate a required persistent storage area. |
System action | The PLT program terminates and the CICS code module is not enabled. |
User response | Determine why the CICS region is unable to provide storage for the DTAX transaction. If the problem persists Please contact a Dynatrace ONE product specialist by selecting the chat button in the upper-right corner of the Dynatrace menu bar. |
Explanation | The PLT program was unable to allocate a required Message block storage area. |
System action | The PLT program terminates and the CICS code module is disabled. |
User response | Determine why the CICS region is unable to provide storage for the PLT program. |
Explanation | CICS could not load |
System action | The PLT program terminates and the CICS code module is disabled. |
User response | Determine why the CICS region is unable to provide storage for the DTAX transaction. If the problem persists Please contact a Dynatrace ONE product specialist by selecting the chat button in the upper-right corner of the Dynatrace menu bar. |
Explanation | Message transfer from CICS code module to zDC has failed. |
System action | CICS code module operation continues but with missing nodes in the distributed trace. |
User response | Please contact a Dynatrace ONE product specialist by selecting the chat button in the upper-right corner of the Dynatrace menu bar. |
Explanation | The |
System action | None |
User response | Examine the more detailed message in the appropriate CICS job log to look at the precise EIBRESP code that indicates why this EXEC CICS START command failed. If the problem persists, Please contact a Dynatrace ONE product specialist by selecting the chat button in the upper-right corner of the Dynatrace menu bar. |
Explanation |
|
System action | Missing MQ Queue manager name in CICS attachment details. |
User response | With the help of |
Explanation | Indicates that the Language Environment sensor could not be enabled because zDC is unavailable. |
System action | Language Environment sensor is not enabled. CICS code module doesn't monitor LE dynamic calls. |
User response | Start the zDC for CICS code module to reconnect. |
Explanation | Storage allocation for PLT work area failed. |
System action | The PLT program terminates and the CICS code module is disabled. |
User response | Determine why the CICS region is unable to provide storage for the PLT program. |
Explanation | Persistent storage for PLT program is not found. |
System action | The PLT program terminates and the CICS code module is disabled. |
User response | Please contact a Dynatrace ONE product specialist by selecting the chat button in the upper-right corner of the Dynatrace menu bar. |
Explanation | RMI hook initialization failed. |
System action | CICS code module not initialized successfully. |
User response | Please contact a Dynatrace ONE product specialist by selecting the chat button in the upper-right corner of the Dynatrace menu bar. |
Explanation | Disabling RMI hook failed. |
System action | CICS code module not disabled successfully. |
User response | Please contact a Dynatrace ONE product specialist by selecting the chat button in the upper-right corner of the Dynatrace menu bar. |
Explanation | Global work area storage for PLT program is unavailable. |
System action | Hooks don't initialize successfully. |
User response | Please contact a Dynatrace ONE product specialist by selecting the chat button in the upper-right corner of the Dynatrace menu bar. |
Explanation | SOAP hook enable/disable has failed. |
System action | Hook operation fails. |
User response | Please contact a Dynatrace ONE product specialist by selecting the chat button in the upper-right corner of the Dynatrace menu bar. |
Explanation | Language Environment sensor enable/disable has failed. |
System action | Hook operation fails. |
User response | Please contact a Dynatrace ONE product specialist by selecting the chat button in the upper-right corner of the Dynatrace menu bar. |
Explanation | MRO hook enable/disable has failed. |
System action | Hook operation fails. |
User response | Please contact a Dynatrace ONE product specialist by selecting the chat button in the upper-right corner of the Dynatrace menu bar. |
Explanation | Hook operation has failed. |
System action | CICS code module don't initialize successfully. |
User response | Please contact a Dynatrace ONE product specialist by selecting the chat button in the upper-right corner of the Dynatrace menu bar. |
Explanation | The PLT program is unable to connect to the collection system. |
System action | Execution continues. The PLT program tries to re-connect with the collection system during the next 5 minutes window. |
User response | Check if the zRemote code module is up and running and connected to Dynatrace. If not, start the service that is down. If the problem persists, Please contact a Dynatrace ONE product specialist by selecting the chat button in the upper-right corner of the Dynatrace menu bar. |
Explanation | Storage allocation for config block has failed. |
System action | CICS code module doesn't initialize successfully. |
User response | Determine why the CICS region is unable to provide storage for the DTAX transaction. |
Explanation | Storage allocation for message buffer has failed. |
System action | CICS code module doesn't initialize successfully. |
User response | Determine why the CICS region is unable to provide storage for the DTAX transaction. |
Explanation |
|
System action | CICS Applid is not displayed in DTAX screen and in log messages. |
User response | Determine the cause of the problem from |
Explanation |
|
System action | CICS code module doesn't initialize successfully. |
User response | Determine the cause of the problem from |
Explanation |
|
System action | None |
User response | Determine the cause of the problem from |
Explanation |
|
System action | CICS code module operation continues. |
User response | Determine the cause of the problem from |
Explanation | CICS code module didn't get a valid AgentId after initialization. |
System action | CICS code module is disabled. |
User response | Check for error messages in zRemote log. If the zRemote service is not running, start it. |
Explanation |
|
System action | By default CICS code module for CICS Version 4.2 is loaded. |
User response | Determine the cause of the problem from |
Explanation |
|
System action | CICS code module operation continues. |
User response | Determine the cause of the problem from |
Explanation |
|
System action | CICS code module is not disabled successfully. |
User response | Determine the cause of the problem from |
Explanation |
|
System action | RMI exit is not disabled successfully. |
User response | Determine the cause of the problem from |
Explanation |
|
System action | Exits are not started successfully. |
User response | Determine the cause of the problem from |
Explanation |
|
System action | Global Work Area for PLT program FREEMAIN fails. |
User response | Determine the cause of the problem from |
Explanation |
|
System action | CICS code module exits are not enabled successfully. |
User response | Determine the cause of the problem from |
Explanation |
|
System action | CICS code module exits are not stopped successfully. |
User response | Determine the cause of the problem from |
Explanation |
|
System action |
|
User response | Determine the cause of the problem from |
Explanation |
|
System action |
|
User response | Determine the cause of the problem from |
Explanation |
|
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 |
Explanation |
|
System action | DTAX Interval control transaction is not started every 5 minutes. |
User response | Determine the cause of the problem from |
Explanation |
|
System action |
|
User response | Determine the cause of the problem from |
Explanation |
|
System action |
|
User response | Determine the cause of the problem from |
Explanation |
|
System action | CICS code module operation continues. |
User response | Determine the cause of the problem from |
Explanation |
|
System action | User command for |
User response | Determine the cause of the problem from |
Explanation | Error retrieving zOS SMFid. |
System action | CICS code module doesn't initialize. |
User response | Please contact a Dynatrace ONE product specialist by selecting the chat button in the upper-right corner of the Dynatrace menu bar. |
Explanation | CICS code module initialization has failed. |
System action | CICS code module doesn't initialize. |
User response | Please contact a Dynatrace ONE product specialist by selecting the chat button in the upper-right corner of the Dynatrace menu bar. |
Explanation |
|
System action | Authtype not specified in DB2 attachment data in distributed trace. |
User response | Contact your DB2 administrator. |
Explanation | Sending DB2 connection pool information from CICS code module to zDC has failed. |
System action | DB2 attachment details in distributed trace is empty. |
User response | Please contact a Dynatrace ONE product specialist by selecting the chat button in the upper-right corner of the Dynatrace menu bar. |
Explanation | Sending DL1 connection pool information from CICS code module to zDC has failed. |
System action | DLI attachment details in distributed trace is empty. |
User response | Please contact a Dynatrace ONE product specialist by selecting the chat button in the upper-right corner of the Dynatrace menu bar. |
Explanation | CICS code module could not send message to zDC. |
System action | No data passes from CICS to zDC. |
User response | Please contact a Dynatrace ONE product specialist by selecting the chat button in the upper-right corner of the Dynatrace menu bar. |
Explanation | The RDO definition for DTAX transaction is not found. |
System action | CICS code module not enabled and the PLT program execution terminates. |
User response | Define DTAX transaction for the PLT program. Refer to CICRDO member in SZDTSAMP installation library for sample definition. |
Explanation | CICS code module could not find the configuration data with sensor settings. |
System action | CICS code module doesn't initialize. |
User response | Please contact a Dynatrace ONE product specialist by selecting the chat button in the upper-right corner of the Dynatrace menu bar. |
Explanation | CICS code module could not find the config block with CICS sensor settings. |
System action | CICS code module is disabled. |
User response | Check if the CICS Transaction Server sensor is placed in the CICS code module Mapping. |
Explanation | Couldn't enable CICS code module. |
System action | CICS code module doesn't initialize successfully. |
User response | Please contact a Dynatrace ONE product specialist by selecting the chat button in the upper-right corner of the Dynatrace menu bar. |
Explanation | Could not find the Copyright block in ZDTAGTxx module. |
System action | CICS code module continues. No PTF/Build date is printed in the zRemote log. |
User response | Please contact a Dynatrace ONE product specialist by selecting the chat button in the upper-right corner of the Dynatrace menu bar. |
Explanation | Configuration block with the CICS sensor information is not found. |
System action | CICS code module is disabled. |
User response | Check if the CICS transaction server sensor is placed in the CICS code module mapping. |
Explanation | This message is an extention of |
System action | CICS code module is disabled. |
User response | Follow |
Explanation | Couldn't enable Trace hook. |
System action | Trace hook is not installed. |
User response | Look in CICS log for problems. If nothing, Please contact a Dynatrace ONE product specialist by selecting the chat button in the upper-right corner of the Dynatrace menu bar. |
Explanation | Couldn't disable trace hook. |
System action | Trace hook is not installed. |
User response | Look in CICS log for problems. If nothing, Please contact a Dynatrace ONE product specialist by selecting the chat button in the upper-right corner of the Dynatrace menu bar. |
Explanation | Bad address for DSA storage |
System action | Dynatrace hooks are not enabled. |
User response | CICS getmain failed. Check CICS logs and correct problem. |
Explanation | Storage allocation for DSA area has failed. |
System action | Dynatrace hooks are not enabled. |
User response | Check CICS log and correct the problem. |
Explanation | Bad address for DSA storage free |
System action | No attempt to free main storage. |
User response | This is usually not a problem as Dynatrace code module usually just didn't get any storage for this configuration. |
Explanation | Bad address for DSA storage free from CICS chain. |
System action | No attempt to free main storage. |
User response | The storage chain is broken or corrupt. If this repeats, Please contact a Dynatrace ONE product specialist by selecting the chat button in the upper-right corner of the Dynatrace menu bar. |
Explanation | DTAX time value was not in the range from 1 to 5. |
System action | The value is reset to 5. |
User response | If you are changing ICE values in the DTAX transaction make sure it is value from 1 to 5. |
Explanation | CICS code module has been updated. A CICS restart is required to run the new code. |
System action | None |
User response | Restart CICS when you can to pick up new code module versions. |
Explanation | CICSPlex name not found for the CICS region due to an unexpected error indicated by the error code “xx” |
System action | CICS code module continues initialization. |
User response | None |
Explanation | Couldn't disable Language Environment sensor. |
System action | Language Environment sensor is not turned off, CICS code module continues to monitor LE events. |
User response | Please contact a Dynatrace ONE product specialist by selecting the chat button in the upper-right corner of the Dynatrace menu bar. |
Explanation | Couldn't enable Language Environment sensor. |
System action | CICS code module doesn't monitor LE events. |
User response | Please contact a Dynatrace ONE product specialist by selecting the chat button in the upper-right corner of the Dynatrace menu bar. |
Explanation | Couldn't disable the TRUE and GLUE exits after two consecutive attempts. |
System action | CICS code module might cause an |
User response | Examine CICS log for |
Explanation | CICS code module has detected an unsupported version of CICS. |
System action | CICS code module is disabled. |
User response | Upgrade your CICS region to a version supported by Dynatrace. |
Explanation | Loading of the CICS code module has failed. |
System action | CICS code module is disabled. |
User response | Examine the CICS job output for any other messages that may be relevant to the failure. Please contact a Dynatrace ONE product specialist by selecting the chat button in the upper-right corner of the Dynatrace menu bar. |
Explanation | The |
System action | None. |
User response | Examine the more detailed message in the appropriate CICS job log to look at the precise EIBRESP code that indicates why this EXEC CICS RETRIEVE command failed. Please contact a Dynatrace ONE product specialist by selecting the chat button in the upper-right corner of the Dynatrace menu bar. |
Explanation | The |
System action | None. |
User response | Examine the more detailed message in the appropriate CICS job log to look at the precise EIBRESP code that indicates why this EXEC CICS START command failed. Please contact a Dynatrace ONE product specialist by selecting the chat button in the upper-right corner of the Dynatrace menu bar. |
Explanation | During CICS startup or DTAX command processing, the Agent program was not marked ThreadSafe. ThreadSafe is required for CICS performance. |
System action | Processing is terminated and the CICS region is not setup to run Dynatrace. |
User response | Check that the Dynatrace CICS resource definitions has been added to the CICS region. Sample resource definitions can be found in installation sample dataset member(CICRDO). Please contact a Dynatrace ONE product specialist by selecting the chat button in the upper-right corner of the Dynatrace menu bar. |
Explanation | RDO definition for |
System action | Execution continues. |
User response | Update the RDO definitions for |
Explanation | There was a problem in retrieving the Global Work Area storage for exit program. |
System action | None |
User response | Determine the cause of the problem from |
Explanation | Exits are enabled but there was a problem in retrieving the Global work area because there was no zDC available. |
System action | None |
User response | Check if the zDC is up and connected to zRA. Please contact a Dynatrace ONE product specialist by selecting the chat button in the upper-right corner of the Dynatrace menu bar. |
Explanation | There was no zDC available for CICS code module to connect to. |
System action | CICS code module is disabled. |
User response | Start zDC and check if the zDC connects successfully to zRA. Please contact a Dynatrace ONE product specialist by selecting the chat button in the upper-right corner of the Dynatrace menu bar. |
Explanation | CICS code module could not retrieve CICS Sensor configuration block. |
System action | DTAX transaction attempts to retrieve CICS Sensor configuration block in the next 5 minutes interval. |
User response | Check if the CICS code module is successfully enabled in the next 5 minutes interval. Please contact a Dynatrace ONE product specialist by selecting the chat button in the upper-right corner of the Dynatrace menu bar. |
Explanation |
|
System action | DTAX transaction sets the ICE value to the default 5 minutes. |
User response | If you want to change the default DTAX ICE value, enter a value between 1 to 5. |
Explanation | No CICSplex name is available for the CICS region. |
System action | CICS code module continues initialization. |
User response | None |
Explanation |
|
System action | Configuration settings are truncated in the DTAX display |
User response | None |
Explanation | Check all CICS code module configuration parameters in Dynatrace UI. |
System action | None |
User response | To view all the CICS code module configuration settings, go to Settings > Server-side service monitoring > Deep monitoring > CICS, IMS and MQ monitoring. |
Explanation | Couldn't enable Language Environment sensor. |
System action | CICS code module doesn't monitor Language Environment events. |
User response | Please contact a Dynatrace ONE product specialist by selecting the chat button in the upper-right corner of the Dynatrace menu bar. |
Explanation | Couldn't disable Language Environment sensor. |
System action | CICS code module continues to monitor Language Environment events which might cause overhead. |
User response | Please contact a Dynatrace ONE product specialist by selecting the chat button in the upper-right corner of the Dynatrace menu bar. |
Explanation | Dynatrace CICS code module versions are different. |
System action | None. |
User response | Perform If PLT is older
If CICS code module version is older (
|
Explanation | Invalid minute value entered for the Language Environment sensor. |
System action | None. |
User response | Enter a valid interval, between 1-1000 minutes, to enable the Language Environment sensor. |
Explanation | The Language Environment sensor interval value entered is out of range. |
System action | None. |
User response | Enter a valid interval value between 1-1000 minutes to enable the Language Environment sensor. |
Explanation | User issued a |
System action | Check if the connection exists between the z/OS CICS code module and the zRemote code module. |
User response | None |
Explanation | User issued a |
System action | Disable all the exits used by CICS code module and terminate the 5 minutes DTAX cycle. |
User response | None |
Explanation | User issued a |
System action | Display the active CICS Sensor configuration in the DTAX panel. |
User response | None |
Explanation | User issued a |
System action | CICS code module registers with the collection system. On successful connection, respective EXITs and Hooks are enabled. |
User response | None |
Explanation | This message is displayed in zRemote log file when the CICS code module connects during CICS startup. This message gives ZDTPLT compilation and version information. |
System action | None |
User response | None |
Explanation | This message is logged in zRemote log file when the CICS code module connects during CICS startup. This message gives CICS code module module (ZDTAGT) compilation and version information. |
System action | None |
User response | None |
Explanation | This message is logged in zRemote log file when the CICS code module connects during CICS startup. This message gives ZDTSOAPH compilation and version information. |
System action | None |
User response | None |
Explanation | The PLT program is unable to establish connection with the zRemote code module during PLT time. |
System action | Reconnect attempted during the next DTAX cycle, which starts immediately after the CICS region comes up. |
User response | None |
Explanation | There was a problem in retrieving the screen attributes. |
System action | Screen attributes are defaulted to |
User response | None |
Explanation | The exit program |
System action | None |
User response | None |
Explanation | The exit program ZDTAGTxx associated with entryname ZDTAGENT is enabled. |
System action | None |
User response | None |
Explanation | Enable the global exit point specified by |
System action | None |
User response | None |
Explanation | Start the user exit |
System action | None |
User response | None |
Explanation | Start the global exit point specified by |
System action | None |
User response | None |
Explanation | Stop and disable all the exit points associated with the exit |
System action | None |
User response | None |
Explanation | Disable the global exit point |
System action | None |
User response | None |
Explanation | Indicates that CICS sensor configuration has been retrieved successfully after there was a problem in configuration block access. This message follows after ZDTP049S when the CICS transaction server sensor has been placed. |
System action | CICS code module is initialized. |
User response | None |
Explanation | Indicates the CICS Sensors that are placed and active. |
System action | None |
User response | None |
Explanation | Indicates that the CICS Sensors have been updated and the CICS code module honored the changes during DTAX 5 minutes cycle. |
System action | None |
User response | None |
Explanation | EXEC CICS INQUIRE DB2CONN has failed. |
System action | CICS code module operation continues. No DB2 attachment details provided in the distributed trace. |
User response | Determine the cause of the problem from |
Explanation |
|
System action | None this is for information only. |
User response | None |
Explanation | Indicates that the Trace hook is being turned on in the CICS code module. |
System action | None this is for information only. |
User response | None |
Explanation | Indicates that the Trace hook is being turned off in the CICS code module. |
System action | None this is for information only. |
User response | None |
Explanation | Indicates that the Language Environment sensor has been turned on for the current DTAX ICE interval. Note that the Language Environment sensor will be automatically turned off during the following DTAX ICE cycle. |
System action | None this is for information only. |
User response | None |
Explanation | Indicates that the Language Environment sensor has been automatically turned off at the end of the current ICE interval. |
System action | None this is for information only. |
User response | None |
Explanation | Displays the Start TX sensor setting in Deep Monitoring in the web UI for the CICS regions. |
System action | None: this is only informational. |
User response | None |
Explanation | User issued a |
System action | Language Environment sensor is turned on temporarily. CICS code module starts monitoring LE dynamic calls. |
User response | None |
Explanation | DTAX STATUS console command was issued. This can be used for Automated Operations to see if Dynatrace Hooks/Exits are enabled. Field descriptions:
|
System action | None, this is informational only. |
User response | None |
Explanation | Indicates that the DSA at location |
System action | DSA memory is freed. |
User response | None |
Explanation | CICS code module has completed installing SOAP hook for SOAP request monitoring. Return code 0 indicates successful SOAP hook installation. |
System action | CICS code module is ready to monitor SOAP events with successful SOAP hook installation. |
User response | If the Return code is a non-zero value, SOAP hook installation has failed. Please contact a Dynatrace ONE product specialist by selecting the chat button in the upper-right corner of the Dynatrace menu bar. |
Explanation | CICS code module has completed removing SOAP hook. Return code 0 indicates successful SOAP hook removal. |
System action | CICS code module stops monitoring SOAP events if the SOAP hook has been removed successfully. |
User response | If the Return code is a non-zero value, SOAP hook removal has failed. Please contact a Dynatrace ONE product specialist by selecting the chat button in the upper-right corner of the Dynatrace menu bar. |
Explanation | CICS code module has completed installing MRO hook for multi region call monitoring. Return code 0 indicates successful MRO hook installation. |
System action | CICS code module is ready to monitor MRO events with the successful MRO hook installation. |
User response | If the Return code is a non-zero value, MRO hook installation has failed. Please contact a Dynatrace ONE product specialist by selecting the chat button in the upper-right corner of the Dynatrace menu bar. |
Explanation | CICS code module has completed removing MRO hook. Return code 0 indicates successful MRO hook removal. |
System action | CICS code module stops monitoring MRO events if the MRO hook has been removed successfully. |
User response | If the Return code is a non-zero value, MRO hook removal has failed. Please contact a Dynatrace ONE product specialist by selecting the chat button in the upper-right corner of the Dynatrace menu bar. |
Explanation | CICS code module has completed installing ERM hook for DB2 call monitoring. Return code 0 indicates successful ERM hook installation. |
System action | CICS code module is ready to monitor DB2 calls from the CICS region with the successful ERM hook installation. |
User response | If the Return code is a non-zero value, ERM hook installation has failed. Please contact a Dynatrace ONE product specialist by selecting the chat button in the upper-right corner of the Dynatrace menu bar. |
Explanation | CICS code module has completed removing ERM hook. Return code 0 indicates successful ERM hook removal. |
System action | CICS code module stops monitoring DB2 calls if the ERM hook has been removed successfully. |
User response | If the Return code is a non-zero value, ERM hook removal has failed. Please contact a Dynatrace ONE product specialist by selecting the chat button in the upper-right corner of the Dynatrace menu bar. |
Explanation | CICS code module has completed installing PL1 hook for monitoring PL1 dynamic calls. Return code 0 indicates successful PL1 hook installation. |
System action | CICS code module is ready to monitor PL1 dynamic calls with the successful PL1 hook installation. |
User response | If the Return code is a non-zero value, PL1 hook installation has failed. Please contact a Dynatrace ONE product specialist by selecting the chat button in the upper-right corner of the Dynatrace menu bar. |
Explanation | CICS code module has completed removing PL1 hook. Return code 0 indicates successful PL1 hook removal. |
System action | CICS code module stops monitoring PL1 dynamic calls if the PL1 hook has been removed successfully. |
User response | If the Return code is a non-zero value, PL1 hook removal has failed. Please contact a Dynatrace ONE product specialist by selecting the chat button in the upper-right corner of the Dynatrace menu bar. |
Explanation | CICS code module has completed installing COBOL hooks IGZCFCC, IGZCLNK and IGZXFCAL (indicated by “COBOL routine”) for monitoring COBOL dynamic calls. Return code 0 indicates successful COBOL hooks installation. |
System action | CICS code module is ready to monitor COBOL dynamic calls with the successful COBOL hooks installation. |
User response | If the Return code is a non-zero value, COBOL hook installation has failed. Please contact a Dynatrace ONE product specialist by selecting the chat button in the upper-right corner of the Dynatrace menu bar. |
Explanation | CICS code module has completed removing COBOL hook. Return code 0 indicates successful COBOL hook removal. |
System action | CICS code module stops monitoring COBOL dynamic calls if the COBOL hook has been removed successfully. |
User response | If the Return code is a non-zero value, COBOL hook removal has failed. Please contact a Dynatrace ONE product specialist by selecting the chat button in the upper-right corner of the Dynatrace menu bar. |
IMS code module system messages
Explanation | The IMS code module's ABEND recovery routine was invoked by RTM. |
System action | The ABEND recovery process continues. |
User response | Please contact a Dynatrace ONE product specialist by selecting the chat button in the upper-right corner of the Dynatrace menu bar. |
Explanation | The IMS code module's ABEND recovery process was successful. |
System action | The IMS code module is disabled and the IMS system continues to function. |
User response | Please contact a Dynatrace ONE product specialist by selecting the chat button in the upper-right corner of the Dynatrace menu bar. |
Explanation | The IMS code module's ABEND recovery routine was unable to obtain the dynamic storage required to produce ABEND diagnostics. |
System action | The ABEND recovery process continues but some diagnostic information may not be available. A Software ( |
User response | Run the z/OS EREP utility program to print the Software ( |
Explanation | The z/OS system doesn't allow the IMS code module's ABEND recovery process to continue. |
System action | The recovery process terminates and percolates (returns control to RTM). |
User response | Please contact a Dynatrace ONE product specialist by selecting the chat button in the upper-right corner of the Dynatrace menu bar. |
Explanation | An ABEND occurred at offset |
System action | A Software ( |
User response | Run the z/OS EREP utility program to print the Software (SFT) Error Record associated with the ABEND. Please contact a Dynatrace ONE product specialist by selecting the chat button in the upper-right corner of the Dynatrace menu bar. |
Explanation | An ABEND occurred in the |
System action | The recovery process terminates and percolates (returns control to RTM). |
User response | Please contact a Dynatrace ONE product specialist by selecting the chat button in the upper-right corner of the Dynatrace menu bar. |
Explanation | While recovering from an ABEND in the IMS code module, the recovery routine encountered an ABEND. |
System action | The ABEND recovery process continues but does not attempt to produce further diagnostics. The IMS code module is disabled and the IMS system continues to function. |
User response | Please contact a Dynatrace ONE product specialist by selecting the chat button in the upper-right corner of the Dynatrace menu bar. |
Java code module system messages
Explanation | The ODIN zOS stub is returning a diagnostic code. |
System action | Processing continues. |
User response | Please contact a Dynatrace ONE product specialist by selecting the chat button in the upper-right corner of the Dynatrace menu bar. |
Explanation | The ODIN zOS stub can not find the vendor table. |
System action | Processing fails. |
User response | Restart zDC with a current maintaince level (at least the same as Java-ODIN). Then restart the Java process. |
- Install the zDC subsystem
Set up the z/OS Data Collection subsystem (zDC).
- Manage the CICS code module via DTAX transactions
Manage the CICS code module via DTAX transactions.