In Control-M/Server for UNIX and Microsoft Windows 9.0.19 when using User Daily (ctmudly) to order jobs it may fail with error 'User Daily: Failed' in the job output

Version 1
    Share This:

    This document contains official content from the BMC Software Knowledge Base. It is automatically updated when the knowledge article is modified.


    PRODUCT:

    Control-M/Server for UNIX and Microsoft Windows


    COMPONENT:

    Control-M/Server for UNIX and Microsoft Windows


    APPLIES TO:

    Control-M/Server for UNIX and Microsoft Windows 9.0.19



    PROBLEM:

    In Control-M/Server 9.0.19 when using User Daily (ctmudly) to order jobs it may fail with error 'User Daily: Failed' in the job output

    The following messages can be seen in the CE log:

    Could not order job 'mySmartFolder'. Reason: null", [WARNING], T@106, T:ctm.FolderHandler.106, "['mySmartFolder' - 4a409165-1fa6-44fe-b868-a1289cee134f]", com.bmc.ctmsServices.ordering.ActiveJob, ActiveJob::transactionalDoOrder, ,

    Could not order job '<Job or Folder name>'. Reason: String index out of range: -4


    CAUSE:

    CTM-1775 - ctmudly fails to order SMART folder when ADJUST_COND is on CTM-2261 - Ordering jobs ...might fail, if the jobs are not planned ...before or after the order date according to their calendar.... CTM-2565 - ctmudly job not ordered correctly


    SOLUTION:

    CTM-1775 - ctmudly fails to order SMART folder when ADJUST_COND is on
    Patch PACTV.9.0.19.001 contains the resolution to the issue and may be obtained from the Electronic Product Download (EPD) site.

    CTM-2261 - Ordering jobs (and folders) using ctmudly might fail, if the jobs are not planned to be ordered before or after the order date according to their calendar and the job has in or out conditions
    This fix is tentatively planned to be implemented in version PACTV.9.0.19.200 and is currently available in PACTV.9.0.19.101

    CTM-2565 - ctmudly job not ordered correctly in case we use "start day of week" not Monday and we use Days Of Week DnWm
    This fix is tentatively planned to be implemented in version PACTV.9.0.19.200 and is currently available in PACTV.9.0.19.102
    http://documents.bmc.com/supportu/documents/06/16/520616/520616.pdf

    Temporary solution:   In case the patches above cannot be installed, perform the following steps to use the legacy ctmudly utility:

    1. Under the Control-M Server installation, make a backup copy of the current ctmudly script:
        Unix:  mv exe_<os_platform>/ctmudly exe_Linux-x86_64/ctmudly_orig
        Windows:  copy "\Program Files\BMC Software\Control-M Server\ctm_server\exe\ctmudly.bat" "\Program Files\BMC Software\Control-M Server\ctm_server\exe\ctmudly.bat.orig"

     
    2. Copy the old script in the exe directory taking it from the "legacy_bin" directory: 
      
      Unix:  cd ctm_server/legacy_bin/  
              cp ctmudly ctm_server/exe_<os_platform>/  
    Windows:  copy "\Program Files\BMC Software\Control-M Server\ctm_server\legacy_bin\ctmudly.exe" "\Program Files\BMC Software\Control-M Server\ctm_server\exe\ctmudly.exe" 
      
     
    At this point, the legacy ctmudly script is in use.  No recycle of the components is necessary. 
      
    Control-M/Server 9.0.19.200 is tentatively planned to be released in January 2020. 

     


    Article Number:

    000167195


    Article Type:

    Solutions to a Product Problem



      Looking for additional information?    Search BMC Support  or  Browse Knowledge Articles