Obtaining a Personalized FLICENSE File

How to:

FOCUS will not start unless it detects a valid ERRORS file named FLICENSE. FOCUS ships with a default FLICENSE file so that all customers can run FOCUS out of the box.

You must obtain a personalized FLICENSE for your site file as soon as possible. To get the valid FLICENSE file, contact the Customer Support Services (CSS) staff. You can either open a case at http://techsupport.informationbuilders.com/iro/newcase.jsp or call them at (800) 736-6130 or (212) 736-6130. Customer Support Consultants are available Monday through Friday between 8:00 A.M. and 8:00 P.M. EST.

The license file will be generated by CSS and emailed to you. You can then overlay the default FLICENSE file with your personalized FLICENSE file.

On z/OS, FLICENSE must be a member of the ERRORS.DATA library.

The default license file:

You should obtain a personalized license file as soon as possible and install it using the instructions in How to Download and Install the FLICENSE File.

The personalized license file will contain:

Currently, your CPUID and site code registration are not handled by the processing of the FLICENSE file. They continue to be implemented by the REGCPUID and FOCSITE zaps.


Top of page

x
Procedure: How to Download and Install the FLICENSE File
  1. Contact CSS to obtain the personalized FLICENSE file for your site.

    You can either open a case at http://techsupport.informationbuilders.com/iro/newcase.jsp or call them at (800) 736-6130 or (212) 736-6130. Customer Support Consultants are available Monday through Friday between 8:00 A.M. and 8:00 P.M. EST.

    CSS will send you an e-mail that has the FLICENSE file as an attachment named flicense.txt.

  2. Save the attachment to the hard drive on your PC.
  3. Change directories on your PC to the location in which you saved the attachment.
  4. Issue the FTP command from a command window on your PC or use a GUI FTP tool to transfer the file to z/OS:
    ftp your_mainframe_DNS_name

    where:

    your_mainframe_DNS_name

    Is the IP address or DNS name of your mainframe system.

  5. Enter the user ID on your mainframe system that will receive the FLICENSE file:
    ftp> open your_mainframe_DNS_nameĀ Connected to your_mainframe_DNS_name.
    220-FTPD1 IBM FTP CS V1R8 at your_mainframe_DNS_name, 16:13:11 on 2009-09-02.
    220 Connection will close if idle for more than 5 minutes.
    User (your_mainframe_DNS_name:(none)): userid
  6. Enter the password of your mainframe user ID (the password will not display):
    331 Send password please.
    Password:

    The following message indicates that you have successfully logged into your mainframe system and can issue FTP commands:

    230 userid is logged on.  Working directory is "userid.".
  7. Establish ASCII mode transfer:
    ftp> ascii

    The following message indicates that ASCII mode has been established, and FTP is waiting for a command:

    200 Representation type is Ascii NonPrint
  8. Transfer the FLICENSE file from your PC to a physical sequential file on the mainframe user ID:
    ftp> put flicense.txt 'userid.flicense.errors'

    The following messages indicate that the transfer was successful:

    200 Port request OK.
    125 Storing data set userid.FLICENSE.ERRORS
    250 Transfer completed successfully.
    ftp: 9105 bytes sent in 0.00Seconds 9105000.00Kbytes/sec.
  9. Exit the FTP session:
    ftp> quit
    221 Quit command received. Goodbye.
  10. Copy the transferred file to the correct location.

    Use ISPF to copy the physical sequential file to the ERRORS.DATA library as member FLICENSE, replacing the default member that was shipped with FOCUS.

    If CONFIRM is ON, you get the following message indicating that the from file (a physical sequential file) has different data set attributes from the to file (a PDS member):

    Data set attributes are inconsistent. Truncation may result in the right-most portion of some "from" records if COPY is performed.

    Press Enter to complete the copy operation.


Information Builders