There's a table at http://georgejames.com/deltanjiEditions

The free Solo edition is intended for, well, solo situations, with one developer wanting straightforward checkout/checkin source versioning for their namespaces on their local Cache / Ensemble instance.

In your context the Team or Enterprise editions are more likely to be appropriate, particularly since the comparison table shows LUTs not being supported by Solo.

Deltanji is capable of a lot more than simple code versioning. Please contact me via the George James Software website if you'd like to evaluate Team or Enterprise editions, or if the capabilities of the Deploy edition are of interest to you.

It worked for me (2017.2.2 on Windows):

C:\InterSystems\Ens172\bin>CSESSION ENS172 < c:\s\try.script

Node: TIN, Instance: ENS172

USER>zr

USER> ; Test routine created by try.script file

USER> w !,"This is written by INT routine ",$t(+0)

USER> w !," which is created from a script injected to csession."

USER>zs MyBootRoutine

USER>d ^MyBootRoutine

This is written by INT routine MyBootRoutine
 which is created from a script injected to csession.
USER>; Clean up

USER>zr  zs MyBootRoutine

USER>h

C:\InterSystems\Ens172\bin>

Maybe your indented script lines (the ones to insert into the routine) aren't starting with $C(9)

Make your script create an INT routine and run it. Example try.script below. Your lines of code either begin with the TAB character or with a label followed by TAB.

zr
    ; Test routine created by try.script file
    w !,"This is written by INT routine ",$t(+0)
    w !," which is created from a script injected to csession."
zs MyBootRoutine
d ^MyBootRoutine
; Clean up
zr  zs MyBootRoutine
h