Skip to main content

Software  >  Networking  >  

VSE Updates to VTAM V4R2 Resource Definition Reference (Information APAR II09886)
 Manual
 
Abstract
This Techdoc was created to contain VSE updates to the VTAM V4R2 Resource Definition Reference (SC31-6498-01).
 
 
Content

Chapter 4. Start Options: Buffer pool
1. This section on specifying buffer pool options has several references to IOBUF sizes that say, "... add 87 bytes to the specified bufsize value ...". These should all be changed to "... add 71 bytes to the specified bufsize value ...".
2. Table 66 "IBM-Supplied VTAM Buffer Pool Values" has a reference to note 4 by the bufsize 120 in the LFBUF row. That note is not applicable to LFBUF for any operating system. LFBUF bufsize cannot be modified. If it is, IST447I BUFFER SIZE WAS IGNORED FOR ONE OR MORE POOLS will be issued. (MSGIST447I)

DY43650 DUMP PROCESSING OF ABEND0A9 ISTLSCPA, RESULTS IN IST446I I/O ERROR - TIMEOUT, AND CHANNEL ACTIVITY HANGS. MSGIST446I

P. 174

Underneath NOTE: add...

NOTE: The IBM 3172 Interconnect Controller will try to maintain continuous availability of the SSCP -> PU session when there is an XCA major node configured for Network Management, MEDIUM=BOXMGR. The BOXMGR session ends only when either VTAM terminates or the last XCA major node associated with the IBM 3172 Interconnect Controller comes down. If this connection is terminated for any other reason, the IBM 3172 Interconnect Controller will attempt to re-establish this connection.


DY43654 ACTIVATE XCA 081C0000 ON EACH LINK DEFINED


P. 168:

num_stmts, under AUTOGEN currently reads::

num_stmts
specifies the number of VTAM-generated LINE and PU statements. Code a decimal value in the range 1 - 4096. This value is required.

num_stmts will be changed to read::

num_stmts
specifies the number of VTAM-generated LINE and PU statements. Code a decimal value in the range 1 - 4096. This value is required.
.
NOTE: If using the XCA definition to define a D/T3172 then::
.
num_stmts
specifies the number of VTAM-generated LINE and PU statements. Code a decimal value in the range 1 - 255, or

if OF/2 is being utilized in the 3172, then the range is 1 - 245. This value is required.


DY43760 SUPPLY LOGMODE ENTRY FOR 3174 DLUR

The VTAM V4R2 Resource Definition Reference, SC31-6498-01, contains the VTAM Default LOGMODE Table, ISTINCLM, in Appendix A. When this manual is updated, ISTINCLM will contain this new
entry for 3174 DLUR:

DLUR MODEENT LOGMODE=DLUR,FMPROF=X'03',TSPROF=X'03',
PRIPROT=X'B1',SECPROT=X'90',COMPROT=X'3080',
SSNDPAC=X'04',PSNDPAC=X'04',RUSIZES=X'8787',
PSERVIC=X'028000000000185000007E00',
APPNCOS=#CONNECT



DY43784 NEW FUNCTION FOR LOCAL NON-SNA

On page 203 for 4.2 in table 22 add the following:

Operands

BUFNUM

On page 205 for 4.2 add the following for Operand descriptions:

BUFNUM Specifies a number between 1 and 255 inclusive for the number of IO buffers to be used for
    reading from a device. This is useful for devices that are not properly emulating 3x74 type devices. This will help ensure that the screen is fully read when VTAM issues READ and READ Modifies to the device. BUFNUM should be set so that BUFNUM*IOBUF size is large enough to get all of the data from a screen.





DY43813 START OPTION SWNORDER NO LONGER FUNCTIONS AS EXPECTED

SWNORDER Operand Description (VTAM V4R2 Resource Definition Reference, pages 178, 348, and 394) is changed as follows:

