InterTest™ and SymDump ® 11.0
The CNTL=EDIT function is valid for option CMD only.
Action:
Correct the command and retry.
CAIN4606
(*) (*) indirect commands currently in use. Try later.
Reason:
The indirect commands defined for the program/terminal are currently either being edited or executed from another
terminal. They cannot be accessed concurrently.
Action:
Wait until they are available and retry.
CAIN4607
An error occurred processing indirect commands
Reason:
An error occurred while attempting to execute indirect commands or access program IN25ICMD. The reason for the error
follows in the succeeding message.
Action:
None.
CAIN4608
Program (*) is not available.
Reason:
The program specified cannot be found or loaded.
Action:
Ensure that the program is defined in the PPT and can be loaded.
CAIN4609
Storage chains damage detected.
Reason:
InterTest for CICS storage chains have been damaged.
Action:
Get an SVC dump and contact Broadcom Support .
CAIN4610
CWA does not exist.
Reason:
The unprotect CWA option was requested in a CICS region which does not have a CWA generated.
Action:
You are either on the wrong CICS region or you must restart your CICS region with a CWA specified.
CAIN4611
COBOL II runtime module (*) is not defined as ASSEMBLER.
Reason:
The COBOL II runtime modules IGZCPCC and IGZCPAC cannot be defined as other than ASSEMBLER. Therefore,
COBOL dynamic calls cannot be monitored.
 1672


InterTest™ and SymDump ® 11.0
Action:
Define IGZCPCC and IGZCPAC as ASSEMBLER or verify that AUTOINSTALL is not defining them as other than
ASSEMBLER.
CAIN4612
COBOL dynamic calls cannot be monitored.
Reason:
The COBOL II runtime modules IGZCPCC and IGZCPAC cannot be defined as other than ASSEMBLER. Therefore,
COBOL dynamic calls cannot be monitored.
Action:
Define IGZCPCC and IGZCPAC as ASSEMBLER or verify that AUTOINSTALL is not defining them as other than
ASSEMBLER.
CAIN4613
MON or NOM option can only be set on a program.
Reason:
The MON and NOM options cannot be set for a terminal or transaction monitoring entry.
Action:
Correct the request and retry.
CAIN4614
PROG=.ALL is already set for user (*).
Reason:
The PROG=.ALL can only be set by one user and it has already been set by the user specified.
Action:
None.
CAIN4615
PROG=.OPTIONS is already set for user (*).
Reason:
The PROG=.OPTIONS can only be set by one user and it has already been set by the user specified.
Action:
None.
CAIN4616
CICS LINK to (*) program failed.
Reason:
The requested program was not available.
Action:
Contact your systems programmer.
CAIN4617
EIBRESP=X'(*)', EIBRESP2=X'(*)'.
Reason:
This message is produced in conjunction with another message. This message shows the contents of the above fields.
Action:
 1673


InterTest™ and SymDump ® 11.0
Contact your systems programmer.
CAIN4618
CICSPlex resynchronization request failed.
Reason:
This message is produced in conjunction with one or more other messages which give information as to why the request
failed.
Action:
Contact your systems programmer.
CAIN4619
CNTL=OFF,ALL,... command syntax error
Reason:
CNTL=OFF,ALL syntax rules are:
1.TTR= and FTR=, or USR= are required. TTR and FTR terminal IDs must be equal. .ANY or .ALL not allowed
2.No other CNTL options are allowed on the command
Example:
CNTL=OFF,ALL,TTR=T001,FTR=T001
CNTL=OFF,ALL,USR=SMIJO01
Action:
Correct the command and resubmit.
CAIN4620
No breakpoints found for TTR/FTR=terminal or USR=userid
Reason:
CNTL=OFF,ALL,... command did not find any breakpoints for the TTR/FTR=terminal or USR=userid.
Action:
Ensure that you specified the correct terminal or user id.
CAIN4621
Program is not COBOL – (*) option disregarded.
Reason:
The indicated option is only valid for COBOL programs.
Action:
Select a valid option.
CAIN4622
Monitor logging *
Reason:
Monitor logging has been started, stopped, canceled, or deleted.
Action:
No action is required.
CAIN4623
Monitor logging error *
 1674


InterTest™ and SymDump ® 11.0
Reasons:
Write failed.
Session not found.
Stop failed.
Delete failed.
Start failed.
Cancel failed. No active session.
PROTMLOG file not available.
Action:
Correct the command entered and retry.
CAIN4701
Requested service NOT SUPPORTED Request Bytes = xxxxxx
Reason:
An INVALID request was made by one of the InterTest for CICS programs. This is an internal problem.
Action:
Follow these steps:
1.Try the request again
2.If you still have the problem, contact Broadcom Support  for assistance.

CAIN4702
UTILITY in Progress Request NOT PROCESSED
Reason:
The InterTest for CICS Symbolic File was found to be in use by batch UTILITY program.
Action:
Follow these steps:
1.Try request again
2.Run a batch utility REPORT function and then retry request

CAIN4703
invalid sequence number
Reason:
An internal error occurred while reading data from the InterTest for CICS Symbolic file.
Action:
Try recompiling the program and if the problem persists, call Broadcom Support .
CAIN4704
statement number is invalid
Reason:
The specified statement number could not be found on the InterTest for CICS Symbolic File for the requested program.
Action:
If the program is PL1, this statement may have been removed due
 1675


InterTest™ and SymDump ® 11.0
CAIN4705
Subscripts are not supported for this variable
Reason:
The PL1 variable was not defined as an array or the dimensions of the array could not be determined.
Action:
None.
CAIN4707
program NOT FOUND IN ANY SYMBOLIC FILE
Reason:
The program was not found on any symbolic file.
Action:
Specify a correct program name and retry the command.
CAIN4708
request NOT SUPPORTED for xxxxx
Reason:
A request has been made which is not supported for the language, indicated xxxxx.
Action:
None.
CAIN4709
program MUST be at a BREAKPOINT to service request
Reason:
To view a dataitem, the program must be sitting at an InterTest for CICS breakpoint.
Action:
None.
CAIN4710
NO STRUCTURE INFORMATION for request
Reason:
A STRUCTURE (PF12) request was made for a symbolic data item that was not contained in an Assembler DSECT or
was COBOL data item that did not have a valid level number. For example: a COBOL paragraph name or an Assembler
data item, which was defined within a CSECT.
Action:
None.
CAIN4711
STRUCTURE request is INVALID for a PL/I program
Reason:
A STRUCTURE (PF12) request was made for a symbolic data item which was defined in a PL/I program. At this time,
STRUCTURE requests are invalid for PL/I programs.
Action:
None.
 1676


InterTest™ and SymDump ® 11.0
CAIN4712
INCORRECT SYNTAX First assembler dataname IS NOT a Register
Reason:
The first argument for an ASSEMBLER data name was not found to be a register.
Action:
Correct the command and resubmit the request Syntax: 'register.dataname'
register
Specifies a symbolic reference for a register, like TIOABAR, or it may be specified as Rn, where n is the register number,
like R15 for register 15.
.
Specifies a required delimiter.
dataname
Specifies the name of the data area which you wish to see.
CAIN4713
xxxxx Not Found in Symbolic File have ASSUMED its Register
Reason:
A symbolic request was made for an Assembler data item, with the register value (first argument) of 'Rn'. The 'Rn' name
was NOT found in the Symbolic File, but an assumed value was used. For example: the value R15 was specified and not
found, so register 15 was used.
Action:
Correct command and resubmit request if the assumed value was incorrect.
CAIN4714
SUBSCRIPTS and INDEXES cannot be intermixed
Reason:
A symbolic request was made for a COBOL data item with the following syntax: 'dataitem(x1,.,xn)' and the values
specified for 'x1,.xn' were found to be a mixture of SUBSCRIPTS and INDEX names.
Action:
Change the command to specify all SUBSCRIPTS or INDEXES and resubmit the command.
CAIN4715
to many SUBSCRIPTS or INDEXES specified
Reason:
A symbolic request was made for a COBOL data item with the following syntax: 'dataitem(x1,.,xn)' and the number of


exceeded the number of OCCURS clauses that could be used.
Action:
Change the command to specify the correct number of SUBSCRIPTS or INDEXES and resubmit command.
CAIN4716
xxxxxxx not found in Symbolic File
Reason:
The data item, indicated by xxxxxxx, was not found in the InterTest for CICS Symbolic File.
Action:
Check for the following conditions:
 1677


InterTest™ and SymDump ® 11.0
•Correct spelling of dataname.
•The name in the crossreference (The dataname may not be referenced and you compiled with the XREF(SHORT)
option)
•Are you using the correct program?

CAIN4717
xxxxxxx is NEGATIVE
Reason:
The SUBSCRIPT or INDEX, specified by xxxxxxx, contained a NEGATIVE value.
Action:
Correct the value and resubmit the request.
CAIN4718
xxxxxxx is NOT NUMERIC
Reason:
The SUBSCRIPT or INDEX, specified by xxxxxxx, did not contain a NUMERIC value.
Action:
Correct the value and resubmit the request.
CAIN4719
xxxxxxx is NOT a NUMERIC DATA TYPE
Reason:
The SUBSCRIPT or INDEX, specified by xxxxxxx, was not defined with a NUMERIC PICTURE clause.
Action:
Change the command to specify a valid SUBSCRIPT/INDEX, or correct program.
CAIN4720
xxxxxxx CANNOT be used for QUALIFICATION
Reason:
A symbolic request was made for a COBOL data item with the following syntax: 'dataitem2 OF dataitem1' and the value
specified for 'dataitem1' was incorrectly specified. This could occur if its level number was greater than or equal to
'dataitem2' or it was an INDEX name.
Action:
Correct the command and resubmit request.
CAIN4721
Multiple OFFSETS found because of COBOL II OPTIMIZER Option
Reason:
A symbolic request for a COBOL II paragraph name or statement number resulted in more than one offset being found.
This occurs because of the use of the COBOL II Optimize feature.
Action:
None.
 1678


InterTest™ and SymDump ® 11.0
CAIN4722
xxxxxxx NOT Found or BLOCK NOT Active
Reason:
A PL1 label (xxxxxxxx) could not be found or the Procedure name block the label is defined in is not active.
Action:
Retry when the PL1 Block is active .
CAIN4723
xxxxxxx NOT Allocated
Reason:
Storage for the COBOL dataname (xxxxxxxx) has not been allocated
Action:
Retry after the dataname has been allocated .
CAIN4724
(*) PROC/BLOCK NOT Active
Reason:
The PROC/BLOCK specified is not active.
Action:
Specify an active PROC/BLOCK.
CAIN4725
Statement number past the end of the program
Reason:
Specified program statement number is greater than the highest statement number in the program.
Action:
Ensure that the statement number you specified is defined in the program
CAIN4726
(*) BASE pointer not supplied
Reason:
The printer was not set up for a BASED variable.
Action:
Supply a BASE pointer.
CAIN4727
Data Item is an INDEX set to occurrence (*)
Reason:
The item selected is an INDEX set to (*).
Action:
None.
CAIN4728
NO Data Names Index found
Reason:
 1679


InterTest™ and SymDump ® 11.0
No data names index was found.
Action:
Check your compiler options.
CAIN4729
SYMBOLIC DATA was created with an older release
Reason:
The symbolic data found for the program specified was postprocessed by an older release of InterTest for CICS.
Action:
Recompile the program and use the postprocessor from the current release.
CAIN4730
(*) NOT FOUND in requested area
Reason:
The data (*) was not found in the area that you specified.
Action:
Change the area that you are searching or change what you are searching for.
CAIN4731
Data Item is an INDEX - occurrence could not be calculated
Reason:
The data item specified is indexed and InterTest for CICS is unable to calculate the number of times the data item occurs.
Action:
Specify a non-indexed data item.
CAIN4732
No Source Listing saved for program
Reason:
There is no source listing saved to the Symbolic File for this program.
Action:
Check your compile options.
CAIN4733
CrossReference not saved
Reason:
There is no crossreference section saved to the Symbolic File for this program.
Action:
Use LISTER=MAP or LISTER=ALL in your InterTest for CICS post compile processor parameters.
CAIN4734
(*) not referenced
Reason:
The field indicated (*) was defined, but not referenced in the program.
Action:
None.
 1680


