Warning messages TSS7251W, TSS7100W, TSS7170W for DUMMY ACID in the BG partition during the IPL process when in WARN mode.

Document ID : KB000054222
Last Modified Date : 14/02/2018
Show Technical Document Details

Description:

We are currently running in WARN mode and the following messages are appearing in the BG partition during the IPL process:

TSS7053I Default ACID <DUMMY> Assigned
TSS7251W Access Denied to TERMINAL <INTRDR>
TSS7100W 022 J=BGINIT A=DUMMY T=INTRDR F=BATCH - Unauthorized Reader
TSS7170W Job Originated From Protected Reader <INTRDR>
TSS7251W Access Denied to VSEPART <BG>
TSS7250W 136 J=BGINIT A=DUMMY Type=VSEPART Resource=BG
TSS7251W Access Denied to VSEPART <BG>
TSS7000I DUMMY Last-Used 10 Sep 08 10:37 System=VSEA Facility=BATCH
TSS7001I Count=55692 Mode=Warn Locktime=None Name=DUMMY BATCH

These messages appear in BG just after the following message has
appeared in the CA-Top Secret partition F2:

TSS9000I CA-Top Secret security 300610KD active

In our IPL procedures we do have the card

ID USER=FORSEC

After the // JOB BGINIT card and before the EXECs of CASAUTIL and BSSINIT, so we expected that IBM security would have assigned FORSEC to this job prior to the CA-Topsecret startup, so why has
CA-Topsecret assigned the DUMMY ACID to this job?
The ID card is in the ASIPROC as per the following example:
// EXEC BSSINIT
START F1
STOP
// ID USER=FORSEC <<<<<<<<<<<<<
// EXEC PROC=ASSIGN
// EXEC PROC=LIBDEF
/+

Solution:

The BG ASIPROC needs to have the // ID straight after the EXEC BSSINIT eg

// EXEC BSSINIT
// ID USER=FORSEC
START F1
STOP
// EXEC PROC=ASSIGN
// EXEC PROC=LIBDEF
/+

otherwise the BG partition will get the Default acid when TSS activates
and you will see the TSS7053I Default ACID <DUMMY> Assigned message.
The default ACID cannot issue commands like START F1 which is why you receive the warning messages:
TSS7251W Access Denied to TERMINAL <INTRDR>
TSS7100W 022 J=BGINIT A=DUMMY T=INTRDR F=BATCH - Unauthorized Reader
TSS7170W Job Originated From Protected Reader <INTRDR>