|+--SWNORDER=value_of_swnorder_start_option--+                            
       |                                           |                            
    >--+-------------------------------------------+-->                        
       |                                           |                            
       |            +--CPNAME---+                  |                            
       |            |           |                  |                            
       +--SWNORDER=-+-----------+------------------+                            
                    |           |                                              
                    +--STATNID--+                                              

statements: GROUP, LINE
dependency: none

| specifies the way VTAM locates a switched PU. If you do not code this operand the default is the value of | the SWNORDER start option.

| If VTAM does not find the PU using the SWNORDER you specify, it searches using the other method. For | example, if you code SWNORDER=CPNAME and VTAM cannot find a PU with a matching CPNAME, it will | then search by the station identifier (IDBLK and IDNUM operands on the PU definition statement for the
| switched major nodes).

This operand overrides the SWNORDER start option value.

SWNORDER=CPNAME
specifies that VTAM searches for a switched PU by the CPNAME first.

SWNORDER=STATNID
specifies that VTAM searches for a switched PU by the station identifier first.

SWNORDER Start Option Description (V4R2 page 586) is changed as follows:

    +--SWNORDER=CPNAME--------------------------+                            
      |                                           |                            
   >--+-------------------------------------------+-->                          
      |                                           |                            
      +--SWNORDER=-+--CPNAME---+------------------+                            
                   |           |                                                
                   +--STATNID--+

specifies the way VTAM locates a switched PU. If you do not code SWNORDER, VTAM searches for a PU by the CPNAME first. If VTAM does not find the PU by the CPNAME, it searches by the station identifier (IDBLK and IDNUM operands on the PU definition statement for the switched major nodes).

| You can change the value of SWNORDER with the MODIFY VTAMOPTS | command while VTAM is
| running. You can override this start option for specific resources by coding the SWNORDER operand
| on the GROUP or LINE statements.

SWNORDER=CPNAME

specifies that VTAM searches for a switched PU by the CPNAME first.

SWNORDER=STATNID

specifies that VTAM searches for a switched PU by the station identifier first.


DY43827 SESSION SETUP FAILS WITH 08970007

On page 144, in the writeup under VFYOWNER=NO, change:

"the CDRSC is updated with the owning SSCP name received, unless the CDRSC is across the APPN-subarea boundary and the two conditions listed under VFYOWNER=YES are met:
- The CDRSC is predefined with the NETID operand on the NETWORK definition statement.
- CDRM=cdrmname is coded."

to:

"the CDRSC is updated with the owning SSCP name received, unless the CDRSC is across the APPN-subarea boundary and CDRM=cdrmname is coded."


DY43890 WARM START FAILS FOR ISTTRL MSGIST116I MSGIST061I

VTAM V4R2 Resource Definition Reference (SC31-6498-01) needs to be updated to remove the CONFGDS and CONFGPW operands from theTransport Resource List Major Node (pages 459-460: Table 40, Full Syntax for VBUILD, and Operand Descriptions).


DY43968 FUNCTIONAL ENHANCEMENT RESETLU KEYWORD FOR A DEPENDENT LU

The VTAM V4R2 Resource Definition Reference (SC31-6498-01) will be changed to include the new RESETLU keyword.

LOCAL SNA Major Node
RESETLU=YES|NO (default is YES)
statement: PU, LU


Network Control Program (NCP) Major Node
RESETLU=YES|NO (default is YES)
statement: Group,Line,PU,LU

Switched Major Node
RESETLU=YES|NO (default is YES)
statement: PU, LU

LU Group Major Node

RESETLU=YES|NO (default is YES)
statement: LU

Model Major Node
RESETLU=YES|NO (default is YES)
statement: LU

determines if a DACTLU followed by an ACTLU should
be sent to the LU when a session is terminated with
a flavor of Cleanup.

RESETLU=YES
allows a DACTLU-ACTLU to flow to an LU when the
LU-LU session terminates with a Cleanup flavor.

RESETLU=NO
prevents a DACTLU-ACTLU from flowing to an LU when the

LU-LU session terminates with a Cleanup flavor.

