Try this:

ClassMethod test2()
{
  set tKP = ..%New()
  set tIdentifierSerial = ##class(HS.Message.AddUpdateHubRequest).%OpenId(21986071).Identifiers
  zw tIdentifierSerial
  set tKP.IsSerial = 1
  set tKP.IsList = 1
  set tSerial = tIdentifierSerial.GetObjectNext(.tKey)
  for {
    if tKey="" {quit}
    do tKP.SerialList.InsertObject(tSerial)
    set tSerial = tIdentifierSerial.GetObjectNext(.tKey)
  }
  w tKP.%Save()
}

Your code does not take into account the numbers, so an incorrect result is given for "L33T C0d3r".

SELECT JSON_ARRAYAGG(json_obj)
  FROM (SELECT TOP 5
            JSON_OBJECT(
              'Name':name
              ,'Age':age
              ,'DOB':to_char(dob,'Day DD Month YYYY')
            ) json_obj
           FROM sample.person
       )

SELECT JSON_ARRAYAGG(json_obj)
  FROM (SELECT JSON_OBJECT(
                'Name':name
                ,'Age':age
                ,'DOB':to_char(dob,'Day DD Month YYYY')
                ) json_obj
       FROM sample.person
       )
  WHERE %VID BETWEEN 1 AND 5

Reduced your code to 137:

ClassMethod ToKeyPad(p) As %String
{
 f i=1:1:$l(p){f j=0:1:9{f l=1:1:$f($p(" 0^1^ABC2^DEF3^GHI4^JKL5^MNO6^PQRS7^TUV8^WXYZ9","^",j+1),$e($$$UPPER(p),i))-1 s r=$g(r)_j}} q r
}

Yes, most likely this is legacy code. For some reason I thought that since the %JSON package classes appeared only in IRIS, the code would also have to be new.

PS: by the way, can you compile an XData block without a name? Studio doesn't highlight the error?

For versions of Caché 5.0.x, try the following code:

#include %systemInclude

n

s list=$lb(
  "test",
  "for",
  "searching unknown strings here is a very long piece with enough characters to get a lowercase alpha as a $list marker",
  "items",
  "in",
  "aaatArGetwaaaa",
  "lists",
    $lb(
    "/subs",
    "/values",
    "nested list",
    "did you see that ""w"" before the third piece?",
    "Stuart Strickland",
    "Yaron Munz")
)

s str=$$$UPPER($$cccvt^%Wpglo(list,$$$MaxStringLength,.warn))
; or
; s str=$$$UPPER($$listDump^%Wprim(list,9))

i 'warn {
 s str=$e(str,3,$l(str)-2) ; remove << & >>
 ;s @("LIST="_str) zw LIST
 
 w !,$f(str,$$$UPPER("Targetw"))
}

Result: 162

If you end up searching for globals that use $lb(), then you might find it useful:

• $$gloFind^%Wprog(gref,string,case,.record) - for Caché 5.0.x
• ##class(%Global).Find/Get() - for new versions of Caché/IRIS

Out of curiosity, how would you override that write statement in %CSP.Lookup? Isn't that generated code which one wouldn't want to touch?

I also noticed three things from your screenshots:

1. instead of the standard program %SYS.Task.RunLegacyTask you are using a non-standard CTools.Task.Legacy. Is this how it should be?
2. you have disabled "Reschedule task after system restart?". Is this how it should be?
3. your task is scheduled for 4:00:00 under Task2, but judging by the history, it was launched at 11:52 and 11:56 under Administrator. Something doesn't add up here.

Now it's clearer, you're cleaning up own audit records.
As @Yaron Munz pointed out, it's most likely that the Task2 user does not have some rights.

For simplicity, you can login to Caché Terminal under this user in the ACB namespace and call your code:

ACB:Task2>Do ^CleanAuditLogTables(14)

I am confused by the name of your task "Clean Audit Log Tables" and the fact that for some reason it is in the ACB namespace. This is your own task?

By default, Caché already has a system task PurgeAudit in the %SYS namespace, where you can also specify the number of days (Purge Audit Log)

Hi Ashok. Can you tell in more detail what exactly is the problem of not-keeping the trailing zeros: calculations give an incorrect result, an error is generated or something else?

USER>set json = { "decimal": (12.000)} zw json
json={"decimal":12}  ; <DYNAMIC OBJECT>

USER>set n=12.000 zw n
n=12

In this case, it will be easier to temporarily dump the data into globals. Then you can access this data at any time, including through %ScrollableResultSet.

Here is a small example:

ClassMethod tt() [ Language = tsql, ReturnResultsets, SqlName = mycls, SqlProc ]
{
  drop table if exists mytemp1,mytemp2
  select name,dob,spouse into mytemp1 from Sample.Person where name like 'A%'
  select name,age,home_city,home_state into mytemp2 from Sample.Person where home_state = 'MA'
}

ClassMethod Test()
{
  d ##class(%SQL.Statement).%ExecDirect(,"call dc.mycls()")
  
  d ##class(%SQL.Statement).%ExecDirect(,"select * from mytemp1").%Display()
  d ##class(%SQL.Statement).%ExecDirect(,"select * from mytemp2").%Display()

  ; and even so
  d ##class(%SQL.Statement).%ExecDirect(,"select * from mytemp1 cross join mytemp2").%Display()
}

You are right, this is a mistake in the documentation.

Here is part of my code for IRIS 2023.2:

var connection =

new OdbcConnection(

"DRIVER={InterSystems IRIS ODBC35};SERVER=localhost;PORT=1972;DATABASE=USER;UID=_system;PWD=SYS;Unicode SQLTypes=1;Query Timeout=1");

Connection and display of the query result were successful.