A fix is available
APAR status
Closed as new function.
Error description
New function adds a suboption to the TEST(SEPARATE) compiler option, TEST(SEPARATE(DSNAME)), that directs the compiler to store the name of the SYSDEBUG file in the generated object program, similar to how TEST(SEPARATE) support was implemented in COBOL V4.2
Local fix
N/A
Problem summary
**************************************************************** * USERS AFFECTED: All users of IBM Enterprise COBOL V6.2 * * compiling and debugging programs that * * specify the TEST(SEPARATE) compiler option * * who would like to have the name of the * * SYSDEBUG file stored in the resulting * * program object. * **************************************************************** * PROBLEM DESCRIPTION: New function: New suboptions have been * * added to the existing SEPARATE * * suboption of the TEST compiler option. * * The suboptions are SEP(NODSNAME), * * which supports the current behavior, * * and SEP(DSNAME). If the user specifies * * TEST(SEPARATE(DSNAME)), then the * * compiler will store the name of the * * SYSDEBUG file in the program object, * * similar to what was done in the V4.2 * * COBOL compiler. * **************************************************************** * RECOMMENDATION: Apply the provided PTF. * **************************************************************** Prior to this new function, it was not possible to have the SYSDEBUG file name stored in the object program, when the TEST(SEPARATE) compiler option was specified. This was done intentionally in V6.2, because in most cases the system or LPAR where the program was compiled would be different than the system or LPAR where the module got deployed, making this SYSDEBUG file name irrelevant. Some customers also expressed concerns over the security implications of storing the SYSDEBUG file name in the program object. It turns out that customers in smaller installations may actually develop and test their COBOL applications on a single system or LPAR. These customers would like to avoid the overhead of having to use the COBOL runtime debug file EXIT IGZIUXB (or IGZIUXC/IGZIUXD) to specify the SYSDEBUG file name.
Problem conclusion
Temporary fix
Comments
The compiler has been updated to support the new DSNAME suboption of the SEPARATE suboption. When TEST(SEPARATE(DSNAME)) is specified for a compile, the SYSDEBUG file name will be stored in the program object. As long as the COBOL application is deployed on the same system or LPAR that
APAR Information
APAR number
PH04485
Reported component name
ENT COBOL FOR Z
Reported component ID
5655EC600
Reported release
620
Status
CLOSED UR1
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2018-10-24
Closed date
2018-11-22
Last modified date
2018-12-12
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Modules/Macros
IGY8RWTU IGYCASMB IGYCCBE IGYCCCRT IGYCCICS IGYCCSRV IGYCDGEN IGYCDIAG IGYCDMAP IGYCEN$0 IGYCEN$1 IGYCEN$2 IGYCEN$3 IGYCEN$4 IGYCEN$5 IGYCEN$8 IGYCEN$D IGYCEN$R IGYCFGEN IGYCFREE IGYCINIT IGYCJA$0 IGYCJA$1 IGYCJA$2 IGYCJA$3 IGYCJA$4 IGYCJA$5 IGYCJA$8 IGYCJA$D IGYCJA$R IGYCLIBH IGYCLIBO IGYCLIBR IGYCLSTR IGYCLVL0 IGYCLVL1 IGYCLVL2 IGYCLVL3 IGYCLVL8 IGYCMALL IGYCOB2E IGYCOPI IGYCOSCN IGYCPGEN IGYCRCTL IGYCRDPR IGYCRDSC IGYCREAL IGYCRWT IGYCSCAN IGYCSIMD IGYCUE$0 IGYCUE$1 IGYCUE$2 IGYCUE$3 IGYCUE$4 IGYCUE$5 IGYCUE$8 IGYCUE$D IGYCUE$R IGYCXREF IGYDRV IGYEQCWI IGYMSGE IGYMSGK IGYMSGT IGYQCBE IGYZQDRV IGYZQENU IGYZQJPN
Fix information
Fixed component name
ENT COBOL FOR Z
Fixed component ID
5655EC600
Applicable component levels
R620 PSY UI59885
UP18/11/29 P F811
R621 PSY UI59886
UP18/11/29 P F811
R622 PSY UI59887
UP18/11/29 P F811
R62H PSY UI59888
UP18/11/29 P F811
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":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SS6SG3","label":"Enterprise COBOL for z\/OS"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"620","Edition":"","Line of Business":{"code":"LOB35","label":"Mainframe SW"}}]
Document Information
Modified date:
12 December 2023