ASG-Rochade SCANCOB Release Notes

Transcription

1 ASG-Rochade SCANCOB Release Notes Version March 8, 2007 CO This publication contains information about all modifications made to ASG-Rochade SCANCOB (herein called SCANCOB) since Version ISP Updates ASG encourages you to visit http// and sign onto the Intelligent Support Portal (ISP) to verify whether any product or documentation revisions, new maintenance, or service packs apply to this release of the product or its accompanying documentation. Product Information The SCANCOB scanner tool performs two major functions It inspects the source code to ensure that it conforms to your programming standards, and it extracts information about the relationships between your program and other system components for documentation purposes. The information provided by SCANCOB comprises an overview of the relationships between different programs, files, procedures, functions, and CICS/DL/I and DB2 elements, as well as information about file organization and file access. Enhancements and Changes Version Besides the job ROCOBSC, there is now an additional sample job, ROCOBSC7, for scanning JCL. It supports the improved mechanism offered by Version 7 of ASG-Rochade (herein called Rochade) for passing parameters to the client via a dataset defined through a PARMFILE DD statement. Copyright 2007 ASG GmbH & Co. KG, a wholly owned subsidiary of Allen Systems Group, Inc. All rights reserved. All names and products contained herein are the trademarks or registered trademarks of their respective holders. 1

2 Version This version contains a COBOL front end that processes Enterprise COBOL. It performs source code transformations before executing standard SCANCOB COBOL analysis. You can find the transformation rules in the member ECO#CO3 in <HLQ>.ROPROD.README. Note The Enterprise COBOL to COBOL II transformation approach is available in the z/os version of SCANCOB. Version These modifications and enhancements have been made to SCANCOB in Version Added parameters for SCANCOB CALLPARM Section <COPP> When scanning copy books standalone that contain replacing pattern in a form xxx, ASG recommends that you it specify parameter colon_as_char=2 in section <COPP>. The SCANCOB tokenizer will then treat a colon () as a normal character instead of a word separator. Section <COPA> These parameters have been added SPACE_MARKER=<character1><character2>... Defines characters that should be treated as blank when they occur in column 7. DEBUG_LINE_AS_CODE=0 1 With DEBUG_LINE_AS_CODE=1, DEBUG lines (character D in column 7) are treated as code lines. Otherwise, they are treated as comment lines. ONLY_COPYBOOKS=0 1 The parameter ONLY_COPY_BOOKS=1 should be set when you use SCANCOB to scan COBOL copy book libraries. 2

3 COPY_LEVEL=nn <unlimited> Use this parameter to suppress the copy book expansion at the defined level. COPY_LEVEL=0 means that SCANCOB does not expand copy books that are implemented in the source file. COPY_LEVEL=1 means that the first level is expanded but copy books included in an expanded copy book are not resolved, etc. NO_KEYWORDnn=<cobol word> Use this parameter when <cobol word> should not be treated as a COBOL keyword (e.g., NO_KEYWORD1=COLOR). IS_KEYWORDnn=<cobol word> Use this parameter when <cobol word> should be treated as a COBOL keyword. ASG recommends that you use this parameter when SCANCOB analysis sources with COBOL II dialect but some of the sources contain OS/VS COBOL keyword definitions. It is useful to define these keywords as predefined IS_KEYWORD2=REMARKS IS_KEYWORD3=EXHIBIT IS_KEYWORD4=RECURSIVE Section <REPLACING> with these parameters has been added For scanning copy books standalone that contain REPLACE/REPLACING pattern in a form (XXX), use section <REPLACING> to define a list of replacing patterns that might occur in the copy book definitions. REPLACE1=(PFX) REPLACE2=(XX1) REPLACE3=XX2 REPLACE4='XX3' REPLACE5=L- Section <GENERATOR> MIXEDCASE-FIELDS = YES NO With option YES, the string constants will not automatically be converted to uppercase. This parameter reflects working areas DAT-INI, VARINHA, and VARUSE. SCANCOB now suppresses information for each link qualifier when PARMS=NO is found in the CALLPARM file. 3

