Message Example

In the following example, the user typed ABC for Process Number, a numeric field, resulting in the message PROCESS NUMBER in the upper right corner. Pressing PF1 produces the longer message "ABC" IS INVALID...

node.name                      SELECT PROCESS                   PROCESS NUMBER
 CMD ==> O                                                                hh:mm
 "ABC" IS INVALID; MUST BE IN THE RANGE 0 - 199,999.
   CMD:   O ... OPERATOR TABLE  S ... OPERATOR TABLE/EXEC QUEUE STATUS
          P ... PRINT REPORT    D ... DISPLAY REPORT    V ... VIEW PROCESS
   QUEUE:            ==> _  (A-ALL,W-WAIT,E-EXECUTE,H-HOLD,T-TIMER)
   PROCESS NUMBERS:  ==> ______     ==> ______     ==> ______     ==> ______
   PROCESS NAMES:    ==> ________   ==> ________   ==> ________   ==> ________
   SERVER NAMES:     ==> ________   ==> ________   ==> ________   ==> ________
   STATUS:      (HO,HR,HI,HE,HC,HP,HS,RH,RA,WC,WX,WT,H,R,W)
                     ==> __         ==> __         ==> __         ==> __
   DESTINATION NODES:
                     ==> ________________          ==> ________________
                     ==> ________________          ==> ________________
   USER ID:        NODE ID:
     ==> ________________________________________________________________
                     ==> ________________
     ==> ________________________________________________________________
                     ==> ________________
   DO YOU WANT VALUES FOR THIS REQUEST TO BE CASE SENSITIVE? ==> NO

The following is an of the short text message that is displayed at the top of the screen.

No process(es) found matching the search criteria.

The long text provides a more detailed explanation of the message and can also include the system action and a suggested response. Press PF1 to see the long explanation of the error or type HELP or M on the command line and press Enter. The following figure shows a sample message.

 node.name        Connect:Direct MESSAGE DISPLAY                 hh:mm
 CMD ==>
  MSGID  ==> SVSL003I
  MODULE ==> DMVSOPEN
  Copy requested DISP=(,CATLG) to already cataloged dataset.
 The PROCESS COPY step requested a DISP=(,CATLG) on the TO
 clause of the COPY statement. The requested dataset already
 exists as a cataloged dataset.
 System Action. The PROCESS COPY step is terminated with a
                completion code of 8.
 Response: Either correct the COPY dataset or uncatalog the
           existing dataset and re-submit the PROCESS.

The Statistics Summary screen, an option of the SELECT STATISTICS command, also gives you the option of branching to the message screen associated with a failed Process. Type an M next to the Process name which failed (indicated by an *), and IBM® Connect:Direct® displays the extended message.