ASG-Rochade SCANPLI Release Notes

Size: px

Start display at page:

Download "ASG-Rochade SCANPLI Release Notes"

Horace Bruce
5 years ago
Views:

ASG-Rochade SCANPLI Release Notes Version 3.10.

1 ASG-Rochade SCANPLI Release Notes Version March 8, 2007 PL This publication contains information about all modifications made to ASG-Rochade SCANPLI (herein called SCANPLI) since Version ISP Updates ASG encourages you to visit 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 SCANPLI scanner tool performs two major functions: It inspects the PL/I 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 SCANPLI comprises an overview of the relationships between different programs, files, procedures, functions, and CICS/DLI and DB2 elements, as well as information about file organization and file access. Enhancements and Changes Version Besides the job ROPLIBSC, there is now an additional sample job, ROPLISC7, 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 Version Version The capability to evaluate LIKE clauses has been added to SCANPLI in Version This version of SCANPLI suppresses information about each link qualifier when PARMS=NO is found in CALLPARM. These modifications and enhancements have been made to SCANPLI in Version : Enhanced processing of NAMFIL. A new parameter is available in the 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, that should not be scanned. Example 1: SCANLIB=LIB1 SCANEXCLUDE=*,*ABC Or SCANLIB=LIB1 SCANEXCLUDE=*ABC SCANPLI scans all members in LIB1 whose names do not end in ABC. 2

3 Version Example 2: SCANLIB=LIB1 SCANEXCLUDE=A*,*10* SCANPLI scans all members in LIB1 whose names start with A, except for those whose names contain 10. The parameters CALL-VARIABLE and VARIABLE-CALL from section GENERATOR->CALL-EXTERN (see the CALLPARM file) can now also be used with the same syntax in sections CICS and IMS. These modifications and enhancements have been made to SCANPLI in Version : SCANPLI can create metric information about the analyzed source. Set the parameter SHOW-METRICS=YES in the CALLPARM (section GENERATOR) to have SCANPLI generate information about metrics. OUTFIL now can be a member in a PDS or PDSE. Corrections and Fixes Version Version These errors in SCANPLI have been corrected in Version : A bug in SQL processing with COUNT(*). A bug in SQL processing with built-in functions. A bug in include scan with LIKE clause representation in DAT-LEX: : DCL 01 ZW_KEY LIKE PROV.KEY; DCL R_ZW_KEY CHAR(16) BASED(ADDR(ZW_KEY)); : In cases in which the LIKE attribute related to a structure, the structure elements were not placed correctly in the data lexicon, which then caused undefined import behavior. Errors in SQL processing have been corrected in SCANPLI

4 Version Version These errors in SCANPLI have been corrected in Version : Processing for statements of type: DCL 01 CAKURS01, %INCLUDE YAGKU01; In cases in which the include member was not available, earlier SCANPLI versions saw the source as incomplete and treated it as an include. The new version constructs an empty data description when include is not available, keeping the structure of the source consistent. An error in NAMFIL processing. The notation SCAN=MEMBER caused a missing DD statement warning for DD MEMBER in SCANPLI through An error in PARMFIL processing. The keyword STANDARDS was not treated correctly. Information about checkpoints are no longer generated when STANDARDS is disabled. Errors in SQL processing: In some cases, TIMESTAMP was treated as a column name. In some cases, JOIN was not treated correctly. These errors in SCANPLI have been corrected in Version : SCANPLI documents CALL statements implemented in on error procedures. SCANPLI handles DCL statements in this form: DCL SETNUM PIC'(5)Z9'BASED(ADDR(SETCHAR)); SCANPLI documents DCL statements for external files. An error in the STRUCT table. An error in processing ENTRY statements in internal procedures. An error in evaluation of preprocessor expressions. 4

5 Version These errors in SCANPLI have been corrected in Version : An error concerning virtual tables in DB2 processing. SCANPLI stops the processing when OUTFIL cannot be written to (e.g., no space is available). When this happens, the scanner returns the error code 16. 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. SCANPLI 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 6 and Installation under Windows on page 7. In addition, be sure to heed the information in Upgrade Instructions on page 8. System Requirements ASG provides detailed lists of hardware and software requirements for all Rochade components and relevant operating systems in its ISP at The hardware requirements for SCANPLI 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 SCANPLI: 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 5

6 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 SCANPLI 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. This table lists, in logical order, the datasets that the SCANPLI installation creates on your computer: Dataset Name PFX?.ROPROD.CNTL *.CNTL(ROPLISC) Description Job library for SCANPLI. Job for executing SCANPLI. Note: If you are using SCANPLISC 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 ROPLISC7 instead (see below). *.CNTL(ROPLISC7) Job for executing SCANPLI. 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 these 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(ROPLISCE) PFX?.ROPROD.LOAD *.LOAD(ROPLISC) ROPLISC with external SQL-Analysis (CHK2SQL). Load module library for SCANPLI. Control module for SCANPLI. 6

7 Dataset Name *.LOAD(ROPLI#A) *.LOAD(ROPLI#G) PFX?.ROPROD.DATA *.DATA(PL3C#SRC) *.DATA(PL3C#INC) *.DATA(PL3PARM) *.DATA(PL3CHKF) *.DATA(PL3INCL) PFX?.ROPROD.PL3MACL PFX?.ROPROD.README PFX?.ROPROD.SAMPLES *.SAMPLES(PL3SRC) *.SAMPLES(PL3INCL) Description SCANPLI front end. Scanner back end. Library with control files for SCANPLI. SCANPLI call parameters for scanning sources. SCANPLI call parameters for scanning includes. SCANPLI model map. Checkpoint definitions. Include path for searching PL/I includes. Library with system includes for SQL, CICS analysis. Readme files. Source examples. PL/I source code examples. PL/I include examples. Installation under Windows SCANPLI 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 SCANPLI, 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. 7

8 Upgrade Instructions Note: These upgrade instructions apply only if you are using Rochade 6 or later. If you already have SCANPLI 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. After you have completed the migration successfully, set $OPTION XNSDSNINFO=Y in the parameter file. Note: If you do not have any SCANPLI data in Rochade yet, you must also set $OPTION XNSDSNINFO=Y in the parameter file. Getting Started Before you can run a first scan with SCANPLI, 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 ROPLISC (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 ROPLISC: 8 : //*********************************************************** //* 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 //*

9 : //IMPORT EXEC ROCLIENT,USR='BB',MUSR='PL3SAMPLE', // MVER='INITIAL', // COND=(8,LT,SCAN),REGION=0K //SYSIN DD DSN=&DIR..PL3OUT,DISP=(OLD,DELETE) //* : The sample job expects this prerequest in the database: A user BB with ADM rights. Create this user if necessary A subject area PL3SAMPLE (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='PL3SAMPLE', and MVER='INITIAL') in the job ROPLISC. 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 SCANPLI jobs 1 Decide which of the two scan jobs you want to use for running the scan (i.e., ROPLISC or ROPLISC7). For information, see the table of datasets in Installation under z/os on page 6. 2 Open the job that you have chosen in step 1 and make adjustments as instructed in the comments within that job. 3 Submit the job. 9

10 10

ASG-Rochade SCANCOB Release Notes

ASG-Rochade SCANCOB Release Notes Version 3.10.007 March 8, 2007 CO31100-310 This publication contains information about all modifications made to ASG-Rochade SCANCOB (herein called SCANCOB) since Version