Default language.

Defining a default VTAM mode table entry

You should define a default mode table entry to control the request unit size (RUSIZES) parameter that VTAM uses to send BMC AMI Ops application messages to NCPs in your network.

If you do not create a default entry, VTAM could select a RUSIZES number that is too small for BMC AMI Ops product messages, which could result in message truncation.

Related topics

Defining-a-VTAM-major-node-for-the-CAS

Define-CAS-to-CAS-communication

To create a default mode table entry

  1. Use the example given in the following figure to define an entry:

             TITLE 'modetab - MODE Table - Entries'
    modetab MODETAB ,
             MODEENT LOGMODE=BBCDEF,                            X
                   FMPROF=X'13',                                X
                   TSPROF=X'07',                                X
                   PRIPROT=X'B0',                               X
                   SECPROT=X'B0',                               X
                   COMPROT=X'50B1',                             X
                   SSNDPAC=X'00',                               X
                   SRCVPAC=X'00',                               X
                   RUSIZES=X'F8F8',                             X
                   PSNDPAC=X'00',                               X
                   PSERVIC=X'060200000000000000002300',         X
                   ENCR=X'00'
             MODEEND ,
             END ,

    modetab is a mode table name that you supply. If you already have an entry with these defaults, use that entry as the modetab value in Defining-a-VTAM-major-node-for-the-CAS.

  2. Use the sample JCL in JCL for assembling a mode table entry to assemble the mode table source and link-edit it into SYS1.VTAMLIB on all systems where cross-system communication is to be enabled.

    Important

    • You can choose any name that you want for the load module. The name that you choose becomes the actual name of the mode table.
    • Before you can assemble the mode table source, you must have access to the macro library that is used to assemble VTAM applications.
    • Your system might have a user version of the VTAM definition library concatenated to the SYS1.VTAMLIB library, or it might use a different library altogether.
    • If you have a shared DASD environment where all systems share the same SYS1.VTAMLIB, you need to perform this step only once.
    //ASM     EXEC PGM=ASMBLR,PARM='OBJECT,NODECK'
    //SYSLIB   DD  DSN=SYS1.SISTMAC1,DISP=SHR
    //         DD  DSN=SYS1.MACLIB,DISP=SHR
    //SYSUT1   DD  DSN=&&SYSUT1,UNIT=VIO,SPACE=(1700,(600,100))
    //SYSTERM  DD  SYSOUT=*
    //SYSPRINT DD  SYSOUT=*
    //SYSLIN   DD  DSN=&&OBJSET,UNIT=VIO,SPACE=(80,(200,50)),
    //             DISP=(MOD,PASS)
    //SYSIN    DD  DSN=datasetname(membername),DISP=SHR
    //*
    //LINK    EXEC PGM=IEWL,PARM=(XREF,LET,LIST,NCAL,REUS),
    //             COND=(8,LT,ASM)
    //SYSLIN   DD  DSN=&&OBJSET,DISP=(OLD,DELETE)
    //         DD  DDNAME=SYSIN
    //SYSLMOD  DD  DSNAME=SYS1.VTAMLIB(membername),DISP=SHR
    //SYSUT1   DD  DSNAME=&&SYSUT1,UNIT=VIO,
    //             SPACE=(1024,(50,20))
    //SYSPRINT DD  SYSOUT=*
    //*

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*