The OPSAUTO function enables you to query and change the autoenabled status of rule members before CA OPS/MVS is active. Doing so through ADDRESS AOF host commands requires CA OPS/MVS to be active.
Note: You can use OPSAUTO in OPS/REXX and in the PROC section of an AOF TOD rule, but not in any other rule context.
Example: Set autoenabled status
This REXX statement sets the autoenabled status of mem1 and resets the status of mem2. All arguments are converted to uppercase.
address TSO
"ALLOC FILE(DD1) DA('OPS.TEST.RULES') SHR REUSE"
Old_State_Mem1 = OPSAUTO("S","DD1","mem1")
Old_State_Mem2 = OPSAUTO("R","DD1","mem2")
"FREE FILE(DD1)"
OPSAUTO returns a single character indicating the autoenabled status of a member of a rule data set before this function executed. If the function returns the character Y, the member is autoenabled; a returned N indicates that the member is not autoenabled. If the returned value contains more than one character, that value is an error message.
The OPSAUTO function has the following format:
var = OPSAUTO(func,ddname,member)
The func code may be one of the following:
Inquires about the autoenabled status of the specified member.
Resets the autoenabled flag for the specified member.
Sets the autoenabled flag for the specified member.
The ddname is the name of a previously allocated ddname; it must represent a partitioned data set. Allocate the rule data set using the ADDRESS OPSDYNAM or TSO ALLOCATE command or an equivalent method.
The member is the name of any existing member in the data set associated with the ddname. This member must have valid ISPF statistics.
| Copyright © 2011 CA. All rights reserved. | Tell Technical Publications how we can improve this information |