PK32733: DISPLAY TERMINATED WITH MAX LINES DSN9023I -DSMC DSNX9COM '-DISPLAY PROC' ABNORMAL COMPLETION

A fix is available

 

APAR status

  • Closed as program error.

Error description

  • The customer has a DB2 V8 NFM datasharing group environment,
    When running a batch job to issue a DIS PROC(*.*) SCOPE(GROUP)
    they are receiving the following message :

    DISPLAY TERMINATED WITH MAX LINES
    DSN9023I -DSMC DSNX9COM '-DISPLAY PROC' ABNORMAL COMPLETION
    DSN
    END

    Based on the customer's testing, it seems the SP's display
    terminates in a different member where it was executed.
    Additional symptom:
    DISPLAY PROCEDURE(SYSPROC.*) command from TSO can result in
    S04E rc00e20004.

Local fix

  • n/a

Problem summary

  • ****************************************************************
    * USERS AFFECTED: DB2 users of commands *
    * -display procedure, or *
    * -display function specific *
    * with the scope(group) keyword. *
    * *
    ****************************************************************
    * PROBLEM DESCRIPTION: When issuing command *
    * -display procedure(*.*) scope(group) *
    * in a batch job, the following message *
    * is returned: *
    * DISPLAY TERMINATED WITH MAX LINES *
    * DSN9023I -DSMC DSNX9COM '-DISPLAY *
    * PROC' ABNORMAL COMPLETION *
    ****************************************************************
    * RECOMMENDATION: *
    ****************************************************************
    For the commands issued from the console, we have a limit
    for the output messages. But for the commands issued from
    a batch job, we should not have such a limit. Currently,
    the code that processing the return data from datasharing
    members doesn't know if the command is issued from console
    or from a batch job, so in case the return data from data
    sharing members exceeds the max data line limit, it issues
    DSNX958 message even if the command is from a batch job

Problem conclusion

  • Add code to find out whether the command is from console
    or not. If it's not from console, don't check the max data
    line limit. Just write all the messages returned from all
    data sharing members in the job output.

Temporary fix

Comments

APAR Information

  • APAR number

    PK32733

  • Reported component name

    DB2 OS/390 & Z/

  • Reported component ID

    5740XYR00

  • Reported release

    810

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2006-10-10

  • Closed date

    2006-12-01

  • Last modified date

    2007-01-03

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

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

    UK20205 UK20206

Modules/Macros
DSNX9COM          

Fix information

  • Fixed component name

    DB2 OS/390 & Z/

  • Fixed component ID

    5740XYR00

Applicable component levels

  • R710 PSY UK20205

       UP06/12/19 P F612

  • R810 PSY UK20206

       UP06/12/19 P F612

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.

Rate this page:

(0 users)Average rating

Add comments

Document information


More support for:

DB2 for z/OS

Software version:

810

Reference #:

PK32733

Modified date:

2007-01-03

Translate my page

Machine Translation

Content navigation