4 Version These modifications and enhancements have been made to SCANCOB in Version Enhanced processing of NAMFIL. A new parameter is available for use in NAMFIL. You can use the parameter SCANEXCLUDE to exclude members from the scan. Format SCANEXCLUDE=[pattern,] exclude_pattern where pattern defines a list of members in library SCANLIB. When a pattern is not defined, all members in SCANLIB are assumed. exclude_pattern defines a list of members, which is a subset of the members defined in pattern also that should not be scanned. Example 1 SCANLIB=LIB1 SCANEXCLUDE=*,*ABC Or SCANLIB=LIB1 SCANEXCLUDE=*ABC SCANCOB scans all members in LIB1 whose names do not end in ABC. Example 2 SCANLIB=LIB1 SCANEXCLUDE=A*,*10* SCANCOB scans all members in LIB1 whose names start with A except for those whose names also contain 10. The parameters CALL-VARIABLE and VARIABLE-CALL from section GENERATOR->CALL-EXTERN (see CALLPARM) can now also be used with the same syntax in sections CICS and IMS. 4

5 Version These modifications and enhancements have been made to SCANCOB in Version SCANCOB can create metric information about the analyzed source. Use parameter SHOW-METRICS=YES in the CALLPARM (section GENERATOR) to have SCANCOB generate information about metrics. SCANCOB can create a list of all statements in the source that contain REPLACE/REPLACING. This list is stored in a work area in the import file. Use parameter SHOW-REPLACING=YES in CALLPARM (section GENERATOR) to have SCANCOB generate information about REPLACE/REPLACING statements. Corrections and Fixes Version These errors in SCANCOB have been corrected in Version The error in VORELLE TABLE processing. A missing END TABLE statement caused a loop in the scanner front end. An error in nested program processing. SCANCOB did not treat names of nested programs correctly when the names were defined using literals like this one PROGRAM-ID. 'GETBYOFFS' IS COMMON. An error during copy book processing. The copy book information was truncated when the 88 level definition used the name EXECUTE. If, for instance, you are using 88 names, such as RETURN, END, or EXECUTE, you must define them via the NO_KEYWORD parameter in the <COPA> section. Example <COPA> NO_KEYWORD4=RETURN NO_KEYWORD5=END NO_KEYWORD6=EXECUTE 5

6 Version An error in SQL processing with built-in functions. An error in SQL extraction. In some cases, the extracted SQL statement exceeded the COBOL programming area column 12 to 71. Improved VALUE definition processing. Literals in notation H'<hex code>' are now treated correctly. An error in SPECIAL-NAMES paragraph processing. If the source contains a SPECIAL-NAMES paragraph with EBCDIC, use the IS_KEYWORD parameter in section <COPA> to declare EBCDIC. For example SPECIAL-NAMES. ALPHABET X IS EBCDIC DECIMAL-POINT IS COMMA. <COPA> IS_KEYWORD8=EBCDIC An error in processing complex expressions in parameter definitions of intrinsic function parameters, for example COMPUTE A = FUNCTION MOD((Z-DATE/100) 100) An error in processing the OS/VS keyword NOTE. These errors in SCANCOB have been corrected in Version The usage of EXAMINE (a language element from an older COBOL dialect) was causing an error. The new version handles EXAMINE when the word is defined with IS_KEYWORD in CALLPARM (i.e., IS_KEYWORD=EXAMINE). SCANCOB analyzed in RECORD definitions entry names of the format FILLER-XX (where XX is any characters) as FILLER and not as correct entry names as expected. A bug in SQL processing with COUNT(*). A bug in SQL processing with built-in functions. A bug in the Generator module. On rare occasions, the generation of the DATA-LEX table was causing a S0C4. A bug in CICS processing with CICS DFHVALUE(OPEN). 6

7 A bug in copy book processing. The earlier version created an error when the copy book contained a REPLACE statement that did not end with a dot (.). For example, in the source is a copy statement like this and the copy book cop-book contained only a REPLACE statement definition COPY cop-book.. * look at the two '.' * the first '.' ends the copy statement, the second * '.' is the end marker for the statement in the * copy book A bug in recognition of a replacing pattern, when the pattern contained string quotes. For example ==op-read-pahistakt== by =='read-pahistakt== '== A bug in the collating sequence clause. For example SOURCE-COMPUTER. IBM OBJECT-COMPUTER. IBM-3083 COLLATING SEQUENCE IS SEQUENCE-BCD. SPECIAL-NAMES. COPY TRSEQBCD. * BLOCK 95 IS IIIA. DATA DIVISION ALPHABET SEQUENCE-BCD IS LOW-VALUE '0' THRU '9' 'ø' 'œ' '' '>' '?' SPACE 'A' THRU 'I' '&' '.' '(' '<' 'J' THRU 'R' '-' '$' THRU ';' QUOTE '+' '/' 'S' THRU 'Z' ',' '%' '=' '"'. 7

