COMPREHENSIVE DATA
HANDLING SYSTEM (CDHS),
EMISSIONS INVENTORY
SUBSYSTEM USERS GUIDE
APTD-1550
U.S. ENVIRONMENTAL PROTECTION AGENCY
Office of Air and Water Programs
Office of Air Quality Planning and Standards
Research Triangle Park, North Carolina 27711
-------
APTD-1550
COMPREHENSIVE DATA
HANDLING SYSTEM (CDHS),
EMISSIONS INVENTORY
SUBSYSTEM USERS GUIDE
by
International Business Machines Corporation
Federal Systems Division
18100 Frederick Pike
Gaithersburg, Maryland 20760
Contract No. 68-02-0638
EPA Project Officer: Lloyd Hedgepeth
Prepared for
ENVIRONMENTAL PROTECTION AGENCY
Office of Air and Water Programs
Office of Air Quality Planning and Standards
Research Triangle Park, North Carolina 27711
July 1973
-------
The APTD (Air Pollution Technical Data) series of reports is issued by the
Office of Air Quality Planning and Standards, Office of Air and Water Pro-
grams, Environmental Protection Agency, to report technical data of interest
to a limited number of readers. Copies of APTD reports are available free of
charge to Federal employees, current contractors and grantees, and non-
profit organizations - as supplies permit - from the Air Pollution Technical
Information Center, Environmental Protection Agency, Research Triangle
Park. North Carolina 27711 or may be obtained, for a nominal cost, from the
National Technical Information Service, 5285 Port Royal Road, Springfield,
Virginia 22151.
This report was furnished to the Environmental Protection Agency by
International Business Machines Corporation, Federal Systems Division,
Gaithersburg , Maryland, in fulfillment of Contract No. 68-02-0638. The
contents of this report are reproduced herein as received from the con-
tractor . The opinions, findings, and conclusions expressed are those
of the author and not necessarily those of the Environmental Protection
Agency
Publication No. APTD-1550
11
-------
TABLE OF CONTENTS
1.0 Introduction 1
2.0 Emissions Inventory System Overview 2
2.1 Organization 3
2.2 Communication and Data Formats 8
2.2.1 Master File 8
2.2.2 Transact ion Records 15
3.0 File Maintenance and Retrieval 46
3.1 File Maintenance 47
3.2 Retrieval 52
3.2.1 Retriever Language and Operators 53
3.2.2 Retrieval Logic 65
4.0 Output Programs 72
4.1 File List 73
4.2 Summary Report 75
4.3 NEUS Point Source 84
4.4 NEDS Area Source 86
4.5 NEDS Area Source Report 88
5.0 Data Conversion Programs 90
5.1 NEDS Point Source to EIS 91
5.2 NEDS Area Source to EIS 92
6.0 Emission Factors Table Programs 100
6.1 Emission Factors Table Generator 101
6.2 Emission Factors Transaction Generator 103
6.3 Emission Factors Insert 105
iii
-------
7.0 System Operation
7.1 Cataloged Procedures 108
7.1.1 EISANCNV - NEDS Area Source Output 109
7.1.2 EISANRPT - NEDS Area Source Report
7.1.3 EISCNVRT - NEDS Point Source to EIS
7.1.4 EISEFGEN - Emission Factors Table Generator
7.1.5 EISEFINS - Emission Factors Insert 130
7.1.6 EISEFUPD - Emission Factors Transaction Generator ..
7.1.7 EISFUPDT - File Maintenance
7.1.8 EISNACNV - NEDS Area Source to EIS 1A9
7.1.9 EISNCONV - NEDS Point Source Output 154
7.1.10 EISPREPT - File List Output 15g
7.1.11 EISRETVR - Retrieval 164
7.1.12 EISSREPT - Summary Report Output 173
7.2 Use of Cataloged Procedures 180
Appendix 183
iv
-------
FIGURES
2.1-1 EIS System Flow 5
2.2.1-1 EIS Master Record Structure 9
2.2.1-2 EIS Master Record Format 10
2.2.2-1 EIS Transaction Cards 16
4.1-1 File List Data Flow and Deck 74
4.2-1 Permanent Summary Report Generation 81
4.2-2 Permanent Summary Report Execution 82
4.2-3 Temporary Summary Report Generation and Execution 83
4.3-1 NEDS Point Source Output Data Flow and Deck 85
4.4-1 NEDS Area Source Data Flow and Deck Setup 87
4.5-1 NEDS Area Source Report Data Flow and Deck 89
7.1.1-1 EISANCNV Data Flow 110
7.1.1-2 EISANCNV DDNAMES Ill
7.1.1-3 EISANCNV Substitutable Parameter 112
7.1.1-4 EISANCNV Procedure 113
7.1.2-1 EISANRPT Data Flow 115
7.1.2-2 EISANRPT DDNAMES 116
7.1.2-3 EISANRPT Substitutable Parameters 117
7.1.2-4 EISANRPT Procedure 118
7.1.3-1 EISCNVRT Data Flow 120
7.1.3-2 EISCNVRT DDNAMES 121
7.1.3-3 EISCNVRT Substitutable Parameters 122
7.1.3-4 EISCNVRT Procedure 123
-------
7.1.4-1 EISEFGEN Data Flow 125
7.1.4-2 EISEFGEN DDNAMES 126
7.1.4-3 EISEFGEN Substitutable Parameters 127
7.1.4-4 EISEFGEN Procedure 128
7.1.5-1 EISEFINS Data Flow 131
7.1.5-2 EISEFINS DDNAMES 132
7.1.5-3 EISEFINS Substitutable Parameters 133
7.1.5-4 EISEFINS Procedure 135
7.1.6-1 EISEFUPD Data Flow 138
7.1.6-2 EISEFUPD DDNAMES 139
7.1.6-3 EISEFUPD Substitutable Parameters 140
7.1.6-4 EISEFUPD Procedure 141
7.1.7-1 EISFUPDT Data Flow 144
7.1.7-2 EISFUPDT DDNAMES 145
7.1.7-3 EISFUPDT Substitutable Parameters 146
7.1.7-4 EISFUPDT Procedure 147
7.1.8-1 EISNACNV Data Flow 150
7.1.8-2 EISNACNV DDNAMES 151
7.1.8-3 EISNACNV Substitutable Parameters 152
7.1.8-4 EISNACNV Procedure 153
7.1.9-1 EISNCONV Data Flow 155
7.1.9-2 EISNCONV Data Flow 156
7.1.9-3 EISNCONV Substitutable Parameters 157
7.1.9-4 EISNCONV Procedure 158
7.1.10-1 EISPREPT Data Flow 160
vi
-------
7.1.10-2 EISPREPT DDNAMES 161
7.1.10-3 EISPREPT Substitutable Parameters 162
7.1.10-4 EISPREPT Procedure 163
7.1.11-1 EISRETVR Data Flow 166
7.1.11-2 EISRETVR DDNAMES 167
7.1.11-3 EISRETVR Substitutable Parameters 168
7.1.11-4 EISRETVR Procedure 169
7.1.12-1 EISSREPT Data Flow 174
7.1.12-2 EISSREPT DDNAMES 175
7.1.12-3 EISSREPT Substitutable Parameters 176
7.1.12-4 EISSREPT Procedure 177
7.2-1 Sample EIS Job Stream 182
vii
-------
TABLES
3.2-1 Retrieval Names 57
3.2-2 Repeating Retrieval Names 59
5.2-1 Area Source Categories 95
5.2-2 EIS Area Source Records 97
viii
-------
1.0 INTRODUCTION
This document is intended to provide instruction in the use of the Emission
Inventory Subsystem (EIS) of the Comprehensive Data Handling System (CDHS).
With this goal in mind the document is organized in the following manner:
o SECTION 2.0 - Contains an overview of the EIS system, a brief functional
description of each component program comprising the system and a de-
tailed discussion of the system master file and the general transaction
cards required to build the master file.
o SECTIONS 3.0 through 6.0 - Contain detailed functional descriptions of
each program in the EIS system, along with complete Instructions on
the use of all program functions. The sections are organized as
follows:
SECTION 3.0 - File Maintenance and Retrieval
SECTION 4.0 - Output Programs
SECTION 5.0 - Data Conversion Programs
SECTION 6.0 - Emission Factors Table Programs
o SECTION 7.0 - Contains complete instructions, with examples, on how to
run the EIS system on the computer.
If a more complete knowledge of the logic of the EIS system is desired it
is suggested that the user consult the EIS Program Documentation Manual.
-------
2.0 EMISSIONS INVENTORY SUBSYSTEM (EIS) OVERVIEW
When dealing with atmospheric pollution, it is necessary to amass, catalog,
sort, evaluate, and perform calculations upon large volumes of data. The
Emissions Inventory Subsystem of the Comprehensive Data Handling System
provides a systematic method for collecting this data in a data base that
will provide a central source for the information needed to help control
air pollution. If the system is to be helpful it must maintain the data
base, keeping the information current, and provide a means for access to
the information, presenting it in a usable form.
The Emissions Inventory Subsystem provides the ability to create and
maintain, and to retrieve and print data from the data base. The creation
and maintenance is accomplished with the File Maintenance program. This
program allows the user to keep his data base Information current and useful.
Access to the data base information is provided by the Retrieval program
set. These programs provide the means of extracting desired information
from the data base. The output print programs are then used to convert
the extracted information to a form readable by the user. These three
functions form the basic system.
In addition to the basic system, several preprocessor and postprocessor
programs are provided which perform functions necessary to make this
system compatible with existing systems. Other programs provide services
which help make the maintenance process automatic. All of the system
programs are described in detail in the following sections.
-------
2.1 ORGANIZATION
The Emission Inventory Subsystem of CDHS is organized around two main
programs, File Maintenance and Retrieval. There are ten other programs
in the system that perform service functions. The interface for the pro-
grams that feed the File Maintenance program is the EIS transaction card.
The Master File serves as the interface for the rest of the programs.
The EIS components are:
o File Maintenance - This program is used to create and maintain
the Master File.
o Retrieval Language Processor - This program generates the retrieval
program.
o Retrieval - This program is used to extract information from the
Master File.
o File List - This program provides a detailed listing of the Master
File.
o Summary Report Output - This program will produce a listing of
emission totals for selected control breaks.
o NEDS Point Source Output - This program converts the Master File to
NEDS Point Source card formats.
o NEDS Area Source Output - This program converts the Master File area
records to NEDS Area Source card formats.
o NEDS Area Source Report - This program prints a formatted listing
of NEDS Area Source cards.
-------
o NEDS Point Source Conversion - This program converts NEDS Point
Source cards to EIS transaction cards.
o NEDS Area Source Conversion - This program converts NEDS Area
Source cards to EIS transaction cards.
o Emission Factor Table Generator - This program is used to generate
the emission factors table.
o Emission Factor Insertion - This program inserts the emission
factors into the (23 card) EIS transactions.
o Emission Factor Transaction Generator - This program generates
transaction cards to update emission factors in the Master File.
Figure 2.1-1 illustrates the flow of the EIS system.
-------
I^NEDS Area
I Source
Keypunch EIS
Input Load
Sheet
1
r
| EIS
Transactions
EIS System Flow
Figure 2.1-1
-------
NEDS Point
Source Out
Program
T
[NEDS Point
Source Cards
Retrieval
Control Cards
NEDS Area
Source Out
Program
Detail List
of Master
File
EIS System Flow
Figure 2.1-1 (cont.)
-------
Master
Update
Control
rarriR
h>
w
Emission
Factor Update
Program
I
EIS
Transactions
File
Maintenance
Program
Master
File
EIS System Flow
Figure 2.1-1 (cont.)
-------
2.2
COMMUNICATION AND DATA FORMATS
2.2.1
MASTER FILE
The EIS master file is a three level hierarchical file with three different
segment types. The highest, or master record level segment is called the
PLANT
POINT SOURCE
MACHINE PROCESS
plant segment. There is no limit to the number of master records allowed
on an EIS master file. Subordinate to each master record (plant segment)
may be up to 99 point source segments, each describing a different source
of pollution (air stack) within the plant described by the plant segment.
And subordinate to each point source segment are 1 to 6 machine process
segments, each describing a different polluting process or machine feeding
into the given point source. Figure 2.2.1-1 illustrates the hierarchical
structure of an EIS master record.
The format of each segment type on the master file is illustrated in
Figure 2.2.1-2. Each field illustrated relates directly to a field on
one of the input transaction cards.
-------
PLANT SEGMENT
Point Source 1
Machine Process 1
Machine Process 2
Type 0 Segment
Type 1 Segment
Type 2 Segment
Machine Process 6
Point Source 2
Machine Process 1
Machine Process 2
Type 1 Segment
Type 2 Segment
Machine
Point
Process
Source
3
6
Type 1 Segment
o unlimited plant segments (type 0)
o up to 99 point source
segments (type 1 subordinate to
each plant segment.
o up to 6 machine process segments
(type 2) subordinate to each point
source
EIS MASTER RJECORD STRUCTURE
Figure 2.2.1-1
9
-------
Fixed (Plant) Segment (Segment 0)
Position
Format
1 -
3 -
7 -
10 -
1A -
19 -
22 -
25 -
27 -
39 -
A3 -
A6 -
61 -
71 -
81 -
129 -
133 -
139 -
2
6
9
13
18
21
2A
26
38
A2
AA
A5
60
70
80
128
132
138
186
XX
xxxx
XXX
xxxx
xxxxx
XXX
XXX
XX
x-x
xxxx
XX
A
A-A
x-x
x-x
x-x
xxxx
XXXXX. X
x-x
*
*
*
*
*
*
*
*
*
*
Symbol
Numeric
Numeric
Numeric
Numeric
* Numeric
* Numeric
* Alphanumeric
* Alphanumeric
* Alphanumeric
Numeric
Numeric
Alphabetic
Alphabetic
Alphanumeric
* Alphanumeric
Alphanumeric
* Numeric
* Numeric
* Alphanumeric
Description
State Code
County Code
AQCR Number
Plant Id
Date of Segment
Segment Id
User Control Region
Local Control
User Plant Id
City
UTM Zone
Ownership
Contact
Telephone
Principal Product
Name and Address
Number of Employees
Property Area
Mailing Address
E1S Master Record Format
Figure 2.2.1-2
10
-------
Point Source Segment (Segment 1)
Position
1 -
3 -
7 -
10 -
14 -
20 -
22 -
24 -
27 -
31 -
33 -
37 -
42 -
48 -
55 -
63 -
68 -
73 -
76 -
80 -
83 -
2
6
9
13
18
19
21
23
26
30
32
36
41
47
54
62
67
72
75
79
82
86
Format
XX
xxxx
XXX
xxxx
xxxxx
X
XX
XX
XXX
xxxx
XX
XXX. X
xxxx.x
x-x
x-x
x-x
xxxxx
xxxxx
XX. X
xxxx
XX. X
xxxx
Symbol
Numeric
Numeric
Numeric
Numeric
* Numeric
* Numeric
Numeric
Numeric
* Alphanumeric
Numeric
Numeric
Numeric
Numeric
* Numeric
* Numeric
Numeric
Numeric
Numeric
Numeric
Numeric
Numeric
Numeric
Description
State Code
Count y Code
AQCiR Number
Plant Id
Date of Segment
Segment Id
Segment Id Sequence
Point Id (NEDS)
Point Id (User)
SIC Code
IP? Code
UTM Horizontal Coordinates
UTM Vertical Coordinates
Latitude
Longitude
Annual Throughput
Normal Operating
Boiler Design Capacity
Space Heat
Stack Height
Stack Diameter
Stack Temperature
EIS Master Record Format
Figure 2.2.1-2 (Continued)
11
-------
Position
87
94
99
103
108
112
119
131
133
137
145
148
151
154
161
168
- 93
- 98
- 102
- 106
107
- Ill
- 117
118
- 130
- 132
- 137
- 144
- 147
- 150
- 153
- 160
- 167
- 174
175
176
177
Format
x-x
xxxxx
xxxx
xxxx
X
xxxx
x-x
X
x-x
XX
xxxxx
XXXXX. XX
XXX
xxx
XX. X
x-x
x-x
x-x
X
X
X
Symbol
Numeric
* Numeric
Numeric
Numeric
Numeric
Numeric
Numeric
Numeric
Numeric
Numeric
* Numeric
* Numeric
Numeric
Numeric
Numeric
Numeric
* Numeric
Numeric
* Numeric
Numeric
* Numeric
Description
Exhaust Flow Rate
Velocity
Plume-Height
Points with Common
Stack
Compliance Status
Compliance Schedule
Compliance Update
ECAP
Control Regulations
2
Number of Pollutants
Pollutant Id
Control Equipment Cost
Primary Control Equipment
Secondary Control Equipment
Estimated Control Efficiency
Emissions Estimate
Emissions Measured
Allowable Emissions
Emission Units
Estimation Method
Test Method
Note: Positions 133 - 177 may be repeated up to 15 times to allow
for 16 pollutants from a single source. The Number of
Pollutants field determines the number of repetitions.
E1S Master Record Format
Figure 2.2.1-2 (Continued)
12
-------
Machine Process Segment (Segment 2)
Position
1 -
3 -
7 -
10 -
1A -
20 -
22 -
24 -
32 -
38 -
45 -
52 -
55 -
58 -
65 -
91 -
93 -
2
6
9
13
18
19
21
23
31
36
37
44
51
54
57
62
63
64
89
90
92
97
Format
XX
xxxx
XXX
xxxx
xxxxx
X
XX
XX
x-x
xxxxx
X
x-x
XXXX. XXX
x.xx
XX. X
xxxxx
X
A
x-x
X
XX
xxxxx
Symbol
Numeric
Numeric
Numeric
Numeric
* Numeric
* Numeric
Numeric
* Numeric
Numeric
* Numeric
* Numeric
Numeric
Numeric
Numeric
Numeric
Numeric
Numeric
Alphabetic
Alphanumer
* Alphabetic
* Numeric
* Numeric
Description
State Code
County Code
AQCR Number
Plant Id
Date of Segment
Segment Id
Segment 1 Id
Segment 2 Id
SCC Code
BEC Code
Fuel Units
Fuel, Process, Solid Waste
Maximum Design
Sulfur Content
Ash Content
Heat Content
Confidentiality of Data
Source Code
Source Description
Emission Factor Source
f
Number of Emission Factors'
Pollutant Id
EIS Master Record Format
Figure 2.2.1-2 (Continued)
13
-------
Position Format Symbol Description
98 - 106 xxxxxx.xxx * Numeric Emission Factor
107 A * Alphabetic Ash/Sulfur Code
108 x * Numeric Emission Factor Units
Note: Positions 93-108 may be repeated up to 15 times to allow
for 16 emission factors per process. The number of
Emission Factors field determines the number of repeti-
tions.
* Not part of NEDS point source file.
1 Only year portion of date obtained from NEDS point source
file. Remainder of field filled with zeroes.
2 Determined by File Maintenance program.
EIS Master Record Format
Figure 2.2.1-2 (Continued)
14
-------
2.2.2 TRANSACTION RECORDS
The master file is constructed from the information contained on the EIS
input transaction cards. There are three classes (or types) of cards: a
zero card, a one card and a two card. The zero card contains general
identification for the plant or source; the one card contains information
relative to specific emission points within a source; the two card contains
fuel and process information. The following paragraphs explain the contents
of each field on the transaction cards. Figure 2.2.2-1 illustrates the format
of the cards. The same formats are used to enter both point source data and
area source data. However, the meanings of some fields will be changed when
area source data is to be entered.
15
-------
Card Columns 1-18 of all Cards (Key)
CC
1-2
3-6
7-9
10 - 13
14 - 18
Format
xx
xxxx
XXX
xxxx
xxxxx
Symbol
Numeric Code
Numeric Code
Numeric Code
Numeric Code
Numeric
Description
State Code
County Code
AQCR Number
Plant Id
Date of Record
Card 01 - Plant Identification
CC
19 -
22 -
24 -
36 -
40 -
43 -
58 -
68 -
78 -
21
23
35
39
41
42
57
67
77
79
80
Format
XXX
XX
x-x
xxxx
XX
A
A-A
x-x
x-x
XX
X
Symbol
Alphanumeric Code
Alphanumeric Code
Alphanumeric Code
Numeric Code
Numeric Code
Alphabetic Code
Alphabetic
Alphanumeric
Alphanumeric
Numeric
Alphabetic Code
Description
Control Region
Local Control
Plant Id
City
UTM ZONE
Ownership
Contact
Telephone
Principal Product
Card Number
Transaction Code
EIS TRANSACTION CARDS
Figure 2.2.2-1
16
-------
Card 02 - Plant Identification
CC
19 -
67 -
71 -
78 -
66
70
76
77
79
80
Format
x-x
x-x
xxxxx.x
XX
X
Symbol
Alphanumeric
Numeric
Numeric
Numeric
Alphabetic Code
Description
Name and Address
Number of Employees
Property Area
Not Used
Card Number
Transaction Code
Card 03 - Plant Identification
CC
19 - 66
67 - 77
78 - 79
80
Format
x-x
XX
X
Symbol
Alphanumeric
Numeric
Alphabetic Code
Description
Mailing Address
Not Used
Card Number
Transaction Code
EIS TRANSACTION CARDS
Figure 2.2.2-1 (Cont.)
17
-------
Card 11 - Point Source Parameters
cc
19 -
21 -
23 -
26 -
30 -
32 -
36 -
41 -
47 -
54 -
62 -
67 -
72 -
75 -
78 -
20
22
25
29
31
35
40
46
53
61
66
71
74
77
79
80
Format
XX
XX
XXX
xxxx
XX
XXX. X
xxxx.x
x-x
x-x
x-x
xxxxx
xxxxx
XX. X
XX
X
Symbol
Numeric
Numeric
Alphanumeric
Numeric
Numeric
Numeric
Numeric
Numeric
Numeric
Numeric
Numeric
Numeric
Numeric
Numeric
Alphabetic Code
Description
Segment ID
Point Id (NEDS)
Point Id (Local)
SIC Code
IPP Code
UTM Horizontal Coordinates
UTM Vertical Coordinates
Latitude
Longitude
% Annual Throughput
Normal Operating
Boiler Design Capacity
Space Heat %
Not Used
Card Number
Transaction Code
EIS TRANSACTION CARDS
Figure 2.2.2-1 (cont.)
18
-------
Card 12 - Point Source Parameters
cc
19 -
21 -
25 -
28 -
32 -
39 -
44 -
48 -
53 -
57 -
64 -
76 -
78 -
20
24
27
31
38
43
47
51
52
56
62
63
75
77
79
80
Format
XX
xxxx
XX. X
xxxx
x-x
xxxxx
xxxx
xxxx
X
xxxx
xxxxxx
X
x-x
XX
X
Symbol
Numeric
Numeric
Numeric
Numeric
Numeric
Numeric
Numeric
Numeric
Numeric
Numeric
Numeric
Numeric
Numeric
Numeric
Alphabe
Description
Segment ID
Stack Height
Stack Equivalent Diameter
Stack Temperature
Exhaust Flow Rate
Velocity
Plume Height
Points with Common Stack
Compliance Status
Compliance Schedule
Compliance Update
ECAP
Control Regulations
Not Used
Card Number
Transaction Code
EIS TRANSACTION CARDS
Figure 2.2.2-1 (cent.)
19
-------
Card 13 - Point Source Parameters
cc
19 -
21 -
26 -
33 -
36 -
39 -
42 -
49 -
56 -
66 -
78 -
20
25
32
35
38
41
48
55
62
63
64
65
77
79
80
Format
XX
xxxxx
xxxxxx.xx
XXX
XXX
XX. X
xxxxxxxx
xxxxxxxx
xxxxxxxx
X
X
X
XX
X
Symbol
Numeric
Numeric
Numeric
Numeric
Numeric
Numeric
Numeric
Numeric
Numeric
Numeric
Numeric
Numeric
Numeric
Alphabetic
Description
Segment ID
Pollutant ID
Control Equipment Cost
Primary Control Equipment
Secondary Control Equipment
Estimated Control Efficiency
Emissions Estimate
Emissions Measured
Allowable Emissions
Emission Units
Estimation Method
Test Method
Not Used
Card Number
Transaction Code
EIS TRANSACTION CARDS
Figure 2.2.2-1 (cont.)
20
-------
Card 21 - Fuel, Process Parameters
cc
19 -
21 -
23 -
31 -
37 -
44 -
51 -
54 -
57 -
62 -
78 -
20
22
30
35
36
43
50
53
56
61
77
79
80
Format
XX
XX
x-x
xxxxx
X
xxxxxxx
XXXXX. XXX
x.xx
XX. X
xxxxx
XX
X
Symbol
Numeric
Numeric
Numeric Code
Numeric Code
Numeric Code
Numeric
Numeric
Numeric
Numeric
Numeric
Numeric
Alphabetic Code
Description
Segment 1 ID
Segment 2 ID
SCC Code
BEC Code
Fuel Units
Fuel, Process, Solid Waste
Maximum Design
Sulfer Content
Ash Content
Heat Content
Not Used
Card Number
Transaction Code
EIS TRANSACTION CARDS
Figure 2.2.2-1 (cont.
21
-------
Card 22 - Fuel. Process Parameters
cc
19 -
21 -
25 -
51 -
78 -
20
22
23
24
49
50
77
79
80
Format
XX
XX
X
X
x-x
X
XX
X
Symbol
Numeric
Numeric
Numeric
Alphabetic
Alphanumeric
Alphabetic
Numeric
Alphabetic
Code
Description
Segment 1 ID
Segment 2 ID
Confidentiality of data
Source Code
Source Description
Emission Factor Source
Not Used
Card Number
Transaction Code
EIS TRANSACTION CARDS
Figure 2.2.2-1 (cent.)
22
-------
Card 23 - Fuel, Process Parameters
CC
19 - 20
21 - 22
23 - 27
28 - 36
37
38
39 - 54
55 - 70
71 - 77
78 - 79
80
Format
xx
XX
xxxxx
XXXXXXX.XXX
Symbol
Numeric
Numeric
Numeric
Numeric
Alphabetic Code
Numeric Code
xx
Numeric
Alphabetic Code
Description
Segment 1 ID
Segment 2 ID
Pollutant ID Code
Emission Factor
Ash/Sulfur Code
Emission Factor Units
Repeat CC 23 - 38
Repeat CC 23 - 38
Not Used
Card Number
Transaction Code
EIS TRANSACTION CARDS
Figure 2.2.2-1 (cont.)
23
-------
Card Columns 1-18 of all cards;
1. State Code: State identification number as defined by the
SAROAD air quality numbering system.
2. County Code: Codes to be used are listed in the SAROAD Station
Coding Manual for Aerometric Sampling Networks, Publication No.
APTD-0907 of the Environmental Protection Agency.
3. AQCR Number: Number for the Air Quality Control Region in
which the Plant is located.
4. Plant ID: This field identifies each source in a county. The
numbering system is sequential, starting with the number one
and continuing until all facilities containing point sources
that are located in a given county are assigned a number.
5. Date of Record: The Julian date for the data recorded on
the card. The format for this field is YYDDD.
24
-------
Card 01
1. Control Region: A user defined field to identify state or
county control areas.
2. Local Control: A user defined field to identify plants that
are physically in one control region but have control responsi-
bility in another region.
3. Plant ID: A user defined field to be used if the local identi-
fication conventions differ from NEDS.
4. City: The four-digit SAROAD code number corresponding to the
city in which the source is located. There are a few cities
in the United States that are not considered to be inside any
county but are considered independent entities. In such cases,
enter the city code in both the City and County Code fields.
5. UTM Zone: The zone number must be known in order to locate
the point source via the UTM coordinate system; this number is
found on all USGS maps showing UTM coordinates. Although most
states are within a single UTM zone, a few states and counties
are in two UTM zones. For this reason a UTM zone number is
required for each record.
25
-------
6. Ownership: A single alphabetic character ownership code.
The code should be selected from the following list:
Symbol Ownership
P Private
L Local Government
S State Government
F Federal Government
U Utility
7. Contact: The last name of the person responsible for pollution
control activity at the source. If the responsible individual
is not identifiable, then record a descriptive and appropriate
title.
8. Telephone: The area code and telephone number of the person
to be contacted should be entered in this field.
9. Principal Product: A brief description of the principal product
produced by this plant.
10. Card Number: 01
11. Transaction Code: The transaction codes are:
A - Add
C - Change
D - Delete.
26
-------
Card 02
1. Name and Address: Provide a descriptive name for the
facility and a usable mailing address. Use common abbre-
viations as much as possible. The address should include a
street number, city and a zip code. The zip code should appear
in the last five positions of the field.
2. Number of Employees: Record the number of persons actually
working at this location.
3. Property Area: The area, to the nearest tenth acre, of the
land occupied by the facility.
4. Card Number: 02
5. Transaction Code: The transaction codes are:
A - Add
C - Change
D - Delete.
27
-------
Card 03
1. Mailing Address: The address of the person to contact if it
is different than the establishment name and address.
2. Card Number: 03.
3. Transaction Code: The transaction codes are:
A - Add
C - Change
D - Delete.
28
-------
Card 11
1. Segment ID: Each point source set (11, 12, and a 13 card)
creates a point source segment in the master file. Each
point source segment under the same facility segment must
have a unique segment ID number. This number must also be
used to reference a particular segment when making a change
or deleting a segment.
2. Point ID (NEDS): This is a sequential number designated
for each pollutant discharge point within the facility.
3. Point ID (Local): This is a field for a user defined point
source identification when the NEDS Point Id is not sufficient
to show local control.
A. SIC code: This information is necessary to use the source
data for modeling air quality. Enter the appropriate
Standard Industrial Classification code.
5. IPP code: This column should be completed with the standard
process code.
29
-------
6. UTM Horizontal and Vertical Coordinates: The UTM coordinate
system is another means of identifying the location of the
point source. Coordinates are obtained from USGS maps or their
equivalent with scales less than 1:62,500. All spaces in these
columns must be filled in with numbers and zeros. Accuracy to
0.1 kilometer accuracy is desired.
7. Latitude and Longitude: This is an alternate means of identifying
the location of the point source. Coordinates may be obtained from
USGS maps or their equivalent.
8. % Annual Throughput: The annual production, consumption, throughput,
or other valid number representing the operating of the source should
be proportionally divided into the four 3-month categories listed
below. The wieghted portion of production occurring in each category
is reported as a percentage of total annual throughput. The field is
divided into four equal subfields of two numbers each. The first two
positions are for December through February. The next two are for
March through May. The next two are for June through August. The
last two are for September through November.
9. Normal Operating: The hours per day, days per week, and weeks per
year that the source operates under normal and usual conditions
should be entered here.
30
-------
10. Boiler Design Capacity: Numerical values in this field should
be entered if the boiler burns fuel to heat water or steam,
or if it is normally sold according to the heating capacity
(BTU per hour). Units are in millions of BTU per hour based
on the maximum capacity or design of the boiler.
11. Space Heat %: An estimate of the percent of total fuel used
for space heating at the plant should be entered here. If no
fuel is used for space heating, enter zeros in this field.
12. Card Number: 11
13. Transaction Code: The transaction codes are:
A - Add
C - Change
D - Delete
31
-------
Card 12
1. Segment ID: Enter the same number as In the Segment ID
of the 11 card.
2. Stack Height: If the exact location of the discharge of
pollutants is well defined there will be a stack or some
other enclosed, constrained, or physically-bounded area where
pollutants are emitted. In such instances, the stack height
is the vertical distance between the point of emission and
ground level. If no stack can be identified or there is a
changing locus of emissions within the facility then complete
only the Plume Height field and leave the rest of the stack
data blank.
3. Stack Equivalent Diameter: The stack diameter is the inside
diameter of a round gas exit at the point of emission; for
non-round exits, it is an equivalent diameter calculated from
the cross-sectional area at point of discharge. Using a
measured or estimated cross-sectional area, the equivalent
diameter (De) is calculated as follows:
De = 1.128 \/A~
where A is in square feet.
32
-------
4. Stack Temperature: The temperature of the exhaust stream at the
stack exit should be reported in degrees Fahrenheit under normal
operating conditions. If measured temperatures are not available,
an estimate to the nearest 50°F should be made.
5. Exhaust Flow Rate: This number should be specified by recording
the design or maximum exhaust-gas volume unless actual measurements
are available. Units are actual cubic feet per minute and represent
the total volume of exhaust gas released at the operating temperature
of the stack (assume gas pressure is the same as normal atmospheric
pressure).
6. Velocity: This number should be specified by recording the design
or maximum exhaust-gas velocity unless actual measurements are
available. Units are feet per minute.
7. Plume Height: This field is to be filled in if the previous fields
on stack data are all blank. The plume height is a gross estimate
and is used only when the source has no definable stack.
8. Points with Common Stack: Columns 48 and 49 contain the NEDS Point ID
of the first point source discharging through the stack. Columns 50
and 51 contain the NEDS Point ID of the last point source discharging
through the stack. For a complete definition of common stack see EPA
publication APTD-1135, Guide For Compiling A Comprehensive Emission
Inventory, for March 1973.
33
-------
9. Compliance Status: One of the following codes must be selected to
record the present status of the source under existing legal
requirements:
Code
1 Source is in compliance with the most stringent air
pollution control requirements.
2 Source is not in compliance with existing legislation
and no variance has been given.
3 Source is not in compliance with existing legislation
but a variance has been given.
4 Compliance status is unknown.
10. Compliance Schedule: If the compliance status code is 2 or 3,
enter the year and month by which this source must be in
compliance.
11. Compliance Update: The day, month, and year of the most recent
change in compliance status for the source be entered in this
field. Leave the field blank if compliance status has been
reported as unknown (code 4). If the source is in compliance
with existing air pollution control legislation, then record
the record the time that such legislation was enacted.
12. ECAP: Certain point sources are required to submit to
government agencies on Emergency Control Action Program
34
-------
that specifies a detailed plan for immediately reducing
emissions whenever air pollution in an area is considered an
emergency condition. The following list shall be used to
denote whether or not an ECAP has been submitted to an appro-
priate government agency. Leave blank if status is unknown.
0 ECAP is not required
1 ECAP is required but has not been submitted
2 ECAP has been submitted.
13. Control Regulations: This field is used to identify air pollu-
tion control regulations that are in effect and apply to the
source.
14. Card Number: 12
15. Transaction Code: The transaction codes are:
A - Add
C - Change
D - Delete
35
-------
Card 13
1. Segment ID: Enter the same number as in the Segment Id of the
11 card.
2. Pollutant ID: This field is a five digit code that represents
the pollutants whose emissions are being measured. Source is
SAROAD Parameter Coding Manual, EPA Publication No. APTD-0633.
3. Control Equipment Cost: Enter the annual cost of maintenance
and operation of pollution control equipment.
4. Primary Control Equipment: This field should be completed with
the Control Equipment Identification Code. Only control devices
that reduce the uncontrolled emission normally associated with
the specific source process should be reported.
5. Secondary Control Equipment: If there is an additional control
device installed for this pollutant enter the Control Equipment
Identification Code in this field.
36
-------
6. Estimated Control Efficiency: The overall collection effi-
ciencies in weight percent of all control equipment at the
point source should be entered. Assume that the pollutant
load entering the control equipment is the normal, uncontrolled
quantity for that specific process.
7. Emissions Estimate: The annual, controlled emissions from
the point source, in tons per year, should be entered here.
These calculations should include the effect of pollutant
removal by installed control equipment.
8. Emissions Measured: The annual, controlled emissions from
the point source, in tons per year, as actually measured by
test equipment should be entered here. These measurements
can be compared against the estimates to check the validity
of the emission factors.
9. Allowable Emissions: Entered here should be the maximum
emissions, in tons per year, that the source is legally
allowed to discharge into the atmosphere.
10. Emission Units: This field is for future expansion of the
system. It will eventually allow the user to specify units for
the emissions in other than NEDS units. It is currently ignored
by the system.
37
-------
11. Estimation Method: The following code list must be used to
specify the method used to ascertain the estimated emissions:
Code Description of Method
0 Not applicable (if emissions are negligible)
1 Stack-test results or other emission
measurement
2 Material balance using engineering knowledge
and expertise of process
3 Emission calculated using emission factors
4 Guess
If code 3 is used the file maintenance program will calculate the
estimated emissions if all the factors are present.
12. Test Method: A user defined code to indicate the method used to
ascertain the measured emissions.
13. Card Number: 13
14. Transaction Code: The transaction codes are:
A - Add
C - Change
D - Delete.
38
-------
Card 21
1. Segment 1 ID: Enter the same number as in the Segment ID of
the 11 card for the point source to which this segment belongs.
2. Segment 2 ID: Each Fuel-Process set (21,22,23) creates a Fuel-
Process segment in the master file. Each Fuel-Process segment
under the same point source segment must have a unique Segment
2 ID number. This number must also be used to reference a
particular segment when making a change or deleting a segment.
3. SCC Code: The Source Classification Code process description
that most nearly describes the process should be entered by
its eight-digit numerical code. If the most appropriate SCC
description appears to be significantly different from the
actual process, enter nothing in this field, but enter NEW
SCC NEEDED in the Source Description field of the 22 card.
4. BEC Code: Enter the Basic Equipment Classification Code that
describes the equipment or process for this source. The last
two digits are used to sequentially number identical units at
the same source.
39
-------
5. Fuel Units: This field is for future expansion of the system.
It will eventually allow the user to specify units for the fuel-
process field in other than NEDS units. It is currently ignored
by the system.
6. Fuel, Process, Solid Waste: The annual figures will be reported
in this field using the units associated with the SCC code for
this process.
7. Maximum Design: The maximum hourly design rate of the most
important process equipment, or the upper operating limit that
generally would not be exceeded in normal practice, should be
entered here. Units are expressed in those corresponding to
the SCC for the process.
8. Sulfur and Ash Content: Entries are to be made in these columns
for all combustion processes. If the process does not burn fuel,
leave the field blank.
9. Heat Content: This field is to be completed only when the process
involves combustion. Units are millions of BTU per SCC.
10. Card Number: 21
40
-------
11. Transaction Code: The transaction codes are;
A - Add
C - Change
D - Delete.
41
-------
Card 22
1. Segment 1 ID: Enter the same number as on the Segment 1 ID
of the 21 card.
2. Segment 2 ID: Enter the same number as on the Segment 2 ID
of the 21 card.
3. Confidentiality of Data: Process information occasionally is
collected by a government agency under a guarantee that the
data will be treated in a confidential manner and will not
be released to the public. This column indicates whether or
not any data for this source are officially considered con-
fidential. A one (1) indicates confidential classification,
a two (2) no classifiaction and a blank indicates an unknown
status.
4. Source Code: this is needed for NEDS reporting. Enter the
following codes for the process category: B - Boiler, P -
Process, C - Other Combustion unit.
5. Source Description: Enter a brief description of the source
or comments as needed.
-------
6. Emission Factor Source: If this field contains a T the
Emission Factors insertion program will insert the appropriate
Emission Factors from a table of SCC codes.
7. Card Number: 22
8. Transaction Code: The transaction codes are:
A - Add
C - Change
D - Delete.
-------
Card 23
1. Segment 1 ID: Enter the same number as in the Segment 1 ID of
the 21 card.
2. Segment 2 ID: Enter the same number as in the Segment 2 ID of
the 21 card.
3. Pollutant ID Code: This field is a five digit code that represents
the pollutant whose emissions are being measured. Source is SAROAD
Parameter Coding Manual, EPA Publication No. APTD-0633.
4. Emission Factor: The emission factor is a statistical average
of the rate at which a pollutant is released to the atmosphere
as a result of some activity, such as combustion or industrial
production, divided by the level of that activity. The emission
factors for each SCC may be found in the EPA publication Compilation
of Air Pollutant Emission Factors. Publication No. AP-42.
5. Ash/Sulfur Code: This code indicates whether or not the Ash or
Sulfur percentage is to be used in the calculation of the estimated
emissions. The codes are: A - Ash, S - Sulfur and blank is
neither apply.
6. Emission Factor Units: This field is for future expansion.
Eventually it will indicate the units in which the emission
44
-------
factors are expressed. The emission factors are now treated
as standard NEDS units. Reference OAP Publication No. AP-42.
7. Card Number: 23
8. Transaction Code: The transaction codes are:
A - Add
C - Change
D - Delete.
Note: Card columns 23 to 38 may be repeated two more times on the
same 23 card. This allows the storing of up to three sets of
emission factors information on each card.
45
-------
3.0 FILE MAINTENANCE AND RETRIEVAL
There are two major EIS programs for building, maintaining and retrieving
data from the EIS master file. These are the File Maintenance program and
the Retrieval program.
-------
3.1 FILE MAINTENANCE
The File Maintenance program performs two basic functions, the creation
of a new system master file and the modification of an existing system
master file. The program can operate in any of three modes to support
the two basic functions. These modes are add, change and delete. Every
transaction card input to the file maintenance program must be either
an add, change or delete card, identified by an A, C or D in column 80.
Add cards are used to create a new system master file, and to add new
records to an existing file. Add cards are always entered in logical
segment groupings. Thus, a type 0 segment must be added as a complete
entity of one 01 card, one 02 card and one 03 card. Similarly, a type I/
type 2 segment combination must be added subordinate to an already
existing type 0 segment as a complete entity of one 11 card, one 12 card,
one or more 13 cards, and multiple occurrences of one 21 card, one
22 card and one or more 23 cards. A type 2 segment cannot be added by
itself. That is, it must be added in conjunction with a type 1 segment.
Up to six type 2 segment can exist subordinate to one type 1 segment.
Change and delete cards are used to modify an existing system master file.
Any data field specified as non-blank on a change card will replace the
corresponding field in the designated file record. Change cards use the
same format as add cards except that all data fields except the fields
being changed are left blank. Thus any field on any card can be changed
except the record key, segment 1 and segment 2 ID's and pollution ID.
47
-------
Delete cards can be used to delete an entire logical record (type 0 segment
and all subordinate type 1 and 2 segments), a type 1 segment (with all
subordinate type 2 segments) or a single type 2 segments.
All transaction cards entered into the file maintenance program must be
sorted in master file sequence either by the user or by the emission
factors insertion program, as the master file is passed only once per
run for fast performance.
Add Cards
Records are created or added to the master file using the following com-
binations of ADD cards. Only those fields with the name filled in are
required. All other fields may be blanks. At least the three cards
shown in each segment are required to create each segment.
To add a plant segment (type 0 segment):
KEY I DATE I I (31 I A
KEY
KEY
03
13 14
18
To add a point source segment (type 1 segment), which is allowed
to have subordinate to it up to six machine process segments
(type 2 segments):
KEY
KEY
KEY
DATE
ID
ID
ID | POLL. ID
11
12
13
A
A
A
1 13 14 18 19 20 21 25 78 79 80
48
up to 16
-------
KEY
KEY
KEY
DATE
ID
ID
ID
ID2
ID2
ID2
1 21
1*2
POLL. ID| 23
A
A
A
up to 6
sets with
up to 16
23 cards
per set
13 14 18 19 20 21 22 23 27 78 79 80
Up to 16 unique pollutant ID'3 are allowed. Thus multiple type 13A and
23A cards are allowed. One, two or three pollutant ID's can be present
on any type 23A card. Also, since up to six (there must be at least one)
machine process (type 2) segments can be subordinate to any point source
(type 1) segment, there can be up to six sets of the 21A/22A/multiple
23A type cards following the last 13A card of each point source segment.
Change Cards
Any record on an existing master file can be changed through the use of a
change card. Depending on the segment type being changed, certain fields
on the card are required to be filled in. Other than these required fields,
any other fields on the card which is non-blank will replace the corres-
ponding field of the indicated record on the master file.
To change a field in a master file record, only the single transaction
card which contains that field need be used. For example, assume that
the field called COMPLIANCE-STATUS is to be changed. This field is part
of the point source (type 1) segment and is included in the type 12 trans-
action card. Thus only a type 12 change card is required. The types 11
and 13 cards are unnecessary.
The following is the format for each type of change card, with the re-
quired fields filled in by name.
49
-------
o Type 01 change card:
KEY
1 13
DATE
14 18
01
78 79
C
80
o Type 02 change card:
KEY
1 13
DATE
14 18
02
78 79
C
80
o Type 03 change card:
KEY
1 13
DATE
14 18
03
78 79
C
80
o Type 11 change card:
KEY
1 13
DATE ID
14 18 19 20
11
78 79
C
80
o Type 12 Change card:
KEY
1 13
DATE ID
14 18 19 20
12
78 79
C
80
o Type 13 change card:
KEY
1 13
DATE ID PO
14 18 19 20 21
LL. ID 1 13
25 78 79
C
80
o Type 21 change card:
KEY
1 13
DATE ID IE
14 18 19 20 21
2 21
22 78 79
C
80
o Type 22 change card:
KEY
1 13
DATE ID IE
14 18 19 20 21
•2 22
22 78 79
C
80
o Type 23 change card:
KEY
1 13
DATE ID IE
14 18 19 20 21
2 POLL. ID 23
22 23 27 78 79
C
80
50
-------
Delete Cards
Three segments (or segment combinations) can be seleted from an existing
master file. The following cards, with required fields filled in,
illustrate how to delete these segments.
o Delete an entire logical record of plant (type 0) segment and
all subordinate point source (type 1) and machine process
(type 2) segments:
t KEY I | 01 I D |
1 13 78 79 80
o Delete a point source (type 1) segment and all subordinate
machine process (type 2) segments:
I KEY I | ID | | 11 | D |
1 13 19 20 78 79 80
o Delete a machine process (type 2) segment:
| KEY | | ID |lD2 | | 21 I D I
1 13 19 20 21 22 78 79 80
In general, the KEY, IDs, card number and transaction code are required
for all types of transactions. In addition, the POLL. ID and DATE are
required for adding or changing information in the master file.
51
-------
3.2 RETRIEVAL
The CDHS retrieval component retrieves data from files based on English-
like retrieval statements. The retrieved data records are placed on an
answer data set for future processing. The answer data set may be sorted
or not depending on the sort specifications.
The functions of the language processor/retriever are:
a. Editing and processing of retrieval and control statements.
b. Compilation of the retrieval logic to produce a COBOL program
for actual retrieval.
c. Execution of the COBOL program and the construction of the
answer data set containing records qualified for retrieval
by the retrieval specification.
52
-------
3.2.1 RETRIEVAL LANGUAGE AND OPERATORS
The CDHS retrieval language consists of $$ control statements, retrieval
statements and sort statements. The statements must be specified in a
prescribed order. A retrieval that produces an unsorted answer set re-
quires three control statements. If the answer set is to be sorted an
additional control statement is required. The two valid statement
sequences are:
a. Unsorted Answer Set
$$QUERY
$$IF
Retrieval Statements
$$END
b. Sorted Answer Set
$$QUERY
$$SORT
Sort Statements
$$IF
Retrieval Statements
$$END
53
-------
QUERY Control Card
The query control indicates the beginning of the set of statements for a
retrieval. This card is required and contains four fixed format fields
as follows:
Cols 1-7 $$QUERY
Cols 12-13 Major sort key
Cols 16-23 Query name
Col 26 Type 2 Record processing indicator
The major sort key field is used to separate the answer sets from batched
retrievals. The batched retrieval feature is not implemented. Therefore,
this field may contain blanks or any other two characters.
The query name field contains a one to eight character name that is
assigned to the query.
The type 2 record processing indicator field may contain a blank indicating
that the type 2 records are to be Included with each qualifying record or
the letter N indicating that the type 2 records are to be omitted.
54
-------
SORT Control Card
The sort control card indicates that a sorted answer set is desired. This
card is optional and if present contains one fixed format field as follows:
Cols 1-6 $$SORT
Immediately following the sort control cards are from one to five sort
specification statements. The sequence of these cards determine the order
of the sort minor key. The first card will be the high subfield of the
minor key, the next will be the next lower subfield and the last card will
be the lowest subfield of the last card will be the lowest subfield of the
sort minor key. Each sort statement consists of two fixed format fields
as follows:
Col 7-36 Sort name
Col 38-47 Sort order
The sort name field contains the name of a data file field which is to
be sorted. This name must be one of the names listed in Table 3.2-1
or 3.2-2.
The sort order field describes the order of sorting the specified field.
This field must contain the word ASCENDING or DESCENDING depending on the
desired sort order.
55
-------
For example, if the order of the sort control cards is as follows:
AQCR ASCENDING
PLANT DESCENDING
POLLUTANT ID DESCENDING
The retrieved data will be sorted first by AQCR in ascending order, then
by plant in descending order within each AQCR, then by Pollutant ID within
each Plant in descending order. The user must visualize how the sort
specifications will cause the data to be presented in the requested re-
port as this can make a significant difference in the amount of printout
which will result assuming a report is generated.
56
-------
The following list of names from the fixed segment may be referenced in
a retrieval specification statement in either EIS fixed format or COBOL
language.
AQCR
CITY
CONTACT
COUNTY
DATE-OF-SEGMENT
LOCAL-CONTROL
NUMBER-OF-EMPLOYEES
OWNER
PLANT-ID
PRINCIPAL-PRODUCT
PROPERTY-AREA
SEGMENT-DAY
SEGMENT-ID
SEGMENT-YEAR
STATE
TELEPHONE
USER-CONTROL-REGION
USER-PLANT-ID
UTM-ZONE
The following two names from the fixed segment may be referenced in a
retrieval specification in the COBOL language only.
ESTABLISHMENT
MAILING-ADDRESS
RETRIEVAL NAMES
Table 3.2-1
57
-------
The following list of names from the point source segment may be referenced
in a retrieval specification statement in either EIS fixed format or COBOL
language.
ANNUAL-THRUPUT
BOILER-DESIGN-CAPACITY
COMPLIANCE-S CHEDULE
COMPLIANCE-SCHEDULE-MONTH
COMP LIANCE-S CHE DULE-YEAR
COMPLIANCE-STATUS
COMPLIANCE-STATUS-DAY
COMPLIANCE-STATUS-MONTH
COMPLIANCE-STATUS-UPDATE
COMPLIANCE-STATUS-YEAR
CONTROL-REGULATIONS
DAY-WEEK
DEC-FEE
DIAMETER
ECAP
EMISSION-NBR
FLOW-RATE
HEIGHT
HOURS-DAY
IPP
JUN-AUG
LATITUDE
LATITUDE-DEGREE
LATITUDE-MINUTE
LATITUDE-SECOND
LONGITUDE
LONGITUDE-DEGREE
LONGITUDE-MINUTE
LONGITUDE-SECOND
MAR-MAY
NEDS
NORMAL-OPERATING
PLUME
POINT-ID
POINT-S OURCE-DATA
POINTS-PER-STACK
REG-1
REG-2
REG-3
SEP-NOV
SIC
SPACE-HEAT
STACK-DATA
TEMPERATURE
USER
UTM-COORDINATES
UTM-HORIZONTAL
UTM-VERTICAL
VELOCITY
WEEK-YEAR
RETRIEVAL NAMES
Table 3.2-1 (Continued)
58
-------
The following list of names from the repeating portion of the point
source segment may be referenced In a retrieval specification statement
In either EIS fixed format or COBOL language.
ALLOWABLE
CNTL-EQUIP-COST
CONTROL-EQUIPMENT
EMISSION-UNITS
EMISSIONS
EST-CONTROL-EFF
ESTIMATES
ESTIMATION-METHOD
MEASURED
POLLUTION-ID
PRIMARY
SECONDARY
TEST-METHOD
REPEATING RETRIEVAL NAMES
Table 3.2-2
59
-------
IF Control Card
The IF control card indicates the beginning of the retrieval specifications
for this query. This card is required and nay be in one of three formats.
o IF Format 1.
This format of the IF control card is as follows:
Cols 1-4 $$IF
The IF format 1 is used when it is desired to state the retrieval specifi-
cation in EIS fixed format form.
Immediately following the IF format 1 card are the EIS fixed format retrieval
specification cards. Each of these cards contain a clause of the retrieval
specification where a clause is defined to consist of subject name, a
relational operator and an object name. For example, A = B is a clause
with A the subject name, = the relational operator and B the object name.
A multiple clause retrieval specification, i.e., A = B AMD C = D, consists
of two clauses A = B, C = D connected by the logical connector AND. The
format of fixed format retrieval specification cards is as follows:
Cols 8-6 Left Parenthesis
Cols 7-36 Subject name
Cols 38-39 Relational operator code
Cola 41-74 Object name
Cols 76-78 Logical connector
60
-------
The left parenthesis field may contain up to four parentheses right
Justified in the field.
The subject name field must contain one of the data file field names listed
in Table 3.2-1 or Table 3.2-2. Any other name will cause a diagnostic.
The relational operator field must contain one of the following codes
left justified in the field.
Code Meaning
= equal
x' less than
,. greather than
N= not equal
N< not less than
N> not greater than
The object name field may contain one of the data file field names listed
in Table 3.2-1 or Table 3.2-2, a numerical literal, or an alphanumeric
literal delineated by quotes. If right parentheses are needed to balance
any left parentheses they must be placed in the object name field immedi-
ately after the last character of the object name.
The logical connector field may contain blanks or the words AND or OR.
Blanks in this field terminate the editing of the retrieval specification.
The words AND or OR indicate that another clause follows and editing is
to continue.
61
-------
o IF Format 2.
This format of the IF control card consists of three fixed
format fields as follows:
Cols 1-4 $$IF
Cols 10-13 USER
Col 26 Qualification Type
The IF format 2 is used when it is desired to state the retrieval
specification in COBOL language.
Immediately following the IF format 2 control cards are one or more cards
containing the retrieval specification. These cards are punched according
to COBOL rules for syntax and punctuation. The first word on the first
card must be IF. Data file field names referenced in the retrieval
specification must be one of those listed in Table 3.2-1 or Table 3.2-2.
Since the HIS language processor does not examine these cards nay improper
punching could result in COBOL diagnostics or unpredictable retrieval.
The qualification type field must be the character Y if the retrieval speci-
fication refers to any of the data file field names listed in Table 3.2-2.
o IF Format 3.
This format of the IF control card consists of four fixed
format fields as follows:
Cols 1-4 $$IF
Cols 10-13 USER
Cols 16-23 Library member name
Col 26 Qualification Type
62
-------
The IF format 3 is used when It is desired to insert a previously written
COBOL language retrieval specification statement into a query. The
retrieval specification must follow the rules defined for a retrieval
specification following an IF format 2 control card. The main difference
between IF format 2 and IF format 3 is that for format 2 the retrieval
specification is in-line immediately following the IF format 2 control
card while for format 3 the retrieval specification is from a user library
by means of the member name field.
63
-------
END Control Card
The END control card indicates the end of the set of statements for a
retrieval. This card is required and contains $$END in card columns 1-5.
-------
3.2.2 RETRIEVAL LOGIC
The following discussion will illustrate how the retriever processes
the logical records of the data file. The processing varies depending
on what fields are being used for qualification and whether or not a
sort is specified and if so what field is being used for the sort.
For qualification purposes a logical record consists of the fixed seg-
ment (type 0 record) and a single point source segment (type 1 record).
Qualification cannot be performed on just the fixed segment. The machine
process segments (type 2 records) cannot be used for qualification. At
the user's option (the N in the query control card) they are either
omitted or added to each qualifying logical record.
65
-------
Assume that the following logical records exist on some data file.
STATE
SIC
35
POLLUTION-ID
00002
00005
SIC
32
STAT
09
POLLUTION-ID
00003
00001
00002
00005
00004
ESTIMATES
27
55
1 32
43
13
CE
ESTIMATES
23
35
14
Type 0 Record
Type 1 Record
Repetition 1
Repetition 2
Logical
Repetition 3 Record 1
Repetition 4
Repetition 5
Type 0 Record
Type 1 Record
Repetition 1
Repetition 2
Repetition 3
Logical
Record 2
The first logical record has a STATE value of 10, SIC value of 32 and five
repetitions containing POLLUTION-ID values of 00001 to 00005 and ESTIMATES
of 13 to 27. The second logical record has a STATE value of 09, SIC value
of 35 and three repetitions. The following query examples will show how
the two logical records will appear on the answer set.
66
-------
o Example 1
It is desired to qualify all records that have a STATE value of
10 or 09. Sorting is not desired. The query is:
$$QUERY EXAMPLE 1
$$1F USER
IF STATE = '10' OR - '09'
$$END
The answer set will contain the following two records. Since a sort
was not specified the records will be in file order.
STATE
10
Type 0 Record
STATE
JS2.
Type 1 Record
Repetition 1
Repetition 2
Answer Set
Repetition 3 Record 1
Repetition 4
Repetition 5
Type 0 Record
Type 1 Record
Repetition 1 Answer Set
Record 2
Repetition 2
Repetition 3
67
-------
Example 2
It is desired to qualify all records that have a STATE value of
10 or 09 and to sort the qualifying records in ascending order of
STATE values. The query is:
$$QUERY EXAMPLE 2
$$SORT
STATE ASCENDING
$$IF USER
IF STATE - '10' OR = '09'
$$END
The answer set will contain the following two records and since a
sort was specified to record order is changed.
STATE
09
Type 0 Record
Type 1 Record
STATE
10
Repetition 1 Answer Set
Record 1
Repetition 2
Repetition 3
Type 0 Record
Type 1 Record
Repetition 1
Repetition 2 Answer Set
Record 2
Repetition 3
Repetition A
Repetition 5
68
-------
Example 3
It is desired to qualify all records that contain a POLLUTION-ID
of 00001 or 00002 and to sort the qualifying records in ascending
order of STATE values. This query is qualifying on a field in
the repetitions data. The retriever cycles through the repetition
data and marks those repetitions that meet the qualification. The
repetitions that did not qualify are removed. The query for this is
$$QUERY EXAMPLE 3
$$SORT
STATE ASCENDING
$$IF USER
IF POLLUTION-ID <=> '00001' OR =• '00002'
The answer set will contain the following two records:
STATE
09
POLLUTION-ID
00002
STATE
10
POLLUTION-ID
00001
00002
Type 0 Record
Type 1 Record
Repetition 2
Type 0 Record
Type 1 Record
Repetition 2
Repetition 3
Answer Set
Record 1
Answer Set
Record 2
69
-------
Example 4
It is desired to qualify all records that contain a POLLUTION-ID
of 00003 or 00005 and to sort the qualifying records according to
POLLUTION-ID for STATE. This query is qualifying on a field in the
repetitions data and also sorting on a field in the repetition
data. The retriever cycles through the repetition data and for
each repetition that meets the qualification outputs a logical
record on the answer set. The query is:
$$QUERY EXAMPLE 4
$$SORT
STATE ASCENDING
POLLUTION-ID DESCENDING
$$IF USER
IF POLLUTION-ID => '00003' OR '00005'
$$END
The answer set for this query will contain the following four records:
STATE
09
POLLUTION-ID
00005
Type 0
Type 1 Record Answer Set
Record 1
Repetition 3
70
-------
STATE
09
POLLUTION-IDl
00003
Type 0 Record
Type 1 Record Answer Set
Record 2
Repetition 1
STATE
Ifl
POLLUTION-ID
00005
Type 0 Record
Type 1 Record Answer Set
Record 3
Repetition A
STATE
POLLUTION-ID
Type 0 Record
Type 1 Record Answer Set
Record 4
Repetition 1
71
-------
4.0 OUTPUT PROGRAMS
.There are five output programs in the EIS system, each producing a dif-
ferent form of output. These five are the File List, Summary Report, NEDS
Point Source, NEDS Area Source, and NEDS Area Source Report output pro-
grams .
72
-------
4.1 FILE LIST
This program produces a detail listing of the EIS master file. The mas-
ter file is listed with one point source record per page. If a single
plant location has more than one point source, the plant/location infor-
mation is repeated for each point source page. If area source data is in
the same file as point source, the point source data should be selected
by use of the EIS retrieval capability (IF USER-PLANT-ID N = 'AREA
SOURCE').
This program can also be used to print a detail listing of all of the
retrieval answer files. It will list the area source records but the
field headings will be meaningless.
The data flow and run deck setup are illustrated in Figure 4.1-1.
73
-------
Data Flow
faster
File
EIS File
Print
EIS File
Detail List
EIS
Retrieval
(if needed)
Point
Answer
Deck
y"
Print Pgm.
JCL
''Retrieval
JCL
(optional)
FILE LIST DATA FLOW AND DECK
Figure 4.1-1
74
-------
4.2 SUMMARY REPORT
The EIS Summary capability is Intended to be a tool for Air Pollution
Control Agencies. It is used with the EIS Retrieval capability, i.e.,
the retrieval program will select data and sort it in order to produce
the summary.
The following data values are summed.
1 - Source Count - This is a sum of sources emitting a pollutant.
2 - Estimated Emissions - This is a sum of estimated emissions.
3 - Actual Emissions - This is a sum of actual (measured)
emissions.
4 - Allowable Emissions - This is a sum of allowable (standard)
emissions.
5 - Control Equipment Cost - This is a sum of the cost for the
control equipment.
A number (any combination of any five data fields in the point and stack
data) of summarys can be produced. There can be from one to five levels
of totals. These are specified by supplying simple "Move" statements.
Example:
MOVE AQCR TO BREAK-ONE
75
-------
The field to be summed is moved into a system control field. There are
five such control fields, each corresponding to the five levels of totals.
The control fields are:
BREAK-ONE Lowest level of total
BREAK-TWO Next higher level
BREAK-THREE Next higher level
BREAK-FOUR Next higher level
BREAK-FIVE Highest level of total
The data must be sorted to correspond to the Summary being produced. This
is accomplished by executing the EIS retrieval capability to produce the
Summary input data. Note that because emissions are by pollutant, one of
the sorts must be pollutant identification to produce a meaningful
summary.*
o Example 1:
To produce a summary of emissions by SIC within a county, the
following retrieval and summary statements must be provided by
the user (retrieval qualifications are not shown).
*The only meaningful summary totals are those at the POLLUTION-ID level.
If all of the data items are for the same pollutant then all totals are
meaningful. If two or more pollutants have been selected, only the
totals up to the level for POLLUTION-ID are meaningful. For example, if
POLLUTION-ID were at BREAK-THREE level, BREAK-ONE, BREAK-TWO, and BREAK-
THREE level sums would be meaningful but BREAK-FOUR and BREAK-FIVE sums
would not be meaningful.
76
-------
Retrieval
SORT SIC, COUNTY, POLLUTION-ID
(major to minor)
Summary
MOVE MSTR-POLLUTION-ID (EM-SET-INDEX) TO BREAK-ONE.
MOVE MSTR-COUNTY TO BREAK-TWO.
MOVE MSTR-SIC TO BREAK-THREE.
o Example 2:
To produce a summary of emissions by PLANT within SIC within CITY
within COUNTY the following retrieval and summary statements must
be provided.
Retrieval
SORT COUNTY, CITY, SIC, PLANT, POLLUTION-ID
Summary
MOVE MSTR-POLLUTION-ID (EM-SET-INDEX) to BREAK-ONE.
MOVE MSTR-PLANT TO BREAK-TWO.
MOVE MSTR-SIC TO BREAK-THREE.
MOVE MSTR-CITY TO BREAK-FOUR.
MOVE MSTR-COUNTY TO BREAK-FIVE.
77
-------
The summary report can be personalized, i.e., certain page header and
column header information can be provided by the user. This informa-
tion is provided on control cards. The information can be changed
each time the summary is executed.
Control cards for providing information to the summary report are
described below.
Card 1
Cols Content Default
1-3 OP1
6-37 Line 1 of Report Title EMISSIONS INVENTORY SYSTEM
38-69 Line 2 of Report Title STANDARD SUMMARY OUTPUT
71-78 Date
Card 2
Cols
1-3
6-37
38-69
Content
OP 2
From Organization
To Organization
Default
AIR POLLUTION CONTROL AGENCY
INFORMATION
78
-------
Card 3
Cols
1-3
6-13
14-21
22-29
30-37
38-45
46-53
54-61
62-69
Card 4
Cols
1-3
6-13
14-21
Content
OP 3
Part
Part
Part
Part
Part
Part
Part
Part
1
2
1
2
1
2
1
2
of
of
of
of
of
of
of
of
Column
Column
Column
Column
Column
Column
Column
Column
1
1
2
2
3
3
4
4
Header
Header
Header
Header
Header
Header
Header
Header
Content
OP4
Part
Part
1
2
of
of
Column
Column
5
5
Header
Header
Default
BREAK
FIVE
BREAK
FOUR
BREAK
THREE
BREAK
TWO
Default
BREAK
ONE
The Summary Report Control Cards are used to "personalize" this report.
A report header defaults are as follows:
AIR POLLUTANT EMISSIONS SUMMARY
EMISSIONS INVENTORY SYSTEM FROM AIR POLLUTION CONTROL AGENCY
STANDARD SUMMARY OUTPUT TO INFORMATION
BREAK BREAK BREAK BREAK BREAK
FIVE FOUR THREE TWO ONE
79
-------
The summary statements (MOVE) are actually compiled into a program and
executed. It is this program which reads the control cards (if any) and
produces the summary report.
A summary program can be temporary (for ad-hoc reports) or permanent (for
standard reports), i.e., the program can be compiled, used and deleted from
the system or it can be compiled and stored on a library to be used over
and over again. These options are illustrated by figures 4.2-1 through
4.2-3.
80
-------
Data Flow
Move
Statements
COBOL
Compiler
Link Edit
I
Load
(Program^
Library
Deck
LINKEDIT
JCL
Move
Statements
COBOL JCL
(including member name
for Load Library)
PERMANENT SUMMARY REPORT GENERATION
Figure 4.2-1
81
-------
Data Flow
Master
File
EIS Retrieval
Program
Answer
File
Summary
Control
Cards
^
W
Summary
Program
fc
W
Summary
Report
. ^-^
Deck
I
Summary
Control Cards
I Summary
| JCL
Retrieval
JCL
PERMANENT SUMMARY REPORT EXECUTION
Figure A.2-2
82
-------
Data Flow
^ "
Master
File
k.
w
EIS
Retrieval
k.
- — w
^ ^
Answer
File
[Move
Statements
X
Summary
Control
Cards
fc
W
fc,
w
COBOL
Compiler
and Link
Edit
1
Summary
Program
1
Summary
Report
^ -*
Source
^ Library
^
^ ... 1
Deck
f Summary Control Cards
j Summary JCL
Edit JCL
I Move Statements
| COBOL JCL
Retrieval
JCL
TEMPORARY SUMMARY REPORT GENERATION AND EXECUTION
Figure 4.2-3
83
-------
4.3 NEDS POINT SOURCE OUTPUT
The NEDS point source output program converts the records on an EIS file
to NEDS format point source records. Each EIS record is converted as fol-
lows: the type 0 record produces an API record; the type 1 record pro-
duces AP2, AP3, AP4 and APS records; and each type 2 record produces an
AP6 record. If a single plant (type 0 record) has more than one point
source (type 1 record), the API record is repeated for each new type 1
record. If area source data is in the same file as point source data,
the point source data should be selected onto a separate file by use of
the EIS retrieval capability (IF USER-PLANT-ID N = 'AREA SOURCE').
The data flow and run deck setup are illustrated in Figure 4.3-1.
84
-------
Data Flow
Master
File
EIS Retrieval
(if needed)
NEDS Point
Source
Output
Diagnostic
Messages
Point
Source
Answer
Deck
1
NEDS Point Source JCL
Retrieval JCL
(optional)
NEDS POINT SOURCE OUTPUT - DATA FLOW AND DECK
Figure A.3-1
85
-------
4.A NEDS AREA SOURCE OUTPUT
This program produces NEDS Area Source output from EIS Area Source data.
The program expects input to be Area Source data. Therefore, if Area
Source data is in the same file as Point Source data, it must be
selected onto a separate file by use of the EIS retrieval capability
(IF USER-PLANT-ID - AREA SOURCE).
There is one control card which allows the user to specify whether the
NEDS "action" code will be A (add), D (delete) or C (change). All action
codes must be the same for a given run. Default (no control card) will
be A.
Control Card Format
Cols
1-16
17
18
19-80
Content
NEDS AREA SOURCE
Not Used
Action Code
Not Used
The data flow and deck setup is illustrated in Figure 4.4-1.
86
-------
Data Flow
Master
File
Control
Cards
Area Source
Output
NEDS Area
Source
Cards
Deck
( Control
1 Card
| Area Source
1 Output JCL
X
Retrieval
JCL
NEDS AREA SOURCE OUTPUT - DATA FLOW AND DECK
Figure 4.4-1
87
-------
4.5 NEDS AREA SOURCE REPORT
The NEDS area source report program produces a formatted listing from
NEDS area source records. One complete set of NEDS area source
records (AAl through AA6) will be listed per page. If errors exist in
the NEDS records, the results will be unpredictable.
The data flow and run deck setup are illustrated in Figure 4.5-1.
88
-------
Data Flow
NEDS
Cards
NEDS Area
Source
Report
Diagnostic
Messages
NEDS Area
Source
Listing
Deck
NEDS Area
Source JCL
NEDS AREA SOURCE REPORT - DATA FLOW AND DECK
Figure 4.5-1
89
-------
5.0 DATA CONVERSION PROGRAMS
There are two EIS conversion programs which convert other types of data
to EIS format. These are the NEDS Point Source to EIS and the NEDS Area
Source to EIS.
90
-------
5.1 NEDS POINT SOURCE TO EIS
This Program converts NEDS Point Source input to the Emission Inventory
System transaction card format. The one (1) card in the NEDS Point
Source input creates the EIS zero (0) record transaction cards. Cards
two (2) through five (5) in the NEDS Point Source input create the EIS
one (1) record transaction cards. The six (6) card in the NEDS Point
Source input creates the EIS two (2) record transaction cards.
All data items in the EIS transaction records which have no corresponding
data items in the NEDS input records are set to blanks with the exception
of the following:
1. SET-ID (SEGMENT-1-ID) - Set to the same value as the NEDS
POINT-ID.
2. POLLUTANT-ID - Five digit parameter codes are given to pollutants
reported in NEDS input data. These codes are taken from the
SARQAD Parameter Coding Manual, EPA Publication No, APTD-0633.-
3. SEGMENT-2-ID - Initialized to 5 and incremented by 5 for each
AP6 card. (2 digits)
4. EMISSION-FACTOR-SOURCE (EF-SOURCE) - A one byte code telling
the emission factor program to provide POLLUTANT-ID's. Set to
"A" for the Emission Factors Insertion Program.
91
-------
5.2 NEDS AREA SOURCE TO EIS
This program converts NEDS Area Source input to the Emission Inventory
System transaction card format. The first five (5) area source input
cards are all required to generate the EIS transaction records.
All data items in the EIS transaction records which have no corresponding
data items in the NEDS input records are set to blanks with the exception
of the following:
1. USER-PLANT-ID - A literal of 'AREA SOURCE1 is placed in this
field.
2. PLANT-ID - PLANT-ID is set to 9999 since the lowest level
addressed is the Area Quality Control Region (AQCR).
3. NUMBER-OF-EMPLOYEES - This field is filled by the value in the
county population field of the three (3) cards in NEDS Area
Source input.
4. SET-ID - SET-ID is initialized to 01 and incremented sequen-
tially by 1 for each emission category reported on the NEDS
Area Source input records (e.g., RESIDENTIAL FUEL = 01,
COMMERCIAL AND INSTITUTIONAL FUEL = 02, INDUSTRIAL - 03, etc.)
5. NEDS-POINT-ID - The NEDS-POINT-ID is set to 99 since the AQCR
is again the smallest area reported on. (2 digits)
92
-------
6. USER-POINT-ID - There are thirteen USER-POINT-IDs corresponding
to the thirteen major categories reported in NEDS Area Source
input. (3 digits.)
901 = RESIDENTIAL FUEL
902 = COMMERCIAL AND INSTITUTIONAL FUEL
903 = INDUSTRIAL FUEL
904 = ON SITE INCINERATION
905 = OPEN BURNING
906 =• GASOLINE FUEL
907 = DIESEL FUEL
908 = AIRCRAFT
909 = VESSELS
910 = EVAPORATION
911 = MEASURED VEHICLE MILES
912 = MISCELLANEOUS DUST
913 - MISCELLANEOUS BURNING
7. SIC - SIC is set to 9999. (4 digits.)
8. IPP - IPP is set to 99. (2 digits.)
9. POLLUTANT-ID - POLLUTANT-ID is given the five digit code from
the SAROAD Parameter Coding Manual. EPA Publication No. APTD-
0633 representing the five major pollutants reported.
10. ESTIMATION METHOD - ESTIMATION METHOD is set to '3' indicating
that emissions are to be calculated.
93
-------
11. SCC - SCC codes are supplied by the program reflecting the area
code, SDD-ID, sulfur Indicator, and ash Indicator.
12. FUEL PROCESS SOLID WASTE RATE - The value here will be the
value found in each fuel reported under the major emission
categories.
94
-------
Category
Residential Fuel
EIS ID
(USER-POINT-ID)
901
.Commercial and Insti-
tutional Fuel
902
Industrial Fuel
903
co
H O
V0
£j On Site Incineration
CO
Open Burning
Gasoline Fuel
Diesel Fuel
904
905
906
907
Fuel/Pollutant Source
Anthracite Coal
Bituminous Coal
Distillate Oil
Residual Oil
Natural Gas
Wood
Anthracite Coal
Bituminous Coal
Distillate Oil
Residual Oil
Natural Gas
Wood
Anthracite Coal
Bituminous Coal
Coke
Distillate Oil
Residual Oil
Natural Gas
Wood
Process Gas
Residential
Industrial
Commercial/Institutional
Residential
Industrial
Commercial/Institutional
Light Vehicle
Heavy Vehicle
Off Hiway
Heavy Vehicle
Off Hiway
Rail Locomotive
(AREA) SCC
90100111
90100222
90100330
90100440
90100500
90100600
90200111
90200222
90200330
90200440
90200500
90200600
90300111
90300222
90300700
90300330
90300440
90300500
90300600
90300800
90401100
90401200
90401300
90501100
90501200
90501300
90602100
90602200
90602300
90702200
90702300
90702400
-------
vO
CT>
Category
Aircraft
Vessels
Evaporation
Measured Vehicle Miles
>
x-v H o Miscellaneous Dust
o o* po
O t-n O
a. i M
N^ (-« Ci
O
Miscellaneous Burning
EIS ID
(USER-POINT-ID)
908
909
910
911
912
913
Fuel/Pollutant Source
Military
Civil
Commercial
Anthracite Coal
Diesel Oil
Residual Oil
Gasoline
Solvent Purchased
Gasoline Marketed
Limited Access Roads
Rural Roads
Suburban Roads
Urban Roads
Dirt Roads Traveled
Dirt Air Strips
Construction Land Area
Rock Handling & Storing
Forest Fires
Slash Burning
Frost Control
Structure Fires
Coal Refuse Burning
(AREA) SCC
90803100
90803200
90803300
90900111
90904230
90900A40
90904430
91005100
91005200
91106100
91106200
91106300
91106400
91207100
91207200
91207300
91207400
91308100
91308200
91308300
91308400
91308500
-------
CARD 01:
FIELD
State
County
AQCR
Plant ID
Date of Record
User Plant ID
Own
Action
Card Number
All Other Fields
CONTENTS
NEDS State
NEDS County
NEDS AQCR
9999
NEDS Year of Record-Day
AREA SOURCE
NEDS Density
NEDS Action
01
Blanks
CARD 02:
FIELD
State through Date of Record
Number of Employees
Action
Card Number
All Other Fields
CONTENTS
Same as Card 01
NEDS County Population
NEDS Action
02
Blanks
CARD 03:
FIELD
State through Date of Record
Action
Card Number
All Other Fields
CONTENTS
Same as Card 01
NEDS Action
03
Blanks
EIS AREA SOURCE RECORDS
Table 5.2-2
97
-------
CARD 11:
FIELD
State through Date of Record
Set ID
Point ID - NEDS
Point ID-User
SIC
IPP
Action
Card Number
All Other Fields
CONTENTS
Same as Card 01
Emission Source Count
Internally Generated
99
Category Code
9999
99
NEDS Action
11
Blank
CARD 12:
FIELD
State through Set ID
Action
Card Number
All Other Fields
CONTENTS
Same as Card 11
NEDS Action
12
Blanks
CARD 13:
FIELD
State through Set ID
Pollutant ID
Estimate Control Efficiency
Estimation Method
Action
Card Number
All Other Fields
CONTENTS
Same as Card 11
Pollutant ID Cod
Particulates - 11101
S02 - 42401
NOX - 42602
HC - 43101
CO - 42101
NEDS Action
13
Blanks
EIS AREA SOURCE RECORDS
Table 5.2-2 (cont.)
98
-------
CARD 21:
FIELD
State through segment 1 ID
Segment 2 ID
SCC
Fuel, Process, Solid Waste
Percent Sulfur
Percent Ash
Heat Content
Action
Card Number
All Other Fields
CONTENTS
Same as Card 11
Internally Generated
Segment Count
NEDS Fuel/Pollution times
Heat Content if not
zero
NEDS Percent Sulfur
NEDS Percent Ash
Zero or NEDS quantity (Forest
fires, slash burning,
frost control and coal
refuse burning) ,
NEDS Action
21
Blanks
CARD 22:
FIELD
State through Segment 2 ID
Action
Card Number
All Other Fields
CONTENTS
Same as Card 21
NEDS Action
22
Blanks
CARD 23:
FIELD
State through Segment 2 ID
Action
Card Number
All Other Fields
CONTENTS
Same as Card 21
NEDS Action
23
Blanks
EIS AREA SOURCE RECORDS
Table 5.2-2 (cont.)
99
-------
6.0 EMISSION FACTORS TABLE PROGRAMS
There are three EIS programs Co facilitate the creation, maintenance and
use of the emissions factors tables. These are the Emissions Factors
Table Generator, Emission Factors Transaction Generator and Emission
Factors Insert Programs.
100
-------
6.1 EMISSION FACTORS TABLE GENERATOR
The CDHS Emission factors table generator constructs a two page table
consisting of SCC numbers and their associated emission factors. The
first page contains the SCC number, the date assigned to the SCC number
and any ash and/or sulfur content percentage for that SCC number. The
table generator program will assign to each SCC number an index value
which points to the emission factors for the SCC. The emission factors
are in the second page of the table. Each emission factor entry has an
associated pollutant identification number, an emission factor units
indicator and a flag indicating whether the ash or sulfur percentage is
to be used when emission values are computed.
The emission factors table is generated from card input. There are two
types of cards and they may be arranged in any order convenient to the
user. The table capacity is 800 SCC numbers and 1200 emission factors.
The two card formats are the SCC card format (type 1) and the emission
factor card format (type 2).
101
-------
SCC Card Format
There must be one of these cards for each SCC number which is to be
entered into the table. The format is:
Cols 1-8 SCC Number
Cols 9-13 Date of SCC in Julian Format (YYDDD)
Cols 14 - 16 Ash Percentage (one assumed decimal place - XX.X)
Cols 17 - 19 Sulfur Percentage (two assumed decimal places - X.XX)
Cols 79 1
| SCC I DATE I ASH I SUL | |l |
1 89 13 14 16 17 19 79
Emission Factors Card Format
There may be from one to sixteen of these cards for each SCC number.
The format is:
Cols 1-8 SCC Number
Cols 9-13 Pollutant Identification Number
Cols 14 - 22 Emission Factor (three assumed decimal places
XXXXXX.XXX)
Col
Col
Col
| SCC
1
23
24
79
1 POLL.
8 9
Units
of Measure Code
Ash/Sulfur
2
ID |
13 14
EM.
(contains an
FACT. IUNIT
22 23
A or S)
1 A/s| \2
24 79
I
102
-------
6.2 EMISSION FACTORS TRANSACTION GENERATOR
The emission factors transaction generator will allow the user to automat-
ically update the EIS master file to reflect new emission factors according
to an SCC data criteria. This program has a single fixed format control
card as follows:
Cols 1-5 SCC Date (Julian format YYDDD)
Col 7 Mode of Operation.
The SCC date field contains a date value which is used as a lower limit
for the SCC emission factors table search. Each SCC in the emission
factors table has an associated date. When the date associated with the
SCC number in the table is equal to or chronologically later than the
date on the control card, the new factors will be inserted into the trans-
actions which are created by the transaction generator. These transactions
are then used to update the file.
The user should keep a log of SCC codes versus dates so that all necessary
emission factors may be updated. The mode of operation field should
contain an A, T or N indicating A mode, T mode or N mode of operation.
If blank the default mode is T.
103
-------
T mode: In this mode, the program examines the EF-SOURCE field of the
type 2 master file record. If this field is not T, the type 2 record
is skipped. If T, then the emission factors table is searched using the
SCO as an argument. Each pollutant identification number in the type 2
record is used to search for the emission factors associated with the SCC
number. If a previous emission factor is found, the new emission factor,
the emission factor units of measure code, and the A/S (ash-sulfur) flag
are inserted into that repetition.
N mode: In this mode, operation is identical to the T mode except that"'
the EF-SOURCE field is not examined. Therefore, this mode will insert
emission factors into all type 2 records which meet the SCC date criteria.
The pollutant identification number search is still performed.
A mode: In this mode, the EF-SOURCE field is not examined and the
pollutant identification number search is not performed. Therefore,
this mode of operation will replace all the emission factors in all
type 2 records with matching SCC codes whose SCC dates meet the date
criteria.
104
-------
6.3 EMISSION FACTORS INSERT
The CDHS emission factors insert program will search the emission factors
table using the SCC number as an argument and Insert one or more of the
associated emission factor values into EIS file maintenance transactions
prior to their input to file maintenance.
To perform this function, this program requires the EIS 21, 22 and one
or more 23 transactions. The 21 transaction contains the SCC number to
be used as the search argument. The EF-SOURCE field in the 22 transaction
may contain a blank or the character A or T. If blank, emission factors
insertion does not occur. If A or T, the program will operate in the ALL
mode or the TABLE mode respectively.
ALL mode: In this mode the program will search the emission factors table
using the SCC number in the 21 transaction as a search argument and insert
all the emission factors that are associated with this SCC number. The ALL
mode requires a single 23 transaction to immediately follow the 22 trans-
action containing the A in EF-SOURCE. The 23 transaction must contain the
key fields; the remaining fields are ignored. For each emission factor a
23 transaction will be constructed by the program from the information
supplied by the user's 23 card and from the emission factors table. The
data inserted into the 23 transaction will be the pollutant identification
number, the emission factor, the emission factor units of measure code
and the A/S ash sulfur percentage flag.
105
-------
TABLE mode: In this mode the program will search the emission factors
table using the SCC number in the 21 transaction as a search argument
and insert only those emission factors whose insertion is requested.
The TABLE Mode requires one or more 23 transactions to immediately follow
the 22 transaction containing the T in EF-SOURCE. Each 23 transaction
must contain from one to three pollutant identification numbers. The
pollutant identification number is used to search the list of emission
factors associated with the SCC number. If found the emission factor, the
emission factor units of measure code and the A/S ash sulfur percentage
flag are inserted into the 23 transaction.
106
-------
7.0 SYSTEM OPERATION
This section explains how the various components of the EIS System are
run on the computer. There are two parts to this Section. The first
explains the use of the Job Control Language (JCL) cataloged procedures
for executing each EIS component and the next gives an example of the use
of the cataloged procedures.
107
-------
7.1 CATALOGED PROCEDURES
The cataloged procedures supplied with E1S are discussed In the following
pages. The documentation of each procedure consists of the following: a
brief narrative discussing the function of the procedure and its inputs
and outputs; a block flow diagram of the data flow through the procedure;
a table of DDNAMES used by the EIS programs involved; a table of substi-
tutable parameters controlling the procedure; and a listing of the pro-
cedure itself. Non-EIS DDNAMES such as STEPLIB and those needed by COBOL
are not discussed in this section. Generally, most Input data sets
supplied by the user (control cards, etc.), are defined by the deferred
DDNAME of INPUT.
108
-------
7.1.1 EISANCNV - NEDS AREA SOURCE OUTPUT
EISANCNV is executed to output NEDS area source data from EIS file records.
The input to the program consists of an EIS file (either master or answer)
and is defined by EISF1LE. There are two output files used by the program.
The first, defined by NEDASFIL, contains the NEDS area source records
produced by the program. The second, defined by NEDASLOG, contains
diagnostic messages generated during the output process.
109
-------
NEDS Area
Source
Output
Diagnostic
Messages
NEDS
Cards
EISANCNV - Data Flow
Figure 7.1.1-1
110
-------
DD NAME
Description
EISFILE
NEDASFIL
NEDASLOG
EIS master file to be converted
Data set to contain NEDS records
Print file for diagnostic messages
EISANCNV - DDNAMES
Figure 7.1.1-2
111
-------
Parameter
Name
Default
Value
Description
PROJECT
PROGRAM
MSTRFIL
NEDSOUT
OUT
EIS
AXASNEDS
FTMSTRAA
B
A
Highest level index of data set names
(e.g., EIS.DATA.EFTABLE)
Program to convert EIS area source
file to NEDS records
Lowest level index of EIS file to be
converted
Sysout class of NEDS records
Sysout class of all print files
EISANCNV - Substitutable Parameters
Figure 7.1.1-3
112
-------
tIS CATALOGED PROCEDURES
u>
it
(D
CO
n
o
o
n>
o.
M
n>
EISANCNV
//*
//EISANCNV PROC PROJECT=E1S,
// ' PRUGRAM=AXASNcDS,
// MSTRFIL=FTMSTRAA?
// NEDSOUT=Bf
// OUT=A
//*
//CONVERT EXEC PGM=uPROGRAM,
// REGION=24K,
// TIME=(1,0)
HURLEY RF
//* CONVERT EIS AREA SOURCE FILE TO NEDS FORMAT
//*
//STEPLIb DO OSNAME=tPRUJECI. .LUAD,
// VOLUME = ( PRI VATt ,Rt TAIN) .
// DtSP=( SMK.PASS)
// DD DSNAME=SVS1 . ANS.CObSUBR.
// OISP=JSHR, PASS)
//*
//* INPUT DATA SET - EIS MASTER FILE
//*
//EISFILE 00 DSNAHE=CPRUJECT . .DATA. CMSTRF1L.
// VOLUME=IPRIVATE. RETAIN),
// DISP=( SHR.PASS)
//*
I If OUTPUT DATA SET - NEDS FILE
//*
//NfcDASFIL 00 SYSOUT=£,NEOSOUT
//* OUTPUT DATA SET - DIAGNOSTIC MESSAGES
//*
//NEDASLOG DD SYSOUT=tOUT
//*
//* OUTPUT DATA SETS - SYSTEM OPERATION
//*
//SYSPRINT DO SYSOUT=£OUT
//*
//SYSOUT DD SYSOUT=£OUT
//SYSOBOUT DO SYSOUT=COUT
//*
//SYSDTERH DD SYSOUT=£OUT
//*
//SYSUnUMP DD SYSOUT=tOUT
//*
WF4 06/30/74 00000100
00000200
OD000300
00000400
00000500
00000600
00000700
OOOC0800
00000900
OOOC1000
00001100
OD001200
00001300
00001400
00001500
03001600
00001700
03001800
00001900
00002000
00002100
00002200
00002300
00002400
00002500
00002600
00002700
00002800
00002900
00003000
00003100
00003200
OD003300
OD003400
00003500
03003600
03003700
00003800
00003900
0000400'0
00004100
00004200
OD004300
03004400
00004500
03004600
-------
7.1.2 EISANRPT - NEDS AREA SOURCE REPORT
EISANRPT is executed to produce a formatted listing of NEDS area source
records. The Input to the program consists of NEDS area source records
and is defined by NEDSFILE. There are two output files used by the pro-
gram. The first, defined by EISPRINT, contains diagnostic messages pro-
duced during the reporting process. The second, defined by NEDSPRINT,
contains the formatted listing of the NEDS records.
114
-------
NEDS Area
Cards
NEDS Area
Source
Report
Diagnostic
Messages
NEDS Area
Source
Listing
EISANRPT - Data Flow
Figure 7.1.2-1
115
-------
DDNAME
Description
NEDSFILE
NEDSPRINT
EISPRINT
NEDS Area Source Records to be Listed
Print File for Area Source Listing
Print File for Diagnostic Messages
EISANRPT - DDNAMES
Figure 7.1.2-2
116
-------
Parameter
Name
Default
Value
Description
PROJECT
PROGRAM
NEDSFIL
OUT
EIS
HXANREPT
NEDS
Highest level index of data set
names (e.g., EIS.DATA.EFTABLE)
Program to list NEDS area source
records
Lowest level index of NEDS file to
be listed
Sysout class of all print files
EISANRPT - Substitutable Parameters
Figure 7.1.2-3
117
-------
EIS CATALOGED PROCEDURES
00
00
II
ro
t
•c-
Crt
O
O
to
a
c
•i-i
to
//* EISANRPT HURLEY RF
//*
//EISANRPT PROC PRUJECT=EIS.
// PKOGRAM=HXANREPT,
// NEUSFIL=NEDS.
// OUT=A
//*
//REPORT EXEC PGM=CPROGRAM,
// REGION=40K,
// T1ME = ( 1,0)
//*
//* PRODUCE NEDS AREA SOURCE DETAIL REPORT
//*
//STEPLIB DD DSNAME=tPRUJECT. .LUAD, .
// VOLUME = ( PRIVATE, RETAIN) ,
// DISP=( SHK.PASS)
// DD DSMAME=SYS1.ANS.CUOSUBR,
// DISP=(SHR,PASS)
INPUT DATA SET - NEDS AREA SOURCE FILE
//*
//NEDSFILE DD DSNAME = CPKUJdC T . .DAT A. CNEOSF IL >
// VOLUME = 1 PRIVATt, RETAIN I,
// DI SP=( SHR.PASS)
//*
//* OUTPUT FILE - NEDS AKEA SOURCE DETAIL REPORT
//*
//NEDSPRNT DD SYSOUT=COUT
OUTPUT FILE - DIAGNOSTIC MESSAGES
//EISPRINT DD SYSOUT=COUT
//*
//* OUTPUT DATA SETS - SYSTEM OPERATION
//SYSPRINT DD SYSOUT=tOUT
//*
//SYS"OUT DD SYSOUT = tOUT
//*
//SYSD30UT DD SYSOUT=tOUT
//*
//SYSDTERM DD SYSOUT=tOUT
//SYSUDUMP DD SYSOUT=£OUT
//*
06/30/74 00000100
00000200
00000300
00000400
00000500
00000600
00000700
00000800
00000900
00001000
OD001100
00001200
00001300
OOOC1400
00001500
00001600
00001700
00001800
00001900
00002000
03002100
00002200
00002300
00002400
00002500
00002600
00002700
03CC2800
OOOC2900
00003000
00003100
00003200
00003300
00003400
00003500
00003600
00003700
00003800
00003900
00004000
00004100
OJ004200
00004300
00004400
00004500
-------
7.1.3 EISCNVRT - NEDS POINT SOURCE TO EIS
EISCNVRT is executed to convert NEDS point source records to EIS trans-
actions. The input to the conversion program consists of a NEDS point
source file and is defined by NEDSFILE. There are two output files
used by the conversion program. The first, defined by EISTRANS, contains
the EIS file maintenance transactions produced by the conversion program.
The second, defined by EISPRINT, contains diagnostic messages generated
during the conversion process.
119
-------
File
vy
NEDS Point
Source to EIS
Conversion
Diagnostic
Messages
EIS
Transactions
EISCNVRT - Data Flow
Figure 7.1.3-1
120
-------
DD NAME
Description
NEDSFILE
EISTRANS
EISPRINT
Data set containing NEDS point source records
Data set to contain generated EIS transactions
Print file for diagnostic messages
EISCNVRT - DDNAMES
Figure 7.1.3-2
121
-------
Parameter
Name
Default
Value
Description
PROJECT
PROGRAM
OUT
EIS
CXNEDSCV
Highest level index of data set
names (e.g., EIS.DATA.EFTABLE)
Program to convert NEDS point source
records to EIS transactions
Sysout class of all print files
EISCNVRT - Substitutable Parameters
Figure 7.1.3-3
122
-------
E1S CATALOGED PROCEDURES
//«•
EISCNVRT
HURLEY RF
N>
U)
00
1-1
n>
M
CO
n
^
i-i
o
o
0)
ex
c
1-1
n>
//EISCNVRT PROC PROJECT=EIS.
// PROGRAM=CXNEDSCV,
// OUT=A
//*
//CONVERT EXEC PGM=GPROGRAM,
// REGION=20K,
// TIME=ll.O)
//*
//* CONVERT NEDS POINT SOURCE RECORUS TO EIS TRANSACTIONS
//*
//STEPLIB DD DSNAME=GPROJECT..LOAD,
// VOLUME=(PRIVATE.RtTAIN),
// . DISP=(SHR,PASS)
// 'DO DSNAME=SYSl.ANS.COBSUBR.
// DISP=(SHR,PASS)
//* INPUT DATA SET - NEDS KECOKDS
//*
//NEOSFILE DD DONAME= 1 NPUT ,
// DCB=BLKS U£=80
//*
//* OUTPUT OATA SET - EIS TRANSACTIONS
//*
//EISTRANS DD ODNAME=OUT PUT
//*
'//* OUTPUT OATA SET - DIAGNOSTIC MESSAGES
//*
//fclSPRINT DD SYSOUT=COUT
//*
//* OUTPUT OATA SETS - SYSTEM OPERATION
//*
//SYSPRINT DD SYSOUT=&OUT
//SYSOUT DD SYSOUT=GOUT
//*
//SYS"OBOUT DD SYSOUT=&CUT
//*•
//SYSDTERM DD SYSOUT=tOUT
//*
//SYSUDUMP DO SYSOUT=COUT
//*
WF4 06/30/74 00000100
00000200
00000300
00000400
00000500
00000600
00000700
00000800
00000900
00001000
00001100
00001200
00001300
00001400
00001500
00001600
00001700
OOOC1800
00001900
00002000
00002100
00002200
00002300
00002400
00002500
00002600
00002700
00002800
00002900
00003000
OD003100
00003200
00003300
00003400
00003500
00003600
00003700
00003800
00003900
00004000
00004100
00004200
00004300
-------
7.1.4 EISEFGEN-EMISSION FACTORS TABLE GENERATOR
EISEFGEN is executed to generate an emission factors table. The input to
the generation program consists of emission factors table transactions and
is defined by ETBGIN. There are two output files used by the generation
program. The first, defined by ETBGTABL, contains the emission factors
table produced by the generation program. The second, defined by ETBGERR,
contains diagnostic messages generated during the emission factors table
generation process.
124
-------
Emission
Factors Table
ransactions
Emission
Factors Table
Generator
Diagnostic
Messages
Emission
Factors
Table
EISEFGN - Data Flow
Figure 7.1.4-1
125
-------
DD NAME
Description
ETBGIN
ETBGERR
ETBGTABL
Emission factor table transactions
Print file for diagnostic messages
Data set to contain emission factors table
EISEFGEN - DDNAMES
Figure 7.1.4-2
126
-------
Parameter
Default
Description
PROJECT
PROGRAM
EFTABLE
UNIT
SERIAL
DISP
SPCUNIT
PRIMARY
SECNDRY
TEMP
OUT
EIS
EXTBGN
EFTABLE
2314
009858
'NEW, CATLG,
DELETE'
TRK
SYSOUT
A
Highest level index of data set
names (e.g., EIS.DATA.EFTABLE)
Program to generate emission factors
table
Lowest level index of emission
factors table
Unit type upon which the emission
factors table is to reside
Volume serial of volume upon which
emission factors table is to reside
Disposition of emission factors
table
Units in which space for the emis-
sion factor table is to be allocated
Number of units to be allocated for
the emission factors table's
primary allocation
Number of units to be allocated for
the emission factors table's
secondary allocation
Unit type for temporary work space
Sysout class for all print files
EISEFGEN - Substitutable Parameters
Figure 7.1.4-3
127
-------
EIS CATALOGED PROCEDURES
•S
n>
00
n
o
n
(o
o.
c
i-i
n>
//* EISEFGEN HURLEY RF
//*
//EISEFGEN PROC PROJECT=EIS,
// PROGRAM=EXT3GN.
// EFTABLE=EFTABLE,
// TEMP=SYSOUT,
// UNIT=2314,
// SERIAL=009658,
// DISP='NEW,CATLG,DELETE',
// SPCUNIT=TRK,
// PRIMARY=5.
// SECNDRY=1.
// QUT=A
//*
//GENERATE EXEC PGM=CPROGRAM.
// REGION=100K.
// TIME=I1,0)
//*
//* GENERATE EIS EMISSION FACTORS TABLE
//*
//STEPLIB DD DSNAME=CPKOJECT..LOAO,
// VOLUME=IPrtIVATt,RETAIN),
// OISP=(SHR,PASS)
// 00 DSNAME=SYS1.ANS.COBSU3R,
// DISP=(SHR,PASSJ
//*
//* INPUT DATA SET - EF TABLE TRANSACTIONS
//*
//ETBGIN DD DONAME=INPUT,
// OCB=BLKSIZE=80
//*
//* INPUT DATA SET - SORT PROGRAM LIBRARY
//*
//SORTLIB DO OSNAME=SYS1.SORTLIU,
// VOLUME=(PRIVATE,RETAIN),
// DISP=(SHR.PASSJ
//*
//* UJTPUT DATA SET - DIAiiNOSTIC MESSAGES
//*
//ETBGERR 00 SYSOUT=COUT
//*
//* OUTPUT DATA SET - EMISSION FACTORS TABLE
//*
//ETBGTABL DD UNIT=CUNIT,
// VULUME=(PRlVATc,kETAIN,SER=CSERIAL),
// DISP=(tDISP).
// SPACE=(tSPCUNIT, ((.PRIMARY, tSECNDRY I, RLSE )
// DSNAME=tPROJECT..DATA.CEFTABLE
//*
//* UTILITY DATA SETS
//*
//SORTWK01 DD UNIT=£TEMP,
// SPACE=(TRK,(10,5),,CONTIG)
//*
//SORTWK02 DD UNI T=( £T EMP.SEP = SCJRTWK01),
// SPACE=(TRK,(10,5)..CONTIG)
06/30/74 00000100
00000200
00000300
00000400
00000500
00000600
00000700
oocooooo
00000900
00001000
00001100
00001200
00001300
00001400
00001500
00001600
00001700
00001800
00001900
00002000
00002100
00002200
OOOC2300
00002400
00002500
00002600
00002700
00002800
00002900
00003000
00003100
00003200
00003300
00003400
00003500
00003600
00003700
00003800
00003900
00004000
00004100
00004200
00004300
00004400
00004500
00004600
00004700
00004800
00004900
00005000
00005100
00005200
00005300
00005400
00005500
00005600
-------
EIS CATALOGED PROCEDURES
Tl
N)
VO
n>
~j
O
O
rr
M
2!
O
O
(D
Q.
C
H
0)
//*
//SURTWK03 OD UNI T=t tfEMP. SfcP= ( SURTWK01 , SORTWK02 ) ) t
// SPACE=ITRK,(10,5).,CUNTIG)
//* OUTPUT DATA SETS - SYSTEM OPERATION
//*
//SYSPRINT DO SYSOUT=tOUT
//SYSOUT DO SYSOUT=tOJT
//*
//SYSDBOUT DO SYSOUI=tOUT
//*
//SYSDTERM DO SYSOUT=COUT
//*
//SYSUOUMP DD SYSOUT=COUT
00005700
09005800
00005900
00006000
00006100
00006200
00006300
00006400
OD006500
00006600
00006700
00006800
00006900
00007000
00007100
00007200
-------
7.1.5 EISEFINS - EMISSION FACTORS INSERT
EISEFINS is executed to insert emission factors into EIS file maintenance
transactions. There are two input files used by the insertion program.
The first, defined by EFIXTIN, contains the EIS transactions into which
the emission factors are to be inserted. The second, defined by EFIXTABL,
contains the emission factors table. There are two output files used by
the insertion program. The first, defined by EFIXTOUT, contains the EIS
transactions into which the emission factors have been inserted. The
second, defined by EFIXERR, contains diagnostic messages generated
during the insertion process.
130
-------
EIS
Transactions
fei
V
Emission
Factors
Insert
4 1
" '
pdated
ransac
tions
Diagnostic
Messages
EISEFINS - Data Flow
Figure 7.1.5-1
131
-------
DD NAME
Description
EFIXTIN
EFIXTABL
EFIXERR
EFIXTOUT
EIS Transactions into which emission factors are to be
inserted
Emission factors table
Print file for diagnostic messages
Data set to contain EIS transactions into which
emission factors have been inserted.
EISEFINS - DDNAMES
Figure 7.1.5-2
132
-------
Parameter
Name
Default
Value
Description
PROJECT
PROGRAM
EFT ABLE
TRAMS
UNIT
SERIAL
DISP.
SPCUNIT
PRIMARY
SECNDRY
EIS
EXEFIX
EFTABLE
TRANS
2314
009858
'NEW, PASS,
DELETE1
TRK
Highest level index of data set
names (e.g., EIS.DATA.EFTABLE)
Program to Insert emission factors
into EIS transactions
Lowest level index of emission
factors table
Lowest level index of EIS trans-
actions
Unit type upon which the EIS trans-
actions are to reside
Volume serial of volume upon which
the EIS transactions are to reside
Disposition of EIS transactions
Units in which space for the EIS
transactions is to be allocated
Number of units to be allocated for
the EIS transactions' primary
allocation
Number of units to be allocated for
the EIS transactions' secondary
allocation
EISEFINS - Substitutable
Figure
Parameters (Sheet 1 of 2)
7.1.5-3
133
-------
TEMP
OUT
SYSOUT
A
Unit type for temporary work space
Sysout class of all print files.
EISEFINS - Substitutable Parameters (Sheet 2 of 2)
134
-------
ElS.CATALOGED PROCEDURES
OJ
"3
H
(D
.0
W
M
co
Procedure
//* EISEFINS HURLEY RF
//*
//EISEFINS PROC PROJECT=tIS.
// PROGRAM=EXEFIX,
// EFTABLE=EFTABLb.
// TEMP=SYSOUT,
// UNIT=2314,
// SERIAL=009858.
// DISP='NEH,PASS,DELETE',
// SPCUNIT=TRK,
// PRIMARY=5.
// SECNDRY=1.
// TRANS=TRANS,
// OUT=A
//*
//INSERT EXEC PGM=CPROGKAM,
// REGION=100K.
// TIKE=11.0)
//*
//* INSERT EMISSION FACTORS INTO EIS TRANSACTIONS
//*
//STEPL18 00 USNAME=CPROJECT..LOAO,
// VOLUME=(PRIVATE,RETAIN),
// DISP=fSHR.PASSJ
// DO DSNAME=SYS1.ANS.CODSUBR,
// DISP={SHR,PASSJ
//*
//* INPUT DATA SET - EIS TRANSACTIONS
//*
//EFIXTIN DO ODNAME=INPUT,
// DCB=BLKSUE = 80
//*
//* INPUT DATA SET - EMISSION FACTORS TABLE
//*
//EFIXTABL DO DSNAME = CPi
-------
EIS CATALOGED PROCEDURES
•8
H
0 UNIT=(CTEMP,SEP = SURTKK01)t
// ' SPACE=(TRK,(10,!>)..CONTIG)
//*
//SORTWK03 00 UNIT=(tTEMP.SEP=(SORTrtKOl,SORTHK02)),
// SPACE=tTRK,(10t5)..CUNTIG)
//*
//* OUTPUT DATA SETS - SYSTEM OPERATION
//* ,
//SYSPRINT 00 SYSOUT=£OUT
//*
//SYSOUT 00 SYSOUT=COJT .
//*
//SYSOBOUT 00 SYSOUT=tOUT
//*
//SYSDTERM 00 SYSOUT=COUT
//*
//SYSUOUMP oo SYSOUT=COUT
//*
00005700
00005800
00005900
00006000
00006100
00006200
00006300
00006i»00
00006500
00006600
00006700
00006800
00006900
00007000
00007100
00007200
00007300
00007*00
00007500
00007600
00007700
00007800
00007900
00008000
rl
O
8
O
o
D
-------
7.1.6 EISEFUPD - EMISSION FACTORS TRANSACTION GENERATOR
EISEFUPD is executed to update emission factors existing in the EIS master
file with new emission factors from the emission factors table. There are
three input files used by the emission factors transaction generator pro-
gram. The first, defined by EF1FMSTR, contains the EIS file to be updated.
The second, defined by EFIFTABL, contains the emission factors table. The
third, defined by EFIFIN, contains the control card which determines the
emission factors to be updated. There are two output files used by the
program. The first, defined by EFIFXOUT, contains the EIS file mainte-
nance transactions to update the emission factors in the master file.
The second, defined by EFIFERR, contains diagnostic messages generated
during the transaction generation process.
137
-------
EIS
Master
Control
Card
I
Emission
Factors
Transaction
Generator
Emission
Factors
Table
Diagnostic
Messages
EISEFUPD - Data Flow
Figure 7.1.6-1
138
-------
DD NAME
Description
EFIFIN
EFIFMSTR
EFIFTABL
EFIFERR
EFIFXOUT
Control card
EIS master file to be updated
Emission factors table
Print file for diagnostic messages
Data set to contain generated EIS transactions
EISEFUPD - DDNAMES
Figure 7.1.6-2
139
-------
Parameter
Name
Default
Value
Description
PROJECT
PROGRAM
MSTRFIL
EFTABLE
TRANS
UNIT
SERIAL
DISP
SPCUNIT
PRIMARY
SECNDRY
EIS
EXEFIF
FTMSTRAA
EFTABLE
TRANS
2314
009858
'NEW, PASS,
DELETE'
TRK
OUT
Highest level index of data set
names (e.g., EIS.DATA.EFTABLE)
Program to create EIS transaction to
update emission factors
Lowest level index of EIS master
file to be updated
Emission factors table
Lowest level index of data set to
contain generated EIS transactions
Unit type upon which the EIS trans-
actions are to reside
Volume serial of volume upon which
the EIS transactions are to reside
Disposition of EIS transactions
Units in which space for the EIS
transactions are to be allocated
Number of units to be allocated for
the EIS transactions' primary
allocation
Number of units to be allocated for
the EIS transactions' secondary
allocation
Sysout class for all print files
EISEFUPD - Substitutable Parameters
Figure 7.1.6-3
140
-------
EIS CATALOGED PROCEDURES
00
ON
I
CO
w
o
o
fD
O.
C
II*
II*
//EISEFUPO
II
II
II
II
II
It
II
II
II
II*
//EFUPOATE
II
II
II*
II* PRODUCE
II*
//STEPL1B
II
II
II
II
EISEFUPD
PROC PROJECT=EIS,
PROGRAM=EXEFIF,
MSTRFIL=FTMSTRAA,
EFTABLE=EFTAOLE,
TRANS= TRANS.
HURLEY RF
SERIAL=009658,
01SP='NEW.PASS.UELETE1 ,
SPCUNIT=TRK,
PRIMARY=5,
SECNDRY=1,
OUT = A
EXEC PGM=£PROGRAM,
REGION=80K,
TIME = ( 1,01 '
EIS TRANSACTIONS TO UPDATE EMISSION FACTORS
00 OSNAME=CPROJECT..LOAD,
VOLUME=< PR1VATE.RETAIN).
DISP=
-------
EIS CATALOGED PROCEDURES
//* OUTPUT DATA SETS - SYSTEM OPERATION
//*
//SYSPRINT 01) SYSUUT=tOUT
//*
//SYSOUT OD SYSOUT=tOUT
//*
//SYSDBOUT DO SYSOUT=tOUT
//*
//SYSDTERM DD SYSOUT = (;auT
//*
//SYSUDUMP 00 SYSOUT=GOUT
//*
00005700
00005800
00005900
00006000
00005100
00006200
00006300
00006400
00006500
00006600
00006700
00006800
00
•vj
o
§
o
o
m
a.
-------
7.1.7 EI3FUPDT - FILE MAINTENANCE
EISFUPDT is executed to perform file maintenance functions upon the EIS
master file. There are two input files used by the file maintenance pro-
gram. The first, defined by EISOLDMS, contains the EIS master file to be
updated (if any). The second, defined by EISTRANS, contains the EIS file
maintenance transactions. There are two output files used by the file
maintenance program. The first, defined by EISMASTR, contains the updated
or created EIS master file. The second, defined by EISERROR, contains
diagnostic messages generated during the file maintenance process and a
listing of the input file maintenance transactions.
143
-------
EIS
Transactions
Diagnostic
Messages
EISFUPDT - Data Flow
Figure 7.1.7-1
144
-------
DD NAME
Description
EISTRANS
EISOLDMS
EISMASTR
EISERROR
EIS transactions to update the master file
EIS master file to be updated
New EIS master file
Print file for diagnostic messages
EISFUPDT - DDNAMES
Figure 7.1.7-2
145
-------
Parameter
Name
Default
Value
Description
PROJECT
PROGRAM
OLDMSTR
NEWMSTR
UNIT
SERIAL
DISP
SPCUNIT
PRIMARY
SECNDRY
OUT
EIS
FXFILMNT
FTMSTRAA
FTMSTRAB
2314
009858
'New, Catlg,
Delete1
TRK
10
Highest level index of data set
names (e.g., EIS.DATA.EFTABLE)
EIS file maintenance program
Lowest level index of EIS master
file to be updated
Lowest level index of updated EIS
master file.
Unit type upon which new file is to
reside
Volume serial of volume upon which
new file is to reside
Disposition of new file
Units in which space for the new
file is to be allocated
Number of units to be allocated for
the new file's primary allocation
Number of units to be allocated for
the new file's secondary allocation
Sysout class of all print files.
EISFUPDT - Substitutable Parameters
Figure 7.1.7-3
146
-------
EIS CATALOGED PROCEDURES
(TO
w
1-1
CO
a
O
H
l-f
O
O
(0
(X
l-t
(D
//* EISFUPDT HURLEY RF
//*
//EISFUPDT PROC PP.OJECT = E IS ,
// PROGRAM=FXFILMNT,
// OLDMSTR=FTMSTRAA,
// NEWMSTR=FTMSTRAB,
// UN1T=2314,
// SERIAL=009858,
// DISP=fNEW,CATLG.DELETE',
// SPCUNIT=TRK,
// PRIMARY=10.
// SECNDRY=5,
// OUT=A
//*
//UPDATE EXE,C PGM=CPROGRAM,
// REGION=50K.
// T1ME=(2,0» ,
//*
//* UPDATE THE EIS DATA BASE
//*
//STEPLIB DO DSNAME=CPRUJECT..LOAD,
// VOLUME = lPRlVATt.RcTAIN) ,
// DISP=(SHR.PASS)
// DO DSNAME=SYSl.ANS.COBSUBR,
// DISP=(SHR,PASS)
//*
//A INPUT DATA SET - TRANSACTION FILE
//*
//EISTRANS UD OL)NAME=I NPUT ,
// UCB=BLKS1ZE=80
//*
//* INPUT DATA SET - OLD MASTER DATA BASE
WF4 06/30/7*
//EISOLDMS DO OSNAME=tPROJECT..uATA.tOLDMSTR,
// VOLUMES.PHIVATE.RLTAIN),
// 01SP=(SHR.PASS)
//*
//* UUTPUT DATA SET - NEW MASTER DAJA BASE
//*
//EISMASTR DO UNtT=CUNIT.
// VOLUME = ( PRlVATE,RETAIN,SER = tSERIAL ),
// D1SP=(CDISP),
// SPACE=(CSPCUNIT,(&PHI MARY,tStCNDRY ) ,RLSE),
// DSNAME=£PRUJECI..DATA.tNEWMSTR
//*
//* OUTPUT DATA SET - DIAGNOSTIC MESSAGES
//*
//EISERROR DO SYSOUT=tOUT
//*
//* OUTPUT DATA SETS - SYSTEM OPERATION
//*
//SYSPRINT DD SYSOUT=£OUT
//*
//SYSOUT OD SYSOUT=£OUT
//*
//SYSOBOUT DO SYSOUT=COUT
00000100
00000200
00000300
00000400
00000500
00000600
00000700
00000800
00000900
00001000
00001100
00001200
00001300
00001*00
00001500
00001600
00001700
OOC01800
00001900
00002000
00002100
00002200
OD002300
00002400
00002500
00002600
00002700
00002800
00002900
00003000
OD003100
00003200
00003300
00003400
00003500
00003600
00003700
00003800
OC003900
000040CO
00004100
00004200
00004300
00004400
00004500
00004600
00004700
OOC04800
00004900
00005000
00005100
00005200
00005300
00005400
00005500
00005600
-------
EIS CATALOGED PROCEDURES
//* 00005700
//SYSOTERM DO SYSOUT=£Our 00005800
//« 00005900
//SYSUDUMP DD SYSOUT=tOUT 00006000
//* OD006100
OQ
H
(D
o
o
-------
7.1.8 EISNACNV - NEDS AREA SOURCE TO EIS
EISNACNV is executed to convert NEDS area source records to EIS trans-
actions. The input to the conversion program consists of a NEDS area
source file and is defined by NEDSFILE. There are two output files used
by the conversion program. The first, defined by EISATRAN, contains the
EIS file maintenance transactions produced by the conversion program.
The second, defined by EISAERRS, contains diagnostic messages generated
during the conversion process.
149
-------
NEDS Area
Source to EIS
Conversion
Diagnostic
Messages
EIS
Transactions
EISNACNV - Data Flow
Figure 7.1.8-1
150
-------
DD NAME
Description
NEDSFILE
EISATRAN
EISAEERS
Data set containing NEDS area source records
Data set to contain generated EIS transactions
Print file for diagnostic messages
EISNACNV - DDNAMES
Figure 7.1.8-2
151
-------
Parameter
Name
Default
Value
Description
PROJECT
PROGRAM
NEDSFIL
EISOUT
OUT
EIS
CXASUMRY
NEDS
B
A
Highest level index of data set
names (e.g., EIS.DATA.EFTABLE)
Program to convert NEDS area source
record to EIS transactions
Lowest level index of data set
containing NEDS records
Sysout class of EIS transactions
Sysout class of all print files
EISNACNV - Substitutable Parameters
Figure 7.1.8-3
152
-------
£IS CATALOGED PROCEDURES
in
00
i-t
n
00
i
I
O
o
ro
o.
H
to
//* EISNACNV HURLEY RF
//*
//EISNANCV PROC PROJECT=E1S.
// PRUGRAM=CXASUMRY,
// NEDSFIL=NEDS.
// E1SOUT=B,
// OUT = A
//*
//CONVERT EXEC PGM=GPROGRAM.
// REGION=24K.
// T1ME=(1,0)
//*
//* C0^4VERT NEDS AREA SOURCE FILE TO EIS FORMAT
//*
//STEPLI3 DU DSNAME=tPROJECT..LUAD,
// VOLUME=«PRIVATC,RETAIN),
// DISP=(SHR.PASS)
// DO DSNAME = SY^1.A,\S.CD6SUBR.
// OISP=(SHR,PASS)
//*
//* INPUT UATA SET - NEDS AREA SOURCE FILE
//*
//NEDSFILE DO DSNAHE = £PXOJECT..DATA.CNEDSFIL .
// VOLUME = (PRIVATE,RETAIN ),
// DISP=(SHR.PASS)
//*
//* OUTPUT DATA SET - EIS TRANSACTIONS
//*
//EISATRAN DO SYSOUT=£EISOUT
//*
//* OUTPUT DATA SET - DIAGNOSTIC MESSAGES
//*
//E1SAERRS DD SYSOUT=CCUT
//*
//* OUTPUT DATA SETS - SYSTEM UPERATION
//*
//SYSPRINT DO SYSOUT=tOUT
//*
//SYSOUT OD SYSOUT = £LOUT
//*
//SYSDBOUT DD SYSOUT=COUT
//*
//SYSDTERM DD SYSOUT=CUUT
//*
//SYSUDUMP DO SYSOUT=£OUT
//*
06/30/7^
00000100
OD000200
00000300
00000400
00000500
OD000600
00000700
03000800
00000900
00001000
00001100
OD001200
00001300
00001400
00001500
00001600
00001700
00001800
00001900
00002000
00002100
00002200
00002300
00002400
00002500
00002600
00002700
00002800
00002900
00003000
00003100
00003200
00003300
00003400
00003500
00003600
000037CO
00003800
00003900
00004000
00004100
00004200
00004300
00004400
00004500
00004600
-------
7.1.9 EISNCONV - NEDS POINT SOURCE OUTPUT
EISNCONV is executed to produce NEDS point source data from EIS file records.
The input to the program consists of an EIS file (either master or answer)
and is defined by EISMASTR. There are two output files used by the program.
The first, defined by NEDSFILE, contains the NEDS point source records
produced by the program. The second, defined by EISPRINT, contains dianostic
messages generated during the output process.
154
-------
NEDS Point
Source
Output
Diagnostic
Messages
EISNCONV - Data Flow
Figure 7.1.9-1
155
-------
DD NAME
Description
EISMASTR
NEDSFILE
EISPRINT
EIS master file
Data set to contain generated NEDS records
Print file for diagnostic messages
EISNCONV - DDNAMES
Figure 7.1.9-2
156
-------
Parameter
Name
Default
Value
Description
PROJECT
PROGRAM
MSTRFIL
NEDSOUT
OUT
EIS
NXNEDSCV
FTMSTRAA
B
A
Highest level index of data set
names (e.g., EIS.DATA.EFTABLE)
Program to convert EIS point source
file to NEDS point source records
Lowest level index of EIS file to
be converted
Sysout class of NEDS records
Sysout class of all print files
EISNCONV - Substitutable Parameters
Figure 7.1.9-3
157
-------
EIS CATALOGED PROCEDURES
hrj Crt
3 25
TO O
C O
M Z
n> <
K
00
VO
I
O
O
(0
O.
c
l-t
n>
//* EISNCONV HURLEY RF
'//*
//EISNCONV PROC PROJECT=E1S,
// PROGRAM=NXNEDSCV,
// MSTRFtL=FTMSTRAA,
// NEDSOUT=B.
// OUT=A
//*
//CONVERT EXEC PGM=£PROGRAM,
// REGION=20K,
// TIME=«1.0>
//*
//* CONVERT EIS POINT SOUKCE FILE TO NEDS FORMAT
//STEPLIB DD DSNAME=GPROJECT..LOAU,
// VOLUME=( PRIVATE, RETAIN) ,
// DISP=(SHR,PASS)
// DD DSNAME = SYSl'. ANS.COBSUBRf
// DISP=(SHR,PASSt
//*
//* INPUT DATA SET - EIS MASTER FILE
//*
//EISMASTR DD DSNAME = tPKUJECT . .OAT A. tMSTRF IL .
// VOLUME=( PRIVATE, RtTAIN),
// DISP=( SHR.PASS)
//*
//* OUTPUT DATA SET - NEDS FILE
//*
//NEDSFILE DD SYSOUT=CNEDSOUT
//*
//* OUTPUT DATA SET - DIAGNOSTIC MESSAGES
//*
//EISPRINT DO SYSOUT=tOUT
//*
//* OUTPUT DATA SETS - SYSTEM OPERATION
//*
//SYSPRINT DO SYSOUT=tOUT
//*
//SYSOUT DD SYSOUT=tOUT
//*
//SYSOBOUT DD SYSUUT=tOUT
//*
//SYSDTERM DD SYSOUT=tOUT
//*
//SYSUDUMP DD SYSOUT=tOUT
//*
06/30/7^ 00000100
03000200
00000300
00000400
00000500
00000600
03000700
00000800
00000900
00001000
00001100
00001200
03001300
00001400
00001500
OD001600
00001700
00001800
00001900
00002000
00002100
00002200
00002300
00002400
OOC02500
00002600
00002700
03002800
00002900
00003000
03003100
00003200
03003300
03003400
00003500
03003600
00003700
00003800
00003900
03004000
00004100
03004200
00004300
03004400
00004500
00004600
-------
7.1.10 EISPREPT - FILE LIST OUTPUT
EISPREPT is executed to produce a detailed listing of an EIS file. The
input to the file list program consists of an EIS file (either ma^r.r-.r en
answer) and is defined by EISMASTR. The output from the file list pro-
gram consists of a detailed listing of each record in the file and is
defined by EISFILE.
159
-------
File List
L
File Listing
EISPREPT - Data Flow
Figure 7.1.10-1
160
-------
DD NAME
Description
EISMASTR EIS file to be listed
EISFILE Print file for EIS file listing
EISPREPT - DDNAMES
Figure 7.1.10-2
161
-------
Parameter
Name
Default
Value
Description
PROJECT
PROGRAM
MSTRFIL
OUT
EIS
PXFILPRT
FTMSTRAA
Highest level index of data set
names (e.g., EIS.DATA.EFTABLE)
Program to format and list EIS file
Lowest level index of EIS file
(master or answer) to be listed
Sysout class of all print files
EISPREPT - Substitutable Parameters
Figure 7.1.10-3
162
-------
EIS CATALOGED PROCEDURES
a\
O)
(D
O
//* F. JSPOPPT H'JP.LEY RF WF<;
'//*
//EISPREPT PROC PROJECT=EIS,
// PRCGRAM=PXFILPKT.
// MSTRFIL=FTMSrRAA.
// OUT=A
//*
//REPORT EXEC PGM=£PROGRAM,
// TIME=<1,0>,
// REGION=24K.
//*
//* FORMAT EIS MASTER FILE
//*
//STEPLIB UD DSNAME=£PROJECT..LOAD,
// VOLUME=(PKIVATb,RETAIN),
// OISP=fSHR.PASS)
// DD OSNAME=SYSI.ANS.COBSUBR,
// DISP=
-------
7.1.11 EISRETVR - RETRIEVAL
EISRETVR is executed to retrieve an answer file from the EIS master file.
The procedure consists of four separate steps.
The first step, the retrieval language processor, generates a COBOL
program to perform the actual retrieval of the answer file. The input
to the language processor consists of retrieval query cards specifying
the qualifications of the answer file to be retrieved and is defined by
CINPUT. There are two output data sets used by the language processor.
The first, defined by COUTPUT, contains the COBOL source code produced
by the language processor. The second, defined by CERROR, contains
diagnostic messages generated during the language processing process.
The second step, the COBOL compiler, compiles the source code produced
by the language processor and produces an object module which is passed
to the third step, the linkage editor. The linkage editor combines the
retriever object code with COBOL subroutines and produces an executable
load module of the retriever program.
The fourth step, the retriever, processes the EIS master file and pro-
duces the answer file. The input to the retriever consists of the EIS
master file and is defined by RINPUT. There are two output files used
by the retriever. The first, defined by ROUTPUT, contains the answer
164
-------
file produced by the retriever. The second, defined by RERROR, contains
diagnostic messages generated during the retrieval process.
165
-------
Query
Cards
^.
11 ' W
Language
Processor
t
w
Diagnostic
Messages
^
Retrieve:
Source
Code
fC_J>
Source
Code
Library
fe.
COBOL Compile
and Link
Edit
Retriever
^oad
Module
EIS
Master
File
^.
p.
Retrieval
^
w
Diagnostic
Messages
EISRETVR - Data Flow
Figure 7.1.11-1
166
-------
DD NAME
Description
CINPUT
COUTPUT
CERROR
RINPUT
RERROR
ROUTPUT
Retrieval query cards
COBOL retrieval program source code
Print file for diagnostic messages
EIS master file from which answer file is to be retrieved
Print file for diagnostic messages
Answer file retrieved from EIS master file.
EISRETVR - DDNAMES
Figure 7.1.11-2
167
-------
Parameter
Name
Default
Value
Description
PROJECT
PROGRAM
MSTRFIL
ANSWRFL
UNIT
SERIAL
DISP
SPCUNIT
PRIMARY
SECNDRY
TEMP
SORTSPC
OUT
EIS
RXCMAIN1
FTMSTRAA
ANSWER
?314
009858
'NEW, PASS,
DELETE'
TRK
SYSOUT
50
Highest level index of data set
names (e.g., EIS.DATA.EFTABLE)
Program to generate retrieval
program
Lowest level index of EIS master file
from which answer file is to be
retrieved
Lowest level index of EIS answer file
Unit type upon which answer file is
to reside
Volume serial of volume upon which
answer file is to reside
Disposition of answer file
Units in which space for the answer
file is to be allocated
Number of units to be allocated for
the answer file's primary allocation
Number of units to be allocated for
the answer file's secondary allocation
Unit type for temporary work space
Number of tracks to be allocated for
sort work space
Sysout class of all print files
EISRETVT - Substitutable Parameters
Figure 7.1.11-3
168
-------
EIS CATALOGED PROCEDURES
n>
11-4
w
Procedure
//* EISRETVR HURLEY
//*
//EISRETVR PROC PROJECT=EIS,
// PROGRAM=RXCMAIN1,
// TEMP=SYSOUT,
// SORTSPC=50.
// QUT=A,
// MSTRFIL=FTMSTRAA,
// ANSWRFL=ANSWEK.
// UNIT=2314.
// SERIAL=009858,
// OISP='NEW.PASS,DELETE',
// SPCUNIT=TRK,
// PRIMARY=10,
// SECNDRY=5
//*
//COMPILE EXEC PGM=CPROGRAM,
// REG10N=26K,
// TIME = (l.O»
//*
//* PRODUCE EIS RETRIEVAL PROGRAM
//*
//STEPLIB OD DSNAKE=CPROJECT..LOAD,
// VCJLUME = < PRIVATE, RETAIN) ,
// DISP=(SHR,PASS)
// OD DSNAME=SYS1.ANS.CUBSUBR•
// DISP=(SHR.PASS)
//*
//* INPUT DATA SET - RETRIEVAL REQUEST CARDS
//*
//CINPUT DD DDNAME=INPUT,
// DCB=BLKSHb = 80
//* OUTPUT DATA SET - COBOL RETRIEVAL PROGRAM SOURCE CODE
//*
//COUTPUT DD UNIT=tTEMP,
// DISP=(NEH.PASS),
// SPACE=«TRK,(5.2),KLSE) ,
// DSNAME=CCPROGRA«
//*
//* OUTPUT DATA SET - DIAGNOSTIC. MESSAGES
//*
//CERRUR DD SYSOUT=COUT
//*
//* OUTPUT DATA SETS - SYSTEM OPERATION
//*
//SYSPR1NT DD SYSOUT=COUT
//*
//SYSOUT OD SYSOUT=COUT
//*
//SYSOBOUT DD SYSOUT=&OUT
//*
//SYSOTERM DO SYSOUT=COUT
//*
//SYSUDUMP DD SYSOUT=tOUT
WF4 06/30/74 OD000100
00000200
00000300
00000400
00000500
00000600
00000700
00000800
00000900
00001000
03001100
00001200
00001300
00001400
00001500
OD001600
00001700
00001800
00001900
00002000
03002100
03002200
00002300
03002400
00002500
00002600
00002700
03002800
00002900
OOC03000
00003100
00003200
03003300
00003400
03003500
00003600
00003700
00003800
00003900
00004000
00004100
03004200
00004300
03004400
00004500
03004600
00004700
00004800
00004900
00005000
00005100
00005200
03005300
03005400
00005500
03005600
-------
EIS CATALOGED PROCEDURES
OQ
(t>
^J
«
M
W
g
O
o
fl>
CL
c
O
O
//COBOL EXEC PGM=tKFCBLOO,
// PARM='SIZb=94K,BUF=10K,NOSEO.NOSOURCE,FLAGEt,
// REGION=100K,
// TIM£=(2,0)
//*
//* COMPILE RETRIEVAL PROGRAM
//*
//STtPLlB DD DSNAME=SYS1.ANS.COBLIB.
// DISP=
-------
EIS CATALOGED PROCEDURES
DD DSNAME=CPRUJECT..LOAD,
VOLUME=(PRIVATE.RETAIN),
DISP=(SHR.PASS)
DO DSNAME=SYS1.ANS.COBSUBR,
VOLUMES PRIVATc.RETAIN),
D1SP=ISHR.PASS)
T!
TO
M
C/J
n
o
o
(D
D-
O
O
3
rt
•//SYSLIB
//
//
//
//
//
//*
//* INPUT DATA SET - COBUL rtfcTkltVAL PROGRAM OBJECT COOE
//*
//SYSLIN 00 DSNAM£=tC06JMOD.
// D1SP=10LD,DELETe)
// DD DONAME=INPUT,
// DCB=BLKSIZE=80
//*
//* OUTPUT DATA SET - DIAGNOSTIC MESSAGES
//*
//SYSPRINT DD SYSOUT=£OUT
//*
//* OUTPUT DATA SET - COBOL RETRIEVAL PROGRAM LOAD MODULE
//*
//SYSLMCD 00 UNIT=CT£MP,
// OISP=(MOD,PASS),
// SPACE=tTRK.(lO.b.ll),
// OSNAME=CtLJADMOO(RETRIEVE)
//*
//* UTILITY DATA SET
//*
//SYSUT1 DO UNIT=6TEMP,
// SPACE=(TRK.(10.5M
//*
//RETRIEVE EXEC PGM=*.LKED.SYSLMOD,
// REGIUN=40K,
// TIME=(1.0)
//*
//* RETRIEVE RECORDS FROM EIS MASTER FILE
//*
//STEP"LIB 00 DSNAME = £PKOJECT. .LOAD,
// VOLUME=(PRIVATE.RETAIN I,
// DISP=(SHR,PASS)
// 00 DSNAME=SYS1.ANS.COBSU6R.
// D1SP=(SHR,PASS)
//*
//* INPUT DATA SET - EIS MASTLR FILE
//*
//RINPUT 00 DSNAME=£PROJECT..OATA.tMSTRFIL.
// VOLUME = (PRIVATE.Kb TAIN) ,
// DISP=(SHR,PASS)
//*
//* INPUT DATA SET - SORT PROGRAM LIBRARY
//*
//SURTLIB .DD DSNAME=SYS1.SORTLIB,
// VOLUME=
-------
E1S CATALOGED PROCEDURES•
//RERRQR
•5
i-i
re
w
M
W
B
N>
(-• >Ti
I-J
!-• O
M O
i re
4S |x
'x-x H
o re
§
00 SYSOUT=£OUT
//* OUTPUT DATA SET - RECORDS RETRIEVEO FROM EIS MASTER FILE
//*.
//ROUTPUT DO UNIT=£UNIT ,
// VOLUME=
-------
7.1.12 EISSREPT - SUMMARY REPORT OUTPUT
EISSREPT is executed to produce a summary report of an EIS file (either
master or answer). The procedure consists of three separate steps.
The first step, the COBOL compiler, compiles the skeleton summary pro-
gram with user supplied control cards. The input to the COBOL compiler
consists of COBOL statements controlling the breaks in the report to be
produced. The output from the COBOL compiler consists of an object
module which is passed to the second step, the linkage editor. The
linkage editor combines the summary program object code with COBOL sub-
routines and produces an executable load module of the summary report
program.
The third step, the summary report program, generates the summary of the
EIS file. There are two input files used by the summary program. The
first, defined by SUMCARDS, contains the control cards for the titling of
the report. The second, defined by EISFILE, contains the EIS file to be
summarized. There are two output files used by the summary program.
The first, defined by CARDLOG, contains the control card log. The second,
defined by SUMFILE, contains the summary report of the EIS file.
173
-------
s
Break
Control
Cards
It
w
COBOL
Compiler
/ ^
/Source
\Library
unnnary
Program
Object
Linkage
Editor
Summary
rogram
Load
\ t
1 ' W
EIS File
Summary
Program
'Summary
Control
Cards
File Summary
Report
Control
Card Log
EISSREPT - Data Flow
Figure 7.1.12*-!
174
-------
DD NAME
Description
SUMCARDS Control cards for summary report
ElSFILE EIS file to be summarized
CARDLOG Print file for control card log
SUMFILE Print file for summary report
EISSREPT - DDNAMES
Figure 7.1.12-2
175
-------
Parameter
Name
Default
Value
Description
PROJECT
MEMBER
M2
M3
MA
M5
M6
MSTRFIL
TEMP
OUT
EIS
BDSUMARY
BDFILSEC
BDWORK77
BDWORK01
BDRPTSEC
BPSUMARY
FTMSTRAA
SYSOUT
Highest level index of data set
names (e.g., EIS.DATA.EFTABLE)
Name of first member of summary
program
Name of second member
Name of third member
Name of fourth member
Name of fifth member
Name of sixth member
Lowest level index of EIS file to
be summarized
Unit type to be used for temporary
workspace
Sysout class for all print files
EISSREPT - Substitutable Parameters
Figure 7.1.12-3
176
-------
EIS CATALOGED PROCEDURES
3
N>
I
//* EISSREPT HURLEY RF
//*
//ESISREPT PROC PROJECT=EIS,
// ' TEMP=SYSOUT,
// MSTRFIL-FTMSTRAA,
// MEMBER=BDSUMARY,
// M2=BOFILSEC,
// M3=BDWORK77,
// M5=BDRPTSEC.
// M6=BPSUMARY.
// OUT=A
//*
//COMPILE EXEC PGM=IKFCBLOO,
// PARM=«SIZE=94K,BUF=10K.NOSEO.NOSOURCEt,
// REGION=100K,
// TIME=(2.0)
//*
//* COMPILE EIS SUMMARY PROGRAM
//*
//STEPLIB DD OSNAME=SYS1.ANS.COBL1B.
// DISP=ASS)
//*
//* INPUT DATA SET - COBOL SUMMARY PROGRAM SOURCE CODE
//*
DO DSNAME=CPROJECT..SOURCE(CMEMBER),
VOLUMESPKIVATk.KbTAIN),
DISP=(SHR,PASS)
//SYSIN
II
II
//*
II
II
//*
II
II
U
//*
II
II
II
//*
II
II
II
II*
II
II
II
//*
II
DD DSNAMES&PROJECT..SOURCEUM2).
VOLUME=(PRIVATE,RETAIN),
OISP=(SHR,PASS)
DO DSNAME=6PROJECT..SOUKCE(CM3J,
VOLUME=(PRIVATE,RETAIN),
DISP=(SHR,PASS)
DD DSNAME=CPRUJECT..SOURCE!CM4),
VOLUME=(PRIVATE.RtTAINl,
DISP=(SHR,PASS)
DD DSNAME-CPRUJECT..SUURCEI&M5I.
VOLUME=(PRIVATE.RETAIN).
OISP=(SHR,PASS)
DD DSNAME-CPRUJECT..SOURCE(CM6I,
VOLUME=(PRIVATE,RETAIN),
DISP=ISHR,PASS)
i)D ODNAME=INPUT,
WF4 06/30/7A 00000100
00000200
00000300
03000400
00000500
00000600
03000700
OOOOOBOO
00000900
00001000
00001100
03001200
03001300
00001400
03001500
03001600
00001700
03001800
03001900
00002000
00002100
03002200
03002300
00002400
00002500.
00002600
03002700
00002800
00002900
00003000
03003100
00003200
00003300
03003400
00003500
00003600
03003700
00003800
00003900
00004000
00004100
03004200
00004300
00004400
03004500
00004600
OOOO4700
03004800
00004900
00005000
03005100
00005200
00005300
00005400
00005500
03005600
-------
EIS CATALOGED PROCEDURES
TJ M
H- M
OQ CO
e co
1-1 pa
// DCB=8LKSIZE=80
//*
//* OUTPUT DATA SET - DIAGNOSTIC MESSAGES
//*
//SYSPRINT DD SYSOUT=COUT
//*
//* OUTPUT DATA SET - COBOL SUMMARY PROGRAM OBJECT CODE
//*
//SYSLIN DD UNIT=£TEMP.
// DISP=(NEW,PASS),
// SPACE=(TRK,I 5,2),RLSE) ,
// DSNAME=tCOBJMOO
//*
//* UTILITY DATA SETS
//*
//SYSUTi bU UNIT=£TEMP,
// SPACE=(TRKV.( 50, 100) )
//*
//SYSUT2
//*
//SYSUT3
//SYSUTI
•
I-1
1
^^\
o
o
'rocedui
1 >
ro
/ /
//*
//LKED
/ /A
00 UNIT=(GTEMP.SEP=SYSUT1),
SPACE=(TRK,(50,100))
00 UNIT=(tTEMP,SEP=(SYSUTl,SYSUT2»)t
SPACE=
-------
EIS CATALOGED PROCEDURES
TO
C
-J
O
o
3
W
co
H
o
o
n>
s-
1-1
ffi
//*
//SYSLMOO OD UNlT=tTEMP,
// DISP=(MOD,PASS),
// SPACE=(TRK,UO,5,l)) .
// DSNAME = ttLOADML)D(SUMMARY)
//*
//* UTILITY DATA SET
//*
//SYSUT1 OD UNIT=CTEMP,
// SPACE=(TRK,<10,5M
//*
//SUMMARY EXEC PGM=*.LKEO.SYSLMOO,
// REGION=30K.
// TIME=(1,0)
//*
//* PRODUCE EIS SUMMARY R.6PORT
//*
//STEPLIB OD DSNAME=CPROJECT..LOA[),
// VOLUME=(PR1VATE,RETAIN).
// DISP=(SHR,PASSI
// OD DSNAME=SYSl.ANS.CO^SUaR,
// DISP=(SHR.PASS)
//*
//* INPUT DATA SET - CONTROL CARDS
//*
//SUMCAROS 00 DDNAME=INPUT,
// OCB=8LKSIZE=80
//* INPUT DATA SET - EIS MASTER FILE
//*
//EISFILE 00 DSNAME=tPRUJECT..DATA.tMSTRFIL,
// VOLUME=
-------
7.2 USE OF CATALOGED PROCEDURES
The following section gives an example of how to use the cataloged pro-
cedures. The sample run described In this section creates an EIS master
file, retrieves an answer file from It, lists the answer file and pro-
duces a summary report. Figure 7.2-1 Illustrates the job control cards
required to perform this run.
The first step creates an EIS master file named EIS.DATA.FTMSTRAA. Since
the file is being newly created rather than updated, the DDNAME EISOLDMS
is nullified with a DD DUMMY statement to indicate that no old master file
exists. The file maintenance transactions must consist entirely of "Add"
transactions. After the file has been created, it is cataloged by the
JCL so that it may be referred to by succeeding steps without supplying
specific location information.
The second step Involves the retrieval language processor to read the
queries and generate a retriever program. The program will be compiled
with the parameters specified on the EXEC card rather than those in the
procedure. An answer file named EIS.DATA.ANSWER will be produced and
passed to later steps. It may be referred to by succeeding steps as if
it has been cataloged. However, it will be deleted at the end of the job.
Step three invokes the file list program to list the answer file.
180
-------
The final step merges the COBOL break control statements with the skeleton
summary report program and compiles it. Again the parameters used during
compilation will be overridden by the EXEC statement. The control cards
defined by SUMMARY.INPUT will control the titling of the summary report.
181
-------
//STEP1 EXEC EISFUPDT,
// NEWMSTR-FTMSTRAA
//UPDATE.EISOLDMS DD DUMMY
//UPDATE.INPUT DD *
(EIS file maintenance transactions)
/*
//STEP2 EXEC EISRETVR
//COMPILE.INPUT DD *
(EIS retrieval queries)
/*
//STEP3 EXEC EISPREPT
MS TRFIL»ANSWER
//STEP4 EXEC EISSREPT,
// MSTRFIL=ANSWER
//COMPILE.INPUT DD *
(COBOL break control statements)
/*
//SUMMARY.INPUT DD *
(EIS summary report control cards)
/*
Sample EIS Job Stream
Figure 7.2-1
182
-------
APPENDIX
This appendix presents sample system runs. In the samples the transactions,
files, and tables are represented as residing on disk, tape and card and are
shown changing media during and between runs. This is not a system require-
ment but is mearly to indicate the flexibility of external data storage. The
following is not an exhaustive list of possible system program combinations
but is a sample of possible uses.
Figure A-l shows a system start up run. There are no existing files for the
Emission Factor Table, or the Master File. The first step is to create an
Emission Factor Table using program EXTBGN. The table can then be used to
insert the new Emission Factors into EIS transactions. The NEDS Point Source
Transactions are run through program CXNEDSCV to convert them to the EIS
input transaction format. The NEDS transaction cards are put into a hold
file.
The new EIS transactions can now be used as input to program EXEFIX which
will use the Emission Factor Table to insert the emission factors into the
transactions. These updated EIS transactions can then be used to create a
master file using program FXFILMNT. Notice that there is no old master file
being used in this run.
Figure A-2 shows the conversion of NEDS Area Source Transactions into EIS
transactions using program CXASUMRY. The EIS transactions are then run
through program EXEFIX. In this run, since the Emission Factor Table
already exists, we use it to insert the emission factors into the EIS
transactions.
183
-------
The new transactions are now used to update the existing Master File using
FXFILMNT. The old master file should be kept until the next update has been
run. This will provide a backup file in case anything happens to the current
master file. At this point the master file may be listed using program
PXFILPRT. The formatted listing provides a further backup for the file.
The entire file should be listed periodically to provide current file status
checks.
Figure A-3 shows the retrieval program (RXCAMAIN1) being used to select the
Area Source records from the master file. The File Print Program PXFILPRT
is used to print a formatted listing of the Answer File. The program AXSNEDS
used the Answer File and produces the NEDS Area Source Cards. The Area Source
cards may be listed using program HXANREPT which produces a formatted list of
the NEDS formats.
Figure A-4 shows the retrieval program RXCMAIN1 being used to select the Point
Source records from the master file. The answer file from this retrieval is
then listed using program PXFILPRT. The answer set is then used as input to
program NXNEDSCV which converts it to NEDS Point Source Cards. The NEDS
cards can then be used to file the quarterly NEDS report.
Figure A-5 shows the retrieval program RXCMAINl being used to select a set
of data based on the requirements of the Request Cards. A formatted detail
listing of the answer set is produced by program PXFILPRT. The information
in the answer set is summarized by program EISSREPT to produce the EIS
Summary Report.
Figures A-6 through A-8 are the EIS card input forms for point source data.
ISA
-------
Emission
Factor
Transactions
• NEBS Point
Source
Transactions
NEDS Point
Source
Transactions
Old EIS
Point Source
Transactions
V
Figure A-l
185
-------
_\
tfEDS Area
I Source
Transactions
[NEDS Area
Source
Transactions
fC ^^
Emissior
Factor
Table
w
W
l_ EXEFIX
'Emission
Factor
Insertion
k
W
Diagnostic
Messages
EIS Area
Source
Trans
Master
File
h.
1
r
FXFILMNT
File
Maintenance
Program
1
Diagnostic
Messages
^—^~^
aid
Master
File
New
Master
File
^
W
PVVT1 PUT
File
Print
Program
fc
W
Formatted
File Listing
I ^
Master
File
Figure A-2
186
-------
r Retrieval
Request
Cards
Formatted
File Listing
AXASNEDS
5IS to NEDS
krea Source
Conversion
1
r
— fc
P
Diagnostic
Messages
/NEDS\
/ Area \_
I Source J
\Cards/
Formatted
NEDS Area
Source list
Figure A-3
187
-------
t Retrieval
Request
:ards
strieval
IRequest
Cards
PXFILPRT
File
Print
Program
t
Formatted
File Listing
NXNEDSCV
EIS to NEDS
Point Source
Conversion
1
r
t
Diagnostic
Messages
NEDS Point
Source
Cards
Figure A-4
188
-------
r Retrieval
Request
Cards
trieval
Request
Cards
RXCMAIN1
Retrieval
Program
Diagnostic
Messages
V
Answer
File
PXFILPRT
File
Print
Program
fc,
W
Formatted
File Listing
taswer
file
EISSREPT
Summary
Report
Summary
Report
Figure A.-5
189
-------
Si
1
••
2
to.
fifV
AOCf
Ptonl ID
NumtW
0m
Of RMord
lnv
EMISSION INVENTORY SUBSYSTEM (ElSl
COMPREHENSIVE DATA HANDLING
SYSTEM (CDHS) PLANT IOCNTIFICATION
N*m« o* Per»on
Competing Form,
Control
togon
It 20 21
IOC4I
Control
22 21
UMT Pl»m IO
24 2* 2* ! 21 ^ 2i 21 JO 31 J2 33 M »
C.IY
M 17 18 M
UTM
40 41
-
» rroaucl
! 1
•
0
c
1
A
•n
H-
00
C
10
11 [20
It 1 20
?1
!'
Etl4bll»hm«nl HMtrtf ma Adrjnnt
«.,- «^«.»
1
NwffltMr of
Enuiui.ii
• 7 li It 70
Prop4ny»r
71 72 71 ; 74
M
tin
I
77
•
•
79
0
s
0
C
7>
2
C
3
*
•0
I
-------
s»
1
1«
Ccx
nly
AOC
!
j''*UVr
D»M of ftocofd
YMf | Day
14 15_L 17 1.
t ! :
EMISSION INVENTORY SUBSYSTEM (EISI
COMPREHENSIVE DATA HANDLING
SYSTEM ICOHS)
POINT SOURCE
ISogmori 1)
Input Fnrm
Name of Person
Completing Fofm_
^
19
1'
20
f
NCOS
21 ! 22
Mnt ID
UOT
23 : 24 I 25
SIC
26 27 28 29
IPP
30 31
UT»
Horuonlal
32 33 34 35
A
Vwtiuri
36 37 38 39 40
A
°~>
41 42
L«t
-------
SUM
1
County
AOCP.
Plant ID
NumMr
10
11
IJ
13
D««
Vaar
14 IS
of Racord
Da.
!•' 17
II
V
ii
20
•a*
21
22
1
23
,
24
K
sec
III
2i
27
21
IV
29
JO
HC
10
j
•ffi'
It
20
•B'
Jl
22
<
J
23
i
> .
24
j;
EMISSION INVENTORY SUBSYSTEM IEISI
COMPREHENSIVE DATA HANDLING
SYSTEM ICOHS)
Machirve - PTOCMS
(•MMMM21
FU* PTOC.M
SoM W4WH
Ofwr»t*ng KM*
Mai.mum Dmv
iM
Sovrca DaacnDtoon
»
28
27
21
25
30
t
J2
BO
5
>>
i
^'
19
20
V
21
22
Mutant
ID
23
24
2S
26
27
!_*_.
•
25
X 11 32 33 34 »
! ™ !
: A .
M
|j
37
• "
M
ID
M 40 41 4? 43
EmMMn FBCKM
44 46 4t 47 41 49
j
Conlv
i
s
1 -
So'&l S2
. . .
C
9nMm
A.
t *
S3
J"
M
P
55 S6
MM
COMWM
57 5« 59
tO*°
60 61
•2 *3 «4 <8 M [ §7
DM
H
EnwMion Factor
. A
A
• 9
70|71
70 71
k- —
• :
i
72
72
•
7J
7
2
c
1
•
•
73
•
•
2
e
2
A
•
•
I
2
C
«
3
A
4)
------- |