InterTest™ and SymDump ® 11.0
CAIN4735
No LinkageEditor data saved for program
Reason:
There is no linkageeditor map saved to the Symbolic File for this program.
Action:
InterTest for CICS was unable to save the linkageeditor map. Check the linkageeditor step for errors.
CAIN4736
88LEVEL items are not supported.
Reason:
The data item is defined as an '88' level, and it cannot be referenced by InterTest for CICS.
Action:
Do not reference data items defined as 88 level.
CAIN4737
Qualified Names are only for Based Variables
Reason:
You attempted to specify a qualified name for a nonBASED variable.
Action:
Specify qualified names only for BASED variables.
CAIN4738
No Paragraph names were found
Reason:
There were no paragraph names found for this program.
Action:
None.
CAIN4739
No Labels were found
Reason:
There were no labels found in this program.
Action:
None.
CAIN4740
request NOT SUPPORTED for an INDEX
Reason:
The request you made is not a valid request for an index.
Action:
Specify a valid index request.
CAIN4741
NOTAUTH CONDITION RESOURCE LEVEL SECURITY FAILED FOR "(*)"
Reason:
 1681


InterTest™ and SymDump ® 11.0
You are not authorized to perform the requested task. Resource level security checking is in effect.
Action:
Contact the Security Administrator.
CAIN4742
No procedure names were found
Reason:
No procedure names were found to match the specified criteria.
Action:
Check the selection criteria and try again.
CAIN4743
PROTSYM record not found file corrupted
Reason:
The PROTSYM file is corrupted so the requested record could not be found.
Action:
Contact your systems programmer for assistance.
CAIN4744
Syntax error in command
Reason:
There was a syntax error in the command.
Action:
Correct the command syntax and try again.
CAIN4745
Too many indexes specified
Reason:
More indexes were specified than are allowed. COBOL and PL/I support 7 and 15 levels of subscripting, respectively.
Action:
Correct the request and resubmit.
CAIN4746
Program language is not supported
Reason:
The language used in the specified program is not supported.
Action:
None.
CAIN4747
Too many qualifications (max = 15)
Reason:
More than 15 qualifications were requested.
Action:
Correct the request and try again.
 1682


InterTest™ and SymDump ® 11.0
CAIN4748
Indexed qualified names are not supported
Reason:
A request was made for indexed qualified names but this is not supported.
Action:
None.
CAIN4749
(*) contains too many numeric digits
Reason:
The field specified contains too many numeric digits.
Action:
Correct the request and resubmit.
CAIN4750
(*) datatype not supported for subscript
Reason:
The specified datatype is not supported for subscripting.
Action:
None.
CAIN4751
Reference Modification fields are out of range
Reason:
The values entered for the starting point and/or length reference a location that is greater than the dataname's length.
Action:
Correct the erroneous fields and reenter the request.
CAIN4752
Reference Modification field not positive number
Reason:
Either the starting position or the length field is not a positive number.
Action:
Correct the field and reenter the request.
CAIN4753
Array usage requires latest postprocessor output
Reason:
Your PL1 program needs to be recompiled and post processed with the latest PL1 PostProcessor module IN25SYMP.
This new version has enhanced support for displaying PL1 arrays.
Action:
Recompile your program using the newest PL1 postprocessor.
CAIN4901
InterTest RELEASE (*) NOT COMPATIBLE WITH CICS RELEASE (*)
 1683


InterTest™ and SymDump ® 11.0
Reason:
The release of InterTest for CICS is not compatible with the release of CICS.
Action:
Install a compatible version of InterTest for CICS, or contact Broadcom Support .
CAIN4902
END OF TRANSACTION
Reason:
The transaction has ended.
Action:
None.
CAIN4903
INCORRECT VERSION OF IN25OPTS SHOWN VALUES MAY BE INCORRECT
Reason:
InterTest for CICS has determined that an incorrect version of IN25OPTS is being used, and the values may be incorrect.
Action:
Regenerate IN25OPTS.
CAIN4904
NO IN25OPTS TABLE FOUND DEFAULTS ARE DISPLAYED
Reason:
IN25OPTS module was not found, and the defaults are displayed.
Action:
Generate an IN25OPTS module.
CAIN4905
Invalid option or command entered.
Reason:
An invalid option or command was entered.
Action:
Correct the request and retry.
CAIN4906
Current GENLEVEL is 970
Reason:
This message informs you of your site's current GENLEVEL of InterTest for CICS.
Action:
None.
CAIN4624
Incorrect path set for headless debugging *
Reasons:
USS path not found, has incorrect syntax, or is more than 243 characters long.
 1684


InterTest™ and SymDump ® 11.0
Action:
•Correct the USS path entered in IN25OPTS options.
•Assemble and refresh IN25OPTS options.
CAIN4625
Error loading API for headless debugging *
Reason:
CAVHFMIO API load failed.
Action:
Contact Broadcom Support .
CAIN4626
Breakpoints are not allowed on statements that contain ENTRY verbs
Reason:
Statement contains an ENTRY verb.
Action:
Put the breakpoint on the next statement.
CAIN5101
LANG= value doesn't match install options
Reason:
InterTest for CICS has determined that the LANG= value does not match the installed options.
Action:
Check the LANG= parameter, and select an installed option.
CAIN5102
Terminal ID specified is invalid or not installed
Reason:
The terminal specified was not found or has not been installed.
Action:
Specify a valid terminal or install the terminal you want to use.
CAIN5103
CA InterTest profile update failed
Reason:
Your request to update the InterTest for CICS profile failed.
Action:
Check your request for errors. If you find None, contact Broadcom Support .
CAIN5104
Load on IN25OPTS failed
 1685


InterTest™ and SymDump ® 11.0
Reason:
Module IN25OPTS was not loaded due to an error.
Action:
Check the assembly and CHEDT of IN25OPTS, and try to load the module again.
CAIN5105
Invalid keyword in command
Reason:
You have specified an invalid keyword in your command.
Action:
Check your spelling. Specify a valid command.
CAIN5198
CA InterTest profile updated with default options
Reason:
The InterTest for CICS profile has been updated with the default options.
Action:
None.
CAIN5199
CA InterTest profile updated
Reason:
The InterTest for CICS profile has been updated.
Action:
None.
CAIN5301
VIRC: TERMINAL STORAGE GETMAIN FAILURE=
Reason:
A Terminal Storage getmain request failed in transaction VIRC.
Action:
Ensure that your CICS region has enough DSA storage available. If it does, contact Broadcom Support .
CAIN5302
VIRC: CRTE TRANSACTION NOT FOUND IN TOR
Reason:
The CICS 'CRTE' transaction is not defined in the TOR
Action:
Ensure that the TOR has the CRTE transaction id defined.
CAIN5303
VIRC: TRANSACTION STARTED WITH NO DATA
Reason:
The InterTest for CICS VIRC transaction was started improperly.
Action:
 1686


