Code Debug TSO Messages

XPD@@01E

INCORRECT OR MISSING EXEC PARM

Explanation: This message can be generated by both the started task and the file formatting program. The only time that it may lead to confusion is when BLK parameter is too small or the QNAME is too short.

User Response: If you see this message generated by a file formatting program and all parameters appear correct, BLK is most likely too small. Please see to the suggested BLK parameter formula.

XPD@@02E       

DISABLE BLKSIZE OPTIMIZATION, WHATEVER IT IS

Explanation: There are I/O optimization products (i.e., ULTIMIZER) that can alter the BLKSIZE. This error is generated when the DCB’s BLKSIZE changes after an OPEN.

User Response: Code Debug requires precise BLKSIZE as specified in EXEC PARM.

XPD@@03E 

THIS IS NOT A STARTED TASK

Explanation: It must be a started task.

User Response: Please do not submit from TSO.

XPD@@04E

ENQ PROPAGATING TASK ALREADY STARTED

Explanation: The operator already issued a START command for our started task, and it is operating.

User Response: Another START command is neither needed nor allowed.

XPD@@05W

DATA SET FOR ENQ PROPAGATION IS FULL

Explanation: This is a warning. The shared file is full and the appropriate action is to stop all started tasks and create a larger file.

User Response: If stopping all started tasks is not possible at this time, you may wait and all terminating Code Debug Batch Connect jobs will be removed from the shared file. This will free up space within the shared file. At that point, the started task will recognize this and continue.

XPD@@06E

CODE DEBUG ENQS PROPAGATED
WITHOUT STARTED TASK

Explanation: In this situation, either CA-MIM is not active or some other means of propagating SYSTEMS ENQs is available.

User Response: Due to the fact that the SYSTEMS ENQs are propagated, the started task is redundant and therefore unnecessary.

XPD0000

UNABLE TO TERMINATE TEST
REQUESTED BY CODE DEBUG MODULE

Module: ADSRA000

User Response: Contact your internal technical support immediately. BMC needs to be informed of all circumstances leading to this message.

XPD0001

LMS ERROR RC = XX, REASON CODE = YYY

Module: ADSRA001

Explanation: An error was encountered in License Management software.

User Response: Ensure LMSINIT has been run and subsystem is operational. Otherwise, Contact BMC Support with the return and reason codes.

XPD0007 

ESTAE MACRO ERROR - RETURN CODE X(2)

Module: ADSRA105

Explanation: A critical error occurred while a STAE/ESTAE macro was being issued.

User Response: Contact your internal technical support.

XPD0011

VTAM NODE: A(8) USER: B(8) JOBNAME: C(8)

Module: CSSMVS

Explanation: A Batch Connect job is ready for connection—A(8) is the VTAM NODE, B(8) is the userid, C(8) is the job name. Messages XPD0012 and XPD0013 will follow.

XPD0012

JOBNUMBER: D(8) STEP: E(8) PROCSTEP: F(8)

Module: CSSMVS

Explanation: This is a continuation of message XPD0011. D(8) is the job number. E(8) is the step name. F(8) is the procedure step name, if any. Message XPD0013 follows.

XPD0013

IS WAITING FOR CONNECTION ON SYSTEM G(4)

Module: CSSMVS

Explanation: This is a continuation of message XPD0012. G(4) is the system ID.

XPD0025

STORAGE AVAILABLE FOR SIMULATE LIST

Module: ADSRA058

Explanation: No main storage was available to build a list of simulated module names.

User Response: Increase the REGION size and try the test again.

XPD0033

MEMORY ALLOCATION FAILED. BYTES REQUESTED N(4) MNEMONIC X(8)

Module: ADSRA003 and ADSRA007

Explanation: Allocation of virtual storage in subpool zero failed for Code Debug control block allocation.

User Response: If the length specified seems reasonable, increase the REGION size; or contact your internal technical support.

XPD0034 

CONTROL STACK ENTRY MAXIMUM EXCEEDED

Module: ADSRA106

Explanation: The number of hierarchical levels in Code Debug exceeds the control stack capacity. This stack is used as an internal control mechanism by Code Debug to maintain proper linkages between call interfaces.

User Response: Contact your internal technical support.

XPD0054

OPEN FAILED FOR DDNAME X(8)

Module: ADSRA170

Explanation: The data set from which Code Debug obtains its input could not be opened.

User Response: Check your batch JCL stream, TSO CLIST, or Code Debug TSO Installation Defaults panel to include the appropriate DD. If the problem persists, contact your internal technical support.

XPD0067

GETMAIN FAILED. BYTES REQUESTED - N(4)

Module: ADSRA097 and ADSRA553

Explanation: An attempt to acquire additional storage failed.

User Response: Increase the REGION allocated to the TSO logon session or the JOB step.

XPD0070

INVALID TRANSLATE OVERRIDES: X(40)

Module: ADSRA007

Explanation: The data supplied in the CTLTRLAT field has failed the validation check.

User Response: Ensure that valid values were supplied for the CTLTRLAT field during the product installation. Changes to offsets X'00' through X'40' and/or alphanumeric offsets are not allowed.

XPD0071

OVERRIDE VALUES CONTINUED: X(40)

Module: ADSRA007

Explanation: A continuation of the display from message XPD0070. Displays the next forty bytes of the CTLTRLAT field.

User Response: See message XPD0070.

XPD0087

BREAKPOINT OFFSET N(4)
EXCEEDS THE SIZE OF MODULE X(8)

Module: ADSRA104 and ADSRA601

Explanation: An interrupt address is invalid in the module for which a monitor event occurred.

User Response: Ensure that the member keyword for the appropriate Code Debug command was specified. If the problem cannot be resolved, contact your internal technical support.

XPD0099

GLOBAL SYSTEM PARAMETER NOT FOUND - X(8)

Module: ADSRA110

Explanation: An invalid condition was detected in an Code Debug control block during processing of the current command.

User Response: This message must be communicated to your internal technical support.

XPD0100

THIS MODULE FOR MVS - CMS USE ADSRA232

Module: ADSRA242

Explanation: Module ADSRA242 can only be used to list the sizes of modules running under the MVS operating system.

User Response: For CMS, use module ADSRA232.

XPD0101

NO SBL CELLS TGT ENTRY FOR X(8)

Module: ADSRA189

Explanation: The DDIO data set member for the specified module does not contain a task global table record for the secondary base locator cells. No processing will occur for fields which are assigned secondary base locators (see DMAP for module).

XPD0102

X(8) NOT FOUND IN USER LIBRARY

Module: ADSRA189

Explanation: The specified load module was not found in the library allocated under the XTASKLIB ddname. This condition precludes referencing of fields with secondary base locators.

XPD0103

RDB FOR FIELD RETRIEVAL
HAS NO EDB NOTIFY TECHNICAL SUPPORT

Module: ADSRA189

Explanation: The Code Debug element display block retrieve module has been passed a record display block without an EDB pointer.

User Response: This condition must be reported to your internal technical support.

XPD0104

NESTING DEPTH OF 24 EXCEEDED FOR X(30)

Module: ADSRA189

Explanation: The maximum record hierarchy depth of twenty-four levels has been exceeded for the specified data element. As a result, the processing of the current command is terminated.

User Response: None.

XPD0105

RECORD HIERARCHY LEVEL COUNT
NEGATIVE NOTIFY TECHNICAL SUPPORT

Module: ADSRA189

Explanation: The level counter used by the Code Debug record hierarchy scan module was decremented until it became negative. Processing of the current command is terminated.

User Response: This condition should be reported to your internal technical support.

XPD0111

NO MODULES FOUND IN RB OR LOAD LISTS

Module: ADSRA242

Explanation: An attempt was made to display the sizes of all modules in the RB or LOAD list, but none were found.

User Response: This is presumed to be an Code Debug problem; therefore, contact your internal technical support.

XPD0113

MACHINE INSTRUCTION (iiii oooo) ENCOUNTERED
BY CODE DEBUG:
MEMBER=lmod, MODULE=csect,
OFFSET=xxxxxxxx, ADDRESS=xxxxxxxx

Module: ADSRA129

Explanation: An unrecognized instruction was encountered in a user program by Code Debug while attempting to resume execution. The instruction will be executed in the application after any breakpoint has been removed.

User Response: None.

XPD0118

SVRB SEARCH UNRESOLVED AFTER 5 LEVELS

Module: ADSRA016

Explanation: SVRB could not be found after five levels of the request block chain were searched.

User Response: Contact your internal technical support.

XPD0121

UNCORRECTABLE I/O ERROR FOR
MEMBER C(8) IN C(8) SYNAD GPR 1 CONTENTS = X(4)

Module: ADSRA512

Explanation: An I/O error occurred during an attempt to access the MEMBER and DD as specified in the message.

User Response: Verify correct use of DCB information for all data sets allocated per the DD specified. For example:

Ensure that libraries have a RECFM of U and are usable load module libraries.

Ensure that LRECL/BLKSIZE are valid and consistent for all data sets.

XPD0125

CODE DEBUG = N(4) OTHER = N(4) TOTAL = N(4)

Module: ADSRA242

Explanation: The accumulated totals of both Code Debug and subpool zero are printed as the result of an XTEST ADSRA242 command.

User Response: None.

XPD0138

SIZE OF X(8) AT N(4) IS N(4)

Module: ADSRA242

Explanation: This is an informational message printed to communicate the module size and location for XTEST ADSRA242.

User Response: None.

XPD0150

I/O ERROR WHILE READING MODULE X(8)

Module: ADSRA097

Explanation: There may be a problem with the module’s addressing mode.

User Response: Contact your internal technical support.

XPD0151

DELETE OF USER MODULE X(8) FAILED - RC = N(2)

Module: ADSRA454

Explanation: An attempt to delete an Code Debug or user module failed.

User Response: Probable Code Debug system error. Contact your internal technical support.

XPD0152

TROUBLE CLOSING USER FILES X(8)

Module: ADSRA020 and ADSRA097

Explanation: Code Debug could not close user files.

User Response: Either the files were not opened, or you need to try RETEST and then use the EXIT command.

XPD0153

DD X(8) NOT OPEN, CANNOT DO FUNCTION

Module: ADSRA097

Explanation: Code Debug cannot perform any function on the indicated ddname and associated data set because it is not open.

User Response: None.

XPD0154

ERROR DOING JFCB FOR DDNAME X(8)

Module: ADSRA097

Explanation: An I/O operation error (possibly a READ error) was detected while the Job File Control Block was performed for the indicated ddname.

User Response: None.

XPD0155

NO STORAGE FOR RDJFCB GETMAIN

Module: ADSRA559

Explanation: In the type N(13) form of the XA 2.2 RDJFCB, a GETMAIN was done and failed.

User Response: Try a larger REGION size.

XPD0157

TYPE 07 OF RDJFCB FAILED. CHECK THE FILE ALLOCATIONS.

Module: ADSRA559

Explanation: In the type X’07’ form of the RDJFCB, a return code greater than zero was encountered. This should not happen at this point.

User Response: Contact your internal technical support.

XPD0159

THE ONLY OPTIONS FOR RA206 ARE OPEN (1), CLOSE (2), AND BLDL (3)

Module: ADSRA097

Explanation: Code Debug internal message. The OPTION parameter received in ADSRA097 is incorrect.

User Response: Contact your internal technical support.

XPD0160

TGT DID NOT POINT TO EXPECTED MCB

Module: ADSRA130

Explanation: The Task Global Table did not point to the Module Control Block.

User Response: Contact your internal technical support.

XPD0162

NO TYPE T RECORD FOUND FOR TGT
FIELD IN MODULE C(8) - CHANGE
LOGGING SUSPENDED

Module: ADSRA134

Explanation: One of the TGT (Task Global Table) fields required for review mode data change logging was not found in the DDIO file for the specified module. This condition is normally the result of execution with a down-level DDIO. Execution logging will continue.

User Response: None.

XPD0163

NO X(21) TGT ENTRY FOR X(8)

Module: ADSRA458

Explanation: No TGT (Task Global Table) record of the specified type was found in the DDIO data set member for the designated module. The absence of this record precludes determination of addresses for data elements with this type of base locator.

User Response: Contact your internal technical support.

XPD0164

X(21) IN THE TASK GLOBAL TABLE NOT INITIALIZED

Module: ADSRA458

Explanation: The base locator assigned to the specified module and data element was not initialized. This situation normally is encountered when an attempt is made to reference an item with a secondary base locator before the indicated module is executed.

User Response: None.

XPD0165

INVALID DATA TYPE DETECTED FOR X(30) IN X(8)

Module: ADSRA173 and ADSRA680

Explanation: An unrecognized data type code was found in the DDIO data set record for the specified data element and module.

User Response: None.

XPD0180

FASTBREAK SUPPRESSED FOR X(8)

Module: ADSRA374

Explanation: FastBreak cannot function for Code Debug Release 3.0 or releases prior to it.

User Response: None.

XPD0199

USER MODULE X(8) DELETED

Module: ADSRA454

Explanation: Code Debug successfully deleted the specified module from memory. This occurs during “clean up” processing.

XPD0201

THE CSVQUERY MACRO WAS INVOKED
FOR MODULE, C(8,1,<MEMBER>), AND FAILED.
RETURN CODE (IN HEX): X(1,2,<REASON>).

Module: ADSRA223

Explanation: The CSVQUERY macro failed with a non-zero return code.

User Response: Contact your internal technical support.

XPD0202

MODULE, C(8,1,<MEMBER>),
HAS MORE THAN 2 SEGMENTS,
LOAD MODULE CONTROL
BLOCK PROCESSING CONTINUED.

Module: ADSRA223

Explanation: The CSVQUERY macro returned information that points to the module having more than two segments.

User Response: Contact BMC Support.

XPD0239

MODULE NOT FOUND - X(8)

Module: ADSRA017

Explanation: The specified module was not found in the data set referenced by the XTASKLIB DD.

User Response: Check each library for the member. If not found, locate the member and include an appropriate allocation to the XTASKLIB DD. If the problem persists, contact your internal technical support.

XPD0240

CONTROL STACK ENTRY MAXIMUM EXCEEDED

Module: ADSRA017

Explanation: The module intercept control stack used by Code Debug to maintain module transfer information exceeded specified number of levels.

User Response: The defaut number of nesting levels is 99. Determine if the program hierarchy contains more than 99 levels of calls outstanding at any given time. If it does not, check for a module loop where the module calls itself. You can use the "SET NESTED nnn" command if and Initial Script to increase the number of levels allowed. If unable to resolve the problem, contact your internal technical support.

XPD0250

NO LOAD MODULE FOUND FOR
X(8) IN XTASKLIB DATA SET

Module: ADSRA054

Explanation: No load module was found for the specified CSECT in the XTASKLIB data set.

User Response: Check your specified CSECT entry.

XPD0251

DATA SET NAME X(44) INCORRECT OR
COULD NOT BE ALLOCATED

Module: ADSRA054

Explanation: The data set name entered on the LOAD command was in error, or the temporary ddname had a conflict (XPLOADCW).

User Response: Check your data set name entry.

XPD0252

DDNAME X(8) INCORRECT OR COULD NOT BE ALLOCATED

Module: ADSRA054 and ADSRA097

Explanation: The ddname entered on the LOAD command was in error.

User Response: Check your ddname entry.

XPD0253

DDNAME LENGTH AS ENTERED IS INCORRECT

Module: ADSRA054

Explanation: A maximum of eight (8) characters is allowed for the data set name.

User Response: Check your ddname entry.

XPD0254

DSNAME LENGTH AS ENTERED IS INCORRECT

Module: ADSRA054

Explanation: A maximum of 44 characters is allowed for the data set name.

User Response: Check your dsname entry.

XPD0292

OPEN FAILED FOR DDNAME X(8)

Module: ADSRA051, ADSRA097, and ADSRA223

Explanation: The specified ddname could not be opened.

User Response: Verify that the ddname is present and that it contains the proper attributes. If the problem reoccurs, contact your internal technical support.

XPD0311

BLDL FAILED FOR MODULE X(8)

Module: ADSRA051 and ADSRA223

Explanation: The module specified could not be loaded for the reason given.

User Response: Check for problems with the data set.

XPD0312

UNCORRECTABLE I/O ERROR FOR
MEMBER X(8) IN X(8) SYNAD GPR 1 CONT N(4)

Module: ADSRA051, ADSRA097, ADSRA099, and ADSRA223

Explanation: An error was encountered while an attempt was made to READ for a load module library found in the XTASKLIB concatenation.

User Response: If the library is otherwise useable, contact your internal technical support.

XPD0317

IDENTIFY FAILED FOR MODULE X(8)
WITH A RETURN CODE OF N(2)

Module: ADSRA495 and ADSRA497

Explanation: A module to be simulated was already loaded and resides in memory. The purpose of the IDENTIFY is to allow the return of an alternate entry point when a load macro is issued for the given module. A SET DYNAMIC command must appear before the first CALL command for the simulation to be effective.

User Response: Contact your internal technical support.

XPD0318

MAXIMUM NUMBER OF DYNAMIC
MEMBERS EXCEEDED N(2)

Module: ADSRA497

Explanation: The maximum number of dynamic members that can be maintained by Code Debug exceeded Code Debug capacity. Nothing can be done by the programmer to circumvent this problem.

User Response: Contact your internal technical support.

XPD0319

MAXIMUM NUMBER OF SIMULATED
MEMBERS EXCEEDED N(2)

Module: ADSRA495

Explanation: The maximum number of simulated members which can be maintained by Code Debug exceeded Code Debug capacity. Nothing can be done by the programmer to circumvent this problem.

User Response: Contact your internal technical support.

XPD0322

THE LOAD MODULE DID NOT BEGIN WITH IGZ OR CEE C(8)

Module: ADSRA322

Explanation: This module only handles IGZ or CEE modules.

User Response: Check the context of your load module entry.

XPD0323

ATTEMPT TO LOAD C(8) FAILED -
ABEND CODE = C(4) REASON CODE = X(1)

