EE The 60 day trial period has expired. Contact your IBM service representative or local software dealer to order your copy.
WQ Confirm delete: %1. Click on Delete to delete the item, Cancel to continue without deleting the item.
II %1 cannot be deleted. Select OK to cancel the action.
WW The ECFWORK directory, %1, has only %2 bytes available. Errors may occur due to unavailable disk space.
EE Empty folder name field. Type a valid name (1 or more characters) in the field.
WW Could not find environment file. Click on Continue to continue without restoring your environment, Cancel to end the startup.
WW Saved environment cannot be restored. Click on Continue to continue without restoring your environment, Cancel to end the startup.
WS %1 already exists in the current folder. Click on Replace to overwrite the existing object, Cancel to continue without adding an object.
EE Settings profile %1 could not be found. Ensure that it is in the directory specified by ECFWORK in your CONFIG.SYS file.
EE The specified ECFWORK directory, %1, could not be found. Ensure that CONFIG.SYS specifies an existing directory for ECFWORK.
WW Cannot access environment file ECFMAIN.INI. Click on Continue to continue closing without saving your environment, Cancel to cancel the close.
EE Could not save environment file ECFMAIN.INI because it is corrupted. Program Conversion and Structuring will exit without saving your environment.
II A folder cannot be placed into a folder it already contains.
II The object %1 you are trying to add already exists.
II Cannot drop a folder into itself.
II Object name already exists in the folder.
WQ The files %1 and %2 represent the same object: %3. Click on Replace to overwrite.
WQ Do you want to cancel the %1 process? Click on Yes to cancel the process or No to continue processing.
II %1 process has been cancelled.
II %1 process has been cancelled. System messages will be displayed.
II The input program contains one or more EXIT PROGRAM statements.
II The CICS HANDLE commands on the lines below specified conditions that cannot be raised by any CICS commands in the input program. In structuring these HANDLE commands are deleted from the output program.
II The conditions listed below were specified on CICS HANDLE commands but they cannot be raised by any CICS command in the input program. In structure mode these conditions are deleted from the CICS HANDLE command in the output program.
EE Unrecoverable Program Conversion and Structuring error on file CQF. Contact the IBM Product Support Center.
EE Unrecoverable Program Conversion and Structuring error on file DTF. Contact the IBM Product Support Center.
EE Unrecoverable Program Conversion and Structuring error on file GSF. Contact the IBM Product Support Center.
EE Unrecoverable Program Conversion and Structuring error on the Input COBOL File.
EE Unrecoverable Program Conversion and Structuring error on the Input COBOL Report.
EE Unrecoverable Program Conversion and Structuring error on the Output COBOL File.
EE Unrecoverable Program Conversion and Structuring error on file OCQ. Contact the IBM Product Support Center.
EE Unrecoverable Program Conversion and Structuring error on the Output COBOL Report.
EE Unrecoverable Program Conversion and Structuring error on file OPT. Contact the IBM Product Support Center.
EE Unrecoverable Program Conversion and Structuring error on file PTF. Contact the IBM Product Support Center.
EE Unrecoverable Program Conversion and Structuring error on the Reengineering Report file.
EE Unrecoverable Program Conversion and Structuring error on Non-Returning Calls file.
EE Unrecoverable Program Conversion and Structuring error.
EE Unrecoverable Program Conversion and Structuring error on file DTF2. Contact the IBM Product Support Center.
EE Unrecoverable Program Conversion and Structuring error on file GSF2. Contact the IBM Product Support Center.
EE Unrecoverable Program Conversion and Structuring error on file PTF2. Contact the IBM Product Support Center.
EE Unrecoverable Program Conversion and Structuring error on file CMSRF. Contact the IBM Product Support Center.
EE Unrecoverable Program Conversion and Structuring error on file RD. Contact the IBM Product Support Center.
EE Unrecoverable Program Conversion and Structuring error on file DTF3. Contact the IBM Product Support Center.
EE Unrecoverable Program Conversion and Structuring error on file GSF3. Contact the IBM Product Support Center.
EE Unrecoverable Program Conversion and Structuring error on file PTF3. Contact the IBM Product Support Center.
EE Unrecoverable Program Conversion and Structuring error on file CICS. Contact the IBM Product Support Center.
EE Unrecoverable Program Conversion and Structuring error due to corrupted file CICS. Check that you are using the original file shipped with the product. If this does not resolve the problem, contact the IBM Product Support Center.
WQ %1 already exists. Click on Replace to replace the file.
EE Maximum of 10 active host sessions exceeded. Shut down any unused active servers and retry the operation.
EE Program Conversion and Structuring's workstation component is unable to establish a communications session with the host. Click on Help for more detail.
EE The file on the host is being used by another user. Retry the action when the file is not being used.
II Incorrect system name entered preceding the file name. Enter OS2, VM, or MVS.
II The %1 processing for '%2' was successful. The %3 has been updated. System messages will be displayed.
II The %1 processing for '%2' was successful.
EE Communications error occurred during processing with the host. Check the job status on the emulation window for messages.
II The %1 processing for '%2' was successful. The %3 has been updated.
EE The REXX procedure, %1, could not be found on the host. Click on Help for more detail.
II System name syntax not valid. Enter OS2 for an OS/2 system, VM for a VM system, or MVS for an MVS system.
EE An error in Analyze or Structure processing resulted in the following return code: %1. Click on Help for more detail.
EE An error in Convert processing resulted in the following return code: %1. Click on Help for more detail.
EE The report file cannot be displayed because it has an incorrect format. Click on Help for more detail.
EE The report parser cannot read the Reengineering Report file, %1. Rerun Analyze or Structure to produce a new report.
EE The report parser cannot write to the file %1. Delete the file and rerun Analyze or Structure to produce a new report.
EE Host file allocation error for file %1. Click on Help for more detail.
EE Host file allocation error for file %1. Click on Help for more detail.
EE An error in Modularize processing resulted in the following return code: %1. Click on Help for more detail.
EE An OS2 file error occurred in function %1 with a return code of %2 when Program Conversion and Structuring attempted to open the local file. Check the OS/2 Manual for an explanation of the return code
EE An I/O error occurred on the OS/2 file system in function %1. Check the OS/2 Manual under the specified function.
II File, %1, not found. Check to make sure the file name is correct or the file exists. Click on Help for correct file name syntaxes.
II The syntax of the file name, %1, is not valid or the file does not exist. Click on Help for correct file name syntaxes.
II The syntax of the directory, %1, is not valid or the directory does not exist. Click on Help for correct directory syntaxes.
EE File, %1, has been locked by another user. Try again when the file is no longer in use.
EE File, %1, is read only. You can only browse the file.
EE File, %1, not authorized for your use. Obtain authorization from the file owner or system administrator.
EE File, %1, cannot be saved because it exceeds allocated storage. Allocate more storage and try the save again.
II File, %1, has an incorrect file type. Acceptable types are sequential and partitioned.
II No items were found matching the specified name.
EE File mode, %1, does not match any of your linked disks. Correct the file mode, or link to the appropriate disk, and try the action again.
EE File mode, %1, has not been accessed. Access the file mode and try the action again.
EE Dataset, %1, not found.
EE Dataset, %1, not authorized for your access. Obtain authorization from the dataset owner or the system administrator.
EE Dataset, %1, exceeded the allocated storage. Allocate more storage for the dataset.
EE Path not found %1. Check the path specified or create the necessary directories.
EE Authorized to read but not update file %1. Obtain authorization from the file owner or your system administrator.
II Selection Error - File must be a partitioned dataset. Select a partitioned dataset.
II Selection Error - File must be a sequential dataset or a PDS member. Select a sequential dataset or a PDS member.
EE Error while accessing local file %1. Check to see if you are attempting to write into a protected area.
EE System error. Check the error log for diagnostic information.
EE There is not enough memory on your workstation. Close all unnecessary windows and applications and try the action again.
II Memory allocation error. Program Conversion and Structuring cannot perform the requested action. Close all unnecessary windows and applications and try the action again.
EE Unrecognized internal return code received. Contact your IBM service representative.
WQ Convert settings profile already exists as an Analyze/Structure settings profile. Click on Replace to overwrite the existing profile.
EE Cannot save the settings into the read only file, %1. Enter or select another file name.
EE Cannot locate the default settings profile, %1. Contact your administrator.
EE Cannot have more than 3 COPY library names in the list.
EE Output file name cannot be the same as the input file name. Specify another file name.
EE Cannot have more than 6 COPY library names in the list.
EE No Copy libraries specified. Click on Help for detail.
WW Analyze or Structure options are invalid. Default options will be used. Click on Continue to continue processing or Cancel to cancel it.
WW Convert options are invalid. Default options will be used. Click on Continue to continue processing.
WS The Output file name, %1, is incorrect. Click on Change to enter a new name.
WS Non-returning CALLs file name is incorrect or does not exist. Click on Change to enter a new name.
WS The Output Copy Library name, %1, is incorrect. It must be a directory name. Click on Change to enter a new name.
EE The Output Copy Library name cannot be the same as any of the Input Copy Library names.
WS The Output file, %1, already exists. Click on Replace to replace the file or Change to enter a new file name.
WS The Output Copy Library name, %1, is the same as one of the Input Copy Library names. Click on Change to change the Output Copy Library name.
WS The output file name cannot be the same as the input file name. Click on Change to specify another file name.
WQ Analyze/Structure settings profile already exists as a Convert settings profile. Click on Replace to overwrite the existing profile.
II Cannot display Input Repair window because there is no PERFORM Detail information in the Reengineering Report.
II Cannot display Input Repair window because a recursive network exists.
WS Do you want to display the new Reengineering Report? Click on Refresh to close the current report and display the new one.
II No Reengineering Report exists. Rerun Analyze or Structure to create a new report.
II The Input Repair window will be updated based upon the data in the newly created Reengineering Report.
II A problem was encountered during Expert Advice. Please see the file ECFTIRS.LOG in the Program Conversion and Structuring working directory for more details.
II There is no data for the Roots Expert Advice window because there is no roots data on the PERFORM Detail page of the Reengineering Report.
II There is no data for the Non-Roots Expert Advice window because there is no non-roots data on the PERFORM Detail page of the Reengineering Report.
WQ Do you want to save your changes before closing the edit window? Click on Save to save your changes.
EE A system error was caused by a missing DLL file. Contact your IBM service representative.
WQ Your input file has been modified. Do you want to save it before running Analyze?
WQ Your input file has been modified. Do you want to save it before running Structure?
EE Internal error. Contact your IBM service representative.
II Cannot find the text specified in the entry field.
II %1 in the "Find" field cannot be found.
II The internal RD file %1 cannot be found.
WQ The file will be saved as %1. Click on Save to save the file or Cancel to cancel the save.
WQ The file, %1, already exists. Click on Replace if you want to overwrite the existing report file on your workstation.
EE The Reengineering Report %1 cannot be displayed because it cannot be determined whether it is an Analyze or Structure report. Click on Help for more detail.
EE Invalid directory or drive is not ready. Select a valid directory or drive which is ready.
EE Invalid path. Check the path entered or select the path from the directory list.
EQ %1 the file %2 using profile %3?
II A severe error has occurred during %1 processing. The return code is %2.
II A severe error has occurred during %1 processing. The return code is %2. System messages will be displayed.
II The requested item, '%1', can not be found.
WQ Confirm clear request. Click on Continue to clear, or on Cancel to continue without clearing.
EE Program Conversion and Structuring is already processing another request. Restart this action after that process has completed.
EQ Program Conversion and Structuring is already processing another request. Do you want to wait until that action completes? Click on Continue to wait, or on Cancel to exit.
EW You were waiting for another process to end, but have asked to stop waiting. Click on Continue to continue closing this process, or on Cancel to return to waiting.
II The process you were waiting for has ended. Program Conversion and Structuring will now continue.
II A severe error has occurred while waiting for another process to end. The return code is %2.
II A severe error has occurred during %1 processing. The return code is %2. %3 processing was not initiated.
II A severe error has occurred during %1 processing. The return code is %2. %3 processing was not initiated. System messages will be displayed.
II A severe error has occurred during %1 processing. The return code is %2. %3 processing was successful.
II A severe error has occurred during %1 processing. The return code is %2. %3 processing was successful. System messages will be displayed.
EE Message file, ECF.MSG, could not be found. Click on Help for detail.
EE Message too long for display. Contact your IBM representative.
EE Message number not found in message file. Contact your IBM representative.
EE Unable to access message file. Contact your IBM representative.
EE Invalid message file format. Contact your IBM representative.
EE Invalid insertion variable count. Contact your IBM representative.
EE Not enough memory available to perform message extraction. Click on Help for detail.
EE Cannot display the error message box. Contact your IBM representative.
II Cannot load message resource file. Contact your IBM representative.
EE Message filename exceeds allowable range.
II Cannot display the Help due to insufficient disk space or memory. Close Program Conversion and Structuring, free some disk space and memory, and restart Program Conversion and Structuring.
EE Cannot associate Help instance with the window due to insufficient disk space or memory. Close Program Conversion and Structuring, free some disk space and memory, and restart Program Conversion and Structuring.
EE Host file allocation error in EXEC (ECFSCPC) for file %1.
EE %1 is a sequential dataset. Only a partitioned dataset is allowed.
EE Cannot initialize ISPF environment.
EE ISPF variables need to be set for CCCA. %1 needs to be initialized.
EE Error in opening file %1.
EE Error in reading or writing to file %1.
EE Using invalid key to access VSAM option file %1.
EE Error in allocating the Conversion reports dataset. The dataset name is %1. Click on Help for detail.
S Line %1, symbol %2: symbol %3 was expected.
EXPLANATION: PCS expected a different symbol from the symbol found on the specified line.
RESPONSE: Correct the symbol that caused the error.
S Line %1, symbol %2: End of file was expected.
EXPLANATION: PCS expected no more symbols in the program, but found the listed symbol.
RESPONSE: Correct the symbol or symbols that caused the error.
S Line %1: Symbol %2 is not a valid COBOL symbol.
EXPLANATION: The listed symbol is not one of the valid COBOL symbols. For example, this could happen if a data name has a non-COBOL character in it, such as % or $.
RESPONSE: Correct the symbol or remove it.
S Line %1: Symbol %2 exceeds the maximum symbol length.
EXPLANATION: A symbol was found that exceeds 67 characters in length. This message will not occur for continued nonnumeric literals longer than 67 characters.
RESPONSE: Truncate and/or correct the symbol.
S Unrecoverable parsing error -- parsing terminated.
EXPLANATION: This message can occur only if PCS found previous errors. The messages for those errors will be listed above this message. This message indicates that PCS found an error from which it was not able to recover in order to continue processing.
RESPONSE: Correct the errors listed above this message.
S Line %1: Illegal character found in column 7.
EXPLANATION: A character was found in column 7 that is not a continuation character (-), comment character(* or /), debug character (D), or blank.
RESPONSE: Correct the character.
S Line %1: Blank continuation line found.
EXPLANATION: The character in column 7 is a continuation character (-), but no continuation text follows.
RESPONSE: Either delete the continuation character, delete the line, or add text to the line.
S The Data Division was not found in the input program.
EXPLANATION: The input program does not contain the Data Division header.
RESPONSE: Check that the Data Division header is not contained in a copy member, the header begins in area A (columns 8 through 11), the header is spelled correctly, and the keyword DATA is not continued on multiple lines. If the header is not there, add it.
S No termination statement found in the input program.
EXPLANATION: The program does not contain either of the termination statements STOP RUN or GOBACK.
RESPONSE: Add the appropriate termination statement.
S Line %1: Too many sections in DECLARATIVES.
EXPLANATION: This is a PCS restriction; there can be no more than 100 sections in DECLARATIVES.
RESPONSE: Decrease the number of sections in DECLARATIVES by merging, rewriting, and/or deleting sections.
S Line %1: Too many sections in Procedure Division.
EXPLANATION: This is a PCS restriction; there can be no more than 2,145 sections in the Procedure Division.
RESPONSE: Decrease the number of sections in the program by merging, rewriting, and/or deleting sections.
S Line %1: Too many paragraphs in section %2.
EXPLANATION: This is a PCS restriction; there can be no more than 9,999 paragraphs plus sentences containing NEXT SENTENCE in a section.
RESPONSE: Decrease the number of paragraphs in the section by merging, rewriting, and/or deleting paragraphs.
S Line %1: GO TO between DECLARATIVES and nonDECLARATIVES.
EXPLANATION: There is a transfer of control by GO TO statement from DECLARATIVES to nonDECLARATIVES, or from nonDECLARATIVES to DECLARATIVES.
RESPONSE: Eliminate or modify the target of the GO TO statement.
S Line %1: PERFORM of nonDECLARATIVES procedure from DECLARATIVES or of DECLARATIVES procedure from nonDECLARATIVES.
EXPLANATION: Transfer of control by PERFORM statement between DECLARATIVES and nonDECLARATIVES.
RESPONSE: Eliminate or modify the target of the PERFORM statement.
S Line %1: Invalid PICTURE clause.
EXPLANATION: A PICTURE clause was found that contains invalid characters or does not contain any PICTURE character string.
RESPONSE: Either correct the characters in the PICTURE character string, or add a character string if one is missing.
S Too many lines in the input program. The program must contain fewer than 1,000,000 lines.
EXPLANATION: This is a PCS restriction; the input program must contain fewer than 1,000,000 lines.
RESPONSE: Try to simplify or segment the program into smaller parts.
S Line %1. More than six AFTER clauses in PERFORM statement.
EXPLANATION: Only up to six AFTER clauses are permitted in a PERFORM statement.
RESPONSE: Decrease the number of AFTER clauses in the PERFORM statement, so that it is within the limit of six.
S Expecting END-EXEC but found end of file.
EXPLANATION: An END-EXEC did not end a CICS command.
RESPONSE: Examine the program to determine the missing END-EXEC and insert one.
S Invalid CICS condition %1 found.
EXPLANATION: The CICS HANDLE command had an invalid condition.
RESPONSE: Either delete the invalid condition or replace with a valid one.
S Line %1: Label %2 not found.
EXPLANATION: A GO TO, ALTER, or PERFORM statement refers to a label that is not present in the input program.
RESPONSE: If the label is not contained in a COPY member, select the Bring Procedure Division COPY members inline option; enter the correct names for the COPY libraries. If the label is not in a COPY member, check the spelling of the label.
S Invalid CICS command %1 found.
EXPLANATION: The CICS command is not valid.
RESPONSE: Either delete the invalid command or replace with a valid one.
S Line %1: Negative integer in TIMES option of PERFORM.
EXPLANATION: A PERFORM statement was found that specifies a negative TIMES value.
RESPONSE: Correct the TIMES value.
S Line %1: ALTER of %2 causes GO TO between DECLARATIVES and nonDECLARATIVES.
EXPLANATION: There is a transfer of control from DECLARATIVES to nonDECLARATIVES, or from nonDECLARATIVES to DECLARATIVES, due to an ALTER statement.
RESPONSE: Eliminate or modify the ALTER statement.
S Line %1: Performed procedure is partly in DECLARATIVES, partly in nonDECLARATIVES.
EXPLANATION: A performed procedure crosses the boundary between DECLARATIVES and nonDECLARATIVES.
RESPONSE: Eliminate or modify the PERFORM statements.
S Invalid HANDLE AID option %1 found.
EXPLANATION: The HANDLE AID option found is not recognizable.
RESPONSE: Either delete the invalid option or replace with a valid one.
S A GO TO statement specifies a non-terminating CICS HANDLE target label.
EXPLANATION: A non-terminating CICS HANDLE target follows CSF-HANDLER label and precedes CSF-MAIN. PCS restricts such a label's use in a GO TO statement.
RESPONSE: Eliminate or modify the target of the GO TO statement.
S Line %1: ALTER of nonDECLARATIVES from DECLARATIVES or of DECLARATIVES from nonDECLARATIVES.
EXPLANATION: Either an ALTER statement in DECLARATIVES is modifying a label in nonDECLARATIVES, or an ALTER statement in nonDECLARATIVES is modifying a label in DECLARATIVES.
RESPONSE: Eliminate or modify the ALTER statement.
S Line %1: A PERFORM statement specifies a non-terminating CICS HANDLE target label.
EXPLANATION: A non-terminating CICS HANDLE target follows the CSF-HANDLER label and precedes CSF-MAIN. PCS restricts such a label's use in a PERFORM statement.
RESPONSE: Eliminate or modify the PERFORM statement.
S Line %1: A CICS command was found but the CICS Version/Release option was set to "No CICS."
EXPLANATION: PCS did not expect to find any CICS commands because the user specified "No CICS." PCS cannot determine the semantics of the CICS commands because the correct CICS level was not specified.
RESPONSE: Specify the CICS level and run the program through PCS again.
S Invalid CICS FEPI command found.
EXPLANATION: The CICS FEPI command is not valid.
RESPONSE: Either delete the invalid command or replace with a valid one.
S Line %1: EXIT PROGRAM statement found. PCS does not allow the use of this statement.
EXPLANATION: This is a PCS restriction unless the input language is VS COBOL II Release 3; EXIT PROGRAM statements cannot be used in the input program.
RESPONSE: Eliminate the statement, or change it to GOBACK or STOP RUN.
S The PROGRAM-ID was not found in the input program.
EXPLANATION: The input program does not contain the PROGRAM-ID paragraph.
RESPONSE: Check for any misspelling or add the PROGRAM-ID paragraph.
I A period was found in column 73 of each input program line listed below. These periods were not recognized by PCS as ending a sentence. Check the input program to see if any of these periods should end a sentence; if so, move the period into area B (columns 12 through 72).
EXPLANATION: This message is usually listed when a line of code becomes too long to completely fit in area B, and the period ends up in column 73. This situation does not affect the processing of the program, unless the period ends an IF statement, for example.
RESPONSE: No action is required. You could check to see whether the periods in the listed lines belong in area B. If so, move them. You may have to split lines to do so.
W Priority numbers were found on the following section labels, listed with their line numbers in the input program. They could cause the structured output program to behave differently from the input program.
%1, %2
EXPLANATION: Transfers of control between sections with priority numbers can cause differences in behavior of PERFORM and ALTER statements.
RESPONSE: No action is required. However, you could remove the priority numbers, especially if the structured program behaves differently from the input program.
E A CICS HANDLE statement was found on each line of the input program listed below. These statements could cause the structured output program to either not compile or to behave differently from the input program. Check the structured program to determine whether these statements perform the desired function.
EXPLANATION: If the input program contains CICS HANDLE statements, the structured program may not compile.
RESPONSE: Remove the HANDLE statements and rerun PCS.
E A SQL WHENEVER statement was found on each line of the input program listed below. These statements could cause the structured output program to either not compile or to behave differently from the input program. Check the structured program to determine whether these statements perform the desired function.
EXPLANATION: PCS does not structure the complex logic of SQL WHENEVER statements. If the input program contains WHENEVER statements, the structured program may not compile, since the labels listed in the WHENEVER statements may not be present in the structured program. If the structured program does compile, it may not execute correctly, since the WHENEVER statements introduce unstructured logic into the structured program.
RESPONSE: Remove the WHENEVER statements from the input program, then rerun PCS.
E A COPY statement was found on each line in the Procedure Division of the input program listed below. The copy members associated with these statements will not be structured. To structure the copy members along with the rest of the program, rerun PCS, entering the names of the copy libraries. If you do not want to structure the copy members along with the rest of the program, make sure that the copy members conform to the input program requirements listed in the PCS User's Guide.
EXPLANATION: This message will appear when PCS finds COPY statements in the Procedure Division of the input program. This could happen if you did not select the "Bring Procedure Division copy members inline" option, or if you entered the wrong copy library names.
RESPONSE: If you want copy members structured along with the rest of the program, select the "Bring Procedure Division copy members inline" option, enter correct copy library names, and rerun PCS. If you request Procedure Division copy members to be structured with the rest of the program, PCS will structure the program as a whole, including the copy members. The copy member code will be included as part of the structured program, not as members to be copied.
E No Procedure Division was found. PCS did not create a structured output program.
EXPLANATION: The input program did not contain the Procedure Division header. This message can only be produced when the input program is VS COBOL II Release 3, since Procedure Division is not required in that language. The message indicates that PCS did not find the Procedure Division and did not attempt to structure the program. No output program is produced in this case.
RESPONSE: None if the program is not supposed to contain a Procedure Division. Otherwise, check that the Procedure Division header is not contained in a copy member, the header is in area A (columns 8 through 11), the header is spelled correctly, and the keyword PROCEDURE is not on multiple lines.
E Output may not be functionally equivalent due to the presence of CICS commands PUSH/POP.
EXPLANATION: PCS cannot guarantee that the output program will behave the same as the input program due to PUSH and POP CICS commands, as it adds a more complex dimension to the control flow.
RESPONSE: If your program requires PUSH and/or POP, delete the PUSH and/or POP commands from the program, restructure the program, and manually insert the PUSH and/or POP commands in the structured program where appropriate.
E Output may not be functionally equivalent due to the presence of the CICS HANDLE ABEND command with the LABEL option.
EXPLANATION: PCS cannot guarantee that the output program will behave the same as the input program due to the CICS HANDLE ABEND command, as it adds a more complex dimension to the control flow..
RESPONSE: Either delete the CICS HANDLE ABEND command from the program, or replace it with CICS HANDLE ABEND PROGRAM(name).
S Line %1: There are more than 99 ENTRY statements in one paragraph of the input program. You should divide the paragraph containing this line into two or more smaller paragraphs and then rerun PCS.
EXPLANATION: There are more than 99 ENTRY statements in one paragraph of the input program. The line number given is that of the 100th.
RESPONSE: Divide the paragraph containing this line into two or more smaller paragraphs and rerun PCS.
S Line %1: An input program label is altered but does not contain a single GO TO statement. This program must be compilable with no errors before it can be structured by PCS.
EXPLANATION: Not a legal COBOL program. The line number given is that of the first such altered label.
RESPONSE: Correct the program and rerun PCS.
S Line %1: A targetless GO TO statement was found that is not in an altered paragraph. This program must be compilable with no errors before it can be structured by PCS.
EXPLANATION: Not a legal COBOL program. The line number given is that of the first targetless GO TO that is not altered.
RESPONSE: Correct the program and rerun PCS.
S Line %1: A SORT INPUT PROCEDURE or SORT/MERGE PROCEDURE has complex usage that would require integration by PCS into procedures that invoke it. This transformation cannot be applied due to the restricted syntax of the SORT and MERGE verbs. You should recode this procedure so that it has a single entry and a single exit.
EXPLANATION: Integration cannot be applied due to the restricted syntax of the SORT and MERGE verbs. The causes of the complex usage are listed in the Messages section of the Reengineering Report. Other procedures' properties are reported in the PERFORMS Analysis Detail or PERFORMS Transformation Results Detail of the Reengineering Report. The line number given is that of the initial label of the SORT/MERGE procedure.
RESPONSE: Recode this procedure so it has a single entry and a single exit. The detail reports can help you do this. Then rerun PCS.
S Line %1: There are too many ENTRY statements, PERFORM statements, and/or performed procedures with the same final label in one paragraph of the input program. If possible, you should divide the paragraph containing this line into two or more smaller paragraphs and then rerun PCS. However, the PCS limit on the number of different performed procedures that may have the same final label is 99.
EXPLANATION: The number of complex performs, multi-entry/exit procedures, and ENTRY statements in one paragraph exceeds 99; OR the number of complex and multi-entry/exit procedures that have the same final label but different initial labels exceeds 99.
RESPONSE: If the former condition is the cause, divide the paragraph containing this line into two or more smaller paragraphs and rerun PCS. If the second condition is the cause, recode procedures with the different initial labels to have the same initial label, or recode procedures to have a single entry and exit, then rerun PCS.
S Line %1: There is an ALTER of the final label of a performed procedure. PCS does not allow the final label of any performed procedure to be altered.
EXPLANATION: PCS does not allow the final label of any performed procedure to be altered.
RESPONSE: Recode the ALTER or the performed procedure and rerun PCS.
S Line %1: There are more than 499 different non-returning CALL statements (either different CALL-literal or different USING lists).
EXPLANATION: The number of distinct calls to modules in non-returning CALLs file exceeds the PCS limit of 499. Two CALLs to the same module are distinct if their USING lists are different.
RESPONSE: Remove module names from the non-returning CALLs file, or reduce the number of distinct CALLs to such modules.
I All program termination statements are in DECLARATIVES. The structured program may appear to have no exit from the mainline. Also, if the termination statement(s) can be reached while a PERFORM is active, you should examine the value specified for "PERFORMs reached in non-initial state."
EXPLANATION: The structured program may appear to have no exit from the mainline.
RESPONSE: If the termination statement(s) can be reached while a PERFORM is active, examine the value specified for "PERFORMs reached in non-initial state." You can use the PERFORMs Analysis Detail of the Reengineering Report (Analyze), or the PERFORMs Transformation Detail of the Reengineering Report (Structure) to determine this.
I PERFORM . . . UNTIL refers to a procedure that contains no statements, or only an EXIT statement. Listed below are the input program line numbers and procedure labels of such PERFORM statements. You may want to verify that this is intended in the input program, as this may represent an endless loop in both the input and output programs.
%1, %2
EXPLANATION: The input program line numbers of PERFORM . . . UNTIL statements that reference null procedures are listed. A null procedure either has no statements, or only an EXIT statement.
RESPONSE: Verify this is intended in the input program, as it may represent an endless loop in both the input and output programs.
I PERFORM . . . TIMES refers to a procedure that contains no statements, or only an EXIT statement. Listed below are the input program line numbers and procedure labels of such PERFORM statements. You may want to examine these statements in the input program to see whether they should be removed for greater efficiency.
%1, %2
EXPLANATION: The input program line numbers of PERFORM . . . TIMES statements that reference null procedures are listed. A null procedure either has no statements, or only an EXIT statement.
RESPONSE: Examine these statements in the input program to see whether they should be removed for greater efficiency.
I PERFORM . . . VARYING refers to a procedure that contains no statements, or only an EXIT statement. Listed below are the input program line numbers and procedure labels of such PERFORM statements. The function of these statements is to change the value(s) of the VARYING control data items. You may want to examine these statements in the input program to see whether they should be recoded as MOVE or SET statements for greater efficiency.
%1, %2
EXPLANATION: Input program line numbers of PERFORM . . . VARYING statements that reference null procedures are listed.
RESPONSE: See if these statements should be recoded in the input program as MOVE or SET statements for greater efficiency.
I Options input to PCS caused the program to be analyzed under an assumption that active PERFORM statements are left as active when GOBACK is encountered. This means that reinvocation (following GOBACK) can expect the PERFORM return mechanisms to be in their last-used state. If you are certain that the program is never reinvoked (following GOBACK) expecting PERFORM mechanisms to be in their last-used state, rerun PCS without selecting "Performs reached in non-initial state."
This will usually improve the readability of the structured program.
EXPLANATION: Reinvocation (following GOBACK) can expect the PERFORM return mechanisms to be in their last-used state.
RESPONSE: If you are certain that the program is never reinvoked (following GOBACK) expecting PERFORM mechanisms to be in their last-used state, rerun PCS without selecting "Performs reached in non-initial state."
I Options input to PCS caused the program to be analyzed under an assumption that any active PERFORM statement is deactivated when GOBACK is encountered. While this usually produces the most readable structured program, you should make sure that this assumption is correct. If you are uncertain whether the program is ever reinvoked (following GOBACK) expecting PERFORM mechanisms to be in their last-used state, select "Performs reached in non-initial state" and rerun PCS.
EXPLANATION: Reinvocation (following GOBACK) never expects that the PERFORM return mechanisms are in their last-used state.
RESPONSE: While this usually produces the most readable structured program, make sure that this assumption is correct. If you are uncertain whether the program is ever reinvoked (following GOBACK) expecting PERFORM mechanisms to be in their last-used state, select "PERFORMs reached in non-initial state" and rerun PCS.
I The output program paragraphs listed will always terminate the program through STOP RUN, GOBACK, EXIT PROGRAM, CICS commands ABEND, RETURN or XCTL, or CALL of a program that can never return.
EXPLANATION: The output program paragraphs listed will never return to their invoking paragraphs. When executed, they will always terminate the program through STOP RUN, GOBACK, EXIT PROGRAM, CICS commands ABEND, RETURN or XCTL,or CALL of a program that can never return.
RESPONSE: None -- informational message only.
I The line numbers listed are associated with CALLs of programs that you specified could never return to their caller. You should check the list of non-returning modules specified to make sure that none of the modules listed in that file can ever return to its caller.
EXPLANATION: PCS treats CALLs of modules listed in the non-returning CALLs file as never returning control to the calling program (the program being structured). These CALL statements are moved to the CSF-TERMINATION procedure of the structured program if you selected the option "Keep program terminations."
RESPONSE: Check the list of non-returning modules specified to make sure that none of the modules listed in that file can ever return to its caller.
E Each of the multi-entry and/or multi-exit procedures listed below is invoked as an INPUT or OUTPUT PROCEDURE by one or more SORT or MERGE verbs. You should carefully examine the Reengineering Report to make sure that these entries/exits are intended. Review the User's Guide material about SORT/MERGE Procedures.
EXPLANATION: PCS can structure certain programs containing multi-entry and/or multi-exit procedures that are invoked by SORT or MERGE. However, the messages issued from the sort interface (DFSORT or other) may differ between the input program and the structured output. In particular, when your input program terminates while in a SORT or MERGE, and you have not specified to keep program terminations, your output program will terminate after normal return from the SORT or MERGE.
This means that the abend resulting from GOBACK during SORT or MERGE will not be produced in the output program. Choosing to keep program terminations will eliminate this situation.
RESPONSE: Carefully compare the SORT/MERGE routines in the input and structured programs, and test the structured program before putting it into production. You can use the Reengineering Report to find the multiple entry and exit points.
I The input program contains one or more EXIT PROGRAM statements. PCS analyzes these statements under the assumption that they always terminate the program unless immediately followed by the PCS generated CALL CSF-ILBOABN0 statement.
EXPLANATION: PCS treats EXIT PROGRAM statements as if they terminate the program.
RESPONSE: None -- informational message only.
I The CICS HANDLE commands on the lines listed below specified conditions that cannot be raised by any CICS command in the input program. In structure mode these HANDLE commands are deleted from the output program.
EXPLANATION: Since none of the conditions specified on the listed HANDLE commands can be raised, these HANDLE commands have no impact on program execution and will not appear in the structured program.
RESPONSE: None -- informational message only.
I The conditions listed below cannot be raised by any CICS HANDLE commands in the input program. In structure mode, these conditions are deleted from the CICS HANDLE command in the output program. The conditions are listed with the input program line numbers of the CICS HANDLE command on which they were specified.
EXPLANATION: Each condition listed below was specified on a HANDLE command, but cannot be raised. These conditions have no impact on program execution and will not appear on a HANDLE command in the structured program..
RESPONSE: None -- informational message only.
S Illegal intermediate form.
EXPLANATION: PCS produced illegal internal representation of input program.
RESPONSE: Check to see that all PCS requirements have been satisfied. If so, contact your IBM Product Support Center.
S An infinite loop exists in the input program that only passes through labels and GO TOs. This loop must be eliminated or a statement must be inserted in this loop before PCS processing can continue.
EXPLANATION: An infinite loop exists that passes only through labels and GO TO statements.
RESPONSE: Look at the Reengineering Report for possible infinite loop identification. Eliminate the infinite loop or insert a statement in the infinite loop.
S Input program too large for structuring.
EXPLANATION: The input program is too large or too complex for PCS to structure.
RESPONSE: Segment the largest procedure(s) in the input program and run PCS again.
W Each of the following is a line number of the input program that contains a predicate whose true and false branches proceed to the same place. These "useless predicates" do not appear in the output program. You may want to examine each useless predicate to ensure that it has absolutely no function; that it could not cause a divide-by-zero abend during evaluation, for example. If the predicate had any function, you should code a statement on one of its branches so that it is no longer useless,
then invoke PCS with the modified program.
EXPLANATION: PCS discovered one or more useless predicates in the input program but did not replicate them in the output program.
RESPONSE: See message text.
I One or more infinite loops were discovered in the input program. You may want to examine the loops to ensure that they are intended. Refer to the Reengineering Report for more details.
EXPLANATION: PCS discovered one or more infinite loops in the input program. The infinite loops appear in the output program.
RESPONSE: See the Reengineering Report for more information. If the infinite loops were not intended, correct them.
E No Data Division entry was found for one or more data items used by PCS-transformed PERFORM . . . VARYING statements. You will need to replace with SET statements any of these MOVE statements that reference index data items to make your program compilable. You should use your compiler to locate any such statements.
EXPLANATION: PCS produced MOVE statements containing input program data items for which no Data Division entry was found.
RESPONSE: Replace with SET statements any of these MOVE statements that reference index data items.
I The following input program line numbers represent lines of code that are unreachable regardless of the data. You may want to examine the unreachable code in the input program to ensure that it is intended. Code that is unreachable depending on data values is not reported and will appear in the output program.
EXPLANATION: Line numbers were reported for lines of the input program that contain unreachable code.
RESPONSE: Examine the input program to ensure that the unreachable code is intended. If it is not, correct the input program.
I The following are the names of input program procedures that can never be invoked regardless of the data values. You may want to examine these unreachable procedures to ensure that they are needed. Procedures that cannot be invoked depending on data values are not reported and will appear in the output program.
EXPLANATION: Names and input program line numbers of unreachable procedures were reported.
RESPONSE: Examine the input program to ensure that unreachable procedures are intended. If they are not, correct the input program.
I The input program can terminate abnormally by running off the end of the program. The output program will simulate this condition.
EXPLANATION: In OS/VS or DOS COBOL, VS COBOL II Release 2, and VS COBOL II Release 3 (with CMPR2), running off the end of a program causes an abend. To simulate this condition, the following statement was inserted in the output program: CALL CSF-ILBOABN0USING CSF-FALL-OFF-END. In VS COBOL II Release 3 (with NOCMPR2), running off the end of a program causes implicit execution of an EXIT PROGRAM statement. To simulate this condition, the following statements were inserted in the output program:
EXIT PROGRAM and CALL CSF-ILBOABN0 USING CSF-FALL-OFF-END.
RESPONSE: Examine the output program to ensure that the paths in the program logic that may cause abends are intended. If any are not, correct the logic either in the input program and invoke PCS with the corrected input program, or in output program.
I The input program can terminate abnormally by encountering targetless GO TO statements that have not been altered. To simulate this abend condition, CALL CSF-ILBOABN0 has been inserted where required.
EXPLANATION: A statement that causes an abend was inserted on one or more lines of the output program.
RESPONSE: Examine the output program to ensure that the paths in the program logic that may cause abends are intended. If any are not, correct the logic either in the input program and invoke PCS with the corrected input program, or in the output program.
I SORT/MERGE procedure(s) have been placed at the end of the output program.
EXPLANATION: The output program contains SORT and/or MERGE procedures that are required to be sections. You chose to have output program procedures structured as paragraphs, so the SORT/MERGE procedures had to be placed at the end of the output program.
RESPONSE: None -- informational message only.
I Procedure name prefixes were not stripped because the input program has DBCS labels.
EXPLANATION: You selected the "Replace prefixes" option. Due to DBCS labels in the input program, this request could not be performed.
RESPONSE: None -- informational message only.
I Procedure name prefixes were not added because the input program has DBCS labels.
EXPLANATION: You selected the "Add PCS prefixes" option. Due to DBCS labels in the input program, this request could not be performed.
RESPONSE: None -- informational message only.
S Line %1, symbol %2: A syntax error was found on this symbol.
EXPLANATION: PCS found a syntax error. This symbol may have caused the error, or the error may have occurred several symbols before the listed symbol.
RESPONSE: Correct the symbol or symbols that caused the error.
S Line %1: An infinite loop exists in the input program that only passes through labels and GO TOs. Label %2 is involved in the infinite loop. This loop must be eliminated or a statement must be inserted in this loop before PCS processing can continue.
EXPLANATION: An infinite loop exists that passes only through labels and GO TO statements.
RESPONSE: Look at the Reengineering Report for possible infinite loop identification. Eliminate the infinite loop or insert a statement in the infinite loop.
(.txt)