You might have been able to monitor progress by running the JOBEXAM utility from another session connected to the %SYS namespace.

With %Library.Integer you can set MINVAL and MAXVAL parameters on your property:

Property Age As %Library.Integer(MAXVAL = 6, MINVAL = 2);

I think there's an easier way.

Use Studio to create a project that contains your INC file.

Save the project.

When exporting the production, use the "Studio Project Files" button and choose your project.

When the project selector dialog closes, the main export dialog shows your INC on the list of what will be exported.

Ideally the responses by Jenny Ames and [@Matt Spielman] would have been posted in the "Your Answer" area of DC rather that using the "Add new comment" link. That way  the OP, [@Conor Browne], could accept one of the answers by clicking on the grey checkmark at the top of the answer to turn it green. Doing this helps with DC housekeeping by removing the question from the "unanswered" list.

If Jenny and/or Matthew were to re-post their responses using the "Your Answer" field then Conor will be able to credit one of them with answering his question. Even them posting "See my answer in comments above" would be sufficient to give Conor somewhere to set a checkmark.

Alternatively Conor could either accept my answer (though it's not actually answering his question), or he could post an answer of his own, then accept it.

Judging by this subsequent post by [@Mike Kadow] he resolved this issue. I'm posting this answer so his question no longer reports as having no answer.

This link posted in a comment by [@Joyce Zhang] is a good resource for Mike's problem.

Mike, please set the checkmark against this answer, or any other that may appear, so as to mark the question "answered" in DC.

Looks like this functionality was moved to a routine named %GSET.

At least, in earlier versions (I checked 2008.1) the %GOF utility used %SYS.GSET but in newer ones (I checked 2017.1) it uses %GSET.

If you are working directly with globals (as your example seems to imply) you will have to iterate appropriately through your global, test the relevant value, and kill any node that matches.

Be sure that you also understand that a KILL will delete any subtree of the node you kill.

To efficiently maintain the sort of uniqueness you seem to be describing (i.e. for any Y there must be no more than one X for which $list(^myglobal(X))=Y) you will probably need to maintain a cross-reference (a.k.a. index) such as ^myglobalX("index1",Y)=X and check for the existence of a record here before saving a new record.