Module: ADSRA322

Explanation: Could not load COBOL system module.

User Response: Contact your internal technical support.

XPD0324

CSECT C(8) WAS NOT LINK EDITED WITH
THE SYSTEM MODULE C(8)

Module: ADSRA322

Explanation: The CSECT could not be found in the system module. System library may not be allocated properly.

User Response: Check your system library allocation.

XPD0348

EXECUTION OF BEFORE/AFTER COMMAND FAILED

Module: ADSRA508

Explanation: Before and after breakpoints could not be set for the indicated intercept module.

User Response: Contact your internal technical support.

XPD0349

PARSE OF SETUP COMMAND FAILED

Module: ADSRA508

Explanation: Parsing failed for the indicated intercept module.

User Response: Contact your internal technical support.

XPD0352

OFFSET VALUE X(6) INVALID

Module: ADSRA286

Explanation: The specified OFFSET contains nonhexadecimal equivalent data. Valid characters are 0 through 9 and A through F. The OFFSET string is terminated by the first blank or left parenthesis.

User Response: Check the content of the specified OFFSET string.

XPD0396

 FIRST CALL COMMAND REQUIRES MODULE NAME

Module: ADSRA455

Explanation: The first time a CALL command is entered, a module name is required. If the succeeding CALL commands references the same module and entry point, the CALL command can be specified without keywords.

User Response: Contact your internal technical support.

XPD0397

LOAD MODULE X(8) NOT FOUND
FOR X(8) IN XTASKLIB DATA SET

Module: ADSRA455

Explanation: The specified load module was not found for the given CSECT.

User Response: Verify that the module specified is located in one of the data sets found in the XTASKLIB DD concatenation.

XPD0407

LOAD MODULE FOR X(8) NOT FOUND

Module: ADSRA028

Explanation: No load module was found for the specified module.

XPD0413

NO PROCEDURE DIVISION FOR X(8) LIST X(5) REJECTED

Module: ADSRA208

Explanation: The specified module does not have a PROCEDURE DIVISION statement. The indicated list is rejected for the above reason.

XPD0414

X(5) N(4) NOT FOUND IN X(8)

Module: ADSRA208

Explanation: The specified module does not contain the requested type. Valid record types are A, B, D, E, G, H, I, P, R, S, T, W, X, Y, 1, 2, 3, 5, @, $, #.

XPD0415

EXCESSIVE RECORD STRUCTURE
DEPTH ENCOUNTERED WITH X(30) AT STATE N(6)

Module: ADSRA208

Explanation: The specified identifier has an excessive record structure depth.

XPD0419

NO ELEMENTARY ITEM FOR X(30) IN X(8)

Module: ADSRA174

Explanation: No elementary item was found for the specified identifier in the module.

XPD0420

CANNOT FIND SOURCE FOR DATA ITEM

Module: ADSRA174

Explanation: No data item found.

User Response: Verify the data item name. If the data item does exist, Contact BMC Support.

XPD0421

INSUFFICIENT MEMORY FOR EDB

Module: ADSRA174

Explanation: There was insufficient memory for the element display block.

XPD0422

’C(1),’ IS AN INVALID TYPE

Module: ADSRA175

Explanation: The data conversation failed. The data item has an invalid type and cannot be converted.

User Response: Verify the data item type. Contact BMC Support.

XPD0423

EXCESSIVELY HIGH NUMBER

Module: ADSRA175

Explanation: A number higher than 1,152,921,504,606,846,976 was encountered when an attempt was made to convert user-specified data to binary.

User Response: Correct the data and try the command again.

XPD0424

TYPE X(1) HAS LENGTH OF N(2)

Module: ADSRA175

Explanation: The length of the specified type exceeds the maximum length permitted.

User Response: After determining the length of the field as found in the program, update and execute the command again. If the problem persists, contact your internal technical support.

XPD0425

SOURCE LENGTH ZERO OR NEGATIVE

Module: ADSRA175

Explanation: The data entered as the value of the field is null.

User Response: Include the appropriate data, and try the command again.

XPD0426

ZERO OR NEGATIVE TARGET LENGTH

Module: ADSRA175

Explanation: The field, which is to contain the converted data, has a null length.

User Response: Contact your internal technical support.

XPD0427

SOURCE AND TARGET TYPE = X(1)

Module: ADSRA175

Explanation: An internal conversion error was encountered.

User Response: Contact your internal technical support immediately.

XPD0428

SOURCE POINTER IS NULL

Module: ADSRA175

Explanation: An internal conversion error was encountered.

User Response: Contact your internal technical support immediately.

XPD0429

TARGET POINTER IS NULL

Module: ADSRA175

Explanation: An internal conversion error was encountered.

User Response: Contact your internal technical support immediately.

XPD0430

X(1) IS AN INVALID TARGET TYPE

Module: ADSRA175

Explanation: The specified target type is invalid. The valid types include Z (zoned), P (packed), or B (binary). This error is not externally controllable.

User Response: Contact your internal technical support immediately.

XPD0438

X(7) ABEND AT X(4) IN C(8), HANDLER IS IN CONTROL

Module: ADSRA304

Explanation: An ABEND occurred within the specified module at the specified offset, but an LE condition handler is registered. Control is passed to the condition handler. Code Debug takes no action.

User Response: None. The application’s registered condition handler received control for the abend. If you would like Code Debug to handle the abend, alter your application to not register the condition handler.

XPD0439

X(7) ABEND AT N(4) REASON
CODE N(2) [non-LE/370 format]

XPD0439

X(7) COND X(4) ABEND AT N(4)
REASON CODE N(2) [LE/370 format]

Module: ADSRA104, ADSRA105, and ADSRA304

Explanation: This message is generated when a system or user ABEND occurs during Code Debug or user module execution. It is followed by additional information.

User Response: If you have difficulty exiting the session, issue the RETEST command, and then the EXIT command.

XPD0440

NO DATA ELEMENTS IN TOKEN X(4) FOR MODULE C(8)

Module: ADSRA187

Explanation: No data elements were found in the identifier for the specified module.

User Response: Check the DDIO data set for the indicated identifier and, if not present, contact your internal technical support.

XPD0441

 INVALID DATA TYPE FOR INIT

Module: ADSRA187

Explanation: The data type, as found in the DDIO data set, is invalid.

User Response: Contact your internal technical support.

XPD0442

NO MEMORY FOR RIM CONTROL BLOCK

Module: ADSRA187

Explanation: Code Debug attempted to obtain memory in which to build an important control block.

User Response: Contact your internal technical support.

XPD0443

NO RDB FOR ITEM TOKEN X(4) IN C(8)

Module: ADSRA187

Explanation: An error occurred while Code Debug was attempting to locate an internal control block (the RDB).

User Response: Contact your internal technical support.

XPD0444

NO MEMORY FOR RECORD RDB

Module: ADSRA187

Explanation: Code Debug attempted to obtain memory for an important control block, but was unsuccessful.

User Response: Increase the region size and try the test again.

XPD0455

MODULE X(8) CONTAINS ONE OR MORE
UNRESOLVED EXTERNAL REFERENCES

Module: ADSRA222

Explanation: The specified load module was link edited with unresolved external references. Code Debug recognized this and will try to resolve these external references if the module is called.

User Response: Resolve the external references if Code Debug is unable to do so. If conflicts still exist, contact your internal technical support.

XPD0460

TROUBLE CLOSING USER FILES

Module: ADSRA020

Explanation: This message is no longer valid.

User Response: None.

XPD0461

CODE DEBUG FORCE CLOSING OF DDNAME = X(8)

Module: ADSRA020, ADSRA442

Explanation: During test termination, Code Debug detected that the file allocated to the indicated DDNAME was left open. Code Debug then attempted to close the file.

User Response: None.

XPD0468

UNRESOLVED STATIC REFERENCE TO
MODULE X(8) HAS BEEN TREATED AS DYNAMIC

Module: ADSRA098

Explanation: The load module contained a static call to a module which was unresolved. Code Debug will load from the XTASKLIB DD if not simulated. This message is only a warning.

XPD0469

COMMAND NAME INVALID

Module: ADSRA553

Explanation: An invalid command or option relating to the XCOMPILE or XSYMDIR maintenance was entered.

XPD0472

ERROR LOADING X(8)

Module: ADSRA222

Explanation: An error was encountered processing the control records in the listed member.

User Response: Ensure that the name is a valid member of the library defined by the XTASKLIB DD.

XPD0473

NO RLD ENTRIES X(8)

Module: ADSRA222

Explanation: The module being loaded has been read to the end of file condition and no RLD or CTL records were found.

User Response: Check the link edit for errors.

XPD0498

BREAKPOINT AT STATE N(3) OFFSET N(3)
IN MODULE X(8) HAS BEEN MODIFIED.

Module: ADSRA604

Explanation: The breakpoint specified cannot be reset because it has been modified. The user program may have self-modifying code. Processing is terminated.

XPD0529

END OF FILE ENCOUNTERED ON X(8).
THE LAST RECORD IS USED FOR ANY LATER
ASSIGNS FROM THIS FILE.

Module: ADSRA170

Explanation: The file specified on an ASSIGN command using the DDN PARM encountered an end-of-file. This, and all subsequent ASSIGNs from this file, will use the last record.

XPD0558 

OPTION SUPPLIED TO ADSRA005 IS INVALID

Module: ADSRA558

Explanation: A request to ADSRA558 is unknown.

User Response: An internal error has occurred. Contact BMC Support.

XPD0559

ADSRA558 GETMAIN REQUEST FAILED

Module: ADSRA558

Explanation: A GETMAIN request failed for ADSRA558.

User Response: Increase storage allocation for Code Debug. If the problem continues, Contact BMC Support.

XPD0560

NO JFCB POINTER CREATED IN ADSRA558

Module: ADSRA558

Explanation: JFCB pointer was not created.

User Response: Contact BMC Support.

XPD0564

NO INDEX CELLS IN TGT FOR X(8)

Module: ADSRA028

Explanation: No index cells were listed in the TGT for the specified module.

XPD0565

NO DATA DIVISION ENTRIES FOR X(8)

Module: ADSRA028

Explanation: No data division entries were listed for the specified module.

XPD0566

NO ITEM FOR INDEX X(30) IN X(8)

Module: ADSRA028

Explanation: No identifier was listed for the specified index.

XPD0568 

UNABLE TO LOAD X(8) LIBRARY
ROUTINE X(8) FROM XTASKLIB DATA SET

Module: ADSRA227

Explanation: Code Debug attempted to load a library subroutine for the specified language type to resolve external references in a user program. The subroutine was not found in the XTASKLIB data set.

User Response: Relink the module or include the library subroutines in the XTASKLIB concatenation.

XPD0570

ERROR UPDATING XDYNAMIC DATA SET MEMBER X(8) TO X(8) RC=N(4)

Module: ADSRA051

Explanation: The STOW macro failed for the specified module.

XPD0571

NOTE LIST NOT SUPPORTED FOR LOAD MODULE X(8)

Module: ADSRA051

Explanation: The NOTE LIST for load modules is not supported.

XPD0572

ERROR WITH IEWBIND FUNC=LOADW, (module name) IS A (“PROGRAM OBJECT” or “LOAD MODULE”)
AND THE XDYNAMIC DATASET IS A (“PDS” or “PDSE”).

Module: ADSRA051

Explanation: A critical error occurred using the IEWBIND macro.

User Response: If you are using program objects and the XDYNAMIC data set is a PDS, make the XDYNAMIC data set a PDSE. Otherwise Contact BMC Support. The XDYNAMIC “data set type” can be changed via the test panel by entering the SEtup, Extended, and Work commands.

XPD0573

UNRESOLVED STATIC REFERENCE TO
MODULE X(8) COULD NOT BE RESOLVED

Module: ADSRA098

Explanation: The load module contained a static call to a module which was unresolved. Code Debug was unable to load the module from XTASKLIB DD. The test will be terminated.

XPD0574

TRANSFER REFERENCE TO MODULE X(8)
COULD NOT BE RESOLVED

Module: ADSRA098

Explanation: The load module contains a transfer module, and a call was made to a module that could not be found in the XTASKLIB DD. The test will be terminated.

XPD0575

NO DYNAMIC CALL BLOCK FOUND FOR DYNAMIC INTERCEPT

Module: ADSRA594

Explanation: No dynamic call block was found for the dynamic intercept.

User Response: Contact your internal technical support.

XPD0576

ERROR WITH IEWBIND FUNC=SAVEW, (module name) IS A (“PROGRAM OBJECT” or “LOAD MODULE”)
AND THE XDYNAMIC DATASET IS A (“PDS” or “PDSE”).

Module: ADSRA051

Explanation: A critical error occurred using the IEWBIND macro.

User Response: If you are using program objects and the XDYNAMIC data set is a PDS, make the XDYNAMIC data set a PDSE. Otherwise Contact BMC Support. The XDYNAMIC “data set type” can be changed via the test panel by entering the SEtup, Extended, Work commands.

XPD0601

NO MODULE CONTROL BLOCK FOUND TO RESET FOR MODULE X(8)

Module: ADSRA058

Explanation: There is no module control block for the module specified. This module may not be a member of the load module, or the load module may not have been loaded.

XPD0602

NO OUTSTANDING SKIP FOR MODULE X(8)

Module: ADSRA058

Explanation: After skipping the modules, if they are to be reset, they must be loaded. If they cannot be loaded, then recovery is accomplished with a RETEST command.

XPD0603

KEYWORD IS MISSING FOR THE SHOW COMMAND.

Module: ADSRA245

Explanation: The keyword is missing for the SHOW command.

User Response: Reenter the command with the keyword. See the Code Debug TSO and IMS Quick Reference or Reference Manual for valid keywords.

XPD0604

ONLY SUBPOOL 0 CAN BE DISPLAYED.

Module: ADSRA245

Explanation: Only subpool 0 can be displayed.

User Response: Reenter command specifying subpool 0.

XPD0605

SKIP CANNOT BE DELETED FROM MODULE ’C(8),’

Module: ADSRA058

Explanation: The module has a dummy MOB. Therefore the control blocks for the module are not complete.

User Response: ’INTERCEPT’ the program to force the completion of Code Debug control blocks.

XPD0607

 X(8) REQUESTED N(4) BYTES - TOTAL IS N(4)

Module: ADSRA212

Explanation: The indicated Code Debug module has requested the specified amount of memory. The total amount allocated in the current session is also displayed. The generation of this message is triggered by assigning the Code Debug $CONCODE variable a value of 1092. It is suppressed when the value is changed.

XPD0610

INVALID KEYWORD X(16)

Module: ADSRA245

Explanation: The keyword is invalid for the SHOW command.

User Response: Reenter the command with a proper keyword. See the Code Debug TSO and IMS Quick Reference or Reference Manual for valid keywords.

XPD0614 

NO ENTRY POINT FOUND FOR X(8) IN MODULE X(8)

Module: ADSRA455

Explanation: An invalid entry point name was specified for the given load module.

User Response: Look at the ENTRY USING parameter list to determine the proper name of the entry point. If some question arises as to the way the load module is link edited, use the MVS AMBLIST utility to generate a link map.

XPD0629

SET DYNAMIC WAS NOT THE FIRST REFERENCE TO MODULE X(8) SET DYNAMIC NOT DONE

Module: ADSRA497

Explanation: A SET DYNAMIC must be the first reference to an Assembler module that is going to be called dynamically.

XPD0678

DEFAULT C(8) LIST HAS BEEN REPLACED BY SET C(8) COMMAND

Module: ADSRA055

Explanation: The default list, as found in the CMSC PARMLIB, was replaced by the list of modules or DDNAMEs as specified on the Code Debug SET EXCLUDE/NOCANCEL/DDIGNORE/TDODDXCL command.

XPD0700

CODE DEBUG INTERNAL TABLE OVERFLOW

Module: ADSRA227

Explanation: The Code Debug internal table for resolving external references in library subroutines exceeded its limit.

User Response: Relink the module without NCAL to continue testing, and contact your internal technical support.

XPD0732

MAXIMUM NUMBER OF ENTRIES (100) HAS BEEN EXCEEDED FOR C(8) SET OPTION

Module: ADSRA055

Explanation: The exception list, which is created and updated by the SET EXCLUDE/NOCANCEL/DDIGNORE/TDODDXCL command, cannot contain more than 100 entries.

XPD0733

CURRENT C(8) LIST HAS BEEN UPDATED TO INCLUDE NEW ENTRIES FOR THE SET C(8) COMMAND

Module: ADSRA055

Explanation: The list, which is created and updated by the SET EXCLUDE/NOCANCEL/DDIGNORE/TDODDXCL command, was updated to include the entries specified.

XPD0743

LOAD MODULE X(8) NOT DELETED - DATA HAS BEEN LOGGED FOR ROUTINE X(8)

Module: ADSRA085

Explanation: Review mode logging was activated and logged execution information for the specified routine. The load module containing this routine cannot be deleted or cancelled.

XPD0745

ATTEMPT TO DELETE MODULE X(8) FAILED WITH RETURN CODE OF N(2)

Module: ADSRA085

Explanation: The module specified as the positional value of the DELETE command cannot be handled by the system. The return code from GPR 15 is displayed in hexadecimal format. This module can be statically linked and cannot be deleted.

XPD0747

X(8) CANNOT BE DELETED - IT IS A SIMULATED MODULE

Module: ADSRA085

Explanation: The module specified as the positional value of the DELETE command is not a load module. It is a dummy module that cannot be deleted.

XPD0748

NO DYNAMIC CALL BLOCK FOUND FOR X(8) - CONTACT TECHNICAL SUPPORT

Module: ADSRA085

Explanation: The DELETE request could not be satisfied because a special Code Debug internal control block could not be located. The pseudo module name associated with the control block appears in the message.

XPD0768

NO BREAKPOINT TABLE ENTRY FOR OFFSET N(4) IN MODULE X(8)

