Scope: Tulsa Complex B Logon Procedure Effective Date: June 12th, 2011 Group Name: Software Services Mainframe Affected Locations: Tulsa - Complex B (PB02)
Summary: As the next phase of our TSO standardization effort, the following changes are being made to the Complex B (PB02) TSOLOGA logon procedure. The TSOLOGA logon procedure is being updated to access a standard set of system libraries (see Appendix A) and use HP . These changes will take effect with the next monthly Complex B system outage, currently scheduled for June 12th.
Justification: Standardize Tulsa Complex B logon procedures using HP standard dataset names.
Benefits to Users:
Currently the system ISPF, TSO, CLIST and REXX libraries used by the TSOLOGA TSO/E Logon procedure do not adhere to HP standard naming conventions. This makes maintenance harder and more error prone and can lead to the wrong CLIST of REXX Exec being updated/invoked. Standardizing library names will simplify this process and bring the logon TSOLOGA into compliance with HP standards. Details: • 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. • 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 • 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. • A new option E will now be available on the main ISPF dialog panel (see Appendix C). This is a standard HP selection.
Please see the attached word document that provides additional detail
Primary Contact: Richard Reed (richard.reed@hp.com) Secondary Contact: Rick Rakoc (richard.rakoc@hp.com)
|