It MAY be the case that there are 'unexpected' data types, in one, possibly even two of our files. Occasionally (maybe 100 times per second), a PHANTOM executed ITYPE will cause a message to be written to the errlog, stating: Tue Oct 16 07:14:53 0 <user name> Program ".ITYPE.": pc = 38, Message[040025]
I especially like the 'pc = 38' part... which translated of course means 'nonnumeric where numeric required...' We can find these because we have other tools in place to associate an error with a time of execution, but is there a(n) <easy> way to see the errant EXECUTED TCL statement as an alternative to being taunted by the error message? -- john ------- u2-users mailing list [email protected] To unsubscribe please visit http://listserver.u2ug.org/