Module: ADSRA130 and ADSRA478

Explanation: No matching offset could be found in the statement breakpoint table corresponding to the interrupt address.

User Response: The material required to recreate the problem should be forwarded to your internal technical support.

XPD0779

COBOL SORT IN PROGRESS AT TERMINATION

Module: ADSRA269

Explanation: This informational message is issued to make you aware that a premature end of a COBOL SORT was initiated. This occurred either because of an abnormal termination, or because an Code Debug EXIT was issued while within an interactive PAUSE. Special processing is required by Code Debug to close the COBOL SORT work files.

XPD0798

TABLE CAPACITY OF N(2) EXCEEDED FOR PTRTABLE

Module: ADSRA001

Explanation: The maximum number of system control parameters, which can be maintained by Code Debug, was exceeded.

User Response: This problem cannot be circumvented and should be reported to your internal technical support.

XPD0804

DIAGNOSE DUMP

Module: ADSRA148

Explanation: You requested a dump of the Code Debug session. The task abends with a user 3009 ABEND.

XPD0805      OPTION INVALID

XPD0806

MODULE NAME UNKNOWN TO CODE DEBUG

Module: ADSRA148

Explanation: The DIAGNOSE ADSRANNN option was specified, but the requested module could not be found. This facility is not generally used by application programmers.

User Response: If a problem exists, contact your internal technical support.

XPD0820

UNKNOWN TRANSLATOR TYPE = X(10) FOR MODULE X(8) INFORMATION ONLY

Module: ADSRA252

Explanation: An unknown type of translator was found in the IDR records.

User Response: This message should be communicated to your internal technical support.

XPD0844

NO SORT-RETURN FOR ANS68 VER 2 COBOL

Module: ADSRA409

Explanation: SORT-RETURN is allowed in Versions 3 and 4 of ANS 68 COBOL, but not Version 2. Do not use with this version of COBOL.

XPD0850

ERROR WHILE PROCESSING DDNAME X(8) FREE DATA SET AND REALLOCATE CORRECTLY

Module: ADSRA170

Explanation: An error occurred while the data set with the indicated ddname was being read. If the data set is a PDS, the member name may be incorrectly spelled or nonexistent.

User Response: The file must be freed and the data set with correct member reallocated.

XPD0851

0 WARNING: BLDL FAILED DURING CODE DEBUG COBOL TRAP PROCESSING FOR MEMBER X(8).

Module: ADSRA477

Explanation: This is an Code Debug internal error and will not affect program execution.

User Response: You can use GO to continue. This condition should be reported to your internal technical support.

XPD0852

DDNAME X(8) HAS NOT BEEN ALLOCATED

Module: ADSRA170

Explanation: The ddname was not allocated.

User Response: The Code Debug TSO ALLOCATE command can be used to allocate the ddname while in the TSO session.

XPD0853

THIS DDNAME X(8) MUST POINT TO A PS DATA SET

Module: ADSRA170

Explanation: This ddname must have a physical sequential data set, or the member name must be added.

XPD0854

MORE THAN 600 MODULES DYNAMICALLY LOADED

Module: ADSRA051

Explanation: Too many modules were dynamically loaded.

User Response: Contact BMC Support.

XPD0863

FILE NAME X(8) FILE TYPE, TEXT NOT FOUND

Module: ADSRA455

Explanation: The specified file name was not found for the given CALL.

User Response: Verify that the module with the file type TEXT exists on the user disk.

XPD0864 

PREVIOUS COMMANDS FOR X(8) ARE OF NO EFFECT - DIFFERENT COPY OF MODULE LOADED BY PEM - LINK PARM OF REUS REQUIRED

Module: XPHOGNCQ

Explanation: PEM invoked a module that was previously loaded by Code Debug during the processing of one or more commands that made reference to the designated module. Because the module was not linked with the REUS PARM, PEM loaded a fresh copy of the module, negating the Code Debug processing for the original copy.

User Response: If the module cannot be recompiled or relinked, Code Debug reference to the module should be deferred until it is loaded by PEM. This can be done with a conditionally executed BEGIN group associated with a CALL or TRANSFER command. Processing continues after the message.

XPD0865

X(8) NOT LINKED WITH REUS PARM

Module: XPHOGNCQ

Explanation: HOGAN application modules should be link edited with the REUS PARM. This is a warning message since no Code Debug function is impaired for the designated module.

XPD0868

PECNTL FILE NOT ALLOCATED

Module: ADSRA284

Explanation: Use of PANEXEC with one of the Code Debug products requires that a PECNTL DD be allocated.

User Response: Contact your internal technical support.

XPD0869

%CONCAT PANEXEC CONTROL CARD NOT FOUND IN PECNTL

Module: ADSRA284

Explanation: A %CONCAT PANEXEC control card was not found in PECNTL.

User Response: Contact your internal technical support.

XPD0871

CANNOT FIND MODULE X(8)

Module: ADSRA129

Explanation: The MCB could not be found for this module. Severe error.

User Response: Contact your internal technical support.

XPD0872

X(8) WAS NOT LOADED - MODULES LINKED WITH RMODE ANY CANNOT BE TESTED

Module: ADSRA051 and ADSRA223

Explanation: The module specified was not loaded by Code Debug because the VS attribute flags in the associated library directory entry indicated that it had been link edited with RMODE ANY.

User Response: If this message occurs after Code Debug TSO is installed, contact your internal technical support.

XPD0873

31-BIT ADDRESSING MODE WAS DETECTED AT THE TIME MODULE X(8) WAS RETURNING TO MODULE X(8)

Module: ADSRA274

Explanation: The addressing mode was changed from 24-bit to 31-bit mode by the specified module. Code Debug changes the mode back to 24-bit and terminates the test instead of returning control to the calling module.

User Response: If this message occurs after Code Debug TSO is installed, contact your internal technical support.

XPD0881

MODULE X(8) ALREADY IN MEMORY OR IN LPA LIB, INTERCEPT BYPASSED

Module: ADSRA497

Explanation: The specified module could not be intercepted under Code Debug control because it was already resident in real memory or in the link pack area.

User Response: Contact your internal technical support.

XPD0884 

MODULE X(8) COULD NOT BE FOUND IN THE CODE DEBUG OR USER LIBRARY OR STEPLIB

Module: ADSRA497

Explanation: The CTLCBLII installation default parameter was set to prevent the use of DDIO data set information for testing the specified module.

XPD0889

PANEXEC CONTROL CARD DD STATEMENT NOT FOUND

Module: ADSRA051 and ADSRA223

Explanation: The PANEXEC control card file was not allocated.

User Response: Allocate the file and retry.

XPD0890

INSUFFICIENT STORAGE FOR FILE LRP

Module: ADSRA405

User Response: The REGION parameter for the TSO session or the batch JOB should be increased.

XPD0891

INSUFFICIENT STORAGE FOR FILE FDB

Module: ADSRA405

User Response: The REGION parameter for the TSO session or the batch JOB should be increased.

XPD0892

INSUFFICIENT STORAGE FOR FILE BUFFER

Module: ADSRA405

User Response: The REGION parameter for the TSO session or the batch JOB should be increased.

XPD0893

MODULE NAME INVALID FOR FILE BUFFER

Module: ADSRA553

Explanation: The module name was not located in the XCOMPILE or XSYMDIR data sets.

XPD0894

CAN’T FIND OPERAND1

Module: ADSRA553

Explanation: The first operand is missing for the command.

XPD0895

NO XSYMDIR RECORD

Module: ADSRA553

Explanation: XSYMDIR does not contain the record for KAYS support.

User Response: Recompile with Code Debug and try again.

XPD0896

CAN’T FIND OPERAND2

Module: ADSRA553

Explanation: The second operand is missing for the command.

XPD0897

NO XSYMDIR RECORD

Module: ADSRA553

Explanation: The record was not found in the XSYMDIR data set.

User Response: Make sure that it was compiled with Code Debug.

XPD0898

INSUFFICIENT DIRECTORY SPACE IN XCOMPILE

Module: ADSRA553

User Response: Reallocate the XCOMPILE data set with a larger directory block.

XPD0899

INSUFFICIENT VIRTUAL STORAGE FOR STOW

Module: ADSRA553

User Response: The REGION size for the TSO session or the batch JOB should be increased.

XPD0900

XSYMDIR DATASET PERMANENT I/O ERROR

Module: ADSRA553

Explanation: Cannot access the XSYMDIR data set.

User Response: Contact your internal technical support.

XPD0902

ESTAE EXIT ENTERED - DUMP TAKEN

Module: ADSRA553

Explanation: The program encountered ESTAE EXIT and a dump was taken. Control was transferred to EPILG000.

XPD0904

INVALID OPERAND PAIR

Module:   ADSRA553

Explanation: Invalid operands were entered for the command.

XPD0911

MODULE X(8) HAS OVERLAY FORMAT - NOT SUPPORTED BY CODE DEBUG

Module: ADSRA223

Explanation: This is a warning message, but it should be heeded if you want to set breakpoints in any areas where overlay structures occur.

User Response: The module should be recompiled without overlays in order to permit the use of DDIO information for testing purposes.

XPD0912

ATTEMPT TO LOAD X(8) FAILED - ABEND CODE = X(3) REASON CODE = N(1)

Module: ADSRA054 and ADSRA223

Explanation: The specified module could not be loaded for the reason indicated by the ABEND code and the reason code. Typically, this is a MODULE MARKED NOT EXECUTABLE problem, such as an S706.

XPD0915

MODULE X(8) NOT AUTOMATICALLY CANCELLED - BREAKPOINTS HAVE PREVIOUSLY BEEN SET

Module: ADSRA274

Explanation: The specified module was not deleted at the time of return to its dynamic VS COBOL II caller. This is supported in Code Debug TSO.

User Response: If this message occurs after Code Debug TSO is installed, contact your internal technical support.

XPD0916

ACCEPT REJECTED FOR DDNAME X(8) RECORD FORMAT MUST BE EITHER FIXED OR VARIABLE

Module: ADSRA170

Explanation: This ddname must have a physical sequential data set, or the PDS member name must be added.

XPD0917

INPUT ERROR OCCURRED FOR DDNAME X(8)

Module: ADSRA170

Explanation: This ddname must have a physical sequential data set, or the PDS member name must be added.

XPD0955

SPECIAL MCB BUILT FOR MEMBER X(8)

Module: ADSRA222

Explanation: This is an informational message only. Code Debug will not attempt to read any information from a load module; however, a generic MCB (module control block) for the load module is built. No submodules within the load module can be accessed during the test.

XPD0965

RETEST WITHOUT A NEW COPY CANNOT BE VALID

Module: ADSRA444

Explanation: To retest, a new copy of the program must occur. Due to line edit options, a new copy of the program is required.

User Response: Issue the RETEST command with a NEWCOPY option.

XPD0966

RETEST WITHOUT NEW COPY CANNOT BE USED WITH REVIEW MODE OPTION

Module: ADSRA444

Explanation: The user is in a REVIEW mode.

User Response: Exit the REVIEW mode and reissue the RETEST command.

XPD0996

BREAKPOINT REMOVED FROM TARGET OF EXECUTE AT ADDRESS xxxxxxxx

Module: ADSRA104

Explanation: A breakpoint instruction has been encountered on an instruction that is the target of an EXECUTE instruction. Because this is not supported by Code Debug, the breakpoint has been removed.

User Response: Execution of the application should continue. If you want a breakpoint action to occur on an EXECUTE instruction, place the breakpoint on the EXECUTE instead of the target.

XPD0997

INVALID INSTRUCTION DETECTED. BREAKPOINTING CONFLICT !!

Module: ADSRA104

Explanation: A breakpoint instruction has been encountered which was not placed by Code Debug. The Code Debug SVC or TEST instruction has occurred within the user’s code or a supporting product. These instructions are not supported in a debugging session unless placed by Code Debug.

User Response: The PSW address indicates the location of the offending instruction. If the instruction was not compiled as part of the user’s application and there is no active product utilizing the instruction, Contact BMC Support.

XPD0998

PEM DELETES FOR X(8) CANNOT BE SUPPRESSED - NEITHER REENTRANT NOR REUSABLE

Module: XPHOGNCQ

Explanation: The SET NOPEMDEL facility is valid only for HOGAN programs that have been link edited with either the REUS or RENT parameters.

XPD0999

USER REQUESTED S0C1 DUMP HAS BEEN CREATED, ALL REGISTERS ARE CORRECT EXCEPT GPR 15, GPR 15 WILL POINT TO THE ORIGINAL INTERRUPT ADDRESS

Module: ADSRA104

Explanation: You requested a dump after a S0C1 ABEND, and set ABNDEXIT OFF and ABNDDUMP ON. This forces a dump, but GPR 0 points to a save area with 0-15 and GPR 15 to the ABEND address.

XPD1000

BTS INTERCEPTION BYPASSED BY CODE DEBUG

Module: XPTSO

Explanation: Because no program or trancode was entered for a BTS intercept, Code Debug will not perform any intercepts for this BTS run.

XPD1001

NO MODULE NAME ON TEST COMMAND

Module: XPDRP and XPTSO

Explanation: The syntax for the TEST command requires that a program name be one of the operands. The command has no meaning without it.

XPD1002

NO TEST COMMAND ENTERED

Module: XPTSO

Explanation: A batch Code Debug TSO test requires at least one TEST command to specify the module to be tested.

XPD1003

XPOUT DD CARD MISSING, NOTHING SPOOLED

Module: XPTSO

Explanation: The XPOUT DD refers to the Code Debug TSO session log. If it is not present, you cannot spool (log) the output from a test.

XPD1004

NO PARMS ENTERED FOR IMS TEST

Module: XPDRP and XPTSO

Explanation: When testing an IMS program, Code Debug TSO needs a PARM string containing such information as the PSB, the type of test, and so forth. In batch, this is in the JCL; in interactive testing, it should come from the installation defaults, based on the PARM entered on the IMS test screen in the PARM Passing Option field.

XPD1005

NO PARMS ENTERED FOR BTS TEST

Module: XPTSO

Explanation: When testing a BTS program, Code Debug TSO needs a PARM string containing such information as the PSB, the type of test, and so forth. In batch, this is in the JCL; in interactive testing, it should come from the installation defaults, based on the PARM entered on the IMS test screen in the PARM Passing Option field.

XPD1007

FIRST COMMAND MUST BE XPED COMMAND

Module: XPTSO

Explanation: In a batch Code Debug TSO test, the first command must be an XPED command. This command identifies the environment to be used for the test.

XPD1008 

NO MODULE NAME ON INTERCEPT COMMAND

Module: XPTSO

Explanation: The INTERCEPT command requires a program name to identify the program to be tested. The transaction name is not sufficient, because there can be more than one program per transaction.

XPD1009

TOO MANY XPED COMMANDS ENTERED

Module: XPDRP and XPTSO

Explanation: The maximum number of XPED commands that can be entered for a batch or interactive test is one.

XPD1010

ERROR IN ENVIRONMENT ON XPED COMMAND

Module: XPDRP and XPTSO

User Response: For the list of valid environments, consult the Code Debug TSO and IMS Reference Manual.

XPD1011

ONLY ONE TEST COMMAND ALLOWED IN IMS

Module: XPDRP and XPTSO

Explanation: An attempt was made to perform more than one test in a single IMS/DRP test session. This is not permitted.

XPD1012

TOO MANY INTERCEPT COMMANDS ENTERED

Module: XPDRP and XPTSO

Explanation: The maximum number of INTERCEPT commands that can be entered when testing a transaction is 50.

XPD1015

INVALID MODULE NAME

Module: XPDRP and XPTSO

Explanation: The module name specified on the command that caused this message is not a valid name under MVS naming rules. The module name is probably misspelled.

XPD1019

INVALID COMMAND ENTERED

Module: ADSRA412, ADSRA507, XPTSO, and XPDRP

Explanation: The command entered is not a valid Code Debug command.

User Response: Check your spelling on the command.

XPD1021

TEST COMMAND ENTERED IN BTS/DLG ENVIRONMENT

Module: XPTSO

Explanation: The TEST command is not valid in the BTS or DLG environments.

User Response: Use the INTERCEPT command instead.

XPD1022

TEST MODULE NAME C(8) NOT IN USER LIBRARY

Module: XPDRP and XPTSO

Explanation: The module to be tested could not be found in the user library (STEPLIB DD in batch; XTASKLIB under TSO).

User Response: If the module is in this library, contact your internal technical support.

XPD1023

INTERCEPT MODULE C(8) NOT IN USER LIBRARY

Module: XPTSO

Explanation: The module to be intercepted could not be found in the user library (STEPLIB DD on the TEST STEP).

User Response: If the module is in this library, contact your internal technical support.

XPD1024

NO XTASKLIB ALLOCATED

Module: XPTSO

Explanation: The XTASKLIB DD must be allocated for an interactive test.

User Response: Contact your internal technical support.

XPD1026

ENVIRONMENT CAN ONLY BE TSO OR SPF

Module: XPDRP and XPTSO

Explanation: There is a severe processing error in Code Debug TSO.

User Response: Contact your internal technical support.

XPD1029

TRANCODE INVALID ON THE TEST COMMAND

Module: ADSRA516

Explanation: The TRANCODE keyword is not valid on the TEST command.

User Response: Use the INTERCEPT command or the LOADM keyword on the TEST command.

XPD1030

MISSING TRANCODE NAME - INTERCEPT COMMAND

Module: ADSRA507 and ADSRA516

Explanation: The TRANCODE name is required on the INTERCEPT command.

User Response: See the Code Debug TSO and IMS Quick Reference or Reference Manual for more information on this command.

XPD1031

BAD TRANCODE NAME ON INTERCEPT COMMAND

Module: ADSRA507 and ADSRA516

Explanation: The syntax for a valid TRANCODE name (according to IMS and BTS rules) was violated by the TRANCODE keyword entry on the INTERCEPT command.

XPD1032

BAD PARMS ENTERED ON THE TEST COMMAND

