II12403: THIS APAR DESCRIBES THE VTAM GENERIC RESOURCE SUPPORT FOR NETVIEW ACCESS SERVICES INTR. BY APAR PQ35801 PTF UQ44881.

APAR status

• Closed as documentation error.

Error description

• DESCRIPTION:
  This APAR implements the VTAM Generic Resource support for
   NetView Access Services. This new feature allows NV/AS to
   exploit the capabilities provided by the VTAM Generic
   Resource feature in a Sysplex environment, such as improved
   availability and automatic workload balancing.
  
  NV/AS VERSION:  V2.1.1   569503601  HNVS111
  
   1 - SYSTEM PREREQUISITES:
    - MVS/ESA 5.1 or higher
    - Sysplex Environment with an MVS Coupling facility
    - VTAM 4.2 or higher
  
   2 - SYSTEM CONFIGURATION
   2.1 - COUPLING FACILITY STRUCTURE ALLOCATION
   NV/AS uses a list structure in Coupling Facility to keep the
   list of all the users logged on to all the NV/AS instances
   with the same Generic Resource name.
  A Coupling Facility Structure MUST be defined in the
   active CFRM policy with the following characteristics:
  
     STRUCTURE NAME(EMS_grname)
     SIZE(maxSize)
     INITSIZE(initialSize)
     PREFLIST(cfName1,cfName2)
  
   Where:
    grname: The NV/AS generic resource name.
    maxSize and initialSize: Specify the maximum and initial
    amount of space to be allocated for the structure.
   The number is specified in units of 1K (1024 bytes).
   cfName1 and cfName2: The names of the preferred and alternate
   coupling facilities where the structure must be allocated.
  
  2.1.1 - EXAMPLE OF COUPLING FACILITY STRUCTURE DEFINITION
  
     STRUCTURE NAME(EMS_NVPROD11)
     SIZE(2000)
     INITSIZE(1000)
     PREFLIST(CF01,CF02)
  
  Where:
   NVPROD11: The VTAM generic resource name for that NV/AS.
   The name of the coupling facility structure must always
   start with "EMS_"
   2000: Specifies that structure size can grow  up to 2 Mb
   1000: Specifies that structure will be initially allocated
   with 1 Megabyte size.
   CF01 and CF02: The names of the preferred and alternate
   coupling facilities where the structure is allocated
  
  2.1.2 - STRUCTURE SIZE CONSIDERATOINS
  A 1 Megabytes coupling facility structure allows NV/AS to
  handle up to 5700 users logged in at the same time.
  For example: INITSIZE(1000), allows NV/AS to handle about
  5700 users logged on at the same time.
  SIZE(2000), allows the structure size to be increased
  to handle up to 11.000 users logged on at the same time.
  
  2.1.3 - CFLEVEL CONSIDERATIONS
  CLEVEL >= 1 Coupling Facility is required for NV/AS to be able
  to automatically increase the size of the structure up to the
  maximum size if this becomes full during the running of the
  product. If you have a CFLEVEL=0 coupling facility, NV/AS can
  run, but it cannot automatically increase the structure size
  if this becomes full. In this case INITSIZE must be set so
  that it can handle the maximum number of simultaneously logged
  on users. When the EMS_grname structure is allocated on a
  CFLEVEL=0 Coupling Facility, at StartUp time NV/AS fails the
  first time it tries to connect to the CF structure. It then
  sends EMS0573E and EMS0574E messages to indicate that the
  structure is allocated on a CFLEVEL=0 coupling facility and
  that it does not support dynamic size altering. After these
  messages NV/AS will re-connect to the structure without
  Size Alter support.
  
  2.2 - VTAM CONFIGURATION
  - VTAM must be configured to work with Generic Resource
  - STRGR VTAM start option must specify the name of a coupling
    Facility Structure. Default Value is ISTGENERIC
  - ISTGENERIC coupling facility structure must  be allocated
  - There must be an active CFRM policy for the SysPlex
    environment
  - VTAM must be connected to ISTGENERIC structure
  
  2.3 - NV/AS CONFIGURATION
  - NV/AS loadlib MUST be APF authorized
  - EMSBROAD (broadcast)VSAM Dataset must be shared if you want
    to use the Global Broadcasting Feature.
  - All other VSAM datasets can or cannot be shared depending
    on your system configuration. Sharing Clsuter VSAMS always
    affects the NV/AS performance.
  
  3 - CUSTOMIZATION
   - VTAM Generic Resource in NV/AS can be activated using the
     new NV/AS startup parameter: GRNAME='Generic Resource name'
     (can be 1 to 8 character string)
     Example:
     APPL ACBNAME=I9PC96D0,PASSWORD=SECRET,
          BUFFMAXN=1000,BUFFLEN=1024,
          GRNAME=NVPROD1,RCONNECT=YES..........
   - NV/AS instances starting with the same GRNAME are part of
     the same NV/AS GR group, and can all be addressed using the
     GR Name.
   - A NV/AS instance can belong to one single group at a time
     (only one GRNAME parameter is allowed).
   - VTAM Generic resource name cannot be changed while NV/AS
     is running. NV/AS startup parameters must be changed
     and NV/AS must be recycled.
  
  4 - NV/AS VTAM GENERIC RESOURCE FUNCTIONS - USAGE
  4.1 - LOGGING ON TO NV/AS
  - NV/AS users can log on to NV/AS using the 'Generic Resource
    Name' that is 'logon applid=NVASTEST'
  - Users can still log on using the ACB name
  - If user is not logged on to any NV/AS in the GR group, VTAM
    decides to which NV/AS in the GR group to route the session
    based on system load.
  
  4.2 - USER AFFINITY
  - If a user disconnects from an NV/AS by leaving active
    application sessions, every time a user reconnects with the
    same userid (from the same, or from another terminal) its
    session is always transferred to that NV/AS.
  - All users logging on with the same userid are always put
    in session with the same NV/AS instance.
  - You can force the logon to a particular NV/AS instance by
    specifying 'LOCAL' in the Location field of the Logon Panel.
  - From ADM Option 1 user can see ACB name and GR name of the
    NV/AS instance he/she is actually logged on.
  
  4.3 - CONNECTING TO VTAM GENERIC RESOURCE APPLICATIONS
  NV/AS allows the user to connect to applications that are
  themselves VTAM GR. To allow NV/AS to connect to an application
  with its GR name, in ADM option 4, set the "Primary LU Name"
  field to the application VTAM Generic name.
  Some restrictions apply when connecting to VTAM GR
  applications:
  - A pseudo terminal in session with a GR application using its
    GR name cannot establish another session with that
    application via its real ACB name. This applies only
    to applications using Individual pseudo teminals.
  - A pseudo terminal requesting a second session with the same
    VTAM GR application always resolves to the same application
    instance.
    This applies to applications using Shared Pseudo-terminals.
  
  4.4 - MULTITERMINAL AND TERMINAL ASSUME FUNCTIONS
  - No interface changes for these functions.
  
  4.5 - SESSION SHARING
  - Two users that want to share a session MUST be logged on to
    the same NV/AS instance.
  - NV/AS does not provide automatic session transfer for
    session sharing requests. User must log on to that instance
    using the ACB name.
  
  4.6 - SIMPLE BROADCAST
  - New parameter in 'Broadcast a message' panel (ADM option 8),
    to specify: Add/Change/Delete of a General Broadcast message
    locally or to propagate the change to all NV/AS instances
    in the same GR group. .
  - EMSBROAD VSAM dataset does NOT need to be shared.
  
  4.7 - SELECTIVE BROADCAST
  - To share Selective Broadcast messages among all NV/AS
    instances in a GR group, EMSBROD VSAM Cluster MUST be shared
    among all NV/AS instances in the Generic Resource group.
  
  4.8 - SINGLE OPERATOR INTERFACE
  In the NV/AS WTOR Operator interface there si now the
  capability to send a command from one NV/AS to another NV/AS
  or to all NV/AS instances in the same GR group.
  - CANCEL, DISPLAY USERS, DISPLAY SESSIONS and DISPLAY TERMINALS
    operator commands are enhanced to accept a new keyword
    DISPLAY ....,XCF=( Instance_name,  ALL )
    Where:
    - Instance_name is the ACB name of the NV/AS instance to
      which the command is sent
    - XCF=ALL, the command is sent to all NV/AS instances in the
      GR group and run by all of them
    - 'XCF=' must be the last keyword in the command string
  - Command results are sent back to the command originating
    instance and displayed by that instance.
  
  4.9 - SIMPLE BROADCAST MESSAGE AS INPARM PARAMETER
  A new INPARM parameter has been added to the NV/AS
  initialization statements to allow a user to define a
  "Simple Broadcast" messagge in the initialization statements,
  rather than having to define from ADM option 8 after that NVAS
  has been started. The syntax for the new statement is:
     BRODMSG=<your message text>,
   - The BRODMSG keyword is optional,
   - it must be followed by the = sign,
   - the message text must be enclosed between minor and major
     signs
   - a comma sign must follow the major sign
   - Message text cannot span more than one lines
   - Message text can be maximum 75 characters long
   - Message text can contain any characters except "<" and ">".
   - BRODMSG keyword can be repeated on more than one line.
   - BRODMSG keyword can be used indipendently from the GRNAME
     parameter
  
  Example:
   APPL ACBNAME=I9PC96D0,PASSWORD=SECRET,
        BRODMSG=<Welcome to support Center. Services will be >,
        BRODMSG=<available from 8.00 (AM)- to 4.00 (PM)>,
        BUFFMAXN=1000,BUFFLEN=1024,..........
  
  4.10 - NEW PSEUDO TERMINAL HANDLING
  The NVAS administrator can share EMSSRTS VSAM cluster among
  different NVAS instances in a GR group and avoid conflicts
  in the use of pseudo-terminals by using a new way to define
  the pseudo-terminals logical units pool (LUNT tables).
  - Code the following statement in the NV/AS start-up job:
       //EMSLUNT DD DSN=ems.v2r1m1.inparms(ludefs),DISP=SHR
  - If EMSLUNT is coded, pseudo terminals definitions are taken
    from the partitioned dataset member pointed to by EMSLUNT
    and definitions in the EMSSRTS are ignored.
  
  EMSLUNT pseudo terminals pool definition syntax:
  - One or more sections for each pseudo terminals type (unique,
    individual and shared). Sections are optional, but if no
    sections are defined for unique or individual type,
    no pseudo terminals will be available for that type.
  - An unique or individual section may have an identifier
    (1 to 7 character string).
  - Applications defined (from ADM option 4) with
    PREFIX=identifier will only use the pseudo terminals
    defined in this section.
  - Applications whose PREFIX is different from any section
    identifier in the EMSLUNT file, will use all the
    Pseudo-Terminals defined in section that have  no identifier
    or have identifier=GENERAL
  - A section must begin with one of the following lines:
       "*NVAS-UNIQUE",  "*NVAS-INDIVIDUAL", "NVAS-SHARED"
    or, if there is a section identifier:
       "*NVAS-UNIQUE identifier",  "*NVAS-INDIVIDUAL identifier"
    Do not code anything else after the identifier.
  - One entry for each pseudo-terminal with VTAM APPL syntax:
      xxxxxxxx APPL ACBNAME=xxxxxxxx,MODETAB=......
    where xxxxxxxx is an alphanumeric 8 characters string.
  AND/OR
  - One entry for each pseudo terminals pool:
      PREFIX="prefix_name",MIN=n,MAX=m
    where prefix_name is an alphanumeric 1-7 characters string,
    n and m are in the 0-65536 range and m>=n.
    No blanks inside this statement.
    The number of prefix characters plus the number of m and n
    figures must be less or equal to 8.
  - A section must finish with "*END".
  - If two sections of the same type and with the same
    identifier are defined, one of them is ignored.
  
  EMSLUNT can directly point to SYS1.VTAMLST NV/AS LUs
  definition member.
  
  NV/AS must be recycled to activate changes in the EMSLUNT
  definitions.
  
  NV/AS does not use the pseudo-terminals pools for all the
  applications that are defined in the following way:
  - The Pseudo terminal prefix is an 8 characters
    pseudo-terminal name and ACB type is unique or individual.
  - A generic pseudo-terminal name has been specified.
  - ACB Type = N.
  
  Example of EMSLUNT definition:
   *NVAS-UNIQUE
       I9PCLU02 APPL
       I9PCLU03 APPL
       I9PCLU05 APPL
   *END
   *NVAS-INDIVIDUAL
       I9PCLI02 APPL
       I9PCLI05 APPL
   *END
   *NVAS-UNIQUE     sect1
       I9PCLU06 APPL
   *END
   *NVAS-SHARED
       PREFIX=I9PCLS,MIN=0,MAX=01
   *END
  

Local fix

Problem summary

• See Error Description
  

Problem conclusion

• See Error Description
  

Temporary fix

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

Fix information

Applicable component levels