IBM Support

II10281: NETVIEW FTP GUIDE FOR SENDING DOCUMENTATION TO THE IMS SUPPORT TEAM

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as canceled.

Error description

  • The purpose of this APAR is to provide information necessary
    when transmitting data/documentation via NFTP (Netview File
    Transfer Protocol) to the IBM Support Center for IMS .
    
    This procedure is valid for IMS.
    *******************************************************
    *******************************************************
                      NETVIEW FTP INSTRUCTIONS
    When supplying documentation requested by the IMS change
    teams these instructions should be followed to transmit
    the documentation using Netview/FTP.
    
    Sending sites must have STLMVS1 and server LUs ST11FT01
    and ST11FT02 (in the USIBMST network) defined in the
    Netview FTP node table.
    
    The destination should be specified as follows:
    
    ** The remote node (RMTNODE) for STL is: 'STLMVS1'
    
    ** The sending userid (USER= on JOB stmt) must be: 'FTPSEND'
    
    ** The STL userid (RSECURP) must be: 'FTPSTL'
    
    ** Allow compression to default.
    ***  ***   ***   ***   ***   ***   ***   ***   ***
    
    ** The dataset naming convention that MUST be used is:
     RFILEID='FTPIMS.PMRnnnnn.Bxxx.Cyyy.IMSrrr.zzzzzz'
      ==> 'FTPIMS' must be the high level qualifier
      ==> nnnnn = PMR number from RETAIN
      ==> xxx = branch office number from PMR
      ==> yyy = country number from PMR
      ==> rrr = IMS version/release (i.e. 510, 610, etc.)
      ==> zzzzzz = numbered dataset type (i.e. DUMP01, OLDS03,etc.)
          Dump datasets which cannot be formatted by IPCS, such as
          SYSUDUMPs, must use zzzzzz = 'SYSUDUMP' or 'DATA'.
    
    
    After sending the dataset(s) to STL, the associated PMR should
    be updated with the dataset name(s), file attributes, and a
    description of the dataset contents (i.e. syslog, SVC dump,etc.)
    
    ****************************************************************
    Sample job to send data to STL for the IMS change team:
    //NVFTPSTL JOB  USER=FTPSEND,...
    //STEP1   EXEC PGM=DVGIFBI
    //DVGLOG   DD  SYSOUT=*
    //SYSPRINT DD  SYSOUT=*
    //SYSUDUMP DD  SYSOUT=*
    //SYSIN    DD  *
     FUNCTION=ADD
     XMODE=TO
     RMTNODE=STLMVS1
     RSECURP=(FTPSTL,FTPSTL)
     RFILEID='FTPIMS.PMRnnnnn.Bxxx.Cyyy.IMSrrr.zzzzzz'
     RSTATOPT=MNE
     QSTAT=RELEASE
     SNOTIFY='your.userid'
     SFILEID='dataset.name.of.file.you.are.sending'
    /*
    
    ** FAILURE TO FOLLOW ANY OF THESE GUIDELINES MAY RESULT IN THE
    ** LOSS OF THE DATA SET.  IT IS RECOMMENDED THAT YOU RETAIN THE
    ** ORIGINAL DATA SET(S) FOR 30 DAYS FOLLOWING TRANSMISSION OR
    ** UNTIL CONFIRMATION FROM THE CHANGE TEAM IS RECEIVED TO ENSURE
    ** RECEIPT OF THE DATA BY THE SUPPORT TEAMS.
    
    *********************************************************
    Note: The IBTS information will be invalid and will be
          removed from this APAR after Februaury 1, 1999 .
          IBTS transmissions will not function after that
          date.
    *********************************************************
    

Local fix

Problem summary

Problem conclusion

Temporary fix

Comments

  • INFOAPAR IBTS IMS WIDEBAND
    

APAR Information

  • APAR number

    II10281

  • Reported component name

    V2 LIB INFO ITE

  • Reported component ID

    INFOV2LIB

  • Reported release

    001

  • Status

    CLOSED CAN

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    1997-02-18

  • Closed date

    1998-11-05

  • Last modified date

    2002-10-29

  • 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":"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"}}]

Document Information

Modified date:
29 October 2002