PRODUCT: IMPACT
Work Order-3966
A. OPLIST ERROR IN IMPACT

OPTION 4 - PARENTS OF IMPACT ITEM - not all parent records were reported 
because only parents in conditional statements were accepted. 

Work Order-3968 
B.	FIX AND IMPROVE PARENT PROCESSING IN IMPACT

1. If the data field in Cobol program is redefined a few times and any of 
   the redefined fields have different length than the original one, in 
   parents report (***IDNL) original field appears with the length of 
   redefined fields.
2. If some parts of data description are located in the body of the main 
   program and other parts in the copybook (different member), parents 
   report lost parent data names located in the main program.
3. Impacted data names file (***0IDNL) and parents file (***IDNL) didn't 
   contain level number before the data name

Work Order-3979
C.	SUBORDINATE LEVELS TREATED AS IMPACTED ITEMS

If a data name is an 'impacted' item (found in the defined search strings) 
and has subordinate levels of data, all subordinates (including 88-level 
condition names) should be considered as impacted items as well and 
included in the general list of impacted items, which they weren't.

Parents must be provided for these subordinates (including 88-level) the 
same as for any other impacted item.


PRODUCT: JCLVIEW
Work Order-3991
A.	JCLVIEW ADMIN STEP PRODUCED THE WRONG DJLIST

In the ADMIN Step the wrong format of a DJLIST was produced


PRODUCT: VirtualSource
Work Order-3994 & 3995 & 3997 
A.	CORRECTIONS

1. In ADMIN step, message '201I LESS THAN 04 PARMS RECEIVED' was produced.
2. In Step 3.2, (01 level) no report was produced.
3. In Steps 3.3 and 3.4 if the MEMBER NAME is different than the PROGRAM   
   ID, message 'PM@LIS-03 NO REQUESTED DATA FOUND IN THIS RUN' was produced.
4. In ADMIN, Step 1 -'MEMBERS') when panel SVMBR@ was displayed, pressing the 
   F3 key mistakenly returns to the SVQRY@ panel (outside of the ADMIN) instead 
   of returning to the SV@QFVSA panel (inside ADMIN).



PRODUCT: SVCOMMANDS
Work Order-3978
A.	@SV.CALL DIDN'T PROCESS COBOL PROGRAMS CORRECTLY

When @SV.CALL ran processed a Cobol source module and it had, in columns 1-6 
of the line, @@@@@@ instead of the normal line number, member name was missing 
from the report.

Work Order-3983
B.	Cobol Replace statement processing has been added. 

Work Order-3990
C.	@SV.REFORMAT PROCESSING HAS BEEN CHANGED

The verification option of @SV.REFORMAT didn't work properly.
SystemVision tried to invoke Cobol 74 compiler (IKFCBL00) instead of Cobol II 
compiler (IGYCRCTL) with MLIST/all verification option was prohibited.

Work Order-4000
D.	@SV.CALL LOOPING PROBLEM

When COBOL keyword 'REPLACE' is a part of dataname, @SV.CALL function looped.

E. @SV.RATE Miscalculated CALL count

In prior releases the CALL count was only the number of actual CALL statements 
in a program NOT the actual number of invocations of each CALL use as it should 
have done.