z/OS code module messages

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 contact support.

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 contact support.

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 support. 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 is shown in the message.
SYSTEM ACTION	Execution terminates.
USER RESPONSE	Examine the return and reason codes or supply this message to support. 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 support. 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 support. 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 support. Try to and 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 support. Enter the ISPF zDC control system and 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 support. 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 support.

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 is not processed.
SYSTEM ACTION	The command is ignored and processing continues.
USER RESPONSE	Reenter a valid command if possible. If the command was valid, refer this problem to support.

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

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

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 in order to activate ARM processing.

ZDC040I @@ DEREGISTERED FOR AUTOMATIC RESTART

EXPLANATION	This message indicates that an IXCARM has been issued in order for the server to go to a normal end of job.
SYSTEM ACTION	Processing continues.
USER RESPONSE	None.

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.

ZDC049I THE FOLLOWING MODULES ARE LOADED INTO PRIVATE STORAGE

EXPLANATION	This message is printed in the SYSPRINT data set and indicates that all modules named next via ZDC009I messages were loaded into the private area of zDC.
SYSTEM ACTION	Processing continues.
USER RESPONSE	None.

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 is already active and is already marked as the default subsystem.
SYSTEM ACTION	zDC execution ends.
USER RESPONSE	Only one zDC subsystem at a time may be marked as the default. Change the parameter specification of this zDC to indicate DEFAULT(NO) and reexecute 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 the 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 joblog 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 support.

ZDC065I zDC INITIALIZATION SUCCESSFUL. RETCODE=00/00 @@

EXPLANATION	This message is written to SYSPRINT indicating that initialization of zDC has been successful.
SYSTEM ACTION	Processing continues.
USER RESPONSE	None.

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

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 joblog 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 if the queue reaches 100%. This message first displays when the queue reaches 75% and it re-displays at each five percent interval. When queue drops below 75% this message no longer displays. 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 support.

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 call support.

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 call support.

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 call support.

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 call support.

ZDC078W QUERT.STAWXXX UNEXPECTED @@ DISPATCH DELAY @@ @@ @@ @@)

EXPLANATION	This message is written to SYSPRINT indicating that the zDC appears to be getting insufficent processor service to handle messages in a timely fashion.
SYSTEM ACTION	Processing continues.
USER RESPONSE	There are 2 formats of the message: {QueRt.StaWDGp Unexpected GP dispatch delay} {QueRt.StaWZSp Unexpected ZIIP dispatch delay} followed by 4 hex words. 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. E.g.: 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. The message will display at most once every 10 minutes (Default). An unexpected delay defaults to .25 sec - e.g. 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. (e.g. 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.

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.

ZDC101I END OF SYSIN PARAMETER LISTING TRANBUF-Megabytes=@@

EXPLANATION	This message indicates that the //SYSIN parameters specified by the customer have all been previously listed.
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 reexecute 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 joblog 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,

ZDC105E ILLOGICAL SEQUENCE OF COMMENT CONTROL CHARACTERS

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 reexecute zDC.

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 reexecute 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 reexecute 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 reexecute 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 the international character $ # or @. The first character must be a letter.
SYSTEM ACTION	zDC execution ends.
USER RESPONSE	Correct the SUBSYSTEM_ID parameter and reexecute 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 reexecute 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 reexecute 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 reexecute 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. Reexecute 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 is LOG_INITIAL(CLOSED). Specify all the other parameters for logging that are applicable to your SMS environment, and also specify LOG_INITIAL(CLOSED). You can dynamically start logging using the specified parameters if the need arises. With the log in a CLOSED state no system resources are consumed.
SYSTEM ACTION	zDC execution ends
USER RESPONSE	Correct the LOG_INITIAL parameter and reexecute 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 reexecute 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 reexecute 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 reexecute 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 reexecute 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 reexecute zDC.

ZDC134E LOG_DATACLASS PARAMETER IS INVALID

EXPLANATION	The LOG_DATACLASS parameter must specify a 1- to 8- character name for the data class SMS parameter that is defined in your installation for the log data set.
SYSTEM ACTION	zDC execution ends.
USER RESPONSE	Correct the LOG_DATACLASS parameter and reexecute 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 reexecute 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 reexecute 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 reexecute 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 reexecute 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 reexecute 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 dows not 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 Kiloby 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) - 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 DEPRICATED

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. E.g. ZDCDISPATCHDELAYRPTM(15) reports delays at most every 15 minutes. Note if no exceptions occur, no warning is reported. 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 reexecute 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 reexecute the zDC.

