Assessing program-to-program traffic

When a message processing program directs an output message to another program, that secondary transaction is queued. The transaction code is sometimes unique for convenience of the processing program's logic.

Otherwise, the secondary transaction is queued along with any messages from terminal origin.

You can use the two Messages—Program-to-Program reports to separately count transaction traffic. The following example illustrates the two tabulations. The column headed Destination appears above a list of transaction codes that were queued to another program. The originating program is not identified. The column headed Transaction Code appears above a list of the initial transaction codes that invoked the programs that issued the secondary transactions.

If you had program-to-program switches during conversational transaction processing, these will be included in the lists.

          MESSAGES--PROGRAM TO PROGRAM        DATE 06/05/07
 
                      TOTAL
      DESTINATION     MESSAGES
 
      ELEANOR             1
      SW1050              1
      T2741N1             1
      T2742N3             1
 
          MESSAGES--PROGRAM TO PROGRAM        DATE 06/05/07
 
      TRANSACTION     TOTAL
      CODE            MESSAGES
 
      TA10                107