|
|
|
CONTROL FIELD: Data element indicating the contents of an eight-byte sort control field based at each control break.
DESCRIPTION FIELD: Data element identifying totals on summary line or a DESCRIPT header as defined through the use of DESCRIPT statements.
PROCESSING ID: Data element indicating record type:
C = CA JARS for CICS, IMS, IDMS and ADABAS Interfaces D = DOS H = History R = RJE/APPC S = MVS T = TSO and the VM and Roscoe Interfaces U = Unit record (forms) * = Budget - = Credit + = Debit
JOB NAME: Job or session name taken from the JOB statement.
PROGRAM/PHASE NAME: Program name from the PGM= parameter on the EXEC statement. Phase name from DOS record.
RUN START DATE: The date that the initiator selected the step. First step start date equals job start date.
JOB CLASS: Job input class from the JOB statement. Blank for TSO or started task. For RJE/APPC this is the APPC class.
ACCOUNTING FIELDS: The first 16 positions of accounting information taken from the JOB statement. Excludes periods and spaces.
COMPLETION/CANCEL CODE: Step completion code from SMF record. If all steps completed normally then the job record is assigned a completion code of 0000.
USER IDENTIFICATION: An eight-character field present on the SMF records which is available to users for accounting purposes. An SMF exit routine would be able to place information into this field so that all SMF records for any job would be identified. This field contains the CA Top Secret or RACF userid unless otherwise filled by the user in an SMF exit routine. This data element is not applicable for data collected under VSE.
STEP NAME: Step name taken from the name on the EXEC statement. When executing PROC, the PROC name displays as the step name.
START TIME: The time that the initiator selected the step. First step start time equals job start time.
STOP TIME: The time that the SMF type 30-4 record was moved to the SMF buffer, indicating step termination. The last step stop time is moved to the job record as job stop time.
JOB NUMBER: The JES assigned job number. At the summary line, this element displays as the total number of jobs, which does not include zero step job records.
PRIORITY LEVEL: JES job selection priority at the time the job was submitted.
PRINT FORMS ID: Forms number, based on SYSOUT class not 'B', or the specifications in the STDPUNCH statement.
PUNCH FORMS ID: Forms number, based on SYSOUT class = 'B', or the specifications in the STDPUNCH statement.
CARDS READ: Number of card image records read by the reader for each step (input by DD DATA or DD * statements in JCL).
LINES PRINTED (TOTAL): Total of standard and special lines printed.
CARDS PUNCHED: Class = B SYSOUT is considered cards punched, unless overridden by the STDPUNCH statement.
CORE USED: The amount of storage used by a job step. The value displayed at the job level is the largest of step values. The value displayed at summary levels is the largest encountered since the last control break.
CORE ALLOCATED: Partition/region size in 1K-Byte increments. For MVS, this data element contains the sum of core used from the top of the private area and core used from the bottom of the private area.
PERCENT OF UNUSED CORE: The percent of core allocated but not used for any job step. When displayed in a report, the largest value encountered is displayed at the summary levels. This data element is not applicable for data collected under DOS.
SETUP/IDLE TIME: The amount of time which a DOS partition is inactive between jobs. The difference between the stop time of one job and the start time of the succeeding job. This data element is not applicable for data collected under SMF.
ELAPSED TIME: The duration of a job or job step as the difference between the start and stop time.
CPU TIME: Actual time used by the executing job or job step in the Central Processing Unit excluding wait, interference, intervention and overhead time. For MVS users, the sum of CPU Time under TCB and CPU time under SRB.
Note: Be aware that the Option statement, cols 53-57, can modify this.
OVERHEAD TIME: Actual time spent executing instructions within the DOS Supervisor area (exclusive of those instructions executing within DOS partition boundaries) in support of the executing problem program.
WAIT TIME: Accumulation of the time the CPU was idle, either because the system was not active or was waiting for the completion of an event such as an I/O operation. VSE only.
PROCESSOR TIME: Processor utilization based on user-defined parameters entered through the RATE statement.
I/O TIME: A value, in hours, used in computing I/O charges. Calculated by dividing EXCP counts for each of the six classes of I/O devices (reader, printer, etc.) by the appropriate EXCPs per second factors from a RATE or TSORATE statement, then dividing the sum of the results by 3600 to convert to hours. Value is calculated for each step record and accumulated to the job record.
Note: The Option statement, position 52, can cause Device Connect Time as opposed to EXCPs to be collected.
TOTAL TIME: The combined Processor Time plus I/O Time.
TOTAL # OF DEVICES USED: The number of different peripheral I/O devices allocated at the job and step levels.
READER I/O USAGE: The number of EXCPs recorded for reader devices at the detail and summarization levels. Only those reader devices defined on CONFIG statements contribute to this count.
PRINTER I/O USAGE: The number of EXCPs recorded for printer devices at the detail and summarization levels. Only those printer devices defined on CONFIG statements contribute to this count.
Note: Is only present for nonspooled print.
PUNCH I/O USAGE: The number of EXCPs recorded for punch devices at the detail and summarization levels. Only those punch devices defined on CONFIG statements contribute to this count.
Note: Is only present for nonspooled punch.
UNIT RECORD I/O USAGE: The sum of reader I/O, printer I/O and punch I/O counts in MVS.
TAPE I/O USAGE: The number of EXCPs recorded for tape devices at the detail and summarization levels. Only those tape devices defined on CONFIG statements contribute to this count.
DISK I/O USAGE: Data element indicating the number of EXCPs recorded for disk devices at the detail and summarization levels. Only those disk devices defined on CONFIG statements contribute to this count.
OTHER I/O USAGE: The number of EXCPs recorded for other devices at the detail and summarization levels. Only those other devices defined on CONFIG statements contribute to this count.
TOTAL I/O USAGE: Sum of all I/O counts.
Note: *Data Elements 33 through 40 can be affected by Option statement, position 52, which could cause CA JARS to use Device Connect Time instead of EXCP count.
PERCENT OF TOTAL CHARGE WITHIN JOB CLASS: Total charge for this job or session as a percentage of the total charges for all jobs and sessions with the same job class, if it belongs to one of the seven possible job classes specified on the PRIORITY statement. Otherwise, it is the percent of the total charges for all jobs and sessions not in any of the specified job classes.
PERCENT OF TOTAL CHARGE: The total charge for a job or session as defined by rate type control statements, as a percentage of the combined total charges of all jobs.
ADJUSTED RATE: A dollar value used in calculating processor charge. Computed as the sum of the Basic Rate and (Core Factor times either Core Allocated or Core Used). Basic Rate and Core Factor are taken from a RATE or TSORATE statement.
PROCESSOR CHARGE: A component of the total charge for a job or step computed by multiplying Processor Time by Adjusted Rate. Value is calculated for each step record and accumulated to the job record. Note that value may be affected by Class and/or Priority Factors from a PRIORITY statement.
I/O CHARGE: A dollar amount computed by multiplying the calculated I/O time by the Basic I/O Rate taken from the appropriate (based on CPU ID) RATE or TSORATE statement. Note that the value may be affected by the Priority and/or Class factors taken from a PRIORITY statement. Value is calculated for each step record and accumulated to the job record.
TOTAL CHARGE: A dollar amount computed for step records as the sum of Processor and I/O Charges. Job Record Total Charge is the accumulation of Step Record Total Charges plus Setup and U/R Charges.
DISTRIBUTED CHARGE: Data element calculated when operating cost is specified on the PARMS statement and based on % of Total Charge. This is referred to as the Cost Distribution feature.
U/R CHARGE: A component of Total Charge computed as the sum of the products of unit record I/O Counts (Cards Read, Lines Printed, etc.) and the unit record factors from a RATE, TSORATE or FORMRATE statement, then dividing by 1000. Value is calculated for Job Records only.
SETUP CHARGE: A component of Total Charge computed as the product of the Tape Allocation Charge and the Tape Device Count plus the product of the Disk Allocation Charge and the Private Disk Device Count. Tape and Disk Allocation Charges are taken from a RATE or TSORATE statement. Value is computed only for job records.
STEP NUMBER: Step number (first step = 1, second step = 2, etc.). This data element reflects the number of steps when displayed at job and summary levels, which does not include zero step job records.
CPU IDENTIFICATION: A one-character code identifying the source of data collection. For SMF records, this is the first character of the four-byte System Identification field unless overridden by the Option statement, position 43. For DOS records, this is the code as placed there by the $JOBACCT Interface routine. The RATE and PRIORITY statements have these codes in order to associate the proper accounting algorithm with each input record.
PROGRAMMER NAME: Taken from the OS JOB statement parameter carried in the SMF records.
TERMINATION INDICATOR: A two-character data element indicating how a step or job terminated, as follows: 00 - normal termination; 02 - abnormal termination; 08, 10, 20, 40 - canceled by SMF exits IEFACTRT, IEFUSI, IEFUJI IEFUJV, respectively; 01 (in a step record) - step was flushed (not executed). Not applicable to VSE data.
READER START DATE: Date the reader recognized the JOB card for this job.
READER START TIME: The time the reader recognized the JOB card for this job.
READER QUEUE TIME: The amount of time a job spends in the reader queue prior to the initiation time of the first job step. When displayed in a report, this data element is averaged at the summary levels, based on the number of jobs processed in the reporting period. This data element is not applicable for data collected under VSE.
WRITER QUEUE TIME: The amount of time elapsed after the termination of a job until the last output writer record (last SYSOUT data set has been purged) is written on the SMF file.
When displayed in a report, this data element is averaged at the summary levels, based on the number of jobs processed in the reporting period. This data element is not applicable for data collected under DOS.
TURNAROUND TIME: As defined for the Report Writer, this includes the Reader Queue Time, Elapsed Time of the job, and Writer Queue Time, combined. It is the time starting with the reading of a job into the reader queue through to the time when the last output writer record is written following the purging of the last SYSOUT data set for a given job. This can be changed based on a selection on the OPTION statement.
When displayed in a report, this data element is averaged at the summary levels, based on the number of jobs processed in the reporting period. This data element is not applicable for data collected under VSE.
ELAPSED TIME: See 25.
CPU TIME: See 26.
OVERHEAD TIME: See 27.
WAIT TIME: Accumulation of time periods when the CPU is idle, for example, not executing instructions because the system is inactive or waiting for the completion of some event such as an I/O operation.
PROCESSOR TIME: See 29.
I/O TIME: See 30.
TOTAL TIME: See 31. For non-RJE records.
STORAGE INDICATOR/APPC TYPE: For non-RJE records, indicates type of storage allocated: R=real, V=virtual. For RJE records with the APPC type it signifies what types of APPC record: I=Inbound, O=Outbound, T=Transaction.
PAGE-IN COUNT: The sum of pages-in, VIO pages-in and common area pages-in from type 30 SMF records for MVS.
PAGE-OUT COUNT: The sum of page-out(s) and VIO page-out(s) from type 4, 30 or 34 SMF records for MVS. For VS1, the page-out count from the type 4 SMF record is used.
TOTAL PAGES: Total of page in and page out counts.
ELAPSED PAGING RATE: Data element indicating relative paging activity in a virtual (VS) environment at the detail and summarization levels. This value is calculated by dividing the Total Paging Count by Elapsed Time in minutes. This provides an index to the number of pages per elapsed minute recorded for a particular job, program, time period, etc.
CPU PAGING RATE: Data element indicating relative paging activity in a virtual (VS) environment at the detail and summarization levels. This value is calculated by dividing the Total Paging Count by CPU Time in seconds. This provides an index to the number of pages per CPU second recorded for a particular job, program, time period, etc.
Note: This field is influenced by the Option statement, positions 53-57.
I/O INDEX: Data element indicating I/O or CPU-boundness at the detail and summarization levels. This value is calculated by dividing the Total I/O count by CPU time in seconds. This provides an index to the number of EXCPs per CPU second for a job, program, time period, etc.
Note: This field is influenced by the Option statement, positions 52-57.
CREDIT AMOUNT: The amount to be credited to a particular account code or user/cost center based on a CREDIT statement.
DEBIT AMOUNT: The amount to be debited to a particular account/user/cost center based on a DEBIT statement.
BUDGET AMOUNT: A dollar amount specified on BUDGET statements which is accumulated to each summary level at which time data elements for percent of budget spent and amount over/under budget may be computed and displayed.
Ideally, BUDGET statements should be coded in such a way that at least one is present within every control break for a particular report. This assures that there is a nonzero budget amount at each summary level for the calculation of percent of budget spent and amount over/under budget data elements.
OVER/UNDER BUDGET: Calculated based on the budget amount specified on a BUDGET statement.
% BUDGET SPENT: Calculated based on the total charge and the budget amount specified on the BUDGET statement.
GROUP CODE #1: Blank unless specified on a GROUPC statement (grouping feature).
GROUP CODE #2: Blank unless specified on a GROUPC statement (grouping feature).
GROUP CODE #3: Blank unless specified on a GROUPC statement (grouping feature).
PARTITION-ID/RJE TYPE/TASK TYPE: For VSE data, the partition in which the job was executed. For RJE records, A=APPC, B=BSC, S=SNA. For non-RJE records, S=STC, J=JOB, T=TSU, A=APPC.
READER DURATION: The amount of time elapsed between Reader Start time and Reader Stop time as recorded by SMF. This is the actual time spent reading the job into the system.
WRITER DURATION: The amount of time elapsed between Output Processor Start time and Output Processor Stop time as recorded by SMF. This is the actual time spent purging all SYSOUT data sets for a job, inclusive of intervention time.
ELAPSED TIME - AVERAGED: Duration of jobs or job steps divided by the number of jobs or job steps (TSO session time).
CPU TIME - AVERAGED: The sum of Step CPU time under TCB and Step CPU time under SRB divided by the number of steps.
Note: This field is influenced by the Option statement, positions 53-57.
NUMBER OF READERS USED: The number of different reader devices allocated at the job and step levels. Only those reader devices defined on CONFIG statements are included in this count.
NUMBER OF PRINTERS USED: The number of different printer devices allocated at the job and step levels. Only those printer devices defined on CONFIG statements are included in this count.
NUMBER OF PUNCHES USED: The number of different punch devices allocated at the job and step levels. Only those punch devices defined on CONFIG statements are included in this count.
NUMBER OF TAPE DRIVES USED: The number of different tape devices allocated at the job and step levels. UNIT=(TAPE,DEFER): defers mounting of device until data set is opened. However, allocation of the device does occur. Thus, the number of tape mounts indicated by will not match the total number of physical tape mounts.
NUMBER OF DISKS USED: The number of different disk devices allocated at the job and step levels. Only those disk devices defined on CONFIG statements are included in this count.
NUMBER OF PRIVATE DISKS USED: The number of different disk (private) devices allocated at the job and step levels. Only those disk devices defined on CONFIG statements (as private) are included in this count.
NUMBER OF OTHERS USED: The number of different other devices allocated at the job and step levels. Only those other devices defined on CONFIG statements are included in this count.
BLANK SPACE: Used to adjust print line spacing.
INPUT DEVICE NAME/APPC LOCAL LU NAME: Logical input device name from the SMF type-26 record, or the local LU name for APPC records.
NUMBER OF SWAPS: Number of address space swap sequences, swap-out and swap-in.
SWAP PAGES-IN: Number of pages swapped in including LSQA, fixed pages, and pages active when address space was swapped in.
SWAP PAGES-OUT: Number of pages swapped out including LSQA, private area fixed pages, and private area nonfixed changed pages.
TOTAL SWAP PAGES: Sum of swap page-in(s) and swap page-out(s).
TPUTS ISSUED/APPC BYTES SENT: Number of TPUTs for a TSO session. For an APPC task, number of Bytes Sent, otherwise zero.
TGETS SATISFIED/APPC BYTES RECEIVED: Number of TGETs for a TSO session. For an APPC task, number of Bytes Received, otherwise zero.
ACTIVE TIME: Under MVS, swapped-in time plus swapped-out (but ready) time.
ACTIVE TIME: See A7.
ACTIVE TIME: See A7.
CONNECT TIME: The duration of a TSO session as the difference between the LOGON and LOGOFF time.
CONNECT TIME: See B0.
CONNECT TIME: See B0.
CONNECT CHARGE: A dollar amount computed by multiplying Connect Time by the Connect Time Rate from the appropriate (based on CPU-ID) TSORATE statement.
TSO NUMBER: TSO User Identification number from the type 26 (Job Purge) SMF Record.
JOB REQUEUED INDICATOR: A two-character code identifying jobs which meet either of the following criteria:
The first character of the code is set to 1 for a job that appears to have been restarted. The second character is set to 1 for a job that is apparently a restart of a previous job. For example, if a job was submitted, and then restarted twice, the three resultant job records would contain the codes, 1 , 11, 1, respectively.
To assist the user in identifying and reporting on these types of jobs, the Reader Start Times of each restarted job are incremented by one second. Because they are written before an occurrence of the conditions described above is detected, step account records may not contain the same values in this field as their corresponding job account record.
INPUT DEVICE ROUTE CODE: A number identifying the RJE station from which a job was submitted.
PRINT DEVICE ROUTE CODE: A number identifying the RJE station to which output for a SYSOUT dataset was directed.
ALLOCATION TIME: The difference between step-initiation time and program load time. This is the period of time used by the initiator to allocate I/O devices and main storage. Allocation time and active time (for non-MVS users) should very closely approximate step elapsed time.
ALLOCATION TIME: See B8.
ALLOCATION TIME: See B8.
RESIDENT TIME: Under MVS, swapped-in time.
RESIDENT TIME: See C1.
RESIDENT TIME: See C1.
CPU TIME (SRB): Under MVS, certain functions, such as I/O operations, are performed in support of a transaction under the control of an SRB. CPU resources used for these functions are accumulated as CPU Time under SRB.
Note: This field is influenced by the Option statement, position 53.
CPU TIME (SRB): See C4.
CPU TIME (SRB): See C4.
CPU TIME (TCB): Under MVS, when a transaction is executing instructions, it is under the control of its TCB, and its CPU utilization is accumulated as CPU time under TCB. In a non-MVS environment, this is the only component of CPU utilization that can be allocated directly to a problem program.
Note: This field is influenced by the Option statement, position 53.
CPU TIME (TCB): See C7.
C9 CPU TIME (TCB): See C7.
CPU INDEX: Under MVS, this index is defined as CPU Time under SRB * 100 / Total CPU Time. As with I/O Index, a high value implies a step/job is I/O bound while a low value implies a step/job is CPU bound.
Note: This field is influenced by the Option statement, positions 53-57.
SERVICE UNITS: Measure of service used by the MVS System Resource Manager to adjust the allocation of resources. Service units are made up of CPU, I/O, and storage components. These components are weighted by Service Definition Coefficients supplied to MVS in the Installation Performance Specification.
SERVICE RATE: Service units per second of Active Time.
PAGE SECONDS: Under MVS, main storage demand is monitored by the System Resource Manager. With each change in the number of pages held by a transaction, the number of pages previously held is multiplied by the number of milliseconds since the last change, and the result is accumulated over the life of the transaction. (This data element is carried in units of page-seconds, rather than page-milliseconds, by the Report Writer.)
PERFORMANCE GROUP NUMBER: Under MVS, each batch job step and TSO session can be assigned a different Performance Group Number. This is used by the System Resource Manager to determine the rate at which each transaction is entitled to service.
DAY OF WEEK INDICATOR: Number between 0 and 7 indicating the day of the week on which a job or step's run (start) date falls. 0 implies an invalid run date. 1 is Monday and 7 is Sunday.
DAY OF WEEK: A character field which spells out the day of the week (Monday, Tuesday, etc.) is available for display at the detail level.
GROUP CODE #4: Blank unless specified on a GROUPC statement (grouping feature).
GROUP CODE #5: Blank unless specified on a GROUPC statement (grouping feature).
GROUP CODE #6: Blank unless specified on a GROUPC statement (grouping feature).
FORMS COUNT: The number of SYSOUT table entries appended to a job level account or history record. Generally, this is the number of different forms used by a job, but may be higher if, for instance, two print datasets specifying the same Forms-ID were routed to different destinations.
SYSOUT CLASS: Available for display only when forms records are sorted on.
SYSOUT TYPE CODE: Available for display only when printing or sorting forms data. A one-byte code: 1 = standard print, 2 = special print, 3 = punch output. The allocation of the code is based on the STDFORM/STDPRINT/STDPUNCH statements.
SYSOUT INTERVENTION CODE: Under MVS, a one-byte code available for display when Forms Records are selected for printing which indicates what form of operator intervention may have occurred during the printing or punching of a SYSOUT data set. The code is interpreted as follows:
space no intervention of any type
1 continuation of an interrupted data set
2 printing or punching was restarted
4 printing or punching was interrupted
8 printing or punching was terminated
Note that under certain circumstances these codes may logically be added; for example, a code of A would indicate that a restarted data set had been terminated.
OUTPUT DEVICE NAME/APPC PARTNER LU NAME: Logical output device name available only when printing or sorting forms data; or the APPC Partner Logical Unit name for APPC-type RJE records.
LINES PRINTED (STANDARD): Number of logical records written by the writer by form number and class (includes JOBLOG and copies).
LINES PRINTED (SPECIAL): Number of special lines printed, denoted by a SYSOUT class other than A or B and a forms ID other than l.
PAGES PRINTED (STANDARD): Number of pages printed for SYSOUT = A, forms ID =STD or blank.
PAGES PRINTED (SPECIAL): Number of pages printed for SYSOUT other than A or B and forms ID other than STD or blank.
Note: *For Data Elements E5 through E8, the differentiation between STANDARD and SPECIAL can be altered by using the STDFORM/STDPRNT/STPPUNCH statements.
PAGES PRINTED (TOTAL): Total of standard and special pages printed.
NUMBER OF TAPE MOUNTS: Number of tape mounts from type 30 SMF records when available. Otherwise, this data element contains the same value as Number of Tapes.
JOB NUMBER: The JES assigned job number. At the summary line, this element displays as the total number of jobs, which does not include zero step job records. This field should be used instead of the DE ID 14, if displaying of six digit job numbers is required.
2ND ACCOUNTING FIELD: Bytes 17-32 of the accounting information from the job. Bytes 1-16 of the CA DISPATCH accounting information.
3RD ACCOUNTING FIELD: Bytes 33-48 of the accounting information from the job. Bytes 17-31 of the CA DISPATCH accounting information. Byte 16, "*" indicates CA DISPATCH zero step job, and "$" indicates an orphan type 6 zero step job.
USER FIELDS/APPC USER DATE FIELD: Three fields in the basic accounting record which are available for sorting and display that have been reserved for the use of user exit routines. The User Character field contains user data for APPC-type RJE records.
USER FIELDS: See F4.
USER FIELDS: See F4.
CONTROL BREAK COUNT: Output Data Element available for display at all summary levels. At the lowest summary level, it is the count of the number of account records from which data was accumulated. At each higher summary level, it is the count of the number of control breaks at the next lower level. The count, at each summary level, is reset to zero following a control break at that or any higher summary level.
ABSORPTION RATE: Service Units divided by seconds of Resident Time (that is, the average rate at which service units are accumulated while a task is resident). This data element is of value primarily when attempting to compare levels of service between different performance groups, or between several executions of the same job or program at different times of the day or week.
SMF AUDIT FLAG: Indicates which SMF records were used to create this print line.
I/O COUNT BY DEVICE: I/O count based on device specification on DEVADDR/DEVNMBR statement.
RJE CONNECT TIME/APPC SRB TIME: The amount of time elapsed between the successful logon of an RJE session (identified by a type 47 or 52 SMF record) and the first subsequent logoff (identified by a type 48 or 53 SMF record) for the same line; for SNA and BSC types. For APPC bytes it is the SRB Time used.
RJE TRANSMISSION COUNT/APPC BYTES SENT: EXCP count from SMF 48 or SMF 53 record. For APPC, the number of bytes sent.
RJE TIMEOUT COUNT/JES2 SNA LUSTAT/APPC EXCP COUNT: Number of timeouts from SMF 48 record. For JES2 SNA, the number of LUSTATS. For APPC, the number of EXCPs.
RJE NAK COUNT/APPC BYTES RECEIVED: Number of negative acknowledgements from SMF 48 or 53. For APPC, the number of bytes received.
RJE LINE ERROR COUNT/SNA TEMP ERRORS/APPC DEVICE CONNECT: The number of RJE line errors from the SMF 48 record. For JES3, this also includes the sum of the following: command rejects, interventions required, out checks, equipment checks, data checks, data overruns and lost data errors. For JES2 SNA it is the number of temporary errors. For APPC, the Device Connect time in 1/1000ths of a second.
RJE DATA CHECK COUNT/SNA EXCEPTION RESPONSES/APPC # CALLS: The number of line data checks taken from the SMF 48 record. For JES3 environments it contains zero. For JES2 SNA it is the number of exception responses. For APPC, it is the number of APPC calls.
RJE ACTIVE TIME/APPC TCB TIME: An estimate of the amount of time an RJE line is in the process of transmitting data to or from a remote terminal. The estimate is based on the assumption that each time out is a period of approximately three seconds duration during which there was no data transmission activity, and that the count of time outs times three seconds subtracted from the session's connect or elapsed time results in active time. For APPC records, it is the TCB time used in 1/100th of a second.
RJE INVALID LOGON COUNT/APPC # of CONVERSATIONS: A count of the number of attempts to logon a RJE line which failed because an invalid password was entered. This count is essentially the number of type 49 SMF records encountered between a logoff and the next subsequent logon of a remote line. For APPC, the number of conversations.
RJE LINE PASSWORD/APPC TP NAME: Password from RJE signon. For APPC it is the TP Name.
RJE LINE REMOTE NAME/APPC STEP NAME: Remote terminal name from RJE signon. For APPC it is the Step Name.
RJE LINE NAME/APPC JOB NAME: Remote line name from RJE signon. For APPC it is the Job Name.
RJE CHARGE/APPC CHARGE: For records sourced by the SMF 30 record (i.e., Batch Jobs, Started tasks), RJE charge contains a charge based on the RJERATE/SNARATE Statement if the input route code is set. It will contain a charge based on the APPCRATE statement if the JobID indicates the task as APPC. When associated with an RJE session record, it is a charge based on the RJERATE/SNARATE; when associated with an SMF 33 record, it contains a charge based on the APPCRATE statement.
RJE SESSION COUNT: Number of RJE sessions.
RJE CONNECTION TYPE: Value is either S - SNA or B - BSC
| Copyright © 2012 CA. All rights reserved. |
|