C306M1C TS

	Making your legacy system source code migration and translation efforts, effortless.

C306M1C:
    Support Home
    Release Notes
    PTFs

2600 Kitty Hawk Road, Suite 111
Livermore, CA. 94551
1.415.777.5400


Release Notes for C306M1C:
C306M1C was released on December 2, 2002. SystemVision SVCOMMANDS Work Order 3859 @SV.CALL: 8 BYTE PROC NAME NOW NOT REPORTED AS AN EXTERNAL CALL Work Order 3865 SQL ANALYSIS SIGNIFICANTLY CORRECTED AND IMPROVED Work Order 3867 @SV.MEMBER: PROCESSED COMMENT RECORDS IN ERROR Work Order 3868 @SV.CALL PL/1 PICKED UP SOME QUALIFIED VARIABLES IN ERROR Work Order 3869 @SV.CALL: BUILT-IN FUNCTION RETURNED TO REPORT Work Order 3870 @SV.IDENT: JCL MEMBERS HAD PROCESSING ERRORS Work Order 3871 @SV.JOB NOT REPORTING CORRECTLY Work Order 3872 SVCOMMANDS NOW ACCEPTS INVALID COPY NAMES JUST LIKE THE COBOL COMPILER DOES Work Order 3878 @SV.SCAN WITH COMMENT=NO DIDN’T WORK WHEN @SV.SCAN RAN, COMMENT RECORDS WERE REPORTING FOR BOTH ASSEMBLER AND COBOL PROGRAMS BUT SHOULDN’T HAVE WHEN COMMENT=NO WAS USED. Work Order 3879 SVSRC MACRO WORKED CORRECTLY IF THE PROCESSED SOURCE RESIDED IN A PDS LIBRARY BUT IF IT RESIDED IN A PANVALET OR LIBRARIAN DATASET, THE MESSAGE ‘SYSPRINT NOT ALLOCATED - FILE IN USE’ WAS PRODUCED. Work Order 3884 MACRO "SVSRC" WITH AN MLIST LOOKED FOR DNAME AND SHOULDN’T HAVE Work Order 3885 SVSRC WON’T HANDLE STLIST IF MEMBER NAME NOT IN 61,73 The SVSRC macro was unable to find the source member name in a list being edited if that list was not a ‘traditional’ STLIST (member name in column 61 or 73) but whose @LIST record defined it as one. Such is the case when an SVCOMMANDS run catalogs a list in a run in which it has referred to an input list as ‘LIST=’. This convention is commonly used in SystemVision OPLISTs. Work Order 3886 PL/1 BASED(ADDR() CONSTRUCT WAS HANDLED INCORRECTLY SV.ATTRIBUTE MISREPORTED THE ATTRIBUTES AND/OR REDEFINES NAME FOR DATANAMES THAT ARE BASED(ADDR(SOMETHING)) FOLLOWED BY AN ATTRIBUTE (LIKE CHAR(20)). Work Order 3887 @SV.ION WITH MLIST=XXX,IMS=NO DIDN’T FIND ANY DATA @SV.CICS PHASE=SOURCE USES A CMLIST AND CTLIST AS INPUT. FORMATS OF THESE LISTS WERE CHANGED. Work Order 3890 @SV.COPY, XRMEMBER=COPY HAS PROBLEM FOR SQL INCLUDE THE DESCRIPTION OF THE OPTION XRMEMBER=COPY WAS CLARIFIED AND THE PROBLEM WITH @SV.COPY, XRMEMBER=COPY AGAINST "EXEC SQL INCLUDE NAME" WAS FIXED Work Order 3893 @SV.LIST WITH NYM=LIK DIDN’T WORK Work Order 3895 CHANGE INSTALL PANEL FOR PRINTER TYPE Work Order 3904 @SV.DNAMES, TITLE CARD PROCESSING FOR ASSEMBLER AND COBOL DIDN’T WORK Work Order 3906 @SV.ENTRY DIDN’T REPORT ENTRY POINTS AFTER THE MAIN ENTRY POINT WHEN @SV.ENTRY FUNCTION RAN AGAINST A PL/1 SOURCE MODULE WITH TWO OR MORE MAIN ENTRY POINTS, ONLY THE FIRST ONE WAS BEING IDENTIFIED. SystemVision IMPACT Work Order 3877 IMPACT DOESN’T REPORT PARMS CONTAINING IMPACT ITEMS IMPACT’s KWIC step, option 3 - Records and parms, item e, ‘Impact Parms or records containing Parms passed/received’ did not report data names and records that contained impact items but were themselves not previously identified as impact items. It only reported a data name as an impacted parm if that data name was an impact item that was identified in the INITIAL or ALIAS step and was passed or received by a program. This has been corrected. If a parm is itself an impact item or is not, but does contain one or more impact items, it is reported in the list of impacted parms (xxxIPRM) with a ‘P’ in column 1. Any impact item(s) it contains will appear underneath it. For any name in this list that is defined in a copybook, the copybook name is reported in column 11. For all names in the list, the program-id is in column 21 and the line number on which the name is defined in the program (after all copybooks have been expanded) appears in column 62. SCENARIOS Work Order 3888 SCENARIOS PRODUCT @PM.RPT FUNCTION WAS NOT WORKING CORRECTLY

PTFs (Program Temporary Fixes) for C306M1C:
Here is a list of PTFs for release C306M1C. Click on the PTF number to view the entire PTF.

3878	Customer requested CASE=ASIS as the default CASE option.
3908	Tech service hours and FAX number have changed.
3920	Two table names referred to on this panel have changed and a line has been deleted.
3922	Some users of new SQL analysis provided in C306M1C had 0C4 ABENDS on first runs. The cause was two separate things; first an attempt to process an SQL cursor declaration that spanned more than 600 lines, and secondly the code contained a structure which had not previously been seen by ADPAC. So this patch doubles the size of an internal table in PM@SQ7 and also contains a correction for the new code structure.
3923	Correct open processing of work files, DCB record format field. The error resulted in an abend or missing reported output data.
3925	When @SV.CALL ran against COBOL source with construction such as: CALL 'PROGNAME' USING COPY COPYNAME REPLACING == AB == BY ==CD==. (REPLACING is continuing to the next line) PROGNAME was not reported.
3928	When @SV.CALL ran against PL/1 source modules, some called program names were reported invalidly.
3930	It was discovered that any qualified names that occurred in a cursor declaration were not shown as qualified (Q) in DNAMES report.
3935	@SV.PROC: it failed to report a step which occurred immediately before an EXEC IJKJEFTX and it contained no DD cards of its own.
3936	DL1 related data sets were dropped when running @SV.JCL or @SV.LIST merging DSLIST with JCLIST.
3940	A customer has special code in cursor DECLARE and SELECT which is not clearly supported by IBM SQL manual. Changes were made to support customer usage.
3942	Repository function with Datamanager failed to report properly a group of 88-Levels that contained two separate groups of un-names values.
3943	When @SV.CALL runs with CICS option, no requested data is found. CICS option doesn't handle CICS processing properly.
3952	1.Function @SV.CALL with option KWIC against ASSEMBLER modules didn't work as expected. Nothing was found. 2.Function @SV.STRING against multi-language modules couldn't recognize language type of the processed module if it started with comment lines.
3954	1.When @SV.STRING ran with options LANG=COBOL, NARRATIVE=ALL, against multilanguage library (with COBOL ans ASSEMBLER source), unnecessary ASSEMBLER comment lines located before CSECT statement were reported. 2.When @SV.STRING ran with options LANG=ASM, NARRATIVES=ALL, DIVISION=(DATA,PROC), necessary comment lines before CSECT statement were not reported.
3955	DESCRIPTION: When @SV.STRING ran with option DIVISION=(IDENT,ENV,DATA,PROC), LANG=TEXT, division option was not ignored and nothing was reported.
3956	DESCRIPTION: EXEC CICS READ/WRITE FILE('FILENAME') is as valid as EXEC CICS READ/ WRITE FILE ('FILENAME') - with blank(s) between FILE and ('FILENAME'). When @SV.CICS ran, FILENAME couldn't be recognized when READ and FILE('FILENAME') are located on different lines of the program.
3960	DESCRIPTION: When @SV.CICS ran and some of the processed dataset names contained word 'FILE' as a part of the name, new element names ended by 'FILE' were reported.
3968	DESCRIPTION: Correction of PARENT processing in IMPACT product.
3978	DESCRIPTION: Correction of @SV.CALL function processing.
3979	DESCRIPTION: When the IMPACT product is used, if any data names contain any of the defined search character strings (are impacted items) and these data names have subordinate levels of data, all subordinates (including 88-level condition names) should be considered as impacted items too and included in the general list of impacted items. Parents must be provided for these subordinates (including 88-level) like for real impacted items.
3991	DESCRIPTION: When ADMIN step of JCLVIEW product ran, wrong DJLIST was produced.
8225	DESCRIPTION: When @SV.CALL ran against ASSEMBLER source and there was a data name with '@' in 6th position, wrong member names were reported.


Home \| Products \| Services \| Support \| About Us \| Contact Us
ADPAC's Privacy Statement.
© ADPAC Corporation. All rights reserved.