DY44152 NEW FUNCTION FOR VSE/ESA VTAM 4.2

Under 2.15.7.50 MAXDATA, change the sentence "MAXDATA is ignored for type 2.1 nodes attached through an NCP or a 3172 controller." to "MAXDATA is ignored for type 2.1 nodes attached through an NCP, a 3172 controller, or an Open Systems Adapter (OSA)."


DY44211 IST322I CONFIGURATION COSAPPN INVALID VALUE IST323I LABEL= NA MACRO=LINEROW KEYWORD=CAPACITY

The VTAM V4R2 Resource Definition Reference (SC31-6498-01) has been changed to add to the range of values allowed for min and max under the CAPACITY operand for APPN Class of Service:

1K-1000K and 1M-1000M


DY44212 RETRIES=NONE IS NOT VALID IN THE GROUP WITH VTAM 420

The VTAM V4R2 Resource Definition Reference (SC31-6498-01) defines the format of the RETRIES keyword for the NCP major node incorrectly. The format has been changed as follows (note the comma before pause_interval):

RETRIES >------------------------------------------------->                  
             |--RETRIES=(,pause_interval,maximum_retries)--|

range: 0-255 should be changed to:
range: pause_interval - 0-255
maximum_retries - 0-127

The sentence beginning 'If neither pause_interval nor n is
specified...' should be changed to:
If neither pause_interval nor maximum_retries is specified,
the RETRIES operand is ignored.


DY44294 PERFORMANCE PROBLEMS WHEN NETLEVEL IS LEFT TO DEFAULT (80) AND LENGTH GREATER THAN 1024

VTAM V4R2 Resource Definition Reference (SC31-6498-01), Packet Major Node must have the following changes:                                
                                                                 
Tables 34 and 35 need to be updated to indicate that there is a dependency between NETLEVEL and PLENGTH.                        
                                                                 
In the section describing the NETLEVEL keyword the following should be added:                                                
 'If NETLEVEL=80 is coded or defaulted, PLENGTH must be coded no greater than 1024 on this PORT or any VCPARMS statements.'    

In the section describing the PLENGTH keyword the following should be added:                                              
 'If PLENGTH=2048 or PLENGTH=4096 is coded the NETLEVEL keyword on the PORT statement must be set to 84.'
 

DY44621 TG NEGOTIATION DONE ON REMOTE PREDEFINED TG - XID FAILS IN REMOTE CP WITH SENSE 10160016

VTAM V4R2 Resource Definition Reference (SC31-6498-01)
 o Local SNA Major Node, 2.10.3.46 TGN              
 o NCP Major Node, 2.13.5.109 APPN TGN              
 o Packet Major Node (VM/VSE), 2.14.5.63 APPN TGN    
 o Switched Major Node, 2.15.7,83 APPN TGN

  Change the second paragraph so that it reads:                
 .                                                              
By specifying a tg_number you indicate a predefined TG that must be accepted by the partner node.


DY44681 XCA MAJOR NODE MEDIUM=CSMACD WITH PUTYPE=4

Under External Communication Adapter Major Node, the PUTYPE operand description should be changed for PUTYPE=4 to:

PUTYPE=4
specifies a connection to an IBM 37xx Communication Controller running NCP/Token-Ring interconnection (NTRI) or a connection through a CSMA/CD 802.3 LAN to a 37xx Communication Controller running NCP. Specify PUTYPE=4 only if MEDIUM=RING or MEDIUM=CSMACD on the PORT definition statement.


DY44818 ADD CLRSESSQ SUPPORT FOR DEPENDENT, SWITCHED LU'S :

VTAM V4R2 Resource Definition Reference (SC31-6438-01) has been updated to include the CLRSESSQ support for Model Major Nodes and Switched Major Nodes as follows:

SECTION 2.11 - MODEL MAJOR NODE:

In sections 2.11.2 PU Definition Statement and 2.11.3 LU Definition Statement, add the following alphabetically in the list:

CLRSESSQ=YES|NO (default is NO)