ZDC207E ZEDC_COMPRESS MUST BE SMALLER THAN TCP_BUFFER

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 reexecute 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 reexecute 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 reexecute 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) - 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 remote agent is required. The remote agent isn't specified in the DTAGTCMD parameter.
SYSTEM ACTION	zDC is terminated
USER RESPONSE	Add zremoteagent= to DTAGTCMD resubmit zDC.

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.

ZDC220I FIXED COMMON STORAGE - SQA: @@ ESQA: @@

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.

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

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 parameter DTPIPEPATH, DTCHDIR, DTAGTCMD, or DTLOG is 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 reexecute zDC.

ZDC951I CICS property update too frequent, under 30sec., discarded

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.

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% that new messages is not 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().

ZDC953I ZIIP_ENABLE requires zremoteagent=, ZIIP_ENABLE NO forced

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.

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

ZDC955L Dynatrace zLocal agent connected to Dynatrace Server ZDC-Job/ID: @@/@@

EXPLANATION	zLocal agent has connected thru the zRemote agent to the Dynatrace server.
SYSTEM ACTION	Informational, processing continues.
USER RESPONSE	No action required.

ZDC956E Dynatrace zLocal agent disconnected from Dynatrace Server ZDC-Job/ID:@@/@@

EXPLANATION	zLocal agent has disconnected from the Dynatrace server.
SYSTEM ACTION	Informational, processing continues.
USER RESPONSE	If this is not planned, investigate the outage.

ZDC957I Dynatrace Check Agent Mapping. Capture Events disabled for xxxx iAdk. Diag:xxxxxxxx

EXPLANATION	Ignore if expected, otherwise check System Profile in Dynatrace client UI.
SYSTEM ACTION	Informational, processing continues.
USER RESPONSE	No action required.

ZDC958I Dynatrace INIT completed, ZDC AgentId received ZDC-Job/ID:@@/@@)

EXPLANATION	ZDC has completed sending INIT msg and received an AgentId response.
SYSTEM ACTION	Informational, processing continues.
USER RESPONSE	No action required.

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 joblog for additional error messages, correct them if possible. If still unresolved, refer this problem to support.

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 agent.
SYSTEM ACTION	Processing terminates.
USER RESPONSE	Check joblog for additional error messages, correct them if possible. If still unresolved, refer this problem to support.

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 joblog for additional error messages, correct them if possible. If still unresolved, refer this problem to support.

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 joblog for additional error messages, correct them if possible. If still unresolved, refer this problem to support.

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 joblog for additional error messages, correct them if possible. If still unresolved, refer this problem to support.

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 joblog for additional error messages, correct them if possible. If still unresolved, refer this problem to support.

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 joblog for additional error messages, correct them if possible. If still unresolved, refer this problem to support.

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 joblog for additional error messages, correct them if possible. If still unresolved, refer this problem to support.

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 joblog for additional error messages, correct them if possible. If still unresolved, refer this problem to support.

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 joblog for additional error messages, correct them if possible. If still unresolved, refer this problem to support.

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 joblog for additional error messages, correct them if possible. If still unresolved, refer this problem to support.

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 joblog for additional error messages, correct them if possible. If still unresolved, refer this problem to support.

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 joblog for additional error messages, correct them if possible. If still unresolved, refer this problem to support.

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 joblog for additional error messages, correct them if possible. If still unresolved, refer this problem to support.

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 agent. 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. Support 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. Support may ask that system parameters be changed to cause these messages.
SYSTEM ACTION	Informational, processing continues.
USER RESPONSE	Informational, processing continues.

