K E Y / 1 0 1   7.1   —   R E A D M E   —   July 2004

 1) The Key/101 CICS definitiions have been changed.  If you are using
    RDO please review the distributed source members: KMRDO and KMPLTSD.
    If you do not use RDO to maintain your Key/101 CICS definitions then
    please review source members: KMPCT, KMPPT, KMFCTV and KMPLTSD.
    (Some programs have been added and some removed and the TWASIZE was)
    increased from 48 to 128.)
            
 2) All relevant service previously distributed in ZAP and/or source
    format by TSI/Mercator is now integrated within the product.
      
 3) The "SPECIAL" and "CUSTOM" ZAPS previously distributed by TSI/
    Mercator have also been integrated into the product but these custom
    options must be activated with a new procedure if their use is
    desired.  An example of this procedure is distributed in the
    provided KEYMSYO source member.  The sample that is provided is the
    current state, as installed, of the custom options.  You will note
    from the sample that options 10 and 11 are delivered in the active
    state.  By running the provided procedure a complete list of the
    currently available custom options will be printed.  There are
    currently 32 options that may be activated but we made room for 130.
    Feel free to ask for new "special" or "custom" options.
       
 4) The provided Cobol statistics programs are now all LE conforming.
         
 5) The MVS VTAM (SAO) system includes five Cobol modules: CNTRLPGM,
    TMSCLOSE, TMSESPRT, TMSIOERR and TMSPRGCK.  These programs are now
    all LE conforming and therefore will need access to the LE
    runtime library (CEE.SCEERUN).  If this library is not in your
    LINKLIST then it will be necessary to provide a STEPLIB or JOBLIB
    DD statement for this dataset in the Key/101 startup JCL.
   
 6) The TMS20$V7 batch utility program will now accept a PARM= value
    on the EXEC statement that will allow overrides to the parameters
    placed on the generated DFHMSD macro statements.  If the PARM=
    keyword is not specified then PARM='TIOAPFX=YES' is the assumed
    default.
   
 7) The MVS SYSPRINT output BLKSIZE for all batch utility programs has
    been changed from 133 to 3990.

 8) The QNAME for all MVS Key/101 ENQ's has been changed from TSIENQRQ 
    to PSKEY101.  If your shop has elected to downgrade the Key/101
    SYSTEMS level ENQ's to SYSTEM level then your GRSRNLxx member may
    need to be modified.  (We do not recommend this practice unless
    you can be absolutely sure that all Key/101 usage is confined to a
    single LPAR.)

 9) 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") then you may need to add "SECCLAS=TSIKM"
    to the parameters specified in the ASMEXIT procedure.

10) 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.

11) The default output block size for the MVS TMS20$ZD batch extract
    utility program has been changed from 80 to zero.  This means that
    if the BLKSIZE= parameter is not specified with the OUTFILE
    parameter on the EXTRACT control statement then the BLKSIZE=
    parameter must be specified on the DD statement. In past releases if
    the above scenario was encountered the block size would simply
    default to 80, a rather inefficient block 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) then you may want to activate option 30 in
    the KEYMSYO custom options procedure.  If option 30 is on the
    default block size will be set to 80 as in prior releases of the
    product.  This option is the reverse of the custom zap formerly
    known as "ZD0BLKSZ".

12) The default VSE logical unit for the TMUSER file in the TMS20$Z0
    batch utility (Batch Upload) has been changed from SYS010 to
    SYS014.  The change was made due to 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.
    
13) 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.

    ___________________________________________________________________ 
    
    Fixes for currently supported versions of our products are published 
    on our web site as they become available.  Please select the FTP
    directory for your product(s) from our support page noted below. We
    recommend that customers periodically check for new fixes.


    Our support page is at: http://www.phoenixsoftware.com/support

Home | About Us | Contact Us | Products | Support | News | International To request detailed product information or talk to a Phoenix Software representative, call 1-310-338-0400, send a fax to 1-310-338-0801, or send an . © Copyright 1997– by Phoenix Software International. All rights reserved. Trademarks and registered trademarks are properties of their respective owners. Please send comments, questions, and/or suggestions to the