The following are special considerations when using the EVOKE keyword.
Four bytes must be added to the length of each of these parameters. An additional 4 bytes must be added if any parameters are specified. These bytes are required by the system.
Use the following formula to determine the total length of the
parameters:
4 + (length of 1st parameter + 4) + (length of
2nd parameter + 4)
+ ... (length of nth parameter + 4)
Following is an example using this formula:
EVOKE(LIBRARY1/PROGRAM1 'THIS IS AN EXAMPLE OF
A
CHARACTER STRING' &FIELD1 35)
Assume that &FIELD1 has a length of 10.
4 + (40 + 4) + (10 + 4) + (2 + 4) = 68
This keyword is required when either the SECURITY or SYNLVL keywords are specified. At run time, the SECURITY and SYNLVL keywords are used only when EVOKE is also in effect.
The EVOKE keyword is ignored at run time when CANCEL, CNLINVITE, EOS, FAIL, NEGRSP, RSPCONFIRM, or RQSWRT is in effect. These keywords must have option indicators when they apply to a record for which the EVOKE keyword applies. If a CANCEL, CNLINVITE, EOS, FAIL, NEGRSP, or RQSWRT keyword with no option indicator applies to a record for which EVOKE applies, an error message is issued and the EVOKE keyword is ignored at creation time.
You cannot specify EVOKE with the TIMER keyword.
Option indicators are valid for this keyword and are required if this keyword is specified more than once for each record format or file.
(C) Copyright IBM Corporation 1992, 2006. All Rights Reserved.