OA65082: CUNMRCSM CONFIGDD NOT FOUND UNEXPECTED OUTPUT

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• CUNMRCSM CONFIGDD DD may not be found even though it has been
  specified and does exist.  When the DD is specified with DSN= or
  is dynamically allocated CUNMRCSM fails to open the DD under
  and fopen() invocation and receives errnojr C00B0006.
  
  When CUNMRCSM fopen() for CONFIGDD fails for any reason, you
  will see the the error message in job output:
  
      No CONFIGDD found, default CCSIDs will be used.
  
  This problem when the dataset created for the CONFIGDD has any
  attribute other then RECFM(FB).  When the DD is coded with DD *
  without DSN= the CONFIGDD is opened succesffully and honored.
  
  ie:
  //CONFIGDD  DD *
  # DEFAULT EBCDIC CCSID WORK AS INPUT
  DEFAULT_EBCDIC_CCSID=1047
  # DEFAULT ASCII CCSID WORK AS OUTPUT
  DEFAULT_ASCII_CCSID=923
  
  
  The data translated in the body of the resulting email may
  produce unexpected output.  This is because the CCSIDs used in
  the translation may not be using the intended CCSIDs that were
  specified in the CONFIGDD.
  
  
  Note, when the CONFIGDD parameters are not specified, CUNMRCSM
  default is to use CCSID 1141 for DEFAULT_EBCDIC_CCSID and CCSID
  923 for DEFAULT_ASCII_CCSID.
  
  
  Additional Keyword:
  JrEdc1opsEexisting06
  

Local fix

• BYPASS/CIRCUMVENTION:
  Ensure that the CONFIGDD is allocated as RECFM(FB) or use
  CONFIGDD * specification instead.
  

Problem summary

• ****************************************************************
  * USERS AFFECTED: Users of Unicode Services explore the        *
  *                 CUNMCSMM/CUNMRCSM utility.                   *
  ****************************************************************
  * PROBLEM DESCRIPTION: CUNMCSMM/CUNMRCSM will fail to open     *
  *                      //DD:CONFIGDD when it is allocated as   *
  *                      RECFM(F) since only RECFM(FB,80) is     *
  *                      supported currently. The following      *
  *                      message will be received: "No CONFIGDD  *
  *                      found, default CCSIDs will be used."    *
  ****************************************************************
  The CUNMCSMM/CUNMRCSM utility should support //DD:CONFIGDD with
  whatever RECFM it already has and issue the appropriate error
  message when opening //DD:CONFIGDD failed.
  

Problem conclusion

• After the ++PTF is applied, the CUNMCSMM/CUNMRCSM will be able
  to open //DD:CONFIGDD with whatever RECFM it already has. In
  addition, the appropriate error message will be displayed when
  opening //DD:CONFIGDD failed.
  

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:

  UJ93502 UJ93503 UJ93504

Modules/Macros

• CUNMCSMI
  

Fix information

• Fixed component name

  UNICODE SUPPORT

• Fixed component ID

  5752SCUNI

Applicable component levels

• R7B0 PSY UJ93504

     UP23/09/06 P F309

• R7D0 PSY UJ93503

     UP23/09/06 P F309

• R7E0 PSY UJ93502

     UP23/09/06 P F309

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.