EMSA Subsystem
The EMS Analyzer is used to query the EMS logs and generate reports that can be viewed on a terminal or sent to the spooler, to an Enscribe database or to a Comma Separated Values (CSV) file.
EMSA comes with a default DDL dictionary so that Enform reports can be created based on Enscribe data files.
CSV files can be exported to a PC for analysis and reporting using programs like ACCESS or EXCEL.
The EMS Analyzer's default parameterized filter can be used to specify a set of search criteria.
EMSA comes with tokenized filters that can be customized using a conversational interface. The EMS logs can be searched for events based on: start and stop time, event number, event type, process ID, subsystem ID, logical device, system name , or text string.
EMSA is frequently used to isolate EMS messages generated by application programs, which are then used to help resolve application problems.
Installing EMSA does not require a SYSGEN. It is installed using a TACL routine supplied with the product.
The EMSA Subsystem includes the following components :
EMSA The EMSA object file.
EMSACSTM The default EMSACSTM file, created when EMSA is installed.
EMSADDL The default EMSA DDL for the Enscribe database.
EMSADEF The default EMSA DEF for the Enscribe database.
EMSAFLTR The default EMSA filter. Use this as a template for customized filters.
Customized filters may be owned by the users who create them or some other suitable userid and shared by appropriate users.
EMSASSID File containing the Subsystem ID (SSID) for each of the most common HP NonStop server subsystems.
EMSATEXT Text file containing EMSA Help and Error messages.
The system manager may also have created one or more alternate collectors specifically for EMSA use.
RISK The EMSA subsystem is used for reporting only. It does not pose any security risks.
Customizing the EMSA environment
Each time a user invokes EMSA, a file called EMSACSTM is invoked before the first prompt. The EMSACSTM file is an obey file that resides in each user's default sub- volume. The file can be used to customize the user 's EMSA environment by defining options such as function key/command associations.
The EMSACSTM files should be secured properly. Please refer to Gazette section on *CSTM Configuration Files.
Securing EMSA Components
BP-FILE-EMSA-01 EMSA should be secured "UUNU".
BP-OPSYS-OWNER-02 EMSA should be owned by SUPER.SUPER.
BP-OPSYS-FILELOC-02 EMSA must reside in $SYSTEM.SYSTEM.
BP-FILE-EMSA-02 EMSADDL should be secured "NUNU".
BP-OPSYS-OWNER-02 EMSADDL should be owned by SUPER.SUPER.
BP-OPSYS-FILELOC-02 EMSADDL must reside in $SYSTEM. SYSTEM.
BP-FILE-EMSA-03 EMSADEF should be secured "NUNU".
BP-OPSYS-OWNER-02 EMSADEF should be owned by SUPER.SUPER.
BP-OPSYS-FILELOC-02 EMSADEF must reside in $SYSTEM. SYSTEM.
BP-FILE-EMSA-04 EMSFLTR should be secured "NUNU".
BP-OPSYS-OWNER-02 EMSFLTR should be owned by SUPER.SUPER.
BP-OPSYS-FILELOC-02 EMSFLTR must reside in $SYSTEM. SYSTEM.
BP-FILE-EMSA-05 EMSASSID should be secured "NUNU".
BP-OPSYS-OWNER-02 EMSASSID should be owned by SUPER.SUPER.
BP-OPSYS-FILELOC-02 EMSASSID must reside in $SYSTEM. SYSTEM.
BP-FILE-EMSA-06 EMSATEXT should be secured "NUNU".
BP-OPSYS-OWNER-02 EMSATEXT should be owned by SUPER.SUPER.
BP-OPSYS-FILELOC-02 EMSATEXT must reside in $SYSTEM. SYSTEM.
If available, use Safeguard software or a third party object security product to grant access to EMSA object files only to users who require access in order to perform their jobs.
BP-SAFE-EMSA-01 Add a Safeguard Protection Record to grant appropriate access to the EMSA object file.
| Discovery Questions | Look here: | |
|---|---|---|
| OPSYS-OWNER-02 | Who owns the EMSA file? | Fileinfo |
| OPSYS-OWNER-02 | Who owns the EMSADDL file? | Fileinfo |
| OPSYS-OWNER-02 | Who owns the EMSADEF file? | Fileinfo |
| OPSYS-OWNER-02 | Who owns the EMSFLTR file? | Fileinfo |
| OPSYS-OWNER-02 | Who owns the EMSASSID file? | Fileinfo |
| OPSYS-OWNER-02 | Who owns the EMSATEXT file? | Fileinfo |
| FILE-POLICY | Who is allowed to use EMSA on the system? | Policy |
| FILE-EMSA-01 | Is the EMSA object file correctly secured with Guardian or Safeguard? | Fileinfo Safecom |
| FILE-EMSA-02 | Is the EMSADDL file correctly secured with Guardian or Safeguard? | Fileinfo Safecom |
| FILE-EMSA-03 | Is the EMSADEF file secured correctly? | Fileinfo |
| FILE-EMSA-04 | Is the EMSFLTR file secured correctly? | Fileinfo |
| FILE-EMSA-05 | Is the EMSASSID file secured correctly? | Fileinfo |
| FILE-EMSA-06 | Is the EMSATEXT file secured correctly? | Fileinfo |
Related Topics
EMS