DTAX system 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 Agent is not enabled.
User Response	Determine why the CICS region is unable to provide storage for the DTAX transaction. If the problem persists contact support.

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 Agent 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 Agent is disabled.
User Response	Determine why the CICS region is unable to provide storage for the DTAX transaction. If the problem persists contact support.

ZDTP004S ZDTDCCAL final block send failed. rc:<xx>.

Explanation	Message transfer from CICS Agent to zDC failed.
System Action	CICS Agent operation continues but with missing nodes in the PurePath.
User Response	Contact support.

ZDTP005S START DTAX ICE failed.

Explanation	The EXEC CICS START command used to initiate the DTAX ICE transaction in 5 minutes interval failed.
System Action	N/A
User Response	Examine the more detailed message in the appropriate CICS joblog to look at the precise EIBRESP code that indicates why this EXEC CICS START command failed. If the problem persists, contact support.

ZDTP006S Inquire MQCONN <QMGR Name> returned with resp:<xx> resp2:<xx>.

Explanation	EXEC CICS INQUIRE for MQ Connection information 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 support.

ZDTP008S GETMAIN PLT Workarea failed.

Explanation	Storage allocation for PLT workarea failed.
System Action	The PLT program terminates and the CICS Agent 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 Agent is disabled.
User Response	Contact support.

ZDTP010S Turn ON RMI Hook failed with rc: <xx>.

Explanation	RMI hook initialization failed.
System Action	CICS Agent not initialized successfully.
User Response	Contact support.

ZDTP011S Turn OFF RMI Hook failed with rc: <xx>.

Explanation	Disabling RMI hook failed.
System Action	CICS Agent not disabled successfully.
User Response	Contact support.

ZDTP012S GWA Storage unavailable.

Explanation	Global work area storage for PLT program is unavailable.
System Action	Hooks are not initialized successfully.
User Response	Contact support.

ZDTP013S SOAP hook <nn> failed with rc: <xx>.

Explanation	SOAP Hook enable/disable failed.
System Action	Hook operation failed.
User Response	Contact support.

ZDTP014S LE hook <nn> failed with rc: <xx>.

Explanation	LE Hook enable/disable failed.
System Action	Hook operation failed.
User Response	Contact support.

ZDTP015S MRO hook <nn> failed with rc: <xx>.

Explanation	MRO Hook enable/disable failed.
System Action	Hook operation failed.
User Response	Contact support.

ZDTP016S ZDTHKIDR failed with rc: <xx>.

Explanation	Hook operation failed.
System Action	CICS Agent not initialized successfully.
User Response	Contact support.

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 Server, Collector and zRemote Agent are up and running. If not, start the service that is down. If the problem persists, contact support.

ZDTP018S CONF block allocation failed.

Explanation	Storage allocation failed for config block.
System Action	CICS Agent not initialized 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 failed for message buffer.
System Action	CICS Agent not initialized successfully.
User Response	Determine why the CICS region is unable to provide storage for the DTAX transaction.

ZDTP020S Get CICS Applid failed. resp:<xx>, resp2:<xx>, rcode:<xx>.

Explanation	EXEC CICS ASSIGN for APPLID retrieval failed.
System Action	CICS Applid not displayed in DTAX screen and in log messages.
User Response	Determine the cause of the problem from resp and resp2 codes.

ZDTP021S Get STARTCODE failed. resp:<xx>, resp2:<xx>, rcode:<xx>.

Explanation	EXEC CICS ASSIGN for program startcode retrieval failed.
System Action	CICS Agent not initialized successfully.
User Response	Determine the cause of the problem from resp and resp2 codes.

ZDTP022S CICS DELAY failed. resp:<xx>, resp2:<xx>, rcode:<xx>.

Explanation	EXEC CICS DELAY failed.
System Action	N/A
User Response	Determine the cause of the problem from resp and resp2 codes.

ZDTP023S Inquire DB2Entry failed. resp:<xx>, resp2:<xx>, rcode:<xx>.

