InterTest™ and SymDump ® 11.0
A cursor-sensitive command was entered on the command line without any argument, but the cursor was not located on a
valid data field.
The command fails because no argument can be determined.
Action:
Repeat the command by specifying a valid argument or position your cursor on a valid data line.
CAPI052I
Profile restored as of <hh:mm:ss> on <yyyy/mm/dd>.
Reason:
A report which you have already viewed at least once has been selected for viewing again. The viewing environment
for this report, including the contents and status of the keep window, have been restored from your profile to its previous
state.
The time and date appearing in the message indicate the last time this report was exited by your userid.
Action:
This is an informational message, no action is required.
CAPI055I
Tag request cancelled.
Reason:
You entered a TAG or . command to create a bookmark in the current report, but you failed to specify a tag name. When
prompted for a name, you responded by pressing END to cancel the request or by leaving the name field blank.
The command is cancelled, no bookmark is created.
Action:
This is an informational message, no action is required.
Enter HELP TAG for more information about this command, or repeat the command and press HELP while the pop-up
prompt is displayed.
CAPI056I
Tag <label> added for line number <nnnnn>.
Reason:
This message is displayed in response to a successful TAG or .label command. The new tag name and corresponding
line number are displayed in the text of the message.
Action:
This is an informational message, no action is required.
Enter L label  at any time in the current session to instantly position the viewer to the current line.


Enter HELP TAG or HELP LOCATE for more information about setting and retrieving bookmarks.
CAPI057I
Tag <label> replaced for line number <nnnnn>.
Reason:
This message is displayed in response to a successful TAG or .label command, if the label you specified already existed
from a previous TAG or .label command. The tag name and line number are displayed in the text of the message.
Action:
This is an informational message, no action is required.
Enter L label  at any time in the current session to instantly position the viewer to the current line.
Enter HELP TAG or HELP LOCATE for more information about setting and retrieving bookmarks.
 1738


InterTest™ and SymDump ® 11.0
CAPI058I
Locate request cancelled.
Reason:
You entered a LOCATE command to position the viewer to a bookmark, but you failed to specify a tag name. When
prompted for a name, you responded by pressing END to cancel the request or by leaving the name field blank.
The command is cancelled, no repositioning is performed.
Action:
This is an informational message, no action is required.
Enter HELP LOCATE for more information about this command, or repeat the command and press HELP while the pop-
up prompt is displayed.
CAPI059E
Tag<label> not found.
Reason:
You entered a LOCATE command to position the viewer to a bookmark, but the tag name you specified was not
recognized.
The command is cancelled, no repositioning is performed.
Action:
Check the spelling of your tag name, then repeat the command.
Enter HELP LOCATE for more information about this command, or repeat the command and press HELP while the pop-
up prompt is displayed.
CAPI060I
Print cancelled.
Reason:
You initiated a print request for one of the following:
•
•The current display using a PRINT command.
•
•An entire report using a p line command from the repository index selection list.
•
•A symbolic listing using a p line command from a symbolic file member selection list.
•
When prompted for specifications, you pressed END to cancel the request. No data was printed.
Action:
This is an informational message, no action is required.
If you intended to complete the print request, repeat the command. When prompted for specifications, complete the fields
on the pop-up screen and press Enter to print.
For more information about the specifications, press HELP while the pop-up screen is displayed.
CAPI061E


CAPI061E
Error printing member.
Reason:
An error occurred while attempting to print a listing from a symbolic (PROTSYM or CSL) file.
The listing is not printed.
Action:
 1739


InterTest™ and SymDump ® 11.0
This is an internal error, contact Technical Support.
CAPI062E
Error printing report.
Reason:
An error occurred while attempting to print one of the following:
•
•The current display using a PRINT command.
•
•An entire report using a p line command from the repository index selection list.
•
The listing is not printed.
Action:
This is an internal error, contact Technical Support.
CAPI063I
<nnn> page(s) printed.
Reason:
This message is displayed in response to a successful PRINT request. < nnn> indicates the number of pages printed from
the current display.
The number of pages is determined by the number of lines printed and the number of lines per page requested.
Action:
This is an informational message, no action is required.
CAPI064I
Print was successful.
Reason:
This message is displayed in response to a successful p line command. The selected report or symbolic listing was
printed.
Action:
This is an informational message, no action is required.
CAPI066I
Profile updated.
Reason:
You have successfully completed a PROFILE command or option 5 of the SYM command: Dynamic Symbolic Support for
Endevor . Your profile variables have been updated.
Action:
This is an informational message, no action is required.
CAPI067I
Profile update cancelled.
Reason:
You pressed END to exit either the PROFILE dialog or the Dynamic Symbolic Support Options window (option 5 of the
SYM command). Your profile variables were not updated.
Action:
 1740


InterTest™ and SymDump ® 11.0
This is an informational message, no action is required.
If you intended to update the profile, repeat the command. When you have set all of the variables as desired, press Enter
to exit the dialog and update your profile with the new settings.
CAPI070W
No program name specified.
Reason:
You entered a VIEW primary command but failed to specify which program name you wanted to view.
Action:
No listing is displayed for viewing. Enter HELP VIEW  for more information about the VIEW command.
CAPI071W
Symbolic information not found in report.
Reason:
You entered a VIEW primary command but no symbolic information was found in the report for the specified program.
Action:
No listing is displayed for viewing.
Check that the program name was spelled correctly, and that symbolic information was used for the program when the
report was formatted.
You may need to add the program listing to a symbolic file, or add the symbolic file to your global or supplemental
symbolic file list.
Enter HELP VIEW  for more information about the VIEW command.
CAPI074W
Member not found.
Reason:
You entered a SELECT primary command but the member you selected was not found in the member list.
Action:
No listing is displayed for viewing. Check that the program name was spelled correctly, and that the member actually
exists in the symbolic file.
CAPI075W
No program name specified
Reason:
You entered a SELECT primary command but did not specify the name of the program you would like to select for
viewing.
Action:
No listing is displayed for viewing. Enter the command again with a valid program name argument.
CAPI075W0
Dynalloc failed for <ddname>, rc=<nn>, reason=<nnn>
Reason:


Dynalloc failed for <ddname>, rc=<nn>, reason=<nnn>
Reason:
A dynamic allocation failure occurred. The ddname and return codes from SVC 99 are displayed in the text of the
message.
Action:
Evaluate the return codes from SVC 99 (dynalloc) to determine the cause of the failure.
 1741


InterTest™ and SymDump ® 11.0
This error is often caused by a pre-existing allocation for the same ddname. If this is the case, free the allocation and try
again.
If you cannot determine the cause of this error, contact Technical Support.
CAPI098E
Error initializing repository API, rc=nnn.
Reason:
An internal error was detected while attempting to initialize the repository API.
This may indicate one of the following conditions:
•
•Insufficient storage was available to load the API modules.
•
•One or more API modules could not be located.
•
•The license management program was not available.
•
Action:
Verify that your session has a sufficient region size, that your product libraries have been made available by LIBDEF or
through linklist, and that the Common Components and Services  has been properly installed.
If you are still unable to determine the cause of this error, contact Technical Support.
CAPI099E
Error initializing symbolic API, rc=nnn.
Reason:
An internal error was detected while attempting to initialize the symbolic API.
This may indicate one of the following conditions:
•
•Insufficient storage was available to load the API modules.
•
•One or more API modules could not be located.
•
Action:
Verify that your session has a sufficient region size, and that your product libraries have been made available by LIBDEF
or through linklist.
If you are still unable to determine the cause of this error, contact Technical Support.
CAPI100I
Repository contains <nnn> report(s).
Reason:
This message appears whenever the repository index selection list is initially displayed or updated.
This occurs when you:
 1742


InterTest™ and SymDump ® 11.0
•
•Start a new viewer session.
•
•Use the REFRESH command to update the contents of the list.
•
•Use the SETINDEX command to select a new repository.
•
<nnn> indicates the number of reports in the repository, each of which appears in the selection list, sorted in descending
order by date.
Action:
This is an informational message, no action is required.
CAPI101W
Help file DD is not allocated.
Reason:
A HELP command was entered but the CAOIHELP DD statement is not properly allocated. Help cannot be displayed.
Action:
Allocate CAI.CAVHHELP using DDNAME CAOIHELP and restart the viewer.
CAPI102E
Error reading help file.
Reason:
A HELP command was entered but the CAOIHELP DD statement does not point to the CAI.CAVHHELP data set.
Action:
Free and reallocate CAOIHELP to point to CAI.CAVHHELP, then restart the viewer.
CAPI103W
Help not available for <topic>.
Reason:
A HELP command was entered with an explicitly defined topic name, but no help member was found for that topic.
Action:
Try one of the following HELP topics:
•
•HELP ALL lists all available help topics.
•
•HELP MSG lists help topics for Broadcom  messages.
•
•HELP SCREENS list help topics for viewer screens.
•
•HELP COMMANDS list help topics for viewer commands.
•
CAPI108W
Selected entry cannot be <action>.
Reason:
 1743


InterTest™ and SymDump ® 11.0
You have selected an item from the report tree selection list for an expand, collapse, toggle, or explode action.
The item that you selected has no subordinate items, so the action cannot be performed.
Items that can be expanded, collapsed, or exploded are indicated by + or - in the area between the line number and item
description, as follows:
•+ indicates that an item has subordinate items which are not visible, and therefore the item can be expanded or
exploded. Use + or / to expand the item or ! to explode it.
•- indicates that an item has subordinate items which are already visible, and therefore the item can be collapsed. Use -
or / to collapse it.
NOTE
An expanded item indicated by - can also be exploded using ! if any of its subordinate items have the + indicator.
Action:
Select a different item or use a different line command.
CAPI109W
Selected entry is already <expanded|collapsed>.
Reason:
You have selected an item from the report tree selection list for an expand + or collapse - action.
The item that you selected was already expanded or collapsed, so your action cannot be performed.
Items which can be expanded, collapsed, or exploded are indicated by + or - in the area between the line number and
item description, as follows:
•+ indicates that an item has subordinate items which are not visible, and therefore the item can be expanded or
exploded. Use + or / to expand the item or ! to explode it.
•- indicates that an item has subordinate items which are already visible, and therefore the item can be collapsed. Use -
or / to collapse it.
NOTE
An expanded item indicated by - can also be exploded using ! if any of its subordinate items have the + indicator.
Action:


Action:
Select a different item or use a different line command.
CAPI111E
Error deleting report.
Reason:
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.
CAPI112W
Report is locked and cannot be deleted.
Reason:
You attempted to delete a report from your repository, but the report has been locked and cannot be deleted.
Action:
The user owning the lock is displayed in the Lock field of the repository index selection list. Contact this user to determine
if the report is still needed. If not, use the u line command to unlock the report.
 1744


InterTest™ and SymDump ® 11.0
CAPI118E
Access denied, request=<nn>, rc=<nn>.
Reason:
You attempted to access the contents of a repository, but access was denied by your system administrator.
The request types are:
•
•5 - Open a report for viewing
•
•9 - Delete a report from the repository
•
•16 - Lock a report to prevent accidental deletion
•
•17 - Unlock a report to allow deletion
•
•21 - Update report options
•
•22 - Print a report
•
The return codes are defined by your system administrator in the custom security exit.
Action:
Contact your system administrator.
CAPI120W
Report is already locked.
Reason:
You attempted to lock a report using an l line command, but the report was already locked.
Action:
The user owning the lock is displayed in the Lock field of the repository index selection list. Contact this user to determine
if the lock is still needed. If not, ask the user to unlock the report, then try again.
CAPI121E
Lock error, rc=<nnn>.
Reason:
An error occurred while you were attempting to lock a report. The report was not locked.
Action:
This usually indicates that the report was locked or deleted by another job or user after your repository index selection list
was initially displayed.
Use the REFRESH command to update the contents of the repository index selection list. If the report still appears in the
list, and the report has not been locked by another user, this may indicate an internal error. Contact Broadcom Support .
CAPI122I
Report has been locked.
Reason:
A report was successfully locked in your repository in response to an l line command from the repository index selection
list.
Action:
 1745


