IBM Support

II08267: VIBTS - WIDEBAND TRANSMISSION FORMAT FOR SSP AND NTUNEMON APAR DOC. - SEE II11535 FOR THE NEW PROCEDURE TO SEND DOC. 12/98

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as canceled.

Error description

  • NOTE: This process will be discontinued Jan. 1, 1999.  The
    new process utilizing NetView FTP (NvFTP) will replace the
      current WIDEBAND/IBTS process.  Please refer to II11535 for
      details for registering and using NvFTP and ensure that your
      co-ordinator has the proper NvFTP program and is registered
      for sending doc to the NCP support origanization.
    
    SSP      565504100 565400900 568606400 566533801 566428901
             566632201
    NCPMON   566533802 566428902
    NTUNEMON 564807700 564807701 564807702
    CCP      566428901 566533801
    WIDE BAND WIDEBAND
    THE PURPOSE OF THIS INFO APAR IS TO PROVIDE DESTINATION
    INFORMATION AND REQUESTED FORMATS TO BE USED WHEN TRANSMITTING
    DATA TO THE SSP CHANGE TEAM VIA THE 'VTAM INTEGRATED BULK
    TRANSMISSION SYSTEM'(VIBTS), ALSO KNOWN AS 'WIDEBAND' OR 'IBTS'.
    REQUIRED INFORMATION:
              NODE ID:   RDC
         NETWORK NAME:   USIBMSI1
                 ATTN:   SSP WIDEBAND COORDINATOR
    ******
    JOB FILE CONTROL NUMBER : 4060 (RMJFNO=4060)
    ******
    REQUIRED FILE NAMES:
    --------------> xxxxxx.PMRyyyyy.Bzzz.Caaa.type
    WHERE:          xxxxxx IS SSPIBTS
                    yyyyy  IS PMR NUMBER (or APAR NUMBER)
                    zzz    IS THE B/O NUMBER
                    aaa    IS THE COUNTRY CODE
                    type   DESCRIBES THE FILE (eg. dump,trace,etc)
    *
    SEND 1 FILE PER TRANSMISSION.  WE CANNOT ACCEPT MULTIFILE
    FORMAT.
    *
    UNDER NO CIRCUMSTANCES USE FRP (FAITHFUL REPRODUCTION), OR
    DSS DUMP DATA SETS.
    *
    USE STANDARD LABEL TAPES.
    *
    **FAILURE TO FOLLOW ANY OF THESE GUIDELINES WILL RESULT IN
    **THE LOSS OF THE DATA SET.  IT IS RECOMMENDED THAT YOU
    **RETAIN A COPY OF THE DATA SET(S) FOR 15 DAYS FOLLOWING
    **TRANSMISSION TO ENSURE RECEIPT OF THE DATA BY THE
    **SUPPORT TEAMS.
    
    
    THE REQUESTED TAPE FORMAT FOR TRANSMISSION OF NCP DUMPS IS
    AS FOLLOWS:
    
       BLKSIZE:   512                  BLKSIZE:   2048
       LRECL  :   512    ** OR **      LRECL  :   2048
       RECFM  :   FB (OR F)            RECFM  :   FB (OR F)
    
    DUMP DATA SETS MUST USE THE FOLLOWING FORMAT:
    1)MVS - COPY THE OUTPUT FROM IFLREAD (SYSUT2) TO TAPE USING
            'IEBGENER'.  THE TAPE MUST BE UN-LABELED, AND THE
            DUMP MUST BE UN-FORMATTED.  BLOCKIZE,LRECL, & RECFM
            MUST BE AS PREVIOUSLY DESCRIBED.
    
    2)DOS - COPY THE OUTPUT FROM IFUREAD  (SYS008) TO TAPE USING
            'DITTO' OR EQUIVALENT.  THE TAPE MUST BE UN-LABELED
            AND THE DUMP UN-FORMATTED.  BLOCKSIZE, LRECL, & RECFM
            MUST BE AS PREVIOUSLY DESCRIBED.
    
    TRACE DATA SETS MUST USE THE FOLLOWING FORMAT :
    
          LRECL:  133
        BLKSIZE:  1330
          RECFM:  FBA
        DENSITY:  1600 OR 6250 BPI
    
    
    THIS INFORMATIONAL APAR IS PROVIDED AS PER THE D.O.U.
    SIGNED BY VARIOUS WIDEBAND FACILITY SITES.
    NOTE: TRANSMITTERS ARE ASKED TO RETAIN A COPY OF THEIR DATA
          SETS FOR 15 DAYS FOLLOWING TRANSMISSION OF THAT DATA.
    

Local fix

Problem summary

Problem conclusion

Temporary fix

Comments

APAR Information

  • APAR number

    II08267

  • Reported component name

    PA LIB INFO ITE

  • Reported component ID

    INFOPALIB

  • Reported release

    001

  • Status

    CLOSED CAN

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    1994-10-17

  • Closed date

    1994-10-17

  • Last modified date

    1998-12-04

  • 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

[{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SG19N","label":"APARs - OS\/390 environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"001","Edition":"","Line of Business":{"code":"","label":""}},{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SG32M","label":"APARs - VSE\/ESA environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"001","Edition":"","Line of Business":{"code":"","label":""}},{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SG19M","label":"APARs - z\/OS environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"001","Edition":"","Line of Business":{"code":"","label":""}},{"Business Unit":{"code":null,"label":null},"Product":{"code":"SG19O","label":"APARs - MVS environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"001","Edition":"","Line of Business":{"code":"","label":""}},{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SSSN3L","label":"z\/OS Communications Server"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"001","Edition":"","Line of Business":{"code":"LOB35","label":"Mainframe SW"}},{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SG27M","label":"APARs - z\/VM environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"001","Edition":"","Line of Business":{"code":"LOB16","label":"Mainframe HW"}}]

Document Information

Modified date:
04 December 1998