Explanation	EXEC CICS INQUIRE DB2ENTRY failed.
System Action	CICS Agent operation continues.
User Response	Determine the cause of the problem from resp and resp2 codes. If the problem persists, contact support.

ZDTP024S CICS Agent could not locate a valid AgentId. Possibly a misconfigured or disconnected zRemote. Please check the zRemote or Server logs.

Explanation	CICS Agent did not get a valid AgentId after initialization.
System Action	CICS Agent disabled.
User Response	Check for error messages in zRemote or Server logs. If the Collector/Server is down, start the services.

ZDTP025S Inquire System failed. resp:<xx>, resp2:<xx>, rcode:<xx>.

Explanation	EXEC CICS INQUIRE SYSTEM for CICS version retrieval failed.
System Action	By default CICS Agent 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 support.

ZDTP026S Inquire Program failed. resp:<xx>, resp2:<xx>, rcode:<xx>.

Explanation	EXEC CICS INQUIRE PROGRAM failed.
System Action	CICS Agent operation continues.
User Response	Determine the cause of the problem from resp and resp2 codes. If the problem persists, contact support.

ZDTP027S Disable Exit program failed. resp:<xx>, resp2:<xx>, rcode:<xx>.

Explanation	EXEC CICS DISABLE PROGRAM for all exits failed.
System Action	CICS Agent not disabled successfully.
User Response	Determine the cause of the problem from resp and resp2 codes. If the problem persists, contact support.

ZDTP028S Disable RMI Exit failed. resp:<xx>, resp2:<xx>, rcode:<xx>.

Explanation	EXEC CICS DISABLE PROGRAM for RMI exit failed.
System Action	RMI exit not disabled successfully.
User Response	Determine the cause of the problem from resp and resp2 codes. If the problem persists, contact support.

ZDTP029S START Exit failed. resp:<xx>, resp2:<xx>, rcode:<xx>.

Explanation	EXEC CICS ENABLE START failed for XPCREQC/XRMIIN/XRMIOUT exit.
System Action	Exits not started successfully.
User Response	Determine the cause of the problem from resp and resp2 codes. If the problem persists, contact support.

ZDTP030S FREEMAIN failed. resp:<xx>, resp2:<xx>, rcode:<xx>.

Explanation	EXEC CICS FREEMAIN failed.
System Action	Global Work Area for PLT program FREEMAIN failed.
User Response	Determine the cause of the problem from resp and resp2 codes. If the problem persists, contact support.

ZDTP031S Enable Exit failed. resp:<xx>, resp2:<xx>, rcode:<xx>.

Explanation	EXEC CICS ENABLE PROGRAM for enabling exits failed.
System Action	CICS Agent exits not enabled successfully.
User Response	Determine the cause of the problem from resp and resp2 codes. If the problem persists, contact support.

ZDTP032S STOP Exit failed. resp:<xx>, resp2:<xx>, rcode:<xx>.

Explanation	EXEC CICS DISABLE stop for exits failed.
System Action	CICS Agent exits not stopped successfully.
User Response	Determine the cause of the problem from resp and resp2 codes. If the problem persists, contact support.

ZDTP033S Cancel ReqID failed. resp:<xx>, resp2:<xx>, rcode:<xx>.

Explanation	EXEC CICS CANCEL REQID failed.
System Action	DTAX ICE transaction not cancelled.
User Response	Determine the cause of the problem from resp and resp2 codes. If the problem persists, contact support.

ZDTP034S Inquire ReqID failed. resp:<xx>, resp2:<xx>, rcode:<xx>.

Explanation	EXEC CICS INQUIRE REQID failed.
System Action	DTAX ICE transaction not started successfully.
User Response	Determine the cause of the problem from resp and resp2 codes. If the problem persists, contact support.

ZDTP035S GETMAIN failed. resp:<xx>, resp2:<xx>, rcode:<xx>.

Explanation	EXEC CICS GETMAIN for Global Work Area failed.
System Action	Global Work Area for PLT program not allocated. CICS Agent not initialized successfully.
User Response	Determine the cause of the problem from resp and resp2 codes. If the problem persists, contact support.

