Key/101 Enhancements

New releases and corrective service for currently supported versions of our products are published on our website support page or the product support matrix as they become available. We recommend that customers periodically check for new fixes.

Expand all | Collapse all

Version 8.1

If you are upgrading from a Key/101 product release that is prior to 7.1 then it is imperative that you read the README document for the 7.1 and 7.2 release. The README71 and README72 members are installed into the Key/101 macro library when the 8.1 version of the Key/101 product is installed.

  • All service as documented on the Phoenix Software FTP server through release 8.0 has been incorporated into release 8.1 of the Key/101 product.
  • Fixes for currently supported versions of our products are published on our web site as they become available. Please select the corrective service download link for your product from our product support matrix. We recommend that customers periodically check for new fixes.

Version 8.0

If you are upgrading from a Key/101 product release that is prior to 7.1 then it is imperative that you read the README document for the 7.1 and 7.2 release. The README71 and README72 members are installed into the Key/101 macro library when the 8.0 version of the Key/101 product is installed.

  • All service as documented on the Phoenix Software FTP server through release 7.2 has been incorporated into release 8.0 of the Key/101 product.
  • New UPGRADE and BACKOUT functions have been added to the batch TMS20$XB program. These functions may be used to facilitate a KEY/101 system upgrade. The FORMULA and DATA files may now be upgraded in place, although we continue to strongly recommend that you back up your production files before any software upgrade. Refer to the installation manual and the distributed sample JCL in members EZUPGRD and EZBKOUT for additional information on these functions.

Version 7.2

If you are upgrading from a Key/101 product release prior to 7.1, it is imperative that you read the section on the 7.1 release above before continuing.

  • All service as documented on the Phoenix Software FTP server through release 7.1 has been incorporated into release 7.2 of the Key/101 product.
  • All versions of the Key/101 product except SAO have been upgraded to support RMODE ANY execution. All non-batch components of the Key/101 product have been converted to 31-bit applications. The use of 24-bit storage has been reduced to approximately 10K for each concurrently signed-on Key/101 user.
  • The Key/101 CICS definitions have been changed. If you are using RDO, review the distributed source members KMRDO and KMPLTSD. If you do not use RDO to maintain your Key/101 CICS definitions, review source members KMPCT, KMPPT, KMFCTV and KMPLTSD. (TASKDATALOC(ANY) has been added to all of the provided transaction definitions.)
  • All user exits (including the KEYMSSE exit) must now support AMODE 31 execution. Some of the passed parameters will be defined in 31-bit storage. Your exits should be link edited as AMODE 31 or AMODE ANY and optionally as RMODE ANY. If your exits are compiled with a reasonably current Cobol compiler, they are probably already properly linked. If your exits are written in Assembler, some changes may be required to permit them to run as AMODE ANY programs.
  • The maximum size of the Key/101 CACHE buffer pool has been increased to 32M from 511K, and the default distributed CACHE buffer pool size has been increased to 768K from 100K. By tailoring and running the provided KEYMS6C job stream, you can change the default value. Acceptable values range from 64 (64K) to 32768 (32M) or zero. For all versions of the Key/101 system except SAO, the cache buffer pool will reside in 31-bit storage.

Version 7.1

  • The Key/101 CICS definitions have been changed. If you are using RDO, review the distributed source members KMRDO and KMPLTSD. If you do not use RDO to maintain your Key/101 CICS definitions, review source members KMPCT, KMPPT, KMFCTV and KMPLTSD. (Some programs have been added, and some removed; the TWASIZE was increased from 48 to 128.)
  • All relevant service previously distributed in ZAP and/or source format by TSI/Mercator is now integrated into the product.
  • The "SPECIAL" and "CUSTOM" ZAPS previously distributed by TSI/ Mercator are also integrated into the product. To use, you activate these options with a new procedure. An example procedure is distributed in the KEYMSYO source member. The sample provided is the current state, as installed, of the custom options. Note from the sample that options 10 and 11 are delivered in the active state. Run this procedure to print a complete list of the currently available custom options. As of this release, there are 32 options that may be activated, but there is room for 130. Feel free to ask for new "special" or "custom" options.
  • All Cobol statistics programs provided conform to LE.
  • The MVS VTAM (SAO) system includes five Cobol modules: CNTRLPGM, TMSCLOSE, TMSESPRT, TMSIOERR and TMSPRGCK. These programs now conform to LE, and therefore need access to the LE runtime library (CEE.SCEERUN). If this library is not in your LINKLIST, you must include a STEPLIB or JOBLIB DD statement for this data set in the Key/101 startup JCL.
  • The TMS20$V7 batch utility program will now accept a PARM= value on the EXEC statement that allows overrides to the parameters placed on the generated DFHMSD macro statements. If PARM= is not specified, PARM='TIOAPFX=YES' is the default.
  • The MVS SYSPRINT output BLKSIZE was increased to 3990 from 133 for all batch utility programs.
  • The QNAME for all MVS Key/101 ENQs was changed from TSIENQRQ to PSKEY101. If your shop has elected to downgrade the Key/101 SYSTEMS level ENQs to SYSTEM level, you may need to modify your GRSRNLxx member. (We do not recommend this practice unless you are absolutely sure that all Key/101 usage is confined to a single LPAR.)
  • The default SECCLAS= value on the MVS KEYMSSE macro was changed from "TSIKM" to "PSIKM". If your use of the security exit relied on the old default value ("TSIKM"), you may need to add "SECCLAS=TSIKM" as a parameter in the ASMEXIT procedure.
  • CICS Key/101 users that have renamed the CEMT or CSMT transaction must specify the new CEMT=xxxx parameter on the KEYMSINT macro in the INTJOB procedure. XXXX is the new name for the CEMT/CSMT command processor.
  • The default output block size for the MVS TMS20$ZD batch extract utility program was changed from 80 to zero. This means that if the BLKSIZE= parameter is not specified with the OUTFILE parameter on the EXTRACT control statement, the BLKSIZE= parameter must be specified on the DD statement. Previously, the block size defaulted to 80 in this case, which is not an efficient size. If your extract job streams do not specify the BLKSIZE= parm on the OUTFILE parameter of the EXTRACT control statement and do not currently specify the BLKSIZE= parm on the DD statement (i.e., you were depending upon the default block size of 80), you may want to activate option 30 in the KEYMSYO custom options procedure, which sets the default block size to 80. This option is the reverse of the "ZD0BLKSZ" custom zap.
  • The default VSE logical unit for the TMUSER file in the TMS20$Z0 batch utility (Batch Upload) was changed from SYS010 to SYS014 because of a conflict with TMFORM1 when using BDAM files. Since VSE allows the EXTENT statement to override the default logical unit, this change should not affect any existing TMS20$Z0 jobs.
  • As with earlier versions, the Formula file and the Data Entry file (TMFORM1 and TMDATA1) must be backed up using the batch utilities on your current KeyMaster system and then redefined, reinitialized and restored using the batch utilities installed with the new release of Key/101.

» Key/101