Where to put the OPTIONS instruction in an AOF RULE

[Marcel van Ek]

Can someone conslusively explain the difference of putting this line in an AOF rule )INIT section, versus putting it in the )PROC section?

 

options "NOFIRELIMIT NOMAXTIME NOMAXCLAUSES NOMAXCOMMANDS" 

 

The doc mentions that putting it in a )PROC section, it will not be effective the very first time the code executes, but will affect all consequent firings.

We thought putting it in the )INIT section would then also affect the first firing of the rule, but tests indicate that it won’t work at all.  ?

So if we now understand correctly, putting an options instruction in the )INIT section only affects the )INIT section, not the rest of the rule.. Correct?

 

Regards,

 

Marcel van Ek,

ATOS NL

[Chris_Stallone]

Anyone able to assist Marcel?

 

Marcel van Ek wrote:

 

Can someone conslusively explain the difference of putting this line in an AOF rule )INIT section, versus putting it in the )PROC section?

 

options "NOFIRELIMIT NOMAXTIME NOMAXCLAUSES NOMAXCOMMANDS" 

 

The doc mentions that putting it in a )PROC section, it will not be effective the very first time the code executes, but will affect all consequent firings.

We thought putting it in the )INIT section would then also affect the first firing of the rule, but tests indicate that it won’t work at all.  ?

So if we now understand correctly, putting an options instruction in the )INIT section only affects the )INIT section, not the rest of the rule.. Correct?

 

Regards,

 

Marcel van Ek,

ATOS NL

[dan Lutkus]

Marcel,  the options  statements are handled by a grex exit that gets executed when the "section" is executed.   So if you want the option statement to affect the rule before its first firing,  you must put the OPTIONS statement in the INIT section of the rule.  If you put it in the PROC section of the rule, the option won't be available until the rule fires once.   What anomaly did you see?     

[dan Lutkus]

Marcel,  the options  statements are handled by a grex exit that gets executed when the "section" is executed.   So if you want the option statement to affect the rule before its first firing,  you must put the OPTIONS statement in the INIT section of the rule.  If you put it in the PROC section of the rule, the option won't be available until the rule fires once.   What anomaly did you see? 

[Marcel van Ek]

Hi Dan,

we had this in the )INIT section of a )CMD rule (that called STATESET rexx in the )PROC section )

options "NOFIRELIMIT NOMAXTIME NOMAXCLAUSES NOMAXCOMMANDS" 

Still we noticed this error a few times lately:

OPS1097J ERROR 97 RUNNING STATESET, LINE 1139: OVER 128 CLAUSES EXECUTED

Now, it doen't even explain the 128 limit (our related parms are

AOFMAXCLAUSES

25000

REXXMAXCLAUSES

1000000

 

So that's not it...

But since we thought that any maxclause limit was prevented, no idea where it came from....

We moved the options into the )PROC section, and have not encountered it since....

[dan Lutkus]

Sorry for the duplicate messages, but I do see where in the code maxclauses is overridden when the PROC section executes in the REXX related control blocks.  I need to investigate a bit to see if we can make this work more logically..