sx25debug Command

AIXLink/X.25 1.1 for AIX: Guide and Reference

sx25debug Command

Purpose

Checks that the X.25 microcode is functioning, and sends debug messages from the microcode.

Syntax

Description

The sx25debug command is a debugging aid that has two basic functions. If the -i flag is specified, you can enter characters at the keyboard, and this causes the microcode to be polled to make sure that it is operational. A response of "pse_gdebug: Alive " indicates that it is functioning normally.

Note: If the -i flag is specified, the sx25debug command cannot be run as a background process, since it must be able to access the tty.

The second main function is to read debug and error messages from the microcode and print them on stdout. This can aid in debugging microcode problems.

To exit sx25debug, enter Ctrl-E, or press the interrupt key (usually Ctrl-C).

Flags

-b BoardNumber	Specifies the board number to communicate with. If the -b flag is not specified, the board number defaults to 0.
-i	Specifies interactive mode (reads characters from the tty). Every time a character is read, a message is sent to the microcode on the board, which should elicit a response indicating that the microcode is running. This allows the you to poll the adapter to make sure that the microcode is operational.

Security

Access Control:

You must have root authority to run this command.

Examples

To start an interactive session, enter:
```
sx25debug -i
```
This should produce the following output:
```
Type is BoardType
```
where BoardType is either "PMA", "C2X", or "C1X". If this is the first time that the sx25debug command has been run since the board was configured, you will see:
```
cyc_main: Entering scheduler loop.
```
for a C2X or C1X board, or:
```
rticmain: Entering scheduler loop.
```
for a PMA board.
If you then hit any character on the keyboard, you should see:
```
pse_gdebug: Alive
```
This indicates that the microcode is functioning normally.
To start a "read-only" session, enter:
```
sx25debug
```
This will print out any debug messages from the microcode.
Either of these modes can have their output redirected or piped by the shell. For example, if you want to start an interactive session on board number 1 and save the output to a file, enter:
```
sx25debug -i -b 1 | tee /tmp/sx25debug.out
```

Files

/usr/bin/sx25debug

Contains the sx25debug command.

[ Previous | Next | Contents | Search ]