Maintaining compatibility with scheduling solutions

Here’s a simple worked example of how S2PX will maintain compatibility of your solution with your existing job scheduling tools.

Unknown Attachment

Given 2 server jobs and 1 sequencee …

 Seq1 runs and calls srv1 then srv2.

What you’ll get after S2PX conversion is …

• srv1 -> Px Job srv1P1 and Px Job  srv1P2 with a Sequence Job srv1  to run them, and

• srv2 -> PX Job srv2 (with no co-ordinating Sequence Job required)

(Assuming a backup strategy of BACKUP_SERVER_JOB with suffix Px , the original srv1 will be backed up to srv1Px and  srv2 backed up to srv2Px.)

The original Seq1 will (without requiring modification) now invoke …

1. Sequence Job srv1 (which itself runs Px Job srv1P1 and Px Job srv1P2 ), then

2. PX Job srv2

Unknown Attachment