TPX Session Management for z/OS

 View Only
  • 1.  Tuesday Tipp for TPX: Some fields of the ACT can be updated dynamically - but what about the others?

    Posted Feb 24, 2015 04:04 AM

    When doing updates for an application in the ACT there are a couple of

    fields which cannot be updated dynamically by reloading the ACT. These are

    - Type (SHR, GRP, UNQ, TPX)

    - Keep Virtual Terminal

    - End-to-End Option

    - Readbuf Technique

    - Screen Even if Readbuf Technique

    - Inbound Compression

    - Opengate Control User

    - Load Module Name

     

    You can recognize these fields by the missing asterisk '*' in front of

    them. You can make changes to these fields become effective by restarting

    TPX. If you do not want this to do then you can follow these steps:

     

    1. Save the changes done in the ACT entry for the application.

    2. Let all users log off that application

    3. Quiesce the application using TPXOPER command "Q <applid>"

    4. RELOAD ACT=<act-table>

    5. Activate the application again using TPXOPER-command "ACT <applid>"



  • 2.  Re: Tuesday Tipp for TPX: Some fields of the ACT can be updated dynamically - but what about the others?

    Posted Feb 25, 2015 03:58 AM

    I think that point 2 (all the users must log off from application) is a step backward... because it's good that quiescing does not imply logoff users! So...



  • 3.  Re: Tuesday Tipp for TPX: Some fields of the ACT can be updated dynamically - but what about the others?

    Posted Feb 26, 2015 02:47 AM

    When you Quiesce an application in TPXOPER you get a panel (TEN0203) telling you about the success of that operation.

    Field STATUS contains 'QUIESCED' if no user was logged on any more, it contains the status 'PQUIESCE' (Pending Quiesce) if one or more users are still logged on. It also lists these users.

    Quiesceing an application means that no new user can logon. For the change of the type of virtual terminals this is not enough. It is essential that the application is quiesced AND all that users are logged off - otherwise this field cannot be changed dynymically. Reason for this is that TPX cannot handle users logged on with terminals of Type SHR and others with Type of UNQ or GRP at the same time.