8 Version These errors in SCANCOB have been corrected in Version An error in the VARINHA table. VARINHA documents every value assigned to a variable in the source. In certain cases, earlier versions of SCANCOB documented too much information about index variables. An error in the handling of floating point formats. The format [+-].nnn is now scanned correctly, for example 01 SSATX-1-RATE-1 PIC SV9(6) COMP-3 VALUE MOVE +.5 TO SSATX-1-RATE-1. An error concerning LINEAGE-COUNTER in expressions. An error in expressions. The expression (8 OR 9) as shown in this example was not supported IF NV-ART >= 2 AND <= 5 OR = (8 OR 9) CALL statements to a nested program ID using the identifier of the nested program are now documented correctly. Earlier versions of SCANCOB recognized calls to a nested program only when the CALL statement used a literal format. An error in scanning copy books. In some cases, when a copy book contained incomplete record definitions with ascending level numbers, some of the data description entries were not documented, for example 05 name pic x. 02 name1 pic x. 02 name2 pic x. An error in EXEC SQL analysis (i.e., a CASE statement in SELECT). An error in COPY statement processing. For example, this code was evaluated incorrectly COPY CO3866I SUPPRESS EJECT * comment. An error in the handling of nested inline perform statements. An error in processing of PANVALET copy statements (++INCLUDE ). Several errors in the handling of nested COBOL programs COPY statements in a nested program were not documented if the nested program was implemented in a copy book. COBOL sources that implement nested programs on the same program level are now supported. 8

9 Installation Information For information on installing Rochade and Rochade components under all supported operating systems, see the Rochade readme file (i.e., the file readme_en.pdf) and the ASG-Rochade Installation Guide. SCANCOB consists of two components that must be installed separately on your z/os machine and on a Windows PC; for details, see Installation under z/os on page 9 and Installation under Windows on page 11. In addition, be sure to heed the information in Upgrade Instructions on page 11. System Requirements ASG provides detailed lists of hardware and software requirements for all Rochade components and relevant operating systems on its ISP at http//cust.asg.com/rochade/productspecifications/supportedenvironments.html. The hardware requirements for SCANCOB are the same as for Rochade (see the section on system requirements in the ASG-Rochade System Administrator s Guide). These are the software requirements for SCANCOB Rochade 5.40 or later ASG-Rochade AutoPilot (herein called AutoPilot) 3.40 or later ASG-Rochade I-RIM (herein called I-RIM) 1.40 or later Installation under z/os For information about the installation of Rochade components under z/os, see the section about installation under MVS (synonymous with z/os in this context) in the Rochade readme file. You can install the z/os component of SCANCOB in any one of these modes Standalone on a machine on which Rochade is not installed. In the context of a Rochade environment Using a Rochade environment that already exists. Installing it together with a new Rochade environment. 9

