RAKF FACILITY violation on HTTPX resource during server shutdown

[mgrossmann]

Description

During normal HTTPD shutdown, a RAKF security violation occurs after the server has already reached SHUTDOWN state. The server shuts down cleanly (quiesce → socket thread → workers → filesystem → SHUTDOWN), but then an unauthorized access attempt is made to the HTTPX FACILITY resource via SVC244.

Console Log

FFFF 14.09.03 STC  113  HTTPD100I CONS(0) START
FFFF 14.09.03 STC  113  HTTPD100I CONS(0) STOP
FFFF 14.09.03 STC  113  HTTPD002I Server is QUIESCE
FFFF 14.09.05 STC  113  HTTPD060I SHUTDOWN socket thread    TCB(9CDC18) TASK(194FC8) STACKSIZE(32768)
FFFF 14.09.04 STC  113  HTTPD060I SHUTDOWN worker(1A68F8)   TCB(9B92E8) TASK(1CAFC8) STACKSIZE(65536)
FFFF 14.09.04 STC  113  HTTPD060I SHUTDOWN worker(1A6B80)   TCB(9B9618) TASK(1B9FC8) STACKSIZE(65536)
FFFF 14.09.05 STC  113  HTTPD060I SHUTDOWN worker(1A6C80)   TCB(9B9868) TASK(1A8FC8) STACKSIZE(65536)
FFFF 14.09.05 STC  113  HTTPD047I Terminating File System
FFFF 14.09.05 STC  113  HTTPD002I Server is SHUTDOWN
FFFF 14.09.05 STC  113  RAKF0005 INVALID ATTEMPT TO ACCESS RESOURCE
FFFF 14.09.05 STC  113  RAKF000A     ~~$~ ,HTTPX   ,FACILITY,SVC244

Analysis

The RAKF violation happens after HTTPD002I Server is SHUTDOWN, suggesting that a cleanup step (likely program name deregistration or similar SVC244 call) runs after the security context or authorization has already been torn down.

The resource name HTTPX in FACILITY class via SVC244 points to a program authorization check that occurs too late in the shutdown sequence.

Expected Behavior

Server shutdown should complete without RAKF violations. Either:

1. The SVC244 call should happen earlier in the shutdown sequence (before security context cleanup), or
2. The STC should be authorized for the HTTPX FACILITY resource in RAKF, or
3. The call causing this access check should be skipped/guarded during shutdown.