Caché up to 2018.1  and early versions of IRIS didn't have this
%sqlc. .....   feature

Awaiting Review simply says that no member has written a review yet
that was approved for publishing.
Actually, out of 1236 packages 
959 have a review which is ~77.7%  since start of OEX 
It could take hours but also  years

To clarify things:

• ##class(SYS.Database).shows only the actual status Mounted / Unmounted
• It doesn't record any transitions
• DISMOUNTED (same as MOUNTED) is such a transition
• It is recorded in messages.log of your system directory

Example:
06/10/26-22:00:23:437 (14644) 0 [Generic.Event] Dismounted database c:\intersystems\iris242\mgr\uiris\ 
That's what you you have to scan if you chase the transition
 

not correct. SINGLE line ELSE is part of Objectscript since ever
You just need a double space after the ELSE

USER>p 
ck       read "?",x,! 
         if x?.N write "numeric",! 
         else  write "other",! 
         goto ck 
USER>d ck 
?5 
numeric 
?a 
other

• This example is using a TEMPORARY Table based on Process Private Globals.
• You can access the content of the table just from the process that created the table. 
  Not from any other process.
• From SMP you see the Table Definition from any Namespace because ot the %ZZ. package.
  so the table is FOUND but EMPTY
• Though your SELECT from SMP runs in a totally different process with anything but your Process Private Global
• You have to get your final SELECT and generating your temporary table into the same Process,

• To achieve this in SMP, declare your ClassMethod As SqlProcedure like this:

  ClassMethod Export(nspace = "", query As %String = "") As %Integer [ SqlName = ZZEXPORT, SqlProc ]
  {
  	new $namespace
  	;; and so on

• Then you can run it from SMP using this SQLprocedure as Static WHERE condition.

  SELECT * from %ZZ.resultset
  WHERE ZZEXPORT('SAMPLES',
  'SELECT TOP 5 Description, ErrorStatus, Priority from ENS.MessageHeader')=0

• For Static WHERE Conditions see my article just 6 years back.

• Using a TEMPORARY table avoids problems if running in more than 1 instance in parallel. 

  Sorry, 
  The new Editor is not so well-suited for long line replies. I dislike it.

I composed a variant that doesn't require any code in ENS.
It can all run from your ONS namespace.
All you need is a valid SQL SELECT statement
First, the utility class:

Class User.ZZ [ Abstract ]
 {

ClassMethod Export(nspace = "", query = "") As %Integer
{
	new $namespace
	zn:$l(nspace) nspace
	&SQL(DROP TABLE %ZZ.resultset)
	; default just for demo
		set:'$l(query) query="SELECT TOP 5 ssn, home_state,name from Sample.employee"

    ;
	set sql=2,
		sql(1)="CREATE GLOBAL TEMPORARY TABLE %ZZ.resultset as ",
		sql(2)=query
	set statement=##class(%SQL.Statement).%New()
	set result=statement.%ExecDirect(.statement,.sql)
	quit result.%SQLCODE
} }

a quick demo:

USER>set select="SELECT TOP 3 home_state,name,SSN from Sample.employee"
USER>w ##class(ZZ).Export("SAMPLES",select)
0
USER>:sql
SQL Command Line Shell
----------------------------------------------------
[SQL]USER>>select * from %ZZ.resultset
5.      select * from %ZZ.resultset 
| Home_State | Name | SSN |
| -- | -- | -- |
| NC | Emerson,Xavier O. | 217-28-9642 |
| CO | Malkovich,Bob V. | 226-71-5540 |
| UT | Joyce,Juanita V. | 396-77-7486 |
 
3 Rows(s) Affected
statement prepare time(s)/globals/cmds/disk: 0.0579s/39,198/181,087/0ms
 execute time(s)/globals/cmds/disk: 0.0002s/4/815/0ms
 query class: %sqlcq.USER.cls73
----------------------------------------------------------

[SQL]USER>>cos ZN "SAMPLES"
[SQL]SAMPLES>>select * from %ZZ.resultset
6.      select * from %ZZ.resultset

| Home_State | Name | SSN |
| -- | -- | -- |
| NC | Emerson,Xavier O. | 217-28-9642 |
| CO | Malkovich,Bob V. | 226-71-5540 |
| UT | Joyce,Juanita V. | 396-77-7486 |
 
3 Rows(s) Affected
statement prepare time(s)/globals/cmds/disk: 0.0552s/39,198/181,087/0ms
 execute time(s)/globals/cmds/disk: 0.0002s/4/815/0ms
 query class: %sqlcq.SAMPLES.cls92
--------------------------------------------------
[SQL]SAMPLES>>q
 
SAMPLES>

hope this helps:
The temporary table is visible from both namespaces
And the utiltiy is not tied to a specific query or table
All just runs and exists in your process.
Also no traces in the Journal 
 

I was just running it without any problem in Windows Docker Desktop
Some preparation:

• docker pull intersystemsdc/iris-community
  • 28 days old !
• set DOCKER_BUILDKIT=1
• docker compose build --no-cache

No problems with build

Start also OK