Updating license information

Updating license information

Overview

Option 4 UPDATE of the "License Information Menu" enables you to update license information dynamically, for example, after you have received a new license file.

The following conditions must be fulfilled for dynamic update:

  • The active license file is defined via the LST parameter Bnn_LICX_DSNAME (not via the DD statement BnnLICX).
  • The license data in the new license file is valid.

Update methods

According to your preference, you can choose between the following methods for the update after having received a new license file:

-OR-

Important: You should never use method b) without making a backup first. In case of any problems during the update, your backup enables you to revert to the original situation by restoring your backed-up license file under its original name and running option 2.4.4 again.

Note on master/slave

If you are working with BQL_SHARE_OPTION=ALL, option 2.4.4 has to be called for the license information update on the master and on each slave.

Otherwise option 2.4.4 has to be called for the license information update on the master only.

Procedure

  1. In the "Service Manager Selection Menu", choose option 2.4.4.

    The "Update License File" panel is displayed:

    PEB4LX40 ----------------------------------------------------------------------
    Command ===> _________________________________________________________________

    Update License File Subsys-ID - B92P
    Sysname - BETA

    Please enter below the name of the data set/member which contains the new
    license conditions:

    Data Set Name ===> _________________________________________________ (*)
    Member Name ===> ________ (*)

    Generate job to replace file after successful update ===> NO (**)

    (*) If you leave the fields blank, the active license file will be used.
    (**) If the data set name and/or the member name do not match the
    definition set in the current LST parameter B88_LICX_DSNAME, and the
    field is set to YES , a job is created which replaces the contents
    of the data set and/or member name of the current LST parameter
    B88_LICX_DSNAME with the contents of this data set and/or member name.

    Press the ENTER key to process the update request.
    Press the END key to return to the previous menu.

  2. Depending on your chosen update method:
    • If a), use the fields Data Set Name and Member Name to specify the name of your uploaded license file and press ENTER.
    • If b), leave the fields Data Set Name and Member Name blank and press ENTER. This means that your active license file will be used (i.e. the one defined via the LST parameter Bnn_LICX_DSNAME).

    A confirmation panel is displayed.

  3. Check the displayed file names carefully. If they are correct, type Y in the Confirm field and press ENTER to initiate the update.

    PEB4LX44 ---------------------------------------------------------------------
    Command ===> _________________________________________________________________

    Update License File Subsys-ID - Q93V
    Sysname - BETA



    Current License File: BETA.LICX(LICX)

    New License File : BETA.LICX.ALT(NEWLICX)





    Confirm ===> Y (Y/N)




    Press the ENTER key to confirm your request.
    Press the END key to abort the update request.

    If the update was okay, panel PEB4LX40 is displayed again with the Update successful (RC-0) message.

    The rest of the procedure is only of interest if you have chosen method a).

  4. When you are returned to the previous panel, enter YES in the Generate job... field to generate JCL for a copy job.
  5. Specify a sysout class and modify or confirm the job card in the displayed panel to continue with the batch job generation.

    PEB4LX45 ---------------------------------------------------------------------
    Command ===>

    Update License File Subsys-ID - Q92S
    Sysname - BETA

    SYSPRINT Options:

    Sysout Class ===>


    Job Card:
    ===> //COPLICX JOB 1,ACCOUNT,CLASS=A,MSGCLASS=P,NOTIFY=&SYSUID
    ===> //*
    ===> //*
    ===> //*





    Press ENTER to continue with the batch job generation.
    Press END to abort the batch job generation.

    The generated JCL is displayed in the ISPF editor. You can submit the job immediately or save the JCL for later use.

Result

If the license data in the new license file is valid:

  • The active license information is updated.
  • If you have chosen method a) and specified YES in the Generate job... field, submit the generated JCL to make the change permanent. Otherwise, the change will only be reflected in the STC and will only be temporary.
  • The new dataset name and details of the change can be displayed under option 2.4.1:

    Data Set Name : ALLSYS.Q92.TEST2.LICX
    Obtained from : Dynamically overwritten by USERBSA on 2017-12-19 at 14:47:47

Fields

Field

Description

Data Set Name

Dataset name of the license file.

Member Name

Member name if this is a PO dataset.

Generate job to replace file after successful update

If YES, JCL for a batch job is generated that replaces your active license file with the specified new license file.

Default=NO