InterTest™ and SymDump ® 11.0
This is an informational message, no action is required.
CAPI123W
Report is not locked.
Reason:
You attempted to unlock a report using a u line command, but the report was not locked.
Action:
This is a user error, the report cannot be unlocked.
CAPI124E
Unlock error, rc=<nnn>.
Reason:
An error occurred while you were attempting to unlock a report. The report was not unlocked.
Action:
This usually indicates that the report was unlocked or deleted by another job or user after your repository index selection
list was initially displayed.
Use the REFRESH command to update the contents of the repository index selection list. If the report still appears in the
list, and the report is still locked, this may indicate an internal error. Contact Broadcom Support .
CAPI125I
Report has been unlocked.
Reason:
A report was successfully unlocked in your repository in response to a u line command from the repository index selection
list.
Action:
This is an informational message, no action is required.
CAPI140E
Invalid value for <option>, specify <value-type>.
Reason:
You entered an invalid value for a report option.
The name of the option for which the error was detected and the correct value type for that option are both identified in the
text of the message.
Action:
Enter HELP RPTOPTS to list all of the options and their possible values. Correct the value for the option and press Enter
to validate it.
CAPI141E
Internal Error.
Reason:
An internal error was detected while you were attempting to update report options.
Action:
Contact Broadcom Support .
CAPI145E
Dynalloc failed for <ddname>, rc=<nn>, reason=<nnn>.
 1746


InterTest™ and SymDump ® 11.0
Reason:
A dynamic allocation failure occurred while you were attempting to display your system installation options using an
OPTIONS command.
The ddname and return codes from SVC 99 are displayed in the text of the message.
Action:
Evaluate the return codes from SVC 99 (dynalloc) to determine the cause of the failure.
This error is often caused by a pre-existing allocation for the same ddname. If this is the case, free the allocation and try
again.
If you cannot determine the cause of this error, contact Technical Support.
CAPI146E
Error writing report, rc=<nnn>.
Reason:
An error occurred while you were attempting to display the system installation options.
The return code from the options program CAOUOPTS is included in the text of the message.
Action:
For more information, execute CAOUOPTS in batch using the sample JCL provided in CAI.CAVHJCL or the following JCL
model:
// JOB
//STEP1    EXEC PGM=CAOUOPTS //STEPLIB  DD DSN=CAI.CAVHLOAD,DISP=SHR//SYSPRINT DD SYSOUT=*
If the return code in batch matches the return code from this message, review the job output for information related to the
error.
If you cannot determine the cause of this error, contact Technical Support.
CAPI147E
Error opening report.
Reason:
An error occurred while you were attempting to display the system installation options.
The output from CAOUOPTS containing your installation options could not be opened.
Action:
This probably indicates an internal error.
To view your options, execute CAOUOPTS in batch using the sample JCL provided in CAI.CAVHJCL or the following JCL
model:
// JOB


model:
// JOB
//STEP1    EXEC PGM=CAOUOPTS//STEPLIB DD DSN=CAI.CAVHLOAD,DISP=SHR
//SYSPRINT DD SYSOUT=*
If this problem persists, contact Technical Support.
CAPI199E
License Management not installed.
Reason:
The license management component of Common Components and Services  was not properly installed.
Action:
Contact Broadcom Support .
CAPI201E
Dynalloc failed for <ddname>, rc=<nn>, reason=<nnn>.
Reason:
 1747


InterTest™ and SymDump ® 11.0
A dynamic allocation failure occurred while you were executing the symbolic utilities using a SYM command.
The ddname and return codes from SVC 99 are displayed in the text of the message.
Action:
Evaluate the return codes from SVC 99 (dynalloc) to determine the cause of the failure.
This error is often caused by a pre-existing allocation for the same ddname. If this is the case, free the allocation and try
again.
If you cannot determine the cause of this error, contact Technical Support.
CAPI202E
Invalid symbolic file.
Reason:
The data set you have entered as a symbolic file is not a valid PROTSYM or CSL file.
Action:
Correct the data set name and try again.
If you cannot determine the cause of this error, contact Technical Support.
CAPI203E
Symbolic API error, func=<name>, rc=<nnn>.
Reason:
An error occurred while attempting to execute a symbolic utility using a SYM command.
The function name and return code are provided in the text of this message to assist Broadcom Support  with the problem
determination.
Action:
For some function types, this may be caused by an invalid symbolic file. Verify that your symbolic file name is correct.
If you still cannot determine the cause of this error, contact Technical Support.
CAPI204E
Error retrieving CSL directory, rc=<nnn>.
Reason:
An error occurred while attempting to display a list of members for a CSL file.
The return code from program CAOUCSLD is included in the text of this message.
Action:
For more information, execute CAOUCSLD in batch using the sample JCL provided in CAI.CAVHJCL or the following JCL
model:
// JOB


model:
// JOB
//STEP1    EXEC PGM=CAOUCSLD//STEPLIB DD DSN=CAI.CAVHLOAD,DISP=SHR// DD
DSN=CAI.CAVHLOAD,DISP=SHR//CAISYM   DD DSN=your.csl.dsn,DISP=SHR//SYSPRINT DD SYSOUT=*
•
•Note that your installation may use an alternate name for CAISYM.
If the return code in batch matches the return code from this message, review the job output for information related to
the error.
If you cannot determine the cause of this error, contact Technical Support.
•
CAPI205E
Open failed for <ddname>.
Reason:
 1748


InterTest™ and SymDump ® 11.0
An error occurred while attempting to execute a symbolic utility using the SYM command.
A file required by the utility could not be opened.
The ddname identifying the file is included in the text of the message.
Action:
Contact Broadcom Support .
CAPI206E
Error printing CSL member, rc=<nnn>.
Reason:
An error occurred while attempting to display a listing for a CSL member.
The return code from program CAORMAIN is included in the text of this message.
Action:
For more information, execute CAORMAIN in batch using the sample JCL provided in CAI.CAVHJCL or the following JCL
model:
// JOB
//STEP1    EXEC PGM=CAORMAIN//STEPLIB DD DSN=CAI.CAVHLOAD,DISP=SHR
// DD DSN=CAI.CAVHLOAD,DISP=SHR//CAISYM   DD DSN=your.csl.dsn,DISP=SHR//CAIPRINT DD SYSOUT=//
CAIPRNT1 DD SYSOUT= //CAIPRNT2 DD SYSOUT= //CAIOPTS  DD   PRINTCSL member-name/*
•
•Note that your installation may use alternate names for CAISYM, CAIPRINT, CAIPRNT1, CAIPRNT2, and CAIOPTS.
If the return code in batch matches the return code from this message, review the job output for information related to
the error.
If you cannot determine the cause of this error, contact Technical Support.
•
CAPI207I
Member <name> deleted from <dsname>.
Reason:
This message is displayed in response to a successful deletion of a symbolic file member.


Reason:
This message is displayed in response to a successful deletion of a symbolic file member.
The member name and symbolic file dsname are both identified in the text of the message.
Action:
This is an informational message, no action is required.
CAPI208E
Error deleting member.
Reason:
An error occurred while attempting to delete a symbolic file member. The member could not be deleted.
Action:
This problem can occur if the member was already deleted by another job or user after your member selection list was
displayed.
If you are deleting from a PROTSYM file, verify that the delete password was entered correctly.
If you still cannot determine the cause of this error, contact Technical Support.
CAPI209W
CA SymDump not available on this system as set in CAVHCONF
Reason:
 1749


InterTest™ and SymDump ® 11.0
The CAVHCONF configuration module, which is loaded into the CSA, indicates that the product is not intended to be used
on this system.
Action:
Contact your systems programmer to ensure that the CAVHCONF configuration macro was implemented correctly on this
system and that the CAVHINIT process was run.
CAPI210E
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.
CAPR312W
NO SYMBOLIC INFORMATION FOUND FOR PROGRAM "PPPPPPPP".
Reason:
Symbolic information was requested for a program but no information was found in any of the available PROTSYM or CSL
files.
Missing symbolic information usually results in termination of the requested report generation.
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 in your installation defaults, your JCL, or a SYMDSN override.
If you still cannot determine the cause of this message, contact Technical Support.
CAPR313E
ERROR SEARCHING SYMBOLIC FILE DIRECTORY.
Reason:
Possible internal error.
Action:
Save all output materials and contact Technical Support.
CAPR318E
ERROR READING SYMBOLIC INFORMATION FOR PROGRAM <PPPPPPPP>.
Reason:
Possible internal error.
Action:
Save all output materials and contact Technical Support.
CAPR321E
CSECT xxxxxxxx SYMBOLIC INFORMATION IS INCOMPLETE.
Reason:
The symbolic information for CSECT xxxxxxxx  is incomplete.
Action:
 1750


InterTest™ and SymDump ® 11.0
Reload the program listing into the symbolic file. If the program was CAoptimized, recompile/optimize the program using
the SYM option to update your PROTSYM file, then relink the program and ensure that the updated PROTSYM file is
available. If the program was not CAoptimized, reload the listing using the appropriate postprocessor.
If you still cannot determine the cause of this message, contact Technical Support.
CAPR322E
CSECT xxxxxxxx SYMBOLIC INFORMATION CONTAINS NO LISTING DATA.
Reason:
An unexpected end of file was detected while reading the symbolic information for CSECT xxxxxxxx .
Action:
Reload the program listing into the symbolic file. If the program was CAoptimized, recompile/optimize the program using
the SYM option to update your PROTSYM file, then relink the program and ensure that the updated PROTSYM file is
available. If the program was not CAoptimized, reload the listing using the appropriate postprocessor.
If you still cannot determine the cause of this message, contact Technical Support.
CAPR323E
CSECT xxxxxxxx SYMBOLIC INFORMATION CONTAINS ERRORS.
Reason:
An error was detected while reading the symbolic information for CSECT xxxxxxxx .
Action:
Reload the program listing into the symbolic file. If the program was CAoptimized, recompile/optimize the program using
the SYM option to update your PROTSYM file, then relink the program and ensure that the updated PROTSYM file is
available. If the program was not CAoptimized, reload the listing using the appropriate postprocessor.
If you still cannot determine the cause of this message, contact Technical Support.
CAPR327W
CSECT xxxxxxxx IS AN INVALID CSECT NAME AND HAS BEEN IGNORED.
Reason:


Reason:
An invalid CSECT name was encountered during input options processing.
Action:
Correct the invalid CSECT name and rerun the job.
If you still cannot determine the cause of this message, contact Technical Support.
CAPR333W
TIMSV FILE FOR JOB xxxxxxxx IS INCOMPLETE.
Reason:
Not all of the expected timing measurement information appears in the CAITIMSV.
Action:
Check the execution step for any abnormal completions, and rerun the job. Contact Broadcom Support  for assistance.
CAPR334E
INTERNAL ERROR CONDITION DETECTED. CONTACT CA.
Reason:
A serious internal error occurred during processing of the COBOL program. Processing of the COBOL program
terminates. Diagnostic information for use by Broadcom Support  personnel is displayed. The job step abends.
Action:
Retain all JCL and listings and contact Technical Support for assistance.
 1751


InterTest™ and SymDump ® 11.0
CAPR338E
INTERNAL ERROR CONDITION DETECTED. CONTACT CA.
Reason:
A serious internal error occurred during processing of the COBOL program. Processing of the COBOL program
terminates. Diagnostic information for use by Broadcom Support  personnel is displayed. The job step abends.
Action:
Retain all JCL and listings and contact Technical Support for assistance.
CAPR339E
MAXIMUM WORKSPACE EXCEEDED. CANNOT PROCESS REQUESTED QUANTITY OF INPUT/OUTPUT.
Reason:
The internal sort routine ran out of space. The allowable maximum working space has been exceeded.
Action:
Rerun the job with fewer report requests.
CAPR340E
WORKSPACE EXCEEDED. PLEASE INCREASE REGION BY UP TO xxxx K.
Reason:
The internal sort routine ran out of space.
Action:
Increase the region size, or reduce the number of reports requested.
CAPR436E
INTERNAL ERROR CONDITION DETECTED. CONTACT CA.
Reason:
A serious internal error occurred during processing of the COBOL program. Processing of the COBOL program
terminates. Diagnostic information to be used by Broadcom Support  personnel is displayed. The job step abends.
Action:
Retain all JCL and listings and contact Technical Support for assistance.
CAPR441W
xxxxxxxx MUST PRECEDE yyyyyyyy, FOUND zzzzzzzz. yyyyyyyy IS IGNORED.
Reason:
An input statement was ignored because the expected xxxxxxxx  was not found.
Action:
Review the edited input. Rerun the job with the correct input if necessary.
CAPR442W
xxxxxxxxxxxxxxxxxxx IS NOT RECOGNIZED AND WILL BE IGNORED.
Reason:
An input string was not recognized and will be ignored.
Action:


