WCC Export / Import

[Anon Anon]

Is there a way in WCC that you can export jobs from one environment to another? Thanks

[Jonathan Wilson]

denniscl, most customers utilize the autosys command "autorep" to move jobs between instances. However it is possible using the WCC ECLI feature
to do the same thing as long as both the Source and Target Autosys are defined within the WCC.

1. Click on the main ECLI tab
2. In the middle part of the ECLI interface fill out the fields in the "CA Workload Automation AE Import/Export" section. For an export you could
enter Name=test% and select the source Autosys instance. Then click the Export button - it will give you all the jil for jobs that start test%, in
the form of a text file. Save that file for use in the next step.
3. In the same section of ECLI, click the Browse button and locate the file you saved in step #2 (with all jobs like test%), then click the Import button.
The jobs are imported into your target Autosys. Note you might have to touch up owner, machine fields, etc so that they are correct/valid on
the target Autosys box.

I'd recommend reviewing the Tutorial section at the top-right of the WCC page to learn how to export/import calendars as well.

[Anon Anon]

Hello,
Most people like me that worked with AutoSys 4.5 over a couple years took the habit of using command line to import and export job definitions from one environment to another.

For example log into an old environment and type "autorep -j ALL -q > all_job_defs.jil"
Log into the new environment and type "jil < all_job_defs.jil"

Of course this is a very simplified way of doing it... If the "receiving" environment is not empty you may get duplicate job name errors when running the script.
Thus sometimes people do an autorep to get all the existing job names, then edit the file in vi to replace insert_job with delete_job to "trim" all the job definitions before running the insert jil.
You may also do update_job commands when necessary, for existing jobs that need to be modified.
The delete_box command can also be useful to delete a box and all the jobs it contains, in the receiving environment.

But this old-fashioned way is not necessarily recommended: I will look into using WCC to do all that, to avoid going into command line when not absolutely required.

[Anon Anon]

Hello – good feedback, thanks!
Question: Will you be using WCC if you had to dump in for example 300 jobs?

Regards,
Chris

From: CA Workload Automation (Distributed) Global User Community [mailto:[e-mail]]
Sent: October 31, 2012 11:16 AM
To: [e-mail]
Subject: [CA AutoSys Workload Automation General Discussion] RE: WCC Export / Import

Hello,
Most people like me that worked with AutoSys 4.5 over a couple years took the habit of using command line to import and export job definitions from one environment to another.

For example log into an old environment and type "autorep -j ALL -q > all_job_defs.jil"
Log into the new environment and type "jil < all_job_defs.jil"

Of course this is a very simplified way of doing it... If the "receiving" environment is not empty you may get duplicate job name errors when running the script.
Thus sometimes people do an autorep to get all the existing job names, then edit the file in vi to replace insert_job with delete_job to "trim" all the job definitions before running the insert jil.
You may also do update_job commands when necessary, for existing jobs that need to be modified.
The delete_box command can also be useful to delete a box and all the jobs it contains, in the receiving environment.

But this old-fashioned way is not necessarily recommended: I will look into using WCC to do all that, to avoid going into command line when not absolutely required.
Posted by:pgoulet
--
CA Communities Message Boards
99541012
[e-mail]
https://communities.ca.com

This email message is confidential, may be legally privileged and is intended for the exclusive use of the addressee. If you received this message in error or are not the intended recipient, you should destroy the email message and any attachments or copies, and you are prohibited from retaining, distributing, disclosing or using any information contained. Please inform us of the delivery error by return email. Thank you for your cooperation.

Le pr�sent message �lectronique est confidentiel et peut �tre couvert par le secret professionnel. Il est � l'usage exclusif du destinataire. Si vous recevez ce message par erreur ou si vous n'en �tes pas le destinataire pr�vu, vous devez d�truire le message et toute pi�ce jointe ou copie et vous �tes tenu de ne pas conserver, distribuer, divulguer ni utiliser tout renseignement qu'il contient. Veuillez nous informer de toute erreur d'envoi en r�pondant � ce message. Merci de votre collaboration

[RAMON FERRERIS]

Hi:

I have used WCC for import and exports. Now, one piece I have some
problems, It could be me, is that we are using the WCC export out of ECLI
and the output that comes out is like when you move a text file out of
unix to dos.

So I have to open the file in wordpad (or write) and then save it as
text to make it more user friendly.

I have been training my users to do the same sequence of commands.


