CA View - XMS Session Hang on Reaching USERMAX
search cancel

CA View - XMS Session Hang on Reaching USERMAX

book

Article ID: 202966

calendar_today

Updated On:

Products

Deliver View

Issue/Introduction

There are two SARXMS regions in use, a primary region and a secondary region, for VTAM users.

Once the primary region reaches the USERMAX limit, users are passed to the secondary region.

Those in the secondary region experience the following hang:

STC00763  SARVERR1  SARI0002_TPXBA008_VT EBCVTDRV REQ=OPNDST RTNCD=1001 FDBK2=08210000 IGNORE ERROR
STC00763  SARVERR1  SARI0002_TPXBA008_VT RtnCd Analysis=OPNDST failed                              
STC00763  SARVERR1  SARI0002_TPXBA008_VT FDBK2 Analysis=Request reject-Invalid Session parameter   
STC00763  SARVDRV4  SARI0002_TPXBA008_VT ***REJECTED*** OPNDST FAILURE                             
STC00763  SARVDRV5  SARI0002_TPXBA008_VT 010303B19030800007E6E68700028000                          
STC00763  SARVDRV5  SARI0002_TPXBA008_VT 00000018501B847F000008E2C1D9C9F0                          
STC00763  SARVDRV5  SARI0002_TPXBA008_VT F0F0F100000000000000000000000000                          
STC00763  SARVETX1  SARI0002_TPXBA008_VT TASK ENDED         CPU=     0.00 LOGON=2020/161 10:02:36  


Environment

Release : 14.0

Component : CA View

Cause

The root problem was found to be in TPX, where the PCIF 5F vector was not being tracked.

Resolution

It was suggested that the SARXMS parameter VTAMPASS be set to VTAMPASS=YES on all of the SARXMS tasks, rather than just the primary task, so that there would not be any hang condition in either of the tasks.

To allow View to move users to a second SARXMS region, once the USERMAX parameter value was reached in the first region, the client made the following TPX update:

. Reserve Option 18 must be turned on to use 57 Vector.