You can to change default file I/O from GB18030 to UTF8.

To do that, execute do ^NLS and choose:

2) Select defaults
2) I/O tables
4) File

And choose UTF8 there. After that, your I/O table should look like that:

I/O table              Current default
---------------------  --------------------
....
4) File                UTF8 (*)

After that, restart Cache and delete/reimport faulty files in Atelier

Note that this action (changing NLS defaults) can be disruptive to existing Cache applications.

If you're sure that your id bigger ids are generated later, you can only get the first id from index and after that iterate the data global directly:

set FromDateH = (+$h-1)
set id = ^TestI("StartDateIDX",FromDateH,id)
for {
    set id=$order(^TestD(id),1,dat)
    quit:id=""
    //dat=$lb("a","b","c","d","e")
}

Also you can use three-argument form of $order to iterate and get data in one command.

Finally, consider checking work-heavy system with %SYS.MONLBL to verify what lines consume more  time.

There are many ways to launch InterSystems IRIS.

If you want to launch it on AWS you can do it one of the following ways.

  1. Provision a EC2 instance with SUSE/RHEL/Ubuntu AMI and install InterSystems IRIS on Linux. Here's the guide. Quickstart.
  2. Provision a EC2 instance with SUSE/RHEL/Ubuntu AMI, install Docker and run InterSystems IRIS  in a container. Documentation. First Look.
  3. Use InterSystems Cloud Manager to provision AMI and run InterSystems IRIS. Documentation. First Look.

What to choose?

  • If you need to run a lot of or a variable number of servers choose 3.
  • If you're unfamiliar with Docker choose 1.
  • If you're familiar with Docker (or want to become familiar with it) choose 2.

It would be easier to start and finish the transaction in one method (or rather one request to a BO).

Why not send the request to BO containing a list of UPDATES to perform and BO would automatically wrap them in a transaction, returning either a success or error and the position of failed UPDATE statement? Even better send list of some struct and construct statements in BO.

While workarounds are possible (1 Job for BO + indefinite timeout + FIFO on caller part) it would probably be a bad idea.

1: How can the httprequest object be viewed in Ensemble?

You can use DEBUG=2, to see the output you need to start your BH in Debugging mode.

Another option would be to install Debugging proxy such as Fiddler and specify ProxyServer/ProxyPort settings in your BH.

Finally, you can install packer sniffer such as WireShark and see the raw packets.

These options are discussed more in detail in my series of articles Debugging Web: part1, part2.

2: How is the Adapter password set?

No need to write code for that, just set Credentials setting in your BH.