InterTest™ and SymDump ® 11.0
Ensure that InterTest for CICS was installed properly for MRO usage, and that there are no nonInterTest programs in your
CICS region that issue a START for program IN25VIRC.
CAIN5304
VIRC: A REMOTE VTAT TRAN NOT DEFINED IN TOR=XXXX FOR AOR=XXXX
Reason:
The required InterTest for CICS transactions were incorrectly defined for MRO operation.
Action:
One VTAT transaction must be defined as local in each AOR. A remote VTAT transaction must be defined in the TOR for
each AOR One VIRC transaction must be defined as local in the TOR and AORs.
Example:
TOR AOR1 AOR2
VTA1 >VTAT
VTA2 >VTAT
VIRC VIRC VIRC
CAIN8000
The latest Symbolic file version does not match the current load module
Reason:
You have multiple symbolic versions of the program and the datetime of the load module does not match the most
recently compiled symbolic version. If an older version of the program matches the load, it is indicated as DATE/TIME
MATCH in the Symbolic File Selection Screen Comment field.
Action:
If the load module is the correct version (you did not forget to do a NEW COPY after recompiling, then select the symbolic
file which matches the load. If you forgot to do a NEW COPY after recompiling then Clear the screen, new copy the
program, and retry the request
CAIN8001
WARNING ssssssss Symbolic yyddd/hh:mm mismatches load yyddd/hh:mm
Reason:
The active load module is out of sync with the preselected symbolic file, or does not match any symbolic file members.
Possible causes of this message are:
•


Possible causes of this message are:
•
•A symbolic file was previously selected and it does not match the active load module.
•
•The program was recompiled after a symbolic file was preselected, and a CNTL=NEW was not executed.
•
•One or more of your symbolic files is defined incorrectly or not available. The VRPT transaction (Option 03) can be
used to display your symbolic files and their statuses.
•
Action:
Press Enter and continue with breakpoint using the program from the ssssssss symbolic file. Once at the breakpoint
screen you can continue monitoring, or abend the task, correct the mismatch problem, and reexecuted the program.
CAIN8002
WARNING Symbolic file date/time not equal to module date/time.
 1687


InterTest™ and SymDump ® 11.0
Reason:
You have one symbolic version of a COBOL or PL/I program and it does not match the current load module datetime. The
possible causes of this message are as follows:
•
•You don't have the proper symbolic files and load libraries defined.
•
•Your PL/I program may have been postcompiled with a InterTest for CICS release earlier than 4.4 or 5.3.
•
•Your PL/I compiler was installed with the TSTAMP=NO option.
•
•You recompiled your program and did not do a CEMT NEW copy or CNTL=NEW.
•
Action:
Press Clear to cancel the LIST or process the CNTL command with no symbolics, or select a symbolic to use. In either
case, you have an outofsync problem that you should correct.
CAIN8003
Invalid character entered
Reason:
A character other than S was specified next to a symbolic file.
Action:
Try selecting a symbolic file by specifying S.
CAIN8004
No selection made.
Reason:
You pressed ENTER without selecting a symbolic file.
Action:
Either select a symbolic file, or press Clear to cancel the LIST request or process the CNTL request with no symbolics.
CAIN8005
Only one "S" may be entered
Reason:
You tried to select more than one symbolic file.
Action:
Either select a single symbolic file, or press Clear to cancel the LIST request or process the CNTL request with no
symbolics.
CAIN8006
Matching Symbolic must be used. Symbolic display will be switched*
Reason:
You tried to set monitoring for a non matching symbolic file and there is a matching load/protsym combination available.


InterTest for CICS is going to switch the display to the matching symbolic for you.
Action:
Review and respecify your monitoring request using the proper symbolic file that matches the load module.
 1688


InterTest™ and SymDump ® 11.0
CAIN8981
Line commands D, H, and R are valid for file PROTDMP only
Reason:
An attempt was made to Delete, Hold, or Release a dump not belonging to this region.
Action:
You can only Delete, Hold, or Release dumps belonging to the current region's Dump file.
CAIN8982
Internal trace was empty at dump capture, trace unavailable
Reason:
There was no information to gather for the trace, so no trace was taken. The CICS Systems Initialization Table (SIT)
specifies no internal tracing is to be performed in the region.
Action:
Contact your systems programmer.
CAIN8983
CA InterTest is not started
Reason:
InterTest for CICS has not been started.
CAIN8007
PROTSYM version mismatch. DWARF data available.
Reason:  There is no PROTSYM file for this load module, or you have multiple symbolic versions of the program and
the date/time of the load module does not match the most recently compiled symbolic version. If an older version of the
program matches the load, it will be indicated as DATE/TIME MATCH in the Symbolic File Selection Screen Comment
field. However, DWARF data is available which is always a match.
Action:  Either use DWARF, or if the load module is the correct version, then select the symbolic file which matches the
load. If there is no matching symbolic file available, CLEAR the screen, create a NEW COPY of the program, and retry the
request.
InterTest Batch Messages and Abend Codes
InterTestBatch Messages and Abend Codes
ABA00
PROGRAM CHECK INTERRUPTION WHILE PROCESSING I/O REQUEST
ABA03
WHEN TASK ATTEMPTED TO TERMINATE, ONE OR MORE SUBTASKS NOT TERMINED
ABA05


ABA05
AREA TO BE FREED BY FREEMAIN MACRO OVERLAPPED
Reason:  Free area in virtual storage or part of the area was still fixed in real storage.
 1689


InterTest™ and SymDump ® 11.0
ABA06
PRIOR REQUEST FOR QUEUED MODULE NOW REQUESTED BY LINK, LOAD, ATT OR XCTL MACRO
ABA0A
R-TYPE FREEMAIN MACRO SPECIFIED AREA THAT OVERLAPPED
Reason:  Free area in virtual storage or part of area was still fixed in real storage.
ABA13
DATA SET REQUESTED BY OPEN MACRO NOT FOUND (TAPE ONLY)
ABA14
CLOSE MACRO ENCOUNTERED I/O ERROR WHILE ATTEMPTING PARTIAL RELEASE OF SPACE IN DASD
CAMRA011
NO MEMBERS IN LIBRARY
Reason:  The library specified contains no members.
CAMRA012
NO MATCHES
Reason:  The pattern specified produced no matches.
CAMRA013
CAN'T OPEN LIBRARY
Reason:  An error occurred when opening specified library.
CAMRA014
FREED
Reason:  All possible ddnames were freed.
CAMRA028
MEMBER IS EMPTY
Reason:  The member does not contain any JCL.
CAMRA029
NOT AN EXEC STATEMENT
Reason:  Selected statement is not a valid JCL statement.
CAMRA033
CANNOT LOAD JCLCHECK
Reason:  Load module JCLCHECK cannot be found or loaded.
 1690


InterTest™ and SymDump ® 11.0
CAMRA034
NO PROCLIB
Reason:  You must supply at least one PROCLIB
CAMRA035
INVALID DSN
Reason:  The data set name is not valid.
CAMRA036
DDNAME NOT ALLOCATED
Reason:  The ddname specified was not pre-allocated as required.
CAMRA037
SELECTION NOT ALLOWED
Reason:  Member selection list is not allowed; member name is required.
CAMRA038
SOME ALLOCATIONS FAILED
Reason:  Review for highlighted allocations errors.
CAMRA090
DDNAME REQUIRED
Reason:  Data set cannot be allocated without ddname.
CAMRA092
BROWSE/EDIT ERROR
Reason:  ISPF is unable to browse or edit selected data set.
CAMRA093
INVALID LINE COMMAND
Reason:  Enter ALLOCATE, BROWSE, CONVERT (CLIST), EDIT, or FREE.
CAMRA094
INVALID LIBRARY TYPE
Reason:  Only PDS, Librarian , and Panvalet  are supported.
CAMRA095
NOTHING TO ALLOCATE/FREE
Reason:  The member contains only messages or empty lines.
 1691


InterTest™ and SymDump ® 11.0
CAMRA097
NO ALLOS TO ALLOCATE
Reason:  ALIB member is empty or contains only message allos.
CAMRA098
INTERNAL ERROR - PLIST
Reason:  Invalid PLIST supplied.
CAMRA099
CANNOT LOAD FAIR/OPEN ERROR
Reason:  Cannot load Librarian  FAIR modules or OPEN failed.
CAMRA101
INVALID LINE CMD
Reason:  Enter BROWSE, EDIT/SELECT, ALLOC, FREE, or CONVERT.
CAMRA102
MEMBER NAME REQUIRED
Reason:  Enter a member name in the provided field.
CAMRA103
MEMBER REPLACED
Reason:  Member was replaced in data set.
CAMRA104
INVALID LINE CMD
Reason:  Enter F to free, B to browse, or E to edit.
CAMRA105
INVALID LINE CMD
Reason:  Enter B to browse or S to select for JCL conversion.
CAMRA107
INVALID LINE CMD
Reason:  Enter I, D, R, S, AL, or F line command.
CAMRA301
OPEN ERROR
Reason:  OPEN failed for ALIB library.
 1692


InterTest™ and SymDump ® 11.0
CAMRA302
MEMBER NOT FOUND
Reason:  Requested member was not found in library.
CAMRA303
FIND ERROR
Reason:  FIND caused an error other than not found.
CAMRA304
INVALID RECORDS
Reason:  Invalid ALLO records found in member.
CAMRA305
EMPTY MEMBER
Reason:  Member requested contains no records.
CAMRA306
NEW MEMBER
Reason:  Member not found in library; new member created.
CAMR900E
Initialization error - CA LMP not installed.
Reason:
The license management component of Common Components and Services  was not installed properly.
Action:
Contact Broadcom Support .
CAMR901E
CAVHCONF module not found in the CSA.
Reason:
The CAVHCONF configuration module was not found in the CSA.
Action:
Check with your system programmer to ensure that the CAVHINIT process was run.
CAMR902W
CA InterTest not available on this system as set in CAVHCONF.
Reason:
The CAVHCONF configuration module, which is loaded into the CSA, indicates that the product is not intended to be used
on this system.
 1693


InterTest™ and SymDump ® 11.0
Action:
Check with your system programmer to ensure that the CAVHCONF configuration macro was implemented correctly on
this system and that the CAVHINIT process was run.

CAMR910E
SYM RECORD WITHOUT SYMBOLIC OPERAND
CAMR911E
SYM REPLACEMENT RECORD NOT FOUND
CAMR912E
"PGM=" NOT FOUND IN PROGRAM RECORD
CAMR914E
IBM DB2 "SYSTSIN" DD NOT FOUND
CAMR915E
IBM DB2 "LIB" STATEMENT ERROR
CAMR916E
IBM DB2 "LIB" STMT INVALID DSNAME
CAMR917E
IBM DB2 "PROGRAM" STATEMENT ERROR
CAMR950I
SVC INTERCEPT INSTALLED SUCCESSFULLY
CAMR951E
SVC NUMBER WAS NOT SPECIFIED
Reason:
An SVC number is required when the CAVHINIT initialization program executes on an LPAR that has InterTest Batch
enabled.
Action:
Specify a three-digit SVC number from 200 to 255 in your CAVHINIT parameters.
 1694


InterTest™ and SymDump ® 11.0
CAMR952E
INVALID ARGUMENT LENGTH
CAMR954E
VALUE OUT OF RANGE (MUST BE 200-255)
CAMR955E
UNABLE TO LOAD SVC INTERCEPT MODULE
CAMR956E
UNABLE TO LOAD SVC INTERCEPT PROLOGUE
CAMR957E
UNABLE TO INSTALL SVC INTERCEPT
CAMR960E
SYSTEM NOT INITIALIZED FOR BATCH LINK, REPLY "RETRY" OR "CANCEL"
CAMR961E
INT1OPTS DD MISSING OR INVALID
Reason:  The INT1OPTS DD statement was not included in the JCL for a Batch Link step, or the file referenced by the DD
statement is the wrong format for Batch Link options. Correct the JCL and resubmit the job.
CAMR962E
EXEC= OPTION MISSING OR INVALID
Reason:  The INT1OPTS DD statement did not contain any EXEC= option, or the name specified was invalid. Correct the
JCL and resubmit the job.
CAMR963E
EXEC=CAMRBL01 IS NOT VALID IN INT1OPTS
Reason:  EXEC=CAMRBL01 in INT1OPTS is not valid when you submit batch jobs for Batch Link.
CAMRS01W
BLSCHTBL NOT ANCHORED.
Reason:  Batch Link Schedule table not created and anchored off the CAAT. Review the initialization job log to determine
cause. Rerun the initialization after correcting the cause.
CAMRS02E
INT1SKUT DD NOT FOUND.
 1695


InterTest™ and SymDump ® 11.0
Reason:  The DD statement with INT1SKUT name was not found in the job stream. Correct error and rerun the
appropriate job.
CAMRS03E
CANNOT DETERMINE DSORG. EXPORT ABORTED.
Reason:  Export operation has aborted because the DSORG of the dataset pointed to by INT1SKUT DD statement is
unknown. DSORG must be either PS or PO.
CAMRS04E
INVALID MEMBER NAME SPECIFIED FOR SEQUENTIAL DATASET. EXPORT ABORTED.
Reason:  Export operation has aborted because a member name was specified for a sequential dataset. Correct the error
and rerun Export.
CAMRS05E
PDS WITH NO MEMBER NAME SPECIFIED.
Reason:  Schedule found a partitioned dataset but there was no member name specified. Correct the error and rerun the
job.
CAMRS06I
SCHEDULE EXPORTED TO ==> xxxxx
Reason:  Schedule is being exported to an external dataset named xxxxx.
CAMRS07I
TOTAL RECORDS EXPORTED TO INT1SKUT DD: nnnn
Reason:  During a Schedule Export operation, nnnn records were exported to the INT1SKUT DD.
CAMRS08I
BLSCHTBL IS EMPTY.
Reason:  Batch Link Schedule Table was found anchoring off CAAT, however it does not contain any active schedules.
CAMRS09E
DSORG NOT SUPPORTED, EXPORT ABORTED.
Reason:  Schedule Export operation has aborted due to the DSORG of the dataset pointed to by INT1SKUT DD
statement is of a type not supported. DSORG must be either PS or PO.
CAMRS10I
INT1SKUT DD OPENED.
Reason:  Informational message.
CAMRS011I


Reason:  Informational message.
CAMRS011I
INT1SKUT DD OPEN FAILED.
Reason:  The dataset pointed to by the INT1SKUT DD statement cannot be opened. Determine cause and rerun the job.
 1696


InterTest™ and SymDump ® 11.0
CAMRAS12I
RECORD SKIPPED. INVALID DB TYPE
Reason:  Schedule IMPORT operation found an import record with an invalid TYPE. The record is not imported.
CAMAS13I
IMPORT DSN ==> xxxxx
Reason:  xxxxx is the fully qualified dataset containing the Schedule to be imported.
CAMRS14W
SCHEDULE IMPORT NON ZERO RC = nn
Reason:  Import operations received a non zero return code of nn. Possible RC from Import:
0 = Import successful
4 = BLSCHTBL either is not anchored or does not exist
8 = INT1SKUT DD statement is missing.
CAMRS15I
RECORDS READ FROM INT1SKUT DD: nnnnn
Reason:  During a Schedule Import operation, nnnn records were imported
CAMRS16I
BATCH LINK SCHEDULE IMPORTED
Reason:  Informational Message.
CAMRS17I
SCHEDULE WILL BE IMPORTED TO REFRESH BLSCHTBL
Reason:  The default refresh option will be used to import the Schedule.
CAMRS18I
SCHEDULE WILL BE ADDED TO BLSCHTBL.
Reason:  ADD option specified by the Execution PARM is used to add from external dataset to the current active
schedules in CSA.
CAMRS19E
INT1SKUT DD OPEN FAILED.
Reason:  Open of dataset pointed to by INT1SKUT DD card failed.
CAMRS20E
INT1SKUT DD CARD NOT FOUND.
Reason:  INT1SKUT DD card is missing from the execution JCL. Make sure the DD Name is correctly spelled.
 1697


InterTest™ and SymDump ® 11.0
CAMRS20E0
BATCH LINK SCHEDULE NOT IMPORTED.
Reason:  For reasons stated in previous messages, the Batch Link Schedule was not imported.
CAMRS21I
INT1SKUT CLOSED.
Reason:  Informational message.
CAMRS22W
BLSCHTBL NOT ANCHORED.
Reason:  The Batch Link Schedule table is not anchored off CAAT. Review the initialization job log to determine cause.
Correct error and rerun export operation.
CAMRS23I
SP241 ACQUIRED AT ADDR ==> xxxxxxxx
Reason:  Information. Subpool 241 at address xxxxxxxx was acquired for Batch Link Schedule in-core table.
CAMRS24E
#CAAT ADD CA ANCHOR FAILED. RC=nn
Reason:  The #CAAT facility to add Batch Link Schedule table failed. Return code is nn. Make sure the initialization
program, CAVHINIT, is executing out of an APF authorized library.
CAMRS25W
SP241 GETMAIN FAILED.
Reason:  GETMAIN for Subpool 241 storage failed. This could be caused by excessive number of entries defined as
SCHTBSIZE in CAVHCONF. Each entry requires 27 bytes. Another likely cause - your CSA is over utilized. Discuss this
issue with your Systems Programmer.
CAMRS26I
ACQUIRED SP241
Reason:  Informational message.
CAMRS27I
CA ANCHORED ADDED.
Reason:  Informational. The Batch Link Schedule table was successfully anchored by the initialization routine.
CAMRS28W
CAMBSTBZ LOAD FAILED. SCHEDULING DISABLED.
Reason:  LOAD of CAMBSTBZ table failed, Batch Link Scheduling facility has been disabled. Make sure the load library


containing CAMRBSTBZ is in the STEPLIB concatenation stream. Rerun the initialization routine.
 1698


InterTest™ and SymDump ® 11.0
CAMRS29I
MAXIMUM SCHEDULE ENTRIES DEFINED: nnn
Reason:  Your installation has defined nnn as the maximum number of schedule entries that can be defined in the
schedule table.
CAMRS29W
0 ENTRIES DEFINED. SCHEDULING DISABLED.
Reason:  Informational. The SCHTBSIZE option in CAVHCONF defined 0 entries for Batch Link Schedule table, resulting
in the Schedule facility being disabled. To enable the Schedule facility, change the value of the SCHTBSIZE option. See
Installing for instructions on modifying this table. Rerun InterTest Batch initialization routine.
CAMRS30I
NUMBER OF SCHEDULE ENTRIES IMPORTED: nnn
Reason:  The total number of entries successfully imported is nnn entries.
CAMRS31W
INSUFFICIENT SCHEDULE TABLE SIZE. nn SCHEDULE ENTRIES NOT IMPORTED.
Reason:  There were nn entries from the INT1SKUT data set not imported due to the size restriction of the Batch Link
Scheduling Table (option SCHTBSIZE in CAVHCONF). A return code of 12 was also raised. To review the entries that
were imported, select Option 1 from the InterTest Batch DB2 and IMS Schedule Menu.
CAMRS32W
BLSCHTBL IS FULL. CANNOT ADD ANY MORE.
Reason:  The In Core Schedule Table is full. Additional schedule entries cannot be added. A return code of 4 indicated
some of the entries from the INT1SKUT data set were added. A return code of 8 indicated that none of the entries from
the INT1SKUT were added. You can display the contents of the schedule table by selecting Option 1 from the InterTest
Batch DB2 and IMS Schedule Menu.
CAMRS33E


Batch DB2 and IMS Schedule Menu.
CAMRS33E
SLOT NUMBER REQUESTED > MAXIMUM SIZE.
Reason:  Internal schedule component error. Contact Broadcom  for assistance.
CAMRS34E
BLSCHTBL SLOT NUMBER ERROR. FOUND=> nnnn.  IN SLOT NUMBER => nnnn.
Reason:  Internal schedule component error. Contact Broadcom  for assistance.
INTA006
DATA SET NOT CATALOGED
Reason:  The data set requested on the panel is not a cataloged data set. Check the name of your fully qualified data set
and retry.
 1699


InterTest™ and SymDump ® 11.0
INTA007
DATA SET IS AN ALIAS
INTA008
CATALOG DOES NOT EXIST
INTA009
SYNTAX ERROR IN DSNAME
INTA010
INVALID DATA SET NAME
Reason:  The data set name entered has invalid syntax.
INTA020
CA PANVALET LIB INVALID
Reason:  Only OS libraries can be specified for output.
INTA021
ENTER REQUIRED FIELD
Reason:  Enter required field at the cursor.
INTA110
INVALID DATA SET NAME
Reason:  The data set name entered has invalid syntax.
INTA120
NO DD STATS TRANSLATED
Reason:  The step selected contained no DD statements to translate.
INTA130
STEP NOT FOUND
Reason:  The input JCL either does not contain an exec card, or the step requested on the input specification panel
cannot be found in the member specified.
INTA210
INVALID DATA SET ORG
Reason:  The data set name entered has invalid syntax.
INTA211
INVALID RECORD FORMAT
 1700


InterTest™ and SymDump ® 11.0
Reason:  The record format is not fixed.
INTA212
INVALID RECORD LENGTH
Reason:  The record length must be 80.
INTA220
MISSING DDNAME
Reason:  Ddname must be specified at the cursor position.
INTA221
NO DSN, TERM, OR SYSOUT
Reason:  Enter a data set name, terminal, or SYSOUT at the cursor.
INTA222
INVALID DATA SET NAME
Reason:  Check data set name.
INTA223
INVALID DISPOSITION
Reason:  The DISP is incorrect. Valid DISP entries are SHR, OLD, and NEW.
INTA224
INVALID COMMAND
Reason:  An invalid command was entered on the command line.
INTA225
INVALID RECORD FORMAT
Reason:  Check record format.
INTA226
INVALID DSORG
Reason:  Use a DSORG of PS or PO.
INTA300
MSL BUILD ERROR PDS ERR
INTA301
MSL BUILD ERROR PAN ERR
Reason:  A Panvalet  read error or access error may have occurred.
 1701


InterTest™ and SymDump ® 11.0
INTA302
MEMBER NOT FOUND
Reason:  The member name requested on the panel cannot be found in the specified PDS.
INTA303
NOT A PDS OR PANLIB
Reason:  Input file is neither a PDS nor a PANLIB.
INTA304
MEMBER NOT FOUND/PRESENT
Reason:  Selected member was not found or not present during ALIB I/O.
INTA305
I/O ERROR ON DIRECTORY
Reason:  An I/O error occurred during the read of a PDS directory.
INTA306
INPUT FILE NOT PRE-ALLOC
Reason:  The input file was not pre-allocated or the allocation failed.
INTA307
INPUT FILE OPEN ERROR
Reason:  The input PDS you have entered is an ALIB, with a RECL=150. The input data set can be either a JCL PDS or a
CA PANVALET LIB.
INTA308
OUT FILE NOT PRE-ALLOC
Reason:  The output file was not pre-allocated or the allocation failed.
INTA309
OUTPUT FILE OPEN ERROR
Reason:  The output PDS you have entered as an ALIB is not defined correctly. An ALIB PDS must be defined as
RECL=150.
INTA310
INVALID ACCESS CODE
Reason:  Enter this member's correct access code.
INTA311
MEMBER NOT READ
Reason:  An internal error occurred when trying to read member.
 1702


InterTest™ and SymDump ® 11.0
INTA312
INVALID CONTROL CODE
Reason : Enter this library's correct control code.
INTA510
ALLOCATION FAILED
Reason:  The browse temporary data set could not be allocated.
INTA520
DCB OPEN FAILED
Reason:  The browse temporary data set could not be opened.
INTA610
CLIST ERROR HAS OCCURED
INTA620
CLIST WRITE ERROR
Reason:  An error occurred during CLIST file write.
INTA621
CLIST BUILD ERROR
Reason:  An error occurred during CLIST build.
INTAK210
DATA SET NOT AVAILABLE
Reason:  The DISP specified is requesting exclusive control and the data set may already be in use.
INTAK218
VOLUME IS NOT MOUNTED
Reason:  The volume specified in the JCL is not active. Modify the volume and retry allocation
INTAK219
UNIT NAME UNDEFINED
Reason:  The specified unit name is undefined in DSNAME allocation.
INTAK350
INVALID PARM IN TEXT
Reason:  There is an unacceptable parameter in the JCL. The JCL being used is not valid for execution in batch. Modify
the JCL and retry allocation.
 1703


InterTest™ and SymDump ® 11.0
INTAK360
INVALID KEY IN TEXT
Reason:  Invalid key specified in text unit (all SVC 99 functions).
INTAK364
DSNAME ALLOCATION ERROR
Reason:  JOBLIB, STEPLIB, JOBCAT, and STEPCAT are not valid ddnames for TSO.
INTAK368
UNAUTHORIZED USER
Reason:  An authorized function was requested by an unauthorized user.
INTAK369
INVALID PARAMETER LIST
Reason:  Invalid parameter list format (all SVC 99 functions).
INTAK410
DDNAME UNAVAILABLE
Reason:  One of the ddnames being allocated is already defined to your TSO session. Free the DD and try to allocate
again.
INTAK420
DDNAME IS OPEN
INTAK438
DDNAME NOT ALLOCATED
INTAK448
DATA SET ALREADY EXISTS
Reason:  Occurs when attempting to allocate a data set with a DISP=NEW and the data set already exists.
INTAL708
DATA SET NOT CATALOGED
Reason:  One of the data sets in your JCL is defined with a DISP=OLD or SHR and the data set is not cataloged.
INTAM100
INVALID OPTION
Reason:  Options 1, 2, 3, 4, and 5 are the only options available.
 1704


InterTest™ and SymDump ® 11.0
INTAM704
DUPLICATE DSN ON VOL
INTAM714
SPACE NOT AVAILABLE
Reason:  The JCL you are attempting to allocate contains a new data set, and the volume specified for that data set does
not have sufficient space to allocate it. Specify another volume.
INTAN708
CATALOG ERROR
Reason:  Structure inconsistent.
INTB000
FUNCTION FAILED
INTB001
CATALOG I/O ERROR
INTB002
CATALOG I/O ERROR
INTB003
INVALID MEMBER NAME
INTB004
INVALID DATA SET NAME
INTB005
VOLUME NOT AVAILABLE
INTB006
DAIR ERROR
Reason:  Error occurred using Dynamic Allocation Interface Request.
INTB007
DAIR CATALOG ERROR
INTB008
DAIR ALLOCATE ERROR
 1705


InterTest™ and SymDump ® 11.0
INTB009
DAIR FREE ERROR
Reason:  Dynamic Allocation Interface Request attempted to free a data set via ddname unsuccessfully.
INTB100
NOTHING TO ALLOCATE
Reason:  Allocate was requested but no ddnames existed to allocate.
INTB101
REQUEST BLOCK FAILURE
Reason:  GETMAIN failed to get storage for request block in SVC99.
INTB102
PAGE FAILED FOR TEXTUNIT
Reason:  GETMAIN failed to get a page for SVC99 text units and PTR
INTG001
INVALID LINE COMMAND
INTG002
NUMBER IS INVALID
Reason:  A number is not allowed with the "AL" line command
INTG003
MEMBER NOT FOUND
Reason:  Selected member was not found.
INTG005
INVALID PRIMARY COMMAND
Reason:  Enter UP, DOWN, END, RETURN, SELECT, or LOCATE.
INTG007
NO OPERATOR FOUND
Reason:  Operator for command not present or valid.
INTG008
MEMBER IS SAVED
Reason:  Intaenter has overwritten the input member and DSN
 1706


InterTest™ and SymDump ® 11.0
INTG009
MEMBER IS CREATED
Reason:  Intaenter has written to a new member or DSN.
INTG101
COMMAND NOT FOUND
Reason:  Command is either not found or miskeyed.
INTG102
MEM REPLACE NOT ALLOWED
Reason:  REPLACE NO was specified on out panel. Use Y.
XDAIR004
INVALID PARM LIST
Reason:  The parameter list passed to DAIR was invalid.
XDAIR008
CATALOG ERROR
Reason:  An error occurred in the catalog management routine.
XDAIR016
NO TIOT ENTRIES
Reason:  No TIOT entries are available for use.
XDAIR020
DSNAME UNAVAILABLE
Reason:  The data set requested is not available.
XDAIR024
DSNAME IS CONCATENATED
Reason:  DSNAME requested is a member of a concatenated group.
XDAIR028
DSNAME IS NOT ALLOCATED
Reason:  DSN is not allocated or its attribute list is not found.
XDAIR032
DSN PREVIOUSLY ALLOCATED
Reason:  DSN previously allocated permanently, DISP=NEW not allowed.
 1707


InterTest™ and SymDump ® 11.0
XDAIR036
ERROR OCCURRED IN CATLG
Reason:  An error occurred on a catalog information routine (IKJEHCIR)
XDAIR040
RETURN AREA EXHAUSTED
Reason:  The provided return area is exhausted and more index blocks exist.
XDAIR044
DELETE PREVIOUSLY USED
Reason:  You specified DELETE or a request of OLD, MOD, or SHR with no volume.
XDAIR048
RESERVED
XDAIR052
REQUEST DENIED
Reason:  Request has been denied by installation exit.
001
I/O error.
Attempt to read after AT END.
Reading a wrong length record.
002
I/O error.
003, 004, and 008
I/O error.
013
Something does not match up between the program and the DD statement. Check the system message (IEC141I)
for a more complete description of the error.
02x
Conflicting DCB for a direct file
030
Error in DCB for ISAM file.
 1708


InterTest™ and SymDump ® 11.0
031
I/O error on an ISAM file.
032
Error in DCB for ISAM file.
033
I/O error on an ISAM file.
034
Error in DCB for ISAM file.
035
Error in DCB for ISAM file.
036
No prime data area was specified for an ISAM file.
037
Invalid buffer length was specified.
038
The index area is too small.
039
END-OF-DATA problem with an ISAM file.
03A
I/O error on an ISAM file.
03B
Opening an ISAM file that is already open.
03C
Error in DCB for an ISAM file.
03D
Conflict in DCB for ISAM file - the DCB=DSORG=IS was omitted.
 1709


InterTest™ and SymDump ® 11.0
03E
I/O error during the load of an ISAM file.
0C1, 0C2, and 0C3
Invalid or missing DD statement.
Reading or writing an unopened file.
Runaway or uninitialized subscript or index.
Dropping out of end of program.
0C4 and 0C6
Invalid or missing DD statement.
Reading or writing an unopened file.
Runaway or uninitialized subscript or index.
Dropping out of end of program.
Opening or closing a file twice.
Coding equal BLKSIZE and LRECL for variable length records.
Omitting a parameter from a CALL list.
Using a divisor or multiplier that is too large.
Using the wrong SORTLIB in a COBOL sort.
0C7
Data item not initialized.
DISPLAY data moved to a numeric group item.
Improper definition in LINKAGE SECTION.
Improper definition in FILE SECTION.
Invalid or improperly aligned data in an input file.
Improper initialization using MOVE ZERO.
Runaway or uninitialized subscript or index.
0C8 and 0CA
Arithmetic overflow: the receiving field of an arithmetic operation is too small.
0C9 and 0CB
Divide exception: dividing by zero.
0CC, 0CD, 0CE, and OCF
A problem in floating point operation. Did you specify COMP-1 or COMP-2 usage accidentally?
13E in BMP Region
CA InterTest Batch END, QUIT, or CANCEL caused a detach error in the BMP region.
 1710


InterTest™ and SymDump ® 11.0
213
The system could not find the file as specified in the allocate statement. Check system message for further
Reason.
437
An I/O error occurred while processing the end-of-volume condition.
706
Attempt to execute a program that has been marked 'not executable' by the linkage editor.
Attempt to execute an object file.
Attempt to execute a source file.
806
The load module was not found in the system library or the dynamic STEPLIB you provided.
80A
Not enough virtual storage was available to allocate the amount required by the program. Log on specifying
a larger region size and retry. Some data centers have TSO size restrictions. If you specify a size larger than
permitted, the size allocated will default to the data center's default size.
90A
An area of main storage was released by a program, but it was an area that was not attached to the program. This
usually means a file was closed twice.
913
A security or password violation has occurred.
B37
The file required more direct access space than was requested by the DD statement. This is usually caused by
incorrect direct access space allocation or a program loop that contains a WRITE statement.
C03
The application that you were debugging has left some files open. Correct the logic in your application to close
the files before exiting.
D37
The file required more direct access space than was requested by the DD statement. This is usually caused by an
underestimated direct access space allocation or a program loop that contains a WRITE statement.
 1711


InterTest™ and SymDump ® 11.0
E37
The volume does not contain enough available space to allocate the amount requested for a file.
519
A procedure exit has been reached, and the user has bypassed statements so the references to the calling
statement are not defined.
SymDump  Batch Messages
This section defines all the errors, warnings, and informational messages specific to SymDump  Batch. It serves as a
debugging tool for programmers using SymDump  Batch in a z/OS environment.
Message Format
All messages issued by SymDump  Batch are in the format CAP xyyyz , where CAP is the message prefix for SymDump
Batch and xyyyz  are described in the following table:
Code Description Value Description
x Component issuing the
messageC
D
E
H
I
R
U
ZExecution Monitor
SymDump
Abend Handler
TSO facility
Repository Interface
Analyzer Reporter
Utilities
REST API
yyy Message number I-999 Message identifier
z Action to be taken E
I
WAn error has occurred.
Processing will not continue.
This is an informational
message, no action is required.
This is a warning message.
Processing will continue, but
there may be an impact on
results.
Three vertical dots between two messages mean that all message numbers falling between those two numbers produce
the same message text and have the same Reason and Action text as the surrounding messages.
Example:
CAPR334E . . . CAPR338E
Optimizer/II  Considerations
SymDump  Batch can be used as a replacement execution-time environment for Optimizer/II  users. However, some
messages specifically relating to the Analyzer and Detector features of Optimizer/II  do not appear in this section.
 1712


InterTest™ and SymDump ® 11.0
When executing OS/VS COBOL programs that have been optimized with the DTECT or XCOUNT option, you may
encounter individual messages related to these features with the following prefixes that do not appear in this section:
Prefix Description
CAPA Analyzer
CAPC Execution Monitor
CAPD Detector
CAPE Extended Detector
CAPR Reporter
If you encounter any messages beginning with these prefixes, you should always refer to this section first.
CAPC011W
NO INPUT DATA PRESENT – INSTALLATION DEFAULTS USED.
Reason:
There were no records in the CAIOPTS data set. All the installation-specified option settings in the default CSECT module
apply for this execution.
Action:
Ensure that default options are intended; see the Options in Effect section of the Execution Monitor Summary. Make any
necessary corrections and rerun.
CAPC012I
INPUT OPTION DISPLAY COMPLETE.
Reason:
This message is printed on CAIPRINT to announce the end of input data in the CAIOPTS data set.
Action:
None.
CAPC013I
'keyword' PARAMETER IGNORED DUE TO PREVIOUSLY DEFINED dddddddd STATEMENT.
Reason:
The SYMDSN, PRTLIB, or NDVRDSN parameter was specified in the CAIOPTS data set, but the CAISYM, CAIPRTLB, or
CAINDVR DD was already coded in the JCL. These parameters cannot be used to override DD statements in the JCL.
Action:
This is an informational message, no action is required. The parameter is ignored.
However, to eliminate this error, remove the DD statement from your JCL or remove the parameter from CAIOPTS.
CAPC018E


CAPC018E
DYNAMIC ALLOCATION FAILED FOR DDNAME dddddddd, RC=nn, S99INFO=hhhh, S99ERROR=hhhh.
Reason:
An error occurred during an attempt to dynamically allocate the file specified by DDNAME. This could be a simple user
error such as a misspelled data set name, or it could be a system problem. nn is the return code from SVC 99. hhhh gives
various informational reason codes about the error encountered during SVC 99 processing.
Depending on the error, the job step may be terminated. If the allocation was for a symbolic (PROTSYM or CSL) data set,
execution continues. However, some symbolic information may not be available in your reports.
Action:
 1713


InterTest™ and SymDump ® 11.0
See one of the following IBM publications for an interpretation of these SVC 99 error codes, or retain all JCL and console
log information and contact Broadcom Support  for assistance.
•
•GC28-1150-1 MVS/XA SPL: System Macros and Facilities Volume 1
•
•GC28-0627-2 OS/VS2 MVS SPL: Job Management, pages 27-31.
•
CAPC020W
'string' IS NOT RECOGNIZED AND WILL BE IGNORED.
Reason:
An unrecognizable keyword has been located in the CAIOPTS DD and is ignored. Scanning resumes with the next token
on the card image or the next record, and execution continues.
Action:
Correct the string on the CAIOPTS DD statement and resubmit the job.
CAPC021I
'string' IS AN INVALID OPERAND FOR 'keyword'. KEYWORD REJECTED.
Reason:
An unrecognizable operand has been located in the 'keyword' option of the CAIOPTS DD statement that was specified;
the operand is ignored. Scanning resumes with the next token on the card image or the next record, and execution
continues.
Action:
Correct the string and resubmit the job.
CAPC022I
'string' IS AN INVALID OPERAND FOR 'keyword'. NAME MUST NOT EXCEED 8 CHARACTERS.
Reason:
A valid keyword is followed by a token (option value) that is greater than 8 characters. The keyword is ignored. Scanning
resumes with the next token on the card image or the next record, and execution continues.
Action:
Correct the token, make it fewer than 9 characters, and resubmit the job.
CAPC023I


CAPC023I
'string' IS AN INVALID OPERAND FOR 'keyword'. NAME CONTAINS AN INVALID CHARACTER.
Reason:
A valid 'keyword' is followed by a token (option value) that contains a non-alphanumeric character. The 'keyword' is
ignored. Scanning resumes with the next token on the card image or the next record. Execution continues.
Action:
Correct the token, make it an alphanumeric character, and resubmit the job.
CAPC024I
'string' IS AN INVALID OPERAND FOR 'keyword'. VALUE EXCEEDS MAXIMUM ALLOWABLE SIZE.
Reason:
A valid keyword contains an option value that exceeds the limit placed on the magnitude or size of that value. The value is
set to the maximum.
 1714


InterTest™ and SymDump ® 11.0
Action:
No action required. However, to eliminate this informational message, correct the value of the option and resubmit the job.
CAPC025I
'string' IS AN INVALID OPERAND FOR 'keyword'. VALUE MUST BE NUMERIC.
Reason:
A valid 'keyword' contains a non-numeric option value. The 'keyword' is ignored, and the default (if any) for this keyword is
used. Scanning resumes with the next token on the card image or the next record, and execution continues.
Action:
No action required. However, to eliminate this informational message, correct the value of the option and resubmit the job.
CAPC030I
CA SymDump Batch RTL INITIALIZATION REQUESTED.
Reason:
The RTL initialization program was invoked to initialize the SymDump  Batch RTL.
Action:
None.
CAPC031I
CA SymDump Batch RTL INITIALIZATION COMPLETED.
Reason:
The SymDump  Batch RTL was initialized successfully.
Action:
None.
CAPC032E
CA SymDump Batch RTL INITIALIZATION FAILED.
Reason:
An error was encountered while attempting to initialize the SymDump  Batch RTL.
Action:
Save all output listings and contact Technical Support.
CAPC033I
CA SymDump Batch RTL REFRESH REQUESTED.
Reason:
The RTL initialization program was called but the SymDump  Batch RTL was already initialized. A refresh will instead be
attempted.
Action:
None.
CAPC034I
CA SymDump Batch RTL REFRESH COMPLETED.
Reason:
The SymDump  Batch RTL was refreshed.
Action:
None.
 1715


InterTest™ and SymDump ® 11.0
CAPC035E
CA SymDump Batch RTL REFRESH FAILED.
Reason:
The SymDump  Batch RTL was not refreshed because the DELETE function failed one or more modules.
Action:
Save all output listings and contact Broadcom Support .
CAPC040I
CA SymDump Batch RTL TERMINATION REQUESTED.
Reason:
The RTL termination program was invoked to terminate the SymDump  Batch RTL.
Action:
None.
CAPC041I
CA SymDump Batch RTL TERMINATION COMPLETED.
Reason:
The SymDump  Batch RTL was terminated successfully.
Action:
None.
CAPC042E
CA SymDump Batch RTL TERMINATION FAILED.
Reason:
The SymDump  Batch RTL was not terminated because the DELETE function failed for one or more modules.
Action:
Save all output listings and contact Technical Support.
CAPC043W
CA SymDump Batch RTL IS NOT INITIALIZED.
Reason:
The SymDump  Batch RTL was not terminated because it had not been previously initialized.
Action:
None.
CAPC077E
ERROR ADDING FILE TO THE CAIPRINT REPOSITORY.
Reason:
An error occurred while adding a CAIPRINT report to the central VSAM repository.
Action:
Review the supplementary CAPC077E message that follows for more information about the nature of the error. Take
appropriate steps to resolve the indicated error. A list of supplementary CAPC077E messages follows:
 1716


InterTest™ and SymDump ® 11.0
•CAPC077E Invalid request
•CAPC077E Unable to allocate ACB
•CAPC077E Unable to allocate RPL
•CAPC077E Unable to modify RPL
•CAPC077E Unable to allocate repository
•CAPC077E ENQUEUE failed
•CAPC077E Unable to open repository
•CAPC077E Unable to read repository record
•CAPC077E Unable to read repository record for update
•CAPC077E Unable to write repository
•CAPC077E Unable to close repository
•CAPC077E DEQUEUE failed
•CAPC077E repository is full
•CAPC077E Logic error, READ prior to OPEN
•CAPC077E Invalid index id requested
Verify the following:
•The repository was correctly generated at installation time (see Allocate CAIPRINT Repository Library).
•The PRTLIB option in the default CSECT, CAOETABL, specifies the correct library.
•The repository is not full. If it is full, use the utility program, CAOUPRTU, to delete or archive selected reports.
If the error persists, save all output listings and contact Technical Support.
CAPC078W
FILE NOT ADDED TO THE CAIPRINT REPOSITORY.
Reason:
Conditions prevented a CAIPRINT report from being written to the repository.
Action:
Review the supplementary CAPC078W message that follows for more information about what prevented the
CAIPRINT report from being written to the repository. If needed, take appropriate steps to resolve the problem. A list of
supplementary CAPC078W messages follows:
•CAPC078W Report not found in repository
•CAPC078W Report date mismatch
•CAPC078W Report time mismatch
•CAPC078W Lock error


•CAPC078W Report time mismatch
•CAPC078W Lock error
•CAPC078W Duplication limit exceeded
•CAPC078W Repository is empty
If you want to have CAIPRINT reports written to the central VSAM repository, verify the following:
•The repository was correctly generated at installation time (see Allocate CAIPRINT Repository Library).
•The PRTLIB option in the default CSECT, CAOETABL, specifies the correct library.
•The DUPLIM option in the default CSECT, CAOUDFRX is not set too low.
•If you do not want to have CAIPRINT reports written to the central VSAM repository, set the PRTREPT option in the
default CSECT, CAOETABL, to PRTDD.
If the problem persists, save all output listings and contact Technical Support.
 1717


InterTest™ and SymDump ® 11.0
CAPC081E
INVALID PROGRAM RETURN SEQUENCE. SEE USER GUIDE FOR CALL/ENTRY/RETURN REQUIREMENTS.
Reason:
The Execution Monitor is in the process of monitoring the exit of a given program. During save area chain validity
checking, it is determined that a serious violation of save area linkage has occurred that makes further execution
impossible. The Execution Monitor abends the task with a U1081 abend and a dump.
Action:
Review the source code of the named module for proper adherence to standard linkage conventions. If all appears
reasonable, save all the documentation and contact Broadcom Support  for assistance.
CAPC082E
OUT OF SPACE FOR INTERNAL CONTROL BLOCKS. INCREASE REGION SIZE.
Reason:
A conditional GETMAIN failed in an attempt to obtain more storage from subpool 0 (user storage). Execution is terminated
immediately with a U1082 abend.
Action:
Increase the region size available to the job step and resubmit the job.
CAPC084E
INVALID ERROR CODE PASSED TO CAOCER00.
Reason:
Internal programming error. A module has called the error print module, CAOCER00, with an invalid error code in Register
0. Execution is terminated immediately with a U1084 abend.
Action:
This is a product error. Contact Broadcom Support  for assistance.
CAPC088E
UNABLE TO LOAD MODULE CAODMAIN
Reason:
The Execution Monitor was unable to load Abend Reporter module, CAODMAIN. Execution terminates.
Action:
Verify that the library containing module CAODMAIN is available at execution-time in LINKLIST or LPA, or was specified in
the JCL in STEPLIB or JOBLIB.
CAPC089E
INVALID CALL TO CPXCEM INTERNAL ENTRY POINT
Reason:


CAPC089E
INVALID CALL TO CPXCEM INTERNAL ENTRY POINT
Reason:
An error has occurred upon entry to the Execution Monitor. The task abends with a U-1089 abend.
Action:
Save all the output and contact Technical Support for assistance.
CAPC091E
INTERNAL ERROR. MTAP/XTAP CANNOT BE TRACED ACROSS THE RUN UNIT.
Reason:
Execution is terminated with a U1091 abend and a dump. Either Abend Reporter or MAPPER called the Execution
Monitor to locate the first MTAP or XTAP associated with the run unit prior to the current one supplied as input.
 1718


InterTest™ and SymDump ® 11.0
Action:
Save all related documentation, including the dump, and contact Technical Support for assistance.
CAPC094E
PRINT FILE HAS BEEN OMITTED AND CANNOT BE ALLOCATED. RUN TERMINATED.
Reason:
This message is issued after message CAPC018E is issued to the console and user log. The CAIPRINT file is required for
execution, and the allocation failure causes immediate termination of the run with a U1094 abend code and dump.
Action:
CAPC018E should provide clues to the failure of dynamic allocation, or you can supply a DD statement of your own to
identify the problem. Correct the error accordingly and resubmit the job.
CAPC097E
INTERNAL ERROR. DIAGNOSTIC PGM IN CONTROL.
Reason:
The error recovery mechanisms (for example, ESTAE exits) of the Batch runtime system have encountered an
unexpected and unrecoverable abend. The most likely event is an unexpected 0Cx abend in the runtime system.
This could be traceable to an invalid control block, product logic error, or user error. The runtime system captures a few
data elements related to the abend and attempts to relate the abending PSW address to an offset within a named module.
The abend code (e.g., 0C4) and the registers at abend, along with other pertinent information are written to CAIPRINT.
The execution monitor then issues a user ABEND code of 1097 and an ABEND dump is produced.
The difference in abend code reflects what process was in control at the time of the abend.
This message is issued (abend code 1097) when a user diagnostic program was in control and did not return to its caller.


Configuring documents how a customer can create a reporting module for specific abend codes that are given control
by Abend Reporter to report on the error. For example, assume that the runtime system has initially trapped a system
0C1. Normally, Abend Reporter calls the distributed module CAOD00C1 to produce the abend box (description, probable
causes, etc.). If a 1097 abend appears, you should look for the presence of an entry for 0C1 in the user abend table
module CAOCAB80. This customization process is also discussed in Configuring.
Action:
Contact Broadcom Support to report the problem after the dump is available. In the RTM2WA summary, abends are
represented by a chain of SDWA control blocks displayed in chronological order from the oldest to the newest. Generally,
diagnose the problem by finding the SWDA in the RTM2WA SUMMARY chain that matches the abend code and registers
displayed on CAIPRINT. The unexpected and unrecoverable abend is documented as the SDWA that is queued just prior
to the final user abend code 1097.
CAPC098E
INTERNAL ERROR. ABEND REPORTER IN CONTROL.
Reason:
The error recovery mechanisms (for example, ESTAE exits) of the runtime system have encountered an unexpected and
unrecoverable abend. The most likely event is an unexpected 0Cx abend in the runtime system.
This could be traceable to an invalid control block, product logic error, or user error. The runtime system captures a few
data elements related to the abend and attempts to relate the abending PSW address to an offset within a named module.
The abend code (for example, 0C4) and the registers at abend, along with other pertinent information, are written to


CAIPRINT. The execution monitor then issues a user abend code of 1098 and an abend dump is produced.
As the message text implies, the difference in abend code reflects what process was in control at the time of the abend.
This message is issued when SymDump  (CAOD xxxx) was in control and did not return to its caller.
Action:
Contact Broadcom Support  to report the problem after the dump is available. In the RTM2WA summary, abends are
represented by a chain of SDWA control blocks displayed in chronological order from the oldest to the newest. Generally,
 1719


InterTest™ and SymDump ® 11.0
diagnose the problem by finding the SDWA in the RTM2WA SUMMARY chain that matches the abend code and registers
displayed on CAIPRINT. The unexpected and unrecoverable abend is documented as the SDWA that is queued just prior
to the final user abend code 1098.
CAPC099E
INTERNAL ERROR. EXECUTION MONITOR OR MAPPER IN CONTROL.
Reason:
An unrecoverable abend has occurred in the runtime system. The most likely event is an unexpected 0Cx abend.
Action:
Contact Broadcom Support  to report the problem after the dump is available.
CAPD107E
INSUFFICIENT MAIN STORAGE AVAILABLE.
Reason:
SymDump  ran out of memory.
Action:
If possible, increase the region size. If this does not resolve the problem, save all output materials and contact Broadcom
Support .
CAPD109W
SNAPSHOT CALL TURNED OFF.
Reason:
The region size is not large enough for operation of the SNAP feature. The feature is turned off and program processing
continues.
Action:
Increase region size. For details, see CICS Interfaces and Compatibility.
CAPD110W
SYMBOLIC FILE INITIALIZATION FAILED.
Reason:
An error was detected while trying to access a PROTSYM or CSL file. SymDump  reporting continues, but symbolic
support will not be provided for this execution.
Action:
Verify that your PROTSYM and CSL data set names have been specified correctly and that the files are correctly defined.
Rerun the job if necessary. If you cannot determine the cause of this message, contact Broadcom Support .
CAPD112W
NO SYMBOLIC INFORMATION FOUND FOR PROGRAM "xxxxxxxx".
Reason:


CAPD112W
NO SYMBOLIC INFORMATION FOUND FOR PROGRAM "xxxxxxxx".
Reason:
Abend Reporter is attempting to retrieve symbolic information for a program, but no information was found in any of the
PROTSYM or CSL files available to Abend Reporter.
Abend Reporter processing continues, but symbolic support is not provided for the program.
Action:
First, verify that the symbolic information has been written to a PROTSYM file or a CSL file. Then verify that the symbolic
file is available to Abend Reporter using your installation defaults, your JCL, or a SYMDSN override.
If you still cannot determine the cause of this message, contact Technical Support.
 1720


InterTest™ and SymDump ® 11.0
CAPD113W
SYMBOLIC MEMBER DATE/TIME DOES NOT MATCH CURRENT PROGRAM.
Reason:
Symbolic information was found for at least one version of your program in one of the available symbolic files, but the time
stamp in the program does not exactly match the symbolic information.
Action:
First, verify that the symbolic information for the current version of your program has been written to a PROTSYM file or
a CSL file. If the program has been recompiled and relinked, the symbolic file must be reloaded. This problem can also
occur if your program has been recompiled and the symbolic file updated, but the program has not yet been relinked. If
you have correctly loaded the latest symbolic information into a symbolic file, verify that the symbolic file is available to
Abend Reporter using your installation defaults, your JCL, or a SYMDSN override.
If you still cannot determine the cause of this message, contact Technical Support.
CAPD114W
SYMBOLIC FILE READ ERROR-SYMBOLIC INFORMATION MAY BE INCOMPLETE.
Reason:
An error was detected while attempting to read symbolic information from one of the available symbolic files. SymDump
processing continues, but symbolic information may be incomplete.
Action:
Verify that all of your available symbolic files are valid, and that their data set names are specified correctly in your
installation defaults, JCL, or CAISYM override statements. Correct the error and rerun the job if necessary. If you still
cannot determine the cause of this message, contact Broadcom Support .
CAPD115W
INTERRUPT OCCURRED IN REGION OR SYSTEM. NO CSECT DUMP WAS PRODUCED.
Reason:
An interrupt occurred outside of a user program or outside the user region. Processing continues.
Action:
None.
CAPD116W


Action:
None.
CAPD116W
CSECT LENGTH UNKNOWN, PROCEEDING TO DUMP ENTIRE LOAD MODULE.
Reason:
Abend Reporter was unable to determine the length of a control section, so the entire load module has been dumped
instead using a standard "dump" format.
Action:
None.
CAPD117W
UNABLE TO LOCATE LOAD MODULE; LOAD MODULE DUMP SUPPRESSED.
Reason:
Abend Reporter was unable to relate an interrupt address with a load module name during a scan of system control
blocks (CDE chain queued off the TCB). Processing continues.
Action:
None.
 1721


InterTest™ and SymDump ® 11.0
CAPD118W
PROCESSING TERMINATED DUE TO INSTALLATION REQUEST.
Reason:
An entry in the user table CAOCAB80 specified that DETECT equals OFF. A report will not be produced.
Action:
None.
CAPD123I
INSTRUCTION LOCATED PRIOR TO THE FIRST PROCEDURE STATEMENT. POSSIBLE ERROR COMPUTING THE
SIZE OF A VARIABLE-LENGTH TABLE.
Reason:
The instruction which corresponds to the indicated program offset is located prior to the first Procedure Division statement
in the program and does not correspond to a COBOL source statement. One possible reason for this is that an error
occurred while computing the size of a variable-length table.
Action:
Verify that the DEPENDING ON variables for any variable-length tables are initialized before the tables are referenced.
Alternatively, if a CAPD113W message was displayed, indicating that the symbolic file member does not exactly match the
program in the executable load module, follow the action specified for that message.
CAPD137I
CSECT DUMP SUPPRESSED DUE TO EXCLUSION CRITERIA.
Reason:
The abending CSECT was not displayed in the Abend Reporter because it was specifically excluded using the
CAOUXMOD option of default options member, CAOUDFRX.
Action:
None.
CAPD138I
INTERRUPT OCCURRED IN REGION OR SYSTEM. DUMPING CSECT FOR CALLING PROGRAM.
Reason:
An interrupt occurred outside of a user program or outside of the user region. The CSECT dump will be generated for the
previously active user program (as indicated in the save area chain).
Action:
None.
CAPD140E
INTERNAL ERROR DURING DB2 PROCESSING. DB2 PROCESSING HALTED.
Reason:


INTERNAL ERROR DURING DB2 PROCESSING. DB2 PROCESSING HALTED.
Reason:
An error occurred in the reporter which accesses the DB2 catalog. Processing is halted for the DB2 section of the report.
Action:
Rerun the job with the options DUMP ON and DB2TRACE ON specified in the CAIOPTS DD. Collect all output including
JCL, log messages and dump. Contact Broadcom Support .
CAPD141E
ERROR PROCESSING SQLCODE. RETURN CODE FROM DSNTIAR=rc.
Reason:
 1722


InterTest™ and SymDump ® 11.0
An error occurred while trying to print the message associated with SQLCODE. The return code from DB2 module
DSNTIAR is indicated in the message.
Action:
Rerun the job with the options DUMP ON and DB2TRACE ON specified in the CAIOPTS DD. Collect all output including
JCL, log messages, and dump. Contact Broadcom Support .
CAPD142W
THE PARAMETER LIST FOR THE LAST SQL CALL WAS NOT FOUND.
Reason:
The parameter list for the last SQL call was not found in the DB2 control block.
Action:
If an SQL statement has been executed in the application, collect all output (including JCL, log messages, and dump) and
contact Technical Support. Otherwise, no action is necessary.
CAPD143W
PROGRAM pppppppp HAS BEEN RECOMPILED SINCE IT WAS LAST BOUND.
Reason:
The indicated program has been recompiled since the last time that the package or plan containing the program was
bound.
Action:
If you are using a product such as Bind Analyzer , which allows programs to be changed without rebinding, no action is
necessary. Otherwise, rebind the package or plan for the program.
CAPD144W
UNABLE TO FIND A UNIQUE SQL STATEMENT IN SECTION sssss FOR THE INDICATED STATEMENT TYPE.
Reason:
The SQL statement number could not be used to find the last SQL statement (because the program was recompiled since
the last time it was bound or the statement number was greater than 32767, and was therefore saved in the catalog table
as 0). When Detector tried to use the section number and statement type to find the last SQL statement, it found multiple
statements of that type in the section.
Action:
None.
CAPD145W


statements of that type in the section.
Action:
None.
CAPD145W
SQL STATEMENT sssss WAS NOT FOUND IN THE DB2 CATALOG.
Reason:
The indicated SQL statement could not be found in DB2 catalog table SYSSTMT or SYSPACKSTMT.
Action:
Contact Broadcom Support .
CAPD146W
PLAN pppppppp WAS NOT FOUND IN THE DB2 CATALOG.
Reason:
The indicated plan could not be found in the DB2 catalog table SYSPLAN.
Action:
Collect all output including JCL, log messages, and dump. Contact Broadcom Support .
 1723


InterTest™ and SymDump ® 11.0
CAPD147I
NO OBJECT DEPENDENCIES WERE FOUND FOR PLAN pppppppp.
Reason:
No entries were found in the DB2 catalog table SYSPLANDEP for the indicated plan.
Action:
None.
CAPD148I
NO PACKAGE LIST WAS FOUND FOR PLAN pppppppp.
Reason:
No entries were found in the DB2 catalog table SYSPACKLIST for the indicated plan.
Action:
None.
CAPD149I
NO ACTIVE PACKAGES WERE FOUND FOR PLAN pppppppp.
Reason:
None of the entries found in the DB2 catalog table SYSPACKLIST for the indicated plan corresponded to programs that
were active at the time of the report.
Action:
None.
CAPD150I
NO OBJECT DEPENDENCIES WERE FOUND FOR PACKAGE pppppppp.
Reason:
No entries were found in the DB2 catalog table SYSPACKDEP for the indicated package.
Action:
None.
CAPD151I
NO DBRMS WERE FOUND FOR PLAN pppppppp.
Reason:
No entries were found in the DB2 catalog table SYSDBRM for the indicated plan.
Action:
None.
CAPD152I
NO ACTIVE DBRMS WERE FOUND FOR PLAN pppppppp.
Reason:
None of the entries found in the DB2 catalog table SYSDBRM for the indicated plan corresponded to programs that were
active at the time of the report.
Action:
None.
 1724


InterTest™ and SymDump ® 11.0
CAPD153E
CHARACTER CONVERSION FAILED: RC = nn, REASON = mm.
Reason:
An error occurred when converting a string from UTF-8 to EBCDIC.
Action:
Collect all output including JCL, log messages, and dump. Contact Broadcom Support .
CAPD154W
CAODSTKN – LOAD OF CAOUDIXR FAILED.
Reason:
Dynamic symbolic support encountered an error loading module CAOUDIXR.
Dynamic symbolic support is not able to populate mismatched symbolic for the abending CSECTs.
Action:
Ensure that the SymDump  Batch product load module libraries are correctly defined in your JCL or are defined in your
installation's LNKLST.
CAPD157W
CAOFMAIN – LOAD OF CAODNDVR FAILED.
Reason:
Dynamic symbolic support encountered an error loading module CAODNDVR.
Dynamic symbolic support will not be able to populate mismatched symbolic for the abending CSECTs.
Action:
Ensure that the SymDump  Batch product load module libraries are correctly defined in your JCL or are defined in your
installation's LNKLST.
CAPD158W
CAOFMAIN – LOAD OF CAOUDIXR FAILED.
Reason:
Dynamic symbolic support encountered an error loading module CAOUDIXR.
Dynamic symbolic support will not be able to populate mismatched symbolic for the abending CSECTs.
Action:
Ensure that the SymDump  Batch product load module libraries are correctly defined in your JCL or are defined in your
installation's LNKLST.
CAPE001E
mmmmmmmm NOT FOUND - INITIALIZATION INCOMPLETE.
Reason:
An Abend Handler module was not available during initialization of Abend Handler.
Action:


An Abend Handler module was not available during initialization of Abend Handler.
Action:
Ensure that all Abend Handler modules from CAI.CAVHLOAD are available when initializing Abend Handler.
CAPE002E
INTERCEPT FAILED - INITIALIZATION INCOMPLETE.
Reason:
The SymDump  SVC hook could not be inserted.
Action:
 1725


InterTest™ and SymDump ® 11.0
Review all installation procedures. Rerun the job once more. If this message appears again, notify Broadcom Support .
CAPE003I
UNABLE TO OBTAIN LOCK. REFRESH WILL CONTINUE WITHOUT LOCK.
Reason:
Another job was using SymDump  when an attempt was made to reinitialize. SymDump  is reinitialized.
Action:
None.
CAPE003W
UNABLE TO OBTAIN LOCK. CONTINUE INITIALIZATION WITHOUT LOCK?
Reason:
Another job was using SymDump  when an attempt was made to reinitialize.
Action:
If you reply Y or YES, SymDump  reinitializes. If you reply N or NO, initialization is terminated.
CAPE004I
SQA TABLE RESIDES IN CORE AT ADDRESS nnnnnnnn.
Reason:
This message is for diagnostic purposes only.
Action:
None.
CAPE005I
INITIALIZATION COMPLETED.
Reason:
You have successfully initialized or refreshed the SymDump  system.
Action:
None.
CAPE006E
INTERNAL ABEND ENCOUNTERED.
Reason:
This message is issued whenever SymDump  has detected an internal error.
Action:
Collect all output including JCL, log messages, and dump. Contact Broadcom Support .
CAPE007E
INTERRUPT AT PSW xxxxxxxx EP=xxxxxxxxR0-R3 xxxxxxxx xxxxxxxx  xxxxxxxx  xxxxxxxxR4-R7 xxxxxxxx
xxxxxxxx  xxxxxxxx  xxxxxxxxR8-RB xxxxxxxx  xxxxxxxx  xxxxxxxx  xxxxxxxxRC-RF xxxxxxxx  xxxxxxxx  xxxxxxxx
xxxxxxxx
Reason:
The SymDump  ESTAE has intercepted an internal error. This message indicates the PSW and registers from the time of
the error.


the error.
Action:
Collect all output including JCL, log messages, and dump. Contact Broadcom Support .
 1726


InterTest™ and SymDump ® 11.0
CAPE008E
REPORT TERMINATED BECAUSE XXXXXXXXXXXXXXX.
Reason:
A condition has occurred which has prevented the completion of the SymDump .
Action:
Collect all output including JCL, log messages, and dump. Contact Broadcom Support .
CAPE009E
REPORT WAS NOT PRODUCED BECAUSE NO PRB WAS FOUND.
Reason:
Abend Handler could not find a Program Request Block (PRB) on the RB chain.
Action:
None.
CAPE010E
UNABLE TO LOCATE RUNTIME MODULES. INITIALIZATION INCOMPLETE.
Reason:
A module required for initialization was not found.
Action:
Ensure that all SymDump  Batch modules are available when initializing SymDump .
CAPE011E
EXCEPTION ENCOUNTERED IN CAOETSEL.
Reason:
This message is issued whenever SymDump  has detected an internal error in module CAOETSEL while attempting to
evaluate possible exclusion criteria.
Action:
Collect all output including JCL, log messages, and dump. Contact Broadcom Support .
CAPE013I
UNABLE TO OBTAIN LOCK. ABEND HANDLER WILL BE DISABLED WITHOUT LOCK.
Reason:
Another job was using SymDump  when an attempt was made to disable it. SymDump  will be disabled.
Action:
None.
CAPE013W
UNABLE TO OBTAIN LOCK. CONTINUE TO DISABLE ABEND HANDLER WITHOUT LOCK?
Reason:
Another job was using SymDump  when an attempt was made to disable it.
Action:
If you reply Y or YES, SymDump  will be disabled. If you reply N or NO, it will not.
CAPE014I
ABEND HANDLER IS NOT ACTIVE - NO ACTION WILL BE TAKEN.
 1727


InterTest™ and SymDump ® 11.0
Reason:
An attempt was made to disable SymDump  support when it was already disabled. SymDump  remains disabled.
Action:
None.
CAPE015I
ABEND HANDLER IS NOW DISABLED.
Reason:
SymDump  has been successfully disabled.
Action:
None.
CAPE016W
OPTIONS NOT UPDATED BECAUSE MODULE CAOETABL IS NOT AVAILABLE.
Reason:
An attempt to update CAOETABL was made, but CAOETABL was not available.
Action:
The SymDump  options table is not updated. Ensure that CAOETABL is available through STEPLIB, JOBLIB, LINKLIST or
LPA and is APF authorized.
CAPE017I
ABEND HANDLER IS NOT CURRENTLY ACTIVE - NO ACTION WILL BE TAKEN.
Reason:
An attempt was made to update the SymDump  options, but SymDump  was not initialized on the system.
Action:
The options are not updated. Your options table will be loaded when you initialize SymDump .
CAPE018I
OPTIONS SUCCESSFULLY UPDATED.
Reason:
A successful update of CAOETABL has been completed.
Action:
None.
CAPE019I
UNABLE TO OBTAIN LOCK. OPTIONS WILL BE UPDATED WITHOUT LOCK.
Reason:
Another job was using SymDump  when an attempt was made to update the options table. The SymDump  options will be
updated
Action:
None.
CAPE019W
UNABLE TO OBTAIN LOCK, SHOULD TABLE UPDATE CONTINUE WITHOUT LOCK?
Reason:
Another job was using Abend Handler when an attempt was made to update the options table.
 1728


InterTest™ and SymDump ® 11.0
Action:
If you reply Y or YES, Abend Handler will be updated. If you reply N or NO, it will not.
CAPE021E
REPORT WAS NOT PRODUCED BECAUSE A NECESSARY MODULE WAS MISSING.
Reason:
Abend Handler was unable to load CAOCEM00.
Action:
Ensure that the SymDump  Batch RTL is available through STEPLIB, JOBLIB, LINKLIST or LPA.
CAPE022I
jjjjjjjj  ssssssss ABENDED taaa IN PROGRAM pppppppp AT OFFSET +oooooo.
Reason:
SymDump  has completed a report, but no symbolic information was available for the abending program.
Action:
Use your report to correct the application.
CAPE023I
jjjjjjjj  pppppppp ABENDED taaa AT ssssssssssssssssssssssssss.
Reason:
SymDump  has completed a report, and symbolic information was available for the abending program.
Action:
Use your report to correct the application.
CAPE024E
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Reason:
An invalid reply was entered by the operator.
Action:
Reply Y or N.
CAPE025I
jjjjjjjj  ssssssss UNHANDLED CONDITION CEEnnnnx RAISED IN PROGRAM pppppppp AT OFFSET +oooooo.
Reason:
SymDump  has completed an unhandled LE condition, but no symbolic information was available for the offending
program.
Action:
Use your report to correct the application.
CAPE026I


program.
Action:
Use your report to correct the application.
CAPE026I
jjjjjjjj  pppppppp UNHANDLED COND CEEnnnnx AT ssssssssssssssssssssssssssssssssssssssssssssssss
Reason:
SymDump  has completed an unhandled LE condition, and symbolic information was available for the offending program.
Action:
Use your report to correct the application.
 1729


InterTest™ and SymDump ® 11.0
CAPE027I
ABEND REPORT SUPPRESSED DUE TO STOPDD ddname
Reason:
The indicated DD name was specified in the JCL for the abending job step. The abend report is suppressed.
Action:
None
ABEND REPORT SUPPRESSED DUE TO KEY LESS THAN 8
Reason: SymDump  Batch reports on abends that occur in key 8. If the abend occurs in any other key, SymDump  Batch
will not report on the abend.
Action: None
ABEND REPORT SUPPRESSED DUE TO RMODE 64 PSW
Reason: The abending program resides above the bar. The abend report is suppressed.
Action: None
CAPE028I
ABEND REPORT NOT GENERATED DUE TO EXCLUSION CRITERION: keyword value
Reason:
The abending job step matched an exclusion criterion specified either in the CAOETXCL macro of default member
CAOETABL, or in user exit CAOEUSR1. The message indicates the matching criterion.
Action:
None
CAPE029I
ABEND REPORT GENERATED REGARDLESS OF EXCLUSION CRITERIA DUE TO EXIT CAUEUSR1
Reason:
The abending job step matched inclusion criteria specified in user exit CAOEUSR1. The abend report is generated
regardless of whether it matched exclusion criteria specified in the CAOETXCL macro of default member CAOETABL.
Action:
None
CAPE030W
ALLOCATE FOR dddddddd FAILED. NETMAN INTERFACE NOT AVAILABLE. LOAD for mmmmmmmm FAILED.
NETMAN INTERFACE NOT AVAILABLE.
Reason:
The specified module could not be loaded or the specified DDNAME could not be dynamically allocated.
Action:


Action:
Ensure that the instructions for using the Netman  interface in Configuring have been followed and that all installation
defaults have been set up correctly. If so, contact Broadcom Support.
CAPE031I
RECORD HAS BEEN ADDED TO NETMAN FILE.
Reason:
A record was added by Abend Handler to the Netman  database using the Machine Generated Problem Tracking system.
 1730


InterTest™ and SymDump ® 11.0
Action:
The record is now available for review by an authorized Netman  user.
CAPE032W
NETMAN INTERFACE FAILED DURING UPDATE.
Reason:
An error has occurred while attempting to log a record to Netman  for Machine Generated Problem Tracking.
Action:
Ensure that the instructions for using the Netman  interface in Configuring have been followed and that all installation
defaults have been set up correctly. If so, contact Broadcom Support.
CAPE033W
CAOECEEI–LOAD OF CAOEGMSG FAILED.
Reason:
Language Environment Unhandled Condition support encountered an error loading module CAOEGMSG. LE Unhandled
Condition messages will not be retrieved.
Action:
Ensure that the SymDump  Batch product load module libraries are correctly defined in your JCL or are defined in your
installation's LNKLST.
CAPE034W
CAOECEEI – CAOEGMSG FAILED. RC = nnnn .
Reason:
Retrieval of LE messages function failed, where nnnn  is the severity code returned by CEEMGET, LE Callable Service.
Action:
Contact Broadcom Support  for assistance.
CAPH600W
member NOT CONVERTED, ALREADY EXISTS ON OUTPUT.
Reason:
CAOHCNVT has determined that the CLIST being converted already exists in the output library. CAOHCNVT bypasses
converting this member and attempts to convert the next member. The program ends with a Return Code of 4.
Action:
To convert this member, you either have to rename it in the source library (SYSUT1) data set, or rerun CAOHCNVT
specifying PARM=REPLACE.
CAPH601E
member NOT CONVERTED, OUTPUT DIRECTORY FULL.
Reason:


CAPH601E
member NOT CONVERTED, OUTPUT DIRECTORY FULL.
Reason:
During an attempt to update the directory of the output CLIST library, the directory became filled.
Action:
CAOHCNVT terminates processing and ends with a return code of 8. Either reallocate the output library (SYSUT2) with
additional directory space, or scratch unused members.
CAPH602E
CONVERSION ABORTED, PERMANENT I/O ERROR HAS OCCURRED.
 1731


InterTest™ and SymDump ® 11.0
Reason:
During an attempt to update or read the directory of the output CLIST library, a permanent I/O error occurred. CAOHCNVT
aborts with a U1602 abend.
Action:
Check the allocation of the output library and reallocate it on a different disk if necessary. Rerun the job.
CAPH603E
CONVERSION ABORTED, OUTPUT LIBRARY UNOPENED.
Reason:
During an attempt to update the directory of the output CLIST library, the STOW SVC ended with a return code indicating
the CLIST library did not open.
CAOHCNVT aborts with a U1603 abend. This should not occur since, if the output library does not open, an S0C1 should
occur on the first WRITE. This indicates that there may be a probable IOS error.
Action:
Contact Broadcom Support .
CAPH604E
member NOT CONVERTED, INSUFFICIENT VIRTUAL STORAGE.
Reason:
During an attempt to process the directory of the output CLIST library (SYSUT2), the BLDL or STOW routine ended
abnormally due to insufficient virtual storage availability. CAOHCNVT ends with a return code of 8.
Action:
Increase the REGION size on the EXEC or JOB card and resubmit the job.
CAPH605I
member HAS BEEN SUCCESSFULLY CONVERTED.
Reason:
CAOHCNVT has successfully converted the named input CLIST library member to variable format and stored it under the
same name into the output CLIST library. CAOHCNVT attempts to process the next member (if any).
Action:
None.
CAPH606E
synadaf error message text.
Reason:


None.
CAPH606E
synadaf error message text.
Reason:
An I/O error has occurred while accessing either the input or output CLIST libraries causing the CAOHCNVT SYNAD
routine to get control. CAOHCNVT invokes the SYNADAF facility to format an error message, after which it aborts with a
U1606 abend.
Action:
Check the DCB attributes of the two libraries, correct the error, and resubmit the job.
CAPI000E
Internal error during initialization.
Reason:
An internal error was detected while attempting to initialize the repository viewer API. This typically indicates that an ISPF
environment could not be established.
Action:
 1732


InterTest™ and SymDump ® 11.0
Verify that a valid ISPF environment exists.
If you cannot determine the cause of this error, save any output or screen shots and contact Technical Support.
CAPI002E
<char> is not a valid line command.
Reason:
A line command was entered that is not supported by the current selection list.
Action:
Return to the selection list from which this message was displayed, then press HELP to display the help text for the
display.
The valid line commands for the selection list will be listed in the help text. Enter a valid line command.
If you believe that the line command that you entered was valid, contact Technical Support.
CAPI004E
<keyword> is not a valid command for this screen.
Reason:
A command was entered on the command line that is not supported by the current display.
Action:
Return to the screen from which this message was displayed, then press HELP to display the help text for the screen.
The valid commands for the screen will be listed in the help text. Enter a valid command.
If you believe that the command that you entered was valid, contact Technical Support.
CAPI005E
<keyword> is only valid while a report is loaded.
Reason:
A command was entered on the command line that is not supported unless a report has been selected for viewing.
Action:
Only the TAG (.label), LOCATE, and NOTES commands require an open report to be valid. Enter HELP  command-name
for more information about any of these commands.
If you received this message after entering any other command, contact Technical Support.
CAPI006E
<keyword> is not a valid command.
Reason:
An unrecognized command was entered on the command line.
Action:


Reason:
An unrecognized command was entered on the command line.
Action:
Return to the screen from which this message was displayed, then press HELP to display the help text for the screen.
The valid commands for the screen will be listed in the help text. Enter a valid command.
If you believe that the command that you entered was valid, contact Technical Support.
CAPI007E
Command argument exceeds maximum length of 32 characters
Reason:
An argument specified for the command exceeds 32 characters.
Action:
Repeat the command with the correct arguments.
If you are not sure about the required arguments for the command, enter HELP  command-name  for more information.
 1733


InterTest™ and SymDump ® 11.0
CAPI010E
Internal error.
Reason:
An internal error was detected while the repository viewer was attempting to locate a column header in the current display.
Action:
Contact Broadcom Support .
CAPI011W
No column specified.
Reason:
A command was entered that requires a column header as an argument, but no column header was provided.
Action:
Repeat the command with the correct arguments.
If you are not sure about the required arguments for the command, enter HELP  command-name  for more information.
CAPI012W
Column does not exist.
Reason:
A command was entered that requires a column header as an argument, but the argument provided does not match any
column header for the current display.
Action:
Repeat the command with the correct column header argument.
If you are not sure about the required arguments for the command, enter HELP  command-name  for more information.
CAPI015E
Internal error.
Reason:
An internal error was detected while the repository viewer was attempting to interpret a d line command.
Action:
Contact Broadcom Support .
CAPI016I
Delete cancelled.
Reason:
A delete confirmation pop-up message was displayed in response to a d line command entered on the repository index
selection list, and you responded by pressing END to cancel the request.
Action:
This is an informational message, no action is required.
If you intended to delete the report from your repository, repeat the d line command and confirm the deletion by pressing
Enter as described in the text of the pop-up message.
For more information about confirming a deletion request, enter HELP DELETE  or press HELP while the pop-up message
is displayed.
CAPI017E
Error deleting report.
Reason:
 1734


InterTest™ and SymDump ® 11.0
You attempted to delete a report from your repository, but an error was detected and the report could not be deleted.
Action:
The report may have been deleted by another user after you had entered the viewer.
Return to the repository index selection list, then enter REFRESH  and press Enter to rebuild the list.
If the report still appears in the list, contact Technical Support.
CAPI018I
Delete cancelled.
Reason:
A report was successfully deleted from your repository in response to a d line command from the repository index
selection list.
Action:
This is an informational message, no action is required.
CAPI021W
No search argument specified.
Reason:
A FIND command was entered on the command line, but no search argument was provided.
Action:
Repeat the command with the correct arguments.
If you are not sure about the required arguments for this command, enter HELP FIND  for more information.
CAPI022E
Internal error.
Reason:
An internal error was detected while the repository viewer was attempting to execute a FIND request.
Action:
Contact Broadcom Support .
CAPI023W
Not found.
Reason:
A FIND command was entered on the command line, but the search argument was not found.
Action:
If the search was executed in the forward direction, enter RFIND  to resume the search starting from the top of the display.
If the search was executed in the backward direction, enter RFIND  to resume the search starting from the bottom of the
display.
If you are not sure about the required arguments for this command, enter HELP FIND  for more information.
CAPI026W
Sort invalid for this display.
Reason:
A SORT command was entered on the command line, but the current display does not support sorting.
Action:


Action:
Sorting is only allowed on the repository index selection list or a symbolic file member selection list.
If you have entered a SORT command from one of these displays and this message appeared, contact Technical Support.
 1735


InterTest™ and SymDump ® 11.0
CAPI027I
Sort completed.
Reason:
This message is displayed in response to a successful SORT command. The current display has been sorted on the
contents of the specified column and in the order requested.
Action:
This is an informational message, no action is required.
Enter *SORT ** to restore the current display to its original order.
CAPI030I
SetIndex cancelled.
Reason:
You entered a SETINDEX command to change the name of your repository, but when prompted for a new data set name,
you pressed END to cancel the request.
Action:
This is an informational message, no action is required.
If you intended to change the repository data set name, repeat the SETINDEX command, enter a new name in the field
provided, and press Enter to complete the command.
Enter HELP SETINDEX  for more information about this command, or press HELP when prompted for a new repository
name.
CAPI035W
Cursor not on a data line.
Reason:
A KEEP command was entered but the cursor was not in a valid position. No change was made to your keep window.
Action:
If you are attempting to add a data line to your keep window, place the cursor on the data line and repeat the command.
Only data lines located below the information and header lines can be added to the keep window.
If you are attempting to remove a data line from your keep window, place the cursor on the line within the keep window
that you would like to remove and repeat the command.
Enter HELP KEEP  for more information about this command.
CAPI036I
Keep window is enabled.
Reason:
This message is displayed in response to a KEEP ON command. The keep window is displayed, unless it is empty.
Action:


Action:
This is an informational message, no action is required.
Enter KEEP OFF  to disable the keep window, or enter HELP KEEP  for more information about this command.
CAPI037I
Keep window is disabled.
Reason:
This message is displayed in response to a KEEP OFF command. The keep window is suppressed, even if it contains
data.
Action:
This is an informational message, no action is required.
 1736


InterTest™ and SymDump ® 11.0
Enter KEEP ON  to enable the keep window, or enter HELP KEEP  for more information about this command.
CAPI040I
Options updated.
Reason:
This message is displayed when you press END from the report options display to return to the repository index selection
list.
The repository is updated to reflect the options that you have selected for the report.
Action:
This is an informational message, no action is required.
Use CANCEL instead of END to exit the report options screen without updating the report options in your repository.
Enter HELP RPTOPTS or press HELP while the report options screen is displayed for more information about viewing
and updating report options.
CAPI041E
Error updating options.
Reason:
An error was detected while attempting to update report options in your repository.
Action:
The report may have been deleted by another user after you had entered the viewer.
Return to the repository index selection list, then enter REFRESH  and press Enter to rebuild the list.
If the report still appears in the list, contact Technical Support.
CAPI042I
Options update cancelled.
Reason:
You entered a CANCEL command from the report options screen to return to the repository index selection list.
Any changes to your report options were discarded.
Action:
This is an informational message, no action is required.
CAPI045I
Notes request cancelled.
Reason:
You attempted to open the electronic notepad for a report by entering an n line command from the repository index
selection list or by entering the NOTES command on the command line, but no existing notes were found in your profile
for the report.
Because your profile can only hold notes for a limited number of reports, a confirmation is required before a new notepad
can be created.


can be created.
When prompted for a confirmation, you pressed END to cancel the request instead of pressing Enter to continue.
The request is cancelled, and the notepad is not created.
Action:
This is an informational message, no action is required.
CAPI049W
Cursor is not on a valid data field.
Reason:
 1737