Previous Topic: COMMENT Statement

Next Topic: CONFIGX Statement


CONFIG Statement

Use this optional statement to define your peripheral device configuration to the report writer. CA JARS uses CONFIG statements, if present, rather than generic device addresses.

Note: The CONFIG statement does not support four-character device numbers. Use the CONFIGX statement.

On the CONFIG statement, each device must have a unit address and be associated with a unit type keyword. The valid unit type keywords are:

Each unit address must be a four-character code in the format cuublank

where:

cuu

is the device address or device number.

blank

is the last character of a unit address field which must be a blank.

Only devices defined on CONFIG statements are represented in your system use reports. If the OPTION statement was coded to use only CONFIG statements rather than picking the data up from the SMF records, a warning message is printed during the input phase identifying each device encountered in the accounting data that was not defined on the CONFIG statements. Processing continues but no utilization statistics are carried through CA JARS for these devices. This could have an adverse effect on computer billing reports charging for I/O device utilization.

If you wish to report on only a few isolated devices, such as system resident DASD units or one bank of tape drives, use CONFIG statements to screen out all devices not desired in the report.

You can use as many as 17 type/address fields on a CONFIG statement. The first blank field terminates the processing of the statement. All the unit addresses of the same unit type must be grouped together. Duplicate unit type keywords are not allowed but multiple statements can be used as needed.

The following is an example showing a typical CONFIG statement setup:

position   1         2         3         4         5                  8
  1........0.........0.........0.........0.........0........       ...0
   CONFIG  READ00C 01C WRIT00E 00F PUNC00D
   CONFIG  TAPE280 281 282 283 284 285 286 287
   CONFIG  DISK130 131 132 133 134 135
   CONFIG  330 331 332 333 334 335
   CONFIG  OTHE00A 01F

The five statements specify that the installation has two statement readers: 00C and 01C; two line printers: 00E and 00F; one card punch: 00D; eight magnetic tape units: 280 through 287; 12 direct access storage devices: 130 through 135 and 330 through 335; and two other I/O devices: 00A and 01F.

Note: The DASD addresses are continued on the next CONFIG statement without repeating the keyword DISK.

The CONFIG statements can also dynamically perform channel equates. As indicated in the previous example, DASD units 130 through 135 can be switched over to channel 3.

To consolidate utilization statistics to correspond to the real device address, all I/O information for units 330 through 335 is added to the corresponding device address on channel 1 by using the channel equate feature as follows:

position   1         2         3         4         5                  8
  1........0.........0.........0.........0.........0........       ...0
   CONFIG  DISK1=3 130 131 132 133 134 135

The four-character equate must be in the format c=nblank. Multiple equates may be used simultaneously, as needed, up to a maximum of three. Such equates pertain to device addresses following the equate(s) and are reset by a subsequent set of equates or unit type keyword.

All consecutive equates must be made to a single channel (for example, C=X C=Y C=Z) where all appropriate devices with channel X, Y, or Z are changed to channel C for reporting and billing purposes.

Equates may be changed within a unit type. For example, DASD units 130 through 135 can have secondary paths on channels 3 and 4 while units 250 through 257 have a secondary path on channel 5. All I/O information for units 330 through 337 and 430 through 437 is added to the corresponding device address on channel 1. Likewise, entries for 550 through 557 are converted to channel 2 addresses by using the channel equate feature as follows:

position   1         2         3         4         5                  8
  1........0.........0.........0.........0.........0........       ...0
   CONFIG  DISK1=3 1=4 130 131 132 133 134 135 136 137
   CONFIG  2=5 250 251 252 253 254 255 256 257

If you wish to drop all references to any device on one or more channels in the SMF data, use the DROP keyword on a CONFIG statement. The format is DROPXYZ , where all X, Y, and Z channel device addresses are eliminated from the input data. The following examples show the use of the DROP keyword.

The example below shows the use of the DROP keyword to eliminate all channel 6 device addresses from the input data. Note the three blank positions following the number 6.

position   1         2                                         8
  1........0.........0.............                        ....0
   CONFIG  DROP6

The following example shows the use of the DROP keyword to eliminate all device addresses in the input data since, in this example, the computer only uses channels 0 through 6. Note that many channels can be identified by using multiple four-character entries and terminating with a blank character.

position   1         2         3         4         5                 8
  1........0.........0.........0.........0.........0........    .....0
   CONFIG  DROP012 345 6

Position

Field Length

Field Name

Notes

1

1

Reserved

Not used

2-9

8

Statement Type

CONFIG

10-77

4
.
.
.
up to 16
additional
occurrences
.
.
.

Type/Address Table

If Unit Type use xxxx where:
xxxx:
READ for card readers
WRIT for line printers
PUNC for card punches
TAPE for tape units
DISK for disk units
OTHE for other units

If Unit Address use cuu where:
cuu: device address or device number
blank: blank

If Channel Equate use c=n where:

c: primary channel
=: code as shown
n: secondary channel
blank: blank

If drop, use DROP followed by ABC, where A, B, and C represent channels for which I/O device statistics are not wanted.

78-80

3

Reserved

Not used