Reason:
An input string was not recognized and will be ignored.
Action:
Review the edited input. Rerun the job with the correct input if necessary.
 1752


InterTest™ and SymDump ® 11.0
CAPR443W
OPTS FILE IS EMPTY OR OMITTED – DEFAULT VALUES ASSUMED.
Reason:
The input parameter file has no data. The default values are used.
Action:
Review the default values. Rerun the job if necessary.
CAPR444W
BLANKS ARE ILLEGAL WITHIN A SUBLIST. SUBLIST HAS BEEN TERMINATED IN ERROR.
Reason:
A blank was found in a parentheses-enclosed list. The sublist was terminated by replacing the first blank with a right
parenthesis. Any remaining data is ignored.
Action:
Review the edited input. Rerun the job with the correct input if necessary.
CAPR445W
CARD ENDED WITHOUT TERMINAL QUOTE. ONE IS ASSUMED.
Reason:
Character strings are not permitted to extend across statements. A beginning quote was found without a corresponding
ending quote. An ending quote was supplied in column 73.
Action:
Review the edited input. Rerun the job with the correct input if necessary.
CAPR446W
RIGHT PARENTHESES ARE ILLEGAL EXCEPT TO TERMINATE A SUBLIST.
Reason:
A right parenthesis was found without a corresponding left parenthesis. The right parenthesis was ignored.
Action:
Review the edited input. Rerun the job with the correct input if necessary.
CAPR447W
LEFT PARENTHESES ARE ILLEGAL EXCEPT TO START A SUBLIST.
Reason:
A left parenthesis was found within a sublist. Multiple levels of parentheses are not allowed. The left parenthesis is
ignored.
Action:
Review the edited input. Rerun the job with the correct input if necessary.
CAPR448W
IMPROPER USAGE OF RESERVED WORD xxxxxxxx, WILL BE REJECTED.
Reason:


IMPROPER USAGE OF RESERVED WORD xxxxxxxx, WILL BE REJECTED.
Reason:
xxxxxxxx  is used in the wrong context or follows an error in a preceding keyword. xxxxxxxx  is ignored.
Action:
Review the edited input. Rerun the job with the correct input if necessary.
 1753


InterTest™ and SymDump ® 11.0
CAPR449W
xxxxxxxx INVALID OPERAND FOR yyyyyyyy, KEYWORD REJECTED.
Reason:
xxxxxxxx  is not a valid subparameter of keyword yyyyyyyy . The keyword is rejected.
Action:
Review the edited input. Rerun the job with the correct input if necessary.
CAPR450W
xxxxxxxx REQUIRES yyyyyyyy, FOUND zzzzzzzz. KEYWORD IGNORED.
Reason:
The keyword xxxxxxxx  is ignored because the expected yyyyyyyy  was not found.
Action:
Review the edited input. Rerun the job with the correct input if necessary.
CAPR451W
SUBLIST LIMIT OF kkkkkkkk (nnnn) HAS BEEN EXCEEDED. EXCESSIVE ENTRIES WILL BE IGNORED.
Reason:
Keyword kkkkkkkk  has a maximum of nnn subparameters and that number was exceeded. Excess entries are ignored.
Action:
Review the edited input. Rerun the job with the correct input if necessary.
CAPR452W
xxxxxxxx TOO LONG FOR yyyyyyyy. KEYWORD REJECTED.
Reason:
xxxxxxxx  is too long for keyword yyyyyyyy . The keyword is rejected.
Action:
Review the edited input. Rerun the job with the correct input if necessary.
CAPR453W
xxxxxxxx TOO LONG FOR yyyyyyyy. VALUE TRUNCATED.
Reason:
Value xxxxxxxx  is too long for keyword yyyyyyyy . Value xxxxxxxx  is truncated to the correct length.
Action:
Review the edited input. Rerun the job with the correct input if necessary.
CAPR499E
INTERNAL ERROR CONDITION DETECTED. CONTACT CA.
Reason:


CAPR499E
INTERNAL ERROR CONDITION DETECTED. CONTACT CA.
Reason:
A serious internal error occurred during processing of the COBOL program. Processing of the COBOL program
terminates. Diagnostic information is displayed for Broadcom Support  personnel. The job step abends.
Action:
Retain all JCL and listings and contact Technical Support for assistance.
CAPU001E
SYSPRINT DD STATEMENT MISSING OR INVALID.
 1754


InterTest™ and SymDump ® 11.0
Reason:
The SYSPRINT DD statement was not specified correctly.
Action:
Correct the SYSPRINT DD statement in the JCL and rerun the job.
CAPU002E
LIBRARY DD STATEMENT MISSING.
Reason:
The library DD statement was not specified.
Action:
Correct the library DD statement in the JCL and rerun the job.
CAPU003E
LIBRARY NOT DIRECT ACCESS.
Reason:
The library data set does not reside on direct access volume. The library cannot be processed by CAOUMRS.
Action:
Correct the data set name in the JCL or move this library to a direct access volume.
CAPU004E
LIBRARY DD STATEMENT INVALID.
Reason:
The library data set was not specified correctly.
Action:
Correct the library data set in the JCL and rerun the job.
CAPU005E
LIBRARY HAS AN INVALID VOLUME SEQUENCE NUMBER.
Reason:
The library data set resides on multiple volumes and cannot be processed by CAOUMRS.
Action:
Check the JCL to ensure it points to the correct library.
CAPU006E
LIBRARY NOT A PARTITIONED DATASET.
Reason:
The library is not a partitioned data set and cannot be processed by CAOUMRS.
Action:
Check the JCL to ensure it points to the correct library.
CAPU007E
LIBRARY DATASET HAS AN INVALID RECFM.
Reason:
The library data set is not a valid load library and cannot be processed by CAOUMRS.
Action:
Check the JCL to ensure it points at the correct library.
 1755


InterTest™ and SymDump ® 11.0
CAPU008E
UNABLE TO READ LIBRARY DICTIONARY.
Reason:
An I/O error occurred while attempting to read the library directory. The directory may be damaged.
Action:
Check the directory to ensure it contains valid data. Correct or restore the library and rerun the job.
CAPU009E
UNABLE TO READ LIBRARY MEMBER: XXXXXXXX.
Reason:
An I/O error occurred while attempting to read a library member. The member may be damaged.
Action:
Check the member to ensure it contains valid data. Correct or restore the library member and rerun the job.
CAPU010E
UNEXPECTED END OF FILE PROCESSING MEMBER: XXXXXXXX.
Reason:
The load module text information is incomplete. A member may be damaged.
Action:
Check the member to ensure it contains valid data. Correct or restore the member and rerun the job.
CAPU011W
MAXCSECT WAS EXCEEDED PROCESSING MEMBER XXXXXXXX.
Reason:
The load module being processed has more than 512 CSECTs.
Action:
Pass PARM='MAXCSECT=nnnn ' on the exec card when invoking MRS to increase the value of MAXCSECT, where nnnn
is the maximum number of CSECTs to be processed for a load module.
CAPU012W
BINDER ERROR PROCESSING xxxxxxxx FUNCTION. RC= xx REASON= xxxxxxxx
Reason:
The BINDER encountered an error during function xxxxxxxx .
Action:
Check to ensure that all members are bound/link-edited correctly. Processing continues.
CAPU013W
BINDER ERROR PROCESSING xxxxxxxx  FUNCTION FOR MODULE xxxxxxxx . RC= xx REASON= xxxxxxxx
Reason:


Reason:
The BINDER encountered an error during function xxxxxxxx.
Action:
Check to ensure that all members are bound/link-edited correctly. Processing continues.
CAPU014E
MAXIMUM SYSIN RECORDS EXCEEDED FOR CAOZAP
 1756


InterTest™ and SymDump ® 11.0
Reason:
Only 100 SYSIN records can be processed per run.
Action:
Limit the number of SYSIN records to a maximum of 100.
CAPU122E
LICENSE MANAGEMENT PROGRAM NOT INSTALLED.
Reason:
The API for the License Management Program could not be found.
Action:
This error will not cause any immediate problems. Execution continues normally; however, this message will be repeated
each time a SymDump  Batch module is executed until the License Management Program is installed correctly. For more
information, see the Common Components and Services  documentation.
CAPU301E
CAIPRINT OPEN FAILED.
Reason:
An error occurred while attempting to open the CAIPRINT file. CAIPRINT formatting ends. No CAIPRINT output is
generated.
Action:
Contact Broadcom Support .
CAPU302E
OPEN FAILED FOR CAIPRINT WORK FILE.
Reason:
An error occurred while attempting to open the CAIPRINT work file. CAIPRINT formatting ends. No CAIPRINT output is
generated.
Action:
Contact Broadcom Support .
CAPU303E
OPEN FAILED FOR CAIPRINT REPOSITORY.
Reason:
An error occurred while attempting to open the CAIPRINT repository. CAIPRINT formatting ends. No CAIPRINT output is
generated.
Action:
Contact Broadcom Support .
CAPU304E
MEMORY MANAGER INITIALIZATION FAILED.
Reason:
An internal error was detected while formatting an Abend report.
Action:
Save all materials and contact Technical Support.
 1757


InterTest™ and SymDump ® 11.0
CAPU305E
MEMORY MANAGER PUT FAILED.
Reason:
An internal error was detected while formatting an Abend report.
Action:
Save all materials and contact Technical Support.
CAPU306E
MEMORY MANAGER GET FAILED.
Reason:
An internal error was detected while formatting an Abend report.
Action:
Save all materials and contact Technical Support.
CAPU308I
SYMBOLIC INFORMATION AUTO POPULATED TO dsn.
Reason:
Symbolic information for the program name in the program box was automatically populated by the Endevor  dynamic
symbolic support feature to the PROTSYM data set named dsn.
Action:
None. Informational only.
CAPU309E
SYMBOLIC FOR PROGRAM pgm  NOT POPULATED. DYNAMIC SYMBOLIC SUPPORT ERROR. RC=xxxx ,
RSC= yyyy
Reason:
Symbolic information for the pgm named in the program box was NOT populated due to an error encountered by the
Endevor  dynamic symbolic support feature. Return code from DSS is xxxx. Reason code from DSS is yyyy.
The following table provides a list of possible return codes (RC) and reason codes (RSC) the API and various components
may return.
NOTE
Other numeric return codes and reason codes are also returned by Endevor  and z/OS binder services API
(IEWBIND). For more information, see the respective articles.
Function RC RSC Meaning
API 00 0 Operations completed
successfully.
Endevor 12 0 1. Incorrect C1DEFLTS used.
2. Listing data set referenced by
the footprint is not cataloged.
3. For more information see
the SYSOUT containing the
Endevor  API execution report.


the SYSOUT containing the
Endevor  API execution report.
Endevor 32 15 Endevor  encountered critical
error and cannot continue.
 1758


InterTest™ and SymDump ® 11.0
Any function Any four digit code CCI The CAICCI component
encountered an error
communicating with the list
server (INTNDVRx). See
appropriate CCI documents for
details.
Any function Any four digit code CDRV One of the components
(Broadcom  Testing and Fault
Management) used by the list
server interface encountered
an error. Examine SYSOUT
data sets from the started task
INTNDVRx for appropriate
component error logs and
solutions.
NDSB 04 NDSB Compressed footprint in IDRU
invalid.
API 02 NDVR GETMAIN failed.
API 08 NDVR Endevor  server not activated.
API 12 NDVR Invalid or missing parameter
in NDVRCOMM. Listing data
set not found. See Endevor
Message and Response file.
API 16 NDVR Bad return code from Endevor .
See Endevor  documentation.
API 20 NDVR Data set open failed.
API 28 NDVR Allocation error. See SRVPRINT
file.
API 32 NDVR IN25DALC load failed.
API 36 NDVR ENA$NDVR load failed.
API 40 NDVR Endevor  footprint not found for
requested element.
API 44 NDVR Requested CSECT not found.
API 48 NDVR IN25CDRV load failed.
NSRV 08 NSRV Listing server abort or failed.
NIDR 02 XIDR GETMAIN failed.
NIDR 08 XIDR PARM error.
NIDR 20 XIDR CAOUXDSB load failed.
NIDR 2C XIDR No IDRU found for CSECT in


