IBM Support

PK70581: BATCHREP STUCK IN STARTED STATUS. NO OUTPUT SEEN. EYUVC1231E

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • If a BATCHREP (Batched repository update request) is submitted
    from the WUI, specifying a PDS with a member name that includes
    the ワ symbol (British Sterling Pound symbol), the request will
    fail, and the following message is displayed on the WUI:
    .
    EYUVC1231E  xxxxxxxx request failed. Request complete for 1
    records. (Failed, Exception)
    .
    Further, the submitted request then remains with a Processing
    State of STARTED.
    .
    The same BATCHREP request completes successfully when submitted
    through the EUI.
    .
    The problem here is codepage related.  The WUI currently only
    supports four different codepages - US English, Japanese, and
    two different Chinese codepages. It does not support UK English.
    On a z/OS system, with a US English codepage, x'5B' shows up as
    '$'.  On a z/OS system, with a UK English codepage, x'5B' shows
    up as
     'ワ' (British Sterling Pound Symbol).
    Since the WUI does not support UK English codepage, when you
    enter the ワ Pound symbol in the browser, it flows into CICS as
    x'B1' instead of x'5B'.  CPSM method EYU0XDBM converts the
    character string to upper case, and in the process, the x'B1'
    becomes an x'F1'.
    .
    CPSM trace will show this as the following:
    .
    EYUQXDBT IN
       *FUN FUNCTION( BATCHDR )
       *CHR DEBUG( MOS XDBT )
       *CHR INPUTDSN( MY.DATASET.NAME                  )
       *CHR INPUTMEMBER( ワTEST )
       *CHR PRINTCLASS( X )
       *CHR PRINTNODE( LOCAL    )
       *CHR OUTPUTUSER( MYUSERID   )
       *EYU RUNTYPE( EXECUTE          )
    OUT
       *RSP RESPONSE( EXCEPTION )
       *RSN REASON( METHOD_FAILED )
       *STA STATUS( OUTPUT_SEC_VIOLATION )
    .
    The failed process does not get cleaned up properly, and will
    remain in STARTED status.
    .
    Additional Symptom(s) Search Keyword(s):
    KIXREVSCB
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All CICSPlex SM V3R2M0 Users.                *
    ****************************************************************
    * PROBLEM DESCRIPTION: If a BATCHREP SUBMIT action is          *
    *                      performed using an INPUTMEMBER          *
    *                      parameter value that contains invalid   *
    *                      characters, then the SUBMIT action      *
    *                      might fail with a FAILED (1029)         *
    *                      response and a EXCEPTION (1359)         *
    *                      reason.                                 *
    *                                                              *
    *                      After the exception, the BATCHREP       *
    *                      request will remain outstanding in      *
    *                      'STARTED' status until the CMAS is      *
    *                      restarted.                              *
    ****************************************************************
    * RECOMMENDATION: After applying the PTF that resolves this    *
    *                 APAR, all CMASes and WUI servers must be     *
    *                 recycled to pick up the new code.  Note that *
    *                 the restarts do not need to be done at the   *
    *                 same time.                                   *
    ****************************************************************
    Method EYU0XDBT (XDBT) is called to process a BATCHREP SUBMIT
    action. It retrieves the parameter values associated with the
    request and builds a BATCHREP record and places this record onto
    the CMASes BATCHREP list. The key for this record is the
    request's INPUTDSN (primary key) and INPUTMEMBER (secondary key)
    values.
    
    XDBT then invokes EYU0XDBM (XDBM) passing the INPUTDSN and
    INPUTMEMBER parameters. XDBM folds these parameters to upper
    case and then reads the CMASes BATCHREP list using the folded
    INPUTDSN and INPUTMEMBER values as a key.
    
    As XDBT wrote the request to the CMASes BATCHREP list using an
    unfolded key, the XDBM read request fails if one of the
    characters in the INPUTDSN or INPUTMEMBER parameters does not
    support standard EBCDIC folding.  This causes XDBM to create an
    exception, which is returned to the user.
    
    XDBM attempts to clean up the CMASes BATCHREP list, but as it is
    still attempting to use folded key values, the request to remove
    the record from the CMASes BATCHREP list fails. This causes the
    BATCHREP request to remain until the CMAS restart.
    

Problem conclusion

  • XDBM has been changed so that it does not attempt to fold the
    INPUTDSN and INPUTMEMBER parameters. This is to ensure that
    the same values used to build the BATCHREP record in XDBT are
    used by XDBM.
    
    XDBT has been changed to perform extra validation on the
    following parameters:
    
      INPUTDSN - valid z/OS Dataset name
      INPUTMEMBER - valid z/OS Dataset member name
      PRINTCLASS - valid characters: A-Z,0-9,*
      PRINTNODE - valid characters: A-Z,0-9, National or a single *
      OUTPUTUSER - valid characters: A-Z,0-9, National or a single *
    
    XDBT will fold the INPUTDSN and INPUTMEMBER values so that the
    folded values will be used for the CMASes BATCHREP list record
    and passed to XDBM.
    
    The BATCHREP resource table has been changed so that new
    FEEDBACK error codes are returned:
    
      10  BATCHREP_INV_INPUTMEMBER Invalid input member
      11  BATCHREP_INV_INPUTDSN    Invalid input data set name
      12  BATCHREP_INV_PRINTCLASS  Invalid output class
      13  BATCHREP_INV_PRINTNODE   Invalid print node
      14  BATCHREP_INV_OUTPUTUSER  Invalid destination userid
    

Temporary fix

  • FIX AVAILABLE BY PTF ONLY
    

Comments

APAR Information

  • APAR number

    PK70581

  • Reported component name

    CICSTS V3 Z/OS

  • Reported component ID

    5655M1500

  • Reported release

    50M

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2008-08-18

  • Closed date

    2008-11-04

  • Last modified date

    2008-12-01

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

    PK70525

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

    UK41246

Modules/Macros

  •    BATCHREP EYUA2554 EYUCXDBT EYUC2554 EYUE2554
    EYUK2554 EYUL2554 EYUP2554 EYUQXDBT EYURXDBT EYUR2554 EYUS2554
    EYUTRDAT EYUT2554 EYUX2554 EYUYXDBT EYUY2554 EYUZXDBT EYU0XDBM
    EYU0XDBT EYU9XDBC EYU9XDPU EYU9XDP3 EYU9XDP4
    

Publications Referenced
SC34685001    

Fix information

  • Fixed component name

    CICSTS V3 Z/OS

  • Fixed component ID

    5655M1500

Applicable component levels

  • R50M PSY UK41246

       UP08/11/07 P F811

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":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SSGMGV","label":"CICS Transaction Server"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"3.2","Edition":"","Line of Business":{"code":"LOB35","label":"Mainframe SW"}},{"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":"3.2","Edition":"","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
01 December 2008