IBM Support

PK07942: USING REMOTE STC TO ISSUE COMMANDS, CCF ENDED W\ RC=0 EVEN WHEN THE REMOTE STC ENCOUNTERED AN ERROR PROCESSING THE ICMD CALL.

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • When using the remote stc to issue commands, ccf ended with
    a zero return code (rc=00) - even when the remote stc encounters
    an error processing the icmd call.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All users of IMS CCF.                        *
    ****************************************************************
    * PROBLEM DESCRIPTION: Using Remote STC to issue commands,     *
    *                      CCF ended with RC=0 even when the       *
    *                      Remote STC encounterd an error          *
    *                      processing the ICMD call.               *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    When using the Remote STC to issue commands, CCF ended with
    a zero return code even when the Remote STC encounterd
    an error processing the ICMD call.
    

Problem conclusion

  • Added a new runtime option for /CCFMOD processing. If the
    /MOD COMMIT fails for any IMS in the group (other then the
    first), CCF can now reverse the online change for any
    systems where the /MOD COMMIT was already successful.
    
    Care MUST be used when using this option. The customer
    should understand all of the implications of restoring
    old ACBLIB members before using this option.
    
    Added a new runtime option where CCF can add the NOFEOV
    parameter to all /DBD and /DBR commands.
    
    Added a prescan process for database commands. When using
    the Remote STC to issue commands, if database commands do
    not complete in the alloted timeframe and Command Retry
    is going to take place, CCF will now scan the Database
    Control Blocks to see if the resource is in the proper
    state. If so, CCF will not need to re-issue the command.
    This should cut down access to the Recon Datasets.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PK07942

  • Reported component name

    IMS COMMAND CTL

  • Reported component ID

    5655F4000

  • Reported release

    110

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2005-06-24

  • Closed date

    2005-08-16

  • Last modified date

    2005-09-02

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

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

    UK06327

Modules/Macros

  •    CCFAPPC0 CCFDB510 CCFDB610 CCFDB710 CCFDB810
    CCFDB910 CCFEDIT0 CCFEXEC0 CCFH1FEV CCFH1MOR CCFOPRT0 CCFOPTS0
    CCFP100  CCF9GBL0
    

Fix information

  • Fixed component name

    IMS COMMAND CTL

  • Fixed component ID

    5655F4000

Applicable component levels

  • R110 PSY UK06327

       UP05/08/17 P F508

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.

[{"Line of Business":{"code":null,"label":null},"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SSCBTY6","label":"IMS Command Control Facility"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"110"}]

Document Information

Modified date:
21 October 2020