Module: ADSRA516

Explanation: The PARM string on the TEST command contained an invalid character length (not between 1 and 100).

XPD1034

NO PARMS ENTERED ON THE TEST COMMAND

Module: ADSRA516

Explanation: The TEST command requires certain parameters to set up the test correctly.

User Response: See the Code Debug TSO and IMS Quick Reference or Reference Manual for more information on this command.

XPD1035

NO PARMS SHOULD BE ENTERED ON THE INTERCEPT COMMAND

Module: ADSRA516

Explanation: The INTERCEPT command should not contain the PARM keyword.

XPD1036

NO ENTRY NAME ON TEST COMMAND

Module: ADSRA516

Explanation: If no entry point is specified, then Code Debug TSO uses the link-edited entry point to begin program execution. Code Debug TSO could not determine the entry point, and it was not specified.

XPD1037

BAD ENTRY NAME ON TEST COMMAND

Module: ADSRA516

Explanation: The value used for entry point on the TEST command does not follow the naming conventions for a valid entry point or module name.

XPD1038

NO LOAD MODULE NAME ON TEST COMMAND

Module: ADSRA516

Explanation: The TEST command requires that a program name be one of the parameters entered.

XPD1039

NO INITIAL SCRIPT NAME ON TEST COMMAND

Module: ADSRA516

Explanation: The INITSCR keyword was specified on the TEST command, but no value (actual test script) was specified for it.

XPD1040

 NO INITIAL SCRIPT NAME ON INTERCEPT COMMAND

Module: ADSRA507 and ADSRA516

Explanation: The INITSCR keyword was specified on the INTERCEPT command, but no value (actual test script) was specified for it.

XPD1041

NO POST SCRIPT NAME ON TEST COMMAND

Module: ADSRA516

Explanation: The POSTSCR keyword was specified on the TEST command, but no value (actual test script) was specified for it.

XPD1042

ADSRA093 INVALID

Module: XPINIT and CSSMVS

Explanation: ADSRA093 was reassembled incorrectly. Reassembly usually occurs because of changes to ADSCPDEF (installation defaults).

XPD1044

NO POST SCRIPT NAME ON INTERCEPT COMMAND

Module: ADSRA507 and ADSRA516

Explanation: The POSTSCR keyword was specified on the INTERCEPT command, but no value (actual test script) was specified for it.

XPD1047

BAD LOAD MODULE NAME ON INTERCEPT COMMAND

Module: ADSRA516

Explanation: The initial test script name entered as a value on the TEST command does not conform to the naming conventions for a member of a PDS.

XPD1049

BAD POST SCRIPT NAME ON TEST COMMAND

Module: ADSRA516

Explanation: The post test script name entered as a value on the TEST command does not conform to the naming conventions for a member of a PDS.

XPD1052

BAD INITIAL SCRIPT NAME ON INTERCEPT COMMAND

Module: ADSRA507 and ADSRA516

Explanation: The initial test script name entered as a value on the INTERCEPT command does not conform to the naming conventions for a member of a PDS.

XPD1053

BAD POST SCRIPT NAME ON INTERCEPT COMMAND

Module: ADSRA507 and ADSRA516

Explanation: The post test script name entered as a value on the INTERCEPT command does not conform to the naming conventions for a member of a PDS.

XPD1056

NO MODULE NAME ON INTERCEPT COMMAND

Module: ADSRA516

Explanation: The syntax for the INTERCEPT command demands that a program name be entered for it. The INTERCEPT command has no meaning without this keyword.

XPD1057

BAD ENTRY NAME ON INTERCEPT COMMAND

Module: ADSRA507 and ADSRA516

Explanation: The ENTRY keyword on the INTERCEPT command specifies an entry point that does not fit the naming requirements for the entry point within a module.

XPD1058

NO ENTRY NAME ON INTERCEPT COMMAND

Module: ADSRA507 and ADSRA516

Explanation: If no entry point is specified, Code Debug TSO uses the link-edited entry point to begin program execution. Code Debug TSO could not determine the entry point since it was not specified.

XPD1059

NO LOAD MODULE NAME ON INTERCEPT COMMAND

Module: ADSRA507 and ADSRA516

Explanation: The syntax for the INTERCEPT command demands that a program name be entered for it. The INTERCEPT command has no meaning without this keyword.

XPD1060

BAD LOAD MODULE NAME ON INTERCEPT COMMAND

Module: ADSRA507 and ADSRA516

Explanation: The load module name specified on the INTERCEPT command does not conform to the naming conventions for an MVS load module name.

XPD1061

EXTRANEOUS KEYWORD

Module: ADSRA516

Explanation: A keyword parameter specified on either the TEST or the INTERCEPT command was not valid.

User Response: Check to see if this is a spelling error.

XPD1063

NO COMMAND ENTERED TO DELETE

Module: ADSRA516

Explanation: A DELETE has been entered on the INTERCEPT command, but there was no previous INTERCEPT command entered.

XPD1064

CANNOT USE DELETE ON THE TEST COMMAND

Module: ADSRA516

Explanation: A DELETE is not valid on the TEST command.

User Response: If you are trying to do another test, simply enter another TEST command.

XPD1065

NO DB2 PLAN-NAME ENTERED ON THE TEST COMMAND

Module: ADSRA516

Explanation: The internal DB2PLAN keyword requires the value of a valid Db2 plan name.

User Response: If you are not running with the Db2 DSN run support, leave this keyword off; otherwise, specify a valid Db2 plan name.

XPD1066 

BAD PLAN-NAME ENTERED ON THE TEST COMMAND

Module: ADSRA516

Explanation: The plan name specified for the internal DB2PLAN keyword is an invalid plan name, according to the naming rules for a Db2 plan name.

XPD1067

NO PLAN-NAME ENTERED ON THE INTERCEPT COMMAND

Module: ADSRA507 and ADSRA516

Explanation: The internal DB2PLAN keyword requires a value of a valid Db2 plan name.

User Response: If you are not running with the Db2 DSN run support, leave this keyword off; otherwise, specify a valid Db2 plan name.

XPD1068

BAD PLAN-NAME ENTERED ON THE INTERCEPT COMMAND

Module: ADSRA507 and ADSRA516

Explanation: The plan name specified for the internal DB2PLAN keyword is an invalid plan name, according to the naming rules for a Db2 plan name.

XPD1069

NO DB2 SYS-NAME ENTERED ON THE TEST COMMAND

Module: ADSRA516

Explanation: The internal DB2SYS keyword requires a value of a valid Db2 system name.

User Response: If you are not running with the Db2 DSN run support, leave this keyword off; otherwise, specify a valid Db2 system name.

XPD1070

BAD DB2 SYS-NAME ENTERED ON THE TEST COMMAND

Module: ADSRA516

Explanation: The system name specified for the internal DB2SYS keyword is an invalid system name, according to the naming rules for a Db2 system name.

XPD1071

NO DB2 SYS-NAME ENTERED ON THE INTERCEPT COMMAND

Module: ADSRA507 and ADSRA516

Explanation: The internal DB2SYS keyword requires a value of a valid Db2 system name.

User Response: If you are not running with the Db2 DSN run support, leave this keyword off; otherwise, specify a valid Db2 system name.

XPD1072

BAD DB2 SYS-NAME ENTERED ON THE INTERCEPT COMMAND

Module: ADSRA507 and ADSRA516

Explanation: The system name specified for the internal DB2SYS keyword is an invalid system name, according to the naming rules for a Db2 system name.

XPD1073

DB2 PARMS USED FROM FIRST INTERCEPT COMMAND

Module: ADSRA507 and ADSRA516

Explanation: This is an informational message only. The Db2 PARMS for the current INTERCEPT command will be taken from those established for the first INTERCEPT command.

XPD1074

BAD DB2 PARM ON COMMAND

Module: ADSRA516

Explanation: The Db2 keyword on the INTERCEPT command requires a value of either YES or NO. Something other than one of these two choices was entered for the value.

XPD1075

ERROR IN KEYWORD

Module: ADSRA516

Explanation: An invalid keyword was entered for either the TEST or INTERCEPT command.

User Response: Check the spelling on the keyword. If this is an interactive test, ensure any parameter strings containing spaces or commas are enclosed in apostrophes.

XPD1076

RA516 BAD TRAN DATA ENTERED ON INTERCEPT COMMAND

Module: ADSRA516

Explanation: The length of the data found in the transaction buffer exceeds the maximum length permitted.

XPD1077

RA516 NO TRAN DATA ENTERED ON INTERCEPT COMMAND

Module: ADSRA516

Explanation: No data was found in the transaction buffer.

XPD1080

NO START PARAMETER ENTERED - INTERCEPT COMMAND

Module: ADSRA507 and ADSRA516

Explanation: The START keyword was used on the INTERCEPT command but no value was entered along with it. This shuts down the test. If START is not entered, it defaults to 1.

XPD1081

TOO MANY DIGITS ON START PARM - INTERCEPT

Module: ADSRA507 and ADSRA516

Explanation: A maximum of four digits is allowed for the START keyword on the INTERCEPT command.

XPD1082

TOO MANY DIGITS ON MAX PARM - INTERCEPT

Module: ADSRA507 and ADSRA516

Explanation: A maximum of four digits is allowed for the MAX keyword on the INTERCEPT command.

XPD1083

INVALID DIGITS ON START PARM - INTERCEPT

Module: ADSRA507 and ADSRA516

Explanation: A nonnumeric character was detected in the value for the START keyword. The value must be a 1-4 digit number.

XPD1084

INVALID DIGITS ON MAX PARM - INTERCEPT

Module: ADSRA507 and ADSRA516

Explanation: A nonnumeric character was detected in the value for the MAX keyword. The value must be a 1-4 digit number.

XPD1085

NO MAX PARAMETER ENTERED - INTERCEPT COMMAND

Module: ADSRA507 and ADSRA516

Explanation: A MAX keyword was entered on the INTERCEPT command, but no value was assigned to it. This shuts down the test; if the MAX keyword is not entered, it defaults to UNLIMITED.

XPD1086

RA516 X(6) KEYWORD MISSING ON DB2SP CARD

Module: ADSRA516

Explanation: The specified keyword was missing.

XPD1087

RA516 X(6) DB2SP KEYWORD UNDEFINED

Module: ADSRA516

Explanation: The specified keyword was invalid.

XPD1088

RA516 X(6) VALUE HAS INVALID LENGTH

Module: ADSRA516

Explanation: The length of the value specified for the specified keyword exceeds the maximum length permitted.

XPD1089

RA516 X(6) VALUE IS MISSING OR INVALID

Module: ADSRA516

Explanation: The value specified for the specified keyword was missing or invalid.

XPD1090

SETTING LETRAP OFF IN AN XPLINK ENVIRONMENT IS NOT RECOMMENDED

Module: ADSRA109 and ADSRA410

Explanation: When testing in an XPLINK environment with LETRAP OFF, it is possible to experience a S0C4 ABEND if a stack overflow condition occurs when the Guard Page strategy is deployed.

User Response: If vulnerable, retest specifying SET LETRAP ON in an initial script, or specify the LE run-time STACK parameter to increase the size to a value large enough that an overflow won’t occur.

XPD1091

DEFINE LENGTH OF N(4) IS GREATER THAN DATA GROUP N(4) SIZE OF N(4)

Module: ADSRA286

Explanation: An attempt was made to define an item to a length greater than that available to the data group.

User Response: If it is necessary to define such a large field, contact your internal technical support.

XPD1092

INSUFFICIENT MEMORY FOR X(21)

Module: ADSRA436

Explanation: You must increase the TSO logon size or the REGION permitted on the batch JOB in order to run this test.

User Response: If this is a problem, contact your internal technical support.

XPD1093

INSUFFICIENT MEMORY FOR ALLOCATION OF X(21) FOR X(8)

Module: ADSRA389, ADSRA423, ADSRA608, ADSRA623, and ADSRA695

Explanation: You must increase the TSO logon size or the REGION permitted on the batch JOB in order to run this test.

User Response: If this is a problem, contact your internal technical support.

XPD1095

NO BREAKPOINT TABLE FOR MODULE X(8)

Module: ADSRA434

Explanation: In order to set a breakpoint in the specified module, you must compile it under Code Debug control.

User Response: If the module is compiled with Code Debug and you still can’t set breakpoints, contact your internal technical support.

XPD1102

NO DEFINITION RECORD FOUND FOR DATA ITEM X(30) IN MODULE X(8)

Module: ADSRA436

Explanation: In trying to supply the linkage section for a COBOL subprogram being unit tested, Code Debug discovered a problem with the DDIO data set.

User Response: Recompile the program and test again. If that doesn’t work, contact your internal technical support.

XPD1103

NO ELEMENT DISPLAY BLOCK FOUND FOR DATA ITEM X(30) IN MODULE X(8)

Module: ADSRA436

Explanation: An attempt was made to reference the specified data item, but the necessary element display block (an Code Debug internal control block) was not available.

User Response: Recompile the program and test again. If that doesn’t work, contact your internal technical support.

XPD1104

NO INTERFACE ITEMS FOUND FOR ENTRY C(8)

Module: ADSRA436

Explanation: In trying to supply the linkage section for a COBOL subprogram being unit tested, Code Debug discovered a problem with the DDIO data set.

User Response: Try recompiling the program and testing again. If that doesn’t work, contact your internal technical support.

XPD1105

NO SNT ENTRY FOUND FOR STATEMENT N(3) IN MODULE X(8)

Module: ADSRA469

Explanation: An attempt was made to reference a statement for which there was no entry in the statement number table (SNT).

User Response: Contact your internal technical support.

XPD1107 

NO STATEMENT NUMBER TABLE ENTRY FOUND FOR X(30) IN MODULE X(8)

Module: ADSRA436

Explanation: An attempt was made to reference a statement for which there was no entry in the statement number table (SNT).

User Response: Contact your internal technical support.

XPD1108

PCB COUNT EQUALS MODULE INTERFACE COUNT FOR X(30) IN MODULE X(8) PSB PASSED TO MODULE X(8)

Module: ADSRA436

Explanation: This is an informational message indicating that the PSB appears to contain the proper PCBs for the program.

XPD1109

PCB COUNT FOR X(8) EXCEEDS ITEM INTERFACE COUNT - PCB PASSED TO MODULE X(8)

Module: ADSRA436

Explanation: This is an informational message. There were more PCBs than receiving fields. They will be moved into the receiving fields from the first one, ignoring the extra ones.

XPD1110

INVALID CODE DEBUG SVC NUMBER (nnn).

Module: ADSRA111

Explanation: The SVC necessary to perform breakpoint processing could not be found.

User Response: Run the job JCLSVCIN, which may be found in your installation libraries, to install the necessary SVC. This job may be included in your IPL procedures. If not included in your IPL procedures, it must be run after each IPL to avoid this error.

XPD1111

UNABLE TO LOCATE MODULE = X(8), ENTRY = X(8), MEMBER = X(8)

Module: ADSRA417

Explanation: The specified module could not be found in the XTASKLIB or STEPLIB.

User Response: Check the spelling on the module and verify that the module you are seeking is in your test load library. If the discrepancy remains, contact your internal technical support.

XPD1112

TRAP BREAKPOINTING ACTIVATION FAILURE.. RC= X(4)

Module: ADSRA111

Explanation: The attempt to install and activate the optional TRAP break pointing has failed. SVC break pointing, if specified, will be used instead.

User Response: Contact your internal technical support. Processing will continue, if possible, with SVC break pointing.

XPD1113

SVC BREAKPOINTING IS ACTIVE

Module: ADSRA111

Explanation: The optional break pointing SVC has been installed and is active.

User Response: None.

XPD1114

CONTROL BLOCK ERROR N(2)

Module: ADSRA247 and ADSRA367

Explanation: An Code Debug internal control block was overlayed.

User Response: Contact your internal technical support.

XPD1115

64-BIT REGISTER INTEGRITY HAS BEEN COMPROMISED

Module: ADSRA102, ADSRA111, ADSRA105, ADSRA302

Explanation: A system error occurred while Code Debug was attempting to save the high-order halves of the 64-bit registers on a z/architecture machine.

User Response: Contact your internal technical support. If the application runs strictly without 64-bit resources, execution should continue normally.

XPD1116

TRAP BREAKPOINTING IS ACTIVE

Module: ADSRA111

Explanation: The optional TRAP break pointing has been installed and is active.

User Response: None.

XPD1117

SVC BREAKPOINTING ACTIVATION FAILURE.. RC= X(4)

Module: ADSRA111

Explanation: The attempt to install and activate the optional SVC break pointing has failed. The default ESPIE break pointing will be used instead.

User Response: Contact your internal technical support. Processing will continue with ESPIE break pointing.

XPD1120

INSUFFICIENT STORAGE TO BUILD CONTROL BLOCK

Module: ADSRA171, ADSRA223, ADSRA409, ADSRA593, ADSRA609, ADSRA616, and ADSRA617

User Response: You must increase either the TSO logon size or the REGION parameter on the JCL to run the batch test.

XPD1121

INSUFFICIENT STORAGE TO BUILD LRP BLOCK

Module: ADSRA407

User Response: You must increase either the TSO logon size or the REGION parameter on the JCL to run the batch test.

XPD1125

INVALID CODE DEBUG CONTROL BLOCK - B(2)

Module: ADSRA172, ADSRA173, and ADSRA680

Explanation: An invalid condition was detected when building an Code Debug control block.

User Response: Contact your internal technical support.

XPD1127

NO CA-OPTIMIZER BASE LOCATORS FOR X(8)

Module: ADSRA217

Explanation: The module was compiled using the CA-OPTIMIZER, but no CA-OPTIMIZER base locators were found.

User Response: Contact your internal technical support.

XPD1129

NO SLS MEMBER FOR X(8)

Module: ADSRA217

Explanation: This is an informational message reminding you that there is no DDIO data set for the specified module.

User Response: If you wish to use Code Debug DDIO debugging facilities, you must compile under Code Debug control.

