Specifies the 1- to 4-character upper limit of the range of job account
numbers.
If the JTHRU= parameter is specified on this statement, it causes
a range of JES2 account numbers to correspond to a single network account
number in the JES2-to-network lookup table. Also, only two entries are created
in the appropriate lookup tables (one for either limit of the range), regardless
of range size. Ranges of this type may be used to cause the JES2 account numbers
for an entire department, for example, to be converted to a single network
account number for charging outside the local node.
This parameter
defaults to the name specified on the JACCT= parameter.
This parameter
is ignored if TYPE=NET.
Modification: Single-system
warm start.
Specifies the 1- to 8-character upper limit of the range of network
account numbers.
If the NTHRU= parameter is specified on this statement,
it causes a range of network account numbers to correspond to a single JES2
account number in the network-to-JES2 lookup table. Also, only two entries
are created in the appropriate lookup tables (one for either limit of the
range), regardless of range size. Ranges of this type may be used to cause
all of the network account numbers in use at some distant location to be converted
to a single JES2 account number for local charging.
This parameter
defaults to the name specified on the NACCT= parameter.
This parameter
is ignored if TYPE=JES2.
Modification: Single-system
warm start.
Specifies the type of account number defined by this statement.
- JES2
- This statement defines a JES2 account number.
- NET
- This statement defines a network account number.
- BOTH
- This statement defines both a JES2 and network account number. Duplicate
entries will be made in both lookup tables.
If the NETACCT statement specifies two ranges (that is, both JTHRU=
and NTHRU= are specified) then the JES2 account range will be converted to
the low end of the network account number range. Also, the network account
number range will be converted to the low end of the JES2 account number range.
Because of these conversions, it may be desirable to define ranges of this
type with two separate NETACCT statements; one statement specifying the JES2
range (TYPE=JES2) and the other specifying the network range (TYPE=NET).
If the TYPE= parameter is not specified on the NETACCT statement or is specified
as TYPE=BOTH, then duplicate entries will be made in both lookup tables. For
example, assume the following specification:
NETACCT JACCT=1234,NACCT=NET001A
In this case, if a job enters the local node with JES2 account number “1234”
and does not specify a network account number through a /*NETACCT statement,
it will be assigned network account number “NET001A” by JES2 input
service. Conversely, if a job (or SYSOUT) is received from another node which
specifies network account number “NET001A” in its NJE job header,
it will be assigned the local JES2 account number “1234”.
The entries may also be assigned on two different NETACCT statements as follows:
NETACCT JACCT=1234,NACCT=NET001A,TYPE=JES2
NETACCT JACCT=9999,NACCT=NET001A,TYPE=NET
In this example,
a job entering the local node and specifying JES2 account number “1234”
will be assigned network account number “NET001A” as in the previous
example, but a job received from the network specifying network account number “NET001A”
will be assigned JES2 account number “9999” for local processing.
For this example, if a job enters the local node specifying JES2 account number “9999”,
it will not be assigned network account number “NET001A” because there
is no entry for JES2 account number “9999” in the JES2-to-network
lookup table. Therefore, no network account number will be assigned, rather
it will remain as binary zeros.
This parameter has no default.
Modification: Single-system warm start.