ZDTP036S START DTAX ICE failed. resp:<xx>, resp2:<xx>, rcode:<xx>.

Explanation	EXEC CICS START 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 support.

ZDTP037S LOAD Agent failed. resp:<xx>, resp2:<xx>, rcode:<xx>.

Explanation	EXEC CICS LOAD PROGRAM for ZDTAGTxx module failed.
System Action	ZDTAGTxx PTF and build date not printed in the log messages.
User Response	Determine the cause of the problem from resp and resp2 codes. If the problem persists, contact support.

ZDTP038S LOAD ZDTSOAPH failed. resp:<xx>, resp2:<xx>, rcode:<xx>.

Explanation	EXEC CICS LOAD PROGRAM for ZDTSOAPH module failed.
System Action	ZDTSOAPH PTF and build date not printed in the log messages.
User Response	Determine the cause of the problem from resp and resp2 codes. If the problem persists, contact support.

ZDTP039S Release agent failed. resp:<xx>, resp2:<xx>, rcode:<xx>.

Explanation	EXEC CICS RELEASE PROGRAM for ZDTAGTxx/ZDTSOAPH module failed.
System Action	CICS Agent operation continues.
User Response	Determine the cause of the problem from resp and resp2 codes. If the problem persists, contact support.

ZDTP040S CICS Receive failed. resp:<xx>, resp2:<xx>.

Explanation	EXEC CICS RECEIVE DATA failed.
System Action	User command for DTAX transaction not received and hence not processed successfully.
User Response	Determine the cause of the problem from resp and resp2 codes. If the problem persists, contact support.

ZDTP041S zOS SMFid unavailable.

Explanation	Error retrieving zOS SMFid.
System Action	CICS Agent not initialized.
User Response	Contact support.

ZDTP042S ZDTDCCAL INIT message send failed. rc: <xx>.

Explanation	CICS Agent initialization failed.
System Action	CICS Agent not initialized.
User Response	Contact support.

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.

ZDTP044S ZDTDCCAL Register Connection pool failed. rc:<xx>.

Explanation	Sending DB2 connection pool information from CICS Agent to zDC failed.
System Action	DB2 attachment details in PurePath is empty.
User Response	Contact support.

ZDTP045S ZDTDCCAL Register DLI Connection pool failed. rc:<xx>.

Explanation	Sending DL1 connection pool information from CICS Agent to zDC failed.
System Action	DLI attachment details in PurePath is empty.
User Response	Contact support.

ZDTP046S ZDTDCCAL Message send failed. rc:<xx>.

Explanation	CICS Agent could not send message to zDC.
System Action	No data passed from CICS to zDC.
User Response	Contact support.

ZDTP047S DTAX Transaction definition not found. Disabling dynatrace agent.

Explanation	The RDO definition for DTAX transaction is not found.
System Action	CICS Agent 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.

ZDTP048S Config block retrieval failed. rc:<xx>.

Explanation	CICS Agent could not find the configuration data with sensor settings.
System Action	CICS Agent not initialized.
User Response	Contact support.

ZDTP049S Config block not found.

Explanation	CICS Agent could not find the config block with CICS Sensor settings.
System Action	CICS Agent disabled.
User Response	Check if the CICS Transaction Server sensor is placed in the CICS Agent Mapping.

ZDTP050S DTAX Enable failed. rc:<xx>.

Explanation	CICS Agent Enable failed.
System Action	CICS Agent not initialized successfully.
User Response	Contact support.

ZDTP051S ZDTAGT Copyright Info not found.

Explanation	Could not find the Copyright block in ZDTAGTxx module.
System Action	CICS Agent continues. No PTF/Build date is printed in the zRemote log.
User Response	Contact support.

ZDTP052S Check Agent Mapping if the CICS Transaction Server sensor is placed.

Explanation	Configuration block with the CICS Sensor information is not found.
System Action	CICS Agent is disabled.
User Response	Check if the CICS Transaction Server sensor is placed in the CICS Agent Mapping.

ZDTP053S Disabling CICS Agent.