Maybe is Me.

Thanks
Ramon
Desk: [phone]
Mobile: [phone]
Borrowed this:
The First Law of Autosys:
A Job will remain at rest until acted up by an event, at which time all
other conditions are evaluated to determine if it should run.




From: "CA Workload Automation (Distributed) Global User Community"
<[e-mail]>
To: "[e-mail]"
<[e-mail]>,
Date: 10/31/2012 11:23 AM
Subject: RE: [CA AutoSys Workload Automation General Discussion]
RE: WCC Export / Im



Hello ? good feedback, thanks!
Question: Will you be using WCC if you had to dump in for example 300
jobs?

Regards,
Chris

From: CA Workload Automation (Distributed) Global User Community [
mailto:[e-mail]]
Sent: October 31, 2012 11:16 AM
To: [e-mail]
Subject: [CA AutoSys Workload Automation General Discussion] RE: WCC
Export / Import

Hello,
Most people like me that worked with AutoSys 4.5 over a couple years took
the habit of using command line to import and export job definitions from
one environment to another.

For example log into an old environment and type "autorep -j ALL -q >
all_job_defs.jil"
Log into the new environment and type "jil < all_job_defs.jil"

Of course this is a very simplified way of doing it... If the "receiving"
environment is not empty you may get duplicate job name errors when
running the script.
Thus sometimes people do an autorep to get all the existing job names,
then edit the file in vi to replace insert_job with delete_job to "trim"
all the job definitions before running the insert jil.
You may also do update_job commands when necessary, for existing jobs that
need to be modified.
The delete_box command can also be useful to delete a box and all the jobs
it contains, in the receiving environment.

But this old-fashioned way is not necessarily recommended: I will look
into using WCC to do all that, to avoid going into command line when not
absolutely required.
Posted by:pgoulet
--
CA Communities Message Boards
99541012

[e-mail]
https://communities.ca.com

This email message is confidential, may be legally privileged and is
intended for the exclusive use of the addressee. If you received this
message in error or are not the intended recipient, you should destroy the
email message and any attachments or copies, and you are prohibited from
retaining, distributing, disclosing or using any information contained.
Please inform us of the delivery error by return email. Thank you for your
cooperation.

Le pr?sent message ?lectronique est confidentiel et peut ?tre couvert
par le secret professionnel. Il est ? l'usage exclusif du destinataire.
Si vous recevez ce message par erreur ou si vous n'en ?tes pas le
destinataire pr?vu, vous devez d?truire le message et toute pi?ce
jointe ou copie et vous ?tes tenu de ne pas conserver, distribuer,
divulguer ni utiliser tout renseignement qu'il contient. Veuillez nous
informer de toute erreur d'envoi en r?pondant ? ce message. Merci de
votre collaboration
Posted by:chris.trinidad1.1
--
CA Communities Message Boards
99540775

[e-mail]
https://communities.ca.com


*************************** IMPORTANT
NOTE*****************************-- The opinions expressed in this
message and/or any attachments are those of the author and not
necessarily those of Brown Brothers Harriman & Co., its
subsidiaries and affiliates ("BBH"). There is no guarantee that
this message is either private or confidential, and it may have
been altered by unauthorized sources without your or our knowledge.
Nothing in the message is capable or intended to create any legally
binding obligations on either party and it is not intended to
provide legal advice. BBH accepts no responsibility for loss or
damage from its use, including damage from virus.
*******************************************************************************

[Anon Anon]

I know this thread is super old however I think for others searching for help it's useful knowledge.

 

We also just recently upgraded from autosys 4.5 to 11.3 and we had a script that uses this basic principle. However when we used jil to delete the current DEV schedule and import the modified job definitions in its place we would get strange behavior from the UI. I would be able to list all the boxes and jobs using wildcards but when clicking on them I would be greeted with the message I131001 No matches for the search criteria.

 

Sometimes I would be able to see a box's definition but had a red error saying there were problems loading the page. When clicking on any of that box's jobs or children, I would go back to I131001 No matches for the search criteria.

Eventually I figured out that by changing our method of deleting the jobs with a straight delete_job on all previous job definitions, I isolated the boxes on their own and used delete_box instead and stopped bothering with the children of those boxes since delete_box takes care of the hierarchy during deletion.

 

The UI was MUCH happier with this approach and no longer broke the relationships between boxes and their children.

 

I hope this is useful to someone else as I spent many hours figuring out the problem.