2 Migrating HP 260 Applications

Completing HP 260 Program Analysis

Before continuing with this section, make sure you have done the following:

1 Used the BINCHK program to check the HP 260 programs you intend to transfer to the HP 9000 Series 800.

2 Removed binary code from the HP 260 programs to be transferred.

3 Transferred your HP 260 applications from the HP 260 to the HP 9000 Series 800.

If you have completed the above steps, you are ready to complete the program analysis process.

list

The list command is used after the program (.PROG) files are transferred from the HP 260 to the HP 9000 Series 800.

The purpose of the list command is to make ASCII text files from the program files. This is a preliminary step to using the Eloquence stmtcheck command. Use the list command in the following manner:

list programname > textfilename

Refer to the Eloquence Manual for information on the options available with the list command.

By diverting the output to textfilename you now have available a source listing of the program as an ASCII text file.

To speed up this process, it is possible to write a script file that will convert all program (.PROG) files in the specified directory to ASCII text files named filename.txt. You might call this script file list_all. This is sure to be of assistance in the first phase of migration. Here is an example list_all script file:


for i in *.PROG
do
list $i > 'basename $i .PROG'.txt
done

stmtcheck

The next step is to check the text files for critical statements. Critical statements are those HP 260 statements that are not implemented or work differently in Eloquence. This check is done using the Eloquence stmtcheck command. Use the stmtcheck command in the following manner:

stmtcheck textfilename

This checks the named text file for critical statements. If any are found, the program and the program lines containing the critical statements are indicated. If you need a hard copy of this, use the following command sequence:

stmtcheck textfilename | lp

The added | lp sends the result of the stmtcheck to the default printer.

The stmtcheck program also works with wildcard characters. This simplifies the stmtcheck process. For example, if all the text files you created with list have the extension .txt, the command stmtcheck *.txt can be executed. This will cause all files in the current directory with the extension .txt to be checked, and therefore prevent executing the stmtcheck command for each text file.

NOTE: Before using the stmtcheck program, verify that there is a file named .260stmt in your HOME directory or in the directory /opt/eloquence6/tools. If not, change to the directory /opt/eloquence6/tools and copy the file d.260stmt to .260stmt. The file .260stmt contains the critical statements that the stmtcheck program checks for.

Refer to page 25 for more information on the Eloquence stmtcheck command.

store

Once you know which statements, if any, need to be changed, you can either change the program (.PROG) within Eloquence or change the text file using any HP-UX editor. If you chose to make the changes within Eloquence, delete the text file to save disk space. If you chose to change the text file, you must use the store command after making your changes. The Eloquence store command converts the ASCII text file containing program source code to an Eloquence program (.PROG) file. For instructions on how to use this command, refer to the Eloquence manual.


HP260 to Eloquence Migration - 13 FEB 2003