IBM Support

PI35035: CCCA TEST COMPILE GETS IEF210I JCL ERROR

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Error Description:
    The test COBOL compile job to verify a CCCA conversion fails
    with a JCL error MSGIEF210I for UNIT=VIO if the unit name VIO is
    not defined in the hardware configuration.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED: Users of CCCA on z/OS                        *
    ****************************************************************
    * PROBLEM DESCRIPTION: Compile jobs generated by CCCA could    *
    *                      fail with a JCL error with message      *
    *                      IEF210I.                                *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    CCCA optionally performs a test compile of converted source
    code.  This is done by invoking an in-line JCL procedure to call
    the compiler, based on one previously supplied with the compiler
    itself, but as the output is not required, the output SYSLIN DD
    statement is overriden to DD DUMMY.  The SYSLIN DD statement
    within the procedure specifies UNIT=VIO, and JCL processing
    validates this even though it is going to be overriden.  If the
    installation does not have UNIT=VIO defined, or has it only
    defined in SMS but not in the hardware configuration, this
    causes a JCL error with message IEF210I saying that the unit
    name is invalid.  The same reference to UNIT=VIO also occurs
    in the sample JCL for batch processing supplied with CCCA.
    
    All other references to unit names in the skeleton JCL and
    the samples refer to a unit name which can be customised as
    part of the product environment options, so this reference
    to UNIT=VIO should also be customised to use the installation
    work file unit name.
    
    Note that the same problem may also occur with UNIT=SYSDA if
    it is only defined to SMS, not in the hardware configuration,
    because the overriden JCL statement has the DUMMY option
    and is not passed to SMS.  A simple solution in this case is
    to set the work file unit name in the environment options to
    SYSALLDA instead.
    

Problem conclusion

  • The skeleton and sample files have been changed to use the
    installation work file unit name specified in the environment
    options rather than the fixed value of UNIT=VIO.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PI35035

  • Reported component name

    CCCA FOR OS/390

  • Reported component ID

    5648B0500

  • Reported release

    210

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2015-02-16

  • Closed date

    2015-02-17

  • Last modified date

    2015-03-03

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

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

    UI25203

Modules/Macros

  • ABJCNVCS ABJCNVS  ABJCOMP  ABJCONV  ABJCONVC
    

Fix information

  • Fixed component name

    CCCA FOR OS/390

  • Fixed component ID

    5648B0500

Applicable component levels

  • R210 PSY UI25203

       UP15/02/18 P F502

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":"SG19M","label":"APARs - z\/OS environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"210","Edition":"","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
03 March 2015