Reason:
Informative. Identifies the version and compile date and time for the CA InterTest for CICS PL/I post‑processor program, IN25SYMP.
Action:
None.
Reason:
Informative during initialization of IN25SYMP. Processing for the requested program has begun.
Action:
None.
Reason:
Informative during termination of IN25SYMP. The number of records used on the PROTSYM file for listing information displays.
Action:
None.
Reason:
Informative during termination of IN25SYMP. The number of records used on the PROTSYM file for SYMbolic information displays.
Action:
None.
Reason:
Informative. The final return code from routine IN25ASMP displays.
Action:
None.
Reason:
Informative. The final return code from routine IN25SYMP displays.
Action:
None.
Reason:
A variable was found in the Variable Storage Map section of the compiler output whose associated block cannot be identified.
Action:
Contact CA technical support with program listings.
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.
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.
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
...DEFINED base_variable...
Also, ensure that the variable does not refer either to a subscripted array element or qualified name.
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 the chapter "Accessing Main Storage: CORE" of the CA InterTest for CICS User Guide.
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 the chapter "Accessing Main Storage: CORE" of the CA InterTest for CICS User Guide.
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.
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 pre‑processor 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.
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 CA technical support.
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.
Reason:
An unanticipated error occurred during processing of the attribute list.
Action:
Call CA technical support.
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 out‑of‑order entries. Do not use END block_name statements to close multiple blocks.
Reason:
The flagged variables within the PL/I program were unreferenced.
Action:
Informational only. The flagged variables cannot be viewed online.
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:
...BASED( ADDR( variable ) )
or
...DEFINED base_variable...
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.
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.
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:
Action:
Assign unique names.
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.
Reason:
The CONNECT attribute is missing from the named variable, found in the specified statement number. When the CONNECT attribute is missing, CA InterTest for CICS and CA 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.
Reason:
The flagged variables within the PL/I program are not supported.
Action:
Informational only. The flagged variables cannot be viewed online.
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.
Reason:
Limit of 3 subscripts for the pointer.
Example:
DCL 1 ABC BASED(ADDR(BCD(1,2,3,4)))
Action:
None.
Reason:
The compiler generated times stamp cannot be found in the //SYSPRINT listing used as input. This may occur because CA SymDump for CICS failed to find the date/time record. The date and time of the post‑processor's execution is used in lieu of the compiler timestamp.
Action:
Contact Technical Support.
Note: For messages SYMP500 to SYMP599: You are advised to contact CA technical 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.
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 CA technical support if this error occurs.
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 CA technical support if this error occurs.
Reason:
An error occurred while resolving structure nesting. Structure elements may not be properly resolved.
Action:
Call CA technical support.
Reason:
The specified compiler input record was ignored.
Action:
Call CA technical support.
Reason:
The specified compiler input record was assumed to repeat variable map column headings.
Action:
Call CA technical support.
Reason:
The specified compiler input record was assumed to identify the compiler's diagnostic messages section.
Action:
Call CA technical support.
Reason:
The specified compiler input record contains a title in an unexpected position. This line is assumed to list statement offsets.
Action:
Call CA technical support.
Reason:
The specified compiler input record contains a decimal offset. The hexadecimal value is used instead.
Action:
Call CA technical support.
Reason:
The nesting depth exceeds the limit in the specified compiler statement.
Action:
Call CA technical support.
Reason:
The block for the specified variable could not be found.
Action:
Call CA technical support.
Reason:
The statement was out of the expected range for the specified block.
Action:
Call CA technical support.
Reason:
The specified variable could not be found.
Action:
Call Technical Support.
Reason:
An unexpected character was found in the margin delimiter position.
Action:
Call CA technical support and provide the information in the message.
Reason:
aaaa was positioned at a blank.
Action:
Call CA technical support and provide the information in the message.
Reason:
An IN structure was found at an invalid location.
Action:
Call CA technical support and provide the information in the message.
Reason:
The specified variable is already resolved.
Action:
Call CA technical support and provide the information in the message.
Reason:
The specified aggregate name was not found.
Action:
Call CA technical support and provide the information in the message.
Reason:
The block could not be resolved. The outermost block is assumed.
Action:
Call CA technical support and provide the information in the message.
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.
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.
Reason:
While scanning the PL/I compiler output, an end‑of‑file 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.
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 CA technical support with the dump.
Reason:
The routine that does I/O to the PROTSYM file returned with a non‑zero 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.
Note: Function code 8 usually means the file is full.
Reason:
An error has occurred trying to open the INPUTT file.
Action:
Ensure that the ddNAME/DLBL INPUTT points to a file that contains the output listing of the PL/I compiler.
Reason:
An error has occurred attempting to open the SYSPRINT file.
Action:
Ensure that the ddNAME/DLBL SYSPRINT is coded in your JCL.
Reason:
The internal table used to keep track of variable information has exceeded its limits.
Action:
This error is usually caused when the Attribute and Cross Reference section of the compile output could not be found by IN25SYMP.
This can occur if the compiler options ATTRIBUTE(FULL) and XREF(FULL) were not specified, or if the PL/I compile abnormally terminates or terminates with a return code greater than 8. Check for these conditions and if they occur, correct and rerun the job. If neither has occurred, contact CA technical support with the dump.
Reason:
The internal table used to keep track of PROC BLOCKS has exceeded its limits.
Action:
This error is usually caused when the Storage Requirements section of the compile output could not be found by IN25SYMP. This can occur if the compiler option STORAGE was not specified, or if the PL/I compile has abnormally terminated or terminated with a return code greater than 8. Check for these conditions and if they occur, correct and rerun the job. If neither has occurred, contact CA technical support with the dump.
Reason:
An internal table used to keep track of information about statements has overflowed.
Action:
This occurs under several conditions. If reorder has been specified in the procedure block, remove the reorder option. This may also occur if a large number of source statement lines contain multiple PL/I statements (such as, A=B; C = D; E = F;). This can also occur if the PL/I pre‑processor command %NOPRINT was specified.
Reason:
An internal table used to keep track of information about statements has overflowed.
Action:
This occurs under several conditions. If reorder has been specified in the procedure block, remove the reorder option. This may also occur if a large number of source statement lines contain multiple PL/I statements (e.g., A=B; C = D; E = F;). This can also occur if the PL/I pre‑processor command %NOPRINT was specified.
Reason:
An error was detected while attempting to find the largest PL/I statement number.
Action:
Check compiler output and the line listed. Correct the problem and rerun the job.
Reason:
An error has occurred during Phase 1 of IN25SYMP processing.
Action:
Check the Job Log for operating system or PL/I error indicators. Correct and rerun the job.
Reason:
For VSE only. Probably, a control card is either missing or invalid. Or, there may be a problem with the SYMbolic File or with the JCL for the "MESSAGE" file.
Action:
Correct the control card, SYMbolic File, or JCL.
Reason:
An END‑OF‑FILE condition occurred during the Phase 1 scan of the PL/I compiler output.
Action:
IN25SYMP prints the compiler output and terminates processing. This condition can occur when the PL/I compiler detects program errors that would prohibit successful compilation. Refer to the PL/I compiler output for error messages.
Reason:
VSE only. The VSAM I/O routine, IN25ASMP, could not be dynamically loaded. Possible causes include incorrect installation or partition/JCL that does not allow sufficient storage for loading this phase.
Action:
Check that the specified phase is in the execution phase library and that there is adequate storage.
Reason:
For VSE/POWER only. A POWER spool retrieval failed. This message identifies the request. If only one job gets this error, the JCL for the job is probably incorrect. If all jobs get this error, CA InterTest for CICS may not have been properly installed and customized.
Action:
Check the JCL and, if necessary, CA InterTest for CICS installation and customization.
Reason:
The PL/I compiler options NOSYNTAX and NOCOMPILE can prevent the normal completion of the compilation process, either conditionally, depending on the severity of the errors, or unconditionally. The CA InterTest for CICS PL/I post‑processor program, IN25SYMP, terminates immediately when it recognizes an aborted compilation.
Action:
Usually, correction of compilation errors resolves this problem.
Reason:
An internal table has exceeded the limit of the halfword index. The post‑processor program terminated to prevent subsequent errors. This situation should not occur for programs with significantly less than 32,767 statements. Because support is limited to programs with less than 10,000 statements, this situation is unlikely to occur.
Action:
Call CA technical support and provide the information in the message.
Reason:
An undocumented error code has forced termination of IN25SYMP.
Action:
Contact CA technical support.
|
Copyright © 2014 CA Technologies.
All rights reserved.
|
|