10 This table lists, in logical order, the datasets that the SCANCOB installation creates on your computer Dataset Name PFX?.ROPROD.CNTL *.CNTL(ROCOBSC) Description Job library for SCANCOB. Job for executing SCANCOB. Note If you are using SCANCOBSC in conjunction with a Rochade version earlier than 7.0, you must use this scan job. If you are running Rochade 7.0 or later, you can also use this job, but in that case, ASG recommends that you use the job ROCOBSC7 instead (see below). *.CNTL(ROCOBSC7) Job for executing SCANCOB. Note ASG recommends that you use this scan job if you are running Rochade 7.0 or later. It supports the improved mechanism offered by the newer Rochade versions for passing parameters to the client via a dataset defined through a PARMFILE DD statement. For details, see the section on calling a batch client under MVS in the ASG-Rochade Programmer s Guide Volume 3. *.CNTL(ROCOBSCE) PFX?.ROPROD.LOAD *.LOAD(ROCOBSC) *.LOAD(ROCOB#A) *.LOAD(ROCOB#G) PFX?.ROPROD.DATA *.DATA(CO3C#SRC) *.DATA(CO3C#CPY) *.DATA(CO3PARM) *.DATA(CO3CHKF) *.DATA(CO3INCL) ROCOBSC with external SQL-Analysis (CHK2SQL). Load module library for SCANCOB. Control module for SCANCOB. SCANCOB front end. Scanner back end. Library with control files for SCANCOB. SCANCOB call parameters for scanning sources. SCANCOB call parameters for scanning copies. SCANCOB model map. Checkpoint definitions. Include path for searching COBOL copy books. 10

11 Dataset Name PFX?.ROPROD.CO3MACL PFX?.ROPROD.README *.README(ECO#CO3) PFX?.ROPROD.SAMPLES *.SAMPLES(CO3SRC) *.SAMPLES(CO3COPY) *.SAMPLES(CO3CPY11) Description Library with system copy books for SQL, CICS analysis. Readme files. Documentation about Enterprise COBOL to COBOL II conversion. Source examples. COBOL source code examples. COBOL copy book examples. COBOL copy book examples. Installation under Windows SCANCOB requires procedures for importing the scanner results into Rochade. These procedures are provided by the procedure package ROSCAN3, which you can install using the standard two-step installation process for Rochade components under Windows first the ADM installation, then the Application installation. The ADM installation installs the procedure package into the Rochade databases. It requires that you have operator or administrator rights. Hence, this installation should be carried out by a system or Rochade database administrator. The Application installation registers the procedure package on the local computer. This step is not mandatory for SCANCOB, but it is useful to have the procedure package properly registered so that it is listed with the correct status during future installation activities. If you need more information about ADM and Application installation, see the ASG-Rochade Installation Guide. Upgrade Instructions Note These upgrade instructions apply only if you are using Rochade 6 or later. If you already have SCANCOB data in Rochade, ASG recommends that you migrate those data to Rochade s extended naming concept, which allows long item names. For information about migration to the extended naming concept, visit the ISP and see the technical bulletin Rochade XNS Migration Utility for Legacy Scanner Applications. 11

12 After you have completed the migration successfully, set GEN-SHOR-NAMES=V6 in the parameter file. Note If you do not have any SCANCOB data in Rochade yet, you must also set GEN-SHOR-NAMES=V6 in the parameter file. Getting Started Before you can run a first scan with SCANCOB, these requirements must be fulfilled The scanner must have been installed successfully. The packages ROSCAN and I-RIM must have been installed successfully. If you also want to have the scan result imported into Rochade immediately after the scan (i.e., if you also want to run the IMPORT step of the scan job), the Rochade server must be running. For a first test of the scanner in the Rochade environment, ASG suggests that you use the job ROCOBSC (PFX?.ROPROD.CNTL), which contains a step named IMP. In this step, the result of the source code analysis is imported into Rochade. Extracted from the job ROCOBSC //************************************************** //* call import //************************************************** //* please adjust the parameter //* //* USR MUSR CLISECT //* //* USR... User name for $movelog //* MUSR... Name of the subject area //* MVER... version Name for subject area //* //IMPORT EXEC ROCLIENT,USR='BB',MUSR='CO3SAMPLE', // MVER='INITIAL', // COND=(8,LT,SCAN),REGION=0K //SYSIN DD DSN=&DIR..CO3OUT,DISP=(OLD,DELETE) //* 12

13 The sample job expects this prerequest in the database A user BB with ADM rights. Create this user if necessary. A subject area CO3SAMPLE (with information model C-RIM and version INITIAL) for importing the scanner result. Create this subject area if necessary. Note If you want to use a different name for the user, subject area, or subject area version, change the corresponding entries (i.e., USR='BB', MUSR='CO3SAMPLE', and MVER='INITIAL') in the job ROCOBSC. After you have installed I-RIM, use the I-RIM Information Model Composer to generate your information model based on C-RIM (called C-RIM here, but could have a different name). For details, see the ASG-Rochade I-RIM System Administrator s Guide. To execute the SCANCOB jobs 1 Decide which of the two scan jobs you want to use for running the scan (i.e., ROCOBSC or ROCOBSC7). For information, see the table of datasets in Installation under z/os on page 9. 2 Open the job that you have chosen in step 1 and modify it as instructed in the comments within that job. 3 Submit the job. 13

14 14