NIDR 2C XIDR No IDRU found for CSECT in
NDVR_NAM2 or NDVR_ELEM.
CSVQ 30 XIDR CSECT from IDRU does not
match CSECT in NDVR_NAM2.
BINDER 44 XIDR Requested CSECT not found by
binder.
Action:
Appropriate action should be taken based on the return and reason code.
 1759


InterTest™ and SymDump ® 11.0
CAPU310W
CAOFSYMP – LOAD OF CAODNDVR FAILED.
Reason:
Dynamic symbolic support encountered an error loading module CAODNDVR.
Dynamic symbolic support will not be able to populate the symbolic file.
Action:
Ensure that the SymDump  Batch product load module libraries are correctly defined in your JCL or are defined in your
installation's LNKLST.
CAPU311W
NO FOOTPRINT WAS FOUND FOR PROGRAM XXXXXXXX. .
Reason:
Program XXXXXXXX  does not have the required Endevor  footprint.
Dynamic symbolic support is unable to populate the symbolic file for the indicated program.
Action:
Ensure that the indicated program is under Endevor  control and that the associated load modules were generated using
the Endevor  Generate facility.
For more information, see Dynamic Symbolic Support For Endevor  in Symbolic Support.
CAPU312I
END OF DATA ENCOUNTERED BEFORE END OF MAP. SOME VARIABLES MAY NOT BE DISPLAYED.
Reason:
The storage associated with a data area is shorter than the map of the area in the symbolic file member. This can occur in
the following instances:
•The current record for a variable-length file is shorter than the maximum length defined in the File Section of a COBOL
program.
•The BLLMAX value is smaller than the length of an 01 item in the Linkage Section of a COBOL program.
•The REGMAX value is smaller than the length of a DSECT definition for which there is an active USING in an
Assembler program.
•The symbolic file member does not exactly match the program in the executable load module, as indicated by a
CAPD113W message.
Any variables that map to data beyond the end of the available storage will not be displayed.


Any variables that map to data beyond the end of the available storage will not be displayed.
Action:
No action is required. However, the message may be eliminated if it was not caused by a short record in a variable-length
file using one of the following methods:
•If the message is displayed because the BLLMAX value is smaller than the length of an 01 item in the Linkage Section
of a COBOL program, specify a larger BLLMAX value and rerun the job.
•If the message is displayed because the REGMAX value is smaller than the length of a DSECT definition for which
there is an active USING in an Assembler program, specify a larger REGMAX value and rerun the job.
•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.

CAPU313E
OFFSET DOES NOT CORRESPOND TO A STATEMENT WITHIN THE PROGRAM.
Reason:
 1760


InterTest™ and SymDump ® 11.0
The indicated program offset does not correspond to a source statement in the program. A source statement could not be
found.
Action:
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. Otherwise, contact Technical Support.
CAPU399E
INTERNAL ERROR. CAIPRINT FORMATTER IN CONTROL.
Reason:
The error recovery mechanisms (for example, ESTAE exits) of the CAIPRINT Formatter have encountered an unexpected
and unrecoverable abend. The most likely event is an unexpected OCx abend.
This could be traceable to an invalid control block, product logic error, or user error. A few data elements related to the
abend are captured and an attempt is made to relate the abending PSW address to an offset within a named module.
The abend code (for example, OC4) and the registers at abend, along with other pertinent information, are written to
CAIPRINT and a dump is produced.
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 SDWA in the RTM2WA SUMMARY chain that matches the abend code and registers
displayed on CAIPRINT.
CAPU400I
THE FOLLOWING EXPIRED REPORTS WILL BE DELETED:
Reason:
While adding an Abend report to the repository, one or more reports were found that exceeded the expiration limit
established for your installation by the EXPDAYS option in CAOUDFRX. These reports were deleted.
Action:


Action:
No action is required. However, to prevent this message and the automatic deletion of abend reports from your repository,
set the EXPDAYS option to zero.
CAPU401I
J=jjjjjjjj,S=ssssssss,P=pppppppp,O=oooooo,ccccc.
Reason:
This informational message appears once for each report that was automatically deleted due to expiration. The job name,
system name, program name, offset, and completion code are used to identify the message.
Action:
No action is required. However, to prevent this message and the automatic deletion of abend reports from your repository,
set the EXPDAYS option to zero.
CAPU402I
AUTO-MAINTENANCE COMPLETED.
Reason:
This message is written after all abend reports in your repository have been tested for expiration, only if reports were
actually deleted during the process.
Action:
No action is required.
 1761


InterTest™ and SymDump ® 11.0
CAPU502E
RUN TIME DEFAULTS CSECT 'CAOUDFRX' NOT FOUND. REPORTING TERMINATED.
Reason:
The options reporting program was unable to find the runtime default options member, CAOUDFRX. Options reporting
was terminated.
Action:
Verify that the library containing the runtime options member, CAOUDFRX, is available to the options reporting program in
LINKLIST or LPA, or was specified in the JCL in STEPLIB or JOBLIB.
CAPU307E
Record Error. Special Record Expected But Not Found.
Reason:
An internal error was detected while formatting an Abend report.
Action:
Save all materials and contact Technical Support.
CAPHC001I
The CA SymDump Batch repository file prtlib.name is at nn.n% capacity.
SymDump  Batch is capable of capturing future abend reports to facilitate rapid problem diagnosis. This will help
ensure normal business processes complete in a timely manner.
Reason:
The SymDump  health check program CAOCHCHK has performed a check on the PRTLIB file and has found the file to be
within safe capacity levels.
Action:
No action is required.
CAPHC001W
CA SymDump Batch repository file is nearing capacity.
File prtlib.name is at nn.n% capacity.
If the repository becomes full, future abend reports will not be captured.
Reason:
The index file has met or exceeded the capacity trigger set in the CAOETABL options table parameter PRTLHCT=. The
SymDump  Batch PRTLIB file is filling up and may not have the capacity to save future abend reports.
Action:
The SymDump  Batch repository file must be maintained using utility program CAOUPRTU. Procedure CAIPRTU can be


used to execute the utility to copy or delete dump reports from the repository file to free space for future abend reports.
SymDump REST API Messages
This section defines errors, warnings, and informational messages specific to SymDump Batch REST API and SymDump
CICS REST API.
Message Format
All messages issued by SymDump BATCH REST API and by SymDump CICS REST API are in the format CAVHR<xyz >
 1762


InterTest™ and SymDump ® 11.0
 CAVHR01E
Invalid key, no corresponding report found.
Reason:
The report key provided does not exist in the requested dump repository.
Action:
Use the Reports REST API endpoint of the dump repository to extract the report key, and provide a valid key.
CAVHR03E
When you populate a non LE-enabled ASSEMBLER option,
the ndvrDSSdsn option data set name of a PROTSYM file is required.
Reason:
If the ndvrDSSasm  value set to 'Y', the non LE-enabled ASSEMBLER option is active and the ndvrDSSdsn  option is
required.
Action:
Specify the ndvrDSSdsn  option, or remove ndvrDSSasm  option from the request body.
CAVHR04E
Values to populate a non LE-enabled ASSEMBLER option are 'Y' or 'N'.
Reason:
Valid ndvrDSSasm  option values to populate a non LE-enabled ASSEMBLER option are 'Y' or 'N'.
Action:
Change the ndvrDSSasm  option to 'Y' or 'N' as appropriate.
CAVHR05E
Invalid mainframe user credentials.
Reason:
Invalid mainframe user name or password.
Action:
Provide valid mainframe user credentials.
CAVHR06E
Checked Exception with recoverable condition.
Reason:
Check the message for a reason
Action:
Check the message for actions.
CAVHR07E
<dataset name > data set not found.
Reason:
The data set that was provided does not exist.
 1763


InterTest™ and SymDump ® 11.0
Action:
Provide a valid data set name.
CAVHR08I
Delete request successful.
Reason:
A report was successfully deleted from your repository.
Action:
Informational message, no action required.
CAVHR09E
This is an exception message originating from Spring Boot.
Reason:
Check the message for a reason.
Action:
Check the message for actions.
CAVHR10I
Lock request successful.
Reason:
A report was successfully locked in your repository.
Action:
Informational message, no action required.
CAVHR11E
Report is already locked.
Reason:
You tried to lock a report that is already locked.
Action:
Contact the user who locked the report to determine if the lock is still needed. If the lock is no longer needed, ask the user
to unlock the report, then try again to lock the report.
NOTE
The user who owns the lock is displayed in the Lock  field of Report REST API endpoint.
CAVHR12I
Unlock request successful.
Reason:
A report in your repository was successfully unlocked.
Action:
Informational message, no action required.
 1764


InterTest™ and SymDump ® 11.0
CAVHR13E
Report is not locked.
Reason:
You attempted to unlock a report that is not locked. Unlocked reports cannot be unlocked
Action:
Informational message, no Action required.
CAVHR14I
Update report option is successful.
Reason:
Report options are successfully updated in the repository.
Action:
Informational message, no action required.
CAVHR15E
<option_name > value exceeds the maximum size <size>.
Reason:
The < option_name > value exceeds the maximum number of characters allowed.
Action:
Specify the ndvrDSSdsn  option, or remove ndvrDSSasm  option from the request body.
CAVHR16E
Locked report options cannot be updated.
Reason:
The requested options for the specific report are locked and cannot be updated.
Action:
Unlock the report and resend the update report options request.
CAVHR17E
Report is locked and cannot be deleted.
Reason:
The report you tried to delete is locked. You cannot delete locked reports.
Action:
Unlock and delete the report
Common Runtime Messages
The followong list shows common runtime messages
CAVH001E UNKNOWN PARM PROCESSING ERROR. INITIALIZATION PROCESSING TERMINATED
Reason:
Program CAVHINIT encountered unrecognized or mutually exclusive parameters.
 1765


InterTest™ and SymDump ® 11.0
Action:
Review the PARM() parameters on the CAIRIM control statement that invokes CAVHINIT, and correct any errors. For
more information, see Activate Your Product.
CAVH002E <table> ADD FAILED, INITIALIZATION TERMINATED
Reason:
Program CAVHINIT failed to load the specified table into CSA.
Action:
Correct any errors that could have made the table unavailable and rerun. If the problem persists, contact Broadcom
Support.
CAVH003I <table> LOADED
Reason:
Program CAVHINIT successfully loaded the specified table into CSA.
Action:
None.
CAVH004I PRODUCT INTENT: <option> OPTION <’ON’ or ‘OFF’>
Reason:
Program CAVHINIT documents the product intent option settings from table CAVHCONF. This message is issued once for
each of the product intent options: DYNAMIC, INTBAT, SYMBAT, SYMCICS, and INTCICS.
Note:  If DYNAMIC is ON, the settings for the products are set based on the availability of LMP keys.
Action:
None.
CAVH005E SBONLY AND RTLONLY MAY NOT CANNOT BOTH BE SPECIFIED
Reason:
These options are mutually exclusive.
Action:
Specify SBONLY, RTLONLY, or neither and resubmit your CAIRIM job.
CAVH006E #LPA ADD FOR CAOSBID FAILED
Reason:
CAVHINIT cannot load CAOSBID into CSA.
Action:
Verify that module CAOSBID (in yourhlq .CAVHAUTH) is available.
CAVH007E LICENSE MANAGEMENT PROGRAM NOT INSTALLED
Reason:
The CAIRIM Common Services component is not available.
Action:


Reason:
The CAIRIM Common Services component is not available.
Action:
Review the CAIRIM/CAS9 job for errors. If the cause is not obvious, Broadcom Support.
 1766


InterTest™ and SymDump ® 11.0
Dynamic Symbolic Support Messages
This section lists the messages that can be produced by the InterTest for CICS symbolic postprocessor program
IN25SYMP. These messages include a description of the internal logical problem that caused the message to be issued.
Although certain messages are duplicates, the different message codes help InterTest for CICS support personnel locate
the exact location of the error.
NOTE
DRC=n stands for a unique return code used by InterTest for CICS personnel for debugging purposes only.
CAIN5900I
mm/dd/yyyy  hh:mm:ss IN25NDVR STARTED FOR PRGNNAME – pppppppp.
Reason:
This message is issued by IN25NSRV where mm/dd/yyyy hh:mm:ss indicates the date and time when the message was
issued. This is an informational message indicating that the Listing Server is retrieving the symbolic for program named
pppppppp. This message is used to serve as a beginning bookmark for message extraction. All messages issued after
this message are extracted by message extraction service.
Action:
None.
CAIN5903E
mm/dd/yyyy  hh:mm:ss IN25NSRV CCI SPNPARM FAILED.
Reason:
This message is issued by IN25NSRV where mm/dd/yyyy hh:mm:ss indicates the date and time when the message was
issued. This error occurred when IN25NSRV issued a CCI SPNPARM request. Message CAIN5930 is usually issued in
conjunction with this message.
Action:
Examine feedback area provided in message CAIN5930 to determine the cause of the error, correct the error and do the
request again.
CAIN5903E0
mm/dd/yyyy  hh:mm:ss IN25NSRV CCI INIT FAILED.
Reason:


