Data collection

• Lines of Business
• Location Job owners (Point of contact information)
• Generate a JIL file (export jobs) from the latest AutoSys job definitions.
• Run analysis scripts on JIL file and review results
• Run the AutoSysConvert.pl script to perform initial conversion
• Examine customer’s organizational structure (who owns what jobs?)
• Review customer’s batch documentation standards
• Gather customer job scripts to support identifying embedded AutoSys utilities.
• Gather a list of service accounts used with the jobs
• Gather a list of non-expired service accounts used with the jobs
• Gather a list of privileged service accounts used with the jobs
• Gather a list of privileged non-expired service accounts used with the jobs

Initial Assessment

• Review data collected from customer’s current environment
• Identify functionality not directly converted by initial conversion
• Identify impact of conversion on customer’s job scripts, if any
• Identify risk areas

Project phases

• Typically phased by organizational or application group boundaries
• Goal is to plan phases with jobs that can be converted independently
• Risk mitigation
• Effort to complete conversion

Convert AutoSys objects to WCC objects

• AutoSysConvert.pl typically customized to optimize conversion
• Run script to produce WCC Job and Job Stream definition files
• Review files for missing functionality identified by conversion script
• Identify intent of missing functionality
• Identify equivalent WCC implementation
• Potentially update autoSysConvert.pl to further automate conversion
• Compare generated WCC objects to AutoSys job definitions and customer documentation

Additional Conversion steps

• Eliminate AutoSys utilities from Customer job scripts
• Recommend / Make changes
• Test updated job scripts
• Generate implementation documentation consistent with customer’s standards
• Present conversion results and documentation to job/application owner
• Incorporate review feedback into the converted WCC scheduling objects and documentation

Test Conversion

• Identify test cases required to validate conversion
• Load WCC scheduling objects into a test environment
• Stub any applications not available in test environment
• Execute test cases
• Verify functional equivalence of WCC scheduling objects
• Use WCC reporting to verify job stream Run Cycles

Production Cutover

• Identify back out plan
• Transition converted AutoSys jobs into production
• Monitor production during initial cutover
• Obtain acceptance from Job / Application owners