Previous Topic: CONFIG Statement

Next Topic: CREDIT Statement


CONFIGX Statement

The CONFIGX statement allows for the specification of four-character device numbers. The operation of the statement is similar to the CONFIG statement.

Use this optional statement to define your four-character peripheral device configuration to the report writer. Refer to the CONFIG/CONFIGX option of the OPTION statement. CA JARS relies on CONFIG/CONFIGX statements, if present, rather than generic device numbers.

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

Each device number must be a five-character code in the format xxxxblank

where:

xxxx

is the device number.

blank

is the last character of a device number field which must be a blank.

Only devices defined on CONFIG/CONFIGX statements are represented in your System Use reports. If the OPTION statement was coded to use only CONFIG/CONFIGX statements, rather than picking the data up from the SMF records, a warning message is printed during the input phase. The message identifies each device encountered in the accounting data that was not defined on the CONFIG/CONFIGX 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, the CONFIG/CONFIGX statements are used to screen out all devices not desired in the report.

There can be as many as 14 type/number fields used on a CONFIGX statement. The first blank field terminates the processing of the statement. All the device numbers of the same device type must be grouped together. Duplicate device type keywords are not allowed but multiple statements can be used as needed.

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

position   1         2         3         4         5                  8
  1........0.........0.........0.........0.........0........       ...0
   CONFIGX READX000C 001C WRITX000E 000F PUNCX000D
   CONFIGX TAPEX1280 1281 1282 1283 1284 1285 1286 1287
   CONFIGX DISKX1130 1131 1132 1133 1134 1135
   CONFIGX 1330 1331 1332 1333 1334 1335
   CONFIGX OTHEX500A 101F

The five statements specify that the installation has two statement readers: 000C and 001C; two line printers: 000E and 000F; one card punch: 000D; eight magnetic tape devices: 1280 through 1287; 12 direct access storage devices: 1130 through 1135 and 1330 through 1335; and two other I/O devices: 500A and 101F.

Note: The DASD numbers are continued on the next CONFIGX statement without repeating the keyword DISKX.

If you wish to drop all references to any device number in the SMF data, use the DROPX keyword on a CONFIGX statement. The format is DROPX xxxxblank, where xxxx is the device number to be eliminated from the input data. The following examples show the use of the DROPX keyword.

The following example shows how to use the DROPX keyword to eliminate the device number 1365 from the input data.

position   1         2                                         8
  1........0.........0.............                        ....0
   CONFIGX DROPX 1365

This example shows how to use the DROPX keyword to eliminate the device numbers 1131 through 11351 in the input data.

position   1         2         3         4         5                 8
  1........0.........0.........0.........0.........0........    .....0
   CONFIGX DROPX 1131 1132 1133 1134 1135

Position

Field Length

Field Name

Notes

1

1

Reserved

Not used

2-9

8

Statement Type

CONFIGX

10-79

5
.
.
.
up to 13
additional
occurrences
.
.
.

Type/Address Table

If Unit Type use xxxxx where xxxxx equals:
READX
WRITX
PUNCX
TAPEX
DISKX
OTHEX

If Unit Address use ccuu where:
ccu: device number
blank: blank

If Channel Equate use cc=nn where:
cc: primary channel
=: code as shown
nn: secondary channel

If drop, use DROPX followed by AABB , where AA and BB represent channels for which I/O device statistics are not wanted.