First, I would not use the input values directly in the query text, but would use Input Host Variables
Second, if it is necessary, it is more elegant to use the following syntax:

Set stmt = ##CLASS(%SQL.Statement).%New()
Set query = $$$FormatText("Select Val1, Val2 FROM Table WHERE Val1=%1",$$$quote("SomeCondition"))

Ideally these should be :
&SQL(SELECT Val1, Val2
INTO :val1, :val2
FROM Table
WHERE Val1='SomeCondition')

This is and now works:

&SQL(SELECT Val1, Val2
               INTO :val1, :val2
               FROM "Table"
               WHERE "Val1"='SomeCondition')

See more here: Evaluating XPath Expressions

Let's try to guess the return value of method t1().

Is that supposed to be hard? I immediately visually determined the result 20.

To be honest I don't really understand the point which the author wanted to convey. Maybe it's the lack of English.

In this case, the t3 method code is equivalent to the following code:

ClassMethod t3(ByRef pA, ByRef pB) [ ProcedureBlock = 1 ]
{
  set pA=4, pB=5
  set x=$increment(pA)*$increment(pB)
}

PS: by the way, absolutely nothing will change fundamentally if you replace "return" with "quit" (and "ByRef" with "Output").

Hi Ponnumani.

I would like to make a number of clarifications:

• VALUELIST = "A A- B B- O" -> VALUELIST = " A A- B B- O"
• it is necessary to consider the order of the fields in the global on the basis of Storage. For example, I have following Storage:
  

  <Data name="samplexlsconversionDefaultData">
  <Value name="1">
  <Value>%%CLASSNAME</Value>
  </Value>
  <Value name="2">
  <Value>name</Value>
  </Value>
  <Value name="3">
  <Value>DOB</Value>
  </Value>
  <Value name="4">
  <Value>address</Value>
  </Value>
  <Value name="5">
  <Value>PhoneNumber</Value>
  </Value>
  <Value name="6">
  <Value>BloodGroup</Value>
  </Value>
  </Data>

• need to add check for the presence of double quotes in strings, e.g. bla"bla
• the date format for CSV should not be in the internal Caché format, because the date 37893 to users of other system/DBMS nothing says unlike e.g. 1944-09-30.

I still prefer to use built-in tools when they are there, rather than reinventing the wheel.

Class User.samplexlsconversion Extends (%Persistent, %Populate)
{

Property name As %String;

Property DOB As %Date;

Property address As %String;

Property PhoneNumber As %Numeric;

Property BloodGroup As %String(VALUELIST = " A A- B B- O");

ClassMethod TestExport2CSV()
{
  
  d ..%KillExtent()
  d ..Populate(1000)
  
  s tmp=..%OpenId(1)
  s tmp.name=tmp.name_$c(34)
  d tmp.%Save()
  
  s tmp=..%OpenId(2)
  s tmp.name=$c(34)_tmp.name_$c(34)
  d tmp.%Save()

  s mgr = ##class(%SQL.Export.Mgr).%New()
  s mgr.FileName = "c:\Temp\test.csv"
  s mgr.ClassName = ..%ClassName(1)
  s mgr.TableName = $$$CLASSsqltablename($$$gWRK,mgr.ClassName)
  s mgr.Delimiter = ","
  s mgr.StringQuote = $c(34)
  s mgr.DateFormat = 3
  s mgr.TimeFormat = 1
  s mgr.TimeStampFormat = 1
  s mgr.NoCheck = $$$YES
  s mgr.HasHeaders = $$$YES
  
  s cols="Name:S;Address:S;PhoneNumber:N;BloodGroup:S;DOB:D"
  f i=1:1:$l(cols,";") {
    s c=$p(cols,";",i)
    d mgr.ColumnNames.Insert($p(c,":",1))
    d mgr.ColumnTypes.Insert($p(c,":",2))
  }
  
  d mgr.Export()
}
}

Hi Robert.

Exactly.

Programmatically Managing Roles:

This command can only be invoked either from a routine that is part of the CACHESYS database or if the current privileges held include Write permission for the CACHESYS database (%DB_CACHESYS:W).

Note that setting $ROLES only alters a process’s added roles, not its login roles.

There is a third way, but I specifically did not publish it.

What will the following code output?

s resptext="{""access_token"":""4SDFDSFDSF-aSDASDASD"",""expires_in"":""3300"",""refresh_token"":"""",""scope"":""sms_send"",""token_type"":""Bearer""}"

s sc = ##class(%ZEN.Auxiliary.jsonProvider).%ParseJSON(resptext,,.pObject,1)
i $$$ISOK(sc) {
  w pObject,!!,
    pObject."access_token",!,
    pObject."expires_in",!
  k arr s arr="" d pObject.%CopyToArray(.arr) zw arr
}else{
  d $system.OBJ.DisplayError(sc)
}

My result (2018.1):

USER>d ^test
1@%ZEN.proxyObject
 
4SDFDSFDSF-aSDASDASD
3300
arr("access_token")="4SDFDSFDSF-aSDASDASD"
arr("expires_in")=3300
arr("refresh_token")=""
arr("scope")="sms_send"
arr("token_type")="Bearer"

What will the following code output?

USER>k arr d pObject.%CopyToArray(.arr) zw arr

PS: "in" ≠ "expires_in"

The presence of a potential opportunity to read the documentation via "Class Reference".
For macros from *.inc this is not possible.

See:

• %SYS.LockQuery
• %SYS.ProcessQuery:VariableByPid()/VariableByJobNumber()
• %SYSTEM.Memory:VariableStats()

PS: $SYSTEM.Util.CleanDeadJobs().

Still another option:

Class dc.test Extends %Persistent
{

Property JSONData As list Of %String [ SqlListType = SUBNODE ];

ClassMethod Test()
{
  d ..%KillExtent()
  
  f l=$lb("apple","pear","plum"),$lb({"Name":"Kyle"}.%ToJSON(),{"Name":"Evgeny"}.%ToJSON()) {
    s t=..%New()
    d t.JSONData.InsertList(l)
    d t.%Save()
  }

  zw @$system.Dictionary.comMemberKeyGet($this,$$$cCLASSstorage,$$$nameDefaultStorageNameGet,$$$cSDEFdatalocation)
  
  s rs=##class(%SQL.Statement).%ExecDirect(,"select distinct json_arrayagg(JSONData %foreach(test)) from dc.test_JSONData")
  while rs.%Next() {
    s jsonStr=rs.%GetData(1),
      json=[].%FromJSON(jsonStr)

    w !,jsonStr,", %Size()=",json.%Size(),!
  }
}

}

Result:

USER>d ##class(dc.test).Test()
^dc.testD=2
^dc.testD(1)=$lb("")
^dc.testD(1,"JSONData")=3
^dc.testD(1,"JSONData",1)="apple"
^dc.testD(1,"JSONData",2)="pear"
^dc.testD(1,"JSONData",3)="plum"
^dc.testD(2)=$lb("")
^dc.testD(2,"JSONData")=2
^dc.testD(2,"JSONData",1)="{""Name"":""Kyle""}"
^dc.testD(2,"JSONData",2)="{""Name"":""Evgeny""}"
 
["apple","pear","plum"], %Size()=3
 
[{"Name":"Kyle"},{"Name":"Evgeny"}], %Size()=2

Doc:

• SqlListType
• JSON_ARRAYAGG