Launch job that is not shell script
Launch job that is not shell script
Hi I have a problem to launch controlm jobs.
I have this job with task type job:
#!/bin/env /opt/myshell.sh
echo ok
When I launch it, the controlm execute: /bin/sh -x myjob
I want that controlm execute: myjob (without /bin/sh)
Can someone help me?
I have this job with task type job:
#!/bin/env /opt/myshell.sh
echo ok
When I launch it, the controlm execute: /bin/sh -x myjob
I want that controlm execute: myjob (without /bin/sh)
Can someone help me?
- th_alejandro
- Nouveau
- Posts: 188
- Joined: 26 Nov 2008 12:00
- Location: Bogotá
Just write the command in the command option
Do not use a shell to run a single command. Simply, type your command in 'Command' (General tab) and Select 'Task Type' as 'Command' from selection list.
- th_alejandro
- Nouveau
- Posts: 188
- Joined: 26 Nov 2008 12:00
- Location: Bogotá
why not ?
Why you can't change this from EM GUI ?.
Check your autorizathion profile.
Check your autorizathion profile.
- th_alejandro
- Nouveau
- Posts: 188
- Joined: 26 Nov 2008 12:00
- Location: Bogotá
of course you can.
Of course you can.
- Simply, hold your job.
- Doble-click to edit properties
- Click on general tab
- Check your 'Job Type' is OS.
- Type the new command in '*Command:' entry.
- Click on Save & Close button
- Free your job
- Rerun your job
This operation only work until the next new Day. To make changes for all day, you must edit ypour job using Desktop and re-save the table.
- Simply, hold your job.
- Doble-click to edit properties
- Click on general tab
- Check your 'Job Type' is OS.
- Type the new command in '*Command:' entry.
- Click on Save & Close button
- Free your job
- Rerun your job
This operation only work until the next new Day. To make changes for all day, you must edit ypour job using Desktop and re-save the table.
- nicolas_mulot
- Nouveau
- Posts: 149
- Joined: 07 Jan 2010 12:00
kambiante,
Refer to "Specifying the shell type" in the "control-m administrator guide" (V6.4.xx) or "control-m agent for Unix and Microsoft Windows administrator guide", if you use V6.3.xx.
According to the information specified here, it looks like controlm expects YOU to specify either /bin/sh, ksh, csh or tcsh.
This is not what you specify in your example, so ctm should apply a default of /bin/sh ( I could not identify where from).
If you read a bit further, the table "Shell parameters" tells that you can adjust the behaviour of the shell. The "n" option seem to address
your request. Please note the restriction attached to this parm.
Tell us the results
Nicolas Mulot
Refer to "Specifying the shell type" in the "control-m administrator guide" (V6.4.xx) or "control-m agent for Unix and Microsoft Windows administrator guide", if you use V6.3.xx.
According to the information specified here, it looks like controlm expects YOU to specify either /bin/sh, ksh, csh or tcsh.
This is not what you specify in your example, so ctm should apply a default of /bin/sh ( I could not identify where from).
If you read a bit further, the table "Shell parameters" tells that you can adjust the behaviour of the shell. The "n" option seem to address
your request. Please note the restriction attached to this parm.
Tell us the results
Nicolas Mulot
- nicolas_mulot
- Nouveau
- Posts: 149
- Joined: 07 Jan 2010 12:00
kambiante,
I have no opportunity to test your case.
Did you set the "Bourne Shell Flags" to "n" using the ctmagcfg utility ?
If so, I cannot help you any further and, as mentionned previously, it seems that controlm does not siupport other shels than the 4 listed in the agent admin guide
Cheers
Nicolas Mulot
I have no opportunity to test your case.
Did you set the "Bourne Shell Flags" to "n" using the ctmagcfg utility ?
If so, I cannot help you any further and, as mentionned previously, it seems that controlm does not siupport other shels than the 4 listed in the agent admin guide
Cheers
Nicolas Mulot
- nicolas_mulot
- Nouveau
- Posts: 149
- Joined: 07 Jan 2010 12:00