In CA TPX, using TPXOPER VTADD fails with error: MENOVA03 VTAMLST member not found.

Products

• TPX - Session Management
• Vman Session Management for z/OS

Issue/Introduction

Using either 'VTADD member' or 'VTADD=member', I keep getting this error:

MENOVA03 VTAMLST member not found

Corresponding TPX LOG message:

TPXL0006 11/13/08.318 15:38:45.63 VTAMLST ADDITIONAL NODE vtamlu

Environment

Release: NVINAM00200-5.3-TPX-Session Management-Access Management package
Component:

Cause

A TPX operator session gives an authorized user the ability to monitor and control processing and resources.

The VTADD command adds virtual terminals or virtual printers while CA-TPX is still running, using a member in the VTAMLST data set where additional virtual terminals or virtual printers have been defined. This member must contain only the new virtual terminals or printers. It should not contain the Primary ACB or the Shared ACB.

Resolution

Verify the following:

1. Does member name specified in the VTADD command actually exist in the data set referred to on the VTAMLST DD?
   • Format: VTADD member or VTADD member SYSID=tpxappl
   • Is there a typing error in the command that you entered in TPXOPER?
2. Did you successfully vary this member active to VTAM?
   • VTAM activation message: 
     IST097I VARY ACCEPTED 
     IST093I vtamlu ACTIVE 
     IST097I DISPLAY ACCEPTED 
     IST075I NAME = vtamlu, TYPE = APPL SEGMENT 
     IST486I STATUS= ACTIV, DESIRED STATE= ACTIV 
     IST360I APPLICATIONS: 
     IST080I KH32249U CONCT      KH32249G CONCT 
     IST314I END
3. Do you need to use the SYSID=tpxappl parm?
   • SYSID identifies a specific instance of CA-TPX on which the command is to be executed.
   • The output is routed back to the issuer; tpxappl identifies the instance of CA-TPX. It is the unique VTAM Application Name (referred to as the Primary APPL in the Installation Guide) opened by the target instance.
4. Does the data set associated with TPX proc VTAMLST DD use parm FREE=CLOSE?
   • If FREE=CLOSE is required in your environment on a permanent basis, you will not be able to use VTADD. You will need to cycle TPX to make the new terminals available.
   • TPX cannot release or update existing VTAM members while TPX is running. VTADD provides the capability to add virtual terminals (or printers) by recognizing a new member in the VTAMLST PDS or PDS/E that was not present when TPX was started. However, FREE=CLOSE prevents TPX from being able to add this new member while TPX is running, thus rendering the VTADD command ineffective in your environment.

Additional Information

TPX 5.4 Operator Guide - VTADD Command