Syntax
WAKE report_name [ PA expression ] [ GS status ]
Parameters
Wake can be abbreviated as WU.
report_name
The report to reactivate.
PA expression
Specifies a text or numeric expression to pass to to the report. This bypasses the prior move to the Glb.Param built-in segment attribute. If a numeric value is used, it is converted to text.
Refer to Passing Parameters for more information.
This expression is limited to a maximum length of 254 characters.
Note: This length restriction does not apply to Windows runtime.
GS status
Indicates, using the specified variable, that there is no eligible target report.
Description
The Wake logic command reactivates a report suspended by a previous Sleep or CriticalPoint logic command. When a Wake logic statement is executed, a Wake message is sent to the specified report.
The Wake logic command can also be executed from a report method. If multiple copies of the report are running, each copy of the report is set a Wake message by the Wake logic command. Specifically, it sends Wake messages to any reports with the same repository path, segment name, and report name that are suspended on the same workstation.
If multiple copies of the report are running, only one copy receives the data specified by the PA command option.
Reports check for Wake messages when Sleep or CriticalPoint logic statements are executed.
Passing parameters
If a parameter is passed, the Glb.ParamFlag built-in segment attribute is first set to Y in the report, to signal that there is parameter data included with the Wake logic command. Glb.ParamFlag is then set to the appropriate value (which depends on whether data has been sent) at the next Sleep logic command or CriticalPoint Sleep logic command variant.
Parameter data is not saved for recovery.
Note: For MCP-based systems, if the Wake command includes parameter data it is queued for all copies of the Report.
Failure behavior
If there is no eligible target report, the Glb.Status built-in segment attribute is set to "*****". Use the GS logic command option to direct the Glb.Status built-in segment attribute value to a variable.
Restrictions
The following restrictions apply to the Wake logic command:
If the specified report is not running, the Wake message is discarded.
For an MCP-based system, the WAKE.UP; command is ignored in standalone Reports and in Reports generated as Coroutines. Refer to the Agile Business Suite Runtime for ClearPath MCP Administration Guide for more information on Coroutines.
For an MCP-based system, if the Report currently has 63 outstanding input messages a WAKE.UP; command is not sent.
Queued Wake messages are not recovered.
Note: For more details on waking large numbers of reports in MCP-based systems, refer to the Agile Business Suite Runtime for ClearPath MCP Administration Guide, Waking a Sleeping Report.
Example
If SD_CustCnt <> Glb.Zeros Wake Invoice PA Cust_Param GS Param_Status End