September 3, 2003
Series on South Migration
CIT plans to shut down the South system effective January 12, 2004. Watch two Web sites regularlyTitan/South System News and the Titan Transition. Both Web pages are continually updated.
This is the seventh article in the series on the migration processsso that you don't miss important news and you do have a smooth transition to Titan. These articles are reprinted from Titan Transition Migration Process Web page.
Topics to be covered in this series over the next months
Special Considerations < ARTICLE BELOW
Special Considerations
Multiple Titan USERids
Titan disk data sets begin with a USERid (aaaaiii).
Each Titan USERid is associated with one and only one account. If your South system initials are valid for multiple accounts, you will have multiple USERids on Titan. For example, user iii, valid for accounts aaaa and bbbb, will have two USERids on Titan: aaaaiii and bbbbiii.
Initially, USERid aaaaiii is valid for account aaaa and USERid bbbbiii is valid for account bbbb. Later, you may decide to change your USERid (e.g., aaaaiii) to be valid for a different account. Your USERid (aaaaiii) will not change even though you are no longer associated with account aaaa.
Account Sponsors
Account Officials
To provide customers additional flexibility in managing their accounts, there are four types of Account officials on Titan:
- Account sponsors
- Security coordinators
- Billing coordinators
- Deregistration officials
Set Your Titan Sponsor USERid
Account sponsors on the South system whose initials are valid for multiple accounts (and thus have multiple userids on Titan) must select one of their Titan USERids to be their Titan Sponsor USERid. Go to South Web Sponsor and select Set Titan Sponsor Userid under the Accounts section. This Titan Sponsor USERid can be used to perform sponsor functions for any of the accounts for which one is a sponsor.
Account Sponsor Authorities
Account sponsors and Deregistration officials on the South system continue to have all of the authorities they currently have on the South system. South account sponsors and DO's should be aware of the following differences on Titan:
- Accounts sponsors can assign security coordinators and billing coordinators to give limited authority to others to handle specific aspects of account managment.
- There is no limit to the number of alternates for any of these positions.
- Security coordinators have all of the security authorities of an account sponsor. They cannot add, remove or reassign customers within their account, nor can they see billing data for the account.
- Billing coordinators can access the billing information for the account but have no other authorities of the account sponsor.
The Titan Accounts page provides details of the duties and responsibilities of these four positions.
Databases
DB2 data, objects and privileges will be moved to Titan by our system staff. In general, DB2 will function the same on Titan as it does on the South system. However, users may be affected by changes in RACF security implementation and JCL syntax on Titan.
Example 1: If you have South system initials valid for multiple accounts, when you issue the SQL statement:
SET CURRENT SQLID='mysqlid'
Example 2: If you use the USER= parameter on your JOB card:
Please check South System Summary of Changes for additional information about differences between the South and Titan systems.
Users will be allowed to test on Titan prior to the DB2 migration. Please contact Database Technologies Staff at (301) 496-9158 for assistance.
Transferring Data
FTP is available on Titan. For specific information on using FTP on Titan, refer to the manual: Network Access to the Titan System, available online at the CIT Publications page, under OS/390 Systems: OS/390 Connectivity.
CONNECT:Direct provides data transfer capabilities between computing systems in a robust manner. The naming convention for CONNECT:Direct on Titan is as follows:New Node Names and IDs on Titan
- The node name is NIH.STD.NDM
- The APPLid is NIH4NDM
- The NETid is NIH
Users need a valid Titan USERid and RACF password to use CONNECT:Direct.
Administrators of remote systems should add the above CONNECT:Direct node definitions to their net map files and also add the VTAM definition to their VTAM tables. Changes to the SNODE specification should not be made until the application actually moves to Titan.
Comments | NIH Computer Center | Transition to Titan | Subscribe/Unsubscribe | Current Issues | Archive |