Explanation	This message is an extention of ZDTP052S.
System Action	CICS Agent is disabled.
User Response	Follow ZDTP052S.

ZDTP054S Turn ON Trace Hooks failed with rc: @@

Explanation	Trace hook enable failed.
System Action	Trace hook not installed.
User Response	Look in CICS log for problems. If nothing contact support.

ZDTP055S Turn OFF Trace Hooks failed with rc: @@

Explanation	Trace hook disable failed.
System Action	Trace hook not installed.
User Response	Look in CICS log for problems. If nothing contact support.

ZDTP056S DSASTK address is not NULL -logic error

Explanation	Bad address for DSA storage.
System Action	Dynatrace hooks not enabled.
User Response	CICS getmain failed check CICS logs and correct problem.

ZDTP058S DSASTK address is Zero can not free GWA: @@

Explanation	Bad address for DSA storage free.
System Action	No attempt to freemain storage.
User Response	This is usually not a problem as Dynatrace code module usually just didn't get any storage for this configuration.

ZDTP059S reemain failed for DSA area @@

Explanation	Bad address for DSA storage free from CICS chain.
System Action	No attempt to freemain storage.
User Response	The storage chain is broken or corrupt if this repeats contact support.

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	Restart CICS when you can to pick up new version.
User Response	Restart CICS when you can to pick up new code module versions.

ZDTP060S Invalid ICE value, resetting to 5

Explanation	DTAX time value was not in the range of 1 to 5.
System Action	Value is reset to 5.
User Response	If you are changing ICE values in the DTAX transaction make sure it is value 1 to 5 .

ZDTP001W Please update PLT, INITPARM and RDO to ZDTPLT.

Explanation	RDO definition for ZDTPLT with suffix (66/67/68/69/70) 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 Agent is disabled.
System Action	N/A
User Response	Determine the cause of the problem from resp and resp2 codes. If the problem persists, contact support.

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	N/A
User Response	Check if the zDC is up and connected to zRA. If the problem persists, contact support.

ZDTP004W zDC <zDC Name> unavailable.

Explanation	There was no zDC available for CICS Agent to connect to.
System Action	CICS Agent is disabled.
User Response	Start zDC and check if the zDC connects successfully to zRA. If the problem persists contact support.

ZDTP005W Config block retrieval failed. Attempt re-retrieval during ICE.

Explanation	CICS Agent could not retrieve CICS Sensor configuration block.
System Action	DTAX transaction attempts to retreive CICS Sensor configuration block in the next 5 minutes interval.
User Response	Check if the CICS Agent is successfully enabled in the next 5 minutes interval. If the problem persists contact support.

ZDTP006W DTAX ICE is out of range 1 - 5 minutes. Forcing ICE to 5 minutes.

Explanation	DTAX ICE command was issued with an invalid value.
System Action	DTAX transaction sets the ICE value to the default 5 minutes.
User Response	If you would like to change the DTAX ICE value enter a value from one to five.

ZDTP001I DTAX User Command: PING.

Explanation	User issued a DTAX PING command.
System Action	Check if the connection exists between the z/OS CICS Agent and the zRemote Agent.
User Response	N/A

ZDTP002I DTAX User Command: DISABLE.

Explanation	User issued a DTAX DISABLE command.
System Action	Disable all the exits used by CICS Agent and terminate the 5 minutes DTAX cycle
User Response	N/A

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	N/A

ZDTP005I DTAX User Command: ENABLE.

Explanation	User issued a DTAX ENABLE command.
System Action	CICS Agent registers with the collection system. On successful connection, respective EXITs and Hooks are enabled.
User Response	N/A

ZDTP006I ZDTPLT[CPLT] Compiled on mm dd yyyy hh:mm:ss.

Explanation	This message is displayed in zRemote log file when the CICS Agent connects during CICS Startup. This message gives ZDTPLT compilation and version information.
System Action	N/A
User Response	N/A

ZDTP007I ZDTAGT <PTF> <Build Date> <Build Time> VER <Product Release> <CICS Version>.

