IF the batch job is scheduled, and IF you have an automated operations tool, and IF your scheduler has an external command interface, THEN:
What we (in Pecan/Beta42/ASG Workload scheduler) was define a variable (example $CICS1), and make a predecessor for the batch job with the value $CICS1 = UP. In the automated operations too, we had two message traps: one for the HASP message indicating CICS1 started, which would set the variable to UP, and one for the HASP message indicating CICS1 ended, setting the variable to DOWN. The scheduler would then only start the job when the variable was set to UP. I believe you can do a similar thing with scheduling environment (SCHENV= on the job card), too. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
