Scope: Tulsa Complex A (SYK, SYV, SYZ, CA01)
Effective Date: May 14-15, 2011
Group Name: Software Services Mainframe
Affected Locations: Tulsa SEA
Summary:
As the next phase of our TSO standardization effort, the following changes are being made to the Complex A (SYK,SYV,SYZ,CA01) TSO logon procedures.
This change affects the following logon procedures:
TSOLOGA, TSOLOGCM, TSOLOGCY, TSOLOGC2, TSOLOGDA, TSOLOGD2, TSOLOGOL, TSOLOGOP, TSOLOGRF, TSOLOGSM
These logon procedures are being updated to access a standard set of system libraries (see Appendix A in attachment). These changes will take effect with the next monthly Complex A system outage, currently scheduled for May 14-15.
Justification:
TSO system Libraries need to be standarized to ensure proper and consistant maintenance.
Benefits to Users:
Currently there are numerous system ISPF, TSO, CLIST and REXX libraries used by the standard TSO/E Logon procedures. This makes maintenance harder and more error prone and can lead to the wrong CLIST of REXX Exec being invoked. Standardizing library names will simplify the process and reduce the need for multiple logon procedures.
Details:
Summary of Changes -
• The contents of the old libraries have been copied to their new replacements. You should experience no differences with the operation of your TSO/E applications after the change.
• In cases where there were several related libraries, these have been merged into one new library. In the few cases where there were duplicate names, the newest version was used.
• The old libraries will still be available for at least 120 days after the upgrade to give time for you to update any references you may have to the old libraries in your private JCL, CLIST or REXX members. The old libraries will be locked down, preventing any future updates.
• If you have a private CLIST or REXX EXEC library that reference or re-allocates the old libraries, you will need to update those references with the new names.
• After the change all production and test JCL that references the old libraries will need to be updated. The CIG team will be notifying the system owners of any production jobs that need to be updated and will work with them to make the changes. Changes to test/private JCL libraries are the responsibilty of the dataset owner.
• The new user test CLIST/REXX library is SYS4.USR.CLIST.VB. This replaces TSO.TSTCMD and TSO.USRCLIST. The format of the new library has been kept Variable Blocked (VB) to simplify the upgrade.
• The new user production CLIST/REXX library is SYS3.USR.CLIST.VB. This replaces TSO.PRDCMD and TSO.PROD.REXX. The format of the new library has also been kept Variable Blocked (VB) to simplify the upgrade. To correct a security exposure this library is now catenated before the user test library (SYS4.USR.CLIST.VB).
• The SYS4.USR.CLIST.VB library is provided for user developed CLIST/REXX members and can be updated by anyone with a TSO userid. The SYS3.USR.CLIST.VB library is for production user developed CLIST/REXX members, it is RACF protected and only updatable by using OM (Object Manager).
• After the change this will be the process to implement user developed CLISTS/EXEC’s using OM.
o Add your new or updated CLIST/EXEC to the SYS4.USR.CLIST.VB library. If the member does not already exist in any of the production libraries you will be able to immediately test it. If you have no need to promote your CLIST/EXEC to production you can stop here.
o Testing - If this is an update to an existing member in SYS3.USR.CLIST.VB and you wish to test it, you will need to use the %ISPFTEST EXEC to swap your CLIST concatenation order prior to executing the CLIST/EXEC and prior to invoking ISPF. This is necessary since there would be a member with the same name in the production library and it is concatenated before the test library. When resolving names the system always selects the first member it finds in a library concatenation. The %ISPFTEST exec swaps the order of the user libraries, so that the test library comes first. Once you have finished testing you can then either logoff or exit ISPF and execute the %ISPFPROD EXEC to reset the CLIST library concatenation order.
SYSPROC order after executing %ISPFTEST (order for testing)
//SYSPROC DD DISP=SHR,DSN=SYS3.TSO.CLIST.VB
// DD DISP=SHR,DSN=SYS1.TSO.CLIST.VB
// DD DISP=SHR,DSN=SYS2.TSO.CLIST.VB
// DD DISP=SHR,DSN=SYS4.USR.CLIST.VB <= test before prod
// DD DISP=SHR,DSN=SYS3.USR.CLIST.VB
SYSPROC order after executing %ISPFPROD (default order)
//SYSPROC DD DISP=SHR,DSN=SYS3.TSO.CLIST.VB
// DD DISP=SHR,DSN=SYS1.TSO.CLIST.VB
// DD DISP=SHR,DSN=SYS2.TSO.CLIST.VB
// DD DISP=SHR,DSN=SYS3.USR.CLIST.VB <= prod before test
// DD DISP=SHR,DSN=SYS4.USR.CLIST.VB
o After you have finished testing you would then implement your new/updated CLIST/EXEC using OM. OM will then copy the CLIST/EXEC from SYS4.USR.CLIST.VB to SYS3.USR.CLIST.VB and delete the member from SYS4.USR.CLIST.VB.
• A new option E will also be available on the main ISPF dialog panel (see Appendix C). This is a new standard HP selection.
Primary Contact: richard reed (richard.reed@hp.com)
Secondary Contact: rick rakoc (richard.rakoc@hp.com)
|
Usercomm - TULSA - Complex A TSO Logon Procedues and System Library Standardizationc (Update) 