XPD1130

OUT OF MEMORY

Module: ADSRA418, ADSRA440, ADSRA459, ADSRA670, ADSRA676, ADSRA679, ADSRA689, and ADSRA690

User Response: Increase either the TSO logon size or the REGION parameter on the JCL to run the batch test, and begin the test again.

XPD1133

CODE DEBUG CONTROL BLOCK STRUCTURE ERROR - N(2)

Module: ADSRA208

Explanation: An Code Debug internal control block was either overlayed or built incorrectly.

User Response: Contact your internal technical support.

XPD1135

ERROR ON COPY FOR MEMBER X(8)

Module: ADSRA051

Explanation: An attempt to perform a dynamic call intercept on a module failed.

User Response: Contact your internal technical support.

XPD1137

NO BREAKPOINT TABLE ENTRY FOR STATE (B,3) IN MODULE X(8)

Module: ADSRA402

Explanation: During the processing of a primary breakpoint command (such as BEFORE, COUNT, or TRACE), Code Debug was unable to locate the specified statement.

User Response: If the statement is clearly a valid one, contact your internal technical support.

XPD1139

INSUFFICIENT STORAGE FOR SHOW PREV BUFFER

Module: ADSRA403

Explanation: Code Debug ran out of memory.

User Response: Increase either the TSO logon size or the REGION parameter on the JCL for the batch test, and begin the test again.

XPD1142

GO TO NOT PERMITTED WHERE TARGET IS WITHIN PERFORMED OUT-OF-LINE PROCEDURE

Module: ADSRA426

Explanation: This is a restriction on the use of the OPTIMIZE option with VS COBOL II. When a paragraph was optimized into a series of multiple performs, you cannot branch to it through the use of the Code Debug GO TO construct.

User Response: Check the I-level (informational) messages from VS COBOL II in your compilation listing. These will flag the paragraphs that fall into this category.

XPD1143

MODULE X(8) HAS BEEN COMPILED WITH THE OPTIMIZE COMPILER OPTION OR INLINE COMPILER OPTION

Module: ADSRA420

Explanation: There are certain limitations on testing programs compiled with the OPTIMIZE compiler option or the INLINE compiler option.

User Response: See to the Code Debug TSO and IMS PL/I or C User Guide for more information on these restrictions.

XPD1144

MODULE X(8) HAS BEEN COMPILED WITH THE COBOL OPTIMIZE COMPILER OPTION

Module: ADSRA193

Explanation: There are certain limitations on testing programs compiled with the COBOL OPTIMIZE compiler option.

User Response: See to the Code Debug TSO and IMS COBOL User’s Guide for more information on these restrictions.

XPD1145 

MODULE <module-name> WAS COMPILED WITH THE TEST OPTION. THIS OPTION CAN CAUSE UNEXPECTED BEHAVIOR AND SHOULD BE REMOVED. (UNLESS OPT(1) OR OPT(2) AND TEST(NOEJPD,NOSOURCE) OPTIONS WITH COBOL 5.1 OR NEWER)

Module: ADSRA193

Explanation: Testing programs compiled with the TEST option can give unpredictable results.

User Response: See to the Code Debug TSO and IMS COBOL User’s Guide for more information on these restrictions.

XPD1146

NO PREVIOUS BREAKPOINTS TO SHOW

Module: ADSRA463

Explanation: An attempt to show all the WHEN breakpoints has been made, but no WHEN breakpoints were in effect.

XPD1147

WARNING, COBOL PROGRAM LANGUAGE LEVEL IS NOT IDENTIFIABLE

Module: ADSRA193

Explanation: The COBOL language level could not be determined.

User Response: Make sure the level of the COBOL compiler is supported. See to the Code Debug TSO and IMS Installation and Configuration Guide section entitled “Prerequisites” for a list of supported COBOL releases.

XPD1149

XPTSO IMS INTERCEPTION BYPASSED BY CODE DEBUG

Module: XPTSO

Explanation: This is an informational message telling you that an IMS test is being invoked with Code Debug TSO allocations, but Code Debug will not intercept any modules.

User Response: If this is not your intention, contact your internal technical support.

XPD1153

NOTE: THE AUTOCAN FEATURE DOES NOT AUTOMATICALLY DELETE VS COBOL II MODULES

Module: ADSRA274

Explanation: The SET AUTOCAN feature does not delete modules compiled with VS COBOL II. The automatic cancel will only take effect on modules compiled with OS/VS COBOL or ANS COBOL.

XPD1162

CLASS CODE > 255 NOT SUPPORTED BY THIS IMS RELEASE

Module: ADSIM017

Explanation: An IMS message class number reserved for use by Code Debug IMS is greater than 255. This class code is valid for IMS 9.1 and newer, but is invalid if IMS 8.1 or older is used.

XPD1163

FAILURE TO FIND DSN BY ADSRA558. DDNAME IS X(8)

Module: ADSRA223

Explanation: The call to ADSRA558 to find a DSN and build a pseudo JFCB block failed. The LMB and DCB does not have a pointer to the JFCB to get a DSN for load messages. This condition should not occur.

User Response: Contact your internal technical support. Also check for previous messages in the session log.

XPD1164

ANOTHER USER IS CURRENTLY TESTING THE SAME PROGRAM AS YOU ARE ATTEMPTING TO TEST. COMPILE YOUR PROGRAMS WITH NORES TO AVOID THIS CONFLICT.

Module: ADSRA107

Explanation: If the program is compiled with RES, only one user at a time can execute that program.

User Response: Recompiling programs with NORES can resolve the problem.

XPD1165

ATTACH OF THE IMS REGION FAILED. RETURN CODE = N(4)

Module: ADSIM003

Explanation: During the attach of the Code Debug IMS BMP to setup, the test failed. The IBM return code is given.

User Response: Contact your internal technical support.

XPD1166

THE NUMBER OF TRANSACTIONS EXCEEDS THE MAXIMUM OF 45.

Module: ADSIM003

Explanation: Only 45 transactions can be selected for an Code Debug IMS test.

User Response: Drop some of the transactions on the Setup panel.

XPD1167

GETMAIN FAILED FOR USER SEGMENT WORK AREA.

Module: ADSIM003

Explanation: An attempt to get storage for work areas failed.

User Response: Try increasing the TSO logon size.

XPD1168

GETMAIN FAILED FOR CLASS WORK AREA.

Module: ADSIM003

Explanation: An attempt to get storage for work areas failed.

User Response: Try increasing the TSO logon size.

XPD1169

X(5) ABEND IN PROCESSING THE IMS REGION. THE INTERNAL CODE DEBUG IMS PROGRAM HAS ABENDED. PLEASE CHECK THE STATUS OF CODE DEBUG IMS ENTITIES. TRAN = X(8), PSB = X(8)

Module: ADSIM003

Explanation: A system or user ABEND occurred while the Code Debug IMS validation BMP was active. User ABEND codes are in decimal format.

User Response: If the reason for the ABEND is not apparent from the code, Contact BMC Support.

XPD1170

THE PSB IS LOCKED OR MARKED NON-SCHEDULABLE.

Module: ADSIM003

Explanation: The PSB associated with the transaction code to be tested is stopped or locked.

User Response: Restart the PSB and retry the test.

XPD1171 

A DATABASE USED BY THIS PSB IS STOPPED.

Module: ADSIM003

Explanation: One of the databases used by this PSB is stopped.

User Response: Restart the database and retry the test.

XPD1172

THE TRANCODE IS MARKED AS STOPPED, LOCKED, OR NON-SCHEDULABLE.

Module: ADSIM003

Explanation: The transaction code to be tested is stopped, locked, or cannot be scheduled.

User Response: Restart the transaction code and retry the test.

XPD1173

THE TRANSACTION NAME ENTERED IS NOT DEFINED TO IMS.

Module: ADSIM003

Explanation: The transaction specified on the test panel is not defined to this control region.

User Response: Verify that the transaction code is spelled correctly and the IMS region ID is correct.

XPD1174

THE PSB NAME ENTERED IS NOT DEFINED TO IMS.

Module: ADSIM003

Explanation: The PSB associated with this test is not defined in this control region.

User Response: Verify that the PSB libraries are correct and the PSB GEN has been done.

XPD1175

NEITHER A TRANSACTION OR PSB NAME WAS ENTERED.

Module: ADSIM003

Explanation: The Code Debug test could not find a valid PSB or transaction to test.

User Response: If a valid PSB or transaction code was entered on the Setup panel, Contact BMC Support.

XPD1176

IN AN MPP TEST THE PSB HAS NO TRANSACTIONS.

Module: ADSIM003

Explanation: The Code Debug test could not find a valid PSB or transaction to test.

User Response: If a valid PSB or trancode was entered on the Setup panel, Contact BMC Support.

XPD1177

IN AN IFP TEST THE PSB HAS NO TRANSACTION DEFINED.

Module: ADSIM003

User Response: Make sure the IMS GEN was done and the correct program was specified on the panel.

XPD1178

AN CODE DEBUG INTERNAL ERROR HAS OCCURRED.

Module: ADSIM003

User Response: Contact BMC Support.

XPD1179

IN AN MPP OR IFP TEST, THIS PSB REQUIRES A TRANCODE.

Module: ADSIM003

User Response: Make sure the correct program was specified on the Setup panel and the library allocations specified during setup are correct.

XPD1180

THE PSB NAME ENTERED IS NOT GENED FOR THIS TRANSACTION.

Module: ADSIM003

Explanation: The trancode and module entered on the Setup panel do not agree.

User Response: If the trancode/module pair is unique, only one of them has to be entered on the Setup panel. Also, check if the IMS APPLCTN and TRANSACT macros are correct.

XPD1181

THIS PARALLEL SCHEDULABLE PSB CANNOT BE RUN AS A BMP.

Module: ADSIM003

Explanation: As generated, this PSB cannot be run as a BMP.

User Response: Use either IFP or MPP to test.

XPD1182

THIS BMP OR IFP PSB CANNOT BE RUN AS AN MPP.

Module: ADSIM003

Explanation: As generated, this PSB cannot be run as an MPP.

User Response: Try using the BMP or IFP option.

XPD1183

NO CLASS AVAILABLE FOR THIS MPP TEST.

Module: ADSIM003

Explanation: All available classes used for testing an MPP program are in use.

User Response: Try later or have the Code Debug installer increase the number of classes.

XPD1184

TRANSACTION X(43) IS CURRENTLY IN USE.

Module: ADSIM003

Explanation: The named transaction is currently in use by another Code Debug IMS test session.

User Response: Try later. The INTER command on the Setup panel will show the current Code Debug IMS test sessions.

XPD1185

THE INFORMATIONAL ENQUE FAILED. CONTACT TECHNICAL SUPPORT.

Module: ADSIM003

Explanation: There is an internal problem in Code Debug IMS.

User Response: Contact BMC Support.

XPD1186

ERROR IN ASSIGNING AN CODE DEBUG TEST CLASS. SOME TEST TRANSACTIONS MAY NOT HAVE BEEN REASSIGNED TO THEIR ORIGINAL CLASS.

Module: ADSIM003

Explanation: The assign/reassign of the user’s trancode class failed on the setup or at the end of the test.

User Response: If the failure is at the end of the test, the trancode can be reassigned by the IMS operator or anyone else with the proper authority. Verify that the IMS security GEN was done and is active before contacting the BMC Support Center.

XPD1187

CODE DEBUG INTERNAL ERROR - INVALID RETURN CODE FROM IMS EXIT.

Module: ADSIM003

User Response: Contact BMC Support.

XPD1188

ERROR IN REASSIGNING THE TEST TRANSACTION/S. SOME TEST TRANSACTIONS MAY NOT HAVE BEEN REASSIGNED TO THEIR ORIGINAL CLASS.

Module: ADSIM003

Explanation: The reassign of the user’s trancode class failed at the end of the test.

User Response: The trancode can be reassigned by the IMS operator or anyone else with proper authority. Verify that the IMS security GEN was done before contacting the BMC Support Center.

XPD1189 

THE ENQ TO SERIALIZE THE CODE DEBUG BMP FAILED. PLEASE TRY AGAIN.

Module: ADSIM003

Explanation: Another user can be starting an Code Debug IMS test and the setup BMP is in use.

User Response: Try starting the test again. If the error persists, Contact BMC Support.

XPD1190

THE REASSIGN OF USER TRANSACTIONS WAS NOT DONE.

Module: ADSIM003

Explanation: The internal BMP used at test-end could not be run. The test transactions remain assigned to the Code Debug classes.

User Response: Have the IMS operator reassign them to their original class. If the problem persists, contact your internal technical support.

XPD1191

ADSIM001 NOT RESPONDING (+10 SECONDS), TERMINATING THIS TEST.

Module: ADSIM003

Explanation: Code Debug TSO IMS service routine ADSIM001 is serialized via an ENQ. If the service does not respond, other test attempts will fail with the XPD1189 message. XPD1120 is issued when terminating the offending test, allowing other tests to proceed.

User Response: Check to see if Transaction XPEDTX1 or Program ADSIM001 is stopped. If so start them.

XPD1198

BTSCOM00 NOT FOUND IN MODULE BTSRC000. TEST TERMINATED.

Module: XPBTBTSF

Explanation: Code Debug received an incorrect address of CSECT BTSCOM00 within BTSRC000. The problem occurs because BTSCOM00 is not the first CSECT in BTSRC000 at the user site.

User Response: Contact your internal technical support if the problem cannot be corrected at the user site.

XPD1199

THERE HAS BEEN A PARSING ERROR - CONTACT TECHNICAL SUPPORT.

Module: ADSIM003

Explanation: The PARM string passed to Code Debug IMS is not in the correct format.

User Response: Check the PARM strings as installed before contacting the BMC Support Center.

XPD1200

THE RESTART OF X(5) X(8) FAILED. STATUS = X(2)

Module: ADSIM003

Explanation: A restart of the named IMS entity (i.e., TRAN...) failed. The IMS status code is given.

User Response: Contact your internal technical support.

XPD1201

A CONVERSATIONAL TRANSACTION IS NOT ALLOWED IN A BMP TEST.

Module: ADSIM003

Explanation: This transaction is generated as Conversational (SPA was specified on the TRANSACT macro).

User Response: Try testing with MPP or IFP.

XPD1202

X(5) ABEND IN PROCESSING THE X(3) REGION. CODE DEBUG WILL ATTEMPT TO RESTART THE USER PGM AND/OR TRAN. IF THE IMS TERMINAL IS LOCKED, IT WILL HAVE TO BE STARTED MANUALLY.

Module: ADSIM003

Explanation: There was an ABEND during a user test in an MPP, BMP, or IFP message region. User ABEND codes are in decimal format.

User Response: Check the status of the test tran and program. Code Debug IMS may not have been able to restart them. If your IMS terminal is locked, it will have to be restarted by someone with authorization. If the reason for the ABEND is not apparent from the code, Contact BMC Support.

XPD1203

PROCESSING ENDED DUE TO ATTENTION INTERRUPT.

Module: ADSIM002

Explanation: The Code Debug IMS test was ended when the attention key was hit. This is an informational message.

XPD1204 

A NON-BLANK STATUS CODE OF X(2) WAS RETURNED AFTER A DLI CALL.

Module: ADSIM003

Explanation: While running the Code Debug BMP to set up an IMS test, one of the calls to the database returned a bad status code. The code is given.

User Response: Check the IMS system log for additional error messages. If the error is not apparent, contact your internal technical support.

XPD1205

ABEND OCCURRED DURING PROCESSING

Module: ADSIM002

Explanation: The IMS region ended with a system or user ABEND. User ABEND codes are in decimal format.

User Response: If the reason for the ABEND is not apparent from the code, Contact BMC Support.

XPD1206

A NON-BLANK STATUS CODE OF X(2) OCCURRED DURING /RSTART PROCESSING. THE INTERNAL CODE WAS N(3).

Module: ADSIM003

Explanation: Code Debug is unable to RSTART the terminal associated with the IMS transaction.

User Response: If your terminal is hung in response mode, try to free it by entering the IMS /RSTART command.

XPD1207

UNABLE TO OPEN DDNAME XXXXXXXX

Module: XPBTBTSE

Explanation: An OPEN failed for the ddname specified.

User Response: Make sure that the ddname specified is available.

XPD1208 

LOAD MODULE XXXXXX NOT FOUND

Module: XPBTBTSE

Explanation: The load module specified was not found in the allocated library.

User Response: Contact your internal technical support.

XPD1209

LOAD MODULE IN OVERLAY FORMAT - NOT SUPPORTED BY CODE DEBUG TSO

Module: XPBTBTSE

Explanation: Code Debug TSO does not support overlay format.

User Response: The module should be recompiled without overlays for testing purposes.

XPD1210

UNABLE TO OPEN DDNAME XDYNAMIC

Module: XPBTBTSE

Explanation: An OPEN failed for the XDYNAMIC ddname.

User Response: Verify that the XDYNAMIC ddname is available.

XPD1212 

READ FAILURE FOR DDNAME XXXXXXXX

Module: XPBTBTSE

Explanation: Code Debug TSO was unable to read the specified ddname.

User Response: Contact your internal technical support.

XPD1213

WRITE FAILURE FOR DDNAME XDYNAMIC

Module: XPBTBTSE

Explanation: Code Debug TSO was unable to write to the XDYNAMIC ddname.

User Response: Contact your internal technical support.

XPD1214

INSUFFICIENT DIRECTORY BLOCKS FOR XDYNAMIC

Module: XPBTBTSE

User Response: Reallocate XDYNAMIC with increased number of directory blocks.

XPD1215

INSUFFICIENT MEMORY FOR BUFFER

Module: XPBTBTSE

User Response: The REGION parameter for the TSO session or the batch JOB should be increased.

XPD1216

XXXXXXXX MUST BE ALLOCATED TO SUPPORT BLOCKSIZE XXXXX

Module: XPBTBTSE

Explanation: The ddname must have a blocksize greater than or equal to the blocksize specified.