Specifies whether a dependent LU is forced into an inhibited session state when the LU is disabled.
When the LU is enabled, it is returned to normal status. Sessions, however, are not connected.

CLRSESSQ=NO
Specifies that the LU is not forced into inhibited session state. NO is the default.

CLRSESSQ=YES
Specifies that the LU is forced into inhibited session state. Both active and pending sessions are
removed from the session queue.

SECTION 2.14 - SWITCHED MAJOR NODE:

In sections 2.14.6 PU Definition Statement and 2.14.8 LU Definition Statement, add the following alphabetically in the list:

CLRSESSQ=YES|NO (default is NO)

Specifies whether a dependent LU is forced into an inhibited session state when the LU is disabled.
When the LU is enabled, it is returned to normal status; sessions, however, are not connected.

CLRSESSQ=NO
Specifies that the LU is not forced into inhibited session state. NO is the default.

CLRSESSQ=YES
Specifies that the LU is forced into inhibited session state. Both active and pending sessions are
removed from the session queue.


DY44972 ALLOW PACING / VPACING SPECIFICATION ON DYNAMICALLY CREATED ILUS



Under the MODEL Major Node, Table 32 - Model Major Node Definition Statements and Operands:  


Page 248-249, under PU, add:                                  
Operands   Page  .....  Default  .....                        
PACING     272          1                                    
VPACING    279          2                                    
                                                             
Under Full Syntax for the PU statement in the MODEL major node on page 250-251, add:
                                       
   -----PACING=1------------------------                      
   |                                   |
>-------------------------------------------->    
   |             ---1---------------   |          
   |             |                 |   |          
   -----PACING=-------------------------          
                 |                 |              
                 ---pacing number---              
                                                 
   -----VPACING=2-----------------------          
   |                                   |          
>-------------------------------------------->
                                                               
   |             ---2----------------  |                      
   |             |                  |  |                      
   -----VPACING=------------------------                      
                 |                  |                        
                 ---vpacing number---                        
                                                               
Under Operand Descriptions for PACING (page 272) and VPACING (page 279), add PU to the statements:
                     
 statements: PU,LU  
                                           
Also add a note under each description:
NOTE: If a dynamic CDRSC (ILU) uses a dynamic PU created from a MODEL definition, the PACING (or VPACING) values are obtained from the PU definition in the MODEL major node that was used to define the dynamic PU.


DY45021 SNS 08090000 ACTIVATING DLUR SUPPORTED PUS


Chapter 2 Major Nodes,      
Switched Major Node, CPNAME keyword, DLUR physical units:      
                                                               
The third sentence should be changed to read 'Code CPNAME only when the DLUR is not adjacent (has no APPN connections, predefined or dynamic, with the DLUS).  If the DLUR is adjacent, you must use a different means of identification dependent upon DLC support.'


DY45029 MODE #BATCHC & #INTERC MISSING IN ISTINCLM THE SESSION CAN'T BE STARTED BECAUSE OF MISSING MODES


The VTAM V4R2 Resource Definition Reference (SC31-6498-01) contains the VTAM Default LOGMODE Table, ISTINCLM, in Appendix A. When this manual is updated, ISTINCLM will contain these new entries:

#BATCHC  MODEENT LOGMODE=#BATCHC,FMPROF=X'13',TSPROF=X'07',
               ENCR=B'0000',SSNDPAC=3,RUSIZES=X'F7F7',    
               SRCVPAC=3,PSNDPAC=3,APPNCOS=#BATCH

#INTERC  MODEENT LOGMODE=#INTERC,FMPROF=X'13',TSPROF=X'07',
               ENCR=B'0000',SSNDPAC=7,RUSIZES=X'F7F7',    
               SRCVPAC=7,PSNDPAC=7,APPNCOS=#INTER    



DY45033 ADD DLRORDER START OPTION

Switched Major Node, Operand Descriptions, CPNAME

In 'DLUR physical units:' change it to say

