JES2 presents information in both single-line and multiple-line format. The format of multiple-line messages is different from that of single-line messages. A multiple-line message consists of:

1. A control line containing:
   • The message identifier
   • An indication of the information in the following data lines
   • A three-digit decimal connect identification number, which varies.
2. Two or more data lines. The number of lines varies with the amount of information displayed.

The following figure is an example of a multiple-line message.

$HASP826 NODE(1) 239
$HASP826 NODE(1) NAME=POK,STATUS=OWNNODE,
$HASP826         AUTH=(DEVICE=NO,JOB=YES,NET=NO,
$HASP826         SYSTEM=YES),TRANSMIT=BOTH,
$HASP826         RECEIVE=BOTH,HOLD=NONE,PENCRYPT=NO,
$HASP826         REST=0,COMPACT=0,LINE=0,
$HASP826         LOGMODE=,PASSWORD=(VERIFY=(NOTSET),
$HASP826         SEND=(NOTSET)),PATHMGR=YES,PRIVATE=NO,
$HASP826         SUBNET=,TRACE=NO

If JES2 is responding to a request for information about a range of devices that requires multiple lines, a multiple-line message will be issued for each device. For example, $D NODE(1-3) causes JES2 to display three multiple-line messages: one each for node 1, 2, and 3.

$HASP826 NODE(3) STATUS=(PENDING/POK)

When automating messages, it is recommended that your automation program determine how many lines are contained in the message. If there is more than one line, your automation program should process the first line as the control line of a multiple-line message. Table 1 lists the message identifiers for the messages that JES2 issues as multiple-line messages.

JES2 cannot issue some of the messages listed in single-line format.