IBM Support

OA40946: INSTREAM DATA CAN BE LOST FROM AN INSTREAM PROC WHEN AN INCLUDE IS USED IN THAT PROC.

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • The Converter can get confused and loses track of instream
    data when that data exists in an instream proc, and that
    proc utilizes an Include statement.
    For example, given the following JCL, and if the INC1
    INCLUDE member contains simply a comment statement,the
    resulting SYSUT2 DD would not receive any data.
    
      //PROC1    PROC
      //         INCLUDE MEMBER=INC1
      //PSTEP1   EXEC PGM=IEBGENER
      //SYSUT1   DD *
      --- instream data rec 1
      --- instream data rec 2
      --- instream data rec 3
      /*
      //SYSUT2   DD SYSOUT=*
      //SYSPRINT DD SYSOUT=*
      //SYSIN    DD DUMMY
      //PROC1    PEND
      //JSTEP1   EXEC PROC1
    .
    Additional Symptoms:  Other instream procedure issues have
    been seen fixed by this APAR, so this fix is highly
    recommended.
    

Local fix

  • N/A
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED: Installations running HBB7780                *
    ****************************************************************
    * PROBLEM DESCRIPTION: Instream data can be lost when it       *
    *                      resides in an instream procedure that   *
    *                      also has an INCLUDE statement           *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    When an instream procedure contains instream (SYSIN type)
    data, and the instream procstep also has an INCLUDE statement
    in it, the instream data may not become known to the job step.
    This is because in this case, the JCL Converter builds the
    internal text unit for the SYSIN type DD statement with an
    incorrect Data Set Identifier (DSID) sequence number.
    
    See the Submitter Text for this APAR for an example of the
    JCL that can lead to this problem.
    

Problem conclusion

  • JCL Converter processing will be changed to provide a correct
    DSID sequence number when building text units for SYSIN type
    statements that reside in instream procedures that also
    contain INCLUDE statements.
    

Temporary fix

Comments

APAR Information

  • APAR number

    OA40946

  • Reported component name

    CONVERTER/INTER

  • Reported component ID

    5752SC1B9

  • Reported release

    780

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2012-12-04

  • Closed date

    2013-01-08

  • Last modified date

    2013-03-26

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

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

    UA67642

Modules/Macros

  • IEFCNEXP IEFCNINC
    

Fix information

  • Fixed component name

    CONVERTER/INTER

  • Fixed component ID

    5752SC1B9

Applicable component levels

  • R780 PSY UA67642

       UP13/01/23 P F301

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":"780","Edition":"","Line of Business":{"code":"","label":""}},{"Business Unit":{"code":null,"label":null},"Product":{"code":"SG19O","label":"APARs - MVS environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"780","Edition":"","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
26 March 2013