Control-M Agent failed to execute job as the job is unable to generate SYSOUT or OUTPUT, throw "CTM5125 OUTPUT FILE OPEN ERROR" error and exit with "exit code 128"

Version 2
    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/Agent for UNIX and Microsoft Windows


    COMPONENT:

    Control-M/Agent for UNIX and Microsoft Windows


    APPLIES TO:

    All versions of Control-M/Agent for UNIX and Microsoft Windows Microsoft Windows Only



    PROBLEM:

    - Control-M job are submitted to Control-M/Agent for execution but failed exit code 128 and unable to open output file
    - From the CTMRJOBWIN2K_*.log, the following error related to exit code 128 is reported:
    0515 12:29:35:829 CTMRJOBWIN2K:        using sysout: 'I:\Program Files\BMC Software\Control-M Agent\<Agent Node ID>\SYSOUT\mem_<Order ID>_<Runcount>.dat'
    0515 12:29:35:845 CTMRJOBWIN2K:<<< addRedirectionToSysout exit with :'1'
    0515 12:29:35:845 CTMRJOBWIN2K:        using command line: '".\TEMP\00rki.cmd" >> "I:\Program Files\BMC Software\Control-M Agent\<Agent Node ID>\SYSOUT\mem_<Order ID>_<Runcount>.dat'" 2>&1 '
    0515 12:29:36:595 CTMRJOBWIN2K:      _access is looking for the : 'I:\Program Files\BMC Software\Control-M Agent\<Agent Node ID>\SYSOUT\mem_<Order ID>_<Runcount>.dat'
    0515 12:32:59:312 CTMRJOBWIN2K:        FAIL to find the file after -- 500 times
    0515 12:32:59:312 CTMRJOBWIN2K:<<< isExistSysoutFile exit with: '0'
    0515 12:32:59:312 CTMRJOBWIN2K:        The Job Exit code is: '128'

    - The Control-M job output will throw the following error:
    Failed to get output datas.
    Code: 0, msg:Request rejected by Data Center
    CTM5125 OUTPUT FILE OPEN ERROR: No such file or directory
     


    CAUSE:

    Microsoft Windows Operating System is denying Control-M/Agent to start a process to run the job.


    SOLUTION:

    - Do discuss with the System Administrator is there is restriction on the Operating System or policy which prevent the Control-M/Agent to start a process to run a job.
    - Following are alternative solutions to use while the system administrator is investigating the root cause:
    Solution 1:
    1. On the Control-M/Agent Windows machine, Go to "Start" -> Run
    2. Enter "services.msc" to launch the Windows Services Windows
    3. Right-click on the Control-M/Agent
    4. Select Properties
    5. On the "Log On" tab enable the option for "Allow service to interact with desktop"
    6. Restart the agent.


    Solution 2:
    - Review the Control-M job definition and ensure that the TASKTYPE is COMMAND instead of JOB
    - Do esnure that the MEMNAME and MEMLIB is removed from the Control-M Job definition:

    1. Choose Tasktype JOB
    2. Remove the value in MEMNAME and MEMLIB field
    3. Change back to Tasktype back to COMMAND.


    Article Number:

    000153542


    Article Type:

    Solutions to a Product Problem



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