mm/dd/yyyy  hh:mm:ss IN25NSRV CCI INIT FAILED.
Reason:
This message is issued by IN25NSRV. where mm/dd/yyyy hh:mm:ss indicates the date and time when the message was
issued. CCI INIT action has failed. This error occurred when IN25NSRV issued a CCI INIT request. Message CAIN5930 is
usually issued in conjunction with this message.
Action:
Examine feedback area provided in message CAIN5930 to determine the cause of the error, correct the error and do the
request again.
CAIN5904I
mm/dd/yyyy  hh:mm:ss IN25NSRV WAITING FOR WORK.
Reason:
This message is issued by IN25NSRV where mm/dd/yyyy hh:mm:ss indicates the date and time when the message was
issued. This is an informational message indicating that the Listing Server is waiting for work.
Action:
None.
 1767


InterTest™ and SymDump ® 11.0
CAIN5905E
mm/dd/yyyy  hh:mm:ss IN25NSRV RECVANY FAILED.
Reason:
This message is issued by IN25NSRV where mm/dd/yyyy hh:mm:ss indicates the date and time when the message was
issued. This error occurred when IN25NSRV issued a CCI Receive Any request. Message CAIN5930 is usually issued in
conjunction with this message.
Action:
Examine feedback area provided in message CAIN5930 to determine the cause of the error, correct the error and do the
request again.
CAIN5905E0
mm/dd/yyyy  hh:mm:ss IN25NSRV RECVANY FAILED, INVALID DATA.
Reason:
This message is issued by IN25NSRV where mm/dd/yyyy hh:mm:ss indicates the date and time when the message
was issued. This error occurred when IN25NSRV issued a CCI Receive Any request and the data received are invalid.
Message CAIN5930 is usually issued in conjunction with this message.
Action:
Examine feedback area provided in message CAIN5930 to determine the cause of the error, correct the error and do the
request again.
CAIN5905E1
mm/dd/yyyy  hh:mm:ss IN25NSRV RECVANY FAILED, RECEIVED NULLS.
Reason:
This message is issued by IN25NSRV where mm/dd/yyyy hh:mm:ss indicates the date and time when the message was
issued. This error occurred when IN25NSRV issued a CCI Receive Any request and the data received contained all null
values. Message CAIN5930 is usually issued in conjunction with this message.
Action:
Examine feedback area provided in message CAIN5930 to inspect the block received. This could be the result of
transmission error. If the problem persists contact Broadcom Support .


transmission error. If the problem persists contact Broadcom Support .
CAIN5905E2
mm/dd/yyyy  hh:mm:ss IN25NSRV RECVANY FAILED, INVALID LENGTH.
Reason:
This message is issued by IN25NSRV where mm/dd/yyyy hh:mm:ss indicates the date and time when the message was
issued. This error occurred when IN25NSRV issued a CCI Receive Any request and length of the data block received was
incorrect. Message CAIN5930 is usually issued in conjunction with this message.
Action:
Examine feedback area provided in message CAIN5930 to inspect the length of data block received. This could be the
result of transmission error. If the problem persists contact Broadcom Support .
CAIN5907E
mm/dd/yyyy  hh:mm:ss IN25NSRV SENDSPEC FAILED.
Reason:
This message is issued by IN25NSRV where mm/dd/yyyy hh:mm:ss indicates the date and time when the message
was issued. This error occurred when IN25NSRV issued a CCI Send action. Message CAIN5930 is usually issued in
conjunction with this message.
Action:
 1768


InterTest™ and SymDump ® 11.0
Examine feedback area provided in message CAIN5930 to determine the reasons for the failure. This could be the result
of transmission error. If the problem persists contact Broadcom Support .
CAIN5908W
mm/dd/yyyy  hh:mm:ss IN25NSRV GETMAIN FAILED.
Reason:
This message is issued by IN25NSRV where mm/dd/yyyy hh:mm:ss indicates the date and time when the message was
issued. The message indicated that GETMAIN for 32K of main storage has failed.
Action:
Make sure that you have specified a sufficiently large region size to meet the many main storage requirements of the
Listing service.
CAIN5909I
mm/dd/yyyy  hh:mm:ss IN25NSRV REQUEST RECEIVED FOR eeeeeeee.
Reason:
This message is issued by IN25NSRV where mm/dd/yyyy hh:mm:ss indicates the date and time when the message was
issued. This is an informational message indicating that a listing request for element named eeeeeeee has been received.
Action:
None.
CAIN5913I
mm/dd/yyyy  hh:mm:ss IN25NSRV SENDING RESPONSE
Reason:
This message is issued by IN25NSRV where mm/dd/yyyy hh:mm:ss indicates the date and time when the message
was issued. This is an informational message indicating that the request by message CAIN5909 has been serviced and
response is being sent back to the remote host.
Action:
None.
CAIN5930I
mm/dd/yyyy  hh:mm:ss IN25NSRV CCI FEEDBACK: feedback info.
Reason:
This message is issued by IN25NSRV where mm/dd/yyyy hh:mm:ss indicates the date and time when the message was


issued. This is the message that is usually issued in conjunction with CCI-related error conditions. Feedback is a 256
bytes area containing CCI return codes, reason codes, and brief description associated with the error encountered.
Action:
Use the information provided in this message in conjunction with the failure message to diagnose the error.
CAIN5950I
mm/dd/yyyy  hh:mm:ss IN25NSRV SHUTDOWN.
Reason:
This message is issued by IN25NSRV where mm/dd/yyyy hh:mm:ss indicates the date and time when the message was
issued. This is an informational message indicating that the Listing server is shutting down.
Action:
None.
 1769


InterTest™ and SymDump ® 11.0
CAIN5970W
LINK TO IN25SPOL FAILED.
Reason:
This message is issued by IN25NSRV indicating that LINK to IN25SPOL has failed. Message extraction will not be
performed.
Action:
Determine that the data set containing IN25SPOL is either defined in the LINKLIST or is properly defined in the STEPLIB
concatenations.
CAIN5980E
CA SCM CRITICAL ERROR. ERROR CODE: eeee. REQUEST FOR pppppppp NOT SERVICED.
Reason:
This message is issued by IN25NSRV and is used as an end bookmark for message extraction. All messages issued
before this message are extracted by the message extraction service.
Action:
None.
CAIN5980E0
CA SCM CRITICAL ERROR. ERROR CODE: rrrr. REQUEST FOR mmmmmmmm NOT SERVICED.
Reason:
This message is issued by IN25NSRV. This indicated that Endevor  for mainframe encountered a critical error. The error
code is rrrr. Symbolic request for element named mmmmmmmm is not serviced.
Action:
Use the rrrr error code in conjunction with the SRVPRINT log and DSSLOG to determine the cause, correct the error and
redo the request.
CAIN5990I
ALLOCATION OF LOG FILE FAILED. LOGGING DISABLED.
Reason:
This message is issued by IN25FSYM, indicating that dynamic allocation for SRVPRINT DD has failed. Logging activities
is disabled. This message is usually followed by IBM IKJ5635 message providing the dynamic allocation text unit that
failed.
Action:
Determine and correct the cause for failure then retry the action.
CAIN5990I0
LINK TO IN25SPOL FAILED.


CAIN5990I0
LINK TO IN25SPOL FAILED.
Reason:
This message is issued by IN25NSRV. LINK SVC for IN25SPOL has failed. Message extraction will not be performed.
Action:
Make sure that the data set containing IN25SPOL is either defined in the LINKLIST or properly defined in the STEPLIB
DD.
CAIN5991W
HHMM DOES NOT MATCH.
Reason:
 1770


InterTest™ and SymDump ® 11.0
This message is issued by IN25FSYM. The hour and minute of the timestamp found in the symbolic does not match the
timestamp provided by the caller for the same symbolic. Requested action is not performed.
Action:
Provide the correct timestamp value and try the action again.
CAIN5995E
NO PROTSYM SEARCH LIST PROVIDED.
Reason:
This message is issued by IN25FSYM. User did not provide one or more PROTSYM data set names to perform symbolic
search. Requested action is not performed.
Action:
Provide at least one or up to a maximum of eight PROTSYM fully qualified data set names to be used for symbolic search.
CAIN6000E
DYNAMIC UNALLOCATION FAILED FOR nnnnnnnn. RC= rr. RSN= ssssssss.
Reason:
This message is issued by IN25FSYM. Dynamic allocation of data set with nnnnnnnn DD name has failed. Return code
from Dynamic Allocation is rr and the reason code is ssssssss.
Action:
Use the return code and reason code to determine the cause of the failure. Correct the error and retry the action.
CAIN6000W
DYNAMIC UNALLOCATION FAILED FOR dddddddd RC=rr. RSN=ssssssss
Reason:
This message is issued by IN25FSYM. Dynamic unallocation of dddddddd DD name has failed. The Dynamic
Unallocation return code is rr and reason code is ssssssss.
Action:
Use the return code and reason code to determine the cause of the failure. Correct the error and retry the action. If the
error persists, call Broadcom Support .
CAIN6010W
LOAD OF pppppppp FAILED. RC= rr
Reason:


LOAD OF pppppppp FAILED. RC= rr
Reason:
This message is issued by IN25FSYM. Loading of program named pppppppp has failed. The return code is rr.
Action:
Make sure that the data set containing the pppppppp program is in the LINKLIST or defined in the STEPLIB DD.
CAIN6020W
FAILED IN ROUTINE: rrrrrrrrrr RC= rr
Reason:
This message is issued by IN25FSYM. Routine named rrrrrrrr has failed with a return code of rr. This message is usually
associated with IN25SAPI and rrrrrrrr is the failed SAPI function.
Action:
Determine the error and retry the request.
 1771


InterTest™ and SymDump ® 11.0
CAIN6070E
CRITICAL ERROR LD@DSSDSN INVALID VALUE.
Reason:
This message is issued by IN25FSYM. The data set name provided in LD@DSSDSN is invalid.
Action:
LD@DSSDSN should contain a valid DD name to be used for DSS logging. It is usually specified as DSSLOG. Correct
the DD name and retry the action.
CAIN7000W
IN25NDVR MAJOR ERROR, LOG FILE NOT OPENED
Reason:
SRVPRINT log file not opened. Endevor activity log disabled.
Action:
We recommend that //SRVPRINT DD SYSOUT=* be defined in the job's JCL so that relevant error can be captured to
assist in problem analysis. This would avoid the need to recreate the error.
CAIN7010I
IN25NDVR ALLOCATION OF LOG FILE FAILED.
Reason:
Dynamic allocation of activity log has failed. This message is usually followed by IBM IKJ5635 message providing the
dynamic allocation text unit that failed.
Action:
Determine and correct the cause of the error and retry the request.
CAIN7020W
LOAD OF IN25DALC FAILED.
Reason:
IN25NDVR encountered an error trying to LOAD IN25DALC. Endevor List request will not be performed.
Action:
Make sure that the data set containing IN25DALC load module is either defined in the LINKLIST or is defined in the
STEPLIB concatenation.
CAIN7030W
LOAD OF ENA$ NDVR FAILED.
Reason:
IN25NDVR cannot LOAD the ENDEVOR API. Endevor List request will not be performed.
Action:


Action:
Make sure that Endevor AUTHLIB and CONLIB data sets are either defined in the LINKLIST or defined in the job's JCL.
CAIN8000W
JESMSGLG JCT MTTR FOUND.
Reason:
This message is issued by IN25SPOL when Broadcom Support  requested diagnostic messages. The message indicates
that MTTR of JESMSGLG JCT was found.
Action:
None.
 1772


