AXCEL User Program
AXCEL User Program
The Accelerator (AXCEL) program transforms HP NonStop server compiled language object code to produce accelerated object code, which may run faster. How much faster depends on whether or not the code runs on a RISC (TNS/R) system or an older CISC (TNS) system.
AXCEL is used with TNS compilers and not with native compilers. Native languages are already accelerated for performance. Programs consisting mainly of calls on system code do not get much additional performance gain by acceleration because system code has already been native-compiled. Programs consisting of large amount of user code may gain significant performance by the acceleration compilation (See Figure 6-1).
Figure 6.1: Accelerating
RISK AXCEL presents no security risks.
Securing AXCEL
BP-FILE-AXCEL-01 AXCEL should be secured "UUNU".
BP-OPSYS-OWNER-02 AXCEL should be owned by SUPER.SUPER.
BP-OPSYS-FILELOC-02 AXCEL must reside in $SYSTEM.SYSTEM.
AP-ADVICE-AXCEL-01 AXCEL is resource intensive and could affect application processing. Code need not be accelerated on the system where the accelerated object file will be executed.
AP-ADVICE-AXCEL-02 To avoid impacting applications, programs should be accelerated on a development or test system and the accelerated program moved to the secure site.
If available, use Safeguard software or a third party object security product to grant access to AXCEL object files only to users who require access in order to perform their jobs.
BP-SAFE-AXCEL-01 Add a Safeguard Protection Record to grant appropriate access to the AXCEL object file.
| Discovery Questions | Look here: | |
|---|---|---|
| FILE-POLICY | Are accelerations performed on the system? | Policy |
| OPSYS-OWNER-02 | Who owns the AXCEL object file? | Fileinfo |
| FILE-POLICY | Who is allowed to execute AXCEL on the system? | Policy |
| FILE-AXCEL-01 | Is the AXCEL object file correctly secured with the Guardian or Safeguard system? | Fileinfo Safecom |
Related Topics
Compilers
Securing Applications
