What's the best way to debug my script errors?
They're similar to compiler errors. Start with the first one and proceed
sequentially. There's a good chance many others will go away.
1. Read the description of the error in the error msg manual.
2. Whittle your testcase down to the fewest number of tags or control
words and command options which still demonstrate the problem.
Remove PROF(DSMPROF4) if you're not using GML tags or relying on
symbols set by the profile.
3. Scan the Remarks and Notes sections in the GML Starter Set Reference
manual for the tag causing the error or the Script Language Reference
for the control word in error.
4. See if the GML User's Guide or Script User's Guide has additional
information which would help pinpoint the problem.
5. For GML, check the GML User's Guide chapter on Common Problems.
6. If possible, check the value of system symbols.
For example, when you get the error about line length exceeding page
width, test the values of those system symbols to see what values
you're exceeding. Use the .TY control word to flash the values back to
your screen.
7. Use the .IT control word to monitor symbol substitution, GML processing
and execution of the control words.
8. Pull in the source from your imbed files so you can see it inline with
the other files to watch for control word interaction.
9. Pull in source from local macros if necessary.
10. Ask your IBM account team to forward your question through the IBM
support channels.
11. If all else fails, call level 1!
Last updated: 93/08/04 14:02:04