HP NonStop Pathway/iTS SCUP Reference Manual Abstract This manual describes the SCREEN COBOL Utility Program (SCUP), a utility that enables SCREEN COBOL application programmers to control and manipulate SCREEN COBOL object files and to convert SCREEN COBOL object programs to web clients. Product Version Pathway/iTS 1.0 and 1.1 Supported Release Version Updates (RVUs) This publication supports J06.03 and all subsequent J-series RVUs, H06.03 and all subsequent H-series RVUs, and G05.
Document History Part Number Product Version Published 127342 Pathway/TS D42 August 1996 426747-001 Pathway/iTS 1.0 October 2000 520269-001 Pathway/iTS 1.0 Update June 2001 520269-002 Pathway/iTS 1.0 and 1.
Legal Notices Copyright 2010 Hewlett-Packard Development Company L.P. Confidential computer software. Valid license from HP required for possession, use or copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor's standard commercial license. The information contained herein is subject to change without notice.
HP NonStop Pathway/iTS SCUP Reference Manual Index Figures Tables Legal Notices What’s New in This Manual iii Manual Information iii New and Changed Information About This Manual v Related Documentation v Notation Conventions vii HP Encourages Your Comments iii x 1.
2. SCUP Commands (continued) Contents 2. SCUP Commands (continued) CMDSYS Command 2+\8 CMDVOL Command 2+\9 COMPRESS Command 2+\9 CONVERT Command 2+\10 COPY Command 2+\25 DELETE Command 2+\27 EXIT Command 2+\28 FC Command 2+\28 FILE Command 2+\29 HELP Command 2+\31 INFO Command 2+\31 OBEY Command 2+\34 OBEYSYS Command 2+\35 OBEYVOL Command 2+\35 OUT Command 2+\36 SYSTEM Command 2+\36 VOLUME Command 2+\38 3. Using SCUP A.
What’s New in This Manual Manual Information HP NonStop Pathway/iTS SCUP Reference Manual Abstract This manual describes the SCREEN COBOL Utility Program (SCUP), a utility that enables SCREEN COBOL application programmers to control and manipulate SCREEN COBOL object files and to convert SCREEN COBOL object programs to web clients. Product Version Pathway/iTS 1.0 and 1.1 Supported Release Version Updates (RVUs) This publication supports J06.03 and all subsequent J-series RVUs, H06.
What’s New in This Manual • Changes to the 520269-001 Manual Changed “Compaq NonStop Kernel Operating System” to “HP NonStop Operating System”. Changes to the 520269-001 Manual The Compaq NonStop™ Pathway/iTS product was formerly called Pathway/TS. For the Pathway/iTS 1.0 independent product release, the product was renamed to conform to current Compaq product naming standards and to reflect the internet (web client) capabilities of the product.
About This Manual This manual describes the SCREEN COBOL Utility Program (SCUP), which enables SCREEN COBOL application programmers to control and manipulate SCREEN COBOL object files. The manual includes SCREEN COBOL object file handling concepts, SCUP commands available for object file manipulation, and examples that demonstrate general SCUP usage.
Related Documentation About This Manual Pathway/iTS Management Programming Manual Describes the management programming interface for Pathway/iTS objects in the PATHMON environment. Pathway Products Glossary Defines Operator Messages Manual technical terms used in this manual and in other manuals for the Pathway products: Pathway/iTS, NonStop TS/MP, and Pathway/XM.
Notation Conventions About This Manual Notation Conventions General Syntax Notation The following list summarizes the notation conventions for syntax presentation in this manual. UPPERCASE LETTERS. Uppercase letters indicate keywords and reserved words; enter these items exactly as shown. Items not enclosed in brackets are required. For example: MAXATTACH lowercase italic letters. Lowercase italic letters indicate variable items that you supply. Items not enclosed in brackets are required.
General Syntax Notation About This Manual braces on each side of the list, or horizontally, enclosed in a pair of braces and separated by vertical lines. For example: LISTOPENS PROCESS { $appl-mgr-name } { $process-name } ALLOWSU { ON | OFF } | Vertical Line. A vertical line separates alternatives in a horizontal list that is enclosed in brackets or braces. For example: INSPECT { OFF | ON | SAVEABEND } … Ellipsis.
Notation for Messages About This Manual Notation for Messages The following list summarizes the notation conventions for the presentation of displayed messages in this manual. Nonitalic text. Nonitalic letters, numbers, and punctuation indicate text that is displayed or returned exactly as shown. For example: Backup Up. lowercase italic letters. Lowercase italic letters indicate variable items whose values are displayed or returned. For example: p-register process-name [ ] Brackets.
Change Bar Notation About This Manual Change Bar Notation Change bars are used to indicate substantive differences between this manual and its preceding version. Change bars are vertical rules placed in the right margin of changed portions of text, figures, tables, examples, and so on. Change bars highlight new or revised information. For example: The message types specified in the REPORT clause are different in the COBOL85 environment and the Common Run-Time Environment (CRE).
1 Introduction to SCUP Introduction to SCUP The SCREEN COBOL Utility Program (SCUP) simplifies your task of maintaining SCREEN COBOL object library files.
Introduction to SCUP Introduction to SCUP For example, executing the command SCOBOLX/IN TESTFILE/ MANUF; causes SCREEN COBOL to compile SYMBOLS the program in TESTFILE, and to generate directory entry MANUFDIR, object code file MANUFCOD, and symbol table MANUFSYM. SCUP automatically processes all three associated object files. A diagram of SCREEN COBOL object files is shown in Figure 1-1. Figure 1-1.
Converting SCREEN COBOL Programs to Web Clients Introduction to SCUP Converting SCREEN COBOL Programs to Web Clients SCUP lets you convert a SCREEN COBOL application (a group of related program units within an object library) to a web client without making any changes to the SCREEN COBOL source code. Requester-based business logic is converted to Java classes; screen components are converted to HTML pages with embedded JavaScript code.
Controlling TCP Access Introduction to SCUP • • • • • Name of the program (taken from the PROGRAM-ID paragraph in the Identification Division) Access flag for the program unit Version of the program Location and size in the code file where the program object code is stored Flag that indicates whether a symbol table exists for the SCREEN COBOL program When displaying information about the contents of a SCREEN COBOL object file, SCUP retrieves some of the information from the directory file and retrieves
Copying Programs Introduction to SCUP Figure 1-2. Directory File with Access Flags Shown MANUFDIR OFF ON ON ON OFF ON ON OFF ON ON C(1) C(2) Library A(1) A(2) A(3) A(4) B(1) B(2) B(3) SYM SYM Access MANUFCOD Code for A(1) Code for C(1) Code for A(2) Code for Code for A(3) B(1) Code for B(2) Code for A(4) Code for C(2) Code for B(3) MANUFSYM Symbol Table Symbol Table for C(1) for C(2) VST002.vsd Copying Programs You can copy programs from one object file to another.
Compressing Programs Introduction to SCUP Figure 1-3. Code and Directory Files With Deleted Programs MANUFDIR ON A(1) ON A(2) ON A(3) OFF A(4) ON B(1) OFF B(3) ON C(2) SYM Deleted MANUFCOD Code for A(1) Code for C(1) Code for A(2) Code for A(3) Code for B(1) Code for B(2) Code for A(4) Code for C(2) Code for B(3) Deleted MANUFSYM Symbol Table Symbol Table for C(1) for C(2) VST003.vsd Compressing Programs The space occupied by a deleted version of a program remains part of the code file.
SCUP Version Compatibility Introduction to SCUP Figure 1-4.
Introduction to SCUP SCUP Version Compatibility HP NonStop Pathway/iTS SCUP Reference Manual—520269-002 1 -8
2 SCUP Commands SCUP commands are divided into two categories: • • Utility commands, which are associated with use of the SCUP utility Basic commands, which are associated with control of the SCUP utility A complete list of available commands appears in Table 2-1 and Table 2-2. Table 2-1. SCUP Utility Commands Command Description ALTER Changes either the accessibility of SCREEN COBOL program units or the access setting of the SCREEN COBOL library.
SCUP Utility Commands SCUP Commands All commands can include comments. Comments must be delimited by a space followed by the double hyphen (--) symbol. The double hyphen symbol and all subsequent characters up to the next double hyphen, or the end of the effective record, are ignored. SCUP Utility Commands SCUP utility commands allow you to access and manipulate compiled programs in the SCREEN COBOL object files.
File-Name Expansion Within OBEY files SCUP Commands File names of disk files are represented to subsystem programs by these parts concatenated into a contiguous string with each part separated from the other by a period: \system-name.$volume-name.subvolume-name.disk-file-name When only a partial file name is supplied as a command parameter, the internal representation of the file name is expanded into the full four-part file name. As a minimum, a partial file name must consist of disk-file-name.
File-Name Expansion for Object-File Names SCUP Commands File-Name Expansion for Object-File Names File-name expansion for a SCREEN COBOL object-file name also is controlled by the CMDSYS and CMDVOL commands. This is a special case of command file-name expansion because the SCREEN COBOL compiler generates three object-file names. The SCREEN COBOL short-form file name has the form of a disk-file name: [\system.][$volume.][subvol.
Interactive Mode SCUP Commands command is a SCUP command. When commands are present, SCUP executes the commands and terminates without reading command-file. The following applies to the OUT option of the SCUP command: • • • If the OUT file specification is a disk file name and the file already exists, the listing is appended to the file. If the OUT file specification is a disk file name and the file does not exist, an EDIT file is created.
Noninteractive Mode SCUP Commands Noninteractive Mode SCUP functions in noninteractive mode when commands are entered through a command file. For example: 1> scup / IN command-file / In this example, SCUP reads commands from a command file. When an end-of-file or an EXIT command is encountered, SCUP terminates and the command interpreter is activated. Command Descriptions SCUP utility and basic commands are described in the following paragraphs. Command descriptions appear in alphabetic order.
ALTER Command SCUP Commands (program-name) is a SCREEN COBOL program name. The program name can be a single program name or several program names separated by commas. (*) is all program names in the object file. If program-name or * is omitted, the ALTER command changes the access setting for the library in the object file control record. This setting determines the access of all programs subsequently added to the object file. (version) is the version of the specified program name.
ASSUME Command SCUP Commands The following example of the ALTER command makes the latest version of the program test-prog1 and all versions of test-prog2 inaccessible to the PATHWAY system: ALTER scobj (test-prog1,test-prog2(*)), ACCESS OFF The following example of the ALTER command makes the second version of the program test-prog3 accessible to the PATHWAY system: ALTER scobj (test-prog3(2)), ACCESS ON The following example of the ALTER command designates ACCESS OFF for the object file.
CMDVOL Command SCUP Commands system name. Omitting the system name in this command permits references to long device names; long device names are prohibited in network-form file names. If the specified system name is invalid, or would be invalid when combined with the current CMDVOL setting, an error occurs. An error message is displayed and the CMDSYS setting is not changed.
CONVERT Command SCUP Commands file-name is a SCREEN COBOL object file name. If the file-name option is omitted, the file specified in the FILE command is used. The COMPRESS command renumbers the version numbers of the existing program in the object file without reordering the version priority; the earliest version is always 1. For example, assume POBJ contains four versions of a program and version 3 is deleted, leaving versions 1, 2, and 4.
CONVERT Command SCUP Commands CONVERT [ SCOBOL-OBJECT ] [ file-name ] [ , pobj-spec ] , INITPROG program-id [ , CONFIGFILE config-file [ , APPNAME app-name [ , JAVAVOL [\system.]$volume.subvol [ , HTMLVOL [\system.]$volume.subvol [ , CHARSET SJIS ] ] ] ] ] pobj-spec is: prog-name [ , prog-name ]... prog-name is: ( { program-id } [ ( version ) ] ) { * } file-name is the first four characters of the SCREEN COBOL object-file name. If this parameter is omitted, the currently opened file is used.
CONVERT Command SCUP Commands INITPROG program-id identifies the program ID of the first program unit to be executed. This is similar to the INITIAL attribute of the TERM object in a Pathway configuration. The corresponding Java code will be the first code to be executed in the web client. This parameter is required; if it is omitted, the converter generates an error. The converter uses the program-id value to trace the program logic to identify all the program units.
CONVERT Command SCUP Commands CHARSET SJIS specifies that the SCOBOL program being converted contains Japanese kanjikatakana characters.
CONVERT Command SCUP Commands Configuration File Format The configuration file specified in the CONFIGFILE parameter provides default values that are used by the converter. The file format is similar to that of an .INI file. It has multiple sections, each consisting of a section heading followed by a list of name-value pairs, as follows: "["section-name"]" [ name = value ; ]... "["section-name"]" [ name = value ; ]... "["section-name"]" [ name = value ; ]... "["section-name"]" [ name = value ; ]...
CONVERT Command SCUP Commands Screen Section Parameters The Screen section contains parameters related to the presentation (display appearance) of the converted web client. The following table describes each parameter, its valid values, and its default value. The default value is used if no configuration file is specified or if that parameter is not specified in the configuration file.
CONVERT Command SCUP Commands type or size in the configuration file and convert the application again, then deploy the new HTML pages and discard the Java files. Note. When you specify a GIF file name in the Background parameter, specify only the file name; do not include the path. Ensure that at deployment time, the specified GIF files are available at the location where the converted HTML files are placed.
CONVERT Command SCUP Commands Deployment Environment Section Parameters Note. The Deployment Environment section is not currently used by the converter or by JMAKENV. This section is defined for future use. The Deployment Environment section contains parameters related to the environment where the converted application will be deployed. The following table describes each parameter, its valid values, and its default value.
CONVERT Command SCUP Commands Parameter Name Valid Values Default Value ON ERROR CLAUSES 0 - 32767 500 Maximum number of ON-ERROR clause count in a program unit. OVERLAY AREAS 0 - 32767 1000 Maximum number of overlay areas per program unit. PARAGRAPHS 0 - 32767 1000 Maximum number of paragraphs per program unit. PERFORM DEPENDING OPCODES 0 - 32767 300 Maximum number of PERFORM DEPENDING statements in a program unit.
CONVERT Command SCUP Commands Summary Information After converting individual program units, the converter generates a brief summary about the conversion that includes the following: • Unsupported Statements This is the number of unsupported statements that the converter detected during the conversion and includes the following types: • • • Warnings: The number of warning messages detected by the converter.
CONVERT Command SCUP Commands The following is a typical example of the Total summary: Total Summary for CONVERT command Unsupported Statements : 4 Warnings : 1 Errors : Internal Errors : 0 3 Operational Details General The CONVERT command converts the Working-Storage Section and Procedure Division components of the SCREEN COBOL program units to Java classes and includes the necessary classes from the Pathway/iTS Java import library.
CONVERT Command SCUP Commands Restrictions The following restrictions apply to the conversion process: • • • The converter works with block-mode non-IDS SCREEN COBOL program units only. Symbol information for the program units must be available in the POBJSYM file, which must reside in the same volume and subvolume as the SCREEN COBOL object file. The CONVERT command supports up to 15 levels in a group data declaration, whereas the Screen COBOL language supports up to 48 levels.
CONVERT Command SCUP Commands 1. Comment out the statements of the method in the generated Java file after the return statement, then recompile the Java code. • No such method error Cause: Occasionally, the converter cannot distinguish between the section name and the first paragraph name within the section, and generates the error No such method. Recovery: Manually check the generated code.
CONVERT Command SCUP Commands Cause. SCUP returns this error when you attempt to reconvert a program unit of the existing SCOBOL object after transferring the Java, HTML, and MAP files from the original location to another location. SCUP purges the original files and then re-creates them to reflect the changes. If SCUP is not able to locate any of the original files mentioned in the MAP file for purging, it returns this error. Recovery. Complete the following steps: 1.
CONVERT Command SCUP Commands file mycfg. The converted Java files are created in $abc.java, and the HTML files are stored in $abc.html, both on the current system. CONVERT defg (*(1)), INITPROG myprog, CONFIGFILE mycfg, & APPNAME myapp, JAVAVOL $abc.java, HTMLVOL $abc.
COPY Command SCUP Commands COPY Command The COPY command copies a set of programs from one SCREEN COBOL object file to another. If a program named in the COPY command has an associated entry in the symbol table file, the symbol table is copied to the destination symbol table file. COPY [ SCOBOL-OBJECT ] [ source-file-name ] { ( program-name [ ( version ) ] } { [ , program-name [ ( version ) ] ] ...
COPY Command SCUP Commands program name in the object file. The old and new program name and version numbers are displayed after the copy operation is complete. If two or more versions of the same program are specified in the COPY command, the last program specified becomes the latest version in the destination object file. This gives you control over the priority assigned to program versions when copying from one file to another.
DELETE Command SCUP Commands TEST (4) TEST (5) TEST (2) TEST (3) The following example copies the latest versions of program TEST into FILE2. COPY file1(*), file2 $MKT.OLDSV.FILE1 COPY TO $MKT.OLDSV.FILE2 EXTENTS: DIR(00016,00032) COD(00032,00064) SYM(00032,000128) TEST1 (2) TEST1 (1) TEST3 (1) TEST3 (1) TEST7 (2) TEST7 (1) DELETE Command The DELETE command removes programs from the SCREEN COBOL object file directory; the code and symbol table file space is not reclaimed.
EXIT Command SCUP Commands previous version becomes the latest version. The deleted program name and version number are displayed after the DELETE operation is performed. When executing a DELETE command, SCUP allows shared access to the SCREEN COBOL object file. From the moment the DELETE command completes, any attempt to find the specified programs (either through the CALL verb in a SCREEN COBOL program or through the INITIAL setting when starting a terminal) will fail.
FILE Command SCUP Commands Subcommands and their associated strings are entered beneath the displayed command line and terminated with a carriage return. Replacement, insertion, and deletion begins with the character positioned directly above the subcommand (R, I, D). Subcommand R replaces characters in the command line with replacement-string on a one-for-one basis. Subcommand I inserts characters in the command line with insertion-string on a one-for-one basis.
FILE Command SCUP Commands The SCREEN COBOL compiler names the object files POBJCOD, POBJDIR, and POBJSYM (if the SYMBOLS compiler command was specified) within the default system, volume, and subvolume.
HELP Command SCUP Commands HELP Command The HELP command displays the syntax of SCUP commands. HELP [ command-name ] [ < param-name > ] command-name is the name of a SCUP command for which the syntax is displayed. < param-name > is any parameter value that is enclosed in angle brackets when displayed by the command-name option. The angle brackets must be included. If parameters are omitted, the names of all SCUP commands are displayed.
INFO Command SCUP Commands If this parameter is omitted, the file specified in the FILE command is used. (program-name) is a SCREEN COBOL program name. The program name can be a single program name or several program names separated by commas. (*) is all program names in the object file. If program-name or * (for a program name) is omitted, no information about programs in the object file is displayed. (version) is the version of a specified program name.
INFO Command SCUP Commands The following example displays information about all versions of a program called TEST-PROG. INFO $data.subvol.file1 (test-prog:(*)) $DATA.SUBVOL.
OBEY Command SCUP Commands The following example displays detailed information about the latest version of the program called TEST-PROG: ?INFO $data.subvol.file1 (test-prog), DETAIL $DATA.SUBVOL.
OBEYSYS Command SCUP Commands the original input file for SCUP was a terminal, the terminal is issued a prompt. If the input file was not a terminal, SCUP terminates. The following are examples of the OBEY command: OBEY abc.scupcmd OBEY scupcmd OBEYSYS Command The OBEYSYS command sets the default system for expansion of obey file names. OBEYSYS [ \system ] system is a Guardian node name. If the OBEYSYS command is not issued, the default settings in effect when SCUP was started are used.
OUT Command SCUP Commands previous setting applies. If both names are omitted and the file from which the OBEYVOL command was read is a disk file, the defaults for obey file-name expansion are set to the system, volume, and subvolume of the current command input file. If both names are omitted and the file from which the OBEYVOL command was read is not a disk file, an error occurs; an error message is displayed and the OBEYVOL defaults are not changed.
SYSTEM Command SCUP Commands The following are examples of the SYSTEM command: SYSTEM \ny SYSTEM \sd HP NonStop Pathway/iTS SCUP Reference Manual—520269-002 2- 37
VOLUME Command SCUP Commands VOLUME Command The VOLUME command sets the default volume and subvolume for expansion of any file names. VOLUME { $volume } { [ $volume. ] subvol } volume is a Guardian volume name. subvol is a Guardian subvolume name. A VOLUME command is equivalent to entering both an OBEYVOL and a CMDVOL command with the same specification. Note that this does not necessarily mean that the settings for OBEYVOL and CMDVOL would be identical following a VOLUME command.
3 Using SCUP This section illustrates the use of the SCUP utility to control and manipulate SCREEN COBOL object files. The examples show building a new SCREEN COBOL object file ($DATA.NEWSV.POBJ) from selected program units in two existing SCREEN COBOL object files ($DATA.OLDSV.POBJ and $MKT.OLDSV.SCOB). Note. This section does not describe use of the CONVERT command.
Using SCUP • The DELETE command deletes all versions except the latest version of program FUNC-PROG in object file $MKT.OLDSV.SCOB. ?delete $mkt.oldsv.scob (func-prog(+)) $MKT.OLDSV.SCOB DELETED FUNC-PROG (1) DELETED FUNC-PROG (2) • The ALTER command sets to OFF the access to version 2 of program TESTPROG in object file $DATA.OLDSV.POBJ. The OFF setting makes the version unavailable to the TCP for execution in the PATHWAY system. ?alter (test-prog(2)), access off $DATA.OLDSV.
Using SCUP FUNC-PROG (4) COMPRESSED $MKT.OLDSV.SCOB • FUNC-PROG (1) The FILE command sets the default object file name to $DATA.NEWSV.POBJ, making the files POBJCOD and POBJDIR the default SCREEN COBOL object files. ?file $data.newsv.pobj FILE IS $DATA.NEWSV.POBJ • The ALTER command sets to OFF the access to the latest version of program TEST-PROG in object file $DATA.NEWSV.POBJ. ?alter (test-prog), access off $DATA.NEWSV.
Using SCUP HP NonStop Pathway/iTS SCUP Reference Manual—520269-002 3 -4
A SCUP Messages The SCUP program displays diagnostic messages during various phases of processing. This appendix describes two types of SCUP messages: • • General SCUP messages, which can be returned from a number of different commands Converter messages, which can be returned during conversion of a SCREEN COBOL requester to a web client by means of the CONVERT command SCUP messages consist only of displayed text, with no visible message numbers.
General SCUP Messages SCUP Messages ERROR - ILLEGAL CHARACTER Cause. The command contained an illegal character. Effect. The command fails. Recovery. Remove the illegal character. ERROR - ILLEGAL ENTRY Cause. The HELP command contained an illegal entry. Effect. The command fails. Recovery. Specify a valid HELP command entry. The HELP command accepts only SCUP command names and symbol names enclosed in angle brackets. ERROR - ILLEGAL NAME Cause. The command contained an illegal name. Effect.
General SCUP Messages SCUP Messages ERROR - ILLEGAL SYNTAX Cause. The command contained illegal syntax. Effect. The command fails. Recovery. Correct the command syntax. ERROR - OBEY LIMIT EXCEEDED Cause. The limit of four nesting levels for the OBEY command was exceeded. Effect. The command fails. Recovery. Reduce the number of OBEY commands that call files containing OBEY commands. ERROR - PROGRAM NAME NOT IN FILE - program-name (version-number) Cause.
General SCUP Messages SCUP Messages Recovery. Change one of the file names. FILE ERROR - file-name - message (errnum) Cause. A file-system or sequential I/O procedure error (identified by message and errnum) occurred during operation of the command. Effect. The command fails. Recovery. Refer to the description of the file-system error in the Guardian Procedure Errors and Messages Manual and take corrective action as specified. FILE NAME ERROR - file-name (errnum) Cause.
General SCUP Messages SCUP Messages SYSTEM NAME ERROR (system-num) Cause. An invalid system name was entered. Effect. The command fails. Recovery. Check the specified system name for accuracy and correct it as needed. SYSTEM NOT ACCESSIBLE Cause. The named system could not be accessed by the user. The system might not be on the network. Effect. The command fails. Recovery. Correct the network problem. VOLUME NAME ERROR (system-num) Cause. An invalid volume name was entered. Effect. The command fails.
Converter Messages SCUP Messages Converter Messages The following messages can be issued by the SCUP converter during the operation of the CONVERT command, which converts a SCREEN COBOL requester to a web client.
Converter Messages SCUP Messages If your local operating procedures require contacting the HP Global Customer Support Center (GCSC), supply your NonStop system number and the numbers and versions of all related products as well. Error - APPNAME app-name mismatch. A prior version of the converted software exists with a different value for the APPNAME parameter. Cause. A prior attempt was made to convert the application by specifying the same INITPROG parameter but with a different APPNAME parameter.
Converter Messages SCUP Messages Effect. The conversion fails. Recovery. Refer to the description of the file-system error in the Guardian Procedure Errors and Messages Manual and take corrective action as specified. Restart the conversion. Error - INITPROG program-id mismatch. A prior version of the converted software exists with a different value for the INITPROG parameter. Cause. A prior attempt was made to convert the application by specifying a different value for the INITPROG parameter. Effect.
Converter Messages SCUP Messages Cause. The converter could not open the specified configuration file because of the indicated file-system error. Effect. The conversion fails. Recovery. Refer to the description of the file-system error in the Guardian Procedure Errors and Messages Manual and take corrective action as specified. Restart the conversion. Error - Section section-name not found in configuration file config-file Cause. The specified section name was not found in the configuration file.
Converter Messages SCUP Messages Error - Program unit compiled with pre C20 version compiler Cause. An attempt was made to convert a program unit that had been compiled with a C20 or earlier version of the SCREEN COBOL compiler. Effect. The conversion fails. Recovery. Compile the SCREEN COBOL source using a compiler whose version is C30 or later, then reconvert the application. Error - Purge error for the file file-name (errnum) Cause.
Converter Messages SCUP Messages • • If errnum is specified in the message, refer to the description of the file-system error or sequental I/O error in the Guardian Procedure Errors and Messages Manual and take corrective action as specified. Then restart the conversion. If no corrective action is possible, contact your service provider. If no errnum is specified, the HTML files generated thus far are named SCRNnnnn, where nnnn is a value from 0000 and 9999.
Converter Messages SCUP Messages Cause. The converter encountered a SCREEN COBOL statement that is not supported for conversion. The following statements are not supported for conversion and can appear in this message: DEVICEINFO RECEIVE UNSOLICITED MESSAGE REPLY UNSOLICITED MESSAGE SEND MESSAGE TERMINALINFO RESTART-TRANSACTION Effect. The conversion program continues with the conversion; however, the converted program unit does not compile correctly. Recovery.
Converter Messages SCUP Messages HTML file error for html-file-name (errnum) Cause. A file-system error or sequential I/O error (identified by errnum) occurred while the converter was writing the HTML source file specified by html-file-name. Effect. The conversion fails for that program unit. Recovery. Refer to the description of the file-system error or sequental I/O error in the Guardian Procedure Errors and Messages Manual and take corrective action as specified. Then restart the conversion.
Converter Messages SCUP Messages Effect. The conversion continues after generating the warning. The application will fail at run time if the program units identified by the specified program-ids are not converted. Recovery. Include the missing program units in the current POBJ file and reconvert the application. Warning - Unable to resolve program units used in CALL working-storage statement Cause. The converter traces the call sequence in the POBJ file starting with the INITPROG.
Converter Messages SCUP Messages Warning - Unsupported statement encountered during conversion of program unit program-unit: unsupported-statement Cause. The converter encountered a SCREEN COBOL statement that is not supported for conversion. The following statements are not supported for conversion and can appear in this message: CHECKPOINT DISPLAY RECOVERY EXIT RECOVERY PRINT SCREEN RECONNECT MODEM SCROLL USE Effect. The conversion program continues with the conversion.
Converter Messages SCUP Messages HP NonStop Pathway/iTS SCUP Reference Manual—520269-002 A -16
Index A access flags for TCPs 1-4, 2-6 ACCESS parameter, ALTER command 2-7 alignment of screen fields 2-15 ALTER command 2-1, 2-6 application name, used during conversion 2-12 APPNAME mismatch… (error message) A-7 APPNAME parameter, CONVERT command 2-12 ASSUME command 2-1, 2-8 B background parameter 2-15 BREAK key 2-5 C CALLED PROGRAM UNITS parameter 2-17 CHARSET SJIS parameter, CONVERT command 2-13 CMDSYS command 2-1, 2-8 CMDVOL command 2-1, 2-9 COD (code) file 1-1 code file compressed programs 1-6 delet
D Index Configured limit violation… (error message) A-7 Continuation limit exceeded (error message) A-1 Continuation line is EOF (error message) A-1 continuing commands 2-5 controlling TCP access 1-4 CONVERT command description 2-1, 2-10 error and warning messages A-6 example commands 2-23 Java classes and HTML files generated 2-20 restrictions 2-21 summary 2-19 summary example 2-19 troubleshooting 2-21 Convert Environment section parameters 2-16 Converter internal error (error message) A-6 Converting SCR
I Index HTMLVOL parameter, CONVERT command 2-12 I Illegal character (error message) A-2 Illegal entry (error message) A-2 Illegal name length (error message) A-2 Illegal name (error message) A-2 Illegal numeric length (error message) A-2 Illegal syntax (error message) A-3 INDEX RESOLVING OPCODES parameter 2-17 INFO command 2-1, 2-30 initial program unit, during conversion 2-12 INITPROG mismatch… (error message) A-8 INITPROG not found in file (warning message) A-13 INITPROG parameter, CONVERT command 2-12
R Index Program unit compiled with pre C20 version… (error message) A-10 Program version not in file (error message) A-3 Purge error for the file (error message) A-10 R reclaiming object file space 1-6 REDEFINES parameter 2-18 RUN command 2-4 running SCUP 2-4, 3-1 S SCREEN COBOL object files access flags 2-6 code file name (COD) 1-1 compressing 1-6 contents 1-1 converting to web clients 1-3, 2-10 copying programs 1-5, 2-10 default file names 2-3 deleting programs 1-5, 2-26 directory file name (DIR) 1-1
U Index U Unable to allocate flat segment (error message) A-10 Unable to create HTML file (error message) A-10 Unable to create Java file (error message) A-11 Unable to deallocate flat segment (error message) A-11 Unable to resolve program units… (warning message) A-14 Unsupported statement encountered… (error message) A-12 Unsupported statement encountered… (warning message) A-15 V version numbers 1-3 VOLUME command 2-1, 2-37 Volume name error (error message) A-5 W web clients, converting SCREEN COBOL
Special Characters Index HP NonStop Pathway/iTS SCUP Reference Manual—520269-002 Index -6
