cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Relation of SIGN and SIGN2 in license file with reservation in Options file

Relation of SIGN and SIGN2 in license file with reservation in Options file



Introduction:

When a feature contains both SIGN and SIGN2 in the license file and the keyword SIGN in the option file is assigned with value of SIGN, reservation does not work

Explanation:

  • When a feature contains both SIGN and SIGN2 in the license file and the keyword SIGN in the option file is assigned with value of SIGN, reservation does not work. However, if the keyword SIGN is assigned with the value SIGN2, reservation works as intended.

  • Reservation does not applies, when SIGN2 keyword is used instead of SIGN keyword in the RESERVE line of the option file. 

  • With respect to License file, Depending on your signature configuration, the keyword must be either SIGN or SIGN and SIGN
  • The option file present functionality only contains the information about one SIGN value. It does not record the information about second SIGN value if two entries exist in the FEATURE line(SIGN & SIGN2) .

    Under this scenario, option file functionality holds the value of SIGN2. 

    EXAMPLE :

    FEATURE Line :

    INCREMENT f1 demo 1.000 permanent 1
    VENDOR_STRING=commercial:permanent SUPERSEDE DUP_GROUP=UH \
    ISSUED=07-Apr-2021 BORROW=4320 SN=398-18816728 SIGN="XXX" SIGN2="YYY"

    OPTIONS file should be :

    RESERVE 1 f1 :SIGN="YYY" User ronald.exner

    instead of

    RESERVE 1 f1 :SIGN="XXX" User ronald.exner



    Note :

    SIGN2 is a deprecated functionality

Was this article helpful? Yes No
No ratings
Version history
Last update:
‎Feb 15, 2023 12:20 AM
Updated by:
Contributors