IBM Support

PI94376: JSONTRANSFRM CONTROL BLOCK DOES NOT CONTAIN THE TIMESTAMP OF WHEN THE JSBIND FILE WAS GENERATED

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • The JSONTRANSFRM resource control block ml_jstr_cb does not
    contain the timestamp of when the JSBIND file was generated.
    
    This APAR has been created to store the timestamp in this
    control block so it is possible to tell from a CICS dump when
    the JSBIND file was generated.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All CICS users.                              *
    ****************************************************************
    * PROBLEM DESCRIPTION: JSBIND timestamp difficult or           *
    *                      impossible to locate in dump.           *
    ****************************************************************
    DFHJS2LS or DFHLS2JS is run to create a JSON binding file.  The
    JSON binding file, with extension .jsbind, is created in the
    bundle directory and contains a timestamp of when it was
    generated.
    A JSONTRANSFRM bundle resource is created in CICS and the
    DFHJSON linkable interface is used to convert application data
    to JSON or vice-versa.
    DFHJS2LS or DFHLS2JS is rerun to make a change to the JSON
    binding file, but the change is not seen at runtime.  From a
    CICS dump it can be difficult or impossible to locate the
    timestamp of the JSON binding file in use by CICS meaning it
    may not be possible to confirm that CICS is using the updated
    file.
    

Problem conclusion

  • DFHMLJS has been modified to store the JSON binding file's
    timestamp in the JSONTRANSFRM control block when the file is
    parsed.
    
    DFHMLJS has also been updated so that a new trace point, ML
    0709, is issued when DFHJSON is called if ML level 2 tracing is
    active.  This trace point shows the JSON binding file timestamp.
    The CICS TS for z/OS Knowledge Center will be updated
    to list this trace point.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PI94376

  • Reported component name

    CICS TS Z/OS V5

  • Reported component ID

    5655Y0400

  • Reported release

    100

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2018-02-27

  • Closed date

    2018-06-18

  • Last modified date

    2018-07-02

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

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

    UI56621 UI56622 UI56623 UI56624

Modules/Macros

  • DFHJSON  DFHMLDM  DFHMLDUF DFHMLJS  DFHMLPC  DFHMLRL  DFHMLST
    DFHMLTF  DFHMLTRI DFHMLXT
    

Fix information

  • Fixed component name

    CICS TS Z/OS V5

  • Fixed component ID

    5655Y0400

Applicable component levels

  • R000 PSY UI56624

       UP18/06/19 P F806

  • R100 PSY UI56623

       UP18/06/19 P F806

  • R800 PSY UI56621

       UP18/06/20 P F806

  • R900 PSY UI56622

       UP18/06/23 P F806

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":"5.4","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":"5.4","Edition":"","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
02 July 2018