C306M1D was released on April 1, 2004.

PRODUCT: IMPACT

PRODUCT: SVCOMMANDS

1. SQL REPORTS - DROP TABLE SYNONYMS

AFTER CONSULTATION WITH ADPAC CLIENTS IT REVEALED THAT OUR INCLUSION IN REPORTS OF SQL ANALYSIS (DNAMES AND IONAMES) OF TABLE SYNONYMS IS MORE CONFUSING THAN HELPFUL, SO TABLE SYNONYM NAMES WILL NO LONGER BE REPORTED EXCEPT WHERE THEY MIGHT BE USED AS QUALIFIERS FORMING PART OF COMPOUND NAMES FOR COLUMNS IN SELECT AND WHERE CLAUSES.

SQL TABLE NAME LOST AFTER 'JOIN'

SQL QUAL NAME REPORT CORRECTION

RESTORE DL1 DATASET REPORTING

HANDLE SPECIAL SF SQL CODE



@SV.CALL 

MISSING CALLED PROGRAM
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.

SOME INVALID CALLED MODULES REPORTED
WHEN @SV.CALL RAN AGAINST PL/1 SOURCE MODULES, SOME CALLED PROGRAM
NAMES WERE REPORTED INVALIDLY.

CICS OPTION DIDN’T WORK PROPERLY
WHEN @SV.CALL RUNS WITH CICS OPTION, NO REQUESTED DATA IS FOUND.
 CICS OPTION DOESN’T HANDLE CICS PROCESSING PROPERLY.

@SV.CALL AND @SV.STRING PROBLEMS
FUNCTION @SV.CALL WITH OPTION KWIC AGAINST ASSEMBLER MODULES DIDN’T
WORK AS EXPECTED. NOTHING WAS FOUND.
FUNCTION @SV.STRING AGAINST MULTI-LANGUAGE MODULES COULDN’T RECOGNIZE
LANGUAGE TYPE OF THE PROCESSED MODULE IF IT STARTED WITH COMMENT LINES.

@SV.CALL FOR COBOL SOURCE MAY LIST AS ‘SSAID?’
WHEN @SV.CALL RAN AGAINST COBOL SOURCE, DYNAMIC NAMES MAY BE REPORTED AS  ‘SSAID?’.
PROCESSING OF DYNAMIC NAMES FOR @SV.CALL (LANGUAGE=COBOL), WAS FIXED AND
 BROUGHT INTO ACCORD WITH SVCOMMANDS MANUAL.

@SV.CICS 

CAN’T FIND DYNAMIC NAME IF FILE(‘NAM’)
 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.

UNKNOWN ELEMENT NAMES REPORTED
 WHEN @SV.CICS RAN AND SOME OF THE PROCESSED DATASET(FILE) NAMES
 CONTAINED WORD ‘FILE’ AS A PART OF THE NAME, NEW ELEMENT NAMES ENDED BY
 ‘FILE’ WERE REPORTED.

REPORT IS MISSING SOME DATA
 WHEN @SV.CICS RAN AND CICS CODE IS LOCATED INSIDE SQL CODE, SOME DATA
 COULD BE MISSED FROM REPORT.


@SV.DSN 

SOURCE=PROC ERRORS CORRECTED


@SV.SCAN 

KWIC=(WORD,AFTER) TRUNCATING WORD

IF OPTION KWIC=(WORD,AFTER) WAS USED, SOME REPORTED WORDS WERE TRUNCATED.


@SV.PROC 

DROPPING STEP W/O DD CARD FIXED


@SV.REP

2. CORRECT REPOSITORY ERRORS ON 88-LEVELS

@SV.STRING 



WHEN @SV.STRING RAN WITH OPTIONS LANG=COBOL, NARRATIVE=ALL, AGAINST MULTILANGUAGE 
LIBRARY (WITH COBOL AND ASSEMBLER SOURCE), UNNECESSARY ASSEMBLER COMMENT LINES 
LOCATED BEFORE CSECT STATEMENT WERE REPORTED.

WHEN @SV.STRING RAN WITH OPTIONS LANG=ASM, NARRATIVES=ALL,  DIVISION=(DATA,PROC), 
NECESSARY COMMENT LINES BEFORE CSECT STATEMENT WERE NOT REPORTED.

@SV.STRING WITH LAN=TEXT PROBLEM FIXED

WHEN @SV.STRING RAN WITH OPTION DIVISION=(IDENT,ENV,DATA,PROC), LANG=TEXT, DIVISION 
OPTION WAS NOT IGNORED AND NOTHING WAS REPORTED.

VARIOUS JCL PROCESSING ERRORS CORRECTED

LONGER IKFEFT STEPS NOW HANDLED PROPERLY

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.

DESCRIPTION: When ADMIN step of JCLVIEW product ran, wrong DJLIST was produced.

DESCRIPTION: Correction of PM@IOR for missing 6 Line Header File.

2. When @SV.CALL ran against ASSEMBLER source and there was a data name with '@' in 6th position, wrong member names were reported.