Explanation	This message is logged in zRemote log file when the CICS Agent connects during CICS Startup. This message gives CICS Agent module (ZDTAGT) compilation and version information.
System Action	N/A
User Response	N/A

ZDTP008I ZDTSOAPH <PTF> <Build Date> <Build Time> VER <Product Release>.

Explanation	This message is logged in zRemote log file when the CICS Agent connects during CICS Startup. This message gives ZDTSOAPH compilation and version information.
System Action	N/A
User Response	N/A

ZDTP009I INIT failed during PLT. Trying to reconnect...

Explanation	The PLT program is unable to establish connection with the zRemote Agent during PLT time.
System Action	Reconnect attempted during the next DTAX cycle, which starts immediately after the CICS region comes up.
User Response	N/A

ZDTP010I Screen size unavailable.

Explanation	There was a problem in retrieving the screen attributes.
System Action	Screen attributes are defaulted to Screen Width=80, Screen Height=24.
User Response	N/A

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	N/A
User Response	N/A

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	N/A
User Response	N/A

ZDTP013I ENABLE Exit program(ZDTAGTxx) with Exit([exit name]).

Explanation	Enable the global exit point specified by [exit name] associated with the ZDTAGTxx exit.
System Action	N/A
User Response	N/A

ZDTP014I START TRUE(ZDTAGTxx) with ENTRYNAME(ZDTAGENT).

Explanation	Start the user exit ZDTAGENT associated with the exit program ZDTAGTxx.
System Action	N/A
User Response	N/A

ZDTP015I START Exit program(ZDTAGTxx) with Exit([exit name]).

Explanation	Start the global exit point specified by [exit name] associated with the exit program ZDTAGTxx.
System Action	N/A
User Response	N/A

ZDTP016I STOP Exit program(ZDTAGTxx) and all associated exits.

Explanation	Stop and disable all the exit points associated with the exit ZDTAGTxx.
System Action	N/A
User Response	N/A

ZDTP017I DISABLE Exit program(ZDTAGTxx) with Exit([exit name]).

Explanation	Disable the global exit point [exit name] associated with the exit ZDTAGTxx.
System Action	N/A
User Response	N/A

ZDTP019I Config block retrieved successfully.

Explanation	Indicates 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 Agent is initialized.
User Response	N/A

ZDTP020I Active Sensors: <TX | MQ | DB2 | DB2R | SOAP | CTG | DB2Fetch | DLI | DLIR | LE>.

Explanation	Indicates the CICS Sensors that are placed and active.
System Action	N/A
User Response	N/A

ZDTP021I CICS Sensors updated.

Explanation	Indicates that the CICS Sensors have been updated and the CICS Agent honored the changes during DTAX 5 minutes cycle.
System Action	N/A
User Response	N/A

ZDTP022I Inquire DB2Conn failed. resp:<xx>, resp2:<xx>, rcode:<xx>.

Explanation	EXEC CICS INQUIRE DB2CONN failed.
System Action	CICS Agent 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 support.

ZDTP023I DTAX ICE interval set to: @@ minute(s).

Explanation	DTAX ICE value was changed.
System Action	None this is for information only.
User Response	None this is for information only.

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 support

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 support

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 support

ZDTI035W Retry not permitted, must percolate.

Explanation	The z/OS system does not 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 support

ZDTI036W ZDTIIInn zzzzzzzz yyyymmdd hh.mm VER vv.rr.mm ABEND at offset xxxxxx.

Explanation	An ABEND occured at offset xxxxxx in the IMS Code Module module ZDTIIInn, where nn corresponds to the IMS version (for example, 12, 13, 14). The remaining fields describe the maintenance level of the IMS Code Module 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 support

ZDTI037W ZDTIIInn zzzzzzzz yyyymmdd hh.mm VER vv.rr.mm ABEND offset N/A, no SDWA provided.

Explanation	An ABEND occured in the IMS Code Module module ZDTIIInn, where nn corresponds to the IMS version (for example, 12, 13, 14). The remaining fields describe the maintenance level of the IMS Code Module 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 support

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 support