For TCP/IP for VSE and its related components, use the Product Key installation procedure found in the TCP/IP installation manual.

Transcription

1 June 10, 2008 CSI Product Keys in VSE All of the Software Products from CSI International are protected by a Product Key. For TCP/IP for VSE and its related components, use the Product Key installation procedure found in the TCP/IP installation manual. For the following products, the product keys must be installed in your system using the process described in this document: - BIM-ALERT (release 5.1D and above) - BIM-EDIT (release 5.6 and above) - BIM-EPIC (release 6.4 and above) - BIM-FAQS/ASO (release 5.2D and above) - BIM-FAQS/PCS (release 5.2D and above) - BIM-PC/TRANSFER (release 1.8D and above) - CSI-Sort - CSI-QCOPY for VSE (release 1.3A and above) - Data-Miner (release 4.3 and above) - Dr. Crypto - Dr. D (release 6.8 and above) - Entrée for VSE - HFS - M-Pact for VSE (CSI-PACK) - Override for VSE (CSI-BUFF) - RAAD for VSE - Reliant for VSE (CSI-RECOV, CSI-JOURNAL, CSI-JMASTER) - SeeVSE - Vault for PC Files - VSAM/Easy (release 4.3 and above) - VSHARE for VSE (release 3.0 and above) - VSUM for VSE For all other CSI Products (formally BIM products), an expiration zap is required to authorize the product. 1

2 Overview A separate Product Key will be issued to you for each CSI International VSE product you have licensed. Each Product Key is for a specific product, and will authorize the use of that product on a specific CPU until a specific date, depending on the type of license agreement you have signed. If you are licensed to run a product on more than one physical CPU, then you will be issued a separate Product Key for each CPU serial number. (Note that LPARs are considered to be the same physical CPU). If you did not receive Product Keys for each of your products, please contact your CSI International product sales representative. The Product Key validation process contained in each CSI product requires the following: 1) Access to a PRODKEYS.PHASE that contains all of your product authorization keys. See Installing Product Keys below. 2) Access to an SVA phase CSI$PKSV. See Activating Product Key Processing below. Getting New Product Keys and BIM Expiration Zaps Most CSI product keys expire annually on the anniversary of your license agreement. BIM expiration zaps expire on April 1 st of each year. New Product keys are available on the web site approximately 90 days prior to your license anniversary. New BIM expiration zaps are available on the web site shortly after January 1 st of each year. 2

3 Installing Product Keys Each CSI International VSE product will look for its Product Key in a load module named PRODKEYS that you will generate at your site using the JCL shown below: // JOB PRODKEYS CATALOG PRODUCT CODES // LIBDEF *,SEARCH=(PRD1.BASE) location of PRODKEY macro // LIBDEF PHASE,CATALOG=lib.slib your common library // OPTION CATAL // EXEC ASSEMBLY PRODKEY ACE-DEEM-BLOC-HILL-MEN * SAMPLE PRODUCT1 12/31/2003 PRODKEY ANTS-HELP-CRIB-HILL-WHAT * SAMPLE PRODUCT2 12/31/2003 END // EXEC LNKEDT /& Notes: The PRODKEY values in the above sample will not work on your machine. You must use the PRODKEY values that were supplied to you by CSI for your specific cpu. The PRD1.BASE is the location used to find the PRODKEY macro. The PRODKEY macro is shipped as part of VSE/ESA. The lib.slib is where you want the PRODKEYS load module to be linked. To be properly available to all CSI International products, it should be in a permanent LIBDEF. IBM ships a dummy PRODKEYS.PHASE in the library PRD1.BASE. Depending on your sites LIBDEFs, you may need to delete/replace/move this dummy phase. 3

4 Activating Product Key Processing The Product Key processing must be activated in your system prior to running any CSI International VSE product. (except TCP/IP for VSE and its related components.) This activation is accomplished by running the following job: // JOB CSIPKINT // LIBDEF *,SEARCH=(lib.slib) // SETPFIX LIMIT=4K // EXEC CSIPKINT /& Notes: This job must be run in a static partition. Normally this would be done as part of the BGINIT job run during IPL. The lib.slib is where the programs CSIPKINT and CSI$PKSV are defined. These two modules are shipped with all CSI International VSE products. The SETPFIX statement is only required if you are running this on a VSE system that is running under VM, and the partition being used does not have any ALLOCR defined to it. This job will load phase CSI$PKSV into your 31-bit SVA. This SVA phase contains control information about your CPU that is used by the Product Key validation process contained in each CSI product. If for any reason, the SVA module CSI$PKEY is corrupted during operation, it can be refreshed by running this job again and adding a PARM= REFRESH to the EXEC statement. This job only needs to be run once per IPL. You do not need to run this job when adding or changing PRODKEY entries. The Product Key validation process contained in each CSI product will use the SVA phase CSI$PKSV and the PRODKEYS.PHASE generated in the prior step. 4

5 Product Authorization Messages When you attempt to use a CSI International product, you may receive one of the following messages: prodname-9998 prodname-9999 WARNING - PRODUCT AUTHORIZATION EXPIRES IN nn DAYS This message is generated when authorization is set to expire in 30 days or less. PRODUCT AUTHORIZATION HAS FAILED, REASON=nnn, CPU=xxxxxxxx This message is generated if the product is unable to validate a Product Key., REASON= can be one of the following: 12 GETVIS Failed 20 Load For PRODKEYS table has failed 24 No Product Key found for the product and/or cpu serial number. 28 Product Key has expired. 32 CSI$PKSV not in SVA 36 CSI$PKSV module has been corrupted 40 CSIPKINT job has not run, or failed during execution. Depending on the product, these messages could appear on the system console, in the SYSLST output of the job, or on the screen if you are using a CICS product. If you see one of these messages, contact your CSI International product sales representative for a new Product Key. 5