The major impact is the default collation for CACHETEMP/IRISTEMP.   This may affect sorting!

There is my related question Multi Language Sort  

@Vitaliy Serdtsev provided an excellent solution as reply to the problem
including a detailed example of how to cover solve the issues I found
with basic features already available in Caché since almost ever(?).

To get rid of xmlns: attribute In your SOAPservice class you may try

Paramter NAMESPACE = "";

It seems that your CSP page doesn't assign a license user.  So your user is your session ID.  3 in parallel.
Take a look to ##class(%CSP.Session).Login( . . . ) for details

The scope and the dimension of possibilities are much wider with IRIS than it was with Caché.
Very generally speaking: There is nothing in Caché that you can't do with IRIS.
The only thing you might miss eventually, are some ancient compatibility hooks back to the previous millennium. 
Also, support of some outdated operating system versions is gone

Very generally speaking: There is nothing in Caché that you can't do with IRIS.

The only thing you might miss eventually, are some ancient compatibility hooks back to the previous millennium. 

In general YES.
I did it myself with preIRIS  Caché.
Data and Tables and Views and Triggers are not demanding.
Migrating Stored Procedures could take a little bit more effort.
But the ability to transform Stored Procedures to Class Methods should allow also to solve tricky situations.

(I'm personally proud that over more than a decade I never lost a benchmark against Oracle)) 

With your service contract WRC should be able to provide you with a kit for 2015
Once restored the DB should have no problem to upgrade.

Hi Jeff;

all you have to do is to set the Stream location to a  Global in *TEMP Database.
Example:
 

Ok ... so this actually works:

ClassMethod GetHL7Msg(pId As %String) As %Stream.GlobalCharacter [ SqlName = GetMsg, SqlProc ]
{
    Set tHl7 = ##class(EnsLib.HL7.Message).%OpenId(pId,,.tSC)
    Throw:$$$ISERR(tSC) ..GetErr(-400, "HL7 Message with ID "_pId_" Not Found.")
    Set tMsg = ##class(%Stream.GlobalCharacter).%New()
           SET tMsg.%Location="^mtemp.JEFF"
    Set tSC = tHl7.OutputToLibraryStream(.tMsg)
    Do tHl7.%Close()
    If tSC Set tSC=tMsg.%Save()
    Throw:$$$ISERR(tSC) ..GetErr(-400, $system.Status.GetErrorText(tSC))
    Return tMsg."%%OID"
}

>>>>>

this would be a typical exercise to use XSLT support

but for this simple case using $FIND Function in a loop may do it as well.

set a="<Name>ABC</Name><RollNo>45</RollNo><Name>XYZ</Name><RollNo>66</RollNo><Name>xyz</Name>RollNo>89</RollNo>"
set p=1
for  {
      set f=$find(a,"<RollNo>",p) quit:'f
      set t=$find(a,"<",f-1) quit:'t  set p=t-2
      set $e(a,f,p)="**"
     }

"there is no real advantage to having a temp table unless you are worried about storage."

"That is not as simple as the Microsoft code"

Both observations are correct.
Though there is an implementation of TSQL that mentions SELECT ... INTO explicitly
But you have to declare that your context is TSQL

but this not Cache SQL anymore as initially inquired

in IRIS you have to do it in 2 steps

• CREATE GLOBAL TEMPORARY TABLE tempfemale (     Category,      CrewNumber,      MedicalCertificationDate,      Seat,      SeatbeltUsed,      Sex,      ShoulderHarnessUsed,      ToxicologyTestPerformed,      childsub ) see: https://docs.intersystems.com/irisforhealthlatest/csp/docbook/Doc.View.cls?KEY=RSQL_createtable#RSQL_createtable_temp  
• and INSERT  INTO tempfemale       SELECT       Category, CrewNumber, MedicalCertificationDate,Seat,                    SeatbeltUsed, Sex, ShoulderHarnessUsed, ToxicologyTestPerformed,                                childsub               FROM Aviation.Crew               WHERE Sex = 'F'

see:  https://docs.intersystems.com/irisforhealthlatest/csp/docbook/Doc.View.cls?KEY=RSQL_insert#RSQL_insert_select 

Further elaborating on the suggestion of @Vic Sun 

set file="c:\whateverfilename.txt"   ;according to file system and access rights
if $data(^%SYS)    ; or whatever global
open file:("WNS")
use file zwrite @$ZR  ; send all output to file
close file

you can even verify it from terminal command line and the result looks like this:

^%SYS("tercap","vt320","bin","hon")=$c(3,155)_"1m"
^%SYS("tercap","vt320","bin","ich")=$c(0,0,155,129,0,0)_"@ÿ"
^%SYS("tercap","vt320","bin","il")=$c(0,0,155,129,0,0)_"Lÿ"
^%SYS("tercap","vt320","bin","il1")=$c(2,155)_"L"
^%SYS("tercap","vt320","bin","ind")=$c(2,27)_"D"
^%SYS("tercap","vt320","bin","init")=$c(18,155)_"!p"_$c(155)_"62""p"_$c(27)_"F"_$c(27)_")0"_$c(155)_"?7h"                                                      ^%SYS("tercap","vt320","bin","poff")=$c(3,155)_"4i"
^%SYS("tercap","vt320","bin","pon")=$c(3,155)_"5i"
^%SYS("tercap","vt320","bin","ri")=$c(2,27)_"M"
^%SYS("tercap","vt320","bin","ron")=$c(3,155)_"7m"
^%SYS("tercap","vt320","bin","uon")=$c(3,155)_"4m"
^%SYS("tercap","vt320","cols")=80
^%SYS("tercap","vt320","flags")=16
^%SYS("tercap","vt320","lins")=24
^%SYS("tercap","vt320","names")="vt320|VT320|DEC-vt320"
^%SYS("tercap","vt320","src","aoff")="$c(155),""0m"""
^%SYS("tercap","vt320","src","bell")="$c(7)"
^%SYS("tercap","vt320","src","bon")="$c(155),""5m"""
^%SYS("tercap","vt320","src","bormap")="1,108,1,108,1,107,1,107,1,109,1,109,1,106,1,106,1,113,1,113,1,120,1,120,1,113,1,113,1,120,1,120,1,108,1,107,1,109,1,106,1,113,1,113,1,120,1,120,1,97,1,97,1,97,1,97,0,42,1,126,1,97"
^%SYS("tercap","vt320","src","clr")="$c(155),""H"",$c(155),""J"""
^%SYS("tercap","vt320","src","coff")="$c(155),""?25l"""

using 

$P(pData,",",78,79)

should do it 

To list a global (that's what ^%G does) it might be easier to run a FOR loop using $QUERY() function.
example in docs

"NotIn" is not part of InterSystems ObjectScript. Also not "in" . This is SQL slang
Alternative to the proposal of @Adrian Zeeman  you may try this construct:

if '($LF($LFS("A39,A40,O01,O11,O09,R01"),msgType) { . . . 

Depending on how you have built your WebAPI every request may run its own session with its own job id.
CSP has the concept of a SessionID to bypass such problem.
But it requires that you pass the Id back to the client and clean it up once done.

You may follow this philosophy using a random unused key [ $D(^SORT(key))=0 ]  instead of $J that you pass back to the client.
Cleaning it up is a good practice to avoid to much waste in your global. [ BTW. also with $JOB ]

 

according to results found by Google, this seems to be an issue of your Eclipse Setup / Config / Version (?)
and nothing specific to Atelier.

e.g https://kodlogs.com/33629/java-lang-illegalstateexception-injectionmanagerfactory-not-found

It looks to me as if the query optimizer gets confused to have INSERT and UPDATE to the SAME table in sequence.
If they both run well when separated I'd suggest calling both in sequence.
From code or performance, I see no advantage to pack them together. Rather the opposite.

quick sketch:

• open file 
• start loop
• read line
• split pieces P1,P2
• set ^global(p1,p2)=""
• done