A fix is available
APAR status
Closed as program error.
Error description
RDZUTIL V9110 INTERNAL DEFECTS AND ENHANCEMENTS
Local fix
n/a
Problem summary
**************************************************************** * USERS AFFECTED: 01.all users of AKGCC, batch code coverage * * 02.all batch Code Review users * * 03.RDz Utilities users who embed the * * provided AKGCx procedures in a job. * * 04.z/OS system programmer * * 05.All headless code coverage users who use * * the -localonly parameter or the AKGCC * * procedure. * * 06.All users of the Code Coverage * * Collector. * * 07.All users of the Code Coverage * * Collector. * * 08.All users of the Code Coverage * * Collector. * * 09.All users of the Code Coverage * * Collector. * * 10.All users of the Code Coverage * * Collector. * * 11.All users of the Code Coverage * * Collector. * **************************************************************** * PROBLEM DESCRIPTION: 01.batch CC fails if the collector * * does not report the IP address * * 02.enhancement to support new batch * * Code Review features * * 03.RDz Utilities procedures AKGCC and * * AKGCR do not have an embedded PEND * * statement at the end. * * 04.RDzUtil SMPE sample jobs AKG4MNT * * and AKG5MKD reference invalid DSN * * in comments * * 05.EQA9999W - Debug Tool TCPIP error * * 06.Code Coverage only shows a single * * entry point for code coverage of * * COBOL applications. * * 07.Code Coverage can take a long time * * to run with larger files. * * 08.Code Coverage includes modules that * * a user does not want covered. * * 09.Code Coverage options could only be * * specified at startup of the daemon * * and not easily changed. * * 10.There is no way to associate a code * * coverage result with a test id. * * 11.In RDz 9.1, code coverage may not * * provide accurate coverage from the * * first entry point into a file to * * the second entry point for the * * initial file in an application. An * * initial file that contains a single * * entry point may incorrectly report * * no coverage. * **************************************************************** * RECOMMENDATION: * **************************************************************** 01.On some systems, the CC collector cannot retrieve the local address, which results in AKG0413W report generation failed due to EQA9999W - Debug Tool TCPIP error. 02.enhancement to support new batch Code Review features LIST: a table-like list to specify source code to be reviewed SYSLIB: syslib concatenation fro code review JUNIT: code review report in JUnit fomat 03.Rational Developer for System z Utilities procedures AKGCC and AKGCR do not have an embedded PEND statement at the end. The procedures have instructions on converting the procedure to a job, but this results in JCL error without the missing PEND. Workaround: Add "// PEND" after the procedure, and before the EXEC card. 04.Rational Developer for System z Host Utilities (RDzUtil) SMPE sample jobs AKG4MNT and AKG5MKD reference invalid DSN in comments. SAKGJCL should be SAKGSAMP. 05.When using the -localonly parameter with the code coverage daemon, whether by command line, of by using the code coverage procedure AKGCC, the daemon is unable to determine the loopback ip address for binding for some TCP/IP configurations. This results in the localonly parameter being ignored, and also results in the code coverage session launched by AKGCC failing. 06.Rational Developer for System z (RDz) Host Utilities Code Coverage only shows a single entry point for code coverage of COBOL applications. 07.Rational Developer for System z (RDz) Host Utilities Code Coverage can take a long time to run with larger files. 08.Rational Developer for System z (RDz) Host Utilities Code Coverage includes modules that a user does not want covered. 09.Rational Developer for System z (RDz) Host Utilities Code Coverage options could only be specified at startup of the daemon and not easily changed. 10.Rational Developer for System z (RDz) Host Utilities There is no way to associate a code coverage result with a test id. 11.In Rational Developer for System z (RDz) Host Utilities 9.1, code coverage may not provide accurate coverage from the first entry point into a file to the second entry point for the initial file in an application. An initial file that contains a single entry point may incorrectly report no coverage.
Problem conclusion
01.Tool is enhanced to use localhost if no IP address is provided by the collector 02.enhancement to support new batch Code Review features 03.Missing PEND statement is added. 04.Comments are updated. 05.The code coverage daemon used for headlesss will now properly detect the loopback address, and if no loopback address is defined, it will log an error indicating the problem. AKGCC is enhanced to attempt to bypass the problem when it occurs. 06.Code Coverage results for COBOL applications now provide paragraph level coverage. 07.Code Coverage has reduced the number of calls to the debug engine in order to improve performance. 08.The customer can specify a file with a list of modules to exclude using the -moduleexcludelist parameter. This parameter can also be used in the startup key. The file should contain a list of module to exclude, separated by new lines, and may include regular expressions. 09.The startup key parameter in the JCL can be used to specify desired parameters. For example: For Debug Tool, module level coverage can be specified using the following: EQA_STARTUP_KEY=CC,program_name,cclevel=MODULE For Debug Tool, function level coverage, and tag can be specified using the following: AQE_STARTUP_KEY=CC,program_name,cclevel=MODULE,tag=regression Test The list of code coverage parameters, and their values is as follows: cclevel MODULE,FUNCTION,LINE prevresultpath valid z/os UNIX path to a previous result file reportformat html savesource true,false zipresult true, false ignoreerrors true,false timeout valid integer, >0 testid any alpha-numeric string tag any alpha-numeric string. Quotes are allowed, and must be used if multiple tags are to be specified. Multiple tags should be separated by a comma (,). For example tag='value1,value2' moduleexcludelist valid z/OS UNIX path to a file containing the list of modules to exclude. 10.The -testid parameter can be used with the Code Coverage Collector, as well as with the startup key. 11.Code Coverage was skipping the first entry point in the first file in an application in some cases, which then resulted in incorrect coverage result. Code Coverage has been corrected to properly detect the first entry point and provide appropriate coverage.
Temporary fix
Comments
APAR Information
APAR number
PI18894
Reported component name
RD/Z UTILITIES
Reported component ID
5724T0733
Reported release
910
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2014-05-29
Closed date
2014-12-05
Last modified date
2014-12-09
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
UI23675
Modules/Macros
AKGCC AKGCCINI AKGCCX AKGCR AKGCRLIC AKGCRX AKGFT001 AKGXCC01 AKG4MNT AKG5MKD
Fix information
Fixed component name
RD/Z UTILITIES
Fixed component ID
5724T0733
Applicable component levels
R910 PSY UI23675
UP14/12/09 I 1000
Fix is available
Select the PTF appropriate for your component level. You will be required to sign in. Distribution on physical media is not available in all countries.
[{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SSQ2R2","label":"Rational Developer for System z"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"910","Line of Business":{"code":"LOB17","label":"Mainframe TPS"}}]
Document Information
Modified date:
14 October 2021