For DLUR-defined PUs, CPNAME may be specified for a single PU which in non-adjacent to the DLUS (non-adjacent means there is no APPN connection between the DLUS and the control point named via CPNAME). When the DLUR-defined PU is adjacent to the DLUS, or when more than one PU with the same CPNAME must be defined, a different means of identification dependent upon DLC support must be used For example, IDBLK/IDNUM for Internal PUs). Additional information can be found in the VTAM Network Implementation Guide and in the publications for your DLUR implementation.

Start Options

In 'Start Options Syntax Diagrams' add

       .-DLRORDER=STATNID-------.                    
    >--+------------------------+------------------->
        -DLRORDER=-+-STATNID-+--'                    
                    -CPNAME--'                      

In 'Session Control Start Options' add

+-----------+-----------------------------------+  
                                                       
    | DLRORDER  | The way VTAM locates a DLUR PU    |  
    +-----------+-----------------------------------+  

In 'Description of Start Options' add

DLRORDER

        .-DLRORDER=STATNID-------.                    
    >>--+------------------------+----------------->>  
         -DLRORDER=-+-STATNID-+--'
                                                               
                    -CPNAME--'                                
                                                               
    specifies the way VTAM locates a DLUR PU.  If you do not code DLRORDER,    VTAM searches for a DLUR PU by the station identifier (IDBLK and IDNUM operands on the PU definition statement for the switched major nodes)first.  If VTAM does not find the PU by STATNID it searches for the DLUR PU by CPNAME.                                                    
                                                                   
    You can change the value of DLRORDER with the MODIFY VTAMOPTS command while VTAM is running.                      
                                                               
  DLRORDER=CPNAME                                              
     specifies that VTAM searches for a DLUR PU by the CPNAME first.                                                    
                                                               
  DLRORDER=STATNID                                              
      specifies that VTAM searches for a DLUR PU by the station identifier first (default).  NOTE: For regular (non-DLUR) switched PUs see the SWNDORDER start option.                                              
                                                               
 In 'Description of Start Options', SWNORDER, add              
                                                               
    NOTE: SWNORDER controls only regular (non-DLUR) switched PUs.  For DLUR-defined PUs see the DLRORDER Start Option.    

                                                                       
DY45057 START OPTION DYNADJCP=NO DOES NOT PREVENT ADJCP CONNECTIONS

For each major node which allows the DYNPU operand, modify the list of DYNPU operand default exceptions so that it does not include DYNADJCP=YES.


DY45064 IST322I IST323I INVALID VALUE, MACRO=LINE, KEYWORD=RETRIES WHEN LNCTL=BSC AND RETRIES=(3,5,255)

For the NCP Major Node the RETRIES operand description must show the syntax as

  >--+------------------------------------------------+-->    
     |                                                |      
     +-- RETRIES=(,pause_interval,maximum_retries,) --+      

and must indicate that for LNCTL=BSC or LNCTL=SS the range for maximum retries is 0-255, otherwise it is 0-127.





DY45099 AE APAR - COMPLETION FOR DY44839


Under the Topic External Communication Adapter (XCA) Major Node a new parameter will be supported for the Subarea XCA PU macro.

Table 21 External Communication Adapter Major Node-Subarea Node

NAME     DEFINITION     Operands        Default                
_______________________________________________

                                                     
name     PU             MACADDR                      
                        ISTATUS         ACTIVE      
                        MULTGSUP        YES          
                        PUTYPE          5            
                        SAPADDR         4            
                        SPAN                        
                        SUBAREA         in_xid_value
                        TGN             1    

