Limited support

   

BMC provides limited support for this version of the product. As a result, BMC no longer accepts comments in this space. If you encounter problems with the product version or the space, contact BMC Support.

BMC recommends upgrading to the latest version of the product. To see documentation for that version, see BMC AMI Batch Optimizer (Advanced and Standard) 2.9.

Change of VIO devices to non-VIO devices

If a step allocates a data set on a VIO device, Job Optimizer cannot split the step. You can change the allocation to a non-VIO device by using the EVENT=CHANGE statement in a UCF member.

For example, if you know that a data set uses a VIO device named VIO, you can change it to use a non-VIO device named SYSDA by using the following statements:

EVENT=CHANGE
EVENTID=UNIT
FROM=VIO 
TO=SYSDA

As another example, if your storage group ACS routine assigns a storage group of SMSVIO, you can have Job Optimizer override those assignments with another storage group by including a statement in your UCF member. This action override allows your ACS routines to remain as they are coded and only affects those jobs that are under the control of Job Optimizer.

EVENT=CHANGE
EVENTID=STORGRP 
FROM=SMSVIO 
TO=SMSNOVIO


Was this page helpful? Yes No Submitting... Thank you

Comments