When a user initiates an application that VirtualZ has been configured to manage (such as a COBOL compiler), VirtualZ intercepts and redirects that application’s processing as directed by your VirtualZ policies.
When VirtualZ detects the execution of an application it has been configured to manage, your policies are evaluated to determine where that application should execute. The application can be routed to any z/OS system in your organization over your TCP/IP network. It’s possible to designate different target destinations depending on user identity, accounting information, or jobnames, giving you the ability to steer work to different targets based on your business priorities. You can also have multiple targets, either for full tolerance, load balancing, or whatever other reason you like.
When the request reaches the desired destination, VirtualZ orchestrates running the unit of work on the target system, including automatically tailoring the JCL for that application according to the unique configuration of the target system. This tailoring process allows you to compensate for subtle differences between the original source system and the target system, such as differences in dataset names or other z/OS configuration differences. This approach helps to ensure that the application will run properly, even if the target is not an exact clone of the source system.
The application executes normally on the target system with VirtualZ returning all processing results back to the original submitting system’s job step. Messages, data, and SYSOUT generated by the target application are all captured and dynamically returned to the submitter as the target job runs.
The original user sees the same output, return codes, and results as if the job had been run locally. Thus, the user is provided with the seamless experience expected from a locally processed unit of work.
The key is that with VirtualZ, the user operates as usual, makes no changes, and is totally unaware of the redirection of the work. VirtualZ gives you the flexibility to take advantage of excess capacity or adapt to sudden changes in business requirements. By simply changing your VirtualZ policies, the system can redirect your workloads in whatever manner you choose, and you can modify these policies at any time to meet changing requirements.