It is possible to have several different versions of $OPTIONS for use with ASM2.
How do I use a different $OPTIONS member for a specific ASM2 job that may have different settings?
This will force ASM2 to use the new $OPTIONx version for this step.
NOTE: "x" designates any alpha numeric character, for example, $OPTIONZ