The routine SDAMA307 is using a Cache specific $Q function.
At column 20, line 161, source module /srv/vista/dewdrop/routines/SDAMA307.m
%GTM-E-RPARENMISSING, Right parenthesis expected
I wasn't sure whether to put this in refactoring services since its scheduling related.
On a side note...
- I was attempting to examine whether or not the routine was actually used vs called. Called has been well defined in the routine link above - caller and call graphs. For the sake of this discussion used defines something that explicitly causes/triggers the pieces of code to be executed. An example of use - could be a menu that a user invokes through the terminal. Wouldn't it make sense to also graph which menu options can cause portions of the routine to execute code? You could continue to extend the idea further by graphing HL7 events as well.
- I'm asking because as the codebase is refactored I don't understand how we assess whether or not the code in XYZ routine is still used and/or deprecated. Or maybe we're taking a different approach?