//This script identifies unsupported indents 
/*
Author: IBM
Comment: this script was sent to us to help identifying problems with imported non-standard indents that prevent 9.3 working properly

 

the cause of the problem is thought to be a mishandling of customised indents.
This can occur if the data originates in another application and is copied or imported into DOORS.

The only workable solution at this stage is to remove the indents, or replace them with standard DOORS indents. 
This will have to be done manually, so you have the option of how you want to edit the data. 
We do have a DXL script, which, when run on a module, will print out a list of absolute numbers for objects which contain these non-standard indents. This list can used to identify where to make the change.
In this context, a non-standard indent is one which is not measured in multiples of 360 units.

The script is limited in that it currently only works for the object text attribute, and if more than one indent is present, only the first will be detected.

Your log file highlights a module with ID 00001b27.With these 2 lines you can identify the name of the affected module. Once identified please run the attached script.
You will then need to edit these indents, save the module and then restart all DWA processes again.

Please then verify if the system memory exhausted error still occurs.


*/
Object o 
string s, sm 

int i = null
int rem

Module m = current

Regexp pattern = regexp ("\\\\li[0-9]+")
//Regexp pattern = regexp2 ("\\\\li[0-9]+") // for version 9.x

bool found

for o in m do {

		 i = null

		 s = richTextNoOle (o."Object Text")

		 if (pattern s) {

		 		 sm = s[match 0]
		 
		 		 i = intOf sm [3:] "\n"
		 		 rem = i % 360

		 		 if (rem !=0) {

		 		 		 print o."Absolute Number" "\n"
		 		 }
		 }
}

e Number" "\n"
		 		 }
		 }