PH18904: UPDATE INITCHECK SO IT DOES NOT REPORT AN UNINITIALIZED FIRST BYTE WHEN NOADV AND WRITE AFTER ADVANCING IS USED

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• When the NOADV compiler option is used and WRITE ... AFTER
  ADVANCING is used to write an output record, the WRITE AFTER
  ADVANCING phrase will cause a carriage control character to be
  written into the first byte of the output record (such as x'40'
  if WRITE AFTER ADVANCING 1 LINE is used).  As such, it isn't
  really necessary to pre-initialize the first byte of the output
  record definition.  However, INITCHECK will catch the fact that
  the first byte is not initialized and issue a warning.
  INITCHECK will now catch this situation and not issue a warning
  if the first byte is uninitialized.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED: Users of Enterprise COBOL for z/OS V6 using  *
  *                 the INITCHECK compiler option on programs    *
  *                 that have WRITE ... FROM ... AFTER           *
  *                 ADVANCING where the FROM data item has an    *
  *                 uninitialized 1-byte field as the first      *
  *                 subordinate to the group sender.             *
  ****************************************************************
  * PROBLEM DESCRIPTION: Incorrect output: INITCHECK gives a     *
  *                      misleading uninitialized message about  *
  *                      the 1-byte data item. It does not need  *
  *                      to be set, since that 1-byte field is   *
  *                      used and set by the generated code to   *
  *                      set FCB fields for the runtime WRITE    *
  *                      routine.                                *
  ****************************************************************
  * RECOMMENDATION: Apply the provided PTF.                      *
  ****************************************************************
  The compiler was flagging the 1-byte field as not being set
  because it was not set, but it does not need to be set by the
  user, so we should try to avoid the INITCHECK message
  

Problem conclusion

• The compiler was changed to suppress an INITCHECK message for
  a 1-byte field as the top-level subordinate to a FROM
  identifier in a WRITE ... FROM ... ADVANCING statement.
  

Temporary fix

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

  PH20991

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 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 UI67017

     UP19/12/19 P F912

• R621 PSY UI67018

     UP19/12/19 P F912

• R622 PSY UI67019

     UP19/12/19 P F912

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.