HP 3000 Manuals

##RJSTAT [ RJE User/Programmer Reference Manual ] MPE/iX 5.0 Documentation


RJE User/Programmer Reference Manual

#RJSTAT 

The #RJSTAT command provides statistical information on frequency of
subsystem command use, elapsed times and tallies of data transmitted and
received.  This information may be displayed on $STDLIST or to a
statistic file reference specified by the user.

Syntax 

     #RJSTAT [statistic file reference ]

Parameters 

You can specify the following parameter with the #RJSTAT command.

   statistic file      This specifies the output file for this operation.

        reference      Statistic file reference can be any of the following:

                       logical device number
                       "device class name"
                       actual file designator
                       *formal file designator

                            @procedurename[{(G)}
                                           {(P)}
                                           {(S)}]

                       See appendix B for statistic file characteristics.  To designate
                       the user-written procedure and the SL file containing it,
                       precede the actual name of the procedure, procedurename, with an
                       @, followed optionally by a letter in parentheses indicating the
                       SL file search order.  When G is specified, the segmented
                       library files are searched in the following order:  logon group
                       SL, SL.PUB in the logon account, SL.PUB.SYS. When P is
                       specified, the segmented library files are searched in the
                       following order:  SL.PUB in the logon account, SL.PUB.SYS. When
                       S is specified or the parameter omitted, the system segmented
                       library file, SL.PUB.SYS is searched.

                       Default:  If the statistic file reference is omitted from the
                       #RJSTAT command, the display of RJE performance information is
                       sent to $STDLIST.

                       For information on user-written procedures, refer to appendix E,
                       "User-Written Procedures." An example of the display is shown
                       below.

     ******    RJE PERFORMANCE STATISTICS         ******
     * ELAPSED REAL TIME:               10:1:321       *
     * ELAPSED CPU TIME:                0:12:17        *
     * RECORDS SENT TO HOST:            0              *
     * CHARACTERS SENT TO HOST:         0              *
     * RECORDS SENT FROM HOST:          0              *
     * CHARACTERS SENT FROM HOST:       0              *
     * RJE COMMAND FILE COMMANDS:       0              *
     * RJLINE COMMANDS:                 0              *
     * RJIN COMMANDS:                   0              *
     * RJOUT COMMANDS:                  0              *
     * RJLIST COMMANDS:                 0              *
     * RJPUNCH COMMANDS:                0              *
     * RJIO COMMANDS:                   0              *
     * RJEOD COMMANDS:                  0              *
     * RJINFO COMMANDS:                 0              *
     * RJEDEBUG COMMANDS:               0              *
     * RJSTAT COMMANDS:                 1              *
     * RJCONTINUE COMMANDS:             0              *
     * RJCMDFILE COMMANDS:              0              *
     * RJHELP COMMANDS:                 0              *
     ***************************************************

Comments 

The units of time for both real time elapsed since RJE processing began
and for CPU time is hours:minutes:milliseconds.  All other information is
a tally.

The statistic file is opened in append access mode, so that old
statistical information is retained.  If an item of RJE performance
statistical information overflows, then the word "OVERFLOW " will be
printed instead of a number.

If an error occurs using the statistic file reference, then a message
"**** STATISTIC FILE ERROR: x, yy" is issued.  A description of this
error is in Appendix A, "Interpreting Messages."



MPE/iX 5.0 Documentation