User Response: Reallocate the ddname specified with an increased blocksize.

XPD1217

ASSEMBLER MACRO ISITMGD FAILED OR IS NOT SUPPORTED ON SYSTEM

Module: XPBTBTSE

User Response: Contact BMC Support.

XPD1218

ERROR - BINDER INVOKED FROM WITHIN USER EXIT

Module: XPBTBTSE

User Response: Contact BMC Support.

XPD1219

ERROR - OPERATING SYSTEM NOT AT CORRECT DFSMS/MVS LEVEL

Module: XPBTBTSE

User Response: Contact BMC Support.

XPD1220

ERROR - IEWBIND MODULE COULD NOT BE LOCATED BY CODE DEBUG

Module: XPBTBTSE

User Response: Contact BMC Support.

XPD1221

ERROR - GETMAIN FAILURE FOR BINDER GETBUF FUNCTION

Module: XPBTBTSE

User Response: Contact BMC Support.

XPD1222

DFSMS BINDER ERROR FUNC=function RTNCODE=nn RSNCODE=nnnnnnnn

Module: XPBTBTSE

User Response: See IBM z/OS MVS Program Management: Advanced Facilities manual for the IBM Linkage Editor Binder Return and Reason codes for the indicated function.

XPD1223

THIS OFFSET LOWER THAN PREVIOUS ONE X(40)

Module: ADSRA608

Explanation: A possible error may have been detected. Even though statements are in sequential order, offsets may not be (i.e., multiple CSECT).

User Response: Contact your internal technical support.

XPD1228

THE FOLLOWING VARIABLE HAS BEEN TRUNCATED TO 126 CHARACTERS: X(255)

Module: ADSRA614

Explanation: Any name greater than 126 characters is truncated. This can create unintentional duplicate names.

User Response: One solution is to rename to retain uniqueness.

XPD1229

X(30) IN X(8) HAS INVALID ADDRESS OF N(4)

Module: ADSRA409

Explanation: The address of the designated data item is either invalid or fetch-protected. A value of zero is substituted for the address of the item.

User Response: This condition should not occur and should be reported to your internal technical support.

XPD1231

THE CODE DEBUG X(5) EXIT ROUTINE HAS BEEN ISSUED AGAIN AFTER BEING RESET

Module: ADSRA105

Explanation: A S0C1 program interrupt was intercepted by the ESTAE exit routine when the Code Debug ESPIE/SPIE macro was issued. The appropriate exit is established again.

XPD1232

(4) BREAKPOINT(S) RESET IN MODULE X(8) AFTER MEMORY OVERLAY

Module: ADSRA602

Explanation: One or more breakpoints were reset as a consequence of the execution of an Code Debug command that changed memory contents in a module being tested.

User Response: The breakpoints can be restored if valid OP codes are found at the original offsets.

XPD1233 

NO DEFINITION FOR MACRO ON STATE N(3)

Module: ADSRA608

Explanation: Since the verb was not on the list of OP codes, a macro is assumed. But no OPSYN or definition for the macro was found on the indicated statement.

XPD1234

ATTEMPT TO LOAD X(8) FAILED - ABEND CODE = X(4) REASON CODE = N(1)

Module: ADSRA107

Explanation: The module specified with the USERABTX SET command for use as the batch abnormal termination exit routine could not be loaded. The ABEND and reason codes describing the problem are formatted in this message.

XPD1235

CANCEL REQUEST BY X(8) SATISFIED - X(8) HAS BEEN DELETED

Module: ADSRA268 and ADSRA494

Explanation: The cancel of the previously loaded dynamic module was performed as requested.

XPD1236

CANCEL REQUEST BY X(8) IGNORED - NO PRIOR DYNAMIC CALL OF X(8)

Module: ADSRA268 and ADSRA494

Explanation: A cancel was requested for a module which was either not called dynamically or was previously cancelled.

XPD1240

CODE DEBUG ESPIE RESET BY X(8) MASK BITS N(2) - CODE DEBUG ESPIE RESTORED

Module: ADSRA273

Explanation: The Code Debug issued ESPIE was reset by the specified program. The Code Debug issued ESPIE must be the active ESPIE, therefore, the Code Debug issued ESPIE was restored.

XPD1243

INSUFFICIENT MEMORY INDICATED BY X(7) ABEND - LARGER REGION SIZE MAY BE REQUIRED

Module: ADSRA105

Explanation: A system ABEND was caused by insufficient memory.

User Response: The test should be reinitiated with a larger region or address space.

XPD1244

STATEMENT NUMBER N(3) SKIPPED AFTER NULL PERFORM IN MODULE X(8)

Module: ADSRA449

Explanation: A skip was processed for a PERFORM that did not have code associated with it. The next statement with one or more instructions was bypassed even though it was not designated for skip processing.

XPD1245

X(8) X(10) FROM LINKLIST

Module: ADSRA222

Explanation: The load module name was preloaded or loaded from LINKLIST. Code Debug may not be able to access the module.

User Response: Contact your internal technical support.

XPD1246

NO INCORE JFCB FOR X(8)

Module: ADSRA222

Explanation: There was an I/O operation error in the JOB file control block accessing the XTASKLIB or USERLIB.

User Response: Contact your internal technical support.

XPD1247

RECURSIVE ABEND CONDITION ENCOUNTERED - NOTIFY TECHNICAL SUPPORT

Module: ADSRA105 and ADSRA304

Explanation: An ABEND occurred during the processing of a previous ABEND. The test is terminated with a user 3007 abend and a dump.

User Response: The information in the session log should be given to your internal technical support.

XPD1250

MESSAGE NUMBER N(4) NOT AVAILABLE

Module: ADSRA125

Explanation: Code Debug was unable to obtain the message text, for the specified message number, from the message module.

User Response: Contact BMC Support.

XPD1251

IMS INTERCEPT IS NOT AVAILABLE. ENSURE CODE DEBUG INTERCEPT INSTALL JOB, JCLIMSLR, HAS BEEN RUN.

Module: ADSIM017

Explanation: JCLIMSLR must be run after each IPL of your system.

User Response: Contact your internal technical support.

XPD1252

PC ROUTINE ABENDED.

Module: ADSIM017

Explanation: There was an unrecoverable error in Code Debug’s IMS intercept PC.

User Response: Contact BMC Support.

XPD1253

CODE DEBUG TRANCODE SWITCHING INACTIVE.

Module: ADSIM017

Explanation: Code Debug’s IMS PC intercept is installed, but is “inactive.” JCLIMSLR must be run with PARM=ACTIVATE.

User Response: Contact your internal technical support.

XPD1254

UNKNOWN IMS SUBSYSTEM NAME ims-subsystem-id

Module: ADSIM017

Explanation: Code Debug’s IMS PC intercept was not initialized with the IMS subsystem being tested (ims-subsystem-id). Either specify the correct IMS subsystem name, or run JCLIMSLR with PARM=DEACTIVATE, modify the control cards to include the desired IMS subsystem name, and run JCLIMSLR with PARM=ACTIVATE.

User Response: Contact your internal technical support.

XPD1255

HANDSHAKE ALREADY DONE IN ADDRESS SPACE.

Module: ADSIM017

User Response: Contact BMC Support.

XPD1256

STORAGE OBTAIN FAILED.

Module: ADSIM017

Explanation: The REGION allocated to your TSO ID is insufficient.

User Response: Increase the REGION allocated to your TSO ID and try again. If the problem persists, Contact BMC Support.

XPD1257

FORCE/ACTIVATE SINCE HANDSHAKE.

Module: ADSIM017

User Response: Contact BMC Support.

XPD1258

NO HANDSHAKE DONE IN ADDRESS SPACE.

Module: ADSIM017

User Response: Contact BMC Support.

XPD1259

HANDSHAKE DONE BY ANOTHER TASK.

Module: ADSIM017

User Response: Contact BMC Support.

XPD1260

COMMIT FAILED. NO RESERVED TRANCODES.

Module: ADSIM017

User Response: Contact BMC Support.

XPD1261

RESERVE FAILED. ALL TARGET TRANCODES ARE BUSY.

Module: ADSIM017

Explanation: All Code Debug IMS pseudo transaction codes are disabled or busy.

User Response: Try again later or contact the individuals responsible for Code Debug IMS and have them increase the available number of Code Debug IMS pseudo transactions and include the new set in the JCLIMSLR intercept install JCL.

XPD1262

ELIMINATE FAILED. TARGET TRANCODE UNKNOWN.

Module: ADSIM017

User Response: Contact BMC Support.

XPD1263

ELIMINATE FAILED. TARGET TRANCODE USED BY ANOTHER TASK.

Module: ADSIM017

User Response: Contact BMC Support.

XPD1264

UNEXPECTED RETURN CODE FOR /DISPLAY TRANSACTION COMMAND.

Module: ADSIM017

User Response: Contact BMC Support.

XPD1265

INVALID TRANCODE NAME.

Module: ADSIM017

User Response: Specify a valid transaction code name.

XPD1266

TARGET TRANCODE UNDEFINED TO IMS.

Module: ADSIM017

Explanation: The selected Code Debug pseudo transaction is not defined to IMS. (Code Debug pseudo transactions usually start with XPED followed by a four digit number, e.g. XPED0001.)

User Response: Contact the individuals responsible for Code Debug IMS and have them ensure that the Code Debug pseudo transactions are defined to the desired IMS subsystem.

XPD1267

UNEXPECTED RETURN CODE FOR /DISPLAY TRANSACTION QCNT CMD.

Module: ADSIM017

Explanation: When issuing the above command, Code Debug encountered a return code that could not be handled.

User Response: Contact BMC Support.

XPD1268

INVALID TRANCODE NAME (QCNT).

Module: ADSIM017

Explanation: While issuing the /DISPLAY transaction QCNT CMD, it was discovered that the transaction name is invalid.

User Response: Specify the correct transaction code name to be displayed. If the problem persists, Contact BMC Support.

XPD1269

/ASSIGN TRANCODE FAILED.

Module: ADSIM017

Explanation: Attempt to assign a dummy transaction code failed on the local LPAR.

User Response: Contact BMC Support.

XPD1270

response-type RECEIVED FROM LPAR lparname

Module: ADSIM019

Explanation: response-type can be NEGATIVE RESPONSE or POSITIVE RESPONSE. lparname is the name of the LPAR that provided the response. NEGATIVE RESPONSE indicates that there was a problem with the HCI on LPAR lparname. Processing continues.

User Response: Review the HCI configuration information supplied at Code Debug TSO installation and correct as necessary. Also ensure that the HCI specified is active on LPAR lparname. If these don’t resolve the issue, Contact BMC Support.

XPD1271

IMS INTERCEPT IS NOT AVAILABLE.

Module: ADSIM019

Explanation: The Code Debug IMS intercept is not active on this LPAR.

User Response: Run program XPIMSTLT to install and activate Code Debug IMS intercept.

XPD1272

SYSTEM RELEASE LEVEL LESS THAN OS 390.

Module: ADSIM019

Explanation: IMS cross-LPAR support requires a minimum operating system level of OS 390.

User Response: None.

XPD1273

IMS SUBSYSTEM NOT DEFINED AS AN IMSPLEX TO XPIMSTLR.

Module: ADSIM019

Explanation: The request received was for an IMS subsystem that is not defined as a member of an IMS Shared Queue in the XPIMSTLR control cards.

User Response: Review the control cards used as input to the XPIMSTLR program and correct them as necessary.

XPD1274

TOO MANY LPARS DEFINED IN IMSPLEX.

Module: ADSIM019

Explanation: IMS Shared Queue support is limited to ten LPARs. More than that have been defined in the control cards used as input to the XPIMSTLR program.

User Response: Review the control cards used as input to the XPIMSTLR program and correct them as necessary.

XPD1275

THIS LPAR NOT DEFINED DURING INSTALL.

Module: ADSIM019

Explanation: The current LPAR is not defined as part of an IMS Shared Queue environment in the control cards used as input to the XPIMSTLR program.

User Response: Review the control cards used as input to the XPIMSTLR program and correct them as necessary.

XPD1276

LPAR lparname NOT DEFINED DURING INSTALL.

Module: ADSIM019

Explanation: The LPAR lparname was not defined in the HCI configuration information supplied at Code Debug TSO installation.

User Response: Review the HCI configuration information supplied at Code Debug TSO installation and correct it as necessary.

XPD1277

LPAR lparname NOT RESPONDING.

Module: ADSIM019

Explanation: An attempt to contact LPAR lparname has timed-out. This message can result if an LPAR is down.

User Response: If the LPAR is active, review the LPAR data supplied in the HCI configuration information specified at Code Debug TSO installation and correct it as necessary. If this does not resolve the issue, Contact BMC Support.

XPD1290

EXECUTION CANNOT BE RESUMED, THE ESPIE RECOVERY EXIT HAS BEEN TURNED OFF. MEMBER= X(8), MODULE= X(8)

Module: ADSRA129

Explanation: Execution of the application module could not be continued subsequent to Code Debug processing. The Code Debug ESPIE and the Code Debug SVC recovery exits have been disabled.

User Response: Remove the command SET ESPIE OFF from your initial script, or, if your site has the optional Code Debug SVC breakpointing installed, add to your initial script the commands SET SVCBP ON and SET USVC ### (where ### is the SVC number that was assigned to Code Debug during installation).

XPD1316

 ADSIS316 - MULTI-BATCH STAGING FILE OPEN FAILED.

Module: ADSIS316

Explanation: The utility was unable to open the file that contains the Multi-Batch records.

User Response: Ensure the file is properly allocated and initialized.

XPD1316

ADSIS316 - NO UPDATE ACCESS TO MULTI-BATCH FILE.

Module: ADSIS316

Explanation: The utility requires update access to the file that contains the Multi-Batch records.

User Response: Ensure update access is provided to the file that contains the Multi-Batch records.

XPD1316   

ADSIS316 - NO PARM PASSED.

Module: ADSIS316

User Response: Contact BMC Support.

XPD1316 

ADSIS316 - TABLE OVERLOW (> 5000 RECS) RUN AGAIN

Module: ADSIS316

Explanation: When the utility is run, obsolete Code Debug Eclipse records are deleted. This message indicates that more than 5000 obsolete Code Debug Eclipse records were encountered. The first 5000 were deleted, but the utility must be run again to delete the remaining obsolete records.

User Response: Run the utility again to delete the remaining obsolete records.

XPD1316

ADSIS316 - MULTI-BATCH INTERCEPT NOT INSTALLED.

Module: ADSIS316

User Response: Contact BMC Support.

XPD1316

ADSIS316 - MULTI-BATCH FILE I/O ERROR.

Module: ADSIS316

Explanation: The utility was unable to read from or write to the file that contains the Multi-Batch records.

User Response: Ensure the file is properly allocated and initialized.

XPD1316 

ADSIS316 - GETMAIN FOR KEY HOLD AREA FAILED.

Module: ADSIS316

User Response: Increase the REGION size for the job and run it again.

XPD1316

ADSIS316 - INVALID PARM VALUE (NOT G, B OR S).

Module: ADSIS316

User Response: Contact BMC Support.

XPD1316

ADSIS316 - INVALID PARM LENGTH.

Module: ADSIS316

User Response: Contact BMC Support.

XPD1316

ADSIS316 - INVALID PARM ADDRESS.

Module: ADSIS316

User Response: Contact BMC Support.

XPD1316

ADSIS316 - NO RECORDS TO DELETE.

Module: ADSIS316

Explanation: Informational message that indicates that there were no obsolete Code Debug Eclipse records.

XPD1316

ADSIS316 - nnnn RECORDS OF TYPE G DELETED.

Module: ADSIS316

Explanation: Informational message that indicates that there nnnn obsolete Code Debug Eclipse records deleted.

XPD1360

INVALID PARAMETER FOR REVIEW MODE

Module: ADSRA136

Explanation: The parameter is not valid for revision mode.

User Response: Check the command syntax.

XPD1362

COMMAND REJECTED - REVIEW MODE NOT IN EFFECT

Module: ADSRA136

Explanation: The command is valid only when review mode is in effect.

User Response: Check your reference manual.

XPD1365

REVIEW PROCESSING INTERRUPTED BY ATTENTION

Module: ADSRA136

Explanation: A review execution pause was requested with the attention key.

User Response: None.

XPD1940

DATE/TIME OPTION HAS BEEN DISABLED - BY DEFAULT

Module: ADSRA194

Explanation: Checking for a date/time mismatch has been disabled.

User Response: None.

XPD1941

SECURITY CHECK FAILED FOR <language-type> LANGUAGE

Module: ADSRA194

Explanation: An attempt was made to access the DDIO file for a member of a language type for which you are not licensed.

User Response: Contact your internal technical support if you believe you are licensed for the specified language.

XPD1942

NO DATE/TIME PRESENT FOR MODULE <module-name>

Module: ADSRA194

Explanation: The specified load module does not contain a date/time stamp. Therefore, Code Debug TSO cannot guarantee an exact match between the load module and the DDIO file member.

User Response: None.

XPD1943

PLEASE COMPILE WITH CURRENT CSS FOR FULL NESTED COBOL SUPPORT

Module: ADSRA194

Explanation: The nested COBOL program was processed with a back-level CSS. For full nested COBOL support, you must recompile your program with a currently supported level of LP.

User Response: None.

XPD1944 

A DSA FOR MODULE X(8) WAS NOT FOUND DURING TERMINATION

Module: ADSRA194

Explanation: During termination of a test that was initiated by the EXIT command, the named module had opened files, but did not close them. Code Debug tried to determine the Dynamic Storage Area (DSA) for the module in order to close the files but was unsuccessful. The files will be closed by MVS.

User Response: None. This message is informational only.

Explanation: There is a limitation of 32,767 data set names for DDIO/source libraries.

User Response: Eliminate some DDIO/source data set names via combination or by breaking the test case into smaller units.

XPD1945

