IBM Support

ZZ00641: ICO REST API NOT ALLOWING PROJECTNAME AND DOMAINNAME

Subscribe to this APAR

By subscribing, you receive periodic emails alerting you to the status of the APAR, along with a link to the fix after it becomes available. You can track this item individually or track all items by product.

Notify me when this APAR changes.

Notify me when an APAR for this component changes.

Direct link to fix

 

APAR status

  • Closed as program error.

Error description

  • We observed that the documented use of projectName and
    domainName in the header for calling the ICO REST API for ICO
    2.5.0.2 is not working.
    When using these headers in the REST call they are not
    populated and the default values remain.
    In the workflow we log parameters... (the object's name and
    description and also the user, project and domain.) Notice that
    the defaults seem to be being used.
    [root@SECLDVVICOSRV01 ~]# cat SystemOut.log |grep LOG
    [3/15/17 18:13:40:257 CET] 000001e1 LoggerScripta I
    LOGREST:testname
    [3/15/17 18:13:40:258 CET] 000001e1 LoggerScripta I
    LOGREST:testdesc
    [3/15/17 18:13:40:258 CET] 000001e1 LoggerScripta I
    LOGREST:Domain:Default
    [3/15/17 18:13:40:258 CET] 000001e1 LoggerScripta I
    LOGREST:Project:admin
    [3/15/17 18:13:40:258 CET] 000001e1 LoggerScripta I
    LOGREST:User:admin
    [root@SECLDVVICOSRV01 ~]#
    

Local fix

  • We would need to apply the LA fixes from the following two
    APARs-
    1. ZZ00600 - 2.5.0.2-CSI-ICO-LA0001
    2. ZZ00604 - 2.5.0.2-CSI-ICO-LA0003
    and also this 3rd APAR you are reading.
    

Problem summary

  • We observed that the documented use of projectName and
    domainName in the header for calling the ICO REST API for ICO
    2.5.0.2 is not working.
    When using these headers in the REST call they are not
    populated and the default values remain.
    In the workflow we log parameters... (the object's name and
    description and also the user, project and domain.) Notice that
    the defaults seem to be being used.
    [root@SECLDVVICOSRV01 ~]# cat SystemOut.log |grep LOG
    [3/15/17 18:13:40:257 CET] 000001e1 LoggerScripta I
    LOGREST:testname
    [3/15/17 18:13:40:258 CET] 000001e1 LoggerScripta I
    LOGREST:testdesc
    [3/15/17 18:13:40:258 CET] 000001e1 LoggerScripta I
    LOGREST:Domain:Default
    [3/15/17 18:13:40:258 CET] 000001e1 LoggerScripta I
    LOGREST:Project:admin
    [3/15/17 18:13:40:258 CET] 000001e1 LoggerScripta I
    LOGREST:User:admin
    [root@SECLDVVICOSRV01 ~]#
    

Problem conclusion

Temporary fix

Comments

APAR Information

  • APAR number

    ZZ00641

  • Reported component name

    SMRTCLOUD ORCHS

  • Reported component ID

    5725H2800

  • Reported release

    250

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2017-03-30

  • Closed date

    2017-04-14

  • Last modified date

    2017-04-14

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

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

Fix information

  • Fixed component name

    SMRTCLOUD ORCHS

  • Fixed component ID

    5725H2800

Applicable component levels

  • R250 PSY

       UP

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SS4KMC","label":"IBM SmartCloud Orchestrator"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"250","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
14 April 2017