Debugging SLAX scripts

In this recipe, we'll take the original show-int.slax script again, but pretend that it's not working and investigate the options available when you're trying to debug a script.

Getting ready

In order to complete this recipe, you'll need access to a JUNOS router. Only a basic operating configuration is required.

How to do it...

We're going to use the original show-int.slax script from the first recipe, and modify it to add diagnostic information. So load that file and follow the directions to make modifications. The following are the steps for the recipe:

1. Decide what type of user interaction is most appropriate for the case that you are working on. Consult the following table:

Use case	Method
Immediate user feedback of runtime situation events	<output> jcs:printf(“Something happened”);
Notification of information that might have use beyond immediate invocation	jcs:syslog(“user.notice”, “Something happened”);
Developer feedback and diagnostic information	jcs:progress(“Something...