Default language.

Creating a mode table entry to correct a sense code of 800A0000


Use the following procedure to prevent data truncation by accommodating the buffer size of your network channel programs (NCPs). If you receive a message in the SYSLOG that contains sense code 800A0000, at least one of the network channel programs (NCPs) in your network has a message buffer that is smaller than the BMC AMI Ops default buffer of 3840 bytes. As a result, some of the data that is traveling to that system is truncated. To prevent this situation, you must create an entry in the mode table to accommodate the NCP buffer size.

Perform the following steps on all systems that are connected to the NCP:

To create a mode table entry to correct a sense code of 800A0000

  1.  Add the entry shown in the following figure to the mode table that you created in Defining-a-default-VTAM-mode-table-entry.

             TITLE 'BBMODEA - MODE Table - Entries'
    BBMODEA  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 ,

             MODEENT LOGMODE=logmode,                           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'yyyy',                             X
                   PSNDPAC=X'00',                               X
                   PSERVIC=X'060200000000000000002300',         X
                   ENCR=X'00'
             MODEEND ,
             END ,

    The variables are as follows:

    • logmode is the name of the entry that you are adding.
    • RUSIZES=X’yyy’ is a hexadecimal number that is as close to 3840 bytes as possible.

  2. Check the MAXDATA parameter in the NCPGEN for the NCP that is used to communicate with the failing system. To accommodate as much data as possible, use the following table to find the number that is closest to this MAXDATA value. The number that you choose must be at least 15 bytes smaller than the MAXDATA value.

    B

    A

    8

    A

    9

    A

    A (10)

    A

    B (11)

    A

    C (12)

    A

    D (13)

    A

    E (14)

    A

    F (15)

    5

    256

    288

    320

    352

    384

    416

    448

    480

    6

    512

    576

    640

    704

    768

    832

    896

    960

    7

    1024

    1152

    1280

    1408

    1536

    1664

    1792

    1920

    8

    2048

    2304

    2560

    2816

    3072

    3328

    3584

    3840

    9

    4096








    For example, if you choose to specify 3072, determine its hexadecimal representation by finding the number's value in the A columns, which is 12 (C). Then, find its value in the B column, which is 8. So, you would specify C8C8 on the RUSIZES parameter.

    Important

    You need to repeat the digits because the RUSIZES parameter contains two bytes. The first byte (AB) reflects the size of the incoming NCP buffer; the last byte (AB) reflects the size of the outgoing buffer. Usually, these two numbers are the same.

  3. Assemble the mode table source and link-edit it into SYS1.VTAMLIB on all CAS systems where cross-system communication is enabled. You can use the sample JCL in Defining-a-default-VTAM-mode-table-entry for this step.

  4. In the member that contains the system VTAM definition, add the MODETAB operand to the APPL statement as shown:

    VBUILD TYPE=APPL
    name   APPL AUTH=(ACQ),PARSESS=YES,MODETAB=module,
    DLOGMOD=BBCDEF

    The variables are as follows:

    • name is the name that you assigned to the system image for the CAS.
    • module is the name of the load module that you created in Step 1 (VTAM mode table entry for NCP).

  5. Enter VARY NET,INACT,ID=name to deactivate the major node member.

    Important

    This command causes a service interruption for any active terminal sessions.

  6. Enter VARY NET,ACT,ID=name to reactivate the member and make the MODETAB parameter accessible to VTAM.

 

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