XYGATE License Expiration
XYGATEAC
Product license file: P06F001
Macro to install license: XAC_INSTALL_LICENSE
Expiration behavior: The DBSO program reads the license file on startup to determine when the license will expire. The license is checked once each day from then on until the DBSO program is stopped. Starting two weeks before the license expires, a countdown message is placed in the XYGATEAC startup banner. When the license is expired, the program writes an error message to the home terminal of the DBSO program and stops.
Please note that an expired license can impede access to the system if XYGATEAC controlled TACLs are in use.
XYGATEPC
Product license file: P07F001
Macro to install license: XPC_INSTALL_LICENSE
Expiration behavior: The XYGATEPC program reads the license file at every program invocation. Starting 30 days before the license expires, a countdown message is written to EMS. When a license does not exist, an EMS message is reported. If the license has expired, an EMS message is written, a message is also written to the home terminal, and the program terminates.
XYGATECM
Product license file: P08F001
Macro to install license: XCM_INSTALL_LICENSE
Expiration behavior: The XYGATECM process reads its license initially when it is started. From then on, it only checks to see if the timestamp on the license file has changed or if the LOAD-CONFIG command is executed. If the timestamp has changed, the license is re-read. When the expiration date is reached, XYGATECM writes an error message to its home terminal and stops.
XYGATESP
Product license file: P09F001
Macro to install license: XSP_INSTALL_LICENSE
Expiration behavior: The XYGATESP server does not report any licensing error messages at all. When it is started less than 30 days to expiration or if the license does not exist or of the license has expired, no message of any kind is displayed.
XYGATESR
Product license file: P23F001
Macro to install license: XSR_INSTALL_LICENSE
Expiration behavior: The XYGATESR server reads the license file each time it is invoked. Starting 30 days before the license expires, a countdown message is written to EMS. When a license does not exist, an EMS message is reported. If the license has expired, an EMS message is written, a message is also written to the home terminal, and the program terminates.
XYGATEOS
Product license file: $vol.subvol.P19F001
Macro to install license: XOS_LICENSE_INSTALL
Expiration behavior: The XYGATEOS program reads the license file on startup. From then on, once every 24 hours it checks to see if the timestamp on the license file has changed. If the timestamp has changed, the license is re-read. If the license expiration is in less than 30 days then XYGATEOS will audit the warning message that the license is going to expire in less than 30 days.
If the license file is bad or expired then XYGATEOS will return NORECORD for all requests. For the first request after the license has expired, XYGATEOS will audit that it will return NORECORD for all subsequent requests.
XYGATEPQ
Product license file: P15F001
Macro to install license: XPQ_INSTALL_MACRO
Expiration behavior: The XYGATEPQ program reads the license file at every program invocation. Starting 30 days before the license expires, a countdown message is written to EMS. When a license does not exist, an EMS message is reported. If the license has expired, an EMS message is written, and the program terminates.
XYGATEUA
Product license file: P25F001
Macro to install license: XUA_INSTALL_MACRO
Expiration behavior: The XYGATEUA program reads the license file on startup. From then on, once every 24 hours it checks to see if the timestamp on the license file has changed. If the timestamp has changed, the license is re-read. If the license expiration is in less than 30 days then XYGATEUA will audit the warning message that the license is going to expire in less than 30 days.
If the license is expired, only SUPER.SUPER and the owner of the XYGATEUA installation can log on to the system. When the owner or SUPER.SUPER has installed the valid license file, the XUGATEUA server needs to be stopped and restarted.
XYGATESW Host
Product license file: P44F001
Macro to install license: XSW_INSTALL_LICENSE
Expiration behavior: When the XYGATESW program, which coordinates all data collection, receives the command to start a new collection, it checks its expiration date. If the expiration date is within the next two weeks but has not expired, a warning message is passed back to the client where it is displayed as part of the collection start. If the expiration date has been reached, a warning message is passed back to the client and the collection is not started.
XYGATESW Client
Product license file: <install directory>/xsw_cpf/P47F001
Macro to install license: n/a
Expiration behavior: When the XYGATESW client is started, the license is checked. If it is not valid, an error message is displayed, and the client terminates.
XYGATESM Host
Product license file: P26F001
Macro to install license: XSM_INSTALL_LICENSE
Expiration behavior: XSM will not function if there is a problem with XTR?s License
XYGATESM Client
Product license file: P65F001
Macro to install license: n/a
Expiration behavior: The GUI will not start.
XYGATETR
Product license file: P46F001
Macro to install license: XTR_INSTALL_LICENSE
Expiration behavior: At XYGATETR server startup time the license file is checked. If the license has expired (or they are not licensed for the node) the server will not run. A message will be sent to the GUI client. This will be used by all our GUI products.
The XYGATETR server does not report any licensing error messages to EMS. When started less than 30 days to expiration or if the license has expired, no error message of any kind is displayed. If the license does not exist, no EMS message is displayed. Instead, an error message is displayed on the home terminal indicating that an open error has occurred, and the program terminates. A saveabend file is also created.
XYGATERM Client
Product license file: P68F001
Macro to install license: n/a
Expiration behavior: The GUI will not start.
XYGATEFE (NonStop Server)
Product license file: P18F001
Macro to install license: XFE_INSTALL_LICENSE
Expiration behavior: The XYGATEFE server reads the license file at every program invocation. Starting 30 days before the license expires, a countdown message is written to EMS. When a license does not exist, an EMS message is reported. If the license has expired, no EMS message is displayed. Instead, an error message is displayed on the home terminal indicating that the license has expired, and the program terminates. Additionally, a Saveabend file is created.
XYGATEFE Windows
Product license file: P17F001
Macro to install license: n/a
Expiration behavior: The XYGATEFE server reads the license file at every program invocation. Starting 30 days before the license expires, a countdown message is placed in the XYGATEFE startup banner. Once the license becomes invalid, an error message is displayed, and the program terminates.
XYGATEFE OS 390
Product license file: P31F001
Macro to install license: n/a
Expiration behavior: The XYGATEFE server reads the license file at every program invocation. Starting 30 days before the license expires, a countdown message is placed in the XYGATEFE startup banner. Once the license becomes invalid, an error message is displayed and the program terminates.
XYGATEFE Unix
Product license file: P33F001
Macro to install license: n/a
Expiration behavior: The XYGATEFE server reads the license file at every program invocation. Starting 30 days before the license expires, a countdown message is placed in the XYGATEFE startup banner. Once the license becomes invalid, an error message is displayed, and the program terminates.
XYGATEEFTP NonStop Server
Product license file: P24F001
Macro to install license: XEF_INSTALL_LICENSE
Expiration behavior: The XYGATEEF program checks the license file each time a client requests an FTP connection. If the license file is invalid, then the server disconnects.
XYGATEMA
Product license file: P28F001
Macro to install license: XMA_INSTALL_LICENSE/ XMA_NETWORK_LICENSE_INSTALL
You must first install the XMA license on the main node using XMA_INSTALL_LICENSE. XMA_NETWORK_LICENSE_INSTALL will then copy the license to all the remote nodes.
Expiration behavior: When an XMA SERVERCLASS starts, the license file is checked. If the license file has expired, the server will not start. The XYGATESR object used by XYGATE/MA checks the P28F001 license also. It will ABEND if the license has expired.
XYGATEOA
Product license file: P43F001
Macro to install license: XOA_INSTALL_LICENSE
Expiration behavior: XYGATEOA checks its license on startup. If the license has expired, it will not start.
Please note that if you have configured your OSS service to start XYGATEOA via XYGATEAC and the XYGATEAC license has expired, you will not be able to log in to OSS.
XYGATEKM
Product license file: P32F001
Macro to install license: XKM_INSTALL_LICENSE
Expiration behavior: The XYGATEKM server reads the license file at every program invocation. Starting 30 days before the license expires, a countdown message is written to EMS. When a license has expired (or is not found), an error message is written to EMS and the program terminates.
XYGATESO
Product license file: P74F001
Macro to install license: XSO_INSTALL_LICENSE
Expiration behavior: The XYGATESO server does not report any licensing error messages when it is started less than 30 days to expiration or if the license does not exist. If the license has expired, no EMS message is displayed. Instead, an error message is displayed on the home terminal indicating that the license has expired, and the program terminates. All remaining XSO programs continue to function.
XYGATEEL
Product license file: P16F001
Macro to install license: n/a
Expiration behavior: The XYGATEEL server does not report any licensing error messages to EMS. When started less than 30 days to expiration or if the license has expired, no error message of any kind is displayed. If the license does not exist, no EMS message is displayed. Instead, an error message is displayed on the home terminal indicating that an open error has occurred, and the program terminates.
XYGATEHE
Product license file: P39F001
Macro to install license: XHE_INSTALL_LICENSE
Expiration behavior: The XYGATEHE server does not report any licensing error messages to EMS. When started less than 30 days to expiration, no message of any kind is displayed. If the license does not exist, no EMS message is displayed. Instead an error message is displayed on the home terminal indicating that an open error has occurred, and the program terminates. If the license has expired, no EMS message is displayed. Instead, an error message is displayed on the home terminal indicating that the license has expired, and the program terminates.
XYGATESH
Product license file: P63F001
Macro to install license: XSH_INSTALL_LICENSE
Expiration behavior: The XYGATESH server reads the license file at every program invocation. Starting 30 days before the license expires, a countdown message is written to EMS. When a license does not exist, no EMS message is reported. Instead, a message is written to the home terminal indicating that the license is bad. If the license has expired, no EMS message is written. Instead a message is written to the home terminal indicating that the license is bad, and the program terminates.
Related Articles
XYGATE: XYGATE host license keys - what happens with a system change?
The licensing system does not enforce core checking. EMS messages may appear, but it shouldn?t impact how the product works. The license should work if the system name/expand number is valid (valid as in known by HPE and XYPRO). A change in the ...
How to check if a license is expiring
Licenses can be checked using the license check macro, the XYGATE Configuration Manager GUI (XCF) or using the asset feature in XS1. Option 1: Using the license check macro on the Nonstop LICCHK <$VOL>.<SUBVOL>.<LICENSEFILE> product_version for ...
XAC: When does XAC warn about product license expiration
As the license expiration message is written to the EMS collector defined in the XAC ACCONF file. XMA can be configured to include a EMS mover and apprporiate filter to send the message to send an email or take some other action. To remove the ...
XYGATE: License Bad - has no signature
This issue can be resolved by re-uploading the license in BINARY. When a license is uploaded in ASCII instead of binary, you will get this error message. Steps to resolve: 1. Purge or rename the bad license out of the way 2. Re-upload the license to ...
XYGATE: How to install an individual XYGATE product license from a P99F001 master license file
License Installation Directions: 1. Please upload the p99F001 license file in binary to a temporary subvolume. **Make sure this is uploaded anywhere other than a product installation subvolume. It should not be uploaded to the product installation ...