II11512: VIBTS - IBTS TO NVFTP. NETVIEW, SA/390 AND NPM LVL2 HOW TO SEND DOC NETVIEW AND SA/390 LEVEL2.

APAR status

• Closed as canceled.

Error description

• This APAR has been opened to provide information on how to
  send documentation to the Netview and SA/390 Level2 Center
  using the NetView FTP product as a replacement for VIBTS
  The information is specifically addressed to all IBM and Tivoli
  centers that currently send documentation to the Netview Lab
  via IBTS or Wide-Band.
  The security access to the Netview Teams and to the system
  files will be implemented using the RAP security feature of the
  NetView FTP product. End of this record discusses WEB use.
  ** This procedure is valid for NetView and related products.
     (Netview, TME 10 NetView for OS/390...)
      compids: 565500700 5697b8200 and related
  ________________________________________________________________
  The Sender should verify the following information and use the
  sample JCL to submit a request to send the DOC files to his/her
  local NvFTP product:
   1. Ensure your location has the NetView FTP MVS 2.2.1 product
      installed (product - 568510801  /  fmid - HNTV230 ).
   2. Ensure your location has been registered to NetView FTP IBM
      community:(this is for VTAM LUnames and Server Group Table
      entries -  see info apar II11372 for details of getting the
      package wwsgt).
   3. Once the above conditions are in place do the following:
       A. notify the Netview Team that you have documentation to
          send (this can be handled via the pmr) and supply the
          the following information to allow them to authorize
          your transfer:
            1. TSO userid you will be using to Submit the file
               transfer request to your NvFTP
            2. Nvftp NODE name of your system
  4. Wait for reply from the Netview Team verifying the access
     profiles are in place before submitting the request to
     transfer data.  Use the sample JCL below for destination
     information:
     *********************************************************
     *** NOTE THAT LOWER CASE CHARACTERS  CAN or SHOULD    ***
     *** BE CHANGED TO MATCH YOUR ENVIRONMENT. UPPERCASE   ***
     *** KEYWORDS SHOULD BE CODED AS IS or SEE REFERENCED  ***
     *** NOTE(S) BELOW.   *(comments- should be removed)   ***
     *********************************************************
     //jcl job card info
     //JOBLIB   DD  DSN='your nvftp SDVGLMD1 dataset'
     //ADD      EXEC PGM=DVGIFBI,REGION=4M
     //SYSUDUMP DD  SYSOUT=*
     //DVGLOG   DD  SYSOUT=*
     //SYSPRINT DD  SYSOUT=*
     //SYSIN    DD  *
     FUNCTION=ADD
     XMODE=TO
     RMTNODE=RALVS6  *(can use explicit LU - see note1)
     SFILEID='source_dataset_name'
     RFILEID='NVL2.FTPnnnnn.dump'  *(nnn=pmr# / see note2)
     RSTATOPT=MNE
     SSECURP=('*','*')
     RSECURP=(NVWIBTS,NVWIBTS)
     SNOTIFY=(yourid,yournode)      *(optional parameter)
     RNOTIFY=(NVWIBTS,RALVS6)       *(verify ID/Node via pmr)
     /*
  ....
  NOTES:
  1. You may code explicit LUnames for our servers if you do not
     have RALVS6 in your Server Group Table. Our servers are
     NRANFM61, 62, 63 or 64. (i.e. you may use RMTLU=NRANFM62)
  2. You will be authorized to create the receiving dataset names
     'NVL2.FTP**' Please use your pmr number followed by the file
     type (i.e FTP12345.dump - pmr12345.log or pmr12345.trace)
  3.  Direct contact of the change team can be made via
  email (szerszek@us.ibm.com) or
  via VM szerszek AT IBMUS
     or via any person listed in callup under Steve Fediuk at
  RTP. Raleigh North Carolina
    ||||Note that this bullet is not an offer to accept
    ||||documentation via these email contacts.
  In addition to sending DOC via Netview FTP, if you
  have access to the WEB you can alternatively transmit
  doc to FTP site via anonymous and place doc at site
  testcase.software.ibm.com directory /s390/toibm/netview
     If this method is used make sure that bin is used
  and that the pmr is updated with the correct file name.
  We can then download data from this site.  Data must
  be in terse format or in non variable block format
  and we must know the lrecl and block size as well so
  that we can rebuild the data on RALVS6. (mvs)
  

Local fix

Problem summary

Problem conclusion

Temporary fix

Comments

• Closing for retention
  

APAR Information

• 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