PROC(NUMBER_ARGUMENTS,
      FAILURE_CODE,
      MESSAGE_BUFFER_PTR,
      MESSAGE_BUFFER_LENGTH,
      TEXT_AREA_PTR,
      TEXT_AREA_LENGTH,
      NUMBER1,
      NUMBER1_LENGTH)
      OPTIONS(FETCHABLE)
      REORDER;
 /*---------------------*/
 /* LINKAGE FROM CALLER */
 /*---------------------*/
 DCL  NUMBER_ARGUMENTS        FIXED BIN(31);
 DCL  FAILURE_CODE            FIXED BIN(31);

 DCL  MESSAGE_BUFFER_PTR      PTR;                                   
 DCL  1 MESSAGE_BUFFER_STR    BASED(ADDR(MESSAGE_BUFFER_PTR)),      
        4 MESSAGE_BUFFER      CHAR(255);
 DCL  MESSAGE_BUFFER_LENGTH   FIXED BIN(31);

 DCL  TEXT_AREA_PTR           PTR;                                  
 DCL  1 TEXT_AREA_STR         BASED(ADDR(TEXT_AREA_PTR)),            
        4 TEXT_AREA           CHAR(15);                              
 DCL  TEXT_AREA_LENGTH        FIXED BIN(31);

 DCL  NUMBER1                 FIXED BIN(31);
 DCL  NUMBER1_LENGTH          FIXED BIN(31);

The first field is called TEXT and has a maximum size of 15 bytes. Data can be moved from and to it using PL/I field TEXT-AREA. If it is not a fixed-length field, then the TEXT-AREA-LENGTH must be used to determine the actual length. If the program wants the length to change, it must store the required value in field TEXT-AREA-LENGTH.
The second field is numeric, which in the Navigator is defined as NUM32. Data can be moved from and to it using field NUMBER1. It would be unusual to want to make use of field NUMBER1-LENGTH.
If the field is not nullable, the field contains a value of 4 on entry to the PL/I program.
If the NUMBER1-LENGTH field is NULL, it is set to 0. This situation might occur if the field was NULL before the program was called. If the program sets the field NULL, it also set NUMBER1-LENGTH to 0.