Hi Uma,
for this case you can use FileEvent Objects too. The FileEvent Object gives you a little bit more flexibility than filter systemoutput.
You can script something like this:
: SET &E2# = GET_FILESYSTEM(<YourUnixServer>,'</your/unix/path/filename',PATH_FILE_COUNT)
: IF &E2# = 1
: PRINT "Eureka file is ready"
: PRINT "Countet Files &E2#"
: ELSE
: PRINT " I'm still waiting"
: ENDIF
For more Information about FileEvent Objects see Automic Manual File Event
Hope that helps
Andrzej Golaszewski
------------------------------
Senior Administrator and Consultant Business Automation
SID-LRZS
------------------------------
Original Message:
Sent: 08-03-2020 01:05 PM
From: Uma J
Subject: How to trigger Windows jobs based on output of UNIX jobs
Hi,
I am looking for a solution with steps as how to trigger Windows jobs based on the output status of a UNIX job in CA Workload Automation Desktop Client Version: 12.1.00.00
In the Unix script we can only create the output status of existence of file or not.
It the file exists, then it has it trigger Windows jobs otherwise no action has to be done. In the Unix job (in Unix Server A), how can that output status be setup and sent as input value so that it can trigger the refresh scripts in the Windows job (in Windows Server B). The servers A and B has no connectivity, hence through D-Series we wanted to handle.
Thanks in Advance
------------------------------
Uma
------------------------------