ADSRA194 CSS SHARED DIRECTORY HAS ALLOCATED > 32767 DSNAMES

Explanation: There is a limitation of 32,767 data set names for DDIO/source libraries.
User Response: Eliminate some DDIO/source data set names via combination or by breaking the test case into smaller units.

XPD1947

ADSRA194 PROGRAM <name> PROCESSED BY AUTOMATIC BINARY OPTIMIZER, SOURCE UNAVAILABLE.

Explanation: The program has been processed by IBM’s Automatic Binary Optimizer (ABO). Because this causes a reconfiguration of the load module, it no longer matches what was produced during the original compilation. Since Common Shared Services (CSS) creates the information used by Code Debug TSO from the compilation listing, all program offsets are now invalid, and the source will not be displayed.

User Response: Use the original non-ABO version for testing, or re-compile the source and re-link the program.

XPD2100

THE COMBINED CSECT SIZES HAVE EXCEEDED THE LOAD MODULE LENGTH VALUE CONTAINED IN THE CDE EXTENT LIST

Module: ADSRA218 and ADSRA219

Explanation: The combined CSECT sizes have exceeded the size of the load module. Continued processing could lead to the building of incorrect control blocks and possible storage corruption.

User Response: Contact your internal technical support.

XPD2210

PL/I OPT MODULE WAS PRELOADED OR IS IN PROTECTED STORAGE - CANNOT RESET ESPIE OR ESTAE

Module: ADSRA221

Explanation: Code Debug was unable to preset a desired number of options because they had already been implemented or the options module is in protected storage and cannot be modified.

User Response: Depending on the environment and the type of Code Debug functions used, testing may function normally. If an ABEND occurs or breakpoints are not recognized, the user should place loadable modules into a non-authorized library as specified in SETUP and then rerun the test.

XPD2211

LE/370 LIBRARIES ARE PRELOADED OR IN PROTECTED STORAGE - CANNOT TURN TRAP OFF AS REQUESTED

Module: ADSRA221

Explanation: Code Debug was unable to preset a desired number of options because they had already been implemented or the options module is in protected storage and cannot be modified.

User Response: Depending on the environment and the type of Code Debug functions used, testing may function normally. If an ABEND occurs or breakpoints are not recognized, the user should place loadable modules into a non-authorized library as specified in SETUP and then rerun the test.

XPD2212

NO PL/I OPTIONS MODULE TO RESET

Module: ADSRA221

Explanation: Code Debug was unable to preset desired options because it could not locate a PL/I options module.

User Response: Depending on the environment and the Code Debug functions used, testing may or may not function normally. If an ABEND occurs or breakpoints are not recognized, the user should ensure that language options and modules are in a library specified in SETUP.

XPD2213

CEE SPIE OPTION WAS FORCED TO ON

Module: ADSRA221

Explanation: Code Debug expects the LE TRAP option to be TRAP(ON,SPIE). Code Debug has found TRAP(ON,NOSPIE) and has forced TRAP(ON,SPIE).

User Response: None.

XPD2214

LE ENVIRONMENT RECOGNIZED

Module: ADSRA221

Explanation: LE module CEEBINIT was found.

User Response: None.

XPD2215

LE ENVIRONMENT HAS NOT BEEN RECOGNIZED AND THE LE ROUTINES HAVE NOT BEEN ESTABLISHED

Module: ADSRA221

Explanation: LE module CEEBINIT was not found.

User Response: Add the LE runtime libraries to your SETUP.

XPD2222

MODULE X(8) HAS LINKAGE SECTION WITHOUT USING

Module: ADSRA417

Explanation: Normally, when a linkage section is coded in a program, there is a USING clause in the Procedure Division or entry statement.

XPD2520

MAXIMUM NUMBER OF DDIO FILES ALLOCATED

Module: ADSRA252, ADSRA253

Explanation: The maximum number of DDIO files are currently allocated.

User Response: Exit Code Debug TSO to dynamically unallocate all DDIO files.

XPD3000

ABEND-AID DD HAS BEEN ALLOCATED TO A TEMPORARY DATASET

Module: ADSRA311

Explanation: If you don’t have an ABEND-AID DD card allocated to your test session, Code Debug will dynamically allocate one for you (if you are using the AA SNAP command).

User Response: None.

XPD3001

NO LEAID MODULE FOUND UNDER LE/370 ENVIRONMENT

Module: ADSRA311

Explanation: In order for the ‘AA SNAP’ command to function in an LE environment, BMC’s ABEND-AID LEAID must be installed as an LE abnormal termination exit.

User Response: See to the applicable Language Environment (LE) task in either “Milestone 3: Configure ABEND-AID — New Installation” or “Milestone 4: Configure ABEND-AID — Upgrade” in ABEND-AID installation and Configuration Guide.

XPD3002

THE AA SNAP FUNCTION REQUIRES A SUPPORTED RELEASE OF ABEND-AID/SNAPAID

Module: ADSRA311

Explanation: In order to use the AA SNAP command, you must have previously installed and activated BMC’s ABEND-AID product.

User Response: If ABEND-AID is installed at your site, ensure that it has been activated.

XPD3003

PASSING mmmmmmmm DDIO INFO TO aaaaaaaa RELEASE vvrr

Module: ADSRA311

Explanation: This message is informational. It indicates the source member and the release of SNAPAID or LEAID being used for an AA SNAP command.

User Response: None.

XPD3030

CHANGED KEYWORD IGNORED WITH DEFINE

Module: ADSRA286

Explanation: The changed keyword and the defined keyword are mutually exclusive. If both are specified, the defined keyword takes precedence.

XPD3031

DEFINE LENGTH OF X(4) AND OFFSET OF X(4) EXCEEDS THE END OF DATA GROUP B(4) WHICH HAS A SIZE OF X(4)

Module: ADSRA286

Explanation: The field being defined must not overlap the data group boundary.

User Response: None.

XPD3032 

DEFINE LENGTH OF ’,X(4),’ IS GREATER

Module: ADSRA286

Explanation: This message is no longer valid.

User Response: None.

XPD3035

INSUFFICIENT MEMORY FOR X(21)

Module: ADSRA436

Explanation: No storage can be allocated for the element display block.

User Response: Increase the REGION size for the TSO logon or batch JOB.

XPD305

MAXIMUM OF 15 BASE REGISTERS EXCEEDED

Module: ADSRA217

Explanation: The maximum number of base locator cells that Code Debug can maintain is 15. This maximum was exceeded.

User Response: Contact your internal technical support.

XPD3052

ALLOCATION OF GPR BUFFER FAILED

Module: ADSRA217

Explanation: An attempt to allocate memory failed for the GPR buffer.

User Response: Contact your internal technical support.

XPD3067

TO BROWSE PDS - ENTER LIB AND MEMBER

Module: ADSRA407

Explanation: To browse a data set, you must enter the member name as well as the name of the data set.

User Response: None.

XPD3072

NO BLI FOR OFFSET ’X(4)’ IN ’C(8)’

Module: ADSRA217

Explanation: This message is no longer valid.

User Response: None.

XPD3073 

NO CAPEX BASE LOCATORS FOR ’C(8)’

Module: ADSRA217

Explanation: This message is no longer valid.

User Response: None.

XPD3081

ATTEMPT TO LOAD ’C(8)’ FAILED -

Module: ADSRA308

Explanation: Because Test Case Facility is obsolete, this message is no longer valid.

User Response: None.

XPD3082

TCF FUNCTION: ’C(4)’ FAILED

Module: ADSRA308

Explanation: Because Test Case Facility is obsolete, this message is no longer valid.

User Response: None.

XPD3083

LOOKUP FOR ’C(44)’ FAILED

Module: ADSRA308

Explanation: Because Test Case Facility is obsolete, this message is no longer valid.

User Response: None.

XPD3097

INSUFFICIENT STORAGE TO BUILD CONTROL BLOCK

Module: ADSRA307 if Testing PL/I, ADSRA309 if Testing C

Explanation: An Element Display Block for a data item could not be created.

User Response: Increase either the TSO logon size or the REGION parameter on the JCL in order to run the batch test and begin the test again.

XPD3220

FAILED TO DYNAMICALLY ALLOCATE LINKLIST LIBRARY RC=X(2) RSNCODE=X(2)

Module: ADSRA223, ADSRA322

Explanation: When attempting to load a module from the LINKLIST, the library allocation failed. See 'Interpreting DYNALLOC return codes' in the IBM MVS Programming: Authorized Assembler Services Guide

XPD3221

FAILED TO OPEN THE DYNAMICALLY ALLOCATED DDNAME

Module: ADSRA223, ADSRA322

Explanation: When attempting to load a module from the LINKLIST, Code Debug is unable to open the dynamically allocated library.

XPD3222

FAILED TO CLOSE THE DYNAMICALLY ALOCATED DDNAME

Module: ADSRA222, ADSRA322

Explanation: When attempting to load a module from the LINKLIST, Code Debug is unable to close the dynamically allocated library.

XPD3223

FAILED TO DYNAMICALLY DEALLOCATE LINKLIST LIBRARY RC=X(2) RSNCODE=X(2)

Module: ADSRA222, ADSRA322

Explanation: When attempting to load a module from the LINKLIST, Code Debug is unable to dynamically deallocate the LINKLIST library. See 'Interpreting DYNALLOC return codes' in the IBM MVS Programming: Authorized Assembler Services Guide

XPD3224

FAILED TO DYNAMICALLY ALLOCATE NEW DD FOR CODE DEBUG TASK LIBRARY RC=X(2) RSNCODE=X(2)

Module: ADSRA322

Explanation: When attempting to load a Language Environment module from the LINKLIST, Code Debug is unable to allocate an additional ddname. See 'Interpreting DYNALLOC return codes' in the IBM MVS Programming: Authorized Assembler Services Guide

XPD3225

FAILED TO DYNAMICALLY DEALLOCATE PRIMARY LINKLIST DD RC=X(2) RSNCODE=X(2)

Module: ADSRA322

Explanation: When attempting to load a Language Environment module from the LINKLIST, Code Debug is unable to deallocate the primary LINKLIST ddname. See 'Interpreting DYNALLOC return codes' in the IBM MVS Programming: Authorized Assembler Services Guide

XPD3226

FAILED TO DYNAMICALLY DECONCATENATE LINKLIST LIBRARY RC=X(2) RSNCODE=X(2)

Module: ADSRA322

Explanation: When attempting to load a Language Environment module from the LINKLIST, Code Debug is unable to deconcatenate the LINKLIST library. See 'Interpreting DYNALLOC return codes' in the IBM MVS Programming: Authorized Assembler Services Guide

XPD3333

CEE COBOL TRAP OPTION WAS FORCED TO OFF

Module: ADSRA417

Explanation: This message is no longer valid.

User Response: None.

XPD3650

STATEMENT IS NOT EXPANDABLE

Module: ADSRA365

Explanation: The GEN command is only allowed on EXPANDABLE statements.

User Response: None.

XPD3651

GEN PREVIOUSLY PERFORMED FOR EXEC

Module: ADSRA365

Explanation: A GEN was previously performed on this statement.

User Response: None.

XPD3652

DELETE PREVIOUSLY PERFORMED FOR EXEC

Module: ADSRA365

Explanation: A DELETE GEN was previously performed on this statement.

User Response: None.

XPD3700

NUMBER IN INSERT NOT NUMERIC C(8)

Module: ADSRA370

Explanation: You attempted to insert a line using a line number that is not numeric.

User Response: Check the listing for a valid line number. This is probably a typographical error.

XPD3701

MISSED NUMBER IN INSERT COMMAND C(8)

Module: ADSRA370

Explanation: An attempt was made to insert a line of code from a user test script. However, there was no line number specified on the INSERT command.

User Response: Add the line number and resubmit.

XPD3702

INSERTED LINE MORE THAN 61 BYTES C(8)

Module: ADSRA370

Explanation: An inserted line cannot exceed 61 bytes.

XPD3703

INSERTED LINE NUMBER NOT FOUND IN C(8)

Module: ADSRA370

Explanation: The line number specified does not exist or is a display-only line. INSERT cannot be performed at the indicated line number.

XPD3704

COMMAND PERMITTED ONLY ON CODE LINE

Module: ADSRA370

Explanation: The INSERT command is allowed only for a code line.

User Response: Retry the INSERT command on a code line.

XPD3705

COMMAND NOT PERMITTED FOR THIS COBOL VERB

Module: ADSRA370

Explanation: The INSERT command is not permitted on COBOL verbs such as PERFORM, GOBACK, RUN STOP, and EXIT.

XPD3730

CONTROL BLOCKS DISAGREE ON COBOL TGT LENGTH

Module: ADSRA373

Explanation: The COBOL TGT length calculated by module ADSRA373 does not agree with the length contained in the Code Debug COBOL extension block. This may be a result of incorrect Memory Map information that was supplied by CSS. If testing is continued, it is likely that data displayed by Peek and/or Keep will be incorrect or not addressable.

User Response: Contact your internal technical support.

XPD3801

NO MATCH ON EXTERNAL NAME: xxxxxxxx USING TOKEN: xxxxxxxx

Module: ADSRA380 and ADSRA394

Explanation: External CSECT name was not found using indicated CSS Token.

User Response: Contact your internal technical support.

XPD3860

ERROR RETRIEVING NPMAP RECORDS FROM CSS FOR <module>

Module: ADSRA386

Explanation: A CSS error has occurred while trying to retrieve NPMAP records for the specified module. This is probably caused by running Code Debug with a back-level version of CSS.

User Response: Check to make sure you are using a currently support CSS release. If you have installed the correct release, contact your internal technical support.

XPD3870

GETMAIN FAILED IN MODULE X(8) FOR N(4) HEX BYTES

Module: Multiple modules.

Explanation: An attempt to acquire additional storage failed.

User Response: Increase the REGION size and try again.

XPD3871

INVALID TOKEN IN CSS CLIST - N(4) - X(30)

Module: ADSRA387

Explanation: A valid verb matching the token cannot be found in the CSS CLIST.

User Response: Contact your internal technical support.

XPD3872

NO BREAKPOINTS FOUND FOR NEXT COMMAND - MODULE X(8)

Module: ADSRA387

Explanation: An attempt to resolve breakpoints for the NEXT command failed.

User Response: Contact your internal technical support.

XPD3873

SIZE ERROR - BREAKPOINT TABLE BUILD HALTED FOR MODULE <module-name>

Module: ADSRA387

Explanation: An internal error occurred in calculating the length of the breakpoint table. If allowed to continue, serious run-time errors would occur attempting to process breakpoint requests.

User Response: Contact your internal technical support.

XPD3874

ERROR RETRIEVING EXTENDED CLIST FROM CSS FOR <module>

Module: ADSRA387

Explanation: A CSS error has occurred while retrieving an extended CLIST for the specified module. This is probably caused by running Code Debug with a back-level version of CSS.

User Response: Check to make sure you are using a currently support CSS release. If you have installed the correct release, contact your internal technical support.

XPD3880 

INSUFFICIENT STORAGE TO BUILD STATEMENT NUMBER TABLE FOR X(8)

Module: ADSRA388, ADSRA389, and ADSRA608

Explanation: You must increase either the TSO logon size or the REGION parameter for the JCL used to run the batch test.

XPD3881

ERROR IN SOURCE LISTING - CANNOT BUILD STATEMENT NUMBER TABLE FOR X(8) - ERROR CODE X(4)

Module: ADSRA388

Explanation: An error was found building the SNT. Code Debug encountered a problem with the source listing.

User Response: Contact your internal technical support.

XPD3882

UNABLE TO RETRIEVE LAST SOURCE LINE. CSS RC=N(4)

Module: ADSRA388

Explanation: While constructing the statement number table (SNT), Code Debug could not retrieve the last statement in the source.

User Response: Contact your internal technical support.

XPD3883

UNABLE TO RETRIEVE FIRST SOURCE LINE. CSS RC=N(4)

Module: ADSRA388

Explanation: While constructing the statement number table (SNT), Code Debug could not retrieve the first statement in the source.

User Response: Contact your internal technical support.

XPD3884

INVALID STATEMENT NUMBER IN SOURCE. SLPDLLN# = N(4)

Module: ADSRA388

Explanation: The indicated source line has an invalid external number.

User Response: Contact your internal technical support.

XPD3885

INVALID DATA IN DMAP RECORD. SLPDMDEF=N(4); TOKEN=N(4)

Module: ADSRA388

Explanation: Code Debug found an invalid definition line in the DMAP.

User Response: Contact your internal technical support.

XPD3886

UNABLE TO RETRIEVE THE CSS COLUMN TABLE. CSS RC=N(4)

Module: ADSRA388

Explanation: There was a failure in the CSS Column Table that was needed to create the statement number table (SNT).

User Response: Contact your internal technical support.

XPD3887

PROGRAM X(8) DOES NOT HAVE A PROCEDURE DIVISION

Module: ADSRA388

Explanation: The named program does not have a Procedure Division statement. Code Debug does not support testing of these types of programs.

User Response: None.

XPD3920

INVALID TOKEN IN CSS CLIST - N(4) - X(30) - X(8)

Module: ADSRA392

Explanation: A valid verb matching the token cannot be found in the CSS CLIST.

User Response: Contact your internal technical support.

XPD3930

INSUFFICIENT STORAGE TO BUILD PROCEDURE HIERARCHY TABLE FOR X(8)

Module: ADSRA393

Explanation: Code Debug attempted to obtain memory for the Procedure Hierarchy Table, but there was not enough memory.

User Response: Increase the region size and try again.

XPD3931

SEVERE ERROR OCCURRED DURING LINE NUMBER CONVERSION:

Module: ADSRA393

Explanation: A severe error occurred in the conversion of internal statement numbers to external statement numbers.

User Response: Contact your internal technical support.

XPD3932

SNT = N(4) EXTERNAL = N(4) INTERNAL = N(4)

Module: ADSRA393

Explanation: A severe error occurred in the conversion of statement numbers. This message tells you the name of the statement number table (SNT) that Code Debug is trying to convert.

