How to clear a user that is stuck in the signon process?

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

Symptoms: 

A user is attempting to logon to TPX and gets a message similar to:

SIGNON DISALLOWED

USER SIGNON ALREADY IN PROGRESS

 

Cause: 

User already exists in TPX storage.  

They may have become "stuck" during the signon process or not properly cleaned up during the previous TPX session.

 

Resolution

First ensure that any and all fixes related to SIGNON have been applied.

User storage will be cleared when TPX is cycled.

To correct the situation without cycling TPX, you can use the following workarounds to delete the user from memory.

 

Workaround #1: 

This is the preferred method.

This is a new feature added to TPX 5.4 with PTFs RO86230 & RO86231: USER ID LOCKED, PROVIDE METHOD TO RELEASE USER ID

  • ENHANCEMENT DESCRIPTION:  Update the MOD U= oper command to provide a method to free a locked user id. 

 

If you do not have these fixes applied, you will need to use workaround #2.

 

  1. Use the TPXOPER command:  MOD U=userid,ERASE

 

ERASE - Removes the specified user ID from memory. This operand is for use with the U=userid only.

TPX documentation - Operator Commands MODIFY Command

 

Workaround #2:  *** USE WITH CAUTION ***

It is strongly recommended that you discuss the appropriateness of taking this step with CA Technical Support BEFORE proceeding.

  1. Go into TPXOPER. Type 'D MEM,U=xxxxxxxx' where xxxxxxxx is the userid and press ENTER.

  2. The Memory Display/Update screen is presented with the following fields:

    Sample TPXOPER display: D MEM,U=ABCDE01

    FieldMeaning
    ADDRESSHexadecimal address of memory in address space.
    OFFSETHexadecimal offset from beginning of location displayed.
    hex dataEach row contains four words of hexadecimal data at the indicated address.
    char dataEach row contains 16 bytes of character data at the indicated address. Non-displayable hexadecimal characters are translated to a period(.).

    Figure 1


  3. On first line of data under the heading line (ADDR OFFSET ...) go to the right side of the screen into the area between asterisks which is
    the character display area (NOT the hex area in the center).


    Behind the *UIDX you will see the userid that was specified in the D MEM command. (In this example the userid is ABCDE01.)

    Figure 2


  4. Type over the USERID in the character display area (outlined in red in the previous step), NOT in the hex area.

    We recommend using only upper-case letters, such as all X's.

    - DO NOT use spaces.

    - DO NOT hit"erase eof ".

    - DO NOT key outside of the USERID otherwise TPX WILL ABEND.

    Keying over the USERID creates a mock USERID linked to TPX and frees the valid USERID to logon again and continue.

    Since the purpose of this is to create a phony USERID, you can key over part or all of the valid USERID, so long as the resulting USERID is not a 'real' USERID. Sample after over-typing valid USERID with non-existent USERID:

    Figure 3


    Notice that the hex area (outlined in blue) above has not yet changed.

  5. Press PF9 to update. The change will not take place until you press PF9.

    Sample after pressing PF9:

    Figure 4


    Note that the hex area has changed to correspond to the new userid value: seven X's (hex E7) and a space (hex 40) has remained unchanged. (It is possible to have an eight character TSO userid, which is why the eighth character in this example was always a space.)

  6. Press PF3 to end. This takes you back to OPER command line.

  7. The original userid should now be able to logon to TPX.

Note: This procedure should be used with extreme caution!

 

Additional Information:

For access to the ERASE parameter for MODIFY command, apply Published Solutions for TPX 5.4:  PTFs RO86230 & RO86231

TPX documentation - Operator Commands MODIFY Command

 

TPX documentation - Operator Commands DISPLAY Command for Memory