Communities
A collaborative platform to connect and grow with like-minded Informaticans across the globe
Product Communities
Connect and collaborate with Informatica experts and champions
Discussions
Have a question? Start a Discussion and get immediate answers you are looking for
User Groups
Customer-organized groups that meet online and in-person. Join today to network, share ideas, and get tips on how to get the most out of Informatica
Get Started
Community Guidelines
Knowledge Center
Troubleshooting documents, product guides, how to videos, best practices, and more
Knowledge Base
One-stop self-service portal for solutions, FAQs, Whitepapers, How Tos, Videos, and more
Support TV
Video channel for step-by-step instructions to use our products, best practices, troubleshooting tips, and much more
Documentation
Information library of the latest product documents
Velocity (Best Practices)
Best practices and use cases from the Implementation team
Learn
Rich resources to help you leverage full capabilities of our products
Trainings
Role-based training programs for the best ROI
Certifications
Get certified on Informatica products. Free, Foundation, or Professional
Product Learning Paths
Free and unlimited modules based on your expertise level and journey
Resources
Library of content to help you leverage the best of Informatica products
Tech Tuesdays Webinars
Most popular webinars on product architecture, best practices, and more
Product Availability Matrix
Product Availability Matrix statements of Informatica products
SupportFlash
Monthly support newsletter
Support Documents
Informatica Support Guide and Statements, Quick Start Guides, and Cloud Product Description Schedule
Product Lifecycle
End of Life statements of Informatica products
Ideas
Events
Change Request Tracking
Marketplace
English
  • Common Content for Data Engineering 10.2.1
  • All Products

Table of Contents

Search

  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 dps Command Reference
  16. infacmd edl Command Reference
  17. Infacmd es Command Reference
  18. infacmd ihs Command Reference
  19. infacmd ipc Command Reference
  20. infacmd isp Command Reference
  21. infacmd ldm Command Reference
  22. infacmd mas Command Reference
  23. infacmd mi Command Reference
  24. infacmd mrs Command Reference
  25. infacmd ms Command Reference
  26. infacmd oie Command Reference
  27. infacmd ps Command Reference
  28. infacmd pwx Command Reference
  29. infacmd rms Command Reference
  30. infacmd rtm Command Reference
  31. infacmd sch Command Reference
  32. infacmd search Command Reference
  33. infacmd sql Command Reference
  34. infacmd tdm Command Reference
  35. infacmd wfs Command Reference
  36. infacmd ws Command Reference
  37. infacmd xrf Command Reference
  38. infacmd Control Files
  39. infasetup Command Reference
  40. pmcmd Command Reference
  41. pmrep Command Reference
  42. Working with pmrep Files

Command Reference

Command Reference

Back Next

UpdateSchedule

UpdateSchedule

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
UpdateSchedule
 command uses the following syntax: 
UpdateSchedule
<-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
UpdateSchedule
 options and arguments:
Option
Argument
Description
-DomainName
-dn
domain_name
Required. Name of the Informatica domain. You can set the domain name with the -dn option or the environment variable INFA_DEFAULT_DOMAIN. If you set a domain name with both methods, the -dn option takes precedence.
-UserName
-un
user_name
Required if the domain uses Native or LDAP authentication. User name to connect to the domain. You can set the user name with the -un option or the environment variable INFA_DEFAULT_DOMAIN_USER. If you set a user name with both methods, the -un option takes precedence.
Optional if the domain uses Kerberos authentication. To run the command with single sign-on, do not set the user name. If you set the user name, the command runs without single sign-on.
-Password
-pd
password
Required if you specify the user name. Password for the user name. The password is case sensitive. You can set a password with the -pd option or the environment variable INFA_DEFAULT_DOMAIN_PASSWORD. If you set a password with both methods, the password set with the -pd option takes precedence.
-SecurityDomain
-sdn
security_domain
Required if the domain uses LDAP authentication. Optional if the domain uses native authentication or Kerberos authentication. Name of the security domain to which the domain user belongs. You can set a security domain with the -sdn option or the environment variable INFA_DEFAULT_SECURITY_DOMAIN. If you set a security domain name with both methods, the -sdn option takes precedence. The security domain name is case sensitive.
If the domain uses native or LDAP authentication, the default is Native. If the domain uses Kerberos authentication, the default is the LDAP security domain created during installation. The name of the security domain is the same as the user realm specified during installation.
-Gateway
-hp
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.
-ResilienceTimeout
-re
timeout_period_in_seconds
Optional. Amount of time in seconds that infacmd attempts to establish or re-establish a connection to the domain. If you omit this option, infacmd uses the timeout value specified in the INFA_CLIENT_RESILIENCE_TIMEOUT environment variable. If no value is specified in the environment variable, the default of 180 seconds is used.
-ScheduleName
-scn
schedule_name
Required. Name of the schedule. The schedule name is case sensitive.
-Description
-scd
schedule_description
Optional. Schedule description.
-Recurrence
-r
once|daily|weekly|monthly
Required. Specify whether the schedule runs once or recurs.
-StartTime
-st
yyyy-MM-dd HH:mm
Required. Date and time that the recurrence starts.
-EndTime
-et
yyyy-MM-dd HH:mm
Optional. Date and time that the recurrence ends.
-TimeZone
-tz
timezone
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.
-DailyRunEvery
-dre
daily_run_every
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.
-RunDaysOfWeek
-rdw
mon|tue|wed|thu|fri|sat|sun
Optional. Run the schedule on certain days of the week.
-RunDayOfWeekMonth
-rdwm
monday|tuesday|wednesday|thursday|friday|saturday|sunday
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.
-RunDayofMonth
-rdm
1-30|LAST_DAY_OF_MONTH
Optional. Run the schedule on day n of the month.
-RepeatCount
-rc
repeat_count
Optional. End the recurrence after a number of runs instead of on a date.
RemoveRunnableObjects
-rro
removeRunnableObjects
Optional. Removes objects from the schedule. Enter objects in the following format:
"{mapping|workflow}:Data Integration Service/Application/{Mapping|Workflow}[[?]
[parameterFilePath=PATH_TO_PARAMETER_FILE|
parameterSet=PARAMETER_SET_NAME]
&runAsUser=USER_NAME
&runAsUserSecurityDomain=SECURITY_DOMAIN
&runAsUserPassword=PASSWORD]]"]
-AddRunnableObjects
-aro
addRunnableObjects
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:
"mapping:DIS_1234/Application_mapping/Mapping_abc"
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
    &runAsUserSecurityDomain=SECURITY_DOMAIN
    &runAsUserPassword=PASSWORD
  • osProfileName=OS_PROFILE_NAME
For example:
"workflow:DIS_1234/Application_workflow/Workflow_abc?parameterFilePath=
C://Informatica/Parameter Files/Parameter.xml
&runAsUser=Administrator
&runAsUserSecurityDomain=Native
&runAsUserPassword=Administrator"
For a list of the valid time zone values, see Valid Time Zone Parameters.
0 COMMENTS
We’d like to hear from you!