InterTest™ and SymDump ® 11.0
CAIN8010I
JESYSMSG JCT MTTR FOUND.
Reason:
This message is issued by IN25SPOL when Broadcom Support  requested diagnostic messages. The message indicates
that MTTR of JESMSGLG JCT was found.
Action:
None.
CAIN8020I
ACQUIRED MSGLOG AND SYSMSG JCT
Reason:
This message is issued by IN25SPOL when Broadcom Support  requested diagnostic messages. This message indicates
that the JCT for JESMSGLG and JESYSMSG have been acquired.
Action:
None.
CAIN8030W
UNABLE TO ACQUIRE JCT OF EITHER JESMSGLG OR JESYSMSG.
Reason:
This message is issued by IN25SPOL when Broadcom Support  requested diagnostic messages. The message indicated
that IN25SPOL was unable to acquire the JCT of either JESMSGLG or JESYSMSG. Message extraction will not be
performed.
Action:
Contact Broadcom Support  with the information.
CAIN8040I
STIMER WAIT FOR JQE UPDATE.
Reason:
This message is issued by IN25SPOL when Broadcom Support  requested diagnostic messages. The message indicated
that IN25SPOL has issued a STIMER SVC to wait for JQE update to complete.
Action:
None.
CAIN8050I
THERE ARE NO SJQES RETURNED.
Reason:
This message is issued by IN25SPOL indicating that IEFSSREQ did not return SJQES information. Message extraction
will not be performed.
Action:
None.
CAIN8060I
THERE ARE NO SOUTS RETURNED.
Reason:


CAIN8060I
THERE ARE NO SOUTS RETURNED.
Reason:
This message is issued by IN25SPOL indicating that IEFSSREQ did not return SOUTS information. Message extraction
will not be performed.
 1773


InterTest™ and SymDump ® 11.0
Action:
None.
CAIN8070I
UNABLE TO ACCESS JOB QUEUE.
Reason:
This message is issued by IN25SPOL indicating that IEFSSREQ was unable to access JES job queue.
Action:
None.
CAIN8080I
IN25SS71 LOAD FAILED.
Reason:
This message is issued by IN25SPOL indicating that loading of IN25SS71 has failed.
Action:
Make sure that the data set containing IN25SS71 is either in the LINKLIST or the STEPLIB concatenation is properly
defined.
CAIN8090I
IN25SDSB LOAD FAILED.
Reason:
This message is issued by IN25SPOL indicating that loading of IN25SDSB has failed.
Action:
Make sure that the data set containing IN25SDSB is either in the LINKLIST or the STEPLIB concatenation is properly
defined
CAIN8091I
jjjj IS THE PRIMARY JOB ENTRY SUBSYSTEM. SYSTEM ID FROM JQRYSSID ===> iiii.
Reason:
This message is issued by IN25SPOL when Broadcom Support  requested diagnostic messages. This is an informational
message indicating that jjjj is the primary job entry subsystem whose id is iiii.
Action:
None.
CAIN8092I
dddddddd IS THE DDN OF jjjjjjjj RETURNED.
Reason:
This message is issued by IN25SPOL when Broadcom Support  requested diagnostic messages. This is an informational
message indicating dddddddd is the DD name of jjjjjjjj returned. jjjjjjjj can either be JESMSGLG or JESYSMSG.
Action:
None.
CAIN8093I
ASSOCIATED DSN: datasetname.
Reason:
 1774


InterTest™ and SymDump ® 11.0
This message is issued by IN25SPOL when Broadcom Support  requested diagnostic messages. This is an informational
message indicating that the fully qualified data set name for the DD name cited in message CAIN8092 is datasetname.
Action:
None.
CAIN8094I
JOBNAME: jobname JOBID: iiiiiiii
Reason:
This message is issued by IN25SPOL when Broadcom Support  requested diagnostic messages. This is an informational
message indicating that the active job name is jobname whose jobid is iiiiiiii.
Action:
None.
CAIN8095I
IEFSSREQ TYPE=QUERY FAILED. RETURN CODE= cccc REASON CODE= ssss
Reason:
This message is issued by IN25SPOL indicating that IEFSSREQ type of query has failed with a return code of cccc and
reason code of ssss.
Action:
Determine the cause of failure based on the return code and reason code.
CAIN8096I
IEFSSI SUBFUNCTION 80 FAILED. SSOBRETN= rrrr STATREAS= ssss.
Reason:
This message is issued by IN25SPOL indicating that IEFSSI subfunction 80 has failed. The subsystem return code is rrrr
and reason code is ssss. Message extraction will not be performed.
Action:
Contact Broadcom Support .
CAIN8097I
JESMSGLG dddddddd NOT FOUND.
Reason:
This message is issued by IN25SPOL indicating that dddddddd token for JESMSGLG is not found.
Action:
None.
CAIN8098W
POSSIBLE CHAINING ERROR. SEE REG 8 FOR DETAILS.
Reason:


POSSIBLE CHAINING ERROR. SEE REG 8 FOR DETAILS.
Reason:
This message is issued by IN25SPOL indicating that IN252POL was unable to locate SSVE control blocks via chaining
through various JES control blocks. Message extraction will not be performed. General Purpose Register 8 points to the
chain.
Action:
Contact Broadcom Support .
 1775


InterTest™ and SymDump ® 11.0
CAIN8100I
SPOOL READ FUNCTION CURRENTLY DOES NOT SUPPORT JES3 AT BELOW ZOS 01.11.01 LEVEL.
Reason:
This message is issued by IN25SPOL indicating that spool read function does not support JES3 at a level below ZOS
01.11.01 level. Message extraction will not be performed.
Action:
None.
CAIN8100I0
STARTING MSGLOG00 PROCESS.
Reason:
This message is issued by IN25SS71 when Broadcom Support  requests diagnostic messages. This is an informational
message indicating that message extraction of JESMSGLG is being started.
Action:
None.
CAIN8110I
STARTING SYSMSG00 PROCESS.
Reason:
This message is issued by IN25SS71 when Broadcom Support  requests diagnostic messages. This is an informational
message indicating that message extraction of JESYSMSG is being started.
Action:
None.
CAIN8120I
OBTAINED JCT FROM INSTOR BUFFER
Reason:
This message is issued by IN25SS71. It is an informational message indicating that JCT information was obtained from in-
storage buffer.
Action:
None.
CAIN8120I0
OBTAINED IOT FROM INSTOR BUFFER
Reason:
This message is issued by IN25SS71. This is an informational message indicating that IOT information was obtained from
in-storage buffer.
Action:
None.
CAIN8130E
INVALID REQUEST.
Reason:
This message is issued by IN25SS71. This is a should not occur error.
Action:
Contact Broadcom Support .
 1776


InterTest™ and SymDump ® 11.0
CAIN8140W
FAILED TO LOCATE PDDBS FOR BOTH JESMSGLG AND JESYSMSG.
Reason:
This message is issued by IN25SS71 indicating that it cannot locate the PDDBs for JESMSGLG and JESYSMSG.
Action:
Contact Broadcom Support .
CAIN8150I
JESMSGLG BUFR IS EMPTY
Reason:
This message is issued by IN25SS71 indicating that the JESMSGLG buffer is empty. Message extraction cannot be
performed.
Action:
None.
CAIN8160I
MSGLOG OBTAINED FROM INSTOR BUFFER
Reason:
This message is issued by IN25SS71 when Broadcom Support  requests diagnostic messages. This is an informational
message indicating that JESMSGLG messages were extracted from in-storage buffer.
Action:
None.
CAIN8170I
MSGLOG READ FROM LAST TRACK.
Reason:
This message is issued by IN25SS71 when Broadcom Support  requests diagnostic messages. This is an informational
message indicating that JESMSGLG messages were extracted from the last track specified in MTTR.
Action:
None.
CAIN8180I
MSGLOG RECORD COUNT EXHAUSTED.
Reason:
This message is issued by IN25SS71 when Broadcom Support  requests diagnostic messages. This is an informational
message indicating that JESMSGLG messages extraction has exhausted its record count.
Action:
None.
CAIN8190I
SYSMSG RECORD COUNT IS ZERO.
Reason:
This message is issued by IN25SS71 when Broadcom Support  requests diagnostic messages. This is an informational
message indicating that JESYSMSG record count is zero.
Action:
None.
 1777


InterTest™ and SymDump ® 11.0
CAIN8200I
SYSMSG OBTAINED FROM INSTOR BUFFER
Reason:
This message is issued by IN25SS71 when Broadcom Support  requests diagnostic messages. This is an informational
message indicating the JESYSMSG information was extracted from in-storage buffer.
Action:
None.
CAIN8210I
SYSMSG RECORD COUNT EXHAUSTED.
Reason:
This message is issued by IN25SS71 when Broadcom Support  requests diagnostic messages. This is an informational
message indicating that JESYSMSG messages extraction has exhausted its record count.
Action:
None.
CAIN8230I
SYSMSG READ FROM LAST TRACK.
Reason:
This message is issued by IN25SS71 when Broadcom Support  requests diagnostic messages. This is an informational
message indicating that JESYSMSG messages were extracted from the last track specified in MTTR.
Action:
None.
CAIN8240E
SUBSYSTEM FUNCTION 71 SPOOL READ FOR JCT FAILED. RC= rrrr SSOBRETN= cccc SSJIRETN= ssss.
Reason:
This message is issued by IN25SS71 indicating that IEFSSREQ subfunction 71 has failed reading the JCT. The return
code is rrrr, subsystem reason code is cccc, subsystem return code is ssss. Message extraction is not performed.
Action:
Contact Broadcom Support  with the error message.
CAIN8260W
OUTPUT DCB OPEN FAILED.
Reason:
This message is issued by IN25SS71 indicating that open attempt of output DCB for JOBLOG DD statement has failed.
Message extraction will not be performed.
Action:
Determine the reason for open failure. DD statement: //JOBLOG DD SYSOUT=* may be missing.
CAIN8270I


CAIN8270I
NO MORE SYSOUT FROM JES.
Reason:
This message is issued by IN25SS71 indicating end of file condition has reached.
Action:
None.
 1778


InterTest™ and SymDump ® 11.0
CAIN8300I
JCT RETREIVAL ERROR.
Reason:
This message is issued by IN25SDSB indicating there was an error retrieving job's JCT. Message extraction will not be
performed.
Action:
None.
CAIN8310I
IOT RETRIEVAL ERROR.
Reason:
This message is issued by IN25SDSB indicating there was an error retrieving job's IOT. Message extraction will not be
performed.
Action:
None.
CAIN8320I
OBTAINED IOT FROM INSTOR BUFFER
Reason:
This message is issued by IN25SDSB when Broadcom Support  requests for diagnostic messages. The message
indicated that job's IOT information was obtained from in-storage buffer.
Action:
None.
CAIN8330E
JESMSGLG ALLOCATION FAILED. MSGLOG NOT COLLECTED.
Reason:
This message is issued by IN25SDSB indicating that dynamic allocation of JESMSGLG data set name has failed.
Message extraction will not be performed.
Action:
None.
CAIN8340E
JESYSMSG ALLOCATION FAILED. SYSMSG NOT COLLECTED.
Reason:
This message is issued by IN25SDSB indicating dynamic allocation of JESYSMSG data set name has failed. Message
extraction will not be performed.
Action:
None.
CAIN8350W
FAILED TO LOCATE PDDBS FOR BOTH JESMSGLG AND JESYSMSG.
Reason:
This message is issued by IN25SDSB indicating that attempts to locate the PDDBs for JESMSGLG and JESYSMSG has
failed. Message extraction will not be performed.
Action:
 1779


InterTest™ and SymDump ® 11.0
None.
CAIN8360I
SUBSYSTEM FUNCTION 71 SPOOL READ FOR JCT FAILED. RC= rrrr SSOBRETN= ssss SSJIRETN=nnnn
Reason:
This message is issued by IN25SDSB indicating that IEFSSREQ subfunction 71 has failed reading the JCT. The return
code is rrrr, subsystem reason code is ssss, subsystem return code is nnnn. Message extraction is not performed.
Action:
Contact Broadcom Support  with this message.
CAIN8380I
JESMSGLG ALLOCATED. DDNAME: dddddddd
Reason:
This message is issued by IN25SDSB when Broadcom Support  requests for diagnostic messages. The message provides
the dynamic allocation returned DDNAME as dddddddd.
Action:
None.
CAIN8390I
JESMSGLG DYNAMIC ALLOCATION FAILED. RC/RSN: rrrr/ssss
Reason:
This message is issued by IN25SDSB indicating that dynamic allocation of SYSOUT for JESMSGLG has failed. The
dynamic allocation return code is rrrr, its reason code is ssss. This message is usually followed by IBM IKJ5635 message
providing the dynamic allocation text unit that failed. Message extraction will not be performed.
Action:
Determine and correct the cause for the failure, than retry the request.
CAIN8400W
INPUT DCB OPEN FAILED.
Reason:
This message is issued by IN25SDSB indicating that open of input DCB has failed. The two input data sets involved
are JESMSGLG and JESYSMSG. When these data sets were allocated successfully, open should not fail. Message
extraction will not be performed.
Action:


