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

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

book

Article ID: 54222

calendar_today

Updated On:

Products

Top Secret Top Secret - LDAP Top Secret - VSE

Issue/Introduction

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

TSS7053I Default ACID <defacid> Assigned
TSS7251W Access Denied to TERMINAL <INTRDR>
TSS7100W 022 J=BGINIT A=defacid T=INTRDR F=BATCH - Unauthorized Reader
TSS7170W Job Originated From Protected Reader <INTRDR>
TSS7251W Access Denied to VSEPART <BG>
TSS7250W 136 J=BGINIT A=defacid Type=VSEPART Resource=BG
TSS7251W Access Denied to VSEPART <BG>

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

TSS9000I CA-Top Secret security 300610KD active

In our IPL procedures we do have the card:

ID USER=user

After the // JOB BGINIT card and before the EXECs of CASAUTIL and BSSINIT, it is expected that IBM security would have assigned 'user' to this job prior to the Top Secret startup, so why has Top Secret assigned the 'defacid' to this job?

The ID card is in the ASIPROC as per the following example:

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

Environment

Release:
Component: TSSVSE

Resolution

The BG ASIPROC needs to have the // ID straight after the EXEC BSSINIT, for example:

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

Otherwise the BG partition will get the Default acid when Top Secret activates and you will see the TSS7053I Default ACID <defacid> Assigned message. The default ACID cannot issue commands like START F1 which is why you receive the warning messages.