EPA-454/B-94-007
AIRS User's Guide
Volume AQ3:
Air Quality Data Storage
U. S. Environmental Protection Agency
Office of Air Quality Planning and Standards
Technical Support Division
National Air Data Branch
Research Triangle Park, North Carolina 27711
February 1994
-------
AIRS User's Guide
Air Quality Data Storage Volume AQ3
Table of Contents
1.0 Introduction 1-1
2.0 AQ Data Storage Overview 2-1
3.0 General Operational Procedures 3-1
3.1 Registration and Equipment Requirements 3-1
3.2 Screening Files 3-2
3.3 General Conventions and Procedures 3-5
3.3.1 Standard PF Keys 3-5
3.3.2 Other Special Keys 3-5
3.4 AIRS Logon Procedures 3-7
3.4.1 TCP Logon 3-7
3.4.2 EPA Computer System Logon 3-9
3.4.3 CICS Logon 3-12
3.4.4 Invoking AIRS 3-15
3.5 AIRS Logoff Procedures 3-17
3.5.1 CICS Logoff 3-17
3.5.2 TCP Disconnect 3-17
3.6 AIRS AQS Top Level User Procedures 3-19
3.6.1 AIRS Main Menu 3-21
3.6.2 User Profile Screen - Description 3-23
3.6.3 User Profile Screen - Usage 3-25
3.6.4 AIRS AQS Main Menu 3-27
3.6.5 AQ Data Storage Submit Menu 3-29
3.6.6 Batch Job Submission 3-33
3.6.7 Error Handling 3-35
3.7 Batch Processing 3-37
3.7.1 Checking Batch Job Status 3-37
3.7.2 Checking Batch Job Output 3-39
3.8 Checking Batch Jobs With SYSD 3-43
3.8.1 Invoking SYSD 3-43
3.8.2 The SYSD Primary Option Menu 3-43
3.8.3 Setting Your SYSD Profile 3-45
3.8.4 SYSD Job Queue Display Screen - Description 3-47
3.8.5 SYSD Job Queue Display Screen - Usage 3-48
3.8.6 SYSD Job Queue Display Screen - Functions 3-49
3.8.7 SYSD Job Output Display Screen - Description 3-51
3.8.8 SYSD Job Output Display Screen - Usage 3-53
3.8.9 SYSD Job Output Display Screen - Functions 3-54
3.8.10 SYSD Job Dataset Display Screen 3-56
3.8.11 SYSD Spool Display Screen 3-58
3.8.12 Terminating SYSD 3-60
Table of Contents ii September 1993
-------
AIRS User's Guide
Volume AQ3 Air Quality Data Storage
3.9 Checking Batch Jobs With SDSF 3-61
3.9.1 Invoking SDSF 3-61
3.9.2 The SDSF Primary Option Menu 3-61
3.9.3 Job Selection Options 3-63
3.9.4 SDSF Job Status Display Screen 3-35
3.9.5 SDSF Input Queue Display Screen 3-67
3.9.6 SDSF Output Queue Display Screen 3-69
3.9.7 The SDSF Job Dataset Display Screen 3-71
3.9.8 The SDSF Output Display Screen 3-71
3.9.9 Terminating SDSF 3-73
3.9.10 Ending Your TSO Session 3-73
4.0 The LOAD Process 4-1
4.1 Overview 4-1
4.1.1 Record Reformatting and Initialization 4-3
4.1.2 Validation of Important Fields 4-3
4.1.3 Interactions Among Records 4-4
4.2 Data Submission Procedures 4-6
4.2.1 Transaction Record Format 4-6
4.2.2 Transaction File Medium 4-6
4.2.3 Transaction File Format 4-6
4.2.4 Tape Submission 4-7
4.2.5 Screening File Selection 4-7
4.3 LOAD Initiation Procedures 4-8
4.3.1 User Profile Screen 4-8
4.3.2 AIRS AQS Main Menu 4-8
4.3.3 AQ Submit Menu 4-11
4.3.4 LOAD Job Submission Screen 4-11
4.3.4.1 Screen Description 4-11
4.3.4.2 Screen Usage 4-15
4.3.5 LOAD Restart Screen 4-18
4.3.5.1 Screen Description 4-18
4.3.5.2 Screen Usage 4-18
4.3.5.3 Restart Precautions 4-19
4.3.6 LOAD Job Submission . 4-20
4.4 LOAD Validation Procedures 4-22
4.4.1 Using the MESSAGE Process 4-22
4.4.2 Using LOAD Printed Output 4-24
4.5 LOAD Follow-Up Procedures 4-28
4.6 Restrictions, Limitations, and Warnings 4-29
September 1993 iii Table of Contents
-------
AIRS User's Guide
Air Quality Data Storage Volume AQ3
5.0 The EDIT Process 5-1
5.1 Overview 5-1
5.1.1 Edit Levels and Edit Checks 5-3
5.1.2 Modification of Screening Records 5-4
5.2 EDIT Initiation Procedures 5-6
5.2.1 User Profile Screen 5-6
5.2.2 AIRS AQS Main Menu 5-6
5.2.3 AQ Submit Menu 5-8
5.2.4 EDIT Job Submission Screen 5-8
5.2.4.1 Screen Description 5-8
5.2.4.2 Screen Usage 5-12
5.2.5 EDIT Job Submission 5-14
5.3 EDIT Validation Procedures 5-16
5.3.1 Using the MESSAGE Process 5-16
5.3.2 Using EDIT Printed Output 5-18
5.4 Interpreting EDIT Reports 5-21
5.4.1 EDIT Summary Report 5-23
5.4.2 EDIT Error Report 5-25
5.4.3 EDIT Patterns and Gap Failure Report 5-27
5.4.4 EDIT Shewhart Failure Report 5-29
5.5 EDIT Follow-Up Procedures 5-30
5.6 Restrictions, Limitations, and Warnings 5-31
6.0 The CORRECT Process 6-1
6.1 Overview 6-1
6.2 CORRECT Features 6-4
6.2.1 Screening File Access 6-4
6.2.2 Modes of Operation 6-6
6.2.3 Exclusion Status 6-7
6.2.4 Edit Checks 6-9
6.2.5 Related Transactions 6-10
6.2.6 Screen Types 6-13
6.2.7 Commands and PF Keys 6-14
6.2.8 Screening File Updating 6-15
6.3 CORRECT Initiation Procedures 6-17
6.3.1 User Profile Screen 6-17
6.3.2 AIRS AQS Main Menu 6-17
6.3.3 AQ Submit Menu 6-17
6.4 CORRECT Operational Procedures 6-19
6.4.1 Initial Screen 6-19
6.4.2 Normal Mode 6-21
6.4.2.1 General 6-21
6.4.2.2 Directives for Accessing Records 6-23
6.4.2.3 Other Normal Mode Directives 6-27
Table of Contents iv September 1993
-------
AIRS User's Guide
Volume AQ3 Air Quality Data Storage
6.4.3 Input Mode 6-29
6.4.3.1 Selecting a Transaction Type 6-29
6.4.3.2 Entering Transaction Data 6-29
6.4.3.3 Input Mode Directives 6-30
6.4.4 Global Mode 6-33
6.4.4.1 Specifying Selection Criteria 6-33
6.4.4.2 How CORRECT Selects Records 6-34
6.4.4.3 Specifying Global Changes 6-37
6.4.4.4 How CORRECT Processes Records In Global Mode 6-40
6.4.4.5 The End of a Global Command 6-41
6.4.5 Summary of CORRECT Directives 6-44
6.4.6 Error Handling 6-49
6.5 CORRECT Follow-Up Procedur.es , 6-54
6.6 Restrictions, Limitations, and Warnings 6-55
7.0 The NOTIFY Process 7-1
7.1 Overview 7-1
7.1.1 Authority To Use NOTIFY 7-3
7.1.2 Screening File Status 7-3
7.1.3 NOTIFY Protects Your Screening File 7-3
7.1.4 NOTIFY Protects the Database 7-4
7.2 NOTIFY Initiation Procedures 7-6
7.2.1 User Profile Screen 7-6
7.2.2 AIRS AQS Main Menu 7-6
7.2.3 AQ Submit Menu 7-6
7.3 NOTIFY Operational Procedures 7-8
7.3.1 NOTIFY Menu 7-8
7.3.2 NOTIFY Error Screen 7-13
7.4 NOTIFY Follow-Up Procedures 7-14
7.5 Restrictions, Limitations, and Warnings 7-15
8.0 The MESSAGE Process 8-1
8.1 Overview 8-1
8.2 MESSAGE Initiation Procedures 8-4
8.2.1 User Profile Screen 8-4
8.2.2 AIRS Main Menu 8-4
8.2.3 AQ Submit Menu 84
8.3 MESSAGE Operational Procedures 8-6
8.3.1 The MESSAGE Screen 8-6
8.3.2 The "No Messages" Screen 8-10
8.4 MESSAGE Follow-Up Procedures 8-12
8.5 Restrictions, Limitations, and Warnings 8-13
September 1993 T Table of Contents
-------
AIRS User's Guide
Air Quality Data Storage Volume AQ3
9.0 The DELETE Process 9-1
9.1 Overview 9-1
9.2 DELETE Initiation Procedures 9-4
9.2.1 User Profile Screen 9-4
9.2.2 AIRS Main Menu 9-4
9.2.3 AQ Submit Menu 9-6
9.2.4 DELETE Job Submission Screen 9-6
9.2.4.1 Screen Description 9-6
9.2.4.2 Screen Usage 9-9
9.3 Batch Job Submission 9-10
9.4 DELETE Validation Procedures 9-12
9.4.1 Using the MESSAGE Process 9-12
9.4.2 Using DELETE Printed Output 9-14
9.5 DELETE Follow-Up Procedures 9-18
9.6 Restrictions, Limitations, and Warnings 9-19
10.0 Archiving and Dearchiving Data 10-1
10.1 Background 10-1
10.2 Procedures 10-2
10.2.1 Dearchiving 10-2
10.2.2 Archiving 10-2
11.0 Update Processes 11-1
11.1 Overview 11-1
11.2 SCAN 11-2
11.2.1 Overview 11-2
11.2.2 The SCAN Summary Report 11-6
11.2.3 The SCAN Detail Report 11-8
11.2.4 The SCAN Inventory Report 11-10
11.2.5 The SCAN Current and Old NAMS Reports 11-12
11.2.6 The SCAN Non-NAMS Criteria Report 11-14
11.2.7 The SCAN Excluded SLAMS Data Report 11-16
11.2.8 The SCAN SLAMS Report 11-18
11.2.9 The SCAN Precision and Accuracy Report '.' 11-20
11.2.10 The SCAN NAMS/SLAMS Site/Monitor Update Report 11-22
11.3 EXCLUDE , 11-23
11.4 ARCHIVE and DEARCHIVE 11-24
11.5 UPDATE .' 11-27
Table of Contents vi September 1993
-------
AIRS User's Guide
Volume AQ3 Air Quality Data Storage
12.0 BROWSE Screening File Transaction Generate Option 12-1
12.1 Overview 12-1
12.2 Detailed Instructions 12-4
12.2.1 Selecting a Screening File 12-4
12.2,2 Requesting the Transaction Generate Option 12-4
12.2.3 Entering Site or Monitor Selection Criteria 12-4
12.2.4 Generating Transactions 12-4
12.2.4.1 Creating Delete Transactions 12-5
12.2.4.2 Creating Insert Transactions 12-5
12.2.4.3 Creating Modify Transactions 12-5
September 1993 vii Table of Contents
-------
AIRS User's Guide
Air Quality Data Storage Volume AQ3
List of Figures
Figure 2-1. The Primary AIRS Subsystems and Relevant User's Guide Volumes 2-2
Figure 2-2. Processes of the Air Quality Data Storage Subsystem 2-3
Figure 2-3. Initiation of Online and Batch Data Storage Processes 2-5
Figure 3-1. Naming Convention for AIRS Screening Files 3-3
Figure 3-2. Sample TCP Logon Session 3-6
Figure 3-3. Using the EPA Logon Screens 3-8
Figure 3-4. News Alert & User Memo Screens 3-10
Figure 3-5. Using the CICS Logon Screen 3-11
Figure 3-6. Invoking AIRS from CICS 3-14
Figure 3-7. CICS Logoff Screens 3-16
Figure 3-8. Hierarchical Relationships Among AIRS Processes 3-18
Figure 3-9. The AIRS Main Menu 3-20
Figure 3-10. The AIRS AQS User Profile Screen 3-22
Figure 3-11. The AIRS AQS Main Menu 3-24
Figure 3-12. The AQ Data Storage Subsystem (Submit) Menu 3-26
Figure 3-13. Using the AQ Data Storage Submit Menu 3-28
Figure 3-14. The AIRS Error Screen 3-30
Figure 3-15. Job Disposition (Error) Screen 3-31
Figure 3-16. Job Number Screen 3-32
Figure 3-17. Sample MESSAGE Screen 3-36
Figure 3-18. Sample Batch Job Log and Step Summary Reports 3-38
Figure 3-19. Sample LOAD Summary Reports 3-40
Figure 3-20. Sample EDIT Summary Reports 3-41
Figure 3-21. SYSD Primary Option Menu 3-42
Figure 3-22. Specifying SYSD Job Selection Parameters 3-44
Figure 3-23. The SYSD Job Queue Display Screen (Option 5) 3-46
Figure 3-24. The SYSD Job Output Display Screen (Option 6) 3-50
Figure 3-25. The SYSD Job Dataset Display Screen 3-55
Figure 3-26. The SYSD Spool Display Screen 3-57
Figure 3-27. The SDSF Primary Option Menu 3-62
Figure 3-28. Specifying SDSF Job Selection Criteria 3-64
Figure 3-29. The SDSF Job Status Display Screen 3-66
Figure 3-30. The SDSF Input Queue Display Screen 3-68
Figure 3-31. The SDSF Output Queue Display Screen 3-70
Figure 3-32. The SDSF Job Dataset Display and Output Display Screens 3-72
Figure 4-1. LOAD Data Flow Diagram 4-2
Figure 4-2. AIRS AQS User Profile and Main Menu Screens 4-8
Figure 4-3. The LOAD Job Submission Screen 4-10
Figure 4-4. The LOAD Job Submission Screen Showing an Error Message 4-14
Figure 4-5. The LOAD Job Number Screen 4-16
Figure 4-6. The LOAD Restart Screen 4-17
Figure 4-7. Sample MESSAGE Screen Showing LOAD Messages 4-21
Table of Contents viii September 1993
-------
AIRS User's Guide
Volume AQ3 Air Quality Data Storage
Figure 4-8. Sample LOAD Summary Reports for Successful Jobs 4-23
Figure 4-9. Sample LOAD Summary Reports for Failed Jobs 4-25
Figure 5-1. EDIT Data Flow Diagram 5-2
Figure 5-2. AIRS AQS User Profile and Main Menu Screen 5-5
Figure 5-3. The EDIT Job Submission Screen 5-7
Figure 5-4. The EDIT Job Submission Screen Showing an Error Message 5-11
Figure 5-5. The EDIT Job Number Screen 5-13
Figure 5-6. Sample MESSAGE Screen Showing EDIT Messages 5-15
Figure 5-7. Sample EDIT Summary Reports for Successful and Failed Jobs 5-17
Figure 5-8. The EDIT Summary Report 5-22
Figure 5-9. The EDIT Error Report 5-24
Figure 5-10. The EDIT Patterns and Gap Failure Report 5-26
Figure 5-11. The EDIT Shewhart Failure Report 5-28
Figure 6-1. CORRECT Data Flow Diagram 6-2
Figure 6-2. Sample CORRECT Warning and Error Screens 6-3
Figure 6-3. CORRECT Modes of Operation '. 6-5
Figure 6-4. Sample CORRECT Screen Showing Level-1 Edit Errors 6-8
Figure 6-5. Sample CORRECT Data and Specification Screens 6-12
Figure 6-6. AIRS AQS User Profile and Main Menu Screens 6-16
Figure 6-7. Invoking CORRECT from the AQ Submit Menu 6-18
Figure 6-8. Using the DELETE Command in Normal Mode 6-20
Figure 6-9. Using the NUM Command 6-22
Figure 6-10. Selecting a Transaction Type for Input Mode 6-28
Figure 6-11. The Global Select Screen 6-32
Figure 6-12. The Global Change Screen 6-36
Figure 6-13. The Global Status Screen 6-39
Figure 6-14. PF Keys for Switching Among CORRECT Modes of Operation 6-47
Figure 6-15. The AIRS Error Screen 6-48
Figure 7-1. NOTIFY Data Flow Diagram 7-2
Figure 7-2. AIRS AQS User Profile and Main Menu Screens 7-5
Figure 7-3. The NOTIFY Menu Screen 7-7
Figure 7-4. The NOTIFY Menu Screen Showing an Error Message 7-9
Figure 7-5. The NOTIFY Error Screen 7-12
Figure 8-1. MESSAGE Data Flow Diagram 8-2
Figure 8-2. AIRS AQS User Profile and Main Menu Screens 8-3
Figure 8-3. Sample MESSAGE Screen 8-5
Figure 8-4. The MESSAGE Screen Showing an Error Message 8-7
Figure 8-5. The "No Messages" Screen 8-11
September 1993 ix Table of Contents
-------
AIRS User's Guide
Air Quality Data Storage Volume AQ3
Figure 9-1. DELETE Data Flow Diagram 9-2
Figure 9-2. AIRS User Profile and Main Menu Screens 9-3
Figure 9-3. The DELETE Job Submission Screen 9-5
Figure 9-4. The DELETE Job Submission Screen Showing an Error Message 9-8
Figure 9-5. Sample MESSAGE Screen Showing DELETE Messages 9-11
Figure 9-6. Sample DELETE Summary Report for Successful Jobs 9-13
Figure 9-7. Sample LOAD Summary Reports for Failed Jobs 9-15
Figure 11-1. The SCAN Summary Report 11-5
Figure 11-2. The SCAN Detail Report 11-7
Figure 11-3. The SCAN Inventory Report 11-9
Figure 11-4. The SCAN Current and Old NAMS Report 11-11
Figure 11-5. The SCAN Non-NAMS Criteria Report 11-13
Figure 11-6. The SCAN Excluded SLAMS Data Report 11-15
Figure 11-7. The SCAN SLAMS Report 11-17
Figure 11-8. The SCAN Precision and Accuracy Report 11-19
Figure 11-9. The SCAN NAMS/SLAMS Site/Monitor Update Report 11-21
Figure 11-10. The UPDATE Detail and Summary Reports 11-25
Figure 11-11. The UPDATE Inventory Report 11-26
Figure 12-1. BROWSE Data Flow Diagram 12-2
Figure 12-2. BROWSE/GENERATE Processing . 12-3
Figure 12-3. Browse Data Types Screen 12-9
Figure 12-4. Browse Screening File Selection Screen 12-10
Figure 12-5. Browse Site Data Selection Criteria Screen 12-11
Figure 12-6. Browse Site Data Screen 12-12
Figure 12-7. Browse Site Data Screen with Action Code Entry Window ("D") 12-13
Figure 12-8. Browse Site Data Screen with Delete Confirmation Window 12-14
Figure 12-9. Browse Site Data Screen with Screening File Record Message 12-15
Figure 12-10. Browse Site Data Screen with Action Code Entry Window ("I") 12-16
Table of Contents x September 1993
-------
AIRS User's Guide
Volume AQ3 Air Quality Data Storage
List of Tables
Table 3-1. AIRS Standard PF Keys 3-4
Table 4-1. Related Screening File Records 4-5
Table 6-1. .Related Screening File Records 6-11
Table 6-2. CORRECT Directives for Normal Mode 6-25
Table 6-3. CORRECT Directives for Input Mode 6-31
Table 6-4. CORRECT Directives for Global Mode 6-42
Table 6-5. Summary of CORRECT Directives 6-45
Table 6-6. CORRECT Operational Error Messages 6-50
Table 11-1. Dataset Names of SCAN Report Files 11-4
September 1993 xi Table of Contents
-------
AIRS User's Guide
Air Quality Data Storage Volume AQ3
1.0 Introduction
This manual explains how to use the Air Quality Data Storage Subsystem of AIRS, the Aerometric
Information Retrieval System. AIRS is a computer-based system for handling the storage and retrieval
of information pertaining to airborne pollutants. It is administered by the U. S. Environmental Protection
Agency, Office of Air Quality Planning and Standards, Monitoring and Data Analysis Division, National
Air Data Branch, located in Research Triangle Park, North Carolina. AIRS is installed on the IBM
computer system at EPA's National Computer Center in Research Triangle Park, North Carolina. AIRS
uses the ADABAS database management system to manage its data files and the CICS teleprocessing
monitor to provide the interface between users and programs.
The AQ Data Storage Subsystem that this manual describes is used to load data into the AIRS database
and to alter or delete information loaded previously. The data include descriptions of air monitoring
stations and their measurements of airborne pollutant concentrations. This manual is intended for the
person who initiates and controls such data storage activities. It gives step-by-step instructions for
carrying out each of the necessary tasks.
The rest of this manual is organized for easy reference to the required information. Section 2 summarizes
the concepts of the AQ Data Storage Subsystem that form the basis for its operational procedures and also
outlines a typical sequence of data storage processes. Section 3 explains the general administrative and
operational procedures of the AQ Data Storage Subsystem. Sections 4 through 9 present detailed
instructions for each of the AQ Data Storage processes available to users. Sections 10 and 11 describe
other processes that are carried out by the AIRS database administrator (ADBA). Section 12 describes
the Screening File Transaction Generate Option of the online AQ Browse process.
Although this manual presents complete operating instructions for the AQ Data Storage Subsystem,
information in other volumes of the AIRS User's Guide may be needed to use it successfully.
Instructions for coding AIRS transactions are given in Volume AQ2, and AIRS codes are listed in
Volume GC2. The data dictionary in Volume AQ1 describes the files, records, and fields of the AIRS
database and other closely related files used in the Air Quality Subsystem. A list of people to contact
for information or assistance with AIRS is given in Volume AA1. Information about computer center
procedures can be found in the "NCC-IBM User's Guide", and manuals about specific software products
such as ADABAS and NATURAL are available from the vendors of the software.
September 1993 1-1 Introduction
-------
AIRS User's Guide
Volume AQ3 Air Quality Data Storage
2.0 AQ Data Storage Overview
AIRS has four main subsystems that correspond to the four general types of data in the AIRS database:
Geographic, Common, and Maintenance Subsystem (Geo-Common)
Facility Subsystem
Air Quality Subsystem
Area Mobile Source
Figure 2-1 illustrates the relationships among the AIRS subsystems and identifies the relevant volumes
of the User's Guide.
The Geo-Common Subsystem consists mostly of reference data used by the other two subsystems, such
as FIPS state codes and state names for example. It is maintained by the AIRS database administrator.
Users can generate reports of Geo-Common data but can not alter the data.
The Facility and Air Quality Subsystems deal with air pollution data submitted by the responsible state
and regional organizations to the National Air Data Branch. Facility data pertain to the emissions of
pollutants by point (stationary) and area (mobile or nonspecific) sources. The data include information
about the emitting source, such as location and type, and the estimated or measured annual emissions of
criteria pollutants. The Area Mobile Source Subsystem contains emissions inventories from small
stationary and mobile sources, forest fires, fugitive transport, and natural; sources. EPA provides
emission estimates for the nation, whereas the states provide emission inventories for non-attainment
areas.
The Air Quality Subsystem deals with.the measurement of ambient air pollution by thousands of
monitoring stations in the United States and its possessions and trust territories. The Air Quality data
include descriptions of air monitoring sites and monitoring equipment, measured concentrations of air
pollutants and related parameters, and calculated summary and statistical information.
The Air Quality Subsystem is further subdivided into two subsystems based on the functions performed:
storing and retrieving data. Two volumes of the User's Guide describe how to store data. Volume AQ2
tells how to code the AQ data as card-image transactions, and this volume tells how to use AIRS to
process these transactions.
September 1993 2-1 Overview
-------
Air Quality Data Storage
AIRS User's Guide
Volume AQ3
AIRS - Aerometrlc Information Retrieval System
volume AA1
Air Quality
Subsystem
Monitoring Sltoc
Measured ambient
concentrations
of air po 1 1 utants
Volumes AQ1 -
AQ5
Geo- Common
Subsystem
Codes & Values
Reference data
and control
I nf or met Ion
volumes GC1-GC4
Fact llty
Subsystem
Bnlttlng Point
Sources
Point Sources
Emissions of
criteria
pol I utants
Volumes AF1 -
AF5
Area and Mob I le
Source Subsystem
Em I ss I ons
Inventor lee
Area and mob I le
sources emissions
of pol I utants
Volumes AM1 -
AVM
Data
Storage
(Vols. A02 ft AQ3)
Data
Retrieval
(Vols. A04 & A05D
Data
Dictionary
C volume A01)
Oeu
Coding
Instructions
(Volume «Q23
Operoiing
Instruct Ions
(Volume AO3D
<==== This volume
Figure 2-1. The Primary AIRS Subsystems and Relevant User's Guide Volumes
Overview
2-2
September 1993
-------
AIRS User's Guide
Volume AQ3
Air Quality Data Storage
AIRS
Air
.Qua 1 i ty
Data
System
i
ILOAD
i
! EDIT
' DELETE
i
1 CORRECT
i -
| NOT 1 FY
i
i BROWSE ([Transaction
•MESSAGE
i
! SCAN
i
! EXCLUDE
1
' UPDATE
i
! ARCHIVE
iDEARCHIVE
BATCH
BATCH
BATCH
ONL 1 NE
ONLINE
Generate) ONLINE
ONL 1 NE
BATCH
ONL 1 NE/ BATCH
BATCH
BATCH
BATCH
\
\
V
/
/
\
\
\
i
i
i
i
l
i
i
i
i
/
/
/
USER
L _ _
ADBA
Figure 2-2. Processes of the Air Quality Data Storage Subsystem
September 1993
2-3
Overview
-------
AIRS User's Guide
Air Quality Data Storage Volume AQ3
The essential function of the Air Quality Data Storage Subsystem is to read the card-image transactions
coded by local, state, and regional users of AIRS, validate the transactions, and use them to update the
AIRS database. Two types of processes have been defined to accomplish that: user processes, which are
available to all qualified AIRS users, and ADBA processes, which are available only to the AIRS database
administrator. Figure 2-2 illustrates this condition and identifies the processes in each category.
User processes are primarily for reading and validating the input transactions. They are:
LOAD copies the input transactions from a user-supplied tape or disk file into a
screening file.
EDIT checks the validity of the transactions in the screening file and produces a
report that identifies any errors.
CORRECT alters, deletes, or inserts transactions in the screening file according to user
directives in order to fix errors.
NOTIFY informs the AIRS database administrator that a screening file is ready for
update processing and locks the file to prevent changes, or revokes a prior
notification and unlocks the file.
MESSAGE allows users and the AIRS database administrator to view and dispose of
status messages generated by other processes such as LOAD, EDIT, and
NOTIFY.
BROWSE allows the user to generate screening file transactions (for site and monitor
(Transaction Generate) data types only).
ADBA processes are primarily for updating the AIRS database and for miscellaneous maintenance
functions. They are:
SCAN produces reports used by the database administrator to coordinate update
processing among multiple screening files, and irreversibly locks the files to
prevent user access.
EXCLUDE sets or clears the exclusion status of transactions in SCANed screening files;
excluded transactions are not processed by UPDATE.
UPDATE updates the AIRS database files using the validated transactions in SCANed
screening files, produces reports that describe the updating done, and deletes
from the screening files the transactions used in the updating.
ARCHIVE removes data for one or more years from the AIRS database.
DEARCHIVE loads ARCHIVEd data into the AIRS database.
Overview 2-4 September 1993
-------
AIRS User's Guide
Volume AQ3
Air Quality Data Storage
I End
UUWt&l
kCSSAGE
N3TIFY
BROWSE
Figure 2-3. Initiation of Online and Batch Data Storage Processes
September 1993
2-5
Overview
-------
AIRS User's Guide
Air Quality Data Storage Volume AQ3
The Data Storage processes are classified as "online" or "batch". An online process interacts with you.
It acts on the information you enter at the terminal keyboard and displays the results on the terminal
screen. A batch process, on the other hand, does its work independently. You specify at the terminal
what you want done and a batch job is submitted to do it. There is usually a delay of a few hours
between the time you initiate the process and the time it executes. You see the results of the batch
process by looking at the printed report it produces. The similarities and distinctions between online and
batch processes are illustrated in Figure 2-3.
Whether online or batch, every Data Storage process is initiated in the same way. AIRS is menu driven,
which means you select what you want to do from a list of choices displayed on a terminal screen. All
the Data Storage user processes are choices on a single menu screen, and you use the same procedure
to select any of them. If you choose an online process, the program associated with that process begins
executing. It displays screens and responds to the data and commands you enter until you terminate the
process. If you choose a batch process, you are presented with a screen for specifying JCL parameters
and any other necessary information. When you have entered the specifications, a batch job is submitted
to perform the real work of the process you selected. In either case, you can go back to the Data Storage
menu screen and choose another process if you want to. Alternatively, you could go back to a higher
level menu and choose a completely different function such as data retrieval, or you could terminate your
AIRS session.
Central to all the AQ Data Storage processes is the screening Tile, a special kind of file that holds AIRS
transactions. A screening file is an AD ABAS file like the other files in the AIRS database, but it is not
considered part of the master database (site, summary, and raw data). The purpose of a screening file
is to hold the AIRS transactions that are going to update the master database. Each screening file record
contains a copy of an AIRS input transaction plus some control fields used by the Data Storage processes.
The edit level field, for example, tells what types of edit checks the record has passed. The complete
record format is listed in Volume AQ1 of the AIRS User's Guide.
The AIRS database administrator allocates a screening file (or several, if necessary) to each organization
submitting air quality data to AIRS. Each screening file "belongs" to an organization for its exclusive
use; access to the file is controlled by passwords. Screening files are allocated for each state, and for
some local, regional, or federal organiztions such as TV A. Also, the AIRS database administrator has
several files for special uses.
Generally, a particular screening file is dedicated to a single batch of AIRS transactions from the time
they are loaded into it until they are used to update the AIRS database. (A batch of transactions might
be one month's data for a state, for example.) However, there is no requirement that a file be used that
way. Several batches of transactions could be loaded into a screening file and processed together.
All the Data Storage processes use a screening file in some way. The NOTIFY and MESSAGE processes
do not access a screening file directly, but use the name of a screening file to perform their functions.
The other processes (except ARCHIVE/DEARCHIVE) directly read and write information in a screening
file. Since the screening file is the common point of reference for the processes and there are rules and
procedures for using this file, there is a high probability that only valid information gets into the AIRS
database. For example, the UPDATE process uses only those transactions that have been completely
validated by the EDIT function. While the ADBA has temporary control of a screening file to perform
Overview 2-6 September 1993
-------
AIRS User's Guide
Volume AQ3 Air Quality Data Storage
a database update, the file cannot be altered. Neither LOAD nor EDIT nor CORRECT will access a file
that is locked, and the file remains locked until the update has been done. These safeguards are designed
to prevent the accidental loading of invalid data into the AIRS database and the accidental corruption of
valid data in a screening file.
September 1993 2-7 Overview
-------
AIRS User's Guide
Volume AQ3 Air Quality Data Storage
3.0 General Operational Procedures
This section describes the preliminary things you have to do in order to use the Air Quality Data Storage
Subsystem. It also explains the operational procedures common to all the Data Storage processes
discussed in following sections.
3.1 Registration and Equipment Requirements
Any governmental or private organization may submit air quality data for inclusion in the AIRS database.
Usually the state agency responsible for air pollution management submits the data for that state, but other
organizations, including nongovernmental bodies or corporations, may also submit data. AIRS can handle
confidential as well as public data, so organizations with special or private air quality data may take
advantage of AIRS data handling facilities, subject to the approval of the database administrator.
In order to use the AIRS data storage facilities you must register with the AIRS database administrator
for the Air Quality Subsystem, listed in Volume AA1 of this User's Guide. The AIRS database
administrator needs to know what organizations or groups are using AIRS so screening files and other
resources can be allocated. The ADBA also needs to know the identity and group affiliation of each
individual who will use AIRS so the necessary access authorities can be established in control files.
(Only the members of a group can access the screening files allocated to thai: group.) An individual is
identified within AIRS by the user-ID assigned by the EPA National Computer Center. If you do not
have a valid NCC-IBM user-ID, contact the TSSMS Office of the Computer Center or the AIRS database
administrator to find out how to obtain one.
To use AIRS, you need the equivalent of an IBM 3270 Model 2 terminal connected to the NCC-IBM
computer system through the EPA telecommunications network. The optimal configuration is a 3270-type
terminal or a personal computer (PC) with a 3270-type emulation card and a high speed communications
line. An alternative is the Computer Center's protocol converter, called the "TCP", which provides 3270
emulation for many brands of asynchronous terminals. You could use a personal computer with
asynchronous communications equipment for a terminal, but a PC emulating an asynchronous terminal
emulating a 3270 terminal may be too complicated to be useful. The minimum acceptable
telecommunications speed is 1200 bps; higher speeds (2400 or 9600 bps) are preferable. Contact the
Computer Center for information about the types of terminal and communications equipment best suited
for your needs.
September 1993 3-1 Procedures
-------
AIRS User's Guide
Air Quality Data Storage Volume AQ3
3.2 Screening Files
As mentioned in Section 2, screening files play a central role in the operation of the Data Storage
Subsystem. They are the common link among all the Data Storage processes.
Some screening files are owned by the AIRS database administrator and are used for special functions.
For example, a transaction that changes the designation of monitoring station type to "NAMS" must be
in an ADBA's screening file in order to pass edit checks. That requirement ensures that the ADBA will
be aware of all such transactions, since the ADBA must approve them.
The ADBA allocates regular, user screening files to each organization or group of AIRS users submitting
data. Each screening file is assigned a unique name using the convention shown in Figure 3-1. You need
be concerned only with the last eight characters of the name. The "AM-" prefix is dropped from all the
names you will see and use in the Data Storage processes. For example, an ADBA's screening file might
be named "ANADBA02". A file allocated to a group of users at the EPA regional office in Atlanta could
have the name "R04AQA01", and the name of a file used by EPA's Environmental Monitoring Systems
Laboratory might be named "O88AQB01".
It is important that a group of users coordinate their usage of the available screening files. Loading a
batch of transactions into a screening file that someone else just finished editing and correcting could
cause confusion and errors, not to mention hard feelings. Another situation to avoid is loading the same
batch of transactions into two different screening files and processing both of them. It might be advisable
to have a screening file status sheet posted in a conspicuous place that shows who is using each screening
file and for what purpose. It is easier to prevent mistakes than to repair the damage resulting from them.
There are a few restrictions on the usage of screening files. As we have noted before, at least one type
of transactions has to be in an ADBA's screening file in order to pass edit checks. If you have to process
one of those types (they are noted in the coding instructions in Volume AQ2 and in EDIT error
messages), contact the ADBA for assistance. There is no way you can move the transactions from your
screening file directly to the ADBA's file.
Another restriction is that monitors are linked to screening file groups. (A group is all the screening files
that have the same name except for the two-character sequence number at the end.) All the data
(transactions) for a particular monitor must come from the same screening file group that the initial
transaction came from. Each monitor is "owned" by its screening file group and can be updated only
from a screening file in that group. This restriction should be of concern only if you are a member of
more than one group of users. In that case, you must be sure to use a screening file appropriate for the
transactions you are processing.
Procedures 3-2 September 1993
-------
AIRS User's Guide
Volume AQ3
Air Quality Data Storage
Screening File Name Format: PP-TNNNNNSS
PP- Subsystem Prefix
T Type of Owner
AM- = Air Quality
A = ADBA
R = EPA Region
S = State
L = Local
0 = Other
NNNNN Owner Name / Identification
for owner type A: "NADBA"
for owner type R,S,L: ##AQA
("##" is a numeric region or state code)
SS
for owner type 0:
Sequence Number
88AQx
("x" is a unique alpha identifier such as A, B, etc.)
"01", "02", etc.
Figure 3-1. Naming Convention for AIRS Screening Files
September 1993
3-3
Procedures
-------
Air Quality Data Storage
AIRS User's Guide
Volume AQ3
Table 3-1. AIRS Standard PF Keys
This table summarizes the standard PF key definitions used throughout AIRS.
Kgy.
PF3
PF4
Function
End
Return
(to AQS Main Menu)
Explanation
Terminates the current function and goes back to the
previous function.
Terminates the current function and goes back to the
AIRS AQS Main Menu.
PF5
Quit
Terminates the AIRS session (and the NATURAL
session).
NOTE
The ways that PF3, PF4, and PF5 terminate the current function differ among AIRS
programs. Most programs complete the current function (by carrying out the actions
specified or implied by what is on the screen) while some abort the current function and
ignore the screen. The specific interpretation is explained in the section for each Data
Storage process.
PF7
PF8
Previous
Next
Pages backward to the previous screen in a series of
screens with the same format.
Pages forward to the next screen in a series of screens
with the same format or goes to the next record in a
file.
Procedures
3-4
September 1993
-------
AIRS User's Guide
Volume AQ3 Air Quality Data Storage
3.3 General Conventions and Procedures
This section explains the general conventions and normal procedures used throughout the AIRS Air
Quality Data Storage Subsystem.
3.3.1 Standard PF Keys
AIRS, like many other applications on IBM computer systems, makes use of the 3270-type terminal's
Program Function keys as a shorthand means of entering instructions or commands that control what a
program does. Indeed, most AIRS programs do not accept typed commands; the PF keys are the only
way to specify what you want to do.
The number of PF keys defined for a particular program depends on the program's complexity or
versatility, and the meaning of a particular PF key may differ from one program to another. However,
a few directives, such as "end this function" or "end this session", are available in nearly every AIRS
program. The same PF keys are used for these common commands throughout AIRS. Furthermore, the
AIRS usage of PF keys is similar to the usage in many widely-used programs such as ISPF.
The standard AIRS PF keys are listed and explained in Table 3-1.
Many 3270-type terminals have 24 PF keys and define the PF13-PF24 keys as the default or primary set
and PF1-PF12 as the secondary set. AIRS uses only the first 12 PF keys, PF1-PF12; the PF13-PF24
keys are not used or recognized. For example, PF15 is not equivalent to PF3.
3.3.2 Other Special Keys
Two other special keys on a 3270-type keyboard are important for AIRS. They are discussed below.
The ENTER key is probably the most frequently used special key. It causes the information on the
screen to be passed to the AIRS program for processing. After processing the information, the program
may redisplay the same screen or a different one depending on the circumstances. In essence, the
ENTER key tells a program to process the current screen, then do the next thing in logical sequence.
The CLEAR key aborts the active AIRS session, then starts a new AIRS session. Since any activities
pending at the time may not be completed properly, use of this key is not recommended.
September 1993 3-5 Procedures
-------
AIRS User's Guide
Air Quality Data Storage Volume AQ3
Welcome to the Environmental Protection Agency National Computer Center
Please enter one of the following selections:
IBM for IBM
UNI for SPERRY
TCP for 3270 EMULATION
FMO for FMO POP
VAX for VAX
PRIME for PRIME
Enter selection: tcp
Connected.
-------
AIRS User's Guide
Volume AQ3 Air Quality Data Storage
3.4 AIRS Logon Procedures
This section explains how to begin an AIRS terminal session.
3.4.1 TCP Logon
This page gives instructions for using the protocol converter, or "TCP", to simulate a 3270-type terminal.
If you are using an actual 3270-type terminal, skip this page.
1. Prepare your equipment for use by turning on power, adjusting terminal! settings, executing your
PC's communications program, or any other necessary preliminaries. If you do not already know
what communications parameters to use, contact the Computer Center for assistance.
2. Dial the appropriate phone number and establish connection with the EPA telecommunications
network. The Computer Center will tell you how to do this if you do not know.
3. Press the ENTER or RETURN key on your terminal once or twice until the message "Welcome
to the Environmental Protection Agency National Computer Center..." is displayed on your
terminal. (The complete text of the message is shown in Figure 3-2.)
4. Type "tcp" and press ENTER or RETURN to choose the 3270 emulation option from the menu.
5a. If you know the "initial signon character" for your terminal, type it three or four times at half-
second intervals until the TCP responds by clearing the screen and displaying a message. Type
only the signon character; do not press ENTER or RETURN. Typical signon characters are "M"
for a DEC VT-100 terminal and "]" for a Televideo 950 terminal.
5b. If you do not know the "initial signon character" for your terminal, press ENTER or RETURN
three or four times at half-second intervals until the TCP responds with the message " > >
COMMTEX Cx-80 DATA EXCHANGE «" and follow the instructions displayed on the screen.
(Figure 3-2 shows an example of this procedure.)
6. When the TCP knows what kind of terminal you are using, it responds by clearing the screen and
displaying the message "** Cx-80 VER 04.76 **". (The version number, "04.76", may change
from time to time as the TCP is expanded to handle more types of te/minals.) Do not do anything
while this message is displayed; just wait patiently. After a few seconds you will see the EPA
logon menu described on the next page. Your terminal is now effectively a 3270-type, and the
procedures from this point on are the same as for an actual 3270 terminal.
September 1993 3-7 Procedures
-------
Air Quality Data Storage
AIRS User's Guide
Volume AQ3
NETHAIN U.S. Environmental Protection Agency
Menu System
Date:
Tine:
Terminal:
Logmode:
06/18/93
11:34:05
T260192
MSDLCO
Please enter (election or command and then press ENTER.
1. INFORMATION Metis Alerts and User ttenos
Z. SYSTEM MENU System Selection Menu
3. MAIL EPA Electronic Mail for 3270
4. APPLICATIONS EPA Applications Menu
5. INTER-AGENCY Inter-Agency Applications Menu
A. PUBLIC Public Access Applications Menu
WARNING: The use of this computer is for official Government business only.
Unauthorized use of this computer is a criminal offense under Title 18
United States Code, Section 641, and nay subject violators to a fine of
:up to $10;000, or:Imprisonment of up to 10 years, or both.
Command ===> airs
Optional Quick Logon - USERIO ««»> pkb
PASSWORD ===> xxxxxx or
Fl/f13=Help F5/F17=Refresh F12/F24=Cancel
NPELM002 'Missing PASSWORD
10:25:36 Tern T24BK044 MSDLCQ
NET-PASS Userid PKB
06/18/93
U.S. Environmental Protection Agency
NETPASS Logon
Enter USERID and PASSWORD and then press ENTER
Userid: PKB
Options:
Password:
New Password:
Figure 3-3. Using the EPA Logon Screens
Procedures
3-8
September 1993
-------
AIRS User's Guide
Volume AQ3 Air Quality Data Storage
AIRS Logon Procedures (continued)
3.4.2 EPA Computer System Logon
AIRS is available only in the production CICS environment of the NCC-IBM computer system. The
instructions on this page explain how to logon directly to AIRS. Section 3.4.3 describes CICS logon
procedures.
The EPA logon procedure involves the EPA Menu System screen, shown at the top of Figure 3-3. You
can invoke AIRS from this screen.
1. Turn on your 3270-type terminal (or follow the TCP logon procedures above). The EPA Menu
System screen, shown in Figure 3-3, should be displayed on your terminal. (If it is not, contact
the Computer Center for assistance.) Type 'AIRS' at the command === = >.
2. TAB to USERID = = = > and type your userid. Press ENTER. TAB to PASSWORD = = = >
and type your password. Press ENTER.
This completes the Quick Logon Procedure. The AIRS Main Menu (see Figure 3-7) will appear after
a short delay. If you did not enter your userid or password correctly, the NETPASS Logon menu shown
at the bottom of Figure 3-3 will be displayed. Re-enter your userid and password and press ENTER.
Warning
If you enter your password incorrectly three times, your userid is revoked by NCC. In that case, NCC
staff will have to call User Support staff in order to get your userid re-established.
News Alerts and User Memos also can be displayed prior to logon by selecting T or typing
"Information" from the EPA Menu System screen (see Figure 3-3).
September 1993 3-9 Procedures
-------
Air Quality Data Storage
AIRS User's Guide
Volume AQ3
1NFOMP1 U.S. ENVIRONMENTAL PROTECTION AGENCY Date: 03/26/91
News Alert I User Mem Facility Tine: 13:16:16
XX XX XXXXXX XXXXXX XX XXXXX XX XX XXXXXXXX XXXXX
XXX XX XXXXXXXX XXXXXXXX XX
XXXX XX XXX XXX XX
XX
XX
XX
XX
XX
XX XX XXX XXX XX
XX XX XXX XXX XX
XXXX XXX XXX XX
XXX XXXXXXXX XXXXXXXX XX
XX XXXXXX XXXXXX XX
Please enter selection or command and then
1. NEWS ALERTS
2. USER NEMOS
3. REGISTRATION INFORMATION
Comnand ==> 1
F1/F13*Help F3/F15=Exit
XXXXX
XXX
XXX
XXX
XXX
XXXXX
XXXXX
XXX XX XXXXXXXX XXXXXXX
XXXX XX XX
XX XX XX XXXXX
XX XX XX XXXXX
XX XXXX XX
XX XXX XX
XX XX XX
XX XX
XX XX
XX XX
XX XX
XXXXXXX
XXXXX
press ENTER.
INF1MN1 U.S. ENVIRONMENTAL PROTECTION AGENCY Date: 03/26/91
News Alert Facility Time: 13:16:24
Select news alerts and then press ENTER.
--DATE----- TITLE - ID--
91/03/25 FILE-AID/SPF V6.4.1 AVAILABILITY ALERT4
91/03/25 OS PL/1 VER 2 RELEASE 3 PRODUCTION RELEASE ALERT1
91/03/21 PLSORT RELEASE 6.3A IN PRODUCTION 3/25/91 ALERTS
91/03/U NEW NCC MENU SYSTEM ALERTS
91/03/12 BASIS REL K VERS 9.0 AVAILABLE FOR TESTING ALERT11
91/03/12 FOCUS PUT LEVEL 9012 AVAILABLE FOR TESTING ALERT10
91/03/01 REMOVAL OF IDMS FROM NCC IBM ALERT3
91/02/27 CHANGE IN ARCHIVAL OF DATA SETS (UPDATE) ALERT2
91/02/19:SAS RELEASE 6.06 PRODUCTION DATE 01/21/91 ALERT6
: Cofmond •*»»>
M/F13=HELP F3/F15=Exit F5/F17=Rep Find F1/F19=Baekward F12/F24=Cencel
Figure 3-4. News Alert & User Memo Screens
Procedures
3-10
September 1993
-------
AIRS User's Guide
Volume AQ3
Air Quality Data Storage
ZZSMSHT U.S. Environmental Protection Agency
PRODUCTION CICS logon
Date: 06/27/93
Time: 14:18:11
Enter USERID and PASSUORD and then press ENTER.
USER ID «=>
PASSWORD «=> HEW PASSUORD ===>
Change other Logon parameters (Y/M) »==> Y Cancel
PF1/13=Help PF3/15=Exit
ZZSNLNG
•
••
t
f
U.S. Environmental Protection Agency Date: 06/27/91
PRODUCTION CICS sign-on Tine: K:19:(K
Enter USER ID and PASSWORD and then press ENTER.
USER ID
PASSWORD
ACCT ID
FINAS
*=>
===>
===>
===>
CROUP IDENT ===>
INITIAL
oninund **s>
•F1/13=Help
TRANS =>
PF3/15
BLY
NEW PASSWORD ===>
'
ASUD BIN NUMBER ===>
A1RSP PRINT DEST ===>
ASUD
AIRS
=Exit
S
?
t
^
'
.
Figure 3-5. Using the CICS Logon Screen
The "sign-on complete" message is displayed after successful logon.
September 1993
3-11
Procedures
-------
AIRS User's Guide
Air Quality Data Storage Volume AQ3
AIRS Logon Procedures (continued)
3.4.3 CICS Logon
This section explains how to use the CICS logon screen shown in Figure 3-5 to tell CICS who you are,
what computer account code to be charged, and other related information. If you entered "airs" rather
than "pcics" on the EPA Logon Screen shown at the top of Figure 3-3, the screen shown at the top of
Figure 3-5 will not be displayed.
1. Type your NCC-IBM userid into the field labeled USERID.
2. Type your NCC-E3M password in the field labeled PASSWORD, flt does not show on the
screen when you type it.) You must enter your password every time you logon; it is not
saved like the other values on the screen.
3. If you want to change your NCC-IBM password, type the new value in the NEW
PASSWORD field. Like the password field, the value you type does not show on the
screen. Type carefully! (Every new user of the NCC-IBM computer system must change
his or her password during initial logon.)
4. Type "Y" to change the other logon parameters.
5. After you press ENTER, the screen at the bottom of Figure 3-5 will be displayed. Supply
values on the CICS logon screen for the fields labeled ACCOUNT, FIMAS IDJ and
GROUP. All the values you enter on this screen (except password) are saved in your CICS
logon profile for subsequent logons. You can retrieve your profile values by typing your
NCC-IBM user-ID in the USERID field and pressing ENTER. You should use "AIRSP"
for FIMAS ID, and GROUP is usually the same as ACCOUNT. You must use an account
for which you are authorized, of course.
6. You may specify "airs" for INITIAL TRANSACTION if you wish, and thereby tell CICS
to invoke AIRS after completing the logon. With respect to logging onto AIRS, it makes
no difference whether you enter "airs" on this screen or a later one. (To erase an initial
transaction name saved from a previous logon, type all spaces in this field. Clearing the
field with the 3270's erase-to-eof key does not work.)
7. Press ENTER to initiate logon after you have typed in or erased values from the fields as
described above. If logon is successful, and you did not specify an initial transaction of
"airs", the Production CICS Menu System screen is displayed until you take further action,
as described in subsequent steps.
Procedures 3-12 September 1993
-------
AIRS User's Guide
Volume AQ3 Air Quality Data Storage
AIRS Logon Procedures (continued)
CICS Logon (continued)
8. If you forgot to enter a value for one of the required fields of the CICS logon screen, the
message "•**** ERROR - NOfield name SPECIFIED, BUT IS REQUIRED" is displayed.
Type a value for the field identified in the message and press the ENTER key again.
9. If you entered an incorrect value for a field Of the CICS logon screen, the message "*****
ERROR - INVALID field name SPECIFIED" is displayed. The message is slightly
different if the incorrect value was your password: "***** ERROR - INVALID SIGNON
ATTEMPT - PASSWORD NOT AUTHORIZED". Carefully type the correct value for the
field identified in the message and press the ENTER key again. Note that the message may
identify ACCOUNT as the invalid field if the GROUP value is wrong.
10. If you specified "airs" as your initial transaction, the AIRS Main Menu will be displayed.
11. If you did not specify an initial transaction of "airs" on the CICS logon screen, you must
invoke transaction "airs" now. Type "airs" at the COMMAND prompt and press ENTER.
September 1993 3-13 Procedures
-------
Air Quality Data Storage
AIRS User's Guide
Volume AQ3
ZZMIWP1
XX XX XXXXXX
U.S. Environmental Protection Agency
News Alert ft U*er Nemo Facility
XXXXXX XX XXXXXX
XXX XX XXXXXXXX XXXXXXXX XX XXXXXXXX
XXXX XX XXX
XX XX XX XXX
XX XX XX XXX
XX XXXX XXX
XXX XX XXX
XXX XX XXX
XXX XX XXX
XXX XX XXX
XX XXX XXXXXXXX XXXXXXXX XX XXXXXXXX
XX XX XXXXXX
XXXXXX XX XXXXXX
xxxxx
xxxxx
XXX
XXX
XXX
XXX
xxxxx
xxxxx
Date:
Time:
Terminal:
XXXXXX
XXXXXXXX
XXX
XXX
XXX
XXX
XXXXXXXX
XXXXXX
03/26/91
13:16:16
H0422232
XXXXXX
XXXXXXXX
XXX
XXX
XXX
XXX
XXXXXXXX
xxxxx
Please enter selection or coonand and then press ENTER.
1. INFORMATION
2. SIGN-ON
3. APPLICATIONS
4. EXIT
Command «*»»>
News Alerts and User Nemos
Change CICS Sign-on Parameters
EPA Applications Menu for CICS
Exit CICS and return to EPA Menu System
F1/F13=Help F3/F15»Exit F10/F22=Lock F12/F24=CICS
i02/16/90 Aerometric Information Retrieval System
: / Main Menu
1. Air Quality (AQS)
2. Facility (AFS)
3. Area Mobile Source (AMS)
4. Geographic/Common (GCS)
5. AIRS Graphics (AG)
.Please enter Selection:
AAPOOO
PF3=end
PF5=terminate
Figure 3-6. Invoking AIRS from CICS
Invoking CICS transaction "AIRS" causes the main menu to be displayed.
Procedures
3-14
September 1993
-------
AIRS User's Guide
Volume AQ3 Air Quality Data Storage
AIRS Logon Procedures (concluded)
3.4.4 Invoking AIRS
AIRS is a NATURAL "application"; AIRS programs are written in the NATURAL programming
language and they execute under NATURAL'S control. Invoking AIRS could be a two-step process:
executing NATURAL and selecting AIRS as the application. A special program (a CICS "transaction")
is available that simplifies the AIRS logon procedure. The program takes care of executing NATURAL
and selecting AIRS as the application. All you have to do is execute the special AIRS program. This
page explains the simple procedure.
1. Type "airs" on the screen and press ENTER. (If AIRS is your initial transaction, then of
course you do not have to type "airs"; you just press ENTER.)
2. When CICS recognizes the "airs" transaction name, it initiates NATURAL and supplies
NATURAL with all the information it needs to start up the AIRS application. As a result
of all that, the first AIRS screen appears, as shown at the bottom of Figure 3-6.
3. If you made a mistake in typing "airs", the logon screen is redisplayed with the error
message "EPA002B2 Valid cmds are HELP, EXIT & LOCK, for CICS cmds enter 'CICS
'". The cursor is positioned at the COMMAND prompt. Type "airs" there and
press ENTER. You do not need to clear the screen before typing "airs".
4. If a message is displayed on your screen that starts with the number "NATSxxx" or
"NAT9xxx", then something is wrong with NATURAL or AD ABAS. You will not be able
to use AIRS until the problem is fixed, and you should skip to the CICS logoff instructions
given on the next page. Problems of this sort are usually resolved by the Computer Center
within a fairly short time (30 to 45 minutes). Try again after an appropriate delay.
When you have successfully logged on to AIRS, follow the AIRS top level user procedures given later
in this section.
September 1993 3-15 Procedures
-------
Air Quality Data Storage
AIRS User's Guide
Volume AQ3
HAT9995
KATURAL SESSION IERMIHATED
CSSf logoff • NATURAL SESSION TERMINATED
DFH3506I 14:26:36 SIGN-OFF IS COMPLETE
NETMAIN
U.S Environmental Protection Agency
Menu System
Please enter selection or command and then press ENTER.
1. INFORMATION News Alerts and User Memos
2. SYSTEM MENU System Selection Menu
3. • tMAl L.:•; :"•,..•••••:.:2EPA E1ect ron i c Me iI for 3270
Date: 03/26/91
Time: 11:34:05
Terminal: 1260192
Logmode: S3278R2
Figure 3-7. CICS Logoff Screens
Procedures
3-16
September 1993
-------
AIRS User's Guide
Volume AQ3 Air Quality Data Storage
3.5 AIRS Logoff Procedures
Compared to logon procedures, the AIRS logoff procedures are very simple.
3.5.1 CICS Logoff
1. When you end your AIRS session, a the NATURAL termination message appears at the top of the
screen and CICS waits for you to tell it what to do next. This is shown at the top of Figure 3-7.
At this point you could type "airs" to start another AIRS session, type another CICS transaction
name to do something different (look at the status of batch jobs using SYSD, for example), or end
your CICS session.
2. To end your CICS session and logoff, type "cssf logoff' and press the ENTER key, as shown in
Figure 3-7. You can type over the NATURAL message.
3. If the logoff is successful, CICS briefly displays the message "DFH3506I time SIGN-OFF IS
COMPLETE" near the bottom of an otherwise blank screen, and then the EPA logon menu screen
appears.
4. If you typed "cssf but forgot the "logoff1 pan of the command, the "SIGN-OFF IS COMPLETE"
message stays on the screen. Press the ENTER key and the CICS logon screen will be displayed.
Instructions at the bottom of the screen indicate what you can do to logoff. The simplest method
is to press the PF12 key, which completes the logoff. Alternatively, you could press the PF3 key,
which causes the screen to clear. Then carefully type "cssf logoff' and press ENTER again.
5. If you typed "cssf1 wrong, the message "DFH2001I INVALID TRANSACTION
IDENTIFICATION name - PLEASE RESUBMIT" is displayed. Carefally type "cssf logoff1 and
press ENTER again.
3.5.2 TCP Disconnect
If you are using the TCP (protocol converter) to simulate a 3270-type terminal, you should disconnect
from the protocol converter when you have ended your CICS session. The TCP has a limited number
of ports, and when you disconnect your terminal the port you have been using becomes available to other
users.
1. To disconnect from the TCP, hold down the CONTROL key and press the Y key (CNTL/Y).
2. The TCP clears the screen, displays the message "* Cx-80 DISCONNECT *", and disconnects
from the telecommunications line.
September 1993 3-17 Procedures
-------
Air Quality Data Storage
AIRS User's Guide
Volume AQ3
I II
Figure 3-8. Hierarchical Relationships Among AIRS Processes
Procedures
3-18
September 1993
-------
AIRS User's Guide
Volume AQ3 Air Quality Data Storage
3.6 AIRS AQS Top Level User Procedures
When you begin an AIRS session you make a series of high-level choices about what you want to do.
The part of AIRS that handles these choices is called the "top level user session". This section of the
User's Guide tells what it does and how to use it.
The top level user session consists of four screens. Descriptions of the screens and detailed instructions
for using them to access the Air Quality Data Storage Subsystem are given on following pages. The first
screen, the AIRS main menu, allows you to choose the AIRS subsystem - Air Quality, Facility, Area
Mobile Source, Geo-Common, or Graphics - you wish to enter. The second screen, the user profile,
is for specifying things that will be in effect for the duration of your AIRS AQS session or until you
return to the user profile screen and change them. This includes the selection of a screening file. The
third screen is the AIRS AQS main menu. With it you choose the AIRS Air Quality function ~ data
storage or data retrieval - you want to do. (When an AIRS database administrator is using the system,
the main menu screen also includes update functions for each subsystem that are available only to the
ADBA.) The fourth screen is a subsystem/function menu that shows the processes available for the
AIRS AQS subsystem and the type of function that you chose from the previous menu. The format of
each subsystem/function menu is somewhat different since the number and types of processes are different
for each subsystem.
The four screens of the top level user session form the apex of a hierarchicaJ relationship among AIRS
processes (hence the name "top level"). This is illustrated in Figure 3-8, where each box represents a
process. When you make a choice from a menu at one level, you automatically move down to the next
level along the line, or path, dictated by your choice. There you can make another choice and move
down another level until you reach the lowest level available in that path, When you complete the
process at the end of the path you automatically move back up to the process at the next higher level in
the path. You can also use the PF3 key to terminate the current process and move one level up the path
you came down, ultimately reaching the main menu at the top of the AIRS hierarchy. One more PF3
at that point takes you out of AIRS and back to CICS, the next "higher" level. (Two other AIRS AQS
standard PF keys provide "shortcuts". PF4 moves you directly to the AIRS main menu or the AQS main
menu from any process lower in the hierarchy, and PF5 takes you out of AIRS to CICS from any
process.)
You can go up and down several different paths in one AIRS session. For example, you could go down
the AQ Data Storage path to CORRECT and fix an error in a screening file, then up to the AQ Data
Storage Subsystem menu and down to EDIT to submit a batch job for checking the same screening file.
Then you could go up to the main menu, go down the Geo-Common Retrieval path, submit a batch job
to list, for example, valid interval codes, and finally end the AIRS session by pressing PF5.
September 1993 3-19 Procedures
-------
Air Quality Data Storage
AIRS User's Guide
Volume AQ3
IOZ/23/SJ;
Aerometrfc Inforwation Retrievat Sy»tea
MPCOO
PF3=end
4. CeoorBphlc/Comion (CCS)
5. AIRS Graphics :(AG)
Please enter Selection: 1
PF5=terminate
02/16/90
AIRS Air Quality Subsystem
User Profile COT
AAPOOOO
Password:
Printer ID: RMTOOO
Account code: ASWD
Bin Nunber: B132
SCREENING FILES
ANADBF01 Air Quality Screening File Readonly Not Locked
ANADBF95 Air Quality Screening File Read Only Not Locked
S55AQA01 Air Quality Screening File Update Not Locked
Enter Profile Data (optional)
PF3=end PF4=subsystem menu
PF5=terminate
Figure 3-9. The AIRS Main Menu
The AIRS AQS user profile screen appears after subsystem selection.
Procedures
3-20
September 1993
-------
AIRS User's Guide
Volume AQ3 Air Quality Data Storage
Top Level User Procedures (continued)
3.6.1 AIRS Main Menu
The main menu is the first screen of the AIRS user session. It is displayed when you invoke AIRS from
CICS or when you use the PF3 or PF4 key on the AIRS AQS user profile screen.
The AIRS main menu is used to select the subsystem (Air Quality, Facility, Area Mobile Source, Geo-
Common, Facility, or Graphics) you want to use. The subsystem menu is shown at the top of Figure
3-9.
The instructions for using the main menu to select the Air Quality Data Subsystem are very simple:
1. After the PLEASE ENTER SELECTION prompt, type " 1" and then press the ENTER key. This
selects the AQS subsystem of AIRS.
2. If you entered the selection correctly, the AQS user profile screen will be displayed. It is shown
at the bottom of Figure 3-9.
3. If you entered the wrong main menu selection, a different menu will be displayed. Press PF3 or
PF4 to return to the main menu, specify option "1", and press ENTER.
4. If you entered an invalid selection, the message "INVALID SELECTION - RE-ENTER" is
displayed at the top of the screen. Carefully type "1" in the selection field and press ENTER.
You can also use the PF5 key to terminate your AIRS session (and your NATURAL session) while the
AIRS main menu is displayed. If you use any other PF or PA key., the message "NAT1011
REQUESTED FUNCTION KEY NOT ALLOCATED" is displayed at the top of the screen.
September 1993 3-21 Procedures
-------
AIRS User's Guide
Air Quality Data Storage Volume AQ3
02/16/90 AIRS Air Quality Subsystem AAPOOOO
User Profile COT
Password: Account code: ASUD
Printer ID: RHTOOO Bin Number: B132
SCREENING FILES
SANADBF01 Air Quality Screening File Read Only Mot Locked
ANADBF95 Air Quality Screening File Read Only Not Locked
SS5AQA01 Air Quality Screening File Update :Not Locked
Enter Profile Data (optional)
PF3=end PF4=subsystem menu PF5=terminate
Figure 3-10. The AIRS AQS User Profile Screen
Procedures 3-22 September 1993
-------
AIRS User's Guide
Volume AQ3 Air Quality Data Storage
Top Level User Procedures (continued)
3.6.2 User Profile Screen - Description
The user profile screen is the second screen of the AIRS AQS top level user session. It is displayed when
you invoke the AIRS Air Quality Subsystem from the AIRS main menu or when you use the PF3 key
on the AIRS AQS main menu screen. You use the profile screen to specify three types of information:
an AIRS AQS (ADABAS) password, parameters to be used in the JCL of any AIRS AQS batch jobs you
may submit, and screening file selection. These parameters remain in effect throughout your AIRS
session or until you return to the user profile screen and change them.
A sample user profile screen is shown in Figure 3-10. Your NCC-fflM user-ID is displayed in the
second line of the screen heading. Below that are four fields where you enter a password and specify
JCL parameters: NCC-IBM account code, remote printer site-ID, and bin or box number. The AIRS
database administrator can establish an AIRS profile for you with default values of your choosing for the
JCL parameters. Then your defaults will be displayed on the user profile screen.
Beneath the heading "screening files" is a list of screening files you are authorized to access. (If no
screening files are listed, you can not use any of the AQ Data Storage processes described in this
manual.) The list includes the screening file name, the type of data it holds (Air Quality or Source), the
type of access for which you are authorized (read only or both read and update) and the status of the
screening file (locked for scan, update or by user, or not locked). To the left of each screening file name
is a field, which does not show on the screen, for selecting the file. You may select one screening file
for each type of data. If all your screening files are for Air Quality data, you may select only one file.
At the bottom left corner of the screen are two messages. The first one, "ENTER PROFILE DATA
(OPTIONAL)", means you are to specify your profile information in the fields provided. "Optional"
means that you can either use the default values for account code, printer ID, and bin/room displayed on
the screen, or you can enter different values; you can not leave any of those fields blank. Furthermore,
in order to use any of the AQ Data Storage processes described in this manual, you must also specify a
password and select a screening file. (On the other hand, it is generally not necessary to enter a
password or select a screening file when you use the Data Retrieval subsystems.)
The second message at the bottom of the screen, "PF3 = end PF4=subsystem menu PF5=terminate", is
a reminder that you can use the PF3 or PF4 key to return to the main menu or the PF5 key to terminate
AIRS from this screen. If the second message also includes the phrase "PF8=more", then all the
screening files you are authorized to access could not be listed on this screen, and you can use the PF8
key to advance to the next screen of file names. (A note of caution: you can not come back to the current
screen once you have paged forward with PF8, so be sure you have finished with the current screen
before you page forward.)
September 1993 3-23 Procedures
-------
Air Quality Data Storage
AIRS User's Guide
Volume AQ3
02/16/90
AIRS Air Quality Subsystem
User Prof1l« CQT
AAPOOOO
Password:
Printer 10: RMTOOO
Account code: ASM)
Bin Nurber: 8132
SCREENING FILES
ANADBF01 Air Quality Screening file Read Only Mot locked
ANADBF95 Air Quality Screening file Readonly Mot locked
SS5A6A01 Air Quality Screening File Update Mot Locked
Enter Profile Data {optional)
PF3=end PF4=subsystem menu
PF5=terminate
02/22/90
AIRS Air Quality Subsystem
Main Menu
AAPOOOA
1. Submit Data
2. Retrieve Data - Standard Batch
3. Retrieve Data - Ad Hoc Batch
4. Browse Data - Online
Please enter Selection:
NEED ASSISTANCE?
CALL THE AQS HOTLINE AT 1-800-333-7909
PF3=end(profile)
PF4=subsystem menu
PF5=terminate
Figure 3-11. The AIRS AQS Main Menu
The AIRS AQS main menu appears after the user profile is established.
Procedures
3-24
September 1993
-------
AIRS User's Guide
Volume AQ3 Air Quality Data Storage
Top Level User Procedures (continued)
3.6.3 User Profile Screen - Usage
To specify your user profile for AQ Data Storage processes, follow these instructions:
1. In the PASSWORD field, type the password for the screening file you plan to select for use during
this AIRS session. Use the password the AIRS database administrator gave you when you were
registered as an AIRS data storer. The password will not show on the screen when you enter it,
so type carefully! (If you think you made a mistake, tab to the start of the password field, press
the ERASE EOF key, and type the password again.)
2. The ACCOUNT CODE, PRINTER ID, and BIN NO fields show the values you specified to the
AIRS database administrator when you were registered as an AIRS user, or they have prototype
values. Since the prototype values for ACCOUNT CODE and BIN NO are not valid for use in
JCL, you should replace them. Use valid codes assigned to you by the computer center for account
and bin. (You also will be able to change the values for each batch job you submit, if you want
to.) If you want your output printed at the computer center, specify "RMTO" or "LOCAL" as the
printer-ID. Otherwise, specify the remote site-ID where you want it printed, such as "RMT321".
To send your output to the default printer at one of the logical mainframe computers, specify the
LMF's node number as the printer-ID ("N7" for example). To send your output to a remote
printer attached to an LMF, specify both the node number and the remote-ID ("N7R100" for
example).
3. Select an Air Quality screening file from the list at the middle of the screen. Using the TAB or
NEW LINE key, move the cursor to the selection field beside the name of the file you want, then
type "x" (or any other character but space). If the message "PF8=MORE" is displayed in the
lower left corner of the screen, more screening files are available that would not fit on the current
screen. Press the PF8 key to see them. (If you press PF8 when there .are not more files available,
the message "NO SCREENING FILES REMAINING" is displayed at the top of the screen.)
4. Press the ENTER key. If all your user profile specifications are valid, the AIRS main menu screen
will appear. If you erased the value from one of the JCL fields, the message "field CANNOT BE
BLANK" appears at the top of the user profile screen, where field refers to account, printer-ID,
or bin number. If you selected more than one AQ screening file, the message "TOO MANY AIR
QUALITY SCREENING FILES SELECTED" is displayed. Correct the error and press the
ENTER key again. '
You may use the PF3 or FP4 key to return to the AIRS main menu or the PF5 key to terminate your
AIRS session (and NATURAL). If you use any PA or PF key other than PF3, PF4, PF5, or PF8, the
message "NATlOll REQUESTED FUNCTION KEY NOT ALLOCATED" is displayed at the top of
the screen.
September 1993 3-25 Procedures
-------
Air Quality Data Storage
AIRS User's Guide
Volume AQ3
05/25/89
f>F3=end
AIRS Air Quality Subsystem 4APOOOA
Main Menu
1. Submit Data
2. Retrieve Data - Standard Batch
3. Retrieve Data - Ad Hoc Batch
4. Browse Data - Online
Please enter Selection: 1
NEED ASSISTANCE?
CALL THE AOS HOTLINE AT 1-800-333-7909
PF4=subsystem menu PF5=terminete
03/06/90
AIRS Air Quality Subsystem
Submit
AMP002
Enter Selection:
1 LOAD Input Transactions to Screening File
2 EDIT Screening File (Batch Execution)
3 CORRECT Screening File (Online Adds, Changes, Deletes)
4 NOTIFY AIRS Data Base Administrator for UPDATE
5 RECEIVE Messages
6 DELETE all Transactions from Screening File
PF3=end
PF4=subsystem menu
PF5=terminate
Figure 3-12. The AQ Data Storage Subsystem (Submit) Menu
The AQ "submit" menu appears after selecting option 1 of the AIRS AQS main menu.
Procedures
3-26
September 1993
-------
AIRS User's Guide
Volume AQ3 Air Quality Data Storage
Top Level User Procedures (continued)
3.6.4 AIRS AQS Main Menu
The AIRS AQS main menu is used to select the type of Air Quality function (data storage or retrieval)
you want to do. The main menu is shown at the top of Figure 3-12.
The instructions for using the main menu screen to select the Air Quality Data Storage Subsystem are
very simple:
1. After the ENTER SELECTION prompt, type " 1" and then press the ENTER key. This selects the
"submit AQ data" function of AIRS. (An ADBA using this screen would also be able to choose
an "update AQ data" function, which uses the data you have prepared with the submit function to
update the AIRS database.)
2. If you entered the selection correctly, the "submit" menu of the AQ Data Storage Subsystem will
be displayed. It is shown at the bottom of Figure 3-12.
3. If you did not select a screening file on the user profile screen, the message "NO SCREENING
FILE SELECTED ENTER PF3 TO SELECT ONE" is displayed at the top of the main menu
screen when you select option 1. Return to the user profile screen (see instructions below) and
select a screening file.
4. If you entered the wrong main menu selection, a different menu will be displayed. Press PF3 to
return to the AIRS AQS Main Menu, specify option "1", and press ENTER.
5. If you entered an invalid selection, the message "INVALID SELECTION - RE-ENTER" is
displayed at the top of the screen. Carefully type "1" in the selection field and press ENTER.
If you want to go "up" from the main menu screen to the AIRS AQS user profile screen, the instructions
are equally simple:
1. Press the PF3 key while the main menu is displayed. The user profile screen will appear.
To return to the AIRS main menu:
1. Press the PF4 key while the AQS main menu is displayed. The AIRS main menu will be
displayed.
You can also use the PF5 key to terminate your AIRS session (and your NATURAL session) while the
AQS main menu is displayed. If you use any other PF or PA key, the message "NAT1011
REQUESTED FUNCTION KEY NOT ALLOCATED" is displayed at the top of the screen.
September 1993 3-27 Procedures
-------
Air Quality Data Storage
AIRS User's Guide
Volume AQ3
05/25/89
AIRS Air Quality Subsystem ANP002
Suberit
Enter Selection:
1 LOAD Input Transactions to Screening File
2 EDIT Screening file (Batch Execution)
3 CORRECT Screening File (Online Adds, Changes, Deletes)
4 NOTIFY AIRS Data Base Administrator for UPDATE
5 RECEIVE Messages
6 DELETE all Transactions from Screening File
PF3=end
PF4=main menu
PF5=terminate
05/25/89
AIRS Air Quality Subsystem
JCL Parameters for LOAD Batch JOB
AMP002
ENTER:
PF3=«nd
Data Set Name
•Tape Number
Screening File Id
JOB Name
Account Code/UID
Time (MM , SS)
Priority
Message Class
Number of Copies
•Form Number
Room/Bin Number
Hold Output (Y/N)
Printer Site Id
ANADBF96
SFP LOAD1
ASWD AIRSP
03,00
2
A
01
6132
N
RMTOOO
Press ENTER to submit JOB
PF4=mein menu
PF5=terminate
Figure 3-13. Using the AQ Data Storage Submit Menu
The LOAD job submission screen appears after selecting submit menu option 1.
Procedures
3-28
September 1993
-------
AIRS User's Guide
Volume AQ3 Air Quality Data Storage
Top Level User Procedures (concluded)
3.6.5 AQ Data Storage Submit Menu
The AQ submit menu is the last screen of the Top Level User Session. It is used to select which of the
Data Storage processes you want to use: LOAD, EDIT, CORRECT, NOTIFY, MESSAGE, or DELETE.
The submit menu is shown at the top of Figure 3-13.
To select one of the AQ Data Storage processes listed on the submit menu, follow these instructions:
1. After the "ENTER SELECTION:" prompt, type the selection number of the process you want to
use, then press the ENTER key. The selection number is displayed beside the name of each
process on the submit menu screen. To select the LOAD process, for example, you would type
the number "1".
2. If you entered the selection correctly, the first screen of the process you chose will be displayed.
For example, if you chose LOAD, the screen for submitting a LOAD batch job could be displayed
(as shown in Figure 3-13).
3. If you did not enter a valid selection number, the message "INVALID SELECTION - RE-ENTER"
is displayed at the top of the screen. Carefully type one of the available selection numbers and
press the ENTER key.
The following PF keys are active while the AQ submit menu screen is displayed:
PF3 invokes the AIRS AQS main menu
PF4 also invokes the AIRS AQS main menu
PF5 terminates the AIRS session (and NATURAL)
If you use any other PA or PF key, the message "NAT1011 REQUESTED FUNCTION KEY NOT
ALLOCATED" is displayed at the top of the screen.
September 1993 3-29 Procedures
-------
AIRS User's Guide
Air Quality Data Storage Volume AQ3
06/13/87 AIRS ERROR 12:10:28
AN AIRS Program detected a NATURAL Error.
Record the information shown below and call the ADDA.
ERROR NUMBER: 82
ONE NUMBER : 1420
PROGRAM NAME: AMP090A
•Press ENTER to terminate.
Figure 3-14. The AIRS Error Screen
Procedures 3-30 September 1993
-------
AIRS User's Guide
Volume AQ3 Air Quality Data Storage
02/25/93 AIRS Air Duality Subsystem AMP002
LOAD JOB Disposition For Screening File XANADBF96
UNABLE TO SUBMIT BATCH JOB
INTERNAL CARD READER IS BUSY
PRESS ENTER TO RETRY
PF3=end PF4=main menu PFS-terrainate
Figure 3-15. Job Disposition (Error) Screen
September 1993 3-31 Procedures
-------
Air Quality Data Storage
AIRS User's Guide
Volume AQ3
05/25/89
PF3=ehd
AIRS Air Quality Subsystem
LOAD JOB Muaber For Screening File ANADBF96
AMP002
JOB Status: JOB 2675 Submitted
:PF4=main menu
PF=terminate
Figure 3-16. Job Number Screen
Procedures
3-32
September 1993
-------
AIRS User's Guide
Volume AQ3 Air Quality Data Storage
3.6.6 Batch Job Submission
The batch job submission process generates a batch jobstream to execute the user-selected Submit batch
option (LOAD, EDIT). The jobstream contains the control cards (JCL) and other information needed
to execute the batch submit option you requested. Since the details of the jobstream are unique to each
batch submit option, each one has its own job submission program.
If submission of the batch job occurs without error, the job submission process displays a "job number"
screen, as shown in Figure 3-16. This is the normal course of events; errors in the job submission
process are very rare.
Only if the job submission fails does the job submission process display a "job disposition" screen as
shown in Figure 3-15. The screen briefly describes the error condition and suggests what you should do
in order to proceed. There are basically two error conditions: the account number you used is not valid,
or something is wrong with the "internal card reader", which is the part of the computer operating system
that reads the submitted jobstream and turns it into a batch job. If the account code is wrong, you must
return to the JCL parameters screen and correct it. If the internal card reader is busy, you may be
successful if you try the job submission again (by pressing ENTER). If the internal card reader is
"unavailable", trying again to submit the job is not likely to be fruitful; you will have to try at another
time.
You can use the following PF keys to exit from the job disposition screen:
PF3 return to the AQ report selection menu
PF4 return to the AIRS AQS main menu
PF5 terminate the AIRS session
Using any of these PF keys terminates your submit request; a job will not be submitted.
Error Messages
The following error messages may appear on the job disposition screen:
INTERNAL CARD READER IS BUSY
PRESS ENTER TO RETRY
The internal card reader may be temporarily overloaded. Press the ENTER key to try the job
submission again. If the failure persists, try again at a later time.
INTERNAL CARD READER IS UNAVAILABLE
PRESS ENTER TO RETRY
Something is wrong with the internal card reader. Although you can try to submit the job again,
that is unlikely to be successful. You should inform the AIRS database administrator if this error
occurs.
September 1993 3-33 Procedures
-------
AIRS User's Guide
Air Quality Data Storage Volume AQ3
USER ACCOUNT CODE IS INVALID
PRESS PF3 AND TRY AGAIN
The account code you specified is not valid for your user-ID. Return to the JCL parameters screen
and specify a valid account code.
Procedures 3-34 September 1993
-------
AIRS User's Guide
Volume AQ3 Air Quality Data Storage
3.6.7 Error Handling
The programs of the top level user session and the AQ data storage processes are designed to detect
errors and take appropriate action. But not all error conditions could be anticipated during program
design, and some can not be "fixed" by you or the program. Such error conditions might arise due to
a flaw in the program, internal problems with the database or NATURAL, or hardware malfunctions.
If one of these "abnormal" errors occurs while you are using an online program, one of two things will
happen. If the error condition is relatively benign, a message will appear at the top of the screen that
includes "NATxxxx", where "xxxx" is a NATURAL error number. (An example of this is the message
you get sometimes when you use an invalid PF key.) Try to interpret the message and take the action
necessary to correct the error.
If the error condition is serious enough to disrupt normal program operation, the AIRS error screen
shown in Figure 3-17 will appear. (The CORRECT process uses a different screen format.) There is
nothing you can do to recover from an error when this screen appears. Write down the information on
the screen (or print a screen image), press ENTER to terminate your AIRS session, and contact the AIRS
database administrator.
September 1993 3-35 Procedures
-------
AIRS User's Guide
Air Quality Data Storage Volume AQ3
01/20/87 AIRS Air «uality Subsystem MESSAGE
Messages for Screening File S55AQA02
Date Time User —- ---Message Text
K 01-07 20:24 USR EDIT failed - an ADABAS error occurred for JOB 'USREDITV.
D 01-08 09:38 DOU LOAD failed - Screening File 'SS5AQA02' was locked.
0 01-08 12:42 DOU LOAD unsuccessful - Input Transaction File was empty.
D 01-08 19:11 DOU LOADed 00002704 records into Screening File 'SS5AQA02'.
D 01-09 13:27 DOU EDITed 00002704 records in Screening File 'S55AQA02'.
NO MORE MESSAGES
:D,k=msg disp PF8=next PF3=end PF4=main menu PF5=tertninate PA1=oops
Figure 3-17. Sample MESSAGE Screen
Procedures 3-36 September 1993
-------
AIRS User's Guide
Volume AQ3 Air Quality Data Storage
3.7 Batch Processing
The LOAD and EDIT data storage processes do their work as batch jobs iinstead of performing their
functions online like the other AQ data storage processes. This section explains how to tell when a
LOAD or EDIT batch job has executed and whether it completed its function successfully.
3.7.1 Checking Batch Job Status
The MESSAGE process of the AQ Data Storage Subsystem is the method provided by AIRS for
determining if a batch job you submitted has finished. Detailed instructions for using MESSAGE are
presented in a subsequent section of this manual, but the essential information is that each batch process
stores a message you can retrieve. The message says whether the process did or did not successfully
complete its work and includes the date and time when the process ended. Thus, a simple way to check
the status of a LOAD or EDIT job is to use the MESSAGE process. A sample MESSAGE screen is
shown in Figure 3-17.
The other methods for checking the status of batch jobs are not part of AIRS. They are the SYSD
processor, available under CICS, and the SDSF processor, available under TSO/ISPF. Although these
two facilities are more complicated to use than the MESSAGE process, they are also much more
versatile. In addition to providing comprehensive information about batch job status, they allow you to
view the output of a batch job on your terminal and route the output to alternate destinations.
Rudimentary instructions for using the SYSD and SDSF processors are presented below.
September 1993 3-37 Procedures
-------
Air Quality Data Storage
AIRS User's Guide
Volume AQ3
J £ S 2 JOB LOG - SYSTEM E P A 2 .. NODE NCCIBM1
12.14.04 JOB22463 IEF677I WARNING NESSAGE(S) FOR JOB JVMSGCST ISSUED
12.14.OS JOB22463 ICH70001I JVM LAST ACCESS AT 12)05:04 ON WEDNESDAY. SEPTEMBER 29. 1993
12.14.05 JOB22463 JHASP373 JVMSGCST STARTED - INIT 22 - CLASS Z - SVS EPAG
12.14.13 JOB22463 NCC802I JVMSGCST ENDED 09/29/93. CODE 0. ELAPSED t06. CPU iQO. EXCPS
12.14.13 JOB22463 JHASP395 JVMSGCST ENDED
— JES2 JOB STATISTICS
29 SEP 93 JOB EXECUTION DATE
59 CARDS READ
435 SYSOUT PRINT RECORDS
0 SYSOUT PUNCH RECORDS
28 SYSOUT SPOOL KBYTES
0.13 MINUTES EXECUTION TIME
NCC900I
NCC904I JOB22463 JVMSGCST STEP JS30.STEP1
NCC900I
NCC906I START 09/29/93 12:14:07 STOP 09/29/93 12:14:12 ELAPSED
NCC900I
NCC908I TCB :00.13, SRB :00.01, VEC :00.00,
NCC908I AOABAS :00.06 TOTAL
NCC900I
NCC910I I/O COUNTS: DA 1. MT 0. OTHER 0.
NCC910! ADABAS 46 TOTAL
NCC900I
NCC912I I/O BY DDNAME(UNIT) CMWKF02(ACB) : 1
NCC900I
NCC914I REGION USAGE: REGION REQUESTED
NCC914I BELOW 2972K. SYS 236K; ABOVE 4K. SYS 9596K; TOTAL
NCC900I
NCC916I PAGING COUNTS:
NCC916I IN: 0, VIO 0, SWAP 0, HSPACE 0 TOTAL
NCC916I OUT: 0. VIO 0. SWAP 0. HSPACE 0 TOTAL
NCC900I
NCC918I STEP CHARGES AT PRTY 2 (FACTOR-1)
NCC918I CPU :00.20 » {564.00/HR
NCC918I I/O 47 » $.12/1000
NCC918I
NCC918I TOTAL COST:
NCC900I
CC: 0
:05
:00.20
nn 47
7000K
12808K
0
0
$.03
$.01
$.04
Figure 3-18. Sample Batch Job Log and Step Summary Reports
Procedures
3-38
September 1993
-------
AIRS User's Guide
Volume AQ3 . Air Quality Data Storage
3.7.2 Checking Batch Job Output
The primary means of determining whether a batch job executed successfully, and whether it did what
you wanted it to, is the printed output of the job. This includes both the reports generated by the AIRS
programs and the job control information generated by the computer operating system.
One of the first things you should check is the "JES2 job log", which is printed at the beginning of the
output of all batch jobs. A sample job log is shown at the top of Figure 3-18. The format of the job log
varies somewhat depending on the type of error and its cause, but if you see 'the word "abend" or a non-
zero condition code (shown as "CC=####), there was an error of some type and the batch job probably
was not successful. You should check the summary report for each step of the job to determine when
the error occurred. A sample step summary report is shown at the bottom of Figure 3-18. Contact the
AIRS database administrator or the computer center user support group for help with finding the cause
of the error and a way to avoid it.
An error condition that is detected and acted upon by an AIRS program may not result in a non-zero
condition code. Both LOAD and EDIT generate summary reports which you should examine. The
reports summarize what was done if the program executed successfully, or they identify an error
condition. Examples of the LOAD and EDIT summary reports are shown in Figures 3-19 and 3-20.
Each page shows a "good" report at the top and a "bad" report at the bottom. For some errors you
should contact the AIRS database administrator, as with the sample EDIT report. Other errors are self-
explanatory, such as the one shown in the sample LOAD report.
In most instances, your LOAD and EDIT batch jobs will be successful; errors during execution are
uncommon. Even when there are no operational errors, you still need to look carefully at the reports
LOAD and EDIT produce to make sure the results are what you expected. For example, if you expected
to process ten thousand records with LOAD but the summary report says only one hundred records were
actually processed, you need to investigate the cause of the discrepancy.
September 1993 3-39 Procedures
-------
AIRS User's Guide
Air Quality Data Storage Volume AQ3
09/30/93 AEROMETRIC INFORMATION RETRIEVAL SYSTEM PAGE: 1
AMP010 • AIR QUALITY SUBSYSTEM
LOAD SUMMARY REPORT
FOR SCREENING FILE ANAOBA10
INPUT TRANSACTION FILEi ASWJ.TRAINING.TESTDATA.NEW 1ST VOLUME: USS199
TRANSACTION TYPE NUMBER
11
7
14
224
111
104
120
12
1
TOTAL 604
SITE
MONITOR
SLAMS
HOURLY
DAILY
COMPOSITE
PRECISION
ACCURACY
INVALID
A1-A7
F1-F5
M.N.P.R-V
1
2
3
8
9
09/30/93 AEROMETRIC INFORMATION RETRIEVAL SYSTEM PAGE: 1
AMP010 AIR QUALITY SUBSYSTEM
LOAD SUMMARY REPORT
FOR SCREENING FILE ANADBA10
INPUT TRANSACTION FILE: JVMASUD.TEMP.SR839B 1ST VOLUME: USS1B7
ERROR: THE SCREENING FILE COULD NOT BE ACCESSED BECAUSE IT WAS IN USE.
Figure 3-19. Sample LOAD Summary Reports
Procedures 3-40 September 1993
-------
AIRS User's Guide
Volume AQ3
Air Quality Data Storage
09/30/93
AMP050
AEROMETRIC INFORMATION RETRIEVAL SYSTEM
AIR QUALITY SUBSYSTEM
EDIT SUMMARY REPORT
FOR SCREENING FILE ANAOBA10
PAGE:
TRANSACTION TYPE
•TRANSACTIONS PRESENTLY AT EDIT LEVELS-
-LEVEL 0- -LEVEL 1- -LEVEL 2-
SITE1
SITE2
SITE3
SITE4
SITES
SITES
SITE?
MONITORl
MONITOR?
MONITOR3
MONITOR*
SLAMS PM
SLAMS PM
SLAMS PM
SLAMS S02
SLAMS S02
SLAMS CO
SLAMS CO
SLAMS N02
SLAMS N02
SLAMS 03
SLAMS 03
SLAMS PB
HOURLY
DAILY
COMPOSITE
PRECISION
ACCURACY
INVALID
Al
A2
A3
A4
AS
A6
A7
Fl
F2
F3
F«
M
V
N
P
V
R
V
S
V
T
V
U
1
2
3
8
9
TOTAL
1
2
2
1
0
0
0
1
2
1
0
0
1
0
1
0
0
1
0
1
0
1
0
4
4
52
0
0
1
76
1
0
0
0
1
0
0
1
0
0
2
1
0
1
0
1
1
0
1
0
1
0
0
2
0
0
0
0
0
13
0
0
0
0
0
1
1
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
122
51
0
0
0
0
175
PASSED ALL
-EDIT LEVELS-
0
0
1
0
0
0
0
0
0
0
0
0
0
0
1
1
0
0
0
0
0
0
1
96
56
52
120
12
0
340
USER
•EXCLUDED-
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
--TOTAL--
2
2
3
1
1
1
1
2
2
1
2
1
1
1
2
2
1
1
1
1
1
1
1
224
111
104
120
12
1
604
09/30/93
AMP050
AEROMETRIC INFORMATION RETRIEVAL SYSTEM
AIR QUALITY SUBSYSTEM
EDIT SUMMARY REPORT
FOR SCREENING FILE ANADBA10
PAGE:
ERROR: THE EDIT COULD NOT BE DONE BECAUSE OF AN ADABAS ERROR. PLEASE KEEP THIS REPORT AND NOTIFY THE AIRS DATABASE ADMINISTRATOR.
CONTROL-BLOCK
COMMAND-CODE
COMMAND-ID
FILE-NUMBER
RESPONSE-CODE
ISN
ISN-LOWER-LIHIT
ISN-QUANTITY
FORMAT-BUFFER-LENGTH
RECORD-BUFFER-LENGTH
SEARCH-BUFFER-LENGTK
VALUE-BUFFER-LENGTH
L4
TFD5
0022
0009
00000094
00000000
00000000
0021
0005
0001
0001
ISN-BUFFER-LENGTH
COMMAND-OPTION-1
COMMANO-OPTION-2
AODITIONS-1
ADDITIONS-2
FIELD-IN-ERROR
BYTE-IN-ERROR
ADDITIONS-3
ADDITIONS-4
COMMAND-TIME
USER-AREA
0004
0000
*•**
•-E
00000000
AS
1234567690123456789012345678901234567890
FORMAT-BUFFER • BB,1,A,BC.3,U.BD.1,A.
RECORD-BUFFER •
SEARCH-BUFFER • .
VALUE-BUFFER •
Figure 3-20. Sample EDIT Summary Reports
September 1993
3-41
Procedures
-------
Air Quality Data Storage
AIRS User's Guide
Volume AQ3
ZZMWtPt U.S. Environmental Protection Agency
Hews Alert I User New Facility
XX XX XXXXXX XXXXXX XX XXXXXX XXXXX
XXX XX XXXXXXXX XXXXXXXX XX XXXXXXXX XXXXX
XXXX XX XXX XXX XX XXX XXX
XX XX XX XXX XXX XX XXX XXX
XX XX XX XXX XXX XX XXX XXX
XX XXXX XXX XXX XX XXX XXX
XX XXX XXXXXXXX XXXXXXXX XX XXXXXXXX XXXXX
XX XX XXXXXX XXXXXX XX XXXXXX XXXXX
Please enter selection or command and then press ENTER.
1. INFORMATION News Alerts and User Memos
2. SIGN-ON Change CICS Sign-on Parameters
3. APPLICATIONS EPA Applications Menu for CICS
«. EXIT Exit CICS and return :to EPA Menu System
Command »«»> sysd ;V
F1/F13=Help F3/F15=Exit F10/F22=Lock F12/F24=CICS
Date:
Tine:
Terminal:
XXXXXX
XXXXXXXX
XXX
XXX
XXX
XXX
XXXXXXXX
XXXXXX
03/26/91
13:16:16
H0422232
XXXXXX
XXXXXXXX
XXX
XXX
XXX
XXX
XXXXXXXX
XXXXX
INPUT ===>
0 -PARKS
1 - BROWSE
2 - EDIT
3 - UT1L
4 - ACTIVE
5 - N
6 • 0
7 • PRINTER
8 - JFT
C - CICS
T • TUTORIAL
U -USER
X - END
CPMS/SYSD PRIMARY OPTION MENU
- Specify CPMS/SYSD parameters
- Display source data
• Create or change source data
-:Perform utility functions
- Display active jobs
- Display jobs in the input and output queues
- Display jobs in the output queue
-Display/change a printer's status
- Job/file tailoring
-ENTER CICS transactions
-Display information about CPMS/SYSD
•Perform user file maintenance
-Terminate CPMS/SYSD session
(1/1)
SCROLL: CSR
USER - PKBASWD
DATE - 6/18/93
TIME - 13:12:04
TERMINAL - P43C
PRESS END KEY TO TERMINATE CPHS/SYSD.
Figure 3-21. SYSD Primary Option Menu
The SYSD processor displays its primary option menu when it is invoked.
Procedures
3-42
September 1993
-------
AIRS User's Guide
Volume AQ3 Air Quality Data Storage
3.8 Checking Batch Jobs With SYSD
Of the two non-AJRS facilities for monitoring batch jobs (SYSD and SDSF), the SYSD processor may
be the more convenient since it runs under CICS like AIRS. That means you do not have to logoff from
CICS and logon to TSO in order to check the status of your LOAD or EDIT jobs. You do have to end
your AIRS session.
The instructions for using SYSD presented here are, of necessity, rather superficial. This manual can
not include a complete description of all the SYSD capabilities and options. However, these instructions
should be sufficient to allow you to check the status of a batch job and to view its output with SYSD.
3.8.1 Invoking SYSD
You invoke SYSD from CICS. That means you can invoke it after you have completed the CICS logon
procedures described earlier in this section, or after you have terminated your AIRS session. To invoke
SYSD, simply type "sysd" on the screen, press the ERASE EOF key, then press the ENTER key.
3.8.2 The SYSD Primary Option Menu
The first screen SYSD displays is the "primary option menu", shown in Figure 3-21. You use it to
invoke the various things SYSD can do, just as you use the AIRS main menu to select the various things
AIRS can do. You select one of the options listed on the menu by typing its code or name after the
"INPUT = = = >" prompt, then pressing the ENTER key. To select the "display active jobs" option,
for example, you could type either the code "4" or the name "active".
The first time you use SYSD, you should select the first menu option, "specify CPMS/SYSD
parameters". This option is explained in Section 3.8.3. Use it to specify the categories of jobs SYSD
will display and the actions of PF keys.
SYSD menu options 4, 5, and 6 allow you to find out about batch jobs. Probably the most useful of
those is option 5, "display jobs in the input and output queues". With it you can determine your job's
position in the input and output queues and estimate when it will execute or print. You can also look at
the output generated by your jobs and route the output to the printer site of your choice.
September 1993 3-43 Procedures
-------
Air Quality Data Storage
AIRS User's Guide
Volume AQ3
INPUT
CPHS/SYSO PARAMETER OPTIONS
GENERAL
1IST
PF
JFTPANEL
OUEUID*
PRINTPRM
END
Display/change general parameters
Display/change JES and lift defaults
Display/change PF key assignments
Set initial JFT panel display
Set GET/PUT TS queue identifiers
Set PRINT parameters
Return to main menu
SCROLL: CSR
USER PKBASWD
DATE • 6/18/93
TINE - 13:12:41
TERMINAL - P43C
INPUT ===>
JES/LIST PARAMETER DEFINITIONS
(1/1)
SCROLL: CSR
USER - PKBASUD
PRINT CONTROL:
Printer identifier ==>
JOB SELECTION CRITERIA:
Job prefix ==> PKB*
Class ==> *
Destination ==>
Display SYSIN -=> N
JOB STATEMENT INFORMATION:
xs>
==>
==>
»=>
Printer display (Cpms/Jes2) ==> C
USE:
Y
N
N
Display TSO/STC ==> N
Figure 3-22. Specifying SYSD Job Selection Parameters
Procedures
3-44
September 1993
-------
AIRS User's Guide
Volume AQ3 . Air Quality Data Storage
3.8.3 Setting Your SYSD Profile
The first time you use SYSD you should choose option zero ("parms") and establish your SYSD profile
settings, especially the parameters relating to selection of batch jobs. SYSD saves your profile and recalls
it whenever you use SYSD. For our purposes, the most important part of your profile is the set of
parameters for selecting which batch jobs SYSD displays when you use the job display options of the
SYSD primary menu. Essentially, you can choose to see all jobs or just your own. Since SYSD does
not have a "find" command that would allow you to locate your job(s) in the list of all jobs, it is probably
better to limit the display to just your jobs.
When you select the "parms" option of the primary menu, SYSD displays the parameter options menu
shown at the top of Figure 3-22. Choose the "display/change JES and list defaults" option by typing " 1"
after the "INPUT = = = >" prompt, then press the ENTER key. The screen titled "JES/list parameter
definitions" will appear next. A sample is shown at the bottom of Figure 3-22. Use the following
instructions to specify your SYSD profile:
1. Tab to the SCROLL field at the top right corner of the screen and type "page". With this setting,
job lists and job output scroll up or down by one screenful when you use the PF7 or PF8 keys.
(You could also enter "half, which scrolls by half a screenful.)
2. Tab to the JOB PREFK field at the middle of the screen and type your NCC-IBM user-ID
followed by an asterisk (*). Then tab to the next field, which is under the USE heading, and type
"y". With these two specifications, SYSD displays only your jobs when you choose options 4, 5,
or 6 from the primary menu. If at some time you want to display all jobs, simply return to the
JES/list parameter definition screen and change the "y" following your user-ID to "n".
3. If you want to further restrict job selection, you can type values for the CLASS and
DESTINATION fields and enter "y" under the USE heading. Otherwise, type "n" in the USE
column for those two fields.
4. Enter "n" for the two fields labeled DISPLAY SYSIN and DISPLAY TSO/STC.
5. Press the PF3 key. This causes SYSD to check your specifications, save them, and return to the
SYSD parameter options menu. Press PF3 again to return to the primary menu.
6. If an error message appears on the screen when you press PF3, try to correct the problem and press
ENTER. You can press the PF1 key to obtain SYSD online help. If that is not sufficient, contact
the computer center for assistance.
September 1993 3-45 Procedures
-------
Air Quality Data Storage
AIRS User's Guide
Volume AQ3
CPMS/SYSO PRIMARY OPTION MENU
INPUT
0 - PARMS - Specify CPMS/SYSO parameters
1 - BROWSE - Display source date
2 - EDIT - Create :or change source data
3 - UTIL • Perform utility functions
4 » ACTIVE - Display active jobs
5 - N - Display jobs in the input and output queue
6-0 - Display jobs in the output queue
7 - PRINTER - Display/change a printer's status
8 - JFT - Job/file tailoring
C - CICS - ENTER CICS transactions
T - TUTORIAL - Display information about CPMS/SYSD
U - USER - Perform user file maintenance
X -:END - Terminate CPMS/SYSD session
PRESS END KEY TO TERMINATE CPMS/SYSD.
SCROLL: CSR
USER - PKBASUD
DATE - 6/18/93
TIME - 13:12:04
TERMINAL - P43C
MVS/JES2 JOB QUEUE DISPLAY
INPUT ===>
(1/1)
SCROLL: PAGE
JOB* JOBNAME
T3913 MAK
J5559 MAK950
J2396 MAKLIST
J4322 MAK950
STA
TSU
A**
PPU
PPU
XHA
PR I
15
9
1
1
HELD
PRT
LOCAL
HOLD
R0321
HOLD
PUN
LOCAL
LOCAL
R0321
LOCAL
END OF DATA
A=release C*cancel D=delete H=hold P=print S=select T=route V=view
Figure 3-23. The SYSD Job Queue Display Screen (Option 5)
Procedures
3-46
September 1993
-------
AIRS User's Guide
Volume AQ3 Air Quality Data Storage
3.8.4 SYSD Job Queue Display Screen - Description
You can determine which batch jobs are waiting to execute (the input queue) and which jobs are waiting
to print (the output queue) using option 5 (or "N") of the SYSD primary option menu. A sample of the
SYSD "job queue display" screen is shown in Figure 3-23.
If your SYSD profile is set as recommended on the previous page, only your own jobs are displayed.
Otherwise all jobs are shown (or the subset you selected), and you must scroll through the list using the
PF8 (down/forward) and PF7 (up/backward) keys to fold your own jobs. There is no command for
finding a particular job or type of job in the list.
The identity and status of jobs are presented in several columns across the job queue display screen. The
following information is displayed:
0 The options column, explained below.
JOB# The job number assigned by the computer system.
JOBNAME The job name you chose when you submitted the job.
STA Status of the job. The two usual status codes are:
x** The job is in the input queue for job class "x" (A** for class A, for
example), and is either awaiting execution or is executing, as indicated by
the XHA column (see below).
PPU The job has executed and is in the print/punch output queue.
XHA Additional job status information. The two usual values are "W", meaning the job
is waiting to execute, and "1", meaning the job is executing on CPU number 1.
PRI The priority of the job within its queue.
HELD The number of held datasets in the job's output.
PRT,PUN The destination of printed (PRT) and punched (PUN) output.
Near the top of screen, to the right of "INPUT = = = >", is the command entry field. It is not
particularly useful, since nearly all commands have a PF key equivalent that is more convenient to use.
At the bottom of the screen is a list of the operations you can perform on your own jobs. These are
described on subsequent pages. You can not apply any of the operations to jobs that are not yours.
(Your jobs have your user-ID as the first three characters of the jobname.)
September 1993 3-47 Procedures
-------
AIRS User's Guide
Air Quality Data Storage Volume AQ3
3.8.5 SYSD Job Queue Display Screen - Usage
When your jobs are listed on the screen you can perform the functions shown at the bottom of the screen
(except PRINT, which does not work). To use one of the functions:
1. Tab to the options field (the "0" column) beside the job of interest.
2. Type the letter code of the function you want to use. The cursor will automatically move to the
PRT column.
3. For the ROUTE function only, type the desired destination of your output in the PRT column,
replacing what was there. (Use site-IDs such as "LOCAL", "R321", or "N7R100", as discussed
previously in the instructions for the AIRS user profile screen.)
4. Press the ENTER key.
Now comes the tricky part: the screen does not show the effects of what you did! It appears as if the
function you entered was completely ignored. If you wait about five seconds and press ENTER again,
however, the effects will show. This odd behavior results from measures implemented by the computer
center to make SYSD operate efficiently. Although SYSD processes your command right away, it only
"reads" the status of your jobs about every five seconds. So when using SYSD, you will almost always
have to press ENTER once to issue a command, then press ENTER again a few seconds later to see the
results.
If you make a mistake, SYSD displays an error message under the "INPUT = = = > " prompt. Suppose,
for example, you typed the wrong function code beside a job. After you press ENTER, SYSD displays
the error message "E0002 - ONE OR MORE INVALID LINE OPTIONS WERE FOUND" and
highlights the invalid function code. At this point, the only tab stop in the options column is the place
where the invalid code was entered. If you simply press ENTER, the invalid code is erased and the
screen returns to normal with a tab stop beside each job listed. Or you can tab to the invalid code,
change it, then press ENTER. In this case, the new code you entered is processed.
When you have finished using the SYSD job queue display screen, press the PF3 (END) key to return
to the primary option menu. Alternatively, you can use the primary command field (at the "INPUT
= = = > " prompt) to transfer directly to another option of the primary menu or to terminate SYSD. To
transfer to the job output display screen (option 6), for example, you could type " =6" and press ENTER.
To terminate SYSD, you could type "=X" and press ENTER. If you enter an invalid command, SYSD
displays the message "E0001 - INVALID PRIMARY COMMAND (ENTER ASSUMED)" and clears
the primary command field.
Procedures 3-48 September 1993
-------
AIRS User's Guide
Volume AQ3 Air Quality Data Storage
3.8.6 SYSD Job Queue Display Screen - Functions
Eight functions are listed at the bottom of the SYSD job queue display screen. Brief descriptions of the
functions are given below.
ROUTE (T) - changes the destination of job output. Probably the most common use for this feature
is printing the "held" output of a job, which is identified by "HOLD" in the PRT column of the
display. To print held output, tab to the "0" column beside the job and type V, type "local" or
a remote site-ID such as "r321" in the PRT column, then press ENTER. The screen will appear
unchanged, as discussed above. After about five seconds, press ENTER again and the print
destination you entered should be displayed in the PRT column.
CANCEL (C) - removes a job from the input queue or aborts a job that is executing. Its output is
placed in the output queue. This function has no effect on jobs in the output queue.
DELETE (D) - does the same thing as CANCEL and also deletes the job's output from the output queue.
This function is irreversible; once you have deleted the output it can not be recovered.
HOLD (H) - retains a job in its present queue, either input or output. A held job in the input queue
will not be executed; one in the output queue will not be printed. The hold condition is removed
by RELEASE.
RELEASE (A) - reverses the effect of the HOLD function. This makes a job in the input queue
available for execution or a job in the output queue available for printing. Note: If you submitted
an AIRS batch job and specified that the output was to be held, you can not print the output using
RELEASE. You must use the ROUTE function, described above.
PRINT (P) - is not implemented on the NCC-IBM computer system. Do noi: use it.
SELECT (S) - displays a list of a job's "print" datasets. These are the various parts of the printed
output, such as JCL listing and job log. This function can be used for jobs in either the input
queue or the output queue.
VIEW (V) - displays the content of a job's "print" datasets. This function can be used for jobs in either
the input queue or the output queue.
Unlike the other functions, the results of using SELECT and VIEW are displayed immediately. You do
not have to press ENTER twice to SELECT or VIEW a job's datasets. Moire information about using
SELECT and VIEW are presented in the description of SYSD's job output display screen, which begins
on the next page.
September 1993 3-49 Procedures
-------
Air Quality Data Storage
AIRS User's Guide
Volume AQ3
CPMS/SYSO PRIMARY OPTION MENU
0 - FARMS
1 - BROWSE
2 - EDIT
3 • UT1L
4 » ACTIVE
5 - N
6-0
7 • PRINTER
8 - JFT
C - CICS
T - TUTORIAL
U - USER
X - END
Specify CPMS/SYSD parameters
Di splay source data
Create or change source data
Perform utility functions
Display active jobs
Display jobs in the input and output queue
Display jobs in the output queue
Display/change a printer's status
Job/file tailoring
ENTER CICS transactions
Display information about CPMS/SYSD
Perform user file maintenance
Terminate CPMS/SYSD session
SCROLL: CSR
USER • PKBASVD
DATE - 6/18/93
TIME -13:12:04
TERMINAL - P43C
PRESS END KEY TO TERMINATE CPMS/SYSO.
INPUT «==>
0 JOB* JOBNAME C
J5751 HSW350S A
J2865 HSW350DU A
J4276 HSUC350 A
J4210 HSUC350 F
-* *END OF DATA*
MVS/JES2 JOB OUTPUT DISPLAY
(1/1)
SCROLL: PAGE
NOHSRU PP DEST
R 49 LOCAL
90 HOLD
00 HOLD
00 HOLD
FCB
****
FORM
STD
STD ****
STD ****
8381 8381
UCS
****
****
»**»
GT15
(KLINES GRPID
25K 1.1.1
356 1.1.1
4K 1.1.1
4K 1.1.1
Asrelease C»cancel D=delete H=hold P=pr?nt S=select T=route V=view
Figure 3-24. The SYSD Job Output Display Screen (Option 6)
Procedures
3-50
September 1993
-------
AIRS User's Guide
Volume AQ3 Air Quality Data Storage
3.8.7 SYSD Job Output Display Screen - Description
The SYSD "job output display" screen identifies which jobs are in the output queue and gives more
detailed information about mem than does the SYSD "job queue display". You invoke the job output
display screen with option 6 (or "0") of the SYSD primary option menu. A sample job output display
screen is shown on Figure 3-24.
If your SYSD profile is set as recommended previously, only your own jobs are listed on the job output
display screen. Otherwise all jobs are shown (or the subset you selected), and you must scroll through
the list using the PF8 (down/forward) and PF7 (up/backward) keys to locate your own jobs. There is
no command for rinding a particular job or type of job in the list.
The identity of jobs and information about them is presented in several columns across the job output
display screen. The following information is displayed:
0 The options column, in which you specify what you want to do.
JOB# The job number assigned by the computer system.
JOBNAME The job name you chose when you submitted the job.
C The job class assigned to your job by the computer system.
NOHSRU Status information. Each letter of the heading may appear beside a job to indicate
its status. The only two letters that are meaningful for AIRS are:
N - non-printable (set by the HOLD function, cleared by RELEASE)
R - currently printing
PP The priority of the job within its queue.
DEST The destination of the job's output.
FORM The form (type of paper) on which the output is to be printed.
FCB,UCS The forms control buffer and character set to be used for printing the job's output.
#LINES .. The number of lines in the job's output.
GRPID The group-ID assigned to the output by the computer system.
Near the top of screen, to the right of "INPUT = = = >", is the command entry field. It is not
particularly useful, since nearly all commands have a PF key equivalent that is more convenient to use.
September 1993 3-51 Procedures
-------
AIRS User's Guide
Air Quality Data Storage Volume AQ3
At the bottom of the screen is a list of the operations you can perform on your own jobs. These are
described below. You can not apply any of the operations to jobs that are not yours. (Your jobs have
your user-ID as the first three characters of the jobname.)
Procedures 3-52 September 1993
-------
AIRS User's Guide
Volume AQ3 Air Quality Data Storage
3.8.8 SYSD Job Output Display Screen - Usage
Using the job output display screen is much like using the job queue display screen. When your jobs are
listed on the screen you can perform the functions shown at the bottom of the screen (except PRINT,
which does not work). To use one of the functions:
1. Tab to the options field ("O" column) beside the job of interest.
2. Type the letter code of the function you want to use. The cursor will automatically move to the
"C" column.
3. For the UPDATE function only, tab to the DEST column and type the desired destination of your
output. Use a site-ID such as "LOCAL" or "R321".
4. Press the ENTER key.
The job output display screen exhibits the same odd behavior (and for the same reason) as described on
a previous page for the job queue display screen. That is, for any of the functions except SELECT or
VIEW, you have to press ENTER once to issue your command, wait five seconds for SYSD to "read"
the new status of your jobs, then press ENTER again to see the results.
If you make a mistake, SYSD displays an error message under the "INPUT = = = >" prompt. If you
enter an invalid function code beside a job, SYSD displays the error message "E0002 - ONE OR MORE
INVALID LINE OPTIONS WERE FOUND" and highlights the invalid function code. At this point, the
only tab stops on the screen are the primary command input field, the scroll amount field, and the field
in the options column where the invalid code was entered. If you simply press ENTER, the invalid code
is erased and the screen returns to normal with all its usual tab stops. Or you can tab to the invalid code,
change it, then press ENTER. In this case, the new code you entered is processed.
When you have finished using the SYSD job output display screen, press the PF3 (END) key to return
to the primary option menu. Alternatively, you can use the primary command field (at the "INPUT
= = = >" prompt) to transfer directly to another option of the primary menu or to terminate SYSD. To
transfer to the job queue display screen (option 5), for example, you could type "=5" and press ENTER.
To terminate SYSD, you could type "=X" and press ENTER. If you enter an invalid command, SYSD
displays the message "E0001 - INVALID PRIMARY COMMAND (ENTER ASSUMED)" and clears
the primary command field.
September 1993 3-53 Procedures
-------
AIRS User's Guide
Air Quality Data Storage Volume AQ3
3.8.9 SYSD Job Output Display Screen - Functions
The seven functions listed at the bottom of the SYSD job output display screen are mostly the same as
the functions described previously for the SYSD job queue display screen. Brief descriptions of the
functions are given below.
UPDATE (U) - allows you to change information about a job in any column where there is a tab stop.
The only recommended use for this feature is printing the "held" output of a job, which is
identified by "HOLD" in the DEST column of the display. To print held output, tab to the "0"
column beside the job of interest and type "u", tab to the DEST column and type "local" or a
remote site-ID such as "r321", then press ENTER. The screen will appear unchanged, as discussed
above. After about five seconds, press ENTER again and the print destination you entered should
be displayed in the DEST column.
DELETE (D) - deletes a job's output from the output queue so there is nothing to be printed. This
function is irreversible; once you have deleted the output it can not be recovered.
HOLD (H) - retains a job in the output queue, so its output is not printed. The hold condition is removed
by RELEASE.
RELEASE (A) - reverses the effect of the HOLD function, and makes a job's output available for
printing. Note: If you submitted an AIRS batch job and specified that the output was to be held,
you can not print the output using RELEASE. You must use the UPDATE function, described
above.
PRINT (P) - is not implemented on the NCC-IBM computer system. Do not use it.
SELECT (S) - displays a list of a job's "print" datasets. These are the various parts of the printed
output, such as JCL listing, job log, and reports generated by AIRS programs.
VIEW (V) - displays the content of a job's "print" datasets. Use this function to see the output generated
by one of your jobs.
Unlike the other functions, the results of using SELECT and VIEW are displayed immediately. You do
not have to press ENTER twice to SELECT or VIEW a job's datasets. More information about using
SELECT and VIEW is presented below.
Procedures 3-54 September 1993
-------
AIRS User's Guide
Volume AQ3
Air Quality Data Storage
INPUT ««*>
HVS/JES2 JOB OUTPUT DISPLAY
SCROLL: PAGE
0 JOB* JOBNAME C NOHSRU PP DEST
T575T HSU350S A
J2865 HSW3500U A
J4276 HSWC3SO A
J4210 HSWC350 F
J5147HSVC350 :•:-• F
*END OF DATA* *
49 LOCAL
90 HOLD
00 HOLD
00 HOLD
98 HOLD
FORM
STD
STD
STD
8381
838
FCB
•**•. -.•**•*
8381 GT15
8381 GT15
UCS fLUIES GRP1D
25K 1.1.1
356 1.1.1
2K 1.1.1
4K 1.1.1
4K 1.1.1
A=release D=delete H=hold P=print S=select U=update V=view
INPUT ='
0 DSN
CC
LOG
JCL
MSG
104
* * *
OPTIONS
»> SCROLL: PAGE
HSNC NUNLIN DEST FORM COPIES FCB UCS RECFM LRECL
*** CONDITION CODES DISPLAY.
A 13 HOLD STD . 1 **»* •*** UA 133
A 70 HOLD STD 1 **•*•»** f 132
A : 87 HOLD STD 1 ******** vA 133
A 1877 HOLD STD 1 **•«**•* UA 251
END OF DATA * * *
=a> p = PRINT, V=VIEW
Figure 3-25. The SYSD Job Dataset Display Screen
The job dataset display screen is invoked when you use the SELECT function.
September 1993
3-55
Procedures
-------
AIRS User's Guide
Air Quality Data Storage Volume AQ3
3.8.10 SYSD Job Dataset Display Screen
The "job dataset display" screen, shown at the bottom of Figure 3-25, appears when you use the SELECT
function of SYSD's job queue and job output screens. The job dataset display screen identifies and
describes each part of a SELECTed job's printed output, and allows you to view the content of any of
them. The job's name and number are shown in the top line of the screen following the screen title. The
body of the screen has a line of information for each logical part (dataset) of the job's output. The
information is presented in columns. The more significant ones are:
O The options column. You may enter the "V" option to view the content of a
dataset. (The "P" [print] option listed at the bottom of the screen does not work;
do not use it.)
DSN The dataset identifier (name). The datasets identified as CC, JCL, LOG, and MSG
are generated by the computer system for each job. Datasets identified by three-
digit numbers are generated by programs executed in the job.
HSNC Status information. An "N" in this column indicates the HOLD function was used
on this job. The job class assigned by the computer system is shown under the letter
"C" in the column heading.
NUMLIN The number of lines in the dataset.
COPIES The number of copies of the output to be printed.
LRECL The logical record length for the output dataset.
In the unlikely event that a job has more datasets than will fit on one screen, you may use the PF8 and
PF7 keys to scroll forward and backward through the list. Besides looking at the list of output datasets,
the only thing you can do on the job datasets display screen is select a dataset to view. If there is a
dataset you want to look at, tab to the options column beside it on the screen, type "v", and press
ENTER. That will invoke the SYSD "spool display" screen which is described below.
When you have finished using the job dataset display screen, you can use the PF3 key to return to the
job queue or job output display screen where you "came from", or you can transfer directly to another
option of the SYSD main menu by typing "=option" in the primary command field after the "INPUT
= = = > " prompt and pressing the ENTER key.
Procedures 3-56 September 1993
-------
AIRS User's Guide
Volume AQ3 Air Quality Data Storage
INPUT «
0 DSN
CC
V tOG
JCL
MSG
104
* * *
OPTIONS
HSNC NUNL1N DEST
*** CONDITION CCC
A 13 HOLD
A 70 HOLD
A 87 HOLD
A 1877 HOLD
END OF DATA * * *
==> p s PRINT, V
SCROLL: PAGE
FORM COPIES FCB UCS RECFM LRECL
)ES DISPLAY ;
STO 1 . **** **•• UA 133
STD 1 •••••*•• F 132
STO 1 ••** •.•••*••• VA 133
STD 1 *••*••*• UA 251
= VIEW
MVS/JES2 SPOOL DISPLAY - TADSFL /J4105 (1/1)
INPUT ==«• SCROLL: PAGE
DSN = LOG LINE = 000001 SIZE = 000013 COLS = 001 080 LRECL = 133
JES2 JOB LOG -- SYSTEM EPA2 -- NOD
JOB 4105 IEF097I TADSFL - USER TAD AND GROUP ASUD ASSIGNED
09.55.00 JOB 4105 ICH70001I TAD LAST ACCESS AT 09:52:09 ON TUESDAY, MARCH
09.55.00 JOB 4105 SHASP373 TADSFL STARTED • INIT 1 - CLASS A - SYS EPA2
09.55.42 JOB 4105 NCC005I * JOB TADSFL ENDED 03/03/87 AT 9:55:42. PRTY=02
09.55.42 JOB 4105 (HASP395 TADSFL ENDED
JES2 JOB STATISTICS
03 MAR 87 JOB EXECUTION DATA
19 CARDS READ
2.047 SYSOUT PRINT RECORDS
0 SYSOUT PUNCH RECORDS
256 SYSOUT SPOOL KBYTES
0.70 MINUTES EXECUTION TIME
Figure 3-26. The SYSD Spool Display Screen
The spool display screen is invoked when you use the VIEW function.
September 1993 3-57 Procedures
-------
AIRS User's Guide
Air Quality Data Storage Volume AQ3
3.8.11 SYSD Spool Display Screen
The SYSD "spool display" screen shows the content of a job's printable output datasets. It appears when
you use the VIEW function of SYSD's job queue, job output, and dataset display screens. A typical
spool display screen is shown at the bottom of Figure 3-26. The top line displays the screen title and
shows the jobname and job number. In the next line are the primary command input and scroll amount
fields. Below that is a line giving dataset information and display status in several fields, including:
DSN dataset identifier (like the "job dataset" screen)
LINE line number of the first line of output on the screen
SIZE total number of lines in the dataset
COLS leftmost and rightmost columns of the output on the screen
LRECL length of lines in the dataset.
You may enter values in the DSN, LINE, and COLS fields to switch among datasets and to display
particular lines and columns of the output. Beneath the DSN line, 20 lines of job output are displayed.
The spool display screen acts as a window through which you view the job output. You can move the
window (or scroll the output) to see other parts. You can enter a command in the primary input field
at the "INPUT = = = >" prompt or use the PF key allocated for the command. The available commands
are:
UP PF7 Moves the window toward the beginning of the dataset.
DOWN PF8 Moves the window toward the end of the dataset.
LEFT PF10 Moves the window toward the beginning of the lines of output.
RIGHT PF11 Moves the window toward the end of the lines of output.
TOP Moves the window to the first line of the dataset.
BOTTOM Moves the window to the last line of the dataset.
You can use the LINE and COLS fields in conjunction with or instead of the scrolling commands.
Entering " 1" in the LINE field has the same effect as entering the TOP command, for example. You can
make SYSD "wrap" long lines by entering "1" and "133" in the COLS fields. Each line of the output
takes up two lines on the screen, with the first 80 characters on one line and the remaining characters on
the next line. Conversely, you can display only a small part of the lines of output, say columns 20
through 40, by setting the COLS fields accordingly.
Procedures 3-58 September 1993
-------
AIRS User's Guide
Volume AQ3 Air Quality Data Storage
In many output datasets, the first character of each line is a code for controlling vertical spacing of the
paper when printing takes place. SYSD does not use that information, so the spacing of lines on the
screen may not correspond to the spacing of the printed output.
When you have finished using the spool display screen, you can use the END command (PF3) to return
to the screen you came from, or you can transfer directly to another option of the SYSD main menu by
entering "=option" in the primary command field.
September 1993 3-59 Procedures
-------
AIRS User's Guide
Air Quality Data Storage Volume AQ3
3.8.12 Terminating SYSD
When you are finished using SYSD, you must do something to terminate it. You can do that very easily
from any SYSD screen.
While the primary option menu screen is displayed, you can terminate SYSD by:
- pressing the END (PF3) key, or
- typing "X" in the primary command field (after the "INPUT = = = >" prompt) and then pressing
the ENTER key.
While any other SYSD screen is displayed, you can terminate by typing "=x" in the primary command
input field and then pressing the ENTER key. Or you can press the END (PF3) key until you get to the
primary option menu and use the termination methods given above.
When SYSD terminates, the screen clears and you are returned to CICS. At that point you may invoke
AIRS or you may logoff CICS using the procedures given earlier in this section.
Procedures 3-60 September 1993
-------
AIRS User's Guide
Volume AQ3 Air Quality Data Storage
3.9 Checking Batch Jobs With SDSF
SDSF, the "Spool Display and Search Facility", is the second of the two non-AIRS facilities for checking
the status of batch jobs. Although SDSF has even more capabilities and options than SYSD, which was
described in the previous subsection, the basic capabilities of the two are similar.
If AIRS is the only thing or the predominant thing you do on the NCC-IBM computer system, then SDSF
may be more difficult or less convenient for you to use than SYSD. That is because SDSF cannot be
invoked from CICS, the teleprocessing environment of AIRS and SYSD. To use SDSF, you must logon
to the TSO facility of the NCC-IBM system. If you are unfamiliar with TSO, you may not want to
bother to learn how to logon and how to invoke SDSF. If you already know how to use TSO, you may
not want to bother to switch between CICS (for AIRS) and TSO (for SDSF). The choice is up to you.
3.9.1 Invoking SDSF
You can invoke SDSF directly from TSO or as an option of the ISPF facility of TSO. That means you
can invoke SDSF only after you have completed TSO logon procedures. This manual does not describe
the TSO logon procedures, since they are not needed for using AIRS; refer to the NCC-IBM User's
Guide. To invoke SDSF directly from TSO, simply type "sdsf after TSO's READY prompt, and press
the ENTER key. To invoke SDSF as a subfunction of the ISPF facility, select option E of the ISPF main
menu, then select option S of the EPA sub-menu.
3.9.2 The SDSF Primary Option Menu
The first screen SDSF displays is the "primary option menu", shown in Figure 3-27. You use it to
invoke the various things SDSF can do, just as you use the AIRS main menu to select the various things
AIRS can do. You select one of the options listed on the menu by typing its code to the right of the
"COMMAND INPUT = = = >" prompt, then pressing the ENTER key. To select the option "display
active users of the system", for example, you would type the code "da".
The first time you use SDSF, you may want to set the SCROLL field in the upper right corner of the
screen to your preference of "page", "half, or "csr" (which scrolls the screen according to the position
of the cursor). The setting you choose will be stored and recalled the next time you use SDSF.
The SDSF menu options DA, I, O, and ST allow you to find out about batch jobs. Probably the most
useful of these is ST, "display status of jobs in the JES2 queues", because it allows you to see on one
screen the status of jobs that are waiting to execute, are currently executing, and are waiting to print.
(This is similar to option 5 of the SYSD facility, described in the previous subsection.)
September 1993 3-61 Procedures
-------
AIRS User's Guide
Air Quality Data Storage Volume AQ3
V1R3M2 - - -------------- SDSF PRIMARY OPTION MENU
COMMAND INPUT ===> SCROLL ===> PAGE
PREFIX=ML2* DEST=(ALL) OWNER=*
Type an option or command and press Enter.
LOG - Display the system log
DA - Display active users of the system
I - Display jobs in the JES2 input queue
0 - Display jobs in the JES2 output queue
N - Display jobs in the JES2 held output queue
ST -.Display status of jobs in the JES2 queues
PR - Display JES2 printers on this system
INIT -Display JES2 initiators on this system
TUTOR - Short course on SDSF (ISPF only)
END - Exit SDSF
: Use;Help;key for.iinore information. . :
5665-488 (C) COPYRIGHT IBM CORP. 1981, 1991. ALL RIGHTS RESERVED
Figure 3-27. The SDSF Primary Option Menu
The SDSF processor displays its primary option menu when it is invoked.
Procedures 3-62 September 1993
-------
AIRS User's Guide
Volume AQ3 Aiir Quality Data Storage
3.9.3 Job Selection Options
SDSF does not have a "profile" screen for defining job selection as SYSD does. You must define your
selection criteria each time you use SDSF. Figure 3-28 illustrates specifying SDSF Job Selection
Criteria. You can do that with the PREFDC and DEST options of the SDSF primary menu and with
variations of the I, 0, and ST options explained below. If you do not specify selection criteria, then just
your own jobs qualified by the menu option you used are selected. For example, if you use the "O"
option without any selection criteria, SDSF will select your jobs that are held or waiting to print.
The PREFDC option of the SDSF primary menu is really a command rather than a selection. With it you
specify the leading character(s) of jobnames you want to be selected for display on your screen. By
default, SDSF sets the prefix to your NCC-IBM user-ID. You could select jobs for user-ID "USR", for
example, by typing "prefix usr*" in the COMMAND INPUT field, then pressing the ENTER key. You
can change the prefix by specifying a different value, and you can eliminate a prefix by using the
PREFIX command without a value. You can also use the PREFIX command on other SDSF screens.
It is not limited to the primary menu screen.
The DEST command works like PREFIX except it specifies selection of jobs according to their output
destination rather than their jobname. To select jobs routed to printer site-ID RMT321, you would type
"dest r321" in the COMMAND INPUT field and press the ENTER key. All the forms of destination
that have been discussed before are valid for the DEST command: LOCAL, RMT123, R456, and N5R37,
for example. You can use the DEST command in combination with PREFIX if you want to.
You can also select jobs according to their job class by adding a suffix to the "I" and "O" commands for
invoking SDSF's input and output job queue display functions. Job classes are identified by a single
letter (A, B, E, etc.). Each job is assigned to an input job class defined by the computer center based
on the job time you specify when you submit it. To select only jobs on the input queue in class B, you
would type "ib" in the COMMAND INPUT field (menu selection "I" followed by the job class "B"
designation). The output of a job belongs to an output job class based on parameters in the JCL. To
select jobs with output class F, you would type "of in the COMMAND INPUT field.
Finally, you can specify the equivalent of a PREFIX command in combination with the "ST" option of
the primary menu. To do that, you supply the jobname prefix after the ST command. For example, you
could display the status of jobs for user-ID "USR" by entering the command "st usr*". This feature is
available only with the ST option of the primary menu, not for the DA, I, or O1 options. (SDSF uses the
current setting of PREFIX, which is your own user-ID by default, if you do not specify a prefix with the
ST option.)
September 1993 3-63 Procedures
-------
AIRS User's Guide
Air Quality Data Storage Volume AQ3
V1R3M2 SDSF PRIMAL OPTION MENU
COMMAND INPUT «•»> prefix usr* SCROLL -"»> PAGE
PREFIX=MLZ* OEST«{ALL> OUNER=*
Type an option or command and press Enter.
LOG * Display the system tog
DA • Display active users of the system
I • Display jobs in the JES2 input queue
0 • Display jobs in the JES2 output queue
H - Display jobs in the JES2 held output queue
ST - Display status of jobs in the. JES2 queues
PR • Display JES2 printers on this system
INIT - Display JE52 initiators on this system
TUTOR - Short course on SDSF (ISPF only)
END - Exit SDSF
Use Kelp key for more information.
5665-488 COPYRIGHT IBM CORP. 1981, 1991. ALL RIGHTS RESERVED
V1R3M2'—. •--- SDSF PRIMARY OPTION MENU -
COMMAND INPUT »=> st usr« SCROLL ===> PAGE
PREFIX=ML2* DESTs(ALL) OWNER=*
Type an option or command and press Enter.
LOG - Display the system log
DA -Display active users of the system
I - Display jobs in the JES2 input queue
0 - Display jobs in the JESZ output queue
N - Display jobs in the JES2 held output queue
ST - Display status of jobs in the JES2 queues
.;PR ;.:.-:Display JES2 printers on this system
INIT ;::•;- Display JES2 initiators on this system
TUTOR :;r Short course on SOSF (ISPF only)
C. .END;,: :.••• Ex.'* SDSF: . . .'. . ........
^Use Help;key for more information. ;
5665-488 :(C>:COPYRIGHT IBM CORP. 1981, 1991. ALL RIGHTS RESERVED
Figure 3-28. Specifying SDSF Job Selection Criteria
Job selection criteria may be entered on the primary option menu screen.
Procedures 3-64 September 1993
-------
AIRS User's Guide
Volume AQ3
Air Quality Data Storage
3.9.4 SDSF Job Status Display Screen
The SDSF job "status display" screen allows you to see the status of batch jobs in both main queues of
the NCC-IBM computer system: the execution queue (jobs waiting to execute or currently executing)
and the print queue (jobs that have executed and are waiting to print). You can also change the status
of your own jobs. A sample of the job status display screen is shown in Figure 3-29.
The job status display screen lists the jobs selected according to any criteria you entered, such as prefix
or destination. The total number of jobs selected by your criteria is shown in parentheses after the word
LINE at the top of the screen. Information about the jobs is presented in several columns across the
screen. You can enter commands or other information in some of the columns to change the status of
your own jobs (but not others'). The most important columns are:
NP
S
P
9
JOBNAME
JOB-ID
PRT-DEST
QUEUE
C
POS
Command input. You may enter a one-character comm;md in this field to change
a job's status or get more information. Some of the available commands are:
Selects the job's output for viewing.
Purges the job from the execution or print queue; nothing is printed.
Displays a list of the job's output datasets; any of them may be selected for viewing
with "S".
The job name chosen when the job was submitted.
The job number assigned by the computer system.
The destination of the job's output. You may change this field to reroute your job
output. "HOLD" is shown as the destination of held output of AIRS jobs.
The main job queue, "execution" or "print".
The job class assigned by the computer system.
The relative position of the job in its queue and class. The next job to be executed
or printed has position "1". This column is blank while a job is executing.
If all the selected jobs do not fit on one screen, you can scroll through the list with the DOWN (PF8) key
and the UP (PF7) key. You can also look for a particular jobname by entering "FIND "
in the COMMAND INPUT field. You do not have to specify the entire jobname. You may use the
END (PF3) key to return to the SDSF primary option menu screen or you may invoke one of the other
primary menu options by entering its code in the COMMAND INPUT field.
September 1993
3-65
Procedures
-------
AIRS User's Guide
Air Quality Data Storage Volume AQ3
V1R3M2 SDSF PRIMARY OPTION MENU
COMMAND INPUT •««> 8t SCROLL «»> PAGE
P«EFIX«*LZ* DEST-CALL) OWNER«*
Type an option or command and press Enter.
L06 • Display the system log .
DA - Display active users of the system
I • Display jobs in the JES2 input queue
0 - Display jobs in the JES2 output queue
H ' Display jobs in the JES2 held output queue
ST - Display status of jobs in the JES2 queues
PS - Display JES2 printers on this, system
INIT - Display JES2 initiators on this system
TUTOR - Short course on SDSF (ISPF only)
END - Exit SDSF
Use Help key for more Information.
•5665-488 CO COPYRIGHT IBM CORP. 1981, 1991. ALL RIGHTS RESERVED
SDSF STATUS DISPLAY ALL CLASSES LINE 1-3 (3)
COMMAND INPUT ==> SCROLL ===> PAGE
NP JOBNAME Job-id Prt-Dest Queue C JP Pos Stat ASys Programmer-Name
MLZ : TSU05813 LOCAL EXECUTION 2 EPA2 LOCKARD.MARNIE
ML2AE834 JOB05348 R255 PRINT W 1 13T TIME INVENTORY DETAIL
MLZAE834 JOB05363 R255 PRINT U 1 13T TIME INVENTORY DETAIL
Figure 3-29. The SDSF Job Status Display Screen
The job status display is invoked by the "st" option of the primary menu.
Procedures 3-66 September 1993
-------
AIRS User's Guide
Volume AQ3
Air Quality Data Storage
3.9.5 SDSF Input Queue Display Screen
The SDSF "input queue display" screen shows information about batch jobs that are waiting to execute
and are executing. A sample screen is shown at the bottom of Figure 3-30.
The jobs listed on the input queue display screen are selected according to any criteria you may have
specified, such as prefix, destination, and job class. In the top line of the screen SDSF shows which job
classes were selected and, in parentheses following the word LINE, the number of jobs selected. The
detailed information about jobs is presented in several columns across the screen. You can enter
commands or alter the information hi some of the columns to change the status of your own jobs or to
get additional information. The more significant columns are:
NP
P
9
Command input. You may enter a one-character command in this field to change
a job's status or get more information. Some of the available commands are:
Selects the job for viewing. You can look at the job log and the JCL while a job
is waiting to execute.
Purges the job from the queue; it is not executed and nothing is printed.
Displays a list of a job's datasets, any of which may then be selected for viewing
with "S".
JOBNAME The job name chosen when the job was submitted.
JOB-ID The job number assigned by the computer system.
The job priority assigned by the computer system.
The job class assigned by the computer system.
P
C
POS
The relative position of the job within its job class. The next job to be executed has
position " 1". While a job is executing this column is blank and "EPA2" is displayed in the
ASYS column.
PRT-DEST The destination of the job's output. You may enter a valid site-ID in this field to reroute
the job's output from one destination to another. "HOLD" is shown as the destination of
held output.
If all the selected jobs do not fit on one screen, you can scroll through the list with the DOWN (PF8) key
and the UP (PF7) key. You can also scroll RIGHT (PF11) to see additional columns of information and
LEFT (PF10) back to normal. As with the SDSF status display screen, you can look for a particular
jobname by entering "FIND " in the COMMAND INPUT field.
When you have finished with the input queue display screen, use the END (PF3) key to return to the
SDSF primary option menu screen, or invoke one of the other primary menu options by entering its code
in the COMMAND INPUT field.
September 1993
3-67
Procedures
-------
AIRS User's Guide
Air Quality Data Storage Volume AQ3
V1R3M2 SDSf PRIMARY OPTION MENU
COMMAND INPUT *"» i SCROLL «=> PAGE
Type en option or command and press Enter.
LOG - Display the system tog
OA - Display active users of the system
I * Display jobs in the JES2 input queue
0 - Display jobs in the JES2 output queue
K - Display jobs in the JES2 held output queue
ST ' Display status of jobs in the JES2 queues
PR * Display JES2 printers on this, system
1NIT ' Display JES2 initiators on this system
TUTOR - Short course on SDSF (ISPF only)
END - Exit SDSF
Use Help key for more information.
c
:5665-488: CO :COPTRIGHT IBM CORP. 1981, 1991. ALL RIGHTS RESERVED
SDSF INPUT QUEUE:DISPLAY ALL CLASSES LINE 0-0 (0)
COMMAND INPUT «=> SCROLL ===> PAGE
iNP JOBNAME Job-id PC Pos Prt-Dest ASYS Stat Causer Programmer-Name
Figure 3-30. The SDSF Input Queue Display Screen
The input queue display is invoked by the "i" option of the primary menu.
Procedures 3-68 . September 1993
-------
AIRS User's Guide
Volume AQ3 Air Quality Data Storage
3.9.6 SDSF Output Queue Display Screen
The SDSF "output queue display" screen is invoked by the "0" option of the primary menu. The output
queue display screen shows information about batch jobs that have executed and are waiting to print. A
sample screen is shown in Figure 3-31. As with the other SDSF screens described on the preceding
pages, you can enter commands to change the status of your own jobs and to view the output. Which
jobs are listed on the screen depends on the selection criteria you may have specified, such as prefix and
destination. The number of jobs selected is shown in parentheses after the word LINE near the top right
corner of the screen.
Information about jobs in the output queue is presented in columns across the screen. Quite a lot of
information is available; you can scroll right to see additional columns. Some of the columns are tab
stops where you can enter commands that change the status of your own jobs or request additional
information. The more significant columns are:
NP Command input. You may enter a one-letter command in this field to view or purge the
output of a job. Some of the available commands are:
S Selects the job for viewing. You can then look at all the job's printable output.
P Purges the job from the print queue; nothing is printed.
? Displays a list of a job's datasets, any of which may then be selected for viewing with "S".
JOBNAME The job name chosen when the job was submitted.
JOB-ID The job number assigned by the computer system.
DEST The destination of the job's output. You may enter a valid site-ID in this field to
reroute the job's output from one destination to another. "HOLD" is shown as the
destination of held output.
C The output (message) class chosen when the job was submitted. You can change this field.
TOT-RCDS The number of lines of output. While a job is actually printing, the PRT-REC column
shows how many lines have printed and the DEVICE column shows the printer-ID.
As with the other SDSF screens described previously, you can scroll through the list of jobs with the UP
(PF7), DOWN (PF8), LEFT (PF10), and RIGHT (PF11) keys; and you can use the FIND command to
locate a particular job in the list. You can return to the primary option menu with the END (PF3) key
or invoke another option of the primary menu by entering its code in the COMMAND INPUT field of
the output queue display screen.
September 1993 3-69 Procedures
-------
Air Quality Data Storage
AIRS User's Guide
• Volume AQ3
V1R3M2
COMMAND INPUT «*> «
SDSf PRIMARY OPTION MENU
SCROLL «=> PAGE
Type an option or command and press Enter.
LOG • Display the system log
DA - Display active users of the system
1 • Display jobs in the JES2 input queue
0 - Display jobs in the JES2 output queue
H - Display jobs in the JES2 held output queue
ST - Display status of jobs in the JES2 queues
PR - Display JES2 printers on this system:
JNIT - Display JES2 initiators on this system
TUTOR - Short course on SDSF (ISPF only)
END - Exit SDSF
Use Help key for more information.
5665-488 (C) COPYRIGHT IBM CORP. 1981, 1991. ALL RIGHTS RESERVED
SDSF OUTPUT ALL CLASSES
COMMAND INPUT ===>
NP JOBNAME Jobid Dest
MLZAE834 JOB05348 R255
MLZAE834 JOB05348 R25S
MLZAE834 JOB05363 R255
MLZAE834 JOB05363 R255
ALL FORMS LINES 1,932
C Form FCB UCS Uriter
F STD **** ****
F STD **** ****
F STD **** ****
F STD **** ****
LINE 1-4 (4)
SCROLL ===> PAGE
Tot-Reds Status Device
483
483
483
483
Figure 3-31. The SDSF Output Queue Display Screen
The output queue display is invoked by the "0" option of the primary menu.
Procedures
3-70
September 1993
-------
AIRS User's Guide
Volume AQ3 .. Air Quality Data Storage
3.9.7 The SDSF Job Dataset Display Screen
The SDSF "job dataset display" screen is invoked when you enter "?" in the NP column beside a job
listed on the job status display screen (ST function), the input queue display screen (I function), or the
output queue display screen (0 function). A sample screen is shown at the top of Figure 3-32.
The job dataset display screen identifies and gives information about each part of the printed output of
a selected job. The jobname and job number are given in the top line of the screen. The information
about job datasets is listed in columns across the screen. The more significant columns are:
DDNAME Logical name of the dataset used in the JCL.
STEP-NAME Job step in which the dataset was created.
DSID Dataset ID. Numbers above 100 are created by programs.
C Output class of the dataset.
REC-CNT Number of lines in the dataset.
You may enter "S" in the NP column to select a dataset for viewing, or use the END (PF3) key to return
to the screen you came from.
3.9.8 The SDSF Output Display Screen
The SDSF "output display" screen is invoked when you select job output for viewing by entering an "S"
in the NP column of a screen. A sample screen is shown at the bottom of Figure 3-32.
The output display screen has few remarkable features. The jobname, job number, and dataset id are
shown in the top line of the screen, and the COMMAND INPUT field occupies the second line. The rest
of the screen displays the job output. You can use the UP (PF7), DOWN (PF8), LEFT (PF10), and
RIGHT (PF11) keys to scroll the output, and you can use the FIND command to locate a specific text
string. The RFIND (PF5) key repeats the last FIND command. The NEXT and PREV commands scroll
to the start of the next or previous output dataset, and the TOP and EOT commands scroll to the
beginning and end of the output.
When you have finished using the output display screen, you may use the END (PF3) key to return to
the screen you came from.
September 1993 3-71 Procedures
-------
Air Quality Data Storage
AIRS User's Guide
Volume AQ3
: SOSF JOB DATA SET DISPLAY • JOB HLZAE834 (J0605363)
:;; ;•: COMMAND INPUT «««>,
M HP DONAME stepnaott
JESMSGLG JES2
."• ::.:..-.::••• : . i;::,'->»aESJCL JES2
•: " ' '•":.;'.-.---'..-i':-iii"^IESVSMS(i--JES2
:,••.:.-: -'^'V-^K'^CMPRIHT STEP1
••..•' : - • • • - - : :X' :; • :- ' • •:;. * ''•••• :SYSPR I NT STEP2
':::•:: - V:-'::':-":- V^F^CMPRIHT STEP3
••" • "•• -•:;' -•':.. ^vV/H^y^SYSPRIMT STEP4
• ••-,...:--^ •.".,» ::--:s:s^->6lPRIHT STEPS
•• '.:.v-:v. '.;.. ' :•:. :V- ' v-:'s/« '-.SYSOUT STEP6
:':;: •:••:.'•'•:-:•;::;;:: • ^rMfifcMPRINT STEP7
••'•:.' I-;' : ".'..', • . ... '': •: '-V • ?%;' : SCMPRT01 STEP7 '
•: : - ••:• •... : : d. ., ;;:-; ^ .:,;::.,: ;;:' ^ % CMPRl NT ' CLEANUP
:: : :: CHPRTOI CLEANUP
procname OSID C R*c-cnt Pages CC
STEP1
STEP1
STEP1
SORT
STEP1
STEP1
STEP1
STEP1
2
3
4
110
117
121
128
132
139
143
144
153
1 54
13
135
272
13
3
13
3
13
15
13
53
13
10
1
1
1
1
1
1
LINE 1-13 (13)
: SCROLL -«»> PAGE
Oest
R255
R255
R255
R255
R255
R255
R255
R255
R255
R255
R255
R255
R255
Node
1
1
1
1
1
1
1
1
1
1
1
1
1
Rmt
255
255
255
255
255
255
255
255
255
255
255
255
255
Forms
STD
STD
STD
STD
STD
STD
STD
STD
STD
STD
STD
STO
STO
SOSF OUTPUT DISPLAY ML2AE834 JOB05363 DSID 4 LINE 0 COLUMNS 02- 81
COWWND INPUT ===> SCROLL ===> PAGE
********************************* JQP OF DATA **********************************
STMT NO. MESSAGE
: 3 IEFC001I PROCEDURE NATPAEMS WAS EXPANDED USING PRIVATE LIBRARY ASUD.PR
39 1EFC001I PROCEDURE NATPAEMS WAS EXPANDED USING PRIVATE LIBRARY ASUD.PR
75 IEFC001I PROCEDURE NATPAEMS WAS EXPANDED USING PRIVATE LIBRARY ASUD.PR
106 IEFC001IPROCEDURE JUSOSORT WAS EXPANDED USING SYSTEM LIBRARY SYS1.USE
116 IEFC001I PROCEDURE NATPAEMS WAS EXPANDED USING PRIVATE LIBRARY ASUD.PR
147 lEFCOOTi PROCEDURE NATPAEMS WAS EXPANDED USING PRIVATE LIBRARY ASUD.PR
ICH70001I MLZ LAST ACCESS AT 06:54:09 ON TUESDAY, NOVEMBER 24, 1992
1EF142I MLZAE834 STEP! STEP1 - STEP WAS EXECUTED - COND CODE 0000
NCC9021 ***************** U.S.EPA SYSTEM EPAG - STEP SUMMARY *****************
NCC900I
NCC9041:JOB05363 MLZAE834 STEP STEP1.STEP1
NCC900I
NCC906I START 11/24/92 6:56:01 STOP 11/24/92
NCC900I
NCC908I TCB :00.08, SRB :00.01, VEC
NCC908I ADABAS
NCC900I
NCC910I I/O COUNTS: DA 0, NT 0, OTHER
NCC910I ADABAS
NCC900I
CC:
6:56:04 ELAPSED
:03
:00.00,
:00.03
TOTAL
:00.12
1,
2 TOTAL nn
Figure 3-32. The SDSF Job Dataset Display and Output Display Screens
These screens can be invoked from the ST, I, and 0 primary functions of SDSF
by entering the "?" and "S" line commands.
Procedures
3-72
September 1993
-------
AIRS User's Guide
Volume AQ3 Air Quality Data Storage
3.9.9 Terminating SDSF
When you have finished using SDSF, you can terminate it using the END (PF3) key while the primary
option menu screen is displayed. If you invoked SDSF directly from TSO, the END key takes you back
to the READY prompt of TSO. If you invoked SDSF as option 8 of ISPF, the END key takes you to
the ISPF primary menu. Also as ISPF option 8, you can terminate SDSF from any screen by entering
ISPF's "= < option>" command in the COMMAND INPUT field. For example, entering "=x" while
you are viewing job output would terminate both SDSF and ISPF, and take you to the READY prompt
of TSO.
3.9.10 Ending Your TSO Session
You can logoff from TSO after a READY prompt is displayed on the screen. Simply type the word
"logoff1 and press the ENTER key. TSO displays a summary of usage and cost figures for your session,
then the EPA logon menu appears.
September 1993 3-73 Procedures
-------
AIRS User's Guide
Volume AQ3 Air Quality Data Storage
4.0 The LOAD Process
LOAD is logically the first process of the AQ Data Storage Subsystem of AIRS. This section describes
what LOAD does and how to use it.
4.1 Overview
LOAD is a batch process that reads AIRS input transaction records, sorts them, and writes them into a
screening file. LOAD is the only process of the AQ Data Storage Subsystem that reads the card-image
input transactions you submit to AIRS. The other processes can access and use transaction data only after
LOAD has written them in a screening file. That is why you must process each file of transactions
through LOAD before you can use the other AQ Data Storage processes on those transactions.
The data flow diagram in Figure 4-1 illustrates how LOAD is invoked and what it does. Like other batch
AIRS processes, LOAD executes under the control of JCL and parameters that you specify during an
AIRS terminal session. The primary input to the process is a file of AIRS input transactions and the
primary outputs are an updated screening file and a report listing how many transactions were loaded.
LOAD also accesses the Table File to read and write control information and to write a status message
that you can view using the MESSAGE process.
LOAD processes the entire input transaction file and creates a record in the screening file for each input
transaction record. LOAD does not delete or replace any records already in the screening file. Thus,
if you were to run LOAD twice using the same input transaction file and screening file, you would end
up with two copies of every transaction in the screening file. Periodically during the processing, LOAD
writes a record in the Table File that identifies the last transaction record loaded into the screening file.
If some failure of the computer system prevents LOAD from processing the entire input file, the
information written in the Table File can be used to restart LOAD at the last checkpoint. This feature
allows you to complete the loading of a transaction file without creating duplicates.
LOAD does more than simply copy the AIRS input transactions from your card-image file into your
screening file. LOAD reformats and initializes fields, validates important fields, and checks for
interactions between records being loaded and records already in a screening file.
September 1993 4-1 LOAD
-------
Air Quality Data Storage
AIRS User's Guide
Volume AQ3
Top LeveI
User
Session
Menus
JOB
JCL and
parameters
Disk
Input
Transaction
Fi le
f
AMP010
LOAD
Program
Summary Report
ADABAS
Figure 4-1. LOAD Data Flow Diagram
Screen!ng
FI le
LOAD
4-2
September 1993
-------
AIRS User's Guide
Volume AQ3 Air Quality Data Storage
4.1.1 Record Reformatting and Initialization
The formats of the transaction and screening records differ somewhat. (See Volume AQ1 for record
layouts.) Screening records have some additional fields and the relative positions of some fields are
different. LOAD rearranges the fields of the transaction record as required and supplies values for the
additional fields in the screening record. Some of the additional fields are used by the Data Storage
processes for information and control. They are:
USER-ID Who last updated the record. LOAD stores your NCC-IBM user-ID in
this field.
EDIT-LEVEL-FLAG What type (level) of edit checks the record has passed. LOAD stores
zero to indicate no edit checks have been passed.
EXCLUDED-FLAG Whether the record is excluded from use by other Data Storage
processes. LOAD stores zero to indicate the record is not excluded.
DATE-EXCLUDED When the record was excluded (YYMMDD). LOAD stores blanks
because the record is not excluded.
The fields for state, county, site, parameter, POC, year, transaction type, month, day, hour, and action
code comprise the "key" of every screening record. LOAD stores blanks in any of those fields not
defined in an input transaction record. For example, an input transaction for reporting composite data
(transaction type 3) does not have fields for day or hour, so LOAD stores blamks in those fields when it
creates the corresponding screening record.
4.1.2 Validation of Important Fields
Because the transaction type and action code fields are so important to the other AQ Data Storage
processes, LOAD checks those two fields and stores"?" for invalid codes. There are pairs of action code
and transaction type fields in the screening record. Into one field of the pair LOAD copies the code from
the input transaction, even if it is invalid. The EDIT and CORRECT processes validate this field when
edit checks are done on the record. Into the other field of the pair, LOAD stores a copy of the original
code if it is valid or "?" otherwise. The Data Storage processes use this second field in all contexts
except edit checking, since it has a known set of values: the valid codes or"?". LOAD also checks every
position of input transaction records for non-printable characters and substitutes"?" for each one it finds.
September 1993 4-3 LOAD
-------
AIRS User's Guide
Air Quality Data Storage Volume AQ3
4.1.3 Interactions Among Records
LOAD checks whether any records that were already in the screening file are related to any of the records
being loaded. Table 4-1 lists the relationships among the types of AIRS transactions, if there are any
related records in the screening file and if their edit level is greater than one, LOAD lowers the edit level
to one. (Edit level is described in more detail in the section describing the EDIT process.) An edit level
greater than one signifies that a record has passed edit checks involving interactions with other screening
records or with the AIRS database. Since the records being loaded may affect those interactions, LOAD
sets the edit level field to indicate that the applicable edit checks must be done again.
LOAD 4-4 September 1993
-------
AIRS User's Guide
Volume AQ3
Air Quality Data Storage
Table 4-1. Related Screening File Records
This table lists the relationships among screening file records for the LOAD process.
Input Transaction Type
Site (A1,A2,A3,A4,A5,A6,A7)
Monitor (F1,F2,F3,F4',F5)
SLAMS (M,N,P,R,S,T,U,V)
Min. Detectable (Z)
Hourly Data (1)
Daily Data (2)
Composite Data (3)
Null Value (4)
Precision Data (8)
Accuracy Data (9)
Related Records
Other records with the same site-ID (state, county, site)
Other records with the same monitor-ID (site-ID, parameter,
POC)
Other SLAMS records (transaction types M - P and R - V)
with the same monitor-ID and year
Other type-Z records with the same monitor-ID
Other type-1 records with the same monitor-ID, year, and
month; and type-4 records with the same monitor-ID
Other type-2 records with the same monitor-ID, year, and
month; and type-4 records with the same monitor-ID
Other type-3 records with the same monitor-ID, year, and
composite period
Other type-4 records with the same monitor-ID; and any type-1
or type-2 records with the same monitor-ID that pertain to a
month within the date range of the null value transaction
Other type-8 records with the same monitor-ID, year, and month
Other type-9 records with the same monitor-ID, year, and month
September 1993
4-5
LOAD
-------
AIRS User's Guide
Air Quality Data Storage Volume AQ3
4.2 Data Submission Procedures
This section describes how to supply a file of AIRS transactions for processing by LOAD.
4.2.1 Transaction Record Format
AIRS input transaction records have an 80-character card-image format. Volume AQ2 of this User's
Guide explains how to code the transactions, and Volume AQ1 shows the record formats of input
transaction and screening files. Refer to those volumes for detailed information.
4.2.2 Transaction File Medium
LOAD can read AIRS input transactions from a single file on magnetic tape or on disk. Magnetic tape
is the only practical medium for supplying a large number of input transactions. This is especially true
if the data originate on a computer system that is not connected with the NCC-IBM system or if the
transactions are encoded from paper forms by a "keypunch" service.
A relatively small number of transactions could be transmitted from, say, a personal computer to a disk
file on the NCC-IBM computer system using the EPA telecommunications network, or the transactions
could be entered directly into a disk file using the text editing facilities available on the NCC-IBM
system. Neither of these methods is practical for significant numbers of transactions, however.
4.2.3 Transaction File Format
To be compatible with LOAD, an input transaction file must have two characteristics:
fixed-length records of 80 characters (LRECL=80), and
fixed-length blocks of one or more records (RECFM=FB).
If the file is catalogued, there are no other requirements. (According to computer center policy, a disk
file must be catalogued.) A tape file that is not catalogued must have the following additional
characteristics:
number of reels: 1
recording density: 6250 or 1600 bits per inch
number of tracks: 9
label type: NL (no label)
file position: first file on the tape
block size: 4000 bytes (50 records per block)
Note that a file must be catalogued if it does not fit on one reel of tape. Contact the computer center
for assistance if you need to create a catalogued tape file.
LOAD 4-6 September 1993
-------
AIRS User's Guide
Volume AQ3 Air Quality Data Storage
4.2.4 Tape Submission
The NCC-IBM User's Guide explains the procedure for submitting a tape to the EPA National Computer
Center (see "Foreign Tapes", Section 3.3.4.3). To briefly summarize the procedure, you send the tape
to NCC with the requisite identification affixed, and the computer center assigns an ID-number by which
you can access the tape. When you have finished with the tape, you notify the computer center and the
tape is returned to you. Refer to the NCC-IBM User's Guide for details of the procedure.
4.2.5 Screening File Selection
When you have a file of input transactions ready to use, you need to determine what screening file they
will be loaded into. If your AIRS user group has only one screening file for air quality data, the choice
is easy. If your group has several screening files, you must consult with the other users to determine
which file is available. Remember that LOAD can affect the edit level of records already in a screening
file, so you should be careful not to mess up the editing you or someone else has done by loading
transactions into the wrong file. Also, LOAD can only be used with a screening file that is not locked
for update processing.
A more subtle consideration in choosing a screening file is monitor "ownership". When information
about a site or monitor is loaded into the database or changed, the group name of the screening file from
which the information came is stored with the monitor information. (The group name is the first six
characters of the screening file name.) Thereafter, all transactions applicable to that monitor, including
transactions supplying raw data values, must be in a screening file of the same group. The EDIT process
applies this edit check to all transactions in order to detect miscoded monitor-IDs. In most groups of
AIRS users, monitor ownership is not a significant consideration because all the screening files available
for use have the same group name. Those AIRS users with access to more than one group of screening
files must remember to use the appropriate screening file for each monitor.
After you have prepared an input transaction file and chosen a screening file to use, you are ready to
initiate the LOAD process.
September 1993 4-7 LOAD
-------
Air Quality Data Storage
AIRS User's Guide
Volume AQ3
02/16/90
AIRS Air Quality Subsystem
User Profile COT
Password:
Printer 10: RMTOOO
Account Code: ASM)
Sin Number: 8132
SCREENING FILES
AtlAOBFOI Air Quality Screening File
ANADBF95 Air Quality Screening File
OCSCSF01 Air Quality Screening File
Enter Profile Data (optional)
PF3=end
PF4=subsystem menu
Read Only
Read Only
Update
AAPOOOO
Not Locked
Not Locked
Not Locked
PF5=terminate
02/22/90 AIRS Air Quality Subsystem
:•''• '••'*'. '•"••• Main Menu
1. Submit Data
2. Retrieve Data - Standard Batch
3. Retrieve Data - Ad Hoc Batch
4. Browse Data - Online
Please enter selection: 1
NEED ASSISTANCE?
CALL THE AOS HOTLINE AT 1-800-333-7909
AAPOOOA
PF3*end(profUe)
PF4=subsystem menu
PF5=terminate
Figure 4-2. AIRS AQS User Profile and Main Menu Screens
The AIRS AQS main menu appears after the user profile is .established.
LOAD
4-8
September 1993
-------
AIRS User's Guide
Volume AQ3 Air Quality Data Storage
4.3 LOAD Initiation Procedures
This section tells how to initiate the LOAD process. "Initiating" LOAD means specifying the information
needed for the LOAD program and submitting a batch job to execute it. Before using LOAD you must
complete the data submission procedures given in the previous section.
You initiate the LOAD process by selecting the appropriate options from the menus of the AIRS Top
Level User session and entering the required information. See Section 3.4 of this manual for AIRS logon
procedures, Section 3.6 for Top Level User procedures.
4.3.1 User Profile Screen
When you begin an AIRS terminal session, the first screen is the user profile. A sample is shown in
Figure 4-2. If you plan to use LOAD, you must choose a screening File and enter its password on the
user profile screen. If you neglect to enter the password or enter it incorrectly, the LOAD initiation will
appear to work correctly, but the LOAD program will not be able to load your data and the batch job
will terminate in error. Be sure you select a screening file and enter its AIRS password.
4.3.2 AIRS AQS Main Menu
The second screen of an AIRS terminal session is the AIRS AQS main menu. A sample is shown in
Figure 4-2. Choose option 1, "submit data". If you forgot to select an air quality screening file, the
main menu screen displays an error message and you are advised to return to the user profile screen to
select a screening file. An error message is not displayed if you forgot to enter your AIRS password.
The AQS Hotline number is displayed on the screen for users who need assistance.
September 1993 4-9 LOAD
-------
Air Quality Data Storage
AIRS User's Guide
Volume AQ3
05/25/69
AIRS Air Quality Subsystem
Submit
AMP002
Enter Selection: 1
1 LOAD Input Transactions to Screening file
2 EDIT Screening file (Batch Execution}
3 CORRECT Screening File (Online Adds, Changes, Deletes)
4 NOTIFY AIRS Data Base Administrator for UPDATE
5 RECEIVE Messages
6 DELETE all Transactions from Screening File
PF3=end PF4=main menu PF5=terminate
05/25/89
PF3=end
AIRS AIR Quality Subsystem
JCL Parameters for LOAD Batch Job
AHP002
ENTER:
Data Set Name
Tape Number
Screening File Id
JOB Name
Account Code/UID
Time (MM , SS)
Priority
Message Class
Number of Copies
Form Number
Room/Bin Number
Hold Output (Y/N)
Printer Id
ANADBF96
SFP LOAD1
ASWD AIRSP
03,00
2
A
01
8132
N
RMTOOO
Press ENTER to submi t JOB
PF4=ma?n menu
PF5=terminate
Figure 4-3. The LOAD Job Submission Screen
The LOAD job submission screen appears after seleciing submil menu option 1.
LOAD
4-10
September 1993
-------
AIRS User's Guide
Volume AQ3 Air Quality Data Storage
4.3.3 AQ Submit Menu
The AQ Data Storage Subsystem "submit" menu, shown in Figure 4-3, is the third screen of the AIRS
terminal session. To invoke LOAD, select option 1 of the submit menu, "load input transactions to
screening file".
4.3.4 LOAD Job Submission Screen
The LOAD job submission screen appears next. A sample is shown at the bottom of Figure 4-3. Use
this screen to specify the information needed to submit a LOAD batch job. (The LOAD restart screen,
discussed in the next subsection, may also provide information for the batch job.)
4.3.4.1 S creen Description
All but the first two fields of the LOAD job submission screen have values from your user profile or
appropriate default values. Use one of the first two fields to specify either the dataset name or the tape
ID-number of your file of input transactions.
DATA SET NAME
If the input transactions you want to load are in a catalogued tape or disk file, enter the complete
dataset name in this field. For example, USRACCT.QTR1.AQ.TRANS is a valid dataset name
for a person with user-ID USR and account ACCT. Be sure the dataset name is valid, since it
is not checked by the program. The LOAD batch job will fail if the dataset name is invalid.
You do not have to enter the name in upper case; the program takes care of that.
TAPE NUMBER
If the input transactions you want to load are in a tape file, enter the tape ID-number assigned
by the computer center in this field. For a foreign tape the ID-number has the format Blxxxx,
where xxxx is a number. Be sure you enter the correct ID-number; it is not checked by the
program. If you were to enter the wrong number, the LOAD batch job would fail or "garbage"
could be loaded into your screening file.
The next field of the screen is for information only; it is not a data entry .field.
SCREENING FILE ID
is the name of the screening file you chose on the user profile screen. Do not change this field.
September 1993 4-11 LOAD
-------
AIRS User's Guide
Air Quality Data Storage Volume AQ3
The other fields of the LOAD job submission screen pertain exclusively to the JCL for the LOAD batch
job. They all have default values that you can change if you desire. You can find more information
about these fields in Section 4 of the NCC-IBM User's Guide.
JOB NAME
is the eight-character job name for the batch job to be submitted. The first three characters are
your user-ID and cannot be changed. The last five characters have the default value "LOAD1",
but you may change them to any value consisting of letters and numbers.
ACCOUNT CODE
is the NCC-IBM account to which the cost of the LOAD batch job will be charged. The initial
value shown on the screen is what you specified for account code on the AIRS user profile
screen. You can change it to a different value, but it must be a valid code that you are
authorized to use. The FIMAS code "AIRSP", appended to the account code, cannot be changed.
TIME IN MINUTES,SECONDS
is the maximum CPU time allowed for your LOAD batch job. You may change the default three
minutes, zero seconds to another value so long as it is a valid job time. The amount of time
specified affects when the job will run; jobs with shorter times generally run sooner than jobs
with longer times. The NCC-IBM User's Guide explains the allowed formats of the job time
parameter and the effect of job time on job scheduling. A job time of 30 seconds should be
ample for loading 10,000 transactions, and the default time of three minutes should be enough
for loading 100,000 transactions.
PRIORITY
is a one-digit code that affects job scheduling and cost. The default value "2" is normal priority.
You may specify higher priorities of "3" or "4" which may cause a job to execute sooner, but
cost more. You may specify a lower priority of " 1" which causes a job to be executed at night
and costs less. Note that a job with more than ten minutes for CPU time will execute only at
night, so it is pointless to specify any priority but "1" for such a job.
MSGCLASS
(message class) is a one-character code that defines a category of printed output. The default
value "A" is a general category. You may also use "F" to specify output to the laser printer at
NCC.
NUMBER COPIES
is the number of copies of batch job output to be printed. The default value is one; permissible
values are 1 through 99.
LOAD 4-12 September 1993
-------
AIRS User's Guide
Volume AQ3 Air Quality Data Storage
FORM NUMBER
is a four-digit code for the type of paper your output is printed on, the number of lines printed
per inch, and whether lower case letters are printed. The default value is blanks, which results
in usage of the standard form (STD). For the local printers at NCC the standard form is 6111,
upper-case only on 15 x 11-inch paper. Other common forms are 6311, for upper- and lower-
case at six lines per inch on 15 x 11-inch paper; and 8381, available only on the laser printer,
for upper- and lower-case at eight lines per inch on 11 x 8.5-inch paper. Be aware that remote
printers may not be set up to handle anything but the standard form.
ROOM/BIN NUMBER
is a four-character code used by the computer center for distribution of printed output to the
appropriate location. The initial value shown on the screen is what you specified on the AIRS
user profile screen. You may change it to another valid bin number.
OUTPUT HELD
is a yes/no field that specifies whether the output of your LOAD batch job is to be held in the
output queue of the computer system (yes) or to be printed (no). The default value is "N" (no).
PRINTER-ID
is the printer site-ID where the output of your LOAD batch job is to be printed. The initial value
shown on the screen is what you specified on the AIRS user profile screen. You may change it
to another valid printer site-ID, such as "LOCAL" or "R321" or "N7R100". This field is not
used if you specify "Y" for OUTPUT HELD, and may be blank in that case.
September 1993 4-13 LOAD
-------
Air Quality Data Storage
AIRS User's Guide
Volume AQ3
DATA SET NAME OR TAPE MUST BE ENTERED
05/25/89
AIRS AIR Quality Subsystem
JCL Parameters for LOAD Batch Job
ANP002
ENTER:
Data Set Name
Tape Hunter
Screening File Id
JOB Mam
Account Code/UlD
Time (MM , SS)
Priority
Message Class
Number Of Copies
Form Number
Roan/Bin Number
Hold Output (Y/N)
Printer Id
ANADBF96
SFP LOAD1
ASUD A1RSP
03,00
2
A
01
B132
N
RHTOOO
PF3=end
Press ENTER to submit JOB
PF4=main menu
PF5=terminate
Figure 4-4. The LOAD Job Submission Screen Showing an Error Message
LOAD
4-14
September 1993
-------
AIRS User's Guide
Volume AQ3 Air Quality Data Storage
4.3.4.2 Screen Usage
When you have specified the information on the LOAD job submission screen as you want it, press the
ENTER key. Each field of the screen is checked. If something is wrong an error message is displayed
at the top of the screen and the cursor is positioned to the invalid field. Correct the error and press the
ENTER key again.
While the LOAD job submission screen is displayed, you may use the standard AIRS PF keys:
PF3 return to the AQ submit menu
PF4 return to the AIRS AQS main menu
PF5 terminate your AIRS terminal session
An error message is displayed at the top of the screen if you use any other PF or PA key. A LOAD
batch job is not submitted when you use any PF or PA key. Upon successful job submission, the Load
job number screen shown in Figure 4-5 is displayed.
The following messages may occur while the LOAD job submission screen is displayed:
DATA SET NAME OR TAPE MUST BE ENTERED
This message is displayed if you enter both a dataset name and a tape ID-number or if you enter
neither of them. Erase the value from one of the fields if you specified both, or enter a value
for one of the fields if you specified neither.
INVALID FIELD
This message is displayed if you enter an invalid value or erase the value of a required field. Use
the position of the cursor to determine which field is invalid.
INVALID PF KEY
This message occurs if you use the PF8 key, which is not valid on this screen.
NAT1011 REQUESTED FUNCTION KEY NOT ALLOCATED.
This message results from the use of any PA key or any PF key other than PF3, PF4, PF5, or
PF8. Only the PF3, PF4, and PF5 keys are valid on this screen.
September 1993 4-15 LOAD
-------
Air Quality Data Storage
AIRS User's Guide
Volume AQ3
05/27/90
:ik .,,!::,; AIRS AIR;OuBtfty:Subsy8tem :
LOAD JOB Mmber for Screening file ANAD8F95
JOB STATUS: JOB 8386 submitted
PF3=end . . PFA=nain menu PF5=terminate
AHP002
Figure 4-5. The LOAD Job Number Screen
This screen appears on a successful job submission.
LOAD
4-16
September 1993
-------
AIRS User's Guide
Volume AQ3 Air Quality Data Storage
OS/27/90 MRS Air Quality Subsystem AMP002
Restart LOAD
User Id Jobnane Date Time Key
SFP SFPIOAD1 890114 0347 390670090424014851013100I
SFP SFPLOMOM 890323 1259 2S0010001VI1014871311100M
SFP SFPLOOAD 890902 0201 2903710038110248801121OOM
d=delete s=select PF3=end PF4=main menu PF5=terminai:e
Figure 4-6. The LOAD Restart Screen
This screen appears if a previous LOAD job for the same file did not finish.
September 1993 4-17 LOAD
-------
AIRS User's Guide
Air Quality Data Storage Volume AQ3
4.3.5 LOAD Restart Screen
The batch LOAD program periodically takes a "checkpoint" of its progress by saving the key of the next
transaction record to be loaded. If the program fails before processing all the transaction records in the
file, LOAD can be restarted at the last checkpoint and continue processing the same input transaction file.
Without this feature, it would be necessary to delete the transactions loaded by the unsuccessful LOAD
job before loading the same file again. Otherwise, duplicates of some transaction records would be
loaded into the screening file. When the batch LOAD program has processed all the records of an input
transaction file, it deletes the checkpoint information.
If the screening file you selected for LOAD was involved in a previous LOAD job that failed, the LOAD
restart screen appears after you have completed the LOAD job submission screen. Otherwise, the restart
screen is not displayed.
4.3.5.1 Screen Description
A sample of the LOAD restart screen is shown on the facing page. There is a line of information on the
screen for each failed LOAD job that applies to your screening file. Each line shows the user-ID of the
person who submitted the job, the job name, the date and time of execution, and the key of the next
record to be processed. You may delete restart entries or select a restart entry to be used in the LOAD
job being submitted. At the bottom of the screen is a list of the valid options and PF keys you may use.
If there are too many restart entries to fit on one screen, "PF8 = MORE" is displayed at the end of the
PF key message near the bottom of the screen. You may use the PF8 key to view the next screen of
restart entries, but you cannot come back to the current screen once you have left it.
4.3.5.2 Screen Usage
Use of the LOAD restart facility is optional. If you want to restart a failed LOAD job, simply type an
'S' to the left side of the restart entry under the column heading '0', then press the ENTER key. The
information in the selected restart entry is used with your job submission specifications to submit a LOAD
restart job. In particular, the job name from the restart entry is used instead of the job name you entered
on the LOAD job submission screen.
If you want to delete a load job, type 'D' to the left side of the restart entry under the column heading
'O', then press the enter key. The information in the selected restart entry is deleted.
If you decide not to submit a restart job, just press the ENTER key without selecting a restart entry, or
press the PF3 key. Your original job specifications are used to submit a normal LOAD batch job. But
remember: if pertinent restart information exists and you do not use it, you probably will create duplicate
records in the screening file. (The only exception is when the key of the restart entry is blank, indicating
that no records were loaded by the failed LOAD job.)
LOAD 4-18 September 1993
-------
AIRS User's Guide
Volume AQ3 Air Quality Data Storage
While the LOAD restart screen is displayed, you may use the following standard AIRS PF keys:
PF3 submit a batch job then return to the AQ submit menu
PF4 return to the AIRS AQS main menu
PF5 terminate your AIRS terminal session
PF8 display the next restart screen
If you use any other PF key or a PA key, an error message is displayed at the top of the screen.
The following error messages can occur while the LOAD restart screen is displayed:
INVALID SELECTION
This error occurs when you enter a restart entry option that is not displayed at the bottom of the
screen. Enter one of the displayed options to submit a restart job or delete a restart entry, or
erase the invalid number and press ENTER to submit a normal LOAD job.
USER ID NOT = TO USER SIGNED ON
This error occurs when you select a restart entry that does not have your user-ID associated with
it. Choose an entry that has your user-ID or erase the option and press ENTER to submit a
normal LOAD job. (See "Restart Precautions" below.)
INVALID PF KEY
This message occurs if you use the PF8 key when it is not allowed. PF8 is allowed when
"PF8=MORE" is displayed near the bottom of the screen. The PF8 key pages forward to the
next screen of LOAD restart entries if there are too many entries to fit on one page.
NAT1011 REQUESTED FUNCTION KEY NOT ALLOCATED.
This message results from the use of any PA key or any PF key other than PF3, PF4, PF5, or
PF8. Only those four PF keys are valid on this screen.
4.3.5.3 Restart Precautions
You must use the same input transaction file for a LOAD restart job as for the original job. If you were
to use a different input file, the restart facility of LOAD could not work properly. For the same reason,
you must not change anything in the transaction file between the initial and the restart LOAD jobs.
If other users are loading transactions into the same screening file contemporaneously, or if you are one
of a group of users who share responsibility for loading an input transaction file, there may be restart
entries for the other users. Be aware that you are not permitted to restart a failed LOAD job that was
submitted by another user. If you choose another user's restart entry, an error message is displayed
at the top of the LOAD restart screen and the LOAD batch job is not submitted. If you simply made a
mistake and typed the wrong number, correct it and press ENTER again. However, if the only available
restart entry is for another user, you should abort the LOAD process with the PF4 or PF5 key (see
below), and have the other user submit the LOAD restart job. The only other alternative, which is not
recommended, is to ignore the restart information and submit a normal LOAD job.
September 1993 4-19 LOAD
-------
AIRS User's Guide
Air Quality Data Storage Volume AQ3
4.3.6 LOAD Job Submission
When all the fields of the LOAD job submission screen are correct and the restart screen processing is
completed, the LOAD batch job is submitted using the parameters you specified on the LOAD job
submission screen. If it is a restart job, however, the job name from the restart entry is used instead of
the name you specified on the job submission screen.
Reference Section 3.6.5 for more details on batch job submission.
LOAD 4-20 September 1993
-------
AIRS User's Guide
Volume AQ3 Air Quality Data Storage
05/27/90 AIRS AIR Quality Subsystem ; MESSAGE
Messages for Screening File OCSCSF02
Date Tire User Message Text---— — -• -
K 01-07 20:24 USR EDIT failed - an ADABAS error occurred for JOB 'USREDIT1.
0 01-08 09:36 OOU LOAD failed - Screening File 'OCSCSF02' was locked.
D 01-08 12:42 DOU LOAD unsuccessful -Input Transaction File uac; empty.
0 01-08 12:11 DOU LOADed 00002704 records into Screening File 'OCSCSF02'.
D 01-09 13:27 DOU EDITed 00002704 records in Screening File 'OCSCSF02'.
NO MORE MESSAGES
D,K = msg disp PF8=next PF3=end PF4=main menu PF5=terminate PA1=oops
Figure 4-7. Sample MESSAGE Screen Showing LOAD Messages
September 1993 4-21 LOAD
-------
AIRS User's Guide
Air Quality Data Storage Volume AQ3
4.4 LOAD Validation Procedures
This section tells how to determine whether a batch LOAD job was successful.
As outlined in Section 3.7 of this manual, there are two sources of information about the status of your
batch LOAD job: a message you can view using the MESSAGE process, and the printed output of the
batch job.
4.4.1 Using the MESSAGE Process
The MESSAGE process of the AQ Data Storage Subsystem is the method provided by AIRS for
determining whether a LOAD batch job was successful. Detailed instructions for using MESSAGE are
presented in Section 8 of this manual. In brief, MESSAGE displays on your terminal screen the
messages pertinent to your screening file that have been generated by the batch processes of the Air
Quality Subsystem, including LOAD, EDIT, and UPDATE.
A LOAD message indicates whether the LOAD batch job was or was not successful and includes the
user-ID of the person who submitted the batch job and the date and time of job execution. If LOAD was
successful, the message tells how many transaction records were loaded. If LOAD failed, the message
indicates the reason why. The sample MESSAGE screen on the facing page shows examples of both
kinds of LOAD messages.
It is possible to get misleading information if you use MESSAGE while your LOAD batch job is
executing. When the LOAD batch program begins executing, it writes a message that says the job failed
because of a "system error". This is done so the appropriate message will be in place in case the job
does fail later due to a system error, such as exceeding the time limit for the job. When the LOAD
program completes its processing of the input transaction file, it replaces the "system error" message with
one that says the LOAD was successful. Similarly, if the LOAD program terminates because of a non-
system error condition (the screening file is locked, for example), it replaces the "system error" message
with the appropriate LOAD error message.
The point of this discussion is: wait until your LOAD batch job has finished executing before you use
MESSAGE to check its status. Otherwise, you may be misled by the temporary error message the LOAD
program creates.
LOAD 4-22 September 1993
-------
AIRS User's Guide
Volume AQ3
Air Quality Data Storage
09/30/93
AMP010
AEROMETRIC INFORMATION RETRIEVAL SYSTEM
AIR QUALITY SUBSYSTEM
LOAD SUMMARY REPORT
FOR SCREENING FILE OOEVSF10
INPUT TRANSACTION FILE: SYS87105.T104133.RAOOO.TADLOADD.R0000007
PAGE: 1
1ST VOLUME: B14467
TRANSACTION TYPE
SITE
MONITOR
SLAMS
HOURLY
DAILY
COMPOSITE
PRECISION
ACCURACY
INVALID
TOTAL
A1-A7
F1-F5
M.N.P.R-V
1
2
3
8
9
NUMBER
6
3
14
204
111
104
116
12
1
571
09/30/93
AMP010
AEROHETRIC INFORMATION RETRIEVAL SYSTEM
AIR QUALITY SUBSYSTEM
LOAD SUMMARY REPORT
FOR SCREENING FILE ODEVSF10
INPUT TRANSACTION FILE: ASWD.TRAINING.TESTOATA.NEW
PAGE: 1
1ST VOLUME: USS199
TRANSACTION TYPE
SITE
MONITOR
SLAMS
HOURLY
DAILY
COMPOSITE
PRECISION
ACCURACY
INVALID
TOTAL
A1-A7
F1-F5
M.N.P.R-V
1
2
3
NUMBER
11
7
14
224
111
104
120
12
1
604
Figure 4-8. Sample LOAD Summary Reports for Successful Jobs
These samples show report formats for tape (top) and disk (bottom) files.
September 1993
4-23
LOAD
-------
AIRS User's Guide
Air Quality Data Storage Volume AQ3
4.4.2 Using LOAD Printed Output
The primary means of determining the success or failure of a LOAD batch job is the printed output of
the job. Unless the LOAD program terminates due to a system error, such as an I/O error, it generates
a LOAD summary report. You can tell easily from the summary report whether LOAD was or was not
successful.
If there is no LOAD summary report, then the batch job terminated due to a computer system error.
Look at the JES2 job log and die job step summary to determine what the error was. Contact the AIRS
database administrator or the computer center user support department for assistance if you need help.
Samples of the LOAD summary report are shown on the facing page and on the next page. The heading
of the report always has the same format. The date of program execution is printed in the upper left
corner of the page using the mm/dd/yy format. The name of the screening file into which transactions
were to be loaded is printed at the middle of the page in the last line of the heading. If the input
transaction file is catalogued, the name of the file is listed at the left side of the page just below the
heading. At the right side of the page in the same line is a field labeled "1st volume". This is the ID-
number of the tape volume (reel) or the disk pack on which the input transaction file resides. If your
input transaction file is on tape and is not catalogued, the tape ID-number printed in the LOAD report
can help you keep track of which file the report applies to.
The body of the report has three basic formats, depending on whether LOAD was or was not successful.
In the usual case, when LOAD processes the input transaction file successfully, the report body lists the
number of transactions loaded, including the total number and a breakdown by transaction type. Only
the transaction types actually present are listed, so if there were no site transactions, for example, there
is no report entry for site transactions. Examples of this report format are shown one the facing page.
If LOAD was not successful, the body of the summary report is a message that identifies the error
condition. The message has two general formats depending on the type of error. Examples are shown
in the figure on the next page. In the first case, a one-line message identifies a condition the LOAD
program detected that prevented it from loading transactions into the screening file. Examples of this
kind of error are an empty input transaction file or a screening file locked for update processing. In the
second case, a one-line message indicates that an "ADABAS error" occurred and additional information
is listed below the message. An error of this kind implies some sort of malfunction in ADABAS, the
AIRS database, or the LOAD program. Be sure to contact the AIRS database administrator if LOAD
terminates due to an ADABAS error. The information listed below the error message may be useful for
diagnosing and correcting the problem.
LOAD 4-24 September 1993
-------
AIRS User's Guide
Volume AQ3
Air Quality Data Storage
09/30/93
AMP010
AEROMETRIC INFORMATION RETRIEVAL SYSTEM
AIR QUALITY SUBSYSTEM
LOAD SUMMARY REPORT
FOR SCREENING FILE ANADBA10
INPUT TRANSACTION FILE: JVMASWO.TEMP.SR839B
ERROR: THE LOAD COULD NOT BE DONE BECAUSE USER-ID 'JVM' CANNOT UPDATE THE SCREENING FILE.
PAGE: 1
1ST VOLUME: USS187
09/30/93
AMP010
AEROMETRIC INFORMATION RETRIEVAL SYSTEM
AIR QUALITY SUBSYSTEM
LOAD SUMMARY REPORT
FOR SCREENING FILE ANADBA10
PAGE:
INPUT TRANSACTION FILE: TADASWD.CORRECT.DATA 1ST VOLUME: USR020
ERROR: THE LOAD COULD NOT BE DONE BECASUE OF AN ADABAS ERROR. PLEASE KEEP THIS REPORT AND NOTIFY THE AIRS DATABASE ADMINISTRATOR.
CONTROL-BLOCK
COMMAND-CODE
COMMAND-ID
FILE-NUMBER
RESPONSE-CODE
ISN
ISN-LOWER-LIHIT
ISN-QUANTITY
FORMAT-BUFFER-LENGTH
RECORD-BUFFER-LENGTH
SEARCH-BUFFER-LENGTH
VALUE-BUFFER-LENGTH
Nl
TAD
0079
0201
00000000
00000000
00000000
0020
0110
0000
0000
ISN-BUFFER-LENGTH
COMMAND-OPTION-]
COMMAND-OPTION-2
ADDITIONS-!
ADDITIONS-2
FIELD-IN-ERROR
BYTE-IN-ERROR
ADDITIONS-3
ADDITIONS-4
COMMAND-TIME
USER-AREA
1234567890123456789012345678901234567890
FORMAT-BUFFER • AA.
RECORD-BUFFER
370679001
14015
?XV«20111860910
TADOO
SEARCH-BUFFER •
VALUE-BUFFER •
0000
-8900
****
00005607
ASWO
Figure 4-9. Sample LOAD Summary Reports for Failed Jobs
These samples show report formats for minor (top) and ADABAS (bottom) errors.
September 1993
4-25
LOAD
-------
AIRS User's Guide
Air Quality Data Storage Volume AQ3
All the error messages the batch LOAD program can generate are listed below, with a brief explanation
of the cause of the error and what you can do to resolve it. In practice, some of the messages will never
occur because the top level user session checks for the pertinent error condition. Two messages are listed
for each error condition. The first one is printed in the LOAD summary report. The second one is the
message you get with the MESSAGE process.
ERROR: THE SCREENING FILE COULD NOT BE ACCESSED BECAUSE IT DOES NOT
EXIST.
LOAD failed - Screening File 'name'does not exist.
The LOAD program could not find information about the specified screening file in the AIRS
Table file. This could only occur if the Table file changed between the time you submitted the
LOAD job and the time it executed. Contact the AIRS database administrator.
ERROR: THE SCREENING FILE IS NOT FOR AIR QUALITY DATA.
LOAD failed - Screening File 'name' not for AQ data.
The specified screening file is for Facility data rather than Air Quality data. This could only
occur if the Table file changed between the time you submitted the LOAD job and the time it
executed. Contact the AIRS database administrator.
ERROR: THE SCREENING FILE COULD NOT BE ACCESSED BECAUSE IT WAS LOCKED
FOR OTHER PROCESSING.
LOAD failed - Screening File 'name' was locked.
The specified screening file has been locked for update processing using the NOTIFY process.
If the file was locked unintentionally, you may be able to unlock it with the NOTIFY process.
If the AIRS database administrator has used the SCAN process on the screening file, it cannot
be unlocked with NOTIFY. Contact the AIRS database administrator.
ERROR: THE SCREENING FILE COULD NOT BE ACCESSED BECAUSE IT WAS IN USE.
LOAD failed - Screening File 'name' was in use.
The specified screening file was in use for an extended period of time when the LOAD program
attempted to use it. Another AIRS process or maintenance functions performed by the computer
center may have been using the file. Initiate LOAD again.
ERROR: THE LOAD COULD NOT BE DONE BECAUSE USER-ID 'user-ID9 CANNOT
ACCESS THE SCREENING FILE.
LOAD failed - you cannot access Screening File 'name'.
You are not authorized to use the specified screening file. This could only occur if the Table file
changed between the time you submitted the LOAD job and the time it executed. Contact the
AIRS database administrator.
LOAD 4-26 September 1993
-------
AIRS User's Guide
Volume AQ3 Air Quality Data Storage
ERROR: THE LOAD COULD NOT BE DONE BECAUSE USER-ID '< user-ID >' CANNOT
UPDATE THE SCREENING FILE.
LOAD failed - you cannot update Screening File ' '.
You are authorized only to read the specified screening file, not to update it by loading
transactions. This could only occur if the Table file changed between the time you submitted the
LOAD job and the time it executed. Contact the AIRS database administrator.
ERROR: THE LOAD COULD NOT BE DONE BECAUSE INPUT TRANSACTION FILE
'< name >' WAS EMPTY.
LOAD unsuccessful - Input Transaction File was empty.
The specified input transaction file did not contain any records when the LOAD program
executed. If you are using uncatalogued tape input, verify that it is unlabeled, that the input
transactions are in the first file on the tape, and that you specified the correct tape ID-number.
If you are using a catalogued tape or disk file for input, verify that you specified the correct
dataset name. If your specifications are correct, contact the AIRS database administrator or the
computer center for assistance.
ERROR: THE LOAD COULD NOT BE DONE BECAUSE THE RESTART ISN '< number >'
DOES NOT EXIST.
LOAD failed - Restart ISN ' < number >' does not exist.
The LOAD program could not find the required restart information in the AIRS Table file. This
could only occur if the Table file changed between the time you submitted the LOAD job and the
time it executed. Contact the AIRS database administrator.
ERROR: THE LOAD COULD NOT BE DONE BECAUSE OF AN ADA BAS ERROR. PLEASE
KEEP THIS REPORT AND NOTIFY THE AIRS DATABASE ADMINISTRATOR.
(The rest of this message lists AD ABAS parameters.)
LOAD failed - an ADABAS error occurred for JOB ' '.
An error occurred for which the LOAD program cannot take corrective action. Contact the AIRS
database administrator and pass along the information in the error report so the problem can be
resolved.
(No LOAD summary report is generated by the batch job.)
LOAD failed - a system error occurred for JOB ''.
A "system error" occurred while the LOAD program was running. This type of error includes
things such as exceeding the time limit for the job or an I/O error. If neither a message nor a
LOAD summary report is generated, there may be something wrong with the JCL for the batch
job. An invalid dataset name could cause this kind of error. Contact the AIRS database
administrator or the computer center user support department for assistance if you need it. You
should determine the cause of the error before initiating LOAD again.
September 1993 4-27 LOAD
-------
AIRS User's Guide
Air Quality Data Storage Volume AQ3
4.5 LOAD Follow-Up Procedures
When you have successfully loaded an input transaction file into a screening file, there remain only a few
more things to do to complete the LOAD process.
If your file of AIRS input transactions is on tape, you should notify the computer center that you have
finished using the tape and request that it be returned to you. Promptly removing your tape from the
computer center minimizes the tape storage charges assessed against your computer account and reduces
the number of tapes the computer center must deal with. •'
You should make sure the other members of your user group are aware of which screening file you are
using and that you have loaded transactions into it. It is probably not advisable for two people to use the
same screening file at the same time for different sets of transactions. Keeping the other members of
your group informed of the status of your screening file may prevent usage conflicts. However, there
is no limitation on usage of a screening file inherent in the AIRS software. If you prefer to share a
screening file with other users in your group, or if you want to load several different sets of transactions
into a screening file yourself, you can do so.
You may find it helpful to generate a listing of the data in your screening file. A standard report is
available in the Air Quality Data Retrieval Subsystem for producing a listing of the raw data transactions
in a screening file. See Volume AQ4 of this User's Guide for details.
The EDIT process follows logically after LOAD. The transactions you have loaded must pass edit checks
applied by the EDIT process before you can notify the AIRS database administrator to use them for
updating the database. The next section of this manual explains how to use EDIT.
LOAD 4-28 September 1993
-------
AIRS User's Guide
Volume AQ3 Air Quality Data Storage
4.6 Restrictions, Limitations, and Warnings
You should consider the following points with respect to using the LOAD process:
1. Do not bypass the AIRS top level user session and submit a LOAD job directly, even if you are
an experienced user of the NCC. The batch part of the LOAD process depends on error checking and
other validation done in the top level user session. Bypassing that error checking could cause corruption
of your screening file or error termination of the LOAD program.
2. The user profile screen lists all the screening files you are authorized to use, and it does not
indicate the status of the files. If you select a screening file that is locked for update processing, LOAD
will fail because it cannot access the screening file. Be sure you choose an appropriate screening file.
3. Be sure you do not load the same set of input transactions into two different screening files. The
EDIT process does not detect this condition. If both screening files were used in update processing, the
UPDATE program would error terminate. That is something the AIRS database administrator would
prefer not happen.
4. Be sure you load your input transactions into the right screening file. There is no easy way to
delete many transactions from a screening file, and there is no way to move transactions from one
screening file to another.
5. Remember that LOAD only adds records to a screening file; it does not delete or replace any
records already there. If you want to delete records from a screening file before running LOAD, you
can use CORRECT to delete a fairly small number of records. Contact the AIRS database administrator
if you need to delete a large number of screening records. The database administrator can use a utility
program that deletes large numbers of records much more efficiently than CORRECT.
September 1993 4-29 LOAD
-------
AIRS User's Guide
Volume AQ3 Air Quality Data Storage
5.0 The EDIT Process
EDIT is logically the second process of the AQ Data Storage Subsystem of AIRS. This section describes
what EDIT does and how to use it.
5.1 Overview
EDIT is a batch process that validates the AIRS transactions in a screening file. Only after transactions
have been completely validated by EDIT can they be used to update the AIRS database.
The data flow diagram in Figure 5-1 illustrates how EDIT is invoked and what it does. Like other batch
AIRS processes, EDIT executes under the control of JCL and parameters that you specify during an AIRS
terminal session. The primary input to the process is a screening file of AIRS transactions, and the
primary output is a report that identifies errors found and summarizes the edit: status of the transactions.
The Geo-Common, summary, and raw data files of the AIRS database are secondary inputs, and EDIT
may modify the screening file by setting the edit level field of the records it validates. EDIT also
accesses the Table File to read and write control information and to write a status message that you can
view using the MESSAGE process.
EDIT validates all the transactions (records) of a screening file except those marked as excluded, which
are counted but otherwise ignored. (Exclusion status is set or cleared with the CORRECT process,
described in the next section.) The validation involves three classes of edit checks, referred to as level-1,
level-2, and level-3, which are described in the next section. The status of each transaction with respect
to validation is stored in the screening record. When all the fields of a transaction have passed a certain
level of edit checks, EDIT stores a value (1, 2, or 3) in field EDIT-LEVEL-FLAG of the screening.
record, and the transaction is said to have passed that level of edit checks. A transaction must pass the
checks at each level before it is checked at the next level. When a transaction has passed all three levels
of edit checks, it can be used to update the AIRS database. A value of zero in field EDIT-LEVEL-FLAG
indicates that a transaction has not passed any level of edit checks.
Once a transaction has passed level-1 or level-2 edit checks, EDIT does not repeat those checks on
subsequent executions of the program. On the other hand, EDIT applies level-3 edit checks to eligible
transactions every time you run it. Because the level-3 checks are expensive to perform, an option is
available which allows you to specify the highest level of edit checks to be applied in a given execution
of the EDIT program. Using that option, you can find and correct the lower-level edit errors before
applying the more expensive level-3 validation. There are no other EDIT options, and EDIT does not
have (or need) a restart mechanism like the LOAD process.
September 1993 5-1 EDIT
-------
Air Quality Data Storage
AIRS User's Guide
Volume AQ3
Top LeveI
User
Sess ion
Menus
JOB
JCL and
parameters
ADABAS
Table
Fi le
t
AMPD5D
EDIT
Program
Summary Report
ADABAS
Err or Repor t s
Figure 5-1. EDIT Data Flow Diagram
EDIT
5-2
September 1993
-------
AIRS User's Guide
Volume AQ3 Air Quality Data Storage
5.1.1 Edit Levels and Edit Checks
EDIT performs three types of transaction validation, called level-1, level-2, find level-3 edit checks. In
theory, the scope of each type of edit check is fairly well defined, ranging from validation of an
individual field to validation of many transactions in relation to values already in the AIRS database. In
practice, the distinctions among the types of edit checks are sometimes difficult to make, and the level
assigned to a particular edit check is an arbitrary decision.
The purpose of level-1 checks is to assure that each field or closely related group of fields of a transaction
has an appropriate value. For example, the level-1 edit checks would verify that a state code is valid or
that a numeric field has a numeric value within allowed limits. Many of the level-1 edit checks are done
by comparing the value coded on an AIRS transaction with the permitted values stored in the AIRS Geo-
Common and Site files. Some of the checks use tables of allowed values that are coded in the EDIT
program. The program developers tried to minimize the number of these internal tables, since they are
more difficult to change and document than values in the Geo-Common file.
The level-2 edit checks validate the relationships between transactions or between related fields on
different transactions. The most common level-2 check is for duplicate transactions, in which two or
more screening records have identical values for the fields that uniquely identify a transaction. Another
example is checking that both of two related transactions are present in the screening file when one cannot
be used without the other.
All the other types of transaction validation are lumped together as level-3 edit checks. One type of level-
3 edit check is the simulated update, which determines whether the action specified by a transaction
makes sense with respect to the database file it affects. For example, the simulated update rejects a
transaction that would delete information that is not there to delete, or would insert a value where one
already exists. Another main category of level-3 edit checks is the statistical tests of data values. They
test the properties of groups of data values after the simulated update has been done, which means the
tests may involve values both from transactions and from the database. The statistical tests attempt to
mimic the judgement of a human data analyst with respect to the reasonableness of the data values for
a day or a month. The tests identify values that do not conform with empirically derived measures of
"goodness", typically values that are substantially different from other contemporary values.
Detailed information about edit checks is presented in Volume AQ2 of this User's Guide. Volume AQ2
describes how to code Air Quality transactions and tells how to correct edit errors.
September 1993 5-3 EDIT
-------
AIRS User's Guide
Air Quality Data Storage Volume AQ3
5.1.2 Modification of Screening Records
Generally speaking, EDIT changes only the EDIT-LEVEL-FLAG field of screening records and does not
alter any data fields. Numeric fields are the one exception. EDIT replaces leading blanks with zeros
in numeric fields and rewrites the screening record. This applies to all fields defined as numeric in the
coding instructions in Volume AQ2 of this User's Guide. The replacement takes place only if the
numeric field has a value; it does not occur if the numeric field is completely blank.
EDIT does the replacement of leading blanks before applying edit checks to a screening record, since edit
checks of numeric fields require that every position of the field contains a digit. The CORRECT process
applies the same level-1 edit checks as EDIT, but does not replace leading blanks beforehand. If you
view screening records with CORRECT before running EDIT, any numeric fields with leading blanks
will be flagged as invalid by the edit checks CORRECT does.
EDIT 5-4 September 1993
-------
AIRS User's Guide
Volume AQ3 Air Quality Data Storage
02/16/90 AIRS Air Qualfty Subsystem AAPOOOO
User Profile COT
Password: Account Code: ASUD
Printer ID: RM1000 Bin Number: 8112
SCREWING FILES .--- —
ANAOBF01 Air Quality Screening File Read Only Mot Locked
ANADBF95 Air Quality Screening file Read Only Not Locked
OCSCSF01 Air Quality Screening File Update Hot Locked
Enter Proftie Data (optional)
PF3=end PF4=subsystem menu PF5=terminate
02/22/90 AIRS Air Quality Subsystem AAPOOOA
Main Menu
1. Submit Data
2. Retrieve Data - Standard Batch
3. Retrieve Data - Ad Hoc Batch
4. Browse Data - Online
Please enter selection: 1
NEED ASSISTANCE?
CALL THE AQS HOTLINE AT 1-800-333-7909
PF3=end(profile) - . PF4=subsystem menu PF5=terminate
Figure 5-2. AIRS AQS User Profile and Main Menu Slcreen
The AIRS AQS main menu appears after the user profile is established.
September 1993 5-5 EDIT
-------
AIRS User's Guide
Air Quality Data Storage Volume AQ3
5.2 EDIT Initiation Procedures
This section tells how to initiate the EDIT process. "Initiating" EDIT means specifying the information
needed for the EDIT program and submitting a batch job to execute it. In order to have something to
EDIT, you must load input transactions into a screening file with the LOAD process which is described
in Section 4 of this manual.
You initiate the EDIT process by selecting the appropriate options from the menus of the AIRS Top Level
User session and entering the required information. See Section 3.4 of this manual for AIRS logon
procedures, Section 3.6 for Top Level User procedures.
5.2.1 User Profile Screen
When you begin an AIRS terminal session, the first screen is the user profile. A sample is shown in
Figure 5-2. To use EDIT, you must enter a password and choose a screening Tile on the user profile
screen. If you neglect to enter a password, the EDIT initiation will appear to work correctly, but the
EDIT program will not be able to access your screening file and the batch job will terminate in error.
Be sure you enter your AIRS password and select a screening file.
5.2.2 AIRS AQS Main Menu
The second screen of an AIRS terminal session is the AIRS AQS main menu. A sample is shown in
Figure 5-2. Choose option 1, "submit air quality data". If you forgot to select an air quality screening
file, the main menu screen displays an error message and you are advised to return to the user profile
screen to select a screening file. An error message is not displayed if you forgot to enter your AIRS
password.
EDIT 5-6 September 1993
-------
AIRS User's Guide
Volume AQ3
Air Quality Data Storage
05/25/89
AIRS Air Quality Subsystem
Submit
AMP002
Enter Selection: 2
1. LOAD Input Transactions to Screening JFile ::
2. EDIT Screening File (Batch Execution)
3. CORRECT Screening File (Online Adds, Changes, Deletes)
4. NOTIFY AIRS Data Base Administrator for UPDATE :
5. RECEIVE Messages :
:6. DELETE all Transactions from Screening File
PF3=end
PF4=subsystem menu
PF5=terminate
05/25/89
ENTER:
PF3=end
AIRS Air Quality Subsystem
JCL Parameters for EDIT Batch JOB
AHP002
Edit Level
Screening File Id
JOB Name
Account Code/UID
Time (MM , SS)
Priority
Message Class
Number of Copies
Form Number
Room/Bin Number
Hold Output (Y/N)
Printer Site Id
1
ANADBF96
SFP EDIT1
ASUD AIRSP
03,00
2
A
01
B132
N
RMTOOO
Press ENTER to submit JOB
PF4=subsystem menu
PF5=terminate
Figure 5-3. The EDIT Job Submission Screen
The EDIT job submission screen appears after seleciing submit menu option 2.
September 1993
5-7
EDIT
-------
AIRS User's Guide
Air Quality Data Storage Volume AQ3
5.2.3 AQ Submit Menu
The AQ Data Storage Subsystem "submit" menu, shown in Figure 5-3, is the third screen of the AIRS
terminal session. To invoke EDIT, select option 2 of the submit menu, "EDIT screening file (batch
execution)".
5.2.4 EDIT Job Submission Screen
The EDIT job submission screen appears next. A sample is shown at the bottom of Figure 5-3. Use this
screen to specify the information needed to submit a EDIT batch job.
5.2.4.1 S creen Description
All the fields of the EDIT job submission screen have values from your user profile or appropriate default
values when it is displayed initially.
The first field on the screen is for specifying the highest level of edit checks to be applied to the records
of the screening file.
EDIT LEVEL
is a one-digit field that specifies the highest level of edit checks you want EDIT to perform
during this execution of the program. The default value is 1; acceptable values are 1, 2, and 3.
The next field of the screen is for information only; it is not a data entry field.
SCREENING FILE ID
is the name of the screening file you chose on the user profile screen. Do not change this field.
The other fields of the EDIT job submission screen pertain exclusively to the JCL for the EDIT batch
job. They all have default values that you can change if you desire. You can find more information
about these fields in Chapter 4 of the NCC-IBM User's Guide.
JOB NAME
is the eight-character job name for the batch job to be submitted. The first three characters are
your user-ID and cannot be changed. The last five characters have the default value "EDITl",
but you may change them to any value consisting of letters or numbers.
ACCOUNT CODE
is the NCC-IBM account to which the cost of the EDIT batch job will be charged. The initial
value shown on the screen is what you specified for account code on the AIRS user profile
screen. You can change it to a different value, but it must be a valid code that you are
authorized to use. The FIMAS code "AIRSP", appended to the account code, cannot be changed.
EDIT 5-8 September 1993
-------
AIRS User's Guide
Volume AQ3 Air Quality Data Storage
TIME IN MINUTES,SECONDS
is the maximum CPU time allowed for your EDIT batch job. You may change the default three
minutes, zero seconds to another value so long as it is a valid job time. The amount of time
specified affects when the job will run; jobs with shorter times generally run sooner than jobs
with longer times. The NCC-IBM User's Guide explains the allowed formats of the job time
parameter and the effect of job time on job scheduling. It is difficult to estimate accurately the
amount of time needed for an EDIT batch job, since it depends on the number of transactions
edited, the level of edit checks performed, and the number of errors found. The default time of
three minutes is probably sufficient for performing all three levels of edit checks on 10,000
transactions. A time of one minute is probably enough to perform just level-1 edit checks on the
same number of transactions.
PRIORITY
is a one-digit code that affects job scheduling and cost. The default value "2" is normal priority.
You may specify higher priorities of "3" or "4" which may cause a job to execute sooner, but
cost more. You may specify a lower priority of "1" which causes a job to be executed at night
and costs less. Note that a job with more than ten minutes for CPU time will execute only at
night, so it is pointless to specify any priority but "1" for such a job.
MSGCLASS
(message class) is a one-character code that defines a category of printed output. The default
value "A" is a general category. You may also use "F" to specify output to the laser printer at
NCC.
NUMBER COPIES
is the number of copies of batch job output to be printed. The default value is one; permissible
values are 1 through 99.
FORM NUMBER
is a four-digit code for the type of paper your output is printed on, the number of lines printed
per inch, and whether lower case letters are printed. The default value is blanks, which results
in usage of the standard form (STD). For the local printers at NCC the standard form is 6111,
upper-case only on 15 x 11-inch paper. Other common forms are 6311, for upper- and lower-
case at six lines per inch on IS x 11-inch paper; and 8381, available only on the laser printer,
for upper- and lower-case at eight lines per inch on 11 x 8.5-inch paper. Be aware that remote
printers may not be set up to handle anything but the standard form.
ROOM/BIN NUMBER
is a four-character code used by the computer center for distribution of printed output to the
appropriate location. The initial value shown on the screen is what you specified on the AIRS
user profile screen. You may change it to another valid bin number.
OUTPUT HELD
is a yes/no field that specifies whether the output of your EDIT batch job is to be held in the
output queue of the computer system (yes) or to be printed (no). The default value is "N" (no).
September 1993 5-9 EDIT
-------
AIRS User's Guide
Air Quality Data Storage Volume AQ3
PRINTER-ID
is the printer site-ID where the output of your EDIT batch job is to be printed. The initial value
shown on the screen is what you specified on the AIRS user profile screen. You may change it
to another valid printer site-ID, such as "LOCAL" or "R321" or "N7R100". Tnis field is not
used if you specify "Y" for OUTPUT HELD, and may be blank in that case.
EDIT 5-10 September 1993
-------
AIRS User's Guide
Volume AQ3
Air Quality Data Storage
INVALID FIELD
03/06/90
AIRS Air Quality Subsystem AMP002
JCL Parameters for EDIT Batch JOB
ENTER: Edit Level
Screening File Id
JOB Name
Account Code/UID
TIME
-------
AIRS User's Guide
Air Quality Data Storage Volume AQ3
5.2.4.2 Screen Usage
When you have specified the information on the EDIT job submiss:on screen as you want it, press the
ENTER key. Each field of the screen is checked. If something is wrong an error message is displayed
at the top of the screen, as shown in Figure 5-4, and the cursor is positioned to the invalid field. Correct
the error and press the ENTER key again.
While the EDIT job submission screen is displayed, you may use the standard AIRS PF keys:
PF3 return to the AQ submit menu
PF4 return to the AIRS AQS main menu
PF5 terminate your AIRS terminal session
An error message is displayed at the top of the screen if you use any other PF or PA key. An EDIT
batch job is not submitted when you use any PF or PA key. Upon successful job submission, the Edit
job number screen shown in Figure 5-5 is displayed.
The following messages may occur while the EDIT job submission screen is displayed:
INVALID HELD
This message is displayed if you enter an invalid value or erase the value of a required field. Use
the position of the cursor to determine which field is invalid.
INVALID PF KEY
This message occurs if you use the PF8 key, which is not valid on this screen.
NAT1011 REQUESTED FUNCTION KEY NOT ALLOCATED.
This message results from the use of any PA key or any PF key other than PF3, PF4, PF5, or
PF8. Only the PF3, PF4, and PF5 keys are valid on this screen.
EDIT 5-12 September 1993
-------
AIRS User's Guide
Volume AQ3
Air Quality Data Storage
02/Z7/90
AIRS Air Quality Subsystem
EDIT JOB Number for Screening file AMADBF95
JOB STATUS: JOB 8773 Submitted
PF3=end
PF4=subsystem menu
AMPOO;>
PF5=terminate
Figure 5-5. The EDIT Job Number Screen
This screen appears on a successful EDIT submission.
September 1993
5-13
EDIT
-------
AIRS User's Guide
Air Quality Data Storage Volume AQ3
5.2.5 EDIT Job Submission
When all the fields of the EDIT job submission screen are correct, the EDIT batch job is submitted using
the parameters you specified on the EDIT job submission screen.
Reference Section 3.6.5. for more details on batch job submission.
EDIT 5-14 September 1993
-------
AIRS User's Guide
Volume AQ3 Air Quality Data Storage
01/20/87 AIRS Air Quality Subsystem MESSAGE
Messages for Screening File OTKASF01 !;
Date Time User •••••«——••••» Message Text •- —•--••-:-«.»~--~
K 04-0720:24USREOrr failed • an ADABAS error occurred for JOB 'USREOIT1'.
K 04-09 10:14 USR EDIT failed - Screening File 'OTNASF01' was locked.
D 04-09 17:55 TAD LOADed 00013729 records into Screening File 'OTNASF01'.
D 04-10 23:27 TAD ED ITed 00013729 records in Screening File 'OTNASF01'.
NO MORE MESSAGES
D,K*msg disp PF8=next PF3=end PF4=raain menu PF5=termina'ce PA1=oops
Figure 5-6. Sample MESSAGE Screen Showing EDIT Messages
September 1993 5-15 EDIT
-------
AIRS User's Guide
Air Quality Data Storage Volume AQ3
5.3 EDIT Validation Procedures
This section tells how to determine if an EDIT batch job was successful.
As outlined in Section 3.7 of this manual, there are two sources of information about the status of your
batch EDIT job: a message you can view using the MESSAGE process, and the printed output of the
batch job.
5.3.1 Using the MESSAGE Process
The MESSAGE process of the AQ Data Storage Subsystem is the online method provided by AIRS for
determining whether an EDIT batch job was successful. Detailed instructions for using MESSAGE are
presented in Section 8 of this manual. In brief, MESSAGE displays on your terminal screen the
messages pertinent to your screening file that have been generated by the batch processes of the Air
Quality Subsystem, including LOAD, EDIT, and UPDATE.
An EDIT message indicates whether an EDIT batch job was or was not successful and includes the user-
ID of the person who submitted the batch job and the date and time of job execution. If EDIT was
successful, the message tells how many transaction records were edited. If EDIT failed, the message
indicates the reason why. The sample MESSAGE screen in Figure 5-6 shows examples of both kinds
of EDIT messages.
It is possible to get misleading information if you use MESSAGE while your EDIT batch job is
executing. When the EDIT batch program begins executing, it writes a message that says the job failed
because of a "system error". This is done so the appropriate message will be in place in case the job
does fail later due to a system error, such as exceeding the time limit for the job. When the EDIT
program completes its processing of the screening file, it replaces the "system error" message with one
that says the EDIT was successful. Similarly, if the EDIT program terminates because of a non-system
error condition (the screening file is locked, for example), it replaces the "system error" message with
the appropriate EDIT error message. These messages are listed in the next subsection.
The point of this discussion is: wait until your EDIT batch job has finished executing before you use
MESSAGE to check its status. Otherwise, you may be misled by the temporary error message the EDIT
program creates.
EDIT 5-16 September 1993
-------
AIRS User's Guide
Volume AQ3
Air Quality Data Storage
09/30/93
AMP050
AEROHETRIC INFORMATION RETRIEVAL SYSTEM
AIR QUALITY SUBSYSTEM
EDIT SUMMARY REPORT
FOR SCREENING FILE ANAOBA10
PAGE:
TRANSACTION TYPE
-TRANSACTIONS PRESENTLY AT EDIT LEVELS-
•LEVEL 0- -LEVEL 1- -LEVEL 2-
SITE1
SITE2
SITE3
SITE4
SITES
SITES
SITE?
MONITOR!
MONITOR2
MONITORS
MONITOR*)
SLAMS PM
SLAMS PM
SLAMS PM
SLAMS S02
SLAMS S02
SLAMS CO
SLAMS CO
SLAMS N02
SLAMS N02
SLAMS 03
SLAMS 03
SLAMS PB
HOURLY
DAILY
COMPOSITE
PRECISION
ACCURACY
INVALID
Al
A2
A3
A4
AS
A6
A7
Fl
F2
F3
F4
M
V
N
P
V
R
V
S
V
T
V
U
1
2
3
8
9
TOTAL
1
2
2
1
0
0
0
1
2
1
0
0
1
0
1
0
0
1
0
1
0
1
0
4
4
52
0
0
1
76
1
0
0
0
1
0
0
1
0
0
2
1
0
1
0
1
1
0
1
0
1
0
0
2
0
0
0
0
0
13
0
0
0
0
0
1
1
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
122
51
0
0
0
0
175
PASSED ALL
-EDIT LEVELS-
0
0
1
0
0
0
0
0
0
0
0
0
0
0
1
1
0
0
0
0
0
0
1
96
56
52
120
12
0
340
USER
-EXCLUDED-
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
--TOTAL--
2
2
3
1
1
1
1
2
2
1
2
1
1
1
2
2
1
1
1
1
1
1
1
224
111
104
120
12
1
604
09/30/93
AMP050
AEROMETRIC INFORMATION RETRIEVAL SYSTEM
AIR QUALITY SUBSYSTEM
EDIT SUMMARY REPORT
FOR SCREENING FILE ANAOBA10
PAGE:
ERROR: THE EDIT COULD NOT BE DONE BECAUSE OF AN ADABAS ERROR. PLEASE KEEP THIS REPORT AND NOTIFY THE AIRS DATABASE ADMINISTRATOR.
CONTROL-BLOCK
COMMAND-CODE
COMMAND-ID
FILE-NUMBER
RESPONSE-CODE
ISN
ISN-LOUER-LIMIT
ISN-QUANTITY
FORMAT-BUFFER-LENGTH
RECORD-BUFFER-LENGTH
SEARCH-BUFFER-LENGTH
VALUE-BUFFER-LENGTH
SI
COMP
0063
0201
00000000
00000000
00000000
0060
1550
0040
0080
ISN-BUFFER-LENGTH
COMMAND-OPT ION- 1
COMMAND-OPT ION-2
ADDITIONS-1
ADDITIONS-2
FIELD-IN-ERROR
BYTE-IN-ERROR
ADDITIONS-3
ADDITIONS-4
COMMAND-TIME
USER-AREA
0000
H
1
1
-6280
••**
00008363
ASWO
1234567890123456789012345678901234567890
FORMAT-BUFFER • .
RECORD-BUFFER •
SEARCH-BUFFER • SA.
VALUE-BUFFER • 37063007212113185
Figure 5-7. Sample EDIT Summary Reports for Successful and Failed Jobs
The report formats differ for successful (top) and unsuccessful (bottom) jobs.
September 1993
5-17
EDIT
-------
AIRS User's Guide
Air Quality Data Storage Volume AQ3
5.3.2 Using EDIT Printed Output
The primary means of determining the success or failure of a EDIT batch job is the printed output of the
job. The EDIT program always generates a summary report unless the job terminates due to a system
error, such as exceeding the job time limit. You can tell easily from the summary report whether the
EDIT program executed successfully and get an overview of the results.
If EDIT does not generate a summary report, then the batch job terminated due to a computer system
error. Look at the JES2 job log and the job step summary to determine what the error was. Contact the
AIRS database administrator or the computer center user support department for assistance if you need
help.
When EDIT runs normally, the summary report has the format shown in Figure 5-7. It lists the number
of transactions in several categories and the total number of transactions. If your EDIT summary report
does not look like that, your EDIT job probably was not successful.
If EDIT was not successful, the body of the summary report is a message that identifies the error
condition. An example is shown at the bottom of Figure 5-7. A one-line message describes what
prevented EDIT from editing the transactions, such as a screening file that was locked for update
processing. If the message says that an "AD ABAS error" occurred, additional information is listed below
the message. An error of this kind implies some sort of malfunction in ADABAS, the AIRS database,
or the EDIT program. Be sure to contact the AIRS database administrator if EDIT terminates due to an
ADABAS error. The additional information listed below the error message may be useful for diagnosing
and correcting the problem.
All the "unsuccessful job" messages the EDIT program can generate are listed below, with a brief
explanation of the cause of the error and what you can do to resolve it. In practice, some of the
messages should never occur because the top level user session checks for the pertinent error condition
before submitting the EDIT batch job. Two messages are listed for each error condition. The first one
is printed in the EDIT summary report. The second one is the message you get with the MESSAGE
process.
THE SCREENING FILE SELECTED FOR EDITING WAS EMPTY.
EDITED 00000000 records in Screening File 'name'.
This is really a statement of fact rather than an error. The screening file you selected for editing
was empty or all the records were marked as excluded. Be sure you selected the right screening
file. If you ran LOAD recently to load transactions into die file, verify that LOAD was
successful. If LOAD worked and you specified the right screening file, contact the AIRS
database administrator for assistance.
EDIT 5-18 September 1993
-------
AIRS User's Guide
Volume AQ3 Air Quality Data Storage
ERROR: THE SCREENING FILE COULD NOT BE ACCESSED BECAUSE IT DOES NOT
EXIST.
EDIT failed • Screening File 'name' does not exist.
The EDIT program could not find information about the specified screening file in the AIRS
Table file. This could only occur if the Table file changed between the time you submitted the
EDIT job and the time it executed. Contact the AIRS database administrator.
ERROR: THE SCREENING FILE IS NOT FOR AIR QUALITY DATA.
EDIT failed - Screening File 'name' not for AQ data.
The specified screening file is for Facility data rather than Air Quality data. This could only
occur if the Table file changed between the time you submitted the EDIT job and the time it
executed. Contact the AIRS database administrator.
ERROR: THE SCREENING FILE COULD NOT BE ACCESSED BECAUSE IT WAS LOCKED
FOR OTHER PROCESSING.
EDIT failed - Screening File 'name' was locked.
The specified screening file has been locked for update processing using the NOTIFY process.
If the file was locked unintentionally, you may be able to unlock it with the NOTIFY process.
If the AIRS database administrator has used the SCAN process on the screening file, it cannot
be unlocked with NOTIFY. Contact the AIRS database administrator.
ERROR: THE SCREENING FILE COULD NOT BE ACCESSED BECAUSE IT WAS IN USE.
EDIT failed - Screening File 'name' was in use.
The specified screening file was in use for an extended period of time when the EDIT program
attempted to use it. Another AIRS process or maintenance functions performed by the computer
center may have been using the file. Initiate EDIT again.
ERROR: THE EDIT COULD NOT BE DONE BECAUSE USER-ID 'user-ID' CANNOT ACCESS
THE SCREENING FILE.
EDIT failed - you cannot access Screening File 'name'.
You are not authorized to use the specified screening file. This could only occur if the Table file
changed between the time you submitted the EDIT job and the time it executed. Contact the
AIRS database administrator.
ERROR: THE EDIT COULD NOT BE DONE BECAUSE USER-ID 'user-ID' CANNOT UPDATE
THE SCREENING FILE.
EDIT failed - you cannot update Screening File 'name'.
You are authorized only to read the specified screening file, not to update it. EDIT updates the
screening file by setting the edit level of transactions, so you must have update authority for each
screening file you edit. After determining that you selected the right screening file, contact the
AIRS database administrator to obtain update authority. When you have update authority, you
may initiate EDIT again.
September 1993 5-19 EDIT
-------
AIRS User's Guide
Air Quality Data Storage Volume AQ3
ERROR: THE EDIT COULD NOT BE DONE BECAUSE OF MISSING ARCHIVE RECORD FOR
FILE 'file number'
EDIT failed - ARCHIVE Record missing for Hie 'file number1.
One of the records EDIT needs in order to obtain archive information about database files is not
available. Contact the AIRS database administrator to have this problem corrected. Be sure to
note the file number listed in the message; that information will make it easier to identify and fix
the problem. Do not initiate EDIT again for any screening file until you have been notified that
the problem is fixed.
ERROR: THE EDIT COULD NOT BE DONE BECAUSE OF OVERFLOW OF 'table name'.
EDIT MUST BE MODIFIED.
EDIT failed - 'table name' overflow, please contact ADBA.
The EDIT program has several internal tables that hold information from groups of transactions
while level-3 edit checks are being done. The table named in the error message could not hold
enough items to edit the transactions in your screening file. Note the table name and contact the
AIRS database administrator. Do not initiate EDIT again for the same screening file until you
have been notified that the problem is fixed.
ERROR: THE EDIT COULD NOT BE DONE BECAUSE OF AN ADABAS ERROR. PLEASE
KEEP THIS REPORT AND NOTIFY THE AIRS DATABASE ADMINISTRATOR.
(The rest of this message lists ADABAS parameters.)
EDIT failed • an ADABAS error occurred for JOB 'job name'.
An error occurred for which the EDIT program cannot take corrective action. Contact the AIRS
database administrator and pass along the information in the error report so the problem can be
resolved.
(An EDIT summary report is not generated by the batch job.)
EDIT failed • a system error occurred for JOB 'job name',
A "system error" occurred while the EDIT program was running. This type of error includes
things such as exceeding the time limit for the job or an I/O error. If neither a message nor a
EDIT summary report is generated, there may be something wrong with the JCL for the batch
job. Contact the AIRS database administrator or the computer center user support department
for assistance if you need it. You should determine the cause of the error before initiating EDIT
again.
EDIT 5-20 September 1993
-------
AIRS User's Guide
Volume AQ3 Air Quality Data Storage
5.4 Interpreting EDIT Reports
This section explains how to interpret the reports EDIT generates as a result of applying edit checks to
the transactions in a screening file.
As explained in the previous section, EDIT always generates a summary report unless the job fails due
to a system error. Three other reports may also be generated in addition to the summary report: the error
report, the patterns and gap failure report, and the Shewhart failure report. They follow after the
summary report in the job's printed output.
As indicated by their names, the three additional reports tell what the EDIT program found wrong with
the transactions it checked. Which of the reports is generated depends on the highest level of editing you
requested when you submitted the EDIT job and the types of errors discovered by the EDIT program.
Therefore, the absence of these reports from the EDIT printed output does not necessarily mean the
screening file is error free. Their absence means only that no errors resulted from the types of checks
EDIT performed. For example, if you restricted EDIT to level-1 and level-2 edit checks and the only
errors were at level 3, then none of die three error reports would be generated; but the transactions still
would be invalid. Only after EDIT has applied all three types of edit checks are the transactions
completely validated. Use the information presented in the EDIT summary report and in the error reports
(or the absence of the error reports) to determine when your screening file is sufficiently valid and ready
for update processing.
Volume AQ2 of this User's Guide gives detailed descriptions of the edit checks related to the EDIT error
reports. The following subsections describe what the EDIT reports look like ajid explain how to interpret
them.
September 1993 5-21 EDIT
-------
Air Quality Data Storage
AIRS User's Guide
Volume AQ3
09/30/93
AMP050
AEROMETRIC INFORMATION RETRIEVAL SYSTEM
AIR QUALITr SUBSYSTEM
EDIT SUNHARr REPORT
FOR SCREENING FILE ANAOBA10
PAGE:
TRANSACTION TYPE
-TRANSACTIONS PRESENTLY AT EDIT LEVELS-
-LEVEL 0- -LEVEL 1- -LEVEL 2-
SITE1
SITE:
SITE3
SITE4
SITES
SITE6
SITE?
NONITOR1
MONITORS
MONITORS
MONITOR*
SLAMS PM
SLAMS PM
SLAMS PM
SLAMS S02
SLAMS S02
SLAMS CO
SLAMS CO
SLAMS N02
SLAMS N02
SLAMS 03
SLAMS 03
SLAMS PB
HOURLY
DAILY
COMPOSITE
PRECISION
ACCURACY
INVALID
TOTAL
Al
A2
A3
A4
AS
A6
A7
Fl
F2
F3
F4
M
V
N
P
V
R
V
S
V
T
V
u
1
I
3
8
9
1
2
2
1
0
0
0
1
2
1
0
0
1
0
1
0.
0
1
0
1
0
1
0
4
4
52
0
0
1
76
1
0
0
0
1
0
0
1
0
0
2
1
0
1
0
1
1
0
1
0
1
0
0
2
0
0
0
0
0
13
0
0
0
0
0
1
1
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
122
51
0
0
0
0
175
PASSED ALL
-EDIT LEVELS-
0
0
1
0
0
0
0
0
0
0
0
0
0
0
1
1
0
0
0
0
0
0
1
96
56
52
120
12
0
340
USER
•EXCLUDEO-
--TOTAL--
2
2
3
1
1
1
1
2
2
1
2
1
1
1
2
2
1
1
1
1
1
1
1
224
111
104
120
12
1
604
Figure 5-8. The EDIT Summary Report
EDIT
5-22
September 1993
-------
AIRS User's Guide
Volume AQ3 Air Quality Data Storage
5.4.1 EDIT Summary Report
A sample EDIT summary report is shown in Figure 5-8. The report heading tells when EDIT was run
and what screening file was checked. The date of program execution is printed in the upper left corner
of the page using the mm/dd/yy format. The name of the screening file being edited is printed at the
middle of the page in the last line of the heading.
The report body lists the number of transactions processed, with subtotals for each transaction type and
edit status. The first column of the report, with the heading TRANSACTION TYPE, identifies each type
of transaction in the screening file. Only the transaction types actually present are listed, so if there were
no site transactions, for example, there would be no report entry for transaction types Al - A7. Notice
that type V transactions are listed separately for each of the pollutants to which they apply.
The next three columns of the summary report, under the heading TRANSACTIONS PRESENTLY AT
EDIT LEVELS, give the number of transactions that are presently at level 0, level 1, and level 2 edit
checks.
The PASSED ALL EDIT LEVELS column lists the number of transactions that have passed level-1,
level-2, and level-3 edit checks.
The USER EXCLUDED column gives the number of excluded transactions that EDIT read but did not
check. (All excluded transactions have an edit level of zero, meaning they have not passed any edit
checks.)
The TOTAL column lists the total number of transactions of each type. Similarly, the TOTAL row at
the bottom of the report lists the total number of transactions in each category. The number in the lower
right corner of the report is the total number of records in the screening file.
If all the transactions in your screening file are valid, all the transaction counts will be in the column for
PASSED ALL EDIT LEVELS. If you have excluded some transactions, they will be in the USER
EXCLUDED column. When your screening file is used to update the AIRS database, the number of
transactions processed by the UPDATE program is the same as the total of the PASSED ALL EDIT
LEVELS column in your last EDIT summary report for the file (unless the SCAN process or the database
administrator excludes some of the transactions - see Section 11).
September 1993 5-23 EDIT
-------
Air Quality Data Storage
AIRS User's Guide
Volume AQ3
09/30/93
ANPOSO
AEROHETRIC INFORMATION RETRIEVAL SYSTEM
AIR QUALITY SUBSYSTEM
EDIT ERROR REPORT
FOR SCREENING FILE ANADBA10
PAGE:
RECORD KEY
RECORD I » 1 * 2 + 3-
TRANSACTION
000038SO 03-063-0001-12126-1-86-3-01- - -I 3030630001121261C002091860107410023
E'W"
ERROR - INVALID STATE CODE
WARNING - CANNOT VERIFY COUNTY CODE
00003851 03-063-0001-12126-1-86-3-02- - -I 3030630001121261C002091860207410024
E«W"
ERROR - INVALID STATE CODE
WARNING • CANNOT VERIFY COUNTY CODE
00003852 03-063-0001-12126-1-86-3-03- -
-I 303063000112126K002091860306410025
E'W"
ERROR - INVALID STATE CODE
WARNING - CANNOT VERIFY COUNTY CODE
00003853 03-063-0001-12126-1-86-3-04- - .1 3030630001121261C001091860406410026
ERROR - INVALID STATE CODE
WARNING - CANNOT VERIFY COUNTY CODE
00003854 03-063-0001-12126-1-86-3-06- - -I 3030630001121261C002091860606420029
E'W"
ERROR - INVALID STATE CODE
WARNING - CANNOT VERIFY COUNTY CODE
00003655 03-063-0001-12126-1-86-3-06- - -I 3030630001121261C002091860607420030
E'W"
ERROR - INVALID STATE CODE
WARNING - CANNOT VERIFY COUNTY CODE
00003856 03-063-0001-12126-1-86-3-07- - -I 3030630001121261C002091860702420031
E'W"
ERROR . INVALID STATE CODE
WARNING - CANNOT VERIFY COUNTY CODE
ERROR
.6 « 7 » 8 LEVEL
I 1
I 1
I 1
I 1
I 1
I 1
I 1
00003854 03-063-0001-12126-1-86-3-06-
00003855 03-063-0001-12126-1-86-3-06-
-I 3030630001121261C002091860606420029
-I 3030630001121261C002091860607420030
2 RECORDS ERROR - DUPLICATE RECORDS
I 2
I 2
00003857 03-063-0001-12126-1-86-3-08- -
-I 3030630001121261C002091860806420032
E'W"
ERROR - INVALID STATE CODE
WARNING - CANNOT VERIFY COUNTY CODE
I 1
Figure 5-9. The EDIT Error Report
EDIT
5-24
September 1993
-------
AIRS User's Guide
Volume AQ3 Air Quality Data Storage
5.4.2 EDIT Error Report
The EDIT error report, shown in Figure 5-9, has an entry for every error detected in the AIRS
transactions in the edited screening file, including the "statistical" errors thai: also are listed in the two
reports described below. If no errors are detected, the error report is not printed.
The heading of the error report is like the summary report. Significant items are the date and the
screening file name.
The body of the report has two main parts that identify the transactions and the errors. The leftmost two
columns of the report identify which screening record(s) an error applies to. The RECORD # column
gives a record's ADABAS internal sequence number (ISN), and the RECORD KEY column gives its
AD ABAS "key". These two identifiers can be used in the CORRECT process to find the transactions
that need to be fixed. The "key" is the first 25 characters of the screening record, consisting of codes
for state, county, site, parameter, POC, year, transaction type, month, day, hour, and action code.
Section 6.4 of this volume gives more information about record keys and using them with CORRECT.
The other two columns of the report describe the errors EDIT detected. The ERROR LEVEL column
at the right side of the page indicates which level of edit checks the transaction(s) failed. The
TRANSACTION column displays the error messages and other information to indicate what is wrong
with a transaction.
Entries in the EDIT error report have one of two basic formats. The first format is used when multiple
transactions are involved in an error. (This includes most level-2 errors and many level-3 errors.) In
the multiple-transaction format, the record identification columns list the record number and key of the
first and last transaction involved, with the word "THRU" between them. A message in the
TRANSACTION column tells what the error is and how many transactions are involved. The
transactions are not listed in the error report, however.
The second report format is used for errors that involve a single transaction. The record number and key
of the transaction are shown in their respective columns, and the transaction in question is listed in the
TRANSACTION column in AIRS input transaction format. The second line of the report entry flags the
invalid fields and identifies each problem as an error or a warning. (For Level-3 "Data Exist" errors,
except for transactions types Z and 4, the third line will display the data values on the database. These
values will be identified with a "DB*" notation preceding the value.) Subsequent lines list the pertinent
error messages, one for each error or warning flag. The flags for erroneous fields are the characters "E"
(error) or a "W" (warning), which are printed under the first position of each erroneous field. If the field
is longer than one character, the remaining positions are flagged with asterisks. For example, a five-
character field with an error would be flagged with "E****", while a warning applicable to a two-
character field would be flagged with "W*". The order of the error messages printed in subsequent lines
of the report entry corresponds to the left-to-right order of the error flags.
September 1993 5-25 EDIT
-------
Air Quality Data Storage
09/30/93
AMP050
TEST H - MAX HOUR TEST H
RECORD KEY
3706700014240116610601001
THRU
3706700014240118610621161
3706700014240118610601001
THRU
3706700014240118610621161
3706700014240118610601001
THRU
3706700014240118610621161
3706700014240118610601001
THRU
3706700014240118610621161
AIRS User's Guide
Volume AQ3
AEROMETRIC INFORMATION RETRIEVAL SYSTEM PAGE: 1
AIR QUALITY SUBSYSTEM
EDIT PATTERNS AND GAP FAILURE REPORT
FOR SCREENING FILE ANADBA10
• HI OIFF TEST D - DIXON RATIO TEST S - SPUE TEST C - HI-CONS-4-HR
YYMMDD HOURS -—HOURLY VALUES FAILING TEST(S) / TEST(S) FAILED-— FAILED GAP TEST
860605 00-07
08-15
16-23
860614 00-07
08-15
16-23
860615 00-07
08-15
16-23
8606
860601 00-07
08-15
16-23
860602 00-07
08-15
16-23
860604 00-07
08-15
16-23
640.
680.
650.
685.
680.
H
650.
685.
GAP SIZE
680.
650.
680.
685.
.0680 .
.0685 .
650.
50.
600.
650.
650.
600.
650.
650.
605.
650.
610.
650.
1650
0650
685.
1685.
HHS
690.
655.
H
685.
690.
655.
19 NUN
685.
690.
685.
655.
.1685
.0655
660.
90.
695.
665.
H
665.
H
600.
1660. 1665.
HH C M C
690.
645.
630.
ABOVE GAP
690.
605.
690.
695.
660.
.5660 .
.0660 .
665.
600.
615.
: 224
665.
632.
611.
603.
605.
0665
0665
90.
660.
695.
1690.
M C
660.
695.
690.
SLOT
660.
599.
660.
635.
690.
.0690
.0690
655.
692.
1673.
MH C
643.
690.
685.
BELOW
605.
690.
615.
678.
.0685
.0688
650.
670.
1980.
MHSC
650.
670.
680.
GAP: 3 FAILED GAP
609.
670.
611.
670.
680.
.0680
.0620
Figure 5-10. The EDIT Patterns and Gap Failure Report
EDIT
5-26
September 1993
-------
AIRS User's Guide
Volume AQ3 Air Quality Data Storage
5.4.3 EDIT Patterns and Gap Failure Report
The EDIT patterns and gap failure report, shown in Figure 5-10, is printed only when hourly
(interval = 1) data for a criteria pollutant fail a level-3 statistical test. These tests involve the values for
an entire day (pattern tests) or month (gap test), and may use data both from transactions in the screening
file and from the Hourly File of the AIRS database. If no errors of this type occur the report is not
printed. For each entry in this report there is a corresponding entry in the EDIT error report.
As with the other EDIT reports, the page heading lists the date of report generation and the name of the
screening file. The transactions that fail a pattern or gap test are identified in the RECORD KEY
column, which lists the 25-character "key" of the first and last transactions involved in the test. The
columns labeled YYMMDD and HOURS give the date and time to which the test applies. When a report
entry is for a gap test, the message "FAILED GAP" is printed under the heading FAILED GAP TEST.
The information presented under the HOURLY VALUES FAILING TEST(S) heading depends on which
type of test is involved, pattern or gap. For the gap test, a message is printed that gives information
about the size and position of the gap in the data values. This is followed by a listing of the hourly
values for the month that failed the test. An exception to this is source-oriented S02 data. Only the
message giving the size and position of the gap is printed. The data will be treated as if it had passed
the gap test. Other means are available to list the values for the month. (There are standard AIRS
reports for listing data values in a screening file and in the Hourly File. See Volume AQ4 of this User's
Guide for a description of the Air Quality Retrieval Subsystem.)
For the gap test to be meaningful, there must be a minimum number of values for a month. If there are
not enough values in a particular month, EDIT prints a message warning that the test could not be done
and stating the number of transactions involved. Such transactions do not fail the gap test, since the test
could not be performed. The message is intended to make you aware that the gap test has not been
applied to the transactions in question and that they might have failed the gap test if it could have been
performed.
For failures of the pattern tests, more useful information is listed in the report. The values involved in
the test are listed under the HOURLY VALUES FAILING TEST(S) heading. Under the values are
indicators of the types of pattern test each value failed. The indicators and their meanings are listed
across the top of the report page. Multiple indicators are shown under a value if it fails more than one
pattern test. A value with no indicators under it did not fail any pattern tests.
See Volume AQ2 of this User's Guide for more detailed information about the nature of the gap and
pattern tests.
September 1993 5-27 EDIT
-------
Air Quality Data Storage
AIRS User's £uide
Volume AQ3
03/30/87
AMP050
AEROMETRIC INFORMATION RETRIEVAL SYSTEM
AIR QUALITY SUBSYSTEM
EDIT SHEUHART FAILURE REPORT
FOR SCREENING FILE OCSCSF02
PAGE:
....+....!....+—.2-...*
RECORD KEY
YYMH DAYS
-DAILY VALUES FAILING SHEUHART TEST-
3706700284240118421111 M
THRU
3706700284240118421114 M
4 RECORDS WARNING - NOT ENOUGH DAILY HISTORICAL VALUES TO RUN SHEWHART TEST
3706700284240118520502 M
THRU
3706700284240118520502 M
1 RECORDS WARNING - NOT ENOUGH DAILY HISTORICAL VALUES TO RUN SHEWHART TEST
370670028424011852121S M
THRU
3706700284240118521231 M
8512 01-08 5555. 666.6 7777. 888.8
09-16 9999. 1212. 232.3 34.34 4.54S .5656 .0676 .7878
17-24 8.989 90.90 1313. 2424. .30V .30 .30V 6868.
25-31 7979. 8080. 9191. 1234. 234.5 34.56
Figure 5-11. The EDIT Shewhart Failure Report
EDIT
5-28
September 1993
-------
AIRS User's Guide
Volume AQ3 Air Quality Data Storage
5.4.4 EDIT Shewhart Failure Report
The EDIT Shewhart failure report, shown in Figure 5-11, is printed only when daily (interval=7) data
for a criteria pollutant fails the Shewhart test, a level-3 statistical test. The Shewhart test involves data
for an entire month, and may use values both from transactions in the screening file and from the Daily
File of the AIRS database. If no errors of this type occur the report is not printed.
As with the other EDIT reports, the page heading lists the date of report generation and the name of the
screening file. The transactions that fail the Shewhart test are identified in the RECORD KEY column,
which lists the 25-character "key" of the first and last transactions involved in the test. The columns
labeled YYMM and DAYS give the dates to which the test applies. Under the heading DAILY VALUES
FAILING SHEWHART TEST the report lists the values involved in the test.
The Shewhart test involves the comparison of one month's values with previous months' values. If the
data for previous months is not available, EDIT cannot perform the test. In that case EDIT prints a
message warning that the Shewhart test could not be done and stating the number of transactions
involved. Such transactions do not fail the Shewhart test, since the test could not be performed. The
message is intended to make you aware that the transactions have not been tested, and that they might
have failed the Shewhart test had it been performed.
September 1993 5-29 EDIT
-------
AIRS User's Guide
Air Quality Data Storage Volume AQ3
5.5 EDIT Follow-Up Procedures
When EDIT runs successfully there are two possible situations: no errors were detected with any
transactions or some errors were detected. If there were no errors from level-3 edit checks, you have
nearly completed your part of the AIRS data submission process. All that remains for you to do is to
use the NOTIFY process to inform the ADBA that the screening file is ready for update. Instructions
for using the NOTIFY process are given in Section 7 of this manual.
If EDIT found errors in your screening file, you may use the CORRECT process to fix the errors or to
exclude or delete the erroneous transactions. The EDIT error report serves as a guide for making the
necessary changes with CORRECT. You can locate the erroneous transactions using either the record
number or the 25-character key listed in the error report. After fixing the problems with CORRECT,
run EDIT again to set the edit level of the transactions and to find any additional errors. Repeat this
cycle until the errors have been eliminated.
If you have just a few "problem" transactions that you have not been able to fix after a few EDIT-
CORRECT cycles, it may be better to go ahead and submit the screening file for update processing even
though not all the transactions are fixed. After the update has been done, only the transactions you
excluded or that did not pass level-3 edit checks will be left in the screening file. With only those
transactions in the file, you can fairly cheaply re-edit them until the problems are resolved. You could
then load another set of transactions into the same screening file and combine the old problem transactions
with the new set of transactions in the next update cycle. This procedure could significantly reduce your
costs for each batch of transactions you submit. It also might streamline your operations, since you can
do the research for the problem transactions while the main body of your transactions are going through
the update processing, rather than waiting to submit them until the problems are resolved.
EDIT 5-30 September 1993
-------
AIRS User's Guide
Volume AQ3 Air Quality Data Storage
5.6 Restrictions, Limitations, and Warnings
There are a few points you should consider with respect to using EDIT:
1) Ensure that LOAD has completed successfully before you run EDIT, so that the records to be
edited are in the proper screening file.
2) If EDIT is run with level-3 editing requested it applies the level-3 edit checks not only to the
records at level 2, but also to the records already at level 3. This must be done to ensure that any
changes to the database that could affect the transactions are checked. It also means that it will be
expensive to repeatedly edit a screening file in which most of the transactions are at level-3.
3) EDIT does not "share" a screening file with any other AIRS process. Therefore EDIT waits until
another process, such as CORRECT, has finished using the screening file before it begins to do any edit
checks. Once EDIT has begun, other processes cannot update the screening file (although they can read
it). Do not try to run LOAD or CORRECT at the same time you are running EDIT.
4) Although EDIT checks many things about your transactions, it cannot detect or diagnose every
possible error. With a quick look at a listing of the data in your screening file, you may spot a problem
EDIT missed. You should take an active role in the validation of your transactions and apply your
judgment and experience to ensure the correctness of your data.
September 1993 5-31 EDIT
-------
AIRS User's Guide
Volume AQ3 Air Quality Data Storage
6.0 The CORRECT Process
CORRECT is one of the primary processes of the AQ Data Storage Subsystem of AIRS, like LOAD and
EDIT. This section describes what CORRECT does and how to use it.
6.1 Overview
The main purpose of the CORRECT process is to fix (that is, to correct) errors in the AIRS transactions
in a screening file. Usually, those errors would have been identified by the EDIT process. CORRECT
displays the contents of a screening file record (an AIRS transaction) on your terminal screen using a
format that identifies each field of the transaction. You can alter the displayed transaction by changing
values, adding new values, or erasing values. You also can insert or delete entire records (transactions).
CORRECT applies level-1 edit checks to each transaction it displays, and identifies on the screen any
fields that are invalid. CORRECT has a variety of commands for finding a particular record to be
displayed, switching among its three modes of operation, and applying changes to sets of records. These
are discussed in following sections.
The data flow diagram in Figure 6-1 illustrates CORRECT's operating environment. CORRECT is
invoked directly from the submit menu of the Air Quality Subsystem. It executes online and displays
screens showing AIRS transactions, menu/specification screens, and error screens. CORRECT reads
AIRS transactions from a screening file and writes altered transactions into it. To perform level-1 edit
checks, CORRECT reads information from the Site and Geo-Common files. CORRECT accesses the
Table file to determine whether you have authority to update the screening file or browse (read) it only.
CORRECT also uses the screening file name you selected and the AIRS password you entered on the
AIRS user profile screen.
CORRECT reverts control to the Air Quality submit menu when you terminate it with the PF3 key.
Alternatively, you may invoke the AIRS AQS main menu with the PF4 key or terminate your AIRS
terminal session with the PF5 key. CORRECT processes any pending directives for altering a screening
file record before transferring control or terminating your AIRS terminal session.
September 1993 6-1 CORRECT
-------
Air Quality Data Storage
AIRS User's Guide
Volume AQ3
Menus
CORRECT
Screens
Top LeveI
User
Session
AMP060
CORRECT
Program
ADABAS
Figure 6-1. CORRECT Data Flow Diagram
CORRECT
6-2
September 1993
-------
AIRS User's Guide
Volume AQ3
Air Quality Data Storage
08-08-87
COMMAND
AIRS Air Quality Subsystem - CORRECT
IANAOBF9S
ERROR
*• WARNING :.i:v* •:•"•;;,••• •'•:'-
You ere not authorized to update Screening File ?ANAD8F95'.
You may browse the file but updating will not be allowed.
If you want to continue the CORRECT session,
leave the coonand area blank and press ENTER.
If you want to terminate the CORRECT session, use one of the following.
/Key Command Action
:::PF3 -END Return to the AQ Submit Menu (AMP002)
PF4 RETURN Return to the AIRS Main Menu (AAPOOOA)
PF5 QUIT Terminate the AIRS terminal session
08-08-87
COMMAND ===>
AIRS Air Quality Subsystem - CORRECT
OCSCSF01
ERROR
>>> ERROR <<<
Your password does not permit access to Screening File 'OCSCSFOV.
.You must terminate the CORRECT session.
Enter one of the following directives...
Key Command Action
PF3 END Return to the AQ Submit Menu'(AMP002)
PF4 RETURN Return to the AIRS Main Menu (AAPOOOA)
PF5 QUIT Terminate the AIRS terminal session
Figure 6-2. Sample CORRECT Warning and Error Screens
September 1993
6-3
CORRECT
-------
AIRS User's Guide
Air Quality Data Storage Volume AQ3
6.2 CORRECT Features
This section describes the features of the CORRECT program that form the basis for the operational
procedures presented later in this section.
6.2.1 Screening File Access
CORRECT accesses the Air Quality screening file currently selected for your AIRS session - the one
you chose from the list displayed on the AIRS user profile screen. To do so, CORRECT uses the AIRS
password you also entered on that same screen. If you neglect to enter a password or if you enter it
incorrectly, CORRECT cannot access the screening file.
If you have update authority for the selected screening file, CORRECT allows you to alter the contents
of the file. (The AIRS user profile screen lists the type of access authority you have for each screening
file.) If you have read-only authority for a screening file, CORRECT will display records but will not
allow you to alter them. The same rule applies if you have update authority but the screening file has
been locked using the NOTIFY process: you can browse the transactions, but CORRECT will not permit
you to alter the file. Once the AIRS database administrator has locked a screening file for update
processing, CORRECT will not access the file at all. (The NOTIFY section of this volume gives more
information about locked screening files.)
If CORRECT determines that your access to a screening file must be restricted or denied, it displays a
screen to tell you so. The screens in Figure 6-2 show samples of such screens. The screen at the top
of the page is an example of a warning message, informing you that access to the screening file is
restricted. You can choose to use CORRECT to browse the file, without altering anything, or choose
to terminate CORRECT. The screen at the bottom of the page is an example of an error message,
informing you that access to the screening file is denied. You have no choice but to terminate
CORRECT.
CORRECT 6-4 September 1993
-------
AIRS User's Guide
Volume AQ3
Air Quality Data Storage
AQ
Submit
Menu
I
CORRECT
Normal
Mod*
CORRECT
Global
Mode
CSelect Data}
I
CORRECT
Global
Mode
CEnter Changes}
I
CORRECT
Global
Mode
CProcess Dote}
CORRECT
Input
Mode
CChoose Type]
I
CORRECT
Input
Mode
CEnter Data}
September 1993
Figure 6-3. CORRECT Modes of Operation
6-5
CORRECT
-------
AIRS User's Guide
Air Quality Data Storage Volume AQ3
6.2.2 Modes of Operation
CORRECT has three operating modes: normal, global, and input. Figure 6-3 illustrates the relationships
among the modes and types of screens displayed in each mode.
Normal mode is the default or basic operating mode. It might be called a single-record mode. In this
mode, you can direct CORRECT to access any record in the screening file based on its record number
(assigned by ADABAS) or its "key" (the data fields that uniquely identify a transaction). You can also
make CORRECT go from the current record to the next one, to the first record for the next monitor or
next site, to the next record failing level-1 edit checks, or to the first record in the file (all in key order).
Normal mode is suited for correcting isolated errors in transactions that EDIT has identified, and for
browsing transactions in key order.
Global mode allows you to select a subset of transactions in the screening file on the basis of attributes
you specify, and to apply changes to them if you wish. This mode facilitates making the same correction
to several related records or viewing records in a particular category. For example, you could change
the method code of all the transactions from a particular monitoring site, or you could look at all the
transactions that failed level-1 edit checks. If you specify changes for the transactions, you can choose
whether to view each one after the changes have been applied. When a transaction is displayed, you can
make additional changes to it or even delete it, just as if you were in normal mode. If you choose not
to view the transactions as they are being changed, CORRECT may display a status screen periodically
to inform you of the progress of the global changes.
You can use input mode to create new AIRS transactions (screening file records). Transaction data
entered in this way through CORRECT are stored exactly like data loaded into the screening file from
card-image transactions using the LOAD process (see Section 4). This method of entering data is suitable
only for small amounts of data, since everything must be typed in by hand. You choose from a menu
which type of transaction you want to create, then CORRECT displays a screen appropriate for that type
and you enter values for the fields. You can create several transactions of the same type without having
to go back to the transaction type selection menu. If you do this, CORRECT retains the values entered
for "key" fields from screen to screen so you do not have to enter them for every transaction.
In CORRECT's normal and global modes you can delete transactions from the screening file. You
should use this feature with care, since a transaction is removed permanently from the screening file and
cannot be recovered once it has been deleted.
CORRECT 6-6 September 1993
-------
AIRS User's Guide
Volume AQ3 Air Quality Data Storage
6.2.3 Exclusion Status
In any of its three modes, CORRECT can set or clear the exclusion status of a transaction. When a
transaction's exclusion status is set, that transaction is ignored by the other main data storage processes:
EDIT, SCAN, and UPDATE. Once set, the exclusion status remains set until you clear it with
CORRECT (or delete the transaction). The ability to temporarily exclude transactions from EDIT-
UPDATE processing may be useful in instances when transactions fail edit checks and the way to resolve
the problem cannot be determined immediately. When CORRECT sets a transaction's exclusion status,
it also sets the transaction's edit level to zero. (The EDIT section of this volume gives more information
about edit levels.)
CORRECT displays the current setting of a transaction's exclusion status along with the other transaction
fields. As shown in the figure below, the exclusion status appears under the left side of the box on the
screen, after the label "Excluded? (Y/N)".
September 1993 6-7 CORRECT
-------
AIRS User's Guide
Air Quality Data Storage Volume AQ3
07'01-88 : AIRS Air Quality Subsystem • CORRECT OCSCSF01
:COMMAND ===> Normal mode
DAILY Data Trans. Type: 2 j
ID#: 00008024 : Key: 37-067-0001-42401-3-88-2-02-30-..-I Edit Level: 0 j
Excluded?
-------
AIRS User's Guide
Volume AQ3 Air Quality Data Storage
6.2.4 Edit Checks
CORRECT applies level-1 edit checks to a transaction before displaying it initially and each time you
change it. If any fields of the transaction fail the edit checks, CORRECT flags each erroneous field on
the screen and displays messages describing the errors. CORRECT uses exactly the same level-1 edit
checks as the EDIT process, and displays the same error messages when fields are invalid. If a
transaction has already passed level-1 edit checks (the field EDIT-LEVEL-FLAG of the screening file
record is non-zero), CORRECT does not perform any edit checks unless you change a field of the
transaction.
Figure 6-4 shows a typical CORRECT screen displaying a transaction with errors. The error flag "«"
appears to the right of each incorrect field and the corresponding error messages are displayed at the
bottom of the screen. Sometimes several flagged fields go with a single error message. This is illustrated
in the sample screen in Figure 6-4 by the "invalid monitor-ID" message, which applies to the error flags
beside the "state-county-site" and "parameter-POC" fields, since those fields comprise the AIRS monitor-
ID. Although the screen flags every invalid field, there is room for only the first eight messages. When
you fix the first errors on the screen, CORRECT removes the corresponding error messages and displays
new messages for the remaining errors.
CORRECT displays a transaction's edit level in the box near the top of the screen. If the edit level is
zero, the transaction has failed at least one level-1 edit check; if edit level is one, the transaction has
passed level-1 edit checks. Similarly, edit levels of two and three indicate that: the transaction has passed
level-2 and level-3 edit checks. (Only the EDIT process applies level-2 and level-3 edit checks;
CORRECT does not.)
When you fix all the errors identified on a CORRECT screen, you will see the edit level change from
zero to one. Conversely, if you enter an invalid value in a field of a valid transaction, you will see the
edit level change to zero in conjunction with the appearance of an edit error message on the screen. If
a transaction has an edit level of one or higher, CORRECT does not apply edit checks to it until you
change a field. It is important to realize that if you change a field of a transaction that was already at
edit level two or three, CORRECT will lower the edit level to one (or to zero, if you specify an invalid
value). Since CORRECT does not perform level-2 or level-3 edit checks, you must use EDIT to restore
the original edit level of the changed transaction.
Due to the way CORRECT operates, it may give misleading information about edit levels zero and one.
Transactions that have edit level zero in the screening file may appear to have edit level one. When
CORRECT reads a screening file record with an edit level of zero, it applies level-1 edit checks.
CORRECT then displays the transaction and shows the results of the edit checks, including the resulting
edit level. If a transaction in the screening file is valid but has edit level zero, it will appear to have edit
level one when CORRECT displays it. This situation could arise if you use CORRECT with a screening
file that has not been processed by EDIT, for example. The situation can also occur when you look at
excluded transactions. They always have edit level zero in the screening file, but may appear to have
edit level one if they pass CORRECT's edit checks.
September 1993 6-9 CORRECT
-------
AIRS User's Guide
Air Quality Data Storage Volume AQ3
Another quirk in the way CORRECT handles edit checks pertains to global mode. As will be explained
in more detail later in this section, you can choose to display each record affected by changes made in
global mode or to perform the changes without displaying the affected records. In the former case,
CORRECT applies edit checks before displaying each changed record, just as described in the paragraphs
above. In the latter case, when changed records are not displayed, CORRECT does not perform edit
checks, and it sets the edit level to zero in each affected record. (Omitting the edit checks improves
CORRECTS performance as an online program.) Since the non-displayed transactions are not checked,
CORRECT tries to ensure that the changes you specify are valid. Before making any changes to the
transactions, CORRECT checks your specifications for how to change the records and allows you to
specify only valid values for the fields to be changed.
6.2.5 Related Transactions
If you use CORRECT to change a transaction whose edit level is two or three (thereby lowering its edit
level to one or zero), CORRECT also lowers (to one) the edit level of other transactions in the screening
file related to the one you changed. The same thing occurs if you delete or insert a transaction. This
is analogous to what LOAD does when it loads new transactions into a screening file, and the underlying
reason is the same for both LOAD and CORRECT. If the altered, deleted, or inserted transaction
belongs to a set of related records that have passed edit checks applied to the set (that is, level-2 and
level-3 checks), then any change to a member of the set may affect the properties of the set as a whole.
Therefore, CORRECT lowers the edit level of the related transactions so that the properties of the new
set will be tested again by EDIT. The new transaction set must pass level-2 and level-3 edit checks again
before it can be used to update the AIRS database.
CORRECT uses the same definition of related transactions as LOAD, which was given in Table 4-1 of
this volume and is repeated in Table 6-1 below.
CORRECT 6-10 September 1993
-------
AIRS User's Guide
Volume AQ3 Air Quality Data Storage
Table 6-1. Related Screening File Records
This table lists the relationships among screening file records used by the CORRECT process.
Transaction Type Related Records
Site (Al, A2, A3, A4, Other records with the same site-ID (state, county, site)
A5, A6, A7)
Monitor (F1,F2,F3,F4, Other records with the same monitor-ID (site-ID, parameter,
F5) POC)
SLAMS (M,N,P,R,S,T,U,V) Other SLAMS records (transaction types M - V) with the same monitor-
ID and year
Min. Detectable (Z) Other type-Z records with the same monitor-ID
Hourly Data (1) Other type-1 records with the same monitor-ID, year, and month; and
type-4 records with the same monitor-ID
Daily Data (2) Other type-2 records with the same monitor-ID, year, and month; and
type-4 records with the same monitor-ID
Composite Data (3) Other type-3 records with the same monitor-ID, year, and composite
period
Null Value (4) Other type-4 records with the same monitor-ID
Precision (8) Other type-8 records with the same monitor-ID, year, and month
Accuracy (9) Other type-9 records with the same monitor-ID, year, and month
September 1993 6-11 CORRECT
-------
Air Quality Data Storage
AIRS User's Guide
Volume AQ3
07-01-88
COMMAND «*»> ML
—•Record not Available
I COMPOSITE Data
ID*: 00008071 Key:
AIRS Air Quality Subsystem - CORRECT
OCSCSF01
Normal Mode
37-067-0038-12112-1-82-3-01-..-..-N
Trans. Type:
Edit Level:
Excluded? (t/N): N
:State-County-Site:
Parameter-fOC:
Interval Code:
Units Code:
Method Code:
Sampling Year : Global Select
Global command terminated: 12 records were read, 0 updated
•Specify the attributes of Screening file records to be selected
then press ENTER. Fields left blank do not affect selection.
For 'key' fields enter only a minimum to select just that value.
Specify both a minimum and a maximum to select a range of values.
'Key' Fields:
State-County-Site:
:: • Parameter POC:
. . ,: '.;••.'.-.-;•.. iSampling Year:
...•' .: : :; ; . -Transaction Type:
::;: .;: iSampling Month-Day-Hour:
'• . .''v .'.'. ::-::::::-:::-.'•'''•• •-•. .."Action Code:
Status Fields:
:Edit Level
-------
AIRS User's Guide
Volume AQ3 Air Quality Data Storage
6.2.6 Screen Types
CORRECT uses three general types of screens: data, specification, and error.
Data screens are for viewing, altering, or creating transactions. There is a separate format for each of
the 24 types of AIRS transactions, although all formats have some similarities. Examples of this screen
type are shown on the facing page and in Figure 6-4. These screens are used in all three CORRECT
modes of operation.
Specification screens are for choosing a selection from a menu or entering specifications for data
selection or alteration. There are only a few of these screens, which are used in global and input modes.
The global mode data selection screen, shown on the facing page, is an example of this type of screen.
Error screens are for reporting error conditions and listing the available alternatives for continuation or
termination of the CORRECT session. Examples of this screen type are shown in Figure 6-2.
The top part of all three screen types has the same format. The first line shows the date, process
identification (CORRECT), and screening file name. The second line provides a place for entering a
CORRECT command and displays the current operating mode (normal, global, or input). The next few
lines of the screen present various types of information, depending on the screen type, enclosed in a
"box". On data screens, the box contains two lines of protected fields that you cannot change. The top
line identifies the transaction type, giving its description at the left and the transaction type code at the
right. The second line includes fields for identifying the record (ID number and key) and the record's
edit level. On specification and error screens, the box contains instructions or status information. The
top line of the box also serves as a message area, where CORRECT displays informational or error
messages, usually in response to directives you enter.
September 1993 6-13 CORRECT
-------
AIRS User's Guide
Air Quality Data Storage Volume AQ3
6.2.7 Commands and PF Keys
All three CORRECT screen types have a command input field in which you can enter a directive, or
command. There are about 17 commands you can use to tell CORRECT what you want it to do. Some
commands are valid only in one or two of CORRECTS operating modes, and some are valid in all
modes. For example, the "FR" command, which tells CORRECT to go to the first record in the
screening file, is valid only in normal mode. The "QUIT" command, which terminates your AIRS
terminal session, is valid in all operating modes. Table 6-5, presented later in this section, lists all the
CORRECT commands and tells the modes in which they are valid.
CORRECT recognizes commands only if they are in upper case. In normal circumstances, CICS or
NATURAL converts everything you type to upper case before passing it on to CORRECT, so there is
no problem. If you disable that automatic case conversion, you will have to enter all CORRECT
commands in upper case yourself.
There are PF key equivalents for many CORRECT commands. In those cases, pressing a PF key is
equivalent to typing the corresponding command and pressing the ENTER key. Unlike most other AIRS
programs, CORRECT also responds to the PA1 and PA2 keys. There are no commands equivalent to
these PA keys (just as there are no PF key equivalents to some typed commands). In most cases, you
must use either a command or a PF key, but not both.
In general, using the ENTER key (without entering a command) causes CORRECT to do the next logical
thing in the current operating mode: apply edit checks to the transaction displayed on the screen, process
a menu selection, or take the default action following an error. Using a PA/PF key (or typing the
equivalent command in the command input field and pressing the ENTER key) generally causes
CORRECT to do something different: display a different transaction, switch to a different operating
mode, or end the CORRECT session, for example.
The sections below deal with operational procedures and list and explain how to use all of CORRECT's
commands, PF keys, and PA keys.
CORRECT 6-14 September 1993
-------
AIRS User's Guide
Volume AQ3 Air Quality Data Storage
6.2.8 Screening File Updating
There may be an occasion when you make several changes in a transaction displayed on your screen and
then realize that it is not the one you intended to change. By now you cannot remember the original
values of the fields you changed. Don't despair. Because of die way CORRECT updates records in the
screening file, you may be able to recover the original transaction unchanged.
When you tell CORRECT to display a transaction, it reads the corresponding screening file record and
keeps a copy of it in memory. Any changes you make on the screen are applied to the copy of the
transaction in memory. Only when you tell CORRECT to display a different transaction, change to a
different operating mode, or end the session does CORRECT determine whether to update the screening
file record. If all the fields you can change are identical in the memory copy and the file copy,
CORRECT does not rewrite the screening file record. This would be the case when you are browsing
through some transactions without applying any changes, for example. If the memory copy differs from
the file copy, CORRECT rewrites the screening file record, making it just like what you see on the
screen.
Fortunately, for those rare occasions when you need to restore a transaction's original values, you can
tell CORRECT to ignore all the changes in the memory copy of a transaction and leave the screening file
record unchanged. The various ways of accomplishing this (PA1 key, PF2/CANCEL directive, and SKIP
command) are described in the section on operating procedures.
Note that CORRECT does not consider edit level (a field you cannot change directly) in determining
whether to update a record in the screening file. CORRECT sees no difference between a screening file
record with edit level zero and a screen copy of it, having passed edit checks, with edit level one.
Therefore, CORRECT does not update the screening file. This feature allows you to browse a screening
file without changing anything, including edit level. An unfortunate side effect is that you may be misled
about the edit level of some transactions, as discussed above in the section on edit checks.
September 1993 6-15 CORRECT
-------
AIRS User's Guide
Air Quality Data Storage Volume AQ3
02/16/90 AIRS Air Quality Subsystem AAPOOOQ
User Profile COT
Password: Account Code: ASUD
Printer ID: HMTOOO 8in Number: 6132
SCREENING FILES
ANADBF01 Air Quality Screening File Read Only Not Locked
AHADBF95 Air Quality Screening File Read Only Not Locked
OCSCSF01 Air Quality Screening File Update Not Locked
Enter Profile Data (optional)
PF=end PF4=subsystem menu :pF5=terminate
02/22/90 AIRS Air Quality Subsystem AAPOOOA
Main Menu
1. Submi t Data
2. Retrieve Data - Standard Batch
3. Retrieve Data - Ad Hoc Batch
4. Browse Data - Online
: Please enter selection: 1
NEED ASSISTANCE?
CALL THE AOS HOTLINE AT 1-800-333-7909
Pr3=end(profile) PF4=subsystem menu PF5=terminate
Figure 6-6. AIRS AQS User Profile and Main Menu Screens
The AIRS AQS main menu appears after the user profile is established.
CORRECT 6-16 September 1993
-------
AIRS User's Guide
Volume AQ3 Air Quality Data Storage
6.3 CORRECT Initiation Procedures
This section tells how to initiate the CORRECT process. Normally you would use CORRECT after
checking the validity of the transactions in a screening file with EDIT. However, you can use
CORRECT at any time with a screening file that is not locked by the AIRS database administrator.
You invoke the CORRECT process by selecting the appropriate options from the menus of the AIRS Top
Level User session. See Section 3.4 of this manual for AIRS logon procedures, section 3.6 for Top
Level User procedures.
6.3.1 User Profile Screen
When you begin an AIRS terminal session, the first screen is the user profile. A sample is shown at the
top of Figure 6-6. To use CORRECT, you must enter a password and choose a screening Tile on the
user profile screen. If you do not enter a password, you will not be able to access the screening file.
Be sure you enter your AIRS password and select a screening file.
6.3.2 AIRS AQS Main Menu
The second screen of an AIRS terminal session is the AIRS AQS main menu. A sample is shown at the
bottom of Figure 6-6. To use CORRECT, choose option 1, "submit air quality data". If you forgot to
select an air quality screening file, the main menu screen displays an error message and you are instructed
to return to the user profile screen to select a screening file. There is no message if you forgot to enter
an AIRS password.
6.3.3 AQ Submit Menu
The AQ Data Storage Subsystem "submit" menu, shown in Figure 6-7, is the third screen of the AIRS
terminal session. To invoke CORRECT, select option 3 of the submit menu, "correct screening file
(online adds, changes, deletes)".
September 1993 6-17 CORRECT
-------
Air Quality Data Storage
AIRS User's Guide
Volume AQ3
05/25/89
AIRS Air Quality Subsystem
Submit
AMP002
Enter Selection: 3
PF3=end
IOAD Input Transactions to Screening file
EDIT Screening File (Batch Execution)
CORRECT Screening File (Online Adds, changes. Deletes)
NOTIFY AIRS Data Base Administrator for UPDATE
RECEIVE Messages
DELETE all Transactions from Screening File
PF4=raain menu
;PF5=terminate
08-08-87
COMMAND ===>
AIRS Air Quality Subsystem - CORRECT
OCSCSF01
Normal Mode
MINIMUM DETECTABLE value
1D#: 00000001 Key: 37-063-0052-42101-1-85-Z-08-.,
-..-M
Trans. Type: Z j
Edit Level: 3
Excluded? (Y/N): N
Action Code: M
State-County-Site: 37 063 0052
Paranieter-POC: 42101 1
Interval Code: 1
Units Code: 005
Method Code: 011
Date Range Start: 85 08 (YY-MM)
Date Range End: 85 08 (YY-MM)
Decimal Position: 2
Minimum Detectable Value: 0099
Figure 6-7. Invoking CORRECT from the AQ Submit Menu
The CORRECT screen appears after selecting submit menu option 3.
CORRECT
6-18
September 1993
-------
AIRS User's Guide
Volume AQ3 Air Quality Data Storage
6.4 CORRECT Operational Procedures
This section tells how to use CORRECT. It also explains the meaning of CORRECT error messages and
what to do about them.
6.4.1 Initial Screen
When you invoke CORRECT from the AQ submit menu, one of three possible screen types will appear.
Which one of them CORRECT displays depends on the contents of the screening file, its status, and your
access authority.
If the screening file is not locked and contains at least one transaction, and if you are authorized to update
the screening file, then CORRECT enters its normal operating mode and displays the first record of the
file (in key order) using the data screen format appropriate for the type of transaction in the record. In
spite of the restrictive tone of that statement, a data screen is what you will normally see when you
initiate CORRECT, because in normal usage you will meet all those conditions. That is, you will
normally be using CORRECT to fix errors in transactions that you have loaded into a screening file.
If any of the "normal" conditions does not apply, CORRECT will display a warning screen or an error
screen initially. (See Figure 6-2 for examples of these screen types.) A warning screen appears if your
access to the screening file is restricted, and an error screen appears if access to it is denied. Both screen
types explain the reason why access to the screening file is being restricted or denied.
When a warning screen appears, you may choose to continue the CORRECT session or to terminate it.
The screen gives instructions for taking either course. Usually, pressing the ENTER key puts you into
normal mode so you can browse the file. If the file is empty, however, pressing ENTER puts you into
input mode. (CORRECT automatically puts "INPUT" in the command input field for you.)
When an error screen appears, you must terminate the CORRECT session. The screen gives instructions
for doing that.
One set of conditions results in a warning screen followed by an error screen. If you have read-only
access authority for a screening file and that file is empty, CORRECT is not "smart" enough to recognize
the implications (that you cannot browse an empty file). It displays the warning screen to tell you that
you cannot update the file, then it displays the error screen to tell you the file is empty and you cannot
use input mode.
September 1993 6-19 CORRECT
-------
AIRS User's Guide
Air Quality Data Storage Volume AQ3
07-01-88 AIRS Air Quality Subsystem - CORRECT OCSCSF01
COMMAND «*»> delete Normal Mode
I SLAMS Methods I Frequencies • TSP Trans. Type: V I
I ID*: 00008048 Key: 37-067-0002-11101-1-85-V-..-..-..-1 Edit Level: 0 |
Excluded? (Y/N): N Action Code: 1
State-County-Site: 37 067 0002 «
:Parameter^POC: 11101 1 «
interval Code: 7 Year: 85
Codes for Sampling Methods Used: 091 .
- frequency Distribution of Observations in Value Ranges
Range: 1 23 4 5 6 78 9
* OSS: 0001 0002 0003 0004 0005 0006 0007 :0008
Exceptional Data Flag: _ « (0=No. 2»Yes. Exceptional Events in Data)
ERROR - Invalid MONITOR-ID
ERROR - Invalid EXCEPT-DATA-FLAG
07-01-88 AIRS Air Quality Subsystem - CORRECT OCSCSF01
COMMAND ===> Normal Mode
:- ••-- Record was deleted
I HOURLY Data Trans. Type: 1 |
I ID#: 00008049 Key. 37-067-0002-11101-2-81-1-10-31-07-1 Edit Level: 0 |
Excluded? (Y/N): N Action Code: I
State-County-Site: 37 067 0002
Parameter-POC: 11101 2 «
Interval Code: 5 Units Code: 001 Method Code: 091
Sampling YY-MM-DD: 81 10 31 Start Hour: 07 Decimal Position: 2
Value : Sample Validity Value Sample Validity
: dumber Value Flag Number Value Flag
1: 2: 9999 V
3: ~ 4:
.: .:.•.:::'-,•:-5:,- ~ .' • . .6:
'• •'•;:':. •:•-:•:'.:?: :•••• •' • ' 8: '
"ERROR -Invalid MONITOR-ID
Figure 6-8. Using the DELETE Command in Normal Mode
CORRECT 6-20 September 1993
-------
AIRS User's Guide
Volume AQ3 Air Quality Data Storage
6.4.2 Normal Mode
Normal mode is the default mode of operation for CORRECT. In this mode, you can access any record
in the screening file using a variety of commands and PF keys. If you have update authority, you can
change or delete records.
6.4.2.1 General
The way normal mode works is straightforward. When you enter normal mode, CORRECT displays the
"current" record and shows the results of edit checks applied to it (as described earlier in this section).
When you begin a CORRECT session, the current record is the first record in the screening file (in key
order). Using the directives discussed on the following pages, you can select a different record and make
it the current one.
If you have update authority, you can change or delete the current record. To change it, you tab to a
field and type a new value or erase the value. Each time you press the ENTER key, CORRECT
examines the fields to see if any of them have changed and applies level-1 edit checks if any have. Then
CORRECT displays the record again so you can see the effects of the changes you made. This continues
as long as you press the ENTER key. If you enter a command or use a PF key to access a different
record, change operating mode, or end the CORRECT session, CORRECT compares the transaction data
on the screen and in the screening file record. If they are different, CORRECT updates the record to
incorporate the changes you made, lowers the edit level of related records if necessary, and displays the
message "Record updated" on the next screen to let you know it changed the record. You can combine
making changes to the record and using a command or PF key into one step, if you want to. Of course,
you will not see the results of CORRECT's edit checks if you do this.
To delete the current record, type "delete" in the command field and press ENTER or a PF key. If you
press ENTER, CORRECT deletes the current record and displays the next record (in key order). If you
use a PF key, CORRECT deletes the record and then takes the action appropriate to the PF key.
CORRECT displays the message "Record deleted" on the next screen to let you know it deleted the
record. This sequence is illustrated in Figure 6-8.
CORRECT does not allow you to change or delete the current record if you do not have authority to
update the screening file. If you attempt to do so, CORRECT redisplays the unaltered record with an
error message noting that your changes were ignored. If you issued a directive to access a different
record or change mode, CORRECT displays the error message on the next screen so you will know the
changes were not accepted or the record was not deleted.
September 1993 6-21 CORRECT
-------
Air Quality Data Storage
AIRS User's Guide
Volume AQ3
07-01-88
COMMAND «
=> nun 8079
AIRS Air Quality Subsystem - CORRECT
OCSCSF01
normal Mode
SLAMS Methods I Frequencies - CO
ID#: 00008053 Key: 37-067-0003-42101-1-85-V-..-.
Trans. Type: V
.-..-1 Edit Level: 0
Excluded? (Y/K): N
State-County-Site: 37 067 0003 «
Parameter-roc: 42101 1 «
Action Code: 1
interval Code: 1
Codes for Sampling Methods Used: 011
Year: 85
Range: 1
* DBS: 0001
-Frequency Distribution of Observations in Value Ranges-
23 4 5 6 7 8
0002 0003 0004 0005 0006 0007 0008
Exceptional Data Flag: _ « (0=No, 2»Yes. Exceptional Events in Data)
ERROR - Invalid MONITOR-ID
ERROR- Invalid EXCEPT-DATA-FLAG
AIRS Air Quality Subsystem - CORRECT
OCSCSF01
Normal Mode
07-01-88
COMMAND ===> NUM 6079
-- ID '8079' not found
SLAMS Methods & Frequencies - CO Trans. Type: V
ID#: 00008053 Key: 37-067-0003-42101-1-85-V-..-..-..-I Edit Level: 0
Excluded? (Y/N): N
State-County-Site: 37 067 0003 «
Parameter-POC: 42101 1 «
Action Code: I
Interval Code: 1
Codes for Sampling Methods Used: 011
Year: 85
---••--••-•Frequency Distribution of Observations in Value Ranges
Range: 12 3 4 5 6 7 8 9
# OBS: 0001 0002 0003 0004 0005 0006 0007 0008
;Exceptional Data Flag: _ << (0=No. 2=Yes. Exceptional Events in Data)
ERROR -Invalid MONITOR-ID
ERROR - Invalid EXCEPT-DATA-FLAG
Figure 6-9. Using the NUM Command
An error message results if the specified record number does not exist.
CORRECT
6-22
September 1993
-------
AIRS User's Guide
Volume AQ3 Air Quality Data Storage
6.4.2.2 Directives for Accessing Records
CORRECT has two types of directives for accessing records (that is, for choosing which record will
become the current record). They are called "direct access" and "relative access" commands. You use
these commands by typing them in the command input field of the screen and pressing the ENTER key.
(One command has a PF key equivalent.) The record access directives are listed in Table 6-2.
The direct access commands, NUM and KEY, allow you to go to a specific record in the screening file
by giving its ID number or its AIRS key, respectively.
The syntax of the NUM and KEY commands is similar:
NUM ID-number
KEY key-value (or KEY 'key value')
The ID number used with the NUM command is the internal sequence number, or ISN, assigned to the
record by AD ABAS. It is listed as "record #" in the EDIT error report (see Section 5 of this volume)
and as "ID#" on CORRECT screens. To access a record with NUM, you must specify its ID number
exactly. (You do not have to use leading zeros.) If no record in the screening file has the ID number
you specify, CORRECT keeps the same current record and displays an error message. (This is illustrated
in Figure 6-9.) The same thing occurs if you enter a non-numeric value for ID number or omit the ID
number: CORRECT takes no action but to display an error message.
The AIRS key used with the KEY command consists of these fields of the screening file record:
Field Name Field Size
state 2
county 3
site 4
parameter 5
POC 1
year 2
transaction type 1
transaction-ID 1
filler 1
21
month (composite period) 2
day 2
hour 2
action code 1
25 characters
September 1993 6-23 CORRECT
-------
AIRS User's Guide
Air Quality Data Storage Volume AQ3
Some parts of the key are not defined for some transaction types. For example, composite data
(transaction type 3) does not have fields for day and hour. Those fields are blank in the key of the
record, and in order to specify the complete AIRS key for such a record you must include the blanks in
the value you enter. A transaction-ID and a one-character filler will replace the month field for site and
monitor transactions. (When CORRECT displays a record's key inside the box on a transaction display
screen, it replaces each blank with a period to make it easier to see how many positions are blank. You
should not use periods when you specify a key value for the KEY command, however.)
The KEY command accesses the record whose key is equal to or greater than the value you specify.
Thus, the KEY command provides more flexibility than the NUM command. KEY will always access
a record unless the key value you enter is greater than the highest key in the screening file. (In that case,
CORRECT displays an error message and retains the same current record.) Since the KEY command
does not require an exact match on the value you enter, you can specify a partial key, rather than the full
25 characters. For example, you could access the first record for a particular monitor by entering just
the monitor-ID (the state through POC fields of the key). To specify a key value with embedded blanks,
you must enclose the value in single quotes. (Without the quotes, CORRECT stops "reading" the key
value when it encounters the first blank.) The last key command entered is retained in the command line
until you exit from normal mode or until you enter another command.
CORRECT's normal mode relative access commands allow you to access a screening file record based
on its relative "position" in the file, according to its 25-character key. This is the same order as records
are listed in the EDIT error report. The relative access commands are listed and explained in Table 6-2.
Note that these commands do not have a value associated with them as the direct access commands do
(the ID number or key value). For example, to go forward three records in the screening file, you must
use the NR command three times.
If CORRECT cannot find a record that meets the criteria for one of the relative access commands, it
retains the same current record and displays an error message. For example, if the current record is the
last one in key order at edit level zero, the NL command will fail, and CORRECT will display the
message "Record not available" on the screen of the current transaction.
CORRECT 6-24 September 1993
-------
AIRS User's Guide
Volume AQ3 Air Quality Data Storage
Table 6-2. CORRECT Directives for Normal Mode (1 of 2)
Direct Access Commands
Command Description
NUM ID-number Selects the record whose record ID number (1SN)
matches the value specified in the command
KEY key-value Selects the record whose AIRS key equals or exceeds the
value specified in the command
Relative Access Commands
Command Meaning Description
FR First Record Selects the record with the lowest (first) key value
NS Next Site Selects the first record for the next site-ID (state-county-
site) in ascending key order
NM Next Monitor Selects the first record for the next monitor-ID (state-
county-site-parameter-POC) in ascending key order,
skipping any site transactions (types A-D) that may be
present
NL Next Level-0 Selects the next record in ascending key order that has
zero for edit level
NR Next Record Selects the next record in ascending key order
The PF8 key is equivalent to the NR command.
PR Previous Record Selects the previous record (in logical sequence) to the
record displayed on the screen.
PD Previous Selects records previously displayed by any of the access
Displayed Record commands.
The PF7 key is equivalent to the PR command.
September 1993 6-25 CORRECT
-------
Air Quality Data Storage
AIRS User's Guide
Volume AQ3
Table 6-2. CORRECT Directives for Normal Mode (2 of 2)
Kev
(none)
PA1
PA2
PF2
PF3
PF4
PF5
PF6
PF9
Mode Change and Other Miscellaneous Directives
Command Description
DELETE Deletes the current record from the screening file. CORRECT
obtains the next record in key order and displays it. (Wrap-
around to the first record occurs when you delete the last
record.)
(none) Terminates CORRECT and returns control to the AQ submit
menu. CORRECT does not update the current record and
ignores the command input field of the screen.
(none) Redisplays the current record as it was when you pressed
ENTER the last time. This is useful for restoring the screen
after making several erroneous changes or accidentally erasing
all fields.
CANCEL Negates any changes made to the current record since it was
accessed. CORRECT re-reads the record from the screening file
and displays it.
END Terminates CORRECT and returns control to the AQ submit
menu. CORRECT updates the current record if necessary before
terminating.
RETURN Terminates CORRECT and returns control to the AIRS AQS
main menu. CORRECT updates the current record if necessary
before terminating.
QUIT Terminates CORRECT and the AIRS terminal session.
CORRECT updates the current record if necessary before
terminating.
INPUT Invokes input mode. CORRECT updates the current record if
necessary before switching to input mode.
GLOBAL Invokes global mode. CORRECT updates the current record if
necessary before switching to global mode.
CORRECT
6-26
September 1993
-------
AIRS User's Guide
Volume AQ3 Air Quality Data Storage
6.4.2.3 Other Normal Mode Directives
CORRECT has several other normal mode directives that serve various functions, such as changing to
other operating modes or terminating CORRECT. The other directives are listed and explained in Table
6-2. There are PF key equivalents for many of the commands. Using either the command or the PF key
produces the same result.
Unlike most CORRECT directives, the DELETE and CANCEL commands can be combined with the PF
key form of other directives. For example, if you wanted to delete the current record and create a new
one to take its place, you could type "delete" in the command field and press the PF6 key to switch to
input mode. CORRECT would delete the current record, switch to input mode, and display the message
"Record deleted" on the first input mode screen to confirm that it deleted the record.
September 1993 6-27 CORRECT
-------
Air Quality Data Storage
AIRS User's Guide
Volume AQ3
•a-dd-yy AIRS Afr Quality Subsystem - CORRECT filename
COMMAND ««•> ....space for transaction type code or command.... input Node
To select one of the transaction types listed below,
enter its code in the COMMAND field and press ENTER.
To terminate input node, use the END coonand or PF3
Code Transaction Type
A1 Site data, part 1
A2 Site data, part 2
A3 Site data, part 3
A4 Site data, part 4
AS Site Location Description
A6/A7 Site Cements 1/2
F1 Monitor data, part 1
F2 Monitor data, part 2
F3 Monitor date for PM-10
F4/F5 Monitor Comments 1/2
1
2
3
Hourly data
Daily data
Composite data
Code Transaction Type
H SLAMS sunnsry - PM data
N SLAMS sunmary - PM exceedances
P SLAMS sunnary - S02
R SLAMS sunmary -CO
S SLAMS sunmary • N02
T SLAMS suonry -03
U SLAMS summary • LEAD
V : -SLAMS methods & frequencies
Z Minimum detectable value
4 Missing data reason (noil value)
8 Precision data
9 ' Accuracy data
nw-dd-vy AIRS Air Quality Subsystem - CORRECT filename
COMMAND ===> space for command input.... operating mode
I DAILY Data Trans. Types 2 j
100:12345678 Key: 12-345-6789-01234-5-67-8-90-12-34-5 Edit Level: 0
Excluded? (Y/N): N
State-County-Site:
Parameter-POC:
Interval Code:
Units Code: "
Method Code:
Action Code:
Sampling YY-MM-DD:
Sampling frequency: _
:Sample Value: ~
.Sampling Start Hour:
Decimal Position:
Validity Flag:
Figure 6-10. Selecting a Transaction Type for Input Mode
CORRECT
6-28
September 1993
-------
AIRS User's Guide
Volume AQ3 Air Quality Data Storage
6.4.3 Input Mode
Input mode may be invoked from CORRECTS normal or global modes of operation with the INPUT
command or the PF6 key. Using input mode, you can create screening file records containing any type
of AIRS input transaction. CORRECT allows you to use input mode only if you have update authority
for the screening file.
Input mode is simple to use. After you choose a transaction type, CORRECT displays a screen of the
appropriate format with all the data fields blank. You enter values into the fields and CORRECT
performs level-1 edit checks. When you end input mode or enter some other input mode directives,
CORRECT creates a screening file record containing the data you entered.
6.4.3.1 Selecting a Transaction Type
When you invoke input mode from normal or global mode, CORRECT displays the screen shown at the
top of the facing page. The screen identifies all the AIRS transaction types and gives the corresponding
codes. To select a transaction type, you enter its one- or two-character code in the command input field,
and press the ENTER key. CORRECT then displays an "empty" screen for that transaction type, on
which none of the data fields have values. This is illustrated on the facing page. If you fail to specify
a valid transaction type, CORRECT displays an error message on the selection screen and waits for you
to enter one of the codes listed on the screen. You can do that or terminate input mode with one of the
directives given later in this section.
6.4.3.2 Entering Transaction Data
Once CORRECT has displayed an empty screen for the selected transaction type, using input mode is
much like using normal mode. The data entry screens for input mode are exactly the same as the screens
used in normal mode. You type values in the fields shown on the screen, and each time you press
ENTER, CORRECT applies level-1 edit checks and shows the results on the screen. If any fields are
invalid, they are flagged with " < <" and corresponding error messages are listed at the bottom of the
screen. Although the transaction data you enter does not have to pass level-1 edit checks in order to
create a screening file record, it cannot be used to update the AIRS database until it does pass edit checks.
You can continue as long as you wish the process of entering values for fields and pressing ENTER to
validate them. CORRECT does not actually create a screening file record until you use a directive that
causes a different screen to be displayed. CORRECT puts the message "Record created" on that screen
to confirm that it created the record. If you change your mind and decide not to create a new transaction,
CORRECT has directives that allow you to do that, too. The input mode directives are explained below.
September 1993 6-29 CORRECT
-------
AIRS User's Guide
Air Quality Data Storage Volume AQ3
6.4.3.3 Input Mode Directives
Table 6-3 lists the CORRECT directives for input mode. When both a command and a PF key are listed
for a directive, you will obtain the same result using either one. If you use a directive that is not valid
in input mode, CORRECT takes no action except to display an error message on the screen.
CORRECT 6-30 September 1993
-------
AIRS User's Guide
Volume AQ3
Air Quality Data Storage
Table 6-3. CORRECT Directives for Input Mode
None of the following directives causes CORRECT to create a record in the screening file.
Key Command Description
PA1 (none) Terminates CORRECT and returns control to the AQ submit menu.
CORRECT does not create a screening file record and ignores the
command input field of the screen.
PA2 (none) Redisplays the current record as it was when you pressed ENTER the
last time. This is useful for restoring the screen after making several
erroneous changes or accidentally erasing all fields.
PF2 CANCEL If used on the transaction type selection screen, this directive terminates
input mode and invokes normal mode. If used on the data entry screen,
any values entered are ignored, a screening record is not created, and the
transaction type selection screen is displayed.
All of the following directives cause CORRECT to create a record in the screening file if they are used
on a data entry screen.
PF3
PF4
PF5
PF6
RETURN
QUIT
INPUT
PF7
PF8
PF9
END Ends input mode and invokes normal mode, If CORRECT creates a
screening record, it displays the newly created record in normal mode.
Terminates CORRECT and returns control to the AIRS AQS main menu.
Terminates CORRECT and the AIRS terminal session.
Re-invokes input mode. The transaction type selection screen is
displayed.
SR Re-invokes input mode. The same input screen and transaction type used
for the prior screen are displayed.
NR Facilitates creation of multiple transactions of the same type. When you
use this directive, CORRECT creates a screening record from the values
on the data entry screen, then displays the same screen again, retaining
the values you entered in key fields and some other fields. Transaction
type changes to the next type in the sequence Al, A2, A3, A4, A5, A6,
A7, Fl, F2, F3, F4, F5
GLOBAL Invokes global mode, ending input mode.
September 1993
6-31
CORRECT
-------
AIRS User's Guide
Air Quality Data Storage Volume AQ3
08-12-87 AIRS Air Quality Subsystem - CORRECT OCSCSF03
COMMAND «=«> Global Select
Specify the attributes of Screening File records to be selected
then press ENTER. Fields left blank do not effect selection.
For 'key' fields enter only a minimum to select just that value.
Specify both a minimum and a maximum to select a range of values.
Minimum Maximum
'Key' Fields:
State-County-Site: ;
Parameter-POC: "
Sampling Year: ~
Transaction Type: P V
Sampling Month-Day-Hour: __..;,
Action Code: _
Status Fields:
Edit Level (s): 0 1 2 Excluded?
Data Fields:
Interval Code: Method Code:
Decimal Position: Units Code:
Figure 6-11. The Global Select Screen
CORRECT 6-32 September 1993
-------
AIRS User's Guide
Volume AQ3 Air Quality Data Storage
6.4.4 Global Mode
Global mode may be invoked from CORRECTS normal or input modes of operation with the GLOBAL
command or the PF9 key. Using global mode you can specify criteria to select a subset of screening file
records. Then you can view the selected records and change some of them, or apply changes to all of
them without viewing them. Even if you do not have update authority, you can use global mode to look
at a selected subset of records.
Although global mode is the most complicated of CORRECTS three operational modes, it is not really
difficult to use. It allows you to do some things easily and quickly that would take longer and be more
difficult to do in normal mode. A global "command" consists of three phases. First you specify selection
criteria, then CORRECT looks for records that meet the criteria and tells you how many it found.
Second, if you have update authority, you specify what changes to apply to each selected record and
whether you want to see each one. Third, CORRECT applies the changes to the records and displays
them if you requested it to do so. The following subsections describe each phase in more detail.
6.4.4.1 Specifying Selection Criteria
When you invoke global mode from normal or input mode, CORRECT displays the "global select" screen
shown in Figure 6-11. The values you enter on this screen determine which records of the screening file
will be involved in the global mode processing. There are brief instructions in the box near the top of
the screen. Under the box are three groups of fields in which you can enter selection criteria: key fields,
status fields, and data fields. You must enter a value in at least one field.
The key fields comprise the key of a screening file record, as discussed earlier in this section. There
are two columns of key fields on the screen, labeled minimum and maximum. You can enter values in
both the minimum and the maximum columns to define a range of values to be selected, or you can
specify a single value to be selected by entering it just in the minimum column. If you enter values only
in the maximum column, CORRECT interprets that as the high limit of a range that includes all keys less
than or equal to the values you enter. Leaving a field blank in both columns tells CORRECT to select
all values of that field. Several of the key fields have hierarchial relationships that you must respect when
you specify selection criteria. To use the site field you must also use county, and to use county you must
also use state. On the other hand, you can use state alone, or use state and county without using site.
Similar relationships hold for parameter and POC, and for year, month, day, and hour.
To minimize the number of records CORRECT has to read to process your selection criteria, you should
enter values for site-ID (state-county-site) or monitor-ID (state through POC) whenever possible. Doing
so will reduce the time and cost of performing a global "command". (See the next subsection for more
details.)
September 1993 6-33 CORRECT
-------
AIRS User's Guide
Air Quality Data Storage Volume AQ3
The status fields, edit level and excluded, pertain to the status of screening records rather than the
transaction data they contain. You may enter as many as four values for edit level; acceptable values are
0, 1,2, 3, and 9. You may enter either "Y" or "N" for exclusion status. CORRECT selects screening
records that have an edit level and exclusion status that match any of the values you enter. If you do not
specify an edit level or an exclusion status, CORRECT does not use that field as a criterion for selecting
screening records.
The data fields work like the status fields, but they pertain to values in the transaction data. You may
enter as many as four values for each of the four data fields: interval code, method code, units code, and
decimal position. CORRECT selects screening records that have any of the values you specify for each
of die fields. If you do not specify a value for a field, CORRECT does not use that field as criterion for
selecting screening records. For example, you might enter "7" for interval code, enter "1" and "2" for
decimal position, and leave blank the method and units fields. In that case, CORRECT would select
screening records having interval code 7 and decimal position indicators of either 1 or 2. It would
disregard the method code and units code in the screening records, basing the selection only on interval
code and decimal position.
CORRECT checks the values you enter as global mode selection criteria to ensure that they are
reasonable. If you enter invalid criteria CORRECT flags each invalid field or group of fields with
" < <" and displays error messages for the first two errors in the bottom line of the screen. You must
fix the errors before you can proceed with the global "command".
6.4.4.2 How CORRECT Selects Records
The key and status fields on the global select screen are indexed by AD ABAS, the database management
system of AIRS. (In ADABAS terminology, these fields are "descriptors" and their values are stored in
the "associator".) Because ADABAS maintains an index of these fields, CORRECT can find out which
values are present in the screening file without having to read the records. The "data" fields on the
global select screen are not indexed, and CORRECT must read a screening record to determine whether
it satisfies your selection criteria for those fields.
CORRECT uses a two-step process to select screening records that meet your selection criteria. In the
first step, CORRECT uses the indexed (key and status) fields to determine approximately how many
records qualify. In the second step, CORRECT reads each screening record qualified in the first step
and rigorously applies the complete set of selection criteria to each one. Any records that fail the second
round of selection are discarded; they are not displayed or changed by the global command.
CORRECT 6-34 September 1993
-------
AIRS User's Guide
Volume AQ3 Air Quality Data Storage
The results of the first selection step are usually approximate because of the way AD ABAS indexes the
key fields. The index has an entry for each unique value of the entire 25-character screening record key,
but not for each of the separate fields shown on the global select screen. To select records using the
index, CORRECT must construct a range of 25-character keys that includes all possible values implied
by the key values you enter. To do this, CORRECT uses the following procedure:
(1) If a key field in the maximum column is blank, copy into it the value from the corresponding
field in the minimum column.
(2) Replace each blank in the maximum column with "9".
(3) Use the unaltered minimum column and the revised maximum column to define the low and high
ends of an inclusive range of 25-character keys to be selected.
As you can see, this method of selecting records is effective only if you specify values for fields at the
beginning of the key: state, county, and site. If you leave state blank, for example, then CORRECT must
select all possible values (blanks through "99"). That effectively negates any selection based on key,
since all possible keys in the screening file fall within that range. (The other indexed fields, edit level
and exclusion status, do not share this imprecision, since CORRECT can look for specific values in the
index rather than ranges.)
Having applied approximate selection criteria using the indexed fields, CORRECT reports to you the
number of screening records that qualified. This is the maximum number of records the global command
will affect. If the number seems reasonable, you can continue the command. If the number is grossly
different than you expected, you can abort the global command and try different selection criteria. Of
course, if the number qualified is zero, you have no choice; you must either specify different criteria or
end global mode. CORRECT displays a message on the global select screen to tell you nothing was
selected.
If you have update authority, CORRECT tells you the number of records qualified by the indexed
selection step in a message displayed on the "global change" screen, described in the next subsection.
If you do not have update authority, CORRECT includes the message
Maximum # records selected: number
on the screen when it displays the first selected record.
September 1993 6-35 CORRECT
-------
AIRS User's Guide
Air Quality Data Storage Volume AQ3
07-19-89 AIRS Air QualitySubsystem - CORRECT OCSCSF03
/COMMAND «=>•;: Global Change
102 records will be read to process your selection criteria. 1
Specify the global changes you want made in each of the selected records,
then press ENTER. You nay cancel global mode with the END command (PF3). j
Display each record? (T/N): N : DELETE each record? (Y/N): N
State-County-Site:
Parameter-POC:
Set Sampling Year: ~ To
'these •:«=> Transaction Type: _ <=== these
•fields/: Month-Day-Hour: ~ values
Action Code:
. ; Interval Code:
.".:"•"•:::: Method Code: ~
Units Code:
Decimal Position:
.:'.:! Sampling Frequency:
Exclusion Status: Y (Y/N)
Figure 6-12. The Global Change Screen
CORRECT 6-36 September 1993
-------
AIRS User's Guide
Volume AQ3 Air Quality Data Storage
6.4.4.3 Specifying Global Changes
If you have update authority for the screening file, CORRECT displays the "global change" screen after
completing the first step of screening record selection described in the previous subsection. An example
of the global change screen is shown on the facing page. The screen has three functions:
It tells you how many records were selected using the key and status fields.
It allows you to choose whether to view each selected record.
It allows you to specify changes (or deletion) for each selected record.
Inside the box near the top of the screen, CORRECT shows the number of records qualified by the first
step of the global selection process, and lists brief instructions for using the screen. As explained in the
previous subsection, the global command may affect fewer records than the number listed on the screen,
since some of them may not satisfy the complete set of selection criteria.
Just below the box are two questions you must answer with "Y" (yes) or "N" (no). The first question
asks if you want CORRECT to display each record it selects, and the default answer is yes. If you
change that to no, CORRECT changes or 'deletes selected records but does not display them. In the
following paragraphs this is referred to as "no-show mode".
The second question asks if you want CORRECT to delete each record it selects, and the default answer
is no. If you change the answer to yes, CORRECT will delete each of the selected records (in no-show
mode) or put "DELETE" in the command input field of each screen when it displays selected records (in
show mode). In show mode, you can override the DELETE command for a particular record by erasing
it from the command input field.
The middle part of the global change screen displays the "global change" fields, in which you can enter
values. These fields tell CORRECT how you want to change selected records. CORRECT stores the
values you enter in the corresponding fields of screening records it selects. Any fields you leave blank
are ignored; they do not affect the selected records. If you do not want to change records, you can leave
all the global change fields blank. Note that there is a global change field for transaction type. Using
global mode is the only way you can change the transaction type of screening records.
When you press the ENTER key, CORRECT checks your global change specifications. To ensure that
you do not introduce errors into your transaction data, CORRECT allows onJy valid values in the global
change fields. It applies a subset of level-1 edit checks to the values you enter. If a field or group of
fields fails the edit checks, CORRECT displays the error indicator " < <" beside it and lists an error
message at the bottom of the screen. As many as six error messages can be displayed there. You can
proceed with the global command only after correcting all the errors in the values.
September 1993 6-37 CORRECT
-------
AIRS User's Guide
Air Quality Data Storage Volume AQ3
You should specify a reasonable combination of the display, delete, and change options on the global
change screen. For example, it does not make sense to both delete and change records, particularly if
you also choose not to display them. (In this case, CORRECT simply deletes the records and ignores
the changes specified.) One combination of options is not allowed. If you specify that records should
not be displayed, deleted, or changed (a "do nothing" command), CORRECT displays an error message
and you must change one of the options to proceed. The default combination (view the records, do not
delete them, do not make any changes) is suitable for browsing records. CORRECT uses this
combination of options if you do not have update authority for the screening file. If you do have update
authority, you can delete or alter a record as you wish, once global mode has selected and displayed it.
CORRECT 6-38 September 1993
-------
AIRS User's Guide
Volume AQ3 Air Quality Data Storage
07-19-89 AIRS Air duality Subsystem - CORRECT OCSCSF03
11:27:32 Global Mode
| : ..GLOBAL COMMAND STATUS |
•'•'•."•';. Your global command is being executed.
Records processed: 211 Elapsed time: 0:15
.Of the 258 candidate records for this command,
129 have been processed so far,
35 met selection criteria and were updated.
Also, 62 related records have been checked and
81 have had edit level lowered to 1.
Figure 6-13. The Global Status Screen
September 1993 6-39 CORRECT
-------
AIRS User's Guide
Air Quality Data Storage Volume AQ3
6.4.4.4 How CORRECT Processes Records In Global Mode
When you have specified valid global change options, CORRECT begins the second stage of record
selection and record processing. (If you do not have update authority, CORRECT chooses the global
change options for you.)
CORRECT reads each of the records that were qualified using the indexed key and status fields in the
first stage of selection. After reading a record, CORRECT applies your complete set of selection criteria.
It compares the values of each field of the global select screen with the corresponding field in the record
to see if they are compatible. If any one field fails the test, CORRECT rejects the record and reads the
next one.
You should be aware that in global mode, CORRECT reads the records in order of their ID numbers,
rather than in key order as in normal mode. The ID-number order is the normal way AD ABAS makes
the qualified records available to CORRECT, and often (but not always) ID-number order corresponds
with key order. (The central database administrator of the computer center strongly discourages the kind
of sorting that CORRECT would need to do to put the qualified records in key order, and that is why
CORRECT does not do it.)
What happens after CORRECT selects one of the qualified records depends on the global change options
you specified. If you chose not to display records, CORRECT either deletes the record or stores in the
record the values you entered in the global change fields, sets the record's edit level to zero, and rewrites
it. (CORRECT does not apply edit checks to the changed record.) Then CORRECT checks to see if
there are any other records in the screening file related to the one deleted or altered. CORRECT updates
each one that has an edit level higher than one by lowering its edit level to one. (See the "Related
Transactions" section above for more details on related records.)
The process of selecting and deleting or changing records continues until all the selected and related
records have been processed. If numerous records are involved, CORRECT interrupts itself periodically
and displays the "global status" screen shown in Figure 6-13. The status screen shows how many records
CORRECT has processed and how much time (minutes:seconds) has elapsed since the global command
processing began. You do not have to respond to the status screen by pressing any key on your terminal.
In fact, CORRECT will not accept any input while the status screen is displayed. The information on
the screen is updated each time CORRECT interrupts itself, which generally occurs every two to eight
seconds.
The global status screen serves two purposes. First, it lets you know that something is being
accomplished as you wait for the command to finish. You can track the progress of the global command
by noting the number of records that have been read and updated. Second, the act of displaying the status
screen breaks up CORRECT's global processing into segments short enough to meet computer center
standards. Each time CORRECT displays the status screen, other users get a chance to use the ADABAS
and CICS facilities that CORRECT was using.
CORRECT 6-40 September 1993
-------
AIRS User's Guide
Volume AQ3 Air Quality Data Storage
If you chose the default option of displaying records in global mode, the method of selecting a record and
applying global changes is exactly the same as described above. After that, the procedure is somewhat
different. First, CORRECT compares the "changed" record with the original and sets the edit level to
zero if there are any differences. Then, if the record's edit level is zero (either because of changes or
because it was already zero) CORRECT applies level-1 edit checks and sets the edit level to one if there
are no errors. Finally, CORRECT displays the record using the same screen format as normal mode.
If you chose the delete option, CORRECT puts "DELETE" in the command input field of the screen.
You can override the default deletion of a particular record by erasing the DELETE command.
When a selected record has been displayed, global mode is very similar to normal mode. You are free
to change the fields displayed on the screen if you wish. Each time you press the ENTER key,
CORRECT applies level-1 edit checks to the transaction data and displays the results. You must enter
a command or use a PF key to make CORRECT do something else, such its retrieve the next selected
record. Table 6-4 lists the global mode directives.
Which directive you use determines what CORRECT does next. In most cases, CORRECT rewrites the
screening record (if it has been changed) and lowers the edit level of related records. If you use the NR,
DELETE, or SKIP command, CORRECT finds the next record that meets selection criteria, applies
global changes, and displays it. CORRECT may display the global status screen if many screening
records must be read to find the next one that meets selection criteria. This process is repeated until all
the qualified records have been read or you terminate the global command. Note that you can use the
NOSHOW command to switch from the mode in which CORRECT displays selected records to the mode
in which records are not displayed. This allows you to see the effect of your global change specifications
on a few records and verify that they are correct, then switch modes and process the rest of the records
without having to view each one. (CORRECT does not allow you to use the NOSHOW command if you
did not specify global changes.)
If you do not have update authority, the global mode processing is essentially the same as described
above, except that you cannot change or delete the selected screening records.
6.4.4.5 The End of a Global Command
When CORRECT has processed all the screening records selected for a particular global command, it
displays the global select screen again. The same is true if you terminate a global command with the
CANCEL (PF2) or GLOBAL (PF9) directives. Global mode remains in effect, and you can begin
another global command if you wish.
When a global command ends normally or when you terminate it with a directive, CORRECT displays
a message summarizing what was done. If you used a directive to end the command, the message says
"global command terminated". Otherwise, the message says "global command completed". In both
cases, the remainder of the message lists the number of records that were read and the number that were
updated.
September 1993 6-41 CORRECT
-------
Air Quality Data Storage
AIRS User's Guide
Volume AQ3
Table 6-4. CORRECT Directives for Global Mode (1 of 2)
None of the following directives causes CORRECT to update the displayed record of the screening file.
Key Command Description
(none)
PA1
PA2
PF2
(none)
CANCEL
(none)
SKIP
Terminates CORRECT and returns control to the AQ submit menu.
CORRECT does not update the screening record and ignores the
command input field of the screen.
Redisplays the current screen as it was when you pressed ENTER the
last time. This is useful for restoring the screen after making several
erroneous changes or accidentally erasing all fields.
If used on the global select screen, this directive terminates global mode
and invokes normal mode. If used on the global change screen or a
transaction display screen, this directive aborts the global command;
global mode remains active and the global select screen is displayed.
"Skips" (does not do) updating of the current record and obtains the next
selected record. If no global changes were specified, this is equivalent
to the NR command (see below).
All of the following directives cause CORRECT to update the displayed record of the screening file.
PF3
PF4
PF5
PF6
PF7
PF8
PF9
END Ends global mode and invokes normal mode.
RETURN Terminates CORRECT and returns control to the AIRS AQS main menu.
QUIT Terminates CORRECT and the AIRS terminal session.
INPUT Invokes input mode.
PR Previous record: When used on a transaction display screen, CORRECT
updates the current record (if necessary), obtains the preceding selected
record, and displays the previous record.
NR Next record: When used on a transaction display screen, CORRECT
updates the current record (if necessary), obtains the next selected
record, and displays it. When used on global select or global change
screen, this directive is equivalent to pressing ENTER.
GLOBAL Re-invokes global mode. The global select screen is displayed.
CORRECT
6-42
September 1993
-------
AIRS User's Guide
Volume AQ3 Air Quality Data Storage
Table 6-4. CORRECT Directives for Global Mode (2 of 2)
(none) DELETE Deletes the displayed record from the screening file and obtains the next
selected record.
(none) NOSHOW Switches to the global mode in which selected records are not displayed.
The current record is updated normally, then all remaining selected
records are processed as if you had chosen not to display records when
you entered specifications on the global change screen. This command
is valid only if you specified deletion or changes on the global change
screen.
September 1993 6-43 CORRECT
-------
AIRS User's Guide
Air Quality Data Storage Volume AQ3
6.4.5 Summary of CORRECT Directives
This subsection presents a summary of the numerous CORRECT directives (commands and PF keys)
described in preceding parts of this section. It also gives an overview of the logical relationships among
CORRECT's operating modes.
Table 6-5 lists every CORRECT directive and indicates the circumstances in which it is valid. The table
tells you only when you can use a directive; refer to the appropriate part of the operating instructions to
find out what it does.
Figure 6-14 illustrates the hierarchical relationships among CORRECT's operating modes and sub-modes.
The figure also shows which PF keys cause transitions from one mode to another. The corresponding
commands cause the same mode changes, of course.
CORRECT 6-44 September 1993
-------
AIRS User's Guide
Volume AQ3
Key
PA1
PA2
PF2
PF3
PF4
PF5
PF6
PF7
PF8
PF9
—
—
—
—
~
—
—
—
—
Table 6-5. Sun
Normal
Command Mode
—
—
CANCEL
END
RETURN
QUIT
INPUT
PR
NR
GLOBAL
KEY
NUM
FR
NL
NM
NS
SR
PD
DELETE
yes
yes
(yes)
yes
yes
yes
(yes)
(yes)
yes
yes
yes
yes
yes
yes
yes
yes
(yes)
yes
(yes)
nmary or C
G
Select
yes
yes
yes
yes
yes
yes
(yes)
no
yes
yes
no
no
' no
no
no
no
no
no
no
ORRECT
ilobal Mcx
Change
(yes)
(yes)
(yes)
(yes)
(yes)
(yes)
(yes)
(yes)
(yes)
(yes)
no
no
no
no
no
no
no
no
no
Directives (1
ie
Display
yes
yes
yes
yes
yes
yes
(yes)
no
yes
yes
no
no
no
no
no
no
no
no
(yes)
Air Quality Data Storage
of 2)
Input Mode
Select Input
(yes)
(yes)
(yes)
(yes)
(yes)
(yes)
(yes)
no
(yes)
(yes)
no
no
no
no
no
no
no
no
no
(yes)
(yes)
(yes)
(yes)
(yes)
(yes)
(yes)
(yes)
(yes)
(yes)
no
no
no
no
no
no
no
no
no
September 1993
6-45
CORRECT
-------
AIRS User's Guide
Air Quality Data Storage Volume AQ3 •
Table 6-5. Summary of CORRECT Directives (2 of 2)
SKIP no no no yes no no
NOSHOW no no no (yes) no no
"Yes" in the table means a directive is valid for the indicated mode of operation.
"(Yes)" means the directive is valid only if you have update authority.
"No" means the directive is not valid for the indicated mode.
CORRECT 6-46 September 1993
-------
AIRS User's Guide
Volume AQ3
Air Quality Data Storage
AQ Submit
Menu
CAMP002D
Figure 6-14. PF Keys for Switching Among CORRECT Modes of Operation
The arrows show transfers between modes caused by the indicated PF keys. Not shown are the PA 1,
PF4, and PF5 keys, which have the same effect (termination of CORRECT) regardless of where in the
structure they are used.
September 1993
6-47
CORRECT
-------
Air Quality Data Storage
AIRS User's Guide
Volume AQ3
08-08-87
COMMAND ===>
AIRS Air Quality Subsystem -CORRECT
OCSCSF03
ERROR
> > > AIRS ERR 0 R < < <
An error has occurred from which recovery is not possible.
You must terminate your AIRS session.
Please record the information shown below and contact the AIRS ADBA.
Error type ==> ADABAS Error Number ==> 9
frosram Name ===> AMP060T1 line Number ===> 0
Other Information
An AOABAS error occurred during Ieve 1-1 edit checks.
fMT-BUF= SRCH-BUF=
The AOABAS Control Block follows...
.SI. : .0032.0009.00000000.00000000.00000000.OMO.0764.0040.0040J
0000. .v ..8015.**** . .. .00000003.ASWD]
Press ENTER to terminate.
Figure 6-15. The AIRS Error Screen
This screen results from unanticipated or catastrophic errors.
CORRECT
6-48
September 1993
-------
AIRS User's Guide
Volume AQ3 Air Quality Data Storage
6.4.6 Error Handling
Preceding parts of this section have mentioned error screens and error messages CORRECT uses. This
subsection summarizes CORRECTS error handling procedures and lists its error messages.
CORRECT displays four kinds of error information. The first kind, which is the most benign, results
from level-1 edit checks. The error information takes the form of error flags ("<<") beside fields and
messages at the bottom of the screen. These messages are for your information only, and have no effect
on the way you use CORRECT. Volume AQ2 of the AIRS User's Guide lists all the error messages
resulting from level-1 edit checks and describes what they mean.
The second kind of error information results from operational mistakes you may make, such as using an
invalid directive. These error messages appear in the top "edge" of the box on CORRECT screens.
Table 6-6 lists and explains the operational error messages.
The third kind of error information is presented on CORRECT's warning and error screens, which
generally report a condition that restricts or prohibits your usage of CORRECT. Both of these error
types are associated primarily with the status of a screening file or the AIRS transaction data in it.
CORRECT's warning and error screens are self explanatory; they describe the error condition and tell
you what you can do to continue or terminate your CORRECT session. Samples of these screens are
shown in Figure 6-2.
The fourth kind of error, which is the most disruptive with respect to using CORRECT, is the
unanticipated or "catastrophic" error. There are many possible error conditions in a system as complex
as AIRS, and it is not feasible for CORRECT to "understand" all of them. When an error condition
arises that CORRECT is not programmed to handle, it displays the error screen shown in Figure 6-15.
When this happens, you must end your AIRS terminal session. Typically, the "AIRS error screen" is
displayed when ADABAS reports to CORRECT that it could not do something CORRECT requested,
such as reading a record. Unfortunately, inactivity of your terminal is another common cause of the
AIRS error screen. If you are interrupted during a CORRECT session and do not do anything on your
terminal for five to ten minutes, the AD ABAS/NATURAL system "times out" and returns error code 9
to CORRECT at the next activity. CORRECT cannot deal with this error, so it displays the error screen.
If the AIRS error screen appears during your CORRECT session, look at the fields labeled error type
and error number. If they are "ADABAS" and "9", the cause is the time-out described above. If the
error number or error type has any other value, record all the information on the screen, press ENTER,
and contact the AIRS database administrator.
September 1993 6-49 CORRECT
-------
AIRS User's Guide
Air Quality Data Storage Volume AQ3
Table 6-6. CORRECT Operational Error Messages (1 of 4)
'NOSHOW command invalid - ignored
This message occurs in global mode if you attempt to switch to "no-show" mode when you are not
changing or deleting selected records. This condition could arise if you do not have update
authority or if you simply did not specify changes or deletion. If you want to continue the global
command, you must view each selected record. You can terminate the global command if you
wish, using a directive such as CANCEL (PF2).
'value1 is not a valid ID#
This message occurs in normal mode if you specify a non-numeric value for a screening record ID
number in the NUM command. Enter a numeric record ID number or erase the command.
At least one field must be specified
This message occurs if you press ENTER without entering any selection criteria on the global select
screen. You must specify a value in at least one field.
Command and PF key are incompatible
This message occurs on any screen if you enter a command and press a conflicting PF key. Since
CORRECT does not know which one should be given precedence, it requires that you choose one
of them. This situation is most likely to arise after an error message. For example, if you were
using the NL command to find each record with edit level zero, CORRECT would give a "record
not available" message after the last one, and leave the NL command on the screen. If you then
pressed PF3 to end the CORRECT session, CORRECT would give this message. You would have
to erase the NL command before using the PF3 key to end the session.
ID# 'number* not found
This message occurs in normal mode if no record in the screening file has the ID number you
specified in a NUM command.
Incomplete command
This message occurs in normal mode if you enter the NUM command without specifying a record
ID number or if you enter the KEY command without specifying a record key.
Invalid command
This message occurs in any operating mode if you enter something in the command input field that
CORRECT does not recognize as a command. All the valid commands are listed in Table 6-5.
CORRECT 6-50 September 1993
-------
AIRS User's Guide
Volume AQ3 Air Quality Data Storage
Table 6-6. CORRECT Operational Error Messages (2 of 4)
Invalid command for this mode
This message occurs in any operating mode if you enter a CORRECT command that is not valid
in that operating mode.
Invalid criteria - change specifications or END
This message is displayed on the global select screen if you enter invalid selection criteria. Either
correct the mistake(s) in the selection criteria (marked with " < <") or use the END (PF3) directive
to terminate global mode.
Invalid key (key name)
This message occurs when you use a PF key or PA key that is not defined for CORRECT.
Invalid key (key name) for this mode
This message occurs when you use a PF key that is not valid in the current CORRECT operating
mode. (At the present time, all the PF keys defined for CORRECT are valid in all modes, so this
error will not occur.)
Invalid selection - respecify or END
This message occurs on the input mode transaction type menu screen if you do not enter a valid
transaction type code. You must enter the correct value or use the END (PF3) directive to
terminate input mode.
Invalid specification - change or END
This message occurs on the global change screen if you enter invalid specifications for record
display, deletion, or change. Either correct the mistakes (marked with " < <") or terminate the
global command with a directive such as END (PF3).
KEY 'key value' not found
This message occurs in normal mode if no record in the screening file has a key equal to or greater
than the value you specified in a KEY command. Use a different key value or erase the KEY
command.
No changes requested - change specifications or END ,
This message occurs on the global change screen if you specify a "do nothing" command: do not
display selected records, do not delete them, and do not change them. You must change your
specifications or terminate the global command with a directive such as END (PF3).
September 1993 6-51 CORRECT
-------
AIRS User's Guide
Air Quality Data Storage Volume AQ3
Table 6-6. CORRECT Operational Error Messages (3 of 4)
Nothing selected - change specifications or END
This message occurs on the global select screen when the selection criteria you entered did not
qualify any records in the screening file. You may enter different selection criteria and press
ENTER, or terminate the global command with a directive such as END (PF3).
Record not available
This message occurs in normal mode when CORRECT reaches the last record of the screening file
(in key order) without finding the record you requested with one of the relative access commands:
NR, NS, NM, or ML. This is CORRECT's way of saying it came to the "end of file". Use a
different record access directive, such as FR or KEY; or terminate your CORRECT session with
the END command.
Record not created
This message occurs in (or following) input mode to inform you that CORRECT did not create a
new screening record. This happens when you do not enter any values on the "empty" data entry
screen or if you use the CANCEL (PF2) directive after entering values.
Updating not allowed - changes ignored
This message occurs in normal or global mode when you do not have update authority for the
screening file and attempt to change a displayed transaction. CORRECT ignores the change(s) you
entered and restores the record to its original state.
Updating not allowed - command ignored
This message occurs in normal or global mode when you do not have update authority for the
screening file and attempt to delete a displayed transaction. CORRECT ignores the DELETE
command and retains the record in the screening file. In normal mode, CORRECT redisplays the
same record, and you must erase the DELETE command to continue. In global mode, CORRECT
erases the DELETE command, goes on to the next selected record, and displays this message on
its screen.
You cannot use input mode - update authority is required
This message occurs in normal or global mode when you do not have update authority for the
screening file and attempt to use CORRECT's input mode.
Record not available - Now at start of file
This message occurs in normal mode when CORRECT reaches the first record of the screening file
(in key order). This is CORRECT's way of saying it came to the "top of file".
Record not available - Now at end of file
This message occurs in normal mode when CORRECT reaches the last record in the screening file
(in key order). This is CORRECT's way of saying it came to the "end of file".
CORRECT 6-52 September 1993
-------
AIRS User's Guide
Volume AQ3 Air Quality Data Storage
Table 6-6. CORRECT Operational Error Messages (4 of 4)
Record not available - Now at end of PD records
This message occurs in normal mode when CORRECT reaches the first record displayed of the
records which had been previously displyed using different access commands.
Record not available - Max records scrolled
This message occurs in normal or global or input mode, when the number of records displayed is
greater than 100.
Record not available - Now at start of selected records
This message occurs in global mode when CORRECT reaches the first record among the selected
records, and the user presses PF7 or enters the PR command.
Record not available - Now at start of newly created records
This message occurs in input mode when CORRECT reaches the first record created and the user
presses PF7 or enters the PR command.
September 1993 6-53 CORRECT
-------
AIRS User's Guide
Air Quality Data Storage Volume AQ3
6.5 CORRECT Follow-Up Procedures
The primary purpose of CORRECT is to fix the errors in transaction data that EDIT has identified.
Therefore, after fixing errors, you should run EDIT again to verify that the errors are corrected and to
set the edit level of the transactions to 3 so they can be used to update the AIRS database.
CORRECT 6-54 September 1993
-------
AIRS User's Guide
Volume AQ3 Air Quality Data Storage
6.6 Restrictions, Limitations, and Warnings
Although CORRECT can do many things, there are some limitations:
1) In normal mode, there are no relative access commands for moving backward (toward the beginning
of the file). In order to return to a screening record you have gone past, you must go back to the
beginning of the file and move forward again until you reach it, or you must use one of the direct access
commands, NUM or KEY. The omission of backward movement commands, such as "previous record"
or "previous site", was a system design decision based on the assumption that too much processing would
be required to execute such commands.
2) CORRECT does not properly handle a "time out" as a special error condition, and terminates the
AIRS session when it occurs. A time out happens when CORRECT reads a record from the screening
file, then neither rewrites that record nor reads another one within a period of about ten minutes. The
most common cause of a time out is simply inactivity of your terminal, which could happen if you have
to answer a phone call or get a cup of coffee. But a time out could also occur while you are using your
terminal if the time you spend working on one record exceeds the per-record time limit set by AD ABAS.
You can avoid a time out error (in normal mode, at least) by periodically issuing a NUM command for
the current record. That causes CORRECT to write then re-read the same record.
3) There is no way to switch from one screening file to another at the level of CORRECT in the AIRS
hierarchy of programs. (See Figure 3-9.) This situation is unhandy if you need to use CORRECT with
multiple screening files, since you must return to the AIRS user profile screen to select a different file.
4) When a CORRECT screen shows edit level-1 for a displayed transaction, there is no way to tell
(in normal mode) whether the edit level in the screening file record is really 1 or 0. If the record has
edit level 0 but passes all level-1 edit checks, CORRECT will show the edit level as 1.
September 1993 6-55 CORRECT
-------
AIRS User's Guide
Volume AQ3 Air Quality Data Storage
7.0 The NOTIFY Process
NOTIFY is logically the last user process of the AQ Data Storage Subsystem of AIRS. This section
describes what NOTIFY does and how to use it.
7.1 Overview
The purpose of the NOTIFY process is to allow you to inform the AIRS database administrator that your
screening file is ready to be used to update the AIRS database. You can also use NOTIFY to rescind a
prior notification. NOTIFY informs the database administrator of your request to set or rescind a
screening file's ready-for-update status.
The data flow diagram in Figure 7-1 illustrates NOTIFY's operating environment. NOTIFY is invoked
directly from the submit menu of the Air Quality Subsystem. It executes online and displays the
NOTIFY menu screen or an error screen. NOTIFY reads information from the Table file about your
screening file and updates that information according to your selection on the menu screen. NOTIFY
writes a message for the AIRS database administrator and a message for the user in the Table File.
Normally, NOTIFY reverts control back to the Air Quality submit menu when it has finished its
processing. Instead, you may invoke the AIRS AQS main menu with the PF4 key or terminate your
AIRS terminal session with the PF5 key. NOTIFY performs the action you select from the menu before
transferring control to another function or terminating your AIRS terminal session.
NOTIFY verifies that you have the necessary authority to change the ready-for-update status of the
screening file. If you do not have the necessary authority, NOTIFY displays an error screen with an
explanatory message instead of the menu screen. NOTIFY also verifies that the screening file's status
can be changed as you request. If your request can not be honored, NOTIFY displays an error message
on the menu screen.
The following subsections describe some of NOTIFY's features in more detail.
September 1993 7-1 NOTIFY
-------
Air Quality Data Storage
AIRS User's Guide
Volume AQ3
Top LeveI
User
Sess ion
Menus
AMP080
NOT IFY
Program
ADABA5
Menu or
Error Screen
Table
Fl le
Figure 7-1. NOTIFY Data Flow Diagram
NOTIFY
7-2
September 1993
-------
AIRS User's Guide
Volume AQ3 Air Quality Data Storage
7.1.1 Authority To Use NOTIFY
NOTIFY allows you to change the status of an Air Quality screening file for which you have update
authority. You can not use NOTIFY with a screening file for which you have read-only authority, or
with a screening file that is not for Air Quality data. The AIRS user profile screen lists your access
authority (read-only or update) and the type (Air Quality or Facility) of each of your screening files.
NOTIFY verifies that the screening file you selected on the AIRS user profile screen is for Air Quality
data and that you have authority to update it.
7.1.2 Screening File Status
NOTIFY determines a screening file's status from the value of the STATUS-FLAG field of the AIRS
Table file. There are four STATUS-FLAG values:
N The screening file is not locked; it can be accessed and used freely by the data storage
processes, but it is not eligible for update processing. NOTIFY stores this value when you
rescind a ready-for-update notification, and the UPDATE process stores this value after
using the screening file to update the database.
L The screening file is locked; it is available only to the database administrator for update
processing, and can not be used with the LOAD, EDIT, or CORRECT processes. NOTIFY
stores this value when you notify the AIRS database administrator that your screening file
is ready for update processing.
S The AIRS database administrator has selected the screening file for use with the SCAN
process (see Section 11).
U The screening file has been processed by SCAN and is ready for use with the UPDATE
process (see Section 11).
NOTIFY can change a screening file's status from N (not locked) to L (locked) or from L back to N.
NOTIFY can not alter a screening file's status after the AIRS database administrator has begun using it
for update processing and its status is S or U. While a screening file has status S or U, you can not use
it with any of the data storage processes, although you can list the raw data transactions in it using the
AQ Retrieval Subsystem.
7.1.3 NOTIFY Protects Your Screening File
NOTIFY protects your screening file by locking it when you set its ready-for-update status. While it is
locked, your screening file can not be accessed by the LOAD or EDIT processes, and it can not be
altered by the CORRECT process. This ensures that your transactions and their edit levels do not change
between the time you use NOTIFY and the time the AIRS database administrator uses the screening file
to update the database. The file is "frozen" in the same state as when you did its final EDIT. Were this
not the case, it would be difficult to reconcile the results of UPDATE processing with expected results
September 1993 7-3 NOTIFY
-------
AIRS User's Guide
Air Quality Data Storage Volume AQ3
based on EDITing of the file. For example, if you were allowed to load more transactions into a
screening file after setting its ready-for-update status, the new transactions might interact with the
previously validated transactions, and their edit level might be lowered from 3 to 1. The transactions
with lowered edit levels would not be used by UPDATE, contrary to your expectations.
7.1.4 NOTIFY Protects the Database
NOTIFY protects the AIRS database with two related restrictions. First, NOTIFY allows only one
screening file of a group to be locked at a given time. (The screening files of a group have the same
names except in the last two character positions, such as "R04AQA01" and "R04AQA02".) This
restriction protects the database by preventing the use of incompatible transactions from different
screening files. Incompatible transactions are possible because EDIT only checks the transactions in one
screening file at a time; it does not cross-check among the screening files of a group. For example, it
is possible that in one screening file there could be a transaction to delete a value from the database and
a transaction in another screening file to change the same value. Both transactions could be validated
independently, and either one could legally update the database. But if both transactions were used, the
ultimate effect on the database would depend on the order in which the screening files were processed.
You could end up with a value where you did not expect one, or vice versa.
The second restriction follows as a consequence of the first. NOTIFY requires that EDIT must have
applied lev el-3 edit checks to a screening file (and that at least one transaction must have passed the level-
3 checks) since the last database update involving any screening file in the same group. If your screening
file has not passed level-3 edit checks since the last "group update", NOTIFY will not allow you to set
the ready-for-update status. The reason for this restriction can be explained by continuing the example
presented above. After the first screening file has been processed and UPDATE has deleted the value
from the database, edit checks would have to be run on the second screening file. The modify
transaction, which previously had passed level-3 edit checks, would now fail because the value to be
modified had been deleted from the database. Thus, the second round of edit checks required by
NOTIFY would prevent the incompatible transactions being processed by UPDATE.
NOTIFY 7-4 September 1993
-------
AIRS User's Guide
Volume AQ3
Air Quality Data Storage
02/16/90
AIRS Air Quality Subsystem
User Profile COT
AAPOOOQ
Password:
Printer 10: RHTOOO
/•Account Code: ASUD
Bin lumber: 6132
SCREENING TILES
ANADBF01 Air Quality Screening File Read Only Not Locked
ANADBF95 Air Quality Screening File Read Only Not Locked
S55AQA01 Air Quality Screening File Update Not Locked
Enter;Prof iIe Data (opt i onaI)
PF3=end : .; • :PF4=subsystem menu
PF5=terminate
02/22/90
AIRS Air Quality Subsystem
Main Menu
1. Submit Data
2. Retrieve Data - Standard Batch
3. Retrieve Data - Ad Hoc Batch
4. Browse Data - Online
Please enter Selection: 1
NEED ASSISTANCE?
CALL THE AQS HOTLINE AT 1-800-333-7909
AAPOOOA
PF3=end (profile)
PF4-subsystem menu
PF5=terminate
Figure 7-2. AIRS AQS User Profile and Main Menu Screens
The AIRS AQS main menu appears after the user profile is established.
September 1993
7-5
NOTIFY
-------
AIRS User's Guide
Air Quality Data Storage Volume AQ3
7.2 NOTIFY Initiation Procedures
This section tells how to initiate the NOTIFY process. Normally you would use NOTIFY when you have
validated the transactions in a screening file with EDIT and you want them to be used to update the AIRS
database. You also might use NOTIFY to rescind a prior ready-for-update notification if you change
your mind about the readiness of a screening file for update processing.
You initiate the NOTIFY process by selecting the appropriate options from the menus of the AIRS Top
Level User session. See Section 3.4 of this manual for AIRS logon procedures, Section 3.6 for Top
Level User procedures.
7.2.1 User Profile Screen
When you begin an AIRS terminal session, the first screen is the user profile. A sample is shown at the
top of Figure 7-2. To use NOTIFY, you must choose a screening file on the user profile screen. You
do not need to enter your AIRS password to use NOTIFY, but you may need it if you use another Data
Storage process in the same AIRS terminal session.
7.2.2 AIRS AQS Main Menu
The second screen of an AIRS terminal session is the AIRS AQS main menu. A sample is shown at the
bottom of Figure 7-2. To use NOTIFY, choose option 1, "submit air quality data". If you forgot to
select an air quality screening file, the main menu screen displays an error message and you are advised
to return to the user profile screen to select a screening file.
7.2.3 AQ Submit Menu
The AQ Data Storage Subsystem "submit" menu, shown in Figure 7-3, is the third screen of the AIRS
terminal session. To invoke NOTIFY, select option 4 of the submit menu, "notify AIRS database
administrator for update".
NOTIFY 7-6 September 1993
-------
AIRS User's Guide
Volume AQ3 Air Quality Data Storage
05/25/89 AIRS AIR Quality Subsystem AHP002
Submit
Enter Selection: 4
1 LOAD input Transactions to Screening File :
2 EDIT Screening File (Batch Execution)
3 CORRECT Screening file (Online Adds, Changes, Deletes)
4 NOTIFY -AIRS Data Base Administrator for UPDATE
5 *EC€IVE Messages . • :•••'-,-:.^:. : "••••', • . • :•'•• • •
6 DELETE all Transactions :from Screening File
PF3=end PF4=main menu PF5-terminate
05/11/87 AIRS Air Quality Subsystem NOTIFY
Menu for Screening File S55AOA01
ENTER selection:
1 UPDATE from Screening File
9 Cancel UPDATE request
PF3=end -PF4=main menu PF5=terminate
Figure 7-3. The NOTIFY Menu Screen
The NOTIFY menu appears after selecting submit menu option 4.
September 1993 7-7 NOTIFY
-------
AIRS User's Guide
Air Quality Data Storage Volume AQ3
7.3 NOTIFY Operational Procedures
This section tells how to use NOTIFY. It also explains the meaning of NOTIFY error messages and what
to do about them.
After invoking NOTIFY from the submit menu, one of two possible screens will appear: the NOTIFY
menu or the NOTIFY error screen.
7.3.1 NOTIFY Menu
If you are authorized to use NOTIFY for the screening file you selected, the NOTIFY menu is displayed.
A sample is shown at the bottom of the facing page. Use this screen to specify the ready-for-update
status of a screening file.
The screen is simple and easy to use. Beside the "ENTER selection" prompt, type one of the two option
codes listed on the screen:
1 to set the ready-for-update status of your screening file
9 to rescind a ready-for-update status set previously.
To exit from NOTIFY without doing anything, leave the option field blank.
When you have typed the code for the option you want to use, press the ENTER key or one of the
standard PF keys listed at the bottom of the screen. ENTER and PF3 have the same effect: they transfer
control back to the Air Quality submit menu. PF4 transfers control to the AIRS main menu, and PF5
terminates the AIRS terminal session.
NOTIFY acts on your ready-for-update specification regardless of which one of the four keys you use
(ENTER, PF3, PF4, or PF5). The PF keys do not abort the action of NOTIFY. They only determine
where control is transferred after NOTIFY has set the ready-for-update status of the screening file as you
directed. To exit from NOTIFY without changing the screening file's status, leave the option field blank.
If you use NOTIFY correctly and if you specify a valid ready-for-update status, NOTIFY sets the
screening file status as you requested and exits without displaying any other screen or confirming that
the screening file's status was changed. The absence of an error message means NOTIFY did as you
requested. If you use the ENTER key, the next screen after NOTIFY will be the submit menu.
NOTIFY 7-8 September 1993
-------
AIRS User's Guide
Volume AQ3 Air Quality Data Storage
05/11/87 AIRS Air Quality Subsystem NOTIFY
Nenu for Screening file S55AQA01
CUTER selection: 9
1 UPDATE from Screening File
9 Cancel UPDATE request
Screening File 'S55AOAOV is not locked for update
PF3=end PF4=main menu PF5=terminate
Figure 7-4. The NOTIFY Menu Screen Showing an Error Message
September 1993 7-9 NOTIFY
-------
AIRS User's Guide
Air Quality Data Storage Volume AQ3
If you use the NOTIFY menu incorrectly or if you attempt to set a screening file's status improperly,
NOTIFY takes no action on your request and redisplays the menu with an error message near the bottom
of the screen. A sample of the menu screen with an error message is shown on the facing page. You
must correct the error and press ENTER or one of the valid PF keys in order to continue.
Any of the following error messages can be displayed on the NOTIFY menu screen. They are listed in
alphabetical order.
Date of edit level three is less than last update date
This message occurs if you choose NOTIFY option 1, to set the ready-for-update status of your
screening file, when it has not been validated by EDIT recently enough or when none of the
transactions in it have passed level-3 edit checks. To be eligible for update processing, level-3 edit
checks must have been applied to the screening file since the last database update involving any
screening file in the same group, and at least one transaction in the screening file must have passed
the level-3 edit checks. You must run EDIT again and apply level-3 edit checks before you can
set the screening file's ready-for-update status. Erase the "1" from the option field of the menu
and press ENTER or one of the valid PF keys to exit NOTIFY.
Invalid disposition code. Use '!' (update) or '9' (cancel update)
This message occurs if you enter an invalid option code in the field beside "ENTER selection".
Type one of the valid codes, "1", "9", or blank, then press ENTER or one of the valid PF keys.
Screening File '' has already been Scanned
This message occurs if you choose NOTIFY option 9, to rescind the ready-for-update status of your
screening file, when it has already been selected by the AIRS database administrator for use in
update processing (that is, it has a status code of "S" or "U"). Once the database administrator has
begun using the file, you can not rescind the ready-for-update status. Erase the "9" from the option
field and press ENTER or one of the valid PF keys to exit NOTIFY.
Screening File '' is not locked for update
This message occurs if you enter NOTIFY option 9, to rescind the ready-for-update status of your
screening file, when it is not locked (that is, it has a status code of "N"). If you intended to lock
the screening file, change the "9" in the option field to "1" then press ENTER or one of the valid
PF keys. To exit NOTIFY without changing the screening file's status, erase the "9" from the
option field and press ENTER or one of the valid PF keys.
Screening File '' is locked for another process
This message occurs if you enter a code of "1" (update) or "9" (cancel update) when the screening
file has been locked by or for a process other than NOTIFY, SCAN, or UPDATE.
NOTIFY 7-10 September 1993
-------
AIRS User's Guide
Volume AQ3 Air Quality Data Storage
Screening File group is already locked for update
This message occurs if you choose NOTIFY option 1, to set the ready-for-update status of your
screening file, when another screening file in the same group (see note below) is already locked
for update processing (that is, it has a status code of "L", "S", or "U"). You must rescind the
ready-for-update status of the other screening file or wait until it has completed update processing
before you can set the ready-for-update status of the current screening file. Erase the T from the
option field and press ENTER or one of the valid PF keys to exit NOTIFY.
Note: The current version of NOTIFY generates this message whether the locked screening file
is the same one you tried to lock or another one in the same group. A future version of NOTIFY
probably will include a separate message for the case in which the screening file you attempt to
lock is die one already locked.
Unrecognized function. Use PF3, PF4, or PF5
This message results from the use of a PA key or PF key that is not defined for this screen. The
valid "action" keys for this screen are ENTER, PF3, PF4, and PF5.
September 1993 7-11 NOTIFY
-------
AIRS User's Guide
Air Quality Data Storage Volume AQ3
OS/11/87 AIRS Air Quality Subsystem .-,' : NOTIFY
You carrot update from Screening File 'OTHASFOV
Press PF3 to return to the AIRS AQ Supervisor
Press PF4 to return to the AIRS Main Menu
' Press PF5 to terminate your AIRS session
Figure 7-5. The NOTIFY Error Screen
NOTIFY 7-12 September 1993
-------
AIRS User's Guide
Volume AQ3 Air Quality Data Storage
7.3.2 NOTIFY Error Screen
NOTIFY displays an error screen instead of the menu screen if a condition exists that prohibits you from
using NOTIFY with the selected screening file. A sample of the NOTIFY error screen is shown on the
facing page. A message in the second line of the screen identifies the error condition, and following lines
list the PF keys you may use to terminate NOTIFY. Although the screen does not say so, you may also
press the ENTER key, which has the same effect as PF3. (Note that the AQ submit menu, which is
invoked by PF3, is called the "AQ supervisor" on the NOTIFY error screen.)
All the messages NOTIFY can display are listed below with a brief explanation of the cause of the error.
In practice, only the last error message should ever occur. The other error conditions are detected by
the AIRS top level user session. The first three error messages could occur only if the Table File were
corrupted between the time you began your top level user session and the time you invoked NOTIFY.
That is extremely unlikely.
Screening File ' < name >' does not exist
There is no record in the Table File of the screening file named in the message. This message
indicates the Table File is corrupted. Note the screening file name listed in the message and
contact the AIRS database administrator.
Screening File '' not for AQ data
The screening file named in the message is not for Air Quality data. This message indicates the
Table File is corrupted. Note the screening file name listed in the message and contact the AIRS
database administrator.
You cannot access Screening File ' < name >'
You are not authorized to access the screening file named in the message. Since you can only
select a screening file you are authorized to access, this message indicates the Table File is
corrupted. Note the screening file name listed in the message and contact the AIRS database
administrator.
You cannot update from Screening File ''
You do not have update authority for the screening file named in the message. In order to change
the screening file's ready-for-update status, you must have update authority. If you selected the
wrong screening file, return to the AIRS user profile screen and make the correct selection, then
invoke NOTIFY again. If you selected the right screening file and you are supposed to have update
authority, contact the AIRS database administrator.
September 1993 7-13 NOTIFY
-------
AIRS User's Guide
Air Quality Data Storage Volume AQ3
7.4 NOTIFY Follow-Up Procedures
After you have set the ready-for-update status of your screening file, it will be used fairly soon thereafter
in the regularly scheduled update cycle for the Air Quality Subsystem of the AIRS database. When your
screening file is involved in the update activities, several reports are produced by the SCAN process (see
Section 11). The reports are written in files that you can look at and print if you wish. The database
administrator posts the current status of update activities and lists which SCAN reports are available in
dataset AIRA.NADB.MESSAGE(UPDATE). You can browse that dataset using option 1 of the SYSD
or ISPF processor (see Section 3) to determine when your screening file was used in update activities and
to determine the names of the datasets containing the pertinent SCAN reports. If you do not get any
indication within a reasonable time that your screening file is being used in the update processes, contact
the AIRS database administrator.
When the database administrator has finished using your screening file to update the database, it is
automatically unlocked and you may begin using it again to load and validate more transactions, the
UPDATE process creates a message that you can "receive" with the MESSAGE process, which is
described in the next section of this volume. The message tells when your screening file was used to
update the database and how many data values were involved. When you receive the UPDATE-generated
message, you can use the screening file again.
If you use NOTIFY to clear the ready-for-update status of your screening file, it immediately becomes
available to you. You then may use any of the data storage processes with the Screening File (LOAD,
EDIT, or CORRECT).
NOTIFY 7-14 September 1993
-------
AIRS User's Guide
Volume AQ3 Air Quality Data Storage
7.5 Restrictions, Limitations, and Warnings
When using NOTIFY, keep in mind these features that are designed to protect your screening file(s) and
the AIRS database:
1) You can not use a screening file after setting its ready-for-update status.
2) At any particular time, you can set the ready-for-update status of only one file in a group of
screening files.
3) In order to set the ready-for-update status of your screening file, it must have passed level-3 edit
checks since the last update involving any screening file in the same group.
Also, you should be aware of the ambiguity of NOTIFY's error message, "Screening file group is already
locked for update". NOTIFY displays this message whether the locked file is the one you selected or
another file in the same group. Only the database administrator can determine which file it is. A future
version of NOTIFY will probably include an additional message to inform you that the file you are
attempting to lock is already locked.
September 1993 7-15 NOTIFY
-------
AIRS User's Guide
Volume AQ3 Air Quality Data Storage
8.0 The MESSAGE Process
MESSAGE is a utility process of the AQ Data Storage Subsystem of AIRS. This section describes what
MESSAGE does and how to use it.
8.1 Overview
The purpose of the MESSAGE process is to display messages related to a particular screening file and,
optionally, to delete them. The messages are created by other processes of the Air Quality Data Storage
Subsystem. Typically, a message is just one line of text, enough to tell you when a process executed and
whether it completed successfully. MESSAGE does the same things for the AIRS database administrator
as for you, the user of the Data Storage Subsystem. Your messages are generated by the LOAD, EDIT,
and UPDATE processes; the database administrator's messages are generated by SCAN, UPDATE, and
ARCHIVE. Messages for the database administrator are also generated by NOTIFY when you set or
rescind the ready-for-update status of screening files.
The data flow diagram in Figure 8-1 illustrates MESSAGE'S operating environment. MESSAGE is
invoked directly from the submit menu of the Air Quality Subsystem. It executes online and displays one
or more screens of messages which it reads from the Table File. MESSAGE will delete from the Table
File some or all of the displayed messages if directed to do so by specifications entered on the MESSAGE
screen. If there are no messages for the selected screening file, MESSAGE displays a screen that tells
you so.
Normally, MESSAGE reverts control to the Air Quality submit menu when it has finished its processing.
However, you may invoke the AIRS main menu with the PF4 key or terminate your AIRS terminal
session with the PFS key. MESSAGE processes your specifications for deleting or keeping messages
before transferring control to another function or terminating your AIRS terminal session.
September 1993 8-1 MESSAGE
-------
Air Quality Data Storage
AIRS User's Guide
Volume AQ3
Top LeveI
User
Session
Menus
MESSAGE Screens
AMPQ9D
MESSAGE
Program
ADABAS
Table
Fi le
Figure 8-1. MESSAGE Data Flow Diagram
MESSAGE
8-2
September 1993
-------
AIRS User's Guide
Volume AQ3
Air Quality Data Storage
02/16/90
AIRS AIR Quality subsystem
User Profile COT
AAPOOOQ
'Password:
Printer ID: RHTOOO
Account Code: ASUD
Bin Number: B13Z
SCREENING FILES
ANAOBF01 Air Quality Screening File
ANAOBF9S Air Quality Screening File
S55AQA01 Air Quality Screening File
Enter Profile Data (optional)
PF3*end PF4=subsystem menu
Read Only
Readonly
:update
Not Locked
:Not Locked
Not Locked
PF5=terroinate
02/22/90 AIRS Air Quality Subsystem
Main Menu
1. Submit Data
2. Retrieve Data - Standard Batch
3. Retrieve Data - Ad Hoc Batch
4. Browse Data - Online
Please enter Selection: 1
NEED ASSISTANCE?
CALL THE AQS HOTLINE AT 1-800-333-7909
PF3*end (prof He) PF4=subsystem menu
AAPOOOA
PF5=terminate
Figure 8-2. AIRS AQS User Profile and Main Menu Screens
The AIRS AQS main menu appears after the user profile is established.
September 1993
8-3
MESSAGE
-------
AIRS User's Guide
Air Quality Data Storage Volume AQ3
8.2 MESSAGE Initiation Procedures
This section tells how to initiate the MESSAGE process. Normally you would use MESSAGE when you
want to check the status of a data storage process you initiated earlier.
You invoke the MESSAGE process by selecting the appropriate options from the menus of the AIRS Top
Level User session. See Section 3.4 of this manual for AIRS logon procedures, Section 3.6 for Top
Level User procedures.
8.2.1 User Profile Screen
When you begin an AIRS terminal session, the first screen is the user profile. A sample is shown at the
top of Figure 8-2. To use MESSAGE, you must choose a screening file on the user profile screen.
You do not need to enter your AIRS password to use MESSAGE, but you may need it if you use another
Data Storage process in the same AIRS terminal session.
8.2.2 AIRS Main Menu
The second screen of an AIRS terminal session is the AIRS main menu. A sample is shown at the bottom
of Figure 8-2. To use MESSAGE, choose option 1, "submit air quality data". If you forgot to select
an air quality screening file, the main menu screen displays an error message and you are instructed to
return to the user profile screen to select a screening file.
8.2.3 AQ Submit Menu
The AQ Data Storage Subsystem "submit" menu, shown in Figure 8-3, is the third screen of the AIRS
terminal session. To invoke MESSAGE, select option 5 of the submit menu, "receive messages".
MESSAGE 8-4 September 1993
-------
AIRS User's Guide
Volume AQ3 Air Quality Data Storage
OS/25/89 AIRS AIR Quality Subsystem AMP002
Submit
Enter Selection:
•t: LOAD Input!Transactions to Screening File
2 EDIT Screening File (Batch Execution)
3 CORRECT Screening File (Online Adds, Changes, Deletes)
:4 NOTIFY AIRS Data Base Administrator for UPDATE
5 RECEIVE Messages
6 DELETE all Transactions from Screening File
PF3»end PF4=main menu PF5.=terminate
06/06/87 AIRS Air Quality Subsystem MESSAGE
Messages for Screening File S55AQA01
Date Time User Message Text
K 04-21 13:27 RRM EDIT failed - an ADABAS error occurred for JOB 'RRHEOITV
D 04-22 09:38 TAD LOAD failed - Screening File 'S55AQA01' was locked.
K 04-23 12:42 RRM LOAD unsuccessful - Input Transaction File was empty.
K 04-23 19:11 RRM LOADed 00002704 records in Screening File 'S55AQAOV.
K 04-24 13:27 RRM EDITED 00002704 records in Screening File 'S55AQAOT.
MORE...
D,K=msg disp PF8=next PF4=main menu PF=terminate PA1=oops
Figure 8-3. Sample MESSAGE Screen
The MESSAGE screen appears after selecting submit menu option 5.
September 1993 8-5 MESSAGE
-------
AIRS User's Guide
Air Quality Data Storage Volume AQ3
8.3 MESSAGE Operational Procedures
This section tells how to use MESSAGE. It also explains the meaning of MESSAGE error messages and
what to do about them.
After invoking MESSAGE from the submit menu, one of two possible screens will appear. If there is
at least one message pertinent to the screening file you selected on the user profile screen, you will see
the normal MESSAGE screen, described below. If there are no messages for the screening file you
selected, you will see a "no messages" screen, which is described later.
8.3.1 The MESSAGE Screen
The format of the MESSAGE screen is shown at the bottom of the facing page. The current date is given
in the upper left corner of the screen and the name of the selected screening file is shown in the second
line of the screen title. The area for displaying messages occupies most of the screen, between the
column headings near the top and the PF key designations at the bottom. The line just above the PF key
designations is reserved for operational messages. The left part of the line contains either "MORE...",
to indicate that there are more messages available for viewing that would not fit on the current screen,
or "NO MORE MESSAGES". The remainder of the line is used for error messages. If you make a
mistake, this is where MESSAGE tells you about it.
There are several columns, or fields, associated with each message on the screen. They are identified
in the column headings. The "date" and "time" columns give the date (as month-day) and the time (as
hounminute) when the message was created. This is approximately the completion time of the process
generating the message. The messages are displayed in chronological order, oldest first. Next is the
"user" column, which shows the NCC-IBM user-ID of the person who initiated the process generating
the message. The text of the message follows the user-ID and occupies most of the line. Although all
the messages currently defined have only one line of text, the MESSAGE screen can display multiple-line
messages if they are created. The date, time, and user-ID are displayed in the first line of a message and
are not repeated in subsequent lines.
At the left side of the screen is an unlabeled column for specifying the disposition of each message: keep
(K) or delete (D). MESSAGE assigns a default disposition of K (keep). In other words, by default, all
messages are kept. You can override the default disposition of any message by typing "d" in its
disposition field, or change the disposition from one to the other by typing "d" or "k" in the disposition
field. The example of the MESSAGE screen shown at the bottom of the facing page shows the messages
for "user" TAD changed to delete (D). Putting any other character in the field, including blank, results
in an error message (see below).
MESSAGE 8-6 September 1993
-------
AIRS User's Guide
Volume AQ3 Air Quality Data Storage
06/01/87 AIRS Air duality Subsystem MESSAGE
Messages for Screening File R01BOS01
Date Time User .............wvxe8M8e text>----------
E 06-13 22:08 BSJ EDITed 00037638 records in Screening File 'R01BOS01'
NO MORE MESSAGES Invalid disposition code. Use 'D' (delete) or '«' (keep).
D,K=msg disp PF8=next PF3=end PF4=main menu PFS-terminate PA1=oops
Figure 8-4. The MESSAGE Screen Showing an Error Message
September 1993 8-7 MESSAGE
-------
AIRS User's Guide
Air Quality Data Storage Volume AQ3
When you have specified the disposition codes for the messages, press ENTER or one of the other keys
listed at the bottom of the screen. Pressing any of the keys except PA1 causes MESSAGE to act on the
disposition codes of the messages on the screen. (Any messages that have not been displayed are not
affected.) Each message with disposition code D is deleted. Each message with disposition code K is
retained and is available for viewing again in another MESSAGE session. The PA1 key is an escape
mechanism. It terminates MESSAGE and returns you to the Air Quality submit menu without processing
any of the message disposition codes on the screen. All the messages are kept regardless of their
disposition codes. (Any messages deleted on a previous screen are still deleted, however.) The PA1 key
would be useful if you invoked MESSAGE by mistake, for example, and wanted to escape without having
to respecify any changed dispositions for the messages.
What MESSAGE does after processing the message disposition codes depends on which "action" key you
press. The valid keys and their effects are:
ENTER
or Return to the Air Quality submit menu.
PF3
PF4 Return to the AIRS AQS main menu.
PF5 Terminate the AIRS terminal session.
PF8 Display the next screen of messages. This key is valid only if there are more
messages available to be displayed, as indicated by "MORE..." in the lower left
corner of the screen. Otherwise, using PF8 results in an error message.
PA1 Return to the Air Quality submit menu without processing the message disposition
codes on the current MESSAGE screen.
If you use the MESSAGE screen incorrectly or specify an invalid disposition code, MESSAGE takes no
action on the message disposition codes and displays an error message near the bottom of the screen.
An example of the MESSAGE screen with an error message is shown on the facing page. You must
correct each invalid disposition code and press ENTER or one of the other valid keys in order to
continue.
Any of the following error messages can be displayed on the MESSAGE screen. They are listed in
alphabetical order.
Invalid disposition code. Use 'D' (delete) or 'K' (keep).
There are only two valid codes for message disposition. You must one of them. Each invalid code
is highlighted on the screen; the valid codes are not highlighted. Tab to the invalid code(s) and
type the correct value(s), then press ENTER or another valid key listed at the bottom of the screen.
'Next screen' command invalid — no more messages available.
You can use the PF8 key only if there are more messages available to view, as indicated by
"MORE..." in the lower left corner of the screen. Use one of the other valid PF keys or ENTER
instead of PF8.
MESSAGE 8-8 September 1993
-------
AIRS User's Guide
Volume AQ3 Air Quality Data Storage
Unrecognized function. Use PF3, PF4, PF5, PF8, OR PAL
You have used a PA or PF key that is not defined for MESSAGE. Use the ENTER key or one
of the keys listed in the error message.
September 1993 8-9 MESSAGE
-------
AIRS User's Guide
Air Quality Data Storage Volume AQ3
8.3.2 The "No Messages" Screen
If there are no messages for the screening file you selected, MESSAGE displays a screen that tells you
so. An example of the "no messages" screen is shown below.
The "no messages" screen lists the AIRS standard PF keys you can use to terminate MESSAGE, and the
result of using each one. For consistency with the MESSAGE screen that displays messages, you can
also use the ENTER and PA1 keys. They have the same effect as PF3: control returns to the AQ submit
menu.
If you use a PA or PF key that is not defined for MESSAGE, the terminal alarm beeps to signal that you
have used an invalid key. There is no error message.
MESSAGE 8-10 September 1993
-------
AIRS User's Guide
Volume AQ3 Air Quality Data Storage
06/01/87 AIRS Air Quality Subsystem MESSAGE
There are no messages for Screening File ONADBF98
Press PF3 to return to the AIRS AO Supervisor
Press PF4 to return to the AIRS Main Menu
Press PF5 to terminate your AIRS session
Figure 8-5. The "No Messages" Screen
September 1993 8-11 MESSAGE
-------
AIRS User's Guide
Air Quality Data Storage Volume AQ3
8.4 MESSAGE Follow-Up Procedures
The primary purpose of MESSAGE is to tell you the status of one of the AQ Data Storage processes as
it relates to your screening file. Once you have seen the status message, there is really nothing more you
can do with MESSAGE. You should take appropriate action based on the content of the status message.
For example, when you receive a message that says your screening file has been used to update the
database, you should make it known to others in your group that the screening file is available for use
again.
You should make it your practice to delete your messages after you have read them, or at least when the
LOAD-EDIT-UPDATE cycle is completed for a screening file. Retaining messages unnecessarily clutters
your MESSAGE screen and the Table file.
MESSAGE 8-12 September 1993
-------
AIRS User's Guide
Volume AQ3 Air Quality Data Storage
8.5 Restrictions, Limitations, and Warnings
When using MESSAGE keep in mind these features:
1) The default action, taken when you press ENTER, is to exit from MESSAGE and return to the AQ
submit menu. If there are more messages than will fit on one screen, you must remember to use the PF8
key in order to view the additional messages. If you do not view the additional messages, they are
automatically kept.
2) MESSAGE shows you all the messages for a screening file, including those generated by other
users. Be careful not to delete their messages inadvertently.
3) Like all other AQ Data Storage processes, MESSAGE deals only with the screening file you
selected on the AIRS user profile screen at the start of your session. If you need to receive messages for
several screening files, you must select each one at the user profile screen then invoke MESSAGE.
4) The AIRS database administrator periodically deletes "old" messages - those which have been
retained for several weeks or months. If there is some reason why you need to keep messages for a long
time, make arrangements with the database administrator.
5) You can not use MESSAGE to find out when the database administrator has processed your
screening file with SCAN (see Section 11). That information is posted in dataset
AIRA.NADB.MESSAGE(UPDATE), which you can look at using option 1 of the SYSD or ISPF
processor (see Section 3).
September 1993 8-13 MESSAGE
-------
AIRS User's Guide
Volume AQ3 Air Quality Data Storage
9.0 The DELETE Process
DELETE is the process used to delete transactions from a Screening File in the AQ Data Storage
Subsystem of AIRS. This section describes what DELETE does and how to use it.
9.1 Overview
DELETE is a batch process that deletes all transactions in a Screening File.
DELETE deletes one transaction at a time until all transactions have been deleted. After the successful
completion of DELETE, the Screening File contains no transactions and it is available for processing new
transactions.
The data flow diagram in Figure 9-1 illustrates how DELETE is invoked and what it does. Like other
batch AIRS processes, DELETE executes under the control of JCL and parameters that you specify
during an AIRS terminal session. DELETE also accesses the Table File to read and write control
information and to write a status message that you can view using the MESSAGE process. The primary
outputs of this process are a screening file with no transactions and a DELETE Summary Report stating
the number of records deleted.
September 1993 9-1 DELETE
-------
Air Quality Data Storage
AIRS User's Guide
Volume AQ3
. 1
//A
•*
— T$\
Menus
Top Level
User
Session
/
JOB
S^*
JCL and
parameters
AMP020
DELETE
Program
Screen)ng
Fl le
Summary Report
Figure 9-1. DELETE Data Flow Diagram
DELETE
9-2
September 1993
-------
AIRS User's Guide
Volume AQ3
Air Quality Data Storage
02/16/90
AIRS Afr Quality Subsystem
User Profile COT
AAPOOOO
Password:
Printer ID: RMTOOO
.Account Code: ASWD
Bin Number: 8132
SCREENING FILES
ANADBF01 Air Quality Screening File
ANADBF95 Afr Quality Screening File
S55AQA01 Air Quality Screening File
Read Only
Read Only
Read Only
Not Locked
Not Locked
Not Locked
Enter Profile Data (optional)
PF3=end PF4»matn menu
PF5=terminate
02/22/90 AIRS Air Quality Subsystem
Main Menu
1. Submit Data
2. Retrieve Data - Standard Batch
3. Retrieve Data -Ad Hoc Batch
4. Browse Data - Online
Please enter Selection: 1
NEED ASSISTANCE?
CALL THE AOS HOTLINE AT 1-800-333-7909
AAPOOOA
PF3=end (profile)
PF4=subsystem menu
PA5=terminate
Figure 9-2. AIRS User Profile and Main Menu Screens
The AIRS main menu appears after the user profile is established.
September 1993
9-3
DELETE
-------
AIRS User's Guide
Air Quality Data Storage Volume AQ3
9.2 DELETE Initiation Procedures
This section tells how to initiate the DELETE process. "Initiating" DELETE means specifying the
information needed for the DELETE program and submitting a batch job to execute it.
You initiate the DELETE process by selecting the appropriate options from the menus of the AIRS Top
Level User session and entering the required information. See Section 3.4 of this manual for AIRS logon
procedures, Section 3.6 for Top Level User procedures.
9.2.1 User Profile Screen
When you begin an AIRS terminal session, the first screen is the user profile. A sample is shown at the
top of Figure 9-2. If you plan to use DELETE, you must choose a screening file and enter its
password on the user profile screen. If you neglect to enter the password or enter it incorrectly, the
DELETE initiation will appear to work correctly, but the DELETE program will not be able to delete
transactions from the screening file and the batch job will terminate in error. Be sure you select a
screening file and enter its AIRS password.
9.2.2 AIRS Main Menu
The second screen of an AIRS terminal session is the AIRS main menu. A sample is shown at the bottom
of Figure 9-2. Choose option 1, "submit air quality data". If you forgot to select an air quality screening
file, the main menu screen displays an error message and you are advised to return to the user profile
screen to select a screening file. An error message is not displayed if you forgot to enter your AIRS
password.
DELETE 9-4 September 1993
-------
AIRS User's Guide
Volume AQ3
Air Quality Data Storage
06/02/89
AIRS Air Quality Subsyste
Submit
AMP002
Enter Selection: 6
1 LOAD Input Transactione to Screening File
2 EDIT Screening File (Batch Execution)
3 CORRECT Screening File (Ontine Adds, Changes, Deletes)
4 NOTIFY AIRS Data Base Administrator for UPDATE
5 RECEIVE Messages
6 DELETE all Transactions from Screening File
PF3=end PF4=main menu PF5=terminate
06/02/89
AIRS Air Quality Subsystem
JCL Parameters for DELETE Batch JOB
AMP002
ENTER
PF3*end
Screening File Id
JOB Name
Account Code/UID
Time (MM,SS)
Priority
Message Class
Number of Copies
Form Number
Room/Bin Number
Hold Output (Y/N)
Printer Site Id
. ANADBF96
TAD DEL01
ASUD AIRSP
03, 00
2
A
01
B044
N
RMTOOO
Press ENTER to submit JOB
PF4=main menu
PF5=terminate
Figure 9-3. The DELETE Job Submission Screen
The DELETE job submission screen appears after selecting submit menu option 6.
September 1993
9-5
DELETE
-------
AIRS User's Guide
Air Quality Data Storage Volume AQ3
9.2.3 AQ Submit Menu
The AQ Data Storage Subsystem "submit" menu, shown at the top of Figure 9-3, is the third screen of
the AIRS terminal session. To invoke DELETE, select option 6 of the submit menu, "DELETE all
Transactions from Screening File".
9.2.4 DELETE Job Submission Screen
The DELETE job submission screen appears next. A sample is shown at the bottom of Figure 9-3. Use
this screen to specify the information needed to submit a DELETE batch job.
9.2.4.1 Screen Description
All fields of the DELETE job submission screen have values from your user profile or appropriate default
values. The first field of the screen is for information only; it is not a data entry field.
SCREENING FILE ID
is the name of the screening file you chose on the user profile screen. Do not change this field.
The other fields of the DELETE job submission screen pertain exclusively to the JCL for the DELETE
batch job. They all have default values that you can change if you desire. You can find more
information about these fields in Chapter 4 of the NCC-IBM User's Guide.
JOB NAME
is the eight-character job name for the batch job to be submitted. The first three characters are
your user-ID and can not be changed. The last.five characters have the default value "DEL01",
but you may change them to any value consisting of letters and numbers.
ACCOUNT CODE
is the NCC-IBM account to which the cost of the DELETE batch job will be charged. The initial
value shown on the screen is what you specified for account code on the AIRS user profile screen.
You can change it to a different value, but it must be a valid code that you are authorized to use.
The FIMAS code "AIRSP", appended to the account code, can not be changed.
TIME IN MINUTES,SECONDS
is the maximum CPU time allowed for your DELETE batch job. You may change the default three
minutes, zero seconds to another value so long as it is a valid job time. The amount of time
specified affects when the job will run; jobs with shorter times generally run sooner than jobs with
longer times. The NCC-IBM User's Guide explains the allowed formats of the job time parameter
and the effect of job time on job scheduling. A job time of 30 seconds should be ample for
deleting 10,000 transactions, and the default time of three minutes should be enough for deleting
100,000 transactions.
DELETE 9-6 September 1993
-------
AIRS User's Guide
Volume AQ3 Air Quality Data Storage
PRIORITY
is a one-digit code that affects job scheduling and cost. The default value "2" is normal priority.
You may specify higher priorities of "3" or "4" which may cause a job to execute sooner, but cost
more. You may specify a lower priority of "1" which causes a job to be executed at night and
costs less. Note that a job with more than two minutes for CPU time will execute only at night,
so it is pointless to specify any priority but "1" for such a job.
MSGCLASS
(message class) is a one-character code that defines a category of printed output. The default value
"A" is a general category. You may also use "F" to specify output to the laser printer at NCC.
NUMBER COPIES
is the number of copies of batch job output to be printed. The default value is one; permissible
values are 1 through 99.
FORM NUMBER
is a four-digit code for the type of paper your output is printed on, the number of lines printed per
inch, and whether lower case letters are printed. The default value is blanks, which results in
usage of the standard form (STD). For the local printers at NCC the standard form is 6111, upper-
case only on 15 x 11-inch paper. Other common forms are 6311, for upper- and lower-case at six
lines per inch on IS x 11-inch paper; and 8381, available only on the laser printer, for upper- and
lower-case at eight lines per inch on 11 x 8.5-inch paper. Be aware that remote printers may not
be set up to handle anything but the standard form.
ROOM/BIN NUMBER
is a four-character code used by the computer center for distribution of printed output to the
appropriate location. The initial value shown on the screen is what you specified on the AIRS user
profile screen. You may change it to another valid bin number.
OUTPUT HELD
is a yes/no field that specifies whether the output of your DELETE batch job is to be held in the
output queue of the computer system (yes) or to be printed (no). The default value is "N" (no).
PRINTER-ID
is the printer site-ID where the output of your DELETE batch job is to be printed. The initial
value shown on the screen is what you specified on the AIRS user profile screen. You may change
it to another valid printer site-ID, such as "LOCAL" or "R321" or "N7R100". This field is not
used if you specify "Y" for OUTPUT HELD, and may be blank in that case.
September 1993 9-7 DELETE
-------
Air Quality Data Storage
AIRS User's Guide
Volume AQ3
INVALID FIELD
06/02/89
AIRS A!r Quality Subsystem
JCL Parameters for DELETE Batch JOB
AMP002
ENTER
Screening File Id
JOB Name
Account Code/UIO
Time (MN.SS)
Priority
Message Class
Hunter of Copies
form Number
Room/Bin Number
Hold Output (Y/N)
Printer Site Id
ANADBF96
TAD DEL01
ASUD AIRSP
03, 00
2
A
01
B044
N
RMTOOO
PF3=end
Press ENTER to submit JOB
PF4=main menu
PF5=terminate
Figure 9-4. The DELETE Job Submission Screen Showing an Error Message
DELETE
9-8
September 1993
-------
AIRS User's Guide
Volume AQ3 Air Quality Data Storage
9.2.4.2 Screen Usage
When you have specified the information on the DELETE job submission screen as you want it, press
the ENTER key. Each field of the screen is checked. If something is wrong an error message is
displayed at the top of the screen and the cursor is positioned to the invalid field. Correct the error and
press the ENTER key again.
While the DELETE job submission screen is displayed, you may use the standard AIRS PF keys:
PF3 return to the AQ submit menu
PF4 return to the AIRS AQS main menu
PFS terminate your AIRS terminal session
An error message is displayed at the top of the screen if you use any other PF or PA key. A DELETE
batch job is not submitted when you use any PF or PA key.
The following messages may occur while the DELETE job submission screen is displayed:
INVALID HELD
This message is displayed if you enter an invalid value or erase the value of a required field. Use
the position of the cursor to determine which field is invalid.
INVALID PF KEY
This message occurs if you use the PFS key, which is not valid on this screen.
NAT1011 REQUESTED FUNCTION KEY NOT ALLOCATED.
This message results from the use of any PA key or any PF key other than PFS, PF4, or PFS.
Only the PF3, PF4, and PFS keys are valid on this screen.
September 1993 9-9 DELETE
-------
AIRS User's Guide
Air Quality Data Storage Volume AQ3
9.3 Batch Job Submission
When all the fields of the DELETE job submission screen are correct, the DELETE batch job is
submitted using the parameters you specified on the DELETE job submission screen.
Reference Section 3.6.5 for more details on batch job submission.
The following error messages can occur while the DELETE job submission error screen is displayed:
INTERNAL CARD READER IS BUSY PRESS ENTER TO RETRY.
The system internal card reader was busy when the job was submitted. You should press ENTER
to return to the Job Submission screen and resubmit the job.
USER ACCOUNT CODE IS INVALID PRESS PF3 AND TRY AGAIN.
The Account Code entered on the DELETE Job Submission Screen is invalid. You should check
the Account Code entered on the screen.
INTERNAL CARD READER IS UNAVAILABLE PRESS ENTER TO RETRY.
The System internal card reader was unavailable when the job was submitted. You should re-
submit the job.
DELETE 9-10 September 1993
-------
AIRS User's Guide
Volume AQ3 Air Quality Data Storage
06/02/89 AIRS Air Quality Subsystem MESSAGE
Messages for Screening file ANADBF96
t>ate Tiae User --"-""--Message Text
K 06-02 11:11 FOB DELETE failed • Screening File 'ANADBF96' was locked.
K 06-02 15:21 FGB OELETEed 00000072 records from Screening File 'ANAOBF96'.
< OPERATOR INSTRUCTIONS AND ERROR MESSAGES >
D,K=msg disp PF8=next PF3=end PF4=main menu PF5=termirvate PA1=oops
Figure 9-5. Sample MESSAGE Screen Showing DELETE Messages
September 1993 9-11 DELETE
-------
AIRS User's Guide
Air Quality Data Storage Volume AQ3
9.4 DELETE Validation Procedures
This section tells how to detenrine whether a batch DELETE job was successful.
As outlined in Section 3.7 of this manual, there are two sources of information about the status of your
batch DELETE job: a message you can view using the MESSAGE process, and the printed output
(DELETE Summary Report) of the batch job.
9.4.1 Using the MESSAGE Process
The MESSAGE process of the AQ Data Storage Subsystem is the method provided by AIRS for
determining whether a DELETE batch job was successful. Detailed instructions for using MESSAGE
are presented in Section 8 of this manual. In brief, MESSAGE displays on your terminal screen the
messages pertinent to your screening file that have been generated by the batch processes of the Air
Quality Subsystem, including LOAD, EDIT, DELETE, NOTIFY, and UPDATE.
A DELETE message indicates whether the DELETE batch job was or was not successful and includes
the user-ID of the person who submitted the batch job and the date and time of job execution. If
DELETE was successful, the message tells how many transaction records were deleted. If DELETE
failed, the message indicates the reason why. The sample MESSAGE screen on the facing page shows
examples of both kinds of DELETE messages.
It is possible to get misleading information if you use MESSAGE while your DELETE batch job is
executing. When the DELETE batch program begins executing, it writes a message that says the job
failed because of a "system error". This is done so the appropriate message will be in place in case the
job does fail later due to a system error, such as exceeding the time limit for the job. When the
DELETE program completes its processing of the screening file, it replaces the "system error" message
with one that says the DELETE was successful. Similarly, if the DELETE program terminates because
of a non-system error condition (the screening file is locked, for example), it replaces the "system error"
message with the appropriate DELETE error message.
The point of this discussion is: wait until your DELETE batch job has finished executing before you use
MESSAGE to check its status. Otherwise, you may be misled by the temporary error message the
DELETE program creates.
DELETE 9-12 September 1993
-------
AIRS User's Guide
Volume AQ3
Air Quality Data Storage
09/30/93
AMP020
EPA AEROMETRIC INFORMATION RETRIEVAL SYSTEM (AIRS)
AIR QUALITr SUBSYSTEM
DELETE SUMMARY REPORT
FOR SCREENING FILE ANAOBA10
PAGE 1
320 EXISTING RECORDS WERE DELETED FROM THE SCREENING FILE.
* • * PROGRAM AMP020 TERMINATED SUCCESSFULLY ON 93-09-30 AT 11:09:27.3 • • •
Figure 9-6. Sample DELETE Summary Report for Successful Jobs
September 1993
9-13
DELETE
-------
AIRS User's Guide
Air Quality Data Storage Volume AQ3
9.4.2 Using DELETE Printed Output
The primary means of determining the success or failure of a DELETE batch job is the printed output
of the job. Unless the DELETE program terminates due to a system error, such as an I/O error, it
generates a DELETE summary report. You can tell easily from the summary report whether DELETE
was or was not successful.
If there is no DELETE summary report, then the batch job terminated due to a computer system error.
Look at the JES2 job log and the job step summary to determine what the error was. Contact the AIRS
database administrator or the computer center user support department for assistance if you need help.
Samples of the DELETE summary report are shown in Figures 9-6 and 9-7. The heading of the report
always has the same format. The date of program execution is printed in the upper left corner of the
page using the mm/dd/yy format. The name of the screening file from which transactions were deleted
is printed at the middle of the page in the last line of the heading.
The body of the report has three basic formats, depending on whether DELETE was or was not
successful. In the usual case, when DELETE processes the screening file successfully, the report body
lists the number of records deleted. An example of this report format is shown in Figure 9-6.
If DELETE was not successful, the body of the summary report is a message that identifies the error
condition. The message has two general formats depending on the type of error. Examples are shown
in the figure on the next page. In the first case, a one-line message identifies a condition the DELETE
program detected that prevented it from deleting transactions from the screening file. Examples of this
kind of error are user not authorized to update screening file or a screening file locked for update
processing. In the second case, a one-line message indicates that an "ADABAS error" occurred and
additional information is listed below the message. An error of this kind implies some sort of
malfunction in ADABAS, the AIRS database, or the DELETE program. Be sure to contact the AIRS
database administrator if DELETE terminates due to an ADABAS error. The information listed below
the error message may be useful for diagnosing and correcting the problem.
DELETE 9-14 September 1993
-------
AIRS User's Guide
Volume AQ3 Air Quality Data Storage
09/30/93 EPA AERONETRIC INFORMATION RETRIEVAL SYSTEM (AIRS) PAGE 1
AMP020 AIR QUALITY SUBSYSTEM
DELETE SUMMARY REPORT
FOR SCREENING FILE ANAOBA10
ERROR: The DELETE could not be done beciuse user-id JVM cannot updite the Screening File.
• • * PROGRAM AMP020 TERMINATED UNSUCCESSFULLY ON 93-09-30 AT 11:15:56.3 • • •
09/30/93 EPA AEROMETRIC INFORMATION RETRIEVAL SYSTEM (AIRS) PAGE 1
AMP020 AIR QUALITY SUBSYSTEM
DELETE SUMMARY REPORT
FOR SCREENING FILE ANA08A10
ERROR: The DELETE could not be done beciuse of «n ADABAS error. Please keep all reports and notify the AIRS database administrator.
ERROR INFORMATION
ERROR NUMBER • 1302
LINE NUMBER • 6SO
Figure 9-7. Sample LOAD Summary Reports for Failed Jobs
These samples show report formats for minor (top) and ADABAS (bottom) errors.
September 1993 9-15 DELETE
-------
AIRS User's Guide
Air Quality Data Storage Volume AQ3
All the error messages the batch DELETE program can generate are listed below, with a brief explanation
of the cause of the error and what you can do to resolve it. In practice, some of the messages will never
occur because the top level user session checks for the pertinent error condition. Two messages are listed
for each error condition. The first one is printed in the DELETE summary report. The second one is
the message you get with the MESSAGE process.
ERROR: THE SCREENING FILE COULD NOT BE ACCESSED BECAUSE IT DOES NOT
EXIST.
DELETE failed - Screening File 'name'does not exist.
The DELETE program could not find information about the specified screening file in the AIRS
Table file. This could only occur if the Table file changed between the time you submitted the
DELETE job and the tune it executed. Contact the AIRS database administrator.
ERROR: THE SCREENING FILE IS NOT FOR AIR QUALITY DATA.
DELETE failed - Screening File 'name' not for AQ data.
The specified screening file is for Facility data rather than Air Quality data. This could only occur
if the Table file changed between the time you submitted the DELETE job and the time it executed.
Contact the AIRS database administrator.
ERROR: THE SCREENING FILE COULD NOT BE ACCESSED BECAUSE IT WAS LOCKED
FOR OTHER PROCESSING.
DELETE failed - Screening File 'name' was locked.
The specified screening file has been locked for update processing using the NOTIFY process. If
the file was locked unintentionally, you may be able to unlock it with the NOTIFY process. If the
AIRS database administrator has used the SCAN process on the screening file, it can not be
unlocked with NOTIFY. Contact the AIRS database administrator.
ERROR: THE DELETE COULD NOT BE DONE BECAUSE USER-ID 'USCr-ID' CAN NOT
ACCESS THE SCREENING FILE.
DELETE failed - User-ID can not access Screening File 'name'.
You are not authorized to use the specified screening file. This could only occur if the Table file
changed between the time you submitted the DELETE job and the time it executed. Contact the
AIRS database administrator.
ERROR: THE DELETE COULD NOT BE DONE BECAUSE USER-ID ' < user-ID >' CAN NOT
UPDATE THE SCREENING FILE.
DELETE failed - User-ID can not update Screening File ''.
You are authorized only to read the specified screening file, not to update it by loading
transactions. This could only occur if the Table file changed between the time you submitted the
DELETE job and the time it executed. Contact the AIRS database administrator.
DELETE 9-16 September 1993
-------
AIRS User's Guide
Volume AQ3 Air Quality Data Storage
ERROR: THE DELETE COULD NOT BE DONE BECAUSE OF AN ADABAS ERROR. PLEASE
KEEP ALL REPORTS AND NOTIFY THE AIRS DATABASE ADMINISTRATOR.
(The rest of this message lists ADABAS parameters.)
DELETE failed - an ADABAS error occurred for JOB '< job name>'.
An error occurred for which the DELETE program can not take corrective action. Contact the
AIRS database administrator and pass along the information in the error report so the problem can
be resolved.
(No LOAD summary report is generated by the batch job.)
DELETE failed - a system error occurred for JOB ' < job name>'.
A "system error" occurred while the DELETE program was running. This type of error includes
things such as exceeding the time limit for the job or an I/O error. If neither a message nor a
DELETE summary report is generated, there may be something wrong with the JCL for the batch
job. An invalid dataset name could cause this kind of error. Contact the AIRS database
administrator or the computer center user support department for assistance if you need it. You
should determine the cause of the error before initiating DELETE again.
September 1993 9-17 DELETE
-------
AIRS User's Guide
Air Quality Data Storage Volume AQ3
9.5 DELETE Follow-Up Procedures
After the user verifies the successful completion of the DELETE process, the empty screening file is
available for processing new transactions.
You should make sure the other members of your user group are aware of which screening file you are
using and that you have deleted records from it. It is probably not advisable for two people to use the
same screening file at the same time for different sets of transactions. Keeping the other members of
your group informed of the status of your screening file may prevent usage conflicts. However, there
is no limitation on usage of a screening file inherent in the AIRS software. If you prefer to share a
screening file with other users hi your group, you can do so.
DELETE 9-18 September 1993
-------
AIRS User's Guide
Volume AQ3 Air Quality Data Storage
9.6 Restrictions, Limitations, and Warnings
You should consider the following points with respect to using the DELETE process:
1. Do not bypass the AIRS top level user session and submit a DELETE job directly, even if you are
an experienced user of the NCC. The batch part of the DELETE process depends on error checking and
other validation done in the top level user session. Bypassing that error checking could cause corruption
of your screening file or error termination of the DELETE program.
2. The user profile screen lists all the screening files you are authorized to us and indicates the status
of the files. If you select a screening file that is locked for update processing, DELETE will fail because
it can not access the screening file. Be sure you choose an appropriate screening file.
3. Be sure you execute the DELETE process for the correct screening file.
4. The screening file must be for Air Quality data only.
September 1993 9-19 DELETE
-------
AIRS User's Guide
Volume AQ3 Air Quality Data Storage
10.0 Archiving and Dearchiving Data
This section discusses the procedures for reloading (dearchiving) old raw data values into the AIRS
database so they can be updated.
10.1 Background
The AIRS database includes a huge amount of air quality data. Values have been reported by thousands
of monitors during a period of several decades. The oldest values date back to 1957. However, the
"active" part of the AIRS database contains only the raw data values for the current year and at least the
five previous years. (Data for more than five years may be active, depending on the availability of disk
space.) The older data are "archived", or removed from the online AIRS database and kept on magnetic
tape. When necessary, the old data can be "dearchived", or reloaded into the active part of the database.
If an archived year is referenced during data storage or data retrieval operations, the AIRS software
generates an error message noting that condition.
There are practical reasons for archiving old data. The cost of providing immediate access to all the
AIRS data would be prohibitive. The data for just five years includes several million values and occupies
quite a bit of disk storage space on the NCC-IBM computer system. Furthermore, there is very little
need for the old data. Most users of AIRS never need to access data more than a few years old.
Only data in the AIRS Hourly raw data file are archived at this time. The other raw data files (Daily and
Composite) are small enough that archiving has not become necessary yet. There are no plans to archive
any data from the Summary file; it will contain summary information for all reported data.
September 1993 10-1 Dearchiving Data
-------
AIRS User's Guide
Air Quality Data Storage Volume AQ3
10.2 Procedures
10.2.1 Dearchiving
If you need to alter data that have been archived, contact the AIRS database administrator. The database
administrator will need to know what year is involved and probably will want to know why it is necessary
to alter the data, since the effort and expense involved is not trivial.
When data for the year(s) you requested have been reloaded into the AIRS database, the database
administrator will contact you. Then you can complete the normal validation of the transactions with
EDIT and notification of readiness for update with NOTIFY. The validated transactions can be used in
the next update of the database.
No formal procedures have been established for how long the dearchived data can remain in the AIRS
database after the updating has been completed. You should tell the database administrator approximately
how long you will need to have the updated data available when you request the dearchiving.
10.2.2 Archiving
When you have finished using die dearchived, updated data, it must be archived again. Contact the AIRS
database administrator when you no longer need access to the dearchived data.
Dearchiving Data 10-2 September 1993
-------
AIRS User's Guide
Volume AQ3 Air Quality Data Storage
11.0 Update Processes
This section describes the AQ data storage processes used by the database administrator to update the
AIRS database.
11.1 Overview
The preceding sections have described the procedures you use to prepare transactions for updating the
AIRS database. Once you have validated your transactions and notified the database administrator they
are ready to be used, the database administrator takes control of your transactions and performs the actual
updating of the AIRS database. You can not perform an update yourself; that function is reserved for
the database administrator.
The following sections describe the processes the database administrator uses for updating the database
and for archiving and dearchiving data. The processes are SCAN, EXCLUDE, UPDATE, ARCHIVE,
and DEARCHIVE.
September 1993 11-1 Update Processes
-------
AIRS User's Guide
Air Quality Data Storage Volume AQ3
11.2 SCAN
11.2.1 Overview
The main purpose of the SCAN process is to provide the reports the AIRS database administrator uses for
planning updates and handling special transactions. The reports give an inventory of the types and numbers
of transactions in a screening file. The database administrator uses that information to determine which
screening files can be combined together in one update job. SCAN generates the following reports for each
screening file processed:
Summary Report
Detail Report
Inventory Report
Current NAMS Report
Old NAMS Report
Non-NAMS Criteria Report
Excluded SLAMS Data Report
SLAMS Report
Precision and Accuracy Report
NAMS/SLAMS Site/Monitor Update Report
The following subsections describe each of these reports. Only the SLAMS and the Precision and Accuracy
reports are routinely distributed to users, but you can obtain any of the other reports as well. Each one is
written to a disk file. You can view any of the reports on your terminal by browsing a file using the SYSD
processor discussed in Section 3. You can print a copy of any of the reports using the PRINTOFF command
available under TSO; see the NCC-1BM User's Guide for usage instructions. Table 11-1 gives the dataset
naming convention used for SCAN report files. The AIRS database administrator puts the actual names of
the available report files in dataset AIRA.NADB.MESSAGE(UPDATE). That dataset also tells how to print
a copy of a report file using the PRINTOFF command available under TSO. (There is no command available
in CICS to print a dataset. You must logon to TSO.)
Besides generating reports, SCAN also identifies transactions that need special attention and either removes
them from the screening file or sets their exclusion status so they will not be used to update the database.
The "special" transactions are: SLAMS summary transactions (types P-V); raw data transactions for a time
period covered by a record in the SLAMS summary file; and raw data transactions submitted by NAMS
monitors.
SCAN removes SLAMS transactions from a screening file, stores them in another file, and generates a
SLAMS report (described later in this section). EPA regulations require that the reporting organization
responsible for submitting the SLAMS data must review the report and approve it in writing. When the AIRS
database administrator receives written approval, he or she loads the transactions into an ADBA screening
file and uses them to update the AIRS database. To ensure there are no changes in raw data without a
corresponding change in SLAMS summary information, SCAN excludes any raw data transactions that pertain
to a time period covered by an existing SLAMS summary record, unless there is also a SLAMS transaction
in the same screening file. One of the SCAN reports identifies the transactions excluded because of conflict
Update Processes 11-2 September 1993
-------
AIRS User's Guide
Volume AQ3 Air Quality Data Storage
with SLAMS summary information. SCAN generates a report involving NAMS and SLAMS sites and
monitors to show their changes, based on a "simulated update" of the database from a screening file, for use
by the database administrator.
SCAN is a batch process. The AIRS database administrator initiates it using terminal screens for selecting
the screening file(s) to be processed and for specifying JCL parameters.
September 1993 11-3 Update Processes
-------
Air Quality Data Storage
AIRS User's Guide
Volume AQ3
Table 11-1. Dataset Names of SCAN Report Files
SCAN Report
Summary
Detail
Inventory
Current NAMS
Old NAMS
Non-NAMS
Excluded SLAMS Data
SLAMS )
)
Precision and Accuracy )
NAMS/SLAMS Site/Monitor
Update
Report File Dataset Name
AIRA.SUMMARY.yz/e-7D
AIRA.DETAILS.yj/e-7D
AIRA.INVENT.yz/e-7D
AIRA.CURNAMS.yz7e-7D
AIRA.OLDNAMS.yz/e-7D
AIRA.NONNAMS.yz/e-7D
AIRA.EXSLAMS.yz/e-7D
AIRA.SLAMS.yz/e-7D
AIRA.SMONUPD.yi/e-7D
The file-ID part of all the dataset names is the same. It has this format:
file-ID = AMPUQ.Dyymmdd.Thhmmss.sfiiame
where yymmdd and hhmmss are the date and time when the SCAN batch job was submitted and sfiiame
is the name of the screening file processed. For example, if the AIRS database administrator initiated
a SCAN of screening file R09AQA01 on October 26, 1987, at 15 seconds after 4:27 pm, the value of
file-ID would be "AMP120.D871026.T162715.R09AQA01".
The SLAMS report and the Precision and Accuracy report are both contained in the same file.
Update Processes
11-4
September 1993
-------
AIRS User's Guide
Volume AQ3
Air Quality Data Storage
09/27/93
AHP120
R
NAMS E SCREENING
CORD G ST FILE NAME
04 AL L01AQB01
09 CA L06AQA01
01 ME L23AQA01
01 ME L23AQC01
05 MI L26AQA02
09 NV L32AQA01
__ 03 PA L42AQA01
04 TN L47AQA01
088AQ001
R01AQASI
03 OE S10AQA01
10 10 S16AQA02
05 IL S17AQA02
04 KY S21AQA01
01 MA S25AQA01
OS MI S26AQA02
TOTAL
SCAN NUMBER
AEROMETRIC INFORMATION RETRIEVAL SYSTEM
AIR QUALITY SUBSYSTEM
SCAN SUMMARY REPORT
PAGEi 1
> UPDATE SCAN SCAN REPORTS WITH TRANS
: READY REMOVED EXCLUDED INFORMATION EXCLUDED
l.OSO
203.445
224
2.065
323
2.700
4.647
21
13
12
1,736
441
1,126
74
28
6,493
224.398
DATE
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
TIME
0 1 3
0 3
0 3
0 3
0 1 3
0 1 3
0 2 3
0 3
0
0
0 1 3
0 1 3
0
0 2 3
0
0 1 3
0
COST
78
78
7 8
7 8
7 8 ^
7 8 =
7 8
7 8
8
8 ^
78
7 8
6 8
6 7 8
8
7 8
CPU
Figure 11-1. The SCAN Summary Report
September 1993
11-5
Update Processes
-------
AIRS User's Guide
Air Quality Data Storage Volume AQ3
11.2.2 The SCAN Summary Report
The SCAN Summary report summarizes the screening files that SCAN processes. Figure 11-1 shows
the report format. The first column is an underlined space for the ADBA to record the initials of the
appropriate NAMS coordinator. The next two columns are region code and state abbrevation. These
columns will be underlined blank spaces except for state or local screening files, in v/hich case the EPA
region code will appear in the region column and the state abbrevation will appear in the state column.
The next column will be the screening file name. The next three columns contain a recap of transactions
from the Detail Report of each screening file. They contain transactions ready for update, transactions
which SCAN has removed, and transactions which SCAN has excluded from updating.
The next eight columns contain numbered flags for each report produced for that screening file by SCAN.
The flags correlate to the following reports:
1 Current NAMS 5 SLAMS Summary
2 OLD NAMS 6 Site Monitor
3 Non-NAMS Criteria 7 Inventory
4 Excluded SLAMS 8 Detail
The last column (TRANS EXCLUDED) will be underlined blank spaces, to allow the ADBA to enter
a number for an audit trail.
If SCAN encounters an error during processing, it prints an error report in place of the Summary Report.
The SCAN Error Report has a format like those used by LOAD and EDIT, as shown in Section 3 of this
volume (see Figures 3-16 and 3-17).
Update Processes 11-6 September 1993
-------
AIRS User's Guide
Volume AQ3 Air Quality Data Storage
08/23/93 AEROHETRIC INFORMATION RETRIEVAL SYSTEM PAGE: 1
AMP120 AIR QUALITY SUBSYSTEM
SCAN DETAIL REPORT
FOR SCREENING FILE S18AQA01
READY FOR UPDATE EDIT LEVEL USER SCAN SCAN
TRANSACTION TYPE DELETES INSERTS MODIFIES NO EFFECT TOTAL 0 1 2 EXCLUDED EXCLUDED REMOVED
SITE Al 0 2 0 0 21 00 0 0 0
SITE A2 02002000000
SITE A3 02002000000
SITE A4 0210 3 000 000
SITE AS 0200 2 000 000
SITE A6 0200 2 000.000
SITE A7 02002000000
MONITOR Fl 02002000000
MONITOR F2 02002000000
HOURLY 1 0 19.410 0 0 19.410 0 0 00 0 0
DAILY 2 1 438 0 0 439 0 0 4 112 0 0
PRECISION 8 0600 6000 000
TOTAL 1 19.872 1 0 19.874 1 0 4 112 0 0
Figure 11-2. The SCAN Detail Report
September 1993 11-7 Update Processes
-------
AIRS User's Guide
Air Quality Data Storage Volume AQ3
11.2.3 The SCAN Detail Report
The SCAN Detail Report summarizes the status of a screening file and the results of SCAN processing
of it. Figure 11-2 shows the report format. The report lists the number of transactions in each of eleven
categories. There is a line for each type of transaction in the screening file, and a column for each
category. The first five columns list the number of transactions that will be used to update the database.
Included in this category are transactions at edit level three that will delete, insert, or modify values in
the database; and transactions that passed edit checks but will have no effect on the database. (No-effect
status is not currently implemented, and this column always contains zero.). The fifth column is the total
of the previous four.
The next five columns of the summary report list the number of transactions present in the screening file
that will not be used to update the database. The first three of these columns represent transactions that
have not passed all edit checks and have edit levels of zero, one, or two. The other two columns give
the number of transactions you have excluded from update processing using CORRECT and the number
of transactions SCAN has excluded. (The SCAN-excluded transactions appear in the Excluded SLAMS
Data report.)
The last column of the report lists the number of SLAMS transactions SCAN removed from the screening
file and saved in a holding file, pending approval of the SLAMS report as described in the Overview
section.
Update Processes 11-8 September 1993
-------
AIRS User's Guide
Volume AQ3
Air Quality Data Storage
03/08/93
AMP120
SITE
330074001
330074001
330074001
330074001
330110015
330110015
330110015
330110015
330110015
330110015
330110015
330110015
330111007
330111007
330111007
330112001
330112001
330112001
330130003
330130003
330130003
330130003
330130003
330135001
330135001
330135001
330135001
330135001
330150009
330150009
330150009
330190003
MONITOR
442011
442011
442011
442011
824031
824031
824031
824031
824032
824032
824032
824032
824031
824031
824031
824031
824031
824031
824031
824031
824031
824031
824031
811021
824031
824031
824031
824031
824031
824031
824031
811021
M
T
3
3
3
3
3
3
3
3
3
3
3
3
3
3
3
3
3
3
3
3
3
3
3
3
3
3
3
3
3
3
3
3
METH
on
Oil
Oil
Oil
091
091
091
091
091
091
091
091
091
091
091
091
091
091
091
091
091
091
091
064
091
091
091
091
091
091
091
064
UNIT
008
008
008
008
001
001
001
001
001
001
001
001
001
001
001
001
001
001
001
001
001
001
001
001
001
001
001
001
001
001
001
001
I
N
T
1
1
1
1
7
7
7
7
7
7
7
7
7
7
7
7
7
7
7
7
7
7
7
7
7
7
7
7
7
7
7
7
YR
92
92
92
92
92
92
92
92
92
92
92
92
92
92
92
92
92
92
92
92
92
92
92
92
92
92
92
92
92
92
92
92
E
X
MON C
06
07
08
09
07
10
11
12
03
10
11
12
10
11
12
10
11
12
06
09
10
11
12
08
06
10
11
12
10
11
12
11
AEROMETRIC INFORMATION RETRIEVAL SYSTEM
AIR QUALITY SUBSYSTEM
SCAN INVENTORY REPORT
FOR SCREENING FILE S33AQA02
-—VALUES READY FOR UPDATE-—
DELETES INSERTS MODIFIES
PAGE:
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
510
732
730
558
5
5
5
1
6
5
5
5
5
5
5
5
5
5
4
5
5
5
5
0
5
4
5
5
5
5
5
4
..
:s
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
1
0
0
0
0
0
0
0
0
V
1ST A
MAX NMODHH L
99.79 071100
10.37 100300
99.79 110200
1.47 122600
99.88 031300
10.42 100300
3.39 112000
6.11 120200
11.68 100300
4.01 112000
6.94 120200
99.79 101500
99.79 110800
4.90 120200
4.19 062900
11.45 091500
10.63 100300
3.17 112000
5.88 120200
99.79 062300
3.17 102100
1.04 110800
4.46 120200
12.01 100300
4.78 112000
5.84 120200
V
2ND A
MAX MMODHH L
3.76 070500
4.12 100900
99.79 110800
6.03 032500
4.01 100900
1.32 110200
3.44 121400
4.37 100900
2.01 110200
3.35 122000
11.30 100300
2.39 112000
2.34 122000
1.28 061700
4.87 090900
3.63 100900
1.24 110300
3.38 121400
4. 58 062900
2.88 101500
.96 112000
1.50 122000
4.00 100900
1.68 110200
3.89 121400
V
3RD A
MAX HMDDHH L
3.20 072900
3.91 102100
99.79 112600
3.68 030100
3.77 102100
1.27 111400
3.28 122000
4.08 102100
1.43 111400
3.08 121400
3.62 100900
.96 111400
2.23 121400
.63 061100
3.97 092700
3.40 102100
1.18 111400
2.58 122000
2.25 060500
2.46 100900
.88 111400
.96 122600
3.99 102100
1.43 110800
2.90 122000
TOTAL
2.659
Figure 11-3. The SCAN Inventory Report
September 1993
11-9
Update Processes
-------
AIRS User's Guide
Air Quality Data Storage Volume AQ3
11.2.4 The SCAN Inventory Report
The SCAN Inventory report lists detailed information about the transactions in a screening file that will
update the Hourly, Daily, and Composite files of the database. Basically, this report tells the database
administrator what is in a screening file. The administrator can use that information to schedule database
updates and to avoid any potential conflicts between screening files.
Figure 11-3 shows the Inventory report format. The report has a line for each set of related transactions.
in most cases, that is the transactions for one month from a particular monitor. (If a monitor uses more
than one method during the month, there is a line for each method used.) Each line contains the same
types of information, which are identified by the column headings.
The first two columns identify the monitor-ID (state, county, site, parameter, and POC codes), and the
third column shows the monitor type. The next six columns identify the data by listing the codes for
collection/analysis method, reporting units, sampling interval, the year and month, and if it has been
excluded. The three columns in the middle of the line list the number of individual values that will be
deleted, inserted, and modified by the transactions. (The number of transactions is not listed.) The last
three groups of columns show the three highest transaction values in the month and their dates and times
of occurrence. Validity flags are shown in the columns labeled "VAL". (The maximum values are not
listed for secured monitors or if data has appeared in the Current NAMS, Old NAMS, Non-NAMS
Criteria, or Excluded SLAMS Reports.)
The last line of the report gives the total number of values to be deleted, inserted, and modified by all
the transactions in the screening file.
Update Processes 11-10 September 1993
-------
AIRS User's Guide
Volume AQ3
Air Quality Data Storage
09/27/93
AMP120
SITE MONITOR
390350045 121282
390490021 121281
390490081 121281
390610014 121281
390610035 121281
391130004 121281
391130019 121282
391530024 121281
391534002 121281
390610021 421011
390990009 424011
390990009 442011
390350013 811021
390350026 811021
390350027 811021
390350038 811021
390350045 811021
390350060 811021
390490004 811021
390490004 811021
390490024 811021
390490024 811021
390610014 811021
390610037 811021
390615001 811021
390618001 811021
390990006 811021
390990006 811021
AEROMETRIC INFORMATION RETRIEVAL SYSTEM
AIR OUAim SUBSYSTEM
SCAN CURRENT (AFTER 93/04) NAMS REPORT
FOR SCREENING FILE S39AQA01
M
T NETH
092
092
092
092
092
092
092
1 092
1 092
1 067
1 061
1 019
1 063
1 063
1 063
1 062
1 063
1 063
1 064
1 064
1 062
1 062
1 063
1 063
1 063
1 063
1 063
1 064
I 0
N T
UNIT T YR R
001 C 93 2
001 C 93 2
001 C 93 2
001 C 93 2
001 C 93 2
001 C 93 2
001 C 93 2
001 C 93 2
001 C 93 2
007 1 93 3
007 1 93 3
007 1 93 3
001 7 93 3
001 7 93 3
001 7 93 3
001 7 93 3
001 7 93 3
001 7 93 3
001 7 93 2
001 7 93 3
001 7 93 2
001 7 93 3
001 7 93 3
001 7 93 3
001 7 93 3
001 7 93 3
001 7 93 3
001 7 93 3
F
HIST L
MAX YYNMDD G
.35 9005
.19 9103
.11 8912
.08 8911
.36 9009
.09 8912
.07 8907
.15 8911 •
.17 8907
13.5 920203
.248 911220
.143 910716
183 920617
125 891025
211 891025
151 891027
140 900322
120 930618
79 900827
79 900827
95 900805 •
95 900805
104 891218
109 900803
92 891218
102 900827
138 890711
138 890711
1ST
MM
.08
.05
.03
.04
.03
.04
.04
.17
.04
4.3
.107
.089
SO
68
61
73
67
93
59
63
99
60
76
66
72
68
64
61
V L
A 0
NMOOHH L C
04
06
04
04 0
04 0
04 D
06
06
04 D
071512
071216
072516
072400
070600
070600
070500
070600
070600
062400
070600
061200
072800
070600
070600
070600
070600
072600
070600
V L
2ND A 0
MM MMDOHH L C
.08 05
.04 04
.03 05
.04 06
.03 05
.04 06
.03 04 0
.03 04 D
.03 05
3.5 070216
.08* 072218
.083 072517
68 072400
40 072400
63 070200
39 071200
43 071800
54 061800
44 072400
74 061800
52 070600
66 071800
63 071800
66 071800
50 072400
51 072800
47 071400
3RD
MM
.07
.03
.03
.03
.03
.03
.03
.03
.03
2.5
.062
.082
39
25
56
34
40
39
43
53
48
53
47
54
30
45
39
V L
A 0
NMODHH L C
06
05
06
05
06
05 D
05 ' D
05
06
070215
070516
070216
071200
071200
070900
073000
071200
040700 D
071800
050900 D
070400
072400
072400
072400
071200
072200
072000
4TH
MM
2.5
.061
.079
35
12
55
27
37
38
24
51
45
29
27
24
28
38
34
PAGE:
V L
A 0
HMODHH L C
071516
072219
071815
071800
073000
072800
072400
072400
063000
071200
062400
071800
071200
071200
071200
073000
070200
070800
TOTAL
VALUES
3
3
3
3
3
3
3
3
3
736
705
711
1
5
4
29
5
4
15
5
44
14
5
5
5
4
6
8
TOTAL
2.338
08/16/93
AMP120
AEROMETRIC INFORMATION RETRIEVAL SYSTEM
AIR QUALITY SUBSYSTEM
SCAN OLD (BEFORE 93/04) NAMS REPORT
FOR SCREENING FILE S27AQA01
PAGE:
SITE MONITOR
270530056 421011
270530954 421011
270530056 424011
270530954 424011
271230864 424011
270530953 426021
271230864 426021
270031002 442011
270531007 811021
270532006 811021
270533004 811021
271230021 811021
271230047 811021
271370027 811021
M
T METH
1 066
1 054
1 020
1 060
1 020
1 042
1 014
1 047
1 064
1 064
1 062
1 065
1 065
1 064
I Q
N T
UNIT T YR R
007 1 93 1
007 1 93 1
007 1 93 1
007 1 93 1
007 1 93 1
007 1 93 1
007 1 93 1
007 1 93 1
001 7 93 1
001 7 93 1
001 7 93 1
001 7 93 1
001 7 93 1
001 7 93 1
F
HIST L
MAX YYMMDD G
15.0 891024
8.9 900308
.053 910118
.130 920408
.077 910723
.179 920728
.108 910502
.112 890704
134 900111
99 900111
134 900111
148 920611
192 891024
105 920212
1ST
MAX
7.7
5.7
.026
.053
.036
.104
.081
.085
54
59
91
49
89
54
V L
A 0
MMDDHH L C
030221
030221
012012
031503
010112
030223
030222
030214
030200
030200
030200
010700
031800
032600
V L
2ND A 0
MAX MMDDHH L C
5.5 030220
5.7 032407
.026 030412
.051 031504
.032 012012
.102 030222
.073 030223
.085 030215
42 032600
36 032600
56 010700
41 012500
81 031900
26 030200
3RD
MAX
5.1
5.1
.026
.040
.026
.095
.071
.077
28
30
54
35
70
23
V L
A 0
MMDOHH L C
032901
011116
030413
031502
010113
030218
030509
030216
012500
012500
032600
021800
032300
032000
4TH
MAX
4.8
5.0
.024
.038
.026
.093
.069
.075
25
26
52
35
58
22
V L
A 0
MMDDHH L C
032900
010817
022517
031507
022510
030219
030220
030213
010700
010700
011900
022400
032900
011900
TOTAL
VALUES
2,114
2.118
2.107
2.117
2.110
2.100
2.064
2.110
15
15
15
10
31
11
TOTAL
16.937
Figure 11-4. The SCAN Current and Old NAMS Reports
September 1993
11-11
Update Processes
-------
AIRS User's Guide
Air Quality Data Storage Volume AQ3
11.2.5 The SCAN Current and Old NAMS Reports
The SCAN "Current NAMS" and "Old NAMS" reports list information about the raw data values in the
screening file reported by NAMS monitors. Figure 11-4 shows the report formats, which are identical
except for the report title. The "current" report pertains to values measured in the current or the previous
calendar quarter; the "old" report pertains to values measured before that. (The AIRS database
administrator can specify a different cutoff date for SCAN to use instead of the default, which is the first
month of a quarter 120 days before the current month. The cutoff date in effect is listed in the page
heading of the two NAMS reports.)
SCAN generates two separate NAMS reports because EPA is concerned about the timeliness with which
NAMS monitors submit data and the quality of the data submitted. The "current" report includes data
submitted by NAMS monitors within the time period EPA considers reasonable. The transactions
referenced by the "current" report are processed normally to update the database. The transactions
referenced by the "old" report are tardy, and EPA wants to give them special attention before allowing
them to update the database.
The NAMS reports have an organization similar to the Inventory report. There is a line in the report for
each related set of values measured by a NAMS monitor. The first two columns identify the monitor,
and the next six columns (monitor type, method, units, interval, year, and quarter) list the items that
define the related set. The next three columns contain the historical maximum value for the previous four
years and the previous quarters of the current year, the date it occurred, and a flag. The historical
maximum flag will show an "*" if any data in the Screening File has a greater value than the current
historical maximum. A "D" will show if the historical maximum will be deleted by a delete transaction
from the Screening File. An "M" will show if the historical maximum is being modified by a tranaction
from the Screening File. The historical maximum flag will be blank if there is no change to the historical
maximum. The next four groups of columns list the four highest values for the set, the date and time
when they occurred, the validity flag, and the origin of the value. If the "LOC" (location) column
contains "D", the value is in the database. Otherwise, the value is in the screening file. The last column
of the report lists the number of values that will be deleted, inserted, and modified for the quarter by the
transactions in the related set, after the simulated update has been completed. If the total value count is
zero, all values for the quarter are being deleted. (The number of transactions is not listed.) The last
line of the report gives the total number of values affected by all the transactions referenced in the report.
In order to produce the NAMS reports, SCAN does a "simulated update". That is, SCAN retrieves any
existing values for the pertinent monitor and quarter from the database and applies the transactions in the
screening file to determine the resulting state of the data, just as if UPDATE had processed the
transactions. Having done that, SCAN finds the four highest values and indicates in the report whether
each one came from the transactions or the database. This is particularly important in the "old" report,
as it helps the database administrator identify transactions that may significantly alter previously reported
data.
Update Processes 11-12 September 1993
-------
AIRS User's Guide
Volume AQ3 Air Quality Data Storage
09/27/93 AEROMETRIC INFORMATION RETRIEVAL SYSTEM PAGE: 1
AMP120 AIR QUALITY SUBSYSTEM
SCAN NON'NAMS CRITERIA REPORT
FOR SCREENING FILE S46AQA01
[Q F VL V L VL VL
M NT HIST L 1ST A 0 2ND A 0 3RD A 0 4TH A 0 TOTAL
SITE MONITOR T METH UNIT T YR R MAX YYMMOO G MAX MMDDHH L C MAX HMODHH L C MAX MMOOHH L C MAX MHDOHH L C VALUES
460110002 811021 2 063 001 7 93 2 89.0 901002 21.5 061200 17.8 041300 17.8 052600 17.4 041900 16
460990004 811022 2 063 001 7 93 2 114.0 890422 19.2 040700 17.2 041900 15.0 051300 13.2 061200 IS
460990006 811021 2 063 001 7 93 2 64.0 910828 34.3 041900 20.9 040700 20.8 051300 20.1 051900 IS
461030002 811022 2 063 001 7 93 2 136.0 910205 34.1 041600 24.4 050700 23.1 051300 23.1 051900 31
461030012 811022 2 063 001 7 93 2 145.0 920204 77.9 042300 67.0 040900 62.8 051700 59.0 042700 46
461030013 811021 3 063 001 7 93 2 137.0 930302 63.7 051700 59.0 042300 36.7 062400 36.1 052700 41
461031001 811022 2 063 001 7 93 2 174.0 911211 81.4 040800 77.2 041600 54.8 042300 50.3 040900 86
TOTAL 250
Figure 11-5. The SCAN Non-NAMS Criteria Report
September 1993 11-13 Update Processes
-------
AIRS User's Guide
Air Quality Data Storage Volume AQ3
11.2.6 The SCAN Non-NAMS Criteria Report
The SCAN Non-NAMS Criteria Report lists information about the raw data values in the screening file
reported by non-NAMS monitors concerning the criteria pollutants and TSP.
The Non-NAMS Criteria Report has a format identical to the two NAMS reports that SCAN generates.
The first eight columns identify the data by listing the reporting monitor, monitor type, method, units,
interval, and the year and quarter. The next three columns contain the historical maximum value for the
prevous four years and the previous quarters of the current year, the date it occurred, and a flag. The
historical maximum flag will show an "*" if any data in the Screening File has a greater value than the
current historical maximum. A "D" will show if the historical maximum will be deleted by a delete
transaction from the Screening File. An "M" will show if the historical maximum is being modified by
a transaction from the Screening File. The flag will be blank if there is no change to the historical
maximum. The next four groups of columns list the four highest values, when they occurred, their
validity flags, and their origin (screening file or database). The last column lists the number of values
affected by the transactions. The value is the number for the quarter after the simulated update has been
completed. If the total value is zero, all values for the quarter are being deleted. The report has one line
for each monitor-quarter and the last line of the report gives the total number of values involved.
Update Processes 11-14 September 1993
-------
AIRS User's Guide
Volume AQ3 Air Quality Data Storage
09/27/93 AEROMETRIC INFORMATION RETRIEVAL SYSTEM PAGE:
AMP120 AIR QUALITY SUBSYSTEM
SCAN EXCLUDED SLAMS DATA REPORT
FOR SCREENING FILE S35AQA02
SITE
350010008
350010022
350010023
M
MONITOR T
811021 2
811022 1
811021 2
NETH UNIT
063 001
064 001
063 001
I Q
N T
T YR R
7 92 2
7 92 2
7 92 2
F
HIST L
MM YYMMDD G
74 891124
77 880128
100 890621
1ST
MAX
47
33
36
V L
A 0
MMDDHH L C
043000 D
061700 D
062300 D
V L
2ND A 0
MAX NHDDHH L C
45 062300 D
31 062300 D
31 061100 D
V L
3RD A 0
MAX MMDDHH L C
41 061700 0
30 043000 0
29 041200 D
4TH
MAX
30
29
29
V L
A 0
MMDDHH L C
061100 D
042400 D
041800 D
TOTAL
VALUES
]
1
1
14
13
14
TOTAL -. 41
Figure 11-6. The SCAN Excluded SLAMS Data Report
September 1993 11-15 Update Processes
-------
AERS User's Guide
Air Quality Data Storage Volume AQ3
11.2.7 The SCAN Excluded SLAMS Data Report
The SCAN Excluded SLAMS Data report identifies data that SCAN marked as excluded because of
possible conflicts between raw data and SLAMS summary data. Figure 11-6 shows the report format.
The SLAMS file of the AIRS database contains an annual summary of the data reported by each SLAMS
and NAMS monitor. The reporting organization responsible for a monitor must certify the accuracy of
that summary information before it is put into the SLAMS file. Any transactions that alter the raw data
for which the summary is based could cause the summary to change, too. Therefore, if SCAN finds raw
data transactions in a screening file that pertain to a monitor and year for which a SLAMS summary
record exists, and if there is not also a SLAMS transaction in the screening file for updating the summary
information, then SCAN marks the raw data transactions as excluded. The excluded transactions can not
be used to update the database until the appropriate SLAMS transactions have been added to the screening
file.
The Excluded SLAMS Data report has a format identical to the two NAMS reports that SCAN generates.
The first eight columns identify the data by listing the reporting monitor, monitor type, method, units,
and interval, and the year and quarter (see Figure 11-6). The next four groups of columns list the four
highest values, when they occurred, their validity flags, and their origin (screening file or database). The
last column lists the number of values affected by the transactions. The report has one line for each
monitor-quarter, and the last line of the report gives the total number of values involved.
Update Processes 11-16 September 1993
-------
AIRS User's Guide
Volume AQ3
Air Quality Data Storage
02/22/93
ANP120
EPA AEROMETRIC INFORMATION RETRIEVAL SYSTEM (AIRS)
AIR QUALITY SUBSYSTEM
SCAN SLAMS REPORT
FOR SCREENING FILE S45AQA02
PAGE:
LEAD UG/CU.METER
1992
45 SOUTH CAROLINA
SITE-ID
PARAMETER POC
STREET ADDRESS
CITY
EXCEPTIONAL
EVENTS
DATA
SAMPLING
INTERVAL
--1ST
QUARTER--
NUMBER ARITH
DBS
MEAN
--2NO QUARTER--
NUMBER ARITH
DBS MEAN
-3RD
QUARTER-
NUMBER ARITH
DBS
MEAN
— 4TH
QUARTER-
NUMBER ARITH
DBS
MEAN
CHARLESTON CO
45-019-0001 12128 2
CHARLESTON COUNTY HEALTH OEPAR
CHARLESTON
45-019-0003 12128 2
JENKINS ST. FIRE STATION
NORTH CHARLESTON
GEORGETOWN CO
45-043-0001 12128 1
GEORGETOWN COUNTY HEALTH DEPT
GEORGETOWN
16
.017
14
.031
15
.018
REPORT ORG: 001 - SOUTH CAROLINA DEPARTMENT HEALTH AND ENVIRONMENTAL CO
METHOD(S): 092 - HI-VOL ATOMIC ABSORPTION
16
.009
15
.010
14
.009
REPORT ORG: 001 - SOUTH CAROLINA DEPARTMENT HEALTH AND ENVIRONMENTAL CO
METHOO(S): 092 - HI-VOL ATOMIC ABSORPTION
16
.022
15
.013
14
.025
REPORT ORG: 001 - SOUTH CAROLINA DEPARTMENT HEALTH AND ENVIRONMENTAL CO
METHOD(S): 092 - HI-VOL ATOMIC ABSORPTION
15
11
15
.020
.006?
.012
02/22/93
AMP120
NOTE: A MEAN VALUE FOLLOWED BY *?* WAS COMPUTED FROM OBSERVATIONS THAT DID NOT MEET SUMMARY CRITERIA.
EPA AEROMETRIC INFORMATION RETRIEVAL SYSTEM (AIRS) PAGE:
AIR QUALITY SUBSYSTEM
SCAN SLAMS REPORT
FOR SCREENING FILE S45AQA02
SITE-ID PARAMETER POC
STREET ADDRESS
CITY
" LEAD UG/CU. METER 1992
EXCEPTIONAL -1ST QUARTER-
EVENTS SAMPLING NUMBER ARITH
DATA INTERVAL OBS MEAN
45 SOUTH CAROLINA "
-2ND QUARTER- --3RD QUARTER-
NUMBER ARITH NUMBER ARITH
OBS MEAN OBS MEAN
-4TH QUARTER-
NUMBER ARITH
OBS MEAN
45-045-0008 12128 1
GREENVILLE HEALTH DEPT - 110 T
GREENVILLE
45-045-1002 12128 3
PARKER FIRE STATION (SEWAGE AN
GREENVILLE
45-045-2002 12128 1
PUBLIC WORKS BUILDING
GREER
15
.015
12
.006
15
.018
REPORT ORG: 001 - SOUTH CAROLINA DEPARTMENT HEALTH AND ENVIRONMENTAL CO
METHOD(S): 092 - HI-VOL ATOMIC ABSORPTION
15
.011
12
.007
15
.023
REPORT ORG: 001 - SOUTH CAROLINA DEPARTMENT HEALTH AND ENVIRONMENTAL CO
METHOD(S): 092 - HI-VOL ATOMIC ABSORPTION
15
.008
30
.007
30
.014
REPORT ORG: 001 - SOUTH CAROLINA DEPARTMENT HEALTH AND ENVIRONMENTAL CO
METHOD(S): 092 - HI-VOL ATOMIC ABSORPTION
15
13
20
.003
.011
.013
NOTE: A MEAN VALUE FOLLOWED BY T WAS COMPUTED FROM OBSERVATIONS THAT DID NOT MEET SUMMARY CRITERIA.
Figure 11-7. The SCAN SLAMS Report
September 1993
11-17
Update Processes
-------
AIRS User's Guide
Air Quality Data Storage Volume AQ3
11.2.8 The SCAN SLAMS Report
The SCAN SLAMS report lists the values contained in SLAMS transactions in the screening file. This
report is distributed to the reporting organization, which must review the data, certify that it is correct
by signing the report, and return the signed report to the AIRS database administrator. (The certification
is mandated by EPA regulations.) After receiving the signed certification, the AIRS database
administrator uses the SLAMS transactions to update the SLAMS summary file of the database. SCAN
removes the transactions from the screening file and writes them in a holding file at the time it generates
the SLAMS report. The database administrator reloads the transactions from the holding file in order
to use them in an update. This prevents accidental alteration or deletion of the transactions and ensures
that the values appearing in the certified report are the same ones used to update the database.
SLAMS summary data are reported only for monitors sampling criteria pollutants. The specific items
reported vary from pollutant to pollutant. Because of the disparity in items reported, the SLAMS report
has a different format for each pollutant. The report at the top of Figure 11-7 shows one of the formats.
The SCAN-generated SLAMS report has the same format as the SLAMS report available in the AQ
Retrieval Subsystem. Refer to Volume AQ4 of the AIRS User's Guide for samples of all the report
formats and a description of report contents.
The SCAN-generated SLAMS report includes only the data from SLAMS transaction in the screening
file; it does not use any data from the SLAMS file of the database. When a SLAMS transaction has an
action code of "delete", the SLAMS report does not show any values for that monitor. This is illustrated
in the report at the bottom of Figure 11-7.
It is possible to have two report entries for the same monitor: one for a delete transaction which has no
values listed, and another entry listing the values from an insert transaction. (Note that using just a
modify transaction would accomplish the same thing.)
Update Processes 11-18 September 1993
-------
AIRS User's Guide
Volume AQ3
Air Quality Data Storage
02/22/93
AHP120
REGIONi 04 STATEi SOUTH CAROLINA (45)
AEROMETRIC INFORMATION RETRIEVAL SYSTEM PAGE: 1
AIR QUALITY SUBSYSTEM
SCAN PRECISION AND ACCURACY REPORT
FOR SCREENING FILE S4SAQA02
AGENCY: SOUTH CAROLINA DEPARTMENT HEALTH AND ENVIROHM TYPE: AUTOMATED ANALVZERS(C)
PRECISION DATA
t I PREC PROB LIMIT
PARAMETER
CARBON MONOXIDE
SULFUR DIOXIDE
NITROGEN DIOXIDE
OZONE
PM10 TOTAL 0-10UH
(42101)
(42401)
(42602)
(44201)
(81102)
YR
92
92
92
92
92
ANALS
2
5
4
17
1
CHECKS
47
120
79
382
3
LOU
-11
-14
-18
-10
+05
UP
+13
+12
+15
+10
+08
LEVEL123 L
30
93
S3
290
1
EVEL*
0
0
0
0
0
—ACCURACY DATA
PROBABILITY LIMITS FOR
» AUDITS LEVEL1 LEVEL2 LEVELS LEVEL4
LOW UP LOU UP LOW UP LOW UP
-07 +04 -01 +04 -03 +07
-05 +03 -02. +03 -04 +01
-05 +03 -08 +03 -03 +02
-03 +03 . -03 +03 -03 +02
02/22/93
AMP120
REGION: 04 STATE: SOUTH CAROLINA (45)
AEROMETRIC INFORMATION RETRIEVAL SYSTEM PAGE:
AIR QUALITY SUBSYSTEM
SCAN PRECISION AND ACCURACY REPORT
FOR SCREENING FILE S45AQA02
AGENCY: SOUTH CAROLINA DEPARTMENT HEALTH AND ENVIRONM TYPE: MANUAL METHODS(I)
PARAMETER
LEAD (TSP)
PM10 TOTAL 0-10UM
(12128)
(81102)
YR
92
92
I COLL
SAMPS SITES
87 2
44
---PRECISION DATA
PROB LIMIT COLL SAHPS VAL COLL
LOU UP BELOW LIMIT DATA PAIRS
ACCURACY DATA
---PROBABILITY LIMITS FOR--
LEVEL1 LEVEL2 LEVEL3
AUDITS LOU UP LOW UP LOU UP
1 -05 +09
86
20
1
24
33
113
•04 +03
-03 +02
-01 +05
Figure 11-8. The SCAN Precision and Accuracy Report
September 1993
11-19
Update Processes
-------
AIRS User's Guide
Air Quality Data Storage Volume AQ3
11.2.9 The SCAN Precision and Accuracy Report
The SCAN Precision and Accuracy report gives information about the precision and accuracy of monitors
appearing in the SCAN-generated SLAMS report. Tne Precision and Accuracy report is distributed with
the SLAMS report to the reporting organizations responsible for submitting SLAMS summary data. The
information provided by the report may be helpful in evaluating the "goodness" of the SLAMS data.
The Precision and Accuracy report has two formats, for "continuous" and "intermittent" data. Figure
11-8 shows a sample of each format. The SCAN-generated Precision and Accuracy report has the same
format as the Precision and Accuracy report available in the AQ Retrieval Subsystem of AIRS. Refer
to Volume AQ4 of the AIRS User's Guide for a description of the report format. The report gives the
collective precision and accuracy of all the monitors of a particular type within the purview of a reporting
organization. The precision and accuracy of individual monitors is not available in AIRS.
Update Processes 11-20 September 1993
-------
AIRS User's Guide
Volume AQ3
Air Quality Data Storage
06/13/93
AHP120
AEROHETRIC INFORMATION RETRIEVAL SYSTEM
AIR QUALITY SUBSYSTEM
SCAN NAMS/SLAMS SITE/MONITOR UPDATE REPORT
FOR SCREENING FILE L23AQBSI
PAGE: 1
MONITOR: 230070004811022 ACTION CODE: M MONITOR TYPE: 2
FIELD IDENTIFIER NEW FIELD VALUE
OLD FIELD VALUE
DATE-SAMPLING-ENDED
930331
MONITOR: 230070004811023 ACTION CODE) I MONITOR TYPE: 2
MONITOR-TYPE
DATE-TYPE-EFF
ANALYZ-LAB
COLLECT-LAB
REPORT-ORG
RO-EFFECTIVE-DATE
DATE-SAMPLING-BEGAN
PROJECT-CLASS
HONITOR-COMMENTS-1
MONITOR-COMMENTS-2
SITE-CRITERIA-HET
DATE-SITE-CRITERIA'MET
WORST-SITE
NUM-SCH-SAMPLE-MO (01)
NUM-SCH-SAMPLE-MO (02)
NUM-SCH-SAMPLE-MO (03)
NUM-SCH-SAMPLE-MO (04
NUM-SCH-SAMPLE-MO
NUM-SCH-SAMPLE-MO
NUM-SCH-SAMPLE-MO
NUM-SCH-SAMPLE-MO
NUM-SCH-SAMPLE-MO
NUM-SCH-SAMPLE-MO
NUM-SCH-SAMPLE-MO (11)
NUM-SCH-SAMPLE-MO (12)
REQ-SAMPLING-FREQ-ST
RSF-EFFECTIVE-OATE-ST
SHORT-TERM-SCH-SAT-ST
FIRST-EXCEED-CORRECTION-ST
PROBE-LOCATION-CODE
PROBE-HEIGHT
HORIZONTAL-DISTANCE
VERTICAL-DISTANCE
UNRESTRICTED-AIR-FLOW
2
930401
116
116
103
930401
930401
02
PRIMARY AND COLLOCATED WEDDING SAMPLERS REPLA
ANDERSON SAMPLER ON APRIL 1 1993
Y
9304
1
10
10
10
10
10
10
10
10
10
10
10
10
3
930401
N
N
1
004
1
1
Y
Figure 11-9. The SCAN NAMS/SLAMS Site/Monitor Update Report
September 1993
11-21
Update Processes
-------
AIRS User's Guide
Air Quality Data Storage Volume AQ3
11.2.10 The SCAN NAMS/SLAMS Site/Monitor Update Report
The SCAN NAMS/SLAMS Site/Monitor Update report lists information about the NAMS and SLAMS
site and monitor changes. This report tells the database administrator what is in a screening file that
affects NAMS and SLAMS site and monitor records in the Site file. The administrator can use that
information to determine how these sites and monitors are being changed.
Figure 11-9 shows the NAMS/SLAMS Site/Monitor Update report format. The report first lists
information that identifies the site or monitor affected, the action to be taken, and the type of site or
monitor affected.
After listing site or monitor identification information, the report lists the identity of each site or monitor
field affected, the new value of the field, and the old value of the field. For a deletion of an existing site
or monitor, no new or old site or monitor fields are listed. For an insertion of a new site or monitor,
the valued new site or monitor fields are listed. For a modification of an existing site or monitor, the
valued new and old modified site or monitor fields are listed.
In order to produce this report, SCAN does a "simulated update". That is, SCAN retrieves any existing
information for the pertinent site or monitor from the database and applies the site or monitor transactions
in the screening file to determine the resulting state of the site or monitor, just as if UPDATE had
processed the transactions.
Update Processes 11-22 September 1993
-------
AIRS User's Guide
Volume AQ3 Air Quality Data Storage
11.3 EXCLUDE
The EXCLUDE process allows the AIRS database administrator to selectively exclude some transactions
in a screening file from update processing, or to de-exclude transactions excluded by SCAN. The
exclusion status set by EXCLUDE is different from the exclusion status you as a user can set with
CORRECT. EXCLUDE's exclusion status is automatically cleared (removed) by UPDATE;
CORRECTS exclusion status is not.
The primary purpose for EXCLUDE is to reverse the exclusion of transactions done by SCAN. The
database administrator would normally do this after determining that the SCAN-excluded transactions are
ready to be used to update the database. At the request of the coordinator for NAMS data, the database
administrator also uses EXCLUDE to exclude transactions for NAMS monitors that have questionable
data values. EXCLUDE sets or clears the exclusion status of raw data transactions (types 1, 2, and 3
for hourly, daily, and composite data), and associated minimum detectable (type Z) and null value (type
4) transactions. It does not affect site (types A-D), monitor (types F-I), or SLAMS (types P-V)
transactions.
EXCLUDE may be used either online or in batch. To use it in batch, the database administrator specifies
exclusion or de-exclusion criteria and JCL parameters using terminal screens, then submits a batch job.
September 1993 11-23 Update Processes
-------
AIRS User's Guide
Air Quality Data Storage Volume AQ3
11.4 ARCHIVE and DEARCHIVE
The AIRS database administrator uses the ARCHIVE process to remove data from the raw data files, and
uses the DEARCHIVE process to restore the archived data to the database. Both are batch processes.
As explained in Section 10 of this volume, it is necessary to archive data from the AIRS database because
there is too much data to keep online all the time. The ARCHIVE process allows the database
administrator to remove all the data for a year from any one of the raw data files of the database. The
ARCHIVE program extracts data for the selected year from the Hourly, Daily, or Composite file and
writes it to magnetic tape. The program also changes the control information in the Table file to indicate
the data for that year is archived. After the tape of extracted data has been validated, an AD ABAS utility
program deletes the archived records from the raw data file. (The record deletion is done by the central
database administrator at the request of the AIRS database administrator.)
The procedure for de-archiving data is the reverse of the procedure for archiving. First, the central
database administrator, at the request of the AIRS database administrator, loads data from one of the
archive tapes into the appropriate file of the database. Then, after verifying that the data were loaded
successfully, the AIRS database administrator changes the control information in the Table file to indicate
that the data for that year have been de-archived and are available online.
Both ARCHIVE and DEARCHIVE generate simple reports that summarize what was done and list the
names of the files involved.
The AD ABAS utility program that deletes or loads data must have exclusive use of the affected database
file. Therefore, the ARCHIVE and DEARCHIVE processes are usually scheduled to run late at night
when usage of the database is minimal.
Update Processes 11-24 September 1993
-------
AIRS User's Guide
Volume AQ3
Air Quality Data Storage
09/07/93
AMP160
SITE MONITOR
•OU-
ST RO PARK
471570043 12128 1
471S70043 12128 1
471570043 42401 1
471570043 42401 1
TOTAL
QTR
1
AEROMETRIC INFORMATION RETRIEVAL SYSTEM
AIR QUALITY SUBSYSTEM
UPDATE DETAIL REPORT
FOR SCREENING FILE ANAD8A99
SUMMARY
....DATA VALUES UPDATED SLAMS RECORDS UPDATED— RECORDS
DELETES INSERTS MODIFIES DELETES INSERTS MODIFIES UPDATED
93
93
93 1
93
UPDATE
TOTAL
1
1
1
3
PAGE:
1ST
SCAN EXC
EXCLUDED CORR
0
0
0
0
09/30/93
AMP160
AEROMETRIC INFORMATION RETRIEVAL SYSTEM
AIR QUALITY SUBSYSTEM
UPDATE SUMMARY REPORT
PAGE:
FILE NAME
L01AQB01
L06AQA01
L23AQA01
L23AQC01
L26AQA02
L32AQA01
L42AQA01
L47AQA01
088AQ001
R01AQASI
S10AQA01
S16AQA02
S17AQA02
S21AQA01
S25AQA01
S26AQA02
S30AQA01
S31AQA01
S35AQA02
S36AQA02
S37AQA02
S38AQA02
S39AQA01
DELETES
0
0
0
0
0
0
0
0
0
0
0
0
0
532
0
0
22
0
0
0
0
0
0
rnkvcj urimiu
INSERTS
7.333
1.574,685
1,447
15,210
326
19.529
33.221
19
13
0
11.448
445
1.194
0
0
46,777
20,008
230
62.180
673,331
11.605
54.812
5,614
MODIFIES DE
0
13
0
0
0
0
0
0
0
0
0
0
0
0
0
2.120
0
0
0
0
0
0
5
SLAMS RECORDS UPDATED
LETES INSERTS MODIFIES
dunnnni
RECORDS
UPDATED
25
221
2
23
37
18
67
1
2
0
33
54
124
11
0
78
49
44
75
98
63
49
101
UPDATE
TOTAL
7.358
1,574.919
1.449
15.233
363
19.547
33.288
20
15
0
11.481
499
1,318
543
0
48,975
20,079
274
62,255
673,429
11.668
54,861
5,720
SCAN UPDATED
EXCLUDED
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
279
6
0
0
0
FROM
1,050
203.457
224
2.065
323
2,700
4.647
21
13
12
1,736
441
1.126
74
28
6.493
3.788
218
8.138
90.158
2.063
7.365
1,488
TOTAL
554 2.539.427
2,138
1,175 2,543,294
285
337,628
Figure 11-10. The UPDATE Detail and Summary Reports
September 1993
11-25
Update Processes
-------
Air Quality Data Storage
AIRS User's Guide
Volume AQ3
09/02/93
AMP160
AEROMETRIC INFORMATION RETRIEVAL SYSTEM
AIR QUALITY SUBSYSTEM
VENTURA COUNTY APCO
INVENTORY REPORT
FOR SCREENING FILE L06AQB03
I
PAGE:
SITE
061112002
061113001
061113001
061113001
061113001
061113001
061113001
061113001
061113001
061113001
061113001
061113001
061113001
061113001
061113001
061113001
061113001
061113001
061113001
MONITOR
431021
421011
426021
426021
426021
426021
426021
426021
426021
426021
426021
426021
426021
426021
426021
426021
426021
442011
611021
TRANS
TYPE
MONITOR
MONITOR
MONITOR
HOURLY
HOURLY
HOURLY
HOURLY
HOURLY
PRECISION
HOURLY
PRECISION
HOURLY
PRECISION
HOURLY
PRECISION
HOURLY
PRECISION
MONITOR
MONITOR
MON
TYPE
2
2
2
2
2
2
2
2
2
2
2
2
2
2
2
2
2
1
2
METH
014
014
014
014
014
035
014
035
014
035
014
03S
014
035
UNIT
007
007
007
007
007
007
007
007
007
007
007
007
007
007
N
T YR
1 82
1 64
1 85
1 86
1 87
1 87
1 88
1 88
1 69
1 89
1 90
1 90
1 91
1 91
MON
02
02
01
09
01
01
01
01
01
04
01
01
01
01
DATA VALUES UPDATED —
DELETES INSERTS MODIFIES
TOTAL
2
1
3
1
5
1
3
1
3
1
1
30
Figure 11-11. The UPDATE Inventory Report
Update Processes
11-26
September 1993
-------
AIRS User's Guide
Volume AQ3 Air Quality Data Storage
11.5 UPDATE
UPDATE is one of the key processes of AIRS. It uses the validated, non-excluded transactions in a
screening file to update the AIRS database.
UPDATE is a batch process that only the AIRS database administrator can use. Like the other batch
processes of the AQ data storage subsystem, UPDATE is initiated using terminal screens for
specifying options and JCL parameters. One of the main options the database administrator specifies
is which screening file(s) UPDATE will process. (The information derived from SCAN helps the
database administrator decide which files to choose.)
UPDATE processes each screening file separately. It uses every transaction in a screening file that is
not excluded and has edit level 3 to update the Site file, SLAMS file, or raw data files of the AIRS
database. Based on the action code of a transaction, UPDATE deletes, inserts, or modifies values in
the appropriate file. When some fields of the Site file are changed, UPDATE generates historical
records in that file that can be used to track when and how those fields were changed. When
UPDATE changes any fields of the raw data files, it automatically updates the corresponding
information in the Summary file. After using transactions to update the database, UPDATE deletes
them from the screening file. It also de-excludes any transactions that were excluded by SCAN or
EXCLUDE. It does nothing with transactions that you excluded using CORRECT or with
transactions having edit levels less than 3.
After processing all the transactions in a screening file, UPDATE unlocks it so you can use it again.
UPDATE also stores the current date and time as the date of last update in the screening file used for
updating and in all the other screening files belonging to the same group. (All screening files whose
names begin with the same six letters are in the same group.) Finally, UPDATE creates a message
stating when the update was done and how many raw data values were deleted, inserted, and
modified. (If there were no raw data transactions in your screening file, the value count will be zero.
This does not mean the update failed, just that it did not affect any raw data values.) You can
"receive" the message using the MESSAGE process, described in an earlier section of this volume.
UPDATE generates three reports that annotate the processing performed: the Detail report, the
Summary report, and the Inventory report. Figures 11-10 and 11-11 show their formats. (The
database administrator does not normally distribute the reports to users, but you can request a copy of
the Detail report for your screening file if you want it.)
UPDATE generates a separate Detail report for each screening file processed. This report lists the
number of data values and database records updated (or the number of SCAN-excluded transactions
that were de-excluded) for each monitor in the screening file having transactions at edit level 3. A
line of the report that has a non-blank value in the QTR column gives the number of values deleted,
inserted, and modified in the raw data files and the number of transactions that were excluded from
UPDATE processing (by SCAN or EXCLUDE). A line of the report in which the QTR column is
blank gives the number of records updated in the SLAMS file and the Summary file. The UPDATE
TOTAL column gives the total number of database records affected by the update counts in that line.
The 1ST EXC CORR column gives a flag Y (Yes) or blank (no change necessary) to indicate whether
the first exceedance correction for the state or EPA needs to be changed to Y (Yes).
September 1993 11-27 Update Processes
-------
AIRS User's Guide
Air Quality Data Storage Volume AQ3
The UPDATE Summary report contains one line for each screening file processed during an
UPDATE job. It lists the same numeric information as the Detail report, but gives counts at the
screening file level instead of the monitor level.
If the data was submitted from a screening file belonging to a California local agency, UPDATE
generates an Inventory report for transactions that were updated to the database. If the screening file
submitted for update is a California local agency screening file, UPDATE generates a message for at
least two USER-IDs that are specified when the update is submitted and also generates a sequential
file of transactions in AIRS input format.
Update Processes 11-28 September 1993
-------
AIRS User's Guide
Volume AQ3 Air Quality Data Storage
12.0 BROWSE Screening File Transaction Generate Option
The BROWSE process of AIRS allows the user to selectively retrieve data from the AQ files by data
type, e.g., site. Online field-by-field Help is available to the user; it provides lists of selection criteria
field values from which the user may select. Two BROWSE programs, BROWSE Site and BROWSE
Monitor, can be used to create site or monitor AIRS Input Transactions and add them to the user's
screening file. This section describes how to use BROWSE to generate these transactions. Figure 12-1
contains a data flow diagram for the BROWSE process.
12.1 Overview
The BROWSE process screening file transactions may be created directly from Browse Data Display
screens. Currently this option is limited to the Site and Monitor data types. This feature is not meant,
in any way, to replace the CORRECT function of the Air Quality Subsystem. The extensive edits of the
CORRECT function are not available while in Browse. The CORRECT function should be used to "fine
tune" and correct any transactions generated in this way. As with CORRECT, any existing transactions
in the screening file that are related to the transactions that you generate will have their edit level flags
reduced to 1, if these flags are greater than 1.
Figure 12-2 shows the BROWSE/Generate processing flow. If the Transaction Generate Option was
selected on the Browse Data Types Screen (Figure 12-3) and a screening file was selected, the Screening
File Transaction Generate Option is enabled. If a screening file was not initially selected from the User
Profile Screen, the Screening File Selection Screen (Figure 12-4) will appear. A window for entering
a password will appear if necessary.
The Transaction Generate Option produces AIRS input Site transactions if Browse Site was selected; it
produces Monitor transactions if Browse Monitor was selected. It prompts the user to select an Action
Code for the transactions (Insert, Modify, or Delete). For Insert transactions, it prompts for a new Site
or Monitor ID. The new transactions are placed in the screening file that the user selected.
September 1993 12-1 BROWSE
-------
Air Quality Data Storage
AIRS User's Guide
Volume AQ3
Menus
BROWSE
Screens
Top Level
User
Session
T
AMP500
BROWSE
Prop-am
Figure 12-1. BROWSE Data Flow Diagram
BROWSE
12-2
September 1993
-------
AIRS User's Guide
Volume AQ3
Air Quality Data Storage
Cat*
T«*
Selection
1
Screening
Pile
Selection
AIRS-
TaOle
-G-
Record
AIRS- Table
File
f^M-fm-ft
HvC^ra
V S
Selection
O-tterla
Screene
\
Selection
Crltsrle
Entry/
Va 1 Idol 1 on
Help
Dots
01 delay/Modify
Screens
Data Display/
Modify/
Generate
AM-Slte,
Monitor
Figure 12-2. BROWSE/Generate Processing
September 1993
12-3
BROWSE
-------
AIRS User's Guide
Air Quality Data Storage Volume AQ3
12.2 Detailed Instructions
This section describes how to use the Transaction Generate option.
12.2.1 Selecting a Screening File
, Before you can generate transactions, you must first enter the correct password and select the screening
file into which the transactions are to be generated. You may do so at two separate points in the
Transaction Generate process:
1) The first point at which you may enter the password and select a screening file is on the User
Profile Screen that appears when you select "Air Quality (AQS)" from the AIRS Main Menu.
2) The second opportunity occurs after you have indicated the type of transaction (site or monitor) and
entered a "G" (Generate) on the Browse Data Type Screen.
12.2.2 Requesting the Transaction Generate Option
From the AQS Main Menu, select the "Browse Data" option. When the Browse Data Types Screen
appears, you may request the Transaction Generate option by entering a selection type of either" 1" (site)
or "2" (monitor), changing the "B" (Browse) to a "G" (Generate), and pressing ENTER.
If you have not already selected a screening file and entered a password, the Screening File Selection
Screen (Figure 12-4) will appear and you will be prompted to select one. Enter an "X" next to the
appropriate screening file and press ENTER. If you have not already entered the password, a window
for doing so will appear.
12.2.3 Entering Site or Monitor Selection Criteria
Next, either the Browse Site Data or Browse Monitor Data Selection Criteria Screen (Figure 12-5) will
appear. Enter the criteria necessary to specify the site or monitor record(s) upon which you want to
model the new transactions and press ENTER.
12.2.4 Generating Transactions
The Browse Site Data or Browse Monitor Data Screen that appears looks much like the normal Browse
screens. (Figure 12-6 contains a sample Browse Site Data Screen.) The main difference is that the cursor
can be moved to certain fields and transactions can be generated by pressing PF9, as discussed below.
BROWSE 12-4 September 1993
-------
AIRS User's Guide
Volume AQ3 Air Quality Data Storage
12.2.4.1 Creating Delete Transactions
Press PF9 to initiate transaction generation and to display the Action Code entry window (Figure 12-7).
Enter "D" and press ENTER. A window for confirmation will appear (Figure 12-8). Pressing PF9 a
second time will cause the Delete transaction to be written to the screening file. Pressing PF2 from the
Action Code entry or Confirmation windows will cancel the request. A message will appear at the top
of the screen signifying that the transaction was generated (Figure 12-9).
12.2.4.2 Creating Insert Transactions
Press PF9 to initiate transaction generation and to display the Action Code entry window (Figure 12-10).
Enter "I" and a new record key in the spaces provided. Press ENTER. You may now type over the
contents of any field on which the cursor can be positioned (use the TAB key to jump field to field, the
arrow keys to move up and down). Use the ENTER key to move to subsequent Browse pages for the
Site or Monitor record that was selected as the "source." After you have changed all the fields on all
the pages that you want to change, press PF9 a second time to generate the Insert transactions.
The minimum transactions required to insert a new record will always be generated. The exact number
and type of transactions generated is dependent on the data type; consult Volume AQ2, Air Quality Data
Coding, of this User's Guide for more information. Any Insert transactions that are considered optional
(see Volume AQ2) will be generated only if the fields that are part of the transaction contain
corresponding values on the Browse screen. The value of any field not specifically blanked out on the
Browse screen will be carried over to the generated transaction.
12.2.4.3 Creating Modify Transactions
Press PF9 to initiate transaction generation and to display the Action Code entry window. Enter an action
code of "M" and press ENTER. You may now type over any of the fields to which the cursor can be
positioned (use the TAB key to jump field to field, the arrow keys to move up and down). Use the
ENTER key to move to subsequent Browse pages for the Site or Monitor record that was selected as the
"source". After you have changed all the fields on all the pages that you want to change, press PF9 a
second time to generate the Modify transactions and to write them to your screening file.
Error Messages
The following error messages may be displayed from the Browse Data Types selection screen. In each
case, (xxxxxxxx) represents the screening file name.
PLEASE USE A VALID PF-KEY
Press PF3, PF4, or PF5 to terminate, or ENTER to proceed.
PLEASE ENTER A VALID OPTION
Select the type of Air Quality data to be browsed by entering a number (1 - 10).
September 1993 12-5 BROWSE
-------
AIRS User's Guide
Air Quality Data Storage Volume AQ3
GENERATE OPTION IS NOT AVAILABLE FOR THIS DATA TYPE
The Generate option has not been implemented for all data types. Make another data type
selection, or quit the Browse Generate feature.
ONLY VALUES 'B' OR 'G' ARE VALID FOR THIS FIELD
Enter "B" to browse only, or "G" to generate AIRS input transactions.
NO PASSWORD WAS ENTERED FOR SCREENING FILE (xxxxxxxx)
You did not enter a password for the screening file you selected. Select the screening file again
and enter its password.
(xxxxxxxx) CURRENTLY IN USE
The screening file is being used by another user or process. Try again later.
PASSWORD DOES NOT ALLOW ACCESS TO SCREENING FILE (xxxxxxxx)
The password you entered is not the correct screening file password, so you can not use Browse
Generate to add transactions to screening file (xxxxxxxx).
YOUR PASSWORD DOES NOT ALLOW YOU TO UPDATE SCREENING FILE: (xxxxxxxx)
The password you entered allows read access only to this screening file.
BROWSE 12-6 September 1993
-------
AIRS User's Guide
Volume AQ3 Air Quality Data Storage
The following error messages may be displayed if the user selected a screening file from the User Profile
screen. In each case, (xxxxxxxx) represents the selected screening file name.
(xxxxxxxx) SELECTED FROM THE USER PROFILE SCREEN COULD NOT BE FOUND
There is a system-level error involving this screening file. The user should report this error to the
AIRS Database Administrator.
(xxxxxxxx) IS LOCKED - STATUS (X)
The screening file is locked for another AQS process, such as L(0)AD, (C)ORRECT, (B)ROWSE,
(E)DIT, (S)CAN, or (U)PDATE. The status flag (X) indicates the process that has exclusive use
of the screening file. You must allow that process to end normally before you may generate
transactions to the screening file.
FILE TYPE IS NOT AIR QUALITY
There is a system-level error involving this screening file that allowed it to be included in an AQS
screening file selection list. Report this error to the AIRS Database Administrator.
YOU DO NOT HAVE UPDATE AUTHORITY FOR: (xxxxxxxx)
You must have update authority to add transactions to an AQS screening file. Access authorities
(Read or Update) are assigned to individual users by the AIRS Database Administrator.
PLEASE PRESS PF3 or ENTER
Press PF3 to end the screening file display and selection process; press ENTER to proceed with
the search.
The following error messages may be displayed if the user selected an ineligible screening file from the
User Profile screen, then asked the system for a list of files from which to re-select:
YOU HAVE MORE THAN 12 SF.S, USE USER PROFILE SCREEN TO SELECT
An unusable screening file was somehow selected from the User Profile Screen. You must return
to that screen to select a screening file that is eligible for Browse Generate.
NO AIR QUALITY SCREENING FILE FOUND FOR USER (XXX)
(XXX) is the user's user-ID. There are no Air Quality screening files available to this user.
YOU DO NOT HAVE UPDATE ACCESS TO AN AQS SCREENING FILE
At least one eligible, unlocked, Air Quality screening file was found, but the user does not have
update access authority for any.
AIR QUALITY SCREENING FILE(S) FOR USER: (XXX) LOCKED
Eligible AQS screening files were found for which user XXX has authority, but another AQS
process has exclusive use of the file(s).
September 1993 12-7 BROWSE
-------
AIRS User's Guide
Air Quality Data Storage Volume AQ3
The following error messages may be displayed if the user did not select a screening file from the User
Profile screen:
PLEASE ENTER AN "X" TO SELECT A SCREENING FILE - OR PRESS PF3 TO EXIT
Only the characters V or 'X* may be used to select the screening file from the Screening File
Selection screen.
PLEASE SELECT ONLY 1 SCREENING FILE
Enter an 'X' next to only one screening file name.
PLEASE PRESS AVAILABLE PF KEY OR ENTER
Press PF3, PF5, or ENTER.
The following error messages specific to the Transaction Generate function may be displayed from the
Browse Site Data or Browse Monitor Data display screen:
ENTER ACTION CODE OR PRESS PF2 TO CANCEL
After pressing PF9 to start the Transaction Generate function, you must enter an action code for
the transactions that are to be generated (T = Insert; 'M' = Modify; 'D' = Delete).
A NEW KEY IS REQUIRED FOR INSERT
If you are creating Insert transactions, you must enter the new site-ID or monitor-ID to be coded
on the transaction(s).
PLEASE CHOOSE PF2 OR PF9
If you have entered an action code of 'D' (Delete), you must confirm this choice by pressing PF9;
otherwise, you must press PF2 to cancel the delete transaction request.
BROWSE 12-8 September 1993
-------
AIRS User's Guide
Volume AQ3
Air Quality Data Storage
01/27/93
AIRS AI8 QliAUTY ;SUBSYSTBM :: ;; AMP500
is:;::;: jjsflrows*'.Data 'Types '.^•..V.:• '•• ••. :,:• •*••-•••. ..:•-•
1. AMPS1OS - Site
2. AMP510M - Monitor
3. AMP510Y • Sumary
4. AMPS1OH - Hourly
5. AMP5100 - Daily
6. AMP510C - Composite
7. AHP510T • History
8. AMPS1OR - P/A Reporting Organization Sunnary
9. AMPS 10N • P/A Monitor Sunnary
10. AMPS1OP - P/A Monitor Raw Data
Please Enter Selection : 1_ B (B»Browse, G«Gen«rate)
PF3=end
PF4=main menu
PF5=terminate
Figure 12-3. Browse Data Types Screen
September 1993
12-9
BROWSE
-------
Air Quality Data Storage
AIRS User's Guide
Volume AQ3
A I8S A1 r Quail ty Subsystem
:|i;:Screenlng M le Selection,;,:.
OTRNGA01
PF3=end
AHS5100
PF5=tcrminate
Figure 12-4. Browse Screening File Selection Screen
BROWSE
12-10
September 1993
-------
AIRS User's Guide
Volume AQ3 Air Quality Data Storage
11/12/92 AIRS Air Quality Subsystem AMPS10S
Brouse:Site Data
Selection Criteria
State : 25
County: 009
Site : 0005
PF3=end PF4=main menu PF5=terminate
Figurey 12-5. Browse Site Data Selection Criteria Screen
September 1993 12-11 BROWSE
-------
Air Quality Data Storage
AIRS User's Guide
Volume AQ3
11/25/92
AIRS Air Quality Subsystem
Browse Site Data
AMP510SB
Page 1/3
State : 23 MAINE
County: 001 ANDROSCOGGIN GO
Site : 0001
AQCR: 107 ANDROSCOGGIN VALLEY
MSA : 4240 LEWISTON-AUBURN, ME
CMSA: 9999 DESCRIPTION UNKNOWN
Elevation (MSL)
Land Use
Location Setting
Latitude
Method Of Cetera.
Datua
UTM
Zone
Address -,. ."•• ,•:;•.,.,-:
Support Agency
Location Descrip.
49 METERS
2 COMMERCIAL
1 URBAN AND CE
404:40:55:2000
XXXXXXXXXX
83 NAD 83
Date Established
Date Last Updated
Date Terminated
Longitude
Est. of Accuracy
Scale
19
Easting : 402000
Northing
88/01/01
89/06/22
88/03/01
+ 07:01:32:8000
XXXXXXXXXX
111111
4883250
MUTUAL BANK-GR. FALLS PLAZA
300 DESCRIPTION UNKNOWN
THIS IS THE LOCATION DESCRIPTION
PF3=end : PF4=main menu PF5=terminate PF7=prev PF8=next PF9=gen
Figure 12-6. Browse Site Data Screen
BROWSE
12-12
September 1993
-------
AIRS User's Guide
Volume AQ3
Air Quality Data Storage
01/27/93
State : 23 NAME
County: 001 *--
Site : 0001
Elevation (MSL
Land Use
Location Settl
Latitude
Method of;Dete
Datum
UTN
Zo
AIRS AIR QUALITY SUBSYSTEM
Browse Site Data
AOCR: 107
Enter Action Code:
D - Delete
M - Modify
I - Insert
Key Required For Insert
D -
AKPS10SB
Page 1/3
Press ENTER to continue, PF2 to Cancel
ANDROSCOGGIN VALLEY
+TON-AUBURN, ME
CMSA
76/01/01
69/06/22
92/09/01
-07:01:32:8
XXXXXXXXXX
ABCDEF 2:8
X
4883250
Address
Support Agency
Location Descrip.
MUTUAL BANK-GR. FALLS PLAZA
1 MAINE D.E.P. BUREAU OF AIR QUALITY CONTROL, AUGUST
THIS IS THE LOCATION DESCRIPTION
PF3=end PF4=main menu PF5=terminate PF7=prev PF8=next PF9=gen
Figure 12-7. Browse Site Data Screen with Action Code Entry Window ("D")
September 1993
12-13
BROWSE
-------
Air Quality Data Storage
AIRS User's Guide
Volume AQ3
01/27/93
State : 23 NAME
County: 001 +--
Site : 0001
Elevation
-------
AIRS User's Guide
Volume AQ3
Air Quality Data Storage
SCREENING FILE RECORD CREATED FOR ACTION-CODE: D
01/27/93 AIRS Air Quality Subsystem
Browse Site Data
Site-Id
: 23-001-0001
State or
Local Site
AMPS 1 OSS
Page 2/3
Id: XXXXXXXXXX
' Site toe. :• •
Type
3
. - -;. • . -;3. '•;.
Tangent
PF3=end
Description
: DOWNWIND FRINGE OF MSA/CMSA
DOWNWIND FRINGE
Street Type
Number Road
1 1
2 2
33
4 4
5 5
6 6
7 7
8 8
9 2
PF4=main menu
OF MSA/CMSA
Direction
To Street
NE
NW
SW
SW
NW
NE
NE
NW
SE
PF5=terminate
Traffic
Flow
1250
234567
345678
456789
567890
678901
789012
890123
901234
PF7=prev
Flow
Year
1977
1978
1979
1980
1981
1981
1982
1982
1989
NSA CMSA
Rep. Rep.
0380
0013
Street Name
STREET NAME 1
STREET NAME 2
STREET NAME 3
STREET NAME 4
STREET NAME 5
STREET NAME 6
STREET NAME 7
STREET NAME 8
BYTE BLVD.
PF8=next PF9=gen
Figure 12-9. Browse Site Data Screen with Screening File Record Message
September 1993
12-15
BROWSE
-------
Air Quality Data Storage
AIRS User's Guide
Volume AQ3
^:::^^f-^:^::.^^
:"• -^ '""•'•
¥^fjj'j'ff:^:^f^
Islpofl^l-:/?.®
:' -'• •-'•' • ':'.:\'.'-, .'•'.' •Site^tbie^PIS
•*:'- • • ' Type;
.. • . ;: '• .'.3-::': :•••;
• ":•: .-' - 'J ••'••:' : : .:?&;-:
''• VH.^;.'\'.V:V:. Tangent
PF3=end
:.*:?De« •
oow
.;tibow>
- •:*::i:-.>¥i:4
::Stre*:"i
Nurabe
^.1^
i'^2^^
•.•••3 •••'•!
Browse Site Data
fc:X-.;r::":;-;V;:: ::•/" '• •• • '"'-v,.
State or Local Site
id: xxxmxxxx
iinter Action Code:
0 i Delete
H - Modify
I - Insert
?£&:/-"'v&i
;!£.;;;;•:.:•••;• -::99
Press ENTER
- 4 ... •. ."•."4-. •
' -:5, •';/.. 5'
: -6' •:-•••' . 6
":-;7- --., 7.
V:;;>8. ;:.;..:- 8'
••;:-.9Vv" 2 '
f Required For Insert
001 1234
to continue, PF2 to Cancel
NS 456789
NU 567890
NE 678901
NE 789012
NU 890123
ES 901234
PF4=main menu PF5=terminate PF7=prev
r
SA CMSA
ep. Rep.
380
013
Street Name
STREET NAME
STREET NAME
•STREET NAME
1980 STREET NAME
1981 STREET NAME
1981 STREET NAME
1982 STREET NAME
1982 STREET NAME
1989 BYTE BLVD.
AMP510SB
Page 2/3
1
2
3
4
5
6
7
8
PF8=next PF9=gen
Figure 12-10. Browse Site Data Screen with Action Code Entry Window ("I")
BROWSE
12-16
September 1993
------- |