extraction will not be performed.
Action:
Determine and correct the cause of the failure, and retry the request.
CAIN8410I
INPUT DDNAME: sys E N D O F F I L E
Reason:
This message is issued by IN25SDSB indicating the end of file condition for DD named sys has reached.
Action:
None.
CAIN8410W
OUTPUT DCB OPEN FAILED.
Reason:
 1780


InterTest™ and SymDump ® 11.0
This message is issued by IN25SDSB indicating that open of JOBLOG SYSOUT has failed.
Action:
Verify that //JOBLOG DD SYSOUT=* is defined in the job's JCL.
SYMP001I
*INTERTEST VERSION ID: x.x COMPILED: dd mm yy hh:mm:ss *****
Reason:
Informative. Identifies the version and compile date and time for the InterTest for CICS PL/I postprocessor program,
IN25SYMP.
Action:
None.
SYMP002I
INTERTEST — PL/I POSTCOMPILER RUN FOR PROGRAM: progname
Reason:
Informative during initialization of IN25SYMP. Processing for the requested program has begun.
Action:
None.
SYMP003I
LISTER RECORDS ADDED TO PROTSYM FILE: nn
Reason:
Informative during termination of IN25SYMP. The number of records used on the PROTSYM file for listing information
displays.
Action:
None.
SYMP004I
SYMBOLIC RECORDS ADDED TO PROTSYM FILE: nn
Reason:
Informative during termination of IN25SYMP. The number of records used on the PROTSYM file for symbolic information
displays.
Action:
None.
SYMP005I
IN25ASMP RETURN CODE ON FINAL PROCESSING: nn
Reason:
Informative. The final return code from routine IN25ASMP displays.
Action:
None.
SYMP006I
IN25SYMP RETURN CODE ON FINAL PROCESSING: nn
Reason:
Informative. The final return code from routine IN25SYMP displays.
 1781


InterTest™ and SymDump ® 11.0
Action:
None.
SYMP101W
BLOCK NAME CANNOT BE RESOLVED. VARIABLE AND PARAMETER RESOLUTION MAY BE AFFECTEDDRC=n
BLOCK NAME= blockname
Reason:
A variable was found in the Variable Storage Map section of the compiler output whose associated block cannot be
identified.
Action:
Contact Broadcom Support  with program listings.
SYMP102W
VARIABLE DISPLACEMENT CANNOT BE DETERMINED.DRC=n, VARIABLE NAME= variable name
Reason:
A variable was found in the Variable Storage Map section of the compiler output whose associated attributes could not be
identified.
Action:
Ensure that all data names are unique within each block.
SYMP103W
PARAMETER DISPLACEMENT CANNOT BE DETERMINED.DRC=n, PARAMETER NAME= parameter name
Reason:
A parameter passed to a procedure could not be resolved and will not be available to the CORE transaction, or an
associated block could not be determined.
Action:
Ensure that all data names are unique within each block and that no procedure or entry statements are suppressed by
%NOPRINT. Check for other error messages.
SYMP104W
BASED/DEFINED VAR PTR/BASE CANNOT BE FOUND.DRC=n, VARIABLE NAME= variable name POINTER NAME
= pointer name
Reason:
The pointer associated with a BASED variable or the "base" variable of a "redefined" variable (see message SYMP115W)
could not be resolved. The "pointer" name can be either the name of the associated pointer or the "base" area for the
redefinition.
Action:
Try simplifying the expression of the base area. For example, use the following syntax to declare a "redefined" variable:
...BASED( ADDR( variable) )
or


...BASED( ADDR( variable) )
or
...DEFINED base_variable...
Also, ensure that the variable does not refer either to a subscripted array element or qualified name.
SYMP105W
ADDRESSES OF THE FOLLOWING BASED VARIABLES CANNOT BE DETERMINED FROM THE PL/I CROSS
REFERENCE. IN ORDER TO ACCESS THESE VARIABLES ONLINE, YOU MUST SPECIFY A QUALIFIED NAME IN
THE INTERTEST CORE COMMAND.   list of variable names
 1782


InterTest™ and SymDump ® 11.0
Reason:
One or more BASED (*) variables were found in the PL/I Cross Reference. IN25SYMP was unable to determine the
pointer to the variables specified.
Action:
Informational only. When attempting to view the variable online, you must use the POINTER option in the CORE
command. For more information, see the section CORE Commands for PL/I Symbolic Programs in Accessing Main
Storage CORE.
SYMP106W
ADDRESSES OF THE BASED STRUCTURES CONTAINING THE FOLLOWING VARIABLES COULD NOT BE
DETERMINED. IN ORDER TO ACCESS THESE VARIABLES ONLINE, YOU MUST SPECIFY A QUALIFIED NAME IN
THE INTERTEST CORE COMMAND.   list  of variable names
Reason:
A SYMP105W message was issued for the major structure containing the variable name(s).
Action:
Informational only. When attempting to view the variable online, you must use the POINTER option in the CORE
command. For more information, see the section CORE Commands for PL/I Symbolic Programs in Accessing Main
Storage CORE.
SYMP107W
THE FOLLOWING PL/I COMPILER OPTION IS REQUIRED IN ORDER FOR IN25SYMP TO PROCESS CORRECTLY
compiler option.
Reason:
The listed PL/I compiler option was not specified.
Action:
Ensure that the following options were specified to the PL/I compiler:
AGGREGATE OPTIONS
ATTRIBUTES(FULL) SOURCE
MAP STATEMENT (or GOSTMT)
NEST STORAGE
OFFSET XREF(FULL)
If all of the previous options were not specified, code the appropriate option(s) and rerun the job.
If all of the above options were specified, ensure that the options section is included in the PL/I compiler listing and that


the output of the compiler was directed to the INPUTT DD statement, or that the compiler terminated with a return code of
8 or less.
SYMP108W
WARNING: "%NOPRINT" OPTION SPECIFIED. ****
NOTE
Indiscriminate use of this option could cause program failure or incorrect results.
Reason:
The NOPRINT option was specified on the control card. This option suppresses checking for the occurrence of the
preprocessor control statement "%NOPRINT". If the use of this facility suppresses the listing of PROCEDURE or ENTRY
statements that contain parameter lists, or suppresses the listing of the final END statement of the program, the results
may be unpredictable. Possible effects include the inability to resolve parameter variables properly as well as possible
abnormal termination of SYMP.
Action:
Remove the NOPRINT option or ensure that the required information is not suppressed.
 1783


InterTest™ and SymDump ® 11.0
SYMP110W
STRUCTURE NAME "IN" ENCOUNTERED WHILE SCANNING CROSS REFERENCE/ATTRIBUTE LISTVARIABLE:
variable name STATEMENT NO: statement number
Reason:
While resolving structure nesting information, the identified variable in the specified statement number was found in a
major or minor structure named "IN". If this is not true, the variable may not be properly resolved.
Action:
None, if the previous condition described is correct. Otherwise, call Broadcom Support .
SYMP111W
UNABLE TO DETERMINE LENGTH OF DATA ITEM. "REFER" OPTION NOT SUPPORTED FOR BASED
VARIABLES.VARIABLE: variable name STATEMENT NO: statement number
Reason:
Dynamically sized items are not supported. Examples of such include string parameters that inherit their size from the
calling block, automatic strings whose length is an expression, and based strings whose length is specified by the REFER
option. Such variables may not be available to the CORE transaction when debugging.
Action:
None.
SYMP112W
UNEXPECTED CONVERSION ERROR WHILE PROCESSING THE CROSS REFERENCE/ATTRIBUTE LIST
FOR:VARIABLE: variable name STATEMENT NO: statement number
Reason:
An unanticipated error occurred during processing of the attribute list.
Action:
Call Broadcom Support .
SYMP113W
LABEL DISPLACEMENT CANNOT BE DETERMINED FOR: xxxxxxxx
Reason:
The indicated label could not be associated with its block.
Action:
Ensure that the label names are unique. Check the statement/offset table for missing or outoforder entries. Do not use
END block_name statements to close multiple blocks.
SYMP114W
NO STORAGE WILL BE ALLOCATED FOR THE FOLLOWING UNREFERENCED VARIABLES. THE VARIABLES
CANNOT BE ACCESSED.
Reason:


CANNOT BE ACCESSED.
Reason:
The flagged variables within the PL/I program were unreferenced.
Action:
Informational only. The flagged variables cannot be viewed online.
SYMP115W
THE FOLLOWING LINE CONTAINS "%NOPRINT" WHICH COULD PREVENT PROPER RESOLUTION OF SOME
VARIABLES.  input  compiler record
 1784


InterTest™ and SymDump ® 11.0
Reason:
Use of the compiler option %NOPRINT may cause the suppression of information needed to resolve variables properly.
Action:
Ensure that %NOPRINT does not suppress the printing of:
•
•PROCEDURE or ENTRY statements containing parameter lists.
•
•Declarations of redefined variables using expressions such as
•
...BASED( ADDR( variable ) )
or
...DEFINED base_variable...
SYMP116W
THE FOLLOWING "DEFINED" STRUCTURE IS NESTED TOO DEEPLY TO PROPERLY RESOLVE ITS LENGTH:
structure
Reason:
When a CORE command displays the specified structure, the area displayed is correct but is not be limited to the correct
length. This error occurs only with a structure nesting depth that exceeds 16, which is not currently allowed by any version
of the PL/I compiler.
Action:
None.
SYMP117W
LENGTH OF DEFINED STRUCTURE "structure" CANNOT BE RESOLVED DUE TO CONTAINED ARRAY "array"
Reason:
When a CORE command displays the specified DEFINED structure containing an array or a substructure that contains
an array, the area displayed is correct but it is limited to the correct length. This error occurs only with a structure nesting
depth that exceeds 16, which is not currently allowed by any version of the PL/I compiler.
Action:
None.
SYMP118W
VARIABLE "element name" IS A DUPLICATE NAME WITHIN A STRUCTURE.STRUCTURE, "structure name", IS
DECLARED IN STATEMENT statement numberDRC = n.
Reason:
A duplicate name was found in a structure. All names must be unique within a major structure. If not, the following
problems can occur:
 1785


InterTest™ and SymDump ® 11.0
•
•Selection of an incorrect variable
•
•Incorrect attributes for a variable
•
•Incorrect resolution of parameters
•
•System errors not apparently related to these variables
•
Action:
Assign unique names.
SYMP119W
NO AUTOMATIC VARIABLES FOUND FOR PROCEDURE procnamePARAMETER parameter CANNOT BE
RESOLVEDDRC = n.
Reason:
No AUTOMATIC variables were declared for the specified procedure. Parameters cannot be resolved for any PL/I
procedure unless AUTOMATIC variables are declared in it.
Action:
You can circumvent this restriction by declaring an AUTOMATIC variable. This variable does not have to be referenced.
SYMP120W
STRUCTURE INFORMATION FOR: variablename IS INVALID. SPECIFY CONNECT ATTRIBUTE, OTHERWISE
ONLINE STRUCTURE REQUEST WILL SHOW INVALID INFORMATION. STATEMENT #: nnn
Reason:
The CONNECT attribute is missing from the named variable, found in the specified statement number. When the
CONNECT attribute is missing, InterTest for CICS and SymDump  for CICS cannot display a valid structured CORE
display.
Action:
Redefine the variable with the CONNECT attribute to obtain a structured CORE main storage display.
SYMP121W
COMPILER EXTERNAL SYMBOL DICTIONARY NOT AVAILABLE. ADDRESSES OF THE FOLLOWING
CONTROLLED VARIABLES CANNOT BE DETERMINED.
List of variable names
Reason:
The External Symbol Dictionary is not in the compiler listings. As a result it is not possible to determine the address of
controlled variables. Therefore they cannot be displayed.
Action:
Informational only. If you desire to display controlled variables, recompile with the ESD option.
SYMP122W
THE FOLLOWING VARIABLES CAN ONLY BE ACCESSED THROUGH CA INTERTEST BATCH.
Reason:


