How to identify STX users?

Products

Teleview TELEVIEW- PACKAGE TPX - Session Management Vman Session Management for z/OS

Issue/Introduction

Trying to delete a user assigned to the group that I am authorized to administer, yet I get message MENA8034 You do not have authority to do this DELETE.I've been told this is because the user I'm trying to delete is a STX user. How can I identify STX users? And what is needed so that I can delete them?

Environment

Release:
Component: TLVIEW

Resolution

A customer does not need to be licensed (authcode or LMP code) for STX, STX structures can still be created and copied from userid to userid within TPX (especially on static users). They can be created by selecting STX options by mistake and not cancelling out, but backing out. In this case, a STX structure is created even if no data is entered on the STX side.

Thus, an ADMINISTRATOR needs both TPX and STX Administrator capabilities all set to Y in order to be able to delete such a userid. See Knowledge document How to add STX Administrator authority? for details .

If an administrator without STX authority tries to delete a STX user through TPXADMIN User Maintenance panels, they will get the message MENA8034 You do not have authority to do this DELETE. (Note that there are also other causes for this message.)

To check if the user has STX:

ONLINE: This user has an asterisk next to STX User Options which indicates that they have a STX structure.

                  TPX User Maintenance                     Panelid  -TEN0118                                                           Userid   - Select Option ===>                                         Terminal -                                                            Date     -     Userid: USER002                                        Time     -  * 1  TPX User Options  2  TPX Session Options * 3  STX User Options  4  STX Session Options   5  Maintain List of Profiles  6  Maintain Administrator Capabilities  7  Maintain TPX VIEW Capabilities * Indicates this user has signon access to this CA product.

BATCH: Here's a quick report to identify any userids with STX data only (non-TPX):

//BATCHADM EXEC TPX,VNODE='*BATCH*'//EXTFILE  DD UNIT=SYSDA,SPACE=(CYL,(1,1))//RPTFILE  DD SYSOUT=*//*//SYSIN DD *CC  extract if user has any STXCEXTRACT GIVING(EXTFILE) USER AND NO SESSIONS (VUSR$TPX(N))cSET RTITLE1 ' ================= 'SET RTITLE2 '  USERIDs with STX 'SET RTITLE3 ' ================= 'REPORT GIVING(RPTFILE) USING (EXTFILE)     ((' &UIDXNAME')) Sample output: =================USERIDs with STX=================$STXMODLSTXUSERASTXUSERBSTXUSERCSTXUSERD

As noted in the Batch Admin Guide, if you choose to delete the users with TPX batch, DELETE STX indicates that you are deleting CA STX values and signon authority. If the user or profile does not have TPX signon authority, the user is deleted.

NOTE: An extract on VUSR$TPX(N) will only identify those userids that have only STX values and no TPX values.

CA TPX and CA STX share a common administration structure.

CA-N-Vision/STX was an advanced ACF/VTAM application that addressed the problems associated with accessing an X.25 network. It allowed a 3270 terminal user to access applications on an X.25 network via the SNA host. (Support for STX was dropped in 2010.)