Table of Contents


  1. Preface
  2. Command Line Programs and Utilities
  3. Installing and Configuring Command Line Utilities
  4. Using the Command Line Programs
  5. Environment Variables for Command Line Programs
  6. Using infacmd
  7. infacmd as Command Reference
  8. infacmd aud Command Reference
  9. infacmd autotune Command Reference
  10. Infacmd bg Command Reference
  11. infacmd ccps Command Reference
  12. infacmd cluster Command Reference
  13. infacmd cms Command Reference
  14. infacmd dis Command Reference
  15. infacmd dp Command Reference
  16. infacmd idp Command Reference
  17. infacmd edp Command Reference
  18. Infacmd es Command Reference
  19. infacmd ihs Command Reference
  20. infacmd ipc Command Reference
  21. infacmd isp Command Reference
  22. infacmd ldm Command Reference
  23. infacmd mas Command Reference
  24. infacmd mi Command Reference
  25. infacmd mrs Command Reference
  26. infacmd ms Command Reference
  27. infacmd oie Command Reference
  28. infacmd ps Command Reference
  29. infacmd pwx Command Reference
  30. infacmd roh Command Reference
  31. infacmd rms Command Reference
  32. infacmd rtm Command Reference
  33. infacmd sch Command Reference
  34. infacmd search Command Reference
  35. infacmd sql Command Reference
  36. infacmd tdm Command Reference
  37. infacmd tools Command Reference
  38. infacmd wfs Command Reference
  39. infacmd ws Command Reference
  40. infacmd xrf Command Reference
  41. infacmd Control Files
  42. infasetup Command Reference
  43. pmcmd Command Reference
  44. pmrep Command Reference
  45. Working with pmrep Files



Updates a schedule that the Scheduler Service manages. Update a schedule to change the start or end times, recurrence, or objects that run on the schedule. To view the current options, run the infacmd sch ListSchedule command.
The infacmd sch
command uses the following syntax:
<-DomainName|-dn> domain_name <-UserName|-un> user_name <-Password|-pd> password [<-SecurityDomain|-sdn> security_domain] [<-Gateway|-hp> gateway_host1:port gateway_host2:port...] [<-ResilienceTimeout|-re> timeout_period_in_seconds]
<-ScheduleName|-scn> schedule_name [<-ScheduleDescription|-scd> schedule_description] <-Recurrence|-r> once|daily|weekly|monthly <-StartTime|-st> yyyy-MM-dd HH:mm [<-EndTime|-et> yyyy-MM-dd HH:mm] [<-TimeZone|-tz> time_zone] [<-DailyRunEvery|-dre> daily_run_every] [<-RunDaysOfWeek|-rdw> mon|tue|wed|thu|fri|sat|sun] [<-RunDayOfWeekMonth|-rdwm> monday|tuesday|wednesday|thursday|friday|saturday|sunday] [<-RunDayOfMonth|-rdm> 1-30|LAST_DAY_OF_MONTH] [<-RepeatCount|-rc> repeat_count] [<-RemoveRunnableObjects|-rro> removeRunnableObjects] [<-AddRunnableObjects|-aro> addRunnableObjects]
To configure multiple values for an argument, separate the values with commas.
The following table describes infacmd sch
options and arguments:
Name of the Informatica domain.
User name to connect to the domain
Password for the user name.
Name of the security domain to which the domain user belongs.
gateway_host1:port gateway_host2:port ...
Required if the gateway connectivity information in the domains.infa file is out of date. The host names and port numbers for the gateway nodes in the domain.
Amount of time in seconds that infacmd attempts to establish or re-establish a connection to the domain.
Required. Name of the schedule. The schedule name is case sensitive.
Optional. Schedule description.
Required. Specify whether the schedule runs once or recurs.
yyyy-MM-dd HH:mm
Required. Date and time that the recurrence starts.
yyyy-MM-dd HH:mm
Optional. Date and time that the recurrence ends.
Optional. Time zone for the schedule start time.
To configure the time zone, you can enter the time zone ID number or the Olson Database ID.
Default is locale of the client machine.
Optional. Run the schedule on an interval.
The following list describes the options that you can configure:
  • minute(s). Run the schedule daily every n minutes.
  • hour(s). Run the schedule daily every n hours.
  • day(s). Run the schedule every n days.
  • week(s). Run the schedule every n weeks.
  • month(s). Run the schedule every n months.
  • year(s). Run the schedule every n years.
  • FIRST. Run the schedule every first n day of the month. Use the -rdwm option to specify the day or days of the week.
  • SECOND. Run the schedule every second n day of the month. Use the -rdwm option to specify the day or days of the week.
  • THIRD. Run the schedule every third n day of the month. Use the -rdwm option to specify the day or days of the week.
  • FOURTH. Run the schedule every fourth n day of the month. Use the -rdwm option to specify the day or days of the week.
  • LAST. Run the schedule every last n day of the month. Use the -rdwm option to specify the day or days of the week.
Optional. Run the schedule on certain days of the week.
Optional. Run the schedule on certain days of the week every month. Use the -dre options to run the schedule every first, second, third, fourth, or last n day of the month.
Optional. Run the schedule on day n of the month.
Optional. End the recurrence after a number of runs instead of on a date.
Optional. Removes objects from the schedule. Enter objects in the following format:
"{mapping|workflow}:Data Integration Service/Application/{Mapping|Workflow}[[?]
Optional. Adds objects to the schedule. Objects that you would like to schedule. Enter the object type, followed by the path to the object on the Data Integration Service. For example:
Optionally, use the following arguments to configure a parameter file, parameter set, run as user, or operating system profile for the object:
  • parameterFilePath=PATH_TO_PARAMETER_FILE
  • parameterSet=PARAMETER_SET_NAME
  • runAsUser=USER_NAME
  • osProfileName=OS_PROFILE_NAME
For example:
C://Informatica/Parameter Files/Parameter.xml
For a list of the valid time zone values, see Valid Time Zone Parameters.


We’d like to hear from you!