THE FOLLOWING VARIABLES CAN ONLY BE ACCESSED THROUGH CA INTERTEST BATCH.
Reason:
The flagged variables within the PL/I program are not supported.
Action :
Informational only. The flagged variables cannot be viewed online.
 1786


InterTest™ and SymDump ® 11.0
SYMP123W
THE FOLLOWING EXTERNAL VARIABLES CANNOT BE ACCESSED THROUGH CA INTERTEST BATCH DUE TO
THE RENT OPTION.
Reason:
The flagged variables within the PL/I program are not supported.
Action:
Informational only. The flagged variables cannot be viewed with the use of the RENT option.
SYMP124W
THE POINTER FOR A BASED(ADDR VARIABLE CAN NOT HAVE MORE THAN 3 SUBSCRIPTS.
Reason:
Limit of 3 subscripts for the pointer.
Example:
DCL 1 ABC BASED(ADDR(BCD(1,2,3,4)))
Action:
None.
SYMP125W
CURRENTLY, THE FOLLOWING VARIABLES CAN NOT BE PROPERLY DISPLAYED BY INTERTEST/CICS and
INTERTEST BATCH.
List of variables
Reason:
InterTest for CICS and InterTest Batch cannot support variables with BASED ADDRESS variables with subscripts.
Action:
Informational only. These variables cannot be displayed.
SYMP126W
THE FOLLOWING VARIABLES RESIDE WITHIN AN UNNAMED STRUCTURE AND MAY NOT BE QUALIFIED
List of variables
Reason:
The indicated variables are defined within a structure that was defined with a name of ' '. Since the variable name ' '
cannot be referenced, the structure name cannot be used as qualifier.
Action:
Informational only. If the variable names indicated are not unique, the variables may not be displayable by the Broadcom
Application Quality and Testing Tools.
SYMP182W
UNABLE TO OBTAIN TIMESTAMP INFORMATION FROM LISTING, CURRENT DATE/TIME WILL BE
USED.PARAMETER parameter  CANNOT BE RESOLVEDDRC = n.
Reason:


USED.PARAMETER parameter  CANNOT BE RESOLVEDDRC = n.
Reason:
The compiler generated times stamp cannot be found in the //SYSPRINT listing used as input. This may occur because
SymDump  for CICS failed to find the date/time record. The date and time of the postprocessor's execution is used in lieu
of the compiler timestamp.
Action:
Contact Broadcom Support .
 1787


InterTest™ and SymDump ® 11.0
Note:  For messages SYMP500 to SYMP599: You are advised to contact Broadcom Support . Provide the message
number, text, and DRC code (if available). Also provide the IN25SYMP version ID and compile date and time (see
message SYMP001I) and the release number of the PL/I compiler you are using.
SYMP500E
ERROR SCANNING SOURCE FOR COMMENTS/LITERALS STATEMENT NUMBER:statement number COMMENT/
LITERAL SCAN FLAGS: xxxxxxxx
Reason:
An error occurred while scanning for comments and literals. If comments or literals contain text that resembles either a
PROCEDURE or ENTRY statement with parameters, some parameter variables may not be properly resolved.
Action:
Ensure that comments and literals do not contain text as previously described. Check message SYMP103W. Call
Broadcom Support  if this error occurs.
SYMP501E
UNABLE TO DETERMINE BEGINNING STATEMENT NUMBER FOR BLOCK. ANY VARIABLES DECLARED
IN THIS BLOCK PRIOR TO THE INDICATED STATEMENT NUMBER WILL NOT BE RESOLVED. xxxxxxxx AT
STATEMENT:statement number
Reason:
An error occurred while identifying the beginning statement number for a block. Variables declared between the beginning
of the block and the statement number may not be properly resolved.
Action:
Place an executable statement before the first variable declaration in this block. Call Broadcom Support  if this error
occurs.
SYMP502E
EXPECTED "IN..." NOT FOUND WHILE SCANNING CROSS REFERENCE/ATTRIBUTE LISTVARIABLE variable
STATEMENT NO: statement number
Reason:
An error occurred while resolving structure nesting. Structure elements may not be properly resolved.
Action:
Call Broadcom Support .
SYMP503E


Action:
Call Broadcom Support .
SYMP503E
WARNING — THE FOLLOWING LINE ASSUMED TO BE PART OF COMPILER INFORMATORY MESSAGE AND
IGNORED:   input compiler  recordDRC = n.
Reason:
The specified compiler input record was ignored.
Action:
Call Broadcom Support .
SYMP503E0
WARNING — THE FOLLOWING LINE ASSUMED TO BE A REPETITION OF VARIABLE MAP COLUMN HEADINGS:
input compiler  recordDRC = n.
Reason:
The specified compiler input record was assumed to repeat variable map column headings.
Action:
 1788


InterTest™ and SymDump ® 11.0
Call Broadcom Support .
SYMP503E1
WARNING — THE FOLLOWING LINE ASSUMED TO IDENTIFY COMPILER DIAGNOSTIC MESSAGES SECTION:
input compiler  recordDRC = n.
Reason:
The specified compiler input record was assumed to identify the compiler's diagnostic messages section.
Action:
Call Broadcom Support .
SYMP503E2
WARNING — THE FOLLOWING LINE CONTAINS TITLE IN UNEXPECTED POSITION — ASSUMED TO LIST
STATEMENT OFFSETS:  input compiler  recordDRC = n.
Reason:
The specified compiler input record contains a title in an unexpected position. This line is assumed to list statement
offsets.
Action:
Call Broadcom Support .
SYMP503E3
WARNING — THE FOLLOWING LINE CONTAINS UNEXPECTED DECIMAL OFFSET — HEX VALUE WILL BE USED:
input compiler  recordDRC = n.
Reason:
The specified compiler input record contains a decimal offset. The hexadecimal value is used instead.
Action:
Call Broadcom Support .
SYMP504E
UNEXPECTED STRUCTURE NESTING DEPTH OF n EXCEEDS PREVIOUS COMPILER LIMIT IN STATEMENT
statement number
Reason:
The nesting depth exceeds the limit in the specified compiler statement.
Action:
Call Broadcom Support .
SYMP505E
BLOCK NOT FOUND FOR VARIABLE variable, DECLARED IN STATEMENT NO. nn
Reason:
The block for the specified variable could not be found.
Action:
Call Broadcom Support .
SYMP507E
STATEMENT OUT OF EXPECTED RANGE FOR BLOCK block name
Reason:
The statement was out of the expected range for the specified block.
 1789


InterTest™ and SymDump ® 11.0
Action:
Call Broadcom Support .
SYMP508E
SEARCH FAILED FOR: variableDRC = n
Reason:
The specified variable could not be found.
Action:
Call Technical Support.
SYMP509E
INCLUDE OF USER FILES THROUGH INTEGRATED PREPROCESSOR NOT SUPPORTED. USE SEPARATE
PREPROCESSOR STEP
Reason:
The integrated INCLUDE and MACRO preprocessors of PL/I for z/OS are not supported. If you are using the integrated
SQL preprocessor, programs that contain EXEC SQL INCLUDE statements for user-defined members still require a
separate preprocessor step. (EXEC SQL INCLUDE statements for SQLCA and SQLDA are supported when using the
integrated SQL preprocessor.)
Action:
Use a separate preprocessor step to incorporate external files into your program.
SYMP599E
UNEXPECTED CHAR IN MARGIN DELIMITER POSITIONM, L, MACRO, MRGCHR: aaa, bbb, ccc, dddDRC = n.
Reason:
An unexpected character was found in the margin delimiter position.
Action:
Call Broadcom Support  and provide the information in the message.
SYMP599E0
"aaaa" POSITIONED AT BLANKSTRING: "portion of listing line"DRC = n.
Reason:
aaaa was positioned at a blank.
Action:
Call Broadcom Support  and provide the information in the message.
SYMP599E1
"IN" FOUND AT INVALID LOCATIONSTRING: "portion of listing line"DRC = n.
Reason:
An IN structure was found at an invalid location.
Action:
Call Broadcom Support  and provide the information in the message.
SYMP599E2
VARIABLE "variable", DECLARED IN STATEMENT statement number, IS ALREADY RESOLVEDDRC = n.
Reason:


Reason:
The specified variable is already resolved.
 1790


InterTest™ and SymDump ® 11.0
Action:
Call Broadcom Support  and provide the information in the message.
SYMP599E3
AGGREGATE NAME NOT MATCHED  aggregate name DRC = n.
Reason:
The specified aggregate name was not found.
Action:
Call Broadcom Support  and provide the information in the message.
SYMP599E4
FORWARD SCAN FAILED TO RESOLVE BLOCKOUTERMOST BLOCK ASSUMEDDRC = n.
Reason:
The block could not be resolved. The outermost block is assumed.
Action:
Call Broadcom Support  and provide the information in the message.
SYMP599E5
STRUCTURE PROCESSING ERROR variable name
Reason:
An error has occurred in recording a variables structure position while processing the aggregate table.
Action:
This can occur if the PL/I compile abnormally terminates or terminates with a return code greater than eight. Check these
conditions and if they occur, correct them and rerun the job. If neither has occurred, contact Broadcom Support  with the
complete job output.
SYMP599E6
STORAGE DESCRIPTOR NAME NOT MATCHED variable name
Reason:
A variable name in the storage offset table could not be matched.
Action:
This can occur if the PL/I compile abnormally terminates or terminates with a return code greater than eight. Check these
conditions and if they occur, correct them and rerun the job. If neither has occurred, contact Broadcom Support  with the
complete job output.
SYMP801E
nn STATEMENTS ENCOUNTERED; PROGRAMS WITH MORE THAN 10,000 STATEMENTS NOT
SUPPORTED.RESULTS WILL BE UNPREDICTABLE, WITH SEVERE ERRORS LIKELY.
Reason:
Because of a bug in the PL/I compiler that truncates high order digits from statement numbers in the statement/offset


table, programs with over 9,999 statements cannot be supported completely. This message is usually accompanied by
other error messages. Online debugging is affected significantly.
Action:
None.
 1791


InterTest™ and SymDump ® 11.0
SYMP901S
THE PL/I COMPILER OPTIONS LISTED ABOVE WERE NOT SPECIFIED AND HAVE CAUSED IN25SYMP TO
TERMINATE
Reason:
One or more SYMP107W message(s) were issued.
Action:
Ensure that the following options were specified to the PL/I compiler:
AGGREGATE
OPTIONS
ATTRIBUTES(FULL)
SOURCE
MAP
STATEMENT (or GOSTMT)
NEST
STORAGE
OFFSET
XREF(FULL)
See the SYMP107W messages for the specific options missing.
If all options were not specified, code the appropriate options and rerun the job.
If all of the above options have been specified, ensure that the options section is included in the PL/I compiler listing and
that the output of the compiler was directed to the INPUTT DD statement, or that the compiler terminated with a return
code of 8 or less.
SYMP902S
UNEXPECTED TERMINATION OF COMPILER OUTPUT HAS OCCURREDDRC = n.
Reason:
While scanning the PL/I compiler output, an endoffile condition was raised for the INPUTT DD statement.
Action:
Check that all the PL/I options required by IN25SYMP were set, or that the compiler terminated with a return code of 8 or
less. Correct the problem and rerun the compile and IN25SYMP.
SYMP903S
UNEXPECTED ERROR DETECTED. ERROR CORE=nnnnDRC = n.
Reason:
A PL/I error condition occurred that IN25SYMP was not designed to handle.
Action:
Check the PL/I ONCODEs and take the appropriate suggested action. If unsuccessful, contact Broadcom Support  with the
dump.
SYMP904S
IN25ASMP FUNCTION FAILED. FUNCTION CODE= n DRC = n.


IN25ASMP FUNCTION FAILED. FUNCTION CODE= n DRC = n.
Reason:
The routine that does I/O to the PROTSYM file returned with a nonzero return code.
Action:
Check the error messages from IN25ASMP and take appropriate action, and then rerun the job. This error normally
indicates a problem with the PROTSYM file. If this is the first use of the PROTSYM file, check the job that initialized
the file for normal completion. If this is not the first use of the file, check for a physical or logical error on the file. The
MESSAGE DD statement contains more information.
 1792