MULTGSUP                                          
                ------MULTGSUP = YES ------        
               |                           |      
          >----|---------------------------------->
               |                           |      
               |                   -YES-   |      
                ----MULTGSUP = ---|-----|--        
                                   -NO--          

                                                               
           statements: PU (subarea node)                      
           dependency: none                                    
           
          specifies whether Multi-Link TGs are supported on this connection.  For most configurations, the MULTGSUP parameter should be YES.                  
                                                               
          When the default is used, or MULTGSUP is explicitly coded to YES, the XIDs received from the connecting node must have the XID2 Multiple-link TG support bit turned ON, meaning Multiple-link TGs are supported.  In addition, VR TG sequence number checking on inbound PIUs will be performed.        
                                                             
          When coded to NO, the XIDs received from the connecting node will be allowed to have the XID2 Multiple-link TG support bit OFF, meaning Multiple-link TGs are not supported.  In addition, VR TG sequence number checking on inbound PIUs will not be performed.                              
                                                             
           **** WARNING ****                                  
          If coded incorrectly, this could cause Subarea XCA connections to fail at activation. This parameter is introduced to support Subarea XCA connections which traverse mediums that do not support Multi_link TGs.  The specific configuration which required this parameter follows:
            VTAM A/OSA ===tkr=== 2210 ---X.25 PSDN--- NPSI/NCP === VTAM B
                                                             
          In this case, the NPSI/NCP X.25 connection does not support multi-link TGs.  


    DY45360 IST321I IST323I FOR PUTYPE=4 WHEN MEDIUM=FDDI


    The VTAM V4R2 Resource Definition Reference (SC31-6498-01) will be changed under External Communication Adapter Major Node, PUTYPE, PUTYPE=4 to state simply:
                                 
    PUTYPE=4                                                        
      Specifies a connection to an IBM 37xx Communication Controller


    DY45707 IST530I FLOODS CONSOLE AND EFFECTIVELY HANGS VTAM


    The VTAM V4R2 Resource Definition Reference (SC31-6498-01), under the Start Options Syntax Diagrams and the Descriptions of Start Options, will be changed to default IOMSGLIM to 100:

        ---IOMSGLIM=100-----------------------                                  
           |                                    |                                  
       >------------------------------------------->                                
           |                                    |                                  
           ---IOMSGLIM=number_of_message_pairs---  


    DY46311: COMMUNICATION CONTROLLER FOR LINUX ON ZSERIES V1R1 SUPPORT


    In Chapter 2 ("Major nodes") in the "External communications adapter (XCA) major node" section, the following subsections are updated:

    - In the "PU Definition Statement" section under "Subarea XCA" (2.7.1.5), a new row is added to the table of valid operands (Table 21) for XCA subarea nodes (alphabetically under the PU definition statement) and appears as follows: 

                                                        
         Operand     Topic   Required  Sift effect  Default   
         ALLOWACT    (tbd)    (no)      (none)       NO


    NOTE that "(no)" and "(none)" should NOT appear in the table; these columns should remain blank. Also, "(tbd)" should be replaced by a hyper-text link to the new section describing this new operand (see below).

    - Under "Full Syntax", under the "PU" definition statement, the railroad tracks are updated to include (in alphabetical order) the new ALLOWACT operand as shown below:

             _ALLOWACT=NO_______          
                                                                 
        >___|___________________|___>                            
            |            _NO__  |                                
            |_ALLOWACT=_|_____|_|                                
                        |_YES_|                                  

    - "Operand descriptions": A new section is added (in alphabetical order) to describe the new ALLOWACT operand as shown below:

    ALLOWACT

              _ALLOWACT=NO_______                                  
          >___|___________________|___>                              
              |            _NO__  |                                  
              |_ALLOWACT=_|_____|_|                                  
                          |_YES_|                                    

    Specifies whether this physical unit (PU) allows activation of an NCP major node for an NCP running on the "Communication Controller for Linux on zSeries" product. (See Chapter 21 "Operating with an NCP" in the z/OS Communications Server: SNA Network Implementation guide for more information on running NCPs with the "Communication Controller for Linux on zSeries" product.)

    ALLOWACT=NO
    This physical unit does not allow activation of an NCP major node for an NCP running on the Communication Controller for Linux on zSeries" product.

    ALLOWACT=YES
    This physical unit allows activation of an NCP major node for an NCP running on the "Communication Controller for Linux on zSeries" product.


    DY46363 IST319I IST323I WHEN NETID=(,NOXNETLS)

    The VTAM V4R2 Resource Definition Reference (SC31-6498-01) is missing NOXNETLS information for PUs in Local SNA, Model, Channel_Attachment (SDLC non-switched), and Packet major nodes. The following should be added under NETID for each of these major nodes:

    NETID=(,NOXNETLS)
    specifies that VTAM does not allow nonnative network attachment for LU-LU sessions for this PU. When NETID=(,NOXNETLS), VTAM indicates to the NCP that this PU will use VTAM's native network ID.

    LU-LU sessions should fail if the NETID sent in the bind from the LU is different than the NETID specified in VTAM, even though PU-PU connections can establish. If no NETID is included in the bind, or if the NETID is the same as that specified by VTAM, the LU-LU session should activate.

    NOTE: NETID=(,NOXNETLS) is valid only when YES is specified on the XNETALS start option. If NETID=(,NOXNETLS) is coded and XNETALS=YES is not coded, NETID defaults to the native network ID, and a message is issued that NETID has the wrong value.  


    DY46471: New Function VTAM 31 BIT I/O BUFFER Support

    Please add new section for new VSE only start option IOBUF31 after section 4.4.51 (INOPDUMP).

    IOBUF31 (VSE)

          _IOBUF31=NO________                                                      
     >>__|___________________|____________________________________><                
         |_IOBUF31=_ _YES_ __|                                                      
                    |_NO__|                                                        

    IOBUF31 is a VSE only start option, and requires a specific level of z/VSE. It allows the VSE system administrator to control the VTAM allocation for system storage associated with IO operations. The two primary storage areas that are controlled by the IOBUF31 setting are:

    1. VTAM IO buffers (IOBUF pool)
    2. VTAM packing buffers (used for CTC based DLCs)

    This option allows VTAM to exploit 31 bit storage for IO operations. The default for IOBUF31 is NO, meaning the IO buffers will be restricted to 24 bit storage. When YES is specified, VTAM will use 31 bit storage for the IO buffer pool and packing buffers (related to CTC based devices). This option is not modifiable.

    IOBUF31 = NO
    When IOBUF31 defaults to NO or is specified as NO, VTAM will allocate all IO buffers below the 16 megabyte line (24 bit storage).

    IOBUF31 = YES
    When IOBUF31 is specified as YES, VTAM will allocate all IO buffers (and CTC packing buffers) above the 16 megabyte line (31 bit storage). When YES is specified VTAM will not support any ICA (Integrated Communications Adapter) attached devices (SDLC, BSC, X.25 and LAN). When YES is specified, ICA resources can not be activated.                                                                                                                                                                                                
                                                             
     
     
    		 

    Copyright and trademark information
    IBM, the IBM logo and ibm.com are trademarks of International Business Machines Corp., registered in many jurisdictions worldwide. Other product and service names might be trademarks of IBM or other companies. A current list of IBM trademarks is available on the Web at "Copyright and trademark information" at www.ibm.com/legal/copytrade.shtml.
    Rate this page
    Please take a moment to complete this form to help us better serve you.
    This material provides me with the information I need.




    This material is clear and easy to understand.




    Did the information help you to achieve your goal?
    What updates, improvements, or related information would you like to see in this document?
    Your response will be used to improve our document content. Requests for assistance, if applicable, should be submitted through your normal support channel as we cannot respond from this site.
    Input the verification number to submit feedback:
    Document information
     Product categories:
     Software
     Networking
     Enterprise Connectivity
     VTAM for VSE/ESA and VM/ESA
     All
     Operating system(s):
      VSE/ESA
     Software version:
      4.2
     Reference #:
      7012028
     IBM Group:
     Software Group
     Modified date:
     2008-05-26

    Translate My Page
     
     

    Rate this page

    Help us improve this page. Your response will be used to improve our document content. Requests for assistance, if applicable, should be submitted through your normal support channel as we cannot respond from this site.