User Response: Contact your internal technical support.

XPD3933

A ZERO SRBLSEXT VALUE HAS ENDED THE SRB BUILD PROCESS.

Module: ADSRA393

Explanation: During the SRB build process, a value of zero was found for the last external number in the range. A zero value is not valid.

User Response: Contact your internal technical support.

XPD3934

ASSOCIATED VALUES: SRBFSEXT = N(4) SRBFSINT = N(4)

Module: ADSRA393

Explanation: This message gives associated hexadecimal values relating to the preceding message which should be of assistance in locating the failing source statement.

User Response: Contact your internal technical support.

XPD3940

VARIABLE OPTIMIZED OUT/NOT REFERENCED USING TOKEN: xxxxxxxx

Module: ADSRA394

Explanation: Unable to display variable because it was not referenced or has been optimized out.

User Response: If desired variable has been referenced in your program, recompile without optimization and retest.

XPD3960

ERROR BUILDING VARIABLE REFERENCE TABLE - SEE LOG

Module: ADSRA396

Explanation: An error occurred when trying to retrieve the PL/I Variable Reference Table.

User Response: Recompile your program with the ’DDIO(OUTPUT(VARREF))’ parameter.

XPD3961

X(8) WAS COMPILED WITHOUT THE “DDIO(OUTPUT(VARREF))” PARM WHICH IS REQUIRED FOR PEEK/KEEP FUNCTIONALITY.

Module: ADSRA396

User Response: Recompile using the correct parameter.

XPD3962

X(8) WAS COMPILED WITHOUT THE “DDIO(OUTPUT(VARREF))” PARM WHICH IS REQUIRED FOR PEEK/KEEP FUNCTIONALITY.

Module: ADSRA396

User Response: Recompile using the correct parameter.

XPD3963

GETMAIN FAILED FOR THE VARIABLE REFERENCE TABLE

Module: ADSRA396

Explanation: Code Debug attempted to obtain memory for the Variable Reference Table, but there is not enough memory.

User Response: Increase the region size and try again.

XPD3964

THE CSS LIBRARIES ALLOCATED TO THIS SESSION DO NOT SUPPORT THE REQUIREMENTS OF THIS RELEASE OF CODE DEBUG TSO.

Module: ADSRA396

Explanation: The CSS libraries installed are not compatible with the current version of Code Debug TSO.

User Response: Make sure that the correct version of CSS is used.

XPD3965

THE CSS LIBRARIES ALLOCATED TO THIS SESSION DO NOT SUPPORT THE REQUIREMENTS OF THIS RELEASE OF CODE DEBUG TSO.

Module: ADSRA396

Explanation: The CSS libraries installed are not compatible with the current version of Code Debug TSO.

User Response: Make sure that the correct version of CSS is used.

XPD3970

A GETMAIN FOR N(4) HEX BYTES FAILED. SEE LOG.

Module: ADSRA340, ADSRA387, ADSRA397, and ADSRA621

Explanation: An attempt to allocate memory for the Code Debug breakpoint table or Unicode Conversion services failed.

User Response: Increase the REGION size and try again.

XPD3971

A WORKAREA GETMAIN FAILURE OCCURRED FOR N(4) HEX BYTES OF STORAGE.

Module: ADSRA397

Explanation: An attempt to get storage for work areas failed.

User Response: Try logging on with a larger REGION size.

XPD4020

NO BREAKPOINT TABLE ENTRY FOR STATEMENT

Module: ADSRA402

Explanation: During the processing of a primary breakpoint command (such as BEFORE, COUNT, or TRACE), Code Debug was unable to locate the specified statement.

User Response: If the statement is clearly a valid one, contact your internal technical support.

XPD4021

STATEMENT NUMBER NOT FOUND IN MODULE

Module: ADSRA402

Explanation: The requested statement number does not exist in this module.

XPD4022

BREAKPOINT NOT PERMITTED FOR DISPLAY ONLY LINE

Module: ADSRA402

Explanation: Breakpoints are not permitted on lines that are for display only.

XPD4024

ONETIME BREAKPOINT ENCOUNTERED

Module: ADSRA403

Explanation: Execution has paused at a breakpoint set by a ONETIME or RUNTO command.

XPD4025

ONETIME/RUNTO NOT PERMITTED - BEFORE BREAKPOINT EXISTS

Module: ADSRA402

Explanation: Onetime breakpoints are not allowed on lines already containing a before breakpoint.

XPD4029

SPECIFIED EXECUTION MAX HAS BEEN REACHED

Module: ADSRA403

Explanation: The maximum breakpoint execution count has been reached.

XPD4032

PAUSE REQUESTED WITH ATTENTION/PA1 KEY

Module: ADSRA403

Explanation: A pause of the execution was requested by pressing the attention key.

XPD4037

CANNOT EXCEED SPECIFIED EXECUTION MAX

Module: ADSRA403

Explanation: A maximum breakpoint execution count has been reached and cannot be exceeded.

User Response: Reset breakpoint execution count.

XPD4038

BREAKPOINT WITHOUT ACTION INDICATOR

Module: ADSRA403

Explanation: An ABEND or GOBACK processing is in progress.

XPD4039

WHEN PAUSE WITH NO SATISFIED CONDITION

Module: ADSRA403

Explanation: A WHEN “true” condition was not found in the WHEN chain.

XPD4040

CODE COVERAGE RESULTS FOR PROGRAM PGMNAME WITH SYSTEM NAME SYSNAME HAVE SUCCESSFULLY BEEN WRITTEN TO THE REPOSITORY REPOSITORY-NAME

Module: ADSRA432

Explanation: The program identified by pgmname has had its Code Coverage data written to the Repository specified by repository-name with the user identifier specified by sysname.

XPD4041

XVTTARIO - text message RPERRRET=nn RPERRCD=nnnn

Module: ADSRA432

Explanation: The repository I/O module has returned the error code specified by RPERRRET. RPERRCD will vary based on the message content. Currently, the values of RPERRRET and the message can be:

• 04 - MISSING DDNAME/DD CARD
• 08 - RECORD NOT FOUND - UNABLE TO PROCESS
• 12 - INVALID REPOSITORY DATA SET
• 16 - INVALID RPIO PARMLIST - NO VALID REQUEST SPECIFIED
• 20 - I/O ERROR, RPERRCD = RPLRTNCD+RPLERRCD
• 24 - OPEN ERROR, RPERRCD CONTAINS ACB ERROR FLAG
• 28 - REPOSITORY ENQUEUE FAILED
• 32 - LOGIC ERROR BUILDING MULTI-PART REC
• 36 - LOGIC ERROR, UPDATE FOUND DUPLICATE TIMESTAMP
• 40 - LOGIC ERROR, SEGMENT NOT FOUND WHILE UPDATING
• 48 - LOGIC ERROR - UPDATING, REC LVL BAD
• 52 - REPOSITORY DOWNLEVEL RELEASE

User Response: For RPERRRET = 04 through 12, correct the error and retry. Ensure that the repository file was created and initialized correctly and that it was properly allocated through the Code Debug setup panels or in the JCL (if a Batch test). For codes 16 through 52, Contact BMC Support.

XPD4042

ERROR CODE <ERRCODE> ACCESSING REPOSITORY FOR DEBUG=<TYPE>

Module: ADSRA433

Explanation: The CCHILITE command attempted to retrieve a repository record with the DEBUG type indicated. However, no record matched the specified retrieval criteria.

User Response: If RPERRCD is not = 8 (8 = Not found), Contact BMC Support.

XPD4043

REPOSITORY REC FOR <CSECT> DEBUG=<OPTION> RETRIEVED FOR HIGHLIGHTING

Module: ADSRA433

Explanation: The CCHILITE command succeeded in retrieving a repository record with the DEBUG type indicated.

XPD4050

LOAD MODULE NOT FOUND FOR SOURCE NAME

Module: ADSRA405

Explanation: This message is no longer valid.

User Response: None.

XPD4120

INVALID COMMAND

Module: ADSRA412

Explanation: The command specified is not a valid Code Debug command.

User Response: Check your spelling of the specified command. See to the Code Debug TSO and IMS Reference Manual.

XPD4121

EXTRANEOUS KEYWORD

Module: ADSRA412

Explanation: When parsing the command issued, an extraneous keyword was found.

User Response: Check command syntax and try again.

XPD4122

RETEST INVALID IN THIS ENVIRONMENT

Module: ADSRA412

Explanation: The RETEST command is not valid in a Dialog box, Db2, or IMS message region environment.

XPD4123

RETEST INVALID IN THIS ENVIRONMENT

Module: ADSRA412

Explanation: The RETEST command is not valid in an IMS message region or an IMS BMP or Fast Path environment.

XPD4140

IDENTIFIER NAME NOT FOUND IN MODULE

Module: ADSRA538

Explanation: The data name specified in the DISPLAY command cannot be found in the current module.

XPD4142

COMMAND NOT PERMITTED FOR MODULE WITHOUT SOURCE

Module: ADSRA414

Explanation: The specified command is valid only when there is available source for the module.

User Response: None.

XPD4145

CTLDTOFF=N PREVENTS SET DATETIME OFF COMMAND DURING CODE COVERAGE (DEFAULT)

Module: ADSRA612

Explanation: The date/time off option (CTLDTOFF) as specified in the installation defaults is set to NO. This means that the SET DATETIME OFF command cannot be used.

User Response: To allow the SET DATETIME OFF command, change CTLDTOFF=NO to CTLDTOFF=YES in the CMSC PARMLIB. See to the section entitled “Run-Time Parameter Keywords” in the Code Debug TSO and IMS Advanced Configuration Guide.

XPD4146

CTLDEBUG=N PREVENTS LOGIC ALTERING ACTIONS DURING CODE COVERAGE

Module: ADSRA353, ADSRA612, and ADSRA688

Explanation: Certain Code Debug commands and/or actions can alter the logic flow of a program. For Code Coverage, if CTLDEBUG=NO in the CMSC PARMLIB, the following commands will be prevented:

• ACCEPT
• DROP
• DLI
• FADB2
• GETMAIN
• GOBACK (GO BACK)
• GOTO (GO TO)
• MOVE
• RETURN
• SKIP
• USE
• USING
• Overtyping Storage.

User Response: To allow logic altering commands, change CTLDEBUG=NO to CTLDEBUG=YES in the CMSC PARMLIB. See to the section entitled “Run-Time Parameter Keywords” in the Code Debug TSO and IMS Advanced Configuration Guide.

XPD4147

POTENTIAL LOGIC ALTERING ACTION, DEBUG BIT SET

Module: ADSRA353, ADSRA612, ADSRA688

Explanation: The natural logic flow of the program may have been altered by the use of an Code Debug TSO command or feature. The records that are written to the Code Coverage Repository for this test will reflect that.

XPD4148

****** CODE COVERAGE ******

Module: ADSRA353, ADSRA612, ADSRA688

Explanation: This line of text is designed as an attention-getter to alert the user to other, more complex error messages.

User Response: None.

XPD4149

ONE (OR MORE) OF THE GPREGS HAS BEEN ALTERED

Module: ADSRA353

Explanation: Since changes to the General Purpose Registers are not logged, this message informs the user when they have been changed during a Code Coverage test session.

User Response: None.

XPD4150

BASE LOCATOR NOT INITIALIZED

Module: ADSRA439 and ADSRA459

Explanation: There was a failure in constructing the element display block (EDB) for the specified data. Base locator cells were not initialized.

User Response: Contact your internal technical support.

XPD4151

NO IDENTIFIER NAME LOCATED

Module: ADSRA623

Explanation: No data information was found for the specified data name.

XPD4156

TGT ADDRESS FOR PROGRAM <MODULE> IS INVALID, ADDRESS = <ADDRESS>

Module: ADSRA246

Explanation: The SHOW DCB command failed because the COBOL TGT was invalid.

User Response: Contact your internal technical support.

XPD4170

CEE COBOL TRAP OPTION WAS FORCED TO OFF

Module: ADSRA221 and ADSRA417

Explanation: This is an Code Debug default.

XPD4171

NO SOURCE LISTING DATA SET MEMBER FOR X(8)

Module: ADSRA417

Explanation: The specified source listing cannot be found in the allocated DDIO data set.

User Response: Check to make sure that the correct DDIO is allocated. Recompile the program and try again.

XPD4172

X(3) APPLICATION MODULE NOT FOUND IN USER LIBRARY

Module: ADSRA417

Explanation: The application module being referenced could not be found in the user library.

User Response: If the application is in the user library, contact your internal technical support.

XPD4173

CSECT IS NOT A MAIN PROCEDURE

Module: ADSRA417

Explanation: In validating the test command parameter, the module found does not represent a main procedure.

User Response: Contact your internal technical support.

XPD4174 

NO DATE/TIME PRESENT FOR X(9) MODULE

Module: ADSRA417

Explanation: The module control block (MCB) of the specified module does not have date/time information.

User Response: Contact your internal technical support.

XPD4175

EXECUTION OF BEFORE COMMAND FAILED

Module: ADSRA417

Explanation: Execution of before command failed. If this is a Topaz/COPE/IMS test, you must have source for the initial program. 

User Response: Contact your internal technical support.

XPD4176

PL/I RUNTIME LIBRARIES MUST BE ALLOCATED IN XTASKLIB

Module: ADSRA221 and ADSRA417

Explanation: The PL/I run-time libraries must be specified on the Load Module Libraries screen (option 1 on the Setup Menu).

User Response: Verify that the libraries are present on the Load Module Libraries screen. If the libraries are listed and the message persists, contact your internal technical support.

XPD4177

PL/I SPIE AND STAE WERE RESET BY CODE DEBUG

Module: ADSRA221

XPD4178

PLIXOPT SPIE AND STAE RESET BY CODE DEBUG

Module: ADSRA221

XPD4180

REQUESTED SOURCE MODULE NOT AVAILABLE

Module: ADSRA418

Explanation: No SLS member in the DDIO data set matches the requested source module.

User Response: Contact your internal technical support.

XPD4181

DATA DEFINITION INVALID, NOT FOUND OR DUPLICATED

Module: ADSRA418

Explanation: No data table entry (DTE) can be found for the specified COBOL level 88 data name.

User Response: Contact your internal technical support.

XPD4182

DATA DEFINITION NOT FOUND FOR X(64)

Module: ADSRA418

Explanation: No data table entry (DTE) can be found for the specified data name.

User Response: Contact your internal technical support.

XPD4183

ERROR PROCESSING X(38)... MAY BE OPTIMIZED OUT

Module: ADSRA418

Explanation: An internal error occurred while Code Debug was processing a variable. This can be caused when a compiler optimizes out a variable, which usually occurs if a variable is declared, but not used.

User Response: If the variable was optimized out, any attempt to reference the variable cannot be successful. If the variable was not optimized out, contact your internal technical support.

XPD4184

A LABEL IS NOT A VALID VARIABLE NAME

Module: ADSRA418

Explanation: The label that is referenced is not valid.

XPD4185

DUPLICATE DATA NAME, QUALIFICATION IS REQUIRED

Module: ADSRA418

Explanation: The specified data name has a duplicate data name specified in the application program.

User Response: Qualify the desired data name. See to the User Guide or Reference Manual for qualification rules.

XPD4186

DATA NAME X(64) WAS NOT FOUND

Module: ADSRA418

Explanation: The specified data name is unknown to the application program.

User Response: Contact your internal technical support.

XPD4187

EXPRESSION ERROR (X,4,1,<Return Code>) - C,44,1,<Reason>

Module: ADSRA418

Explanation: CSS could not locate a variable in the C Language expression for the Return Code (in HEX) and Reason given.

User Response: Check for errors based on the Reason given. If the error is not apparent, Contact BMC Support with the Return Code and Reason.

XPD4190

PROCEDURE NAME NOT FOUND IN MODULE SOURCE LISTING

Module: ADSRA419

Explanation: The procedure name specified in the command is not found in the source module.

User Response: Contact your internal technical support.

XPD4191

NO SOURCE MODULE CONTROL BLOCK FOUND FOR PROCEDURE

Module: ADSRA419

Explanation: When trying to evaluate a paragraph or section name, they could not be found in the existing source module window block.

User Response: Verify that the correct DDIO file is allocated. Recompile the program and try again.

XPD4192

MODULE NOT FOUND

Module: ADSRA419

Explanation: The specified module cannot be found in the allocated user library.

XPD4193

LOAD OF MODULE C(8) FAILED

Module: ADSRA432, ADSRA433

Explanation: This message will usually be followed by a User 3398 ABEND. The module could not be found, processing is terminated.

User Response: Check your STEPLIB, JOBLIB, or LIBDEF/ISPLLIB concatenations for the proper Code Coverage libraries.

XPD4194 ADSRA432 "**** ******* ******* *******"
XPD4194 ADSRA432 " ---- WARNING ---- "
XPD4194 ADSRA432 " CODE COVERAGE RESULTS ARE BASED, IN PART, ON THE"
XPD4194 ADSRA432 " MAPPING OF PROGRAM SOURCE CODE TO THE COMPILER-GENERATED "
XPD4194 ADSRA432 " MACHINE INSTRUCTIONS EXECUTED. BECAUSE THE RESULTS FOR "
XPD4194 ADSRA432 " OPTIMIZED PROGRAMS CAN SEEM ILLOGICAL, XPEDITER/CODE "
XPD4194 ADSRA432 " COVERAGE MAY MAKE CERTAIN INFERENCES, INDICATED BY AN "
XPD4194 ADSRA432 " ASTERISK (*), IN AN ATTEMPT TO CLARIFY ACTUAL PROGRAM "
XPD4194 ADSRA432 " EXECUTION. "
XPD4194 ADSRA432 "******  ******* **** *******"

Module: ADSRA432

Explanation: There are certain limitations on testing programs compiled with the COBOL OPTIMIZE compiler option.

User Response: See to the Code Debug TSO and IMS COBOL User Guide for more information on these restrictions.