Space announcement This documentation space provides the same content as before, but the organization of the content has changed. The content is now organized based on logical branches instead of legacy book titles. We hope that the new structure will help you quickly find the content that you need.

Code Debug Service Provider Messages


The messages in this section are generated by the Code Debug Service Provider.

Codes

Description

DSH4003W Partial SVCDUMP has been taken

Explanation: The Code Debug Service Provider DSHSRVS runtime routine was unable to capture a complete SVCDUMP for the terminating task.

System Action: Code Debug Service Provider DSHSRVS runtime routine unable to capture SVCDUMP.

User Response: Ship the SVCDUMP to BMC only when requested by Code Debug CICS BMC Support.

Module: DSHSRVS

DSH4004W SETLOCK OBTAIN request failed for LOCAL lock RC(##)

Explanation: The Code Debug Service Provider DSHSRVS runtime routine encountered errors during the acquisition of the LOCAL lock. The return_code indicates the exception conditions encountered:

RC 4

The lock was already held by the caller.

RC 8

The conditional obtain process was unsuccessful. The lock is owned by another processor.

System Action: Code Debug Service Provider DSHSRVS runtime routine unable to capture SVCDUMP for the terminating task.

User Response: Contact BMC Support.

Module: DSHSRVS

DSH4005W SDUMPX request failed RC(##) RSN(##)

Explanation: The Code Debug Service Provider DSHSRVS runtime routine encountered errors during the capture of an SVCDUMP. The return_code and reason_code indicates the exception conditions encountered:

RC 8


The system was unable to schedule a dump.


RSN 0

No SVC dump was requested.


RSN 1

An SVC dump was successfully started.


RSN 2

An SVC dump was suppressed because the capture phase of another SVC dump was in progress.


RSN 3

An SVC dump was suppressed by a request by the installation.


RSN 4

An SVC dump was suppressed by a SLIP NODUMP command.


RSN 5

An SVC dump was suppressed because a SYS1.DUMP data set was not available.


RSN 6

An SVC dump was suppressed because an I/O error occurred during the initialization of the SYS1.DUMP data set.


RSN 8

An SVC dump was suppressed because an SRB could not be scheduled to activate the dump tasks in the requested address spaces.


RSN 9

An SVC dump was suppressed because a terminating error occurred in SVC dump before the first dump record was written.


RSN A

An SVC dump was suppressed because a status stop SRB condition was detected.


RSN B

An SVC dump was suppressed by DAE.


RSN 15

The parameter list address is zero.


RSN 16

The parameter list is not a valid SVC or SNAP parameter list.


RSN 17

The caller-supplied data set is not supported.


RSN 18

The start address is greater than or equal to the end address in a storage list.


RSN 19

The caller-supplied header is longer than 100 characters.


RSN 1A

The caller requested a 4K buffer, but did not reserve it.


RSN 1B

A storage list overlaps the 4K buffer


RSN 1C

The caller-supplied DCB is not valid.


RSN 22

The 4K buffer was requested with an SVC dump already in progress.


RSN 25

A non-valid subpool ID was specified in the subpool list.


RSN 28

Part of the parameter list is inaccessible.


RSN 29

The caller-supplied DCB is inaccessible.


RSN 2A

The caller-supplied storage list is inaccessible.


RSN 2B

The caller-supplied header data is inaccessible.


RSN 2C

The caller-supplied ECB is inaccessible.


RSN 2D

The caller’s ASID list is inaccessible.


RSN 2E

The caller’s SUMLIST/SUMLSTA is inaccessible.


RSN 2F

The caller’s SUBPLST list is inaccessible.


RSN 30

The caller’s KEYLIST is inaccessible.


RSN 31

Copies of the SLIP register and PSW are inaccessible.


RSN 32

The caller-supplied SRB is inaccessible.


RSN 33

The version number in the parameter list is not valid.


RSN 34

The caller’s LISTD is inaccessible.


RSN 35

The caller’s SUMLISTL is inaccessible.


RSN 36

The parameter list contains conflicting parameters.


RSN 37

The ID is longer than 50 characters.


RSN 38

The ID is not addressable.


RSN 39

The PSWREGS area is an incorrect length.


RSN 3A

The PSWREGS area is not addressable.


RSN 3B

The symptom record is not valid.


RSN 3C

The symptom record is not addressable.


RSN 3D

The DEB for the caller-supplied DCB is inaccessible.


RSN 3E

SVC dump is already using the maximum amount of virtual storage (as determined by the installation, using the MAXSPACE parameter on the CHNGDUMP command) to process other dumps.


RSN FF

An SVC dump was suppressed for some other unspecified reason.

System Action: Code Debug Service Provider DSHSRVS runtime routine unable to capture SVCDUMP for the terminating task.

User Response: Contact BMC Support.

Module: DSHSRVS

SSX0001I System Authorization Facility is not Active

Explanation: The Code Debug Service Provider subsystem security interface has determined that System Authorization Facility (SAF) is not active.

System Action: All Service Requester address space connection request will be granted.

User Response: Correct problems related to you external security manager.

Module: DBUGSSX

SSX0002I SAF Return Code(SAF RC,RACF RC,RACF RSN)

Explanation: The Code Debug Service Provider subsystem security interface received an invalid response from RACROUTE. The SAF_RC indicates the exception conditions encountered by System Authorization Facility (for an explanation of the RACF_RC and RACF_RSN see you external security manager reference for the RACROUTE interface):

RC 4

Requested function could not be completed.

RC 8

Requested function has failed.

System Action: All Service Requester address space connection requests will be granted.

User Response: Correct problems related to your external security manager.

Module: DBUGSSX

SSX0003I Resource(resource name)

Explanation: The Code Debug Service Provider subsystem security interface resource name for failing RACROUTE request.

System Action: None.

User Response: None.

Module: DBUGSSX

XSP0001E Service Provider requires a minimum operating system release

Explanation: The Code Debug Service Provider utilizes functions found on the minimum operating system and will not properly operate on prior releases of MVS.

System Action: Code Debug Service Provider initialization is terminated.

User Response: see to Prerequisites in the “Planning” section of the Code Debug CICS Installation and Configuration Guide, and upgrade to the minimum supported operating system or above.

Module: DBUGSTC

XSP0002E Service Provider entered in non-authorized state

Explanation: The Code Debug Service Provider was fetched from a non-APF authorized library concatenation.

System Action: Code Debug Service Provider initialization is terminated.

User Response: APF authorize the library, which contains the Code Debug Service Provider, and/or remove non-APF authorized libraries from the STEPLIB concatenation. See the Code Debug CICS Installation and Configuration Guide.

Module: DBUGSTC

XSP0003E Service Provider entered in incorrect execution key

Explanation: The Code Debug Service Provider was entered in a PSW key other than four.

System Action: Code Debug Service Provider initialization is terminated.

User Response: Update the MVS Program Properties Table to include DBUGSTC with an execution key of four. See the section entitled “Task 4.3.3 Define the Code Debug Service Provider Program Properties to MVS” in the Code Debug CICS Installation and Configuration Guide.

Module: DBUGSTC

XSP0004E Service Provider Dynamic Storage Manager initialization error

Explanation: The Code Debug Service Provider DSHSRVS has failed to initialize, R15 contains the return code from the dynamic storage handler and R0 contains the corresponding reason code.

RC 4

Allocation failure for dynamic storage handler.



RSN 4

Insufficient storage is available.


RSN 8

Insufficient central storage to back the request.


RSN C

System cannot page in the page table associated with the storage.

RC 8

Load failure for dynamic storage handler (DSHSRVS).


RC C

Error establishing recovery environment (ESTAE|ESTAEX).


RC 10

Incorrect Address Space Control mode (not Primary).


System Action: Code Debug Service Provider initialization is terminated.

User Response: Choose the appropriate action:

Allocation failures

Increase the amount of storage available to the private area.

Load failures

Resolve errors related to DSHSRVS load.

Recovery errors

Contact BMC Support.

Addressing mode errors

Contact BMC Support.

Module: DBUGSTC

XSP00005I Module "module" has an invalid module header

Explanation: The Code Debug Service Provider has detected an invalid module header during the fetch of module "module". The Code Debug Service Provider APF authorized library has been either damaged or violated.

System Action: Code Debug Service Provider initialization is terminated.

User Response: Contact BMC Support.

Module: DBUGSTC

XSP00006I Module "module" has an invalid release stamp "stamp"

Explanation: The Code Debug Service Provider has detected an invalid release stamp during the fetch of module "module". The Code Debug Service Provider APF authorized library has been either damaged or violated.

System Action: Code Debug Service Provider initialization is terminated.

User Response: Contact BMC Support.

Module: DBUGSTC

XSP00007I Module "module" has an invalid message table header

Explanation: The Code Debug Service Provider has detected an invalid message table header during the fetch of module "module". The Code Debug Service Provider APF authorized library has been either damaged or violated.

System Action: Code Debug Service Provider initialization is terminated.

User Response: Contact BMC Support.

Module: DBUGSTC

XSP00008I Module "module" has an invalid message table name "name"

Explanation: The Code Debug Service Provider has detected an invalid message table name during the fetch of module "module". The Code Debug Service Provider APF authorized library has been either damaged or violated.

System Action: Code Debug Service Provider initialization is terminated.

User Response: Contact BMC Support.

Module: DBUGSTC

XSP0010I Code Debug for CICS Service Provider Release ##.##.##

Explanation: The Code Debug Service Provider release "##.##.##" is initializing.

System Action: None.

User Response: None.

Module: DBUGSTC

XSP0011I Execution parameters:

Explanation: Code Debug Service Provider execution parameters prefix message.

System Action: None.

User Response: None.

Module: DBUGSTC

XSP0012I Execution parameters

Explanation: Code Debug Service Provider execution parameter string.

System Action: None.

User Response: None.

Module: DBUGSTC

XSP0013E Service Provider SYSEVENT TRANSWAP error RC(return_code)

Explanation: The Code Debug Service Provider encountered an error attempting to make the address space non-swappable which is required for cross memory operations. The return_code indicates the exception conditions encountered by MVS as follows:

RC 4

The address space became non-swappable before it could be swapped out.

System Action: Code Debug Service Provider initialization is terminated.

User Response: Restart the Code Debug Service Provider. If the problem persists, contact BMC Support.

Module: DBUGSTC

XSP0021I Subsystem Identifier.... ssid

Explanation: Code Debug Service Provider Subsystem Identifier ssid from the execution parameters.

System Action: None.

User Response: None.

Module: DBUGSTC

XSP0022I Control Pool Size....... size

Explanation: Code Debug Service Provider Control Pool size derived the execution parameters.

System Action: None.

User Response: None.

Module: DBUGSTC

XSP0023I Descriptor Pool Size.... size

Explanation: Code Debug Service Provider Descriptor Pool size from the execution parameters.

System Action: None.

User Response: None.

Module: DBUGSTC

XSP0024I Common Pool Size........ size

Explanation: Code Debug Service Provider Common Pool size from the execution parameters.

System Action: None.

User Response: None.

Module: DBUGSTC

XSP0025I Trace Table Size........ size

Explanation: Code Debug Service Provider internal Trace Table size from the execution parameters.

System Action: None.

User Response: None.

Module: DBUGSTC

XSP0026I Task Thread Limit....... limit

Explanation: Code Debug Service Provider Task Thread limit from the execution parameters.

System Action: None.

User Response: None.

Module: DBUGSTC

XSP0027I Cross Memory Task Limit....... limit

Explanation: Code Debug Service Provider Cross Memory Task Thread limit from the execution parameters.

System Action: None.

User Response: None.

Module: DBUGSTC

XSP0028I CICS SVC Front-End...... svc_number_list

Explanation: Code Debug Service Provider CICS SVC Front-End SVC number list.

System Action: None.

User Response: None.

Module: DBUGSTC

XSP0029I TCP Listener Port …. Portnumber

Explanation: Code Debug Service Provider Subsystem TCP Port Number to listen on, from the execution parameters.

System Action: None.

User Response: None.

Module: DBUGSTC

XSP0030I TPCONFIG Member Name …. Membername

Explanation: Code Debug Service Provider DD statement TPCONFIG specifies a PDS or PDS/E. This is the member name in that data set to open. From the execution parameters.

System Action: None.

User Response: None.

Module: DBUGSTC

XSP0031I Highest supported release = CICS TS version.release (CICS nn.nn.nn)

Explanation: Code Debug Service Provider includes support up through the specified release.

System Action: None.

User Response: None.

Module: DBUGSTC

XSP0097E Initialization aborted due to prior errors

Explanation: Code Debug Service Provider initialization has been aborted due prior errors.

System Action: Code Debug Service Provider initialization is terminated.

User Response: Correct the errors as reported in prior messages.

Module: DBUGSTC

XSP0098E Abend "abend" occurred in Procedure (Function)

Explanation: An abend has been trapped in Procedure during the processing of MVS Function.

System Action: Code Debug Service Provider initialization is terminated.

User Response: Contact BMC Support.

Module: DBUGSTC

XSP0099E Abend "abend" occurred in Procedure offset "offset"

Explanation: An abend has been trapped in Procedure at offset.

System Action: Code Debug Service Provider initialization is terminated.

User Response: Contact BMC Support.

Module: DBUGSTC

XSP0111E Abend "abend" trapped in procedure during Parse of Execute Parameters

Explanation: An abend has been trapped in Procedure during the parse of execute parameters.

System Action: Code Debug Service Provider initialization is terminated.

User Response: Contact BMC Support.

Module: DBUGSTC

XSP0112E Subsystem Identifier parameter is required and is not present

Explanation: The Subsystem Identifier positional parameter is required and is not present.

System Action: Code Debug Service Provider initialization is terminated.

User Response: Correct the Code Debug Service Provider execution parameters and restart the Code Debug Service Provider.

Module: DBUGSTC

XSP0113E Subsystem Identifier parameter syntax error

Explanation: The Subsystem Identifier positional parameter does not conform to the proper syntax.

System Action: Code Debug Service Provider initialization is terminated.

User Response: Correct the Code Debug Service Provider execution parameters and restart the Code Debug Service Provider.

Module: DBUGSTC

XSP0114E Subsystem Identifier parameter "ssid" is invalid

Explanation: The Subsystem Identifier positional parameter ssid is invalid. The Subsystem Identifier should be from one to four (1-4) alphanumeric characters.

System Action: Code Debug Service Provider initialization is terminated.

User Response: Correct the Code Debug Service Provider execution parameters and restart the Code Debug Service Provider.

Module: DBUGSTC

XSP0115E Subsystem Identifier "ssid" is reserved by IBM

Explanation: The Subsystem Identifier positional parameter ssid specified is reserved by IBM.

System Action: Code Debug Service Provider initialization is terminated.

User Response: Correct the Code Debug Service Provider execution parameters and restart the Code Debug Service Provider.

Module: DBUGSTC

XSP0116E Keyword parameter syntax error

Explanation: The keyword execution parameter does not conform to the proper syntax.

System Action: Code Debug Service Provider initialization is terminated.

User Response: Correct the Code Debug Service Provider execution parameters and restart the Code Debug Service Provider.

Module: DBUGSTC

XSP0117E Keyword parameter "keyword" is invalid

Explanation: The Keyword execution parameter keyword is invalid.

System Action: Code Debug Service Provider initialization is terminated.

User Response: Correct the Code Debug Service Provider execution parameters and restart the Code Debug Service Provider.

Module: DBUGSTC

XSP0118E keyword parameter syntax error

Explanation: The keyword parameter does not conform to proper syntax. The keyword parameter either requires an operand value or does not support an operand.

System Action: Code Debug Service Provider initialization is terminated.

User Response: Correct the Code Debug Service Provider execution parameters and restart the Code Debug Service Provider.

Module: DBUGSTC

XSP0119E keyword operator "operator" is invalid

Explanation: The keyword operator "operator" is invalid. Keywords, which require operand values, should be separated with the assignment operator "=".

System Action: Code Debug Service Provider initialization is terminated.

User Response: Correct the Code Debug Service Provider execution parameters and restart the Code Debug Service Provider.

Module: DBUGSTC

XSP0120E keyword operand "operand" is invalid

Explanation: The keyword operand "operand" is invalid. The token type for the keyword operand does not conform to the required syntax.

System Action: Code Debug Service Provider initialization is terminated.

User Response: Correct the Code Debug Service Provider execution parameters and restart the Code Debug Service Provider.

Module: DBUGSTC

XSP0121W keyword operand "operand" is not within bounds

Explanation: The keyword operand "operand" is not within bounds of the minimum and maximum values. The default value for the keyword operand will be used.

System Action: The Subsystem initialization continues.

User Response: Correct the Code Debug Service Provider execution parameters.

Module: DBUGSTC

XSP0122W keyword operand "operand" is a duplicate entry

Explanation: The keyword operand "operand" has already been specified. The duplicate value will be discarded.

System Action: The Subsystem initialization continues.

User Response: Correct the Code Debug Service Provider execution parameters.

Module: DBUGSTC

XSP0123W keyword operand "operand" exceeds sub-operand limit

Explanation: The keyword operand "operand" sub-operand limit has been exceeded. All excessive sub-operand values will be discarded.

System Action: The Subsystem initialization continues.

User Response: Correct the Code Debug Service Provider execution parameters.

Module: DBUGSTC

XSP0124E PORT specified but no MEMBER

Explanation: Execution parameters included PORT, but not MEMBER. If either is used, the other is also required.

System Action: The subsystem initialization continues, but the TCP subtask will not be started.

User Response: Correct the Code Debug Service Provider execution parameters. If the TCP subtask is required, provide the MEMBER parameter on a Service Provider INITTCP command.

Module: DBUGSTC

XSP0125E MEMBER specified but no PORT

Explanation: Execution parameters included MEMBER, but not PORT. If either is used, the other is also required.

System Action: The subsystem initialization continues, but the TCP subtask will not be started.

User Response: Correct the Code Debug Service Provider execution parameters. If the TCP subtask is required, provide the PORT parameter on a Service Provider INITTCP command.

Module: DBUGSTC

XSP0198E Abend "abend" occurred in Procedure (Function)

Explanation: An abend has been trapped in Procedure during the processing of MVS Function.

System Action: Code Debug Service Provider initialization is terminated.

User Response: Contact BMC Support.

Module: DBUGSTC

XSP0199E Abend "abend" occurred in Procedure offset "offset"

Explanation: An abend has been trapped in Procedure at offset.

System Action: Code Debug Service Provider initialization is terminated.

User Response: Contact BMC Support.

Module: DBUGSTC

XSP0301E Subsystem "ssid" is currently active

Explanation: Code Debug Service Provider subsystem "ssid" is currently active on an MVS image. Code Debug Service Provider subsystems must be uniquely named on a single MVS image.

System Action: Code Debug Service Provider initialization is terminated.

User Response: Verify the correct Subsystem Identifier has been specified. If a prior instance of the Code Debug Service Provider has not properly terminated, contact BMC Support.

Module: DBUGSTC

XSP0302E ENQ failure for Queue(queue) Resource(resource) RC(return_code)

Explanation: The Code Debug Service Provider encountered an error during the acquisition of the subsystem name enqueue request to MVS. The return_code indicates the exception conditions encountered by MVS as follows

RC 8

A previous request for control of the same resource has been made for the same task. The task has control of the resource.

RC 14

A previous request for control of the same resource has been made for the same task. The task does not have control of the resource.

RC 18

Environmental error. The limit for the number of concurrent resource requests has been reached. The task does not have control of the resource unless some previous ENQ or RESERVE request caused the task to obtain control of the resource.

System Action: Code Debug Service Provider initialization is terminated.

User Response: Contact BMC Support.

Module: DBUGSTC

XSP0303E Invalid Job Entry Subsystem Communication Table (JEST) at address

Explanation: The Code Debug Service Provider has detected an error in the Job Entry Subsystem Communication Table (JEST) at the specified address. The Code Debug Service Provider cannot locate or create the required Subsystem entry.

System Action: Code Debug Service Provider initialization is terminated.

User Response: Contact BMC Support.

Module: DBUGSTC

XSP0304E JES Subsystem Communications Vector Table (SSCT) at address, Subsystem Name "ssid" (xxxxxxxx)

Explanation: The Code Debug Service Provider has detected an invalid JES Subsystem Communications Vector Table (SSCT) at the specified address for subsystem "ssid". The Code Debug Service Provider can not locate or create the required Subsystem entry.

System Action: Code Debug Service Provider initialization is terminated.

User Response: Contact BMC Support.

Module: DBUGSTC

XSP0305E Invalid Subsystem Communications Vector Table (SSCT) at address, Subsystem Name "ssid" (xxxxxxxx)

Explanation: The Code Debug Service Provider has detected an invalid Subsystem Communications Vector Table (SSCT) at the specified address for subsystem "ssid". The Code Debug Service Provider can not locate or create the required Subsystem entry.

System Action: Code Debug Service Provider initialization is terminated.

User Response: Contact BMC Support.

Module: DBUGSTC

XSP0306E Subsystem entry "ssid" at address is in-use

Explanation: The Code Debug Service Provider has detected the subsystem "ssid" at the specified address is in use.

System Action: Code Debug Service Provider initialization is terminated.

User Response: Verify the correct Subsystem Identifier has been specified. If a prior instance of the Code Debug Service Provider has not properly terminated, contact BMC Support.

Module: DBUGSTC

XSP0307A Subsystem entry "ssid" at address is in-use, reply U to use or A to abend

Explanation: The Code Debug Service Provider has detected the subsystem "ssid" at the specified address is in-use and the OVERRIDE parameter has been specified.

System Action: Code Debug Service Provider initialization is terminated when A is issued. Otherwise, the Code Debug Service Provider will overlay the specified subsystem entry.

User Response: Respond to the operator reply with A or U per Code Debug CICS Customer Support direction only, misuse of the OVERRIDE parameter can result in system damage.

Module: DBUGSTC

XSP0308A Subsystem entry "ssid" at address is not an Code Debug for CICS entry, reply U to use or A to abend

Explanation: The Code Debug Service Provider has detected the subsystem "ssid" at the specified address is not a Code Debug subsystem entry and the OVERRIDE parameter has been specified.

System Action: Code Debug Service Provider initialization is terminated when A is issued. Otherwise, the Code Debug Service Provider will overlay the specified subsystem entry.

User Response: Respond to the operator reply with A or U per Code Debug CICS Customer Support direction only, misuse of the OVERRIDE parameter can result in system damage.

Module: DBUGSTC

XSP0309A Subsystem entry "ssid" at address has an invalid anchor block, reply U to use or A to abend

Explanation: The Code Debug Service Provider has detected the subsystem "ssid" at the specified address has an invalid Code Debug anchor block and the OVERRIDE parameter has been specified.

System Action: Code Debug Service Provider initialization is terminated when A is issued. Otherwise, the Code Debug Service Provider will abandon the anchor block and all related storage areas.

User Response: Respond to the operator reply with A or U per Code Debug CICS Customer Support direction only, misuse of the OVERRIDE parameter can result in system damage.

Module: DBUGSTC

XSP0310E Storage Obtain for Subsystem "ssid" SSCT length(length) failed RC(return_code)

Explanation: The Code Debug Service Provider was unable to obtain storage in MVS subpool 245 for the subsystem "ssid" entry of the specified length. The return_code indicates the exception conditions encountered by MVS as follows:

RC 4

Insufficient storage is available.

RC 8

Insufficient central storage to back the request.

RC C

System cannot page in the page table associated with the storage.

System Action: Code Debug Service Provider initialization is terminated.

User Response: Resolve the shortage of storage in MVS subpool 245 (Common SQA/ESQA) and restart the Code Debug Service Provider. If the problem persists, contact BMC Support.

Module: DBUGSTC

XSP0311I Subsystem "ssid" has been dynamically created (SSAFF Index index)

Explanation: The Code Debug Service Provider has dynamically created the subsystem "ssid" entry with the Subsystem Affinity index value of index.

System Action: None.

User Response: None.

Module: DBUGSTC

XSP0312E Required Module "module" was not found

Explanation: The Code Debug Service Provider can not locate the required module "module" in the STEPLIB library concatenation. The Code Debug Service Provider APF authorized library has been either damaged or violated.

System Action: Code Debug Service Provider initialization is terminated.

User Response: Contact BMC Support.

Module: DBUGSTC

XSP0313E Service Provider Anchor Block has an invalid eyecatcher "eyecatcher" (X'xxxxxxxxxxxxxxxx')

Explanation: The Code Debug Service Provider has detected an invalid eyecatcher during the fetch of Code Debug Anchor Block. The Code Debug Service Provider APF authorized library has been either damaged or violated.

System Action: Code Debug Service Provider initialization is terminated.

User Response: Contact BMC Support.

Module: DBUGSTC

XSP0314E Service Provider Anchor Block has an invalid release stamp "stamp"

Explanation: The Code Debug Service Provider has detected an invalid release stamp during the fetch of Code Debug Anchor Block. The Code Debug Service Provider APF authorized library has been either damaged or violated.

System Action: Code Debug Service Provider initialization is terminated.

User Response: Contact BMC Support.

Module: DBUGSTC

XSP0315E Invalid Address Space Vector Table (ASVT) at address

Explanation: The Code Debug Service Provider has detected an error in the Address Space Vector Table (ASVT) at the specified address. The Code Debug Service Provider can not determine the maximum number of MVS address spaces available.

System Action: Code Debug Service Provider initialization is terminated.

User Response: Contact BMC Support.

Module: DBUGSTC

XSP0316E Storage Obtain for Service Provider Vector Table length(length) failed RC(return_code)

Explanation: The Code Debug Service Provider was unable to obtain storage in MVS subpool 241 for the Code Debug Service Provider Vector Table of the specified length. The return_code indicates the exception conditions encountered by MVS as follows:

RC 4

Insufficient storage is available.

RC 8

Insufficient central storage to back the request.

RC C

System cannot page in the page table associated with the storage.

System Action: Code Debug Service Provider initialization is terminated.

User Response: Resolve the shortage of storage in MVS subpool 241 (Common CSA/ECSA) and restart the Code Debug Service Provider. If the problem persists, contact BMC Support.

Module: DBUGSTC

XSP0317E Storage Release for Service Provider Vector Table address(address) length(length) failed RC(return_code)

Explanation: The Code Debug Service Provider was unable to release storage in MVS subpool 241 for the Code Debug Service Provider Vector Table at the specified address and of the specified length. The return_code indicates the exception conditions encountered by MVS as follows:

RC 4

Not all requested virtual storage was freed.

RC 8

No virtual storage was freed because part of the storage area to be freed is fixed.

System Action: Code Debug Service Provider termination continues.

User Response: Contact BMC Support.

Module: DBUGSTC

XSP0318E Delete error for Service Provider Message Table Token(token)

Explanation: The Code Debug Service Provider was unable to delete the Service Provider Message Table (program manager token "token") from MVS subpool 241. See prior Code Debug Service Provider program manager error message for explanation of error condition.

System Action: Code Debug Service Provider termination continues.

User Response: Contact BMC Support.

Module: DBUGSTC

XSP0319E Delete error for Service Provider Anchor Block Token(token)

Explanation: The Code Debug Service Provider was unable to delete the Service Provider Anchor Block (program manager token "token") from MVS subpool 241. See prior Code Debug Service Provider program manager error message for explanation of error condition.

System Action: Code Debug Service Provider termination continues.

User Response: Contact BMC Support.

Module: DBUGSTC

XSP0398E Abend "abend" occurred in Procedure (Function)

Explanation: An abend has been trapped in Procedure during the processing of MVS Function.

System Action: Code Debug Service Provider initialization is terminated.

User Response: Contact BMC Support.

Module: DBUGSTC

XSP0399E Abend "abend" occurred in Procedure offset "offset"

Explanation: An abend has been trapped in Procedure at offset.

System Action: Code Debug Service Provider initialization is terminated.

User Response: Contact BMC Support.

Module: DBUGSTC

XSP0401I Service Provider initialization started

Explanation: The Code Debug Service Provider address space is initializing.

System Action: None.

User Response: None.

Module: DBUGSTC

XSP0402E ALESERV extract Home for Service Provider failed RC(return_code)

Explanation: The Code Debug Service Provider encountered an error during the processing of an ALESERV EXTRACTH request. The return_code indicates the exception conditions encountered by MVS as follows:

RC 24

Program error. AR 1 contained an ALET of 1 on input or contains an ALET associated with the caller’s PASN-AL.

RC 60

System error. An unexpected error occurred. The request was not completed.

System Action: Code Debug Service Provider initialization is terminated.

User Response: Contact BMC Support.

Module: DBUGSTC

XSP0403E SSAFF Set for Service Provider Affinity Index(index) failed RC(return_code)

Explanation: The Code Debug Service Provider encountered an error during the processing of a SSAFF SET.

System Action: Code Debug Service Provider initialization is terminated.

User Response: Contact BMC Support.

Module: DBUGSTC

XSP0404E TCBTOKEN for Service Provider failed RC(return_code)

Explanation: The Code Debug Service Provider encountered an error during the processing of a TCBTOKEN request. The return_code indicates the exception conditions encountered by MVS as follows:

RC 10

The TCB could not be seeenced.

RC 14

The TCB did not pass the acronym check.

RC 18

The TCB has terminated.

RC 20

An unexpected error occurred.

RC 24

The contents of access register 1, used to address the parameter list, were not valid.

RC 28

The parameter list is not valid.

RC 30

The task is scheduled for termination, but has not yet terminated.

RC 34

The caller is not running in task mode.

System Action: Code Debug Service Provider initialization is terminated.

User Response: Contact BMC Support.

Module: DBUGSTC

XSP0405E Home ASID "asid" for Service Provider address space is invalid

Explanation: The Code Debug Service Provider has determined that the Home ASID "asid" is invalid (asid > ASVTMAXU).

System Action: Code Debug Service Provider initialization is terminated.

User Response: Contact BMC Support.

Module: DBUGSTC

XSP0406E Required Module "module" was not found

Explanation: The Code Debug Service Provider can not locate the required module "module" in the STEPLIB library concatenation. The Code Debug Service Provider APF authorized library has been either damaged or violated.

System Action: Code Debug Service Provider initialization is terminated.

User Response: Contact BMC Support.

Module: DBUGSTC

XSP0407E Service Provider Global Block has an invalid eyecatcher "eyecatcher" (X'xxxxxxxxxxxxxxxx')

Explanation: The Code Debug Service Provider has detected an invalid eyecatcher during the fetch of Code Debug Global Block. The Code Debug Service Provider APF authorized library has been either damaged or violated.

System Action: Code Debug Service Provider initialization is terminated.

User Response: Contact BMC Support.

Module: DBUGSTC

XSP0408E Service Provider Global Block has an invalid release stamp "stamp"

Explanation: The Code Debug Service Provider has detected an invalid release stamp during the fetch of Code Debug Global Block. The Code Debug Service Provider APF authorized library has been either damaged or violated.

System Action: Code Debug Service Provider initialization is terminated.

User Response: Contact BMC Support.

Module: DBUGSTC

XSP0409E Storage Obtain for Trace Table length(length) failed RC(return_code)

Explanation: The Code Debug Service Provider was unable to obtain storage in MVS subpool 241 for the Code Debug Service Provider Trace Table of the specified length. The return_code indicates the exception conditions encountered by MVS as follows:

RC 4

Insufficient storage is available.

RC 8

Insufficient central storage to back the request.

RC C

System cannot page in the page table associated with the storage.

System Action: Code Debug Service Provider initialization is terminated.

User Response: Resolve the shortage of storage in MVS subpool 241 (Common CSA/ECSA) and restart the Code Debug Service Provider. If the problem persists, contact BMC Support.

Module: DBUGSTC

XSP0410I Subsystem Interface initialization started

Explanation: The Code Debug Service Provider subsystem interface is initializing.

System Action: None.

User Response: None.

Module: DBUGSTC

XSP0411I Subsystem Interface Security Module "module" was not found

Explanation: The Code Debug Service Provider cannot locate the subsystem interface security module "module" in the STEPLIB library concatenation. The Code Debug Service Provider will grant all connection requests.

System Action: None.

User Response: This message is purely informational, indicating the absence of the optional security module. If the site does not intend to use the optional module, no action is necessary. If the site does intend to use the exit, review its installation in the STEPLIB of the Service Provider.

Module: DBUGSTC

XSP0412I Subsystem Interface initialization complete

Explanation: The Code Debug Service Provider subsystem interface has successfully initialized.

System Action: None.

User Response: None.

Module: DBUGSTC

XSP0413W Storage Obtain for Hardware Detection Routine Work Area length(length) failed RC(return_code)

Explanation: The Code Debug Service Provider was unable to obtain storage in MVS subpool 253 for the hardware detection routine work area of the specified length. The return_code indicates the exception conditions encountered by MVS as follows:

RC 4

Insufficient storage is available.

RC 8

Insufficient central storage to back the request.

RC C

System cannot page in the page table associated with the storage.

System Action: Code Debug Service Provider initialization continues, hardware exploitation will be suppressed.

User Response: Resolve the shortage of storage in MVS subpool 253 (Private LSQA/ELSQA) and restart the Code Debug Service Provider. If the problem persists, contact BMC Support.

Module: DBUGSTC

XSP0414W Hardware Detection Routine failed RC(return_code)

Explanation: The Code Debug Service Provider Hardware Detection routine did not complete successfully. The return_code indicates the exception conditions encountered as follows:

RC 4

The Hardware Detection routine has been entered in an invalid state (Problem State and/or non-zero PSW Key).

RC 8

An invalid hardware detection work area has been passed to the Hardware Detection routine.

RC 10

An invalid Service Provider anchor block address has been passed to the Hardware Detection routine.

RC 14

The Hardware Detection routine was unable to acquire the CPU lock.

RC 18

The Hardware Detection routine was unable to release the CPU lock.

RC 1C

An abend has been trapped during Hardware Detection routine processing.

System Action: Code Debug Service Provider initialization continues, hardware exploitation will be suppressed.

User Response: Contact BMC Support.

Module: DBUGSTC

XSP0415W Storage Release for Hardware Detection Routine Work Area address(address) length(length) failed RC(return_code)

Explanation: The Code Debug Service Provider was unable to release storage in MVS subpool 253 for the hardware detection routine work area at the specified address and of the specified length. The return_code indicates the exception conditions encountered by MVS as follows:

RC 4

Not all requested virtual storage was freed.

RC 8

No virtual storage was freed because part of the storage area to be freed is fixed.

System Action: Code Debug Service Provider initialization is terminated.

User Response: Contact BMC Support.

Module: DBUGSTC

XSP0416W Delete for Module "module" failed RC(return_code)

Explanation: The Code Debug Service Provider program manager delete service was unable to remove the specified module from MVS storage. The return_code indicates the exception conditions encountered by MVS as follows:

RC 4

Request was not issued for this module, or attempt was made to delete a system module.

System Action: Code Debug Service Provider program manager delete service request is suppressed.

User Response: Contact BMC Support.

Module: DBUGSTC

XSP0417E Storage Obtain for Task Storage Anchor Block Length(length) failed RC(return_code)

Explanation: The Code Debug Service Provider was unable to obtain storage in MVS subpool 129 for the task storage anchor block of the specified length. The return_code indicates the exception conditions encountered by MVS as follows:

RC 4

Insufficient storage is available.

RC 8

Insufficient central storage to back the request.

RC C

System cannot page in the page table associated with the storage.

System Action: Code Debug Service Provider initialization is terminated.

User Response: Contact BMC Support.

Module: DBUGSTC

XSP0418E Storage Release for Task Storage Anchor Block address(address) length(length) failed RC(return_code)

Explanation: The Code Debug Service Provider was unable to release storage in MVS subpool 129 for the task storage anchor block at the specified address and of the specified length. The return_code indicates the exception conditions encountered by MVS as follows:

RC 4

Not all requested virtual storage was freed.

RC 8

No virtual storage was freed because part of the storage area to be freed is fixed.

System Action: Code Debug Service Provider termination continues.

User Response: Contact BMC Support.

Module: DBUGSTC

XSP0420I Resource Manager initialization started

Explanation: The Code Debug Service Provider resource manager interface is initializing.

System Action: None.

User Response: None.

Module: DBUGSTC

XSP0421E RESMGR add for Type(type) failed RC(return_code)

Explanation: The Code Debug Service Provider was unable to register the specified resource manager type (AddrSpc|Task) with MVS. The return_code indicates the exception conditions encountered by MVS as follows:

RC 12

Program error. The caller did not provide the address of a word to contain the token of the new resource manager.

RC 16

Program error. The caller did not provide the resource manager description through the ROUTINE parameter.

RC 20

Program error. The TCB address provided did not represent a valid TCB.

RC 24

Program error. The ASID provided did not represent a valid ASCB.

RC 28

Program error. The request type was not ADD or DELETE.

RC 32

Environmental error. RESMGR was unable to obtain storage for a work area it needed to process the request.

RC 36

Program error. The caller held an incorrect lock.

RC 40

Program error. It is not valid to establish a task resource manager for a specific task that is not in the home address space of the requestor.

RC 44

System error. An unrecoverable error occurred while processing the request.

RC 48

Environmental error. RESMGR was unable to obtain storage to maintain information about RESMGR.

RC 52

Program error. The caller is not authorized to use RESMGR.

RC 56

Environmental error. The TCB was already terminating and no more dynamic resource managers can be established for it.

RC 60

Environmental error. The ASCB was already in termination and no more dynamic resource managers can be established for it.

RC 64

Program error. The TTOKEN parameter specified a task in an address space other than the home address space.

System Action: Code Debug Service Provider initialization is terminated.

User Response: Choose the appropriate action:

Program error

Contact BMC Support.

Environmental error

Resolve the environmental issues and restart the Code Debug Service Provider. If the problem persists, contact BMC Support.

System error

Contact BMC Support.


Module: DBUGSTC

XSP0422I Resource Manager initialization complete

Explanation: The Code Debug Service Provider resource manager interface has successfully initialized.

System Action: None.

User Response: None.

Module: DBUGSTC

XSP0430I Program Call initialization started

Explanation: The Code Debug Service Provider program call interface is initializing.

System Action: None.

User Response: None.

Module: DBUGSTC

XSP0431E AXRES failed RC(return_code)

Explanation: The Code Debug Service Provider was unable to reserve an authorization index.

System Action: Code Debug Service Provider initialization is terminated.

User Response: Restart the Code Debug Service Provider. If the problem persists, contact BMC Support.

Module: DBUGSTC

XSP0432E AXSET for AX(ax) failed RC(return_code)

Explanation: The Code Debug Service Provider was unable to set the home address space to the specified AX.

System Action: Code Debug Service Provider initialization is terminated.

User Response: Restart the Code Debug Service Provider. If the problem persists, contact BMC Support.

Module: DBUGSTC

XSP0433E LXRES failed RC(return_code)

Explanation: The Code Debug Service Provider was unable to reserve a non-system linkage index.

System Action: Code Debug Service Provider initialization is terminated.

User Response: Restart the Code Debug Service Provider. If the problem persists, contact BMC Support.

Module: DBUGSTC

XSP0434E ETCRE failed RC(return_code)

Explanation: The Code Debug Service Provider was unable to create the program call table.

System Action: Code Debug Service Provider initialization is terminated.

User Response: Restart the Code Debug Service Provider. If the problem persists, contact BMC Support.

Module: DBUGSTC

XSP0435I Program Call initialization complete

Explanation: The Code Debug Service Provider program call interface has successfully initialized.

System Action: None.

User Response: None.

Module: DBUGSTC

XSP0440I SVC Front-End initialization started

Explanation: The Code Debug Service Provider SVC Front-End Interface is initializing.

System Action: None.

User Response: None.

Module: DBUGSTC

XSP0441E CICS SVC svc_number validation failed address(address)

Explanation: The Code Debug Service Provider was unable to validate the CICS SVC Front-End interface currently installed.

System Action: Code Debug Service Provider initialization is terminated.

User Response: Contact BMC Support.

Module: DBUGSTC

XSP0442E Storage Obtain for CICS SVC svc_number CDE Length(length) failed RC(return_code)

Explanation: The Code Debug Service Provider was unable to obtain storage in MVS subpool 245 for the CICS SVC Front-End Interface of the specified length. The return_code indicates the exception conditions encountered by MVS as follows:

RC 4

Insufficient storage is available.

RC 8

Insufficient central storage to back the request.

RC C

System cannot page in the page table associated with the storage.

System Action: Code Debug Service Provider initialization is terminated.

User Response: Contact BMC Support.

Module: DBUGSTC

XSP0443E SETLOCK obtain for LOCAL lock failed with RC(return_code)

Explanation: The Code Debug Service Provider CICS Front-End initialization service encountered errors during the acquisition of the LOCAL lock. The return_code indicates the exceptional conditions encountered:

RC 4

The lock was already held by the caller.

RC 8

The conditional obtain process was unsuccessful. The lock is owned by another processor.

System Action: Code Debug Service Provider initialization is terminated.

User Response: Contact BMC Support.

Module: DBUGSTC

XSP0444E SETLOCK obtain for CMS lock failed with RC(return_code)

Explanation: The Code Debug Service Provider CICS Front-End initialization service encountered errors during the acquisition of the CMS lock. The return_code indicates the exceptional conditions encountered:

RC 4

The lock was already held by the caller.

RC 8

The conditional obtain process was unsuccessful. The lock is owned by another processor.

System Action: Code Debug Service Provider initialization is terminated.

User Response: Contact BMC Support.

Module: DBUGSTC

XSP0445E LPA Queue CDE add for CICS SVC svc_number failed address(address)

Explanation: The Code Debug Service Provider CICS Front-End initialization service encountered errors during the add processing for the CICS SVC Front-End module onto the LPA Queue.

System Action: Code Debug Service Provider initialization is terminated.

User Response: Contact BMC Support.

Module: DBUGSTC

XSP0446E ENQ failure for Queue(queue) Resource(resource) RC(return_code)

Explanation: The Code Debug Service Provider CICS SVC Front-End initialization service encountered an error during the acquisition of SVCTABLE serialization. The return_code indicates the exceptional conditions encountered by MVS as follows:

RC 8

A previous request for control of the same resource has been made for the same task. The task has control of the resource.

RC 14

A previous request for control of the same resource has been made for the same task. The task does not have control of the resource.

RC 18

Environmental error. The limit for the number of concurrent resource requests has been reached. The task does not have control of the resource unless some previous ENQ or RESERVE request caused the task to obtain control of the resource.

System Action: Code Debug Service Provider initialization is terminated.

User Response: Contact BMC Support.

Module: DBUGSTC

XSP0447E SVCUPDTE Replace for CICS SVC svc_number failed RC(return_code)

Explanation: The Code Debug Service Provider CICS SVC Front-End initialization service encountered an error during the replacement of the CICS SVC entry point address. The return_code indicates the exceptional conditions encountered by MVS as follows:

RC 4

The macro was coded incorrectly.

RC C

Program Error. A REPLACE request contained incorrect information.

RC 10

Program Error. A REPLACE request contained illogical information.

RC 14

Program Error. The function specified was not REPLACE, DELETE, or EXTRACT.

RC 18

Program Error. The user attempted to update an extended SVC router entry in the SVC table.

RC 28

System Error. An error occurred while updating the SVC table.

RC 44

Program Error. A request was made to update an extended SVC, but no extended SVC routing code was provided.

RC 48

Program Error. A request was made to update an non-extended SVC, but an extended SVC routing code was provided.

RC 52

Program Error. A request was made to update an extended SVC, but the extended SVC type did not match the system-defined type for that extended SVC.

System Action: Code Debug Service Provider initialization is terminated.

User Response: Contact BMC Support.

Module: DBUGSTC

XSP0448E DEQ failure for Queue(queue) Resource(resource) RC(return_code)

Explanation: The Code Debug Service Provider CICS SVC Front-End initialization service encountered an error during the release of SVCTABLE serialization. The return_code indicates the exceptional conditions encountered by MVS as follows:

RC 4

The resource (or resources, if you specified GENERIC=YES) has been requested for the task, but the task has not been assigned control of it. The task continues waiting.

RC 8

Control of the resource (or resources, if you specified GENERIC=YES) has not been requested by the active task, or the resource has already been released.

System Action: Code Debug Service Provider initialization is terminated.

User Response: Contact BMC Support.

Module: DBUGSTC

XSP0449I SVC Front-End initialization complete

Explanation: The Code Debug Service Provider SVC Front-End Interface has successfully initialized.

System Action: None.

User Response: None.

Module: DBUGSTC

XSP0450I Storage Manager initialization started

Explanation: The Code Debug Service Provider storage manager is initializing.

System Action: None.

User Response: None.

Module: DBUGSTC

XSP0451E Storage Manager initialization failed RC(return_code) RSN(reason_code)

Explanation: The Code Debug Service Provider was unable to initialize the storage manager service. The return_code and reason_code indicates the exception conditions encountered:

RC 4

Storage manager initialization failed.

RSN 0

Storage manager was entered in cross memory mode (PASN¼HASN¼SASN).

RSN 4

Storage manager has determined the Primary ASN is invalid.

RSN 8

Storage manager has determined the Primary address space is not connected to the Code Debug Service Provider (SRVTSRDB = 0).

RSN 12

Storage manager is already initialized.

RSN 16

Storage manager Anchor Block load error.

RSN 20

Storage manager Anchor Block format error.

RSN 24

Storage Pool parameter error.

RSN 28

Storage Pool allocate error.

RSN 32

Storage Pool PAM allocate error.

RSN 36

Storage manager encountered an abend during processing.

System Action: Code Debug Service Provider initialization is terminated.

User Response: Contact BMC Support.

Module: DBUGSTC

XSP0452I Storage Manager initialization complete

Explanation: The Code Debug Service Provider storage manager has successfully initialized.

System Action: None.

User Response: None.

Module: DBUGSTC

XSP0453E TCP subtask initialization skipped due to error

Explanation: An error was detected prior to this point (see prior messages) that prevents initialization of the TCP subtask.

System Action: The subsystem initialization continues, but the TCP subtask will not be started.

User Response: Resolve the Code Debug Service Provider prior error. If the TCP subtask is required, provide the corrected parameter on a Service Provider INITTCP command.

Module: DBUGSTC

XSP0460I subtask "subtask" initialization started

Explanation: The Code Debug Service Provider subtask (Monitor|Command) is initializing.

System Action: None.

User Response: None.

Module: DBUGSTC

XSP0461E ATTACH for subtask "subtask" failed RC(return_code)

Explanation: The Code Debug Service Provider was unable to start the specified subtask (Monitor|Command). The return_code indicates the exception conditions encountered:

RC 4

Program error. ATTACH was issued in a STAE exit. Processing not completed.

RC 8

Environmental error. Insufficient storage available for control block for STAI/ESTAI request. Processing not completed.

RC C

Program error. An incorrect exit routine address or incorrect parameter list address was specified with STAI parameter. Processing not completed.

RC 14

Program error. An authorized task that specified JSTCB=YES is not a job step task. Processing not completed.

RC 18

Program error. An attempt to create a new subtask would cause the current task to have a mix of job step and non-job step subtasks. Processing not completed.

System Action: Code Debug Service Provider initialization is terminated.

User Response: Choose the appropriate action:

Program error  Contact BMC Support.
Environmental error   Resolve the environmental issues and restart the Code Debug Service Provider. If the problem persists, contact BMC Support.
Resolve the environmental issues and restart the Code Debug Service Provider. If the problem persists, contact Code Debug CICS Customer Support (see “Customer Support” on page vi)

Module: DBUGSTC

XSP0462E subtask "subtask" initialization failed Abend "abend"

Explanation: The Code Debug Service Provider subtask (Monitor|Command) abended with the specified completion code during initialization

System Action: Code Debug Service Provider initialization is terminated.

User Response: Contact BMC Support.

Module: DBUGSTC

XSP0463I subtask "subtask" initialization complete

Explanation: The Code Debug Service Provider subtask (Monitor|Command) has successfully initialized.

System Action: None.

User Response: None.

Module: DBUGSTC

XSP0464E TCP subtask initialization has failed

Explanation: An error was detected prior to this point (see prior messages) during initialization of the TCP subtask. Initialization of the subtask is terminated.

System Action: The subsystem initialization continues, but the TCP subtask will not be started.

User Response: Resolve the Code Debug Service Provider prior error. If the problem persists, contact BMC Support.

Module: DBUGSTC

XSP0489I Service Provider initialization complete

Explanation: The Code Debug Service Provider has successfully initialized.

System Action: None.

User Response: None.

Module: DBUGSTC

XSP0498E Abend "abend" occurred in Procedure (Function)

Explanation: An abend has been trapped in Procedure during the processing of an MVS Function.

System Action: Code Debug Service Provider initialization is terminated.

User Response: Contact BMC Support.

Module: DBUGSTC

XSP0499E Abend "abend" occurred in Procedure offset "offset"

Explanation: An abend has been trapped in Procedure at offset.

System Action: Code Debug Service Provider initialization is terminated.

User Response: Contact BMC Support.

Module: DBUGSTC

XSP0501I Subtask "subtask" termination initiated

Explanation: The Code Debug Service Provider subtask (Monitor|Command) is terminating.

System Action: None.

User Response: None.

Module: DBUGSTC

XSP0502I Subtask "subtask" termination complete

Explanation: The Code Debug Service Provider subtask (Monitor|Command) has successfully terminated.

System Action: None.

User Response: None.

Module: DBUGSTC

XSP0503I Service Provider termination complete

Explanation: The Code Debug Service Provider has successfully terminated.

System Action: None.

User Response: None.

Module: DBUGSTC

XSP0598E Abend "abend" occurred in Procedure (Function)

Explanation: An abend has been trapped in Procedure during the processing of MVS Function.

System Action: Code Debug Service Provider termination continues.

User Response: Contact BMC Support.

Module: DBUGSTC

XSP0599E Abend "abend" occurred in Procedure offset "offset"

Explanation: An abend has been trapped in Procedure at offset.

System Action: Code Debug Service Provider termination continues

User Response: Contact BMC Support..

Module: DBUGSTC

XSP0701E Loader Token token for Service Provider Termination routine is invalid

Explanation: The Code Debug Service Provider has detected an invalid loader token for termination services.

System Action: Code Debug Service Provider termination clean up is bypassed.

User Response: Contact BMC Support.

Module: DBUGSTC

XSP0702W Service Provider Termination routine completed with RC(return_code)

Explanation: The Code Debug Service Provider termination services routine encountered errors during processing. The return_code indicates the exception conditions encountered:

RC 4

Processing errors where encountered during clean up processing. Termination processing complete.

RC 8

Termination services detected an invalid processing mode. Termination cleanup has been bypassed.

RC C

Termination services detected an invalid Service Provider Anchor Block. Termination clean up bypassed.

System Action: Code Debug Service Provider termination completed, resource clean up may be incomplete.

User Response: Contact BMC Support.

Module: DBUGSTC

XSP0703E Storage Release for Service Provider Vector Table address(address) length(length) failed RC(return_code)

Explanation: The Code Debug Service Provider was unable to release storage in MVS subpool 241 for the Code Debug Service Provider Vector Table at the specified address and of the specified length. The return_code indicates the exception conditions encountered by MVS as follows:

RC 4

Not all requested virtual storage was freed.

RC 8

No virtual storage was freed because part of the storage area to be freed is fixed.

System Action: Code Debug Service Provider termination continues.

User Response: Contact BMC Support.

Module: DBUGSTC

XSP0798E Abend "abend" occurred in Procedure (Function)

Explanation: An abend has been trapped in Procedure during the processing of MVS Function.

System Action: Code Debug Service Provider termination continues.

User Response: ContactBMC Support.

Module: DBUGSTC

XSP0799E Abend "abend" occurred in Procedure offset "offset"

Explanation: An abend has been trapped in Procedure at offset.

System Action: Code Debug Service Provider termination continues.

User Response: Contact BMC Support.

Module: DBUGSTC

XSP0801E Resource Manager requires a minimum operating system release of OS/390 2.10

Explanation: The Code Debug Service Provider resource manager utilizes functions found on OS/390 2.10 and will not properly operate on prior releases of MVS.

System Action: Code Debug Service Provider resource manager processing is terminated.

User Response: Upgrade your operating system to a current release of OS/390 or z/OS.

Module: DBUGRMGR

XSP0802E Resource Manager entered in problem program state

Explanation: The Code Debug Service Provider resource manager was entered on problem program state.

System Action: Code Debug Service Provider resource clean up is bypassed.

User Response: Contact BMC Support.

Module: DBUGRMGR

XSP0803E Resource Manager entered in incorrect execution key

Explanation: The Code Debug Service Provider resource manager was entered in a PSW key other than zero.

System Action: Code Debug Service Provider resource manager processing is terminated.

User Response: Contact BMC Support.

Module: DBUGRMGR

XSP0804E Resource Manager Dynamic Storage Manager initialization error

Explanation: The Code Debug Service Provider resource manager DSHSRVS has failed to initialize, R15 contains the return code from the dynamic storage handler and R0 contains the corresponding reason code.

RC 4

Allocation failure for dynamic storage handler.

RSN 4

Insufficient storage is available.

RSN 8

Insufficient central storage to back the request.

RSN C

System cannot page in the page table associated with the storage.

RC 8

Load failure for dynamic storage handler (DSHSRVS).

RC C

Error establishing recovery environment (ESTAE|ESTAEX).

RC 10

Incorrect Address Space Control mode (not Primary).

System Action: Code Debug Service Provider resource manager processing is terminated.

User Response: Choose the appropriate action:

Allocation failures

Increase the amount of storage available to the private area.

Load failures

Resolve errors related to DSHSRVS load.

Recovery errors

Contact BMC Support.

Addressing mode errors

Contact BMC Support.

XSP0805E Resource Manager parameter list address(address) is invalid RMPL(address) SPANCHOR(address)

Explanation: The Code Debug Service Provider resource manager was entered with an invalid parameter list at the specified address.

System Action: Code Debug Service Provider resource manager processing is terminated.

User Response: Contact BMC Support.

Module: DBUGRMGR

XSP0806E Home ASID "asid" is invalid

Explanation: The Code Debug Service Provider resource manager has determined that the Home ASID "asid" is invalid (asid > ASVTMAXU).

System Action: Code Debug Service Provider resource manager processing is terminated.

User Response: Contact BMC Support.

Module: DBUGRMGR

XSP0807E Service Requester Descriptor Block address(address) is invalid

Explanation: The Code Debug Service Provider resource manager was passed an invalid Service Requester Descriptor Block address.

System Action: Code Debug Service Provider resource manager processing is terminated.

User Response: Contact BMC Support.

Module: DBUGRMGR

XSP0808I Resource Manager entered for mode type processing

Explanation: The Code Debug Service Provider resource manager has entered for the specified mode (Task|AddrSpc) and type (Term|Abterm) processing.

System Action: None.

User Response: None.

Module: DBUGRMGR

XSP0809E Loader Token token for Service Provider Termination routine is invalid

Explanation: The Code Debug Service Provider resource manager has detected an invalid loader token for termination services.

System Action: Code Debug Service Provider resource clean up is bypassed.

User Response: Contact BMC Support..

Module: DBUGRMGR

XSP0810W Service Provider Termination routine completed with RC(return_code)

Explanation: The Code Debug Service Provider termination services routine encountered errors during processing. The return_code indicates the exception conditions encountered:

RC 4

Processing errors where encountered during clean up processing. Termination processing complete.

RC 8

Termination services detected an invalid processing mode. Termination cleanup has been bypassed.

RC C

Termination services detected an invalid Service Provider Anchor Block. Termination clean up bypassed.

System Action: Code Debug Service Provider termination completed, resource clean up may be incomplete.

User Response: Contact BMC Support.

Module: DBUGRMGR

XSP0811E RESMGR delete for Type(type) Token(token) failed RC(return_code)

Explanation: The Code Debug Service Provider resource manager routine encountered errors during the delete processing of the specified resource manager (Task|AddrSpc) with the specified token. The return_code indicates the exception conditions encountered:

RC 4

The resource manager is currently in use. It has been queued for deletion. The ECB, if provided, will be posted when the delete process has completed.

RC 8

The resource manager was queued for deletion by a previous request. It is still active and will be deleted as soon as it is no longer in use.

RC 12

Program error. The caller did not provide a token to RESMGR.

RC 16

Program error. The token provided did not represent a currently established resource manager.

RC 20

Program error. The TCB address provided did not represent a valid TCB.

RC 24

Program error. The ASID provided did not represent a valid ASCB.

RC 28

Program error. The request type was not ADD or DELETE.

RC 32

Environmental error. RESMGR was unable to obtain storage for a work area it needed to process the request.

RC 36

Program error. The caller held an incorrect lock.

RC 40

Program error. It is not valid to delete a task resource manager for a specific task that is not in the home address space of the requestor.

RC 44

System error. An unrecoverable error occurred while processing the request.

RC 48

Program error. The ECB parameter was specified but is not supported for the particular type of delete request.

RC 52

Program error. The caller is not authorized to use RESMGR.

RC 64

Program error. The TTOKEN parameter specified a task in an address space other than the home address space.

System Action: Code Debug Service Provider termination completed, resource manager removal may be incomplete.

User Response: Contact BMC Support.

Module: DBUGRMGR

XSP0812I Resource Manager processing complete for SSID(ssid)

Explanation: The Code Debug Service Provider resource manager has completed resource clean up for the specified subsystem.

System Action: None.

User Response: None.

Module: DBUGRMGR

XSP0898E Abend "abend" occurred in Procedure (Function)

Explanation: An abend has been trapped in Procedure during the processing of MVS Function.

System Action: Code Debug Service Provider resource manager processing continues.

User Response: Contact BMC Support.

Module: DBUGRMGR

XSP0899E Abend "abend" occurred in Procedure offset "offset"

Explanation: An abend has been trapped in Procedure at offset.

System Action: Code Debug Service Provider resource manager processing continues.

User Response: Contact BMC Support.

Module: DBUGRMGR

XSP0901I Termination routine entered for type processing

Explanation: The Code Debug Service Provider termination services routine was entered for the specified termination processing (Initialization|Termination|Abterm|Resmgr).

System Action: None.

User Response: None.

Module: DBUGRTERM

XSP0902E STIMERM set failed RC(return_code)

Explanation: The Code Debug Service Provider termination services encountered an error during the processing of a STIMERM.

System Action: Code Debug Service Provider termination services processing continues.

User Response: Contact BMC Support.

Module: DBUGTERM

XSP0903W Service Requester quiesce time out has occurred with # connected address spaces

Explanation: The Code Debug Service Provider termination services encountered a time out condition while attempting to quiesce the specified number of connected Service Requester address spaces.

System Action: Code Debug Service Provider termination services processing continues. The Service Provider cross memory resources may not be completely clean up.

User Response: None.

Module: DBUGTERM

XSP0904E Storage Obtain for Service Request Block length(length) failed RC(return_code)

Explanation: The Code Debug Service Provider termination exit scheduler was unable to obtain storage in MVS subpool 241 for Service Request Block (SRB) of the specified length. The return_code indicates the exception conditions encountered by MVS as follows:

RC 4

Insufficient storage is available.

RC 8

Insufficient central storage to back the request.

RC C

System cannot page in the page table associated with the storage.

System Action: Code Debug Service Provider will not be able to perform asynchronous resource clean up for connect Service Requester address spaces.

User Response: None.

Module: DBUGTERM

XSP0905E Schedule of Asynchronous Termination Routine failed Abend "abend"

Explanation: The Code Debug Service Provider termination exit scheduler abended with the specified completion code during schedule processing.

System Action: Code Debug Service Provider will not be able to perform asynchronous resource clean up for connect Service Requester address spaces.

User Response: Contact BMC Support.

Module: DBUGSTC

XSP0906E Storage Release for Service Request Block address(address) length(length) failed RC(return_code)

Explanation: The Code Debug Service Provider termination exit scheduler was unable to release storage in MVS subpool 241 for the Service Request Block (SRB) at the specified address and of the specified length. The return_code indicates the exception conditions encountered by MVS as follows:

RC 4

Not all requested virtual storage was freed.

RC 8

No virtual storage was freed because part of the storage area to be freed is fixed.

System Action: Code Debug Service Provider termination exit scheduler processing is incomplete.

User Response: Contact BMC Support.

Module: DBUGTERM

XSP0907E DETACH for Service Provider subtask "subtask" failed Abend "abend"

Explanation: The Code Debug Service Provider termination services encountered errors during DEATCH processing for the specified subtask (Monitor|Command). The return_code indicates the exception conditions encountered:

RC 4

An incomplete subtask was detached with STAE=YES specified; DETACH processing successfully completed.

System Action: Code Debug Service Provider termination services processing continues.

User Response: Contact BMC Support.

Module: DBUGTERM

XSP0908E Storage Manager termination failed RC(return_code) RSN(reason_code)

Explanation: The Code Debug Service Provider termination services encountered errors during termination for the storage manager service. The return_code and reason_code indicates the exception conditions encountered:

RC 4

Storage manager initialization failed.

RSN 0

Storage manager entered in cross memory mode (PASN^=HASN^=SASN).

RSN 4

Storage manager has determined the Primary ASN is invalid.

RSN 8

Storage manager has determined the Primary address space is not connected to the Code Debug Service Provider (SRVTSRDB = 0).

RSN 12

Storage manager is not initialized.

RSN 16

Storage Pool deallocate error.

RSN 20

Storage Pool PAM deallocate error.

RSN 24

Storage manager anchor block delete error.

RSN 28

Storage manager encountered an abend during processing.

System Action: Code Debug Service Provider termination services processing continues.

User Response: Contact BMC Support.

Module: DBUGSTC

XSP0909E ETDES for ET(et) failed RC(return_code)

Explanation: The Code Debug Service Provider was unable to destroy the specified program call table. The return_code indicates the exception conditions encountered:

RC 4

The specified entry table was destroyed. There were connections to linkage indexes, PURGE=YES was specified, and the entry table was disconnected.

System Action: Code Debug Service Provider termination services processing continues, cross memory resources clean up may be incomplete.

User Response: None.

Module: DBUGTERM

XSP0910E LXFRE for LX(lx) failed RC(return_code)

Explanation: The Code Debug Service Provider was unable to free the specified linkage index. The return_code indicates the exception conditions encountered:

RC 4

The specified linkage indexes were freed. Entry tables were connected, but FORCE was specified and was successfully executed.

RC 8

Some of the specified linkage indexes were freed. Entry tables were connected. FORCE was specified but one or more of the necessary disconnects failed. No action by the issuer of LXFRE is required in this situation.

System Action: Code Debug Service Provider termination services processing continues, cross memory resources clean up may be incomplete.

User Response: None.

Module: DBUGTERM

XSP0911E AXSET for AX(ax) failed RC(return_code)

Explanation: The Code Debug Service Provider was unable to set the home address space to the specified AX.

System Action: Code Debug Service Provider termination services processing continues, cross memory resources clean up may be incomplete.

User Response: None.

Module: DBUGTERM

XSP0912E AXFRE for AX(ax) failed RC(return_code)

Explanation: The Code Debug Service Provider was unable to free the specified authorization index. The return_code indicates the exception conditions encountered:

RC 4

The specified authorization index or indexes are not successfully freed. One or more of the indexes are unavailable for use.

System Action: Code Debug Service Provider termination services processing continues, cross memory resources clean up may be incomplete.

User Response: None.

Module: DBUGTERM

XSP0913E Storage Release for Service Provider Vector Table address(address) length(length) failed RC(return_code)

Explanation: The Code Debug Service Provider termination services was unable to release storage in MVS subpool 241 for the Code Debug Service Provider Vector Table at the specified address and of the specified length. The return_code indicates the exception conditions encountered by MVS as follows:

RC 4

Not all requested virtual storage was freed.

RC 8

No virtual storage was freed because part of the storage area to be freed is fixed.

System Action: Code Debug Service Provider termination services processing continues.

User Response: Contact BMC Support.

Module: DBUGTERM

XSP0914E Storage Release for Service Requester Descriptor Block address(address) length(length) failed RC(return_code)

Explanation: The Code Debug Service Provider termination services was unable to release storage in MVS subpool 241 for the Code Debug Service Requester Descriptor Block at the specified address and of the specified length. The return_code indicates the exception conditions encountered by MVS as follows:

RC 4

Not all requested virtual storage was freed.

RC 8

No virtual storage was freed because part of the storage area to be freed is fixed.

System Action: Code Debug Service Provider termination services processing continues.

User Response: Contact BMC Support.

Module: DBUGTERM

XSP0915E Storage Release for Service Requester Data Anchor address(address) length(length) failed RC(return_code)

Explanation: The Code Debug Service Provider termination services was unable to release storage in MVS subpool 241 for the Code Debug Service Requester Data Anchor at the specified address and of the specified length. The return_code indicates the exception conditions encountered by MVS as follows:

RC 4

Not all requested virtual storage was freed.

RC 8

No virtual storage was freed because part of the storage area to be freed is fixed.

System Action: Code Debug Service Provider termination services processing continues.

User Response: Contact BMC Support.

Module: DBUGTERM

XSP0916E Storage Release for Task Storage Block address(address) length(length) failed RC(return_code)

Explanation: The Code Debug Service Provider termination services was unable to release storage in MVS subpool 241 for the Code Debug Task Storage Block at the specified address and of the specified length. The return_code indicates the exception conditions encountered by MVS as follows:

RC 4

Not all requested virtual storage was freed.

RC 8

No virtual storage was freed because part of the storage area to be freed is fixed.

System Action: Code Debug Service Provider termination services processing continues.

User Response: Contact BMC Support.

Module: DBUGTERM

XSP0917E Storage Release for Local System Function Table address(address) length(length) failed RC(return_code)

Explanation: The Code Debug Service Provider termination services was unable to release storage in MVS subpool 205 for the Code Debug Local System Function Table at the specified address and of the specified length. The return_code indicates the exception conditions encountered by MVS as follows:

RC 4

Not all requested virtual storage was freed.

RC 8

No virtual storage was freed because part of the storage area to be freed is fixed.

System Action: Code Debug Service Provider termination services processing continues.

User Response: Contact BMC Support.

Module: DBUGTERM

XSP0918E ATSET for AX(ax) failed RC(return_code)

Explanation: The Code Debug Service Provider was unable to set the specified authorization index (PT=NO and SSAR=NO).

System Action: Code Debug Service Provider termination services processing continues, cross memory resources clean up may be incomplete.

User Response: None.

Module: DBUGTERM

XSP0919E ETDIS failed RC(return_code)

Explanation: The Code Debug Service Provider was unable to disconnect the Home address space from the Service Provider program call entry table.

System Action: Code Debug Service Provider termination services processing continues, cross memory resources clean up may be incomplete.

User Response: None.

Module: DBUGTERM

XSP0920E ALESERV delete for Service Provider ALET(alet) failed RC(return_code)

Explanation: The Code Debug Service Provider was unable to disconnect the Service Provider address space from the Home address space PASN-AL. The return_code indicates the exception conditions encountered:

RC 4

Program error. The caller is not EAX-authorized to the address space specified by the ALET. The entry is not deleted.

RC 14

Program or environmental error. The input ALET corresponds to an access list entry that is not valid.

RC 1C

Program error. The caller is holding a lock.

RC 20

Program error. The caller is disabled.

RC 24

Program error. AR 1 contained an ALET of 1 on input or an ALET for the caller’s PASN-AL.

RC 28

Program error. The caller specified an ALET that is not valid.

RC 2C

Program error. The caller attempted to delete ALET 0, 1, or 2.

RC 30

Program error. A problem-state caller with PSW key 8-F attempted to delete an entry from the PASN-AL for a space other than a SCOPE=SINGLE data space.

RC 60

System error. An unexpected error occurred. The request was not completed.

RC 64

Program error. A problem-state caller with PSW key 8-F tried to delete an entry using CHKEAX=NO.

RC 78

Program error. A problem-state caller with PSW key 8-F tried to delete an entry from the PASN-AL. The caller is neither the creator nor the owner of the data space, or the PSW key of the caller did not match the storage key of the data space.

System Action: Code Debug Service Provider termination services processing continues, cross memory resources clean up may be incomplete.

User Response: Contact BMC Support.

Module: DBUGTERM

XSP0921E RESMGR delete for Type(type) Token(token) failed RC(return_code)

Explanation: The Code Debug Service Provider termination services routine encountered errors during the delete processing of the specified resource manager (Task|AddrSpc) with the specified token. The return_code indicates the exception conditions encountered:

RC 4

The resource manager is currently in use. It has been queued for deletion. The ECB, if provided, will be posted when the delete process has completed.

RC 8

The resource manager was queued for deletion by a previous request. It is still active and will be deleted as soon as it is no longer in use.

RC 12

Program error. The caller did not provide a token to RESMGR.

RC 16

Program error. The token provided did not represent a currently established resource manager.

RC 20

Program error. The TCB address provided did not represent a valid TCB.

RC 24

Program error. The ASID provided did not represent a valid ASCB.

RC 28

Program error. The request type was not ADD or DELETE.

RC 32

Environmental error. RESMGR was unable to obtain storage for a work area it needed to process the request.

RC 36

Program error. The caller held an incorrect lock.

RC 40

Program error. It is not valid to delete a task resource manager for a specific task that is not in the home address space of the requestor.

RC 44

System error. An unrecoverable error occurred while processing the request.

RC 48

Program error. The ECB parameter was specified but is not supported for the particular type of delete request.

RC 52

Program error. The caller is not authorized to use RESMGR.

RC 64

Program error. The TTOKEN parameter specified a task in an address space other than the home address space.

System Action: Code Debug Service Provider termination services processing continues, resource manager removal may be incomplete.

User Response: Contact BMC Support.

Module: DBUGTERM

XSP0922E Service Requester SYSEVENT OKSWAP error RC(return_code)

Explanation: The Code Debug Service Provider encountered an error attempting to make the address space swappable. The return_code indicates the exception conditions encountered by MVS as follows:

RC 4

The request was not honored because it was not for the current address space.

RC 8

The request was not honored because the issuer was not authorized.

System Action: Code Debug Service Provider termination services processing continues.

User Response: Contact BMC Support.

Module: DBUGTERM

XSP0923E Data Services Clean up failed RC(return_code) RSN(reason_code)

Explanation: The Code Debug Service Provider encountered an error attempting perform Data Services clean up. The return_code and reason_code indicates the exception conditions encountered as follows:

RC 4

Error during processing.

RSN 1

Region descriptor delete failed.

RSN 2

Owned shared storage delete failed.

RSN 3

Region descriptor and Owned shared storage delete failed.

RC 8

Parameter error.

RSN 0

Invalid Region descriptor token.

RC 12

Storage manager error.

RSN #

Storage manager return/reason code.

RC 16

Environmental error.

RSN 0

Invalid secondary ASN.

RSN 4

Service Requester vector error.

RSN 16

Abend during processing.

System Action: Code Debug Service Provider termination services processing continues, Data Services clean up may be incomplete.

User Response: Contact BMC Support.

Module: DBUGTERM

XSP0924E Unchain of Service Requester Descriptor Block failed RC(return_code) RSN(reason_code)

Explanation: The Code Debug Service Provider encountered an error attempting unchain the Service Requester Descriptor Block. The return_code and reason_code indicates the exception conditions encountered as follows:

RC 16

Error during processing.

RSN 16

Error acquiring the LOCAL lock.

RSN 20

Error acquiring the CMS lock.

RSN 24

Abend during processing.

System Action: Code Debug Service Provider termination services processing continues, Service Requester related storage areas will be released during Code Debug Service Provider address space termination.

User Response: Contact BMC Support.

Module: DBUGTERM

XSP0925E POST for Asynchronous Cleanup ECB failed RC(return_code)

Explanation: The Code Debug Service Provider encountered an error attempting to POST the Asynchronous Cleanup ECB. The Service Provider Data Services Cleanup processing may not occur. The return_code indicates the exception conditions encountered as follows:

RC 8

Indicates an asynchronous POST is in progress. You specified ERRET; however, if an error occurs before POST completes, the error routine that you specified will not receive control.

System Action: Code Debug Service Provider termination services processing continues. Service Provider Data Services storage owned by the Service Requester address space may not be released. Service Requester related storage areas will be released during Code Debug Service Provider address space termination.

User Response: Contact BMC Support.

Module: DBUGTERM

XSP0926E Service Requester cleanup time out has occurred for Descriptor Block address(address)

Explanation: The Code Debug Service Provider Asynchronous Cleanup processing has timed out for the specified Service Requester Descriptor block address.

System Action: Code Debug Service Provider termination services processing continues. Service Provider Data Services storage owned by the Service Requester address space may not be released. Service Requester related storage areas will be released during Code Debug Service Provider address space termination.

User Response: Contact BMC Support.

Module: DBUGTERM

XSP0981E Termination Services requires a minimum operating system release of OS/390 2.10

Explanation: The Code Debug Service Provider asynchronous termination routine utilize functions found on OS/390 2.10 and will not properly operate on prior releases of MVS.

System Action: Code Debug Service Provider asynchronous termination processing is terminated.

User Response: Upgrade your operating system to a current release of OS/390 or z/OS.

Module: DBUGTERM

XSP0982E Termination Services entered in problem program state

Explanation: The Code Debug Service Provider asynchronous termination routine was entered on problem program state.

System Action: Code Debug Service Provider asynchronous termination processing is terminated.

User Response: Contact BMC Support.

Module: DBUGSTC

XSP0983E Termination Services entered in incorrect execution key

Explanation: The Code Debug Service Provider asynchronous termination routine was entered in a PSW key other than zero.

System Action: Code Debug Service Provider asynchronous termination processing is terminated.

User Response: Contact BMC Support.

Module: DBUGTERM

XSP0984E Termination Services Dynamic Storage Manager initialization error

Explanation: The Code Debug Service Provider asynchronous termination routine DSHSRVS has failed to initialize, R15 contains the return code from the dynamic storage handler and R0 contains the corresponding reason code.

RC 4

Allocation failure for dynamic storage handler. 

RSN 4

Insufficient storage is available.

RSN 8

Insufficient central storage to back the request.

RSN C

System cannot page in the page table associated with the storage.

RC 8

Load failure for dynamic storage handler (DSHSRVS).

RC C

Error establishing recovery environment (ESTAE|ESTAEX).

RC 10

Incorrect Address Space Control mode (not Primary).

System Action: Code Debug Service Provider asynchronous termination processing is terminated.

User Response: Choose the appropriate action:

Allocation failures

the amount of storage available to the private area.

Load failures

Resolve errors related to DSHSRVS load.

Recovery errors

Contact BMC Support.

Addressing mode errors

Contact BMC Support.

Module: DBUGTERM

XSP0985E Termination Services parameter list address(address) is invalid SPANCHOR(address)

Explanation: The Code Debug Service Provider asynchronous termination routine was entered with an invalid parameter list at the specified address.

System Action: Code Debug Service Provider asynchronous termination processing is terminated.

User Response: Contact BMC Support.

Module: DBUGTERM

XSP0986E Service Requester Descriptor Block address(address) is invalid

Explanation: The Code Debug Service Provider asynchronous termination routine encountered an invalid Service Requester Descriptor Block address.

System Action: Code Debug Service Provider asynchronous termination processing is terminated.

User Response: Contact BMC Support.

Module: DBUGRMGR

XSP0987I Asynchronous Termination routine entered for Service Requester job_name

Explanation: The Code Debug Service Provider asynchronous termination routine has been entered for specified Service Requester.

System Action: None.

User Response: None.

Module: DBUGTERM

XSP0988W Service Requester Termination routine completed with RC(return_code)

Explanation: The Code Debug Service Provider termination services routine encountered errors during processing. The return_code indicates the exception conditions encountered:

RC 4

Processing errors where encountered during clean up processing. Termination processing complete.

RC 8

Termination services detected an invalid processing mode. Termination cleanup has been bypassed.

RC C

Termination services detected an invalid Service Provider Anchor Block. Termination clean up bypassed.

System Action: Code Debug Service Provider termination completed, resource clean up may be incomplete.

User Response: Contact BMC Support.

Module: DBUGTERM

XSP0989I Asynchronous Termination routine completed for Service Requester job_name

Explanation: The Code Debug Service Provider asynchronous termination routine has completed processing for specified Service Requester.

System Action: None.

User Response: None.

Module: DBUGTERM

XSP0990E SETLOCK obtain for LOCAL lock failed with RC(return_code)

Explanation: The Code Debug Service Provider termination services routine encountered errors during the acquisition of the LOCAL lock. The return_code indicates the exception conditions encountered:

RC 4

The lock was already held by the caller.

RC 8

The conditional obtain process was unsuccessful. The lock is owned by another processor.

System Action: Code Debug Service Provider termination services processing continues, first level data capture processing is incomplete.

User Response: Contact BMC Support.

Module: DBUGTERM

XSP0991I Termination Services dump has been captured

Explanation: The Code Debug Service Provider termination services routine has successfully captured the required SVCDUMP.

System Action: Code Debug Service Provider termination services processing continues.

User Response: Ship the SVCDUMP to BMC only when requested by Code Debug CICS Customer Support.

Module: DBUGTERM

XSP0992I Partial Termination Services dump has been captured

Explanation: The Code Debug Service Provider termination services routine was unable to captured a complete SVCDUMP.

System Action: Code Debug Service Provider termination services processing continues.

User Response: Ship the SVCDUMP to BMC only when requested by Code Debug CICS Customer Support.

Module: DBUGTERM

XSP0993E SDUMPX request failed with RC(return_code) RSN(reason_code)

Explanation: The Code Debug Service Provider termination services routine encountered errors during the capture of an SVCDUMP. The return_code and reason_code indicates the exception conditions encountered:

RC 8

The system was unable to schedule a dump.

RSN 0

No SVC dump was requested.

RSN 1

An SVC dump was successfully started.

RSN 2

An SVC dump was suppressed because the capture phase of another SVC dump was in progress.

RSN 3

An SVC dump was suppressed by a request by the installation.

RSN 4

An SVC dump was suppressed by a SLIP NODUMP command.

RSN 5

An SVC dump was suppressed because a SYS1.DUMP data set was not available.

RSN 6

An SVC dump was suppressed because an I/O error occurred during the initialization of the SYS1.DUMP data set.

RSN 8

An SVC dump was suppressed because an SRB could not be scheduled to activate the dump tasks in the requested address spaces.

RSN 9

An SVC dump was suppressed because a terminating error occurred in SVC dump before the first dump record was written.

RSN A

An SVC dump was suppressed because a status stop SRB condition was detected.

RSN B

An SVC dump was suppressed by DAE.

RSN 15

The parameter list address is zero.

RSN 16

The parameter list is not a valid SVC or SNAP parameter list.

RSN 17

The caller-supplied data set is not supported.

RSN 18

The start address is greater than or equal to the end address in a storage list.

RSN 19

The caller-supplied header is longer than 100 characters.

RSN 1A

The caller requested a 4K buffer, but did not reserve it.

RSN 1B

A storage list overlaps the 4K buffer

RSN 1C

The caller-supplied DCB is not valid.

RSN 22

The 4K buffer was requested with an SVC dump already in progress.

RSN 25

A non-valid subpool ID was specified in the subpool list.

RSN 28

Part of the parameter list is inaccessible.

RSN 29

The caller-supplied DCB is inaccessible.

RSN 2A

The caller-supplied storage list is inaccessible.

RSN 2B

The caller-supplied header data is inaccessible.

RSN 2C

The caller-supplied ECB is inaccessible.

RSN 2D

The caller’s ASID list is inaccessible.

RSN 2E

The caller’s SUMLIST/SUMLSTA is inaccessible.

RSN 2F

The caller’s SUBPLST list is inaccessible.

RSN 30

The caller’s KEYLIST is inaccessible.

RSN 31

Copies of the SLIP register and PSW are inaccessible.

RSN 32

The caller-supplied SRB is inaccessible.

RSN 33

The version number in the parameter list is not valid.

RSN 34

The caller’s LISTD is inaccessible.

RSN 35

The caller’s SUMLISTL is inaccessible.

RSN 36

The parameter list contains conflicting parameters.

RSN 37

The ID is longer than 50 characters.

RSN 38

The ID is not addressable.

RSN 39

The PSWREGS area is an incorrect length.

RSN 3A

The PSWREGS area is not addressable.

RSN 3B

The symptom record is not valid.

RSN 3C

The symptom record is not addressable.

RSN 3D

The DEB for the caller-supplied DCB is inaccessible.

RSN 3E

SVC dump is already using the maximum amount of virtual storage (as determined by the installation, using the MAXSPACE parameter on the CHNGDUMP command) to process other dumps.

RSN FF

An SVC dump was suppressed for some other unspecified reason.

System Action: Code Debug Service Provider termination services processing continues, first level data capture processing is incomplete.

User Response: Contact BMC Support.

Module: DBUGTERM

XSP0997E ENQ/DEQ failure for Queue(queue) Resource(resource) RC(return_code)

Explanation: The Code Debug Service Provider termination services encountered an error during the acquisition/relinquishment (ENQ/DEQ) of the Service Requester Anchor Block. The return_code indicates the exception conditions encountered by MVS as follows:

ENQ Return Codes

RC 4

A previous request for control of the same resource has been made for the same task. The task has control of the resource.

RC 14

A previous request for control of the same resource has been made for the same task. The task does not have control of the resource.

RC 18

Environmental error. The limit for the number of concurrent resource requests has been reached. The task does not have control of the resource unless some previous ENQ or RESERVE request caused the task to obtain control of the resource.

DEQ Return Codes

RC 4

RC 4
The resource (or resources, if you specified GENERIC=YES) has been requested for the task, but the task has not been assigned control of it. The task continues waiting.

RC 8

Control of the resource (or resources, if you specified GENERIC=YES) has not been requested by the active task, or the resource has already been released.

System Action: Code Debug Service Provider termination services processing continues.

User Response: Contact BMC Support.

Module: DBUGTERM

XSP0998E Abend "abend" occurred in Procedure (Function)

Explanation: An abend has been trapped in Procedure during the processing of MVS Function.

System Action: Code Debug Service Provider termination services processing continues.

User Response: Contact BMC Support.

Module: DBUGTERM

XSP0999E Abend "abend" occurred in Procedure offset "offset"

Explanation: An abend has been trapped in Procedure at offset.

System Action: Code Debug Service Provider termination services processing continues.

User Response: Contact BMC Support.

Module: DBUGTERM

XSP1001E Monitor subtask requires a minimum operating system release of OS/390 2.10

Explanation: The Code Debug Service Provider monitor subtask utilizes functions found on OS/390 2.10 and will not properly operate on prior releases of MVS.

System Action: Code Debug Service Provider monitor subtask is terminated.

User Response: Upgrade your operating system to a current release of OS/390 or z/OS.

Module: DBUGMTSK

XSP1002E Monitor subtask entered in non-authorized state

Explanation: The Code Debug Service Provider was fetched from a non-APF authorized library concatenation.

System Action: Code Debug Service Provider monitor subtask is terminated.

User Response: APF authorize the library, which contains the Code Debug Service Provider, and/or remove non-APF authorized libraries from the STEPLIB concatenation. See the Code Debug CICS Installation Guide.

Module: DBUGMTSK

XSP1003E Monitor subtask entered in incorrect execution key

Explanation: The Code Debug Service Provider monitor subtask was entered in a PSW key other than four (4).

System Action: Code Debug Service Provider monitor subtask is terminated.

User Response: Contact BMC Support.

Module: DBUGMTSK

XSP1004E Monitor subtask Dynamic Storage Manager initialization error

Explanation: The Code Debug Service Provider monitor subtask DSHSRVS has failed to initialize, R15 contains the return code from the dynamic storage handler and R0 contains the corresponding reason code.

RC 4

Allocation failure for dynamic storage handler.

RSN 4

Insufficient storage is available.

RSN 8

Insufficient central storage to back the request.

RSN C

System cannot page in the page table associated with the storage.

RC 8

Load failure for dynamic storage handler (DSHSRVS).

RC C

Error establishing recovery environment (ESTAE|ESTAEX).

RC 10

Incorrect Address Space Control mode (not Primary).

System Action: Code Debug Service Provider monitor subtask is terminated.

User Response: Choose the appropriate action:

Allocation failures

Increase the amount of storage available to the private area.

Load failures

Resolve errors related to DSHSRVS load.

Recovery errors

Contact BMC Support.

Addressing mode errors

Contact BMC Support.

Module: DBUGMTSK

XSP1005E Monitor subtask attached with invalid parameter address(address)

Explanation: The Code Debug Service Provider monitor subtask was attached with an invalid parameter list at the specified address.

System Action: Code Debug Service Provider monitor subtask initialization is terminated.

User Response: Contact BMC Support.

Module: DBUGMTSK

XSP1006E SSAFF Set for Service Provider Affinity Index(index) failed RC(return_code)

Explanation: The Code Debug Service Provider monitor subtask encountered an error during the processing of a SSAFF SET.

System Action: Code Debug Service Provider monitor subtask initialization is terminated.

User Response: Contact BMC Support.

Module: DBUGMTSK

XSP1011E STIMERM set failed RC(return_code)

Explanation: The Code Debug Service Provider monitor subtask encountered an error during the processing of a STIMERM.

System Action: Code Debug Service Provider monitor subtask is terminated.

User Response: Contact BMC Support.

Module: DBUGMTSK

XSP1021I Asynchronous Cleanup started for job_name

Explanation: The Code Debug Service Provider Asynchronous Cleanup routine has started for the specified Service Requester address space. All Service Provider Data Services resources owned by the specified Service Requester address space will be released.

System Action: None.

User Response: None.

Module: DBUGMTSK

XSP1022I Asynchronous Cleanup completed for job_name RC(return_code) RSN(reason_code)

Explanation: The Code Debug Service Provider Asynchronous Cleanup routine has completed for the specified Service Requester address space. The return_code and reason_code indicates the exception conditions encountered:

RC 0

Processing complete.

RC 4

Error during processing.

RSN 1

Error releasing region descriptor.

RSN 2

Error releasing shared storage.

RSN 3

Error releasing region descriptor and shared storage.

RC 8

Parameter error.

RSN 0

Invalid Region descriptor token.

RC 12

Storage manager error.

RSN #

Storage manager return/reason code.

RSN 1

An SVC dump was successfully started.

RC 16

Environmental error.

RSN 0

Invalid secondary ASN.

RSN 4

Service Requester vector error.

RSN 16

Abend during processing.

System Action: Service Provider Data Services resources owned by the specified Service Requester address space may not have been released.

User Response: Contact XBMC Support if errors occurred during processing.

Module: DBUGMTSK

XSP1029E Service Requester Descriptor Block address(address) is invalid

Explanation: The Code Debug Service Provider Asynchronous Cleanup routine was passed an invalid Service Requester Descriptor Block address.

System Action: Code Debug Service Provider Asynchronous Cleanup processing is suppressed.

User Response: Contact BMC Support.

Module: DBUGMTSK

XSP1098E Abend "abend" occurred in Procedure (Function)

Explanation: An abend has been trapped in Procedure during the processing of MVS Function.

System Action: Code Debug Service Provider monitor subtask is terminated.

User Response: Contact BMC Support.

Module: DBUGMTSK

XSP1099E Abend "abend" occurred in Procedure offset "offset"

Explanation: An abend has been trapped in Procedure at offset.

System Action: Code Debug Service Provider monitor subtask is terminated.

User Response: Contact BMC Support.

Module: DBUGMTSK

XSP2001E Command subtask requires a minimum operating system release of OS/390 2.10

Explanation: The Code Debug Service Provider command subtask utilizes functions found on OS/390 2.10 and will not properly operate on prior releases of MVS.

System Action: Code Debug Service Provider command subtask is terminated.

User Response: Upgrade your operating system to a current release of OS/390 or z/OS.

Module: DBUGCTSK

XSP2002E Command subtask entered in non-authorized state

Explanation: The Code Debug Service Provider was fetched from a non-APF authorized library concatenation.

System Action: Code Debug Service Provider command subtask is terminated.

User Response: APF authorize the library, which contains the Code Debug Service Provider, and/or remove non-APF authorized libraries from the STEPLIB concatenation. See the Code Debug CICS Installation Guide.

Module: DBUGCTSK

XSP2003E Command subtask entered in incorrect execution key

Explanation: The Code Debug Service Provider command subtask was entered in a PSW key other than four (4).

System Action: Code Debug Service Provider command subtask is terminated.

User Response: Contact BMC Support.

Module: DBUGCTSK

XSP2004E Command subtask Dynamic Storage Manager initialization error

Explanation: The Code Debug Service Provider command subtask DSHSRVS has failed to initialize, R15 contains the return code from the dynamic storage handler and R0 contains the corresponding reason code.

RC 4

Allocation failure for dynamic storage handler.

RSN 4

Insufficient storage is available.

RSN 8

Insufficient central storage to back the request.

RSN C

System cannot page in the page table associated with the storage.

RC 8

Load failure for dynamic storage handler (DSHSRVS).

RC C

Error establishing recovery environment (ESTAE|ESTAEX).

RC 10

Incorrect Address Space Control mode (not Primary).

System Action: Code Debug Service Provider command subtask is terminated.

User Response: Choose the appropriate action:

Allocation failures

Increase the amount of storage available to the private area.

Load failures

Resolve errors related to DSHSRVS load.

Recovery errors

Contact BMC Support.

Addressing mode errors

Contact BMC Support.

Module: DBUGCTSK

XSP2005E Command subtask attached with invalid parameter address(address)

Explanation: The Code Debug Service Provider command subtask was attached with an invalid parameter list at the specified address.

System Action: Code Debug Service Provider command subtask initialization is terminated.

User Response: Contact BMC Support.

Module: DBUGCTSK

XSP2006E SSAFF Set for Service Provider Affinity Index(index) failed RC(return_code)

Explanation: The Code Debug Service Provider command subtask encountered an error during the processing of a SSAFF SET.

System Action: Code Debug Service Provider command subtask initialization is terminated.

User Response: Contact BMC Support.

Module: DBUGCTSK

XSP2011E QEDIT set limit failed RC(return_code)

Explanation: The Code Debug Service Provider command subtask encountered an error during the processing of a QEDIT limit set operation. The return_code indicates the exception conditions encountered by MVS as follows:

RC 8

The limit for the number of CIBs to be chained was exceeded; an issuer who made a request to free all the CIBs on a chain as not in supervisor state and PSW key zero; or the user provided an invalid address for the pointer to the CIB chain, an invalid address for the CIB address, or an invalid CIB number as input to the macro.

System Action: Code Debug Service Provider command subtask initialization is terminated.

User Response: Contact BMC Support.

Module: DBUGCTSK

XSP2012E QEDIT release CIB address(address) failed RC(return_code)

Explanation: The Code Debug Service Provider command subtask encountered an error during the processing of a QEDIT release operation of the specified CIB. The return_code indicates the exception conditions encountered by MVS as follows:

RC 4

The CIB to be deleted was not found on any CIB chain.

User Response: Contact BMC Support.

System Action: Code Debug Service Provider command subtask initialization is terminated.

Module: DBUGCTSK

XSP2013W Command verb code CIBVERB(verb) is unknown or unsupported, ignored

Explanation: The Code Debug Service Provider command subtask encountered an unknown or unsupported verb code as specified.

System Action: Code Debug Service Provider command subtask will ignore the command.

User Response: If the verb code is for START or MODIFY, contact BMC Support.

Module: DBUGCTSK

XSP2014E Modify command parameter is required and is not present

Explanation: Code Debug Service Provider command subtask detected a syntax error in the Modify command. A command parameter is required and was not specified.

System Action: Code Debug Service Provider command subtask will ignore the command.

User Response: Reissue the Modify command with the correct syntax.

Module: DBUGCTSK

XSP2015E Command parameter "parameter" is invalid

Explanation: Code Debug Service Provider command subtask detected a invalid command Modify command parameter as specified.

System Action: Code Debug Service Provider command subtask will ignore the command.

User Response: Reissue the Modify command with a valid command.

Module: DBUGCTSK

XSP2016E command operand is required and is not present

Explanation: Code Debug Service Provider command subtask detected a syntax error in the specified command.

System Action: Code Debug Service Provider command subtask will ignore the command.

User Response: Reissue the Modify command with valid command syntax.

Module: DBUGCTSK

XSP2017E command operand syntax error

Explanation: The command parameter does not conform to proper syntax. The command parameter either requires an operand value or does not support an operand.

System Action: Code Debug Service Provider command subtask will ignore the command.

User Response: Reissue the Modify command with valid command syntax.

Module: DBUGCTSK

XSP2018E command operand "operand" is invalid

Explanation: The command operand "operand" is invalid. The token type for the command operand does not conform to the required syntax.

System Action: Code Debug Service Provider command subtask will ignore the command.

User Response: Reissue the Modify command with valid command syntax.

Module: DBUGCTSK

XSP2019E Abend "abend" trapped in command during processing of MODIFY command

Explanation: An abend has been trapped in command during the parse of command parameters.

System Action: Code Debug Service Provider command subtask will ignore the command.

User Response: Reissue the Modify command. If the problem persists, contact BMC Support.

Module: DBUGCTSK

XSP2020I Command "command" has completed RC(return_code)

Explanation: The Code Debug Service Provider command subtask has completed the specified command.

System Action: None.

User Response: None.

Module: DBUGCTSK

XSP2101I Job Name ASID Status Type Version Ident Connects

Explanation: The Code Debug Service Provider STATUS command processor header line.

System Action: None.

User Response: None.

Module: DBUGCTSK

XSP2102I -------- ---- -------------- -------- -------- -------- --------

Explanation: The Code Debug Service Provider STATUS command processor header line.

System Action: None.

User Response: None.

Module: DBUGCTSK

XSP2103I job name asid status type ##.##.## ident #

Explanation: The Code Debug Service Provider STATUS command processor detail line.

System Action: None.

User Response: None.

Module: DBUGCTSK

XSP2104I # connected Service Requester address spaces

Explanation: The Code Debug Service Provider STATUS command processor trailer line.

System Action: None.

User Response: None.

Module: DBUGCTSK

XSP2105E SETLOCK obtain for LOCAL lock failed with RC(return_code)

Explanation: The Code Debug Service Provider STATUS command processor encountered errors during the acquisition of the LOCAL lock. The return_code indicates the exception conditions encountered:

RC 4

The lock was already held by the caller.

RC 8

The conditional obtain process was unsuccessful. The lock is owned by another processor.

System Action: Code Debug Service Provider STATUS command will bypass processing.

User Response: Reissue the STATUS command. If the problem persists, contact BMC Support.

Module: DBUGCTSK

XSP2106E SETLOCK obtain for CMS lock failed with RC(return_code)

Explanation: The Code Debug Service Provider STATUS command processor encountered errors during the acquisition of the CMS lock. The return_code indicates the exception conditions encountered:

RC 4

The lock was already held by the caller.

RC 8

The conditional obtain process was unsuccessful. The lock is owned by another processor.

System Action: Code Debug Service Provider STATUS command will bypass processing.

User Response: Reissue the STATUS command. If the problem persists, contact BMC Support.

Module: DBUGCTSK

XSP2107E Storage Obtain for Service Requester List length(length) failed RC(return_code)

Explanation: The Code Debug Service Provider STATUS command processor was unable to obtain storage in MVS subpool 0 for Service Requester List Storage Area of the specified length. The return_code indicates the exception conditions encountered by MVS as follows:

RC 4

Insufficient storage is available.

RC 8

Insufficient central storage to back the request.

RC C

System cannot page in the page table associated with the storage.

System Action: Code Debug Service Provider STATUS command will bypass processing.

User Response: If the problem persists, contact BMC Support.

Module: DBUGCTSK

XSP2108E Storage Release for Service Requester List address(address) length(length) failed RC(return_code)

Explanation: The Code Debug Service Provider STATUS command processor was unable to release storage in MVS subpool 0 for the Service Requester List Storage Area at the specified address and of the specified length. The return_code indicates the exception conditions encountered by MVS as follows:

RC 4

Not all requested virtual storage was freed.

RC 8

No virtual storage was freed because part of the storage area to be freed is fixed.

System Action: Code Debug Service Provider STATUS command processing continues.

User Response: If the problem persists, contact BMC Support.

Module: DBUGCTSK

XSP2201I Service Provider dump has been captured

Explanation: The Code Debug Service Provider DUMP command processor has successfully captured the Service Provider address space SVCDUMP.

System Action: None.

User Response: None.

Module: DBUGCTSK

XSP2202E SETLOCK obtain for LOCAL lock failed with RC(return_code)

Explanation: The Code Debug Service Provider DUMP command processor encountered errors during the acquisition of the LOCAL lock. The return_code indicates the exception conditions encountered:

RC 4

The lock was already held by the caller.

RC 8

The conditional obtain process was unsuccessful. The lock is owned by another processor.

System Action: Code Debug Service Provider DUMP command will bypass processing.

User Response: Reissue the DUMP command. If the problem persists, contact BMC Support.

Module: DBUGCTSK

XSP2203W Partial Service Provider dump has been captured

Explanation: The Code Debug Service Provider DUMP command processor was unable to capture a complete SVCDUMP of the Service Provider address space SVCDUMP.

System Action: None.

User Response: None.

Module: DBUGCTSK

XSP2204E SDUMPX request failed with RC(return_code) RSN(reason_code)

Explanation: The Code Debug Service Provider DUMP command processor encountered errors during the capture of an SVCDUMP. The return_code and reason_code indicates the exception conditions encountered:

RC 8

The system was unable to schedule a dump.


RSN 0

No SVC dump was requested.


RSN 1

An SVC dump was successfully started.


RSN 2

An SVC dump was suppressed because the capture phase of another SVC dump was in progress.


RSN 3

An SVC dump was suppressed by a request by the installation.


RSN 4

An SVC dump was suppressed by a SLIP NODUMP command.


RSN 5

An SVC dump was suppressed because a SYS1.DUMP data set was not available.


RSN 6

An SVC dump was suppressed because an I/O error occurred during the initialization of the SYS1.DUMP data set.


RSN 8

An SVC dump was suppressed because an SRB could not be scheduled to activate the dump tasks in the requested address spaces.


RSN 9

An SVC dump was suppressed because a terminating error occurred in SVC dump before the first dump record was written.


RSN A

An SVC dump was suppressed because a status stop SRB condition was detected.


RSN B

An SVC dump was suppressed by DAE.


RSN 15

The parameter list address is zero.


RSN 16

The parameter list is not a valid SVC or SNAP parameter list.


RSN 17

The caller-supplied data set is not supported.


RSN 18

The start address is greater than or equal to the end address in a storage list.


RSN 19

The caller-supplied header is longer than 100 characters.


RSN 1A

The caller requested a 4K buffer, but did not reserve it.


RSN 1B

A storage list overlaps the 4K buffer


RSN 1C

The caller-supplied DCB is not valid.


RSN 22

The 4K buffer was requested with an SVC dump already in progress.


RSN 25

A non-valid subpool ID was specified in the subpool list.


RSN 28

Part of the parameter list is inaccessible.


RSN 29

The caller-supplied DCB is inaccessible.


RSN 2A

The caller-supplied storage list is inaccessible.


RSN 2B

The caller-supplied header data is inaccessible.


RSN 2C

The caller-supplied ECB is inaccessible.


RSN 2D

The caller’s ASID list is inaccessible.


RSN 2E

The caller’s SUMLIST/SUMLSTA is inaccessible.


RSN 2F

The caller’s SUBPLST list is inaccessible.


RSN 30

The caller’s KEYLIST is inaccessible.


RSN 31

Copies of the SLIP register and PSW are inaccessible.


RSN 32

The caller-supplied SRB is inaccessible.


RSN 33

The version number in the parameter list is not valid.


RSN 34

The caller’s LISTD is inaccessible.


RSN 35

The caller’s SUMLISTL is inaccessible.


RSN 36

The parameter list contains conflicting parameters.


RSN 37

The ID is longer than 50 characters.


RSN 38

The ID is not addressable.


RSN 39

The PSWREGS area is an incorrect length.


RSN 3A

The PSWREGS area is not addressable.


RSN 3B

The symptom record is not valid.


RSN 3C

The symptom record is not addressable.


RSN 3D

The DEB for the caller-supplied DCB is inaccessible.


RSN 3E

SVC dump is already using the maximum amount of virtual storage (as determined by the installation, using the MAXSPACE parameter on the CHNGDUMP command) to process other dumps.


RSN FF

An SVC dump was suppressed for some other unspecified reason.

System Action: Code Debug Service Provider DUMP command will bypass processing.

User Response: Reissue the DUMP command. If the problem persists, contact BMC Support.

Module: DBUGCTSK

XSP2205E Service Requester job_name is not connected

Explanation: The Code Debug Service Provider DUMP command processor has determined the specified Service Requester is not connected.

System Action: Code Debug Service Provider DUMP command will bypass processing.

User Response: Correct the job name and resubmit the DUMP command.

Module: DBUGCTSK

XSP2301I Service Requester job_name disconnect has been scheduled

Explanation: The Code Debug Service Provider DISCONNECT command processor has scheduled the specified Service Requester for asynchronous termination.

System Action: None.

User Response: None.

Module: DBUGCTSK

XSP2302E Service Requester job_name is not connected

Explanation: The Code Debug Service Provider DISCONNECT command processor has determined the specified Service Requester is not connected.

System Action: Code Debug Service Provider DISCONNECT command will bypass processing.

User Response: Correct the job name and resubmit the DISCONNECT command.

Module: DBUGCTSK

XSP2303E Service Requester job_name is pending termination completion Status(status)

Explanation: The Code Debug Service Provider DISCONNECT command processor has determined the specified Service Requester is already pending termination.

System Action: Code Debug Service Provider DISCONNECT command will bypass processing.

User Response: None.

Module: DBUGCTSK

XSP2304E Service Requester job_name is pending Abterm processing IRB(address) STATUS(status)

Explanation: The Code Debug Service Provider DISCONNECT command processor has determined the specified Service Requester is already pending asynchronous termination.

System Action: Code Debug Service Provider DISCONNECT command will bypass processing.

User Response: None.

Module: DBUGCTSK

XSP2305E Service Requester job_name Asynchronous Termination Schedule failed RC(return_code)

Explanation: The Code Debug Service Provider DISCONNECT command processor asynchronous termination schedule failed for the specified Service Requester. The return_code indicates the exception conditions encountered:

RC 4

The Asynchronous Termination Scheduler was passed an invalid Service Descriptor Block.

RC 8

The Asynchronous Termination Scheduler abended during processing.

System Action: Code Debug Service Provider DISCONNECT command will bypass processing.

User Response: Reissue the DISCONNECT command. If the problem persists, contact BMC Support.

Module: DBUGCTSK

XSP2306E SETLOCK obtain for LOCAL lock failed with RC(return_code)

Explanation: The Code Debug Service Provider DISCONNECT command processor encountered errors during the acquisition of the LOCAL lock. The return_code indicates the exception conditions encountered:

RC 4

The lock was already held by the caller.

RC 8

The conditional obtain process was unsuccessful. The lock is owned by another processor.

System Action: Code Debug Service Provider DISCONNECT command will bypass processing.

User Response: Reissue the DISCONNECT command. If the problem persists, contact BMC Support.

Module: DBUGCTSK

XSP2307E SETLOCK obtain for CMS lock failed with RC(return_code)

Explanation: The Code Debug Service Provider DISCONNECT command processor encountered errors during the acquisition of the CMS lock. The return_code indicates the exception conditions encountered:

RC 4

The lock was already held by the caller.

RC 8

The conditional obtain process was unsuccessful. The lock is owned by another processor.

System Action: Code Debug Service Provider DISCONNECT command will bypass processing.

User Response: Reissue the DISCONNECT command. If the problem persists, contact BMC Support.

Module: DBUGCTSK

XSP2501I Service Provider shutdown in progress

Explanation: The Code Debug Service Provider SHUTDOWN command is quiescing the Service Provider address space.

System Action: None.

User Response: None.

Module: DBUGCTSK

XSP2502E SHUTDOWN command rejected, # connected Service Requester address spaces

Explanation: The Code Debug Service Provider SHUTDOWN command processor has detected connected Service Requester address spaces.

System Action: Code Debug Service Provider SHUTDOWN command will bypass processing. This message is followed by message XSP2504I.

User Response: Disconnect all Service Requester address spaces and reissue the SHUTDOWN command. Use transaction XPOF in each connected region. If Remote Operations Command Interface (ROCI) is configured, use the STOP command in ROCI.

Module: DBUGCTSK

XSP2503E SHUTDOWN command rejected, shutdown already in progress

Explanation: The Code Debug Service Provider SHUTDOWN command processor has detected shutdown is already in progress.

System Action: Code Debug Service Provider SHUTDOWN command will bypass processing.

User Response: Wait for Service Provider shutdown to complete.

Module: DBUGCTSK

XSP2504I Issue STATUS command. Use XPOF transaction in listed regions to shutdown Code Debug for CICS.

Explanation: The Code Debug Service Provider rejected the SHUTDOWN command and issued message XSP2502E. The STATUS command lists the connected address spaces that prevent Service Provider shutdown. The XPOF transaction in each of those address spaces causes Code Debug CICS to shut down. Code Debug CICS shut down includes disconnecting from the Service Provider.

System Action: None.

User Response: Follow these steps:



      1. Issue the Code Debug Service Provider STATUS command.
      2. Invoke the XPOF transaction in each listed address space. 
      3. Reissue the STATUS command to confirm that no connected address spaces remain.
      4. Then, the Service Provider SHUTDOWN command may be reissued.

If Remote Operations Command Interface (ROCI) is configured, issuing the STOP command in ROCI is equivalent to invoking the XPOF transaction.

Module: DBUGCTSK

XSP2997E ENQ/DEQ failure for Queue(queue) Resource(resource) RC(return_code)

Explanation: The Code Debug Service Provider command processor encountered an error during the acquisition/relinquishment (ENQ/DEQ) of the Service Requester Anchor Block. The return_code indicates the exception conditions encountered by MVS as follows:

ENQ Return Codes

RC 4

A previous request for control of the same resource has been made for the same task. The task has control of the resource.

RC 14

A previous request for control of the same resource has been made for the same task. The task does not have control of the resource.

RC 18

Environmental error. The limit for the number of concurrent resource requests has been reached. The task does not have control of the resource unless some previous ENQ or RESERVE request caused the task to obtain control of the resource.

DEQ Return Codes

RC 4

The resource (or resources, if you specified GENERIC=YES) has been requested for the task, but the task has not been assigned control of it. The task continues waiting.

RC 8

Control of the resource (or resources, if you specified GENERIC=YES) has not been requested by the active task, or the resource has already been released.

System Action: Code Debug Service Provider command processing terminates.

User Response: Contact BMC Support.

Module: DBUGCTSK

XSP2998E Abend "abend" occurred in Procedure (Function)

Explanation: An abend has been trapped in Procedure during the processing of MVS Function.

System Action: Code Debug Service Provider command subtask is terminated or the command processor will bypass processing.

User Response: Contact BMC Support.

Module: DBUGCTSK

XSP2999E Abend "abend" occurred in Procedure offset "offset"

Explanation: An abend has been trapped in Procedure at offset.

System Action: Code Debug Service Provider command subtask is terminated or the command processor will bypass processing.

User Response: Contact BMC Support.

Module: DBUGCTSK

XSP3001I Now serving TCP address "address" port "portnumber"

Explanation: Code Debug Service Provider has successfully issued the LISTEN command for the address and port number shown.

System Action: None.

User Response: None.

Module: DBUGTCP

XSP3002E DBUGTCP cannot locate TCP/IP

Explanation: Code Debug Service Provider attempted to issue a TCP/IP command and received the ERROR response.

System Action: The TCP subtask terminates immediately.

User Response: Ensure the Service Provider job/started task has the IBM TCP SEZALOAD library in JOBLIB/STEPLIB. If the problem persists, contact BMC Support.

Module: DBUGTCP

XSP3005E TCP subtask attached with invalid parameter address(address)

Explanation: The Code Debug Service Provider TCP subtask was attached with an invalid parameter list at the specified address.

System Action: Code Debug Service Provider TCP subtask initialization is terminated.

User Response: Contact BMC Support.

Module: DBUGTCP

XSP3006E TPCONFIG DD statement not found

Explanation: The Code Debug Service Provider parameters contained MEMBER and PORT, so the Service Provider requires DD statement TPCONFIG. It is not found.

System Action: Code Debug Service Provider TCP subtask initialization is skipped.

User Response: Review the Service Provider JCL; ensure it contains the DD statement TPCONFIG. If it was not present, modify the JCL, shut down this instance of the Service Provider, and resubmit the modified Service Provider JCL. If it was present, contact BMC Support.

Module: DBUGSTC (startup) or DBUGCTSK (INITTCP command)

XSP3007E TPCONFIG dataset open failed

Explanation: The Code Debug Service Provider requires that this data set be a PDS or PDS/E. A different data set organization type was detected.

System Action: Code Debug Service Provider TCP subtask initialization is skipped.

User Response: Review the Service Provider JCL; ensure the DD statement TPCONFIG specifies a PDS or PDS/E. If it does not, modify the JCL, shut down this instance of the Service Provider, and resubmit the modified Service Provider JCL. If it does, contact BMC Support.

Module: DBUGSTC (startup) or DBUGCTSK (INITTCP command)

XSP3008E FIND failed for MEMBER name membername

Explanation: The Code Debug Service Provider FIND for the specified membername failed.

System Action: Code Debug Service Provider TCP subtask initialization is skipped.

User Response: Review the Service Provider JCL; ensure the data set specified by the TPCONFIG DD contains the member in question. If it does not, create the member and use the INITTCP command to start the TCP subtask. If the membername is already present in the data set, contact BMC Support.

Module: DBUGSTC (startup) or DBUGCTSK (INITTCP command)

XSP3009E TPCONFIG invalid record dropped

Explanation: While parsing the XDSS records contained in the TPCONFIG member, a record was found to be incomplete or contain invalid data.

System Action: Code Debug Service Provider TCP subtask initialization is skipped.

User Response: Review the records and correct the error. After correcting it, use the INITTCP command to start the TCP subtask.

Module: DBUGSTC (startup) or DBUGCTSK (INITTCP command)

XSP3010E DBUGTCP ACCEPT API processing module cannot be loaded

Explanation: Code Debug Service Provider attempted to issue a TCP ACCEPT command and received the ERROR response.

System Action: The TCP subtask terminates immediately.

User Response: Ensure the Service Provider job/started task has the IBM TCP SEZALOAD library in JOBLIB/STEPLIB. If the problem persists, contact BMC Support.

Module: DBUGTCP

XSP3011E DBUGTCP TCPservice call RC returncode value ERRNO error number

Explanation: DBUGTCP issued the specified TCP call and received an unexpected returncode/error number combination.

System Action: The TCP subtask terminates immediately.

User Response: Contact BMC Support.

Module: DBUGTCP

XSP3012E DBUGTCP error from SOCKET call

Explanation: Code Debug Service Provider attempted to issue a TCP SOCKET command and received the ERROR response.

System Action: The TCP subtask terminates immediately.

User Response: Ensure the Service Provider job/started task has the IBM TCP SEZALOAD library in JOBLIB/STEPLIB. If the problem persists, contact BMC Support.

Module: DBUGTCP

XSP3013E DBUGTCP busted chain in routinename

Explanation: Code Debug Service Provider found an invalid storage chain while processing in the specified subroutine.

System Action: The TCP subtask terminates immediately.

User Response: Contact BMC Support.

Module: DBUGTCP

XSP3014E Invalid TCP data read, begins with xx

Explanation: Code Debug Service Provider received TCP data that does not conform to its transmission standard.

System Action: The TCP subtask terminates immediately.

User Response: Some other product or system has sent data to the TCP address and port number that this Service Provider instance is “listening” on. Contact your TCP systems programmer.

Module: DBUGTCP

XSP3015I GETHOSTBYNAME could not resolve domainname

Explanation: An TPCONFIG XDSS entry specified a domain name instead of an IP address. DBUGTCP calls your Domain Name Server to convert it to an IP address. Your Domain Name Server was unable to resolve the specified name.

System Action: The TCP subtask skips this XDSS entry.

User Response: Validate that the domain name shown is correct. If it was specified incorrectly, fix the XDSS entry and save it, then use the TERMTCP and INITTCP commands to stop and restart the Service Provider’s TCP subtask. If the domain name shown is correct, contact your TCP systems programmer to have your Domain Name Server updated.

Module: DBUGTCP

XSP3016E HOSTENT structure error errorcode

Explanation: Code Debug Service Provider performed GETHOSTBYNAME and received an unexpected returncode.

System Action: The TCP subtask terminates immediately.

User Response: Contact BMC Support.

Module: DBUGTCP

XSP3017E PORT number must be between 1 and 65535

Explanation: Execution parameter PORT must be in the range 1 - 65535.

System Action: Code Debug Service Provider TCP subtask initialization is skipped.

User Response: Review the execution parameters and correct the error. You can use the INITTCP command to provide the correct PORT number and start the TCP subtask

Module: DBUGSTC (startup) or DBUGCTSK (INITTCP command)

XSP3018E TPCONFIG member contained no valid XDSS data

Explanation: No valid XDSS entries were found in the TPCONFIG data set within the member specified.

System Action: Code Debug Service Provider TCP subtask initialization is skipped.

User Response: Review the TPCONFIG member and correct the entries. After making the corrections, you can use the INITTCP command to the TCP subtask. If the membername itself was incorrect, you can specify the correct membername on the INITTCP command.

Module: DBUGSTC (startup) or DBUGCTSK (INITTCP command)

XSP3020E DBUGTCP description routine routinename error RC nnnn

Explanation: A logic error has occurred within DBUGTCP.

System Action: The TCP subtask terminates immediately.

User Response: Contact BMC Support. Provide the complete “3020E” message, as seen in your Service Provider log.

Module: DBUGTCP

XSP3021E DBUGTCP description routine routinename data begins with xx

Explanation: DBUGTCP received data from DUGDSRV that does not conform to the established standard.

System Action: The unrecognized data is skipped. DBUGTCP continues to process.

User Response: Contact BMC Support. Provide the complete “3021E” message, as seen in your Service Provider log.

Module: DBUGTCP

XSP3022E DBUGTCP description routine routinename

Explanation: A logic error has occurred.

System Action: The TCP subtask terminates immediately.

User Response: Contact BMC Support. Provide the complete “3022E” message, as seen in your Service Provider log.

Module: DBUGTCP

XSP3023E TCP subtask was not initiated - cannot be terminated

Explanation: User has entered a TERMTCP command when the TCP subtask had never been initiated.

System Action: None.

User Response: None.

Module: DBUGCTSK

XSP3024E TCP subtask has already terminated

Explanation: User has entered a TERMTCP command after the TCP subtask had already terminated.

System Action: None.

User Response: None.

Module: DBUGCTSK

XSP3025E TCP subtask cannot be initiated

Explanation: User has entered an INITTCP command, but parameter errors (identified in earlier error messages) prevent the Service Provider from honoring the command.

System Action: None.

User Response: Correct the parameter errors shown in earlier error messages. Some parameters can be re-specified as a part of the INITTCP command. See the Code Debug CICS seeence Manual description of the Service Provider INITTCP command.

Module: DBUGCTSK

XSP3026E TCP subtask is currently active

Explanation: User has entered an INITTCP command while the TCP subtask is already active.

System Action: None.

User Response: None.

Module: DBUGCTSK

XSP3027E TCP BIND failed; port portnumber is in use or is reserved

Explanation: The PORT provided in your Service Provider execution parameters is not available.

System Action: The TCP subtask terminates immediately.

User Response: Contact your TCP systems programmer to have a valid and unique PORT number assigned to this Service Provider.

Module: DBUGTCP

XSP3028E TCP subtask beginning shutdown

Explanation: An error has occurred and has been communicated in an earlier error message. The TCP subtask has begun to shut down.

System Action: The TCP subtask terminates immediately.

User Response: Contact BMC Support. Provide the complete Service Provider log.

Module: DBUGTCP

XSP3030E PORT number must be numeric without leading zeros

Explanation: During parsing of the PORT number, it was determined that the value was non-numeric or contained leading zeros.

System Action: Code Debug Service Provider TCP subtask initialization is skipped.

User Response: Review the TPCONFIG member and correct the entries. After making the corrections, you can use the INITTCP command to the TCP subtask. If the membername itself was incorrect, you can specify the correct membername on the INITTCP command.

Module: DBUGSTC (startup) or DBUGCTSK (INITTCP command)

XSP3031E End of record reached while parsing PORT number

Explanation: During parsing of the PORT number, the end of the record was reached before parsing completed.

System Action: Code Debug Service Provider TCP subtask initialization is skipped.

User Response: Review the TPCONFIG member and correct the entries. After making the corrections, you can use the INITTCP command to the TCP subtask. If the membername itself was incorrect, you can specify the correct membername on the INITTCP command.

Module: DBUGSTC (startup) or DBUGCTSK (INITTCP command)

XSP3032E End of record reached while parsing Domain Name/IP Address

Explanation: During parsing of the Domain Name/IP Address, the end of the record was reached before parsing completed.

System Action: Code Debug Service Provider TCP subtask initialization is skipped.

User Response: Review the TPCONFIG member and correct the entries. After making the corrections, you can use the INITTCP command to the TCP subtask. If the membername itself was incorrect, you can specify the correct membername on the INITTCP command.

Module: DBUGSTC (startup) or DBUGCTSK (INITTCP command)

XSP3033E TPCONFIG RECFM must be VB

Explanation: The RECFM of the TPCONFIG data set must be VB.

System Action: Code Debug Service Provider TCP subtask initialization is skipped.

User Response: User should recreate TPCONFIG file using the same DCB as shown in the SMXDSAMP member JCLTPCNF.

Module: DBUGSTC (startup) or DBUGCTSK (INITTCP command)

XSP3034E TPCONFIG LRECL must be 256

Explanation: The LRECL of the TPCONFIG data set must be 256.

System Action: Code Debug Service Provider TCP subtask initialization is skipped.

User Response: User should recreate TPCONFIG file using the same DCB as shown in the SMXDSAMP member JCLTPCNF.

Module: DBUGSTC (startup) or DBUGCTSK (INITTCP command)

XSP3097I Service Provider at IPaddress port portnumber is connected

Explanation: This Service Provider has successfully communicated with the Service Provider at the IP address and port number shown.

System Action: None.

User Response: None.

Module: DBUGTCP

XSP3098I Service Provider at IPaddress port portnumber is unavailable

Explanation: This Service Provider could not communicate with the Service Provider at the IP address and port number shown.

System Action: None.

User Response: None.

Module: DBUGTCP

XSP3099I Service Provider at IPaddress port portnumber is disconnected

Explanation: This Service Provider was communicating with the Service Provider at the IP address and port number shown, but the connection has now ended.

System Action: None.

User Response: None.

Module: DBUGTCP

XSP3101I Release SSID Image Port IP Address

Explanation: The Code Debug Service Provider SHOWTCP command processor header line.

System Action: None.

User Response: None.

Module: DBUGCTSK

XSP3102I -------- ---- ---- ----- ---------------

Explanation: The Code Debug Service Provider SHOWTCP command processor header line.

System Action: None.

User Response: None.

Module: DBUGCTSK

XSP3103I release SSID image port IPaddress

Explanation: The Code Debug Service Provider SHOWTCP command processor detail line.

System Action: None.

User Response: None.

Module: DBUGCTSK

XSP3104I No data to display

Explanation: The Code Debug Service Provider SHOWTCP command was entered, but the TCP subtask has no data about other Service Providers, or the TCP subtask was not initiated.

System Action: None.

User Response: None.

Module: DBUGCTSK

XSP5001E Subsystem Interface requires a minimum operating system release

Explanation: The Code Debug Service Provider subsystem interface utilizes functions found on the minimum operating system and will not operate properly on prior releases of MVS.

System Action: Code Debug Service Provider subsystem interface processing is terminated.

User Response: See to Prerequisites in the “Planning” section of the Code Debug CICS Installation and Configuration Guide, and upgrade to the minimum supported operating system or above.

Module: DBUGSSI

XSP5002E Subsystem Interface entered in non-authorized state

Explanation: The Code Debug Service Provider was fetched from a non-APF authorized library concatenation.

System Action: Code Debug Service Provider subsystem interface processing is terminated.

User Response: APF authorize the library, which contains the Code Debug Service Provider, and/or remove non-APF authorized libraries from the STEPLIB concatenation. See the Code Debug CICS Installation and Configuration Guide.

Module: DBUGSSI

XSP5003E Subsystem Interface entered in incorrect execution key

Explanation: The Code Debug Service Provider subsystem interface was entered in a PSW key other than one (1).

System Action: Code Debug Service Provider subsystem interface processing is terminated.

User Response: Contact BMC Support.

Module: DBUGSSI

XSP5004E Subsystem Interface Dynamic Storage Manager initialization error

Explanation: The Code Debug Service Provider subsystem interface DSHSRVS has failed to initialize, R15 contains the return code from the dynamic storage handler and R0 contains the corresponding reason code.

RC 4

Allocation failure for dynamic storage handler.


RSN 4

Insufficient storage is available.


RSN 8

Insufficient central storage to back the request.


RSN C

System cannot page in the page table associated with the storage.

RC 8

Load failure for dynamic storage handler (DSHSRVS).

RC C

Error establishing recovery environment (ESTAE|ESTAEX).

RC 10

Incorrect Address Space Control mode (not Primary).

System Action: Code Debug Service Provider subsystem interface processing is terminated.

User Response: Choose the appropriate action:

Allocation failures

Increase the amount of storage available to the private area.

Load failures

Resolve errors related to DSHSRVS load.

Recovery errors

Contact Code Debug CICS Customer Support (Customer Solutions).

Addressing mode errors

Contact Code Debug CICS Customer Support (Customer Solutions).

Module: DBUGSSI

XSP5005I Service Provider SSID(ssid) connection complete

Explanation: The Code Debug Service Provider subsystem interface completed connect processing for the specified subsystem.

System Action: None.

User Response: None.

Module: DBUGSSI

XSP5006I Service Provider SSID(ssid) disconnection complete

Explanation: The Code Debug Service Provider subsystem interface completed disconnect processing for the specified subsystem.

System Action: None.

User Response: None.

Module: DBUGSSI

XSP5007E Service Provider SSID(ssid) connection authorization failed with RC(return_code)

Explanation: The Code Debug Service Provider subsystem security interface has determined the requester address space is not authorized to connect to the specified subsystem.

System Action: The Code Debug Service Provider connect request is denied.

User Response: Determine if the requester address space should be granted access to the Code Debug Service Provider.

Module: DBUGSSI

XSP5010E ALESERV extract Home for Service Requester failed RC(return_code)

Explanation: The Code Debug Service Provider subsystem interface encountered an error during the processing of an ALESERV EXTRACTH request. The return_code indicates the exception conditions encountered by MVS as follows:

RC 24

Program error. AR 1 contained an ALET of 1 on input or contains an ALET associated with the caller’s PASN-AL.

RC 60

System error. An unexpected error occurred. The request was not completed.

System Action: Code Debug Service Provider subsystem interface processing is terminated.

User Response: Contact Code Debug CICS Customer Support (Customer Solutions).

Module: DBUGSSI

XSP5011E Service Requester STOKEN(stoken) mismatch with active Descriptor Block STOKEN(stoken)

Explanation: The Code Debug Service Provider subsystem interface encountered an error while processing a connection request. The STOKEN of the Service Requester does not match the STOKEN in the Descriptor Block on chain.

System Action: Code Debug Service Provider subsystem interface processing is terminated.

User Response: Contact BMC Support.

Module: DBUGSSI

XSP5012E Service Requester connection is pending termination completion Status(status)

Explanation: The Code Debug Service Provider subsystem interface encountered an error while processing a connection request. The Service Requester is pending completion of a prior disconnect request.

System Action: Code Debug Service Provider subsystem interface processing is terminated.

User Response: Contact BMC Support.

Module: DBUGSSI

XSP5013E Storage Allocate for control_block length(length) failed RC(return_code)

Explanation: The Code Debug Service Provider subsystem interface was unable to obtain storage for control block of the specified length.

Control Block

MVS Subpool

Service Requester Descriptor Block

241

Data Services Anchor

241

Task Storage Stack

241

Local System Function Table

205

Module: The return_code indicates the exception conditions encountered by MVS as follows:

RC 4

Insufficient storage is available.

RC 8

Insufficient central storage to back the request.

RC C

System cannot page in the page table associated with the storage.

System Action: Code Debug Service Provider subsystem interface processing is terminated.

User Response: Resolve the shortage of storage in MVS subpool and restart the connection request to the Code Debug Service Provider. If the problem persists, contact BMC Support.

Module: DBUGSTC

XSP5014E TCBTOKEN for Service Requester failed RC(return_code)

Explanation: The Code Debug Service Provider subsystem interface encountered an error during the processing of an TCBTOKEN request. The return_code indicates the exception conditions encountered by MVS as follows:

RC 4

The input STOKEN or TTOKEN does not represent a valid address space.

RC 8

No local lock was held.

RC C

A local lock was held, but not the local lock of the associated address space.

RC 10

The TCB could not be referenced.

RC 14

The TCB did not pass the acronym check.

RC 18

The TCB has terminated.

RC 1C

The TCB associated with the TTOKEN represents a different task than when the TTOKEN was obtained.

RC 20

An unexpected error occurred.

RC 24

The contents of access register 1, used to address the parameter list, were not valid.

RC 28

The parameter list is not valid.

RC 2C

The ASCB address is the address of the wait ASCB. The system cannot obtain the TTOKEN.

RC 30

The task is scheduled for termination, but has not yet terminated.

RC 34

The caller is not running in task mode. This return code is valid only for TYPE=CURRENT, TYPE=PARENT, or TYPE=JOBSTEP.

System Action: Code Debug Service Provider subsystem interface processing is terminated.

User Response: Contact BMC Support.

Module: DBUGSSI

XSP5015E Service Requester SYSEVENT TRANSWAP error RC(return_code)

Explanation: The Code Debug Service Provider subsystem interface encountered an error attempting to make the address space non-swappable which is required for cross memory operations. The return_code indicates the exception conditions encountered by MVS as follows:

RC 4

The address space became non-swappable before it could be swapped out.

System Action: Code Debug Service Provider subsystem interface processing is terminated.

User Response: Contact BMC Support.

Module: DBUGSSI

XSP5016E RESMGR add for Type(type) failed RC(return_code)

Explanation: The Code Debug Service Provider subsystem interface was unable to register the specified resource manager type (AddrSpc|Task) with MVS. The return_code indicates the exception conditions encountered by MVS as follows:

RC 12

Program error. The caller did not provide the address of a word to contain the token of the new resource manager.

RC 16

Program error. The caller did not provide the resource manager description through the ROUTINE parameter.

RC 20

Program error. The TCB address provided did not represent a valid TCB.

RC 24

Program error. The ASID provided did not represent a valid ASCB.

RC 28

Program error. The request type was not ADD or DELETE.

RC 32

Environmental error. RESMGR was unable to obtain storage for a work area it needed to process the request.

RC 36

Program error. The caller held an incorrect lock.

RC 40

Program error. It is not valid to establish a task resource manager for a specific task that is not in the home address space of the requestor.

RC 44

System error. An unrecoverable error occurred while processing the request.

RC 48

Environmental error. RESMGR was unable to obtain storage to maintain information about RESMGR.

RC 52

Program error. The caller is not authorized to use RESMGR.

RC 56

Environmental error. The TCB was already terminating and no more dynamic resource managers can be established for it.

RC 60

Environmental error. The ASCB was already in termination and no more dynamic resource managers can be established for it.

RC 64

Program error. The TTOKEN parameter specified a task in an address space other than the home address space.

System Action: Code Debug Service Provider subsystem interface processing is terminated.

User Response: Choose the appropriate action:

Program error

Contact BMC Support.

Environmental error

Resolve the environmental issues and restart the connection request to the Code Debug Service Provider. If the problem persists, contact BMC Support.

System error

Contact BMC Support.

Module: DBUGSSI

XSP5017E ATSET for AX(ax) failed RC(return_code)

Explanation: The Code Debug Service Provider subsystem interface was unable to set the specified authorization index (PT=YES and SSAR=YES).

System Action: Code Debug Service Provider subsystem interface processing is terminated.

User Response: Contact BMC Support.

Module: DBUGSSI

XSP5018E ETCON failed RC(return_code)

Explanation: The Code Debug Service Provider subsystem interface was unable to connect the Home address space to the Service Provider program call entry table.

System Action: Code Debug Service Provider subsystem interface processing is terminated.

User Response: Contact BMC Support.

Module: DBUGSSI

XSP5019E ALESERV add for Service Provider STOKEN(stoken) failed RC(return_code)

Explanation: The Code Debug Service Provider was unable to add the Service Provider address space to the Home address space PASN-AL. The return_code indicates the exception conditions encountered:

RC 8

Program error. The caller is not EAX-authorized to the specified space; the entry is not added. The ALET returned is incorrect.

RC C

Environmental error. The current access list cannot be expanded. There are no free ALEs and the maximum size has been reached.

RC 10

Environmental error. ALESERV could not obtain storage for an expanded access list.

RC 18

Program error. A problem-state caller with PSW key 8 - F tried to add an entry to the PASN-AL for a space other than a SCOPE=SINGLE data space.

RC 1C

Program error. The caller is holding a lock.

RC 20

Program error. The caller is disabled.

RC 24

Program error. AR 1 contained an ALET of 1 on input or contained an ALET for the PASN-AL.

RC 38

Program error. The input STOKEN is not valid.

RC 4C

Program or environmental error. The space represented by the input STOKEN is not valid for cross memory access.

RC 50

Program error. The ALESERV parameter list is not valid.

RC 54

Program error. The caller tried to add a data space to an access list as a private entry.

RC 5C

Program error. The caller was not authorized to add a data space or a hiperspace to an access list.

RC 60

System error. An unexpected error occurred. The request was not completed.

RC 64

Program error. A problem-state caller with PSW key 8 - F tried to add an entry using CHKEAX=NO.

RC 68

Program error. The caller attempted to add a hiperspace under conditions which are not allowed.

RC 6C

Program error. The caller tried to add an entry for a SCOPE=COMMON data space to a DU-AL.

RC 70

Environmental error. The caller tried to add an entry for a hiperspace and did not have the move-page facility installed.

RC 74

Program error. A problem-state program with PSW key 8 - F has already added an entry for the data space to the PASN-AL.

RC 78

Program error. A problem-state program with PSW key 8 - F tried to add an entry to the PASN-AL. The caller is neither the owner nor the creator of the data space.

System Action: Code Debug Service Provider subsystem interface processing is terminated.

User Response: Contact BMC Support.

Module: DBUGSSI

XSP5020E Storage Deallocate for control_block address(address) length(length) failed RC(return_code)

Explanation: The Code Debug Service Provider subsystem interface was unable to release storage for the control block at the specified address and of the specified length.

Control Block

MVS Subpool

Service Requester Descriptor Block

241

Data Services Anchor

241

Task Storage Stack

241

Local System Function Table

205

Module: The return_code indicates the exception conditions encountered by MVS as follows:

RC 4

Not all requested virtual storage was freed.

RC 8

No virtual storage was freed because part of the storage area to be freed is fixed.

System Action: Code Debug Service Provider subsystem interface processing continues.

User Response: Contact BMC Support.

Module: DBUGSSI

XSP5021E Loader Token token for Service Provider Termination routine is invalid

Explanation: The Code Debug Service Provider subsystem interface has detected an invalid loader token for termination services.

System Action: Code Debug Service Provider resource clean up is bypassed.

User Response: Contact BMC Support.

Module: DBUGSSI

XSP5022W Service Provider Termination routine completed with RC(return_code)

Explanation: The Code Debug Service Provider termination services routine encountered errors during processing. The return_code indicates the exception conditions encountered:

RC 4

Processing errors where encountered during clean up processing. Termination processing complete.

RC 8

Termination services detected an invalid processing mode. Termination cleanup has been bypassed.

RC C

Termination services detected an invalid Service Provider Anchor Block. Termination clean up bypassed.

System Action: Code Debug Service Provider termination completed, resource clean up may be incomplete.

User Response: Contact BMC Support.

Module: DBUGSSI

XSP5023E Chain of Service Requester Descriptor Block failed RC(return_code) RSN(reason_code)

Explanation: The Code Debug Service Provider subsystem interface was unable add the Service Requester Descriptor Block to the active address space chain. The return_code and reason_code indicates the exception conditions encountered:

RC 16

Error during processing.


RSN 16

SETLOCK obtain for LOCAL lock failed.


RSN 20

SETLOCK obtain for CMS lock failed.


RSN 24

Abend occurred during processing.

System Action: Code Debug Service Provider subsystem interface processing terminates.

User Response: Contact BMC Support.

Module: DBUGSSI

XSP5080E Loader Token token for Subsystem Security Interface routine is invalid

Explanation: The Code Debug Service Provider has detected an invalid loader token for Subsystem Security Interface.

System Action: Code Debug Service Provider subsystem interface processing terminates.

User Response: Contact BMC Support.

Module: DBUGSSI

XSP5081E Storage Obtain for Security Interface Parameter List length(length) failed RC(return_code)

Explanation: The Code Debug Service Provider subsystem interface was unable to obtain storage in MVS subpool 129 for the Security Interface Parameter List of the specified length. The return_code indicates the exception conditions encountered by MVS as follows:

RC 4

Insufficient storage is available.

RC 8

Insufficient central storage to back the request.

RC C

System cannot page in the page table associated with the storage.

System Action: Code Debug Service Provider subsystem interface processing terminates.

User Response: Contact BMC Support.

Module: DBUGSSI

XSP5082E Subsystem Security Interface Abend "abend" offset "offset"

Explanation: The Code Debug Service Provider subsystem interface trapped the specified abend at the specified offset while processing an address space authorization request.

System Action: The Code Debug Service Provider connect request is denied.

User Response: Contact BMC Support.

Module: DBUGSSI

XSP5083E Storage Release for Security Interface Parameter List address(address) length(length) failed RC(return_code)

Explanation: The Code Debug Service Provider subsystem interface was unable to release storage in MVS subpool 129 for the Security Interface Parameter List at the specified address and of the specified length. The return_code indicates the exception conditions encountered by MVS as follows:

RC 4

Not all requested virtual storage was freed.

RC 8

No virtual storage was freed because part of the storage area to be freed is fixed.

System Action: Code Debug Service Provider subsystem interface processing continues.

User Response: Contact BMC Support.

Module: DBUGSSI

XSP5090E SETLOCK obtain for LOCAL lock failed with RC(return_code)

Explanation: The Code Debug Service Provider subsystem interface routine encountered errors during the acquisition of the LOCAL lock. The return_code indicates the exception conditions encountered:

RC 4

The lock was already held by the caller.

RC 8

The conditional obtain process was unsuccessful. The lock is owned by another processor.

System Action: Code Debug Service Provider subsystem interface processing continues, first level data capture processing is incomplete.

User Response: Contact BMC Support.

Module: DBUGSSI

XSP5091I Subsystem Interface dump has been captured

Explanation: The Code Debug Service Provider subsystem interface routine has successfully captured the required SVCDUMP.

System Action: Code Debug Service Provider subsystem interface processing continues.

User Response: Ship the SVCDUMP to BMC only when requested by Code Debug CICS Customer Support.

Module: DBUGSSI

XSP5092I Partial Subsystem Interface dump has been captured

Explanation: The Code Debug Service Provider subsystem interface routine was unable to captured a complete SVCDUMP.

System Action: Code Debug Service Provider subsystem interface processing continues.

User Response: Ship the SVCDUMP toBMC only when requested by Code Debug CICS Customer Support.

Module: DBUGSSI

XSP5093E SDUMPX request failed with RC(return_code) RSN(reason_code)

Explanation: The Code Debug Service Provider subsystem interface routine encountered errors during the capture of an SVCDUMP. The return_code and reason_code indicates the exception conditions encountered:

RC 8

The system was unable to schedule a dump.


RSN 0

No SVC dump was requested.


RSN 1

An SVC dump was successfully started.


RSN 2

An SVC dump was suppressed because the capture phase of another SVC dump was in progress.


RSN 3

An SVC dump was suppressed by a request by the installation.


RSN 4

An SVC dump was suppressed by a SLIP NODUMP command.


RSN 5

An SVC dump was suppressed because a SYS1.DUMP data set was not available.


RSN 6

An SVC dump was suppressed because an I/O error occurred during the initialization of the SYS1.DUMP data set.


RSN 8

An SVC dump was suppressed because an SRB could not be scheduled to activate the dump tasks in the requested address spaces.


RSN 9

An SVC dump was suppressed because a terminating error occurred in SVC dump before the first dump record was written.


RSN A

An SVC dump was suppressed because a status stop SRB condition was detected.


RSN B

An SVC dump was suppressed by DAE.


RSN 15

The parameter list address is zero.


RSN 16

The parameter list is not a valid SVC or SNAP parameter list.


RSN 17

The caller-supplied data set is not supported.


RSN 18

The start address is greater than or equal to the end address in a storage list.


RSN 19

The caller-supplied header is longer than 100 characters.


RSN 1A

The caller requested a 4K buffer, but did not reserve it.


RSN 1B

A storage list overlaps the 4K buffer


RSN 1C

The caller-supplied DCB is not valid.


RSN 22

The 4K buffer was requested with an SVC dump already in progress.


RSN 25

A non-valid subpool ID was specified in the subpool list.


RSN 28

Part of the parameter list is inaccessible.


RSN 29

The caller-supplied DCB is inaccessible.


RSN 2A

The caller-supplied storage list is inaccessible.


RSN 2B

The caller-supplied header data is inaccessible.


RSN 2C

The caller-supplied ECB is inaccessible.


RSN 2D

The caller’s ASID list is inaccessible.


RSN 2E

The caller’s SUMLIST/SUMLSTA is inaccessible.


RSN 2F

The caller’s SUBPLST list is inaccessible.


RSN 30

The caller’s KEYLIST is inaccessible.


RSN 31

Copies of the SLIP register and PSW are inaccessible.


RSN 32

The caller-supplied SRB is inaccessible.


RSN 33

The version number in the parameter list is not valid.


RSN 34

The caller’s LISTD is inaccessible.


RSN 35

The caller’s SUMLISTL is inaccessible.


RSN 36

The parameter list contains conflicting parameters.


RSN 37

The ID is longer than 50 characters.


RSN 38

The ID is not addressable.


RSN 39

The PSWREGS area is an incorrect length.


RSN 3A

The PSWREGS area is not addressable.


RSN 3B

The symptom record is not valid.


RSN 3C

The symptom record is not addressable.


RSN 3D

The DEB for the caller-supplied DCB is inaccessible.


RSN 3E

SVC dump is already using the maximum amount of virtual storage (as determined by the installation, using the MAXSPACE parameter on the CHNGDUMP command) to process other dumps.


RSN FF

An SVC dump was suppressed for some other unspecified reason.

System Action: Code Debug Service Provider subsystem interface processing continues, first level data capture processing is incomplete.

User Response: Contact BMC Support.

Module: DBUGSSI

XSP5097E ENQ/DEQ failure for Queue(queue) Resource(resource) RC(return_code)

Explanation: The Code Debug Service Provider subsystem interface encountered an error during the acquisition OR relinquishment (ENQ or DEQ) of the Service Requester Anchor Block. The return_code indicates the exception conditions encountered by MVS as follows:

ENQ Return Codes

RC 4

A previous request for control of the same resource has been made for the same task. The task has control of the resource.

RC 14

A previous request for control of the same resource has been made for the same task. The task does not have control of the resource.

RC 18

Environmental error. The limit for the number of concurrent resource requests has been reached. The task does not have control of the resource unless some previous ENQ or RESERVE request caused the task to obtain control of the resource.

DEQ Return Codes

RC 4

The resource (or resources, if you specified GENERIC=YES) has been requested for the task, but the task has not been assigned control of it. The task continues waiting.

RC 8

Control of the resource (or resources, if you specified GENERIC=YES) has not been requested by the active task, or the resource has already been released.

System Action: Code Debug Service Provider subsystem interface processing is terminated.

User Response: Contact BMC Support.

Module: DBUGSSI

XSP5098E Abend "abend" occurred in Procedure (Function)

Explanation: An abend has been trapped in Procedure during the processing of MVS Function.

System Action: Code Debug Service Provider subsystem interface processing is terminated.

User Response: Contact BMC Support.

Module: DBUGSSI

XSP5099E Abend "abend" occurred in Procedure offset "offset"

Explanation: An abend has been trapped in Procedure at offset.

System Action: Code Debug Service Provider subsystem interface processing is terminated.

User Response: Contact BMC Support.

Module: DBUGSSI

XSP7001E Invalid Primary ASN(asid)

Explanation: The Code Debug Service Provider storage manager has determined that the Primary ASID "asid" is invalid (asid > ASVTMAXU).

System Action: Code Debug Service Provider storage manager request is suppressed.

User Response: Contact BMC Support.

Module: DBUGSMGR

XSP7002E Invalid Service Requester vector entry for ASID(asid)

Explanation: The Code Debug Service Provider storage manager has determined that the Primary address space is not connected to the Code Debug Service Provider (SRVTSRDB = 0).

System Action: Code Debug Service Provider storage manager request is suppressed.

User Response: Contact BMC Support.

Module: DBUGSMGR

XSP7003E Storage Manager already initialized for ASID(asid) SMAB(address)

Explanation: The Code Debug Service Provider storage manager has determined the Primary address space has already initialized storage manager.

System Action: Code Debug Service Provider storage manager request is suppressed.

User Response: Contact BMC Support.

Module: DBUGSMGR

XSP7004E Storage Manager Anchor Block module format error

Explanation: The Code Debug Service Provider storage manager has detected an invalid module format for the storage manager anchor block. The Code Debug Service Provider APF authorized library has been either damaged or violated.

System Action: Code Debug Service Provider storage manager initialization request is suppressed.

User Response: Contact BMC Support.

Module: DBUGSMGR

XSP7005E Procedure parameter area for subpool Pool is invalid

Explanation: The Code Debug Service Provider storage manager has detected invalid subpool entry in the storage manager anchor block. The Code Debug Service Provider APF authorized library has been either damaged or violated.

System Action: Code Debug Service Provider storage manager initialization request is suppressed.

User Response: Contact BMC Support.

Module: DBUGSMGR

XSP7006E Storage Obtain for subpool Pool failed RC(return_code) ID(id) Length(length) SP(subpool) Key(key)

Explanation: The Code Debug Service Provider storage manager was unable to obtain storage for the specified subpool entry. The return_code indicates the exception conditions encountered by MVS as follows:

RC 4

Insufficient storage is available.

RC 8

Insufficient central storage to back the request.

RC C

System cannot page in the page table associated with the storage.

System Action: Code Debug Service Provider storage manager initialization request is terminated.

User Response: Resolve the shortage of storage in specific MVS subpool. If the problem persists, contact BMC Support.

Module: DBUGSMGR

XSP7007E Storage Obtain for area PAM failed RC(return_code) ID(id) Length(length)

Explanation: The Code Debug Service Provider storage manager was unable to obtain storage for the specified subpool entry Page Allocation Map (PAM). The return_code indicates the exception conditions encountered by MVS as follows:

RC 4

Insufficient storage is available.

RC 8

Insufficient central storage to back the request.

RC C

System cannot page in the page table associated with the storage.

System Action: Code Debug Service Provider storage manager initialization request is terminated.

User Response: Resolve the shortage of storage in specific MVS subpool. If the problem persists, contact BMC Support.

Module: DBUGSMGR

XSP7008E Storage Release for subpool Pool failed RC(return_code) ID(id) Length(length) SP(subpool) Key(key)

Explanation: The Code Debug Service Provider storage manager was unable to release storage for the specified subpool entry. The return_code indicates the exception conditions encountered by MVS as follows:

RC 4

Not all requested virtual storage was freed.

RC 8

No virtual storage was freed because part of the storage area to be freed is fixed.

System Action: Code Debug Service Provider storage manager processing continues.

User Response: Contact BMC Support.

Module: DBUGSMGR

XSP7009E Storage Release for area PAM failed RC(return_code) ID(id) Length(length)

Explanation: The Code Debug Service Provider storage manager was unable to release storage for the specified subpool entry Page Allocation Map (PAM). The return_code indicates the exception conditions encountered by MVS as follows:

RC 4

Not all requested virtual storage was freed.

RC 8

No virtual storage was freed because part of the storage area to be freed is fixed.

System Action: Code Debug Service Provider storage manager processing continues.

User Response: Contact BMC Support.

Module: DBUGSMGR

XSP7010E Storage Manager not initialized for ASID(asid)

Explanation: The Code Debug Service Provider storage manager has determined the Primary address space has not initialized storage manager.

System Action: Code Debug Service Provider storage manager request is suppressed.

User Response: Contact BMC Support.

Module: DBUGSMGR

XSP7098E Abend "abend" occurred in Procedure (Function)

Explanation: An abend has been trapped in Procedure during the processing of MVS Function.

System Action: Code Debug Service Provider storage manager request is terminated.

User Response: Contact BMC Support.

Module: DBUGSMGR

XSP7099E Abend "abend" occurred in Procedure offset "offset"

Explanation: An abend has been trapped in Procedure at offset.

System Action: Code Debug Service Provider storage manager request is terminated.

User Response: Contact BMC Support.

Module: DBUGSMGR

XSP8001E Library DD statement ddname not found in TIOT

Explanation: The Code Debug Service Provider program manager was unable to locate to specified ddname in the TIOT.

System Action: Code Debug Service Provider program manager open request is suppressed.

User Response: Contact BMC Support.

Module: DBUGPMGR

XSP8002E Invalid DD statement for Library ddname+# type type

Explanation: The Code Debug Service Provider program manager has detected an invalid DD statement in the Library concatenation.

System Action: Code Debug Service Provider program manager open request is suppressed.

User Response: Correct the Library concatenation DD statement.

Module: DBUGPMGR

XSP8003E SWA Manager request for Library ddname failed RC(return_code)

Explanation: The Code Debug Service Provider program manager open service was unable to complete SWAREQ processing for the specified ddname. The return_code indicates the exception conditions encountered by MVS as follows:

RC 8

The SVA in the SWA prefix was not valid.

RC 24

You attempted to read a block that was not yet written.

RC 28

The pointer to the EPAL was not valid.

System Action: Code Debug Service Provider program manager open request is suppressed.

User Response: Contact BMC Support.

Module: DBUGPMGR

XSP8004E OBTAIN request for Library ddname+# failed RC(return_code)

Explanation: The Code Debug Service Provider program manager open service was unable to obtain VTOC information for the specified Library concatenation entry. The return_code indicates the exception conditions encountered by MVS as follows:

RC 4

The required volume was not mounted.

RC 8

The format-1 DSCB was not found in the VTOC of the specified volume.

RC C

A permanent I/O error was encountered, or an invalid format-1 DSCB was found when processing the specified volume, or an unexpected error return code was received from CVAF (common VTOC access facility).

RC 10

Invalid work area pointer.

System Action: Code Debug Service Provider program manager open request is suppressed.

User Response: Correct the Library concatenation DD statement. If the problem persists, contact BMC Support.

Module: DBUGPMGR

XSP8005E Incorrect organization "dsorg" for Library ddname+#

Explanation: The Code Debug Service Provider program manager open service detected an invalid data set organization (DSORG) for the specified Library concatenation entry.

System Action: Code Debug Service Provider program manager open request is suppressed.

User Response: Correct the Library concatenation DD statement.

Module: DBUGPMGR

XSP8006E Incorrect record format "recfm" for Library ddname+#

Explanation: The Code Debug Service Provider program manager open service detected an invalid data set record format (RECFM) for the specified Library concatenation entry.

System Action: Code Debug Service Provider program manager open request is suppressed.

User Response: Correct the Library concatenation DD statement.

Module: DBUGPMGR

XSP8007E Storage Obtain for Library ddname DCB length(length) failed RC(return_code)

Explanation: The Code Debug Service Provider program manager open service was unable to obtain storage in MVS subpool 130 for Library DCB of the specified length. The return_code indicates the exception conditions encountered by MVS as follows:

RC 4

Insufficient storage is available.

RC 8

Insufficient central storage to back the request.

RC C

System cannot page in the page table associated with the storage.

System Action: Code Debug Service Provider program manager open request is suppressed.

User Response: Resolve the shortage of storage in MVS subpool 130 (Private). If the problem persists, contact BMC Support.

Module: DBUGPMGR

XSP8008E Open for Library ddname failed RC(return_code) DCBOFLGS(flags)

Explanation: The Code Debug Service Provider program manager open service was unable to open the specified Library DCB. The return_code indicates the exception conditions encountered by MVS as follows:

RC 4

All data sets were opened successfully, but one or more warning messages were issued.

RC 8

At least one data set (VSAM or non-VSAM) was not opened successfully; the access method control block was restored to the contents it had before OPEN was issued; or, if the data set was already open, the access method control block remains open and usable and is not changed.

RC C

A non-VSAM data set was not opened successfully when a non-VSAM and a VSAM data set were being opened at the same time; the non-VSAM data control block was not restored to the contents it had before OPEN was issued (and the data set cannot be opened without restoring the control block).

System Action: Code Debug Service Provider program manager open request is suppressed.

User Response: Correct errors with the specified Library DCB. If the problem persists, contact BMC Support.

Module: DBUGPMGR

Explanation: The Code Debug Service Provider program manager open service was unable to open the specified Library DCB. The return_code indicates the exception conditions encountered by MVS as follows:

RC 4

All data sets were opened successfully, but one or more warning messages were issued.

RC 8

At least one data set (VSAM or non-VSAM) was not opened successfully; the access method control block was restored to the contents it had before OPEN was issued; or, if the data set was already open, the access method control block remains open and usable and is not changed.

RC C

A non-VSAM data set was not opened successfully when a non-VSAM and a VSAM data set were being opened at the same time; the non-VSAM data control block was not restored to the contents it had before OPEN was issued (and the data set cannot be opened without restoring the control block).

System Action: Code Debug Service Provider program manager open request is suppressed.

User Response: Correct errors with the specified Library DCB. If the problem persists, contact BMC Support.

Module: DBUGPMGR

XSP8009E DEBCHK for Library DCB(address) failed RC(return_code)

Explanation: The Code Debug Service Provider program manager open service was unable to open validate the DEB for the specified Library DCB. The return_code indicates the exception conditions encountered by MVS as follows:

RC 4

Either (a) the DEB table associated with the job step does not exist; or (b) the DEBTBLOF field of the DEB was set to zero or a negative number, or was larger than the DEB table; or (c) register 1 did not contain the same address as the DEB table entry.

RC 8

An invalid TYPE was specified. (The DEBCHK routine was entered by a branch, not by the macro.)

RC C

Your program was not authorized and TYPE was not VERIFY.

RC 10

DEBDCBAD did not contain the address of the DCB (or ACB) that was passed to the DEBCHK routine.

RC 14

The AM value does not equal the value in the DEBAMTYP field.

RC 18

The DEB is not on the DEB chain and TYPE=ADD was specified.

RC 1C

TYPE=ADD was specified for a DEB that was already entered in the DEB table.

RC 20

The DEB table exceeded the maximum size and TYPE=ADD.

System Action: Code Debug Service Provider program manager open request is suppressed.

User Response: Contact BMC Support.

Module: DBUGPMGR

XSP8010E Illegal Close for Library ddname DCB(return_code)

Explanation: The Code Debug Service Provider program manager close service was requested to close an illegal Library DCB (LINKLIB or TASKLIB) as specified.

System Action: Code Debug Service Provider program manager close request is suppressed.

User Response: Contact BMC Support.

Module: DBUGPMGR

XSP8011E Close for Library ddname failed RC(return_code)

Explanation: The Code Debug Service Provider program manager close service was unable to close the specified Library DD. The return_code indicates the exception conditions encountered by MVS as follows:

RC 4

At least one data set (VSAM or non-VSAM) was not closed successfully.

System Action: Code Debug Service Provider program manager close request is suppressed.

User Response: Correct errors with the specified Library. If the problem persists, contact BMC Support.

Module: DBUGPMGR

XSP8012W Storage Release for Library ddname DCB address(address) length(length) failed RC(return_code)

Explanation: The Code Debug Service Provider program manager was unable to release storage in MVS subpool 130 for library DCB at the specified address and of the specified length. The return_code indicates the exception conditions encountered by MVS as follows:

RC 4

Not all requested virtual storage was freed.

RC 8

No virtual storage was freed because part of the storage area to be freed is fixed.

System Action: Code Debug Service Provider program manager processing continues.

User Response: Contact BMC Support.

Module: DBUGPMGR

XSP8013E Invalid BLDL list address(address) passed to procedure

Explanation: The Code Debug Service Provider program manager directory fetch service was passed an invalid BLDL list address.

System Action: Code Debug Service Provider program manager directory fetch request is suppressed.

User Response: Contact BMC Support.

Module: DBUGPMGR

XSP8014E BLDL for Library ddname DCB(address) failed RC(return_code) RSN(reason_code)

Explanation: The Code Debug Service Provider program manager directory fetch service was unable to retrieve the directory information for the specified Library DD. The return_code and reason_code indicates the exception conditions encountered by MVS as follows:

RC 8

Error during processing.


RSN 0

A permanent I/O error was detected when the system attempted to search the directory.


RSN 4

Insufficient virtual storage was available.


RSN 8

Invalid data extent block (DEB).

System Action: Code Debug Service Provider program manager directory fetch request is suppressed.

User Response: Correct errors with the specified Library. If the problem persists, contact BMC Support.

Module: DBUGPMGR

XSP8015E Module "module" in Library ddname is not loadable

Explanation: The Code Debug Service Provider program manager load service was unable to load the specified module from the specified Library DD (not loadable).

System Action: Code Debug Service Provider program manager load service request is suppressed.

User Response: Contact BMC Support.

Module: DBUGPMGR

XSP8016E Load for Module "module" in Library ddname failed PDS2LIBF(flags)

Explanation: The Code Debug Service Provider program manager load service was unable to load the specified module from the specified Library DD (DCB/Directory mismatch).

System Action: Code Debug Service Provider program manager load service request is suppressed.

User Response: Contact BMC Support.

Module: DBUGPMGR

XSP8017E Storage Obtain for Module "module" length(length) failed RC(return_code)

Explanation: The Code Debug Service Provider program manager load service was unable to obtain storage in MVS subpool 130|241|252 for the specified module. The return_code indicates the exception conditions encountered by MVS as follows:

RC 4

Insufficient storage is available.

RC 8

Insufficient central storage to back the request.

RC C

System cannot page in the page table associated with the storage.

System Action: Code Debug Service Provider program manager load service request is suppressed.

User Response: Resolve the shortage of storage in specified MVS subpool. If the problem persists, contact BMC Support.

Module: DBUGPMGR

XSP8018E Load for Module "module" in Library ddname failed RC(completion_code) RSN(reason_code)

Explanation: The Code Debug Service Provider program manager load service was unable to fetch the specified module. The completion_code and reason_code indicates the exception conditions encountered by MVS.

System Action: Code Debug Service Provider program manager load service request is suppressed.

User Response: Contact BMC Support.

Module: DBUGPMGR

XSP8019E Module "module" in Library ddname has an invalid module header

Explanation: The Code Debug Service Provider program manager load service has detected an invalid module header during the fetch of module "module". The Code Debug Service Provider APF authorized library has been either damaged or violated.

System Action: Code Debug Service Provider program manager load service request is suppressed.

User Response: Contact BMC Support.

Module: DBUGPMGR

XSP8020E Module "module" in Library ddname has an invalid release stamp "stamp"

Explanation: The Code Debug Service Provider program manager load service has detected an invalid release stamp during the fetch of module "module". The Code Debug Service Provider APF authorized library has been either damaged or violated.

System Action: Code Debug Service Provider program manager load service request is suppressed.

User Response: Contact BMC Support.

Module: DBUGPMGR

XSP8021E Storage Obtain for Module "module" XTLST length(length) failed RC(return_code)

Explanation: The Code Debug Service Provider program manager load service was unable to obtain storage in MVS subpool 255 for the specified module’s XTLST entry of the specified length. The return_code indicates the exception conditions encountered by MVS as follows:

RC 4

Insufficient storage is available.

RC 8

Insufficient central storage to back the request.

RC C

System cannot page in the page table associated with the storage.

System Action: Code Debug Service Provider program manager load service request is suppressed.

User Response: Resolve the shortage of storage in MVS subpool 255 (Private LSQA/ELSQA. If the problem persists, contact BMC Support.

Module: DBUGPMGR

XSP8022E Storage Obtain for Module "module" CDE length(length) failed RC(return_code)

Explanation: The Code Debug Service Provider program manager load service was unable to obtain storage in MVS subpool 255 for the specified module’s CDE entry of the specified length. The return_code indicates the exception conditions encountered by MVS as follows:

RC 4

Insufficient storage is available.

RC 8

Insufficient central storage to back the request.

RC C

System cannot page in the page table associated with the storage.

System Action: Code Debug Service Provider program manager load service request is suppressed.

User Response: Resolve the shortage of storage in MVS subpool 255 (Private LSQA/ELSQA. If the problem persists, contact BMC Support.

Module: DBUGPMGR

XSP8023E Storage Obtain for Module "module" LLE length(length) failed RC(return_code)

Explanation: The Code Debug Service Provider program manager load service was unable to obtain storage in MVS subpool 255 for the specified module’s LLE entry of the specified length. The return_code indicates the exception conditions encountered by MVS as follows:

RC 4

Insufficient storage is available.

RC 8

Insufficient central storage to back the request.

RC C

System cannot page in the page table associated with the storage.

System Action: Code Debug Service Provider program manager load service request is suppressed.

User Response: Resolve the shortage of storage in MVS subpool 255 (Private LSQA/ELSQA. If the problem persists, contact BMC Support.

Module: DBUGPMGR

XSP8024E Storage Release for Module "module" address(address) length(length) failed RC(return_code)

Explanation: The Code Debug Service Provider program manager load service was unable to release storage in MVS subpool 130|241|252 for the specified load module at the specified address and of the specified length. The return_code indicates the exception conditions encountered by MVS as follows:

RC 4

Not all requested virtual storage was freed.

RC 8

No virtual storage was freed because part of the storage area to be freed is fixed.

System Action: Code Debug Service Provider program manager load service request is suppressed.

User Response: Contact BMC Support.

Module: DBUGPMGR

XSP8025E Storage Release for Module "module" XTLST address(address) length(length) failed RC(return_code)

Explanation: The Code Debug Service Provider program manager load service was unable to release storage in MVS subpool 255 for the XTLST for the specified module at the specified address and of the specified length. The return_code indicates the exception conditions encountered by MVS as follows:

RC 4

Not all requested virtual storage was freed.

RC 8

No virtual storage was freed because part of the storage area to be freed is fixed.

System Action: Code Debug Service Provider program manager load service request is suppressed.

User Response: Contact BMC Support.

Module: DBUGPMGR

XSP8026E Storage Release for Module "module" CDE address(address) length(length) failed RC(return_code)

Explanation: The Code Debug Service Provider program manager load service was unable to release storage in MVS subpool 255 for the CDE for the specified module at the specified address and of the specified length. The return_code indicates the exception conditions encountered by MVS as follows:

RC 4

Not all requested virtual storage was freed.

RC 8

No virtual storage was freed because part of the storage area to be freed is fixed.

System Action: Code Debug Service Provider program manager load service request is suppressed.

User Response: Contact BMC Support.

Module: DBUGPMGR

XSP8027E Storage Release for Module "module" LLE address(address) length(length) failed RC(return_code)

Explanation: The Code Debug Service Provider program manager load service was unable to release storage in MVS subpool 255 for the LLE for the specified module at the specified address and of the specified length. The return_code indicates the exception conditions encountered by MVS as follows:

RC 4

Not all requested virtual storage was freed.

RC 8

No virtual storage was freed because part of the storage area to be freed is fixed.

System Action: Code Debug Service Provider program manager load service request is suppressed.

User Response: Contact BMC Support.

Module: DBUGPMGR

XSP8028E Invalid Module Token value X"token"

Explanation: The Code Debug Service Provider program manager delete service was passed an invalid module token value.

System Action: Code Debug Service Provider program manager delete service request is suppressed.

User Response: Contact BMC Support.

Module: DBUGPMGR

XSP8029E Module Token/Name mismatch, Token X"token" Name "module"

Explanation: The Code Debug Service Provider program manager delete service was unable to validate the module token passed with the specified Module name.

System Action: Code Debug Service Provider program manager delete service request is suppressed.

User Response: Contact BMC Support.

Module: DBUGPMGR

XSP8030E Invalid parameter passed to procedure

Explanation: The Code Debug Service Provider program manager delete service was passed an invalid parameter list.

System Action: Code Debug Service Provider program manager delete service request is suppressed.

User Response: Contact BMC Support.

Module: DBUGPMGR

XSP8031E Delete for Module "module" failed RC(return_code)

Explanation: The Code Debug Service Provider program manager delete service was unable to remove the specified module from MVS storage. The return_code indicates the exception conditions encountered by MVS as follows:

RC 4

Request was not issued for this module, or attempt was made to delete a system module.

System Action: Code Debug Service Provider program manager delete service request is suppressed.

User Response: Contact BMC Support.

Module: DBUGPMGR

XSP8098E Abend "abend" occurred in Procedure (Function)

Explanation: An abend has been trapped in Procedure during the processing of MVS Function.

System Action: Code Debug Service Provider program manager processing is terminated.

User Response: Contact BMC Support.

Module: DBUGPMGR

XSP8099E Abend "abend" occurred in Procedure offset "offset"

Explanation: An abend has been trapped in Procedure at offset.

System Action: Code Debug Service Provider program manager processing is terminated.

User Response: Contact BMC Support.

Module: DBUGPMGR

XSP9001I Automatic Restart Manager event event complete

Explanation: The Code Debug Service Provider has successfully completed the specified event notification with Automatic Restart Management.

Register

The Code Debug Service Provider has notified Automatic Restart Management that initialization has begun.

Reregister

The Code Debug Service Provider has notified Automatic Restart Management that restart initialization has begun.

Ready

The Code Debug Service Provider has notified Automatic Restart Management that initialization or restart initialization has completed.

System Action: None.

User Response: None.

Module: DBUGSTC

XSP9002W Automatic Restart Manager event event failed RC(return_code) RSN(reason_code)

Explanation: The Code Debug Service Provider has failed during the specified event notification with Automatic Restart Management. For Automatic Services Management request macro IXCARM, see the z/OS MVS Programming: Sysplex Services Reference manual Return and Reason Codes section.

Register

The Code Debug Service Provider has encountered a failure during Automatic Restart Management register notification processing.

Reregister

The Code Debug Service Provider has encountered a failure during Automatic Restart Management reregister notification processing.

Ready

The Code Debug Service Provider has encountered a failure during Automatic Restart Management ready notification processing.

System Action: Code Debug Service Provider initialization is continued without Automatic Restart Management support.

User Response: Correct error condition, then shut down and restart the Code Debug Service Provider.

Module: DBUGSTC


 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*