CA Spool

Expand all | Collapse all

Tech Tip: CA Spool and IBM’s Red Alert notification related to z/OS Unicode Services Conversion Information Service

  • 1.  Tech Tip: CA Spool and IBM’s Red Alert notification related to z/OS Unicode Services Conversion Information Service

    Posted 10-07-2015 11:16 AM

    Per IBM’s Red Alert notification z/OS Unicode Services Conversion Information Service will fail after December 15, 2015.
    It has been confirmed that parts of our CA Spool product will be affected so you have to take action today.

     

    IBM has created specific z/OS release maintenance to resolve the underlying problem.

     

    When contacting IBM ask for IBM APAR OA48941.

     

    OA48941: UNICODE CONVERSION INFORMATION SERVICE FAILS RC8 RSNB SYSTEM TOD CLOCK TIMESTAMP EXCEEDS 12/15/2015 13:24:57.238527 CUNLINFO

     

    See http://www-01.ibm.com/support/docview.wss?uid=isg1OA48941

     

    Applicable component levels are :

     

    R7A0 PSY UP IA48941
    R780 PSY UP GA48941
    R790 PSY UP HA48941

     

    Be aware that IBM has to be contacted to confirm the IBM APAR number and applicable PTFs for your specific z/OS system level.
    There is no circumvention to mitigate the reported problems other than to install the maintenance recommended by IBM.



  • 2.  Re: Tech Tip: CA Spool and IBM’s Red Alert notification related to z/OS Unicode Services Conversion Information Service

    Posted 03-28-2016 10:26 AM

    Hello Community,

     

    It has been reported to us that the problem reported by IBM via the Red Alert already discussed in this post can impact clients using the Java Transformer option.

    The CAIQD2E started task fails to initialize and it ends with an undocumented Return Code 998.

    When using the CAIQD2E startup parameter D2E_TRACE=ALL to debug the problem is noticed that no D2ELOG report is created.
    Also the JavaVMOption(n) section (where n goes from 1 to 5) of the D2ETRACS report does not contains valid information.
    If you see all these symptoms then please follow the original recommendation to contact IBM for the appropriate solution.

     

    Thanks for your continued support

     

    Regards, Cesar